How to spot a fake design portfolio: checking that a designer's work is their own
On this page
- What makes a design portfolio fake?
- Which checks work, and how much do they prove?
- How do you run a portfolio walkthrough that tests ownership?
- What about NDA work and team projects?
- Is AI-generated work in a portfolio fake?
- What should you do if the work isn't theirs?
- How do you keep portfolio checks fair?
- Design portfolio check you can copy
- Questions people ask
The reliable way to spot a fake design portfolio is a process walkthrough: ask the designer to take you through one project from the earliest sketch to the final screen, explain what they tried and dropped, name who else worked on it, and make a small change live. Back that up with three quick checks: a reverse image search of a few portfolio images, the co-owners and credits on any Behance project, and an employment check for client work they claim. Figma version history and Content Credentials can add evidence when they exist, but their absence proves nothing. Team work is normal; the question is which part was theirs. As of November 2026.
Where the portfolio review sits in the loop, and how to score it, is in the interview guide for designers; screening questions about portfolio ownership are in graphic designer screening questions. This page covers checking that the work is real.
What makes a design portfolio fake?
Most problems are one of six kinds, from mild to serious:
- Inflated credit. A team project shown as solo work, or a junior's contribution shown as the lead's.
- Concept work shown as shipped work. A redesign nobody commissioned, presented as a client engagement.
- Undisclosed generated work. Images made with AI tools presented as hand-made craft for a role that needs that craft.
- Invented clients or employers. Logos and company names the designer never worked for; the resume checks in resume fraud red flags apply.
- Stolen work. Another designer's projects or shots copied under the candidate's name.
- A whole borrowed persona. Microsoft Threat Intelligence reported in June 2025 that North Korean remote IT workers "establish legitimacy through fake portfolios and profiles on developer platforms like GitHub and LinkedIn." That warning concerns technical roles, but remote design and front-end jobs attract the same tactics.
Which checks work, and how much do they prove?
| Check | How | What it shows | Limit |
|---|---|---|---|
| Reverse image search | Google's Search with an image: upload a file, drag one in, or paste an image link | Results can include "websites with the image or a similar image," so an earlier copy under another name shows up | Cropped or recolored copies may not match; private work never appears |
| Behance co-owners and credits | Open the project's info and the listed co-owners' profiles | Behance's help center says a co-owner must accept the invitation before their name shows, and co-owned projects appear on every co-owner's profile; credits show in the project info | Credits are added by the uploader; a missing credit is not proof of theft |
| Figma version history | The candidate opens the file on a screen share and shows the history | Figma says version history is "a timeline of events dating back to the file's creation," with a checkpoint every 30 minutes (Figma Learn) | A duplicated file "doesn't include any comments or version history from the original file" (Figma Learn), and drafts and Starter plan files show only 30 days |
| Content Credentials | Drop the image into Adobe's Inspect tool | Adobe says it shows details "such as who created the content, how it was created, and whether generative AI was used" | Most images carry no credentials; absence means nothing |
| Employment or client check | Confirm the claimed employer or client through contacts you find yourself | Whether the designer worked there in the stated role | Usually not which screens they made; see how to verify employment history |
| Process walkthrough with a live change | Video call with screen share | Whether the person can reproduce the thinking and the craft | Takes 30 to 45 minutes of a designer's time |
How do you run a portfolio walkthrough that tests ownership?
Pick the project yourself, from the two or three the candidate says best match the role, so they cannot steer to the one they rehearsed. Then ask for the parts of the work a copier does not have:
- "Show me the earliest version." Sketches, wireframes, a first rough flow. Designers who did the work usually have them, even if messy.
- "What did you try that didn't make it?" Rejected directions and why they were rejected are hard to invent on the spot.
- "Who else worked on this, and what did they own?" A clear line between their part and the team's is a good sign, not a weakness.
- "What changed after research or launch?" Real projects come with constraints and surprises.
- "Open the file and change one thing." Swap a component, adjust a layout for a smaller screen, restyle a state. Watch how they work in their own file.
If you use a paid or unpaid exercise as well, the authorship checks in how to verify take-home assignment authorship apply to design work too.
What about NDA work and team projects?
Much good design work cannot be shown. Agency and in-house designers often work under nondisclosure agreements, and nearly all product design is a team effort. Do not ask a candidate to send client files they are not allowed to share, and do not mark them down for a redacted case study. Ask instead:
- "Can you show this on a screen share with the client's name and data hidden?"
- "Walk me through it without the visuals: the problem, your decisions and the result."
- "Which of these screens did you design yourself?"
Apply the same allowance to every candidate. A designer with only redacted work and a designer with a public Behance profile should be scored on the same walkthrough.
Is AI-generated work in a portfolio fake?
Not by itself. Many designers now use generative tools for mood boards, placeholder imagery or production steps, and that can be entirely legitimate. It becomes a problem when generated work is presented as hand-made craft for a role that needs that craft, or when a candidate hides how a piece was made when asked. Three habits keep it fair:
- Say in the posting what you expect, for example "Tell us which pieces used AI tools and how."
- Ask every candidate the same question: "How did you make this one?"
- Test the craft the role needs in the walkthrough or exercise, rather than trying to detect generated images.
What should you do if the work isn't theirs?
- Ask before you conclude. "I found this image on another designer's profile from 2023. Can you tell me about that?" Studios repost team work, and two designers may share a project.
- Decide on facts: what you found, where, with dates, and what the candidate said. A failed walkthrough matters more than a search result.
- Leave takedowns to the owner. Behance's copyright guide and Dribbble's reporting page are built for the copyright owner ("If you believe that a shot on Dribbble infringes one or more of your copyrights"). If you can reach the original designer, telling them is the useful step.
- If it looks organized, such as the same portfolio behind several applicants with different names, follow North Korean IT worker red flags and report to the FBI at ic3.gov. The same checks for code are in how to spot a fake GitHub profile.
How do you keep portfolio checks fair?
- Same checks at the same stage for every finalist. Not only for candidates with unfamiliar schools, names or locations.
- Judge the work, not the presentation. A polished template is not evidence of skill, and a plain one is not evidence of fraud.
- Pay attention to time. Long unpaid exercises put off strong candidates; a 45-minute live walkthrough often tells you more. See how to evaluate a take-home assignment.
- Record facts, not impressions: "Walkthrough of [project] by [name] on [date]: showed early wireframes and two rejected directions; made a layout change live."
Design portfolio check you can copy
Candidate: ____________ Role: ____________ Checked by: ______
[ ] Project chosen by us from the candidate's top three: ______
[ ] Reverse image search on 3 images; earlier copies found? Y / N
[ ] Behance co-owners and credits reviewed (if on Behance)
[ ] Claimed employer or client confirmed via contact we found
[ ] Walkthrough: earliest version shown? Y / N
[ ] Walkthrough: rejected directions explained? Y / N
[ ] Walkthrough: own part vs team's part stated clearly? Y / N
[ ] Live change made in the candidate's own file
[ ] Asked how each piece was made (tools, including AI)
Outcome (facts only): ___________________________________________
Google, Behance, Figma, Adobe, Dribbble and Microsoft sources checked as of November 2026.
Questions people ask
How can I tell if a designer's portfolio is really their own work?
Ask them to walk you through one project from the earliest sketch to the final screen, explain what they tried and dropped, say who else worked on it, and make a small change live. Back that up with a reverse image search of a few portfolio images, the credits on any Behance project, and an employment check for client work they claim. The walkthrough is the strongest test; the other checks only show where an image appears and what the designer says about it.
Can I reverse image search a design portfolio?
Yes. Google's Search with an image lets you upload an image, drag one in or paste an image link, and its results can include websites with the image or a similar image. An earlier copy under another designer's name is worth raising with the candidate. A clean result proves nothing, because much design work is never public.
Should I ask a designer for their original Figma files?
Ask to see the file on a screen share rather than asking them to send client files, which may be under a nondisclosure agreement. Figma's version history shows a timeline back to the file's creation, but Figma says a duplicated file does not include the original's version history, and drafts and Starter plan files show only 30 days, so a short history is not proof of anything.
Is a portfolio made with AI tools a fake portfolio?
Not by itself. It becomes a problem when a candidate presents generated work as their own hand-made craft for a role that needs that craft, or hides how it was made when asked. Say in the posting what you expect, ask every candidate how each piece was made, and where a file carries Content Credentials, Adobe's Inspect tool can show whether generative AI was used.