PDF
Your PDF
Paste your PDF. Nothing to upload.
←PDF
Make a mind map
Turn a PDF into a mind map
The document has an outline. The argument has a shape, and they are not the same.
Free to try, no card. Your PDF opens in Ancher.
Document structure in orderPage numbersTables as tables
Kept in parts
Every one of these stays separately addressable instead of collapsing into one block of text.
CentreBranchesCross-linksGaps
Mind map
The structure of an argument, laid out so the shape is visible at a glance.
A report's contents page is a sequence chosen for completeness; the argument inside it depends on itself in ways the numbering never shows. Ancher uses the preserved structure to find the sections, then maps how they actually rely on each other — which finding rests on which method, which conclusion needs a caveat from twenty pages earlier.
The honest version
Section 4 depends on a caveat in section 2, and the numbering hides that
Documents are linear because paper is. Arguments are not: a result in the discussion frequently holds only under a limitation stated in the methods, and the two sit forty pages apart with nothing connecting them but a reader's memory. A map can draw that dependency, and it is the thing a contents page structurally cannot show.
One page of one PDF, at p. 6, read two ways.Illustrative. The figure is invented; the gap it falls into is not.
as established earlier, this holds only under the assumption described in
In the methods section — not readThe specific never reaches the draft
Mind map
In the methods section
linear response assumed
from p. 6
Lands in the draft, with its timecode
- The centre is the document's actual claim, which is often not what the title announces.
- Cross-links are drawn where a later section depends on an earlier caveat, with both page numbers.
- Sections that support nothing are marked, because a document can contain a chapter its argument never uses.
What comes out
Mind map, section by section
The structure of an argument, laid out so the shape is visible at a glance.
Centre
The document's actual claim, taken from where the argument converges rather than from the title.
Branches
The supporting sections, in the order the argument needs rather than the order they are printed.
Cross-links
Cross-links wherever a later section depends on an earlier caveat, with both pages.
Gaps
Claims the document makes without support, and sections its argument never uses.
Legend
What a line means, plus the document and its date, so the map travels alone.
PDF-to-mind-map prompt
The link on its own gets a summary. This is the instruction that produces the 5 sections above, in that order, with the rules that keep them honest. Paste it with your PDF — in Ancher, or in whatever assistant you already use.
Map this document. (1) Put its actual claim at the centre, from where the argument converges rather than the title. (2) Branch the supporting sections in the order the argument needs, not the order printed. (3) Draw a cross-link wherever a later section depends on an earlier caveat, with both page numbers. (4) Mark claims with no support and sections the argument never uses. (5) Include a legend with the document and date. Keep it under thirty nodes.
The detail, if you want it
How each part of a PDF becomes a section
| From the PDF | Into | Why |
|---|---|---|
| Document structure in order | Branches | Headings, body and captions arrive as separate elements, which is what makes the document's own divisions usable as a starting skeleton. |
| Reading order | Cross-links | Reading order survives, so a phrase like as established earlier can be resolved to the section it refers back to. |
| Page numbers | Cross-links | Both ends of a dependency carry a page number, which is what makes a drawn link checkable rather than asserted. |
| Embedded images and figures | Centre | Figure captions frequently carry the tightest statement of a finding in the whole document, which makes them a good candidate for the centre. |
| Tables as tables | Gaps | A claim with no table behind it in a document full of tables is a visible absence, and the map marks it. |
Everything Ancher keeps from a PDF
Document structure in order
Headings, body and captions arrive as separate elements, so the document's own outline survives ingest.
Page numbers
A page-level anchor is what makes a citation checkable by someone else holding the same file.
Tables as tables
Tables come back as their own elements rather than as flattened lines, so a figure stays attached to the row and column that give it meaning.
Embedded images and figures
Figure captions frequently carry the tightest statement of a finding in the whole document.
Reading order
Elements come back in sequence, which is what lets a section be reassembled rather than guessed at.
Word and PowerPoint too
The same path takes .docx and .pptx, so a deck and its write-up can sit in one collection.
The four steps
- Add the PDF. Upload the file. Ancher parses it into ordered elements rather than one flat string, keeps the page number on each, and pulls out the embedded images.
- Nothing gets flattened. Document structure in order, page numbers, tables as tables, embedded images and figures, reading order, word and powerpoint too stay separately addressable instead of collapsing into one block of text.
- Ask for a mind map. Ancher fills centre, branches, cross-links, gaps, legend using the mapping above, not a generic summary pass.
- Check it before you use it. Every specific keeps a link back to where it came from in the PDF, so a claim can be verified without reopening the source.
Where this goes wrong
- A map that mirrors the contents page is an outline drawn sideways. If nothing links across sections, the structure was copied rather than read.
- Long documents make wide maps. Past thirty nodes it stops being one screen, and a map you have to navigate is a document with extra steps.
- A dependency the map draws is a reading of the argument, not a claim the author made. Check the pages before treating it as the author's own logic.
Questions people ask
How is this different from the contents page?
A contents page shows the order of printing. The map shows which sections the argument actually depends on, which is frequently a different shape — and the dependencies that cross twenty pages are the ones no reader holds in their head.
What size document works?
Long enough to have real structure, short enough that thirty nodes covers it — roughly a paper or a report rather than a book. A book becomes a map you navigate rather than see.
Does it show weaknesses?
It shows claims with nothing supporting them and sections the argument never uses, which is frequently the same thing. It does not judge the reasoning; it makes the shape visible so you can.
Bring your own PDFs
Everything you save lives in one workspace, so the mind map is built from your sources — not from a model's memory of the internet.
Open Ancher →Not a PDF? The same mind map also comes from YouTube video, X thread, LinkedIn post.