Symbol Docs
Features

Date and time fields

How a date and time field stores the moment you pick, so it means the same instant on every device and sorts and filters correctly.

A date and time field holds one moment. Symbol stores it in UTC, so the same value means the same instant on your phone, in the browser and for an assistant, whatever time zone each of them is in.

Picking a time

In the web app and the mobile app you pick a time in your own time zone. Symbol saves the instant you picked. Someone in another time zone sees the same moment in theirs: 3 pm in Sydney on 3 November shows as 4 am in London.

Saving a capsule never moves a time you did not pick again. Editing another field leaves it on the same instant.

Sorting and filtering

Because every value names an instant, sorting a Type by a date and time field and filtering it by a range compare moments, not text. A capsule written from the phone and one written by an assistant sort together correctly.

Older values

Values saved before this change may be stored as they were sent, for example 2026-11-03T15:00 with no time zone. They keep working:

  • A value with no time zone is read as UTC, and a date with no time as midnight UTC. Sorting and filtering already read them this way.
  • They change only when the capsule's field values are saved again. That save stores each one in UTC, naming the same instant. Opening a capsule, or saving only its title, leaves them as they are.

For developers

field_values on POST /api/preview/capsules and PUT /api/preview/capsules/{id} (and every MCP and Bridge write) accept a datetime value in any of these forms:

You sendMeansStored as
2026-11-03T15:00:00+11:00the offset as written2026-11-03T04:00:00.000Z
2026-11-03T15:00UTC (no offset)2026-11-03T15:00:00.000Z
2026-11-03 15:00:00ZUTC2026-11-03T15:00:00.000Z
2026-11-03midnight UTC2026-11-03T00:00:00.000Z

The stored form is UTC with a four-digit year, T, seconds, a fraction of at least three digits and Z. Digits beyond milliseconds are kept (.123456), so an offset value and its UTC equivalent store the same string. The response and every later read return the stored form. The same applies to a datetime column in a table field. A date field is a separate type and keeps YYYY-MM-DD.

A value must name an instant Symbol can sort and filter: a real calendar date, a year from 0001 to 9999 once converted to UTC, and an offset under 16 hours. Anything else answers 422 with a datetime_range error naming the field, for example 2026-11-03T15:00:00+16:00, 0000-06-01T12:00:00Z, or 0001-01-01T00:30:00+01:00, which is year zero in UTC. The write is all or nothing.

The one exception keeps older capsules saveable. A value already stored on that capsule, in that same field (or the same row and column of a table), that falls outside this range is kept byte for byte when you send it back unchanged, for example in a full field map that edits another field. Sending a different such value, or sending it for a new capsule or another row, is refused. Duplicating a capsule leaves such a value out of the copy. To change it, clear the field or send a supported instant.

When the field values of a capsule are submitted, every supported datetime value in them is stored in the UTC form, including unchanged older values. A write that sends no field_values changes none of them.

On this page