World Labs continues its steady Marble updates. Since formally launching the generative world model last November, the company has shipped export refinements, introduced an API, closed a billion-dollar fundraising round, and previewed Spark 2.0, all in the span of a few months. Today’s release adds two new models, Marble 1.1 and Marble 1.1 Plus, each representing a distinct improvement to how the platform generates 3D worlds.
Marble 1.1 is positioned as the new default. World Labs recommends it as the starting point for new users, replacing the original model (now labeled Marble 1.0) with what the company describes as improved generation quality at the same fixed cost of 1,500 credits per world. The upgrade brings better output fidelity without changing the pricing or workflow and should be a drop in improvement.
The more interesting addition is Marble 1.1 Plus. Where previous Marble models generated worlds within a fixed spatial footprint, 1.1 Plus automatically expands its coverage of 3D space to produce larger worlds when the scene allows for it. The pricing reflects this; a 1,500-credit base cost plus 300 credits for each additional “dynamic cube” the model adds during generation. It is a variable cost structure, which is new for Marble.
When the platform launched, the ability to generate explorable 3D environments from text prompts was the headline. But practical constraints around world size and editability were always part of the tradeoff. With 1.1 Plus, World Labs is pushing against the spatial ceiling with larger, more expansive worlds generated in a single pass, without requiring users to manually expand boundaries.
Alongside the new models, the update brings several quality of life improvements. A new model selector now appears in the omnibox and other Create surfaces, making it easy to switch between Marble 1.0, 1.0 Draft, 1.1, and 1.1 Plus. The assets page now shows which model was used to generate each world or draft. Advanced editing has been surfaced more prominently under a new “Create & edit” option in the omnibox, and the assets page itself has received visual, layout, and performance improvements.
On the bug fix side, World Labs has resolved an issue where multiple projects open across different browser tabs would conflict with each other and fixed a visibility cascading issue in Studio where toggling a parent node’s visibility did not properly propagate to child nodes.
The original Marble 1.0 and Marble 1.0 Draft models remain available, so existing workflows are unaffected.
Learn more about the latest Marble update on the World Labs documentation site.
