The best image format for WordPress is WebP for photographs and graphics, with JPG and PNG as automatic fallbacks, and SVG for logos and icons. WordPress powers a huge share of the web, and images are usually the heaviest thing on any page it serves, so the format you upload directly shapes how fast your site loads and how well it ranks. WordPress handles a lot for you, generating multiple sizes of every upload, but it will not choose the ideal format unless you set it up to. This guide covers which format to use, how WordPress processes images, and the settings and plugins that keep a WordPress site fast.

Why image format matters so much on WordPress

On a typical WordPress page, images account for the majority of the bytes a visitor downloads. That means image format is the single biggest lever on page speed, and page speed feeds directly into Core Web Vitals, which Google uses as a ranking signal. A theme can be lean and the hosting fast, but a page stuffed with oversized JPGs will still crawl. Choosing an efficient format and letting WordPress serve appropriately sized versions is the highest-impact optimisation most sites can make, and it costs nothing but a little setup.

How WordPress handles image uploads

When you upload an image, WordPress does not just store it. It generates several resized copies automatically, thumbnail, medium, large, and full, so it can serve a size appropriate to each context. It also builds the responsive srcset markup so browsers pick the right size per device. This is powerful, but it works from whatever you upload, so a 5000-pixel original produces bloated copies at every size. Uploading a sensibly sized, efficiently compressed original means every generated version is lean too.

WebP: the modern default

WebP is the format to standardise on. It produces files 25 to 35% smaller than JPG at the same quality, supports transparency like PNG, and is now supported by every current browser. WordPress has supported WebP uploads since version 5.8, and with the right plugin it can serve WebP versions of your existing JPGs and PNGs automatically, falling back to the original for any browser that cannot display it. Moving a media library to WebP is often the single biggest speed win a WordPress site can get.

JPG and PNG as fallbacks

WebP does not mean abandoning the older formats. JPG remains the safe fallback for photographs and PNG for graphics needing transparency, and a good optimisation plugin keeps the originals so any browser lacking WebP support still gets a working image. In practice you upload a JPG or PNG as usual and the plugin generates and serves a WebP alongside it, delivering the smaller file where it can. This gives you WebP's savings with none of the compatibility risk, which is why it is the recommended setup rather than WebP-only.

SVG for logos and icons

For your logo and interface icons, SVG beats any raster format. It is vector, so it stays razor sharp at every screen density from one tiny file. WordPress does not allow SVG uploads by default for security reasons, since an SVG can contain script, so you enable it with a plugin that sanitises the files on upload. Once enabled, a logo served as SVG is smaller and sharper than a PNG equivalent and never needs multiple sizes generated. Reserve SVG for logos, icons, and simple graphics, never photographs.

Choosing the right image sizes

WordPress generates several sizes, but you control the dimensions. Set the large size to no wider than your content area, often around 1200 to 1600 pixels, so full-width images are not needlessly huge. Uploading a 4000-pixel photo when your content column is 800 pixels wide wastes bandwidth even after WordPress resizes, because the largest generated copy is still oversized. Match your registered image sizes to your theme's actual layout, and every image the site serves stays proportionate to where it appears.

Compression and optimisation plugins

An optimisation plugin automates the whole pipeline. Popular options compress every upload, generate WebP versions, and can strip unnecessary metadata, all without you touching an image by hand. Many also optimise your existing library in bulk, converting years of accumulated JPGs and PNGs to WebP in one pass. Some offload the processing to their own servers to spare your hosting. Whichever you choose, the effect is the same: images arrive on the page compressed and in the best format automatically, which is far more reliable than remembering to optimise each one manually.

Lazy loading images

Lazy loading defers images until a visitor scrolls near them, so a page's initial load only fetches what is immediately visible. WordPress enables lazy loading by default on images below the fold, adding the loading attribute automatically. This speeds up the first paint noticeably on image-heavy pages. The one exception is your largest above-the-fold image, often the hero, which should load eagerly so it does not delay the Largest Contentful Paint metric. Most optimisation plugins let you exclude that image from lazy loading with a single setting.

Stripping metadata

Photographs carry metadata, camera model, GPS location, colour profiles, that a website rarely needs and which adds weight. Stripping this metadata shrinks each file with no visible change, and most optimisation plugins do it as part of compression. Removing GPS data also has a privacy benefit, since you probably do not want to publish where a photo was taken. The only metadata worth keeping is the colour profile if colour accuracy matters. Otherwise, stripping it is a free, invisible size reduction across the whole library.

A recommended WordPress image setup

Put it together and the setup is straightforward. Register image sizes that match your theme's layout. Install an optimisation plugin that compresses uploads, generates and serves WebP with fallbacks, and strips metadata. Enable sanitised SVG for your logo and icons. Keep WordPress's default lazy loading, but load your hero image eagerly. Then simply upload sensibly sized originals and let the pipeline do the rest. With this in place, every image on the site is compressed, correctly sized, and served in the best format automatically, and the site stays fast as the library grows.

