There’s a particular kind of frustration that comes from finishing a retouching job and then spending forty minutes exporting it. The creative work is done. The client is waiting. And you’re sitting there clicking through Save for Web dialogs like it’s 2009, manually typing in filenames, second-guessing your JPEG quality slider every single time.

I’ve been doing commercial post-production for fifteen years. I’ve processed product shots for e-commerce catalogues, delivered layered comps to ad agencies, and built batch systems for studios running thousands of files a month. Export workflow is, without question, where most photographers and retouchers leave the most time on the table. And the fix is almost never glamorous. It’s settings, naming conventions, and a little upfront discipline.

What’s Actually Happening When You Export Without a System

Photoshop doesn’t know what you’re delivering or who you’re delivering it to. Every time you hit Export As or Save for Web, it starts from wherever you left it last. That means if you adjusted quality to 65 for a web preview last Tuesday and forgot, every file you export today inherits that. Quality inconsistency isn’t just an aesthetic problem. It’s a trust problem with clients who notice, and a file-size problem when you’re uploading 300 assets to a CDN.

More importantly, Save for Web (legacy) and Export As handle color profiles differently. Save for Web strips the profile by default, which is what most web delivery requires. Export As embeds it unless you tell it not to. If you’re handing off files for print, digital signage, or app UI assets, those are three different answers. Getting it wrong means your client’s developer is wondering why the hero image looks slightly muddy on the website, and you’re spending an hour troubleshooting something that should have been a non-issue.

Building an Action-Based Export Stack

The fastest thing I ever did for my export speed was stop treating each delivery format as a one-off decision and start treating it as a named preset backed by an action.

Here’s the stack I use for a standard e-commerce client delivering to three destinations: web (sRGB, JPEG, quality 80, no profile embedded, 2000px on the long edge), internal review (sRGB, JPEG, quality 60, watermark layer visible, 1200px), and print vendor (Adobe RGB, TIFF, LZW compression, full resolution, profile embedded).

Each of those is a Photoshop action that handles the conversion, resizing, and export in sequence. The web action alone runs in about four seconds per file. At quality 80 in Save for Web, a 2000px JPEG for a clean product shot typically lands between 400 and 700KB. Consistent, predictable, fast.

If you’re building this yourself, start by recording the action with a representative file open. Go to Window, Actions, hit the New Action button, and record every step including the Image Size adjustment and the Save for Web export with your locked settings. When you stop recording, test it on three different files before you trust it on a real job.

Where Scripts Become Necessary

Actions handle repetitive tasks well, but they have a ceiling. If your filenames need to include the original document name, a delivery date, or a version number, actions alone won’t get you there. That’s where a simple Photoshop script, written in JavaScript, takes over.

I learned this the hard way. Early in my consultancy I spent the better part of a day manually renaming and exporting 200 product files because the client needed outputs formatted as SKU-COLOR-SIZE.jpg and I didn’t have a script ready. It took about six hours. The script I wrote afterward takes eleven seconds to run on the same job. I keep that in a spreadsheet alongside every other time saving I’ve tracked from automation. The total is over 2,400 hours at this point, which is not a number I’m sharing to impress anyone. It’s a number I keep because it reminds me that upfront investment in a system always pays.

For most export renaming tasks, the ExtendScript Toolkit is overkill. A short script using app.activeDocument.name, a replace() call to strip the file extension, and your naming convention appended before the export call is usually under twenty lines. There are also third-party panels like Davide Barranca’s Photoshop Scripts Panel that make managing and running scripts significantly less painful if you’re not comfortable in a code editor.

Handling Multi-Client Delivery Without Losing Your Mind

Running a consultancy means I’m not just exporting for one client format. I’m context-switching between brands with different aspect ratio requirements, different color profile expectations, and different folder structures on every project.

My solution is a master Actions panel organized by client type, not by task. I have a folder called Ecomm-White-BG, another called Agency-Print-Delivery, another called Social-Crops. Inside each folder are the export actions specific to that context. When I open a new job, I look at which folder applies and run from there. Color-coded, naturally. Agency work is blue. E-commerce is green. Social is orange.

Droplets are underused for this kind of setup. A Droplet is essentially an action saved as a standalone application. You drag a folder of files onto the Droplet icon and it processes and exports everything automatically, including opening files, running the action, and saving to a destination folder, without you touching Photoshop at all. File, Automate, Create Droplet. Point it at your action, set your destination folder, choose how to handle errors, and save it somewhere obvious. I keep mine on the desktop during active projects.

The Folder Structure That Keeps Deliveries Clean

Export speed means nothing if you lose track of what went where. My standard delivery folder for any job has three subfolders: FINAL-WEB, FINAL-PRINT, and REVIEW. Every action exports directly into the correct subfolder using a hardcoded path set inside the action. No manual sorting after the fact.

The one thing I’d change if I were starting over is I’d lock in this folder convention on day one of running client work instead of retrofitting it two years in. Changing a system mid-project is where mistakes live.

Your export workflow isn’t the exciting part of post-production, but it’s the part that determines whether you look like a professional or someone who’s still figuring it out. Build it once, trust it, and let the actions do the boring work so you can focus on the retouching that actually requires your eyes.