Safely encode text or links for URLs (percent-encoding per RFC 3986) - locally in your browser, with no upload.
Running locally on your device ...
Running locally on your device ...
0%
Your files never left your device
No. Everything runs in your browser - your file never leaves your device. How this is verifiable
A URL may only contain certain characters. Spaces, accented letters, ampersands, slashes or question marks must be replaced, otherwise the link breaks or a parameter is misread. Percent-encoding per RFC 3986 solves this by rewriting such characters into a harmless sequence of a percent sign and two hex digits (a space becomes %20). This tool does that reliably for any text you want to put into a link or parameter.
You choose between two modes. In component mode truly every special character is encoded - that is right when your text is the value of a single parameter (such as a search term), because then an & or = inside it must not tear the URL apart. In whole-URL mode the structural characters of an address (slashes, ?, &) stay untouched and only the other unsafe characters are encoded - suitable when you are carrying a complete address.
Encoding runs entirely locally in your browser in pure JavaScript - your text is not uploaded, not stored, and no foreign library is loaded from a CDN. The reverse direction is handled by the URL decode tool. You can download the result as a text file or copy it straight out.
| Input formats | Text input |
|---|---|
| Output format | TXT |
| Batch processing | No |
| Processing | Locally in your browser (JavaScript) |
| File upload | None |
Limitations: Percent-encoding is not encryption: anyone can read it back, it only makes a text transport-safe. Component mode also encodes structural characters such as / and &, which makes a complete address unusable - that is what whole-URL mode is for. Very large texts are limited by your device memory.
No. Encoding runs entirely locally in your browser; your text never leaves your device and is not stored.
Component for the value of a single parameter (then & and = are encoded too). Whole URL when you are carrying a complete address and its structure (slashes, ?, &) should be preserved.
No. Percent-encoding only makes text URL-safe; anyone can read it back. For secrecy use an encryption tool.
With the URL decode tool: it turns the %-sequences back into readable text.
Decode URL · Encode to Base64 · Slugify · Text to Base64 · Encode HTML · Escape JSON