Menu Slideshow: Keep the Menu Visible, Rotate the Offers
A menu slideshow is a sequence of menu images, promotions or videos that plays repeatedly on a restaurant screen. It can be useful for showing specials. It can also make ordering harder when a customer starts reading a price and the entire menu disappears.
Our recommendation is straightforward: keep essential ordering information visible and rotate secondary content in a separate area or on another screen. More slides are not the same thing as a better menu.
This guide covers what belongs in a loop, how to test its timing and when a still board is the stronger choice.
Illustrative cafe layout, not a product screenshot.
What should stay visible in a menu slideshow?
Keep the information required to place a normal order on screen: core categories, item names, relevant sizes, prices and important conditions. Those are not promotional messages. They are the interface between a hungry customer and the cashier.
A seasonal drink photograph, dessert suggestion or upcoming event can rotate. The only explanation of what a combo includes should not.
If your restaurant TV menu is one small display, prioritize a readable static menu. Add a slideshow only when enough space remains to preserve the ordering information. Squeezing the main menu into a narrow strip to make room for a giant advertisement defeats the purpose.
Our digital menu board design guide covers category grouping and hierarchy. Decide that structure before choosing transitions.
Choose the format by the customer's task
Rotating menu boards are not interchangeable with static boards. The right format depends on whether someone is ordering, browsing or waiting.
| Screen job | Recommended starting point | What to avoid |
|---|---|---|
| Primary ordering menu | Stable items, prices and categories | Making customers wait for essentials to return |
| Promotion next to a complete menu | Short, independent offer slides | Offers that need several slides to explain |
| Waiting-area content | A longer mix of relevant information | Obscuring pickup instructions |
| Breakfast and lunch changeover | A scheduled menu replacement | Looping unavailable dayparts together |
Each menu slideshow slide should make sense on its own. A customer may arrive halfway through the loop and never see the previous slide. Avoid sequences where the product appears first, the price later and the conditions last.
Calculate the wait hidden inside the loop
Imagine a digital menu board playlist containing five slides, each displayed for ten seconds, with instantaneous transitions. The full loop lasts fifty seconds.
If a particular price appears on just one slide, that price is absent for forty seconds between appearances. A customer who looks up immediately after its slide ends may wait almost forty seconds to see it again.
That is arithmetic from an illustrative playlist, not an observed restaurant benchmark. Longer transitions add more time. Repeating a slide changes the calculation but does not remove the underlying problem.
A menu slideshow should not force customers to memorize a board or hold up the queue. Before increasing slide count, ask whether the new content actually needs that position on the ordering screen.
Keep the same core menu in place while the secondary promotional panel changes.
Test reading time instead of guessing a universal duration
There is no single slide duration that works for every menu, language, audience and viewing distance. A large photo with a short offer requires a different reading task from a dense list of ingredients and prices.
Test your menu slideshow from the actual queue. Ask someone unfamiliar with the layout to find an item, choose a size and explain the offer. Watch whether the slide changes before they finish. Include people who read at different speeds where possible.
Nielsen Norman Group's research on auto-forwarding carousels describes web users missing information when panels rotate automatically. It is not a restaurant-screen trial, but it supports a relevant caution: content that disappears can interrupt reading.
If reading feels rushed, simplify the slide or keep it static. Slowing a large loop can help people read each slide while making them wait longer for another slide. That trade-off is another reason not to rotate essential prices.
Build a small, purposeful playlist
Start with fewer messages than you think you need. One clear drink offer and one dessert suggestion are easier to maintain than a dozen loosely related promotions.
- Define the core information that must remain visible.
- Give each promotional slide one item or offer and its relevant conditions.
- Use artwork sized for the actual screen orientation.
- Check legibility on the screen, not only in the editor.
- Watch a complete loop from more than one arrival point.
- Record an owner and expiry date for every time-limited offer.
Your menu slideshow also needs an update routine. A price embedded in a PNG or video does not change merely because a separate price field changes. When pricing moves, replace every affected asset and confirm the version actually playing.
Keep dayparts separate from slideshow timing
Slideshow timing controls how long one asset remains visible. Daypart scheduling controls which menu should be available at a particular time.
Do not put breakfast, lunch and dinner into one repeating loop if the kitchen is serving only lunch. Instead, switch the active menu at the correct time and use any promotional loop within that service period.
See our digital menu board scheduling guide for the planning workflow. Confirm supported formats, scheduling behavior and recovery on your actual software and player before relying on them.
Frequently asked questions
Can I make a menu slideshow with ordinary presentation software?
Yes, you can design slides and export supported media formats. Playback, remote updates, scheduling and recovery are separate questions. Check what your screen or player accepts; do not assume a presentation file will play directly.
How many slides should I use?
Use the fewest needed for distinct, useful messages. Keep the complete ordering menu visible rather than selecting an arbitrary maximum and filling it.
Should every slide have motion?
No. Motion should have a reason, such as demonstrating a product. Moving prices, rapid transitions and competing animations make the reading task harder.
When is a static menu better?
When space is limited, guests need the full menu to order, or the team cannot reliably maintain several assets. A clear still board is a valid digital menu.
Make the menu useful before making it move
A good menu slideshow adds information without taking away the information customers already need. Keep the menu steady, make the offers self-contained and test the result during a realistic ordering task.
If you are evaluating MenuPi, start with your actual menu and display arrangement. Prove the layout and update workflow first; the transitions can wait.