Open source · Apache-2.0 · TypeScript
Open-source PowerPoint viewer and WYSIWYG editor for React, Vue 3, Angular, Svelte 5, and vanilla JavaScript. A headless TypeScript core loads, edits, and saves .pptx files; the components render them as live HTML, CSS, and SVG.
npm i pptx-react-viewerLive demo
This is the real editor running in your browser: the same deployed demo app you would get from npm, embedded live. Switch frameworks, or split the view and watch two independent apps co-edit one deck.
Features
187+ preset shapes, 23 chart types, SmartArt, animations, morph transitions, embedded fonts, EMF and WMF metafiles, and 3D models, all drawn as HTML, CSS, and SVG. Text stays selectable and screen readers keep working.
Rendering →A ribbon, inspector panels, and on-canvas manipulation for text, shapes, tables, charts, and SmartArt, with full undo history. Master and layout elements are editable too.
Editing →Loading produces a fully-typed data model with sixteen element types. Saving writes valid OpenXML with themes, masters, layouts, and OOXML Strict conformance intact, so edited decks reopen cleanly in PowerPoint.
Load and save →Co-edit through a Yjs CRDT with presence tracking, character-level text merging, and a peer-to-peer transport that needs no server.
Collaboration →PNG, JPEG, SVG, PDF, GIF, and video straight from the browser. SVG export also runs headlessly in Node.js with no DOM.
Export →Open and save password-protected files with AES-128 and AES-256 agile encryption.
Encryption →Create decks programmatically with the fluent builder, or convert them to clean Markdown or positioned HTML with media extraction and speaker notes.
Builder API →Every UI label resolves through one of 1,600+ pptx.* translation keys, wired to the i18n library your app already uses: react-i18next, vue-i18n, or ngx-translate.
Localization →Automation
pptx-viewer-mcp exposes 50+ PPTX tools with Zod schemas over the Model Context Protocol, so Claude, Cursor, and Copilot can read, edit, and convert presentations directly. The same functions run headlessly in Node, Bun, or serverless runtimes, and a CLI covers one-off conversions.
MCP and tools →
{
"mcpServers": {
"pptx": {
"command": "npx",
"args": ["pptx-viewer-mcp"]
}
}
}import { PptxHandler } from 'pptx-viewer-core';
const handler = new PptxHandler();
const deck = await handler.load(bytes);
// Every element is a typed, discriminated union
for (const el of deck.slides[0].elements) {
if (el.type === 'text') el.text = rebrand(el.text);
}
// Serialize straight back to a valid .pptx
const file = await handler.save(deck.slides);Quickstart
Install the package for your framework, pass the raw .pptx bytes, and give the container a height. Editing, presenting, collaboration, and export are props away.
import { PowerPointViewer } from 'pptx-react-viewer';
import { useEffect, useState } from 'react';
import 'pptx-react-viewer/styles';
export function Deck() {
const [content, setContent] = useState<Uint8Array | null>(null);
useEffect(() => {
fetch('/deck.pptx')
.then((r) => r.arrayBuffer())
.then((buf) => setContent(new Uint8Array(buf)));
}, []);
if (!content) return <div>Loading...</div>;
return (
<div style={{ height: '100vh' }}>
<PowerPointViewer content={content} canEdit />
</div>
);
}FAQ
Yes. Everything is Apache-2.0 licensed: the core, all five UI packages, the MCP server, and the demos. There is no paid tier.
Yes. Saving writes valid OpenXML with themes, masters, layouts, and OOXML Strict conformance preserved, so a deck loaded, edited, and saved here reopens cleanly in PowerPoint.
No. Parsing, rendering, editing, and saving all happen in the browser. The core also runs in Node.js and Bun for server-side or CLI work.
As live HTML, CSS, and SVG rather than a canvas bitmap. Text stays selectable, zoom stays sharp, and screen readers work.
Not by default. The bundled transport is peer-to-peer (y-webrtc), which works from static hosting. For persistence and authentication you can point it at a y-websocket relay instead. Collaboration →
Yes. AES-128 and AES-256 agile encryption are supported for both opening and saving.
React 19, Vue 3, Angular, Svelte 5, and a zero-framework vanilla build. Each package bundles the same core engine, so rendering is identical everywhere.
OLE objects are read-only and a few visual effects are approximated on screen. The limitations page lists exactly what to expect. Limitations →
Get started
Add PowerPoint support to your app with one dependency. Apache-2.0 licensed, strict TypeScript, no native dependencies. Try the demo with one of your own decks, then follow the quick start.