> For the complete documentation index, see [llms.txt](https://docs.augelab.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.augelab.com/key-features/annotate-data-for-object-detection/augment-dataset.md).
# Augment Dataset
Dataset augmentation creates new training images by applying controlled transformations to your existing labeled images while keeping bounding boxes perfectly aligned.
Used correctly, augmentation helps your model **generalize** (perform well on new images). Used incorrectly, it can **make training worse** by teaching the model unrealistic patterns.
***
## ⚖️ What Augmentation Is (and Is Not)
| **Augmentation IS...** | **Augmentation IS NOT...** |
| ----------------------------------------------- | ---------------------------------------------------- |
| A way to simulate lighting, rotation, or noise. | A substitute for missing camera angles or products. |
| A tool to improve robustness in small datasets. | A fix for incorrect or "sloppy" initial labels. |
| A method to reduce overfitting. | A guarantee of better results (over-doing it hurts). |
***
## Strategic Usage
When Augmentation Is Helpful
* **Small Datasets:** You have few images per class.
* **Environmental Variation:** You expect shifts in lighting (day/night), glare, or motion blur.
* **Overfitting:** Training accuracy is high, but real-world performance is low.
* **Rare Classes:** Some objects appear infrequently in your real data.
When Augmentation Is Unnecessary (or Risky)
* **Diverse Real Data:** You already have thousands of varied, real-world images.
* **Subtle Features:** Your inspection depends on tiny scratches or textures that blur/noise might destroy.
* **Stable Environments:** The lighting, camera, and product positions never change. For example, a fixed position object does not need rotation augmentation.
{% hint style="warning" %}
**Disk Space Alert:** Augmentation generates new physical files. Enabling many options can cause your dataset folder size to explode. **Run augmentation only after finishing manual labels and keeping a backup.**
{% endhint %}
***
## 🛠️ How the Augmentation Window Works
In the Image Annotation Window, navigate to **Tools** → **Augment Dataset**.
### Interface Breakdown
| Section | Function |
| -------------------- | ----------------------------------------------------------------------------------------------------- |
| **Quick Presets** | One-click configurations to apply sensible starting defaults.  |
| **Quick Toggles** | Enable/disable entire groups (e.g., Color, Noise) quickly.  |
| **Detailed Options** | Fine-tune intensity for Brightness, Contrast, Blur, Noise, and Perspective tweaks. |
***
## A Safe, Practical Workflow
1. **Clean Baseline:** Finish manual labeling first (or at least a clean subset).
2. **Backup:** Duplicate your dataset folder.
3. **Start Small:** Use a preset or minimal manual settings.
4. **Visual Audit:** Open the generated folder and check:
* Are the bounding boxes still centered on the objects?
* Do augmented images still look realistic?
5. **Train & Compare:** Compare the results of a model trained with and without augmentation.
***
## ❓ Troubleshooting
📉 "My model got worse after augmentation"
This often means the augmentation didn't match reality.
* **Try:** Reduce augmentation intensity.
* **Try:** Disable transforms that create unrealistic images (e.g., don't use 180° rotation if parts are always upright).
🖼️ "Boxes look wrong on augmented images"
* **Try:** Reduce geometric transforms (rotation/perspective).
* **Try:** Validate that your labels were tight and correct before augmentation.
📂 "It generated too many files"
* **Try:** Disable most transforms and keep only the ones you really need.
* **Try:** Use augmentation on a smaller subset of images.