This page describes the specifications within the scope of the V3C reference tools, the codec profiles they cover, and the high-level architecture that brings context to their applicability.
The MPEG V3C Immersive Platform provides reference tools for volumetric video, content that captures 3D objects and scenes so a viewer can move freely around them rather than watching from a fixed camera. The implementation is built around MPEG Visual Volumetric Video-based Coding (V3C, ISO/IEC 23090-5), which defines a common container and bitstream structure for two related coding approaches: V-PCC (video-based point cloud compression) for volumetric objects, and MIV (MPEG Immersive Video, ISO/IEC 23090-12) for multi-view scenes with depth. The platform aims to cover an end-to-end path: encoding source content into a V3C bitstream, packaging and delivering it, then decoding and rendering it in real time.
On the rendering side, the work targets a Unity-based player so volumetric assets can be integrated into interactive applications, using the same separation-of-concerns pattern used across 5G-MAG's immersive media tools (see "What the reference tools implement" below for how the decoder plugin and the engine split the work). According to 5G-MAG, a significant part of the initial contribution came from InterDigital and Philips; treat any specific partner attribution as something to confirm against 5G-MAG's own announcements before relying on it externally.
The reference tooling in this area is still maturing, and the exact set of public repositories changes as the project develops. For the authoritative, current list of repositories and their implementation status, see the Resources page rather than relying on a hard-coded list here. Implementation-status and roadmap details are tracked on the V3C Kanban board linked from the Resources.
Standards being implemented
The V3C reference tools relate to the following specifications. For the full, maintained list, see the standards portal page linked below.
| Specification | Title |
|---|---|
| ISO/IEC 23090-5 | Visual volumetric video-based coding (V3C) and video-based point cloud compression (V-PCC) |
| ISO/IEC 23090-12 | MPEG immersive video (MIV) |
| ISO/IEC 23090-10 | Carriage of visual volumetric video-based coding data |
What the reference tools implement
The MPEG V3C Immersive Platform aims to cover the full path for volumetric content:
- Encode: turn source content (a point cloud for V-PCC, or multi-view-plus-depth for MIV) into a V3C bitstream. V3C projects the 3D data onto 2D planes, packs them, and codes the resulting geometry, occupancy, and attribute videos with a conventional 2D video codec, while the 3D structure is carried in a compact atlas metadata stream.
- Package and deliver: store the V3C bitstream in ISOBMFF per ISO/IEC 23090-10 and describe it as a DASH presentation so it can be delivered adaptively over HTTP, on the same 5G Media Streaming path used for other media.
- Decode and render: decode the atlas and the component videos and reconstruct the 3D representation for real-time display.
On the client, the platform targets a Unity-based player. A V3C decoder is exposed to the engine as a plugin: the plugin owns the V3C-specific work (parsing the atlas, decoding the geometry, occupancy, and attribute video sub-bitstreams, and reconstructing the 3D representation), while the Unity engine owns presentation and interaction. This separation lets the same decoder serve different front ends and keeps the volumetric decode path independent of the rendering engine.
How the tools map to the standard
| Standard | What it defines | Where it appears in the tools |
|---|---|---|
| ISO/IEC 23090-5 | V3C base bitstream and the V-PCC profile | Encoder output and decoder input; point-cloud reconstruction |
| ISO/IEC 23090-12 | MIV profile (multi-view plus depth) | Encoder output and decoder input; viewport synthesis for multi-view scenes |
| ISO/IEC 23090-10 | Carriage of V3C data in ISOBMFF, with DASH support | Packaging and delivery stage |
The two coding profiles produce the same V3C bitstream structure, so the carriage, delivery, and decoder-plugin machinery is shared between the point-cloud (V-PCC) and multi-view (MIV) cases.
Release and edition coverage
ISO/IEC 23090-5 has been published in successive editions (2021, 2023, 2025). Because the reference tooling is still maturing, the exact edition and feature subset each component targets changes as the project develops; treat the edition support as tracked in the repositories rather than fixed here. For the authoritative, current list of repositories and their implementation status, see the Resources page and the V3C Kanban board linked from the Resources.
Getting started
- Read the Volumetric Video Tech page for how V3C, V-PCC, and MIV work end to end.
- Check the Resources page for the current set of repositories and pick the component you need (encoder, decoder plugin, or player).
- Follow the build and run instructions in each repository's README; the Tutorials page and the Developer Exchange collect walkthroughs and demos.
- Track open work and status on the Resources and the linked Kanban board.
Go deeper
Technical documentation providing context to this project can be found in the link below.
A list of relevant specifications can be found in the link below.
High-level architecture
MPEG V3C Immersive Platform
The diagram below shows the end-to-end V3C pipeline, from encoding source content into a V3C bitstream, through packaging and delivery, to decoding and rendering in the Unity player via the decoder plugin.
Figure: high-level architecture of the MPEG V3C Immersive Platform, showing the encode, deliver, decode, and render stages.
The blocks in the diagram map to the repositories listed on the pages below.
These specifics on this page were not confirmed against a primary source: the exact ISO/IEC 23090-5 edition and the V3C/MIV feature subset each reference-tool component targets (this changes as the project develops and is tracked in the repositories). The ISO part numbers themselves (23090-5, 23090-10, 23090-12) are taken from the ISO catalogue. Verify the edition and feature coverage against the repository READMEs and the Kanban board before relying on it externally.