How to Manage Mixed Frame Rates and Resolutions in NLE Timelines

The first clip dropped into a new sequence is a 59.94 phone shot. The A-cam is 23.976 UHD. The archive is 29.97 interlaced. The show delivers 1080p 23.976, and social wants 9:16 cutdowns next week. Every major NLE will play all of that in one timeline. The open question is what compromises it made to get there. So set the sequence to the primary delivery format, then conform everything else into it on purpose. A timeline holds one frame size at a time. It holds one frame rate, one field order, and one pixel aspect ratio. Automatic scaling and automatic frame sampling are not the same thing as a decision your team made.

Set the sequence from the delivery target, not whichever clip lands first.

Pick the timeline from the delivery, not the bin

Start a mixed-format project from the final master. If there are several masters, start from the most important one. Broadcast specs come from the network or platform, and 1080i 59.94, 1080p 23.976, and 2160p 25 are all common. Theatrical means a DCI raster and aspect ratio. Branded and web work often means a family of deliverables at once: UHD and HD landscape, plus vertical and square cutdowns. Your timeline decision should account for these format properties:

Frame rate: 23.976, 24, 25, 29.97, 50, 59.94, or another required rate
Frame size: HD, UHD, DCI 2K, DCI 4K, vertical, square, or custom
Aspect ratio: 1.78, 1.85, 2.00, 2.39, 9:16, 1:1, or platform-specific
Scan type: progressive or interlaced
Pixel aspect ratio: square pixels in modern media, but not always in legacy media
Audio sample rate: 48 kHz for professional video workflows
Color pipeline: SDR, HDR, log-managed, display-referred, or ACES-style workflow

These are project decisions. Acquisition serves the creative intent; delivery constrains the timeline. A post meeting before shooting is still the cleanest place for your team to settle it. That meeting earns its hour on shows with framing charts and safe areas to honor, high-speed footage to interpret, and archive or social extracts to fit. If the project is already shot, make the same decision as early as possible in editorial. Once cutting starts, changing the sequence frame rate ranges from painful to impossible depending on the NLE. Even where it is technically possible, the change shifts edit timing, speed effects, and captions. It reaches VFX turnovers, audio references, and online conform behavior too.

Frame rate is the hard choice

Resolution mismatches are the manageable half of this problem. Frame-rate mismatches are where projects get weird. A timeline plays at one frame rate. When a source clip does not match, the NLE has to decide which source frames appear on which timeline frames. Video frames are indivisible, so there is no showing half a source frame for half a timeline frame. The software has five ways out. It can repeat or drop whole frames. It can blend adjacent frames or synthesize new ones. Or it can change playback speed.

Frame-rate conversion maps source frames unevenly when rates don't match.

Those are very different operations.

Method	What it does	Best used when	Common risk
Frame sampling	Drops or repeats whole frames to match the timeline rate	Quick real-time playback when minor cadence issues are acceptable	Judder, uneven motion, duplicate frames
Frame blending	Blends adjacent frames to smooth the rate mismatch	Temporary conversions or shots with limited motion	Ghosting, soft edges, smeared movement
Optical flow or motion estimation	Synthesizes new frames between existing frames	High-quality slowdowns or conversions where smooth motion matters	Warping, tearing, strange artifacts around fast motion or occlusion
Speed conforming	Changes playback speed so captured frames play at the timeline rate	High-speed footage intended as slow motion, or rate changes with creative intent	Wrong duration if used accidentally, sync issues with production audio
Pulldown handling	Adds, removes, or preserves a 24-ish to 29.97 or 59.94 cadence	Broadcast workflows, telecined archive, legacy masters	Baked-in cadence errors, interlace artifacts, duplicate frames
Standards conversion	Converts between rate families such as 25, 29.97, 50, and 59.94	Required delivery in a different regional or broadcast standard	Motion artifacts, audio speed or pitch issues if not managed deliberately

In shorter form, the six methods work like this:

Frame sampling: repeats or drops frames to fit the timeline
Frame blending: blends adjacent frames to reduce stutter, often at the cost of ghosting
Optical flow or motion estimation: creates new intermediate frames, which can look smoother but may create warping artifacts
Speed conforming: plays all captured frames at the timeline rate, creating true slow motion or fast motion
Pulldown: maps 24-ish material into a 29.97 or 59.94 cadence, often for broadcast or legacy workflows
Standards conversion: converts between rate families, such as 25 to 29.97 or 23.976 to 25

