Free URL Encoder & Decoder
Percent encode a query value or a full URL, or decode %20 and + back into readable text. Paste a link and see its protocol, host, path and every query parameter. It runs entirely in your browser, so nothing is uploaded.
Component encodes everything, use it for a single query value. Full URL keeps : / ? & = intact, so a whole link still works.
Handy for a quick encode or a link check. Test the final URL in a browser before you ship it.
Encode or decode in four steps.
Pick a direction, set the mode, type or paste, then copy or download the result. It updates live as you type.
Pick a direction
Choose Encode to turn plain text into a safe URL string, or Decode to turn %20 and friends back into readable text. The swap button flips direction and carries your result over.
Set the mode
When encoding, pick Component for a single query value or Full URL to keep a whole link working. When decoding, you can treat + as a space for form-encoded strings.
Type or paste
The result updates live as you type. Paste a full URL and the breakdown panel shows the protocol, host, path and each query parameter with its decoded value.
Copy or download
Copy the result in one tap, or download it as a .txt file. Everything happens on your device, nothing is sent to a server.
An encoder that knows the difference.
Encoding a whole URL and encoding one query value are different jobs, and mixing them up is how links break. This tool keeps the two apart and shows you exactly what changed.
Two encode modes
Component mode uses encodeURIComponent and encodes everything, right for a value going into a query string. Full URL mode uses encodeURI and keeps : / ? & = intact, so a complete link still works after encoding.
Forgiving decoder
Decodes percent sequences back to plain text, with an option to treat + as a space for form-encoded strings. A malformed sequence gets a clear message instead of a cryptic failure.
URL breakdown
Paste a full URL and see it taken apart: protocol, host, path, and a table of every query parameter with its decoded value. Handy for debugging a link that misbehaves.
Private by design
It runs entirely in your browser. Nothing you paste is sent to a server, so links with tokens, session IDs or internal hostnames stay on your own machine.
Links that never break.
A quick encode is fine for one link. But if your product builds URLs all day, campaign links, redirects, share links, signed download links, that logic belongs in your own codebase, tested once and trusted everywhere. That is the kind of web engineering we do at Techliphant, shaped around how your product actually works.
Working with encoded data too? Try the Base64 encoder and decoder.
Common questions.
URLs can only carry a limited set of characters safely. Percent encoding replaces everything else with a % followed by two hex digits, so a space becomes %20 and an ampersand becomes %26. The receiving end decodes the sequence back to the original character.
Whenever you put user text or data into a link: a search term in a query string, an email address in a mailto link, a redirect URL inside another URL. If the value can contain spaces, &, =, ? or # and you do not encode it, the URL breaks or the value gets cut off at the wrong character.
Component mode (encodeURIComponent) encodes everything that is not a plain letter, digit or a few safe marks, including : / ? & and =. Use it for a single value, like one query parameter. Full URL mode (encodeURI) leaves those structural characters alone, so an entire link keeps its shape while spaces and other unsafe characters still get encoded.
Both are real. %20 is the standard percent encoding for a space and works everywhere in a URL. The + convention comes from HTML form submissions, where a space in a form field is sent as + in the query string. That is why this tool has a "treat + as a space" option when decoding.
Reserved characters like : / ? # & = have a job inside a URL, they mark where one part ends and the next begins. They only need encoding when they appear as data rather than structure. Unsafe characters like spaces, quotes and anything outside ASCII have no place in a raw URL at all, so they always need encoding.
Double encoding happens when an already encoded string is encoded again, so %20 becomes %2520 because the % itself was encoded to %25. The giveaway is %25 followed by two more hex digits. Decode the string twice here and you will see whether one pass or two brings back readable text.
Modern browsers show them, but under the hood they travel percent encoded as UTF-8 bytes. A single Devanagari character becomes three %XX sequences and an emoji becomes four. This tool encodes and decodes them correctly, so you can round-trip any language.
No. The whole tool runs in your browser using JavaScript. Nothing you type or paste leaves your device, which matters when a URL carries an access token, a session ID or an internal address.
Yes. A quick encode or decode is handy, but if your team builds links, redirects or tracking URLs every day, that logic belongs inside your own software, tested and consistent. That is the kind of web and integration work we do at Techliphant.
Private by design: this tool runs entirely in your browser, so nothing you type or paste is sent anywhere or stored. URLs with tokens, session IDs or internal hostnames stay on your own device. It is provided free for quick encoding, decoding and link checks.
Ready when you are
Let's build something exceptional.
Tell us about your business, your stack, and the problem you are trying to solve. We respond with a clear next step usually a 30-minute discovery call, no fluff.