How to Keep a Simple Version Log for AI-Assisted Portraits

You open a folder and find three images called final, final-new, and final-really-new. One has better lighting. Another has the jacket you wanted. You cannot remember which reference photo produced either result.

That is the problem I would solve before generating another image. You do not need a complex production system. A small version log can help you remember what changed, compare results fairly, and avoid sharing the wrong file.

Here is a practical workflow for a personal portrait or a couple-photo concept.

Disclosure: This article comes from the team behind Imya and Tryonr. Their tools are optional examples, not independent recommendations. The cover is an AI-generated editorial illustration, not a demonstrated result from either product.

Save your source photos separately from generated images. Give the folder a clear name such as portrait-originals and avoid saving edits over those files.

Choose a short reference label: reference-a, for example. Your working notes can refer to that label without repeating personal details about the people pictured.

Before uploading anyone’s photo, get their permission and review the service’s current privacy and retention information. A folder naming system does not provide consent, and a private folder on your computer does not make an upload private.

Write a single question before making a change. “Would a darker jacket separate the subject from this background?” is more useful than “Make this better.”

For a clothing-focused concept, you might use Tryonr’s outfit preview tool to explore that question. Keep the original reference and intended change in your notes.

The preview is not a fitting-room measurement. It cannot establish actual comfort, garment sizing, or how a fabric will move. AI may also change details you did not request, so record those differences rather than ignoring them.

Use a plain note, spreadsheet, or notebook. For each version, record:

• File name: a unique label such as portrait-v03.

• Reference: which original file you used.

• Intended change: the one thing you wanted to explore.

• Observed differences: what actually changed, including unwanted changes.

• Decision: keep, revise, or reject, with a short reason.

Here is a hypothetical entry: “v03; reference-a; darker jacket; stronger contrast but altered cuff and hand; revise.” It captures both the useful part and the limitation without pretending the result was fully accurate.

Changing the outfit, background, pose, and lighting together makes it difficult to identify why you prefer a result.

If you next explore couple portrait concepts with Imya, start a separate scene version. Note the agreed clothing direction and the new question about composition or setting.

You do not need to use both tools or pass an image between them. Treat each experiment as its own optional step, using references you are permitted to upload. A simple phone photograph or a paper sketch may answer your planning question just as well.

Inspect faces, hands, garment edges, background details, and any text. Compare against the originals when identity or clothing accuracy matters.

Record unresolved issues. “Approved as a mood concept, not an accurate product image” is a more useful label than a vague “done.” If you share a generated image, make its nature clear wherever a viewer could reasonably mistake it for an actual photograph or product result.

Keep the exported file name in the log. That small habit helps prevent sending an earlier version by accident.

A version log is not about making a creative project bureaucratic. It is about remembering your decisions and keeping uncertainty visible.

Start with one reference label, one question, and one short review note. The next time you compare two portraits, you will know what you are comparing—and why.