encoding
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.
Encode bytes as whole-value Base62, or decode Base62 text back to bytes. Choose either supported digit and letter ordering.
Runs in your browser — your input is processed on this device and never uploaded.
Enter text or upload a file to encode. To decode, enter the encoded text.
Results appear here.
Base62 writes bytes using only the digits and the upper- and lowercase letters, 62 characters in all. The output has no punctuation, so it drops into URLs, file names and identifiers without escaping. Unlike Base64 there is no standard, and implementations disagree on the alphabet order.
0-9 A-Z a-z (the default) or 0-9 a-z A-Z. Use the same ordering for encoding and decoding.Base64 needs two symbols beyond letters and digits, + and / in the standard alphabet. Both mean something in URLs and file paths, so Base64 values get escaped or switched to a URL-safe variant. Base62 avoids the question by using no symbols at all, which is why short-link services and ID generators often use it.
The cost is a little length. Each Base62 character carries just under 6 bits, against exactly 6 for Base64, so the output is slightly longer.
Base64 is standardized in RFC 4648 and handles large data well. Base58 also avoids symbols and drops look-alike characters too, at a small cost in length. Hex is longer still and needs no alphabet agreement at all.
Because the input is converted as one large number rather than in blocks, conversion gets slower as the input grows, which is why this tool stops at 1 MiB. For bigger payloads, Base64 is the practical choice.
Warning
Confirm the alphabet ordering the receiving system expects. Decoding with the other ordering does not fail; it returns different bytes. And like any encoding, Base62 hides nothing from anyone who decodes it.
Explore tools with similar capabilities.
encoding
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.
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.
Encode bytes with Bitcoin-alphabet Base58 or Base58Check, or decode them back. Supports optional Base58Check version-byte validation.
encoding
Encode bytes with a self-identifying multibase prefix, or detect the prefix and decode an existing multibase string.