Skip to content

Ultralytics Public

Introduction

The VisionCapsules® AI Marketplace can download an Ultralytics YOLO model and package it as a VisionCapsule automatically, without any capsule code. It downloads the weights from Ultralytics, converts them to OpenVINO on your own server, fills in one of the capsule templates published in the ultralytics directory of the Capsule Zoo, and packages the result into the open vision capsule format (a .cap file) in My VisionCapsules.

This page covers:

  • how to download and package a model in the AI Marketplace;
  • what each kind of model reports;
  • which Ultralytics models are not packaged yet.

The capsule templates, the choice of classes and the processing time of the capsules are on the YOLO Capsules page.

Note

AOTU does not distribute these capsules. They are built on your machine from the Ultralytics weights, which are licensed under the Ultralytics AGPL-3.0 License. The AI Marketplace asks you to accept the license before it packages a model. The server needs internet access to download the weights, and the packaging service must be running next to the marketplace (the dialog shows a warning if it is not).

Download and Package a Model

  1. Open the AI Marketplace.
  2. In Explore VisionCapsules, choose Ultralytics Public in the source menu. The list shows the weights that Ultralytics publishes, grouped by family (YOLO26, YOLO11, YOLOv8, ...). Use the model version menu to show one family.
  3. Click the download icon at the end of a row, or tick several rows and click Download & Package Selected.
  4. The dialog Package Model into Open Vision Capsules Format opens for the first model, filled in from the model you chose. The source, model version, task, format, weights file and input size are fixed; you can change the capsule name and version. When you chose several models, each one gets its own step, one after another. OK goes to the next model; it is enabled once you have accepted the license and the fields are valid. Cancel drops that model only. Depending on the model, the step shows more fields after the common ones:

    Model What the step shows
    Detection and segmentation The model's own class names, read from the weights and shown read-only, and how many there are (Maximum Vocabulary classes). The default class names are optional and editable: the capsule's classes option starts with them (empty: every class), and can be changed at run time.
    Oriented boxes (-obb) The same class names. The default class names are greyed out: the classes option is not available for these models.
    Pose (-pose) The same, and the keypoint names, which start with the 17 COCO person keypoints (nose, left_eye, ... right_ankle) and can be edited. Empty means the same names for a model with 17 keypoints, and numbered names (keypoint_1, ...) for another number.
    Classification (-cls) The model's own 1,000 ImageNet class names, read-only, and the default class names (optional, editable: the classes the attribute can take; empty: all 1,000). Then the classes of the detections to classify (for example person) and the name of the attribute to set.
    YOLO-World and YOLOE The vocabulary (it starts with the 80 COCO classes; up to the maximum number of classes, 100 by default) and the default class names. See Vocabulary and Default Class Names.
    YOLOE prompt-free (-pf) The same two boxes. The vocabulary is fixed (4,585 classes) and read-only; you choose the default class names.

    The class names are read when the step opens. The weights are downloaded for that, and the first time the converter is installed, which takes minutes. You can press OK without waiting; the weights are downloaded again when packaging.

  5. OK on the last model starts the download and the packaging of all the models. The dialog then shows the progress of each model (downloading, converting, testing, packaging). Each model appears under the name it will have in My VisionCapsules, for example Detector Yolo26s Seg.

  6. When a model is done, it is in My VisionCapsules, named detector_<model> (classifier_<model> for classification), for example detector_yolo26n. Load it with the right arrow or Run Selected, and enable it on a stream like any other capsule.

The first time, the converter (PyTorch and Ultralytics, about 1.5 GB) is installed. YOLO-World and YOLOE also download a text encoder (350 to 600 MB). This can take several minutes; later models are much faster.

To package a model that is not in the list, for example one you trained yourself, click Package Model in My VisionCapsules and provide the .pt file, the OpenVINO files (.xml and .bin) or an ONNX file. The form has the same fields as the dialog above, and you fill them in yourself.

Capsule Name and Version

The capsule name is generated from the model (for example detector_yolo26s_seg); a number is added if the name is already taken. The Version is a whole number from 1: it is the capsule's own version, written in its capsule.py (version = 1) and reported by BrainFrame. The capsule format requires an integer there. In My VisionCapsules, the version column shows the model family and the version, for example YOLOE | v1, like the v0.32.0 | v1.0 of the capsules in the AOTU list, which show the release and the release version.

What the Capsule Reports

Task What each detection contains
Object detection A class name, a bounding box and a confidence.
Instance segmentation A polygon that outlines the object, derived from its mask. The mask_threshold option tunes the outline.
Pose estimation A bounding box, and the keypoints in the extra data keypoints, as [x, y, confidence] in frame pixels.
Oriented boxes A rotated rectangle (its four corners), and its angle in the extra data.
Image classification An attribute set on the detections of another capsule. A classifier capsule follows a detector.

Models That Are Not Packaged Yet

These weights appear in the Ultralytics Public list of the AI Marketplace, greyed out, with the reason in the description. They are not packageable yet. This lists what has not been built, not what cannot be done. Some of them (SAM, SAM 2, MobileSAM and YOLO-NAS) are not Ultralytics models: Ultralytics hosts the weights and supports them in its library. What each one needs:

Models What is missing
yolo11n-grayscale A template for a one-channel input. The converter reads the model, but the capsule fails to run it because the templates feed three color channels. The template would convert the frame to grayscale first.
YOLOv8 -human models, YOLO26 -reid and -s3d A converter that can read them. The Ultralytics version that the converter installs (8.4.214 when this was tested) does not have the model classes these files need (HumanModel, ReidModel, the s3d module). With a version that does, they may fit an existing template (not checked).
YOLO26 -depth and -sem (semantic segmentation) A decision on how a capsule reports them. The converter refuses these tasks today. A depth map or a class per pixel has no BrainFrame output type of its own; semantic segmentation could be reported as polygons per class.
YOLO26 -stereo3ddet A way to give the capsule two images, since it detects from a stereo pair. Not evaluated yet.
SAM, SAM 2 and MobileSAM A capsule that takes prompts, for example the boxes of another capsule, and returns masks. Not evaluated yet.
YOLO-NAS A converter for the library it comes from, and a template for its output. Not evaluated yet.

Models Without Weights in the Releases

The list in the AI Marketplace is built from the weight files (.pt) that Ultralytics publishes in the releases of its assets repository. The marketplace reads the releases from GitHub and keeps the result for six hours, so new weights, and new releases, appear without a software update. If GitHub cannot be reached, it shows the last copy it has, or the list that shipped with the software.

The Ultralytics models page also describes models for which Ultralytics publishes no weights in these releases: YOLOv4, YOLOv6, YOLOv7, SAM 3, and YOLO27 (marked "Coming Soon"). They are not in the list. To use your own copy of such a model, export it to OpenVINO or ONNX and add it with Package Model. That has not been tried for these models.