Your First Game Jam: What to Expect and How You Can Help

Your first game jam is a chance to help make a small game within an event’s rules and time limit. You do not have to arrive with a studio-sized idea. Look for a jam that fits your experience, available time, and the kind of work you want to try.

A jam is an event, not a game genre or a promise that every entry will become a finished commercial release. The useful starting question is not “Can we build our dream game?” but “What can we make playable together?”

A game jam is not always a weekend competition

The Ludum Dare FAQ defines game jams as events where games are made. It says many last a few days or a week, while others run for hours or as long as a month. Competitive jams add winners, but competition is not part of every jam.

The itch.io documentation describes another important split: some jams happen online, while others connect to a physical gathering. Ranked jams can include voting after submissions close; non-ranked jams do not need a leaderboard.

Choose the format before choosing a project. A relaxed community event and a judged contest may ask for very different things from the same beginner.

What can you contribute without programming?

Writing code is only one possible contribution. For example, the University of Waikato’s 2026 Global Game Jam site invited people to identify skills including art, game testing, graphic design, storytelling, writing, and programming. It also allowed people to arrive individually and form teams at the event.

Here are examples of small tasks you could offer a team. The team’s needs and the event’s rules still decide which roles are useful.

Interest	A focused contribution
Art or graphic design	Create a small set of character poses, icons, or readable menu elements.
Writing or storytelling	Write a short scene, clear instructions, or concise item descriptions.
Playing and testing	Try a build without coaching and note confusing controls, broken actions, and unclear goals.
Programming	Build one interaction or help connect a teammate’s work to the playable game.

Be honest about what you can finish. “We can use three icons by tomorrow” gives a team something clearer to plan around than a promise to handle all the art.

The result can be a prototype, or even a board game

Waikato’s organizer page describes teams making video games or board games around a revealed theme. Its 2026 event included a local showcase and asked participants to upload both finished and partially built games.

A prototype is a small version used to show or test an idea. A jam entry can therefore be worth sharing even when it has rough art or a short play time. Follow the organizer’s submission requirements rather than assuming an unfinished entry is always accepted.

Read the rules before using tools or assets

An asset is a piece of content such as an image, sound, font, or 3D model. Permission to use an asset and permission to use it in a particular jam are separate checks.

The GMTK 2026 rules provide a concrete example. That completed event allowed pre-existing code and legally usable art and audio, required credit for external art and audio, and prohibited generative-AI art or audio for the game and its itch.io page. Those rules should not be assumed to apply to every other jam.

• Eligibility: Check age requirements, team rules, and whether you need to attend a venue.
• Time: Confirm the submission deadline and its time zone, not just the event’s headline dates.
• Tools and content: Check restrictions on engines, pre-made work, external assets, and AI.
• Submission: Confirm supported platforms, required files, credits, and whether updates are locked during judging.

The same GMTK event required a game playable on a Windows PC with a keyboard or mouse, with a browser version also accepted. A working project in your editor is not automatically a usable submission.

Keep the first project small enough to share

We suggest choosing one central action and a clear stopping point. A single room, one puzzle, or a short conversation can give your team a concrete target without requiring a large world.

Leave room for someone outside the team to try it. Ask what they understood, where they got stuck, and whether they could finish without help. Treat those answers as feedback on the game, not a judgment of your talent.

Before committing, read the current event page and ask the organizer whether beginners can join without a team. A clear role and a manageable idea are more useful than trying to learn every part of game development at once.