Client Says Your Art Is AI and Won't Pay? What to Send

Send one calm written reply with three things: a plain statement that you drew the piece, a short folder of dated process files, and the invoice terms you already agreed. You will not win by arguing, but you can make the client's doubt checkable. Below is the reply to paste, the folder to build, and what to do if the job ran through a platform.

Whether you can hold files or collect depends on your contract and where you live, so read your own agreement before you act on anything here.

Reply once, in writing, and keep it flat

Do not answer the minute you read the message. Screenshot it, wait, then send a short reply that moves the client from "it feels like AI" to "here is a record I can check."

Template (the brackets are yours to fill):

Thanks for telling me. I drew this by hand over [number] sessions between [date] and [date]. Here is the record of the process: [link or attached folder]. If something specific looks wrong to you, tell me what it is and I will go through it with you. The invoice for [amount] is due on [date] under the terms we agreed.

Four lines, no heat, no threats. Offer one short call where you open the layered file and scroll through it. Keep every later message in writing and stick to dates, files and agreed terms, which is the same advice the Smashing Magazine guide to clients who refuse to pay gives for any payment dispute. A CGArchitect thread on a deadbeat client lands in the same place: keep records of approvals and keep the tone factual.

If you want a shorter version for the very first message, the five-minute "Is this AI?" reply is built for that moment.

Send five named files, not a mystery folder

A client who opens a folder called "stuff" will not read it. Name each item so a stranger can follow your work in order:

1. 01 brief and agreed terms. The contract or the email thread that sets scope and price.
2. 02 sketch and draft approvals. Messages with dates, showing the client saw early stages.
3. 03 time lapse. The full export, not a clip. The steps are in exporting the full Procreate video in four taps.
4. 04 layered file screenshots. Layer panel open, three or four stages.
5. 05 dated saves or version history. File dates, and version history if your app keeps it.

Put one line on top: "Everything below is dated and was made while I worked on your piece."

Count what you can fill. If you have at least three of the five, send them and say plainly which ones you do not have. Do not pad. If you are missing most of them, the fix for the next job is in what to save and when.

Pick your reply by what the client actually said

The client says	You do
"This looks like AI," nothing more	Send the five files once. Ask what they need to see to be satisfied.
Quotes a detector score	Do not argue about the score. Offer the dated process record instead.
Names a specific problem (a hand, a style, a face)	Treat it as a normal revision request, answered separately from the AI question.
Goes quiet after your evidence	One follow-up: restate the due date and where the files are. Then stay in writing.
You used a small amount of AI	Say so plainly. Never write "no AI" if that is untrue.

The follow-up line, as a template: "Checking in on the files I sent on [date]. If you need anything else to see how it was made, tell me what and I will send it. The invoice for [amount] stays due on [date] under our agreement."

Three moves that make it worse

• Sending a detector score of your own. A number that can swing either way hands the client something new to argue about. Send the process record.
• Posting the dispute, or the client's name, in public. It pulls the fight away from the evidence and makes a quiet settlement harder.
• Offering a discount before any evidence. It tells the client the doubt was fair.

Process files do work as an answer. When Japanese illustrator Araizumi was accused of using AI, the reply that settled it was videos and screenshots of the working files showing the process and separate layers.

If the job ran through a platform, the clock is already running

On Upwork fixed-price contracts, you have seven calendar days to review the payment details and submit a dispute, or the remaining funds go back to the client. The dispute needs a reason and details showing the work is complete. Mediation follows: a dispute specialist asks both sides for documents and proposes a resolution that is non-binding, so neither side has to accept it.

The rule: the day the client objects, open the platform's dispute page, find the window, and put the last day in your calendar.

Example: say you delivered a $450 illustration on October 6 and the client objects on October 9. Seven days from October 9 is October 16. Everything you want reviewed goes into the dispute form by then, not into a side chat the reviewer never sees.

Platform template (for the dispute form):

Contract [name], milestone [name], delivered [date]. The client objected on [date] saying the work looks AI generated. The attached folder shows the dated process: [list the five items]. I am happy to go through any item the client names.

Keep later messages inside the platform thread so they are on the record there. Off a platform, the written reply and the folder are your whole route.

Check your contract before you hold anything back

Many freelancers ask whether they can keep the final files until they are paid. Holding deliverables only works in practice when your agreement set that term at the start, as Ruul's guide to unpaid clients points out. You cannot invent it mid-dispute. If the files are already delivered, there is nothing to hold, and the folder and the invoice terms are your two tools.

A kill fee is a clause that sets an amount to be paid if a finished illustration is rejected, commonly 25 percent of the full fee. It exists only if your contract says so. Read your clause and quote it as written. Do not tell the client it applies.

Keep the working files until the invoice is settled. Deleting them after delivery removes the only proof you have.

Do this in the next ten minutes

Open a new folder for the job in question and create the five names above. Drop in whatever you already have. Then write down the date the client objected and the platform window, if there is one. You can send the reply tomorrow with a clear head. The folder is the part that cannot wait.

Make the next job easier to defend

The pattern is the same every time: the client has no way to check how a piece was made, so doubt turns into a hold on payment. The cleanest fix is a record created while you work, not rebuilt afterwards.

DrawDog is a menu bar app for Mac and Windows that runs while you work and records process metadata: session time, file growth, stroke frequency and app usage. It never records file contents, file names, keystrokes or screen contents. When the piece is done you send one link, and your client verifies it with no account and nothing to install. The certificate shows time spent, stroke count, AI tool percentage and a file fingerprint match. It is a record, not a legal document. The free tier covers three certificates per month, with no credit card.

Download DrawDog free

If you want proof that holds up before a client asks for it, read what a DrawDog certificate records or download DrawDog and seal your next piece as you make it.