Publishing to Your VIVERSE Account

All creations published to your VIVERSE account are known as "Worlds" and can be accessed on the "My Worlds" tab of the account page or the VIVERSE Studio. Here, you can also see any creators that you are following or worlds that you have favorited.

Currently, Worlds can only be associated with, owned and managed by one VIVERSE account. The owner's account name will display under the world on the VIVERSE world discovery page.

Video Overview

The VIVERSE Studio Interface

The is the one-stop-shop for managing all content associated with your VIVERSE account and profile.

Dashboard

The main dashboard of the VIVERSE studio includes metrics on how users engage with your content. Currently, this includes the number of views, unique viewers, new viewers, and likes. You may update the date range to filter for specific sections of metrics.

Content

The content page lists all of the worlds you have published on VIVERSE. Each tile displayes the world's name, discoverability setting, and engagement metrics with controls to access its settings. You may search or filter for specific categories of worlds using the toolbars.

Upload

The upload page allows you to manage and add specific content to your VIVERSE account. For each world, you can see its status, visibility setting, and an area to edit its settings.

The upload page can also be used to create and upload new worlds to VIVERSE.

Profile Settings

The settings page can be used to manage and update your profile information which is displayed for any viewers looking at your creator page.

Scene vs World URLs

When publishing to VIVERSE, creations will be given a single-player Scene URL and a multi-player World URL.

The Scene URL, such as https://create.viverse.com/scenes/1234567, is designed as a preview for creators to quickly iterate on their project's visuals and mechanics without worrying about networked gameplay. The Scene URL can be shared and accessed by anyone with access to the URL, however you will not be able to see or hear other networked avatars.

The World URL, such as https://create.viverse.com/aBCdEfG, is the fully published, multiplayer environment that may be made discoverable by other VIVERSE users on the world discovery page. The World URL's accessibility is determined by the World's settings. Here you will be able to see and hear other networked avatars who have access to the World URL

World Settings

A world's settings can be edited by clicking the kebab menu next to your world on your account page.

With the world settings, you can configure your world's name, description, thumbnail, and accessibility settings. Both Genre and Access will influence how your world is categorized and displayed on the VIVERSE world discovery page.

Worlds can be set to one of three accessibility states and can be password protected to add an additional level of security.

Worlds can be assigned a genre, which impacts curation and discovery on the VIVERSE webpages.

Worlds can also be assigned a device filter, regulating which user devices are intended to experience the world based on its optimization.

Discovery

Worlds that are made "Public" are discoverable on the VIVERSE world discovery page. Worlds are categorized automatically by genre settings and device compatibility (corresponding to file size and optimization level), as well as manually by the VIVERSE curation team.

What are the Creator Tools?

VIVERSE includes a robust series of tools for artists and developers to build engaging 3D experiences. These tools are sorted into two main categories:

• Integrations with development platforms, such as PlayCanvas and Unity, that allow creators to publish directly to VIVERSE.

• Developer tools and SDKs, such as Polygon Streaming, which can either be used in creations published to VIVERSE or hosted elsewhere.

Tools for Publishing to VIVERSE

VIVERSE is a web-based platform for 3D content where creators can showcase their work to the VIVERSE user-base and monetize. Our goal is to help you publish from the platform that works best for you and leverage your chosen tools. Whether you are hosting a meetup, creating an engaging narrative, or building a full length multiplayer game, there are several options for you to publish your work on VIVERSE.

Don't see your platform? Join our and let us know how you would like to be able to publish to VIVERSE.

Standalone Developer Tools

Along with our platform integrations that allow you to publish to VIVERSE, we also have a number of standalone developer tools that can be utilized in experiences hosted on and off of VIVERSE. These tools help creators get the most out of their 3D experience and make the difficult parts of online development easier.

NOTE: VIVERSE SDKs cannot be used with projects published via the , which do not have App IDs.

The Creator Community & Getting Support

VIVERSE is proud to support the work many of the most innovative artists, developers, educators, and entrepreneurs across the world. Our is the epicenter of our creator community and the best way to get connected with other innovative builders.

