Effect #072 in our rendered series
Directional wipe transition
One scene slides over another from a chosen side with a small parallax, then a second push returns.
Rendered by us at 1920x1080 over shots from Tears of Steel (Blender Foundation, CC-BY 3.0). Expand plays the full 1080p file.
Edit in Premiere, Resolve or After Effects? Jump to editor templates. Making many versions of the same video? Use the code route.
Make this effect with
Built and tested by us
Other ways, not tested by us
Use it in a real edit
The same directional wipe from the skyline into the warm room. Nothing in the composition changed except the footage file.
The composition plays your clip as a muted <video> layer under the graphics (the file plate.mp4 in the code below), so you swap the footage by replacing that file and rendering again. To use the graphics in an editor instead, switch the background off and render a transparent MOV (an H.264 MP4 cannot carry transparency):
npx hyperframes render . -o overlay.mov --format mov --fps 24 --variables '{"plate":false}'The routes in full
With Claude Code: the prompt we used
Rendered and tested by us in HyperFrames 0.8.10 on Nov 7, 2026.
Write a HyperFrames directional wipe transition where one scene slides over another from a chosen side. Make the direction and the duration variables.
What changed since this prompt: the demo on this page is our second version, 5 seconds long, rebuilt on 2 shots from Tears of Steel with the same animation idea. The full composition below is the one we rendered; its build log lists every change.
Built by a Claude Code subagent (Sonnet) from the HyperFrames registry block directional-wipe, HyperFrames 0.8.10. Claude Code then checked the composition with hyperframes lint and hyperframes check before we rendered it.
What we had to correct (10 notes from the build log):
- 6 Nov 2026, lint 1: 0 errors, 0 warnings.
- Adapted from the registry block directional-wipe (clip-path reveal of scene B over scene A with a small parallax under it). Structure and the clock-driven clip/parallax technique come from our own chromatic-wipe-transition demo.
- Variables: direction (left, right, up, down), wipe duration in seconds (0.3 to 1.6, clamped), plate.
- Changes made while writing, before lint: scene B label colours were darkened (white on the first orange and the first blue measured under 4.5:1, now above 5:1); scene text never fades, it only scales or slides, so text stays at full contrast whenever visible; the channel-split and glow of the chromatic demo were left out (a white glow over white text would lower contrast), replaced by an 8 px white rim that rides the wipe edge.
- Second push uses the same travel direction as the first, so the loop restarts from the opening scene A with no jump. Second wipe starts at 3.2 s, so the longest duration (1.6 s) still finishes at 4.8 s.
- Text sits under an opaque shape only where the wipe deliberately covers scene A (or scene B on the return push), for the length of the wipe.
- Decided against: an exit fade (not needed, the return push already restores the opening state), diagonal wipes (not asked for).
- hyperframes check: "Check failed", 4 errors, by design for a push where scene B covers scene A. Quoted: "t=1.5-3.63s (21 samples) content_overlap #alab inside #blab \"Scene A\" - Two text blocks overlap and may render unreadable" and "t=1.94-3.61s (4 samples) text_occluded #alab inside div.sbg.bbg \"Scene A\" - Text is hidden beneath an opaque element" (and the same for #asub), plus one warning "container_overflow #A inside #stage overflowed left 70px" from the parallax slide. Scene A is under scene B only while the push covers it. Render: flash check passed. Looked at 1920 px frames at 1.7 s (push just started), 2.3 s (B settled) and 3.6 s (return push half way): the two scenes' titles overlap at the moving edge for a few frames ("SScene A"), which is the parallax and is expected.
- v2 (7 Nov 2026): real footage from Tears of Steel, plates tr_engines, tr_thom. One wipe at 2.0 s (wipeDuration variable default 0.8 s).
- v2 (7 Nov 2026, lead): poster moved to 3.6 s: the earlier poster caught the transition mid-blur; a poster must show a clean, legible shot (consultant round 2).
With HyperFrames code
Rendered and tested by us in HyperFrames 0.8.10 on Nov 7, 2026.
npx hyperframes add directional-wipe
npx hyperframes render . -o out.mp4 --fps 24Settings you can change without rebuilding (pass them with --variables):
| Setting | Name | Type | Default |
|---|---|---|---|
| Wipe direction | direction | enum | left |
| Wipe duration (seconds) | wipeDuration | number | 0.8 |
| Show background | plate | boolean | true |
Our full composition (index.html, 5 KB)
<!doctype html>
<html lang="en" data-composition-variables='[{"id":"direction","type":"enum","label":"Wipe direction","default":"left","options":[{"value":"left","label":"Left"},{"value":"right","label":"Right"},{"value":"up","label":"Up"},{"value":"down","label":"Down"}]},{"id":"wipeDuration","type":"number","label":"Wipe duration (seconds)","default":0.8,"min":0.3,"max":1.6,"step":0.1},{"id":"plate","type":"boolean","label":"Show background","default":true}]'>
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=1920, height=1080" />
<link href="https://fonts.googleapis.com/css2?family=Montserrat:wght@800&display=block" rel="stylesheet" />
<script src="gsap.min.js"></script>
<style>
*, *::before, *::after { box-sizing: border-box; margin: 0; padding: 0; }
html, body { width: 1920px; height: 1080px; overflow: hidden; background: transparent; }
#root { position: relative; width: 100%; height: 100%; overflow: hidden; background: transparent; }
#stage { position: absolute; inset: 0; overflow: hidden; }
.scene { position: absolute; inset: 0; font-family: "Montserrat", sans-serif; font-weight: 800; }
.vid { position: absolute; left:-140px; top:-140px; width:2200px; height:1360px; object-fit: cover; }
#rim { position: absolute; left: 0; top: 0; background: #fff; opacity: 0; z-index: 5; }
</style>
</head>
<body>
<div id="root" data-composition-id="main" data-start="0" data-duration="5" data-fps="24" data-width="1920" data-height="1080">
<div id="stage">
<div class="scene" id="A"><video class="plate vid" src="plate_a.mp4" muted playsinline data-start="0" data-duration="3.0"></video></div>
<div class="scene" id="B"><video class="plate vid" src="plate_b.mp4" muted playsinline data-start="2.0" data-duration="3.0"></video></div>
<div id="rim"></div>
</div>
</div>
<script>
window.__timelines = window.__timelines || {};
(function () {
const v = window.__hyperframes.getVariables();
const tl = gsap.timeline({ paused: true });
if (!v.plate) document.querySelectorAll(".plate").forEach((e) => (e.style.display = "none"));
const W = 1920, H = 1080, OS = 140, PAR = 70;
const DIRS = { left: [-1, 0], right: [1, 0], up: [0, -1], down: [0, 1] };
const dirName = DIRS[v.direction] ? v.direction : "left";
const dx = DIRS[dirName][0], dy = DIRS[dirName][1];
const horiz = dx !== 0;
let D = Number(v.wipeDuration);
if (!isFinite(D)) D = 0.8;
D = Math.max(0.3, Math.min(1.6, D));
const T1 = 2.0, T2 = 99;
const ease = gsap.parseEase("power4.inOut");
const A = document.getElementById("A"), B = document.getElementById("B"), rim = document.getElementById("rim");
const RIM = 8;
rim.style.width = (horiz ? RIM : W) + "px"; rim.style.height = (horiz ? H : RIM) + "px";
// pixel insets for the clip; every side that is not the wipe edge reaches OS px beyond the frame
function clipFor(q, second) {
const dim = horiz ? W : H;
const val = second ? (q <= 0 ? -OS : q * dim) : (q >= 1 ? -OS : (1 - q) * dim);
let t = -OS, r = -OS, b = -OS, l = -OS;
if (!second) {
if (dirName === "right") r = val; else if (dirName === "up") t = val; else if (dirName === "down") b = val; else l = val;
} else {
if (dirName === "right") l = val; else if (dirName === "up") b = val; else if (dirName === "down") t = val; else r = val;
}
return "inset(" + t.toFixed(1) + "px " + r.toFixed(1) + "px " + b.toFixed(1) + "px " + l.toFixed(1) + "px)";
}
function edgeBase(q) {
if (dirName === "right") return W * q;
if (dirName === "up") return H * (1 - q);
if (dirName === "down") return H * q;
return W * (1 - q);
}
const st = { t: 0 };
function paint() {
const t = st.t;
const u1 = Math.max(0, Math.min(1, (t - T1) / D)), u2 = Math.max(0, Math.min(1, (t - T2) / D));
const q1 = ease(u1), q2 = ease(u2);
const second = t >= T2;
const q = second ? q2 : q1;
B.style.clipPath = t < T1 ? clipFor(0, false) : (second ? clipFor(q2, true) : clipFor(q1, false));
// parallax: the incoming panel carries a short offset, the panel under it is pushed a little the other way
let bOff, aOff;
if (!second) { bOff = (1 - q1) * -PAR; aOff = q1 * PAR; } else { bOff = q2 * PAR; aOff = (1 - q2) * -PAR; }
B.style.transform = "translate(" + (dx * bOff).toFixed(1) + "px," + (dy * bOff).toFixed(1) + "px)";
A.style.transform = "translate(" + (dx * aOff).toFixed(1) + "px," + (dy * aOff).toFixed(1) + "px)";
const moving = (t >= T1 && t < T1 + D) || (t >= T2 && t < T2 + D);
const u = second ? u2 : u1;
rim.style.opacity = moving ? (Math.sin(Math.PI * u)).toFixed(3) : "0";
const e = edgeBase(moving ? q : 0) + (horiz ? dx : dy) * bOff;
rim.style.transform = horiz ? "translate(" + (e - RIM / 2).toFixed(1) + "px,0px)" : "translate(0px," + (e - RIM / 2).toFixed(1) + "px)";
}
// one scalar clock drives the clip, the parallax and the rim
tl.to(st, { t: 5, duration: 5, ease: "none", onUpdate: paint }, 0);
tl.eventCallback("onUpdate", paint);
paint();
tl.to({}, { duration: 5 }, 0);
window.__timelines["main"] = tl;
})();
</script>
</body>
</html>
With Remotion
We have not built this effect in Remotion. If you use it, read its licence first: Individuals (personal or commercial use), organisations or teams with a total headcount of 3 or less, non-profits, and anyone evaluating Remotion before commercial use. A company does not qualify merely because it is unprofitable. Everyone not eligible for the Free License needs a Company License. Remotion licence FAQ, checked Nov 4, 2026.
In your editor: Premiere, Resolve, After Effects, CapCut
We have not reviewed an editor template for this effect yet.
Variations
The same composition rendered again with different settings. Nothing was rebuilt.
{"direction":"left","wipeDuration":1.4}{"direction":"up","wipeDuration":0.4}{"direction":"down","wipeDuration":1.6}Spec and test details
- Engine
- HyperFrames 0.8.10, GSAP 3.14.2 (local copy)
- Length and frame rate
- 5 seconds at 24 fps, rendered at 1920x1080
- Video files on this page
- H.264: 1920x1080 for Expand (5337.9 KB), 1280x720 in the page (1834.2 KB), 640x360 in galleries (358.6 KB), no audio
- Picture check
- The 1080p file scores VMAF 97.3 against our render master and keeps 92% of its edge detail (measured by us with FFmpeg libvmaf and OpenCV)
- Footage
- huge glowing rocket engines firing, warm and pink (Tears of Steel, 0:09); young Thom close-up, canal behind, soft daylight (Tears of Steel, 5:16)
- Tested in editors
- None yet
- Flash check
- Passed: at most 1 general and 0 red flashes in any second. automated approximation of WCAG 2.3.1 on a 96x54 grid, whole loop including the restart; not a certification.
- Licence
- Composition adapted by us from the HyperFrames registry (Apache-2.0); text fonts from Google Fonts under the SIL Open Font License.
- Last tested
- Nov 7, 2026
- Machine
- Laptop: AMD Ryzen 7 7735U (8 cores, 16 threads), 31 GB RAM, Windows 11 Home; CPU rendering
Technical details: render times and file sizes
- Render of the 5-second master: 61.4 s (2 render workers, on the laptop above).
- full.mp4: 5337.9 KB
- hero.mp4: 1834.2 KB
- hero.webp: 29.9 KB
- tile.mp4: 358.6 KB
- tile.webp: 8.7 KB
- real-edit.mp4: 1234.2 KB
- real-edit-full.mp4: 4454.2 KB
- real-edit.webp: 35.2 KB
- Variation "subtle": rendered in 63.8 s, 366.5 KB
- Variation "bold": rendered in 66.7 s, 346 KB
- Variation "down-long": rendered in 74.1 s, 372.4 KB
Credits
- Built from the HyperFrames registry component directional-wipe by HeyGen (Apache-2.0), adapted by us.
- Fonts from Google Fonts, under the SIL Open Font License.
- Footage: Tears of Steel, (c) Blender Foundation, mango.blender.org, licensed CC-BY 3.0. We cropped the shots to 16:9 and laid our graphics over them.
- Editor templates and other routes on this page belong to their creators, who are credited on each card.
Related effects and jobs
Page checked on Nov 4, 2026.



