Encode
Turns text into percent-encoded form (%XX, UTF-8) — safe for URLs, query parameters and API requests.
URL Encode & Decode
Percent-encode and decode text and addresses — with single-component and full-URL modes, and full UTF-8 support. Everything runs in your browser.
encodeURIComponent — encodes everything (& = ? / : …)
Decode
Recovers the original text from a percent-encoded string, with a clear message on invalid input.
Component or full URL
"Component" encodes everything (encodeURIComponent); "Full URL" preserves the address structure (encodeURI).
Frequently asked questions
What is URL encoding (percent-encoding)?
URL encoding, also called percent-encoding, replaces characters that are unsafe in a URL (spaces, non-Latin letters, & ? = / and more) with %XX sequences based on their UTF-8 bytes. This lets addresses and parameters travel correctly across the web.
What is the difference between "Component" and "Full URL"?
"Component" uses encodeURIComponent and encodes everything, including characters that are special in a URL (& = ? / : #). Use it for a single parameter value. "Full URL" uses encodeURI and preserves URL structure (scheme, slashes, separators), encoding only the genuinely unsafe characters.
Does it support Cyrillic and emoji?
Yes. Encoding is UTF-8 based, so Cyrillic, emoji and any Unicode characters are correctly turned into %XX sequences and restored exactly on decode.
Why does decoding show an error?
The input contains an invalid percent-sequence — e.g. a "%" not followed by two hex digits (like %ZZ or a truncated %A). Check that you pasted the whole string without missing characters.
When is a space encoded as + versus %20?
In a URL path and with encodeURIComponent, a space becomes %20. The + character means a space only in form data (application/x-www-form-urlencoded), i.e. the query part. This tool uses %20, which is valid in both cases.
Is my data uploaded anywhere?
No. All encoding and decoding happens locally in your browser via JavaScript — nothing is sent to a server.