Key takeaways
- Component mode protects separators inside one value; whole URI mode retains URI delimiters.
- The query parser treats plus signs as spaces and keeps repeated keys in order.
- Percent encoding is reversible representation, not encryption or a reason to trust a link.
The URL encoder decoder converts text to or from percent-encoded form and displays query parameters in a table. Use it when constructing one query value, inspecting an encoded path fragment or checking how repeated parameters appear in a link. The pasted address is treated as text and is never opened by the parser.
Choose the operation based on the part of the address you are handling. A full URI has structural punctuation, while a single value can contain that same punctuation as ordinary data. Preserving a separator and escaping a separator have different purposes; neither choice is universally correct for every input.
Before you start
Identify whether your input is plain text, an already encoded value or a whole address. Encoding an already encoded value escapes its percent signs again. That can be intentional when nesting values, but it can also create an unexpected extra encoding layer. Save a copy of the original text before experimenting with repeated transformations.
The two main modes follow the browser’s URI functions. Component mode pairs encodeURIComponent with decodeURIComponent. Whole URI mode pairs encodeURI with decodeURI. For exact behaviour, consult the ECMAScript URI handling definitions, checked 16 November 2026. The interface names both pairs so that the choice remains visible.
The separate query field is independent from the encode/decode field. Paste a query such as ?q=tea&page=2, or a full URL with a query. Query rows represent parsing, not a second encoded-output format. Changing one field does not silently overwrite the other, which makes side-by-side inspection possible.
Step by step with CrizaTools
- Open URL Encoder Decoder and choose Action as Encode or Decode.
- Choose Mode. Use Component for one value, and Whole URI when URI delimiters should retain their structural role.
- Paste the input into Text or encoded URI. The result updates automatically.
- Read any field error. A malformed escape must be corrected before a decoded result is available.
- Use Copy beside the encoded or decoded result.
- For inspection, paste a query or full address into Query string or full URL. Read the Key and Value columns under Query parameters.
- Check repeated keys, empty values and spaces before using the text in another system. The parser does not decide which repeated value a remote application will use.
Two worked examples
Example 1: a search value containing an ampersand. Choose Encode and Component, then enter tea & coffee. The output is tea%20%26%20coffee. The two spaces become %20, and the ampersand becomes %26, so it remains part of the value rather than acting as a query separator.
If this value belongs to a parameter named q, the relevant query text is q=tea%20%26%20coffee. Decode the encoded value in Component mode to recover the original text. In Whole URI mode, the ampersand is preserved because that mode allows URI delimiters; it is therefore inappropriate when this ampersand must stay inside one query value.
Example 2: repeated parameters and a plus sign. Paste ?name=Asha+Rao&tag=a&tag=b into the separate query field. The table contains three rows: name with value Asha Rao, tag with value a, and tag with value b.
The plus sign becomes a space under form query rules. Both tag rows remain visible in their original order. By contrast, using the standalone Component Decode action on Asha+Rao leaves the plus sign unchanged. To express a literal plus sign in a form-style query value, encode it as %2B. These are different decoding contexts, so inspect the result appropriate to your destination.
Limits and what to watch for
Each text field is limited to 10 MB, and the query table supports at most 1000 pairs. Very large strings can still take time to process or render. Use a smaller representative section when inspecting an unusually long query. The table is intended for readable inspection rather than bulk log analysis.
Malformed percent escapes, such as %ZZ, are rejected. Encoded bytes that do not form valid UTF-8 are also rejected. The query parser validates escapes before creating its table so that a malformed sequence is not silently replaced with another character. A partial result could hide the very problem you are trying to diagnose.
Queries follow the WHATWG URL standard, including form-style handling of plus signs. A raw # ends the query portion; an encoded %23 can remain inside a value. A full URL is parsed locally to obtain its query, without fetching the address or putting it in browser history. Source checked 16 November 2026.
Encoding does not encrypt data or establish whether a link is trustworthy. The converted text remains reversible. Keep credentials and other sensitive values out of shared links, tickets and screenshots. The tool itself keeps inputs in browser state and does not append them to its own page address or analytics events.
Common mistakes
- Encoding a whole address with Component mode when only one value needed escaping.
- Using Whole URI mode for a value containing
&or=. - Expecting standalone decodeURIComponent behaviour to turn
+into a space. - Decoding the same value repeatedly without checking its original encoding layer.
- Assuming a repeated key is equivalent to one comma-separated value.
- Treating readable decoded text as proof that a link is safe to visit.
Questions and answers
Which mode should encode an individual query value?
Choose Component mode. It escapes structural punctuation inside that value so that the punctuation does not become a query delimiter when the value is inserted into an address.
Why does whole URI decoding keep some percent escapes?
decodeURI preserves encoded reserved delimiters whose decoded form could change URI structure. If you are decoding the contents of a single parameter, choose Component mode instead and inspect the resulting value.
Does the table combine repeated keys?
No. Each occurrence gets its own row, preserving order. The receiving application may use the first value, the last value or a list; consult that application’s rules before interpreting repeated keys.
What should I do when a percent escape is invalid?
Return to the original source if possible and check whether the string was truncated or encoded incorrectly. Do not guess missing bytes from the displayed text. Correct the input and let the tool validate it again.
Does pasting a URL send a request to that site?
No. The parser reads the string locally. It does not navigate to the address, request its content or test whether it exists. Copying a result also does not open the destination.
Sources
- ECMAScript: URI handling functions, checked 16 November 2026.
- WHATWG URL: URLSearchParams, checked 16 November 2026.
Inspect strings with URL Encoder Decoder and structured request bodies with JSON Formatter.
Free tools for this
PDF & image
URL Encoder Decoder
Encode or decode URI components and whole URLs, catch invalid percent escapes and inspect query parameters in a table.
PDF & image
JSON Formatter
Format, validate and minify JSON in your browser. Shows the line and column of any error, sorts keys and copies or downloads the result.
PDF & image
Hash Generator (SHA-256 etc.)
Hash text or files with SHA-1, SHA-256, SHA-384 and SHA-512 using Web Crypto.