Why editing multiple open pictures uses memory

Your photo files may be only a few megabytes each, yet your computer gets slower as you open more pictures in an editor. The file size is not the whole story: the editor needs memory to display the full image and may also keep layers, edits, and working copies available.

Use the Photo Editor to compare a normal editing session with one picture open and then several. You can check memory use in your computer's own system monitor while you work.

Check memory use as you open pictures

1. Open the Photo Editor and load one picture from your device using the editor's available file-opening controls.
2. Note the picture's pixel dimensions if you can. A picture that is 6000 by 4000 pixels has 24 million pixels, even if its compressed file is small.
3. Make a simple edit, such as trying an adjustment or adding a layer. Keep the picture open while you check memory use in Task Manager on Windows or Activity Monitor on a Mac.
4. Open another picture using the workflow you normally use, such as a separate editor window or document, and check memory again. Repeat with another picture, keeping other apps and browser tabs as steady as you can.

On Windows 11, open Task Manager with Ctrl + Shift + Esc and look at Processes and Performance. On a Mac, open Applications › Utilities › Activity Monitor and select the Memory view. A browser can split its work across processes, so the browser's total may not appear as one simple number.

What the result means

Memory rises with each picture

This is expected. The editor has to keep the open images available so it can show them and respond to edits. Larger pixel dimensions generally take more memory, whether or not the original files look small on disk.

Memory rises after an edit or layer

The editor may need extra working space for an adjustment, a layer, a selection, or an undo step. Some editing operations keep earlier or intermediate image data so you can change or undo the result. The exact amount depends on the editor and the operation.

The editor gets slow when total memory is nearly full

When available memory runs low, the operating system may move some data to storage, which is much slower than RAM. The whole computer can feel sluggish, not just the photo editor. Close a few open pictures or other demanding apps and see whether responsiveness returns.

The memory number barely changes

That does not prove the editor uses no extra memory. The browser may reuse memory it already reserved, the operating system may report it differently, or the image may be small. Compare the same workflow more than once and pay attention to whether the editor remains responsive.

How to reduce memory use

1. Close pictures you are finished with. Save your work first, then close documents or editor windows you no longer need. Keeping an image open can keep its working data in memory.
2. Close unused browser tabs and apps. A video stream, large web app, or other editor can compete for memory. On Windows 11, use Task Manager › Processes to find apps using a lot of memory. On a Mac, check Activity Monitor › Memory and quit apps you recognize and are not using.
3. Work with smaller copies when full resolution is unnecessary. A photo meant for a small web graphic may not need the full dimensions of a camera original. Make a smaller working copy with an image app that can resize it, and keep the original unchanged in case you need it later.
4. Use fewer active layers and effects. The Photo Editor includes layers, brushes, selections, text, adjustments, and filters. If your edit has many separate elements, remove any you no longer need or simplify the edit where possible. Save a copy before making changes you might want to undo.
5. Restart the browser after saving. If memory stays high after you have closed the pictures, save your work and restart the browser. This can release memory held by a long-running session.
6. Restart the computer if the slowdown continues. This gives the operating system a fresh start and closes background processes that may have accumulated. Reopen only the pictures and apps you need, then compare performance again.

Why a small photo file can need a lot of memory

JPEG and other common photo files are compressed to take up less storage. To edit and display them, an editor usually works with a decoded image: the pixel data expanded into memory. One simple estimate for an image with four bytes per pixel is width multiplied by height multiplied by four.

For example, a 6000 by 4000 image would need about 96 megabytes for one basic pixel buffer: 24 million pixels multiplied by four bytes. That is only an illustration, not a measurement of the Photo Editor's actual memory use. The editor, browser, color data, layers, undo information, and other working buffers can add to the total. Several open images can therefore take much more memory than their combined file sizes suggest.

The Photo Editor runs in your browser, and the pictures and edits stay on your device.