WolfPPT - Documentation
How do I use WolfPPT to edit existing PowerPoint decks in Python?
Use WolfPPT Community to open, inspect, edit, and save existing PPTX presentations from Python. Start with the published 0.1.6 examples below; native rendering and source-bound reporting are separate Commercial workflows, and the wolf command belongs to Wolf Runtime.
Last updated: November 9, 2026.
Documentation topics
- How do I install WolfPPT Community, Commercial, or Wolf Runtime?
- How do I open, inspect, edit, and save a PPTX with WolfPPT?
- Which WolfPPT Python APIs work in the published 0.1.6 package?
- How do I edit PPTX text, table cells, and chart data with WolfPPT?
- How do I copy, reorder, and delete slides with WolfPPT?
- How do I render PPTX to PDF and PNG with WolfPPT Commercial?
- How do I refresh a PPTX report and handle WolfPPT refusals?
- How do I migrate python-pptx code to WolfPPT without assuming full compatibility?
Choose the workflow before installing
These docs separate package editing from rendering and guarded report publication. That distinction matters when an example looks familiar but imports a module that your installed wheel does not include. Community examples here were executed with wolfppt 0.1.6 from public PyPI. Commercial examples were checked against engine source and named tests, not executed against an authenticated Commercial installation.
Begin with installation if you need to identify the distribution and version. Continue to the quickstart for a complete create, save, reopen, inspect, edit, and save sequence. The input is deliberately synthetic so that the example does not depend on a private template, a particular shape name, or a reporting fixture that is unavailable in the public package.
Getting started, API, features, and migration
The topic map below is organized around tasks rather than a list of product promises. The API reference documents the exercised entry points for the published package. Text, tables, and charts explains when to edit a run, select a cell, or replace a category chart dataset. Slides and layouts covers layout inspection, placeholders, same-presentation duplication, movement, and removal.
Rendering describes explicit font admission, PDF and PNG selection, and output publication in Commercial. Reports and refusals explains source hashes, expected old values, target discovery, and receipts. Migration and limits gives a package-member comparison you can run before making a controlled change to your own python-pptx workflow. Read that boundary before replacing imports across an application.
Complete example
from wolfppt import Presentation
prs = Presentation()
slide = prs.slides.add_slide(prs.slide_layouts[6])
slide.shapes.add_textbox(0, 0, 3657600, 914400).text = "Monthly review"
prs.save("docs-example.pptx")
print(len(Presentation("docs-example.pptx").slides))A first package-only example
Install wolfppt==0.1.6, then run this Python script in a directory where the named output does not contain valuable work. It creates one blank-layout slide with one text box, writes the presentation, and opens the saved file again. Printing one confirms that this particular output can be reopened and that it contains one slide. It is not a rendering or Open XML schema-validation result.
Geometry is expressed directly in English Metric Units, or EMUs. The examples use integer coordinates so they do not depend on helper modules absent from the published 0.1.6 wheel. The chart topic explicitly installs python-pptx for chart-data containers and enums. That dependency is stated locally rather than implied to be part of WolfPPT.
Evaluation boundary
A reader landing on any topic should be able to tell what to install, which interface owns the operation, what the example changes, and which claims stop at the saved package. Use the topic links as a checklist when evaluating an existing automation job. If a workflow needs another dependency or edition, that prerequisite is stated on the topic rather than hidden behind a shared installation command.
Example projects
Each project is a complete folder you can run: a self-made sample document, the script that edits it, a requirements.txt that pins the Wolf release and every dependency with hashes, and the output the run prints. Download the zip, or read every file in the one-page Markdown source listing.
- Update a deck's table, chart and text (wolfppt==0.1.6): Fills a quarterly review deck's Q3 table column, chart series and subtitle with the python-pptx object model, then shows that every package part it did not edit is byte-for-byte identical. Download pptx-update-deck.zip or read the source listing.
What it does not do
- These pages are an exercised API subset, not an exhaustive promise of python-pptx behavioral compatibility.
- Preserving an unedited package member does not mean the renderer understands or displays its contents.
- Community 0.1.6 does not include the wolfppt.util, wolfppt.enum, or wolfppt.chart convenience modules used by newer source examples.
- No PowerPoint GUI rendering parity is claimed. Check the actual output for your fonts, content, and intended use.