# Organize your scenes and collections

Your library is where you work with captures. Published scenes are the experiences you share. Collections bring related published scenes together under one link.

## Find the capture you need

Use library search, source filters, status filters and sorting to find a capture or job. Depending on your content, the library can show drafts, published items, processing work, combined scenes and larger projects.

Keep useful names on your captures. A name such as a room, location or date is easier to recognize later than a camera's original filename. Where different sources appear together, inspect the source and status instead of assuming every item came through the same workflow.

## Bring a splat you already have

Twinbly supports importing compatible existing splats so you can prepare and share them without running a new photo-to-3D job. Start with the Import action in the library and follow the file types accepted by the current upload control.

The public import workflow includes PLY. A file with a familiar extension is not a guarantee that every encoding or asset layout is supported. Check the imported result before promising an external file will work. An imported capture may also lack camera-path or processing data used by other tools.

## Work on a scene, then share it

Open a library capture in the viewer or editor. You can prepare its appearance, add explanations and decide when to publish. A scene assembled from several captures still has relationships to its component captures; read deletion warnings before removing one.

When you want someone else to maintain an independent copy, use [gifting](/learn/gift-a-splat). When you want to keep control of the shared experience, use [publishing](/learn/publish-and-embed).

## Make a collection

Use Collections to create a group of related published scenes. Add a meaningful title and description, select the scenes, and arrange them in an order that makes sense. Review the collection's own visibility before sharing its link.

Useful examples include several rooms of a property, a series of places on a route, a group of artworks, or captures made at different project stages. A collection groups scenes; it does not geometrically merge them or automatically create a synchronized comparison tool.

Member-scene access rules still apply. A collection cannot make a draft or unavailable scene public simply by including it. Collection limits depend on your plan.

## Follow processing and recover deliberately

For processing captures, inspect status and the app's failure or recovery message. Starting again or reprocessing may be a new paid operation; review the estimate and keep track of the existing job before creating another one.

Cancelled jobs show Cancelled in the library and job report. Their elapsed time stops at the recorded cancellation rather than continuing as active processing.

In-app notifications and available email preferences help you follow work without watching a progress page continuously. Delivery depends on your preferences and the available notification channel.

## Review activity and available files

Published-scene insights can help you understand views and engagement. Treat them as collected observations, with the history and detail actually available, rather than a complete visitor census.

Download or retrieve the formats offered for the particular result. Some outputs are streamed or still being converted; not every capture offers every file type. Scene display edits do not necessarily change exported source geometry.

[Understand processing and outputs](/learn/processing-workflows) · [Open your library](/dashboard/library) · [Compare plans](/pricing)