LifterLMS says 1.7 million downloads. WordPress.org says 10,000 active installs. Both are true.
Picking a WordPress LMS means reading vendor numbers carefully. The gap between cumulative downloads and active installs is the clearest example, and understanding it tells you more about choosing course software than any feature table.

Table of contents
If you are choosing software to sell courses on WordPress, you will spend a lot of time reading numbers that are technically accurate and quietly incomparable. LifterLMS is a good case study, because its own figures and the public ones look wildly different — and neither is wrong.
The two numbers, side by side
LifterLMS puts its own track record at more than 1.7 million plugin downloads, over 130 million course enrollments, a 4.8/5 rating, users in 169 countries, and independent ownership for 12+ years.
The public WordPress.org listing for the free core plugin currently shows 10,000+ active installations, a 4.8-star rating from around 390 reviews, with the plugin updated within the last few days.
That is a 170-fold gap on the headline figure, and the explanation is mundane: downloads and active installs measure different things.
- Cumulative downloads counts every download since launch — every fresh install, every manual update package, every test site, every site that installed it and removed it a week later. Over twelve years, it accumulates and never decreases.
- Active installs is WordPress.org's estimate of sites currently running the plugin, right now, rounded down to a coarse bracket.
Neither is dishonest. But only one of them tells you how many people are running this today, and it is the smaller one.
What the active-install number does and doesn't capture
Being fair to LifterLMS here matters, because the naive reading is also wrong.
The 10,000+ figure covers the free core plugin as distributed through WordPress.org. LifterLMS's actual business is the paid layer — add-ons and bundles that a serious course site buys, sold and updated directly rather than through the repository. Sites running those are not necessarily reflected in the repository's estimate, and a plugin whose real customers are on commercial licences will always look smaller in that bracket than it is.
The enrollment figure points at the same thing: 130 million enrollments across a comparatively small number of sites implies the sites using it are substantial, not hobby projects. That is a genuinely relevant signal for a buyer, and arguably a better one than install count.
So the useful discipline is not "distrust vendor numbers". It is compare like with like: when you evaluate three LMS plugins, put their WordPress.org active installs next to each other, then put their vendor claims next to each other. Never one against the other.
The ownership point is more than trivia
One item in that list deserves more weight than it usually gets: independently owned for over twelve years.
WordPress plugins have been consolidating hard. A plugin gets acquired, the roadmap changes, the pricing model is revised at renewal, and the free tier that convinced you to build on it gets narrowed. If your entire course business — content, enrolments, payment history — lives inside that plugin's data model, you are exposed to a decision you have no part in.
Twelve years of independent ownership is not a guarantee of anything. But a company that has stayed independent through the entire acquisition wave has at least demonstrated it is not built to be flipped. On infrastructure you plan to run for years, that is a real consideration, and it costs nothing to check for any plugin you are evaluating.
The founder story that goes with it — Chris Badgett moving from Alaskan sled dog guide to edtech CEO — is charming and tells you nothing about the software. Filed accordingly.
The question no LMS comparison asks
Feature tables for course plugins compare quizzes, drip content, certificates and payment gateways. They almost never mention the thing most likely to cause you grief.
An LMS is the heaviest thing most people ever install on WordPress. Progress tracking writes to the database on nearly every student interaction. Enrolment, completion and reminder logic runs on scheduled tasks. Reporting queries scan tables that grow with every student. On the shared hosting most WordPress sites start on, that is exactly the profile that produces the intermittent, hard-to-reproduce slowdowns we picked apart in why WordPress sites randomly slow down.
Before you compare features, answer these:
- Where is video hosted? Not on your web host. A course platform serving video from the same server as the site is a bill and an outage waiting to happen.
- What happens at 500 concurrent students? Ask the vendor, and ask your host separately. The answers rarely match.
- Can you export enrolments and progress? If the answer is a CSV of students but not their progress, you cannot ever migrate without losing history.
- What does a renewal cost in year three? Launch pricing on add-on bundles is not the number that matters.
Hosting choice does more for an LMS site's reliability than plugin choice does. Our Hostinger vs SiteGround vs Bluehost comparison covers the tiers where this starts to matter.
Where LifterLMS fits
It suits people building a course business on their own infrastructure — you want your own domain, your own checkout, your own student data, and no platform taking a slice or changing terms. The free core plugin means you can build the entire structure of a course before spending anything, which is a genuinely fair way to sell software.
It suits you poorly if you want to publish one small course quickly and have no interest in maintaining WordPress. In that case a hosted platform is less work, and our guide to selling digital products covers the lighter routes.
Bottom line
The 1.7 million and the 10,000 are both real; they answer different questions. Ask the vendor for enrolments and revenue-scale evidence, ask WordPress.org how many sites run it today, and never let one stand in for the other.
Then spend your remaining research time on hosting and data export rather than the feature grid. Those are the two decisions you cannot cheaply reverse once students are enrolled.
Sources


