Mobile apps feel smooth partly because moving from one screen to the next is animated: a card expands into a detail view, a list slides away, a header stays in place. Traditional websites, by contrast, flash white and redraw the whole page every time you click a link.
For years, the only way to get app-like transitions on the web was to build the site as a single-page application with a heavy JavaScript framework. The View Transition API changes that. It lets browsers animate between page states, and even between separate pages, with very little code. This guide explains what it does, where it helps and what to watch out for.
The short answer
View transitions are a browser feature that animates the change from one view to another. The browser takes a snapshot of the old page, renders the new one, and animates between them, by default with a quick cross-fade.
- Same-document transitions animate changes within one page, such as filtering a list or opening a panel.
- Cross-document transitions animate navigation between separate pages of a normal multi-page website, using a few lines of CSS.
Browsers that don’t support them simply change pages as usual, so they can be added as a progressive enhancement without risk.
How view transitions work
When a transition starts, the browser:
- captures a snapshot of the current state;
- updates the page, or loads the new page;
- captures the new state;
- animates from the old snapshot to the new one using CSS animations you can customise.
You can also give individual elements a view-transition-name. When an element with the same name exists on both the old and new page, the browser animates it from one position and size to the other. That is how a product thumbnail can appear to grow into the main image on the next page.
MDN’s reference on the View Transition API explains the full set of options.
Transitions between pages with CSS only
For a multi-page site, the basic cross-document transition needs only this in the CSS of both pages:
@view-transition {
navigation: auto;
}
With that rule in place, supporting browsers cross-fade between pages on the same site. To animate a specific element, give it the same name on both pages:
.site-header {
view-transition-name: site-header;
}
The header then stays visually in place while the rest of the page changes. Chrome’s developer documentation on view transitions includes worked examples of both types.
Where view transitions help
Used with restraint, transitions make a site feel faster and easier to follow:
| Situation | How a transition helps |
|---|---|
| Moving between related pages | Keeps the header and navigation steady, so the change feels smaller |
| Opening a project or product from a list | Shows that the detail page belongs to the item clicked |
| Filtering or sorting a list | Lets visitors see items move rather than jump |
| Switching tabs or steps in a form | Makes it clear which direction the visitor is going |
| Changing language versions | Softens a full-page swap while keeping the layout in place |
The goal is orientation, not decoration. A transition should help visitors understand where they are, not slow them down to admire the effect.
Browser support and progressive enhancement
At the time of writing (October 2026), same-document transitions are supported in the major browser engines, and cross-document transitions in Chromium-based browsers and Safari, with support continuing to expand. Check current support on MDN or a compatibility table before relying on a particular feature.
Because unsupported browsers ignore the CSS and navigate normally, view transitions are a safe progressive enhancement. Nobody loses functionality; some visitors simply get a smoother experience.
Accessibility: respect reduced motion
Some people experience discomfort, dizziness or distraction from animation. Operating systems let users ask for reduced motion, and websites should honour it. Turn transitions off, or reduce them to a simple fade, for those visitors:
@media (prefers-reduced-motion: reduce) {
::view-transition-group(*),
::view-transition-old(*),
::view-transition-new(*) {
animation: none !important;
}
}
Also keep transitions short. Anything that delays a visitor reaching the content they asked for is a usability problem, however polished it looks. Our guide to micro-interactions and motion design covers the wider principles.
Performance considerations
View transitions are handled by the browser and are generally efficient, but a few points matter:
- Keep animations simple. Cross-fades and movements using opacity and transform are cheap for the browser to render.
- Don’t delay navigation. The new page still has to load. A transition can’t hide a slow server or heavy page; it can only make a fast one feel smoother.
- Name only a few elements. Each named element is captured and animated separately. A handful is fine; dozens can make transitions janky on low-end phones.
- Measure. Check that Core Web Vitals don’t worsen after adding transitions, particularly Interaction to Next Paint on pages with same-document transitions. See our guide to Core Web Vitals.
Adding transitions to an existing site
You don’t need a rebuild to try view transitions. A cautious approach:
- Add the basic cross-fade rule and test it on a staging copy.
- Check every page type, including forms, the home page and any pages with embedded videos or maps.
- Add a name to one stable element, usually the header, and confirm it stays steady between pages.
- Add the reduced-motion rule before going live.
- Watch for layout shifts or slow interactions in your performance reports during the first weeks.
If any page behaves oddly, you can exclude it by leaving the rule out of that page’s CSS.
Do you still need a single-page application?
Many sites were built as single-page applications partly to get smooth transitions. Cross-document view transitions remove much of that reason for content sites such as company websites, blogs and marketing pages. A multi-page site is usually simpler, faster to load first time, and easier for search engines to crawl.
Single-page architectures still make sense for highly interactive tools and dashboards. Our guide to websites versus web applications explains where that line usually falls.
Frequently asked questions
Do view transitions affect SEO?
Not directly. Search engines read each page’s HTML as normal, and the transitions are a visual effect in the browser. Keeping pages fast and crawlable matters far more.
Can view transitions be used on WordPress sites?
Yes. Cross-document transitions are added in CSS, so they work with most themes. Test carefully with your page builder, because some add scripts or layouts that interfere with named elements.
Are view transitions the same as page-loading animations?
No. Loading animations, such as spinners, show that something is happening. View transitions animate between two finished states. They should never replace making pages load quickly.
What to do next
Try the basic cross-fade on a staging copy of your site, check it on a mid-range phone, and test with reduced motion turned on in your device settings. If it feels smoother without slowing anything down, keep it; if not, leave it out.
When we build a site through our website design and development service, motion is used sparingly, respects reduced-motion settings and is tested against performance targets. If your current site feels clunky between pages, our website redesign service can address the causes, from slow loading to inconsistent layouts.