Apple Watch silent alarm not working: what to check
Short answer: the four causes that account for almost all of these are the watch wasn't on your wrist (charging, or you took it off at 2am), the strap was too loose for the taptic engine to couple properly, an alarm you set on the iPhone never became a watch alarm, and a Focus or Sleep schedule changed how alerts were delivered. Work through those in that order before you assume the hardware is broken.
Apple moves settings between watchOS versions, so this page deliberately describes what to look for rather than a menu path that will be wrong in six months. Search the setting name in the Settings app on the watch or the Watch app on your phone — that's more reliable than any tutorial, including this one.
Full disclosure: we make Silent Wake, a dedicated wrist-worn vibration alarm. Most of this page is troubleshooting a product we don't sell. The last section is the honest argument for when a smartwatch is the wrong tool, and we've tried to keep it to the cases where that's actually true.
Start here: was the watch on your wrist?
Unglamorous, and it's the answer more often than everything below combined.
An Apple Watch is a daily-charge device. The natural place for a daily-charge device to spend the night is on a charging puck, and a watch on a charging puck taps nobody. People set the alarm, put the watch on to charge, and are then baffled the following morning. If your charging routine is overnight, your watch alarm is decorative.
The second version of this: you took it off during the night. Straps get uncomfortable, wrists sweat, and a half-asleep person removing a watch will not remember doing it in the morning. If the watch is on the nightstand when you wake, that's your answer.
The third: wrist detection. When the watch can tell it isn't being worn, its alerting behaviour changes. If you've turned wrist detection off — many people do, to stop the watch locking constantly — you may also have changed how and whether alerts reach you. Check whether it's on and what your watch is configured to do when it thinks it's off-wrist.
The strap was too loose
The taptic engine works by moving a small mass against the case, and the case has to be in firm contact with skin for you to feel it. A watch that slides an inch up your forearm during the night is transmitting most of that energy into the air.
This is the single most common fixable cause. Tighten it one hole past where you'd wear it in the day — snug, not tight enough to leave a mark or restrict circulation. Wearing it slightly further up the forearm, where the wrist is less bony and the band sits flatter, often helps too.
Also worth knowing: haptics are easier to sleep through on the top of the wrist than the underside, where the skin is thinner and more sensitive. Flipping the watch so the case sits against the inside of your wrist overnight is free and frequently works.
The alarm existed on the phone but not on the watch
Alarms in the Apple ecosystem can live in more than one place, and the relationship between them has changed across OS versions.
The behaviours worth understanding are: an alarm created on the watch is a watch alarm and fires on the watch. An alarm created on the iPhone may or may not surface on the watch, depending on your settings and whether the two are connected at the time. And on some configurations, an iPhone alarm going off can cause the watch to alert instead of the phone if the watch detects you're wearing it — which is a feature that also means the reverse can happen.
The practical test: set the alarm directly on the watch itself, using the watch's own Alarms app, and see if the failure persists. If it doesn't, your problem was never the hardware — it was which device owned the alarm.
Related, and a frequent surprise: a Sleep schedule set up in the Health or Sleep app is a different thing from an alarm in the Alarms app. Both can wake you, both can be disabled independently, and turning one off does not turn the other on.
Focus modes, Sleep Focus, and Silent Mode
Three separate things people conflate.
Silent Mode mutes sound. It is not supposed to disable haptics — that's the entire point of it. If you've silenced the watch and are getting no tap either, something else is going on, and it's worth checking whether you've also enabled a setting that reduces or disables haptic feedback generally.
Focus modes, including Sleep Focus, change which notifications get through. Alarms are normally exempt, but Focus configurations can be edited, and a Focus that's set up unusually — or a Sleep Focus schedule that's ending at the wrong time — will change what reaches you overnight.
Theatre Mode (or whatever the current equivalent is called) keeps the screen dark and can affect alerting behaviour. Check whether it's on; it's easy to enable accidentally from the control centre and easy to forget about.
Haptic strength. There is a setting controlling how strong system haptics are, and a related option for making alerts more pronounced — usually described as prominent or emphasised haptics. If yours is on the weak setting, turn it up and enable the prominent option. This is one of the highest-value five-second fixes on this page.
Battery, power reserve, and updates
| Symptom | Likely cause | What to check |
|---|---|---|
| Nothing at all, watch shows a red lightning bolt or a minimal clock face | Power reserve — the watch shut down non-essential functions overnight | Whether the battery lasts your full night; charge earlier in the evening rather than overnight |
| Worked for months, then stopped after an update | OS change altered a default or reset a setting | Re-check haptic strength, Focus settings, and whether the alarm still exists |
| Intermittent — some mornings yes, some no | Loose strap, or the watch coming off during the night | Tighten the band; check where the watch is when you wake |
| Alarm fires on the phone, not the watch | Alarm ownership and connection state | Set the alarm on the watch itself |
| Third-party alarm app is unreliable | Background execution limits | Use the built-in Alarms app; third-party alarms are not guaranteed to run |
On battery: an Apple Watch that's a couple of years old holds noticeably less charge than a new one, and the first thing to fail is the tail end of a long night. If the alarm is fine at 6am but has never once worked at 7:30am, look at battery health before anything else.
On third-party alarm apps: iOS and watchOS restrict what apps may do in the background. The built-in Alarms app has privileges a downloaded app does not. If you're relying on a third-party alarm and it's flaky, that's expected behaviour rather than a bug.