Portfolio Review Checklist: What Indie Studios Actually Look At in 90 Seconds

Watched an indie studio lead close an ArtStation tab in 11 seconds last month. Artist had 47 pieces. First three were AI-composited environment moodboards with the classic melted geometry in the mid-ground. Tab closed. Filed under no.

That's portfolio review at small studios in 2026. Nobody scrolls. Nobody clicks into subfolders. The first six thumbnails decide if you get a call or get archived. Since the ArtStation flood of 2025, when generative tools made "impressive" concept art trivial to fake, indie leads have gotten faster and more paranoid.

Not writing this from theory. Just passing on what studio founders tell me they do in the 90 seconds they give a candidate. The indie game portfolio review checklist below came out of those conversations.

The 90-second review, minute by minute

Timing I keep hearing from leads who hire for small teams. Uncomfortably short. Also honest.

• 0 to 10 seconds: Grid scan. Are the first six thumbnails coherent? Do they read at a glance? Any AI-slop tell (six-fingered hands, melted rings, physically impossible reflections)?
• 10 to 30 seconds: Click into the top piece. Look for process shots, iteration, breakdown. Single beauty render with no context? Suspicion rises.
• 30 to 60 seconds: Scan the About section. Shipped game? Jam entry with a real link? GitHub with commits? Anything verifiable.
• 60 to 90 seconds: Book a call, save for later, or close.

Ninety seconds. If you built your portfolio to reward the patient reader who scrolls to piece 22, you built it for a reader who doesn't exist. Studios with three people and a runway don't have patient readers. They have exhausted founders reviewing applications between builds.

Why indie hiring isn't AAA hiring

At a large studio, an art director hires for a slot. Environment artist, character artist, VFX. Portfolio proves depth in one lane. At an indie studio with four people, the lead is hiring a human who'll sit in Discord for the next 18 months, ship alongside them, and probably do three jobs. Portfolio has to prove taste and range at once.

Same portfolio gets celebrated at an AAA recruiter interview and skipped at a two-person team. Different discipline.

The six thumbnails that decide everything

Take one thing from this: reorder your portfolio right now so the first six pieces are your strongest, most recent, most coherent work. Not your favorites. Not the sentimental ones. The strongest.

Coherent means the six pieces feel like they belong together. Same visual voice, same level of finish, same discipline. A grid that jumps from anime chibi to grimdark realism to isometric pixel art tells the reviewer you have no identity. Fine at art school. A killer when a solo dev is trying to figure out if you can hold a project's visual direction for two years.

The ArtStation team's written about this shift toward tighter, curated pages, and if you look at how their featured artists present themselves, the top portfolios are almost aggressively focused. Six to twelve pieces. One clear specialty. No filler.

What makes a lead close the tab in under 15 seconds

• Inconsistent finish: One masterwork surrounded by unfinished sketches suggests the masterwork was carried by a friend, a tutorial, or a generator.
• No dates: Undated work looks like it might be from 2019. Or older. Recent work signals current ability.
• Cover art with no gameplay: A stunning splash screen for a game you can't play anywhere is worth almost nothing to a lead who needs to ship.
• AI tells in the grid: Blurred midgrounds, impossible architecture, jewelry that dissolves into itself. Indie leads have gotten very good at spotting these. Coverage on 80 Level through 2025 turned this into common vocabulary in art director circles.
• No links out: No itch page, no Steam page, no GitHub, no LinkedIn, no jam entries. Just images. Flags as unverifiable.

The AI-slop problem and how leads vet around it

Every indie lead I talk to has a personal vetting protocol now. Generative tools got good enough that a static beauty shot no longer proves you can draw. Proves you can prompt. Not the same skill. Hiring the wrong one wastes six months.

What leads ask for now, in order of trust:

1. Timelapse videos. A 30-second speedpaint of you working in real software with visible layers, brush presses, and undo strokes beats 20 finished pieces. Nothing fakes a timelapse convincingly yet.
2. Process breakdowns. Sketch, blockout, lighting pass, final. Four images of the same piece at four stages. AI outputs can't fake this coherently.
3. Live drawing tests. A 45-minute paid test where you screen-share a small task. Uncomfortable but decisive.
4. Shipped work. A game on itch.io or Steam with your name credited, playable right now.

Zero of these four in your portfolio? You're asking the reviewer to trust images. In 2026, that trust is gone. Fix it this week.

For programmers: the equivalent of process breakdowns

Programmers get away with cleaner portfolios because code is more self-evidencing than art. Same principle though. Show the work, not the result.

• A GitHub with commits stretching over months. Not one dump of finished code.
• A written breakdown of one hard technical problem you solved. Two paragraphs, not a novel.
• A playable build. Web build ideally. If a lead has to download a zip and hope it compiles, they won't.
• A jam entry from any of the recent Ludum Dares or the upcoming Steam Next Fest in October 2026. Jams prove you finish things.

