imajes.

How image, sound, video and document files actually work — and what it takes to publish them.

Archive since 2003

Imajes / Publishing

Publishing

How Much Does It Cost to Run a Website Per Year: Fixed vs Variable Expenses

When planning a small site’s annual budget, the most eye-opening distinction is between immutable costs and infrastructure that scales with traffic. Even a microsite will owe for its domain and hosting, but a popular site will also rack up fees on add-ons that seem unnecessary for low-volume pages. We dug into the facts to break the annual costs into their fixed and variable parts, for sites of any size.

September 8, 2026 · 3 min read · Searched for: “how much does it cost to run a website per year”

Illustration for “How Much Does It Cost to Run a Website Per Year: Fixed vs Variable Expenses”
Server racks at the NOIRLab Headquarters Computer Server Room in Tucson, Arizona, in 2011. Photo: NOIRLab/NSF/AURA/T. Slovinský, CC BY 4.0, via Wikimedia Commons.
In this article
  1. Domain and registration
  2. Hosting choices
  3. Email and certificate
  4. Backups and storage
  5. Two worked budgets
  6. Updates and labor

Domain and registration

Understanding what a domain renewal costs is a good place to start, and not just because it’s a line-item cost to budget. Even before considering hosting, email, or backups, a once-promoted domain can cost a notable sum on renewal, so that expense is not a one-off.

GoDaddy’s listed renewal price for a.com is $22.99, plus any added ICANN fee; GoDaddy’s fee is marked as $0.20.

Hosting choices

The hosting layer is where a site’s overall cost splits into fixed and variable parts. At the smallest scale, a site could run on a static host within a free pricing tier. Cloudflare Pages leverages the company’s free Bandwidth Cloud to serve raw static content, so Cloudflare Pages is free for basic use (though paid Worker plans start qualified users on a $5 per month commitment.)

A more full-featured static host can be a fixed cost or a variable one, depending on the site’s shape. Netlify offers the Netlify Starter Plan free, with paid bandwidth falling under its Pro Plan, priced at $19 per user per month.

For a more dynamic site, even a tiny one, the costs start to scale with traffic. Shared hosting or a basic VPS are both in this category. DigitalOcean sells a Droplet as a basic server with tiered pricing; its foundation droplet prices at $4.00 per month. That’s a fixed cost, one that can sit under a site’s total limit, though more compute power becomes necessary as a site’s demand grows. Comparably, German company Hetzner publishes a low-end instance in its cloud stack at €4.51.

Email and certificate

Separating the sending email layer from the hosting layer comes as a distinction of cost. Amazon SES prices a one-off email at $0.10 per 1,000 messages, opening up potential charges for attachments and outbound data that can add up. In contrast, a hosted email box in a full-stacked office suite can cost more as a month-to-month service. Google Workspace Business Starter, for a hosted suite including email, currently costs $7 per user per month. Microsoft 365 Business Basic is comparable, priced at Microsoft 365 Business Basic is comparable, priced at $6.00 per user per month.

The TLS layer can come free, thanks to projects by Let’s Encrypt and bundles from platform providers like Cloudflare, so a certificate is the line-item cost only when a site uses it.

Backups and storage

Storing a site’s off-site copy as an archive or a mirror is a sensible insurance, though it can add up. Backblaze B2 charges $6 per terabyte per month, so

At low volumes, though, this isn’t a critical factor, and “backups” doesn’t necessarily imply a dedicated storage bucket. A 1 to 10 megabyte site will only need 0.001 to 0.001 TB in storage, about one one-millionth of the Backblaze plan, so its storage doesn’t land close to thresholds at embarking scale.

Two worked budgets

The site’s upfront costs can be a vision of its shape. A personal site that does not receive a flood of traffic, built entirely with a standard stack, can keep its expenses fixed, mainly bound by the hosting choice.

Unplugged from the heap: an example of an ideal static host, ](https://blog.logrocket.com/static-generators-perf/tests/phase-one). An access-logged server is a thing of simpler times, so we consider a setup that statically hosts on the server side, like Netlify. Compare it to the shared hosting we tested on.

Using these figures, an unstyled HTML/PHP site will load at around 0.02 seconds; a standard CMS page such as WordPress will be 0.1-0.15; prestige front-end pages (loaded with React etc.) have load times of 0.20+. Those hosted by mature static generators (e.g., Hugo) are all at 0.06 or lower.

Updates and labor

A site’s size can moot the VM price or the CDN subscription, but what can’t be left to computers is the planning of deliverables. Sites with frequent code and content updates, especially business sites, will need a line-item for labor, which can be larger than hosting.

This will depend on the site’s end state, and the ‘editor’ of its final state. Commonly, sites that are treated like lone artifacts are maintained in one combined clip, but more visionary sites– especially branded sites– create a stream for design/ content updates, especially when estimates detail.

The number of requests will depend on the editor’s charge and update habit, but just as the front-end stack can speed up load times, for example, arrange both stacks in an exercise that comes often enough to argue for tech stack at the center of the exercise.

More in Publishing