Spline's Omma Connects Studio Assets to Canvas for Integrated Web Deployment.

Spline has quietly shipped a bridge between its creative and deployment tools. Users can now import assets from Omma Studio directly into Omma Canvas and Omma Chat, eliminating the need to recreate or manually transfer work between environments.

The announcement on LinkedIn was brief, but the implications are clear for creators already working across Spline's AI-powered stack. Omma Studio, launched earlier this year, handles asset generation using text prompts for 3D models, video, and audio. Omma Canvas, introduced shortly after, orchestrates up to 100 parallel AI agents to build interactive web experiences, apps, and games.

Until now, assets created in Studio existed in isolation. Designers would generate a 3D object or video clip, then face friction moving it into a live project. The new import capability means a model generated in Studio can be dropped into a Canvas project without export-import gymnastics or format conversions.

This matters most for teams prototyping quickly or iterating on interactive experiences. A designer working on a product landing page can now generate variations of a hero asset in Studio, test them in Canvas alongside live code and physics simulations, and push the winner to production—all within Spline's ecosystem.

Omma Canvas already supports standard formats like GLB, GLTF, CSV, and JSON, so the Studio integration likely follows similar patterns under the hood. The difference is workflow speed. Instead of context-switching between tools, creators stay in a single environment where assets, agents, and deployment are tightly coupled.

The practical use cases stack up quickly:

Prototyping with real assets. Instead of placeholder shapes, designers can work with final or near-final 3D models, animations, and soundscapes from the start.

Iteration at production speed. Generate multiple asset variations in Studio, import them to Canvas, and let AI agents build out UI, interactions, and logic around each version in parallel.

Unified asset libraries. Teams can maintain a Studio collection of brand-consistent 3D elements, videos, and audio that feed directly into Canvas projects across campaigns or product launches.

For solo creators, this collapses the creative pipeline. A developer building an interactive educational prototype or webcam-controlled game can now generate custom assets in Studio, import them into Canvas, and deploy a working prototype in a single session.

Spline continues to position Omma as experimental. The company describes the beta as "a bit experimental" on its updates page, and this latest feature follows that tone. The LinkedIn post offered no documentation, no walkthroughs, just a one-line capability announcement.

That sparse communication style is consistent with how Spline has rolled out Omma features so far: ship fast, let users discover capabilities, iterate based on what sticks. It works when the product is intuitive enough that people can figure it out by poking around, which seems to be the bet here.

For teams already embedded in the Spline ecosystem, this update removes a pain point. For designers evaluating whether to commit to Omma's multi-tool workflow, it strengthens the case that assets created in one part of the platform won't get stranded.