url-decode.com

Use this table to check the percent-encoded form of common special characters before you decode or troubleshoot a URL. Each character is replaced by a percent sign followed by its hexadecimal code — for example, ! becomes %21, # becomes %23, and ? becomes %3F. These characters need encoding because they play structural roles in a URL, so leaving them raw can break how a link is parsed.

Character-to-Encoding Reference

The following pairs come from the reference table published on url-decode.com. The left column is the literal character; the right column is its encoded form.

The same source also gives three everyday examples: a space becomes %20, a forward slash / becomes %2F, and a colon : becomes %3A.

Why These Characters Need Encoding

URL encoding and decoding exist so that addresses and data pass correctly between browsers, servers, and APIs. The characters in the table are not arbitrary — they carry structural meaning inside a URL. ? starts a query string, & separates parameters, # marks a fragment, / separates path segments, and : separates a scheme from the rest of the address. If these appear unencoded where they are meant to be data, the URL can be misread, break, or fail to pass data between systems.

Encoding replaces each such character with a standardized percent-encoded sequence, so the URL keeps its structure while the data travels intact. Decoding reverses the process for people who need to read, edit, share, or troubleshoot the link.

Worked Example

An encoded URL such as:

http%3A%2F%2Furl-decode.com%2Ftool%2Furl-decode

decodes to:

http://url-decode.com/tool/url-decode

Reading it against the table: %3A → :, %2F → /. The result is a normal, human-readable address.

Checking a Decoded Result

After decoding, compare the output against the table above rather than assuming it is correct:

• Structural characters restored in the right places. A decoded : should sit after the scheme (http:), and / should separate path segments. If a %2F was meant to be literal data inside a parameter, decoding it to / may change how the URL is interpreted.
• Spaces look right. %20 should come back as a space. If the output shows a literal + where you expected a space, note that + has its own encoding (%2B) and is not the same as %20.
• No leftover percent sequences. If % codes remain, the input may have been double-encoded or only partially decoded.
• Brackets and reserved symbols match the source. [ and ] should return as %5B and %5D when encoded; seeing them raw in an encoded string is a sign to re-check the input.

For multi-line input, url-decode.com offers a "Decode each line separately" option, which is useful when you have several entries and want each one decoded on its own line. You can paste encoded text, load it from a URL, or upload a text file, then copy or download the result.

Quick Decision Guide

• Decoding a single link to read it: paste it into the decoder and check the output against the table.
• Decoding a batch of links or parameters: enable per-line decoding so entries stay separated.
• Encoding a value for use in a query string: replace each character in the table with its encoded form, and remember that a space is %20.
• Unsure whether a character is safe raw: if it appears in the table, encode it when it is meant as data rather than URL structure.

URL encoding and decoding are necessary because certain characters—such as :, /, ?, &, and spaces—have structural meaning inside a URL. If they appear as literal data, browsers, servers, and APIs can misread where one part of the address ends and another begins. Encoding converts those characters into percent-encoded sequences (for example, a space becomes %20), while decoding turns them back into readable text so people can inspect, edit, share, and troubleshoot links.

The structural problem: reserved characters

A URL is not free-form text; it is a structured address. Characters like / separate path segments, : separates the scheme from the host, ? starts the query string, and & separates query parameters. When one of these characters is part of the actual data rather than the structure, using it literally causes the URL to be parsed incorrectly.

The URL Decoder reference lists the characters that must be encoded before use in a URL, including:

For example, a query value that itself contains & would otherwise look like the start of a new parameter. Encoding it as %26 keeps it as data.

What encoding guarantees across systems

URL encoding replaces reserved and unsafe characters with standardized percent-encoded sequences. This matters because the same URL may pass through a browser, a server, a proxy, and an API. Each of those systems parses the address independently. A standardized encoding removes ambiguity, so the data arrives intact instead of being split, truncated, or rejected.

The url-decode.com page states the purpose directly: encoding helps ensure URLs are transmitted correctly across the web, and without it, URLs containing special characters may break, become unreadable, or fail to pass data correctly between systems.

Why decoding is equally necessary

Encoded URLs are hard for humans to read. A link like:

http%3A%2F%2Furl-decode.com%2Ftool%2Furl-decode

is technically valid but difficult to verify at a glance. Decoding converts it back to:

