Plugin how-tos · Explainer
What Is the WordPress Plugin Repository? Explained

Short answer
The WordPress plugin repository is the official free plugin directory on WordPress.org. Developers publish open-source plugins there after a review, and site owners install and update them straight from the Plugins screen in the dashboard. Every plugin must follow the WordPress.org plugin guidelines and use a GPL-compatible license.
Key takeaways
- The repository is WordPress.org's free, official plugin directory.
- Plugins > Add New Plugin in your dashboard searches the repository directly.
- Every listed plugin must follow the detailed plugin guidelines and use a GPL-compatible license.
- Check last update, tested version and support threads before installing.
- Closed plugins stop getting updates, so replace them if the reason is security.
What is the WordPress plugin repository?
The WordPress plugin repository is the official, free directory of plugins at WordPress.org, where developers publish open-source plugins and site owners search, install and update them.
You may see it called the plugin directory, the plugin repo or simply WordPress.org plugins. All three names mean the same thing: the collection at wordpress.org/plugins.
The repository holds tens of thousands of plugins, from small single-purpose tools to large projects such as WooCommerce. Our article on how many plugins are on WordPress.org tracks the count.
Every plugin listed there is free to download. Some are complete products, while others are free versions of plugins that also sell paid upgrades elsewhere.
How does the plugin repository connect to your site?
The Plugins > Add New Plugin screen in your WordPress dashboard is a search window into the repository, so installing a plugin there downloads it straight from WordPress.org.
When you search for a plugin in your admin area, WordPress asks the WordPress.org API for matching results. Clicking Install Now downloads the zip from the repository and unpacks it on your server.
Updates work the same way. WordPress checks the repository regularly for new versions of your installed plugins and shows an update notice when one is available.
Plugins from other sources, such as premium plugins you buy, do not come through this screen. You upload them as zip files, and they use their own update systems. Our explainer on what a WordPress plugin is covers the difference.
What information does each plugin page show?
Each plugin page shows a description, screenshots, installation notes, FAQ, changelog, ratings, active installation count, last update date, tested WordPress version and a link to its support forum.
These details help you judge a plugin before you install it. Look for:
- Last updated: a plugin untouched for years may not work with current WordPress.
- Active installations: a rough sign of how widely used and tested it is.
- Tested up to: the latest WordPress version the developer has checked.
- Requires PHP: the minimum PHP version it needs.
- Ratings and reviews: read the recent ones, not just the average.
- Support forum: check how many recent threads are resolved.
The Advanced View link on each page shows download history and older versions. That is useful if you need to roll back after a bad update.
Who runs the WordPress plugin repository?
The repository is run by WordPress.org and reviewed by the volunteer Plugin Review Team, which checks new submissions against the plugin guidelines before they go live.
The team publishes updates on its Make WordPress Plugins blog. It reviews every new plugin, handles guideline reports and can close plugins that break the rules or have security problems.
Reviews look at code safety, licensing and behavior, not at whether a plugin is good. A listed plugin has passed the guidelines, but quality and support still vary widely.
What rules must plugins in the repository follow?
Plugins must follow the WordPress.org detailed plugin guidelines, which require a GPL-compatible license, no hidden tracking without consent, no obfuscated code, and honest, non-spammy behavior.
The full list lives in the detailed plugin guidelines in the Plugin Handbook. The main points are:
- GPL-compatible license: code and included assets must use a license compatible with the GNU General Public License.
- Human-readable code: no obfuscated or packed code that hides what it does.
- No tracking without consent: plugins cannot collect user data without clear opt-in.
- No trialware: free plugins cannot lock built-in features behind a payment or time limit.
- Respectful admin experience: no hijacking the dashboard with excessive notices or ads.
- No external code execution: plugins cannot load executable code from third-party servers.
These rules are why plugins from the repository are generally safer than random downloads. They do not guarantee a plugin is bug-free.
How is the repository different from premium plugin marketplaces?
The repository only lists free, GPL-licensed plugins reviewed against WordPress.org rules, while marketplaces and vendor sites sell paid plugins with their own review standards and licensing.
| Feature | WordPress.org repository | Premium vendors and marketplaces |
|---|---|---|
| Price | Free | Paid, usually yearly licenses |
| Install from dashboard | Yes | Usually by zip upload |
| Automatic updates | Built in | Through the vendor's license system |
| Review process | Plugin Review Team guidelines | Varies by vendor or marketplace |
| Support | Public forum, volunteer or developer | Usually ticket-based, included with license |
| Source code | Open and public | Often GPL, but only sent to buyers |
Many developers use both. They list a free version in the repository and sell a Pro add-on from their own site.
How do developers submit a plugin to the repository?
Developers upload a zip on the WordPress.org add plugin page, wait for the review team's feedback, then publish code through the Subversion (SVN) repository they are given.
- Create a WordPress.org account
- Prepare the plugin with a valid readme.txt file
- Submit the zip on the add your plugin page
- Respond to any review emails and fix issues
- Once approved, commit the code to the SVN repository
- Tag a release so it appears for users
Review times vary with the size of the queue. The Plugin Handbook explains SVN, readme headers and release tagging in detail.
After launch, developers ship updates by committing new code and tagging a new version. Our guide on how to update a plugin on WordPress.org walks through that process.
What happens when a plugin is closed in the repository?
A closed plugin is removed from search and can no longer be downloaded, usually because of a security issue, a guideline breach or the developer's request.
Sites that already have it installed keep running it. They simply stop getting updates, and WordPress may show a notice that the plugin is no longer available.
If a plugin you rely on is closed for security reasons, deactivate it and look for an alternative. Our guide on what happens when a plugin is closed on WordPress.org explains how to check the reason and what to do next.
Are plugins from the repository safe to use?
Repository plugins are reviewed and can be closed quickly when problems appear, which makes them safer than unofficial downloads, but you should still check updates, reviews and support before installing.
Security issues are found in popular plugins from time to time. The difference is that the repository has a process to push fixes and close abandoned plugins.
Keep plugins updated, delete ones you no longer use, and avoid installing several plugins that do the same job. Our guide on enabling automatic plugin updates shows how to keep them current.
Never download repository plugins from third-party mirror sites. Always install them from your dashboard or directly from WordPress.org.
Can every WordPress site use the plugin repository?
Self-hosted WordPress sites can install any repository plugin, while WordPress.com sites need a plan that allows plugins, and some managed hosts block specific plugins.
Managed hosts often ban plugins that duplicate their own features, such as caching or backup tools, or that cause heavy server load. Check your host's list if an install is refused.
Multisite networks let only the network admin install plugins. Site admins can then activate the ones the network makes available.
Frequently asked questions
Is the WordPress plugin repository free?
Yes. Every plugin in the repository is free to download and use. Some developers offer paid upgrades or add-ons on their own websites, but the version listed on WordPress.org itself costs nothing.
Is the plugin repository the same as the plugin directory?
Yes. Plugin repository, plugin directory and plugin repo all refer to the same collection of free plugins on WordPress.org. Repository is the older name, coming from the Subversion code repository behind each plugin.
How long does plugin review take on WordPress.org?
It depends on the size of the review queue and how many issues the reviewers find. Some plugins are approved within days, while others take several weeks. Clean code and a complete readme file help speed things up.
Can I sell a plugin through the WordPress plugin repository?
No. The repository only hosts free plugins. You can list a free version there and sell a premium add-on from your own website, as long as the free plugin does not lock its built-in features behind payment.
Why can't I find a plugin in the repository anymore?
It was probably closed, either by the developer or by the review team because of a security issue or guideline breach. Closed plugins disappear from search, but the page usually shows a notice explaining the closure.
Sources
- WordPress Plugins WordPress.org
- Detailed Plugin Guidelines WordPress Developer Resources
- Add Your Plugin WordPress.org
- Make WordPress Plugins Make WordPress
- GNU General Public License v2.0 GNU Project
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
Related guides
About the editors
Researched from the primary sources listed above and checked against our editorial rules before publishing.


