Proposed Pull Request Change

📄 Document Links

View on GitHub View on Microsoft Learn

--- title: Estimate the Cost of Using Azure Blob Storage description: Estimate Azure Blob Storage costs for storing, uploading, downloading, transferring, and renaming data. services: storage author: normesta ms.service: azure-blob-storage ms.topic: concept-article ms.date: 09/02/2026 ms.author: normesta ms.custom: - subject-cost-optimization - build-2025 # Customer intent: "As a cost manager, I want to estimate the costs of using cloud storage, so that I can optimize spending on data storage and transfer operations." --- # Estimate the cost of using Azure Blob Storage This article helps you estimate the cost to store, upload, download, and work with data in Azure Blob Storage. All calculations are based on a fictitious price. You can find each price in the [sample prices](#sample-prices) section at the end of this article. > [!IMPORTANT] > These prices are only examples. Don't use them to calculate your costs. For official prices, see the [Azure Blob Storage pricing](https://azure.microsoft.com/pricing/details/storage/blobs/) or [Azure Data Lake Storage pricing](https://azure.microsoft.com/pricing/details/storage/data-lake/) pages. For more information about how to choose the correct pricing page, see [Understand the full billing model for Azure Blob Storage](../common/storage-plan-manage-costs.md). ## The cost to store data Calculate your storage costs by multiplying the **size of your data** in GB by the **storage price of the chosen access tier**. For example, assuming [sample pricing](#sample-prices), if you plan to store 10 TB of blobs in the cool access tier, the capacity cost is $0.0115 * 10 * 1024 = **$117.76** per month. Depending on how much storage space you need, it might make sense to [reserve capacity](storage-blob-reserved-capacity.md) at a discount. You can reserve capacity in increments of 100 TiB and 1 PiB for a one-year or three-year commitment duration. Reserved capacity is available only for data stored in the hot, cool, and archive access tiers. The following table uses the [sample prices](#sample-prices) in this article to compare the pay-as-you-go and reserved capacity cost of storing 100 TB (102,400 GB) of data. | Calculation | Hot | Cool | Archive | |-----------------------------------------------------------|--------|--------|---------| | Monthly price for 100 TB of storage | $2,130 | $1,178 | $205 | | Monthly price for 100 TB of storage (one-year reserved) | $1,747 | $966 | $183 | | Monthly price for 100 TB of storage (three-year reserved) | $1,406 | $872 | $168 | To calculate the point at which reserved capacity begins to make sense, divide the cost of reserved capacity by the pay-as-you-go rate. For example, if the cost of one-year reserved capacity for cool tier storage is $966 and the pay-as-you-go rate is $0.0115, the calculation is $966 / $0.0115 = 84,000 GB (roughly **82 TB**). If you plan to store at least 82 TB of data in the cool tier for the entire reservation period, reserved capacity begins to make sense. The following table calculates the break-even point in TB for each access tier. | Calculation | Hot | Cool | Archive | |------------------------------------------------------|--------------------|---------|---------| | Monthly price per GB of Data storage (pay-as-you-go) | $0.0208 | $0.0115 | $0.002 | | Price for 100 TB of reserved storage | $1,747 | $966 | $183 | | Break-even for one-year reserved capacity | 82 TB¹ | 82 TB | 89 TB | | Break-even for three-year reserved capacity | 66 TB¹ | 74 TB | 82 TB | ¹The hot tier has multiple pay-as-you-go rates. The price of the first 50 TB and the price of the second 50 TB are factored into this calculation.<br /> To learn more about reserved capacity, see [Optimize costs for Blob Storage with reserved capacity](storage-blob-reserved-capacity.md). For general information about storage costs, see [Data storage and index meters](../common/storage-plan-manage-costs.md#data-storage-and-index-meters). ## The cost to transfer data When you transfer data, you pay for _write_ and _read_ operations. Some client applications use extra operations to transfer data, such as operations to list blobs or get properties. The [AzCopy](../common/storage-use-azcopy-v10.md) utility is optimized to transfer data efficiently and can serve as a canonical example on which to base your cost estimates. See [Estimate the cost of using AzCopy to transfer blobs](azcopy-cost-estimation.md). ### The cost to upload When you upload data, your client divides that data into blocks and uploads each block individually. Each uploaded block counts as a _write_ operation. You need a final write operation to assemble blocks into a blob stored in the account. The number of write operations required to upload a blob depends on the size of each block. The default block size for uploads to the Blob Service endpoint (`blob.core.windows.net`) is **8 MiB**, and you can configure it. The block size for uploads to the Data Lake Storage endpoint (`dfs.core.windows.net`) is **4 MiB**, and you can't configure it. Smaller blocks can increase upload parallelism, but they also require more write operations and can increase costs. The following table uses the [sample prices](#sample-prices) in this article and assumes an **8-MiB** block size to estimate the cost to upload **1,000** blobs that are each **5 GiB** in size to the hot tier. | Price factor | Value | |----------------------------------------------------------------------|-------------| | Number of MiB in 5 GiB | 5,120 | | Write operations per blob (5,120 MiB / 8-MiB block) | 640 | | Write operation to commit the blocks | 1 | | Total write operations (1,000 * 641) | 641,000 | | Price of a single write operation (price / 10,000) | $0.0000055 | | **Cost of write operations (641,000 * price of a single operation)** | **$3.5255** | For more detailed examples, see [Estimate the cost to upload](azcopy-cost-estimation.md#the-cost-to-upload). ### The cost to download The number of operations required to download a blob depends on which endpoint you use. If you download a blob from the Blob Service endpoint, you pay for a single _read_ operation. If you download a blob from the Data Lake Storage endpoint, you pay for multiple read operations because blobs download in 4-MiB blocks. If you download blobs from the cool or cold tier, you also pay a data retrieval fee per GiB downloaded from the cool, cold, or archive tier. The following table uses the [sample prices](#sample-prices) in this article to estimate the cost to download **1,000** blobs that are **5 GiB** each in size from the cool tier by using the Blob Service endpoint. | Price factor | Value | |------------------------------------------------------------------|-------------| | Price of a single read operation (price / 10,000) | $0.000001 | | **Cost of read operations (1,000 * operation price)** | **$0.001** | | Price of data retrieval (per GiB) | $0.01 | | **Cost of data retrieval 1,000 * (5 * price of data retrieval)** | **$50.00** | | **Total cost (read + retrieval)** | **$50.001** | Utilities such as AzCopy also use list operations and operations to get blob properties. These charges are relatively small compared to the overall bill. For examples, see [Estimate the cost to download](azcopy-cost-estimation.md#the-cost-to-download). ### The cost to copy between containers If you copy a blob to another container in the same account, you pay for a single _write_ operation based on the destination tier. If the destination container is in another account, you also pay for data retrieval and a _read_ operation based on the source tier. If the destination account is in another region, you pay for network egress. The following table uses the [sample prices](#sample-prices) in this article to estimate the cost to copy **1,000** blobs that are **5 GiB** each in size between two containers in the hot tier. | Price factor | Value | |-------------------------------------------------------------------|--------------| | Price of a single write operation (price / 10,000) | $0.0000055 | | **Cost to write (1,000 * price of a single operation)** | **$0.0055** | | Price of a single read operation (price / 10,000) | $0.00000044 | | **Cost of read operations (1,000 * price of a single operation)** | **$0.00044** | | **Total cost (cost to write + cost to read)** | **$0.0059** | For a complete example, see [Estimate the cost to copy between containers](azcopy-cost-estimation.md#the-cost-to-copy-between-containers). ## The cost to rename a blob The cost to rename blobs depends on the file structure of your account and the number of blobs that you're renaming. If the account has a flat namespace, there's no dedicated operation to rename a blob. Instead, your client tool copies the blob to a new blob and deletes the source blob. Delete operations are free. Therefore, when you rename a blob, you're billed for the cost of a single _write_ operation. If the account has a hierarchical namespace, there's a dedicated operation to rename a blob, and it's billed as an _iterative write_ operation. The cost of a write operation against the Blob Service endpoint is lower than the cost of an iterative write operation against the Data Lake Storage endpoint. Therefore, renaming blobs individually costs less in accounts that have a flat namespace. The following table uses the [sample prices](#sample-prices) in this article to calculate the cost to rename 1,000 blobs. | Price factor | Hot | Cool | Cold | |---------------------------------------------------------------------------------------------|-------------|------------|------------| | Price of a single write operation to the Blob Service endpoint (price / 10,000) | $0.0000055 | $0.00001 | $0.000018 | | **Cost to rename 1,000 blobs (1,000 * price of a single operation)** | **$0.0055** | **$0.01** | **$0.018** | | Price of a single iterative write operation to the Data Lake Storage endpoint (price / 100) | $0.000715 | $0.000715 | $0.000715 | | **Cost to rename Data Lake Storage directories (1,000 * price of a single operation)** | **$0.715** | **$0.715** | **$0.715** | Based on these calculations, the cost to rename 1,000 blobs in the hot tier differs by **70** cents. ## The cost to rename a directory If the account has a flat namespace, blobs are organized into _virtual directories_ that mimic a folder structure. A virtual directory forms part of the name of the blob and is indicated by the delimiter character. Because a virtual directory is a part of the blob name, it doesn't actually exist as an independent object. You can't rename a virtual directory without renaming all of the blobs that contain that virtual directory in the name. To effectively rename each blob, client applications have to copy a blob and delete the source blob. If the account has a hierarchical namespace, directories aren't virtual. They're concrete, independent objects that you can operate on directly. Therefore, renaming a directory is far more efficient because client applications can rename a directory in a single operation. The following table uses the [sample prices](#sample-prices) in this article to calculate the cost to rename 1,000 directories that each contain 1,000 blobs. | Price factor | Hot | Cool | Cold | |---------------------------------------------------------------------------------------------|------------|------------|------------| | Price of a single write operation to the Blob Service endpoint (price / 10,000) | $0.0000055 | $0.00001 | $0.000018 | | **Cost to rename blob virtual directories (1,000 * 1,000 * price of a single operation)** | **$5.50** | **$10.00** | **$18.00** | | Price of a single iterative write operation to the Data Lake Storage endpoint (price / 100) | $0.000715 | $0.000715 | $0.000715 | | **Cost to rename Data Lake Storage directories (1,000 * price of a single operation)** | **$0.715** | **$0.715** | **$0.715** | Based on these calculations, the cost to rename 1,000 directories in the hot tier that each contain 1,000 blobs differs by almost **$5.00**. For directories in the cold tier, the difference is over **$17**. ## Example: upload, download, and change access tiers This example shows four months of spending based on uploads, downloads, and the impact of moving objects between tiers. ### Upload, download, and access tier parameters At the beginning of each month, 1,000 files are uploaded to the hot access tier. Each file is 5 GB in size. During the month, client workloads read half of these files. After 30 days, a [lifecycle management policy](lifecycle-management-overview.md) moves the other half to the cool access tier to save on storage costs. In March, client applications read 10% of the data stored in the cool access tier. A lifecycle management policy moves those blobs back to the hot tier after clients read them. Twenty days into April, clients once again read 10% of the data stored in the cool access tier. However, those blobs are stored in the cool tier for less than 30 days. Because the lifecycle management policy moves those blobs back to the hot tier before the minimum 30 days elapses, you incur an early penalty. The early deletion penalty is the cost of cool storage for 10 days. ### Four-month Azure Blob Storage cost calculations The following table uses the [sample prices](#sample-prices) in this article to demonstrate four months of spending. > [!NOTE] > These calculations provide an approximate estimate given sample pricing. If you upload blobs in batches, prorate some storage costs because the blobs don't incur costs for the entire month. See [Data storage and index meters](../common/storage-plan-manage-costs.md#data-storage-and-index-meters). | Cost factor | January | February | March | April | |-------------------------------------------------------------------------|--------------|---------------|----------------|-----------------| | **Cost to write 1,000 blobs to the hot tier**¹ | **$3.53** | **$3.53** | **$3.53** | **$3.53** | | Number of blobs in the hot tier after monthly ingest | 1,000 | 2,000 | 2,100 | 2,155 | | Number of blobs to move to the cool tier | 0 | 1,000 | 1,050 | 1,078 | | **Cost to set blobs to the cool tier (billed as a write operation)** | **$0.00** | **$0.01** | **$0.0105** | **$0.010775** | | Number of blobs in the cool tier | 0 | 1,000 | 1,050 | 1,078 | | Total size of blobs in the cool tier (GB) | 0 | 5,000 | 5,250 | 5,388 | | Number of blobs read from the cool tier then moved back to the hot tier | 0 | 100 | 105 | 108 | | **Cost to read blobs from the cool tier** | **$0.00** | **$0.0001** | **$0.000105** | **$0.00010775** | | **Cost to move blobs back to the hot tier** | **$0.00** | **$0.0001** | **$0.000105** | **$0.00010775** | | Number of blobs that remain in the cool tier | 0 | 900 | 945 | 970 | | Total size of blobs that remain in the cool tier (GB) | 0 | 4,500 | 4,725 | 4,849 | | **Cost to store blobs in the cool tier** | **$0.00** | **$51.75** | **$54.34** | **$55.76** | | **Early deletion penalty** | **$0.00** | **$0.00** | **$0.00** | **$0.41** | | Number of blobs that remain in the hot tier | 1,000 | 1,100 | 1,155 | 1,185 | | Total size of blobs that remain in the hot tier (GB) | 5,000 | 5,500 | 5,775 | 5,926 | | **Cost to store blobs in the hot tier** | **$104.00** | **$114.40** | **$120.12** | **$123.27** | | Number of blobs read from the hot tier | 500 | 550 | 578 | 593 | | **Cost to read blobs from the hot tier** | **$0.00022** | **$0.000242** | **$0.0002541** | **$0.00026076** | | **Monthly total** | **$107.53** | **$169.69** | **$178.00** | **$182.98** | ¹The number of operations required to complete each monthly upload is **641,000**. The formula is 1,000 blobs * (5 GiB / 8-MiB blocks + 1 write operation to assemble each blob).<br /> ## Sample prices [!INCLUDE [Sample prices for Azure Blob Storage and Azure Data Lake Storage](../../../includes/azure-blob-storage-sample-prices.md)] ## See also - [Plan and manage costs for Azure Blob Storage](../common/storage-plan-manage-costs.md) - [Map each REST operation to a price](map-rest-apis-transaction-categories.md) - [Get started with AzCopy](../common/storage-use-azcopy-v10.md)