What is urlencode and why is percent-encoding necessary?

What is urlencode? URL encoding (or percent-encoding) is an RFC 3986 mechanism for encoding characters in Uniform Resource Identifiers. Certain characters (such as spaces, slashes, ampersands, or question marks) have reserved semantic meanings in URLs; percent-encoding maps them to % followed by their two-digit hexadecimal byte value.

How to url encode js strings in modern JavaScript?

In JavaScript, use encodeURIComponent(str) to encode query parameter values. For whole URLs where structural delimiters should be preserved, use encodeURI(str). For application/x-www-form-urlencoded query strings, use new URLSearchParams().

What is the difference between %20 and + for space encoding?

Standard RFC 3986 percent-encoding requires %20 for spaces anywhere in a URL. The plus symbol '+' is only valid for spaces inside query strings formatted as application/x-www-form-urlencoded (HTML form submission standard).

Advanced URL Encoder & Decoder - Character Selection & Percent Encoding | NR Tech Studio

RFC 3986 Standard • Multi-Byte UTF-8 • Custom Character Masking

Advanced URL Encoder & Decoder - Character Selection & Percent Encoding

A professional custom url encode decode tool and online url percent encoding tool. Easily url encode string data or decode url string payloads, master url encode js functions, inspect url encoding characters, understand what is urlencode, and use this encode url characters tool and advanced url encoder with character selection to url encode and decode and format urlencode text.

Raw Plain Text / Decoded String

Percent-Encoded Output

0 input chars • 0 output chars • 0 bytes

Presets:

RFC 3986 URL Percent Encoding Codes Reference Table

In web protocols, url percent encoding replaces non-ASCII and reserved ASCII characters with a % followed by their two hexadecimal digits. Here are the most critical url encoding codes for standard web communication:

Character	ASCII Code	Percent Code	URI Semantic Meaning
Space ( )	32 (0x20)	`%20` or `+`	Space separation in query or path
Forward Slash (`/`)	47 (0x2F)	`%2F`	Path segment separator
Question Mark (`?`)	63 (0x3F)	`%3F`	Start of query string parameter list
Ampersand (`&`)	38 (0x26)	`%26`	Query string parameter delimiter
Equals Sign (`=`)	61 (0x3D)	`%3D`	Key-value query parameter assignment
Hash Sign (`#`)	35 (0x23)	`%23`	Fragment identifier / document anchor
Colon (`:`)	58 (0x3A)	`%3A`	Protocol/Scheme separator & Port delimiter
At Symbol (`@`)	64 (0x40)	`%40`	User info / HTTP Basic authentication boundary

URL Encode in JavaScript: Functions & Implementation Details

Modern developers frequently need to url encode js strings. JavaScript provides two native global functions, each serving distinct use cases:

encodeURIComponent(str): Encodes all characters except A-Z a-z 0-9 - _ . ! ~ * ' ( ). Use this whenever encoding individual query parameter values (e.g. search queries, redirect URLs).
encodeURI(str): Designed for complete URLs. Preserves URI protocol delimiters (: / ? # & =) while encoding illegal characters like spaces and Unicode characters.
decodeURIComponent(str): Decodes percent-encoded components back to raw UTF-8 string representations.

Frequently Asked Questions: Online URL Percent Encoding Tool

What happens to UTF-8 multi-byte characters like emojis during percent encoding?

UTF-8 characters with code points above 127 are split into multiple bytes (2 to 4 bytes). Each individual byte is prefixed with a percent sign. For example, the rocket emoji 🚀 (code point U+1F680, 4 bytes: 0xF0 0x9F 0x9A 0x80) encodes as %F0%9F%9A%80.

Why do some systems encode space as + while others use %20?

%20 is defined in RFC 3986 as the official percent-encoding for spaces across all URI parts. In contrast, + is specified in HTML forms (MIME type application/x-www-form-urlencoded) specifically for query parameters.

Is percent encoding case-sensitive?

RFC 3986 specifies that hexadecimal digits in percent-encoding should be uppercase (e.g. %2F rather than %2f) to normalize comparison, though decoders must accept both cases interchangeably.