Freelance Contract Template: Everything You Need to Include in 2026

Sixty-four million Americans freelance. The majority of them either use a contract template they found on Google, sign whatever the client sends over, or -- worst of all -- work on a handshake and an email thread.

Here's the thing about contracts: a good one is worth more than a good client. A bad client with a strong contract can't hurt you -- they can try, but the language protects you. A good client with a bad contract can accidentally destroy you, because when things go sideways (and they will), the document is all that matters.

This guide covers the 12 clauses that should appear in every freelance contract. Not vague principles -- actual language you can adapt. Whether you're building your own contract from scratch or reviewing one a client just sent you, this is the checklist.

The 12 Essential Clauses Every Freelance Contract Needs

1. Scope of Work (The Most Important Clause)

If you only get one clause right, make it this one. The scope of work defines exactly what you're delivering, in what format, by when, and how many times the client gets to ask for changes. Everything that goes wrong in a freelance engagement -- scope creep, misaligned expectations, "I thought this was included" -- traces back to a vague scope of work.

Be specific to the point of redundancy. Don't write "website redesign." Write "redesign of 8 pages (Home, About, Services, Contact, Blog, Portfolio, FAQ, and Pricing) in Figma, delivered as desktop and mobile mockups in PDF and Figma file formats, with 2 rounds of revisions included."

The rule is simple: if it's not in the scope, it's not included. Period.

Here's sample language for three common freelance types:

Web designer:

Contractor shall design a responsive website consisting of 6 pages: Home, About, Services, Contact, Blog Index, and Blog Post template. Deliverables include Figma source files and exported assets. Design does not include development, copywriting, stock photography, or SEO optimization unless specified in an addendum.

Freelance writer:

Contractor shall write 4 blog articles of approximately 1,500 words each on topics mutually agreed upon prior to drafting. Deliverables include Google Docs with suggested meta descriptions. Fee includes one round of revisions per article. Research, interviews, and image sourcing are not included.

Developer:

Contractor shall build a custom contact form with field validation, email notification via SendGrid API, and submission logging to a PostgreSQL database. Deliverables include source code via GitHub repository and deployment to Client's staging environment. Ongoing maintenance, hosting configuration, and third-party API costs are not included.

2. Payment Terms

Payment terms define how much you get paid, when you get paid, and what happens when the client doesn't pay on time. The industry standard for project-based work is 50% upfront, 50% on delivery. For larger projects ($10,000+), a three-milestone structure works better: 40% at signing, 30% at midpoint, 30% on delivery.

Never start work before receiving the first payment. This isn't paranoia -- it's policy. The deposit confirms the client is serious and creates a financial commitment on their side before you invest your time.

Late payment penalties are not optional. Without them, you have no leverage when an invoice sits unpaid for 45 days. The standard penalty is 1.5% to 2% per month on overdue balances, and it should be stated clearly in the contract so nobody can claim they didn't know.

Client shall pay 50% of the total project fee ($X) upon execution of this Agreement and the remaining 50% upon delivery of final deliverables. Invoices are due within 14 days of receipt. Late payments shall accrue interest at a rate of 1.5% per month (18% annually) on any unpaid balance. Contractor reserves the right to suspend work on any project with an outstanding balance exceeding 14 days past due.

That last sentence matters. If the client stops paying, you stop working. Without that language, they could argue you breached the contract by pausing delivery.

3. Timeline and Milestones

A start date, milestone dates, and a final delivery date. These seem obvious but they do two things most freelancers overlook: they protect you from projects that drag on indefinitely, and they establish that the client has deadlines too.

The biggest timeline risk in freelance work isn't you missing a deadline -- it's the client missing theirs. They owe you content, feedback, assets, or approvals. When those are late, your entire schedule shifts. Without a clause addressing client-caused delays, you eat the cost of the schedule disruption.

Project timeline begins on the date Contractor receives the signed Agreement and initial deposit. The estimated completion date is [X weeks/months] from the start date, contingent upon Client providing all required materials, feedback, and approvals within 5 business days of each request. Delays caused by Client shall extend the project timeline by an equivalent duration. If Client-caused delays extend the project beyond [X date], Contractor reserves the right to renegotiate the project fee to reflect changed circumstances.

4. Revision Limits

Revisions are where freelance projects go to die. The client thinks "a few tweaks" is a revision. You think a complete directional overhaul is a new project. Without a contractual definition, you're both right and both angry.

Two to three revision rounds is standard. Define what counts as a round: one consolidated set of written feedback, delivered at one time, addressing the current deliverable. Not a rolling stream of Slack messages over two weeks. Not "just one more thing" repeated fifteen times.

