How to Make a PNG Smaller Without Losing Transparency

Shrink a transparent PNG without adding a white background. Use lossless compression, resize oversized art, and check soft edges before any web upload.

Compression mockup with a checkerboard logo and magnified soft transparent edge
Contents
  1. Compress the PNG in GIMP before using a website
  2. Run lossless compression without flattening the alpha
  3. Resize before compressing when dimensions are oversized
  4. Switch to WebP only when the destination accepts it
  5. Check soft edges on two backgrounds

To make a PNG smaller without losing transparency, resize it to the largest dimensions you actually need, then run lossless PNG compression. Keep the file as PNG when exact pixels matter. For web delivery, WebP can cut more weight while retaining alpha, but check that the destination accepts it.

The checkerboard is not the transparency. It only shows where the alpha channel makes pixels clear. Flattening the image or saving as JPG removes that channel, which can turn clear areas black in some apps. Start with the export settings before reaching for another tool.

Compress the PNG in GIMP before using a website

In GIMP, choose File > Export As, select PNG, and set the compression level to 9. GIMP’s own documentation says this setting is lossless: it takes longer to encode, but it does not lower image quality. Leave alpha enabled. Export a copy so the working file stays untouched.

There is one obscure checkbox worth knowing: Save color values from transparent pixels. Turn it on when another app may use hidden RGB data under fully clear pixels, as game engines and texture workflows sometimes do. For a Shopify logo or a Figma export used only as a picture, those hidden colors usually don’t matter.

GIMP gets this right, but the export dialog is fussy and slow for a one-off file (especially on a phone, where it isn’t an option). It also won’t rescue a 4000-pixel logo that only appears at 400 pixels. Ten times the width means far more pixel data than the layout can show.

Run lossless compression without flattening the alpha

A lossless PNG compressor rewrites filters and compressed data while keeping the file in PNG format. It should not paint a white matte behind the subject. If the result still ends in .png and an image inspector reports RGBA or alpha, the transparency channel survived. Check the edge anyway.

I ran a controlled 1600×1200 TrueColorAlpha graphic through Araluma Compress. The file (built like a typical transparent web asset) fell from 1,289,041 bytes to 43,474 bytes, or 97%, and reached the finished screen in 7.516 seconds in Chromium. Dimensions stayed at 1600×1200.

That’s unusually high. The source had large transparent areas and simple color blocks, which PNG compressors love; a noisy product photo won’t shrink by the same percentage. My downloaded file kept alpha, though soft semitransparent pixels changed slightly after the browser redraw. The white-background composite measured 57.6 dB PSNR against the source, with no visible difference at 100%.

Lossless recompression has a ceiling. Palette tools such as pngquant can go further by reducing millions of possible colors to a smaller indexed set while keeping full alpha transparency. That step is lossy, even though the output still says PNG. It nails flat stickers and simple marks, but gradients can band and tiny color shifts may matter in brand assets. Test one file before processing a folder. No shortcuts.

Close. The catch is: alpha used as a data mask deserves a byte-level workflow, not a browser canvas. For normal logos, stickers, interface art, and product cutouts, visual inspection is the useful test. For shader masks or scientific images, keep the original and use a desktop encoder that promises exact channel preservation.

Resize before compressing when dimensions are oversized

Compression removes inefficient encoding; resizing removes pixels. If a transparent badge is 3000×3000 but the site renders it at 600×600, reducing each dimension to one fifth leaves one twenty-fifth as many pixels. That usually beats another pass through a compressor by a wide margin.

Use the operating system’s image editor when it preserves alpha. In GIMP, choose Image > Scale Image, enter the final width, keep the chain icon locked, and export a new PNG. On macOS, Preview can resize PNG files, but its export controls are thinner and make transparent-edge checks less obvious.

The browser route is an image resizer with an aspect-ratio lock. It handles the arithmetic quickly, but resizing is irreversible: thin type, counter-forms, and one-pixel strokes can turn soft when you go too small. Keep a full-size master beside the upload copy.

For website assets, the order matters. Resize first, compress second, then follow a broader web image workflow for responsive sizes. Compressing a giant source and shrinking it later wastes time because the second export rewrites the file again.

Switch to WebP only when the destination accepts it

WebP supports transparency in both lossless and lossy modes. Google’s Chromium team reported 26% smaller files than PNG across its lossless test corpus, but that number isn’t a promise for your logo. Flat icons may barely move; photographic cutouts with soft shadows often give the encoder more room.

For a website you control, convert PNG to WebP, inspect the result, and keep the PNG as the editing master. WebP is a poor handoff when a marketplace, email builder, or older design tool insists on PNG. Compatibility wins there.

AVIF can go smaller again and retain transparency. The PNG-to-AVIF converter suits modern web delivery, but encoding takes longer and sharp type can show faint fringing. Use the image format guide when you’re choosing a delivery format rather than fixing one upload.

Don’t convert to JPG. It has no alpha channel, so an editor must fill clear pixels with black, white, or another matte color. The technical reason is covered in this transparency guide.

If the file already has a white box, follow this guide before trying to compress the damaged copy.

Check soft edges on two backgrounds

Open the compressed file over white, then over black or deep gray. A clean cutout should keep the same silhouette without a pale fringe, dark halo, stair-stepped curve, or broken drop shadow. Zoom to 100%, not 800%, because the normal display size is what customers on Etsy or Amazon will see.

Also compare the pixel dimensions and file type. A smaller byte count means little if the tool quietly flattened the image or cut the canvas. Quick check: the filename ends in PNG or another alpha-capable format, the dimensions match your target, and the corners remain clear.

For an editable logo, keep PNG and take the lossless saving. For a site asset, test WebP after resizing. Then place the result on a dark card and a white page; if both edges hold up, upload that copy and leave the master alone.