A Client Photo Portal for Repeat Commercial Clients

Picture a normal commercial account. In February you shoot a product range for a marketing coordinator. In May you shoot the team. In September you shoot the new store. In January the same company calls again, but the coordinator has moved on, and the person now holding the brief has none of your emails.

What happens next is familiar. Somebody searches a shared inbox for your studio name. They find a transfer link that died months ago. They find a folder on a drive that has three copies of the same image with names like final_v2_USE_THIS. Then they email you and ask for everything again, and you spend an afternoon reconstructing a delivery you already made and were already paid for.

Nothing about that is a storage problem. The files exist. The problem is that the route to them was attached to one person and one email thread, and both are gone. Fixing it means the route has to outlive the person.

Make one gallery for the company, not one per shoot. The gallery lives at your own address, for example yourstudio.clientgallery.io/acme, and it is provisioned automatically with your studio subdomain. Inside it, each shoot is a section.

When you shoot again, you do not send a new link. You add a section to the gallery that already exists. Sections are created in the studio, or automatically by dragging a folder in, which makes one section per folder. The structure is exactly one level deep: a gallery holds sections, and a section does not hold further sections. That constraint is worth accepting, because a flat list of shoots is what a stranger can actually scan.

The payoff is that the link in the February email is the same link as the link in the September email. Someone who finds either one lands on a page that shows every shoot since. The link did not have to be maintained. It just never changed.

For how to name those sections so they stay legible after a dozen jobs, see organising multiple shoots for one client. For making the page read as your studio rather than as a tool, see the branded client portal guide.

A durable link is only durable if the thing it points at does not expire. Here the distinction matters and it is worth being exact about, because the two halves of a delivery behave differently.

So: the gallery is permanent, the full-resolution handoff is a window. Do not tell a commercial client that everything is available forever, because the second half of that sentence is not true and they will find out at the worst moment.

You can also revoke a gallery, which kills the page, the ZIP and the full-resolution link together. Useful if a relationship ends badly or a campaign has to come down.

The reason a permanent gallery beats a permanent folder is that the client can serve themselves. From the gallery, they download the whole thing in one click, or any single image on its own. No request, no wait, no afternoon of your time.

That is the part that changes the economics of a repeat account. A client who needs one product shot for a slide deck at 6pm gets it at 6pm. You are not the bottleneck, and you are not doing unpaid retrieval work between paid jobs.

One detail to plan around: a section link is view-only. Opened on its own, a section has no whole-gallery download, no full-resolution handoff, no picks, no comments and no face search. So send the parent gallery link, not a section link, whenever the client is meant to download. Use section links only to point somebody at one specific shoot to look at.

If the account is sensitive, turn on the per-gallery password. It is off by default, and on the server it gates the gallery page, the whole-gallery download, the full-resolution ZIP, comments and face search. A section link resolves to its parent, so one password covers every shoot. Be aware of the limit: individual proof image URLs are public and do not expire, so the password stops the gallery page from disclosing those URLs, but it does not protect an image URL that somebody already holds.

This is the paragraph a marketing manager will test within a year, so state it in your own words before they discover it.

Full-resolution delivery works by you uploading a full-resolution ZIP for the gallery. It stays live for 3 days per handoff, and you can re-upload it at any time. Across the whole account, 100 GB of those ZIPs can stand at once. The proofs in the gallery are permanent; the masters behind them are a handoff you open on request.

Practically, that means a client asking in November for the print files from last March's shoot needs you to re-upload before they can pull them. That is a message and an upload, not a rebuild, because the gallery, the sections and the proofs are all still there. But it is not self-service, and pretending otherwise is how you end up with an angry email.

The working arrangement that holds up over years looks like this. You keep the masters, in your own backup, as you already do. The gallery is the permanent reference layer the client browses and pulls web-usable images from. Full resolution is opened on request with a stated turnaround, for example same business day. Write that turnaround into the delivery email once, and the expectation is set for every shoot after it. clientgallery.io hosts JPEGs; it does not warehouse RAW files or master video, which is what keeps the price flat.

The client sees a gallery. You need something more than that: a place to remember who briefed what, which licence was discussed, what the invoice covered, and what they said they wanted next quarter.

The studio dashboard has a client record with free-text notes, and galleries attach to it. That record is yours. It is not visible to the client, there is nothing for them to log into, and nothing shows them a list of everything you hold. Treat the notes field as your account history: dates, contact names as they change, agreed usage, what has been re-uploaded and when.

This division is deliberate. The client-facing surface is one link and a list of shoots, which is all a stranger can be expected to understand. The complexity lives on your side, where it belongs.

An account you shoot four times a year for five years is twenty deliveries. The ceilings you are working inside are simple.

The 1,000-photo ceiling is the one that shapes the structure, and the answer is not to fight it. Split by year. Acme 2025, Acme 2026, Acme 2027, each with a section per shoot, and the current year linked from your delivery emails. A gallery that grows forever eventually becomes a page nobody wants to scroll, which defeats the purpose, and it hits the ceiling in the middle of a job rather than at a moment you chose.

Splitting by year also gives the client a natural way to talk about the archive. "It is in the 2025 gallery, autumn campaign section" is an instruction a new hire can follow.

Be straight about this one, because promising otherwise costs you the account later. A gallery is a delivery and reference surface. It is not an asset management system.

If the client genuinely needs rights metadata on each file, usage terms recorded per image, licence expiry dates that trigger a warning, controlled vocabularies and keyword taxonomies, or multiple named users with different permissions and an audit trail of who downloaded what, they need a digital asset manager. That is a real category of software with real budgets attached, and it is the correct purchase for a company at that size. Tell them so. Then keep delivering into the gallery and let their team ingest from it, which is a perfectly normal arrangement.

The signals are easy to read. A single marketing contact who wants to find last year's photos needs a permanent link. A legal or brand team asking who is allowed to use which image until when needs a DAM. Do not sell the first as the second.

The structure only pays off if the link ends up somewhere institutional rather than in one person's inbox. A few habits do most of the work.

• Send it to a shared address as well as a person. Copy the marketing or brand inbox on every delivery, not only the individual who briefed the job.
• Ask once for it to be filed. A single line asking them to paste the link into their brand guidelines document or team wiki takes ten seconds and outlives everyone on the thread.
• Keep the subject line stable. Use the same convention every time, with the company name in it, so a search of the inbox surfaces the whole history.
• Repeat the same link in every delivery email. Any one of twenty emails then leads to the current gallery.
• Say what full resolution requires. One sentence about the 3-day handoff window and how to ask for a re-upload, in every delivery email.

None of this is administration you have to maintain. There is no client account to provision, no seat to revoke when somebody leaves, and no password reset request landing on you two years later. That is the quiet advantage of a link-based portal over a login-based one for accounts where the people change faster than the relationship does.