Skip to main content
idapt
HomeCodeAI ModelsPricing
Sign inStart free
  • Home
  • Pricing
  • AI Models
  • Image models
  • Voice models
  • Video models
  • Rankings
  • New models
  • Model status
  • Multi-Model Chat
  • Agents
  • Computers
  • Drive
  • Automations
  • AI Gateway
  • All features β†’
  • LLM cost calculator
  • Token counter
  • All free tools β†’
  • Blog
  • Use cases
  • Comparisons
  • Best of
  • Benchmarks
  • Demos
  • Changelog
  • Help center
  • FAQ
  • Privacy
  • Compare all models
  • Support
  • idapt Code
  • Developers
  • Quickstarts
  • API reference
  • API pricing
  • CLI
  • MCP
  • Downloads
  • Desktop
  • Badges and embeds
Β© idapt[email protected]TermsPrivacy PolicyLegal noticeReport content
X (Twitter)
Help Center
πŸ“

Import markdown notes

Found this helpful? Share it:

Bring your Obsidian vault or Notion export into the Knowledge Base. Point the importer at a folder of markdown files and your notes, folders, and links come over together πŸ“

Importing draws on your Knowledge quota, which is separate from Drive storage and runs from 10 MB on Free to 5 GB on Max. See What is the Knowledge Base? for the full ladder.

Import a folder of notes

  1. Open the Knowledge tab in your workspace.

  2. Click Import folder in the sidebar header, or go to Settings β†’ Import and choose Markdown folder β†’ Knowledge. Then pick a folder of markdown or text files.

  3. The folder tree is recreated inside the Knowledge Base as folders and notes.

Works with Obsidian and Notion

An Obsidian vaultimports as-is. Wikilinks resolve across the whole Knowledge Base, so a [[link]] finds its note no matter which folder either file sits in. Backlinks and the graph light up as soon as the import finishes.

Notion's Markdown exportworks the same way: unzip it, then import the folder.

How files are named

  • Markdown files(.md, .markdown) import under their filename with the extension dropped, so Roadmap.md becomes a note titled Roadmap.

  • Other text files import as basename_<ext>, so readme.txt becomes a note titled readme_txt. This keeps a notes.md and a notes.txt from fighting over the same title.

  • Duplicate titles are auto-suffixed, never skipped. Two files that would land on the same title both import, and the second gets a numbered suffix. Nothing is dropped for having a name twice.

What is skipped, and the caps

Only text files import. Any file without an importable text extension, like an image, a PDF, or another binary, is skipped. Upload those to your Drive instead.

Two size caps apply to an import:

  • 256 KB per note: a single file larger than this is not imported.

  • 2,000 notes per workspace: an import that would push the Knowledge Base past this is refused.

The caps and your Knowledge quota are checked up front, and the whole import runs as one transaction. If it would not fit, nothing is written, so you never end up with half a vault.

Export the Knowledge Base

The Knowledge Base exports as a ZIP of markdown files, keyed by folder path, so the structure you see in the workspace is the structure you get back.

That is the same layout the importer accepts, so an export from idapt round-trips cleanly into Obsidian.

Related articles

πŸ“

What is the Knowledge Base?

One Knowledge Base per workspace: markdown notes with folders, wikilinks, tags, and a graph, shared by your team and your agents.

πŸ•ΈοΈ

Wikilinks, backlinks, and the graph

Connect notes with [[wikilinks]], see what links back, tag them, and explore the whole Knowledge Base as a graph.

Up next

Agents remember with Knowledge

How agents use the workspace Knowledge Base as their memory: the injected Index, the knowledge tools, and the toggles that control access.

Was this helpful?