Studio Queues
Proof of Human Made Art: How to Show Your Work Is Yours

Studio Queues Team · Last updated August 25, 2026

Proof of Human Made Art: How to Show Your Work Is Yours

Proof of human made art is now part of the sale. Process files, timelapse recording, layered source files, and documented milestones that settle the question early.

Being asked to demonstrate that you drew your own work is a new part of the job, and an irritating one. It arrives at the worst moments: mid-negotiation with a client who seems otherwise keen, or under a post that was doing well until someone asked.

The artists who handle it easily are not the ones with the best argument. They are the ones who already have the files. Proof of human made art is a record-keeping problem, and the record has to exist before anyone asks for it, because assembling it afterwards looks exactly like assembling it afterwards.

TL;DR

Proof of human made art is a record you build while working rather than when challenged. Keep layered source files instead of flattening, run timelapse capture by default, keep dated stage exports, and keep the intake that shows the brief arrived before the work existed. Content Credentials are a real standard worth using, but the core specification deliberately does not attribute content to a person, so it records tool and edit history rather than proving authorship. Answer the question plainly when it comes, and do not use detection tools on other artists.

Why proof of human made art became part of the job

Buyers commissioning custom work are spending money on something that does not exist yet, from someone they often have not met. Verification anxiety was already part of that transaction, and it has broadened.

The Bureau of Labor Statistics notes that artists spend their time and effort selling their work and building a reputation. Reputation now includes being demonstrably the person who made the thing, which is an additional overhead nobody asked for and which falls hardest on artists who work cleanly and quickly.

The good news is that the fix is mechanical. It is not a debate you have to win, it is a folder you either have or do not.

Build the record while you work

Four habits, all cheap, all worth more than any argument.

Keep the layered file. Do not flatten and delete. A working file with named layers, hidden false starts, and construction geometry underneath is the single most convincing artifact you can produce, because it contains the decisions rather than the result.

Record by default. Most drawing software will capture a timelapse without you doing anything after setup. Turn it on and forget it. The value is that it exists for the piece nobody expected to be questioned, which is always the one that gets questioned.

Export dated stages. Sketch, line, flats, finish, each saved as its own file with the date intact. Cheap to do, and it gives you a sequence rather than a single image.

Keep the intake. The brief, the references the client sent, and the timestamp on all of it. This is the underrated one, because it demonstrates that a specific request existed before the work did, which is a fact about sequence rather than a claim about process.

Store these somewhere durable. A chat thread is not storage, since accounts get deleted and platforms lose history.

What Content Credentials actually do

The stock advice now is to use Content Credentials, and it is worth understanding what they are before relying on them.

Content Credentials are produced under a technical standard from the Coalition for Content Provenance and Authenticity. The specification attaches tamper-evident, cryptographically signed data to a file, recording facts about how the content was created, what tools or processes were used, and how it has changed over time. Those statements are bundled into a signed manifest that travels with the asset, so a viewer with a compatible tool can inspect the history.

For an artist this is genuinely useful. A file carrying a credential showing it was made in a drawing application across a series of edits is a stronger artifact than a bare JPEG.

What Content Credentials do not do

Here is the part the stock advice leaves out, and it matters.

C2PA's own FAQ states that the core Content Credentials specification does not support attribution of content to individuals or organizations, deliberately, so that the standard remains maximally privacy-preserving. It notes that some user communities are developing extensions allowing attribution where the risks of disclosing creator identity are well understood.

So a credential records tool and edit history. It does not assert that you personally made the work, which is the exact claim an artist is being asked to support. Treat it as corroborating metadata rather than as an answer.

There is a second practical limitation. Provenance metadata can be stripped or lost when a platform re-encodes an upload, which is a known weakness of any metadata-based approach. The credential may survive on the file you send a client and not on the version that appears in a feed.

None of that means skip it. It means your own files remain the primary record and the credential is a supporting one.

Platform-level signals

Where your work is published carries information too.

A Studio Queues artist profile ships noai, noimageai in its meta robots tag, which is a machine-readable request that the page and its images not be used for AI training or image generation. It is a directive rather than an enforcement mechanism, and honest framing matters here: it asks, it does not compel.

What it does give you is something concrete to point at. When a client asks what happens to their commission, an answer that names a specific tag on a specific page is better than a general reassurance, and it is verifiable by anyone who looks at the page source.

The profile also holds the intake questions, the agreed scope, and the milestone history attached to the client rather than to a conversation, which is the same record-keeping argument in a different form. You can set up a profile and have that documentation accumulate as a side effect of running the job.

Answering the question when it comes

Short, unbothered, and factual works better than anything else.

Offer the timelapse or the layered file. Do not offer a lecture. The person asking is usually a nervous buyer rather than an accuser, and treating the question as an insult turns a cautious client into a lost one.

If it is a public accusation rather than a private question, answer once, plainly, with the evidence, and then stop. Extended threads defending yourself perform badly and keep the accusation visible for longer than the answer.

Putting the answer somewhere permanent helps. A line in your commission terms noting that you keep process files and will share them on request means the question often does not get asked, and when it does you are pointing at an existing policy rather than reacting.

What not to do

Do not run detection tools on other artists. Publicly available detectors are not reliable enough to settle anything, and a false accusation does real damage to someone whose income depends on their reputation. If you would not want it aimed at you on the strength of a tool's output, do not aim it at anyone else.

Do not reconstruct a process after the fact. Producing a suspiciously tidy set of stages after being questioned looks worse than having nothing. Keep the real record instead.

Do not make it your whole identity. Branding everything you post around not using AI shifts the subject away from your work. Show the work, keep the files, answer when asked.

Frequently asked questions

What is the best single piece of proof? The layered working file. It contains decisions, false starts, and structure that a finished image does not, and it is difficult to fabricate convincingly after the fact.

Do I need to record every piece? Set capture to run automatically and the question stops mattering. The piece you did not record is always the one that gets questioned.

Are Content Credentials worth the setup? Yes as supporting metadata, no as a substitute for your own files, since the core specification does not attribute work to a person.

What if a client asks and I have nothing? Say so honestly and offer to work in stages on their piece with visible progress. Do not manufacture evidence for past work.

Should I put this in my terms? A short line stating you retain process files and share them on request is useful, and it belongs alongside the rest of your terms rather than as a separate statement.

Does posting process content help? Yes, and it does other work at the same time. Regular process posts build a public history that answers the question before it is asked, and the promotion tactics that get your reach cut covers why process content is worth posting anyway.

The honest summary

Proof of human made art comes down to whether you kept the files. Layered sources, automatic timelapse, dated stages, and an intake record that shows the brief predates the work. All of it is free, all of it takes minutes to set up once, and none of it can be assembled convincingly after someone asks.

Content Credentials are a real standard and worth using, with the caveat that the core specification deliberately does not attribute content to a person, so it supports your case rather than making it.

When the question comes, answer it plainly and move on. And if you want the intake, scope, and milestone history to accumulate on their own while you work, you can set up a Studio Queues profile. Founding artists get 0% platform fees active for as long as premium subscription stays active, first 500 spots only. Stripe processing fees still apply.