The hotel reception clock showed 3:47 PM for six weeks before anyone noticed. The front desk staff had stopped seeing it, the maintenance crew assumed it was decorative, and the guests who checked their watches against it were quietly adjusting their own timepieces to match a clock that was wrong. That is what happens when you install a lobby screen without thinking about what it means to run a display unattended for months. The lobby clock is not a gadget. It is infrastructure, and infrastructure fails in predictable ways.
A kiosk clock display is a screen running a browser locked to a single clock page. No address bar. No tabs. No way for a passerby to navigate away. The machine boots, the browser launches, the clock appears, and nothing else is reachable. That is the whole job.
The hardware barely matters. A small form-factor PC, a mini computer behind the panel, an old laptop with the lid open, a tablet on a stand: any of them will run a clock for years. What matters is that the software starts unattended and stays put. That separates a kiosk clock from someone opening a browser and pressing F11, which lasts until the first restart.
The steps below cover launching a browser in kiosk mode, stopping the screen from sleeping, avoiding burn-in on a panel that never changes, and making the whole thing survive months without anyone touching it. The steps are the same whether you are setting up one screen in a dental office or twenty across a corporate campus.
What a kiosk clock display does
A kiosk clock display is a dedicated screen showing nothing but the current time, running in a locked-down browser session. The "kiosk" part is not about the enclosure or the stand. It is about the software configuration that prevents anyone from leaving the page, opening a new tab, or closing the window.
The clock page itself is deliberately boring. It shows large digits, maybe the date, possibly the seconds. There are no controls, no navigation, no settings gear to click. The page is the entire experience, and the experience is just the time, readable from across the room.
The use cases are everywhere. Hotel lobbies, office reception desks, medical waiting rooms, gym floors, factory floors, exam halls, police station waiting areas, and broadcast studios all have a version of this problem: people need to know the time, and the person who would normally check their phone is too far from their phone or too busy to look.
A kiosk clock display solves that with zero interaction. Nobody touches anything. The clock is just there, always on, always right.
Hardware that works for a kiosk clock display
The Raspberry Pi is the workhorse of the kiosk world. A Pi 4 or Pi 5 with 2GB of RAM is plenty for a clock page. The Pi boots from a microSD card or USB drive, launches the browser in kiosk mode, and sits there drawing about 5 watts. The only real risk is the SD card wearing out from constant writes. Mitigate it by using a high-endurance card or booting from a USB SSD.
An old laptop works when you already have one. The screen is built in, the keyboard and trackpad are attached, and the whole thing can sit on a shelf behind the display. The main problems are heat and the lid. A laptop that runs 24/7 with the lid closed needs the lid-close action set to "do nothing" in the power settings, or it will sleep the moment someone shuts it. And a laptop that runs hot for months will eventually cook its own battery. Remove the battery if it is removable and run on AC power only.
A dedicated mini PC is the most expensive option and the least likely to surprise you. These are small form-factor computers designed to run unattended. They have no battery, no screen, no keyboard, and no moving parts beyond a fan. Choose one when the clock display is part of a larger installation that already has infrastructure.
A TV screen is the display itself. Consumer TVs are cheap, bright, and available everywhere. The problem with TVs is the built-in smart features. A "smart" TV wants to show you its own home screen, update its own firmware, and occasionally refuse to wake from standby. For a kiosk display, a "dumb" monitor with no smart features is actually better. Or use a TV with the smart features turned off and the input locked to the HDMI port the Pi is connected to.
Step 1: Configure the device for kiosk mode
Start the browser with the kiosk switch and the fullscreen clock address. Store that address in a CLOCK_URL environment variable, then launch Chrome or Edge with:
chrome --kiosk "$CLOCK_URL"
That opens fullscreen with no interface and ignores most attempts to leave the page. Firefox has a similar mode with --kiosk. The exact flag depends on the browser and version, so check the documentation for the specific build you are using.
Kiosk mode is not the same as fullscreen. Fullscreen mode is what you get when you press F11: it hides the browser chrome but still allows Alt+Tab, Ctrl+T, and the usual escape hatches. Kiosk mode is a hard lock. The browser takes over the display, and there is no way out without killing the process, which requires a keyboard shortcut that the kiosk configuration can block.
For a clock display, kiosk mode is the right level of lockdown. Nobody needs to do anything except look at the time. If a visitor somehow manages to exit the clock, the installation has failed.
Step 2: Auto-launch the fullscreen clock on boot
A kiosk clock that requires someone to log in and start the browser is not a kiosk clock. It is a computer that happens to have a clock on it. The entire point of a kiosk is that it comes up on its own, without human intervention, after a power cut.
Add the kiosk command to the machine's startup items, a scheduled task at logon, or a systemd user service on Linux. The exact mechanism depends on the operating system, but the principle is the same: when the machine boots, the browser starts, and the clock appears.
On Windows, press Win+R, type shell:startup, and drop a shortcut to the kiosk command in the Startup folder. On Linux with systemd, create a user service file that runs the browser command. On macOS, add a login item in System Preferences.
The critical part is auto-login. A kiosk that stops at a password prompt after a reboot is not unattended. Configure the operating system to log in automatically to a dedicated restricted account. The account should have no password, no network shares, and no access to anything sensitive. It exists solely to run the clock.
Step 3: Prevent screen sleep and burn-in
Turn off sleep, screen blanking, and the screensaver at the operating system level rather than relying on the page. A kiosk clock display that has gone dark is indistinguishable from a broken screen, and nobody in a lobby will move the mouse to wake it.
Set the display timeout to never, turn off the screensaver, and on a laptop set the lid-close action to do nothing if the lid will be shut. On Windows, change the power plan to never turn off the display. On Linux, turn off DPMS (Display Power Management Signaling) and the screensaver daemon. On macOS, set "Prevent automatic sleeping when the display is off" and turn off the screensaver.
The Screen Wake Lock API is a useful second line of defense. A page can request a screen wake lock, and the system will hold the display on while the page is visible. It is not a substitute for the system settings on a permanent installation, because the lock is released whenever the page is hidden, and a browser crash takes it with it.
Assume burn-in will happen on OLED and plan around it. Organic light-emitting diode panels degrade with use, and a static clock face is exactly the kind of image that causes permanent ghosting. If you must use an OLED panel, run light on dark, reduce the brightness, enable pixel shifting if the panel supports it, and accept that the display has a finite life measured in months rather than years.
Ordinary LCD and LED-backlit panels are not meaningfully susceptible to burn-in, which makes them the safer choice for a screen that will show one thing forever. The trade-off is that LCDs have worse contrast and viewing angles, but for a clock in a lobby, that rarely matters.
Step 4: Connectivity and power-recovery considerations
A kiosk clock display needs a connection to sync its time, and it needs the power to come back on after an outage. Both of those are usually automatic, but both have failure modes worth planning for.
The browser clock gets its time from the operating system, which syncs via NTP (Network Time Protocol) to a time server. If the connection is down, the clock keeps running on the local hardware clock, which drifts by a few seconds per month. That is fine for a lobby clock. It is not fine if the clock is used for anything time-sensitive, so make sure the device has a wired Ethernet connection or a stable Wi-Fi signal.
Power recovery is about the BIOS settings. Most machines have a setting for what happens when AC power is restored. The options are usually "power off," "power on," and "last state." Set it to "power on" so the machine boots itself after an outage. If you leave it at "power off," the kiosk will stay dead until someone presses the power button, which defeats the purpose of an unattended installation.
A UPS (uninterruptible power supply) is optional but recommended. A small UPS will keep the kiosk running through brief outages and give it a clean shutdown for longer ones. For a single clock, the cost is probably not worth it. For a lobby that runs 24/7, it might be.
Raspberry Pi specific setup steps
The Raspberry Pi is the most common kiosk clock platform, so it deserves its own section. Start with Raspberry Pi OS Lite (no desktop) and install a minimal X server and a browser. The default Chromium build works fine, but the kiosk flag is slightly different from the desktop version.
The key file on the Pi is /etc/xdg/lxsession/LXDE-pi/autostart or a systemd service, depending on how you want to launch the browser. The simplest approach is to create a systemd user service that runs the kiosk command, enable it with systemctl --user enable, and set the user to auto-login.
The Pi's SD card is the weak point. Flash memory has a finite number of write cycles, and a browser writing cache files constantly will wear out a cheap card in months. Use a high-endurance card rated for dashcam or surveillance use, or better yet, boot from a USB SSD. The performance difference is negligible for a clock, but the reliability difference is enormous.
TV screen display setup
A TV used as a kiosk display needs its settings adjusted before you mount it. Turn off the sleep timer, turn off the screensaver, and set the picture mode to a preset that does not process the image. Most TVs have a "game mode" or "PC mode" that turns off the motion smoothing and other processing that adds input lag and can make text look soft.
Set the TV to the correct HDMI input as the default. Some TVs will boot to their own smart home screen and never switch to the input, which means the clock is there but invisible. If the TV has a "power on" setting, set it to "last state" or "always on" so it comes back to the right input after a power cut.
Turn off the TV's own Wi-Fi and networking. A smart TV that updates its firmware in the middle of the night and reboots into a new interface is a clock that is broken. The TV should be a dumb monitor, and the Pi should do all the thinking.
Running a kiosk clock display unattended for months
A kiosk clock display should run for months without anyone touching it. That means the system needs to be self-healing, and you need a way to check on it without visiting the lobby.
Configure the browser to reload the page periodically in case it crashes or the JavaScript engine runs out of memory. A page reload every 24 hours is usually enough. The --kiosk flag in Chrome has a --remote-debugging-port option that lets you see the page from another machine, but for a simple clock, a cron job that restarts the browser daily is simpler and more reliable.
Watchdog scripts that restart the browser if it crashes are a good idea. A simple shell script that checks if the browser process is running and starts it if not, run every minute from cron, is enough to make the kiosk self-healing.
The operating system itself will eventually need updates, but automatic updates on a kiosk are risky. An update that requires a reboot will take the clock down at the worst possible moment. For a clock, the safest approach is to turn off automatic updates and apply them manually when someone is physically present to deal with problems.
Troubleshooting common kiosk issues
The clock is not showing. Check the basics first: is the monitor on, is the HDMI cable seated, is the Pi getting power? The most common kiosk failure is a loose cable or a monitor that went into standby and never woke up.
The clock is showing the wrong time. The system clock is probably out of sync. Check that NTP is running and that the device can reach the time server. If the connection is down, the clock will be wrong until it comes back.
The clock is showing but the display is dark. The screen is probably sleeping or blanking. Check the power settings and make sure the display timeout is set to never. The Screen Wake Lock API only works while the page is visible, so if the system blanked the screen, the page cannot prevent it.
The browser crashed and will not come back. The watchdog script should handle this. If it does not, check the logs and make sure the script is running. A browser that crashes on a kiosk is rare, but it happens, and the system needs to recover on its own.
The clock is showing but it is wrong by minutes. The hardware clock is drifting, and NTP is not correcting it. Check that NTP is configured and that the time server is reachable. If the device has no connection, the clock will drift, and there is nothing you can do about it except connect the network.