The moment you leave town, a client will ask for a revision on a project from two years ago. This is a universal constant in post-production, right up there with drives filling up on Fridays and clients requesting "just a small change" that requires a full re-export.

When you keep everything, the problem is not finding the project. The problem is accessing it from a hotel room in another country with mediocre Wi-Fi.

Remote Desktop: The Brute Force Approach

The fastest way to access a large archive remotely is to not move the files at all. Instead, remote into the machine that already has them.

Parsec is the tool that makes this work for editing. Unlike generic remote desktop apps, Parsec was built for low-latency video. It streams your desktop at high frame rates with hardware encoding, which means you can actually scrub a timeline without wanting to throw your laptop out a window.

From over 5,000 miles away in the Swiss Alps, the latency sits around 150 milliseconds. That is just enough to feel slightly off, like editing through a thin pane of glass. Precise trimming is annoying. But rough cuts, review passes, and color adjustments are all perfectly workable. For a quick client revision, it gets the job done without transferring a single byte.

The limitation is obvious: you need a solid internet connection on both ends, and your home machine needs to be on and accessible. A NAS with wake-on-LAN and a static IP or dynamic DNS setup handles the second part. The first part depends on wherever you happen to be.

Proxies on Dropbox: The Portable Approach

For situations where the connection is too slow or unreliable for remote desktop, proxies are the answer.

The workflow is straightforward. Before leaving, transcode your active projects to lightweight proxies. H.265 or AV1 at a low bitrate will compress a 500 GB project down to something that fits on a laptop drive. Save those proxies into a Dropbox folder, let them sync, and you have a portable version of your edit that works offline.

AV1 in particular is worth the encode time. It produces remarkably small files at decent quality. A 4K ProRes source that takes up 2 TB can compress to AV1 proxies that fit in under 50 GB. The tradeoff is that encoding is slow, but if you start the job the night before you fly out, it is ready by morning.

Once you are on location, reconnect the proxies in your NLE, make your edits, and the project file itself is small enough to sync back through Dropbox in seconds. When you get home, relink to the original media and export.

When Neither Option Works

Sometimes the footage you need is not on an active project. It is buried in an archive, and you do not have proxies for it. In that case, there are two choices: remote in and start the transcode job remotely, or accept that this revision waits until you are back at your desk.

Having a well-organized archive makes the first option viable. If your projects are structured consistently and your NAS is accessible, you can remote in, kick off a proxy encode, and check back in a few hours. If your archive is a pile of unlabeled drives, you are out of luck until you land.

The Real Cost of Keeping Everything

Storing 100 TB is not free. Drives, enclosures, electricity, cloud sync subscriptions, and the occasional replacement when a disk fails. The running cost adds up.

The question worth asking is how much of that 100 TB you actually need. Camera originals and final deliverables, absolutely. But render files, unused B-roll, and orphaned media from projects that wrapped years ago might be inflating that number significantly.

The Clip Sweeper storage calculator can help you model what your archive actually costs to maintain, and whether trimming the dead weight would change the math on your storage setup. Sometimes the cheapest terabyte is the one you do not have to store at all.