How to Set a Custom Alarm Sound on Your iPhone

The alarm sound lives in the Clock app, not in Settings. Open Clock, tap the Alarms tab, tap the alarm you want to change, tap Sound, then tap Save. Apple’s guide describes the choice on that row as a vibration, song, or ringtone, and a tone you exported from GarageBand sits in that list beside Apple’s own. Engadget reports that a tone added with iOS 26’s Use as Ringtone shows up there too.

That is the entire procedure, and it is not where the mornings are lost. Three things about alarm sounds are easy to miss: a wake up alarm attached to a sleep schedule reverts unless you confirm it one specific way, neither way of adding a tone offers to put it on an alarm, and the tone you would happily pick as a ringtone is the wrong pick here.

Where the alarm sound is chosen

Alarm sounds are per-alarm, not global. Every alarm in Clock carries its own sound, so the 6:10 weekday alarm and the 9:00 Saturday one can differ, and changing one leaves the other alone. There is nothing anywhere in Settings called “alarm sound”.

Apple documents two routes back into an existing alarm, and both end on the same screen: tap the alarm time, or tap Edit at the top left and then tap the alarm time. Settings governs a different set of sounds entirely — that is where you change the system ringtone for calls, and the message alert has its own tone screen again. Nothing set on either of those reaches an alarm.

The wake up alarm reverts after one morning

A wake up alarm created from a sleep schedule is edited on a different screen from every other alarm, and it is the one place a new tone disappears on its own. Apple’s route in the iPhone User Guide runs through Clock, Alarms, then Change, then down to Alarm Options.

The trap is inside Apple’s own numbering. The final step reads: tap Done, then tap Change Next Alarm Only. Change This Schedule appears one line lower, in a Note, where Apple says that tapping it also updates the recurring wake up alarm in your sleep schedule. Follow the instructions literally and your tone plays tomorrow, then every morning after that quietly uses the old one, with nothing on screen to say so.

1. Step 1

   Open Clock, Alarms, then Change

   Ordinary alarms open by tapping the alarm time. The wake up alarm is reached only through Change.

2. Step 2

   Scroll down to Alarm Options

   Apple's step is to scroll to Alarm Options and turn the alarm on, and only then change the options underneath it.

3. Step 3

   Tap Sounds & Haptics

   The row is named Sounds & Haptics here, not Sound. Apple describes the choice as a vibration or ringtone.

4. Step 4

   Tap Done, then Change This Schedule

   Change Next Alarm Only gives your tone exactly one morning. Change This Schedule is the option that keeps it.

Two smaller differences live on the same screen. It carries its own Alarm volume slider, which ordinary alarms do not have — theirs comes from the Ringtone and Alerts slider in Settings on iOS 26. And because a song is not on the menu there, a custom wake up sound has to be a tone file rather than music you already own.

An exported tone never offers itself to an alarm

Adding a tone ends on a screen that does not mention alarms, whichever route you take. On iOS 18 and earlier, or when the sound needs editing such as layering, the route is GarageBand, and Apple’s GarageBand share steps name three destinations for a finished tone once the export completes. Every one of them is about calls, messages or a contact card. Alarm is not among them. On those older versions the route comes with a catch: GarageBand’s App Store listing now requires iOS 26.0 or later, so it 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. Exporting a tone in GarageBand is that route written out in full; what matters here is only what the prompt leaves out.

iOS 26 skips that prompt and leaves alarms out just the same. Its Use as Ringtone action, which Apple has not documented, reportedly takes an MP3 or M4A under 30 seconds from Files or Voice Memos and opens Settings at Sounds & Haptics, then Ringtone, with the new tone at the top of the list — a ringtone screen, not Clock. Use as Ringtone in Files sets out its steps.

That missing option is why people conclude a GarageBand tone works only for calls, messages and contacts. It does not. The tone exists; it is waiting in a list nobody sent them to, and the trip through Clock is a separate step you have to make yourself. No choice of format changes this part. On iOS 26 an MP3 or M4A reportedly needs only trimming to under 30 seconds, not converting, and converting an MP3 to M4R covers the .m4r a computer sync still expects.

Once a GarageBand tone is on the phone it appears on every alarm’s Sound screen alongside Apple’s built-in ones. Engadget’s alarm sound guide reports the same for a tone added with Use as Ringtone; it is the only report we found, and we have not confirmed it on a device. What a tone competes with there is a song, and the two fail differently.

Apple names “song” as a choice without attaching conditions to it, and publishes nothing about what happens when that song sits in your library but has never been downloaded to the phone. That silence is the practical argument for a tone file: a file on the device has no streaming state to lose. A voice memo tone is the same kind of object, so it lands in whichever row its route puts it: exported from GarageBand, or set straight from Voice Memos with Use as Ringtone.

Why the best ringtone makes the worst alarm

A ringtone and an alarm are heard by two different people. One is awake, holding the phone, in a room where other sounds already exist. The other is unconscious. Apple’s documentation records three consequences of that, and they are worth reading before choosing a tone.

The design consequence is the part nobody states. A ringtone succeeds by being recognizable — you need to know it is your phone. An alarm succeeds by crossing a boundary, and the whole crossing happens in the first second of audio. A song you love makes a poor alarm precisely because you have learned to hear it comfortably, which is the opposite of the required effect.

Fade settings follow directly from that, and the pair that makes a ringtone sound finished is the wrong pair here.

A ringtone can earn a fade-in: the clip usually starts mid-phrase, and a soft entry hides the cut while you reach for the phone. An alarm has no such grace. A half-second fade spends half of the only second that has to do the work, and spends it below the volume that wakes anyone. Leave the fade-in at zero, and put the clip’s start on the loudest moment of the audio rather than on a tidy bar line.

Keep the fade-out short rather than absent. A hard cut can end in an audible click, while a long tail ends the clip in quiet — the last thing an alarm should do. Two tenths of a second removes the click and is short enough that nothing goes soft.

When a custom alarm sound is the wrong project

A custom alarm sound earns the effort in one case. If Apple’s built-in tones still wake you, replacing them buys nothing: they are short, abrupt and deliberately unmusical, which is most of the specification for an alarm. If you have started sleeping through them, a tone that is louder and less predictable than the one your ear has learned is a real fix.

If the complaint is that you dislike waking to a jingle rather than that you miss it, stop before the trimmer. The alarm time, the snooze duration and the alarm volume in Settings are all on screens you already have open, and changing one of those addresses more mornings than the tone does.

And if an alarm you already built plays nothing, check its Sound before rebuilding it. An alarm that only vibrates has its Sound set to None, which is one of the causes on Apple’s checklist for a quiet alarm. A tone that stays inaudible everywhere, not just in Clock, is a different fault — that one is why a tone stays silent.