Nutrient Python SDK

In-process Python bindings for the Nutrient document-processing engine. Open, convert, edit, OCR, extract, and export PDFs and Office formats directly from a Python process — no external server, no network round-trips, no DWS dependency. Different product from the nutrient-dws REST client (which is the hosted alternative).

Documentation

Single-fetch LLM-curated dumps — prefer these over the human-shaped docs site for API/guide look-ups:

• Guides: https://www.nutrient.io/guides/python/llms.txt
• API reference: https://www.nutrient.io/api/python/ — no llms.txt; instead every API page has a Markdown variant. Take any page URL, drop the trailing slash, append .md (e.g. https://www.nutrient.io/api/python/document.md).
• Cross-product index (other Nutrient SDKs): https://www.nutrient.io/llms.txt

Install

pip install nutrient-sdk

• Package name on PyPI: nutrient-sdk
• Import name in code: nutrient_sdk (underscored)
• Python: 3.8+ (per the PyPI metadata for the current 1.x line)

Hello world (PDF/Office conversion)

from nutrient_sdk import Document, License, PdfExporter

License.register_key("your-license-key")

with Document.open("input.docx") as doc:
    doc.export("output.pdf", PdfExporter())

Key concepts

• vs nutrient-dws: the nutrient-dws PyPI package is the DWS REST API client — it makes HTTPS calls to Nutrient's hosted Processor API. nutrient-sdk is in-process — it runs natively in your Python process with no network and no quota. Both are official; pick nutrient-sdk for self-contained workloads or when you can't depend on external network access.
• vs the third-party pspdfkit PyPI package: there is an unofficial pspdfkit package on PyPI from 2017 (third-party, unmaintained, unrelated to Nutrient). Don't use it. nutrient-sdk is the only official Nutrient in-process Python SDK.
• vs in-process server SDKs in other languages: see nutrient-nodejs-server-sdk, nutrient-java-server-sdk, nutrient-dotnet-server-sdk for the same in-process capability in Node.js / Java / .NET.