What You Can Do

The URL Encoder & Decoder Tool converts Japanese text and special characters in URLs to safe percent-encoding format (%XX), and vice versa, all within your browser. Perfect for API development debugging, search query creation, and sharing Japanese URLs. Adopts RFC 3986-compliant UTF-8 encoding.

  • ✅ Encode: Convert Japanese text and symbols like "検索" → "%E6%A4%9C%E7%B4%A2"
  • ✅ Decode: Restore percent-encoded strings to original text
  • ✅ RFC 3986 Compliant: Accurate conversion following URL standard specifications
  • ✅ One-click toggle between encoding and decoding
  • ✅ Full Unicode support with UTF-8 for all languages
  • ✅ Completely free with no registration required
  • ✅ All processing is done in your browser - no data is sent to any server

Use Cases

  • API Development & Debugging - Properly encode URL parameters containing Japanese text or symbols
  • URL Sharing - Turn Japanese keywords that go into a URL (parameter values) into %XX form
  • Query Parameter Creation - Convert search keywords to URL format
  • Browser Address Bar Analysis - Convert encoded URLs to readable format
  • Web Development Learning - Perfect for understanding URL encoding mechanisms

How to Use

Basic Usage

Simply enter the string you want to encode or decode and click the corresponding button to execute the conversion.

What is URL Encoding

URL encoding (percent-encoding) is a method to convert characters that cannot be used in URLs or reserved characters into a safe format. It is necessary when using multibyte characters like Japanese or special characters in URLs.

Conversion Examples

  • Japanese: "検索" → "%E6%A4%9C%E7%B4%A2"
  • Space: "hello world" → "hello%20world"
  • Symbols: "?&=" → "%3F%26%3D"

Common Use Cases

  • Search Parameters: Including Japanese text in search queries
  • API Calls: Including special characters in URL parameters
  • Link Sharing: Sharing URLs containing Japanese text
  • Debugging: Checking the content of encoded URLs

Notes

  • URL encoding uses UTF-8 character set
  • Be careful not to encode already encoded strings (double encoding)
  • Encode only necessary parts, not the entire URL

Application Scenarios

  • Web API query parameter creation
  • Form data URL transmission
  • Decoding encoded URLs
  • Japanese URL conversion
  • Development and debugging work

Technical Explanation of URL Encoding

About RFC 3986 - Basics of URL Standards

RFC 3986 (Uniform Resource Identifier: Generic Syntax) is the official standard specification by IETF (Internet Engineering Task Force) that defines the syntax of URLs and URIs. It was published in 2005 as a revision of RFC 2396 from 1998.

Reserved Characters Defined in RFC 3986

