Leonardo’s Phoenix family is documented as a foundation model with separate 0.9 and 1.0 identities. A workflow that mixes reference images should pin both the generation model and the guidance mode rather than relying on the Phoenix name alone.
A family with distinct versions
Leonardo’s model documentation lists Phoenix 0.9 and 1.0 with separate identifiers and style settings. The product site describes an emphasis on prompt adherence and creative control. Those are the vendor’s capability descriptions, not a benchmark this editorial team independently measured. Exact IDs and enabled features can change, so a production record should retain the actual response model/version.
References are not all the same
Leonardo’s official Image Guidance documentation distinguishes Style Reference, Content Reference and Character Reference. A style reference can guide treatment while a content reference can influence structure; character reference may help maintain resemblance but the documentation says it is not a face-swap guarantee. Choosing the wrong guidance type is a common reason a team gets aesthetically consistent art with the wrong subject.
A reproducible character concept brief
Describe physical costume elements, pose, framing and palette in separate clauses. Supply only reference images you are permitted to use. Make one neutral baseline image and a small scene grid. Inspect hair, clothing marks, accessories, face shape and background across results. If output identity drifts, do not simply increase guidance strength indefinitely; adjust the reference strategy and accept the limits of the model.
API parameters require version checks
The official API guide names reference parameters including init image identifiers and strength types; supported preprocessors depend on the model. Do not copy numeric IDs from an archived example into a new integration without rechecking the current endpoint. Store a model ID, guidance type, source image ID, prompt version and response metadata. API availability and developer permissions are separate from web-app access.
Human depiction and rights
A reference image containing a real individual requires appropriate consent and purpose limitation. Character consistency is not authorization to clone a person’s likeness. Record licensed artwork inputs, trademark constraints and whether the final design is clearly fictional. A photoreal person or product generated from references should not be passed off as actual photography.
Where Phoenix fits
Phoenix can suit teams needing guided character or style concepts with a documented platform. For precise pose geometry, a control-oriented local stack may be more appropriate; for exact brand assets, path-editable vector tools may be necessary. Do not choose on proprietary scores alone: test your own brief with documented versions before committing to production.
Worked scenario: a hypothetical production brief
Example: A publisher commissions six illustrations featuring a fictional courier. A style reference establishes inked linework, while a character reference supplies the costume and silhouette. The editor inspects every panel for continuity of bag, hat and face details, not just color mood. If the character changes identity, that panel is rejected. The team records the actual Phoenix model ID and reference settings used for the accepted panels. It does not claim this method guarantees continuity, and the character remains a fictional design cleared under the publisher’s own art rights.
Additional editorial and quality safeguard
For a comic or storyboard, create a character bible containing agreed costume shapes, characteristic props, color codes and unacceptable identity drift. Human reviewers should compare the same landmarks across panels before approving them. Images with consistent palette but different faces are not successful continuity. Ask the model for a new variant rather than editing the story bible to rationalize mistakes.
Reference-image and rights boundary
The described Leonardo Phoenix workflow (Phoenix 0.9 / 1.0) is based on documentary source material, not an independently generated portfolio or test. A reviewer should compare the exact version and reference controls in the intended interface and clear the rights to every uploaded photo, likeness, logo and final asset. Do not infer guaranteed visual consistency, commercial permission or worldwide availability from a product feature page.
Sources & Further Reading
- Leonardo AI — Phoenix model versions documentation (living documentation; version pin required)
- Leonardo AI — Generate Images Using Image Guidance (living documentation; version pin required)