Free tool
Local HAR analyzer
Inspect a HAR network recording locally to identify failed requests, slow responses, and request timing without replaying traffic.
Inspect a network capture locally
Choose a HAR 1.2 file up to 20 MiB and 10,000 requests. Parsing happens in a local browser worker. Your file stays in this tab and requests are never replayed.
Maximum 20 MiB. Files with more than 10,000 requests or nesting deeper than 32 are rejected.
Builder example: compare a successful read with a slow HTTP 500 submission. Agency / QA example: distinguish a missing resource from a request with no recorded response. Both are synthetic captures.
Read the evidence carefully
Failed includes HTTP 4xx and 5xx responses and status 0, where no HTTP response was recorded. A redirect is not automatically a failure. Missing or negative timing fields are shown as unknown, never as zero.
Slowest sorts by the recorded total time. SSL can be included in connection time, so these fields are not added together. A long wait is evidence to investigate, not a diagnosis of the server or network.
Request numbers follow the original HAR entry order. This view and its copied summary omit URLs, headers and bodies. Use the HAR sanitizer when you need to review a redacted file before sharing it.
Examples for your team
Builder example
A builder compares a failed checkout request with its HTTP status and timing to identify the first network failure.
Start your 14-day free trialAgency / QA example
A QA tester groups slow requests from a staging session and shares only reviewed findings with the client delivery team.
Start your 14-day free trial