Developer Utility

UUID Generator

Generate random unique identifiers in UUID v4 format, customize case, hyphen usage, and output format, then copy or download the result as a TXT file.

Generate UUID v4 Quickly generate random UUID v4 values in your browser.

Choose Output Format Organize results as line-separated values, comma-separated values, or a JSON array.

Copy and Download Copy the generated UUID list at once or save it as a TXT file.

Version v4

Count 5

Format Hyphen

Output Line

UUID Generation Settings

Choose the number of UUIDs, letter case, hyphen option, and output format to create a UUID list.

Count

You can generate between 1 and 100 UUIDs at once.

Letter Case

Choose the letter case format for the UUID string.

Hyphen

With hyphens, UUIDs are 36 characters. Without hyphens, they are 32 characters.

Output Format

Choose the output format that fits where you plan to paste the result.

Prefix

Optionally enter a prefix to add before each UUID.

Suffix

Optionally enter a suffix to add after each UUID.

Recommended Presets

Common UUID output combinations for test data, database keys, and API request IDs.

Generated Result

Review the generated UUID list and copy it or download it as a TXT file.

Ready

Click the Generate UUIDs button.

Help

When should I use UUIDs?

UUIDs can be used as low-collision unique identifiers for database primary keys, filenames, API request IDs, temporary data identifiers, and test data generation.

UUID v4 Format

A typical UUID v4 follows the xxxxxxxx-xxxx-4xxx-yxxx-xxxxxxxxxxxx format and is generated from random values. It is 36 characters with hyphens and 32 characters without hyphens.

When should I remove hyphens?

The no-hyphen format can be useful for URL parameters, filenames, or short token-like strings where separators are unnecessary. Use the hyphenated format when a standard UUID display format is required.

Can UUIDs be used as security tokens?

UUIDs are useful as identifiers, but for login session keys, long-term authentication tokens, or other security-sensitive values, it is better to use cryptographically secure random generation on the server side.