Audio · No upload
Ringtone maker
Drop a song, choose the part you want, and download it as a ringtone. The cuts snap to zero crossings so it does not click, the loop seam where the end meets the start is measured and playable on its own, and the length is checked against the phone limits before anything is encoded. Nothing is uploaded.
Getting it onto your phone
Cutting the audio is the easy half. Installing it is where most ringtone tools stop talking, so here is the whole of it — including the part that explains why this page hands you an MP3 rather than something that claims to be a ringtone file.
Android
The MP3 is already the ringtone. Copy it to the phone, put it in the Ringtones folder on internal storage, then open Settings, choose Sound, choose Phone ringtone, and pick it from the list. Some launchers also let you set a downloaded file straight from the file manager by long-pressing it. Nothing needs converting.
iPhone
An iPhone ringtone is an M4R file — AAC audio inside an MP4 container — and iOS will not accept an MP3 in its place. Save this page's MP3 into the Files app, open GarageBand, add an Audio Recorder track, use the loop browser to import the file, trim it to 30 seconds or less, then hold the project in My Songs and choose Share, then Ringtone. On a computer, connecting the phone and dragging the file onto the device in Finder puts it under Sounds.
Why this page does not write M4R itself: making one needs an AAC encoder. Browsers expose an audio encoder, but the open-source browser build this site's own security and browser tests run against advertises no AAC at all, and one major browser has none either — so an M4R button here would work for some visitors, silently produce nothing for others, and could not be checked by the tests that gate every release. A tool that cannot verify its own output is how a broken file ships. The MP3 above is real, the steps are the ones that work, and the limitation is written down instead of hidden.
How this ringtone maker works
What is measured is the audio itself. Your browser decodes the file with its own audio engine into raw samples, and everything after that is arithmetic on those numbers: the waveform strip is a peak envelope, two values per slice, so a short transient cannot hide between two drawn columns. The selection you set in seconds becomes a pair of sample indices, and the readout reports the length, the estimated encoded size at your chosen bitrate, and whether that length fits the phone limits.
How the cut is made is where the honesty is. A cut at a non-zero sample is a step discontinuity and therefore a click, so both edges are moved to the nearest zero crossing within ten milliseconds, and the page prints how many samples that took; where no crossing exists in the window it says so and leaves the edit alone rather than dragging it somewhere you did not choose. Because a ringtone repeats, the end also runs back into the start, and that seam is measured as the jump between the last sample and the first, in dBFS, with a button that plays only the join. The fades are equal-power rather than linear, because loudness follows amplitude squared and a straight-line fade audibly dips in the middle. The trimmed and faded samples are then handed to the shared MP3 pipeline, which is the same encoder every other audio page here uses.
The limits are worth stating plainly. Re-encoding is lossy, so a ringtone cut from an already-compressed song carries a second generation of loss, and no setting here undoes the first one. The seam figure describes the discontinuity in the samples, not how objectionable it will sound on a particular speaker. The phone limits are the published ones and phone software changes. The preview is rendered and played inside this tab and is not the encoded file, so it will not reproduce artefacts that come from the MP3 encoder itself. And this page cannot see the copyright status of anything you open — cutting a ringtone from music you do not own is between you and whoever does.