Bulk Photo Colorization: Color 1,000 Photos at once

Single-photo colorizers are fine for a birthday-gift restoration. But a real archive — a grandmother's shoebox digitized into 1,400 scans, a studio's back catalogue, a museum's B&W collection — breaks them completely. Uploading files one at a time, waiting, downloading, renaming, and doing it again a thousand times isn't a task you finish. It's a task you abandon.

Bulk photo colorization means treating the whole collection as the unit of work, not the individual image. You point at a folder, the tool expands it, queues every photo, and colors them in a continuous run. Revive is built for exactly this: it lives inside Google Drive as a Workspace add-on, so the batch runs where your photos already are — no uploads, no third-party storage, no download-rename-reupload loop.

The problem with "one at a time"

Most colorization tools are single-file by design. That's fine at small scale and disastrous at large scale, because the per-photo overhead — the clicking, waiting, saving, and organizing — dwarfs the actual processing. Do the arithmetic on a thousand photos and the manual handling alone is measured in days.

To batch colorize photos properly you need three things the single-file tools don't offer: a way to select many files at once, a queue that runs them without babysitting, and results that land back in an organized place. Revive's answer to all three is the folder.

Folder-aware batching: how it works

Open the Revive side panel in Drive and pick a whole folder instead of individual files. Revive expands the folder tree, walks into every sub-folder, and queues every supported image it finds. You don't hand-pick files — you hand it the root and it does the discovery.

The output mirrors the input. Every colorized copy lands in the same folder as its original, named filename-color.jpg, with your sub-folder structure intact. A /1950s and /1960s split going in stays a /1950s and /1960s split coming out. Your originals are never modified — the color versions sit right alongside them.

How fast is a batch, really?

Speed is what separates a real bulk workflow from a novelty. Revive colorizes at roughly 50–100 milliseconds per photo on average, which works out to about 1,000 photos in roughly a minute. That's the processing itself — because files never leave Google's infrastructure, you also skip the upload and download time that dominates browser-based tools.

Times are approximate and scale with the ~50–100ms-per-photo average. The point isn't the exact clock reading — it's that a collection you'd never finish by hand is done before your coffee is.

Every input format, one clean output

Real archives are messy. Scans come off different machines and phones in different formats, and a bulk tool has to swallow all of them without you sorting first. Revive accepts JPG, PNG, HEIC, TIFF, and WebP as input and writes a color JPEG for each. Mix formats freely inside one folder — the queue handles them together.

The batch workflow, start to finish

For the full click-by-click version, see how it works. Everything happens inside Drive through the narrow drive.file scope — Revive only touches the files you point it at.

What a big run costs — and what it doesn't

Revive is pay-per-image with no subscription: 1 image equals 1 colorized photo. You buy a pack of image credits, and those credits never expire — so a 10,000-photo archive doesn't force you onto a monthly plan you'll cancel next week. The credits sit on your domain billing account and any Workspace user can spend them, with every job attributed in the usage report. That matters for teams processing archives together.

The per-photo rate drops as packs get bigger. Here's the ladder (savings anchored to a $0.10 list rate):

For genuinely large archives — the 10,000-image kind — custom volume pricing takes the per-photo cost down to 5¢. See the full pricing page for details and FAQs.

You only pay for results

In any batch of thousands, a few files will be corrupt, oddly encoded, or otherwise unprocessable. Revive auto-refunds failed jobs — a credit is only spent on a photo that actually comes back colorized. You're never charged for a file that didn't produce a result, which means you can throw a whole messy folder at it without auditing every file first.

Batch colorizer vs. single-file tool

Who runs batches like this

The people who need bulk colorization aren't usually restoring one photo — they're clearing a backlog. Family archivists digitizing decades of albums. Photographers with vintage reference libraries. Studios and estates with production stills. Libraries, museums, and universities with B&W collections that need to stay inside the institution's own Drive for governance reasons. The common thread: too many images to do by hand, and files that shouldn't leave Google.

If you're weighing the security side of that — why "inside Drive" matters for an institution — it's worth reading whether it's safe to colorize photos in Google Drive. And if you're still deciding on pack size, how much photo colorization costs breaks down the math per archive.

Start small, then run the whole archive

You don't have to commit to a 10,000-image run on faith. Every new account gets 3 free images on signup — no credit card. Colorize three photos from the archive you're worried about, confirm the quality holds on your specific scans, then point Revive at the whole folder. The workflow is identical whether the batch is 3 images or 10,000; only the count changes.