FloSync Blog

How Many Screens Can One Computer Drive?

2026-08-07T10:00:00Z

"How many screens can it run?" is the first question almost everyone asks, and the honest answer is that it is the wrong question by one step. There is no universal number. The number belongs to your computer and your video, not to the software playing it.

FloSync does not set a maximum. One computer runs as many displays as that computer can drive, and if you need more than that, you add another computer. So this is about how to find your number rather than ours.

That is one video across eight panels. The two highlighted ones are the displays this particular computer is driving; the other six belong to other machines. Look at the readout along the bottom: 3840x1080 is what this computer is putting out, and 7680x2160 is the whole wall it is contributing to. Those two numbers are the shape of the problem. The first is a hardware question. The second is a planning question.

Two questions, not one number

When you are sizing a single computer, there are two separate things to establish, and people routinely conflate them.

How many displays will this computer actually expose? This is settled before FloSync is involved, by the machine, its drivers, and any docks or adapters in the chain. FloSync uses the displays and the arrangement your operating system provides, so if Windows or macOS does not list the fourth display in its own settings, FloSync has nothing to show you.

The count is also not the number of sockets on the back. Graphics hardware commonly exposes more connectors than it can drive at once, and a dock can either extend that or quietly cap it. The specification for your exact model is the only reliable source. Counting connectors is how people end up surprised on install day.

Will it play your video smoothly across all of them? This one is about the file as much as the machine: its resolution, its codec, how heavily it is compressed, and how much work the whole playback path has to do to put it on that many pixels. The same computer that handles one clip comfortably can labour on another that looks identical to the eye. Our video preparation guide covers what to choose and why.

Those two questions have different answers and different fixes, and neither has a single cause. A display missing from the operating system could be the driver, the OS configuration, how many outputs the graphics hardware drives at once, a dock, an adapter or a cable, so that is what to work through before buying anything. A picture that stumbles when everything is visible is a signal to test the real media on the real machine, not proof that the file is at fault. Treating either symptom as having one obvious cause is how the wrong thing gets replaced.

What we can honestly tell you about hardware

We test FloSync across a deliberately wide spread of machines, from a laptop eight or nine years old running integrated graphics to a current desktop with a discrete card.

Across that range, FloSync has never been the binding constraint. We are not going to turn that into a table of screen counts, because we have not measured one: that spread exists to catch crashes and sync problems, not to find the point where playback gives out. Publishing a number from it would be describing our hardware and calling it yours.

What we can say without inventing anything is the part that comes from the software rather than the lab: there is no screen limit inside FloSync to run into. Whatever ceiling you meet is outside FloSync, in the equipment and the media.

Test the setup you are going to install

The only capacity answer worth trusting is the one you produce on the actual equipment, and it takes about ten minutes.

Connect every display first and check the operating system's own display settings before opening FloSync, because a screen missing there is a problem to resolve before FloSync enters the picture. Set each display to the resolution and orientation it will run at in the finished installation. Load the video you actually plan to run, not a lighter stand-in, and play it across the whole arrangement full screen rather than judging from a preview. Then watch it for a few minutes, because uneven motion or one panel lagging its neighbor is much easier to fix before the equipment ships to site than after.

If it plays cleanly, that is your answer for that machine with that content. Change the content later and it is worth another ten minutes.

If more than one computer is involved, you do not have to go live to check the wall. Scrubbing the timeline on the server updates the preview on every connected machine, so you can drag through the video and watch whether each one is showing the right piece of the picture, with the room lights on and nothing committed. Getting the arrangement wrong is much cheaper to discover this way than during a first full-screen run in front of an audience.

One computer, several screens

For a lot of installations this is the whole story: one machine, its displays, no network involved.

You choose what the screens do. Independent gives each display its own content, which suits a room where three screens are showing three different things. Mirrored puts the same content on every display, which is what a row of identical menu boards wants. Spanned treats the displays as one surface and spreads a single image across them, which is the video wall case and the one drawn above. The full detail is in Display Modes.

Your screens do not have to match

