URL Encoder & Decoder
Encode or decode URLs and query strings online. Convert special characters to percent-encoding (like %20) and back, instantly and free, right in your browser.
URL Encoder
Safe-encode URLs for web transmission.
Professional Grade Details
Instant Processing
Transformation happens client-side. No data ever leaves your device.
Unicode Support
Fully handles emojis and special characters via modern TextEncoder logic.
Lossless Sync
Switch between modes instantly without losing your original source material.
About this tool
Percent-encode text for safe use in URLs, or decode an encoded URL to read what it really says. Marketers dissect tracking links with it, developers debug malformed query strings, and anyone who's seen %20%3F%26 soup uses it to translate back to human.
How to Encode and Decode URLs
- 1
Paste either direction: plain text with spaces and special characters to encode, or an encoded URL riddled with percent signs to decode.
- 2
Convert — reserved characters become their %XX equivalents, or existing escapes collapse back into readable characters, with Unicode handled correctly both ways.
- 3
Copy the result into your link, query parameter, HTTP request, or investigation notes.
Why Handle URLs with Wrklyst
- Links Decoded Discreetly
- Everything happens in-page — the tracking URL you're dissecting or the parameter you're building is never itself sent anywhere.
- Correct on the Edge Cases
- Unicode, already-encoded fragments, and reserved characters are the places hand-encoding fails; the tool gets them right mechanically.
- Quicker than Documentation
- Faster to paste and convert than to re-look-up which characters need escaping — every single time.
URL Debugging Tips
- Encode parameter values individually, then assemble the URL — encoding the whole thing escapes your own & separators.
- ?, &, and = appearing inside a value are the classic sign encoding was skipped.
- Decode until stable to unwrap redirect chains one layer at a time.
- Non-Latin text in URLs becomes long %-sequences; that's correct behavior, not corruption.
Frequently asked questions
Why do URLs need encoding at all?
URL syntax reserves characters as structure: ? starts the query, & separates parameters, # marks fragments, / divides paths. When your data contains those characters — or spaces, which URLs forbid — they must be escaped as %XX codes so parsers read them as content rather than structure.
What's the difference between %20 and + for spaces?
Both represent a space, in different dialects: %20 is standard percent-encoding valid anywhere in a URL, while + means space only inside query strings, a legacy of HTML form submission. Decoding must respect context — a + in a path is a literal plus sign. When generating URLs yourself, %20 is always safe.
Why is my URL encoded twice, and how do I fix it?
Double encoding — where %20 becomes %2520 — happens when an already-encoded URL passes through another encoding step, typically in redirect chains or misconfigured code. Decode repeatedly until the output stops changing; the count of passes needed tells you how many layers deep the bug sits.
Can I use this to inspect tracking links?
That's a favorite use. Marketing and redirect links often nest a destination URL inside a parameter, encoded once or twice. Decoding reveals the true target and every UTM tag riding along, letting you audit where a link actually leads before clicking or verify your own campaign parameters survived intact.