Skip to main content
Inspiring
October 17, 2025
Solved

Testing updates after releasing the world?

On Steam, there is beta branch where live testing can happen without affecting releases. Is there something similar in Meta Horizon Worlds?

I would like to release my world with core gameplay and base set of assets. This way I can see users' engagement with the world, while working on expanding it in the direction somewhat influenced by the engagement. And of course I'd like to be able to test updates live, before releasing it to the general public. 

VirtuallyARealDinosaur
Community Manager
October 17, 2025

Thanks for the confirmation.

If you have a published world, some folks have a Dev world that is not public in which they invite a limited amount of testers where they make changes before importing the Dev world into the published one using the import world function.

Edit:  found the import world function!

Edit 2: Just to add context for other folks - The "Import World" option is only in the VR editor.

10 replies

VirtuallyARealDinosaur
Community Manager
October 17, 2025

Hello!

Thank you for your post.

You may be able to create a member-only world and invite people as playtesters and build it out. Once you're satisfied, you can copy the world and publish it publicly.

I hope this helps!

motorsepAuthor
Inspiring
October 17, 2025

Thanks, but that sounds cumbersome. If I have a world running, then I have to create another world to test, then when I copy it, wouldn't it create entirely different world than the originally published?

VirtuallyARealDinosaur
Community Manager
October 17, 2025

Let me make sure I understand what your ask is.

You have a published world right now, available to public, you want to test changes to it. You duplicate it, set the duplication to members-only, make changes to test on the members world, once satisfied, you are concerned about having to duplicate the members world you made as a copy to your original already published world?

Is that correct?