Do I need a web hosting agreement if I use a big provider like AWS or a shared host?

Those providers already bind you to their own terms of service and acceptable use policy when you sign up, so you usually do not draft a separate contract with them. You need your own web hosting agreement when you are the one providing hosting to someone else, for example a web designer who hosts client sites, an agency that resells server space, or a freelancer who manages a client's server. In that situation your agreement sits between you and your client.

What uptime percentage should a web hosting agreement guarantee?

Most hosting contracts promise 99.9% uptime, which allows for roughly 43 minutes of downtime per month. Some providers offer 99.99% for higher-tier plans. Avoid promising 100%, which is impossible to honor once you account for maintenance windows and upstream outages. Whatever number you choose, define how it is measured, exclude scheduled maintenance, and state the remedy, usually a service credit, when you miss it.

Who owns the website and data on a hosted server?

The client owns their website files, database, and content. The hosting provider owns the server infrastructure and software it licenses. A clear web hosting agreement says this plainly and gives the client the right to download or migrate their data on request, especially at termination. Without that clause, clients sometimes find their data held hostage during a billing dispute, which damages your reputation even when you are in the right.

Can a hosting provider suspend a website for non-payment?

Yes, if the agreement gives them that right. A well-written contract states how many days past due triggers suspension, requires written notice first, and explains how to restore service once the balance is paid. Suspending without a contractual basis or warning can expose you to a breach claim, so spell out the process rather than acting on an ad hoc basis.

How is a web hosting agreement different from a web design contract?

A web design contract covers the one-time work of building a site: scope, milestones, revisions, and the handoff. A web hosting agreement is an ongoing service that keeps the site online: server space, uptime, backups, support, and recurring fees. Many web professionals sign both with a client, or fold hosting into a single document as a separate recurring section.

Web Hosting Agreement: How to Write One

A practical guide to drafting a web hosting contract. Covers uptime guarantees, billing, backups, acceptable use, liability limits, and termination terms.

A web hosting agreement is the contract that governs the relationship between whoever keeps a website online and whoever owns that website. It sounds like back-office paperwork until something breaks: the site goes down during a product launch, a client stops paying, a server gets hacked, or someone wants their files back in a hurry. When that happens, the agreement is the only thing that decides who is responsible and what they owe.

If you host websites for clients, resell server space, or manage someone else's infrastructure, you need this contract in place before the first site goes live. This guide walks through what a web hosting agreement covers, the clauses that actually matter, a step-by-step drafting process, and the mistakes that turn a routine outage into a legal fight.

What Is a Web Hosting Agreement?

A web hosting agreement is a service contract in which one party, the hosting provider, agrees to store and serve another party's website on its servers in exchange for a recurring fee. The other party, the client or subscriber, agrees to pay and to use the service within defined limits.

The provider is not always a giant data center. Plenty of web hosting agreements are signed by:

Web designers and agencies who host the sites they build, often reselling space from an upstream host
Freelance developers who manage a client's dedicated or virtual server
Managed hosting companies that handle servers, updates, and security for a roster of clients
IT consultants who bundle hosting into a broader support arrangement

In all of these cases the agreement does the same job: it sets expectations for uptime, defines what the client is paying for, limits the provider's liability when things go wrong, and gives both sides an orderly way to end the relationship.

Who Needs One

You need a written web hosting agreement any time you are the one providing hosting rather than buying it. A handshake or an email thread is not enough once real money and real downtime are on the table.

If you are simply a customer of a large host, you do not draft your own contract. You accept their terms of service and acceptable use policy at signup, and those documents already cover the relationship. The need for your own agreement appears the moment you sit on the provider side, even informally, such as a designer who tells a client "I'll handle hosting for $30 a month." That sentence is a hosting service, and it deserves a contract.

Key Clauses in a Web Hosting Agreement

1. Description of Services and Specifications

Spell out exactly what the client is buying. Vague service descriptions are the root of most hosting disputes because the client imagines more than the provider intended to deliver.

Include:

Hosting type (shared, virtual private server, dedicated, cloud, or managed)
Allocated resources: storage, bandwidth or data transfer, RAM, CPU, number of sites or databases
What is included versus billed separately, such as SSL certificates, email hosting, or a content delivery network
Software and control panel access provided
Any overage charges when the client exceeds the plan

2. Uptime Guarantee and Service Levels

This is the clause clients read first. State the uptime percentage you commit to, how you measure it, and what happens when you miss it. A common structure is 99.9% monthly uptime, measured by your monitoring system, excluding scheduled maintenance and outages caused by the client.

The remedy for missed uptime is almost always a service credit, a percentage of the monthly fee returned for each band of downtime, rather than cash damages. Cap the total credit at one month's fee so a bad month does not turn into open-ended liability. For larger clients you may attach a full service level agreement; our guide to writing an SLA breaks down how to structure credits, measurement windows, and exclusions.

3. Fees, Billing, and Renewal

Money disputes end more hosting relationships than technical problems. Be specific:

The recurring fee and billing cycle (monthly, annual)
Setup or migration fees, if any
When payment is due and the grace period
Late fees and what happens to the account when payment lapses
Automatic renewal terms and how the client cancels before renewal
How and when you can raise prices, usually with 30 days' notice

