# Post-training quantization methods support for YOLO models in TensorRT format
**URL:** https://community.ultralytics.com/t/post-training-quantization-methods-support-for-yolo-models-in-tensorrt-format/977
**Category:** Support
**Tags:** question, yolo, code, support
**Created:** [April 15, 2025, 2:37pm UTC](https://community.ultralytics.com/t/post-training-quantization-methods-support-for-yolo-models-in-tensorrt-format/977 "2025-04-15T14:37:20Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@Allan\_K](https://community.ultralytics.com/u/Allan_K)
#### Post date: [April 15, 2025, 2:37pm UTC](https://community.ultralytics.com/t/post-training-quantization-methods-support-for-yolo-models-in-tensorrt-format/977/1 "2025-04-15T14:37:20Z")
Hi everyone,
I’ve been reviewing the [Ultralytics documentation on TensorRT integration](https://docs.ultralytics.com/integrations/tensorrt/) for YOLOv11, and I’m trying to better understand what post-training quantization (PTQ) methods are actually supported when exporting YOLO models to TensorRT.
From what I’ve gathered, it seems that only **static PTQ with calibration** is supported, specifically for **INT8 precision**. This involves supplying a representative calibration dataset during export or conversion. Aside from that, **FP16 mixed precision** is available, but that doesn’t require calibration and isn’t technically a quantization method in the same sense.
I’m really curious about the following:
- Is INT8 with calibration really the _only_ PTQ option available for YOLO models in TensorRT?
- Are there any other quantization methods (e.g., dynamic quantization) that have been successfully used with YOLO and TensorRT?
Appreciate any insights or experiences you can share—thanks in advance!
---
### Author:  [@BurhanQ](https://community.ultralytics.com/u/BurhanQ)
#### Post date: [April 15, 2025, 3:22pm UTC](https://community.ultralytics.com/t/post-training-quantization-methods-support-for-yolo-models-in-tensorrt-format/977/2 "2025-04-15T15:22:17Z")
The TensorRT INT8 quantization that’s supported in `ultralytics` is the same as what is supported via the [TensorRT Python API](https://docs.nvidia.com/deeplearning/tensorrt/latest/_static/python-api/infer/Int8/Calibrator.html). What would the interest be in using dynamic quantization? AFAIK, using dynamic quantization would result in slower inference speeds, as it will have to calculate activations at inference time and some may require floating point operations.
I think anyone seeking to use dynamic quantization is going to benefit more from collecting additional data to calibrate the exported model with. Since dynamic quantization is supposed to be “more flexible” than static, where that flexibility pertains to the data at inference time vs calibration. Monitoring inference performance and collecting data means that one can alway export a model again and recalibrate on updated examples, where as incorporating dynamic quantization is likely to incur performance penalties that are undesirable.
---
### Author:  [@Allan\_K](https://community.ultralytics.com/u/Allan_K)
#### Post date: [April 15, 2025, 3:41pm UTC](https://community.ultralytics.com/t/post-training-quantization-methods-support-for-yolo-models-in-tensorrt-format/977/3 "2025-04-15T15:41:21Z")
Thank you so much for clarification👍
---
### Author:  [@pderrenger](https://community.ultralytics.com/u/pderrenger)
#### Post date: [April 16, 2025, 1:27pm UTC](https://community.ultralytics.com/t/post-training-quantization-methods-support-for-yolo-models-in-tensorrt-format/977/4 "2025-04-16T13:27:28Z")
Hi Allan\_K,
Glad we could help clarify things for you! Let us know if any other questions come up.