Screen Fader
Fading the screen to black to hide scene changes and frame transitions cleanly.
Examples
Captured from this page's own interactive demo below.
Overview
A screen fader is a full-screen overlay (almost always black) that fades in, covers whatever needs to change — a level load, a respawn, a camera teleport — and fades back out. It's the oldest transition in the book, borrowed directly from film editing's 'dip to black'.
It works because it gives the eye a clean break. Hard cuts, teleporting objects, and pop-in read as glitches when the player sees them happen; behind a moment of black, the same changes read as intentional. Film has trained everyone for a century that a fade means 'time or place just changed'.
The speed carries tone: a quick dip (200–400ms) is neutral scene management, while a slow fade reads as somber or final — death, sleep, the end of a chapter.
Interactive Demo
Use Cases
Best Practices
Do
- ✓Ease the fade (ease-in-out) — a linear opacity ramp looks mechanical rather than cinematic.
- ✓Do the actual work (scene load, teleport, state reset) while the screen is fully black — that cover is the whole point.
- ✓Match the speed to the tone: fast dips for routine transitions, slow fades for dramatic beats.
Don't
- ✕Don't lock input for longer than the transition actually needs — an unresponsive fade reads as a hang.
- ✕Don't fade to white for routine transitions — white reads as a flash, explosion, or death; black reads as neutral.
- ✕Don't let multiple systems drive the same fader — one owner, or you get flicker and screens stuck on black.
Common Mistakes
- ⚠Starting the scene load only after the fade-out finishes, doubling the wait instead of loading behind the black.
- ⚠A fader that can get stuck at full black when a transition is interrupted — always have a failsafe fade-in.
- ⚠Forgetting the overlay blocks (or fails to block) clicks and raycasts — decide deliberately and set it explicitly.
Implementation
Paste this into your AI assistant (Cursor, Copilot, Claude) to add the effect to your project.
Add the "Screen Fader" game-feel effect to my project: Fading the screen to black to hide scene changes and frame transitions cleanly.
How it works: A screen fader is a full-screen overlay (almost always black) that fades in, covers whatever needs to change — a level load, a respawn, a camera teleport — and fades back out. It's the oldest transition in the book, borrowed directly from film editing's 'dip to black'.
Guidelines:
- Ease the fade (ease-in-out) — a linear opacity ramp looks mechanical rather than cinematic.
- Do the actual work (scene load, teleport, state reset) while the screen is fully black — that cover is the whole point.
- Match the speed to the tone: fast dips for routine transitions, slow fades for dramatic beats.
Avoid:
- Don't lock input for longer than the transition actually needs — an unresponsive fade reads as a hang.
- Don't fade to white for routine transitions — white reads as a flash, explosion, or death; black reads as neutral.
- Don't let multiple systems drive the same fader — one owner, or you get flicker and screens stuck on black.
Implement the effect in whatever engine/stack the project already uses and follow its existing code style. Wire it up where it makes sense.References
- Unity Manual — CanvasGroup
- Film editing's 'dip to black' — the convention this borrows from
Comments
…