OpenSlideX

OpenSlideX is an open-source, local-first workspace for creating presentations that remain editable after the first draft. It keeps each deck in a folder on the user's computer, with a React-based presentation.tsx file as the canonical source. The project is aimed at people who want agents to help create a deck without handing ownership of the deck to a hosted presentation service. Copy, layouts, assets, and exports can stay beside one another in a normal local project, where they can be opened in an editor, inspected from a terminal, or tracked with Git.

The Workspace provides the visual side of that model. A user can start a blank deck or choose an official template, edit slide content and styling, preview changes locally, and keep working on the same source. An existing OpenSlideX project can also be imported from its folder and reopened for more editing. Template content isn't locked. Copy can be rewritten, images swapped, and each slide restyled in the Workspace. React components represent presentation elements such as slides, text, images, video, shapes, charts, tables, SVG, and embedded HTML. Underneath, OpenSlideX compiles the React source into its portable MotionDoc model. MDX remains available for import and export, but the current documentation is clear that presentation.tsx is the source of truth for a deck.

This setup addresses a familiar problem with AI-made slides. A generated deck can look useful at first, then become awkward to revise because the source is hidden inside a service or flattened into images. OpenSlideX puts the editable structure in the project from the start. Its Workbench supports local preview and validation, and the effect system includes entry, action, and exit effects along with native slide interactions. Because the deck is code-backed, a team can review changes as files and use the same development habits it already uses for other versioned work.

Agent assistance is part of the intended workflow, though it isn't presented as a bundled hosted model. The starter includes project-local skills for source intake and PPTX conversion, React authoring, browser-native HTML authoring, narrative design, motion direction, and visual quality checks. An agent can use those resources to move a brief toward a working draft, while the user refines individual slides in Workspace. This makes OpenSlideX especially relevant to developers, technical teams, and agent users who are comfortable giving structured instructions and reviewing editable output rather than accepting a one-click generated result.

Delivery remains flexible. The homepage advertises export to HTML, MDX, and editable PPTX, so a deck can travel as a web presentation, portable source, or a familiar office file. Local validation and rendering happen before export, and the project keeps assets and generated files alongside the deck. That range is useful when one audience needs a browser link while another expects PowerPoint. Some effects or code-driven behaviors may not map perfectly to every destination, so the editable source remains the most complete version and exported formats are best checked before a high-stakes presentation.

There are two installation paths. The standalone macOS and Windows installers include the required runtime and Chromium renderer, so they don't install system-wide Node.js, npm, or Git and don't require administrator access. Release archives are checked with SHA-256 integrity and GitHub artifact attestations, and normal releases require the GitHub CLI for verification. The command can update to a verified new release or roll back to the retained earlier version, and uninstalling the runtime leaves presentation folders in place. Developers can instead clone the repository or initialize a standalone deck through npm, which currently requires Node.js 22.12 or newer. That flexibility is helpful, though both routes assume more comfort with a terminal than a typical cloud slide editor.

OpenSlideX is free and MIT licensed, with no account requirement, background synchronization, or hidden cloud presentation store in its normal workflow. The site says sponsorship is being prepared, but it doesn't describe a paid product tier. The tradeoff is the shape of a young open-source project. Its official bundled catalog currently names only two templates, and the user is responsible for the local runtime, files, and any external agent setup. For someone who values source ownership, local work, and editable exports, those responsibilities are closely connected to the reasons to choose it.