Freelance Contract Templates

Freelance Contract Templates: Real Examples, Clause-by-Clause

Stop guessing what goes in a freelance contract. Here are complete templates for 5 freelance niches — free to download, no signup required.

3 free downloadsNo signup requiredInstant download

5

niche contract templates

12

essential clauses covered

$0

free to download

3

downloads — no signup

Free Downloads — No Email Required

Three contract tools covering every situation. Click to download instantly — no account, no signup, no catch.

Freelance Contract Starter Kit

Complete starter contract with all 12 clauses filled in with real, usable language — plus 3 appendices: Scope of Work template, Change Order form, and Invoice template. Notes in [brackets] explain every section.

Download Free →

Contract Clauses Library

3 versions of every essential clause — Standard, Strict, and Client-Friendly — with guidance on which to use when. Includes counters for the 5 most common client pushback requests.

Download Free →

Niche Contract Addendums

5 niche-specific addendums for copywriting, design, web dev, social media, and consulting — covering usage rights, file formats, bug fix windows, account ownership, and scope-of-engagement boundaries.

Download Free →

Section 1: Why Generic Contracts Fail Freelancers

If you've ever searched "freelance contract template" and downloaded a random Word document, you already know the problem: it looks like a contract, but it doesn't actually protect you from the things that actually go wrong.

3 things every freelance contract must do

1. Protect scope. Define what you're delivering so precisely that there's no room for “I thought that was included.” Not categories — specific deliverables, formats, quantities.

2. Establish payment. Amount, schedule, method, and what triggers each invoice. Tied to IP ownership so you retain leverage until you're paid.

3. Own your work. Your work product belongs to you until the client pays in full. IP transfers upon payment — not upon delivery. This is your most important leverage point.

The contract paradox

Clients who push back on your contract are the ones who need it most. A client who objects to a kill fee is the client who will cancel mid-project. A client who wants to remove the late payment clause is the client who will pay late. A client who won't sign anything is the client who will dispute payment at the end. The resistance to the contract is the contract telling you something. Don't ignore it.

5 freelance contract mistakes that cause real problems

1
No revision limits. “2 rounds of feedback” becomes 14 rounds of feedback when it's not in writing. The contract is the only thing that makes revision limits real.
2
No kill fee. A client who cancels after 3 weeks of work owes you nothing except your deposit — unless you have a kill fee clause.
3
Vague deliverables. “Website design” is not a deliverable. “5-page responsive website with homepage, about, services, portfolio, and contact — excluding copywriting” is a deliverable.
4
No IP assignment clause. Without this, ownership of the work is legally ambiguous. Tie IP transfer to payment — not to delivery.
5
No late payment clause. Clients pay late because there's no consequence for it. 1.5%/month interest and a work stoppage right change the calculation immediately.

Section 2: The 12 Essential Clauses — Clause-by-Clause

Every clause below addresses a specific problem freelancers encounter. Skip one and you've left a gap a difficult client will eventually find. For each clause: what it does, why it matters, example language, and the red flag to watch for.

01

Scope of Work

What it does: Defines exactly what you will and won't deliver.

Why it matters: Vague scope is the #1 cause of scope creep. 'A website' vs '5-page WordPress site: Home, About, Services, Portfolio, Contact' — these are entirely different contracts.

Example: "Freelancer will deliver: (1) a 5-page responsive WordPress website as specified in Exhibit A. Work not listed in Exhibit A requires a signed Change Order before commencement."

Red flag: A client who resists specifics — "just make it good" — is a scope creep risk. Pin them down before you start.

02

Timeline & Milestones

What it does: Sets project dates and ties milestones to payment.

Why it matters: Without milestone dates, there's no deadline pressure — for either party. Milestone payment triggers also give you leverage if a client goes quiet.

Example: "Project start: [DATE]. Milestone 1 (draft) due [DATE], payment $X due. Final delivery [DATE], final payment due. Client delays exceeding 5 business days in providing materials or approvals will extend the timeline accordingly."

