Parsec Virtual Displays

Virtual Displays is a feature available for Teams and Warp customers that lets you add up to 3 additional virtual displays to the host while connecting to a machine you own through Parsec. The virtual displays show up along with your current physical displays. If the host system has no physical displays attached, Parsec's virtual displays will allow you to connect to the host without requiring an HDMI or Displayport dongle.


Keep in mind that normally you need to join the computer using the same account as the host for the feature to work. The exception is that this isn't necessary for Team customers using Team Computers.

You can enable the setting in the host machine, in Parsec's settings > Host > Virtual Displays. The first time you enable this setting, you must disconnect from your Parsec host and reconnect once for the virtual displays to activate.



  • The host must be running Windows 10 version 1607 or newer, Windows Server 2019 or newer, or macOS 10.15 or newer
  • The host must have the Virtual Display Driver, which is available for download directly from the settings page in Parsec. You may also want to restart the computer after installing it to ensure it works correctly



  • If you use Houdini with virtual displays and privacy mode, Houdini may crash. You can avoid this crash by going into Houdini's installation directory, opening the bin folder, and renaming the OpenCL folder there to something different. When you open Houdini, there will be a warning about OpenCL which can be safely ignored, and Houdini will open fine
  • At least one Virtual Display is required to enable a related feature called Privacy Mode
  • If you are using Parsec Virtual Displays in combination with Privacy Mode, and then decide to disable Privacy Mode but keep virtual monitors, you may need to visit the Windows Display Settings and set your physical monitor to be extended, as it may remain disabled
  • This driver does not negate the need for GRID Virtual Workstation licensing for NVIDIA based cloud GPU instances from AWS, Google Cloud, Azure, and others
  • You may find that your virtual displays are added to the system in a duplicated / clone mode to the physical display if these are connected. You will need to visit the Windows Display Settings on your host and set displays to be extended
  • You may not be able to add custom resolutions to this display via your GPU driver software
  • Virtual Displays do not stick by when you're not connected on Parsec. They are added when you connect via Parsec, and then removed when you disconnect from Parsec


Custom resolutions

Starting in driver version 0.37 you can add up to 5 custom resolutions to the display via the Windows Registry. Each resolution definition must be added to the path below, with a number from 0-4. In case those folders and values are not there, create them manually yourself.


Each definition must contain 3 DWORD values, height, width and hz (frequency) of the resolution and demonstrated below.


Because registry DWORD values are hexadecimal, when adding each value it is helpful to select the radio button for "Decimal" so you can type the value normally.  


In order to apply the resolution, you must disconnect and reconnect to the host with virtual displays enabled.

Parsec supports streaming resolutions up to 3840 pixels wide.