URL utility

URL encoder and decoder

URLs can only contain a limited set of ASCII characters.

Encode and decode URLs

Encoding and decoding happen entirely in-browser.

Why this tool works well

  • Supports full URL mode and component mode.
  • Switch between encode and decode instantly.
  • Works locally with no server round-trips.
  • When building query strings manually for API testing, encode each parameter value separately before joining them. Encoding the entire URL at once can encode the delimiters, breaking the structure.
  • Decode a URL you received to inspect its parameters when the raw string is difficult to read. Percent-encoded values in analytics URLs or redirect chains become readable instantly.

Use cases

Query parameter prep

Encode values before building links.

Broken link debugging

Decode escaped URLs during diagnostics.

API tooling

Prepare encoded paths for test requests.

Practical examples

Component encode

Input: a b&c

Output: a%20b%26c

Decode URI

Input: hello%20world

Output: hello world

Suggested workflow

FAQ

What is full URL mode?

It uses encodeURI/decodeURI to preserve URL structure characters.

What is component mode?

It uses encodeURIComponent/decodeURIComponent for value-level encoding.

What is the difference between encodeURI and encodeURIComponent?

encodeURI encodes a full URL but preserves characters like / : ? & that have structural meaning. encodeURIComponent encodes everything including those characters and is used for individual parameter values.

Why does a space sometimes appear as + and sometimes as %20?

Both are valid in different contexts. %20 is the standard percent-encoding for a space. The + sign is used as a space only in application/x-www-form-urlencoded format, commonly seen in form submissions.

Related tools

Continue with closely related tools for faster multi-step workflows.

Recommended next actions

High-utility picks across categories based on current intent.