FPS to MS Chart for Screen Recording

Quick answer

24fps is 41.67 ms per frame, 25fps is 40 ms, 30fps is 33.33 ms, and 60fps is 16.67 ms. For any other rate, divide 1000 by the FPS value or use the free FPS to MS calculator.

FPS to milliseconds chart

Values are rounded to two decimal places. For the NTSC-style labels 23.976, 29.97, and 59.94, this table divides by the displayed decimal. Use the exact rate from your source or project for longer timing calculations; these labels are not an exact timecode specification. This chart calculates timing, not measured capture performance or input latency.

Why milliseconds per frame matters

At a constant 30fps, the nominal interval is about 33.33 ms. Use that interval to plan a frame-aligned caption, cursor highlight, or cut. It does not diagnose a late effect or dropped frame: inspect the actual recording and timeline before deciding what caused the delay.

30fps is usually enough for screen recordings

Most tutorials, SaaS demos, support replies, and onboarding clips contain deliberate cursor movement and static interface states. Start at 30fps and inspect a short export at its final viewing size. Use 60fps when rapid animation, game footage, or cursor movement needs extra smoothness. File size depends primarily on average bitrate and duration, not frame rate alone.

Resampling and conforming are different operations

In this calculator, conformed length means keeping the same frames and playing them at another rate. A 60fps clip played at 30fps takes twice as long. Resampling can instead preserve the original duration by selecting, blending, or generating output frames. For an evenly spaced 60fps source, selecting every other frame produces a 30fps result at normal speed. Editors use different names for these operations; check whether a command preserves duration.

Use frame math before exporting MP4 or GIF

Use the calculator to plan a pause or compare playback durations before editing. It does not inspect, upload, or convert a video file, and its results do not prove that a recording contains every expected frame. Review the finished clip at its delivery size and check the timing in the editor.

Worked examples for a screen-recording edit

To turn a frame count into milliseconds, multiply the number of frames by 1000 and divide by FPS. A six-frame pause lasts 200 ms at 30fps and 100 ms at 60fps. That gives you a concrete duration when you hold on a menu before a cursor click or leave a caption visible after a zoom.

To go the other direction, multiply milliseconds by FPS and divide by 1000. A 250 ms hold at 30fps is 7.5 frames, so a frame-aligned cut must land at seven frames (233.33 ms) or eight frames (266.67 ms). Use the actual project frame rate and keep full precision until you choose the final frame boundary.

Try it: ten seconds at 60fps, played at 30fps

You can reproduce this example in ScreenBuddy’s browser calculator without a recording, account, or download.

1. Open the FPS to MS calculator and find Clip length and conforming.
2. Choose 60 under From frame rate, 30 under To frame rate, and enter 10 for Clip length (seconds).
3. Read Source frames @ 60fps: 600 and Conformed length: 20.00 s. The calculation is 10 × 60 ÷ 30 = 20 seconds.
4. Change the target to 24: the same 600 frames now take 25.00 s. Switch back to 30 to reproduce the screenshot.

For a normal-speed tutorial, preserve duration when changing the output rate. Use unchanged-frame playback only when you intend to change speed. Adobe’s frame-rate interpretation guide documents reinterpreting footage; Apple’s frame-sampling guide explains matching footage to a project rate. These describe those editors, not additional features of this calculator.

Next, check text and cursor readability with the screen recording quality guide, or plan a short silent loop with the GIF workflow for a GitHub README.

Frequently asked questions

Calculate the exact frame timing

Use the interactive calculator for custom FPS values, clip length, source frame count, and conformed playback duration.