Gemini API: `gemini-embedding-2-preview` Deprecated, Requests Route to `gemini-embedding-2`

Gemini CLINov 6, 2026View original changelog

Google deprecated the gemini-embedding-2-preview model in the Gemini API. From November 6, 2026, requests to the preview ID are automatically routed to gemini-embedding-2 and billed at Gemini Embedding 2 rates. The API schema, pricing and embedding space are unchanged, so developers only need to update the model string, with no re-embedding of stored vectors required.

Key Takeaways

Requests to gemini-embedding-2-preview are routed automatically to gemini-embedding-2 starting November 6, 2026.
Billing moves to Gemini Embedding 2 rates for traffic that still uses the preview ID.
Google states the embedding space is unchanged, so the migration does not call for re-embedding stored vectors.
The only code change is the model string: swap gemini-embedding-2-preview for gemini-embedding-2.
API schema and pricing are unchanged, per Google's notice.
The notice gives no date on which the deprecated identifier stops working, only the routing and billing change from November 6.

What Changed

Google deprecated the gemini-embedding-2-preview model in the Gemini API. Starting November 6, 2026, any request sent to the preview model ID is routed to gemini-embedding-2 and charged at Gemini Embedding 2 rates. The change retires the preview name in favor of the stable one.

What Developers Need to Do

Applications that still call gemini-embedding-2-preview should switch the model string to gemini-embedding-2.

Google states that the API schema, pricing and embedding space are all unchanged. Because the embedding space is unchanged, the migration does not call for re-embedding stored vectors.

Quick Migration Checklist

Search code and configuration for gemini-embedding-2-preview.
Replace it with gemini-embedding-2.
No changes to request or response schemas, and no re-embedding of stored vectors.

Scope of the Notice

Google's notice states the routing behavior and the billing change from November 6, 2026. It does not give a date on which the deprecated identifier stops working.