How it works
React Router maps URLs to components and handles links, nested layouts and the back button without full page reloads. It can be used in three ways: as a plain router inside a single-page app, with data loaders and actions attached to each route, or as a full framework with server rendering and a Vite plugin.
Remix began as a framework built on top of React Router. Its own layer grew so thin that its features were merged into React Router 7 as framework mode, and Remix apps upgrade to it. The Remix name now belongs to Remix 3, a separate project that does not use React. React Router apps deploy to Node.js, Cloudflare Workers, Vercel, Netlify and other hosts through adapters.
React Router and Remix pros and cons
Pros
- One library, from a simple router up to a full framework
- Loaders and actions keep data and forms close to each route
- Built on web standards such as Request, Response and HTML forms
- Deploys to Node.js, serverless and edge hosts
Cons
- Frequent renames and API changes over the years make old guides confusing
- Smaller framework ecosystem than Next.js
- Server Components support is newer than in Next.js
When to use React Router and Remix
Pick it when
- Any React single-page app that needs routing
- Server-rendered React apps that lean on forms and web standards
- Existing Remix apps, which upgrade to it
Skip it when
- You want the largest pool of React framework examples and hosting guides
React Router and Remix pricing
Related terms
More in Frontend
Meta-frameworks