Work through the task
Encode/decode UTF-8 text or escape/unescape a selected text/literal context.
- Select Encode for Base64/URL operations or Escape for literal transformations.
- Choose the direction and context before running. A complete quoted literal can be required when unescaping.
- Review the result before copying or downloading. Editing an input invalidates the previous result; keep an original if the transformation matters.
Example to check
UTF-8 text café 😀 round-trips through canonical Base64. HTML escape turns <b> into <b>.
Limits and output behavior
Maximum 100,000 input characters and 1,000,000 output characters. Contexts have different complete-literal rules; unsupported syntax and malformed encoded input are rejected. Escaping is not application validation, general HTML sanitization or SQL injection protection. Base64 decoding requires canonical padded text without whitespace and valid UTF-8 bytes. URL mode encodes a component, not a complete URL.
Troubleshooting
Confirm the action, direction and literal context. Canonical Base64 requires padding/no whitespace and valid UTF-8; malformed byte sequences or an incomplete quoted literal are rejected.
Questions
Does URL mode encode an entire URL safely for every purpose?
No. It encodes/decodes a URL component. Context, delimiters and the surrounding application still matter.
Input and privacy
Processing runs in this browser. Inputs are not saved automatically. An explicitly chosen local draft, where offered, is plaintext storage on this device. Downloaded files, clipboard contents and browser extensions have separate retention behavior.