MP3 to M4R: Turning an MP3 Into an iPhone Ringtone

Since iOS 26, an MP3 under 30 seconds may not need converting at all. Use as Ringtone in Files reportedly takes the file as it is: touch and hold the MP3, tap Share, then Use as Ringtone, and Settings opens with the new tone at the top of the Ringtone list. Every how-to, MacRumors’ walkthrough among them, names the same two formats: MP3 and M4A. Apple has not documented the action.

An .m4r still matters, just for fewer jobs. It is not a separate audio format but AAC audio inside an MPEG-4 container — the same construction as an .m4a — carrying an extension that marks the file as a tone rather than a song. Converting an MP3 into one means re-encoding it, not renaming it, and a real .m4r earns its place when the tone is going to be copied over from a computer, a step Apple does not document. On an iOS 26 phone, re-encoding matters only when the MP3 is not under 30 seconds and has to be trimmed first.

Even then, the conversion is only half the job. The other half is the install, and that is where most conversions are wasted. This page covers what the format is, why the rename trick fails, the four routes that end with the tone actually playing, and the two where no conversion is needed at all. The Settings side of it belongs to how iPhone ringtones are set.

What an .m4r file actually is

An .m4r file is an MPEG-4 audio file wearing a ringtone extension. Apple’s uniform type identifier registry gives MPEG-4 audio the identifier public.mpeg-4-audio, describes it as a type that represents an MPEG-4 audio layer file, and has it conform to both public.mpeg-4 and public.audio. That is the family .m4a belongs to, and a working .m4r sits in the same family.

Apple publishes no specification page for the .m4r extension itself. So the honest description is not “Apple says an .m4r is X” but “every tool that produces a tone iOS accepts writes the same thing” — AAC frames in an MP4 container, saved under a different suffix.

ToneWand’s own exporter is a concrete example of that. It encodes the trimmed clip as AAC-LC, the mp4a.40.2 profile, at 128 kbps, muxes it into an MP4 container and hands the file back named .m4r — or, as the same bytes, named .m4a under Other formats. Nothing in the container is ringtone-specific; only the suffix changes. The output has been checked in the browser — a valid MP4 that decodes back with the fades intact — but neither file has yet been checked on a device, not synced as an .m4r and not handed to Use as Ringtone as an .m4a, so that last leg is a reasoned expectation rather than a tested claim.

Why renaming an MP3 to .m4r does not work

Renaming a file changes its label, not its contents. An MP3 holds MPEG-1 Audio Layer III frames; change the extension and it still holds MPEG-1 Audio Layer III frames, with no MPEG-4 container anywhere inside. Any decoder that opens the file reads the bytes, and the bytes did not move. On iOS 26 the rename is also beside the point: Use as Ringtone reportedly takes the MP3 itself, and .m4r is not one of the two formats the how-tos name for it. We have not tested what the action does with a renamed file.

What makes the trick look plausible is that the phone plays the MP3 perfectly well. Apple’s iPhone audio playback list names AAC, APAC, MP3, Apple Lossless, FLAC and three Dolby formats. Decoding was never the obstacle.

Those two problems get conflated constantly. The container is a conversion problem, solved by re-encoding. Getting the tone into Settings is an install problem, solved on the phone — by Use as Ringtone since iOS 26, by GarageBand before it. On iOS 26 an MP3 under 30 seconds reportedly has no conversion problem at all, which leaves only the install. On older versions, a converter that only fixes the first problem leaves you exactly where a rename would have, minus the false confidence.

Four routes that turn an MP3 into a ringtone

Four routes end with an MP3 playing when your phone rings, and they differ in who does the converting and who does the installing. Which one is shortest depends mostly on your iOS version and on how long the MP3 runs.

Only the last two leave you with a converted file to handle yourself, and only the sync needs that file to be an .m4r. Since iOS 26, an MP3 under 30 seconds needs no conversion before Use as Ringtone sees it: the action reportedly takes MP3 or M4A — the two formats every how-to names. The same was already true of GarageBand. Apple’s guide to the formats GarageBand imports lists AIFF, WAV, Apple Loops, AAC and MP3, and adds that an imported file is converted to 44.1 kHz, 16-bit when the original differs. If the audio is already on your iPhone, the file format question never arises on either route.