FloSync works with whatever the operating system hands it, and that includes displays that are nothing like each other. Different sizes, different resolutions, portrait next to landscape. Plenty of installations are deliberately mismatched, particularly in creative and artistic spaces where an even grid is not the point. If you are counting screens, count what you have rather than what a matched set would cost.

When one computer is not enough

At some point you run out of outputs, or the machine runs out of headroom for the file. That is not the end of the wall. It is where you add a computer.

Adding a machine to the network is not by itself what makes a bigger wall. Two things do that together. Each computer runs in Spanned mode, and Global Canvas Extension is where you tell it how large the whole wall is and which piece of it this machine is responsible for. That is what the 7680x2160 in the screenshot above is: the full canvas, with each computer painting its own region of it. Then Network Sync keeps the machines playing together, so the seams line up. Network Sync has the setup, and our guide to syncing video across multiple screens walks through building one.

One requirement to plan around: every machine in a spanned wall needs its own copy of the same video available locally. This is a way to spread one picture across many screens, not a way to play several different files in lockstep.

We do not cap the number of machines, so the ceiling stops being a software question and becomes a question about the room: how much equipment you want to own, and how dependable the network between it is.

When you should not use FloSync for this

FloSync cannot make a computer exceed its own hardware. If the operating system will not recognize your displays at the resolution you need, FloSync cannot fix that, and it is worth being clear that installing ours will not.

There is also a category of job we are the wrong answer for. If you need a fixed, vendor-certified appliance that takes one source and splits it across a known wall, with a support contract attached to that exact configuration, buy a dedicated video wall processor. That is what they are for, and the certainty is the thing you are paying for.

FloSync suits the other shape: build with ordinary computers, use whatever screens they can drive, and add machines as the installation grows. The app is free, so how big the wall gets is a hardware question rather than a licensing one.

The short version

Start with the displays your computer actually supports, according to its specification rather than its ports. Test the real video across the real arrangement. Add computers when you run out of outputs or headroom, and not because you hit a limit we imposed, because there isn't one.

Free Video Wall Software: How to Sync Video Across Multiple Screens

2026-08-05T09:30:00Z

A video wall only works when the screens agree. Get that wrong and everyone notices: a panel a half-second behind its neighbors, or three lobby screens that started together at nine and are visibly staggered by lunchtime. The content is fine. The wall is not.

The good news is that this is a solved problem, and solving it does not require a rack of dedicated hardware or a subscription. This guide covers why screens drift apart, the three ways people build a synced video wall, and how to do it across one computer or many.

Why multiple screens drift out of sync

Two identical machines, playing identical files, started at the same instant, will gradually separate. Nothing is broken. Left alone, independently running players simply drift apart, which is the reason multi-screen playback needs software actively keeping them aligned.

Over thirty seconds you would never see it. Over an afternoon it becomes obvious, and over a week of unattended playback it becomes embarrassing.

This is why "just press play on both at the same time" fails, and why it fails slowly, which is worse. A wall that looks perfect during setup can be visibly wrong by the time anyone walks past it.

Software that syncs a video wall properly does not just start the screens together. It keeps them together, for as long as the wall is running, without anyone watching.

Ways to build a synced video wall

There are three honest options, and the right one depends on how many screens you have and how far apart they are.

One computer, several outputs. The simplest setup. A single machine with a multi-output graphics card drives several displays, and because it is one computer with one clock, the screens are inherently in step. The limits are physical: the number of outputs on the card, and how far you can run a cable. Good for a wall in a single room.

A hardware video wall processor. A dedicated box that takes one input and splits it across many screens. These work well and are built for the job. They are also expensive, often proprietary, and tie you to one vendor's ecosystem for the life of the installation.

Networked software sync across multiple computers. Each computer drives its own screens, and they play together over a local network. This is the option that scales: any number of screens, spread as far apart as your network reaches, using ordinary computers. It is also the option that needs the sync problem genuinely solved, because now there are several clocks involved rather than one.

FloSync does the first and third of these. If your wall fits on one machine, use one machine. There is no advantage to adding computers you do not need, and being straight about that matters more than selling you something.

