Extract frames from MP4

The short answer

To extract frames from an MP4, check whether your browser decodes its video codec and choose the image format for export. An MP4 file extension alone does not establish whether its encoded video will decode here. Open the local frame extractor to check your file and choose an output format.

Codec: an MP4 extension does not identify the encoded video

MP4 is the file container used by the test samples; H.264 and HEVC identify different video encodings inside those files. In the recorded test on this machine, the H.264 sample loaded and could be processed, while the HEVC sample was refused by this Chrome session. Treat those as observations about these files on this setup. They do not establish a general MP4, H.264, or HEVC compatibility rule.

The retained earlier HEVC record contains three rows. For each row, requested images were “Not set,” images shown were zero, and the run status was “Not run.” In the 2026-10-23 rerun on this Tencent Cloud CVM (Windows 11 Pro; Chrome 155.0.8059.40), the page displayed Your browser cannot decode the codec in this file. Try an H.264 MP4 or VP8/VP9 WebM. during loading, before a capture mode could be set. This is the result for this file on this machine and browser session; it does not establish a general codec compatibility rule.

Output format: paired local run

The PNG and JPG captures below used the same selected Big Buck Bunny H.264 file, Every original frame mode, and the same Chrome session. I reran the capture changing the output format. The JPG setting remained at its default quality of 95. In each run the browser memory protection stopped extraction. For JPG, 316 is the number already displayed when memory protection triggered; it is not an upper limit.

In this paired test, the JPG run had more images visible before browser memory protection stopped it. The test does not show a completed export for either format. It also does not show the encoded-image byte total, so no ZIP size or compression ratio can be reported. The counts should not be used to predict another file, browser, quality setting, or device.

What this test can and cannot guide

For a comparable local check, keep the selected file and capture mode the same, change only the output format, and record the point where the browser stops the run. If you need a complete sequence, this partial test cannot tell you how many images will finish on your device. Shorter ranges are a cautious next attempt, but their results were not measured in this comparison. The extractor displays completed images and a memory-protection message when a run stops early.

The test was performed on one Tencent Cloud CVM plan with 2 vCPU and 4 GB memory. Windows 11 Pro reported 2 logical processors and 3.94 GB RAM. The recorded Chrome version was 155.0.8059.40; Windows reported an AMD EPYC 9754 CPU. The H.264 sample was a 10-second, 1080p Big Buck Bunny encode from Test-Videos. These setup details identify the scope of the observation; they are not a device recommendation or benchmark for other systems.

This page is about the tested MP4 codec and output-format behavior. For the separate question of how many timestamps a sampling plan requests versus how many images a run actually displays, read the image-count guide.

PNG output was repeated in this browser session and displayed the same partial count as the earlier recorded PNG row. The JPG row was rerun in the same session and its screenshot is retained with the operations evidence. The earlier HEVC outcome is copied from the companion test table; this rerun’s original browser wording is recorded in the codec section above. No export-byte measurement or full-run comparison is available for this page.

Try the local MP4 frame extractor

This is a single-machine observation, not a compatibility matrix. For sample-count arithmetic, boundaries, and the difference between requested timestamps and displayed results, use the image-count guide.