How We Approach a Real Wedding Gallery

Every wedding we shoot produces a full gallery, usually several hundred edited images covering the whole day, getting ready, ceremony, portraits, reception, right up to the last song. Only some of those weddings end up on our Real Weddings page, and when one does, what's shown there is a small, deliberately chosen slice of that gallery, not the whole thing. We get asked about this often enough that it's worth explaining properly, rather than leaving a page of pretty photos to speak for itself.

• Full gallery: 400+ images

• Feature length: 25-40 images

• Consent: Asked before publishing

• Takedown: Anytime, on request

At a glance

• A full gallery runs to several hundred images. A published feature usually sits closer to 25-40.

• We choose features for variety of moment and genuine pacing, not just the prettiest individual shots.

• Anything that touches a guest's privacy, a family's specific wishes, or a genuinely personal moment gets left out by default.

• Couples are asked before their gallery becomes a feature, not after.

• The text around each feature exists so the gallery means something to a reader, not just to a search engine.

What a real wedding feature actually is

A real wedding feature is different from the gallery a couple receives. The couple's gallery is built to document their day as completely and usefully as we can, so they have the ceremony, the family groups, the quiet in-between moments, and the reception in full. A feature is built for a different reader entirely: someone who has never met this couple and is trying to work out what a wedding with us actually looks like, at a specific venue, in a specific season, done a specific way.

That difference in audience is why a feature can't just be a shortened version of the gallery. It has to work as its own small story: enough to show how the day moved, without needing the couple's own memory of it to make sense.

What makes a gallery worth featuring

Not every wedding we shoot becomes a feature, and that's not a judgement on the wedding itself. Most of what we skip is skipped for practical reasons: a couple who'd rather not be shown publicly, a day that overlaps too closely with a feature we've already published, or simply timing.

Among the galleries we do put forward, a handful of things tend to separate the ones that make good features from the ones that don't.

Variety of moment. A gallery with real range, quiet detail shots, unscripted reactions, a proper look at the reception room once it's full, gives a reader far more to go on than a gallery that's mostly posed portraits in nice light. We're looking for a day that shows its own shape.

Pacing that reads clearly in a small set. Some weddings have a rhythm that survives being cut down to 30 photos. Others only make sense at full length, with dozens of small connecting moments between the big ones. The second kind isn't a worse wedding, it's just a harder feature to build well, and we'd rather skip it than force it.

Light and location doing real work. A garden ceremony at 4pm in late autumn reads completely differently to one at midday in January, and a feature earns its place by showing that difference honestly rather than defaulting to the same golden-hour portrait every time.

Something a reader can actually use. If a feature can show a real answer to a question a couple would otherwise have to ask us directly, how a marquee looks once it's dressed, how a small guest list fills a room, what a wet-weather backup actually looked like on the day, it's doing more work than a gallery of beautiful but interchangeable photos.

We're looking for a day that shows its own shape.

How many photos actually make the cut

The full gallery we hand over to a couple is built to be thorough. A published feature is built to be legible at a glance, and those two goals need very different numbers of photos.

In practice, a feature usually lands somewhere between 25 and 40 images, drawn from a gallery that might run to 400 or more. That's a big cut, and it's deliberate. A feature with 150 photos stops being something a reader actually looks at properly; it becomes a scroll they abandon halfway through. A tighter set forces every image to earn its place, and it's genuinely more useful to someone deciding whether our style suits their own wedding.

We build that smaller set the same way we'd build a photo essay: a few wide shots to set the scene, a run of detail and candid moments to carry the middle, and enough of the reception to show how the room actually felt once the formalities were done. It's closer to editing a short film than picking favourites from a contact sheet.

It's closer to editing a short film than picking favourites from a contact sheet.

What we leave out, and why

This is the part that matters most, and it's not really about photography at all.

A wedding gallery is full of people who didn't necessarily sign up to be shown publicly. The couple booked us and knows their day may be featured, but their guests didn't make that choice, and neither did any family members who might prefer to keep certain moments private, a particular cultural or religious element of the ceremony, an emotional reaction during a speech, a candid shot of a guest who'd rather not be online.

Our default is to leave those things out unless there's a clear reason and a clear yes to include them. Practically, that means:

How we handle it in practice

• We ask the couple before a gallery becomes a feature, not after it's already published. If they'd rather not be shown, or want specific moments held back, that's respected without argument.

• Anything that reads as a private family moment rather than a shareable one, certain speeches, certain reactions, stays out by default even if it's a genuinely strong photograph.

• Guests who are clearly visible and identifiable get more caution than the couple themselves, since they didn't choose to be part of a public feature the way the couple did.

• If a couple asks us to take a feature down after it's live, we do that too. It's their wedding, not our content library.

None of this is a legal policy document, and it isn't meant to read like one. It's just how we handle it in practice, and it's worth saying plainly rather than leaving couples to wonder.

It's their wedding, not our content library.

Why we write text around the photos at all

A gallery on its own tells a reader almost nothing useful. It shows what a day looked like, but not why particular choices were made, what the light was doing at that hour, why a couple chose that venue for that time of year, what a guest list that size actually feels like in a marquee. The text is where that context lives.

It also means a Real Weddings page isn't just a wall of images with nothing for a search engine, or a person skimming on their phone, to actually read. If you're at the stage of comparing photographers, our guide to how to choose a wedding photographer in Auckland covers what to look for in a portfolio, including in a page like this one. And if you're curious how a day's photography actually unfolds hour by hour, our wedding photography timeline guide walks through that separately.

The photos are still the point. The text just makes sure they mean something to someone who wasn't there.