URL Encode

URL Encode / Decode Online: The Only Guide You’ll Need

Ever copied a link into a browser bar and watched spaces turn into %20, or pasted a search query into an API request and had it silently break? That’s URL encoding at work — and if you’ve ever needed to fix, inspect, or generate one of these strings, you already know how fiddly it can get by hand.

This guide walks through what URL encoding actually does, when you need it, and how to handle it whether you’re working online, in JavaScript, in Python, or with an npm package — plus where to do it instantly with a free URL encode decode online tool.

What is URL encoding?

URLs can only safely contain a limited set of characters — letters, digits, and a handful of symbols like -, _, ., and ~. Everything else (spaces, &, ?, #, non-English characters, emoji) has to be converted into a %XX sequence, where XX is the character’s hex byte value. A space becomes %20, an ampersand becomes %26, and so on. This process is formally called percent-encoding, though most people just call it “URL encode.”

URL decode is simply the reverse: turning %20 back into a space, %26 back into &, and reconstructing the original readable text.

Why you’d need to url encode decode online

A few common situations where this comes up:

• Building query strings — passing user input, search terms, or filter values through a URL without breaking the request.
• Debugging API calls — decoding a mangled parameter to see what was actually sent.
• Sharing links — encoding URLs that contain spaces, accented characters, or symbols so they don’t break when pasted into email or chat.
• Working with legacy systems — some tools double-encode or mis-encode data, and you need to manually decode it to trace the issue.

For quick, one-off jobs, opening a code editor is overkill. That’s exactly the gap a browser-based url decode online tool fills — paste the string, get the result, done. InspoTool’s URL Encode/Decode tool runs entirely client-side, so nothing you paste in ever leaves your browser.

URL encode decode javascript

JavaScript has this built in — no libraries needed:

// Encode
const encoded = encodeURIComponent("hello world/foo?bar=1");
console.log(encoded); // hello%20world%2Ffoo%3Fbar%3D1

// Decode
const decoded = decodeURIComponent(encoded);
console.log(decoded); // hello world/foo?bar=1

Two functions matter here, and mixing them up is the most common mistake:

• encodeURIComponent() encodes everything that isn’t a letter, digit, or - _ . ! ~ * ' ( ). Use this for individual values you’re inserting into a query string (a search term, a filename, a piece of user input).
• encodeURI() leaves reserved URL characters like /, ?, &, and : untouched, because it assumes you’re encoding a complete URL, not a single value. Use this when encoding a full link rather than one parameter.

Decoding uses the matching pair: decodeURIComponent() and decodeURI().

URL encode decode python

Python’s standard library handles this through urllib.parse:

from urllib.parse import quote, unquote

encoded = quote("hello world/foo?bar=1")
print(encoded)  # hello%20world%2Ffoo%3Fbar%3D1

decoded = unquote(encoded)
print(decoded)  # hello world/foo?bar=1

A couple of Python-specific notes:

• quote() encodes spaces as %20 by default. If you need the older +-for-space convention (common in form submissions), use quote_plus() and unquote_plus() instead.
• For encoding a full dictionary of query parameters at once, urllib.parse.urlencode({"q": "hello world", "page": 2}) builds the whole query string for you.

URL encode decode npm

If you’re working in Node.js, the built-in encodeURIComponent/decodeURIComponent functions (same as browser JavaScript) usually cover it — no install required. For more advanced query-string handling, two popular npm packages fill in the gaps:

npm install query-string

import queryString from "query-string";

const encoded = queryString.stringify({ q: "hello world", page: 2 });
// q=hello%20world&page=2

const parsed = queryString.parse("q=hello%20world&page=2");
// { q: "hello world", page: "2" }

query-string (and the similar qs package) are worth reaching for when you’re building or parsing entire query strings with multiple parameters, arrays, or nested objects — territory where manual encodeURIComponent calls get repetitive fast.

Doing it online, without writing any code

Not every situation calls for opening an editor. If you just need to convert a string once — checking what a tracking link decodes to, cleaning up a URL before sharing it, or prepping a value for a spreadsheet — a browser tool is faster than spinning up a script.

InspoTool’s URL Encode / Decode tool covers exactly that use case:

• Switch between Encode and Decode modes, or let it auto-detect which one you need
• Live preview as you type
• Runs 100% client-side — nothing is uploaded or logged
• Copy or download the result directly
• No signup, no limits, works on mobile

It sits alongside similar utilities — HTML Encode, Base64 Encode/Decode — in InspoTool’s text tools collection, so if URL encoding turns out not to be exactly what you needed, the related tool is one click away.

Quick reference

Whichever route you take, the underlying idea is the same: percent-encoding exists so that URLs can carry any character safely. Pick the method that fits where you’re already working — code when you’re scripting something repeatable, an online tool when you just need the answer right now.

URL encoder/decoder FAQ