Tools

Bulk image compression:
a workflow for designers and bloggers

If you're handling dozens of images at once, a manual approach won't cut it. Here's the exact bulk compression workflow that saves hours every week.

By TingJPG Team

Compressing one image takes thirty seconds. Compressing fifty images one by one takes thirty minutes — and that's thirty minutes you could spend designing, writing, or doing literally anything else.

If you work with images regularly, bulk compression isn't a nice-to-have. It's an essential part of your workflow. This guide walks through exactly how designers and bloggers can compress entire batches of images in one go, without sacrificing quality and without wasting time.


Who this guide is for

🎨

Designers

Delivering client assets, exporting UI mockups, preparing icon sets, or handing off web-ready images for development.

✍️

Bloggers

Publishing photo-heavy posts, managing a recipe or travel blog, or uploading product images to an online store.

🛒

eCommerce owners

Uploading entire product catalogues, seasonal lookbooks, or updating hundreds of listing photos at once.

📸

Photographers

Delivering web galleries, portfolio updates, or client proofing galleries where every image needs to be web-ready.

Whether you're dealing with ten images or five hundred, the principle is the same: compressing one at a time is a bottleneck. A bulk workflow eliminates it.


The problem with one-at-a-time compression

Most people discover image compression the hard way — their site is slow, Google PageSpeed flags it, and they start compressing images manually. That works for a while. But once you're regularly publishing content or delivering client work, the cracks start to show.

Here's what manual, one-at-a-time compression costs you:

ScenarioImagesManual timeBulk time
Weekly blog post8–12 images~8 minutes~1 minute
Product catalogue update50–100 images~45 minutes~3 minutes
Client design handoff20–40 assets~25 minutes~2 minutes
Photo gallery upload100–200 images~2 hours~5 minutes

The time savings compound quickly. A blogger publishing three posts a week saves nearly an hour every week — over 50 hours a year — just by switching to bulk compression.

The bulk compression workflow with TingJPG

TingJPG supports multi-file upload, which means you can compress an entire batch of images in a single session. Here's the exact workflow:

1

Prepare and sort your images

Before uploading, sort your images into folders by type — photos (JPG), graphics and logos (PNG), icons (SVG). This matters because the ideal compression setting differs slightly between photos and flat graphics. Keeping them separate lets you optimise each batch correctly.

2

Rename files before uploading

This is the step most people skip, but it matters for SEO. Rename files from IMG_4823.jpg to something descriptive like minimalist-home-office-desk-setup.jpg. Google reads file names, and descriptive names reinforce your page's keywords. Batch rename tools like Bulk Rename Utility (Windows) or Automator (Mac) can rename hundreds of files in seconds.

3

Upload the entire batch to TingJPG

Go to TingJPG.com and drag your entire folder of images onto the upload area, or click to select all files at once. TingJPG processes every image in parallel — so compressing 50 images takes roughly the same time as compressing 5.

4

Set the right quality level for your use case

The default quality setting works well for most situations. For web images, a setting of 70–80% delivers the best balance. If you're compressing images for print or large-format display, keep quality higher (85–90%). For small thumbnails or social media previews, you can go lower (60–70%) without any visible impact.

5

Download all and spot-check

Click "Download All" to get your compressed images as a zip file. Before uploading to your site, quickly open 3–4 images at full size and compare with the originals. Pay attention to edges, text, and fine details. If everything looks identical, you're done.

💡 Pro tip: Keep a folder called /originals where you always store the uncompressed source files. Never throw these away. If you ever need to recompress at a different quality setting, or the compressed version gets corrupted, you always have a clean original to go back to.

Workflow for designers: delivering client assets

When delivering web assets to a client or developer, every image you hand off should already be compressed and web-ready. Here's a clean handoff workflow:

Designer handoff checklist

  • Export at 2x resolution from your design tool (Figma, Sketch, Adobe XD) for retina displays
  • Save JPG for photos, PNG for elements with transparency, SVG for icons and logos
  • Rename all files descriptively using hyphens (no spaces, no underscores)
  • Upload the full batch to TingJPG and compress
  • Spot-check 5–10 images at full size before delivering
  • Deliver a zip of compressed files alongside a reference sheet listing file names, dimensions, and intended use

Delivering pre-compressed images signals professionalism. Developers don't have to guess whether assets are optimised, and clients get a faster site from day one.

Workflow for bloggers: publishing a new post

A typical blog post with photos has 6–15 images. Running this workflow before every publish takes under five minutes and keeps your site fast as it grows.

Blogger pre-publish checklist

  • Collect all images for the post into one folder
  • Resize images to max 1200px wide before compressing — there's no need for 4000px images on a blog
  • Rename files to match your post's keywords (e.g. sourdough-bread-recipe-step-3.jpg)
  • Upload all images to TingJPG and bulk compress
  • Upload compressed images to your CMS and fill in alt text for every single one
  • Run a quick PageSpeed Insights check after publishing to confirm load times are green
Why resize before compressing? Compression reduces file size, but it doesn't change image dimensions. A 4000px wide photo compressed to 80% quality is still a 4000px wide photo — just smaller in bytes. Resizing to 1200px first, then compressing, gives you the maximum file size reduction with no visible quality difference on screen.

How much can you actually save?

Here's a real-world example. A travel blogger uploads 12 photos per post, publishing twice a week:

Without compressionWith TingJPG bulk
Avg. image size3.2 MB420 KB
Images per post1212
Total per post38.4 MB5 MB
Per month (8 posts)307 MB40 MB
Page load impact8–12 seconds1–2 seconds

That's not just a faster website — it's lower hosting bandwidth, better Google rankings, and a dramatically improved experience for readers on mobile connections.


Quick recap

  • Manual one-at-a-time compression is a bottleneck — bulk compression eliminates it
  • Sort images by type before uploading so you can apply the right quality settings
  • Rename files descriptively before compressing — it helps SEO and keeps assets organised
  • Resize images to their display dimensions before compressing for maximum size reduction
  • Always keep your originals in a separate folder — never throw away uncompressed source files
  • TingJPG's multi-upload lets you compress an entire batch in one session, for free

Start compressing in bulk — free

No signup, no watermarks. Upload your entire image batch and download optimised files in seconds.

Try TingJPG free →
Bulk compression Image workflow Designers Bloggers Web performance TingJPG