URL encoder and decoder

URL encoding replaces characters that are not allowed in a URL with a percent sign followed by two hex digits. For example, a space becomes %20 and an ampersand becomes %26. This is required when passing special characters in query parameters or form data so browsers and servers interpret the URL correctly.

encodeURI encodes a full URL and leaves characters like /, ? and & intact because they have meaning in URL structure. encodeURIComponent encodes a single value within a URL and also escapes those structural characters. Use encodeURIComponent (the Component method) when encoding query parameter values.

Paste the percent-encoded text into the encoded text box and click Decode back to plain text. The tool converts %20 back to spaces, %26 back to &, and all other percent sequences back to their original characters. This is useful for reading tracking URLs, debugging API responses, or decoding shared links.

%20 is the percent-encoded representation of a space character. When a URL contains a space, browsers convert it to %20 or sometimes a plus sign in query strings. Both encoding methods here handle plain spaces the same way.

Yes. Choose the Base64 method to encode text into Base64, or paste Base64 text and click Decode back to plain text to reverse it. Base64 is a different encoding from URL percent-encoding, commonly used for embedding binary-like data in text such as email attachments or data URLs.

The tool runs entirely in your browser and does not transmit your input to any server. However, URL encoding and Base64 are not encryption or hashing; they are text transformations that anyone can reverse. Never put passwords or secret tokens in a URL, encoded or not, as URLs are stored in browser history and server logs.