URL & Link Tools
100% Client-Side 100% Client-Side. URLs are encoded in browser memory with zero server transmission.

URL Encoder (Percent-Encoding)

Encode text and URLs into RFC 3986 percent-encoded strings with multiple standard modes

RFC 3986 URL Percent-Encoding & Decoding Studio

100% Client-side. Safe encoding of reserved delimiters, UTF-8 unicode octets, and query parameters.

Client-Side RAMRFC 3986 / WHATWG

Choose which characters should be percent-escaped

Presets:
91 charactersUTF-8 encoding
119 total charactersReady for HTTP requests
Total Output Length
119
Bytes in UTF-8
Percent Escapes (%XX)
14
Escaped octets
Unreserved Chars
105
A-Z, a-z, 0-9, -_.~
Reserved Chars Preserved
0
Delimiters intact

Standard RFC 3986 Percent-Encoding Quick Reference

Space ( )
%20 or +
Standard space encoding
Slash (/)
%2F
Path segment separator
Question Mark (?)
%3F
Query string start
Ampersand (&)
%26
Query parameter separator
Equals (=)
%3D
Key-value separator
Hash (#)
%23
Anchor / Fragment delimiter
Percent (%)
%25
Percent-encoding escape token
Colon (:)
%3A
Protocol / Port delimiter
At (@)
%40
Userinfo authority delimiter
Plus (+)
%2B
Mathematical plus symbol

About URL Encoder (Percent-Encoding)

Online RFC 3986 URL encoder and percent-escape converter. Safely encode URL query parameters, paths, and international UTF-8 characters into percent-encoding (e.g. %20, %2F, %3F, %26). Features component mode, full URI mode, strict octet mode, and form-urlencoded + mode.

Key Capabilities & Features

  • 4 encoding modes: Component, Full URI, Strict RFC Octets, and Form-Urlencoded
  • Detailed character distribution analysis (unreserved, reserved, percent-escaped)
  • Multi-line batch encoding support
  • One-click copy and .txt download

How to Use URL Encoder (Percent-Encoding)

1

Enter Text or URL

Paste raw strings, query parameters, or entire web addresses.

2

Select Encoding Standard

Choose Component, Full URI, Strict Octets, or Form-encoded mode.

3

Copy Escaped Output

Copy the percent-encoded string for safe use in HTTP headers or URLs.

Privacy & In-Browser Execution Guarantee

100% Client-Side. URLs are encoded in browser memory with zero server transmission.

Frequently Asked Questions

What is the difference between encodeURI and encodeURIComponent?

encodeURI is designed for entire URLs and leaves protocol, host, and path delimiters intact (: / ? # & =). encodeURIComponent encodes every reserved character and is meant for query parameter values.

Why does URL encoding use percent signs?

Per RFC 3986, characters outside the unreserved ASCII set (A-Z, a-z, 0-9, -, _, ., ~) must be represented as a percent sign (%) followed by two hexadecimal digits representing the UTF-8 byte.