Flamingo Raises $4.5M Seed Round

Skip to content

iPad kiosk mode: how to lock an iPad to one app or website

Technology
IT Operations
Aliaska VarievaAliaska Varieva
October 6, 2026
243 views
iPad kiosk mode: how to lock an iPad to one app or website

How to put an iPad in kiosk mode on iPadOS 27 with Guided Access or Single App Mode, lock Safari or Chrome to one website, supervise iPads and set App Lock through an MDM or Apple Configurator, keep kiosk iPads updated with declarative software updates, a check-in kiosk checklist, and how Chrome and Windows kiosks compare.


iPad kiosk mode locks an iPad to one app or one website, either with Guided Access, which you set on the iPad with a passcode, or with Single App Mode, which an MDM or Apple Configurator pushes to a supervised iPad. A check-in iPad at a front desk and a menu board in a lobby both need that lock, and who holds the exit decides which one fits. This guide covers both setups step by step on iPadOS 27, how to lock an iPad to one website, the MDM side for a fleet, where kiosk iPads break and how Chrome and Windows kiosks compare.

TL;DR

  • One iPad. Turn on Guided Access in Settings, Accessibility. It needs no MDM and no supervision, and anyone with the passcode can end it.
  • A fleet. Supervise the iPads through Automated Device Enrollment or Apple Configurator, then push App Lock, the payload behind Single App Mode, from the MDM. The exit lives on the server.
  • One website. Lock Safari or Chrome with either method, then limit it to an allow list or open the site as a full-screen Web Clip.
  • Updates. Plan a monthly maintenance window. On iPadOS 27, OS updates run only through declarative software update settings.

Guided Access vs single app mode

Two features get called iPad kiosk mode, and they are not the same lock. Guided Access is an accessibility setting. Apple describes it as a way to "temporarily restrict your device to a single app", with a passcode, optional Face ID or Touch ID to end the session, and controls for hardware buttons, keyboard, touch areas and a time limit.

Single App Mode is the managed version. It works only on supervised iPads, and an MDM server turns it on through the App Lock payload. The app stays in the foreground with no exit, and only an MDM command or a changed profile ends it. SimpleMDM's guide (updated May 2025) covers the same ground, and our Apple MDM comparison covers which tools can push it.

The practical difference is who holds the exit. With Guided Access, anyone who knows the passcode can end the session at the device. With Single App Mode, the exit lives on the server.

Guided AccessSingle App ModeAutonomous Single App Mode
Set onThe iPad, in SettingsAn MDM, or Apple Configurator over USBThe app itself, with MDM permission
Needs supervisionNoYesYes
Who ends itAnyone with the passcode, Face ID or Touch IDThe MDM or Apple ConfiguratorThe app, when its session ends
FitsOne or two iPadsA kiosk fleetExam, point-of-sale and intake apps

How to put an iPad in kiosk mode with Guided Access

Guided Access suits one or two iPads, a display unit or a trade show stand. Per Apple's iPad User Guide for iPadOS 27, the setup is short:

  1. Open Settings, tap Accessibility, then tap Guided Access and turn it on.
  2. Tap Passcode Settings, set a Guided Access passcode, and choose whether Face ID or Touch ID can also end a session.
  3. Tap Display Auto-Lock and choose how long the screen stays on during a session.
  4. Open the app you want to lock, then triple-click the top button on an iPad with Face ID (the Home button on other models). Asking Siri to "Turn on Guided Access" works too, and so does Control Center if you added Guided Access there.
  5. Circle any screen areas that should ignore touch, open Session Settings to block the top button, volume buttons, motion, keyboard or touch, or to set a time limit, then tap Done and Start.

To end a session, triple-click the same button and enter the passcode, or use Face ID or Touch ID if you turned that option on. Apple's enterprise notes for iPadOS 27.2 list a fix for iPads with a Home button that couldn't exit Guided Access, so update older kiosk iPads before you count on the exit.

The limit is scale. Each iPad is configured by hand, and nothing stops a staff member who knows the passcode from ending the session. That is fine for a display table and a poor fit for forty iPads across three sites.

How to lock an iPad to one website

Locking an iPad to one website is the common request. One r/ipad thread, "PSA: How to lock an iPad to a single website or app (kiosk mode) without buying expensive extra hardware", covers the do-it-yourself route.

