Page transition

Also called route transition or navigation transition

An animation that plays when you move from one page or screen to another, such as the old page fading out as the new one fades in.

What is Page transition?

Without a page transition, clicking a link swaps the whole screen at once. A page transition animates the handoff: the outgoing page fades or slides away while the incoming page arrives, usually within 200 to 400ms. Mobile apps have always done this, and websites increasingly do too.

Pick one style and use it everywhere. A quick crossfade suits most sites. A slide works when pages have a clear order, such as tabs or steps, and should follow the direction of travel. Keep shared parts like the header and navigation still, so only the content area moves.

A page transition should never slow people down. Start it right away instead of waiting for data, keep it short, and respect prefers-reduced-motion. In React apps you can animate the route content with a library like Motion, or use the browser’s View Transitions API, which works within a single-page app and, in supporting browsers, across regular page loads.

Often confused with

View Transitions API
A page transition is the effect. The View Transitions API is one browser feature for building it, by snapshotting the old page and animating to the new one.
All terms

Crossfade

A transition where the old content fades out while the new content fades in at the same spot, so the two briefly overlap.

Direction-aware transition

A transition that slides new content in from the side you are heading toward, so going forward and going back move in opposite directions.

Shared element transition

A transition where an element from one view, like a thumbnail, travels and grows into its place in the next view, linking the two screens.

Perceived performance

How fast an app feels to people, which skeleton screens, instant feedback, and progressive loading can improve even when the real wait stays the same.