Understanding Frame Rates and SMPTE Timecode: Which Is Not a Standard Frame Rate?
SMPTE timecode is a critical tool in video production, enabling precise synchronization of audio, video, and other elements across different devices and workflows. Day to day, at its core, SMPTE timecode assigns a unique identifier to each frame in a video sequence, using a hierarchical system of hours, minutes, seconds, and frames. This system relies heavily on frame rates, which determine how many frames are displayed per second. While many frame rates are compatible with SMPTE timecode, not all are considered standard. Understanding which frame rates are non-standard is essential for professionals working in video editing, broadcasting, or cinematography. This article explores the concept of standard frame rates for SMPTE timecode, identifies which frame rates are not standard, and explains why certain rates are excluded from the standard set Surprisingly effective..
What Are Standard Frame Rates for SMPTE Timecode?
Standard frame rates are those that have been widely adopted across industries and regions due to technical, historical, or regulatory reasons. The most common standard frame rates for SMPTE timecode include 24, 25, 29.Consider this: these rates ensure compatibility with equipment, software, and broadcasting standards. 97, 30, 50, and 60 frames per second (fps).
- 24 fps is the standard for traditional film, originating from the early days of cinema. It balances motion smoothness with cost efficiency.
- 25 fps is used in PAL-based systems, common in Europe, Asia, and parts of Africa.
- 29.97 fps is the standard for NTSC-based systems, prevalent in North America and some parts of South America.
- 30 fps is a rounded version of 29.97 fps, often used in digital video for simplicity.
- 50 fps is standard in regions using the SECAM system or in high-definition
SMPTE frameworks balance precision and adaptability through specific temporal parameters. In practice, 97 remain central, deviations such as 16 or 48 often arise from technical constraints or regional practices. Now, navigating them demands awareness of historical context alongside current demands, ensuring alignment with project requirements. In real terms, these exceptions highlight the dynamic interplay between universal standards and localized execution. While foundational rates like 24, 25, and 29.So a unified approach thus remains central, bridging technical rigor with practical execution. On the flip side, such understanding solidifies their role in maintaining clarity across diverse applications. This equilibrium underscores SMPTE’s enduring relevance in harmonizing disparate systems effectively Worth keeping that in mind. Still holds up..
Frame Rates That Fall Outside the SMPTE Standard
Even though SMPTE timecode can technically be generated for any integer‑based frame count, industry practice reserves the “standard” label for a relatively narrow set of rates. The following frame rates are commonly encountered in the field but are not considered part of the SMPTE‑defined standard suite:
| Frame Rate | Typical Use‑Case | Why It’s Non‑Standard |
|---|---|---|
| 16 fps | Archival footage, low‑bandwidth streaming, certain legacy security cameras | Too low for broadcast‑grade motion rendition; SMPTE timecode was never defined for sub‑24 fps because it would break the hierarchical hour‑minute‑second‑frame structure used in most professional workflows. And |
| 23. 94 fps | Sports broadcasting, high‑action live events | Similar to 23.94 fps itself is not a base standard. Also, sMPTE defines a drop‑frame mode for 60 fps, but 59. |
| 48 fps | High‑speed cinematic sequences (e.97 fps NTSC standard. g.SMPTE timecode does support it via the drop‑frame flag, but it is treated as a derivative of 24 fps rather than a primary standard. 976 fps** (often written as 23.Modern extensions exist, but they are vendor‑specific rather than part of the SMPTE baseline. 98) | “Film look” productions that need to be compatible with NTSC distribution pipelines |
| 90 fps | Virtual‑reality (VR) and high‑frame‑rate gaming capture | Exceeds the typical broadcast ceiling of 60 fps and requires extended timecode formats (e. |
| **59. | ||
| 120 fps | Slow‑motion sports analysis, scientific imaging | Like 90 fps, it falls beyond the conventional broadcast envelope and therefore is handled by proprietary extensions rather than the SMPTE baseline. |
And yeah — that's actually more nuanced than it sounds.
Technical Reasons for Exclusion
-
Word‑Length Limitation – The original SMPTE 12‑M timecode format encodes hours, minutes, seconds, and frames in a 32‑bit word. This design comfortably accommodates up to 60 fps (the maximum of the conventional broadcast set). Higher frame rates would require additional bits, breaking compatibility with legacy LTC (Linear Time Code) and VITC (Vertical Interval Time Code) hardware Simple, but easy to overlook..
-
Broadcast Regulation – Television standards bodies (e.g., FCC in the United States, ETSI in Europe) codify permissible frame rates for over‑the‑air transmission. SMPTE aligns its “standard” list with those regulatory limits to guarantee that timecode can be embedded directly into broadcast streams without conversion Worth knowing..
-
Inter‑operability Concerns – The professional ecosystem—cameras, switchers, editors, and playout servers—has been built around the six core rates. Introducing a non‑standard rate would necessitate firmware updates, new metadata handling, and potential synchronization errors when mixing sources.
-
Drop‑Frame vs. Non‑Drop‑Frame – For frame rates derived from NTSC (29.97, 59.94, 23.976), SMPTE provides a drop‑frame flag that tells the decoder to skip frame numbers at specific intervals to keep the timecode aligned with real‑world clock time. These derived rates are therefore considered “extensions” rather than independent standards.
Practical Implications for Professionals
| Scenario | Recommended Approach |
|---|---|
| Mixing 24 fps film with 30 fps broadcast footage | Convert the 24 fps clip to 23.Which means , MXF‑based timecode) and later down‑sample to a standard 60 fps master before embedding SMPTE timecode for delivery. Worth adding: |
| Shooting high‑speed action at 120 fps for a TV commercial | Record with a camera that outputs a separate metadata timecode (e. |
| Archiving legacy 16 fps security footage | Preserve the original frame rate but generate a secondary SMPTE timecode track at 30 fps for indexing; keep the original frame count in a separate metadata channel. Even so, g. In real terms, 97 fps pull‑up) and apply SMPTE drop‑frame timecode to maintain sync. 976 fps (or use a 24 fps‑to‑29. |
| VR production at 90 fps | Use SMPTE‑ST‑2110‑30 (IP‑based uncompressed video) which supports higher frame rates via extended timecode fields, or adopt a vendor‑specific timecode protocol that maps to SMPTE for final delivery. |
This changes depending on context. Keep that in mind.
Understanding where a frame rate sits relative to the SMPTE standard helps you decide whether to:
- Stay within the standard – simplifying workflow, reducing conversion steps, and ensuring seamless hand‑off between departments.
- Employ a bridge solution – using drop‑frame flags, timecode conversion utilities, or secondary timecode tracks to accommodate non‑standard rates without breaking downstream compatibility.
- Adopt a newer SMPTE extension – such as SMPTE ST‑2110 for IP‑based production, which expands the allowable frame‑rate range while preserving the familiar hour‑minute‑second‑frame hierarchy.
Future Directions
The industry is gradually moving toward IP‑centric production environments (SMPTE ST‑2110, SMPTE ST‑2084, etc.). These standards decouple timecode from the physical tape or LTC signal and embed it directly in network packets, allowing for arbitrary frame rates limited only by network bandwidth and processing power. While the classic SMPTE 12‑M list will likely remain the de‑facto reference for broadcast delivery for years to come, newer specifications already support 90 fps, 120 fps, and even variable‑frame‑rate (VFR) streams used in streaming platforms.
Despite this, the core principle remains unchanged: a reliable, hierarchical time reference that can be read by any compliant device. Whether you are working with a classic 24 fps film reel or a cutting‑edge 120 fps VR capture, the goal is the same—maintain precise synchronization across all elements of the production Worth keeping that in mind. That's the whole idea..
Conclusion
SMPTE timecode has endured for decades because it provides a simple, universally understood language for locating any frame in a video timeline. The standard frame rates—24, 25, 29.97, 30, 50, and 60 fps—represent the sweet spot where historical broadcast constraints, hardware limitations, and global regulatory frameworks intersect. On top of that, frame rates such as 16, 48, 23. 976, 59.94, 90, and 120 fps, while technically possible, sit outside this core set due to word‑length constraints, broadcast regulations, and interoperability concerns.
People argue about this. Here's where I land on it.
For today’s video professionals, the key takeaway is awareness: know which rates are native to SMPTE, recognize when a project demands a non‑standard rate, and apply the appropriate conversion or extension strategy to keep timecode accurate and compatible. As the industry continues to embrace IP‑based workflows and higher frame‑rate content, SMPTE’s underlying concepts will evolve, but the need for a reliable, frame‑accurate timestamp will remain the cornerstone of every successful production pipeline Turns out it matters..
