{# Als einziges Symbol OHNE fill-Attribut: Der Stern zeigt seinen Zustand ueber die Flaeche (.sts-star[aria-pressed="true"] svg { fill: currentColor }). Ein fill am symbol waere ein Praesentationsattribut und schluege die geerbte CSS-Angabe - der gemerkte Stern bliebe dann eine Kontur. #} {# Bedienungssymbole des Notizblocks. Quelle: Lucide (ISC-Lizenz), wie in der Design-Uebergabe "Alltagswerkzeuge v2". Geometrisch statt handgezeichnet: sie stehen in Leisten neben Text, nicht als Kategoriezeichen. #}
Small Things Sorted

View video information

Length, resolution, frame rate, codecs - even for files that will not open.

Stays on your device – The file is read in your browser. It is not uploaded.

Drop your files here

or

You can also paste with Ctrl+V.

What you type is processed in your browser and never sent to us.

How to do it

  1. Pick your videos

    One file or twenty - drop them in.

  2. Let it read

    For the frame rate, each file is played silently for a moment.

  3. Compare the tables

    One table per file, with everything in it.

What this is for

Twenty clips in a folder, and the question is which one is the 4K one. Or: why the file the client sent will not open anywhere.

Two of the values here are not simply readable, and both are marked accordingly:

The frame rate is revealed by no browser. It is measured by playing for a moment - which is why "estimated" stands next to it.

The codecs are not revealed either. They are read out of the file's own header. That works for the MP4 and Matroska families, so for almost everything anyone actually has - and for the rest it honestly says "not determinable" rather than guessing.

A file your browser will not play still gets a row: format, codec and size live in the file, not in the player. That usually explains why it will not open, too.

Common questions

No. Reading happens in your browser, and of large files only the header - the few hundred bytes that carry the structure.

Because there is no other way to get the frame rate: no interface states it. So it plays silently for a moment and watches when the individual frames arrive. The gap between them is the frame rate.

Because the value genuinely cannot be had. Resolution and frame rate need a player - if the browser cannot open the file, they are missing. The codecs are read from the file header, which works for MP4, MOV, MKV and WebM but not for every container. Writing a guess would be worse than the gap.

File size divided by length - how much data each second of video costs. A rough but useful figure: it tells you whether a file is encoded frugally or wastefully for its resolution. The audio is included.

Because it is stated in two places: in the file header and in what the player makes of it. On clean files the two agree; on truncated ones or ones assembled from parts they can diverge. What is shown is what the player says, provided it could open the file.

Missing a tool? Tell us which one.