URL Encoder & Decoder

Encode URL parameters or decode percent-encoded text online. Choose component, complete URL or form mode to handle UTF-8, spaces, plus signs and reserved characters correctly.

0 characters
Result

Your result will appear here.

How to encode or decode a URL value

  1. Paste the original text or the percent-encoded value. Choose Encode or Decode.
  2. Use component mode for one parameter or path segment, complete URL mode to preserve URL separators, or form mode for one form field.
  3. Run the conversion and copy the result. Encode individual parameter values before inserting them into a URL.

Working with URL Encoder & Decoder

Component mode escapes separators such as & and =. Complete-URL mode keeps URL separators. Form mode uses + for spaces and %2B for literal plus signs. Choose the mode that matches the system reading the result.

Example: encode a single URL parameter

Input
Hello, world! ๐Ÿ‘‹ + & = / ?
Result
Hello%2C%20world!%20%F0%9F%91%8B%20%2B%20%26%20%3D%20%2F%20%3F

Questions about URL Encoder & Decoder

Should I encode a complete URL or just a parameter?

For a parameter value, use component mode: & and = become %26 and %3D. Complete URL mode preserves separators such as :, /, ? and &, so it does not protect individual values automatically. Complete URL decoding also leaves reserved escapes such as %2F intact.

Why does a space become %20 in one mode and + in another?

Component mode represents a space as %20 and a literal + as %2B. Form mode uses + for a space and %2B for a literal plus sign. When decoding, only form mode turns a raw + into a space.

Why does %20 turn into %2520?

Encoding an already encoded value encodes the % sign again as %25. This tool processes one layer at a time; decode only as many times as the receiving system expects. Repeated decoding can turn escaped separators into meaningful URL characters.

Can I encode accented letters, non-Latin text and emoji?

Yes, encoding uses UTF-8. Decoding requires valid percent escapes and valid UTF-8 bytes; incomplete sequences or %GG are rejected. This is not a converter for older encodings such as GBK. Decoding displays text; it does not open the resulting address.

Are my files, tokens or text uploaded?

No. These tools process your input in your browser. The website serves the page and its code, but your input is not sent to a conversion server or saved in an account.

Explore all developer tools

Encoding & Files

Move between text, bytes, URLs and embedded images without changing your original data.

Data & Text Inspection

Read structured data, inspect tokens and understand exactly what changed.

Hashes, IDs & Schedules

Check file integrity, generate identifiers and make sense of times and recurring schedules.

Your input and files are processed on your device. Keep sensitive results out of shared clipboards and use a trusted device for private keys and tokens.