The WordPress Plugins Team continues to grapple with a substantial backlog as plugin submissions soar in 2026. As of early May, the team reported over 4,700 plugins in various stages of review, highlighting ongoing challenges in maintaining the plugin repository’s quality and responsiveness.
Key Takeaways
- There are currently 4,770 plugins in the WordPress review queue, with 4,105 older than seven days.
- From 546 plugin requests, 385 were approved while 209 were rejected, reflecting a rigorous review process.
- The majority of pending plugins (3,750) await author action, indicating common revision requests before approval.
- Help Scout support traffic remains high, averaging 215 conversations daily, with 1,725 total conversations ongoing.
- Review bottlenecks persist, emphasizing the need for more reviewers or improved workflow efficiency.
Understanding the Current Plugin Review Landscape
Plugin review is a cornerstone of the WordPress ecosystem’s security and quality assurance. Every plugin submitted to the official WordPress Plugin Directory undergoes rigorous automated and manual checks before approval. The team’s latest statistics reveal a persistent queue growth, a pattern consistent with increasing demand for WordPress extensibility.
As of the report dated May 4, 2026, the Plugins Team is managing 4,770 plugins in the queue. This number includes new submissions, ongoing revisions, and pending rechecks. Notably, 4,105 of these plugins have been in the queue for longer than seven days, indicating significant delays in processing times.
Despite these challenges, the approval rate remains robust. Out of 546 plugin requests processed recently, 385 were approved and 209 rejected. This rejection rate of approximately 38% demonstrates the team’s commitment to upholding standards, filtering out plugins that fail to meet security, compatibility, or quality benchmarks.
Queue Dynamics and Workflow Challenges
The largest segment of pending plugins, about 3,750, are waiting on authors to respond to reviewer feedback. This phase typically involves code revisions, documentation improvements, or clarifying security implementations. Another 450 plugins await reviewer action, with 92 of these not yet having received the initial review email.
This distribution indicates that author responsiveness is a critical factor in queue clearance. Plugins stuck in revision cycles prolong overall processing times, contributing to the backlog. Furthermore, the relatively small number of plugins pending reviewer action suggests that the bottleneck is influenced more by the volume of submissions and author engagement than by reviewer availability alone.
In practice, the review process involves multiple steps: initial automated scans for security risks, manual code review for adherence to WordPress coding standards, and iterative communication with plugin authors for necessary changes. This complex workflow requires coordination among volunteers and team leads, often complicated by resource constraints.
Help Scout Support Queue Reflects Community Demand
Support for plugin developers and users is integral to the Plugins Team’s operations. Current stats from the Help Scout system show 1,725 total conversations, with 900 new conversations recently initiated. The team handles an average of 215 conversations daily, with Tuesday identified as the busiest day. Notably, 3,056 replies have been sent, reflecting active engagement with the community.
This high volume of support interactions signals that plugin developers frequently seek guidance during the review process, especially around compliance and technical standards. Efficient support helps reduce turnaround times by clarifying expectations and assisting in troubleshooting common issues.
Historical Context and Ecosystem Implications
The plugin review backlog has been a recurring theme in WordPress community discussions for several years. Increasing plugin submissions correlate with WordPress’s expanding market share and the growing reliance on plugins for site functionality. However, the volunteer-driven nature of the review team makes scaling challenging.
Over time, the team has implemented improvements such as automated security scans and enhanced reviewer tools. Yet, the volume of submissions continues to outpace these measures. Larger agencies and freelancers often experience delays impacting project timelines, underscoring the need for systemic enhancements.
For context, our previous plugin team coverage tracks the same metrics week-over-week, highlighting trends in submission growth and approval rates.
What This Means for WordPress Users
For plugin developers, the current queue emphasizes the importance of thorough preparation before submission. Ensuring adherence to WordPress coding standards, security best practices, and clear documentation can minimize revision cycles and accelerate approval.
Site owners and agencies should factor potential delays into project timelines when relying on new plugins from the official repository. Where possible, working with established plugins or private repositories may reduce dependency on the public review queue’s pace.
From a broader perspective, the backlog signals ongoing challenges in WordPress’s open ecosystem governance. The balance between maintaining high standards and accommodating growth requires continued investment in automation, reviewer recruitment, and community education.
We recommend agencies and plugin authors engage actively with the review process, responding promptly to feedback to help reduce queue times. Additionally, WordPress leadership might consider incentives or structural changes to expand reviewer capacity, ensuring the ecosystem’s health amid growing demand.
Frequently Asked Questions
Why is the WordPress plugin review queue so long?
The queue length results from a high volume of submissions combined with the detailed manual review process required for security and quality assurance. Many plugins require multiple rounds of author revisions, which can extend processing times.
What can plugin authors do to speed up approval?
Authors should thoroughly test their plugins, follow WordPress coding standards, and provide clear documentation. Promptly addressing reviewer feedback and communicating openly helps minimize delays.
How does the plugin review process impact WordPress site owners?
Delays in plugin approval can affect site owners who depend on new or updated plugins for features and security. Awareness of potential wait times enables better planning and risk management.
Is the plugin review process expected to improve soon?
While WordPress continues to enhance automated checks and reviewer tools, the current backlog suggests improvements will require more reviewer participation and possibly process innovations.
