Convert 23.98 to 29.97 Calculator
Quickly convert footage timing between 23.976 fps and 29.97 fps. Choose whether you want to preserve the same real-world duration or keep the exact same frame count and calculate the new runtime after conforming.
Frame Accumulation Comparison
How to use this convert 23.98 to 29.97 calculator
If you work in editing, finishing, motion graphics, VFX, archive transfer, streaming prep, or broadcast delivery, you will eventually need to convert material between 23.976 fps and 29.97 fps. This calculator is built to make that process fast and accurate. You enter a value, choose whether that value represents seconds, minutes, or total frames, then select your source and target frame rates. The final step is choosing your conversion mode: preserve duration or preserve frame count.
Those two modes matter because frame rate conversion can mean two different things in practice. In one workflow, you keep the same real running time and calculate how many frames are needed at the new frame rate. In another workflow, you keep the exact same frames and simply play them back at a different frame rate, which changes the duration. Editors, assistant editors, online finishing artists, and media managers often use both approaches depending on the delivery specification.
For most searchers looking for a “convert 23.98 to 29.97 calculator,” the key question is simple: what happens to my clip when I move it from 23.976 to 29.97? The short answer is this:
- If you preserve duration, the target frame count becomes higher because 29.97 contains more frames per second than 23.976.
- If you preserve frame count, the clip becomes shorter because the same frames are displayed faster at 29.97.
- The ratio from 23.976 to 29.97 is exactly 1.25, which is why many conversions are easier than they first appear.
Why 23.98 and 29.97 are not the same as 24 and 30
This is one of the most important concepts in professional media workflows. Although people often say 23.98 and 29.97 conversationally, the actual frame rates are usually 23.976 fps and 29.97 fps. These are fractional rates derived from NTSC broadcast history. They are not exactly 24 or 30. That tiny difference may look harmless, but over long runtimes it creates meaningful drift if you use the wrong assumption in a timeline, transcode preset, camera report, or delivery sheet.
For example, a system set to 24 fps will not stay perfectly aligned with a 23.976 workflow over a long program. The same principle applies to 30 vs 29.97. When editors see clips slowly drifting out of sync, or subtitle events no longer matching, it is often because a supposedly “close enough” frame rate was used somewhere upstream.
Time and measurement precision matter in every technical environment, and agencies like NIST provide foundational reference material on accurate timekeeping. In digital preservation and moving image standards, institutions such as the Library of Congress emphasize the importance of preserving exact technical metadata, including frame rate. If you are building a serious post-production workflow, those details are not optional.
The core math behind converting 23.98 to 29.97
Here is the math the calculator uses.
1. Preserve duration
If the real-world running time stays the same, frame count changes.
Source frames = duration × source fps
Target frames = duration × target fps
For 23.976 to 29.97: target frames = source frames × 1.25
That means if your 23.976 clip lasts 60 seconds, it contains 1,438.56 frames. At 29.97, the same 60-second duration requires 1,798.2 frames. In practice, software handles real frames and timecode rules internally, but this calculation gives you the exact timing relationship.
2. Preserve frame count
If you keep the same exact frames and simply play them back at the target frame rate, the duration changes.
New duration = source frames ÷ target fps
Equivalent shortcut = original duration × source fps ÷ target fps
For 23.976 to 29.97: new duration = original duration × 0.8
That means a 60-second clip at 23.976 becomes 48 seconds long if the same frame count is conformed to 29.97. This is effectively a 125% playback speed relative to the original frame rate.
Reference table: frames generated over time
The following comparison table shows how many frames accumulate at each rate over common time spans. These values are useful when checking exports, validating timeline settings, or comparing source and target metadata in editorial tools.
| Time Span | 23.976 fps Total Frames | 29.97 fps Total Frames | Difference | Ratio |
|---|---|---|---|---|
| 1 second | 23.976 | 29.97 | 5.994 | 1.25x |
| 1 minute | 1,438.56 | 1,798.2 | 359.64 | 1.25x |
| 10 minutes | 14,385.6 | 17,982 | 3,596.4 | 1.25x |
| 30 minutes | 43,156.8 | 53,946 | 10,789.2 | 1.25x |
| 1 hour | 86,313.6 | 107,892 | 21,578.4 | 1.25x |
Common conversion outcomes in real workflows
The second table shows what happens when you keep the same frame count but change playback from 23.976 to 29.97. This is often called conforming or reinterpretation, depending on the software you use.
| Original Runtime at 23.976 | Same Frames at 29.97 | Runtime Reduction | Playback Speed Change |
|---|---|---|---|
| 30 seconds | 24 seconds | 20% | 125% |
| 1 minute | 48 seconds | 20% | 125% |
| 10 minutes | 8 minutes | 20% | 125% |
| 30 minutes | 24 minutes | 20% | 125% |
| 60 minutes | 48 minutes | 20% | 125% |
When to preserve duration and when to preserve frame count
Choose preserve duration when:
- You must deliver a program with a fixed runtime.
- You are converting a timeline or sequence for a broadcaster or streaming platform.
- You need graphics, subtitles, chapters, or ad markers to stay aligned to the same real-world timestamps.
- You are estimating render load, storage, or QC based on the target frame rate.
Choose preserve frame count when:
- You are conforming footage for a creative speed change.
- You want to reinterpret or remap source footage without generating synthetic frames.
- You are preparing slow-motion or speed-ramped assets from a master clip.
- You are checking how playback timing changes when moving footage into a different frame rate environment.
23.98 to 29.97 and the role of drop-frame timecode
A common source of confusion is the relationship between 29.97 frame rate and drop-frame timecode. Frame rate and timecode counting method are related, but they are not the same thing. A clip can be 29.97 fps while the timecode display may be drop-frame or non-drop-frame depending on the workflow and deliverable requirements.
Drop-frame timecode was designed to keep timecode labels aligned more closely with clock time in 29.97 systems. It does not mean frames are actually dropped from the media. It means certain frame numbers are skipped in the count display. If you are delivering to broadcast, this distinction matters. If you are simply estimating runtime or comparing accumulated frames, the raw fps math shown in this calculator is still the correct starting point.
For students, archivists, and technicians who need broader context on video and digital format description, university and government research libraries often provide excellent technical references. One useful academic resource is the digital curation and audiovisual guidance available through major university libraries, such as those maintained by Indiana University Libraries, where preservation practices and media metadata are discussed in professional archival contexts.
Practical examples
Example 1: You have a 12-minute documentary segment at 23.976 and need a 29.97 master with the same duration
Enter 12, choose minutes, source 23.976, target 29.97, and preserve duration. The calculator will show the source duration in seconds, the source frame count, and the higher target frame count needed to maintain the same running time. This is useful for planning standards conversion, optical flow processing, frame interpolation, or online finishing steps.
Example 2: You want to conform a 90-second shot from 23.976 to 29.97 using the same frames
Enter 90, choose seconds, source 23.976, target 29.97, and preserve frame count. The result will show a new runtime of 72 seconds. That means the shot now plays faster while using the same captured frames.
Example 3: You only know the total frame count
If a report, asset database, or camera sheet gives you total frames, select frames as the input unit. The calculator converts that frame count into source duration first, then computes the target values from there. This is especially useful when debugging editorial turnovers or comparing metadata between transcoding tools.
Common mistakes people make when converting 23.98 to 29.97
- Treating 23.976 as 24. The difference is small per second, but substantial over long programs.
- Mixing up frame rate conversion with timecode conversion. They are connected, but not identical operations.
- Forgetting to decide whether duration or frame count should remain constant. This is the biggest workflow mistake.
- Assuming every 29.97 deliverable requires the same timecode format. Some specs require drop-frame, others do not.
- Using a rounded mental estimate for final QC. Approximation is fine for planning, not for delivery verification.
Best practices for editors and post teams
- Confirm the exact source frame rate from camera metadata, not memory.
- Check whether your finishing or playout system expects 29.97 drop-frame or non-drop-frame labeling.
- Document whether you are conforming footage or converting timeline duration.
- When possible, test a short section first and verify sync against audio, captions, and graphics.
- Keep a calculator like this handy during prep, ingest, online, and delivery review.
Final takeaway
A good convert 23.98 to 29.97 calculator should do more than spit out a number. It should make the workflow logic clear. When you move from 23.976 to 29.97, you are dealing with a precise 1.25 ratio. If you preserve duration, frame count grows by 25%. If you preserve frame count, runtime shrinks to 80% of the original. Those two truths explain nearly every practical conversion scenario you will encounter.
Use the calculator above whenever you need to estimate frame counts, validate runtime changes, or explain the conversion to a client, producer, assistant editor, or QC technician. In fast-moving production environments, having the right frame rate math ready at the right time prevents expensive mistakes later.
Quick FAQ
Is 23.98 the same as 23.976?
In normal production language, yes. 23.98 is shorthand for 23.976 fps.
Is 29.97 the same as 30 fps?
No. They are close, but not the same. Over long durations, the difference matters.
What is the exact ratio from 23.976 to 29.97?
Exactly 1.25.
What if I want the clip to stay the same length?
Choose preserve duration.
What if I want to keep the exact same frames?
Choose preserve frame count.