If you're choosing between frameworks today, treat 'Remix' as historical and evaluate React Router v7 (or Next.js) on their current docs instead.
About
In practice. What you can do with Remix.
Remix popularized a full-stack React model built on nested routes, loaders, and actions: fetch and mutate data on the server, render on the server first, and enhance progressively on the client. It shipped as an open-source, MIT-licensed framework with adapters for multiple hosting runtimes.
In 2024 the Remix team folded this framework directly into React Router v7, describing the Remix packages as taking 'a little nap' rather than continuing independent development. Existing Remix v2 apps keep working and can move to React Router v7 mainly by renaming imports.
A separate project also called 'Remix' (v3) was announced in 2025, but it drops React entirely in favor of a custom component model forked from Preact, and is still in beta. For anyone evaluating the tool this catalogue entry describes, React Router v7 is the maintained continuation.
Practical uses
Existing Remix v2 codebases that need to keep running and eventually migrate their imports to React Router v7.
Learning the loader/action/nested-route model, since it's the same model now shipped as React Router v7's framework mode.
Features & use cases
Nocode web
Pros and cons. What Remix does well, and what to expect.
Pros
Solid, battle-tested routing/data-loading model that lives on, unchanged in spirit, inside React Router v7.
Open source, MIT-licensed, with a documented low-friction migration path.
Deployable to several runtimes (Node, Cloudflare, Deno) rather than tied to one host.
Cons
Starting a brand-new project as 'Remix' today is confusing: the React framework is dormant, and the active 'Remix' project is an unrelated, pre-release, non-React tool.
No new features or roadmap for the React-based version; all forward development happens under React Router.
When it makes sense. Keep Remix, or challenge it?
Keep if
You already run a Remix v2 app and just need it stable while you plan a React Router v7 migration.
Challenge if
You're starting a new full-stack React project: go straight to React Router v7 instead of Remix.
Our verdict. What to know about Remix.
Why this verdict
Great
Added value
Its core ideas (loaders, actions, nested routes) were valuable enough to become the basis of React Router v7 itself, but the standalone product is no longer where that value is being developed.
Simplicity
File-based routing and conventions get a project running quickly, though understanding loaders/actions/server vs client boundaries takes some ramp-up.
Fit for purpose
Delivers on server rendering and progressive enhancement as advertised, without requiring extra libraries for basic data loading.
Performance
Handles nested layouts, parallel data loading, and multi-runtime deployment well for typical full-stack apps, matching category leaders.
Reversibility
MIT-licensed and open source, and the migration path to React Router v7 is documented as an import rename rather than a rewrite.
