Webpage Image Extractor

Inventory image references from public web pages or a bounded same-domain crawl. Export source-page context, normalized asset URLs, discovery type, available alt text and declared dimensions, with optional status checks and supported raster-file downloads. This is an image-reference inventory rather than a screenshot service, browser-rendering guarantee or grant of image reuse rights.

Quick start

Begin with one known page, same-domain crawling off and downloads off, then inspect URLs and metadata before increasing caps. The existing Wikipedia example is:

{
  "startUrls": [
    { "url": "https://www.wikipedia.org/" }
  ],
  "maxPages": 3,
  "maxImages": 50,
  "crawlSameDomain": false,
  "includeSrcset": true,
  "includeCssBackgrounds": false,
  "checkImageStatus": true,
  "downloadImages": false,
  "connection": "direct"
}

Prefer a video guide? This short Apify walkthrough shows you how to set up and run an Actor. It uses a different Actor, but the setup steps are the same.

What you get

A saved image-reference row with pageUrl, the raw and absolute image URLs, discovery context and available attributes. Optional response checks can add status, MIME type and byte size. A downloadedKey appears only when a supported file was actually saved. Missing response metadata is not a successful download confirmation.

Who is it for?

• SEO and accessibility reviewers inspecting image references and missing alternative text.
• Catalog researchers checking public product-page asset metadata.
• Content migration teams inventorying source URLs before a CMS or design change.
• Asset-data developers retaining source-linked URL lists for separate rights and quality review.

How you can use the data

• Inspect a Wikipedia page's image context. Use the existing page with a small page and image cap, keeping pageUrl, absoluteImageUrl, alt and sourceType. Missing alt text identifies a review candidate rather than proving every rendered image lacks accessible context.
• Review response metadata deliberately. Enable status checks and retain statusCode, mimeType and bytes when available. A failed metadata request leaves uncertainty, while a successful response does not prove visual quality or permission to reuse the image.
• Prepare a bounded site migration inventory. Enable same-domain crawling for your selected public site, keeping small page and image caps and source-page links. Responsive candidates and optional CSS backgrounds can add alternate sizes, icons or tracking assets, not just unique content photographs.
• Save permitted raster assets selectively. Enable downloads only when you need the files and have reuse rights, then inspect downloadedKey rather than assuming every discovered URL became a stored file. Unsupported types, over-limit files and failed downloads can leave metadata rows without files.

Input settings

Setting	Type	Default	Description
startUrls	array	required	Public webpage URLs or direct image URLs to inspect.
maxPages	integer	3	Maximum pages to fetch across all start URLs.
maxImages	integer	200	Maximum image records to save.
crawlSameDomain	boolean	false	Follow same-domain links until maxPages is reached.
includeSrcset	boolean	true	Include responsive image candidates from srcset.
includeCssBackgrounds	boolean	false	Include URLs from inline CSS and page style blocks.
checkImageStatus	boolean	true	Collect image status code, MIME type, and size when available.
downloadImages	boolean	false	Save supported raster image files of at most 15 MB to the run key-value store.
connection	string	direct	Direct access or the existing managed proxy strategy. See input help for costs and precedence.
proxyConfiguration	object	omitted	Optional existing/custom settings that override Connection.

Input options

Quick image inventory

Use one URL, keep crawlSameDomain off, and leave downloadImages off. This is best for a fast list of image URLs and metadata.

Small website audit

Set crawlSameDomain to true, maxPages to 10-25, and maxImages to a reasonable cap. This checks several pages on the same domain without crawling the entire site.

Build a downloadable image set

Enable downloadImages only when you really need the files. Downloaded files are stored in the run key-value store and referenced by downloadedKey in the dataset.

Output data

The existing illustrative row shows shape rather than a new page or file request:

{
  "pageUrl": "https://www.wikipedia.org/",
  "imageUrl": "portal/wikipedia.org/assets/img/Wikipedia-logo-v2.png",
  "absoluteImageUrl": "https://www.wikipedia.org/portal/wikipedia.org/assets/img/Wikipedia-logo-v2.png",
  "sourceType": "img",
  "alt": "Wikipedia",
  "title": null,
  "width": 200,
  "height": 183,
  "mimeType": "image/png",
  "fileExtension": "png",
  "bytes": 16384,
  "statusCode": 200,
  "discoveredAt": "2026-07-08T09:30:00.000Z"
}

The actor saves one dataset row per discovered image URL.

Field	Description
pageUrl	Public page where the image URL was discovered.
imageUrl	Raw image URL as it appeared in the page.
absoluteImageUrl	Normalized absolute image URL.
sourceType	Discovery source: img, srcset, meta, or css.
alt	Image alt text when present.
title	Image title attribute when present.
width / height	HTML-declared image dimensions when present.
mimeType	MIME type from the image response when checked.
fileExtension	File extension parsed from the image URL.
bytes	File size in bytes when the server provides it or downloads are enabled.
statusCode	Image URL HTTP status code when checked.
downloadedKey	Key-value-store key when downloadImages saves the file.
discoveredAt	Timestamp when the image record was produced.

Download your results

