Timeline Template Obsidian: How to Build a Timeline in Your Notes
8 min read ยท 2026-10-10
A timeline template obsidian setup works best as one small note template for events, with a date property on each event. Every event becomes its own note. Then you show all of those notes in date order. You can do that with a core feature like Bases, with a community plugin like Dataview, with a timeline plugin, or with a Mermaid Gantt chart written straight into a note.
This setup works for a project history, a product launch, a study plan, a story you are writing or your own life events. The roadmap below takes you from an empty vault to a working timeline in about a week of short sessions. After that, keeping it up to date takes a few minutes each week. If you would rather see your phases and milestones laid out visually before you build anything, generate your roadmap with AI (first one free), then copy the structure into your vault.
The roadmap at a glance
Goal: A reusable timeline in Obsidian that updates itself when you add a new event note. Duration: About 1 week to set up, then a few minutes per week to maintain.
Decide what your timeline is for (Day 1, 30 minutes)
Pick one use case so your properties stay simple.
- Write one sentence on what the timeline should answer, for example "What happened on this project, and when?"
- Choose the time scale: days, weeks, months or years.
- List the 3 to 5 pieces of information each event needs, such as date, title, type and status.
- Decide whether events have one date or a start date and an end date.
Milestone: A short note called Timeline plan that lists your use case, time scale and properties.
Create the event note template (Day 1, 45 minutes)
Make every new event note look the same.
- Turn on the core Templates plugin and pick a folder for templates.
- Create a note called Event template with properties such as date, end, type and status.
- Add a short body: a heading for what happened, one for why it matters, one for links to related notes.
- Use the {{date}} variable so new events start with today's date, and change it when needed.
Milestone: You can create a new event note from the template in under a minute.
Add your first events (Days 2 to 3, 1 hour)
Give the timeline enough data to be useful.
- Create a folder called Events, or add a tag such as #event to each event note.
- Add 10 to 20 past events, oldest first, so you can spot gaps.
- Use one date format everywhere: YYYY-MM-DD.
- Link each event to the project, person or topic note it belongs to.
Milestone: Your Events folder holds at least 10 notes, each with a valid date property.
Show the timeline (Day 4, 1 hour)
Display all events in date order inside one note.
- Create a note called Timeline.
- Add a sorted view using Bases, Dataview, Mermaid or a timeline plugin (see the next section).
- Check that every event appears and that the order is right.
- Fix any note whose date shows up empty or out of order.
Milestone: Opening the Timeline note shows every event, sorted by date.
Add future events and milestones (Day 5, 30 minutes)
Turn the history into a plan.
- Add upcoming events with a status of planned.
- Mark the 3 to 5 events that really matter with a type of milestone.
- If your view allows it, filter or color planned and done events differently.
Milestone: The timeline shows both past and planned events, with milestones easy to spot.
Keep it alive (Week 2 onwards, 10 minutes per week)
Make sure the timeline stays accurate.
- Add a weekly review note with a link to the Timeline note.
- Change planned events to done, and move dates that slipped.
- Archive or delete events that no longer matter.
Milestone: Four weekly reviews in a row with an up to date timeline.
Four ways to display a timeline in Obsidian
Obsidian has no single built in timeline view, so you choose how to display your event notes. Your notes and template stay the same with Bases, Dataview and Mermaid, so you can start simple and switch later between them.
Here are the four common options:
For most people, Bases or Dataview is the right starting point. They read your notes automatically, so a new event shows up as soon as you create it. Use Mermaid when you need a picture for a meeting. Use a timeline plugin when the visual layout matters every day, as with a story or a research history.
- Bases (core plugin): create a base that filters notes from your Events folder or with your #event tag, then sort by the date property. You get a clean table with no code, and you can edit properties right in the view.
- Dataview (community plugin): write a short query in a Dataview code block, for example TABLE date, type, status FROM #event SORT date ASC. This is flexible and handy if you already use Dataview elsewhere.
- Mermaid Gantt chart (built in): Obsidian renders Mermaid diagrams in a mermaid code block. Start with the word gantt, set dateFormat YYYY-MM-DD, add a section per phase, then one line per task with a start date and a length, such as Research :2026-01-05, 14d. This is the most visual option, but you update it by hand.
- Timeline plugins (community): several community plugins draw a visual timeline from your notes. Each plugin has its own way of reading dates, so read its documentation and adapt your notes to it before you add many events.
How to set up the event template step by step
Your template is the base of everything. Keep the properties short and consistent, because every view depends on them. A simple version uses five properties:
To build it, open the Templates folder, create a note called Event template and add these properties through the Properties panel. Set date as a Date property type. Obsidian then shows a date picker and stores the value in the right format. Under the properties, add three short headings: What happened, Why it matters and Related notes.
If you use the Templater plugin instead of the core Templates plugin, you can go further. For example, Templater can ask for the event title when you create the note, or move the note into the Events folder for you. This is optional. The core Templates plugin is enough for a working timeline.
A quick tip: name event notes with the date first, such as 2026-03-14 Beta launch. Your file list then sorts in date order even without a view, which helps when you scan the folder.
- date: when the event starts.
- end: for multi day events. Leave it empty if there is none.
- type: a value like event or milestone.
- status: a value like planned or done.
- project: a link to the main note.
Examples of timelines you can build
The same template covers very different needs. Only the properties and the time scale change. Here are four setups that work well.
If your timeline is really a plan for the future, with phases and goals, you are building a roadmap. In that case, lay out the phases first, then create one event note per milestone. You can generate your roadmap with AI (first one free) and use its phases, steps and milestones as the starting list of notes in your vault. For the method behind a good plan, read our guide on how to make a roadmap.
- Project timeline: one note per meeting, decision, release or delay. Use the project property to filter one project at a time, and status to separate what is done from what is planned.
- Learning timeline: one note per course module, book or practice project. Add a property for hours spent or a link to your study notes, and mark exams or certifications as milestones.
- Story or worldbuilding timeline: one note per scene or historical event in your world. A visual timeline view helps here, because writers need to see the order of events at a glance.
- Personal life timeline: one note per move, job change, trip or important moment. Use years as the time scale, and keep the body short so the habit stays easy.
When a timeline in your notes is enough, and when it is not
A timeline inside Obsidian is great for personal knowledge. It lives next to your notes, links to them and costs nothing extra. It is private, works offline and grows with your vault.
It has limits when other people need to see or change the plan. Sharing a vault with a team takes extra setup. Moving phases around means editing dates in several notes. A Mermaid chart has to be updated by hand each time. For a team plan that changes often, a visual roadmap you can adjust by drag and drop is usually faster to keep up to date. Not sure which one you need? Our comparison of a roadmap vs a project plan explains the difference.
Many people use both. The visual roadmap shows the big picture: phases, steps and milestones. Obsidian holds the detail: meeting notes, decisions and lessons learned, each linked to the right milestone. If you want a ready structure to start from, browse our roadmap templates.
Once your template works, the hard part is knowing which phases and milestones to plan. If you start from a blank page, generate your roadmap with AI (first one free) and turn each milestone into an event note. For more pitfalls that apply to any plan, see our list of 12 roadmap mistakes to avoid.
Common mistakes to avoid
- Mixing date formats such as 03/14/2026 and 2026-03-14 breaks sorting. Set date as a Date property type and use YYYY-MM-DD everywhere.
- Adding too many properties makes every new note feel like a form. Start with five and add one only when a view needs it.
- Writing all events in one long note stops queries from reading them. Give each event its own note.
- Installing a timeline plugin without checking how it reads dates can leave you with an empty view. Read the plugin documentation first and test it on a few notes before you adapt the rest.
- Building the timeline and never opening it again lets it go stale. Link it from a weekly review note and spend 10 minutes updating it.
- Marking every event as a milestone hides the ones that matter. Keep milestones to the few dates that change what you do next.
Frequently asked questions
Does Obsidian have a built in timeline view?
No, Obsidian has no dedicated timeline view out of the box. You can get close with core features: Bases sorts your event notes by date, and Mermaid Gantt charts draw a visual timeline inside a note. For a true timeline layout, look for a community timeline plugin and check its documentation to see how it reads dates.
What is the best timeline template for Obsidian?
The best template is the simplest one: a note with a date property, an optional end date, a type and a status. Keep the same property names in every event note. That template works with Bases and Dataview. If you add a timeline plugin, check its documentation, because each plugin reads dates in its own way.
Can I make a Gantt chart in Obsidian?
Yes. Obsidian renders Mermaid diagrams, and Mermaid supports Gantt charts. Write gantt as the first line of a mermaid code block, set the date format, then add sections and tasks with a start date and a length. The chart does not update by itself, so it fits plans that change rarely.
How do I sort notes by date in Obsidian?
Give each note a date property, then build a view that sorts on it. In Bases, add a sort on the date property. In Dataview, end your query with SORT date ASC. Starting file names with the date also keeps your file list in order.