# How Twinbly grew: June–October 2026

*Product history · Retrospective published November 1, 2026*

Twinbly brings together creating a 3D Gaussian splat, preparing it in a browser and sharing a place someone else can explore. These selected milestones show how that experience developed from June through October 2026.

June is the starting point of this archive, not a claim about Twinbly's launch date. The periods below describe capabilities available by then; they are retrospective summaries, not the original release announcements. For current availability, plan limits and instructions, follow the linked guides or browse [today's features](/features).

## The June baseline: capture, prepare and publish

By the beginning of June, the web app already connected the essential steps: upload supported video or a photo archive, review the proposed processing, follow the job in your library, and open the resulting capture in a browser. Creators could prepare a scene, add explanatory marks and media, and publish an interactive viewing link.

The visitor experience mattered as much as the capture. Saved views and navigation settings helped someone explore a place without learning an editor. Collections brought related published scenes together, so a property, trip or project could have more than one view.

That provided a practical starting point: capture a room or an object, explain what matters, and send someone a place to explore.

[Choose a processing workflow](/learn/processing-workflows) · [Publish and embed a scene](/learn/publish-and-embed) · [Organize a collection](/learn/library-and-collections)

## June: compose a place from several captures

**Added — combined scenes and matching points.** Creators could add another supported capture to a scene and align overlapping details. A wide capture could provide the setting while a closer capture showed a room, object or important feature. Matching recognizable points helped place those captures together; adding a layer did not automatically align it.

**Improved — preparing the view.** Leveling controls helped straighten a tilted scene. Measurements, adjustable placement and per-capture appearance controls made it easier to prepare a useful presentation and bring separate captures into visual agreement.

**Added — focus and guided exploration.** Zones could emphasize or limit parts of a view, while supported reveal controls let an interior or detailed capture appear when a visitor entered its region. Marks and tour controls gave people a route through the important parts of a scene.

For a property, that could mean an exterior overview with a more detailed interior. For a landscape, it could mean the wider setting and a closer look at a particular feature. Composition remains subject to the supported controls and limitations described in the current guide.

[Combine and align captures](/learn/combine-captures) · [Straighten and measure](/learn/prepare-and-measure) · [Build a tour](/learn/tours-and-navigation)

## July–August: share, gift and manage the result

**Added — gift a copy.** Gifting gave a recipient an independent library copy while the sender kept the original. This opened a different kind of handoff: a family memory someone can keep working with, a client's own capture, or a collaborator's starting point. A viewing link continued to serve people who only needed to explore.

**Added — richer scene context.** Scene photo galleries complemented marks and their attached media. Creators could put ordinary photographs alongside an interactive capture, helping visitors recognize a place and understand details that benefit from a conventional image.

**Improved — sharing and organization.** The public share sheet brought link sharing and QR access together. Library sorting and recently opened information made growing collections easier to navigate, and published-scene insights provided a view of recorded engagement.

**Fixed — calibrated measurements after resizing.** An August correction kept calibrated measurements consistent when a scene was resized. Measurements still depend on a suitable capture and a correctly chosen reference distance; this is not a guarantee of survey accuracy.

[Gift a splat](/learn/gift-a-splat) · [Add marks and photos](/learn/marks-and-media) · [Manage your library](/learn/library-and-collections)

## September: broader capture inputs and developer access

**Added — recordings with multiple parts.** Supported video clips could be brought into one processing timeline. A recording split across camera files could be reviewed together, with the creator checking order and selecting useful parts before processing.

**Expanded — 360 capture workflows.** Supported raw Insta360 recordings and stitched 360 exports gained web intake and preparation workflows. The distinction between a complete panoramic capture and a reframed flat video remained important; camera files still needed to meet the workflow's requirements.

**Improved — larger-site viewing.** Supported completed megasplats could open as one streamed scene, helping visitors explore a larger capture as a connected place. Available outputs and device limits still depended on the particular result and viewing environment.

**Added — a clearer path for developers.** Public API guidance, processing-key management and an activity console made it easier to build a product around Twinbly's processing services. Developers could manage access and follow their account's processing activity while building their own interface around available results.

The practical choice widened: use Twinbly's web experience, or use its documented services as part of another application. The [Legend Guide case study](/developers/legend-guide) now illustrates that second path and distinguishes Twinbly services from the application's own features.

[Prepare a capture](/learn/capture-guide) · [Understand processing and outputs](/learn/processing-workflows) · [Build with the API](/developers)

## October: clearer scene controls and a documented platform

**Improved — working with combined scenes.** Alignment gained a side-by-side way to inspect matching features. Library views made scene relationships easier to identify, helping creators distinguish a composed scene from the captures used inside it.

**Improved — boundaries and camera framing.** Zone editing brought drawing and adjustment into a clearer workflow, with a preview before saving and controls for moving a boundary. Supported combined scenes gained separate inside and outside lens choices, with visitor adjustments constrained by the creator's selected range.

**Fixed — everyday editing and job status.** Updates made annotation controls easier to read in dark mode, kept flight-speed controls with Drone mode, and made cancelled work appear as cancelled in the library and job report.

**Added — features, guides and visible update history.** A public feature directory and practical written guides documented capabilities such as gifting, alignment, measurements, previews and publishing. Product updates became available on the website and in the app. A visible web build and copyable support details made issue reports more precise.

[Read the October updates](/updates) · [Explore features](/features) · [Browse practical guides](/learn)

## Use the platform as it is today

This history is selective. It records customer milestones rather than every adjustment, and it does not establish current support for an older workflow. The [feature guide](/features), [learning guides](/learn), [developer documentation](/developers) and [pricing page](/pricing) describe the current product. New announcements continue in [Product updates](/updates).