Home / Developer Tools / Base64 Encode / Decode
Developer Tools
Convert text and payloads to and from Base64.
Base64 Encode / Decode converts text and binary payloads to and from Base64 — the encoding used to carry binary data in JSON, JWTs, data URIs and email MIME parts.
Enter the text you want to encode (or a Base64 string you want to decode) and run the tool. The probe detects the direction from the input and returns the converted result.
Input: Text — e.g. networkutils.
The output shows the encoded Base64 string (when encoding) or the decoded plaintext (when decoding). Base64 output contains only A–Z, a–z, 0–9, +, / and = padding. If decoding produces unreadable characters, the input was likely binary or a URL-safe variant that needs - and _ substituted for + and /.
→ Encode a payload for a JWT, data URI or JSON field.
→ Decode a Base64 token from an API response or header.
→ Convert between standard and URL-safe Base64 variants.
→ Inspect a Basic-auth Authorization header value.
No. Base64 is an encoding, not encryption — it is trivially reversible and provides zero confidentiality. Never use it to protect secrets. Use it only to transport binary data through text-only channels like JSON, URLs or email.
Standard Base64 uses + and /, which have special meaning in URLs. URL-safe Base64 replaces them with - and _ and often drops = padding, so the output can be embedded in a URL path or query string without encoding.
The input was probably binary data, not text, or it used the URL-safe alphabet. Try substituting -/_ for +//, or treat the decoded bytes as binary rather than text. UTF-8 multibyte characters also look like garbage if decoded as the wrong encoding.