Game Jam Team Finder: Every Active Channel Ranked
The best game jam team finder options right now are ranked Discord servers, itch.io jam threads, and jam-specific matching channels, scored here on skill tagging, time zone overlap, and commitment screening. GMTK alone draws thousands of solo devs hunting teammates, so where you post matters more than how many times you post.
Where can I find teammates for the GMTK Game Jam?
Five channel types are active for game jam team matching: GMTK's official team-finder thread, itch.io jam pages, game dev Discord servers, Reddit, and niche forums. For GMTK specifically, the official thread gets the highest volume of jam-ready people, while Discord servers give you the fastest back-and-forth before the theme drops.
GMTK's own team-finder thread
The GMTK Game Jam page on itch.io hosts an official team-finder thread where thousands of jammers post before the event starts. Because everyone there has already committed to the jam dates, you skip the "are you actually free that weekend?" filter that kills most matches. Post early; the thread floods in the final 48 hours before kickoff.
itch.io jam pages and community posts
Beyond GMTK, every major jam runs its own page with a team-finder forum. Smaller jams mean fewer posts but less competition for skilled teammates.
Discord servers for game devs
Jam-specific and general gamedev servers run matching channels with role tags for discipline and time zone. Response time is minutes, not days, but you will vet people yourself.
Reddit and forum channels
Subreddits and dev forums work for finding one committed partner; they are slow for assembling a full crew of four.
| Channel | Match speed | Commitment filter |
|---|---|---|
| GMTK official thread | Medium | High |
| itch.io jam pages | Medium | High |
| Discord servers | Fast | Low |
| Reddit/forums | Slow | Medium |
Once you have a crew, keep the plan in one place. Our pricing page shows how Inferno fits a tiny crew.
How do Discord servers and itch.io threads compare for team matching?
Discord is faster; itch.io threads are quieter and more deliberate. Neither is great at matching, because both are unstructured: you're scanning posts and hoping skill, time zone, and commitment level line up.
Where Discord wins
Speed and volume. Jam-specific servers have dedicated team-finder channels that fill up in the hours before GMTK kicks off, so you can post and get several replies within minutes. Voice chat also lets you vet people fast: ten minutes of talking reveals more than a week of forum posts. The tradeoff is noise: the same channels are flooded with "programmer looking for team" posts that bury anyone specific, and most matching happens through DMs nobody else can see.
Where itch.io threads win
The official GMTK jam page thread is slower but higher signal. Posts tend to include portfolios, past jam entries, and honest availability, because nobody expects an instant reply. You can also check a person's itch.io profile for shipped games before you commit, which gives you a rough portfolio review built into the channel.
Whichever channel you use, the real problem starts after matching: a Discord DM chain and a spreadsheet won't survive a 48-hour sprint. Once you've found your tiny crew, put the plan somewhere shared. A board like Inferno built for indie game teams keeps tasks, milestones, and the build checklist in one place so you spend the jam shipping, not digging through chat history.
What should I include in my skill and availability profile?
A matched profile needs five fields: discipline, engine, time zone, committed hours, and jam history. Skip any one and you get vague replies from people who can't actually ship a vertical slice with you. The itch.io jam pages support team-finder threads where profiles with these details get responses instead of silence.
Skill tags that actually get matched
"Programmer" is too broad to match on. Tag your discipline plus engine plus one specialty: "Unity, gameplay systems," "Godot, shaders," "Aseprite, pixel art animation." Audio people should state whether they can do adaptive music or only one-shot SFX, since that changes what a team can scope.
Stating availability without overpromising
Give a hard number: "12 hours across the weekend, evenings EST" beats "pretty free." List your time zone explicitly, because a GMTK team spanning PST to CET loses a full day to overlap. One line of jam history, even "finished 2 jams, never shipped," tells teammates what to expect. If you keep your backlog in a board like ours, linking it shows commitment without a word of selling.
How do I post a team-finder listing that actually gets replies?
Listing template
Most listings die because they read like a wish list instead of a pitch. Use this structure:
- Role needed: 2D artist for a GMTK jam entry.
- Theme fit: one line on what you want to build.
- Commitment: 48 hours, roughly 6 hours/day, US Eastern.
- Skills I bring: Unity + code, 4 jams shipped.
- Stack: Discord voice, shared board for tasks.
That last line matters. Naming your coordination tool before the jam starts signals you have shipped before. If you are comparing boards for the jam weekend, our breakdown of Inferno vs Codecks covers what a tiny crew actually needs in 48 hours.
Common listing mistakes
Vague asks like "looking for team" get ignored. So do listings with no time zone, no commitment level, or five open roles at once. Post one specific role, state your availability honestly, and reply to every comment within an hour. Lurkers message whoever looks responsive.
How do I vet a potential jam teammate before committing?
A 15-minute voice call predicts more than any portfolio. Ask the five questions below, then trust signals over self-reports: someone who can point to a finished jam page on itch.io will ship again; someone with only WIP screenshots might not.
Five vetting questions
- What did you ship in your last jam, and what broke? Listen for how they describe scope cuts, not just the win.
- How many hours can you give Saturday and Sunday, honestly? Vague answers now mean no-shows later.
- What's your discipline, and what engine? Confirm they can actually work in your pipeline.
- Have you used Git or Perforce with a team? Merge conflicts eat jam hours.
- What would you do if the build breaks Sunday at 11 PM? You want someone who communicates, not someone who goes silent.
Red flags
"Fixed stuff" commit messages, no shipped projects, and refusing a quick call are the big three. Also watch for availability that only exists "after the jam starts." An active profile in a server like Game Dev League's Discord community is a weak signal on its own, but combined with zero jam history it's a pass. Once you've picked your crew, run the same honesty test on your own stack: our Inferno vs Trello comparison covers where a general kanban falls short for game work.
How do I handle time zones and schedules in a 48-hour jam team?
With 48 hours total, a three-hour-overlap team loses more time to waiting than to building. Map your overlap windows before the jam starts: each teammate posts their committed hours in their own time zone, and you mark the shared blocks where at least two of you are awake. If your overlap is under six hours, treat the jam as async-first, not co-op.
Mapping overlap windows
Write the overlap blocks into your jam channel pinned message, with hard boundaries: "9 PM to 1 AM ET is shared time; everything else is solo." Protect the longest overlap block for decisions that need everyone, like scope cuts after the first playtest. Solo hours go to heads-down work in one discipline so nobody blocks on a half-finished system.
Handoff rituals for async jamming
End every session with a two-line handoff: what shipped, what breaks if you touch it. That single habit kills the "fixed stuff" commit problem before it starts. Assign one person to leave the build in a runnable state before logging off, so the next time zone wakes up to something playable instead of a broken branch and a mystery.
What do I do if my jam team falls apart mid-jam?
Triage in this order: figure out what's actually lost, cut scope to match, and ship something. A broken build at hour 30 with a missing programmer feels fatal, but most jam deaths come from teams trying to hit the original scope with half the crew. If someone ghosts, don't spend two hours chasing them. Post one message, set a 30-minute timer, then reassign their work.
Cut scope, not quality
List every feature and mark which ones the game dies without. A vertical slice with three polished mechanics beats six broken ones. If your artist quit, flat colors and primitives are a legitimate style, not a failure. Judges and players reward a game that ships.
Replacing a discipline mid-jam
You can still find help mid-jam: r/gamejams allows team-finder posts under its rules, so a "need a programmer, 18 hours left, rev share on a fun prototype" post there or in the jam's own Discord can land someone fast. Keep the ask narrow and give them one system to own, not the whole backlog.
How do I keep a jam team organized once you have one?
One board beats three tools
A 48-hour jam punishes scattered setups. When tasks live in Trello, decisions in Discord, and the design doc in Google Docs, someone is always working from stale information, and mid-jam scope creep happens because nobody can see the whole backlog at once.
A single shared board fixes this. Every teammate sees what's in progress, what's cut, and what's blocking the build, without digging through chat history. During a jam, that visibility is the difference between shipping a vertical slice and shipping an apology.
Inferno was built for tiny crews like yours: one workspace where planning, tasks, and the design doc live together, so your artist and your coder stay in sync across disciplines.
Where Inferno falls short for jams
Inferno is built for ongoing studio work, so it carries more structure than a 72-hour jam needs. Setup takes longer than a bare kanban board, and it won't manage your Discord. If you're jamming once, Trello is simpler. If the jam is a proving ground for a tiny crew that plans to ship together, the structure pays off.
FAQ
Is the GMTK Game Jam team finder still active this year?
Yes. The official team-finder thread on the GMTK jam page on itch.io stays active each year, with thousands of jammers posting before kickoff. Post early, because the thread floods in the final 48 hours before the theme drops, and everyone there has already committed to the jam dates.
Can I join a game jam with no experience?
Yes, but be honest about it. One line of jam history, even "never shipped a game," tells teammates what to expect, and some people prefer a clean slate over bad habits. Target smaller jams with less competition for spots, list your real committed hours, and pick one narrow discipline to own so nobody has to guess what you can do.
How early should I start looking for a jam team?
Days, not hours. The official threads and Discord matching channels fill up in the final 48 hours, but the best teammates are already matched by then. Post your listing about a week out, run 15-minute vetting calls, and map your overlap windows before the theme drops so the jam starts with a plan instead of introductions.
Do I need to use Discord to find a game jam team?
No. Discord is the fastest channel for back-and-forth and voice vetting, but itch.io jam threads give you higher-signal posts with portfolios and honest availability, and Reddit works for finding one committed partner. Match speed against the commitment filter you need: Discord replies in minutes but requires you to vet people yourself.
What engine should I list if my teammates use different ones?
List the engine the team will actually build in, then state your transferable skill underneath it: "learning Godot, 3 years Unity" reads better than a shrug. If nobody can switch, an engine mismatch is a real blocker for a 48-hour jam, since merge conflicts and unfamiliar pipelines eat hours you do not have.