Codecs and hardware encoding#
A codec is the method the host uses to compress its screen before sending it to your device. Jump Desktop offers two software codecs that run on the host's CPU (Fluid 2.0 and Fluid) and Hardware, which runs on the host's GPU. The right codec keeps sessions smooth without overloading the host. For example:
- Use Hardware on a Windows host with an NVIDIA GPU to stream video editing or games at high frame rates with low CPU load.
- Use Fluid 2.0 when you connect from Windows or macOS to an Apple silicon Mac driving more than 2 displays, or when you need a color level the GPU cannot encode.
Applies to#
- Jump Desktop on Windows, macOS, iPhone, iPad, and Android Beta. The web browser has no Codec menu; the host selects the codec.
- Fluid connections to Windows, macOS, or Linux hosts Alpha with Jump Desktop Connect.
- Codec selection is available on every plan. Pro and Ultra color require Jump Desktop for Teams Enterprise; see Color levels.
The codecs#
| Codec | Runs on | Best for |
|---|---|---|
| Fluid 2.0 | The host's CPU (software) | Most work. Provides excellent encoding and decoding on computers built within about the last 5 to 7 years, and supports every color level the host offers. |
| Hardware | The host's GPU | Motion, video, and high frame rates with low CPU load, on a host with a supported GPU. |
| Fluid | The host's CPU (software) | Only older computers with slow CPUs and few cores. Supports only the Good color level. |
Choose a codec#
During a Fluid session, open the Codec menu:
| Jump Desktop on | Where |
|---|---|
| Windows, macOS | Remote > Codec |
| iPhone, iPad | Settings button in the session toolbar > Remote > Codec |
| Android | Settings button in the session toolbar > Remote > Codec |
The menu lists Fluid and Fluid 2.0 under Software, followed by Hardware. When the host has hardware encoders from more than one GPU vendor, the menu lists each encoder, such as Hardware (NVIDIA) and Hardware (Intel). Your choice is saved for that host.
If you have not chosen a codec, Jump Desktop uses Hardware on hosts with a recent GPU that supports it, and Fluid 2.0 on other hosts. Mac hosts start with Fluid 2.0.
Which codec to use#
- Host with a supported GPU: start with Hardware. It offloads encoding from the CPU, which benefits video, animation, and high frame rates most.
- Mac host: every Mac supports Hardware except a Mac running in a virtual machine. From iPhone, iPad, and Android, always choose Hardware. From Windows or macOS, Fluid 2.0 is currently recommended for an Apple silicon Mac with more than 2 displays.
- Windows host: choose Hardware when it is available; it is the right choice in most cases.
- You need a color level the GPU cannot encode, such as Ultra on a Mac: use Fluid 2.0. Jump Desktop switches to Fluid 2.0 in this case; see Automatic switching.
- No supported GPU: use Fluid 2.0.
- Very old host with a slow CPU and few cores: try Fluid.
The total pixel count affects performance as much as the codec does, and Retina resolutions multiply the pixel count. To reduce it, see Keep the pixel load in check.
Check which encoder is in use#
Turn on connection statistics and check these rows:
- Encoder: Fluid or Fluid 2.0 for software, or Hardware followed by the GPU vendor, such as Hardware NVIDIA, when the GPU is encoding.
- Encode Time: milliseconds per frame. With Hardware, encode times are higher at low frame rates, so a mostly still screen shows high values. For an accurate reading, keep content moving on screen, for example by playing a video or opening testufo.com.
The Codec menu also shows a check mark next to the codec in use.
Automatic switching#
Jump Desktop changes the codec or color level when the selected combination cannot work. On Windows, macOS, iPhone, and iPad, no message appears. On Android, a message shows the codec or color level you chose, which can differ from the one in use. To confirm the active codec, check the Codec menu or the Encoder statistic.
| You do this | What happens |
|---|---|
| Choose Hardware while the color level is higher than the hardware encoder supports | The color level drops to a level the hardware encoder supports, which can be lower than the highest level the GPU supports. To restore the previous level, choose it again. |
| Choose a color level the GPU cannot encode while using Hardware | The session switches to Fluid 2.0 and keeps your color level. |
| Choose Fluid while the color level is higher than Good, or a color level above Good while using Fluid | The session uses Fluid 2.0. |
| The hardware encoder fails during a session | The session continues on another encoder, usually Fluid 2.0. |
| Your device cannot decode the stream the host's GPU sends, such as High color on a device without 4:4:4 decoding | On Windows, macOS, iPhone, and iPad, the session continues on Fluid 2.0. Your Hardware choice is retained, so your next session tries Hardware again. |
Color levels#
Choose the color level in Remote > Color on Windows and macOS, or Color Quality on iPhone, iPad, and Android:
| Level | Detail | Use it for |
|---|---|---|
| Good | 4:2:0 8-bit | The best performance. |
| High | 4:4:4 8-bit | Sharp text and accurate color. Suitable for most work. |
| Pro | 4:2:0 10-bit | Video editing. Text may appear slightly softer. |
| Ultra | 4:4:4 10-bit | Color-critical editing and animation. |
Pro and Ultra require the Jump Desktop for Teams Enterprise plan. The menu lists only levels the host can encode.
Color levels by host and codec#
| Host | Codec | Good | High | Pro | Ultra |
|---|---|---|---|---|---|
| Mac | Fluid 2.0 | Yes | Yes | Yes | Yes |
| Mac | Hardware | Yes | No | Yes | No |
| Windows | Fluid 2.0 | Yes | Yes | Beta | Beta |
| Windows | Hardware, NVIDIA GPU | Yes | Yes | Beta, on GPUs that support 10-bit | Beta, on GPUs that support 4:4:4 10-bit |
| Windows | Hardware, Intel GPU | Yes | On GPUs that support 4:4:4 | Beta, on GPUs that support 10-bit | No |
| Windows | Hardware, AMD GPU | Yes | No | Beta, on GPUs that support 10-bit | No |
| Linux Alpha | Fluid 2.0 | Yes | Yes | Yes | Yes |
| Linux Alpha | Hardware, NVIDIA GPU | Yes | Yes | On GPUs that support 10-bit | On GPUs that support 4:4:4 10-bit |
| Linux Alpha | Hardware, Intel GPU | Yes | No | On GPUs that support 10-bit | No |
| Linux Alpha | Hardware, AMD GPU | Yes | No | On GPUs that support 10-bit | No |
| Any | Fluid | Yes | No | No | No |
Beta: 10-bit color from Windows hosts is in beta and requires a beta version of Jump Desktop Connect for Windows. The current release of Connect for Windows offers only Good and High, so Pro and Ultra do not appear in the Color menu. Jump Desktop already displays 10-bit color.
Color Passthrough#
Color Passthrough is a setting in the Color menu that shows the host's colors unprocessed, for use on calibrated displays. On uncalibrated displays, colors may look wrong. Color Passthrough is available on every plan. It requires a Windows or macOS client, and a Windows host or a Mac running macOS 15 or later. For settings by kind of work, see Photo editing and design and Video editing and VFX. To calibrate your display and configure DaVinci Resolve for exact color, see Color-accurate work with Color Passthrough.
Requirements#
- To encode with Hardware, the host requires a supported GPU and driver. See Hardware encoding requirements.
- Your device must be able to decode the stream the host's GPU produces. See Hardware decoding requirements.
Codec menu messages#
| Message | Meaning |
|---|---|
| The host doesn't support hardware encoding | The host has no GPU that Jump Desktop can use for encoding. Check the hardware encoding requirements, such as the GPU driver version, or use Fluid 2.0. |
| This computer can't decode the host's hardware codecs (This device can't decode the host's hardware codecs on Android) | Your device cannot decode any codec the host's GPU produces. Check the hardware decoding requirements, or use Fluid 2.0. |
| Codec selection is turned off in Connect Settings (Codec selection is turned off in host settings on Android) | A team administrator has set a fixed codec. See For team administrators. |
For team administrators#
Team administrators on the Jump Desktop for Teams Enterprise plan can configure codec and color defaults for team computers in Connect Settings, under Fluid Settings. See Configure computers with Connect Configurations.
| Setting | Values | Effect |
|---|---|---|
| Default Video Codec | Automatic (default), Fluid, Fluid 2.0 | The codec that sessions start with. While Allow Video Codec Change is on, the Jump Desktop app applies its own codec choice when it connects, so this default mainly takes effect when that setting is off. |
| Allow Video Codec Change | On (default) or off | Off prevents users from changing the codec, and the Codec menu shows Codec selection is turned off in Connect Settings. |
| Default Color Quality | Automatic (default), Good (4:2:0 8bit), High (4:4:4 8bit), Pro (4:2:0 10bit), Ultra (4:4:4 10bit) | The color level that sessions start with. While Allow Color Quality Change is on, the Jump Desktop app applies its own saved color level when it connects, so this default mainly takes effect when that setting is off. |
| Allow Color Quality Change | On (default) or off | Off causes the host to ignore users' color choices. The Color menu still appears available and shows no message. |
To keep team computers on software encoding, set Default Video Codec to Fluid 2.0 and turn off Allow Video Codec Change.
For the other Connect settings and the pages that document each one, see Jump Desktop Connect settings.
Related#
- Hardware encoding requirements
- Hardware decoding requirements
- Get the best performance: network, virtual displays, pixel load, and other session settings.
- Connection statistics
- Virtual displays
- Configure computers with Connect Configurations
- Jump Desktop Connect settings
- Workflows: recommended codec and color settings for each kind of work.