# PDF Footnotes to Markdown: Keep Markers, Definitions, and References Together

Check footnote numbering, links, cross-page continuations, and Markdown rendering after converting a PDF with notes.

A good footnote connects the in-text marker, the note content, and the surrounding paragraph. After converting a PDF to Markdown, click through a few notes in your everyday editor to see whether the content is complete and returns to the original sentence before organizing the rest of the text.

Review the source relationship before reorganizing the file. A correct-looking number attached to the wrong explanation can be harder to notice than a missing note.

## Match markers to complete definitions

Choose a marker in the original body and read its full note. Find both in the Markdown. Check that the explanation starts and ends at the same points and that any citation, qualification, or continuation is present.

Now start from a note in the result and locate the source sentence it explains. This reverse check can reveal duplicated notes or definitions left without a meaningful reference.

Include a short note, a long note, and one containing a citation in your sample. A quick check of only the notes already linked will not find a note omitted completely. Inspect a page from the source as well; the [footnote review article](https://pdfcraft.ai/blog/jev-footnote-review/) explains why that wider view matters.

## Distinguish labels from working links

Some Markdown implementations support reference-and-definition footnotes. A manually written illustration is:

```markdown
The passage includes a qualification.[^sample]

[^sample]: The full explanatory note belongs here.
```

The above shows an example of footnote syntax. [CommonMark](https://spec.commonmark.org/) does not define a standard footnote extension, and support varies across editors. Open a preview to see whether reference marks link to notes as expected, and adjust syntax to match your target application if needed.

If the export uses ordinary text or links instead, inspect that representation rather than forcing it into a different syntax immediately. Renumbering labels can break references unless the marker and definition change together.

Pay attention when numbering restarts by chapter. Two printed note “1” labels may refer to different notes. Your working Markdown must preserve that distinction even if you choose new internal identifiers.

## Follow long notes across page boundaries

A note can start at the bottom of one PDF page and continue on the next. Compare the final source line on the first page with the next page's continuation before deciding where the note ends.

Running headers, page numbers, and the next paragraph can be mistaken for part of the note. Conversely, a continuation can be placed into the main body. Read enough surrounding text to establish ownership rather than joining fragments because they are physically nearby.

For endnotes, pick several citations from different chapters, locate their corresponding entries at the end of the text, and verify the numbering and content. This check is especially worthwhile for books that reuse note numbers across chapters, helping avoid linking an in-text mark to a note in another chapter.

Keep page and chapter locators in your review record, especially if the same numbering appears more than once.

## Preview and test in the destination editor

Open the Markdown where you intend to keep it. Test a marker, read the destination, and return to the sentence. If the editor provides a back-link, check that it returns to the correct occurrence.

For example, Obsidian outlines its supported syntax in its [Markdown reference documentation](https://obsidian.md/help/Editing%2Band%2Bformatting/Obsidian%2BFlavored%2BMarkdown). If you plan to publish your notes to another platform, preview them there as well to see how footnotes render and navigate.

If a note renders as code or plain punctuation, inspect syntax support before changing its content. If it opens the wrong explanation, return to the source mapping. Rendering and recognition errors need different fixes.

## Preserve notes when building a working file

In [PDF Craft's Markdown workflow](https://pdfcraft.ai/pdf-craft/), choose Markdown and review the footnote-related settings before submitting. Download the completed result and compare its notes with the source. Recognition of complex notes still needs review; do not assume every cross-page mapping is correct.

When extracting passages into [research notes](https://pdfcraft.ai/blog/pdf-to-markdown-for-research/), carry the necessary definition with the quotation and record the original page. A marker copied without its note may no longer preserve the author's meaning.

Save the unedited export separately from your corrected copy. The finished Markdown should let you trace a qualification to its source sentence and source document, not merely display a tidy sequence of superscripts.