How to sync video across multiple computers on a network

When the wall outgrows a single machine, you move to networked playback. The setup is deliberately unremarkable:

Install FloSync on each computer that will drive screens.
Pick one machine to act as the server. The others connect to it as clients over the same local network.
Load the same content on each machine. Rather than copying files by hand, clients can pull the server's scenes and content directly when they connect, which saves a lot of time when you are configuring several machines at once.
Arrange each machine's screens to match their physical positions on the wall.
Go live. Every machine plays together, and stays together.

From there it runs unattended. You do not need someone watching the wall.

For a full walkthrough, see the network sync documentation.

Just one computer and a few screens?

Then do that. A single machine with a multi-output graphics card is simpler, cheaper, and has fewer things to go wrong.

FloSync gives you three ways to arrange the screens on one computer:

Spanned stretches one piece of content across all of them as a single canvas. This is the classic video wall.
Mirrored shows the same content on every screen, which suits displays facing different directions.
Independent gives each screen its own content while keeping playback controlled together.

Most installations start here and only add machines when they run out of outputs or run out of cable. The getting started guide covers the initial setup, and display modes covers choosing between the three.

Keeping it in sync around the clock

Signage is not a demo. It runs for days and weeks, unattended, often in a building where nobody thinks about it until something looks wrong.

That changes what "working" means. Starting correctly is easy. Still being correct on Thursday, after four days of continuous playback, is the part that separates software that survives a real installation from software that demos well.

This is worth testing before you commit to anything: leave it running for a full day and come back. Not two minutes. A day.

If you want to get the most out of a long-running wall, the sync optimization guide covers the practical things that help, mostly around how you prepare content and set up the network.

What it costs

Nothing. The FloSync app is free, with no per-screen charges.

That matters more than it sounds for a video wall specifically, because most signage software bills per screen. A wall is by definition a lot of screens, so per-screen pricing scales badly exactly where you need it most: a nine-panel wall costs nine times a single display, every month you keep it running.

Download FloSync and build your wall.

FloSync has been doing multi-screen sync since 2007, which is long enough that the parts you are relying on have been through a great many rooms already. You can read the whole story if you are curious how it started.

Video Wall Software for Trade Shows and Live Events

2026-07-29T14:15:00Z

Running a video wall at a trade show is a different job than running one in a lobby. You are setting up in a venue you may never have visited, on a schedule measured in hours, and once the doors open the display has to hold together without anyone watching it.

That changes what matters in the software. Features that look impressive in a demo are worth very little if they take an afternoon to configure. This guide covers what actually earns its place: synchronization that survives a full show day, setup you can complete under pressure, scheduling that runs the booth without a babysitter, and hardware flexibility that keeps the budget sane.

Key takeaways

Multiple screens showing one piece of content have to stay visually locked together, not just start together, or the effect falls apart within the first hour.
Setup speed is a real selection criterion at events, where booth assembly time is short and there is rarely anyone on site to call for help.
Scheduling lets the booth change content through the day on its own, and cue-based control lets a presenter drive it by hand when that is what the moment needs.
Hardware compatibility drives total cost more than the software does. Software that runs on ordinary computers lets you use gear you own or rent locally.
The FloSync app does multi-screen sync, scheduling, and networked playback across machines, free, with no per-screen fees.

Why sync matters more than anything else at a trade show

At a trade show, people see your wall from every angle and at every distance. If one screen runs a beat behind the others, the illusion of a single display collapses, and it collapses most visibly on exactly the content you spent money on: motion graphics, brand animations, product reveals.

The hard part is not starting together. Any two players can start together. The hard part is still being together at 4pm, after six hours of continuous playback, with nobody having touched anything. Independently running screens drift apart on their own, even when nothing about any of them is broken. Good multi-screen sync holds the screens together across the whole day, so the wall reads as one image instead of a handful of screens quietly drifting apart.

For an events team, that is the difference between watching the wall nervously and being able to leave the booth.

