How to Make a Ringtone From an MP3 (iPhone & Android, 2026)

Custom ringtones are one of the few personalization choices left on a phone — the wallpaper changes, the icons shuffle, the notification chime gets buried under app sounds, but a ringtone is heard by you, in public, every time someone calls. Making one from an MP3 you already own is a 5-minute job once you know which path your phone needs. iPhone and Android take very different routes, and confusing the two is why most people give up halfway.

This guide walks both end-to-end: pick the moment, cut it, convert it (if needed), get it onto the phone, and assign it. It also covers the questions that actually break the workflow — file too long, wrong extension, sync silently failing, ringtone showing up but not playing.

The Two Paths in One Sentence

iPhone needs a .m4r file (which is just an M4A renamed) under 40 seconds, transferred via Music app/Finder on macOS or iTunes on Windows.

Android accepts any MP3 dropped into the /Ringtones folder, no conversion, no sync software.

Everything that follows is detail on those two sentences.

Step 1 — Pick the Right 15 to 30 Seconds

Most carriers ring for 25 to 30 seconds before voicemail picks up. There is no point making a 90-second ringtone — you will never hear past the first chorus. Aim for 20 to 25 seconds, with the recognizable hook landing within the first 1 to 2 seconds.

Three rules for picking the segment:

• Front-load the recognition. A ringtone that opens with a 4-second intro you set up at home is a ringtone that nobody recognizes when it goes off in a coffee shop. Start on the downbeat or the vocal hook, not the silence before it.
• Mind the dynamics. Ringtones play through tiny phone speakers in noisy environments. Quiet, intricate passages disappear. Loud, simple, wide-frequency moments cut through.
• Avoid sudden stops. Most phones loop the ringtone until you answer. A clean fade or a return to a recognizable downbeat loops cleanly; a hard cut on an unfinished bar sounds broken.

Open your file in /ringtone-maker — the waveform shows you where the loud sections are, and you can drag the selection handles to set in/out points to the millisecond. The tool is built specifically for this 15-to-30-second use case and runs entirely in your browser, so the song never leaves your device.

Step 2 — Cut and Export

Drop the MP3 into /ringtone-maker, drag the start and end handles, preview the segment, and click Export. The output format matches the input — if you fed in an MP3, you get an MP3 back. That MP3 works directly on Android. For iPhone, you need one more step.

If you want to fine-tune (fade in/out at the edges to avoid clicks), /audio-trimmer and /mp3-cutter both produce frame-accurate cuts. For the difference between trimming and cutting see trim mp3 without losing quality.

Step 3a — iPhone: The .m4r Path

iPhone ringtones must be:

• M4A audio (AAC inside an MP4 container)
• Renamed with the .m4r extension
• 40 seconds or shorter (the system silently rejects longer files)
• Transferred via the Music app (macOS Catalina or later), Finder (sync), or iTunes (Windows)

The full pipeline:

1. Cut the segment as MP3 in /ringtone-maker. Keep it under 30 seconds. 2. Convert MP3 to M4A using /mp3-to-m4a. The output is now an .m4a file. 3. Rename the extension from .m4a to .m4r. On macOS, click the file once, press Return to rename, change the trailing letters, accept the warning. On Windows, enable "File name extensions" under View in File Explorer first, then rename. 4. Get it onto your phone. This is where most people stall. There are two routes depending on your computer:

On macOS (Catalina or later): Open the Music app. Drag the .m4r file directly into the Music app sidebar — it appears under "Tones" in some versions, or stays in your library. Connect your iPhone via USB cable. Open Finder, click your iPhone in the sidebar, go to the General tab, scroll down, and click Sync. The .m4r will transfer.

On Windows: Install iTunes (Microsoft Store version is current). Open iTunes, drag the .m4r into the iTunes window. Connect your iPhone, click the iPhone icon, go to Tones, check "Sync Tones," and click Apply.

5. Assign the ringtone. On the iPhone: Settings → Sounds & Haptics → Ringtone → your new tone appears at the top of the list. Tap to select.

If the ringtone does not appear after sync: check that the file is genuinely under 40 seconds (the iPhone rejects without warning), confirm the extension is .m4r and not .m4a.m4r (Windows hides extensions by default), and unplug/replug the cable to force a re-sync.

Step 3b — Android: The Ringtones Folder Path

Android does not care about format gymnastics. An MP3 dropped into the right folder is a ringtone.

1. Cut the segment as MP3 in /ringtone-maker or /mp3-cutter. Length does not matter for Android, but 25 seconds is still the sweet spot. 2. Transfer the file to your phone. Pick whichever is easiest: - USB cable. Connect, accept "File transfer / Android Auto" on the phone, open the phone in your computer's file browser, navigate to Internal Storage, paste the file into /Ringtones (create it if it does not exist). - Email it to yourself. Open the email on your phone, download the attachment. - AirDroid, Snapdrop, or Quick Share. Wireless transfer over the local network. - Google Drive. Upload, then download to your phone. 3. If you transferred to Downloads instead of /Ringtones, use the Files app on your phone to long-press the MP3 → "Set as ringtone" (the menu name varies by manufacturer). 4. Assign it. Settings → Sound & vibration → Phone ringtone (or "Ringtone") → pick your file from the list.

On Samsung, the path is Settings → Sounds and vibration → Ringtone. On Pixel, Settings → Sound & vibration → Phone ringtone. On older Android versions some manufacturers disabled the /Ringtones auto-pickup; the Files-app "Set as ringtone" route works on all modern Android builds.

A Note on Copyright