Red flag: A contract with no dates or "ASAP" as a deadline. You need specific dates to invoice on time.

03

Revision Limits

What it does: Caps the number of included revision rounds at a specific number.

Why it matters: Without this, every client believes revisions are unlimited. One round of revisions can become ten. Specify rounds, consolidation requirement, and the cost of additional rounds.

Example: "2 rounds of revisions included. Revision requests must be submitted as a single consolidated list within 7 days of delivery. Additional rounds billed at $[RATE]/hour."

Red flag: "Unlimited revisions until you're happy" — never agree to this. It has no endpoint.

04

Kill Fee

What it does: Compensates you if the client cancels after work has begun.

Why it matters: Without a kill fee, a client can cancel after 3 weeks of your work and owe you only the deposit. Standard kill fee: 25–50% of the remaining balance.

Example: "If Client cancels after work begins, Client will pay for all work completed to date plus a kill fee of 25% of the remaining project balance."

Red flag: A client who insists on removing the kill fee entirely — they're planning an exit before the project starts.

05

Payment Terms

What it does: Specifies the total fee, schedule, payment method, and what triggers each invoice.

Why it matters: Ambiguous payment terms lead to late invoices, payment disputes, and awkward conversations. Specify amounts, dates, and methods so there's nothing to interpret.

Example: "Total fee: $X. 50% ($X) due upon signing before work begins; 50% ($X) due on delivery of final files. Final files will not be released until full payment is received."

Red flag: "We pay on net-60." For freelancers, 60-day payment terms mean you might not get paid until 2 months after delivery. Push for net-14 or net-30.

06

Late Payment Clause

What it does: Creates a financial consequence for late payment and gives you the right to stop work.

Why it matters: Without a late payment clause, clients know there's no penalty for paying whenever they get around to it. 1.5%/month (18% annually) is the standard commercial rate.

Example: "Invoices unpaid after 30 days accrue interest at 1.5% per month. Freelancer may suspend all active work until overdue balances are settled."

Red flag: A client who tries to remove the late payment clause — they're anticipating paying late.

07

IP Assignment

What it does: Specifies who owns the work — and when ownership transfers.

Why it matters: IP tied to payment is your single biggest leverage point. Until they pay, you own the work. Once they pay, it's theirs. This prevents delivery-then-ghost situations.

Example: "Upon receipt of full payment, Freelancer assigns all intellectual property rights in the final deliverables to Client. Until full payment is received, Freelancer retains all rights."

Red flag: A client who wants IP to transfer at delivery, not at payment — this removes your payment leverage. Hold the line here.

08

Non-Disclosure

What it does: Keeps business information confidential for both parties.

Why it matters: If you have access to client strategy, financials, customer data, or unreleased products, you both need this protection. Make it mutual — it should cover both directions.

Example: "Both parties agree to keep confidential all non-public information received from the other party and to use it only for the purposes of this Agreement."

Red flag: An NDA that only covers the client — you need protection for your pricing, processes, and client lists too.

09

Non-Solicitation

What it does: Prevents the client from directly hiring your subcontractors.

Why it matters: If you bring in subcontractors to help on a project, this clause stops the client from cutting you out and hiring them directly at your project's end.

Example: "Client agrees not to directly hire, engage, or contract with any subcontractors introduced by Freelancer in connection with this project for 12 months following its completion."

Red flag: Only necessary if you use subcontractors. Skip it if you work solo.

10

Independent Contractor Status

What it does: Clarifies that you are not an employee of the client.

Why it matters: This matters for taxes, benefits, and legal liability. Required in virtually every freelance agreement — protects you both.

Example: "Freelancer is an independent contractor, not an employee of Client. Freelancer is responsible for all taxes, insurance, and other self-employment obligations."

Red flag: A client who wants to control your hours, equipment, or methods extensively — that may constitute employment under tax law.

