Encoding and decoding tools

Text encoding is one of those problems that looks trivial until you hit it: a query parameter that contains an ampersand, a base64 string with the wrong padding, an HTML snippet that renders its own markup instead of displaying it, a logo you want to inline in a CSS file without triggering another HTTP request. The fix is almost always one round trip through the right encoder or decoder.

These tools cover the formats that come up most often in real work — Base64 (text), URL percent-encoding, HTML entities, and image-to-data-URL embedding — all bidirectional. Encode a value when you need to embed it safely in a URL, JSON payload, HTTP header, email body, or inline in CSS. Decode a value when you are trying to read what something actually contains. Every tool runs in your browser, so you can paste API tokens, internal payloads, or unreleased brand assets without worrying about logging.

The encoder pages also explain the gotchas that catch people out: when to use Base64 versus URL-safe Base64, when to reach for `encodeURIComponent` instead of `encodeURI`, why `+` becomes a space in form data, why `'` is XML-only and not safe for HTML, when embedding an image as a data URL is a smart call and when it's HTML bloat. The kind of detail that turns a five-minute bug hunt into a five-second fix.