Why does the fullscreen clock go dark after a few minutes?

The Fullscreen API does not control screen sleep. The Screen Wake Lock API is a separate permission. Check the browser's address bar for a wake lock icon, or adjust the operating system's power settings.

Can a website force itself into fullscreen mode on load?

No. The Fullscreen API requires a user gesture, a click or keypress, to activate. A page cannot force fullscreen on load, and it cannot exit fullscreen without user interaction.

Does fullscreen mode keep the clock accurate?

Fullscreen mode affects display only. Accuracy depends on the operating system's clock, which syncs with time servers. The browser has no independent time source.

Why does the clock freeze when switching tabs?

Tab throttling. The browser reduces timer frequency in background tabs to save battery. The clock value is correct on return, but the visual update pauses. This is intentional browser behavior.

The screen still sleeps even with the wake lock active. What is wrong?

The wake lock is a request, not a guarantee. Some operating systems force sleep based on power settings that override the browser. The wake lock also releases when the page becomes hidden or the window loses focus. Check both page visibility and system power settings.

Fullscreen Live Clock

Most people assume that hitting the fullscreen button on a clock page also keeps the screen awake. It does not. The Fullscreen API and the Screen Wake Lock API are two separate systems, and confusing them causes the most common frustration with live clocks. Here is how the fullscreen clock display actually works, how to set it up correctly, and what to do when it misbehaves.

How to enter fullscreen mode

Click the fullscreen button on the clock. That is it. The browser needs a user gesture, a click, a tap, or a keypress, to enter fullscreen. This is a hard rule in the Fullscreen API. A website cannot force itself into fullscreen mode when the page loads, and it cannot do it silently in the background. You must click something first.

On a laptop, the F11 key often works as a shortcut. On a Mac, hold the Option key and click the green traffic-light button. Mobile is less predictable.

What the fullscreen clock shows

The fullscreen clock shows the current local time, taken from the operating system's clock. The browser does not have its own time source. It asks the operating system. The operating system syncs with time servers periodically. If the system clock is wrong, the fullscreen clock is wrong.

You see hours, minutes, and seconds. Some layouts include milliseconds. The display updates at the screen's refresh rate, typically 60 times per second. The number is a reference, not a precision instrument. Display resolution is not accuracy. The rendering pipeline adds variable latency, typically 16 to 50 milliseconds depending on frame timing. The number may show three decimal places and still be 50 to 200 milliseconds behind real time.

Keeping the screen awake during fullscreen

Entering fullscreen mode does not prevent the screen from dimming or locking. A presentation timer, a countdown for an exam, or a clock on a wall-mounted display will go dark if the system sleeps.

The Screen Wake Lock API is a separate permission. It tells the device to keep the screen on while the page is visible. The clock may request it automatically when you enter fullscreen. Verify it is active. Some browsers show an icon in the address bar. On others, click the page and look for a prompt.

If the screen still sleeps, check two things. First, is the page actually visible? The wake lock releases the moment you switch tabs or the window loses focus. Second, check the operating system's power settings. The wake lock cannot override a hard system setting that forces sleep after a fixed period. It is a request, not a command.

Multi-monitor fullscreen clock

A second monitor running a fullscreen clock is a common setup for streamers, teachers, and anyone who needs a glanceable time display. The clock fills the second screen while work happens on the primary one.

Open the clock on the monitor intended for the display. Enter fullscreen mode. The clock stays on that screen. Move the mouse back to the main display and continue working. The wake lock applies only to the page, not the monitor. Check the power settings for that second display. Some operating systems allow different sleep timers per monitor. Use that.

For a permanent setup, a dedicated guide covers putting a clock on a second monitor in more detail.

Exiting fullscreen mode

Press the Escape key. That is the universal exit. On a device without a keyboard, look for an "Exit Fullscreen" button in the page controls, or swipe down from the top of the screen to access the tab view.

On mobile, exiting can be less intuitive. The browser may require a tap on the address bar area or a system gesture. If stuck, close the tab entirely and reopen the clock.

Fullscreen clock not working: troubleshooting

The most common issue: the clock went fullscreen, then the screen went dark anyway. That is the wake lock failing, not fullscreen failing. Re-read the section on keeping the screen awake.

If the clock will not enter fullscreen at all, check the browser settings. Some browsers block the Fullscreen API for specific sites. Look for a padlock or information icon in the address bar, open site permissions, and set "Fullscreen" to "Allow."

A frozen clock is likely tab throttling. Browsers slow down background tabs to save battery. The clock value is correct when you return, it recalculates from system time, but the visual update pauses. This is by design, not a bug.

Which browsers support fullscreen clocks?

The Fullscreen API works across all major desktop browsers. Mobile support is inconsistent. iOS Safari had a delayed implementation. On some Android phones, fullscreen mode hides the address bar but leaves status icons visible. On iPhones, adding the clock to the home screen and launching from there may give a truer fullscreen experience.

The Screen Wake Lock API is more recent. Chromium-based browsers have supported it since 2020. Safari added it later. On an older browser or a mobile device with strict power management, the wake lock may silently fail. There is no way for the page to force it.