A generic freelance contract template is better than no contract. But most templates online were written for someone else's situation — different project types, different jurisdictions, different risk tolerances — and signing one as-is often just trades one problem (no contract) for another (bad contract).
This guide does two things: it gives you the full text of a solid baseline freelance contract, and it tells you exactly which parts to customize before you use it. Every clause that needs your attention is flagged. Every default that commonly bites freelancers is explained.
The goal isn't the most comprehensive contract ever written. It's the minimum viable contract that actually protects you — without being so long that clients refuse to sign it.
Already have a contract to review?
Pactly reviews any contract in 30 seconds — flags risks, explains clauses, and tells you what to push back on. Free, no account required.
Upload your contractWhy Most Free Templates Need Editing
The contract templates that rank well on Google are usually either too sparse (a 1-page document that offers essentially no protection) or pulled from a US legal database with jurisdiction-specific language that doesn't apply to freelancers working internationally.
The three most common template problems:
- Generic scope language — "services as agreed upon" is meaningless and scope creep will eat you alive
- No kill fee — client cancels project, you walk away with nothing for work already done
- IP assignment with no carve-out — signs over ownership of tools and frameworks you use on every project
None of these require a lawyer to fix. They just require knowing where to look — which is what this guide is for.
The Template: Section by Section
What follows is a complete freelance services agreement. Each section includes the template text, what it means, what to watch for, and what to change to fit your situation.
Parties & Effective Date
This section identifies who the contract is between. Simple, but a few details matter.
This Freelance Services Agreement ("Agreement") is entered into as of [DATE] ("Effective Date") between [CLIENT FULL LEGAL NAME], a [state/country] [corporation/LLC/individual] ("Client"), and [YOUR FULL LEGAL NAME / BUSINESS NAME] ("Freelancer").
Use the client's legal entity name, not a trading name. If you're signing with "Acme Design" but the legal entity is "Acme Digital, LLC" — use the LLC. It matters if you ever need to enforce the contract. Also: if you operate under a business name (sole trader, LLC), use that entity name for yourself, not just your personal name.
Contracts that don't specify a legal entity for the client — just a person's name with no company information. If the project is large, ask for the full legal entity. Suing a person is much harder than suing a company.
Scope of Work & Deliverables
This is the highest-value clause to customize. Vague scope = unpaid overtime.
Freelancer agrees to provide the services described in Exhibit A ("Services"), attached hereto and incorporated by reference. Freelancer will deliver the specific outputs listed in Exhibit A ("Deliverables") by the dates specified therein. Any services or deliverables not explicitly listed in Exhibit A are outside the scope of this Agreement and require a written Change Order signed by both parties.
Write Exhibit A yourself — don't let it be blank or reference a vague "project brief." List every specific deliverable: "3 responsive landing page designs (desktop + mobile) for pages: Home, About, Pricing," not "website design services." Include: number of revision rounds, file formats on delivery, and what "done" looks like. The more specific, the less room for dispute.
"Services as reasonably requested" or "ongoing support as needed" without a defined hour cap or scope boundary. These phrases are an open invitation for scope creep. Push to replace with explicit deliverables or a capped hourly rate with weekly approval.
Payment Terms
Cash flow depends entirely on this section. Net 60 on a $15,000 project means waiting two months to see your money.
Client shall pay Freelancer [TOTAL FEE] for Services rendered under this Agreement. Payment structure: [DEPOSIT %] deposit due upon signing; remaining balance due within [NET DAYS] days of final delivery. Invoices unpaid after the due date will accrue interest at 1.5% per month (18% annually) on the outstanding balance. If Freelancer must engage a collection agency or legal counsel to recover overdue amounts, Client shall reimburse all associated costs.
Set the deposit to at least 25–50% for any project over $2,000. For ongoing retainers, bill monthly in advance — never in arrears. Net 14 or Net 30 is standard; push back on anything longer. Include the late fee clause exactly as written — it rarely applies, but it incentivizes timely payment. If payment terms are already weak, our late payment guide has the full recovery playbook.
"Upon Client's satisfaction" or "upon project completion" with no definition of completion. This hands the client veto power over when you get paid. Replace with milestone-based or date-based triggers that don't depend on client approval of subjective quality.
Get the template + customization checklist
We'll email you a complete contract template as a Google Doc you can copy and edit. Plus a one-page checklist of every clause that needs your attention. Free.
Intellectual Property & Ownership
IP clauses determine who owns what you create — and critically, whether that includes the tools and frameworks you built your career around.
Upon receipt of full payment, Freelancer assigns to Client all right, title, and interest in the Deliverables specifically listed in Exhibit A ("Assigned Work"). Freelancer retains all rights to: (a) any pre-existing intellectual property, tools, code libraries, frameworks, or methodologies used in creating the Deliverables ("Background IP"); and (b) general skills and knowledge acquired during the engagement. Freelancer grants Client a non-exclusive, perpetual license to use any Background IP incorporated into the Deliverables solely as part of those Deliverables.
The "Background IP" carve-out is the critical piece — it protects your code libraries, design systems, and frameworks. If you build a custom tool or component library during the project, decide upfront whether it's Background IP (you keep it) or a Deliverable (they own it). Get it in writing either way. Never let "all work product" language slide through without this carve-out.
"Work made for hire" language. This is an employment law concept that makes the client the legal author of your work, stripping your moral rights and all future claims — including portfolio rights. It belongs in employment contracts, not freelance agreements. Push to replace with "assignment upon full payment" language like the template above.
Termination & Kill Fee
The most overlooked clause. When a client cancels — and some will — this determines whether you get paid for work already done.
Either party may terminate this Agreement upon [14] days' written notice. In the event of termination by Client for convenience: (a) Freelancer shall be compensated for all work completed and accepted to date, calculated at the pro-rata contract rate; and (b) a cancellation fee of [25%] of the remaining contract value ("Kill Fee") shall be immediately due and payable. In the event of termination by Freelancer due to Client's material breach (including non-payment), the full contract balance becomes immediately due.
The kill fee percentage (25% is standard; some freelancers use 50% for rush projects or clients with a history of cancellations). The notice period — 14 days is reasonable for most projects; longer for large retainers. For fixed-price projects, also add: "work in progress at time of termination shall be delivered to Client within 5 business days."
"Client may terminate at any time for any reason. Upon termination, Freelancer forfeits all rights to unpaid compensation." This is the worst possible termination clause — it lets the client walk away from a 90%-complete project without paying for it. Non-negotiable: you get paid for work done, full stop.
Liability & Indemnification
This section limits your financial exposure if something goes wrong. Without a liability cap, you could theoretically be on the hook for far more than you earned.
In no event shall Freelancer's total liability to Client exceed the total fees paid by Client under this Agreement in the [3] months preceding the claim. Neither party shall be liable for indirect, incidental, consequential, or punitive damages. Client agrees to indemnify and hold harmless Freelancer from any third-party claims arising from Client's use of the Deliverables beyond the scope of this Agreement.
For short projects, change "3 months preceding the claim" to "the total fees paid under this Agreement." This caps your liability at what you actually earned on the project — a completely reasonable ask for most freelance work. If you're working in high-stakes domains (healthcare, finance, legal tools), consider professional liability insurance before taking on clients who want to remove this cap.
Unlimited indemnification language — "Freelancer shall indemnify Client against any and all claims, losses, damages, and expenses." Combined with no liability cap, this could expose you to costs wildly disproportionate to your fee. Always pair any indemnification clause with a clear liability ceiling.
6 Clauses That Need Your Attention Before Signing
- §1 Parties — confirm the client's legal entity name, not just a person's name
- §2 Scope — list every specific deliverable in Exhibit A; don't leave it vague
- §3 Payment — minimum 25% deposit; Net 14–30; include a late fee clause
- §4 IP — carve out your Background IP; delete "work made for hire" language
- §5 Termination — always include a kill fee; always get paid for work done
- §6 Liability — cap your total exposure at total fees paid
When to Use Pactly's Demo Contracts as Your Starting Point
If you'd rather start from a real-world example than a blank template, Pactly pre-loads a set of actual freelance contracts you can browse for free. They're not invented for this article — they're the kinds of agreements freelancers actually sign (and occasionally regret signing).
The demo contracts cover design agreements, development contracts, and consulting agreements. Each one is AI-analyzed, with every risk clause flagged and explained. It's a faster way to understand what a real contract looks like before you start editing your own template.
Browse the demo contracts →Once you've seen what real contract language looks like, go back to your template with a clearer eye for what "normal" is and what's a red flag.
The One Template Change That Matters Most
If you only customize one thing before using this template: write Exhibit A yourself.
Scope is where 80% of freelance disputes start. A vague scope clause is the single most reliable predictor of a bad client experience. Every hour you spend writing a specific, unambiguous scope of work pays back double in avoided arguments and unpaid invoices.
Everything else in the contract — IP, payment, termination — is about limiting damage when something goes wrong. Scope is about preventing it from going wrong in the first place.
Upload a contract you're about to sign
Pactly flags every risk clause, explains the plain-English meaning, and tells you what to change. 30 seconds. Free.
Review your contract nowReady-to-use version of this template.
The complete freelance services agreement — with all 8 clauses, Exhibit A, and signature blocks — formatted and ready to print or save as PDF. Enter your email to download.