[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["難以理解","hardToUnderstand","thumb-down"],["資訊或程式碼範例有誤","incorrectInformationOrSampleCode","thumb-down"],["缺少我需要的資訊/範例","missingTheInformationSamplesINeed","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間：2025-09-04 (世界標準時間)。"],[],[],null,["# Understanding your billing report\n=================================\n\nThis page gives tips and resources to help you understand your Firestore billing\nreport. This page covers the following common sources of billing questions:\n\n- Outside of app usage, sources of costs include import operations, export operations, and console usage.\n- Within your app, real-time updates, no-op writes, and query offsets can make your usage rise faster than expected.\n- As you use the usage dashboard in the console, note the discrepancies between the dashboard and the billing report.\n\nImport and Export Usage\n-----------------------\n\nWhen breaking down your billing report, make sure to review costs related to\n[import and export operations](/firestore/docs/manage-data/export-import).\nThese operations perform read and write operations\nwhich count towards your Firestore billing. Depending on how often you import\nand export data, these operations can make up a significant source of billed\noperations.\n\nNote that the usage dashboard in the console does not reflect reads and writes\nfrom import and export operations. You can view import/export operations and\nrelated costs in the following ways:\n\n### Billing Labels\n\nExport and import operations apply the `goog-firestoremanaged:exportimport`\nlabel to their read and write operations. In the Cloud Billing reports page,\nyou can use this label to view costs related to import and export operations:\n\n### List recent operations\n\nYou can view recent import and export operations using the console or `gcloud`. \n\n### Console\n\nYou can view a list of recent export and import operations in the\n**Firestore Import/Export** page of the Google Cloud console.\n\n[Go to the Import/Export page](https://console.cloud.google.com/firestore/import-export)\n\n### gcloud\n\nUse the [`operations list`](/sdk/gcloud/reference/firestore/operations/list) command to see all running and\nrecently completed export and import operations: \n\n```\ngcloud firestore operations list\n```\n\n### Audit Logs for admin operations\n\nFirestore writes audit logs for export operations, import operations, and\nindexing operations, see [Firestore audit logging information](/firestore/docs/audit-logging).\n\nConsole usage\n-------------\n\nRead operations performed by the Firestore data viewer in the Firebase Console\nand Cloud console count towards your billed Firestore usage. When you open or\nrefresh the Firestore page, the console loads documents to populate the page. As\nlong as the Firestore page remains open, the console uses real-time queries to\nupdate visible documents and collections.\n\nAs you breakdown your usage, factor in console usage as another source of\nFirestore operations. In your billing report, there is no way to distinguish\nconsole traffic from application traffic.\n\nBilled operations\n-----------------\n\nIn addition to the [pricing information](/firestore/pricing), review your app for the following\noperations which can lead to billing rising faster than expected:\n\n- **Real-time updates**\n\n When you\n [listen to the results of a query](/firestore/docs/query-data/listen), you\n are charged for a read each time a document in the result set is added or\n updated. You are also charged for a read when a document is removed from the\n result set because the document has changed. (In contrast, when a document\n is deleted, you are not charged for a read.)\n\n Review the scope of your real-time listeners. Listening to the results of a\n very broad query or listening to an entire collection might result in more\n read operations than required.\n- **No-op writes and no-op deletes**\n\n A no-op is an operation that does not result in changes to any documents. You\n still incur charges for no-op writes and deletes.\n\n For a delete operation, you incur charges even if the given document doesn't\n exist.\n\n For a write operation, you still incur charges if the operations result in no\n changes. For example, an operation that updates a document field to the same\n field value incurs charges.\n- **Query offsets**\n\n [Query offsets](https://googleapis.dev/nodejs/firestore/latest/Query.html#offset) skip a specified number of query results but skipped\n results still count towards billing. Because of this additional cost, you\n should use [cursors](/firestore/docs/query-data/query-cursors) instead of\n offsets.\n\nUsage dashboard discrepancies\n-----------------------------\n\nThe Firestore usage dashboards in the Firebase and Cloud consoles\nprovide an estimate of usage. They can help you identify spikes in usage.\nHowever, the dashboard is not an exact view of billed operations. Billed usage\nis likely higher. In all cases of discrepancy, the billing report takes\nprecedence over the usage dashboard.\n\nOperations that cause discrepancies between the usage dashboard and billed\nusage include:\n\n- Import and export operations. Reads and writes performed by these operations do not show up in the usage dashboard.\n- No-op verify-only writes. Writes that only verify the existence or non-existence of a document contribute to billed read operations, but they show as \\`UPDATE_NOOP\\` and \\`DELETE_NOOP\\` respectively in the write usage dashboard.\n- No-op writes. Operations that do not result in a change to the database, such as an update that does not change field values or a write to a deleted document may show in the usage dashboard as \\`UPDATE_NOOP\\` or \\`DELETE_NOOP\\`. Even though they show as \\`NOOP\\`, they still contribute to billed operations.\n-\n Collapsed writes. In cases with multiple writes to the same document in quick\n succession, the usage dashboard might collapse multiple writes together and\n count them as one. When billing usage, each write is still counted separately.\n\n\n The usage dashboard also collapses writes for field transforms like server timestamps, numeric increments, and array union operations. For field transforms, the usage dashboard might count multiple operations as a single operation.\n- Queries that return zero results. Queries with zero results incur a cost of one read operation. This usage is billed but does not appear in the usage dashboard.\n- Read operations from [index entries read](/firestore/pricing#index-reads). This usage is billed but does not appear in the usage dashboard. For example, aggregation queries bill for index entries read but this usage does not appear in the usage dashboard.\n\nWhat's next\n-----------\n\nFor more help with your billing report, contact [Cloud Billing Support](/support/billing)."]]
