Remote Config

Starting September 1, 2026, Remote Config offers a usage-based pricing structure based on daily fetch request volume. Every project includes a no-cost tier of up to 100,000 daily fetch requests, with pay-as-you-go pricing on the Blaze plan for usage exceeding this threshold. All features (including Personalization, Rollouts, and A/B Testing integration) remain included across both Spark and Blaze plans at no additional cost. To learn more about pricing plans, grace periods, and usage monitoring, see Pricing for Remote Config.

A/B Testing

A/B Testing is now integrated directly into Remote Config as a native feature, bringing experiments into the core Remote Config template lifecycle. To learn more, see Create Firebase Remote Config experiments with A/B Testing and the A/B Testing troubleshooting and FAQ guide.

Firebase AI Logic

Firebase AI Logic now supports the us and eu locations. When you use the Agent Platform Gemini API (formerly Vertex AI) (and depending on the model), you can choose where to access the model to meet your compliance, latency, availability, and durability requirements.

Note that Firebase AI Logic defaults to the following locations:

• When using the new "Agent Platform" initialization syntax: global
• When using the legacy "Vertex AI" initialization syntax: us-central1

Learn more about specifying the location for accessing the model.

Imagen models

All Imagen models shut down on August 17, 2026 (note that this shutdown date was extended from the previous June 30, 2026).

To accommodate this shutdown, we've removed all Imagen APIs from the Firebase AI Logic SDKs and documentation.

This shutdown date is applicable to both the Gemini Developer API (Google AI) and the Agent Platform Gemini API (formerly Vertex AI). As a replacement, you can migrate your apps to use a Gemini Image model (like one of the "Nano Banana" models).

If you use Imagen models via Firebase AI Logic, you can migrate your apps to use a Gemini Image model to restore service. Models that are shut down are no longer accessible or supported by Google, and a request using a shutdown model name returns a 404 error.

SDK Releases

The Firebase Apple SDK (v12.18.0) is now available. For more details, see the Firebase Apple SDK release notes. To install this SDK, see Add Firebase to your app.

The Firebase Android SDKs for Firebase AI Logic, App Check, Cloud Firestore, Cloud Messaging, and SQL Connect have been updated. The Crashlytics Gradle plugin has also been updated. For more details, check out the latest Android Release Notes. To get started with Firebase in Android, see Add Firebase to your Android Project.

The Firebase Android BoM has been updated to v34.17.0. Learn how to add SDKs to your app using the Firebase BoM.

The Firebase Admin Node.js SDK (v14.3.0) is now available. This release includes new features in Firebase SQL Connect and dependency updates in Cloud Firestore and Cloud Storage. To install this SDK, see Add the Firebase Admin SDK to your server.

The Firebase JavaScript SDK (v12.18.0) is now available. For more details, see the Firebase JavaScript SDK release notes. To install the SDK, see Add Firebase to your JavaScript Project.

Firebase AI Logic

Firebase AI Logic supports the latest Gemini stable model gemini-3.7-flash. You can directly access this model in your mobile or web app via either the Gemini Developer API or the Agent Platform Gemini API (formerly Vertex AI).

• If you're using the Gemini Developer API, accessing this model does not require the pay-as-you-go Blaze pricing plan.
• If you're using the Agent Platform Gemini API (formerly Vertex AI) with the legacy "Vertex AI" initialization syntax, make sure to set the location in your request to global.
• If you're migrating from previous models, note the following for this new model:
  • No support for MINIMAL thinking level: gemini-3.7-flash does not support the MINIMAL thinking level. If you set the thinking level to MINIMAL for this model, the request will fail with a 400 error.
  • Sampling parameter deprecation: The latest Gemini 3.x models ignore the temperature, topP, topK parameters for model configuration. For more deterministic responses, define system instructions with explicit rules for your specific use case.
  • Prefilled model turn validation: Prefilling model turns is no longer supported. If the last non-empty turn in the request is a model turn, the API returns a 400 error.