A few years back, I had a Monday morning that I still think about. An e-commerce client needed 500 product images resized, sharpened, and exported to three different specs before end of business. It was the kind of job that makes a less-organized person stare at the ceiling. I had a batch system I’d built the previous weekend, pointed a Droplet at a folder, walked away to get coffee, and came back to 1,500 finished files sitting neatly in color-coded output folders. The whole process ran while I ate lunch.

That’s what Photoshop Droplets actually are. Not a trick, not a novelty feature buried in a menu most people never open. A properly built Droplet is the difference between a studio that scales and one that charges by the hour for work that should take seconds.

What a Droplet Actually Is (and Why It’s Not Just a Fancy Action)

Most photographers know Photoshop Actions. You record a sequence of steps, hit play, done. A Droplet takes that concept one step further: it compiles your action into a standalone application icon that lives on your desktop or anywhere in your file system. You drag a folder, a file, or even a selection of images onto that icon, and Photoshop handles the rest, no open-file dialog, no menu navigation, no clicking play.

Under the hood, Droplets are essentially a wrapper around Photoshop’s Batch command (File > Automate > Batch), with a destination, error handling behavior, and file naming convention baked in at creation time. When you drag images onto a Droplet, it calls Photoshop, feeds it the source files, runs the specified action, applies your output settings, and closes the files. The key distinction from a standard Batch run is portability. You can park a Droplet on your desktop, pin it to a folder, or even hand it to a retoucher on another machine running the same Photoshop version.

Building a Droplet That Won’t Break at 2am

Go to File > Automate > Create Droplet. The dialog has five sections, and most people rush through them. Don’t.

Start with the action selection. Make sure the action you’re pointing to is tested and finalized. A Droplet is only as reliable as the action inside it. If your action has a Save step recorded into it, remove it before building the Droplet. You want the Droplet’s own destination settings to handle saving, not a recorded save dialog that may not match your current export specs.

In the Destination section, choose “Folder” rather than “Save and Close.” This gives you a clean output directory separate from your originals. Always. I keep my source folders on one drive and output folders on a second. It’s the kind of redundancy that sounds obsessive until you accidentally overwrite 200 client files.

The File Naming section matters more than it looks. Build a naming convention that includes the original document name, a sequence number, and the date. Something like: [document name] + [2 digit serial number] + [YYYYMMDD]. This prevents file collisions when running multiple Droplets against overlapping source libraries and makes version tracking straightforward.

Check “Suppress File Open Options Dialogs” and “Suppress Color Profile Warnings.” Without these, Photoshop will pause and ask questions for every file it touches. On a 500-image run, that’s 500 interruptions.

The Error Handling Setting That Saves Projects

The “Errors” dropdown at the bottom of the Create Droplet dialog has two options: “Stop for Errors” and “Log Errors to File.” For any production batch, choose “Log Errors to File” and point it to a text file in your output folder. If a corrupted file or an unexpected color mode causes a failure, Photoshop skips that file, logs it, and keeps moving. You review the log afterward and reprocess just the problem files.

I learned this the hard way years ago. Had an action stop cold at file 47 of 300 because one image was in CMYK instead of RGB. Sat there for 20 minutes before I noticed. Now every Droplet I build logs to a file named _errors_[date].txt in the output folder. Takes five extra seconds to set up and has rescued at least three late-night jobs.

Cross-Platform Droplets and Where They Break

Droplets are technically platform-specific. A Droplet built on a Mac won’t run natively on Windows, and vice versa. However, Photoshop has a workaround. If you drag a Droplet built on one platform onto Photoshop’s application icon on another platform, Photoshop will update it automatically for that OS. This is documented behavior, not a hack, but it trips up studios running mixed environments.

The other common failure point is font dependencies. If your action applies a text layer using a font that isn’t installed on the machine running the Droplet, it will fail or substitute. For any Droplet you plan to share or use across systems, audit your action for font use and either eliminate it or document the dependency clearly in a read-me file alongside the Droplet.

When Droplets Are the Wrong Tool

Droplets are not the answer when your workflow requires decision-making at the file level. If each image needs a different crop ratio, a different background color, or a manual review step, a Droplet will enforce the same choices across every file without asking. That’s its strength in uniform batch jobs and a real problem in editorial or custom retouching workflows.

For those jobs, I use Photoshop’s Image Processor (File > Scripts > Image Processor) for simple resize-and-export tasks, or I build conditional actions using the “Stop” command to pause and prompt the operator at specific decision points. The Droplet stays in my toolkit for the high-volume, uniform jobs where consistency matters more than customization.

The honest case for building your first Droplet is this: find one task you repeat more than 20 times a week, record a clean action for it, and spend 10 minutes setting up a Droplet this afternoon. The time you recover in the first month will exceed the setup cost by a ratio that should embarrass you for not doing it sooner.