URL Encoder & Decoder Online
Percent-encode or decode URLs
Como usar Codificador/Decodificador de URL
- 1
Paste your text or URL
Enter a URL to decode or text to encode.
- 2
Click Encode or Decode
The result appears instantly.
- 3
Copy result
Use the copy button to grab the encoded or decoded value.
Perguntas frequentes
Is my data safe?
What characters get encoded?
What is the difference between %20 and + for spaces?
Why do I see %25 in my encoded URL?
Can I encode an entire URL or only parameters?
Saiba mais
O que é URL Encode/Decode?
Percent-encode special characters for safe use in URLs and query strings, or decode percent-encoded URLs back to human-readable text. Essential for debugging API query parameters, constructing redirect URIs, inspecting encoded form data, and understanding how browsers handle special characters in addresses. Follows RFC 3986 encoding rules. Supports both encodeURIComponent (for individual parameters) and encodeURI (for full URLs). Everything runs locally in your browser — no server, no sign-up.
Por que usar URL Encode/Decode?
- Instant encode/decode — results appear immediately without any button click or page reload.
- RFC 3986 compliant — correctly identifies which characters must be encoded versus which are safe in URLs.
- Useful for debugging API requests — decode complex encoded URLs to see the actual query parameter values.
- Handles full URLs or individual components — choose the encoding mode that matches your use case.
- Completely private — your URLs and query strings never leave your browser.
Casos de uso de URL Encode/Decode
API query string construction
Encode parameter values before appending them to API URLs. Spaces become %20 or +, ampersands become %26 — ensuring the query string parses correctly on the server.
Redirect URI debugging
OAuth flows encode redirect URIs as query parameters. Decode a login URL to inspect the redirect_uri value and verify it matches your registered callback.
Form data inspection
HTML form submissions encode field values as application/x-www-form-urlencoded. Decode form POST bodies to inspect the actual values being sent.
Webhook URL debugging
When a webhook fails, inspect the encoded URL in server logs by decoding it to see the original parameter values that were sent.
Dicas e boas práticas
- 💡Use encodeURIComponent for individual query parameter values. Use encodeURI for an entire URL — encodeURI preserves characters like '/', '?', and '&' that have structural meaning in URLs.
- 💡Spaces can be encoded as either %20 (RFC 3986) or '+' (application/x-www-form-urlencoded). APIs vary — check the API's documentation to confirm which format it expects.
- 💡If you see %25 in an encoded URL, it means a literal '%' was encoded. Double-encoding (encoding an already-encoded URL) is a common mistake that causes %20 to become %2520.
- 💡When building API query strings manually, always encode each parameter value individually before joining them with '&'. Never encode the '&' separator itself.
Como funciona
Encoding uses JavaScript's encodeURIComponent(), which encodes all characters except A-Z, a-z, 0-9, -, _, ., !, ~, *, ', (, and ). This follows the 'unreserved characters' definition in RFC 3986. Decoding uses decodeURIComponent(), which reverses percent-encoding including %20, %2F, %3A, and all other percent-encoded sequences. Invalid percent sequences (e.g., %ZZ) are caught and reported as errors. The tool encodes in UTF-8, matching what all modern browsers use when constructing URLs.