Start Building

Running a game jam can grow your community, give developers a deadline to ship, and create a library of playable games. The best jams feel focused and fair: clear theme, clear rules, and the right tools so everyone can spend time making games instead of fighting logistics. This guide covers planning and tools so you can run a jam that people finish and remember.

1. Define the Jam - Theme, Duration, and Rules

Theme
Pick a theme that is broad enough for variety but specific enough to spark ideas. Examples: "One Button", "Reverse", "Under 10 Minutes to Complete", "Lost and Found". Announce the theme at the start so everyone has the same constraint and can brainstorm.

Duration

  • 48–72 hours – Classic weekend jam; enough time for a small scope and sleep.
  • 7–14 days – Good for online jams where people have day jobs; scope can be a bit bigger.
  • 24 hours or less – High intensity; best for experienced jammers or micro-jams.

Rules
State what is allowed in plain language: engine (any? Unity/Godot/Unreal only?), assets (from scratch only? free/CC only? bought?), team size (solo vs teams), and whether existing code is allowed. A short rules page avoids arguments and keeps judging fair.

2. Schedule and Milestones

  • Announce the jam (theme, dates, platform) at least 1–2 weeks ahead so people can block time.
  • Start at a fixed time (e.g. Friday 5pm UTC) and end at a fixed time (e.g. Sunday 5pm UTC). Use a countdown or count-up timer on the jam page.
  • Submission window – Allow a short buffer (e.g. 30–60 minutes) after the end time for uploads and form submissions.
  • Voting/judging – If you have community voting or judges, set a clear period (e.g. one week) and when results go live.

3. Where to Host and How to Collect Submissions

Hosting the jam

  • itch.io – Create a jam page, set start/end, theme, and rules. Participants submit by submitting their game to the jam. Built-in voting and discovery.
  • Other options – Discord + Google Form, custom site, or a mix: e.g. itch.io for submissions and Discord for chat and announcements.

Submission form
Collect at least: game link (itch, drive, or build URL), team name, short description, and optional screenshot/video link. Keep the form short so people do not drop off at the last minute.

Pro tip: Remind participants to test their build and submit the correct link before the deadline. A "submit early" reminder 2–4 hours before the end reduces last-minute mistakes.

4. Tools for Organizers and Participants

For you (organizer)

  • Timer – itch.io has one; otherwise use a shared countdown (e.g. timeanddate.com).
  • Announcements – Discord, Twitter/X, or email so everyone sees theme, reminders, and rule clarifications.
  • Spreadsheet or form – To track submissions, judge scores, or give feedback.
  • Playable builds – Prefer web (itch.io HTML5) or one-click downloads so judges and players can try games quickly.

For participants

  • Engine – No requirement, or suggest Unity/Godot/Unreal if you want a level playing field.
  • Version control – Recommend Git (GitHub/GitLab) so teams can collaborate and you can verify "made during the jam" if needed.
  • Assets – List allowed sources (e.g. Kenney, OpenGameArt, own assets, no third-party).
  • Communication – Discord or similar so jammers can form teams, ask questions, and share WIP.

5. Judging and Prizes (Optional)

  • Criteria – Fun, theme adherence, creativity, polish. Publish the criteria so submissions are aligned.
  • Voting – Community vote (itch.io), judge panel, or both. Set a clear period and how winners are chosen.
  • Prizes – Optional: certificates, feature on your site, small cash, or asset/store credits. Even "no prizes" is fine if the jam is framed as practice and portfolio.

6. After the Jam

  • Thank participants and highlight a few games (e.g. "Jam Picks") in a post or newsletter.
  • Publish results (winners, links to all games) so everyone gets visibility.
  • Ask for feedback (short form or Discord) so you can improve the next jam.
  • Archive the jam page and submission list so the games remain discoverable.

Summary

A successful game jam needs a clear theme, clear rules, and a fixed schedule so everyone knows what to build and when to submit. Host on itch.io (or similar), use Discord for chat and announcements, and keep submissions simple. Give participants the right tools (engine, assets, version control) and a short submission buffer. Optional judging and prizes can add motivation; after the jam, thank everyone and showcase games so the community grows. For more on shipping under pressure, see our game development guides and Build a Complete Game in Godot 4 course.

Bookmark this guide when you plan your next jam. Share it with your dev friends if it helped.