Metaverse interoperability is the sector’s most repeated promise and its least delivered feature: the idea that an avatar, a wearable, or a piece of virtual land bought in one platform should work in another. In practice, “interoperability” describes at least three different technical problems — 3D file-format compatibility, avatar identity portability, and blockchain-based asset ownership — and they are at wildly different stages of maturity. One is standardizing quickly through boring, well-funded industry consortiums. The other two are mostly bilateral integrations dressed up as open standards, and the sector’s most-cited cross-platform avatar layer was shut down by its acquirer in January 2026.
Key Points:
- 3D-content interoperability is real and shipping: the Alliance for OpenUSD (Pixar, Adobe, Apple, Autodesk, Nvidia) released its Core Specification 1.0 in December 2025, moving Universal Scene Description from a de facto to an internationally recognized standard
- The Metaverse Standards Forum has grown to roughly 2,500 member organizations but explicitly does not write standards itself — it coordinates existing bodies like Khronos and W3C and produces reports, pilots, and testbeds, not binding specs
- Netflix acquired Ready Player Me, the most widely integrated cross-platform avatar system (25,000+ developers), in December 2025 and shut down its public avatar-creation service on January 31, 2026 — converting an open interoperability layer into a closed, internal one overnight
- Blockchain-based asset portability today mostly means bespoke, permissioned integrations — Decentraland’s DAO-gated Linked Wearables registry, Yuga Labs’ Otherside Open Data Kits — not a universal standard any platform can plug into
- ERC-6551 token-bound accounts let an NFT hold other assets and act as a wallet, but the standard operates within a single chain’s ecosystem and has not been formally ratified as an Ethereum standard
Three Problems Hiding Inside One Word
“Metaverse interoperability” gets used as if it were a single technical challenge. It isn’t. Moving a digital asset between platforms actually requires solving three separable problems, each with its own standards bodies, incentives, and maturity level:
- Rendering compatibility — can a 3D model, texture, or scene built for one engine display correctly in another? This is a file-format and geometry problem, solved by formats like glTF (for individual assets) and OpenUSD (for full scenes and pipelines).
- Identity portability — can a user carry a persistent avatar, appearance, and social graph across unrelated platforms? This depends on a third party maintaining a shared avatar system that many platforms voluntarily integrate.
- Economic/ownership portability — can an on-chain asset (land, a wearable, an in-game item) retain verifiable ownership and actually function as a usable item inside a platform that didn’t originally issue it? This is a smart-contract and permissions problem, not a rendering one.
Readers new to the underlying concept of on-chain ownership itself should start with this site’s explainer on how NFTs secure true digital asset ownership before continuing here — this article assumes that mechanism is already understood and focuses on what happens once an owned asset tries to leave its home platform.
The Part That’s Actually Working: File-Format Standardization
The most technically mature layer of metaverse interoperability has nothing to do with blockchains. Universal Scene Description (USD), originally built at Pixar for film production pipelines, is now being positioned as the shared data layer for 3D content generally — games, industrial design, architecture, and virtual worlds alike. The Alliance for OpenUSD (AOUSD), a Linux Foundation project founded by Pixar, Adobe, Apple, Autodesk, and Nvidia, released its Core Specification 1.0 on December 17, 2025, formally moving USD from an informal, Pixar-controlled format to an internationally recognized open standard. By SIGGRAPH 2026 in July, AOUSD had added general members including ByteDance, Huawei, and Unity, and member companies were presenting production workflows built on the spec.
This matters for the metaverse thesis specifically because it’s infrastructure-layer progress that doesn’t depend on any single platform’s user growth. A scene or asset built to the OpenUSD spec can, in principle, move between Nvidia’s Omniverse, Autodesk’s tools, and any other compliant engine without a custom export pipeline for each destination. glTF, a lighter-weight sibling format backed by the Khronos Group, solves the same problem for individual assets and avatars rather than full scenes, and is the format most avatar and wearable systems actually export to.
The caveat: solving “can this model render correctly elsewhere” says nothing about whether a platform will actually let a user bring in an asset it didn’t sell, or whether that asset should retain any economic value once it does. File-format compatibility is a necessary condition for interoperability. It is not a sufficient one.
The Metaverse Standards Forum Coordinates. It Doesn’t Mandate.
The Metaverse Standards Forum (MSF), founded in June 2022 with 35 members, has grown to roughly 2,500 member organizations by 2026, including Nvidia, Meta, Microsoft, Epic Games, Adobe, and the W3C. It is frequently cited as evidence the industry is “solving” interoperability. The Forum’s own description of its role is narrower than that framing implies: it states explicitly that it “does not create standards itself” but instead “coordinates requirements and resources to foster the creation and evolution of standards within standards organizations” like Khronos and W3C. Its concrete output is domain reports, use-case recommendations, pilots, testbeds, and open-source tooling — one active example is its 3D Asset Interoperability project, which tests whether the same asset behaves consistently across multiple rendering engines.
That’s a legitimate and useful function — reducing duplicated standards work across a fragmented industry is genuinely hard coordination labor. But it’s a different claim than “the metaverse now has interoperability standards.” The MSF is a forum for getting standards bodies to agree on requirements, not a body that issues binding specifications platforms must implement. Membership growth (2,500 organizations) measures interest in coordination, not delivered interoperability.
The Cautionary Tale: What Happened to Ready Player Me
The clearest real-world test of avatar-identity interoperability collapsed in real time this cycle. Ready Player Me, an Estonian company that built the most widely adopted cross-platform avatar system — integrated by more than 25,000 developers across roughly 3,000 apps spanning VRChat, Spatial, Somnium Space, and RTFKT — let users create one avatar and carry it, in principle, across every platform that integrated the SDK. It had raised $72 million from investors including Andreessen Horowitz and Konvoy Ventures on exactly that pitch: a shared, portable digital identity layer for the metaverse.
Netflix acquired Ready Player Me, announced December 22, 2025. Ready Player Me shut down its public avatar-creation tools, including its PlayerZero service, on January 31, 2026 — a hard stop, not a wind-down. Roughly 20 of the company’s employees moved to Netflix; only one of its four founders went with them. Netflix has not announced a public timeline for reintroducing avatar creation on its own platforms, and existing users cannot export their avatar files to use on other services going forward.
The mechanism failure here is instructive: Ready Player Me was never a standard in the way glTF or OpenUSD are standards — it was a company running a proprietary SDK that thousands of platforms chose to integrate voluntarily. That’s a business relationship, not an open protocol, and business relationships end when the business is sold. A platform-agnostic identity layer that depends on one company staying independent and staying interested in openness is not actually interoperability infrastructure — it’s a single point of failure wearing interoperability’s branding. Any reader evaluating a platform’s “interoperable avatar” claims should ask specifically whether the underlying layer is an open standard with multiple independent implementers, or a single vendor’s SDK.
How Asset Portability Actually Works Today: Permissioned, Not Universal
Even where blockchain ownership is verifiable, getting an asset to function inside a platform that didn’t issue it requires that platform to explicitly build support for it. Two working examples illustrate how narrow this still is:
Decentraland’s Linked Wearables. Decentraland mints its own wearables on Polygon (avoiding Ethereum mainnet gas fees via the DAO’s meta-transaction system), but it also allows external, non-Decentraland-native NFTs to function as in-world wearables through a feature called Linked Wearables. The catch: a creator must submit a formal proposal to Decentraland’s DAO and get approved through the Linked Wearables Registry before their external collection can be mapped into the world. That’s a governance gate, not an open protocol — every external collection is individually reviewed and admitted, one at a time.
Yuga Labs’ Otherside Open Data Kits. Otherside, the Bored Ape Yacht Club ecosystem’s virtual world, publishes Open Data Kits (ODKs) that let third-party developers read Otherside’s on-chain data — land, characters, items — inside their own applications. This is a real, functioning integration path, and it’s a genuinely more composable model than a fully closed platform. But it’s still Yuga Labs defining the interface on its own terms for its own asset base; it doesn’t make a Decentraland wearable work in Otherside, or vice versa.
ERC-6551 token-bound accounts. This Ethereum standard lets an NFT function as its own smart-contract wallet — capable of holding other tokens, NFTs, and permissions, and signing transactions independently of its owner’s main wallet. It’s a genuinely useful primitive for in-game inventories (an NFT character that “carries” its equipment as sub-assets it actually owns) and is already used across a number of on-chain gaming and NFT projects. Two limits matter for the interoperability claim specifically: it operates within a single chain’s ecosystem rather than across chains, and as of 2026 it has not been formally ratified as an official Ethereum standard, meaning its long-term specification stability isn’t guaranteed the way a finalized EIP’s would be.
Cross-chain bridges (moving MANA or a wrapped NFT between Ethereum and Polygon, for instance) solve a related but distinct problem — getting the same asset recognized on a different blockchain — not making that asset natively usable inside a different platform’s engine and rules. Bridging solves custody and recognition. It doesn’t solve rendering, gameplay integration, or a receiving platform’s willingness to grant the item any function at all.
Interoperability Layer Comparison
| Layer | Mechanism | Maturity | Key risk |
|---|---|---|---|
| 3D file format | OpenUSD (scenes), glTF (assets) — open specs from multi-vendor alliances | Shipping; Core Spec 1.0 released Dec 2025 | Solves rendering only, not economic function |
| Standards coordination | Metaverse Standards Forum (~2,500 members) | Active coordination, no binding output | Membership growth ≠ delivered interoperability |
| Avatar identity | Proprietary vendor SDK (e.g., Ready Player Me) | Collapsed — RPM shut down publicly Jan 31, 2026 post-Netflix acquisition | Single point of corporate failure, not an open protocol |
| Cross-platform asset import | Platform-specific gated registries (Decentraland Linked Wearables, Otherside ODKs) | Working but bilateral, permissioned per platform | Every integration is manually approved, not universal |
| On-chain asset ownership | ERC-6551 token-bound accounts, cross-chain bridges | Functional within one chain/ecosystem | Not cross-chain by default; ERC-6551 not formally ratified |
The Honest Risk Case
The most-cited proof of concept for avatar interoperability no longer exists in its open form. Ready Player Me was the closest thing this sector had to a working, widely adopted portability layer, and it was converted into Netflix’s internal tooling within roughly five weeks of the acquisition being announced. Anyone using RPM’s prior scale as evidence that identity portability is a solved problem needs to update that view — the demonstration case failed, not gradually, but on a hard deadline.
Standards-body activity is not the same as platforms actually adopting cross-platform asset support. A 2,500-member forum and a ratified USD spec are genuine progress on the parts of the problem that are format- and rendering-related. Neither compels Roblox, Fortnite, or any closed platform to accept an externally issued NFT as a functional in-world item, and none of the major platforms with the largest user bases have committed to doing so.
Every working asset-portability example today is a bilateral, revocable arrangement, not a universal right. Decentraland’s DAO can change or end its Linked Wearables program. Yuga Labs controls what its ODKs expose and can change the interface. A user’s ability to move an asset between worlds currently depends on continued goodwill and continued operation from specific companies and DAOs — exactly the single-point-of-failure structure the Ready Player Me shutdown just demonstrated at scale.
This is consistent with this site’s broader position on the metaverse sector: functional, narrower use cases are advancing faster than the durable, platform-independent economies the 2021-2022 cycle originally promised. Interoperability is one of those narrower use cases — real progress at the file-format layer, genuinely unresolved at the ownership and identity layers.
What This Means for Evaluating a Platform’s Interoperability Claims
When a platform or token markets itself on “interoperability,” the specific claim being made is worth pinning down. Three questions separate marketing from mechanism: Is the underlying layer an open standard with multiple independent implementers, or one company’s SDK? Does the integration require case-by-case governance approval, or does it work automatically for any compliant asset? And has the claimed interoperability actually been demonstrated moving a real asset between two platforms neither company controls, or is it a roadmap item? Readers evaluating metaverse-adjacent tokens for dilution and valuation risk more broadly should also see this site’s guide on FDV and token dilution risks in metaverse coins — interoperability claims are a common component of the growth narrative used to justify high fully diluted valuations, and the gap between the pitch and the working mechanism documented here applies directly to that valuation question.
Frequently Asked Questions
Is metaverse interoperability solved yet?
Partially, and only at the file-format layer. 3D asset and scene compatibility has real, shipping standards (OpenUSD Core Specification 1.0, glTF). Avatar identity portability and cross-platform economic asset ownership remain unsolved at an industry-standard level — the working examples that exist are bilateral, permissioned integrations between specific platforms, not universal protocols.
What happened to Ready Player Me?
Netflix acquired the company, announced December 22, 2025, and shut down its public avatar-creation service, including PlayerZero, on January 31, 2026. Existing users cannot export their avatars for use on other platforms going forward. It’s the clearest example of a widely adopted “interoperability” layer turning out to be a single company’s product rather than an open standard.
Does owning an NFT mean it will work in other metaverse platforms?
Not automatically. Owning an NFT proves on-chain ownership of that specific token, but whether a different platform renders it, grants it any in-world function, or recognizes it at all is a separate decision that platform has to make and build support for — as seen with Decentraland’s DAO-gated Linked Wearables approval process and Yuga Labs’ Otherside Open Data Kits, both of which are permissioned, not automatic.
What is the Metaverse Standards Forum, and does it set binding rules?
It’s an industry coordination body, founded in 2022 and grown to roughly 2,500 member organizations by 2026, including Nvidia, Meta, Microsoft, and the W3C. By its own description, it does not create standards itself — it coordinates existing standards organizations and produces reports, pilots, and testbeds. No platform is required to implement its recommendations.
What’s the difference between a cross-chain bridge and true interoperability?
A bridge moves recognition and custody of the same asset from one blockchain to another (for example, Decentraland’s MANA moving between Ethereum and Polygon). It doesn’t make that asset functional inside a different platform’s engine — rendering compatibility, gameplay rules, and a receiving platform’s willingness to grant the item any use are separate problems a bridge doesn’t touch.
This article is for informational and educational purposes only and does not constitute financial advice. Always do your own research and consult a licensed financial advisor before making investment decisions.
Recommended Sources
- Alliance for OpenUSD Announces New Member Milestones and Industrial Momentum Following Core Specification 1.0 — Linux Foundation (OpenUSD Core Specification 1.0 release, Dec 2025, and 2026 member growth)
- The Metaverse Standards Forum — official site (Forum’s role, member count, scope of activities and disclaimer that it does not itself create standards)
- Netflix Acquires Gaming Avatar Maker Ready Player Me — TechCrunch, December 2025
- Netflix Acquires Avatar-Creation Platform Ready Player Me — PocketGamer.biz (acquisition timeline, Jan 31 2026 shutdown date, staff transition details)
- Ready Player Me Discontinued: Top Alternatives — Genies (confirms hard shutdown date and loss of avatar export capability)
- Transactions in Polygon — Decentraland Docs (Polygon-based wearables minting and meta-transaction gas model)
- Travel the Metaverse with Decentraland’s ‘Linked Wearables’ Feature — NFT Plazas (Linked Wearables Registry and DAO approval process)
- ERC-6551: Non-fungible Token Bound Accounts — Ethereum Improvement Proposals (official specification and ratification status)