Cinevva

English

简体中文
한국어
हिन्दी

English

简体中文
한국어
हिन्दी

Appearance

Game Engines for WeChat Mini Games (2026) ​

Game engines for WeChat Mini Games in 2026

WeChat Mini Games (微信小游戏) are the biggest games platform most Western developers have never shipped to. More than 500 million people play them every month, inside the same app they use to message friends and pay for lunch. There's no install, no app store, no download screen. A player taps a link and the game runs.

The catch is that a Mini Game is not a normal web game. It runs in a JavaScript sandbox with no DOM and no HTML, on a custom canvas the platform hands you, and your first package cannot exceed 4 MB. Which engine you pick decides how much of that fight you have to have yourself. This guide compares the real options in 2026.

If you're choosing a browser engine in general first, our web game engines comparison covers the wider field. This page is only about the engines that ship to WeChat.

What makes a WeChat Mini Game different ​

Before the engine choice makes sense, three constraints matter.

There's no DOM. The Mini Game runtime is a bare JavaScript environment with a canvas and a WebGL (and increasingly WebGPU) context, plus WeChat's own APIs for storage, audio, networking, and the social layer. Anything that assumes document, window, or an HTML element has to go through an adapter that fakes those objects. Every engine below ships that adapter.

The 4 MB rule is the whole game. Your initial package, the code and assets that load before the first frame, must fit in 4 MB. Everything else has to be split into subpackages (分包) that download on demand, up to a much larger total. Getting under 4 MB is the single hardest engineering problem on the platform, and it's the main thing your engine either helps or hurts with.

Monetization needs a license. A Mini Game that takes in-app payments needs a Chinese game license, and a foreign studio needs a local publisher to get one. That's a distribution problem, not an engine problem, and we cover it in the WeChat and Douyin publishing guide.

Cocos Creator: the default ​

Cocos Creator is what most WeChat Mini Games are built in, and the platform is built to reward that. Since WeChat client 7.0.7, the Cocos engine runtime is a plugin baked into the WeChat app itself. If a player has run any Cocos Mini Game before, the engine code is already on their phone and doesn't count against your 4 MB. That's a structural advantage no other engine has: your package is just your game, not your game plus the engine.

Cocos also ships the AssetBundle system, which is the cleanest way to handle subpackaging. You mark bundles to load on demand, and the difference between a project that fits in 4 MB and one that doesn't is usually just moving the right bundles out of the main package. It does 2D and 3D, uses TypeScript, and its build panel targets WeChat as a first-class platform.

If you have no existing codebase and you're building for WeChat first, Cocos Creator is the safe pick. Start here unless you have a specific reason not to.

LayaAir: the strong alternative ​

LayaAir (from Laya) is the other engine that adapted to WeChat early and treats it as a first-class target. You pick WeChat Mini Game in the build panel and it publishes. It handles 2D and 3D, uses TypeScript, and has a loyal base of developers who prefer its workflow to Cocos. Developers who've used both tend to describe the choice as a matter of taste rather than capability.

The one thing to weigh: LayaAir's engine runtime is not baked into the WeChat client the way Cocos is, so you pay more of your package budget for the engine itself. For a small 2D game that's usually fine. For an asset-heavy 3D game where every kilobyte of the 4 MB matters, Cocos's built-in plugin can be the deciding factor.

Egret: legacy, use with eyes open ​

Egret (白鹭) is an older 2D HTML5 engine that supported WeChat Mini Games early and powered a lot of the first wave. It still works, but momentum has moved to Cocos and Laya, community activity has thinned, and starting a new project on it in 2026 means betting on a shrinking ecosystem. If you're maintaining an existing Egret game, fine. If you're starting fresh, pick Cocos or Laya.

Unity: the WebGL transform path ​

Unity has no native WeChat export, but Tencent and Unity maintain an official tool that converts a Unity WebGL build into a Mini Game package: the WeChat Mini Game transform SDK, sometimes shipped as the WeChat MiniGame Exporter. As of a mid-2025 update it does one-click export, and the companion minigame-adaptor claims roughly 3x rendering performance over plain WebGL by using WeChat's optimized rendering path.

