Skip to content

POWERPOINT · LOSSLESS RUNTIME

Create, edit, and refine PowerPoint with AI.

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.

Existing-PPTX editing is current at the reviewed boundary. Controlled creation requires a release-verified template or defined-case command path. Word and Excel are planned.

View DeckUse on GitHub

Why lossless

Lossless 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.

  • Surgical minimal changes reduce the risk of damaging layouts, notes, assets, and unrelated slides.
  • Versioned workspaces and operation logs make mistakes easier to trace and recover from.
  • Structured queries and explicit commands keep agents away from raw OOXML.
  • Package validation catches structural problems before export.
SourceUntouched document state

Layouts, notes, assets, and unrelated slides remain outside the requested change.

Supported operationExplicit minimal change

The agent inspects first, then applies a supported operation to the intended target.

ResultInspectable document state

The result can be compared, validated, and recovered within the release boundary.

GROUNDED EXPLANATORY ARTIFACT · BOUNDED PRESERVATION MODEL

Real operation lifecycle

DeckUse is local-first and schema-driven, with explicit, Git-backed, auditable operations on versioned PowerPoint workspaces.

OPERATION PIPELINE
REAL CONTRACT · 417CB9A / SOURCE 1.0.1
  1. 01STEP
    init
  2. 02STEP
    inspect / query
  3. 03STEP
    apply
  4. 04STEP
    validate
  5. 05STEP
    commit / export

What is current

Current behavior, release-scoped paths, and planned formats are separate claims.

Existing-PPTX editingCurrent at the reviewed boundary

Current reviewed proof remains scoped to existing-PPTX behavior in source snapshot 417cb9a / package source 1.0.1.

Controlled creation and commandsRelease-scoped

Requires a release-verified template or defined-case command path, with fixtures that prove the claim.

Word and ExcelPlanned

These formats are Product direction, not current editing or deployment capabilities.

Boundaries

The release boundary is part of the Product, not fine print.

Preservation

Lossless does not mean byte-identical ZIP output, perfect preservation for every PowerPoint feature, or an unlimited zero-collateral-change guarantee.

Formats

DeckUse is not a current Word, Excel, Keynote, or Numbers editor. Word and Excel are planned; Keynote and Numbers are absent.

Target contract

Complete render, visual diff, restore, and branching experiences require new release evidence and are not current claims.

Remote

Remote collaboration is exploratory. It is not presented as available or security-proven.

Product relationship

Choose by document job. DeckUse and DeckOps remain distinct Products with distinct lifecycle boundaries.

PowerPoint runtime

DeckUse

Create, edit, and refine PowerPoint through explicit, Git-backed, auditable operations on versioned PowerPoint workspaces.

Document intelligence

DeckOps

Turn complex documents into reliable knowledge through the DeckOps Product path and its own release boundary.

Compare with DeckOps
For developers

Frequently asked questions

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 DeckHTML—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. DeckHTML moves content between Office files and the web.

Yes. DeckUse is AGPL-3.0. DeckHTML, DeckProbe, and DeckRender are MIT. DeckOps does not yet have an effective repository license on the public legacy repository.

DeckUse current reviewed behavior is scoped to existing PPTX. DeckHTML 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 DeckHTML 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.

Follow the verified DeckUse path.

DeckUse is AGPL-3.0 licensed. The software license is distinct from any future cloud or commercial terms.

View DeckUse on GitHubFor developers

Related resources