Why Does the Browser Freeze When Compressing Very Large Images?
Local compression runs on your own computer's CPU and memory, so a very high-resolution image (a hundred-megapixel panorama, for instance) or processing hundreds of files at once can noticeably slow the browser tab or make it briefly unresponsive.
Why local processing uses so much of your resources
A server-side compression tool runs on compute in a remote data center — your computer only has to upload and download the file. Local processing moves that compute into your own browser instead: decoding, re-encoding, and palette quantization all run on your machine's CPU and memory. A single ordinary photo processes quickly, but a very high-resolution image or a large batch noticeably amplifies that cost.
Common slowdown scenarios and how to handle them
| Scenario | Recommendation |
|---|---|
| A single image at extremely high resolution (a hundred-megapixel panorama, for example) | Check whether the original resolution is actually needed — many use cases are fine with manually downsizing before compressing |
| Dropping in hundreds of images at once | Split into several batches of a few dozen each and process them separately |
| Several other tabs or memory-heavy apps open at once | Close what you don't need before running a large batch |
If the tab genuinely stops responding
If it stays fully unresponsive for several minutes or more, try refreshing the page and starting over with a smaller batch. For very large images or very large batches, splitting the work into smaller pieces is almost always more reliable than forcing everything through in one pass.
- Before running a very large batch, test with a small portion first to estimate how long the full run will take.
- For an important long-running job, avoid switching to other memory-heavy tasks while it's in progress.
Your files are processed in the current browser and are not uploaded as article samples.