SSE (Server-Sent Events) Stream Parser
Paste the raw body of a text/event-stream response and see exactly which events a browser would dispatch, and what would be dropped.
Use the tool
Why this tool exists
When a streaming API misbehaves, the cause is often in the framing: a missing blank line that leaves an event undelivered, a multi-line data field, a stray carriage return, or a retry value that was ignored. Reading raw bytes does not tell you what EventSource will actually do.
This parser follows the WHATWG rules: lines end in LF, CR or CRLF, a leading BOM is dropped, one space after the colon is stripped, data lines are joined with newlines, an event is dispatched only on a blank line, and a trailing event without one is reported as pending rather than delivered. If the data looks like an OpenAI or Anthropic token stream, the text pieces are assembled so you can read the whole reply. It parses a pasted capture; it does not open a connection, which a page that makes no network requests cannot do. Copy the capture from your browser dev tools or from curl -N.
How to use it
- Capture the response body, for example with curl -N or the network tab.
- Paste it into the box.
- Read the dispatched events, comments and any pending event.
- Untick the JSON option if you want raw data strings.
Frequently asked questions
Does it connect to my endpoint?
No. It parses text you paste. Opening a connection would need a network request, and this site makes none.
Why is my last event marked pending?
An event is delivered only when a blank line ends it. If the stream was cut before that line, browsers discard the partial event, and so does this parser.
What is the [DONE] marker?
Some APIs, such as OpenAI streams, end with a data line containing [DONE]. It is ordinary data to SSE; the parser just points it out.
How is retry handled?
A retry field with only digits sets the reconnect delay in milliseconds. Anything else is ignored, as in the specification.