URI Component Decoder
URI Component Decoder applies decodeURIComponent to the complete input. Unlike full-URL decoding, it can turn encoded reserved delimiters such as %2F, %26, and %3D back into literal characters because the input is assumed to be one isolated component. Malformed percent sequences or invalid UTF-8 fail rather than returning a partial conversion.
Runs locally — files stay on your deviceWhy does %2F become a slash here?
An isolated component decoder does not preserve full-URL structural delimiters.
Decode before interpretation, then validate
Percent decoding restores characters, including delimiters that may acquire special meaning if the output is later inserted into a URL without re-encoding.
How it works
decodeURIComponent validates percent triplets and decodes their UTF-8 byte sequences in one operation.
Key concepts
Reserved bytes decode
Output can contain slash, ampersand, equals, or hash.
Plus remains plus
General URI decoding is not HTML form decoding.
When to use it
- Read one encoded query value.
- Decode one path segment for display.
- Reverse URI Component Encoder output.
When not to use it
- Do not decode an entire URL when structure must remain protected.
- Do not execute or route on unvalidated decoded data.
- Do not expect plus to become a space.
Worked examples
Segment slash
- Input
a%2Fb- Expected output
a/b
The encoded delimiter is restored.
Query data
- Input
tea%20%26%20mint- Expected output
tea & mint
Both space and ampersand decode.
Malformed percent
- Input
%ZZ- Expected output
Error
ZZ is not a hexadecimal byte.
Common mistakes
Decoding a complete URL
Protected delimiters can change interpretation. Correction: Use URL Decoder.
Expecting plus conversion
Plus is unchanged. Correction: Use a form-urlencoded parser.
Trusting output
Decoded traversal or control characters may matter downstream. Correction: Validate for the destination.
Best practices
- Decode only at a known component boundary.
- Validate before filesystem, routing, or database use.
- Avoid repeated decoding.
Related operations and differences
URI Component Encoder
Choose URI Component Encoder when you need to encode a query value, path segment or other URL component.; use URI Component Decoder specifically for url component decode.
Base64 Decoder
Choose Base64 Decoder when you need to decode Base64 into readable text.; use URI Component Decoder specifically for url component decode.
Base64 Encoder
Choose Base64 Encoder when you need to encode text as Base64 in your browser.; use URI Component Decoder specifically for url component decode.
Binary to Text
Choose Binary to Text when you need to decode 8-bit binary groups into text.; use URI Component Decoder specifically for url component decode.
Hex to Text
Choose Hex to Text when you need to decode hexadecimal bytes into text.; use URI Component Decoder specifically for url component decode.
HTML Escape
Choose HTML Escape when you need to escape HTML-sensitive characters.; use URI Component Decoder specifically for url component decode.
Limitations and privacy
- No form-urlencoded plus handling, full URL parsing, recursive mode, partial recovery, or destination validation.
The entered value is transformed locally in this browser and is not sent to the Toolbox server.
Copying or pasting sensitive output into another service is a separate disclosure decision.
Frequently asked questions
Does %26 become &?
Yes.
Will plus become a space?
No.
Does malformed input fail?
Yes.
Can decoding change URL meaning?
Yes, if output is inserted without correct component encoding.