In the Discord Server, the community and VIVERSE team would love to hear your questions, bug reports, and ideas for making a more accessible platform. Simply create a new post in the #get-help channel when you land.

For issues related to your VIVERSE / HTC account, we recommend reaching out to the company-wide support channel:

Earning on VIVERSE

We are proud to support developers and teams of all sizes and artistic backgrounds on VIVERSE. In addition to investing in the development of new content on VIVERSE through our , we are excited to offer a number of ways for creators to earn on VIVERSE.

We are currently working to explore and release these tools to our developers. Here are some of the monetization methods that are/will be available to creators...

Default Loading Experience

Because web games and assets take time to transfer over the internet and load onto the player's device, user experience during loading is important. If shown a blank or broken-looking screen during this time, users may leave early, and never get to try the full experience.

While creators should optimize load time as much as possible, it's also somewhat inevitable. As such, VIVERSE provides a default loading experience during the asset pre-load phase:

Custom Loading Screens

However, some creators may wish to make custom loading screens more in line with the aesthetics of their game or app. This can help sell an overall sense of quality and immediately set the tone for users.

VIVERSE creators can make full use of . Just navigate to PlayCanvas Project Settings > Loading Screen and click "Create Default."

If you have the installed, this will inject a VIVERSE logo into the loading screen template, which is required for all projects.

Other than that, loading-screen.js is yours to customize. Add your logo, a tagline in a custom font, or a cool background image, grounding your users in your experience immediately.

Control Which Assets Download During the Loading Screen

All assets with the "Preload" box checked in asset settings will be downloaded during the loading screen phase. Limiting pre-loaded assets can help get users to your game view faster, which will result in fewer overall "bounces" from your game (meaning users who quit the game during loading). So only check "Preload" if the asset is immediately needed - otherwise it will stream in behind the scenes as needed, .

Media Polygon Streaming

Streaming 3D Models into The Environment

If you don't want to use default VIVERSE avatars for your world, the PlayCanvas SDK features a simple method to swap to any .vrm avatar asset in your project.

Per the API docs, import the PlayerService into your .mjs script, which has a localPlayer property of type LocalPlayer, which in turn has a .changeAvatar() method.

import { Script, Asset } from "playcanvas";
import { PlayerService } from "../@viverse/create-sdk.mjs";

export class VvSwitchAvatars extends Script {
  static scriptName = "vvSwitchAvatars";

  /**
   * @attribute
   * @type {Asset}
   */
  vrmAsset = null;

  initialize() {
    this.playerService = new PlayerService();
    this.playerService.localPlayer.changeAvatar(this.vrmAsset);
  }
}

NOTE: this script asset must be placed in /scripts or another subfolder, since it assumes the VIVERSE SDK is one level up, located at: "../@viverse/create-sdk.mjs" - or you can alter this import path as needed. For more information on how .mjs scripts and imports work, see Introduction to MJS.

Because vrmAsset is defined as an attribute of type Asset, we can then select which asset to use directly in the PlayCanvas editor once the script is added to an entity.

When we publish to VIVERSE and load the experience, the .vrm is loaded immediately. Avatar switching for the local player is possible at any point during runtime and can be triggered with UI, trigger colliders, or with any other programmatic callback. Reference Code:

Media Video

Adding Video And Extending Video Functionality

Introduction

In this getting-started guide, we will cover the basics of setting up a project and publishing to VIVERSE using .

Adding Media

Media are added to VIVERSE worlds in Edit Mode using the toolbar at the bottom of the screen. Detailed below are the categories of assets that correspond with the buttons in this toolbar.

Media Audio

Adding Audio And Extending Audio Functionality

An audio clip has been added to the scene.

WebXR experiences can run on desktop, mobile and virtual reality devices alike. Utilizing the XrService in the Create SDK, you can write custom code to manage VR controllers, locomotion settings, and XR session callbacks.

Custom Locomotion Settings

By default, the VIVERSE character controller uses teleport for locomotion, since this is the more comfortable option, in general. However, smooth locomotion (where the player glides smoothly across the floor) can be enabled on either or both controllers by setting the of each.

