Making a Raspberry Pi Run as a Kiosk
The Use Case
A Pi, a screen, one web page, and nobody touching it. A wall dashboard, a shop display, a status board. The Pi boots, Chromium opens full screen on the target URL, the screen never sleeps, and if it crashes it comes back.
The install is a handful of commands; the trick is making it survive reboots, SD card failures and Chromium's habit of popping up bars you did not ask for.

The Fast Path
If you want it running in two minutes:
curl -LJO https://raw.githubusercontent.com/LukeKeam/pi-kiosk/master/install.sh && sudo bash ./install.sh
That is my script, from github.com/LukeKeam/pi-kiosk. Read it before running it, as you should with any script from the internet — it does what the longer version below describes.
The Longer Version, Step By Step
1. Install what you need.
sudo apt update
sudo apt install -y chromium xdotool unclutter sed
Package name caveat: on Raspberry Pi OS Bookworm and newer, chromium is the correct package and chromium-browser no longer exists as a separate package. On older releases it was the other way round. If one install command fails, try the other name before assuming the repo is broken.
2. Kill the screen blanking. A kiosk that turns off after ten minutes is a black screen in a room. In the X session:
xset s noblank
xset s off
xset -dpms
Those three lines disable the screensaver, disable the server's blank behaviour, and disable DPMS power management respectively. All three are needed; doing only the first leaves the monitor free to sleep.
3. Hide the mouse pointer. unclutter -idle 0.5 -root & makes the cursor disappear after half a second of stillness. On a touchscreen this is irrelevant, on a mouse-driven display it is the difference between looking like a kiosk and looking like a desktop.
4. Fix the "restore pages?" bar. Chromium, closed uncleanly, offers to restore the previous session on next launch — a grey bar across the top of your display forever. The fix is to exit cleanly or to prevent the prompt:
sed -i 's/"exited_cleanly":false/"exited_cleanly":true/' ~/.config/chromium/Default/Preferences
sed -i 's/"exit_type":"Crashed"/"exit_type":"Normal"/' ~/.config/chromium/Default/Preferences
5. Launch it. The flag set that actually works for unattended display:
chromium --noerrdialogs --disable-infobars --kiosk --incognito http://your.dashboard/url
--kiosk gives full screen; --noerrdialogs and --disable-infobars remove the translation prompt and the "Chrome is being controlled by automated software" style bars. --incognito avoids accumulating profile state across days.

Making It Start Automatically
Two ways, depending on your setup.
Desktop autostart (if the Pi boots to a desktop session with autologin):
mkdir -p ~/.config/autostart
Create ~/.config/autostart/kiosk.desktop with the Chromium command as Exec=. Simple, and it works.
A systemd user unit is more resilient — it restarts the browser if it dies:
[Unit]
Description=Kiosk
After=graphical.target
[Service]
Environment=DISPLAY=:0
ExecStart=/usr/bin/chromium --noerrdialogs --disable-infobars --kiosk --incognito http://your.dashboard/
Restart=always
RestartSec=5
[Install]
WantedBy=graphical.target
Restart=always is the part that matters for a display nobody is watching. Without it, one JavaScript error that kills the renderer leaves you with a blank screen until someone notices.

Keeping It Honest Over Months
Reboot on a schedule. A weekly sudo reboot from cron clears memory leaks in the browser and the display stack. It sounds crude and it prevents the "it was fine for three weeks then froze" call.
Watch the SD card. A kiosk writes logs and browser caches continuously. Put /var/log on tmpfs and mount the SD card read-mostly if you can, or accept that you will replace the card every year or two. Take an image of a working setup so replacement is a ten-minute job.
Provide a reload path. A page that auto-refreshes (a meta refresh or a daily reload) covers the case where the dashboard stops updating but the browser stays alive — which is the most confusing failure, because the screen looks fine.
Test a power cut. Pull the power and watch it come back. That is the scenario it will actually face, and it is the one people never test.
Don't trust the download button. Trust the hash.
If this was useful, More hands-on tech guides at TechGeek. No pressure — read it whenever it's useful.