Starting September 1st 2026, Remote Config will offer a flexible pricing
structure designed to accommodate projects of all sizes, featuring both a
no-cost plan and a scalable pay-as-you-go tier based on your daily usage.
The following table shows the usage per project for both
Spark and
Blaze plans:
| Details
|
No-cost (Spark Plan)
|
Pay as you go (Blaze Plan)
|
| Fetch Requests
|
Up to 100,000 per day
|
No-cost up to 100,000 per day.
Then:
- $0.000006 per request ($0.06 / 10K requests) for usage between 100,001 and 10,000,000 per day.
- $0.000001 per request ($0.01 / 10K requests) for usage over 10,000,000 per day.
|
| All Features
|
Includes Personalization, Rollouts, A/B Testing integration
|
Includes Personalization, Rollouts, A/B Testing integration
|
| Quotas and Limits
|
See Quotas and limits
|
See Quotas and limits
|
Grace periods and transition
If your project exceeds the Spark plan limits for the first time, you have a
30-day grace period to upgrade to the Blaze
plan
before service throttling begins. We recommend upgrading immediately to ensure
uninterrupted service. Moving to the Blaze pricing plan links your project to a
Google Cloud Billing
account.
Best practices to optimize usage
To optimize usage, do any of the following:
- Client fetch intervals: Avoid setting very low minimum fetch
intervals (for example,
setMinimumFetchIntervalInSeconds) in production
builds. The default recommended interval is 12 hours.
- App startup fetch loops: Ensure your app does not trigger a remote fetch on
every screen transition, activity resume, or component render. Use loading
strategies like Fetch and activate on
load or Activate behind loading
screen responsibly.
- Monitoring: Use Google Cloud console and Firebase console pricing and
usage dashboards to set up automated billing alerts when daily fetch volumes
approach 100,000 requests.
FAQ and troubleshooting
What is the new Remote Config pricing structure taking effect on
September 1, 2026?
Remote Config is moving to a usage-based
pricing structure with a no-cost tier:
- Spark (No-cost) Plan: Up to 100,000 fetch requests per day at no
cost.
- Blaze (Pay-as-you-go) Plan: No-cost for the first 100,000 daily fetch
requests, then:
- $0.06 per 10,000 requests ($0.000006/req) between 100,001 and
10,000,000 requests per day.
- $0.01 per 10,000 requests ($0.000001/req) for usage over 10,000,000
requests per day.
- Features: All advanced features (Personalization, Rollouts, and A/B
Testing integration) remain included across both Spark and Blaze plans
at no additional cost.
Do I need a billing account to get started with Remote Config?
No. You don't need a billing account to get started with
Remote Config. You can use the Spark plan to get started at no cost. A billing account is only required when you upgrade your project to
the Blaze plan to support more than 100,000 daily fetch requests.
What exactly qualifies as a billable fetch request?
A fetch request occurs whenever your client application or backend server
calls the Remote Config server to check for updated parameter values
(for example, invoking fetch() or
fetchAndActivate() in the client SDKs, or retrieving
templates using REST/Admin SDKs).
- Realtime Remote Config: Opening a real-time connection does not
generate continuous individual fetch requests; however, when the server
pushes an invalidation notice, the resulting client call to download the
updated configuration counts as a fetch request.
- Cached values: Using cached values already stored on the device
(reading from disk/memory using
activate() or
getString()) does not generate a network call or count as a
fetch request.
What happens if my project is on the Spark plan and exceeds 100,000 daily
fetch requests? How do I upgrade?
- 30-Day Grace Period: When your Spark project exceeds 100,000 daily fetch
requests for the first time, Firebase grants a 30-day grace period. During
this time, your Remote Config requests will continue to be served
without interruption.
- Throttling Risk: If you don't upgrade to the Blaze plan by the end of
the 30-day grace period, Remote Config service throttling will begin
for requests exceeding the 100,000 daily limit, which may prevent clients
from receiving updated configs.
- How to upgrade: You can
upgrade to the Blaze plan
in the Firebase console to ensure uninterrupted service. Upgrading
to the Blaze plan links your project to a
Google Cloud Billing
account.
Users are not receiving new Remote Config parameter values. Could this
be related to pricing or quotas?
Yes. If your project is on the Spark plan, has exceeded the 100,000 daily
request limit, and the 30-day grace period has expired, incoming requests
over the daily threshold are throttled by the server. Check your usage
metrics in the Firebase console and upgrade to the Blaze plan if your
daily active users require more than 100,000 daily fetches.
How can I see my current usage to estimate my bill?
If you're on the Blaze plan, you can view cost management and usage
reports in the Google Cloud console. For details, see
View your Cloud Billing reports and cost trends.
When filtering by SKU, choose the following SKU:
- SKU ID:
37B1-4623-6F54
- SKU Name: Fetch Requests
If you're on the Spark plan, you can monitor your current usage and active
system limits on the Quotas & System Limits page in
the Google Cloud console. For details, see
View and manage quotas. When filtering reports, make
sure to select the specific Firebase API you want to check quotas for (for
example, firebaseremoteconfig.googleapis.com).
