PrivateMP3

Screen recording audio: measured times and sizes

How long does it take to get the sound out of an hour of screen recording, and how big is the result? These are measured numbers from the shipped tool, not estimates.

What was tested

Six files were made with FFmpeg 9.0.1 from its built-in test sources: a moving 30 fps test pattern for the picture and a 220 Hz tone mixed with quiet pink noise for the sound. They are not captures from any particular recorder. Each one copies a container and track layout that screen recordings commonly use, so the results describe how this tool handles those layouts, not how a given recording app behaves.

FilePictureAudio as writtenSize
A. 60 min MP4H.264, 1920x1080AAC, stereo, 48 kHz, 160 kbps4,388,816,051 bytes (4.39 GB)
B. 10 min MOVH.264, 1920x1080AAC, stereo, 48 kHz, 128 kbps728,935,720 bytes
C. 10 min MKVH.264, 1920x1080Track 1 named System audio: AAC stereo, default. Track 2 named Microphone: Opus mono736,844,134 bytes
D. 10 min WebMVP8, 1280x720Opus, stereo, 48 kHz, 96 kbps requested81,204,433 bytes
E. 1 min MP4H.264, 1920x1080None71,877,497 bytes
F. 30 s MKVH.264, 640x360AAC, 5.1 (six channels), 48 kHz7,999,438 bytes

The built site was served locally and driven in Chrome 153.0.8010.53 on Windows 11, on an Intel Core i5-13600KF with 32 GB of memory, using Playwright. Advertising and analytics requests were blocked so the test did not count as visits. Every saved file was read back with ffprobe to confirm codec, sample rate, channels and duration. Run date: 5 October 2026.

What the File check panel reported

The panel appears under the editor once a file opens. Its bitrate is measured from the track's packets, because containers rarely store one.

FilePanel summaryReady to edit after
AMP4, 1 audio track, 1 video track. AAC, stereo, 48 kHz, 160 kbps12.0 s
BQuickTime File Format, 1 audio, 1 video. AAC, stereo, 48 kHz, 128 kbps1.3 s
CMatroska, 2 audio, 1 video. 1. System audio, eng, AAC, stereo, 160 kbps, default. 2. Microphone, eng, Opus, mono, 73 kbps1.8 s
DWebM, 1 audio, 1 video. Opus, stereo, 48 kHz, 69 kbps1.8 s
ERefused at open: This file has no audio track, so there is nothing to extract.0.1 s
FMatroska, 1 audio, 1 video. AAC, 6 ch, 48 kHz, 186 kbps0.2 s

Ready means the waveform for the whole timeline was drawn. That time follows the length of the audio, not the size of the file: the 4.39 GB hour took 12 seconds, because the picture is never decoded. File D shows why the bitrate is measured. FFmpeg was asked for 96 kbps Opus, but Opus varies its rate with the signal, and the simple test sound needed only 69 kbps.

Export times and sizes

FileOutputTimeSaved sizePanel estimate
A (60 min)MP361.4 s86,400,744 bytesAbout 86 MB
AM4A, unchanged copy6.1 s72,676,105 bytesAbout 72 MB
AWAV29.4 s691,200,044 bytesAbout 691 MB
B (10 min)MP38.8 s14,400,744 bytesAbout 14 MB
BM4A, unchanged copy1.2 s9,739,957 bytesAbout 9.6 MB
BWAV5.0 s115,200,044 bytesAbout 115 MB
C (10 min, track 1)M4A, unchanged copy1.3 s12,263,586 bytesAbout 12 MB
D (10 min)MP39.6 s14,401,320 bytesAbout 14 MB
DM4A, AAC encode3.9 s14,518,706 bytesAbout 14 MB
F (30 s, 5.1)MP3, folded to stereo0.3 s721,320 bytesAbout 721 KB
FWAV, six channels kept0.3 s17,292,140 bytesAbout 17 MB

Every estimate landed within 2 percent of the saved file. On this machine MP3 ran at roughly 60 times real time, so an hour of audio took about a minute. The unchanged M4A copy was about ten times faster again, because nothing is decoded or encoded. WAV sat between the two. A phone will be slower; these are desktop figures.

What ffprobe found in the outputs

Two defects this run found and fixed

The first pass of this test failed in two places, and both failures were reaching visitors.

The unchanged M4A copy failed on every MP4 and MOV source. That priming offset gives the first packet a negative timestamp (-0.0213 s), and the MP4 writer refused it. Matroska files were unaffected, which is why it went unnoticed. The copy now shifts every packet by that offset without changing its bytes. The same failure also left the page on Converting with no error message; a failed job now reports the stage where it stopped.

A 5.1 track to MP3 stopped with a message saying the browser lacked a decoder. The decoder was fine: MP3 cannot hold six channels. All 13 conversion failures recorded between July and October 2026 happened on the MKV page, where six-channel tracks are common, so this is the likely cause; the failure count over the next two weeks will show whether it was. MP3 export now folds such a track to stereo and says so; WAV keeps every channel.

Reading these numbers for your own recording

For an hour-long lecture or meeting saved as MP4 or MOV with AAC audio, the unchanged M4A copy is the quickest and smallest: about 72 MB at 160 kbps, with no generation loss. MP3 at 192 kbps costs 86.4 MB per hour and plays almost everywhere. WAV costs 691 MB per hour for 48 kHz stereo and is only worth it when the next step is an audio editor. If the File check shows a recording with no audio track, the sound was not captured; no converter can recover it. For opening problems, the troubleshooting guide lists what each message means, and the screen recording page covers where Mac, Windows, iPhone and Android save their recordings.

Advertisement

Questions about the test

Why generated files instead of real recordings?
Generated files can be described exactly and rebuilt with the same settings, so a later run measures the tool rather than a different source. They match common container and track layouts, but a real recording may use other settings, and a speech recording compresses differently from a test tone.
Will my phone be this fast?
No. These are desktop figures. Phones decode and encode more slowly, and they stop background tabs, so keep the tab open and the screen on during a long export.
Was any file uploaded during the test?
No. The site ran from a local server and the files were read from the same disk. Advertising and analytics requests were blocked for the run.

Last updated 2026-10-05