URL Encoder and Decoder

Encode URL components

URLs can break when spaces, punctuation, Unicode characters, or reserved symbols are pasted into query strings. Encode values for URLs, or decode percent-encoded strings back into readable text.

Encode values before placing them inside query parameters, redirect URLs, tracking links, callback URLs, or API requests. Decode strings copied from logs, browser address bars, and analytics reports.

Examples

• Encode a search query before placing it after ?q=.
• Decode a copied URL parameter to see the original value.
• Check whether a redirect URL was encoded once or twice.

Best for

• Query strings, redirect URLs, callback parameters, and tracking links.
• API requests that include spaces, symbols, or Unicode text.
• Copied browser or analytics values that need to be readable again.

URL encoding examples

• hello world becomes hello%20world as an encoded URL component.
• a+b@example.com can be encoded before placing it in a query parameter.
• Decode a value like red%20shoes to confirm the original search term.

Related text tools

For encoded payloads, use the Base64 Encoder Decoder. For values inside API examples, use the JSON Formatter. If a URL pattern needs testing, use the Regex Tester.

FAQ

Does this encode a full URL?

It encodes URL components, which is best for parts such as query parameter values.

Why does decoding fail?

Some strings contain incomplete percent sequences such as %E0 or a lone percent sign.

Does it handle Unicode?

Yes. Browser URL encoding supports Unicode characters in URL components.

What is percent encoding?

Percent encoding represents characters with percent signs and hexadecimal values so they can travel safely in URLs.

Why should I not encode an entire URL as one component?

Encoding an entire URL can escape slashes and colons. Encode individual parameter values unless the whole URL is meant to be nested inside another URL.