Skip to content
TheChatArchiveThe Chat Archive
o3-mini· OpenAIHugging Face LMArena Human Preference 140K

How can I insert a timestamp in obsidian (I have these extensions: dataview, tasks and…

From a Chatbot Arena battleThe same person sent this prompt to two anonymous models at once. Compare it with grok-3-preview-02-24’s answer.
  1. User

    How can I insert a timestamp in obsidian (I have these extensions: dataview, tasks and others)

  2. Assistant

    There are several ways to “insert a timestamp” in Obsidian depending on what you need it for. For example, you might want a static timestamp in your note, a dynamically generated one via a template, or even a date field that Dataview and Tasks can query. Here are some common approaches:


    1. Using Obsidian’s Built-In Commands

    Obsidian now includes commands for inserting the current date/time. You can use these as follows:

    • From the Command Palette:
      Press Ctrl+P (or Cmd+P on Mac) to open the Command Palette and search for commands like “Insert current date” or “Insert current time” (the exact name may vary with version).
    • Assigning a Hotkey:
      Go to Settings → Hotkeys and search for “Insert current date” or “Insert formatted date and time.” You can then assign your preferred key combination so you can quickly drop a timestamp at the cursor.

    This method inserts a timestamp exactly as shown. If you need a specific format, you might need to customize it in your operating system’s clipboard (or use a plugin as described next).


    2. Using the Templater Plugin

    If you want more control over the timestamp’s format (or to insert it automatically when creating new notes), Templater is a popular choice. For example:

    1. Install and Enable Templater:
      Open the Community Plugins pane in Obsidian, search for “Templater,” and install it.

    2. Create a Template File:
      In your templates folder, make a file (e.g., New Note Template.md) with contents like:

      # <% tp.file.title %>
      Created on: <% tp.date.now("YYYY-MM-DD HH:mm") %>
      

      (Adjust the date format as needed.)

    3. Use the Template:
      You can either have a new note created with the template (using Obsidian’s template command) or manually insert the template snippet where needed.

    This way, when you create a new note or insert the template, Templater will generate a timestamp in the format you specify.


    3. Integrating with Dataview and Tasks

    If your goal is to have a timestamp that other plugins (like Dataview or Tasks) can recognize as a date, consider these pointers:

    • YAML Front Matter Timestamps:
      Include a date in the YAML front matter of your note. For example:

      ---
      created: 2023-10-02 14:30
      ---
      

      Dataview will automatically recognize and parse this if you use functions like date(created) in your queries.

    • Task Metadata:
      If you’re using the Tasks plugin and you need to schedule or set due dates, you can annotate tasks like:

      - [ ] Example task  
        due:: 2023-10-05
      

      (Make sure the date format matches what Tasks expects, usually YYYY-MM-DD.)

    • Inline Dataview Queries:
      If you want to show a timestamp dynamically in your note, you could use an inline DataviewJS snippet:

      dv.span(`Current time: ${window.moment().format("YYYY-MM-DD HH:mm")}`)
      

      This snippet will render the current time in your note whenever the dataview is refreshed.


    Summary

    • For a simple timestamp insertion: Use Obsidian’s built-in commands (accessible via the Command Palette or hotkeys).
    • For custom formatted or automatic timestamps: Use a template with the Templater plugin (e.g., <% tp.date.now("YYYY-MM-DD HH:mm") %>).
    • For tasks and Dataview integration: Use standard date entries in YAML or inline fields (e.g., created: 2023-10-02 14:30 or due:: 2023-10-05).

    Pick the method that best fits your workflow. If you run into any issues or need further customization, the Obsidian community forum is also a great resource for tips and tricks!

Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.