The first time I lost a client over export settings, I didn’t even realize that’s what had happened. I’d delivered 80 retouched product images for a mid-size e-commerce brand, everything looked great on my end, and then their developer came back three days later saying half the files were too large for their CMS and the color profiles were wrong for web. I had to re-export the entire job manually, one file at a time, because I’d never bothered to build a proper export action. That afternoon cost me four hours. The client relationship cost me more.

That was about twelve years ago. I haven’t manually re-exported a batch since.

The Hidden Cost of “Export As” Every Single Time

Most photographers treat export as an afterthought, something you do when the real work is done. But if you’re shooting commercially, or doing any volume of retouching, export is where time disappears fastest. Think about the decisions you’re making every single time you hit File > Export: color space, resolution, file format, compression level, naming convention, destination folder. That’s six variables, and if any one of them is wrong, you’re either going back to fix it or delivering something suboptimal.

The deeper issue is that Photoshop doesn’t remember what you intended, it only remembers what you did last. So if you exported a 300 DPI CMYK TIFF for a print job yesterday and you’re exporting 72 DPI sRGB JPEGs for web today, you have to manually change every single setting. Every. Time. Multiply that by 50 files and you’re looking at a significant block of time spent on something a well-built action could handle in the background while you’re drinking coffee.

What a Proper Export Action Actually Does

A good export action isn’t just a macro that clicks “Save.” It’s a decision tree baked into a repeatable sequence. Here’s what mine includes for a standard e-commerce web export:

  1. Flatten image (to merge any open adjustment layers I forgot to collapse)
  2. Convert to sRGB IEC61966-2.1 (the profile most CMS platforms and browsers render correctly)
  3. Image Size to longest edge 2000px at 72 PPI, with resample set to Bicubic Sharper
  4. Run a sharpening action (I use a high-pass layer set to Overlay at 30% opacity, then flatten)
  5. File > Export > Export As, with JPEG quality set to 80, metadata stripped except copyright
  6. Save to a pre-defined subfolder called “WEB EXPORTS” inside the current job folder
  7. Close without saving (so the layered master file stays untouched)

That whole sequence runs in about four seconds per file. Batched across a folder of 100 images, it takes roughly seven minutes unattended. The same job done manually would take the better part of an hour, assuming you’re fast and don’t make mistakes.

The JPEG quality setting of 80 is worth pausing on. Quality 100 in Photoshop produces files that are often 3-5x larger than quality 80 with almost no visible difference at web sizes. For a 2000px image, quality 80 typically lands between 400KB and 800KB depending on complexity. Quality 100 can push past 2MB. That matters enormously for page load speed, CDN costs, and CMS upload limits.

Building for Multiple Deliverable Types Without Rebuilding Everything

Where most export workflows break down is when a single job requires multiple output types. Ad agencies almost always do: they want a high-res TIFF for print, a web JPEG for the campaign landing page, and sometimes a PNG with transparency for digital ads. If you’re running three separate manual exports, you’re tripling your exposure to error.

The cleaner approach is to build a set of export actions, one per deliverable type, and run them sequentially from a single Batch command or a parent action that calls each one. I have four standard export actions saved: PRINT (CMYK TIFF, 300 DPI, full resolution, embedded profile), WEB (sRGB JPEG, 72 DPI, 2000px long edge, quality 80), SOCIAL (sRGB JPEG, 72 DPI, 1080px long edge, quality 75), and TRANSPARENT (sRGB PNG-24, 72 DPI, 2000px long edge). Each one saves to its own clearly named subfolder. When a client needs all four, I run a parent action that calls all of them in sequence. One click, four folders, zero re-exporting.

The Weekend I Built a System That’s Saved Me Over 400 Hours

A few years into running my own consultancy, I landed a contract with an agency that needed 500 product shots processed and delivered within a single week. The shooting was handled by their team; I was doing all the post. I spent one Saturday building out a complete batch system: folder structure, naming conventions, retouching actions, and a three-stage export workflow. Sunday I tested it. Monday through Thursday I processed images. Friday I delivered.

I ran the batch export across all 500 files in just under 40 minutes. I’ve since tracked the time that system has saved me (yes, I keep a spreadsheet), and that single workflow template has been repurposed on at least 30 subsequent jobs. The cumulative time savings from that one weekend of setup work is somewhere north of 400 hours.

The Color Profile Problem Nobody Talks About at Handoff

One last thing worth mentioning, because it bites people constantly: stripping versus embedding color profiles on export. If you’re delivering to a web developer or a CMS, embedded sRGB profiles are usually fine and actually helpful for browsers that support color management. But some older upload systems or stock platforms actively choke on embedded profiles and render colors incorrectly. In those cases, you want to convert to sRGB and then strip the profile on export, which you can set inside the Export As dialog by unchecking “Embed Color Profile.”

I now ask every new client, specifically their developer or digital producer, which they prefer before I finalize my export action for their deliverables. It takes one email. It saves a potential re-delivery.

The single most important thing I can tell you is this: the time you spend building a precise, tested export action pays back at a ratio of at least 10 to 1, and every job you take on after that gets cheaper to deliver.