Result
—
Notes
Output is standard Base64 with +/=. URL-safe variant swaps + for - and / for _; decode accepts both. Byte length is shown so you can check payload sizes against API limits.
UTF-8 safe in both directions — emoji and Chinese survive the round trip.
Output is standard Base64 with +/=. URL-safe variant swaps + for - and / for _; decode accepts both. Byte length is shown so you can check payload sizes against API limits.
Encode text to Base64 or decode Base64 back to text with full UTF-8 handling, so accented characters and CJK text survive the round trip instead of turning into mojibake.
URL-safe input is accepted on decode, which is what you usually get from a JWT segment or a query parameter where plus and slash have been replaced.
The decoded byte count is shown so you can tell a truncated payload from a genuinely short one. Everything is processed locally with TextEncoder and TextDecoder.
Need a tool that is not here? Ask for one.