UUID Inspector & GUID Byte Order
Paste an identifier to inspect its bytes, common encodings and embedded timestamp. Everything runs in this browser.
Decoded identifier
Paste an identifier above to inspect it.
UUID byte order
UUID text and RFC/network bytes use the same left-to-right byte order. The traditional .NET Guid.ToByteArray() and SQL Server uniqueidentifier binary representation reverse the first 4-byte, 2-byte and 2-byte groups; the final 8 bytes stay in place. SQL Server comparison/sort order is a separate behavior and is not represented by this byte conversion.
Embedded timestamps
UUID versions 1, 6 and 7, ULIDs, MongoDB ObjectIds and Snowflake IDs contain or encode time. Their time portion is useful for inspection but can reveal creation time; do not treat these identifiers as secrets or authentication tokens.
Snowflake epochs
Twitter/X Snowflake IDs use the Twitter epoch; Discord IDs use the Discord epoch. Other Snowflake implementations may use different epochs or bit layouts and are not decoded by these presets.