What is Chrome Kiosk Mode and How Do You Set It Up on Windows?

Chrome kiosk mode locks Google Chrome to a single website or application by hiding the address bar, tabs, and navigation controls. It’s ideal for use cases such as display signage, self-service terminals, and the like. If you are new to the feature, this guide explains what it is, its purpose, and how you can configure it securely.

Recommended deployment strategies:

Methods to set up your Chrome kiosk mode

Make sure you configure your Chrome kiosk mode smoothly by having these basic requirements in place before proceeding to the methods.

General prerequisites:

• Windows device with Google Chrome installed
• Local administrative access for configuration
• A defined kiosk URL or web application
• Optional management tooling for standardized deployment

Understand Chrome kiosk mode and its limitations

Configure Chrome kiosk mode correctly by first fully understanding what it is, what it can and can’t do. Here’s a short overview:

What is Chrome kiosk mode?

So, Chrome kiosk mode is a browser-level restriction that, when enabled, launches Chrome in a locked, full-screen state and hides UI elements such as navigation controls, tabs, and the address bar. This reduces clutter, prevents unintended interaction, and restricts the session to a single website or application.

Limitations of Chrome kiosk mode

However, kiosk mode has its limitations. It controls only the browser, not the device itself. It doesn’t replace user account controls or OS-level kiosk configurations, and it doesn’t lock down the operating system or restrict access to other applications.

Method 1: Enable Chrome kiosk mode using command-line flags

Using command-line flags is the simplest way to launch Chrome in kiosk mode, as it uses startup parameters. This method doesn’t require any device management or policy enforcement, so if you need single-device setups or temporary kiosks, this is the recommended solution.

Steps:

1. Create a desktop shortcut for Google Chrome. Here’s how:
   • Click the Win key and type Chrome.
   • In the results, right-click on Google Chrome and select Open file location.
   • In File Explorer, right-click Google Chrome > select Send to > Desktop (create shortcut).

Note: If there’s already an existing Google Chrome shortcut on the desktop, proceed to step 2.

2. Right-click the shortcut and select Properties.
3. In the Target field, append the following after the closing quote:

–kiosk https://example.com

4. Click Apply, then OK.
5. Double-click the shortcut to launch Chrome. It should open directly in kiosk mode for the specified URL.

Method 2: Configure Chrome kiosk mode for auto-launch

This method is essentially a continuation of Method 1, as it requires you to automatically launch Chrome in kiosk mode after every reboot. This is a necessary method if you intend to set up unattended or single-purpose systems, such as signage displays or self-service terminals.

Prerequisites:

• A Chrome kiosk shortcut configured using command-line flags (Method 1).
• A dedicated local user account for kiosk use.

Steps:

1. Press Win + R to open the Run dialog, type shell:startup for the kiosk users’ folder or shell:common startup for all users and press Enter to open the Startup folder for the current user.
2. Copy the Chrome shortcut into this folder.
3. Configure the device to automatically sign in to the kiosk user account. Here’s how:
   1. Press Win + R, type netplwiz, and press Enter.
   2. Select the kiosk account, clear Users must enter a username and password to use this computer, and enter the account password when prompted
   3. If the checkbox is missing, go to Settings > Accounts > Sign-in options, turn off the Windows Hello-only sign-in setting, and reopen netplwiz.
4. Restart the device and confirm that Chrome launches directly in kiosk mode.

Tip: Use a dedicated local user account to isolate kiosk activity and reduce risk.

Method 3: Manage Chrome kiosk mode through policy or MDM

What if you need to enforce multiple Chrome kiosk modes? Manual configuration on each device is time-consuming and not practical. In this case, using Chrome policies or Mobile Device Management (MDM) allows you to centrally manage kiosk mode across multiple devices. This approach is recommended for organizations where kiosk mode must be consistent and manageable at scale.

Steps:

1. Download the Chrome policy templates and add them to the policy definitions folder so the following Chrome settings appear in the editor.
2. Apply Chrome policies using Group Policy (gpedit.msc) or your MDM platform.
3. Configure the homepage and startup URLs for your kiosk site.
4. Block all URLs except your kiosk site using URLAllowlist and URLBlocklist to restrict navigation.
5. Turn off extensions, developer tools, printing, and other unnecessary features.
6. Launch Chrome in kiosk mode using startup flags (Method 1).

Startup flags control how Chrome launches. Policies control what Chrome can do after it’s launched. Make sure to combine them.

