Have you ever copied a web link and found it full of %20 and %2F symbols? Those codes are percent-encoding, and they hide the real text. The URL Decoder turns that encoded string back into plain, readable characters.
This tool helps developers, marketers, and support staff read tracking links and query strings. You paste an encoded URL, and the decoded text appears as you type.
Table of Contents
- What the Tool Does
- How to Use It, Step by Step
- How the Decoding Works
- Worked Example
- How to Read the Result
- The Plus Sign and Spaces
- Limitations and Assumptions
- FAQs About the URL Decoder
What the Tool Does
The tool reverses percent-encoding as you type. It follows the strict RFC 3986 rule for web addresses.
- Encoded URL Input: a text box where you paste the encoded string.
- Decoded Plain Text Result: a read only box that shows the readable output.
- Decode URL: a button that runs the conversion, though it also runs as you type.
- Copy: a button that copies the result and shows Copied when it works.
- Three cards at the top show Input Bytes, Output Characters, and Status.
How to Use It, Step by Step
- Paste your encoded link into Encoded URL Input. A sample link loads by default.
- Watch the Decoded Plain Text Result update while you type.
- Press Decode URL if you want to run it again by hand.
- Check the three cards for byte count, character count, and status.
- Press Copy to place the result on your clipboard for pasting elsewhere.
How the Decoding Works
The tool reads your text one character at a time. When it meets a percent code, it swaps in the real character.
Encoded Input→Find Percent Codes→Decode Bytes=Plain Text
A percent code is a percent sign and two hex digits. For example, %20 is a space and %3A is a colon.
Non-English letters use more than one code. The accented letter in cafe arrives as %C3%A9, and the tool joins those bytes into one character.
Worked Example
Dana pastes the sample link that loads with the tool. The encoded string packs a full address and a query into percent codes.
| Stage | Value |
|---|
| Encoded input | https%3A%2F%2Fexample.com%2Fsearch%3Fq%3Dhello%20world%20%26%20test%3D100%25 |
| %3A and %2F | become : and / |
| %3F, %3D, %26 | become ?, =, and & |
| %20 and %25 | become a space and a percent sign |
| Decoded result | https://example.com/search?q=hello world & test=100% |
The cards then read 76 input bytes and 52 output characters. The Status card shows Decoded for this clean input.
A second case shows a query string on its own. The input name%3DJohn%20Doe%26city%3DNew%20York decodes to name=John Doe&city=New York.
How to Read the Result
The Decoded Plain Text Result box holds the readable version. You can select it, read it, or copy it with the button.
The Status card reports one of three words. It shows Empty, Decoded, or Partial so you know what happened.
If a code is broken, the tool still decodes the rest. It keeps the lone percent sign and shows a red note with its position.
For example, 100% decodes to 100% and the status reads Partial. The note points to the incomplete code at position 3.
An empty box shows a gray note that asks for input. The Status card then reads Empty until you type again.
The Plus Sign and Spaces
Spaces can be encoded in two ways on the web. Addresses use %20, while old web forms use a plus sign.
This tool follows the strict address rule. It decodes %20 to a space and keeps a plus sign as a literal plus.
So a path like one+two stays one+two, not one two. This protects real plus signs in paths and search terms.
If your text came from a web form, a plus may have meant a space. In that case, swap each plus for %20 before you decode.
If you need the opposite action, the URL Encoder rebuilds the percent codes. To split a link into its host, path, and query parts, try the URL Parser.
Limitations and Assumptions
- The tool decodes text only. It does not fetch, open, or check the link.
- A plus sign stays a literal plus. Only percent codes like %20 become their characters.
- A broken percent code gives a partial result, not a blank error.
- The three cards update live from your current input, so they match what you paste.
- Invalid bytes that are not valid UTF-8 show as a replacement character with a note.
To pull links out of a block of text, the URL Extractor helps first. For HTML entities inside a page, the HTML Decoder is the right fit. To reverse base64 data in a link, see the Base64 Decoder. More utilities sit in the developer tools hub.
FAQs About the URL Decoder
What Is Percent-Encoding Used For?
Percent-encoding lets spaces, symbols, and non-English letters travel safely inside a web address. Servers and browsers rely on it to keep links from breaking.
Why Do the Input Bytes and Output Characters Differ?
Input Bytes count the encoded text in UTF-8, where each code is several bytes. Output Characters count the shorter decoded result, so the two numbers rarely match.
Does This Tool Send My Link Anywhere?
No. The decoding runs inside your browser with built in functions. Nothing you paste is uploaded or saved by the tool.
Can It Decode a Very Long URL?
Yes. The tool sets no length limit, so long tracking links decode fine. Your browser handles the work without any server.
Which Hex Digits Count as Valid?
A valid code uses 0 to 9 and the letters A to F. The tool reads both upper and lower case hex digits.
Is Decoding the Same as Unescaping HTML?
No. Percent-encoding is for URLs, while HTML uses entities like & and <. Use an HTML focused tool for page content.
This calculator gives general estimates only and is not professional advice. Reviewed for general accuracy by Prof. Dr. Khalil Mudassar, PhD.