How to use
- Pick an encoding and direction.
- Type or paste; the result updates live. Invalid input is reported, not guessed.
Worked example
“héllo wörld” URL-encodes to h%C3%A9llo%20w%C3%B6rld and Base64-encodes to aMOpbGxvIHfDtnJsZA==.
Supported formats and limits
| Input | Text, Files (Base64) |
|---|---|
| Output | Text, Files (decoded Base64) |
| Engine | TextEncoder/TextDecoder with strict validation |
Limitations
- Decoding Base64 to text assumes UTF-8; binary data is offered as a file download instead.
Questions
Is encoding the same as encryption?
No. Base64, URL encoding, HTML entities, hex and Unicode escapes are reversible representations that anyone can decode without a key. Do not use them to hide passwords or secrets.
Which URL encoding should I use?
Component mode encodes every reserved character, for a single query value or path segment. URI mode leaves characters such as / ? & = in place, for a whole address. “héllo wörld” becomes h%C3%A9llo%20w%C3%B6rld.
What happens with binary Base64?
If the decoded bytes are not valid UTF-8 text, they are offered as a file download instead of shown as garbled text. Files can also be encoded to Base64.
Privacy
Runs on your device. Files and text are processed in this browser tab and are not uploaded.
See the privacy policy for how toolsdocks handles data.