How to edit video directly from cloud storage (without downloading everything)
18 min
red
“Edit from the cloud” gets used for three different setups, and they behave very differently when your project has 800 GB of footage in it. One makes a full copy of each file before you can work. One streams the pieces you play. One moves the editing software to the data instead of the data to you.
This guide explains each, what they cost you in disk space and bandwidth, how they behave in Premiere Pro, DaVinci Resolve and Final Cut Pro, and what to watch for when more than one editor touches the same project. It is about desktop editing software. Browser-based editors that open clips straight from a cloud drive are another option, but they suit short social edits more than long projects with heavy camera files.
Three ways to edit from the cloud
1. Sync and download
Dropbox, and Google Drive in its mirroring mode, work this way. A folder on your computer matches a folder in the cloud. Files you use are kept as full local copies.
Both tools have a way to save disk space. Dropbox calls it online-only: the file shows up as a placeholder, uses almost no space, and does not take your disk until you need it. But Dropbox’s own help page is explicit that opening an online-only file downloads it and makes it available offline, so you need enough free space for the whole file first. For a 40 GB camera file, that means waiting for 40 GB. Google Drive for desktop offers streaming and mirroring. Streaming keeps most files in the cloud and uses very little local space, but Google notes it needs a reliable connection. Mirroring stores a full copy on your computer.
Good for: small teams, light footage, documents, assets that get handed off rather than edited live, and people who want files local anyway.
Weak spot: large camera originals. The wait before the first frame can be long, and the local drive fills with copies you did not choose. Editing straight off a sync folder also leaves you to think about what is local and what is not.
2. Mounted streaming drives
Shade, LucidLink and Suite Studios all take this approach. A desktop app mounts the cloud storage so it shows up in Finder or File Explorer like a disk. Your editing software opens files from that drive. Behind the scenes the app fetches only the parts of a file you are reading and keeps recent parts in a local cache.
Shade’s Academy describes its mount (ShadeFS) as similar to how a video player streams: it streams the segments you need in real time rather than requiring complete downloads first. LucidLink describes its filespace as streaming data on demand, and Suite describes pulling only the data an editor needs at a given moment. These are vendor descriptions, so test any of them with your own footage and network.
Good for: teams that want one shared library where editors open the same files without copying them around.
Weak spot: the connection. Playback speed depends on the media’s bitrate against your sustained download speed, so a slow or Wi-Fi-only connection will stutter on heavy codecs. Proxies and wired internet help, and the video storage calculator shows how much data your camera format produces per hour.
3. Remote desktop and cloud workstations
Here you do not stream media to your computer at all. You connect to a powerful computer in a data center, with your footage close to it, and see its screen on yours. Suite Studios, for example, offers cloud-hosted virtual workstations where an editor runs Premiere Pro or DaVinci Resolve while the media stays on the Suite drive.
Good for: weak home connections, heavy sessions (effects, color, 8K), and freelancers who do not own a fast machine.
Weak spot: you are editing through a video feed of someone else’s computer, so latency, color accuracy and audio sync depend on the remote session. You also pay for the workstation by time or plan, on top of storage. Check current pricing with the vendor.
How they compare
Sync and download | Mounted streaming drive | Remote desktop or cloud workstation | |
|---|---|---|---|
Where editing runs | Your computer | Your computer | A computer in the cloud |
What crosses your connection | Whole files (once) | The parts you play | A screen video stream |
Local disk use | High unless set online-only | A cache you size | Almost none |
Start-up wait on a big file | Full download | Short, depends on bitrate | None, once connected |
Home internet matters | For the download | A lot for heavy codecs | For the screen feed |
Typical examples | Dropbox, Google Drive (mirror) | Shade, LucidLink, Suite | Cloud workstation services |
What happens to your local disk
With a mounted drive, “not downloading everything” does not mean no local storage. It means a bounded cache you control. Here is how Shade’s works, from its Academy:
The default cache is 26 GB, stored in a hidden .shade folder in your user directory. You can resize it (the minimum is 1 GB) or move it to an external SSD. Shade recommends a fast external SSD, and says the cache drive must be formatted APFS on macOS, NTFS or ReFS on Windows, or ext4, XFS or Btrfs on Linux. exFAT and Mac OS Extended do not work.
Every five minutes ShadeFS checks the cache. If it is over the limit, it removes the least recently used files until it is back to 90 percent. It removes whole files, never parts of files, so the cache should be larger than the largest file you work with or that file will keep being cleared and re-fetched.
Pinned files are exempt. Pin a file or folder and ShadeFS keeps a full local copy that does not count toward the cache size and survives restarts. You can then work offline. Watch your free disk space, because pins can fill the drive even when the cache looks small.
If the cache drive is nearly full, writes to the mounted drive can pause and uncached files may not open. The desktop app warns you first.
The cache is shared across every drive you mount.
One more local-disk item applies to every approach. Your editing software makes its own working files (media cache, peak files, render files, Resolve cache). Point those at fast local storage, not at the cloud drive, whatever you use for the footage. That is standard practice rather than something a cloud vendor decides.
Premiere Pro, DaVinci Resolve and Final Cut Pro
With a mounted drive the editing software sees ordinary files on a disk, so the usual import and relink steps apply.
Premiere Pro. Mount the drive, then import or drag clips from it like any other volume. Shade also has a Premiere Pro panel that lets editors search the library from inside Premiere, drop an exact sub-clip on the timeline, and see Shade review comments as frame-accurate timeline markers. You can export Shade metadata as an ALE file with a Premiere preset.
DaVinci Resolve. Resolve works through the mounted drive. Shade exports metadata as a CSV with a Resolve preset. Shade’s Academy notes a Resolve-specific detail: when importing that metadata, turn off “Match using clip start and end Timecode” in the import dialog.
Final Cut Pro. Shade works with Final Cut Pro through the mounted drive too. Apple documents that Final Cut Pro libraries can sit on shared storage using NFS or SMB (and Xsan), and that media can sit on any shared volume. Apple’s page does not describe several editors opening the same library at once, so plan on one editor per library unless your storage vendor documents otherwise.
Project files and working together
Footage is the easy half. The project file is where collaboration goes wrong, because an editing project is one file or database that several people might try to save at once.
Premiere Pro has project locking. When it is on, only one person gets write access to a project at a time, and others can open it read-only. Premiere creates a lock file (a .prlock file) beside the project, so it relies on the shared drive showing every user that file. Test that a second editor actually sees the lock on your cloud drive before you rely on it. Productions is Adobe’s feature for splitting a big show into several projects so editors can work in parallel. Locking is switched on in Premiere’s Collaboration preferences, once per workstation.
DaVinci Resolve collaboration runs through a shared project library, either on Blackmagic Cloud or on your own network with the free DaVinci Resolve Project Server, rather than a local library. Bins and timelines lock automatically while someone works in them, and stay read-only for everyone else. When you create a Blackmagic Cloud project you choose whether to sync no media, proxies only, or proxies and originals.
Final Cut Pro: one editor per library, as above.
On the drive itself, Shade shows every person who mounts a drive the same file tree. If you work offline and someone else changes the same file, ShadeFS keeps both versions: theirs under the original name, yours with “-conflict-“ and a number added to the name. Nothing is overwritten, and you pick which to keep. Shade’s documentation does not describe locking for project files, so rely on your editing software’s locking or a team convention.
For a fuller side-by-side of how each editing app shares projects, see the remote video editing workflow guide.
A simple working habit covers most of the risk: one named owner per project file, save new versions with a date or initials, and keep sequences you share in a separate project the owner updates. Shade also has version stacks for assets (cuts, graphics) that nest versions and compare them side by side, which is a separate matter from project file saves.
Setup checklist
Measure your connection (wired, at the time you normally work) and compare it with the bitrate of your footage. If it falls short, plan on proxies.
Install the desktop app and mount the drive. In Shade’s app: find the drive in the left panel, click the menu with three dots, choose Mount Drive. On macOS it appears under /Volumes. Workspace owners and admins can set a custom mount path per drive.
Set the cache. Put it on an external SSD if you can, formatted APFS, NTFS or ReFS, or a Linux format listed above. Set it larger than your biggest file.
Keep your NLE’s media cache and render files on a local SSD.
Pin what you must have offline or cannot risk stuttering, like the footage for tomorrow’s session.
Agree who owns the project file and how you name versions.
For big imports, use the web or desktop app upload. Shade recommends this over copying through the mount for more than 1,000 assets or 100 GB.
Run a 20-minute test edit before the team commits.
When another approach is the better call
If your team works on light footage and mostly shares finished files, a sync tool you already pay for is probably enough. If you only need a mounted drive and do not need Shade’s search, review and client sharing, Shade’s own comparison page says LucidLink is the better choice (see Shade vs LucidLink). If your connection cannot be fixed and your work is heavy, a cloud workstation can be the right call. And if several editors need to work in the same Resolve project at once, that is handled by Resolve’s collaboration tools rather than by storage.
If a shared, searchable library you mount like a disk sounds right for your team, you can see how it works on the features page or check pricing, which starts at $29.75 per seat per month billed annually. For general advice on remote setups, including bandwidth and review, see the same remote workflow guide.
Paying for storage, review and sharing separately?
Shade does all three from $29.75 per seat a month (billed annually), with 500 GB of storage per seat.