React or Next.js — and does the template decide for you?
What choosing a framework actually commits you to, and how much of that a template locks in.
UT Studio6 min read
"React or Next.js" is not really a comparison — Next.js is React with routing, rendering and a build pipeline decided for you. The real question is whether you want those decisions made, and a template makes the answer for you either way.
What the framework decides
| Concern | React alone | Next.js |
|---|---|---|
| Routing | You choose a library | File-system routing |
| Rendering | Client, unless you build more | Server, static or client per route |
| Data fetching | Yours | Server Components, or yours |
| Build | Vite or similar, configured | Configured |
| SEO | Needs work | Server-rendered by default |
| Deployment | Static files anywhere | Node runtime, or static export |
When plain React is the better answer
- The application sits entirely behind a login and SEO is irrelevant.
- You are embedding into an existing page or an app shell you do not own.
- You want static files on a CDN and nothing else — no server, no runtime.
- You have strong opinions about routing and data, and want them.
When Next.js is
- Anything with public pages that need to be found.
- Mixed public and private surfaces in one product.
- You want the first paint to be correct rather than a spinner.
- You would rather spend the decisions elsewhere.
How much does a template lock in?
More than people expect on rendering, less than they fear on components.
- Components port easily. A well-built component reads props and renders; that is framework-portable.
- Routing does not. Moving from file-system routing to a router library is a rewrite of every route.
- Server Components do not port at all. They are a Next.js capability; plain React has no equivalent.
- Tokens and styling port completely. CSS is CSS.
The practical answer
If the template is Next.js and you want plain React, you are keeping the design and rewriting the plumbing — usually more work than it looks. Match the framework at purchase.
Both shapes
Templates mentioned here
Everything above is written against real products. These are the ones this page draws on.