After the included rounds, additional revisions bill at your hourly rate. This isn't punitive -- it's a natural boundary that forces the client to consolidate their feedback and be decisive. Most clients who know revisions four and beyond cost $125/hour will suddenly get much clearer about what they want in rounds one and two.

This Agreement includes 2 rounds of revisions per deliverable. A revision round is defined as one consolidated set of written feedback submitted by Client within 5 business days of deliverable receipt. Feedback received after 5 business days shall constitute the next revision round. Additional revisions beyond the included rounds shall be billed at Contractor's hourly rate of $[X]/hour, invoiced bi-weekly.

5. Intellectual Property Rights

IP is the highest-stakes clause in any freelance contract after payment. The core principle: work-for-hire means the client owns the deliverables they paid for. It does not mean they own your tools, templates, process, or anything you created before or outside of this project.

Two non-negotiable protections here. First, you retain ownership of all pre-existing intellectual property -- your code libraries, design systems, writing frameworks, and any tools you built on your own time. The client gets a license to use them as embedded in the deliverables, not ownership of them.

Second, and this is critical: IP transfers only upon full payment. If the client hasn't paid your final invoice, they don't own the work. This is your single strongest leverage point against non-payment.

Upon receipt of full payment, Contractor assigns to Client all rights, title, and interest in the final deliverables as described in the Scope of Work. Contractor retains ownership of all pre-existing materials, tools, code libraries, frameworks, and methodologies ("Contractor IP"), with a perpetual, non-exclusive, royalty-free license granted to Client solely for use as incorporated in the deliverables. No transfer of intellectual property rights shall occur until all payments under this Agreement have been received in full.

6. Kill Fee / Cancellation Clause

Projects get killed. Budgets get cut. New CMOs come in and scrap everything the old one approved. This is normal. What's not normal is you absorbing the financial hit.

A kill fee compensates you for the work you've completed and for the opportunity cost of the engagement. While you were reserved for this project, you were turning down other work. When the project dies, that pipeline doesn't magically refill.

Industry standard: payment for all completed work, plus 25-50% of the remaining contract value. On a $15,000 project that gets killed at the halfway point, you'd receive $7,500 for completed work plus $1,875-$3,750 as a cancellation fee on the remaining $7,500. Non-refundable deposits (your upfront payment) remain non-refundable.

Either party may terminate this Agreement with 14 days' written notice. Upon termination: (a) Client shall pay for all work completed to the date of termination, calculated on a pro-rata basis; (b) Client shall pay a cancellation fee equal to 25% of the remaining unpaid contract value; (c) all deposits previously paid are non-refundable; (d) Contractor shall deliver all completed work-in-progress within 7 business days of final payment. Intellectual property in unpaid work remains with Contractor.

7. Confidentiality

Confidentiality clauses should be mutual and time-limited. You agree not to share the client's proprietary business information. They agree not to share your pricing, methodology, or business details. Both sides are protected.

Keep it reasonable: a 2-3 year term with standard exclusions for information that's publicly available, independently developed, or required to be disclosed by law. If a client sends you a confidentiality clause with no end date, push back. Perpetual confidentiality obligations are for trade secrets in employment agreements, not for freelance web design projects.

One specific note: make sure the confidentiality clause doesn't prevent you from showing the work in your portfolio. If you can't use the deliverables as a portfolio piece or case study, you're losing marketing value. Negotiate a carve-out that allows you to display the work after launch or with client approval.

Both parties agree to maintain confidentiality of proprietary business information disclosed during the term of this Agreement for a period of 2 years following completion or termination. Confidential information excludes information that: (a) is or becomes publicly available through no fault of the receiving party; (b) was known to the receiving party prior to disclosure; (c) is independently developed without reference to the other party's information; or (d) is required to be disclosed by law. Contractor may display completed deliverables in their portfolio and marketing materials following public launch of the project, unless otherwise agreed in writing.

8. Non-Compete / Non-Solicitation

This one is simple: never accept a non-compete clause as a freelancer. You are not an employee. You are not receiving a salary, benefits, stock options, or job security in exchange for exclusivity. A non-compete restricts your ability to earn a living in your field, and accepting one as a freelancer is trading away your livelihood for a single project fee.

A non-solicitation clause is more reasonable, but keep it narrow. A well-written non-solicitation prevents you from directly poaching the client's specific customers or employees for a limited period -- typically 12 months. It does not prevent you from working in the same industry, serving competitors, or accepting inbound inquiries from people who find you independently.

