Knowledge base
When an older version is the right download, which older versions you can get, and where to find them in the app.
Almost every site should run the current version of our plugins — it has every fix we have made. An older version is the right download in two situations only:
older PHP than the current release needs, and upgrading those is not something you can do today.
looked at. Take a backup before you swap versions.
For every plugin we keep the newest release of each of the two previous major versions, alongside the current one. A major version is the first two numbers: when 1.2.3 is current, you can also download the newest 1.1 release and the newest 1.0 release.
We offer the newest release of each major version rather than every release, because the newest one carries every fix that version ever received. A plugin that is still on its first major version has nothing older to offer yet, and the app says so.
Sign in to the app and open Downloads, then the Older versions tab. Each plugin lists its current release and its older ones, with the release date, the WordPress version it was tested against, the PHP version it needs, and the SHA-256 checksum of the file so you can check the download before you install it.
If you can download a plugin's current version, you can download its older versions too — a plugin included with your plan or licence is included in every version we list.
In WordPress, deactivate and delete the plugin (your settings are kept by the plugins that store them in the database), then Plugins → Add New Plugin → Upload Plugin and choose the older zip. On a site we host, tell us in a ticket that you have pinned an older version, so an automatic update does not replace it before you are ready.
Move back to the current version as soon as the site can take it.
What we have been writing about hosting, SEO and running sites at scale.
How hosting shapes indexing and link equity in 2026: keeping pages indexed, vetting aged domains before you build on them, link building without a footprint, and an honest line on what infrastructure can and cannot do for SEO.
Read the post →A practical checklist for fast, secure WordPress: server-level caching, a per-site object cache, the handful of plugins worth running, keeping the stack current, and the WooCommerce pages you must never cache.
Read the post →What actually separates good managed hosting from a cheap box with a control panel — migrations, backups, isolation, real caching and honest scaling — and how to judge it before you commit.
Read the post →Support is included on every plan, the desk is open 24 hours a day, and you can write to us in any of our 58 languages — we answer you in yours.
Contact support → All articles →