URL Encoder/Decoder
Percent-encode text or full URLs, or decode encoded URLs back to readable text. Supports UTF-8 and form-style + spaces. Free and private.
Runs in your browser. Nothing is uploaded.
About the URL Encoder/Decoder
URLs can only contain a limited set of characters. Spaces, accented letters, emoji and symbols like & or ? must be “percent-encoded” (a space becomes %20, é becomes %C3%A9) or the URL breaks or changes meaning.
This tool percent-encodes text and decodes encoded URLs back into readable text. It's useful for building query strings, debugging redirect URLs, reading tracking links, and checking what an API actually received.
How to use it
- Choose Encode or Decode.
- When encoding, pick “Value / parameter” for a single query value or path segment, or “Full URL” to encode a whole address while keeping its structure.
- Tick “Spaces as +” if the value is for an HTML form submission (application/x-www-form-urlencoded).
- Paste your text. The result updates as you type. Copy it, or press “Use as input” to reverse it.
Examples
A search query value
“café & crêpes?” as a value becomes caf%C3%A9%20%26%20cr%C3%AApes%3F, so the & and ? aren't mistaken for URL syntax.
A full URL
https://x.com/a b?q=é stays a working URL: https://x.com/a%20b?q=%C3%A9. The : / ? and = are kept.
Reading a redirect link
Decoding https%3A%2F%2Fexample.com%2Fhome reveals the destination: https://example.com/home.
Form encoding
With “Spaces as +”, “red shoes” becomes red+shoes, as browsers send it when a form is submitted.
Limitations
- “Value / parameter” mode follows JavaScript's encodeURIComponent, which leaves - _ . ! ~ * ' ( ) unencoded. Some strict systems (e.g. OAuth signatures) also require encoding ! ' ( ) *.
- Decoding fails if a % isn't followed by two hex digits, or if the escapes don't form valid UTF-8. The tool tells you when this happens.
- Only percent-encoding is handled; HTML entities like & are a different format.
Frequently asked questions
What's the difference between encoding a value and a full URL?
Encoding a value escapes everything with special meaning, including / ? & = #, so it can sit safely inside a URL. Encoding a full URL keeps those characters, because they define the URL's structure.
Should spaces be %20 or +?
%20 is correct everywhere in a URL. + means a space only in query strings sent by HTML forms. When in doubt, use %20.
Why is é encoded as two escapes (%C3%A9)?
Characters are first converted to UTF-8 bytes, and é takes two bytes. Each byte becomes one %XX escape. Emoji take four.
Is URL encoding the same as encryption?
No. It only makes text safe to put in a URL, and anyone can decode it.
Related tools
Base64 Encoder/Decoder
Encode text to Base64 or decode Base64 back to text.
JSON Formatter
Format, validate and minify JSON with clear error messages.
UUID Generator
Generate random v4 or time-ordered v7 UUIDs, one or many at a time.
JWT Decoder
Decode JSON Web Tokens to inspect the header, payload and expiry.