If a client insists on a non-compete, you have two options. First, decline the engagement -- a client who wants to own your entire career for the price of one project is not a client who respects your business. Second, if the project fee justifies it, accept a dramatically narrowed version: specific named competitors only (not "the industry"), 3-6 months maximum, and a premium of 30-50% added to your fee to compensate for the restriction.

During the term of this Agreement and for 12 months thereafter, neither party shall directly solicit the employees or contracted freelancers of the other party. This clause does not restrict Contractor from working with Client's competitors, providing services in Client's industry, or accepting inbound inquiries from any source. No non-compete obligation exists under this Agreement.

9. Indemnification

Indemnification clauses determine who pays when things go wrong. In a freelance contract, indemnification should be mutual: you indemnify the client against claims arising from your work (plagiarism, copyright infringement in your deliverables), and the client indemnifies you against claims arising from how they use your work (regulatory violations, misrepresentation to their customers).

The critical detail: cap your liability at the total fees paid under the agreement. This is standard practice and protects you from catastrophic exposure. If you built a $5,000 website and a defect causes the client $200,000 in damages, you should not be on the hook for $200,000. Your maximum exposure should be $5,000 -- the value of the contract.

Also exclude consequential and indirect damages. You are responsible for the deliverables. You are not an insurance policy for the client's entire business.

Each party shall indemnify and hold harmless the other party against third-party claims arising from the indemnifying party's breach of this Agreement or negligence. Contractor's total aggregate liability under this Agreement shall not exceed the total fees paid by Client under this Agreement. In no event shall either party be liable for indirect, incidental, consequential, or punitive damages, including lost profits or lost business opportunities.

10. Dispute Resolution

Nobody wants to think about disputes when they're starting a project. But the cost of resolving a disagreement is defined by what your contract says, not by who's right.

Structure it as a three-step escalation: informal negotiation first (a phone call, 30 days to resolve it between yourselves), mediation second (a neutral mediator, much cheaper than litigation), and binding arbitration or small claims court third.

Two things to insist on. First, jurisdiction should be in your state, not the client's. If you're in Texas and the client is in New York, you don't want to fly to New York for a $7,000 dispute. Second, the losing party should bear the prevailing party's reasonable attorney fees. This discourages frivolous claims.

In the event of a dispute arising under this Agreement, the parties shall first attempt to resolve the matter through informal negotiation for a period of 30 days. If unresolved, the dispute shall be submitted to mediation administered by [mediation service] in [Your City, State]. If mediation fails, the dispute shall be resolved through binding arbitration in [Your City, State] under [arbitration rules]. The prevailing party shall be entitled to recover reasonable attorney fees and costs. This Agreement shall be governed by the laws of the State of [Your State].

11. Termination Clause

Separate from the kill fee, the termination clause defines the mechanics: who can terminate, how much notice is required, and what happens to work-in-progress.

Either party should be able to terminate with written notice -- typically 14 to 30 days. This protects you too. If the client becomes abusive, unresponsive, or fundamentally changes the project direction, you need a clean exit.

Upon termination, payment for completed milestones is non-refundable. Work-in-progress is delivered upon payment. Any deliverables not paid for remain your property.

Either party may terminate this Agreement by providing 14 days' written notice via email. Upon termination: (a) Client shall pay for all milestones completed prior to the termination date; (b) payments for completed milestones are non-refundable; (c) Contractor shall deliver all completed work within 7 business days of receiving final payment; (d) Client shall return or destroy any Contractor confidential materials; (e) all provisions regarding IP, confidentiality, indemnification, and dispute resolution shall survive termination.

That last point -- survival clauses -- is easy to miss. Without it, your IP protections and liability caps evaporate the moment the contract ends.

12. Force Majeure

Before 2020, force majeure clauses were boilerplate filler. Then COVID shut down entire industries overnight. Projects paused indefinitely. Clients disappeared. Freelancers were left holding the bag on half-finished work with no recourse.

A force majeure clause protects both parties from liability when performance becomes impossible due to events outside anyone's control: natural disasters, pandemics, government actions, widespread infrastructure failures.

The key detail: define a time limit. If the force majeure event extends beyond 30-60 days, either party should be able to terminate without penalty, with payment for completed work.

Neither party shall be liable for failure to perform obligations under this Agreement due to events beyond reasonable control, including but not limited to natural disasters, pandemics, government actions, acts of war, labor disputes, or widespread infrastructure failures. The affected party shall notify the other party within 7 days of the event. If the force majeure event continues for more than 30 days, either party may terminate this Agreement with no further liability, except that Client shall pay for all work completed prior to the force majeure event.

