Add your M4R file
Drop one or more .m4r files onto the converter above, or browse for them. They load into browser memory only — nothing is uploaded, so there is no size-based pricing and no server queue.
Re-encoding .m4r audio as .wav changes how the sound is compressed and which players will accept it. Free, private, and validated — the file never leaves your browser.
Batch files can each use a different output. Nothing uploads for local conversions.
Working inputs include camera RAW, browser-local audio/video, PDF, CBZ/CBR comics, office documents, ebooks, markup, 3D models, structured text, images, and archives.Re-encoding .m4r audio as .wav changes how the sound is compressed and which players will accept it. An .m4r file is an iPhone ringtone: AAC audio in an MPEG-4 container, identical to an .m4a in everything but the extension. Apple uses .m4r purely as a routing marker so iTunes and iOS file the audio under Tones instead of Music.
A .wav file is Microsoft's Waveform Audio format, which in practice almost always stores uncompressed PCM samples. Because every bit of the original signal is preserved and no decoding is required, .wav remains the default working format in recording studios and audio editors. For this route the practical draw is bit-perfect with zero generation loss and negligible CPU cost to read or write — balanced against enormous compared with FLAC, which halves the size losslessly, which is worth knowing before you commit a large batch.
The practical trigger for this conversion is usually a mismatch: with .m4r, tones over 40 seconds are rejected outright. Switching to .wav buys you bit-perfect with zero generation loss, which is why it is the better fit for capturing and mixing sessions in a DAW. Because the conversion runs locally, trying it costs nothing but a few seconds of compute on your own machine.
| Aspect | Apple ringtone (.m4r) | WAV audio (.wav) |
|---|---|---|
| Format type | Lossy — discards detail it judges invisible to shrink files | Lossless — every pixel or sample is preserved exactly |
| How it stores data | shares the ISO base media layout of .m4a, carrying AAC-LC audio | a RIFF chunk container whose fmt chunk usually declares linear PCM, though compressed codecs are technically permitted |
| Strongest at | turning a favorite song's hook into a custom iPhone ringtone | capturing and mixing sessions in a DAW |
| Weak spot | tones over 40 seconds are rejected outright | enormous compared with FLAC, which halves the size losslessly |
| Metadata | standard iTunes atoms apply, though iOS shows only the title in the ringtone picker | rIFF INFO chunks hold basic tags, while the Broadcast Wave bext chunk and iXML add description, originator, and timecode for production workflows; some tools also embed ID3 chunks |
Drop one or more .m4r files onto the converter above, or browse for them. They load into browser memory only — nothing is uploaded, so there is no size-based pricing and no server queue.
Select .wav in the output menu next to each file. The menu only offers targets this engine can genuinely produce, so if WAV is selectable, the route is real and validated.
Press Convert. The transcode runs on an FFmpeg engine compiled to WebAssembly, so the audio never leaves your device.
Each result is signature-checked before the download unlocks, so a failed encode can never masquerade as a valid WAV file. Outputs keep the original filename with the .wav extension.
No new loss is introduced — since m4r is lossy-oriented and wav is lossless-oriented, everything the .m4r file still contains is carried over exactly. What was already discarded by the original lossy encode cannot be recovered, though; converting to .wav does not "restore" quality.
Yes — the .m4r file is processed inside your browser tab and never uploaded. The transcode runs on an FFmpeg engine compiled to WebAssembly, so the audio never leaves your device. Close the tab and the file is gone from memory.
Windows, macOS, Linux, iOS, Android, and all major browsers play .wav natively. Recordings that exceed 4 GB require the RF64 variant, which some consumer software fails to recognize.
Larger, sometimes much larger. A lossless .wav must store every pixel or sample the decoder produced, without the perceptual shortcuts .m4r used. Use this route for editing headroom, not for saving space.
This converter strips container metadata deliberately (the FFmpeg command runs with metadata mapping disabled) so exported files do not leak recording details. In the source, standard iTunes atoms apply, though iOS shows only the title in the ringtone picker; none of it is transmitted anywhere because the file never leaves your browser.
Yes — the reverse route exists as a separate tool. Bear in mind that round-tripping .m4r → .wav → .m4r is not a perfect undo when any lossy step is involved; keep your original if fidelity matters.