URL Encode / Decode converts special characters into percent-encoded form and back. Spaces, ampersands, question marks and non-English letters have special meaning or are not allowed in URLs, so they are written as codes like %20 for a space or %26 for &. Decoding turns an unreadable link back into plain text.
Marketers decode tracking links to check UTM parameters, developers encode values before adding them to a query string, and support staff read redirect URLs pasted by users. Encoding a search term like "shoes & bags" before putting it in a link prevents the & from being misread as the start of a new parameter.
How to use URL Encode / Decode
- Paste the URL or text into the main text area.
- Choose Encode or Decode in the settings panel on the right, and whether to encode a full URL or just a component.
- Press the action button to convert.
- Copy the encoded or decoded result.
Features
- Runs in your browser; links containing tokens or emails are not uploaded.
- Handles UTF-8, so accented and non-Latin characters encode correctly.
- Decodes %XX sequences back into readable text.
- Full-URL mode keeps characters like : / ? & intact; component mode encodes them too.
- Shows an error for malformed sequences such as a stray % sign.
When to use it
- Reading the destination hidden inside a long redirect or tracking link.
- Encoding a customer's search phrase before adding it to an API query string.
- Checking campaign parameters in an encoded link copied from an ad dashboard.
Frequently asked questions
Why is a space sometimes + and sometimes %20?
%20 is standard URL encoding. The + sign is used for spaces in HTML form submissions. Both are common; check what your system expects.
When should I encode a full URL vs. a component?
Encode a component, such as a single query value, when inserting it into a URL. Encode a full URL only when the whole link must be passed as a value inside another URL.
Why does decoding fail?
A % sign must be followed by two hex digits. A lone % or invalid sequence cannot be decoded.
Is URL encoding the same as Base64?
No. URL encoding only escapes unsafe characters, leaving normal letters readable. Base64 transforms all of the text.