Blip: the file transfer app that changed how we hand off work

Every photo and video business has the same unglamorous bottleneck. It is not the camera and it is not the edit — it is the handoff.

Getting 400 GB of card offloads to an editor across the city. Getting a graded master to a client whose mail server rejects anything over 25 MB. Getting a photographer's full-resolution RAWs to a retoucher without a platform quietly re-compressing them on the way. Waiting three hours for an upload to finish so that somebody else can spend three hours downloading the same thing.

For years we solved that with a mix of WeTransfer links, shared Drive folders and — more often than we would like to admit — putting an SSD in an auto and sending it across Bengaluru.

Last year we found Blip. It has quietly replaced most of that, and it is the one tool from that year we would genuinely miss.

What Blip actually is

Blip is a peer-to-peer file transfer app. You install it on two devices, pick a file or a folder, and it goes directly from one machine to the other. There is no upload step, no link that expires, no bucket in the middle, and no server holding a copy of your footage.

That one design decision is what makes it interesting for production work, because nearly everything irritating about file delivery is a symptom of the upload-then-download model.

There is no size limit that matters. Blip is built for whole-project transfers rather than the "here is a 2 GB export" case, and people routinely move multi-terabyte folders through it. You are not looking for the tier that unlocks the size you need.

It sends folders, with the folder structure intact. A Premiere or Resolve project with its media, proxies and audio in the right subfolders arrives as a Premiere or Resolve project — not as a zip somebody has to unpack and relink. Same for a Pro Tools session, and same for a shoot folder that is organised by camera and card.

Nothing gets re-encoded. What leaves your machine is byte-for-byte what arrives. That matters more for stills than people expect: a lot of general-purpose sharing tools will helpfully "optimise" an image somewhere in the pipeline, and a retoucher does not want your helpfully optimised JPEG.

It resumes. A transfer that dies at 80% because a phone left Wi-Fi or a fibre link blinked picks up where it stopped rather than starting again. On a 300 GB transfer that is the difference between a tool you trust and a tool you fight.

It is encrypted end to end, over a mutually authenticated TLS 1.3 connection, so neither the wider internet nor whoever else is on the venue Wi-Fi can read what is going past.

It runs everywhere the work does — macOS, Windows, Linux, iPhone, iPad and Android. The phone apps matter more than they sound like they should, which we will come back to.

Where it fits in a photo and video workflow

The abstract pitch is "fast file transfer". The reason it stuck with us is much more specific than that. Here is where it earns its place.

Card offload to editor, in the same building

This is the one that surprised people on our team.

Blip has LAN direct connect: when both devices are on the same network, the transfer runs over that network instead of going out to the internet and back. Your broadband plan becomes irrelevant. A shoot drive moving from the DIT's laptop to the edit machine on the same switch goes at whatever the LAN can carry, which on wired gigabit is roughly 100 MB/s sustained.

Practically: a full day of multicam 4K can be on the editor's machine before the crew has finished packing down, and nobody had to find the drive, unmount it cleanly, walk it over and mount it again.

Rushes coming back from location

An overnight shoot ends at 1am and the edit starts at 9am. Historically that meant either someone driving footage back or someone babysitting a WeTransfer upload in a hotel room and watching it fail at 90%.

With Blip you point it at the folder and go to sleep. It resumes across network drops, and it keeps going as long as the sending machine stays awake — which is a real requirement, and we will get to that.

Full-resolution stills to a retoucher or a client

Photographers have a specific version of this problem: the deliverable is thousands of small-to-medium files rather than one big one, and most transfer tools handle that badly. Zipping 2,000 RAWs to get them through a link, then unzipping on the other side, is a tax paid twice.

Blip moves the folder as a folder. The retoucher gets the same tree you have, sidecars and all.

The finished master to the client

The output of a job is usually one large file — a ProRes master, a long-form event recording, a 4K cut for the client's own team to re-purpose. This is exactly the file that does not fit through email, gets re-compressed by chat apps, and hits the ceiling on a free transfer tier.

The client does need Blip installed, which is the friction point. In practice this has been fine for production companies, agencies and in-house marketing teams, and less fine for one-off clients who want a link they can forward.

Whole project folders, not just exports

The underrated case. Handing a project to another editor, moving a job to a freelancer, sending an archive copy to the client at the end of an engagement — these are all "send this entire directory, intact" operations, and they are the ones the link-based tools are worst at.

The honest limitations

We would rather you find these out here than three weeks in.

Both sides need the app. This is not a link you can drop in an email. For a regular collaborator that is a one-time setup. For a client you will deal with once, it is a real ask, and we still send those a link.

Peer-to-peer means somebody has to be online. A file cannot arrive from a machine that has gone to sleep. Handing something over and closing the laptop does not work the way it does with an upload-based service. Get in the habit of checking the transfer completed before you shut down.

It is not review and approval. There are no timecoded comments, no version stacks, no approval states. If your workflow lives on Frame.io or a similar review tool, Blip does not replace it — it replaces the part before it, where the media has to physically get somewhere.

It is not backup or archive. A transfer is a copy in flight, not a copy at rest. Your 3-2-1 backup plan is unchanged.

It is not a delivery portal. No download analytics, no expiring links, no password-protected landing page with your branding on it. If your client relationship needs that paper trail, keep the portal.

It does not fix your uplink — see below.

The India-specific bit

Worth being blunt about, because it decides whether Blip is transformative for you or merely convenient.

Most Indian broadband is heavily asymmetric. A "300 Mbps" home or small-studio connection often has an upload speed of a fraction of that. No transfer tool can send data faster than your upload link allows, and any product that implies otherwise is describing the download side.

So there are two quite different stories here.

Inside your own network, Blip is transformative. LAN direct connect sidesteps the internet entirely, and studio-to-studio transfers become limited only by your switch and your drives. If most of your handoffs are between machines in one building — DIT to edit, edit to grade, edit to the render box — this is the single biggest win available, and it is free.

Across the internet, Blip removes a step rather than adding bandwidth. The upload-then-download model makes you pay for the transfer twice: once going up, once coming down. Blip pays it once. That is a genuine saving of roughly half the wall-clock time, plus it removes the size ceilings and the expiry dates. But a 500 GB shoot going out over a 40 Mbps uplink is still an overnight job, and it will still be an overnight job on any tool you choose.

For the genuinely enormous handoffs, an SSD in a bag remains undefeated. We have stopped pretending otherwise.

What it costs

At the time of writing, Blip is free for non-commercial use — the Community plan, aimed at personal use, students, hobbyists and nonprofits — with a Business plan at around $25 per user per month (billed annually), which is what commercial use requires, and which comes with a 15-day trial.

If you are a working studio, you are on the paid plan. Priced per seat, that is roughly comparable to a mid-tier cloud storage subscription, with the difference that you are paying for a transport tool rather than for storage you have to keep renting. Check blip.net/pricing before you budget — plans move.

How we use it at Gloworks

Concretely, so you can copy or ignore it:

The pattern that emerged on its own: Blip for anything going to someone we work with regularly, links for anyone else. We did not plan that split; it is just where things settled after a few months.

Should you switch?

If your handoffs are mostly small exports to clients you meet once, probably not — the install requirement outweighs the gains.

If you are moving whole shoots and whole project folders between the same handful of people, and especially if some of those moves happen inside one building, then yes. Install it on two machines and move a real shoot folder over your LAN once. That test takes ten minutes and it is the whole argument.

The reason Blip made this list rather than the dozen other tools we tried last year is not that it does something no one else can. It is that it removed a step we had stopped noticing we were paying for.