How to evaluate setup speed before you buy

Event timelines are unforgiving. You might reach the hall the evening before opening with a few hours to build everything, and anything that needs training, license activation, or a support call is risk you are carrying into a room where you cannot afford it.

What to look for:

Content loads by dragging it in. If putting a video on a screen takes more than a moment, that cost multiplies by every screen and every change.
One action starts the show. You want a single control that takes you from configured to playing fullscreen everywhere.
Playback does not depend on the venue network. More on this below, because it is the single most underrated criterion in event work.

FloSync is built around this shape. Load videos, images, or web pages onto any screen, then start fullscreen playback across every display with one button.

What display modes do you actually need?

Different booths call for different arrangements, and most setups are covered by three display modes.

Independent. Each screen runs its own content. Useful when one booth is showing several products or messages at once, with playback still controlled together.

Mirrored. Every screen shows the same thing at the same moment. The right choice when screens face different directions and every visitor should get the same message wherever they are standing.

Spanned. One continuous canvas stretched across all the displays. This is the classic video wall, and it is what you want for a product launch or a brand moment where scale is the point.

Most event teams end up using more than one across a show. Being able to switch without rebuilding the setup is worth more than it sounds.

When should a booth use scheduling, and when should it not?

If your show runs several days, or you want a different message at opening than at the afternoon lull, scheduling stops that from being somebody's job.

Time-of-day scheduling changes content by the clock. Your morning message becomes your midday message without anyone pressing anything.

Interval scheduling cycles a playlist of scenes on a timer, each one holding for a set duration before the next. For a booth cycling through product demos continuously, this is usually the right answer, and it loops back to the start on its own.

Cue scenes are the exception worth knowing about. A scene set to cue holds indefinitely until someone advances it from the keyboard, or from a MIDI controller. That is what you want when a presenter is speaking to the wall and needs the visuals to move on their beat rather than a timer's, or when staff trigger content based on what a visitor is actually interested in.

Automation for the unattended hours, manual control for the moments that deserve it. Most good booths use both.

What hardware does a video wall really cost?

Hardware routinely costs more than the software in a video wall project, and some of that cost is avoidable. Solutions built around proprietary video controllers add thousands of dollars, and some lock you to particular display brands or player devices.

Software that runs on ordinary Windows and macOS computers keeps your options open. You can use machines you already have, rent locally near the venue rather than shipping, or buy inexpensive PCs and repurpose them after the show.

For a single-computer wall, a multi-output graphics card typically drives a handful of screens. Past that, you move to several computers playing together over the network, which scales the wall without any specialized hardware in the rack. FloSync handles both, so a booth can grow from two screens to twelve without changing approach.

How to drive a wall with more than one computer

When the wall needs more screens than one machine can reasonably drive, you run several computers together on the local network. One acts as the server, the rest connect to it as clients, and they play as a single wall.

What matters operationally:

The screens stay locked to each other, for the length of the show, without anyone intervening.
Import on connect lets a client pull the server's scenes and content files when it connects, so you are not copying files by hand onto every machine at the venue. This is a genuine time saver during setup.
Controller mode lets you run the wall from a laptop at a control position. Your machine drives the show while the client computers drive the displays, and your own screen stays available for monitoring, scrubbing, and switching scenes. In interval mode you can click scene cards to jump between them instantly.

All the machines need the same content and the same local network. That is the practical requirement to plan around.

What video formats should you prepare?

Event production tends to involve high-quality masters, and you want them to play without a conversion scramble the night before.

Look for support across the codecs professional workflows actually produce: H.264, HEVC (H.265), and ProRes, in the usual containers such as MP4, MOV, MKV, and WebM. Images matter too, since plenty of booth content is static: PNG and JPG for stills, animated GIF, and SVG when you want vector artwork to stay crisp at wall scale. Live web pages open up options for anything that needs to reflect real data during the show.

FloSync covers all of the above, and its video preparation guide has specific recommendations if you want your files in the format that plays most reliably across a wall.

Playback should not depend on the venue's Wi-Fi

