Question 1

What is percent-encoding (URL encoding)?

Accepted Answer

Percent-encoding, defined in RFC 3986, is a mechanism for encoding arbitrary data in a Uniform Resource Identifier (URI) using only a limited subset of US-ASCII characters. Unsafe characters are replaced with a "%" followed by two hexadecimal digits representing the character's ASCII value. For example, a space becomes "%20" and an ampersand becomes "%26". This ensures data can be safely transmitted in URLs without being misinterpreted by servers, proxies, or browsers.

Question 2

What is the difference between a URI, URL, and URN?

Accepted Answer

A URI (Uniform Resource Identifier) is the broadest term, encompassing both URLs and URNs. A URL (Uniform Resource Locator) specifies both the identity and the location of a resource on the internet (e.g., https://www.example.com). A URN (Uniform Resource Name) identifies a resource by name within a specific namespace but does not specify its location (e.g., urn:isbn:0451450523). All URLs are URIs, but not all URIs are URLs.

Question 3

What characters must be percent-encoded in a URL?

Accepted Answer

RFC 3986 defines two categories of characters. Unreserved characters (A-Z, a-z, 0-9, hyphen, period, underscore, tilde) never need encoding. Reserved characters (: / ? # [ ] @ ! $ & ' ( ) * + , ; =) have special meanings in URI syntax and must be encoded when used as data rather than as delimiters. All other characters, including spaces and non-ASCII characters, must always be percent-encoded.

Question 4

Why are spaces encoded as %20 instead of +?

Accepted Answer

In RFC 3986 percent-encoding, spaces are encoded as %20. The plus sign (+) is a legacy encoding used specifically in application/x-www-form-urlencoded data (HTML form submissions), not in generic URLs. When encoding a full URL path, %20 is the correct representation. However, when encoding form data sent via HTTP POST or GET query strings, + is commonly accepted as an alternative to %20 for spaces. This tool uses encodeURIComponent, which encodes spaces as %20.

Question 5

What is the difference between encodeURI and encodeURIComponent?

Accepted Answer

encodeURI is designed to encode an entire URI. It preserves characters that are part of URI syntax, such as :, /, ?, #, and &. encodeURIComponent is designed to encode individual URI components, such as query parameter values, where even syntactic characters must be encoded to prevent them from being interpreted as delimiters. For example, encodeURI("https://a.b/c?d=e") works correctly, while encodeURIComponent would encode the slashes and colon. This tool uses encodeURIComponent for maximum safety.

Question 6

How are non-ASCII characters handled in URLs?

Accepted Answer

Non-ASCII characters (such as accented letters, Chinese characters, or emojis) must be encoded before inclusion in a URL. encodeURIComponent first converts the character to UTF-8 bytes, then percent-encodes each byte. For example, the euro sign (€) becomes "%E2%82%AC". For internationalized domain names (IDNs), Punycode is used to represent Unicode domain names using ASCII-compatible encoding (e.g., "münchen.de" becomes "xn--mnchen-3ya.de").

Question 7

What is Punycode and how does it relate to IDNs?

Accepted Answer

Punycode is a special encoding used to represent Unicode characters in ASCII-compatible format for Internationalized Domain Names (IDNs). Because the Domain Name System (DNS) historically supports only ASCII, Punycode converts Unicode domain labels into strings beginning with "xn--". For example, the domain "münchen.de" is represented in DNS as "xn--mnchen-3ya.de". Browsers automatically convert between the Unicode display form and the Punycode DNS form.

Question 8

When should I use a URL encoder?

Accepted Answer

You should use a URL encoder whenever you need to include arbitrary text as part of a URL, especially in query parameters, path segments, or fragment identifiers. Any text containing spaces, ampersands, equals signs, question marks, hash symbols, non-ASCII characters, or control characters must be encoded. URL encoding is essential for web development, API integration, SEO-friendly URLs, and email link generation.

Question 9

What does RFC 3986 specify?

Accepted Answer

RFC 3986 is the Internet standard that defines the generic syntax of Uniform Resource Identifiers (URIs). It specifies the allowed character set, the structure of schemes, authorities, paths, queries, and fragments, and the rules for percent-encoding. Published in 2005, it obsoleted the earlier RFC 2396 and remains the authoritative reference for URL construction and parsing in modern web standards.

Question 10

Can URL encoding be used for security?

Accepted Answer

URL encoding is not a security mechanism—it is a data transport mechanism. While encoding can prevent some simple parsing errors, it does not protect against attacks such as SQL injection, cross-site scripting (XSS), or command injection. Always validate and sanitize user input on the server side, use parameterized queries, and apply proper output encoding appropriate to the context (HTML, JavaScript, CSS, etc.) in addition to URL encoding.

Character	Encoded	Character	Encoded
Space	%20	&	%26
!	%21	=	%3D
#	%23	?	%3F
$	%24	@	%40
+	%2B	/	%2F

URL Encoder / Decoder

Percent-Encoding and URI Standards

Common URL-Encoded Characters

References

Related Tools

Frequently Asked Questions

Related Tools

JSON Formatter

Base64 Encoder / Decoder

CSS Minifier

JavaScript Minifier