Adaptive streaming quality that reads the room.
Remio measures the path between your two devices, sorts it into a local network, the internet or a relay, and picks the bitrate range that minimises both lag and pixelation. Not a slider you drag — chosen automatically as the session starts, and checked again if your network changes.
The path tells us what the network can carry.
Round-trip time — how long a tiny test packet takes to bounce from your client to your host and back — together with how the connection was made, tells Remio what kind of network it is dealing with. Remio checks as the session starts, and again whenever the network path changes.
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 wired LAN that round-trip is tiny. Over Wi-Fi on the same network it is a little longer. On a 4G or 5G link it is clearly longer, and through a relay that has to bounce traffic across a region or two it can grow further, even on a fast modem.
A very short round trip on the same network means a local network — 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 longer 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.
The session starts at a bitrate sized to your screen and frame rate, so a large, fast display starts higher than a small one. From there, the kind of path decides the range Remio works within. If the path changes mid-session — Wi-Fi to cellular, or the connection re-establishing itself — Remio checks it again and adjusts, instead of holding on to a decision made for a network you have left.
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 and no "LAN mode" toggle to remember to flip. The path check is the input, the right range is the output, and the session adapts if the network changes.
A range for each kind of network.
A single adaptive curve has to compromise between networks that have nothing in common. Remio picks the range that fits the path instead: a high one on a local network, a careful one over the internet, a capped one through a relay.
The session starts at a bitrate sized to your screen and frame rate, and the floor stays high so the picture never has to climb back up. The ceiling is 30 to 60 Mbps depending on screen size, which lets the encoder spike when a keyframe demands the headroom — no queue, no lag.
Over the internet the floor drops as low as 300 Kbps when the link gets ugly, and a bad handoff doesn't drop the stream — the encoder gives the network less to chew on and holds the frame rate. Through a relay the ceiling is 15 Mbps, because pushing harder on a shared, constrained path just causes loss.
All of them 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 local network that surge is a routine keyframe; over a constrained path it is the difference between a tolerable session and one that drops out completely.
Checking again when the path changes matters as much as the ranges themselves. If you walk from Wi-Fi to cellular, or the connection restarts itself, Remio re-checks the path so the range matches the network you are on now — not the one the session started on.
What decides the range, nothing hidden.
Four things do all of the work — how the path is classified, the local-network range, the internet and relay ranges, and the render policy. They are the same across every codec and every platform Remio runs on.
About 8 ms of processing latency on a local network.
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. The rest of what you feel on a LAN is your display's own 60 Hz refresh cadence.
On the client: render the newest frame and drop the rest. A lost packet is re-sent straight away if it can still arrive in time; if it can't, Remio skips it and asks for a fresh frame instead of waiting.
One logic, every codec, every platform.
The bitrate ranges are not tied to a specific codec or operating system. The same 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 range logic 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 range 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 range logic as a Windows PC talking to an Android tablet, with hardware acceleration on both ends and no software fallback to slow anything down. Where both ends support them, the same pipeline also carries HDR (from a Mac with Apple silicon or a Windows PC, to a device with an HDR screen) and true 4:4:4 color (from a Mac, or from a Windows PC with NVIDIA or recent Intel graphics, to a Mac, a Windows PC, an iPhone or an iPad).
Three networks, three real experiences.
Numbers in a table are easy. Here is what the adaptive ranges buy 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 lag you can feel 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 network has plenty of headroom for keyframes, 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 internet range absorbing a punch the local-network range 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 a fraction of the bitrate a local network allows — 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. Remio checked the path, the range 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 range to use?
Why separate ranges 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 range as the session starts — you configure nothing, you just see the picture.