The recording for this lesson has not been published yet.
What we cover
Cut vs dissolve vs swipe
Transition duration and rhythm
Match action for invisible transitions
When to avoid transitions entirely
Lesson notes
1. What this lesson is for
In this lesson you choose transitions by narrative logic, so scene changes feel intentional
and, most of the time, invisible. The module principle applies here too:
every movement should communicate emphasis, sequence, or context. A
transition is movement between shots - if it does not say "time passed", "we moved
somewhere else" or "this is connected", a plain cut is usually better.
The deliverable for this module is one scene with intentional keyframes, restrained
transitions and consistent effects. This lesson covers the transitions part.
2. Cut vs dissolve vs swipe
Cut - the default. Instant, invisible when motivated, and used for the
vast majority of edits in professional work.
Dissolve (cross-fade) - one shot blends into the next. It reads as
"time passes" or "these ideas are related". Dip to black or white is a stronger version
that closes a chapter.
Swipe / slide / wipe - the new shot pushes the old one off screen. It
is loud and graphic. Useful for list items, before/after reveals or a deliberately playful
style; distracting in serious content.
Everything else (spins, glitches, zoom blurs, 3D cubes) - treat as a
special effect, not a transition. Use at most once, for a specific reason.
In CapCut, transitions live in a transitions panel; you drag one onto the join between two
clips on the same track and then set its duration in the properties panel. Category names
and whether an "apply to all" option exists vary by version.
3. Decision matrix: which transition, when
Context
Preferred transition
Duration range
Avoid
Same scene, continuous action or dialogue
Cut (match on action)
0 frames
Any visible transition
Jump cut inside a talking head
Cut + punch-in, or cut to B-roll
0 frames
Short dissolve to "soften" it (looks like a mistake)
Time passes, same location
Dissolve
0.5-1.0 s
Swipes and zooms
Change of chapter or topic
Dip to black / white, or cut to title card
0.5-1.2 s
A different flashy transition per chapter
List items, step 1 -> step 2
Consistent slide or swipe, same direction each time
0.2-0.4 s
Mixing directions and styles
Before / after comparison
Wipe or slide
0.3-0.6 s
Dissolve (both images blur together)
Fast-paced montage on music
Cuts on the beat
0 frames
Transitions that smear the beat
Serious or emotional moment
Cut or slow dissolve
0 or 1-2 s
Glitch, spin, whoosh
4. Transition duration and rhythm
A transition steals time from both clips. At 30 fps, a 1-second dissolve overlaps 30 frames
of the outgoing and incoming shot - roughly half a sentence. Keep these rules:
Fast content, short transitions. In a 60-second social cut, anything
over 0.4 s feels slow.
Land on the beat. With music, the midpoint of a dissolve or
the end of a swipe should sit on a beat, not between beats.
Handles. A transition needs extra source footage beyond the cut
point on both clips. If a clip has no spare frames, the editor may shorten the
transition or freeze frames - check the join after applying.
Same type, same duration. Pick a duration per transition type for the
whole project and stick to it.
"Apply to all" is a trap
Applying one transition to every join is the fastest way to transition overload - the
first pitfall of this module. If your version offers it, use it only when every join
genuinely has the same meaning, such as a uniform list sequence.
5. Match action for invisible transitions
The most professional transition is one nobody notices. A match cut on
action cuts in the middle of a movement: the movement begins in shot A and
finishes in shot B, and the eye follows the motion across the edit.
Cut during the movement, not before or after it.
Keep screen direction: if the subject moves left-to-right in A, it
should continue left-to-right in B.
Other invisible bridges: a whip pan at the end of A and the start of B,
something passing close to the lens, or a graphic match (a round
clock face cut to a round plate).
Combine with the J-cuts and L-cuts from module 1 - sound leading the picture hides the
edit even better.
6. When to avoid transitions entirely
Within one continuous conversation or demonstration.
When cutting to music with a clear beat - the cut is the rhythm.
To hide a bad cut. A transition draws attention to exactly the join you want to
hide; fix the cut instead (punch-in, B-roll, better cut point).
When the transition style belongs to a different brand or genre than yours.
When you already used a transition in the last few seconds.
Write down your transition style
Add a transitions section to the brand kit from module 2: which two or three transitions
the project uses, their durations and what each one means. Consistency is what makes a
transition feel designed rather than random.
TRANSITION STYLE SPEC - product_explainer_v2
DEFAULT hard cut
TIME PASSES dissolve, 0.6 s
NEW CHAPTER dip to black, 0.8 s (max 1 per chapter)
LIST STEPS slide left, 0.3 s, same direction every time
FORBIDDEN spins, glitches, 3D, whoosh-zoom, random presets
BUDGET <= 1 visible transition per 20 s of runtime
TRANSITION LOG
JOIN TIME TYPE MEANING KEEP?
01 00:08.2 cut same scene yes
02 00:19.5 dissolve next morning yes
03 00:24.0 swipe (none - decorative) no -> cut
04 00:37.1 dip black chapter 2 yes
7. QA checklist and review prompts
Transition style consistent - same types and durations throughout.
No rhythmic interruptions - transitions sit on beats and do not stall dialogue.
Transition count minimized - every visible transition has a logged meaning.
No frozen or stuttering frames at a transition (missing handles).
Review prompts: which transitions carry meaning? Which are redundant? Where would a hard
cut work better?
8. Exercise
Take an edit (yours or a template) with many decorative transitions and duplicate the
project.
In the copy, replace every decorative transition with a cut or a dissolve according to
the decision matrix.
Find one place where you can build a match cut on action and try it.
Fill in a transition log and a transition style spec for the project.
Show both versions to someone and ask which one looks more professional and why. Note
the answer next to your log.