NEW
Also known as: You Only Look Once
A family of single-stage, real-time object detectors that directly regress bounding boxes and class probabilities from images.
DESCRIPTION
YOLO reframes detection as a single regression task, enabling fast, end-to-end inference. Evolving variants (YOLOv1–v8/YOLO-NAS) improve accuracy, anchors, and architectures. Widely used in embedded and cloud scenarios for surveillance, retail, and robotics, YOLO balances speed and precision with techniques like multi-scale training and NMS. Implementations by Ultralytics and others provide production-ready pipelines.
ALTERNATIVE DEFINITIONS
Joseph Redmon et al.
We reframe object detection as a single regression problem, straight from image pixels to bounding box coordinates and class probabilities.
Defines YOLO’s core formulation as unified regression for detection.
Ultralytics
YOLO (You Only Look Once) is a family of real-time object detection architectures and models.
Emphasizes real-time family of architectures and practical usage.
Papers with Code
YOLO is a unified, real-time object detection system.
Concise characterization as unified and real-time.
RELATED TERMS
Object Detection Bounding Box Non-Maximum Suppression Single-Stage Detector Anchor Boxes mAP Real-time Inference Ultralytics
COMPETING TERMS
KNOWLEDGE AREAS
AI Data Science MLOps Infrastructure
TARGET AUDIENCE
AI Engineer MLOps Engineer Data Scientist Software Developer
EXTERNAL SOURCES
- Wikipedia - You Only Look Once
- arXiv - Original YOLO paper
- Ultralytics - YOLO implementation and usage docs
- Darknet - Original YOLO framework site
TOP QUESTIONS
Why is YOLO popular for real-time applications?
Its single-stage architecture enables high FPS with competitive accuracy, ideal for edge devices and latency-sensitive tasks.
Category: Relevancy
How does YOLO differ from two-stage detectors like Faster R-CNN?
YOLO directly regresses boxes and classes in one pass, while two-stage methods generate proposals first, often trading speed for accuracy.
Category: Comparison
What are common YOLO pitfalls?
Poor anchor configuration, insufficient augmentation, and class imbalance can degrade performance. Proper training schedules and data quality are crucial.
Category: Mistakes
How is YOLO evaluated?
Using mean Average Precision (mAP) across IoU thresholds, as well as latency and throughput for deployment scenarios.
Category: Testing
Which YOLO version should I choose?
Use recent Ultralytics releases for strong defaults and tooling. Choose model sizes based on latency and accuracy needs.
Category: Guidance
What is the biggest misunderstanding about YOLO?
That it is always less accurate than two-stage detectors; modern variants can be highly competitive on accuracy while maintaining speed.
Category: Misunderstanding
How do anchors affect YOLO performance?
Anchors guide initial box predictions; good priors improve convergence and localization. Auto-anchor utilities can optimize them.
Category: Concept
What deployment risks exist with YOLO?
Domain shift and poor lighting degrade detection. Continuous monitoring and model updates mitigate performance drift.
Category: Risks
Where to start learning YOLO?
Begin with Ultralytics tutorials and the original paper, then practice on COCO with transfer learning.
Category: Learning