M4R is an M4A renamed for iPhone ringtones, which is why length limits apply rather than quality ones.
Common Uses
iPhone ringtones
Custom alerts
Notification sounds
M4R Conversion FAQ
Is M4R lossy or lossless?
+
M4R is lossy — the encoder removes data the encoder judges to be inaudible to reach a small file size. M4R drops straight into the iOS Sounds list via Finder or iTunes with no further processing.
How much quality has already been lost in an M4R file?
+
Whatever the original encoder decided to discard, and it cannot be recovered. M4R compresses by modelling what the ear will not notice — quiet sounds sitting under loud ones, frequencies at the edges of hearing — and permanently removing it. At a healthy bitrate that is inaudible to almost everyone. What it is not is reversible, so converting to a lossless format preserves the current state rather than restoring the original. The payload is AAC, conventionally capped at 40 seconds, which is the longest tone iOS will accept.
Why does an iPhone ringtone have to be M4R?
+
Because iOS looks for that specific container in the tones folder and ignores anything else, however identical the audio inside might be. An M4R is ordinary AAC audio with a different extension and a duration under about forty seconds. Convert the track, trim it to the part you actually want, and copy it across through Finder or the Apple Devices app. M4R is an iPhone ringtone — an ordinary AAC file in an MP4 container with the extension changed so iTunes files it as a tone.
Why will an M4R file not play in my browser?
+
Browsers decode a short, fixed list of audio formats and M4R is outside it, so the file downloads instead of playing or the player simply reports an error. Desktop software with a wider codec set opens it without trouble. If the audio has to play on a web page, converting it is the fix — no player configuration will add a decoder the browser does not ship. M4R is Apple-only and length-limited; anything over 40 seconds is silently rejected by the phone.
Do I need a Mac to work with M4R files?
+
No. The format came out of Apple and is what its devices and software produce by default, but the files themselves are ordinary and read fine elsewhere with the right tool. Converting here happens on the server, so no QuickTime install, no Apple hardware and no platform-specific codec pack is involved anywhere in the process.
What bitrate should I convert my M4R files to?
+
Match the destination, not the source. For music, 256 to 320 kbps is transparent to nearly every listener; for speech and podcasts, 96 to 128 kbps is plenty and halves the file again. Encoding above the source bitrate is wasted space — it faithfully preserves audio that has already been through a lossy pass and recovers nothing the first encoder discarded.
Does using M4R require a patent licence?
+
Not for you. The codecs involved are covered by patent pools, and the licensing is settled by the people who ship decoders — the phone, the browser, the operating system — long before a file reaches you. It is why the format is everywhere in hardware and why royalty-free alternatives exist at all, and it changes nothing about converting a file you already have.
Does converting change the sample rate of my M4R audio?
+
Not unless you ask it to. A conversion keeps the source rate — 48 kHz stays 48 kHz, 44.1 kHz stays 44.1 kHz — because resampling is a small quality cost for no benefit when nothing requires it. The exceptions are real: audio CDs need 44.1 kHz, some older hardware players accept nothing else, and voice pipelines often want 16 kHz. Set the rate explicitly in those cases and leave it alone otherwise.
What should I convert M4R to for sharing?
+
For email and social-media sharing, convert M4R to MP3 — universal playback and small file size. For high-fidelity sharing with audiophiles, convert to FLAC or WAV to preserve the original quality.
How much will conversion change the file size?
+
Converting M4R to a lossless format like WAV or FLAC keeps the size large; converting to MP3 or AAC at common bitrates (192-320 kbps) shrinks the file by roughly 5-10x with minimal perceptible quality change.
