Two Photographers, One Client Gallery

This is the thirty seconds of work that saves the most time later, and it is the step most often skipped.

Set both bodies to the same time zone and the same minute before anyone starts shooting. Do it in the car, not at the venue. If your second shooter is bringing two bodies, set all of them, because the backup body is the one that comes out during the ceremony and it is the one nobody checked.

Then make a fallback. Photograph the same phone screen, showing the seconds, with every camera that will be used. If a clock turns out to be wrong anyway, that frame gives you the exact offset, and one shift of capture time in your catalog corrects the whole card.

Clock drift is silent. Nothing warns you. You notice it when you sort the merged take by capture time and the speeches land before the cake cutting, at which point you are repairing an edit you have already finished.

Rename at ingest, before anything else touches the files. Two cards from the same camera brand arrive with the same sequence numbers, and a gallery that holds two photographs called 0148 is a gallery that will eventually cost you an hour.

A pattern that survives the whole job looks like this.

2026-09-11-tremblay-CG-0001

• Date first. It sorts correctly everywhere, in every operating system, forever.
• Client or job name second. So a file that escapes into an email still says what it belongs to.
• Shooter initials third. This is the part that exists only because there are two of you. Keep it after the merge as well, not just during the sort.
• Sequence last. Unique within that shooter's card, which is all it needs to be once the initials are in front of it.

Unique filenames matter more than they used to, because picks now come back as data rather than as a list typed into an email. The two-way Lightroom Classic plugin publishes proofs from your catalog and pulls the client's selections back into it, described step by step in the guide on getting picks back into Lightroom. Two files with the same name in one delivery is the one thing that makes a returned selection ambiguous, and it is entirely avoidable at ingest.

Write the naming rule into the agreement with your second shooter, alongside the delivery format and the deadline. It takes one line, and it means you are never renaming someone else's card at midnight.

Be clear about this one, because a lot of gallery marketing is vague about it and the honest version is simpler.

An account here is one studio and one login. There are no seats, no team members and no per-seat pricing. The lead photographer owns the account, and the second shooter delivers files to the lead rather than uploading into the gallery directly. That is the workflow, and for a normal second-shooter arrangement it is also the right one: the person who is accountable for the edit is the person who controls what the client sees.

One consequence worth saying out loud. The studio key that the Lightroom plugin authenticates with belongs to the account, so it is not something to hand around. If a machine you no longer control has it, regenerate the key from the studio and the old one stops working.

Agree the handoff format in advance. Culled and edited to your look, or raw files for you to edit, are two different jobs and two different fees. Whichever you choose, ask for the whole card rather than a selection if you are paying for coverage, and keep the original capture times intact, because the merge depends on them.

Two takes of the same event are not additive. Half of a second shooter's frames cover a moment the lead also covered, from a different seat. Delivering both versions of every moment is how a 600-photo gallery becomes a 1,400-photo gallery that nobody finishes looking at.

Do it in two passes.

• Pass one, each card alone. Cut the technical failures and the near-identical frames inside each take, the way you would on any job. Nothing about the other card matters yet.
• Pass two, both cards together, sorted by capture time. Now the duplicates are adjacent, because two photographs of the same moment carry almost the same timestamp. Work down the timeline and choose.

The choosing rule that holds up: keep the angle that shows the thing happening, and keep the second angle only when it shows a different thing. During a speech, the lead usually has the speaker and the second shooter has the couple laughing. Those are two photographs. During a first dance shot from both ends of the floor, those are one photograph, and you pick the better one.

Then match the edit. Two white balances in one scroll is the single clearest signal to a client that two different people shot their day. Colour both takes to one look before you publish, even when it means pulling the second shooter's files further than you would pull your own.

Once the cull is done there are two sane orders, and one order that quietly makes the client do your filing.

By capture time. The default, and the reason the clock sync matters. Both cards interleave into one chronological scroll and the gallery reads like the day happened. The client never learns that two cameras were involved, which is the goal.

By part of the job. Sub-galleries are folders inside a gallery, so a long day can be split into named sections while still living behind one link. Name the folders after the parts of the event, and keep them chronological inside. There is more on folder structure in the guide on folders for multi-day events.

Not by photographer. Do not ship a folder called Second Shooter. It asks the client to understand your staffing, it invites them to compare the two takes, and it guarantees that the parents open one folder, see half the ceremony and write to say photos are missing. The shooter code stays in the filename, where it is useful to you and invisible to them.

A two-photographer job is the one most likely to meet a platform limit, so here are the figures in plain form rather than behind the word unlimited.

The line to plan around is the 1,000 photos per gallery, and two photographers is precisely the job that reaches it. The count is taken per gallery. A photo filed into a sub-gallery still belongs to the gallery holding it, so splitting the day into six folders does not buy a single extra slot.

When a two-shooter job genuinely exceeds 1,000 delivered frames, publish a second gallery and split on a line the client already understands, usually the day or the event. There is no per-gallery fee, so the second gallery costs nothing. Decide that before upload night rather than during it.

The storage side is not where you will run out. Seven hundred delivered proofs at roughly 0.6 MB is about 420 MB, so the 250 GB account allowance holds hundreds of jobs that size, and they stay live for as long as the account does. Worth repeating because it is what keeps the price flat: the gallery hosts JPEGs. It does not warehouse RAW files or master video, and your originals stay in your own backup.

Everything above exists so that this part is boring. Both takes are now one set, in one order, in one colour, with unique filenames.

The client gets one link. It sits on your own subdomain with no platform branding on any client-facing page, so the gallery carries your studio name and nobody else's. Hosted galleries do not expire, which matters on a job with two photographers because the credit conversation tends to happen months later, when someone posts the work.

The full-resolution files are a separate handoff. You upload one ZIP for the gallery, containing both takes already merged and named, and it stays live for three days per handoff. You can re-upload it whenever the client asks, and an account holds up to 100 GB of standing ZIPs. Say the three days in the delivery email rather than leaving the client to discover it.

Picks come back into your catalog through the plugin, into one selection list covering both cards. That list is the reason the naming rule was worth following: every line in it points at exactly one file. The mechanics of the publish and pull are on the Lightroom plugin page.

Credit your second shooter in your own words, in the delivery email, in your caption or in the contract. Not in the folder structure, and not in a watermark the client did not ask for.

The honest boundary. The workflow above fits a lead photographer who hires help and is accountable for the delivery. It does not fit two independent photographers who each need to deliver their own work to their own clients.

If that is your situation, do not share one login between two businesses. Every gallery on an account belongs to that account, and there is no per-seat structure that would separate your work from your partner's inside it. At $10 a month, or $100 a year, two accounts is the answer, and it keeps the client lists, the branding and the billing where they belong.

A collective that genuinely operates as one studio, with one brand and one person responsible for delivery, can run on one account. Just understand what you are agreeing to. One credential, one set of galleries, and whoever holds the login can change or delete any of them.

Every figure on this page is a fact about this product, verified in the product code on 11 September 2026 rather than taken from any outside publication. No competitor number is quoted here, so there is nothing else to cite.

• clientgallery.io plan and fair-use figures, verified 11 September 2026: $10 a month or $100 a year, one login per account with no seats or per-seat pricing, unlimited galleries, photos and clients under fair use, 1,000 photos per gallery counted per gallery including photos filed into sub-galleries, proof JPEGs of about 0.6 MB, 250 GB of proofs per paid account, 5 GB on a free account, full-resolution ZIP live 3 days per handoff with 100 GB of standing ZIPs per account, https://clientgallery.io
• clientgallery.io Lightroom Classic plugin, publish proofs from the catalog and pull client picks back into it, verified 11 September 2026, https://clientgallery.io/lightroom