Markdown Export

Markdown export produces a .md file containing your note's content in plain text markdown format. It's the most portable of all the export options — a markdown file opens in virtually any text editor, note-taking app, or version control system.

What makes this different from copying the editor

You might wonder: why export to Markdown when you can just copy the text from the editor? The key difference is figures.

In the editor, figures appear as tags like <figure slug="my-figure" />. These are specific to Accessible Notes — another app won't know what to do with them.

In the Markdown export, every figure tag is replaced with the actual image wrapped in a <figure> element with your alt text and caption:

<figure>
  <img src="data:image/png;base64,..." alt="Description of the figure" />
  <figcaption>Visible caption</figcaption>
</figure>

This means the exported file contains your complete document — content and visuals together — in a format that works anywhere that supports markdown with embedded HTML.

What you get

• Figures embedded as images. Each figure tag is replaced with an embedded image, alt text, and caption.
• Math notation preserved. Mathematical expressions stay in LaTeX format ($...$ for inline, $$...$$ for display). Apps like Obsidian, Typora, and many others render these natively.
• Callout blocks in GitHub-style syntax. Notes, warnings, and tips from your document use the widely-supported GitHub syntax:

  > [!NOTE]
  > This is an informational note.
  

• No proprietary syntax. The output is standard markdown — no Accessible Notes-specific placeholders remain.

Best uses

Markdown works best when you want a document that:

• Will be used in another markdown-based tool (Obsidian, Notion, Typora, Bear, etc.)
• Should be stored in version control alongside code or other text files
• Needs to be portable and readable without special software
• Will be processed by scripts, static site generators, or documentation tools