When a freelance client steals your work, it usually doesn’t look like a dramatic heist. You find your work live somewhere. Or you see your rejected concept in their new campaign. Or they use the deliverable, go silent on the invoice, and somehow that becomes the arrangement. The specific form varies, but the pattern is consistent: a client has taken something that wasn’t theirs to take, and you’re now trying to figure out what you can actually do about it.
The honest answer is that your options depend heavily on what your contract says, what jurisdiction you’re in, and how much this is worth pursuing. None of those factors make the situation less infuriating. But understanding them prevents you from spending six months on a pursuit that was never going to pay out.
Who Owns the Work When a Client Steals It
In most jurisdictions, a freelancer retains copyright in their creative work by default until that copyright is explicitly transferred. “You did the work, so you own it” is the starting point. The transfer only happens through a written assignment, a verbal agreement that the client “owns” the work is generally not sufficient.
What this means in practice: if a client is using finished work they haven’t paid for, they are using work they don’t legally own. The copyright remains with you until the invoice is paid and the assignment clause in your contract is triggered. If your contract doesn’t have an explicit ownership transfer clause tied to payment, the situation is more complicated, but the principle still holds in many places.
Rejected concepts are a clearer case for freelancers. Work that was presented but not accepted was never purchased, never transferred, and never theirs. Using a rejected logo, a pitch concept, an early draft, any of these constitutes use of work the client had no right to without a separate agreement. This is one of the contract clauses worth understanding before you show anything to a client, specifying that rejected or unpurchased concepts remain the freelancer’s property eliminates ambiguity.
The exception that trips up many freelancers: work created under an employee relationship or an explicit work-for-hire agreement. If your contract uses “work for hire” language, the ownership may transfer automatically regardless of payment status, depending on your jurisdiction. This is one reason work-for-hire clauses deserve scrutiny before you sign.
The Three Scenarios and What They Require
Using finished work without paying. This is the most common form. You’ve delivered, they’ve used it, they’re not paying. The copyright argument is your first tool, they’re using work they don’t own. Before anything else, send a formal written notice (email is sufficient) stating that the work is being used without authorization, that copyright remains with you, and that continued use without payment constitutes infringement. This is not the same as filing a legal claim, it’s a demand letter, and it often produces a response when the previous invoice did not. Give them a specific deadline to pay or remove the work.
Using rejected concepts. Take screenshots and document everything before you make contact, dates, URLs, your original files with creation timestamps. Then send the same kind of written notice. If they dispute that the concept was “rejected,” your email trail from the project is your evidence. Most project communication includes the point at which a direction was not selected. Find it.
Claiming ownership they don’t have. Sometimes a client asserts ownership not by using the work but by claiming it in a contract addendum, a cease-and-desist to you, or simply by telling their network you had no rights. This is harder because it’s a dispute about the terms of the agreement rather than a clear use of your work. The response is still written and specific: “Our agreement does not include an ownership transfer clause, and no such transfer has occurred. The work remains my intellectual property.”
What Your Options Actually Are
Cease and desist letter. A formal cease-and-desist from a solicitor or lawyer carries more weight than your own email and signals you’re serious. In many cases, this alone resolves the situation, the client removes the work or pays the invoice to avoid escalation. Costs vary by jurisdiction but is often the most cost-effective first step if a direct email hasn’t worked.
DMCA takedown (where applicable). If the work is being used online and the platform is subject to DMCA rules, you can submit a takedown notice without going through a lawyer. This is specific to online use and doesn’t address the underlying payment issue, but it removes the work from the web, which is sometimes sufficient use to prompt payment.
Small claims or civil court. If the amount is within the small claims threshold in your jurisdiction, this is often the most practical legal route for individual freelancers. The process is designed for non-lawyers and the fees are relatively low. The downside: it takes time, it requires you to be in the right jurisdiction relative to the client, and winning a judgment doesn’t guarantee payment. Many freelancers win and then spend additional time enforcing the judgment.
Platform dispute (if applicable). If the project was through a platform that holds payment in escrow or has dispute resolution, file the dispute through that system. This is the fastest and most reliable route for platform-based work.
What’s Realistic
The difficult truth: the practical value of pursuing a work theft case depends on the amount involved and the client’s location relative to yours. If the dispute involves payment rather than copyright specifically, the process for handling a freelance client dispute covers the escalation arc in more detail. Cross-border enforcement is genuinely hard for individual freelancers. A client in a different country using your work without paying is a real problem that may have no cost-effective legal solution.
For domestic cases below a few thousand dollars, small claims is usually the right call if a cease-and-desist letter hasn’t worked. Above that threshold, get a legal opinion before committing to litigation, the costs of pursuing it can exceed the amount at stake.
The situations most worth pursuing formally: work used at commercial scale (in an active advertising campaign, on a major platform), or cases where your portfolio is harmed by the misattribution or modification of your work. The situations least worth pursuing formally: small invoices, ambiguous contracts, clients in unreachable jurisdictions.
How to Prevent a Freelance Client From Stealing Your Work
The practical prevention is mostly contractual. Ownership transfer tied explicitly to full payment. A clause specifying that rejected or unpresented concepts remain the freelancer’s property. No physical delivery of final files until payment clears, watermarked proofs are the standard for visual work, and they exist precisely for this reason.
The behavioral prevention is recognizing the client red flags that correlate with work theft: clients who want all the files before approving the final invoice, clients who pressure you to skip the contract, clients who ask for extensive unpaid samples or spec work as part of the pitch process. Spec work requests and work theft often come from the same category of client.
If this has already happened to you once, the contract is what you fix before the next project, not the specific client. The clause is a standard provision, not a statement of distrust. Most clients who work professionally will not blink at an ownership-on-payment clause, it’s normal. The ones who push back on it are telling you something about how they view the arrangement.