URL Encoder / Decoder

Percent-encode or decode a URL string.

Encode text for safe use in a URL, or decode a percent-encoded string back to plain text.

How it works

Encoding replaces characters that aren't safe in a URL (spaces, &, ?, non-English letters) with a % followed by their hex byte values. Decoding turns them back.

When it helps

Needed when putting text into query strings, debugging links, or reading encoded tracking URLs.

Which characters get encoded

Letters, digits and a few symbols like '-', '_', '.' and '~' are safe in URLs. Characters with a special meaning — such as '&' (separates parameters), '?' (starts the query), '#' (starts a fragment) and '/' — must be encoded when they appear inside a value. Spaces and non-English letters are always encoded.

Non-ASCII characters are first converted to UTF-8 bytes, so a single letter like 'ş' becomes %C5%9F.

Worked example

Searching for 'cafés & bars' on a site might produce the query string ?q=caf%C3%A9s%20%26%20bars. Without encoding, the '&' would be read as the start of a new parameter and the search would break. Decoding that string gives back the original text.

Marketing links with UTM parameters are often encoded twice by mistake, producing sequences like %2520. If you see that, decode twice to reach the original.

Frequently asked questions

Why does a space become %20?

20 is the hexadecimal code for the space character. In form data, spaces may also appear as +.

Should I encode the whole URL?

Usually only individual parameter values, not the full address.

Is URL encoding the same as encryption?

No. It only makes text safe to put in a URL; anyone can decode it.

Tools In Orbit · About · Contact · Privacy · Terms