View transitions: smoother page changes on a regular website
Short answer: View transitions let the browser animate from one state of a page to the next, or from one page to another, without a heavy JavaScript framework. On an ordinary multi-page website, a few lines of CSS can add a soft fade or make a product photo glide into place on the next page. As of November 2026 support is good in Chromium browsers and Safari but not universal, so treat it as a progressive enhancement: nice where it works, invisible where it doesn't.
For years, smooth page-to-page animation was something only single-page apps could do, and it usually came with a large JavaScript bundle. The View Transition API moves that job into the browser. That matters for small business sites built on WordPress, a static generator or a hosted CMS, because the effect is now available without rebuilding the site as an app.
What a view transition actually does
When a transition runs, the browser takes a snapshot of the old view, updates the page, takes a snapshot of the new view, and animates between the two. MDN's View Transition API overview lists the CSS hooks for customising it, and its usage guide explains that the default animation is a cross-fade.
You can also give individual elements a view-transition-name. The browser then animates that element separately, for example moving a thumbnail from a product grid into the large image position on the product page, while the rest of the page fades.
Same-document and cross-document: two flavours
Same-document transitions
These are for changes within one page: filtering a list, opening a detail panel, switching tabs. Your JavaScript calls document.startViewTransition() and passes it the function that updates the page. MDN lists this as the method for same-document (SPA-style) transitions.
Cross-document transitions
These cover normal navigation from one URL to another, which is what most business websites do all day. Chrome's cross-document guide explains that there is no function to call; the trigger is a same-origin navigation, typically a link click. Two conditions apply:
- Both pages must be on the same origin (same scheme, hostname and port). Going from your main site to a separate shop subdomain won't transition.
- Both pages must opt in with the CSS at-rule
@view-transition { navigation: auto; }.
The same guide notes that navigations such as typing in the address bar, using a bookmark or reloading are excluded, and that if a navigation takes too long (more than four seconds in Chrome's case) the transition is skipped.
Browser support as of November 2026
Support data from MDN's browser compatibility dataset, read in November 2026:
| Feature | Chrome / Edge | Safari | Firefox |
|---|---|---|---|
Same-document (startViewTransition) |
from 111 | from 18 | from 144 |
Cross-document (@view-transition) |
from 126 | from 18.2 | not supported |
Browsers that don't support the feature simply load the next page normally. No error, no broken layout. That's what makes it safe to try. Check the current compatibility tables before you rely on any detail, because this area is still moving.
How to set it up on a multi-page site
- Opt in on every page. Add the
@view-transitionrule to your main stylesheet so all templates share it. - Start with the default cross-fade. Look at it on a slow phone before adding anything fancier.
- Name one or two shared elements. A logo, a header, or the hero image of a listing. Each
view-transition-namemust be unique on a page, so be careful with grids where every card uses the same template. - Respect reduced motion. Some visitors set their device to reduce motion. Wrap custom animations in a
prefers-reduced-motionmedia query and keep them minimal or off for those users. - Control what renders first. MDN's guide to using the API describes
<link rel="expect" blocking="render">to make sure key content is parsed before the transition runs, so the animation doesn't show a half-built page. Use it sparingly; render blocking delays the first paint. - Test real navigation paths. Home to service page, listing to detail, blog index to article, plus the back button.
Where it can go wrong
- Slow pages make it worse, not better. A transition can't hide a slow server. Fix page speed first; Chrome skips transitions on slow navigations anyway.
- Layout jumps. If the old and new pages have very different header heights, a shared element can swoop in an odd direction. Keep shared elements consistent between templates.
- Script timing. Chrome's guide explains that the
pagerevealevent listener must be registered in a classic, parser-blocking script in the head, or markedblocking=renderif it's async. Theme developers who add custom logic need to know this. - Third-party widgets. Chat bubbles, cookie banners and embedded booking tools can flash during the snapshot. Test with them switched on.
- CMS and theme implications. In WordPress or a hosted builder, the CSS rule usually goes in the theme's stylesheet or a custom CSS field. Page builders that add their own transition scripts may conflict; remove one or the other.
Should we use it? A quick decision box
Yes, try it if:
- Your site is a classic multi-page site on one domain.
- Pages already load quickly on mobile.
- There's an obvious "continuity" moment, such as gallery to detail, menu to dish or listing to property.
Hold off if:
- Your pages are slow, or your theme already uses a JavaScript page-transition library.
- Key journeys cross domains (main site to a separate booking or shop domain).
- You don't have time to test on Safari and on a low-end Android phone.
Skip it entirely if it would replace work that matters more: fixing forms, speed or mobile layout.
FAQ
Do view transitions affect SEO?
They don't change your HTML or URLs, so search engines see the same pages. The indirect risk is performance: render blocking used carelessly can delay the first paint.
Will Firefox users see a broken site?
No. Per MDN's compatibility data as of November 2026, Firefox didn't support cross-document transitions; it simply navigates normally.
Can I use view transitions on Shopify or WordPress?
Usually yes for cross-document transitions, because they only need CSS in the theme. Test with your apps and plugins enabled.
Is it worth it for a small business site?
A subtle fade is cheap to add and harmless where unsupported. Elaborate animations are rarely worth the testing time.
Curious whether your site's templates are a good fit for smoother page changes? Send us the URL and we'll take a look.
Sources
- https://developer.mozilla.org/en-US/docs/Web/API/View_Transition_API
- https://developer.mozilla.org/en-US/docs/Web/API/View_Transition_API/Using
- https://developer.chrome.com/docs/web-platform/view-transitions/cross-document
- https://raw.githubusercontent.com/mdn/browser-compat-data/main/css/at-rules/view-transition.json
- https://raw.githubusercontent.com/mdn/browser-compat-data/main/api/Document.json