How Can I Reduce Image File Size? A Practical Guide

Key takeaways

• Resize images to their display dimensions first; dropping a 4000px photo to 1200px cuts file size by roughly 80-90% before any compression.
• Re-save JPEGs at quality 75-85 from the original file, and never re-save a JPEG repeatedly because each pass degrades it.
• Reduce PNG palettes to 256 colors or fewer, or convert photographic PNGs to JPEG or WebP for 70-90% savings.
• Strip EXIF and metadata with ImageMagick's -strip flag to save 50-200 KB per image and remove location data.
• OS tools scale to a handful of files; WordPress libraries with hundreds of images need in-place plugin compression and cleanup.

You can cut most image files by 30–80% without installing anything: recompress JPEGs at quality 70–80, strip PNGs down with palette reduction, and convert photos to WebP when the destination supports it. This guide walks through the exact steps on Windows, Mac, and Ubuntu, format by format, then covers the one case where manual tools stop scaling: a WordPress media library with hundreds of files.

How can I reduce image file size without installing software?

Yes. Windows, Mac, and Ubuntu all ship with tools that handle the two things that actually shrink an image: its dimensions and its compression quality. Resize a 4000px photo to 1200px and you cut file size by roughly 80-90% before touching quality settings.

The two levers: dimensions and compression quality

Dimensions are the big lever. A 4000×3000 photo displayed in a 800px content column carries 15× more pixels than it needs, and every one of them costs bytes. Cut pixels first, then compress.

Compression quality is the second lever. Re-saving a JPEG at quality 80 instead of 95 typically halves the file with no visible difference at web sizes. Windows Photos, macOS Preview, and Ubuntu's Image Viewer all expose these controls.

For format choice, WebP is worth knowing: Google's guidance on image formats covers how it compares to JPEG and PNG. If you also need files renamed to match, see the Media File Renamer comparison.

How do I reduce image file size on Windows?

Windows ships with two tools that cover most one-off jobs: Photos for resizing, and Paint for re-saving a PNG as a JPEG.

Resize with the Photos app

Open the image in Photos, click the three-dot menu, and choose Resize image. Pick a preset or enter custom pixel dimensions, then save. Dropping a 4000px photo to 1600px typically cuts the file by 70-80% because you are discarding pixels, not compressing harder. Quality stays untouched, so this is the right move when you want the same JPEG format at a smaller canvas.

Compress a PNG with Paint and save as JPEG

Paint handles the other case: a screenshot or graphic saved as PNG that bloats to megabytes. Open it in Paint, use Resize if needed, then File > Save As > JPEG photo. JPEG compression flattens flat-color areas, so expect visible artifacts around text and sharp edges. For screenshots with text, keep the PNG and resize instead.

These workflows are fine for a handful of files. Bulk libraries need a different approach, which we cover later, and if you are weighing plugins, the comparison breaks down the options.

How do I reduce image file size on Mac?

Resize and convert with Preview

Preview is the built-in answer for a single image. Open the file, press Command+A to select everything if needed, then choose Tools > Adjust Size and enter your target width, for example 1600px for a blog hero. To shrink a PNG, use File > Export and pick JPEG as the format, then drag the quality slider down until the preview shows an acceptable size. This handles the JPEG and PNG workflows in one tool, with no download required.

Batch-resize multiple images at once

Preview also handles batches. Select multiple files in Finder, open them all in one Preview window, select all thumbnails in the sidebar, then run Tools > Adjust Size once and it applies to every open image. Export the selection back to the same folder and you have resized copies of the whole set. For deeper compression on JPEGs after resizing, a CLI tool like jpegoptim gives you explicit quality flags instead of a slider, per its official documentation.

Where this breaks down is a WordPress media library with thousands of files, duplicates, and unused media. If that is your situation, a plugin approach like FoldRocket vs FileBird covers the bulk-cleanup case that OS tools cannot.

How do I reduce image file size in Ubuntu?

Ubuntu gives you both a terminal and a GUI route, and the terminal is faster for batches.

jpegoptim for JPEGs

Install with sudo apt install jpegoptim, then run jpegoptim --strip-all --max=85 image.jpg to cap quality at 85 while stripping metadata. For a folder, jpegoptim --strip-all --max=85 *.jpg handles everything in one pass. Files are overwritten in place, so work on a copy first.

optipng and pngquant for PNGs

sudo apt install optipng pngquant gets you both. optipng -o2 image.png is lossless and safe anywhere; pngquant --quality=65-80 image.png is lossy, often cuts file size by 60-70%, and can produce an indexed-color PNG some tools handle oddly. Use pngquant for web images, optipng when you cannot accept any pixel change.

ImageMagick convert for both

sudo apt install imagemagick, then convert image.jpg -quality 82 image.jpg or convert image.png -strip image.png. One tool covers both formats and resizing, which is why many scripts lean on it.

These commands work per-file or per-folder, but they never touch WordPress: uploads stay untouched in the library, no ALT text gets written, and nothing is renamed. For a comparison of how a WordPress plugin handles this in-place, see https://foldrocket.com/comparison/imagify/.

