PROVIDER Β· WordPress image optimisation plugin
ShortPixel
ShortPixel is a WordPress image optimisation plugin from Romania supporting batch compression, WebP and AVIF conversion, and reversible original backups, with an optional CDN for cleaning up years of accumulated images.
4.1pts
Pros
Cons
Product Information
Detailed Notes
Overview
Developed in Romania, ShortPixel is one of the most widely used image optimisation plugins in the WordPress ecosystem. Compression, WebP and AVIF conversion, and media library batch processing all live in the admin, with an optional image CDN so both historical and newly uploaded images are covered.
For Media Optimization work it solves the most practical problem, where a site accumulates thousands of unoptimised images over years and manual processing is not realistic. Batch optimisation handles the whole library in one run and can keep original backups for rollback, which is far safer than irreversible compression.
The limits are ecosystem and quota. It is a WordPress plugin unavailable to other stacks, and optimisation consumes credits per image, so large libraries burn allowance in a single batch that needs tier planning.
Core Strengths
- Batch optimisation across the WordPress media library handles years of accumulated images in one run
- WebP and AVIF conversion that pairs with picture tags or a CDN for capability-based output
- Optional original backups with one-click restore when compression results disappoint
- A built-in image CDN option improves delivery and format adaptation without migrating the site
Product Ecosystem
Batch optimisation and formats
Process at lossy, lossless, or smart levels and generate WebP or AVIF copies. Compare quality on a sample first, especially for illustrations and gradient-heavy assets.
Backups, restore, and CDN
Original backups are the safety net for over-compression, and the CDN option suits sites that cannot change internal references. Confirm compatibility with existing caching plugins before enabling it.
Drawbacks
- WordPress only, unavailable to other stacks
- Credits are consumed per image, so large libraries burn allowance in a single batch
- Overlaps with other image and caching plugins, where conflicts are costly to debug
- With the CDN enabled, image requests go to a third party, requiring privacy assessment
Use Cases
- Slimming a WordPress media library (β β β β β ) - Batch processing is its core value
- Moving to WebP or AVIF while keeping originals (β β β β β) - Backups and restore make format migration reversible
- Non-WordPress sites (β ) - The plugin form factor rules it out
- Highly privacy-sensitive sites (β β β ) - The CDN routes requests to a third party and needs review
Pricing
| Plan | Price | Scope |
|---|---|---|
| Free allowance | 100 images per month | Enough for small sites to validate |
| Image credit packs | One-off or monthly | Unit price falls with volume |
| CDN and batch add-ons | Usage-based | CDN bandwidth billed separately |
Credits are consumed per image, with one-off packs suiting a historical cleanup and monthly plans suiting ongoing uploads. Count the existing library first, then decide between a single sweep and spreading the cost monthly.
FAQ
-
Does compression destroy originals? Backups are kept by default with one-click restore, while disabling them makes compression overwrite files. Keep backups for long-term operations at the cost of disk space.
-
Does WebP need extra setup? The plugin generates WebP copies and serves them when supported, but some caching plugins override that logic, so verify rewrite rules and MIME configuration.
-
Is it suitable for large libraries? Yes with quota planning, since optimising tens of thousands of images consumes many credits. Run in batches and check quality and page rendering after each.