Docs / Capturing Traffic
Content Viewers
Purpose-built viewers for every kind of payload.
The Request and Response panes sit side by side, each with its own tabs (Headers, Query, Body, Cookies, Raw, Hex; the Request pane also has Summary). The content adapts to the selected request:
- Summary: URL, status, method, content type, timing, sizes, connection, TLS, and the server certificate (plus GraphQL and gRPC details when present).
- Headers: request/response headers (HTTP/2 pseudo-headers separated).
- Query: the URL's query parameters as name/value pairs.
- Body: pretty-printed JSON, syntax-highlighted XML / HTML / JavaScript / CSS / YAML, formatted form data, and plain text. JSON switches between Text and a collapsible Tree; HTML between Source and Preview.
- Images and PDFs: inline preview in the Body tab (images with dimensions).
- Multipart: each part's name, content-type, filename, and preview.
- Protobuf: decoded field by field, including gRPC frames.
- Cookies: parsed name/value plus domain, path, expiry, and Secure/HttpOnly/SameSite flags.
- Raw: the whole message as text.
- Hex: side-by-side hex + ASCII.
TipWebSocket and SSE requests replace the two panes with a frame or event viewer; see WebSocket.