Draft:Metaverse browser
Submission declined on 12 September 2026 by Fermiboson (talk).
Where to get help
How to improve a draft
You can also browse Wikipedia:Featured articles and Wikipedia:Good articles to find examples of Wikipedia's best writing on topics similar to your proposed article. Improving your odds of a speedy review To improve your odds of a faster review, tag your draft with relevant WikiProject tags using the button below. This will let reviewers know a new draft has been submitted in their area of interest. For instance, if you wrote about a female astronomer, you would want to add the Biography, Astronomy, and Women scientists tags. Editor resources
|  |
Comment: In accordance with the Wikimedia Foundation's Terms of Use, I disclose that I have been paid by my employer for my contributions to this article. SpatialShaman (talk) 23:40, 11 September 2026 (UTC)
Metaverse browser is a category of application software designed to access and render three-dimensional spatial content and services, in a manner analogous to how a web browser accesses and renders web pages from the World Wide Web.[1] Where a web browser retrieves HTML, CSS, and JavaScript from web servers and composites them into two-dimensional pages, a metaverse browser retrieves spatial data formats (such as Metaverse Spatial Fabric (MSF), WASM, and glTF) and real-time service streams from multiple independent providers, compositing them into an interactive three-dimensional scene graph on the user's device.[2]
The Open Metaverse Browser Initiative (OMBI), launched by the Metaverse Standards Forum and Metaversal Corporation (doing business as RP1) in March 2026, is developing open standards and a reference implementation for the metaverse browser engine and metaverse browser.[3] RP1 contributed the architecture and source code.[3] The OMBI's open-source metaverse browser engine, Sneeze, was released in June 2026 under the Apache 2.0 license.[2][4]
Launched in July 2026, Artemis, developed by RP1, is the first and only publicly available implementation.[5]
Concept
[edit]A metaverse browser extends the browsing paradigm, in which a client application renders content on demand from remote servers using open standards, from two-dimensional documents to three-dimensional spatial environments.[1] The OMBI framework describes four defining properties that parallel those of web browsers:[3]
- Trust without knowledge -- A user can connect to any standards-compliant service without pre-installing software from that provider, analogous to how a web browser can navigate to any website without a per-site application.[3]
- No per-application installation -- Content is streamed on demand rather than downloaded and installed as a standalone application.[2]
- Device independence -- Content authored to the standard is accessible from any compliant browser on any supported device, whether AR glasses, VR headsets, desktop computers, smartphones, robotics, AI devices, or autonomous vehicles.[6]
- Content/display separation -- The browser, not the content provider, controls how spatial content is rendered, composited, and presented to the user.[3]
These properties distinguish a metaverse browser from closed virtual world platforms (such as Roblox, Fortnite, or Horizon Worlds), in the same way that a web browser is distinguished from a standalone desktop application.[7]
Relationship to web browsers
[edit]A metaverse browser is not a replacement for the web browser. The OMBI describes the two as complementary: web browsers are optimized for two-dimensional content on flat-screen devices, while metaverse browsers are optimized for three-dimensional spatial content across XR and traditional devices.[3] Both share the principle of rendering open-standard content on demand from remote servers, but differ in architecture:[2]
| Property | Web browser | Metaverse browser |
|---|---|---|
| Primary content model | Document Object Model (DOM) -- hierarchical tree of elements in a 2D page | Scene Object Model (SOM) -- hierarchical tree of spatial objects in 3D space |
| Content formats | HTML, CSS, JavaScript, images, video | MSF, WASM, glTF, spatial audio |
| Connection model | Typically one server per page; stateless HTTP request/response | Many simultaneous persistent connections to independent real-time services |
| Standards bodies | W3C, WHATWG | Khronos Group, Metaverse Standards Forum, W3C |
Content produced for the metaverse browser is expected to be accessible from web browsers as well (via WebXR or a reduced 2D representation), much as a website can be accessed from both desktop and mobile browsers with differing levels of fidelity.[3]
Architecture
[edit]Browser engine
[edit]A metaverse browser requires a metaverse browser engine (MBE), the core software component responsible for ingesting spatial content, managing the scene graph, and producing rendered frames. The relationship between a metaverse browser engine and a metaverse browser is analogous to that of a browser engine (such as Blink, WebKit, or Gecko) and a web browser.[2][3] The MBE's responsibilities include:
- Multi-Origin Scene composition -- Receiving spatial data from multiple independent services and merging it into a single coherent scene.[2]
- Rendering -- Submitting the composed scene to a rendering engine via an abstraction layer (such as ANARI).[8]
- Input and interaction -- Translating device input (gaze, hand tracking, controllers) via OpenXR.[8]
- Service connectivity -- Maintaining persistent real-time connections to multiple concurrent services.[3]
- Sandboxing -- Isolating third-party service code (typically WASM modules) so that no service can interfere with another or with the browser itself.[9]
The reference MBE under development by the OMBI is named Sneeze, released as open-source software in June 2026.[2]
Scene Object Model
[edit]The Scene Object Model (SOM) is the metaverse browser's central data structure, functionally analogous to the web browser's Document Object Model (DOM). According to the OMBI's technical documentation, the SOM maintains a hierarchical tree of spatial objects contributed by multiple independent spatial fabrics. Each spatial fabric owns a branch of the tree and can create, update, or remove objects within its branch, while the browser enforces access control to prevent cross-fabric interference.[10]
Spatial fabrics
[edit]A spatial fabric is a three-dimensional coordinate space consisting of content and services that can manipulate content within the fabric. The OMBI describes a spatial fabric as the spatial equivalent of a website: an operator hosts a fabric on their own server, and the metaverse browser retrieves and renders it.[10] A single metaverse browser session may connect to multiple spatial fabrics simultaneously, compositing them into a unified scene for the user. Spatial fabrics can be nested hierarchically.[10][2] Content within a spatial fabric may include fully virtual environments, digital twins of physical locations, or scenes generated from world models and other physical AI systems.
History
[edit]Conceptual origins
[edit]The idea of navigating a persistent, shared 3D space has appeared in science fiction since at least Neal Stephenson's 1992 novel Snow Crash, which depicted a virtual-reality metaverse governed by a standards body and accessible from devices ranging from high-end systems to cheap public terminals.[11] Ernest Cline's 2011 novel Ready Player One further popularized the concept of an immersive, shared virtual environment.[12] These fictional depictions generally portrayed single monolithic virtual worlds rather than an open ecosystem of interoperable services accessed through a standards-based client.[1]
RP1 prototype
[edit]RP1 developed a metaverse browser prototype to navigate their first universal public spatial fabric in 2025 using the Wonderland Engine on top of WebXR within a standard web browser. The prototype demonstrated key concepts including multi-service composition, spatial fabrics, and large-scale avatar presence (up to 100,000 concurrent users in a single unsharded instance).[13]
Open Metaverse Browser Initiative
[edit]In March 2026, the Metaverse Standards Forum and RP1 launched the Open Metaverse Browser Initiative (OMBI), with the stated goal of establishing interoperability standards for spatial content access.[3] In June 2026, at AWE USA 2026, the OMBI released the Sneeze metaverse browser engine as open-source software under the Apache 2.0 license, hosted on GitHub and open to industry contributions.[2][4] Alongside the Sneeze release, the OMBI announced the Open Metaverse Academic Alliance (OMAA), a research partnership with universities led by the University of Rochester.[14][4]
Artemis native launch
[edit]In July 2026, RP1 released Artemis as a standalone native application powered by the Sneeze engine, rather than as a WebXR application running inside a web browser. The company described it as an early alpha release.[5]
Standards and protocols
[edit]A metaverse browser relies on a combination of existing and proposed open standards:[8][2]
| Standard | Organization | Role in the metaverse browser |
|---|---|---|
| glTF | Khronos Group | 3D model and scene delivery (geometry, PBR materials, textures, animations) |
| OpenXR | Khronos Group | XR device abstraction (headset tracking, input, rendering submission) |
| ANARI | Khronos Group | Rendering abstraction (high-level scene description API delegating to a rendering engine) |
| WebAssembly | W3C | Sandboxed execution of third-party service logic within the browser |
| SPIR-V | Khronos Group | Portable binary format for GPU shaders and compute kernels |
The OMBI has stated its intention to work with existing standards bodies rather than create competing specifications.[3]
Industry reception
[edit]The metaverse browser concept and the Sneeze engine release received coverage from technology publications following AWE 2026 in June 2026. Tim Bajarin, writing in Forbes, highlighted Sneeze among the notable developments at the conference, framing it within a broader shift in the spatial computing industry toward open standards and artificial intelligence.[6] In a separate Forbes article, Michael Ashley described the OMBI's approach and included an interview with RP1 CEO Sean Mann.[15] Dean Takahashi of GamesBeat published an exclusive interview covering the Sneeze release, the OMBI's goals, and the formation of the OMAA academic alliance, characterizing the initiative as an effort to create "a world without app stores" for spatial computing.[2] VR.org published an independent editorial analysis of the Sneeze release, examining both the technical claims and the broader industry context noting it as "the most encouraging announcement of AWE".[16] OMBI was nominated as a finalist for the Auggie Award for "Ethical XR Product of the Year" at AWE 2026.[17] In March 2026, The Verge reported that Epic Games and Google had signed a commercial agreement referencing "metaverse browsers" as a new application category, though key details of the agreement remained redacted.[18]
Relationship to WebXR
[edit]WebXR is a W3C standard that provides XR capabilities to content running inside a web browser. A metaverse browser does not replace or compete with WebXR; the OMBI has stated that the volume of spatial content generated for the metaverse is expected to increase demand for WebXR as the primary means by which web browser users on 2D devices access that content in a reduced-fidelity view.[3]
See also
[edit]References
[edit]- 1 2 3 "RP1 says that metaverse needs its own browser". VentureBeat / GamesBeat. 2025. Retrieved 2026-04-25.
- 1 2 3 4 5 6 7 8 9 10 11 Takahashi, Dean (2026-06-15). "Metaverse Standards Forum introduces Sneeze, the 1st open metaverse browser engine -- exclusive interview". GamesBeat. Retrieved 2026-08-13.
- 1 2 3 4 5 6 7 8 9 10 11 12 "Metaverse Standards Forum and RP1 Create the Open Metaverse Browser Initiative". Metaverse Standards Forum. 2026-03-11. Retrieved 2026-04-25.
- 1 2 3 "RP1 and the Metaverse Standards Forum Introduce Sneeze, the First Metaverse Browser Engine for Spatial Computing" (Press release). Business Wire. 2026-06-15. Retrieved 2026-08-13.
- 1 2 "RP1 Launches Artemis, the World's First Native Metaverse Browser" (Press release). Business Wire. 2026-07-06. Retrieved 2026-08-13.
- 1 2 Bajarin, Tim (2026-06-18). "At AWE 2026, Spatial Computing Grows Up And AI Is Now The Story". Forbes. Retrieved 2026-08-13.
- ↑ "RP1 debuts a scalable platform for the 'shardless' metaverse". VentureBeat / GamesBeat. 2024. Retrieved 2026-04-25.
- 1 2 3 "The Standards Sneeze Builds On". Open Metaverse Browser Initiative. Retrieved 2026-08-13.
- ↑ "Trust and Isolation". Open Metaverse Browser Initiative. Retrieved 2026-08-13.
- 1 2 3 "Core Concepts". Open Metaverse Browser Initiative. Retrieved 2026-08-13.
- ↑ Stephenson, Neal (1992). Snow Crash. Bantam Books. ISBN 0-553-08853-X.
- ↑ Cline, Ernest (2011). Ready Player One. Crown Publishers. ISBN 978-0-307-88743-6.
- ↑ "RP1 Shatters Metaverse Limits: Showcases Technology Platform Capable of Scaling to Billions of People" (Press release). Business Wire. 2023-06-14. Retrieved 2026-09-11.
- ↑ "Open Metaverse Academic Alliance (OMAA)". University of Rochester. 2026. Retrieved 2026-08-13.
- ↑ Ashley, Michael (2026-06-24). "Inside AWE 2026: Redefining the Line Between the Digital and the Real". Forbes. Retrieved 2026-08-13.
- ↑ "The Metaverse Just Got Its First Open-Source Browser Engine. Here Is Why That Matters". VR.org. 2026. Retrieved 2026-08-13.
- ↑ "2026 Auggie Awards Finalists Announced". AWE. 2026. Retrieved 2026-08-13.
- ↑ Peters, Jay (2026-03-04). "Epic and Google have signed a special deal for a new class of 'metaverse' apps". The Verge. Retrieved 2026-09-08.
LLM-generated pages with certain obvious signs of being machine generated may be deleted without notice.
Instead, only summarize in your own words a range of independent, reliable, published sources that discuss the subject.
See the advice page on large language models for more information.