URL Encoder & Decoder
Encode or decode URL text and query values instantly with browser-native percent encoding.
Input
Use component mode for query parameter values. Full URI mode preserves URL separators such as : / ? & =.
Result
URL encoding
Percent encoding converts characters that may have special meaning in a URL into a safe representation. Spaces in a component, for example, become %20.
Component vs full URL
encodeURIComponent is usually appropriate for individual query values. encodeURI is intended for a full URI and leaves structural separators intact.
Runs locally
Encoding and decoding happen entirely in your browser.
How to use this tool effectively
Percent-encode text so it can safely appear inside URL components, or decode percent-encoded values back into readable text. This is especially useful for query parameters, redirect URLs, search terms and API requests.
Common uses
- Encode spaces, ampersands and non-ASCII characters inside a query parameter.
- Decode a copied tracking URL to understand the original parameter text.
- Prepare values for links generated by JavaScript or API clients.
- Compare full URL encoding with component-level encoding when debugging requests.
Example: encode a search query
coffee & tea
coffee%20%26%20tea
The ampersand must be encoded when it is part of a value; otherwise it could be interpreted as a separator between query parameters.
Common mistakes to avoid
- Do not encode an entire URL with a component encoder if you need to preserve separators such as : / ? and &.
- Avoid double-encoding values that already contain percent escapes such as %20.
- Remember that plus signs may represent spaces in form-style query strings but not in every URL context.
Encoding and decoding use browser-native functions. The text you enter is processed locally and is not sent to KRIYANO.
Frequently asked questions
What is percent encoding?
It represents characters with a percent sign followed by hexadecimal bytes, allowing reserved or non-ASCII characters to be carried safely in URL components.
Should spaces become %20 or +?
General URL component encoding commonly uses %20. The plus sign is a convention used by application/x-www-form-urlencoded data and many query-string implementations.
Why does decoding sometimes fail?
Malformed percent sequences, such as a lone % or incomplete hexadecimal escape, are not valid encoded input and can cause a decoder to reject the value.