Add Option to Group and Display Photos by Local Time (Instead of UTC) #2432

New issue

Open

opened 2026-02-20 01:11:28 -05:00 by deekerman · 1 comment

deekerman commented

2026-02-20 01:11:28 -05:00

Owner

Originally created by @drumstick93 on GitHub (Oct 30, 2025).

Confirmation

I checked this request against the roadmap and existing issues

What Problem Does This Solve and Why Is It Valuable?

disclaimer: I had the GPT link on photoprisim website helps me try to find a solution and ultimately ended up writing this for me. Hope it make it into an update some time!

PhotoPrism currently normalizes all timestamps to UTC for storage, indexing, and grouping. While this ensures consistency across devices and time zones, it can cause photos taken late in the evening to appear under the next day or even the next month.
For example, a photo taken locally on 2025-09-30 at 23:45 (UTC-4) is stored internally as 2025-10-01 03:45 UTC, which causes it to appear in October rather than September when browsing by month or year.
This behavior is consistent with PhotoPrism’s UTC design, but it’s unintuitive for users who primarily work within a single time zone. Many photographers expect their timelines and folders to follow their local calendar dates, not UTC boundaries.

Problem Summary:
PHOTOPRISM_DEFAULT_TIMEZONE is set correctly and reflected in sidecar YAML files (TimeZone: UTC-4).
The TakenAtLocal field is accurate and matches the camera’s timestamp.
However, the TakenAt field (stored in UTC) crosses into the next day/month for late-evening photos.
Timeline and folder grouping are currently based on the UTC date, not the local date.

What Solution Would You Like?

Add a configuration or settings option such as:
PHOTOPRISM_GROUP_BY_LOCAL_TIME=true
or a UI toggle like “Group photos by local time instead of UTC”, which would cause PhotoPrism’s indexing and timeline views to group photos based on TakenAtLocal rather than TakenAt.

What Alternatives Have You Considered?

No response

Additional Context

Benefits:
Makes date-based browsing intuitive for users who shoot and organize photos within a single region.
Keeps internal UTC consistency while offering flexibility in presentation.
Reduces confusion when late-night photos appear to “move” into the next day or month.
Additional Context:
This behavior has been observed consistently across recent PhotoPrism releases (latest Docker image, MariaDB backend). The sidecar metadata correctly records both TakenAtLocal and TakenAt timestamps, confirming that time zone detection is accurate — the issue lies purely in how grouping is derived.

Originally created by @drumstick93 on GitHub (Oct 30, 2025). ### Confirmation - [x] I checked this request against the roadmap and existing issues ### What Problem Does This Solve and Why Is It Valuable? disclaimer: I had the GPT link on photoprisim website helps me try to find a solution and ultimately ended up writing this for me. Hope it make it into an update some time! PhotoPrism currently normalizes all timestamps to UTC for storage, indexing, and grouping. While this ensures consistency across devices and time zones, it can cause photos taken late in the evening to appear under the next day or even the next month. For example, a photo taken locally on 2025-09-30 at 23:45 (UTC-4) is stored internally as 2025-10-01 03:45 UTC, which causes it to appear in October rather than September when browsing by month or year. This behavior is consistent with PhotoPrism’s UTC design, but it’s unintuitive for users who primarily work within a single time zone. Many photographers expect their timelines and folders to follow their local calendar dates, not UTC boundaries. **Problem Summary:** PHOTOPRISM_DEFAULT_TIMEZONE is set correctly and reflected in sidecar YAML files (TimeZone: UTC-4). The TakenAtLocal field is accurate and matches the camera’s timestamp. However, the TakenAt field (stored in UTC) crosses into the next day/month for late-evening photos. Timeline and folder grouping are currently based on the UTC date, not the local date. ### What Solution Would You Like? Add a configuration or settings option such as: PHOTOPRISM_GROUP_BY_LOCAL_TIME=true or a UI toggle like “Group photos by local time instead of UTC”, which would cause PhotoPrism’s indexing and timeline views to group photos based on TakenAtLocal rather than TakenAt. ### What Alternatives Have You Considered? _No response_ ### Additional Context Benefits: Makes date-based browsing intuitive for users who shoot and organize photos within a single region. Keeps internal UTC consistency while offering flexibility in presentation. Reduces confusion when late-night photos appear to “move” into the next day or month. Additional Context: This behavior has been observed consistently across recent PhotoPrism releases (latest Docker image, MariaDB backend). The sidecar metadata correctly records both TakenAtLocal and TakenAt timestamps, confirming that time zone detection is accurate — the issue lies purely in how grouping is derived.

deekerman added the

idea

label

2026-02-20 01:11:28 -05:00

deekerman commented

2026-02-20 01:11:29 -05:00

Author

Owner

@graciousgrey commented on GitHub (Oct 31, 2025):

Thank you very much for your feedback!

This may be related to:

https://github.com/photoprism/photoprism/issues/4036

@graciousgrey commented on GitHub (Oct 31, 2025): Thank you very much for your feedback! This may be related to: - https://github.com/photoprism/photoprism/issues/4036