UUID Parser and Validator
Validate and inspect UUID versions 1, 3, 4, 5, 6, 7, and 8, including variant, version, timestamp where defined, and byte-level fields.
1. Input UUIDs
Paste one or more UUIDs, one per line.
2. Parsed results
Showing 7 of 7 results
4. Summary
3. UUID details
Selected:
550e8400-e29b-41d4-a716-446655440000UUID breakdown
4 bytestime_mid
2 bytestime_low
and_version
2 bytesclock_seq
and_reserved
2 bytesnode
6 bytes
Binary (Hex)
55 0e 84 00 e2 9b 41 d4 a7 16 44 66 55 44 00 00Binary
01010101 00001110 10000100 0000000011100010 10011011 01000001 1101010010100111 00010110 01000100 0110011001010101 01000100 00000000 000000005. Export / code
[
{
"uuid": "550e8400-e29b-41d4-a716-446655440000",
"version": 4,
"variant": "RFC 9562 (formerly RFC 4122)",
"valid": true
},
{
"uuid": "6ba7b814-9dad-11d1-80b4-00c04fd430c8",
"version": 1,
"variant": "RFC 9562 (formerly RFC 4122)",
"valid": true,
"timestamp": "1998-02-04 22:13:53.151Z",
"unixMs": 886630433151
},
{
"uuid": "12d3c0f3-9c9d-11ee-be56-0242ac120002",
"version": 1,
"variant": "RFC 9562 (formerly RFC 4122)",
"valid": true,
"timestamp": "2023-12-17 05:28:13.472Z",
"unixMs": 1702790893472
},
{
"uuid": "01890f2d-3c80-7b11-b3e0-6b8f84b3a2d0",
"version": 7,
"variant": "RFC 9562 (formerly RFC 4122)",
"valid": true,
"timestamp": "2023-07-01 01:59:30.176Z",
"unixMs": 1688176770176
},
{
"uuid": "4f7e5b6c-9a1d-5c4b-8b6a-9b1c2e3d4f5a",
"version": 5,
"variant": "RFC 9562 (formerly RFC 4122)",
"valid": true
},
{
"uuid": "0190b9d0-d5cc-7f7e-b2e4-0c1d2e3f4a5b",
"version": 7,
"variant": "RFC 9562 (formerly RFC 4122)",
"valid": true,
"timestamp": "2024-07-16 04:33:09.580Z",
"unixMs": 1721104389580
},
{
"uuid": "3d813cbb-47fb-32ba-91df-831e1593ac29",
"version": 3,
"variant": "RFC 9562 (formerly RFC 4122)",
"valid": true
}
]What is UUID Parser and Validator?
Validate and inspect UUID versions 1, 3, 4, 5, 6, 7, and 8, including variant, version, timestamp where defined, and byte-level fields. One or many UUID strings in supported textual formats. Validity, version, variant, timestamp where applicable, byte breakdown, and bulk summary.
Open the tool
What the tool does
- Input: One or many UUID strings in supported textual formats.
- Controls and processing: Single/bulk parsing, normalized display, version/variant interpretation, timestamp conversion, byte fields, and summary counts.
- Output: Validity, version, variant, timestamp where applicable, byte breakdown, and bulk summary.
How to use it
- Provide the input. One or many UUID strings in supported textual formats.
- Review the settings. Single/bulk parsing, normalized display, version/variant interpretation, timestamp conversion, byte fields, and summary counts.
- Generate, inspect, and export. Validity, version, variant, timestamp where applicable, byte breakdown, and bulk summary.
Key features
- Input: One or many UUID strings in supported textual formats.
- Controls and processing: Single/bulk parsing, normalized display, version/variant interpretation, timestamp conversion, byte fields, and summary counts.
- Output: Validity, version, variant, timestamp where applicable, byte breakdown, and bulk summary.
Useful workflows
- Validate and inspect UUID versions 1, 3, 4, 5, 6, 7, and 8, including variant, version, timestamp where defined, and byte-level fields.
- Use it when you need this deliverable or diagnostic result: Validity, version, variant, timestamp where applicable, byte breakdown, and bulk summary.
- Place it before the next verified workflow step: validating the UUID with the target language library and application schema.
Limits and safety notes
- RFC 9562 is the current UUID specification and obsoletes RFC 4122; versions 6, 7, and 8 must not be described as RFC 4122 versions. Timestamp and field meanings differ by version, and the current byte-label mapping needs conformance tests against RFC 9562.
Troubleshooting
- Paste only the raw value or message expected by the tool; preserve quotes, delimiters, escaping, and line endings, then test a minimal valid sample.
- If parsing succeeds but the meaning is wrong, compare the output with the target standard or runtime; successful parsing is not proof of operational validity.
- RFC 9562 is the current UUID specification and obsoletes RFC 4122; versions 6, 7, and 8 must not be described as RFC 4122 versions. Timestamp and field meanings differ by version, and the current byte-label mapping needs conformance tests against RFC 9562.
Frequently asked questions
What is UUID Parser and Validator?
Validate and inspect UUID versions 1, 3, 4, 5, 6, 7, and 8, including variant, version, timestamp where defined, and byte-level fields.
How do I use UUID Parser and Validator?
Provide the expected input, review the page settings, then verify the result before copying or downloading it. Expected output: Validity, version, variant, timestamp where applicable, byte breakdown, and bulk summary.
What input does it accept?
One or many UUID strings in supported textual formats.
What output does it produce?
Validity, version, variant, timestamp where applicable, byte breakdown, and bulk summary.
What are the limits?
RFC 9562 is the current UUID specification and obsoletes RFC 4122; versions 6, 7, and 8 must not be described as RFC 4122 versions. Timestamp and field meanings differ by version, and the current byte-label mapping needs conformance tests against RFC 9562.
Related AppKiro tools
Start with a verified input
Test with a small, non-sensitive sample, verify the key settings and output, then apply the result to the real workflow.
Open the tool