Can you edit cloud video files offline?

18 min

red

You can, but only for files that are fully on your local disk before you lose the connection. A mounted cloud drive looks like a normal folder, which makes it easy to forget that most of what you see is not actually on your machine. Open a clip on a plane and you find out which files were really there.

Below: how mounted drives cache, what pinning actually guarantees, how much disk to set aside, what happens to your edits when you reconnect, and a checklist for travel and location days.

What a mounted cloud drive actually stores on your computer

A mounted cloud drive shows your whole library as a local volume, but it only downloads the parts of files you read. Those pieces go into a cache on your disk. Playback feels local because the cache is local, and the cache fills up as you work.

The cache has a size limit and old data gets evicted, so a file you opened last week may not be there today. With no connection, anything not cached cannot be opened at all.

So “offline editing” really means “make sure the files I need are fully downloaded and protected from eviction before I go offline.” Every tool below handles that step differently, and the differences matter on a trip.

Cache versus pin: the difference that decides whether you can work

A cache is temporary and automatic. A pin (or “make available offline”, or “mirror”) is a promise that a complete copy stays on disk.

Behavior

Cache (default)

Pinned or offline copy

What is stored

Pieces of files you read

A full copy of the file or folder

Removed automatically?

Yes, when space is needed

No, until you unpin

Works with no internet?

Only if you happened to read that data

Yes

Counts toward cache limit?

Yes

Depends on the tool

The last row is where tools differ most, so read the details for whichever one you use.

How Shade handles caching and pinning

The cache. ShadeFS, the part of the Shade desktop app that mounts your drive, keeps a cache of 26 GB by default in a hidden folder in your user directory. You can change the size (the minimum is 1 GB) and move the cache to another folder or an external drive. Shade recommends a fast external SSD and notes the cache drive must be formatted APFS (macOS), NTFS or ReFS (Windows), or ext4, XFS or Btrfs (Linux). exFAT and Mac OS Extended drives do not work. The cache size is shared across all mounted drives.

Every 5 minutes ShadeFS checks the cache. If it is over the limit, it removes the least recently used files until usage falls to 90% of the limit. It removes whole files, never parts of files, so Shade advises setting the cache larger than your largest single file. Otherwise that file keeps getting evicted and re-downloaded.

Pinning. To work offline, you pin a file or folder. In the Shade app you right-click and choose Pin to Cache. On macOS you can also do it in Finder on a mounted drive. Shade then downloads a complete copy to your cache directory. Per Shade’s documentation:

  • Pinned files are not subject to the cache size limit or eviction. You can pin as much as your disk holds.

  • You can pin without mounting the drive first.

  • Pinning a parent folder covers everything inside it.

  • Unpinning a file also deletes its local copy.

  • Files you open through the mounted drive download ahead of pinned files, so pinning slows down while you play media rather than the other way around. Shade’s troubleshooting guide suggests starting pins when you are not actively playing media if you have a deadline.

Because pinned files do not count against the cache size, a big pin can fill a disk even when the cache setting looks fine. If the cache drive nearly fills, Shade says files that are not already cached may not open and writes to the mounted drive pause. The desktop app warns you as space runs low, and the Cache Management screen shows how much space your pins use.

How much local disk to plan for

Disk planning is arithmetic: hours of footage you need offline, times the data rate of that footage, plus working room. The figures below are estimates built from published codec rates. Your footage will differ, so check a real clip’s data rate before you rely on them.

Published rates used here:

  • Apple ProRes 422 HQ, UHD (3840x2160) at 24p: 707 Mb/s, or 318 GB per hour (Apple ProRes white paper).

  • Apple ProRes 422 HQ, 1920x1080: about 220 Mb/s at 29.97 fps (Apple’s ProRes support page). Converting that to storage gives roughly 99 GB per hour (our calculation: 220 divided by 8, times 3,600 seconds).

  • Shade’s Academy lists typical 4K H.264 at 35 to 100 Mbps and 1080p H.264 at 8 to 15 Mbps.

Scenario (all estimates)

Math

Local space to pin

4 hours of UHD ProRes 422 HQ for a rough cut on location

4 x 318 GB

about 1.3 TB

6 hours of 1080p ProRes 422 HQ

