Encoding Tools

Encoding is not encryption and it protects nothing. What it does is let binary data survive a channel that only accepts text: a certificate pasted into a config file, an image embedded in an email template, a password in a Basic auth header, a file name pushed through a URL.

The three tools here cover the two encodings that actually come up in day-to-day administration. Everything runs in the browser, so a private key or an internal document is never uploaded.

Tools in this category

  • Advanced base64 encoder and decoder — encode and decode whole files as well as text, with drag and drop, file download and support for larger inputs. Use this one when a file is involved.
  • Base64 encoder & decoder — a stripped-down text-only version for the common case: paste a string, get the result, move on.
  • URL encoder and decoder — percent-encode query parameters and paths, and decode a URL that arrived mangled in a log line or a ticket.

Where these get used

Certificates are the everyday case. A PEM file is Base64 with a header and footer around it, which is why you can paste one into a text field at all. When a load balancer rejects a certificate, decoding the body is often enough to see that two files were concatenated in the wrong order, or that a chain is missing.

URL encoding shows up as a bug, not a task. A share path with a space, a customer name with an ampersand, a search string with a plus sign: each one breaks something downstream, and the fix is to encode it before it goes into the URL rather than after something has already failed. Decoding works the other way, turning an unreadable line in a proxy log back into the request someone actually made.


Related guides


Other tool categories