URL Encode / Decode
Percent-encode text for safe use in URLs and query strings, or decode an encoded string back to readable text. It all runs in your browser.
- 🔒 100% private — no uploads
- 🆓 Free, no watermark
- 📱 Works on any device
How to encode
- 1
Paste or type your text
Type directly or paste your text into the box. It’s processed right in your browser — nothing is uploaded to a server.
- 2
See the result instantly
The tool updates live as you type, showing the URL-encoded result with no “submit” button or waiting.
- 3
Copy or keep going
Copy the result with one click, tweak your input, or clear it and start again. Free, instant and private.
Why use URL Encode / Decode?
Encode for URLs
Turns spaces, ampersands, equals signs and Unicode into safe percent-encoding for query strings and paths.
Unicode-safe
Uses UTF-8 percent-encoding so non-Latin characters and emoji encode and decode correctly.
100% private
Everything runs locally in your browser with JavaScript. Your text is never uploaded, stored or seen by anyone — it even works offline.
Works on any device
No install and no account. Runs in any modern browser on Windows, macOS, Linux, Android or iPhone.
Why URLs need percent-encoding
In a URL, characters like ?, &, = and # aren’t text — they’re structure: they separate the path from the query and one parameter from the next. If a value you’re passing contains them (a search term with an ampersand, say), the URL breaks or silently loses data. Percent-encoding replaces each unsafe byte with %XX so the value travels intact: “fish & chips” becomes fish%20%26%20chips.
Encode the value, not the whole URL
The classic mistake is encoding an entire URL, which turns its own slashes and question marks into %2F and %3F and breaks it. Encode only the piece you’re inserting — a query-string value, a path segment — the way JavaScript’s encodeURIComponent does (and this tool matches). Decoding is the reverse: paste any %-encoded string to read it, including doubly-encoded values you may need to run through twice.
Frequently asked questions
Which characters get encoded?
Anything not safe in a URL component — spaces become %20, and reserved characters like & = ? # are percent-encoded, matching encodeURIComponent.
Is my text uploaded to a server?
No. The tool runs entirely in your browser, so whatever you type or paste stays on your device. It’s safe for code, tokens and confidential text, and works offline once loaded.