← All Tools Dev

URL Encoder & Decoder

Encode text to URL-safe format and decode percent-encoded URLs — RFC 3986 compliant, instant results.

How to Use the URL Encoder / Decoder

Paste text into the left box and click Encode to turn spaces, Chinese characters, emoji and special symbols into percent-encoded URL-safe strings. Paste an encoded string and click Decode to get the readable form back.

Essential when building query strings for APIs, sharing links with special characters, or debugging why a URL breaks in a browser or email client. Encode the values of query parameters separately - never the whole URL at once, or the delimiters will be encoded too.

Tip: many frameworks encode automatically, but double-encoded values like percent-2520 are a common bug. If you see percent-25 in your output, your data was encoded twice - decode once more to fix it.

When building URLs in code, always encode user input - a single unencoded space or Chinese character can break a link or trigger a 400 error. For email links with subject lines, encode the whole subject parameter, not just the visible text.

Quick Reference — Common Encoded Characters

Space = %20 / = %2F ? = %3F = = %3D & = %26 # = %23 % = %25 + = %2B : = %3A @ = %40 ! = %21 ( = %28 ) = %29

About This URL Encoder

This free URL encoder and decoder converts text to URL-encoded format (percent-encoding) and back, following RFC 3986. URL encoding converts unsafe ASCII characters into a "%" followed by two hexadecimal digits, allowing special characters to be safely transmitted in URLs. All processing happens in your browser.

Features

How to Use

  1. Choose Encode or Decode mode
  2. Type or paste your text into the input area
  3. Click Convert to see the result instantly
  4. Use the character reference to add common encoded characters with one click

Frequently Asked Questions

Why do URLs need encoding?

URLs can only contain certain ASCII characters. Characters like spaces, ?, &, and # need to be encoded as %XX sequences to be transmitted safely.

What's the difference between encodeURI and encodeURIComponent?

encodeURIComponent encodes more characters (including /, ?, &, =) making it suitable for query string parameters. This tool uses encodeURIComponent/decodeURIComponent.

Can I encode a full URL?

For encoding specific query parameters, use Encode mode. To decode a full encoded URL, use Decode mode.

Is my data sent to a server?

No. All encoding and decoding happens entirely in your browser. Nothing is sent anywhere.