Encoders & Decoders
Base64, URL, JWT, hash.
Image to Base64 Converter
Convert any image to a Base64 data URL — for inline embedding in HTML, CSS or JSON.
URL Encoder & Decoder
Encode special characters for URLs or decode encoded URLs back to readable text.
JWT Decoder
Decode JSON Web Tokens to inspect header and payload — entirely client-side.
Base64 Encoder & Decoder
Encode any text to Base64 or decode Base64 back to text — UTF-8 safe.
HTML Encoder & Decoder
Escape HTML special characters or decode HTML entities back to text.
Hash Generator (SHA family)
Generate SHA-1, SHA-256, SHA-384 and SHA-512 hashes from any text.
Encoders and decoders: which transformation you need
Four of these encoders and decoders make text safe for a channel that cannot carry it as-is, and two of them, the JWT decoder and the hash generator, are routinely mistaken for security features. None of them encrypts anything, and all of them run in your browser.
Escaping for a context
The URL Encoder and Decoder uses encodeURIComponent, which is for one value going into a query string: a space becomes %20 and an ampersand %26, and an unencoded ampersand is how a search for cats and dogs silently becomes a search for cats. A %25 in the output means something was encoded twice. The HTML Encoder and Decoder escapes the five characters that matter in HTML text and decodes any entity the browser knows; that escaping does nothing inside a script block or a URL, so it is a utility for reading and preparing text rather than a sanitiser.
Bytes as text
The Base64 Encoder and Decoder handles UTF-8, so accents, Arabic and emoji round-trip where the browser's bare btoa() throws, and it uses the standard alphabet with + and /, not the URL-safe variant. Base64 makes data a third larger and hides it from nobody. The Image to Base64 Converter turns an image into a data URI and a matching CSS background-image rule and shows both sizes; it suits an icon of a kilobyte or two and loses on anything shared across pages, because an embedded image cannot be cached on its own.
Reading, not verifying
The JWT Decoder splits a token, shows the header and payload as JSON and flags an expired exp claim. It does not check the signature, and anyone holding the token can read the same claims, so a payload is never a secret and a decoded role is never proof. Paste expired or test tokens, never live ones. The Hash Generator computes SHA-1, SHA-256, SHA-384 and SHA-512 of pasted text through the browser's own crypto.subtle; it is for checksums, and passwords need a slow algorithm such as bcrypt or Argon2 instead. For hashing a file rather than text, use the file hash generator.