Most HMIs let operators jump between screens with a bar of text buttons or a nested menu tree, but neither shows what a display actually looks like until it opens. A thumbnail navigation menu solves that by presenting a grid of small live or scaled previews, so the operator recognizes the screen they want by its picture rather than its name. This pattern has become common in web-based SCADA, where a browser can render dozens of miniatures at once. This guide explains what a thumbnail menu is, when it beats a button bank or a tree, and how it behaves on a distributed cloud system.
Display Thumbnail Navigation Menu in one line: A display thumbnail navigation menu is a screen or panel that shows small graphical previews of the available displays, letting an operator select one by recognizing its picture instead of reading a label. It is a visual alternative to a text button bank or a menu tree, and each thumbnail links directly to the full display it represents.
A thumbnail navigation menu is a grid of miniature representations of the operator displays, each one a scaled-down or simplified image of the real screen behind it. When the operator taps or clicks a thumbnail, the full display opens. The core idea is recognition over recall: instead of remembering that the demethanizer graphic is called DM-201 in a text list, the operator scans a wall of small pictures and points at the one that looks right. Because the human eye reads a familiar layout faster than it reads a name, a good thumbnail grid can be quicker to navigate than a menu once the operator knows the plant.
Thumbnails come in two broad flavors. Static thumbnails are fixed images captured once, cheap to render and stable, but they cannot show current conditions. Live thumbnails are miniature renderings of the actual display that update in the background, so a screen with an active alarm or an abnormal value can carry that state into the preview - a red border, a flashing symbol, or a changed color visible at a glance. Live thumbnails turn the menu into a lightweight overview in its own right, because an operator can spot which of thirty screens is misbehaving without opening any of them.
Menus of this kind are usually organized rather than dumped in one flat grid. Thumbnails may be grouped by area, unit, or function, sometimes with a filter or search box above the grid so the operator can narrow a large plant to a handful of relevant screens. Hover behavior often enlarges a preview or reveals its name, which keeps the grid dense while still confirming the exact target before the click. The result is a directory that is both compact and visual.
A button bank is a row or column of labeled navigation buttons, always visible and instantly familiar, but it carries no information about what each destination looks like or what state it is in. It works well when there are a handful of top-level screens whose names the operator knows cold. It scales badly, though, because a plant with a hundred displays cannot fit a hundred buttons, and a purely textual list forces the operator to translate a name into a mental picture every time.
A menu tree handles scale by nesting, letting an operator drill from area to unit to screen, but nesting hides destinations behind several clicks and demands that the operator remember the path. A thumbnail menu sits between these two: it shows many destinations at once like a button bank, but conveys each one visually and can carry live state like an overview. For a large, visually distinct set of screens it often reduces both the number of clicks and the cognitive effort of choosing.
The trade-off is space and rendering cost. Thumbnails need real screen area to stay recognizable, and live thumbnails need the system to render many miniatures continuously, which is heavier than drawing a list of text. In practice a thumbnail menu is best used as a dedicated screen-selection page or a slide-out panel rather than a permanent fixture on every display, and it often works alongside a compact button bar that handles the few most-used jumps.
Thumbnail navigation is a natural fit for browser-delivered SCADA because a modern browser can render and update many small graphics at once, and the same page adapts to a laptop, a control-room monitor, or a tablet by reflowing the grid. On a cloud platform such as Merobix, where an operator may be responsible for many sites rather than one plant, a thumbnail grid can present each remote facility as a live tile, so the health of the whole fleet is visible from a single screen and one tap opens the site in question.
Live thumbnails become especially valuable when the operator is remote and cannot walk the plant. A tile that changes color the moment a site goes into alarm gives the same at-a-glance awareness a control-room video wall would, but on any device with a browser. This ties the navigation menu directly to the monitoring job: the menu is not just a way to get somewhere, it is a way to notice that somewhere needs attention.
There are practical limits to respect over cloud links. Rendering dozens of live tiles pulls a steady stream of updates, which matters on a metered or slow cellular connection, so a well-designed system lets the grid fall back to static thumbnails or a lighter status color when bandwidth is tight. The menu should also make it obvious when a tile's data is stale, so an operator never mistakes a frozen preview for a calm site.
They overlap but are not the same. An overview display is a single designed graphic that summarizes plant state, while a thumbnail menu is a grid of previews whose main job is letting the operator select and open other displays. A thumbnail grid built from live previews can act as a lightweight overview, but its primary purpose is navigation rather than presenting a unified process picture.
It depends on the implementation. Static thumbnails are fixed images and never change, which is cheap and stable. Live thumbnails are miniature renderings of the real display that update in the background, so they can show current alarms or abnormal values, at the cost of more continuous rendering and, on a cloud system, more network traffic.
A button bar is best for a small set of frequently used screens whose names the operator knows well, because it is always visible and takes little space. A thumbnail menu earns its place when there are many visually distinct screens, when operators recognize screens faster by their picture than their name, or when live previews can double as a fleet or plant status view.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.