Image Optimization for WordPress on Windows

WordPress can generate multiple image sizes, but it cannot recover from a poor source choice. Uploading a 6000-pixel PNG photo creates unnecessary work and leaves a heavy full-size original in the library. Good WordPress image optimization starts by matching the source to the theme and ends by checking what the browser actually downloads.

Measure the theme before resizing

Open a representative post in Edge and inspect the featured image and content column. Record the rendered width at desktop and mobile breakpoints. Also check archive cards, because the same featured image may appear in a wide article header and a narrow listing grid.

Do not adopt a universal 1920-pixel rule without measuring. A publication with a 760-pixel content column needs different candidates from a full-width photography theme.

Prepare the source on Windows

For a single image, resize a copy in Paint. For a photo essay or migration, use PowerToys Image Resizer from File Explorer.

A practical folder layout is:

article-name\originals\
article-name\wordpress-upload\

Keep camera files and design masters in originals. Put only reviewed delivery copies in wordpress-upload. Use descriptive filenames such as oak-desk-cable-management.jpg, not IMG_4821-final2.jpg.

Before upload, remove location metadata when it should not be public. Check screenshots for customer names, browser tabs, internal URLs, and notification content.

Understand what WordPress generates

WordPress has supported responsive images since version 4.4 by adding srcset and sizes to generated markup. Its responsive image documentation explains that WordPress creates intermediate sizes and lets the browser choose a candidate.

That system depends on the theme and the size selected in the editor. Inserting Full Size can still make a browser download an oversized source. Custom blocks and background-image CSS may bypass normal responsive markup.

After changing theme image sizes, older uploads may need thumbnail regeneration. New settings do not automatically rebuild every historical file.

Choose formats by image content

Content	Starting format	Reason
Editorial or product photo	JPEG or WebP	Efficient for continuous tone
Screenshot with small type	PNG or high-quality WebP	Preserves edges and text
Transparent illustration	WebP or PNG	Keeps transparency
Logo from vector artwork	SVG when the theme permits	Scales without raster blur

Do not save photographs as PNG only because it sounds higher quality. Do not convert transparent artwork to JPEG unless the background has been intentionally flattened. See lossy versus lossless compression for the tradeoff.

Audit the live post

Publish to a staging environment and inspect the image request in Edge DevTools. Confirm:

• the browser selected a candidate close to the rendered width;
• the full-size original is not used for a small card;
• width and height prevent layout shift;
• the featured image remains sharp at common breakpoints;
• alt text describes the editorial purpose of the image;
• lazy loading is not applied to the likely above-the-fold hero.

Run the test on a real post template, not an isolated Media Library preview. Plugins, CDNs, and themes can rewrite the final markup.

When GetCompress fits WordPress production

Paint and PowerToys handle occasional resizing. GetCompress is the better fit when a Windows editorial team prepares recurring featured images, screenshots, galleries, and WebP or JPEG variants before Media Library import. Local batch presets keep source dimensions consistent without sending draft or embargoed material to an online optimizer.

It does not replace WordPress responsive markup, a CDN, descriptive alt text, or live-page testing. It prepares cleaner source files for those systems.