Decode URL-encoded text online when a query value or copied link contains percent escapes and you want to read the underlying characters. This decoder applies decodeURIComponent to the pasted string, making it useful for developers debugging request parameters, support staff examining a sample, and learners exploring URL encoding. It treats the entire input as one encoded component; it is not a browser navigation tool, a URL inspector, or a request sender. The decoded result should be interpreted in the context in which the original string was created.
Paste the encoded value into “Paste URL-encoded text,” then select “Decode URL.” For example, Hello%20World%21 decodes to Hello World!. The action is disabled when the field is empty. The result is shown as “Decoded Text,” with shared output options and the configured filename decoded.txt. If decoding throws, the component displays “Invalid URL-encoded string” and clears the previous output. Changing the input clears the error, and Clear resets input, result, and error state together.
The helper calls decodeURIComponent directly. It decodes percent-encoded UTF-8 sequences as supported by that browser function and does not expose a character-set option, plus-as-space mode, or automatic URL parsing. A plus sign is not universally treated as a space by component decoding; that behavior belongs to certain form-encoding conventions. A malformed percent triplet or invalid UTF-8 sequence can throw an error. When the input is an entire address, decoding every component together can change its structure or meaning, so parse it first and decode only the value that needs inspection.
For a practical debugging example, copy a query value such as q=green%20tea from a URL, isolate the value after the equals sign, and decode that component to see green tea. Do not include surrounding URL delimiters unless you intend to decode them as literal text. If the source uses application/x-www-form-urlencoded rules, check whether plus represents a space and use a form-aware parser for an exact interpretation. The URL Parser can show a full address's query pairs, while this page focuses on turning percent-escaped component text back into readable characters.
Decoded text is not made safe just because it is readable. It may contain HTML, script-like text, credentials, or control characters; do not execute or render untrusted output as code. Percent-decoding is not decryption, authorization, malware scanning, or link reputation checking. If a decode error occurs, verify the original was not truncated and check each percent sign has two hexadecimal digits; avoid replacing escapes manually unless you understand the sender's encoding convention. Keep the original value alongside any decoded interpretation for reproducibility.
The client component stores the input, output, and current error locally and invokes the decoder directly; it does not make a conversion request in this component. This describes this code path only and is not a site-wide privacy promise. Use non-sensitive examples where possible and follow your organization's policy for production URLs or user data. For reverse conversion, the URL Encoder applies encodeURIComponent to a component, while the Base64 Decoder is appropriate only when the data is Base64 rather than percent encoded.
When a query has multiple fields, decode one parameter value at a time so delimiters remain meaningful. For instance, in q=red%20shoes&sort=price, the ampersand separates two parameters and should not be confused with part of the q value. The URL Parser can show those pairs from a complete absolute URL. Decoding the complete search string as one component may turn encoded delimiters into visible punctuation, but it does not tell you which characters were structural and which belonged to an original value.
Percent-decoded text can reveal whitespace, non-ASCII characters, or reserved punctuation that was less visible in the original address. This is useful for debugging, but the result might still require HTML escaping or another context-specific transformation before display in an application. URL decoding is not a general-purpose sanitization step. Preserve the encoded source and apply output encoding appropriate to the destination context to avoid mixing URL representation with HTML, SQL, shell, or JavaScript safety.
For a robust troubleshooting record, capture the complete original URL, isolate the parameter under investigation, note the expected decoding convention, and compare the decoded characters with the server's interpretation. If a plus sign appears, determine whether the source uses form encoding rather than assuming it is a literal plus or a space. The helper does not expose a plus-to-space switch. For that specific format, use a parser that explicitly implements application/x-www-form-urlencoded behavior.