Open your run's dataset, choose Export and select JSON, CSV or Excel. JSON keeps nested fields together. CSV and Excel are useful when you want to review the records in a spreadsheet.

See Apify's download and export guide for the available formats and field options.

Pricing

A run has a start event after validation, and each saved image-reference row creates an item event. A metadata row can still be saved when a status check or file download is unavailable, so the paid row does not guarantee a stored image file. Empty fetched pages do not create image-record charges, while the run can retain its start charge.

Keep page and image caps small and enable downloads only when needed. Platform storage, transfer and optional proxy usage can also apply. See the live Pricing tab for current rates and tiers.

Tips for best results

• Start with a metadata inventory. Keep downloads and same-domain crawling off for a first page review.
• Retain source-page links. The same asset can appear in several contexts, so keep evidence before making accessibility or migration decisions.
• Choose responsive and CSS discovery deliberately. Alternate resolutions, icons and tracking assets can be relevant or unwanted for your workflow.
• Inspect null response values. Status, MIME and size information is available only when the relevant request succeeds.
• Confirm downloadedKey before using a file. A saved reference does not mean a file was downloaded.
• Respect caps and rights. A bounded crawl is not a complete site mirror or permission to reuse assets.

Limits and caveats

• Only scan public pages that you are allowed to access.
• The actor does not bypass login walls, CAPTCHA, paywalls, or private content.
• Some websites block automated requests. Use proxies only when needed and allowed.
• Download mode saves only supported raster-image MIME types. It rejects non-image responses and skips files whose declared or streamed size exceeds 15 MB.
• Requests are limited to public HTTP(S) destinations. Private, loopback, link-local, credentialed, and unsafe redirect destinations are rejected.
• A successfully fetched HTML page with no image candidates succeeds with an empty dataset. Unavailable or access-denied targets also succeed empty with truthful per-target reasons. Inaccessibility alone does not establish privacy or deletion. Systemic request failures still fail the run.
• CSS extraction is optional because CSS can contain icons, tracking pixels, and other assets you may not need.

Width and height are HTML-declared values rather than an independent inspection of each image's pixel dimensions. The source reads public HTML rather than executing page JavaScript, so client-rendered or lazily inserted assets can be missed. Discovery sources include img, srcset, metadata and optionally inline or embedded CSS.

Image response checks and downloads are optional enrichment. A failed check, unsupported file or failed optional file-store write can leave the reference row available without complete response metadata or downloadedKey. The dataset does not certify that a URL is currently usable or safe to republish.

Existing matching same-run PENDING_WORK can restore queued pages and saved-image identities after a platform restart. It is not a new-run continuation input, and a new run has its normal start charge and can save the same references again. Processing is bounded to five minutes from the original run start, even if a longer platform timeout is selected. A charge limit can stop collection before the requested caps. Previously saved rows remain useful when an isolated target is unavailable. Deadline recovery and RUN_SUMMARY persistence are best effort.

Use this actor only on public pages you are allowed to access and process. It does not bypass authentication, CAPTCHA, paywalls, robots restrictions, or private content. Review the target website's terms and applicable privacy, copyright, and data-protection rules before downloading or reusing image files.

Automation and integrations

Save your settings for next time

Once you have an input that works for you, save it as an Apify task. This keeps your settings together so you can use them again without filling in the form from scratch.

Run on a schedule

Need fresh results regularly? You can schedule the Actor or a saved task to run at a time that suits you.

Each scheduled run collects the data again. If you want to compare results or highlight changes, add that step in your own workflow.

Send results to your other tools

Use n8n, Make or Zapier to connect this scraper to the rest of your workflow. For example, you could pass its results to an AI assistant or add records to a spreadsheet. Follow the Apify integration guides for your chosen tool.

For a custom connection, an Apify webhook can notify your app when a run finishes or fails. Your app can then fetch the results or handle the failure.

API usage

Want to collect this data from your own app or automation? The examples below send input to the scraper and show how to collect its results.

The Node.js and Python examples wait for the run to finish before reading its results. The cURL example starts the run and returns its details. Wait for that run to finish, then use its defaultDatasetId to fetch the results.

For setup instructions, see Apify's JavaScript client guide, Python client guide and Actor runs API reference.

cURL

curl -X POST 'https://api.apify.com/v2/acts/fetch_cat~webpage-image-extractor/runs?token=APIFY_TOKEN' \
  -H 'Content-Type: application/json' \
  -d '{
    "startUrls": [{ "url": "https://www.wikipedia.org/" }],
    "maxPages": 3,
    "maxImages": 50
  }'

