If you publish regularly — a blog, a product gallery, a portfolio — you're not compressing one photo, you're compressing a folder of them, over and over, the same way each time. Here's a batch workflow that turns that into a two-minute habit instead of a chore.
Processing a whole folder at once
Quick answerSelect or drag in every photo for the post at once. The tool applies the same format, quality, and resize settings to each one, shows a per-image before/after size, and lets you grab everything together as a single ZIP instead of clicking Download a dozen times.
A typical illustrated blog post might use anywhere from five to twenty images — a hero photo, a few inline screenshots, a gallery. Compressing them one at a time in separate tabs or apps is slow and easy to get inconsistent (one image ends up at quality 90, another at quality 60, and the page looks uneven). Doing it as a batch keeps every image in the post on the same settings.
Drop all the files for the post into the drop zone in one action, or use choose from your computer and multi-select them. Each file appears as its own row with a live progress bar, its own before/after size and percentage reduction, and its own Download link, so you can still fix one outlier image individually if it needs a different quality without touching the rest of the batch.
Saving your settings so you never re-type them
Quick answerConfigure format, quality, and resize once, name it in My saved presets (for example "Blog thumbnail"), and click Save preset. It's stored locally in your browser and reapplies with a single click next time — no re-typing width, height, or quality.
If your blog always uses, say, WebP at quality 78, resized to a maximum width of 1400 pixels for inline images, typing those three values in every time you sit down to write a post adds friction that eventually gets skipped — which is how unoptimized, oversized images end up published anyway.
A saved preset removes that friction. Once saved, it shows up as a chip you can click to instantly reapply that exact combination of format, quality, resize mode, and target size or percentage. You can save more than one — a "Blog thumbnail" preset alongside a "Gallery full-size" preset, for instance — and switch between them per image type. Everything is stored via your browser's localStorage, so nothing is sent anywhere and the presets stay on the device you saved them on.
Why this matters for page speed
Unoptimized images are one of the most common causes of a slow-loading blog post. A consistent, pre-set compression habit means every image you publish is already sized and compressed correctly by the time it reaches your CMS — instead of relying on a plugin to fix it after upload.
Quick answerTurn on Export as WebP + JPEG + PNG together before downloading the ZIP, and every image in the batch is included in all three formats in a single pass — useful when your CMS theme wants a modern format plus a fallback.
Many themes serve a WebP image with a JPEG `<picture>` fallback for older browsers, or a plugin expects a specific format for a particular placement (a featured image, an og:image, a thumbnail). Rather than re-uploading the same batch three times with the format dropdown changed each time, the multi-format toggle produces all three outputs for every image in one ZIP download.
- WebP: the primary, smallest-file version for modern browsers.
- JPEG: a compatible fallback, or for systems that specifically require .jpg.
- PNG: a lossless copy, useful for graphics or anywhere transparency needs to survive.
Example (illustrative): a batch of eight gallery photos, compressed with multi-format export on, might produce a ZIP with 24 files — eight WebP, eight JPEG, eight PNG — organized so you can pick whichever format each placement on your site actually needs, without reprocessing.
Picking a sensible width for a content column
Quick answerMatch the maximum width to where the image will actually display — roughly 1200–1600px is typically enough for a blog content column, while a full-bleed hero banner may need more. Anything wider than the space it occupies just adds file weight with no visible gain.
It's common to upload a photo straight from a 12+ megapixel camera or phone (often 4000 pixels or wider) into a blog post that displays images at maybe 700-900 pixels wide on screen. The browser will scale that down visually, but the visitor still downloads the full, oversized file — that's wasted bandwidth and slower page loads for no visual benefit.
The social media size chips can help for specific placements too: they fit an image to a named platform size (for example a common Instagram or Facebook dimension) without cropping, only shrinking to fit — handy if the same photo is also being shared to social alongside the blog post.
Rough starting widths by placement (adjust to your actual theme layout)
| Placement | Suggested max width |
|---|
| Inline blog content image | 1200–1600px |
| Thumbnail / card preview | 400–600px |
| Full-bleed hero banner | 1920–2400px |
| Social share image | use a social size preset |
💡 Habit to build: resize once to the placement's real display width, save that as a preset per image type, then reuse the preset every time you publish — consistency matters more than any single perfect setting.
Frequently asked questions
Can I compress an entire folder of blog photos in one go?
Yes. Drop multiple files into the drop zone at once, or select them all when choosing from your computer. Every image is processed with the same format, quality, and resize settings, listed individually with its own before/after size, and can be downloaded one by one or together as a single ZIP file.
How do I reuse the exact same compression settings for every new blog post?
Set the format, quality, and resize options the way you want once, type a name like Blog thumbnail into My saved presets, and click Save preset. It is stored locally in your browser via localStorage, so on your next post you just click that saved preset to reapply the same combination instantly, without retyping anything.
Why would I export the same batch as WebP, JPEG, and PNG together?
Some CMS themes serve WebP with a JPEG fallback for older browsers, and some plugins expect PNG for specific placements like featured images with transparency. Turning on the multi-format export toggle before downloading the ZIP produces all three formats for every image in the batch in one pass, instead of reprocessing the same files three times.
What image width should I use for blog post photos?
For most blog content columns, resizing to a maximum width of roughly 1200 to 1600 pixels is generally more than enough for sharp display, since the photo is rarely shown larger than the article's content width even on large screens. Going wider than the space it will actually occupy on the page mainly adds file weight without a visible benefit.
Do the social media size presets crop my images?
No. The social media size chips fit the image inside the selected platform's dimensions while keeping the aspect ratio and only shrinking, so the full image is preserved rather than being cropped to fill the frame. If your source photo has a different ratio than the target, some empty space in that dimension is simply not filled rather than cutting content.
Batch-compress your gallery now
Multi-file processing, saved presets, and multi-format ZIP export — free, and nothing ever leaves your browser.
Try the free Image Compressor →
A note on the numbers above: file counts, sizes, and width suggestions in this guide are illustrative approximations, not guaranteed results — actual output depends on your specific images and theme layout. Use the tool's live before/after preview to confirm exact sizes for your files. This guide is informational and not a substitute for your CMS or theme's specific image requirements.