Quick Answer
US fair use is a case-specific assessment of all four statutory factors. Paid work can qualify, but credit, a fixed copying percentage or a client approval does not establish fair use. Document the exact use and reasoning, then obtain permission or replace the asset if the basis remains unclear.
Assess fair use in paid client work#
If you use third-party material in paid client work, make the call based on sources you can defend, not myths. This guide gives you a practical go-or-no-go path and a permission fallback when support is weak.
Start with the US Copyright Office fair-use guidance. It explains the four factors and why no fixed amount of copying guarantees a fair result.
Keep a simple record in your project file:
- what source you relied on
- when you checked it
- which path you chose: analysis, permission, or replacement
Keep scope explicit. This guide is U.S.-anchored. Use U.S. fair-use materials as your starting point, then pause on cross-border work and confirm which terms and approvals apply to the engagement.
That is a risk checkpoint, not a full legal conclusion. If a project involves another country or worldwide rights, flag that in writing before delivery and get explicit confirmation on the rights path.
Do not skip the paper trail. If questions come up later, dated notes and approvals give you a clearer record than memory.
Start with the legal baseline before tactics#
Before you get tactical, treat this as a rights check, not a creativity check. Review Title 17 first, then decide whether you have a defensible analysis path or should get permission.
Avoid rule-of-thumb calls like "under 10% is safe" or "a few lines is always fine." Copyright analysis is complex and situation-based, so your decision has to match the specific use, context, and output.
Treat attribution as good practice, not as your only checkpoint. Crediting a source can help with transparency, but it does not by itself answer whether a specific reuse decision is appropriate in your situation.
Also document implementation, not just intent. Teams may agree in principle and later disagree about how reuse appeared in the final deliverable. Save the source copy, what you used, your short purpose note, and the written approval or analysis memo. If that record is thin, move to permission, replacement, or professional counsel.
Decide early between fair use and permission#
Choose the path before you draft: proceed under the four-factor fair use test, request permission, or decline and replace the material. Fair use is case-specific, courts make the final call, and attribution alone does not protect against an infringement claim.
| Path | When it fits | Key checkpoints | Keep on file |
|---|---|---|---|
| Proceed under the four-factor fair use test | You can defend the use on specifics, not assumptions | Work through all four factors and pressure-test market-substitution risk before proceeding | Dated note with source, portion, purpose and reasoning across all four factors |
| Send a permission request | Facts are mixed, ownership is identifiable, or risk is unclear | You cannot confidently defend a fair-use position or market-substitution risk is uncertain | Written request and any written approval or scope terms you receive |
| Decline or replace source material | Risk is high, ownership is unclear, or timing is too tight to verify rights | Substitution risk appears high or rights cannot be confirmed in time | Internal decision note on what was removed or replaced and who approved |
If the facts are ambiguous and deadlines are tight, choose permission over assumption. If you cannot clearly defend the fair-use case, and you cannot secure permission in time, replace the material before publication.
If you need a cleaner way to document scope, approval, and rights assumptions before drafting, start with Gruv's freelance contract generator.
Apply the four-factor fair use test to paid client work#
In paid client work, treat fair use as a defense and use the four-factor fair use test as a documented risk check rather than a gut call. Commercial use can raise scrutiny, but it does not automatically fail factor one. If factor four suggests plausible market harm, pause and escalate for legal review before delivery.
Assess the actual use across all four factors. Section 107 lists examples of purposes that may qualify; the list is illustrative, and a purpose label alone does not decide the outcome.
Factor one#
Factor one looks at purpose and character, including whether the use is commercial. Ask what the client is actually paying for. If third-party material supports your analysis, commentary, or instruction, your position can be stronger than if it supplies the core value of the deliverable.
Do not rely on a single label as a shortcut. Your note should explain the actual purpose, the limited use, and why the client output is not a substitute for the original.
Factor two#
Factor two considers the nature of the original: creative or factual, published or unpublished. Factual and published works tend to present a stronger case than highly creative or unpublished works, but the factors must be considered together.
Watch for derivative-work risk in adapted creative assets. Copyright ownership includes the right to create derivative works, so repackaging or reworking expressive material for client use may point you to permission first.
Factor three#
Factor three examines the amount and substantiality used. There is no fixed word count or percentage that is always fair use. Ask instead whether you took only what was needed for this exact purpose.
Use a simple checkpoint: save the source copy, mark the exact portion used, and add one sentence on necessity. If you cannot justify each excerpt, crop, or frame, narrow it.
Factor four#
Factor four is market effect, and in paid work it is a direct risk checkpoint. Ask whether your use could affect the potential market for the original, including whether the client deliverable could replace the original or a licensed version.
| Scenario | Signals that help | Signals that hurt | Practical call |
|---|---|---|---|
| Short quotes in commentary | Used to analyze or respond; only needed passage used | Quote becomes core value of deliverable | May be supportable if tightly limited and documented |
| Screenshots in paid training | Used to explain a specific point; limited to learner need | Collection of screenshots functions as a substitute | Case-by-case; review amount and market effect closely |
| Reused creative assets adapted for client use | Use is limited and tied to direct discussion of the original | Asset is repackaged or lightly edited for client commercial use; may be derivative | May require permission first or replace with original material |
Treat this as a verification gate. If substitution is plausible, escalate for legal review before delivery or publication.
Use market substitution as an internal escalation trigger when deciding whether to publish. It does not replace the combined legal assessment of all four factors.
Build an evidence pack before you deliver#
If you plan to rely on fair use in paid client work, build a short evidence pack before handoff so the decision path is clear and reviewable.
Keep the file set small and usable. You do not need a long memo. A practical file can include:
- the source copy you reviewed, saved in the version and format you used
- a short purpose statement explaining what the deliverable does and why third-party material appears
- an excerpt rationale listing what you used and why each piece was necessary
- brief notes on your analysis and any comparison examples you relied on
Be specific. Save the exact file, screenshot, timestamp, or passage you used, and mark the exact excerpt in your draft.
Save ownership posture, not just the content. Do not stop at the content itself. Document what you checked about who controls the rights. Rights posture can be less obvious than the byline, including cases where a party claims rights as an exclusive licensee tied to a freelance creator.
If ownership is unclear, treat that as a stop signal and move to permission or legal review before delivery. The same goes for signs of derivative-use risk or possible removal of copyright management information.
Add a final sign-off before release. Before release, record who approved the use, when, for which asset, and under which path: fair use or permission.
If the path is fair use, note who accepted the risk call and why. If the path is permission, attach the written grant that matches the actual use. If you cannot identify the approver or the backing document, pause delivery.
For a step-by-step walkthrough, see DMCA for Freelancers in Client Content Disputes.
Use the permission path when risk is high#
If ownership is unclear or the use looks high-risk, move from a fair-use argument to permission before publication or handoff. The job here is straightforward: identify the likely rights holder, request the exact use, and release only when the written grant matches the deliverable.
Identify who can grant the rights you need. A registration record can supply a claimant lead; confirm authority and current ownership or license scope using relevant agreements and transfer records.
Section 408(a) concerns registration, not a mandatory clearance checklist. A work can be protected without registration, and permission does not depend on obtaining the claimant’s deposit copy or filing-fee trail.
A registration record can point to a claimant, but it is not automatic proof of current ownership in every dispute. If record details conflict with byline, publisher, platform terms, or client-provided facts, pause and request stronger chain-of-title support.
Send a permission request that leaves little room for ambiguity. A practical request can be narrow enough to approve or reject as written, rather than vague enough to invite confusion.
I'm requesting permission to use the following material: [identify the work and exact excerpt/asset].
Proposed use: [describe the client deliverable and purpose].
Format and channels: [website, PDF, email course, social post, paid ad, training deck, etc.].
Territory: U.S. only or worldwide (specify the agreed scope).
Duration: [one-time use / 12 months / perpetual].
Edits or adaptations: [none / crop, resize, annotate, excerpt].
Please confirm whether you control these rights and, if approved, reply with the terms and any required credit language.
This is a practical scope-control script, not a statutory form. Save the sent request, response, and exact asset version referenced.
Even if permission comes by email, make sure the writing matches the real use: material, use, channels, territory, duration, and limits on edits, sublicensing, or client transfer. If the client rights requested exceed the grant, stop and resolve the gap before handoff.
If permission stalls, use a controlled fallback. Do not ship with permission "pending." Use this order:
- Replace the asset with original, licensed, or public-domain material.
- Reduce the excerpt only after reassessing all four factors; a smaller amount is not automatic clearance.
- Remove the claim-dependent section if it depends on uncleared third-party material.
If there is no usable written grant, treat the asset as not cleared.
Put Indemnification Limitation of Liability and Termination in your contract#
Once a project includes third-party materials, your contract becomes a practical risk-control tool. It should say who handles claims, who pays if that fails, and how far liability goes.
Allocate risk clearly. Start with indemnification. It is a promise that one party covers the other party's legal costs and damages for specified claims, usually third-party claims. Here, precision matters. Define which claims trigger indemnity and the process for handling a claim.
If client-provided assets create the risk, say so directly.
Negotiate a liability cap and check its exclusions, whether it covers indemnity obligations, and enforceability under the applicable law. A cap allocates exposure between the contracting parties; it does not limit a third-party rights holder’s claim automatically.
Before you sign, confirm:
- how the cap is calculated (for example, total fees paid or a fixed amount)
- that the clause wording is clear enough to avoid ambiguity
Keep other key clauses explicit. If you include termination or IP terms, write them in plain contract language so responsibilities are clear.
If you need a deeper breakdown, see Work for Hire vs. Assignment of Rights: A Freelancer's Guide to Owning Your IP.
Set Governing Law Jurisdiction and Dispute Resolution before project kickoff#
If you and the client are in different countries, agree on governing law, jurisdiction, and dispute handling before kickoff, and put it in a signed written contract. Leaving venue vague can create avoidable disputes about where the contract is interpreted or enforced, because contract rules vary by jurisdiction.
Choose the law and forum on purpose. Name both governing law and jurisdiction in clear language. Governing law identifies which legal rules interpret the contract. Jurisdiction identifies where disputes are heard. In cross-border work, that choice can materially affect how enforcement plays out.
Set the escalation path in writing. Define what happens before formal escalation, in order:
- written notice of the dispute
- a negotiation window the parties agree to
- the next step if no resolution is reached
Written sequencing makes disputes easier to handle because the process is documented before pressure builds.
Keep terms consistent across contract documents. Before kickoff, confirm the same governing-law, jurisdiction, and dispute language is aligned across your contract documents. If enforceability is central to the deal, get country-specific legal review.
Spot red flags that require legal counsel#
Treat this as a stop-sign section: if rights or liability terms are unclear, pause and get legal review before you deliver files or sign.
Escalate when you see any of these:
- Unclear authority to use or transfer the asset, including conflicting ownership or license records.
- Vague or conflicting IP clauses, including work-made-for-hire or assignment terms.
- Indemnity obligations whose covered claims, defense process or relationship to a liability cap are unclear.
- An intended payment condition for rights transfer that is absent from the agreement. Do not assume payment automatically controls transfer.
If you want a quick ownership refresher before review, see Work for Hire vs. Assignment of Rights: A Freelancer's Guide to Owning Your IP.
Handle common freelancer scenarios with clear decision rules#
Use one rule for every third-party asset: ship it only with documented rights analysis, express written permission where required, or a replacement. That keeps the decision defensible when fair use is uncertain and treated as an affirmative defense.
| Scenario | Main risk | If X, do Y |
|---|---|---|
| Short quotes | No fixed word-count or percentage safe harbor is provided here | If you can document a rights basis for this exact use, proceed with a memo. If rights are unclear, request permission, escalate, or replace it. |
| Screenshots | Reuse may include protected visual elements you do not control | Assess the protected elements, exact purpose, amount and distribution. If the rights basis is unclear, seek permission, review or replacement. |
| Training slides | Client-ready materials can circulate beyond the original context | If third-party elements have documented rights status for the actual distribution context, proceed with a memo. If not, request permission, escalate, or replace. |
| Social snippets | Fast reuse can skip rights verification | If rights and scope are documented for this channel and audience, proceed with a memo. If not, request permission, escalate, or replace. |
| Adapted graphics | Adaptation can still reuse protected expression | If rights clearly cover the adapted use, proceed with a memo. If coverage is unclear, request permission, escalate, or replace. |
Two failure modes create late risk:
- Client-supplied assets without proof of rights. Treat these as unverified until the client provides clear documentation.
- Scope creep that changes how or where the asset is used. Recheck rights when channel, audience, or use context changes.
Review each third-party item before publication or handover. Record its rights basis and supporting documentation; escalate unresolved questions. An invoice-submission date may be too late if the material is already public.
Use client scripts that protect the deal and your downside#
Put the decision in writing every time: approved for current scope under fair-use analysis, permission required, or hold until the contract is fixed. Keep the wording narrow so you do not imply broader clearance than your documentation supports.
That protects the deal because fair-use outcomes are case by case, not automatic. It also reduces risk if the channel, audience, or commercial use changes later.
Script for approved use under fair-use analysis#
Use this only when your file has a documented four-factor analysis for the exact use in scope.
Our project file records a four-factor assessment for this asset and the current distribution. The named project owner has accepted the risk for this scope. This is an internal decision, not a guarantee of fair use. Recheck before changing the excerpt, channel, audience or reuse plan.
Before sending, confirm your file includes the source copy and factor-by-factor notes.
Script for permission required#
Use this when analysis is not strong enough for approval or the asset is too central to treat casually.
I cannot approve this asset on analysis alone for the current project. Please send a permission request to the rights holder covering the exact material and intended use, and copy me on the written response. Please confirm approval or choose a replacement by the project deadline so the project can stay on schedule.
Save the written response with your project records so the granted scope is clear.
Script for cannot proceed without contract fix#
Use this when rights-clearance responsibility is not clearly allocated in the agreement.
I cannot proceed with this third-party asset until the contract is updated. The agreement must clearly state who handles rights clearance and what happens if permission is missing, delayed, or disputed. Please send revised language, or confirm the agreement will be clarified before this asset is included in final deliverables.
Also recheck ownership clauses, licensing terms, and any work-for-hire language. If ownership or license scope is still unclear, pause and ask questions or negotiate before proceeding, or point the client to Work for Hire vs. Assignment of Rights: A Freelancer's Guide to Owning Your IP.
Closing script for acceptance and escalation#
Close the loop in writing so no one later argues there was implied approval.
Please reply confirming one of the following for the project file: approved under documented fair-use analysis for current scope, permission request in progress, replacement asset selected, or hold pending contract revision. If any rights or contract issue remains unresolved after your review, consider legal review before delivery.
The safest way to move fast on client work#
The safest way to move quickly is to make key scope and asset-usage decisions early, document them, and switch to permission or replacement when details are unclear. In paid work, that usually saves more time than fixing avoidable issues after production.
Decide before production, not during cleanup. Make the usage call at the statement of work, outline, or mockup stage. If a deliverable includes third-party text, images, screenshots, charts, or clips, flag each item and choose a path before execution. Proceed on your documented decision, request permission, or replace it.
Get written approval of the project vision before work begins. Keep that approval in the same file as your notes on what is being used, why it is included, and who approved it, so questions can be resolved quickly later.
Paper trail beats memory. Keep dated records of approvals, scope notes, and asset decisions in one place instead of relying on verbal sign-off.
If details are still unclear, pause early. That short pause is usually cheaper than rework at the end.
Put the decision into the workflow. Treat rights checks as part of delivery, not admin overhead. Your SOW or kickoff notes should make ownership and approval responsibilities explicit, and allow you to pause, replace, or remove material when proof is missing.
This matters most when assets are added after kickoff, because late additions are where rushed decisions usually show up.
Your next step. Use this checklist on your next project before kickoff:
- add an asset-check line to the SOW, outline, or mockup for each third-party asset
- require written approval of the project vision before production starts
- document who approves added assets and how delays are handled
Make rights review part of the next project’s scope and approval process. For ownership terms, see Work for Hire vs. Assignment of Rights.
After your process is in place, you can simplify invoicing and cross-border payouts where supported in one workflow with Gruv for freelancers.
Frequently Asked Questions
Can freelancers rely on fair use for paid client work?
Sometimes, but not as a blanket rule. Fair use is a flexible exception, and its boundaries can be unclear in practice. For paid client work, treat it as a case-by-case call for the specific use, with written notes to support that call.
How much can I copy before I need permission?
There is no fixed word count, percentage, or clip length that makes copying automatically safe. If you cannot clearly justify why that exact amount is necessary for your purpose, move to permission first.
Does giving credit to the original source make use legal?
No. Credit can be good practice, but it does not replace permission, a license, or a defensible fair-use position. Copyright protection is automatic, so missing notice or registration does not mean a work is free to reuse.
Does a purpose such as commentary or parody automatically qualify?
No. Commentary, criticism and parody may support fair use, but a purpose label is not an automatic pass. Assess the actual use across all four factors, including the amount and market effect.
When should I stop and involve legal counsel?
There is no universal threshold that fits every project. Escalate when ownership, scope, or risk is unclear and your file cannot show a clear, defensible decision path. That is especially important in paid work, where disputes can become expensive.
What if the client says they own the rights but cannot prove it?
Ask for evidence of authority and license scope. If the rights basis remains unresolved, pause the asset, seek review or replace it. A contract amendment allocating responsibility does not itself supply permission from the rights holder.
What if the material is factual, like data or a list of dates?
Facts themselves are not subject to copyright, but creative expression usually is. You can use the underlying facts while avoiding copied wording or other creative expression from the source.
Is fair use a guarantee that I am safe if someone complains later?
No. Fair use can be raised as a defense if infringement is challenged, but it does not prevent disputes by itself. Keep your analysis and records organized, and switch to permission when the facts stay unclear.
Try a related tool
Researched and edited by the Gruv editorial team. Gruv builds cross-border billing, payouts, and finance-operations software for global businesses.
Sources
- copyright.gov/fair-usetrusted
- copyright.gov/title17/92chap1.htmltrusted
Educational content only. Not legal, tax, or financial advice.
Related Posts
Work for Hire vs Assignment of Rights for Freelancers
A freelance agreement is not just about price and scope. It decides who controls the rights in the work. If the ownership language is loose, rights can move earlier than you expect, cutting down your control once the work is delivered or used.
The Freelance Payment Penalty: A Modeled Audit of Platform Fees, FX Spreads, and Payout Delays
The money rarely disappears through a single, easy-to-spot fee. The real loss is stacked. A marketplace takes its commission, a processor adds a charge for international cards, a bank or payment company converts the currency at a spread, a platform holds the funds before release, and a wire sheds a little to intermediaries on the way in. Each layer looks defensible on its own, but the worker feels the combined result as a smaller deposit and a later payday.
How to Respond to a Subpoena for Business Records
Move fast, but do not produce records on instinct. If you need to **respond to a subpoena for business records**, your immediate job is to control deadlines, preserve records, and make any later production defensible.