Diagnosing dormant binary assets and storage bloat in local wikis
Personal knowledge graphs that rely on plain text files for notes still store rich binary assets: architecture diagrams, whiteboard photos, raster mockups, audio voice recordings, and technical PDF manuals. When notes are revised, older screenshots superseded, or exploratory audio memos transcribed into text, the underlying binary files often remain indefinitely in your media folder.
Because Markdown stores connections as textual pointers rather than maintaining a centralized database catalog, identifying unreferenced binary payloads requires a full reverse reference audit.
Reverse index construction: correlating file paths against note text
The Unused Attachment Reviewer scans your attachment directory listing and cross-correlates every asset against all active Markdown files. To prevent false alarms, the engine parses your documents sequentially and isolates distinct reference styles:
- Explicit Transclusions: Syntax designed specifically to embed media into the rendered document, such as Obsidian wikilink embeds (
![[diagram.png]]), CommonMark images (), and raw HTML image tags (<img src="...">). Any file matching an explicit embed is verified as In Use. - Loose Prose Mentions: Instances where a filename appears within paragraphs, inline code, or task descriptions without formal embed markers. These occurrences signify that a file is part of your intellectual context even if not visually rendered, alerting you to inspect the note before relocating the file.
- High-Confidence Dormant Orphans: Media assets that appear in neither embedding syntax nor body prose across your entire note corpus. These represent prime candidates for storage reclamation.
Safe quarantine workflows using non-destructive shell automation
Immediate, hard deletion of binary files carries serious operational hazards. Upcoming drafts, external Git repositories, or local build scripts might depend on files that are not actively linked in your primary notes folder.
Rather than deleting files on disk, this browser utility produces a non-destructive Bash migration script. When executed in your vault root, it safely moves all flagged orphan assets into an isolated quarantine folder (.archive/orphaned_attachments/). This preserves file metadata, maintains your commit history, and ensures immediate, one-click restoration if an asset is ever needed again.
Defensive spreadsheet hygiene: formula injection mitigation
When exporting media audit registers to CSV for vault maintenance records or team review, special care must be taken with untrusted filenames. Operating system files or user-named assets beginning with mathematical symbols (such as =, +, -, or @) can trigger dynamic formula execution when opened in Microsoft Excel or Google Sheets. Every exported field is sanitized with an apostrophe prefix to ensure spreadsheet software treats all paths as inert plain text.
Complementary vault maintenance utilities
Maintain complete integrity across your personal knowledge collection with these offline browser tools:
- Attachment Path Auditor: Identify broken media links, non-portable absolute filesystem paths, and remote CDN dependencies.
- Vault Health Inspector: Comprehensive audit of note backlinks, orphan attachments, and file integrity.
- Broken Wikilink Finder: Find dangling note connections, casing mismatches, and dead links.
- All Tools Directory: Discover private browser-based utilities for Markdown workflows.