URL Encode and Decode – Safe URL and Query Handling
Encode and decode URLs, components, and query parameters with precision. Supports plus (+) spaces for form-style encoding, tolerant decoding, and quick query parsing.
What is URL encoding, and when should I use it?
URL encoding converts characters that are unsafe in URLs into percent-encoded sequences (like %20 for a space) so they can be transmitted reliably.
Use it when: - Adding query parameters (e.g., name=John Doe → name=John%20Doe). - Building URLs programmatically. - Ensuring data survives across redirects, forms, and API calls.
What is the difference between encodeURI and encodeURIComponent?
Use encodeURI for full URLs—it preserves reserved characters like /, :, ?, and & so the URL structure stays intact. Use encodeURIComponent for parts of a URL (like a query value) because it encodes almost all non-alphanumeric characters.
Examples: - encodeURI("https://site.com/a?b=c&d=e") → "https://site.com/a?b=c&d=e" - encodeURIComponent("a&b=c d") → "a%26b%3Dc%20d"
Why do some encoders use plus (+) for spaces?
In application/x-www-form-urlencoded (used by HTML forms), spaces are encoded as + instead of %20.
Examples: - Form-style: "hello world" → "hello+world" - Standard percent-encoding: "hello world" → "hello%20world"
This tool lets you use + when encoding and treats + as a space when tolerant decoding is enabled.
What is “tolerant decoding,” and when should I enable it?
Tolerant decoding helps when input contains mixed or partially encoded data. The tool first tries decodeURI (safer for full URLs) and falls back to decodeURIComponent if needed. It also handles + as a space.
Enable it if you are unsure how the text was encoded or you receive user-generated/legacy URLs. Disable it when you need strict validation.
How do I parse query parameters from a URL?
Choose “Parse Query Parameters,” then paste a full URL or a raw query string. The tool extracts keys and values and shows them line by line.
Example: https://example.com/?a=1&b=two%20words →
a=1
b=two words