If you searched for “chromebook kiosk mode” hoping to lock your own laptop into one app for a study session, the short version is: that’s not what it’s for. Kiosk mode is a Google Admin console feature for devices an organization owns and manages — school labs, store displays, library terminals. It runs exactly one app, and nobody signs in.
This guide covers what kiosk mode actually is, how IT admins turn it on, what it can and can’t control, and how it compares to Guest mode. Along the way we’ll flag where kiosk mode simply doesn’t apply — like if you’re on your own Chromebook and just don’t want to lose your open tabs, which is a completely different problem with a completely different fix.
What Is Chromebook Kiosk Mode?
Chromebook kiosk mode is officially defined as a session that runs a single Chrome or Android app, with nothing else accessible to whoever’s using the device. There’s no desktop, no other apps, no way to open a second browser window — the device does one job.
It exists for situations where you want a Chromebook to behave less like a general-purpose computer and more like a purpose-built appliance. Think a self-checkout screen, a digital sign, or a lobby check-in station. Whoever walks up to it gets the one app the organization configured, full stop.
Here’s the quick version for anyone trying to figure out if this even applies to them:
| Your situation | Does kiosk mode apply? |
|---|---|
| Personal, unmanaged Chromebook | No — kiosk mode isn’t available outside a managed organization |
| School- or work-issued Chromebook | Only if your IT admin turns it on and configures it |
| Retail, library, or event display device | Yes, once it’s enrolled and set up by an admin |
| You just want to focus in one app on your own device | Not kiosk mode — look at window management or a focus extension instead |
| You want to stop losing browser tabs on your daily-driver Chromebook | Not kiosk mode — that’s a session-saving problem, covered further down |
Who Can Turn On Kiosk Mode on a Chromebook?
Only an administrator, and only on a device already enrolled in that organization. Devices must be enrolled before an admin can turn on Kiosk Mode at all. It simply isn’t an option on a Chromebook you bought for yourself and signed into with a personal Google Account.
That enrollment requirement is the whole story of why kiosk mode feels invisible to most Chromebook owners. If you’ve never seen a setting for it in your own Settings app, that’s expected. It doesn’t live there. It lives entirely in the Google Admin console, which is the tool IT teams use to manage fleets of devices across a school district, a retail chain, or a company.
Because it depends on enrollment, kiosk mode also inherits whatever else comes with managed status — an admin can control updates, restrict settings, and see the device in their console. If you’re on a work or school Chromebook and something feels locked down that you didn’t expect, kiosk configuration is one of several admin-controlled behaviors worth asking your IT contact about, alongside things like disabled guest browsing or a fixed homepage.
How Do Admins Set Up a Kiosk App on a Chromebook?
Admins choose the kiosk app from the Google Admin console, not from the device itself. The exact path is Devices > Chrome > Apps & extensions > Kiosks, where an admin selects which Chrome or Android app auto-launches when the device starts.
The process has a few more decision points than just picking an app, especially if the deployment needs a specific ChromeOS version or tighter network controls.
- Confirm enrollment. The Chromebook needs to already be enrolled in the organization — kiosk configuration won’t show up as an option otherwise.
- Open Kiosks in the Admin console. Navigate to Devices > Chrome > Apps & extensions > Kiosks.
- Pick the app. Choose the Chrome or Android app that should launch automatically, or add a web-based option (more on that below).
- Adjust device settings if needed. Under Devices > Chrome > Settings > Device settings, an admin with Mobile Device Management privilege can pin a ChromeOS version or block standard auto-updates for kiosk devices specifically.
- Restart the device. Kiosk policy changes require a restart to take effect.
- Verify the policy applied. Check chrome://policy on the device to confirm the new kiosk configuration is live.
That last verification step matters more than it looks. Policy pushes from the Admin console aren’t always instant, and a device that hasn’t restarted yet will keep running its old configuration.
What Can Kiosk Settings Control?
Kiosk settings control which app runs, which URLs it can reach, and which ChromeOS version it’s allowed to update to. Beyond just picking the launching app, the Admin console gives IT teams a handful of levers specific to locked-down deployments.
URL Blocking is the one most admins reach for first. It lets you specify up to 1,000 allowed or blocked URL entries, which is how a kiosk browser session gets restricted to, say, one internal web tool instead of the open internet. That’s a meaningful limit to plan around if you’re configuring a device meant to reach dozens of internal subdomains. You’ll want to think in terms of patterns, not individual pages, to stay under it.
Version control is the other big one. From Devices > Chrome > Settings > Device settings, an admin can pin the ChromeOS version a kiosk app runs, or block the device from taking standard auto-updates altogether. Both require Mobile Device Management admin privilege, so this isn’t something a general IT helpdesk account can flip on its own.
What Happened to Chrome Apps in Kiosk Mode?
Chrome apps, the older packaged-app format, no longer work in kiosk sessions. Google phased them out of kiosk deployments the same way it phased them out of the broader Chrome Web Store, and organizations that depended on them had to migrate.
There was a grace period. Organizations could temporarily keep using Chrome apps in kiosk sessions specifically through an opt-in setting, but that only lasted up to ChromeOS version 151. If your fleet is still running an older kiosk app built on that format, it’s worth checking your current ChromeOS version against that cutoff before you assume it’ll keep working after the next update.
Check your kiosk app format before your next update cycle. If a kiosk deployment still relies on a legacy Chrome app and the fleet is approaching or past ChromeOS version 151, that app may stop launching. Confirm with your kiosk app vendor whether a web-based or Android replacement is available before devices update further.
This is a real migration headache for organizations with older kiosk fleets, especially ones running specialized software from a vendor that hasn’t updated its packaging. The practical fix isn’t a setting. It’s replacing the app itself with a supported format, which is exactly what the next section covers.
Can a Chromebook Kiosk Run Web Apps?
Yes, through Isolated Web Apps, which give kiosk deployments a supported path that isn’t tied to the deprecated Chrome app format. Admins add one by going to Add > Add an Isolated Web App in the kiosk configuration and entering the app’s web bundle ID.
This matters for any organization that built its kiosk experience around internal web tools rather than a native Android app. Instead of trying to wrap a website in something clunky, an Isolated Web App gets packaged with its own bundle ID and added directly to the list of apps a kiosk device can launch, alongside the standard Chrome and Android options.
This is still a fundamentally different thing from ordinary browsing. A kiosk running a web app doesn’t give the person standing at the device a normal browser with tabs, bookmarks, or an address bar. It opens that one specific app, full screen, and nothing else. For organizations weighing whether to go with a native app, a Chrome app they’re phasing out, or an Isolated Web App, that consistency is usually the deciding factor: whichever format, the end result on screen should look identical to the person using the device.
Kiosk Mode vs Guest Mode: What’s the Difference?
Kiosk mode locks a managed device to one pre-selected app; guest mode gives anyone a temporary, full browsing session with no sign-in required. They sound similar (both let someone use a Chromebook without an account) but they solve opposite problems.
| Kiosk mode | Guest mode | |
|---|---|---|
| Requires enrollment/management | Yes | No — works on personal devices too |
| Who configures it | An admin, in advance | Anyone, from the sign-in screen |
| What the user sees | One fixed app only | A regular, full browser session |
| What happens when the session ends | Restarts into the same app | Chrome deletes files, cookies, site data, and browsing activity |
| Typical use | Retail displays, library terminals, event check-in | Lending your device, quick sign-in-free browsing |
Guest mode starts from the sign-in screen by selecting “Browse as Guest,” and when that session ends, ChromeOS deletes the files, cookies, website data, and browsing activity tied to it. It’s a full browser, just a disposable one. Kiosk mode never opens a general browser at all. There’s no address bar to type into, no new tab to open.
One overlap worth knowing: on a managed Chromebook, an administrator can turn off guest browsing entirely, the same way they control kiosk configuration. If “Browse as Guest” is missing from a work or school device’s sign-in screen, that’s an admin decision, not a bug. For more on how guest sessions behave, our Chromebook guest mode guide covers what’s available and what isn’t once you’re in one.
What Are Common Uses for Chromebook Kiosk Mode?
Kiosk mode shows up wherever an organization wants a Chromebook to act like a fixed-purpose device instead of a general computer. The common thread is that whoever’s standing in front of it shouldn’t be able to do anything except the one task the device was set up for.
- Retail and signage. A store display or digital menu board that only ever shows one app or page, with no way for a customer to poke around the rest of the device.
- Libraries and public terminals. A catalog lookup station or research kiosk locked to a single search tool, often paired with URL Blocking so it can’t wander off to unrelated sites.
- Events and check-in. A registration or check-in screen running one form-style app, reset automatically between attendees.
Schools use it too, particularly for testing scenarios where a device needs to run one assessment app and nothing else for the length of an exam. The pattern is consistent across all of these: an admin decides in advance exactly what the device should do, and kiosk mode removes every other option from the person using it.
What none of these use cases involve is someone’s personal, everyday Chromebook — the one with a dozen browser windows open, a half-finished spreadsheet, and three tabs of research you were saving for later. Kiosk mode isn’t built to protect that kind of session; it’s built to eliminate the need for one in the first place.
What Should You Check If Kiosk Policies Aren’t Applying?
Start with a restart, then confirm the policy landed with chrome://policy. Kiosk configuration changes (a new app, an updated URL block list, a version pin) don’t take effect until the device restarts, so a policy that “isn’t working” is often just waiting for that reboot.
- Re-check the Admin console settings. Confirm the app, URL Blocking list, or device settings saved correctly under Devices > Chrome > Apps & extensions > Kiosks.
- Restart the device. Kiosk policy changes require a restart before they apply.
- Open chrome://policy on the device. This shows the policies currently in effect, so you can confirm the new configuration took hold rather than assume it did.
- Check admin privilege level. Version pinning and auto-update blocking specifically require Mobile Device Management admin privilege — a lower-privilege console account won’t be able to change those.
If everything checks out in chrome://policy but behavior still looks wrong, the issue is more likely the app itself — an Isolated Web App bundle ID that’s slightly off, or a Chrome app that stopped working after the ChromeOS version 151 cutoff — than the kiosk configuration path.
How Do You Protect Your Tabs on a Regular Chromebook?
Kiosk mode has nothing to do with this, and that’s the point worth landing on. If you’re reading this because you searched “kiosk mode chromebook” hoping it would keep your open tabs safe, it won’t — kiosk mode doesn’t manage tabs at all. It replaces your whole browsing session with one fixed app, which is the opposite of what you want if your problem is losing a window full of open work.
On a regular, unmanaged Chromebook, the built-in options for keeping your session alive are limited. Chrome’s “Continue where you left off” startup setting reopens your last windows, but it only helps if Chrome closes cleanly. It won’t save you from a crash mid-session, and it only ever remembers one state, not a history of them. There’s also no version history, so if you close the wrong window by accident, that specific set of tabs is just gone.
That gap is exactly what BelayTab covers, and it’s a fit for your day-to-day Chromebook, not a kiosk device an admin manages. It’s free, doesn’t need an account, and saves any open window as a named session with one click or Ctrl + Shift + S. It also snapshots every open window automatically on a five-minute timer and again when a window closes, keeps the last 20 versions of each session so restoring never overwrites your work, and holds deleted sessions in a 30-day trash. Everything (snapshots, deleted sessions, your browser’s recently closed windows, and export files) lives on one Recovery screen, so you’re not hunting across menus after something disappears.
If you manage a fleet of Chromebooks and kiosk mode is the right call for your public-facing devices, that’s a separate track entirely — handled in the Admin console, not by browser extensions. But for the laptop you work from every day, the two problems don’t overlap, and it’s worth having a real answer for both instead of hoping kiosk-mode terminology solves a tab-loss problem it was never built for.