Webflow CMS Date Field Time Zone Configuration

There is no built-in configuration for a per-visitor time zone offset for Webflow {{date}} tags. Date fields store timestamps in UTC and render using the site's primary time zone setting; the visual editor lacks a per-field or per-visitor time zone selector across all plan tiers.

Likely explanation vs confirmed facts

Confirmed: UTC storage is the default; the site's primary time zone controls rendering. No built-in per-visitor offset control exists.

Likely: Lower plan tiers may restrict custom code execution, affecting JavaScript SDK-based offset implementation. Plan upgrades or downgrades can reset custom scripts, requiring re-application after publishing.

1. Inspect the rendered HTML of a collection list date element and compare the displayed time against the stored UTC timestamp and the site's primary time zone setting.
2. Add a console.log of Intl.DateTimeFormat().resolvedOptions().timeZone alongside the Webflow date tag to verify client-side offset behavior.
3. Publish the site in an incognito window with different locale settings and confirm whether date displays shift consistently or reset.
4. Check the plan tier's custom code permissions in Webflow's hosting settings; ensure JavaScript SDK execution is allowed for the specific tier.

One missing diagnostic detail that would change the recommendation is the specific plan tier and whether custom code execution is permitted. If this changes, the recommendation for using the JavaScript SDK or exploring tier-specific formatting controls may shift.