Skip to main content
Theo33271504y28c
Participant
February 15, 2026
Question

Error opening raw file (LRC->PS): "there isn't enough room to display this document"

  • February 15, 2026
  • 1 reply
  • 0 views

After opening, processing and closing a few raw files from Lightroom Classic (15.1.1) in Photoshop (27.3.1), opening another raw file results in error message "there isn't enough room to display this document". My Win11 PC has 100's of GB free on C: (SSD) and D: (HDD) and 64 GB of RAM of which Photoshop is set to use 85%. My graphics card is an RTX 4060 Ti, with 16GB GDDR6.
What does ‘not enough ROOM’ really mean? It cannot be disk space or RAM…
The only solution is to close and restart Photoshop, which is rather annoying to do every few files.

1 reply

Sameer K
Community Manager
Community Manager
February 16, 2026

Hey, ​@Theo33271504y28c. Welcome to the Photoshop Community. I'll help you figure this out. Based on the limited description, it is difficult to pin down. We'll need specific workflow info to be sure.

 

Please share a video of the issue and the system info from Photoshop Help > System Info. Copy and paste it into a text document, then upload and attach it here.

 

As a test, try these steps:

1—Go to Photoshop > Settings > Performance > Advanced Settings > Disable/uncheck GPU Compositing & restart Photoshop. 

 

2—Please test and confirm if Photoshop (Beta) has an issue. You can get Photoshop (Beta) from the Creative Cloud > Apps tab > Beta Apps section. 

 

Thanks! 
Sameer K

(Type '@' and type my name to mention me when you reply)

Theo33271504y28c
Participant
February 16, 2026

Hi, ​@Sameer K,

I'll give (1) a go today, which I found under Photoshop > Edit > Preferences > Performance...
Meanwhile please find attached the System Info.

Anyhow, what could be the exact meaning of the error message ‘there isn't enough ROOM to display this document’? It sounds very odd. Not enough pixels on screen? Not enough RAM? Not enough scratch disk space?

Cheers,

Theo

P.S. I found this issue mentioned in older posts, but no solution…