If you manage even five WordPress sites, swapping image optimization plugins isn’t a five-minute job. One wrong click multiplied across a client portfolio is a Monday morning you don’t want.<\/p>\n\n\n\n
Moving from Imagify to ShortPixel Image Optimizer<\/a> is straightforward, but only if you do it in the right order. Skip a step, and you can end up with images that are visibly degraded, with no way to recover the originals.<\/p>\n\n\n\n This guide walks you through it the way an agency should run it: site by site, repeatable, and with backups front and center.<\/p>\n\n\n\n Imagify and ShortPixel Image Optimizer both compress your images<\/a> and serve lighter versions to visitors. They just make different decisions about how aggressive to be.<\/p>\n\n\n\n The problem starts when you optimize an image that’s already been optimized. The second plugin doesn’t know what the first one threw away. It just compresses what it sees.<\/p>\n\n\n\n That’s called double compression, and it shows up as:<\/p>\n\n\n\n Imagify’s default Lossy is already aggressive. Let ShortPixel Image Optimizer run another pass on top of that, and you can easily end up with images that look noticeably worse than they should. And the original is gone.<\/p>\n\n\n\n That’s why the migration has two paths, and picking the right one for each site matters.<\/p>\n\n\n\n Before touching anything, ask: do we want ShortPixel Image Optimizer to re-optimize the existing library, or just take over from here?<\/p>\n\n\n\n Path A \u2014 Restore the originals first, then let ShortPixel Image Optimizer optimize.<\/strong> Cleaner option. Restore Imagify’s backups, uninstall it, install ShortPixel Image Optimizer, run a fresh optimization on untouched files. You end up with one plugin, one set of settings, and full freedom to pick Lossy, Glossy, or Lossless.<\/p>\n\n\n\n Path B \u2014 Keep the existing optimizations and use ShortPixel Image Optimizer only for new uploads.<\/strong> This is the fallback when restoration isn’t possible. Maybe the client disabled backups. Maybe they were lost in a host migration. Either way, the old library stays as Imagify left it, and ShortPixel Image Optimizer handles everything from here on.<\/p>\n\n\n\n For most agency workflows, Path A is the one you want whenever it’s available. We’ll cover both.<\/p>\n\n\n\n Open the client site and check whether Imagify actually has the originals.<\/p>\n\n\n\n Go to Settings > Imagify<\/strong> and look at the Backup original images<\/strong> setting. If it’s on (it is by default), you’re probably fine. To confirm, open the site via FTP or your host’s file manager and check this folder:<\/p>\n\n\n\n You should see files there, organized by year and month, mirroring your uploads folder. If the folder is empty or missing, skip to Path B.<\/p>\n\n\n\n If Imagify was optimizing images from Custom Folders too, check this path as well:<\/p>\n\n\n\n Non-negotiable. Before any bulk action, back up the whole site: files and database. UpdraftPlus, BlogVault, your host’s snapshot tool, whatever you normally use.<\/p>\n\n\n\n For agencies, this is also the right moment to spin up staging and test the migration there first. WooCommerce stores in particular don’t react well to surprises with product images.<\/p>\n\n\n\n In the WordPress admin, go to Media Library<\/strong> and switch to List View<\/strong>. Top-right corner, click Screen Options<\/strong>, and bump Number of items per page<\/strong> to 500 or 1000.<\/p>\n\n\n\n Then:<\/p>\n\n\n\n Imagify will work through the list and swap the optimized files back for the originals. Move through every page until the whole library is done.<\/p>\n\n\n\n For a library with 10,000+ images, this takes a while, and your browser tab needs to stay open. Run it in chunks, ideally outside peak hours, and keep an eye on server load.<\/p>\n\n\n\n For images optimized through Custom Folders, repeat the same process from Media > Other Media<\/strong>.<\/p>\n\n\n\n Open a handful of images in the Media Library and check that they’re back to their original file size and quality. If anything didn’t restore, the Imagify column usually tells you why.<\/p>\n\n\n\n Now you can safely remove the plugin.<\/p>\n\n\n\n Don’t skip the uninstall step. Two image optimization plugins active at the same time is a mess: both will hook into the upload process, both will try to manage WebP<\/a> and AVIF<\/a> generation, and you’ll lose an afternoon figuring out which one is doing what.<\/p>\n\n\n\n Install ShortPixel Image Optimizer<\/strong> from the WordPress repository. Activate it, paste in your API key, and configure your settings before<\/em> running anything in bulk.<\/p>\n\n\n\n A sensible default for most client sites:<\/p>\n\n\n\n For photography clients or portfolio sites, drop Compression to Lossless or test Glossy carefully on a few representative pages before bulk processing.<\/p>\n\n\n\n Go to Media > Bulk ShortPixel<\/strong> and start the process. Because you restored originals first, every image is being compressed once, by one plugin, at the level you picked.<\/p>\n\n\n\n That’s your clean baseline.<\/p>\n\n\n\n Sometimes restoration just isn’t possible. Common reasons:<\/p>\n\n\n\n In any of these cases, the existing Media Library is what you have to work with.<\/p>\n\n\n\n The key principle: don’t re-optimize the old images with Lossy or Glossy.<\/strong> If you must run a bulk operation, set ShortPixel to Lossless first or mark them as already optimized when ShortPixel is enabled.<\/p>\n\n\n\n Here’s why. The images have already had quality stripped out by Imagify. Lossy or Glossy will strip out more, and there’s no Ctrl+Z for that. Lossless, on the other hand, doesn’t throw away visual information, or simply mark them as optimized. It just finds more efficient ways to encode what’s already there. The savings are modest, but the images stay safe.<\/p>\n\n\n\n The Path B migration looks like this:<\/p>\n\n\n\n That last step is what protects you. A bulk optimization with ShortPixel Image Optimizer processes the entire library, including everything Imagify already touched. Leave it alone, and the old files stay as they are. New uploads get optimized from day one.<\/p>\n\n\n\n One site? The steps above are all you need. Twenty sites? The migration itself is the easy part. The hard part is doing it consistently across every client.<\/p>\n\n\n\n ShortPixel lets you create subaccounts from a single parent account, each with its own API key and credit allocation. Alternatively, you could use API Key Aliases. For agencies, this is how you should structure things from day one.<\/p>\n\n\n\n Set up the parent account once, then create one subaccount per client site. Each gets:<\/p>\n\n\n\n One client’s heavy month doesn’t eat into another client’s quota. And you never have to guess who optimized what.<\/p>\n\n\n\n Pick one default ShortPixel configuration that fits the majority of your portfolio, simple business sites, blogs, basic e-commerce, and apply it without thinking on every site. Document it once. The configuration above is a fine starting point.<\/p>\n\n\n\n Deviations are okay. Photography portfolios will want Lossless. News sites might want more aggressive resizing. But every deviation should be intentional and documented in that client’s internal notes.<\/p>\n\n\n\n The goal isn’t perfect uniformity. The goal is that any team member opening a ShortPixel setup six months from now immediately understands what they’re looking at.<\/p>\n\n\n\n Don’t plan a “migration weekend” where you switch everything at once. Something will go sideways on one or two sites, and you want bandwidth to handle it.<\/p>\n\n\n\n A reasonable cadence:<\/p>\n\n\n\n The two-line version:<\/p>\n\n\n\n Either way: full backup before you start, subaccounts or api key aliases for clean client billing, and a standardized setup across the portfolio. The migration itself is half an hour or less per site. Everything else is what keeps you from inheriting a mess six months from now.<\/p>\n\n\n\n No. Running two image optimization plugins at the same time causes conflicts with upload hooks, WebP\/AVIF generation, and backup handling. Finish your restoration in Imagify first, then deactivate and uninstall it before installing ShortPixel.<\/p>\n\n<\/div>\n<\/div>\n Yes. Imagify’s WebP and AVIF files are tied to that plugin’s settings. Once ShortPixel is installed and configured, it will generate fresh WebP and AVIF versions during bulk optimization (or for new uploads, automatically).<\/p>\n\n<\/div>\n<\/div>\n Most of the time, this means the backup file is missing or corrupted for that specific image. The Imagify column in the Media Library will show the reason. Those images need to be treated as Path B cases: leave them as they are, and let ShortPixel handle them on Lossless only if at all.<\/p>\n\n<\/div>\n<\/div>\n For a typical small business site (a few hundred images), 20 minutes or less including backup. For a media-heavy site with 10,000+ images, plan for 1-2 hours of unattended bulk processing, spread across one or two off-peak windows.<\/p>\n\n<\/div>\n<\/div>\n Usually no. WordPress thumbnails are already on disk, and ShortPixel will optimize them as part of bulk optimization. Only regenerate thumbnails if you’ve also changed your theme or registered new image sizes around the same time.<\/p>\n\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n\n\n Easily optimize all your customers’ images using ShortPixel Image Optimizer.<\/p>\n\n\n\nWhy a plugin swap needs a plan<\/strong><\/h2>\n\n\n\n
\n
The two paths<\/strong><\/h2>\n\n\n\n
Path A: The clean migration<\/strong><\/h2>\n\n\n\n
Step 1 \u2014 Confirm backups exist<\/strong><\/h3>\n\n\n\n
\/wp-content\/uploads\/backup\/<\/code><\/pre>\n\n\n\n\/imagify-backup\/<\/code><\/pre>\n\n\n\nStep 2 \u2014 Take a full site backup<\/strong><\/h3>\n\n\n\n
Step 3 \u2014 Restore the originals in Imagify<\/strong><\/h3>\n\n\n\n
\n
Step 4 \u2014 Spot-check the restoration<\/strong><\/h3>\n\n\n\n
Step 5 \u2014 Deactivate and uninstall Imagify<\/strong><\/h3>\n\n\n\n
Step 6 \u2014 Install ShortPixel Image Optimizer and configure it<\/strong><\/h3>\n\n\n\n
\n
Step 7 \u2014 Run a bulk optimization with ShortPixel<\/strong> Image Optimizer<\/h3>\n\n\n\n
Path B: When you can’t restore the originals<\/strong><\/h2>\n\n\n\n
\n
\n
Agency workflow: doing this across a portfolio<\/strong><\/h2>\n\n\n\n
Use subaccounts or API Key Aliases to keep client billing clean<\/strong><\/h3>\n\n\n\n
\n
Standardize your settings before you start<\/strong><\/h3>\n\n\n\n
Migrate in waves<\/strong><\/h3>\n\n\n\n
\n
Quick recap<\/strong><\/h2>\n\n\n\n
\n
FAQs<\/strong><\/h2>\n\n\n
Can I keep both Imagify and ShortPixel active during the migration?<\/strong><\/h3>\n
Will I lose my WebP and AVIF versions when I uninstall Imagify?<\/strong><\/h3>\n
What if Imagify’s restore action fails on some images?<\/strong><\/h3>\n
How long does the whole migration take per site?<\/strong><\/h3>\n
Do I need to regenerate thumbnails after switching?<\/strong><\/h3>\n
Try ShortPixel on WordPress for free!<\/h3>\n\n\n\n