ToolsForWeb

Saved

Tap ☆ on any tool to keep it here.

AboutFAQContactPrivacyTerms
toolsforweb

Encoding & Decoding

Convert between text and wire formats: Base64 with URL-safe and Unicode support, URL percent-encoding, JSON string escapes, and text to binary or hex.

4 tools
Base64 Encode / Decode

Encode text to Base64 or decode it back, with URL-safe and Unicode support.

URL Encode / Decode

Percent-encode or decode text for use in URLs and query strings.

JSON String Escape / Unescape

Escape text for a JSON string, or unescape a JSON string back to plain text.

Text to Binary & Hex Converter

Convert text to binary, hex or decimal bytes, or decode bytes back to text.

About Encoding & Decoding

Convert text between human-readable form and the encodings used on the wire. The Base64 tool encodes and decodes with the standard and URL-safe alphabets, handles full Unicode and tolerates missing padding; the URL tool percent-encodes text for paths and query strings, with a strict component mode and a spaces-as-plus option, and reports malformed escapes instead of guessing.

The JSON string tool escapes quotes, backslashes and line breaks so text fits inside a JSON value, and unescapes strings copied from logs or payloads. The text to binary and hex converter shows the UTF-8 bytes behind any text in binary, hex or decimal, and decodes them back.

All four run in your browser. For related formats, the Web & Dev tools cover HTML entities and URL parsing, the Converters include a number base converter for single numbers, and the Security tools decode JWTs, which are base64url under the hood.

Questions

Is Base64 encryption?

No. Base64 is an encoding that anyone can reverse; it makes binary data safe to carry in text, like email or JSON. Never use it to hide secrets.

What is the difference between Base64 and Base64URL?

Base64URL swaps + and / for - and _ and usually drops the = padding, so the result can sit in a URL or filename without escaping. JWTs use Base64URL.

Which encoder do I need?

It depends on where the text is going. Use URL encoding for a value inside a link or query string, JSON escaping for text inside a JSON string, and Base64 to carry arbitrary bytes, such as a file or binary token, through a text-only channel. Binary and hex show the raw bytes themselves and are mostly for inspection and debugging.

Should spaces in a URL be %20 or +?

In the path, always %20. In a query string, + is the traditional form-encoding for a space and most servers accept it, but %20 works everywhere.