Any Website Data Scraper PRO plus – No Limits – Data Excavator is a Windows desktop application built in C# (.NET) that crawls pages and extracts structured data from them using CSS and XPath selectors, then exports the results to XLSX, CSV, JSON or MySQL. It bundles a Chromium Embedded Framework browser so it can reach content that only appears after JavaScript runs or behind a login, and it runs separate thread pools per project for scanning and parsing. It is aimed at developers, data analysts and agencies who want a self-hosted scraping engine rather than a hosted API or a browser extension.
The product sells on ThemeForest for $199 and is authored by a developer trading under the Data Excavator name. The listing does not disclose a sales figure, so there is no purchase history to weigh up — buyers are effectively assessing an unproven listing on the strength of its stated architecture.
What Any Website Data Scraper PRO plus actually does well
The core of the tool is a three-part pipeline: a crawler that walks a site, a grabber that parses the pages it retrieves, and an input/output layer that writes results out. Splitting those responsibilities matters because crawling and parsing have different bottlenecks, and the vendor states that each project gets its own thread pool for scanning and a second pool for parsing. In practice that means a slow, image-heavy site does not stall the parsing queue, and several projects can run against different domains at once without competing for the same workers.
Selector-based extraction is the second pillar. Because the tool accepts both CSS selectors and XPath expressions, it covers the two conventions most people already know from browser dev tools and from libraries such as Scrapy or BeautifulSoup. XPath is the more expressive of the two and is the difference between scraping a clean product grid and scraping a table where the column position shifts between pages.
The embedded Chromium browser is the feature that widens the addressable set of targets considerably. A large share of modern sites render prices, stock levels and reviews client-side, so a plain HTTP fetcher returns an empty shell. Running a real browser engine means the tool sees the same DOM a person would, and the vendor explicitly claims support for sites that require authorisation and for interaction driven by JavaScript.
Export formats and binary handling
Results can be written to XLSX, XLS, CSV, JSON or pushed into MySQL. That spread covers the three common downstream destinations: a spreadsheet for a non-technical stakeholder, JSON for an application, and a database table for ongoing analysis. The vendor also states that images and other binary payloads are saved to disk alongside the export and referenced through an images column or the equivalent JSON property, including images delivered as data:blob URIs. For catalogue work — product photography, supplier listings — that saves a second pass with a separate downloader.
Ready-made configurations and source access
The listing mentions a pre-built configuration for AliExpress, which suggests the vendor intends to ship starting points rather than leaving every project blank. It also states that the C# source is commented, which is relevant if the intent is to extend the engine or embed it in a larger internal system rather than use the GUI as-is.
Where Any Website Data Scraper PRO plus fits, and where it does not
The clearest fit is competitive price monitoring. A retailer or agency tracking SKUs across marketplaces needs repeatable extraction at volume, a database sink, and the ability to re-run the same project on a schedule. The MySQL export and per-project thread pools map directly onto that workflow.
Supplier and catalogue consolidation is the second strong case. Importing a few thousand products from a distributor’s site, with images, into a spreadsheet or store back end is exactly the shape of task the export layer was designed for. Data teams preparing a training or analysis set fall into the same bracket, since JSON output drops straight into most pipelines.
It is the wrong choice for anyone who needs scraping to run unattended on a Linux server or inside a CI job. The application is a .NET Framework desktop program with an embedded browser; the vendor describes hardware dependence in terms of the operator’s own machine, and nothing in the listing suggests a headless deployment mode or a hosted API. Teams that need scheduled cloud execution, managed proxies or automatic anti-bot handling should be looking at a hosted scraping service instead. It is also a poor fit for someone who wants to extract a single page once — the setup cost of defining selectors and a project is not repaid at that scale.
Strengths and limitations of the Data Excavator engine
Strengths
- Genuine parallelism: separate thread pools for crawling and parsing, configurable per project, with multiple projects able to run concurrently against different sites.
- Chromium rendering built in, so JavaScript-driven content and logged-in areas are reachable without bolting on a separate headless browser.
- Both CSS and XPath selectors supported, which covers simple and awkward page structures alike.
- Five export targets including a direct MySQL write, plus automatic image capture with references preserved in the output.
- Commented C# source, which makes the tool extendable rather than a closed box.
- One-off licence cost with no per-request or per-row billing, unlike most hosted scraping APIs.
Limitations
- Windows and .NET Framework only. There is no stated Linux or macOS build, and no documented headless or server-deployment path.
- The vendor’s throughput claims — hundreds or thousands of requests per second — are tied to unspecified “good hardware” and are not backed by any published benchmark. Treat them as a ceiling under ideal conditions, not an expectation.
- No disclosed sales history on the marketplace listing, so there is no independent track record of updates or support responsiveness to rely on.
- Selector-based extraction is brittle by nature. When a target site changes its markup, projects break and need re-tuning; the listing does not describe any auto-repair or change-detection mechanism.
- Nothing in the listing addresses proxy rotation, CAPTCHA handling or rate-limit management, which are the practical failure points on large commercial targets.
- It is a desktop GUI tool first. Teams wanting a library to call from their own code will be working around the application rather than with it.
How it compares with the wider scraping category
Buyers researching this space usually weigh three options: browser extensions and no-code point-and-click scrapers, hosted scraping APIs, and scriptable frameworks. Extensions are cheap and immediate but typically operate one page at a time and cannot sustain volume — the vendor’s own comparison makes this point, and it is a fair one. Hosted APIs remove infrastructure concerns and handle blocking, but charge per request or per record and keep the data pipeline on someone else’s servers.
Any Website Data Scraper PRO plus miscellaneous sits between those poles. It offers more throughput and structure than a plugin, and more control and lower marginal cost than a hosted service, at the price of running everything locally and owning the maintenance. Against scriptable frameworks it trades flexibility for a GUI, built-in scheduling of projects, and export plumbing that would otherwise be assembled by hand. The trade is reasonable for a small team without a dedicated engineer; it is a harder sell for a engineering-led team already comfortable with code.
Frequently Asked Questions
Does this scraper work on sites that load content with JavaScript?
Yes. The application embeds the Chromium Embedded Framework, so pages are rendered in a real browser engine before extraction and content injected by JavaScript is present in the DOM. The vendor also states that sites requiring authorisation are supported. That makes it viable on modern storefronts and dashboards where a plain HTTP request would return an empty template.
What export formats does Data Excavator support?
It writes to XLSX, XLS, CSV, JSON and MySQL. Images and other binary files are saved to disk next to the export and linked through an images column in tabular formats or the matching JSON property. The vendor notes that data:blob encoded images are handled correctly, so media does not need a separate download step.
Can it run on a server or in the cloud?
Not as described. The product is a Windows desktop application built on .NET Framework with an embedded browser, and the vendor frames performance in terms of the operator’s own machine or a powerful server PC. No headless mode, Linux build or hosted API is mentioned in the listing. Unattended cloud execution is therefore not a documented capability.
Is a single $199 licence enough for large scraping jobs?
The licence is a one-off purchase with no per-request charges, so volume does not increase cost. The real constraint is local: throughput depends on the machine’s cores and network, and the vendor’s highest figures assume strong hardware. Large jobs are limited by infrastructure and by how well the target site tolerates the request rate.
Verdict on Any Website Data Scraper PRO plus miscellaneous
This is a credible buy for a Windows-based freelancer, agency or data analyst who needs repeatable extraction from JavaScript-heavy or login-protected sites, wants results in a spreadsheet or MySQL, and prefers a one-off licence to a metered API. The combination of dual thread pools, an embedded Chromium engine and five export targets is a coherent package at $199. It is not the right purchase for teams needing headless Linux deployment, managed proxy and CAPTCHA handling, or a library to embed in existing code — and the absence of any published sales or support history means the first cohort of buyers is taking a measured risk on an unproven listing.
