Choose by who edits it
If your team edits copy and swaps case images weekly and nobody writes code, Webflow's editor is a real advantage. If edits are rare and the site is a showpiece, that advantage shrinks.
Where Next.js wins
Custom motion that carries state between pages, such as a shape that moves from a card into a case page, is a first-class pattern with the View Transitions API and the Web Animations API. Real-time 3D with a hard weight budget is also simpler when you own the whole build.
You also control exactly what ships: our concept sites record 0.28 to 1.41 MB on first load and CLS of 0.000 to 0.001, because nothing is added that was not chosen.
Where Webflow wins
Speed to a first version, a visual editor for non-developers, and hosting you do not think about. For a brochure site with standard sections, it is a sound default.
The rule we use
If the site is the portfolio piece that wins you work, and it needs motion or 3D that a template cannot do, build it in code. If it is the place where updates happen weekly, keep the editor. You can also do both: a code-built showcase page beside a Webflow blog.