The Complete Wedding Photography Post-Production Workflow
After the selection comes production: a consistent edit, an understandable proof, checked output and a delivery you can reproduce. Treat each handoff as a decision with a record.
Define the finished job before editing the first photograph
A post-production workflow should end in a checked delivery, not merely a completed edit. The files a client receives, the photographs used in an album and the records retained by the studio are different outputs. Decide how they connect before creating hundreds of derivatives.
Start a job sheet with the promised deliverables, intended destinations and decisions still needed. A wedding may require a full-resolution gallery, a small announcement selection, several wall-print candidates and an album. Record which person reviews each item and which decisions require a new proof. Use the actual agreed scope; a workflow article cannot determine what your own client was promised.
This guide begins where the import-to-final-selection workflow leaves off. It covers production after the job reaches the archive: editing continuity, proofs, revisions, delivery, print preparation and album handoff. The examples are hypothetical studio exercises, not claims about a particular wedding or measured Lightbox Pro performance.
Original educational workflow diagram. The branches describe separate production tasks, not an implemented Lightbox Pro delivery service.
Establish the archive checkpoint and file identities
Before developing the full job, confirm that every camera and card has been accounted for and that a separate, readable recovery copy exists. A catalog count cannot prove that every file copied correctly. The detailed copying and restore procedure belongs in a professional photo-library backup plan; use this checkpoint to verify that it has actually happened.
Separate original files, working edits and output. One practical arrangement is a stable job folder with Originals, Working, Output and Records branches. Keep camera/card identity when filenames repeat. Do not flatten two cameras’ IMG_0042 files into one folder and hope the operating system chooses the right version.
Give the job a concise identifier and preserve a mapping between camera filenames, any renamed working files and client-facing names. For example, a delivery named River_0127.jpg might map to source Camera-B/Card-03/IMG_6841.CR2. The mapping is what makes a later request for a different crop actionable. The displayed sequence number alone is not a source identity.
Use distinct output folders for approved versions, such as Gallery_v01 and Album_v03. Avoid overwriting a previously delivered file while leaving its old preview in a client gallery. If a correction replaces a delivered photograph, record which version it replaces.
Freeze the editing selection without freezing judgment
A final editing set should mean that these originals are scheduled for production. Keep unresolved frames in a separate review set, and retain useful alternates until the job is accepted. An unrated photograph is not automatically a deletion candidate, and an editing selection is not yet a client album choice.
Inspect the selection as a story before doing detailed retouching. Check people, ceremony coverage, transitions and repetition. Then compare the technical close calls using the sharpness inspection procedure. Establish which rendering supplies the detail; a reduced preview may be sufficient for expression but insufficient for deciding fine focus.
Reviewed Lightbox Pro 0.1.2 (60) supports local referenced catalogs, ratings, labels, sets, one-to-six-image Light Table and native Loupe. Committed photographs become browsable during import while offline-preview preparation continues. Those tools support a manual selection checkpoint; they do not establish automated wedding storytelling or a finished card-ingest and backup system.
For an outside editor, make the handoff explicit. Supply exact source identities, a short style reference, output requirements and a list of exceptions. Lightbox Pro’s Transfer Copy mode can prepare separate source copies while retaining the archive references. Open With can hand available files to a chosen application. Neither operation translates Lightbox editing recipes into another editor’s adjustments.
Edit for continuity, then inspect exceptions
Begin with representative photographs from each lighting situation rather than the easiest single portrait. A useful test set might include window-lit preparation, the ceremony aisle, a backlit portrait, a mixed-light reception table and the dance floor. Establish whether the selected RAW processor handles the exact cameras and difficult exposures before applying a treatment to the whole job.
Work in two scales. At the sequence scale, align brightness, color and contrast so adjacent photographs feel intentional. At the image scale, resolve the individual crop, distractions and local treatment. A consistent ceremony sequence is more useful than one striking image surrounded by visibly unrelated edits.
Synchronize settings only across photographs that share a suitable starting condition. A change that improves one backlit frame can damage the next frame taken after the subject moved into shade. Compare the first, middle and last photograph in each edited group, plus any outlier. Separate second-camera material where its rendering needs a different starting treatment.
Keep the scope of retouching clear. Dust removal, temporary distractions, clothing adjustments and changes to a person’s appearance are different decisions. Record an unusual request rather than guessing. If a composite or object removal changes an important moment, keep the earlier version and note the change in the production record.
Save the editable work as well as the rendered result. Depending on the editor, that may mean a catalog, sidecar, layered document or another project file. A finished JPEG preserves one appearance; it does not necessarily preserve the route back to a different crop or retouching decision.
Make color decisions in a controlled path
Use a maintained, profiled display and reasonably consistent viewing conditions for final color decisions. A laptop viewed beside a warm lamp and a phone at maximum outdoor brightness are different viewing situations. A client’s screenshot is useful feedback about their experience, but it is not a calibrated measurement of the delivered file.
Adobe distinguishes assigning from converting a color profile: assignment changes the interpretation of existing color numbers, while conversion changes numbers for another color space. Do not assign a convenient profile to make a warning disappear. Convert an output copy as required, preserve the working master and embed the intended profile when the chosen format and destination support it.
Keep the editor, rendered file and destination aligned. Test a representative output through the actual gallery or print route. If a file looks different, first compare the same version in a color-managed viewer, check its embedded profile and inspect whether the service resized or reprocessed it. Changing the master to compensate for an unidentified delivery problem can create a second problem.
Lightbox Pro’s current preview editing includes crop, Light brightness/contrast, Levels, Color Balance and Duotone. Its Original RGB histogram is a prepared-preview histogram, not live adjusted or sensor data. App-controlled sensor RAW development and finished protected rendered export remain unfinished in reviewed build 60. Use a validated RAW editor and output workflow for the production steps described here.
Build proofs that can be revised unambiguously
A proof is a review artifact with a defined purpose. If the client is choosing album photographs, show identifiable images and explain what a selection means. If they are approving retouching, make the relevant changes visible. Do not let a low-resolution selection proof accidentally become the file used for a large print.
Keep filenames or stable image IDs visible in the review route. Ask for comments against those IDs rather than descriptions such as “the one where we are near the tree.” Where privacy matters, choose an access-controlled service you have evaluated and test the recipient experience. The website’s demonstration gallery is not a substitute for an actual hosted delivery system.
Separate revision types. A request to exchange an expression, alter a crop, change skin treatment or choose another album photograph affects different files. Keep a small revision register and mark each item reviewed, in progress, reproofed or accepted. Review the revised set once as a whole; a changed image can alter the balance of the neighboring sequence.
For example, if River_0127 changes from color to monochrome in proof version two, retain the first proof’s identity in the register. Confirm whether the change applies only to the album or also to the main delivery. Without that distinction, two technically correct outputs can contradict the client’s intention.
Prepare outputs for their actual destinations
Use separate presets for separate purposes. A proof, a client download and an album spread should not be indistinguishable files in a single export folder. Record pixel dimensions, format, profile, crop, sharpening treatment and naming rules for each output, then check the results rather than trusting the preset name.
| Output | Primary decision | Check before release |
|---|---|---|
| Selection proof | Which photograph does the client want? | Correct identities, complete review set and clearly limited use. |
| Full-resolution delivery | Which finished files were promised? | Dimensions, crop, profile, visible treatment, filenames and download integrity. |
| Print candidate | Will this crop work at the chosen size? | Retained pixels, important edges, lab specifications and a suitable print proof. |
| Album spread | Is this layout ready for the selected product? | Template version, sequence, trim, gutter, text and approved spread version. |
Pixel dimensions, print size and ppi are related: a retained 3600-pixel width placed at 12 inches supplies 300 ppi. Changing a resolution label alone adds no detail. Adobe’s image-size explanation separates that change from resampling. Treat 300 ppi here as arithmetic, not a rule for every output; follow the selected provider’s current requirements.
Provider instructions differ. WHCC’s album documentation, for example, specifies high-quality JPEGs with an embedded RGB profile and supplies product templates. That is evidence for its particular album route, not permission to submit identical settings to every lab. Confirm the actual product, ordering method and correction policy before preparing the full set.
For books, Blurb explains that full-bleed artwork extends beyond trim and important content belongs inside the safe area. Use the selected product’s template; a layout that merely touches the on-screen page edge can fail in production.
Perform a delivery preflight on the rendered files
Inspect output files, not just the editor’s preview. Choose examples across every lighting group and inspect all images with substantial retouching or unusual crops. Review at the intended display size, then inspect detail where necessary. A clean master does not prove that a later resize or export preserved it correctly.
- Compare expected and actual output counts, including intentional omissions and duplicates.
- Check orientation, crop edges, names and the intended version of monochrome or color treatment.
- Look for rendering errors, strong sharpening halos, missed retouching and conspicuous color discontinuities.
- Confirm file dimensions and embedded profiles with a suitable information tool.
- Open several delivered downloads after passing through the actual service, using a separate destination so the test cannot replace the masters.
A second review after a break is useful for problems that become invisible during a long edit. Where possible, have another person check the delivery list and spelling in album material. They do not need to reinterpret the whole artistic edit to catch a missing file or a wrong date.
If a gallery download is smaller than expected, distinguish service-generated previews from the original download option before changing exports. If a client reports a crop issue, identify the file version and print ratio first. The right fix may be another output crop, not a new edit of the source.
Keep the checked delivery locally after upload. Test the recipient’s download path with a small selection and verify that the resulting archive opens, the filenames remain understandable and the expected full-size files are present. Record any intentional service resizing. An upload-complete message is not proof that the client can retrieve the intended version, especially when separate preview and download settings exist.
Hand an album designer a coherent, traceable package
Keep the album selection separate from the main delivered set. Supply the selected finished images, exact image IDs, an agreed sequence or story outline, names and dates as confirmed, and the selected product specification. Include any image whose crop or placement is restricted.
A photographer’s favorites and a client’s must-include list may differ. Reconcile those lists before a detailed layout, explaining where a requested image is a supporting moment rather than a suitable full-spread photograph. Keep an alternate if a selected frame lacks enough usable pixels for the proposed placement.
Approval of image choices is not approval of the layout, cover text or final order. Use distinct review checkpoints. The album design guide covers that production process in depth. Lightbox Pro’s reviewed source does not contain a completed album designer or synchronized hosted client selections; local sets can prepare the selection for your established external tools.
Close the job with records that survive the delivery link
Retain the source archive, final catalog decisions, editable work, delivered outputs and a concise record of what was supplied. Keep the delivery version and album approval together. A temporary gallery link may eventually expire; it should not be the studio’s only evidence of the finished work.
Test restoration to a separate location rather than over the working job. Open a catalog copy, resolve representative originals, inspect a saved edit in its editor and open the final output. Record any missing fonts, profiles, sidecars or linked documents while they are still recoverable.
Leave the next person a useful starting point: source locations, final selection, editor version, output presets, delivery date, album version and outstanding matters. That person may be your future self answering a print request years later. A dependable post-production process makes that request a retrieval task instead of a reconstruction exercise.