There is a new open source PowerPoint alternative in Rust gathering serious momentum on GitHub, and it deserves your attention for more than novelty value. DeckCraft, from the ArtCraft team, is a clean-room reimplementation of Microsoft PowerPoint written in pure Rust — no Microsoft code, no compatibility shims, just a from-scratch presentation engine. At the time of writing it holds nearly 3,900 stars and more than 2,200 forks, and it can already open and save real .pptx files, run full-screen slide shows with transitions and animations, and be driven entirely by AI agents through an MCP server. If your business pays for presentation software — or your teams generate decks inside automated pipelines — here is what matters, what still does not work, and whether it deserves a slot in your 2026 tooling evaluation.
What DeckCraft actually is
DeckCraft is one of the Crafting Apps, a family of free, open-source creative tools from the ArtCraft team, each written from scratch in Rust: PhotoCraft (image editing), VectorCraft (vector illustration), FilmCraft (video editing), LightCraft (photo library and raw development), PdfCraft (PDF reading and organising), EffectCraft (motion graphics), DesignCraft (page layout) and DeckCraft itself for presentations, alongside ArtCraft, the team’s AI image and video studio. The “clean-room” part matters commercially: because it was reimplemented from a blank slate rather than derived from any proprietary codebase, the licensing is unambiguous — dual-licensed MIT/Apache-2.0 — which means a company can adopt it, fork it, or embed it without the legal fog that surrounds some reverse-engineered tools.
The project is admirably honest about where it stands. DeckCraft is in alpha, heading for beta, and it publishes a measured parity assessment against its explicit target, Microsoft PowerPoint for Mac 16.113 (Microsoft 365): 84% feature breadth measured across 191 tracked PowerPoint features, and roughly 55% “ready for real work” once you discount for interaction polish, stability and .pptx exchange fidelity. Few open-source projects quantify their own incompleteness this precisely, and that transparency is itself a trust signal for any team doing build-vs-buy due diligence.
Why an open source PowerPoint alternative in Rust is trending now
Presentation software is one of the quietest line items in enterprise IT budgets — and one of the most irritating. Multiply a per-seat licence across a few hundred employees, add the fact that most of those employees use perhaps a tenth of the feature set, and the economics start to look indefensible. DeckCraft attacks that from two directions at once. First, the price: free, forever, with no telemetry phoning home and no cloud account required to open a file. Second, and more interesting for 2026, the architecture: every action in DeckCraft is a command with a stable identifier, so humans, scripts and AI agents all use the same verbs. More than 200 commands are scriptable from the CLI, a JSON control channel, or an MCP server that AI agents can drive directly.
That agent-first design is the real reason this repository is trending, not just the “PowerPoint in Rust” headline. We are in the middle of a wave where teams want agents to produce artefacts, not just chat about them — and a presentation tool that an agent can drive deterministically is genuinely new. Combine that with the offline-first story (your pitch decks never leave your machine, which matters for legal, finance and anyone under data-residency obligations) and the broader momentum of the storytold suite, and the star count starts to make sense. It is not hype; it is three real buyer pains — cost, privacy and automation — converging on one project.
What DeckCraft can actually do today
The README documents a working feature set that already covers the core presentation workflow end to end. For building decks: slide masters and eleven layouts with placeholders that inherit position and formatting, eight original themes with colour and font schemes, sections, speaker notes, comments, headers and footers, and custom slide sizes. For drawing: more than 150 preset shapes with adjust handles, connectors that stay glued to shapes, freeform and curve tools, boolean shape merging (union, combine, fragment, intersect, subtract), gradient, picture and pattern fills, dashed outlines with arrowheads, shadows, glow, soft edges and reflections.
Text gets in-place editing with full font and paragraph formatting, bullets and numbering, multi-column layouts, autofit, vertical text, fields and hyperlinks. Content support includes pictures with crop and corrections, styled tables, charts, basic SmartArt, and audio/video playback across a serious codec list (MP3, AAC, FLAC, ALAC, Ogg, Opus, WAV, AIFF for audio; H.264, HEVC, VP9 and AV1 for video). For presenting: transitions including Morph, entrance/emphasis/exit and motion-path animations, per-paragraph builds, full-screen slide show, presenter view, pen tools, rehearsal timings and media playback.
On file exchange — the make-or-break for any Office alternative — DeckCraft opens and saves .pptx presentations, exports PDF (slides, notes pages and handouts with selectable text), PNG and JPEG, and can even render an animated GIF of a deck. Unsaved work is protected by AutoRecover. Platform coverage is unusually broad for a project this young: native builds for macOS, Windows, Linux and FreeBSD, plus a web version, with Windows installers and portables for x64, arm64 and even 32-bit x86, a signed and notarised macOS universal build, and Linux packaged as AppImage, Flatpak, .deb, .rpm and tarball for both x86_64 and ARM64.
How it works: every button is a command
This is the part that separates DeckCraft from every other “free PowerPoint clone” and the part most relevant if you run AI automation or document pipelines. The command-line tool exposes the whole application:
deckcraft-cli commands format.— lists every available commanddeckcraft-cli run --sample --cmd 'slide.new={"layout":"titleOnly","title":"Hello"}' --save hello.deckcraft— builds a deck headlesslydeckcraft-cli mcp— starts an MCP server over stdio for AI agentsdeckcraft-cli mcp --connect 7990— drives a running DeckCraft instancedeckcraft-cli mcp --automation-read-root DIR --automation-write-root DIR— confines a headless agent to specific folders
Think about what that unlocks in practice: a CI job that renders last month’s metrics into a board-ready deck every Monday morning, a sales agent that assembles a personalised pitch from your CRM data, or a reporting pipeline where the “export to PowerPoint” step stops being a brittle macro and becomes a versioned, testable command sequence. The confinement flags show the team has thought about the security model too — an agent that can only read and write inside designated directories is far easier to approve in a corporate environment. If you are already investing in workflow automation, this is the kind of building block that turns “AI can draft text” into “AI can ship finished artefacts”.
From our experience: the honest limitations
We evaluate open-source tools for client work regularly, and the rule is simple: adopt for what it does today, not the roadmap. DeckCraft’s own numbers tell you exactly where the edges are. That 84% breadth figure drops to about 55% “ready for real work” — and the weak dimensions are the ones that bite in production: file-format fidelity (PPTX exchange has never been tested against a corpus of real-world decks, and the team tracks known round-trip losses openly), localisation (around 8%), AI features (around 10%) and ecosystem (templates and add-ins are explicitly out of scope, at roughly 25%). There are 427 open issues at the time of writing, which is healthy activity for an alpha but not a number you ignore.
The practical gotchas we would flag in a client review: building from source on Linux requires ALSA headers for slide-show sound (libasound2-dev on Debian/Ubuntu) and the build simply stops without them; the Windows app initialises only DirectX 12 by default, which can crash some graphics drivers before the window appears (there is a documented WGPU_BACKEND workaround, but it is the kind of thing that generates support tickets); and fonts come from a sibling craft-fonts repository that you clone alongside, otherwise it falls back to system fonts. None of these are deal-breakers — they are alpha-stage rough edges, documented in the open, which is precisely how you want them.
When not to use it: for mission-critical client-facing decks where pixel-perfect round-tripping with Microsoft Office matters; anywhere you depend on real-time co-authoring with Office users; and anywhere your workflow leans on the PowerPoint add-in or template ecosystem. For those, the licence fee is still the cheaper option — an honest build-vs-buy analysis says so. Where it shines today: offline-first and air-gapped environments, automated deck generation in pipelines, privacy-sensitive organisations that do not want pitch decks transiting a cloud service, and engineering teams that want a hackable, scriptable presentation layer. We keep a running eye on tools like this in our AI tools directory, because the automation story is where the long-term value sits.
Getting started in five steps
- Grab a release build, not the source. Unless you want to hack on it, download the latest release from the DeckCraft GitHub repository: Windows MSI or portable, macOS universal DMG, or Linux AppImage/.deb/.rpm/Flatpak. Installers are code-signed.
- On Linux, install the audio headers first.
sudo apt install libasound2-devon Debian/Ubuntu (or the alsa-lib equivalents on Fedora/Arch) before building from source — otherwise the build halts at the audio dependency. - Verify the toolchain with the sample deck. From a source checkout:
git clone https://github.com/storytold/deckcraft, thencargo run --release -p deckcraft-cli -- render --sample --all --scale 1 out/renders every slide of the built-in sample deck to a folder. If that works, your build is healthy. - Explore the command surface. Run
deckcraft-cli commands format.and try a headless edit — for example, creating a slide and saving it — before you touch the GUI. This is the interface your automation will actually use. - Try the MCP server with your agent.
deckcraft-cli mcp --automation-read-root ./in --automation-write-root ./outgives an AI agent a sandboxed presentation workspace. Start with read-only experiments before letting anything write.
Frequently asked questions
Is DeckCraft really free for commercial use?
Yes. It is dual-licensed MIT/Apache-2.0, and because it is a clean-room reimplementation written from scratch in Rust, there is no proprietary code in the lineage and no licence fee, seat limit or feature gate. You can use it internally, ship it to clients, or fork it — the standard open-source obligations (preserve the licence notice) are the only strings attached.
Can DeckCraft open my existing PowerPoint files?
It opens and saves .pptx files, and exports PDF, PNG, JPEG and animated GIF. The honest caveat — stated by the project itself — is that .pptx exchange has not yet been tested against a corpus of real-world decks, and known round-trip losses are tracked in the open. For casual and moderately complex decks it works; for intricate corporate templates with embedded objects and exotic formatting, verify fidelity before you commit.
How does DeckCraft compare to LibreOffice Impress?
Impress is the mature incumbent: battle-tested, broad format support, and fine for everyday use, but ageing architecture and no agent story. DeckCraft is the challenger: a modern Rust codebase, native performance, a measured parity checklist against current PowerPoint, and a CLI-plus-MCP design that lets scripts and AI agents drive it. Today Impress is the safer default for general office use; DeckCraft is the more interesting bet for automation-heavy and offline-first teams — and the one improving faster.
Can AI agents really build presentations with it?
Yes, and this is DeckCraft’s standout feature. Every action is one of 200+ commands with a stable identifier, exposed through the CLI, a JSON control channel and an MCP server over stdio. An agent can create slides, apply layouts and themes, insert charts and media, and save .pptx output — all deterministically, all confinable to designated directories. It turns “generate a deck” from a brittle screen-automation hack into a proper API call.
Is it stable enough to replace PowerPoint today?
For most teams, not yet — the project rates itself around 55% ready for real work, and the gaps (PPTX round-trip fidelity, localisation, template ecosystem) are exactly the ones that matter in a mixed Office environment. But “replace PowerPoint for everyone” is the wrong bar. As a secondary tool for automated reporting, offline-first workstations, or privacy-sensitive decks, it is already worth piloting. Revisit the decision at beta; the project estimates it is only a few hundred agent-hours away.
DeckCraft is the latest evidence that the most interesting open-source work in 2026 is happening at the intersection of classic desktop software and agentic automation. A clean-room, Rust-native presentation engine with honest metrics, real .pptx support and a genuine API for AI agents is worth more than a dozen AI slide-generator demos — because it is infrastructure, not a demo. If you are weighing build-vs-buy on internal tooling, or you want AI agents wired into your document workflows instead of just your chat window, talk to us — this is the kind of evaluation we do every week.