So “make it fit” isn't one operation. A 59.94 clip in a 23.976 sequence can be frame-sampled to normal-speed playback, or interpreted as slow motion. A 29.97 archive clip in a 23.976 documentary timeline can be frame-sampled or motion-converted, or it can get cadence removal if it holds telecined film. Those paths produce different motion, different artifacts, and sometimes different durations.

Don't confuse slow motion with conversion

High-speed footage is one of the most common sources of mixed frame rates. The editorial intent decides how the clip should behave. The number stamped on the file does not. A camera can record 120 fps with a playback base of 23.976. The NLE may already see that clip as slow motion. Its file metadata tells the software to play those 120 captured frames across a 23.976 timeline. No frame-rate conversion is needed for the slow-motion look, because the clip arrived conformed. A 59.94 clip behaves differently. If the editor wants it to play in real time in a 23.976 timeline, the NLE has to convert the motion by dropping, blending, or synthesizing frames. If the editor wants that same clip as slow motion, interpret or speed-adjust it so every source frame is used over a longer duration. This distinction is worth making clear in bins and notes. Label high-speed material by intent, not just technical rate:

Real-time 59.94 for conversion to timeline
59.94 intended as 40 percent slow motion in 23.976
120 fps base-conformed to 23.976 in camera
29.97 archive with possible pulldown
Variable frame rate phone capture requiring transcode

Label media that way and editors stop guessing. A stutter is either a bad conversion or a deliberate speed change, and the note says which.

Resolution is more forgiving, but framing isn't

Most modern NLEs handle mixed frame sizes without drama. A UHD clip can sit in an HD timeline, and a 1080 clip can sit in a UHD timeline. A 4.6K camera source can be reframed inside a 2K or HD finish. The software scales clips according to the sequence or project settings, and you can override sizing clip by clip. The default scaling choice may not match the creative framing.

Fit preserves the full image with margins; fill crops to cover the frame.

Typical scaling behaviors include:

Fit: scales the whole image inside the frame, possibly creating letterbox or pillarbox areas
Fill: scales until the frame is filled, cropping edges if the aspect ratio differs
Stretch: distorts the image to fill the frame, which is wrong unless the distortion is intentional
Center crop or no scale: keeps the source size relative to the timeline, cropping large sources
Custom transform: manual scale, position, rotation, and crop decisions per shot

A UHD interview in an HD timeline gives you room to punch in or reframe. A 1080 source in a UHD timeline has to be enlarged, which some content survives and some does not. Two framing questions need a house answer before the cut gets deep:

A 4:3 archive clip in a 16:9 show: pillarbox, crop, blur fill, graphic treatment, or recreated background
A 2.39 camera frame inside a 1.78 delivery: letterbox, center extraction, or alternate framing

Technical resizing and creative composition are the same decision seen from two sides, so settle delivery format and framing intent together. If production shot open gate for multiple aspect ratios, editorial needs the framing guides or the notes that go with them. Otherwise a temp reframe becomes the final reframe by accident.

How the major NLEs tend to handle it

The details vary by application. The pattern does not. The timeline has fixed format settings, and the NLE conforms mismatched clips through project, sequence, or clip-level controls. Final Cut Pro is famously automatic at project creation. Add the first video clip to a new project and it can set the project format, frame size, and frame rate from that source media. That is convenient for quick jobs and risky for professional mixed-format work when the first clip isn't representative. Final Cut also lets you modify project settings and control frame size and frame-rate conform behavior clip by clip. Create or adjust the project intentionally instead of letting the first inserted clip define the show. DaVinci Resolve reads resolution, frame rate, and image scaling from project and timeline settings. Those same settings drive monitoring and output behavior. Mixed frame sizes are handled through timeline resolution and image scaling, with manual overrides available per clip. Resolve also supports individual timeline settings, which is what you want when one project owes several deliverables at different resolutions or sizing rules. Some frame-rate choices in Resolve are foundational, so set them early. Premiere Pro, Media Composer, and other NLEs follow the same broad logic under different menu names. A sequence has settings, and the NLE adapts clips that don't match. You can choose scale behavior, interpret footage, and create proxies. You can also render previews and apply motion interpolation or timewarp effects. Finding the button is rarely the hard part. Documenting the intended handling is, so another editor or assistant, and later the colorist and online artist, get the same result.

