ToolJovia
Files

Local Markdown File Link Auditor

Review links and images across actual selected Markdown notes and asset files without opening their destinations.

✓ Browser-local processing
Files are read locally and are not uploaded.

Loading tool…

How to use Local Markdown File Link Auditor

Treat a small selected folder’s flat filenames as a closed local inventory. Parse the actual Markdown source, retain link/image positions and show which relative targets are present in the selection. External links and fragment claims remain explicitly unverified; the tool neither crawls your disk nor renders untrusted notes.

  1. Select small .md notes and companion files with distinct flat names, or load the generated original example.
  2. Run the bounded CommonMark source inspection and review resolved local edge evidence.
  3. Download the closed-inventory report; inspect absent targets in the real project before calling them broken.

Good to know

  • Choose 1–30 files including 1–20 .md files, at most 1 MiB selected bytes and 50,000 aggregate Markdown UTF-16 characters. Markdown must be well-formed UTF-8; one BOM, if present, remains in source offsets. Companion contents are not decoded or type-certified.
  • Selected names form one exact case-sensitive flat root. No directory permission, filesystem traversal, extension/index guessing, symlink handling or paths inferred from absolute local locations is used. The tool can only say absent from this selected root, not missing everywhere.
  • CommonMark 0.31.2-style parser output supplies ordinary link/image and reference uses; ASCII reference labels only in this selected profile. Raw HTML, wiki links, plugins and literal unresolved brackets are not interpreted as links. URI schemes remain inert external source strings; fragments are retained without heading/anchor certification.
  • Parser import runs inside one same-origin module Worker, with 10 seconds for preparation and a separate 2-second compute limit. Combined AST is capped at 15,000 nodes/40 levels, definitions and edges at 1,000 each, and the report at 500,000 characters. Worker/DOM browser compatibility requires separate native verification.
  • Processing is local. Output is limited to 1,000,000 text characters unless a stricter file limit is stated.

Common questions

Why does a known file appear absent when it lives in a nested project folder?

This input profile uses the selected flat filenames, not an operating-system directory tree. It does not guess missing directory structure. Treat the report as evidence about this selection and use your project’s actual paths for a full repository check.

Is this input sent to a server?

No. The application processes this input inside your browser tab and does not save it to persistent storage.

Keep going with related tools

All files →