How to Manage .kmindz Mind Map Files in Obsidian
The point of .kmindz files is to make maps real vault files that can be organized, synced, backed up, and kept for the long term.
Key takeaways
- Store .kmindz files near the vault topics they support.
- Use Markdown for detail and maps for structure.
- Let your vault sync, backup, and version habits cover map files too.
Folder structure
If your vault is already organized by project, area, or topic, .kmindz files should follow that structure. Avoid putting every map into a temporary dump folder unless that folder is intentionally your map index.
The simplest rule is contextual ownership: put the map near the subject it explains. Search, moves, and archive work all become easier later.
Name maps for future you
A map filename should describe the topic, not the moment it was created. `product-roadmap.kmindz` will age better than `new-map-3.kmindz`.
If your Obsidian system already uses dates, project IDs, or PARA folders, let .kmindz files follow the same convention.
- Use topic, project, or durable task names.
- Avoid draft, test, and new-map names for long-lived files.
- Keep related Markdown notes, assets, and .kmindz files close together.
How maps and Markdown divide the work
Maps are strong at branches, dependencies, priorities, and relationships. Markdown is stronger for evidence, quotes, long explanations, and continuous writing.
A good vault workflow does not force everything into the map. The map becomes a structure layer that helps you return to detailed notes.
Related resources
See plugin capabilities and pricing.
Open KMind Zen on the official Obsidian community plugin page.
Understand the long-term file boundary.
Track releases, installation notes, and technical issues.
FAQ
Should .kmindz files live inside the vault?
Yes, when using the Obsidian plugin. That lets your normal sync, backup, and folder organization apply.
Should .kmindz replace Markdown notes?
No. Use maps for structure and relationships; use Markdown for detailed writing and source material.