Free tool · works now

Attachment Path Auditor

Audit image and media links in Markdown notes for missing files, remote URLs, and absolute paths.

Runs 100% in your browser. Audit image embeds, audio memos, and PDF links across your vault. Flag missing files, absolute path portability hazards, and unorganized media.

10References
4Resolved
1Missing files
2Absolute paths
1Remote URLs
1Outside folder
Source Markdown notes1003 chars
Vault file & attachment inventory8 files
Attachment Reference Audit Breakdown10 audited
LineTarget / FilenameMedia TypeStatusResolution / Portability Advice
6system-architecture.png
wikilink-embed
imageResolvedResolved by filename to "attachments/system-architecture.png".
7network-topology.svg
wikilink-embed
imageResolvedResolved by filename to "attachments/network-topology.svg".
8distributed-consensus-diagram.png
wikilink-embed
imageMissing fileAttachment "distributed-consensus-diagram.png" not found anywhere in the provided vault inventory.
11attachments/interview-memo.m4a
wikilink-embed
audioResolvedResolved to "attachments/interview-memo.m4a".
12standup-recording.wav
wikilink-embed
audioOutside folderFile located in vault ("standup-recording.wav"), but outside designated attachment directory "attachments".
Suggested fix: attachments/standup-recording.wav
15https://cdn.example.com/assets/cloud-diagram.png
markdown-image
imageRemote URLExternal remote URL. Dependent on third-party host and network availability.
16/Users/developer/Desktop/screenshot-2026.png
markdown-image
imageAbsolute pathAbsolute filesystem path. Breaks portability across devices and collaborators.
Suggested fix: Relative path in vault (e.g. attachments/screenshot-2026.png)
17file:///Users/developer/Documents/specs/hardware-spec.pdf
markdown-link
pdfAbsolute pathAbsolute filesystem path. Breaks portability across devices and collaborators.
Suggested fix: Relative path in vault (e.g. attachments/hardware-spec.pdf)
20attachments/whitepaper.pdf
markdown-link
pdfResolvedResolved to "attachments/whitepaper.pdf".
21app-icon.png
wikilink-embed
imageAmbiguousAmbiguous reference: 2 files share filename "app-icon.png" (ui/app-icon.png, assets/brand/app-icon.png).
Missing Attachments Checklist1 files
Formula-Guarded CSV ExportSpreadsheet ready
"Line","Syntax","Raw Target","Media Type","Status","Matched Path","Explanation"
"Line 6","wikilink-embed","system-architecture.png","image","resolved","attachments/system-architecture.png","Resolved by filename to ""attachments/system-architecture.png""."
"Line 7","wikilink-embed","network-topology.svg","image","resolved","attachments/network-topology.svg","Resolved by filename to ""attachments/network-topology.svg""."
"Line 8","wikilink-embed","distributed-consensus-diagram.png","image","missing","None","Attachment ""distributed-consensus-diagram.png"" not found anywhere in the provided vault inventory."
"Line 11","wikilink-embed","attachments/interview-memo.m4a","audio","resolved","attachments/interview-memo.m4a","Resolved to ""attachments/interview-memo.m4a""."
"Line 12","wikilink-embed","standup-recording.wav","audio","outside-folder","standup-recording.wav","File located in vault (""standup-recording.wav""), but outside designated attachment directory ""attachments"". (Fix: attachments/standup-recording.wav)"
"Line 15","markdown-image","https://cdn.example.com/assets/cloud-diagram.png","image","remote-url","None","External remote URL. Dependent on third-party host and network availability."
"Line 16","markdown-image","/Users/developer/Desktop/screenshot-2026.png","image","absolute-path","None","Absolute filesystem path. Breaks portability across devices and collaborators. (Fix: Relative path in vault (e.g. attachments/screenshot-2026.png))"
"Line 17","markdown-link","file:///Users/developer/Documents/specs/hardware-spec.pdf","pdf","absolute-path","None","Absolute filesystem path. Breaks portability across devices and collaborators. (Fix: Relative path in vault (e.g. attachments/hardware-spec.pdf))"
"Line 20","markdown-link","attachments/whitepaper.pdf","pdf","resolved","attachments/whitepaper.pdf","Resolved to ""attachments/whitepaper.pdf""."
"Line 21","wikilink-embed","app-icon.png","image","ambiguous","ui/app-icon.png","Ambiguous reference: 2 files share filename ""app-icon.png"" (ui/app-icon.png, assets/brand/app-icon.png)."

