Same message.
Different wrapping.
Encode Unicode text as UTF-8 Base64, or encode and decode URL components with clear errors.
Encoding
01 / INPUT TO OUTPUTA clearer view starts here.
Your result will appear here.
Same device. A little less friction.
Less context switching.
More getting it done.
One focused workbench. Six useful tools.
Your data stays in session memory until you clear it.
Bring your input
Paste test data or open a local UTF-8 file.
Make it make sense
Choose the rules. Run the tool. Inspect the result.
Take your work with you
Copy or download only when you’re ready.
At this desk: Encoding
Choose Base64 or URL-component encode/decode. Base64 uses the standard alphabet with canonical padding; whitespace is rejected on decode.
UTF-8 decoding is strict. Invalid byte sequences, padding, percent escapes, and unpaired Unicode surrogates produce errors. Base64 is not encryption.
URL mode uses encodeURIComponent/decodeURIComponent, not full-URL or form encoding. A plus sign is preserved when decoding. Input limit is 5 MiB; output limit is 32 MiB.
Clear session removes application references, not downloaded files or browser/OS memory. Ordinary application asset requests still reach the host. There is no analytics, content persistence, or processing service.