TechCompare LogoTechCompare
← Back to Home

Text Encoding Converter

Instantly convert between Text, Base64, Binary, Hexadecimal, and Decimal. Perfect for encoding/decoding, debugging, and data analysis.

About this tool

The Text Encoding Converter transforms any string between Base64, binary, hexadecimal, decimal, and UTF-8, all in one place and all running locally in your browser. Paste text into one field and every other representation updates live, which is exactly the workflow you want when decoding a JWT, debugging a malformed API response, inspecting a suspicious string, or solving a CTF puzzle.

Use it when a backend returns Base64-encoded binary data and you need to see what's inside, when you're copy-pasting hex dumps between tools, or when you need to round-trip UTF-8 text through an encoding to prove nothing is corrupted. Because conversion happens entirely client-side, it's safe for tokens, fragments of secrets during local debugging, or anything else you wouldn't paste into a random online encoder.

Supported encodings

Base64 (RFC 4648 with standard alphabet), binary (grouped by byte), hexadecimal (2 chars per byte), decimal (byte values separated by spaces), and raw UTF-8 text. All conversions are round-trip-safe for any valid Unicode input, including emoji and combining characters.

When to use it

Ideal for decoding Base64 strings from JSON payloads, inspecting hex data from packet captures, sanity-checking a URL-safe token, or teaching how the same bytes look across encodings. Pair it with the JSON Formatter when the decoded output is itself JSON, and the Unix Timestamp tool when the decoded payload contains epoch times.

Frequently asked questions

How do I convert text to Base64?
Paste your string into the Text field and the Base64 output appears instantly. The tool uses standard Base64 (RFC 4648), so the output is identical to Linux's base64 command and every major language's built-in Base64 encoder.
What's the difference between Base64 and hex encoding?
Both represent binary data as text, but with different alphabets. Base64 uses 64 characters and needs roughly 4 chars per 3 bytes (33% overhead). Hex uses 16 characters and needs exactly 2 chars per byte (100% overhead). Base64 is denser; hex is easier to read byte-by-byte.
Why does my UTF-8 text break when converted to binary?
UTF-8 encodes non-ASCII characters as multi-byte sequences, so a single emoji or accented letter becomes 2-4 bytes. The binary output will be longer than the character count suggests, that's correct behaviour, not a bug.
Is it safe to paste sensitive data into the converter?
Yes. The encoding conversion runs entirely in your browser with JavaScript, nothing is sent to our servers, logged, or stored. You can verify this with your browser's Network tab: no requests fire when you type.
What is URL-safe Base64?
A variant that replaces `+` with `-` and `/` with `_` so the result can be safely placed in URLs without percent-encoding. JWT tokens use URL-safe Base64. Standard Base64 is fine for most other uses.
Can I decode Base64 back to the original text?
Yes, the converter is bidirectional. Paste Base64 into the Base64 field and you'll get the original UTF-8 string back. If decoding fails silently, the input isn't valid Base64 (wrong characters, bad padding, or it was double-encoded).

Related tools

JSON Formatter

Validate, format, and minify JSON data with syntax highlighting.

Use tool ➜

Unix Timestamp

Convert between Unix timestamps and human-readable dates.

Use tool ➜

Password Generator

Generate secure, random passwords locally in your browser.

Use tool ➜

Color Picker

Pick colors and convert between HEX, RGB, HSL, CMYK, and HSV formats.

Use tool ➜