Ms Office Powerpoint Python

Microsoft PowerPoint — Python

Companion skill to ms-office-python (parent). For other areas see: ms-office-excel-python, ms-office-word-python, ms-office-graph-python, ms-office-enterprise-sso-python, ms-office-security-python.

Overview

.pptx (Office Open XML, OOXML) is a zip of XML parts that PowerPoint understands. python-pptx is the dominant Python library for reading and writing .pptx; it manipulates the XML model directly without needing PowerPoint installed. The 2026 ecosystem state is stable but in maintenance mode — see the Gotchas section.

python-pptx does NOT render slides — it manipulates the OOXML model only. Previews, thumbnails, and PDF exports route through PowerPoint itself or LibreOffice headless (soffice --headless --convert-to pdf). Plan the pipeline accordingly.

For generating PowerPoint decks from richer content sources (Markdown, data, templates), the production-grade path lives in the presentation-builder skill family. This skill covers Python-direct work on the .pptx format itself.

Library Selection

Install Commands

RHEL 9 / AlmaLinux 9 / Rocky 9

sudo dnf install -y python3.12 python3-pip python3-devel gcc-c++ libxml2-devel libxslt-devel
python3 -m pip install --upgrade pip
python3 -m pip install python-pptx defusedxml
# Optional, for PDF / preview / Markdown:
sudo dnf install -y libreoffice-core libreoffice-impress
python3 -m pip install pypandoc

Debian 12 / Ubuntu 24.04

sudo apt update
sudo apt install -y python3.12 python3-pip python3-dev build-essential libxml2-dev libxslt1-dev
python3 -m pip install --upgrade pip
python3 -m pip install python-pptx defusedxml
sudo apt install -y libreoffice-core libreoffice-impress
python3 -m pip install pypandoc

Windows 11

winget install --id Python.Python.3.12 -e --silent
python -m pip install --upgrade pip
python -m pip install python-pptx defusedxml pypandoc
# Optional, requires PowerPoint installed:
#   python -m pip install pywin32
# Optional, headless conversion (no PowerPoint required):
#   winget install --id LibreOffice.LibreOffice -e --silent

Capability Matrix

Decision Sections

When to use python-pptx vs presentation-builder

The two paths are complementary, not exclusive. presentation-builder orchestrates higher-level pieces; python-pptx is the low-level primitive.

Preview / PDF / thumbnail generation

python-pptx produces no images. Three options for getting visual output from a .pptx:

1. LibreOffice headless — cross-platform, no PowerPoint license required:

   soffice --headless --convert-to pdf deck.pptx --outdir /tmp/out
   soffice --headless --convert-to png deck.pptx --outdir /tmp/out   # first slide only
   

2. PowerPoint COM (Windows only, requires PowerPoint installed):

   import win32com.client
   pp = win32com.client.Dispatch("PowerPoint.Application")
   pp.Visible = 1  # COM contract — required even for "headless" use
   deck = pp.Presentations.Open("deck.pptx", WithWindow=False)
   deck.SaveAs("deck.pdf", FileFormat=32)  # PDF
   deck.Close(); pp.Quit()
   

3. External render service — Graph endpoint /sites/.../drives/.../items/{id}/preview for SharePoint-hosted decks, or commercial APIs (out of scope).

LibreOffice headless contention is the same issue as with Word — use a per-process UserInstallation profile in parallel CI runs.

Slide-layout reuse vs raw shapes

python-pptx supports two distinct workflows:

• Layout-driven (preferred): open a template .pptx, iterate prs.slide_layouts, instantiate slides from layouts, fill in placeholders. Output looks consistent and lives in the same theme.
• Shape-driven (last resort): add raw text frames, rectangles, images at absolute (left, top, width, height) coordinates. Works but produces decks that feel hand-mashed; templates / themes / dark mode handling break.

Always start layout-driven. Fall back to shape-driven only when the template doesn't expose the needed placeholder.

Canonical Pattern (modified C3)

Open a template, create slides from data, save — most common PowerPoint task.

# CONFIDENCE: minimal viable pattern — production hardening notes in the Security Hardening section below; full references/ guide planned (v1.1).
from pptx import Presentation
from pptx.util import Inches

