AWS S3 Pricing in 2026: What You’ll Actually Pay
AWS S3 pricing looks simple at first.
You store data. You pay per GB. Easy enough.
But once your app starts moving files around, the bill can include more than storage. Amazon S3 pricing can also include requests, retrievals, data transfer, replication, management tools, and other usage-based charges.
This guide keeps things simple. We’ll walk through what S3 charges for, how the main storage classes compare, what usually surprises teams, and when an S3-compatible alternative like Filebase may be worth comparing.
Pricing note: The examples below use US East / N. Virginia where possible. AWS pricing varies by Region and workload, so check the AWS Pricing Calculator before making a final decision. AWS also notes that S3 charges can include storage, requests, retrievals, data transfer, management, replication, and query-related features.
How AWS S3 pricing works
AWS S3 pricing is based on four main things:
| Cost | What it means | Why it matters |
|---|---|---|
| Storage | How much data you store each month | This is the base cost most teams check first |
| Requests | Actions like GET, PUT, COPY, POST, LIST, and SELECT | High-traffic apps can create lots of small charges |
| Retrievals | Reading data from infrequent-access or archive tiers | Cheaper storage can cost more if you access it often |
| Data transfer | Moving data out of S3 | This is often where bills get surprising |
There are other costs too, like replication, S3 Inventory, Storage Lens, Batch Operations, Object Lambda, and S3 Select. But for most teams, the first question is simpler:
How much data are you storing, and how much of it leaves S3 each month?
That question usually tells you whether storage, requests, or egress will drive your bill.
How much does AWS S3 cost per GB?
In US East / N. Virginia, S3 Standard storage starts at $0.023 per GB-month for the first 50 TB. That means 1 TB in S3 Standard costs about $23.55/month for storage only.
1 TB = 1,024 GB
1,024 GB × $0.023 = $23.55/month
That is useful math, but it is not the full AWS S3 pricing story. Downloads, API requests, replication, retrieval fees, and management features can all increase the final cost.
Amazon S3 storage class pricing
Amazon S3 has several storage classes. Each one is designed for a different access pattern.
Here’s the simple version:
| Storage class | Approx. us-east-1 storage price | Best for | Watch out for |
|---|---|---|---|
| S3 Standard | $0.023/GB-month | Frequently accessed data | Egress and request costs |
| S3 Standard-IA | $0.0125/GB-month | Infrequent access with fast retrieval | Retrieval fees, 30-day minimum |
| S3 One Zone-IA | $0.01/GB-month | Re-creatable infrequent data | Single Availability Zone |
| S3 Intelligent-Tiering | Tier-dependent | Unknown access patterns | Monitoring fee for eligible objects |
| S3 Glacier Instant Retrieval | $0.004/GB-month | Rare access, fast retrieval | Retrieval fees, 90-day minimum |
| S3 Glacier Flexible Retrieval | $0.0036/GB-month | Archives that can wait | Restore step required |
| S3 Glacier Deep Archive | $0.00099/GB-month | Long-term cold archive | Slow restores, 180-day minimum |
The warm rule of thumb:
| If your data is... | Start with... |
|---|---|
| Active and frequently accessed | S3 Standard |
| Rarely accessed but still needed quickly | Standard-IA or One Zone-IA |
| Long-term archive data | One of the S3 Glacier classes |
The storage class matters, but the access pattern matters more. A cheaper class is only cheaper when your data behaves the way that class expects.
Amazon S3 standard storage pricing per GB-month
For many teams, S3 Standard is the first storage class to understand.
It is the default fit for active files, user uploads, application assets, and data your app reads often. In US East / N. Virginia, Amazon S3 standard storage pricing per GB-month starts at $0.023 per GB for the first 50 TB.
That makes it easy to estimate the storage-only part of an AWS S3 bucket:
| Data stored in S3 Standard | Storage-only estimate |
|---|---|
| 500 GB | $11.50/month |
| 1 TB | $23.55/month |
Just remember: this table does not include requests, retrievals, data transfer, replication, or other AWS S3 storage charges.
AWS S3 request pricing
S3 requests are the actions your app performs against buckets and objects.
| Request type | Common example |
|---|---|
| GET | A user views or downloads a file |
| PUT | Your app uploads a file |
| LIST | Your app lists objects in a bucket |
| COPY | Your app copies an object |
| Lifecycle transition | S3 moves an object to another storage class |
For small apps, request charges are often minor. For busy apps, they can add up.
This matters for products with lots of small objects, previews, thumbnails, logs, build artifacts, or AI pipelines that read and write files constantly.
Amazon S3 data transfer pricing
Amazon S3 data transfer pricing is one of the most commonly missed parts of the bill.
Uploading data into S3 is usually free. Moving data out of S3 is where many teams start to feel the cost. AWS includes the first 100 GB/month of data transfer out to the internet, aggregated across AWS services and Regions except China and GovCloud. After that, standard transfer pricing applies.
Here’s a simple example:
1 TB stored in S3 Standard:
1,024 GB × $0.023 = $23.55/month
1 TB downloaded to the internet:
1,024 GB - 100 GB free = 924 GB billable
If transfer is $0.09/GB:
924 GB × $0.09 = $83.16/month
Estimated total before requests:
$23.55 + $83.16 = $106.71/month
That’s the moment AWS S3 pricing starts to feel different. In this example, transfer costs more than 3x the storage.
Commonly missed Amazon S3 pricing costs
Most S3 bill surprises come from the same few places.
| Cost | Why it surprises teams |
|---|---|
| Data transfer out | Downloads, public assets, restores, and file delivery can cost more than storage |
| Versioning | Old object versions still use storage |
| Small objects | Some storage classes have minimum billable object sizes |
| Retrieval fees | IA and Glacier classes are cheaper until you access them too often |
| Replication | Cross-Region copies can add storage, request, and transfer costs |
This does not mean S3 is bad. It means S3 is flexible, and flexible systems usually have more pricing variables.
The trick is not to memorize every fee. The trick is to know which fees apply to your workload.
How to estimate your AWS S3 bill
Use this formula:
Monthly S3 cost =
storage
+ requests
+ retrievals
+ data transfer
+ replication
+ management features
Then answer these questions:
| Question | Why it matters |
|---|---|
| How much data will you store? | Sets your base storage cost |
| How often will users download it? | Shows whether egress will matter |
| How many files will your app read and write? | Helps estimate request volume |
| Are files hot, warm, or cold? | Helps choose the right storage class |
| Are you replicating data? | Adds storage and transfer considerations |
For planning, manual math is helpful. For production, use the AWS Pricing Calculator.
AWS S3 pricing examples
| Scenario | Storage-only estimate | What to notice |
|---|---|---|
| 500 GB in S3 Standard | $11.50/month | Small apps may stay close to storage cost if downloads are low |
| 1 TB in S3 Standard | $23.55/month | Good baseline for active AWS S3 storage |
Now add downloads and the picture changes.
| Scenario | Estimated AWS S3 cost before requests |
|---|---|
| 1 TB stored, no downloads | $23.55/month |
| 1 TB stored, 1 TB downloaded to internet | About $106.71/month |
This is why “how much does S3 cost?” is not quite enough. The better question is:
How much data are you storing, and how much are people moving?
When AWS S3 is a good fit
AWS S3 is a strong choice when your application is already deeply built on AWS.
It is especially useful if you need AWS-native services like IAM, Lambda, CloudFront, Athena, Glue, Redshift, EMR, lifecycle policies, replication workflows, or Glacier archive tiers.
S3 can be the right default when your team wants:
| Need | Why S3 fits |
|---|---|
| Deep AWS integration | S3 connects across the AWS ecosystem |
| Many storage classes | You can tune storage by access pattern |
| Archive storage | Glacier tiers are strong for long-term retention |
| Mature controls | IAM, policies, logging, and lifecycle tools are broad |
For AWS-native teams, staying with S3 may be the simplest path.
When to consider an S3-compatible alternative
An S3-compatible alternative may make sense when you mostly need object storage, but not the full AWS ecosystem.
This tends to happen when your workload is file-heavy. Think user uploads, media libraries, AI file pipelines, backups, customer downloads, datasets, app assets, or developer artifacts.
That is where pricing clarity starts to matter. Not because AWS S3 pricing is wrong, but because storage, egress, and request meters can make future costs harder to predict. If your app still relies on S3-compatible tools, the right AWS S3 alternative should feel familiar without recreating the same billing complexity.
AWS S3 vs Filebase
Filebase is an S3-compatible object storage platform for teams that want simpler pricing, free object egress, and object storage that works with existing S3-compatible tools.
Filebase is not trying to replace every S3 use case. If your app depends heavily on AWS-native services or Glacier Deep Archive, S3 may still be the better fit.
But if your workload is file-heavy and egress-sensitive, Filebase is worth comparing. Filebase’s object storage page lists pricing that starts at $7.50 for 500 GB, then scales at $15/TB, with free object egress.
| Scenario | AWS S3 estimated cost | Filebase estimated cost | Better fit |
|---|---|---|---|
| 1 TB stored, no downloads | About $23.55 before requests | About $15 | Depends on AWS integration needs |
| 1 TB stored, 1 TB downloaded | About $106.71 before requests | About $15 | File-heavy workloads may favor Filebase |
| Deep cold archive | Glacier may be much cheaper | Not Filebase’s lane | AWS |
The fair way to think about it:
AWS S3 is a broad storage platform. Filebase is a focused S3-compatible object storage option for teams that care about predictable pricing and frequent file movement.
Bottom line
AWS S3 pricing is not just storage pricing.
For a realistic estimate, look at storage, requests, retrievals, data transfer, replication, and management features. If your workload stays mostly inside AWS and needs deep AWS integrations, S3 is often a strong default.
If your app moves a lot of files, serves frequent downloads, or needs more predictable object storage pricing, an S3-compatible alternative like Filebase may be worth a closer look.
Start with three numbers:
- how much data you store,
- how much data leaves storage each month,
- how often your app reads and writes objects.
Those three numbers will tell you more than any headline price.
Frequently asked questions
What is Amazon S3 used for?
Amazon S3 is used to store and retrieve object data, including application files, backups, media assets, datasets, logs, archives, and static website files. In AWS, S3 is commonly used when teams need scalable object storage connected to the broader AWS ecosystem.
How much does 1 TB cost on AWS S3?
In US East / N. Virginia, 1 TB in S3 Standard costs about $23.55/month for storage only. This does not include requests, retrievals, data transfer, replication, or management features.
Is AWS S3 free or paid?
AWS S3 is a paid service, but AWS offers free tier allowances for eligible new customers. Once your usage exceeds those allowances, Amazon S3 pricing applies based on storage, requests, data transfer, retrievals, and other usage.
Why is my S3 bill higher than expected?
Your S3 bill may be higher than expected because Amazon S3 pricing includes more than storage. Data transfer out, request volume, retrieval fees, versioning, replication, and management tools can all add cost.
Does AWS S3 charge for downloads?
Yes. AWS can charge for data transferred out of S3 to the internet after the monthly free allowance. Transfer costs depend on destination, Region, and usage.
Is S3 cheap storage?
S3 can be cheap storage for some workloads, especially when data stays inside AWS or is stored in the right archive class. But for file-heavy apps with frequent downloads, data transfer can become a larger cost than storage.
What is the biggest commonly missed S3 cost?
Data transfer out is often the biggest commonly missed cost. A team can have a small storage bill but a much larger total bill if users download or move a lot of data.