Magic Scraper.app VS Diffbot

Magic Scraper.app's answer

Chrome Manifest V3, with a service worker background script and chrome.scripting for in-page extraction. Plain JavaScript, CSS and HTML — no framework, no bundler, no build step and no third-party runtime dependencies. The whole extension is six files and every line that runs ships inside the package; nothing is fetched or evaluated at runtime.

It installs with activeTab, scripting and downloads only. Broader access is requested at the moment a feature needs it, and declining leaves the rest working.

Magic Scraper.app's answer

Most scrapers stop at the list. Magic Scraper opens the page behind every row, takes the fields that only exist there, and merges them back into the table as extra columns — chained as many levels deep as the data requires. A product catalogue gives you name and price; the SKU, material and lead time live on each product's own page, and that is the gap it closes.

The second thing is where the data goes: nowhere. There is no server, no account and no telemetry. The free version makes no network requests at all. Everything is detected, collected and exported inside the browser you are already using.

Magic Scraper.app's answer

Often they shouldn't. If the data you want is already visible in the list, several free tools will get it, and there is no reason to pay anyone for that.

Choose this one when you find yourself scraping a list and then opening every row by hand to collect the fields that only exist on the detail page. That specific job is what it was built for, and it is the one thing the alternatives do not describe doing.

The other reason is architectural rather than featural: competing tools commonly route your scrape through their servers, which means an account, a quota, and your data on someone else's machine. This one has no servers to route anything through.

Magic Scraper.app's answer

People who live in spreadsheets and do not want to write code: analysts, researchers, procurement and e-commerce teams comparing suppliers or competitor catalogues, recruiters and journalists building lists, and anyone whose job involves getting a web table into Excel before they can start the actual work.

Developers use it too, but for a different reason — it answers in thirty seconds the question that would otherwise cost an afternoon of writing and maintaining a one-off script.

Magic Scraper.app's answer

It started with a catalogue that showed only name and price, where everything that mattered — SKU, material, lead time, the maker — sat one click away on each product's own page. The existing tools all collected the list perfectly and then stopped, which left 200 tabs to open by hand.

Drill-down was built for exactly that, and the rest followed from making it usable on real sites: pages that paginate awkwardly, values that sit outside the table, columns that need renaming because the markup names them Text 2. The privacy stance was not a marketing decision either — once everything runs in the browser, there is nothing a server would be for.