Bulk File and Image Downloader: Download Images from Website
Pricing
from $1.40 / 1,000 file downloadeds
Bulk File and Image Downloader: Download Images from Website
Download files in bulk from direct links, or every image, video, audio file, PDF, document or archive on a list of web pages. Each file is stored with a link you can open, plus its name, type, size, SHA-256 checksum, image width, height and alt text. Duplicates are found and not charged.
Pricing
from $1.40 / 1,000 file downloadeds
Rating
0.0
(0)
Developer
vøiddo
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
a day ago
Last modified
Categories
Share
Download files in bulk from direct links, or every image, video, audio file, PDF, document or archive on a list of web pages. Each file is stored with a link you can open, plus its name, type, size, SHA-256 checksum, image width, height and alt text. Duplicates are found and not charged.
- Pay per file stored (the price is on the Pricing tab): files up to 10 MB count once, and the platform usage of the run is included. Failed links, skipped files and duplicates cost nothing.
- No login, no cookies, no account on the site: public files and web pages only.
- Export to JSON, CSV, Excel, XML or HTML, or read the rows through the Apify API.
- Start it from the Console, on a schedule, through the API, or as a tool for agents over MCP.
- Tested every day on its example input, with the rows checked, and repaired when a check fails.
What you can use it for
- Product images: every photo of a list of product pages in the largest size offered, with alt text and size.
- Document collection: the PDF, Word, Excel and CSV files linked from report, tender or dataset pages.
- Site migration and backup: the images, video and files of the pages you move, with a checksum for each.
- Image datasets: pictures with their alt text, width and height, ready to label, train or index.
- Broken media checks: every image and file a page uses that answers with an error, listed with the reason.
What you get
Every result is one row in the run's dataset. Download it as JSON, CSV, Excel or HTML, or read it through the Apify API. The main fields:
| Field | Meaning |
|---|---|
fileUrl | File |
fileName | Name |
fileType | Type |
fileBytes | Bytes |
imageWidth | Width |
imageHeight | Height |
altText | Alt text |
url | Source link |
error | Error |
Example row:
{"kind": "file","url": "https://thumb.wikimedia.org/wikipedia/commons/thumb/b/b6/Allen%27s_Hummingbird_Nest_%288563916462%29.jpg/330px-Allen%27s_Hummingbird_Nest_%288563916462%29.jpg","pageUrl": "https://en.wikipedia.org/wiki/Hummingbird","finalUrl": "https://thumb.wikimedia.org/wikipedia/commons/thumb/b/b6/Allen%27s_Hummingbird_Nest_%288563916462%29.jpg/330px-Allen%27s_Hummingbird_Nest_%288563916462%29.jpg","foundIn": "img srcset","fileName": "Allen's_Hummingbird_Nest_(8563916462).jpg","fileType": "image","contentType": "image/jpeg","fileBytes": 40850,"sha256": "75c9387c0cd37a20c116ef7702a2bc0cc4c4a2705368a34c8f5f2b80a5867679","imageWidth": 330,"imageHeight": 330,"altText": "Each approximately the size of a pea, two eggs in the nest of an Allen's hummingbird","fileUrl": "https://api.apify.com/v2/key-value-stores/aBcDeFgHiJkLmNoPq/records/000009-Allen's_Hummingbird_Nest_(8563916462).jpg?signature=1a2b3c4d5e","duplicateOf": null,"chargeUnits": 1,"error": null,"downloadedAt": "2026-10-23T16:39:41Z"}
How to use it
- Open the Input tab (or call the actor through the API, see below).
- Fill in Pages, File types, Maximum files per page; the form opens with a working example.
- Set Maximum results to cap the size and the cost of the run.
- Click Start. Rows appear on the Output tab while the run works.
- Download the dataset, or connect it to Google Sheets, Make, Zapier, n8n or a webhook.
Input
| Field | Type | Required | Description |
|---|---|---|---|
fileUrls | array | no | Direct links to files of any type (images, video, audio, PDF, documents, archives). Each one is downloaded whatever its type. A link that turns out to be a web page comes back as a row that says so: put it under Pages instead. |
pageUrls | array | no | Web pages to download files from: the images it shows (the largest size it offers), its video and audio, and the files it links to, filtered by File types. Pages are read as HTML without a browser, so files a page loads with JavaScript only are not found. |
fileTypes | select | no | Which files to take from Pages. Direct file links are always downloaded. Allowed: image, video, audio, pdf, document, archive. |
sameSiteOnly | boolean | no | Take only files on the host of the page or its subdomains, leaving out files on other hosts (many sites keep their images on a separate CDN host, so this can drop them). Default: false. |
maxFilesPerPage | integer | no | Caps the files taken from one page, in the order they appear on it. Default: 200. |
minImageKB | integer | no | Images found on pages that are smaller than this are left out (icons, spacers, tracking pixels) and not charged; 0 keeps every image. Direct links are always kept. Default: 5. |
maxFileMB | integer | no | Larger files come back as a row with the reason, at no charge. Above 100 MB give the run more memory: 1 GB for every 150 MB of this limit (a few files can be in memory at once). Default: 100. |
maxItems | integer | no | The run stops after this many result rows. It also caps what one run can cost. Default: 1000. |
proxyConfiguration | object | no | Leave as is: the run starts on the cheapest network the site accepts and switches to Apify Proxy automatically when the site blocks it. Pick proxy groups here only to force one specific network. |
Example input:
{"pageUrls": ["https://en.wikipedia.org/wiki/Hummingbird"],"fileTypes": ["image"],"maxFilesPerPage": 20,"maxItems": 20}
Pricing
You pay per file stored, at the price per file on the Pricing tab. A file up to 10 MB counts once; a larger one counts once more for every started 10 MB (a 25 MB video counts three times). Pages read, links that fail, files left out by your filters and duplicates cost nothing. Set Maximum files per page, Maximum file size and Maximum results to cap what a run can cost; the run also stops at your spending limit.
Limits and notes
- One row per file: the stored copy (fileUrl), the link it came from, the page it was found on and where on the page (img, srcset, link, video, og:image ...), its name, type, content type, size, SHA-256 checksum, and for images the width, height and alt text.
- The files are records in the run's key-value store; fileUrl opens them directly and works in the dataset table, in spreadsheets and in your own code. They are kept as long as your Apify plan keeps the run's storage.
- Images on pages come in the largest size the page offers in srcset, and lazy loading attributes (data-src and the like) are read, so the real image is taken instead of a placeholder.
- The same file under two links is stored once: the second row has duplicateOf and costs nothing. A link that appears on several pages is downloaded once.
- Files are read only from addresses whose robots.txt allows it, and not from hosts that close their content to machine learning agents in robots.txt. Such a file comes back as a row with the reason, at no charge. Only download files you have the right to copy.
- Pages are read without a browser: files a page shows only after running JavaScript (most social networks, many shops) are not found. Links to their files can still be given under File links.
- Only publicly visible data is collected. No login, no paywalled content, no personal contact details.
- The actor reads only pages that the site's robots.txt leaves open to automated access.
- Sites change their pages from time to time. The actor is checked automatically and repaired when a check fails.
- Each run sends one short usage record to the developer: the Actor and run IDs, the number of results, whether the run succeeded (and if not, the kind of error, such as "blocked" or "input problem"), whether the account is on a paid Apify plan, how the run was started (for example from the Console, the API or a schedule) and a one-way fingerprint of the account (a hash, not the account ID), so that repeat runs of one account count once. It contains nothing from your input or results.
Run it through the API
Python, with the apify-client package:
from apify_client import ApifyClientclient = ApifyClient("<YOUR_APIFY_TOKEN>")run = client.actor("v0iddo/bulk-file-downloader").call(run_input={"pageUrls": ["https://en.wikipedia.org/wiki/Hummingbird"], "fileTypes": ["image"], "maxFilesPerPage": 20, "maxItems": 20})for item in client.dataset(run["defaultDatasetId"]).iterate_items():print(item)
JavaScript, with the apify-client package:
import { ApifyClient } from 'apify-client';const client = new ApifyClient({ token: '<YOUR_APIFY_TOKEN>' });const run = await client.actor('v0iddo/bulk-file-downloader').call({"pageUrls": ["https://en.wikipedia.org/wiki/Hummingbird"], "fileTypes": ["image"], "maxFilesPerPage": 20, "maxItems": 20});const { items } = await client.dataset(run.defaultDatasetId).listItems();console.log(items);
One HTTP call that waits for the run and returns the rows (for runs that finish within 5 minutes):
curl -X POST "https://api.apify.com/v2/acts/v0iddo~bulk-file-downloader/run-sync-get-dataset-items?token=<YOUR_APIFY_TOKEN>" \-H "Content-Type: application/json" \-d '{"pageUrls": ["https://en.wikipedia.org/wiki/Hummingbird"], "fileTypes": ["image"], "maxFilesPerPage": 20, "maxItems": 20}'
Use it from an agent (MCP)
Claude, Cursor, VS Code and other MCP clients can call this actor as a tool through the Apify MCP server. Add it to the client's MCP configuration:
{"mcpServers": {"apify": {"url": "https://mcp.apify.com?tools=v0iddo/bulk-file-downloader","headers": {"Authorization": "Bearer <YOUR_APIFY_TOKEN>"}}}}
Then ask, for example: "Download every product photo on these pages and give me the image links with their sizes."
FAQ
Do I need an account on the site, cookies or an API key?
No. The actor reads only what every visitor of the site can see, without logging in. You only need an Apify account to start it.
How many results can one run return?
Up to 50,000 rows per run. Without a limit it stops at 1,000. Set Maximum results to the number you need; large jobs can also be split into several runs or scheduled.
How am I charged?
Per file stored, at the price on the Pricing tab for your Apify plan; a file over 10 MB counts once more for each started 10 MB. The platform usage of the run is included, with no fee per page read. Failed links, skipped files and duplicates cost nothing, and when the run reaches your spending limit it stops after the last file you can pay for.
Why did my run return no results?
The status message of the run says why: nothing matched the input, the input was not a page the actor understands, the page is closed to automated access by robots.txt, or the site refused every network the actor tried. Check the input against the example above and run it again with a small limit.
Can I run it on a schedule?
Yes. Save your input as a task and add a schedule in the Apify Console (daily, hourly or with a cron expression). Each run gets its own dataset, so you keep a history.
Which formats can I export?
JSON, CSV, Excel, XML, HTML table and RSS from the Output tab or the API. Integrations send the rows to Google Sheets, Slack, Make, Zapier, n8n or a webhook.
Is collecting this data allowed?
The actor collects only what the site publishes to every visitor, without a login, and it reads only pages that robots.txt leaves open. Public data can still be personal data under laws such as the GDPR, and sites have their own terms: make sure your use of the data follows the rules that apply to you.
What happens when the site changes its pages?
Automated tests run the actor every day on the example input and check the rows, not only that the run finished. When a check fails, the actor is repaired and rebuilt; the build history on this page shows each update.
Something is missing or wrong. Where do I report it?
Open an issue on the Issues tab of this actor with the run link. Requests for a new field are welcome too.