Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared Managed Cloud India
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Best lists Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Plugin how-tos · Guide

How Do You Set Up Smush Settings in WordPress?

Short answer

Open Smush in your WordPress dashboard, turn on automatic compression, pick Basic, Super or Ultra compression, and run Bulk Smush for older images. Then set image sizes, turn on lazy load, and add preload, WebP, AVIF or the CDN only if your plan and site need them. Check the result on a few real pages before you change more settings.

Key takeaways

  • Automatic compression in Smush only covers the image sizes you select, so check Image Sizes first.
  • Super compression gives about 2 times the compression of Basic, while Ultra gives about 5 times.
  • Smush skips automatic compression for images larger than 32 MB, so compress those files by hand.
  • Lazy load should run in only one plugin at a time, and hero images should stay out of lazy load.
  • Next-Gen Formats and the Smush CDN are Pro features, with Pro plans from $50 a year for 1 site as of November 2026.
  • Turn on Backup original images before you bulk optimize, or you cannot restore the originals later.

What does Smush do and where are its settings?

Smush compresses images, lazy loads offscreen images, and can serve WebP, AVIF and CDN images from one plugin.

Smush is made by WPMU DEV. WordPress.org lists it as used by more than 1 million sites, with a 4.8 out of 5 rating and an update on 16 November 2026, as of November 2026.

You will find its screens under Smush in the WordPress admin menu. The main screens are Dashboard, Bulk Smush, Lazy Load and Preload, Next-Gen Formats, CDN, Tools and Settings.

The Dashboard shows Quick Feature Controls for the main features. Each card links to the screen where you change that feature in detail, according to the Smush usage guide.

If you want a short overview before you change settings, read our Smush review. It covers the same free and Pro split used in this guide.

What should you set first after installing Smush?

Set automatic compression, a compression level, image sizes and lazy load first, then run Bulk Smush once.

Start with the setup wizard if it appears. It covers automatic compression, metadata, full-size images, lazy load and usage data, according to WPMU DEV.

Use this order for a new site:

  1. Turn on Automatic Compression in Smush > Tools.
  2. Pick a compression level in Bulk Smush.
  3. Select the image sizes to compress.
  4. Turn on Lazy Load in Smush > Lazy Load and Preload.
  5. Run Bulk Smush for images already in your library.
SettingWhere to find itSafe first choice
Automatic CompressionSmush > Tools > GeneralOn
Compression levelSmush > Bulk SmushBasic, then Super if files stay large
Image SizesSmush > Tools > Image SizesAll image sizes
Lazy LoadSmush > Lazy Load and PreloadOn, with hero images excluded
Backup original imagesSmush > ToolsOn before bulk work

Allow 10 to 30 minutes for a small library. A large library takes longer, and Smush can keep working in the background.

How do you choose a compression level in Smush?

Pick Basic for light compression, Super for smaller files, and Ultra only if you pay for Pro and need the most compression.

Basic is the standard level. Super uses lossy compression and gives about 2 times the compression of Basic, according to WPMU DEV. Ultra gives about 5 times the compression of Basic and needs Pro.

Lossless compression keeps more image data. Lossy compression removes more data to make a smaller file, so check image quality on a few photos after you switch.

If an image returns an API error, the level can be the cause. The Smush usage guide says thumbnails often compress well at Basic, but larger or original images may need Super or Ultra.

Change the level in Bulk Smush before you run a bulk job. New uploads use the level you set for automatic compression.

How does Bulk Smush work?

Bulk Smush scans your media library, compresses images that still need work, and shows how many images it finished and how much space it saved.

Open Smush > Bulk Smush and start the job from there. The screen lists images that need attention, and you can also compress single images from the Media Library.

Smush also covers images outside the media library through Directory Smush. WordPress.org says this covers images in theme folders, plugin folders and other server folders.

If a bulk job stops, do not run the same job again at once. The Smush docs say automated retries are limited to 5 times per 1000 images, and you can raise that limit only with a code change in wp-config.php.

Check the count after the job ends. If some images stay unoptimized, open one in the Media Library and look for an error or a file-size limit.

How do you set up automatic compression and image sizes?

Turn on Automatic Compression, choose the image sizes to cover, and decide what happens to originals and metadata before you upload more images.

Automatic Compression optimizes every image copy WordPress makes as soon as it is created. The Smush usage guide says it only covers the sizes you selected in Image Sizes.

Images larger than 32 MB are not compressed automatically, even with this setting on. Compress those files before upload, or compress them by hand in the Media Library.

Use these Tools settings:

  • Automatic Compression: on, so new uploads are compressed at once.
  • Optimize original images: on only if you want the full-size file compressed too.
  • Remove Metadata from Images: on for most sites, off if you need camera data kept.
  • Image Sizes: turn on All image sizes unless a size is unused.
  • Email Notification: on if you want a message when a background job ends.

