Home › All Tools ›

URL Decoder

Use URL Decoder online for free at FreeToolZones — no sign-up, no watermark.

Loading tool...

Percent-encoded text is everywhere: in shared links, in server logs, in analytics exports, and in API requests. A web address full of percent-20 and percent-2F sequences is hard to read, hard to check, and hard to explain to someone else. The URL Decoder on FreeToolZones turns that encoded text back into readable form, so you can see the real characters, verify a link, or recover the original value that was passed in a query string.

This guide explains how decoding works, when to enable the plus-to-space option for form-encoded data, and why malformed percent sequences are reported as errors instead of producing partial output. You will find step-by-step instructions, practical examples from debugging links and reading logs, and honest notes about the limits of decoding. If you need to understand what an encoded URL really says, this page shows you how.

What Is the URL Decoder?

The URL Decoder is a free online tool that reverses percent-encoding. Percent-encoding represents a byte as a percent sign followed by two hexadecimal digits. For example, a space is commonly written as percent-20, and non-English characters appear as sequences of percent-encoded UTF-8 bytes. Decoding replaces each valid percent sequence with the character it represents, restoring the original readable text.

The decoder tries the strictest interpretation first. It attempts to decode the input as a URI component, which handles percent sequences for all characters, including those that carry structural meaning in URLs. If that attempt fails because the input contains a sequence that is invalid as a component, it falls back to decoding as a full URI, which is more permissive about structural characters. If both attempts fail, the tool reports a malformed percent sequence error rather than returning partially decoded text. This behavior protects you from acting on a misleading half-decoded result.

An optional checkbox handles form-encoded query strings, where a plus sign represents a space. This convention comes from HTML form submission: when a browser submits a form with the standard encoding type, spaces in field values become plus signs. The decoder checkbox, labeled Convert plus to a space, replaces plus signs with spaces before decoding, so form data reads correctly. Leave the checkbox unticked for ordinary URLs, where a plus sign should stay a plus sign unless it was percent-encoded as data.

  • Two-stage decoding: component decoding first, with a full-URI fallback for structural sequences.
  • Plus-to-space option: correctly handles form-encoded query strings where plus means space.
  • Malformed sequence errors: lone percent signs and invalid hex pairs are reported, not silently passed through.
  • Character counts: input and decoded lengths are shown with the result.
  • Browser-only processing: decoding happens locally; nothing is uploaded.
  • Copy support: copy the decoded result for pasting elsewhere.

How to Use the URL Decoder

The widget has one large input box, a plus-to-space checkbox, and three buttons. Follow these steps to decode percent-encoded text.

  1. Paste encoded text into the input box. Copy the percent-encoded text or URL into the field labeled Encoded text. The placeholder shows a short example with encoded spaces and punctuation. You can paste a full URL, a single query value, or any text containing percent sequences.
  2. Decide whether to convert plus signs to spaces. Tick the checkbox labeled Convert plus to a space only when the input comes from a form-encoded query string, where plus signs represent spaces. For ordinary encoded URLs and values, leave it unticked so literal plus signs are preserved.
  3. Click Decode. Press the Decode button. If the input box is empty, the tool asks you to enter some encoded text first. Otherwise, decoding runs immediately. If the input contains a malformed percent sequence, an error message explains the problem and no partial output is produced.
  4. Review the counts and the decoded text. The result shows the input character count and the decoded character count, followed by the decoded text. The decoded text is usually shorter, because each three-character percent sequence becomes one character or one byte of a multi-byte character. Read through it to confirm it matches what you expected.
  5. Copy the result. Click Copy result to place the decoded text on your clipboard. If you try to copy before decoding, the tool reminds you to decode first. There is no download button in this widget, so paste the copied text where you need it.
  6. Clear and decode the next value. Click Clear to empty the input box and remove the output, then paste the next encoded value. Check the plus-to-space setting each time, because it may need to change between a form-encoded value and an ordinary URL.

If decoding produces text that still contains percent sequences, the input may have been double-encoded. Decode the result a second time to remove the second layer, but only when you are confident double encoding is the cause. Decoding an already-decoded value that legitimately contains percent signs can change its meaning.

Key Features of the URL Decoder

The decoder is built around correctness: it either returns the fully decoded text or reports an error. The features below explain how it achieves that and what each control means.

  • Component-first decoding. The first decoding attempt treats the input as a URI component, which decodes percent sequences for every character, including slashes, question marks, and ampersands that were encoded as data. This is the correct interpretation for encoded values, and it reveals the full original text.
  • Full-URI fallback. If component decoding fails, the tool tries decoding as a full URI, which leaves certain structural sequences untouched. This fallback handles encoded full URLs that contain sequences component decoding rejects, giving you a readable result in more cases without sacrificing the strict first attempt.
  • Strict malformed-sequence handling. A lone percent sign, a percent sign followed by non-hexadecimal characters, or an incomplete UTF-8 byte sequence causes both decoding attempts to fail. The tool then shows a specific error message with examples of malformed input, instead of returning text with some sequences decoded and others left raw.
  • Form-encoding support. The plus-to-space checkbox implements the form submission convention explicitly and only when you ask for it. This avoids the common mistake of decoding form data with plus signs left intact, which leaves spaces unreadable, and the opposite mistake of turning literal plus signs into spaces in ordinary URLs.
  • UTF-8 reconstruction. Multi-byte percent sequences are reassembled into the correct Unicode characters, so accented letters, non-Latin scripts, and emoji appear correctly in the decoded output. A truncated multi-byte sequence is treated as malformed and reported as an error.
  • Length transparency. The input and decoded character counts help you spot double encoding and truncation. If the decoded text is still much longer than expected, or still contains percent signs, further investigation is warranted before you trust the result.

