What this tool does
URL encoding problems usually appear in redirects, callback parameters or unreadable query strings. This page helps you convert values safely so you can see exactly what is being sent and received.
- Encodes special characters in URLs and query strings using percent-encoding so they travel safely across HTTP requests.
- Decodes percent-encoded strings back to human-readable form for debugging redirects, callback parameters and API queries.
- Handles both full URLs and individual query parameter values, making it practical for OAuth flows, analytics debugging and log inspection.
How to use it
- 1
Choose Encode when you need to make a raw string URL-safe, or Decode when you have a percent-encoded value to inspect.
- 2
Paste the URL or parameter value into the input field.
- 3
Review the output and verify the result looks correct for the context you are working in.
- 4
Copy the encoded or decoded value into your request, config, or documentation.
Example
A developer copies a redirect URL from an OAuth flow that contains an encoded callback address and decodes it to verify the destination before testing further.
https%3A%2F%2Fapp.example.com%2Fcallback%3Fsession%3Dabc123https://app.example.com/callback?session=abc123Use cases
- Inspecting callback URLs during OAuth or SSO debugging.
- Encoding query parameter values before sharing links or testing API requests.
- Decoding percent-encoded URLs copied from logs, analytics tools or server traces.
Common mistakes
Encoding an already-encoded URL
Double-encoding turns percent signs into %25, which breaks the final URL in unpredictable ways. Decode first if the string already contains percent signs.
Encoding the full URL instead of just the parameter value
The slashes and colons in a URL have meaning. Usually only the query parameter values need to be encoded, not the entire string.
Forgetting that spaces can appear as + or %20
Both forms are valid in different contexts. Query strings often use + while paths and JSON expect %20.
FAQ
When should I encode a URL vs a query parameter?
Encode individual parameter values before placing them inside a URL. Encoding the whole URL is usually incorrect because structural characters like slashes and question marks have specific meaning.
What is the difference between + and %20 for spaces?
Both represent a space but in different contexts. Query strings traditionally use + while path segments and most modern APIs prefer %20.
Does this tool send my URLs anywhere?
No. Encoding and decoding happen locally in the browser.
Can I use this for OAuth callback debugging?
Yes. It is useful for decoding redirect URIs and callback parameters that arrive percent-encoded during OAuth or SSO flows.
Why does my encoded URL look different from what the browser shows?
Browsers often decode URLs for display while keeping the encoded version in the actual request. The underlying encoded form is what matters for servers and APIs.
Privacy and security
- Encoding and decoding happen locally in the browser.
- No query string or URL is uploaded to a third-party service.
- That is useful when links include internal paths, tokens or debugging parameters.
Related tools
Related tools for the next step in the same workflow:
Next step
Encode or decode the value locally, then continue with related text and debugging tools if the request flow still needs inspection.