⌘ K
har → curl · browser exports · per-request · live

Replay a HAR log as cURL

Paste an HTTP Archive (HAR) exported from Chrome, Firefox or Safari DevTools and get one cURL command per request. Headers, methods and request bodies all carry across.

HAR → cURL
Input
325 B
16 lines
Output
166 B
5 lines
Status
ready
live
Ratio
0.51×
out/in
input · har json
output · curl
# Request 1: GET https://api.example.com/users
curl -X GET \
  'https://api.example.com/users' \
  -H 'Accept: application/json' \
  -H 'Authorization: Bearer abc123'
Quick Start

How HAR replay works

Each log.entries[] item describes one HTTP request. We emit a labelled cURL command per request and skip browser-managed headers (Host, Content-Length, Cookie) so the commands replay cleanly.

  1. 01

    Export HAR

    In DevTools Network panel: right-click → Save all as HAR with content.

    Parsing is strict-but-tolerant — comments and trailing commas are accepted on input where the source format historically permits them; output stays canonical.

    exportstricttolerantliveparse
    devtools · sourcehar · live
    Save all as HAR
    loaded · parsedtarget · ready
  2. 02

    Paste JSON

    Drop the entire .har file contents — it's just JSON.

    Conversion preserves type information where the target supports it (numbers stay numeric, booleans stay boolean) so the destination parser never has to re-coerce.

    inputtype-preservinglosslesslivememoised
    in · optionsjson · live
    { "log": { "entries": [...] } }
    options applied · liveround-trip
  3. 03

    Per-request cURL

    Each entry emits a # Request N: METHOD url header and a multi-line cURL command.

    Re-encoding is idempotent: running output back through the same converter produces the same bytes, which keeps round-trips git-friendly.

    emitidempotentround-tripdiff-cleandeterministic
    n requests · convertedn curls · ready
    curl -X GET 'https://...' \
  -H 'Accept: application/json'
    converted · livediff-clean
  4. 04

    Copy or download

    Save as .sh and run, or paste individual commands into your terminal.

    Copy writes via navigator.clipboard.writeText; downloads use the target’s native MIME so editors apply the right syntax highlighting on open.

    replayclipboardtarget MIMEblobclient-side
    ✓ · copiedready · done
    ✓ Copied
    shipped · ready to shipsuccess
Pro tips

Converting between formats, safely

Pick the strictest source format

Lossy formats hide bugs. Choose JSON or YAML as your source-of-truth, convert downstream as needed.

Round-trip in CI

If your converter is idempotent, your CI can verify A → B → A equals the original. Catches subtle data loss.

Numbers vs strings differ

YAML/TOML have a number type; CSV doesn’t. Quote IDs in CSV to keep leading-zero values intact.

Watch character encoding

Source format may be Latin-1 / Windows-1252; target should be UTF-8. Convert encoding before structure.

Preserve comments where you can

YAML and TOML support comments. Don’t silently drop them — they often encode intent.

Schema-aware beats blind

Use a schema to guide conversion. Field types, required-ness, and defaults survive better with structure.

Related toolscURL to fetch()cURL to CodecURL to PythoncURL to NodecURL to GocURL to PowerShell
Use Cases

When to replay HAR

Debug, share, regression-test.

Bug reproduction

Hand a failing flow to a backend dev as runnable curl commands. Type information survives: numbers stay numeric, booleans stay boolean, strings stay strings. The destination parser doesn't have to re-coerce, which avoids the "'true' becomes "true"" bug class.

round-trip safe

Load testing

Bootstrap a request set for k6 / hey / wrk. Run output back through the inverse converter to verify idempotent round-trips in CI. A → B → A should produce byte-identical input — if it doesn't, you've found data loss.

type-preserving

API documentation

Lift recorded requests straight into curl examples. Comments and metadata survive where the target format supports them (YAML, TOML, HCL). The tool doesn't silently drop intent-encoded annotations, which keeps your config self-documenting.

schema-aware

Test fixtures

Snapshot a user journey as a deterministic script. Pair with a schema (JSON Schema, OpenAPI, Zod, Pydantic) to catch shape drift on either side. Catch breaking changes at conversion time rather than at runtime in production.

lossless

Outage forensics

Replay a session captured before an incident to compare behaviour. Output respects target-format conventions: quoting in CSV, indent in YAML, brackets in JSON. Existing parsers don't need patches, and the result drops into legacy pipelines unchanged.

diff-clean

Hand-off

Share network traces with teammates who don't have your browser open. Encoding-aware: handles UTF-8 vs UTF-16 vs Latin-1 / Windows-1252 transparently. The character-set surprise that breaks "works on my machine" doesn't apply here.

spec-grade
FAQ

Frequently asked questions

Cookie headers are dropped because they're often session-scoped. Add -b 'name=value' manually if you need them.
Yes — request.postData.text becomes --data on the matching command.
Text bodies only. Multipart binary uploads need the original file plus -F flags.
curl sets Host automatically from the URL; including the original would conflict.
No. HAR parsing and cURL emission run locally in your browser.
Suggest a tool

Something missing?

Tell us what you need. We ship the top requests every two weeks.

Sent straight to the maintainers · no account needed
47 in queue·8 shipped this month
Request queued. Thanks!