Presentation toolUpdated 2026.11.05

PPT Master Tutorial: Install It and Export Editable PowerPoint

Install PPT Master from GitHub and export editable PowerPoint, with Windows setup and native chart-data guidance.

Aaron recommends Open official GitHub

PPT Master is Hugo He's open-source workflow for AI agents that can read files and run commands, turning documents or a topic into editable PowerPoint. Its native text and shapes remain editable; updating chart values through PowerPoint's Edit Data requires the separate native chart/table export. It suits people who already have source material and need a deck they can revise, with a final content and layout review before delivery. Official README, export FAQ.

Official links: GitHub repository · v6.8.0 downloads · Windows setup
Version and source check: v6.8.0, released October 30, 2026; official documentation and issue discussions checked November 5, 2026.

Decide what needs to remain editable

Moving a title and changing a chart's numbers are different requirements. Default shape export is a starting point for text, position and color changes. For a monthly report that someone will update through chart data or table controls, request native PowerPoint Chart/Table objects. Official FAQ.

PPT Master export decision: use default shapes for text, position and color changes; choose the supported native chart/table export when chart values or table structure must remain editable.

What must change? Export choice Delivery check
Text, position or color Default editable shapes Select, edit, move and save the objects
Chart data or table-specific controls --native-charts-and-tables Open Edit Data for a supported chart; confirm the table is a native Table

Default shape export has no chart data workbook. The native option covers supported data charts and plain text-grid tables, so it is not a promise that every graphic becomes a data-backed chart. Microsoft PowerPoint is the project's primary validation target; other presentation apps may render the objects differently. Official FAQ.

Download, install and make a first deck

These steps summarize the v6.8.0 documentation. Installing the workflow does not include an AI host account or a model usage allowance. Getting Started.

  1. Prepare a supported Python and agent host. The documented Python range is 3.10–3.14. On Windows, add Python to PATH. Use an agent host with access to the working folder and shell commands, such as the hosts listed in the official guide. Windows setup, host requirements.
  2. Choose the download. Use Code → Download ZIP or clone the original repository. If the full download is too large, the release page also provides ppt-master-skill-v6.8.0.zip, without the repository's bundled example decks. Official README.
  3. Install the matching dependencies. From a full repository's root, Windows users can follow the commands below. A skill-only installation instead uses requirements.txt in the installed skill directory. The documented npx skills add hugohe3/ppt-master route also needs those Python dependencies. Getting Started.
python --version
python -m pip install -r requirements.txt

For a skill-only installation:

python -m pip install -r "<installed-skill-dir>/requirements.txt"
  1. Open the writable working folder and provide the brief. Name the source file, audience, decision, slide count, ratio and facts that must not change. The default route confirms the brief and design before production. Quick removes that interaction, so a clear brief matters more. The active project's path is reported by the agent; its default output is under <active-project>/exports/, not a generic repository-root exports/. Getting Started.

Example brief, written for this guide:

Use sources/product-brief.docx to create eight 16:9 slides for a department manager deciding whether to proceed to another evaluation round. List missing information and confirm the direction first. Do not invent data. Identify whether charts that need monthly updates can use the native chart export.

Before delivery, open the PPTX and check source values, text overflow and the objects that colleagues must edit. For a chart that needs updates, check Edit Data too. See the editable PowerPoint delivery checks.

What changes in v6.8.0?

  • Image backend default: the project's release notes name gpt-image-2.5-sunburst as the OpenAI backend default, with OPENAI_MODEL available to override it. This is a PPT Master configuration value; confirm model access and prices with the provider. Release notes.
  • Arbitrary positive W:H ratios: a request can specify ratios such as 16:9, 4:1 or 1.85:1. The backend selects a nearby size supported by its model, then placement follows the target crop policy. A ratio request does not guarantee those exact output pixels. Image reference.
  • Python support capped at 3.14: the release notes identify dependency wheel problems on Python 3.15. Check the supported version before treating a source-build error as a PPT Master failure. Release notes.

For work slides, decide which faces, product marks or text must stay inside the crop before generating images. Checking the placed result is more useful than assuming a correctly entered ratio protects important content. This is an editorial recommendation based on the documented size/crop distinction.

Troubleshooting: identify the failing layer

Symptom Check first Source
python opens Microsoft Store or is not found Python installation and PATH Windows guide
Missing modules Use python -m pip for the Python that runs the workflow; check the dependency-file location Windows guide
A dependency falls back to a source build Confirm Python 3.10–3.14 before changing other components Windows guide
Imported template reports has no positive source frame Keep the conversion report and check the affected version; do not delete visible rules to suppress the error Issue #329

In #329, a user reported a corporate-template import blocked by degenerate geometry. The maintainer corrected the geometry handling, and the reporter confirmed that the path completed. The useful lesson is to inspect whether diagnostics correspond to missing or displaced content, rather than discarding every warning or removing objects indiscriminately. Maintainer explanation and follow-up.

Costs, data and limits

The project uses the MIT License. Agent plans, model usage and optional image services have their own billing. Budget the program's license, agent/model access and image sources separately instead of treating an open-source download as an entirely free production chain. License, provider and image routes.

A workflow running in your working environment can still send material to a cloud agent or image provider. Check your organization's rules for source documents and the rights to photos, logos and templates before using them. This is a work-planning recommendation, not a confidentiality promise about a service.

Next steps

Sources and verification date

Checked November 5, 2026, against v6.8.0, released October 30, 2026. Technical documentation is pinned to that tag; the issue discussion and repository metadata are dated observations.

  1. Official README: purpose, download routes, image services and limits.
  2. v6.8.0 release notes: image backend, ratios and Python changes.
  3. Getting Started: prerequisites, folder roles, dependencies and output location.
  4. Windows installation guide: supported Python versions and troubleshooting.
  5. FAQ: shape export versus native chart/table objects.
  6. Image-generation reference: target ratios, supported backend sizes and cropping.
  7. Issue #329 and maintainer/reporter follow-up: the template-geometry case.
  8. MIT License.