Webcam A/V Sync & Latency Meter: Conversions

Convert ms to frames

How to convert ms to frames

Convert ms to frames using the formula below.

Common ms to frames conversions

Why frames matter for A/V sync

A/V sync is measured in milliseconds in software but perceived in frames by viewers. One frame at 30fps lasts 33.33 ms.¹ The smallest unit of visual change a viewer sees is the frame boundary, so an audio offset smaller than one frame (under 33 ms) arrives within the same frame as the visual event, which most viewers cannot consciously detect. An offset of two frames (66 ms) is at the perceptible boundary for most people under passive viewing conditions, and three frames (100 ms) is clearly detectable by most viewers.

Converting your measured millisecond offset to frames at 30fps tells you how many video frames separate the audio event from the visual event, a more intuitive quantity for video editors and streaming technicians comparing sync quality. A frame count maps directly to what an editor sees on a timeline, so describing the gap in frames rather than milliseconds makes the severity immediately visible in a way that does not require mental unit conversion.

Each complete frame of desync at 30fps represents 33.33 ms of offset in the recording or stream. Human observers detect audio-leading-video misalignment at approximately 45 ms in controlled perceptual research, just over 1.35 frames at 30fps.² An offset that produces 2 or fewer frames of desync is in the edge-of-perceptible range for passive viewers. Three or more frames pushes the offset to clearly detectable. Knowing where your measured result falls in this perceptual range helps you prioritize whether the sync correction is urgent or whether a rough approximation from the first session is close enough for your audience.

When you need to explain A/V sync quality to a collaborator who does not think in milliseconds, the frame count from this converter provides a common reference point. A video editor working in Premiere Pro or DaVinci Resolve aligns cuts on frame boundaries; describing your sync gap in frames immediately maps to the same unit of measure they use every day. Saying the stream has 2.16 frames of desync at 30fps is cleaner than saying it has 72 ms, because the editor can look at the timeline and picture exactly what 2.16 frames looks like without unit conversion.

Using frame count in editor notes

Frame counts are useful when you label test clips, write troubleshooting notes, or ask a collaborator to inspect a timeline. The correction still belongs in milliseconds, but the frame count gives editors a visual unit they can verify without recalculating every time. Adding the frame count alongside the raw millisecond value in your project notes means anyone reviewing the clip later can immediately grasp the severity without opening a calculator.

Using this converter with your OBS sync measurement

After running the 5-clap test on the Webcam A/V Sync & Latency Meter page, convert your millisecond offset to frames using this calculator. An offset of +72 ms at 30fps equals 2.16 frames, just over two full frames of desync. The decimal portion (0.16 frame) represents 5.3 ms of sub-frame offset.

In OBS, the Sync Offset field applies the correction in milliseconds, not frames. Enter the original millisecond value in OBS for the correction. Use the frame count here to understand the magnitude of the desync in terms a video editor immediately recognizes. Furthermore, frame count is useful when reporting sync issues to a manufacturer or support team; 2.2 frames of desync at 30fps is more specific than approximately 72 ms.

Frame count as a communication tool

Expressing your A/V sync measurement in frames rather than milliseconds removes an extra conversion step for collaborators who work in video timelines. A 2.1-frame offset at 30fps is immediately visualizable in a Premiere or Resolve timeline; a 70 ms offset requires calculation. When reporting sync issues to a camera manufacturer's support team, citing both the frame count and the raw millisecond value (for example, 2.1 frames at 30fps, measured at 70 ms with the five-clap browser test) gives their engineers both the perceptual context and the technical data they need to investigate the pipeline contribution for your specific camera model.

The OBS Sync Offset correction applies in milliseconds, not frames.³ Enter the raw millisecond value from the five-clap test in OBS Advanced Audio Properties rather than converting to frames first. The frame count from this converter is for reference and communication; the correction mechanism in OBS accepts only a millisecond integer.

Keeping the OBS correction in milliseconds

