
A long WAV can exceed the size that standard RIFF's 32-bit data-size field can represent. FFmpeg's WAV muxer offers RF64 for files larger than four gigabytes, but the receiving software must support it. Choose the container behavior before recording or exporting a very large audio handoff.
Key Takeaways
- The limitation concerns container size representation, not only audio duration.
- RF64 auto can switch when the output grows beyond the RIFF limit.
- Legacy compatibility must be checked on the receiving system.
Estimate the handoff size before choosing a mode
Record duration, sample rate, channel count and sample format. A multichannel high-resolution recording can reach the size boundary sooner than a shorter or simpler recording. Do not use “less than an hour” as a universal compatibility rule.
The FFmpeg WAV muxer documentation defines three rf64 modes: auto, always and never. It describes never as the default and warns that oversized plain RIFF files can have incorrect size representation, leaving some or all audio unreadable in many applications.
- Identify whether the expected output could exceed the standard RIFF size capacity.
- Ask whether the recipient's editor supports RF64.
- Choose auto when a standard RIFF start with a later RF64 switch suits the agreed compatibility.
- Use always only when an RF64 file is explicitly acceptable regardless of size.
- Export to a distinct destination and open the completed result in the receiving application.
The options belong to the WAV muxer; verify the installed FFmpeg build's help before applying them in a production command.
Compare the compatibility tradeoff
In a hypothetical long-form interview delivery, a producer has several channels of isolated microphones. The team should agree on RF64 support before generating one very large WAV, rather than discovering the recipient can read only the beginning.
Auto reserves header space using a JUNK chunk. The documentation notes that compliant RIFF readers should ignore it, while extremely simplistic readers may be confused. Auto is therefore a compatibility strategy, not a promise that every old player works.
Verify more than whether the file opens
Inspect the reported duration, channels and sample rate. Play and seek near the beginning, middle and end, including the last required words. A readable opening does not establish that the entire large file is accessible.
For channel preparation, use the separate multichannel preflight guide. Correct channel order does not remove a container size limit.
If RF64 is unsupported, agree on another delivery arrangement before conversion or segmentation. Keep the complete source intact. The cited documentation describes a recovery-related ignore_length option for an oversized RIFF file, but that is not a reason to deliberately create an invalid delivery or promise complete recovery.
Related tasks
- What to Check Before Merging Audio into a Multichannel Stream
- Why Do Delivered Dialogue, Music, and Effects Stems No Longer Line Up?
- Why Does My BWF Recording Appear Far Away from the Playhead After Import?
Sources and scope
- FFmpeg official documentation source: WAV muxer: RF64 auto, always and never modes; RIFF size-field limit and compatibility caveats.
Documentation-based guidance. All scenarios and acceptance worksheets are proposed or hypothetical; no hands-on test, search-volume measurement or AI-citation ranking is claimed.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. This is documentation-based guidance with proposed examples, not a claim of hands-on testing or an independent product review. Report a correction.
Cover: AI-generated conceptual editorial illustration; not a real application screenshot, observed output or before-and-after test.