We are using the Plasmic Loader SDK combined with Plasmic CMS for our images (such as logos and product assets), and we are seeing an issue where the Plasmic Image Optimizer API completely drops the width parameter in production.
When inspecting the optimized image URLs generated on our live site, we notice they look like this:
https://img.plasmic.app/img-optimizer/v1/img?src=https%3A%2F%2Fsite-assets.plasmic.app%2F824c61d7889372e2c0d56fe3d5d096d9.png&q=75
The q=75 quality parameter is appended correctly, but the w= parameter is missing. This is happening even though we explicitly have the width attribute configured in the right-hand settings panel inside Plasmic Studio for these specific assets.
If we manually append &w=100 to that optimizer URL string in the browser, the endpoint works and serves a scaled image. However, Plasmic isn’t passing the value along to the API query for some reason.
What we have already tested/checked:
-
Studio Settings: We confirmed the width properties are set explicitly in the configuration panel for these components.
-
Publishing Status: We fully deployed the changes across both staging and production environments to rule out caching/stale builds.
-
Studio Layout Validation: We noticed some initial layout errors in the “Issues” panel regarding “Img width and Height” mismatch conflicts across screen variants. To test, we cleaned one of those up. Even on a perfectly clean, simple asset with zero Studio errors (like a standalone logo component), the
wparameter is still dropped.
How can we force the Studio-defined width setting to successfully append as a w= query parameter in the final URL?
Thanks in advance for any insights!