URL Decoder - Decode Percent Encoding

Decode percent-encoded URLs and query strings. Convert %20 and other escape sequences back to readable text. Fast, private, works offline.

Drop a text file here

or paste encoded text below

Encoded URL or Text

decodeURIComponent (recommended)

decodeURI

Decoded Output

URL Parser - Break Down URLs into Compon…

View all Url encoders →

Frequently Asked Questions

URL decoding converts percent-encoded characters (like %20 for space, %26 for &) back to their original form. It reverses URL encoding/percent encoding to make URLs and query strings human-readable again.

decodeURI preserves encoded reserved URL characters (:, /, ?, &, =) to maintain URL structure. decodeURIComponent decodes everything including reserved characters, making it suitable for query parameter values and form data.

Use decodeURIComponent for individual query parameters, form values, or any user data embedded in URLs. Use decodeURI only for complete URLs where you want to preserve the URL structure characters.

URL encoding makes characters safe for transmission in URLs - it's reversible by design and provides no security. Encryption protects data confidentiality using keys. Anyone can decode a URL instantly.

Yes. UTF-8 encoded characters (like %C3%A9 for é, %E2%9C%93 for ✓, or multi-byte emoji sequences) decode correctly to their Unicode representations, supporting all languages and symbols.

Malformed percent sequences (incomplete like %2, invalid hex like %ZZ) will show an error. Ensure the input contains valid %XX sequences where XX is a hexadecimal value (0-9, A-F).

Yes. Some systems double-encode URLs (like %2520 for space). Run the decoder twice to remove both encoding layers. Each pass removes one layer of percent encoding.

In query strings, + often represents a space (legacy form encoding). This tool uses standard JavaScript decoders which don't automatically convert + to space - you may need to replace + with %20 first.

Yes, URL encoding/decoding is fully reversible. Encoding then decoding returns the original text. However, some characters have multiple valid encodings (space can be %20 or +), so re-encoding might differ.

Yes. All decoding happens in your browser using JavaScript's built-in decodeURI and decodeURIComponent functions. No data is sent to any server - your content stays completely private.

Related Tools