Does this make a real network request?

No. You paste headers you already have, from browser dev tools, curl -i, or a server log. The tool only parses the text you provide; it never fetches a URL.

What format should I paste?

One header per line as "Name: Value", optionally with a request line (GET /path HTTP/1.1) or status line (HTTP/1.1 200 OK) as the first line. Blank lines and a trailing body are ignored.

What happens with duplicate header names?

Duplicates, such as multiple Set-Cookie lines, are kept as separate rows in the table. In the copied JSON, duplicate values are combined into an array under that header name.

Why does a header show no explanation?

Only common, well-known headers have a built-in explanation. Custom headers (like X-Request-Id or a vendor-specific header) still parse correctly, just without a description.

Is my pasted data stored anywhere?

No. Parsing runs entirely in your browser with JavaScript. Nothing is uploaded, logged, or saved after you leave the page.

HTTP Header Parser

Paste raw HTTP request or response headers and get a structured, labeled table with explanations, plus a one-click copy as JSON.

Raw Headers

Paste headers on the left to see the parsed table

Header	Value	Notes

Copied!

Summary

Paste raw HTTP request or response headers and get a structured, labeled table with explanations, plus a one-click copy as JSON.

How it works

Paste raw headers into the text box, one per line, in "Name: Value" format.
The first line is read as a request line (METHOD /path HTTP/1.1) or a status line (HTTP/1.1 200 OK).
Every following line is split on the first colon into a header name and value.
Known headers get a short explanation pulled from a built-in reference table.
Click "Copy as JSON" to copy the parsed headers as a JSON object to your clipboard.

Use cases

Turn headers copied from browser dev tools into a readable table.
Check what a Cache-Control or Content-Security-Policy value actually means.
Convert a pasted response into JSON for a bug report or documentation.
Spot duplicate or malformed header lines before debugging further.
Review CORS-related headers (Access-Control-*) at a glance.
Inspect Set-Cookie attributes without counting commas and semicolons by hand.

Frequently Asked Questions

Last updated: 2026-09-19 · Reviewed by Nham Vu