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.

Statusidle Files File Duration Source Selection Phone fit Cut Loop seam Estimated size Network since file read
Waveform — the selection is bracketed

    

    

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.

Frequently asked questions

Is my music uploaded anywhere?
No. Your browser opens the file with its File API and decodes the audio itself, and the trimming, the fades and the export all happen inside this tab. The readout's network meter counts every request from the moment your file is read and stays at zero. There is one honest footnote and the meter is arranged so it does not hide it: the MP3 encoder is a library this page downloads once, and it is fetched before the meter arms — while you are still choosing a file — so the zero you read is about your audio and not about the page. Nothing you choose is ever sent anywhere.
How do I put this on an iPhone?
An iPhone will not take an MP3 as a ringtone directly. It wants an M4R file, which is AAC audio in an MP4 container, and the two routes to one are GarageBand on the phone or a computer. On the phone: save the MP3 from this page to the Files app, open GarageBand, start an audio recorder track, import the file from Files, trim it to 30 seconds or less, then use Share and choose Ringtone. On a computer: connect the phone, drag the file into the device's General tab in Finder or the equivalent, and it appears under Sounds. This page does not make M4R itself, and that is deliberate rather than an oversight — see the explanation below for why an honest MP3 plus these steps beats a file that only claims to be a ringtone.
Why does my ringtone click at the start or when it repeats?
Because a cut in the middle of a waveform is a step, and a step is a broadband click. If the sample where you cut is not close to zero, the speaker is asked to jump instantly from silence to that value, and you hear it as a tick. Snapping the cut to the nearest zero crossing removes it, and this page reports how many samples it moved rather than just claiming the cut is clean; if there is no zero crossing within ten milliseconds it says so and leaves your cut alone. The second click is the one people miss: a ringtone repeats, so the end runs straight back into the start, and that join is a cut nobody inspects. The readout measures that jump in dBFS and the loop seam button plays the join on its own so you can hear it before the phone does.
How long can a ringtone be?
An iPhone ringtone is capped at 30 seconds, and going over is not a matter of taste: the file is refused rather than trimmed for you. Android is more relaxed and 40 seconds is a safe practical ceiling, though most people never hear past the first ten. Below about three seconds a tone reads as a notification blip rather than a ring. The readout turns those numbers into a verdict on the selection you actually made, so the length is settled before anything is encoded rather than after your phone rejects the file.
Which audio formats work here?
MP3 is the output, and the input list — MP3, M4A and AAC, WAV, OGG and Opus, FLAC, AIFF and WebM audio — is simply every audio format your browser can decode itself. That is the whole selection rule: decoding is done by the browser's own audio engine, so this page ships no decoder, and a format the browser cannot open is refused by name rather than attempted. Encoding is the one exception and it is disclosed everywhere it matters: the MP3 encoder is the LAME library, vendored as lamejs, downloaded once by your browser and run inside this tab. Re-encoding is lossy, so cutting a ringtone out of an already-compressed song costs a generation of quality.

Related tools