Install Docling on Windows
Windows 10 / 11 (64-bit) with Python 3.10+. The shortest reliable path is 64-bit Python + virtual environment + uv. Verify each command against the official installation docs.
Requirements checklist
- Windows 10 or 11, 64-bit (32-bit Python will fail on torch wheels).
- Python 3.10, 3.11 or 3.12, 64-bit, installed from python.org with “Add python.exe to PATH” checked.
- PowerShell (or Windows Terminal). Commands below assume PowerShell.
- ~2–4 GB free disk for first-run model downloads.
py --version; py -c "import struct; print(struct.calcsize('P')*8)"You want 3.10+ and 64. If you see 32, uninstall that Python and install the 64-bit build.
Install 64-bit Python correctly
- Download the Windows installer (64-bit) for Python 3.11 or 3.12.
- On the first installer screen check “Add python.exe to PATH”, then “Install Now”.
- Confirm in a new PowerShell window:
py --versionpip --versionIf py is not found, close and reopen the terminal (PATH refresh) or reinstall with the PATH option checked. The Microsoft Store Python shim can also shadow python — prefer the py launcher or the python.org build.
Virtual environment in PowerShell
py -m venv .venv.venv\Scripts\Activate.ps1python -m pip install -U pipSet-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser once, then activate again.Fastest install: uv (recommended)
uv resolves pre-compiled wheels and avoids most native-compiler failures on Windows:
uv add doclingWith extras (examples):
uv add "docling[rapidocr]"Or in an existing uv project: uv venv --python 3.12, activate, then uv pip install docling.
Standard install: pip
pip install doclingIf that succeeds you are done — skip to verification. If pip starts compiling packages and fails with a C++ error, do not fight it: either switch to uv above or fix the toolchain in the next section.
Fix “Microsoft Visual C++ 14.0 is required”
Fix A (easiest) — use uv so you get wheels instead of a compiler invocation. Fix B — install the toolchain:
winget install Microsoft.VisualStudio.2022.BuildTools- In the installer select the “Desktop development with C++” workload (MSVC 14.0+).
- Restart the terminal, re-activate the venv, delete any half-built env if needed, and retry
pip install docling. - Core Docling usually has wheels — this error mostly appears with extras like
tesserocrorfasttext. If only an extra needs compiling, considerrapidocr/easyocrinstead.
OCR extras on Windows
| Engine | Windows install | Notes |
|---|---|---|
| RapidOCR (easiest) | pip install "docling[rapidocr]" | Pip-only, no system binary. Good default on Windows. |
| EasyOCR | pip install "docling[easyocr]" | Pip-only, larger download, good multilingual. |
| Tesseract | Install UB Mannheim binary + set PATH and TESSDATA_PREFIX, then pip install "docling[tesserocr]" | Best accuracy control, but needs the system binary + language data. |
Compare quality and languages in the OCR guide. For scanned PDFs force full-page OCR: docling convert scan.pdf --ocr-mode full_page.
GPU / CUDA via WSL2
Native Windows CUDA depends on your PyTorch build and drivers. The simplest reliable GPU path is WSL2 with Ubuntu + NVIDIA CUDA drivers for WSL:
- Install WSL2 + Ubuntu from the Microsoft Store, install the NVIDIA Windows driver with WSL support.
- Inside WSL2 follow the Linux guide (CUDA-enabled torch), then select the device explicitly:
docling convert report.pdf --device cudaVerify with python -c "import torch; print(torch.cuda.is_available())" — it must print True before GPU flags can help. CPU-only installs are fully supported; GPU only adds speed.
Verify
docling --helpdocling convert sample.pdf --to mdUse a small digital PDF first (no OCR, no GPU). The very first run downloads models — keep the connection alive. Then try --to json and an OCR engine to confirm each layer.
Common Windows errors
- Installation fails / C++ 14.0 required — see installation fails and MSVC 14.0 required.
pythonopens the Microsoft Store — use thepylauncher or disable the Store alias; prefer the python.org build.- 32-bit torch wheels / “not a supported wheel” — you have 32-bit Python; reinstall 64-bit.
- Permission errors — never use an admin shell as the fix; a venv plus
--user-free install is the fix. - Slow first conversion — normal: models are downloading. Pre-fetch with
docling-tools models download --all.
Windows FAQ
uv or pip on Windows?
uv add docling. It resolves pre-compiled wheels and skips the MSVC toolchain that pip sometimes demands for optional extras.Do I need Visual Studio?
Which OCR engine is easiest on Windows?
TESSDATA_PREFIX.Can I use my NVIDIA GPU on Windows?
--device cuda.PowerShell blocks venv activation?
Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser once, then .venv\Scripts\Activate.ps1 again.Verified with Docling v2.129.0 · Last checked 2026-09-22 · Official source