The 2026 numbers do not say what the pitch assumes.
If you are considering a 3D virtual event, start by accepting what the industry data says, because it is not encouraging for the usual version of this idea.
Bizzabo’s 2026 benchmark research reports that 78% of organisers say in-person conferences, summits and conventions are their organisation’s most impactful marketing channel, that 40% plan to run more events this year, and that 54% of attendees plan to attend more in-person events than last year. Virtual is not displacing the conference. Anyone selling you a 3D event as a replacement for a room is selling against the evidence.
Three other findings in the same research point somewhere more useful:
- Only 15% of organisers rate their networking opportunities as very effective, and that figure fell sharply from 2025.
- 53% of attendees plan to attend more webinars in 2026, and 61% of organisers report webinar attendance rising year over year.
- 82% of organisers already create video on demand from their events, and 53% gate at least some of it.
Read those together and the actual problem shows up. Organisers are producing more content than ever, publishing it after the fact, and getting steadily worse at the one thing a physical venue is supposed to be for. The gap is not attendance. The gap is that an event ends on a Thursday and by Monday everything that happened inside it is a folder of MP4s and a spreadsheet of leads.
The first wave failed because it promised presence.
The 2020 and 2021 pitch for virtual environments was “it feels like being there”. It did not, attendees knew immediately, and the category acquired a reputation it is still carrying.
That failure was a positioning failure more than a technical one. Measured against a room, a browser tab loses on every axis that matters: peripheral vision, the accidental conversation, the physical commitment that keeps someone in the building. You cannot win that comparison and you should stop entering it.
Measured against the thing it is actually competing with — a grid of video tiles and a PDF agenda — a 3D environment wins on a different and narrower set of things:
| 3D environment | Video call and agenda page |
|---|---|
| Content has a location you can return to | Content is a list that scrolls |
| Sponsors occupy space, not a logo strip | Sponsors are a slide between sessions |
| Self-directed — attendees choose a path | Linear — attendees follow a schedule |
| Persists after the live days | Ends when the call ends |
| Shareable as a link, no install | Shareable as a link, no install |
| Costs a build | Costs a subscription |
That last row is the honest one, and it is why most events should not build one.
Stop selling presence. Sell persistence and discovery, which are things a browser genuinely does better than a room.
What we built, and the numbers that came out of it.
In May 2021 we helped deliver CRUSH City, a white-labelled 3D conference environment for Avalara’s flagship CRUSH event, working with Shiraz Creative on their ATTND.live platform.
The scale, for calibration:
| Live dates | 24–26 May 2021 |
| Attendees | 6,000+, globally |
| Structure | 18 neighbourhoods, each an industry or topic |
| Keynotes | 4 headline, 21 industry-focused |
| Interactive stations | 100+ resource and activity points |
| Availability after the event | 30 days on demand |
The row people skim past is the last one. Three days of live programming, then thirty days during which the environment stayed open and the content stayed where attendees had left it. In practice that is where a large share of the value sits, and it is the part a video call structurally cannot do.
The technical shape was a Unity WebGL client embedded in a React application, with .NET 5 services on AWS, Mux carrying the video, and Mixpanel and Sentry watching behaviour and errors. Our own work was the streaming pipeline for the 3D assets, wiring Unity’s runtime data into a custom analytics backend so engagement could be tracked in real time, the integration between the Unity canvas and the surrounding web application, and the performance, load and frame-rate testing that had to hold across desktop and mobile browsers.
The design lesson is in the screenshot at the top of this article. Down the left-hand side: home, agenda, quick navigation, map. The environment is a browser for content, not a substitute for a room. The attendees who got value out of it were the ones who found what they came for quickly, and every design decision that made wandering more charming at the expense of finding was a decision we would not repeat.
The delivery constraints that decide feasibility.
The entire argument for a browser-delivered event is that there is no install and no store. That single commitment sets every technical constraint that follows.
WebGL2 is the floor. It is what a Unity Web build guarantees, and it is what the audience’s browsers actually have. WebGPU is available and useful if you need compute, but it is opt-in, absent from Firefox by default, and irrelevant to most event environments.
Download time is a commercial decision, not a technical one. The question is how long this specific audience will wait before closing the tab, and everything about scene complexity, texture budget and asset streaming follows from the answer. Set the number before the art is approved, not after.
Memory, not frame rate, is what kills it. Browser 3D does not degrade gracefully when it runs out; it stops. The ceiling on a mid-range phone from three years ago is far below what the workstation running the review meeting suggests, and that device is your real minimum spec.
There is no captive audience. Someone in a hotel ballroom stays because leaving is socially awkward and their coat is on the chair. Someone in a browser tab leaves for free, instantly, and never tells you why. Every second of loading and every unclear navigation decision is paid for in attendance.
Serve Brotli over HTTPS, test on the old phone rather than the new one, and treat the first thirty seconds as the whole product. If the first thirty seconds are a loading bar, the rest of the build does not matter.
Measure the tail, not the peak.
Virtual event reporting is full of numbers that flatter the organiser and tell the sponsor nothing. If you are going to spend on a 3D environment, the reporting has to justify it, which means measuring different things.
| Commonly reported | Worth reporting instead |
|---|---|
| Registrations | Unique attendees who actually entered |
| Time in world | Sessions and resources actually opened |
| Booth visits | Contact events a sponsor can follow up |
| Peak concurrency | The thirty-day tail after the live days |
| Sessions streamed live | Share of the whole library that got consumed |
| Average session length | Return visits by the same person |
The right-hand column is also the column that renews a sponsorship. “Four hundred people walked past your building” is a number an experienced sponsor has learned to ignore. “Sixty people opened your material, nineteen came back a second time, here they are” is a number they will pay for again.
This is why the analytics integration is not a phase-two item. If the environment cannot say who did what, you have built an experience and not a channel, and next year’s budget conversation will go badly.
When to build one, and when to use a video call.
- Build one when the content outlives the dates. A large library, a sponsor programme, and a reason for people to come back in week three. That is the case a 3D environment answers.
- Build one when discovery is the problem. If your agenda page has ninety sessions and nobody can find the six that apply to them, spatial structure genuinely helps.
- Build one when it is your event, repeatedly. The cost is a build; it amortises across editions. White-labelling matters here — it should look like your event, not like a vendor’s template with your logo on it.
- Do not build one for presence. If the goal is people feeling together, spend the money on getting them together.
- Do not build one for a single day with twelve sessions. A well-run webinar and a good on-demand page will beat it on every measure including cost.
- Do not build one without deciding the analytics first. The environment is the visible part; the evidence it produces is the part that gets it funded again.
The 3D event is a narrower product than the 2021 wave claimed and a more durable one than its reputation suggests. It is a persistent, navigable, measurable home for a content library that would otherwise disappear into a folder — and if that is not the problem you have, the honest recommendation is a video call.
What this means for a buyer.
Start with the business decision, audience, and evidence the project must produce. Simam Digital can turn that into a focused discovery, prototype, MVP, or production roadmap across AI applications, SaaS platforms, digital twins, real-time 3D, XR, and interactive systems.
