JSONPath Tester
Run JSONPath expressions against a document and see every match live.
Identify a UUID's version and variant, and extract its timestamp.
The UUID Decoder reads a UUID’s version and variant bits, explains what each means, and extracts the creation timestamp from the versions that carry one — including version 1’s unusual 1582 epoch.
Every UUID carries its own version and variant in fixed bit positions, so a single identifier can tell you how it was made. This reads them and explains what each answer means, rather than just printing a number.
For the time-based versions it goes further and extracts the timestamp: version 1 and 6 count 100-nanosecond intervals since 1582, which is a genuinely strange epoch, and version 7 counts milliseconds since 1970. Either way you get a readable date. It also recognises the nil and max UUIDs, normalises whatever form you paste — braces, a urn: prefix, no hyphens, mixed case — and gives you back the canonical form.
Not just a number but what it implies — whether the id is random, hashed or time-based, and what that means for sorting and privacy.
Versions 1 and 6 count 100-nanosecond intervals since 1582 and version 7 counts milliseconds since 1970; both become a readable date.
Braces, a urn:uuid: prefix, missing hyphens and mixed case are all accepted and normalised.
The all-zero and all-F UUIDs are identified as the defined special values rather than as malformed input.
The variant bits distinguish an RFC 4122 UUID from the legacy NCS and Microsoft layouts, which changes how the rest is read.
With or without hyphens, braces or a urn:uuid: prefix.
Which of the eight versions it is, and what that means in practice.
Versions 1, 6 and 7 carry a creation time, which is extracted and shown as a date.
Copy the normalised UUID, or the urn: form if you need it.
The first character of the third group. In 550e8400-e29b-41d4-a716-446655440000 that is the "4", so it is a version 4 UUID. The tool reads it and explains what the version implies.
Versions 1, 6 and 7. Version 4 is entirely random, and versions 3 and 5 are hashes, so none of those can tell you when they were made.
Because that is when the Gregorian calendar was adopted. The count is in 100-nanosecond intervals since 15 October 1582, which is an odd choice and part of why v7 exists.
All zeros — a defined value meaning "no UUID", used as a placeholder. The max UUID, all Fs, was standardised alongside v7 as its counterpart.
What people who use the UUID Decoder think of it. Reviews come from visitors and are posted as written.
No ratings yet
Yours would be the first.
0 reviews
Newest first
No reviews yet
Be the first to rate the UUID Decoder. It takes half a minute and no account.
Write the first reviewRun JSONPath expressions against a document and see every match live.
Generate TypeScript interfaces from a sample JSON payload.
Stack CSS filters on a real image and copy the declaration.
Build media queries with framework breakpoints and modern features.
Compute a CRC-32 checksum in hex, decimal and signed form.
Build a docker-compose.yml with databases, caches and health checks.
Turn a JSON object into a TOML document with proper tables and arrays of tables.
Convert Base64 back to hexadecimal, with your choice of separator.