Webflow CMS Date Field: Static UTC vs Client‑Side Time Zone Conversion – Which Approach Should You Choose?

Goal

Display event dates on a Webflow site in the local time zone of each visitor, rather than the uniform UTC that the CMS stores.

Constraints

Webflow’s CMS date fields are saved in UTC and rendered using a static format chosen in the template. The platform offers no built‑in per‑visitor time‑zone conversion or dynamic formatting options.

Unresolved Decision

Should developers rely on the native Webflow date field with its static UTC value, or implement a custom JavaScript solution that adjusts the displayed time using the browser’s Intl API or a library such as Luxon?

Questions

• Is there any planned Webflow feature that will enable per‑visitor time‑zone conversion for CMS date fields?
• What are the performance and maintainability trade‑offs between using a lightweight client‑side script versus a more complex server‑side approach (e.g., a CMS workflow that stores epoch timestamps)?
• How can developers keep the time‑zone data accurate across daylight‑saving changes without introducing significant overhead?