Display a spreadsheet on a signage screen without mirroring a PC

Why not just mirror your office PC to the screen?

Mirroring works until the office PC sleeps, updates, or gets borrowed for something else, and then the workshop screen shows a desktop, a screen saver, or nothing; publishing the sheet as a web page takes the PC out of the chain completely.

Mirroring has three failure points. The PC has to stay powered up every shift, or the wall goes dark. The desktop, with whatever happens to be on it, becomes a public display. And the video cable becomes part of the building: a passive HDMI cable holds a signal dependably to about 25 ft, and a run near 50 ft usually needs an active or fiber cable. Publishing removes all three. The player pulls a link, the PC goes home at the end of the shift, and the only thing on the wall is the tab you chose to publish. Checking what the screen shows gets simple too: the published link opens in any browser, so opening it on your phone shows you exactly what the wall sees.

What do you need before you start?

You need three things: a hosted copy of the sheet that can publish a read-only web link, a player on the screen that can show a web page or an image file, and a network path between the player and that link.

• A hosted sheet with a publish option. The share or publish menu in a cloud spreadsheet hands out a read-only link for one tab. The link has to open with no sign-in prompt, because the player has no account to sign in with.
• A player that renders web pages. Most signage players, whether a TV stick, a player box, or a display with a built-in player, offer a web page or URL content type. How a web page signage player caches and reloads pages is worth reading before you commit to one.
• A player that only shows images and video from a card. This includes our panel-mount units, which play images and video from microSD or USB, with the software included and no subscription. These take the auto-exported image route in the steps below. Where a change has to reach the wall within minutes, a card-based player is the wrong choice and a web-page player is the right one; where a shift-change update is fast enough, the card route is simpler.
• A network path. The player needs outbound internet access to pull the page. On a locked-down plant network, put the player on a segment that allows that, or use the card route.

Mount the screen so nobody works underneath an unsecured panel, and route its power cable where pallet trucks and forklifts cannot reach it.

How do you publish the sheet so the screen can read it?

Open the hosted sheet, use the share or publish menu to create a read-only web link for the one tab the floor needs, and open that link in a browser on your phone to confirm it shows the table with no sign-in prompt.

1. Build a floor tab. One tab holds only what the floor reads: line or job, quantity, status, and due time. Calculations, notes, and anything private stay on other tabs, because the publish step exposes exactly the tab you publish.
2. Trim the tab to the room. The worked example below lands on 12 rows for a 20 ft read on a 43-inch panel, so keep the visible table near that count and archive finished rows instead of letting the list grow down the wall.
3. Publish the tab and test the link. Copy the published link into a private browser window on your phone. If it asks you to sign in, the publish step is not finished. Set fonts, colors, and column widths before you publish, because the wall renders the sheet's own formatting.

How do you put the link on the screen?

In the player's content menu, choose the web page or URL content type, paste the published link, and set the player to reload that page every 5 minutes; then leave it as the only item in the playlist.

4. Add the link as web page content. The player treats the published page like any other playlist item.
5. Set the reload to 5 minutes. Players name the setting differently; it lives with the web page content settings, usually as a field for a number of minutes.
6. Set the output resolution to the panel's native 1920 x 1080. Pixel-for-pixel output keeps the text at the size the row-count example below assumes. A table that lands in one corner of the panel is the size mismatch case, and the fix for content that shows too small walks through it.
7. On a card-based player, export an image instead. Schedule a job on the office PC that saves the floor tab as a PNG to the card or stick, and check the player's documentation for how it picks up a changed file, because players differ there. Our card-based units are built to play the files in their playlist, so the export job sets the update speed, and a shift-change cadence is the honest expectation.

How often should the sheet refresh?

Set the reload to 5 minutes: fast enough that an edit made in the office reaches the wall before someone walks out to check it, and slow enough that the player is not reloading the page hundreds of times a day.

Five minutes also matches how a production sheet changes. Job status moves a few times an hour, so the wall stays within one status change of the truth. Faster reloads only add page loads; slower ones start to matter when someone walks to the board, does not find their job, and walks back to ask. The reload timer covers the data half of the job; somebody still has to edit the sheet. The pattern that holds up is a 5-minute reload for the data plus a fixed 5-minute tidy once a week, when someone deletes finished rows and re-sorts the list. Workflow guides for restaurant screens report the same failure with harder evidence: most of those screens end up showing stale content for months, because every update gets treated like a design project. A plain table on a plain tab is easier to keep alive than a designed slide.

