Install PPTKit

July 15, 2026 ยท View on GitHub

This guide is for application developers installing PPTKit to build presentations. For contributing to PPTKit itself, use the Developer Workflow.

PPTKit is in pre-release development. The package API may change before the stable release.

Requirements

  • Node.js 20 or newer plus pnpm/npm for package installation and application builds
  • A modern browser for runtime-only SVG preview or browser PPTX generation

The default Core, exporter, and SVG renderer entry points do not require Node APIs at runtime in the browser. Node is required by the repository toolchain, package managers, and explicit /node entry points.

For a zero-build static page, use the official per-package ESM or global browser bundles described in Use PPTKit Directly in a Browser.

Install the packages

pnpm add @pptkit/core @pptkit/pptx-exporter @pptkit/svg-renderer

or:

npm install @pptkit/core @pptkit/pptx-exporter @pptkit/svg-renderer

Package entry points

ImportRuntime
@pptkit/coreBrowser and Node.js
@pptkit/layoutBrowser and Node.js
@pptkit/pptx-exporterBrowser-neutral generation; returns PPTX bytes and loads URL assets
@pptkit/pptx-exporter/nodeNode.js generation and file output; loads URL and local path assets
@pptkit/svg-rendererBrowser-oriented per-slide SVG preview strings; URL assets or a custom resolver
@pptkit/cliNode.js command line

The four browser-safe packages also expose a ./browser ESM subpath. Their published dist/browser/global.js files can be loaded in dependency order when import maps are not available.

For a typical application, import @pptkit/core to create and validate a presentation. Use @pptkit/pptx-exporter when the application needs bytes for a browser download, or @pptkit/pptx-exporter/node when a Node.js process should write an editable .pptx file.

Next step

Continue with the Quick Start to create and export your first deck.