Skip to main content

Teleportation Mechanism

After a portal has been created and displayed to users, users can teleport through the portal from the origin virtual world to the destination virtual world using one of the three teleportation mechanisms below.


For Web-based VR and AR environments, MHTTP leverages the simplicity and ubiquity of HTTP to teleport from current world to destination world. For apps and game environments where HTTP is not used as a navigation mechanism, MHTTP supports both deeplinks and what we call bridging to perform teleportation.

Deeplinks are useful for apps and games that already support iOS or Android deeplinks. They can be inserted directly into Open Portal Schema’s destination.url property as follows:

"destination": {
"url": "mymetaverse://lobby"


Bridging is useful for ecosystems like Roblox, where the main way of transporting a user from one world to another world within Roblox is through Roblox’s own API calls. It is not done through a URL or deeplink.

If you are creating a portal within ecosystems like Roblox, instead of providing a URL or deeplink, you can provide enough information in the Open Portal Schema file for teleportation to still happen. To teleport into a particular Roblox world, the MHTTP-Roblox bridge looks at the portal JSON file, extracts the relevant properties, and invokes the necessary Roblox API calls with the necessary parameters to teleport the user.

A series of MHTTP-[different platforms like Roblox and Minecraft] are on the roadmap to translate MHTTP into teleportation mechanisms native to each platform.