Base64 / Base58 / Base32 Encoder
Encode and decode text and files using Base64, Base64URL, Base58, Base32, Base32hex, Base62, Base45, Ascii85 or Hex directly in your browser.
You can switch between encoding modes with tabs and instantly view the results.
This tool supports UTF-8 text, including line breaks and non-ASCII characters, making it suitable for handling multilingual content and structured data.
Encoded results can be copied with a single click for use in APIs, filenames, URL-safe payloads, or configuration values.
All processing is performed locally in your browser.
No input data is sent to any server, ensuring a fast and secure encoding experience
for development, testing, and debugging tasks.
UTF-8 friendly. Base64 output works well for filenames or URL-safe payloads.
Hex dump and byte arrays
Turns the text above (as UTF-8 bytes) into a hex dump or a ready-to-paste byte array, and reads a dump from xxd, hexdump -C or plain hex back into bytes.
GuideHow to use & features
- Paste the text you want to convert, then hit the Encode/Decode buttons in each tab to get results.
- Toggle URL Safe or remove line breaks for Base64 and reuse the same input for Base32 or Base58.
- Use the copy buttons to move any output elsewhere; large payloads may need a moment to finish.
- All processing stays in the browser—your input is never sent to a server.
SamplesSample input & output
Base64 encode text
Hello, DevToolKits! (UTF-8)
SGVsbG8sIERldlRvb2xLaXRzISAoVVRGLTgp
FAQFAQ
Which formats are supported?
Base64, Base32 and Base58. Enter text and choose encode (convert) or decode (turn back).Can it handle Japanese text?
Yes. Text is converted as UTF-8 bytes, so Japanese and emoji come back correctly on decode.Is Base64 encryption?
No. Base64 is an encoding that represents bytes using only text characters, and anyone can reverse it. It cannot protect secrets.Can it decode Base64URL (with `-` and `_`) as used in JWTs?
No. The Base64 here is the standard form with `+` and `/`. A string containing `-` or `_` gives an error. Use the JWT tool to inspect a JWT.What are Base32 and Base58?
Base32 uses the RFC 4648 characters (`A-Z` and `2-7`) with no trailing `=`; it appears in two-factor authentication secrets. Base58 uses the Bitcoin alphabet (without `0`, `O`, `I` and `l`) and has no checksum.Can it convert images or files?
No. Input is text only. Everything is processed in your browser and nothing is sent.
Use casesCommon use cases
Checking Basic auth and API header contents
Decode an `Authorization: Basic ...` value to confirm it has the `username:password` form.Reading Base64 values in Kubernetes Secrets and environment variables
Quickly turn values stored as Base64, as in `kubectl get secret` output, back into text.Checking a two-factor authentication (TOTP) secret
Decode a Base32 secret to check its contents, or create Base32 from text.Trying Base58 IDs and short notations
Convert Bitcoin-style identifiers and short IDs that avoid confusing characters, and see the result.
NotesNotes & limitations
It is not encryption
Base64, Base32 and Base58 are encodings anyone can reverse. Do not use them to "hide" passwords or similar.Read JWT-style Base64URL in Base64URL mode
Formats using `-` and `_`, such as the header and payload of a JWT, can be encoded and decoded in Base64URL mode (no = padding is added). Base64 mode also reads both forms. Signatures are not verified.Decoded output is shown as UTF-8 text
If the source is binary, such as an image or compressed data, you get garbled characters. It is not meant for binary data.Base58 has no checksum
Base58Check (such as Bitcoin addresses) is not verified. Long inputs can also take a while to convert.
AboutAbout this tool
Base64, Base58, and Base32 Encoder/Decoder
Base encodings are used to represent binary or structured data as plain text. This tool helps encode and decode Base64, Base58, and Base32 strings directly in the browser, which is useful when working with API payloads, tokens, hashes, keys, URLs, and debugging data formats.
Common use cases
- Decode API payloads: Inspect Base64-encoded fields in logs, requests, or responses.
- Prepare text-safe values: Encode data for configuration, URLs, headers, or test fixtures.
- Compare encoding formats: Check how the same input appears as Base64, Base58, or Base32.
Things to watch
Encoding is not encryption. Base64 or Base58 can be decoded by anyone who has the string. Do not treat encoded secrets as protected data, and be careful when sharing API keys, tokens, cookies, or private material.
Articles for this tool
Base64, Base58, and Base32 Explained: When and How to Use Each Encoding
How Base64 works at the bit level, why it adds 33% to data size, how Base64, Base64Url, Base58 and Base32 differ, and practical use cases for each.
Encoding vs Hashing vs Encryption: The Difference and When to Use Each
Base64 encoding, SHA-256 hashing and encryption are constantly confused but serve different purposes. A comparison table, examples, and when to use each.
