Exits
Fade Out Down Animation
Sinks downward while fading away.
Card title
Supporting copy goes here.
Opens with this animation loaded. Nothing is uploaded — the scene travels in the link.
.fade-out-down {
transform: translate3d(130px, 90px, 0);
box-shadow: 0px 10px 30px 0px #00000059;
width: 220px;
height: 140px;
background: #1c1e2a;
border-radius: 18px;
color: #e7e9ee;
font-size: 14px;
animation: fade-out-down-anim 700ms linear 0ms infinite both;
will-change: transform, opacity;
}
@keyframes fade-out-down-anim {
0% {
transform: translate3d(130px, 90px, 0);
opacity: 1;
animation-timing-function: ease-in;
}
100% {
transform: translate3d(130px, 138px, 0);
opacity: 0;
}
}
@media (prefers-reduced-motion: reduce) {
.fade-out-down {
animation: none;
transition: none;
}
}Why it is built this way
Downward exits suit dismissal — the thing is falling away. Upward exits suit completion, as though the item has been consumed. The direction is doing real work here, not decoration.
What it animates
2 properties across 2 CSS declarations. The bar shows when each one is moving.
opacitytransformWhat it costs to run
Opacity and y are handled by the compositor: no layout, no repaint, and the work can run off the main thread. This is the cheap end of CSS animation, which is why it stays smooth on a slow phone where other properties will not.
It runs for 0.70s across 4 keyframe stops, with every property moving over the same window.
One curve throughout: Ease In on a card. Keeping a single easing across every property is what makes a multi-property animation read as one movement rather than several things happening at once.
Accessibility
Nothing here hides content — opacity and y move over 0.70s and the element is visible throughout. The exported prefers-reduced-motion guard still silences it, which matters most for the looping ones: motion that never stops is the kind that makes people feel unwell.