Web deployment
How the engine reaches a browser, and what that costs you in shipping size, startup time, and integration with the rest of your web stack.
| Meep Web-native | Unity Cross-compiled | |
|---|---|---|
| Runtime architecture | Native JavaScript Runs in the browser as JS; no cross-compile step. | C# → IL2CPP → WASM 11 Cross-compiled. Game logic runs as WebAssembly, not native JS. |
| Minimal bundle size ⓘ | ~150 KB 1 ,2 | ~5–15 MB 12 Compressed minimum for a near-empty build. |
| Tree-shaking ⓘ | ✓ 2 Per-file ES modules, dead code drops cleanly. | ◐ Code stripping at build, but the runtime is monolithic. |
| Asset streaming ⓘ | ✓ AssetManager streams lazily by URL. | ✓ Addressables system; requires explicit setup. |
| HTML / CSS / JS interop ⓘ | Native Game is a JS module; share the DOM, CSS, fetch, anything. | Bridged JS↔C# via SendMessage / .jslib — not native cohabitation. |
| Native browser DevTools ⓘ | Full Set breakpoints in gameplay code, inspect entities in Sources. | Limited Source maps land in IL2CPP-emitted C++, not your C#. |
| Mobile web | ✓ | ◐ Runs, but bundle and memory are heavy for mobile browsers. |