Skip to content
Welcome back Continue →

Free web design contract template (Word)

Reviewed by Clausery editors · · 3 min read

A contract between a web designer/developer and a client covering design scope, number of pages, CMS/platform, revisions, hosting/domain responsibilities, fees, launch and post-launch support.

No sign-up. Editable Word (.docx) or print to PDF. Your answers stay in your browser. Updated .

A web design contract defines what website the designer will build, what platform/CMS it will use, how many pages/templates, who provides content, what browsers/devices it supports, the launch process, and what post-launch support is included.

Web projects are prone to scope creep (extra features, content delays). Clear revision rounds, content deadlines and change-order procedures are essential.

What to include#

  • Parties and project. Designer/developer name/business; client name; project description/scope; start date and estimated launch date.
  • Scope and deliverables. Number of pages/templates, platform (WordPress, Webflow, custom), key features (contact form, e-commerce, blog), design rounds, browser/device support, and whether content migration is included.
  • Client responsibilities. Content copy, images and branding assets by deadlines, feedback turnaround, domain/hosting setup, and point of contact.
  • Fees and payment. Total project fee, deposit (e.g. 50%), milestone payments (design approval, development, launch), late fees, and extra-work/change-order rates.
  • Launch, support and IP. Launch date, client training/walkthrough, post-launch support period (e.g. 30 days bug fixes), hosting/maintenance terms, IP transfer on final payment, and designer portfolio rights.

How to fill it in#

  1. Step 1: Define scope tightly

    List specific pages, templates and features; anything not listed is out of scope.

  2. Step 2: Set content deadlines

    Client-delayed content is the #1 reason web projects slip — state who provides what by when, and delays push launch.

  3. Step 3: Limit revisions

    Include 2-3 rounds of design revisions and change-order rate for extra features.

  4. Step 4: Specify browser/device support

    Name supported browsers (evergreen) and breakpoint targets (desktop, tablet, mobile); you cannot support every legacy browser.

  5. Step 5: Clarify post-launch

    Include 30 days bug fixes; ongoing maintenance/hosting is a separate retainer or client responsibility.

Questions

Who owns the website?

Client owns the final design and content on final payment; designer retains rights to code libraries/portfolio unless work-for-hire.

Do I provide hosting?

Choose a clear policy — either you arrange hosting (with a recurring fee) or the client signs up for their own account.

Are plugins/fonts included?

State who pays for premium themes/plugins/fonts and who holds the licenses.

What about SEO?

Specify whether basic on-page SEO is included or a separate service.

What if the client does not provide content?

Include a clause that content delays push the timeline and may incur a project-pause fee.

Browse all templates →

These are general templates, not legal or tax advice. Have anything unusual reviewed for your jurisdiction.

Continue drafting Top