Calculator
Price your own ratio.
This calculator multiplies numbers you type. It does not know your contract, and it does not know how your files compress. Put in the gigabytes, the storage rate, the egress rate, and a ratio you are willing to assume. The table shows those two lines at 1× and at your ratio, per month and per year. Placeholders are examples. They are not Amazon's price.
Price a smaller file.
Enter your size and your rates. Then type a ratio you are willing to assume. The table compares 1× with that assumption. It is not a quote from us.
How does this storage cost calculator work?
Stored cost at 1× is your gigabytes times your storage rate. At your ratio, the gigabytes are divided by that ratio first. Egress works the same way on the monthly egress you typed. Yearly is monthly times twelve. Empty fields stay blank. A ratio below 1 is rejected. Nothing here is measured on your files.
The ratio is an assumption you own. 2 means you are asking what the lines would look like if the file were half the size. 1 means no change, which is a useful sanity check. We deliberately do not prefill 10.7. That figure is the enwik9 text benchmark, original divided by the compressed file, as of Oct 14, 2026. It is not a default for a bucket, a backup, or a log archive. If you type it anyway, you are choosing it. The label on the field says so.
Both rates should be in the same currency. The dollar sign on the label is a prompt to look at your bill, not a switch that converts currencies. The output is a number with two decimals in that currency. If your bill is in euros, type euros. The math does not care. It also does not add tax, discounts, or free tiers. If the first 100 GB of transfer are free on your plan, subtract them before you type the egress volume, or accept that the table overstates that line.
What costs does the calculator leave out?
Retrieval, API requests, replication as a separate copy, minimum storage duration, and per-object monitoring fees. Those can dominate a bill of small or cold objects. The table is only storage rate times size, and egress rate times egress, at 1× and at your ratio. Use it for those two lines, then read the provider page for the rest.
A Glacier-class restore is not modeled. Neither is a lifecycle transition request, nor Intelligent-Tiering's monitoring charge, nor a NAT gateway's processing fee. The S3, Cloud Storage, and Azure Blob pricing pages list those. If your pain is requests rather than gigabytes, this calculator will look quiet and your bill will not. Go to the S3 page on this site and count objects before you trust a capacity-only estimate.
Replication is only included if you fold the second copy into the size you type, and the transfer into the egress you type. The calculator will not double anything for you. That is on purpose. Hidden multipliers are how these tools lie. If you have two regions, add the second region's gigabytes yourself and use that region's rate.
What should I do with the yearly difference?
Treat it as a reason to measure, not as a saving you have earned. If the difference is small at a ratio you believe, stop. If it is large, take a sample of the files and see whether that ratio is available. Send us the sample if you want it measured. We will not turn this table into a quote.
A large number at an optimistic ratio is a fantasy with a decimal point. Drop the ratio until it is one you have seen on a sample of this data, from gzip, from zstd, or from a test we run. Then look again. The project is worth doing only at a ratio you can reproduce and restore. Include the decompressor in your own total if you will store it beside the data. The homepage benchmark does that for enwik9. You should do it for your file.
Bring the printout to the same review as the provider pricing page, with the date. When the page changes, your typed rate is stale and so is the yearly figure. The calculator does not watch AWS for you. None of the spokes on this site do either. They tell you which line to look at. You type what it costs.
Questions.
Why isn't 10.7× the default?
Because that number is enwik9, a text benchmark, as of Oct 14, 2026. It is not your data. A default would look like a promise. Type a ratio you assume, or leave the field blank until you have a sample. The table stays empty rather than invent a saving.
Where do I get the storage rate?
From your invoice, or from the provider's current pricing page for your class and region. Amazon S3, Google Cloud Storage, and Azure Blob Storage all publish those pages. Write down the date. Do not use the placeholders in this form. They are examples so the boxes are not mysterious.
Can this estimate Datadog or Splunk?
Only the archive portion, and only if that portion is priced per gigabyte stored or sent. Event and ingest prices belong on the vendor's rate card, not in this table. The log page explains the difference. Do not force an event price into a per-gigabyte box.
Provider docs, not our price list.
Links checked Oct 21, 2026. Rates and rules on those pages can change.
Keep reading.
Send us a sample.
We will measure it on your files. We will not quote a savings number we have not measured. Write hello@qzip.ai or join the waitlist.