CensusPlugin profiles › WP Downgrade

WP Downgrade | Specific Core Version

Figures from the Plugin Directory Census · as of 28 Aug 2026

100,000

Active installs, lower bound

Group: 100,000 to 999,999 installs

1,208

Days since the last release

Group median: 12

4.8

out of 5, from 169 ratings

Group median: 4.7 (10+ ratings)

no threads

Support threads, two months

Group: 68.2%

Full profile on wordpress.orgShow on the mapCompare with your own plugins

What is WP Downgrade and who is behind it?

WP Downgrade is a WordPress plugin in the “Admin and backup” field, made by Reisetiger. It has been listed in the directory since 30 Apr 2016, so for 10 years. It is the only plugin by Reisetiger with at least 10,000 installs. With 100,000 to 199,999 active installs it belongs to the 100,000 to 999,999 installs group; its last release came 1,208 days before the reference date, and it is tested up to WordPress 6.2.

This is how the author describes the plugin on wordpress.org:

“Automatically downgrad or update to any WordPress version you want directly from the backend.”

Self-description on wordpress.org, retrieved on 10 Sept 2026

When was WP Downgrade last released?

The last release of WP Downgrade came 1,208 days before the reference date; the group median is 12 days. That makes WP Downgrade silent in the census, meaning no release for more than 365 days, as are 5.3% of the group.

WP Downgrade · 1,208 days today1 month3 months1 year3 years10 years
Each dot is a plugin in the 100,000 to 999,999 installs group, placed horizontally by days since its last release, on a logarithmic scale. The dashed line marks 365 days.

How many installs does WP Downgrade have?

WP Downgrade had 100,000 to 199,999 active installs on the reference date. Within its group, 219 plugins had a higher band and 179 plugins the same band.

The API reports installs only as a lower bound with one significant figure: 100,000 means at least 100,000 and at most 199,999.

Which WordPress version is WP Downgrade tested with?

On the reference date the plugin page on wordpress.org showed the notice “This plugin hasn’t been tested with the latest 3 major releases of WordPress”, because the “tested up to” field was below 6.9 (6.2). The notice describes only that field; it does not say whether the plugin runs on newer versions. 8.0% of the group carried it.

How does WP Downgrade compare with its group?

The group holds 399 listed plugins. 99.0% of them had a more recent last release than WP Downgrade; 5.3% had no release for more than 365 days.

FigureWP DowngradeGroup, 399 plugins
Days since the last release1,208median 12
Rating4.8 (169)median 4.7 (10+ ratings)
Support threads marked resolvednot stated68.2%
Tested up to6.247.6% on 7.1
Requires PHPnot statedmost often 7.4 (41.6%)

All values on the reference date

Slugwp-downgrade
AuthorReisetiger
Active installs100,000 to 199,999
Last release1,208 days before the reference date
Tested up toWordPress 6.2 · core on the reference date: 7.1
Requires WordPress3.0
Requires PHPnot stated
Rating4.8 out of 5 from 169 ratings
Support threads, two monthsnone in the window
Listed since30 Apr 2016
Total downloads1,676,713, updates included
Tagscore, downgrade, rollback, version, wp-core

Tags

TagPlugins with 10,000+ installs and this tagRank by installsMedian days since release
core311,208
downgrade32121
rollback42132
version63770
wp-core111,208

Rank 1 has the highest installation band among plugins with 10,000+ installs and this tag; equal bands share a rank.

Class of 2016

WP Downgrade has been listed since 30 Apr 2016. Of the 200 plugins with 10,000+ installs added in 2016, 87.0% released within the 365 days before the reference date.

Same group, shared tags

Not a recommendation; the same figures for comparison. Alphabetical.

PluginActive installsLast releaseRating
Advanced Automatic Updates20,000 to 29,9991,911 days before the reference date4.7 (61)
Change Admin Email50,000 to 59,999142 days before the reference date4.8 (140)
Display PHP Version30,000 to 39,9991,200 days before the reference date4.9 (35)
PHP Compatibility Checker200,000 to 299,99939 days before the reference date2.7 (131)
WP Rollback300,000 to 399,999121 days before the reference date4.9 (215)

Do you maintain WP Downgrade?

If you maintain WP Downgrade, you can link to this profile, for example from your readme or your website. Both snippets show this badge:

WP Downgrade in the Plugin Directory Census 01/2026

HTML

<a href="https://hafenstudios.com/en/census/plugins/wp-downgrade/"><img src="https://hafenstudios.com/census/plugins/badge-en.svg" alt="WP Downgrade in the Plugin Directory Census 01/2026" width="220" height="40"></a>

Markdown

[![WP Downgrade in the Plugin Directory Census 01/2026](https://hafenstudios.com/census/plugins/badge-en.svg)](https://hafenstudios.com/en/census/plugins/wp-downgrade/)

The image is loaded from hafenstudios.com; as with every request, our server records the usual access data, which is deleted after 14 days. If you prefer not to, use a plain text link.

A value is wrong? Write to moin@hafenstudios.com; a documented correction leads to a new version.

How to cite

hafenstudios (2026): WP Downgrade | Specific Core Version, profile in the Plugin Directory Census 01/2026, reference date 28 Aug 2026. https://hafenstudios.com/en/census/plugins/wp-downgrade/

Source and status

All values come from the full pull of the public wordpress.org API on 28 Aug 2026 (reference time 21:56:30 UTC). The analysis and text on this page are available under CC BY 4.0; the raw values come from the public wordpress.org API and are in the raw data. How the count was made is set out in the method, what the fields do not say under limits. hafenstudios builds WordPress plugins itself, see the conflict of interest. Corrections to moin@hafenstudios.com; a documented correction leads to a new version. From issue 02 this page will also show the change since the previous reference date. Collected and prepared by Horst Wenzel.

Plugin names and trademarks belong to their owners. hafenstudios is not affiliated with the authors named here.