Cull, Then Edit, Without Switching Apps

For years, a normal post-production routine meant two separate stops: one tool to cull, a different one to edit, with an export and import step wedged in between just to get your selects from one to the other. It works, but it also means every shoot carries a small tax of context switching, remembering which app has the latest version of a photo, and keeping culling decisions in sync with editing ones. An intelligent Studio project removes that tax by putting culling and editing in the same place, in whatever order actually suits how you work. The difference shows up less in any single photo and more in how the whole day feels.

The old habit: cull here, edit there

Most photographers did not choose a two-tool workflow so much as inherit it, because culling and editing used to live in genuinely different pieces of software with different strengths. The cost of that split rarely shows up as one big problem. It shows up as dozens of small ones: exporting a folder of selects, waiting for an import to finish, occasionally re-culling a frame you already decided on because you lost track of which tool held the current version.

None of that is a reflection of bad habits. It is just what happens when a workflow is stitched together from separate tools that were never designed to share a project in the first place. Multiply those small frictions across every shoot in a season and they add up to something closer to a second, invisible job layered on top of the actual editing.

When two tools quietly fall out of sync

The subtlest cost of a two-tool workflow is not the time spent exporting and importing, it is the small inconsistencies that creep in when culling decisions and editing decisions live in different places. A photo gets rejected during a second look in the editing tool, but the culling tool still lists it as a keeper. A rating changes halfway through a project, and now two files disagree about which version is current. None of these mistakes are dramatic on their own, but tracking them down costs real time, and they only happen because the two halves of the job were never actually talking to each other.

Keeping culling, editing, review, and export inside one project removes the disagreement by removing the second copy of the truth. A rating, a flag, or a color label only exists in one place, so there is nothing left for it to drift out of sync with.

What “non-linear” actually means day to day

In a Studio project, culling, editing, review, and export are stages within one project rather than separate tools you move between. Non-linear means you are not required to finish one stage before starting the next. Cull half a gallery, start editing your favorites from that half, go back and finish culling, then export a batch while you keep refining the rest. The order follows how you actually think through a shoot instead of forcing you into a fixed sequence.

This matters most on the shoots that do not fit a tidy, linear process anyway. A wedding with an early first look, a product session with a client waiting on proofs, a family shoot interrupted halfway through by a toddler’s nap, all of these benefit from a workflow that bends around the day rather than demanding the day fit the software.

A built-in editor that removes the reason to leave

The built-in editor, currently in beta, is what makes staying in one project realistic rather than just convenient in theory. It offers manual sliders and a histogram for real, hands-on adjustment, crop and straighten you can apply after an AI pass, presets you import from Lightroom or build yourself, and versions so you can branch a photo to try a different treatment without touching the original. None of these require opening a separate program, which is the entire premise of keeping cull and edit together in the first place. Quality is comparable to Lightroom, though not every AI tool is inside the editor yet, so it is fair to treat this first version as a strong early release rather than a full replacement for every tool you currently reach for.

Culling a shoot inside the Imagen project view

Because the manual tools and the AI tools sit side by side in the same interface, moving between an automated pass and a precise hand adjustment does not require switching context the way moving between two separate applications does. Familiar shortcuts and a familiar layout keep that transition small.

A day in the workflow, start to finish

Picture a Sunday full of back-to-back portrait mini-sessions. You upload each session as its own project, and the first edited batches start arriving by timestamp while later sessions are still processing. Between clients, you review the early frames, apply more than one AI Profile to a chosen set of photos when a client wants two distinct looks from the same short session, and fine-tune a handful of shots with the manual sliders. By the time the last session wraps, most of the earlier galleries are already reviewed and close to ready, without a single export and reimport step anywhere in the middle of the day.

The same pattern holds on a bigger single shoot. On a wedding day, you might cull and start editing the getting-ready coverage while the ceremony is still uploading, then repeat that for each block of the day as it finishes, rather than treating the whole event as one giant batch you cannot touch until every frame has processed.

Compare either scenario to the old routine: cull each block in one tool, export the selects, open a second tool, reimport, edit, and only then move on. Doing that several times in one day is where a surprising share of a photographer’s actual working hours used to disappear.

If you still want to finish in Lightroom, that stays easy

None of this requires leaving Adobe behind. Lightroom remains a full partner in this process, not a tool you are asked to drop. AI Profile and AI tool edits carry over as XMP, while manual adjustments, ratings, flags, and color labels made inside Imagen stay in Imagen, so if a shoot is finishing in Lightroom, review your choices first and download once processing is complete. Whether you finish entirely in one project or hand off partway through, the choice depends on your workflow, not on a limitation in either direction.

This flexibility also helps mid-project. If you start a shoot assuming you will finish everything inside Imagen, then realize partway through that a specific set needs finishing touches only Lightroom Classic offers, switching plans does not mean starting over. Export what is ready, keep working on the rest, and decide the finishing tool set by set rather than committing to one path before you have seen the results.

For more on structuring a full day of back-to-back sessions, our valuable tips library has practical guidance worth a look.

Where the assistant fits into a single-project flow

With culling and editing sharing a project, the assistant can work across both instead of being limited to one stage. Ask it to find every photo from a specific session where a client is genuinely laughing, and use that shortlist as your starting point for both the final cull and the edits you spend the most time on. It currently works by recognizing what is in a shot rather than pinpointing where within it, so placing a mask on one exact spot is not something it does yet, and very subjective requests can still be a stretch.

The same search works weeks later too, when you are trying to recall which client asked for a specific variation on a look. Search by what actually happened in the photo rather than relying on memory or a file naming system to reconstruct it.

Within those limits, it is a fast way to move between the two stages without losing track of what you were looking for, which matters most on a day with several sessions stacked close together and very little time to re-orient between them.

What’s new in Imagen: Imagen is now an intelligent, agentic Studio for professional photographers, so culling and editing share one project and you never switch apps between them. The built-in editor (Beta) brings manual sliders, a histogram, crop, straighten, presets, and versions, and you can still send AI edits to Lightroom Classic as XMP or export JPG, TIFF, or PNG from Imagen. The Studio is rolling out gradually as a beta.

Frequently asked questions

Do I lose anything by keeping culling and editing in the same project?

No. You get the same manual review, ratings, and controls either way, without the export and import steps a two-tool workflow used to require, and without the sync problems that come with keeping two separate records of the same decisions.

Can I still send finished work to Lightroom afterward?

Yes. AI edits carry over as XMP, and manual adjustments made in Imagen stay with the project, so exporting to Lightroom for final delivery is fully supported.

Does moving between culling and editing in one project cost more?

No. Working across both stages in one project does not add cost. What you pay for, on a pay as you go plan, is tied only to the photos you export at the end.

Is this a separate app I need to learn?

No. It is the same Imagen you already use, with culling and editing now sharing one project instead of living in separate tools.

Ready to stop exporting and reimporting between two tools? See how one project in Imagen’s new Studio handles culling, editing, and export together at imagen-ai.com.