Skip to main content

Find your next tool

Prepare, check, then export

URL Decode & Encode (UTF-8, Shift_JIS, EUC-KR)

Paste an encoded link or any text and the result appears as you type: %20 becomes a space and %C3%A9 becomes é. Each line is decoded on its own, so a column of links copied from a log or a spreadsheet stays a column. Switch to Encode to turn text into a safe query value, a whole URL or form data.

Loading text workspace…

Benefits

  • Reads Japanese, Korean and Chinese links from older sites: choose Shift_JIS, EUC-JP, EUC-KR, GBK or Big5, or pick the character set the page suggests when UTF-8 fails.
  • Shows a pasted link as a table of its parts and decoded query parameters, with a CSV download for a spreadsheet.
  • Spots links that were encoded twice (%2520 instead of %20) and decodes them in one step, up to five rounds.

When this helps

  • Read the search terms and tracking parameters in a long link from analytics or a server log.
  • Prepare a value with &, = or spaces for a query string, an API call or a mailto link.
  • Fix a list of links that shows %E6%9D%B1… instead of Japanese, Korean or Chinese words.

How to use this tool

  1. Paste text or links, one per line, or import a TXT file.
  2. Choose Decode or Encode. For encoding, choose what the text is for: a query value or path segment, a whole URL, or form data.
  3. Leave Character set on UTF-8 unless the text comes from a site that uses Shift_JIS, EUC-KR or another older set.
  4. Copy or download the result, open URL parts for the parameter table, or continue to the next text tool.

What percent-encoding does, and why the same text can be encoded three ways

A URL may contain only a small set of ASCII characters. Everything else, from a space to é or 東, is first turned into bytes, and each byte is written as % and two hexadecimal digits (RFC 3986, section 2.1). In UTF-8, which almost every site uses today, é is two bytes and becomes %C3%A9, and 東京 is six bytes and becomes %E6%9D%B1%E4%BA%AC. Decoding reverses those steps, so the decoder has to know which character set produced the bytes: %93%8C%8B%9E reads as 東京 in Shift_JIS and as unreadable symbols in UTF-8.

Encoding depends on where the text will go. A query value or path segment (encodeURIComponent in JavaScript) must encode &, =, / and ? so that they are not read as separators: a b&c=d/é becomes a%20b%26c%3Dd%2F%C3%A9. A whole address (encodeURI) keeps those characters, because they give the URL its structure: a%20b&c=d/%C3%A9. HTML forms send application/x-www-form-urlencoded data, where a space is + and only * - . _ stay as they are: a+b%26c%3Dd%2F%C3%A9. All three results come from this page.

Older Japanese, Korean and Chinese sites, mail systems and search logs still use Shift_JIS, EUC-JP, EUC-KR, GBK or Big5. Browsers can read these sets but write only UTF-8, so this page builds its encoding tables from the browser’s own decoder: 検索 東京 becomes %8C%9F%8D%F5%20%93%8C%8B%9E in Shift_JIS and %E6%A4%9C%E7%B4%A2%20%E6%9D%B1%E4%BA%AC in UTF-8. When a line is not valid UTF-8, the page tries the other sets and previews each one that reads it. Short byte strings can be valid in more than one set, and only a person can tell which reading makes sense.

Two problems turn up in real links. A link encoded twice shows %2520 where a space should be, because the % of %20 was encoded again as %25; the page notices escapes left in the result and offers to decode again, up to five rounds. A % that is not followed by two hex digits, as in 100% sure, is kept as a literal %, the way browsers treat it, and counted so you can check it. In our test run, decoding 9,000 analytics links (844,889 characters) took 48 ms and encoding 1,050,000 characters took 0.11 s. The editor holds up to 2,000,000 characters and works on long texts in a background thread.

Formats, limits and privacy

  • Up to 2,000,000 characters in the editor and TXT files up to 2 MiB. Texts of 50,000 characters or more are processed in a background thread.
  • Internationalized domain names are shown in their ASCII form (xn--…); the page does not convert punycode.
  • This is not a link checker or a link expander: it does not open the URL, follow redirects or reveal where a short link leads.
  • A character that does not exist in the chosen older set, such as an emoji in Shift_JIS, is written as &#NNNN; (its Unicode number), the way browsers send it from a form, and the page counts these.

These tools process text locally. There is no draft autosave. Download important work before leaving; temporary file handoffs expire after 30 minutes.

Frequently asked questions

Why does + sometimes mean a space?

Form data and most query strings write a space as +, a rule of the application/x-www-form-urlencoded format. In a path, + is a plus sign. Read + as a space is on by default for decoding; turn it off for paths or for values where + is meant literally, such as a phone number like +44.

What is the difference between encodeURI and encodeURIComponent?

encodeURIComponent encodes every character that has a meaning in a URL, including & = / ? and #, so use it for one query value or path segment. encodeURI leaves those characters alone and is meant for a whole address that is already put together. On this page they are called Query value or path segment and Whole URL.

Why do I see strange symbols after decoding?

The bytes were written in a different character set from the one used to read them. Japanese links from older sites often use Shift_JIS or EUC-JP, Korean ones EUC-KR, and Chinese ones GBK or Big5. Choose that set under Character set, or select one of the suggestions the page shows when a line is not valid UTF-8.

How do I decode a URL that was encoded twice?

If the result still shows %20, %3A or similar codes, the text was encoded more than once. Select Decode again, or tick Decode until nothing is left encoded; the page then decodes up to five times and says how many rounds it needed.

Can I decode many links at once?

Yes. Paste one link per line, up to 2,000,000 characters. Each line is decoded on its own, a line that cannot be decoded is left unchanged and listed by number, and the result keeps the line order so it can go back into a spreadsheet column.

Is my link sent to a server?

No. Encoding, decoding and the parameter table run in your browser, and nothing you paste is sent to MAXScanner or stored. Analytics record only which option was used, never the text. Links can contain session tokens or e-mail addresses, so avoid pasting them into tools that upload.

Continue your document workflow

Use a Continue button inside the workspace to carry your text; these links open a fresh tool.