Watch for pulldown, interlacing, and variable frame rate

The worst mixed-format issues come from media that looks normal at first glance. Archive and broadcast masters carry hidden complications. So do screen recordings, phone footage, and web downloads. Pulldown is the classic trap. A file may report as 29.97 while the content underneath is 23.976 film-style material with a repeated-field or repeated-frame cadence. Cut it as ordinary 29.97 into a 23.976 timeline and you can bake in uneven motion or duplicate frames. When the cadence is consistent, removing pulldown before editorial or during ingest recovers the original progressive cadence. When the cadence is broken, expect shot-by-shot treatment. Interlaced footage is another place to slow down. An interlaced source in a progressive timeline isn't automatically a problem, but deinterlacing quality is. Bad deinterlacing creates combing, softened motion, or jagged edges. When the delivery itself is interlaced, field order comes into play as well. A field-order mistake makes motion vibrate or judder, and it is obvious on proper monitoring. Variable frame rate footage comes from phones, webcams, and screen recordings, plus some capture utilities. The file may average 30 fps while its timing drifts across the clip. NLEs have improved at reading it. Even so, transcode variable frame rate sources to a constant frame rate mezzanine before serious cutting. That is what keeps sync sound and turnovers reliable in longform editorial and multicam. These sources deserve extra attention during ingest:

Phone video with variable frame rate
29.97 files that may contain 23.976 pulldown
Interlaced archive masters
Clips with mismatched or missing timecode
Camera files recorded at high speed for slow motion

Normalize or label them at ingest. Once they spread through an edit and get duplicated into selects, they become much harder to trace.

Use proxies and dailies to lock the intent early

Casual proxy-making hides format problems until online. A proxy should be lightweight, and it should still preserve everything conform depends on:

Source filename, reel or tape name, and timecode
Frame rate interpretation and audio sync
Color transform notes and framing

On high-volume shows, assistants receive material from many cameras, locations, and departments. An unscripted day can deliver stage cameras, interviews, and behind-the-scenes footage. The same day can deliver high-speed cameras, follow-home crews, and archival inserts. That volume makes “just transcode everything to the edit codec” tempting, but decide the mixed frame-rate handling before the transcode batch runs. Good proxy and dailies decisions include:

Transcode variable frame rate sources to constant frame rate
Preserve source timecode and reel metadata wherever possible
Keep proxy frame rate aligned with the intended editorial interpretation
Burn in source name, source timecode, and frame rate for review copies when useful
Document any pulldown removal, deinterlacing, or standards conversion

Dailies are more than viewing files. They are the bridge from set to post. Frame them properly, manage color enough for editorial, and keep them technically consistent. Editors then cut faster, and the post supervisor can trust that the offline isn't building avoidable conform surprises.

When to convert media instead of relying on the timeline

Letting the NLE conform clips live in the timeline is fine, especially during rough cut. Some sources still deserve a pre-converted mezzanine. Consider converting or normalizing media before edit when:

The source is variable frame rate
The source has unstable pulldown cadence
The source is interlaced and the project is progressive
The source codec performs poorly in the NLE
The online, color, or VFX team requires a specific format

Live conversion is flexible. It also makes renders slower and results less predictable across systems. Baking a high-quality conversion into a mezzanine file removes the ambiguity, at the cost of another asset to track and some later flexibility. For hero shots, archive-heavy sequences, and anything going to VFX, the safer path is to agree on the conversion method and create a managed intermediate.

Render settings are part of the format decision

A timeline render isn't automatically the same as the source, the project, or the final master. Render settings can override timeline resolution and resize clips. They can also change codec, change field order, and apply frame-rate conversion. In mixed-resolution projects, some tools render individual clips at the project or render resolution. Others render source clips at their original resolution for dailies or turnovers. That distinction is the whole section. A master render should match the delivery spec. A render for dailies or review files may instead need source resolution, source frame rate, handles, or no timeline resize at all. So may a VFX plate or an archival pull. One render preset can't safely serve every purpose.

