Base64 Encode & Decode
Convert text to Base64/Base64URL and decode strings back to plain text for debugging emails, API requests, or JWTs.
VXRpbHN2ZXJzZSB0b29scyAmIGNvbnZlcnRlcnM=
VXRpbHN2ZXJzZSB0b29scyAmIGNvbnZlcnRlcnM
Utilsverse tools & converters
Whitespace is ignored automatically. URL-safe output replaces `+` and `/` with `-` and `_`, removing padding for tokens like JWTs.
How to run quick Base64 conversions
Paste any text into the encoder and you immediately get both standard Base64 output and the URL-safe variant used by JWTs, cookies, and query parameters. Need the reverse? Drop a Base64 string into the decoder and we automatically normalize whitespace, padding, and URL-safe characters before translating it back into readable text.
Use this for email templates, binary blobs, or webhook payloads that need to stay ASCII-friendly without leaving the browser.
Practical tips
- Choose the URL-safe variant when embedding tokens inside URLs or cookies.
- Seeing decode errors? Check for characters outside A-Z, a-z, 0-9, +, /, -, or _.
- Pair with the URL Encode & Decode tool when you need to nest Base64 inside query parameters.
Where Base64 shines
It keeps binary data safe across text-only channels. A few fast examples:
- Embedding inline images in HTML or CSS.
- Passing payloads through systems that strip non-ASCII characters.
- Sharing JWT header and payloads before verifying signatures in the JWT Decoder.
Example workflow
Paste {"id":123,"role":"admin"} → copy the Base64URL output for a JWT payload → verify the decoded claims with the JSON Formatter before shipping.
FAQ highlights
Do you store anything? No—everything runs locally and clears when you refresh the page.
Can I encode files? Drag the file into a text editor to grab its string output first. Multi‑megabyte binaries work best with dedicated CLI tools.