URL Encode & Decode Online
Private by design — runs entirely in your browser
Encode strings for safe use in URLs, or decode percent-encoded sequences back to plain text. Toova handles every reserved character correctly, supports UTF-8 multi-byte sequences, and runs entirely in your browser.
What URL encoding actually does
URLs only allow a small set of ASCII characters. Everything else — spaces, ampersands, slashes, question marks, plus any non-ASCII letter — has to be percent-encoded as %XX bytes. Get this wrong and your link breaks, your query string parses incorrectly, or your form data is mangled on the server. Toova encodes and decodes both directions safely, including UTF-8 multi-byte sequences.
Component vs full URL
There are two flavors of URL encoding. Component encoding escapes every reserved character — what you want when injecting a value into a query string parameter. Full-URL encoding leaves slashes, question marks, and ampersands alone so the URL stays valid. Toova exposes both modes so you can pick the right one depending on whether you are encoding a value or a whole link.
Browser-only
All encoding and decoding happens inside your browser. Nothing is uploaded, nothing is logged. That matters when the value you are encoding is a user ID, a session token, or anything sensitive — you can paste it without worrying about a third party seeing it. The page works offline after first load and there are zero outbound requests during encoding.
Frequently Asked Questions
- What is the difference between encodeURI and encodeURIComponent?
- encodeURI leaves URL structural characters (slashes, question marks, ampersands) alone, so it is for encoding a full URL. encodeURIComponent escapes everything, which is what you want when injecting a value into a single query string parameter.
- Does it handle UTF-8?
- Yes. Non-ASCII characters are encoded as multi-byte UTF-8 sequences in percent form. Decoding restores the original characters exactly, including emoji and CJK text.
- Why does space sometimes become + and sometimes %20?
- Application/x-www-form-urlencoded (form bodies) uses + for spaces. URL paths and query strings use %20. Toova lets you pick the right encoding for the context — picking the wrong one is one of the most common bugs in form handling.
- Can I encode multiple lines at once?
- Yes. Paste any multi-line string and the tool encodes each character correctly, including newlines which become %0A or %0D%0A. The output stays on a single line, as URLs require.
- Is my input sent anywhere?
- No. Encoding and decoding run entirely in your browser. Nothing is uploaded, and the page works offline after first load.