I’m trying to re-save a large batch of PSD files (including all subfolders) to force Photoshop to embed the “Maximize Compatibility” composite. In older versions of Photoshop, Image Processor allowed saving directly back to the original file location without creating any subfolders. In the current version, Image Processor always creates new subfolders (JPEG, PSD, TIFF) in every directory, even if I only select “Save as PSD” and uncheck everything else. There’s no option anymore to overwrite the existing PSD files on the same path. What I need is simple: process all PSD files recursively,re-save them as PSD,overwrite the originals,without generating new subfolders in every directory. Right now Image Processor seems to make this impossible.Batch + Actions still works, but Image Processor used to support this workflow too. So my question is: Is this just me missing a hidden setting, or did Adobe actually remove the ability to save to the original location without creating subfolders? If that option is gone, is there any official workaround besides using Batch + a custom Action or writing JSX scripts? Thanks!

.random..

Inspiring

Question

Image Processor no longer overwrites original files?

Forum|Forum|5 months ago
November 29, 2025
3 replies
1919 views

I’m trying to re-save a large batch of PSD files (including all subfolders) to force Photoshop to embed the “Maximize Compatibility” composite. In older versions of Photoshop, Image Processor allowed saving directly back to the original file location without creating any subfolders.

In the current version, Image Processor always creates new subfolders (JPEG, PSD, TIFF) in every directory, even if I only select “Save as PSD” and uncheck everything else. There’s no option anymore to overwrite the existing PSD files on the same path.

What I need is simple:

process all PSD files recursively,
re-save them as PSD,
overwrite the originals,
without generating new subfolders in every directory.

Right now Image Processor seems to make this impossible.

Batch + Actions still works, but Image Processor used to support this workflow too.

So my question is: Is this just me missing a hidden setting, or did Adobe actually remove the ability to save to the original location without creating subfolders?

If that option is gone, is there any official workaround besides using Batch + a custom Action or writing JSX scripts?

Thanks!

macOS

Stephen Marsh

Community Expert

You can save without creating sub-folders by using the "select folder" option with "keep folder structure" and selecting the parent/root top-level directory, however, originals will not be overwritten, a "_1" suffix will be added. The script would require modification to work differently.

.random..Author

Inspiring

Thanks, I’m aware of that workaround – the problem is, as you said, that it creates duplicate files with a _1 suffix.

In our case we need to re-save millions of existing PSDs in place with max compatibility, without breaking the folder structure or doing any manual merging afterwards.

I’ve ended up using a custom script that opens each file and saves it back over itself, which works great – I just find it strange that this isn’t possible directly in Image Processor anymore, given that it used to be trivial.

Stephen Marsh

Community Expert

Thanks, I’m aware of that workaround – the problem is, as you said, that it creates duplicate files with a _1 suffix.

The Image Processor version that ships with Photoshop 2026 is "1.2.0.3", it would surprise me if Adobe has made any changes to this script in years.

So perhaps it never did overwrite?

As I previously mentioned, the code would need to be edited to do so, such as removing the following highlighted entry (untested):

Code_4Nb97kZ7wx.png

A

aditya_6641

First off, you're not going crazy, I just tested this myself in the latest Photoshop, and you're absolutely right. The "save in same location" behavior you remember from older versions is indeed gone. The Image Processor now forces you to choose a destination folder and will always create those subfolders (JPEG, PSD, TIFF), even if you only have one format selected

Stephen Marsh

Community Expert

I'll look into this... The opposite requirement was needed in this topic:

https://community.adobe.com/t5/photoshop-ecosystem-discussions/batch-remove-maximize-compatibility-from-psd-folders/m-p/15481712

.random..Author

Inspiring

I finally solved the issue by having GPT generate a script that simply goes through the entire top-level folder (including all subfolders), opens every PSD, and performs a Save As to the same location. That forces Photoshop to rebuild the composite layer. It works — but honestly, the fact that this is necessary is mind-blowing.

We have millions of files in thousands of folders in our company archive, and every now and then a PSD ends up saved without Maximize Compatibility enabled.

Result? Lightroom refuses to import it.
Seriously? Lightroom cannot handle a PSD — an Adobe-native format — just because it’s missing a composite preview? That was jaw-dropping.

Fine, I thought I’d batch-fix it via Bridge.
Except Bridge’s Image Processor can’t resave PSDs.

Alright then, Photoshop Image Processor… because that one does have a “Maximize PSD Compatibility” checkbox. Except it forces everything into newly generated subfolders named “PSD” and gives you no way to overwrite files in their original structure.

So what exactly is the expected workflow here?
Am I supposed to open folder after folder manually, drag files back into place, and overwrite them manually with a file manager?

It’s absurd. Adobe products try to do a million things simultaneously and somehow fail at the most basic pipeline needs. No wonder people are moving away from Adobe — the ecosystem feels increasingly disconnected from real production workflows.

E

ExUSA

Legend

Thanks for asking — the feature we (and frankly the entire magazine publishing industry) desperately need in Bridge is a way to visually manage and assemble full publications made in InDesign.

Imagine a flatplan module inside Bridge that could:

Display every InDesign page as a separate thumbnail (not just the first page).
Allow teams to drag and drop pages or PDF ads to reorder or build an entire issue visually.
Automatically sync page order and numbering back to the linked InDesign documents.
Run a quick preflight (RGB images, low-res, bleeds, etc.) before export.
Export the final issue as ordered PDFs — ready for print or digital.

Right now, every publisher has to plan issues manually in Excel or fake it using dummy InDesign files. It’s absurd that in 2025, a product called Creative Cloud still has no built-in tool for real collaborative flatplanning or issue management.

We produce ELLE and ELLE Decoration under BurdaMedia International (Europe), and we’ve been trying to raise this internally with Adobe for months — through support, enterprise channels, and LinkedIn. Still no answer.

A lightweight Bridge-InDesign integration like this would solve one of the biggest workflow gaps in publishing — and I’d love to connect with anyone at Adobe who wants to see how easily this could be implemented.

Don't get your hopes up. This sounds more like a plugin to InDesign or an add-on to Adone Experience Manager. Bridge is barely hanging on, they don't even have cloud storage support.

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded