Magento 2 and Adobe Commerce storefronts built on the Luma theme, or themes derived from it, write a lot of product data into the page for their own scripts: each price as a plain number, the old price beside it on a sale, the SKU as an attribute, and the whole gallery as a list of images. Web Product Scraper reads that data instead of guessing from what is displayed, then gives you one row per product in Excel, CSV or JSON, and the photos in a folder per product.
Add to Chrome, it's free No account · private by default
Open a category or search results page of the Magento store in Chrome, click the Web Product Scraper icon, set how many pages to read and press the Scrape button. With Full: open each product page chosen, each row gets the SKU, brand, description, category and full gallery from the product page. Then download Excel, CSV or JSON, open it in Google Sheets, or download a ZIP of the photos.
Luma-style themes keep each value in a known place.
The price box carries every amount as a machine-readable number for the theme's scripts. With Full, the default on Magento categories, prices come from the numbers in each product page's price box, so currency symbols, thousands separators and "As low as" labels never get in the way.
On a sale the box holds a final price and an old price. The final price is the price; the old price becomes the MRP column, only when it is higher.
The SKU from the product's SKU attribute, and the brand, when the theme shows it as its own block or in schema markup.
The short overview beside the price when there is one, else the text of the Details tab.
The last category in the breadcrumb trail above the product, when the page carries a breadcrumb.
Category and catalog search pages in grid or list mode, numbered ?p=2, ?p=3 with a next arrow. A run follows them up to the page you set.
A Magento product page does not load its gallery from the images you see. It carries a block of configuration for the gallery script, listing every image with three addresses: a thumbnail, the image shown on the page, and the full version used for zoom. Web Product Scraper reads that list and takes the full version of each image, in the store's order, including the ones you would only see by clicking through the slides: up to 20 photos, without those that belong only to a colour swatch.
When a page has no such list, the reader falls back to the images in the product media area. Either way, each product's photos land in a folder named after it in the ZIP.
Not every Magento 2 store looks like Luma underneath. Themes that replace the front end, such as Hyvä, and headless storefronts built with PWA Studio or a separate framework, can drop the gallery configuration or lay out the price box differently.
On Hyvä the Magento reader keeps what it finds and the general reader fills the rest; PWA Studio front ends are read by the general reader, from the structured product data most storefronts publish. On either, "Teach this site" fixes any field that comes out wrong: press Pick next to it, click the right value on the page once, and save the rule for that store.
When a store shows both, the price with tax is likely the one taken.
Each product keeps up to 20 photos; photos that belong only to a colour swatch are skipped.
A brand that appears only in the More Information table is not read.
One row per configurable product, with the parent SKU and the price of the option the page preselects.
The page range is the current page only (choose All pages for the rest); a Scrape stops after 100 products.
In the admin, System, Data Transfer, Export, with entity type Products, writes every product to a CSV that Magento can import again; the file appears in the export list once the store's cron has run. Its image columns (base_image, small_image, thumbnail_image, additional_images) hold paths under pub/media/catalog/product, not the pictures: copy that folder from the server over SFTP or the host's file manager to have the files.
Export the CSV from System, Data Transfer, Export as above, then in Google Sheets choose File, Import, Upload and pick the file: every product opens as a row. The CSV is a snapshot; a sheet that updates by itself needs a sync service or a Magento extension, which are usually paid.
Without admin access, the storefront is what you have. The extension reads the pages you open in your own browser, with no module installed on the store.
The spreadsheet here has one row per product with readable columns. Map them when you import into Magento or anywhere else.
Real exports the extension made from its own sample shop: 12 made-up products, two pages, read in Full. They show what the files hold; they were not made from a Magento store.
From your own Magento 2 admin: System, Data Transfer, Export, entity type Products, file format CSV, then open the CSV in Excel. From a store you do not run, open a category page with Web Product Scraper and download an .xlsx directly: one row per product, special and regular price apart, prices as numbers.
No. A configurable product is one row, with the price its page shows before a size or colour is chosen. Its child products are not listed one by one.
Yes, both are Magento 2 underneath. Magento 1, which reached its end of life in 2020, goes through the general reader instead.
Yes, two ways. From your own store: export the CSV in System, Data Transfer, Export, then in Google Sheets use File, Import, Upload. From any Magento store's pages: after a run, press Open in Google Sheets in step 4, and the extension copies the table and opens a new Google Sheet to paste it into.
In your own store's admin, System, Data Transfer, Export with the entity type Products gives a CSV, but the image columns hold file paths inside the store's media folder, not the pictures. From a store's public pages, Web Product Scraper exports the products to Excel or CSV and the photos as files, a folder per product.
