Why Your Browser Alarm Isn't Ringing (And How to Fix It)
Web-based alarms work great when they work. When they don't, the cause is usually one of five things. Here's how to diagnose and fix yours.
The five common causes
If your web-based alarm didn't ring when you expected, it's almost certainly one of these:
- The browser tab was closed
- Autoplay was blocked because you hadn't interacted with the page
- The tab was discarded/suspended by the browser
- The computer went to sleep
- The audio output was muted or routed elsewhere
Let's go through each.
Cause 1: The tab was closed
This is by far the most common reason. A web alarm runs as JavaScript inside a browser tab. When you close that tab, all the JavaScript stops. There's no JavaScript left to fire your alarm at the scheduled time.
You don't need the tab to be visible — minimized is fine, behind other tabs is fine. But the tab must exist.
Fix: Keep the alarm tab open. On ClockWithUs, the alarm is also persisted across page navigation (so you can browse other pages on the same site), but closing the browser entirely will still end it.
Cause 2: Autoplay was blocked
Modern browsers block sound from playing on a page unless the user has interacted with that page. This stops ads from blaring at you. But it also means an alarm sound can be blocked if you set the alarm and then walked away without clicking anything.
How to tell: you'll often see the alarm overlay appear on the page, but no sound plays.
Fix: Click anywhere on the page after setting the alarm — anywhere counts as "interaction" and unblocks audio. Most alarm sites also play a test sound or otherwise capture a click during setup, which usually handles this automatically. If sound is still blocked, check your browser's site settings for the page and explicitly allow sound.
Cause 3: The tab was suspended
If you keep a tab open but ignore it for a long time (especially on mobile), the browser may "discard" or suspend it to save memory. The tab still appears in your tab list but its JavaScript is paused.
Chrome calls this "tab discarding"; Safari calls it "snapshot mode." Either way, your alarm won't fire because the timer code isn't running.
Fix:
- Keep the alarm tab visible (not behind dozens of other tabs)
- Tap or click the tab occasionally to mark it as active
- On Chrome desktop, pin the tab — pinned tabs are less likely to be discarded
- For overnight alarms, consider using your phone's native alarm app instead
Cause 4: The computer went to sleep
If your laptop goes to sleep at 11 PM and your alarm is set for 7 AM, the JavaScript inside the browser is also asleep. When the computer wakes, the alarm time has already passed.
Fix:
- Plug the computer in (lid-closed sleep is usually triggered by battery saver)
- Disable sleep in your power settings for the duration of the alarm
- On macOS: Settings → Lock Screen → "Turn display off after" = Never (or longer than your alarm)
- On Windows: Settings → System → Power → Screen and sleep → set to Never
- The ClockWithUs alarm requests Wake Lock API when you set an alarm, which can help prevent display sleep on supported browsers — but it doesn't override aggressive power settings
Cause 5: Audio is muted or routed elsewhere
Sometimes the alarm fires correctly but the sound goes nowhere. Common reasons:
- System volume is muted or at zero
- Audio is routed to Bluetooth headphones (which are off, or in their case)
- The browser tab is muted (right-click tab → "Unmute site")
- An external monitor with no speakers has hijacked audio output
Fix: Before relying on a critical alarm, do a test run a few minutes before the real time. Set an alarm for 2 minutes from now and confirm it actually rings audibly through your current audio setup.
When NOT to use a web-based alarm
Web alarms have a place, but be honest about their limits. Don't rely on a web alarm for:
- Critical wake-up times (flights, exams, job interviews) — use your phone's native alarm with backup
- Overnight alarms when your computer might sleep — same advice
- Times when you'll close the browser — the alarm dies
Web alarms are great for:
- Reminders during the workday while you're at your computer
- Cooking timers, exercise intervals, study sessions
- Quick "remind me in 20 minutes" needs
- Setting alarms on a shared family computer without using anyone's phone
Frequently asked questions
Why isn't my web alarm playing sound?
Most often, the browser blocked audio because you hadn't interacted with the page. Click anywhere on the page after setting the alarm — that unblocks audio for that site. If that doesn't fix it, check that your system volume is up and the browser tab isn't muted (right-click tab > Unmute).
Will a web alarm work if I close the browser?
No. Web alarms run as JavaScript inside an open browser tab. Closing the tab — or the entire browser — ends the JavaScript and the alarm won't fire. For alarms that need to fire when the browser is closed, use your phone's native alarm app or a desktop alarm app, not a web-based one.
Why does my alarm fire late or not at all when my laptop wakes from sleep?
Because the JavaScript timer was paused while the laptop slept. When the laptop wakes, the alarm time has already passed. To prevent this, disable sleep mode while your alarm is scheduled, or use your phone's alarm instead.
How do I keep a browser tab from being suspended?
Pin the tab (right-click the tab > Pin) — pinned tabs are less aggressively discarded. Keep it visible rather than behind many other tabs. Avoid using mobile browsers for long-running alarms; mobile aggressively suspends background tabs to save battery.
Are web alarms reliable enough to wake me up for work?
For most people, not as your primary alarm. Use your phone's native alarm app for that — it's designed to fire even when the phone is locked and asleep. Web alarms are great for daytime reminders while you're at your computer, but not for critical overnight wake-ups.