URL Encoder / Decoder

Input

Output

A Developer's Guide to URL Encoding (Percent-Encoding)

Ensure your URLs are safe and valid by correctly encoding special characters with our online URL Encoder & Decoder. This tool is essential for web developers who need to pass data in query strings or handle filenames with special characters. Convert any string into a universally accepted URL-safe format, or decode a percent-encoded string back to its original human-readable form.

About the URL Encoder & Decoder

URL encoding, officially known as Percent-Encoding, is a critical mechanism for ensuring that URLs are transmitted and interpreted correctly across the internet. URLs are restricted to a limited subset of the ASCII character set. This tool translates any "unsafe," "reserved," or non-ASCII characters into a safe format, which consists of a percent sign (%) followed by the two-digit hexadecimal representation of the character's byte value. Our converter provides a simple, client-side interface for performing both encoding and decoding operations instantly.

How the Converter Works

This tool simplifies the two main operations of URL data formatting.

Using the Converter

Enter Your Text: Type or paste the string you wish to convert into the "Input" text area.
Choose an Action:
- Click Encode to convert your text into the URL-safe, percent-encoded format.
- Click Decode to convert a percent-encoded string back to its original, human-readable form.
Get the Result: The converted text will appear in the "Output" box, ready to copy.

The Technical Principles of URL Encoding

Understanding why and how URL encoding works is fundamental for web development and creating robust web applications.

Why Encoding is Necessary

The syntax of a URL is highly structured. Certain characters are reserved because they have a special meaning for interpreting the URL's structure.

