Choose a capture and processing workflow
Twinbly brings capture processing, browser editing and sharing together. Start with the input you have, review the proposed work and its price, then use the result in the workflow it supports.
Photos, video and 360 captures
Overlapping photos and supported video can be processed into a 3D scene. Capture quality matters: move around the subject, keep useful detail visible, and avoid excessive blur or incomplete coverage. The capture guide explains common mistakes and supported 360 preparation.
Supported raw Insta360 captures and full stitched 360 exports have their own intake requirements. A reframed flat video is different from the complete panoramic sphere. Follow the current input instructions rather than assuming every camera's original files are accepted.
For drone photos and video, read the combined-capture guide. For a qualifying Matterport scan, read the E57 preparation guide. Specialized workflows have eligibility and input requirements; a guide does not mean every mode is enabled for every account.
Review before starting paid work
Twinbly can help assess a capture and propose processing choices. Where the controls are available, review input frames and adjust quality or processing choices for your goal. A quick share and a detailed presentation may call for different choices.
Read the estimate and any warnings before starting. Estimates are not guarantees of final cost, completion time or reconstruction quality. Quality labels are not a promise of a fixed GPU model. More spending cannot repair every unsuitable capture.
Use the current pricing page for plan limits and wallet information. Processing is funded through the wallet; subscriptions also govern platform capacity and features. Avoid treating included credit as unlimited processing.
Follow the job and inspect the result
Processing is asynchronous. Keep the job or capture in your library and follow its status. If a step fails, inspect the actual recovery action before starting more work. A retry can be a new paid operation.
When processing finishes, open the result and inspect what it captured. Prepare the scene, add useful context, and publish only when you intend to share it. A processing result is not automatically a public Twinbly page.
Understand output choices
Available assets depend on the job and conversion readiness. Some results provide source files; others are delivered through streamed formats. Training completion does not mean every optional conversion is ready, and not every result has PLY, SOG/SOGS and 3D Tiles at the same time.
Use the download or delivery links actually provided. If you export assets, verify what edits are included: hiding or clipping part of an interactive scene does not inherently remove it from source geometry.
Larger sites and surveys
The Survey Console supports eligible larger capture workflows. Good positioning data and capture coverage matter. Standard GPS, corrected positions and verified survey accuracy are different things; review measured results rather than assuming every reconstruction is survey-grade.
Plan, rollout and workflow restrictions apply. Specialized refinement, baking and tile-recovery options should be used only when offered and documented for your account. Do not assume a capability is generally available because it appears as planned in a schema.
Build an integration or use an agent
The developer guide provides a more detailed path: create an appropriate processing key, quote work, upload, start, monitor and retrieve available outputs. Keys use their owner's account and wallet. Store secrets in a protected runtime, not a public page or shared prompt.
An agent should obtain a spending decision, preserve the job handle and reconcile uncertain results before retrying. Processing keys and read-only scene tokens are different credentials. A dedicated CLI or MCP server is not required to use the documented HTTP API; do not invent an installation or connection address.
Developer guide as Markdown · Explore features · Start a capture