🔗

Free URL Encoder & Decoder

Encode or decode URLs and query string parameters instantly — free, private, no signup.

← Back to all tools

Advertisement

Result will appear here...

Copied!

Advertisement

How to Encode or Decode a URL

1

Paste your URL or text

Enter the URL you want to encode, or paste a percent-encoded string you want to decode back to readable text.

2

Click Encode or Decode

Click "Encode" to convert special characters to percent-encoding, or "Decode" to reverse an already-encoded string.

3

Copy the result

Click "Copy" to copy the output to your clipboard. Use it directly in your code, API calls, or browser address bar.

Frequently Asked Questions

What is URL encoding?

URL encoding (percent-encoding) converts characters that are not allowed in URLs into a % followed by two hex digits. For example: space → %20, & → %26, = → %3D, making URLs safe for transmission.

Why do I need to encode URLs?

URLs can only contain certain ASCII characters. Special characters like spaces, &, =, and #, plus non-ASCII characters like accented letters or emoji, must be encoded so browsers and servers interpret them correctly.

What characters get percent-encoded?

All characters except letters (A-Z, a-z), digits (0-9), and the unreserved characters (- _ . ~) get encoded. Common examples: space → %20, & → %26, = → %3D, / → %2F, + → %2B, ? → %3F, # → %23.

When should I encode query string values?

Always encode individual query parameter values before appending them to a URL. Without encoding, characters like & and = inside a value will break the URL structure and be misinterpreted by servers.

How do I decode %20 and other percent sequences?

Paste the encoded URL or string into this tool and click Decode. All percent-encoded sequences (%20, %2F, %3D, etc.) are converted back to their original readable characters instantly.

Can I encode non-English characters in a URL?

Yes. Non-ASCII characters (like é, ü, Chinese characters, or Arabic text) are first converted to UTF-8 bytes, then each byte is percent-encoded. For example, é becomes %C3%A9.

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

In query strings (after ?), spaces can be encoded as either + or %20. In URL paths (before ?), only %20 is correct. This tool uses %20 (encodeURIComponent standard), which is safe in both positions.

Related Tools