Almost every guide to this spends its time on the trimming, which is the part that takes a minute and goes right the first time. Then it stops at the moment the file lands in your downloads folder — which is where the actual difficulty starts.
So: how to pick the thirty seconds, what format each phone will accept, and the three things that make a ringtone sound wrong even when the cut was clean.
The tool Audio Cutter Trim a song or recording to the part you actually want. Drag the handles, save it.Pick the part people will actually hear
A ringtone is not a short version of a song. It is the first few seconds of one, played from a speaker the size of a fingernail, usually from inside a pocket or a bag.
Two consequences, and both of them change which section you choose.
Start on the good bit. Nobody hears the end of a ringtone — the phone is answered, silenced or missed long before it gets there. If the first two seconds are a quiet intro, that is the whole ringtone as far as anyone in the room is concerned. Cut to the chorus, or the hook, or whatever the recognisable part is, and start on it rather than leading up to it.
Avoid anything that lives in the bass. A phone speaker is physically too small to move much air, so the low end largely disappears. A section carried by a bassline is unrecognisable through it; one carried by voice or a melody in the middle of the range survives. This is why so many ringtones sound thin and tinny compared with the same song in headphones — nothing is wrong with the file.
Length: about thirty seconds, and less is usually better
Thirty seconds is the practical ceiling and also more than you need. Phones ring for a while before going to voicemail, and a ringtone loops, so the length of the clip is not the length of the ringing.
What the length does change is the loop point. A clip that ends mid-phrase and jumps back to the start is noticeable and irritating in a way that a well-chosen fifteen seconds is not. Ending somewhere the music resolves — the end of a line, a beat where something lands — makes the loop sound deliberate.
Android: the file is the ringtone
Android is the easy one. It accepts a plain MP3 and there is no special format.
The general shape is the same on every Android phone: get the file into the device’s Ringtones folder, then choose it in the sound settings. Most phones will also let you pick any audio file straight from storage without moving it first.
The exact wording of the menu differs by manufacturer — Samsung, Pixel, Xiaomi and the rest each name it slightly differently, and it moves between Android versions — so the reliable instruction is: look in Settings for Sound, then the ringtone, then whatever option lets you add your own. If your phone shows the file, you are finished.
iPhone: it has to be an M4R, and that is less than it sounds
An iPhone will not take an MP3 as a ringtone. It wants a file with the extension .m4r, and this is the single thing that sends most people looking for help. If you already have the right thirty seconds and only the format is wrong, converting it is the whole job.
Here is the part worth knowing, because it makes the whole problem smaller: an M4R is an M4A. Same AAC audio, same MP4 container, different extension. Apple uses the extension to mark a file as a ringtone rather than a song. There is no separate encoding step and no quality difference — cut to M4A and you already have the audio an M4R contains.
Getting it installed is the part that genuinely changes. Broadly there are two routes, and which one is current depends on your iOS version:
- On the phone itself, using Apple’s own GarageBand app: import the clip into a project, then export it as a ringtone. This has worked for years and needs no computer.
- Through a computer, syncing the M4R across with Finder on a Mac or the Apple Devices app on Windows. This is the older route and it has been renamed more than once.
We are not going to print the exact taps, because Apple moves them and a wrong instruction that stays online is worse than no instruction. Search for the method for your own iOS version — the audio file you made here is the same either way.
Three things that make a ringtone sound wrong
Silence at the start. Half a second of nothing before the sound begins is inaudible in a song and fatal in a ringtone: it lands right where the phone would otherwise have got your attention. Trim to the first sound, not to the bar before it.
A click at the beginning or the end. If the cut lands while the waveform is at full height, the sound jumps from loud to nothing in a single sample, and that jump is a click. Cutting in a gap, or on a note that has already decayed, avoids it — and that is far easier to place against a waveform you can see than against a pair of typed timestamps.
Too quiet. A ringtone competes with a street, a café, a washing machine. A section recorded quietly, or one that begins with a fade-in, loses that competition regardless of how the phone’s volume is set. Pick a loud passage.
One more thing about quality
It is tempting to keep the ringtone at the highest bitrate available. Do not bother.
The limiting factor is the speaker, by an enormous margin. A 30-second clip at a moderate bitrate is a fraction of a megabyte and sounds identical, through a phone speaker, to the same clip at the maximum — the difference is far below what that hardware can reproduce. If you want the reasoning in full, the bitrate guide works through what each setting actually buys.
What matters is the thirty seconds you chose. Nothing downstream of that decision will rescue the wrong ones.