How to Manage Mixed Frame Rates in a Single Timeline

Set the timeline frame rate from the delivery spec, not from the first clip you drag into the project.

Choose the timeline from the delivery target, then fit mixed sources into it.

That one decision prevents most mixed-frame-rate problems from turning into editorial archaeology later. For a 23.976 master, build a 23.976 timeline. For 25p broadcast delivery, build 25p. For a main output at 29.97 or 59.94, use that rate. The source footage can be 23.976, 24, 25, 29.97, 30, 50, 59.94, 60, 100, 120, or something weird from a phone. The timeline is the container that defines how motion is sampled, where edits fall, how timecode is counted, and how every downstream department understands the edit. Mixed frame rates aren't automatically a problem. Modern NLEs can place mismatched clips in a single sequence and conform them to the timeline. The problem is when your team doesn't decide which clips should maintain real-time speed, which clips should become slow motion, which clips need conversion, and which clips are risky enough to normalize before editorial starts cutting.

Pick the timeline rate from the master, not the camera bin

The “most common source frame rate” matters, but only after you know the master requirement. For example, a documentary might have interviews at 23.976, archival at 29.97, drone at 59.94, phone footage at variable frame rate, and screen recordings at odd rates. If the delivery is a 23.976 streaming master, your team should usually build the editorial timeline at 23.976. The 29.97 archive will need cadence handling, while the 59.94 drone footage may play real time with frame dropping or may be interpreted for slow motion. Your team may need to transcode the VFR material, but none of that means the timeline should become 59.94 just because someone added the first beautiful drone shot to the sequence. The timeline decision should come from the project’s technical spec. At minimum, lock these early:

Master frame rate
Raster and aspect ratio
Progressive or interlaced delivery
Audio sample rate, usually 48 kHz for production workflows
Timecode convention, including drop-frame or non-drop-frame where relevant
Color pipeline and offline or online media plan
VFX pull requirements, if plates need a different handling path

This is why workflow memos and dailies specs matter. Camera, sound, editorial, VFX, and finishing all need to know the base frame rate and audio assumptions. If the dailies vendor makes proxies at one rate, editorial cuts in another, and finishing receives camera originals interpreted a third way, the conform becomes a detective job. A useful rule: choose the timeline rate based on the primary master, then create alternate timelines or derived exports for secondary deliverables. Don't make the edit timeline chase every social cutdown, broadcaster, event screen, or review file unless that's actually the primary output.

Know what your NLE is doing when rates don't match

When you put a mismatched clip into a timeline, the NLE has to make the source frames fit the sequence clock. It can do that in several ways, and each one creates a different visual result.

Method	Duration behavior	Best use	Main risk
Frame sampling	Preserves real-time duration by dropping or repeating frames	Simple conversions, edits with limited motion, cases where artifacts must stay predictable	Judder, repeated motion bumps, or uneven cadence
Frame blending	Preserves real-time duration by mixing adjacent frames	Mild mismatches where a softer look is acceptable	Ghosting, soft edges, smeared motion
Optical flow or motion estimation	Preserves real-time duration by generating new frames	Shots with clean motion where smoother cadence matters	Warping around limbs, wheels, water, flashes, or compression noise
Pulldown or cadence conversion	Preserves real-time duration while mapping one cadence to another	Film-to-video or video-to-film family conversions such as 23.976 and 29.97 workflows	Incorrect cadence, hard-to-spot motion rhythm problems
Clip interpretation or conforming	Changes playback speed so original frames play at the new rate	Intentional slow motion, speed normalization, MOS shots where duration can change	Sync drift, duration changes, audio pitch or timing problems

Common frame-rate handling methods include:

Frame sampling: repeats or drops frames to preserve real-time speed
Frame blending: blends adjacent frames to smooth mismatches, often with ghosting
Optical flow or motion estimation: generates new in-between frames, often smoother but artifact-prone
Pulldown or cadence conversion: maps film-style rates into video-style rates
Clip interpretation or conforming: changes the playback rate of the clip itself

