Why So Many Modern Casual Games Are 3D Now

A Shift Most Players Did Not Notice

Browser-game portals used to be mostly 2D. Top-down arcade titles, side-scrolling platformers, sprite-based match-three games. The occasional pseudo-3D game using 2D-with-perspective tricks. True 3D was the exception, reserved for a handful of high-end web games that did not run well on most machines.

Open a portal today and there is more 3D than there used to be. Top-down arcade titles using 3D models with stylised lighting. Side-scrolling games with depth-of-field. Match-three games with physics-driven board pieces that bounce and rotate in three dimensions. The 2D games are still around, and still plentiful, but 3D is no longer the exception.

The shift happened gradually enough that most players did not notice. But it was real, and the reasons it happened are interesting — they have less to do with players demanding 3D and more to do with what 3D became cheap to ship.

What Changed Technically

The simple version: rendering a 3D scene used to be expensive enough that only specialised engines could do it well in a browser, and the specialised engines required specialised developers, and the specialised developers were expensive. Casual game studios stayed 2D not because they preferred it but because 2D was tractable for the team they could afford.

What changed:

WebGL became universal. WebGL, the browser's interface to the graphics card, reached all the major browsers by the mid-2010s, but developers who knew it well took several more years to become common, and for a while that skill came at a premium. As more developers learned it, a 3D browser game stopped being an exotic project.

Three.js commoditised the basics. Three.js, a JavaScript library that wraps WebGL with a more approachable API, became one of the most widely used libraries for browser 3D. Many casual 3D browser games use Three.js or a similar high-level wrapper such as Babylon.js or PlayCanvas. The library handles the boring parts (camera math, asset loading, shader management) and leaves the developer free to focus on the actual game.

Game engine ports filled the gap for studios. Engines such as Unity and Godot can export to the web. A studio that already had a Unity-fluent team could ship to the web with their existing 3D skills. The 2D-only constraint became a 2D-by-choice option, not a 2D-by-necessity ceiling.

Mobile hardware caught up. A 3D scene that was a stretch for a mid-range phone some years ago is routine for a recent one, and a large share of the audience for browser games is on phones. The hardware to support 3D games finally arrived where the players are.

The cumulative effect is that 3D became the path of least resistance for many casual game projects. 2D is still chosen sometimes for specific aesthetic reasons, but it is no longer the default that 3D has to overcome.

What Changed Aesthetically

The aesthetic shift mattered as much as the technical one. Two distinct trends drove it:

Stylised low-poly became hot. Through the early 2010s, the aesthetic ambition of 3D was photorealism — game studios chasing the visual fidelity of AAA productions. Photorealism is expensive, slow to produce, and visually competitive (the next game is always going to look better than yours). A different aesthetic emerged in parallel: stylised low-poly. Crossy Road and Hipster Whale's broader catalog (native mobile games rather than browser games) showed that a 3D game could look distinctive, sharp, and finished with a fraction of the asset budget of photorealistic competition. The stylised look was arguably better for casual games — clearer at small sizes, more recognisable on a phone, easier to develop. Once a few hits proved the aesthetic worked, many casual developers followed.

3D physics became a selling point. 2D physics is fine; 3D physics is more interesting. Objects can fall in two dimensions, but they can roll, bounce, slide, and tumble in three. The entire genre of "physics-based casual games" benefits from genuine 3D physics in a way that 2D versions of the same concepts do not. The same is true for racing games, marble runs, and most physics-puzzle subgenres. The physics is the gameplay, and 3D physics gives the gameplay more dimensions to play in.

3D gave casual games a way to look "premium." 2D casual games, fairly or not, often read as cheap. Pixel art carries indie credibility but also has a "I made this in a weekend" connotation. 3D, even in a stylised low-poly form, reads as polished — the player assumes the developer invested in the visual language. For studios trying to differentiate from the perceived bottom of the casual market, 3D became a signal of seriousness. The signal was somewhat circular (3D is "premium" because premium games are 3D), but circular signals are still signals.

Where 2D Still Wins

To be fair to 2D, there are still real categories where it dominates:

Pixel-art retrocore. Anything that wants to lean into 80s/90s arcade aesthetics. Pixel art is intentional in these cases, not a budget constraint. Recent successes like Vampire Survivors, Balatro, and most of the indie roguelike scene are unapologetically 2D for aesthetic reasons.

Card games and deckbuilders. Cards are 2D objects. A 3D card game would be perverse. The category has refined 2D presentation to a high art — clean iconography, readable card faces, smooth in-and-out animations. There is no upside to forcing 3D here.

Puzzle games with grid logic. Match-three, Tetris-likes, Sudoku, sliding-tile puzzles. The gameplay is on a flat grid. Some recent entries dress the grid in 3D (with pieces that rotate and bounce), but the underlying game is 2D, and pure-2D versions remain perfectly viable.

