In November 2025, something happened to your browser that you almost certainly didn’t notice. WebGPU, the interface that lets web code speak directly to your graphics card, became officially supported across Chrome, Edge, Firefox and Safari, a milestone Google’s Chrome team announced on 25 November and described as the biggest web graphics launch since WebGL.
Put simply, the code running in a tab can now reach your GPU in much the same way an installed game does. If you play at a browser-based platform such as Vegastars casino, you can see how modern casino games increasingly rely on web technologies to deliver game lobbies, animations and account access without requiring a separate app download.
What follows leans on records rather than promises: Adobe’s own end-of-life documentation, browser vendor release notes, the Khronos Group, the changelogs of the rendering libraries themselves and Chorus connection reporting for the New Zealand side.
No marketing pages. And there’s a good question sitting underneath all of it. Of all the categories that could have led the charge into serious browser graphics, why did casino games get there first?
They had a deadline.
The Deadline That Rebuilt Everything
Most software modernises gradually. Casino studios weren’t given that option.
Adobe stopped distributing and updating Flash Player after 31 December 2020, then began blocking Flash content from running inside the player on 12 January 2021. The final update shipped on 8 December 2020, as The Verge reported at the time.
Nobody was ambushed. Adobe announced the plan in July 2017, working with Apple, Facebook, Google, Microsoft and Mozilla, giving the industry three and a half years to prepare. Adobe also named the replacement stack outright in its enterprise end-of-life notes: HTML5, WebGL and WebAssembly.
That’s a vendor handing every studio a set of blueprints.
Forrester analysed the same moment and laid out three routes for any Flash-dependent business in The End Of Flash: retarget the content to HTML5, rewrite core applications in modern frameworks, or retire the content altogether.
Plenty of companies chose retirement. Studios with thousands of games and players logging in daily couldn’t, so they took the expensive road and rebuilt.
A forced rewrite is a strange sort of gift in software, because it lets you design for the device people are holding now rather than the one they owned in 2009. Everything that came next flowed from that.
You can see the result in any modern lobby. Vegastars, for instance, runs its full library in the browser on iOS and Android with nothing to download, carrying over 5,000 pokies and live titles. That reach came straight out of the rebuild rather than being bolted on afterwards.
Meet the Machinery Behind the Curtain
So why does a game packed with movement load in a couple of seconds? Clever compression only gets you so far; the bigger gain comes from how the animation is stored in the first place.
Traditional sprite animation saves a separate image for every single frame, which balloons file sizes fast. Skeletal animation works differently.
Spine, from Esoteric Software, attaches artwork to bones and animates the bones, and the developer credits this approach with smaller file sizes, fewer art assets to produce and smoothness that adapts to whatever frame rate the device can manage.
The movement isn’t baked at 30 frames per second and shipped. It’s calculated live, so a better screen gets a better result from the exact same download.
Spine also ships runtimes for HTML5, JS, Unity, C++, iOS and Android, meaning one animation export can serve every platform a studio supports. Its own showcase notes it’s used across mobile and desktop games, interactive storytelling and film, by studios of every size.
The rest of the stack is similarly borrowed rather than bespoke:
- WebGL and WebGPU: the pipes carrying browser code through to your graphics card
- PixiJS: the 2D renderer that draws thousands of moving objects without stalling, which launched version 8 in March 2024 with a WebGPU renderer alongside its WebGL one
- Spine: bone-based animation keeping downloads small while movement stays fluid
- Three.js, Babylon.js and PlayCanvas: the 3D side, all now WebGPU-capable, with Three.js adding its renderer from r163
- WebAssembly: lets code written in other languages run at near-native speed inside the tab
None of this was built for casino games. The studios were simply the ones with both the budget and the hard deadline to adopt it at scale before anyone else.
It stacks up in practice, too. On the live side, Vegastars streams HD dealer tables from Evolution and Pragmatic Play Live studios straight into the browser on any device. Video streaming and GPU rendering sharing one tab is a fair measure of how much your browser handles these days.
Why It Looks Better From Here?
Beautiful rendering counts for nothing if the assets crawl down the wire. This is where New Zealand does rather well.
Chorus reported fibre uptake of 72.1% of passed addresses in its Q4 FY25 update, covering 1,115,000 connections. A global fibre uptake report cited in the same quarterly reporting places us 19th worldwide, sitting just behind Sweden and Japan.
Then came the Big Fibre Boost, completed in June 2025, which lifted 50/10Mbps home plans to 100/20Mbps and 300/100Mbps plans to 500/100Mbps at no extra wholesale cost to retailers. The entry-level Kiwi connection doubled overnight.
Average monthly fibre usage climbed to 671GB in June, up from 642GB in April, with roughly 17% of connections passing a terabyte a month. A quarter of Chorus residential connections were already on 1Gbps or better as at Q3 FY25.
Fibre uptake across the main centres:
| Location | Fibre uptake | Detail |
|---|---|---|
| Auckland | 76.4% | Flat, with new addresses outpacing connections |
| Dunedin | 76.4% | Up 1.6% on the student return |
| Wellington | 70.8% | Up 0.3% |
| Chorus national | 72.1% | 1,115,000 connections, Q4 FY25 |
Studios noticed. Once you can assume most of your audience has real bandwidth, art directors get permission to use larger textures, layered audio and full intro sequences.
A library drawing on Pragmatic Play, Play’n GO, NetEnt, Push Gaming, Hacksaw Gaming, BGaming and PG Soft, as independent NZ reviews of Vegastars document, means dozens of separate art teams and engine choices all arriving through one tab, with an NZD cashier handling the local end.
So when did you last sit and watch a game load? The waiting bar vanished so gradually that most of us never registered it going.
The Restraint That Keeps It Smooth
Faster pipes and better tooling still leave one judgement call: when to actually switch the newest thing on. The smartest engineering decision in browser graphics right now might be knowing to leave it off.
PixiJS launched v8 with WebGPU as its default renderer. Then, in v8.1.0 that April, the maintainers reverted the default back to WebGL, citing inconsistent WebGPU behaviour across browsers and choosing a consistent experience for the majority of users. WebGPU stayed available as an opt-in.
Reading the rollout timeline in Chrome’s own WebGPU overview, you can see why they waited. Chrome shipped WebGPU first in version 113, covering Windows via Direct3D 12, macOS and ChromeOS. Android followed in Chrome 121, limited to devices on Android 12 or later with Qualcomm or ARM GPUs.
Firefox reached Windows in version 141 and added Apple Silicon macOS support in 145. Safari arrived with version 26 across macOS Tahoe, iOS, iPadOS and visionOS.
François Beaufort of the Google Chrome team, writing in Chrome’s WebGPU ecosystem documentation, explained: ‘WebGPU is often perceived as a web graphics API that grants unified and fast access to GPUs by exposing cutting-edge hardware…’.
That access is now broad. At the Khronos Group’s 3D on the Web event during GDC 2026 in San Francisco, the position given was that WebGPU is available in all major browsers on most platforms, with WebGPU compatibility mode shipping on Chrome for Android in February 2026.
Compatibility mode is the line that counts for us, because it extends WebGPU to older and mid-range phones rather than flagships alone.
Reach has always been worth more than peak performance in this category. New titles land weekly on Vegastars from studios building on the newer stack, which is how most players will meet this technology without ever opening a release note.
The Tab Stopped Apologising
The interesting outcome here goes beyond browser games catching up with installed ones. The browser became the default target, installed software became the special case, and a category few people associate with technical ambition helped fund the tooling everyone else now uses for free.
With WebGPU shipping by default across the major browsers and compatibility mode reaching modest Android hardware, the ceiling has lifted while the price of entry hasn’t moved. You still need a browser and a link.
Next time a Vegastars game opens instantly and moves without a stutter, that’s roughly fifteen years of standards work, one immovable date in December 2020 and a fibre network most of us stopped thinking about years ago.
Responsible Gambling Notice: Gambling should be treated strictly as entertainment, not as a way to make money. Players should set clear spending and session limits before playing, avoid chasing losses, take regular breaks and stop if the experience no longer feels enjoyable or affordable. 18+ only.
