Table of Contents
- 1.Why You Need a Batch Image Workflow
- 2.The Universal Dimensions Cheat Sheet
- 3.Step 1: Organize Your Source Files
- 4.Step 2: Resize All Images to Platform-Specific Sizes
- 5.Step 3: Compress for Target File Size
- 6.Step 4: Convert to the Right Format
- 7.Step 5: Strip EXIF Metadata
- 8.Step 6: Rename Files for SEO and Organization
- 9.Common Batch Processing Mistakes to Avoid
- 10.Automation Tips for Power Users
1. Why You Need a Batch Image Workflow
If you manage a website, run an online store, or post regularly on social media, you probably process dozens of images per week. Doing this one by one is not just slow — it is error-prone. Inconsistent dimensions, forgotten compression, and leftover EXIF data are all symptoms of a missing workflow.
A proper batch workflow gives you three things: speed, consistency, and quality. Speed because you process 50 images in the time it used to take for 5. Consistency because every image follows the same rules. Quality because you never forget the compression or metadata step.
The workflow described here uses entirely browser-based tools. No Photoshop license, no ImageMagick installation, no command line. Everything happens in your browser, which means it works on any computer — including Chromebooks and tablets.
2. The Universal Dimensions Cheat Sheet
Before you start resizing, you need to know your target dimensions. Here is the definitive cheat sheet for 2026:
| Platform / Use Case | Dimensions | Aspect Ratio | Max File Size |
|---|---|---|---|
| Instagram Feed | 1080 × 1080px | 1:1 | 30 MB |
| Instagram Story | 1080 × 1920px | 9:16 | 30 MB |
| Instagram Reels | 1080 × 1920px | 9:16 | 4 GB |
| Facebook Post | 1200 × 630px | 1.91:1 | 8 MB |
| Facebook Cover | 820 × 312px | 2.63:1 | 100 KB |
| Twitter / X Post | 1200 × 675px | 16:9 | 5 MB |
| LinkedIn Post | 1200 × 627px | 1.91:1 | 100 MB |
| Pinterest Pin | 1000 × 1500px | 2:3 | 20 MB |
| TikTok Video Cover | 1080 × 1920px | 9:16 | No limit |
| YouTube Thumbnail | 1280 × 720px | 16:9 | 2 MB |
| Amazon Product | 2000 × 2000px | 1:1 | 10 MB |
| Shopify Product | 2048 × 2048px | 1:1 | 20 MB |
| Etsy Product | 2000 × 2000px | 1:1 | 1 MB |
| Website Hero | 1920 × 1080px | 16:9 | Under 300 KB |
| Blog Post Featured | 1200 × 630px | 1.91:1 | Under 200 KB |
| Email Header | 600 × 300px | 2:1 | Under 100 KB |
| Email Signature | 400 × 100px | 4:1 | Under 50 KB |
Platform limits change occasionally. Always verify current requirements before finalizing a campaign.
3. Step 1: Organize Your Source Files
Before touching any tool, organize your files. Create a folder structure that matches your workflow:
/batch-processing-may-2026/ /01-source/ ← Original files (never modify these) /02-resized/ ← After resizing /03-compressed/ ← After compression /04-final/ ← After format conversion and metadata removal /05-archive/ ← Zip of final files for backup
The golden rule: never modify your source files. Always work on copies. This way, if you make a mistake — wrong dimensions, over-compression, wrong format — you can start over without losing the original.
Pro tip: If your source images are scattered across folders, use your operating system's search to collect them first. On Windows, search *.jpg or *.png in your Pictures folder. On Mac, use Spotlight. Copy all results into your 01-source folder.
4. Step 2: Resize All Images to Platform-Specific Sizes
Resizing before compression is critical. Compressing a 4000×3000px image to 80% quality still produces a huge file. Resizing to display dimensions first, then compressing, is the correct order.
Using PixelTools Image Resizer:
Open the Image Resizer tool in your browser.
Upload all images from your /01-source/ folder. You can select multiple files with Ctrl+A or Cmd+A.
Set your target dimensions. For Instagram feed posts, enter 1080 × 1080. Enable 'Maintain aspect ratio' to prevent distortion.
Choose the resize mode: 'Fit within' keeps the entire image visible with letterboxing if needed. 'Crop to fill' fills the entire frame by cropping edges. 'Stretch' distorts the image to fit — avoid this.
Download all resized images. They will save to your default download folder. Move them to /02-resized/.
Why resize first? A 4000×3000px JPEG at 80% quality is roughly 2.5MB. The same image resized to 1080×1080px is about 180KB before any quality reduction. Resizing is the single most impactful step in file size reduction.
5. Step 3: Compress for Target File Size
After resizing, compress each image to hit your target file size. Different platforms and use cases have different targets:
Website images
Under 200 KB
Quality: 75–80%
Social media
Under 500 KB
Quality: 82–85%
Email images
Under 100 KB
Quality: 70–75%
Using PixelTools Image Compressor:
Open the Image Compressor tool.
Upload all resized images from /02-resized/.
Set the quality slider to your target (80% for web, 85% for social media).
Review the file size reduction shown for each image. If an image is still too large, lower the quality by 5% and re-compress.
Download compressed images and move them to /03-compressed/.
6. Step 4: Convert to the Right Format
Not all platforms accept all formats. Here is when to convert:
- For websites: Convert to WEBP if your CMS or CDN supports it. Use JPG to WEBP Converter for batch conversion. Keep JPEG as a fallback for older browsers.
- For social media: Most platforms prefer JPEG. Do not upload WEBP or AVIF to Instagram or Facebook — they will re-encode it and may handle it poorly.
- For email: JPEG only. Email clients do not reliably support WEBP or AVIF.
- For print preparation: Keep PNG or TIFF. Lossy compression is not suitable for print.
7. Step 5: Strip EXIF Metadata
Before publishing any image online, remove its EXIF metadata. This data includes GPS coordinates, camera model, date taken, and potentially your name or copyright info. It also adds 5–100KB to your file size.
Using PixelTools EXIF Remover:
Open the EXIF Remover tool.
Upload all compressed images from /03-compressed/.
Click process for each image. The tool strips all metadata instantly in your browser.
Download clean images and move them to /04-final/.
Privacy warning: If you have ever posted photos online without removing EXIF data, your home address may be publicly accessible. Always strip metadata before sharing photos taken at home, work, or sensitive locations.
8. Step 6: Rename Files for SEO and Organization
Descriptive file names help with Google Image Search rankings and make your files easier to manage. Replace generic names like IMG_4521.jpg with descriptive names:
Bad file names
- IMG_4521.jpg
- photo_final_v3_EDITED.jpg
- 1000012034.jpg
- image (1).png
Good file names
- red-leather-wallet-mens-bifold.jpg
- summer-collection-hero-banner.jpg
- team-photo-office-2026.jpg
- product-demo-screenshot-dashboard.jpg
Use hyphens (not underscores or spaces) between words. Keep names under 60 characters. Include 2–3 relevant keywords if the image is for a website. Do not stuff keywords — buy-cheap-shoes-online-free-shipping-discount.jpg looks spammy to Google.
9. Common Batch Processing Mistakes to Avoid
10. Automation Tips for Power Users
If you process images regularly, these automation strategies will save hours per month:
Use browser bookmarks for your most-used tools
Bookmark PixelTools Image Resizer, Compressor, and EXIF Remover in a folder. Open all three with right-click → 'Open all bookmarks' to start your workflow instantly.
Create template folders
Keep a folder on your desktop called '_IMAGE_TEMPLATE' with empty subfolders (01-source, 02-resized, etc.). Copy this folder and rename it for each new project instead of creating structure from scratch.
Batch rename with your OS
Windows: select files → right-click → Rename → type a base name (e.g., 'product-') and Windows auto-numbers them. Mac: select files → right-click → Rename → Format → Name and Index.
Set up a checklist document
Keep a simple text checklist on your desktop: 1) Resize → 2) Compress → 3) Convert → 4) Strip EXIF → 5) Rename → 6) Upload. Check off each step so you never forget metadata removal again.
Start Your Batch Workflow
Every tool referenced in this article is free and runs in your browser. No install, no account, no upload to servers.