The About section: where trust is actually built

Most portfolio guides ignore the About section. Mistake. When a lead is on the fence after the visual scan, the About section decides. That's where they figure out if you're a person they can work with for 18 months, or someone who'll ghost them at month six.

(We wrote about the collaboration collapse pattern in why indie teams fall apart at month six. The About section is where a lead tries to sniff out that risk before it becomes their problem.)

A good About section for an indie applicant, in this order:

1. One sentence on what you do and what you're looking for. Not "passionate creator." Something specific. "2D character animator, looking for rev-share or paid work on a shipped 2D action game."
2. Your location and timezone. Small teams sync in Discord. Timezone matters.
3. Availability. Hours per week. Contract length you're open to.
4. Rate range or "open to discussion." Coyness here reads as inexperience.
5. Contact method. Email or Discord. Not a form.

Solo devs like Lucas Pope (Papers, Please, Return of the Obra Dinn) or ConcernedApe (Stardew Valley) don't need About sections because their work speaks. You do. Write it.

Where to find candidates who already meet this bar

Studio side now. The practical question is where to post so applications arrive pre-filtered. Options that won't waste your time:

• Crewforge. Post a rev-share, paid, or unpaid role and let makers apply with their portfolio. You can see open roles at indie studios on Crewforge to benchmark how other small teams describe their needs, then register your studio and post a role in a few minutes.
• ArtStation job boards. Good for artists, noisy for programmers.
• Game jam collaborators. The people you jam with are the people who ship. Still the highest-signal hiring channel in indie.
• Industry reporting. Follow hiring postmortems on Game Developer and GamesIndustry.biz to see how other small studios structure their teams.
• GDC talks. The GDC Vault has multiple postmortems where solo and duo devs describe exactly how they vetted their first collaborators. Watch two before your next hire.

My indie game portfolio review checklist lives on one index card. Sharing it now.

The one-card checklist

Print this. Tape it above your monitor. Use it on the next 10 applications you review.

First 10 seconds: Are the first six thumbnails coherent, dated, and free of obvious AI tells?

First 30 seconds: Does the top piece have process shots or a breakdown?

First 60 seconds: Is there at least one shipped or playable thing linked (itch, Steam, GitHub, jam entry)?

First 90 seconds: Does the About section tell me location, availability, rate, and contact in under 100 words?

Yellow flags: No dates, no process, no shipped work, no rate, no timezone.

Red flags: AI tells in the grid, inconsistent finish across pieces, cover art with no playable game attached.

Green flags: Timelapse videos, credited work on a shipped game, jam history, commits over months not days.

Whole thing. Four checks, three flag categories. Can't answer these in 90 seconds on a candidate's portfolio? The portfolio failed, not you.

How to interview indie game artists after the portfolio passes

Portfolio gets them the call. Call decides the hire. The question of how to interview indie game artist candidates comes up constantly, so here's the compressed version.

A 45-minute call, structured:

• 10 minutes: Walk me through one piece from your portfolio. Any piece. I want to hear how you talk about your own work. Vague answers here are the single biggest predictor of a bad hire.
• 10 minutes: Tell me about a project that failed. Can't name one? They haven't shipped enough.
• 10 minutes: Here's a specific problem from my current project. How would you approach it? Not a test. A conversation. You're checking taste, not correctness.
• 10 minutes: Practical. Timezone, rate, availability, contract length, IP terms.
• 5 minutes: Their questions for you. If they have none, flag.

Then pay them for a small test. Two days of work, market rate. Not a "trial." A real, scoped, paid deliverable. That's the audition. Filters harder than any portfolio can.

Vetting indie game collaborators past the first hire

Once someone passes the portfolio and the call, the last question is whether they're a collaborator or just a contractor. Matters because indie teams live and die on the collaboration layer, not the deliverable layer.

Vetting indie game collaborators comes down to three signals across the paid test:

1. Do they ask questions before they start? Silent starters produce beautiful work that misses the brief. You want someone who pushes back on the brief in the first hour.
2. Do they show work in progress? A collaborator ships a rough version at 30% done and asks for feedback. A contractor disappears for a week and delivers a polished piece you can't cheaply revise.
3. Do they respect the scope? Scoped two days, took five? Not passion. A signal about every future estimate they'll give you.

None of this shows up in a portfolio. All of it shows up in two days of paid work.

What to do this week

Artist or programmer reading this? Open your portfolio right now. Not tomorrow. Now. Look at your first six pieces. Would a tired studio lead with three tabs open close yours in 15 seconds? If yes, reorder them today. Delete the weakest 30%. Add dates. Write a real About section. Link one playable thing.

Studio lead? Print the one-card checklist above and use it on the next application that hits your inbox.