Getting your tools ready…

176 free tools · PDF, images, calculators & more
{/* Tool-first layout (2026-11-14): slim hero — kicker + H1 only. The lead, author byline, published line and pills moved below the tool; nothing sits between the H1 and the tool fields. */}

DEVELOPER FLAGSHIP

URL Encoder Decoder

{/* Tool prominence (54.97.52): the shell tool section is wrapped in the same distinct card as the React surface — soft tint, visible border, soft shadow — so the served HTML shows the card before hydration. */}

At a glance

URL Encoder / Decoder — URL Encoder & Decoder fixes the exact moment a link breaks: a space, an ampersand, or a question mark inside a value that the browser reads as structure instead of text.

Free for the core workflow, no account required. Parsing and transformation are performed locally in the browser from the data you enter.

About URL Encoder / Decoder

URL Encoder & Decoder fixes the exact moment a link breaks: a space, an ampersand, or a question mark inside a value that the browser reads as structure instead of text.

A URL has two kinds of characters: structure (?, &, =, /, #) and data. The moment data contains a structural character, the URL means something different from what you intended — a search for "coffee & tea" becomes a search for "coffee " plus a parameter called " tea". Percent-encoding solves it by replacing each risky byte with % plus two hex digits. Worked example — take the search URL https://example.com/search?q=coffee & tea. Encoding just the value "coffee & tea" gives coffee%20%26%20tea: the space becomes %20 and the ampersand becomes %26. The finished URL is https://example.com/search?q=coffee%20%26%20tea, and the server reads one parameter, q, with the value "coffee & tea". Encode the whole URL instead and you destroy it: the :// and ? get encoded too, and nothing can parse the result. The boundary rule is the whole skill — encode values where the URL is built, decode where it is read, exactly once each way. Table — characters that must be encoded inside a query value: space becomes %20, & becomes %26, = becomes %3D, ? becomes %3F, # becomes %23, + becomes %2B, and % itself becomes %25. A literal + in a query is read as a space by form decoding, which is why "C++" arrives as "C " when it is not encoded. Before / after — before: https://example.com/search?q=coffee & tea (broken: the & splits the query in two); after: https://example.com/search?q=coffee%20%26%20tea (one parameter, correct value). The diagram to keep in mind is a fence: everything left of the ? is the address, everything right of it is data, and encoding is what keeps data from climbing the fence. One developer step usually leads to the next. The JSON Path Explorer queries into a JSON document the way a search query finds rows in a database and the Regex Tester runs JavaScript regular expressions against your real text with live match highlighting. Finally, the URL Parser takes a complete web address apart into its labelled pieces. Sources: RFC 3986, Uniform Resource Identifier (2005); MDN Web Docs, "encodeURIComponent()" (accessed November 2026). Content last reviewed: November 2026. Percent-encoding replaces reserved characters with %XX sequences so they survive transport in URLs. The critical distinction this tool handles: encodeURIComponent (for query values) versus encodeURI (for whole URLs) — mixing them up is the source of most double-encoding bugs.

Primary objective: URL component encoding and decoding locally in the browser.

Privacy assurance: Parsing and transformation are performed locally in the browser from the data you enter.

How to Use URL Encoder / Decoder

  1. Paste the full URL or the single value you need to fix — values are the usual problem, not whole URLs.
  2. Choose Encode for a value going into a query string, or Decode when a log or an error message shows you %XX sequences.
  3. For a query value, encode with the component rules (spaces become %20); for a whole URL, encode only the parts that are data.
  4. Check the output: every & inside a value should now read %26, and the ? that starts the query must still be a plain ?.
  5. Paste the finished URL into a browser or API client and confirm the server receives the value you intended.

Key Use Cases & Applications

  • Fixing a search or filter link where a product name contains & or +.
  • Building an API call with a user-typed query that includes spaces and punctuation.
  • Reading a server log where %20 and %26 hide the original search terms.
  • Preparing a redirect URL that itself contains a query string as a parameter value.
  • Encoding search queries with special characters for API calls.
  • Decoding garbled %XX sequences in server logs to read the original input.

Frequently Asked Questions

Why does my search lose everything after the &?

Because & separates query parameters. A value of "coffee & tea" is read as q=coffee plus a second parameter. Encode the value so & becomes %26 and the whole phrase stays inside q.

When should I use %20 and when is + okay?

In a query string built by a form, + means space. Everywhere else, %20 is the safe encoding for a space — use %20 unless you know the receiver decodes form-style plus signs.

My API returns %2520 — what went wrong?

The value was encoded twice: % became %25, so %20 turned into %2520. Decode once to get back to %20, then find the extra encoding step in your code and remove it.

Do I need to encode a password inside a URL?

Avoid putting passwords in URLs at all — they land in logs and browser history. If a value must travel that way, encode it, but prefer a header or a POST body.

By Shehzad Hussain — owner and editor of ExpTool, based in Multan, Pakistan. He builds and tests every tool on this site himself.

Last updated: 2026-11-04