CORS Header Generator
Generate correct CORS headers, and understand why the request was blocked.
Encode and decode Base32, including the Crockford and hex variants.
The Base32 Encoder & Decoder converts between text and Base32 using four alphabets — RFC 4648, base32hex, Crockford and z-base-32 — with text UTF-8 encoded first so accents and emoji round-trip exactly.
Base32 encodes binary data using 32 characters, five bits at a time, so every five bytes become eight characters. It is less compact than Base64 but far more robust in the places it is used: TOTP secrets, DNS records, filenames and anything a human has to type or read aloud.
Four alphabets are supported. RFC 4648 is the standard one, using A–Z and 2–7. The hex variant sorts in the same order as the underlying data, which matters in a database key. Crockford leaves out I, L, O and U, and treats O as zero and I and L as one when decoding, so a value read over the phone still works. z-base-32 reorders the alphabet to put the easiest characters first. Text is UTF-8 encoded before encoding, so accented letters and emoji round-trip exactly.
RFC 4648 for standards work, base32hex when sort order must match the data, Crockford for values people read aloud, and z-base-32.
Decoding maps O to zero and I and L to one, so a value mistyped from a handwritten note still decodes correctly.
Text is UTF-8 encoded before encoding, so accented letters and emoji survive the round trip instead of being mangled.
Emit or omit the trailing equals signs, and decode strings that arrive either way.
A character that is not in the chosen alphabet is reported as itself, rather than producing silent garbage.
Encode plain text to Base32, or decode a Base32 string back.
RFC 4648 unless you know you need base32hex, Crockford or z-base-32.
The conversion runs as you type, with any invalid character named.
Take the output to your clipboard with one click.
Because it survives contact with humans and case-insensitive systems. Base32 uses no lowercase letters and no punctuation, so it works in a DNS label, a filename, and when read aloud — which is why TOTP secrets use it.
It carries five bits per character instead of six. Base32 output is about 160 per cent of the input size, Base64 about 133 per cent. You trade size for robustness.
It removes I, L, O and U — the first three because they look like 1 and 0, and U to avoid accidental profanity. When decoding it maps O to zero and I and L to one, so a mistyped value still works.
No. It is a reversible encoding with no key, exactly like Base64. Anyone holding the string can decode it.
What people who use the Base32 Encoder & Decoder think of it. Reviews come from visitors and are posted as written.
No ratings yet
Yours would be the first.
0 reviews
Newest first
No reviews yet
Be the first to rate the Base32 Encoder & Decoder. It takes half a minute and no account.
Write the first reviewGenerate correct CORS headers, and understand why the request was blocked.
Build and edit URL query strings without breaking the encoding.
Generate a production Dockerfile with multi-stage builds and layer caching.
Convert between signed and unsigned, with the negation steps shown.
Read a cron expression in plain English and see when it next runs.
Generate an MD5 hash of any text, with a straight answer about when not to.
Identify a UUID's version and variant, and extract its timestamp.
Generate HMAC signatures with SHA-1, SHA-256, SHA-384 or SHA-512.