I'll never forget the afternoon a client's "share this product" link broke for every user with an accent in their name. The URL contained "José," the receiving server saw garbage, and the page 404'd. The fix was one line — percent-encode the parameter — but it taught me something permanent: URLs only safely carry a limited set of characters, and everything else (spaces, ampersands, non-Latin letters) must be encoded before a link is safe to send. This tool does that conversion in both directions: encode messy text into URL-safe form, or decode a cryptic percent-encoded string back into readable text.
What Is URL Encoding?
URL encoding — also called percent-encoding — rewrites unsafe characters as a % followed by two hexadecimal digits. A space becomes %20, an ampersand becomes %26, a question mark becomes %3F. Non-ASCII characters like é or 中 are first converted to their UTF-8 bytes, and each byte gets its own %XX sequence.
Why the fuss? Because certain characters have jobs in a URL. The ? starts the query string, & separates parameters, = joins keys to values. If your search term itself contains an ampersand — say you're searching for "salt & pepper" — the raw & would be read as a parameter separator, splitting your search into two broken pieces. Encoding it as %26 tells every browser and server: this is data, not structure.
Decoding is the reverse trip: turning hello%20world back into hello world so you can read what a link actually contains — useful when you're debugging redirects, inspecting shared URLs, or auditing what parameters a page is passing around.
How to Use the URL Encoder Decoder
Paste your text or URL into the input box. If you're encoding, choose the right mode: component mode for a single value (a query parameter, a path segment), full URL mode for a complete address that's already structured. Click Encode or Decode, and the result appears in the output area, ready to copy.
The mode choice is the one decision that matters. Component encoding escapes everything with a structural job — ?, =, &, / all get encoded — because inside a single value, none of them are structure. Full-URL encoding preserves those characters so your address keeps working. Encoding a whole URL in component mode breaks it; encoding a parameter value in full-URL mode leaves dangerous characters raw.
Use the Swap button to flip input and output when you're working back and forth — encode, check, decode, re-encode — which is exactly the rhythm of debugging a stubborn redirect chain.
Component vs. Full URL Encoding
This table shows the same input through both methods, so the difference is concrete:
| Input | Component encoding | Full URL encoding |
|---|---|---|
hello world | hello%20world | hello%20world |
salt & pepper | salt%20%26%20pepper | salt%20&%20pepper |
https://example.com/a b?x=1 | https%3A%2F%2Fexample.com%2Fa%20b%3Fx%3D1 | https://example.com/a%20b?x=1 |
café | caf%C3%A9 | caf%C3%A9 |
Notice the pattern: component mode encodes the structural characters (:, /, ?, =, &) while full-URL mode leaves them alone. The rule of thumb: encoding a value someone typed into a form or a search box? Component. Encoding a complete link you want to keep clickable? Full URL.
One more encoding you'll meet: spaces as +. In HTML form submissions (application/x-www-form-urlencoded), spaces are traditionally written as plus signs rather than %20. Most decoders handle both, but if you're decoding form data and seeing literal plus signs, that's why — the tool's "treat + as space" option covers this case.
Common Encoded Characters Reference
| Character | Encoded | When you'll see it |
|---|---|---|
| space | %20 | Search terms, file names |
& | %26 | Inside a parameter value |
? | %3F | Inside a value, not as query starter |
= | %3D | Inside a value, not as key-value joiner |
/ | %2F | Inside a path segment value |
# | %23 | Hashtags in shared text |
% | %25 | A literal percent sign in data |
+ | %2B | Phone numbers, math expressions |
Who Uses a URL Encoder Decoder?
Web developers encode query parameters before building API calls and decode opaque URLs while debugging. It's a daily-use utility in any shop that builds links programmatically.
Digital marketers encode UTM parameters and campaign URLs before pasting them into emails and ads, where a raw ampersand or space silently breaks tracking.
SEO specialists audit redirect chains and canonical URLs, decoding percent-encoded addresses to verify they point where intended.
QA testers verify that forms and search boxes handle special characters — typing "fish & chips" into a search and confirming the URL encodes correctly is a standard test case.
Key Features
- Two-way conversion — encode text to percent-encoding, decode it back.
- Component & full-URL modes — the right method for values and for whole addresses.
- UTF-8 aware — accented letters and non-Latin scripts encode correctly.
- Instant results — output updates as you type or paste.
- Swap, copy, clear — one-click actions for back-and-forth workflows.
- 100% free — no account, no limits.
- Private by design — runs on your browser's native encoding functions; nothing is uploaded.
- Works everywhere — any modern browser, desktop or mobile.
Frequently Asked Questions
Is this URL encoder decoder free?
Yes — free, no signup, unlimited use.
What's the difference between encode component and encode full URL?
Component encoding escapes structural characters (?, &, =, /) — use it for a single value. Full-URL encoding preserves them — use it for a complete address.
Why is there a %20 in my URL?
That's an encoded space. Spaces aren't allowed raw in URLs, so they're written as %20 (or + in form data).
What does %26 mean?
An encoded ampersand (&). It appears when the ampersand is data inside a value rather than a parameter separator.
Should I encode the whole URL or just the parameters?
Just the parameter values, with component encoding. Encoding a whole URL with component mode breaks its structure.
Is URL encoding the same as encryption?
No. Encoding only changes the representation so characters travel safely — anyone can decode it. It adds zero security.
Why do I see + instead of %20 sometimes?
HTML forms traditionally encode spaces as +. Both mean "space"; use the "treat + as space" option when decoding form data.
Is my data uploaded anywhere?
No. Encoding and decoding run entirely in your browser using its built-in functions.
Frequently asked
Browsers often auto-decode URLs in the address bar, making it hard to see the raw encoded string for debugging API calls or redirect parameters. This tool gives you the exact raw output.