When Max said "each game has to fit in 12KB," I thought he was joking. A single medium-resolution image is 50KB. A basic framework is 30KB compressed. 12KB is smaller than most email signatures. I spent the first hour trying to convince him to raise the limit. He didnt budge. So I started coding, angry and convinced the project was doomed before it began.
The first game I built under the limit was terrible. It was a Flappy Bird clone that took 11.8KB and played like a PowerPoint presentation. No animation, no sound, no score persistence — just a square falling between two rectangles. I was frustrated because I knew I could make it better with more bytes. But the limit was the limit, so I started making tradeoffs I never would have considered otherwise.
What the Limit Forces You to Learn
The 12KB limit teaches brutal prioritization. Every byte has to earn its place. A particle effect library? That's 3KB gone — better be worth three features you're cutting. A high score system? Only if you can implement it in under 200 bytes. Sound effects? You're writing raw oscillator code, not loading audio files.
The first thing that got cut was everything I thought I needed but never actually used: unused variables, debug code, fallback logic for edge cases that never happened. That saved about 4KB. Then I realized I was writing verbose code out of habit. Ugly? Absolutely. But it works and it saved 2KB.
The most painful cuts were features I genuinely wanted. A settings menu with volume control. A tutorial overlay. Three different difficulty modes. All gone. But here's the thing: nobody missed them. Testers didnt ask for a settings menu because the audio was already fine. They didnt need three difficulty modes because the natural difficulty curve was good enough. I was building features for a theoretical player who needed them — not the actual player in front of me.
Smaller Files, Better Games
After the first game, I got faster. The second game took 8KB and had more mechanics than the first. By the fifth game, I was hitting 6-7KB consistently and the games were better than anything I'd built at 30KB+. The constraint changed how I thought about game design. Instead of asking "what can I add?", I started asking "what can I take out without breaking the fun?"
The best example is Gravity Flip. The game uses exactly three visual elements: a rectangle, a line, and a background color. That's it. 4.2KB total, including the gravity flip logic, collision detection, and score counter. Testers consistently rank it in our top five most addictive games. A game thats smaller than this article you're reading. Honest to god, the limitation made me a better developer.
If you're building browser games, set a file size limit. Pick a number that feels unreasonable — 15KB, 10KB, whatever scares you. You'll cut cruft, discover what actually matters, and end up with a game that loads instantly and plays twice as well.