Cookie Header

Split a Cookie header into name=value lines.

Splits on semicolons and keeps name=value pairs. Unlike Query to JSON this is not a URL query. Unlike User-Agent this is not a browser string. Missing equals fails. Local only.

Splits on semicolons and keeps name=value pairs. Unlike Query to JSON this is not a URL query. Unlike User-Agent this is not a browser string. Missing equals fails. Local only.

Practical limit for Cookie Header: Semicolon pairs with equals. Empty fails. Not a URL query. That is why output can differ from heavy desktop Network software. Read the tool-specific note again: Splits on semicolons and keeps name=value pairs. Unlike Query to JSON this is not a URL query. Unlike User-Agent this is not a browser string. Missing equals fails. Local only.

  1. Keep this tab on Cookie Header (/network/cookie-header). Pasting into the wrong Network tool (for example User-Agent Parse) changes the job.
  2. Paste or type the input Cookie Header expects. Path hint: network · cookie header. Split a Cookie header into name=value lines.
  3. Apply the Cookie Header action only. Parse URL is a different transform (Split a URL into host, path, query, and more.). Splits on semicolons and keeps name=value pairs. Unlike Query to JSON this is not a URL query. Unlike User-Agent this is not a browser string. Missing equals fails. Local only.
  4. Copy the output of Cookie Header if you need it elsewhere. Size/complexity still follows: Semicolon pairs with equals. Empty fails. Not a URL query.
  5. If the text job is actually Guess browser family, version, OS, and mobile., leave Cookie Header and open User-Agent Parse.

Skip Cookie Header when a neighbor tool matches better — start with User-Agent Parse or Parse URL — or when the description already warns the job will fail. In the tool’s own words: Splits on semicolons and keeps name=value pairs. Unlike Query to JSON this is not a URL query. Unlike User-Agent this is not a browser string. Missing equals fails. Local only.

What does Cookie Header do that other Network pages on this site do not?
Splits on semicolons and keeps name=value pairs. Unlike Query to JSON this is not a URL query. Unlike User-Agent this is not a browser string. Missing equals fails. Local only. Short version: Split a Cookie header into name=value lines.
Does Cookie Header upload my file or text to Tool-You servers?
No. Cookie Header runs in this browser tab. Files stay on the device. Limit note: Semicolon pairs with equals. Empty fails. Not a URL query.
Should I use User-Agent Parse instead of Cookie Header?
Use Cookie Header when you need Split a Cookie header into name=value lines. Use User-Agent Parse when you need Guess browser family, version, OS, and mobile. They share a category (Network) but not the same job.
What are the limits of Cookie Header?
Semicolon pairs with equals. Empty fails. Not a URL query. Also: Splits on semicolons and keeps name=value pairs. Unlike Query to JSON this is not a URL query. Unlike User-Agent this is not a browser string. Missing equals fails. Local only.