How to collaborate on a video project without mailing hard drives

Remote video collaboration that starts with solving the file access problem

Somewhere in the world right now, a hard drive is in a FedEx envelope on its way to an editor. It contains 400 GB of footage from a two-day shoot, and the editor cannot start work until it arrives. When it does arrive, the editor will spend an hour copying files to a local drive, discover that two clips are missing, and email the producer to ask for them. The producer will find the clips on a different drive, upload them to a file transfer service, and send a download link. The editor will download them overnight. This process is normal in video production, and it is remarkably slow for an industry that considers itself creative and fast-moving.

Remote video collaboration is difficult for a specific reason: the files are enormous. A ten-minute finished video might originate from 300 GB of raw footage. A feature-length documentary can involve multiple terabytes. These file sizes make the collaboration patterns that work for other creative fields, shared folders, real-time sync, cloud-based editing, either impractical or painfully slow when applied to video without rethinking the approach.

Where current collaboration tools fall short

The video industry has developed tools to address parts of the collaboration problem. Frame.io, Wipster, and similar platforms handle review and approval well. An editor uploads a cut, stakeholders leave timestamped comments, and the editor works through the notes. This solves the feedback loop for works-in-progress.

What these tools do not address is the underlying file access problem. The footage itself, the raw source media that the editor needs to build the timeline, still lives on local drives. Review platforms work with exported drafts, not source files. When a second editor joins the project, they need their own copy of the footage. When the colourist starts work, they need a copy too. Each copy takes time to transfer and risks drifting out of sync if anyone re-organises, renames, or adds to the media set.

Transfer services like Aspera, Masv, and Dropbox solve the "move large files" problem, and they do it well. But transferring files is different from sharing access to files. Every transfer creates a new copy, and every copy is a potential point of divergence. When the producer adds a new interview to the project, does every team member get it? When the assistant editor reorganises the bin structure, does that change propagate? With file transfers, the answer to both is: only if someone manually sends an update.

Cloud storage services like Google Drive and Dropbox can sync files, but they were designed for documents and photos, not for terabytes of video. Syncing 500 GB of ProRes files across four team members means storing 2 TB of identical footage across four machines, with sync conflicts as a constant risk. The storage costs are substantial, and the bandwidth required for initial sync can take days on standard internet connections.

The core problem: every collaborator needs every file

Video collaboration has a structural challenge that text-based and design-based collaboration does not. When two writers collaborate on a document, they share a file measured in kilobytes. When two designers collaborate on a Figma project, the assets stream from the cloud and neither designer stores the full project locally. Video has, until recently, required every participant to hold a complete local copy of the source media. This makes adding a collaborator an expensive operation, measured in time, storage, and bandwidth.

The solution is to separate file access from file possession. Collaborators need to be able to use the footage without each maintaining their own copy. This is the approach that Fabric takes.

A shared cloud media library

Fabric's cloud drive provides a shared workspace where media lives in the cloud and streams to each team member on demand. When an editor opens a clip, the data streams from Fabric's cloud to their workstation. They can scrub through footage, edit in Premiere Pro or DaVinci Resolve, and work with the media as if it were local, but the footage itself remains in a single cloud location that every authorised team member can access.

This changes the onboarding experience for new collaborators. Instead of shipping a drive or waiting for a multi-day transfer, a new team member gets access to the Fabric workspace and can begin working with the media immediately. The footage does not need to be copied, synced, or deduplicated. One copy exists, and everyone works from it.

For creative teams that work with external contractors, this is particularly valuable. A freelance colourist who needs access to the graded footage for a week does not need to receive and return a hard drive. They access the footage through Fabric for the duration of their engagement, and their access can be adjusted when the work is complete.

Finding footage without memorising folder structures

On a local drive, finding a specific clip means knowing where it was filed. Whose naming convention was used? Which drive holds the B-roll from day two? Is the interview with the CEO in the "Interviews" folder or the "Exec" folder? These questions consume surprising amounts of time, especially when multiple people have contributed to the media organisation over the life of a project.

Fabric's semantic search lets team members search for footage by its content rather than its filename or location. If you remember that a clip showed a wide shot of the factory floor, you can search for that and find it, regardless of what the file is called or where it sits in the folder hierarchy. This is useful for individual editors, but it becomes essential for teams, because it removes the dependency on shared organisational knowledge. A new editor joining the project mid-stream does not need a tour of the folder structure. They can search for what they need and find it.

