

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.
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.
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.
| 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. |
"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.
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.
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.
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.
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.
Automate workflows visually. Streamline data collection processes.
Pre-built template for modern websites. Simplifies Scrappey integration.
Access via API marketplace. Easy integration with comprehensive docs.
Scalable actor-based automation. Reliable browser rendering.
AI-powered browser automation. Intelligent session management.
Scrape from your terminal. One command, pipeable output, CI-ready.
Portable skill for Claude Code + Codex. Browser-backed data access on demand.
LangChain connector — clean web data for any chain or agent.

LlamaIndex reader — load modern web pages straight into RAG.
Connect with 7,000+ apps. Automate workflows easily.
Visual workflow automation. Connect with 1,000+ apps easily.
Try It For Free. No Subscription Required. No Credit Card Required. Instant Set-Up. 150 Free Requests Are Waiting For You!
Scrappey.com is a web scraping API that handles all the complex aspects of web scraping, such as handling dynamic content, rotating proxies, advanced request handling, headless browsers, and verification processing. It offers an all-in-one solution for extracting publicly available data from websites.
Scrappey.com provides a web scraping API that allows you to send requests to extract publicly available data from websites. It handles dynamic content and modern website complexity, including rotating proxies, advanced request handling, and verification processing. You can easily extract publicly available data from websites using their built-in features like headless browsers and AI-powered data extraction.
Yes, with Scrappey.com, you have the option to use Sticky Rotating Proxies for seamless scraping. Alternatively, you can also set your own proxies if desired.
Yes, Scrappey.com offers a free trial where you can try it out without a subscription or credit card. Instant setup is provided, and you get 150 free scrapes to explore the capabilities of the platform.
We only charge for successful requests. Failed requests are not counted towards your usage, so you only pay for what works.
No problem, you can pass any JavaScript snippet that needs to be executed by using our JavaScript scenario parameter. This allows you to interact with dynamic content, scroll pages, click buttons, wait for elements, and perform any custom JavaScript actions before extracting the data.
Scrappey.com offers simple and transparent pricing: €0.20 per 1,000 direct HTTP requests and €1.00 per 1,000 full-browser requests. Residential proxies are included on both tiers — no separate proxy billing, no hidden fees, no complicated pricing tiers. You only pay for successful requests.
Scrappey.com provides scalable access for extracting publicly available data. Whether you need to extract data from a few pages or a large dataset of publicly accessible content, you can do so with flexible usage options. Please note that Scrappey.com only supports scraping publicly available data, and users must comply with applicable laws and website terms of service.
Scrappey.com provides various support channels for assistance. You can refer to their documentation, frequently asked questions section, blog, and uptime status page. Additionally, you can get in touch with them via email or join their Discord community for further support.
We don't create custom scraping scripts, however we will gladly write some code snippets helping you to use our most powerful features: AI-powered data extraction and JavaScript scenario. Our documentation includes examples in multiple programming languages to get you started quickly.
Each API call to Scrappey counts as one request. Our pricing is based on successful requests. By default, JavaScript rendering is enabled, which allows you to extract data from modern websites with dynamic content. All features including proxies, CAPTCHA solving, and advanced web access handling are included in each request.
Scrappey's API is optimized for fast response time, even when dealing with complex or protected websites. If other scrapers struggle with sites that have advanced security measures, Scrappey is designed to handle these challenges efficiently, ensuring reliable data retrieval. Our advanced web access handling, residential proxies, and intelligent retry logic work together to maximize success rates.