Screen Image Quality¶

When connecting to a device in remote desktop control mode, the screen image from the remote device is transmitted as a video stream. To achieve high-quality video, stable network conditions are required — but these are not always available. For this reason, we provide several settings that allow you to adjust video transmission according to your current network conditions.

Data Transmission Channel¶

This is the main setting that determines how video data is transmitted between devices.

Available Channels¶

Depending on the network conditions on both sides of the connection, either a WebRTC or WebSocket channel will be used.

WebRTC¶

WebRTC (Web Real-Time Communication) is a technology that enables real-time audio, video, and data exchange directly between browsers or applications, without the need for intermediate servers. It is widely used for video calls, file sharing, and remote access. WebRTC provides high transmission speed and low latency.

However, a direct peer-to-peer (P2P) connection is not always guaranteed. It may be unsupported, restricted, or blocked on one of the devices. In such cases, a TURN server (Traversal Using Relays around NAT) acts as an intermediary, relaying traffic between participants. Although this increases latency and server load, TURN ensures a stable connection even behind strict NATs or firewalls when other methods (like STUN) fail.

WebSocket¶

WebSocket is another mechanism for video transmission (without audio). It uses a persistent WebSocket connection via a special proxy server to receive video from the remote device. In this mode, video data is first sent from the remote device to the proxy server, and then delivered to the operator’s device. Because this introduces an additional relay (the proxy server), delivery speed between the two endpoints is typically lower.

This channel serves as a fallback option, used when network conditions or device configurations prevent WebRTC from being established.

Channel Selection¶

By default, the system attempts to establish a connection via WebRTC, since it generally provides better performance and lower latency compared to WebSocket.

If WebRTC is unavailable for any reason, the system automatically switches to the WebSocket channel. Common reasons include:

• Unsupported environment — for example, outdated browsers.
• Security restrictions — some organizations disable WebRTC through group policies to prevent tracking of employee IP addresses.
• Server overload — the number of available TURN servers may be limited, and overloaded servers can prevent P2P connections from being established.

Even when a WebRTC connection is successfully established, image quality may still be affected by imperfect network conditions that are beyond our control — such as congestion on intermediate routers, VPNs, or other network participants.

If you find that the WebSocket channel provides better quality in your environment, you can set it as the default for a specific device. To do this, open the device card, go to the Settings tab → Connection, and set the Video Transmission Channel field to WebSocket.

You can also switch the channel during an active session. Open the channel settings panel, select WebSocket, and the system will remember this preference — it will be used by default for future connections to this device.

Video Encoding¶

The quality of transmitted video depends directly on the video content and the way it is encoded. Encoding affects both the size of the data being transferred — which must match your network bandwidth — and the level of quality loss during decoding. There are several settings you can use to fine-tune video encoding for your connection.

Codec¶

Video images on the remote device are encoded using one of the codecs supported by most browsers: AV1, H264, or VP8. The remote agent automatically selects one of these codecs based on the capabilities reported by the operator’s browser. In this guide, we won’t go into the technical differences between the codecs. By default, codec priority is as follows (from left to right): AV1, H264, VP8. You can override this priority if needed.

FPS Range¶

When displaying video, FPS (frames per second) is an important characteristic. By default, the FPS range is set to 10–30. You can adjust this range to fit your requirements.

Frame Drop¶

When this option is enabled, the system may skip some video frames under poor network conditions to maintain a stable connection. WebRTC can automatically drop frames to reduce the data being sent and prevent lags or frozen images. As a result, motion may appear less smooth, but the connection remains stable. This option is disabled by default and applies only to the WebRTC channel. It is not recommended for normal network conditions.

Automatic Color Disabling¶

When this option is enabled, the system automatically disables screen colors during poor network conditions and restores them once the connection improves. This option is disabled by default, but you can enable it if needed.

Wallpaper Disabling¶

When enabled, this option removes the desktop wallpaper at the start of a session. This helps reduce the size of video packets transmitted from the remote device to the operator’s device. By default, the option is disabled, but you can turn it on.

You can configure all of these encoding settings individually for each device. To do so, open the agent application settings, go to Video Settings, and adjust the recommended parameters.

You can also set default encoding preferences for all devices linked to your account. To do this, go to the Video Capture Settings section and modify the recommended settings.

Wallpaper disabling can also be enabled in Group Settings:

Color and wallpaper options can also be toggled during an active session directly from the control panel: