Verdict

On an RTX 5070 Ti in PyTorch, DEIM averages 4.3 mAP points higher than RT-DETR at matched parameter counts, winning all 3 nearest-params pairings. RT-DETR is 41.6% faster on average. DEIM leads accuracy across the range; RT-DETR wins on throughput.

DEIM fields 5 measured variants and RT-DETR fields 7, all on the same COCO val2017 protocol on an RTX 5070 Ti. Three pair closely by parameter count, giving 3 matched comparisons.

ModelFamilyParams (M)mAP@50-95FPS
DEIM-NDEIM3.84679.037.0
DEIM-SDEIM10.35210.033.4
DEIM-MDEIM19.65549.028.4
RT-DETR-R18RT-DETR20.24979.047.2
DEIM-LDEIM31.25783.018.6
RT-DETR-R34RT-DETR31.45223.040.2
RT-DETR-LRT-DETR32.95577.027.7
RT-DETR-R50mRT-DETR36.65382.035.3
RT-DETR-R50RT-DETR42.95588.029.8
DEIM-XDEIM62.65961.015.0
RT-DETR-XRT-DETR67.45794.021.8
RT-DETR-R101RT-DETR76.65677.023.6
DEIM and RT-DETR variant ladders interleaved by parameter count on NVIDIA RTX 5070 Ti, PyTorch FP32, batch 1. mAP in percent form. The family column shows where each frontier sits at every size.
Live chartverified data
Accuracy vs parameters on COCO val2017, DEIM and RT-DETR variants highlighted against the full field.

Accuracy at matched compute

mAP is shown in percent. Each DEIM variant is paired with the nearest RT-DETR variant by parameter count. Across the 3 pairings DEIM averages 4.3 mAP points higher and wins all three. DEIM-X reaches 59.6 mAP at the top; RT-DETR-R101 reaches 56.8. At the small end DEIM-N is a 3.78M model at 46.8 mAP, against RT-DETR-R18 at 20.18M and 49.8 mAP.

Speed

Averaged across the matched pairs, RT-DETR is 41.6% faster than DEIM in PyTorch. The gap is widest at the DEIM-L pairing and narrowest at the flagship pairing.

Licensing
DEIM license
Apache-2.0
RT-DETR license
Apache-2.0
Both families
permissive, cleared for commercial use

Which family to pick

Pick DEIM for accuracy per parameter: it wins every matched pairing and reaches 59.6 mAP. Pick RT-DETR for throughput, at 41.6% faster on average, and for the wider ladder of 7 variants. Both ship under Apache-2.0, so licensing does not force the call.

Every number on this page comes from the verified dataset: same 500-image COCO val2017 slice, conf 0.001, IoU 0.6, max 300 detections, pycocotools mAP, identical protocol across all hardware and runtimes. The full protocol is on the methodology page. To rerun this comparison with your own filters, open compare. Accuracy is measured on LibreYOLO retrained checkpoints; other weight sources can yield different values.