Paste a GUID value and check whether it is valid. The tool normalizes common formats for copying.
Identifier validator
Enter a value to see the result automatically.
Guide
Validate GUID values online, accept common brace and compact formats, and copy a normalized lowercase GUID.
GUID values are widely used in Microsoft ecosystems, databases, APIs, logs, and configuration files. They are closely related to UUID values and often appear with braces, parentheses, hyphens, or compact formatting. This validator checks common GUID formats and returns a normalized value.
The tool accepts a GUID with braces, a regular hyphenated GUID, or a compact 32-character value when it follows the expected version and variant pattern. The normalized output is lowercase and hyphenated, which makes it easier to compare, log, and copy into code.
GUID validation is helpful when a value has been copied from a spreadsheet, error log, URL, registry entry, or database export. A missing digit, invalid character, or misplaced separator can be hard to spot visually. This page gives a direct pass or fail result and shows the cleaned output.
Use this tool for everyday validation and formatting. It does not check whether the GUID exists in a database or belongs to a real object. It only checks the structure and normalizes the value.
Quick reference
{550e8400-e29b-41d4-a716-446655440000}
550e8400-e29b-41d4-a716-446655440000
Validation confirms structure, version, and variant patterns. It does not prove that an object exists in a database.
Lowercase hyphenated output makes values easier to compare across logs, APIs, spreadsheets, and tickets.
Most failures come from missing characters, hidden whitespace, invalid hex letters, or mixed-up separators.
In-depth guide
GUID and UUID strings often describe the same 128-bit identifier but arrive in different display forms. Normalization makes copied values easier to compare across .NET, SQL, APIs, and logs.
Values wrapped in braces or parentheses can be valid GUID text. The wrapper is removed from the normalized result.
A 32-character hexadecimal string can be normalized into the familiar 8-4-4-4-12 grouped format.
Uppercase and lowercase hexadecimal letters represent the same identifier. The output uses lowercase for consistent comparison.
A structurally correct GUID is not evidence that a row, user, or object exists in a particular system.
Common mistakes
In many practical workflows the terms are used interchangeably, although GUID is common in Microsoft contexts.
Yes. Values such as {550e8400-e29b-41d4-a716-446655440000} are accepted.
No. It validates the format only.
They commonly use the same 128-bit textual structure. GUID is terminology often used in Microsoft systems, while UUID is the standards-oriented term.
Yes. Hexadecimal GUID text is case-insensitive. This tool returns lowercase output for consistency.