Use DeckCraft when the deck is yours, when you want it on Linux, when you want an agent to drive it, or when a licence line item is a problem. Use PowerPoint when the deck has to survive a round trip through someone else's Microsoft 365, or when the deck contains charts, SmartArt or embedded media that other people will edit. The honest middle: DeckCraft builds and presents decks today; it does not yet receive them safely.
Side by side
| DeckCraft | Microsoft PowerPoint | |
|---|---|---|
| Licence | MIT or Apache-2.0, free, no account, no telemetry | Microsoft 365 subscription; a limited free tier exists for the web version |
| Written in | Rust | TypeScript / C++ / Objective-C across desktop and web |
| Maturity | alpha — self-rated ~55% ready, 84% feature breadth | Shipped and supported for three decades |
| Native .pptx | Open, save and present, with round-trip losses on real-world decks | The format's owner; the reference implementation |
| Agent automation | MCP server, CLI, JSON control channel, 226 commands | Scripting via Office Scripts and VBA; no MCP |
| Platforms | macOS, Windows, Linux, FreeBSD, browser | Windows, macOS, web; no native Linux desktop build |
| Charts | 65% breadth, ~45% ready | Native, with a chart type list nobody else matches |
| SmartArt | 50% breadth, ~35% ready — the shallowest area | Native; the feature other suites copy badly |
| Transitions / animations | 100% / 85% breadth; Morph included | Native, including Morph |
| Presenter view | 68% breadth, ~60% ready | Native, with presenter notes and laser pointer |
| Installers | Code-signed; macOS build signed and notarized | Signed, and the download comes with an account |
| Size | A single native binary, or a browser build | A full Microsoft 365 account |
What DeckCraft has actually finished
This is the part worth reading, because most comparisons of a sixteen-day-old project against a thirty-year-old product stop at feature lists. DeckCraft's roadmap defines an alpha gate — six of PowerPoint's core workflows that must work end to end before the project calls itself alpha — and states that all six pass: build a deck, open and save a .pptx, present with transitions, animations, media and presenter view, add tables and charts, share as PDF, and review.
The breadth number is measured rather than self-assigned. cargo xtask parity walks a checklist of 191 PowerPoint features and reports 84% weighted — 92% of P0 features, 82% of P1, 55% of P2. A separate script matches 59% of 217 app-specific PowerPoint menu items by name, and the project labels that a lower bound rather than a score.
The gap between 84% breadth and ~55% readiness is the honest part of the whole exercise. DeckCraft publishes a per-dimension table that says which of its features survive a real file:
| Dimension | Ready | Dimension | Ready |
|---|---|---|---|
| Platforms | ~80% | File formats | ~58% |
| Features (breadth 84%, with depth) | ~62% | Hardware (GPU, video decode, pens) | ~40% |
| UI/UX fidelity | ~60% | Localization | ~8% |
| Stability | ~60% | Ecosystem (templates) | ~25% |
| Performance | ~55% | AI features | ~10% |
Two numbers in that table predict every complaint you will read about DeckCraft: localization is ~8% and AI features are ~10%. The interface is English-first. The interesting thing about the project is not that it has AI features — it is that the automation surface is the one dimension marked ahead, with the CLI, the JSON control channel and the MCP server already counted as complete.
Where DeckCraft wins
It runs where PowerPoint does not. DeckCraft ships native Linux and FreeBSD builds, and a browser build. PowerPoint's desktop client is Windows and macOS; on Linux you are left with the web version and its compromises. For a Rust shop that wants a slide tool on every machine in the fleet, that alone is decisive.
No licence, no account, no telemetry. There is no sign-in, no tenant and no subscription. A deck written in DeckCraft is a file on a disk. For a company that cannot put a file inside a cloud tenant, that changes what is possible — and it is the same argument that made SolidCraft interesting for the same reason.
Every button is also a command. The CLI, the JSON control channel and the MCP server expose the same 226 commands the UI does. That is what makes it drivable by an agent, and it is a genuinely different bet from "a cheaper PowerPoint": the point is not the slides, it is that something can build them.
Signed and notarized, with no SmartScreen drama. Installers and executables are code-signed, and the macOS build is signed and notarized. For a sixteen-day-old project, that is a deliberate choice, and it is the opposite of what SolidCraft does.
Where PowerPoint wins
Other people's decks. This is the decisive point and no feature count changes it. DeckCraft's own roadmap states that .pptx "has never been tested on a corpus of real decks", and lists the round-trip losses it still has as blocking items — bugs #70, #74 and #77 — plus the EMF and SVG picture handling, the data-loss bug (#60) and the startup-crash bugs (#40 and #59). Those are bug numbers in a public tracker, which is more than most vendors tell you. It is also an admission that the file format is not yet safe in both directions.
Charts and SmartArt. SmartArt is DeckCraft's shallowest measured area at 50% breadth and ~35% readiness, and charts sit at 65% and ~45%. In PowerPoint these are native and mature. A deck with a live chart that someone else will edit is not a DeckCraft deck yet.
Everything around the deck. Templates, the add-in ecosystem, Designer, co-authoring in Microsoft 365, recording, and a web version that needs no install at all. DeckCraft's own ecosystem line reads ~25%.
What neither replaces
If the deck has to round-trip through your client's Microsoft 365 — with an editable chart, a linked spreadsheet and a VBA macro someone else will run — then neither of these is PowerPoint. The realistic choice there is PowerPoint, or a PDF plus a conversation about who owns the master file.
How to decide in one minute
- Will somebody else open this deck in Microsoft 365 and edit it? → PowerPoint.
- Do you need it on Linux, or on a machine with no Microsoft account? → DeckCraft.
- Is the deck going to contain charts or SmartArt that will be edited downstream? → PowerPoint, for now.
- Do you want an agent to assemble the deck from data? → DeckCraft, and nothing else on this list is close.
- Is a per-seat licence the problem? → DeckCraft.
Frequently asked
Is DeckCraft a free alternative to Microsoft PowerPoint?
Yes, and it is usable today for building decks. It measures 84% feature breadth across 191 PowerPoint features, self-rates ~55% ready for real work, passes an alpha gate covering all six of PowerPoint's core workflows, and is free under MIT or Apache-2.0 with no account required.
Can DeckCraft replace Microsoft PowerPoint?
Not for shared corporate decks. Chart and SmartArt fidelity, EMF and SVG picture handling, round-trip losses on real .pptx files, and a data-loss and startup-crash bug are all listed as blocking before beta. Beta needs roughly 75% ready and no blocking gap in the format; the project estimates 120 to 210 agent hours away.
Is DeckCraft safe to install?
Yes. Code-signed installers and executables, a signed and notarized macOS build, MIT or Apache-2.0 licensing, and no account or telemetry. One practical note: on Windows the desktop app initialises DirectX 12 by default, so a very old GPU may need the documented gl override.
Sources: DeckCraft repository (ROADMAP.md, docs/roadmap.md, docs/parity-checklist.md, docs/gaps.md, docs/target-app-parity.md, README.md), read 23 October 2026; Microsoft PowerPoint product documentation. We read the repositories; we did not run the binaries.