Browser-based timers are convenient precisely because they require no installation, but they depend on your browser and device behaving correctly. When something goes wrong, the fix is usually simple once you know where to look. This guide covers the ten most common issues people encounter with online timers, alarms, and clocks, along with the exact steps to resolve each one.
1. My alarm did not go off
This is the most frequently reported issue with any browser-based alarm clock, and the cause is almost always the same: the browser tab was closed, the browser was quit, or the device went to sleep before the alarm time. Browser-based alarms can only fire while the tab remains open and active. This is a fundamental browser security restriction that applies to every website, not just ScreenTimer.
The fix: pin the ScreenTimer tab in your browser so it stays open even when you close other tabs. On mobile, keep the browser in the foreground or enable “keep screen on” in your device settings. For mission-critical alarms like morning wake-ups, always use your phone’s built-in alarm as the primary and the browser alarm as a backup.
2. The timer sound is not playing
Modern browsers block audio playback until the user has interacted with the page at least once. If you open ScreenTimer and immediately start a timer without clicking anything on the page, the browser may silently block the alarm sound when the timer ends.
The fix: click anywhere on the ScreenTimer page before starting your timer. This registers a “user gesture” that unlocks audio playback for the session. Also check that your device volume is turned up and not muted. On mobile, ensure your phone is not in silent or vibrate mode, as this can suppress browser audio on some devices.
3. The timer resets when I refresh the page
Countdown timers and stopwatch sessions run in your browser’s memory. Refreshing the page clears this memory and resets the timer to its starting state. This is expected behavior for a browser-based tool. Your saved alarms, world clock cities, event countdowns, and preferences are stored in localStorage and survive page refreshes, but active countdown and stopwatch sessions do not.
The fix: avoid refreshing the page while a timer is running. If you accidentally refresh, you will need to restart the timer. For long-duration timing, the Event Countdown tool counts down to a specific date and time, so it automatically recalculates the remaining time even after a page refresh.
4. My phone screen keeps going dark and the timer stops
Most phones automatically turn off the screen after a period of inactivity to save battery. When the screen turns off, the browser may suspend or slow down JavaScript execution, causing timers to drift or stop entirely.
The fix: adjust your phone’s screen timeout setting. On iPhone, go to Settings, Display and Brightness, Auto-Lock, and select Never (or a longer duration). On Android, go to Settings, Display, Screen Timeout, and increase it. If your phone supports it, enable a “Stay Awake” or “Keep Screen On” option in Developer Settings. Plugging your phone into a charger while using the timer prevents battery drain during extended sessions.
5. The timer seems inaccurate or drifts over long periods
Browser-based timers use JavaScript timing functions that are generally accurate to within a few milliseconds for short durations. However, over very long periods (multiple hours), minor drift can accumulate. Additionally, if your device is under heavy CPU load from other applications, JavaScript execution may be delayed, causing the timer display to update less frequently.
The fix: ScreenTimer uses Date.now() calculations rather than simple interval counting, which self-corrects for drift on each tick. If you notice drift, close unnecessary browser tabs and applications to reduce CPU competition. For timing needs where absolute precision matters over many hours, a hardware timer or phone alarm is more reliable than any browser-based solution.
6. The world clock shows the wrong time for a city
This is extremely rare because ScreenTimer uses your browser’s built-in Intl API for timezone calculations, which draws from the IANA timezone database maintained by international standards organizations. The most likely cause of incorrect times is an outdated browser that has not received timezone database updates.
The fix: update your browser to the latest version. Chrome, Firefox, Safari, and Edge all include timezone database updates in their regular releases. Also verify that your own device’s system clock is set correctly, since the world clock calculates other city times relative to your local system time.
7. The fullscreen mode is not working
Some browsers restrict fullscreen mode on certain devices or in certain contexts. iPhones running Safari do not support the Fullscreen API for web pages. Some corporate-managed browsers have fullscreen disabled by IT policy.
The fix: on iPhone, the closest alternative is to add ScreenTimer to your home screen via Safari’s Share menu and select “Add to Home Screen.” This opens the site in a standalone window without browser chrome, which is nearly equivalent to fullscreen. On desktop browsers, try pressing F11 for browser-native fullscreen if the in-page fullscreen button does not respond.
8. My saved alarms and world clock cities disappeared
ScreenTimer saves all persistent data (alarms, world clock cities, event countdowns, preferences) in your browser’s localStorage. If you clear your browser data, use incognito or private browsing mode, or switch to a different browser, your saved data will not be available.
The fix: avoid clearing browser data for screentimer.net/ specifically. Do not use incognito mode if you want data to persist. If you use multiple browsers, pick one as your designated ScreenTimer browser and use it consistently. There is currently no account system or cloud sync, so data exists only in the specific browser on the specific device where it was created.
9. The timer looks different or broken on my device
ScreenTimer is designed to work on all modern browsers, but very old browsers or browsers with aggressive content blocking may display elements incorrectly. Ad blockers occasionally interfere with the page layout even though ScreenTimer’s timer functionality does not depend on ads.
The fix: try disabling your ad blocker for screentimer.net/ to see if the layout issue resolves. Update your browser to the latest version. If using an embedded browser within another app (like opening a link from within a social media app), try copying the URL and opening it directly in Chrome, Safari, or Firefox instead.
10. The Pomodoro timer does not ring during my break phase
If you switch away from the ScreenTimer tab during a Pomodoro session and your browser aggressively throttles background tabs, the timer may not fire its alarm at the exact moment the phase ends. Most modern browsers throttle JavaScript in background tabs to save resources.
The fix: enable browser notifications in ScreenTimer's Preferences. Even when the tab is throttled, browser notifications can still fire through the operating system. On Chrome, click the lock icon in the address bar, find Notifications, and set it to Allow for screentimer.net/. The Pomodoro timer will then send a system notification when each phase ends, even if the tab is in the background.
Still Having Issues?
If none of the above solutions resolve your problem, try these general steps: clear your browser cache (but not cookies or localStorage if you want to keep saved data), restart your browser, and try accessing ScreenTimer in a different browser. Most issues are browser-specific rather than tool-specific. You can also reach out at contact@screentimer.net with a description of the issue, your browser name and version, and your device type.
Leave a Reply