# Plugin UI - DIfferent dial sizes in .plugin.js descriptions

**URL:** <https://qa.fmod.com/t/plugin-ui-different-dial-sizes-in-plugin-js-descriptions/24441>\
**Category:** FMOD Engine\
**Tags:** plugin-api\
**Created:** [July 30, 2026, 2:03pm UTC](https://qa.fmod.com/t/plugin-ui-different-dial-sizes-in-plugin-js-descriptions/24441 "2026-07-30T14:03:05Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![horacv1](https://avatars.discourse-cdn.com/v4/letter/h/278dde/32.png) [@horacv1](https://qa.fmod.com/u/horacv1)\
**Post date:** [July 30, 2026, 2:03pm UTC](https://qa.fmod.com/t/plugin-ui-different-dial-sizes-in-plugin-js-descriptions/24441/1 "2026-07-30T14:03:05Z")

</div>

Hey everyone!

Does anyone know if there’s a way to get different dial sizes in a plugin’s UI? Ideally I’d love to be able to pick between at least two sizes, Medium and Small.

I’ve tried messing with size policies, stretch factors, and min/max dimensions, but no luck so far.

Here’s the weird part: if I don’t include a .plugin.js file, FMOD Studio defaults to a “Medium” dial. But as soon as I define the Dial in the description file myself, it renders as small instead. That makes me think this isn’t a layout/spacing issue, but more like two separate widgets entirely. I just can’t find anything in the docs about how to choose one over the other.

Has anyone run into this or know where this is documented?

 ![Screenshot 2026-07-30 095811](https://canada1.discourse-cdn.com/flex036/uploads/fmod/original/2X/2/2be8b9d0103e773311c66e0e1d6e7018f3f366df.png)

---

<div class="post-metadata">

**Author:** ![Leah\_FMOD](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/leah_fmod/32/3685_2.png) [@Leah\_FMOD](https://qa.fmod.com/u/Leah_FMOD)\
**Post date:** [August 13, 2026, 7:25am UTC](https://qa.fmod.com/t/plugin-ui-different-dial-sizes-in-plugin-js-descriptions/24441/2 "2026-08-13T07:25:45Z")

</div>

Sorry for the delayed response!

Studio has a couple of dial sizes that it uses internally, but all dials created using the plugin API use the small dial size. Unfortunately I don’t have any workaround for this at the moment, but I’ve added it to our feature tracker.
