# Publish, share and embed a scene

Turn a finished capture into a link someone can explore in a browser. Twinbly separates your working library capture from publishing, so you can prepare the scene before deciding how to share it.

## Prepare the visitor experience

Open the scene in the editor, check its orientation and appearance, add useful explanations, and set an arrival view. Choose supported movement and idle behavior. Use a title and description that tell a visitor what they are looking at.

Publishing and saved editing are distinct actions. After changing an already published scene, use the appropriate update action and inspect the public result; do not assume every unsaved editor change is already live.

## Draft or live

Use a draft when you are preparing the presentation. A draft is not the same as a public viewing link. Publishing limits and private-sharing or branding options depend on your [plan](/pricing).

When ready, publish and open the resulting link. Check it from a visitor's perspective: the first view, navigation, marks, media and any inserted captures should tell the intended story.

For a client review, an explorable link is often enough. If the client should have their own editable library copy, use [Gift a copy](/learn/gift-a-splat) instead.

## Put it on a website

The sharing controls provide an iframe embed. Choose a supported layout such as landscape, square, portrait or the responsive container option, then copy the embed code into a website area that allows iframes or custom HTML.

Use a landscape embed for a wide property section, a portrait shape for a narrow layout, or a square presentation for an object. Preview the page at phone and desktop widths. Your website provider may restrict custom embeds, so follow its own publishing instructions.

A Twinbly embed remains interactive. It is different from uploading a [preview video](/learn/preview-clips) to another service.

## Understand visibility

Public scenes can be discoverable through Twinbly's public surfaces. Private-sharing options reduce discovery and use direct links, subject to the plan and the scene's settings. Do not treat possession of an unlisted or private link as password protection or assume that every asset requires a recipient account.

Share direct links only with the people you intend to reach. Review optional source-media and external-access settings before publishing. Hiding part of a scene with an editor tool does not prove that source files no longer contain that part.

## Branding, covers and context

Publisher profile fields can help visitors understand who made a scene. Badge controls depend on your plan. Use a useful scene description and relevant links so the capture has context.

Where available, choose an annotation photo as the link-preview cover. This is separate from the initial camera view and the moving preview. Other services may cache a cover or choose a different presentation, so inspect the actual shared result.

## Update, unpublish and restore

Use your published-scene controls to manage live scenes. Unpublishing stops the public link from serving that publication while keeping the library capture. The recently unpublished area provides a restoration path where available; review capacity and scene state when restoring.

Review scene insights when you want to understand visits and engagement. Historical detail is limited to what was actually collected; a count is not a complete record of every person who saw a scene.

To present several scenes under one link, create a [collection](/learn/library-and-collections). A collection does not override the visibility or availability of its member scenes.

[Open your library](/dashboard/library) · [Choose tours and movement](/learn/tours-and-navigation) · [Compare plans](/pricing)