Web Design Contract: Template and Key Clauses (2026)

A web design contract sets the terms between a designer or agency and a client for designing a website. It is different from a pure development contract because the work is visual and subjective, which makes design rounds, approval and ownership of creative assets the parts that cause the most friction. This guide gives you a usable clause-by-clause skeleton, explains what each part does, and flags the common mistakes. This is general information, not legal advice. Contract and copyright rules differ by country, for example the United States, the United Kingdom and India, so have an important agreement checked by a professional in your jurisdiction before you sign. ## When you need this contract Use a written contract for any paid web design work. It matters most when the design will go through several rounds, when the client is particular about look and feel, or when fonts, stock images and other licensed assets are involved. Because taste is subjective, a clear contract about how many design rounds are included and what counts as approval is what keeps a project from dragging on without end. ## The clause-by-clause skeleton 1. Parties and effective date. Name the designer or agency and the client in full, with addresses, and the date the contract starts. 2. Scope and deliverables. Describe what will be designed: the number of page templates or screens, whether it covers desktop and mobile layouts, the design tool used, and what the client receives, such as design files, a style guide, and exported assets. Say whether development or build is included, since web design and web development are often separate. State clearly what is not included. 3. Design process and rounds. The key clause for design. Set out the stages, for example moodboard or direction, first draft, and refinement, and state how many rounds of revisions are included at each stage. Define what counts as a revision versus a brand new direction, and the rate for extra rounds. This single clause prevents endless redesigns. 4. Timelines and milestones. Set a start date, milestones tied to approvals, and a target completion date. Make clear that the schedule depends on the client giving feedback and content on time, so client delay moves the dates. 5. Fees and payment schedule. State the total fee, the currency, and the payment stages, such as a deposit before work starts, a payment at design approval, and a final payment on handover. Give due dates, the payment method, and a late payment charge. 6. Client content and feedback. List what the client must supply, such as text, logos, brand guidelines and images, and consolidated feedback by agreed dates. Missing content delays the project and is not the designer's fault. 7. Intellectual property and ownership. Be precise. Usually the client owns the final approved design once they have paid in full, with the transfer happening on full payment. The designer normally keeps the rights to unused concepts, working files and their own reusable elements unless you agree otherwise. Say clearly whether editable source files are handed over or only exported assets. 8. Fonts, stock images and third party assets. Design often uses licensed fonts, icons and stock photos. State who buys these licences, in whose name, and that the client is responsible for the ongoing licence of anything that is not the designer's own. This avoids a nasty surprise where a font or image was never properly licensed. 9. Portfolio rights. The designer usually wants to show the finished design in their portfolio and case studies and to credit themselves in the site footer. Agree this, and let the client request that sensitive work be kept private. 10. Approval and acceptance. Describe how the client signs off each stage and a review window after which a deliverable is treated as approved if no changes are requested. Written approval at each stage protects both sides. 11. Confidentiality. Both sides keep each other's non public information private, which matters where the designer sees unreleased products or business plans. 12. Warranties. The designer warrants the work is original and done with reasonable skill, and that it does not knowingly copy another's work. Avoid promising results such as traffic or sales, which design alone cannot guarantee. 13. Limitation of liability. Cap the designer's total liability, often at the fees paid, and exclude indirect losses such as lost profits, as far as the law allows. 14. Independent contractor status. State that the designer is an independent contractor, not an employee, responsible for their own taxes. 15. Cancellation and kill fee. Say how either side can end the contract, the notice required, and that the client pays for work and approved stages up to that point. A kill fee compensates the designer if the client cancels a committed project. 16. Governing law and disputes. Name the country or state whose law applies and how disputes are handled, which matters for cross border projects. ## Common mistakes to avoid The biggest mistake is leaving the number of design rounds open, which invites unlimited free revisions. The second is being vague about ownership of source files and unused concepts, which leads to arguments after handover. Others include not sorting out who licenses fonts and stock images, tying IP transfer to anything other than full payment, and promising business results the design cannot control. Fix these and a design project stays on schedule and on budget. ## From a signed contract to a managed project A strong contract is the start. The ongoing part is keeping track of the signed version, the design rounds used, the approval sign offs, and the payment stages, which is easy to lose across email threads and shared drives when you run several clients. Adira is an AI legal operating system built on Claude that keeps the whole cycle, from drafting and reviewing a contract for risk, to signing it, to tracking the key dates and payment stages, in one workspace tuned to how you work, with public per-seat pricing and a short free trial. You can see how it works at adiralaw.com. A single pane showing the status of every contract is on its roadmap. For a single project, a clear template and careful reading are enough; the workspace helps once you manage many clients at once.