Automattic has announced it will resume its contributions to the WordPress open-source project, following a brief pause that surprised many in the community. The update came through a blog post titled “Returning to Core”, published on Thursday evening.

the blog post reads.

“After pausing our contributions to regroup, rethink, and plan strategically, we’re ready to press play again and return fully to the WordPress project,” “Expect to find our contributions across all of the greatest hits —WordPress Core, Gutenberg, Playground, Openverse, and WordPress.org. This return is a moment of excitement for us as it’s about continuing the mission we’ve always believed in: democratizing publishing for everyone, everywhere.”

The announcement comes just one month after Automattic said that WordPress 6.8 would be the last major release for the entire year of 2025. This dramatic change in course has left many within the WordPress community wondering what happened behind the curtain.

Automattic reports that the break was utilized for a better understanding of the different ways WordPress is used around the world. Hence, the company emphasized that it is now more committed than ever to helping “grow and thrive the platform.” The post also mentions an incredible milestone; WordPress powers 43 percent of all sites on the World Wide Web.

What Changed?

What led to the reversal of Automattic’s decision remains unclear. However, sources familiar with the matter told TechCrunch that Automattic CEO Matt Mullenweg shared an internal post on Wednesday night, expressing his desire to release WordPress 6.9 later this year. That release would include an admin refresh and potentially something from WordPress’s new AI development team, which was just announced earlier this week. Mullenweg reportedly said in the internal note.

“I don’t think that will happen without our contributions,”

Speculation Around the Real Motives

Speculation has not been subdued by Automattic’s declared justifications for returning to WordPress development. According to some sources, the choice might have been impacted by pressure, either internal or external. Others think it’s a strategic change brought on by concerns about reputation or business requirements. Others suspect that Automattic’s ongoing legal dispute with WP Engine, a well-known WordPress hosting firm, may be connected to the move.

Since 2024, Automattic and WP Engine have been engaged in a legal battle. The main point of disagreement is Mullenweg’s claim that, in spite of its significant size and income, WP Engine makes insufficient contributions to the WordPress project. He believes the hosting company benefits from the open-source community’s work without giving back and that it profits from confusion between WordPress.org and commercial services like WP Engine. This led to Automattic banning WP Engine from WordPress.org and filing a lawsuit over unauthorized trademark usage.

Mullenweg has argued that WP Engine should either start paying a direct licensing fee or increase its contributions to WordPress. Otherwise, he believes the company should not be allowed to use the WordPress trademark. In response, WP Engine has pushed back, stating that it does not need a license and that Automattic has a flawed understanding of trademark law. WP Engine subsequently filed a countersuit against Automattic. Adding to the recent shakeups, Automattic also laid off 16% of its workforce last month. The company said the restructuring was necessary to improve agility, productivity, and profitability.

Our Opinion

Automattic’s return to contributing to WordPress is not just a course correction—it’s a critical one. While the pause may have offered time to reflect strategically, the reality is that WordPress thrives on active stewardship, especially from its founding company. Given that WordPress powers nearly half the web, any withdrawal, even temporary, sends ripples through the developer and business communities.

The recent announcement is encouraging, but it also raises important questions about leadership transparency and long-term commitment to open-source values. If this move was driven by internal pressures or external challenges like ongoing litigation, it underscores the need for stronger alignment between business objectives and community responsibilities. We believe that stepping back into the fold is a smart and necessary decision, but one that should come with greater consistency and clarity moving forward. The future of WordPress depends not just on code, but on trust.