Percent-escape bytes

Nearby workflows on Toolcore

• URI percent-encoding (encodeURI) — encodeURI/decodeURI vs encodeURIComponent/decodeURIComponent—full URI strings vs components, in the browser. when the payload needs a different encoding or escape format.
• URL parser — Split URLs into protocol, host, path, query, and hash—browser URL API; optional https:// assumption; no fetch. when the payload needs a different encoding or escape format.
• Base64url (URL-safe) encode & decode — UTF-8 ↔ Base64url (RFC 4648: -, _, padding optional on decode)—same bits as Base64, JWT-segment style; client-side. when the payload needs a different encoding or escape format.
• Encoding tools — Hub index: Base64 & URL, Base64url, Base32, Crockford, LEB128, ASCII85, Z85, Base58, base-36, bencode, Morse, quoted-printable, URI, Puny… when the payload needs a different encoding or escape format.

Common use cases

• Percent-escape bytes for quick local checks without uploading data.
• Copy results into tickets, docs, or classroom notes.

Common mistakes to avoid

• Unexpected input shape

  See the intro and how-to notes for accepted formats.

FAQ