Format timestamp as UTC time: timestamp_utc

The timestamp_utc filter formats a UNIX timestamp as a datetime string in UTC (Coordinated Universal Time). It returns the date and time in the standard ISO-like format, without any local time zone conversion.

This is useful when you need to display or log times in UTC, share timestamps with external services that expect UTC, or compare times across different time zones without ambiguity. If you want the local time representation instead, use timestamp_local. If you need a custom format, use timestamp_custom with the local_time parameter set to false.

Usage

Here’s how to use this template function. Copy any example and adjust it to your setup.

{{ 1710510600 | timestamp_utc }}

2024-03-15 13:30:00+00:00

Function signature

The signature is a technical summary of this template function. It shows the name of the function, the values (called parameters) it accepts, and what type of data each parameter expects (for example, a piece of text or a number).

Function parameters that have a = with a value after them are optional. If you leave them out, the default value shown is used automatically. Function parameters without a default are required.

value | timestamp_utc(
    default: Any = None,
) -> str | Any

Function parameters

The following parameters can be provided to this filter.

Using a default value

If the input might not be a valid timestamp, provide a default to avoid errors.

{{ "invalid" | float(0) | timestamp_utc(default="unknown") }}

unknown

Good to know

• The input must be a UNIX timestamp (a number of seconds). Pass a datetime object through as_timestamp first.
• The result is a string, not a datetime object.
• Without a default, the filter raises an error for non-numeric inputs.

Try it yourself

Ready to test this? Open Developer tools > Template, paste the example into the Template editor, and watch the result update on the right. Edit the values to see how the function adapts to your own entitiesAn entity represents a sensor, actor, or function in Home Assistant. Entities are used to monitor physical properties or to control other entities. An entity is usually part of a device or a service. [Learn more].

More examples

Real scenarios where this function comes up in automations and templates. Copy any example and adapt it to your setup.

Display a sensor timestamp in UTC

Convert the last changed timestamp of an entity to a UTC datetime string.

{{ as_timestamp(states.sensor.temperature.last_changed) | timestamp_utc }}

2024-03-15 13:30:00+00:00

Compare local and UTC representations

Display the same timestamp in both local and UTC format to see the difference.

{% set ts = as_timestamp(now()) %}
Local: {{ ts | timestamp_local }}
UTC: {{ ts | timestamp_utc }}

Local: 2024-03-15 14:30:00+01:00
UTC: 2024-03-15 13:30:00+00:00

Log an event time in UTC

Use UTC timestamps in automationsAutomations in Home Assistant allow you to automatically respond to things that happen in and around your home. [Learn more] for consistent logging regardless of time zone.

action:
  - action: notify.log
    data:
      message: >
        Event occurred at
        {{ as_timestamp(now()) | timestamp_utc }}

Still stuck?

The Home Assistant community is quick to help: join Discord for real-time chat, post on the community forum with your template and expected result, or share on our subreddit /r/homeassistant.

Related template functions

These functions work well alongside this one:

• Format timestamp as local time: timestamp_local - Formats a UNIX timestamp as a local datetime string.

• Format timestamp with custom format: timestamp_custom - Formats a UNIX timestamp as a string using a custom format.

• Convert to UNIX timestamp: as_timestamp - Converts a datetime object or string to a UNIX timestamp.

• Current UTC date and time: utcnow - Returns the current date and time in UTC.