| Key | Value | Copy |
|---|---|---|
| {{ p.key }} | {{ p.value }} | |
| No query parameters | ||
| # | Char | Code point | UTF-8 | ASCII | Unreserved | Reserved | Copy |
|---|---|---|---|---|---|---|---|
| {{ r.idx }} | {{ r.charDisplay }} | {{ r.u }} | {{ r.utf8 }} | {{ r.isASCII ? 'Yes' : 'No' }} | {{ r.isUnreserved ? 'Yes' : 'No' }} | {{ r.isReserved ? 'Yes' : 'No' }} |
Uniform Resource Locators are structured web addresses that may include percent escapes, query strings, and fragments, so reading them can be confusing when text is encoded or repeated. A web address decoder and cleaner turns dense links into clear text you can verify and share.
Paste any text or a full link and you get a decoded address when one is present and a readable string otherwise. You can remove common tracking parameters and tidy the host and path to match how people write links and avoid clutter, with the summary calling out how many trackers, duplicates, empty values, or blocked keys were removed.
Character inspection highlights each symbol so mixed encodings or copied artifacts stand out quickly. If the text hides structured data or an encoded blob you get a short preview for a quick look.
A compact summary shows which cleanup choices were applied, so runs remain comparable across cases. Treat results as a convenience and still check unknown links before opening them.
Uniform Resource Locator (URL) decoding converts percent escapes to characters, identifies scheme, host, path, query, and fragment, and returns a normalized display string for inspection. When the text is not a URL, the decoded string is still analyzed to aid review.
Character analysis reports per‑symbol properties: the Unicode code point, its UTF‑8 bytes as uppercase hexadecimal pairs, ASCII membership, and two flags indicating whether the character falls into the unreserved or reserved groups used by URL syntax.
The engine also checks the fully decoded string for two payload types: JavaScript Object Notation (JSON) and Base64‑encoded text. When detected, it renders a short preview and a summary with either line count or character count.
When the decoded text parses as a URL, optional normalizations can improve readability without altering meaning: host casing and www removal, path cleanup, fragment removal, and structured query operations including tracker removal, allow and block rules, duplicate handling, empty-value pruning, and sort order. Internationalized Domain Names (IDN) can be displayed in Unicode for the hostname only, and the tool counts how many parameters each sanitizer removed so changes are auditable.
http:// for parsing only.| Symbol | Meaning | Unit/Datatype | Source |
|---|---|---|---|
d |
Decode depth (max passes) | integer (1–12) | Input |
N |
Unicode normalization form | enum {NFC, NFKC, none} | Input |
cp |
Unicode code point | integer U+0000… | Derived |
u |
Parsed URL instance | object | Derived |
Q |
Ordered query pairs | list of [key, value] | Derived |
Input: https://www.Example.com:80//path/%7Eme/?utm_source=newsletter&id=42&id=9&ref=abc&empty=&q=a+b#top
Settings: depth 2; plus→space; Unicode NFC; show IDN in Unicode; remove default port; collapse slashes; trim trailing slash; remove fragment; lower‑case host; remove www; strip common trackers; de‑duplicate parameters (keep last); remove empty parameters; sort parameters.
Result: https://example.com/path/~me?id=9&q=a%20b
Interpretation: The link is safe to share without trackers, duplicates, or redundant formatting, and its path and host are canonicalized for readability.
| Field | Type | Min | Max | Step/Pattern | Error Text | Placeholder |
|---|---|---|---|---|---|---|
| Text or URL | text | — | — | — | — | https://example.com/?q=%2Bplus or example.com/%7Eme |
| Decode depth | number | 1 | 12 | step 1 | — | — |
| Treat “+” as space | checkbox | — | — | — | — | — |
| Unicode normalization | select | — | — | NFC, NFKC, none | — | — |
| Force scheme | select | — | — | (no change), http, https | — | — |
| De‑duplicate params | select | — | — | (off), keep first, keep last | — | — |
| Input | Accepted Families | Output | Encoding/Precision | Rounding |
|---|---|---|---|---|
| Text | Plain text, web address with or without scheme | Decoded string, character table, payload preview | UTF‑8; code points as U+XXXX; bytes as hex | Exact |
| URL | http, https, scheme‑less with example.com/path |
Normalized display URL, parameters | Re‑encoded with uppercase percent bytes | Exact |
| JSON/Base64 | Embedded in full string | Preview and downloadable text | Up to 100 000 characters in payload view | Exact |
http and https schemes.http:// only for parsing; display scheme follows options.utm_.:80 on http and :443 on https.Processing is browser‑based and no data is transmitted or stored server‑side.
Web address decoding and cleanup from input to a tidy, shareable result.
example.com/%7Eme?q=a%2Bb&utm_source=x, set depth 2 and plus‑as‑space, enable tracker removal, and copy the result http://example.com/~me?q=a%20b.
Pro tip: apply an allow‑list to keep only the keys that matter and discard the rest by default.
No. All decoding and normalization run locally and nothing is sent to a server. Clipboard and downloads occur only when you choose to use them.
Applies to text, links, previews, and QR output.ASCII membership and code points are exact. Unreserved and reserved flags follow internal patterns used for URL syntax. Component‑specific rules can still differ.
Interpret characters in the context of their URL part.Plain text and links with or without a scheme. Inputs with a dot or slash are parsed as links when possible; others are treated as text for analysis.
Scheme‑less parsing assumes http for detection only.Yes. Once the page is available, decoding and previews continue to work because processing happens in the browser.
Network access is not required for the core operations.Increase decode depth above one. The text is decoded pass by pass until it stops changing or the depth limit is reached.
Plus‑as‑space can help with form‑style values.These characters are commonly left unencoded in URLs. The flag helps you spot where encoding is optional versus required for safe transport.
Interpretation can vary by component.No licensing terms are shown in this package. Usage terms depend on how your instance is deployed by its host.
Check your environment’s policies if uncertain.Yes for http and https only. Opening is disabled for other schemes so you can review the text safely first.
Always verify unfamiliar targets before visiting.% followed by two hexadecimal digits.? used to pass parameters.# not sent to the server.