URL Encoder & Decoder
Percent-encode text for use inside URL components or decode percent-encoded values back into readable text.
Use the URL Encoder & Decoder when query parameters, path values, or copied web data contain characters that need to be represented safely inside a URL. Encoding helps preserve the boundary between URL syntax and the data inside it. If a value still looks unreadable after decoding, it may contain another layer such as Base64 or JSON, so work from the outside inward instead of repeatedly encoding or decoding at random.
Encode data safely inside a URL component
URLs use certain characters as syntax. Percent-encoding lets those same characters be represented as data when they would otherwise be ambiguous.
What percent-encoding looks like
A space can appear as %20, and characters such as &, =, ?, and # may need encoding when they are part of a value rather than URL structure.
Encode components, not blindly the entire URL
When building a query string in code, encode the parameter values rather than taking a complete working URL and encoding every colon, slash, question mark, and ampersand. Encoding the whole URL as one component produces a different result.
Why + sometimes means a space
HTML form encoding commonly represents spaces with a plus sign in query strings. General URL percent-encoding often uses %20. This is one reason URL decoding can depend on the context where the string came from.
Double encoding
If an already encoded value is encoded again, the percent sign itself becomes encoded. For example, %20 can become %2520. Decode in controlled steps if you suspect a value has been encoded more than once.
Frequently asked questions
Is URL encoding encryption?
No. Encoded values are still visible and reversible. Never rely on encoding to protect sensitive data.