24fps film to 60i video: four frames stretch across five video fields in 2-3-2-3-2 pattern. NTSC standard, cleaner than 2:2—but inverse telecine needed for clean recovery.
Anyone who needs to convert 24p film footage to NTSC video (60i) cannot avoid 3:2 pulldown — and those who don't understand it will get ghosting, artifacts, and headaches in editing. The process stretches four film frames into five video fields by repeating a specific pattern: two fields for frame 1, three fields for frame 2, two for frame 3, three for frame 4. Then it starts over. This creates the 3:2 ratio — the name says it all.
The practical necessity: Film runs at 24 fps, NTSC video at 29.97 fps (effectively 30 fps). To adjust the speed without simply duplicating or skipping frames, this asymmetrical method was developed. Unlike the older 2:2 pulldown (two fields per frame, evenly), the temporal load is distributed more unevenly — but more smoothly. Theoretically. In practice, you still see judder with fast camera movements or text crawls if the technique isn't implemented cleanly.
On set or in post-production, 3:2 becomes relevant primarily when you convert film footage directly to video output — for example, for television broadcast in NTSC regions (USA, Japan, South America). Modern cameras and DCP players handle this internally; it becomes critical when you're juggling raw media or using legacy hardware. The biggest pitfall: Once pulldown has been applied and you want to convert the material back to 24p later, you need Inverse Telecine — a separate process that decodes the pulldown information and reconstructs the original four frames. Without Inverse Telecine, you end up with noisy, interpolated material.
In VFX workflows, 3:2 is less critical today than it was in the 2000s, as DCI and streaming now prefer native 24p. Nevertheless, anyone working with older archive material, television broadcasts, or international versions for NTSC must know about pulldown — and document whether it has been applied. A common mistake: editing material with pulldown as if it were native 24p, and then wondering about temporal inconsistencies when re-timing.