Website review
This review may include AI-generated content and is not individually verified. Domain, certificate and other facts come from the observed data on this page.
What is Ludum Dare?
Ludum Dare is a recurring online game jam where participants build a complete game from scratch in a short, fixed time window. It's best known for its flagship 48-hour solo event and a parallel 72-hour event that allows teams, assets and a bit more breathing room. The core constraint is the point: you start with a theme announced at the opening and submit a playable game before the clock runs out.
The event has run for many years, which gives it a large back catalogue of entries and a community that expects rapid, rough-around-the-edges prototypes rather than polished commercial releases. Entries are typically judged by other participants across categories like fun, innovation, theme adherence, audio and graphics. That peer feedback loop is often the main draw for newcomers.
Who it suits
- Beginners: the deadline forces you to finish something small, which is the hardest habit to learn.
- Solo developers: the 48-hour track is designed for one person doing code, art and sound.
- Teams: the 72-hour track lets you split roles and use pre-made assets.
- Portfolio builders: a finished jam game is concrete evidence you can ship.
Trade-offs to expect
- Scope discipline matters more than technical ambition; oversized ideas rarely finish.
- 48 hours is genuinely punishing if you also handle art and audio.
- Judging is community-driven, so feedback quality varies and scores aren't a professional review.
A practical next step
Before the next event, pick a tiny genre you already understand—a one-screen arcade loop or a short narrative scene—and prototype it in a single evening. If you can finish that in a few hours, you're ready for 48. If not, enter the 72-hour track or join a team. Check the official site for current dates and rules at Ludum Dare.
How do I participate in Ludum Dare?
Participation happens on Ludum Dare itself: you register an account, then wait for the next event's announcement, which sets the theme and the exact start and end times. When the event opens, you build a complete game from scratch within the time limit and submit it through the site before the deadline.
The two tracks
| Track | Time | Typical approach |
|---|---|---|
| Compo | 48 hours | Solo only; all art, code and audio made during the event; source code shared |
| Jam | 72 hours | Teams allowed; can use pre-made assets and libraries; source sharing optional |
Pick Compo if you want the classic solo sprint and don't mind publishing your source. Pick Jam if you need a team, want to use existing tools or asset packs, or simply need the extra day.
A realistic first run
If you've never done one, treat the first attempt as a rehearsal rather than a competition. Decide on a tool you already know (a general engine or a simple framework), sketch a single mechanic that fits almost any theme, and practise finishing a tiny game in one weekend beforehand. During the event, aim to have something playable by the halfway mark, then use the remaining time for polish and a build that runs on other people's machines.
After you submit
The event continues with a judging phase: you play and rate other entries, and they rate yours. Rating is part of participating, not an optional extra — most feedback and visibility comes from it. Games are then ranked, with separate categories such as fun, innovation, theme, graphics and audio.
Practical checks before the clock starts
- Confirm the deadline in your own timezone, not the site's.
- Test that you can upload and that your exported build runs on a clean machine.
- Prepare a short description and screenshots in advance.
- Keep scope small enough that a broken feature can be cut without killing the game.
A useful next step is to read the rules and past entries on the site, then block out the event weekend in your calendar so the theme reveal doesn't catch you unprepared.
What is the difference between the 48-hour and 72-hour Ludum Dare challenges?
The 48-hour and 72-hour Ludum Dare challenges differ mainly in time limit, team rules, and how much of the game must be made from scratch.
Quick comparison
| 48-hour (Compo) | 72-hour (Jam) | |
|---|---|---|
| Time limit | 48 hours | 72 hours |
| Team | Solo only | Teams allowed |
| Assets | Must be created during the event | May use pre-made assets (with some conditions) |
| Source code | Must be shared | Not required to be shared |
| Overall tone | Stricter, more competitive | More relaxed, beginner-friendly |
The 48-hour version is the classic "compo": one person, two days, everything built from scratch, and you release your source. The 72-hour version is the "jam": you get an extra day, you can work with others, and you can bring in existing art, music, or code, which makes it far more approachable if you have limited time or want to focus on one skill.
How to choose
- Pick 48 hours if you want the pure solo challenge, enjoy the pressure, and are comfortable making your own art and audio.
- Pick 72 hours if you want to collaborate, have a day job or school commitments, or want to use assets you already own.
Both run against the same theme, so the real decision is whether you value the stricter constraints or the extra flexibility. If you are new, start with the 72-hour jam; if you have finished a few games already, try the 48-hour compo for a sharper test. You can check current dates and rules at Ludum Dare.
What tools and game engines can I use to make a Ludum Dare game?
Any engine or framework works. Ludum Dare is a game jam, not a platform, so there is no approved tool list. You pick what lets you finish a playable game in 48 hours (solo) or 72 hours (with a team), and you submit the result through Ludum Dare. The real constraint is your own familiarity, not the tool.
Common choices and who they suit
| Tool | Best for | Trade-off |
|---|---|---|
| Godot | 2D-first solo entries, fast iteration | Smaller asset/plugin ecosystem than Unity |
| Unity | 2D or 3D, lots of tutorials and assets | Heavier setup; easy to over-scope |
| Unreal Engine | 3D entries, strong visuals | Long build/compile times eat jam hours |
| GameMaker | Fast 2D prototypes, pixel art games | Less suited to complex 3D |
| PICO-8 / TIC-80 | Tiny, constrained fantasy-console games | Hard limits on size and scope |
| LÖVE, Pygame, Phaser, raylib | Coders who prefer writing systems themselves | You build menus, saves and editors yourself |
Non-engine tools matter just as much: Aseprite or Piskel for pixel art, Krita or Photoshop for 2D, Blender for 3D, Audacity or sfxr/jsfxr for sound, Bosca Ceoil or LMMS for music, and Trello or a paper list for scoping.
A practical way to decide
Pick the tool you already know, not the one you want to learn. A jam is a bad time to learn a new engine's quirks. Then cut your idea until the core loop is playable within the first third of the time you have.
For example, if you have 48 hours and have never shipped a game, a 2D engine plus a one-mechanic idea — jump, dodge, one enemy type — is far more likely to produce a finished, ratable entry than a 3D project with custom shaders.
Next step
Check the current event's rules and submission requirements on Ludum Dare before you start, since theme, deadlines and category rules change per event. Then do a two-hour test: build a moving character with one interaction in your chosen tool. If that feels slow, switch tools before the jam begins, not during it.
How are Ludum Dare games judged and rated?
Ludum Dare games are judged by the community, not by a panel of experts. After a jam ends, participants and other registered users play the submitted games and rate them against a set of criteria. The game with the highest overall average across those criteria wins.
<h3>Rating criteria</h3>
Ludum Dare typically uses a short list of categories, often including:
- Fun — how enjoyable the game is to play
- Innovation — how original the idea or mechanics feel
- Theme — how well the game interprets the jam's announced theme
- Graphics — visual quality and coherence
- Audio — music and sound design
- Mood — atmosphere and emotional impact
- Overall — a holistic score
Each criterion is rated on a numeric scale, commonly 1 to 5 stars. Your overall ranking is usually calculated from the average of all your ratings, and you also get per-category rankings so you can see where your game stood out or fell short.
<h3>Who can rate, and how feedback works</h3>
Rating is open to the community during a defined judging window after submissions close. Many participants rate games to receive ratings in return, so the system rewards playing and commenting on other people's entries. Written comments are separate from scores and are often the most useful part of the feedback.
<h3>Practical implications for a jam entry</h3>
- Finish and polish — an incomplete game usually scores poorly on Fun and Overall even if the idea is strong.
- Make the theme obvious — if raters can't see how your game fits the theme, the Theme score suffers.
- Keep sessions short — raters have many games to get through; a game that explains itself in seconds gets rated more fairly.
- Audio and mood are cheap wins — a simple sound effect or consistent art style can lift several categories at once.
If you want the exact current criteria, scale, and judging dates, check the rules page on Ludum Dare closer to the event, since the format has been adjusted between editions.
Can I join Ludum Dare if I have never made a game before?
Yes. Ludum Dare is explicitly built around making a complete game from scratch in a single weekend, and first-timers join every edition. The format is the point: a short deadline pushes you to finish something small rather than polish something large.
Ludum Dare itself is the event hub — rules, themes, submission and voting all happen there, and the site is JavaScript-dependent, so plan to browse it in a normal browser rather than a text-only reader.
What the two tracks mean for a beginner
| Track | Time | Best for |
|---|---|---|
| Compo | 48 hours, solo, assets made during the event | A first-timer who wants the full constraint and doesn't mind rough edges |
| Jam | 72 hours, teams allowed, some pre-made assets permitted | Someone who wants a bit more slack or help from a friend |
If you have never made a game, the Jam track is usually the gentler entry: the extra day matters more than you expect, and teaming up with one other person covers a skill you lack.
A realistic first-time approach
Pick a tool you can already use, not the one you aspire to learn. A beginner who knows a little Python, JavaScript or a drag-and-drop engine will finish more often than someone spending Saturday learning a new engine. Scope to something you can build in roughly a third of the available time — a one-screen game with one mechanic, one win condition and one lose condition. Then use the remaining time for the parts beginners underestimate: sound, a title screen, and uploading your entry before the deadline.
Feedback is a core part of the event, so budget time after submitting to play and rate other people's games; that is where most of the learning happens.
Next step
Read the current rules and theme announcement on Ludum Dare, then do a two-hour practice run this weekend: build a tiny playable thing, export it, and upload it somewhere. If that feels manageable, the real event will too.
User reviews (0)