Delivery instrument 01Local / no upload
Know the PDF is right before they open it.
A local CLI that compares your Markdown with the file you’re about to send—then checks the parts long exports quietly lose.
Your documents never leave your machine.
Current reading
One command. An auditable result.
pdfcheck report.md report.pdf --report preflight.html
Inspection circuit
Six independent failures. One delivery gate.
Conversion success only means a file exists. Preflight asks whether it still works.
- 01Hard fail
Outline & targets
Matches Markdown headings against PDF bookmarks and resolves source fragments.
- 02Hard fail
Clickable links
Confirms internal destinations and external URI annotations survived. Never fetches URLs.
- 03Hard fail
Code overflow
Flags positioned text runs that extend past the visible page boundary.
- 04Warning
Empty pages
Finds pages without text, images, or other painted content.
- 05Hard fail
Page drift
Compares actual pagination with a baseline and explicit tolerance.
- 06Selectable
PDF metadata
Reads the output file’s title, author, dates, subject, and keywords.
Source-side test bench
Try the first half of a preflight.
Paste Markdown or load a .md file. This browser demo checks heading fragments and suspiciously long code; the CLI adds definitive PDF inspection. Nothing is uploaded.
Drop a Markdown file here, or use the sample. Maximum 10 MB.
Bench ready
Load or paste a source, then run the local scan.
Reading source signals…
Source reading
—Open local core · v0.1.0
Put preflight beside your exporter.
One Rust binary. No daemon, browser automation, account, telemetry, or network client.
Read the source and full usage →cargo install --git https://github.com/B-Divyesh/sf-long-markdown-pdf-check