YOLO26: NMS-free detection and segmentation

YOLO26 is Ultralytics' newest real-time detector. It finds objects of COCO's 80 classes and returns a box, a class and a confidence for each, and the seg- variants add a mask to every box. Unlike the other YOLOs it needs no non-maximum suppression: the head fires once per object. Five sizes of each, from 6 MB to 142 MB. Its weights are AGPL-3.0, which matters if you serve predictions over a network: read Weights and licence before you deploy it.

Quick start

Python
import mozo

model = mozo.get_model("yolov26/nano")
found = model.predict("example.jpg")

for detection in found[:4]:
    print(detection.class_id, detection.class_name, round(detection.confidence, 2), detection.bbox)
Text only
0 person 0.95 [1305.39, 18.11, 1920.0, 1266.54]
0 person 0.93 [2.34, 121.61, 767.89, 1264.8]
67 cell phone 0.89 [1164.36, 1083.57, 1452.57, 1186.46]
0 person 0.83 [838.34, 220.17, 1454.06, 818.27]

Over HTTP, with mozo start running:

Bash
curl -X POST "http://localhost:8000/predict/yolov26/nano?threshold=0.5" -F "file=@example.jpg"

The response is the same detections as a JSON list, with every PixelFlow field on every detection.

Variants

ID Task Weights (torch) Runtimes Licence
yolov26/nano detection 6 MB torch, onnx AGPL-3.0
yolov26/small detection 20 MB torch, onnx AGPL-3.0
yolov26/medium detection 44 MB torch, onnx AGPL-3.0
yolov26/large detection 53 MB torch, onnx AGPL-3.0
yolov26/xlarge detection 119 MB torch, onnx AGPL-3.0
yolov26/seg-nano instance segmentation 7 MB torch, onnx AGPL-3.0
yolov26/seg-small instance segmentation 23 MB torch, onnx AGPL-3.0
yolov26/seg-medium instance segmentation 55 MB torch, onnx AGPL-3.0
yolov26/seg-large instance segmentation 64 MB torch, onnx AGPL-3.0
yolov26/seg-xlarge instance segmentation 142 MB torch, onnx AGPL-3.0

runtime="auto", the default, picks torch on every device. To run ONNX instead, load the model through a ModelManager, which takes runtime:

Python
from mozo import ModelManager

model = ModelManager().get_model("yolov26", "nano", runtime="onnx-fp32")   # pip install 'mozo[onnx]'

There is no CoreML artifact; No CoreML says why.

Inputs and outputs

Python
model.predict(image, threshold=0.5, labels=None)
Parameter Type Default Description
image str, bytes or numpy.ndarray A file path, encoded image bytes, or an HxWx3 RGB array.
threshold float 0.5 Minimum confidence to keep a detection.
labels list[str] None Class names for this call, replacing the checkpoint's own.

Returns a PixelFlow Detections, best first. Each detection has:

Over HTTP the same parameters are query parameters: threshold, and labels as a comma-separated list (labels=hardhat,vest).

How it behaves

No suppression step

The head fires once per object and the network returns a ranked list of detections, so there is no overlap threshold to tune. predict still takes a confidence threshold and returns the same PixelFlow result as every other detector. YOLOv8, YOLO11 and YOLO12 suppress overlaps in the usual way.

Masks

The seg- variants answer the same call with a mask on every detection, aligned with its box:

Python
found = mozo.get_model("yolov26/seg-nano").predict("example.jpg", threshold=0.25)
mask = found[0].masks[0]
mask.shape, mask.dtype      # ((1281, 1920), dtype('bool'))

They sit in the same family as the detection variants because what they add is a field, not a different question. Two behaviours are Ultralytics' own, and mozo reproduces them rather than tidying them away:

Class ids are contiguous

The YOLO families number COCO's classes 0 to 79, so person is 0. RF-DETR uses COCO's original ids, where person is 1. Mind this when you filter by id, for example before handing people to ViTPose. Class names are read from the checkpoint, so a fine-tuned YOLO26 brings its own vocabulary.

No CoreML

YOLO26 shares YOLO11's C2PSA block, which makes Apple's Metal graph compiler abort the process. The configuration that avoids the crash is slower than torch on mps, so publishing it would make auto pick the slower option on a Mac. The seg- variants share the backbone and inherit the same limit.

Every variant publishes ONNX. A seg- graph has two outputs, the predictions and the prototypes their mask coefficients refer to; a detection graph has one.

Weights and licence

The weights are Ultralytics' ultralytics/assets release v8.4.0, redistributed unmodified. They are AGPL-3.0, or covered by a commercial licence from Ultralytics.

Mozo's own code is Apache-2.0, and so is its YOLO26 inference: it was written independently against the checkpoint format, imports nothing from ultralytics, and was checked against ultralytics 8.4.0. The code and the weights are separate works that travel together. But anything you export from the weights inherits their terms, and serving predictions from them over a network places AGPL-3.0 section 13 obligations on you. Complying is the operator's responsibility.

Every variant ships with the licence and a NOTICE naming the release it came from. To run a server that never offers AGPL weights, leave the YOLO families out of MOZO_ENABLE. The details are in mozo/vendors/yolov26_deploy/PROVENANCE.md.