URL Encoder/Decoder

Encode or decode URL components. Required for building safe URLs with special characters.

Web · percent-encoding · query strings

URL-encode and decode strings for query parameters, path segments, and form bodies. Percent-encoding runs in your browser so you can safely prepare values that contain spaces, unicode, or reserved characters.

Encode & decode Query-safe strings Unicode aware Client-side API debugging

Why encoding exists

URLs can only reliably carry a limited character set in certain components. Spaces, &, =, non-ASCII text, and other reserved characters must be percent-encoded (e.g. space → %20 or + in some form encodings). Decoding reverses the process for readability.

How to use this tool

  1. Paste the raw string (encode) or an encoded string (decode).
  2. Run encode or decode and copy the result.
  3. Place encoded values into query parameters or path segments as appropriate.
  4. For full URL surgery, also see the Query String Parser.

Encode vs components

API / conceptTypical use
encodeURIComponentQuery values & path segments (encodes &, =, etc.)
encodeURIWhole URLs — leaves structural characters
application/x-www-form-urlencodedForms; spaces often become +

Rule of thumb: When building ?q=… values, use component encoding. Double-encoding (%2520) usually means something encoded twice by accident.

Examples

Raw:    hello world & friends
Encoded: hello%20world%20%26%20friends

Raw:    café
Encoded: caf%C3%A9

Common pitfalls

FAQ

Is this the same as Base64?

No. Base64 is a different encoding for arbitrary bytes as text. Use the Base64 tool for that.

Is my string uploaded?

No — encode/decode are local. Privacy Policy.

Why does decode fail?

Malformed % sequences (e.g. truncated %C3) throw errors. Check the source for cut-off copies.

Related tools

Query String Parser Base64 Encoder HTML Entities cURL → fetch

Part of DevToolBox — free developer utilities that run in your browser. About · Privacy

Sponsored