Removing metadata can change colour or orientation in rare cases. The Smush docs warn that EXIF data can hold colour profile or orientation data, so keep a backup if your photos depend on it.

WordPress makes several copies of each upload at different sizes. Compressing all sizes uses more storage, but it keeps each size fast when a theme or plugin calls it.

How do you resize large images in Smush?

Use Large Image Resizing to change the 2560 pixel limit, or turn off scaled images only if you know why you need the full file.

WordPress makes a scaled copy of any image larger than 2560 by 2560 pixels and keeps the original as a backup. The Smush usage guide says you can change that limit in Smush > Tools > Large Image Resizing.

The two choices work like this:

  • Resize large images: set a new max width and height, such as 3000 by 3000 pixels.
  • Disable scaled images: stop WordPress from making scaled copies at all.

If you set 3000 by 3000 pixels and only resize originals, Smush backs up the original, makes a scaled copy, and then resizes that copy to 3000 by 3000 pixels. If you turn on both options, the original is resized to the limit you set.

Do not disable scaled images on a photo site without a plan. Full-size files load slower and use more storage, and that cost adds up across a large library.

Smush Pro also adds Automatic Resizing and Set Image Dimensions in Tools > Image Sizing. Automatic Resizing fits images to their containers, while Set Image Dimensions adds missing width and height values to cut layout shift.

How do you set up lazy load in Smush?

Turn on Lazy Load, pick the areas, media types and post types to cover, then exclude hero images and other above-the-fold images.

Lazy load holds offscreen images until a visitor scrolls near them. The Smush usage guide says this can help page speed most on image-heavy pages.

Open Smush > Lazy Load and Preload and turn on Lazy Load at the top. Then check these controls:

  • Areas to Lazy Load: use All areas, or pick single areas.
  • Media Types to Lazy Load: use All media types, or pick single types.
  • Post types to lazy load: turn each post type on or off.
  • Native lazy loading: turn it on for browser lazy load, or off if a PageSpeed check fails.
  • Noscript Fallback: on for browsers without JavaScript, off if it breaks a script effect.
  • Loading Appearance: pick Fade In, Spinner, Placeholder or no effect.

Use lazy load in only one plugin at a time. The Smush docs warn that a second lazy load plugin can stop Smush lazy load from working as expected.

Some images are skipped by design. An image with fetchpriority set to high is not lazy loaded, and featured images use high priority by default in WordPress 6.3 and later.

Background images need inline CSS to be lazy loaded by Smush. A background set only in a style sheet will not be picked up.

For video embeds, turn on the iframe type, then use YouTube or Vimeo preview images if you want the video to load only after a visitor clicks play. That keeps the heavy iframe off the first load.

How do you set up preload for the largest image?

Turn on Preload in Smush > Lazy Load and Preload, let Smush find the largest above-the-fold image, and exclude pages where that image changes.

Preload tells the browser to fetch the largest visible image early. Smush finds that image on its own and adds fetchpriority set to high, so it is not lazy loaded.

A good Largest Contentful Paint, or LCP, is 2.5 seconds or less. web.dev says LCP reports the render time of the largest image, text block or video in view, and sites should aim for 2.5 seconds or less.

Smush also has a Fetchpriority option that replaces the WordPress default, which gives high priority to the first 3 images on a page. The Smush docs say its own detection is more exact than that default.

Use Clear LCP Data after you change images or templates. The docs say it clears preload data from pages, posts, custom post types, the front page, search, 404 pages and archives.

Add relative URLs, one per line, under Exclude Content from Preload for pages where the main image changes often. That stops Smush from preloading the wrong image.

LCP is a loading metric, while INP measures how fast a page responds to input. Fix the largest image first, then look at other speed settings.

How do you turn on WebP, AVIF and the Smush CDN?

Turn on Next-Gen Formats for WebP or AVIF, and turn on the CDN from the CDN tab, but only on a Pro plan.

Next-Gen Formats is a Pro feature. It serves WebP or AVIF copies from your Media Library without the CDN, according to the Smush usage guide.

It only covers JPEG and PNG images in the Media Library. Images in other folders are not converted by this feature.

WebP is a modern image format with lossy and lossless modes. Google for Developers says lossless WebP files are 26 percent smaller than PNG files, and lossy WebP files are 25 to 34 percent smaller than similar JPEG files.

To use Next-Gen Formats:

  1. Open Smush > Next-Gen Formats.
  2. Turn on Next-Gen Formats.
  3. Pick WebP or AVIF.
  4. For AVIF, turn on JavaScript Fallback if you want older browsers to get the original file.
  5. Turn the feature off to serve the original JPEG or PNG files again.

