# Fyle for design studios

**Client work in every design app, with renders reviewed before they change**

Studios keep client projects, brand assets and renders in shared folders that designers, art leads and now AI agents all touch. Fyle is a desktop drive where a save never silently replaces someone else’s work, and where an art lead can approve what an agent changed.

## Design files can’t be merged

Design files are binary. When two people save the same file, a drive can only keep one, make a conflicted copy, or lock the file. None of these tells the art lead what happened.

Agents can resize assets, write alt text or prepare exports. Studios want that help without an agent replacing a master file.

## How Fyle fits

Available now:

- Organisations with roles: owner, admin, billing, member and viewer. (Available now)
- Two-factor sign-in with an authenticator app, which an organisation can require for everyone. (Available now)

Planned:

- Client folders mount in Finder and File Explorer and open in the design apps you already use. (Planned: desktop launch)
- A save based on an older version becomes a branch, and the reviewer compares both versions side by side. (Planned: review)
- Review rules such as /renders/ to the art leads. (Planned: review)
- Agents work in their own session; new exports land, and edits to masters go to review. (Planned: agent layer)

## An agent at work

The agent exports the logo set into a new folder and writes alt text. It also tries to tidy the layers in the master file, which policy protects, so that edit becomes a branch.

```
$ cd ~/Fyle/clients/northwind/brand-2027
$ fyle agent claude --task "Export the logo set at web sizes and write alt text for each"

Session ended · 3 changes
  exports/web/ (14 files)  new
  exports/web/alt-text.md  new
  masters/logo.ai          branched (protected folder)
15 files landed. 1 branch waiting for review by @art-leads.
```

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

## Client confidentiality and ownership of the work

- Every version records who made it, or which agent session, which helps show how a piece of work developed.
- Agents can only reach the client folders you grant them, with short-lived access (planned).
- Organisation roles already let you separate who can manage billing, members and settings.

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

## Related comparisons

- [Fyle vs Dropbox](https://fyle.sh/compare/fyle-vs-dropbox)
- [Fyle vs Box](https://fyle.sh/compare/fyle-vs-box)
- [Fyle vs LucidLink](https://fyle.sh/compare/fyle-vs-lucidlink)

## Sources

Last checked: October 2026.

1. [Fyle vs Dropbox (sourced comparison)](https://fyle.sh/compare/fyle-vs-dropbox)
2. [Fyle vs Box (sourced comparison)](https://fyle.sh/compare/fyle-vs-box)
3. [Fyle vs LucidLink (sourced comparison)](https://fyle.sh/compare/fyle-vs-lucidlink)