7. Restart the device or run gpupdate /force in the Command Prompt (Windows) to force policy sync.
8. Confirm that kiosk behavior is enforced correctly.

Method 4: Exit Chrome kiosk mode for maintenance

Once you’ve successfully set up Chrome kiosk mode, you’ll also want to know how to exit it and regain control for maintenance tasks such as updates or troubleshooting.

Steps:

1. Press Alt + F4 to close Chrome. If you’re using Chrome on macOS, press Command + Q to do the same.

Note: This works only if OS-level shortcuts aren’t blocked.

2. Press Ctrl + Alt + Del to open the security options.
3. Select Sign Out or Switch user to exit the kiosk session without terminating the system.
4. Go back to the desktop and log out of the kiosk user account. Then, sign in using an administrative or maintenance account.
5. Remove the kiosk shortcut from the Startup folder, or edit the shortcut to remove the –kiosk or –app flags to prevent Chrome from relaunching in kiosk mode after reboot.

Additional considerations

Keep these points in mind to ensure a smoother kiosk configuration and reduce potential risks.

Kiosk mode doesn’t lock the OS

As mentioned in the above sections, Chrome kiosk mode only restricts the browser interface; it doesn’t prevent OS-level access. This means that if users exit the kiosk account, they may still access the desktop or system settings.

Pair with a restricted local user account

Pair a browser kiosk with a dedicated, restricted local user account. This allows you to limit permissions and prevent access to system settings or apps, granting better control. If your kiosk is separate from your admin accounts, you can reduce risk and simplify recovery if anything goes wrong.

Restrict hardware keyboard shortcuts

Keyboard shortcuts like Alt + F4 or Ctrl + Alt + Del can disrupt kiosk mode; it’s recommended to disable or remap them. However, since they operate outside Chrome’s control, they may require separate OS-level restrictions.

Ensure network availability

Web-based kiosks depend on a stable internet connection. Because of this, network availability is critical as a network outage can render the kiosk unusable.

Post-update validation

Sometimes browser updates go unnoticed, but this is critical as updates can change behavior or reset certain settings. To avoid confusion or surprises, always test kiosk behavior after updates or policy refreshes.

Troubleshooting

Here are common issues that can occur while configuring your Chrome kiosk mode, along with quick solutions to resolve them.

Chrome doesn’t launch in kiosk mode

If Chrome is already running in the background, the kiosk shortcut may not start kiosk mode. Close all Chrome windows and background processes, then relaunch the shortcut.

Furthermore, this can also be due to incorrect flag syntax in the shortcut. Confirm that the kiosk flags (Method 1) are correctly appended to the Chrome shortcut target. The flags must appear outside the quotation mark. Here’s an example of how it should look:

Users can exit the browser

This may indicate that Chrome isn’t configured to auto-launch in kiosk mode after reboot. Check startup behavior to confirm.

Moreover, this can mean that keyboard shortcuts, such as Alt + F4, are still available, or the kiosk account has more permissions than it needs. Restrict system shortcuts and review account permissions to ensure kiosk accounts have limited access.

The site doesn’t load

Verify that the device has active network connectivity. It’s recommended to use wired connections for reliability. Also, check URL allowlists in policies to make sure the site isn’t blocked.

Keyboard shortcuts still work

This means system-level shortcuts outside Chrome haven’t been restricted. Remember, system escape paths must be restricted separately through account permissions or OS configurations. You may also consider disabling physical keyboards for public setups.

Updates change behavior

Revalidate flags and policies after major updates. Always test kiosk behavior to catch these changes early and ensure they don’t go unnoticed, preventing confusion and avoidable issues.

How NinjaOne helps manage Chrome kiosks

If you’re managing multiple kiosks, NinjaOne can simplify your process by automating configuration and monitoring. Here’s how:

For Android devices, NinjaOne Android Kiosk Mode helps lock mobile devices to a selected set of apps.

Ensuring smooth operations with Chrome kiosk mode

Chrome kiosk mode offers the quickest way to lock the browser into a single-purpose experience. Pair kiosk mode with a dedicated, restricted user account and centralized device management so the kiosk stays locked down and consistent. When set up correctly, it’s an effective solution for public access systems that rely on web applications.

Related topics:

• What Is a Digital Kiosk and How Does It Work?
• How to Set Up or Remove a Kiosk Account with Assigned Access
• Setting up kiosk mode
• What is iPad Kiosk Mode? A Guide to iPadOS Guided Access
• Android Kiosk Mode