Frames To Ms Calculator

Enter the number of frames and frames per second into the calculator to determine the time in milliseconds. This calculator can also evaluate any of the variables given the others are known.

Frames to Milliseconds Formula

MS = (F / FPS) * 1000

Where MS is the time in milliseconds, F is the number of frames, and FPS is the frame rate in frames per second. To reverse the conversion (milliseconds to frames), use F = (MS / 1000) * FPS.

Frame Time Reference for All Standard Frame Rates

Every frame rate has a fixed time interval per frame. The table below covers every standard frame rate used across cinema, broadcast television, gaming, and high-speed capture, along with where each rate is primarily used.

Why Frame Rates Are Not Round Numbers

Rates like 23.976 and 29.97 fps exist because of the transition from black-and-white to color television in the 1950s. The original NTSC broadcast standard used exactly 30 fps, locked to the 60 Hz power grid in North America. When color information was added to the signal, engineers needed to avoid interference between the color subcarrier frequency and the audio carrier. The solution was to slow the frame rate by a factor of 1000/1001, turning 30 fps into 29.97 fps and 24 fps into 23.976 fps. This 0.1% difference means that 29.97 fps content runs about 3.6 seconds slower per hour compared to true 30 fps, a difference that matters when syncing timecode to wall-clock time.

PAL regions (Europe, most of Asia, Africa, and Australia) adopted 25 fps, locked directly to their 50 Hz power grid. Because 25 divides evenly into whole seconds, PAL never needed a drop-frame timecode workaround.

Drop Frame vs. Non-Drop Frame Timecode

At 29.97 fps, counting every frame sequentially causes the timecode to drift from real time by about 3.6 seconds per hour. Drop-frame timecode compensates by skipping frame numbers 00 and 01 at the start of every minute, except every tenth minute. No actual video frames are dropped; only the counter labels change. This keeps the timecode aligned with clock time to within a few frames over 24 hours. Non-drop timecode counts every frame number in order and is simpler for editing, but the displayed time will not match wall-clock duration. Drop-frame timecodes are written with semicolons (01:00:00;00) while non-drop uses colons (01:00:00:00).

Frame Time in Gaming and Input Lag

In competitive gaming, frame time directly affects perceived responsiveness. A game running at 60 fps delivers a new image every 16.67 ms, while 144 fps reduces that interval to 6.94 ms and 240 fps to 4.17 ms. The total delay between a player pressing a button and seeing the result on screen (input lag) is the sum of several components: the game engine processing time (typically 1 to 3 frames), the GPU render time for that frame, the display’s signal processing delay (5 to 15 ms on most gaming monitors), and the panel’s pixel response time (1 to 5 ms gray-to-gray). At 60 fps, a single frame of engine delay adds 16.67 ms. At 240 fps, that same one-frame delay adds only 4.17 ms.

For context, the average human visual reaction time to a stimulus is roughly 150 to 250 ms. Professional esports players in titles like Counter-Strike and Valorant often react within 150 to 180 ms. At 60 fps, that reaction window spans about 9 to 11 frames. At 240 fps, the same window spans 36 to 43 frames, giving the rendering pipeline more opportunities to display updated game state before the player acts.

Frames to Milliseconds in Video Editing and Subtitles

Video editors working in NLEs like Premiere Pro, DaVinci Resolve, or Avid Media Composer set their timeline to a specific frame rate. Every cut, transition, and keyframe snaps to frame boundaries. When exporting subtitle files in SRT or ASS format, timing is specified in milliseconds or centiseconds, not frames. Converting accurately matters because a subtitle that appears even 2 frames early or late (66 ms at 30 fps) is noticeable to viewers, especially during fast dialogue.

Audio synchronization follows the same principle. Audio editing tools measure time in samples (at 48,000 Hz, each sample is 0.0208 ms) or milliseconds, while video timelines count frames. A/V sync drifts as small as 40 to 50 ms become perceptible to most viewers, meaning even a single-frame offset at 24 fps (41.67 ms) is right at the threshold of detection.

Animation Timing and Frame Duration

Traditional hand-drawn animation is produced at 24 fps but not every frame is a unique drawing. Animating “on ones” means a new drawing every frame (41.67 ms per drawing). Animating “on twos” holds each drawing for 2 frames (83.33 ms per drawing), and “on threes” holds for 3 frames (125 ms). Most theatrical animation mixes these approaches: fast action scenes use ones for smooth motion, while slower scenes use twos to reduce workload without a visible quality loss. Modern digital animation in tools like Toon Boom Harmony, Adobe Animate, or Blender’s Grease Pencil still follows this convention.

In 3D animation and motion graphics rendered at 30 or 60 fps, frame duration directly controls the speed of easing curves. A 10-frame ease-in at 30 fps lasts 333 ms, producing a noticeably different feel than the same 10-frame ease-in at 60 fps (167 ms), which appears snappier. Animators converting projects between frame rates must scale their keyframe timing by the ratio of the new rate to the old rate to preserve the intended pacing.

VR and Motion Sickness Thresholds

Virtual reality headsets have strict frame time requirements because the display must update in sync with head movement. If a frame arrives late, the mismatch between visual and vestibular input causes motion sickness. Meta Quest headsets target 90 fps (11.11 ms per frame) as a minimum, with 120 fps (8.33 ms) preferred. PlayStation VR2 runs at 90 or 120 fps. The total motion-to-photon latency (from head movement to updated pixels) must stay below roughly 20 ms to avoid discomfort, meaning the entire pipeline from sensor reading to rendered frame to display scanout has a very tight time budget measured in single-digit milliseconds.

Example Calculation

A video editor needs to place a subtitle 120 frames into a 29.97 fps timeline. The calculation: MS = (120 / 29.97) x 1000 = 4,004.0 ms, or about 4.004 seconds. In an SRT subtitle file, this would be written as 00:00:04,004. If the same project were re-conformed to 25 fps for PAL broadcast, those 120 frames would land at (120 / 25) x 1000 = 4,800.0 ms, or 4.800 seconds, shifting the subtitle nearly 800 ms later in the timeline.

• All Unit Converters
• Render Time Calculator
• Video File Size Calculator
• Audio Delay Calculator