11

Termination

What it does: Establishes how either party ends the agreement and what's owed.

Why it matters: Without clear termination terms, ending a project becomes a dispute. Both parties need to know the notice period, what gets paid, and what gets delivered.

Example: "Either party may terminate with 14 days written notice. Upon termination, Client will pay for all work completed to date. Kill fee provisions apply if Client terminates without cause."

Red flag: A contract with no termination clause is a trap — if a client goes quiet, you have no defined path out.

12

Governing Law

What it does: Specifies which state's laws govern disputes.

Why it matters: If you and the client are in different states, this matters. Always choose your own state — you know the courts and it's more convenient for you if disputes arise.

Example: "This Agreement is governed by the laws of the State of [YOUR STATE]. Disputes will be resolved by binding arbitration in [YOUR CITY]."

Red flag: A contract that specifies the client's state, especially if they're in a different country. Push back to your own jurisdiction.

Download #1 has all 12 clauses with real, usable language — plus notes in [brackets] explaining each section and 3 appendices (Scope of Work, Change Order, Invoice template). Download the starter kit →

Section 3: 5 Niche Contract Templates

A copywriting contract is not the same as a web development contract. Each niche has specific risks and deliverable types that generic contracts don't cover. Here's what's different in each.

✍️ Copywriting & Content

Niche-specific clauses:

  • Usage rights matrix — web, print, social, paid ads, or full commercial rights
  • Exclusivity clause — will you refrain from writing for direct competitors?
  • Ghostwriting clause — client publishes under their own name, Freelancer agrees not to claim credit
  • Word count ranges per deliverable and how overages are handled
  • Fact-checking responsibility — client reviews for accuracy before publication

Biggest risk in this niche: Unlimited revisions on subjective creative work. Lock in revision rounds and tie them to the stated brief — not to 'until you love it.'

🎨 Graphic Design

Niche-specific clauses:

  • File format delivery spec — exactly which files you'll deliver (PDF, PNG, SVG, AI source, etc.)
  • Source file policy — whether editable files are included or cost extra
  • Font licensing notice — client is responsible for purchasing web/print font licenses
  • Revision tracking sheet — requires consolidated revision requests, not piecemeal feedback
  • Proofing responsibility — client signs off on all text accuracy before final production

Biggest risk in this niche: Font licensing liability. You licensed the fonts for design; if the client uses them in digital products or printed goods, they need their own licenses. Put it in writing.

💻 Web Development

Niche-specific clauses:

  • Bug fix window — typically 30 days post-launch for defects in implemented features
  • Browser/device compatibility scope — exactly which browsers and screen sizes you'll support
  • Hosting and maintenance exclusion — deployment, security, and updates after launch are client's responsibility
  • Third-party API disclaimer — you're not responsible if a third-party service changes after delivery
  • Definition of 'bug' vs. 'new feature' — prevents scope creep under the guise of bug reports

Biggest risk in this niche: Clients confusing a post-launch bug fix with a new feature request. A bug is a defect in agreed functionality. A new request after launch is a new contract.

📱 Social Media Management

Niche-specific clauses:

  • Platform access protocol — how you access accounts (scheduling tool, credentials, or manager access)
  • Posting frequency spec — exactly how many posts per week per platform
  • Account ownership clause — accounts belong to client at all times; access returns within 2 business days of termination
  • Content approval workflow — calendar submitted X days ahead; silence = approval after review window
  • Performance disclaimer — algorithm changes and market factors are outside your control

Biggest risk in this niche: Account ownership disputes. Make it explicit from day one: the accounts, followers, and brand belong to the client. Your access is a service, not ownership.

📊 Consulting & Strategy

