HAR Request to cURL Converter

Pick any request from a local .har capture to inspect and copy a shell-safe cURL command—redacted by default for bug tickets, toggleable for local replay.

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.

Turning Captured Browser Traffic Into Clean cURL Snippets

Reproducing an API bug often comes down to pasting a single working curl invocation into a GitHub issue or running it against staging. Manually copying headers out of a multi-megabyte .har file is error-prone—HTTP/2 pseudo-headers (:method, :authority) break standard cURL, and forgetting to strip Cookie or Authorization leaks live user sessions in public tickets.

This local converter parses the capture inside browser RAM, strips HTTP/2 pseudo-headers plus calculated Host/Content-Length headers, builds a POSIX-quoted curl -X ... -H ... --data-raw ... snippet for each entry, and leaves secret redaction enabled by default until you explicitly toggle it off for private terminal replay.

Workflow & Workstation Script Alternative

  1. Drop a .har file above or click Try sample .har (with mock secrets).
  2. Click Inspect on any request row to preview its full formatted command above the table, then click Copy Selected cURL.
  3. Only uncheck Redact secrets & session cookies if you need real local credentials to replay a request strictly on your own machine—never paste unredacted commands into issue trackers.
# Quick jq snippet to inspect request method, URL, and status from a HAR file locally
jq -r '.log.entries[] | "\(.request.method) \(.response.status) \(.request.url)"' capture.har

Security & Shell Quoting Guarantees

Frequently Asked Questions

Does the generated cURL strip HTTP/2 pseudo-headers like :method and :authority?

Yes. Browser DevTools exports Chrome/Edge HTTP/2 pseudo-headers such as :method, :path, :scheme, and :authority plus Host and Content-Length headers that cause curl errors; this converter omits them cleanly.

Are shell special characters like single quotes or $(...) safely escaped?

Yes. Every URL, header pair, and --data-raw payload is single-quoted with POSIX shell escaping so pasting a snippet into bash or zsh cannot trigger accidental command substitution.

Can I keep real headers when replaying locally on my own terminal?

Yes. Automatic secret redaction starts ON so nothing leaks if you copy into Slack or Jira, and you can uncheck "Redact secrets & session cookies" whenever generating a private cURL strictly for local reproduction.

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 Waterfall & Status Analyzer

Inspect captured HTTP entries locally, filter 4xx/5xx failures, sort slowest calls by latency, and check hosts.

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