piapia123
en

Mock Data Generator

Generators

Everything runs locally in your browser — nothing is uploaded

Input
Drop a file here to load its contents
Output

Write one field per line as name:type, click Run, and get a full dataset. The values follow real formats: names come from curated pools, mobile numbers have the right length and a real prefix, and an email address is built from the reading of the name on the same row, in that locale’s convention. Name, email and username in a row all refer to the same fictional person rather than being drawn independently, so the result survives a screenshot, a demo recording or a test database.

Features

  • Input format: one field per line as name:type, with # comments and either colon style accepted
  • Seventeen types: name, email, phone, username, city, company, date, datetime, number, price, boolean, id, uuid, text, ip, url, enum
  • Arguments in brackets: number(18,60), price(10,500), date(2024-01-01,2024-12-31), enum(active,pending)
  • Name, email and username on a row belong to the same person, with the email prefix matching the name
  • Chinese datasets use Chinese names and cities, English ones use English names and US-style 555-01XX numbers, and Japanese ones use Japanese names with real mobile prefixes (090 / 080 / 070)
  • Seven outputs: a JSON array, RFC 4180 escaped CSV, tab-separated TSV, a single multi-row INSERT statement, escaped XML, YAML and TOML
  • The YAML output guards against the “Norway problem”: values such as `no`, `007` or an empty string, which YAML would read as booleans, numbers or null, are always quoted
  • TSV cannot escape tabs or newlines, so those are replaced with spaces inside values (the tool says so) rather than breaking the column structure
  • An empty input falls back to a built-in field list, so you can see the shape before editing it

How to use

  1. Write one field per line as name:type, or click Sample
  2. Choose the output format: JSON, CSV, TSV, SQL, XML, YAML or TOML
  3. Set the number of rows, and the table name if you are exporting SQL
  4. Pick the data locale: follow the interface, or force Chinese, English or Japanese
  5. Click Run, then Copy

FAQ

Could a generated phone number belong to a real person?
The numbers are well-formed eleven-digit mobile numbers, so in principle one could coincide with a real subscriber. That is fine for demos and tests, but never use them for bulk messaging or cold calls. IP addresses are limited to the private ranges 10.x, 172.16-31.x and 192.168.x, so they never point at a real host.
Why are SQL identifiers not quoted?
Deliberately. Backticks break on Postgres and double quotes break on MySQL in its default mode, while unquoted identifiers work on both. The trade-off is that a field name must not collide with reserved words such as order, group or select, which is also why names are limited to letters, digits and underscores.
Can field names be non-ASCII?
No. Identifiers in the SQL output are unquoted, so spaces, dashes and non-ASCII characters would produce an invalid statement. Field names accept letters, digits and underscores, and cannot start with a digit.
Why is the XML root element called rows?
Because XML has no notion of a table, and the table-name field exists for the SQL output — it allows characters such as dashes, which are illegal in an XML element name, so using it as one would produce XML that cannot be parsed. The XML output therefore uses a fixed `rows` / `row` shape, with fields as elements named after the fields themselves (they are already restricted to `[A-Za-z_][A-Za-z0-9_]*`, which is a valid XML element name).
Is any of this uploaded?
No. Everything is generated in browser memory, the page makes no network requests, and no account or backend is involved, so nothing is stored or logged.

Related tools