These 48 hour game jam tips are built around one hard truth: your first jam isn't won by talent, it's won by finishing. Most first-timers submit nothing — not because they can't code, but because they scoped a game they could never build in a weekend and burned out at hour 30 with a half-broken project.
Scope smaller than feels comfortable
The single biggest mistake is picking a game with too many moving parts. Cut until it hurts, then cut again. A jam game should be one verb the player does, in one screen, toward one clear goal.
Write your idea as a single sentence: "You're a X who does Y to achieve Z." If you need the word "and" more than once, it's too big. Good jam-sized ideas:
- Dodge falling rocks until a timer runs out.
- Stack blocks without toppling the tower.
- Sort incoming orders before the queue overflows.
Bad jam-sized ideas: an open world, a crafting system, procedurally generated levels, online multiplayer, a branching dialogue tree. Those are month-long features, not weekend ones. If you have a big vision, ship the smallest playable core of it and label the rest "post-jam."
Plan the 48 hours before you write code
Time is the enemy, so spend the first hour planning instead of coding. A rough timeline keeps you honest:
- Hours 0–2: Read the theme, brainstorm, lock ONE idea. Sketch the single screen on paper.
- Hours 2–8: Build the core loop with ugly placeholder shapes — grey boxes are fine. Get the main verb working.
- Hours 8–12: Sleep. Yes, really.
- Hours 12–24: Make it a game — win/lose states, a score, a difficulty curve, a start screen, a restart button.
- Hours 24–34: Art, sound, and "juice" (screen shake, particles, feedback).
- Hours 34–42: Playtest, fix the worst bugs, balance the difficulty.
- Hours 42–46: Build, export, and TEST the build. Write the submission page.
- Hours 46–48: Buffer for everything that goes wrong. It will.
The exact hours flex, but the shape matters: playable early, polished late, submitted with time to spare.
Get to "playable" by the end of day one
Your goal for day one is not a pretty game — it's a boring but complete loop you can play from start to finish. If by the end of day one you can lose, see a score, and press restart, you already have a jam entry. Everything after that is upgrading something that already works.
This flips the usual failure mode. People who polish art before the loop exists end up with a gorgeous main menu and no game. Build the skeleton first; decorate the skeleton second.
Cut features without mercy
Keep a "cut list" open right next to your "to-do list." Every hour, move anything you won't finish onto the cut list without guilt. Enemies with three attack patterns? Cut to one. Five levels? Ship one good level. A tutorial? Replace it with a single line of on-screen text.
A useful rule: if a feature isn't visible to the player in the first 30 seconds, question whether it earns its build time. Judges and players spend about two minutes with your game. Spend your hours on what those two minutes actually touch.
Protect your body and your brain
Burnout is a scoping problem wearing a health costume. You cannot code well at 4am on no sleep, and a tired brain writes the bugs that eat hour 40. Treat rest as part of the strategy:
- Sleep at least once. A pulled all-nighter costs you more the next day than it buys you tonight.
- Eat and drink on a timer, not when you remember. Prep food before you start.
- Take a 5-minute walk every couple of hours. Half your bugs solve themselves away from the screen.
- Commit often (git, or even zipped folders). Losing three hours of work to a crash is a real jam-killer.
Leave real time to build and submit
More entries die at submission than in development. Do a full export at hour 30 even if the game isn't done — that "practice build" surfaces the problems (broken paths, missing files, a WebGL build that won't load) while you still have time to fix them. Never let your first build be your final build.
When you export for the web, test the actual uploaded build, not just the editor. A game that runs in Unity but hangs in the browser is a game nobody plays.
Submit it, then share it
The finish line is a submitted, playable link — imperfect and shipped beats perfect and private every single time. If you're still choosing an event, our guide on how to join an online game jam walks through picking one and reading the rules, and if you're stuck on what to make, browse game jam ideas for beginners for scoped-down starting points.
When your entry is done, put it somewhere people can actually click and play. On The Gaming Nest you can publish your WebGL build as an instant, no-download page and share one link with judges and players across the Arab world — the fastest way to turn a weekend of work into real plays and feedback. Finish first, polish later, and get it in front of players.