Editable objects
Supported content is recreated as PowerPoint objects that can be inspected and edited in the resulting file.
WEB CONTENT · EDITABLE DOCUMENT BRIDGE
HTML2Deck turns web content into high-fidelity, editable PPTX and DOCX files—and turns documents back into shareable web pages.
Current at v0.7.2: HTML/URL/stdin/SVG to PPTX or PNG. Testing: PPTX to web. Planned: dedicated DOCX routes.
| Status | Boundary |
|---|---|
| Current | HTML files, URLs, stdin, and SVG to PPTX or PNG (v0.7.2). |
| Release-scoped | PPTX to web (testing). |
| Planned | Dedicated web-to-DOCX and DOCX-to-web routes. |
At v0.7.2, HTML2Deck accepts HTML files, URLs, stdin, or SVG and produces PPTX or PNG through Chromium-rendered DOM inspection and computed layout and styles.
Available now: Chromium-rendered DOM inspection, computed layout/styles, and HTML/SVG-to-PPTX or PNG conversion.
Supported content is recreated as PowerPoint objects that can be inspected and edited in the resulting file.
Unsupported content may be simplified or rasterized. Editability and degradation must be reviewed against the exact fixture.
Product direction: separate PowerPoint and Word flows with artifact-specific contracts, plus Office-to-HTML sharing paths.
Current path · v0.7.2 · HTML / URL / stdin / SVG → PPTX or PNG · editability varies
Supported content is recreated as PowerPoint objects that can be inspected and edited in the resulting file.
Unsupported content may be simplified or rasterized. Editability and degradation must be reviewed against the exact fixture.
GROUNDED EXPLANATORY ARTIFACT · v0.7.2
Local, cloud, and automatic modes may be described only where the named release documents their environment, authentication, upload, and cloud boundaries. Quality, privacy, retention, and pricing are not inferred from the software release.
View HTML2Deck usageMaintain or create release-scoped PowerPoint work with inspectable changes.
Understand the future-state route-to-IR contract and its evidence boundary.
Bridge web-authored content to current PPTX or PNG delivery paths.
Answers 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.
Choose by the lifetime of the work. DeckUse keeps working on the same document with persistent state. DeckOps finishes one bounded document task. HTML2Deck moves content between Office files and the web.
DeckUse is AGPL-3.0. DeckProbe and DeckRender are MIT. HTML2Deck is proprietary. DeckOps does not yet have an effective repository license on the public legacy repository.
DeckUse current reviewed behavior is scoped to existing PPTX. HTML2Deck current path converts HTML, URL, stdin, or SVG to PPTX or PNG. DeckOps remains a future-state product contract until a release proves format-specific IR claims.
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.
Current release: v0.7.2. PPTX-to-web is testing; dedicated DOCX routes are planned.