Import the from the Create SDK into an .mjs script. Per the API docs, this gives you access to both

Pick and Throw

This guide provides instructions for setting up the pick and throw object your Scene.

Introduction

The VIVERSE scene settings interface is used to control several settings for your entire VIVERSE world. The interface can be opened by clicking on the triangle button that is added to the left-hand toolbar when the extension is enabled:

Getting Started with Edit Mode

Edit Mode is available on all worlds you own or where you have been added as a co-owner/moderator. If you are a world owner or co-owner, you will have access to the "Edit Mode" button when you join the world.

When enabling Edit Mode, your controls and interface will be changed, and your camera will be detached from your avatar so that you can more easily navigate and edit your world. When in Edit Mode, your avatar will still be visible and your audio will be audible to others in the world.

The Edit Mode interface has three sections, the performance report in the top-left corner, the media upload toolbar in the bottom of your screen, and the object list in the top right where you can access and control the settings of all media added to your world in Edit Mode.

In order to save your customizations and have others see them, you will need to select the "Close edit mode" button and exit Edit Mode.

Viewing the Performance Report

Adding and Handling Media

Media can be added from several different sources through the toolbar in the bottom of the Edit Mode interface: Sketchfab, Marketplace assets, uploaded assets, and assets linked from external sources. For more information on the types of media you can add and their settings, see .

When media are added to your world, you can access and update their properties through the object list on the right-hand side of the Edit Mode interface. Furthermore, you can quickly reposition your media by clicking and dragging them through your world.

Adding Collaborators

You can add five additional VIVERSE accounts as co-owners of your world. By promoting these users, you are giving them full control over Edit Mode, moderation tools, and world settings for your world. Co-owners can be removed and will not be able to delete the world on your behalf. Co-owners can be added outside of Edit Mode by going to the hamburger settings button in the top-right of your world, selecting the "Permissions" tab, and adding Co-Owners by their user id or display name.

Seat

Add functionality to allow avatar to sit down

Introduction

In December 2025, VIVERSE and the Icosa Foundation, Open Brush's steward, teamed up with digital artist SUTU to create a publishing pipeline for Open Brush creators to host, distribute, and monetize their work on VIVERSE. When publishing to VIVERSE, creators are able to share their work on Mobile, Desktop, and VR through the web browser, complete with networked VRM avatars and real-time chat. The publishing process is a simple and powerful way for Open Brush creators to expand their audiences and make their work more accessible!

Publishing Tutorial

Tips & Troubleshooting

Introduction

This project was created by Dan Greenheck, a 3D web developer and educator, who authored all projects and the custom mesh destruction library. Check out his socials to see the other awesome work he is doing...

YouTube | LinkedIn | X/Twitter | Bluesky

Video Walkthrough

Project Resources

🎯 FPS SHOOTER DEMO —PlayCanvas Project: —VIVERSE World:

🏃🏻‍♂️ PLATFORMER DEMO —PlayCanvas Project: —VIVERSE World:

🪅 THREE-PINATA —NPM Package: —Source:

Templates are starter projects that are pre-built in VIVERSE. They are available on the profile page of your VIVERSE account.

Prerequisites

• In order to create worlds you must first create a VIVERSE account.

Overview

The Networked plugin allows local updates to certain properties of an entity's components to be sent to other connected avatars.

Transform

By adding the Transform component, an entity's position and rotation will be networked across clients.

Anim

By adding the Anim component, an entity's animation state will be networked across clients.

Networking Example

In this video, we have created an arena with a floor, four walls and a ball. The networking module has been added to the ball. After publishing and creating the world in VIVERSE, multiple players can join in the environment. The location of the ball is tracked across all player sessions.

To create the arena and ball in the video, you can follow the tutorial. The instructions below can be used to add Networking functionality to the ball or any other entity of your choosing.

Fundamentals

VIVERSE allows developers to use nearly any of the custom scripting interfaces provided by PlayCanvas, including but not limited to WebRequests like http & websockets, GLSL shaders, and 3rd party libraries imported directly into your project's hierarchy.

