Parse HTTP headers
Paste a raw request or response and get the headers as clean name/value pairs — so you can read the Content-Type, cache directives, and auth headers without squinting at one long block.
Open the tool, then paste the sample input below. Everything runs locally in your browser.
The problem
Headers copied from curl -v or browser dev tools arrive as a dense block. Finding the one header that explains a caching or content-type bug means parsing them into readable pairs. Splitting and normalizing them makes the relevant directive obvious.
Sample input
HTTP/1.1 200 OK
Content-Type: application/json; charset=utf-8
Cache-Control: no-cache, no-store
X-Request-Id: abc-123Expected output
Content-Type application/json; charset=utf-8
Cache-Control no-cache, no-store
X-Request-Id abc-123The status line is separated from the headers, and each header is split into a name and value at the first colon so multi-value directives stay intact.
How to do it
- Paste the raw request or response headers.
- Parse them into name and value pairs.
- Find the header you care about, such as Content-Type.
- Read multi-value directives like Cache-Control.
- Copy the parsed view.
Common mistakes
- Splitting on every colon, breaking values that contain a colon (like a URL or time).
- Treating header names as case-sensitive — they are case-insensitive.
- Losing a folded or repeated header such as multiple Set-Cookie lines.
- Confusing request headers with response headers.
- Including the status line as if it were a header.
Related tools
Related guides
FAQ
How do I parse raw HTTP headers?
Paste the raw block and split each line at the first colon into a name and value. The status line is separated out, and the result is a readable list of header pairs.
Are HTTP header names case-sensitive?
No. Header names are case-insensitive, so Content-Type and content-type are the same header. Values may be case-sensitive depending on the header.
Why split on the first colon only?
Values can contain colons, such as a timestamp or URL. Splitting on the first colon keeps the full value intact.
How are repeated headers handled?
Headers like Set-Cookie can appear multiple times. Each occurrence is kept as its own pair rather than overwriting the previous one.
Are my headers uploaded?
No. Parsing runs locally in your browser. Your headers are not sent to a server.
Header parsing runs locally in your browser. Nothing is uploaded.
Parse headers and URLs, sanitize captures, verify webhooks, plus every other utility.