Enter text and the conversion appears here.
Turn text with non-ASCII characters or symbols into %XX form for URLs. Encoding a value differs from encoding a whole URL, so both are shown. Decode %E3%81%82-style strings back to readable text.
FAQ
Which result should I use?
The value form for anything going after "?q=" or into a single path segment. The whole-URL form when you are handling a complete URL. If you are unsure, ask whether the "/" and "?" characters in your string are acting as separators: if they are, use the URL form; if they are just characters, use the value form.
Can I use Japanese filenames in URLs?
Encoded, yes — but it is not advisable. They get double-encoded when shared onward, and older software that cannot interpret %XX renders the name as garbage. Filenames for distribution are less trouble later when kept to letters, digits and hyphens.
A long URL in an email breaks in the middle.
That is the mail client wrapping the line, not an encoding problem — though URLs containing Japanese are longer because of %XX and so hit it sooner. Wrapping the URL in angle brackets, <https://…>, or using a shortener avoids the break.
Is the text I paste stored?
No, and nothing is sent. The conversion happens in the page and is gone when you close it.