Astro vs Next.js
Sources verified · Sources (8)
For a publishing site, ask how much of each page is content and how much is application UI. Both can produce indexable HTML and integrate a CMS; neither supplies your editorial workflow automatically.
Verdict
Start with Astro for content pages with small interactive islands. Choose Next.js when publishing is part of a React application with substantial shared UI and authenticated features. Astro can render on demand and Next.js can export static pages, so neither label decides the whole architecture. Test editor previews, publish/update behavior, and one representative page's JavaScript before committing.
Pick Astro when
- Most pages are articles, docs, or marketing content, with a few independent interactive elements
- You want content collections and a static publishing workflow, adding request-time rendering only where needed
Skip Astro if
most routes require shared React application state and your team cannot maintain the boundary between islands and the surrounding pages.
Pick Next.js when
- The publishing site shares substantial React UI and authenticated application features with your product
- You need integrated application routes and can maintain content loading, caching, and preview access
Skip Next.js if
the site is mostly articles and a few widgets, and your team has no need for React application features or its server/cache model.