Versions: Try a Different Look Without Touching the Original

Every photographer has finished an edit, looked at it for a second, and wondered what the same photo would look like with a completely different treatment. Maybe the ceremony shot would work better in black and white. Maybe the product photo needs a punchier version for social alongside the accurate one for the catalog. Until now, chasing that second idea usually meant duplicating a file, editing the copy, and hoping you could tell them apart later. Versions solves that specific problem inside Imagen’s editor (Beta).

Here is what Versions actually does, why it matters more than it sounds like on paper, and how it fits alongside the rest of the editing tools you already use.

The problem with committing to one edit too early

Editing decisions compound. Once you have pushed the color, the crop, and the contrast in one direction, trying a genuinely different direction on the same file usually means starting over or working backward through your own adjustments. That friction quietly discourages experimentation, even when a second treatment might be exactly what a client or a gallery needs. Photographers end up settling on the first reasonable edit more often than they would like to admit, simply because trying a real alternative is inconvenient.

Deadlines make this worse, not better. When a gallery is due the same day it was shot, there is rarely time to second-guess an edit once it is finished, so the second idea quietly gets dropped even when it might have been the stronger choice. Versions removes that trade-off entirely, since branching a copy takes seconds rather than the minutes or hours a full re-edit would cost.

The cost of that is invisible until you see the alternative that never got tried. A moody, desaturated treatment of a reception dance floor shot might outperform the brighter default in every way, but only if someone actually builds it and looks at it next to the original.

What Versions actually does

Versions lets you branch a copy of a photo directly inside the same project, without ever touching the original edit. The branch carries its own independent settings from that point forward: a different AI Profile, a different preset, different manual adjustments, all separate from the version you started with. Nothing about the original is altered or put at risk while you experiment on the branch, so there is no real downside to trying something.

This is different from simply duplicating a file in a folder somewhere. Versions live together inside the project, next to each other, so comparing them is a matter of looking rather than hunting through exports or file names to remember which is which.

When photographers reach for a second version

A few situations come up often enough to be worth naming directly. A hero image, like a first look or a ring shot, where you want to weigh a warm, traditional edit against a cooler, more editorial one before either goes to the client. A product shot that needs one version tuned for an accurate catalog listing and a second version punched up for a marketing post. A portrait session where a client specifically asks to see both color and black and white before choosing. In every one of these, Versions removes the choice between committing early or doing double the manual work.

It is also useful simply as a safety net. If you are not sure a bolder edit will land, branch it, look at it next to the safer original, and decide with both options actually in front of you instead of trying to imagine the alternative in your head.

Event photography turns up a similar case. A gallery from a conference keynote might need one version graded for the sponsor’s recap deck and a second, warmer version for attendee social shares, both pulled from the same source frame rather than reshot. Building both inside one project, rather than juggling separate export folders for each audience, keeps the whole gallery organized in one place.

A concrete example: one photo, two directions

Picture a backlit outdoor portrait taken right at golden hour. The original edit leans warm, bright, and soft, which suits most of the gallery. But one particular frame, with strong rim light and a dramatic sky, might actually be stronger as a punchier, more contrasty, slightly cooler edit that reads more editorial than romantic. Instead of guessing which direction the client will prefer, branch a version, push that copy toward the bolder treatment, and put both in front of the client side by side.

Refining an AI edit with manual sliders in the Imagen editor

This is a small example, but it repeats constantly across a working photographer’s week: a family session where a client cannot decide between a bright, airy look and a moodier one, or a corporate headshot where the brand guidelines call for one treatment but the subject clearly looks better in another. Versions turns each of these from a guessing game into an actual comparison.

Versions alongside your AI Profile and presets

Versions becomes more powerful once you connect it to the rest of the editor. Apply your Personal AI Profile to the original and a different preset, or a second AI Profile, to the branch, and you get two fully realized treatments to compare rather than one edit and one guess. Because applying more than one AI Profile to a set of photos is already supported, testing a second look across several images at once, not just one, is realistic rather than tedious.

Presets, whether imported from Lightroom or built inside Imagen, are a natural starting point for a branch. Keep the original tied to your standard look and use the version to test a new preset before deciding whether it earns a permanent place in your workflow.

This pairing is especially useful during a busy season when you are still refining your Personal AI Profile. Branch a small batch of already-delivered photos, run an updated profile against the branch, and compare it to the original delivered version to see exactly how much your editing style has evolved, without touching a single file a client has already received.

Fine-tuning each version on its own terms

Once a version exists, it behaves like any other photo in the editor. Manual sliders and the histogram apply independently to each branch, so you can push the version further in its own direction without dragging the original along with it. Crop and straighten work the same way, which matters when a bolder treatment also calls for a tighter or more dramatic crop than the safer version needs.

That independence is really the whole point. A version is not a preview or a filter layered on top of the original, it is a genuinely separate edit that happens to live next to its source, which means it can be refined exactly as carefully as any other photo you are finishing for delivery.

This matters just as much for smaller adjustments as it does for dramatic ones. A version does not need to be a completely different treatment to earn its place, sometimes the only difference worth testing is a slightly tighter crop or a touch less contrast, and having that comparison available in the same project makes even a small decision easier to make with confidence.

Exporting only the version you actually want

Because pricing follows what you export rather than what you experiment with, building a version to compare against the original does not cost anything on its own. You can branch, adjust, and review as many alternate treatments as you want, and pay only once you decide which version, or versions, actually leave the project. For a client-facing choice, like the color versus black and white example, that means you can genuinely offer both and export whichever one wins, instead of guessing in advance which one to build.

The same content-aware billing that applies to individual AI tools applies here too. If a version only differs in a tool that detects no relevant content on a particular frame, that frame is not charged for a step it never actually needed, the same as it would not be charged on the original. Versions does not multiply your cost just because you built more than one option to look at.

If you want to see how Versions works alongside batch editing and presets in a full workflow, our valuable tips library walks through several related techniques in more detail.

What’s new in Imagen: Imagen is now an intelligent, agentic Studio for professional photographers, built around one project where you cull, edit, review and export in any order. In the built-in editor (Beta) you can branch versions of a photo, set a warmer or moodier treatment beside your AI edit, and keep the one you prefer, with sliders, crop, straighten and presets close by. The Studio is rolling out gradually.

Frequently asked questions

Does creating a Version change or risk my original edit?

No. The original stays exactly as it was. A version is a separate branch with its own settings, so nothing you do while experimenting on it affects the source edit.

Can I apply a different AI Profile to a version than the original?

Yes. Each version carries independent settings, including its own AI Profile, preset, and manual adjustments, so you can genuinely compare two different treatments rather than two shades of the same one.

Do I pay extra just for creating a version to compare?

No. Pricing is tied to what you export, not what you build to compare. You can create and review versions freely and pay only for whichever one you ultimately export.

Is Versions the same as exporting a duplicate file?

Not quite. A version lives inside the same project as the original and carries its own independent edit, which makes side-by-side comparison and later adjustment far more straightforward than managing separate duplicated files.

Have a photo that deserves a second look? Branch your first version inside Imagen’s new Studio, where you cull, edit and export in one project, and compare it against the original at imagen-ai.com.