URL Encoder/Decoder

Percent-encoding writes characters that are not safe in a URL as a percent sign plus two hex digits. Spaces often become %20. Decoding reverses that so you can read the original text.

What you get from URL Encoder/Decoder is concrete. Encode replaces unsafe characters with percent sequences. Decode turns those sequences back into characters. The string stays in the browser. Read those results before you paste them into a template, a file, or a ticket. A copied mistake is harder to see later than a mistake still on this page.

A careful pass on URL Encoder/Decoder looks like this. Start with real input, not a placeholder you do not understand. Paste the URL or text. Then check the middle of the form, because that is where optional fields change the output. Choose encode or decode. Finish by reading the whole result, not only the first line. Copy the result.

The limit is the part people skip on URL Encoder/Decoder. Match the output to the input you actually typed, then decide whether it belongs on the live site. When you already have a percent-encoded string and need the readable text. Decode turns those sequences back into characters.

A second reading of URL Encoder/Decoder is worth it because the first pass is easy to rush. Say out loud what the output is claiming. Encode replaces unsafe characters with percent sequences. Decode turns those sequences back into characters. The string stays in the browser. Then say what it is not claiming. When the text will be placed in a URL and it contains spaces or reserved characters. When you already have a percent-encoded string and need the readable text. No. Encode and decode run in the browser. If those two speeches disagree, change the input or pick a different tool. URL Encoder/Decoder will not resolve the disagreement for you.

Read URL Encoder/Decoder once more as a single job. Part 1: Paste the URL or text. Part 2: Choose encode or decode. Part 3: Copy the result. You should be able to point at this in the result: Encode replaces unsafe characters with percent sequences. You should be able to point at this in the result: Decode turns those sequences back into characters. You should be able to point at this in the result: The string stays in the browser. When should I percent-encode a URL? When the text will be placed in a URL and it contains spaces or reserved characters. When should I decode a percent-encoded URL? When you already have a percent-encoded string and need the readable text. Is the string uploaded? No. Encode and decode run in the browser. Who is URL Encoder/Decoder for? URL Encoder/Decoder is for someone already doing link tools work who needs safely encode and decode URLs to handle special characters. Percent-encoding writes characters that are not safe in a URL as a percent sign plus two hex digits. Spaces often become %20. Decoding reverses that so you can read the original text. The first field was filled with a real value: Paste the URL or text. The result was read: Encode replaces unsafe characters with percent sequences. Optional fields were either filled or left empty on purpose. The copy went into the place the last step names. The boundary in the guide was respected before anything was published.

Keep URL Encoder/Decoder as this step only. When the job moves on, the URL Parser is the next page: URL Parser splits one address into protocol, host, port, path, query parameters, and hash. The Ahrefs DR Checker covers a different piece of the same work: Ahrefs DR Checker sends a domain to the iSkills server, which asks Ahrefs for a Domain Rating when an API key is configured.