If your correction reduces the residual desync to 0.3 frames (about 10 ms), that residual falls well below the typical perception threshold and requires no further adjustment. Most five-clap measurements corrected with the exact OBS offset land in the 0.1 to 0.4 frame residual range after a single careful calibration. The frame count from this converter serves as a communication and documentation tool, while the actual OBS Sync Offset field always accepts the raw millisecond value as an integer without any frame-rate conversion.

Try in the tool

Convert ms to frames

How to convert ms to frames

Convert ms to frames using the formula below.

Common ms to frames conversions

A/V sync in frames at 60fps

At 60fps, one frame lasts 16.67 ms, exactly half a 30fps frame.¹ Streamers and content creators who target 60fps output face a tighter frame budget for A/V sync. An offset of 33 ms, which equals one frame at 30fps, equals two frames at 60fps. The same physical desync looks "worse" in frame count at higher frame rates, even though the millisecond value is identical.

Cameras like the Elgato Facecam and Logitech C922 Pro Stream deliver 60fps in certain modes. Measuring the A/V offset in milliseconds remains the correct approach regardless of frame rate; the offset is a time difference, not a frame count. Converting to frames helps communicate the severity to an audience that thinks in frames rather than milliseconds.

Why the same millisecond offset has a higher frame count at 60fps

Switching a stream or recording to 60fps output does not change the A/V offset in milliseconds. The webcam-to-microphone pipeline delay stays the same regardless of what frame rate OBS encodes at. However, because each 60fps frame lasts only 16.7 ms, a +72 ms offset that was 2.16 frames at 30fps becomes 4.32 frames at 60fps. If you previously accepted 2 frames of desync at 30fps as tolerable, the same hardware on 60fps output shows 4 frames, which most viewers perceive as clearly wrong. This relationship is the strongest argument for measuring and correcting the offset before switching to a 60fps production.

The perception threshold for audio leading video stays at approximately 45 ms regardless of frame rate, because human temporal perception is time-based rather than frame-based.² Your A/V sync correction goal should always be to get the millisecond offset below 45 ms after correction, whatever the output frame rate. At 60fps, 45 ms equals 2.7 frames of residual desync; achievable if you measure accurately and apply the OBS Sync Offset precisely. A 1-frame residual at 60fps (16.7 ms) places you well inside the imperceptible-sync zone and gives high-frame-rate viewers the clean output they expect from a quality stream.

Why 60fps streaming shifts the sync perception threshold

Human A/V sync perception thresholds are based on absolute time (approximately 45 ms for audio leading video), not on frame count. Consequently, a +45 ms offset that is barely at the perceptible threshold at 30fps (1.35 frames) is 2.7 frames at 60fps, but equally imperceptible in both cases because the absolute millisecond value is the same.

For 60fps productions, the practical benefit of the converter is communicating sync quality to collaborators and editors who work in timeline frame counts. Furthermore, high-frame-rate gaming streams where the camera matches the game capture at 60fps require accurate sync correction at the frame boundary, and knowing your 1.2-frame residual error helps assess whether a ±1 frame adjustment in OBS is worth the additional effort.

Gaming streams that simultaneously capture the camera and the game at 60fps expose two sources of A/V offset: the webcam-to-mic offset you measure with this tool, and any game-audio-to-game-video offset from the game capture card if you use one. Measure each offset separately; enter each correction in OBS under the appropriate audio source.³ A game stream with both offsets corrected delivers clean sync across both the game capture and the face cam without viewers needing to distinguish between the two sources.

Separating webcam and game capture offsets

For viewers who consume your 60fps content on a device that downscales to 30fps, the effective frame count for your sync gap halves automatically. A 4.3-frame offset at 60fps displays as a 2.15-frame offset on a 30fps playback device, which lands in the edge-of-perceptible range rather than the clearly wrong range. Correcting the offset before going live ensures clean sync at every playback frame rate, giving your entire audience a good experience regardless of their device limitations.

Communicating 60fps sync in editor timelines

A 60fps timeline makes fractional frames easier to discuss because each frame is only 16.7 ms. If a collaborator asks whether a 40 ms offset matters, the converter shows 2.4 frames at 60fps, which is more concrete than a raw number. You still enter the 40 ms value in OBS, while the frame count helps describe the visual severity in timeline language.

Try in the tool