prs = Presentation("template.pptx")
title_layout = prs.slide_layouts[0]  # Title slide layout (verify index against your template)
for record in [{"title": "Q1", "subtitle": "Revenue up 12%"}, {"title": "Q2", "subtitle": "Revenue up 18%"}]:
    slide = prs.slides.add_slide(title_layout)
    slide.placeholders[0].text = record["title"]     # title placeholder
    slide.placeholders[1].text = record["subtitle"]  # subtitle placeholder
prs.save("output.pptx")

The pattern enforces three things: template-driven layouts (consistent visual), data-driven slide generation (not hand-coded shapes), no rendering side-effects (output is .pptx only — preview is a separate step).

Security Hardening

See ms-office-security-python for the consolidated checklist. Area-specific items:

• Pair python-pptx with defusedxml. python-pptx uses lxml internally; the OOXML parsing path is XXE-exposed in older lxml versions.
• For untrusted .pptx input, parse in a sandboxed subprocess or container. Embedded OLE objects, linked media, and external relationships can pull in arbitrary network content if the deck is later opened in PowerPoint.
• Inspect prs.core_properties (author, last_modified_by, comments, keywords) before publishing externally — PII / internal usernames live here.
• Slides can carry slide notes that are not displayed but ship with the file. When generating decks from internal data, ensure speaker-notes content is intentional — don't leak comments / TODOs.
• Embedded media files (videos, audio) increase deck size and can carry their own malicious payloads. Strip or replace slide.shapes of type Media before publishing externally if provenance is unclear.
• When converting .pptx to PDF via LibreOffice headless, run with --norestore --nodefault --headless --env:UserInstallation=file:///tmp/lo-user-$$ in parallel CI to avoid lockfile contention.
• Refuse to process decks larger than a hard MAX_BYTES cap (e.g. 200 MB). Real decks usually fit; pathological ones don't.
• Embedded fonts (in some templates) carry copyright metadata. Ensure license compatibility before redistributing.

Selection Cheatsheet

• "Read a .pptx programmatically" → python-pptx
• "Generate a deck from data + template" → python-pptx with layout-driven flow
• "Generate a deck from Markdown" → pypandoc OR the presentation-builder skill family
• "Convert .pptx → PDF on Linux" → LibreOffice headless
• "Convert .pptx → PDF on Windows with PowerPoint" → pywin32 COM (legacy; LibreOffice also works)
• "Generate slide-N thumbnails" → LibreOffice headless or external service (no Python-direct option)
• "Read speaker notes" → slide.notes_slide.notes_text_frame.text

Gotchas

• python-pptx is in maintenance mode as of 2026-05 — stable, minor releases, no major roadmap. It will continue to work for current OOXML, but if Office formats evolve significantly the response may lag. Pin a known-good version, run pip-audit regularly (delegate to dep-currency-check), and watch the GitHub repo.
• python-pptx does NOT render — no thumbnails, no PDF, no images. This bites every newcomer; plan the rendering step explicitly.
• Slide-layout indices are template-specific. Hardcoding prs.slide_layouts[0] works for the default template but breaks the moment someone substitutes a customised template. Look up by layout.name for portable code.
• Embedded charts in python-pptx are basic (bar, line, pie). Sankeys, treemaps, complex composites must be pre-rendered as images and inserted as Picture shapes.
• Speaker notes silently inherit theme fonts; setting notes.text_frame.text = ... strips font / colour. Use notes.text_frame.paragraphs[0].add_run(...) for styled notes.
• prs.save(path) overwrites without warning. Layer file-existence checks if overwrite is undesirable.
• python-pptx cannot edit .ppt (legacy Office 97-2003 PowerPoint format). Convert through LibreOffice first.

Platform routing — rendering is the only OS-dependent step

python-pptx itself is pure Python and behaves identically on Windows, macOS and Linux. The split appears the moment you need a PDF or a thumbnail, because python-pptx renders nothing:

LibreOffice headless is the only row that is green everywhere, which makes it the default for any pipeline that has to run on more than one machine. There is no COM on macOS — the Mac path is Apple Events, and it cannot be granted headlessly, so it is unavailable on CI exactly as COM is on Linux. See ms-office-python/references/macos-automation.md.

Update Triggers (per Codex M-1 — alf will scan these)

• Major version bump of: python-pptx, lxml, pypandoc.
• New OOXML / .pptx schema change announced by Microsoft (rare but happens).
• CVE published against lxml (XXE class).
• LibreOffice CLI flag changes for the --convert-to family.
• python-pptx moving back to active development (would unlock chart / animation coverage).
• Annual review on: 2027-05-22.

See Also