@office-kit/pptx

Read, edit, and write .pptx (Office Open XML Presentation) files from TypeScript, in Node.js and the browser, from a single ESM bundle.

Create slides with AI · Documentation · Playground (inspect a deck in your browser) · REPL (write code, watch the deck redraw)

import { loadPresentation, replaceTokensInPresentation, savePresentation } from '@office-kit/pptx';

// A designer makes template.pptx in a presentation app. Your code fills it in.
const pres = await loadPresentation(templateBytes);
replaceTokensInPresentation(pres, { name: 'Alice', event: 'Re:Invent', date: '2026-12-01' });
const out: Uint8Array = await savePresentation(pres);

Status: 0.x, pre-1.0. The capabilities in the scope table are exercised against real PPTX fixtures and validated in CI (see How output is checked). Until 1.0 the public API is not frozen: a breaking change can land in a minor (0.x) release, so pin a version or an exact range.

Create slides with AI and live preview

Create presentations in TSX with a live browser preview and Claude Code or Codex beside the slide. Select an area and ask the agent to change it, edit text directly, and export an editable .pptx file. Changes are saved in the TSX source; saving a source file also updates the preview.

Requires Node.js 22.18 or later. Create a project and start the preview in one command (macOS/Linux):

npx --yes @office-kit/pptx-dev@latest init my-slides && cd my-slides && npm install && npm run dev

Open the local URL printed by the server. The generated project includes deck.tsx, individual slides, a shared theme and a CLAUDE.md authoring guide. For later sessions, run this inside the project:

npx office-pptx dev deck.tsx

npm run dev starts the same preview. To update an existing project's dev tools, stop the server, then run:

npm install -D @office-kit/pptx-dev@latest
npm run dev

Run npm run check to type-check the deck and npm run build to export deck.pptx. AI editing uses your locally installed and authenticated Claude Code or Codex CLI. After edits, changed-slide screenshots are supplied to the agent for design review; capture requires Chrome or Playwright Chromium.

See the preview and agent setup, selection, text editing and visual review, and TSX element reference. To let Claude Code handle project setup as well, follow the skill installation guide.

Why this library

• It reads as well as it writes. Open a deck made in Keynote, Google Slides or any other presentation app, change it, and save it. Every setter has a getter, and there are deck-wide queries (find every hyperlink, every comment by an author, every slide with an empty title).
• Parts it does not model survive the round trip. SmartArt, OLE objects, video, modern threaded comments, and vendor extensions are carried through untouched. The library never silently strips what it does not understand.
• The output is valid, not "valid enough". The Open XML SDK's OpenXmlValidator gates every CI run. A file that opens in one presentation app but breaks Keynote is treated as a bug.
• One ESM bundle for Node and the browser. No fs, Buffer, or zlib on the hot path, and one runtime dependency (fflate, for ZIP).
• You ship only what you import. The API uses side-effect-free functions. CI checks tree-shaking and bundle-size limits (test/tree-shake.test.ts).
• Types follow the spec. The model mirrors ECMA-376 Part 1 §19 (PresentationML). Positions are branded Emu numbers, so inches and points cannot be mixed up by accident.

How it differs from PptxGenJS

PptxGenJS is the established way to generate a deck in JavaScript, and it is good at that job. The difference is direction: PptxGenJS writes new files; @office-kit/pptx reads, edits, and writes. If your deck starts from a template, or from a file a person made, PptxGenJS cannot open it.

Compared against PptxGenJS 4.0.1:

This is the beginning of the README. Read the rest at the original. Read the full README ↗