Smart organisation adds another layer. Media is categorised and tagged based on its content, creating a navigable structure that does not depend on anyone having manually sorted every clip into the right bin. As the media library grows over the course of a project, this automated organisation becomes more valuable, because manual sorting tends to break down under time pressure, which is exactly when projects are at their busiest.

Replacing email threads with timestamped feedback

Feedback on video is inherently time-based. A note like "the transition at the start of section two feels abrupt" requires the reviewer to identify a moment in time and the editor to locate that same moment. When feedback travels via email or messaging, this mapping is imprecise. Reviewers describe moments in approximate terms, editors interpret those descriptions, and misunderstandings are common.

Fabric's annotation tools allow timestamped comments directly on video and audio assets. A reviewer can click on the exact frame they are referencing and leave their note anchored to that moment. For images and design assets, annotations can be drawn directly onto the visual. This eliminates the translation step where an editor must figure out which frame a reviewer is describing.

For teams working across time zones, timestamped annotations are especially helpful. A producer in London can review a cut in the morning, leave detailed time-anchored notes, and an editor in Los Angeles can work through those notes in their afternoon without needing a synchronous call to clarify which moments the notes reference. The feedback is precise enough to act on without discussion.

This also reduces the number of review exports an editor needs to create. Rather than exporting a draft, uploading it to a review platform, collecting feedback, and then returning to the timeline, the review can happen on the media within Fabric. Fewer exports means less time spent waiting for renders and uploads, and less local storage consumed by draft versions.

Sharing cuts with clients and stakeholders

Client review adds another layer of complexity to remote collaboration. Internal team members might be comfortable navigating a shared drive or a specialised review tool, but clients and external stakeholders often need something simpler: a link they can click to watch the latest cut.

Fabric's publish feature creates polished, shareable pages with link analytics. An editor can publish a cut as a clean presentation page, send the link to a client, and see whether and when the client viewed it. This replaces the pattern of exporting a file, uploading it to Vimeo or a file sharing service, and sending a link with no visibility into whether it was received or watched.

The link analytics component is quietly useful for project management. Knowing that a client has viewed a cut but not yet responded is different from not knowing whether they have seen it. It helps producers time their follow-up appropriately and reduces the uncertainty that slows down approval cycles.

Connecting existing storage into one workspace

Most production teams do not start from scratch. They have footage on Google Drive, project files in Dropbox, review assets in Frame.io, and raw media on local drives. A collaboration tool that demands a complete migration to a new storage system creates an adoption barrier that many teams cannot justify mid-project.

Fabric's connections bring existing storage services into the Fabric workspace. Google Drive, Dropbox, Frame.io, and other services can be connected so that media from those sources appears within Fabric alongside cloud-native assets. This means a team can begin using Fabric's search, annotation, and sharing capabilities on their existing media without first moving everything to a new location.

Over time, teams may choose to consolidate their media into Fabric's cloud storage for the streaming and access benefits. But the ability to start by connecting existing services lowers the threshold for adoption and lets teams experience the collaboration benefits before committing to a storage migration.

How this changes the production workflow

Consider a documentary production with a director in Manchester, an editor in Berlin, and a producer in Toronto. Traditional workflow: footage is shot, backed up to drives, drives are shipped or footage is uploaded to a transfer service, each team member downloads what they need, and communication about the footage happens via email with attached screenshots and timecodes.

With a shared cloud media library, the footage is ingested into Fabric's cloud workspace after the shoot. All three team members can access it immediately. The editor begins building a rough cut while the producer reviews raw footage and adds annotations identifying key moments. The director searches for specific interview passages using semantic search and leaves notes on the clips they want the editor to prioritise. When a rough cut is ready, the editor publishes it through Fabric and sends the client a review link. Feedback comes back as timestamped annotations. The entire review cycle happens without a single file being shipped, downloaded, or duplicated.

This does not eliminate every challenge of remote collaboration. Creative communication still requires calls and conversations. Time zone differences still affect responsiveness. But the logistical friction, the hours spent transferring files, the days waiting for drives, the confusion about which version of the footage is current, is substantially reduced.

