Datetimes are stored as UTC, but does the Datetime input field accept input based on the client/browser local timezone?

Help
1

I’ve been wondering about this, because I’ve been trying to view my data for a datetime input field from browsers that use different timezones. Whatever I input on browser A looks the same on browser B, but I don’t think that should be how it works.

For example, I select this as input on the datetime field on Browser A: 2025-12-06 04:00:00

When I view the data on Browser B, it still looks like 2025-12-06 04:00:00.

When I use this data as an input to a flow, I also see the exact same time on the payload (i.e. 2025-12-06 04:00:00), but without a timezone. So my understanding is, the value I thought to be accepted in Browser’ A’s timezone was being treated as “UTC” without an actual conversion.

Am I missing something?

2

As noted in the docs: https://directus.io/docs/guides/data-model/interfaces#datetime

Only the timestamp data type stores and uses Time Zone values. The Data Studio will auto convert based on the users browser setting when a timestamp field is used.

Hope this helps clear things up :slight_smile: