中文

URL Encode/Decode - Online URL Encode/Decode Tool

Input
Output

Online URL encoder/decoder for percent-encoding. Runs entirely in the browser — links are never uploaded.

How to Use & FAQ5 steps · 8 Q&A

URL Encoder/Decoder

Online URL encoder/decoder for percent-encoding. Runs entirely in the browser — links are never uploaded.

How to Use

  1. Choose Encode or Decode modeEncode is the default; switch to Decode when you have a %XX string and want the original text back.
  2. Enter text or a URL-encoded stringPlain text and strings that already contain %XX escapes are both supported; you can paste a whole parameter value directly.
  3. Click "Encode" or "Decode"Switch modes as needed; the result appears in the output box in real time. After encoding, spaces usually become %20.
  4. Copy the resultCopy with one click, or use "Swap" to send the output back to the input for further handling (e.g. decode then re-check).
  5. Notes when assembling into a URLWhen assembling the encoded result into a URL, replace only the parameter value and keep separators like ? = &, joining multiple parameters with &.

Related tools

Base64 Encoder/DecoderSymmetric EncryptionAsymmetric EncryptionHashing

Related reading

URL Encoding: When You Need It, and Where %20 and + Come From

FAQ

What is URL encoding used for?

URL encoding (percent-encoding) escapes special characters like spaces, non-ASCII characters, & and = into the %XX form, so parameters can be safely appended to a URL without being misparsed. For example, an & inside a value would otherwise be read by the server as the start of a new parameter.

Will the online URL encoder upload my links?

No. Everything is processed locally in the browser — neither links nor parameters are uploaded to a server, so using it on URLs that contain internal paths or tokens will not leak them.

What is the difference between encode and decode?

Encoding converts special characters into the %XX form for transmission; decoding restores %XX back to the original characters. This tool supports both directions: a string like %E4%B8%AD decodes back to "中".

Why does the result differ from what I expected?

A common cause is double encoding, or a space encoded as + instead of %20. Check how many times it was encoded, and choose between + and %20 per the target spec — forms often use +, while modern APIs usually require %20.

What is the difference between encodeURI and encodeURIComponent?

encodeURI keeps URL structure characters such as : / ? # & = and suits a full URL; encodeURIComponent encodes them and suits a single parameter value. This tool handles the parameter-value case, equivalent to encodeURIComponent.

Why does one Chinese character become several %XX escapes?

Non-ASCII characters are first encoded into multiple bytes as UTF-8, then percent-encoded byte by byte, so one Chinese character typically maps to several %XX escapes (e.g. "中" → %E4%B8%AD).

Must Chinese or emoji in a URL be encoded?

In almost all cases, yes. Modern browsers display Chinese in the address bar but still send %XX on the wire; if you build URLs by hand or write an API, skipping encoding will likely make the server fail to parse them.

Can I encode only part of a URL?

Yes, and you should. Encode only the parameter values, keeping the protocol, host and path separators intact. Encoding the whole URL at once breaks its structure and makes it unreachable.