Ultralytics YOLO27
YOLO27 models are undergoing final R&D, with a launch anticipated later this year. The models are not yet available, and no launch date has been set. This page previews the upcoming models; features and benchmarks may change before release. Code examples below are intended for use once the models and package support are released and will not work with the current public package. Model weights, configurations, and implementation code are not being released at this time. Join the YOLO27 waitlist to be the first to hear when it launches.
Overview#
Ultralytics YOLO27 is a family of real-time vision models whose detection models
use two complementary designs: a streamlined CNN architecture for the compact N and S models, and a query-based,
NMS-free architecture for the larger M and L models. Both designs deploy through the same interface.
N and S detection models default to the one-to-many head with NMS; use nms=False to select their NMS-free head.
YOLO27 is the upcoming model family in the Ultralytics YOLO series, succeeding YOLO26. It comes in four sizes — N, S, M and L — and supports object detection, instance segmentation, semantic segmentation, depth estimation, classification, pose estimation and oriented object detection. The two-design split applies to detection, instance segmentation, and pose estimation. Semantic segmentation, depth estimation, classification, and oriented object detection use the CNN architecture.
Across its four detection scales, YOLO27 reaches 42.6-60.5 mAP on COCO at 0.44-1.86 ms latency on an NVIDIA RTX PRO 6000 — and up to 61.4 mAP with YOLO27l at a larger 800-pixel input. YOLO27l is the first Ultralytics model to surpass 60 mAP on COCO, while the compact YOLO27n/s improve on YOLO26n/s accuracy at essentially the same speed.
from ultralytics import YOLO
model = YOLO("yolo27n.pt") # load a pretrained YOLO27n model
results = model("path/to/bus.jpg") # run inferenceKey Features#
-
Dual-scale detection Standard detectors predict objects on three feature maps — fine, medium, and coarse. YOLO27 N and S drop the medium one and predict only on a fine map (for small objects) and a coarse map (for large objects), with a fixed scaling on the fused features keeping the two scales balanced. This removes a substantial share of detection-head computation, making the models faster while training as reliably as the full three-scale design.
-
Stronger small-object detection The early, high-resolution feature stage is widened so it can capture more fine-grained detail. Combined with the surviving fine prediction map, this improves localization and regression for small objects — the hardest category for compact models.
-
Foreground alignment supervision During training, an extra lightweight branch learns to tell "object" from "background" at every location. It is designed to close the gap between the denser one-to-many supervision used during training and the one-to-one head that produces the final predictions — cutting that accuracy gap from 0.9/0.8 mAP on YOLO26n/s to just 0.4 mAP on YOLO27n/s, so the deployed one-to-one head keeps nearly all of the training-time accuracy. The branch is used only during training and is removed for inference and export, so it costs nothing at deployment.
-
Query-based detection without NMS The larger models replace dense prediction with a transformer decoder that refines a fixed set of object queries and directly outputs the final detections — no non-maximum suppression post-processing needed. YOLO27m and YOLO27l pair this decoder with an UltraViT backbone that uses self-attention in its deepest stage to capture global context, followed by an FPN/PAN neck.
-
One simple interface Both architectures are used through the same
YOLOPython interface. The right training, validation, prediction, and export pipeline is selected automatically from the model, so code written for one YOLO27 scale works unchanged for the others.
Which YOLO27 Should I Use?#
The following guidance is for choosing a model once YOLO27 is released. For projects today, use YOLO26.
- YOLO27n / YOLO27s — edge devices, drones, and real-time video: the fastest models in the family, with improved small-object detection from the dual-scale design. See NVIDIA Jetson and Raspberry Pi for device-specific deployment.
- YOLO27m — the accuracy-speed sweet spot on GPUs: improves on YOLO26m accuracy at comparable latency, making it the default choice for production GPU deployment.
- YOLO27l — accuracy-critical applications: the first Ultralytics model above 60 mAP on COCO, reaching 61.4 mAP at a larger input size while staying real-time on GPU.
To compare against other families, see all Ultralytics models. To measure the accuracy-speed trade-off on your own hardware rather than ours, see Benchmark mode.
Supported Tasks and Modes#
The following table previews planned task and mode support across the four YOLO27 model scales. Checkmarks indicate intended support at release, not current public availability; all listed model files are unreleased.
| Model | Filenames | Task | Training | Validation | Inference | Export |
|---|---|---|---|---|---|---|
| YOLO27 | yolo27n.pt yolo27s.pt yolo27m.pt yolo27l.pt | Detection | ✅ | ✅ | ✅ | ✅ |
| YOLO27-seg | yolo27n-seg.pt yolo27s-seg.pt yolo27m-seg.pt yolo27l-seg.pt | Instance Segmentation | ✅ | ✅ | ✅ | ✅ |
| YOLO27-sem | yolo27n-sem.pt yolo27s-sem.pt yolo27m-sem.pt yolo27l-sem.pt | Semantic Segmentation | ✅ | ✅ | ✅ | ✅ |
| YOLO27-depth | yolo27n-depth.pt yolo27s-depth.pt yolo27m-depth.pt yolo27l-depth.pt | Depth Estimation | ✅ | ✅ | ✅ | ✅ |
| YOLO27-cls | yolo27n-cls.pt yolo27s-cls.pt yolo27m-cls.pt yolo27l-cls.pt | Classification | ✅ | ✅ | ✅ | ✅ |
| YOLO27-pose | yolo27n-pose.pt yolo27s-pose.pt yolo27m-pose.pt yolo27l-pose.pt | Pose/Keypoints | ✅ | ✅ | ✅ | ✅ |
| YOLO27-obb | yolo27n-obb.pt yolo27s-obb.pt yolo27m-obb.pt yolo27l-obb.pt | Oriented Detection | ✅ | ✅ | ✅ | ✅ |
YOLO27 Detect, Segment, Pose, and OBB models will also work with Track mode, which runs on top of predict for multi-object tracking across video frames.
YOLO27 detection, instance segmentation, and pose estimation use two designs under one interface: the N and S scales use the CNN architecture, while the M and L scales use the query-based NMS-free architecture. Semantic segmentation, depth estimation, classification, and oriented object detection use the CNN architecture.
Performance Metrics#
Detection accuracy is reported on the COCO validation set. See YOLO Performance Metrics for explanations of mAP, precision, and recall. For accuracy beyond COCO, see
Ultralytics Benchmark, which measures macro mAP50-95 across 37
real-world detection datasets spanning medical imaging, remote sensing, industrial, retail, and more. Inference speed is measured on an NVIDIA RTX PRO 6000
(TensorRT 11, FP16) for GPU and an AMD EPYC 9655 (ONNX Runtime, FP32) for CPU. After release, accuracy numbers can be reproduced
with yolo val model=yolo27n.pt data=coco.yaml imgsz=640 nms=False save_json=True.
The detection, instance segmentation, and pose tables use the NMS-free head and COCO evaluation. N/S pose
validation uses rectangular batches (rect=True).
These research results may change during final R&D. Public weights and reproduction instructions will accompany the release.
See Detection Docs for usage examples with these models trained on COCO, which include 80 pretrained classes. The table uses a 640-pixel input; the overview also reports YOLO27l at 800 pixels.
| Model | size (pixels) | mAPval50-95 | Speed CPU ONNX (ms) | Speed RTX PRO 6000 TensorRT11 (ms) | params (M) | FLOPs (B) |
|---|---|---|---|---|---|---|
| YOLO27n | 640 | 42.6 | 16.1 ± 1.6 | 0.44 ± 0.00 | 3.0 | 7.2 |
| YOLO27s | 640 | 50.1 | 33.2 ± 0.1 | 0.64 ± 0.00 | 11.8 | 28.2 |
| YOLO27m | 640 | 56.4 | 74.8 ± 0.5 | 1.01 ± 0.00 | 24.6 | 64.6 |
| YOLO27l | 640 | 60.5 | 149.6 ± 1.4 | 1.86 ± 0.00 | 72.3 | 166.7 |
Params and FLOPs values are for the fused model after Conv/BatchNorm folding and removal of the unused detection branch. Detection, instance segmentation, and pose measurements select the NMS-free head with nms=False; N/S accuracy depends on the selected head. FLOPs include decoder attention matrix multiplications. Pretrained checkpoints retain the full training architecture and may show higher counts.
Usage Examples#
This section provides simple YOLO27 training and inference examples. For custom datasets, see Tips for Best Training Results and the Hyperparameter Tuning Guide.
The example below is for YOLO27 Detect models for object detection.
PyTorch pretrained *.pt models as well as configuration
*.yaml files can be passed to the YOLO() class to create a model instance in Python:
from ultralytics import YOLO
# Load a COCO-pretrained YOLO27n model
model = YOLO("yolo27n.pt")
# Run inference with the YOLO27n model on the 'bus.jpg' image
results = model("path/to/bus.jpg")
# Train the model on the COCO8 example dataset for 100 epochs
results = model.train(data="coco8.yaml", epochs=100, imgsz=640)FAQ#
- Dual-scale detection (N/S): drops the medium prediction map for a faster head with competitive accuracy
- Stronger small-object detection (N/S): a widened early feature stage improves small-object localization
- Foreground alignment supervision (N/S): cuts the one-to-many vs one-to-one accuracy gap from 0.9/0.8 mAP on YOLO26n/s to 0.4 mAP on YOLO27n/s, at zero inference cost
- Query-based NMS-free detection (M/L): a transformer decoder outputs final detections directly
- One simple interface: both architectures run through the same
YOLOclass
Not yet — YOLO27 is unreleased. Continue using YOLO26 for current projects. Preliminary results show improved accuracy across model sizes, with YOLO27l surpassing 60 mAP on COCO. Evaluate the final released models for your workload before migrating.
After release, YOLO27 is intended to use the same
YOLOclass and the same train/val/predict/export API as YOLO26 — the correct pipeline (CNN or query-based) is selected automatically from the model. Swappingyolo26n.ptforyolo27n.ptis the intended model-selection change once YOLO27 support and weights are available.Most detectors predict on three feature maps at different resolutions. YOLO27 N and S keep the fine map that small objects depend on and the coarse map that large objects need, and skip the medium one. This cuts a significant share of detection-head computation, and the training improvements above keep the accuracy-latency tradeoff competitive.
YOLO27l is the first Ultralytics model to surpass 60 mAP on COCO, reaching 60.5 mAP at a 640-pixel input (1.9 ms on an NVIDIA RTX PRO 6000) and 61.4 mAP at an 800-pixel input (2.4 ms). It combines the UltraViT backbone, multi-scale feature fusion, and a query-based detector that produces final detections directly, without NMS.
YOLO27 is undergoing final R&D, with a launch anticipated later this year. No launch date has been set. Model weights and implementation code are not publicly available yet.
Once YOLO27 is released, see Quickstart to install or update the
ultralyticspackage, then load a model as shown below. This example is for use after release:from ultralytics import YOLO # Load a pretrained YOLO27 nano model model = YOLO("yolo27n.pt") # Run inference on an image results = model("image.jpg")See Usage Examples for training and inference examples, or the Val and Export guides for those modes.
Comments9
Ask a question, share your results, or help someone else.
sergshadrap
Guys! You are doing incredible job , The thing I'd asked for is the total size for running model. When we speak about small devices embedded solutions that the -n model is intended to the size is very limited by the SoC properties and that is though to predict if it fits to the board or not. I think pointing the size is also important along the performance metrics for tiny models. Thanks again!
Paula DerrengerUltralyticsThanks from the Ultralytics team and YOLO community—good suggestion. The preview lists
YOLO27nat 3.0M parameters, but actual storage and runtime memory depend on the export format, precision, input size, and backend; exact measurements cannot be published until the models are released. We’ll consider adding artifact-size and memory benchmarks to the YOLO27 documentation, and please keep sharing embedded-device requirements here for team visibility.sergshadrap
Thanks for you! Definitely nobody will ask about exact sizes of the models. What I meant is that most of the camera's SoCs ( for instance) we can split for three major segments, where the middle one is about Arm 1Ggz , 16m flash, and 128m Ram, the high is everything that has more advanced scu with multicores ,spaced flash and Ram and definitely folds more expensive and the low that everything below that. Trying to fit yolo26 to the gk7205v300 that exactly the middle one was a challenge even quantitized to 8. So ... what about the v27? Does it belong to the high-end only or I can try it for the middle one?
Paula DerrengerUltralyticsYOLO27nis intended for edge devices, so it is not high-end-only; its preliminary 3.0M parameters suggest INT8 weights around 3 MB, but 128 MB RAM may still be the limiting factor because activations and backend buffers depend on input size and runtime. For the GK7205V300, consider it a plausible target—not a confirmed fit—until the released model can be exported, profiled at reducedimgsz, and benchmarked on-device;YOLO27m/lare unlikely choices for those constraints. Please keep sharing your embedded results in this discussion so the Ultralytics team can track them alongside the YOLO27 documentation.
Mohammed YasinUltralytics@sergshadrap How's the performance of YOLO26 on such SoCs? Because if it's too big to fit the SoC, then isn't it also too heavy to run? You can always reduce the size of the YOLO models by modifying the YAML file and removing some layers or reducing channels.
sergshadrap
Yeah , that is quite heavy stuff for 1 core 0.9 Ghz SoC , but I have it run . The most stable and sensible (for object recognition) configuration turns to be fp16 288x384 nano , that goes about 0.8 fps in continues run . That's pretty slow , but enough for my current cascade version, where IVE hardware detector is catching "something" and yolo refine the output. Would be glad to get a hint - how to reduce size and reduce layers/ channels. Now I'm on ncnn export tools , so it seems there is no fp8 variant for that tool? Forth to mention I'm on OpenIpc firmware and the majestic additionally quite a leaky guy , so with 128M of memory for all we're on the floor..
Mohammed YasinUltralytics(edited)You can create a copy of this YAML and reduce the float values. Lowering width (the second float value) brings the biggest drop in model file size. Of course, all of these also reduces accuracy. The modified YAML can be loaded and used with
model = YOLO("path/to/yaml")The ending suffix letter like
ndetermines which of the scale values are used from this YAML.sergshadrap
If only I change the model , do I need to re-train the model completely or I could move the weights from existing with some algorithm?
Mohammed YasinUltralyticsYou have to retrain since model structure changes when you do this