How to Prove a Figma Design Was Made by a Human

Use two records together: Figma's version history to show the file changing over time, and a process certificate recorded while you work to show session time and how much of it involved AI tools. Send the client both links.

By the end of this post you will have a setup you can start on your next job, a handoff checklist, and a message to paste to the client.

Last updated: October 12, 2026

Version history shows when the file changed, not who was at the keyboard

Figma saves a history of your file automatically. Its Help Center says Figma records a new checkpoint about every 30 minutes and groups the autosaved versions, so you click a group to expand it and see each one.

That is useful. A client can see the file grew from a rough layout to a finished system over days, not minutes.

But look at what each version carries. The same Help Center page says every version shows the name and avatar of the main contributor, the version name, a description of changes, and the date and time it was created. Figma's developer docs describe the same data: the who and when, plus a title and description you add.

The "who" is the account that saved the change. It tells a client which login was used and when. It does not tell them whether a person drew the frame by hand or a tool produced it. A skeptical client can fairly say anyone could be logged in.

A checkpoint every 30 minutes also shows snapshots, not minutes worked. Two checkpoints an hour apart say nothing about whether you spent five minutes or fifty in between.

Pair it with a process record made while you work

A DrawDog certificate fills the gaps version history leaves. It records session time, file growth, AI tool percentage and a file fingerprint match, and Figma is one of the supported apps. The client opens one link and verifies it with no account and nothing to install.

It does this without reading your work. DrawDog never records file contents, file names, folder paths, keystrokes, screen contents or browser tabs.

One honest limit: a certificate does not catch someone who generates a design with AI and then rebuilds it by hand while a session runs. It is a record of how your session went, not a verdict on every possible trick. Say that plainly if the client asks.

Name 4 to 6 versions while you work, not at the end

A wall of grouped autosaves reads as noise. Named versions read as a story. Figma lets you name a version and add a description, and you need to name one to give it a title at all.

Here is the setup that works:

1. Start your DrawDog session before you open the Figma file. If you start late, the first half of the job has no record.
2. In Figma, click the file name at the top and choose Show Version History. The timeline opens on the right.
3. Work normally. Do not restore old versions or clear anything mid-job.
4. At each milestone, save and name a version. Four to six is enough: "Wireframe done", "Components built", "Client round 1", "Final".
5. Work in the original file the whole time. Copying everything into a fresh file at the end gives you a file with no history, and the evidence resets to zero.

Free plans lose history after 30 days, so save proof at handoff

The Help Center says files in Drafts or in free Starter teams get up to 30 days of version history, while a paid team gets the full history of existing files. Check that page on the day you rely on it, because plan limits change.

Example: say you hand over a landing page design on October 1 and the client raises a question on November 15. That is 45 days later. On a free Starter team, the named versions from early October may be gone, and you have nothing to show.

The rule:

• Drafts or free Starter team: near handoff, open Show Version History and screenshot the named list with the dates visible. Send the screenshot with the certificate link, so your proof does not depend on the history still existing.
• Paid team: the full history stays available, but still name your milestones. A client will not scroll through autosaves.

Write version descriptions that stay true when a tool helped

Add a one line description to each named version so the panel reads like a short log. Example: "Round 1: mobile nav rebuilt by hand, no plugins."

Only write what is true. If a plugin or an AI feature touched a step, say so in that description. If the certificate later shows AI tool use and your description said "all hand drawn", the mismatch costs you more trust than the AI use ever would.

Minor AI use is not a reason to lose a job. The graded certificate has a place for it: A is certified human-made, B is human-made with AI help, and C is recorded but not certified. For wording that keeps the client comfortable, see how to disclose minor AI use without losing the job.

Match the proof to what the client actually asked

The client says	Send	Say
"Show me how it evolved"	Named versions plus a dated screenshot	"Each named version shows my account and the date."
"Prove it wasn't AI"	Certificate link plus the named versions	"The certificate was recorded while I worked. You can open it without an account."
"Does this show who made each change?"	Both, with a plain answer	"Version history shows which account saved each change and when. The certificate shows session time and AI tool percentage."
Others edited the file	Named versions, labeled by person	"Versions 1 to 4 are mine. Version 5 is the copywriter's."

If teammates or the client edited the file, their names appear on their versions. Tell the client which named versions are yours before they open the panel, so nobody reads a colleague's version as your work.

Copy this Figma handoff checklist and client message

Before the job:

• Start the DrawDog session from the menu bar or system tray, then open the Figma file.
• Open Show Version History from the file name menu.

During the job:

• Name a version at every milestone (4 to 6 total) with a one line, true description.
• Work in the original file. Never duplicate it into a new one.

At handoff:

• Scroll the panel once and check that every named version is labeled correctly, yours or someone else's.
• On a free plan, screenshot the named list with dates visible.
• End the DrawDog session and generate the certificate page.
• Send the message below.

The message:

Here is the process record for the [project] design: [certificate link]. It shows session time, how the file grew, and the AI tool percentage, and you can verify it without an account. The named versions in the Figma file (Wireframe done, Components built, Client round 1, Final) are dated and match it.

If the client wants to know more, this is the plain answer to give: version history shows which account changed the file and when, and the certificate shows how long the session ran and how much of it involved AI tools. Neither one claims to show who was physically at the keyboard, and you should not claim that either.

Mistakes that cost you the argument

• Presenting version history alone as proof of human authorship. It proves edits happened, not who or what made them. Pair it with a recorded process.
• Leaving versions unnamed. The client sees timestamps and gives up, or assumes you are hiding something.
• Letting other people's edits sit unlabeled. A stranger's name on a version invites questions about the whole file.
• Overstating the work. "All hand drawn" is a claim the certificate can contradict. Describe each step as it was.
• Starting the process record late. Whatever happened before the session started has no proof.

For the general workflow behind all of this, how to prove to a client you actually made the work covers what to send and when. If you also work in Photoshop, Photoshop version history records different things than Figma's does, and it is worth knowing which is which.

Your next ten minutes

Open your current Figma file, choose Show Version History, and name the versions you already have in a way that tells the story so far. Add one true line of description to each. Then check which plan the file lives on: if it is Drafts or a free Starter team, put a reminder in your calendar for day 25 to take the screenshot.

Start recording before the next file opens

Version history shows the file changing. A process record shows how long you spent and how much of it involved AI tools. Together they give a client something they can check without asking you to take your word for it. The free tier gives you three certificates a month with no credit card, so you can try it on a real job. Download DrawDog free and start a session before you open your next Figma file.

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.