UUID Case Converter & Hyphen Formatter
Standardize your UUIDs' format. Convert between uppercase and lowercase, and add or remove hyphens to match your system's requirements. Accepts UUIDs with or without braces.
Accepts UUIDs with or without hyphens, braces, any case
UUID Format Standards
UUIDs can be represented in multiple formats. The standard RFC 4122 format uses lowercase hexadecimal with hyphens: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
- Standard: Lowercase with hyphens (RFC 4122)
- Uppercase: Often used in Windows/GUID contexts
- No hyphens: Used in compact storage or URLs
- With braces: Microsoft GUID format: {xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}
How the UUID Case Formatter Works
This tool normalizes UUID formatting by applying consistent case (uppercase or lowercase) and hyphenation (with hyphens, without hyphens, or with curly braces). It strips all existing formatting first, then reapplies your chosen style.
The formatter accepts UUIDs in any input format—mixed case, missing hyphens, extra spaces, or curly braces—and produces clean, standardized output. All transformations happen locally in your browser.
Available output formats:
Standard (lowercase + hyphens)
550e8400-e29b-41d4-a716-446655440000Uppercase + Hyphens
550E8400-E29B-41D4-A716-446655440000No Hyphens
550e8400e29b41d4a716446655440000GUID (with braces)
{550E8400-E29B-41D4-A716-446655440000}Real Use Cases
Standardizing config files
A DevOps engineer consolidates configuration from multiple sources where UUIDs appear in different formats and needs them all consistent.
Windows Registry editing
Someone needs to paste a UUID into the Windows Registry in the specific format with curly braces that regedit expects.
URL parameter preparation
A developer removes hyphens from UUIDs to make them more compact for URL query parameters where every character counts.
Database storage optimization
Converting UUIDs to hyphen-free format before storing as BINARY(16) instead of CHAR(36) to save space.
Code generation
Generating C# code where GUID attributes require uppercase with braces: [Guid("...")]
Log normalization
A data pipeline ingests logs with UUIDs in inconsistent formats and needs them standardized before indexing in Elasticsearch.
What to Know Before Using
Input flexibility: Paste UUIDs with any combination of uppercase/lowercase, with or without hyphens, with or without braces. The tool strips everything and reapplies your chosen format.
Validation: The formatter validates that your input contains exactly 32 hexadecimal characters. If validation fails, you'll see an error instead of malformed output.
Format doesn't change value: 550e8400..., 550E8400..., and {550E8400...} are all the same UUID. Formatting is purely for human readability and system compatibility.
Character count: The output shows the character length so you can verify it matches your storage requirements (36 with hyphens, 32 without, 38 with braces).
FAQ
Does changing the case affect the UUID value?
No. UUIDs are case-insensitive by specification. 550e8400 and 550E8400 represent the exact same 128-bit value. Case is purely a formatting convention.
When should I use uppercase vs. lowercase?
Lowercase is the RFC 4122 standard and common in Unix/Linux environments. Uppercase is traditional in Microsoft/GUID contexts. For new projects, lowercase is generally preferred unless you have specific compatibility requirements.
What happens if I remove the hyphens?
The UUID remains valid—hyphens are just visual separators. Many databases store UUIDs as 16-byte binary values (no hyphens). Just be aware that some APIs or libraries expect the hyphenated format.
When do I need curly braces?
Curly braces are primarily used in Windows contexts: Registry entries, COM/DCOM interfaces, and some .NET attributes. Most modern APIs don't require them. Include braces when working with Windows-specific technologies.
Can I convert multiple UUIDs at once?
This tool processes one UUID at a time. For batch conversion of many UUIDs, use the UUID Sort & Organize tool, which includes formatting options along with sorting and deduplication.
Why does my formatted UUID look different?
If only the case or presence of hyphens/braces changed, that's expected. If the actual hex digits changed, your input may have been invalid. The formatter preserves all 32 hexadecimal characters exactly.
Other Free Tools
UUID Generator
Free UUID Generator
UUID Decoder
UUID Decoder & Analyzer
UUID Validator
UUID Validator & Checker
UUID Version Converter
UUID Version Converter (v3, v5)
Bulk UUID Generator
Bulk UUID Generator for Mass Production
ASCII to Hex Converter
ASCII to Hex Converter: Text to Hexadecimal Translator
Barcode Generator
Free Barcode Generator
Binary to Text Converter
Binary to Text Converter
Free Printable Calendar Maker
Create & Print Your Custom Calendar
Pie Chart Maker
Free Pie Chart Maker Online