Your camera-metadata file lists every image used in the reconstruction and where it was taken. During upload, Twinsity pairs each of those entries with the actual image file in the folder you selected.
That pairing is what lets you click the model and see the images that show that spot. When it goes wrong, images go missing from the project.
Twinsity matches on the file path, not just the file name.
Your metadata lists paths like ../images/DJI_0142/FARO_0031.jpg. Twinsity compares those against the paths of the images you selected, matching on as much of the trailing path as it needs to identify each one uniquely.
This is automatic. There is no setting to switch it on.
Multi-camera rigs commonly produce identically-named files in different folders:
images/DJI_0142/FARO_0031.jpg
images/DJI_0143/FARO_0031.jpgTwo different images, same file name. Matching on the name alone would collapse them into one, and one camera would silently lose its image. Including the folder keeps them distinct.
If two files are genuinely indistinguishable by path, that camera entry is reported as unmatched rather than paired with a guess. You will see it in the alignment result as an unmatched camera.
A missing image is visible; a wrongly paired one is not, so an unmatched camera is reported instead of guessed at.
At the Setup step, once metadata and images are both selected, you get one of:
| Result | Meaning |
| Everything paired | Every camera has its image. |
| Some unmatched | The upload continues; those images will be missing. Worth investigating first. |
| Nothing paired | Blocked. Almost always the wrong image folder, or metadata from a different processing run. |
If you need to tidy filenames, do it before exporting from your photogrammetry software, so the metadata records the tidied names.