Skip to main content
Choose a model by the smallest capability set that completes the asset. YingTu uses one Gemini-native API across the family, so changing models normally means changing the path ID and validating model-specific size rules.

​
Decision table

Prices were checked on September 2, 2026. Consult the live pricing page before production use.

​
A practical selection path

  1. Keep gemini-2.5-flash-image when an existing stable integration works and migration has no clear benefit.
  2. For a new 1K-only workload, compare Lite with the original model using your real prompts; Lite is the current efficiency-focused option.
  3. Start most new multi-resolution integrations with gemini-3.1-flash-image.
  4. Test gemini-3-pro-image against Flash on the same high-value brief before accepting the premium.

​
What the live run can and cannot show

The same 1:1 ceramic-object brief completed across all four model IDs. The outputs confirmed size tiers, edit support, task completion, response fields, and MIME variation. They do not form a controlled visual-quality benchmark: the synchronous Flash and Pro requests used higher resolutions than the other models, and a single prompt cannot represent every production workload.
Do not use the observed PNG/JPEG split as a routing rule. File encoding can change; inlineData.mimeType remains authoritative.

​
Open the model guide

Original Nano Banana

Review migration and fixed-resolution tradeoffs.

Nano Banana 2 Lite

Build a current 1K-only integration.

Nano Banana 2

Use the general-purpose multi-resolution model.

Nano Banana Pro

Evaluate premium design and 4K work.