Fake Data Generator

What is a fake data generator?

A fake data generator produces realistic-looking but completely synthetic records — rows of names, emails, addresses, prices, dates and IDs that you can pour into a database, an API mock, or a spreadsheet. The data looks real (so your UI and reports behave like production) but isn't tied to any real person, so it's safe to share and commit.

You reach for one constantly: seeding a freshly migrated database, filling a table so a list view doesn't look empty in a demo, stress-testing pagination, generating a CSV to test an import flow, or building a JSON fixture for front-end work before the backend exists. Typing that data by hand is slow and the values end up unrealistic — everyone's name becomes "Test Test" and every city is "asdf". A generator gives you a thousand believable rows in a second.

This tool lets you design your own schema, pick from 20+ field types, set any row count up to 10,000, and export as CSV, JSON, or SQL — all in your browser.

How to use it

1. Build your schema. Each row in the builder is one column: give it a name (the CSV header / JSON key / SQL column) and choose a field type from the dropdown.
2. Add or remove columns with the buttons — there's no fixed template, so model exactly the table you need.
3. Set the row count (1–10,000).
4. Pick an output format: CSV, JSON, or SQL INSERT. For SQL, type the target table name.
5. Press Generate. A preview of the first 20 rows appears immediately; the full set is held ready for export.
6. Copy the output to your clipboard or Download it as a .csv, .json, or .sql file.

A sensible default schema (name, email, city) is generated the moment the page loads, so you always have something to look at and copy.

The field types

Each field type maps to a realistic value generator:

• Identity: Full Name, First Name, Last Name, Username, Email.
• Location: Street Address, City, Country, Zip.
• Business: Company, Job Title, Currency Amount.
• Numbers & flags: Integer, Float, Boolean.
• Time: Date (YYYY-MM-DD) and Datetime (YYYY-MM-DD HH:MM:SS).
• Identifiers & web: UUID, URL, Color Hex.
• Text: Lorem Word and Lorem Sentence — handy for titles, descriptions, and notes.

Mix and match these to model almost any table: a users table (name, email, username, country), an orders table (UUID, currency amount, datetime, boolean "paid"), or a products table (company, lorem sentence, float price, color hex).

CSV vs JSON vs SQL — which export should I use?

The right format depends on where the data is going — and if you later need to flip an export between the two, the JSON ↔ CSV Converter does it in a click.

CSV

CSV is the universal interchange format. Open it in Excel, Google Sheets or Numbers, feed it to a COPY / LOAD DATA bulk import, or use it to test a file-upload feature. The first line is a header row of your column names, and any value containing a comma, quote or newline is properly quoted and escaped so it round-trips cleanly.

JSON

JSON is what front-end and API work wants. The output is an array of objects — one object per row, your column names as keys — pretty-printed and ready to drop into a fixtures file, a db.json for a mock server, or a request body. Numbers and booleans come through as real JSON numbers and booleans, not strings.

SQL INSERT

SQL INSERT statements let you seed a database directly: copy the output, paste it into your SQL console or a migration, and run it. You set the table name, identifiers are double-quoted, strings are single-quoted with embedded quotes escaped, numbers are emitted bare, and booleans become TRUE / FALSE. It's the fastest way to go from "empty table" to "realistic data" without an ORM or import script.

Seeding databases and testing UIs

Two jobs come up again and again:

Seeding a database. After a migration your tables are empty, which makes the app look broken and hides performance problems. Generate a few thousand rows that match your schema, export as SQL, and run it — now your list views, search, and pagination behave like they will in production. Generate 10,000 rows and you'll quickly see which queries need an index.

Testing UIs and APIs. Front-end developers shouldn't wait for a backend. Model the shape the API will return, export JSON, and wire it into a mock. You can deliberately generate long names and lorem sentences to check how your layout copes with overflow, or generate booleans and dates to exercise every branch of a component.

Because the data is synthetic, it's safe to commit these fixtures to the repo — no risk of leaking real customer data into version control.

Tips for better test data

• Name columns the way your code expects (first_name, created_at) so exports drop straight in.
• Use Datetime for created_at / updated_at columns to get sortable, realistic timestamps.
• Booleans drive branches — add an is_active or paid column to test both states in your UI.
• Generate big once. Make 10,000 rows, download the CSV, and reuse it — no need to regenerate every run.
• For unique keys, use UUID. Every UUID is unique within a batch, so it's safe as a primary key — and if you just need a handful of standalone IDs, the UUID Generator produces them on demand.

The wedge: unlimited, local, no signup

Most people hit a hosted generator like Mockaroo first — and quickly hit its walls: free accounts are capped at 1,000 rows, larger exports and API access need a paid plan, and you have to create an account to do much at all. Your schema and data also travel to someone else's server.

This tool flips all of that:

• No row cap that matters. Generate up to 10,000 rows per click, free, as many times as you like.
• No signup, no account, no quota. Open the page and generate.
• 100% local. Your schema and every generated row are produced in your browser with JavaScript. Nothing is uploaded, nothing is logged, and it works offline.
• No watermark, no upsell. The CSV, JSON or SQL you download is clean and yours.

Build the schema, pick a format, and generate as much realistic test data as you need — instantly and privately.