Web Tools · Free · No signup
Spaces become %20, ampersands %26, accented letters their UTF-8 byte sequences — correct percent-encoding is what keeps query strings, form data and shared links intact. Choose full component encoding (everything special is escaped — for parameter values), URL-preserving encoding (structure like ? & / stays readable), or either direction of decoding. Paste, convert, copy. The conversion is pure browser JavaScript; nothing is sent anywhere.
🔒 100% private: everything runs inside your browser — nothing is uploaded, stored or logged.
Component mode escapes every reserved character (encodeURIComponent semantics); URL mode keeps ? & = / # structure intact (encodeURI semantics).
Turn %20 soup back into readable text, with strict validation of malformed sequences.
Non-Latin text encodes to its UTF-8 byte sequence — the standard browsers and servers expect.
Decode a broken sequence like %E0%A4 and get a clear error instead of silent corruption.
Encoding runs in your browser. URLs with tokens or tracking parameters stay private.
Input & output. Input: any UTF-8 text or URL fragment. Output: percent-encoded text (%-sequences) or decoded text. Both the standard and URL-safe handling of reserved characters are supported via mode selection.
Encoding a full URL in component mode escapes its structure (// and ?) — that mode is for values, not whole links; use “Encode URL” for complete links. Decoding assumes percent-sequences are valid UTF-8. The tool does not validate whether the URL itself is reachable or well-formed beyond the encoding rules.
Component mode (encodeURIComponent) for individual values you place inside a query string — it escapes & = ? so a value cannot break the URL. URL mode (encodeURI) for a whole link you want to keep working: it preserves ://?& structure and only escapes characters that are illegal in URLs.
It became %26 — that is correct. Inside a parameter value, a raw & would split the parameter. Decode it with component mode to get it back.
Both mean space in practice: %20 is the standard percent-encoding, + is a legacy convention from form submission (application/x-www-form-urlencoded). Use %20 when building URLs by hand.
Yes — run decode twice. Sequences like %2520 (encoded %20) need one more pass; the second decode reveals the space.
No — a correctly encoded URL addresses the same resource. Servers decode percent-sequences before routing. Only incorrect double-encoding changes what the server sees.
Keep going
Encode or decode Base64 text with full Unicode and URL-safe support.
Use Tool →
Build tracked campaign URLs with clean, lowercase UTM parameters.
Use Tool →
Turn titles into clean, SEO-friendly URL slugs — batch mode included.
Use Tool →
Format, validate and minify JSON with clear error locations.
Use Tool →
Generate SEO and Open Graph meta tags with a search preview.
Use Tool →
On mobile?
This tool runs in any mobile browser — no app needed. And for the image & PDF side of the toolbox, the CompressoPanda Android app ships 36 tools that run with no connection at all: compression to target size, editing and PDF essentials included.