Runs locally in your browser. Nothing you enter is uploaded to our servers.

Count5
5

Describe fields as type shortcuts (email, uuid, int:18-65) or as a JSON Schema object. Nested objects and arrays are supported.

Type reference

Tap a type to copy it into the clipboard, then paste into the schema.

You can also paste a JSON Schema object with type, format, enum, minimum/maximum, properties, and items.

Schema
Result

Tips for test data

Never use real personal data in fixtures.

Match formats your validators expect (email, phone, IBAN).

Keep seed/reproducibility in mind for flaky tests.

Separate test data from production databases clearly.

Regenerate data when schemas change.

Fake rows for fixtures and QA

Processing stays in your browser — your input is not uploaded to our servers.

The generator builds tabular sample data — names, emails, ids — so you can fill a demo database without copying production PII.

Generated people are fictional. Do not use the emails to spam or to impersonate real staff.

Generate test data

  1. Choose fields and row count

    Only columns the API actually needs. Extra PII in fixtures becomes a habit.

  2. Generate the grid

    Copy JSON or a table into your seed script.

  3. Keep it obviously fake

    If a value could be a real customer, mark the environment as test in the data too.

Test data FAQ

Are these real people?

No. They are synthetic. Still do not ship the dump to a public gist with “looks real” payroll numbers.

Can I generate production-shaped PII?

Shape yes, real identities no. Mask anything that came from prod.

Is generation local?

Yes. Rows are created in the browser.