How the Firefox --kiosk Flag Locks Down Public Displays
This article provides an overview of how launching the Mozilla
Firefox web browser with the --kiosk command-line flag
secures the user interface for public displays and interactive
terminals. By stripping away navigation controls, enforcing full-screen
mode, suppressing menus, and disabling specific keyboard shortcuts, the
kiosk mode ensures users stay confined to a designated web application
without accessing the underlying browser settings.
Full-Screen Enforcement and UI Removal
When Firefox is launched with the --kiosk flag, it
immediately boots into a locked full-screen mode. All standard user
interface elements—often referred to as the "browser chrome"—are
completely removed from the screen.
Specifically, the following elements are hidden:
- The address bar and search bar.
- The tab strip and new tab button.
- Navigation buttons (Back, Forward, Reload, Home).
- The bookmarks toolbar and sidebar.
- The main application menu (the hamburger menu).
- The operating system's window controls (Minimize, Maximize, and Close buttons) and taskbars.
This ensures that a user walking up to a public terminal can only interact with the content of the webpage itself, with no visual tools available to navigate away from the intended URL.
Restricted Keyboard Shortcuts
Hiding the visual interface is only effective if users cannot use a
physical or on-screen keyboard to bypass the restrictions. The
--kiosk flag disables the vast majority of standard browser
keyboard shortcuts.
The following critical shortcuts are blocked in kiosk mode:
- F11: Disabled so users cannot toggle out of full-screen mode.
- Ctrl+T and Ctrl+N: Blocked to prevent opening new tabs or new browser windows.
- Ctrl+W: Disabled to prevent users from closing the current active tab, which would leave them with a blank, unusable screen.
- Ctrl+L, Alt+D, and F6: Disabled so users cannot focus on a hidden address bar to type a new URL.
- Ctrl+H, Ctrl+J, and Ctrl+B: Blocked to prevent access to browsing history, downloads, and bookmarks.
- F12 and Ctrl+Shift+I: Disabled to stop users from opening the Developer Tools to manipulate the webpage's code or view network activity.
Context Menu and Status Bar Suppression
In a standard browsing session, right-clicking anywhere on a page
opens a context menu that allows users to navigate backward, reload the
page, save images, or view the page source. The --kiosk
flag completely disables the default browser right-click context
menu.
Additionally, when a user hovers over a hyperlink in a normal browser window, a small status overlay appears in the bottom-left corner displaying the destination URL. Kiosk mode suppresses this status bar, keeping the underlying web architecture hidden from the public user.
Implementing the Kiosk Flag
Executing this lockdown requires launching Firefox via a command-line interface, terminal, or a modified desktop shortcut. The basic syntax is:
firefox --kiosk https://example.com
To pair the kiosk mode with a private browsing session—ensuring that cookies, cache, and session data are wiped when the browser eventually closes—administrators can combine flags:
firefox --kiosk --private-window https://example.com
For the --kiosk flag to work properly, all existing
instances of Firefox must be closed before running the command. If
Firefox is already running in the background, executing the command will
simply open a new tab in the existing, unlocked browser session.
System-Level Limitations
While the --kiosk flag successfully locks down the
Firefox interface, it only controls the browser application, not the
host operating system. Operating system shortcuts like
Alt+F4 (which closes the application), Alt+Tab
(which switches windows), Ctrl+Alt+Del, and the
Windows key remain active. Administrators deploying public
displays must combine the Firefox --kiosk flag with
operating system-level restrictions—such as Windows Assigned Access or a
restricted Linux window manager—to achieve a completely tamper-proof
environment.