Does Photo Delivery End When the Files Arrive?

For a long time, I delivered photos with a shared Google Drive link. Some clients ask me to upload to a secure share environment of their own instead, such as SS&C Intralinks.

If the goal is to hand over the complete set of files, that is still enough. For B2B work where delivering the full set of shot data completes the job, I still send a Google Drive URL.

What changed is social media work and B2C delivery.

In those two cases, I noticed a distance between handing over files and the client actually being able to use the photos.

Social media photos have a window

For social media work, delivery speed carries meaning.

Right after an event or a shoot, the temperature of that moment is still there. Sometimes the client wants to post the same day. A few hours later, attention has often moved to something else.

So for social work, I do not only develop the photos. I also export them in the aspect ratios the platform actually uses, such as 4:5.

And after building the files to that point, the last thing I do is hand over a Google Drive folder.

The photos still arrive, of course. But what the client wants to do is not manage files. It is to look at the photos, decide "I'll use this one," and use that image right away.

If that is the case, the distance from "I'll use this one" to the download should be shorter.

That was one of the reasons I started building my own image viewer for delivery.

The photos you want to keep are not the photos you want to see

There was another thing I noticed while continuing to deliver work.

An influencer I had photographed before once asked me, "Do you still have the photos from back then?"

That was the first time I really registered that delivered photos are not necessarily kept and managed on the client's side.

Which makes sense, when I think about it. Nobody wants to store dozens or hundreds of delivered photos on their iPhone. Only a few of them will actually be used on social media.

But that does not mean I want to take on permanent asset management for a client's photos either. Doing that would become a separate line of work from shooting and delivery.

What I needed was something in between.

You can look at the photos for a set period. You can search for one when you need it. You can download only the photos you want to use. But it never becomes a permanent asset management service.

I decided to put my image viewer for delivery on that boundary.

Why the window is one month

As a rule, the viewer stays open for one month.

Freshness matters for social media photos, and long-term storage is not what this is for. Even for B2C work like family photos, the assumption is that the client saves them locally after delivery.

So I state the expiration date at delivery, and the client saves the photos they need within that window.

The deadline is a constraint, but it is also what defines what this delivery method is. It is not a vault. It is a place to look at photos, choose, and take them.

I did not stop using Google Drive

Building the image viewer for delivery did not mean letting go of Google Drive. The image data still lives there.

What changed is the surface the client touches. Google Drive stays as the storage, and in front of it I placed a thin interface for looking at photos.

Open the URL and the photos are laid out. Click and you see one large. Download it on the spot if you need it. You can put a star on the ones you care about, copy the file names you selected, or export them as CSV.

What I needed was not a high-functionality photo management service. It was to shorten the distance across "look, choose, take."

Frame.io is a little heavy for this

Using an existing service is an option.

But for my own use, a production and review environment like Frame.io is a little heavy. If you are running review and approval on a video production, those features mean something.

For delivering social photos to an influencer, or handing family photos to a B2C client, that much structure was not necessary. It is also not a feature set I want to pay an extra subscription for, and ask my clients to learn new controls for.

Open a URL. Look at the photos. Download the ones you want. That was about all I needed.

The delivery method depends on what happens after delivery

These days I choose the delivery method by the job.

If it is B2B and handing over the full set of shot data completes it, Google Drive. If it is an urgent social media job, or B2C work where looking at the photos themselves is what matters, the image viewer for delivery.

Neither one is better. What differs is what the other person does after delivery. Receive the set and manage it internally? Or look at the photos right there and decide which ones to use?

For the latter, I came to think the endpoint of delivery should not sit at "the files arrived."

The photos were uploaded.

The URL was sent.

The files arrived.

Technically, delivery is complete at that point. But for work like social media, there is still

"look"

"decide"

"download"

"use"

after it.

What I wanted to shorten was not only the file transfer time.

It was the time it takes for a photo I shot to become something the other person can actually use.