Remote Mac for Video Editing: Bandwidth Guide

Remote Final Cut Pro over VNC is practical once you separate two very different bit rates: the on-disk codec the Mac reads locally, and the compressed screen stream your VNC client receives. Get proxy transcoding right on the Mac and quality settings right on your client, and a 20 Mbps home connection comfortably handles 1080p timeline playback.

For Final Cut Pro, pick a Figment M-series Mac. Pricing starts at $95/month; the exact chip, RAM and disk are set in your configuration quote, and physical M-series plans currently collect requests while supply is confirmed. The $29 virtual Intel macOS plan runs macOS on Intel with no GPU acceleration or audio, which is fine for text and build work but not a useful FCP host. Request your M-series configuration at Figment Mac hosting.

Why VNC Bandwidth Is Not the Proxy Codec Bitrate

Apple ProRes 422 Proxy is designed as a lightweight edit-time codec. Its on-disk bit rate describes how fast the Mac reads and decodes from local storage, not what crosses the internet. Apple documents the proxy choices directly: "Apple ProRes 422 Proxy" or "HEVC", with proxy media available "in a variety of frame sizes from 12.5 percent to 100 percent of the original" (Final Cut Pro User Guide — Create optimized and proxy files).

What actually travels is a compressed screen stream. RFC 6143 notes that "current servers use the ZRLE, TRLE, and CopyRect encodings since they provide the best compression for typical desktops"; ZRLE "combines an encoding similar to TRLE with zlib compression" and operates on 64×64 pixel tiles, and "the server must not send unsolicited updates" — frames are only sent in response to a client FramebufferUpdateRequest (RFC 6143 — The Remote Framebuffer Protocol). When FCP plays a talking-head interview, the timeline, inspector and browser do not change; only the viewer updates, and ZRLE keeps the sustained stream well below any raw-pixel figure.

Color depth amplifies the savings: dropping from 32-bit to 16-bit halves the per-pixel footprint before compression at some cost in color accuracy. For cut-and-timing work rather than final grading, 16-bit is usually enough.

Proxy Workflow: Transcode Before You Edit

Create proxies at import or retroactively through File > Transcode Media. Set the codec to Apple ProRes 422 Proxy and choose a frame size between 12.5% and 100% of the original. For rough-cut work on a 20 Mbps link, 25% of a 1080p source (480×270) or 50% (960×540) is plenty; for careful 1080p timing review, use 100% and lower the VNC frame rate instead.

Once transcoded, open the View pop-up in the upper-right of the viewer and choose Proxy (or Proxy Preferred). FCP then renders from the smaller files, which lowers CPU load on the remote Mac and produces a quieter, more stable VNC stream. For 4K sources, a 25% proxy gives you 1K frames to edit against; the full-resolution render happens on the Mac during export, so your link only carries the low-resolution playback stream during the edit itself.

Bandwidth Requirements Table (Resolution × FPS × Quality → Mbps)

The figures below are typical sustained minimums for continuous proxy playback over VNC. They reflect the compressed screen stream, not the codec bit rate. Actual numbers depend on your VNC client, scene motion and screen area outside the viewer. Measure your own session using the test in the next section.

Fifteen FPS is a practical setting for editing. Cuts happen at a specific frame, not mid-motion, so the lower update rate rarely affects editing accuracy while roughly halving bandwidth.

Running a Bandwidth Test Before You Commit a Session

Do not rely only on a generic speed-test site; measure the real session:

1. Connect to the remote Mac through your VNC client at the resolution you plan to edit at.
2. On the Mac, open Activity Monitor's Network tab, or run nettop -P -J bytes_in,bytes_out in Terminal, and note the interface carrying the VNC session.
3. On your local machine, start a network monitor (Windows: Task Manager → Performance → Ethernet/Wi-Fi, or Get-NetAdapterStatistics in PowerShell; macOS: nettop).
4. Play a 60-second proxy clip in FCP at the viewer size you will actually use.
5. Record the average sustained throughput during playback and compare to the table.

If you are above a comfortable fraction of your uplink, reduce VNC color depth from 32-bit to 16-bit, drop the session frame rate from 30 to 15, or transcode to a smaller proxy frame size (50% → 25%). Each step typically cuts the stream by 30–50%.

VNC Clients Worth Using for Video-Heavy Work

Not every VNC client exposes the controls that matter here. These three do:

For the lowest latency on a stable link, RealVNC Viewer at High quality with ZRLE or Tight is a reasonable starting point. TigerVNC gives finer numerical control, useful when you are dialling in a hard bandwidth ceiling on a shared connection.

When to Upgrade and What Changes

The M-series entry plan at $95/month covers solo editing of a single FCP library. When your work grows, two upgrades are worth asking about in the quote:

• More RAM and faster disk. FCP uses RAM aggressively for background rendering and proxy generation; beachballs between projects usually point there. Specify your working library size and typical media footprint when you request a configuration.
• Managed Build Mac at $249/month. Includes CI setup, backups, monitoring and 30 minutes of monthly support — useful if the same Mac also runs overnight export or render jobs you want supervised.

The $29 virtual Intel macOS plan is not the right host for FCP timelines; keep it for text, scripting and compatible Intel toolchain work. Physical M-series plans and the i3 $49 tier currently collect requests until supply is confirmed, so place your request early if you have a start date.

Start your M-series Mac request at figment.com/mac-hosting/start.

Related Reading

• Time-scheduled remote Mac access
• Remote Mac support technician access
• Mac GitHub Actions self-hosted runner