Using the wrong encoding mode
Use component encoding for query values and path segments. Use full URL encoding only when URL separators such as /, ?, and # must stay readable.
URL Encoder and Decoder Online | Query String Percent Encoding
EncodingRuns in Your Browser (No Uploads)
Encode URL components to safe percent-encoded text or decode encoded URLs back to readable form. Built for query strings, redirects, API parameters, UTF-8 text, and local browser debugging.
Loading…
What to do next
Continue with a related workflow or open the next tool that usually follows this task.
Workflow guide
Base64 decode an API payload
Use this workflow when an API response, webhook, cookie, or configuration value contains Base64 text that needs to be inspected before debugging.
OpenRelated toolHTTP Header Parser | Inspect Request & Response Headers
Parse raw HTTP request or response headers into grouped, normalized debugging output.
OpenHow to Use This Tool
- 1
Select Encode or Decode mode.
- 2
Enter your URL, text, or query string in the input box.
- 3
Choose encoding type: Component (encodeURIComponent) for parts, or Standard (encodeURI) for full URLs.
- 4
See instant results in Live mode or click the button in Manual mode.
- 5
Copy or swap input/output as needed.
When to Use This Tool
Query String Parameter Encoding
Safely encode user input before placing it in query values so spaces, ampersands, equals signs, and Unicode characters do not change parameter boundaries.
API Request Construction
Build REST API URLs with encoded path segments and query values before testing requests or sharing examples.
Redirect and Log Debugging
Decode percent-encoded URLs from server logs, tracking links, redirect chains, and email clients.
International URL Handling
Prepare URLs containing Korean, Japanese, Chinese, accents, or emoji for reliable copying and embedding.
Common Mistakes
Double-encoding percent signs
Encoding a value twice turns %20 into %2520 and can break redirects, signed URLs, OAuth callbacks, and API parameters.
Expecting URL encoding to encrypt data
URL encoding only makes text URL-safe. It does not hide data or protect secrets in links.
Examples
Encode a query parameter value
Encode a raw query value before appending it to a URL so spaces, ampersands, and Unicode text do not break the query string.
Input
JSON formatter & validatorOutput
JSON%20formatter%20%26%20validatorDecode a redirect URL from logs
Turn percent-encoded log output back into a readable URL while debugging redirects, analytics links, or OAuth callbacks.
Input
https%3A%2F%2Fexample.com%2Fsearch%3Fq%3D%EC%95%88%EB%85%95%26page%3D1Output
https://example.com/search?q=안녕&page=1Understanding URL Percent Encoding
Percent encoding replaces unsafe URL characters with %HH hexadecimal byte values, as defined in RFC 3986.
encodeURIComponent-style encoding is safest for query parameter values and path segments.
Full URL encoding keeps structural characters like :, /, ?, and # intact.
UTF-8 encoding preserves international text and emoji across browsers, APIs, and logs.
Frequently Asked Questions
Q.What’s the difference between encodeURIComponent and encodeURI?
A. encodeURIComponent encodes nearly all special characters for URL parts like query values and path segments. encodeURI keeps reserved characters such as :, /, ?, and # so a full URL remains structurally readable.
Q.Why are spaces sometimes %20 and sometimes '+'?
A. %20 is the official standard per RFC 3986. Older web forms sometimes use '+'. This tool encodes spaces as %20 and decodes both %20 and + back to spaces.
Q.Can it handle international text and emojis?
A. Yes—UTF-8 encoding supports all Unicode characters, including emojis, Korean, Japanese, and Chinese.
Q.Is URL encoding a form of encryption?
A. No. URL encoding only makes text safe to place in a URL. It does not hide values, protect secrets, or replace HTTPS.
Q.How do I fix double-encoded URLs?
A. Decode once first. If you still see %25 sequences where percent signs should be, the value may have been double-encoded. Avoid repeatedly encoding the same parameter.
Related workflow guides
Use these focused guides when you need a practical workflow before opening the tool.
Workflow guide
Base64 decode an API payload
Use this workflow when an API response, webhook, cookie, or configuration value contains Base64 text that needs to be inspected before debugging.
Workflow guideDecode a JWT safely before debugging authentication
Use this workflow when a login, API request, or permission check fails and you need to inspect token claims before changing auth code.
Workflow guideCreate a QR code for any link
Use this workflow when a URL needs to move from paper, a slide, a package, or a physical sign into a phone camera quickly.
Workflow guideEncode URL query parameters safely
Use this workflow when a link, redirect URL, webhook callback, or API request fails because a query parameter contains reserved characters.
Workflow guideInspect HTTP response headers before debugging APIs
Use this workflow when a browser request, API response, redirect, or CDN cache behaves differently than expected and you need a clean header-level view first.
Related Tools
Explore more developer tools
Browse All Tools