Slide and layout work
Build a presentation-shaped document with slide layouts, text and visual hierarchy as a browser canary.
In development · MIT or Apache-2.0 · v0.7.0
DeckCraft is the presentation-focused project in the Craft Apps Office line. It is useful for people searching for a free PowerPoint alternative with a visible open-source trail, but it remains in development and should be evaluated against a real sample deck before a talk or client delivery. This page separates the browser experience from a desktop release, explains the tests that expose slide compatibility problems, and keeps PowerPoint parity claims out of the description.
Try the browser editor Try DeckCraft in your browser Read the source
| Platform | Architectures | Build formats | Where work runs |
|---|---|---|---|
| Browser (WebAssembly) | modern browser | deckcraft-web-0.7.0.zip | Browser build; confirm the current hosting and file boundary upstream |
Build a presentation-shaped document with slide layouts, text and visual hierarchy as a browser canary.
Compare an exported sample with the browser canvas, including fonts, images, spacing and the playback path.
Use a small deck to learn the interaction before bringing a real presentation into an early-stage tool.
The GitHub repository and release notes remain the authority for assets, changes and the current compatibility boundary.
This is an upstream preview of DeckCraft. It helps you recognise the workflow, but it is not a promise that every panel, model or file format is unchanged in v0.7.0. Use the release and source links above for the version-specific truth.
Browser experience
Target workflow: slides, layouts and presentation export. The editor opens in the upstream application; This portal does not upload, proxy or retain your files.
DeckCraft is intended for slide and presentation workflows: arranging content on pages, building a visual sequence, checking text and media placement, and preparing an output that someone can present. It belongs to the same Craft family as WordCraft and GridCraft, but it is not a shared office suite in the sense of one account, one file engine or one compatibility promise. Its source repository, release notes and browser package are separate and should be checked separately.
“PowerPoint alternative” is a useful search description only when it is paired with an honest test boundary. Microsoft PowerPoint and other mature presentation tools carry years of work around themes, layouts, fonts, animations, media codecs, speaker notes, presenter view, accessibility and export. DeckCraft is in development. The reason to test it is that you may prefer an inspectable open-source project for a small deck or an early browser canary; the reason to keep a fallback is that a live presentation has little tolerance for an export or font surprise.
A blank title slide proves almost nothing. Create five or six slides that resemble the work you actually do: a title, a text-heavy slide, a two-column layout, an image with a caption, a chart or table if you use one, and a closing slide. Include the fonts, aspect ratio and media types used in delivery. Export the deck, reopen it in the software that will present it, and inspect the same slides at the same size. If the deck uses video, audio, transitions, speaker notes or embedded links, test each one explicitly rather than adding it to a general claim of compatibility.
| Test area | Sample | What to inspect |
|---|---|---|
| Typography | Title, body and a fallback font | Line breaks, overflow, alignment and substitution |
| Media | Image, caption and one real asset | Crop, resolution, placement and export quality |
| Structure | Several layouts and a table | Slide order, spacing and readability in the receiving app |
| Delivery | Export, reopen and present | Fonts, playback, aspect ratio and links still work |
The browser page is the quickest place to run the canary. The official WebAssembly editor runs in the browser session and OpenCraftTools does not receive or store the presentation. That is a clear boundary, not a guarantee of offline recovery: the browser controls memory, font loading, clipboard access, downloads and any local persistence. Save or export before closing the tab, and keep the original deck in a local folder. A browser editor is also not automatically the same as a desktop presentation environment.
If you need a Windows download, follow the upstream release link and record the exact asset and release tag. Compare the desktop behavior with the browser result on the same sample deck. Look for differences in fonts, media access, export size, playback and any feature that depends on an operating-system integration. A successful browser test can justify a closer look; it should not be used as evidence that a desktop build or a live presentation will behave identically.
Presentation tools fail most visibly at the handoff boundary. A font that is missing or substituted changes line breaks, and a small change in a title can push every later element down. An image can look fine in an editor and become soft or cropped after export. A media file can be accepted but fail on the machine used for the talk. For that reason, compare the exported file on the delivery machine, not only on the computer that created it. Keep a PDF or image fallback for important presentations and preserve the editable source separately.
OpenCraftTools links DeckCraft’s upstream repository and release page; it does not host or repackage installer files. Confirm the repository, tag, asset and any checksum information before opening a download. The current browser fact card records the checked WebAssembly release, while the changelog preserves the earlier v0.5.0 story-line entry. Upstream release notes remain authoritative when the project changes. Put the release tag, browser or desktop environment and test deck name in the notes so another person can reproduce the result.
Include the fonts, images, aspect ratio and media behavior that matter, but never make the only production deck the first test.
Build or import the sample, then check layout, font loading, export and local save behavior on the target browser.
Reopen the export in the presentation software and on the machine used for the talk.
Save a PDF or image sequence and retain the editable source until the new workflow has passed a real presentation canary.
DeckCraft is worth trying for a small internal deck, an open-source office experiment, or a browser-first workflow where you can control the file and the receiving environment. It is not yet a reason to remove a mature presentation application from a deadline-driven or media-heavy process. Start with a short deck, learn what survives, and let the evidence decide. The key question is not whether the editor resembles PowerPoint; it is whether your exact slides, fonts, media and delivery steps remain reliable from source to presentation.
DeckCraft is an open-source presentation project presented as a testable free alternative. It is in development and does not claim PowerPoint compatibility parity, so test a real deck first.
Verify the current release with a sample containing your real fonts, images, layouts and media. Reopen the exported result in the software and on the machine used for delivery.
Do not assume that. Fonts, transitions, media and presenter features are separate acceptance tests, and a mature fallback should remain available for a live talk.
No. The browser editor runs in the visitor session and OpenCraftTools provides no account, upload or server-side recovery service. Save or export before closing.
Use the official upstream repository or release link shown on this page. Check the exact tag, asset and any published checksum before opening a package.