Skip to content
search-engine-optimizedby Netsolution
  1. Home
  2. Utilities
  3. URL Encoder / Decoder

URL Encoder / Decoder

Make your URLs transmissible, or make an unreadable address readable.

Processed locally in UTF-8, following RFC 3986. No data is transmitted or stored. No usage limit.

What this tool is for

A web address can only contain a restricted set of characters. No space, no accent, and few punctuation marks. Everything else has to be encoded: replaced by a percent sign followed by a hexadecimal code.

That encoding is invisible as long as it works. It becomes visible the moment it fails: a link that breaks, a truncated parameter, an accent turned into a run of symbols. Those failures nearly always come from a value that was not encoded, or was encoded twice.

This tool does both operations and flags the particular case that plagues developers most: double encoding, when a string that is already encoded gets encoded a second time by another layer of the system.

The sign that should alert you: the presence of %25 in a URL. That is the encoding of the percent character itself, so the symptom of a string encoded twice.

How to read the results

The encoded result should contain only safe characters. Every sequence beginning with a percent sign represents one byte of the original text — an accented character takes two in UTF-8, hence the length.

The decoded result restores the original text. If it still contains percent sequences, the string was encoded several times: decode again.

The scope changes everything. “Parameter value” also encodes slashes and ampersands, which is necessary for a value. “Whole URL” preserves the structure of the address.

The double-encoding warning appears when the string contains %25. It is the most useful diagnosis this tool offers, and the cause of a great many broken links that the redirect checker reveals from the other side.

Common mistakes

Encoding the whole URL instead of the values. The structural colons and slashes then become unreadable to the server, and the address stops working.

Encoding twice. Every application layer believes it has to encode. The result is a link that points elsewhere or returns an error.

Forgetting the ampersand inside a parameter. An unencoded ampersand in a value is read as a parameter separator: everything after it is treated as a new parameter.

Using accents in slugs. It works, but the shared address becomes unreadable. Prefer unaccented slugs.

Confusing URL encoding with HTML encoding. & belongs to HTML, %26 to the URL. Mixing them produces strings that work in neither context.

Going further

Frequently asked questions

Why does my URL contain %20?

Because a URL cannot contain a space. Every forbidden character is replaced by a percent sign followed by its hexadecimal code: a space becomes %20, an at sign %40, the é of “référencement” becomes %C3%A9 in UTF-8. That is percent-encoding, provided for by the URL standard.

When do I need to encode?

As soon as a value contains anything other than unaccented letters, digits, a hyphen, a dot, an underscore or a tilde. It is indispensable for query parameters, where a single unencoded ampersand breaks the interpretation of the whole address.

What is double encoding?

Encoding a string that is already encoded: the percent sign of %20 is itself encoded and becomes %2520. The link breaks or points elsewhere. It is the most frequent failure on this subject, and it nearly always comes from a value encoded twice by two different application layers.

Should I encode the whole URL or only the parameters?

Only the values. Encoding the full address would transform the structural colons, slashes and ampersands, which have to stay readable. Each parameter value is encoded separately, before assembly.

Are accented URLs a problem for SEO?

Technically they work, and Google handles them. But once shared they appear percent-encoded: “référencement” becomes “r%C3%A9f%C3%A9rencement”, unreadable and unappealing. Better to use unaccented slugs.

Space as %20 or as a plus sign?

Both exist, depending on context. The plus sign comes from HTML forms and only holds in the query part of a URL. %20 is valid everywhere. When in doubt, use %20: it works in every case.