Gemini RETIRED TRIVIAL

imagen-4.0-generate-preview-06-06 — Retired

Deprecated
Shutdown
2026-02-17
Status
retired
Replacement
imagen-4.0-generate-001

Quick fix — copy & paste

Choose your language. The "before" block matches the deprecated call; the "after" block is the drop-in replacement.

Breaks on 2026-02-17
# Gemini: imagen-4.0-generate-preview-06-06 (retired)
model = "imagen-4.0-generate-preview-06-06"
Use this instead
# Replacement
model = "imagen-4.0-generate-001"

This migration was generated automatically from the model rename. If your code does more than swap a model id, double-check request/response shapes against the official Gemini migration guide.

Error messages

Seeing one of these? You're in the right place.

  • model_not_found: imagen-4.0-generate-preview-06-06
  • The model `imagen-4.0-generate-preview-06-06` has been deprecated
  • The model `imagen-4.0-generate-preview-06-06` does not exist or you do not have access to it

Replacement options

Other Gemini deprecations

What this means for your code

imagen-4.0-generate-preview-06-06 is an image-generation model called through the images endpoint. Image generation models often change their quality enums, default response format (URL vs base64), supported sizes, and per-image pricing between versions. Migration is rarely a clean string swap.

imagen-4.0-generate-preview-06-06 was retired by Gemini on 2026-02-17. API calls now return an error and the model is no longer accessible. New code should use imagen-4.0-generate-001; legacy code that still references this model id needs to be updated immediately.

Find every call in your codebase

Before you change anything, locate every place the deprecated model id is referenced. Search source files, environment files, feature flags, and config repos. Use these commands from your project root:

Python projects

grep -rn '"imagen-4.0-generate-preview-06-06"' --include="*.py" .

JavaScript / TypeScript projects

grep -rn '"imagen-4.0-generate-preview-06-06"' --include="*.{js,ts,tsx,jsx}" .

Anywhere (configs, scripts, infra)

grep -rn "imagen-4.0-generate-preview-06-06" .

Migration checklist

Steps in order. Skip any that don't apply, but read the whole list — for image gen models, the non-obvious steps are usually the ones that break in production.

  1. 1. Update the model id in image generation calls
  2. 2. Map the old quality enum (standard/hd) to the new model's enum (low/medium/high/auto)
  3. 3. Verify supported sizes — newer models may not support 256x256 or 512x512
  4. 4. Check response_format default — gpt-image-1 returns base64 by default while DALL-E returned URLs
  5. 5. Recompute per-image cost; some new models charge by tile count, not by image

Will this migration cost more?

Switching from imagen-4.0-generate-preview-06-06 to imagen-4.0-generate-001 could change your costs significantly. Calculate the exact difference for your prompts.

Open the cost calculator →