JSON to Query String
Serialise a JSON object into a percent-encoded URL query string.
Generate realistic test rows in JSON, CSV or SQL from fields you choose.
The Fake Data Generator produces test rows from the fields you choose, with each row internally consistent — the name, email and username belong to one person, and the city, region and postcode to one country.
Choose the fields you need and how many rows, and get test data that looks real enough to catch layout problems a row of "test test test" never would. Names, emails, phone numbers, addresses, job titles, dates, prices and identifiers are all available.
Each row is internally consistent, which matters more than it sounds. The name, email and username belong to the same person, and the city, region and postcode belong to the same country — so a row does not read as obviously assembled from parts. Emails use the domains RFC 2606 reserves so nothing can ever be delivered to one by accident. Output comes as JSON, CSV, SQL inserts or a JavaScript array.
The email derives from the name and the postcode from the country, so a record reads as one person rather than as assembled parts.
Names run from three characters to forty and some contain apostrophes — which is exactly what breaks a layout that looked fine with "test test test".
Every address uses a domain RFC 2606 reserves, so nothing can reach a real mailbox even by accident.
JSON for a fixture, CSV for a spreadsheet, SQL for a seed script, or a JavaScript array to paste into a test.
UK, US, German, French, Australian and Indian formats, each with the right postcode shape and phone pattern.
Pick from names, contact details, addresses, dates, numbers and more.
From one row to a thousand.
Addresses, postcodes and phone formats follow the country you choose.
JSON, CSV, SQL inserts or a JavaScript array.
No. Names are drawn from common lists and combined at random, and every email uses a domain reserved for documentation. Any resemblance to a real person is coincidence.
Nothing would be delivered. RFC 2606 reserves example.com, example.org and example.net precisely so that they can never resolve to a real mailbox.
Because "test test test" is always the same length. Real names vary from three characters to forty, some contain apostrophes, and addresses run to several lines — all of which break layouts that looked fine in development.
Yes. Values are drawn from the browser's cryptographic random source, so generating twice gives two different sets.
What people who use the Fake Data Generator think of it. Reviews come from visitors and are posted as written.
No ratings yet
Yours would be the first.
0 reviews
Newest first
No reviews yet
Be the first to rate the Fake Data Generator. It takes half a minute and no account.
Write the first reviewSerialise a JSON object into a percent-encoded URL query string.
Check JSON syntax and get the exact line, column and cause of any error.
Convert Base64 back to hexadecimal, with your choice of separator.
Identify a UUID's version and variant, and extract its timestamp.
See an IP address in binary, hex and decimal, octet by octet.
Convert a TOML config to JSON, with tables and arrays of tables resolved.
Compare two semantic versions and test them against a range.
Encode and decode Base32, including the Crockford and hex variants.