Learn
History for this tool
The most recent data you entered in this tool, stored only in this browser.
Save what you type here, in this browser? Your work would go into this browser's local storage, so a refresh or a trip to another tool does not wipe it. You also get a short list of previous entries under the form, each one restorable with a click. Nothing is ever uploaded, and there is no account.
Being straight about the trade-off: anything kept there can be read by anyone who can use this browser profile, and by any script that later runs on this site. A tool page can hold a private key, a password or a signed token. Saving is convenient; it is not private.
Saved on this device
Your inputs and history are stored locally.
Not saved
This page forgets your work when you leave it.
About this tool
ULIDs are 128-bit identifiers like UUIDs, except the first 48 bits are a millisecond timestamp. That makes them sortable by creation time while staying unique, which is handy as a primary key when you want insertion order without keeping a separate timestamp column.Questions
- Should I use a ULID or a UUID?
- A ULID carries its creation time in its first characters and can sort roughly by time. A random UUID v4 does not expose that timestamp. Choose the format your application accepts; neither one replaces access control.
- Are ULIDs case-sensitive?
- The canonical form is uppercase Crockford Base32, and that is what this tool produces.