One of the most overlooked advances of the web platform in recent years is here: the View Transitions API has moved from experimental to stable support across all major browsers. For a classic multi-page site it means a team can ship native-app-grade animated transitions between pages – without React, Vue, or any SPA framework.
What the View Transitions API Can Do
The API covers two scenarios. Same-document transitions animate changes within a single page – typically when filtering, sorting, or opening a modal. Cross-document view transitions are the real revolution: the browser snapshots the outgoing page, loads the new one, and animates between them. From the user’s perspective it looks like a seamless application, even though the underlying site is plain multi-page HTML.
Chrome added cross-document View Transitions in version 126, Safari followed in 18.2, and from 2026 onwards support is in every major browser. For a marketing site, a documentation portal, a blog, or an e-commerce listing-to-detail flow it’s one of the highest-leverage features the web platform offers in 2026.
How to Ship It in Practice
For the simplest cross-document transitions you need two things. Add this meta tag to the <head> of both pages:
<meta name="view-transition" content="same-origin">And add animation rules in CSS:
::view-transition-old(root) {
animation: fade-out 0.3s ease;
}
::view-transition-new(root) {
animation: fade-in 0.3s ease;
}Done – navigation between pages is now animated. No library, no build step, no JavaScript. For more advanced flows, set view-transition-name on elements you want to “fly” from one page to another (typically a product image transitioning into a detail view).
What’s New in 2026
Chrome 147 introduced element-scoped transitions, which let you animate just a chosen part of the page instead of the full viewport. That’s a big deal for performance – you don’t have to animate the header and footer on every navigation. Two-phase transitions are also in testing, where the old page leaves first and only then does the new page enter with its own animation, opening doors to more sophisticated storytelling.
Performance Impact and SEO Bonus
Transitions run fully natively, off the main JavaScript thread, so they don’t pressure INP. Developers also get a Core Web Vitals win simply by replacing a client-side router with native MPA navigation plus View Transitions – shorter TTI, better INP, and often better LCP. And because these are plain HTML pages, they’re indexable like always, unlike some SPA solutions.
Conclusion
The View Transitions API is the answer to the question of why you’d build a complex SPA at all. In 2026 you get smooth transitions, better performance, and equally strong SEO – with significantly less code. Planning a redesign or wondering whether you’re fighting an unnecessary battle with an SPA framework? Get in touch – we’ll discuss whether the modern web platform could save you months of development.
