Use Cases

Who uses PaperJSX and why.

PaperJSX handles text, images, tables, shapes, and charts well. Three categories of teams rely on it to replace the broken last mile of document generation.

[01] By team type

Built for teams that need the deck itself.

Not a screenshot. Not a PDF. Not a Google Slides link.

AI Agent Developers

Workflows that produce document deliverables

Reports, decks, proposals — through MCP or direct API calls. The declarative JSON schema means AI agents describe slides in structured data instead of fighting imperative APIs. Ship a PaperJSX MCP server in your agent stack.

MCP server integration
Structured JSON input
Deterministic output
No coordinate-level positioning

~150msgeneration time

SaaS Platforms

Add 'Export to PowerPoint' without building a PPTX engine

Tableau and Power BI export slides as static images. PaperJSX exports editable native objects that recipients can actually modify. White-label the output with your brand and ship it as a feature.

White-label ready
SDK or API integration
Native editable output
Custom templates per tenant

6chart types supported

Financial Services

Automated pitch books and QBRs with editable Excel charts

The editable Excel chart isn't a nice-to-have — it's the entire point. Recipients click in and see the actual data. Every chart is backed by an embedded Excel workbook. No other library under $999 can do this.

Excel-embedded charts
Master slide inheritance
Deterministic layout
OOXML spec-validated output

0repair dialogs

[02] Why teams switch

PaperJSX vs. the alternatives.

Every other approach either requires manual coordinate math, produces static images, or triggers repair dialogs.

Capability	PaperJSX	python-pptx	PptxGenJS
API surface	3 lines of JSX or JSON	47 lines for title + subtitle	30+ lines imperative JS
Charts	Editable Excel-embedded	Broken labels (issue #395)	Triggers repair dialogs
Output reliability	OOXML spec-validated	Repair-prone	Repair-prone (issue #1020)
Agent support	MCP server + JSON API	Manual imperative calls	Manual imperative calls

[03] Integration

One API call. One editable deck.

Every use case starts with the same simple contract: structured JSON in, native PPTX out.

Request

typing…

POST /api/v1/renderContent-Type: application/json{  "version": "2.0",  "title": "Q2 Board Update",  "accentColor": "#5A7A9B",  "slides": [    {      "slideType": "kpi-grid",      "title": "Key Metrics",      "items": [        { "label": "ARR", "value": "$2.4M" },        { "label": "NRR", "value": "118%" }      ]    }  ]}

Response

waiting

HTTP/1.1 200 OKContent-Type: application/vnd.openxmlformatsContent-Disposition: attachment;  filename="q2-update.pptx"X-PaperJSX-Duration: 148msX-PaperJSX-Slides: 1<binary .pptx file>

[04] Performance

Numbers teams care about.

PaperJSX is built for production throughput across every use case.

0ms

Typical generation

Slide patterns

Chart types

Output formats

Ready to ship decks from code?

100 free documents/month. No credit card required. Start with the playground or go straight to the API.

Try for free