⚡DevTools12
VIEN
← Back to home

URL Encode/Decode + URL Parser Online

Encode/decode URL components (percent-encoding) + URL parser breaks into protocol/host/path/query/fragment with a decoded params table. Native URL API.

EncodeDecodeParseQuery params
https%3A%2F%2Fexample.com%2Fpath%3Fq%3Dhello%20world%26lang%3Dvi

Why use this tool

🔗
Native URL API

Uses the browser's URL constructor — WHATWG standard, supports IDN, IPv6, full set.

📊
Query params table

Paste a complex URL → break into a key→value table with each value pre-decoded.

🎯
encodeURIComponent native

Encodes all reserved chars per RFC 3986. Decodes back pixel-perfect.

How to use

  1. 1Pick mode: Encode / Decode / Parse.
  2. 2Paste URL or string into the textarea.
  3. 3Encode: spaces + special chars → %xx. Decode: reverse. Parse: break into a table.

What is URL encoding?

URL encoding (percent-encoding) is the mechanism to represent non-ASCII or reserved characters in URLs as %xx (hex). E.g. space → %20, & → %26.

Reserved characters (RFC 3986): ! * ' ( ) ; : @ & = + $ , / ? # [ ]. encodeURIComponent encodes most; encodeURI keeps some safe for full URLs.

  • ✓encodeURIComponent / decodeURIComponent
  • ✓Native URL parser (WHATWG)
  • ✓Decoded query params table
  • ✓Supports IDN, IPv6, ports
  • ✓Protocol / host / path / hash breakdown
  • ✓100% client-side

FAQ

encodeURI vs encodeURIComponent?

encodeURI for full URLs (keeps : / ? & = #). encodeURIComponent for a single component (encodes everything). The tool uses encodeURIComponent by default — stricter.

Why does Parse mode say invalid URL?

The URL constructor is strict. Needs the full form 'https://...' — bare 'example.com' will fail. Add the protocol first.

Does Vietnamese encode correctly?

Yes. Standard UTF-8 — 'ăn' → %C4%83n. Decoding restores correctly.