Base64 Encode Text, Then Make It URL-Safe
Encode text to Base64, then percent-encode the result so it's safe to drop straight into a URL query string or path segment — a raw Base64 string can contain +, / and = characters that some URL contexts mishandle untouched.
The short answer
Paste text, get a URL-safe Base64 payload back in one pass — no manually percent-encoding the +, / and = a raw Base64 string can contain.
- 1
- 2
Questions
Why not just Base64-encode it and use that directly?
Base64 output can contain +, / and = — all of which have special meaning in a URL (+ means space in a query string, / separates path segments). Percent-encoding afterward keeps the payload intact wherever it ends up.
Does this send my data anywhere?
No. Both steps run entirely in your browser — nothing is uploaded or logged.
How do I reverse it?
URL-decode the string first, then Base64-decode the result — the exact inverse order. Build that as its own chain, or just run the two tools manually one after the other.