http://url-decode.com/tool/url-decode

The site describes decoding as translating encoded characters back to their standard form—%3A to :, %2F to /, %20 to a space—which makes URLs easier to inspect, edit, share, and troubleshoot. That readability is the practical reason decoding is used in debugging redirects, checking tracking links, and reviewing form or API data.

When to encode and when to decode

• Encode when you are building a URL and inserting user input or data that may contain reserved characters—search terms, file paths, redirect targets, or parameter values.
• Decode when you receive or encounter a percent-encoded string and need to understand what it actually points to, or when you are diagnosing why a link behaves unexpectedly.

A common failure pattern is double-encoding or decoding at the wrong stage: a value encoded twice shows up with %25 sequences, and decoding only once leaves it still partially encoded. Checking the decoded output against the expected plain URL is a quick way to catch this.

Practical takeaway

Treat encoding as a transmission requirement and decoding as a readability and verification step. If a link contains %20, %2F, or %3A, it has been encoded for transport; decode it before you read, edit, or share it, and encode any raw special characters before you place them into a URL.

Paste the encoded URL into the Input box on url-decode.com and the readable version appears in Decoded Result; if you have several encoded entries, tick Decode each line separately first so each line is handled on its own. You can then copy the result or download it, and the same page also offers an Encode action for the reverse direction.

Decoding a single encoded URL

1. Open url-decode.com. The page shows an Input area at the top and a Decoded Result area below it.
2. Paste your encoded link into Input. For example, paste http%3A%2F%2Furl-decode.com%2Ftool%2Furl-decode.
3. Read the converted link in Decoded Result. The example above becomes http://url-decode.com/tool/url-decode.
4. Copy the result, or use the download option to save it.

The page also provides a Sample you can load to see how the tool behaves before using your own data, and a Load From URL option if the encoded text lives at a web address rather than in your clipboard. A character counter next to each box shows how much text is currently in it.

What the encoded pieces mean

Decoding simply maps percent-encoded sequences back to the characters they stand for. The common ones:

So a query string like search%3Fq%3Durl%2Bdecoder decodes to search?q=url+decoder, which you can read and edit directly.

Decoding multiple lines at once

If your input contains one encoded entry per line — for example a list of tracking links or redirect targets exported from a spreadsheet — enable Decode each line separately before decoding. Each line is then treated as its own URL instead of the whole block being processed as one string. The decoded lines appear in Decoded Result, where you can review them and copy or download the set.

This matters because a multi-line block pasted as a single string would otherwise be decoded as one continuous value, and line breaks or separators could be misread.

Re-encoding when you need to go back

The page includes an Encode action alongside the decoder. Use it when you have edited a decoded URL and need to turn it back into a percent-encoded form for use in a browser request, API call, redirect, or form submission. Encoding is what keeps characters like /, :, ?, and & from being misread as URL structure rather than data.

Common snags

• Result looks unchanged. The input may not actually contain percent-encoded sequences, or it may already be in readable form.
• Only part of a multi-line block converted. Check that Decode each line separately is enabled.
• A decoded URL still fails in the browser. Decoding makes a URL readable; it does not fix a malformed link. Compare the decoded output against the original to spot missing or doubled characters.
• Special characters reappear as %XX after encoding. That is expected — encoding deliberately converts those characters so the URL transmits correctly.

URL Decoder at url-decode.com is a free online tool that converts percent-encoded URLs back into readable links. You paste an encoded URL (or load one from a URL or text file), and the tool returns the decoded form so you can inspect, edit, share, or troubleshoot it. It runs in the browser with no account or installation described on the page.

What the tool does

The page presents a simple two-panel layout: an Input area for the encoded URL and a Decoded Result area for the readable output. The core function is translating percent-encoded sequences back to their standard characters:

For example, this encoded string:

http%3A%2F%2Furl-decode.com%2Ftool%2Furl-decode

becomes:

http://url-decode.com/tool/url-decode

The page also includes an Encode option that performs the reverse operation, converting a normal URL into its percent-encoded form.

Key features listed on the page

• Paste an encoded URL into the input box and decode it.
• Load from URL to pull in an encoded link directly.
• Upload text files containing encoded content.
• Decode each line separately, which the page describes as useful when you have multiple entries.
• Copy or download the decoded result.
• A character counter shows input and output length (e.g., "0 characters" before you type).

