Browser experiment

Browser Image Limits: Why a Small Photo File Can Use a Lot of Memory

A reproducible explanation of pixel buffers, browser limits and why local processing still needs conservative batch sizes.

Last checked September 22, 2026

Compressed bytes are not decoded memory

A JPG may occupy only a few megabytes on disk while expanding into millions of pixels in memory. The browser needs decoded data to draw a canvas, create a thumbnail and encode a new result.

The Image Prep tool limits files to 24 megapixels, 20 MB per input, 20 files and 100 MB total input. The limits reduce risk; they cannot guarantee a successful run on every phone or low-memory device.

A safer batch routine

  1. Test one landscape and one portrait image first.
  2. Process smaller batches when the device becomes slow.
  3. Reduce output dimensions before assuming a format change will solve memory pressure.
  4. Keep originals outside the browser and inspect every downloaded result.

Sources checked