
A same-day sneak peek looks effortless to a couple because almost all of the work happened weeks before their wedding. Trying to find, edit and export fifteen images for the first time during dinner is how you miss the speeches. Treat the preview as its own small deliverable, with its own promise, its own shooting habits and its own half hour.
Same day means at least four different things, and couples assume the most generous one. A single image by cocktail hour. Ten to fifteen edited frames before the reception ends. A carousel that night. A gallery waiting when they wake up. Only one of those is what you are selling, so write that one down.
A usable promise has a number, a time and a condition attached. Something like: you will have ten to fifteen edited previews by 9pm, provided the timeline includes a thirty minute break after portraits and the venue has working internet. That is not fussiness, it is the sentence that lets you step away from the party without looking like you vanished, and it warns the couple in advance that a second shooter may cover the room for half an hour. The contract wording, including what happens when the condition is not met, is in the sneak peek clause worth adding.
Decide the number before you decide the workflow. Fifteen is common because it feels generous and still fits a short window, but the case for other counts, and why more is not better here, is in how many sneak peeks to send. If it costs you an hour of a day you are already being paid for, it is fair to charge, and charging for fast turnaround covers pricing it without it feeling like a penalty.
Last, agree where it lands. A private gallery link, a folder of web-sized JPEGs sent by text, and a set the couple can post that evening are three different deliverables. Ask which they want, ask whether vendors may share, and settle it at the planning call rather than at 8pm with a laptop on your knees.
The preview gets fast when the frames are already easy to find, and you do not need fifteen separate scenes before the reception. Details, getting ready, a first look, ceremony context, the kiss, a few portraits and one candid is a complete set. Speeches and dancing join the full gallery later.
Three habits do most of the work.
If you have a second shooter, agree before the day who supplies preview candidates and how the files reach you. A card handed over at the vendor meal with twelve marked frames on it is useful. A promise to send something later is not.
The edit window is a timeline decision, not a gap you hope will appear. Raise it at the walkthrough or the final planning call, and get it written into the schedule the planner is working from.
Good windows share one property: nothing in them happens only once. The gap after family portraits while the couple takes ten minutes alone. Dinner service, once the room is seated and eating. The vendor meal, which most photographers use because the venue hands it to you. A room flip. Cocktail hour, but only with a second shooter on it.
Bad windows are anything you cannot reshoot: speeches, the first dance, the cake, entrances, the last twenty minutes of golden light. If your only free half hour lands on one of those, you do not have a window. You have a next-morning delivery, which is a perfectly good outcome and has its own workflow.
Ask the venue for somewhere with a door and a power socket. A vacated bridal suite, a back office, the room where the vendor meal is served. Two places to avoid: the corner of the reception room, because a guest will lean over your shoulder and see the unflattering frames you have not chosen yet, and your car, because you cannot hear the room and will not know the speeches started early.
Carry the boring things. A fast card reader, a charged laptop, a short power strip you can reach without unpacking, and an internet plan you have tested inside a building like this one. Phone hotspots are fine as a backup and unreliable as a plan in a stone-walled venue full of guests on one cell tower.
Back up first. Copy every card so far to your working drive and to a second destination, leave the cards full, format nothing. That is not part of the preview, that is the job, and it is the one step you never trade for speed.
Then ingest narrowly. Bring in the frames you marked plus a small buffer either side, so you can still choose between two neighboring exposures. Twenty five marked frames is maybe one hundred to two hundred files. A typical wedding runs 2,000 to 4,000 frames, and importing all of them at 8pm turns a twenty minute selection into an hour of watching previews build.
Two routes work. Import the mini set into a dedicated collection and build standard previews, which keeps everything in one program. Or browse the embedded camera JPEGs in a fast viewer and hand only the finals over for editing, which starts faster but means two applications on a laptop balanced on a chair. Either is fine. Deciding which one at the venue is not.
One rule governs all of it: nothing you do tonight may make tomorrow's real ingest harder. Leave the card structure alone, keep the preview files in their own folder, and let the full job import cleanly next week as though this never happened. If you shoot raw and JPEG, the JPEGs are a legitimate shortcut here, and the raw plus JPEG rush workflow covers when that holds up.
Set two timers before you open anything. Five to eight minutes to flag twenty to thirty candidates, five to eight to cut those to fifteen, then you export what you have. A preview is a timely gesture, not a portfolio submission, and the difference between your fourteenth and fifteenth best frame is invisible to everyone except you.
A set feels generous because it has range, not volume. Here is a shape that works for a wedding, worth adapting rather than following exactly.
| Slot | How many | What it is doing |
|---|---|---|
| Venue or detail | 1 | Sets the scene, gives the post a place |
| Getting ready | 2 | People and anticipation, not just objects |
| First look or pre-ceremony | 1 | The first real reaction of the day |
| Ceremony context | 2 | The room, the aisle, the faces watching |
| Ritual and kiss | 2 | The moment the day is about |
| Couple portraits | 4 to 5 | Different light, distance and orientation |
| Quiet or playful in-between | 1 | The one that shows you were paying attention |
| Early reception | 1 | Only if the timing gives it to you |
No first look? Use a family reaction. Plain ceremony room? Lean into portraits and faces. The only rule that really matters is that the set must not be fifteen versions of two people standing in the same spot in the same light.
Inside each burst, take one frame. Our guide to choosing the best frame from a burst goes deeper, but tonight the fast version is enough: expression, then story, then sharpness among the best two or three. Do look for closed eyes, a hand cropped at the wrist and a white balance that jumps. Do not compare pixels on a set that will be viewed on phones.
The preview is the first thing the couple sees of the gallery, which makes it a promise about the gallery. Use the same camera profile, baseline contrast, approach to skin and crop discipline you will use on the other several hundred images. Then adjust only what each file genuinely needs: exposure, white balance, crop, and one local correction when it changes the picture.
Resist the new look. Wedding adrenaline at 8pm is an excellent way to invent a style you cannot reproduce across a full gallery, and the couple notices when the fifteen photos they posted do not match the seven hundred that arrive later. Skip retouching and elaborate masking entirely: they eat the clock and they make a small set look inconsistent.
Before export, look at the fifteen together rather than one at a time. Do the blacks and skin tones sit in the same neighborhood? Are the portraits warm while the ceremony frames drift green? Are there six verticals in a row? Ten minutes making the set coherent beats one perfect file surrounded by mismatched ones.
Export from a preset you built weeks ago: long edge around 2,400 to 3,000 pixels, sRGB, and a filename the couple will recognize later. Build it once and never think about it at a wedding again.
Open the exported JPEGs before you send them. Count them, check orientation, check no crop went strange, check the names. Thirty seconds here prevents the message you never want to send, which is the second one correcting the first.
Keep the note short. Something like: your first fifteen previews are ready. These are a small taste while I finish photographing the celebration, and the complete gallery will be with you by the date in your contract. Add sharing or credit instructions if you use them.
Then stop. If the couple replies with six exclamation marks, that is the system working, and you can answer after the next block of coverage. A live feedback loop during a reception is how you end up looking at a phone during a speech.
Vendors are worth ten minutes of separate thought. A small folder sent straight to the planner, the venue and the florist, showing their work with your credit terms attached, does more than tagging everybody in one large gallery. Why that is the higher value channel is the argument in why fast galleries win referrals.
Venue internet fails. Timelines collapse. Decide the order you give things up in now, because at 9pm you will take whichever escape route presents itself first.
The slow part of a same-day preview is not editing fifteen files, it is finding them. Kepla clears the obvious misses and hands you the clean frames to choose from, and it never deletes, moves or renames anything, so every frame it did not pick is still there when you want a different one at midnight. We are building it phone first, so the first pass can happen on an iPhone or iPad in a quiet room rather than on a laptop, and the same shoot opens on the Mac later with nothing redone. Being straight about status: the picking app for iPhone, iPad and Mac is still being built. What is live today is our free booking page, which holds dates and takes deposits while we build the rest.
Ten to fifteen is a practical range for a solo photographer. It is enough to feel like a real preview, varied enough to tell a small story, and still possible inside a half hour window at a venue. Adjust it for your package and for whether a second shooter is covering the room while you work. Sending fewer on time beats sending more late.
In a window where nothing happens that you cannot reshoot. The gap after family portraits, dinner service once the room is seated, the vendor meal, or a room flip. Never during speeches, entrances, the first dance or the cake. Agree the window with the planner in advance so it appears on the schedule everybody is working from rather than being a gap you hope for.
No. Use the same profile, contrast and skin treatment you plan to use on the whole gallery, then make normal per-image adjustments. A preview edited in a different style creates two problems: you have to recreate that style across hundreds of images later, and the couple notices when the photos they posted do not match the ones that arrive weeks afterward.
Increasingly yes. A modern phone or tablet with a card reader will browse and rate raw files, and for a fifteen image preview that is often enough, particularly if you shot raw and JPEG and can work from the JPEGs. Kepla is being built phone first for exactly this kind of pass, though the picking app is still in development. The booking page is what is live today.
Test it at the walkthrough rather than discovering it on the day, and carry a hotspot as a backup while assuming a stone building full of guests may defeat it. If upload is impossible, move the finished JPEGs to your phone by cable or camera wifi and send a small set by text when you have signal. Failing that, tell the couple that night that the previews arrive in the morning.
Kepla for Mac clears the obvious misses from a card, names the reason on every frame it sets aside, and leaves the choosing to you. Nothing is ever deleted, moved or renamed. Free through the private preview · the first hundred photographers keep it at $99 a year.