This is the route if you already have a Unity game and want it on WeChat without a rewrite. Be realistic about the tradeoff. Unity WebGL builds are large, and the 4 MB initial package is brutal for an engine that wasn't designed around it. You'll spend real effort on stripping, code splitting, and pushing assets into subpackages. It's a port-an-existing-game tool, not a build-for-WeChat-first tool.

Tuanjie: Unity China's native answer ​

If you like Unity's workflow but want WeChat as a real build target instead of a WebGL conversion, look at Tuanjie (团结引擎), Unity China's localized engine. It's based on Unity 2022 LTS and treats WeChat Mini Games as a native platform alongside iOS and Android, plus domestic targets like OpenHarmony and AliOS. Recent versions added a full real-time global illumination system (TuanjieGI), and it's passed 500,000 downloads.

For a studio committed to the Chinese market with Unity muscle memory, Tuanjie is the most future-proof of the Unity-family options, because WeChat isn't an afterthought bolted on through WebGL. It's a first-class export.

Three.js and raw WebGL ​

You can run Three.js or hand-written WebGL inside a Mini Game through WeChat's weapp-adapter, which stubs out the DOM and canvas objects the library expects. This is the most flexible and the most work: you own the render loop, the asset pipeline, the subpackaging, and every adapter edge case yourself. It makes sense for a small, custom, size-sensitive game where a full engine is overkill, or when your team already lives in Three.js and wants to reuse its code.

This is also the path closest to a browser game you've already built. A Three.js game that runs on the open web is structurally close to one that runs in WeChat. The gap is the adapter and the 4 MB budget, not the rendering.

The quick pick ​

Building for WeChat first, no existing code: Cocos Creator. The built-in engine plugin and AssetBundle system make the 4 MB fight winnable.

Porting an existing Unity game: the WeChat WebGL transform SDK to get there fast, or Tuanjie if you're committing to China long term and want a native target.

Small, custom, or already in Three.js: the weapp-adapter and raw WebGL, and accept that you're doing the plumbing yourself.

Prefer Laya's workflow: LayaAir, with an eye on package size for 3D.

Where Cinevva fits ​

Cinevva builds web-first 3D games on Three.js that run from a link in any browser, which is the same shape a WeChat Mini Game wants: no install, instant play, JavaScript and WebGL under the hood. The Great Firewall and the licensing layer are real, and we're honest that shipping into WeChat means a local publisher and the 4 MB discipline. But the game itself, a browser-native 3D experience with no download, is already the thing the biggest games platform in China is built around. If you're prototyping something you might one day want in front of 500 million Mini Game players, starting in the browser is the least wasted motion.

Frequently asked questions ​

What is the file size limit for a WeChat Mini Game? ​

The initial package is capped at 4 MB. Anything beyond that must be split into subpackages (分包) that load on demand, which together can reach a much larger total. Fitting the first-load experience into 4 MB is the core optimization problem on the platform.

Can I use Unity for WeChat Mini Games? ​

Yes, but not natively. Tencent and Unity provide an official transform SDK that converts a Unity WebGL build into a Mini Game, with one-click export as of mid-2025. Alternatively, Unity China's Tuanjie engine supports WeChat as a native build target. Expect to spend effort on build size either way.

Which engine do most WeChat Mini Games use? ​

Cocos Creator is the most common choice, helped by the fact that its engine runtime is built into the WeChat client, so it doesn't eat into your 4 MB package. LayaAir is the main alternative.

Do WeChat Mini Games support 3D? ​

Yes. Cocos Creator, LayaAir, Unity (via the transform SDK), and Tuanjie all handle 3D, and WeChat's runtime exposes WebGL and increasingly WebGPU. The constraint is package size and performance on low-end phones, not whether 3D is possible.

Can I turn my browser game into a WeChat Mini Game? ​

Often, yes. A game built on Three.js or WebGL can run inside WeChat through the weapp-adapter, which emulates the browser objects the code expects. The work is in the adapter layer and getting under the 4 MB initial-package limit, not in rewriting the game.

Try it right nowStart in the browser, keep your options open

Prototype a web-native 3D game first. It's the same shape a Mini Game wants, minus the sandbox.

Build it free →Free, runs in your browser, nothing to install.