Preservation
Lossless does not mean byte-identical ZIP output, perfect preservation for every PowerPoint feature, or an unlimited zero-collateral-change guarantee.
POWERPOINT · LOSSLESS RUNTIME
DeckUse lets you use AI to create, edit, and refine PowerPoint—from templates or existing decks—while keeping every change inspectable, comparable, and recoverable across repeated edits.
The lossless PowerPoint runtime for agents.
Reviewed DeckUse community source implements PPTX and DOCX editing. XLSX, Keynote, and Numbers are not implemented. Rendering supports review; it does not certify visual quality.
View DeckUse on GitHubLossless means preserving untouched content within supported operations. It does not mean byte-identical ZIP output, perfect preservation for every PowerPoint feature, or an unlimited zero-collateral-change guarantee.
Layouts, notes, assets, and unrelated slides remain outside the requested change.
The agent inspects first, then applies a supported operation to the intended target.
The result can be compared, validated, and recovered within the release boundary.
DeckUse is local-first and schema-driven, with explicit, Git-backed, auditable operations on versioned PowerPoint workspaces.
initinspect / queryapplyvalidatecommit / exportCurrent behavior, release-scoped paths, and planned formats are separate claims.
Reviewed DeckUse community source implements PPTX and DOCX editing. XLSX, Keynote, and Numbers are not implemented. Rendering supports review; it does not certify visual quality.
The release boundary is part of the Product, not fine print.
Lossless does not mean byte-identical ZIP output, perfect preservation for every PowerPoint feature, or an unlimited zero-collateral-change guarantee.
Reviewed DeckUse community source implements PPTX and DOCX editing. XLSX, Keynote, and Numbers are not implemented. Rendering supports review; it does not certify visual quality.
Complete render, visual diff, restore, and branching experiences require new release evidence and are not current claims.
Remote collaboration is exploratory. It is not presented as available or security-proven.
Choose by document job. DeckUse and DeckOps remain distinct Products with distinct lifecycle boundaries.
Create, edit, and refine PowerPoint through explicit, Git-backed, auditable operations on versioned PowerPoint workspaces.
Turn complex documents into reliable knowledge through the DeckOps Product path and its own release boundary.
Compare with DeckOpsAnswers about DeckFlow Products, open source, formats, and pricing.
DeckFlow is open-source document infrastructure for AI agents. It gives agents three Product paths—DeckUse, DeckOps, and HTML2Deck—plus ready-to-use Solutions for presentation and document workflows.
DeckUse edits PPTX and DOCX; DeckOps parses documents into IR and Markdown; HTML2Deck converts web content to PPTX or PNG. Support depends on the reviewed version and mode.
DeckUse community: AGPL-3.0. DeckOps source and releases from 2.0.0: AGPL-3.0-only; earlier releases keep their own licenses. DeckProbe and DeckRender reviewed source: Apache-2.0. HTML2Deck: proprietary. Commercial editions and cloud terms are separate.
DeckUse edits PPTX and DOCX; DeckOps parses documents into IR and Markdown; HTML2Deck converts web content to PPTX or PNG. Support depends on the reviewed version and mode.
DeckFlow uses one-time Credit packs. Credits pay for supported DeckUse, DeckOps, and HTML2Deck tasks as each Product's current release allows. See the pricing page for pack sizes.
No. Solutions are job-led workflows—such as translate, generate, and revamp—that run on the Product paths. They are not a separate Product layer.
DeckUse is AGPL-3.0 licensed. The software license is distinct from any future cloud or commercial terms.