You can legally make a ringtone from a song you own (CD rip, purchased download). You can legally make one from royalty-free music or your own recordings. Streaming-service tracks (Spotify, Apple Music, YouTube Music) are licensed for personal listening only, and ripping or extracting them for re-use is technically a license violation even if the audio quality is fine. For pure personal use the legal exposure is essentially zero, but redistributing or selling the resulting ringtone is genuinely off-limits.

Why Use a Browser Tool Instead of Uploading to a Random Site

Most ringtone-maker websites work by uploading your MP3 to their server, processing it there, and emailing back a download link. That means a copy of your music — possibly a song you legally own, possibly something private like a voice recording — sits on a stranger's storage indefinitely. Some of those services explicitly mention "user uploads" in their terms.

/ringtone-maker processes the file entirely in your browser using WebAssembly. The audio never leaves your computer. There is no upload, no server-side copy, no privacy policy to read. For the same reason, /audio-cutter, /audio-splitter, and /audio-trimmer all run client-side. This is the right default for any audio you would not be comfortable handing to a stranger.

Pre-Flight Checklist

Before you sync, confirm:

• File extension is correct (.m4r for iPhone, .mp3 for Android)
• File length is under 40 seconds for iPhone, under 30 seconds preferred for both
• The file actually plays back from your computer (open it and hit play)
• The phone is unlocked when you connect it (iOS will not transfer to a locked device)
• For iPhone Windows users: iTunes is updated to the current Microsoft Store version

If the ringtone shows up but plays silently, the export step probably wrote a corrupted M4A. Re-export from /mp3-to-m4a and try again. If the ringtone is too quiet, the source MP3 is probably low-volume — re-cut from a louder section, or normalize the source first using audio-cutter (which preserves source levels, so pick a louder source).

Why iPhone Insists on .m4r and Android Doesn't Care

The asymmetry between the two platforms comes down to product philosophy. iOS treats ringtones as a separate content category from music — they appear in their own section of the Music app, sync via a different code path, and live in a different filesystem location on the device. To enforce that separation, iOS requires the .m4r extension as the type tag. The audio inside is plain M4A (AAC in an MP4 container), and a binary diff between an .m4a and an .m4r of the same audio shows zero difference in the audio bytes. Only the filename's extension changes, and that extension is what iOS uses to route the file into the ringtone category.

Android treats ringtones as a metadata flag on a regular audio file. Drop an MP3 into /Ringtones and the system scans the folder, picks up the file, and exposes it in the ringtone picker. There is no separate format because there is no separate category — a ringtone is just an audio file that happens to be tagged for ringtone use. This is why Android accepts MP3, M4A, OGG, FLAC, and WAV interchangeably, and why the Files app's "Set as ringtone" menu item works regardless of where the file lives in storage.

The practical consequence: the Android workflow is genuinely one step (transfer + assign), while the iPhone workflow has the extra format-conversion and sync layers. Neither is harder — they are just different in number of steps.

Picking a Hook That Loops Cleanly

A ringtone plays in a loop until you answer or the call goes to voicemail. A 25-second clip with a hard cut at the end loops with an audible bump every 25 seconds; a 25-second clip that ends on the same beat it started on loops invisibly.

The trick is to set your end point at the same musical position as your start point. If the song is in 4/4 at 120 BPM, each bar is 2 seconds. A 24-second clip is exactly 12 bars and loops cleanly if you start and end on beat 1. A 25-second clip is 12.5 bars and produces a noticeable hiccup at the loop point because the meter resets mid-phrase.

Two practical approaches:

• Pick a length that is a whole-bar multiple. Open /ringtone-maker, zoom in on the waveform, and snap your selection to the same beat at start and end. The waveform usually shows the beat clearly as repeating peaks. 8 bars, 12 bars, or 16 bars are typical.
• Apply a 100-200 ms fade at the end. The fade hides the loop-point discontinuity at the cost of a brief volume dip every loop. Less musical but more forgiving.

For songs you do not know the BPM of, the eyeballed approach works fine — just zoom in and look for repeating peak patterns to find the beat.

What Happens to the File on Each Step

A common confusion is what format the audio is actually in at each stage. Tracking it explicitly:

• Step 1 output (after /ringtone-maker): MP3, same bitrate as input, sample-precise cut at the requested timestamps. On Android this is your final file.
• Step 2 output (after /mp3-to-m4a): M4A — AAC audio at typically 256 kbps inside an MP4 container. The MP3-to-AAC re-encode adds a generation of compression loss, but at 256 kbps AAC the loss is inaudible on phone speakers.
• Step 3 output (after rename): Same M4A bytes, now with a .m4r extension. iOS recognizes this as a ringtone.
• Step 4 output (after sync): A copy of the .m4r lives on the iPhone in the system tones location, ready for assignment.

Nothing in this chain re-encodes twice — the worst case is one MP3-to-AAC pass at step 2, which is the only lossy step in the whole pipeline. Quality on the phone speaker is indistinguishable from the source MP3.

The 5-Minute Recipe

Distilled to the smallest possible workflow:

iPhone: /ringtone-maker → cut to 25 seconds → /mp3-to-m4a → rename .m4a to .m4r → drag to Music/iTunes → sync → Settings → Sounds & Haptics → pick.

Android: /ringtone-maker → cut to 25 seconds → copy MP3 to phone → Settings → Sound → Ringtone → pick.

That is the entire process. Everything above is detail on the parts that go wrong.

For more on cutting MP3 audio cleanly see how to trim mp3 without losing quality. For the Audacity desktop alternative see how to cut audio in Audacity. For the format mechanics behind .m4a vs .mp3 see what is MP3. For other browser-based cuts see /audio-cutter, /audio-splitter, and /mp3-cutter.