HAR to cURL Converter

How to use

1. 1Drop a .har file onto the input area, pick one with the file picker, paste the HAR JSON, or click Load sample to load a runnable example with four representative requests.
2. 2Use the search box, status filter, and method filter to narrow the list to the request you want to replay (for example, only 4xx errors, or only POST requests against api.example.com).
3. 3Click a row in the request list to preview the captured method, URL, host, header count, and body type on the right.
4. 4Pick a shell flavor: POSIX (Bash, Zsh, Git Bash, WSL), Windows PowerShell, or Windows CMD. Quoting and line continuations adjust to match the shell.
5. 5Copy the multi-line command for a runbook, the one-line command for a chat or ticket, or use Copy all to grab every filtered request as a single comment-separated script.
6. 6Watch the warnings panel: multipart file parts surface their original filenames so you can replace each placeholder with a real path on the machine running curl.

About this tool

HAR to cURL Converter takes a HAR 1.2 export from Chrome, Edge, Firefox, or Safari devtools (or from Charles, Playwright, httptoolkit, or any tool that writes the same JSON shape) and turns each captured request into a runnable curl command. Drop the .har file, paste the JSON, or click Load sample to see a realistic example with a GET that carries a query string and cookie, a POST with a JSON body, a form-urlencoded login, and a basic-auth PUT. Every request in the file shows up in a filterable list with method, status, host, and path; search by URL, host, or MIME type, narrow down to 4xx and 5xx errors, or pick a single method. Click any row to render its curl command on the right. Three shell flavors are supported with the right escaping rules. POSIX (Bash, Zsh, Git Bash, WSL) uses single-quoted arguments with the close-and-reopen trick for embedded apostrophes and backslash line continuations. Windows PowerShell uses double-quoted arguments with backtick escaping for backticks, double quotes, and dollar signs to prevent interpolation, and backtick line continuations. Windows cmd.exe uses double-quoted arguments with doubled inner quotes and percent escaping, plus caret continuations. Headers, query strings, cookies, JSON bodies, form-urlencoded bodies, and multipart parts all round-trip. The Authorization header is decoded automatically: a Basic credential becomes a curl -u username:password pair, while bearer tokens stay in the Authorization header. Connection-level headers and HTTP/2 pseudo-headers (:method, :path, :authority) are stripped so the command works against an HTTP/1.1 endpoint. Multipart file parts are emitted with the original filename as a placeholder so you can swap in a real path before running. Both a multi-line command and a paste-anywhere one-line command are available, and a Copy all button concatenates every filtered request as a single shell-comment-separated script for batch replay. Useful for backend engineers reproducing a captured failure outside the browser, QA engineers turning a manual session into a regression script, performance engineers seeding a load test, security testers replaying an attack chain, and anyone who has ever had to copy a request out of devtools by hand. All parsing, decoding, and code generation runs in the browser, so the HAR file, headers, auth tokens, and request bodies never leave your device.

Free to use. Works in your browser. No signup, no login.