Network
HAR Viewer and Analyzer
Upload a browser network archive to isolate failing and slow requests without replaying any traffic.
How this tool works
HAR entries provide request and response metadata that can expose redirects, failures, content types, and timing outliers. Filters help narrow a synthetic or redacted trace.
HAR can contain tokens, cookies, query values, and bodies. Reports redact common credentials but unusual private fields need manual review before sharing.
Examples
- Sort slow requests in a synthetic trace.
- Count failed status codes.
- Inspect MIME types across hosts.
Common use cases
Worked synthetic example
Valid example
Synthetic HAR: GET /orders → 503, 420 ms
Expected: One failed request with status 503 and 420 ms timing. The archive identifies a candidate failure, not its server-side cause.
Failure or warning to recognize
Warning / interpretation
A HAR report shared before reviewing private query strings and response bodies.
Expected: A report redacts common credential fields but may retain unusual private query or body data; inspect exports before sharing.