A drone box says 4K. Your phone app shows a crisp preview. But when you move the footage to a computer, a more basic question appears: what did the drone actually save?

There is a useful way to answer that without guessing from the sticker, a product title or how sharp the clip looks on your phone. Inspect the original video file. It takes a minute, and the result is much more specific than “4K camera”.

There is a catch, though: a video file can tell you its encoded dimensions, frame rate and codec. It cannot, by itself, prove how much real detail the sensor captured or whether an image was enlarged before encoding. This is a file check, not a laboratory camera test.

First, get the right file

If the drone records to a microSD card in the aircraft, inspect the original file from that card. If it records through a phone app, check whether that file is the only recording or a copy of the live feed. And if a clip has already been edited, exported or uploaded to social media, it may no longer have the dimensions or bitrate of the original.

Do not confuse the controller’s live preview with the aircraft’s saved recording. They can be different video streams. Start with the highest-quality original file you can legitimately obtain, and keep the original unchanged while checking it.

Option 1: check the clip in VLC

On Windows, open the video in VLC and select Tools → Codec Information. VLC’s own Windows support documentation describes this as a way to identify the codecs used by a file.

1. Open the original video, not a social-media copy.
2. Open Tools → Codec Information.
3. Look for the video stream’s resolution (width and height) and codec information, if displayed by your VLC version.
4. Record those values along with the file name and where it came from.

If VLC does not show enough detail, use a dedicated metadata tool such as MediaInfo or the command-line option below. Menu labels can vary across operating systems and VLC versions.

Option 2: read the video stream with ffprobe

For a more precise record, FFmpeg’s companion tool ffprobe can report the video stream’s coded width, height, nominal average frame rate and codec name. This command follows the official ffprobe documentation:

ffprobe -v error -select_streams v:0 -show_entries stream=codec_name,width,height,avg_frame_rate -of default=noprint_wrappers=1 "your-video.mp4"

Replace your-video.mp4 with the path to a local file you are permitted to inspect. The output will list the values for the first video stream. This command was checked for syntax using a synthetic, non-drone video file; it is not evidence about any commercial drone.

What do the numbers tell you?

File information	What it can establish	What it cannot establish
3840 × 2160	The saved video stream has a common UHD 4K pixel grid.	Whether the source captured native 4K detail.
4096 × 2160	The saved stream uses a wider 4K-class raster.	Lens sharpness or sensor quality.
1920 × 1080	The inspected file has a Full HD grid.	Whether another recording mode or original file exists.
30/1 or 30000/1001	An average frame-rate value, about 30 fps.	Whether motion looks smooth in every shot.
h264 or hevc	The coded compression format used by the stream.	How much fine detail survived compression.

Note that avg_frame_rate is metadata about the stream and may be an average, especially for variable-frame-rate files. And the word “4K” itself is used for more than one raster size. The key is to compare the exact saved-file dimensions, not rely on a headline label.

What if the file says 4K but still looks soft?

Then you’ve answered only the first question. A 3840 × 2160 file can contain real fine detail, aggressive noise reduction, strong compression, digital sharpening or imagery enlarged from a lower-resolution source. Resolution is the size of the grid, not a certification of its contents.

To evaluate actual image quality, you need more than metadata: compare original footage under controlled conditions, identify the exact model and recording mode, and examine motion, low light, exposure and stabilisation. Our separate explanation of bitrate, sensors and stabilisation looks at those questions. File metadata does not replace that assessment.

Why a retailer’s “4K” claim may still leave a gap

The distinction between a camera label and an actual saved-video specification is not just theoretical. In a 25 September 2026 review of 16 product-page descriptions, ProDrone, the retailer associated with this publication, found three pages explicitly stating 4K recorded video, nine describing 1080p or lower recorded video, and four without a sufficiently exact recorded-video resolution. These figures describe how ProDrone’s own product pages were documented; they are not independent measurements of aircraft, and they do not represent the broader drone market.

The practical lesson is simple: ask the seller which file is actually saved, by which recording mode, on which version of the aircraft. If the answer is unclear, treat it as unknown. A bigger number in the product title cannot fill the missing evidence.

A five-minute buyer’s checklist

• Find the original saved file, preferably directly from aircraft storage.
• Check width, height, frame rate and codec using a known metadata tool.
• Confirm whether the file came from the aircraft, a phone app, a video editor or a website.
• Ask whether “4K” refers to still photography, saved video or live preview.
• Remember that file dimensions alone do not prove native sensor resolution or good image quality.

None of this requires an expensive drone. It requires a specific file and a willingness to ask one unglamorous question: what, exactly, did the camera save?

Editorial note: This is an explanatory method based on the linked tool documentation, not a hands-on test of a named drone. The ProDrone listing audit is a retailer’s own documentation review and is identified as such above.