Check the frame’s dimensions and shape alongside its timing.
Video FPS Checker
Use this Video FPS Checker to read your file’s average frame rate, frame count and duration. Check decimal rates before editing or sharing. Your video stays on your device.
Files stay on your device · Free to use · No account needed
How to use the Video FPS Checker
Choose the video you want to check
Select one MP4, MOV, WebM or MKV file, up to 2 GB. Choose the original recording or the exported file you plan to use. The checker reads the file on your device.
Read the average FPS
Wait for the file analysis to finish, then read the average frame rate alongside the frame count and duration. Keep the decimal part when comparing results: 29.97 and 30 are different rates.
Copy the report or check another file
Copy the results for your editing notes. To compare an export with its source, save the first report before choosing the second file. Checking a video leaves the original unchanged.
Read the result before changing your timeline
A Video FPS Checker answers a practical question: how many video frames are represented per second in this file? That is useful when a camera setting says 30, an editor says 29.97, and the downloaded copy has a different name. The file itself gives you a better starting point than its filename.
The main result is average FPS for the primary video track. The checker reads the track’s frame timing and count, rather than measuring how quickly your screen can play it. A busy computer or a high-refresh-rate monitor does not redefine the recording’s frame rate.
Frame count gives the rate context
A constant-rate, ten-second clip at 30 FPS would normally contain 300 frames. The displayed count comes from the selected video track; it is not a count of visually distinct photographs. Repeated pictures can still occupy separate frames.
Video duration belongs to the video track
A file can contain audio that begins earlier or ends later than its pictures. The timing used for the FPS result belongs to the video track, so another player’s overall duration may differ slightly.
29.97 is a setting worth keeping
Decimal frame rates are normal. A result of about 29.97 FPS does not, by itself, mean that a 30 FPS recording has lost frames. Some common recording rates use a fraction that an app displays as a rounded decimal. Match the source setting deliberately when you create an editing sequence or export preset.
| Displayed FPS | Common exact rate | Compare carefully with |
|---|---|---|
| 23.976 | 24000 ÷ 1001 | 24 FPS |
| 29.97 | 30000 ÷ 1001 | 30 FPS |
| 59.94 | 60000 ÷ 1001 | 60 FPS |
| 24, 25, 30, 50 or 60 | Whole-number rates | The source and export settings |
These are reference values, not an automatic diagnosis of your recording. An average near a familiar rate can also come from uneven frame timing. Use the result together with the source settings when exact delivery specifications matter.
What the Video FPS Checker can tell you about timing
Average FPS describes the recording as a whole. Constant frame rate describes regular spacing between frames; variable frame rate allows those intervals to change. Two videos can have the same average while distributing their frames differently. A single number cannot show every pause or timing change.
This checker reads frame timestamps across the primary video track. Constant means frame spacing stays within a tolerance for timestamp rounding; Variable means repeated differences exceed that tolerance. Unknown covers short clips, isolated timing gaps, duplicate timestamps, coarse timestamp precision or files beyond the timing analysis limit. Average FPS alone does not determine this label.
Minimum and maximum FPS describe non-overlapping windows of at least one second; a final window of at least half a second is included. At least two windows are needed. This smooths individual frame intervals and is not a per-frame instantaneous range. Unknown timing has no range. If an editor requires constant frame rate, deliberately export a constant-rate copy and review its timing and playback.
The same limit applies to missing or repeated pictures. A file may contain 60 frames per second while repeating some images from a lower-rate source. Counting frames cannot establish how many distinct moments the camera captured, or whether an editing tool generated extra pictures.
Check dimensions as well as frame timing · Plan the file size of your next export
Three moments when checking FPS helps
Before combining recordings
Check a phone clip, a camera recording and a screen capture separately before placing them in one project. Keep their reports with your notes. You can then choose the timeline deliberately instead of assuming every source matches the first clip.
When an export looks different
Run the Video FPS Checker on the source and the exported file. If the average changed from about 60 to 30, look at the export settings. If the rate stayed the same, investigate playback performance, motion blur or repeated frames separately.
Before handing a file to someone else
Share the copied result with an editor or collaborator who needs to know what arrived. It helps separate a file’s measured properties from a requested delivery setting. Keep the original source available in case a different export is needed.
Check the finished file, too
Opening a file here does not convert it. Any change to frame rate must happen in your editing or processing tool. After that work is complete, check the downloaded result rather than relying only on the settings you selected.
For uploads, start with the destination’s current requirements. YouTube recommends encoding and uploading at the same frame rate used for recording. Its guidance is linked below; that recommendation is not a universal rule for every editing project.
If you use RemoveText.video for cleanup, keep both the source report and the finished-file report. Review the pictures and sound as well. Matching FPS values alone cannot confirm that an edit preserved every visual detail or kept audio in sync.
YouTube’s recommended upload settings · How video processing works on RemoveText.video
If a file cannot be read
Confirm that the file has finished downloading and is no larger than 2 GB. MP4, MOV, WebM and MKV are accepted containers, but a familiar extension does not guarantee that every file structure can be analyzed. Renaming an unsupported file does not convert it.
A file with no readable video track cannot produce an FPS result. Try the original recording or a fresh export if the copy is damaged. You can choose another file after an error; there is no processing charge and the checker does not alter the rejected file.
Video FPS Checker questions
01Is the Video FPS Checker free?
Yes. You can inspect supported files without an account or credits. Choose one video at a time, up to 2 GB. The tool returns information about the file, so there is no newly encoded video or watermark to download.
02Does my video get uploaded?
No. This checker reads the selected video locally in your browser. The file is not sent to RemoveText.video for analysis. Copy any result you want to keep before closing the page or replacing the selected file.
03Can it tell whether my video is constant or variable frame rate?
Yes, when readable timestamps provide enough evidence. It checks frame spacing across the primary video track, allows for timestamp rounding, and reports Constant or Variable. Short clips, coarse clocks, duplicate timestamps, isolated gaps and files beyond the timing analysis limit remain Unknown. This describes the file's readable timing rather than guaranteeing compatibility with every editor.
04Does 60 FPS always mean better video?
No. Frame rate describes timing, while resolution, compression, exposure and the source recording affect the picture in other ways. A higher number alone does not prove sharper images, smoother captured motion or a better export.
05Can the Video FPS Checker change 30 FPS to 60 FPS?
No. It reads information and leaves your video unchanged. Use an editor for conversion, then inspect the new file. A 60 FPS output can contain duplicated or generated frames; the number alone cannot tell you how those frames were made.
06Why does another app show a slightly different number?
Apps can round differently or display a declared rate instead of a measured average. They may also select different video tracks. Compare the same file and track, retain the decimal values, and distinguish the video duration from the entire file’s duration.
Know your frame rate before the next edit
Open your source in the Video FPS Checker, keep the result, then compare the finished export. A quick check gives you a clear starting point for the next step.