This deserves its own section because it is where event installs most often go wrong.

Convention center networks are expensive, oversubscribed, and unreliable at exactly the moments they matter. So draw a clear line between two different things:

Playback is what your screens are doing during show hours. This should run entirely on the machines in your booth and should never require internet access. If your content stops because the hall Wi-Fi went down, you chose wrong.
Management is how you load content, change a schedule, or check on an install. Doing that remotely is genuinely useful, especially across many locations, and it is reasonable for it to involve a network.

The mistake is not using the network. The mistake is letting the show depend on it. FloSync plays locally on your own machines, so once you are configured, the venue's connection is somebody else's problem for the rest of the week.

Questions to ask before you commit

Work through these with your team, whichever product you are evaluating.

On sync. Ask to see it run for a full day, not a two-minute demo. Anything stays aligned for two minutes. Ask what the screens look like after six hours, and whether keeping them aligned requires anyone to intervene.

On setup. How long from installation to content playing on every screen? Can someone with ordinary technical skills run it, or does it need a specialist? What happens if that specialist is not the one who travels to the show?

On failure. If a machine restarts mid-show, does playback come back on its own? Is there documentation good enough to solve a problem at 8am on the show floor, when a support ticket is useless to you?

On cost. Is it a purchase, a subscription, or free? Are there per-screen or per-player fees? Those scale badly, and a wall is by definition a lot of screens. What hardware does it require that you do not already own?

Planning the install before you travel

Good show days are mostly built in advance.

Content. Prepare files at the right aspect ratio for your arrangement. If you are spanning across screens, work out the total canvas first: a 3x2 wall of 1920x1080 panels wants a 5760x2160 master. Then test every file on the actual hardware before anything ships. Diagnosing a playback problem in your own office is a completely different experience than diagnosing it in a crowded hall.

Hardware. Configure the computers and check that the screen arrangement in the operating system matches the physical arrangement on the wall. Photograph those settings so you can rebuild them on site. Label cables and screens, and bring a wiring diagram.

Contingency. Pack spare cables and adapters, and a backup machine if the install is mission critical. Know what can be rented near the venue. And save your configuration to a file so a replacement computer can be brought up with your content, layout, and schedule intact rather than rebuilt from memory.

What are the most common mistakes?

Buying features you will never use. Enterprise signage platforms sell multi-location management, analytics, and marketing integrations. A single booth needs none of that, and it is being priced into what you pay.

Underestimating setup. Software that looks effortless in a sales demo can be laborious in practice. Do a full dry run on your real hardware. It surfaces the problems a quick test never will.

Assuming the venue network will hold. Covered above, and worth repeating, because it is the failure that takes down the whole booth rather than one screen.

Forgetting about audio. Booth areas are loud and often audio is inappropriate anyway. Make sure you can control sound per screen rather than all or nothing, and think about whether several screens playing the same audio will echo across the space. FloSync gives each screen its own audio toggle, and starts with audio off.

Choosing well

For trade shows and live events, the decision comes down to three things: sync that holds for a full show day without supervision, setup you can finish quickly in an unfamiliar room, and hardware flexibility that keeps you from buying a proprietary rack you will use twice a year.

The FloSync app gives event teams all three, free, with no per-screen charges. It has been doing multi-screen sync since 2007, which is long enough that the parts you are trusting on show day have been through a great many rooms already.

Download it and build your setup before the next show. If you want to talk through a specific install, get in touch.

Why Digital Signage Should Run for Weeks, Not Hours

2026-07-22T10:45:00Z

Most signage software is evaluated in the wrong conditions. Someone loads a video, watches it for two minutes, sees that it looks good, and buys it.

But nobody watches signage for two minutes. A screen in a hotel lobby, a museum gallery or a store window runs for days at a time, unattended, in a building where the person who set it up has gone home. The question that matters is not whether it works. It is whether it is still working on Thursday.

That is a different question, and surprisingly little software is built to answer it.

The demo is not the job

A two-minute demo tests almost nothing. It tests that the file plays.

