2026.10.4
Home ▸ Template functions

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 parameter set to false.

Usage

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

As a filter 
{{ 1710510600 | timestamp_utc }}
Result (stringA piece of text, like a name, message, or entity ID. In templates, wrap strings in quotes, like "living_room" or "lights are on".) 
2024-03-15T13:50: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 = are usually required. A few optional parameters have no default value, so the signature shows them without a = as well. To check whether a parameter is required, look at the parameter list below the signature. Each parameter is marked as Required or Optional.

The most common optional parameter without a default value is default. The default parameter sets the value a function returns when the function can’t produce a result, for example, when float gets text that isn’t a number. If you leave out default, there is no fallback value, so most functions raise an error and the template fails. The parameter list of each function says what happens. If you set default, the function returns your value instead.

How to read a signature

Here is the signature of the round filter as an example:

round(
    value: Any,
    precision: int = 0,
    method: str = "common",
    default: Any,
) -> float | int | Any
  • round is the name of the function.
  • Between the parentheses are the parameters. Each parameter has a name, followed by a colon and the type of value the parameter expects. The type only tells you what kind of value to pass. For default: Any, you pass a value of any type, such as 0 or "unknown", not the word Any.
  • = 0 and = "common" are default values. You can leave out precision and method, and round uses these default values.
  • default has no =, but the parameter list marks default as optional. If you leave out default and round gets a value that isn’t a number, round raises an error.
  • -> shows the type of value the function returns.
  • Inside a signature, | means “or”. This function returns a decimal number, a whole number, or the value you passed as default.

round is a filter, so the first parameter, value, is the value before the |. For example, {{ 3.14159 | round(2) }} returns 3.14.

The types you’ll see most often:

  • str: text, such as "hello"
  • int: a whole number, such as 5
  • float: a decimal number, such as 3.14
  • bool: true or false
  • list: a list of values, such as [1, 2, 3]. list[str] is a list of texts.
  • dict: a set of keys and values, such as {"name": "Kitchen"}
  • datetime and timedelta: a date and time, and a duration. For details, refer to Dates and times.
  • None: no value
  • Any: any type of value

Some signatures use special forms:

  • *args means you can pass any number of values, separated by commas. For example, average(1, 2, 3).
  • value | name(...) means the function is a filter. The value before the | is passed to the filter as its first parameter. Some filter signatures, like the round example, show this value as the first parameter between the parentheses instead.
value | timestamp_utc(
    default: Any,
) -> str | Any

Function parameters

The following parameters can be provided to this filter.

default any (Optional)

The value to return if the formatting fails, such as "unknown". If you leave out default and the formatting fails, timestamp_utc raises an error and the template fails.

Using a default value

If the input might not be a valid timestamp, provide a default to avoid errors. float(none) turns invalid text into none, so the default is used.

TemplateA template is an automation definition that can include variables for the action or data from the trigger values. This allows automations to generate dynamic actions. [Learn more] 
{{ "invalid" | float(none) | timestamp_utc(default="unknown") }}
Result (stringA piece of text, like a name, message, or entity ID. In templates, wrap strings in quotes, like "living_room" or "lights are on".) 
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.
  • The input must be a number, not text. A numeric string such as "1700000000" fails too. Convert states with float or int first.
  • Without a default, the filter raises an error if the input isn’t a number.

Try it yourself

Ready to test this? Open Settings > 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.

TemplateA template is an automation definition that can include variables for the action or data from the trigger values. This allows automations to generate dynamic actions. [Learn more] 
{{ as_timestamp(states.sensor.temperature.last_changed) | timestamp_utc }}
Result (stringA piece of text, like a name, message, or entity ID. In templates, wrap strings in quotes, like "living_room" or "lights are on".) 
2024-03-15T13:30:00+00:00

Compare local and UTC representations

Display the same timestamp in both local and UTC format to see the difference. This example uses a time zone of UTC+1.

TemplateA template is an automation definition that can include variables for the action or data from the trigger values. This allows automations to generate dynamic actions. [Learn more] 
{% set ts = as_timestamp(now()) %}
Local: {{ ts | timestamp_local }}
UTC: {{ ts | timestamp_utc }}
Result (stringA piece of text, like a name, message, or entity ID. In templates, wrap strings in quotes, like "living_room" or "lights are on".) 
Local: 2024-03-15T14:30:00+01:00
UTC: 2024-03-15T13: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.

ActionAn action makes Home Assistant do something, for example, turn on a light, send a notification, or activate a scene. Automations and scripts run a list of actions. [Learn more] 
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.

Tip

AI assistants like ChatGPT or Claude can also explain or fix templates when you describe what you want in plain language.

Related template functions

These functions work well alongside this one: