01Current, release-scoped
DeckUse
Create a controlled PowerPoint variant or maintain an existing deck with inspectable changes.
Follow the current existing-PPTX lifecycle: init, inspect or query, apply, validate, then commit.
DEVELOPERS
Start with the document job. Follow a real technical path.
Choose DeckUse, DeckOps, or HTML2Deck, then inspect the version, source, lifecycle, and limitations behind the path you plan to build on.
| Status | Boundary |
|---|---|
| DeckUse | 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. |
| DeckOps | Reviewed DeckOps source supports parse and convert for PDF, PPTX, and DOCX with format-specific limits. Extract, modify, and export are reserved. CLI parsing is local by default; the browser entry uses cloud services. |
| HTML2Deck | Reviewed HTML2Deck source documents HTML, URL, stdin, and SVG to PPTX or PNG. Editability varies and some content may be rasterized. Dedicated DOCX routes are not established by this review. Free, licensed, and cloud modes have separate limits. |
Architecture and paths
Choose by document job.
The three Products have different responsibilities and lifecycle boundaries.
02Reviewed source
DeckOps
Turn complex documents into reliable knowledge.
Reviewed DeckOps source supports parse and convert for PDF, PPTX, and DOCX with format-specific limits. Extract, modify, and export are reserved. CLI parsing is local by default; the browser entry uses cloud services.
03Reviewed source
HTML2Deck
Turn web-authored work into editable delivery files.
Use the current HTML, URL, stdin, or SVG to PPTX or PNG path, then review the result.
First technical evidence
Inspect the first technical evidence.
Follow the linked source for commands, prerequisites, and version-specific limits.
DeckUse
Current, release-scopedExisting PPTX lifecycle
Version-scoped path
Current, release-scopedinit
inspect/query
apply
validate
commit
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.
DeckOps
Reviewed sourceArchitecture and status
Grounded explanatory architecture
Reviewed sourcedocument
parse
IR
convert
Markdown
Reviewed DeckOps source supports parse and convert for PDF, PPTX, and DOCX with format-specific limits. Extract, modify, and export are reserved. CLI parsing is local by default; the browser entry uses cloud services.
HTML2Deck
Reviewed sourceCurrent conversion direction
Version-scoped path
Reviewed sourceHTML / URL / stdin / SVG
PPTX / PNG
PPTX-to-web is testing. Dedicated DOCX paths are planned. Supported content may remain editable; unsupported content may be simplified or rasterized.
Contract governance
Lifecycle and limits
Status is part of the technical contract, not a decorative badge.
- DeckUse
- 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.
- DeckOps
- Reviewed DeckOps source supports parse and convert for PDF, PPTX, and DOCX with format-specific limits. Extract, modify, and export are reserved. CLI parsing is local by default; the browser entry uses cloud services.
- HTML2Deck
- Reviewed HTML2Deck source documents HTML, URL, stdin, and SVG to PPTX or PNG. Editability varies and some content may be rasterized. Dedicated DOCX routes are not established by this review. Free, licensed, and cloud modes have separate limits.
Developer Docs handoffs
Continue in maintained technical sources.
Supporting projects appear here only as direct technical handoffs, never as primary Products or website destinations.
DeckUse
Source and quickstart / AGPL-3.0Open source (opens in a new tab)
DeckOps
Reviewed sourceOpen context (opens in a new tab)
HTML2Deck
Reviewed sourceView HTML2Deck usage (opens in a new tab)
DeckProbe
Apache-2.0 · 2e5d064View DeckProbe source (opens in a new tab)
DeckRender
Apache-2.0 · 5ed4bdbView DeckRender source (opens in a new tab)
Developer Docs
External documentation / EnglishRead the Docs (English) (opens in a new tab)
Product-owned technical depth
Keep technical depth with its Product.
DeckUse
Runtime details stay with the DeckUse Product path. Use maintained source and Docs for implementation details.
Product pathDeckOps
IR and Parse details stay with DeckOps Docs. Parse is an internal stage, not a website destination.
Product pathHTML2Deck
Conversion directions and format limits stay with the HTML2Deck Product path and maintained source.
Product pathImplementation documentation is currently available in English. Read the Docs (English) (opens in a new tab)
FAQ
Frequently asked questions
What is DeckFlow?
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.
How do I choose among DeckUse, DeckOps, and HTML2Deck?
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.
Is DeckFlow open source?
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.
Which formats are supported today?
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.
How does DeckFlow pricing work?
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.
Are Solutions a fourth product?
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.