How to Finish Your First Game Jam Without Burning Out
You signed up for your first game jam, the theme drops on Friday night, and by Sunday afternoon you have a beautiful player controller and no game. That is the most common way a first jam ends, and it has nothing to do with skill.

You signed up for your first game jam, the theme drops on Friday night, and by Sunday afternoon you have a beautiful player controller and no game. That is the most common way a first jam ends, and it has nothing to do with skill. It comes from planning like a normal project when a jam runs on completely different rules.
I have entered 23 jams and helped run four small ones, and I have watched hundreds of first entries come in. The people who finish are not the best programmers. They scope ruthlessly, ship something playable early, and treat the community around the jam as half the point.
Picking the right first game jam
Not every jam is a good place to start. Length, size and rules change the experience a lot.
| Jam type | Typical length | Good for a first timer? |
|---|---|---|
| Large themed jams on itch.io (thousands of entries) | 48 to 72 hours | Yes, but your game may get few ratings |
| Ludum Dare compo | 48 hours, solo, all assets made by you | Hard; try the 72 hour jam track instead |
| Small community jams (under 100 entries) | 1 to 2 weeks | Best choice; more feedback per entry |
| Tool-specific jams (Scratch, PICO-8, Godot) | 1 week to 1 month | Very good; the audience knows your tool |
For a first jam, I recommend a small one lasting at least a week. You still get the deadline pressure, but you can sleep, and with 60 entries instead of 6,000 people will actually play your game and leave comments.
Scope your first game jam entry to one mechanic
Here is the rule I give everyone: your game should be describable in one sentence with one verb. "Jump between platforms that disappear when you look away." "Push crates onto switches before the timer runs out." If your sentence has "and" in it, cut the second half.
Then plan the jam in rough time blocks. For a 48 hour jam:
- Hours 0 to 2: Brainstorm on paper. Write ten ideas, pick the smallest one that you find funny or interesting.
- Hours 2 to 10: Build the core mechanic with grey boxes. No art. No menus.
- Hour 10: Have a stranger or friend play it for two minutes. If the core is not fun as boxes, change the idea now.
- Hours 10 to 30: Build three to five short levels or one tight loop. Add art and sound once the game works.
- Hours 30 to 40: Polish feedback: screen shake, sound on every action, a clear win and lose state.
- Hours 40 to 46: Upload a build, test it on another computer, write the page.
- Last 2 hours: Buffer. Something will break during upload.
Upload a playable build privately by hour 24. Even if it is ugly, you now have something to submit, and every hour after is improvement rather than rescue.
Why going solo is often better for a first jam
The usual advice is to find a team for your first jam so you are not alone. I think solo is better more often than people admit. Forming a team with strangers on a Discord the night the theme drops means spending the first six hours agreeing on an idea, a tool and a file-sharing setup. Many first-time teams spend more time coordinating than building.
Solo, you make every decision in seconds. You learn which parts of game making you can do and which you avoid. You can use free asset packs from itch.io or Kenney for art and sound if the jam rules allow it, and most do outside of strict compos.
Teams do shine when you already know the people, or when roles are obvious, such as one programmer and one artist who have worked together. If you want collaborators, meet them before the jam. A local game dev meetup is a much better place to find a partner than a frantic team-finder channel.
Write a game page people will click
When the jam ends, there may be thousands of entries. Your page is the only thing standing between your game and being skipped.
- Cover image: a real in-game screenshot at 630 by 500 pixels on itch.io, showing the mechanic, not a logo on black.
- First line: your one-sentence pitch.
- Controls: listed plainly. Raters will not guess.
- A short GIF: five seconds of play. Our guide to devlog GIFs and short clips that show progress applies directly.
- Browser build if possible: web builds get far more plays than downloads, often three to five times as many in my experience.
Rating others is how you get played
On most rated jams, the number of games you play affects how visible your entry is. On itch.io jams and Ludum Dare, people who rate more tend to get rated more, partly from the system and partly because jammers return the favor.
Aim to play and comment on 20 games in the rating week. That is about 20 minutes a day. Write comments that name one specific thing that worked and one thing that confused you. "The double jump felt great, but I did not realize the red tiles were deadly until level 3" helps a developer far more than "nice game." If you want a structure for this, see giving useful feedback on other people's games.
Reply to every comment on your own entry, even the critical ones. Thank people, ask follow-up questions, and note patterns. If three players say the same level is confusing, that is your list for a post-jam update.
After the jam ends
Take two days off. Then write a short post-mortem with three headings: what went right, what went wrong, what I will do next time. Keep it under 500 words. Post it on your itch.io page or your devlog.
Some jam games deserve to grow. If players kept playing after the last level and asked for more, that is a real signal. Most jam entries should simply stay finished, and that is fine. The point of a first jam is the habit of shipping, not the masterpiece.
Frequently asked questions
Do you need to be good at coding to join a game jam?
No. Many jam entries are made in Scratch, Bitsy, Twine or PICO-8, and plenty of first-time jammers learn their tool during the jam. Judges and players care about whether the idea is fun and clear, not how clean the code is.
Can you use pre-made assets in a game jam?
It depends on the rules of each jam. Most community and itch.io jams allow free or pre-made assets as long as you credit them. Strict competitions like the Ludum Dare compo require everything to be made during the event.
How long should a game jam game be?
Aim for 3 to 10 minutes of play. Raters are trying dozens of games, and a short, polished experience gets finished and rated more fairly than a long one they abandon halfway.
More in Community
Community
How to Host a Small Game Jam for Your Own Community
The first jam I organised had 34 people sign up and four submissions.
Community
How to Find a Game Dev Partner for a Small Project
You can code but your art looks like placeholder boxes, or you can draw but every script you write breaks the moment you add a...
Community
How to Handle Negative Feedback on Your Indie Game
You posted your build, waited all evening, and the first comment says the controls feel awful and the art looks like a...