Docling Core
Docling Core is a library that defines core data types and transformations in Docling.
Installation
To use Docling Core, simply install docling-core from your package manager, e.g. pip:
pip install docling-core
Development setup
To develop for Docling Core, you need Python 3.10 through 3.14 and the uv package. You can then install it from your local clone's root directory:
uv sync --all-extras
To run the pytest suite, execute:
uv run pytest -s test
Main features
Docling Core provides the foundational DoclingDocument data model and API, as well as additional APIs for tasks like serialization and chunking, which are key to developing generative AI applications using Docling.
DoclingDocument
Docling Core defines the DoclingDocument as a Pydantic model, allowing for advanced data model control, customizability, and interoperability.
In addition to specifying the schema, it provides a handy API for building documents, as well as for basic operations, e.g. exporting to various formats, like Markdown, HTML, and others.
👉 More details:
Serialization
Different users can have varying requirements when it comes to serialization. To address this, the Serialization API introduces a design that allows easy extension, while providing feature-rich built-in implementations (on which the respective DoclingDocument helpers are actually based).
👉 More details:
Chunking
Similarly to above, the Chunking API provides built-in chunking capabilities as well as a design that enables easy extension, this way tackling customization requirements of different use cases.
👉 More details:
Profiling
The Profiling API enables extraction of comprehensive statistics from DoclingDocument objects, both for individual documents and collections. It provides metrics on document structure (pages, tables, pictures, text items) along with statistical distributions (deciles, histograms) and visualization capabilities for analyzing document collections at scale.
👉 More details:
Contributing
Please read Contributing to Docling Core for details.
References
If you use Docling Core in your projects, please consider citing the following:
@techreport{Docling,
author = "Deep Search Team",
month = 8,
title = "Docling Technical Report",
url = "https://arxiv.org/abs/2408.09869",
eprint = "2408.09869",
doi = "10.48550/arXiv.2408.09869",
version = "1.0.0",
year = 2024
}
License
The Docling Core codebase is under MIT license. For individual model usage, please refer to the model licenses found in the original packages.
Release files for docling-core 2.97.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| docling_core-2.97.1.tar.gz | 379.8 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| docling_core-2.97.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 683.5 kB
Release files / docling_core-2.97.1.tar.gz
| Download URL | docling_core-2.97.1.tar.gz |
|---|---|
| Size | 379.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
bd506e8bf3780e2868be3223d24ffd648d2a625161b9a5ecc10853218dff95a2
|
|
BLAKE2b-256 checksum How to use checksums |
ca34f7299b5c96db1808972ab68b575fecd977351a3461e5a7eb9d600b4f8033
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 18, 2026.
Transparency logRelease files / docling_core-2.97.1-py3-none-any.whl
| Download URL | docling_core-2.97.1-py3-none-any.whl |
|---|---|
| Size | 303.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e4edca6d2d2c57a4352e5a9e33d8401fdbfaef68473389a790ed23f494711930
|
|
BLAKE2b-256 checksum How to use checksums |
9ee7e13e09fa09c8d5326d3f8e52c88c1e2e77fd2f83a3ac4255676ae77ef1b3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 18, 2026.
Transparency log
