Decode multi-encoded URLs, encode strings for safe embedding, and break any URL into its components — with automatic UTM and click ID detection.
URL encoding (percent-encoding) replaces unsafe characters in a URL with a % sign followed by two hex digits. For example, a space becomes %20 and an ampersand becomes %26. This ensures the URL is valid and parseable by browsers and servers.
Double encoding happens when an already-encoded string is encoded again. For example, %20 becomes %2520 (the % is encoded to %25). This is common when URLs are passed through multiple systems — like an ad server wrapping a tracking link that wraps a landing page URL. Multi-encoded URLs can break tracking parameters.
'Encode all' (encodeURIComponent) encodes every special character — use this when embedding a full URL as a parameter value inside another URL. 'Preserve URL structure' keeps the protocol, host, path, and delimiters intact while encoding only the query values — use this to clean up a URL without breaking its structure.
A common cause is double-encoding. If utm_source=google gets encoded to utm_source%3Dgoogle, analytics platforms can't parse it. Use the Decode tab to check if your parameters are over-encoded, and the Pretty Print tab to verify each parameter is correctly separated.
No. This tool runs entirely in your browser. Your URLs are never sent to any server — all encoding, decoding, and parsing happens locally using JavaScript.
Need a full link analysis?
Trace redirect chains, compare mobile vs desktop paths, and score link health.
Open LinkDecoder