Clauses to Never Accept

Not every clause belongs in a freelance contract, and some should trigger an immediate red flag. If you see any of the following in a contract a client sends you, push back before signing:

Unlimited revisions. There is no version of "revisions until satisfied" that doesn't end with you working for free. Every project gets a defined number of rounds. No exceptions.

Non-compete clauses. You are a freelancer, not an employee. A non-compete restricts your ability to earn a living in exchange for nothing. Decline it or charge a steep premium for a very narrow, very short version.

IP assignment for work created outside the project. Some contracts try to claim ownership of anything you create "during the term of this Agreement" rather than "under this Agreement." That's the difference between them owning the logo you designed for them and them owning the SaaS app you're building on weekends. Narrow the IP clause to specific deliverables only.

"Work made for hire" applied to everything. Work-for-hire is a specific legal designation. It should apply to the deliverables described in the scope of work -- not to your pre-existing templates, your proprietary process, or your tools. Always carve out your pre-existing IP.

Indemnification with no liability cap. If a contract asks you to indemnify the client for "any and all damages" with no ceiling, your exposure is theoretically unlimited. A $5,000 project should not carry $500,000 in potential liability. Cap it at 1x-2x the contract value.

The Template Framework

These 12 clauses form the skeleton of a complete freelance contract. In order, your contract should flow like this:

1. Parties -- who's involved, legal names, addresses
2. Scope of Work -- exactly what you're delivering
3. Timeline and Milestones -- when things happen
4. Payment Terms -- how much, when, and penalties for late payment
5. Revision Limits -- how many rounds, what counts
6. Intellectual Property -- who owns what, and when it transfers
7. Confidentiality -- mutual, time-limited, with portfolio carve-out
8. Non-Solicitation -- narrow, reasonable, no non-compete
9. Cancellation / Kill Fee -- what happens if the project dies
10. Indemnification -- mutual, capped at contract value
11. Dispute Resolution -- negotiation, mediation, then arbitration
12. Termination and Force Majeure -- how to exit cleanly

This isn't a template you can copy-paste into a Word doc and send to clients tomorrow. Every project is different. A $2,000 logo design and a $50,000 software build need different levels of detail in the scope, different milestone structures, and different liability considerations. But these 12 clauses should appear in every freelance contract you sign or send, adapted to the specific engagement.

What to Do With Contracts Clients Send You

Most freelancers don't send contracts -- they receive them. The client's legal team drafts the agreement, and the freelancer either signs it or negotiates from a position of uncertainty because they're not sure what's normal and what's not.

Here's the process:

First, run the contract through a checklist. Compare it against the 12 clauses above. What's included? What's missing? A contract that covers payment terms and IP but says nothing about revision limits or kill fees is a contract written to protect the client, not the relationship.

Second, flag any one-sided language. Indemnification that only protects the client. Confidentiality with no end date. Termination that lets the client walk away with no compensation for your completed work. These aren't deal-breakers by themselves, but they need to be addressed before you sign.

Third, negotiate before you sign, not after. The time to add a liability cap or a revision limit is during the contract review. Once you've signed, you've agreed. "I didn't realize what that clause meant" is not a legal defense.

Tools like Clausely exist to make this faster. Upload the contract, get a clause-by-clause analysis, and see exactly what's missing or lopsided. But whether you use a tool or go through it manually, the important thing is that you actually review client contracts against a standard -- not just skim them and hope for the best.

For a deeper look at the specific clauses that cause the most financial damage, read our guide on freelance contract red flags. You can also download our freelance service agreement template and freelance NDA template as starting points. It covers the five clauses that have cost real freelancers real money, with the exact scenarios and dollar amounts.

Your Contract Is Your Business Insurance

Every freelancer invests in their craft. You buy equipment, software, courses. You build your portfolio. You spend years developing expertise. But the single most valuable asset in your freelance business isn't your skill -- it's your contract.

A well-written contract costs nothing to produce and protects everything you've built. A poorly written one -- or worse, no contract at all -- can cost you thousands in unpaid invoices, stolen IP, and legal fees.

The 12 clauses in this guide aren't theoretical. They're the product of thousands of freelancer experiences: projects that went sideways, payments that never came, IP that got claimed, and careers that got restricted. Every clause exists because someone learned the hard way that it was missing.

Write your contracts well. Review client contracts carefully. And never, under any circumstances, start work without a signed agreement that protects your time, your money, and your work.