❓ Frequently Asked Questions
Find quick answers to common questions about UUID Studio Pro
💬 General Questions
Only to open the page. Once it has loaded, generating and managing UUIDs happen in your browser and keep working if the connection drops; opening or reloading the page needs a connection.
In your browser's local storage on your computer. It never leaves your device.
Yes, but data doesn't sync between devices. Export from one device and import to another.
No, but the web app works great on mobile browsers with responsive design.
Limited by browser storage (usually 5-10MB). Approximately 10,000-50,000 UUIDs.
Yes! UUID v4 has a collision probability of ~1 in 5.3 trillion.
🔧 Technical Questions
They're the same thing. GUID is Microsoft's term for UUID. GUID is usually uppercase.
UUID v4 for most cases. UUID v7 for database primary keys. See "Choosing the Right UUID Type" in the help documentation.
Yes! UUIDs are a standard format. No licensing or restrictions.
Yes, they use cryptographically secure random number generation.
ULID is like UUID but more readable and sortable. Use for user-facing IDs or API keys.
A UUID is 128 bits written as 32 hexadecimal digits in five groups separated by hyphens, 8-4-4-4-12, for example 3f2b8c1e-9d4a-4b7e-a1c3-5e6f7a8b9c0d. The first digit of the third group is the version (4 in the example), and the first digit of the fourth group shows the variant, which is 8, 9, a or b for standard UUIDs. To check a value you were given, paste it into the tool's validator before you rely on it.
Either works, because the hexadecimal digits mean the same in both cases and systems are expected to accept both when reading a UUID. The current standard, RFC 9562, asks for lower case when a UUID is written out, and most databases and programming languages print it that way. Microsoft tools often show GUIDs in upper case inside braces, such as {3F2B8C1E-...}; that is the same value in a different format.
In theory yes, in practice no. A version 4 UUID has 122 random bits. You would need to generate about 2.7 billion billion of them before the chance of even one repeat reached 50 percent, far beyond any real system. Repeats seen in practice come from faulty random number generators or copied values, not from the format itself.
Version 7 starts with the creation time in milliseconds and fills the rest with random bits, so UUIDs made later sort after earlier ones. Databases store such keys more efficiently than fully random version 4 values, because new rows go to the end of an index instead of being scattered through it. Use v7 for database primary keys and event IDs, and v4 when the order of creation should not be visible.
A version 4 UUID is pure chance and reveals nothing. A version 7 UUID reveals when it was created, to the millisecond. A version 1 UUID contains its creation time and a node value that, in older software, was the computer's network card address; generators in browsers, this one included, use a random node value instead, but it is still best not to use v1 where the creation time should stay private.
The nil UUID is all zeros: 00000000-0000-0000-0000-000000000000. It is a defined special value meaning no UUID, used as a placeholder or default, never as a real identifier. The standard also defines a max UUID made entirely of f characters, used as an upper bound.
🔍 Troubleshooting
Browser data might have been cleared, or you're in a different browser/profile. Always export backups!
Enable auto-cleanup, set a history limit, or export old data and clear history. Charts are optimized to only re-render when data changes.
Yes, if you haven't closed the tab - use Undo (Ctrl+Z). Otherwise, no - they're permanently deleted.
Check that your JSON is properly formatted. The app validates JSON structure and field types. Use a JSON validator online if needed.
Refresh the page. If problem persists, check browser console for errors.