Remix 3 Beta Preview Ships an Independent Full-Stack Framework Built on Web APIs, Forking From React Toward Preact
Remix released the Remix 3 beta preview on April 30, the first hands-on cut of a full-stack rebuild that drops React in favor of a Preact fork and brings routing, auth, forms, data, and UI under one package.
Overview
The Remix team released the Remix 3 beta preview on April 30, 2026, the first publicly installable build of a framework rebuild that has been signaled for nearly a year. In an announcement post, co-founder Michael Jackson wrote: “Today we’re releasing the Remix 3 beta preview. This is still a pre-release.” The same post says the release “is not production ready yet, and there is still a lot to do.”
The beta is installable today with npx remix@next new my-remix-app, per the Remix blog. The team promises weekly updates from here on: “we’re going to keep moving quickly, following up with new features and releases every week,” Jackson wrote.
What Remix 3 Is
Where earlier versions of Remix were a “center stack” framework focused on routing and rendering on top of React, Remix 3 is being shipped as a single full-stack package. The blog post describes the scope as: “Not just routing. Not just rendering. Not just data. The whole thing: routes, request handlers, responses, middleware, sessions, auth, forms, uploads, assets, data and database management, UI components, theming, networking, tests … everything.” The same post stresses that under the hood “Remix 3 is built from small, composable packages that can stand on their own.”
The design rationale is framed in plain terms by Jackson: “We wanted to build something simpler, faster, and closer to the web itself,” and the framework “should give you leverage before it gives you more decisions to make about which dependencies to use,” according to the same blog post.
One of the more visible new primitives is the frame. As Jackson describes it on the Remix blog: “A frame is server-rendered UI with a src. The client can load it, navigate it, or reload it independently while the server keeps rendering HTML.” The intent, the post says, is “server/client communication that feels like the web: URLs, requests, responses, and markup instead of a separate RPC layer.”
How Remix Got Here
The beta is the latest step in a roadmap Remix laid out in May 2025. In the “Wake up, Remix!” post, co-founders Michael Jackson and Ryan Florence described Remix 3 as “a reimagining of what a web framework can be; a fresh foundation shaped by decades of experience building for the web,” focused on “simplicity, clarity, and performance, without giving up the power developers need.”
The most consequential decision in that earlier post was a break with React. Instead of continuing as a layer over React, the team wrote that “we’re starting with a fork of Preact, a mature virtual DOM library already used heavily at Shopify, Google, and countless others,” according to the Remix blog. The May 2025 post laid out six principles for the new framework — model-first development, building on web APIs, a runtime-only philosophy, avoiding dependencies, demanding composition, and distributing cohesively — as the guardrails for the rebuild.
The context for that pivot is summarized in a GitHub discussion about the project’s earlier name change, which quotes the Remix team’s prior framing of the relationship: “Remix has always just been a layer on top of React Router - and that layer has been shrinking over time.” After Remix v2 merged into React Router v7, the Remix packages went on what the team called a “little nap” while the team focused on shipping React Router v7. Remix 3 picks the name back up but, as the same discussion thread makes clear, the result is not a thin wrapper around React Router — it is new software with a different runtime.
Community Reaction
Reaction in the developer community has been mixed. On Hacker News, one commenter on the launch thread captured the most common form of skepticism: “I migrated my Remix 2 app to react router 7 and I think it’s great…so what is Remix 3 adding?” Other contributors to the same thread pushed back, pointing out that the beta uses TypeScript and esbuild rather than rolling its own bundler, and arguing that the project’s case is precisely that it sits closer to the web platform than the React-centric stack it leaves behind.
What We Don’t Know
Neither the beta preview post nor the earlier “Wake up, Remix!” announcement commits to a date for a 1.0 release. The beta is explicitly not production-ready, and the team’s stated cadence is weekly updates rather than a fixed milestone schedule. The Remix blog post also does not publish performance comparisons against existing React-based stacks, and it does not list which third-party React libraries — if any — will be portable to the new runtime via shims. Migration guidance for projects that moved from Remix v2 to React Router v7 has not been published alongside the beta.