By YiyaoPublished Updated
Read an encoded value before you use it
Paste a percent-encoded value and choose how it should be interpreted. Use URI component for a path segment or a separately encoded value. Use Form value when a plus sign represents a space in form-encoded data. Select Decode to inspect one decoding pass.
Use the output to understand a value before placing it into a request or configuration. Decoding a complete URL can turn encoded characters into separators, so copy the result only after checking which component you intend to use.
Choose the correct decoding mode
Percent escapes represent encoded bytes. In a UTF-8 value, several escaped bytes may combine into one character. The selected mode controls how a literal plus sign is treated before percent decoding.
| Mode | Input example | Decoded result | Use it for |
|---|---|---|---|
| URI component | red+chair%20sale | red+chair sale | A separately encoded component where + is a literal character |
| Form value | red+chair%20sale | red chair sale | A form-encoded value where + represents a space |
| Either mode | %2B | + | An explicitly percent-encoded plus sign |
| Either mode | %252F | %2F | One decoding pass; the remaining escape is not decoded automatically |
Keep URL boundaries intact
A query value can contain characters that also have structural meaning in a URL. For example, an encoded ampersand may belong inside a search term rather than between two query parameters.
Consider the query value red%26blue. Its decoded text is red&blue. To send that same value again, use your request client's parameter builder so the ampersand is encoded as part of the value. Pasting the decoded text directly into a full URL can change how the query is parsed.
When inspecting a full address, identify the scheme, host, path and query first. Decode the component you need rather than treating the complete address as one interchangeable string.
Handle invalid input deliberately
An incomplete percent escape or invalid UTF-8 sequence cannot be decoded with this mode. Check for a truncated value, a copied percent sign or a source that uses a different character encoding.
Keep the original value while investigating the problem. Decode one layer at a time only when the producing system's encoding behavior is known. Repeatedly decoding until the output looks familiar can change the meaning of the original data.
| Condition | Message shown | Next step |
|---|---|---|
| Empty input | Enter encoded text to decode. | Paste a value or use a sample |
| Malformed escape or invalid UTF-8 | Unable to decode: check percent escapes and UTF-8 input. | Check the original source for truncation or encoding differences |
| More than 100000 input characters | Use 100000 characters or fewer. | Inspect a smaller component |
| Copy unavailable or denied | Copy was unavailable. Select the output and copy it manually. | Keep the result selectable |
Use a safe request example
A public-data workflow may return a search filter such as product%20name%3Ddesk%20lamp. Decoding produces product name=desk lamp, which helps explain the stored value. Keep the original alongside the decoded view when comparing logs or preparing a reproducible example.
For a new request, supply the intended parameter name and value through the client library rather than manually joining decoded fragments. Review the resulting URL and response before running a larger authorized job. Use synthetic values when sharing a debugging example.
Decoder questions
Why did + remain unchanged? URI component mode preserves a literal plus. Choose Form value only when the source uses plus signs for spaces.
Why did %252F become %2F instead of a slash? The tool performs one pass. A second layer requires a separate, deliberate decode.
Does decoding send a request to the address? No. The output is displayed as text; the decoder does not open the destination.
Should I paste a secret token? Use a redacted or synthetic example for troubleshooting. Keep credentials in their intended secure configuration workflow.
