Skip to content

Codecs and hardware encoding

The codec is how the remote computer compresses its screen before sending it to you. Jump Desktop offers two software codecs that run on the remote computer's CPU, Fluid 2.0 and Fluid, and Hardware, which uses its GPU. The right choice keeps sessions smooth without overloading the remote computer. For example:

  • Use Hardware on a Windows workstation with an NVIDIA GPU to stream video editing or games at high frame rates with little CPU load.
  • Use Fluid 2.0 on a Mac Studio driving several displays, or when you need a color level the GPU can't encode.

Applies to

  • Jump Desktop on Windows, macOS, iPhone, iPad, and Android. The web browser has no Codec menu; the remote computer chooses.
  • Fluid connections to Windows, macOS, or Linux (beta) remote computers with Jump Desktop Connect.
  • Choosing a codec is available on every plan. Pro and Ultra color need Jump Desktop for Teams Enterprise; see Color levels.

The codecs

Codec Runs on Best for
Fluid 2.0 The remote computer's CPU (software) Most work. Excellent encoding and decoding on computers built in about the last 5 to 7 years, and supports every color level the remote computer offers.
Hardware The remote computer's GPU Motion, video, and high frame rates with low CPU load, on a remote computer with a supported GPU.
Fluid The remote computer'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 Wrench button in the session toolbar, under Codec
Android Wrench button in the session toolbar > Video > Codec

The menu lists Fluid and Fluid 2.0 under Software, then Hardware. When the remote computer has hardware encoders from more than one GPU vendor, the menu lists each one, such as Hardware (NVIDIA) and Hardware (Intel). Your choice is saved for that computer.

If you haven't chosen a codec, Jump Desktop uses Hardware on remote computers with a recent GPU that supports it, and Fluid 2.0 otherwise. Mac remote computers start with Fluid 2.0.

Which codec to use

  • Remote computer with a supported GPU: start with Hardware. It takes encoding off the CPU, which helps most with video, animation, and high frame rates.
  • Mac with an M-series Pro, Max, or Ultra chip, especially with several displays: use Fluid 2.0. On these Macs it usually performs better than Hardware.
  • You need a color level the GPU can't encode, such as Ultra on a Mac: use Fluid 2.0. Jump Desktop switches to it for you; see Automatic switching.
  • No supported GPU: use Fluid 2.0.
  • Very old remote computer with a slow CPU and few cores: try Fluid.

Total pixels matter as much as the codec, and Retina multiplies them. See Keep the pixel load in check.

Check which encoder is in use

Turn on connection statistics and read 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 the screen busy, such as 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 combination you pick can't 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. 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 GPU's best. Choose the color level again to get it back.
Choose a color level the GPU can't 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.

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. Suits most work.
Pro 4:2:0 10-bit Video editing. Text may look slightly softer.
Ultra 4:4:4 10-bit Color-critical editing and animation.

Pro and Ultra need the Jump Desktop for Teams Enterprise plan. The menu lists only levels the remote computer can encode.

Color levels by remote computer and codec

Remote computer 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 (beta) Fluid 2.0 Yes Yes Yes Yes
Linux (beta) Hardware, AMD or Intel GPU Yes No No No
Any Fluid Yes No No No

Beta: 10-bit color from Windows remote computers is in beta, and needs a beta version of Jump Desktop Connect for Windows. The current release of Connect for Windows offers Good and High only, so Pro and Ultra don't appear in the Color menu. Jump Desktop already displays 10-bit color.

Color Passthrough

On calibrated displays, turn on Color Passthrough in the Color menu to show the remote computer's colors unprocessed; on uncalibrated displays, colors may look wrong. It needs a Windows or macOS client, and a Windows remote computer or a Mac running macOS 15 or later.

Hardware encoding requirements

Remote computer GPUs Requirements
Windows NVIDIA, AMD, Intel NVIDIA: driver version 551.76 or later. AMD: keep the graphics driver up to date. Intel: a supported Intel GPU (see below) with an up-to-date graphics driver.
Mac Apple Built into macOS on Macs that support hardware video encoding.
Linux (beta) AMD Install AMD's amf-amdgpu-pro and libamdenc-amdgpu-pro packages from AMD's amdgpu 6.4.4 release. amdgpu 7.0 doesn't include them. Without them, Connect uses Fluid 2.0. If Encoder still doesn't show Hardware after you install them, contact Jump Desktop support.
Linux (beta) Intel A supported Intel GPU (see below). Install Intel's oneVPL GPU runtime (the libmfx-gen library) and the Intel Media Driver for VA-API from your distribution.

NVIDIA GPUs aren't used for hardware encoding on Linux (beta) remote computers.

Intel hardware encoding uses Intel's oneVPL GPU runtime, on Windows and Linux (beta). It supports these Intel GPUs:

  • Integrated graphics in 11th Gen Intel Core processors (Tiger Lake and Rocket Lake) and newer: Alder Lake, Raptor Lake, Meteor Lake, Arrow Lake, Lunar Lake, and Panther Lake.
  • Intel Iris Xe MAX and Intel Arc A-series and B-series discrete GPUs.

Jump Desktop doesn't use older Intel graphics, such as 6th to 10th Gen Intel Core integrated graphics, for hardware encoding. Without another supported GPU, those remote computers use Fluid 2.0.

Hardware encoding also works:

  • At the Windows sign-in screen, before anyone signs in.
  • On a remote computer with no monitor, using virtual displays. See their requirements.
  • In a virtual machine with a GPU passed through to it.
  • Inside a Windows Remote Desktop (RDP) session.

Hardware encoding handles up to four 4K displays.

Codec menu messages

Message Meaning
The host doesn't support hardware encoding The remote computer has no GPU Jump Desktop can use for encoding. Check the 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 can't display what the remote computer's GPU produces. 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 fixed the codec. See For team administrators.

For team administrators

Team administrators on the Jump Desktop for Teams Enterprise plan can set 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 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 matters with that setting off.
Allow Video Codec Change On (default) or off Off stops users changing the codec. 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 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 matters with that setting off.
Allow Color Quality Change On (default) or off Off makes the remote computer ignore users' color choices. The Color menu still looks 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.