Skip to content
toolsbox

URL Encoder & Decoder

Percent-encode or decode URLs and inspect every part — host, path and query parameters.

  • Free
  • No sign-up
  • Runs in your browser

What is a URL encoder and decoder?

URL encoding, also called percent-encoding, replaces characters that are not allowed or have special meaning in a URL with a percent sign followed by two hexadecimal digits. A space becomes %20, an ampersand becomes %26 and a non-Latin letter becomes several percent-encoded UTF-8 bytes. A URL encoder applies that conversion; a decoder reverses it so you can read what a link really contains.

This tool offers two encoding modes that mirror JavaScript's built-in functions, and the difference matters. encodeURIComponent escapes everything except letters, digits and a few marks, including slash, question mark, ampersand and equals sign. Use it for a single value, such as a search term or a redirect target placed inside a query parameter. encodeURI leaves those structural characters alone and is meant for encoding a complete URL without breaking it apart. When decoding, an option treats plus signs as spaces, which is how HTML forms encode query strings.

Beyond plain conversion, a URL parser panel breaks any address into protocol, host, port, path, query parameters and fragment. Query parameters appear in an editable table, so you can change a key or value and rebuild the URL. The tool also flags double-encoding, such as %2520, a common sign that a value was encoded twice somewhere in a redirect or tracking chain.

How to encode or decode a URL

  1. 1

    Paste your text or URL

    Enter a full URL, a query string or a single value you want to encode or decode.

  2. 2

    Choose the encoding mode

    Pick encodeURIComponent for a value going inside a parameter, or encodeURI for a whole URL whose slashes, question mark and ampersands must stay intact.

  3. 3

    Decode with the right space handling

    When decoding form submissions or search URLs, enable the plus-as-space option so a query like red+shoes becomes red shoes instead of keeping the literal plus sign.

  4. 4

    Inspect the parsed URL

    Open the parser panel to see each component separately. Edit query parameter keys and values in the table, add or remove rows, and rebuild a clean URL.

  5. 5

    Watch for double-encoding warnings

    If the tool reports double-encoding, decode once more and trace where the extra encoding was added, often a CMS, redirect plugin or ad platform.

When to use a URL encoder

Auditing tracking and campaign URLs

Long ad and email links pile up UTM tags, click IDs and nested redirect targets. The parser table shows each parameter clearly, so you can spot a misspelled utm_source or a duplicated key before launch.

Debugging redirects and canonical tags

Inconsistent encoding can make one page reachable at two different URLs, such as a path with a literal accent and the same path percent-encoded. Decoding both shows whether they are actually the same address.

Building API requests

Query values with spaces, ampersands or slashes must be encoded with encodeURIComponent, or the server will split them into the wrong parameters.

Reading non-English URLs

URLs with Arabic, Cyrillic or Chinese slugs appear as long strings of percent codes in logs and crawl exports. Decoding them makes server logs and Search Console exports readable.

Fixing broken tracking chains

When analytics shows campaign names like summer%2520sale, double-encoding is the cause. The detector confirms it and points you to the layer that encoded the value twice.

encodeURI vs encodeURIComponent, and why double-encoding happens

The simplest rule: use encodeURIComponent for pieces and encodeURI for whole addresses. If you pass a full URL to encodeURIComponent, its slashes and colon become %2F and %3A and the link stops working as a link. If you pass a parameter value containing an ampersand to encodeURI, the ampersand stays raw and the server reads it as the start of a new parameter.

A classic case is a redirect parameter. If your login page sends users to a return URL that includes its own query string, that entire return URL must be encoded with encodeURIComponent before being added to the outer URL. Otherwise, the inner parameters leak into the outer query.

Double-encoding happens when already-encoded text gets encoded again. The percent sign in %20 becomes %25, producing %2520. It typically appears when several systems each try to be helpful: a CMS encodes a slug, a redirect rule encodes it again, then a tracking platform adds another layer. For SEO, this can create duplicate URLs, broken internal links and 404s that only show up in crawl reports, so fix the source rather than adding another decode step.

Frequently asked questions

Is the URL encoder free?

Yes, the URL encoder and decoder is free to use with no sign-up or limits. Both encoding modes, plus-as-space decoding, the URL parser with editable query parameters and the double-encoding detector are all available to everyone. It is built for developers, SEOs and marketers who regularly clean up tracking links, redirects and API requests.

Are the URLs I paste sent to your server?

No, everything runs locally in your browser and nothing is sent to our server. Encoding, decoding and URL parsing use JavaScript on your device, and the tool never requests the URLs you paste. That makes it safe for links containing session tokens, private document IDs or internal staging addresses that should not be shared.

Should a space be encoded as %20 or a plus sign?

Use %20 in URL paths and in most programmatic encoding, because it is valid everywhere in a URL. The plus sign means a space only in query strings submitted by HTML forms. When decoding, enable the plus-as-space option for form data or search URLs, and leave it off when a literal plus sign is meaningful, such as in phone numbers.

What does %2520 mean in a URL?

%2520 means a space was encoded twice. The first pass turned the space into %20, and a second pass encoded the percent sign as %25, producing %2520. The tool flags this automatically. Decoding once gives %20 and decoding again gives a space, but the real fix is removing the extra encoding step in your CMS, redirect rules or tracking setup.

Does URL encoding affect SEO?

Encoding itself does not hurt rankings, since search engines understand percent-encoded UTF-8 URLs. Problems come from inconsistency. If the same page is linked with encoded and unencoded versions, or double-encoded somewhere, you can end up with duplicate URLs, wasted crawling and broken links. Pick one consistent form and use it in canonical tags, sitemaps and internal links.

Can I edit query parameters and rebuild the URL?

Yes, the parser panel lists every query parameter in an editable table. You can change keys or values, add new parameters or delete unwanted ones such as stray click IDs, then rebuild the URL with correct encoding applied. This is faster and less error-prone than editing a long tracking link by hand.