Ultralytics v8.4.82 is out 
Quick summary: Ultralytics v8.4.82 is a stability-focused release that makes Ultralytics YOLO workflows more reliable, especially for YOLO26 Axelera exports, classification RAM caching, and training/data edge cases. If you’re deploying YOLO26 or training classification models at scale, this update is worth grabbing. ![]()
You can explore the release on GitHub Releases and review the full changelog.
Highlights
More reliable YOLO26 Axelera exports
This is the biggest fix in v8.4.82.
We fixed an issue where Axelera export could accidentally remove its own generated files when run from the model directory, leading to confusing failures like “output model too small” even when compilation had actually succeeded.
This release:
- Uses a safer temporary compile directory
- Prevents cleanup from deleting valid outputs
- Adds better export serialization to avoid shared-state conflicts
- Restores support for
end2end=Falseexports where supported
This should make deployment pipelines much more dependable, including automated jobs on the Ultralytics Platform.
Classification cache='ram' is back, safely
Classification training can now use cache='ram' again without the previous memory growth issue.
Instead of duplicating decoded images across workers, images are now stored in a shared memory buffer, improving memory efficiency while preserving the speed benefits of RAM caching.
Faster failure for empty-label datasets
Training now stops immediately with a clear error when a detection dataset contains no usable labels at all. This helps catch dataset issues earlier and avoids more confusing failures later in training.
Better real-world image handling
We improved image format handling by:
- Adding proper fallback support for
.heif - Removing the invalid
.jpeg2000extension from supported image lists
Python reliability improvements
Several subtle mutable default argument bugs were fixed across metrics, TAL, augmentations, YOLOE, and SAM-related code. These changes improve long-running reliability in notebooks, services, and repeated train/infer workflows.
Improvements
Docs and workflow polish
A few helpful quality-of-life updates landed as well:
- Clearer documentation for
stream=Truebehavior in predict mode - Added docs for
MLFLOW_KEEP_RUN_ACTIVEfor MLflow users - Updated citations for YOLOv7, YOLOv9, YOLOv10, and YOLO12 docs
- Cleaner Slack release and CI notifications
What’s changed
- Guard YOLO26 Axelera end2end exports by @glenn-jocher
- Restore Axelera
end2end=falseexports by @glenn-jocher - Fix mutable default args in metrics and TAL by @raimbekovm
- Fix mutable default args in augment, YOLOE, and SAM by @raimbekovm
- Restore fail-fast when training labels are all empty by @AffanBinFaisal
- Document
MLFLOW_KEEP_RUN_ACTIVEfor MLflow integration by @raimbekovm - Update YOLOv7, YOLOv9, YOLOv10, and YOLO12 citations by @banu4prasad
- Clarify
stream=Truebehavior by @seungcle - Drop phantom
jpeg2000extension and fixheifloader fallback by @raimbekovm - Refactor comments in
tests/__init__.pyfor clarity by @penampungdipek-creator - Fix classification
cache='ram'leak via shared memory tensor by @raimbekovm - Simplify Slack notification messages by @glenn-jocher
- Fix Axelera export deleting its output when run from the model directory by @glenn-jocher
New contributors
Thanks to our new contributors for jumping in:
- @seungcle for their first contribution in PR #24657
- @penampungdipek-creator for their first contribution in PR #24651
Try it out
Update with:
pip install -U ultralytics
If you’re starting a new project, we recommend YOLO26 on Ultralytics Platform for the latest and best-performing Ultralytics model family, with full support for detect, segment, classify, pose, and OBB workflows.
Feedback welcome 
Please give v8.4.82 a try and let us know how it works in your training and deployment pipelines. Feedback, bug reports, and regression checks are always appreciated from the community.