Cloud GPU for video editing: should you cut on a remote machine?

Start with your upload, not the GPU

Footage has to reach the machine before anything else happens, and your home upload is usually the slow end of that trip. Here's the sum for one terabyte, ignoring overheads, so real transfers take longer.

Compare that with your shoot. If a job produces 300 GB a day and your upload is 20 Mbps, each day of shooting takes about a day and a half to send, so you never catch up. On a 500 Mbps office line it's an hour or two over lunch. Coming back is cheap, because only the finished export returns. Nothing on our side counts the traffic, so sending the same project up three times costs you time and no money.

What distance feels like on a timeline

Delay is felt in frames. At 24 fps a frame lasts about 42 ms, so a 100 ms round trip means you see your keypress land roughly 2.4 frames late, and encoding and decoding the picture add to that. Logging clips and rough assembly barely notice. Cutting dialogue or music on a beat notices at once, because your hand and the picture disagree.

You can't tune this away, so pick the room closest to you. The data centers page times your own browser to New York, Miami, San Francisco, Amsterdam and Bucharest, which is better than guessing from a map. Run it from where you actually edit, at the hour you actually edit. Wi-Fi adds its own jitter, so plug in a cable if you can.

Three machine traps to avoid

A card's listed build isn't always an editing machine. Adobe's Premiere requirements are the strict case, so check them first even if you use something else.

• The processor. Adobe's Windows minimum requires AVX2. Intel lists only AVX for the Xeon E5-2630L, and that chip sits beside many cards on our list, RTX 3090 included, so read the processor printed next to the card. That chip is out for Premiere. Several parts fit more than one chassis, so confirm the configurator offers your card on a newer line. Adobe also asks for an Intel 6th Generation or newer chip, so AVX2 alone doesn't settle it: Xeon E5 v4 has AVX2 but is older silicon. The Xeon Silver and Gold line is the safer pick, and Microsoft's Windows 11 processor list names Xeon Scalable but no Xeon E5. The Xeon Silver 4110 builds on the list carry 16 GB, so raise the memory for 4K. Adobe's recommended list names Intel chips with Quick Sync and Ryzen or Threadripper parts, not Xeons, so expect to judge performance yourself.
• The operating system. Adobe lists Windows 11 v24H2 and doesn't list Windows Server at all. Windows 11 Pro is among our images on the widest lines, so confirm it's offered on the line you pick. Windows Server suits other jobs.
• The disks. Base builds on the card list carry two mirrored 500 GB SATA disks or two 240 GB SSDs. That's a system drive, not a place for footage. Adobe recommends a fast SSD for cache and a separate high-speed drive for media, so add storage before you order. A changed build is monthly, not hourly.

For the card, Adobe recommends 8 GB of GPU memory, and 32 GB or more of system memory for 4K. The professional shelf has good options and GeForce cards work too; aim for Adobe's recommended 8 GB and a hardware video encoder. Check any Tesla, Quadro or mobile-class card against your remote tool before you order: Parsec says professional and server cards need hardware encoding, a real or emulated display and WDDM mode, which it says generally means an NVIDIA Grid licence, and that MXM cards tend to lack the encoder. Skip A100 and H100: NVIDIA's matrix shows no video encoder on them, and your remote display wants one.

DaVinci Resolve Studio uses CUDA on Windows and Linux, and Blackmagic says it can use more than one GPU. Read the minimum list in Blackmagic's notes for your version. Check how you're licensed too: Studio accepts a dongle, a Blackmagic Cloud licence or an activation code, and a dongle can't plug into a machine you never touch.

How you'll see the screen

The display tool shapes the feel of the job more than a card upgrade does. All three send you a compressed picture of the desktop.

Parsec and Sunshine both capture a display, and a rack server has no monitor plugged in. Ask us whether an emulator can be fitted before you build a plan around either. Sunshine's docs give this advice for an external GPU: connect a display or dummy dongle to the GPU you capture from. Expect the same on a server with no monitor. The server's iLO or iDRAC console is for rescue and setup, not for editing. Keep any remote tool's admin page away from the public internet: Sunshine's web interface sits on port 47990 and should be reachable only by you. Use the server's firewall to allow Sunshine's ports only from your own address, and do the same for Remote Desktop, with a strong password. If your address changes you'll lock yourself out, so add a console login in the dashboard first; the iLO or iDRAC console gets you back in.

Keep it snappy with proxies

Proxies are lightweight, lower-resolution copies of your clips that you cut with, switching to the full-resolution files when you need them. For remote work they open two useful patterns. Send proxies up first and start cutting while the full files follow overnight. Or cut at home on proxies and use the remote machine only for heavy renders. The full-resolution files still have to reach it for the final export, so do the upload sum for this route too.

Don't trust the stream for colour

A remote picture is fine for cutting, and not for final colour decisions. Parsec's documentation is unusually frank: 8 bits, Rec 709, with colour management steps needed at both ends even for that. HDR and wide-gamut grades can't survive a path like that, and even a good stream is a re-encoded image.

The simple fix: export a short test section, download it, and judge it on your own calibrated screen. If colour is the whole job, a remote box is a render engine for you, not a grading suite.

A one-day test before you decide

A racked server can be ordered by the hour, exactly as it stands, and released from the dashboard, so a trial may not have to cost a month. If a racked machine has a usable card, a processor that passes the checks above and your operating system, try this. Ask us first whether a racked machine can take Windows 11 Pro and stay hourly; if it can't, the honest test of Premiere is one month on a build. A changed configuration or a build to order is monthly only, so this tests the feel, not your final spec.

1. Morning. Install the card's driver, your editor and a remote tool, then open a project and play it. In Task Manager, confirm the GPU is doing the work. If it isn't, or the remote tool can't capture a display, stop here and fix that first: nothing after this step would mean anything.
2. Upload one real camera card and note the true speed. Redo the table above with that number.
3. Cut for an hour on a real sequence. Scrub, trim to a beat, and play audio. Is the sound in step with the picture?
4. Time an export you know from your own PC.
5. Pull the result back and watch it locally. Compare colour and quality.
6. Copy off anything you want to keep, then end the server. An hourly server is released from the dashboard at once and the machine is gone; a monthly build is cancelled with notice instead. Then decide. If the cut felt wrong but the export flew, you've found the proxy-and-render pattern.

When a local upgrade wins

• You edit every day. A machine you own stops costing money, while a rented one never does.
• Your upload is slow and your footage is large.
• You work in HDR, or sell colour accuracy.
• You need to work on a train.

Rent when it's a heavy project with a known end, when editors in different places take turns on one box, or when your own footage is already in a data centre. There's no contract and one month is the default term, so a monthly build can end soon after the project does. Parts we buy in specially can need three months up front. If renders are the bottleneck rather than editing, our Blender render server guide shows how a batch job on a rented card differs.

Questions people ask

Can I edit 4K on a remote GPU machine?

The machine can do it if it meets your editor's list, and Adobe recommends 32 GB or more of memory for 4K. The harder questions are moving the footage and how the delay feels. Test with your own material, ideally using proxies first.

Does Premiere run on Windows Server?

Adobe's requirements list Windows 11 v24H2 and don't mention Windows Server, so it isn't a supported choice. Use Windows 11 Pro where the line offers it.

Is the GPU shared with anyone?

No. It's a whole card in a whole machine rented to one account, handed to your operating system directly.