4. Term, Renewal, and Termination

Define the initial term and whether it renews automatically. Then give both sides a clean exit. Cover:

Notice required to cancel (30 days is typical)
Termination for cause, such as non-payment or violating the acceptable use policy
Whether any prepaid fees are refundable
A data export window after termination so the client can retrieve their site

5. Data, Backups, and Ownership

State plainly that the client owns their website files, databases, and content, and that the provider owns the server hardware and licensed software. Then address backups, which clients always assume exist and are often surprised to learn do not.

Specify the backup frequency, how long backups are retained, and whether restoration is included or billed. If you do not provide backups, say so in writing. Most hosting disputes start in the gap between what a client assumed and what the provider actually agreed to do, so close that gap on paper.

6. Acceptable Use Policy

An acceptable use policy (AUP) protects you and your other clients from one bad actor on a shared server. Prohibit:

Illegal content and copyright infringement
Spam and unsolicited bulk email
Malware, phishing, and hacking activity
Resource abuse that degrades other sites on shared infrastructure
Adult content or other categories you choose not to host

Tie violations to your suspension and termination rights so you can act quickly when a site threatens your network.

7. Suspension and Termination of Service

Give yourself the right to suspend a site for non-payment or AUP violations, but require notice first except in emergencies like an active security threat. Describe how the client restores service. A documented process protects you from a breach claim and protects the client from being cut off without warning.

8. Security Responsibilities

Divide security duties clearly. The provider typically secures the physical server, network, and firewall, while the client is responsible for its own application code, passwords, plugins, and updates, unless you offer managed maintenance as part of the plan. Many hosting disputes after a hack come down to this line being blurry, so draw it sharply.

9. Limitation of Liability and Disclaimers

No host can guarantee a site is never down, never hacked, and never loses data. Limit your liability to the fees paid over a recent period, usually the prior one to three months, and disclaim responsibility for indirect damages like lost sales or lost profits. Clients rarely push back on this when it is reasonable, and it keeps a single outage from threatening your business.

10. Subcontractors and Upstream Providers

Most small hosts do not own a data center. They rent server space from an upstream provider and resell it. If that describes you, your agreement should let you use subcontractors and upstream vendors, and it should make clear that an outage or change at the upstream level can affect the service. You are still on the hook to your client, but you should not promise more reliability than your own provider gives you. Read your upstream contract first, then write your client terms to sit safely inside it.

11. Governing Law and Dispute Resolution

Name the state whose law applies and where disputes are resolved. This prevents a fight over venue before anyone reaches the actual issue, and it matters more than people expect when a client is in a different state.

How to Write a Web Hosting Agreement: Step by Step

Step 1: Identify the parties. Use full legal names, and for businesses, the entity type and state of formation. Name who is the provider and who is the client.

Step 2: Describe the service. List the hosting type, resources, and everything included so the client cannot later claim they expected more.

Step 3: Set the uptime commitment and remedy. Pick a realistic percentage, define how you measure it, exclude maintenance, and state the service credit for missing it.

Step 4: Lay out fees and billing. Cover the recurring fee, billing cycle, late fees, renewal, and price-change notice.

Step 5: Address data, backups, and ownership. Confirm the client owns their content, state your backup practice honestly, and grant a migration window at the end.

Step 6: Attach an acceptable use policy. Define prohibited uses and connect them to suspension rights.

Step 7: Add the legal terms. Limitation of liability, security responsibilities, governing law, and signatures from someone authorized to bind each party.

Common Mistakes to Avoid

Promising 100% uptime. It is physically impossible and instantly exposes you to a credit claim every time a single packet drops. Commit to a number you can actually hold.

Staying silent on backups. Clients assume you back up their site daily and can restore it on demand. If that is not true, the agreement is where you correct the assumption. Silence reads as a promise.

Skipping the acceptable use policy. Without an AUP you have no clean basis to remove a spammer or a malware host that is dragging down every other site on the server.

No limitation of liability. A site that earns the client thousands of dollars a day could, in theory, claim those losses against you for a few hours of downtime. Cap your exposure to the fees paid.

Forgetting the exit. Relationships end. If the agreement has no data-export window, a routine cancellation becomes a standoff over who controls the files.

Confusing hosting with the build. Hosting is an ongoing service, not the one-time work of building a site. If you also build websites, keep that scope in a separate web design contract so the two relationships do not blur together.

Where Hosting Fits With Your Other Contracts

A web hosting agreement rarely stands alone. If you provide ongoing maintenance, updates, and monitoring alongside hosting, a managed services agreement frames that broader relationship and references the hosting terms inside it. And if you simply want a clean, general-purpose framework for any recurring service you sell, a standard service agreement gives you the bones to adapt. The point is to match the document to the relationship: a one-time build, an ongoing host, or a full-service arrangement each call for different terms.

Related guides

Generate Your Web Hosting Agreement with Contractable

A solid web hosting contract is mostly about anticipating the moments when things go wrong and deciding in advance who is responsible. Once you know the structure, the drafting is straightforward, but getting every clause right for your specific plan and client takes care. Contractable generates a customized web hosting agreement in seconds, with the uptime, billing, backup, and liability terms that fit how you actually host. No lawyers or legal background required.