Free Fake JSON Data Generator
Generate fake JSON test data with custom schemas. Supports strings, numbers, dates, emails, and more. Free, fast, and works entirely in your browser with no sign-up required.
Updated
Fake JSON Data Generator
Generate fake JSON test data with custom schemas. Supports strings, numbers, dates, emails, nested objects and more.
Preset Templates
Schema Fields
Generation Options
Frequently Asked Questions
What is the Fake JSON Data Generator?
The Fake JSON Data Generator is a free online tool that generate fake json test data with custom schemas. supports strings, numbers, dates, emails, and more. It runs entirely in your browser with no installation or sign-up needed.
What field types are supported?
String, number, boolean, date, email, phone, name, address, UUID, and Lorem ipsum text.
Can I generate nested objects?
Yes — add nested object fields to create complex JSON structures.
Is it free?
Yes, completely free.
Does the Fake JSON Data Generator work on mobile devices?
Yes, the Fake JSON Data Generator is fully responsive and works on smartphones and tablets. You can use it on any device with a modern web browser -- no app download required.
Do I need to create an account to use this tool?
No account or registration is needed. Simply open the Fake JSON Data Generator in your browser and start using it immediately. There are no sign-up walls or usage restrictions.
How do I use the Fake JSON Data Generator?
Simply enter your input in the provided field, adjust any settings to your preference, and the tool will process it instantly. You can then copy the result to your clipboard or download it.
Which browsers are supported?
The Fake JSON Data Generator works in all modern browsers including Chrome, Firefox, Safari, Edge, and Opera. For the best experience, use the latest version of your preferred browser.
What is the difference between JSON and JSONL output?
JSON output is a single pretty-printed array of objects with two-space indentation — every record sits inside one set of square brackets, which is ideal for pasting into a file, a mock server, or a fixture. JSONL (JSON Lines) puts one complete JSON object on each line with no wrapping array and no commas between records. That line-delimited shape is what many data pipelines, log processors, and bulk-import tools expect, because they can read and process one record at a time without loading the whole file into memory. Choose JSON when a tool or person needs to read the dataset as one structured document, and JSONL when you are streaming records or feeding a bulk loader. This generator offers both formats with a single toggle, so you can produce the same schema either way and copy or download whichever your workflow needs.
What UUID format does the generator produce?
The uuid field type produces version-4 UUIDs, the random variant of the universally unique identifier standard. Each value follows the canonical 36-character pattern of eight, four, four, four, and twelve hexadecimal digits separated by hyphens, with a literal "4" marking the version position and the variant digit constrained to the 8, 9, a, or b range. Because the bits are drawn from your browser's random number generator, the chance of two generated IDs colliding is vanishingly small, which is exactly why v4 UUIDs are the common choice for primary keys, record identifiers, and request IDs in test data. All four preset templates use a UUID as their id field, so loading any preset gives you ready-made identifiers. Add a field of type uuid whenever you need realistic, unique keys rather than sequential numbers in your mock dataset.
What date range and format does the date field use?
The date field type outputs values in ISO 8601 calendar format, written as YYYY-MM-DD — for example 1998-04-23 — with no time component attached. Each date is picked at random from a window that starts on 1 January 1970 and runs up to the current day, so you get a realistic spread of past dates rather than every record sharing one timestamp. That variety is useful for testing how a table sorts chronologically, how a date filter behaves across decades, and whether your formatting handles older years correctly. The ISO ordering also sorts correctly as plain text, which keeps things predictable in spreadsheets and databases. If your schema needs a created or published timestamp, add a date field and give it a clear key name like createdAt; several built-in presets already include one so you can see the format in action immediately.
How many records can I generate at once?
You set the volume with the record count field, which accepts any whole number from 1 up to 1000 in a single generation. Producing a larger batch is one of the main reasons to use mock data rather than hand-typing a record or two: generating a hundred or more rows at once reveals how a table paginates, whether long text values break your layout, and how a list performs when it is actually full. Everything is created locally by your browser, so even a thousand records generate instantly with no upload and no waiting on a server. If you need more than a thousand entries, generate a full batch, then run the tool again and append the additional output to your file. Set your desired count, choose JSON or JSONL, and generate the whole dataset in one click.
What do the preset templates include?
Four presets load a sensible schema instantly so you do not have to build one field by field. The User preset gives you a UUID id, name, email, phone, city, a createdAt date, and an active boolean flag. Product includes an id, name, price, an inStock flag, a lorem description, and createdAt. Order provides an orderId, customer, email, total, status, and orderDate. Blog Post covers an id, title, author, lorem content, a published flag, publishedAt, and a url. Each one is a realistic starting point for a common data model rather than a fixed template — after loading a preset you can rename fields, change types, add new ones, or nest an object inside a record to match your own structure exactly. Pick the closest preset, adjust it to fit your schema, then set a record count and generate.
Related Tools
Free Secure Password Generator
Generate secure, random passwords with customizable options. Free, fast, and works entirely in your browser with no sign-up required.
Free UUID/GUID Generator
Generate universally unique identifiers (UUIDs/GUIDs). Free, fast, and works entirely in your browser with no sign-up required.
Free QR Code Generator Online
Create QR codes for URLs, text, WiFi, and contacts. Customize colors, size, and error correction. Free, private — runs in your browser, no sign-up.
Free JSON Formatter & Validator
Format, validate, and beautify JSON data with syntax highlighting and error detection. Free, fast, and works entirely in your browser with no sign-up required.
About the Fake JSON Data Generator
The Fake JSON Data Generator builds realistic mock datasets from a schema you define, then hands you the result as ready-to-use JSON. Instead of hand-typing dummy records or wiring up a seeding script, you describe the shape of your data field by field, pick how many records you want, and generate an array of objects in a single click. It is aimed at front-end developers building UIs against an API that does not exist yet, QA engineers who need varied test fixtures, and anyone demoing a feature that looks empty without sample content.
Everything happens in your browser. The records are produced locally with your device's random number generator — nothing is uploaded, there is no API call behind the scenes, and there is no sign-up or rate limit. That makes it safe to use for internal projects and quick to run offline once the page has loaded.
Building your schema
You define your data structure as a list of named fields, each with a type. The generator supports sixteen field types: string, number, boolean, date, email, phone, name, firstName, lastName, address, city, country, uuid, lorem, url, and object. Add a field, give it a key name, choose its type from the dropdown, and repeat. Select the object type to nest a group of child fields, so you can model structures like a user with an embedded address rather than a flat record.
Four preset templates load a sensible schema instantly so you don't start from scratch:
- User — id (UUID), name, email, phone, city, createdAt date, and an active boolean
- Product — id, name, price, inStock flag, a lorem description, and createdAt
- Order — orderId, customer, email, total, status, and orderDate
- Blog Post — id, title, author, lorem content, published flag, publishedAt, and a url
Pick a preset to populate the builder, then tweak field names and types to match your own model.
What the generated values look like
Each type produces plausibly formatted data rather than empty placeholders. UUIDs follow the version-4 format; dates are ISO YYYY-MM-DD values drawn at random from 1970 up to today; emails combine a first and last name with a real-looking domain; phone numbers use a +1-NNN-NNN-NNNN pattern; and the lorem type returns a short sentence of roughly 8 to 20 words. Names, cities, and countries are pulled from built-in lists, so an address reads like a street, city, and country code rather than random characters.
You control volume with the record count, which accepts any value from 1 to 1000. Two output formats are available:
- JSON — a pretty-printed array of objects with two-space indentation, ideal for pasting into a file or mock server
- JSONL — one JSON object per line, the format expected by many data pipelines, log processors, and bulk-import tools
Once generated, copy the output to your clipboard or download it as fake-data.json or fake-data.jsonl.
Why mock data matters
Realistic test data exposes problems that a single hard-coded record hides. Generating a hundred users at once reveals how a table paginates, whether long lorem strings break your layout, and how dates sort. Front-end teams can build and style components before the backend is ready, then swap in the live endpoint later. QA can feed the same dataset into automated tests for reproducible runs, and JSONL output drops straight into bulk-load and streaming workflows.
Because every value here is randomly generated and clearly fictitious, the dataset is safe to commit, share in a demo, or paste into a ticket without exposing real customer information. To get started, load a preset or add your own fields above, set a record count, choose JSON or JSONL, and generate.