How do I reduce the file size of a JPEG image?

Quality settings that work in practice

Quality 75-85 is the sweet spot for most photos. Below 70 you start seeing blocking around sharp edges; above 85 you pay double the file size for detail you cannot see at normal viewing sizes. In Preview on Mac, export at 80% and compare. In GIMP or ImageMagick on Ubuntu, use -quality 80. One pass only: re-saving a JPEG repeatedly degrades it, so always work from the original.

Strip metadata and EXIF data

Camera EXIF, GPS coordinates, and editing history can add 50-200 KB per image with zero visual benefit. ImageMagick's -strip flag removes it in one command, and both Windows Photo Editor and Preview can drop it on export. If you run client sites, stripping also removes location data you may not want published. For PNG work later, pngquant's CLI flags are documented at pngquant.org. For bulk WordPress libraries, cleanup tools handle this server-side; check what data processing you agree to at FoldRocket's terms.

How do I reduce the file size of a PNG image?

PNGs are huge because they store every pixel losslessly, usually in 24-bit color. A screenshot that uses only a handful of colors still pays for millions of them. That gap is where the savings live.

Reduce colors or use lossy PNG compression

Cut the palette first. Most screenshots and flat graphics look identical at 256 colors or fewer, and dropping from 24-bit to 8-bit often halves the file. On Windows, Mac, and Ubuntu, ImageMagick does this in one command: magick input.png -colors 256 output.png. For lossy quantization on top, tools like pngquant or the -strip flag remove metadata and near-duplicate colors with no visible difference on UI captures.

When to convert a PNG to JPEG or WebP instead

If the PNG is a photograph, it is the wrong format. Save photos as JPEG at quality 75-80 and you will typically cut 70-90% of the size. For anything going on the web, WebP handles both photos and flat graphics and beats PNG on nearly every realistic image. Keep PNG only where you need transparency or pixel-perfect text.

Should I convert to a different format to reduce image file size?

Sometimes. Re-compressing the same format only gets you so far; switching format can cut file size far more, but only when the format matches the image type.

Decision rules:

• PNG with few colors (logos, screenshots, flat graphics): keep it PNG and reduce colors. Converting to JPEG adds artifacts around hard edges.
• JPEG photos: stay JPEG and lower quality. WebP saves more, but only if you can serve it everywhere your audience needs it.
• Anything photographic where you control delivery: WebP usually wins. Convert with ImageMagick's convert and -quality flags, which control compression per format (ImageMagick documentation).

A quick test: convert one representative file each way, compare sizes at similar visual quality, then batch the winner. Format choice is per-image, not per-site.

When do OS tools stop being enough for a WordPress media library?

Manual compression works until you have a few hundred images. Past that, dragging files through Preview or ImageMagick one batch at a time costs more hours than a plugin license, and it does nothing about the real problem: a junk drawer of unused media, duplicates, and renamed files that no OS tool can see.

FoldRocket runs that whole workflow inside the library. You scan for unused files and duplicates, delete them in bulk, organize what remains with virtual folders, rename files for SEO, and compress on the way through. For agencies, staging sites do not consume seats, so you can hand over cleaner sites on every client build without watching your budget. Pricing starts at €79 for freelancers, per foldrocket.com.

The honest limits of FoldRocket for compression

It is not an image optimizer in the ShortPixel or Imagify sense. There is no CDN delivery, no automatic WebP conversion pipeline, and the AI features are optional, not the core. If your only goal is shaving kilobytes off every upload automatically, a dedicated optimizer plugin does that job with less overhead.

What cleanup adds that compression alone does not

Compression shrinks files; cleanup shrinks the library. Removing 3,000 unused images does more for backup size, search speed, and maintenance sanity than any percentage saved on the remaining ones. The two together are what make a media library usable again.

FAQ

How do you reduce image file size without losing quality?

Use lossless tools first: strip metadata with ImageMagick's -strip flag, run optipng on PNGs, and resize to the dimensions you actually display. Lossless steps alone often save 10-30%. If you need more, re-save JPEGs at quality 80 from the original file, which is visually indistinguishable at web sizes.

What is a reasonable file size for a web image?

Aim for under 100 KB for a standard blog image and under 300 KB for a full-width hero. A 1200px-wide JPEG at quality 80 typically lands in that range. Anything over 500 KB usually means oversized dimensions, the wrong format, or quality set too high. Reduced-color PNG screenshots often stay under 50 KB.

Does resizing an image reduce its file size or just its dimensions?

Resizing reduces both. Fewer pixels means fewer bytes, so dropping a 4000px photo to 1200px cuts file size by roughly 80-90% even before touching compression. Dimensions and file size are linked; you cannot shrink one without the other. Compression quality is the separate second lever you apply after resizing.

Can I compress images already uploaded to WordPress, or do I need to re-upload them?

You can compress them in place. A plugin like FoldRocket works on the existing library, compressing files where they sit while also scanning for unused images and duplicates. Manual routes also work: download, compress with your OS tools, and re-upload, though that risks broken URLs unless you overwrite the same filename.