How to Run Examples Leave feedback

Every code example shown on this documentation site lives in a standalone, runnable form in the GroupDocs.Conversion-for-Python-via-.NET repository on GitHub. Each example ships with its input sample files, so you can clone the repo and run anything with a single command.

Before running the examples, make sure you have:

1. A supported platform and Python version — see System Requirements. Windows, Linux, and macOS (Intel and Apple Silicon) are all supported.
2. Git — or download the repository as a ZIP from GitHub.
3. A license file (optional but recommended) — without one, the library runs in evaluation mode with a watermark and a 3-page cap. See Licensing for how to obtain a free temporary license.

Clone the repository and navigate into the Examples folder:

git clone https://github.com/groupdocs-conversion/GroupDocs.Conversion-for-Python-via-.NET.git
cd GroupDocs.Conversion-for-Python-via-.NET

The repository mirrors this documentation tree. Every documentation page maps to a folder under Examples/, and every tabbed code block on a page maps to a .py file inside that folder. Input sample files live next to the script that reads them.

📂 GroupDocs.Conversion-for-Python-via-.NET
├── README.md
├── LICENSE
├── AGENTS.md                         ← extracted from the pip package for AI tools
├── Dockerfile                        ← runs the whole suite on Linux
├── .github/workflows/run-examples.yml ← CI: runs all examples on every push
└── Examples
    ├── requirements.txt
    ├── run_all_examples.py
    ├── getting-started
    │   └── quick-start-guide
    │       ├── convert_docx_to_pdf.py
    │       ├── convert_pdf_pages_to_png.py
    │       ├── convert_files_in_archive.py
    │       ├── annual-review.pdf
    │       ├── business-plan.docx
    │       └── compressed.zip
    ├── developer-guide
    │   ├── getting-document-info
    │   │   ├── get_document_info.py
    │   │   ├── get_pdf_document_info.py
    │   │   ├── get_wp_document_info.py
    │   │   ├── get_sp_document_info.py
    │   │   ├── get_pres_document_info.py
    │   │   ├── get_image_info.py
    │   │   ├── get_cad_document_info.py
    │   │   ├── get_pm_document_info.py
    │   │   ├── get_email_document_info.py
    │   │   └── (sample inputs: sample-with-toc.pdf, business-plan.doc, …)
    │   ├── loading-documents
    │   │   ├── get-default-load-options/
    │   │   ├── load-file-from-local-disk/
    │   │   ├── load-file-from-stream/
    │   │   └── load-password-protected-file/
    │   ├── converting-documents
    │   │   ├── add-watermark-to-converted-document/
    │   │   ├── convert-document-to-another-format/
    │   │   ├── convert-document-to-multiple-page-files/
    │   │   ├── convert-files-within-document-containers/
    │   │   └── get-possible-conversions/
    │   └── logging-and-diagnostics
    │       └── write_logs_to_console.py
    └── licensing
        ├── set_license_from_file.py
        └── set_metered_license.py

1. Create and activate a virtual environment:

   Create:

   Windows

   py -m venv .venv
   

   Linux

   python3 -m venv .venv
   

   macOS

   python3 -m venv .venv
   

   Activate:

   Windows

   .venv\Scripts\activate
   

   Linux

   source .venv/bin/activate
   

   macOS

   source .venv/bin/activate
   

2. Install dependencies from Examples/requirements.txt:

   Windows

   py -m pip install -r Examples/requirements.txt
   

   Linux

   python3 -m pip install -r Examples/requirements.txt
   

   macOS

   python3 -m pip install -r Examples/requirements.txt
   

3. Configure a license (optional). The suite honours the GROUPDOCS_LIC_PATH environment variable and also picks up any *.lic file dropped into the project root. Set the variable in your shell before running run_all_examples.py:

   Windows (PowerShell)

   $env:GROUPDOCS_LIC_PATH = "C:\path\to\GroupDocs.Conversion.lic"
   

   Linux

   export GROUPDOCS_LIC_PATH="/path/to/GroupDocs.Conversion.lic"
   

   macOS

   export GROUPDOCS_LIC_PATH="/path/to/GroupDocs.Conversion.lic"
   

   Note

   Learn more about licensing, evaluation limits, and how to obtain a free 30-day temporary license in the Licensing documentation topic.

From the repository root, invoke run_all_examples.py. It imports every example in order, prints a per-file status line, and exits with a pass/fail summary.

py Examples\run_all_examples.py

python3 Examples/run_all_examples.py

python3 Examples/run_all_examples.py

Change into the folder that contains the script and run it directly. Input sample files live next to each script, so relative paths resolve correctly.

cd Examples/getting-started/quick-start-guide
python convert_docx_to_pdf.py

Every example writes its output artefacts into the same folder as the script. When an example is documented on this site, the generated artefact is also linked from an output tab next to the code block — click it to download the file that a successful run produces.

The repository includes a Dockerfile that installs the ICU runtime and every Python dependency, then runs the full suite. Use it when you want a clean, reproducible Linux environment without touching your host machine:

docker build -t groupdocs-conversion-examples .
docker run --rm \
    -e GROUPDOCS_LIC_PATH=/license/GroupDocs.Conversion.lic \
    -v /path/to/your/license:/license:ro \
    groupdocs-conversion-examples

Every push to main triggers .github/workflows/run-examples.yml, which runs the entire example suite on ubuntu-latest with Python 3.13. Fork the repository and open a pull request — the workflow runs for free on GitHub-hosted runners and is a quick way to sanity-check local changes in a clean environment.

• DllNotFoundException: libgdiplus on Linux / macOS — install the platform dependencies listed in System Requirements.
• Garbled text or missing glyphs — install Microsoft TrueType fonts (ttf-mscorefonts-installer on Debian / Ubuntu; macOS already ships them). Run fc-cache -f after installing so fontconfig picks them up.
• Evaluation watermark on the output — set GROUPDOCS_LIC_PATH to a valid license file and re-run. See Licensing.
• Anything else — post on the free support forum or visit the Technical Support page.