Table of contents Toc Icon
Table of contents Toc Icon
Remote Rendering is a feature in DaVinci Resolve Studio that sends a queued render job from the machine you are editing on to a second machine that performs the export. The second machine opens on the Deliver page and waits for work to arrive.
It is described as a render farm. Remote Rendering does not make a single export faster simply by sending it elsewhere. The entire job still runs on one machine, so its completion time depends on the performance of that render workstation.
Editors usually reach for this feature because of one of three delays: they cannot keep working while a job exports, several deliverables are due at the same time, or one long export is holding up delivery. Remote Rendering can address the first two by moving jobs to another workstation. It does not divide one long Deliver-page export across several machines.
The sections below cover what the feature does, how to set it up, and what handles the other two situations.
What DaVinci Resolve Remote Rendering does
Remote Rendering requires DaVinci Resolve Studio on both machines, since the feature isn’t part of the free version. Each machine needs its own license, either an activation key or a dongle.
The artist workstation builds jobs on the Deliver page and adds them to the render queue as normal. Instead of rendering locally, it passes the job to a second machine set to Remote Rendering mode.
Both machines must access the same media. Blackmagic is specific about this in the DaVinci Resolve reference manual: the storage volume holding the media in the project references must be mounted on the artist workstation and on the remote workstation. The project must also sit in a shared project library rather than a local one, so both machines can open it.
Setting up a remote render machine
- Mount the storage volume that holds the project media on both machines.
- Open DaVinci Resolve on the machine that will handle the rendering.
- Right-click in the Project Browser and choose Remote Rendering. If a project is already open, choose Workspace and then Remote Rendering.
- The machine switches to the Deliver page and waits for jobs.
- On the artist workstation, add jobs to the render queue and send them to the remote machine.
To put the render machine back to normal use, choose Workspace and then Remote Rendering again.
The render machine can also run with no interface on screen. Launching the Resolve executable with the -rr flag starts it directly in Remote Rendering mode, which suits a machine sitting in a rack with no monitor attached.
Why a single export does not get faster
Remote Rendering distributes jobs. It does not distribute frames.
Send one job to one remote machine, and that machine does all the work, so the export takes as long as that machine needs. If the render box has an older graphics card than your edit workstation, the export finishes later than it would have locally.
The gain shows up with several jobs at once. Five deliverables split across two machines finish in roughly half the clock time, because two exports run at the same time.
Nothing in DaVinci Resolve splits a single Deliver page export across multiple computers. The only thing that shortens one export is a faster machine performing it.
Background rendering in DaVinci Resolve 21
The most common reason editors go looking for Remote Rendering is that they cannot use Resolve while it exports. Resolve 21 deals with this directly.
Blackmagic added background processing in DaVinci Resolve 21, covering renders, quick exports, and proxy generation. You start a render on the Deliver page and keep cutting on the same computer. The DaVinci Resolve 21 New Features Guide documents the feature and the preference that switches it on.
The setting is off by default and sits under the background tasks section of Preferences. Blackmagic sets higher memory and graphics memory requirements for background rendering than for Resolve itself, so a machine that runs Resolve comfortably may still not qualify for it.
A second constraint matters more day to day. Background rendering uses the same graphics card that draws your timeline, so the export and the viewport compete for the same hardware.
In November 2025, Puget Systems found that running a remote desktop stream while using DaVinci Resolve Studio reduced the performance of hardware-accelerated LongGOP encoding by about 6.6% on both the RTX 5090 and the RTX 5070 graphics cards. This drop in performance happened because both the streaming software and Resolve were using the same GPU encoder. Background rendering also puts a similar strain on one graphics card, and cards with less memory show the effects more quickly.
Fusion render nodes and what they cover
A DaVinci Resolve Studio license also activates Fusion Studio, and Fusion Studio includes unlimited network render nodes. Plenty of Studio owners never use them.
Blackmagic describes the capability of rendering Fusion comps on remote CPUs. That wording is worth taking literally. Render nodes handle Fusion compositions written through a Saver node, and they lean on processor performance rather than graphics performance.
They do not render a graded timeline from the Deliver page. If your slow export is a color-graded edit carrying noise reduction and effects, render nodes will not touch it.
The setup requirements are strict, too. Every machine must sit on the same network subnet, and each one needs access to the same files, fonts, and third-party plug-ins used in the composition.
What the three methods have in common
Read together, the built-in options point in one direction.
| Method | What it needs | What it will not do |
| Remote Rendering | More machines, on one network, with the same media volume mounted | Make a single export faster |
| Background rendering | More memory and graphics memory in the machine you already own | Free up the graphics card it shares with your timeline |
| Fusion render nodes | Spare processors on the same subnet with matching files and fonts | Render a graded Deliver page timeline |
None of them shorten a single export on the hardware you have. What shortens an export is a graphics card with more memory and more headroom on the machine doing the work. What lets several exports run at once is more machines that can all reach the same media across one network.
Both of those conditions describe a hosted environment rather than a second machine bought for the office.
A GPU-powered cloud desktop gives you an edit seat and a render seat on the same network and the same storage, ready the day you need it.
Where remote rendering breaks for distributed teams
Once the render machine is in the office and the editor is at home, that media volume has to be reachable from both places. Mounting it over a VPN and then reading full resolution media through that connection for an export is slow enough that the render machine stops being worth using.
Storage paths cause a second problem. The same volume mounted as a drive letter on Windows and as a volume path on macOS gives the two machines different addresses for identical files, and the render job fails to find the media.
Blackmagic Cloud can help distributed teams share projects and media. Cloud projects can sync proxies or both proxies and original media through Blackmagic Cloud Storage. It does not, however, turn Blackmagic Cloud itself into a remote render machine. Rendering still takes place on a computer running DaVinci Resolve.
Running edit and render seats on GPU-powered cloud desktops
A cloud-hosted desktop for DaVinci Resolve puts the edit seats, the render seat, and the storage in one environment. Resolve runs on a GPU instance in the data center, the media sits on storage beside it, and editors connect from the laptop or Mac they already use.
Only the screen image travels to the editor. The footage never leaves the data center, and nobody waits for media to copy before a render can start.
Ace Cloud Hosting delivers these desktops through Managed Citrix DaaS solutions. The graphics component is Citrix HDX Graphics, previously named HDX 3D Pro. It renders on the server graphics card and streams the resulting image to the screen. Citrix documents hardware acceleration for both DirectX and OpenGL without extra configuration, along with an interactive session on connections as low as 1.5 Mbps.
How an allocated vGPU profile changes export time
Export speed in Resolve follows the graphics card doing the work, and its memory in particular. Noise reduction, optical flow retiming, the AI tools, and deep node trees all consume graphics memory, and a card that runs short drops back to slower processing.
On a GPU-powered cloud desktop, each seat is built with an allocated NVIDIA vGPU profile sized to the work. You pick the graphics memory, codec, and grade the job needs instead of accepting whatever card happens to be in the machine on the desk.
This makes a single export faster because the machine is faster. It doesn’t split the job, and the fair comparison is against the workstation your editor uses today.
Background rendering also becomes practical because memory and graphics memory requirements become a provisioning decision rather than a hardware purchase.
Why remote rendering works properly in a hosted environment
The requirement that stops Remote Rendering from working across sites is met by default here.
Every seat in a hosted virtual desktop environment sits on one network and mounts the same storage at the same path. No volume needs to be mounted over a VPN, and there’s no mismatch between a Windows drive letter and a macOS volume path.
You can provision an extra render seat for the week of a delivery and remove it once that delivery is out. Working with a managed desktop-as-a-service provider means you aren’t buying a second workstation and a second Studio license to cover a busy month.
Keeping GPU drivers and Resolve versions aligned
Resolve is sensitive to graphics driver versions, and a render machine that refuses to start is often a driver problem rather than a Resolve problem.
Resolve 21 expects current CUDA and NVIDIA Studio driver versions, listed on the DaVinci Resolve technical specifications page. Blackmagic also dropped support for Intel-based Macs in this release, which removes the common habit of retiring an older Mac into service as a spare render box.
With a managed desktop-as-a-service provider, driver and application versions stay aligned across every seat. A render machine running a different Resolve build from the edit seats is a frequent cause of failed jobs in a self-managed setup.
Matching the fix to your bottleneck
The table below points each situation at the approach that resolves it.
| What is slowing you down | What to use | Reason |
| You cannot work while a job exports | Background rendering in Resolve 21 | Built in and free, if the machine holds enough memory and graphics memory |
| Several deliverables due at once, one office | Remote Rendering to a second Studio machine | Distributes whole jobs across machines on the same network |
| A heavy Fusion composition | Fusion render nodes | Included with Studio and spreads comps across processors |
| One long graded export | A faster GPU on the render machine | Nothing in Resolve splits a single Deliver page job |
| Editors and render machines in different locations | Cloud hosted desktops with GPU acceleration | One network and one storage path for every seat |
| Short term capacity for a delivery deadline | An additional hosted render seat | Added and removed without buying hardware |
Where each method leaves you
Remote Rendering sends whole render jobs to other machines running DaVinci Resolve Studio on the same network with the same media mounted. It does not split a single export, and it becomes unreliable once those machines sit in different locations.
Background rendering in Resolve 21 addresses the most common complaint: being locked out of the application during an export, as long as the machine has the memory and graphics memory.
Fusion render nodes handle compositions rather than graded timelines. For teams whose editors and render machines are not in the same building, cloud-hosted desktops with GPU acceleration put every seat and the storage in one place. Cloud-hosted DaVinci Resolve VDI gives each editor a full Windows workstation with an allocated GPU and lets you add render capacity for a deadline without buying a machine.
We size the GPU, memory, and storage around your codecs and delivery deadlines, so exports run while your team keeps cutting.
Frequently asked questions
Does Remote Rendering work with the free version of DaVinci Resolve?
No. It requires DaVinci Resolve Studio on both the machine sending the job and the machine performing the render, and each needs its own license.
Can Remote Rendering split one export across several computers?
No. It assigns whole jobs. A single export runs on one machine and finishes as quickly as that machine allows.
Do the artist workstation and the render machine need the same operating system?
They do not, though mixing Windows and macOS introduces storage path differences that commonly cause failed jobs. Mapping the shared volume to matching paths on both machines avoids this.
Why is my render machine slower than my edit workstation?
Export speed depends mostly on the graphics card and its memory. A render box built around an older or lower-memory card finishes a graded timeline more slowly than a current edit workstation.
Can I run a render seat in the cloud and keep editing locally?
Yes, though both machines still have to access the same media, which usually causes trouble. Placing the edit seats and the render seat in the same hosted environment removes the media transfer entirely.
