URL Encoder Decoder

The URL Encoder Decoder handles percent-encoding — the %20s and %26s that make text safe to travel inside a URL. It offers the two modes that are constantly confused: component mode, which encodes everything reserved (use it for query parameter values and form data), and full-URL mode, which leaves a URL's structure intact and encodes only the unsafe characters. Decoding reverses either, with a clear error when a percent sequence is malformed.

0 characters · 0 words · 0 lines

Options

How to use URL Encoder Decoder

  1. Paste your text or encoded string into the box.
  2. Choose Encode or Decode, and Component or Full URL handling.
  3. Copy the result from the result box.

Supported behavior

  • Component mode uses encodeURIComponent rules: spaces become %20 and & becomes %26, so values cannot break a query string.
  • Full-URL mode uses encodeURI rules: the scheme, slashes, ? and & that structure the URL are preserved.
  • Decoding reports malformed percent sequences instead of guessing.

Best for

  • Building query strings and callback URLs by hand.
  • Reading encoded parameters in analytics and redirect URLs.
  • Preparing search terms and file names for links.

Limits

  • Double-encoded text (a %2520 in the wild) needs two decode passes — the tool decodes one level at a time so you can see each layer.
  • Plus signs: in query strings a '+' often means a space (form encoding), but percent-decoding alone does not convert it — decode twice with that in mind.

Privacy notes

  • Your text is processed locally in your browser and is never uploaded to a server.
  • URLs you inspect — tokens and all — stay in your browser.

Related tools

URL Encoder Decoder FAQ

What is the difference between Component and Full URL mode?

Component mode encodes the characters that have structural meaning (&, =, ?, /), making it safe for a single value inside a URL. Full URL mode preserves that structure and encodes only unsafe characters like spaces, so whole addresses stay readable.

Why did my link contain %2520?

It was encoded twice: %25 is an encoded percent sign, so %2520 decodes once to %20 and twice to a space. Decode step by step to peel the layers.

Does encoding turn spaces into '+' or '%20'?

This tool always uses %20, the universally valid percent-encoding. The '+' for spaces belongs to HTML form submissions (application/x-www-form-urlencoded), which browsers handle when a form is sent.