How to Download and Prep Images in Bulk

Here’s a workflow I’ve watched people perform more times than I can count. Open a stock photo site. Search. Open the first promising result in a new tab. Then the next one. And the next. Twenty minutes later there are thirty tabs across the top of the browser, each one a single photo, and the actual downloading hasn’t started yet. Right-click, save image as, pick a folder, rename because the file arrived called pexels-photo-3184465.jpeg, repeat twenty-nine times.

Then you open the folder and discover every image is 5,000 pixels wide and 6MB, and none of them can go on a website in that state.

Bulk sourcing is really two problems wearing one coat. Getting the files is the visible half. Making them usable is the half that eats your afternoon. This guide covers both, plus the licensing question that sits awkwardly between them and that most people skip until it bites.

Where Bulk Image Work Actually Starts

Before getting into tools, it’s worth being precise about where a batch of images comes from, because the answer changes what you should do next.

Free stock libraries are the common case: Unsplash, Pexels, Pixabay and the rest. You need twelve images of “modern office workspace” for a blog series, or forty background textures for a design system. The images are free, high quality, and enormous.

Your own camera or phone is the second case. A shoot produces 200 frames, or a site visit produces 60 phone photos that arrive as HEIC and need to become something the web understands. Different problem — no licensing question, but a format conversion one. Our HEIC to JPG guide covers that specific pain.

A client or supplier handoff is the third. Someone sends a Dropbox link with 300 product photos shot at inconsistent sizes, and they all need to conform to one spec before they touch a store. That’s the e-commerce image workflow in its purest form.

A site migration is the fourth and worst. You’re moving a blog with 400 posts and every image needs pulling, resizing and reformatting.

The download step only exists in the first case. Everything after the download is identical across all four, which is why the second half of this guide matters more than the first.

The Licence Question Nobody Reads Until It’s a Problem

Free stock images are free in the way that “free parking” is free — genuinely, but with conditions posted on a sign nobody stops to read.

The three big free libraries all use custom licences rather than Creative Commons, and they are not identical. Broadly, all three let you use images commercially without paying and without asking permission. All three prohibit reselling the image itself as a standalone product. And all three get vague in the same place: what happens when the photo contains an identifiable person or a trademarked object.

That last one is where people get into actual trouble. A model release covers the photographer taking the photo. It does not automatically cover you putting that person’s face on an ad implying they endorse your product. The libraries say this in their terms, in a paragraph most people skim.

Attribution is the other difference. None of the three legally require credit any more, but Unsplash asks for it and their community norms lean hard that way. For a blog post, crediting costs you a line of text and buys goodwill. For a printed brochure, it’s awkward. Decide before you download 40 images, not after.

I’ve written a proper head-to-head on the differences in Unsplash vs Pexels vs Pixabay, including which one actually has the deepest catalogue for the kinds of searches people run.

The short version for bulk work: if the images are going on your own marketing site, all three are fine. If they’re going into a paid product, a client deliverable, or anything with a legal review attached, read the specific licence for the specific library before you commit to 50 files.

Searching Three Libraries at Once

The tab problem I opened with has a structural cause: the libraries don’t talk to each other, so thoroughness means running the same query three times and mentally diffing the results.

That’s the gap our bulk image downloader fills. You type a search term once, it queries Pixabay, Unsplash and Pexels together, you pick what you want, and everything comes back as a single ZIP. No tab per image, no right-click-save ritual, no thirty files named after their provider’s internal ID.

One thing to be clear about, because the phrase “bulk image downloader” gets used for two different tools: this searches stock photo libraries. It does not crawl a website and pull down every image on it. If what you need is “grab all 200 images off this URL,” you want a scraper or a browser extension, and that’s a genuinely different category of tool with its own legal considerations. I’d rather say that plainly than have you discover it after clicking.

For stock sourcing specifically, one search and one ZIP is the entire pitch, and it collapses the slowest part of the job.

Everything You Just Downloaded Is Too Big

This is the part that surprises people, and it’s the reason a “download” guide has to keep going past the download.

Stock libraries serve images at the resolution the photographer uploaded, because they can’t know what you need. That’s frequently 4,000 to 6,000 pixels on the long edge, at 4–8MB per file. A blog hero image needs maybe 1,600 pixels. A product thumbnail needs 400. A social post needs whatever that platform wants this month.

So a batch of 30 stock photos lands as roughly 180MB of images that would each take several seconds to load on mobile. Dropped onto a page unchanged, they’d tank your Core Web Vitals single-handedly — an oversized hero image is one of the most reliable ways to fail a Largest Contentful Paint audit.

The fix is three passes, in this order, and the order matters.

Resize first. Take the whole batch down to the largest dimension you’ll actually display. Doing this first means every subsequent step operates on far less pixel data, which makes everything faster. Our bulk resizer takes the folder and one target width and handles the rest; the bulk resizing guide goes deeper on picking that number and on what “without losing quality” actually means.

Compress second. Now that the pixels are right, squeeze the file size. Quality 80 is the setting I reach for by default on photographic content — the difference from the original is invisible at normal viewing distance and the savings are typically 60–75%. The complete compression guide covers where that number should move.

Convert last. WebP is 25–35% smaller than JPEG at equivalent quality and browser support has been a non-issue for years. Converting after compression rather than before avoids stacking two lossy passes on top of each other. The format conversion guide has the full decision tree, and JPG to WebP is the specific conversion most of these batches need.