The following characters have special meanings in URLs and must be encoded when used as data:

  • : Separator between scheme and host (e.g., https://)
  • / Path separator (e.g., /tools/url-encoder/)
  • ? Query string start (e.g., ?q=search)
  • # Fragment identifier start (e.g., #section)
  • [ ] @ ! $ & ' ( ) * + , ; = Subcomponent delimiters

Unreserved Characters

The following characters can be used without encoding:

  • Alphanumeric: A-Z a-z 0-9
  • Symbols: - _ . ~ (hyphen, underscore, period, tilde)

💡 Encoding in this tool turns every character except the unreserved ones (letters, digits and - _ . ~) into %XX. Reserved characters such as / ? & = are converted too, so use it on part of a URL, such as a parameter value, rather than on a whole URL.

How Percent-Encoding Works

Percent-encoding is a technique to convert characters that cannot be used in URLs into hexadecimal ASCII code representation. The conversion is performed in the following steps:

Encoding Steps (Example: "検索")

  1. Convert to UTF-8 byte sequence
    • "検" → UTF-8: E6 A4 9C (3 bytes)
    • "索" → UTF-8: E7 B4 A2 (3 bytes)
  2. Convert each byte to percent sign + hexadecimal
    • E6 → %E6
    • A4 → %A4
    • 9C → %9C
    • E7 → %E7
    • B4 → %B4
    • A2 → %A2
  3. Result: "検索" → %E6%A4%9C%E7%B4%A2

Decoding Steps (Reverse Conversion)

  1. Convert hexadecimal numbers after percent signs to byte values
  2. Interpret byte sequence as UTF-8 and restore to original string

⚠️ Warning: Re-encoding already encoded strings results in "double encoding" and cannot be decoded correctly. Example: Re-encoding %E6%A4%9C → %25E6%25A4%259C (% becomes %25)

Character Encoding and Mojibake Prevention

The most important aspect of URL encoding is unified Character Encoding. Mojibake (garbled text) occurs when different character encodings are used for encoding and decoding.

Common Character Encodings

Encoding Description URL Encoding
UTF-8 Current web standard. Represents all Unicode characters in 1-4 bytes ✅ Recommended (Used by this tool)
Shift_JIS Legacy Japanese character code. 1-2 bytes ⚠️ Not recommended (compatibility issues)
EUC-JP Japanese code used in UNIX ⚠️ Not recommended (now rare)
ISO-8859-1 For Western European languages. No Japanese support ❌ Cannot use for Japanese

Best Practices to Prevent Mojibake

  • Unify with UTF-8: Match HTML <meta charset="UTF-8"> with server settings (Content-Type)
  • Use UTF-8 for URL encoding: All modern URL encoders including this tool adopt UTF-8
  • Avoid double encoding: Don't call JavaScript's encodeURIComponent() multiple times
  • Use same character code for decoding: Always decode UTF-8 encoded URLs with UTF-8

📌 This tool always uses UTF-8, as do most current web applications and APIs. %XX sequences encoded in Shift_JIS or other encodings cannot be decoded here, so check the character encoding of the system you are sending to.

What is the URL Encoder/Decoder?

This browser-based tool converts Japanese text and special characters in URLs to percent-encoding format (%XX) and vice versa. Adopts RFC 3986-compliant UTF-8 encoding, perfect for API development, search query creation, and sharing Japanese URLs. No registration required for instant use, and no data is transmitted externally.

Who is this for?

Developers adding Japanese text to URL parameters, anyone checking the contents of encoded URLs, engineers building API request URLs with correct encoding, and people formatting URLs for sharing via email or chat.

FAQ

The characters that separate the parts of a URL, such as : / ? & =, are also turned into %XX, so the result no longer works as a link (https://example.com/search?q=café becomes https%3A%2F%2Fexample.com%2Fsearch%3Fq%3Dcaf%C3%A9). Use encoding only on part of a URL, such as a search term that goes after q= or another parameter value or path segment. Decoding a whole URL is fine: the %XX parts turn back into the original characters.

Encoding turns a space into %20. Decoding does not turn + into a space; it leaves + as it is (%2B decodes to +). If + stands for a space, as in a query string sent by an HTML form, replace + with %20 before decoding.

Only letters (A-Z, a-z), digits and the four symbols - _ . ~. Every other symbol, spaces and Japanese text become %XX. The tool also converts ! ' ( ) *, which JavaScript's encodeURIComponent leaves alone, to %21, %27, %28, %29 and %2A, so its output can differ from other tools.

When a % is not followed by two hexadecimal digits (such as 100% or %ZZ), when the bytes of a character are cut off partway (such as %E6%A4, which is not a whole Japanese character), or when the text was encoded in Shift_JIS or another encoding instead of UTF-8. While the tool converts automatically as you type, it does not show an error and simply clears the result; the error appears only when you press the Decode button.

Yes. Double encoding turns the % itself into %25 (%E6 becomes %25E6), so decoding once brings it back to the %E6%A4%9C… form. If the result still contains %XX, decode that result again. Each decode removes one layer; the tool does not detect how many times a string was encoded.

Each character is turned into its UTF-8 bytes and each byte becomes %XX. Most kanji and kana are 3 bytes, so 検索 becomes %E6%A4%9C%E7%B4%A2, and an emoji is 4 bytes, so 😀 becomes %F0%9F%98%80. Decoding also reads the bytes as UTF-8.

📅 Last Updated: October 16, 2026