URL Encoder

Percent-encodes and decodes URL text — spaces, Korean, special characters — so what you paste into an address bar or API call arrives intact. 검색어 becomes %EA%B2%80%EC%83%89%EC%96%B4, and back again.

How to use

1. Paste the text or URL fragment.
2. Encode to make it URL-safe, or decode to read an encoded one.
3. Copy the result into your URL, query string or request.
4. Encode parameter values individually rather than a whole assembled URL — see below.

When you actually need this

• Building query strings containing Korean, spaces or symbols by hand.
• Decoding a %-riddled URL from a log or analytics report to see what it says.
• Preparing redirect and callback parameters that must carry a full URL inside them.
• Debugging why an API call with special characters in a parameter misbehaves.

Why encoding exists, and the double-encoding trap

URLs reserve characters like ?, &, = and # as structure, and historically allow only ASCII — everything else travels as percent-escaped UTF-8 bytes, which is why one Korean syllable becomes three %XX groups. The classic mistakes are two. Encoding an already-assembled URL escapes its structural characters and breaks it — encode the parameter values, then assemble. And double-encoding, where %20 becomes %2520 because an encoded string was encoded again, produces those literal %25 artefacts you see in broken links; decode twice to diagnose. The + sign means space only in form encoding, not in paths — another regular source of confusion.

Related tools

FAQ

Does URL Encoder send my input to a server?

No. The conversion runs in JavaScript inside the page, so API keys, tokens, config files and any other sensitive text stay on your machine. You can verify this by opening your browser's network tab while you use the tool.

Does URL Encoder handle Unicode and non-ASCII characters?

Yes. Text is processed as UTF-8, so accented Latin, Korean, Japanese, Chinese, Cyrillic, Arabic and emoji all round-trip correctly rather than turning into question marks.

Can I use the output in production code?

Yes — the output follows the relevant standard exactly and is safe to paste into your project. As with any tool, run your own tests before shipping anything that depends on it.