Debug query parameters
Decode a copied query value to understand what was actually sent to an API or page.
Free browser tool
URL Encoder and Decoder
The URL encoder and decoder helps you safely convert text for use inside URLs, query strings, redirects, callback URLs, and API requests. Encoding turns reserved characters into percent-encoded sequences so a URL parser does not confuse data with URL syntax.
Decoding reverses percent-encoded text back into readable values. This is useful when debugging query parameters, OAuth redirects, tracking links, encoded paths, and API request examples.
URL encoder/decoder
Encode URL components or decode percent-encoded values.
What this tool does
URL encoding, also called percent encoding, protects text that appears inside URLs. Characters such as spaces, ampersands, question marks, and slashes can have special meaning in a URL, so they need to be encoded when they are part of a value rather than the URL structure itself.
This tool is useful when debugging query parameters, OAuth redirect URLs, webhook callback values, search filters, and API examples. Encoding creates a safe URL component, while decoding makes percent-encoded values readable again.
Common use cases
Prepare callback URLs
Encode redirect or callback values before placing them inside another URL.
Clean up API examples
Convert encoded examples into readable text for documentation and troubleshooting.
Example before and after
Reserved URL characters become percent-encoded so the value can be safely embedded in a query string.
Readable value
name=Ada Lovelace&role=engineerEncoded component
name%3DAda%20Lovelace%26role%3DengineerHow to use
- Paste the text or encoded URL component.
- Choose Encode URL or Decode URL.
- Copy the converted result.
Common errors
Encoding a whole URL as a component
Component encoding is correct for values, but full URLs sometimes need a more selective approach.
Double encoding
Encoding an already encoded value turns % into %25 and can break redirects or API calls.
Malformed percent sequences
A percent sign must be followed by valid hexadecimal characters when decoding.
Why use this tool
Debug query strings and callback URLs.
Create safe URL components for examples.
Read percent-encoded API parameters quickly.
Best practices
Encode values, not separators
Encode query parameter values before joining them with ? and & separators.
Decode for inspection
Decode copied URLs when debugging so you can read the actual value.
Keep redirects explicit
When nesting URLs, encode the nested URL as a parameter value.
Related tools
Related guides
URL encoding explained
URL encoding protects values inside URLs so reserved characters are interpreted as data instead of syntax.
Best practices for working with API responses
API responses are easier to debug when you validate syntax, format payloads, inspect errors, and compare changes deliberately.
How to read HTTP headers
HTTP headers carry metadata that explains how an API response should be parsed, cached, authenticated, and traced.
FAQ
Does this encode a full URL or a component?
It uses component-style encoding, which is safest for query parameter values and path segments.
What does %20 mean?
%20 is the percent-encoded form of a space character.
Can decoding fail?
Yes. A malformed percent sequence can cause decoding to fail.
Is the URL sent to a server?
The tool runs in your browser and does not require login, a database, or server-side processing.