# Shared Element Transition

[Live demo](https://matinmonshizadeh.github.io/animation-handbook/animations/03-page-transitions/shared-element-transition/)

## What it is
A shared element transition keeps one piece of content in view while the page changes around it: a thumbnail in a grid grows and moves into the large picture at the top of its detail page, instead of the two pages simply swapping. It feels as if you travel with the content rather than jump to a new screen. The demo measures where the picture starts and where it ends, then moves a copy of it from one to the other.

## When to use it
- Thumbnail-to-detail navigation in galleries, product grids, and media libraries
- Card-to-modal expansions where the card becomes the modal header
- Any place where the same object exists in both the "before" and "after" view and you want to preserve identity
- Mobile app-style navigation where spatial continuity aids orientation

## How it works
FLIP stands for First, Last, Invert, Play. Record the thumbnail's rectangle (First), reveal the destination and read the hero's rectangle (Last), place a fixed copy on the header's rectangle and draw it back onto the thumbnail with a transform (Invert), then transition that transform to none (Play):

```js
function openDetail(i, dur, ease){                            // dur, ease: the chosen speed and feel
  const p = PROJECTS[i];                                      // the project that was clicked
  const thumbRect = thumbEls[i].getBoundingClientRect();      // FIRST
  detail.classList.add('active');
  const heroRect = detailHero.getBoundingClientRect();        // LAST
  // INVERT: the copy sits on the header's rectangle; a transform draws it back onto the thumbnail
  const sx = thumbRect.width / heroRect.width, sy = thumbRect.height / heroRect.height;
  flipEl.style.cssText =
    `background:${p.bg};top:${heroRect.top}px;left:${heroRect.left}px;`+
    `width:${heroRect.width}px;height:${heroRect.height}px;transform-origin:0 0;`+
    `transform:translate(${thumbRect.left-heroRect.left}px,${thumbRect.top-heroRect.top}px) scale(${sx},${sy});`+
    `border-radius:${10/sx}px/${10/sy}px;transition:none;display:block`;
  void flipEl.offsetWidth;                                     // commit the inverted start
  flipEl.style.transition =                                    // PLAY
    `transform ${dur}ms ${ease},border-radius ${dur}ms ${ease}`;
  flipEl.style.transform = 'none';
  flipEl.style.borderRadius = '0';
}
```

The real grid fades out while the copy travels, and the detail body fades in slightly later (`dur*0.6` delay) so the hero has arrived before its text appears. Reading `offsetWidth` after placing the copy makes the browser apply the inverted start before the transition is switched on — without it the copy would jump straight to the end. The corners are set to `10/sx` by `10/sy` so they still look 10px round while the copy is shrunk.

## Key parameters
| Parameter | Default | Effect |
|-----------|---------|--------|
| Speed | Normal | How long the picture takes to travel and grow: slow is 800ms, normal 500ms and fast 300ms; 300 to 600ms feels responsive without dragging |
| Feel | Smooth | Smooth slows to a stop; Springy grows a little past the header's size, then settles |

## Production notes
- **Read then write** — batch all `getBoundingClientRect()` reads before you touch styles. Interleaving reads and writes causes layout thrashing that stutters the animation.
- **The clone is `position:fixed`**, so it moves in viewport coordinates and ignores the scroll and layout of the pages underneath it. It moves with `transform` alone (a shift and a scale), so the browser lays nothing out while it travels; only its corners are repainted. A scaled copy stretches what is inside it, which suits a picture or a color but not text.
- **Fixed positioning uses viewport coordinates**, which is why the demo reads `getBoundingClientRect()` directly. If your clone lives inside a transformed or scrolled ancestor, offsets must be adjusted.
- **Reduced motion** skips the clone entirely and snaps the detail view in.
- **Library equivalents**: the View Transitions API does this natively by giving both elements the same `view-transition-name`. Framer Motion's `layoutId` and shared `<motion.*>` elements automate FLIP; GSAP's Flip plugin offers the same measure-invert-play primitive.

## See also
- [View Transitions API](../view-transitions-api/) — the browser can do this itself
- [FLIP Technique](../flip-technique/) — the measure-then-move method on its own
- [Portal / Tunnel Zoom](../portal-zoom/) — the next page opens out of a clicked circle
- [Morph Transition](../morph-transition/) — a shape changes instead of moving
