You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I pass different props to the CldUploadButton - which can sometimes change. For example, the folder setting.
The updated value of the prop isn't respected/doesn't trigger a re-rendering - and remains as it was first provided.
Describe the solution you'd like
I think tracking the component props' changes, and then updating accordingly could be useful.
Describe alternatives you've considered
A current alternative is re-triggering rendering by setting CldUploadButton's key prop to whatever changing props you may have. It currently works for me as my dynamic props can be represented by strings.
hi @suuf , thanks for the detailed report and for sharing the workaround.
You're right, the widget is created once when the Cloudinary script loads, and prop changes after that aren't propagated to the existing widget instance. The Cloudinary Upload Widget SDK does have an update() method for this, but wiring it up correctly requires deep-comparing options on each render to avoid unnecessary updates, and confirming which options the SDK accepts at update time vs. creation time.
The key prop workaround you described should suffice for now.
I'll track this as a future enhancement. Thanks for raising it.
Activity
PaulBoye-py commentedon Sep 17, 2026
hi @suuf , thanks for the detailed report and for sharing the workaround.
You're right, the widget is created once when the Cloudinary script loads, and prop changes after that aren't propagated to the existing widget instance. The Cloudinary Upload Widget SDK does have an
update()method for this, but wiring it up correctly requires deep-comparing options on each render to avoid unnecessary updates, and confirming which options the SDK accepts at update time vs. creation time.The
keyprop workaround you described should suffice for now.I'll track this as a future enhancement. Thanks for raising it.