Practical usage guide
What this tool does
Percent-encoding represents characters as UTF-8 bytes written with %HH sequences. A URL component such as a query value has different reserved-character rules from a complete URL, so this page provides separate component and full-URL modes.
Encoding is contextual. A value safe inside a path segment may not be safe as a query value, and encoding an already encoded value can create %25 sequences that require another decoding pass.
Quick start
Choose component or full URL
Use Component for one query value, path segment, or fragment value. Use Full URL when separators such as :, /, ?, and & must remain structural.
Choose one encoding pass
Encode raw text once or decode one layer at a time. Keep the original value so accidental double encoding can be reversed.
Verify reserved characters
After conversion, inspect &, =, ?, #, /, +, and % because changing their role can alter how a server interprets the URL.
Common use cases
Debug query parameters
Decode copied analytics, redirect, or search parameter values into readable UTF-8 text.
Prepare a path or query value
Encode user-facing labels and identifiers before inserting them into a URL component.
Inspect nested redirect URLs
Decode one layer at a time to understand a URL embedded inside another query parameter.
Limitations and important notes
A plus sign is treated as a space in component decode
This matches common HTML form query behavior. If a literal + matters, encode it as %2B before decoding.
Malformed percent sequences fail
A bare % or incomplete byte sequence is not valid percent-encoding and will produce an error instead of a partial guess.
This is not a URL validator or normalizer
The tool does not resolve relative URLs, remove tracking parameters, check a host, or determine whether a destination is safe.