Client galleries built for the way weddings are shared

Your couple opens the link at the reception, and so do forty people they send it to.

Start freeSee a live story

A client gallery has one job that everybody agrees on, which is getting the files to the couple, and one job that almost nobody designs for, which is being seen by the people who will hire you next.

Most galleries are built for the first job. They are a grid, a download button and a print store. That works, and if it is all you need then any of the established tools will do it competently.

What we do differently

The gallery is the last thing your clients ever receive from you, and for most wedding photographers it is also the piece of work the largest number of strangers will ever see. The bride's cousin, the friend who could not fly in, the colleague who asks who shot it. Every one of them opens the same link.

So we built the delivery to survive being forwarded:

It loads on a phone at a venue. Photos are decoded once at upload and emitted as a ladder of widths in AVIF and WebP, and the page fetches only the size it is actually showing. This is the single thing we have spent the most engineering time on, because a gallery that takes eight seconds to paint is a gallery nobody sends on.

It carries your name, not ours. Your colours, your fonts, your studio name, through the brand kit. On paid plans there is no badge of ours anywhere.

It can be a story rather than a wall. The same upload can be laid out as a scroll through the day in the order it happened, with your video clips in the same scroll as the stills. Some couples get a grid, some get the story. That is your call, per wedding.

The practical parts

Selection lists. Ask the couple to pick their album photos with a real deadline, see what they have chosen without emailing them, and send a reminder in one click when the date passes.

Downloads that work. Full-resolution originals, per photo or as a zip for the whole gallery, prepared server side so a large wedding does not depend on the couple's laptop staying awake.

A desktop uploader for the big drops. A whole wedding at once, uploading in parallel, resuming where it left off if the wifi drops or the laptop sleeps. Free, and the browser handles anything smaller.

Storage that does not punish a busy August. Plans are priced by storage rather than by photo count, so a heavy wedding costs you the same as a light one. If you do hit a limit, new uploads pause and nothing already published goes offline.

Try it with a real wedding

The free plan holds about 2,500 photos, which is a whole wedding rather than a sample of one. Upload one you have already delivered, send the link to somebody who was not there, and see whether they reply about it.

Common questions

How many photos can I put in one gallery?
There is no cap on the number of photos in a gallery. Plans are limited by storage, not by photo count, so a wedding of 900 finals is the same to us as one of 300. The free plan holds about 2,500 photos, which is roughly a whole wedding.
Do my clients need an account or an app?
No. A gallery is a link. Your couple opens it in whatever browser they already have, on whatever phone they already own, and so does everyone they forward it to. You can put a password on it if you want to.
Can I use my own branding and domain?
Yes. Galleries carry your studio name, your colours and your fonts through the brand kit, and paid plans remove any Revivre badge. What your clients see and share is yours.
How fast does a gallery load on a phone?
Every photo is re-encoded once at upload into AVIF and WebP at several widths, and the page only ever downloads the width it is showing. A phone at a reception fetches a few hundred kilobytes per photo rather than a full-resolution JPEG.
Can clients download the original files?
Yes. Downloads serve the full-resolution original you uploaded, either for the whole gallery or for individual photos, and you decide whether downloads are on.

Weighing it against something else

More on this

The rest of the product