creatorvalet

Markdown link checker for a local folder

Find broken relative links, missing images and anchors, duplicate headings, front matter issues and unreachable Markdown files—with an exact local report.

  • SECURE
  • NO UPLOADS
  • NO SIGNUP
  • BROWSER BASED
  • FREE
  • FOREVER.

Support us with a link or a share

Local collection

Open a folder in the Markdown link checker

Folder intake keeps the relative paths reported by your browser and includes non-Markdown assets for existence checks. Flat files are an explicit fallback when directory selection is unavailable; nested disk paths cannot be recovered from flat files.

Paste one Markdown document instead
Optional explicit rules

Choose entry files, a template or front matter fields

Without these choices, the checker reports only local syntax facts. It never infers a schema, template, entry point, quality score, freshness or AI readiness from the collection.

Check Markdown links against the collection you actually selected

The checker resolves relative link and image destinations from each browser-reported source path. It decodes URI path characters conservatively, removes a query before file lookup and checks a fragment against a documented source-slug dialect. Exact paths win; a match that exists only after case folding or portable normalization is reported as ambiguous rather than guessed.

External Markdown links are inventory, not live status

HTTP, HTTPS, email and telephone targets are listed as external and never fetched. The tool does not claim that an external page is online, safe, current or correct. Root-relative links also remain unresolved because a browser folder picker cannot prove the future website root that will serve them.

Orphans, templates and front matter require an explicit rule

An orphan finding appears only after you name one or more entry files. Reachability then follows resolved local Markdown links from those entries. Structure comparison likewise needs one exact template path and compares ordered heading paths and levels without changing case or Unicode. Front matter field checks use only the dot paths and YAML 1.2 primitive types you enter; the collection is never treated as its own inferred schema.

The report is evidence, not a quality score

The deterministic creatorvalet.markdown-collection-check/v1 report records browser-reported paths, origins, byte lengths, SHA-256 receipts, BOM and line-ending facts, selected rules and ordered findings with source spans. It contains no source text, timestamp, total score, freshness judgment or AI-readiness claim. Repeating the same bytes, paths, origins and options produces the same JSON bytes.

Your Markdown folder stays local

Directory selection, flat-file fallback, byte reading, UTF-8 decoding, hashing and checking happen in a browser worker after you press the button. Binary assets are inventoried without being decoded as Markdown, and one invalid UTF-8 Markdown file becomes a finding instead of erasing the report for every other file. There is no upload step and no arbitrary collection-size cutoff.

Use the Markdown diff to compare two source versions, the Markdown merger to combine documents, or the Markdown editor to change one document. This checker remains a read-only collection audit.

Questions

Does this check whether external websites are online?

No. HTTP, HTTPS, email and telephone links are inventoried as external and are never fetched or given a status. The checker resolves only paths and anchors inside the files you selected.

How are orphan Markdown files found?

Choose one or more explicit entry files. A Markdown file is called an orphan only when no selected entry reaches it through resolved local Markdown links. Without an entry selection, no orphan claim is made.

Does it infer a front matter schema from my files?

No. You can enter required dot paths and optional primitive types. Without those explicit rules, it reports only malformed YAML, duplicate keys and complex keys it cannot check conservatively.

Are my folder and files uploaded?

No. File reading, UTF-8 decoding, hashing and every rule run in a browser worker in this tab. The report contains provenance and findings, not your source text.