MMAP File Documentation

---

Technical details

Feature	Value
Full name	MindManager Map File (mind map)
File extension	.mmap
MIME type	application/vnd.mindjet.mindmanager
Format type	ZIP package of XML + embedded media
Container / base format	ZIP archive
Primary part	Document.xml (MindManager map schema)
Developer	Corel Corporation (originally Mindjet; acquired 2016)
Introduced	MindManager for Windows, late 1990s
Open standard	No (proprietary XML schema)
Byte order	N/A (ZIP + text XML)
Magic number (hex)	50 4B 03 04 (PK) at offset 0
Encryption	Not encrypted by default (compressed only)
Content held	Topics, subtopics, relationships, notes, icons, callouts, task data, attachments
Full-fidelity app	MindManager (Windows, macOS, web/Teams)
Free import	XMind (File → Import → MindManager)
Template extension	.mmpt (MindManager template)
Related extensions	.mmpt, .xmind, .mm, .zip
Specification / info	mindmanager.com/en/pages/mmap-file/

What is an MMAP file?

An MindManager Map File stores a mind map: a central topic surrounded by branching subtopics, with relationship lines, icons, callouts, notes, hyperlinks and task data such as priority, progress and due dates. It is the native format of MindManager, a commercial visual-thinking and diagramming application first built by Mindjet in the late 1990s and acquired by Corel in 2016, so files you see today are Corel MindManager maps even though the .mmap extension predates the acquisition.

The single most useful technical fact about an .mmap is that it is not a monolithic binary. It is a ZIP archive. Everything a map contains, the structure, the styling and any attached files, is packaged inside that archive, with the map itself described in an XML part called Document.xml. That makes the file inspectable without MindManager, even though full visual fidelity only renders correctly in MindManager itself.

The ZIP package: what is really in the file

Rename a copy of an .mmap to .zip, open it, and you find a small file system. The exact members vary by version, but the shape is consistent:

my-map.mmap  (a ZIP archive)
 ├─ Document.xml         the map: topics, links, notes, task data
 ├─ [Content_Types].xml  MIME types of the parts (OPC-style packaging)
 ├─ meta.xml / properties document metadata (author, dates)
 └─ attachments/ images/ embedded pictures, icons and attached files

Because the container is a plain ZIP, the file begins with the local file header signature 50 4B 03 04 (“PK”). That is the same signature used by DOCX, XLSX, JAR, APK and any ordinary ZIP, so the magic bytes alone cannot identify a mind map; you confirm it by seeing Document.xml and MindManager’s XML namespace inside. The archive is compressed but, by default, not encrypted, which is why the old “encoded and compressed/encrypted” description of .mmap is misleading: you can read the XML straight out of the package.

Document.xml: the map as a tree of topics

The heart of the file is Document.xml, which encodes the map as a nested tree in MindManager’s schema. A map has one central topic, and every other topic is a descendant of it, mirroring the visual branches. Each topic element carries the text you see plus its formatting, position, icons, notes and any task attributes.

<ap:Map xmlns:ap="...">
  <ap:OneTopic>
    <ap:Topic>                       <- central topic
      <ap:Text PlainText="Project plan"/>
      <ap:SubTopics>
        <ap:Topic>
          <ap:Text PlainText="Research"/>
          <ap:Task Priority="1" Progress="50"/>
          <ap:Notes>...</ap:Notes>
        </ap:Topic>
        <ap:Topic><ap:Text PlainText="Design"/></ap:Topic>
      </ap:SubTopics>
    </ap:Topic>
  </ap:OneTopic>
  <ap:Relationships> ... </ap:Relationships>
</ap:Map>

Subtopics nest inside a SubTopics element, so the parent/child hierarchy is literally the XML hierarchy. Non-hierarchical connections, the curved relationship lines that link two branches across the map, are stored separately (they cannot be expressed by nesting, since they join arbitrary topics). Task data such as priority and percent complete rides on the topic as attributes or child elements, which is what lets MindManager export a project map’s tasks to Microsoft Project. Notes, callouts, icons and hyperlink targets are all attached to their topic in the same tree, and references to embedded pictures point at the image parts stored elsewhere in the ZIP.

Styles, layout and why fidelity needs MindManager

The XML also records presentation: branch colours, line styles, the map’s layout algorithm, topic shapes and the overall theme. This is where reading the raw Document.xml stops being enough. The schema is proprietary and not openly published, and the precise placement, growth direction and formatting of branches are interpreted by MindManager’s layout engine. Another tool can read the topic tree and text reliably, but reproducing the exact visual arrangement and every MindManager-specific style is another matter. That is the practical reason a map opened elsewhere may simplify some formatting even when all the content survives.

Embedded attachments inside the package

A topic can carry attached files, and those are stored as parts inside the same ZIP: an attached DOCX, a spreadsheet, an image, even a video can live in the archive. This is convenient (the map is self-contained) but has two consequences. First, it explains why an .mmap can be surprisingly large for a diagram: the size is mostly its embedded media. Second, because you can open the package with any ZIP tool, you can extract those attachments directly, without MindManager, when all you need is a file someone embedded in the map. Copy the .mmap, rename to .zip, and pull the files out of the attachments folder.

Opening and migrating a map

MindManager on Windows or macOS renders an .mmap with full fidelity, and Corel offers web and Microsoft Teams editions for subscribers. There is no current free official viewer, which is the usual pain point: you receive a map and do not own MindManager. The best free route is XMind, which imports MindManager maps through File → Import → MindManager with good structural fidelity, since it reads the same topic tree. ConceptDraw MINDMAP and Seavus iMindQ can also import the format if you already own them.

For a fixed, shareable copy, MindManager exports the map to PDF (preserving the diagram) or to Microsoft Word (which flattens the tree into a heading-and-bullet outline rather than a picture). It can also export tasks to a Microsoft Project .mpp, carrying dates and dependencies but not the free-form layout. If you lack MindManager entirely, the reliable options are to ask the sender to export a PDF, import into XMind, or unzip the file to recover its text and attachments.

FAQ

How do I open an MMAP without MindManager?

Import it into XMind (File → Import → MindManager), which reads MindManager maps well and has a free tier. Alternatively ask the sender to export a PDF, or rename a copy of the file to .zip to extract its Document.xml text and any embedded attachments.

Why is my MMAP actually a ZIP file?

MindManager saves a map as a ZIP package containing an XML description of the map (Document.xml) plus embedded media. Renaming to .zip lets you browse the contents, but you still need MindManager or XMind to see it laid out as a proper map.

What is the difference between MMAP and MMPT?

An .mmap is a saved mind map. An .mmpt is a MindManager template, a starting-point map with a preset theme and structure. Both use the same ZIP-plus-XML packaging; the template is meant to be opened to create new maps from it.

References

• Corel MindManager — MMAP file page
• Corel MindManager — official site
• XMind — imports MindManager maps

Feedback

Was this page helpful?

Yes No

Glad to hear it! Please tell us how we can improve.

Sorry to hear that. Please tell us how we can improve.