However, by default, VIVERSE's PlayCanvas SDK does automatically handles avatar transform and audio networking. For customizing any features related to the VIVERSE avatar, we provide an additional API reference (see VIVERSE SDK APIs below).

VIVERSE SDK APIs

The documentation for VIVERSE's SDK APIs is currently housed here: . We provide interfaces for customizing the default VIVERSE Cameras, Player, Network, and Environment, as well as the unique attributes when in an XR/immersive session in a VR headset.

These interfaces are automatically injected when you activate the VIVERSE Chrome Extension; The folder @viverse is added to your asset folder, which contains all interfaces in the create-sdk.mjs file. All interfaces can be imported and manipulated in your custom scripts.

A Note on No-Code Tools

In addition to adding the create-sdk.mjs file on initialization, the VIVERSE Chrome Extension adds create-extensions-sdk.mjs, which contains all of the interfaces between the no-code tools and PlayCanvas.

Within this file, you can see that each no-code function is assigned a unique trigger string, such as 'trigger:300006' for EntitySubscribeTriggerEnter. This is useful, because you can arbitrarily listen for and fire these exact same event names in custom scripts, connecting together the VIVERSE No-Code Functions and your custom code.

Introduction

Anyone can publish their WebGL-compatible Unity project to VIVERSE in a few simple steps. In this guide, we'll walk through the process of creating an new Unity project, making sure it is compatible with WebGL, and publishing to VIVERSE using the .

While VIVERSE is a great place for multiplayer games with networked avatars — and we have a number of services that can help you implement these features — it is not required to implement networked avatars to publish to VIVERSE.

The can be used to publish any working WebGL build to the VIVERSE platform after an authentication process.

Installation

Using npm:

Note: This CLI requires Node.js version 22.15.0 or higher.

EntityCheckPoint

Create An Action That Sets A New Spawn Point

This guide provides instructions for setting up the EntityCheckPoint action. In the sample app, once the avatar enters one of the green trigger areas, the area becomes the new spawn location.

In this example, a trigger area is created and when triggered, an action sets a new spawn location. Any object can be used as a trigger, as long as the object has a collision component.

TeleportAvatar

Create An Action That Teleports An Object To A Specific Location

This guide provides instructions for setting up the TeleportAvatar action. In the sample app, once the avatar enters one of the green cylinder trigger areas, the avatar is teleported to another location.

In this example, a trigger is created and when the avatar or other objects enter the trigger area, an action teleports the avatar to a specific location. Any object can be used as a trigger, as long as the object has a collision component.

VIVERSE provides a powerful camera system alongside its player controller and input scripting that allows developers to switch between different views and control various camera behaviors. This guide will show you how to implement camera switching in your VIVERSE project.

Basic Camera Switching

The VIVERSE player rig creates several cameras and switches between them depending on your settings and/or world scripting: CAMERA_3RD, CAMERA_1ST, CAMERA_VR, CAMERA_ORBITAL are all separate in the scene hierarchy.

The provides methods to switch between different camera views provided by the VIVERSE avatar rig. Here's a basic .mjs script importing the CameraService and switching to first-person camera mode on init. Simply attach this script to any entity in your project.

NOTE: this script asset must be placed in /scripts or another subfolder, since it assumes the VIVERSE SDK is one level up, located at: "../@viverse/create-sdk.mjs" - or you can alter this import path as needed.

Custom Camera Override Example

If the VIVERSE player rig cameras don't totally meet your needs, you can switch to your own camera entity for cut scenes or preview cameras. Here's a practical example of how to override the default VIVERSE camera with a custom camera on init:

Camera Switching on Events: VR and Player Ready

You can listen for certain events from other services that may be related to your desired camera behavior. For example, on the player:ready event, we know that all player cameras and scripting have loaded in and are ready to interact with the scene:

Additional Camera Properties

The CameraService provides several properties to customize camera behavior:

Additional Resources

EntityRigidbodyAddForceInPhysics

Create An Action That Adds Force To An Object

