Kiosk Mode: Complete Definition and Guide

What is kiosk mode?

Kiosk mode is a configuration of a computer, tablet, phone or screen player that locks it to a single application, shown full screen, with no access to the desktop, the settings, the file browser or any other program. The user can neither close the application, nor open another one, nor change the system. When the session ends, the device returns to its initial state.

The term comes from kiosks, but the technique applies to any device exposed to the public or left unattended: an interactive kiosk for ordering, a digital signage screen in a lobby, a visitor tablet in a museum, a clocking-in station in a workshop, a point-of-sale terminal, a reception screen in a practice. Every operating system offers a form of it: Linux with a dedicated session, Windows with Assigned Access, Android and iOS with their app-pinning modes.

Kiosk mode therefore turns ordinary hardware into a single-purpose device. That is what makes it possible to build a durable kiosk from a standard mini PC instead of buying proprietary equipment.

Why it matters

A device left to the public without a lock does not last a week. Kiosk mode answers five needs.

• Security: the user reaches neither the system, nor the internal network, nor the data of previous sessions. Keyboard shortcuts, ports and context menus are neutralised.
• Reliability: the application restarts by itself if it crashes, the device reboots every night, the session starts clean for each user. The service runs without an employee coming to "fix the screen".
• Cost: standard hardware, replaceable from any shop, instead of a proprietary kiosk sold with its subscription.
• Remote operations: the configuration is described once and applied to a whole fleet, updates are pushed from a central station, logs are collected without travelling.
• User experience: with no distraction and no pointless menu, the user sees the intended journey and nothing else.

How it works

Kiosk mode combines several locks, from the system down to the application. At the operating system level, the device boots straight into a dedicated session, under an account without administrative rights. On Linux, that session starts a minimal window manager and the application, with no desktop and no taskbar. On Windows, Assigned Access restricts an account to one application. On Android, a device managed in "owner" mode pins one application and hides the rest.

At the application level, full screen is enforced, exit shortcuts are disabled, navigation is restricted to the intended pages (in a browser in kiosk mode, the address bar disappears and external links are blocked). A watchdog monitors the process and relaunches it if it stops. A reset happens after each session or after a period of inactivity: cache emptied, temporary files deleted, back to the home screen.

Peripherals follow an explicit policy. A USB stick may be allowed but mounted in an isolated space, read-only, with no possible execution. The keyboard can be reduced to a numeric pad. The network is partitioned: the kiosk talks to the central platform and to nothing else.

Finally, operations: scheduled reboot at night, status monitoring (powered, reachable, application running, disk space), software and content updates from a central station, logs collected for diagnosis. On a fleet of ten or fifty devices, this layer matters more than the lock itself.

Concrete example

The self-service print kiosks KERN-IT operates for the copy service of a university cooperative have been running in kiosk mode for more than ten years. Each student opens a temporary, isolated session: the USB stick is read in a sealed-off space, the print job goes to the copier without the kiosk exposing the internal network, and everything is wiped at the end of the session. A nightly reboot puts every station back into a known state.

The same logic applies to the screens placed above the kiosks: a locked player that boots straight into its sequence of visuals, recovers on its own after a power cut and receives its new content remotely. Across two sites and several dozen devices, the configuration is written as replayable recipes: replacing a failed device means plugging in a new one and applying its recipe, with no manual set-up on site.

Implementation

1. Define what the user must be able to do, and therefore everything they must not: leave the application, plug in a peripheral, reach another address, print elsewhere.
2. Choose the system: Linux for a durable, remotely managed kiosk, Windows when a business application requires it, Android for a visitor or clocking-in tablet.
3. Lock in layers: unprivileged account, dedicated session, full-screen application, disabled shortcuts, USB and network policy.
4. Automate the reset: end of session, inactivity timeout, nightly reboot, automatic relaunch of the application.
5. Describe the configuration as code: a replayable recipe per device, to install, update or replace without manual work.
6. Supervise: state of each device, alerts when one goes silent, log collection. A device you cannot tell is working is a device that is down.
7. Test with the public: a week of pilot reveals the unexpected manipulations (a physical keyboard plugged in, a rotated screen, an escape attempt) that no review finds.

Associated technologies and tools

• Linux (Debian, Raspberry Pi OS): dedicated session with a minimal window manager, automatic start of the application, system services for relaunch and scheduled reboot.
• Chromium or Firefox in kiosk mode: full-screen browser with no interface, suited to kiosk and signage web applications.
• Windows Assigned Access: the kiosk mode built into Windows to restrict an account to one application.
• Android Enterprise (owner mode, app pinning): lock-down of professional tablets and phones.
• systemd and udev: automatic service relaunch, scheduled reboot, USB mounting rules on Linux.
• Ansible: replayable configuration recipes to install and maintain a fleet of devices remotely.
• Raspberry Pi and mini PCs: standard, inexpensive hardware for kiosks and signage players.

Conclusion

Kiosk mode is what lets an ordinary device survive the public: one application, a clean session every time, no access to anything else, and operations that do not depend on a passing employee. The lock itself is set up in a few days; what takes experience is the reliable reset, the peripheral policy and the administration of a fleet over years. KERN-IT implements these configurations for its clients' kiosks, screens and self-service devices, together with the kiosk software and the central platform behind it.