Understand the limit first
A webpage cannot power on a sleeping or shut-down device, override a muted system, or guarantee that an operating system will keep a background tab active. Browsers intentionally restrict background activity to save battery and protect privacy.
Pre-alarm checklist
- Test the selected sound.
Preview it at the exact system volume you will use. - Check every mute control.
Confirm that the device, browser, tab, and external speaker are not muted. - Keep power connected.
Avoid low-power modes that suspend applications or network activity. - Keep the browser and tab open.
Do not close the window or rely on a discarded background tab. - Allow the permissions you need.
Audio, notifications, and microphone access are separate browser permissions. - Run a one-minute test.
Lock or position the device the way you plan to leave it, then confirm the alarm rings.
If the alarm is silent
- Increase system volume and media volume—not only ringtone volume.
- Look for a muted-speaker icon on the browser tab.
- Disconnect Bluetooth headphones or speakers you will not be wearing.
- Preview a built-in tone to separate a custom-file problem from a general audio problem.
- Interact with the page once; some browsers block audio until the user has clicked or tapped.
If the alarm is late or never starts
- Disable battery saver or low-power mode for the test.
- Prevent the computer from sleeping while plugged in.
- Keep the AlarmClock.live tab selected or in an active browser window when possible.
- Avoid private browsing if it clears permissions or local settings when the session ends.
- Confirm that the device clock and time zone are correct.
- Reload the page, recreate the alarm, and test it one minute ahead.
If a custom sound fails
First switch the alarm to a built-in sound. If that works, reselect or rerecord the custom audio and preview it again. Browser cleanup tools, private sessions, changed permissions, and removed local files can affect custom media.
For linked streaming media, remember that a third-party service may require sign-in or a manual play action. Keep a built-in tone as the dependable fallback.
Mobile device considerations
Phones and tablets apply aggressive background restrictions. Keep the browser open, connect power, disable low-power mode, and test after locking the screen. If the test does not ring under the same conditions you plan to use overnight, use the device’s native alarm instead.
Why browsers can delay alarms
Browser timers are not a guaranteed delivery service. Background tabs can be throttled, and audio can be suspended until a user interacts. A page can compare against a target time when it runs again, but it cannot recover an alert at the original moment while the device was asleep.
Technical references: MDN on background-tab behavior and Chrome on Web Audio activation.