← All tools
// ENCODERS

URL Decoder online

Decode percent-encoded URL strings - converts %20, %3D and all encoded characters.

URL Decoder logo
by
CHUNKY
MUNSTER
ENCODED INPUT0 CHARS
DECODED OUTPUT0 CHARS

About URL Decoding

URL encoding (percent encoding) replaces characters that are not safe in URLs with a percent sign followed by two hex digits. This tool uses decodeURIComponent() to convert these sequences back to readable text. Common encodings: %20 = space, %3D = =, %26 = &.

How to Use the URL Decoder

  1. Paste the percent-encoded URL or query string you want to decode into the input field.
  2. Adjust any available options shown - the output updates as you type.
  3. The result updates instantly - no submit button required for most operations.
  4. Click Copy or Download to take the output to your next step.

URL Decoder allows you to revert percent-encoded strings back into readable human text. This free online percent decoding tool is perfect for unwrapping query parameters, analyzing tracking links, or recovering special characters that have been escaped for the web. It uses the industry-standard decodeURIComponent function to ensure that all reserved characters and multi-byte UTF-8 sequences are handled with 100% accuracy.

Advanced URL String Decoding

This URI unescape tool is designed to handle common web encoding variants, including the + as space convention used in HTML form submissions. If you are dealing with nested data, the tool can also detect and process double-encoded strings to reveal the original source text. All operations are executed directly in your browser, ensuring that your sensitive links and data never leave your machine.

Frequently Asked Questions

What’s the difference between %20 and + for spaces?

%20 is the universal percent-encoding for a space and works everywhere. + is a space only in application/x-www-form-urlencoded (HTML form bodies and query strings). Toggle the form-encoding option to switch behaviour.

How does the tool handle UTF-8 characters like é or 😀?

It uses the browser’s decodeURIComponent under the hood, which correctly assembles multibyte UTF-8 sequences (%C3%A9 → é, %F0%9F%98%80 → 😀) into proper Unicode code points.

Why am I seeing "URI malformed" errors?

That happens when a % is followed by something other than two hex digits, or when the byte sequence isn’t valid UTF-8. The original string is left in place and an error message appears so you can spot the bad position.

Is the URL sent to any server?

No - decoding happens entirely in your browser via the built-in decodeURIComponent.

Whether you are auditing a log file or debugging a redirect, this free online URL decoder provides the clear results you need.