URL Encoder / Decoder
Percent-encode query strings and paths.
Never uploadedUTF-8 safe both ways, with URL-safe output when you need it.
The tool handles both directions.
UTF-8 is handled correctly in both directions.
Switch to URL-safe output if the value is going into a query string.
No, and this matters. Base64 is an encoding, not a cipher - anyone can decode it instantly. Never use it to protect a secret; it exists to move binary data safely through text-only channels.
Standard Base64 uses + and /, which have meaning inside a URL. The URL-safe variant swaps them for - and _ and drops the trailing padding, so the string survives being put in a query parameter.
Because most naive implementations use btoa directly, which only handles Latin-1. This one encodes to UTF-8 bytes first, so any character survives the round trip.
Decoders usually accept a string without trailing = signs, and this one restores them automatically. Some strict parsers do require them, so keep the padding if you are handing the value to something you don't control.
Encode text to Base64 and decode it back, correctly handling UTF-8 so emoji and accented characters survive the round trip - something naive implementations using btoa directly get wrong, because that function only understands Latin-1. A URL-safe mode swaps the + and / characters for - and _ and drops padding, which is what you need when the value goes into a query string. Worth repeating: Base64 is an encoding, not encryption. Anyone can reverse it instantly, so never use it to hide a secret.
The last couple are from other categories - there are 81 tools here in total.
Percent-encode query strings and paths.
Never uploadedFormat, validate and minify JSON instantly.
Never uploadedRead a token's header and claims locally.
Never uploadedRandom v4 UUIDs, as many as you need.
Never uploadedStrong random passwords, generated in your browser.
Never uploadedMonthly payment with tax and insurance included.
Never uploaded