SADevToolBox

Encoding Tools

Encoding problems cause broken links, garbled text and failed API calls. Use these tools to encode data safely for its destination or decode values you find in logs, URLs and headers.

Base64 Encoder Encode text or files to Base64, URL-safe Base64 or data URIs. Base64 Decoder Decode Base64 back to text or a downloadable file. URL Encoder Percent-encode URLs and query string values. URL Decoder Decode percent-encoded URLs and inspect query parameters. HTML Encoder Escape <, >, & and quotes as HTML entities. HTML Decoder Convert HTML entities back to readable characters. JWT Decoder Read JWT header and claims. Decoding does not verify the signature.

About these tools

Base64 represents binary data as text, which is how images are embedded in data URIs and credentials are sent in HTTP Basic authentication. URL encoding (percent-encoding) keeps query string values intact. HTML encoding stops text from being interpreted as markup.

The JWT decoder shows the header and payload of a JSON Web Token in readable form, including expiry times. Decoding is not verification: anyone can read a JWT, and only a signature check with the correct key proves it is genuine.

All encoding and decoding happens locally in your browser. Even so, treat production tokens and credentials with care and avoid pasting live secrets into any website.

Frequently asked questions

Is Base64 a form of encryption?

No. Base64 is an encoding, not encryption. Anyone can decode it without a key, so it must never be used to protect sensitive data.

When should I use URL encoding instead of HTML encoding?

Use URL encoding for values placed inside a URL, such as query string parameters. Use HTML encoding for text inserted into an HTML document so characters like < and & are displayed rather than interpreted.