A Raspberry Pi can display a YouTube playlist in a full-screen Chromium window using Raspberry Pi OS’s desktop and kiosk mode. That gives you a compact screen-based player, but it does not guarantee that a live playlist will advance indefinitely without someone checking or intervening.
For a straightforward display, open the playlist’s normal YouTube page. If you build a custom page around an embedded playlist, serve that page as the player’s enclosing context; do not assume a bare embed URL opened directly in the address bar will work. Check autoplay on the Pi itself and plan how you will notice and recover from a pause, error or ended stream.
What this Raspberry Pi setup does
This arrangement is for showing a YouTube playlist on a monitor or television connected to a Pi. Raspberry Pi OS supplies the graphical desktop, Chromium displays the YouTube page, and kiosk mode removes much of the usual browser interface so the page occupies the screen. You can use it for a shop display, a study-room screen or a devotional playlist where a visible player is useful.
The Pi is acting as a browser and display device. It is not itself creating a YouTube Live broadcast, nor does kiosk mode turn a playlist into a guaranteed 24/7 transmission. Playback depends on the page, the player’s current settings, the network, the Pi’s ability to handle the chosen stream and any prompts or errors YouTube presents. The screen can be full-screen while the playback still needs attention.
If your actual aim is to broadcast a video file as a live channel rather than show a playlist on a local screen, those are different jobs. The guide to streaming a playlist on YouTube Live around the clock covers the broadcast side. For a Pi kiosk, keep the scope narrower: make one browser page appear on boot, test the player and provide a way to recover it.
Prepare Raspberry Pi OS, display and network
Install Raspberry Pi OS with its graphical desktop, then complete the initial setup and connect the Pi to the network you expect it to use. A kiosk needs a working desktop session: the approach here is not a headless command-line player. Raspberry Pi’s official kiosk tutorial describes Chromium launched in kiosk mode and gives a baseline of Raspberry Pi 3 or newer with at least 1 GB of RAM for a graphical browser kiosk. Treat that as guidance for the kiosk setup, not a promise that every YouTube stream, codec or resolution will play smoothly.
Have the practical pieces ready: the Pi, a suitable power supply, a microSD card, a display and the cable or adapter that matches the board. Confirm the display is on the correct input. Raspberry Pi 4 and later use micro-HDMI connections for display output, so an ordinary HDMI monitor generally needs a suitable micro-HDMI-to-HDMI cable or adapter. The board’s ability to output a particular display resolution does not establish that it can decode every YouTube stream at that resolution without difficulty.
Do not choose a board solely from a resolution figure or assume all Pi models are interchangeable for this use. The official kiosk baseline is a useful starting point, while the screen resolution, available ports, network conditions and the stream itself shape the result. If you already own a supported board, test it with the actual playlist and screen before buying replacements. Raspberry Pi’s getting started documentation is the place to check model-specific display connections.
If the device will be installed where a keyboard and mouse are not convenient, decide how you will administer it before putting it behind a display. Raspberry Pi’s kiosk tutorial recommends setting up network access and SSH during imaging for remote operation. That helps you reach the system for maintenance, but it is not a substitute for testing a restart or browser recovery in the physical location.
Open the normal YouTube playlist page
For the simplest kiosk, use the playlist’s ordinary YouTube page as the browser destination. This uses the normal YouTube viewing context rather than asking the browser to open an embedded player on its own. Copy the playlist URL carefully and open it in Chromium once by hand before configuring automatic launch. Confirm that the right playlist appears, the first item loads and the Pi can reach it on the actual network.
There is a meaningful difference between the normal playlist page and an embedded player. The normal page is the lower-effort route, with YouTube’s usual page and player controls. It gives you less control over surrounding presentation, and the page may show prompts, recommendations or other interface elements. For a wall display, these may be acceptable; for a branded layout or a tightly controlled visual page, an embed in a page you manage may be preferable.
A useful comparison is:
| Approach | Setup effort | Presentation control | Context and checks |
|---|---|---|---|
| Normal playlist page | Lower; open the playlist URL in Chromium | YouTube controls the surrounding page | Test the actual playlist page and handle any player prompts |
| Playlist embedded in your own page | Higher; create and serve an enclosing webpage | You control more of the surrounding layout | Keep the player inside that webpage; test its embed behaviour and autoplay |
Neither route removes the need to check the player. The normal page is usually the sensible first test. If you are deciding whether your playlist contents and order suit the channel, the playlist automation tools overview may help with the broader workflow, though those tools do not change what this Pi browser can guarantee.
Launch Chromium in kiosk mode
Once Chromium opens the desired page correctly by hand, configure the desktop session to launch Chromium in kiosk mode when the Pi starts. Raspberry Pi’s tutorial shows Chromium launched with the --kiosk flag from the user’s autostart configuration. Follow the instructions for the Raspberry Pi OS version installed on your device; desktop configuration details can change, so avoid copying an old file path or command without checking it against the current tutorial.
The important elements are the browser, the kiosk flag and the playlist page address. Conceptually, the launch command has this shape:
chromium --kiosk "PLAYLIST_PAGE_URL"
Use the actual executable name and autostart location expected by your installed system. The line above illustrates the pieces, not a complete universal configuration: Raspberry Pi OS releases and Chromium packaging can differ. First verify that the command opens the intended page in the current desktop session, then arrange for that same working command to run at login.
Kiosk mode hides browser furniture; it does not make the page immune to interruptions. A connection error, YouTube prompt, expired sign-in state or player control can still interrupt what appears on screen. Keep a practical way to exit kiosk mode while setting it up, and record how to regain the desktop or restart Chromium. Before mounting the Pi out of reach, test a cold boot and confirm that the playlist page opens without manual navigation.
If your target is an always-on broadcast rather than a local display, kiosk mode is not the same as streaming software. A browser window on a Pi presents a page on its attached screen; a broadcast workflow sends a stream to YouTube. Those approaches have different failure points, and a guide to OBS source restart behaviour is relevant only if OBS is part of a separate production setup, not a fix for a YouTube page in Chromium.
Check autoplay in the Pi browser
Autoplay is a setting to verify in the browser session that will run the kiosk. YouTube’s Autoplay Help page explains that the player has an autoplay control and that settings can vary across devices. A setting you changed on a phone, television or another computer should not be treated as proof that the Pi’s Chromium session behaves the same way.
Open the playlist page on the Pi, start playback and inspect the player’s autoplay control. If autoplay is off, switch it on and observe what happens when the current item reaches its next transition. Then close and reopen the browser, or reboot the Pi, and check again. The point is not to assume the setting persists in a particular way; it is to see what the actual kiosk session does after the kind of restart you expect in normal use.
Autoplay is a convenience that can help the player continue between items. It is not documentation that every live playlist will advance forever unattended. A live item may end, the connection may fail, the player may pause, or a prompt may require a person. Keep a check routine appropriate to the importance of the display, and identify who can respond if it stops. For a shop screen, a staff member may be able to reload the page; for a remote site, you may need a way to access the Pi and a person who can confirm whether the screen is actually playing.
Do not confuse “the page opens on boot” with “the programme is recovered after every failure”. Autostart addresses the first event. Recovery means testing what happens after loss of network, a browser crash, a device restart, or an item that ends without the next one playing. Record what you saw rather than assuming that a setting or command covers all of those cases.
Use an embed only inside its enclosing page
An embed is useful if you want to place the playlist within a simple page of your own, but the player should be inside that webpage rather than treated as a standalone destination. YouTube’s Embed videos and playlists guidance documents playlist embedding and the autoplay=1 parameter in embed code. It also explains that embedded playback is intended for an enclosing context; directly opening an embedded-player URL in the address bar can lack an HTTP Referer and may produce error 153.
That distinction matters when configuring kiosk launch. A URL shaped like a YouTube embed address is not automatically a complete webpage context. If you choose an embed, make a real webpage that contains the player and launch Chromium to that page. The page may be hosted locally or at a location you control; in either case test it from the Pi and verify that the player loads as expected. Do not count on a directly opened embed URL always working.
The embed route also shifts some work onto you. You control more of the layout, but you must maintain the enclosing page and test its behaviour after changes. The normal playlist page is less flexible but avoids building that wrapper. Choose based on whether presentation control is worth the extra maintenance, not on an assumption that an embed bypasses YouTube’s player behaviour.
YouTube’s embed documentation describes autoplay=1 for embedded-player code, but the presence of that parameter should not be described as an indefinite-playback guarantee. Test the actual embedded page in Chromium, including a restart and the next-item transition. If YouTube shows an error, check that the player is within the page and that the page is being served as intended before changing unrelated Pi settings.
Test playback, interruption and recovery
A short hands-on test is more useful than leaving the Pi in place and hoping it behaves. Begin with the normal playlist page or the completed enclosing page, then confirm that video and audio play on the target display. Test the screen’s selected input and the volume at the site. A Pi can appear to be working while the monitor is on another input or its speakers are muted, so check what a viewer will actually see and hear.
Next, test the transitions that matter: move to another playlist item, leave the page open for a representative period, restart Chromium and reboot the Pi. If your use depends on a live item continuing, observe what happens when that item ends or the connection is briefly unavailable. These checks do not prove every future condition will be handled; they reveal the specific behaviour of your setup and help you decide how often it needs attention.
Keep a simple recovery note near the device or with the person responsible for it. Include the playlist page address, how to exit kiosk mode, how to reopen Chromium and who should be contacted if the network or account needs attention. If remote access is configured, test it while you still have local access. A recovery plan is useful only if someone can follow it when the display is blank or stuck.
For a channel that must keep broadcasting even when your own computer is off, the Pi kiosk is not the right description of the job. StreamNeo turns an uploaded video into a YouTube live stream, which removes the specific need to leave a personal computer running to deliver that file as a broadcast; you still need to prepare the source and check the channel and player behaviour. Keep that separate from using a Pi to display YouTube locally.
Before committing, compare the operating options on the pricing page. When the file and channel are ready, start free — 24-hour trial, no card.
FAQ
How do I play a YouTube playlist on a Raspberry Pi?
Install Raspberry Pi OS with its graphical desktop, open the playlist’s normal YouTube page in Chromium, and test playback on the Pi. Once it works by hand, configure Chromium to launch that page in kiosk mode at desktop login. Check autoplay and test a restart rather than assuming the playlist will continue unattended.
How do I make YouTube autoplay on boot?
Set Chromium to open the playlist page on boot, then check YouTube’s autoplay control in that same Pi browser session. Autostart opens the page; autoplay concerns player behaviour between items. Test both separately, including after restarting Chromium or the Pi.
Can a Raspberry Pi run YouTube in kiosk mode?
Raspberry Pi’s kiosk tutorial uses Chromium’s kiosk mode and gives a browser-kiosk baseline of Raspberry Pi 3 or newer with at least 1 GB of RAM. That is not a guarantee of smooth playback for every stream or resolution. Test your actual board, network and playlist before relying on it for a display.
Why might a YouTube embed fail when opened directly?
An embedded player is meant to be loaded within an enclosing webpage. YouTube notes that opening an embed URL directly can lack an HTTP Referer and may result in error 153, so put the player in a real page and open that page in Chromium.