URL Encoder / Decoder

Encode or decode URLs — handles CJK paths and special characters.

Source

Paste a URL or text, choose Encode or Decode.

0 chars Ctrl/Cmd + Enter
local only

Result

The result updates in place and stays ready to copy.

Ready for a transform

Use Encode to escape special characters or Decode to read percent-encoded strings.

Mode: encode Changed: 0 Segments: 0
0 chars 0 lines State: idle

How to use

Paste a URL containing CJK characters, spaces, or special symbols, click Encode to get the percent-encoded form; paste an encoded string and click Decode to restore readable text.

encodeURI vs encodeURIComponent: This tool uses encodeURIComponent, which encodes all special characters including / ? & =, making it suitable for encoding individual parameter values. To preserve full URL structure, use encodeURI (out of scope for this tool).

Common encodings: space → %20, &%26, =%3D, %E5%8F%B0, %E5%8C%97. Tilde ~, exclamation !, asterisk *, apostrophe ', and parentheses ( ) are not encoded per RFC 3986.

Quick guide

Use cases, answers, and nearby tools

Compact below-tool notes that help first-run users and repeated visitors move faster without changing the main interface.

Chinese search: URL 編碼器、URL 解碼器、網址編碼 線上、百分比編碼

How to use

Run a clean first pass

  1. Paste a URL, query string, or plain text into the input panel.
  2. Choose Encode or Decode depending on your need.
  3. Review the result and click Copy.

Examples

Real jobs this page helps with

  • API calls with CJKEncode a URL containing Chinese characters before embedding in an API call or HTML link.
  • Reading server logsDecode percent-encoded query strings from server logs to read the original parameters.

FAQ

What people usually want to know

What is the difference between encodeURI and encodeURIComponent?
encodeURIComponent encodes all special characters including / ? & =, suitable for single parameter values; encodeURI preserves URL structure characters. This tool uses encodeURIComponent.
Does any content leave the browser?
No. All encoding and decoding happen locally in the browser.