Crockford Base32 Encoder / Decoder

Encode text or hex bytes to Crockford Base32, or decode it back. The alphabet avoids easily confused letters and is case-insensitive when decoding.

Use the tool

Why this tool exists

Douglas Crockford designed his Base32 to be read and typed by people. It leaves out I, L, O and U so that you do not confuse them with 1 and 0, and to avoid accidental rude words. Decoders treat O as zero and I or L as one, and ignore hyphens, so a value copied from a printout still decodes.

You will see it in ULIDs, which use the same alphabet for their 26-character form, and in some human-friendly identifiers. This tool lets you encode bytes or text, or decode a string to see what it holds. Note that it is the plain alphabet with no check symbol, and it is not RFC 4648 Base32.

How to use it

  1. Choose encode or decode, and whether the bytes are text or hex.
  2. Paste your input. Hyphens and spaces are ignored when decoding.
  3. Copy the result from the output box.

Frequently asked questions

How is it different from RFC 4648 Base32?

The alphabet and the order differ. Crockford uses 0 to 9 then A to Z without I, L, O and U, while RFC 4648 uses A to Z followed by 2 to 7. Strings are not interchangeable.

Is the output padded?

No. Padding characters are not used. The last group is filled with zero bits to reach five, so lengths follow directly from the byte count.

Does it support the check symbol?

No. Crockford describes an optional check character at the end of a value, but this tool encodes and decodes only the data itself, without any check symbol.

Is a ULID decoded correctly here?

The alphabet matches, but a ULID packs 128 bits into 26 characters with a leading padding, so use the ULID tool to read its timestamp and random part.