# Metadata override when calling addFile

**URL:** <https://community.transloadit.com/t/metadata-override-when-calling-addfile/16280>\
**Category:** Uppy\
**Created:** [October 10, 2022, 9:42am UTC](https://community.transloadit.com/t/metadata-override-when-calling-addfile/16280 "2022-10-10T09:42:28Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![ruimcf](https://yyz2.discourse-cdn.com/flex032/user_avatar/community.transloadit.com/ruimcf/32/667_2.png) [@ruimcf](https://community.transloadit.com/u/ruimcf)\
**Post date:** [October 10, 2022, 9:42am UTC](https://community.transloadit.com/t/metadata-override-when-calling-addfile/16280/1 "2022-10-10T09:42:28Z")

</div>

Hello, when I call addFile function in the uppy instance with a metadata object, the fields ‘type’ and ‘name’ are overridden by uppy [uppy/Uppy.js at 930645ecde8359e8729e88ddc35729ddc6c6c980 · transloadit/uppy · GitHub](https://github.com/transloadit/uppy/blob/930645ecde8359e8729e88ddc35729ddc6c6c980/packages/%40uppy/core/src/Uppy.js#L467)

I am using the field ‘type’ in metadata to define important information that I will use right after the file is added, so this override is causing information to be lost.  
I found no mention in comments and in the documentation about restrictions of field in the metadata so this override is came as a surprise.

Is there a reason this override exists?