Shipping SSDs to your editor is not a workflow

The SSD shuttle has been the default for decades. It works, until it doesn't.

Every production has a version of this ritual. The shoot wraps. Someone copies the camera cards to a portable drive. That drive gets labelled, maybe with tape, maybe with a marker, maybe with a sticky note that falls off in transit. Then it gets handed to the editor, or put in a Pelican case and shipped across the country via FedEx.

For co-located teams working in the same building, this is quick enough. The editor walks down the hall, picks up the drive, plugs it in, and starts cutting. The friction is low. But the moment your editor is in a different city, or your colourist is freelance, or your producer needs to review selects from home, the SSD shuttle starts to break down in ways that are easy to overlook until they cost you a deadline.

The real cost of shipping drives

The obvious cost is time. A FedEx shipment takes a day at best, sometimes two or three. If you are working across international borders, customs adds another layer of delay. For a production that wraps on Friday, this means the editor might not have footage until Tuesday or Wednesday of the following week. That is three to four working days of dead time built into your schedule, repeated every time new footage needs to move.

The less obvious cost is risk. Drives fail. They get dropped in transit, they overheat in delivery vans, they occasionally go missing entirely. Anyone who has been in production long enough has a story about a lost drive, and the scramble that followed. Some productions mitigate this by shipping two copies, which doubles the cost and only partially addresses the problem.

Then there is the versioning question. When drives circulate between multiple people, keeping track of which drive has the latest cut, the approved selects, or the most recent colour grade becomes its own project management challenge. You end up with a spreadsheet tracking drive locations, or a Slack channel full of messages like "which drive has the V3 selects?" and "did anyone send the drive back to the colourist?"

None of this is catastrophic on its own. Productions have managed with this system for years, and many still do. But it is worth examining whether the friction is necessary or simply familiar.

How cloud-based media management changes the model

