Nano Banana image editing with private references

Use the highest-quality source reasonably available, with the important subject unobstructed and large enough to inspect. Crop away browser controls, borders, watermarks you do not own, and unrelated objects that may be interpreted as part of the edit. If the source already has the desired framing, select an output ratio that respects it.

When several references are necessary, assign distinct roles. One image may define the subject, another the material finish, and another the color system. Avoid supplying multiple competing identity images or several unrelated style examples. The model needs a hierarchy, and the prompt should state that hierarchy explicitly.

Begin the instruction with what must remain: product silhouette, face, camera angle, layout, logo position, or another protected property. Follow with the requested change: replace the background, adjust the season, alter a material, add controlled lighting, or translate the scene into a new medium. This structure makes the review criteria visible before generation.

Be cautious with phrases such as exactly the same. AI output should be reviewed for identity and legal requirements, and small variations may remain. If exact typography or a regulated claim matters, plan a downstream design check rather than assuming a generated pixel is authoritative.

• Write the protected identity, geometry, and composition requirements before style changes.
• Describe allowed changes as a bounded edit instead of asking for a general improvement.
• Use a downstream design review for exact text, claims, and legally sensitive details.

Select the target aspect ratio according to the final placement. If the output differs from the source ratio, tell Nano Banana how to extend or crop the composition and where new space should appear. Choose the available format for the next stage, then request the protected quote after all reference files and controls are final.

The model page displays the current input limits and output options from the production Catalog. Use those controls instead of assuming the limits from another Nano Banana version. The base model, Pro, Nano Banana 2, and Lite variants have separate adapters, and their names are not interchangeable in a production request.

Review preservation rules before judging style. Compare silhouette, proportions, facial structure, viewpoint, layout, and protected colors. Then inspect the requested change for seams, shadow consistency, reflections, perspective, and whether new objects interact naturally with the unchanged subject.

Use the result stored in the private Library as the review file. If one protected property drifted, strengthen that rule without rewriting successful styling. If the source itself caused ambiguity, improve the crop or replace the reference. This creates a traceable edit loop instead of repeatedly asking the model to try again.

When several references are necessary, decide which source governs identity, composition, material, palette, and style. Do not assume the model will infer that hierarchy from upload order alone. Describe the primary source first, state the attributes that cannot change, and then explain the narrow contribution of each secondary image. If two references disagree on face, product shape, camera angle, or light direction, remove the weaker source or explain the intended conflict explicitly.

Judge an edit by preservation and change separately. First verify that protected geometry, identity, logos, and framing survived; then evaluate whether the requested background, material, color, or atmosphere actually changed. This two-pass review prevents a dramatic but destructive image from being mistaken for a successful edit. Save the accepted result and the reference-role note together so later variants can preserve the approved structure without reconstructing the original intent.

Compare the accepted candidate with the primary source using a checklist, not only a side-by-side impression. Mark every protected property as preserved, changed, or uncertain. Pay special attention to details near the edited region, where texture, shadows, logos, and edges can drift even when the main requested change looks convincing.

If the edit boundary is too broad, revise the instruction to name both the allowed change and the areas that must remain untouched. Do not keep adding style words to solve a preservation failure. A narrower transformation and a cleaner reference hierarchy usually provide more useful evidence than a longer but less structured prompt.