# Fyle for video teams

**Footage and projects on every edit seat, with agents that log, not overwrite**

Video teams share footage, project files and deliverables between editors, assistants and producers. Fyle is a desktop drive that streams files when they are opened, keeps every version of a project file, and lets AI agents do logging and transcription work alongside the team.

## Project files are fragile, and footage is large

Two people saving the same project file usually means one of them loses work, or someone has to dig through a conflicted copy.

Agents can now log clips, write transcripts and build selects. They need access to the same media as the editors, without being able to save over an edit in progress.

## How Fyle fits

Available now:

- Organisations with roles: owner, admin, billing, member and viewer. (Available now)
- Device sign-in for the desktop app and CLI: approve a short code in the browser, with no password typed into a terminal. (Available now)

Planned:

- Media mounts in Finder and File Explorer; files stream when opened and stay in a local cache you control. (Planned: desktop launch)
- A project file saved from an older version becomes a branch; the editor’s current version stays in place. (Planned: desktop launch)
- Agents run in their own session, so logs and transcripts land as new files and edits to shared projects go to review. (Planned: agent layer)
- Review rules by folder, for example /projects/ to the lead editor. (Planned: review)
- Bring your own S3-compatible bucket for footage you already keep in your own account. (Planned: Enterprise)

## An agent at work

The agent reads the interview audio exports, writes transcripts and a selects list, and suggests a change to the edit notes, which the lead editor was working on at the time.

```
$ cd ~/Fyle/productions/harbour-doc
$ fyle agent claude --task "Write transcripts for today’s interviews and a selects list for the edit"

Session ended · 3 changes
  transcripts/day-3-interviews.md  new
  selects/day-3.csv                new
  edit/notes.md                    branched (edited by the lead editor during the session)
2 files landed. 1 branch waiting for review by @lead-editor.
```

Illustration of a planned workflow. Names are examples; commands and output may change before release.

## Unreleased work and contributors’ data

- Agents only reach the productions you grant them, with short-lived access (planned).
- Every version records the person, device or agent session that made it.
- Footage and release forms can contain personal data, so UK GDPR applies. UK-only workspaces are planned for Enterprise.

Not legal advice. Fyle features mentioned here are planned unless marked available now.

## Related comparisons

- [Fyle vs Suite Studios](https://fyle.sh/compare/fyle-vs-suite-studios)
- [Fyle vs LucidLink](https://fyle.sh/compare/fyle-vs-lucidlink)
- [Fyle vs Dropbox](https://fyle.sh/compare/fyle-vs-dropbox)

## Sources

Last checked: October 2026.

1. [ICO: UK GDPR guidance and resources](https://ico.org.uk/for-organisations/uk-gdpr-guidance-and-resources/)
2. [Fyle vs Suite Studios (sourced comparison)](https://fyle.sh/compare/fyle-vs-suite-studios)
3. [Fyle vs LucidLink (sourced comparison)](https://fyle.sh/compare/fyle-vs-lucidlink)
4. [Fyle vs Dropbox (sourced comparison)](https://fyle.sh/compare/fyle-vs-dropbox)