How much does a static site cost? Hosting from nearly free to a few dollars
A static website hosted on S3 and CloudFront, or a static host, costs almost nothing at low traffic, often pennies to a few dollars a month, with data transfer and requests the only real meters. Here is the breakdown and where costs can grow.
Quick answer
A static website is one of the cheapest things you can host: on S3 plus CloudFront, a low-traffic site often costs pennies to a few dollars a month, since you pay only for storage (tiny), requests (cheap), and data transfer out (the main meter). At low traffic it is nearly free; cost grows only with bandwidth as traffic scales. The free tier can cover a small site entirely for the first year. Higher-traffic sites pay mostly for CloudFront data transfer, so egress is the number to watch. There is no server to pay for, which is why static sites are so cheap.
A static site (HTML, CSS, JavaScript, and assets with no server-side application) is the cheapest kind of website to host because there is no compute to pay for. You store the files and serve them, and the only real meters are storage, requests, and data transfer. For most personal and small business sites, the monthly cost rounds to pennies or a few dollars, which surprises people expecting a hosting bill.
What you pay for
| Component | Cost role |
|---|---|
| S3 storage | Per GB, tiny for a static site |
| S3 / CloudFront requests | Per request, very cheap |
| Data transfer out | Per GB, the main meter |
| CloudFront (CDN) | Per GB served plus requests |
| Route 53 (DNS) | Small monthly per hosted zone |
Storage for a static site is usually a fraction of a GB, so it costs almost nothing, and requests are priced per million and stay cheap. The dominant meter is data transfer out to visitors, which is why the question of static-site cost is really a question of bandwidth. The free-tier question overlaps with whether S3 is really free to start.
A rough monthly picture
| Traffic | Rough monthly cost |
|---|---|
| Personal / low traffic | Pennies to about 1 |
| Small business (moderate traffic) | A few dollars |
| Popular site (high bandwidth) | Mostly CloudFront transfer, grows with GB |
The free tier can cover a small site entirely for the first year, and even after, a low-traffic site stays in the pennies-to-a-few-dollars range. Only when bandwidth climbs does CloudFront data transfer become the real cost, and that scales gently, this is the low end of running a website on AWS.
Why static sites are so cheap
There is no server running 24/7, no database, and no compute to keep warm, so you avoid the largest costs of dynamic hosting. You pay only for what visitors actually consume: storage of a few files and the bytes served to them. Adding CloudFront in front reduces origin requests and improves performance, and its data-transfer pricing is competitive, so a CDN often makes a busy static site cheaper and faster at once.
Where cost can grow and how to control it
The one thing that scales a static site's bill is bandwidth, so if you serve large media or high traffic, watch data transfer, the same egress meter covered in the egress reduction checklist. Compress assets, cache aggressively at the CDN, and optimize image sizes to cut bytes served. For a dynamic site with a backend, cost jumps because you add compute, closer to hosting an API. But for a genuinely static site, the answer is simple: it is nearly free at low traffic, and it grows only with the bandwidth you serve.
FAQ
How much does a static site cost to host?
Very little. On S3 plus CloudFront, a low-traffic static site often costs pennies to a few dollars a month, since you pay only for storage (tiny), requests (cheap), and data transfer out (the main meter). The free tier can cover a small site entirely for the first year, and even after, a low-traffic site stays in the pennies-to-a-few-dollars range.
Why is a static site so cheap?
Because there is no server running 24/7, no database, and no compute to keep warm, so you avoid the largest costs of dynamic hosting. You pay only for what visitors consume: storage of a few files and the bytes served to them. Removing the server is what drops the cost from a monthly hosting bill to near zero at low traffic.
What is the main cost of a static site?
Data transfer out to visitors. Storage is a fraction of a GB and costs almost nothing, and requests are priced per million and stay cheap, so bandwidth is the meter that matters. A low-traffic site barely registers, but a high-traffic or media-heavy site pays mostly for CloudFront data transfer, which scales with the GB served.
Does a static site use the AWS free tier?
Yes, effectively. The free tier's S3 storage, requests, and CloudFront data transfer allowances can cover a small static site entirely for the first year, making it genuinely free to start. After the free tier expires, a low-traffic site still costs only pennies to a few dollars a month, so the ongoing cost stays minimal.
How do I keep a high-traffic static site cheap?
Watch data transfer, since bandwidth is the only thing that scales the bill. Compress assets, cache aggressively at the CDN so CloudFront serves from edge rather than origin, and optimize image and media sizes to cut bytes served. A well-cached, compressed static site keeps its cost low even at meaningful traffic because you are serving fewer bytes per visitor.
How does C3X help with static site cost?
C3X reads your Terraform and prices the resources behind a static site (S3 buckets, CloudFront distributions, Route 53 zones) against a live catalog before deploy. For a static site the cost is small, but seeing it confirms the setup is as cheap as expected and catches an accidentally pricey configuration before it ships.
What to do next
Confirm your static site setup is as cheap as it should be. C3X reads your Terraform and prices your resources against a live catalog. Start with the quickstart.
Share this post
Try C3X on your own Terraform
Free and open source. No API key required. One command to install, one command to estimate.