SSE Event Stream Viewer
Inspect live Server-Sent Events or parse SSE text offline, including named events, multiline data, IDs and reconnection.
Connecting sends data directly to the specified server.
Inspect a stream or a saved response
Live mode makes an explicit GET request after Connect. Enter a full HTTP(S) address, choose credential and redirect policies, and optionally set an initial event ID. Example fills an offline sample and never contacts a public service. Parse text works locally and can inspect SSE saved from an API response.
The report retains event names, exact joined data, last event IDs, timestamps, connection attempts and readable HTTP headers. Values stay text; HTML is never rendered and event data is not assumed to be JSON. UTF-8 is decoded across byte boundaries, with replacement for invalid sequences as in an event stream.
Event boundaries and resuming
A blank line completes an event. Repeated data fields join with a newline; an empty data field produces an empty message. CRLF, LF and CR line endings are accepted. One leading BOM is ignored, comments and unknown fields do not become messages, and an incomplete final event is discarded. ID-only blocks update the resume ID; a NUL in an ID makes that field invalid.
This viewer uses Fetch streaming to expose all event names and response details. It is not the browser EventSource object: reconnection is off by default, capped at 10 attempts, and has an explicit session deadline. On a clean EOF or network failure it may retry with the last completed ID encoded in Last-Event-ID. A server retry directive takes effect immediately; delay is clamped to 250–60,000 ms. The default delay is 3,000 ms. Fetch trims edge HTTP whitespace from header values, so an ID starting or ending with a space or tab cannot be sent faithfully and is rejected for initial requests and reconnection. Such IDs are still preserved in parsed event data.
Server setup and limits
Return HTTP 200 with Content-Type: text/event-stream, flush complete records and configure CORS for this origin. HTTP 204 closes without retrying. Other HTTP statuses or wrong content types stop the session. Redirects are rejected unless Follow is selected; Fetch browser policies and credential restrictions still apply. There is no server-side proxy or POST support.
The session is limited to 1–600 seconds (60 by default), 8 MiB received, 1,000 log records or 2 MiB of log data. Lines are capped at 65,536 characters, event data at 262,144 characters, and offline input at 1 MiB. Headers have a 10-second connection deadline. A resume ID must fit 1,024 UTF-8 bytes. Oversize limits stop rather than silently truncate the live stream.
Preview stops at 200,000 characters; Copy and Download report retain the complete bounded report. Stop cancels reading and any waiting retry. Changing connection fields or mode clears the old session; leaving the page aborts it. Credentials and event payloads can be sensitive; no log is saved to browser storage.
Questions & answers
Why are no events appearing?
The server must flush a blank line after data fields. Proxies may buffer output; comments are not dispatched as messages. Check the visible status, content type, CORS and session limits.
Is the event ID a delivery guarantee?
No. Last-Event-ID is a resume hint. The server decides retention and replay; reconnection can still lose or repeat events.
Other Languages
References
How we make sure
We check this tool with the automated test suites linked below. Example checks are shown in their original language.
- Verification method
- Split SSE streams at byte boundaries and check Unicode, newlines, IDs, reconnection and stopping on HTTP 204.
- Comparison reference
- Explicit SSE event fixtures and local HTTP server responses.
- Verification scope
- These samples and boundaries do not prove correctness for every input.
Test source and cases (select a file to read it)
-
stream-tools.test.js
- SSE standard fields, exact multiline/empty data, comments, case and unknown fields
- SSE id-only blocks, reset, NUL ignoring and uncompleted EOF state
These checks cover the listed examples and boundaries, not every possible input. Round trips and checks using the same library are not independent verification.