--- title: Smush PRO – Installation Guide description: "# Overview [Smush Pro optimizes WordPress images](https://nippylaunch.com/mp-files/smush-pro.zip/) through compression, resizing, lazy loading, WebP/next-generation delivery, bulk processing, and optional CDN services. It is designed to reduce image payload while preserving acceptable visual quality. **When to use it.**Use it when the media…" url: "https://nippylaunch.com/docs/smush-pro-installation-guide/" updated: "2026-08-17" category: Resource Library / Performance and Backup --- # Smush PRO – Installation Guide # Overview [Smush Pro optimizes WordPress images](https://nippylaunch.com/mp-files/smush-pro.zip/) through compression, resizing, lazy loading, WebP/next-generation delivery, bulk processing, and optional CDN services. It is designed to reduce image payload while preserving acceptable visual quality. **When to use it.**Use it when the media library needs a consistent optimization pipeline and you can prevent duplicate compression, lazy loading, CDN rewriting, or next-gen delivery. # Before You Begin **Platform compatibility.**Use a WordPress and PHP combination supported by the current developer release. Minimum versions can change; verify the current official product page or plugin/theme metadata before production deployment. Do not bypass an activation or compatibility warning without identifying its cause. ## Requirements and dependencies - **-**Administrator access and a supported WordPress/PHP environment. - **-**Write access to uploads and enough server resources for bulk work. - **-**A verified backup or retained originals before destructive image changes. - **-**A WPMU DEV account may be required for Pro cloud/CDN services and updates. ## Pre-installation checks - **-**Back up the uploads directory and [Database](https://nippylaunch.com/encyclopedia/database/). - **-**Identify existing image compression, WebP/AVIF, lazy-load, CDN, and resizing features. - **-**Select a small representative image sample for quality review before bulk processing. # Installation 1. 1. Go to Plugins > [Add New Plugin](https://nippylaunch.com/mp-files/smush-pro.zip/) > Upload Plugin. 2. 2. [Upload the Smush Pro ZIP](https://nippylaunch.com/mp-files/smush-pro.zip/), install, and activate it. 3. 3. Open Smush and run its setup wizard conservatively. 4. 4. Connect the authorized WPMU DEV account if your entitlement and desired cloud services require it. 5. 5. Optimize the sample set and compare visual quality before running Bulk Smush. # License Activation 1. 1. Use the official WPMU DEV account/dashboard connection shown by the plugin when a valid membership is available. (First, check whether the Pro version is already active, as manual license entry may not be required.) 2. 2. The downloaded archive alone does not guarantee access to Smush Pro CDN, automatic updates, or vendor support. **Important.**A premium download does not automatically establish ownership of the original developer's account, license key, automatic-update service, cloud features, or direct support. Use only [Credentials](https://nippylaunch.com/encyclopedia/credentials/) that are valid for this site and were supplied through an authorized account or an explicit [Nippy Launch](https://nippylaunch.com/encyclopedia/nippy-launch/) entitlement. # Initial Setup 1. 1. Choose the compression level and whether originals are retained. 2. 2. Set maximum image dimensions that match the site's real design needs. 3. 3. Enable lazy loading only if the theme, browser optimization, CDN, or another plugin is not already responsible. 4. 4. Configure next-gen delivery/CDN and verify rewritten URLs. 5. 5. Run bulk optimization in manageable batches and monitor server load. # Recommended Configuration - **-**Keep a recoverable original before approving aggressive compression. - **-**Do not optimize the same image pipeline with multiple plugins or services. - **-**Exclude above-the-fold hero/logo images from lazy loading when it harms Largest Contentful Paint. - **-**Use consistent upload dimensions and avoid generating unnecessary thumbnail sizes. - **-**Check product images, text-in-image graphics, transparency, and retina displays visually. # Main Features The installed edition can provide the following primary capabilities. Availability may depend on the active plan, add-ons, and current release. - **-**Bulk and automatic image compression - **-**Resize detection and maximum-dimension controls - **-**Lazy loading - **-**WebP/next-generation image delivery - **-**Optional CDN and reporting features # How to Use It **Practical starting workflow.**Optimize ten representative files—photo, logo, transparent PNG, product image, and text graphic—then review them on a phone and high-density display. Approve the settings before processing the full library. # Integrations - **-**WordPress Media Library and common image uploads - **-**WooCommerce product galleries - **-**CDNs and host image services require a single-owner configuration - **-**Caching plugins may need a purge after delivery changes Enable an integration only after its account ownership, permissions, data flow, and failure behavior have been tested. Keep secret [Credentials](https://nippylaunch.com/encyclopedia/credentials/) out of page content and screenshots. # Common Issues & Troubleshooting - **- Images do not change.**Check whether files were already optimized, whether the correct thumbnail sizes are displayed, and clear cache/CDN copies. - **- Images disappear.**Disable lazy load or URL rewriting, purge caches, and inspect browser/network errors. - **- Bulk Smush stops.**Run smaller batches, check server resources and cron, and review plugin logs/status. - **- WebP is not served.**Verify the selected delivery method, CDN/server rules, cache, and browser response headers. - **- Pro service is unavailable.**Confirm WPMU DEV account connection and active entitlement. If the problem persists, reproduce it on staging, capture the exact error and relevant logs, and compare the behavior with nonessential plugins temporarily disabled. Restore the production site rather than troubleshooting destructively in place. # Updating the Plugin or Resource 1. 1. Back up uploads, review release notes, and test automatic optimization, lazy loading, CDN delivery, and a new upload on staging. 2. 2. Purge caches after updating delivery rules. 3. 3. Recheck quality and performance metrics rather than assuming the new version is faster. - **-**Confirm that the backup completed and can be accessed independently of WordPress. - **-**Review the official changelog and compatibility notes. - **-**Update during a low-risk window and keep a tested rollback path. - **-**Clear relevant caches and perform the product-specific functional tests listed above. # Uninstallation 1. 1. Disable CDN rewriting and lazy loading before deletion, then purge caches. 2. 2. Restore originals if required and available. 3. 3. Confirm whether generated WebP files and plugin data should remain before removing them. Deactivation and deletion are not the same as data removal. Confirm the product's current cleanup options, [Database](https://nippylaunch.com/encyclopedia/database/) tables, uploaded files, remote data, connected accounts, and continuing external billing or scheduled actions before removal. # Security & Best Practices - **-**Protect account/API connections. - **-**Restrict optimization and restore controls to trusted administrators. - **-**Back up media before bulk or lossy operations. - **-**Do not allow private media URLs to be exposed through a public CDN unintentionally. - vUse unique administrator accounts, least-privilege roles, HTTPS, and multi-factor authentication where supported. - **-**Keep the resource, WordPress, PHP, theme, and dependencies on supported versions. - **-**Store backups and recovery instructions outside the WordPress site. # Final Checklist - ✅A restorable backup was created before installation or major configuration. - ✅All required core plugins, themes, services, and accounts are active. - ✅The resource is installed and activated without WordPress or PHP errors. - ✅The product-specific initial and recommended settings are complete. - ✅The practical workflow was tested as an administrator and as the intended visitor/customer/member. - ✅Email, payments, webhooks, cron, cache, and integrations were tested where applicable. - ✅Security, privacy, consent, data retention, and access rules were reviewed.