The key distinction is real-time conversion versus playback-speed conversion. If you place a 30p clip in a 24p timeline and want it to play in real time, the NLE must discard or resample frames. The clip still lasts the same number of seconds, but its motion cadence changes. If you interpret that 30p clip as 24p, the NLE plays every original frame at 24 frames per second. The motion is smooth because the NLE skips no frames, but the clip becomes slower and longer.

Real-time conversion keeps duration by sampling frames into fewer timeline slots.

That difference is where many timeline problems start. “Make it fit the sequence” and “make it slow motion” aren't the same operation.

Decide which clips are real-time and which are overcrank

Camera teams often shoot high-frame-rate footage for slow motion, but not always. A camera may record 59.94p because the camera operator wanted smoother handheld motion, because the sports delivery is 59.94, because the camera default was never changed, or because someone planned to slow it down later. Your editorial team needs to know the intent. For high-frame-rate media in a lower-frame-rate timeline, there are two normal paths:

Preserve real-time speed when the action should happen at normal duration
Interpret or conform the clip to the timeline rate when the camera team shot the clip as overcrank for slow motion

A 119.88 fps clip in a 23.976 timeline can become clean 20 percent speed slow motion if the NLE plays every recorded frame at the timeline rate. That's an intended use of mixed frame rates. A 59.94 clip in a 23.976 timeline can become 40 percent speed. A 50 fps clip in a 25p timeline can become 50 percent speed. But if the same 59.94 clip is production dialog, interpreting it as 23.976 is wrong. It will stretch the duration and throw sync out immediately. In that case your team should keep it playing in real time, with the NLE adapting frames to the timeline. This is a logging issue as much as a technical one. During ingest, label the intent of non-base-rate clips. Don't treat “60p real-time B-cam” and “60p slow-mo insert” the same just because they have the same metadata.

Watch cadence, especially across 24, 25, and 29.97 families

Cadence is the visible rhythm of motion after the NLE repeats, drops, blends, or synthesizes frames. Bad cadence is the “why does this pan feel stuttery?” problem. It's especially obvious on slow camera moves, scrolling graphics, sports, car shots, and handheld footage with fine detail. Some frame-rate combinations are easier than others. A 50 fps clip in a 25p timeline has a clean 2:1 relationship. A 60 fps clip in a 30p timeline also has a clean 2:1 relationship. A 120 fps clip in a 24p timeline has a clean 5:1 relationship if the exact rates line up. You can predict these conversions. Other combinations are messier. 29.97 into 23.976 often needs a cadence decision. 25 into 23.976 may involve a speed change if you want every frame preserved, or frame interpolation if you need real-time duration. 24.000 and 23.976 look almost identical on a short clip, but they aren't the same rate. Over a long program, that 0.1 percent difference matters for sync, duration, and timecode. Common cadence problems show up as:

Repeating motion bumps on pans or tilts
Ghosted edges from frame blending
Warping around limbs, wheels, water, or flashing lights from optical flow
Micro-stutters from phone or screen-recording material
Inconsistent motion between A-cam and B-cam angles in a multicam edit

Optical flow can be excellent for clean motion, but it can also invent terrible frames around fast action, occlusion, flashes, motion blur, and compression noise. Frame sampling may look harsher but more honest. Frame blending may hide judder at the cost of softness and ghosting. The right choice depends on shot content. Judge cadence on motion, not on still frames. Play the shot at full speed on a proper monitor if you can. A freeze frame won't tell you whether the conversion rhythm feels wrong.

Treat variable frame rate as a different kind of problem

Variable frame rate footage doesn't maintain a constant frame interval throughout the file. Phones, action cameras, webcams, meeting recordings, game captures, and screen recordings can all create VFR media. VFR can appear harmless in a bin because the NLE might report something close to 29.97, 30, 59.94, or 60, but inside the file, the frame timing may shift. That can cause audio drift, random stutter, exports that don't match the edit, or clips that behave differently after render. For professional editorial workflows, your team should usually normalize VFR before it spreads through the edit. Transcode it to a constant-frame-rate mezzanine codec at the intended working rate or at a rate that preserves the source timing cleanly. For SDR editorial, ProRes 422, DNxHR, or another house-approved mezzanine format is usually easier to manage than a long-GOP phone original. For HDR or log sources, make sure the transcode preserves the required color metadata and bit depth.

Normalize variable-frame-rate footage into a stable constant-frame pattern before editing.

Do this early because replacing a few VFR clips during ingest is boring, while replacing dozens of edited VFR clips after lock is harder.

Set up Premiere and Resolve so they don't surprise you

Premiere Pro and DaVinci Resolve can both mix frame rates, but they have different “gotcha” moments. In Premiere Pro, when you add clips to a sequence with a mismatched frame rate, Premiere conforms them to the sequence while maintaining playback speed. That means a 30p clip in a 24p sequence will still play for the same real-world duration unless you explicitly interpret the footage or apply a speed change. You can inspect original frame rate and frame size in the Source Monitor or project metadata, then use interpretation settings when you intentionally want a clip to play back at a different rate. That behavior is useful, but it also means editors can accidentally cut a high-frame-rate slow-motion clip as real-time footage because Premiere is trying to preserve duration. If the camera team shot a 120 fps clip for slow motion, interpret or retime it intentionally. Don't assume the NLE knows the creative intent. In Resolve, project and timeline frame-rate settings deserve extra attention at project creation. Resolve can support mixed frame rates, and your team can control its mixed frame rate handling through project settings and import settings for workflows such as AAF or XML. The mistake to avoid is letting the first imported or edited clip define the project frame rate when that clip isn't the master rate. Accept a Resolve prompt to change the project settings to match incoming media only when that media truly represents the intended timeline format. Resolve also has timeline-level options, retime controls, optical flow settings, and clip attributes that affect how clips play. These are useful, but they can create confusion if one editor interprets footage at the media-pool level while another applies speed changes in the timeline. Agree where the decision lives. A clean team workflow usually separates these actions:

Project or timeline settings define the master edit rate
Clip attributes or interpretation define intended playback rate for source media
Timeline speed effects define creative retimes
Render or export settings define deliverable-specific output

When your team mixes those layers together, conforms become harder to trust.

Keep audio sync tied to speed decisions

Audio sync is where frame-rate choices stop being cosmetic. If a clip’s playback speed changes, its production audio changes duration with it unless you detach, replace, or process the audio separately. Real-time frame-rate conversion should preserve duration. You can convert a 25 fps interview in a 23.976 timeline to the timeline cadence while still lasting the same number of seconds, although the motion may need attention. But if you conform 25 fps picture to 23.976 by playing every frame at the slower rate, the clip becomes about 4 percent longer. Production audio will no longer sync unless you slow it by the same amount. If you slow it, pitch may drop unless you apply pitch correction.

Changing picture playback speed can stretch duration and pull it away from synced audio.

The same applies to 24.000 versus 23.976, just at a smaller scale. If you conform a 24.000 fps source to 23.976, you change speed by about 0.1 percent. On short MOS shots, that may be irrelevant, but on long sync dialog, concert footage, or multicam, it can matter. Your team should usually keep production audio at 48 kHz and sync it against correct timecode or slate information during dailies. If cameras and audio recorders run at different frame-rate or timecode assumptions, the workflow memo needs to state the base frame rate, audio sample rate, and timecode method. Timecode sync generators and smart slates reduce manual syncing, but they only help if your team configures every device to the same plan. Watch for these audio failure modes in mixed-rate projects:

