Firestore Usage Tracker

An interactive guide to understanding Firestore's billing metrics.

Reads

Simulate Operations:

Writes

Simulate Operations:

Deletes

Simulate Operations:

Read Operations

A read operation occurs whenever a document is retrieved from the server. Reads are often the largest contributor to Firestore costs.

get()

// Costs 1 read operation
db.collection('cities').doc('SF').get();

query.get()

// Costs 1 read for EACH document returned
db.collection('cities').where('capital', '==', true).get();

onSnapshot()

// Costs 1 read for initial listen
// Costs 1 read for each subsequent document change
const unsubscribe = db.collection('cities').doc('SF')
  .onSnapshot((doc) => {
    console.log("Current data: ", doc.data());
  });

When Reads are NOT counted

// A document read from cache (not modified) does NOT cost a read
// This happens automatically with onSnapshot listeners
// and when offline persistence is enabled.

Daily Usage Report

Summary of simulated daily operations and estimated cost.

Reads

Writes

Deletes

Estimated Cost

$0.000000

AI Anomaly Detection

Analyze current usage against 30-day averages to find anomalies.