What does a worked example look like at 20 ft?

At a 20 ft reading distance, a 43-inch 1920 x 1080 panel fits about 18 rows using the 30 ft per inch planning figure, or about 12 rows at the safer 20 ft per inch figure, so trim the sheet to a 12-row summary for a board read from a moving aisle.

Take a line leader who reads the board from 20 ft, on a 43-inch 1920 x 1080 display. The arithmetic:

• Active image height: a 43-inch 16:9 panel is 43 x 9 / 18.36 = 21.1 in tall.
• Pixel pitch: 21.1 in / 1080 px = 0.0195 in per pixel.
• Capital height: the FHWA planning figure is 30 ft of viewing distance per inch of letter height, so 20 / 30 = 0.67 in. The safer fast-reading figure of 20 ft per inch gives 20 / 20 = 1.0 in.
• Capitals in pixels: 0.67 / 0.0195 = 34 px; at the safe figure, 1.0 / 0.0195 = 51 px.
• Row height: line spacing of 1.7 x capital height gives 34 x 1.7 = 58 px per row, or 51 x 1.7 = 87 px.
• Rows that fit: 1080 / 58 = 18.6, so 18 rows; 1080 / 87 = 12.4, so 12 rows.

Subtract the header row and any title bar, and you are planning 17 data rows at the minimum figure and 11 at the safe one. If people read from a moving aisle instead of standing at the board, take the safe figure. On a 32-inch panel at the same 1920 x 1080, the pixel pitch shrinks and the counts drop to about 13 and 9 rows, which is why the diagonal matters as much as the resolution. The screen size and viewing distance guide runs the same method for other distances and panel sizes.

How do you check it worked?

Edit one cell in the published tab, wait 5 minutes for the reload, and look at the wall; if the number has not changed, the player is showing a cached page, the wrong link, or a reload setting that is off.

Then work down this list:

• Open the published link on your phone. What the phone shows is what the wall shows, which settles the question of what you are projecting.
• Keep a last-edited stamp in a cell at the top of the tab and bump it whenever you edit. A wall showing yesterday's stamp means a missed edit, not a player fault.
• Switch the screen's power off for 10 seconds and confirm it comes back to the sheet on its own. A workshop board that needs a manual restart after every outage will be dark on the day it matters.
• A not-loading page instead of the sheet is usually the URL path: check it character by character. A media player fixed by correcting its URL path is a typical case.
• On the card route, a wrong-looking image means the PNG is the first suspect, and signage image file troubleshooting covers the file side.

When is a cable or a bigger board the better answer?

Keep the mirror-and-cable setup for one screen within about 25 ft of a PC that stays put and stays powered up, and move to a large LED board when the reading distance passes 60 ft, because 0.67-inch capitals only carry a 20 ft read.

The decision, case by case:

• Direct HDMI from the office PC: one screen, content that changes only at a desk, and the PC within about 25 ft. This is the simple case, and mirroring is fine in it.
• Published web page with a 5-minute reload: the normal case. Any distance from the office, the PC free to shut down, updates within 5 minutes.
• Auto-exported image to a card: no network at the screen, and an update every shift is fast enough.
• Read-only offline table: for a screen with no network at all, the offline factory data table layout is the file-based version of this page.
• Past 60 ft: the capitals need 60 / 30 = 2 in, and a spreadsheet tab on a 1080p panel will not carry that across a hall. Choosing a large LED sign board for a shop floor starts that decision, and the factory displays section collects the rest of these shop-floor screen answers.

Recommendation: publish the floor tab as a read-only web page, point a web-page player at it with a 5-minute reload, and size the tab to 12 rows for a 20 ft read on a 43-inch 1080p panel. Take the direct HDMI cable only when the PC sits within 25 ft and never moves, and take the auto-exported image route when the screen's player reads a card and a shift-change update is the honest speed you can promise the floor.

Questions