# Upload duplicate image in dataset

**URL:** <https://community.ultralytics.com/t/upload-duplicate-image-in-dataset/1895>\
**Category:** Discussion\
**Tags:** feature\
**Created:** [March 25, 2026, 1:50am UTC](https://community.ultralytics.com/t/upload-duplicate-image-in-dataset/1895 "2026-03-25T01:50:17Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Shyob](https://sea1.discourse-cdn.com/flex001/user_avatar/community.ultralytics.com/shyob/32/1377_2.png) [@Shyob](https://community.ultralytics.com/u/Shyob)\
**Post date:** [March 25, 2026, 1:50am UTC](https://community.ultralytics.com/t/upload-duplicate-image-in-dataset/1895/1 "2026-03-25T01:50:17Z")

</div>

Hi~

I just tried uploading some images that already exist in the dataset, and they were saved as a different version without any warnings. I anticipate this will cause data duplication.

Is it possible to add a duplication check feature based on filename and a user-selectable validation method, such as: **Overwrite / Skip / Save as a different name / Cancel**

Also, it would be great if the duplication detection could be based on comparing image content or some more accurate method than just relying on filenames. However, I’m not sure about the feasibility of programming this functionality. Hope you guys can consider this.

 ![image](https://us1.discourse-cdn.com/flex001/uploads/ultralytics1/original/2X/0/02e4a1ca166da5da4c2e60b677a573032c79e5da.png)

---

<div class="post-metadata">

**Author:** ![pderrenger](https://sea1.discourse-cdn.com/flex001/user_avatar/community.ultralytics.com/pderrenger/32/73_2.png) [@pderrenger](https://community.ultralytics.com/u/pderrenger)\
**Post date:** [March 26, 2026, 12:57am UTC](https://community.ultralytics.com/t/upload-duplicate-image-in-dataset/1895/2 "2026-03-26T00:57:04Z")

</div>

Thanks — that’s a very reasonable feature request.

Right now, **Ultralytics Platform** doesn’t show an upload-time duplicate warning at the dataset UI level. It does already use hash-based, content-addressable storage for backend deduplication, as noted in the [dataset docs](https://docs.ultralytics.com/platform/data/datasets/#how-does-storage-work), but that’s mainly for storage efficiency and doesn’t currently act like a “duplicate file conflict” check inside a dataset.

So yes, filename-only checks would help, but content-based duplicate detection is the better approach. Options like `Overwrite`, `Skip`, `Save as a different name`, and `Cancel` all make sense here. I’ll pass this along to the team.

For now, the best workaround is to review in `Table` view and remove extras using the [bulk delete flow](https://docs.ultralytics.com/platform/data/datasets/#bulk-delete).

---

<div class="post-metadata">

**Author:** ![Shyob](https://sea1.discourse-cdn.com/flex001/user_avatar/community.ultralytics.com/shyob/32/1377_2.png) [@Shyob](https://community.ultralytics.com/u/Shyob)\
**Post date:** [March 26, 2026, 6:31am UTC](https://community.ultralytics.com/t/upload-duplicate-image-in-dataset/1895/3 "2026-03-26T06:31:01Z")

</div>

Thank you, i’ll try.
