Choosing between Single Image Editor and Bulk Image Processor

Dropmatico has two engines. Picking the right one takes three seconds once you know the rule.

The one-sentence rule

Use the Single Image Editor when you have one hero asset that needs to ship to many platforms. Use the Bulk Image Processor when you have many assets that all need to ship to one target size. Distribution equals Single Editor. Standardization equals Bulk Image Processor.

When to use the Single Image Editor

You just finished a hero shot, a product screenshot, a launch visual, or a blog header. You need it resized to Instagram feed, LinkedIn landscape, X post, Behance, Dribbble, and a custom email banner. One master in, full Master Set ZIP out.

When to use the Bulk Image Processor

You have 16 product shots from a studio, 16 speaker headshots from an event, or 16 UI captures from a release. Every image needs to ship at the same dimension. Drop the batch, pick the target, export. Everything exits at the exact same spec, uniformly named.

Feature comparison at a glance

Both engines share the same input and output format support, the same browser-native processing, and the same structured ZIP output. The differences come down to input capacity and editing depth.

Single Editor: 1 master image, 15 social and creative platforms (plus 19 marketplaces and 6 custom sizes), 10 filters, zero-latency canvas
Bulk Image Processor: up to 16 images, 100 MB each, 1.6 GB of concurrent throughput, single target size
Both: JPEG, JPG, PNG, WebP, and HEIC input. JPEG, PNG, or WebP output at 1x to 5x scale

Can I use both in one session?

Not in a single session, but you can run them back-to-back. Finish the Bulk Image Processor job, export the ZIP, then open the Single Image Editor for hero polish work. Because processing is local, switching between engines has no context cost and no server queue.