This guide provides instructions for setting up the EntityRigidbodyAddForceInPhysics action. In the sample app, once the avatar enters the blue trigger area, a force is applied to the sphere.

In this example, a trigger is created and when the avatar or other objects enters the trigger area, an action adds force to an object. Any object can be used as a trigger, as long as the object has a collision component. This example uses a 3D box as the trigger area.

Media Images

Adding Images And Extending Image Functionality

An image has been added to the scene and the image has been configured to always face the avatar

Using VIVERSE Studio offers several advantages:

• User-Friendly Interface: The platform is designed to be intuitive, making it easy for users of all skill levels.

• Community Engagement: Connect with other creators and receive feedback on your work.

EntityAssetUnload

Create An Action That Unloads An Asset From The Scene, Stops The Asset From Rendering And Retains The Asset In Memory

This guide provides instructions for setting up the EntityAssetUnload action. In the sample app, the trigger area is outlined in blue. Once the avatar enters into the trigger area, the asset stops rendering in the scene. This will decrease draw calls and improve frames per second, but the asset will be retained in memory.

We created a PlayCanvas sample project that contains examples of how to utilize the PlayCanvas Extension. Download the project and import it into a PlayCanvas account. Publish the project to VIVERSE and enter Preview mode to test out the functionality. The pages listed under API Reference are the functionality that the sample project is demoing.

This project is separated into different stations. Each station has Tags added to help identify the VIVERSE functionality the station is demonstrating.

Quest System

Create A Quest System

This guide provides instructions for setting up the Quest system. In the sample app, the trigger area is outlined in blue. Once the avatar enters into the trigger area, the Quest system starts. The first task requires the user to click on the red box. Once the user clicks on the red box, the first task is completed and the Quest system updates. The second task requires the user to click on multiple green boxes. Each green box that is clicked adds progress to completing the Quest task. Once all of the green boxes have been clicked, the task is completed and the Quest is completed. If the user clicks on a blue box during the quest, the quest system resets and needs to be triggered again in order to restart the quest.

VRAM Classification and Performance Recommendations

To ensure consistent performance and platform compatibility, our system classifies content based on VRAM usage per world and provides platform-specific performance recommendations. Developers should optimize their content to target the desired range of supported devices.

VRAM Usage Categories

The system automatically assigns a performance boundary level based on the amount of VRAM your world uses:

Platform Recommendations

Each boundary level maps to a set of recommended platforms, reflecting performance expectations:

Developer Guidance

• Targeting Wider Compatibility: Aim to keep VRAM usage under 500 MB to support the broadest range of devices.

• Optimizing for Android or iOS: Stay within Low or Medium boundary levels to ensure mobile device compatibility.

• High-End Visuals: Worlds exceeding 800 MB VRAM should be optimized for PC-only audiences.

For best results, monitor your world’s VRAM usage regularly during development and test on target platforms. Pressing 'Shift + .' will open the console to view various profiling values including VRAM.

The Scene Preview

This guide is a walkthrough for uploading and publishing a PlayCanvas project to VIVERSE Create.

Creating A World URL

This guide is a walkthrough creating World from Scene.

EntityToggleCollision

An Action That Toggles An Object's Collider On/Off

This guide provides instructions for setting up the EntityToggleCollision action. In the sample app, every time the avatar enters the green trigger area, a notification is sent to the wall and the collider on the wall is toggled on/off. The wall is green when the avatar can pass through and red when the avatar can not pass through.

In this example, a trigger is created and when the avatar enters the trigger area, an action sends a notification to toggle another object's collider on/off. Any object can be used as a trigger, as long as the object has a collision component. This example uses a 3D box as the trigger area.

EntityEnableCollision

Create An Action That Enables An Object's Collider

This guide provides instructions for setting up the EntityEnableCollision action. In the sample app, every time the avatar enters the red trigger area, a notification is sent to the wall object and the collider on the wall object is enabled. The wall is green when the avatar can pass through and red when the avatar can not pass through.

In this example, a trigger is created and when the avatar enters the trigger area, an action sends a notification to enable another object's collider. Any object can be used as a trigger, as long as the object has a collision component.