Dialog slowly drifting against picture over a long take
Scratch audio matching but external WAV files drifting
Music performance footage losing sync after a 24 to 25 or 25 to 24 conform
Pitch changes after speed conversion
Drop-frame and non-drop-frame timecode confusion in 29.97 workflows

Document intentional speed changes. Don't use interpretation as a sync fix when the speed change isn't intentional. Find the actual source of the mismatch.

Use separate paths for editorial, VFX, archive, and deliverables

Not every source in a mixed-frame-rate timeline needs the same treatment. A clean edit may contain several frame-rate strategies at once. An editorial timeline might keep interview footage real time, interpret high-speed B-roll for slow motion, transcode VFR phone clips to constant frame rate, and send archival 29.97 material through a proper standards conversion. VFX plates may need source-native frame ranges, while the offline timeline needs converted proxies. Social cutdowns may need 29.97, 30, 50, or 60 fps exports even when the hero master is 23.976. The important part is to avoid baking accidental conversions into the wrong asset. When a VFX vendor needs the original 59.94 plate, don't send only a 23.976 editorial render unless your team and the vendor agreed that's the plate. When finishing needs to relink to camera originals, your team needs to document retimes, interpreted clips, and mixed-rate decisions clearly enough to reproduce. For dailies and proxies, decide whether each source should be preserved at source speed or normalized to the edit rate. There's no universal answer. For scripted production, the dailies team often builds dailies around the show’s base frame rate so editorial can cut immediately. For sports, live events, and documentary, retaining source-rate information may be important for later slow motion, replay, or archival handling.

Make the timeline boring on purpose

The best mixed-frame-rate workflow is the one where every mismatched clip has an obvious reason for behaving the way it does. Set the timeline from the master. Inspect source rates during ingest. Label high-frame-rate intent. Normalize VFR. Use interpretation only when you mean to change playback speed. Use frame sampling, blending, optical flow, or standards conversion based on the shot. Keep audio sync tied to duration and timecode. Mixed frame rates are normal now. Phones, mirrorless cameras, cinema cameras, drones, action cams, screen captures, archive, and stock can all show up in the same edit. The timeline can handle that, but only if the team treats frame rate as a workflow decision instead of a metadata surprise.

FAQ

In most professional workflows, the timeline frame rate should match the primary delivery spec, not the first clip imported or the most common camera rate. If the master is 23.976, 25p, 29.97, or 59.94, build the main edit timeline at that rate and decide how each mismatched source should be handled inside it.

Letting footage play in real time preserves its duration and makes the NLE drop, repeat, blend, or synthesize frames to fit the timeline. Interpreting or conforming footage changes the playback rate of the clip itself. For example, a 60 fps clip interpreted as 24 fps will play slower and longer, which is useful for slow motion but wrong for synced dialogue unless the audio is handled accordingly.

Uneven motion usually comes from cadence problems. When source frames don't divide cleanly into the timeline rate, the NLE must repeat, drop, blend, or generate frames. This can create visible bumps on pans, ghosting from frame blending, warping from optical flow, or micro-stutters from phone and screen-recording footage. The best fix depends on the shot, not just the frame-rate numbers.

Variable frame rate footage should usually be transcoded to a constant-frame-rate mezzanine file before serious editorial work. Phones, webcams, meeting recordings, game captures, and screen recordings can report a familiar rate such as 29.97 or 30 while still changing frame timing inside the file. Normalizing early helps avoid audio drift, random stutter, relink problems, and exports that don't match the edit.

Yes. Real-time frame-rate conversion should preserve clip duration, but interpreting footage to a different rate changes duration. For example, conforming 25 fps picture to 23.976 makes it about 4 percent longer, so production audio will drift unless it's slowed by the same amount and pitch is managed. Sync workflows should keep audio at 48 kHz, use correct timecode or slate references, and document any intentional speed changes.

That decision should be logged as part of ingest, not guessed later in the edit. Aspect can hold clip-level notes and fields for intent, camera rate, interpreted rate, and sync status using custom metadata.