Tools

ScrapeConvert: Free Tool to Extract & Convert Website Images

Use ScrapeConvert to collect images from public websites and convert a batch for a migration. Learn what runs locally, what uses a server relay, and what to check before reusing an image.

4 min read

Updated October 9, 2026.

When rebuilding a website, collecting and preparing its images can take longer than expected. ScrapeConvert brings discovery, selection, conversion, and download into one workflow. We built it for this kind of website work and made it open source.

Start with images you own or have permission to reuse. Finding an image on a public page does not establish permission to publish it in a new site or send it to another service.

Choose the right starting point

You can start with a page URL, several URLs, or a sitemap. A sitemap gives the tool a list to work through; it does not prove that every page or image on the site is included. Check the results against the content you actually need to migrate.

If you already have the original files, use local conversion instead. That avoids scraping and gives you a better starting point than downloading an already compressed website copy.

Review before converting

The current ScrapeConvert project documentation describes image discovery, duplicate flags, resizing, and batch conversion to WebP, AVIF, PNG, or JPEG. The tool lists what it finds so you can choose the images worth carrying forward.

A practical migration workflow is:

  1. Try one representative page before starting a larger crawl.
  2. Check that important project photos, logos, and other assets appear in the results.
  3. Review duplicate flags rather than deleting every apparent repeat: you may need different crops or versions.
  4. Select a small test batch and choose an output format and size.
  5. Inspect the converted files, then process the remaining selection and organize the download for the new site.

Keep original files separately. A converter cannot restore detail that was already lost in a small or heavily compressed source image.

Check the output, not just the file size

A smaller file is useful only if it still works for the intended placement. Look at fine text, edges, faces, transparency, and brand colors at the size the image will appear. Compare actual outputs rather than assuming that one format always wins.

Google’s WebP documentation distinguishes lossy and lossless compression and explains format support. Its comparison results are not a promise that every image will shrink by the same percentage. Image changes alone also do not establish that a page will pass a performance assessment or generate more inquiries.

For a project gallery, try a representative photo first. For a logo, check transparency and edge quality. If you need a particular file type for another system, verify that requirement before converting the whole batch.

Local conversion and website scraping handle data differently

Conversion happens in your browser. Scraping uses a server relay to retrieve remote pages, sitemaps, and selected image bytes. That distinction is documented in the project’s architecture overview: local conversion is not evidence that remote scraping never reaches a server.

The site also discloses analytics. We should not describe it as “zero tracking” or “no data collected.” Consult the current privacy information before choosing it for sensitive work; this article does not guarantee the absence of infrastructure logs. Avoid entering private URLs, access tokens, or confidential client material into a public scraping workflow.

What can limit a crawl?

ScrapeConvert is free to use, but that does not mean every request will succeed. The tool’s FAQ describes rate limits, blocked destinations, and sites that refuse automated requests. A large crawl may need to be reduced or retried. Pages that load images dynamically may also need a manual check against the original site.

If a needed image is missing, ask the site owner for the original asset instead of assuming the crawl is complete. If you are preparing a client mockup, confirm the intended use before passing images or their URLs to an external AI tool.

Put the images to work

Download a small sample and confirm the filenames, dimensions, and quality before replacing existing assets. Keep a record of which image belongs on which page, along with any credit or license requirements. That makes the eventual website handoff easier to maintain.

Open ScrapeConvert to choose the current scraper or converter. The source repository is available if you want to inspect how it works.

Need Help With Your Website?

We can help plan an image migration and prepare your content for a new website.

Get in Touch