Nano Banana Getting Started: First Render

Updated: 2026-08-21. Available models, resolution, and billing on each entry follow gemini.google.com and the image generation docs for that day.

Introduction

This is hands-on Nano Banana for beginners: not a long model review, but a path to your first shippable image—what to prepare, how to write round one, how to iterate, how to use references, and what to check before handoff. Beginners should default to Nano Banana 2 (Gemini 3.1 Flash Image / gemini-3.1-flash-image, per docs that day). For quick direction only, mix in Lite.

What this guide solves

• Account, acceptance criteria, and asset rights before you generate
• A first generation that isn’t a pile of style adjectives
• Multi-turn edits that change one thing per round
• Clear reference control scopes and a delivery self-check

Prep: 10 minutes before you start

1. Pick an entry and log identity

Start with one (try more later, but bind one entry per evaluation):

Entry	Link	Notes
China-friendly third-party	Nano Banana 2	Not Google official; read privacy notes first
Official Gemini	gemini.google.com	Matches Google account system
Developer docs	image generation	Look up model IDs and capabilities

In notes: date + URL + on-screen model name. Network/account details for China: China access.

2. Pick a tier (beginner default)

• Default: Nano Banana 2 — balanced; stronger multi-turn and multi-ref; can push higher resolution when docs allow (~4K)
• Direction only: Lite — faster/cheaper, ~1K oriented; not for complex multi-ref
• Brutal acceptance: Pro — high-precision complex jobs; save for finals

Tier comparison: Nano Banana 2 guide.

3. Write a mini acceptance card

Fill these four lines before opening chat:

Use: ________ (e.g. 16:9 article hero)
Subject: ________ (one object/scene; state count)
Must-have: ________ (margin, light, one style sentence)
Ban: ________ (text / watermark / extra limbs / unauthorized brands)

Generating without an acceptance card means you can’t tell which step failed.

4. Assets and rights

• Upload only refs, logos, and packaging shots you have rights to use
• Faces, employee photos, and client products need confirmed authorization
• Don’t ask to imitate a living artist’s unique style

First render: step-by-step

We’ll use a “ceramic lamp hero.” Swap the subject; keep the structure.

Step 1: Choose aspect—say it in sentence one

Lock canvas before content. Common: article hero 16:9, square 1:1, vertical 9:16.

Step 2: Send round-one prompt (no text)

Use: 16:9 blog hero; leave ~30% empty on the right for a title.
Subject: one matte ceramic table lamp, cream shade, slightly left of center on a light wood desk.
Camera: eye-level, soft side light, clean blurred background.
Style: real product photography—not illustration, not sci-fi.
Ban: any on-image text, watermarks, borders, extra cords, warped shade.

Step 3: Composition check only

Ask four questions:

1. Is the subject a lamp (not some other fixture)?
2. Is aspect 16:9 with right-side margin?
3. Any clear defects (collapsed shade, floating object, broken perspective)?
4. Any banned elements (type, watermark, mystery logo)?

Any fail → full redraw or rewrite the prompt—don’t enter fine edits yet.

Step 4: Save a usable frame

Download or pin the composition-correct result and note v1-composition-pass. Later edits start from those constraints.

Step 5: Raise clarity only after composition passes

Then raise resolution via UI options (Nano Banana 2 can reach ~4K when docs support it). Higher resolution cannot rescue wrong composition.

Iterative edits: one variable per round

Once you have a usable frame, follow three rules:

1. State what stays (camera, pose, palette, background)
2. Request one change only
3. Re-check the acceptance card immediately; pass before the next round

Material change

Keep the same composition, camera, lamp shape, and margins.
Only change the base from matte ceramic to walnut wood.
Do not add text; do not change shade color.

Light change

Keep subject, composition, and materials.
Only change light to soft morning window light with lighter shadows.
Do not change the number of background objects.

How to roll back a bad edit

• Return to the last still-correct frame and re-instruct
• Or start a new chat: paste the acceptance card + a short description of the good frame; attach that frame if needed
• Avoid stacking 10 contradictory edits in a drifted long thread

On multi-turn strength, 2 beats Lite; stacked hard constraints can step to Pro. See Nano Banana 2 guide.

How to use reference images

References are not “drop into chat and hope”—you declare control scope.

Recommended phrasing

Image 1: lamp silhouette and proportions (geometry must stay close).
Image 2: palette only (warm wood + cream)—do not copy Image 2 background clutter.
Generate: 16:9, lamp on light wood desk, right-side margin; no text or watermark.

Practical rules

Practice	Note
Say what each image owns	Geometry / palette / scene mood / character identity—separately
Limit count	Beginners start with 1; strong multi-image consistency → Nano Banana 2, not Lite
On conflict, write priority	“Silhouette from Image 1; color from Image 2”
Copyright	Unlicensed images are not commercial delivery evidence

Products and logos: after generation, compare item-by-item to brand source files—“looks close enough” is not a pass.

Delivery checklist

Before sending externally, tick:

• Use and aspect correct; crop/title safe area enough
• Subject type and count correct; no obvious defects or extras
• Iteration did not introduce surprise text, watermarks, or wrong logos
• If refs used: consistency OK and rights traceable
• Required on-image text proofed character-by-character; zero-tolerance copy moved to post layout
• Checked at target display size (thumbnail + full)
• Logged entry, model name/ID (that day), prompt summary for reproducibility
• Commercial release: rights confirmed; sensitive info (faces, addresses, unpublished products) handled

Quick access

• China-friendly third-party: Nano Banana 2
• Official Gemini: gemini.google.com
• Image docs: ai.google.dev image generation

FAQ

Start on Lite or 2?

Learning the process: use 2—fewer fights with tier limits. You already know how to accept and only need many layouts: Lite explore, then upgrade to 2. See Lite guide.

Why do long prompts make images messier?

Long prompts collide. Keep the four-pack: use, subject, aspect, bans; add one style layer at a time. System writing: Prompt playbook.

On-image text keeps failing—what then?

Short titles can be quoted and fixed in a dedicated round; legal microcopy, mixed scripts, and QR codes: generate blank, then type in design tools.

Can I use official Gemini from China directly?

Depends on your network and account conditions; policy can change. Learn on the site’s marked China-friendly entry first, then connect official when needed. Details: China access.

What does it cost? Is it free?

Follow each entry and official docs that day; this tutorial does not hard-code unit prices or quotas.

Official resources

• Gemini
• Gemini API image generation
• Google AI for Developers

Further reading

• Nano Banana guides hub
• What is Nano Banana?
• Nano Banana 2 complete guide
• Nano Banana 2 Lite
• Prompt playbook
• Styles & scenes

Summary

Beginner success is not “perfect poster on try one.” It is: acceptance card → round one validates composition only → one change per round → references declare control → delivery checklist. Smooth that loop before style libraries and APIs; tiers and prices always follow official docs for that day.