aistockfree

Learn

Why 30 to 60 fps, and not 24

Most AI video generators deliver 24 frames per second. It looks fine in the editor, and then it stutters on a phone. Here is why, and how to fix it.

The 60 Hz problem

Almost every phone, laptop and monitor refreshes 60 times per second. 30 fps divides 60 perfectly: every frame stays on screen exactly twice. 24 fps does not: frames have to alternate between staying three refreshes and two refreshes (the old "3:2 pulldown"). The motion speeds up and slows down twelve times per second. On slow scenes you barely notice it. On a camera pan, a flight over a landscape or waves rolling in, it becomes a visible judder, even when the file itself is perfect.

That is why aistockfree accepts videos from 30 to 60 fps: they play smoothly on the screens people actually use.

How not to convert

Don't just change the frame rate in your editor. Exporting a 24 fps clip as 30 fps usually repeats one frame out of every four. The file says 30 fps, but the motion jumps every fifth frame, and it looks worse than the original.

Don't chain two interpolations unless you have checked the result. Each pass invents frames from frames that were already invented, and small irregularities add up into a visible pulse.

How to convert

A quirk of the newest AI models

Some recent generators produce motion that is slightly uneven from the start: frames come in pairs, or the camera imitates the bounce of someone walking or the vibration of a drone, even when you ask for a smooth glide. Interpolation softens it but cannot invent a rhythm that was never there. If a clip pulses before you touch it, try generating it again before spending time on post-production.

More: Why real 4K, in true 16:9 or 9:16 · What makes a loop truly seamless · Why there is no Content ID here, ever