URL Encode
Runs in your browser — your data is never uploaded.
Percent-encode any text so it’s safe to place inside a URL — query parameters, path segments, redirect targets. OkConverter applies strict RFC 3986 component encoding (the same rules as JavaScript’s encodeURIComponent), converting spaces, ampersands, non-ASCII characters and everything else that would break a URL. It all runs locally in your browser.
0 characters · runs entirely in your browser
How to use URL Encoder
- 1
Paste or type the text you need to put inside a URL.
- 2
Click “Encode” — every unsafe character is percent-encoded instantly.
- 3
Copy the encoded string into your query parameter or path.
Share
Embed this tool on your site
Paste this where you want the tool to appear. It runs entirely in your visitor's browser — no uploads, no account, no tracking.
Please keep the attribution line — it's what keeps these tools free.
Need a different size, a dark theme, or a different tool? Build an embed lets you preview it first.
Frequently asked questions
What characters get encoded?+
Everything except unreserved characters (A–Z, a–z, 0–9, “-”, “_”, “.”, “~”) is converted to %XX escapes. Spaces become %20, “&” becomes %26, and multi-byte UTF-8 characters become multiple escapes (é → %C3%A9).
Should spaces be %20 or +?+
This tool emits %20, which is correct everywhere in a URL. The “+” convention is only valid inside application/x-www-form-urlencoded form bodies and query strings — %20 works there too, so %20 is the safer universal choice.
Is my text sent to a server?+
No. Encoding runs entirely in your browser — useful when the text is a callback URL, token or other value you’d rather not share with a third-party site.
When do I need URL encoding?+
Any time user data goes into a URL: search queries, redirect URLs, filenames in paths, or values in query strings. Unencoded special characters can break the URL or change its meaning entirely.