Skip to main content
Perfect_Nemus
Known Participant
July 22, 2026
Question

PS close all files after Image processor massive exporting

  • July 22, 2026
  • 7 replies
  • 84 views

That’s a pretty big issue: 

  1. Open a file
  2. Edit it
  3. launch Image Process using the same folder of the opened file as target

At end end of the process all opened file get closed, withouth asking for saving.

I’m getting pissed off about this, every release one fix and two regressions.

 

 

    7 replies

    Stephen Marsh
    Community Expert
    Community Expert
    July 29, 2026

    I can only test as far back as v2021 on this PC…

     

    EDIT: I'm going to need to re-test as there are different options that need to be documented.

    Perfect_Nemus
    Known Participant
    July 29, 2026

    Are you kidding me??

    Photoshop closes unsaved files without any alert and you move this from “bug-report” to “questions”???

    @D Fosse ​@Sameer K 

    Oliversmith
    Participant
    July 29, 2026

    That’s really frustrating. Photoshop should never close unsaved files without warning. Adobe needs to fix this ASAP.

    D Fosse
    Community Expert
    Community Expert
    July 22, 2026

    OK. I always use Batch, not Image Processor, and it never touches open files. Try that instead. 

    Perfect_Nemus
    Known Participant
    July 29, 2026

    As a workaround, it can be usefull, but the bug is still there

    D Fosse
    Community Expert
    Community Expert
    July 22, 2026

    Not sure I understand what you’re saying.

     

    The whole purpose of the Image Processor is to save the batch of files to the specified location, as an express automated function. You normally don’t want the whole batch to remain open, since that will build up a huge scratch file that could easily choke an average machine, such as, say, a laptop.

     

    If you have other, more special needs, I would recommend File > Automate > Batch, where you could run an action specifically suited for your needs. In the Batch dialog, you can set destination to “None”, leaving it to the action to determine what happens to the processed files (including leaving them open).

    Perfect_Nemus
    Known Participant
    July 22, 2026

    Infact I'm not saying I want the batched exported files to stay opened, only those that were opened BEFORE the batch process.

    Before this bug, If I have an opened file, then I run the image process to the very same folder of the opened file, it simply open a copy of that file (the most recent saved one), it exports that, then it close the copy of the file opened. But the original opened file, the one opened at the very beginning, stays opened. I can well assure this as I'm using this workflow since 2019.

    The fact that image process closes a file where there are unsaved edits, without asking or saving nonetheless, it's a bug.