UUID v4 Generator for Test Data, JSON, CSV, Mock IDs
Use this UUID v4 generator when test data, mock API records, seed rows, fixtures, or prototypes need standard random identifiers without opening a development console or writing a throwaway script.
Developers, QA testers, product builders, and students who need quick identifiers for local work.
A test record, mock response, or prototype often needs realistic IDs before the real system is wired up.
One or more copyable UUID v4 values that can be pasted into fixtures, database seed rows, sample JSON, CSV, URNs, docs, or notes.
Use when
What to include
Steps
Try this
Generate one UUID for a mock customer record.
Useful when a fixture needs one realistic identifier.
Generate five UUIDs for seed data in a local database.
Good for filling a few rows without writing a helper script.
Create three UUIDs I can use in an API response example.
Keeps docs examples realistic without leaking real identifiers.
Good output
- The output is copyable without explanation around it.
- Multiple values are separated clearly as lines, JSON, or CSV when requested.
- Each UUID follows the standard 8-4-4-4-12 hexadecimal format.
- Standard output uses UUID version 4 values.
- URN output starts with urn:uuid: and keeps the UUID body intact.
- Generated identifiers are used as sample IDs, not credentials.
- The page does not imply these values are already stored, reserved, or secure secrets.
Avoid
Limits
FAQ
Which UUID version does this generator create?
It creates standard UUID v4 values. Use them for test data, fixtures, examples, and local prototypes rather than credentials or secrets.
Can I generate more than one UUID?
Yes. Choose one, three, five, or ten UUIDs during confirmation, or ask for a short list in the input.
Can it output JSON, CSV, uppercase, or no-hyphen UUIDs?
Yes. Choose the output format that fits your fixture, docs, or local test workflow.
Can it output UUID URNs?
Yes. Choose URN output when you need values that start with urn:uuid: for namespace or documentation examples.
Are these UUIDs safe for production secrets?
No. Use them as identifiers or sample data, not as passwords, API keys, or access tokens.
Can I use the UUIDs in mock API data?
Yes. They work well for fixtures, sample JSON, documentation examples, and local prototype records.
Does this reserve a UUID in my system?
No. It only creates text identifiers; your application or database still controls whether an ID is stored or accepted.