Skip to content

Image not found

An image reference points at a file that isn't there. This isn't a Keystone check — Pandoc, the tool underneath, can't fetch the file and warns. The build continues, but the image is missing from your book.

What it looks like

![Map](assets/missing.png)

With no assets/missing.png, the build prints (PDF):

WARN: Could not fetch resource assets/missing.png: replacing image with description

and EPUB:

WARN: Could not fetch resource assets/missing.png: PandocResourceNotFound "assets/missing.png"

What it means

Pandoc resolves image paths as it builds. A path that doesn't resolve can't be fetched, so Pandoc drops the image with a warning and carries on — in PDF it substitutes the image's alt text ("replacing image with description"), in EPUB it leaves the reference unresolved. Because it's a warning, a lenient build still succeeds with the image simply gone. Under strict mode it fails the build — which is how you catch a missing image before you publish.

Check the path, and build strict before you publish

Paths are relative to your project, so confirm the spelling and that the file is under assets/ — see Figures & images. Building strict stops the next one rather than shipping the gap.

  • Undefined citation — the other common tool-origin warning that a lenient build lets through and strict mode catches.