Back to feed
Dev.to
Dev.to
7/13/2026
The original title is: "URL Encoding Decoded: A Developer's Guide to encodeURI vs encodeURIComponent"

The original title is: "URL Encoding Decoded: A Developer's Guide to encodeURI vs encodeURIComponent"

Original: URL Encoding Decoded: A Developer's Guide to encodeURI vs encodeURIComponent

Short summary

A developer's guide to JavaScript's encodeURI vs encodeURIComponent, explaining when to use each to avoid common URL-encoding bugs. encodeURI preserves URL-structural characters for full URLs, while encodeURIComponent encodes everything for query parameter values. The article recommends URLSearchParams as the safest approach for building query strings.

  • •Use encodeURI for full URLs; it preserves structural characters like ?, &, =, #, /
  • •Use encodeURIComponent for individual query parameter values to encode everything
  • •Prefer URLSearchParams over manual concatenation for correct, browser-safe encoding

Generated with AI, which can make mistakes.

#ai-tools
Read full article at Dev.to

Is this a good recommendation for you?

Comments

Failed to load comments. Please try again.

Explore more

atob() can't decode a JWT — the Base64URL gotcha (and the fix)
Dev.to
URL Parameters vs Query Strings in Express.js
Dev.to
The original title is about "decode bombs" - URL decoding vulnerabilities. Let me rewrite this as a punchy mobile feed headline.
Dev.to
The headline is about JWT security - pasting JWTs into online decoders leaks credentials, and there's a browser-only fix.
Dev.to