Optimize Images for Web on Windows

Start with the network request, not the design export. A 3000-pixel product photo may look correct in a 640-pixel card because CSS scales it down, but the browser still transfers the large source. The Windows workflow below finds that mismatch, creates sensible variants, and checks the page after deployment.

Find the images that cost the most

Open the page in Microsoft Edge, press F12, select Network, reload, and filter by Img. Sort by transferred size. Record three facts for each expensive request:

1. The file’s pixel dimensions.
2. Its rendered width in the Elements panel.
3. Whether it is above the fold or loaded later.

A hero rendered at 1200 pixels may need a 1920 or 2400 pixel source for dense displays. It rarely needs the original 6000-pixel camera export. A card rendered at 360 pixels should not request the same file as the hero.

Resize one image in Paint

Paint is enough to correct a single oversized source:

1. Open the image and choose Resize and skew.
2. Keep Maintain aspect ratio enabled.
3. Enter the required pixel width, not a percentage guessed from file size.
4. Use Save as so the master remains untouched.

For a 640-pixel card, create an 800-pixel standard candidate and a 1280-pixel dense-display candidate. Check small text and thin product edges after resize. If the source contains transparency, do not save it as JPEG.

Batch resize with PowerToys

Microsoft PowerToys includes Image Resizer , which adds resize commands to File Explorer. Define widths that match the site’s real breakpoints, such as 480, 960, and 1600 pixels, then create copies rather than replacing originals.

PowerToys is useful for dimensions, but it is not a complete delivery pipeline. File naming, format conversion, responsive markup, and visual review still matter. Put generated candidates in a separate folder so they are not mistaken for source artwork.

Choose JPEG PNG WebP or AVIF

Asset	Sensible delivery format	Check closely
Product or editorial photo	WebP, AVIF, or JPEG	Texture, gradients, skin tones
Screenshot with small text	PNG or high-quality WebP	Glyph edges and thin lines
Logo or icon	SVG when the source is vector	Correct view box and accessible label
Transparency with soft shadows	WebP or PNG	Halos on light and dark backgrounds

Do not convert every PNG to JPEG. That can remove transparency and create ringing around text. Do not convert a JPEG photo to PNG either; it usually makes the file larger without restoring lost detail. See lossy and lossless compression for the underlying tradeoff.

Deliver responsive images correctly

Compression alone does not make an image responsive. Provide width candidates and let the browser select one:

<img
  src="product-960.webp"
  srcset="product-480.webp 480w, product-960.webp 960w, product-1600.webp 1600w"
  sizes="(max-width: 720px) 100vw, 50vw"
  width="960"
  height="640"
  alt="Black travel bag open to show the interior compartments"
>

Google recommends standard image elements, useful alt text, responsive candidates, and a fallback src in its image SEO guidance . Width and height reserve layout space. Alt text should describe the image’s purpose, not repeat a list of keywords.

Verify the result in Edge

Reload with cache disabled at desktop and mobile widths. Confirm that the browser chooses the expected srcset candidate, the hero does not shift the layout, and text remains readable. Then use PageSpeed Insights or field data to determine whether image changes improved the actual page. Google treats Core Web Vitals as one part of page experience, not a substitute for useful content.

For unreleased product images, keep the conversion local until publication. See online compressor privacy risks on Windows before sending embargoed assets to a third-party service.

When GetCompress fits web asset preparation

Paint and PowerToys are enough for occasional resizing. GetCompress is the better fit when a Windows team repeatedly receives mixed PNG, JPEG, HEIC, TIFF, and other sources that need consistent dimensions, format variants, and visual review. Saved presets and batch queues prepare local delivery copies before they enter the repository or CMS.

It does not replace responsive markup, CDN configuration, caching, or performance measurement. Test the deployed page and keep the source masters separate from generated web assets.