What this tool does
URL Encoder and Decoder
Your input is sent to the server for this request and is not saved as a tool content record. Infrastructure logs may still record request metadata, so do not submit secrets.
Keep encoding and decoding intent close because users often need both in one workflow.
How to use this tool
How to use URL Encoder and Decoder
Paste text.
Choose encode or decode.
Process and copy the result.
Before and after example
URL Encoder and Decoder example
Input
name=ScriptZip.io&category=developer-toolsOutput
name%3DScriptZip.io%26category%3Ddeveloper-toolsOptions, errors, and limitations
URL Encoder and Decoder options and common errors
Parent category
Explore the Converter Tools hub
Converters for JSON, CSV, XML, Base64, and URL-encoded content.
FAQ
URL Encoder and Decoder FAQ
Why is a space encoded as %20 sometimes and plus other times?
Percent encoded URLs represent a space as %20. In form encoded query data, a plus sign is also commonly interpreted as a space, which is why the two forms appear in different contexts.
Should I encode an entire URL or only a parameter value?
Usually you should encode individual URL components or parameter values, not blindly encode the whole URL. Encoding the scheme separators, slashes, question mark, and other structural characters can make a valid URL unusable.
What characters need URL encoding?
Characters that are not allowed literally in a given URI component, or that have reserved meaning, may need percent encoding. The correct set depends on whether you are encoding a path segment, query value, fragment, or another component.
What is double URL encoding?
Double encoding happens when already percent encoded text is encoded again, turning percent signs into %25 sequences. It often causes APIs or redirects to decode to the wrong value because different layers decode a different number of times.
How are Unicode characters encoded in URLs?
Unicode text is generally converted to UTF 8 bytes and those bytes are percent encoded where required. That is why one visible character can become several percent encoded byte sequences.
Should slashes inside a path value be encoded?
A slash is a path separator, so whether it should be encoded depends on whether it is structural or part of the data inside one path segment. Encoding decisions must respect the URL component being constructed.
How do I encode a literal plus sign in a query string?
In form encoded query data, a plus can be interpreted as a space, so a literal plus is typically percent encoded as %2B. This avoids ambiguity with space conversion.
What are reserved URL characters?
Reserved characters such as colon, slash, question mark, hash, brackets, at sign, and query separators can have structural meaning defined by URI syntax. They should not be percent encoded indiscriminately when they are serving that structural role.
Why does decoding a URL once still leave percent sequences?
The value may have been encoded more than once or may contain a nested encoded parameter. Decode only the layer you actually expect because repeated decoding can change data unexpectedly or create security problems.
Does URL encoding make a value safe from attacks?
No. URL encoding is a representation technique, not an input validation or security control. Applications still need context appropriate validation, authorization, output escaping, and protections against injection and open redirect issues.