Get your menu on the screen.
Find your board code
Open your board in MenuHoster and choose “Show on a TV”. Keep its code or direct board link beside you.
What you should see: The code for the board you want to show.
Connect the PC and open the board
Connect the PC by HDMI, select that input, and open your direct board link in Chrome. Let the board and its media finish loading.
What you should see: The correct menu on the connected display.
Launch Chrome in kiosk mode
Close other Chrome windows. Replace CODE in the command below with your board code, then run it using the Chrome executable installed on your PC.
What you should see: The board in a full-screen browser without the address bar.
Add the command to operating-system startup
Use your operating system’s startup-app settings to run the command after sign-in. Configure automatic sign-in only on the dedicated display account, then restart the PC to verify the full startup flow.
What you should see: The board opens after the configured account starts.
Review sleep and power settings
Use the Keep it on checklist below, then leave the board open without pressing the remote.
What you should see: The board continues to display without interaction.
chrome --kiosk --noerrdialogs --disable-session-crashed-bubble --autoplay-policy=no-user-gesture-required https://menuhoster.com/tv/CODEReplace CODE with your board code. The Chrome executable name or path depends on your operating system.
Configure startup on your PC.
Windows: in Task Scheduler, create a task triggered at sign-in for the dedicated display account. Choose “Run only when user is logged on”, use the full path to chrome.exe as the program, and put the flags and your board URL in Arguments. Disable sleep and restart to test. The kiosk command does not configure sign-in or startup by itself.
Raspberry Pi OS: on a desktop installation that supports XDG autostart, create a .desktop entry in ~/.config/autostart with Type=Application, Name=MenuHoster board and Exec= followed by your installed Chromium executable, the kiosk flags and your board URL. Enable desktop sign-in for the dedicated display account if unattended startup is required. Newer desktop sessions may use different startup settings; verify on your OS version and restart to test.
Keep it on. Check the power settings.
Disable sleep and display blanking in the PC’s power settings. On the TV, review sleep timers, Eco and Auto Power Off. Names vary by model and year. Configure recovery after power loss in the PC firmware if supported.
Leave the board open for a 10-minute test without touching the remote. Then test a reload and a power cycle. A web page cannot override the TV’s physical sleep settings.
What to expect. Know the limits.
The command alone does not configure startup. Chromium or Raspberry Pi OS may use a different executable name; Windows needs Chrome’s full executable path. Managed Chromebox kiosk enrollment has its own setup.
Page fullscreen can end after a reload, including the nightly maintenance reload. Playback resumes, but you may need a remote click or key press to enter fullscreen again. Browser or operating-system kiosk mode is separate; the page cannot force it.
Physical TV browser behavior still needs validation on your model. Test the setup on your own display before relying on it during service.
Something different? Try this.
The command is not found
Install Chrome or use the executable for the browser you installed, such as chromium. Keep the kiosk flags and your board URL.
Chrome opens with an address bar
Close existing Chrome windows before launching the kiosk command. Confirm the command uses two hyphens before kiosk.
The PC restarts but the board does not
Check the startup entry, account sign-in and network connection. A kiosk flag controls the browser window; it does not configure the operating system.