Free URL encoder, decoder, query parser, and URL inspector

Three tabs: **Encode / decode** uses `encodeURIComponent` and `decodeURIComponent` (what you need for individual query values, not whole URLs). Decoding can treat `+` as a space for HTML form–style payloads. **Query string** accepts a bare `a=1&b=two`, a leading `?…`, or a full `https://…` URL and lists every key/value row (duplicates preserved) with optional JSON export. **Validate URL** runs the browser’s `URL` parser on absolute strings and shows href, host, path, search, hash, and query pair count, with a warning for `javascript:` and `data:` schemes.

Use encode mode for text you will place inside a single query parameter. Use decode mode on one encoded component at a time — paste a full URL here only if you intend to decode the entire string (slashes and `?` become percent-sequences).

Plain text

Percent-encoded

hello%20world%3Fx%3D1%26%E4%BD%A0%E5%A5%BD

Loading…

How to use this tool

1
Open URL encoder & decoder
Use it for this task: URL encode / decode, query string parser, URL parts breakdown, UTF-8 safe - 100% local.
2
Choose encode or decode
Paste your text or URL, then pick the direction and options that match your task.
3
Copy the transformed value
Use the encoded or decoded output in your request, config file, browser, or notes.

Quick facts

Runs offline?	Yes — after this page loads, parsing uses only your browser.
Do you upload URLs?	No. Safe Local Tools is static; strings stay in this tab.
Same as encodeURI?	No — this tab uses encodeURIComponent rules (safe inside `?…` values). encodeURI keeps `/ ? #` unescaped for whole-URL fragments.
Server-side redirect checks?	This page only parses what you paste — it does not fetch remote URLs or follow redirects.

Top use cases

URL encode / decode, query string parser, URL parts breakdown, UTF-8 safe - 100% local.
Runs offline?: Yes — after this page loads, parsing uses only your browser.
Do you upload URLs?: No. Safe Local Tools is static; strings stay in this tab.
Same as encodeURI?: No — this tab uses encodeURIComponent rules (safe inside `?…` values). encodeURI keeps `/ ? #` unescaped for whole-URL fragments.
Server-side redirect checks?: This page only parses what you paste — it does not fetch remote URLs or follow redirects.

FAQ

Why does encoding my whole URL break it?▾

`encodeURIComponent` escapes `?`, `/`, and `&`. Use it per parameter value, not on an entire URL you still want to fetch.

Why does decode say malformed?▾

Sequences like `%` alone, `%GG`, or truncated `%E4%BD` throw URIError. Remove partial encodings or paste the exact substring your framework encoded.

Does query parsing normalize keys?▾

We use URLSearchParams as specified: `+` in query values becomes a space, percent-sequences decode to UTF-8, and duplicate keys are listed in order.

Can I validate relative URLs?▾

Not without a chosen base URL — the strict parser expects an absolute string. Join your site origin plus the path in your editor first if needed.

What about IDN / punycode hosts?▾

Modern browsers expose ASCII punycode in hostname fields for international domains — compare with your address bar if labels look different.

Are pasted URLs logged?▾

No server round-trip exists; clear the fields on shared machines when you are done.