There’s a specific kind of frustration I’ve felt more than once: you’ve built a tight, efficient Photoshop action, it runs beautifully, and then you watch a junior retoucher spend forty minutes manually exporting the outputs because nobody thought to bake the delivery specs into the workflow. The retouching is automated. The export is chaos. It’s like designing a Formula 1 car and then letting it coast to the finish line in neutral.

After fifteen years running post-production workflows for ad agencies and e-commerce brands, I can tell you that exports are where most studio time goes to die. Not in the retouching. Not in the masking. In the final fifty feet.

The Actual Problem With “Just Save a JPEG”

Here’s what’s happening technically when you export without a defined spec: Photoshop makes decisions for you, and those decisions are rarely optimal for your delivery context. The “Save for Web” dialog defaults to sRGB with a quality setting of 60, which is fine for a blog thumbnail and genuinely terrible for a client who’s printing a 48-inch trade show banner. Meanwhile, “Export As” and “Save As” don’t even apply the same compression algorithms. They’re not the same tool wearing different clothes. They produce measurably different files.

JPEG compression in Photoshop uses a quality scale of 0 to 12 (in the traditional Save As dialog) or 0 to 100 (in Export As). These scales don’t map linearly to each other. A quality 8 in Save As is not equivalent to 80 in Export As. If you’re building actions for a team and mixing these two export paths, you’re shipping inconsistent files without knowing it.

Color profile embedding is the other landmine. If your working space is ProPhoto RGB and you export without converting to sRGB, the file looks beautiful on your calibrated monitor and completely washed out on the client’s MacBook Air. Every single export action I build now includes an explicit Convert to Profile step, targeting sRGB IEC61966-2.1, before the save command fires.

How to Build Export Logic Into the Action Itself

The cleanest approach I’ve landed on after years of iteration is treating the export step as a non-negotiable final node in every action, not an afterthought you do when the action finishes. Here’s how that looks in practice.

For e-commerce product work, most platforms want JPEGs at 72 PPI, sRGB, with files landing between 500KB and 1.5MB. I target Photoshop’s Save As JPEG at quality 9 (on the 0-12 scale), which gets me around 800KB on a 2000x2000px file with a white background. That hits the sweet spot: fast load time, no visible compression artifacts on product edges, and compliant with Amazon, Shopify, and most major retailer portals without a separate compression pass afterward.

For print delivery, I keep a separate export action that flattens the file, converts to CMYK using the U.S. Web Coated (SWOP) v2 profile, and saves a TIFF with LZW compression. LZW is lossless and keeps print files readable by every prepress shop I’ve ever worked with. The resulting files run 40-60MB for a full-bleed full-page layout, which sounds large but is exactly what you want when a printer is ripping the file at 300 DPI.

The key is that none of this happens manually. It’s all inside the action. Record the conversion, record the save with explicit settings, record the close without saving the working PSD. Done.

Where Batch Processing Breaks If You’re Not Careful

Running exports through Photoshop’s Batch command (File, Automate, Batch) introduces one wrinkle that trips people up constantly: the “Override Action’s Save As Commands” checkbox. If you check it, Photoshop ignores the destination you hardcoded into the action and uses the batch destination instead. If you don’t check it, the action saves to wherever you told it to when you recorded it, which is usually your desktop from six months ago.

My rule is this: if the export action is saving to a relative location (a subfolder within the source folder), leave the override unchecked and let the action handle it. If you’re batch processing to a specific delivery folder that changes per job, use a Droplet instead. A Droplet is just a saved Batch configuration packaged as a drag-and-drop application, and it lets you update the destination without opening Photoshop’s menus. I keep job-specific Droplets on my desktop for active projects and archive them when the job closes.

The Weekend I Stopped Losing Hours to Manual Exports

A few years ago I had a client, a mid-size e-commerce brand, drop 500 product images on me with a 48-hour turnaround. Same background removal, same color correction pass, same three output formats: web JPEG, print TIFF, and a square-cropped social version. I spent a Saturday building a three-action sequence with a master Droplet that processed all 500 images and spat out 1,500 files sorted into three labeled folders. It ran while I made dinner.

I track this kind of thing in a spreadsheet, and that single job clocked about 14 hours of saved manual export time. Across everything I’ve automated over the years, I’m sitting somewhere north of 2,400 hours saved. That’s not a hypothetical. That’s time I’ve spent on actual creative work, on client relationships, on not hating my job.

Making Your Export Actions Bulletproof for a Team

If you’re distributing actions to other people, the export step needs to be even more explicit. Record your actions on a clean installation when possible, or at minimum document which color profile and PPI settings are baked in. I include a read-me text file with every action set I send to clients that lists the exact export specs, the intended delivery context, and which Photoshop version the action was recorded on. Version matters more than people think: export dialogs in Photoshop CC 2022 and later behave differently than in CS6, and an action recorded in one can silently fail in the other.

Test every export action on files you didn’t create. Your own PSDs are too familiar. Hand the action to a colleague with a messy layered file and see what breaks. The failure mode you find in testing is the one you won’t find at 11pm before a client deadline.

The single most important thing you can do for your export workflow is stop treating the save step as something that happens after the work. It is part of the work, and it belongs inside the action.