Real numbers from our own hardware.
About one frame of latency on LAN — your input lands before the next frame draws. Steady 4K at 60 FPS. Hardware H.265, end to end. Every number on this page is measured internally with Remio's own stream-bench harness — no competitor comparisons, no third-party audit yet. The methodology at the bottom shows exactly how we tested, and how you can get a rough read yourself.
Speed you can feel.
Input-to-glass latency — the time between an input event and the moment the resulting frame renders on the client. Measured internally with our stream-bench harness on a LAN-equivalent path, with network conditions emulated in software rather than a live, variable network. Inside that frame, the processing pipeline itself — capture, hardware encode, the LAN hop, hardware decode — costs roughly 8 ms; the rest is the display's own 60 Hz refresh cadence, the same wait you'd have sitting at the machine.
~17–23 ms
Imperceptible on a LAN. This is where Remio's Windows and Mac hosts measure internally — input generally lands before the next frame finishes drawing.
20–40 ms
Still smooth for productivity and most creative work. Typical for solid home Wi-Fi or a same-region relay hop.
40–80 ms
Workable, but you'll start to notice drag and scroll lag. Common on congested networks or longer-distance links.
80+ ms
Frustrating — visible delay on every action. Usually a rough network path, not the app.
Smooth all the way to 4K.
Pick the rate that fits your workload, from battery-saving to full 4K. Remio targets the rate you choose, and bitrate rides your network in real time so quality holds steady instead of stuttering.
Built native. No shortcuts.
We haven't published CPU, memory, or install-size numbers yet — we want a measurement process we trust before we put figures on this page. What we can show you today is exactly how the pipeline is built.
More pixels, sensible bits.
Adaptive encoding gets the most out of your connection. Five presets cover every scenario, all capped at a smooth 60 FPS — Remio shifts between them as your link changes.
From download to streaming, fast.
No accounts. No configuration wizards. No waiting room. Here's roughly what a first-time setup looks like, start to finish.
How we test — and how you can too.
Full transparency about what's behind every number on this page. We haven't published a public, reproducible benchmark suite yet — here's exactly what we did instead, and how you can get a rough read on your own.
Benchmark harness
- Toolstream-bench (internal)
- SetupHost + client, one machine
- NetworkEmulated LAN & WAN profiles
- PipelineReal capture → encode → decode
What we measure
- MetricInput-to-glass latency
- TimestampsIn-process, at send & render
- Frame rateSustained fps under load
- BitrateEncoder output vs. estimate
Hosts tested
- WindowsHardware AMD AMF / NVENC
- MacHardware VideoToolbox
- CodecH.265 primary, H.264 fallback
- VerificationInternal only, so far
These are in-house numbers. They come from our own stream-bench harness, run on a single machine with network conditions emulated in software — not a public, independently verified benchmark suite. That's on our roadmap. Curious about latency on your own setup? The simplest DIY check is two phone cameras: point one at the host screen and one at the client screen side by side, run a millisecond counter or stopwatch on both, and count the frame gap between moving the mouse and seeing it move. Or just download Remio and see how it feels.
Frequently asked questions
How does Remio measure LAN latency?
Why don't you publish CPU, memory, or app-size numbers?
Can I reproduce these numbers myself?
Why does codec choice matter for remote desktop latency?
Are these numbers marketing claims or real measurements?
Run the numbers on your own hardware.
Install Remio on the computer you want to reach and the device you reach it from. The methodology above lists every variable we used — see for yourself.