Why Parsec for a Remote Mac?
Parsec is a remote desktop protocol built for interactivity: hardware-accelerated H.264/H.265 encoding, 60 fps streaming, and client-side rendering tuned for low latency. Where classic VNC redraws the screen and struggles past 15-20 fps, Parsec feels close to sitting in front of the machine, which is exactly what you want for video editing, design work, or any UI-heavy workflow on a cloud Mac.
Because every My Remote Mac server is a dedicated physical Mac Mini with full root access, you can install and run the Parsec macOS host like on any Mac you own. No virtualization quirks, no locked-down environment: the Apple Silicon media engine handles the encoding in hardware.
-
Up to 60 fps streaming
Fluid scrolling, smooth timelines, and responsive UI, far beyond what VNC delivers.
-
Hardware H.265 encoding
Apple Silicon's media engine encodes the stream with near-zero CPU overhead.
-
Low latency by design
Parsec's protocol is built for low latency, ideal for precise cursor work.
-
Free for personal use
The individual Parsec plan costs nothing; Teams plans add admin features.
Requirements
You need very little to get started:
- A dedicated Mac Mini server with admin access. Any My Remote Mac plan works (from $85/mo, USD, excl. tax).
- A free Parsec account and the Parsec client on your local machine (Windows, macOS, or Linux).
- macOS 10.15 or later on the host, which every recent macOS release covers.
- About 10-50 Mbps of bandwidth on your side for a comfortable 1080p-1440p stream.
Our Mac Minis run headless in the datacenter (no physical monitor attached). Parsec needs an active display to stream, so the virtual-display step below is required. It takes two minutes and works reliably.
Step 1: Install Parsec on the Server
Connect to your server with the VNC access included in your plan (or SSH), then install the Parsec macOS host:
# Install Parsec via Homebrew (over SSH or VNC)
brew install --cask parsec
# Or download the official installer, then open it in your VNC session
curl -L -o parsec-macos.pkg "https://builds.parsec.app/package/parsec-macos.pkg"
open parsec-macos.pkg
Launch Parsec, sign in, and enable hosting in the settings. macOS will ask for two permissions. Grant both in System Settings → Privacy & Security:
- Screen Recording, required for Parsec to capture the display.
- Accessibility, required for remote keyboard and mouse input.
- Approve the prompts over your VNC session, then restart Parsec so the permissions take effect.
Step 2: Virtual Display for Headless Streaming
This is the step most tutorials skip, and the number one reason a fresh Parsec install shows a black screen or a tiny low-resolution desktop: a headless Mac has no display for Parsec to capture. Datacenter Mac Minis run without a monitor, so you create one in software.
A virtual display utility such as BetterDisplay registers a full-resolution virtual screen with macOS. Parsec then captures and streams that screen exactly as if a monitor were plugged in:
# Install BetterDisplay (virtual display utility)
brew install --cask betterdisplay
# Then in BetterDisplay:
# 1. Create a new virtual screen (e.g. 1920x1080 or 2560x1440)
# 2. Set it as the main display
# 3. Parsec now streams this display at full resolution
Set the virtual display as the main display. After a reboot, Parsec needs an open desktop session: log in once over VNC, or use Parsec's login-screen build (Step 3) to log in through Parsec itself. If you later enable FileVault, remote unlock needs extra care: see our security guide.
Step 3: Auto-Start and Keep-Awake
Your server is designed for 24/7 operation, so sleep is already disabled. These commands keep it awake and start Parsec automatically, with your user session or, using Parsec's login-screen build, straight after every reboot:
# Keep the Mac awake permanently (already the default on our servers)
sudo pmset -a sleep 0 displaysleep 0 disksleep 0
# Start Parsec with your user session (runs once you are logged in)
osascript -e 'tell application "System Events" to make login item at end with properties {path:"/Applications/Parsec.app", hidden:false}'
# Unattended server: Parsec's login-screen build starts at the macOS login
# window after every reboot (wired network, FileVault off). Install it instead
# of the standard app, then open the installer in your VNC session:
curl -L -o parsec-macos-startup.pkg "https://builds.parsec.app/package/parsec-macos-startup.pkg"
open parsec-macos-startup.pkg
A login item starts Parsec once your user session is open: after a reboot, log in once over VNC or enable automatic login for your user. For an unattended server, install Parsec's login-screen build instead of the standard app. It starts at the macOS login window after every reboot and reopens Parsec after a crash; it requires a wired (Ethernet) connection and FileVault turned off.
Step 4: Performance Tuning
Out of the box Parsec already feels fast. A few settings squeeze out the rest:
- Codec: turn on H.265 (HEVC) in your Parsec client settings: better quality at the same bitrate, hardware-encoded on Apple Silicon, with an automatic fallback to H.264 if either side cannot use it.
- Bandwidth: raise the client limit to 30-50 Mbps for 1440p; our servers' network has headroom to spare.
- Resolution: match the virtual display to your local screen (e.g. 2560x1440) to avoid scaling blur.
- Color: Parsec's 4:4:4 color mode is available on Windows hosts only, not on a Mac host. For sharp text and UI, keep the virtual display at your screen's native resolution and give the stream enough bandwidth.
Parsec vs VNC vs RDP on macOS
Each protocol has its place. VNC (built into macOS as Screen Sharing) is dependable for administration; Parsec is built for fluid, all-day interactive use:
| Criteria | Parsec | VNC | RDP |
|---|---|---|---|
| Frame rate | Up to 60 fps | ~10-20 fps | ~30 fps |
| Latency feel | Near-local | Noticeable lag | Moderate |
| Encoding | Hardware H.264/H.265 | Software framebuffer | Software (no native macOS host) |
| Best for | Editing, design, daily driving | Admin tasks, setup | Windows hosts |
| macOS host support | Yes, native (Apple Silicon) | Built-in (Screen Sharing) | Third-party only |
In practice our customers keep both: VNC for provisioning and recovery (always available, no extra software), Parsec for day-to-day interactive work. My Remote Mac servers offer VNC and SSH. RDP is not available.
Troubleshooting
Black screen or 640x480 resolution after connecting
The Mac has no active display. Create a virtual display with BetterDisplay (see Step 2) and set it as the main screen, then reconnect.
"Host not available" after a reboot
macOS needs a logged-in user session for Parsec to attach to. Log in once via VNC after the reboot, and add Parsec to your login items so hosting starts automatically. To reach the login window through Parsec itself, use Parsec's login-screen build (see Step 3).
Choppy stream or artifacts
Lower the client bandwidth limit or switch to H.264 if your local network struggles; check that no VPN is adding latency. From the server side, our network has ample headroom for multiple 1440p streams.