Generate realistic fake data (names, addresses, emails, phones) for testing without using real personal information.
This tool produces batches of fabricated personal records - names, street addresses, email addresses, and phone numbers - for use in test environments, form testing, and demo data. You pick the fields you want and the number of records, and each row is composed from curated lists and format patterns rather than copied from real people. The thing most users get wrong is treating the output as stable fixtures: each run returns a fresh batch you cannot reproduce on demand, and values that look real are still fabricated - the right shape, but not tied to any real person, so they are not working contacts you can write to or call.
You choose which categories of data to include - names, addresses, emails, phones - and how many records you want. The tool returns one row per record, with a value in every selected field, so a batch can be reviewed at a glance and then moved into a test database, spreadsheet, or fixture file. Generation happens locally in the browser, so nothing you configure is transmitted anywhere.
Each value is constructed to look structurally real: a name has first and last parts, an email has a local part, an @ sign, and a domain, a phone follows the digit pattern of its numbering system, and an address has a house number, street, city, and postal code. The realism is structural - enough to pass format checks and casual inspection, which is what testing needs - while the content stays invented.
No. A generated email is a string shaped like an address, not a registered mailbox, so confirmation links and replies never arrive and messages bounce. Use the values only inside your own test environments, forms, and databases. If a real service demands a working inbox, you need an address you actually control, which is a different tool for a different job.
Values are drawn at random from finite lists, and random draws repeat - more often as the batch grows. If your schema treats email or phone as a unique key, scan the generated rows and replace or regenerate repeats before importing, because the output does not guarantee uniqueness. Regenerating a fresh batch is usually the fastest fix.
The behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.
Format, validate, and beautify JSON with syntax highlighting and error detection.
Encode text or files to Base64 and decode Base64 strings back to their original form.
Format and indent SQL queries for better readability across all major dialects.
Convert HTML markup into clean Markdown syntax with support for tables and lists.
Write Markdown and see the rendered HTML output in real time with live preview.
Visualize unified diffs and patch files with color-coded additions and deletions.