# yolo26 seg merge depth detect

**URL:** <https://community.ultralytics.com/t/yolo26-seg-merge-depth-detect/2200>\
**Category:** Discussion\
**Tags:** code, releases, yolo, support\
**Created:** [September 1, 2026, 6:59am UTC](https://community.ultralytics.com/t/yolo26-seg-merge-depth-detect/2200 "2026-09-01T06:59:08Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![korol](https://sea1.discourse-cdn.com/flex001/user_avatar/community.ultralytics.com/korol/32/1681_2.png) [@korol](https://community.ultralytics.com/u/korol)\
**Post date:** [September 1, 2026, 6:59am UTC](https://community.ultralytics.com/t/yolo26-seg-merge-depth-detect/2200/1 "2026-09-01T06:59:08Z")

</div>

I recently combined YOLO26’s segmentation detection with depth detection, using the same backbone network for both and splitting it into two different task heads. A single inference outputs both segmentation and depth information, with the depth calculation referencing the segmentation info. Here’s the GitHub link, feel free to check it out: [GitHub - koroandiven/yolo26-seg-depth: yolo26-seg with depth · GitHub](https://github.com/koroandiven/yolo26-seg-depth/tree/depth_merge_seg)

---

<div class="post-metadata">

**Author:** ![pderrenger](https://sea1.discourse-cdn.com/flex001/user_avatar/community.ultralytics.com/pderrenger/32/73_2.png) [@pderrenger](https://community.ultralytics.com/u/pderrenger)\
**Post date:** [September 2, 2026, 1:01am UTC](https://community.ultralytics.com/t/yolo26-seg-merge-depth-detect/2200/2 "2026-09-02T01:01:05Z")

</div>

Thanks for sharing this community experiment. The shared backbone with a frozen segmentation path and mask-guided depth decoder is an interesting multitask extension.

It would be helpful to add the exact Ultralytics version or commit used, downloadable weights, and latency/accuracy comparisons against separate `yolo26-seg` and `yolo26-depth` inference. That would make the results in the [`depth_merge_seg` branch](https://github.com/koroandiven/yolo26-seg-depth/tree/depth_merge_seg) easier for others to reproduce and evaluate.

---

<div class="post-metadata">

**Author:** ![korol](https://sea1.discourse-cdn.com/flex001/user_avatar/community.ultralytics.com/korol/32/1681_2.png) [@korol](https://community.ultralytics.com/u/korol)\
**Post date:** [September 9, 2026, 3:24am UTC](https://community.ultralytics.com/t/yolo26-seg-merge-depth-detect/2200/3 "2026-09-09T03:24:24Z")

</div>

the weight is opensource too

---

<div class="post-metadata">

**Author:** ![pderrenger](https://sea1.discourse-cdn.com/flex001/user_avatar/community.ultralytics.com/pderrenger/32/73_2.png) [@pderrenger](https://community.ultralytics.com/u/pderrenger)\
**Post date:** [September 10, 2026, 12:59am UTC](https://community.ultralytics.com/t/yolo26-seg-merge-depth-detect/2200/4 "2026-09-10T00:59:07Z")

</div>

Thanks for clarifying—you’re right. I confirmed that the repository includes open-source `best.pt` and `last.pt` files in the [exp16 weights directory](https://github.com/koroandiven/yolo26-seg-depth/tree/depth_merge_seg/runs/segment/runs/train_depth/yolo26-seg-depth-exp16/weights). Adding a direct link to the recommended checkpoint in the README would make it easier for users to find and reproduce your results.