On a single iPad, open the site in Safari, start Guided Access and circle the address bar and tab controls so they ignore touch. Visitors can still follow links on the page itself, so check where those links lead before the iPad goes on the counter.

On supervised iPads, the MDM handles it in two parts. The Web Content Filter payload has a Specific Web Sites Only list that limits browsing to the sites you add and shows them as bookmarks, and App Lock then pins Safari so nobody leaves it. Apple's notes on the list matter for kiosks: sites ending in .apple.com and .icloud.com always stay reachable, a URL that redirects needs its redirect target added too, and the http and https versions of a site may need separate entries.

A Web Clip payload gives a cleaner screen. With its full-screen option set, the clip opens the site as a full-screen web app with no address bar, and Safari controls appear only when someone navigates away from the clip's URL. Pair it with the allow list above so links out of the page stay blocked too.

Chrome kiosk mode on an iPad

The --kiosk switch is a desktop launch flag, and Chrome on an iPad has no equivalent. The lock comes from Guided Access or App Lock on the Chrome app, and the site list comes from Chrome's own policies. URLBlocklist and URLAllowlist both support Chrome on iOS from version 98, per Google's policy list, so blocking * and allowing the kiosk domain gives the same result as a Safari allow list.

Google's Chrome Enterprise Core pushes those policies to iPads through an MDM that supports AppConfig, and chrome://policy on the iPad shows whether they arrived. If the client doesn't use Chrome Enterprise Core, Google's URL blocking guide says to have the MDM vendor configure the policies instead.

Single app mode through MDM

For a fleet, supervise the iPads and push the lock from the MDM. The video below shows the device side of Single App Mode.

The flow is the same in every MDM: enroll the iPad as supervised, assign the app, then push the App Lock payload. A second option is Autonomous Single App Mode, where an approved app locks the device itself, which suits point-of-sale and exam apps that need to unlock between sessions.

Plan the exit before you deploy. Because the MDM owns it, every maintenance task, from a new app version to a Wi-Fi change, becomes a managed step instead of a quick fix at the device.

Supervise the iPads first

App Lock needs supervision, and Apple's deployment guide lists two ways to get it. iPads enrolled through Automated Device Enrollment are supervised automatically (iPadOS 13.1 or later), which is the route for iPads that sit in Apple Business, the free service that replaced Apple Business Manager in April 2026. iPads bought elsewhere can be supervised by hand in Apple Configurator for Mac over USB, which erases the iPad.

Apple Configurator can also start Single App Mode with no MDM at all. Select the supervised iPad, choose Actions, Advanced, Start Single App Mode, then pick the app and its options. The same menu has Stop Single App Mode for when the iPad comes back in, so this suits iPads that return to the office that set them up. To confirm supervision on any iPad, open Settings, where a supervised iPad says "This iPad is supervised" under the search field.

What the app lock payload controls

App Lock opens the chosen app, blocks every other app and reopens the app after a restart, per Apple's App Lock reference. Its options can switch off touch, the volume buttons, the ringer switch, auto-lock, screen rotation and the Sleep/Wake button, which stops visitors from putting the iPad to sleep or turning it off.

Accessibility features such as VoiceOver, Zoom and AssistiveTouch can stay available through a triple-click, so a kiosk doesn't lock out the people who need them. Only one App Lock payload can sit on a device, and each MDM labels these switches its own way, so check the vendor's names against Apple's list.

Where kiosk iPads break

The lock that keeps users out can also keep updates out. SimpleMDM's guide says apps cannot be updated while a device is in Single App Mode, so you release the lock temporarily to apply pending updates. Apple's App Lock reference says apps can still be updated while App Lock is on, so test one iPad with your MDM before you plan around either answer.

OS updates behave the same way. In an r/Intune thread from August 2026, an admin with roughly 30 kiosk iPads reported that they ignored a declarative device management update policy. Replies split: one admin said kiosk iPads running Guided Access would not update until Guided Access was turned off, another got "Enforce latest" working against a web app in kiosk mode, and a third suggested pinning a Targeted Version instead.

Declarative updates are now the only route. Apple's enterprise notes for iPadOS 27 say legacy software update management, including update commands, update queries and deferral restrictions, no longer works in the 27.0 releases. The same notes fix a bug where the locked app disappeared from the Home Screen and Dock after a Single App Mode payload was removed.

Because the reports above disagree, test one iPad before the update window. Build a monthly maintenance slot where kiosks leave the lock, update and return to it, and write that slot into the client's runbook.

