The upload wizard has four steps: Setup, Preview, Upload, Completed. Setup has two halves. On the left you describe the project; on the right you point Twinsity at your three exports. The reconstruction software you pick on the left decides what the pickers on the right accept, so work left to right.
The wizard opens on Setup.
| Field | Required | Notes |
| Project title | ✓ | Free text. |
| Asset type | ✓ | What you are inspecting: bridge, building, and so on. |
| Reconstruction software | ✓ | The tool that produced your export. |
| Observation profile | ✓ | Which set of observation classes and fields the project uses. |
| AI processing | — | Optional. Which AI models to run, if your plan includes them. |
The observation profile defines the observation classes and fields your team fills in for every finding. Choose the one your inspection uses. See Setting up Observation Profiles.
Under AI processing, select the models to run on this project. Detections appear in the project's Smart Detections view once processing finishes. Leave it empty to skip AI entirely.
Twinsity expects different file formats from each tool, so this choice:
Pick the tool you actually exported from. If your files do not match the choice, the wizard warns you at this step rather than after a long upload.
The Select Project Files heading carries two buttons, With images and 3D model only. Leave With images selected to upload all three exports. If your project has no photography behind it, see Uploading a 3D model without images.
| Picker | You choose | Accepted |
| Camera metadata | A file for every tool but Pix4Dmatic, where it is a folder | .xml (Metashape, iTwin Capture, DJI Terra), .csv (RealityScan), OPF folder (Pix4Dmatic) |
| Images | A folder | .jpg / .jpeg |
| 3D model | A file | .zip or .3tz, whichever software you chose |
Camera metadata files have a 50 MB limit. It does not apply to Pix4Dmatic's OPF folder.
Pix4Dmatic produces an OPF folder of .json files, so the camera metadata picker switches to folder mode when you select that software. If you cannot find a single file to choose, check which software is selected.
Twinsity finds the 3D Tiles root file inside your archive, whatever it is called and whether or not it sits in a subfolder. Zip your export however your software produces it. No renaming, no flattening.
The one exception: tilesets using implicit tiling are not supported. If a model will not load and your export used implicit tiling, re-export without it.
Most exports should use WGS 84 (EPSG:4326), but they differ. DJI Terra wants an arbitrary coordinate system at the preprocessing stage. Each export guide states what its own tool needs.
RealityScan projects using local coordinate systems cannot be imported. Geo-referenced exports work for every supported tool.
The wizard validates while you select, so problems surface here rather than after uploading:
| Check | What it means |
| Software match | Does the metadata file look like it came from the tool you chose? |
| Coordinate system | Can Twinsity read the georeferencing? If not, the upload is blocked. |
| Images ↔ cameras | Does every camera in the metadata have a matching image? See Understanding how your images are matched to the model. |
| File and folder names | Do any names contain characters we cannot accept? See Troubleshooting missing images and rejected files. |
| 3D model present | Has a model file been chosen? Its contents are checked at the next step. |
A warning does not stop you. A blocking error must be fixed before Next works.
Once the wizard knows the total size, it compares it with your remaining storage. If it does not fit you will see Storage limit reached, with the project size and the space available, and you cannot continue.
Checking the preview before you upload.