Processed locally

HAR Analyzer Online

Open a HAR file and inspect network requests, failures, timings, detected issues, sanitized evidence, and AI-ready debug context without uploading the file.

What this tool does

HAR Analyzer is a local HAR file analyzer for browser network captures. It combines a HAR file viewer with a HAR file reader so you can open a HAR file, explore a searchable request timeline, inspect failed and slow requests, review timing data and request details, and prepare sanitized debug context without uploading the capture.

How to use

Follow the core workflow below. Use “Show in tool” to locate the real control in the live tool above.

  1. Load the HAR capture

    Drop a .har file into the tool or choose it from your device. Processing starts locally after the file is loaded.

    Drop your HAR file hereChoose HAR file
  2. Find the requests worth investigating

    Start with the summary, then narrow the request list. Use Failed or Slow status filters, or search by URL, host, or path.

    Status filterFailedSlowSearch URL, host, or path…
  3. Inspect one request in detail

    Select a row in Network Requests, then review Request Details. Use Overview, Headers, Payload, Response, or Timing depending on the problem you are debugging.

    Network RequestsRequest DetailsTiming
  4. Prepare focused debug context

    Optional

    After selecting a request, use Create AI Debug Context if you want a smaller debugging package. Review the Privacy Check before copying anything outside the tool.

    Create AI Debug ContextPrivacy Check

    Select a request first to enable this action.

Success

You have isolated a relevant network request and can inspect the evidence needed for the next debugging step.

Examples

Investigate an API failure

Filter for 4xx and 5xx responses, open the failing request, and compare its headers, timing, and response details.

Find a slow page dependency

Sort or filter by duration to identify the requests that dominate loading time and inspect their timing phases.

Common errors

  • The selected file is not valid HAR JSON or does not contain a log.entries array.
  • A capture is incomplete because DevTools stopped recording before the request finished.
  • Sensitive headers require sanitization before evidence is copied into an issue or AI prompt.

AI workflow

Reduce a large capture to the failed request, its timing, sanitized headers, response evidence, and a concrete debugging task. Copy that structured context into your coding agent instead of pasting the raw HAR.

Frequently asked questions about HAR Analyzer