When a shared setting helps
Use a group when product photos, screenshots, or other images need the same operation. Add files, choose the settings once, and check both portrait and landscape results.
Process photos separately when each needs its own crop, background, or quality choice. Applying one setting to all files does not mean the outputs will have identical dimensions or sizes.
Why large images need more memory
A compressed file can expand substantially when decoded. A 4000×3000 image held as RGBA uses about 48 million bytes for one pixel buffer. Fifty such buffers alone would use roughly 2.4 GB in decimal units, before additional working memory.
Devices with 4 GB of RAM cannot devote all of it to a browser tool. Filecozy limits concurrent work and estimates memory use instead of decoding the whole group at once. Device and browser resources still affect speed.
Background work and downloads
Web Workers let supported processing run away from the main interface thread. This helps responsiveness but does not guarantee a particular frame rate or completion time. The selected image files are processed locally.
Filecozy accepts up to 50 images, 25 MiB per file, and 100 MiB per group. It also enforces a 40-megapixel limit. Review completed results and download them individually or create a ZIP. Temporary preview URLs are released when no longer needed, not while an active preview still uses them.