When you would use it

Encoded URLs show up in browsers, APIs, tracking links, redirects, and online forms. The page explains that special characters like !, #, $, &, /, :, ?, and @ play structural roles in a URL, so they must be percent-encoded to transmit correctly. That makes encoded links hard to read. Decoding helps when you need to:

• Check where a redirect or tracking link actually points.
• Debug an API request whose query string looks garbled.
• Read or edit a URL copied from a form submission.
• Verify that a link was encoded correctly before sharing it.

How to decode a URL

1. Copy the encoded URL (the version containing % sequences).
2. Paste it into the Input box, or use Load From URL / file upload if the content is stored elsewhere.
3. If you have multiple encoded entries, enable Decode each line separately.
4. Read the result in the Decoded Result panel.
5. Copy the output or download it.

Expected result: the %XX sequences are replaced with their original characters, and the link becomes human-readable.

Common snag: if the output still contains % sequences, the input may be double-encoded (encoded twice). Decode the result again to unwrap the second layer.

What it is not

Based on the page, this is a lightweight, immediate-use utility: no sign-up, no software install, and no pricing information is presented. It is a single-purpose converter for URL encoding and decoding rather than a full link-management or security-analysis platform.

URL decoding converts percent-encoded sequences back into the characters they stand for: %20 is a space, %2F is a forward slash /, and %3A is a colon :. You need it whenever a URL, API parameter, or tracking link arrives in encoded form and you want to read, edit, or troubleshoot it. A decoder such as url-decode.com takes the encoded string and returns the original readable URL.

What the three common codes mean

Each percent-encoded sequence is a % followed by two hexadecimal digits representing a character's byte value. The three you will meet most often:

The site's own example makes the transformation concrete. This encoded string:

http%3A%2F%2Furl-decode.com%2Ftool%2Furl-decode

decodes to:

http://url-decode.com/tool/url-decode

Reading it back: %3A restores the colon after http, each %2F restores a slash, and the result is a normal address you can inspect, edit, share, or paste into a browser.

Why these characters get encoded at all

Characters like /, :, ?, &, =, and # have structural jobs in a URL — they separate the scheme, host, path, query, and fragment. If one appears as literal data inside a component, a browser or server may misread the URL's structure. Encoding replaces the character with a percent sequence so it travels as data rather than as syntax.

The site lists the full set of characters that must be encoded before use in a URL, including:

• ! → %21, # → %23, $ → %24, & → %26
• ' → %27, ( → %28, ) → %29, * → %2A
• + → %2B, , → %2C, / → %2F, : → %3A
• ; → %3B, = → %3D, ? → %3F, @ → %40
• [ → %5B, ] → %5D

That is why encoded URLs are common in browsers, APIs, tracking links, redirects, and online forms: encoding keeps the data intact as it passes between systems. Decoding matters for the reverse direction — turning that data back into something a person can read and check.

How to decode a URL with url-decode.com

1. Paste the encoded URL into the Input box. The page shows a character count as you type.
2. Choose line handling if needed. Enable "Decode each line separately" when you have multiple encoded entries stacked on separate lines; otherwise the tool treats the input as one string.
3. Read the Decoded Result panel, which shows the readable format and its own character count.
4. Copy or download the result for use elsewhere.

The page also offers a sample input, a "Load From URL" option for pulling encoded text from a link, and an Encode direction if you need to go the other way. No pricing or login requirement is stated on the page, so treat access terms as unconfirmed rather than assuming the tool is free or open without sign-in.

Verify the result by checking that the decoded string starts with a recognizable scheme (http:// or https://), that slashes fall where path segments should break, and that no stray % sequences remain. If % characters survive decoding, the input may have been double-encoded — decode once more.

Common snags

• Double encoding. A string like %2520 decodes to %20, not to a space. Run it through the decoder twice.
• + versus %20. In form-encoded data, + often means a space, but in a strict URL path it is a literal plus. Check which context your string came from before trusting the output.
• Truncated input. A lone % or a % followed by fewer than two hex digits is malformed and will not decode cleanly; confirm you copied the whole string.
• Decoding changes meaning. If you decode a URL that is meant to stay encoded inside another parameter, re-encode it before sending it onward, or the receiving system may split it at the wrong character.