EdgeFirst/yolo11-seg

YOLO11 Segmentation — EdgeFirst Model Zoo

YOLO11 Segmentation models trained on COCO 2017 (80 classes) and validated on real edge hardware through the EdgeFirst Profiler + Validator pipeline. Each row in the tables below cites the EdgeFirst Studio validation session (v-XXXX) that produced the measurement.

Part of the EdgeFirst Model Zoo.

Training experiment: View on EdgeFirst Studio — dataset, training configuration, metrics, and exported artifacts.

Architecture with C3k2 attention blocks.

---

Reference accuracy — ONNX FP32

Accuracy ceiling for each size, measured against COCO val2017 (5,000 images) with pycocotools. Quantized and compiled artifacts (TFLite INT8, HEF, etc.) are graded against this reference per the EdgeFirst publication rule.

Size	Params	GFLOPs	Box mAP@0.5	Box mAP@0.5-0.95	Mask mAP@0.5	Mask mAP@0.5-0.95	Source
Nano	2.6M	6.5	52.00%	37.22%	47.88%	28.75%	v-1d44
Small	9.4M	21.5	60.60%	44.56%	55.46%	33.33%	v-1d49
Medium	20.1M	68.0	65.91%	49.59%	60.54%	36.61%	v-1d4c
Large	25.3M	87.6	—	—	—	—	—
XLarge	56.9M	195.0	—	—	—	—	—

---

On-target validation results

Each row is one EdgeFirst Studio validation session. Click the Source link to inspect the full session — model artifact, dataset version, parameters, per-stage Perfetto trace, and the host hardware description (hostname, kernel version, SoC, NPU, profiler version).

Two row conventions in the table below:

• Rows without a number under the metric columns are validation sessions that are currently work in progress — typically a larger size that has not yet been profiled on a given NPU, or a session that has not yet been linked to an ONNX FP32 reference. The Studio Source link tracks the current status.
• Rows whose Δ vs FP32 cell carries a ⚠ are published with a caveat: the quantization or runtime regression on that platform exceeds the 10 percentage-point publication threshold we grade every measurement against. The numbers are still measured on real hardware and reproducible from the linked Studio session — they are shown for transparency rather than suppressed. We are actively investigating these regressions in collaboration with the toolchain vendor and working to close the gap; the note immediately under the table summarises the current state.

Size	Platform	Box mAP@0.5	Mask mAP@0.5-0.95	Δ mask vs FP32 (pp)	Inference (ms)	FPS (median)	Source
Nano	NXP i.MX 8M Plus + VeriSilicon NPU	48.22%	26.08%	-2.67	105.78	7.6	v-1d5f
Nano	NXP i.MX 95 + eIQ Neutron NPU	10.82%	4.03%	-24.72 ⚠	43.21	19.0	v-1d5e
Nano	Raspberry Pi 5 + Hailo-8L NPU	50.35%	27.64%	-1.11	28.52	33.6	v-1d5c
Small	Raspberry Pi 5 + Hailo-8L NPU	58.66%	32.39%	-0.94	40.49	24.0	v-1d5d
Medium	Raspberry Pi 5 + Hailo-8L NPU	63.95%	35.52%	-1.09	83.81	11.8	v-1d60

⚠ Investigations in progress. The rows marked ⚠ above show a drop of more than 10 percentage points against the same training session's ONNX FP32 reference. We publish them as-is so the current state of every (model, platform) pair is visible; we are working with the toolchain vendor to close each regression, and the numbers will improve as fixes land. The next snapshot of this card will reflect any recovered accuracy.

---

Validation pipeline

These results are produced by the EdgeFirst on-target validation pipeline:

1. EdgeFirst Profiler runs on the target hardware, executes the full inference pipeline (preprocess → inference → postprocess), and emits per-image predictions in EdgeFirst Arrow/Parquet plus a Perfetto trace.
2. EdgeFirst Validator consumes the predictions and trace, computes pycocotools accuracy metrics and per-stage timing summaries, and publishes the results to the Studio validation session.
3. EdgeFirst HAL (open source) provides the hardware-accelerated preprocessing and post-decoding primitives used at both validation and deployment time, so the timings measured here reflect the same accelerated paths a production runtime would take.

Inference latency is reported as the on-accelerator inference time. FPS is the measured end-to-end pipelined throughput from the Perfetto trace, which generally exceeds 1000 / (preprocess + inference + postprocess) because the runtime overlaps stages across frames.

See EdgeFirst Studio for the full validation pipeline.

---

Downloads

