Developer Tools New Tool

Free Online URL Encoder and Decoder, Component, Full URL & Query Parts

Percent-encode text for a URL or decode it back. Encode a single value the strict way for a query string, or a whole URL the lighter way that leaves the slashes alone, because the two are different and mixing them breaks links. It also splits a full URL into its protocol, host, path, query and fragment.

Free Forever Nothing Uploaded Component or Full Splits a URL

Free Online URL Encoder and Decoder, Component, Full URL & Query Parts

Advertisement Slot (Top Banner) Google AdSense Unit • Responsive Banner

URL Encode / Decode Everything happens in this tab. Nothing you paste is sent anywhere.

Your text or URL

Result

What to do Whole URL (leave the slashes alone)

Buy Us A Coffee

Enjoying WizTools123? Help keep our server infrastructure 100% free and open for everyone.

Buy Us A Coffee

Sponsored Content (Below Tool) Google AdSense Placement

Encoding a Value Is Not Encoding a URL

Mixing the two is how links quietly break.

Input	Encode for a URL (a value)	Whole URL
a/b c	a%2Fb%20c	a/b%20c
https://x.com/?q=a b	https%3A%2F%2Fx.com...	https://x.com/?q=a%20b

Encoding a value escapes the slashes; encoding a whole URL leaves them alone. A single value going into a query string, like a search term, must have its slashes, colons and question marks escaped, because those all mean something in a URL. A whole URL must keep them, because they are the structure. Use the value encoding for one piece you are inserting, and the whole-URL encoding to tidy a URL that has a space or an accent in it. Running the wrong one is how a working link turns into a 404.

The plus sign is decoded two different ways, and only you know which is right. In a normal URL path a plus is a literal plus. In form data submitted by a browser, a plus means a space. There is no way to tell from the text alone, so decoding leaves plus as plus by default and offers a switch to turn it into a space when the input is form data. Guessing would corrupt the other case.

Where Your Input Goes

Nowhere. And you can check that yourself.

A URL often carries a token, and this page never receives the one you paste. It is all done by your own browser. Press F12, open the Network tab, and use the tool: the page fetches its own code and nothing else. Or load the page, turn off your wifi, and carry on. It still runs, because there was never a server in the middle.

How to Encode and Decode a URL

A few steps, and nothing is uploaded.

Choose what you are doing Encode a value for a URL, decode one back, or split a whole URL into its parts.

Paste your input It converts as you type. Nothing is uploaded, so a URL with a token in it is safe here.

Pick value or whole URL when encoding A single query value escapes the slashes; a whole URL keeps them. Running the wrong one breaks the link.

Copy the result Or read the split table, which lists the protocol, host, path, each query parameter and the fragment.

What to Know About URL Encoding

Including the things this tool cannot do.

Encoding a value and encoding a whole URL are different jobs. A value going into a query string must escape its slashes, colons and question marks, because those are URL structure. A whole URL must keep them. Use the value mode for one piece you are inserting and the whole-URL mode to fix a space or accent in a link. The wrong one produces a broken address that looks almost right.

A plus sign is ambiguous when decoding, so it is left alone by default. In a URL path a plus is a literal plus; in browser form data a plus means a space. Nothing in the text says which, so decoding keeps plus as plus unless you switch on the form-data option. Guessing would silently corrupt whichever case you did not mean.

Splitting a URL uses the browser's own parser, which is stricter than a regex. The protocol, host, port, path, each query parameter and the fragment are pulled out the same way the browser does when it loads a page, so edge cases like an @ in the userinfo or an encoded character in the path are handled correctly rather than by a pattern that mostly works.

Never put personal data in a URL if you can avoid it, even encoded. Encoding makes a value safe to travel in a URL; it does not make it private. URLs end up in server logs, browser history, referrer headers and analytics. Encoding an email address or a token so it fits in a query string does not stop all of those places from recording it in full.

Key Features & Capabilities

What this tool does, and what it deliberately does not.

Value or whole URL Escape a single query value, or tidy a whole URL without touching its slashes.

Decode both ways With an option to turn plus into a space for form data.

Split a URL Protocol, host, path, every query parameter and the fragment, listed out.

Clear errors A bad percent sequence is reported instead of failing silently.

As you type No button. It converts while you edit.

Nothing uploaded A URL with a token in it stays in your tab.

About the URL Encode / Decode

Percent-encoding is what lets a space, an accent or a slash travel inside a URL. It comes up whenever you build a link by hand, debug a redirect, or read a value out of a query string, and it has one trap that catches almost everyone: there are two kinds of it, and they are not interchangeable.

Encoding a single value, like a search term going into a query string, escapes everything that has meaning in a URL, including the slashes. Encoding a whole URL leaves that structure alone and only escapes the stray spaces and accents. Run the value encoder on a full URL and every slash becomes %2F and the link dies. This tool keeps the two clearly separate and lets you pick.

It also decodes, with an honest choice about the plus sign, which means a space in form data and a literal plus everywhere else. And it splits a whole URL into its parts using the browser's own parser, so the protocol, host, path, each query parameter and the fragment come out correctly even in the awkward cases a quick regex gets wrong. All of it stays in your browser, which matters because URLs so often carry tokens.

Frequently Asked Questions

Value versus whole URL, the plus sign, and why encoding is not privacy.

You used the value encoder on a whole URL. The value encoder is for a single piece going into a query string, so it escapes slashes on purpose. To tidy a complete URL, switch on the whole-URL option, which leaves the structure alone and only escapes spaces and accents.

Only if the input is browser form data, where plus does mean space. In an ordinary URL a plus is a literal plus. Because the text cannot tell you which, decoding leaves it as a plus by default and gives you a switch to turn it into a space when you know it is form data.

No. Encoding only makes a value safe to travel in a URL. The URL, with the value in it, still ends up in server logs, browser history and referrer headers. Do not rely on encoding to hide an email address or a token; keep sensitive values out of URLs where you can.

It breaks a whole URL into its protocol, host and port, path, each query parameter as its own row, and the fragment. It uses the browser's URL parser, so it handles the awkward cases, like an @ in the address or an already-encoded character, the same way the browser does.

No. Everything happens in your browser. URLs frequently contain tokens and identifiers, and none of that leaves your tab, which you can confirm in the Network tab or by working offline.