Text-heavy games. Visual novels, narrative games, anything where the writing is the primary content. Adding 3D to these mostly makes them worse — the reader's eye should be on the words, not on the 3D environment.

So 2D is not dead. It is a deliberate aesthetic choice for projects that benefit from it, the way 3D used to be a deliberate technical choice.

How Much of the YoyoArena Library Is Really 3D

Everything above is about the industry. The 23 games in the YoyoArena library are a small sample from one site, not a measurement of anything wider, but their source code gives a precise answer to a vague question: how 3D is a game that runs on a 3D library? The figures below were read from the games' source code and are those at the time of writing.

Eleven games use Three.js, and three of them have depth. Eleven games draw with Three.js, a library built for 3D scenes; How Modern Browsers Actually Run a Game counts the split between Three.js, Phaser and plain Canvas 2D. Only three of the eleven view their scene through a perspective camera, the kind that makes distant objects look smaller: Cube Jump, Perfect Stack and Rollout. The other eight, Snake, Brick Breaker, Focus Fire, Gravity Rush, Neon Blaster, Orbit Rush, Perfect Shot and Rope Snip, use an orthographic camera, which draws every object at the same size however far away it is. In all eight the camera sits on the z axis and is never rotated or tilted. On screen they are 2D games that happen to be drawn through a 3D library.

Light and shadow separate the three from the eight. Cube Jump, Perfect Stack and Rollout each create three lights (one ambient and two directional) and turn on shadow mapping. None of the eight orthographic games creates a light at all.

No game ships a model. None of the 23 games contains a 3D model file (glTF, OBJ or FBX) or loads one. The only image files a Three.js game loads as textures are flat SVG pictures, and only two of them do it (Brick Breaker and Neon Blaster); the rest draw their shapes from code. The "meshes" part of the asset bill described in this essay therefore does not apply to this library, which is why the size figures in the engine post are dominated by the engine.

What that does to the essay's thesis. The trend described above is real in this library but narrower than the word "3D" suggests: eleven of 23 games run on a 3D library, and three of the 23 have a perspective view. Whether the same gap between "uses a 3D library" and "is 3D" exists on other portals is a question for someone with a bigger sample.

What This Means for Browser Game Portals

For anyone running a portal of casual games, the shift to 3D has practical implications.

Performance vetting matters more. A 2D game runs fine on almost any hardware. A 3D game on an older phone can fall well short of 60 frames per second if the developer was not careful. Portals that add 3D titles to their library need to test on lower-end devices, not just whatever the developer's testing rig is.

Load times are a bigger deal. A 3D game's asset bundle is usually larger than the 2D equivalent — meshes, textures, shaders all add bytes. Portals that promise "instant play" need to vet for this. A 3D casual game that takes many seconds to load is going to lose players that a quick-loading 2D game would have retained.

Aesthetic consistency takes more work. A 2D-only library has a natural visual unity (everyone is drawing on flat surfaces). A mixed 2D/3D library can look incoherent without thoughtful curation. The portal has to do more visual editing — picking 3D games whose stylised palettes feel related to each other, picking 2D games whose pixel aesthetic feels intentional.

Mobile-first remains the rule. The audience for casual 3D games is primarily mobile. Portals that prioritise desktop-3D-first will misread the market. The 3D casual games that worked at scale (Crossy Road and Stack, for example) were mobile-first or mobile-equivalent. Desktop play is fine, but it is a courtesy fallback, not the primary platform.

Why This Matters Beyond Aesthetics

The 2D-to-3D shift in casual gaming is interesting because it shows the medium maturing. A medium that has only one viable production technique is constrained. A medium where both 2D and 3D are equally accessible to small developers is one with a wider design space.

What 3D specifically opened up: physics-driven puzzles that would not work flat, stylised low-poly aesthetics that read better on phones, casual racing games that compete with native-app racing experiences, and a more "premium" perceived quality bar for the whole category.

What may come next: as WebGPU, a newer graphics interface than WebGL, arrives in browsers (support is still partial in Safari and Firefox, see Sources), the ceiling on what a 3D browser game can do may move up another notch. Effects that are currently expensive (real-time shadows, dynamic lighting, complex post-processing) may become cheaper, and the visual gap between native and browser 3D games may narrow. None of YoyoArena's 23 games uses WebGPU today.

Most players will not notice. The games will just look a little better, run a little smoother, and feel a little more substantial. The platform is doing the work; the player is enjoying the result.

Sources

• WebGPU support tables (caniuse): Chrome and Edge from version 113, Safari from 26 and Firefox from 141, the last two with partial support.