Generate realistic fake data for testing and development. Create names, usernames, emails, addresses, phone numbers, and more. Export to JSON or CSV format
Developers building REST APIs need realistic test data, not empty arrays and placeholder strings. Pick the fields you want, set a row count, and generate fake-but-plausible records you can export as JSON or CSV. Generated emails and usernames are derived from the row's first and last name, so the data reads coherently rather than randomly.
Initializing in your browser…
Generate ultra-secure passwords with presets (Simple to Paranoid), strength analysis, entropy calculation, crack time estimation, password history, and bulk generation
Create stunning CSS gradients with linear/radial/conic types, angle control, position control, multiple color stops, 11 presets, and reverse/randomize features
Design complex box shadows with multi-layer support, inset shadows, visibility toggle, layer reordering, opacity control, and 12 professional presets
Your frontend needs a realistic 3-record user array to build against before the API exists.
Schema defined
id: uuid · name: fullName · email: email · signedUpAt: isoDate · rows: 3
Generated JSON
[
{ "id": "b1f2…9a", "name": "Maya Okafor", "email": "maya.okafor@example.com", "signedUpAt": "2024-03-12T09:14:00Z" },
{ "id": "7c4d…02", "name": "Liam Petrov", "email": "liam.petrov@example.com", "signedUpAt": "2024-05-28T17:02:00Z" },
{ "id": "e9a0…3f", "name": "Sara Kim", "email": "sara.kim@example.com", "signedUpAt": "2024-07-04T11:47:00Z" }
]You define a typed schema and the generator produces internally-consistent fake records, names that look real, valid-format emails, RFC 3339 dates, so your UI, tests, and fixtures exercise realistic shapes instead of "foo/bar". Generation is local, so no real customer data is ever involved.
Developers building REST APIs need realistic test data, not empty arrays and placeholder strings. Pick the fields you want, set a row count, and generate fake-but-plausible records you can export as JSON or CSV. Generated emails and usernames are derived from the row's first and last name, so the data reads coherently rather than randomly.
Toggle the fields you need from a fixed set of about eighteen types: first name, last name, full name, email, phone, username, street address, city, state, country, zip code, company, job title, UUID, date, credit card number, sentence, and paragraph. Each row is a flat object of string values. Values are drawn (uniformly at random) from built-in US/English word lists, so names, cities, and companies look American-English; there is no locale selector. Output is a JSON array or a CSV file, copyable or downloadable. There is no SQL export and no nested-object output. Your field selection and row count are encoded in the page URL, so you can bookmark or share a configuration link.
Select firstName, lastName, email, date, and jobTitle, generate 100 rows, and export as JSON for your mock API.
Pick fullName, company, city, and phone, generate the rows, and download as CSV for import into a dev environment.
Populate a mock API server with realistic JSON so you can demo frontend features before the backend is ready.
Export CSV to test imports, table layouts, and search results without exposing real user data.
Generate realistic rows to test table layouts, search results, and form autofill at various lengths.
Fill demo instances with believable data for client presentations and sales walkthroughs.
Each value is picked uniformly at random from a built-in list, so it is random but readable. The one correlation: email and username are built from the same row's first and last name, so they match the person.
Not directly. Output is JSON or CSV. You can import the CSV into your database or transform the JSON into INSERT statements with a quick script.
No. The word lists are US/English only, so names, cities, and companies look American. There is no locale selector.
This runs as client-side JavaScript. Keys, tokens, payloads, and other inputs never leave your device.