Random and Test Data Generators
These generators produce values you need when building or testing software, and a couple you need away from the keyboard: UUIDs in several versions, random names from six regional pools, test email addresses on reserved domains, fake card numbers that pass Luhn validation, random whole numbers in any range, and URL slugs made from a title. Developers seeding databases, QA testers filling forms, and people running a raffle or naming blog posts use them.
6 free tools · no sign-up · no ads
All Generators (6)
UUID Generator
Generate unique identifiers (UUIDs)Test Credit Card Generator
Generate test credit card numbers for developmentRandom Number Generator
Generate random numbers with custom rangesRandom Name Generator
Generate random names for people and placesRandom Email Generator
Generate random email addresses for testingURL Slug Generator
Generate URL-friendly slugs from text
Which tool do I need?
Create primary keys for seed data
Generate up to 1,000 UUIDs at once in version 4 or time-ordered version 7, and check the version of any existing UUID.
Fill a signup form with realistic fake people
Generate names from a regional pool and pair them with email addresses on domains reserved for testing.
Test card validation in a checkout form
Make Visa, Mastercard, Amex or Discover numbers with the right length, prefix, check digit and CVV length.
Pick a raffle winner or roll a number
Set the minimum and maximum, both included, and draw from the browser's cryptographic generator.
Make a clean URL from a blog post title
Strip accents and punctuation, choose a separator and length, and optionally drop stop words.
About Generators
For test data, use them together. Generate UUIDs as primary keys, names and emails for user rows, and card numbers to exercise the payment form's validation, and you have a seed set with nothing traceable to a real person. The slug generator is useful at the other end of a project, when content is published and needs stable, readable URLs. For identifiers beyond UUIDs, and for hashing the data you generate, look at Calculation Tools and Encoding Tools next door.
Know what each value is and is not. Test card numbers have real prefixes and check digits but are declined by real processors and most sandboxes; use your payment provider's published test cards for end-to-end tests. Emails use example.com, example.org and .test domains that cannot receive mail. Names are drawn independently from small pools, so large batches repeat. UUID versions 1 and 7 embed their creation time. The random number generator uses the browser's cryptographic source, which is fair enough for draws.
Guides
- UUID Generator Guide: Complete Overview of UUIDs and Unique IdentifiersMaster UUID generation with our comprehensive guide. Learn about UUID versions, use cases, and best practices for universally unique identifiers in software development.
- Random Numbers, Names and Emails for Test Data, Done ProperlyUnbiased random ranges, why Math.random is not for raffles, names that break forms in useful ways, and email domains that can never reach a real inbox.
- Test Credit Card Generator Guide: Complete Payment Testing for DevelopersMaster payment testing with our comprehensive guide to test credit card generation. Learn about Luhn algorithm, payment gateway testing, and best practices for secure payment integration testing.
- URL Slugs: How to Write Clean, Stable, Search-Friendly URLsWhat makes a good slug, why hyphens beat underscores, how to handle accents and stop words, and why changing a published slug costs more than you think.
Frequently asked questions
Why should test emails use example.com instead of made-up domains?
Because example.com, example.org, example.net and .test are reserved by RFC 2606 and RFC 6761 and can never deliver mail. An invented domain might be registered by someone, and your test messages would reach them.
Which UUID version should a new project use?
Version 4 if IDs are public and should reveal nothing, version 7 if you want database indexes to stay ordered by creation time. Both are defined in RFC 9562.
Will generated card numbers work in a Stripe or PayPal sandbox?
Usually not. Sandboxes accept only their own documented test numbers. Generated numbers are for checking your form's format and Luhn validation, not for completing a payment flow.
Is it acceptable to copy real customer data into a test environment?
Generally no. Real names, emails and card numbers in test systems bring privacy and PCI DSS obligations with them. Generated data gives the same shape without that exposure.