> For the complete documentation index, see [llms.txt](https://help.sdocs.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.sdocs.com/sdocs/advanced-template-logic/template-attributes/template-attributes-how-to-guides/how-to-format-date-and-time-together.md).

# How To: Format Date and Time Together

Show date and time together, including 12-hour, 24-hour, and timezone-aware output.

Use `format-date` with time patterns when your field stores both date and time.

### Problem

You need to display both date and time, potentially in a specific timezone.

### Solution

**Basic Date and Time:**

```
{{!Opportunity.Created_DateTime__c format-date="MM/dd/yyyy hh:mm:ss a"}}
```

**Result:** `10/28/2024 02:30:45 PM`

**24-Hour Format:**

```
{{!Opportunity.Created_DateTime__c format-date="MM/dd/yyyy HH:mm:ss"}}
```

**Result:** `10/28/2024 14:30:45`

**With Timezone:**

```
{{!Opportunity.Created_DateTime__c format-date="MM/dd/yyyy hh:mm:ss a TZ:America/New_York"}}
```

**Result:** `10/28/2024 02:30:45 PM EST`

### Time Pattern Reference

| Pattern | Meaning      | Example |
| ------- | ------------ | ------- |
| `HH`    | Hour (00-23) | 14      |
| `hh`    | Hour (01-12) | 02      |
| `mm`    | Minutes      | 30      |
| `ss`    | Seconds      | 45      |
| `a`     | AM/PM marker | PM      |

### Common Timezones

```
America/New_York
America/Chicago
America/Denver
America/Los_Angeles
America/Phoenix
Europe/London
Europe/Paris
Asia/Tokyo
Australia/Sydney
```

### Tips

* Times default to GMT unless you set a timezone.
* Use Java timezone codes only.
* Salesforce-supported timezones work best.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.sdocs.com/sdocs/advanced-template-logic/template-attributes/template-attributes-how-to-guides/how-to-format-date-and-time-together.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.