opendatalab/MinerU

Choose this fork if you want a more turnkey API/Docker/demo packaging of MinerU and can tolerate being far behind upstream. Choose upstream if you care about current fixes, active development, and the full maintained feature set.

Choose this fork if you want a browser-centric MinerU deployment with task persistence and richer result review. Choose upstream if you want the latest project fixes, broader maintenance, and less divergence risk.

Choose the fork only if you explicitly want this older baseline and can live without upstream progress. For most adopters, upstream MinerU is the better choice because it is active and substantially ahead.

Prefer this fork only if you specifically want an older pinned MinerU snapshot. For most adopters, upstream is the better choice because this fork shows no added capabilities and is materially behind recent fixes and deployment work.

Prefer this fork if your priority is deployment convenience, Chinese/local environment support, or a simplified service-oriented setup. Prefer upstream if you want the latest extraction quality, active maintenance, and fewer missing features.

Prefer upstream unless you specifically need this older snapshot. This fork adds no visible capabilities and is far behind current MinerU, so it is mainly useful as a starting point for self-maintained customization.

Choose this fork only if you specifically want its web API/Docker packaging workflow. For most adopters, upstream MinerU is the better base because it is much newer, actively maintained, and far more complete.

Choose this fork only if its language-control and human-in-the-loop extraction workflow are the point. If you want a maintained, upstream-aligned document conversion stack, the fork is too stale and too far diverged to be the safer default.

Prefer upstream unless you specifically need a frozen, older baseline. This fork shows no local feature work and is materially behind, so it is better suited as a snapshot than as the foundation for active adoption.