This is not a list of marketing promises. It is what the software does today, explained with enough technical detail that you know exactly what you are downloading.
The difference between usable remote desktop software and infuriating remote desktop software is mouse latency. LineDesk attacks that problem specifically.
Mouse movement travels on its own deliberately unreliable data channel, so a dropped packet never stalls the ones behind it — head-of-line blocking is exactly what causes the classic remote-control stutter. Roughly 125 positions per second are sent, coalesced at both ends to avoid flooding.
Your cursor is drawn instantly on your side without waiting for the remote machine to confirm. Even with 80 ms of round-trip time, moving the mouse feels immediate.
The video jitter buffer is set to zero: we would rather show a slightly imperfect frame now than a perfect one 200 ms late. For remote control, latency matters more than absolute smoothness.
Windows measures scroll in units of 120 per notch. LineDesk tracks those units and accumulates fractions, so a gentle trackpad swipe reproduces fully on the other side instead of getting lost.
Mouse position is transmitted as a proportion of the screen rather than in pixels. That keeps it accurate even when the two displays have different resolutions or DPI scaling — the usual case between a laptop and a large monitor.
Shortcuts, modifier keys and accented characters all pass through. One exception: Ctrl+Alt+Del cannot be simulated — Windows reserves that combination for the system and no user-level program can generate it.
If you support several clients or administer several machines, you should not need five programs open.
A Home tab plus one per connected machine. Maximise, minimise and go full screen with F11, where the toolbar auto-hides to give you the whole display.
Tabs you are not looking at drop to minimum quality on their own. All the available bandwidth goes to the session in front of you, which is the only one you can actually see.
If the remote machine has three displays, they appear as three sub-tabs. Switch between them instantly, without dropping the video or renegotiating the connection.
A classic dual-pane browser, except the far pane is the remote machine's disk.
Your machine on the left, the remote one on the right. Browse either side and files land in whichever folder is open opposite. Entire folders included, with their full subfolder tree.
Files travel on their own channel within the peer-to-peer connection. Our server never sees a single byte. No cloud upload, no middleman: it is your disk to theirs and nothing else.
Block size is recalculated four times per second based on measured throughput. On a LAN it climbs to 128 KB and saturates the link; on a slow connection it drops to 16 KB so the transfer never adds lag to the mouse.
If the name already exists, the new file is saved as file (1).ext. While writing it carries a temporary extension and is only renamed once it has completed cleanly — so a dropped connection never leaves a truncated file masquerading as a complete one.
On path safety. Every filename arrives over the network, so the receiving side sanitises it segment by segment and then verifies that the final path still lands inside the chosen folder. A maliciously named file cannot write outside the destination you picked.
LineDesk's permission model starts from a simple idea: connecting should mean asking permission, not guessing a password.
You type the ID and a prompt appears on the other side. Nobody gets in without the person sitting at that computer authorising it. The requester waits up to two minutes — a human has to answer, not a server.
A manually granted permission lasts ten minutes. Long enough that a network blip does not force you to accept again, short enough that it never leaves the door open indefinitely.
From the tray icon you end the session instantly, and the reason reaches the operator's screen so their client stops retrying. Cutting means cutting — not "cutting until it tries again in two seconds".
A curtain covers the remote screen while you work on the real desktop. The person on the other side sees only a notice and the chat. It uses a built-in Windows capability, with no driver to install.
The unattended access password is stored derived with PBKDF2-SHA256 and a unique salt, and device-book passwords are encrypted with Windows DPAPI, tied to your user account. Neither your disk nor our server ever holds a readable password.
Transport is WebRTC, which requires DTLS-SRTP: there is no option to connect unencrypted. The signalling server only introduces the two machines and never sees session content.
After a drop, LineDesk first tries to repair the existing connection. If that is not enough it rebuilds the session entirely using the stored password, retrying until you close the tab.
Save each machine with a name and see live whether it is switched on. One-click connect, without hunting for the ID every time.
Closing the window does not close the program, so the machine stays reachable. From the tray icon you cut access or quit entirely.
Direct messaging between the two machines, with a taskbar alert and a system notification when the window is not focused. It works even with privacy mode on.
With a fixed password configured, you reach that machine even when nobody is there. This is what people use for servers, digital signage and the office PC.
Windows will not let a normal program control windows belonging to elevated ones. For that, turn on Settings → Administrator permissions on the remote machine: from the next sign-in LineDesk starts elevated on its own, with no Windows prompt each time, and the app says on screen when it is running that way.
We would rather you knew before downloading than after. These are the real limitations of the current version:
If any of those is a deal-breaker for your situation, better to know now. If not, download LineDesk and try it — it is free and there is nothing to cancel afterwards.
They are all unlocked from the first minute. There is no Pro edition.