Artifacts are organized by deployment target. Each model file embeds the EdgeFirst edgefirst.json metadata (training session, dataset version, calibration artifact, converter chain) so a single file is sufficient for deployment — no sidecar configuration required.

Per-artifact download links are populated from the Studio artifact registry. To see the live download table, regenerate this card with --studio against an authenticated Studio session.

---

Inference example (Python)

from edgefirst.hal import Model, TensorImage

# Load the model — embedded edgefirst.json carries labels and decoder config
model = Model("yolo11n-seg-int8.tflite")

# Run inference on an image
image = TensorImage.from_file("image.jpg")
results = model.predict(image)

# Iterate detections
for det in results.detections:
    print(f"{det.label}: {det.confidence:.2f} at {det.bbox}")

EdgeFirst HAL — Hardware abstraction layer with accelerated inference delegates.

---

Traceability

Every measurement in the tables above is reachable through the EdgeFirst Studio validation framework. The v-XXXX Source link on each row resolves to a public Studio URL of the form:

https://test.edgefirst.studio/public/validation/v-XXXX/details

From there, the full provenance chain is one click deeper: training session ID, dataset version, calibration artifact, converter chain (e.g. TFLite quantizer + Neutron compile), validation parameters, and the host hardware description (hostname, kernel version, SoC, NPU, profiler version). The same model file you download from this repository embeds the same chain in its edgefirst.json metadata.

---

See also

Other model families in the EdgeFirst Model Zoo:

Model	Task	Link
YOLOv5 Detection	Detection	EdgeFirst/yolov5-det
YOLOv8 Detection	Detection	EdgeFirst/yolov8-det
YOLOv8 Segmentation	Segmentation	EdgeFirst/yolov8-seg
YOLO11 Detection	Detection	EdgeFirst/yolo11-det
YOLO26 Detection	Detection	EdgeFirst/yolo26-det
YOLO26 Segmentation	Segmentation	EdgeFirst/yolo26-seg

---

Train your own with EdgeFirst Studio

Train on your own dataset with EdgeFirst Studio:

• Free tier includes YOLO training with automatic INT8 quantization and edge deployment.
• Upload datasets via EdgeFirst Recorder or COCO/YOLO format.
• AI-assisted annotation with auto-labeling.
• CameraAdaptor integration for native sensor format training.
• Deploy trained models to edge devices via EdgeFirst Client.

---

Technical notes

Quantization pipeline

All TFLite INT8 models are produced by EdgeFirst's quantization pipeline (details):

1. ONNX export — standard Ultralytics export with simplify=True
2. TF-wrapped ONNX — box coordinates normalized to [0, 1] inside DFL decode
3. Split decoder — boxes, scores, and mask coefficients split into separate output tensors so each receives an independent INT8 quantization scale
4. Smart calibration — calibration samples selected via greedy coverage maximization; the artifact is content-addressed by parameter hash and cached in Studio for deterministic reuse
5. Full integer INT8 — uint8 input, int8 output, MLIR quantizer

Split decoder output format

Segmentation (e.g. yolo11n-seg):

• boxes — (1, 4, 8400) normalized [0, 1] coordinates
• scores — (1, 80, 8400) per-class probabilities
• mask_coefs — (1, 32, 8400) per-anchor mask coefficients
• protos — (1, 160, 160, 32) prototype masks

Each tensor has its own quantization scale and zero point. The EdgeFirst HAL handles dequantization and reassembly automatically; no application code change is required across NPU targets.

Embedded metadata

• TFLite: edgefirst.json and labels.txt embedded in the ZIP-format model file
• ONNX: edgefirst.json embedded in model.metadata_props

No sidecar files required; the model artifact is self-contained.

---

Limitations

• COCO bias — models trained on COCO (80 classes) inherit the dataset's biases (Western-centric scenes, particular object distributions, limited weather/lighting diversity).
• INT8 quantization loss — full-integer quantization introduces accuracy loss relative to FP32; the magnitude per platform is shown in the Δ vs FP32 column above.
• Input resolution — all models expect 640×640 input; other resolutions require letterboxing.

---

Citation

@software{edgefirst_yolo11_seg,
  title = { {YOLO11 Segmentation — EdgeFirst Model Zoo} },
  author = {Au-Zone Technologies},
  url = {https://huggingface.co/EdgeFirst/yolo11-seg},
  year = {2026},
  license = {Apache-2.0},
}

---

_{EdgeFirst Studio · GitHub · Docs · Au-Zone Technologies
Apache 2.0 · © Au-Zone Technologies Inc.}