// UTILITY / 004 • URI_ENCODING

URL Component Encoder & Decoder

Percent-encode and decode URL components, full URIs, and form query values with full RFC 3986 conformity and multi-byte Unicode support. Runs 100% inside your local browser memory.

// PRIVACY_NOTE: Local browser execution. Tool input is strictly processed in-memory and never transmitted to a conversion API or database.
⌘ input.urlUTF-8 / TEXT

URL Input Area

⌘ output.converted

Converted Result

0 characters

// WORKFLOW / STEP_BY_STEP

How to Encode & Decode URLs

Follow these steps to safely escape query parameters, prevent delimiter collisions, and decode percent-encoded strings:

01PHASE_01

Enter or Paste Text / URL

Type or paste your query parameter, path segment, or complete URI into the input editor.

02PHASE_02

Select Specific Encoding Mode

Choose "Component mode" for query values, "Full URL mode" for complete addresses, or "Form value mode" for application/x-www-form-urlencoded syntax.

03PHASE_03

Click Encode or Decode

Run the conversion to generate RFC-compliant percent-encoded output or restore raw UTF-8 text.

04PHASE_04

Inspect Character Count & Metrics

Review the output length and verified encoding mode directly in the editor status bar.

05PHASE_05

1-Click Clipboard Copy

Copy the output directly to your clipboard or clear both editors to begin your next task.

// SPECIFICATION / RFC_3986

URI Encoding Specifications & Standards

Formal specification rules governing reserved characters, percent-encoding, and form value serialization:

[SPEC_01]RFC 3986

Component Mode (encodeURIComponent)

Escapes all reserved punctuation characters (; , / ? : @ & = + $ #). This mode is mandatory for individual query string parameter values to prevent delimiter injection.

encodeURIComponent("a&b=c") -> "a%26b%3Dc"
[SPEC_02]RFC 3986

Full URI Mode (encodeURI)

Preserves structural protocol and path delimiters (http://, /, ?, #, &) while encoding unsafe characters like spaces and Unicode glyphs. Use when encoding full destination links.

encodeURI("https://site.com/search?q=tea & biscuits") -> ".../search?q=tea%20&%20biscuits"
[SPEC_03]W3C FORM

Form Mode (application/x-www-form-urlencoded)

Standardized form value encoding used by HTML forms and URLSearchParams. Spaces are encoded as "+" instead of "%20".

URLSearchParams -> "name=Alex+Smith"
// SPECIFICATION / TECHNICAL_DEEP_DIVE

RFC 3986 Mechanics & Character Sets

Detailed technical analysis of URI reserved character sets, form serialization, and UTF-8 multi-byte octets:

01SPEC_MODE

RFC 3986 Reserved vs Unreserved Sets

RFC 3986 divides the ASCII character space into unreserved characters (A-Z, a-z, 0-9, "-", "_", ".", "~"), which should never be encoded, and reserved characters (; , / ? : @ & = + $ #), which carry structural delimiter meaning.

Unreserved: [A-Za-z0-9-_.~] /* NEVER ENCODED */
02SPEC_MODE

UTF-8 Octet Percent Encoding

Characters outside the ASCII range (such as emojis or international scripts) are first converted to their UTF-8 byte representation, and each byte is emitted as a three-character sequence "%XX".

"🚀" -> F0 9F 9A 80 -> "%F0%9F%9A%80"
03SPEC_MODE

The Plus (+) vs Percent-20 (%20) Distinction

In standard RFC 3986 URI paths, a space is encoded as "%20" and a plus sign "+" is a literal character. In query strings encoded as application/x-www-form-urlencoded, spaces are serialized as "+", which requires form mode decoding.

Path: "/my%20file" vs Query: "?q=my+query"
! // DIAGNOSTICS / ERROR_REMEDIESRESOLUTIONS

Common URL Encoding Errors & Fixes

Diagnose and correct malformed URI errors, double-encoding bugs, and plus-sign confusion:

ERR_URI_MALFORMEDURIError: URI malformed

Root Cause: The string to be decoded contains a percentage sign "%" that is not followed by two hexadecimal digits, or contains split UTF-8 surrogate code units.

Solution: Ensure every percentage sign is followed by two valid hex digits (e.g. %20), or escape raw % characters as %25 before decoding.

ERR_DOUBLE_ENCODINGOutput contains %2520 or %252F (Double Encoding)

Root Cause: A previously percent-encoded string was passed into an encoder again, causing % to be encoded into %25.

Solution: Decode the string once before re-encoding, or ensure your API client does not automatically re-encode already escaped query values.

ERR_PLUS_LITERAL_COLLISIONPlus signs (+) not converting to spaces

Root Cause: The input was encoded using form mode (where + denotes a space), but was decoded using standard Component mode.

Solution: Switch the tool mode to "Form value mode" to properly decode + into whitespace.

# // BOUNDARIES / PLATFORM_LIMITSINVARIANTS

Platform Limitations & Server Bounds

Key constraints regarding URL length restrictions and international domain name handling:

  • HTTP Server Length Limits: While RFC 3986 specifies no arbitrary limit on URI lengths, practical web servers (like Nginx, Apache, or Cloudflare) enforce query length caps between 2,048 and 8,192 bytes. Large payloads should be transmitted via HTTP POST bodies.
  • International Domain Names (IDN): Domain hostnames containing Unicode characters require Punycode translation (e.g. xn--...) rather than standard percent-encoding.
  • 100% Client-Side Execution: All URL conversions run strictly in your local browser memory; no URL strings are transmitted to remote servers.
// UTILITY_GRAPH / COMPANION_TOOLS
002ENCODING

Base64 Text Encoder

Convert text payloads to URL-safe Base64 for query strings and JWT tokens.

006CRYPTO

Hash Generator

Generate cryptographic hashes (SHA-256) of URL strings for cache keys and canonical identification.