🔗 URL Encoder/Decoder

Encode and decode URL parameters, query strings, and special characters

📝 Input No Input
📤 Output No Output
Encoded/decoded output will appear here...

💡 Sample Data

Try these examples to test the encoder/decoder:

About URL Encoder/Decoder

Our free online URL encoder and decoder helps developers encode and decode URL parameters, query strings, and special characters. Whether you're building web applications, working with APIs, or handling user input, our tool provides comprehensive URL encoding capabilities.

Features

How to Use

  1. Enter text to encode or URL-encoded text to decode
  2. Choose encoding type (URL, Component, or Query String)
  3. Click encode or decode buttons
  4. Review character analysis and URL preview
  5. Copy the result or generate a link

Common Use Cases

About this tool

Free Online URL Encoder and Decoder

Percent-encode any URL or query string value — and decode percent-encoded strings back to readable text. Handles full URLs (preserving structural characters) and individual parameter values (encoding everything that needs encoding). All processing is local; nothing is uploaded.

What is URL Encoding?

URLs can only contain a specific set of ASCII characters. Spaces, special characters, and non-ASCII text must be percent-encoded: a % followed by two hexadecimal digits representing the character's UTF-8 byte value. A space becomes %20; the euro sign becomes %E2%82%AC.

encodeURI vs encodeURIComponent

The most common mistake: using encodeURI on a parameter value. If the value contains & or =, they won't be encoded and will break the query string structure.

What is the difference between %20 and + for spaces?

%20 is universal and works everywhere in a URL. + means space only in query strings (application/x-www-form-urlencoded). In path segments, + is a literal plus sign. When in doubt, use %20.

Why does double-encoding produce %25 instead of %20?

The % character itself encodes as %25. Encoding an already-encoded string encodes the % signs — producing %2520 instead of %20. Always encode raw, un-encoded values.

Do I need to encode forward slashes in a path?

Only if the slash is a literal value — not a path separator. A file name containing a slash must be encoded as %2F. A slash acting as a path separator between segments should be left unencoded.

Learn more: URL Encoding Explained: Percent Encoding in Web Development

Related Tools

More Dev Tools

Base64 EncoderBcrypt GeneratorColor PickerCron ParserCSS MinifierCSV ⇄ JSON

Want more detail? Read URL Encoding Explained: Percent Encoding in Web Development.