EntityDisableCollision

Create An Action That Disables An Object's Collider

This guide provides instructions for setting up the EntityDisableCollision action. In the sample app, every time the avatar enters the green trigger area, a notification is sent to the wall object and the collider on the wall object is disabled. The wall is green when the avatar can pass through and red when the avatar can not pass through.

In this example, a trigger is created and when the avatar enters the trigger area, an action sends a notification to disable another object's collider. Any object can be used as a trigger, as long as the object has a collision component.

EntityPlayAnimation

Create An Action That Plays An Animation

This guide provides instructions for setting up the EntityPlayAnimation action. In the sample app, once the avatar enters the trigger area, the character switches to the dancing animation state. When the avatar leaves the trigger area, the character switches back to the idle animation state.

In this example, a trigger area is created and when triggered, an action plays an animation. Any object can be used as a trigger, as long as the object has a collision component.

EntitySubscribeAnimationStart

Create A Trigger Based On When An Animation Starts

This guide provides instructions for setting up the EntitySubscribeAnimationStart trigger. In the sample app, when the avatar enters the blue trigger area, the character’s dancing animation begins to play. The dancing animation has an animation event added and the animation event is triggered whenever the animation starts to play.

In the EntityPlayAnimation example, a 3D model was added, an animation state graph was created, animation states were created and a trigger area was created to initiate the animations. In this example, an animation event is created for the start of the animation.

EntitySubscribeAnimationEnd

Create A Trigger Based On When An Animation Ends

This guide provides instructions for setting up the EntitySubscribeAnimationEnd trigger. In the sample app, when the avatar enters the blue trigger area, the character’s dancing animation begins to play. The dancing animation has an animation event added and the animation event is triggered whenever the animation stops playing.

In the EntityPlayAnimation example, a 3D model was added, an animation state graph was created, animation states were created and a trigger area was created to initiate the animations. In this example, an animation event is created for the end of the animation.

EntitySubscribeAnimationEvent

Create A Trigger Based On A Specific Time During An Animation

This guide provides instructions for setting up the EntitySubscribeAnimationEvent trigger. In the sample app, when the avatar enters the blue trigger area, the character’s dancing animation begins to play. The dancing animation has an animation event added and the animation event is triggered during the animation.

In the EntityPlayAnimation example, a 3D model was added, an animation state graph was created, animation states were created and a trigger area was created to initiate the animations. In this example, an animation event is created for during the animation.

EntityPlaySound

Create An Action That Plays A Sound

This guide provides instructions for setting up the EntityPlaySound action. In the sample app, once the avatar enters the trigger area, a sound plays.

In this example, a trigger is created and when triggered, an action plays a sound. Any object can be used as a trigger, as long as the object has a collision component. This example uses a 3D box as the trigger area.

EntityStopSound

Create An Action That Stops Playing A Sound

This guide provides instructions for setting up the EntityStopSound action. In the sample app, once the avatar leaves the trigger area, the sound stops playing.

In this example, a trigger is created and when triggered, an action plays a sound. Any object can be used as a trigger, as long as the object has a collision component. This example uses a 3D box as the trigger area.

Introduction

In this getting-started guide, we will cover the basics of setting up a ThreeJS project and publishing to VIVERSE using the VIVERSE CLI.

A. Installing Node.js

B. Installing Three.js and making an example project

This guide is a walkthrough for creating an example Three.js project

C. Installing Vite and using it to build your project

D. Installing the VIVERSE CLI

E. Logging in with the VIVERSE CLI

F. Publishing from VIVERSE

Introduction

The following specifications and guidelines will allow you to use our custom shaders in your own project. The project contains custom shaders, custom textures, materials and audio files.

You may use the Shaders, Models, Materials, cube Maps, Seamless Textures and Equirectangular Maps, yet, due to copyright, you are not permitted to use any other assets (such as 3rd party scripts: Audio files, Fonts, Noise Maps or Normal Maps).

Project Title: ShadeArt > Custom shaders showcase [VIVERSE VR Development Workshop -Experimental Shaders Development Space]. VIVERSE world link: Project link: