Quick Answer
Paste a URL with codes such as %20 and press Convert to read it: caf%C3%A9%20au%20lait decodes to café au lait. To make text safe for a link, choose Encode a value: a space becomes %20 and é becomes %C3%A9. Full URLs are also split into host, path and query parameters.
Embed this calculator
Adjust the size if needed, then copy the code below into your page or blog. The calculator will load in an iframe and stay updated automatically.
Table of Contents
- URL Encoder and Decoder
- Quick Answer
- Related Calculators
- How This URL Encoder and Decoder Works
- How to Use the URL Encoder and Decoder
- How Percent-Encoding Works
- Key Terms
- Worked Example
- Real-Life Examples
- URL Encoding vs Base64
- Common Percent Codes
- When to Encode a Value vs a Full URL
- Common Mistakes to Avoid
- Frequently Asked Questions
- References & Sources
How This URL Encoder and Decoder Works
Web addresses can only contain a limited set of characters. Spaces, accented letters, emoji and symbols such as ?, # and the ampersand have to be written as percent codes. This tool decodes those codes back into readable text, or encodes your text so it can go safely into a link.
Three modes:
- Decode: turns %20, %C3%A9 and other codes back into characters.
- Encode a value: for one part of a URL, such as a search term; it also encodes / ? and =.
- Encode a full URL: keeps : / ? and = so the address still works.
- URL parts: decoding a full URL lists its host, path and query parameters.
How to Use the URL Encoder and Decoder
- Choose Decode, Encode a value or Encode a full URL.
- Paste your URL or text into the box.
- Read the result, which updates as you type.
- Check the URL parts table when decoding a full address.
- Press Copy to copy the result.
How Percent-Encoding Works
- Unreserved characters stay: A to Z, a to z, 0 to 9 and – . _ ~ are never changed.
- Other characters: are turned into UTF-8 bytes, and each byte is written as % plus two hex digits.
- Space: becomes %20. In form data a space can also be sent as +.
- Accented letters: é is 2 bytes in UTF-8, so it becomes %C3%A9.
- Decoding: does the reverse, turning each %XX back into a byte and reading the bytes as UTF-8.
Key Terms
- Percent-encoding: writing a character as % followed by its byte in hex.
- Query string: the part of a URL after ?, with key=value pairs.
- Reserved characters: characters with special meaning in URLs, such as / ? # and =.
- UTF-8: the text encoding used for percent-encoded characters.
Worked Example
Encode the search term 50% off shoes for a link.
- Letters and digits stay the same.
- % becomes %25 and each space becomes %20.
- Result:
50%25%20off%20shoes - Decoding
50%25%20off%20shoesgives back 50% off shoes.
Real-Life Examples
- Reading links:
%E2%82%AC100decodes to €100. - Search links: new york pizza becomes
new%20york%20pizza. - Tracking links: decode a long marketing link to see its query parameters.
- File names: my report.pdf becomes
my%20report.pdf.
URL Encoding vs Base64
- URL encoding: keeps readable letters and replaces only unsafe characters with %XX.
- Base64: rewrites all data in a 64-character alphabet; good for binary data.
- For links: URL encoding is the normal choice for text.
For Base64, use the Base64 Encoder and Decoder.
Common Percent Codes
Codes are the hex value of each character’s byte, from RFC 3986.
| Character | Code |
|---|---|
| Space | %20 |
| ! | %21 |
| # | %23 |
| $ | %24 |
| % | %25 |
| + | %2B |
| , | %2C |
| / | %2F |
| : | %3A |
| = | %3D |
| ? | %3F |
| @ | %40 |
When to Encode a Value vs a Full URL
- Value: use it for anything you place inside a URL, such as a search term or a file name. It encodes / ? = and the ampersand so they cannot break the URL.
- Full URL: use it for a whole address that already has its slashes and question mark in the right places.
- Do not encode twice: encoding %20 again gives %2520, which shows up as %20 in the page.
- Plus signs: in query strings, + often means a space; write %2B for a real plus sign.
Common Mistakes to Avoid
- Encoding a whole URL as a value. The slashes become %2F and the link breaks.
- Encoding twice. %20 becomes %2520.
- Forgetting the plus sign. In queries, + may be read as a space.
- Leaving spaces in links. Some apps cut the link at the first space.
- Broken codes. A % not followed by two hex digits cannot be decoded.
Frequently Asked Questions
Paste it, keep Decode selected, and read the result.
It is a space.
Write it as %20. In form query strings it can also appear as +.
Encoding a value also encodes / ? = and the ampersand; encoding a full URL keeps them so the address still works.
é takes 2 bytes in UTF-8, C3 and A9, and each byte gets its own percent code.
The text was encoded twice: %25 is the percent sign, followed by 20.
No. Conversion happens in your browser.
Yes. When decoding a full URL, the table lists the protocol, host, path, each query parameter and the fragment.
Letters, digits and the four symbols – . _ and ~.
Marketing and email links often carry tracking codes and a second, encoded address inside the query string. Decoding the link shows each parameter so you can see where it really goes.
Yes. Paste any percent-encoded text, such as a single query value, and it is decoded the same way.
References & Sources
| Source | Used For | Link |
|---|---|---|
| IETF RFC 3986, Uniform Resource Identifier (URI): Generic Syntax | Reserved and unreserved characters and percent-encoding. | https://www.rfc-editor.org/rfc/rfc3986 |
| MDN Web Docs, encodeURIComponent() | How values are encoded in browsers. | https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/encodeURIComponent |
DigitalCalculators.net. (2026, November 15). URL Encoder and Decoder. https://digitalcalculators.net/url-decoder/