Running 30 stock photos through all three passes takes under a minute in a browser. Doing it one file at a time in an image editor is most of an afternoon. That gap is the entire argument for batch tooling, and it’s the same argument whether the images came from a stock library or a camera.

Naming Things So Future You Doesn’t Suffer

A small discipline that pays off disproportionately: rename before you process, not after.

Files arriving as pexels-photo-3184465.jpeg and photo-1522202176988-66273c2fd55f.jpg are unsearchable six weeks later. You will not remember which one was the office shot. Worse, image filenames are a genuine if modest SEO signal — warehouse-inventory-system.jpg tells a crawler something that photo-1522202176988 does not. If you’re thinking about discoverability at all, our image SEO article covers where filenames sit relative to alt text and structured data in terms of actual impact.

Rename on the way in, while you still remember what you searched for. Batch renaming tools exist on every platform — Finder does it natively on macOS, PowerToys does it on Windows.

Sizing for Where the Images Are Actually Going

One target width doesn’t survive contact with reality, because the same batch usually feeds several destinations.

A blog needs one width. A product grid needs a square crop. Instagram wants 1080×1350 for the 4:5 portrait slot that dominates the feed. LinkedIn wants something else. If the batch is heading to social, the platform size reference lists what each network currently wants, and the aspect ratio calculator works out the pixel dimensions for any ratio you need to hit.

The practical approach is to resize once to your largest destination, then derive the smaller ones from that — not to go back to the 6,000-pixel originals each time. Keep the originals archived somewhere, but work from the resized set.

If the destination needs a specific shape rather than a specific size, bulk crop handles a batch to one aspect ratio in a single pass.

When Bulk Stock Sourcing Is the Wrong Move

I’d be doing you a disservice if I didn’t say this part.

Stock photography looks like stock photography. Download 20 images for “team collaboration” and you’ll get 20 variations on the same well-lit conference room, and so will every competitor searching the same term. There’s a real cost to a site that looks assembled from the same library as everyone else’s.

Bulk stock sourcing earns its place for backgrounds, textures, abstract or supporting imagery, placeholder content during a build, and anywhere the image is decoration rather than argument. It’s a poor substitute for photos of your actual product, your actual team, or your actual work. Those need shooting.

The honest split I’d suggest: source the supporting 80% in bulk and spend the time you saved on the 20% that carries the message.

Putting the Whole Thing Together

The pipeline, end to end: search the libraries in one pass, check the licence for how you’re actually going to use the images, download as a ZIP, rename while you still remember the context, resize to your target width, compress at quality 80, convert to WebP, ship.

The first two steps take judgment. The last four take about a minute for a batch of any reasonable size, provided you’re not doing them one file at a time.

---

Need images and then need them web-ready? Start with the bulk image downloader to search Pixabay, Unsplash and Pexels in one go and get everything as a single ZIP. Then run the batch through the bulk resizer, compressor and format converter — all in your browser, nothing uploaded anywhere, no signup.

Frequently Asked Questions

How do I download multiple images at once instead of one by one?

For stock photography, use a tool that searches the libraries and bundles results into a single archive — BulkImagePro's bulk image downloader queries Pixabay, Unsplash and Pexels together and returns everything as one ZIP, so you avoid opening a tab per image. For downloading every image already embedded on a specific web page, you need a different category of tool: a browser extension or a scraper, since that involves crawling a site rather than searching a photo library.

Are free stock images actually free for commercial use?

Generally yes on Unsplash, Pexels and Pixabay — all three permit commercial use without payment or permission, and none legally require attribution any more. The limits are consistent across them: you cannot resell the image itself as a standalone product, and using photos containing identifiable people in a way that implies endorsement is not covered by the licence. If the images are going into a paid product or a client deliverable, read that specific library's current terms rather than relying on a summary.

Why are downloaded stock photos so large, and what should I do about it?

Stock libraries serve images at the resolution the photographer uploaded, commonly 4,000–6,000 pixels wide at 4–8MB per file, because they cannot know your intended use. A blog hero typically needs about 1,600 pixels and a thumbnail around 400. Resize the batch to your target width first, then compress at around quality 80, then convert to WebP. Doing it in that order avoids stacking lossy passes and keeps each step operating on less data.

Should I resize or compress first?

Resize first. Compression quality settings are applied to whatever pixel data exists, so compressing a 6,000-pixel image and then shrinking it to 1,600 pixels wastes the first pass entirely and can introduce artifacts that the resize then bakes in. Resizing first also makes the compression step faster, since it operates on a fraction of the original pixels. Convert format last, after both.

Can BulkImagePro download all the images from a website URL?

No. The bulk image downloader searches stock photo providers — Pixabay, Unsplash and Pexels — and packages the results as a ZIP. It does not crawl arbitrary websites or extract images embedded in a page you supply. For that you would need a scraper or a browser extension, which carries different legal and copyright considerations depending on the site involved.

What's the fastest way to get a batch of images ready for a website?

Three passes over the whole batch rather than per-file editing: resize everything to one target width, compress at quality 80, convert to WebP. For 30 images this takes under a minute in a browser-based batch tool, against roughly an afternoon doing it individually in an image editor. Rename the files before processing, while you still remember what each one is — descriptive filenames are also a modest SEO signal.