DevBolt
Processed in your browser. Your data never leaves your device.

How do I generate fake JSON data for testing?

Define a schema with 30+ field types (names, emails, addresses, dates, UUIDs, custom patterns) or choose from templates like Users, Products, or Orders. Generate up to 500 rows of realistic mock data. Download as .json or copy to clipboard. Everything runs in your browser — no API key required.

Generate mock user data
Input
Schema: User
Fields: id, name, email, age
Count: 3
Output
[
  { "id": 1,
    "name": "Alice Chen",
    "email": "alice@example.com",
    "age": 28 },
  { "id": 2,
    "name": "Bob Smith",
    "email": "bob@example.com",
    "age": 34 },
  { "id": 3,
    "name": "Eve Johnson",
    "email": "eve@example.com",
    "age": 22 }
]
← Back to tools

JSON Mock Data Generator

Generate realistic fake JSON data for API testing and prototyping. Define your schema with 30+ field types, use preset templates, and download the result.

Available Field Types

Person

  • First Name
  • Last Name
  • Full Name
  • Email
  • Phone
  • Username
  • Avatar URL
  • Company
  • Job Title

Location

  • Street Address
  • City
  • State
  • Zip Code
  • Country
  • Latitude
  • Longitude

ID

  • UUID
  • ObjectId (Mongo)
  • Auto Increment

Number

  • Integer
  • Float
  • Price ($)
  • Boolean

Date/Time

  • Date (YYYY-MM-DD)
  • DateTime (ISO)
  • Unix Timestamp

Network

  • IPv4 Address
  • IPv6 Address
  • URL
  • Domain

Text

  • Color Name
  • Hex Color
  • Paragraph
  • Sentence
  • Word
  • Slug

Other

  • Custom List
  • Null

About JSON Mock Data

  • Generate up to 500 rows of realistic fake data for API testing and prototyping.
  • Choose from 6 preset templates: Users, Products, Orders, Blog Posts, Todos, and Addresses.
  • Custom List fields let you define your own enum values (comma-separated).
  • Wrap output in an array or an object with a custom key name.
  • Download as .json or copy to clipboard for use in Postman, fetch calls, or test fixtures.
  • Everything runs in your browser — no data is sent over the network.

Tips & Best Practices

Pro Tip

Use realistic data types for each field

Names, emails, addresses, and UUIDs each have distinct formats. Using random strings for all fields makes mocks unrealistic and hides bugs — a regex-validated email field won't catch issues if your mock always generates 'test@test.com'. Use field-specific generators for realistic test data.

Common Pitfall

Mock data with identical patterns creates false confidence

If all mock users have the same country, language, or timezone, you won't catch i18n bugs. If all dates are in the same month, date boundary bugs hide. Ensure mocks include edge cases: different locales, DST transitions, Unicode names (é, ñ, 中文), and empty/null optional fields.

Real-World Example

Generate 500 rows to stress-test pagination and search

Test your frontend table component with 500 realistic rows to verify pagination, virtual scrolling, sorting, and filtering all work under load. This catches performance issues that don't appear with 5-row toy datasets.

Security Note

Never use mock data generators to create fake production records

Generated data should only be used in development and testing environments. Inserting fake records into production databases (even 'test' accounts) can violate data integrity, skew analytics, and create compliance issues. Use feature flags or separate environments instead.

Frequently Asked Questions

How do I generate realistic fake JSON data for API testing?
Define your schema using DevBolt's Mock Data Generator, selecting from over 30 field types including names, emails, addresses, phone numbers, UUIDs, dates, URLs, and IP addresses. Specify how many records to generate and the tool produces a JSON array instantly. The generated data follows real-world patterns. This is ideal for populating development databases, testing API endpoints, creating demo data, and load testing. All generation happens client-side.
What field types are available for mock data generation?
DevBolt supports over 30 field types: person fields (name, email, phone, username), address fields (street, city, state, zip, country, lat/long), internet fields (URL, IP, MAC, domain, user agent), commerce fields (product name, price, company), date/time fields (past, future, recent, ISO timestamps), identifiers (UUID, auto-increment), and primitives (integer, float, boolean, lorem ipsum text). You can nest objects and create arrays of any field type.
Can I generate mock data that matches my existing API schema?
Yes, configure field names and types to match your API's response structure. Create nested objects and arrays that mirror your real data model. The output is a valid JSON array usable as mock API responses, imported into development databases, or served from a local mock server for frontend development without waiting for the real backend.

Related Generate Tools