- Getting started with Airtable
- Introduction to Airtable basics
- Contacting Airtable Support Updated
- Airtable home screen
- Glossary of Airtable terminology
- Airtable technical requirements
- Feature differences between Airtable on desktop and mobile
- Airtable keyboard shortcuts
- Using Markdown in Airtable
- Adding descriptions in Airtable
- Finding Airtable IDs
- Airtable Automations
- Automations Overview
- Automation feature walkthroughs
- Integrated automation walkthroughs
- Airtable automation walkthroughs
- Linking existing records using automations
- Conditional groups of automation actions
- Repeating groups of Airtable automation actions
- Creating recurring records using automations
- How to delay Airtable automation runs
- Prevent automations from triggering by mistake
- Use automations to timestamp status updates
- Automation Triggers
- Airtable Triggers
- Airtable automation trigger: When record matches conditions
- Airtable automation trigger: When a form is submitted
- Airtable automation trigger: When record created
- Airtable automation trigger: When record updated
- Airtable automation trigger: When record enters view
- Airtable automation trigger: At scheduled time
- Airtable automation trigger: When webhook received
- Airtable automation trigger: When a button is clicked
- Airtable automation trigger: When email received Updated
- Integrated Triggers
- Airtable Triggers
- Automation Actions
- Airtable Actions
- Airtable automation action: Send email Updated
- Airtable automation action: Create record
- Airtable automation action: Update record
- Airtable automation action: Find records
- Airtable automation action: Sort list
- Airtable automation action: Run a script Updated
- Airtable automation action: Generate with AI
- Integrated Actions
- Airtable automation actions: Slack
- Airtable automation actions: Google Workspace
- Airtable automation action: Send MS Teams message
- Airtable automation actions: Outlook
- Airtable automation actions: Jira Cloud
- Airtable automation actions: Jira Server / Data Center
- Airtable automation actions: Salesforce
- Airtable automation action: Create post in Facebook Pages
- Airtable automation actions: GitHub Issues
- Airtable automation action: Hootsuite post
- Airtable automation action: Send Twilio SMS
- Airtable Actions
- Airtable Bases
- Using Airtable Cobuilder
- Airtable bases overview
- Creating and managing Airtable bases
- Structuring bases in Airtable
- Moving bases between workspaces in Airtable
- Creating and managing tables in Airtable
- Creating Airtable base share links
- Importing third-party data into Airtable
- Using insights in Airtable
- Troubleshooting Airtable base performance
- Airtable Betas
- Collaborating in Airtable
- Airtable Enterprise Support
- General Enterprise information
- External badging in Airtable
- Using app library and components in Airtable Updated
- Ask an Expert beta overview
- European data residency at Airtable
- Airtable user groups overview
- Airtable Enterprise API
- Creating and managing data retention policies in Airtable
- eDiscovery APIs in Airtable
- Airtable and data loss prevention
- Accessing Enterprise audit logs in Airtable
- Set up Jira Server / Data Center to connect with Airtable
- Admin panel pages
- Airtable admin panel overview
- Users - Airtable enterprise admin panel
- Airtable admin panel user details
- Groups - Airtable admin panel
- Workspaces - Airtable Enterprise Admin Panel
- Bases - Airtable admin panel
- Interfaces - Airtable admin panel
- Data sets - Airtable admin panel
- Managed apps - Airtable admin panel
- Components - Airtable admin panel
- Reports - Airtable admin panel
- Settings - Airtable admin panel Updated
- Managing Enterprise organizations
- Managing Enterprise admins in admin panel
- Using Organizations
- Organization branding for apps in Airtable
- Enterprise Hub in Airtable
- Enterprise Hub: Org unit assignment with user groups Updated
- Deactivating, removing access, and reactivating users in the admin panel
- Managing user access to workspaces and bases
- Airtable Enterprise Key Management Updated
- Custom terms of use New
- Enterprise SSO
- General Enterprise information
- Airtable Extensions
- Airtable Fields
- Fields Overview
- Attachment
- Date-based fields
- Formula
- Getting Started with Formulas
- Formula Foundations
- The essentials of Airtable formulas
- Formula writing tips for beginners
- Troubleshooting formulas
- Basic calculations
- Conditional statements
- Logical arguments
- Working with dates
- Displaying DATETIME_FORMAT using the date field in Airtable
- Working with date functions in Airtable
- Calculating the difference between dates in Airtable
- Supported DATETIME_DIFF unit specifiers in Airtable
- Supported DATETIME_FORMAT format specifiers in Airtable
- Using the DATETIME_PARSE() formula in Airtable
- Working with timezones
- Record functions
- Text functions
- Numeric functions
- Common Solutions: Beginner
- Common Solutions: Intermediate
- Common Solutions: Advanced
- Long Text Field
- Linked Record Field
- Linking records in Airtable
- Limiting linked record selection to a view in Airtable
- Dynamic filtering in linked record fields
- Linking to one, many, or a subset of Airtable records
- Converting existing fields to Airtable linked records
- Reordering record links in Airtable
- Understanding linked record relationships in Airtable
- Number-Based Fields
- Other Fields
- Rollup, lookup, and count fields
- Select and user fields
- Integrating with Airtable
- API
- Getting started with Airtable's Web API
- Creating personal access tokens
- Airtable Webhooks API Overview
- Service accounts overview
- Airtable Web API - Using filterByFormula or sort parameters
- Airtable API Deprecation Guidelines
- Airtable API: Common troubleshooting
- Managing API call limits in Airtable
- URL length limitations for web API requests
- Integration services
- Third-party integrations via OAuth overview
- Troubleshooting disconnected OAuth integrations in Airtable
- Options for integrating with Airtable
- Third-party integrations - Common troubleshooting
- Low-code integrations - Common troubleshooting
- Integrating Airtable with external calendar applications
- Visualizing records from Airtable in Tableau
- Visualizing Airtable records in Microsoft Power BI & Power Query
- Integrating HubSpot with Airtable
- Using Zapier to integrate Airtable with other services
- Using Zapier's Multi-Step Zaps to find and update records
- Using IFTTT to integrate Airtable with other services
- Integrating with AWS Lambda & DynamoDB
- Developer tools
- API
- Airtable Interface Designer
- Interface Designer overview articles
- Interface layouts
- Interface elements
- Adding and removing elements in interfaces
- Adding layouts to interfaces
- Formatting elements in interfaces
- Interface element: Button
- Interface element: Calendar
- Interface element: Chart
- Interface element: Filter
- Interface element: Gallery
- Interface element: Grid
- Interface element: Kanban
- Interface element: Number
- Interface element: Record picker
- Interface element: Text
- Interface element: Timeline
- Learning and Resources
- Managing Airtable
- Airtable Policy
- Airtable Records
- Airtable Sync
- Airtable Views
- Airtable Workspaces
- Print
- Share
- DarkLight
- PDF
Timezones and locales in Airtable
- Updated on 14 Dec 2023
- 6 Minutes to read
- Print
- Share
- DarkLight
- PDF
This article covers how to work with and troubleshoot timezones to streamline your team's and organization's work.
Introduction
Insert plan types this feature is available to | |
Platform(s) | Web/Browser, Mac app, and Windows app |
Related reading |
Options for displaying dates in Airtable
Options for displaying dates
All dates are stored in Airtable in Greenwich Mean Time, or GMT. But, how you choose for them to display in your base is a field-level setting that will affect all collaborators. You can have dates display either:
In collaborators' local time, so the datetime will appear different for viewers in different timezones, adjusted from GMT
As the same for everyone, done by switching on the "Use the same timezone for all collaborators" toggle shown below, in the field's customization menu.
Here are a few facts related to this:
There is no workspace, base, table, or user-wide timezone setting in Airtable.
Any formatted date has the potential to be set to any viewer's local time, OR
Any formatted date can be specified to show a specific timezone.
What this means is that collaborators working together in the same base can, and will, see different dates and times unless a specific timezone has been specified (again, on a field-by-field basis).
Setting timezones in Airtable
Setting timezones using SET_TIMEZONE()
There are two ways to manually set a timezone for a date field: using the "Use same timezone for all collaborators" toggle in the field configuration menu and selecting the desired timezone OR using a formula field with the SET_TIMEZONE()
function. Using the toggle is the easiest option and works well for cases where you want the specified timezone to be used 100% of the time. For more complex cases where you might want to conditionally show different timezones, we recommend the formula option.
Setting a timezone in the date field configuration menu
You can choose a specific timezone for a date field by toggling the option to "Use the same time zone for all collaborators" in the field configuration menu. You will then be able to choose your desired timezone from a drop-down list. GMT/UTC will be chosen by default.
![2023-02-22_Set-timezone-in-date-field](http://cdn.airtable.document360.io/d0ee2ee4-3f78-47c7-b388-85e40be9fb89/Images/Documentation/2023-02-22_Set-timezone-in-date-field.png)
Setting a timezone with a SET_TIMEZONE() formula function
The SET_TIMEZONE()
function will allow you to set the timezone for the data from a date type field. This article will cover its use and is part of a guided course which you can view here.
This is written in the form SET_TIMEZONE(datetime, 'timezone identifier')
, in which the format specifier can be something like 'America/Chicago'
, 'Europe/Oslo'
, or 'Pacific/Marquesas'
.
NOTE
For a full list of supported timezone identifiers, see this article.
Whenever you need to set a timezone, you'll need to use this function in combination with DATETIME_FORMAT()
. You'll first write the DATETIME_FORMAT function, and then wrap that function with SET_TIMEZONE().
For example, if a date field is configured to not use GMT time; therefore, the date will be shown in your local timezone (CST). Using the combination of SET_TIMEZONE()
and DATETIME_FORMAT()
, you can convert what's shown in the date field to Los Angeles time.
DATETIME_FORMAT(
SET_TIMEZONE(
Date, 'America/Los_Angeles'),
'M/D/Y h:mm A'
)
Here's the result of this formula:
There's just one problem - the result of this formula is not a formatted date that's readable by Airtable. Remember that DATETIME_FORMAT() converts datetimes into strings. We'll need to use DATETIME_PARSE() to transform this string into a readable date. Below, the {Set Timezone} field is referenced instead of using the original formula above to keep the formula simplified.
DATETIME_PARSE(
{Set Timezone},
'M/D/YYYY h:mm A'
)
Here's the result of this second formula:
The output of this formula is now a formatted date. Now that we've gone over the separate parts of this formula, let's bring it all together into a single formula:
DATETIME_PARSE(
DATETIME_FORMAT(
SET_TIMEZONE(
Date, 'America/Los_Angeles'
),
'M/D/Y h:mm A'),
'M/D/YYYY h:mm A'
)
Notice that the option to "Use the same timezone for all collaborators" is toggled on and the timezone is set to GMT in the field formatting settings. This is needed to display the correct time after manually setting the timezone with the formula.
Setting timezones using using DATEADD()
There's another way to specify timezones that can, at times, be a more simple approach. We've already reviewed the use of DATEADD();
now we'll look at how to use this function alongside timezones.
Remember that the structure of that function is:
DATEADD (Date, #, 'units' )
Or:
DATEADD ({Date Field}, 5 , 'days' )
Since every timezone in the world is offset a certain number of hours from GMT time, we can easily specify a timezone without using the SET_TIMEZONE()
function. Here are a few cities listed with the difference, in hours, from GMT:
New York: -4
Chicago: -5
San Francisco: -7
London: +1
The formula below will convert the GMT time to the local timezones, which are each specified by how many hours they are offset from GMT.
DATEADD ({GMT Date},{GMT Diff}, 'hours' )
This approach can be helpful if a date needs to be specified in GMT time, but collaborators in other regions need to see that time translated to their local timezone.
Setting locales in Airtable
Setting locales
NOTE
For a full list of all locales, see this support article.
Now that we've translated a local time to a specified timezone, let's look at how to further transform that into a locale (a specific language or region).
The SET_LOCALE()
function takes a given datetime input and formats it to match a particular locale. This function is written in the form SET_LOCALE(datetime, 'locale modifier')
, in which the locale modifier can be something like 'en-nz' (New Zealand English), 'tzm' (Amazigh/Berber), or 'zh-tw' (Traditional Chinese).
Locale modifiers can change a number of different aspects of a datetime, including:
Numerical digits: for certain locales not using West Arabic numerical digits, numerical digits will be converted, e.g. for 'ar' (Arabic), 1 => ٢.
Script directionality: for locales using scripts that are written right-to-left, e.g. 'he' (Hebrew), the datetime will change direction accordingly.
Month and weekday names : month/weekday names will be changed to reflect the locale's language, e.g. for 'es' (Spanish), Wednesday => Miércoles.
Long date format : Long datetimes will be formatted according to the preferred format of the locale, e.g. for 'en-gb' (British English), 'MMMM D, YYYY h:mm A' => 'D MMMM YYYY HH:mm'.
As an example, we'll translate the datetime into Spanish. Here's the original formula:
DATETIME_PARSE(
DATETIME_FORMAT(
SET_TIMEZONE(
Date, 'America/Los_Angeles'
),
'M/D/Y h:mm A'),
'M/D/YYYY h:mm A'
)
And here is that same formula with the added locale function:
DATETIME_FORMAT(
SET_LOCALE(
DATETIME_PARSE(
DATETIME_FORMAT(
SET_TIMEZONE(
Date, 'America/Los_Angeles'
),
'M/D/Y h:mm A'),
'M/D/YYYY h:mm A'
),
'ES'),
'LLLL'
)
Troubleshooting timezone issues in Airtable
Troubleshooting timezone issues
While formula functions help take a lot of trouble out of timezones, the nature of time differences can still be confusing from time to time. When something doesn’t work out the way you expected, you can often resolve the issue if you know how to troubleshoot.
Consider the following formula:
IS_SAME(NOW (),{Start Day & Time },'day ')
Something’s not working quite right, but what could it be? Here’s the issue in detail:
You just started using IS_SAME() to match up dates that are the same. In your table, all tasks that have today's date are the same. However, some tasks have a timestamp occurring after 7:00 PM EST and those records are failing to match as TRUE (same) when compared with TODAY() using IS_SAME(). If you change the timestamp to be earlier than 7:00 PM EST everything works fine. Is it some fixed time zone issue with the TODAY() function?
For proper reference, these are the results you’re getting with the formula in question:
We can assume that NOW()
is correctly producing the same date as shown in the {Start Day & Time} field. Because NOW()
is equal to 4/10/2020, the formula should produce a 1 for every record shown here.
In this case, the date field is displaying values in local time, while the NOW()
formula is producing a date in GMT time, which for some of the records falls on the next day. Remember that all dates in Airtable are stored as GMT.