Working with Fabric as a media asset management platform

Fabric functions as a media asset management (MAM) platform, which means it is designed specifically for the types of files and workflows that video production involves. This distinguishes it from general-purpose cloud storage, which treats a 200 GB ProRes file the same as a spreadsheet. Fabric understands media files, provides appropriate previews and playback, supports the metadata and organisational structures that production teams need, and enables the kind of search and discovery that makes large media libraries navigable.

The AI assistant adds a further dimension to working with large media sets. As projects accumulate footage across shoots, seasons, or campaigns, the ability to query the media library conversationally becomes a meaningful time saver. Rather than manually browsing through hundreds of clips, team members can describe what they are looking for and let the AI help locate relevant assets.

A note on connectivity

Fabric requires an internet connection. There is no offline mode. For teams working from well-connected studios and home offices, this is rarely an issue. For on-location work in areas with limited connectivity, source media would need to be captured and stored locally until it can be uploaded. This is a real limitation worth considering alongside the substantial benefits of cloud-based collaboration for the rest of the production workflow.

Frequently asked questions

How do I share large video files with a remote team?

Traditional options include shipping hard drives, using file transfer services like Masv or Aspera, or uploading to cloud storage. A cloud media workspace like Fabric takes a different approach: rather than transferring copies of files to each team member, everyone accesses the same media library in the cloud. This eliminates the need for individual transfers and ensures everyone works from the same set of files.

What is the best tool for remote video collaboration?

It depends on which part of the collaboration you are addressing. Frame.io and Wipster are strong for review and approval workflows. For the underlying file access and media management problem, Fabric's cloud workspace provides a shared environment where all team members can access, search, and annotate source media without maintaining individual copies.

How do you collaborate on a Premiere Pro project remotely?

The project file (.prproj) is small and easily shared. The challenge is the source media it references, which can be hundreds of gigabytes. Options include using shared network storage, syncing media via cloud storage, or using a cloud media platform like Fabric that streams source footage on demand so each editor can work from the same media without local copies.

Can multiple editors work on the same footage simultaneously?

With a shared cloud workspace, multiple editors can access and use the same source footage concurrently. Each editor works in their own Premiere Pro or DaVinci Resolve project file, referencing the shared media. Fabric's cloud drive provides this shared access layer, so editors do not need to duplicate footage across workstations.

How do I send video feedback with precise timecodes?

Fabric's annotation tools allow reviewers to leave timestamped comments directly on video and audio files. Click on the frame you want to reference, type your note, and it is anchored to that exact moment. This replaces vague email descriptions and ensures the editor can locate the precise point being discussed.

What is a media asset management (MAM) platform?

A MAM platform is software designed to store, organise, search, and manage media files throughout their lifecycle. Unlike general-purpose cloud storage, a MAM understands media-specific needs: video playback, frame-accurate navigation, metadata management, and production workflows. Fabric is a MAM platform that adds cloud-native access, semantic search, and collaboration features.

How do I organise footage for a remote team?

Clear folder structures and naming conventions help, but they depend on everyone following the same system. Fabric's semantic search and smart organisation reduce this dependency by making footage searchable by content and automatically categorising media. Team members can find clips by what they contain, not by where someone filed them.

Can clients review video cuts without downloading anything?

Yes. Fabric's publish feature creates shareable pages where clients can watch cuts directly in their browser. Link analytics show whether and when the client viewed the material. This replaces the cycle of exporting, uploading to a separate platform, and sending download links.

Does Fabric work with Google Drive or Dropbox?

Fabric connects to Google Drive, Dropbox, Frame.io, and other storage services through its connections feature. Media from connected services appears within your Fabric workspace alongside cloud-native assets, so you can use Fabric's search, annotation, and sharing tools on files that remain in their original storage location.

Is Fabric suitable for large-scale productions?

Fabric is designed as a media asset management platform, so it handles the file sizes and volumes typical of professional video production. The cloud-native architecture means storage scales with your needs, and the streaming model means individual workstations do not need to hold the full media set locally. For very large productions, the primary consideration is internet bandwidth for streaming high-resolution source media.

Related pages

• Your Cloud

• Search

• Smart Organisation

• Annotations

• Publish

• Connections

• AI Assistant

• Fabric for Video Editors

• Creative Teams

• Review and Approval