Eval: YOLO26 as primary detection/pose backend #1
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Source
Paper: https://arxiv.org/abs/2606.03748 — Ultralytics YOLO26 (June 2026)
Code/weights: https://github.com/ultralytics/ultralytics
What it is
Unified real-time vision model covering detection, instance segmentation, pose
estimation, oriented detection, and classification in a single pipeline. NMS-free
end-to-end inference. 40.9–57.5 mAP on COCO at 1.7–11.8ms T4 TensorRT latency.
YOLOE-26 variant: open-vocabulary (zero-shot, text-prompted) detection. No
retraining required for new categories — "find all food items" works out of the box.
Export targets: TensorRT, ONNX, CoreML, TFLite, OpenVINO, NCNN, ExecuTorch.
cf-vision integration
YOLO26 is a strong candidate for the primary backend in cf-vision, covering the
needs of all current planned consumers:
License constraint (CRITICAL)
Code/weights: AGPL-3.0 or Ultralytics commercial license.
without Ultralytics Enterprise license OR inference-only wrapper around raw weights.
cf-vision's backend abstraction must accommodate a swap to a non-AGPL runtime for
cloud tier (e.g., bare ONNX weights + custom inference, no Ultralytics training code).
The interface should be identical; only the backend differs between free and cloud.
Recommended eval steps
ultralyticsin cf conda env, run YOLO26n on sample Kiwi imagesRelated