Choosing a package

Begin with the integrated toolkit. Move to a lower-level package only when your application needs to own document semantics or the command lifecycle directly.

Decision guide

Your application needs to…Start with

Render, preview, or run an integrated editor sessionpptx-glimpse

Read OOXML semantics, author, edit, or write directly@pptx-glimpse/document

Own rendering and writing, but add command history@pptx-glimpse/editor

pptx-glimpse

This is the recommended starting point for most applications. It converts PPTX to SVG or PNG and provides the integrated edit, rerender, history, and save session used by this site’s demo. It supports Node.js and browser bundles.

Resources

@pptx-glimpse/document

Reads typed source data, derives effective values through a computed view, authors new presentations, edits supported existing content, and writes PPTX with round-trip preservation. It does not render SVG or PNG.

Resources

@pptx-glimpse/editor

Adds validated commands, selection, warnings, and undo/redo history to a document source model. It has no DOM, UI framework, renderer, or file I/O and is currently a 0.x package.