Stateful PPTX operations
DeckUse keeps working on the same PowerPoint document with explicit operations, persistent working state, validation, and traceable output. Current reviewed behavior is scoped to existing PPTX.
COMPARE
Differences you can verify against source.
This page only states differences that point back to a Product page or a public repository. It does not claim speed, accuracy rates, or market share.
Evidence-backed differences
Four differences that matter for agents.
One bounded document task
DeckOps finishes one explicit document job from input to result without a long-lived workspace. Treat format coverage as future-state until a release proves it.
HTML and Office interchange
DeckHTML moves content between Office files and the web. The current path converts HTML, URL, stdin, or SVG to PPTX or PNG. Dedicated DOCX routes are planned.
Open-source repositories
The three Products publish under the DeckFlow GitHub organization. Licenses and release evidence differ by repository—review each product page before relying on a claim.
FAQ
Frequently asked questions
DeckFlow separates Products by document job lifetime: stateful PPTX work (DeckUse), one bounded task (DeckOps), and Office↔web conversion (DeckHTML). Claims stay inside release evidence and public repositories.
Open the DeckUse, DeckOps, and DeckHTML product pages for boundaries, and the public GitHub organization for source. Do not rely on unverified speed, accuracy, or market-share claims.