Wonderland Engine and Zappar have partnered to make it simple for developers to build advanced 3D experiences in Wonderland and deploy them as production-ready WebAR using Zappar’s tracking and publishing stack.
At a practical level, this means Wonderland developers can now access Zappar’s image, world, and face tracking directly inside the Wonderland Engine editor, with a streamlined path from development to live deployment.
In short, this release combines high-performance 3D rendering with dependable mobile WebAR infrastructure, without adding unnecessary friction to your workflow.
Wonderland Engine has a strong following among developers who come from game-engine backgrounds or who prefer a desktop-first, component-driven 3D workflow. Its WebAssembly-based architecture is well-suited to teams building complex, heavily interactive 3D scenes as well as having its own active developer community that, until now, didn't have a native path to production WebAR.
This integration changes that.
By bringing Zappar's tracking and deployment pipeline directly into the Wonderland editor, developers already working in that environment can add reliable mobile WebAR without rebuilding their workflow from scratch.
Advanced 3D content, tested on real devices, shipped to mobile browsers.
The integration centres around a first-party Zappar plugin inside Wonderland Engine
This includes:
These templates work across major browsers and are designed to get developers from project creation to live tracking quickly, without manual wiring of core AR systems.
Through the plugin, developers can access Zappar’s image, face, and world tracking directly inside the Wonderland editor.
When you're ready to publish your WebAR experience, you can upload it to Zapworks directly, and enjoy the same hosting and deployment infrastructure you're used to:
For developers already working with Zappar, this is worth stating plainly: the tracking quality doesn't change. What changes is the authoring environment.
Zappar's Universal AR stack is the same underneath. The difference is that you can now build your scene inside Wonderland's desktop editor, take advantage of its performance-first architecture, and publish through Zapworks, all without switching between disconnected tools.
The integration is available now. To get up and running, the Wonderland Engine plugin documentation walks you through everything from installation to your first published experience. You'll need a Wonderland license to use the editor and a Zapworks license to publish and deploy live experiences. Projects without a Zapworks license will run in development mode.
Here's the full workflow:
If you want to see the full workflow in action, watch the launch webinar, which covers project setup, real-device testing, debugging, and publishing step by step.