The React Foundation launches: Meta hands React to eight members and the Linux Foundation

On February 24, 2026, the Linux Foundation announced the React Foundation at its Member Summit in Napa, California. The same day, Matt Carroll posted the news on react.dev: Meta no longer owns React, React Native or supporting projects such as JSX. The foundation owns them, and LF Projects, LLC hosts them under neutral governance.

The launch ended a process that started in October 2025.

From announcement to launch

1. October 7, 2025

   Seth Webster, Matt Carroll, Joe Savona and Sophie Alpert announce the plan on react.dev, with seven founding members. React Conf opens the same day.

2. Between the two posts

   Huawei joins, making it eight Platinum members.

3. February 24, 2026

   The foundation launches under the Linux Foundation. Ownership moves from Meta.

4. Next

   The team finalizes technical governance and moves repositories, websites and other infrastructure to the foundation.

The October post gave the reason in one line: React "has outgrown the confines of any one company." By then, outside contributors had grown in number and in the scope of their work.

Who sits at the table

Each member places a representative on the board of directors. Seth Webster serves as executive director. The board directs money and resources, and the October post lists its jobs: run React's GitHub, CI and trademarks, organize React Conf, and fund the ecosystem through grants and programs.

Neither post states a budget or a funding commitment from Meta. I found a figure in secondary coverage but not in the primary sources, so I left it out.

The board doesn't steer React

The foundation splits money from code. The board holds the projects and pays for shared work. Technical direction stays with the people who contribute to and maintain React, under a governance structure independent of the board. The October post sets one rule for that structure: no single company or organization should hold too many seats.

A Provisional Leadership Council now designs the structure. The launch post doesn't name its members and promises an update in the coming months. Until that post lands, the people who decided React's roadmap last year still decide it, and most of them work at Meta.

What changes for you

Your package.json stays the same. You install React from the same npm names, file issues in the same repositories until they move, and read the same docs. The foundation changes the risk profile and leaves the API alone.

Three things shift. Vendor risk drops: a Meta reorganization no longer decides React's future alone, since seven other companies with products on React pay into it. Feature priorities change: when React adds a feature, it now reflects the needs of Vercel, Expo, Microsoft and the others, and you can expect more attention on React Native and on frameworks outside Next.js. And funding gets a channel: the grants and programs give ecosystem libraries a place to apply for money, which matters if your app depends on a library with one tired maintainer.

Open questions

• Who sits on the technical council, and how many seats go to Meta engineers.
• When the repository and trademark transfers happen. The launch post gives no dates.
• Which ecosystem projects the grant programs fund first.
• Where React Conf goes next. Planning starts in the coming months.

This week

1. Add governance to your framework due diligence checklist, next to support policy, hiring market and migration cost. React now scores higher on that line.
2. List the community libraries your app can't live without. Once the grant programs open, nominate those first.
3. Watch react.dev for the technical governance post. It decides how much of this split works in practice.