- What's the difference between this and the Fake Address Generator?
- The Fake Address Generator gives you a single record at a time — one address per click — and the output is formatted for a mailing label or a single form field. This one is the tabular version: you pick multiple columns (name + email + phone + address + ...) and get up to 1000 consistent rows in a JSON or CSV file. Use Fake Address for filling out a sign-up form by hand; use Dummy Data for seeding a database or a test suite.
- Are the names, emails, and addresses real?
- No. Names come from public-domain Census frequency lists (the most common 200 first names and 200 last names in the US), addresses use real street names + cities + numbers combined randomly, and emails are built from the random name plus a fake domain (example.com, test.net, etc.). Each row is statistically plausible but the combinations don't refer to real people, businesses, or buildings.
- How are rows kept consistent?
- When the generator builds a row, it picks one first name, one last name, and one state up front, then derives the email and ZIP from those. So Jane Smith's email won't say someone else's name, and Texas rows always start with a TX ZIP prefix. Different rows are independent — row 7's identity has nothing to do with row 8's.
- Will the same generation produce the same data twice?
- Not by default — every tap of Generate uses fresh randomness, so re-running gives you a different batch. If you need reproducible output for tests, the underlying engine accepts a numeric seed; we don't expose that in the UI today, but agents using the engine via MCP can pass one.
- What's the row cap and why?
- 1000 rows. That's enough to seed a development database, populate a CSV preview, or stress-test a table component, without bloating the page or freezing the browser. If you need millions of rows, write a script that calls the engine in a loop — the engine is pure JavaScript with no per-row overhead beyond Math.random().
- Is the data uploaded or logged?
- No. Generation runs entirely in your browser. The data tables (names, cities, companies, ZIP prefixes) are bundled into the page; the JavaScript reads them locally and writes the rows directly into the output area. You can disconnect from the internet and the tool still works.
- Can I use these for payments, real users, or shipping?
- No. Payment processors run AVS checks; the addresses won't validate. Email providers will bounce mail to the fake domains. The names don't correspond to real accounts. Use this output for fixtures, demos, tests, and screenshots — not anywhere that interacts with a real system.
- Why CSV with CRLF line endings?
- RFC 4180 (the de-facto CSV standard) calls for CRLF between rows. Excel, Google Sheets, Numbers, and most CSV parsers handle either, but CRLF is the safer default — especially for Windows-bound users. Quoted fields and double-quote escaping follow the same RFC.
- Can I add more fields?
- Today's field list: first name, last name, email, phone, address, city, state, ZIP, country, company, date, UUID, lorem text, number range. If you want more — gender, age, job title, IBAN, IMEI — let us know and we'll consider adding them. For now, the philosophy is to ship the fields developers actually need 90% of the time and stop there.
- How is this different from faker.js or Mockaroo?
- faker.js is a library — you install it and write code. Mockaroo is a paid service with a sign-up wall once you hit a certain row count. This is the browser version: open the page, click a few buttons, get your rows, close the tab. Zero install, no account, no tiering. For programmatic use, you can call the same engine via the Microapp MCP server.
