How do I sync video clips recorded at different frame rates?

Start with a small inventory. For each clip, note its frame rate and identify a section with motion that will make uneven playback noticeable, such as a pan or someone walking. Then check the project or timeline’s frame rate and the requirements for your intended output. Don’t assume one source clip’s rate is automatically right for the whole edit.

In Final Cut Pro for Mac, the first video clip generally determines the project format, frame size, and frame rate from its source properties, so check the project settings before building the edit around them [S1]. Final Cut Pro also has project settings for format, resolution, and frame rate [S2]. Other editors may work differently.

If you mean syncing separate recordings of the same event, that’s a separate task from frame-rate conforming: first align the recordings using a shared event or audio reference, then inspect how each clip plays in the project.

Compare the source-clip properties with the project or timeline properties in your editor. Use the output requirements as your decision point. If those requirements are unclear, confirm them before doing detailed timing work.

For example, suppose one clip’s properties show 24 fps and another’s show 60 fps. Record those values, check the project’s rate and delivery requirements, and test a representative section of each clip. Those example numbers don’t establish what rate your project should use; that depends on your intended output and workflow.

In Final Cut Pro, check project settings before committing to a timeline: Apple says an existing project’s frame rate cannot be changed unless its timeline is completely empty [S2]. That constraint is product-specific. If a project was created from a clip with an unsuitable rate, check your editor’s documented options rather than assuming changing a clip will change the project.

Inspect each mismatched clip rather than forcing every clip into one assumed conversion mode. In Final Cut Pro, the Video inspector offers Fast (Floor), Fast (Nearest Frame), and Good (Frame Blending) for conforming frame rates. Apple describes different tradeoffs and notes that nearest-frame processing may cause visual stuttering [S1]. Other editors may use different names or behavior, so check their documentation.

Test a short, representative section of each type of footage. Compare the available settings on motion that matters in the shot, and look for distracting stutter, blended-looking motion, or timing that no longer feels right. There is no single choice guaranteed to suit every clip.

Preview the clips in context, especially where the frame rate changes or movement makes uneven motion noticeable. Check that cuts still land where intended and that the action and clip duration make sense in the sequence. Conforming choices affect visual motion, so preview the result rather than judging by a settings label alone [S1].

Keep a note for each test: “Clip: [name], source rate: [value], project rate: [value], conform setting: [option], review: [acceptable / test again], notes: [timecode or observation].” This helps you track what you reviewed; it does not predict how another editor will process the footage. The cited Apple guidance describes Final Cut Pro behavior, not the right project rate for every delivery.