Links
Introduction
Obsidian stores notes as Markdown files. Its flavor adds wikilinks, callouts, embeds, properties, and other syntax on top of CommonMark and GFM.
- Obsidian Help (help.obsidian.md)
- Obsidian Flavored Markdown (help.obsidian.md)
Wikilinks
[[Note]]
[[Projects/Launch]]
[[Note|Alias]]
Links resolve by file name without an extension; folder paths start at the vault root. The pipe sets the display text.
See: Internal links
Link to headings
[[#Heading]]
[[Note#Heading]]
[[Note#Heading#Details]]
One # targets a heading in the current note; repeat it for each nested level.
See: Internal links
Markdown links and URIs
[Launch](Projects/Launch%20plan.md)
[Note](obsidian://open?vault=MainVault&file=Note.md)
Markdown links work too; encode spaces as %20. An obsidian:// URI can open a note in another vault.
Callouts
Basic callout
> [!note] Release notes
> Version 1.15 is out.
> Supports **bold** and [[Note]].
A callout is a blockquote whose first line is [!type]; text after the type is the title.
See: Callouts
Foldable callouts
> [!tip]- Details
> Collapsed by default.
> [!warning]+ Caution
> Expanded by default.
+ starts expanded, - starts collapsed.
See: Callouts
Nested callouts
> [!question] Why nest?
> > [!todo] To group related notes.
> > > [!example] Up to many levels.
Each quote level adds one callout layer.
See: Callouts
Callout types
| Type | Aliases |
|---|---|
note | — |
abstract | summary, tldr |
info | — |
todo | — |
tip | hint, important |
success | check, done |
question | help, faq |
warning | caution, attention |
failure | fail, missing |
danger | error |
bug | — |
example | — |
quote | cite |
Unknown types fall back to note; type names are case-insensitive.
See: Callouts
Embeds and blocks
Embed a note
![[Note]]
The ! prefix renders the linked file inline; edits to the source show up here.
See: Embed files
Embed headings and blocks
![[Note#Heading]]
![[Note#^id]]
Append #Heading or #^id to embed just that section or block.
See: Embed files
Embed images and PDFs
![[image.png]]
![[image.png|320x200]]
![[Document.pdf#page=3&height=400]]
Width-only sizing keeps the aspect ratio; PDFs accept #page=N and #height=N.
See: Embed files
Block identifiers
The key decision. ^id
> A quote worth keeping.
^quote-of-the-day
Put ^id at the end of a paragraph, or on its own line after a structured block. IDs allow letters, digits, and dashes.
Reference it with [[Note#^id]] or embed it with ![[Note#^id]].
See: Internal links
Properties and tags
YAML properties
---
title: Launch plan
aliases: []
tags:
- project
- planning
due: 2026-11-30
done: false
---
Properties are YAML at the top of a note. Each name must be unique in that note.
See: Properties
Default properties
| Property | Type | Purpose |
|---|---|---|
aliases | List | Alternate names |
tags | List | Note tags |
cssclasses | List | Note styling |
Other names get a type on first use; the type is shared vault-wide.
See: Properties
Tags in text
#meeting #tag/subtag #Project_Apollo
Tags allow letters, digits, _, -, and / (nesting), but no spaces. They are case-insensitive.
See: Tags
Tags as properties
---
tags:
- journal
- personal
---
Property tags work like inline tags; tag:inbox also matches nested tags.
See: Properties
Tasks
Checkboxes
- [ ] task
- [x] Write draft
- [ ] Add citations
List items starting with [ ] become checkboxes; indent to nest subtasks.
Custom statuses
- [x] Milk
- [?] Eggs
- [-] Skydiving
Any character inside the brackets counts as complete, while [ ] stays open.
Formatting
Highlights
==highlight==
==🔴 Urgent==
Six color emojis tint a highlight: 🔴 🟠 🟡 🟢 🔵 🟣; otherwise the theme color is used.
Comments
Visible %%comment%% text.
%%
A block comment can span lines.
%%
Comments hide in Reading view. An unclosed block comment hides the rest of the note.
Footnotes
Reference footnotes
A claim with a note.[^note]
[^note]: Source text.
Continues on the next line.
Inline footnotes
A claim with a note.^[Inline source text.]
Inline footnotes render in Reading view only.
0 Comments for this cheatsheet. Write yours!