Skip to content
AbeyIO

03 / Know your source

How to check video codec, resolution, and frame rate

An MP4 extension does not tell you how the video is encoded. Read the video track's technical details, then understand what those values can and cannot explain.

Quick answer: select a supported MP4 or MOV in the Video Information Viewer and select Inspect video. Read Video codec, Resolution, and Average frame rate. The viewer reads local metadata without uploading or decoding the video.

Read a local MP4 or MOV report

  1. Open the Video Information Viewer and select a local file up to 1 GB.
  2. Select Inspect video. The viewer reads the first video track, not every media stream.
  3. Read the codec string, pixel dimensions, duration, and average frame rate. Unknown values remain unreported.
  4. Use Copy report or Download report if you need the details for a bug report or an editing workflow. The report includes the file name; review it before sharing.

The file is not uploaded. The site can make separate requests for assets, analytics, and error reporting. See the processing and privacy limits.

Container, codec, and resolution are different

A container, such as MP4 or MOV, holds media tracks and metadata. A codec, such as H.264 or HEVC, describes how a video stream is encoded. Two MP4 files can use different codecs, profiles, and other encoding settings.

Resolution gives the video track's width and height in pixels. It does not measure sharpness, focus, or compression damage. A large pixel count alone does not establish high image quality.

Our 20-second test recording contains 600 frames. The actual AbeyIO report shows:

FieldExample valueHow to read it
Video codecavc1.64001fH.264 High profile, level 3.1
Resolution1280 × 720Track width × height in pixels
Duration20.000 secondsReported playback duration
Average frame rate30.000 fps600 video samples divided by 20 seconds
Color transferSDR or unspecifiedPQ/HLG HDR was not detected; this does not confirm SDR

Open the actual text report. A codec string is useful when describing a file that does not play, but the string alone does not prove that your browser or device can decode it.

Average FPS does not prove constant frame rate

FPS means frames per second. AbeyIO calculates an average from the video sample count and track duration. It uses the playback duration in the track header when available, with media duration as a fallback.

A constant-frame-rate video aims for uniform frame spacing. A variable-frame-rate video can have uneven spacing and still average 30 fps. The average alone cannot distinguish them. This viewer does not analyze each frame's timing to classify constant or variable frame rate.

Different tools can show slightly different values when they report a nominal rate, use a different track, or use a different duration. Some files have an edit list that changes the playback timeline. Our test recording has media duration slightly longer than its 20-second playback duration.

Do not change a file merely because one report says 29.97 and another says 30. First check what each field measures. A report is also not a conversion: inspecting a video does not change its codec, resolution, or timing.

Other ways to inspect your file

On Mac: QuickTime Player

Open the media file in QuickTime Player. Choose Window > Show Movie Inspector, or press Command-I. Apple's documentation lists information such as compression format, size, frame rate, bit depth, and HDR format. Available details depend on the file.

For a broader report: MediaInfo

MediaInfoOnline provides a browser-based media report and documents local processing without uploading the file. It is an alternative when you need information beyond AbeyIO's focused first-video-track report. Review reports before copying or sharing them; MediaInfoOnline also offers separate report-sharing features.

What the report cannot prove

  • Playback compatibility: identifying a codec does not test decoding. Container, codec profile, browser, operating system, and device can all matter.
  • File integrity: reading metadata does not check every frame for damage.
  • Complete metadata: AbeyIO does not list audio tracks, camera settings, GPS, WebM/MKV information, or YouTube-link details.
  • Successful inspection of every MP4: the parser reads bounded parts of the file, up to about 20 MiB. Unsupported structures, damaged data, or metadata outside those windows can prevent a report.

Sources checked 27 October 2026: MDN media container guide, Apple Movie Inspector instructions, and MediaInfoOnline. The sample values above come from the linked AbeyIO report.