A web design contract protects you by defining scope, payment schedule, ownership, revisions, and what happens if the project stalls or cancels. The clauses that matter most are a deposit, a kill fee, IP transfer on final payment, and a cap on revisions. Have a lawyer review it; this is not legal advice.
A web design contract is the document that makes your proposal binding. It spells out who builds what, who owns it, when and how you get paid, and what happens when things change or go wrong. It’s the difference between an awkward email and an enforceable invoice. Below are the clauses that actually protect you, a copy-paste template, and a plain-English read on each one.
We build websites under other agencies’ brands, so we’ve seen what happens when the contract is thin or missing. It’s never a problem until it’s a big one. The Freelancers Union reports that 71% of freelancers struggle to get paid. A contract is the single biggest thing standing between you and that statistic.
The clauses a web design contract needs
A web design contract doesn’t have to be long. It has to cover the points that turn into fights. These ten do the work:
- Scope of work. What you’re building, tied to the signed proposal. The contract makes the scope you agreed in the proposal legally binding instead of a friendly understanding.
- Payment schedule. A fixed total split into milestones, a deposit before work starts, and a due date on invoices. This is the clause that gets you paid, so don’t soften it.
- Revisions. How many rounds are included and what a revision is. Without this, “a few tweaks” becomes unlimited free work.
- Change orders. Anything outside the scope gets quoted and approved in writing first. This is your change request process written into the agreement, so the first out-of-scope ask isn’t a fight.
- Client responsibilities. Content, assets, approvals, and access by agreed dates. Most missed deadlines are the client’s, and this clause says so up front.
- Ownership and IP. Who owns the final site, and when. The standard is that ownership transfers on final payment, which also means you keep leverage until you’re paid. Get this wrong and you can hand over a site you don’t own the rights to.
- Timeline and delays. An estimated launch that explicitly moves when the client is slow, so their delay doesn’t become your missed deadline.
- Termination. How either side can walk away, with the client paying for work done and deposits non-refundable. Protects you from a project that gets cancelled halfway.
- Warranty and liability. A short defect-fix window after launch, and a cap on your liability at the fees paid. Stops a small bug becoming a large claim.
- Governing law. Which state or country’s law applies and where disputes are settled. Boring until you need it.
Free web design contract template (copy and paste)
A practical skeleton you can adapt. Fill the brackets and have a lawyer check it for your jurisdiction before you use it on a real project.
WEB DESIGN CONTRACT
Between: [Your agency] ("Designer") and [Client name] ("Client")
Date: [Date]
1. SCOPE OF WORK
The Designer will build what's set out in the signed proposal dated [date]:
[list the deliverables, or reference the proposal]. Anything outside that scope is
handled under section 5.
2. PAYMENT
Total: [$ fixed price]. Schedule:
- [30%] deposit before work starts
- [40%] at design approval
- [30%] before launch and handover of final files
Invoices are due within [7] days. Late payment may pause work and accrue [1.5%] per month.
3. TIMELINE
Estimated launch: [date], assuming the Client supplies content, approvals, and access on
time. Client delays move the timeline.
4. REVISIONS
[Two] rounds of revisions are included at the design stage, supplied as one consolidated
set of feedback from [the Client's named decision-maker]. Extra rounds are billed at
[$/hour] or quoted as a change.
5. CHANGES
Any work outside section 1 is a change. The Designer will quote the added cost and time in
a written change order. Work on it begins only after the Client approves it in writing.
6. CLIENT RESPONSIBILITIES
The Client provides final copy, images, logos, brand assets, and any logins by the dates
agreed, and is responsible for the rights and legality of materials they supply and for
approving final content before launch.
7. OWNERSHIP AND INTELLECTUAL PROPERTY
On final payment, the Designer assigns to the Client the rights to the final delivered
design and custom code. The Designer keeps rights to pre-existing tools and general
know-how and may show the work in its portfolio. Third-party themes, plugins, fonts, and
stock are licensed under their own terms.
8. TERMINATION
Either party may end this agreement with [14] days' written notice. The Client pays for all
work completed to that date. Deposits are non-refundable.
9. WARRANTY AND LIABILITY
The Designer will fix defects reported within [30] days of launch at no charge. The Designer
is not liable for indirect or consequential losses, and total liability is limited to the
fees paid under this contract.
10. GOVERNING LAW
This agreement is governed by the laws of [your state or country], and disputes are handled
in [that jurisdiction].
11. ACCEPTANCE
Signed: ____________________ (Designer) Date: __________
Signed: ____________________ (Client) Date: __________
One thing this template is not
It’s a starting point, not legal advice. We build websites; we’re not your lawyers. The clauses above cover the situations we see go wrong on web projects, but a binding contract should be reviewed by someone qualified in your state or country, especially the ownership, liability, and governing-law sections. Use this to get the commercial terms clear in plain language, then have a professional turn it into something enforceable where you operate.
Proposal, contract, change order: how they fit together
These three documents are one system. The proposal wins the project and sets the scope and price. The contract makes those terms binding and adds the legal protections (payment, IP, liability). The change order handles everything that comes up after, so the scope you signed stays the scope you deliver.
Get the first two right and you rarely fight about the third. A vague contract is where scope creep turns from an annoyance into an unpaid month.
Pricing the work in the contract
The payment section is only as good as the number in it. Quote a fixed price you’re confident covers the build plus your margin, which means knowing what the build actually costs you first. Our website cost calculator gives you a fast starting range to mark up from, and our guide to web design pricing covers the models and margins.
If you’d rather not carry the build risk at all, you can get a fixed quote from a white-label WordPress team, put your marked-up number in the contract, and have the work delivered under your brand. You hold the client relationship and the contract; we handle the build.
- A contract protects you by defining scope, payment schedule, ownership, revisions, and what happens if the project stalls.
- The highest-leverage clauses are a deposit, a kill fee, IP transfer on final payment, and a revision cap.
- Spell out who owns what and when, so ownership transfers only after you are paid in full.
- This is a starting template, not legal advice; have a lawyer review it before you sign.
Frequently asked questions
What should a web design contract include?
Ten clauses: scope of work, payment schedule, revisions, change orders, client responsibilities, ownership and IP, timeline and delays, termination, warranty and liability, and governing law. The payment, IP, and liability clauses are the ones that protect you most when a project goes sideways.
Do I need a contract for a small website project?
Yes. Small projects produce just as many payment and scope disputes as big ones, and the Freelancers Union found 71% of freelancers struggle to get paid. A one-page contract that nails scope, payment, and ownership is enough for a small build, and it’s far cheaper than chasing an unpaid invoice.
What’s the difference between a web design proposal and a contract?
The proposal sells the project and lays out scope and price in plain language. The contract makes those terms legally binding and adds the protections a proposal doesn’t, like payment enforcement, IP ownership, and liability limits. Many agencies attach the contract to the proposal so one signature does both.
Who owns the website, the designer or the client?
It depends on what the contract says, which is exactly why the IP clause matters. The common standard is that ownership of the final design and custom code transfers to the client on final payment, while the designer keeps their own tools and reusable code. Third-party themes, plugins, and fonts stay under their own licenses.
Is a web design contract template legally binding?
A template is a starting point, not a finished legal document. It gets your commercial terms clear, but a binding agreement should be reviewed by a lawyer in your jurisdiction, especially the ownership, liability, and governing-law sections. Use the template to agree the plain-English terms, then have it made enforceable where you operate.
How do I handle changes after the contract is signed?
Through a change order. Any request outside the signed scope gets quoted for cost and time in writing, and work starts only once the client approves it. The contract’s change clause sets that expectation on day one, so out-of-scope requests get priced instead of quietly absorbed.
Need the build but not the risk? You can send us the details and we’ll give you a fixed quote you can put straight into your contract and mark up.
Get a free consultation and a fixed quote, usually within one business day, delivered under your agency's brand.