Skip to content
DocDot logo

DocDot

Runs several local PDF parsers such as MinerU and Docling behind one command-line install, converting PDFs to Markdown or JSON without cloud upload.

Actively maintained

DocDot: data, price, alternatives
At a glancechecked Oct 31, 2026

not read yet

Use

For
Developers and teams running local PDF parsers for AI agent workflows on macOS.
Activity
Actively maintainedrelease 4 days ago
How it runs
CLI
Used for
  • Parse PDFs locally with a chosen parser
  • Compare parser accuracy and runtime before choosing one
  • Feed parsed PDF output directly to AI agents
Worth knowingcomputed from what we read · each with its source
Your datawhat they publish, each line with its page · read Oct 23, 2026

These are DocDot's own statements, read from its pages. We did not audit them. A line that is missing was not found on the pages we read; it does not mean the practice is absent.

Alternatives in Developer toolsby use, among tools still maintained

Figure and bar: visits/mo, estimate · year: online since

Compare DocDot with

Pick up to two.

All 10 alternatives to DocDot →

All Developer tools tools →

Not it? Say what you need

beta

Three tools from the Atlas for the job you describe, each with what fits and what does not.

From people who use itnot part of the reading

No notes yet. What do you use DocDot for?

Sign in to leave a note
Questions this page answers
  • What is DocDot?

    Runs several local PDF parsers such as MinerU and Docling behind one command-line install, converting PDFs to Markdown or JSON without cloud upload. It is listed in the Atlas under Developer tools.

  • Who is DocDot for?

    Developers and teams running local PDF parsers for AI agent workflows on macOS.

  • Do people use DocDot?

    Emerging.

  • Is DocDot still maintained?

    Actively maintained: release 4 days ago.

  • Is DocDot safe?

    We do not audit vendors. What DocDot publishes, read 2026-10-23: a trust center.

  • What are alternatives to DocDot?

    In Developer tools, by use: PostHog, Cursor, ezeep, EnConvert, ApyHub.

How we read a tool

No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.

  • Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
  • Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
  • Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
  • The line and the use cases are written by us from the homepage, one tool at a time, and refused when they repeat the vendor's marketing.

How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.

How we read every tool → · By INITE Atlas Desk