Start with a built-in sound and the page visible. This separates a general audio problem from a problem with a particular recording or media link. On the homepage, choose a sound and press Test sound. In the timer directory, press the same-named control before starting your countdown.
1. Enable audio with a click or tap
Browsers restrict automatic audio playback. Interact directly with the sound test after opening or restoring the page. A saved alarm or a restored countdown can retain its time without retaining permission to make sound. If the page reports blocked audio, test again after checking the browser’s site sound setting.
2. Check the tab and the device separately
A device can have its volume up while a browser tab is muted. Look for the tab’s mute control and check the site’s sound permission. Then check the operating system’s volume mixer if it provides per-application controls. Change one setting at a time and repeat the same built-in test so you know what helped.
Use a comfortable volume. If a test still fails, jumping immediately to maximum volume can create an unpleasant surprise when you find the correct output.
3. Find where the sound is going
Connected headphones, Bluetooth speakers, docks, and monitors can become the active output. Disconnect an unused headset or choose the intended speaker in your device’s audio settings. Play the test while looking at that output, then keep the connection unchanged for your session.
4. Rule out the custom sound
If a built-in tone works but an uploaded file does not, preview the file itself. Check for a quiet introduction, an unsupported format, or a temporary file reference lost during refresh. Reselect the original file. For microphone audio, make a new short recording and preview it before assigning it.
A media page URL may need an external player or an extra Play action. Test the studio’s backup tone independently. The custom sound guide explains the difference between files and streaming links.
5. Check whether the browser was running
If the test works while visible but the later alarm is silent, ask whether the device slept, the browser closed, or the tab was discarded. A countdown updating when you return is not evidence that its callback executed at the deadline. Keep the device awake for active browser timers and use a separate alarm for an important wake-up.
When reporting a problem, include the browser and device, whether the built-in test worked, whether the page remained visible, and whether you used speakers or headphones. Do not send private recordings or passwords. You can use our contact page with those observations.
Sources and further reading
These sources explain the underlying browser or data behavior. The setup examples above describe AlarmClock.live.
Continue exploring
Browse all guides · Choose a countdown · Browser reliability
Found a step that no longer matches your browser? Send us a correction.