Before you deploy a check-in or lobby kiosk iPad

A check-in iPad, a wayfinding screen and a visitor sign-in tablet fail in the same places. Run this list on one iPad before the rest ship:

  1. Supervision. Enroll through Automated Device Enrollment, or supervise with Apple Configurator if the iPad was bought outside Apple Business.
  2. The app and its sign-in. Install the app, sign in and test its own session timeout before the lock goes on, because Settings is out of reach afterward.
  3. Lock options. Keep touch on, turn off the Sleep/Wake and volume buttons, and fix rotation to match the mount.
  4. Website kiosks. Put every redirect the site uses on the allow list, sign-in pages included.
  5. Wi-Fi. Push the network as a profile, and keep an Ethernet adapter that fits the iPad's port in the site kit.
  6. Screen and power. Set auto-lock in App Lock or Guided Access so the screen stays awake in opening hours, and mount the iPad within reach of its charger.
  7. Updates. Schedule the monthly window and set the OS version through declarative software update settings.
  8. The exit. Write down who can lift the lock (the MDM admin, the Configurator Mac or the passcode holder) and how fast they can reach the site.

For multi-site fleets, the remote side matters more than the lock itself. Pick an MDM that can lift and reapply App Lock per site or device group, restart a device and show when each kiosk last checked in, so a frozen check-in screen gets fixed from the console instead of a drive. Our MDM pricing guide covers what that costs per device.

Kiosk mode on Chrome and Windows

Off the iPad, the lock moves to a browser flag or a Windows account, and the same question of who holds the exit applies.

Chrome kiosk mode on a PC

On a laptop or mini PC, Chrome kiosk mode is a launch flag. Starting Chrome with --kiosk opens it in full screen, and the Chromium switch list notes that this is not Chrome OS kiosk mode. The flag changes the window, not the machine, so it works as a tidy front end and not as a lock.

A Chrome kiosk still needs a surrounding policy. Keyboard shortcuts, other apps and the desktop sit behind the browser unless the operating system blocks them. A related switch, --kiosk-printing, presses the print button in print preview automatically, which suits receipt and label kiosks.

The full Windows and ChromeOS setup, including how to get back out of a Chrome kiosk, is in our Chrome kiosk mode guide.

For Chromebooks and Android tablets, the lock comes from the management console and not from a flag. The Android side is covered in our Android MDM guide.

Windows Assigned Access

Windows has no Guided Access. The built-in equivalent is Assigned Access, and Microsoft's own examples are public browsing and interactive digital signage. Microsoft Learn (updated 15 July 2026) says a single-app kiosk runs one Universal Windows Platform app or Microsoft Edge in full screen above the lock screen, and if the app closes, it restarts. A restricted user experience is the multi-app option, with a defined app list, a tailored Start menu and taskbar, and AppLocker rules.

Assigned Access applies to Windows 11 and Windows 10 Pro, Enterprise, Enterprise LTSC, Education and IoT Enterprise. Home is not on the list, so a Home-edition mini PC needs an upgrade or a different approach.

Kiosks also lose their lock quietly. A screen that sleeps or locks defeats the point of a menu board, and the fix is a power setting, not a new tool. Our guide to screen timeout settings covers the dashboard and kiosk case.

If you run kiosks for clients, OpenFrame can run a script across a client's devices and collect the output, which makes a quick audit of kiosk settings a single job.

Choosing the right lockdown

Start from the device, then ask who needs the exit. One iPad that a staff member sets up and watches fits Guided Access. A supervised fleet with an MDM fits Single App Mode. A Windows machine fits Assigned Access, and a Chrome flag is a front end that sits on top of one of those, not a replacement. A website-only iPad adds an allow list or a full-screen Web Clip on top of either iPad lock.

Mixed fleets raise the same question at scale, which our MDM solutions comparison answers by platform.

Aliaska Varieva

Aliaska Varieva

VP of Engineering

Hi! I’m Aliaska, and I’ve been working as a software engineer (mostly Java + a bit Kotlin) for over 8 years now. I mostly spend my time building backend services, integrating systems, fixing bugs (the fun part 🙃), and making sure things don’t fall apart behind the scenes.

Related Content

Frequently Asked Questions

/blog/ipad-kiosk-mode

Still deciding?

Ask Mingo answers from our docs and customer stories.

Loading related content and questions