Loading
Loading
Loading
mobile footer

Build the Interaction Layer Your Website is Missing.

Browse All EffectsBrowse All EffectsBrowse All EffectsUpgrade to ProUpgrade to ProUpgrade to Pro

70+ effects free, forever. No credit card.

© 2026 Hyperiux. All Rights Reserved.

AI Component CatalogueHey AI, Learn About Us
Platform

Vault

  • Documentation
  • Pricing
  • Blog
  • Community
  • NPM
  • MCP

Categories

  • All Effects
  • WebGL
  • Text
  • Backgrounds
  • Buttons
  • Carousels
  • Scroll
  • Components
  • Navigation
  • Cursor
  • Transitions
  • Loaders

Documents

  • Introduction
  • Installation
  • CLI
  • Dependencies
  • License

Legal

  • License Agreement
  • Terms of Service
  • Privacy Policy
  • Refund Policy
Socials
  • Twitter / X
  • LinkedIn
  • GitHub
  • Instagram
Contact Us
  • hello@hyperiux.com
New effects, in your inbox

Every new drop, plus the occasional behind-the-scenes build. No spam. Unsubscribe anytime.

All Effects
Featured ComponentsText AnimationsAnimated BackgroundsAnimated ButtonsCarousel EffectsScroll EffectsCreative ComponentsNavigationsCursor EffectsTransitionsLoadersWebGL & 3D Effects
Templates
IntroductionInstallationCLIDependenciesLicense
PricingBlogGithubNPMMCP Doc
Loading
Home/effects/Depth Shift Transition

Depth Shift Transition

A layered route transition that shifts pages with offset, rotation and scale, giving portfolios and brand sites a spatial handoff without a full 3D scene.

GSAPnext-transition-router
DemoDemoDemo

Tune the Real Props

Bg Color

Background color behind the transitioning pages.

Overview

Depth Shift Transition moves the route change through a layered shift in offset, rotation and scale instead of a flat cut.

It gives navigation a sense of space: the current page pulls back, moves aside and makes room while the next view arrives with depth. Use it when a site wants route changes to feel dimensional but does not need a full WebGL scene.

Use Depth Shift Transition on portfolios, agency sites, editorial journeys, brand microsites, and launch pages where navigation can carry a controlled visual moment. The page job is continuity: the visitor should feel the change of route, understand the destination, and keep moving without waiting for the animation to finish performing.

The production risk is disorientation. Perspective motion can feel premium when it is short and clear, but it becomes frustrating when it hides the destination, breaks scroll restoration, or leaves keyboard focus behind on the previous route.


Usage Code

layout
1import DepthShiftTransition from "@/components/effects/depth-shift-transition";2import React from "react";3 4export default function layout({ children }: { children: React.ReactNode }) {5  return (6    <DepthShiftTransition>7      {children}8    </DepthShiftTransition>9  );10}

Example Production Use Case

A creative portfolio can use Depth Shift Transition between project pages so each case study feels connected to the next. The old page recedes, the new page arrives, and the visitor lands in the destination content without losing orientation. The outcome is spatial continuity: navigation feels designed without becoming a loading screen.


Best Used For

  • Portfolio and agency websites where route changes should feel spatial and crafted.
  • Campaign pages where the transition can reinforce a premium visual system.
  • Editorial journeys where depth helps one page hand off to the next.

Not For

Not for dashboards, docs, checkout, search, pricing comparison flows, or routes where navigation speed is the feature.

Not for pages where perspective movement would make users lose their place.


Performance Budget

Keep the transition short, animate transform and opacity, avoid layout reads during route change, and clean up listeners or timelines after navigation completes. Depth should come from composited layers, not from expensive layout work.


Accessibility and Mobile

Move focus to the destination main region or heading after navigation. On mobile, reduce perspective distance and avoid heavy motion that makes the route feel unstable. Reduced-motion users should get instant navigation or a brief fade.


Common Mistakes

  • Using depth motion as fake loading delay.
  • Letting the previous page remain visually dominant after the destination is ready.
  • Forgetting focus restoration after the route changes.
  • Making the perspective shift so strong that the destination feels hard to track.

Changelog

Initial release

API Reference

PropTypeDefaultDescription
bgColorstring#0b0b0cBackground color behind the transitioning pages.
durationnumber0.65Duration of the exit phase. Enter timing scales with this value.
exitOffsetXnumber20Horizontal offset applied to the outgoing page during desktop transitions.
exitOffsetYnumber30Vertical offset applied to the outgoing page during desktop transitions.
exitRotatenumber3Rotation applied to the outgoing page as it recedes.

Questions, Answered.

When should I use Depth Shift Transition?

Use it when a brand, portfolio, or campaign site needs route changes to feel dimensional without using a heavy 3D scene.

Where should Depth Shift Transition mount in the App Router?

Mount it in your root layout around {children}, as in the usage code. Depth Shift Transition renders TransitionRouter from next-transition-router itself, so it stays mounted across navigations and no separate provider or template is needed.

How long should Depth Shift Transition last?

By default the old page shifts away over 0.65s while the new one arrives after a 0.35s delay over 0.4s, so the swap completes in about 0.75s. The duration prop (default 0.65) scales all three values.

How should focus work after Depth Shift Transition?

Focus should move to the destination main region or heading once navigation completes. Keyboard users should not remain anchored to the old route.

What should reduced motion do for Depth Shift Transition?

With reduced motion enabled, the component skips the depth shift and runs a 0.2s opacity fade instead.

Can Hyperiux adapt Depth Shift Transition for a real brand system?

Yes. A custom version should define depth distance, timing, layer behavior, App Router integration, focus restoration, mobile fallback, reduced-motion handling, source handoff, and implementation notes.

Request a Custom Animation

Need a custom effect? Tell us what to create.

Related Effects

Explore All EffectsExplore All EffectsExplore All Effects
Block Transition
GSAPnext-transition-router

Block Transition

Transitions

Chess Grid Transition
GSAPnext-transition-router

Chess Grid Transition

Transitions

Page Flip Transition
Pro
GSAPnext-transition-router

Page Flip Transition

Transitions

SVG Brush Transition
Pro
GSAPnext-transition-router

SVG Brush Transition

Transitions