Add timezone display setting for Table Editor timestamp columns

[gmkwak90]

Hi Supabase team,

I would like to request a display setting for timestamp/timestamptz columns in the Table Editor.

Currently, timestamptz values are displayed in UTC, for example:

2026-06-12 07:00:01+00

For users in other time zones, it would be very helpful if the Table Editor allowed choosing a display timezone, such as:

• Browser local timezone
• Project/database timezone
• Custom timezone, e.g. Asia/Seoul
• UTC

This should only affect the Table Editor display format, not the stored database value.

Use case:
Our database correctly stores timestamps as timestamptz/UTC, but when manually inspecting records in Table Editor, it is difficult to read operational data because our team works in Korea Standard Time, UTC+9.

Expected behavior:
A dashboard-level or project-level preference like:

"Display timestamps in: UTC / Local browser timezone / Custom timezone"

Even just an option to display timestamps in the browser's local timezone would solve most of the problem.

Example:

Current display in Table Editor:

2026-06-12 07:00:01+00

If the display timezone is set to UTC+9 / Asia/Seoul, the same timestamptz value should be displayed as:

2026-06-12 16:00:01+09

The underlying stored value should remain the same. Only the Table Editor display format should change.

This would make debugging logs, daily stats, user activity, and scheduled job records much easier without changing database data.

Thank you.

[harrysun2006]

This is a genuinely useful quality-of-life request — inspecting timestamptz data in UTC when your team lives in KST is a constant little friction, and since you're only asking to change the display, not the stored value, it's a safe scope.

For now the Table Editor always renders timestamptz in UTC with no display-timezone option, so the practical workaround is to inspect via the SQL Editor (or a view) with an explicit conversion:

select
  id,
  created_at,
  created_at at time zone 'Asia/Seoul' as created_at_kst
from your_table
order by created_at desc;

at time zone 'Asia/Seoul' gives you the local wall-clock value for reading, while the stored column stays UTC. If your team inspects the same tables a lot, wrapping that in a view (..._local) makes it a one-click thing in the Table Editor.

That's clearly clunkier than a display preference, though. A dashboard/project-level "display timestamps in: UTC / browser local / custom TZ" toggle is a clean, low-risk feature (display-only, no data change), and "just use the browser's local timezone" alone would cover most of the pain. Worth keeping as a Feature Request and upvoting — it's the kind of small Studio improvement that helps basically everyone outside UTC.

[yakubka]

This is a reasonable UX request and the workaround until a dashboard setting exists is straightforward.

For display purposes you can create a view that casts your timestamptz columns to your local timezone. For example:

CREATE VIEW orders_kst AS
SELECT
  id,
  created_at AT TIME ZONE 'Asia/Seoul' AS created_at_kst,
  amount
FROM orders;

The Table Editor will show that view, and the timestamps will display in KST while the underlying table still stores UTC. The stored value is never changed, so queries from your application that read the base table are unaffected.

A second option if you do not want to create views for every table is to use a generated column:

ALTER TABLE orders
ADD COLUMN created_at_kst timestamptz GENERATED ALWAYS AS (created_at AT TIME ZONE 'Asia/Seoul') STORED;

Neither of these replaces a proper dashboard-level timezone preference, but they make the Table Editor readable right now without waiting for that feature. I would suggest adding this as a GitHub issue with a link back to this discussion so it gets tracked on the roadmap.