Node.js

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('fetch_cat/webpage-image-extractor').call({
  startUrls: [{ url: 'https://www.wikipedia.org/' }],
  maxPages: 3,
  maxImages: 50,
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Python

from apify_client import ApifyClient
import os

client = ApifyClient(os.environ['APIFY_TOKEN'])
run = client.actor('fetch_cat/webpage-image-extractor').call(run_input={
    'startUrls': [{ 'url': 'https://www.wikipedia.org/' }],
    'maxPages': 3,
    'maxImages': 50,
})
items = client.dataset(run['defaultDatasetId']).list_items().items
print(items)

MCP and AI agents

You can ask your AI assistant to collect data with Webpage Image Extractor and help you work with the results. The scraper returns the data, and your assistant can then summarize it, compare records or prepare notes.

Connect your assistant through the Apify MCP server. MCP gives your assistant a way to find this scraper, run it and read the results. Follow the official setup and sign-in guide for your app.

Easier setup with an Apify plugin

If you use a supported coding assistant, the official Apify plugin can set up the connection for you. It connects your assistant to Apify and includes instructions for common tasks. Follow the guide for your particular app.

Use Apify AI in Console

Prefer to keep everything in Apify? Open Apify AI in Console and ask it to find Fetch Cat's Webpage Image Extractor. You can describe the data you want and ask questions about the results.

Apify AI is currently in beta. It asks for confirmation before starting an Actor, and normal run charges apply.

Choose your assistant

• Claude and Claude Code (Anthropic): Apify setup guide.
• ChatGPT and Codex (OpenAI): Apify setup guides.
• Grok Bot (xAI): Apify plugin guide.
• Gemini CLI (Google): MCP server setup guide. Use the server URL below with the HTTP configuration supported by Gemini CLI.

Connect just this scraper

To keep your setup focused on this scraper, add this server configuration to a compatible MCP client:

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=fetch_cat/webpage-image-extractor"
    }
  }
}

Sign in to Apify when your client asks. If your client uses a Bearer token instead, follow its setup guide and keep the token in its secure configuration. Configuration formats vary by app, so use the linked guide if your client needs a different format.

Use Apify's general server

Already connected to the general Apify MCP server at https://mcp.apify.com? You can use it to find this scraper without adding another server. Ask your assistant to use Webpage Image Extractor by Fetch Cat, or give it the identifier fetch_cat/webpage-image-extractor.

Your assistant can check the available settings and retrieve the results from the returned run. If the run is still working, it should follow that run rather than start it again. Both connection options use Apify's hosted service.

Example requests

• “Use Fetch Cat’s Webpage Image Extractor to collect up to 10 image references from https://www.wikipedia.org/ with one page, same-domain crawling off, status checks on and downloads off. Keep source URLs, alt text and uncertain metadata visible.”
• “Collect up to 10 image references from https://www.wikipedia.org/ with a one-page cap, responsive candidates on, CSS backgrounds on and downloads off. Keep discovery types rather than treating every asset as a unique content photograph.”
• “Retrieve up to 5 image-reference rows from https://www.wikipedia.org/ with one page and downloads off. Keep declared dimensions and source links without claiming image reuse rights or independently measured pixel size.”

Normal Apify charges apply. Check the live Pricing tab before asking your assistant to run a larger batch.

Pay with x402

If your AI agent has a funded wallet, it can pay for Apify usage through x402. This experimental option lets an agent use Apify without a conventional account.

Apify AGI provides a prepaid API token with a spending cap after payment. Your agent can use that token to run this scraper through the Apify API or an authenticated MCP connection.

Some MCP setups also support paying for each request directly. That is a different payment option, so check the official guide for its availability.

Follow the official guide for wallet setup, supported payment options and current terms. Apify handles the payments. Keep wallet keys and payment tokens in your agent's secure configuration.

Other ways for agents to pay

Apify also supports MPP for prepaid access through AGI and Skyfire for eligible Actors. If your agent already uses one of these, see the agentic payment guide to choose the right setup.

FAQ

Can it download the actual images?

Yes. Set downloadImages to true. The dataset will include downloadedKey for files saved to the run key-value store.

Can it crawl an entire website?

It can follow same-domain links up to maxPages, but it is designed for bounded audits, not unbounded site mirroring. Increase limits gradually.

Does it support JavaScript-rendered pages?

The first version focuses on public HTML pages. If a site only renders images after browser JavaScript execution, the actor may return fewer images.

Will it extract background images?

Yes, enable includeCssBackgrounds to extract url(...) references from inline styles and page style blocks.

Related Actors

• Sitemap URL Extractor for discovering pages to feed into image audits.
• Website Content Crawler Lite for text/content extraction from public pages.
• Website Screenshot Generator — Capture browser-rendered screenshots or PDFs of public web pages.
• Web Page to Markdown Extractor — Convert public web pages into Markdown, readable text and available page metadata.
• Bulk URL Status Checker — Check public URL status codes, redirects and available response metadata.

Support and feedback

For custom additions or integrations, email hello@fetchcat.dev.

Found an error or have a feature request? Open an issue with the run URL, a non-sensitive input example and what you expected.

Need help sharing it? See Apify’s guide to sharing a run when reporting an issue. Sharing a run can give the developer access to its input, logs and results, so use a run that contains no sensitive data. Please leave out API tokens, passwords, cookies, private documents and personal data. Use a public sample URL or a redacted example instead.

Tried this scraper? We'd love to hear how it worked for you. Leave a review to help others choose the right tool and help us improve it. Your feedback means a lot to us.

Made with care for curious people, AI agents and the possibilities in data. ♥