Barrier
An open-source keyboard and mouse sharing utility for controlling multiple computers from one desk, with screen arrangement and network trust boundaries to configure.
What Barrier is for
Barrier lets one computer's keyboard and mouse move across multiple screens on a local network. One machine acts as the server and the others as clients. The arrangement, screen names, firewall rules and network trust model determine whether the experience is reliable and appropriate.
Make the screen map explicit
A client name must match the server configuration, and the visual arrangement should reflect the physical desk. Start with two computers and one border crossing, then add screens only after pointer movement, keyboard input and reconnection behave as expected.
Keep the network boundary narrow
Keyboard input, clipboard data and pointer movement cross the connection. Use a trusted network, restrict listening access and avoid exposing the service to an untrusted segment. When behavior is unexpected, stop the server before changing multiple settings.
Maintenance note
This page reviews Barrier server/client roles, screen mapping, local-network permissions, clipboard behavior and troubleshooting. Content review date: 2026-08-23.
Save to your cloud drive
Open the cloud drive to get the file directly, or save it for convenient access on another device.
Quark Cloud Drive
RecommendedSave Barrier to this cloud drive
Baidu Netdisk
Save Barrier to this cloud drive
Barrier server and client setup
Connect two trusted computers first, define their screen names and physical positions, then verify pointer, keyboard and reconnect behavior before adding more devices.
Before you start
- Put the computers on a trusted network and identify which machine will host the server.
- Record each machine's intended screen name and physical position.
- Decide whether clipboard sharing is needed and keep sensitive work outside the first test.
Installation steps
- 01
Install the matching builds
Install Barrier on the server and each client, confirm versions and allow only the local network permission required by the test.
- 02
Configure the server role
Choose the server machine, create screen entries using exact client names and arrange them to match the physical desk.
- 03
Configure a client
Enter the server address, use the configured screen name and start the client only after checking that the network path is reachable.
Quick start
- 01
Test pointer and keyboard crossing
Move across one border, type in a harmless text field and return to the original screen, noting any reversed or missing direction.
- 02
Test reconnect behavior
Stop and restart the client on the trusted network, confirm that the pointer returns to the expected screen and inspect logs for repeated failures.
- 03
Review clipboard use
Transfer a non-sensitive sample only if needed, then keep credentials and private documents out of shared clipboard workflows.
Usage tips
- Screen names, server address and physical arrangement are separate settings; verify all three before changing firewall rules.
- A local-network tool should not be exposed directly to the public internet.
- Keep a fallback keyboard and mouse available while adjusting the configuration.
Troubleshooting and uninstall
Why cannot a client connect?
Check the server address, exact screen name, local firewall rule, listening status and whether both computers are on the expected network.
Why is the pointer crossing in the wrong direction?
Compare the server screen map with the physical desk, remove duplicate entries and test one border at a time.
- Stop both rolesStop the server and clients, remove the local network permission and preserve the configuration only if another trusted setup will reuse it.
- Uninstall BarrierRemove the application through the operating system and clear logs or cached configuration that may contain local network details.
Frequently asked questions
Which computer should run the Barrier server?
Use a trusted computer that stays available and can accept local-network connections. Clients connect to it and follow its screen map.
Does Barrier share clipboard contents?
Clipboard behavior depends on the configuration and client version. Test with harmless text first and keep credentials and private documents out of the shared clipboard.
Can Barrier be exposed to the public internet?
It should remain inside a trusted network or a deliberately protected private tunnel. Do not open a local keyboard and clipboard service broadly.