What it does not test is everything that only appears with time: whether screens that started together are still together at the end of the day, whether an installation survives the building losing power overnight, whether a week of continuous playback leaves things exactly as they started.

These are not exotic failure modes. They are the normal operating conditions of every signage installation, and they are invisible in the conditions most people use to evaluate.

What actually degrades

Three things go wrong in long-running installations, in roughly this order.

Timing. This is the most common and the most visible. Multiple screens that were aligned at setup separate over hours, because independently running players drift apart on their own. Nothing has failed. The wall just looks wrong, and it looks wrong in the specific way that reads as cheap: motion that should be one continuous movement across several panels arriving at slightly different moments.

The insidious part is that it is gradual. There is no moment where it breaks. It just gets worse, and because it gets worse slowly, whoever installed it has stopped looking by the time anyone would notice.

Recovery. Buildings lose power. Cleaners unplug things. A machine that needs a human to bring it back is a machine that will be dark until someone visits, which in a distributed installation might be days.

Wear. Software that runs for an hour and software that runs for three weeks are different problems. Small things build up over a long run in ways an afternoon of testing never reveals.

Unattended is the actual requirement

The useful way to think about signage is not "does it play video." It is "how long can I ignore it."

That framing changes what you look for:

Does it hold multiple screens together across a full day, or does it need someone to nudge it?
After a power cut, does the right content come back without a site visit?
If content is scheduled to change at 9am, does that still happen on day twelve?
Can you leave the building?

That last one is the real test. An installation you have to stay near is not an installation, it is a performance.

Why this is the harder half of the problem

Playing a video is easy. Every device made in the last fifteen years can play a video.

Playing the same video, on several screens, in step, continuously, for weeks, with nobody watching, is a genuinely different engineering problem. It is also the part that gets the least attention in product comparisons, because it is the part you cannot see in a screenshot.

This is where FloSync has spent its time. The visible features matter, but the reason the software exists is the unglamorous half: screens that are still right on Thursday.

How to actually test it

Before you commit to any signage software, including this one, do this:

Set it up the way you would really deploy it, with the same number of screens.
Start it and walk away.
Come back a day later and look at it properly.
Pull the power on one machine, restore it, and see what happens without your help.

A day is the minimum. A week is better. If a product only looks correct for the first ten minutes, you will find out eventually, and finding out during a client installation is the expensive version.

The practical shape of it

If you are building something that needs to run unattended, a few things help regardless of what you use:

Prepare content in a format that plays reliably rather than one that merely plays. Our video preparation guide covers the specifics.
Keep the network the screens share simple and predictable. A dedicated network is worth it for permanent installations.
Use scheduling rather than someone remembering to change content. See scheduling.
For installations running days or weeks at a stretch, schedule a daily restart during off-hours. It's routine maintenance, the same as broadcast and AV systems do, not a failure. Our sync optimization guide covers setting it up so it happens on its own.

The FloSync app is free, including for permanent installations, with no per-screen fees. If you are planning something that needs to run for a long time and want to talk it through, get in touch.

FloSync Blog

How Many Screens Can One Computer Drive?

Two questions, not one number #

What we can honestly tell you about hardware #

Test the setup you are going to install #

One computer, several screens #

Your screens do not have to match #

When one computer is not enough #

When you should not use FloSync for this #

The short version #

Free Video Wall Software: How to Sync Video Across Multiple Screens

Why multiple screens drift out of sync #

Ways to build a synced video wall #

How to sync video across multiple computers on a network #

Just one computer and a few screens? #

Keeping it in sync around the clock #

What it costs #

Video Wall Software for Trade Shows and Live Events

Key takeaways #

Why sync matters more than anything else at a trade show #

How to evaluate setup speed before you buy #

What display modes do you actually need? #

When should a booth use scheduling, and when should it not? #

What hardware does a video wall really cost? #

How to drive a wall with more than one computer #

What video formats should you prepare? #

Playback should not depend on the venue's Wi-Fi #

Questions to ask before you commit #

Planning the install before you travel #

What are the most common mistakes? #

Choosing well #