RFC 3986 Percent-Encoder

Percent-encode or decode text strictly per RFC 3986 online for free.

No uploadsNo sign-upInstant results
Strict RFC 3986Every byte as %XX100% Local • Zero Uploads
Percent-encode / decode
Offline engine ready100% private in-browser workspace • Zero cloud uploads
100% Private • Zero Server File Uploads

Why Use Utiliome's Free RFC 3986 Percent-Encoder?

Built from the ground up for strict privacy, instant execution, and zero friction. No subscriptions, paywalls, or account registrations required.

Strict RFC 3986 Percent-Encoding

Encodes sub-delimiters (!, ', (, ), *) in addition to standard JavaScript encodeURIComponent characters.

Encode Every Byte, Upper or Lowercase Hex

Optionally encode every UTF-8 byte into %XX hex triplets with uppercase or lowercase formatting.

Strict RFC 3986 Unreserved Set Enforcement

Escapes !, ', (, ), and *—the five sub-delimiters that standard JavaScript encodeURIComponent leaves unencoded—ensuring 100% RFC 3986 compliance.

Encode-Every-Byte & Hex Case Toggles

Optionally percent-encode every single UTF-8 byte (including alphanumeric ASCII) and switch between uppercase (%2F) and lowercase (%2f) hexadecimal nibbles.

Utiliome vs Traditional Cloud Alternatives

Compare our local-first WebAssembly engine against legacy cloud tools.

Feature Utiliome (Local Browser) Legacy Cloud Converters
RFC 3986 Strictness (! ' ( ) *) Strictly escapes all characters outside ALPHA / DIGIT / "-" / "." / "_" / "~" Wraps encodeURIComponent() directly, leaving ! ' ( ) * unescaped and breaking AWS SigV4
All-Byte %XX Hex Escaping Mode One-click mode to convert every ASCII and UTF-8 byte into %XX triplets Cannot percent-encode unreserved alphanumeric characters when testing parsers
Hexadecimal Case Normalization Toggle canonical uppercase (%3A%2F%2F) per RFC 3986 §2.1 or lowercase (%3a%2f%2f) Hardcoded uppercase only with no normalization control
100% Local Zero-Upload Execution Runs entirely in browser memory via TextEncoder and Uint8Array Sends sensitive OAuth signature base strings to remote servers
How it works

How to Use RFC 3986 Percent-Encoder in 3 Easy Steps

No software installation required. Everything runs directly inside your web browser.

1

Enter Text or URI Payload

Paste text, query fragments, or header strings into the input textarea.

2

Configure Encoding Preferences

Select Strict RFC 3986 or Encode All Bytes, and toggle uppercase vs. lowercase hex digits.

3

Copy Percent-Encoded Output

Copy the encoded string or decoded UTF-8 text directly to your clipboard.

How Percent-Encoding Works (RFC 3986)

Quick Answer: Utiliome converts strings into UTF-8 byte arrays via TextEncoder and percent-encodes octets strictly per RFC 3986 Section 2.1, leaving only the 66 unreserved characters (A–Z, a–z, 0–9, "-", ".", "_", "~") literal—or optionally escaping every single byte into %XX hexadecimal triplets.

Standard JavaScript encodeURIComponent does not encode !, ', (, ), or *. Strict RFC 3986 systems (such as OAuth signature generators and AWS S3 authorization headers) require these characters to be escaped. This tool provides strict RFC 3986 compliance:

Given this input text:

Hello World! (2026) Café

Strict RFC 3986 encoding produces:

Hello%20World%21%20%282026%29%20Caf%C3%A9

Notice that ! becomes %21 and parentheses become %28 and %29. In Encode All Bytes mode, even standard ASCII alphanumeric letters are converted to their %XX byte representations.

For everyday query-string encoding with encodeURIComponent (which leaves !'()* alone and can write spaces as +), use URL Encoder & Decoder.

Which Characters Get Encoded, Hex Case and Decoding

Quick Answer: Unlike standard JavaScript encodeURIComponent(), which follows an older RFC 2396 grammar and leaves "!", "'", "(", ")", and "*" unescaped, our strict RFC 3986 encoder escapes all 18 gen-delims and sub-delims required by OAuth 1.0a (RFC 5849) and AWS Signature Version 4.

Observe these protocol standards when percent-encoding:

  • Uppercase hex recommendation: RFC 3986 Section 2.1 recommends uppercase hexadecimal digits (%2F rather than %2f) for consistency across HTTP servers and CDNs.
  • Decoding checks: A % that is not followed by two hex digits (such as 100% or %ZZ) is reported together with the offending sequence, and bytes that do not form valid UTF-8 (for example a cut-off %E2%82) are reported instead of being turned into replacement characters.
  • Encode All Bytes utility: Converting every byte into percent notation is useful for debugging network proxies and testing URL parser vulnerabilities against over-encoded payloads.

Percent Encoder vs URL Encoder: Which One Do You Need?

Quick Answer: Use this RFC 3986 Percent-Encoder when building canonical cryptographic signature strings, escaping every byte into %XX hex, or enforcing strict uppercase %20 encoding; use URL Encoder & Decoder for everyday web links and form query strings where spaces may map to +.

Both tools produce percent-encoded text, but they follow different rule sets:

Percent Encoder (this page) URL Encoder & Decoder
Character set left unescaped Only the RFC 3986 unreserved set: letters, digits, - . _ ~ JavaScript's encodeURIComponent set, including ! ' ( ) *
Escape every byte, including letters Yes, optional No
Whole-URL mode that keeps / ? & = No Yes (encodeURI)
Space as + for HTML forms No, always %20 Yes, optional
Hex case Uppercase or lowercase Uppercase

OAuth 1.0a signature base strings, AWS Signature V4 canonical requests and many binary-over-URL schemes are defined in terms of RFC 3986, which is where the strict set matters. For ordinary links and form data the URL Encoder is simpler.

Why AWS Signature v4 and OAuth 1.0a Require Strict RFC 3986 Encoding

Quick Answer: Cryptographic HTTP request signing protocols such as AWS Signature Version 4 and OAuth 1.0a (RFC 5849 Section 3.6) mandate deterministic RFC 3986 canonicalization where spaces must be %20 (never +), hex digits must be uppercase (%2A, never %2a), and !'()* must be escaped.

When computing an HMAC-SHA256 canonical request signature for AWS S3, CloudFront, or OAuth APIs, a single character encoding mismatch between your client and the server causes a 403 SignatureDoesNotMatch error:

  1. The 5 Sub-Delimiter Trap (! ' ( ) *): JavaScript's built-in encodeURIComponent("file(1).txt") returns "file(1).txt" unescaped. AWS SigV4 expects "file%281%29.txt".
  2. Uppercase Hex Canonicalization (RFC 3986 §6.2.2.1): While URI parsers treat %2f and %2F as equivalent, cryptographic hash functions hash the raw ASCII bytes of the canonical request, requiring uppercase hex nibbles.
  3. Space Encoding (%20 vs +): application/x-www-form-urlencoded encodes spaces as + (0x2B), whereas RFC 3986 encodes spaces strictly as %20.

For related URI and cryptographic tools, explore URL Encoder & Decoder, Query String Parser, URL Parser, and HMAC Generator & Verifier.

FAQ

RFC 3986 Percent-Encoder FAQ and Technical Guide

Everything you need to know about using Utiliome's free online percent encode.

Why does Strict RFC 3986 mode encode exclamation marks and parentheses?

Standard JavaScript encodeURIComponent leaves "!", "'", "(", ")", and "*" unencoded. Protocols like OAuth 1.0a and AWS SigV4 strictly require every character outside the unreserved set to be percent-encoded.

What is the Encode All Bytes mode used for?

Encode All Bytes converts every single character—including standard letters and numbers—into its percent-encoded UTF-8 byte value for protocol testing and security research.

Which characters never need percent-encoding?

RFC 3986 defines the unreserved set: uppercase and lowercase letters, digits, hyphen, period, underscore and tilde. Everything else, including the space, may need to be encoded as a % followed by two hexadecimal digits, depending on where in the URL it appears.

Is percent-encoding the same as URL encoding?

Yes, the terms describe the same mechanism. Percent-encoding is the formal name used in RFC 3986; URL encoding is the everyday name. Tools differ only in which characters they leave unescaped: this page follows the strict RFC set, while the URL Encoder & Decoder follows the more permissive JavaScript rules used by browsers.

Why does JavaScript encodeURIComponent() not escape parentheses or exclamation marks?

ECMAScript standardized encodeURIComponent() based on RFC 2396 (1998), which classified !, ', (, ), and * as "unreserved" mark characters. RFC 3986 (2005) reclassified those 5 characters as reserved sub-delimiters, which Utiliome escapes automatically in strict RFC 3986 mode.

When should I enable "Encode Every Byte (All Characters)"?

Enable all-byte percent-encoding when testing WAF/IDS normalization filters, debugging URI router decoding behavior, or inspecting the exact UTF-8 %XX byte sequence of an entire string.