UUID · GUID is a UUID
GUID vs UUID
Microsoft's GUID is a UUID with platform-specific formatting and byte order.
Key facts
| Relationship | GUID is a UUID |
|---|---|
| Text form | Often {xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx} |
| Braces | Presentation only |
| Byte order | Mixed-endian in some Windows APIs |
| Collision behavior | Same as the underlying version |
| Common confusion | Copying raw bytes between platforms |
Formatting differences
Windows tools often wrap GUIDs in braces and uppercase the hex. Neither changes the value. The real trap is binary interchange: some Microsoft APIs store the first three fields little-endian, so copying 16 raw bytes between a Windows structure and an RFC-compliant parser can produce a different UUID string.
Safe interchange
Exchange GUIDs as canonical text, not raw bytes, unless both sides document the byte order. When you must use binary, state the layout explicitly and test round-trips across platforms.
Frequently asked questions
Is a GUID always a valid UUID?
The 128 bits are a UUID. Formatting and byte order may differ, so parse it as text when in doubt.
Why does the same value look different in two tools?
One may show braces or uppercase, or one may be interpreting raw bytes with a different endianness.
Can I use braces in a URL?
They must be percent-encoded. Prefer the canonical hyphenated form without braces.