ChatGPT Graphic Design Contract: Source Files + Licensing

For the cross-cluster comparison, see the Using AI to Generate Professional Freelance Documents complete guide.

You need something in writing before the logo project starts, so you ask ChatGPT for a graphic design contract. Ten seconds later you have a clean document with scope, fee, revisions, and an intellectual-property section. It reads like a real agreement.

The trouble is that a generic model does not know how design jobs actually go sideways. It promises to deliver all files on completion, so your editable source art goes out the door with the final export. It assigns the full copyright to the client when a usage license would have covered the fee. And it ties the handover to delivery instead of to payment, which is exactly how designers lose both the files and any bargaining power in one move. If you have ever watched a client walk off with your layered artwork after a half-paid invoice, one of those three defaults is what did it. This post gives you a designer-specific prompt, then the three clauses you rewrite before sending.

The prompt that drafts a designer's contract

Paste this into ChatGPT, Claude, or Gemini, using placeholders for the real client details.

You are an expert at drafting freelance graphic design contracts.
Draft a contract from the details below.

PROJECT: [e.g. "brand identity: logo, color system, 1 brand sheet"]
DELIVERABLES + FORMATS: [e.g. "final logo in PNG, SVG, PDF; brand
  sheet as PDF"]
TOTAL FEE + SCHEDULE: [e.g. "50% deposit, 50% on final delivery"]
REVISIONS INCLUDED: [e.g. 2 rounds, then billed hourly]
USAGE: [where the client may use it: e.g. "web + print marketing,
  worldwide, no resale or sub-licensing"]

Rules:
1. Source files: delivery covers the FINAL artwork in the formats
   above. Editable source files (.ai, .psd, .indd, .fig) are NOT
   included by default; offer them as a separate paid deliverable.
2. Rights: grant the Client a defined USAGE LICENSE (medium, territory,
   term, exclusivity) rather than assigning copyright. Full copyright
   assignment is a separate, priced "buyout" option only.
3. Transfer trigger: no usage rights and no files transfer until the
   Client has paid in full and funds have cleared.
4. Embedded assets: licensed fonts and stock carry their own licenses
   and are not transferred to the Client.
5. Plain English. Flag any clause that depends on my jurisdiction.

Output the contract, then list the decisions you made that I should
confirm.

The rules are doing the work. Strip them out and the model reverts to client-favorable boilerplate that gives away your files and your copyright in the same paragraph. Even with them, confirm the three clauses below, because they are the ones that cost the most when they are wrong.

Clause 1: source files are a separate deliverable, not a default handover

This is the clause designers lose sleep over. Generic AI writes something like "the Designer will deliver all files upon completion," which makes no distinction between the flattened final artwork and the layered, editable source file. Those are not the same asset. The export is the result; the source file is the machine that can rebuild and alter the design forever, which is why it is worth far more.

The industry default runs the other way from what the AI assumes. As Modern Species explains:

In almost all cases, the client owns the "final artwork", but the designer retains ownership of the working design files and all non-final design drafts.

Source: Modern Species, Why Designers Don't Give Up Their Files

So the contract should say delivery covers the final artwork in the agreed formats, and that editable source files are available as a separate paid deliverable if the client wants them. That is not a hardball move, it is standard pricing: Modern Species notes it is common for design firms to charge extra for the working files, at least 50%, if not 100% of the original project price. Another designer reports charging 25% to 100% of the project fee for native files, with the percentage shrinking as the project size grows. The exact figure is your call; the point is that handing over source art is a decision with a price, not a freebie the AI should bundle in silently. The full source-files and licensing guide covers how to tier this; here we are just making sure the prompt does not give it away.

Clause 2: license the usage, do not assign the copyright by default

Generic AI loves to write "the Designer assigns all rights, title, and interest in the work to the Client." That single sentence transfers your copyright, and it usually transfers more than the fee actually bought. There is a real difference between letting a client use a design and handing them ownership of it, and paying for the work does not collapse that difference on its own. As Ludwig IP Law puts it:

Paying for creative work typically grants you the permission to use it, not ownership of the copyright. Unless a written contract transfers copyright ownership, the creator retains the copyright by law.

Source: Ludwig IP Law, Paying for Creative Work Doesn't Mean You Own the Copyright

A usage license keeps the copyright with you and grants the client defined permission: the medium (web, print, packaging), the territory, the term, and whether the use is exclusive. A full copyright buyout is a separate, more expensive option you offer deliberately, not the default the model reaches for.

There is a second trap inside this clause: the fonts and stock photos embedded in your files are not yours to assign in the first place. Bonsai's design contract template carves them out explicitly, defining "background IP" as pre-existing fonts, properly licensed stock, and tools, and granting the client a right to use that background IP rather than ownership of it. Your contract should say the same, so you are not promising to transfer licenses you never held.

Clause 3: rights and files transfer only on cleared payment

This is the leverage clause, and it is the one generic AI most reliably gets backwards. The model ties delivery and the rights transfer to project completion or signing, which means the moment you send the final files you have surrendered everything, even if the last invoice never gets paid. Flip the trigger to payment. AIGA San Francisco's guidance is blunt about it:

Always include a provision making it clear that no usage rights are granted, and no digital files will be delivered, until full and final payment has been received.

Source: AIGA San Francisco, Legalities #33: Do You Have to Give Your Freelance Client Your Digital Files?

Picture the common failure: you finish the brand identity, the client asks for the files to "get started," you send them, and then the final payment goes quiet. If the contract transferred rights on delivery, the client is now using artwork they have legally received and you are chasing money with nothing to hold. If it transferred on cleared payment, the files and the rights are still yours, and their use of unpaid work is unauthorized. Same project, opposite ending, decided by that one clause. The stakes are not hypothetical: nearly 44% of freelancers have been stiffed by a client, and among them, 37% blame vague or poorly written contracts. For designers, the vagueness is almost always a transfer clause pointing at the wrong trigger.

Here is what to rewrite:

Read it once, because AI invents legal specifics

The three rewrites are the predictable gaps. The other rule is to read the whole document before you rely on it, because AI will occasionally state a legal specific with total confidence that is simply wrong. In Mata v. Avianca (2023), lawyers were fined $5,000 for filing a brief ChatGPT had stuffed with fabricated cases. The lesson holds for any document that has to protect real money. As Pactly notes, any text generated by an AI must be treated as a draft and requires final legal oversight.

Or start from a contract built for design work

Every AI-document workflow carries the same tax: you fill in the rules, fix the clauses, paste the output into a document, and reformat it, on every new project. The designer-specific prompt above is far better than a generic request, but that tax does not go away.

If you would rather start from a contract where source-files-as-a-separate-deliverable, usage-license-not-assignment, and transfer-on-payment are already set as the defaults, FreelanceDesk builds it with those choices baked in and generates locally in your browser, so client detail never leaves your machine. It is free.

To go deeper on the IP side, the source-files and licensing guide walks through the usage tiers in full, with the UX-designer version for product work. The base layer sits in the contract essentials post and the generic AI-contract prompt, while the scope-creep guide keeps a logo project from sliding into unpaid redraws.

References

• Why Designers Don't Give Up Their Files : Modern Species
• Paying for Creative Work Doesn't Mean You Own the Copyright : Ludwig IP Law
• Legalities #33: Do You Have to Give Your Freelance Client Your Digital Files? : AIGA San Francisco
• Freelance Design Contract Template : Bonsai
• 3 Reasons to Charge for Native Design Files : Creative Boost
• Freelancer Statistics : TeamStage
• Mata v. Avianca, Inc. : Wikipedia
• Can I Use ChatGPT to Write a Legal Contract? : Pactly
• Sensitive Data in ChatGPT : Cyberhaven