Webflow Developer Contracts: Scope, Ownership and IP Clauses

TL;DR: A Webflow developer contract is settled by five clauses, and the one that decides ownership is the copyright assignment. In the United States a transfer of copyright ownership is not valid unless it is in writing and signed by the owner of the rights conveyed, under 17 U.S.C. § 204(a). A paid invoice is not that document.

Lucas Rocha builds Webflow sites for agencies and end clients and is not a lawyer, so nothing below is legal advice. The US statutes cited here are the clearest published example rather than a universal rule. Treat this as the list to raise with whoever drafts your agreement.

What should a Webflow developer contract include?

A Webflow developer contract has to settle five clauses in writing: how scope is counted, whether copyright is expressly assigned and when, what happens when a work made for hire clause does not apply, which third-party licences travel with the site, and what the client owns if the project ends early. Everything else in a web development agreement is negotiable detail; these five decide who owns the build and what it cost to get there.

• Scope clause: count page templates rather than URLs, and state the revision rounds included.
• Assignment clause: an express written transfer of copyright, signed, effective on a stated trigger.
• Work made for hire clause: rarely effective alone, because a website is not one of the nine statutory categories.
• Licence schedule: every template, font, image and third-party script named with its licence.
• Termination clause: what the client owns if the project stops before the assignment triggers.

How should a Webflow contract define scope so it does not drift?

A Webflow contract defines scope safely when it counts unique page templates rather than published URLs, names the breakpoints to be built, and states how many revision rounds are included before extra work is billed. Counting pages is the most common way a fixed-price Webflow project quietly loses money, because a blog with 200 posts is one Collection page template, not 200 builds. On the Webflow builds I run for agencies the scope clause names the page templates, the CMS Collections and their fields, the breakpoints, the revision rounds and the exclusions such as content entry and copywriting. If your draft counts pages rather than templates, rewrite that line before anyone signs, and price the rounds using my breakdown of agency Webflow pricing.

Does paying a Webflow developer transfer copyright in the build?

Paying a Webflow developer does not by itself transfer the copyright in the design work or the custom code. Under 17 U.S.C. § 204(a), a transfer of copyright ownership other than by operation of law is not valid unless an instrument of conveyance, or a note or memorandum of the transfer, is in writing and signed by the owner of the rights conveyed.

What I see agencies get wrong is treating the invoice as the transfer. An invoice is evidence that money moved, not an instrument of conveyance, so a fully paid project with no assignment clause can leave the developer holding copyright in everything they authored. What I insist on in that clause is a named list of deliverables rather than the phrase "the website", because a clause naming nothing specific invites an argument about what actually changed hands. Which accounts and assets belong in the ownership clause is mapped separately in my guide to who owns your website. If a Webflow contract has no clause using the word "assigns", assume the copyright has not moved.

Why does a work made for hire clause usually fail for a website?

A work made for hire clause usually fails for a website built by an independent contractor because a website does not fall inside the nine categories of commissioned work the statute allows. The U.S. Copyright Office lists those nine in Circular 30: a contribution to a collective work, part of a motion picture or other audiovisual work, a translation, a supplementary work, a compilation, an instructional text, a test, answer material for a test, or an atlas. Circular 30 sets four conditions that must all hold at once, and states that a work failing any one of them is not a work made for hire. The rule I apply on client projects is never to rely on that clause alone: if your agreement has one, add an express assignment straight after it.

• The work must fall within one of the nine listed categories.
• There must be a written agreement between the commissioning party and the creator.
• The parties must expressly agree in that writing that the work is a work made for hire.
• The agreement must be signed by all parties, and failing any one condition defeats it.

Can a copyright assignment be terminated 35 years later?

A copyright assignment granted by an author on or after 1 January 1978 can be terminated by that author under 17 U.S.C. § 203, during the five years following the end of a 35-year period running from execution of the grant, with advance notice served not less than two and not more than ten years before the termination date. A work made for hire is excluded from that right entirely. The contract decision that follows is narrow but real: an agency wanting certainty should ask for the express assignment and accept that it is terminable in the 2060s, rather than reaching for work made for hire wording that will not apply to a website in the first place.

• Copyright in a work by an individual author lasts for the life of the author plus 70 years under 17 U.S.C. § 302, and an assignment covering that term can still be terminated in a five-year window opening 35 years after execution.
• A work made for hire runs 95 years from first publication or 120 years from creation, whichever expires first, and carries no termination right.

Who owns the Webflow template and third-party assets in the build?

A purchased Webflow template is licensed rather than sold, so the template creator keeps ownership of the template and the buyer holds only a licence to use it in one build. Webflow's Single-Use License lets the purchaser build one End Product for themselves or for one client, and states that Webflow itself is not a party to the licence, which sits between the template creator and the buyer. Two restrictions catch agencies out repeatedly: a client who receives the End Product cannot resell it, and neither party may extract a single component and use it outside that End Product. When I audit an inherited Webflow site, the licence trail on the template is the first thing I check.

• Paid template: one End Product for one client, and handing the template itself to someone else hands them your licence with it.
• Free template: unlimited projects and clients, but no resale on a third-party marketplace.
• Template graphics showing real products or trademarks are licensed for editorial use only, and clearance is the purchaser's responsibility.
• Fonts, stock imagery and third-party scripts each need a licence line, since those licences are often tied to the account that bought them.

What happens to ownership if the project stops before launch?

An assignment that takes effect on final payment transfers nothing when a project is abandoned before final payment, which is the single most overlooked consequence of the standard clause. The client is left holding a part-built Webflow site whose design and custom code are still the developer's copyright, and the developer is left holding work nobody will pay for. Both sides usually discover this at the worst possible moment.

The structure I use on longer builds is a staged assignment: each milestone payment assigns the deliverables accepted at that milestone, so a project that stops at stage three leaves the client owning stages one to three outright. If your contract has one assignment trigger at the very end, add a termination clause that says what the client receives and on what terms if the project ends early. How agencies structure the wider delivery relationship around that sits in my white label Webflow workflow guide.

What goes wrong in Webflow developer contracts?

Four failure patterns account for most of the Webflow contract arguments I get called into: scope counted in pages rather than templates, an invoice treated as a copyright transfer, a work made for hire clause used with no assignment behind it, and a single assignment trigger sitting at final payment. Each one costs a sentence to fix while the contract is still a draft, and weeks to argue about at handover.

Clause	What it must name	What breaks if it is missing
Scope	Unique page templates, CMS Collections and their fields, breakpoints, revision rounds, exclusions	A CMS build priced as one page is delivered as hundreds, and the fixed price absorbs it
Copyright assignment	The specific deliverables assigned, in writing, signed by the developer	The developer keeps copyright in the design and custom code after being paid in full
Work made for hire fallback	An express assignment sitting immediately after the work made for hire wording	The work made for hire clause fails on a website and nothing transfers at all
Licence schedule	The Webflow template, fonts, stock images and third-party scripts, each with its licence	The client inherits a site it cannot lawfully reuse, resell or rebuild from
Termination	What the client owns if the project ends before the assignment triggers	An abandoned project leaves a part-built site neither side can use

Want a second opinion on a Webflow scope before you sign it?

Send me the scope and deliverables section of your next Webflow agreement and book a 15-minute call. On the call I will name which deliverables are underspecified from a build point of view, what the work realistically costs in days, and whether the revision rounds match the design you are handing over. Legal wording stays with your lawyer; the build reality is what I can price on the spot. If you are still choosing a developer, my guide to hiring a Webflow developer and my questions to ask a Webflow developer cover the conversation before the contract.