# Builds cause change to fmodstudio.dll.meta

**URL:** <https://qa.fmod.com/t/builds-cause-change-to-fmodstudio-dll-meta/24566>\
**Category:** Unity\
**Tags:** unity\
**Created:** [October 15, 2026, 5:23am UTC](https://qa.fmod.com/t/builds-cause-change-to-fmodstudio-dll-meta/24566 "2026-10-15T05:23:44Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![fendercodes](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/fendercodes/32/2971_2.png) [@fendercodes](https://qa.fmod.com/u/fendercodes)\
**Post date:** [October 15, 2026, 5:23am UTC](https://qa.fmod.com/t/builds-cause-change-to-fmodstudio-dll-meta/24566/1 "2026-10-15T05:23:45Z")

</div>

After we do standalone builds, the `fmodstudio.dll.meta` file gets changes such as those shown below.

 ![Code_oN7MeoIcIz](https://canada1.discourse-cdn.com/flex036/uploads/fmod/original/2X/0/0dae1ca86ced7c2c1e37d623bd09943b20be593b.png)

I think its because the file was made with an older version of Unity perhaps? We are on **6000.3.11f1**. I try not to change third-party code in our project because it becomes difficult to upgrad when you release updates.