Project lifecycle and task-type conversion

A project card is the control point for rename, conversion, duplication, project export, cross-dataset Semantic search and deletion. Duplication creates an independent project with selectable label and annotation copying while reusing media bytes. Task-type conversion edits the existing project in place and can discard geometry, so inspect its calculated preview and export the original first.

Project actions

ActionResult
Rename projectChanges the display name; project data and ids stay in place
Duplicate projectCopies the project with options to include labels and annotations; excluding labels also excludes annotations. Keypoint and anomaly projects retain their required labels. Media bytes are reused by content hash
Change project typeConverts compatible annotations in place after a loss preview
Export projectWrites one lossless AnnotateIt archive for transfer or safety
Semantic searchSearches prepared still images across every dataset in the project on supported platforms
Delete projectRemoves the local project after confirmation

Conversion loss matrix

From → toWhat happens
Detection → segmentationEach box becomes a four-point rectangular polygon; labels are preserved
Segmentation → detectionEach shape becomes its tight bounding box; the precise outline is discarded
Detection/segmentation → classificationRegions and positions are discarded; labels are aggregated per image
Classification mode → another classification modeImage labels remain, but single-label conversion keeps only the dominant label and hierarchy must be rebuilt
Classification → detection/segmentationWhole-image annotations are removed; the label schema remains for new regional annotation
Keypoints → detection/segmentationEach pose becomes an enclosing box or rectangular polygon; joints and skeleton are discarded
Any ordinary project → keypointsBlocked because boxes, regions and image labels cannot define a skeleton

Before Convert project becomes available, the dialog counts affected media, source annotations, regions it will create, annotations it will drop and labels it will re-scope. These values come from the current project rather than a generic warning. If the project has saved prediction-model setups, the dialog also counts and warns that they and their label mappings will be removed. Private imported ONNX files are deleted, while shared downloaded checkpoints stay cached. Conversion cannot be undone; export the project first if the original may be needed.

Project export, dataset export and profile backup

Move one complete project to another installation
Export project
Hand training data to another tool
Export dataset, or Export all datasets as one
Protect everything stored by this installation
Settings → Backup
Return one dataset to an earlier working state
Dataset Versions — not a device backup

Demo projects

Projects installed from Demos behave like projects you created: they can be annotated, duplicated, exported, versioned and deleted. The Demo badge describes their origin and does not make them read-only.

See also

Video tutorial

AnnotateIt tutorial