How does Xtrovert convert a local schedule time to UTC and display it in your time zone?
Xtrovert interprets the date and time selected in the composer in your browser's local time zone, converts it to an ISO UTC timestamp for storage, and converts that timestamp back through the browser when the queue displays it. You therefore choose a local wall-clock time, while the dispatcher compares a normalized instant when deciding what is due.
What happens when you choose a date in the Xtrovert composer?
The browser turns the local date-time field into a JavaScript Date and sends its ISO string to the posts API. That string identifies one UTC instant, and the database stores it in a timestamp-with-time-zone field.
The dispatcher compares that stored instant with the current ISO time on each run. It does not need to know the city typed by the user because the browser conversion already resolved the local offset for that selected date.
What is the fast way to schedule the correct instant with Xtrovert?
The fast way is to confirm the computer's time zone, choose the intended local date and time in Xtrovert, and inspect the queue immediately after saving. If the audience is elsewhere, convert the audience's target time before entering it on your device.
You can test local scheduling behavior in Xtrovert Studio without a live account. Sign in to publish through the connected queue and see the scheduling limits for Free and Pro.
How does the queue display the stored UTC timestamp?
The queue creates a Date from the stored timestamp and formats it with the browser's locale, so it normally appears in the time zone of the device currently viewing the dashboard. The underlying instant remains unchanged.
Changing the device time zone can therefore change the displayed clock time without rescheduling the post. The guide to scheduling for a Mexico audience from Spain gives a practical cross-zone review checklist.
What should you check around daylight-saving time changes?
You should check the actual date, both locations' offsets on that date, and the queue display after saving. Regions can change clocks on different weekends, so a familiar month-to-month offset may not apply to a particular campaign.
Enter the date only after confirming the audience's desired local hour. If you later change the schedule, repeat the conversion rather than assuming the same offset still applies.
How should you finalize a time-zone-sensitive queue in Xtrovert?
Finalize it by reviewing every scheduled card on the device and time zone the team uses for approval, then recording the audience-local equivalent when coordination matters. Avoid changing the reviewing device's zone mid-check without reloading and reconciling the display.
Xtrovert normalizes the selected instant for reliable server-side dispatch and presents it through the viewer's browser. Your explicit audience-time check supplies the context that a timestamp alone cannot infer.