
Portrait generators built around fictional companions started as a novelty, but they settled into something more durable: a general-purpose tool for making a believable human character and keeping that character consistent across dozens or hundreds of images. That skill turns out to be useful well beyond the original use case. Concept artists use it for cast sheets. Indie game developers use it for dialogue portraits. Comics creators use it to previsualize scenes before committing to final linework. Writers use it to pin down what a protagonist actually looks like so their prose stays anchored.
The reason the topic keeps generating friction is that the same pipeline can produce a warm, stylized, clearly fictional character or something that looks uncomfortably like a real person who never agreed to appear. The technology does not distinguish between those outcomes. The operator does.
This guide treats AI companion portraiture as a craft problem first and an ethics problem second, because in practice the ethics only become manageable once you understand the mechanics. If you know exactly which knobs control identity, likeness, and realism, you can steer a project toward the safe side of the line deliberately rather than by accident.
Most modern portrait generation runs on diffusion pipelines with a text encoder, a denoising network, and a decoder. You give it a prompt, it starts from noise, and it iteratively resolves that noise toward something that matches the conditioning. Character consistency, the hard part, comes from additional conditioning signals layered on top.
The model does not "draw" a woman with green eyes. It navigates a high-dimensional latent space where regions correspond to visual concepts, and your prompt steers which region gets sampled. This is why small wording changes cause disproportionate shifts. "Soft studio light" and "window light" can produce nearly identical images, while "soft light" and "soft lighting, film grain" can produce radically different ones.
The practical way to lock a character is to give the model a consistent identity signal. Three approaches dominate:
If your goal is a single striking image, image prompting is enough. If your goal is a recognizable character in fifty different scenes, budget time for a LoRA and a clean dataset.
Identity is only half the problem. ControlNet-style conditioning lets you impose a skeleton, a depth map, or an edge map so the character holds a specific pose regardless of prompt drift. This is what separates a character sheet from a pile of unrelated portraits. Pair it with regional prompting so clothing and background tokens do not bleed into the face region.
The workflow below assumes you are building a fictional character for creative work. It is deliberately structured so that identity, style, and scene are handled in separate passes, which makes debugging far easier.
Spend ten minutes on a plain text document. Capture age range, ethnicity or heritage, build, hair, distinguishing marks, wardrobe palette, and personality in three adjectives. Do not skip this. Prompts written from memory produce inconsistent characters because you unconsciously re-describe them differently each session.
Split your prompt into three blocks that never mix:
Keeping identity text identical across every generation is the single highest-impact habit. Most "the face keeps changing" complaints trace back to rewording the identity block between runs.
Produce 12–20 fast, low-step images. You are not looking for a finished picture; you are looking for a face that reads correctly at a glance. Reject anything with anatomical ambiguity in the hands, ears, or jawline, because those flaws survive upscaling and get more expensive to fix later.
Once a face works, record the seed and the exact prompt string. From there, change one variable per batch: expression only, then wardrobe only, then setting only. This is slow at first and dramatically faster overall, because you always know which change caused a regression.
Do not regenerate a good image because of one bad hand. Mask the region, describe only that region in the inpaint prompt, and keep the denoise strength moderate. Two or three passes almost always resolve fingers, jewellery, and eye reflections.
Move the finished frame into an editor for colour grading, grain matching, and any compositing. A mild grain pass and a subtle vignette do more to sell realism than another 30 sampling steps.
Store the prompt, seed, model version, LoRA hash, and control settings alongside the image. Six weeks later you will not remember which checkpoint produced your best result, and re-deriving it is painful.
A cast sheet with six expressions and four outfits per character is a genuine production asset. Dialogue portrait systems need exactly this kind of consistency, and generating variants is far cheaper than commissioning a full sheet before the script is locked.
Boards do not need beauty, they need clarity. Generating 30 rough frames of a scene lets a director test blocking and pacing before a single camera is set up. Keep the style block deliberately plain so nobody mistakes a board for a finished frame.
Writers and worldbuilders use portrait generators to keep a city's inhabitants visually coherent: clothing silhouettes, colour palettes, age distribution. The output is a reference library, not a deliverable.
Some people simply enjoy designing a character and following them through imagined scenes. That is a legitimate hobby with a long lineage in fan art and tabletop roleplay. The ethical questions below apply to how you publish and label the results, not to whether the private activity is allowed.
This is the core issue and it is not complicated. If a generated image is recognizably a real, identifiable person, and that person has not agreed to it, do not make it and do not publish it. Identifiability is the test, not intent. "It is just a lookalike" stops being a defence the moment a reasonable viewer names the individual.
Practical safeguards that work:
Sexualized depictions of minors are illegal in many jurisdictions and prohibited by essentially every mainstream platform. Abstraction does not help: an anime-styled character described as a schoolchild falls under the same rule. Set your character brief with an explicit adult age range and keep it there.
Generating intimate imagery of a real person without consent causes documented harm and is criminal in a growing number of countries. Treat it as a hard line with no creative exception, and treat "private, never shared" as a weak justification, because files leak and habits escalate.
Style imitation sits in a legal grey zone that varies by jurisdiction. Practically, avoid prompts naming a living artist's style and instead describe the visual qualities you actually want: palette, line weight, lighting model, era. You get a more controllable result and sidestep the argument entirely.
Label AI-generated imagery when the audience could reasonably assume it is a photograph. News, advertising, dating profiles, and claims about real events all require disclosure. Personal creative projects usually do not, but a small watermark costs nothing and prevents awkward conversations later.
Hosting platforms vary widely: some ban all photorealistic human generation, some allow it with disclosure, and some restrict only specific categories. Before you build a large body of work, read the acceptable-use policy of the tool you are using and the platform you intend to publish on. Nothing is more frustrating than finishing a 60-image set on a service that quietly prohibits the category.
Also consider retention. Free tiers frequently reserve the right to use submitted content, and reference images of real people should never be uploaded to a service whose data practices you have not checked. Local generation on your own hardware removes this concern entirely if you have the GPU headroom.
Rather than chasing feature checklists, evaluate against your real constraint.
| Your priority | What to look for |
|---|---|
| Fast one-off portraits | Strong image-prompting, generous free tier, simple UI |
| A consistent character across many images | Character adapter training, seed control, batch tools |
| Precise pose and composition | ControlNet-equivalent conditioning, inpainting, regional prompts |
| Privacy for sensitive references | Local or self-hosted options, no-retention settings |
| Commercial publishing | Clear licence terms, indemnification language, output ownership |
Check three things before committing: whether you own the outputs commercially, whether the service trains on your uploads, and whether the moderation policy permits your category. Those three answers eliminate most candidates immediately.
Is it legal to generate a fictional companion's portrait?
In most places, yes. Legality turns on whether the output depicts a real identifiable person, whether it is sexualized and non-consensual, and whether it involves minors. Fictional adult characters generated without real-person reference are broadly permissible, though platform rules may be stricter than the law.
Do I need permission to use a photo of a friend as a style reference?
Yes, if the output remains recognizable as them. Ask explicitly, in writing, and say how you intend to use and publish the image. A casual "sure" over text about a different context is not sufficient.
How many reference images do I need for a consistent character?
For image prompting, three to five varied angles. For a LoRA, 15–40 images covering different expressions, lighting conditions, and backgrounds, with a consistent face crop. More is not better if the set is repetitive.
Can I tell whether an image was AI-generated?
Not reliably by eye. Metadata often strips on upload, and detectors produce false positives on real photographs. Treat provenance as a disclosure question rather than a detection question.
Should I watermark AI portraits?
For personal work, optional. For anything published as factual, advertising, or on a dating profile, yes. Many platforms now require it, and a discreet corner mark protects you without ruining the image.
What is the fastest way to fix a bad face in an otherwise good image?
Mask the face region, keep the prompt minimal and identity-focused, and use moderate denoise strength. Regenerating the whole frame loses everything else that was already working.
Where should I keep my prompt library?
A plain spreadsheet or a text file in version control. Include prompt, negative prompt, seed, model version, adapter hash, and a thumbnail path. Future you will be grateful.
The technical side of companion portrait generation is now genuinely accessible: a decent GPU, a curated reference set, and a disciplined workflow will get you consistent, striking results. The ethical side requires no special expertise at all, just a simple rule applied consistently. Generate fictional adults, never identifiable real people without documented consent, never minors, and disclose when the audience could be misled.
Everything else, style, mood, subject matter, and how far you push a character's story, is a creative decision that belongs to you. The craft is in making a character who reads as a person across a hundred frames. The responsibility is in making sure that person is not someone real.

Alexander
Vidu Q4 alternatives compared: Kling 4.0, Seedance 2.5, Wan 3.0, and Runway Gen-4 — 4K support, input modes, durations, audio, and what each costs in credits on Domer.
The top 4K AI image generators on Domer compared: Flux 3 Klein, Nano Banana 2.1, GPT Image 2.5, GPT Image 2, and Nano Banana Pro — 4K credit costs, reference limits, and speed.
Nano Banana 2.1 vs GPT Image 2.5 Flare compared: credit costs per resolution, aspect ratios, reference images, text rendering, and which tasks fit each model.