Browser-based tool

HAR File Analyzer

Load a HAR locally, narrow the blast radius in under a minute, and jump straight into safe-share cURL, fetch, or bridge payloads without sending the HAR to a server.

UseKit Home Open analyzer Scope and replay notes

Quick HAR triage

Open, drop, paste, or sample-load a HAR file to inspect slow requests, failures, redirects, initiator guesses, domains, and privacy risk without backend upload.

How to export a HAR file

If HAR is unfamiliar, you can usually export it from the browser Network panel.

  • Chrome / Edge F12 → Network → Reload page → Right-click request list → Save all as HAR with content
  • Shortcut path F12 → Network → Reload page → Export HAR
Client-side only Safe-share by default Bridge fallback included
Waiting for a HAR Open a HAR, paste JSON, drop a file, or load the sample to start analysis.
Drop a HAR file here to start local analysis Supported input shapes: log.entries, entries, or a top-level entries array. Chrome and Edge extension fields are used when present.

HAR workspace

Filters, thresholds, and selection stay shared across Overview, Requests, Waterfall, Initiators, Domains, Redirect chains, and the detail panel.

No HAR loaded yet

The main analyzer shell opens after you open a HAR, paste JSON, drop a file, or load the bundled sample.

Know what this HAR can and cannot tell you

Review the input shape, safe-share behavior, replay limits, and next steps before you copy snippets or send anyone a HAR-derived export.

What this tool does

Open a HAR locally, inspect requests, and move into triage views, privacy warnings, safe-share cURL or fetch, and bridge payloads without uploading the HAR to a backend.

Best for

  • Reviewing a browser export before sending it to support or a teammate.
  • Finding failures, slow requests, redirects, domains, and likely privacy risk fast.
  • Generating a safer starting request for replay, reproduction, or bridge tooling.

Not for

  • Exact browser replay with full cookie, cache, TLS, or service-worker fidelity.
  • Server-side log analysis across many sessions or very large tracing pipelines.
  • Sharing raw HAR files blindly when sensitive headers or payload hints may exist.

Input

Open a HAR file, drop one into the page, or paste HAR JSON. Chrome and Edge exports are the common starting point, and partial HAR shapes are still handled with warnings.

Output

Export summary JSON, copy safe-share cURL or fetch, inspect bridge payloads, and use the warnings, fidelity notes, and request detail panels as reusable troubleshooting output.

How to use

  1. Export a HAR from the browser Network panel and open it here.
  2. Filter the request list until the failing or slow request set is small enough to review.
  3. Copy safe-share output or export summary JSON after checking warnings and privacy notes.

Privacy / local processing

Safe-share mode is the default. It redacts sensitive header values, query values, payload hints, snippets, bridge payloads, raw previews, and summary exports before anything is copied.

The HAR file stays on this device for the core workflow, but raw mode can still reveal sensitive values on screen if you choose to inspect them.

Limits / tradeoffs

Partial HAR files, missing timings, header maps, status 0, redirect gaps, and Chrome or Edge extension fields are handled with warnings instead of hard crashes.

Replay output is approximate. Cache state, session cookies, service workers, TLS state, and runtime environment details are not reproduced exactly from HAR alone.

FAQ

Does safe-share remove the raw HAR itself?

No. Safe-share protects copied snippets and exported summaries. The original HAR remains as loaded until you clear it.

Can I use the generated cURL as an exact replay?

No. It is a practical starting point, not a full browser-state replay.

What if the HAR is incomplete or missing timings?

The analyzer still loads many partial exports and surfaces warnings so you can decide what is still trustworthy.

Last updated

April 5, 2026