Limits on Regional Time Zone Support in Blender’s Render File Path Placeholders

Blender’s Render Properties panel allows the use of strftime‑style placeholders such as %Y, %m, %d, %H, %M, and %S in the output file path. When a render is executed, these tokens are expanded by the internal C library call to localtime(), which reflects the host machine’s configured time zone.

Because the expansion is tied directly to the system clock, there is no exposed UI control or script API to specify an alternative time zone or to force UTC. Consequently, rendering the same scene on two machines set to different zones will produce file names with divergent timestamps, even though the render event itself is identical.

This lack of time‑zone configurability poses a challenge for distributed rendering pipelines and archival workflows that rely on consistent, time‑zone‑agnostic file naming.

Questions for further investigation:

• Does Blender’s current release (2.93 and later) provide any hidden or experimental flags to override the localtime() behavior for file path placeholders?
• Would a future update to the Render Properties panel include a dedicated time‑zone selector for placeholder expansion?
• What best‑practice workflow can developers adopt to standardize timestamps across multi‑region rendering setups?