HAR file analyzer
Drag in a .har export from DevTools, Charles, or Fiddler and get a scraper-focused diagnosis: which anti-bot vendors fired, where the request chain broke, which headers a real browser would send, and how your cookies behaved. 100% client-side — nothing leaves your browser.
Cloudflare / DataDome / Akamai / PerimeterX / Kasada / Imperva detection • Header diff vs real Chrome • Cookie lifecycle • Per-entry flags
Drop a .har file here
or click to choose one. Parsing happens entirely in your browser.
Diagnostic tool. HAR files often contain cookies and auth headers. We process them entirely in your browser — nothing is uploaded. Still, treat your HAR like a password and never share it publicly. For diagnostic and developer use only.
What is a HAR file?
A HAR (HTTP Archive) file is a plain JSON record of every network request a browser made on a page — URLs, methods, request and response headers, cookies, timings, and response bodies. You export one from any browser's DevTools: open the Network panel, right-click any request, and choose "Save all as HAR". Charles Proxy and Fiddler produce the same format. Because a HAR captures both sides of every request, it's the single best artifact for debugging why a scraper behaves differently from a real browser.
Why your scraper gets blocked when Chrome works
When a request that works in Chrome fails from your script, the difference is almost always visible in the headers and the request chain. The four most common causes: a TLS / HTTP-2 fingerprint that identifies a raw HTTP library, missing Sec-CH-UA-* client hints while the User-Agent claims modern Chrome, a missing Accept-Language header, and cookie-binding failures where a clearance cookie like cf_clearance or datadome is never replayed on follow-up requests. This analyzer flags all four directly on your trace.
What the flags mean
| Flag | Meaning |
|---|---|
| CF | Cloudflare touched this response (cf-ray or Server: cloudflare). |
| CHAL | A challenge / interstitial page was returned instead of content. |
| BLOCKED | A 4xx/5xx that looks like a bot-management verdict. |
| NO-UA | No User-Agent header — every real browser sends one. |
| NO-AL | No Accept-Language header. |
| NO-SECCH | UA claims Chrome 100+ but no Sec-CH-UA-* client hints are present. |
| NO-ENC | No Accept-Encoding header. |
| UA-MISMATCH | UA claims Chrome with no Sec-Fetch-* headers, or claims mobile with Sec-CH-UA-Mobile: ?0. |
| INSEC-FETCH | Inconsistent fetch metadata between Sec-Fetch-Site and the Referer. |
| RAW-CLIENT | The UA identifies a raw HTTP library whose TLS/HTTP-2 fingerprint will not match a browser. |
Frequently asked questions
What's a HAR file?
"HTTP Archive" — a plain JSON record of network requests. Export from any browser's DevTools: Network panel → right-click → "Save all as HAR". Charles and Fiddler export the same format.
Does this tool upload my HAR?
No. The file is parsed entirely in your browser with the FileReader API. Nothing is sent to a server — you can confirm this in your own DevTools Network tab.
My HAR has my session cookies — is that safe?
Yes, because parsing is local. Still, treat your HAR like a password: it can contain auth tokens and session cookies, so never share it publicly without sanitising it first.
Why does my scraper get blocked when Chrome works?
Most often one of four things: a TLS / HTTP-2 fingerprint that identifies a raw HTTP client, missing Sec-CH-UA-* client hints, a missing Accept-Language header, or a cookie-binding failure where a clearance cookie is never replayed. The analyzer flags all four directly on your trace.
How big a HAR can it handle?
The analyzer reads the file in your browser and only renders the rows near the viewport, so large multi-thousand-entry traces stay responsive. Very large files (50MB+) just take a moment to parse.
Integrations
n8n
Automate workflows visually. Streamline data collection processes.
n8n Template
Pre-built template for modern websites. Simplifies Scrappey integration.
RapidAPI
Access via API marketplace. Easy integration with comprehensive docs.
Apify
Scalable actor-based automation. Reliable browser rendering.
MCP Server
AI-powered browser automation. Intelligent session management.
Scrappey CLI
Scrape from your terminal. One command, pipeable output, CI-ready.
Claude Code Skill
Portable skill for Claude Code + Codex. Browser-backed data access on demand.
LangChain
LangChain connector — clean web data for any chain or agent.
LlamaIndex
LlamaIndex reader — load modern web pages straight into RAG.
Zapier
Connect with 7,000+ apps. Automate workflows easily.
Make
Visual workflow automation. Connect with 1,000+ apps easily.
Start building with Scrappey
Try it free. No subscription, no credit card, instant setup — your trial is waiting.