Skip to main content

Differences Across Browsers

Chrome​

  • Activation: Kiosk mode in Chrome can be activated via command line arguments.
    • Windows: 
      "C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" --kiosk https://example.com
    • macOS: 
      /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --kiosk https://example.com
    • Linux: 
      google-chrome --kiosk https://example.com
  • Features: Runs in full-screen mode without the standard user interface elements. Provides a straightforward setup for single-page applications.
  • Session Management: Chrome does not include built-in session timeout or reset features in its kiosk mode. These functionalities typically need to be implemented through external scripts or third-party tools.
  • Extensions: Allows the use of extensions, which can be beneficial for customizing the kiosk experience.
  • Exiting: Typically requires closing the browser via keyboard shortcuts (Alt + F4 on Windows, Cmd + Q on macOS, Ctrl + W on Linux).

Edge​

  • Activation: Similar to Chrome, Microsoft Edge (Chromium-based) uses command line arguments.
    • Windows: 
      "C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe" --kiosk https://example.com
    • macOS: 
      /Applications/Microsoft\ Edge.app/Contents/MacOS/Microsoft\ Edge --kiosk https://example.com
    • Linux: 
      microsoft-edge --kiosk https://example.com
  • Features: Edge’s kiosk mode offers a full-screen experience without UI elements and supports Windows 10 Assigned Access for deeper kiosk functionality.
  • Session Timeout: Edge has a built-in session timeout feature that can automatically reset the session after a specified period of inactivity, which is useful for public kiosks.
  • Assigned Access: On Windows 10 and later, Edge can be configured using Windows' Assigned Access feature, allowing more control over the kiosk experience, including restricting access to specific apps and settings.
  • Exiting: Requires closing via keyboard shortcuts or administrative intervention.

Firefox​

  • Activation: Firefox does not have a dedicated kiosk mode flag but can be configured to run in full-screen mode and locked down.
    • Windows/Linux: 
      firefox -kiosk https://example.com
    • macOS: 
      open -a "Firefox" --args -kiosk https://example.com
  • Features: More limited compared to Chrome and Edge, but Firefox 71 and later support the --kiosk flag for easier setup. It relies on add-ons or configuration settings for full kiosk functionality.
  • Session Management: Does not include built-in session timeout or automatic reset features. These need to be configured using add-ons or custom scripts.
  • Customization: Requires more manual configuration and add-ons to achieve a kiosk experience comparable to Chrome and Edge.
  • Exiting: Exiting full-screen mode requires specific key combinations, such as F11.

Opera​

  • Activation: Similar to Chrome, as Opera is also Chromium-based.
    • Windows: 
      "C:\Program Files\Opera\launcher.exe" --kiosk https://example.com
    • macOS: 
      /Applications/Opera.app/Contents/MacOS/Opera --kiosk https://example.com
    • Linux: 
      opera --kiosk https://example.com
  • Features: Full-screen mode without UI elements. Integration and behavior similar to Chrome due to the shared Chromium base.
  • Session Management: Like Chrome, Opera does not have built-in session timeout features. Custom solutions are needed to handle session resets and timeouts.
  • Extensions: Supports extensions for added customization of the kiosk experience.
  • Exiting: Standard closing shortcuts (Alt + F4, Cmd + Q, etc.).

Safari​

  • Activation: Safari does not have a dedicated kiosk mode but can run in full-screen mode.
    • macOS: Safari can be set to full-screen mode by using Control + Command + F or by clicking the green full-screen button on the top left of the window.
  • Features: Limited to full-screen functionality. Kiosk-like behavior requires additional configuration through macOS parental controls or third-party solutions.
  • Session Management: Does not provide built-in session timeout or automatic reset features. These must be managed through macOS settings or third-party applications.
  • Exiting: Exiting full-screen mode requires Control + Command + F again or using the escape key if allowed.

Summary​

  • Chrome and Edge: Both browsers provide robust kiosk mode functionality through command line flags, offering a seamless full-screen experience without UI elements. Edge has additional Windows 10-specific features for kiosk setups.
  • Firefox: Offers a kiosk mode starting from version 71 using the --kiosk flag, but traditionally required more configuration and add-ons.
  • Opera: Similar to Chrome due to the shared Chromium base, offering easy kiosk mode activation through command line flags.
  • Safari: Lacks a dedicated kiosk mode, relying on full-screen functionality and additional macOS configurations for kiosk-like behavior. Safari's limitations make it less ideal for strict kiosk applications.