6 x 99 GB

about 600 GB

6 hours of 1080p H.264 at the top of the range (15 Mbps)

6 x 6.75 GB

about 40 GB

10 hours of 4K H.264 at the top of the range (100 Mbps)

10 x 45 GB

about 450 GB

Then add working room. Renders, exports, cache files from your NLE and project files all land on your disk too. As a rough rule of thumb (an estimate, not a published figure), leave 15 to 25 percent free on top of the footage. Do not run a laptop internal drive close to full.

Camera-original ProRes does not fit on a laptop for long trips, so pin the shots you will actually cut, not the whole shoot. If your edit can run on lower-bitrate media, the pin shrinks a lot. Shade generates proxies automatically, and its Academy covers proxy workflows. The Academy does not say whether pinning grabs proxies, originals or both, so confirm that with Shade before you plan around it.

For bigger planning across a whole library, the video storage calculator is a better starting point, and remote video editing workflow covers the connection side. As a reference point, Shade’s own guidance is 25+ Mbps for 1080p and about 1 Gbps for 4K ProRes when working live from the cloud. Offline work removes that requirement for pinned files, which is the point.

What happens to edits you make offline

This is the part people worry about most, and the tools differ.

In Shade: changes made to pinned files while offline are marked as unsynced (“dirty”). Those files are protected from eviction until they sync, so nothing is lost if the cache fills. When you reconnect, or restart ShadeFS, Shade identifies changed files and syncs them to the cloud. If someone else changed the same file in the meantime, Shade keeps both versions. Their version keeps the original name, and yours is saved next to it with “-conflict-“ and a number added to the file name (Shade’s example is edit.prproj-conflict-2847193021). Nothing is overwritten. You compare the two and keep the one you want. The same applies if two people create a file with the same name.

For a Premiere or Resolve project file, that is the behavior you want, because a project file cannot be merged automatically anyway. The practical rule is the old one: only one person should be working in a given project file while you are away, and a quick message before you leave settles it.

In Dropbox: you can edit a file you made available offline. Dropbox says those changes do not reach other devices until you reconnect, then sync automatically. If someone edited the same file meanwhile, Dropbox’s help describes creating a “conflicted copy” with the editor’s name and date, and you merge by hand.

In Google Drive for desktop: Google offers two modes. Streaming keeps files mainly in the cloud and downloads them as needed. Mirroring keeps a full copy on your computer and in the cloud, with files always available offline. Google says video editing work is faster with mirrored files. The help page we reviewed does not describe how offline edits or conflicts are resolved on reconnect, so check Google’s current documentation or test with a throwaway file.

In LucidLink: you right-click and Pin. LucidLink’s documentation says pinned content is kept in the local cache until you unpin it, shows green when a pin is fully done and available offline, and keeps pinned folders live so teammates’ changes appear without re-pinning. It also says pinning can use up to 80% of your total cache, leaving the rest for streaming, so the cache size you set caps how much you can take offline. Check your cache setting before a trip, since LucidLink lets admins set a filespace-wide default. We could not find LucidLink documentation on conflict handling for offline edits in the pages available to us, so we are not describing it here. If you are weighing the two, see LucidLink vs Shade and LucidLink vs Dropbox.

Checklist: before you go offline

  1. Work out the footage you actually need and estimate disk using the math above.

  2. Check free space on the drive that holds your cache or offline files. Move the cache to an external SSD if the laptop is tight, and confirm the format works.

  3. Pin or mirror the media, the project file, music, graphics and any LUTs. People forget the small files.

  4. Pin early, on a good connection, and not while you are playing back footage.

  5. Confirm the pin finished. Look for the completed status in your tool rather than assuming.

  6. Open the project once with the network off (airplane mode) and scrub through clips.

  7. Tell your team you own that project file while you are away.

  8. When you reconnect, let syncing finish before closing the laptop, then check for conflict copies and decide which version to keep.

  9. Unpin what you no longer need so the disk is free for the next job.

Where this leaves you

Treat pinning as a packing step: decide what you need, check the disk, pin early, test with the network off.

Shade’s pricing starts from $29.75 per seat per month, billed annually, with unlimited AI indexing included. See pricing and the storage page for how drives work.

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.