HAR Waterfall & Status Analyzer

Inspect captured HTTP requests offline, isolate 4xx/5xx API failures, sort endpoints by latency, and audit redacted tokens.

Zero-Upload Guarantee:Processed 100% locally in your browser via WebAssembly & client-side JavaScript. Disconnect Wi-Fi and it still works.(Includes a synthetic 3-request checkout HAR sample)
Drop a .har capture file here
Parses HTTP requests, timings, cookies, and auth tokens completely inside your browser tab.

Diagnosing Slow Endpoints & HTTP Failures Offline

When a QA engineer or customer sends a browser-exported .har trace containing 200+ asset requests, finding the one failing 422 Unprocessable Entity or sluggish API timeout inside raw JSON can feel like hunting in the dark—yet uploading production HAR traces to external web viewers exposes active cookies and OAuth credentials.

This browser-only analyzer parses log.entries[] in local memory, summarizes total requests, unique hosts, and 4xx / 5xx error counts, and lets you switch instantly between capture order and Slowest First with proportional latency bars. Built-in token redaction stays enabled by default so every copied curl command or exported .har stays safe to paste into bug tickets.

QA Triage Workflow & Terminal Equivalent

  1. Drop a Chrome, Edge, Firefox, or Charles Proxy .har capture above, or click Try sample .har (with mock secrets).
  2. Filter by 4xx / 5xx to find rejected calls, or click Slowest First to check backend bottlenecks.
  3. Review the Redaction Audit tab and click Download Sanitized .har to attach a scrubbed trace to your ticket.
# List non-2xx requests sorted by latency locally with jq
jq -r '.log.entries | sort_by(-.time)[] | select(.response.status >= 400) | "\(.response.status)\t\(.time | round)ms\t\(.request.method)\t\(.request.url)"' capture.har

What It Does & Does Not Read

Frequently Asked Questions

Does this HAR file analyzer inspect timing and errors locally?

Yes. Your .har capture stays inside browser RAM. Latency bars, HTTP status filtering (2xx/3xx/4xx/5xx), and unique host metrics compute strictly on the client side.

Does this viewer hide secrets if I decide to download the HAR or copy cURL afterward?

Yes—automatic redaction of Authorization headers, Cookies, query secrets, JWTs, and emails is enabled by default whenever you copy cURL or download a cleaned .har attachment.

How do I spot the slowest or failing API requests quickly?

Click the "4xx / 5xx" status filter pill to isolate errors, or switch sorting from Capture Order to "Slowest First" to surface high-latency endpoints immediately.

Live · Offline

HAR Sanitizer & Token Redactor

Redact Authorization headers, Cookies, API keys, JWTs, query secrets, and email PII from .har logs before sharing.

Open tool
Live · Offline

HAR Request to cURL Converter

Select any API request captured in a .har log and generate a shell-escaped cURL command with optional token masking.

Open tool
Live · Offline

Parquet Viewer & SQL Inspector

Open .parquet files locally, inspect column schema & row groups, run SQL queries, and export CSV/JSON without uploading.

Open tool
Live · Offline

Parquet to CSV Converter

Select columns from local Apache Parquet files and export clean RFC-4180 CSV directly in browser memory.

Open tool