Disclaimer
Review memory limitations, WebAssembly compilation disclaimers, and browser performance parameters.
Device RAM Limits
Browser tabs share system memory. Processing large files can trigger browser limits.
No Backup Hosting
We maintain no database copies of files. Once closed, data is deleted from tab memory.
Completely Offline
Once initial JS loads, conversions work without active network access.
1. Memory Overhead & Tab Crashes
Because M4AtoWAV.com executes all audio transcoding inside your browser sandbox, it requires reading and caching data chunks in device memory (RAM). Most modern web browsers limit the memory footprint of a single tab to between 1.5 GB and 4 GB.
For files exceeding 500 MB, the uncompressed WAV audio output can reach several hundred megabytes. This size, combined with the compiler's cache requirements, can exceed browser thresholds, causing the browser tab to crash or exit. We recommend limiting input sizes to 500 MB.
2. Liability Disclaimers
We do not accept liability for:
- Any loss or corruption of your audio files.
- Conversion failures or incomplete audio tracks.
- Incorrect sample rate mappings or downmixing.
- Loss of album artwork, artist tags, or lyrics metadata (WAV format has limited tag support compared to M4A/MP4 containers).
3. DRM (Digital Rights Management)
Our WebAssembly engine cannot transcode M4A files that are encrypted or protected by DRM systems (such as older Apple FairPlay protected tracks bought on iTunes). Attempting to convert a protected track will return a compilation error.
4. Accuracy of Size Estimates
The WAV output size displayed prior to conversion is an mathematical estimate based on the file duration, target sample rate, target channels, and target bit depth. The actual compiled file size may differ slightly due to header data structures or alignment paddings.