Skip to content
Community

WordPress Plugins Team Reports 4,790 in Queue with 254 Approvals in April 2026

The WordPress Plugins Team reports a backlog of 4,790 plugin submissions with 254 approvals and 470 rejections in April 2026, highlighting ongoing review challenges.

WordPress Plugins Team Reports 4,790 in Queue with 254 Approvals in April 2026

The WordPress Plugins Team has released their status update for April 27, 2026, revealing a heavy backlog in the plugin review queue alongside ongoing approval and rejection activity. This latest data underscores persistent challenges in processing plugin submissions efficiently while maintaining quality and security standards.

Key Takeaways

  • The plugin review queue currently holds 4,790 submissions, with 4,113 older than seven days.
  • In the past week, 254 plugins were approved, while 470 were rejected, reflecting rigorous review standards.
  • New submissions waiting processing number 657, indicating ongoing pressure on review resources.
  • Help Scout support conversations remain high with 1,558 total, including 892 new inquiries this period.
  • The data highlights the need for improved review workflows and community engagement to reduce backlog.

Current Plugin Queue Dynamics

As of April 27, 2026, the WordPress Plugins Team is managing a substantial queue of 4,790 plugin submissions. This figure includes new and pending plugins, signaling a heavy workload for reviewers. Notably, 4,113 of these have been in the queue for more than seven days, indicating delays that may impact developers waiting for approval.

Within the last week, 657 new plugins entered the queue without any processing or response, while 4,133 are pending with some reviewer interaction. Of those pending, 3,609 await author action, suggesting that many submissions require further information or revisions before final decisions can be made. A smaller subset of 440 are pending reviewer action, with 84 still awaiting the initial reviewer email.

These statistics reveal a bottleneck in the review pipeline, where both reviewers and plugin authors must collaborate more effectively to expedite approvals and maintain the ecosystem’s health.

The team approved 254 plugins and rejected 470 within the recent review period. The higher rejection rate reflects the Plugins Team’s commitment to quality and security, filtering out submissions that do not meet WordPress.org standards. This rigorous scrutiny is essential given the potential risks plugins can introduce, from security vulnerabilities to performance degradation.

Additionally, 33 plugins were closed, typically indicating removal of abandoned or problematic submissions. The volume of rejections and closures underscores the importance of clear submission guidelines and thorough reviewer oversight.

Help Scout Support Activity

Support requests managed through Help Scout totaled 1,558 conversations during this period, with 892 new inquiries. The average of 194 conversations per day, peaking on Sunday, indicates active engagement from the community seeking assistance on plugin submissions, reviews, or other related matters.

The Plugins Team responded with 2,609 replies and initiated 758 emails, demonstrating a responsive support operation despite the backlog challenges. Efficient communication is vital to help authors navigate the complex review process and reduce friction.

Review Process Challenges and Community Impact

The large queue and significant number of pending plugins waiting on author or reviewer action highlight ongoing challenges in scaling the review process. The Plugins Team operates with volunteer reviewers and limited resources, which can slow processing times and frustrate developers.

For plugin authors, understanding the importance of promptly responding to reviewer feedback and ensuring compliance with guidelines can accelerate approvals. For reviewers, maintaining detailed, clear communications and prioritizing queue management is key to sustaining ecosystem trust.

Community initiatives to recruit and train new reviewers, improve tooling, and automate parts of the review workflow could help alleviate these bottlenecks. Our previous coverage of WordPress plugin review dynamics shows that these issues have persisted over years, requiring fresh strategic approaches alongside steady operational improvements.

What This Means for WordPress Users

For WordPress developers and agencies submitting new plugins or updates, this report signals a need for patience and proactive engagement with reviewer feedback. Delays in the review queue can impact project timelines, so planning submissions well in advance of release deadlines is advisable.

Site owners relying on plugins should continue to prioritize plugins with active maintenance and clear review histories, as the approval process remains a critical gatekeeper for ecosystem quality and security. Monitoring plugin update activity and community feedback remains essential.

For the broader WordPress community, these statistics emphasize that the plugin repository’s health depends on collaborative efforts across authors, reviewers, and support teams. The persistent backlog suggests that investment in reviewer capacity and smarter automation will be necessary to keep pace with growing plugin demand.

As WordPress continues to evolve, the plugin review process will remain a cornerstone of ecosystem trust. Staying informed about these operational realities helps all stakeholders make better decisions and advocate for improvements.

Frequently Asked Questions

Why is the WordPress plugin review queue so long?

The queue length results from a high volume of submissions combined with limited reviewer resources, many of whom volunteer their time. Complex review requirements and the need for back-and-forth communication with authors also contribute to delays.

What can plugin authors do to speed up approval?

Authors should carefully follow submission guidelines, promptly respond to reviewer feedback, and ensure their code meets security and compatibility standards. Clear communication helps reviewers move plugins through the process faster.

How does the rejection rate affect plugin quality?

A higher rejection rate reflects the team’s emphasis on maintaining high quality and security standards. It protects the ecosystem by preventing low-quality or vulnerable plugins from reaching users.

Is there an effort to add more plugin reviewers?

Yes, the community actively seeks to recruit and train new volunteer reviewers to expand capacity. Improved tooling and automation are also being explored to streamline the review process.

Related News