About The HTTP Response Parser

The HTTP Response Parser converts a raw status line, headers, and optional body into structured JSON so response captures are easier to inspect and share.

Everything runs locally in the browser. Remove secrets, session data, customer records, and internal server details before pasting real response captures.

How to Parse an HTTP Response Online

1. Paste the raw response into the Raw HTTP response box, starting with the status line.
2. Keep the blank line between response headers and body if a body is present.
3. Click Parse Response to create the JSON output.
4. Review or copy the HTTP version, status code, reason phrase, headers, and body.

Choosing Options Correctly

Status line:
- Use the original line, such as HTTP/1.1 200 OK.
- If parsing fails, check that the response starts with an HTTP version and three-digit status code.

Headers and body:
- Keep one header per line with a colon after the header name.
- Preserve the empty line before the body so payload text is not treated as a header.

Common Use Cases

• Inspecting API responses captured from proxies or logs.
• Checking status codes and headers during integration debugging.
• Turning raw response examples into structured documentation snippets.
• Comparing response bodies while keeping metadata visible.

Quick FAQ

Does this fetch a URL?
No. It parses raw HTTP response text pasted into the input.

Will JSON response bodies be parsed as JSON?
Only if the body is valid JSON and the tool provides body parsing. Otherwise it remains raw text.

Why are headers missing?
The response may be copied without the header block, use unusual line endings, or contain malformed header lines.

Can it parse compressed responses?
No. Paste the decompressed response text if the body was gzip, br, or deflate encoded.