How to Create an NVIDIA Mosaic Display Grid

Last updated 27 July 2026

How to Create an NVIDIA Mosaic Display Grid

A Mosaic grid joins several physical outputs into one large logical display. Windows and Backstage then see a single wide surface instead of separate screens, which is what you want when driving an LED wall or a projector array as one continuous canvas.

Requires the Administrator role. Creating a grid resyncs every display involved — the outputs will blank and the desktop will rearrange. Do this in a maintenance window, not during a show.

[USER-ACTION-REQUIRED: Attach a screenshot of the Mosaic tab showing an active grid and the create panel with available displays here]

Before you start

  • You are signed in to System Management as an Administrator
  • Every display that will join the grid is connected and detected
  • Any EDID overrides those outputs need are already applied — EDID is locked once an output joins a grid
  • You know the physical arrangement of the displays: how many columns, how many rows, and which screen is where

Steps

1. Open the Mosaic tab

In the System Management sidebar, under Configure > GPU, select Mosaic. Active mosaic grids lists what already exists; Create a grid below it is where you build a new one.

2. Check which displays are free

The create panel lists every connected display that is not already committed elsewhere, each identified by GPU number, connector, port, and monitor name. A display already in a grid — including a grid that has been removed from the desktop — does not appear here.

3. Choose the grid size

The Grid (columns × rows) dropdown only offers arrangements that fit the number of free displays, so a size you expect but cannot select means fewer displays are free than you think. You need at least two.

4. Choose the mode

Set Mode to Base, Max Performance, or Immersive — see the table below. Max Performance is the default and the right answer for most media-server work.

5. Tick the displays in row-major order

Tick the displays in reading order: left to right along the top row, then the next row down, and so on. The order you tick them in is the physical layout of the grid — this is the step to get right. The number ticked must equal columns × rows exactly, or the create will be refused.

Work out which physical screen is which before you start ticking. Open the Desktop or GPU Status tab, note the connector and port for each screen position, and write the order down. Guessing here produces a grid whose content is scrambled across the wall, and the only fix is to clear it and start again.

6. Create and verify

Select Create grid and confirm. Building a grid takes noticeably longer than other display changes and the screens will blank while it happens. When the page reloads, the new grid appears under Active mosaic grids with its dimensions, total resolution, and member list. Check the member list matches the physical layout before moving on.

7. Clear a grid when you need to change it

There is no edit — to change a grid, clear it and create a new one. Use Clear on the grid, or Clear all grids to remove every grid at once. Both take a while and both blank the displays involved.

Options explained

Setting

Description

Values / Range

Grid (columns × rows)

The arrangement of the displays. Only sizes that fit the number of free displays are offered.

Dropdown — minimum two displays

Mode

How the driver treats the grid. Max Performance is the default; Base and Immersive exist for specific driver behaviours and are rarely needed on a media server.

Base · Max Performance · Immersive

Display selection

Which free displays make up the grid, and in what physical order. Ticked row-major: left to right, top to bottom.

Checkboxes — count must equal columns × rows

Grids removed from the desktop

A grid that has been detached from the Windows desktop is shown separately, marked removed from desktop, and is read-only — it has no Clear button, and its member displays are treated as in use so they cannot be picked for a new grid.

To change or clear such a grid, return it to the desktop first from the Desktop tab, then come back here.

Common Mistakes

  • Ticking displays in the wrong order. Content appears scrambled across the wall — the right image on the wrong screen. There is no reordering: clear the grid and rebuild it with the correct sequence.

  • Building the grid before setting EDIDs. Once an output is a grid member its EDID is locked. Force the EDIDs first, then build the grid.

  • Expecting a display to be selectable when it is not free. A display in another grid — active or removed from the desktop — is not offered. Clear that grid first.

  • Trying to clear a grid that is off the desktop. It is shown read-only by design. Return it to the desktop, then clear it.

  • Setting output color before the grid exists. Creating a grid regroups the outputs into a single entry with its own settings, discarding the per-output work. Build grids first, then set color.

Tips

  • Use identical displays with identical EDIDs across a grid. Mixed timings are the most common source of grids that build but then behave inconsistently.

  • Record the tick order in the project documentation. Rebuilding the grid after a driver update or a server swap is trivial with the order to hand and slow guesswork without it.

  • Once the grid exists, treat it as one output everywhere else: it appears as a single entry on the Outputs and Desktop tabs, and is configured there as a unit.

  • A grid multiplies the pixels one logical display must carry. Check the member outputs on GPU Status afterwards to confirm none of them ended up short of bandwidth.

How to Force an EDID onto a Display Output — do this before building a grid; EDID is locked on grid members.

How to Set Output Color Format, Bit Depth and Range — set format, depth, and range on the finished grid as a single output.

Display and GPU Configuration — the other GPU tabs and the order to work through them.