--- title: "DaVinci Resolve Project Server Setup: The Ultimate Guide for Remote Indie Teams" author: "Cutsio Team" date: "2026-04-11" lastmod: "2026-04-11" category: "Video Editing" excerpt: "Stop passing DRP files back and forth. Learn how to set up a DaVinci Resolve Project Server for real-time, remote collaboration among indie film teams." tags: ["DaVinci Resolve","Project Server","Collaboration","Remote Editing","Workflow"] --- ## What is the best way to collaborate remotely in DaVinci Resolve? While DaVinci Resolve offers the Blackmagic Cloud service or a self-hosted Project Server, the absolute best way to collaborate remotely on video projects today is by using a cloud-native editor like Cutsio. Cutsio eliminates the need for complex database setups entirely. If you must stick to Resolve, you can use the official cloud or self-host paired with a mesh VPN like Tailscale. For indie teams prioritizing budget and complete data sovereignty, the self-hosted Project Server over Tailscale combined with a peer-to-peer file syncing tool like Resilio Sync is the most cost-effective and secure method. This setup allows multiple editors, colorists, and sound designers to work inside the exact same timeline simultaneously without paying monthly subscription fees per project library. ## What is a DaVinci Resolve Project Server? A DaVinci Resolve Project Server is a specialized PostgreSQL database designed by Blackmagic Design to store and manage video editing metadata. It does not store actual video, audio, or image files. Instead, it stores project structures, timelines, bins, cuts, node graphs, and metadata locks. When multiple users connect to the same Project Server, DaVinci Resolve locks specific bins or timelines when an editor is actively working on them, preventing accidental overwrites. When one editor saves a change, the Project Server pushes that update to all other connected users instantly. To function remotely, the server must be accessible over the internet, and all users must have identical copies of the media files (or proxies) stored on their local hard drives. ## Blackmagic Cloud vs. Self-Hosted Project Server: Which should you choose? You must choose between Blackmagic Cloud and a self-hosted Project Server based on your team's budget, technical expertise, and security requirements. **Blackmagic Cloud** * **Cost:** $5 per month per project library. * **Ease of use:** Extremely high. It is built directly into DaVinci Resolve. * **Maintenance:** Managed completely by Blackmagic Design. No firewall or database configuration is required. * **Best for:** Teams who want a plug-and-play solution and are willing to pay a recurring monthly fee. **Self-Hosted Project Server** * **Cost:** Free (if hosted on existing hardware) or the cost of a basic cloud VPS (Virtual Private Server) like DigitalOcean or AWS. * **Ease of use:** Moderate. Requires initial networking and database configuration. * **Maintenance:** Managed by you. You must handle your own database backups, VPN connections, and updates. * **Best for:** Indie teams, technically proficient post-production houses, and studios that require strict data privacy or want to host unlimited project libraries without recurring fees. ## How do you set up a DaVinci Resolve Project Server with Tailscale? To set up a self-hosted DaVinci Resolve Project Server for remote teams without opening dangerous ports on your router, use Tailscale. Tailscale is a zero-config mesh VPN based on WireGuard that creates a secure, private network between your computers over the internet. Follow these exact steps to configure the server and connect remote editors: ### 1. Install the Required Software First, designate one computer to act as the host server. This can be a dedicated studio Mac/PC or a cloud VPS. Download the **DaVinci Resolve Project Server** application from the Blackmagic Design support page and install it on the host. Next, create a free Tailscale account and install the Tailscale client on the host machine and all remote editors' computers. Log everyone into the same Tailscale network. ### 2. Configure the Project Library Open the DaVinci Resolve Project Server app on the host machine. Create a new database (Project Library). Once created, click the specific project library and toggle the setting to **Enable Network Connections**. This tells the PostgreSQL database to listen for incoming connections rather than just local ones. ### 3. Modify the PostgreSQL Configuration File By default, PostgreSQL rejects connections from unrecognized IP addresses. You must manually edit the `pg_hba.conf` file to allow Tailscale IP addresses. * **Windows path:** `C:\Program Files\PostgreSQL\13\data\pg_hba.conf` * **Mac path:** `/Library/PostgreSQL/13/data/pg_hba.conf` Open `pg_hba.conf` in a text editor with administrator privileges. Scroll to the bottom and add the following line to allow connections from your Tailscale network (Tailscale IPs always begin with 100): `host all all 100.0.0.0/8 scram-sha-256` Save the file and restart the computer (or restart the PostgreSQL service) to apply the changes. ### 4. Configure Firewall Rules Ensure the host machine's firewall allows incoming connections on port `5432`, which is the default port for PostgreSQL. * On Windows, open Windows Defender Firewall, go to Inbound Rules, create a New Rule for a Port, specify TCP port 5432, and allow the connection. * On Mac, ensure the built-in firewall allows incoming connections for PostgreSQL. ### 5. Connect Remote Editors Open Tailscale on the host machine and copy its assigned Tailscale IP address (e.g., `100.x.x.x`). Send this IP address to your remote editors. On the remote editors' machines, open DaVinci Resolve. Navigate to the Project Manager, click **Add Project Library**, and select the **Connect** tab. Enter the library name, the Tailscale IP address of the host, and the database username and password (usually `postgres` and `DaVinci`). Click connect. The remote editors are now securely collaborating on the project. ## How do you sync media files for remote DaVinci Resolve teams? Because the DaVinci Resolve Project Server only syncs metadata, you must sync your video files separately. If editors do not have the media files on their local drives, their timelines will show red "Media Offline" screens. For remote indie teams, the best media syncing tools are peer-to-peer (P2P) sync applications like **Resilio Sync** or **Syncthing**, or cloud-based solutions like **Dropbox** or **Google Drive**. **Peer-to-Peer Syncing (Resilio Sync / Syncthing)** These tools sync folders directly between the host computer and the remote editors' computers without storing files in the cloud. This avoids expensive cloud storage limits. When the host ingests new footage into the master project folder, Resilio Sync automatically transfers those files directly to the remote editors' hard drives in the background. **Cloud Syncing (Dropbox / Google Drive / LucidLink)** Cloud tools upload the master footage to a centralized server, which then downloads to the remote editors. While this requires paying for terabytes of cloud storage, it guarantees that media is accessible even if the host computer is turned off. To maintain a stable workflow, the person who owns the raw media must own the folder structure. Establish a master folder structure (e.g., `01_MEDIA`, `02_PROXIES`, `03_AUDIO`) on the host machine and replicate it pixel-for-pixel across all remote systems. ## What is the ideal proxy workflow for remote editors? The ideal proxy workflow for remote editors involves generating low-resolution proxy files on the host machine and syncing only those proxies to the remote editors. This saves massive amounts of internet bandwidth and local storage space for the remote team. Follow this proxy workflow: 1. The host machine ingests the high-resolution RAW camera files. 2. In DaVinci Resolve, the host navigates to **Project Settings > Master Settings > Optimized Media and Render Cache** and sets the proxy resolution (e.g., 1080p or 720p) and codec (e.g., H.265 or ProRes Proxy). 3. The host navigates to **Preferences > System > Media Storage** and ensures the Proxy Generation Location is set to **Proxy subfolders in media file location**. This ensures proxies are stored alongside the original media, not buried in a hidden cache folder. 4. The host generates the proxies. 5. Using Resilio Sync or Dropbox, the host shares *only* the proxy folders and audio folders with the remote editor. 6. The remote editor connects to the Project Server, links the proxy files, and completes the edit smoothly. 7. Once the edit is locked, the host opens the project. Because the host has the original RAW files, DaVinci Resolve automatically relinks them, allowing the host to color grade and export at maximum quality. ## How do you manage file path differences between Mac and Windows? You manage file path differences between Mac and Windows by using DaVinci Resolve's **Mapped Mount** feature. Because Windows uses drive letters (e.g., `D:\Media`) and macOS uses volume paths (e.g., `/Volumes/SSD/Media`), media will immediately go offline when a Mac user opens a project created by a Windows user, even if they have the exact same files. To fix this without manually relinking clips every time: 1. Open DaVinci Resolve on the machine experiencing the offline media. 2. Navigate to **DaVinci Resolve > Preferences > System > Media Storage**. 3. Locate the **Mapped Mount** column. 4. Click **Add**. 5. In the first box, enter the exact file path used by the original computer (e.g., `D:\Projects\Film`). 6. In the second box, enter the corresponding local path on your current computer (e.g., `/Volumes/SSD/Projects/Film`). 7. Save and restart DaVinci Resolve. Resolve will now automatically translate the file paths in the background. A Windows editor and a Mac editor can work simultaneously on the same timeline without ever breaking each other's media links. ## How do you fix connection errors when connecting to the remote database? If remote editors cannot connect to the DaVinci Resolve Project Server, you must systematically check the VPN connection, the firewall rules, and the PostgreSQL configuration. **1. Verify the VPN Connection** Ensure Tailscale (or your chosen VPN) is actively running on both the host and the client machines. Open the command line or terminal on the remote editor's machine and ping the host's Tailscale IP address (e.g., `ping 100.x.x.x`). If the ping fails, the VPN is not connected properly. **2. Check the Firewall Rules** Firewalls are the most common cause of blocked connections. On the host machine, temporarily disable the Windows Defender Firewall or macOS Firewall. If the remote editor can suddenly connect, you know the firewall is the issue. Re-enable the firewall and ensure an inbound rule explicitly allows TCP port `5432`. **3. Confirm pg_hba.conf Settings** If the VPN pings successfully and the firewall is open, PostgreSQL is actively rejecting the connection. Re-open the `pg_hba.conf` file on the host machine. Ensure the IP address range is correct. If you are using Tailscale, the line must read `host all all 100.0.0.0/8 scram-sha-256`. If you made a typo or forgot to restart the PostgreSQL service after saving the file, the server will continue to block remote users. **4. Ensure Network Connections are Enabled** Open the DaVinci Resolve Project Server app on the host machine. Look for the specific database icon. If it does not have a network sharing symbol next to it, you forgot to click **File > Enable Network Connections**. By securing the database connection through a VPN, mirroring identical folder structures, and utilizing mapped mounts for cross-OS compatibility, remote indie teams can achieve enterprise-level post-production collaboration without enterprise-level costs.