Key details

  1. Imagen 4 standard, fast and ultra Gemini API endpoints were scheduled for shutdown on August 17, 2026.
  2. Google's current docs now direct users away from Imagen 4 to Gemini 3.1 Flash Image/Nano Banana models.
  3. Affected model IDs include imagen-4.0-generate-001, imagen-4.0-fast-generate-001 and imagen-4.0-ultra-generate-001.
  4. Google defines shutdown as the endpoint being completely turned off rather than merely unsupported.

What builders should take away

  1. Search code, configuration and stored workflow definitions for the three Imagen 4 model IDs and replace any remaining references.
  2. Run golden-prompt comparisons on the replacement Gemini image model before routing all production traffic.
  3. Recheck safety settings, output formats, latency and current pricing instead of assuming parity with Imagen 4.
  4. Pin replacement model IDs deliberately and monitor Google's deprecation page for future image-model lifecycle dates.

What changed

Google's documented August 17, 2026 shutdown date has passed for the Imagen 4 standard, fast and ultra endpoints in the Gemini API. The affected model IDs include imagen-4.0-generate-001, imagen-4.0-fast-generate-001 and imagen-4.0-ultra-generate-001. Google's current guidance points builders to Gemini 3.1 Flash Image and newer Nano Banana image-generation paths.

Why it matters

Production applications that pinned the old Imagen model IDs can now fail outright. Migration is not just a billing or naming change: builders need to verify request/response handling, image controls, safety behavior and output quality against the replacement model they select.

The deprecation has become a service cutoff

Google announced the deprecation in June and set August 17 as the shutdown date. Current model and deprecation documentation now describes Imagen 4 as shut down, so integrations that postponed migration have crossed from future risk into active availability risk.

The replacement is in the Gemini image family

Google's current documentation recommends Gemini 3.1 Flash Image/Nano Banana models for image generation. Builders should use the current stable model IDs from the Gemini documentation rather than copying older migration examples that may reference superseded preview IDs.

Migration requires behavioral testing

Even when the high-level use case remains text-to-image generation, replacement models can differ in API shape, supported controls, prompt handling, safety filtering, latency, image fidelity and price. A model-ID swap should therefore be validated with production prompts and acceptance criteria.

Timeline

2026-06-15

Google announces Imagen 4 deprecation

Google listed Imagen 4 and other image-generation models for shutdown on August 17.
2026-08-17

Imagen 4 endpoints shut down

The scheduled shutdown date passed and current Google documentation directs builders to newer Gemini image models.

What to watch next

  • Whether Google consolidates additional image models onto the same Gemini interaction pattern.
  • Any migration-specific regressions reported by production users.
  • Future deprecation dates for the recommended replacement endpoints.

Still unclear

  • Google's image-model guidance has changed during the migration period, so builders should verify the current replacement model ID immediately before deployment.
  • Application-level compatibility varies by which Imagen features and controls an integration used.

Sources

Direct reading behind this dossier.

3 sources
Imagen 4
Google AI for Developers primary

Current shutdown notice and migration recommendation.

Gemini deprecations
Google AI for Developers primary

Defines deprecation and shutdown behavior.