Export / import (PDF, Markdown)

You can export notes to external formats and import external Markdown.

• Export: PDF (for printing/sharing) or Markdown (to take notes into other tools). Markdown export adds YAML frontmatter (title / tags / created / updated / pinned / archived) and keeps heading levels H1–H6. Charts export as their underlying data table, diagrams as ```mermaid, math as $$…$$, callouts as `> [!type]`, and video/audio/embeds as links — nothing is silently dropped (it round-trips back on import).
• Import: convert an existing Markdown file, or a folder of Markdown files, into monthlet notes. For folder import, turn on "Keep file names" to convert without renaming by the content title — handy for keeping date-style names (e.g. Obsidian YYYY-MM-DD.md → YYYY-MM-DD.html). You can start an import from the sidebar import button, or from an open note's top-right ⋯ menu → Import (it imports into the folder selected in the sidebar; if none is selected, into the open note's folder, otherwise the top of the vault — so a folder with no notes in it yet can be chosen too). On Windows, the import button / Import menu asks you to choose "Import file…" or "Import folder…" (on macOS one dialog lets you pick either a file or a folder).
• Mermaid promotion: when imported Markdown contains a ```mermaid flowchart (flowchart / graph) or mindmap, it is automatically converted into a diagram block, carrying over node shapes (rectangle, rounded, diamond, circle) and edge labels. Unsupported syntax (e.g. sequence diagrams) is imported safely as a code block.
• Callout promotion: Obsidian callouts such as `> [!note]` / `[!tip]` / `[!warning]` / `[!danger]` are converted into matching callout blocks (when the title is omitted, the type name becomes the title). Plain blockquotes (`>`) are imported as quote blocks as before.
• List import: nested (indented) lists are flattened. Each child item becomes its own item in the same list, indented with a full-width space, so the hierarchy is not kept but no text is lost. Checklist children keep their checked state. A list that mixes tasks (- [ ] / - [x]) with plain items becomes one checklist, with the plain items unchecked.
• Wikilink resolution: Obsidian `[[Note]]` / `[[Note|alias]]` links are turned into monthlet internal links (click to open that note) by matching the name against the imported notes and your existing notes. Folder import also resolves cross-links within the folder. Links to notes that are not found are kept as `[[...]]`. `[[Note#Heading]]` drops the heading anchor and links to the note itself.
• Embed import: Obsidian embeds such as `![[image.png]]` / `![[clip.mp4]]` / `![[audio.mp3]]` copy the attachment file from the source into the note’s folder and display it as an image / video / audio block. Non-media attachments (e.g. PDF) become a clickable link. `![[Note]]` (note embeds) fall back to an internal link, since monthlet has no transclusion block (same resolution as wikilinks above). If the attachment cannot be found or copied, it still becomes the same image / video / audio block (or link for non-media) and is counted as a missing reference in the import result, so you can relink it from the note’s attachment bar.
• Missing references: The import result may show a count of missing references (images and similar). The notes themselves were imported, but files their body points to are not present in the destination. The usual cause is that the file is not anywhere under the source folder (both Obsidian embeds such as `![[image.png]]` and standard `` references are counted the same way). Open the note and the attachment bar at the bottom marks them as not found, so you can relink from there.
• Math import: a standalone `$$ … $$` block becomes a math block rendered beautifully with KaTeX. Inline `$ … $` mixed into text is also rendered as math. Currency like `$5` is not treated as math.
• Unknown frontmatter keys are preserved: keys other than title / tags / created / updated / pinned / archived (e.g. Obsidian’s status, aliases, related, cssclass) are not discarded on import and are written back out when you export to Markdown, so a round trip keeps your metadata. Flat values, booleans and lists (arrays) are supported. A `[[Note]]` written in something like related is kept verbatim as text (links inside frontmatter are not turned into internal links).