tito-PDF Documentation

Troubleshooting

This page focuses on common failure modes and the shortest retry path.

0) Sanity check: which tito-pdf are you running?

command -v tito-pdf
tito-pdf --help

Missing qpdf

Symptoms:

Fix:

brew install qpdf

Missing Python libraries (PyMuPDF / pdfplumber / python-docx)

Symptoms:

Fix: Reinstall tito-pdf using the repo installer (it recreates the runtime venv and installs requirements.txt):

sudo ./install/install.sh
command -v tito-pdf

OCR issues

Symptoms

Fixes / retries

tito-pdf input.pdf --mode fast --md-out out/input.md
tito-pdf input.pdf --mode best --md-out out/input.md
tito-pdf input.pdf --no-ocr --md-out out/input.md

See: OCR.

No tables detected

The tables output (No tables detected.) can be correct.

Retry order (recommended): 1) best mode (auto lenient fallback)

tito-pdf input.pdf --tables --out-dir out --mode best

2) explicitly enable lenient tables

tito-pdf input.pdf --tables --out-dir out --tables-lenient

3) limit pages while iterating

tito-pdf input.pdf --tables --out-dir out --mode best --max-pages 10

See: Tables.

Too many table false positives

If you enabled lenient mode and got junk tables:

tito-pdf input.pdf --tables --out-dir out --mode robust --max-pages 10

Performance

Fastest first:

Example:

tito-pdf input.pdf --mode fast --md-out out/input.md --max-pages 10

Inconsistent output across machines

Even deterministic tools can vary with toolchain versions.

To capture forensic info, enable assets JSON:

tito-pdf input.pdf --md-out out/input.md --assets-json out/input.assets.json

See: Assets JSON.