A free web design contract template covering design deliverables, feedback rounds, content responsibilities, browser support, launch handover, and payment stages. Written for freelance designers and studios.
Most web design disputes trace back to three unwritten assumptions: the client thought copy and images were included, the designer thought two feedback rounds meant two, and nobody decided who handles the site after launch. This contract template settles all three in writing. It defines the deliverables by page templates and revision rounds rather than vague "a website," makes content responsibility explicit (who writes the copy, who supplies photography, and what happens to the timeline when content arrives late), and pins down the technical boundaries, including which browsers and devices are supported and whether accessibility standards are in scope. There's also a kill-fee arrangement so you're paid for completed stages if the client walks mid-project, and a handover section covering hosting, credentials, and whether post-launch changes are billable. Adapt the deliverables schedule to each project and get it signed before design work starts.
Cap them in the contract and define what one round means: a single consolidated set of comments from one nominated client contact, returned within an agreed window. Additional rounds bill at your hourly rate. Consolidation is the key word, since five stakeholders sending notes separately is five rounds wearing a trench coat.
Whichever answer you choose, write it into the contract, because clients routinely assume it's you. If the client supplies content, add a clause pausing the project timeline when materials are late. If you're providing copywriting or stock imagery, list it as a priced line item so its absence from a cheaper quote makes sense.
This template uses stage-based payments with a kill fee: completed stages are payable in full, the current stage is billed for work done, and the deposit is retained. That structure means abandonment costs the client something real, and you're never more than one stage exposed.
Yes, briefly. State the browsers and versions you test against and whether the build targets a standard such as WCAG 2.1 AA. Otherwise you can face demands to debug an eight-year-old browser for free, or discover post-launch that the client's legal team expected an accessibility audit.
Edit the template, upload the final document to Papersign, place fields for both signatures, and send it off. The client signs in their browser, you get a notification, and both parties receive the executed copy for their records.
*Paperform ("Paperform" or "we") provides the information, data, links and other materials on this page (collectively, "Information") for informational and educational purposes only. We do not warrant or represent the accuracy, completeness, currency, or suitability of any Information for any use or purpose. Paperform is not a licensed legal provider nor is it providing any legal advice. Nothing contained in the Information is intended to create an attorney-client relationship, to replace the services of a licensed, trained attorney or legal professional, or to be a substitute for the legal advice of an attorney or trained legal professional licensed in your state/jurisdiction.