Encoders & Converters

Six converters for the encodings developers hit every day: Base64, URL percent-encoding, HTML entities, number bases, Unix timestamps and binary. Each one runs locally in your browser, so the tokens and strings you decode stay on your machine.

Encode and decode text without corrupting it

The Base64 Encode / Decode tool converts text through UTF-8 before encoding, so emoji and accented characters round-trip correctly — a step the browser’s built-in btoa() skips, which is why many converters corrupt anything beyond plain ASCII. The URL Encoder / Decoder percent-encodes query strings and paths, and decodes those %20-riddled links back into readable text. Both directions earn their keep: encoding when you build a URL by hand, decoding when you want to know what a tracking link actually contains before you click it.

The HTML Entity Encoder / Decoder escapes characters like angle brackets and ampersands so user-supplied text can sit inside a page without being parsed as markup, and turns entity-riddled exports back into plain readable text. The Text to Binary Converter translates text into ones and zeros and back — mostly used for teaching and puzzles, but it makes the byte-level view of a string concrete in a way no explanation quite manages.

Convert numbers, bases and timestamps

Two converters deal with numbers rather than text. The Number Base Converter moves values between binary, octal, decimal, hexadecimal and any base up to 36 — handy for reading permission bits, color values or anything a debugger prints in hex. The Unix Timestamp Converter turns epoch seconds or milliseconds into human-readable dates and back again, which is the fastest way to check what moment a raw number in your logs or database actually refers to, in both UTC and your local time zone.

Frequently asked questions

Is Base64 a form of encryption?

No. Base64 is an encoding — anyone can reverse it instantly with a tool like this one or a single line of code. It exists to move binary data through text-only channels, not to hide anything, so never use it to protect passwords or secrets.

Is it safe to decode tokens or credentials with these tools?

Everything on this page runs locally: the string you paste is processed by JavaScript in your browser and never transmitted. That said, treat production secrets with care anywhere — the safe habit is to decode them only in tools you can verify work offline, which these do.

When do I need URL encoding instead of Base64?

URL encoding escapes the specific characters that have meaning in a URL — spaces, ampersands, question marks — so a value can travel inside a query string. Base64 converts arbitrary binary data into a fixed text alphabet. If you are putting a plain text value into a URL parameter, you want the URL Encoder; if you are embedding binary data in text, you want Base64.

Looking for something else? Browse all 67 tools, or jump to JSON Tools, CSV & Data Tools and CSS & Color Tools.