iGuideSmart

URL Encoder & Decoder

Encode and decode URI components safely using encodeURIComponent/encodeURI and inspect parsed query parameters locally.

Formula & Calculation Logic

Uses standard ECMAScript encodeURIComponent (for query parameter values) or encodeURI (preserving protocol/path delimiters).

Primary Formula

Reserved UTF-8 byte → %XX (uppercase hexadecimal)

Example: Encode "a+b & c=1"

  1. 1
    Percent-encode reserved symbols
    + → %2B, space → %20, & → %26, = → %3D
    a%2Bb%20%26%20c%3D1

Common Percent-Encoded URL Characters

RFC 3986 reserved characters frequently encountered in query strings.

Showing 10 of 10 reference values
Reserved URL characters and their percent-encoded values
CharacterEncodedNameTypical Role
(space)%20 or +SpaceSeparates words
&%26AmpersandSeparates query params
=%3DEqualsKey-value assignment
?%3FQuestion MarkStarts query string
/%2FForward SlashPath separator
#%23HashURL fragment identifier
+%2BPlusDecoded as space in forms
%%25PercentEscape prefix itself
@%40At SignEmail / userinfo
:%3AColonScheme / port delimiter

Practical Real-World Use Cases

Building OAuth & Redirect URLs

Safely escape callback URLs and nested query parameters.

Inspecting Analytics & UTM Links

Decode messy tracking URLs into clean key-value pairs.

URL Encoder & Decoder – Frequently Asked Questions

When should I use encodeURIComponent vs. encodeURI?
Use encodeURIComponent for individual query values (it encodes &, =, /, ?). Use encodeURI for an entire URL where you want https:// and / preserved.
Why do spaces sometimes appear as + instead of %20?
HTML form submissions (application/x-www-form-urlencoded) use + for spaces in query strings, whereas RFC 3986 path encoding uses %20.
What causes a URIError when decoding?
Malformed percent sequences such as a lone "%" not followed by two valid hex digits trigger URIError.
View all Developer Tools →