URL Encoder/Decoder
Encode and decode URLs and query strings. Parse parameters into a key-value table. Copy individual params or full URL. 100% offline.
About this tool
A two-way URL encoder/decoder with a query string inspector. Paste any URL or string and tap Encode to get the percent-encoded version (with %20 for spaces, %3A for colons, etc.) ready to put inside another URL as a parameter. Tap Decode to reverse the encoding — useful for inspecting tracking URLs and reading encoded payloads. Drop a URL with a query string into the decoder and the tool splits every ?key=value&... pair into a clean table you can scan, copy row by row, or copy all at once. The encoder also has a Compose tab for building query strings from key-value pairs. Works fully offline.
Details
- Category
- developer
- Version
- 1.0.0
- Size
- 13 KB
- Updated
- Jun 2026
Frequently Asked Questions
What is URL encoding (percent encoding)?
URL encoding replaces unsafe or non-ASCII characters with a % followed by two hex digits. A space becomes %20, ? becomes %3F, é becomes %C3%A9. This is how URLs safely carry data that would otherwise break the URL structure (spaces, slashes, ampersands, accented characters).
When do I need to encode a URL?
When the URL is itself a value inside another URL — like a redirect target, an OAuth callback, or a link inside an email. The rule: any URL that is a value should be percent-encoded. URLs that the browser navigates to directly are usually already fine.
How is this different from Base64?
Base64 is a binary-to-text encoding that produces a string of common ASCII letters and digits. URL encoding (percent encoding) is a character substitution scheme that works one character at a time and produces a %XX pair. They are not interchangeable — use URL encoding for URLs, Base64 for binary blobs and image embeds.
How does the Query Inspector work?
When you decode a URL, anything after the ? is parsed as a query string. Each key=value pair becomes a row in the table. Rows show the key, the decoded value, and a copy button. The "Copy all" button copies the full set of parameters in original order, one per line, as key=value.
Is my data private?
Yes. The encoder and decoder run entirely in your browser using JavaScript's built-in encodeURIComponent, decodeURIComponent, and URLSearchParams APIs. Nothing is sent anywhere. You can safely decode internal tracking links or encoded payloads without worrying about leakage.