That same list explains a wrinkle in the browser row. It names AAC and MP3 by format, not .m4r by extension, and Apple documents nothing about handing a finished tone file back to GarageBand. So the .m4r download is the file for a computer, and on the phone the browser export earns its place in one case: on iOS 26 or later, an MP3 that is not under 30 seconds. Trim it, take the .m4a — one of the two formats Use as Ringtone is reported to take — and finish in Files. On iOS 18 and earlier, a phone-only finish is simpler if you give GarageBand the original MP3 and trim it there yourself, as GarageBand’s export route shows step by step. GarageBand’s App Store listing now requires iOS 26.0 or later, though, so on those versions this works only if GarageBand is already on the iPhone or the App Store offers an older version that still runs there. Apple does not say when it offers that older version; users report it for apps the same Apple Account has downloaded before.

The desktop row is the one that goes wrong most often, because Apple documents no step for moving a tone file from a computer into the Ringtone list. What actually works, and what merely circulates as folklore, is sorted out on putting a tone on without iTunes.

Converting in the browser or on a computer

The choice between a browser trimmer and a desktop tool is really a choice about where the MP3 already lives. Both write the same kind of file; they differ in how much control they give and in what they leave you to finish.

Does an .m4r have to be 30 seconds

The 30-second limit belongs to the install route, not to the container. Nothing in an MPEG-4 file caps how long the audio runs, and a four-second .m4r is a perfectly valid tone. The number comes from Apple’s GarageBand sharing guide, which gives 30 seconds as the maximum length for a ringtone exported from that app and shows a dialog when a project runs longer, so on that route it binds the export rather than the file you imported.

Use as Ringtone checks the file itself. A longer file still shows the option, but iOS answers with a “File Too Large” alert asking for a ringtone under 30 seconds instead of trimming it, as Dedoimedo’s hands-on test shows. On iOS 26, then, the file you convert or trim has to be under 30 seconds. What GarageBand’s dialog does, and why letting it choose is a bad idea, belongs to the GarageBand walkthrough linked above — for conversion purposes, treat 30 seconds as a ceiling rather than a target.

When the .m4r plays but never appears in Settings

A tone that plays fine from Files and never shows up in Sounds & Haptics has usually been stored rather than installed. Playing an .m4r proves the conversion worked; it proves nothing about the install, and the two failures look identical from the outside.

On iOS 26 the install is reportedly one action in Files: the Share steps at the top of this page, with Use as Ringtone under More if it is not listed. Hand that action the original MP3 or the .m4a rather than the .m4r — MP3 and M4A are the two formats every how-to names, while reports on .m4r conflict and none shows a test. Settings should open on the Ringtone screen in Sounds & Haptics with the tone at the top; reports disagree on whether it arrives already ticked, so tap it if it is not. The reported reasons the action is missing or refuses a file, from a clip that is not under 30 seconds to a file still waiting in iCloud Drive, are covered under when Use as Ringtone fails.

The other symptoms and their fixes are collected on ringtone troubleshooting on iPhone, including the common case where the tone is present but you are reading the wrong row — setting a separate text tone is a different list on the same Settings screen, and a tone assigned to one contact overrides whatever is selected there.

One shortcut is worth knowing before you convert anything at all. Recordings you make yourself arrive as .m4a, the same MPEG-4 container under a different extension, which is why recordings from Voice Memos skip the format question entirely.

When converting is the wrong move

Converting an MP3 is the wrong move whenever the phone is going to do the work anyway. Since iOS 26, Use as Ringtone reportedly takes an MP3 under 30 seconds as it is, and GarageBand imports an MP3 as it is, so a conversion beforehand adds a generation of lossy re-encoding and buys nothing. It earns its place only when the file has to change or travel — a long MP3 cut under 30 seconds for the Files action, a tone headed from a desktop library into a sync, a tool that exports nothing else, or a workflow where you want the finished tone archived.

If you would rather an app handled converting and importing in one pass, iPhone ringtone apps worth installing compares them honestly, including where they charge for the part iOS and GarageBand do free. And if the MP3 was only ever a means to an end, buying a ready-made tone sidesteps the format question completely: a purchased tone lands in the list without a file ever existing on your side.