Cimo
Cimo optimizes images in the browser before they are uploaded, so WordPress only ever receives the optimized file. This page explains how that fits with WP Media Cloud, which Cimo settings to use, and what to do when something looks wrong.
How Cimo and WP Media Cloud work together#

- You pick an image in the Media Library uploader.
- Cimo compresses it in your browser and, where the browser supports it, converts it to WebP.
- The optimized file is uploaded to WordPress through the normal media upload.
- WP Media Cloud offloads that file and its generated sizes to your bucket and serves them from your CDN.
Because compression happens before the upload, the first file WP Media Cloud sends to the bucket is already the final version. Nothing has to be uploaded a second time.
WP Media Cloud has no special code for Cimo. It detects Cimo and shows its status on the Integrations page, under Image Optimization, as Active with the Cimo version.
Remove local files (Settings > Offload Behaviour) is safe with Cimo for new uploads. Cimo does not need the server copy after the upload.
Recommended Cimo settings#
Cimo’s settings are under Settings > Cimo in WordPress.
| Setting | Recommendation |
|---|---|
| Optimization toggle | On. |
| WebP quality | Start with the default of 80%. Lower it only if the images still look good. |
| Max image dimension | Set it to the largest size your theme displays. Smaller originals mean less storage and bandwidth. |
| Thumbnail generation | Leave the sizes your theme uses switched on. WP Media Cloud offloads whatever sizes WordPress creates. |
No settings are needed in WP Media Cloud.
Things to know#
- Safari: Cimo’s listing says images uploaded from Safari are optimized but keep their original format. They are not converted to WebP.
- Existing images: In the free version Cimo only optimizes new uploads. Bulk optimization of existing media is a Cimo Premium feature.
- Bulk optimization and offloaded files: WP Media Cloud does not listen for Cimo’s bulk optimization. A file already in your bucket stays as it was. Run Cimo’s bulk optimization before you bulk offload your library with the Bulk Migration Tool. For files already offloaded, see Upload optimized files again on this page.
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.
- In Media Cloud > Settings > Offload Behaviour, switch off Remove local files.
- Bring the files back to the server with Restore to Server on the Dashboard, or run
wp wpmc restore. - Run the optimizer’s bulk optimization and wait until it finishes.
- Run
wp wpmc clear-records. It forgets which files were offloaded on this site. It does not delete anything from your bucket. - If you want the server copies removed again, switch Remove local files back on now.
- Run
wp wpmc offload. Every attachment is uploaded again and replaces the old copy at the same path. - 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 see | What it means | How to fix it |
|---|---|---|
| Uploads are not optimized | Cimo is off, or its script did not run in the browser. | Check that Cimo is active and its optimization toggle is on. Check that a browser extension or a Content Security Policy is not blocking scripts in the WordPress admin. |
| Images uploaded from Safari stay JPEG or PNG | Safari does not support Cimo’s WebP conversion. | Expected. Upload from Chrome, Firefox or Edge when you need WebP. |
| The bucket still has the old version after a Cimo bulk run | WP Media Cloud does not re-upload files that are already offloaded. | See Upload optimized files again on this page. |
| The Integrations page shows Cimo as Not installed | The status is cached for up to 5 minutes. | Wait a few minutes and reload, then check that Cimo is active under Plugins. |