Converters
Base Encoding Converter
Convert text and byte data between Base64, Base64 URL-safe, Base32, Base58, Base62, Base85, hexadecimal, binary, and octal locally in your browser.
Tool
Convert text and byte data between Base64, Base64 URL-safe, Base32, Base58, Base62, Base85, hexadecimal, binary, and octal locally in your browser.
This tool runs in your browser. Your input is processed locally and is not uploaded.
About this Tool
Use this free online base encoding converter to move text or UTF-8 byte data between common developer encodings such as Base64, URL-safe Base64, Base32, Base58, Base62, Base85, hex, binary, and octal. Choose the current source format, choose the target format, and convert locally in your browser. Encoding changes how data is represented; it is not encryption and does not protect sensitive information.
Examples
- Hello → SGVsbG8= in Base64
- SGVsbG8= → Hello from Base64
- Hello → SGVsbG8 in Base64 URL-safe
- Hello → 48656c6c6f in hexadecimal
- 48656c6c6f → Hello from hexadecimal
- Hello → 01001000 01100101 01101100 01101100 01101111 in binary
- Hello → 110 145 154 154 157 in octal
- API token data can be converted between Base64 URL-safe and text
Frequently Asked Questions
What is base encoding?
Base encoding represents text or byte data with a limited alphabet of safe characters. It is commonly used in APIs, URLs, tokens, hashes, files, and debugging tools where raw bytes are hard to copy or display.
Is base encoding encryption?
No. Encoding only changes the representation of data. Anyone who knows the format can decode it, so base encoding should not be used to hide passwords, secrets, or private information.
When should I use Base64?
Use Base64 when binary data needs to travel through text-only systems, such as JSON fields, email bodies, form values, configuration files, and simple API payloads.
What is Base64 URL-safe?
Base64 URL-safe replaces characters that can be awkward in URLs and tokens, especially plus and slash. It is commonly used in URL parameters, JWT-like token parts, and other copy-friendly identifiers.
What are Base32, Base58 and Base62 used for?
Base32 is often chosen for case-insensitive or human-readable values. Base58 avoids visually confusing characters and is common in wallet-style identifiers. Base62 uses letters and digits for compact alphanumeric IDs.
What is Base85 used for?
Base85 is a denser text representation than Base64, so it can encode the same bytes with fewer characters. It appears in formats and workflows that want compact ASCII output while still remaining text-based.
Can hex, binary and octal be converted back to text?
Yes. If the encoded values describe valid bytes, the converter can turn hexadecimal, binary, or octal back into text. Invalid byte groups or incomplete values will fail instead of guessing.
Why does invalid encoded input fail?
Each encoding has strict characters, padding rules, and byte grouping rules. If input contains characters outside the selected alphabet, broken padding, or incomplete byte groups, the tool shows an error so the output is not misleading.
Does this converter upload my data?
No. This tool is designed to run completely in your browser. Your input is converted locally and does not need to be sent to a server.
How are non-English characters handled?
Text is treated as UTF-8 before it is encoded. That means characters such as accents, umlauts, symbols, and emoji can be represented as bytes and converted back when the decoded bytes form valid UTF-8 text.