Different deliverables may need separate export decisions from the same edit.

For delivery renders, pay attention to these settings in the export or delivery page:

Output frame rate
Output frame size
Scaling method and resize filter
Field order or progressive setting
Motion interpolation or frame sampling mode
Codec, bitrate, and chroma subsampling
Audio sample rate and channel layout
Whether the export uses previews, optimized media, proxies, or render cache
Whether the export includes captions, mattes, LUTs, and color management as intended

Then watch motion during QC, not only sharpness. Play the pans and the handheld shots. Play the dance, sports, and fast gestures. Play the rolling credits, the lower-thirds, and the archive inserts, all on the intended monitoring path. Frame-rate mistakes show up as cadence problems before they show up as obvious visual artifacts.

Multiple deliverables may need multiple timelines

One master, one timeline format, one edit. A show that owes HD and UHD masters plus vertical and square cutdowns needs separate timelines or output passes with their own settings. The same applies when textless, broadcast, and social variants are on the list. Nesting or duplicating a locked sequence into alternate formats can work, but only if someone reviews the reframes and graphics, then the subtitles and speed effects, in each format. A UHD 16:9 timeline can generate an HD 16:9 master cleanly. It doesn't automatically generate a good 9:16 version. A 23.976 creative master can be converted for a 29.97 delivery, but treat that conversion as its own deliverable-specific process rather than an afterthought during the edit. A texted broadcast version and a textless international version may share picture timing while requiring different graphics, mattes, and QC passes. The more deliverables you have, the harder the sequence names have to work. Put the frame rate and raster in the name, along with the aspect and the version. “Final_final_v12” tells the finishing team nothing. “EP103_locked_2398_ UHD_178_texted” is ugly, and it removes the guesswork.

The decision that keeps mixed-format timelines sane

Undocumented automatic conforming is the problem. The recurring fix is short:

Set the timeline from the delivery, not from the bin.
Treat frame rate as the choice you cannot easily undo.
Treat resolution as a technical scale operation and a creative framing operation at once.
Decide per clip whether it plays in real time, becomes slow motion, or gets converted outside the timeline.
Normalize variable frame rate, pulldown, and interlaced archive early, and do the same for multicam-heavy material.
Render each output for its actual purpose instead of from a generic preset.

Modern NLEs are very good at hiding format mismatches. That helps while cutting. It hurts at online, when nobody knows what the software hid.

FAQ

Set the timeline to the primary delivery format. The first clip you import or edit should have no say in it. Build the sequence from the master's required frame rate, resolution, and aspect ratio, then from its scan type and pixel aspect ratio, plus its audio sample rate and color pipeline. Letting a random first clip define the sequence creates hidden scaling, cadence, or export problems later.

The NLE adapts the source frames to the timeline frame rate. Depending on the settings, it repeats or drops whole frames, blends them, synthesizes new frames with optical flow, applies pulldown, or changes playback speed. Each method produces different motion and different artifacts, so choose one deliberately in editorial or finishing.

No. If the clip plays in real time, the NLE converts its motion to 23.976 by dropping, sampling, blending, or synthesizing frames. If you want slow motion, interpret or speed-adjust the clip so more of its captured frames play over a longer duration. Real-time conversion and slow-motion conforming are different operations.

Pre-convert when the source is variable frame rate, carries unstable pulldown, or is interlaced in a progressive project. Pre-convert as well when the codec performs poorly in the NLE, when the clip will be used heavily in multicam, or when online, color, VFX, or delivery needs one approved conversion. Timeline conversion stays flexible, but a managed mezzanine reduces ambiguity and improves reliability.

A locked timeline can be duplicated or nested into alternate timelines. Each deliverable still needs its own review pass for framing and graphics, for subtitles, speed effects, and captions, and for export settings. A UHD 16:9 master makes a clean HD 16:9 output, but it will not create a well-composed 9:16 or 1:1 version on its own.

Treat those decisions as asset metadata rather than tribal knowledge. Aspect lets teams add custom fields that record whether pulldown was removed, whether a VFR source was transcoded, whether a clip was deinterlaced, and whether it is intended slow motion. The handling then travels with the asset in custom metadata.