The silent decay of attachments in local-first knowledge bases

Markdown's strength is its pure plain-text longevity. However, rich documentation inevitably incorporates binary assets: system architecture screenshots, vector flowcharts, audio interview recordings, and reference PDF specifications. In Obsidian and CommonMark repositories, media is referenced via embedding syntax like ![[architecture.png]] or standard links like ![Chart](assets/chart.png).

Over time, attachment links suffer from silent decay. Reorganizing folders moves notes without updating relative asset paths, operating system clipboard drops paste non-portable absolute machine paths, and cloud image hosts suffer link rot. Without an automated attachment audit, broken media references linger undetected until critical documentation is needed.

Audit classifications: from resolved assets to portability risks

The Attachment Path Auditor evaluates every media reference against six operational classifications:

  • Resolved (Vault Conformance): The binary file exists in your inventory and resides within your designated assets directory.
  • Missing / Broken: The referenced image, audio memo, or PDF cannot be located anywhere in your vault inventory.
  • Absolute System Path (High Portability Hazard): References using file:///Users/... or /Users/name/Desktop/.... These paths work on the author's local desktop but immediately break when synced to mobile devices, shared with colleagues, or moved to another computer.
  • Remote Web URLs: Images hosted on external HTTP/HTTPS domains. While convenient, remote hosting breaks offline availability and leaves documentation vulnerable to third-party outages.
  • Outside Folder: The attachment exists in the vault, but sits in the root folder or an unorganized subfolder rather than your designated attachments/ directory.
  • Ambiguous Filenames: Multiple files with identical names reside in different directories (e.g. ui/icon.png vs brand/icon.png), making shortest-path resolution unpredictable.

Best practices for organizing Markdown vault media

To ensure decades-long portability for your personal knowledge base:

  1. Designate a Single Attachment Folder: Configure your editor (such as Obsidian's "Files and Links > Default location for new attachments") to save all media into a dedicated subfolder such as attachments/.
  2. Eliminate Absolute Paths: Never link files directly from your Desktop or Downloads folder. Always move binaries into your vault before embedding them.
  3. Localize Cloud Images: Download critical remote diagrams and save them locally to eliminate dependencies on third-party CDNs.
  4. Audit Before Archiving: Run an attachment path audit prior to publishing wikis or migrating notes across storage engines.

Related local note management tools

Explore complementary utilities designed for clean, resilient Markdown documentation:

Questions

Why are absolute filesystem paths dangerous in Markdown notes?

Paths like `file:///Users/username/Desktop/image.png` or `/Users/developer/assets/diagram.png` point to a specific user account on one local computer. When notes are synced to a mobile device, backed up, or shared with teammates, these absolute links fail immediately because the destination directory does not exist on other machines.

How does the auditor verify whether attachments match a designated folder?

When an attachment folder is specified (e.g. `attachments/` or `assets/`), the engine tests whether resolved files live inside that folder. If an image is located in the vault root or another directory, it is flagged as Outside Folder with a suggested relative destination.

Why should personal notes minimize dependencies on remote CDN URLs?

Notes containing remote web images (`https://cdn.example.com/image.png`) rely on constant internet connectivity and third-party host availability. If the host experiences downtime, removes the asset, or modifies URL structures, your documentation suffers permanent data loss.

Are code blocks and syntax samples protected from false attachment extraction?

Yes. The engine parses lines sequentially and tracks code fences (` ``` ` and `~~~`). Any sample image or media syntax inside code blocks is strictly excluded from your attachment audit.

Does this tool upload or scan my personal images or voice notes?

No. The auditor operates strictly on the text strings you paste (the Markdown notes and file inventory path list). No image binaries, audio recordings, or documents are ever uploaded or transmitted.

Want complete media integrity across your local notes?

Complete Obsidian vault compatibility, plain text Markdown on disk, and private on-device notes in Oyma.

tools attachment path auditor downloadDownload for Mac

No account needed. Intel Mac build