encoding
Encode text or uploaded files as Adobe Ascii85, or decode Ascii85 back to binary. It all runs in your browser, so your input stays on the device.
Encode text or uploaded files as Base32, or decode Base32 text and files back to binary. It all runs in your browser, so your input stays on the device.
Runs in your browser — your input is processed on this device and never uploaded.
Base32 represents bytes using 32 characters, and this tool uses the standard uppercase alphabet with padding, as defined in RFC 4648. Each complete group of 5 input bytes becomes 8 Base32 characters, so the encoded form is noticeably longer than the same data in Base64.
Choose Encode for typed text or an uploaded file. Choose Decode to recover the original bytes from valid Base32. Several inputs in one run are fine, and results arrive as files.
The alphabet is the whole point. Base32 drops the case distinction and the characters people most often confuse, so a string survives being read aloud, written on paper, typed by hand, or passed through a system that upper-cases everything.
That makes it the sensible pick for anything a person has to handle: shared secrets, recovery codes, identifiers in filenames or hostnames where case is not reliably preserved. For data that only ever moves between machines, the extra characters buy you nothing.
Base64 is the default for machine-to-machine transport and produces meaningfully shorter output. Hex is longer still than Base32 but maps one byte to exactly two characters, so it is easier to read positionally. Base58 also removes ambiguous characters and drops padding, which suits identifiers people copy around.
Anyone holding the text can recover the bytes. This is a transport format, not protection, and it is not hashing or compression either.
The counterintuitive part is the size: a smaller alphabet means each character carries fewer bits, so the encoded output is longer, not shorter. Base32 spends about 60 percent more characters than the original byte count, against Base64's 33 percent.
More encoding tools on ToolkitBay.
encoding
Encode text or uploaded files as Adobe Ascii85, or decode Ascii85 back to binary. It all runs in your browser, so your input stays on the device.
encoding
Encode text or uploaded files as Base64, or decode Base64 text and files back to binary. It all runs in your browser, so your input stays on the device.
encoding
Encode text or uploaded files as lowercase hexadecimal, or decode hex back to binary. It all runs in your browser, so your input stays on the device.
encoding
Encode bytes as whole-value Base62, or decode Base62 text back to bytes. Choose either supported digit and letter ordering.
Encode bytes with Bitcoin-alphabet Base58 or Base58Check, or decode them back. Supports optional Base58Check version-byte validation.
Find similar tools by category or tag.
Drag a file here, or click to upload.
Up to 5 files · 60 MB total
Upload is optional.