The problem with AirDrop at agency scale

AirDrop is one of the most quietly useful things Apple ever shipped. A designer hands a PSD to a colleague across the desk. An account director sends a quick reference to a client at a meeting. A photographer pulls a camera card and beams the day’s selects to an editor. For moments like those, AirDrop is the right tool. Fast, no setup, no friction.

The problem starts when a creative team that uses AirDrop a hundred times a week begins treating it as the file system. By the time anyone notices, there are seven versions of the campaign deck across as many laptops, the latest brand guidelines live on someone’s iPad that is currently in a coffee shop in Inglewood, and the producer who needs the final cut cannot find it because it was AirDropped to her phone three weeks ago and has since been deleted.

None of this is a failure of AirDrop. AirDrop is doing exactly what it was designed to do: hand a file from one device to another. It is the team’s use of it that has drifted past what it was designed for.

The cost of using AirDrop where a team file system belongs shows up in small ways at first and large ways eventually. Small ways: a producer asks where the final files are and gets four different answers, and seven copies of a 4 GB asset are quietly consuming nearly thirty gigabytes of laptop storage across the team. Large ways: a senior designer leaves, and most of the institutional knowledge leaves with them because everything was on their MacBook.

What a team file system actually looks like

The specifics vary by agency, but the shape is consistent. A central storage system (cloud-hosted, an on-premises file server, or a Mac-friendly NAS) becomes the single source of truth. Permissions are set by role and project. Old versions are kept automatically. External clients get scoped, time-limited access without needing an Apple ID. Backups are real, tested, and complete. Onboarding a new designer takes an hour because everything they need is in one place.

For Apple-first studios the options include shared storage on a Synology or QNAP NAS with macOS-friendly protocols, a cloud system like Dropbox Business or Google Workspace, or a hybrid setup that combines fast local storage with cloud replication. The right choice depends on file sizes, team size, and how often external collaborators need in.

The layered approach

This is not a choice between AirDrop and a team file system. It is recognising that they solve different problems. AirDrop stays in the toolbox for the moments it is good at. The team file system handles everything that needs to survive past today.

When to think about this

You will know it is time when you cannot find the file you need without asking three people, when a project’s “final files” depend on which laptop you happen to be looking at, or when an external client asks for access and the workflow involves emailing them a 4 GB zip. At that point, AirDrop is doing what it can. The team needs the rest of the toolkit.