Free tool · works now

Unused Attachment Reviewer

Audit vault attachments to identify unreferenced orphan files, reclaim storage, and generate archive scripts.

Runs 100% in your browser. Cross-reference vault media files against notes text, detect unreferenced orphans, and produce reversible shell archive scripts.

9Files scanned
4Candidate orphans
1Loose mentions
4In use
2System filtered
Source Markdown notes text618 chars
Attachment file paths inventory11 files
Attachment Audit & Confidence Matrix9 audited
Filename & PathMedia TypeConfidence StatusReferencesProvenance & Explanation
deprecated-roadmap-v1.pdf
docs/deprecated-roadmap-v1.pdf
pdfCandidate Orphan0
0 explicit / 0 loose
Zero mentions detected anywhere in scanned notes. Candidate for archiving.
obsolete-database-erd.svg
assets/obsolete-database-erd.svg
imageCandidate Orphan0
0 explicit / 0 loose
Zero mentions detected anywhere in scanned notes. Candidate for archiving.
orphaned-wireframe.png
attachments/orphaned-wireframe.png
imageCandidate Orphan0
0 explicit / 0 loose
Zero mentions detected anywhere in scanned notes. Candidate for archiving.
unreferenced-voice-memo.mp3
attachments/unreferenced-voice-memo.mp3
audioCandidate Orphan0
0 explicit / 0 loose
Zero mentions detected anywhere in scanned notes. Candidate for archiving.
legacy-cache-diagram.png
attachments/legacy-cache-diagram.png
imageLoose Mention1
0 explicit / 1 loose
Mentioned loosely in prose or script text without explicit Markdown embed syntax (1 occurrence on lines: 12). Inspect before moving or deleting.
core-architecture.svg
attachments/core-architecture.svg
imageIn Use1
1 explicit / 0 loose
Referenced explicitly in notes (1 mention across lines: 6).
cpu-latency-benchmark.png
assets/cpu-latency-benchmark.png
imageIn Use1
1 explicit / 0 loose
Referenced explicitly in notes (1 mention across lines: 7).
hardware-spec.pdf
docs/hardware-spec.pdf
pdfIn Use1
1 explicit / 0 loose
Referenced explicitly in notes (1 mention across lines: 9).
interview-memo.m4a
attachments/interview-memo.m4a
audioIn Use1
1 explicit / 0 loose
Referenced explicitly in notes (1 mention across lines: 8).
Candidate Orphans Checklist4 files
Reversible Shell Archive ScriptSafe non-destructive
#!/usr/bin/env bash
# Script generated by Unused Attachment Reviewer
# Carefully audit before executing in your vault terminal
set -euo pipefail

# Total candidate orphans: 4
mkdir -p .archive/orphaned_attachments
mv "attachments/orphaned-wireframe.png" .archive/orphaned_attachments/
mv "assets/obsolete-database-erd.svg" .archive/orphaned_attachments/
mv "attachments/unreferenced-voice-memo.mp3" .archive/orphaned_attachments/
mv "docs/deprecated-roadmap-v1.pdf" .archive/orphaned_attachments/

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 (![Caption](assets/diagram.png)), 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:

Questions

How does this tool detect unused or orphaned attachments?

The engine scans your inventory of attachment files and performs reverse reference matching against all pasted Markdown note contents. Files that have zero markdown image embeds, wikilink transclusions, standard link references, or loose text mentions are flagged as high-confidence orphans.

Why does the tool generate an archive shell script instead of deleting files directly?

Automated file deletion in local note vaults is risky because some attachments may be referenced by scripts, external project repositories, or upcoming drafts. Generating a non-destructive shell script that moves candidate files to an archive directory (.archive/orphaned_attachments/) allows you to inspect everything in terminal before deciding to purge.

What is the difference between an explicit embed and a loose prose mention?

An explicit embed is an intentional Markdown or Wikilink reference such as ![[diagram.png]] or ![Chart](assets/chart.png). A loose prose mention occurs when a filename appears in plain body text without link syntax. The auditor flags loose mentions separately so you can inspect whether the file is truly unneeded before moving it.

Are code fence blocks excluded from attachment matching?

Yes. Any code samples, syntax documentation, or terminal examples inside fenced code blocks (``` or ~~~) are strictly immune to matching. Example filenames mentioned in code blocks are never counted as active document references.

Does this tool transmit or inspect my vault documents or audio memos?

No. The engine runs 100% locally in your web browser. All reverse reference correlation, confidence calculations, and shell script generation happen purely in client-side memory with zero network requests.

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 unused attachment reviewer downloadDownload for Mac

No account needed. Intel Mac build