Niche-specific clauses:

  • Advice-not-advice disclaimer — you're not a licensed attorney, CPA, or financial advisor
  • Scope-of-engagement boundary — what you advise on and what you explicitly don't
  • Deliverables vs. advice distinction — tangible documents vs. strategic recommendations
  • Narrow non-compete parameters — limited to named direct competitors, not the whole industry
  • Confidentiality of strategic plans — client's proprietary strategies stay confidential; general frameworks are yours

Biggest risk in this niche: Liability for recommendations. A good consulting contract limits your liability to fees paid and makes clear that client owns all business decisions — you advise, they decide.

Download #3 has all 5 niche addendums — complete addendum documents for each niche that bolt on to your base contract. Download the niche addendums →

Section 4: The Negotiation Conversation

Sending a contract isn't the end of the process — clients sometimes push back. Here's how to read what they're actually saying, hold firm on what matters, and know when to compromise.

3 clauses clients try to change (and how to hold firm)

1. “Can we remove the kill fee?”

What they mean: “I want to cancel without consequence.”

Counter: “The kill fee protects my time investment, which starts before you see any deliverables. I can reduce it from 25% to 15%, but I can't remove it entirely. Here's what I can offer: if you cancel within the first 48 hours for any reason, there's no kill fee at all.”

2. “Can we do full payment at the end?”

What they mean: “I don't want to commit money before I see the work.”

Counter: “I structure payment as 50/50 so we're both invested. The deposit is how I block time exclusively for your project. If 50% feels like a lot, I can do 40% to kick off and 60% on delivery — but I can't start without a deposit.”

3. “Can we get unlimited revisions?”

What they mean: “I'm worried I won't like the result.”

Counter: “I can increase included rounds from 2 to 3 — that covers most projects thoroughly. ‘Unlimited’ isn't actually helpful for either of us; defined rounds keep us both on track. I'll also make sure we align on direction before I start, which solves most revision concerns at the source.”

When to walk away vs. compromise

Compromise on: Kill fee percentage (25% to 15% is fine), number of revision rounds (+1 is reasonable), payment timing (net-14 to net-30 is acceptable), governing state (if the client is same-country, their state is workable).

Hold firm on: IP tied to payment (non-negotiable), deposit requirement (never start without one), kill fee existing at all, some form of revision limits, your state for dispute resolution.

Walk away if: They want IP to transfer without full payment, refuse any deposit, want no kill fee and no termination clause, or refuse to sign anything in writing. These aren't negotiation positions — they're warning signs.

The paper trail principle

In every dispute, the hierarchy of evidence is: written contract > signed email agreement > email record > text/DM record > verbal agreement > nothing. If a client changes scope, moves a deadline, or requests something new verbally, follow up in writing: “Just confirming our call — you'd like to add [X] to the project. I'll send over a Change Order covering scope and cost.” The paper trail is your protection if anything goes sideways later.

Section 5: Contract Tools and Workflow

A good contract tool makes the process professional and frictionless for both parties. Here's the practical workflow from draft to signed.

Best free tools for sending contracts

HelloSign / Dropbox Sign: Free tier allows 3 documents/month. Clean interface, legally binding, both parties get a copy. Best for most freelancers starting out.

DocuSign: Industry standard. Free trial, then paid. Worth it if you send more than 3 contracts/month.

Adobe Sign: Included in Creative Cloud plans. Good if you're already paying for Adobe.

PDF + email: Send a PDF, client prints, signs, scans, and emails back. Clunky but legally valid. Use a password-protected PDF to prevent edits.

The 3-step contract workflow

1
Send. Send the contract as a formal step after scope and price are agreed. Include a short note: “Here's the agreement for [PROJECT] — please review and sign. Let me know if you have any questions.” Follow up after 48 hours if unsigned.
2
Countersign. Once the client signs, you sign. Both parties get a copy automatically via most digital signature tools. This is the moment the contract is binding.
3
Save. Store all signed contracts in one place with a consistent naming convention: [ClientName]_[ProjectName]_[YYYY-MM-DD]. You'll want to find these quickly if something comes up later.

