Marble
- Organization: World Labs
- Primary framing: 3D world creation
- Audience signal: Creators, spatial designers, developers
- Output emphasis: Persistent editable 3D worlds
Decision guide · Updated 2026-05-25
Decision guide: Marble vs GWM-1
Two paths into the same future. Pick the one that matches what you want to see, build, or understand.
researchMarbleGWM-1
Visual comparison
Visual comparison
Choose by the job, then check the sources.
Are you comparing a current spatial creation product or a media-company research direction toward general world models?
GWM-1
- Organization: Runway
- Primary framing: General world model research
- Audience signal: Creators, researchers, robotics-adjacent observers
- Output emphasis: Worlds, avatars, and broader future model direction
Choose Marble if
3D world creation
Choose GWM-1 if
General world model research
Check the boundary
The two should be compared as strategic directions, not as identical product offers.
Stable profiles
What this guide decides
- Marble is easier to understand as a current product category.
- GWM-1 matters because it shows a media-generation company repositioning around world modeling, with Characters as a concrete avatar-facing deployment path.
- The two should be compared as strategic directions, not as identical product offers.
Use cases
- Open Marble when that side better matches the visual outcome you want.
- Open GWM-1 when the second path better matches the product or research signal you are checking.
- Use the table below for source-backed details after the visual decision.
Detailed table
The citeable differences stay here.
The table is still available for source-backed comparison, but it no longer owns the first screen.
| Dimension | Marble | GWM-1 |
|---|---|---|
| Organization | World Labs | Runway |
| Primary framing | 3D world creation | General world model research |
| Audience signal | Creators, spatial designers, developers | Creators, researchers, robotics-adjacent observers |
| Output emphasis | Persistent editable 3D worlds | Worlds, avatars, and broader future model direction |
| Commercial signal | Product and API path | Research base plus deployed Characters surface |
FAQ
How should this comparison be read?
Read this page as a category and source comparison, not as a universal benchmark or availability claim. Product access, API access, and open-source status should be checked against the cited sources.
Does this comparison imply every system is a purchasable product?
No. World Models Watch separates comparison coverage from product availability, API access, and commercial claims.
Sources
FAQ
Comparison FAQ
The FAQ explains how comparison pages keep reported, official, product, and research signals separate.
What does World Models Watch count as a world model?
The site tracks systems that model environments, actions, spatial structure, or persistent simulated state. Pure text chatbots and ordinary video generators are only included when they provide a clear bridge toward interactive or physical world modeling.
Why do some AI video systems appear on a world-model site?
Video models are included only when they help explain the path from generated clips to controllable spaces, physics-aware prediction, or agent-ready simulation. The site keeps that distinction explicit so video generation is not overstated as a finished world simulator.
How does the site decide whether a release is reliable enough to list?
Primary sources carry the most weight: official product pages, research posts, papers, documentation, code repositories, and company announcements. Secondary media can be referenced, but it stays labeled as reported or adjacent unless independently confirmed.
What should readers post in comments?
Useful comments add source links, corrections, release-status notes, comparison questions, or concrete reader context. Comments are public immediately, so readers should avoid private information and unsupported promotional claims.
Discussion
Reader discussion
Add source-backed corrections, questions, or notes for this page.
Comments are ready in the codebase. Configure NEXT_PUBLIC_SUPABASE_URL, NEXT_PUBLIC_SUPABASE_PUBLISHABLE_KEY, SUPABASE_SECRET_KEY to enable Supabase-backed discussion in production.
No comments yet. Start with a source note or a question for future coverage.