Playing Google Slides on a kiosk display means showcasing your presentation on digital signage in full-screen mode, in an uninterrupted loop, and with interface elements hidden, completely free of human intervention. This process is accomplished directly by configuring the presentation's web link with auto-advance parameters and assigning it to the target kiosk device with a full-screen execution policy.
Kiosk mode requirements and foundational decisions
Google Slides does not offer a hardware-level locking mechanism on its own. Therefore, the kiosk experience consists of two layers: the presentation layer and the device layer.
Your first decision is whether the presentation will be published publicly or with internal organization access. In accordance with your security rules, you must pay attention to internal access restrictions when publishing slides containing sensitive data on external screens. Published web presentation links must remain accessible depending on the sign-in status of the device.
Your second decision is device management. In enterprise environments, you can use a centrally managed ChromeOS board or run the browser on an external mini PC using kiosk parameters. To understand standalone presentation logic, you can also review the conceptual distinctions outlined in our process for running standalone presentations with PowerPoint kiosk mode.
Publishing the Google Slides link to the web and loop parameters
For your presentation to progress smoothly on the kiosk screen without stalling, you need to use Google Slides' built-in publish to web interface:
- Open your Google Slides file and click File > Share > Publish to web (or directly File > Publish to web).
- In the Link tab, specify the auto-advance timing for the slides (for example, every 5 or 10 seconds).
- Check the options "Start slideshow as soon as the player loads" and "Restart the slideshow after the last slide".
- Click the Publish button and copy the resulting link.
You can directly inspect the parameters included in this link URL. At the end of the URL, the start=true parameter ensures the presentation starts automatically, the loop=true parameter restarts it once it ends, and delayms=5000 advances the slides at intervals of 5000 milliseconds (5 seconds). For full details on these parameters, you can consult our guide on auto-advancing and looping Google Slides.
Setting up a kiosk on managed ChromeOS devices
The Google Admin console is used to deploy a web-based URL as a kiosk app on enterprise ChromeOS devices. Devices must be enrolled in an organization, and the process must be carried out using an account with administrator privileges.
In the Google Admin console, navigate to Menu > Devices > Chrome > Apps & extensions > Kiosks. You can select the relevant organizational unit on the left to define policies by department or team. Hover over Add and click the Add by URL button. Paste the Google Slides web link into the field that appears and click Save.
Under installation policies, select the added web link from the Auto-launch app field so that the presentation launches directly on screen whenever the device boots up. Due to the end of support for Chrome Sign Builder, Google indicates that Chrome apps are being phased out and recommends adding web URLs directly from the Kiosks menu in the Google Admin console for URL-based content, or utilizing an alternative web solution such as Comeen. As stated in official technical documentation, content modifications made to Google Slides URLs do not reflect on screen until the ChromeOS device restarts. Furthermore, scheduling cannot be configured for URLs in the Admin console.
On devices with administrative privileges, a Kiosk Mode session executes a single Chrome or Android app. The operation of this infrastructure and enrollment prerequisites are detailed in the guide on launching a Kiosk Mode app on ChromeOS devices.
Unmanaged displays and alternative kiosk methods
If you are using a standalone computer without a central management console, you can run the Google Chrome browser directly in full-screen kiosk mode. For instance, the steps for launching a kiosk session on a Pixel Slate in developer mode and exiting kiosk mode during device startup using the Ctrl + Alt + s shortcut can reference the principles in the documentation on using Pixel Slate as a kiosk. Note, however, that enabling this setting on a Pixel Slate requires the unit to be administrator-managed with a Chrome Enterprise, Chrome Education, or kiosk license.
On a standard desktop operating system, you can launch Google Chrome with the kiosk parameter via the command line or from a startup shortcut:
chrome.exe --kiosk "PRESENTATION_URL_ADDRESS"
This command hides the browser's address bar, tabs, and window borders, locking the presentation to the screen. To prevent users from accessing the desktop in a kiosk setting, configure local operating system user accounts with restricted permissions.
Example scenario: Company lobby information display
A hypothetical, fully fictional plan for a "Lobby Information Display (Fall 2026 Term)":
Slide 1 (Fictional Title): Tech Summit Welcome Board (Duration: 10 seconds).
Slide 2 (Fictional Agenda): Hall A - 10:00 Opening Keynote, Hall B - 11:30 Panel (Duration: 15 seconds).
Slide 3 (Fictional Refreshments): Lobby floor coffee break hours: 11:00 and 15:00 (Duration: 8 seconds).
Publish Parameter: https://docs.google.com/presentation/d/e/.../pub?start=true&loop=true&delayms=10000
In this setup, all slides are built using text and template graphics. During the visual design phase, you can export announcement templates created with vector tools, place them as slide backgrounds, and set them to loop using the URL shown above.
Troubleshooting and common issues
The most frequent issue encountered in kiosk deployments is that updates do not appear on screen immediately. Changes made to Google Slides URLs added via the Kiosks menu in the Google Workspace Admin console do not appear until the ChromeOS device restarts. When content is refreshed, you must power-cycle the display or reboot the device remotely.
In the event of an internet disruption, the kiosk display may show an offline error warning. Ensure the device is connected to wired Ethernet or a stable Wi-Fi network.
Videos embedded in slides may fail to play automatically or might stall. In accordance with web browser media autoplay policies, verify that videos meant to play on the kiosk are configured with autoplay and mute options inside the Google Slides interface.
Verification and launch checklist
Does the slideshow's "Publish to web" link include the start=true and loop=true parameters?
Does the physical aspect ratio of the kiosk screen match the presentation's page setup (typically 16:9 Widescreen)?
In the ChromeOS Admin console under the Kiosks section, is the web link designated as "Auto-launch app"?
Are screensavers, sleep modes, and automated lock timers turned off at the operating system level?
Have you verified that the browser or Kiosk Mode opens the presentation directly upon device reboot?
Frequently asked questions
Do changes made in Google Slides appear on the kiosk display immediately?
No. Edits made to Google Slides presentations added via URL under Kiosk Mode in the Google Admin console do not update on screen until the ChromeOS device is restarted.
Can presentation display hours be scheduled in the Chrome Admin console?
No. Scheduling cannot be configured for web URLs added directly in the Google Admin console. If you need to schedule content based on specific days or times, you must use Comeen or an alternative web-based CMS solution instead of Chrome Sign Builder.
How do you prevent visitors from stopping the presentation by touching the screen?
On touchscreen displays, tapping the screen can pause or trigger slide transitions even when the browser is running in kiosk mode. To prevent this, you can disable touch inputs within the operating system settings of the kiosk hardware or apply protective hardware/software restrictions over the presentation to block interaction.
← Back to blog