AVIF: the

next step beyond WebP

AVIF is the newest efficient format, and WordPress supports it too. It compresses even smaller than WebP, often 20% smaller again, at the same visual quality, with support for transparency and wide colour. Browser support is now broad but slightly behind WebP, so AVIF works best served with a WebP or JPG fallback. Some optimisation plugins can generate AVIF automatically alongside WebP. For a site chasing the last few kilobytes off every image, AVIF is worth enabling, though WebP remains the safe primary format for now.

The media library and housekeeping

Over time a WordPress media library fills with unused images, old versions, and duplicates that bloat backups and clutter the admin. Periodically clearing out unused media keeps the library manageable and your backups lean. Plugins can identify images not attached to any post or page, though it is worth reviewing before deleting, since some images are used in ways the scan cannot detect. A tidy media library is easier to work with and, once optimised, gives a clear picture of how much space your images actually occupy.

Regenerating thumbnails after a theme change

When you switch themes or change your registered image sizes, existing uploads still have their old generated sizes. Regenerating thumbnails rebuilds every size from the originals to match the new dimensions, which a dedicated plugin does in bulk across the whole library. Skip this and images can appear stretched or served at the wrong size under the new theme. It is a one-time step after any change to your image sizes, and running it keeps the whole library consistent with how the current theme actually displays images.

CDN delivery for images

A content delivery network speeds up image delivery by serving files from a server near each visitor. A CDN caches your images at edge locations worldwide, so a reader far from your host still gets images quickly. Many WordPress optimisation and caching plugins integrate a CDN, and some image-specific CDNs also convert and resize on the fly, handling format and dimensions automatically. For a site with a global audience or heavy traffic, a CDN removes image delivery as a bottleneck and takes load off your origin server at the same time.

Featured images and social previews

Every post's featured image does double duty: it appears in your theme and, through Open Graph tags, as the preview when the post is shared. Set featured images at a size that works for social previews, around 1200 by 630, so shared links look sharp in the feed. An SEO plugin usually maps the featured image to the Open Graph tag automatically. Getting this right means every post that gets shared shows a clean, correctly sized image rather than a cropped thumbnail or nothing at all.

Testing your image performance

After optimising, measure the result. Tools like PageSpeed Insights report on image-related issues, flagging oversized images, missing modern formats, and images without dimensions that cause layout shift. They tie directly into Core Web Vitals, so their advice maps to what Google measures. Running a test before and after an optimisation pass shows exactly how much faster the page has become and highlights any image still holding it back. Treat these reports as a checklist for squeezing the last of the weight out of your images.

Common WordPress image mistakes

A few habits quietly slow WordPress sites. Uploading full-resolution camera images, skipping compression, and not enabling WebP are the most common, each leaving large files where small ones would do. Others include forgetting to set image dimensions, which causes layout shift, and using a slow, feature-heavy plugin that adds more weight than it saves. Every one of these is easy to fix with the setup above. Avoiding them keeps a WordPress site fast as it grows, rather than watching it slow year by year as the library fills.

What is the best image format for WordPress?

WebP for photos and graphics, with JPG and PNG fallbacks, and SVG for logos. WebP files are 25 to 35% smaller than JPG at the same quality and every current browser supports them.

Does WordPress support WebP?

Yes, since WordPress 5.8. You can upload WebP directly, and an optimisation plugin can serve WebP versions of existing JPGs and PNGs automatically with fallbacks.

Can I upload SVG files to WordPress?

Not by default, for security reasons. A plugin that sanitises SVGs on upload enables it safely, after which logos and icons served as SVG are smaller and sharper than PNG.

Do I need an image optimisation plugin?

It is strongly recommended. A plugin compresses uploads, generates WebP, and strips metadata automatically, which is far more reliable than optimising each image by hand.

Should I resize images before uploading to WordPress?

Yes. Upload no wider than your content area, often 1200 to 1600 pixels. A huge original makes every size WordPress generates from it oversized too.

Does WordPress support AVIF?

Yes. AVIF compresses around 20% smaller than WebP at the same quality, and some optimisation plugins generate it automatically. Serve it with a WebP or JPG fallback for full browser support.

Should I use a CDN for WordPress images?

For a global or high-traffic site, yes. A CDN caches images at edge locations worldwide, so distant visitors get them quickly and load comes off your origin server.

Why do my images look wrong after changing themes?

Because existing uploads keep their old generated sizes. Regenerating thumbnails rebuilds every size from the originals to match the new theme's dimensions.

Should I lazy-load WordPress images?

Yes, and WordPress enables lazy loading by default on images below the fold. Keep it on, but load your main above-the-fold hero image eagerly so it does not delay the Largest Contentful Paint.