URL

Web search tool

URL decode online

Decode copied links, callbacks, and query parameter values so you can inspect what a request is really sending.

URL decode onlineURL decoderdecodeURIComponent onlinepercent decode
Output
Decoded

        

Examples for this search

Decode %2Fapp%2Fsettings into /app/settings.

Inspect nested redirect URLs.

Run a second decode if a value is double-encoded.

Component mode uses encodeURIComponent and decodeURIComponent. Full URL mode tries to preserve the URL structure while encoding or decoding path and query values.

Tool guide

What this url encoder decoder does

Use this URL encoder decoder when query parameters, OAuth callbacks, redirect URLs, or copied request strings contain spaces, percent escapes, plus signs, or double-encoded values.

Common use cases

  • Encode a single query parameter value before adding it to a URL.
  • Decode an OAuth redirect URL to inspect nested callback parameters.
  • Parse a query string into a key/value table.
  • Spot values that appear to be encoded more than once.

Accepted input formats

URL component hello world
Full URL https://example.com/callback?next=%2Fapp
Query string ?utm_source=docs&redirect=%2Fapp

How it works

Component mode uses encodeURIComponent and decodeURIComponent. Full URL mode tries to preserve the URL structure while encoding or decoding path and query values.

Common mistakes

  • Encode query parameter values, not an entire URL, when building a query string.
  • A plus sign is a literal plus in many contexts; form encoding may treat it as a space.
  • If decoding once still leaves percent escapes, the value may be double-encoded.
URL encoder decoderURL encode onlineURL decode onlinequery string parser
FAQ

Frequently asked questions

Should I use encodeURI or encodeURIComponent?

Use component mode for query parameter values. Full URL mode is for already assembled URLs.

Can this parse query strings?

Yes. Paste a URL or query string and Toolvert shows the parsed parameters.

Does it send URLs to a server?

No. Encoding, decoding, and parsing happen locally.