Guides Build & Release Try Experimental Web Export

Build & Release 2 min read Updated Aug 2026

Try Experimental Web Export

Lenga can build an early browser version of a project. Use this page to understand what that preview can test, what it cannot do yet, and when it makes sense to try it.

This is not the final editor Export window. If you are shipping a game today, use the current desktop export flow first and treat Web export as a compatibility preview.

What You Can Test

The experimental Web path can:

  • create a browser player bundle
  • load project settings and the startup scene
  • run PHP behaviours
  • include referenced images, audio, scripts, scenes, and project files
  • serve the build locally so you can open it in a browser
  • write a build summary for troubleshooting

Use your own Lenga project when trying the preview. Sample projects are not bundled with the public SDK, so public Web export guidance should not depend on private repository paths.

Who Should Use This Preview

Try this preview if you are comfortable working from the Lenga source project and you want to validate browser compatibility early.

You can skip this page for now if you mostly want to design levels, tune gameplay, or package a desktop build. The production Web workflow will move into the editor with a normal Build & Run experience.

What The Build Produces

A successful Web build produces files such as:

lenga_runtime.html
lenga_runtime.js
lenga_runtime.wasm
lenga_runtime.data
build-manifest.json
export.log

Use lenga_runtime.html as the browser entry point when the build is served locally.

Use export.log when something fails and you need to see what the exporter was doing.

Use build-manifest.json when you need structured details about the generated build, such as the selected project, scene, profile, output paths, and browser entry file.

Current Limitations

Experimental Web export does not yet include:

  • a polished editor Export window
  • automatic Web toolchain setup
  • broad project and browser coverage
  • deploy-to-host workflows
  • final Web-specific project settings
  • production 3D Web physics support

Treat the result as an early browser validation build, not a final shipping package.

What Comes Next

The production Web export work will bring this path into the editor with a normal Build & Run flow, project settings, clearer diagnostics, build history, logs, and deployment-ready output.