Skip to main content
Participant
November 22, 2025
Question

Photoshop 27 uses up system data at exponential speed when converting from raw to jpeg Macbook M4Max

  • November 22, 2025
  • 1 reply
  • 157 views

Hello,

 

I just got a Mac Book M4 Max 48 RAM, 1TB SSD, OS Sequoia 15.5 to run photoshop 27.0 version to convert hundreds of raw images into jpeg files. In a bit, I got a notification that scratch disks are full. When I checked, i saw that system data was using 500 TB. I quit photoshop and opened it again to isnpect- indeed as soon as i run this batch work for file coversion, the system data on Macbook M4 MAX grows exponentialy adding up 1 GB per every few photos being convcerted- i have never seen such thing on my old Windows laptop, using older photoshop version (PS 24 OR PS 25 I belive). 

 

When i restart photoshop, i cannot purge cache- it is greyed out.

 

Did anyone experience this and is there a solution? This is a basic batch task I do very often and this is quite frustrating.

 

Thank you,

Ausra

1 reply

D Fosse
Community Expert
Community Expert
November 22, 2025

You need to specify how you batch and what this batch executes per file, step by step.

 

As long as each file closes before the next one opens, memory/scratch disk is reused and recycled. The net result is that memory/disk consumption should never exceed what is required for the one single biggest file. On my own systems I have never observed any memory/disk buildup, and I run batches all the time.

 

What we have seen occasionally, is that the GPU uses excessive memory which is not recycled, but just builds up. I need to emphasize again that this is not normal and I have never seen it myself. But we do have a number of posts from users indicating that this is something that can happen.

 

Photoshop's use of a scratch disk is a very special case. All other processes and applications will go to the system pagefile on disk when physical memory runs out. That appears to be what is happening here. A system with an integrated GPU (Apple silicon or Windows laptops) will perhaps be particularly vulnerable to this because the GPU uses shared system memory, the GPU doesn't have its own onboard VRAM.

 

In short, this needs to be broken down, and where that memory goes needs to be investigated. I'm not sure what tools are available in MacOS for this.