When to hire a lawyer vs. use a template

Use a template: Projects under $10,000, standard freelance services, clients you've worked with before, standard deliverable types.

Get a lawyer involved: Projects over $10,000, international clients with complex IP implications, projects involving regulated industries (healthcare, finance, legal), any contract where a client asks you to sign their agreement instead of yours — have a lawyer review theirs.

The templates on this page are designed to be solid starting points for most freelance situations. They're not a substitute for legal advice on complex matters.

New to freelance contracts? The contract guide covers the general principles — why contracts matter, what happens when you don't have one, and the core 8 clauses every agreement needs. Read the freelance contract guide →

What happens when scope creep happens despite a good contract? The scope creep guide covers scripts, Change Order procedures, and exactly what to say when a client asks for more. Read the scope creep guide →

Clients who refuse to sign = red flag. See the full list of pre-project warning signs before you commit. Read the client red flags guide →

All 5 niche contract templates are in SoloStack

SoloStack has all 5 niche contract templates plus 45+ other done-for-you business templates for freelancers — proposals, SOPs, client onboarding, scope creep scripts, invoices, and more.

$19/month · Cancel anytime · Instant access

Frequently Asked Questions

Do I really need a contract for small projects?
Yes — and ironically, small projects are where freelancers skip contracts most often and get burned. The dollar amount doesn't determine whether a client will dispute payment or request endless revisions; the absence of a clear agreement does. A 1-page contract covering scope, payment, and revision limits takes 15 minutes to write and prevents the most common freelance disputes at any project size. The $200 project that turns into a 3-month nightmare almost always had no contract.
Can I use a contract template I found online?
You can start with one, but you need to understand every clause before you send it. Many generic freelance contracts from the internet have outdated language, missing clauses, or are written for a different legal context (wrong country, wrong industry). The most important thing: make sure the contract covers scope, payment tied to IP, revision limits, a kill fee, and governing law — those are the clauses that matter most in practice. The templates on this page are written for U.S.-based freelancers and are designed to be readable, not just legally dense.
What if the client won't sign a contract?
Don't start work without one. A client who refuses to sign a basic freelance agreement is the client who needs the agreement most — they're signaling they want the flexibility to dispute, change direction, or disappear without obligation. The professional response: 'I work exclusively with signed agreements — it protects both of us and sets us up for a smoother project. Here's a simple one-pager that covers the essentials.' If they still refuse, that's your answer. See the freelance client red flags guide for more context.
Do freelance contracts hold up in court?
Yes — a clear written agreement signed by both parties is a binding contract. You don't need a lawyer to draft it; you need it to be specific, signed, and not contradicted by other communications. Courts favor clarity: the more specific your scope, payment terms, and deliverables, the stronger your position. In practice, most freelance disputes never reach court — having a contract usually resolves the dispute before it gets there, because both parties can see clearly what was agreed. For projects over $10,000, having an attorney review the contract is worth the investment.
How do I send a contract professionally?
The most professional approach: use a digital signature tool (HelloSign/Dropbox Sign, DocuSign, or Adobe Sign all have free tiers), send a clean PDF, and follow up if it's not signed within 48 hours. Don't attach the contract as a casual mention — send it as a formal step: 'Here's the agreement for [PROJECT NAME] — please review and sign at your convenience. Let me know if you have any questions.' Once signed, both parties get a copy. Store yours in a folder by client and date. The second most professional approach (if you're starting out): email a PDF, ask them to sign and return, and keep the signed copy. Avoid Word documents — they can be edited after signing.

Every Contract Variation Your Business Will Ever Need.

SoloStack members get 50+ done-for-you templates for invoices, proposals, contracts, SOPs, and more — plus a new pack every month.

Get the Full Template Library

Ready to send your first professional contract?

Download the starter kit above, or get the full niche template library — plus 45+ other done-for-you freelance business templates — inside SoloStack.

Instant access. Cancel anytime.