Cloud-based media asset management platforms like Fabric (https://fabric.so/features/your-cloud) offer a different approach. Instead of copying footage to a physical drive and shipping it, you upload the media once to a centralised cloud library. From that point, anyone with access can stream the footage on demand without downloading it to their local machine.

This eliminates the transit delay entirely. The moment footage is uploaded, it is available to the editor, the producer, the colourist, and anyone else on the team. There is no waiting for a drive to arrive, no tracking shipments, no worrying about whether the drive survived the journey.

Fabric's cloud drive (https://fabric.so/features/your-cloud) is designed around this principle. Files live in the cloud and stream on demand, which means your editor can start scrubbing through footage without waiting for a full download. For review and selects, this is often sufficient. The editor can mark selects, build rough assemblies, and move through the editorial process while the full-resolution files continue to be available in the background.

Feedback without the email chain

One of the quieter advantages of moving to a cloud-based system is what it does to the review process. In the SSD shuttle model, feedback typically happens over email or in a call. The producer watches a cut, takes notes with timecodes, and sends those notes in a message. The editor reads the notes, cross-references the timecodes, and makes changes. If the timecodes are off by a few seconds, or the note is ambiguous, there is a back-and-forth to clarify.

Fabric's annotation tools (https://fabric.so/features/annotations) allow timestamped comments directly on the video timeline. A producer can scrub to the exact moment, leave a note, and the editor sees that note pinned to the precise frame. For audio, the same timestamped approach works. For images, annotations can be drawn directly on the file. This keeps feedback specific and reduces the gap between what the reviewer means and what the editor understands.

This matters most when multiple people are reviewing the same piece. Instead of collating feedback from three separate email threads, all notes live on the asset itself. The editor opens the file and sees every comment in context.

Finding footage without remembering where you put it

Large shoots generate enormous volumes of media. A multi-day production might produce hundreds of clips, thousands of photos, and dozens of audio files. In the SSD shuttle model, finding a specific clip means remembering which drive it is on, plugging that drive in, and navigating a folder structure that made sense to whoever organised it on set.

Fabric's semantic search (https://fabric.so/features/search) takes a different approach. Instead of searching by filename or folder path, you search by meaning. If you need the interview clip where the subject talks about their childhood, you search for that concept, and the system surfaces the relevant files. This works across video, audio, images, and documents.

For productions that accumulate media over weeks or months, this becomes increasingly valuable. The alternative is maintaining a detailed logging spreadsheet, which someone has to build and keep current. Semantic search does not replace careful media management, but it does make it far easier to locate material when the folder structure fails you.

Organisation that does not depend on one person's system

Every production has someone who "knows where everything is." They built the folder structure, they remember the naming convention, and they can find any file in thirty seconds. This works brilliantly until that person is unavailable, or until the project gets handed off to someone new.

Fabric's smart organisation features (https://fabric.so/features/smart-organization) help reduce this dependency. Files can be organised by project, by type, by date, or by any taxonomy that makes sense for the production. Combined with semantic search, this means a new team member can find what they need without a guided tour of someone else's folder hierarchy.

Client review without shipping another drive

Client review is another area where the SSD shuttle model creates unnecessary friction. In the traditional workflow, you either ship the client a drive with the cut (adding another round of transit time), upload a compressed version to a file-sharing service (losing quality), or schedule a supervised screening session.

Fabric's publish feature (https://fabric.so/features/publish) allows you to create polished, shareable review pages with link analytics. You send the client a link. They watch the cut in their browser, leave timestamped feedback, and you can see when they viewed it and how far they got. No drives to ship, no downloads to manage, no quality compromises.

Connecting the tools you already use

Most productions already use some combination of Google Drive, Dropbox, or Frame.io for various parts of their workflow. Fabric's connections (https://fabric.so/connections) integrate with these services, which means you do not have to abandon your existing storage. You can connect your Google Drive or Dropbox account and access those files through Fabric's interface, gaining the benefit of semantic search and annotations on top of your current file structure.

This is particularly useful during a transition period. You do not have to move everything at once. You can start by connecting your existing storage, using Fabric as the search and review layer, and gradually shift more of your workflow as the team gets comfortable.

The bandwidth question

It would be dishonest to pretend that cloud-based workflows solve every problem. The elephant in the room is bandwidth. A multi-camera shoot producing several terabytes of RAW footage per day presents a genuine upload challenge. If you are shooting in a remote location with limited internet access, getting that footage into the cloud quickly may not be practical.

This is a real constraint, and it is worth being clear-eyed about it. For these scenarios, the initial ingest may still involve physical media. The footage gets copied to drives on location, and those drives get brought to a location with sufficient upload bandwidth. The difference is that once the footage is in the cloud, it stays there. You are not shipping drives back and forth for the rest of the post-production process.

For the majority of productions, though, bandwidth is less of a barrier than it used to be. Fibre connections capable of sustained upload speeds of 100 Mbps or more are common in most urban areas. A terabyte of footage at 100 Mbps takes roughly 22 hours to upload. That is not instant, but it is often faster than waiting for FedEx, and the upload can happen overnight while the team sleeps.

Proxy workflows also help here. Many productions already generate lower-resolution proxy files for editing. These are a fraction of the size of the original media and upload much faster. The editor works with proxies during the creative edit, and the full-resolution files are available in the cloud for finishing.

When the SSD shuttle still makes sense

There are legitimate cases where physical media remains the right choice. On-set workflows that require immediate playback, shoots in locations with no internet connectivity, and productions dealing with extremely sensitive material that cannot leave physical control all have valid reasons to stick with drives.

Physical media still has a place, but the SSD shuttle as a default workflow, the assumption that footage always moves on drives, deserves re-examination. For most productions, particularly those with remote team members, the cloud-based alternative is faster, safer, and less prone to the versioning chaos that plagues multi-drive workflows.

The AI layer

Fabric's AI assistant (https://fabric.so/features/ai-assistant) adds another dimension to cloud-based media management. Beyond search and organisation, the AI can help with tasks like generating summaries of video content, identifying key moments in footage, and answering questions about your media library. For productions managing large volumes of content, this kind of intelligent assistance can save hours of manual logging and review.

Making the shift

Moving from an SSD shuttle workflow to a cloud-based system does not have to happen all at once. A practical starting point is to run both systems in parallel for a single project. Upload the footage to Fabric while also keeping your drive-based backup. Use the cloud system for review, feedback, and selects. Keep the physical drives as your archive and safety net.

Most teams that try this approach find that the cloud workflow quickly becomes the primary path, with physical drives relegated to archival storage. The speed of feedback, the elimination of transit delays, and the ability to search and find footage without plugging in the right drive make a compelling case on their own.

The SSD shuttle served the industry well for a long time. For co-located teams cutting a single project, it still works fine. But for remote collaborations, multi-stakeholder review processes, and productions that value speed over tradition, the cloud-based alternative is worth serious consideration.

Frequently Asked Questions

How do I send large video files to a remote editor?

Cloud-based media asset management platforms like Fabric allow you to upload footage once and give your editor streaming access. Instead of copying files to a drive and shipping it, the editor can scrub through and work with the footage directly from the cloud. This eliminates transit delays and the risk of lost or damaged drives.

Is cloud upload fast enough for professional video workflows?

For most productions, yes. A standard fibre connection at 100 Mbps can upload a terabyte in roughly 22 hours. Proxy workflows can speed this up considerably, as proxy files are a fraction of the original file size. The upload can run overnight, and in many cases footage is available to the editor faster than a shipped drive would arrive.

What happens if my internet goes down during upload?

Most cloud platforms, including Fabric, handle interrupted uploads gracefully. The upload resumes from where it left off rather than starting over. This makes large uploads more resilient than they might seem at first glance.

Can my editor work with footage without downloading it?

Yes. Fabric's cloud drive (https://fabric.so/features/your-cloud) streams files on demand. Your editor can scrub through footage, review clips, and work with proxy files without downloading the full-resolution originals to their local machine.

How do I keep track of which version of a cut is the latest?

In a cloud-based system, there is one centralised location for all media and project files. Version confusion, the "which drive has V3?" problem, largely disappears because everyone is working from the same library rather than passing drives back and forth.

Is it safe to store production footage in the cloud?

Cloud storage providers typically offer redundancy and backup that exceeds what a single physical drive provides. A portable SSD has one copy of the data. Cloud storage generally maintains multiple copies across geographically distributed data centres. The risk of data loss from a dropped or failed drive is arguably higher than the risk of cloud storage failure.

Can clients review cuts without downloading anything?

Yes. Fabric's publish feature (https://fabric.so/features/publish) lets you create shareable review pages. Clients watch the cut in their browser, leave timestamped feedback, and you can see viewing analytics. No downloads, no drives, no scheduling a screening room.

Does Fabric work with footage stored in Google Drive or Dropbox?

Yes. Fabric's connections feature (https://fabric.so/connections) integrates with Google Drive, Dropbox, Frame.io, and other services. You can access and search files from these platforms through Fabric without moving them out of their current storage.

What about very large shoots with terabytes of RAW footage per day?

For extremely large shoots or remote locations with poor connectivity, the initial transfer may still involve physical media brought to a location with good bandwidth. The key difference is that once footage is in the cloud, it stays there. You eliminate the ongoing back-and-forth shipping of drives through the rest of post-production.

Does Fabric work offline?

Fabric does not have offline support. It is a cloud-based platform that requires an internet connection. For on-set workflows in locations without connectivity, you will still need local storage for the initial capture and ingest phase.

Related pages

• What is a MAM and why you need one

• DAM vs MAM explained

• Video production workflow that doesn't fall apart

• Search fatigue in media production

• Your laptop shouldn't decide what you can work on

• Why you still carry an external hard drive