Google Extends Gemini 2.5 Flash Image Retirement to March 2027
Google's newer lifecycle table replaces the former October cutoff with a March 2027 date, giving Gemini Enterprise Agent Platform users more migration time while its model page remains outdated.
Edited by Tyronne Panaino
Google has moved the documented retirement date for `gemini-2.5-flash-image` on Gemini Enterprise Agent Platform to March 15, 2027. The current lifecycle table, updated October 1, names `gemini-3.1-flash-lite-image` as the replacement, while the model's older details page still shows October 2, 2026 as the cutoff.
The change matters immediately to developers who were preparing for the October 2 deadline. The newer table gives production image workflows more migration time, but the disagreement between two official Google pages also means teams should use the lifecycle record rather than assume every product-specific page reflects the latest schedule.
The newer lifecycle table changes the deadline
Google's model-details page was last updated September 3. It identifies `gemini-2.5-flash-image` as a generally available model released on October 2, 2025 and assigns it an October 2, 2026 retirement date. That page describes an image model supporting generation, editing, multi-turn editing, interleaved text and images, and C2PA Content Credentials.
The lifecycle page is newer: Google marks it as updated October 1. Its image-model table keeps the same model and release date but lists March 15, 2027 as retirement and names `gemini-3.1-flash-lite-image` as the replacement. Google also states on that page that retirement dates can be extended but will not be brought forward. Read together, the two documents show a later official schedule superseding the date that remains visible on the model page.
More time does not make migration automatic
An extension reduces immediate cutoff pressure, but it does not establish drop-in compatibility. The replacement is a different model identifier, and Google's lifecycle guidance tells teams to update the application, test mission-critical features and deploy the change through their normal process.
For image systems, that testing should cover the behavior the application actually depends on. The retiring model's page documents generation, editing, multiple output images, regional availability and several input formats. A migration plan therefore needs to check request formats, output handling, safety controls, latency, visual consistency and any workflow that expects a particular model identifier. Those are practical test areas, not claims that Google has reported a failure in any one of them.
The documentation mismatch is itself operationally relevant
Teams often discover lifecycle dates through a model-specific reference page. In this case, that path still points to the former deadline, while the central lifecycle table carries the later date. Build scripts, internal runbooks or support material copied from the September page could therefore preserve an obsolete cutoff even though Google has extended the platform schedule.
The safest current reading is narrow: Google now lists March 15, 2027 as the retirement date and recommends `gemini-3.1-flash-lite-image`. The fetched documents do not prove that every account or endpoint has already adopted identical lifecycle messaging, and AI News Bank did not test account-level availability. Developers should verify the model IDs and migration behavior in the regions and projects they operate.
What to watch next
The next useful checkpoint is consistency across Google's documentation and service surfaces. The model-details page should eventually match the central lifecycle table, and Google could still extend the date again under its stated policy. Teams should also watch for migration guidance that compares feature coverage between the two image models rather than assuming the replacement behaves identically.
Status
Confirmed. Two official Google documents establish the former and current dates, with the newer lifecycle page naming the replacement. Internal confidence is medium because both sources come from the platform vendor and no independent endpoint or migration test was performed.
Sources
Update note: Last reviewed 2026-10-02. We will revise this post if Google changes the lifecycle table, aligns the model page, or publishes additional migration guidance.
Sources
Drafted with AI assistance from source briefs; reviewed for citation completeness and label accuracy.