38 chars · 1 line
Needs attention
38 chars · 1 line
Needs attention
UUID wrappers
Some logs, GUID APIs, and configuration formats display identifiers inside curly braces. VetaTool's UUID validator expects the bare canonical UUID string, so the surrounding { and } make the input fail the format check. This tool is free to use. No account or payment is required.
Last updated
Brace-wrapped GUIDs are common in some ecosystems, but the validator's accepted form is the 36-character canonical UUID itself. The tool does not strip wrappers automatically.
The braces make an otherwise familiar UUID fail the canonical format check.
{550e8400-e29b-41d4-a716-446655440000}Invalid UUID formatCommon questions
No. They are wrapper syntax used by some representations; the canonical UUID text itself does not include braces.
No. The current validator expects the bare UUID string.
Debugging a specific UUID issue? Browse UUID troubleshooting.