AlbumentationsX vs Legacy Albumentations: Practical Benefits
On this page
- The Legacy Package Is No Longer Maintained
- Which Teams Should Care
- Supply-Chain Security and Deployment Reliability
- Capabilities Added After the Fork
- Performance
- Get Started
- Sources
The legacy albumentations package repository was archived (read-only) on July 10, 2025. No further releases, security patches, bug fixes, pull requests, or issues are possible.
AlbumentationsX continues active development with fifteen releases shipped since the fork and more in progress.
This page covers what changed technically. For the legal side, see the License Guide.
The Legacy Package Is No Longer Maintained
The legacy albumentations package is not "stable" in the sense that it is maintained and reliable. It is frozen. There is a difference:
- No security patches. If a CVE is filed against a dependency or a vulnerability is found in the library itself, nobody will fix it in the legacy package.
- No bug fixes. Known issues in replay, serialization, data-loader randomness, and transform behavior were fixed in AlbumentationsX. Those fixes do not exist in the legacy package.
- No new transforms, no new annotation targets, no performance work. The library stopped evolving in May 2025.
If your team depends on a frozen, unsupported package, that is a risk your security and compliance review should know about.
Which Teams Should Care
| Workload or team | What AlbumentationsX adds | Why the legacy package becomes limiting |
|---|---|---|
| Teams with compliance or security review requirements | OIDC trusted publishing, SBOMs, reproducible lockfiles, SECURITY.md | The legacy package never shipped supply-chain attestation artifacts and will never receive security patches. |
| Rotated object detection | Native OBB support across real transform pipelines | You no longer need custom augmentation geometry for rotated boxes. |
| Pose estimation or facial landmarks | Semantic keypoint label swapping | Flips and symmetry transforms can preserve label meaning, not just coordinates. |
| Medical, remote sensing, hyperspectral, multi-sensor data | Strong multichannel performance work plus non-RGB feature growth | The public benchmark signal is much stronger for multichannel data than for simple RGB-only paths. |
| Video-heavy preprocessing | Repeated video and batch-path optimizations across releases | Video is being optimized as a primary workload, not only supported incidentally. |
| Teams with strict debugging and reproducibility needs | Exact applied-parameter capture and deterministic replay | You can inspect and reconstruct what actually happened to a sample. |
| Pipelines that carry metadata with images | user_data and custom apply_to_X targets | Augmentation can update side-channel data instead of forcing custom wrapper logic around every transform. |
Supply-Chain Security and Deployment Reliability
For teams that must audit or attest their dependency chain, these are the changes that matter most:
- OIDC trusted publishing (no long-lived PyPI API tokens)
- SBOM generation with SHA-256 checksums for every release asset
- Reproducible builds via committed lockfile
- A formal
SECURITY.mdwith disclosure process and SLAs - OpenCV as an explicit optional dependency rather than an implicit heuristic-driven install
- Selectable resize backends (
opencv,pillow,pyvips)
Trusted publishing, reproducible lockfiles, and SBOMs are infrastructure that the legacy package never shipped. Teams with compliance or security review requirements get artifacts they can point to.
Capabilities Added After the Fork
Oriented bounding boxes
AlbumentationsX added and expanded native oriented bounding box support in BboxParams, covering pad/crop workflows, a wide transform set, and the cxcywh coordinate format.
Rotated detection is not a corner case in OCR, aerial imagery, industrial inspection, and document analysis. Without native OBB support, teams end up writing custom geometry code around augmentation rather than using augmentation as infrastructure.
Semantic keypoint label swapping
Automatic semantic keypoint label remapping for orientation-changing transforms such as HorizontalFlip, VerticalFlip, D4, and SquareSymmetry.
In pose, face landmarks, and structured keypoint datasets, flipping geometry without flipping semantic labels silently corrupts supervision. AlbumentationsX can keep "left" and "right" consistent inside the augmentation pipeline itself.
Pipeline extensibility
user_datatarget lets a pipeline carry arbitrary Python objects through augmentation and optionally update them per transform. Useful for captions, camera intrinsics, sensor calibration data, and confidence maps.- Custom
apply_to_Xtargets let teams make augmentation logic first-class for project-specific targets without forkingCompose. Composearithmetic for adding, subtracting, and prepending transforms programmatically.
Exact replay and augmentation debugging
Exact applied-parameter capture with save_applied_params=True and replay through Compose.from_applied_transforms(...). This records the concrete sampled values that were used for a given sample, not just the transform ranges declared in the pipeline.
This makes augmentation debuggable. You can answer "what exactly happened to this sample?" with concrete sampled values, inspect failed samples, and decide whether a sampled variant is realistic for the deployment domain or whether the augmentation is too aggressive.
3D, volumes, and letterboxing
GridShuffle3Dforvolume,mask3d, andkeypoints.LetterBox, the standard scale-to-fit-with-padding preprocessing step used in YOLO-style pipelines, with full target support (images, masks, HBB, OBB, keypoints, volumes).
New transforms
Dithering, AtmosphericFog, ChannelSwap, FilmGrain, Halftone, LensFlare, Vignetting, GridMask, WaterRefraction
The benchmark page itself shows rows where AlbumentationsX has transforms with no legacy package comparison row. That is the clearest sign that the comparison is about feature surface area that continued to grow on one side only.
Performance
All speedup numbers below come from the public comparison at AlbumentationsX vs Legacy Albumentations. The benchmark code and output artifacts are public at albumentations-team/benchmark. Teams can rerun the comparison on their own hardware.
Multichannel
The 9-channel benchmark is the strongest public performance signal. AlbumentationsX wins 62 / 67 head-to-head comparisons with a median speedup midpoint of 1.45x. Headline examples:
PiecewiseAffine:183-191xPadIfNeeded:67-73xRotate:9.0-10xAffine:3.6-3.8x
If your workload is hyperspectral, medical, remote sensing, or anything with > 3 channels, AlbumentationsX is not just "the same API with updated licensing." Full multichannel comparison table.
RGB geometry and distortion
The speedups are concentrated in transforms that dominate augmentation cost once you move past flips and crops. Headline examples:
PiecewiseAffine:174-192xUnsharpMask:1.8-2.0xGridDistortion:1.5-1.8xElasticTransform:1.3-1.4x
Video
AlbumentationsX is ahead in 59 / 89 head-to-head video transforms against the legacy package. Headline examples:
PiecewiseAffine:187-199xUnsharpMask:1.7-1.9xElasticTransform:1.5-1.7x
Performance optimization is ongoing across releases, with continued work on video and batch paths, C++ kernels for normalization and brightness/contrast, and dropout transform internals.
Get Started
pip install albumentationsx
AlbumentationsX is free under AGPL-3.0 for open-source projects and evaluation. For proprietary software, a commercial license removes the AGPL obligations with unlimited developer seats and a single agreement. See the License Guide for AGPL vs commercial details.
Sources
- Benchmark comparison page: AlbumentationsX vs Legacy Albumentations
- Benchmark repository: albumentations-team/benchmark
- Release notes