UUID to Base62 (Short ID) Converter

Standard UUIDs are 36 chars. Base62 encoding (digits + lowercase + uppercase = 62 chars) packs the same 128 bits into 22 characters — handy for shorter URLs, more compact database keys, or paste-friendly identifiers. This tool converts both ways.

How to use the UUID to Base62 (Short ID) Converter

Pick a direction. UUID → Base62 takes any standard 36-character UUID and outputs a 22-character base62 string. Base62 → UUID reverses it, turning the short ID back into the canonical hyphenated UUID. The conversion is exact and lossless in both directions.

Packing 128 bits into 22 characters

A UUID is 128 bits of identifier, normally written as 32 hexadecimal digits with four hyphens — 36 characters in all. Hex is wasteful because it uses only 16 symbols per character. Base62 uses all the digits plus lower- and upper-case letters, 62 symbols, so the same 128 bits fit into 22 characters with nothing lost. The conversion simply reads the UUID as one big number and re-expresses it in base 62.

The payoff is shorter identifiers that are still URL-safe and easy to paste — the same idea behind Bitly-style short links and compact database keys. Because it is a pure change of base, it is fully reversible: every UUID maps to exactly one base62 string and back again, with no collisions and no loss of information.

Common use cases

  • Shorter URLs — expose a 22-character ID in a link instead of a 36-character UUID.
  • Compact keys — store identifiers in fewer bytes while keeping the full 128-bit value.
  • Readable references — give users a shorter code to quote in support tickets or invoices.
  • Decoding short IDs — turn a base62 identifier from a URL back into the UUID your database stores.
  • API design — offer tidy public IDs without changing the UUIDs used internally.

Frequently asked questions

Is the conversion lossless?
Yes. Base62 is just a different way of writing the same 128-bit number, so every UUID maps to exactly one base62 string and converting back returns the original UUID precisely.

Why 22 characters?
62 to the 22nd power is the smallest power of 62 that exceeds 2 to the 128th, so 22 base62 characters are exactly enough to hold any 128-bit UUID. Some values encode shorter and are left-padded to keep the length uniform.

Is base62 URL-safe?
Yes. It uses only A–Z, a–z, and 0–9 — none of the punctuation or padding base64 uses, so it needs no escaping in URLs, filenames, or hostnames.

How is this different from base64?
Base64 uses 64 symbols including two punctuation characters and often padding, which can need escaping. Base62 drops those for an alphanumeric-only string — slightly longer, but safe to drop straight into a URL.
Embed this tool on your site

Free to embed, no attribution required (but appreciated). Paste this where you want the tool to appear: