QR Codes for Photographers, From Album Cards to Client Galleries — featured illustration
Business

QR Codes for Photographers, From Album Cards to Client Galleries

6 min read
Create a QR code

A client opens an album box eighteen months after her wedding, finds a small card tucked under the lid, and scans it to show her mother the full gallery. Whether that works has almost nothing to do with the card and everything to do with a decision made when the code was generated.

The card in the album box

Gallery delivery links are long, hyphenated and impossible to read aloud, which is exactly the problem a code solves. A letterpress card with a code and four words of instruction is the cheapest useful thing a photographer can put in a delivery box, and it turns a link nobody would type into something a client can hand across a kitchen table.

Keep the card simple: a code, a line saying what it opens, the studio name. If the gallery has a PIN, print the PIN. A client who has to email you for a password will show the album to fewer people, which is the opposite of why you made the card in the first place.

Galleries expire, printed cards do not

This is the operational fact the whole practice turns on. Gallery hosts archive delivery sets on a schedule, usually somewhere between a few months and a year after delivery, and reactivating one is a support request at best. Photographers also change hosts, rebrand, drop a domain, or move a portfolio between platforms every few years. The card in the box does none of those things. It sits in a box for decades.

So the code on that card has to be one whose destination you can change later. A code carrying the gallery address directly is welded to that address permanently; when the gallery archives, the card becomes a dead end with your logo on it. A code carrying a redirect you control can be repointed in a minute, and changing a printed code's destination walks through both cases, including what to do if you have already printed the wrong kind.

Repointing is not only for emergencies. Decide now what an expired gallery card should land on. A page that says the gallery has been archived, shows three images from the session, and offers a reorder link is a far better answer than a host's generic not-found screen, and it occasionally sells a print. Put a note in the calendar for the month galleries archive and work through your codes the way you would run an audit for dead codes.

A code on the back of a print

Framed work sells better with a story attached, and the back of a mount is unused space. A small code there can open the location, the conditions on the day, the reason the frame exists, or a short audio note recorded on the shoot.

Two constraints. The code will be small, because the space is small, and a small code needs a short destination and a clean margin; the size guide has the distance arithmetic. And the paper matters more than people expect. An uncoated art stock spreads ink, thickening every module and closing the gaps a decoder is looking for, so print a test at final size on the actual stock rather than on the office laser. A code that reads on copier paper can fail on cotton rag at identical dimensions.

For gallery shows, point prints at a public page rather than a client's set. A wall label is not the place to expose a private gallery.

The wedding code that collects guest photos

Here the direction reverses. Instead of handing guests something to look at, you are asking them to upload, and the failure modes are all about friction.

The target has to accept an upload from a stranger with no account, no download and no sign-in wall. Test it on a phone that has never visited it, on cellular rather than the venue WiFi, with roughly the patience of a guest holding a drink. Put the code in more than one place: table cards, the bar, the back of the order of service. Say what it does in plain words, because "scan here" gets scanned far less often than "send us your photos from tonight".

Then decide in advance what happens to the uploads, because a shared folder filling with two hundred files of unknown orientation is not a deliverable and the couple will ask. Our wedding code page covers the guest-facing side; the editing agreement is yours to have before the day.

A gallery link is a key, not a name

Most gallery hosts protect a set with nothing but an unguessable address. That is a reasonable design, and it has one consequence worth stating plainly: anyone holding the link, or the code, has the gallery. There is no second factor, no account check, no record of who came in.

The code therefore inherits the sensitivity of the images behind it. A family session, fine. A boudoir or maternity set, not on anything that leaves the client's hands and not on a card that might sit on a hall table. For those, a PIN on the gallery is not paranoia; it is the difference between a link and a credential. Tell the client the code is a key, once, in the delivery email. They handle it better than you expect when somebody says it out loud.

When the couple posts the code publicly

It happens constantly. A couple photographs the album card, puts it on a social feed out of sheer delight, and a private gallery is now a public one. Nothing was hacked. They simply did not know the square was the password.

Two habits limit the damage before it happens. Separate a public set from a private one at delivery: a short highlight page you are happy to see shared, and a full gallery that is not on the shareable card. And keep the ability to repoint, because if a private set does go public, the only fast remedy is sending the code somewhere else and reissuing the link to the client.

Be careful what you conclude from the numbers afterward. A code's scan log shows counts over time plus a breakdown by country and device, which tells you a card is being used and roughly from where. It does not tell you who scanned, so a spike after a social post and a spike from a family gathering look identical in the data.

The studio window

The last one is also the easiest. A code on the inside of a studio window, pointing at a booking page, catches the person who walked past at nine on a Sunday when you were closed.

Two details decide whether it works. Print it for the distance someone stands at on the pavement, which is further back than the layout suggests. And mount it so it is read through the glass rather than reflected off it, since codes behind glass have a set of problems all their own that codes on glass and windows covers, including the reversed-artwork trap that catches decals.

If you do one thing after reading this, list every printed code your studio has in circulation and write down where each one points today. The photographers who get caught by an archived gallery are the ones who never made that list. Every code from QRolling's photo code pages is dynamic, so the destination stays editable on the paid plan.

Share this article