URL Encoder & Decoder
Encode special characters for safe URL transmission and decode percent-encoded strings. Free and instant.
Input Text
Characters
0
Words
0
Output
Converted text will appear here
Characters
0
Words
0
Why use our URL Encoder/Decoder?
Encode & Decode URLs
Percent-encode special characters for query strings or decode encoded URLs back to readable text.
RFC 3986 Aware
Handle spaces, ampersands, unicode, and reserved characters the way browsers and APIs expect.
Runs in Your Browser
Encode redirect URLs, OAuth parameters, and API query strings without exposing them to a server.
What is URL Encoding?
URL encoding (percent encoding) replaces unsafe or reserved characters in URIs with a percent sign followed by two hexadecimal digits. For example, a space becomes %20 and an ampersand becomes %26. Browsers and HTTP clients encode query parameters automatically, but developers often need manual encoding when building fetch URLs, OAuth redirect URIs, or deep links.
Our free online URL encoder and decoder converts plain text to percent-encoded form and reverses the process for inspection. Use it when debugging broken links, constructing API requests, decoding analytics parameters, or verifying that special characters survive transit through proxies and CDNs.
URL Encoder Features
- Encode:Convert spaces, unicode, and reserved characters to percent-encoded sequences.
- Decode:Transform %XX sequences back into readable UTF-8 text.
- Component encoding:Safe for query parameter values, path segments, and fragment identifiers.
- Copy & download:Copy encoded or decoded output or save it as a text file.
- Live stats:Track character counts for input and output as you work.
- Privacy:All encoding and decoding happens locally — URLs are never uploaded.
Common Use Cases
API Query Strings
Encode filter values, search terms, and JSON fragments before appending them to REST endpoints.
OAuth & SSO Redirects
Properly encode redirect_uri, state, and scope parameters for authorization server compliance.
Analytics Debugging
Decode UTM parameters and campaign tags from long tracking URLs in marketing reports.
Deep Link Construction
Build mobile app deep links with encoded titles, descriptions, and referral codes.
Email & Newsletter Links
Verify that merge tags and special characters survive encoding in ESP-generated href attributes.
Log & Error Triage
Decode percent-encoded paths in 404 logs, WAF blocks, and CDN access records.
How to Use the URL Encoder/Decoder
Paste Your Text or URL
Enter a plain string to encode or a percent-encoded URL to decode.
Choose Encode or Decode
Click encode to escape special characters or decode to reveal the original readable text.
Review the Output
Confirm percent sequences, spaces, and unicode characters look correct for your use case.
Copy or Download
Copy the result into your API client, HTML template, or config file.
Benefits of Using a URL Encoder/Decoder
Fix Broken Query Strings
Catch unencoded ampersands and spaces that cause parsers to split parameters incorrectly.
Readable Debugging
Decode opaque tracking URLs into human-readable key-value pairs for faster triage.
Standards-Compliant Output
Produce encoding that matches encodeURIComponent behavior in JavaScript environments.
No Server Exposure
OAuth secrets and internal redirect URLs stay on your device during encoding.
Quick Ad-Hoc Encoding
Skip opening devtools or writing one-liners when you need a single encoded value.
Completely Free
Unlimited encode and decode operations with no registration.
URL Encoding Tips
- •Encode components, not full URLs: Encode individual query values or path segments — encoding an entire URL can double-encode the scheme and host.
- •Spaces become %20: Some legacy systems accept + for spaces in query strings; modern APIs prefer %20.
- •Unicode is UTF-8 encoded: Non-ASCII characters encode as multiple %XX bytes — verify the decoded output matches expectations.
- •Reserved characters: Characters like ?, #, &, and = have special URI meaning — encode them inside values, not as delimiters.
- •Double-encoding bugs: If you see %2520, the value was encoded twice — decode once and re-encode at the correct layer.
- •Pair with slug generator: Create a URL-safe slug first, then encode it if embedding in a query parameter.
Start Encoding and Decoding URLs Now
Whether you are building API query strings, debugging OAuth redirects, or decoding analytics parameters, our free URL encoder and decoder handles percent encoding instantly in your browser.
Scroll up, paste your input, and convert locally with no registration required. Completely free, and your URLs stay 100% private on Quick Note.
Related tools
Frequently Asked Questions
What is URL encoding?
URL encoding (percent encoding) replaces characters that are unsafe or reserved in URIs with % followed by two hexadecimal digits. For example, a space becomes %20.
When should I encode a URL?
Encode query parameter values, path segments, and fragment data that contain spaces, unicode, ampersands, or other special characters before sending them in HTTP requests or links.
What is the difference between encode and decode?
Encode converts readable text into percent-encoded form safe for URLs. Decode reverses %XX sequences back into the original readable string.
Should I encode the entire URL?
Usually no. Encode individual components (parameter values, path segments) rather than the full URL including the scheme and hostname, which avoids double-encoding issues.
Is my URL sent to a server?
No. Encoding and decoding run entirely in your browser. Your input never leaves your device.
Why does + sometimes represent a space?
In application/x-www-form-urlencoded query strings, + is historically treated as a space. encodeURIComponent uses %20 instead, which is preferred in modern APIs.
Can I encode unicode characters?
Yes. Unicode text is UTF-8 encoded first, then each byte is percent-encoded. Decoding restores the original unicode characters.
Is the URL encoder/decoder free?
Yes. It is completely free to use with no registration, downloads, or hidden fees.