Skip to content
yutils
Example

Input (encode mode)

hello yutils!

Output

hello%20yutils%21

Note

Spaces become `%20` and `!` is escaped for safety. Decode mode reverses the transformation exactly.

Usage / FAQ

When to use

  • Embed multi-byte / special characters in URL query parameters (e.g. search terms)
  • Safely include Korean category names in API endpoint paths
  • Decode an opaque URL from another site to see where it points
  • Analyze redirect chains — peek inside `?redirect=` parameters
  • Check whether a long URL inside an email body is properly encoded

FAQ

Q.encodeURI vs encodeURIComponent?
A.encodeURI keeps reserved characters like `:`, `/`, `?`, `#` intact for full URLs. encodeURIComponent is for fragments like query values — it also encodes `:` and `/`. This tool uses component semantics.
Q.Should space be `+` or `%20`?
A.URL paths use `%20`; application/x-www-form-urlencoded bodies use `+`. This tool follows the path convention (`%20`) — form data needs an extra step.
Q.What if I encode an already-encoded string?
A.`%20` becomes `%2520` — double encoding. A common debugging pitfall — always check whether the input is already encoded first.
Fun facts
  • Percent-encoding (`%20` and friends) in URLs was formalized in 1994 by Tim Berners-Lee in RFC 1738, with RFC 3986 (2005) as the current standard. `%XX` is the hex value of a byte — and with multilingual URLs growing, UTF-8 + percent-encoding has become the de facto pairing.

    RFC 3986 (2005)
  • RFC 3986's 'unreserved' set — `A-Z a-z 0-9 - _ . ~` — is the small group of characters you can safely embed without encoding. Older RFC 1738 had a wider unreserved set (including `+ - $ . , !`), which was narrowed for compatibility.

    RFC 3986 — Unreserved Characters
  • A classic space-encoding gotcha — inside URL paths it's `%20`, but inside `application/x-www-form-urlencoded` query strings it's `+`. `encodeURIComponent` only emits `%20`; form submissions get `+` treatment from the browser. Two rules in two places, going on 30 years.

    WHATWG URL — Form encoding