URL encode / decode

• component — wraps encodeURIComponent. Escapes everything except A-Z a-z 0-9 - _ . ! ~ * ' ( ). Use this when you're encoding a single piece of data that will sit inside a URL (query value, path segment, form field).
• full URI — wraps encodeURI. Leaves URL-structural characters intact (; , / ? : @ & = + $ #). Use this on an already-assembled URL where you only want to escape stray spaces or unsafe characters.
• form — like component but also turns spaces into +. This is what HTML forms submit as application/x-www-form-urlencoded.

Three patterns that cause most of the URL-encoding bugs we see:

• Double-encoding — encoding an already-encoded string. %20 becomes %2520, which servers happily decode back to %20 instead of a space.
• Encoding a whole URL with encodeURIComponent — this escapes :, / and ?, breaking the URL grammar. Reserve component-encoding for a single value, not a full URL.
• Forgetting + in query values — in a query string, + means space, so a literal plus has to become %2B.

Parse mode runs the input through the browser's URL constructor and shows every piece: protocol, hostname, port, pathname, search, hash, origin, plus a key/value table of every query parameter (already decoded). Use it for:

• Inspecting a webhook payload to see exactly what parameters arrived.
• Auditing a tracking-tagged URL you got in an email.
• Pulling a single parameter (e.g. state) out of an OAuth callback URL.
• Checking that a URL is well-formed before pasting it into config.

Because nothing is uploaded, this is safe for parsing URLs that contain secrets (session IDs, OAuth tokens, signed download links). Server logs of the host you came from won't see the parsed contents either — the URL string only ever existed in your browser tab.