URL Encoder / Decoder
Encode special characters or make encoded URLs readable again.
Input
Whole-URL operations preserve reserved delimiters. Query parsing treats + as a space and preserves repeated keys as pairs. Component decoding keeps a literal + unchanged.
Result
Understand your results
For developers preparing URL components and inspecting query strings.
encodeURIComponent encodes a single value, including reserved separators. encodeURI preserves whole-URL delimiters such as :, /, ?, and &. Their decode counterparts differ too: decodeURI preserves encoded reserved delimiters. Query parsing and generation use form-style encoding, where + represents a space, and return ordered string pairs to preserve duplicate keys.
How to use this tool
- Choose the exact operation before pasting your text.
- For query generation, supply a JSON array of [key, value] string pairs. Query parsing accepts a query string or full HTTP(S) URL.
- Run the operation, review the result, then copy or download it. Malformed encodings show an error while leaving your original input untouched.
What the observations mean
Percent encoding represents encoded bytes with % and hexadecimal digits. encodeURI preserves whole-URI separators, while encodeURIComponent encodes a single component including reserved separators. Query helpers use form conventions and ordered pairs.
Worked example
Encode a single value before placing it inside a URL query.
Component input: tea & coffee
Encoded component: tea%20%26%20coffeeComponent encoding protects the ampersand so it remains part of the value. Query parsing instead follows form-style rules, where + represents a space; repeated keys can retain multiple values.
Limits and processing
Whole-URI encoding and component encoding preserve different separators. Decode only the intended layer; malformed percent escapes can fail. Transformations stay in the browser and do not test a destination server.
Common problems and practical fixes
- A value became two parameters
- Encode the value as a component so an embedded & stays data rather than a query separator.
- Plus signs changed
- URLSearchParams interprets + as a space; a literal plus becomes %2B. decodeURIComponent does not apply the same plus-to-space conversion.
- Decoding fails or produces % escapes
- Check malformed percent sequences and UTF-8. Repeated encoding can produce %25; decode only the layer you understand.
Best practices
Preserve repeated query keys using pairs. Encoding is reversible representation, not encryption or a destination safety check, and the tool never fetches entered URLs.
Practical tips
- Encode a query value as a component before adding it to a hand-built URL. Do not encode the entire URL as one component.
- Repeated encoding can turn % into %25. Only decode data whose encoding you understand.
- The tool does not navigate to or fetch entered URLs. Never include secrets in URLs that will be shared publicly.
Frequently asked questions
Practical answers for using the URL Encoder / Decoder.
Why does a plus sign behave differently?
decodeURIComponent leaves + unchanged. URLSearchParams follows query form conventions and treats + as a space; %2B represents a literal plus.
Are repeated query keys preserved?
Yes. Parsing returns an array of pairs, and generation accepts pairs, so repeated names are not overwritten.
Can decoding fail?
Yes. Incomplete percent escapes, invalid UTF-8 byte sequences, and malformed Unicode cannot be decoded reliably. The error is shown without changing the input.