Rows, test cards, placeholder images, sized files, IDs and text that are safe to use in any test
Everything here runs in your browser. Files are never uploaded.You cannot build a checkout, an upload form or a table until something is in it, and three tidy rows you typed yourself hide every bug. These make the test data instead: rows as JSON, CSV, SQL or XML, card numbers for a payment sandbox, placeholder images at any size, files of an exact byte count, IDs and filler text. Every value is safe by construction: emails and links at example.com, IPs from the RFC 5737 documentation ranges, only the test cards gateways publish, and a seed that brings the same rows back.
Mock Data Generator produces records with realistic names, emails, Indian addresses with real PIN codes, dates, IP addresses, user agents and numbers, as JSON, CSV, SQL INSERT statements or XML, and the same seed always produces the same rows. That repeatability is the feature: a test that fails on run nine is only useful if run nine can be reproduced, and random data that changes every time turns a real bug into a ghost. Its focused pages each start on one job: Fake Address Generator, Random IP Generator, SQL Insert Generator, and it opens set for random dates or user agents.
Test Credit Card Numbers gives only the numbers Stripe and Razorpay publish for their test modes, with a made-up expiry and CVV, as a list, JSON or CSV. It never puts random digits behind a real issuer prefix, because that can produce somebody's live card. See the Stripe test cards and Razorpay test cards lists, or check a pasted number's Luhn digit, scheme and length with the Credit Card Validator or the Luhn Algorithm Checker.
Placeholder Image Generator makes a PNG, JPG, WebP or SVG of any size, labelled with its dimensions, for mockups and layout tests; Blank Image Generator gives a plain colour and Sample Image Download fixed files at stated byte sizes. Dummy File Generator writes a valid TXT, BIN, CSV, PDF, JPG, PNG or ZIP of an exact size up to 1 GB, padded rather than filled with content, to test upload limits; its presets are Dummy PDF Generator, Sample PDF Download, Create Large Test File and Sample CSV File.
Emails and URLs end at example.com, which RFC 2606 reserves, so a seed file loaded into the wrong environment mails nobody. IP addresses come only from 192.0.2.0/24, 198.51.100.0/24 and 203.0.113.0/24, which are never routed. Card numbers work only in a gateway's sandbox. The one gap is phone numbers: India has no fictional range, so a generated mobile number may be real and must never be dialled. The guide Test data that cannot reach a real person explains each rule.
UUID Generator makes v4 random and v7 time-ordered identifiers, up to a thousand at once, and validates one you were given. Prefer v7 for anything that becomes a database primary key: it sorts by creation time, so inserts land at the end of the index instead of scattering through it, which a large table notices.
Password Generator produces random strings for fixtures and seed scripts. Keep these out of the repository even when the data is fake, because a seeded password committed once has a habit of being reused in staging.
Lorem Ipsum Generator gives paragraphs, sentences, words or list items. The reason it is nonsense Latin rather than English is that real words invite people to read and comment on the copy instead of looking at the layout. Generate more than you think you need: a design fails at the long values, not the short ones.
Generated data is polite, and real data is not. Once the happy path works, put in the names with apostrophes and accents, the empty middle name, the four-line address, the email that is 80 characters long and the number that is negative. That is where the interface breaks, and none of it appears in a generated set unless you add it.
No. Names and streets are assembled from lists, emails end at example.com and IPs come from the documentation ranges, so they reach nobody. Cities and PIN codes are real public postal data. Phone numbers follow the Indian format but are random, so never dial one.
No. Test Credit Card Numbers gives only the numbers Stripe and Razorpay publish for their sandboxes, which those gateways refuse in live mode. It never builds a random number behind a real issuer prefix, which could match a live card.
Make a file just under and just over the limit with Dummy File Generator: a valid PDF, JPG, PNG, ZIP or other type at an exact byte count, up to 1 GB. For images at a set width and height, use Placeholder Image Generator.
Yes. Mock Data Generator takes a seed, and the same seed with the same settings produces exactly the same rows, which is what makes a failing test reproducible.
v7 for database keys, because it is time-ordered and keeps inserts at the end of the index. v4 for anything that must reveal nothing about when it was created, since v7 encodes a timestamp.
Up to a thousand UUIDs and several thousand rows of mock data in one go. It all happens in your browser, so the limit is memory rather than a quota.
Because unreadable text keeps attention on the layout. Real copy makes reviewers discuss the wording of placeholder text, and it also hides the fact that nobody has written the real thing yet.
No. Everything is generated in your browser, so a seed file with your own column names in it stays on your machine.