Docs

Image Optimizer by Elementor

4 min readUpdated November 9, 2026

Image Optimizer by Elementor compresses images in the background after they are uploaded. This page explains what that means for your bucket and how to get compressed files into cloud storage. The plugin works with or without the Elementor page builder.

How Image Optimizer and WP Media Cloud work together#

Image Optimizer queues the work as a background job and sends the image to Elementor’s optimization service. The upload request does not wait for it.

  1. WordPress saves the upload and WP Media Cloud sends the original, uncompressed files to your bucket straight away.
  2. Later, Image Optimizer’s background job reads the files from your server, compresses them and writes them back on the server.
  3. WP Media Cloud is not told when this job finishes. The bucket keeps the uncompressed files.

So with Image Optimizer, new uploads stay uncompressed in cloud storage. The compressed versions only exist on your server, if the files were still there when the job ran.

WP Media Cloud shows Image Optimizer on the Integrations page, under Image Optimization. It has no code that reacts to it.

If Remove local files is on, the server copies are deleted right after the first upload. The background job then cannot find them and skips those sizes.

Image Optimizer by Elementor card on the Integrations tab

Choose the approach that suits your site.

GoalWhat to do
Compressed images in the bucket for an existing libraryCompress the library with Image Optimizer’s bulk optimization first. Then offload it with the Bulk Migration Tool.
Compressed images in the bucket for files already offloadedFollow Upload optimized files again on this page. Repeat it from time to time for new uploads.
Compressed new uploads without extra stepsUse an optimizer that WP Media Cloud uploads again after compression, such as EWWW Image Optimizer. Or use one that works before the upload, such as Cimo.

In WP Media Cloud (Media Cloud > Settings > Offload Behaviour): keep Remove local files off while you use Image Optimizer. Otherwise it has nothing to compress.

In Image Optimizer: its listing describes these options. Set them to suit your site.

SettingNotes
Optimize on uploadCompresses new uploads in the background. The bucket still gets the uncompressed file first.
Compression levelLossy gives smaller files. Lossless keeps full quality.
Convert to WebP or AVIFWP Media Cloud does not upload extra files that the plugin adds next to the original. Check a converted image on the front end before using it site wide.
Resize large imagesLimits the largest size. Smaller files mean less storage and bandwidth.

Image Optimizer needs a connected Elementor account.

Upload optimized files again#

WP Media Cloud only uploads a file a second time when an optimizer it listens to reports that it finished. Otherwise the copy in your bucket stays as it was first uploaded.

These steps send the optimized versions of files that are already offloaded. They use WP-CLI.

  1. In Media Cloud > Settings > Offload Behaviour, switch off Remove local files.
  2. Bring the files back to the server with Restore to Server on the Dashboard, or run wp wpmc restore.
  3. Run the optimizer’s bulk optimization and wait until it finishes.
  4. Run wp wpmc clear-records. It forgets which files were offloaded on this site. It does not delete anything from your bucket.
  5. If you want the server copies removed again, switch Remove local files back on now.
  6. Run wp wpmc offload. Every attachment is uploaded again and replaces the old copy at the same path.
  7. Purge the cache in your CDN, so visitors stop getting the old copies.

Between steps 4 and 6, some images are served from your server instead of the CDN. On multisite, run the commands once per subsite by adding --url=<subsite URL>.

Troubleshooting#

What you seeWhat it meansHow to fix it
Images in the bucket are uncompressedExpected. WP Media Cloud uploads before Image Optimizer runs and is not told when it finishes.Follow Upload optimized files again on this page.
Image Optimizer reports it cannot access a fileRemove local files deleted the server copy after offloading.Switch off Remove local files. Restore the files with Restore to Server before a bulk run.
Background optimization never runsImage Optimizer’s jobs are not being processed.Check Tools > Scheduled Actions for pending or failed jobs. Check the Health page in WP Media Cloud for loopback and WP-Cron problems.
The CDN still serves an old version after re-uploadingThe CDN cached the old file. WP Media Cloud does not purge your CDN.Purge the file, or the whole cache, in your CDN.

This website uses cookies to enhance your browsing experience and ensure the site functions properly. By continuing to use this site, you acknowledge and accept our use of cookies.

Accept All Accept Required Only