TFT

Binary UUID / GUID Generator

Generate UUIDs (GUIDs) and view their binary representation. This tool creates random 128-bit unique identifiers and shows them as binary strings. Useful for developers and database work.

Bulk Generation

About UUID/GUID

A UUID (Universally Unique Identifier) or GUID (Globally Unique Identifier) is a 128-bit number used to uniquely identify information. This tool generates UUID version 4, which uses random numbers.

Format: 8-4-4-4-12 hexadecimal digits (32 chars + 4 dashes = 36 chars total). Binary representation uses all 128 bits.

How It Works

This binary UUID/GUID generator creates random Universally Unique Identifiers and displays them in both standard hexadecimal format and binary representation. UUIDs are 128-bit values used to uniquely identify information across systems.

The generation process:

  1. Generate random bytes: 16 random bytes (128 bits) are generated using cryptographically secure random number generation.
  2. Set version bits: For version 4 (random) UUIDs, specific bits are set to indicate the version.
  3. Set variant bits: Certain bits identify the UUID variant (RFC 4122 standard).
  4. Format output: Display as standard hex UUID (with dashes) and as 128-bit binary string.

Standard format: 550e8400-e29b-41d4-a716-446655440000 (32 hex digits + 4 dashes). Binary format: 128 consecutive 0s and 1s showing the actual bit pattern.

When You'd Actually Use This

Database Primary Keys

Generate unique identifiers for database records that need to be unique across distributed systems.

Learning UUID Structure

Understand how UUIDs are constructed at the bit level by seeing both hex and binary representations.

Testing UUID Handling

Generate test UUIDs for development and testing of systems that use UUIDs for identification.

API Development

Create unique resource identifiers for REST APIs and microservices architectures.

Session and Token Generation

Generate unique session IDs, transaction IDs, or correlation IDs for distributed tracing.

File and Asset Naming

Create unique filenames for uploaded files, assets, or generated content to avoid collisions.

What to Know Before Using

UUIDs are 128 bits (16 bytes)

That's 32 hexadecimal digits or 128 binary digits. The dashes in standard format are just for readability.

Version 4 is random-based

Version 4 UUIDs use random numbers. Other versions use timestamps (v1), names (v3/v5), or other methods.

Collision probability is extremely low

You'd need to generate billions of UUIDs per second for years to have a reasonable chance of collision.

Binary representation shows structure

Version and variant bits are visible in binary. Version 4 has pattern 0000 in bits 48-51.

UUIDs aren't secure tokens

While random, UUIDs aren't designed as security tokens. Use proper cryptographic tokens for authentication.

Common Questions

What's the difference between UUID and GUID?

Technically the same thing (128-bit identifier). UUID is the open standard term. GUID is Microsoft's term. They're interchangeable.

How unique are version 4 UUIDs?

Extremely. With 122 random bits, there are 5.3×10^36 possible UUIDs. Collision probability is negligible for any practical use.

What do the version and variant bits mean?

Version (bits 48-51) indicates how UUID was generated (4=random). Variant (bits 64-67) indicates the UUID layout (RFC 4122 standard).

Can I use UUIDs as primary keys?

Yes! They're great for distributed systems where you need unique IDs without coordination. But they're larger and slower than integers.

Should UUIDs be stored as strings or binary?

Binary (16 bytes) is more efficient than string (36 bytes with dashes). But strings are more readable and portable.

Are UUIDs sequential?

Version 4 is random, not sequential. For sequential UUIDs, consider UUIDv7 or COMB GUIDs for better database performance.

Can I generate UUIDs offline?

Yes! Version 4 UUIDs need only a good random number generator. No network or central authority needed.