Back to all features
Open for signals View transitions Interop 2026

Cross-document view transitions

The @view-transition CSS rule sets whether a document opts-in to transitions between documents in a multi-page application. Both the old and new document must opt-in for a transition to be triggered.

Modern Web Guidance

How Modern Web Guidance uses this feature

Coordinates smooth, animated page transitions across multi-page document navigations using @view-transition { navigation: auto; }.

Recommended fallback strategy

Unsupported browsers ignore the @view-transition at-rule and execute standard page loads without errors. All browsers supporting cross-document transitions also support render blocking, ensuring seamless progressive enhancement.

Related use cases

Summary synthesized from Modern Web Guidance (opens in new tab). Read the related use cases for full, human-authored guidance.

Community use cases (1)

Psychpsyo

What I want to do with this feature

Fancier transitions on my website.

What I'm having to do in the meantime

Waiting for Firefox to support these so that my transitions show up there as well.

Signing in with GitHub allows you to cast one-click upvotes and submit structured use cases directly to the web-platform-dx/developer-signals repository.

Our GitHub App only requests access to issue discussions. It never requests or has access to your personal repositories or code.
Sign in with GitHub
Strict feedback template: Please be as concrete as possible. Specific examples from your production apps or projects provide the highest-value signal to standards editors and browser engineers.
Add your specific real-world use cases, even if they seem obvious to you.
0 / 5000 (min 10)
Are you having to use another feature instead, a polyfill, or is it blocking you completely? Why are the alternatives worse?
0 / 5000 (min 10)
Markdown formatting is supported.