How to Batch Compress & Resize an Entire Image Folder Without Losing Subfolder Structure
Shrink a large image collection without rebuilding its folder tree by hand. This browser-based workflow keeps relative paths in one downloadable ZIP.
Why standard online compressors break multi-folder projects
A folder-based workflow often contains meaningful paths such as Episode_01/page_01.jpg or products/summer/front.png. Uploading files one by one can discard those paths, and some services impose per-batch file or upload-size limits. If two folders contain the same filename, a flattened export can also create collisions.
There is no universal 20-file limit across online compressors; limits vary by service and plan. The practical issue is that a large project can require repeated batches, manual sorting, and careful renaming. A folder-aware export carries relative paths through the processing step and writes them into one ZIP.
A browser tool has no fixed server-side file cap, but images must fit in available memory while they are decoded and processed. Very large batches may slow down or exceed the memory available to the browser.
How to compress nested folders in 3 clicks
Folder selection uses the browser’s directory-upload input (commonly exposed as webkitdirectory) to provide files with relative paths. The images stay local; only the finished ZIP is downloaded.
- Choose a folder. Use the folder picker or drop a directory onto the import area. The queue should show each file’s name and relative folder.
- Pick output settings. Set a maximum size, format, and quality. A maximum width and height are bounds: the image keeps its original aspect ratio and is not cropped to fill the box.
- Compress and download. Review the queue, then create one ZIP. Check the folders and a few images before replacing or sharing your originals.
For example, an input at Episode_01/page_01.jpg remains under Episode_01/ in the ZIP. When converting formats, the tool changes the extension to match the encoded output (for example, page_01.webp).
Drop your folder into the free CreaPocket Batch Image Compressor — 100% local, structure preserved.
WebP vs. JPEG vs. PNG compression
There is no fixed compression ratio for an image format. Savings depend on image content, dimensions, encoder quality, and the original file. Flat illustrations, photographs, and transparent graphics respond differently, so compare the actual exports.
| Format | Typical use | Transparency | What to expect |
|---|---|---|---|
| WebP | Web delivery and mixed artwork | Yes | Lossy and lossless modes are supported; lossy WebP can be smaller, but the result varies by image and quality setting. |
| JPEG | Photos and shaded images | No | Lossy compression. Re-encoding may soften detail or add artifacts; transparent pixels are filled with white. |
| PNG | Line art, text, and transparency | Yes | Lossless pixel encoding. It may remain large; converting to PNG does not guarantee smaller files. |
JPEG and lossy WebP discard image information. Export from originals rather than repeatedly recompressing already-compressed files, and inspect fine text and edges at 100% zoom.
Batch folder compression FAQ
Is there a maximum number of images?
CreaPocket does not impose a fixed image-count cap. Practical batch size depends on each image’s dimensions and your browser’s available memory. If processing becomes slow, split the folder into smaller batches.
Will nested folder names stay in the ZIP?
Yes. Folder selection and supported directory drops retain relative paths, so files remain in their original subfolders. Individual files added without a folder path are placed at the archive root.
Does 84% quality mean an image becomes 84% of its original size?
No. It is an encoder quality setting for JPEG or lossy WebP, not a promised file-size ratio. The output can be smaller or larger depending on the source and settings. PNG ignores this slider.
Are my images uploaded to a server?
No. Decoding, resizing, format conversion, and ZIP creation run in your browser. The page loads the ZIP library, but your selected image files are not sent to CreaPocket.