URL Encoder / Decoder
Encode text into URL (percent) encoding and decode it back. Handy for building Japanese URLs and query parameters or inspecting encoded strings.
Examples and how it works
Two hexadecimal digits after % represent one byte. This tool decodes one layer of percent-encoding and reads the bytes as UTF-8.
URL decode
- Input
- A%2BB%20C
- Output
- A+B C
A literal + stays a plus sign; it is not treated as a form-encoded space. Decoding %2520 once produces %20.
Done
URL Encoder / Decoder
How to use
- 1
Enter text
Paste the string you want to encode or decode into the input area.
- 2
Choose a conversion
Press "Encode" or "Decode".
- 3
Copy
Review the result and copy it for use.
Features
- URL-encode text including Japanese characters
- Full RFC 3986 compliance (encodes !, parentheses and more)
- Decodes percent-encoded strings back to text
- Your text is never sent to a server
Use cases
Build links with Japanese text
Encode URLs that contain Japanese search terms or page names for sharing and embedding.
Assemble query parameters
Include text and special characters safely in query strings for forms and APIs.
Inspect encoded strings
Decode percent-encoded output from logs and tools to see the original content.
Details
URL encoding (percent-encoding) replaces characters that are not allowed in URLs and query parameters with a "%" followed by two hex digits. For example, the Japanese character あ becomes %E3%81%82 and a space becomes %20. It prevents garbled text and broken links when sharing URLs or submitting forms.
This tool encodes in full compliance with RFC 3986. JavaScript's encodeURIComponent does not encode "!", the apostrophe, "(", ")" or "*", so this tool is the better choice when strict conversion matters. Decoding accepts both uppercase and lowercase percent notation.
All conversion happens in your browser - the text you enter is never sent to a server. Invalid percent encodings (such as %GG) are detected and reported as an error during decoding.
FAQ
What is the difference between URL encoding and Base64?
URL encoding converts text into characters that are safe in a URL, while Base64 converts binary data into text. They serve different purposes; use URL encoding for links and query strings.
Is Japanese text URL-encoded?
Yes. Japanese characters are converted to their UTF-8 byte sequences and shown as percent notation such as %E3%81%82.
How is a space encoded?
A space becomes %20 (the same as encodeURIComponent). The older "+" form is specific to form submissions.
Is my text sent to a server?
No. All conversion happens locally in your browser.
Related Tools
Hex & Text Converter
Convert Hex bytes and UTF-8 text in your browser. Inspect byte counts, Japanese characters and invalid UTF-8 without uploading data.
JSON Formatter
Format, minify, validate and unescape JSON right in your browser.
Base64 Converter
Encode or decode text, images and files to and from Base64.
UUID Generator
Generate UUIDs (v4) in bulk for free. Handy for API development and test data.
All processing happens in your browser. Your files are never uploaded.
Did you know?
URL encoding represents characters as "%" plus two hex digits. The Japanese character あ becomes %E3%81%82.