Free UUID Validator - Fast Browser Tool

Check UUID structure, version, variant, canonical form, embedded timestamps, and duplicates. Validate one value or a complete list privately inside your browser.

Validate UUID See how it works
UUID versions 1–8 NIL and MAX support Bulk validation No server requests

UUID Validator

Enter one UUID per line. The validator checks up to 100 non-empty values and normalizes every valid result.

Private browser processing
One value per line · Ctrl/⌘ + Enter to validate
Flexible input mode Accept URN, braces, and compact 32-hex values
0 of 100 values

01
Private by design Values stay inside your browser
02
RFC-aware details Version and variant inspection
03
Bulk validation Check up to 100 values
04
Clean exports Copy normalized values or CSV
Developer-friendly inspection

Validate UUID structure without uploading data

A UUID is commonly represented as 32 hexadecimal characters divided into five groups: 8-4-4-4-12. This validator confirms that structure and then inspects the version and variant fields.

Flexible mode can also accept compact hexadecimal values, braced UUIDs, and the urn:uuid: prefix. Every valid value is returned in lowercase canonical form so it can be copied into code, logs, fixtures, APIs, or databases.

For UUID versions 1, 6, and 7, the tool also attempts to decode the embedded timestamp. That timestamp reflects encoded UUID data and does not prove when a database record was created.

Structural validity is not record verification

A structurally valid UUID may still be fabricated, duplicated, incorrectly generated, or absent from your system. Confirm ownership and existence through your own trusted application or database.

Complete validation workflow

More than a basic UUID regex check

Inspect format, metadata, duplicates, and normalized values through a responsive browser-only workflow.

01

Single and bulk validation

Check one UUID or paste up to 100 values with one UUID on each line.

02

Version recognition

Identify RFC-variant UUID versions 1 through 8 and explain their general purpose.

03

Variant inspection

Distinguish NCS, RFC, Microsoft, and future-reserved variant bit patterns.

04

Flexible normalization

Convert supported compact, URN, braced, or uppercase input into canonical lowercase text.

05

Timestamp extraction

Decode representable embedded timestamps from UUID versions 1, 6, and 7.

06

Copy and CSV export

Copy valid normalized UUIDs or download detailed bulk results as a CSV file.

Three simple steps

How to validate a UUID online

No installation, registration, server request, or file upload is required.

1
Step 1

Enter UUID values

Paste one UUID per line or load the built-in examples to explore supported formats.

2
Step 2

Run validation

Check structure, normalized form, special values, version, variant, timestamp, and duplicates.

3
Step 3

Copy or export

Copy an individual normalized UUID, copy every valid value, print results, or download CSV.

Version reference

UUID versions 1 through 8

The version nibble describes the UUID layout when the value uses the RFC variant.

Version 1

Gregorian time based

Contains a timestamp, clock sequence, and node field.

Version 2

DCE security

A legacy DCE Security UUID layout with local-domain data.

Version 3

MD5 name based

Deterministically generated from a namespace and name using MD5.

Version 4

Random or pseudorandom

The widely used layout built primarily from random bits.

Version 5

SHA-1 name based

Deterministically generated from a namespace and name using SHA-1.

Version 6

Reordered time based

Reorders Gregorian timestamp fields for improved database sorting.

Version 7

Unix time based

Begins with a Unix timestamp in milliseconds and sorts chronologically.

Version 8

Custom application data

Provides an RFC-compatible layout for application-defined usage.

Implementation guidance

UUID validation best practices

Combine structural checks with application-level authorization, existence checks, and database constraints.

1

Normalize before comparison

Convert accepted text forms into canonical lowercase UUIDs before deduplication or comparison.

2

Use native UUID database types

Prefer native UUID columns where available instead of storing identifiers as arbitrary text.

3

Do not treat UUIDs as authorization

An unguessable-looking identifier does not replace access control or ownership checks.

4

Validate at system boundaries

Reject malformed path, query, form, and API parameters before database operations.

5

Choose versions intentionally

Use a version appropriate for random identifiers, deterministic names, or time ordering.

6

Avoid timestamp assumptions

An embedded timestamp can be fabricated and does not prove record creation time or authenticity.

Common questions

UUID validator FAQ

What is a valid UUID format?

The canonical UUID text format contains 32 hexadecimal characters divided into groups of 8, 4, 4, 4, and 12 characters by hyphens. An example is 550e8400-e29b-41d4-a716-446655440000.

Which UUID versions can this validator recognize?

The validator recognizes UUID versions 1 through 8 when the UUID uses the RFC variant. It also identifies the special NIL and MAX UUID values.

Can I validate multiple UUIDs at once?

Yes. Enter one UUID per line to validate up to 100 non-empty values. The results include valid and invalid counts, normalized values, versions, variants, formats, and duplicate detection.

Are UUID values uploaded or stored?

No. Validation happens locally in your browser. This template does not upload, save, log, or place entered UUID values in local storage.

What does flexible input mode accept?

Flexible mode accepts canonical UUIDs, 32-character hexadecimal UUIDs without hyphens, UUIDs surrounded by braces, and values beginning with the urn:uuid: prefix. Valid values are normalized to lowercase canonical form.

Can a UUID contain a timestamp?

UUID versions 1 and 6 contain a Gregorian timestamp, while UUID version 7 begins with a Unix timestamp in milliseconds. The validator displays that embedded value when it can be represented as a valid date.

Does a valid UUID prove that an identifier exists?

No. Format validation only confirms that a value has a structurally valid UUID representation. It does not prove that the identifier was generated correctly, is unique, exists in a database, or belongs to a trusted record.

Continue developing

Related developer tools

Generate identifiers, inspect structured data, or create cryptographic hashes in your browser.

Identifier utility

UUID Generator

Generate standards-aware UUID values for development, testing, fixtures, and applications.

 Data utility

JSON Formatter

Format, validate, inspect, and minify JSON data through a clean browser-based interface.

 Cryptographic utility

Hash Generator

Create cryptographic hashes for text or files using modern browser-supported algorithms.

Ready to inspect your UUIDs?

Validate structure, version, variant, timestamps, duplicates, and canonical formatting without sending identifiers to a server.

Validate UUIDs Now