Map Extract
Free tool

URL encoder and decoder

Make text safe to put in a web address, or turn an encoded link full of %20, %26 and %3A back into something you can read. Choose whether you are encoding one value, a whole address or form data, because each needs different rules.

Runs in your browser. Nothing you enter is uploaded.

Three ways to encode the same search phrase

The phrase boiler repair & service, Leeds (24/7) shows why the choice matters. Only the first is safe to drop into a query string as one value.

OptionResultUse it for
Encode a value (encodeURIComponent)boiler%20repair%20%26%20service%2C%20Leeds%20%2824%2F7%29One parameter value or path segment
Encode a whole URL (encodeURI)boiler%20repair%20&%20service,%20Leeds%20(24/7)A complete address that only needs spaces and unsafe characters fixed
Encode for a form (spaces as +)boiler+repair+%26+service%2C+Leeds+%2824%2F7%29Data sent the way HTML forms send it

Encoding or decoding

  1. Paste the text or link

    A search phrase, a parameter value, a whole address or an encoded string. Presets offer a search phrase, an encoded link and an email subject line.

  2. Choose the action

    Encode a value, encode a whole URL, encode for a form, or decode. The result updates immediately.

  3. Check the output

    When encoding a value, every reserved character such as &, / and ? is encoded so it cannot break the address around it. When decoding, a stray % that is not part of a valid sequence produces a clear error rather than a garbled result.

  4. Copy or download

    Copy the result into your link, spreadsheet formula or email template, or download it as a text file.

Example: reading a link someone sent you

A tracking link in a supplier's email (fictional domain) has an address nested inside another, completely percent-encoded. Decoding it shows where it really goes: a search for tea rooms in Whitby on the supplier's own site. Checking a link this way before clicking it is a good habit.

Decoding a lone percent sign, such as 100% typed into a field, shows the error This contains an invalid % sequence instead of guessing.

Input
https%3A%2F%2Fwww.kitebrook.example%2Fsearch%3Fq%3Dtea%20rooms%26town%3DWhitby
Result
https://www.kitebrook.example/search?q=tea rooms&town=Whitby

Where small businesses meet encoding

You rarely notice URL encoding until something breaks. A WhatsApp or mailto link with a pre-filled message stops at the first ampersand. A link to a search on your own site loses everything after a hash sign. A spreadsheet that builds Google Maps search links for a list of towns produces addresses that open the wrong place. In each case the text inside the link needed encoding as a value.

The reverse is just as common: copying an address out of an email, an analytics report or an export and finding it unreadable. Decoding it shows what it really says.

Questions people ask

What is URL encoding?

URL encoding, also called percent encoding, replaces characters that are not allowed or have a special meaning in a web address with a percent sign and two hexadecimal digits. A space becomes %20, an ampersand becomes %26 and a pound sign becomes %C2%A3, because characters outside basic ASCII are encoded as their UTF-8 bytes.

What is the difference between encodeURI and encodeURIComponent?

encodeURIComponent encodes everything that could interfere with an address, including /, ?, & and =, so it is right for a single value inside a link. encodeURI leaves those characters alone because it assumes you are passing a whole address. Using encodeURI on a value is a common cause of broken query strings.

Should a space be %20 or a plus sign?

Both appear. In paths and most of an address, a space must be %20. In query strings sent by HTML forms, a plus sign also means a space, which is what the form option produces. When in doubt, %20 is understood everywhere, while a plus sign in a path is read as a literal plus.

Why do I get an invalid % sequence error when decoding?

A percent sign in encoded text must be followed by two hexadecimal digits. Text such as 100% or %ZZ cannot be decoded, so the tool stops and says so instead of producing a corrupted result. Encode the text first if the percent sign is meant literally.

Where your data goes

Encoding and decoding happen in your browser as you type. Nothing is sent to Map Extract or anywhere else, and no link is opened.

Checked against the tool on

Top