Quality that reads the room.
Remio measures the path between your two devices in real time, classifies it as fiber LAN or anything-else WAN, and picks the bitrate envelope that minimises both lag and pixelation. Not a slider you drag — chosen automatically in the first second.
The first round-trip tells us everything.
Round-trip time — how long a tiny test packet takes to bounce from your client to your host and back — is the single number that separates a fiber LAN from anything else. Remio measures it in the first one to two seconds of every connection, then never has to ask again.
The moment the two devices say hello, Remio sends a tiny packet to the other end and times how long it takes to come back. On a direct gigabit LAN that round-trip is around one to five milliseconds. Over Wi-Fi on the same network it sits closer to ten. On a 4G or 5G link it lands somewhere between forty and a hundred. Through a relay that has to bounce traffic across a region or two, it can climb past eighty even on a fast modem.
Anything under 15 ms gets treated as fiber LAN — the picture is going to look pixel-perfect, the encoder can hand off frames as fast as it can make them, and there is no need to be conservative. Anything 15 ms or more is treated as the wider world: Wi-Fi from another room, a coffee-shop hotspot, an LTE link on a train, a relay server in another city. The bandwidth controller switches gears.
This single threshold is the whole decision. It runs once per session, so the encoder is not constantly second-guessing itself mid-stream, and you never feel the picture wobble while the algorithm makes up its mind. Where one curve would constantly chase a moving target, two envelopes lock in the right behaviour and let the encoder do its job.
The choice is hidden from you on purpose. You connect, the picture appears, the lag is appropriate to the network you happen to be on. No setup screen, no quality slider, no "LAN mode" toggle to remember to flip. The first round-trip is the input, the right envelope is the output, and the rest of the session inherits the good decision.
Two envelopes, picked once per session.
A single adaptive curve has to compromise between two networks that have nothing in common. Two envelopes — one for fiber, one for everything else — let each network type get the bitrate behaviour it actually needs.
Starts at eight megabits, holds that as the floor, and lets the encoder spike to thirty when a keyframe demands the headroom. Eight is the rate the encoder actually produces for desktop content at 60 fps, so the pipeline never throttles below what the encoder puts out — no queue, no lag.
Starts at two megabits, drops as low as three hundred kilobits when the link gets ugly, and caps at fifteen because pushing harder on a constrained path just causes loss. A bad handoff doesn't drop the stream — the encoder gives the network less to chew on and holds the frame rate.
Both envelopes share the same encoder, the same decoder, and the same frame-by-frame render policy. What changes is where the floor sits, where the ceiling sits, and how aggressively the encoder is allowed to push when a brief surge happens. On a LAN that surge is a routine keyframe; on a WAN it is the difference between a tolerable session and one that drops out completely.
Picking the envelope once per session matters as much as the envelope itself. Switching mid-stream means the encoder has to re-base its rate-control state, which causes a visible quality drop while it settles. The first round-trip is the commitment — we live with it for the rest of the connection, and the connection is the better for it.
The exact thresholds, nothing hidden.
Four numbers do all of the work — the threshold, the LAN window, the WAN window, and the render policy. They are the same across every codec and every platform Remio runs on.
About 8 ms of processing latency, even when the network fights back.
The encoder runs ultra-low-latency H.265 with B-frames disabled, so every frame depends only on what came before it — never on what is coming next. One capture per interval, one encoded frame out, sent immediately. No frame pacing, no encoder queue, no "catch up" logic.
On the client: render the newest frame, drop the rest, ask for a keyframe instead of waiting for a retransmit.
Two modes, every codec, every platform.
The LAN and WAN envelopes are not tied to a specific codec or operating system. The same two rules apply whether the connection is H.265 between two Macs, H.264 to an older Windows machine, or H.265 to a modern Android device.
H.265 is the primary codec because it gives the best quality-per-bit for desktop content, and because every Mac, iPhone, iPad, modern Windows GPU, and recent Android chipset has a hardware encoder or decoder for it. Hardware means the work happens on a dedicated silicon block instead of the main CPU — faster, more energy-efficient, and it leaves the rest of the machine free to do what it was doing before the session started.
H.264 is the fallback for the small set of devices that cannot hardware-handle H.265. It uses slightly more bandwidth for the same picture, but it works everywhere, and the same LAN-or-WAN envelope wraps around it without change.
On the encoding side: VideoToolbox on macOS, AMF on Radeon GPUs, QSV on Intel integrated graphics, NVENC on NVIDIA cards under Windows, and VAAPI on Linux hosts. On decoding: VideoToolbox on Apple devices and MediaCodec on Android. None of this is exposed to you — you pair two devices, the engine picks the best codec both sides can hardware-handle, and the envelope picks itself based on the network.
The result: the same adaptive behaviour ships on every supported platform without separate code paths for each OS. A Mac talking to an iPhone gets the same envelope logic as a Windows PC talking to an Android tablet, with hardware acceleration on both ends and no software fallback to slow anything down.
Three networks, three real experiences.
Numbers in a table are easy. Here is what the adaptive envelope buys you in three settings most people actually meet.
Gigabit fiber LAN. Both devices wired or on the same Wi-Fi 6 router — the picture is pixel-perfect at 4K and there is no measurable lag between moving the cursor and seeing it move. Text is razor sharp at 100 percent zoom. Scrolling a website at full speed looks identical to scrolling on the host itself. The encoder is producing at eight megabits, the network has thirty to spare for keyframe headroom, and nothing in the pipeline is throttling anything.
Coffee-shop Wi-Fi. Shared with twenty other laptops, the stream holds 60 fps and stays clean. When the network briefly congests, you might see a fraction of a second of blockiness in a corner, then it clears. The encoder traded a little detail for the frame rate, the client did not stall, and the session never felt like it was about to drop — the WAN envelope absorbing a punch the LAN envelope would have flinched from.
4G LTE hotspot. From a phone in your pocket, the stream sustains a clean 1080p picture at 60 fps on most modern carriers. Detail in high-motion scenes is softer — the encoder is fitting the picture into two or three megabits instead of eight — but the responsiveness is the same. You click, the click registers. You type, the keys echo. The remote desktop feels like a remote desktop, not a video call of one.
None of these three sessions required a settings change, a quality selection, or a network test before starting. The first round-trip arrived, the envelope picked itself, and the experience matched the network you happened to be on.
Common questions
Five questions the adaptive-quality model tends to raise — honest answers below.
What does Remio measure to decide which envelope to use?
Why two fixed envelopes instead of a single adaptive curve?
Does adaptive quality work on cellular?
Is there a buffer that adds lag?
Can I override the auto-detection?
Adaptive quality is on the moment you connect.
Install Remio on the computer you want to reach and the device you reach it from. The bandwidth controller picks the right envelope on the first round-trip — you configure nothing, you just see the picture.