The Smush CDN is also Pro only. Open the CDN tab and click Get Started, then wait for the message that your media is served from the WPMU DEV CDN.

The CDN covers JPG, PNG, GIF and WebP files. WordPress.org lists 119 global CDN servers and up to 500 GB of bandwidth, as of November 2026.

To check the CDN, inspect an image in Chrome or Firefox. The WPMU DEV CDN docs say CDN images start with an assetcdn.net address.

Pro plans start at $50 a year for 1 site, $75 a year for 3 sites, and $100 a year for 10 sites, as of November 2026. WPMU DEV pricing lists 50 GB of CDN bandwidth and 5 GB of backup storage on each of those 3 plans.

If you use another CDN or a caching plugin, test one change at a time. For a wider speed plan, see our guide on how to speed up WordPress.

How do you back up and restore images in Smush?

Turn on Backup original images before you optimize, then use Restore All Images or the Media Library restore action if you need the originals back.

Backup original images must be on before you optimize. The Smush docs say Restore All Images uses those backups to return images and thumbnails to their original state.

Restore All Images only works for images uploaded to the uploads folder through the Media Library. It will not restore images optimized with Directory Smush.

If you optimized originals without a backup, thumbnails can still be remade, but quality may suffer because the source was already compressed. That is why the backup step comes first.

To restore single images, open the Media Library, select the images, and use the Smush restore bulk action. To restore all images, use Restore All Images in Tools.

PNG to JPEG conversion needs the same care. Smush converts only non-transparent PNG files, and only when the JPEG is smaller. The original PNG is deleted unless Backup original images is on.

Keep a full site backup as well. Our guide on how to back up WordPress covers the backup step Smush does not replace.

What mistakes should you avoid?

Avoid running two lazy load tools, skipping backups, and turning on every Pro feature before you check the result.

  • Do not run lazy load in Smush and in another plugin or theme at the same time.
  • Do not lazy load the hero image, logo or other above-the-fold image.
  • Do not bulk optimize without Backup original images turned on first.
  • Do not strip metadata from photos where colour or orientation data matters.
  • Do not turn on the CDN and Next-Gen Formats together without checking a few pages.
  • Do not disable scaled images just to keep full-size files.
  • Do not judge a change from one page only; check the home page, a post and a gallery page.

If a page looks wrong after a change, turn off the last setting you changed and reload the page. That single-change check saves time when two settings interact.

For cache settings that sit next to image settings, see our LiteSpeed Cache settings guide. Change cache and image settings on different days if you can, so you know which change caused a change in speed.

Frequently asked questions

Does Smush work without Pro?

Yes. The free plugin covers automatic compression, bulk compression, lazy load, image resizing and Directory Smush. WebP and AVIF conversion, Ultra compression, automatic image sizing and the image CDN need a Pro plan. Start with the free settings, then add Pro only if a specific limit or feature blocks you.

Will Smush slow down my site?

Smush is meant to cut image weight, but a wrong setting can hurt. Lazy load in two tools at once, lazy loading the hero image, or serving oversized originals can all slow a page. Turn on one feature at a time, check the home page and a post, and turn off the last change if speed or layout gets worse.

Can I undo Smush compression?

Yes, if you turned on Backup original images before you optimized. Use Restore All Images in Tools for the whole library, or use the Smush restore bulk action in the Media Library for single images. Without a backup, thumbnails can be remade, but the original quality may already be lost.

Why are some images not lazy loaded by Smush?

Smush skips images with fetchpriority set to high, and featured images use that value by default. Background images need inline CSS to be lazy loaded. Images may also be skipped if another plugin already handles lazy load, or if you excluded the page, post type or image in the Smush settings.

Do I need the Smush CDN if I already use Cloudflare?

Not always. The Smush CDN serves images from 119 servers and can add WebP conversion and dynamic resizing. If Cloudflare already serves your images well, test Smush CDN on a staging copy first and compare a few pages. Keep only one image CDN active for the same images to avoid conflicts.

How long does Bulk Smush take?

It depends on how many images you have and how large they are. A small library can finish in 10 to 30 minutes, while a large library can take much longer and may keep working in the background. Leave the job running, check the finished count, and compress any images larger than 32 MB by hand.

Sources

  1. Smush | WPMU DEV WPMU DEV
  2. Smush – Image Optimization, Compression, Lazy Load, WebP & CDN WordPress.org
  3. WPMU DEV Membership Plans & Pricing WPMU DEV
  4. WPMU DEV Content Delivery Network (CDN) WPMU DEV
  5. Largest Contentful Paint (LCP) web.dev
  6. An image format for the Web Google for Developers

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

WPLegible editors

Researched from the primary sources listed above and checked against our editorial rules. About the site · How we test