Structural Characters: Characters like the colon (:), slash (/), question mark (?), and ampersand (&) are used to separate the scheme, host, path, query string, and parameters.
Unsafe Characters: Characters like the space, double quotes ("), and angle brackets (< >) are not permitted in URLs because they can be misinterpreted by browsers, servers, or other network equipment.
Non-ASCII Characters: The original URL specification was limited to the ASCII character set. To include international characters (like é, ü, or 日本語), they must be encoded.

The Encoding Process

URL encoding works by replacing a special character with a three-character sequence: a percent sign (%) followed by the two hexadecimal digits that represent the character's value in the ASCII (or UTF-8) table.

Character	Reason for Encoding	Encoded Value
(space)	Unsafe Character	`%20` (or `+` in query strings)
`/`	Reserved Character (path separator)	`%2F`
`?`	Reserved Character (query separator)	`%3F`
`&`	Reserved Character (parameter separator)	`%26`
`=`	Reserved Character (key-value separator)	`%3D`
`é`	Non-ASCII Character	`%C3%A9` (UTF-8 representation)

When to Encode (and When Not To)

Only Encode the Right Parts

You should never encode an entire URL. This would corrupt the structural components like `https://`. URL encoding should only be applied to the individual values within a URL's path or query string.

Correct Usage Example (Query String):

Imagine you have a search URL: https://example.com/search?q= and the user searches for "C++ & Java".

Value to Encode: C++ & Java
Encoded Value: C%2B%2B%20%26%20Java
Final URL: https://example.com/search?q=C%2B%2B%20%26%20Java

In this example, the `+` and `&` symbols are correctly encoded so they are treated as part of the search term, not as special URL characters.

Professional Recommendation

For developers, every major programming language provides built-in functions to handle URL encoding (e.g., encodeURIComponent() in JavaScript, urllib.parse.quote_plus() in Python, UrlEncode() in C#). It is best practice to always use these standardized library functions to encode any user-generated content before inserting it into a URL to prevent errors and security vulnerabilities.

Frequently Asked Questions about URL Encoding

What is URL encoding?

URL encoding, also known as percent-encoding, is a mechanism for translating special characters in a Uniform Resource Identifier (URI) into a format that is universally understood and safely transmitted over the internet. It replaces unsafe or reserved characters with a '%' symbol followed by two hexadecimal digits that represent the character's ASCII value.

Why is URL encoding necessary?

URLs can only be transmitted over the internet using the ASCII character set. Certain characters have special meanings in a URL (e.g., '/', '?', '#', '&') and cannot be used directly as data. URL encoding ensures these characters are correctly interpreted as data, not as part of the URL's structure.

How do I use this URL Encoder/Decoder?

Paste the text or URL you want to convert into the top input box. Click 'Encode' to turn it into a URL-safe string. If you have an encoded string, paste it in and click 'Decode' to revert it to its original form.

What is an example of URL encoding?

A space character is not allowed in a URL. If you encode the string 'hello world', it becomes 'hello%20world', where '%20' is the percent-encoded representation of a space.

What are reserved characters in a URL?

Reserved characters are characters that have a special function within the URL syntax. These include `!`, `#`, `$`, `&`, `'`, `(`, `)`, `*`, `+`, `,`, `/`, `:`, `;`, `=`, `?`, `@`, `[`, and `]`.

What happens if I don't encode a URL correctly?

If you don't encode special characters, a web server or browser may misinterpret the URL. This can lead to broken links (404 errors), incorrect data being passed in a query string, or even security vulnerabilities like Cross-Site Scripting (XSS).

Should I encode the entire URL?

No, you should never encode an entire URL. Encoding characters like ':' and '/' would break the URL's structure (e.g., `https://` would become `https%3A%2F%2F`). You should only encode the specific components of a URL, such as individual query string parameter values.

What is a query string?

A query string is the part of a URL that comes after a question mark (`?`). It is used to pass key-value pairs of data to a web application (e.g., `?search=blue+widgets`). The values in these pairs must be URL-encoded.

Is a plus sign `+` the same as `%20` for a space?

In the query string part of a URL, a plus sign `+` is often interpreted as a space by web servers. `%20` is the official percent-encoding for a space. While both may work in query strings, for other parts of a URL, only `%20` should be used to represent a space.

What are unreserved characters?

Unreserved characters are characters that do not have a special meaning and do not need to be encoded. These include uppercase and lowercase letters (A-Z, a-z), numbers (0-9), and the symbols `-`, `_`, `.`, and `~`.

Does this tool encode Unicode characters?

Yes. When you enter a Unicode character (like 'é' or '😊'), the tool first represents it in its UTF-8 byte sequence and then percent-encodes each of those bytes. For example, 'é' becomes '%C3%A9'.

Is the encoding performed in my browser?

Yes, all encoding and decoding operations are performed securely on the client-side within your browser using JavaScript. Your data is never sent to our servers.

What is Base64 encoding and is it the same as URL encoding?

Base64 is a different binary-to-text encoding scheme. It is not the same as URL encoding. Base64 is used to embed binary data like images into text, while URL encoding is specifically for making characters safe within the URL syntax. You can use our Base64 Converter for that purpose.

Can I decode a string that wasn't encoded?

If you try to decode a plain text string that does not contain any percent-encoded sequences (like '%20'), the decoder will simply return the original string unchanged.

Do modern browsers automatically handle URL encoding?

Yes, when you type a space in your browser's address bar, it will automatically convert it to `%20` before sending the request. However, when you are a developer constructing a URL in your code (e.g., for an API call), you are responsible for correctly encoding the components yourself.

Why does my decoded URL look different from what I see in the browser bar?

Modern browsers often display a decoded, human-readable version of the URL in the address bar for clarity, even though they are sending the fully encoded version to the server in the background.

What is an IRI?

IRI stands for Internationalized Resource Identifier. It is a newer standard that extends the URI scheme to allow for a much wider range of Unicode characters, making web addresses more accessible for non-Latin scripts. IRIs are mapped to URIs (URLs) through encoding for actual use.

What is the ASCII character set?

ASCII (American Standard Code for Information Interchange) is a character set that includes 128 characters, including English letters, numbers, and common symbols. The original URL specification was based on this limited character set.

Should I encode the ampersand `&` character?

Yes, if the ampersand `&` is part of a value in a query string, it must be encoded to `%26`. Otherwise, it will be misinterpreted as a separator between two different key-value pairs.

What about the question mark `?` character?

The first question mark `?` in a URL separates the path from the query string and should not be encoded. Any subsequent question marks that are part of the data in the query string must be encoded to `%3F`.

What is UTF-8?

UTF-8 is a variable-width character encoding that can represent every character in the Unicode standard. It is the dominant character encoding for the World Wide Web. URL encoding handles UTF-8 characters by encoding each byte of their representation.

Do I need to encode `http://`?

No, the `http://` or `https://` part is the URL scheme and should never be encoded. Doing so would make the URL completely invalid.

What is double encoding?

Double encoding is when you URL-encode a string that has already been encoded. For example, encoding `%20` would result in `%2520` (since `%` is encoded as `%25`). This can cause issues and should generally be avoided unless specifically required by a system.

How do I handle file paths in a URL?

Each segment of a file path is separated by a `/`. The slashes should not be encoded. However, if a filename itself contains a special character (like a space or a `#`), that character within the filename must be encoded.

Is a developer needed to handle URL encoding?

While anyone can use this tool to encode or decode a string, properly implementing URL encoding in a web application requires a developer. Programming languages provide built-in functions (like `encodeURIComponent()` in JavaScript) to handle this correctly, and a developer is needed to know when and on which parts of a URL to use them.

link URL Encoder / Decoder