How-to guide
How to Batch Compress Multiple Images at Once
To batch compress multiple images, standardize the output format first — WebP for web and social media, JPEG for email — resize all images to display dimensions, then compress the entire batch at quality 80 with EXIF data stripping enabled. This workflow produces files 60–75% smaller file size than the originals with no visible quality loss.
Free image compressor — no account required
No account · Files deleted within 15 minutes · EXIF data removed
Why batch workflow matters — platform double-compression
Every major platform that hosts images — Instagram, TikTok, LinkedIn, Shopify, WordPress — runs its own compression pass when you upload. You have no control over that pass: the platform chooses the quality setting, the format, and the output dimensions.
What you control is the quality of the source image you provide. This is where double compression becomes critical. If you upload a source image that is already heavily compressed — quality 60 or below — the platform's compression pass amplifies the existing artifacts. Block patterns become visible. Gradients step. Text in images softens noticeably.
If you upload a source image at quality 80–85 from the correct pixel dimensions, the platform's single compression pass produces clean output. Starting from a well-compressed source consistently produces better delivered images than starting from an over-compressed or under-compressed one.
This is why the batch workflow is not just about meeting file size limits — it is about controlling the quality of what your audience actually sees.
Choosing the right format for your batch
The format decision determines everything that follows. Make it before uploading any files.
WebP — the right choice for:
- Website images (blogs, product pages, landing pages)
- Social media uploads (Instagram, LinkedIn, TikTok, Pinterest — all accept WebP in 2026)
- Any digital destination where the browser or platform is known to support WebP
JPEG — the right choice for:
- Email attachments
- Print files
- Images going to systems where WebP support cannot be confirmed (legacy CMS, older plugins)
- Windows desktop sharing where the recipient opens files in a standard photo viewer
PNG lossless — the right choice for:
- Logos, icons, and graphics with transparent backgrounds
- Screenshots where sharp text must be preserved
For most web and social batches in 2026, WebP is the correct default. Process email batches separately as JPEG.
Why resizing before compressing is non-negotiable
This is the single most common mistake in batch image workflows: compressing at camera resolution and expecting file sizes to reach web targets.
A standard iPhone 16 photo: 4032×3024 px, approximately 5–6 MB as JPEG. Compressed at quality 80 without resizing: approximately 2–3 MB — still too large for web delivery and too large for most email attachment budgets.
The same photo resized to 1920 px wide: approximately 1.5 MB JPEG. Compressed at quality 80 WebP: approximately 280–420 KB — within web delivery targets.
Resize is not optional prep — it is the primary size reduction. Lossy compression amplifies what resize achieves. Pictuary applies proportional scaling automatically when you enter a width with height left blank — the aspect ratio is always preserved.
Consistent quality settings across a batch
Consistency matters for visual coherence in a batch — especially for product photography or portfolio images that appear side by side. Varying quality settings produces images that look different from each other at the same displayed size.
| Use case | Recommended quality | Expected file size (1920 px wide) |
|---|---|---|
| Web images, social media | 80 (WebP) | 280–480 KB |
| Images with text overlays | 85 (WebP) | 400–650 KB |
| Email attachments | 75 (JPEG) | 200–400 KB |
| Thumbnails and previews | 75 (WebP) | 100–200 KB |
| Print-quality delivery | 90 (JPEG) | 800 KB–1.5 MB |
EXIF data and batch workflows
Camera photos contain EXIF metadata — GPS coordinates, camera model, shooting settings. In a batch of event or product photography, this metadata adds 30–200 KB per file and includes location data you may not want distributed with the images.
Pictuary strips all EXIF data from every processed image automatically. In a batch of 20 event photos, this removes 600 KB–4 MB of metadata from the combined output — a meaningful addition to overall size reduction.
Batch size and server limits
Pictuary processes images individually. For large batches — 50+ images — process in groups of 10–20 to maintain a clear workflow and avoid losing track of which images have been processed.
Expected output from a typical product photography batch
| Batch | Original (camera JPEG) | After resize + compress (WebP 80) | Reduction |
|---|---|---|---|
| 10 product photos at 1920 px | ~50 MB | ~3–5 MB | ~90% |
| 20 event photos at 1920 px | ~100 MB | ~6–10 MB | ~91% |
| 5 hero images at 1920 px | ~25 MB | ~1.5–2.5 MB | ~90% |
Step by step
Decide on your output format
Before uploading anything, choose your target format. WebP for web and social media — 97% browser support in 2026, 25–35% smaller than JPEG at equivalent quality. JPEG for email — the safest choice for attachments and any destination where WebP support cannot be confirmed. PNG lossless for images with transparency. Standardizing the format across a batch before uploading saves rework.
WebP — A modern image format developed by Google that supports both lossy and lossless compression, full transparency, and produces files 25–35% smaller than JPEG at equivalent visual quality. Browser support reached 97% globally in 2026. WebP is the recommended format for web and social media images. See full definition →Resize all images to display dimensions first
Go to pictuary.com/resize and process each image before compressing. Set width to 1920 px for full-width images, 1200 px for blog or product content, or your specific display width. Resizing eliminates surplus pixels that compression alone cannot remove — it is the most impactful step for reducing file size in a batch workflow. Pictuary uses proportional scaling automatically when you enter a width with height left blank. Download each resized file before moving to compression.
Pixel dimensions — The width and height of an image measured in pixels. Resizing to display dimensions before compressing removes unnecessary pixels and produces significantly smaller output than compressing at the original camera resolution. See full definition →Upload your batch to the Compress tool
Go to pictuary.com/compress. Upload your resized images. Pictuary accepts JPEG, PNG, WebP, and HEIC files. No account is required.
Set consistent quality across the batch
Apply a single quality setting to the entire batch. Use quality 80 for most batches — this is the standard web and social media setting that produces imperceptible quality loss with 50–65% file size reduction. Use quality 85 if the batch includes images with text overlays or sharp geometric edges, where quality 80 begins to introduce subtle softening. Use quality 75 for thumbnails or previews where file size is the priority.
Download all compressed images
Click Compress & Download for each image. EXIF data is stripped from all files automatically. Filenames are preserved. Files are deleted from Pictuary's servers within 15 minutes.