Practical
How to Read What a Video File Actually Contains
The extension tells you almost nothing. Here are the seven things worth knowing about a file, how to find each one, and what each answer means in practice.
4 min read · Published 16 August 2026
Two files both called something.mp4 can be completely different things. One might be 4K at 60 frames a second in H.265 with Opus audio, and the other 480p at 24 frames in H.264 with AAC. The extension is the same because the extension names the box, not what is in it.
Almost every video problem gets easier once you stop guessing about this. A file that will not play, a file that is unexpectedly enormous, a file that looks worse than it should: all three are usually answered by reading what the file is.
The seven things worth knowing
| Field | What it tells you |
|---|---|
| Container | Which players will open it at all |
| Video codec | Whether the picture will decode, and how efficiently it was compressed |
| Resolution | How many pixels, which is the ceiling on detail and nothing more |
| Frame rate | How motion will look, and whether it matches its destination |
| Bitrate | How much data per second, which is the real quality signal |
| Audio codec | Whether the sound will play, and whether a track exists at all |
| Duration | Whether the file is complete or was cut short in transfer |
Reading a file without installing anything
Our own video file info tool reads the file in your browser and reports what it finds. Nothing is uploaded, because the reading happens on your machine, which also means it works on files too large to be worth sending anywhere.
The other option needing no installation is VLC, if it is already on the machine. Open the file, then Tools followed by Codec Information, and it lists the streams with their codecs and resolutions.
Windows can show a little of this in file properties, under the Details tab. It is worth knowing about and worth being warned about: it reports the frame rate and resolution reasonably and is often silent about the codec, which is usually the field you needed.
What each answer actually means
Container
MP4, MOV, MKV and WebM are containers. They decide compatibility more than quality. MP4 opens essentially everywhere. MKV holds anything and is refused by plenty of televisions and older players. If a file will not open at all while other files of the same kind do open, the container is the first suspect.
Video codec
H.264 plays on everything and is the safe answer. H.265, also called HEVC, produces a smaller file for the same quality and is refused by many browsers and older machines. AV1 is smaller again and newer still, with correspondingly patchier support.
If a file gives you sound and a black or green screen, this field is where the answer is.
Resolution
This is the most over-read field on the list. It sets the maximum detail possible and guarantees none of it. A 1080p file at 1 Mbps looks considerably worse than a 720p file at 5 Mbps, because the second one has the data to actually describe its pixels.
Resolution is a ceiling. Bitrate is what fills it.
Frame rate
24 reads as film, 30 as television, 60 as smooth motion and video games. Where this matters is mismatch: 24 frames played on a 60Hz display cannot divide evenly, and the judder people describe as stuttering during slow pans comes from exactly that.
Bitrate
The most informative single number about quality, and the one least often quoted. Read it alongside the resolution, since the same figure means something different at each size.
| Resolution | Low | Reasonable | Generous |
|---|---|---|---|
| 720p | under 2 Mbps | 3 to 5 Mbps | above 6 Mbps |
| 1080p | under 4 Mbps | 6 to 10 Mbps | above 12 Mbps |
| 4K | under 15 Mbps | 25 to 40 Mbps | above 50 Mbps |
These are rough bands for ordinary material in H.264. Efficient codecs need meaningfully less for the same result, and heavy motion or fine detail needs more, so treat them as orientation rather than rules.
Audio codec, and whether there is one
AAC is the usual companion to H.264 and plays everywhere. Opus is excellent and belongs in WebM, and inside an MP4 it produces a file many players open and then play silently.
The more important reading is whether an audio stream is listed at all. No stream means the sound was never in the file, which is a different problem entirely and has a different fix.
Duration
Compare it against what the video should be. A file reporting eleven minutes of a forty minute recording was truncated in transfer, and no player setting will recover the rest.
Three problems this solves immediately
- It will not play. Read the container and both codecs. An unsupported container can be remuxed in seconds. An unsupported video codec needs re-encoding. Knowing which saves you from the expensive answer to the cheap problem.
- It is far larger than expected. Read the bitrate and the codec. An old codec at a high rate is the usual explanation, and re-encoding to something modern often halves the size with no visible change.
- It looks worse than the resolution promised. Read the bitrate. A high resolution at a low rate is a common way to make a file look impressive in a listing and disappointing on screen.
Get into the habit of reading a file before doing anything to it. It takes a few seconds and it regularly turns a long conversion into a short repackage, or shows there was never a problem with the file at all.
Common questions
Does reading a file upload it anywhere?
Not with the tool on this site. The file is read in your browser and nothing is sent to a server, which is why it works on files far too large to upload comfortably.
Why does Windows not show the codec in file properties?
The Details tab reads a limited set of fields and often leaves the codec blank, particularly for newer ones. It is fine for resolution and duration and unreliable for the field you usually want, so it is worth checking elsewhere before concluding anything.
Which field matters most for quality?
Bitrate, read together with resolution and codec. Resolution alone is the most commonly quoted and the least informative, since it sets a ceiling on detail without saying whether there is enough data to reach it.
The file has no audio stream listed. What now?
The sound was never in the file, so no player setting will produce it. That normally means the source keeps its video and audio apart and only the video arrived, which is a separate subject worth reading about on its own.