Practical Use Cases for the URL Decoder

Decoding is a reading and debugging skill. The examples below show where readable URLs and values save time and prevent mistakes.

Reading shared and shortened links

Links shared in messages and documents often arrive percent-encoded, especially when they contain search terms, file names, or non-English text. Decoding the link shows the real destination and parameters in readable form, so you can confirm it points where you expect before clicking or forwarding it. This is a useful safety habit for unfamiliar links.

Debugging query strings and redirects

When a redirect loses parameters or a page receives the wrong value, the encoded query string holds the clue. Decoding each value reveals whether a parameter was encoded correctly, whether a value was double-encoded, or whether a plus sign was misread as a space. Fix the encoding at the source once the decoded values show the fault.

Understanding server logs and analytics exports

Logs and analytics tools record URLs in encoded form. Decoding the recorded addresses makes reports readable: search terms appear as words, page titles appear as text, and campaign values make sense. Decode a sample of log entries to confirm the pattern before processing a full export.

Recovering form submission data

Form submissions encode field values with percent sequences and plus signs for spaces. Decoding with the plus-to-space option restores the exact text the user typed, including spaces, punctuation, and non-English characters. This is useful when inspecting raw submissions, debugging form handling, or recovering data from a log.

Checking double encoding problems

Double-encoded values contain percent-25 sequences where a single percent sign was encoded again. Decoding once leaves visible percent sequences; decoding twice restores the original. Recognizing this pattern in decoded output tells you that some step in the pipeline encoded an already-encoded value, and that the fix belongs in that step.

Inspecting API requests and responses

API debugging often involves reading encoded URLs from logs, proxies, or test tools. Decoding them reveals the actual parameters sent, which you can compare against the API documentation. A mismatch between the decoded parameters and the expected request usually points to an encoding error in the client code.

Tips and Best Practices

  • Decode values separately when precision matters. Decoding a whole URL at once is fine for reading, but for debugging, decode each query value separately. This isolates which value is malformed or double-encoded, instead of letting one bad value block decoding of the whole address.
  • Use the plus option only for form data. Tick the plus-to-space checkbox only when you know the input used form encoding. In ordinary URLs, a plus sign is a literal character, and converting it to a space changes the meaning, for example in a search term or a mathematical expression.
  • Treat malformed errors as information. An error means the input contains a percent sequence that cannot be decoded, such as a lone percent sign or invalid hex digits. Find the offending sequence in the input, check whether the copy was truncated or edited, and fix it before decoding again.
  • Do not trust decoded URLs blindly. Decoding reveals what a URL says, not whether it is safe. A decoded link can still point to a deceptive or malicious destination. Check the domain and path carefully, and do not enter credentials on a page reached through an unfamiliar decoded link.
  • Keep the original encoded text. Save the original before decoding, especially when debugging. The encoded form is what was actually transmitted, and comparing it with the decoded form shows exactly what the encoding step did. Discarding the original makes the problem harder to reproduce.
  • Watch for percent signs in decoded output. If decoded text still contains percent signs followed by hex digits, the input was probably double-encoded. Decode again cautiously, and investigate which step encoded twice. If the percent signs are literal content, leave them alone.

Limitations of the URL Decoder

The decoder reverses percent-encoding only. It does not decode Base64, HTML entities, or other encoding schemes, and it does not parse a URL into its parts, such as host, path, and query parameters. If you need structured URL analysis, split the URL manually or use a dedicated URL parser. The tool also does not validate that a decoded URL exists or is reachable, and it does not follow redirects.

Malformed input produces no output at all, by design. If only one value in a long query string is malformed, the whole decode fails, and you must isolate the bad value yourself. The tool does not repair truncated input or guess at missing characters. Decoding does not make content safe: decoded text should be treated as untrusted input, just like the encoded form, and should never be executed as code or inserted into a page without proper handling. Finally, there is no download button in this widget; copy the decoded result and paste it where it is needed.

Frequently Asked Questions

What does percent-20 mean in a URL?

Percent-20 is the percent-encoded representation of a space. The number 20 is the hexadecimal value of the space byte. Decoding replaces it with an actual space. Other common sequences include percent-2F for a slash and percent-3F for a question mark, when those characters appear as data rather than structure.

When should I tick the plus-to-space checkbox?

Tick it when the input comes from an HTML form submission or another form-encoded source, where spaces are written as plus signs. Leave it unticked for ordinary URLs and encoded values, where a plus sign is meant literally.

Why does decoding fail with a malformed sequence error?

The input contains a percent sign that does not start a valid two-digit hexadecimal sequence, or a sequence of bytes that does not form valid UTF-8. Common causes include a lone percent sign, a truncated copy, or text that was edited after encoding. Find and fix the bad sequence, then decode again.

Why does my decoded text still contain percent signs?

The input was probably encoded twice. The first decode removes one layer and leaves the second layer visible. Decode the result once more to remove the second layer, and investigate which step in your pipeline encoded an already-encoded value.

Can the decoder handle non-English characters?

Yes. Percent-encoded UTF-8 byte sequences are reassembled into the correct Unicode characters, including accented letters, non-Latin scripts, and emoji. If a sequence is incomplete, decoding fails with a malformed sequence error rather than producing a wrong character.

Is decoding the same as making a URL safe?

No. Decoding only changes representation; it reveals what the URL contains. A decoded URL can still be misleading or harmful. Always check the destination carefully before visiting an unfamiliar link.

Related Tools

These related tools encode URLs, decode other formats, and turn links into shareable codes. Browse the full collection from the FreeToolZones home page.

Browse More Tools