Top
Best
New

Posted by teleforce 22 hours ago

An Introduction to YOLO26(blog.roboflow.com)
98 points | 32 comments
yeldarb 12 hours ago|
It’s a big improvement if you’re already paying them but, given their aggressive approach to licensing, I can’t imagine why anyone would choose to use an Ultralytics model on a new project in 2026. You’re just asking to be shaken down and have to pay off a large bill down the line.

RF-DETR is both faster and more accurate and truly open source with an Apache 2.0 license: https://github.com/roboflow/rf-detr

Full disclosure: I’m one of the co-founders of Roboflow (we made RF-DETR, wrote this blog post, and are a sub-licensor of Ultralytics’ models.)

MrGLaDOS 11 hours ago||
“RF-DETR is both faster and more accurate and truly open source with an Apache 2.0 license”

Misleading marketing statement.

The catch is that for image resolutions >=700x700pixels (most production usecases), the roboflow license is actually PML1.0 instead of Apache2.0 https://github.com/roboflow/rf-detr#license

krapht 11 hours ago||
> The catch is that for image resolutions >=700x700pixels (most production usecases)

Citation needed? 2XL looks like you go up to 800x800 pixel inputs. This isn't the dealbreaker you say it is - all pipelines benefit from thoughtful crop and rescaling before going to inference.

MrGLaDOS 9 hours ago||
See the url in my comment (search for the term rfdetr-2xlarge). 2XL does indeed go up to 800x800 and has PML1.0 license instead of apache 2.0.

Rescaling is fine for some purposes but but not for all. For many domain-specific (often less common and odd dimensioned) objects, downscaling will severely reduce recall. There is a reason that Roboflow slaps a license that is not open source on those specific architectures.

In some cases tiled inferencing (for example with https://github.com/obss/sahi ) might do the job.

pzo 15 hours ago||
FWIW there are today many more alternatives with better license. Here is a good meta repo for object detection with different model variants:

https://github.com/LibreYOLO/libreyolo

esquire_900 19 hours ago||
We've been running YOLO for a number of years (since v5) on soccer videos. None of the recent iterations have been significantly better, with v26 scoring worse then v9 and v11 on our tasks. Makes me wonder why this version is being pushed by roboflow and ultralytics.
teruakohatu 19 hours ago||
When I was working with YOLO models it did seem like there was little practical improvements were between all of the spinoff models. It seemed people were pushing new models for personal recognition since the original creator stopped working on it.

That said, many of the claimed improvements in this model were are efficiency related.

yfontana 16 hours ago|||
Can't speak for 26, but a year ago I worked on a project that migrated from v5 to 11 because of improved image segmentation capabilities. My understanding is that the newer versions don't necessarily have better precision/recall, but they tend to be faster for equivalent results, and have increased capabilities.
GL26 16 hours ago|||
What I find cool is not the model in itself, but the architectures / training methods found that make the model better. It gives out a new possibilites for other fields of AI. (Notably if you want to fine tune other CV models)
Onavo 19 hours ago||
The original YOLO author has long quit due to ethical reasons.
utopiah 18 hours ago||
Despite having a very memorable paper on the topic I believe they now work at Ai2.
deviation 12 hours ago||
My buddy has some vision impairments, and I remember training a much older of YOLO's models to detect objects/enemies in Terraria for him. It worked very well.

I then tried trained it on a lot of sample images from a 3D point & shoot game, and was quite disappointed in how it performed.

Has anyone else experimented with it recently? How does this suit as a base-model for training custom classifiers? And with hardware growth in the last ~5 years, is it suitable to run in parallel with games which are graphically intensive?

geuis 17 hours ago||
Was evaluating YOLO26 within the last month for its on-device (iPhone 16 Pro) segmentation capabilities. Its decent, but its biggest limitation is that its only trained on 80 COCO classes (meaning pre-labeled images). If whatever is in your images isn't in the 80 classes, its invisible to YOLO26. Conversely I have SAM2 running on-device and its my current workhorse. The biggest benefit with SAM2 for me is that it does fine-grained segmentation masks but isn't trained on labeled images. This was a specific requirement for the app I'm building. SAM2 isn't anywhere as speedy as the native Vision framework apis, but it is more capable across a vastly wider array of potential image targets.
larodi 17 hours ago|
I would prefer GroundingDINo which is a sort of SAM and Dino combo which does open vocabulary.
geuis 14 hours ago||
Doesn't work for my use-case. GroundingDINO is a text to bounding box model. SAM2 supports coordinate based masks (user taps or clicks somewhere in an image), which is what my research app needs.
pritambarhate 17 hours ago||
Is the license for this AGPL? Can someone please confirm?
trevorhlynn 12 hours ago|
Yes AGPL-3.0
speedgoose 19 hours ago||
I found that while CLIPSeg is slower than YOLOn, it is still pretty fast and if gave me much much better results without training.

If you want to detect objects and speed is important so you can’t use a LLM architecture, you can give it a try too.

Alles 17 hours ago||
Reminder that Ultralytics is pushing AGPL in a very overreaching way with their models that's why they are not available in Frigate

https://github.com/blakeblackshear/frigate/pull/10717

yurimo 18 hours ago||
Wow I'm old, I still remember working with YOLOv2.
larodi 17 hours ago|
One thing I don’t get I why the article is credited to ‘Contributing Author’.

Meanwhile their very own Peter Skalski already does super job with host write ups and examples of all YOLO sorts and is well respected.

More comments...