Choose an HTML file
The editor reads the file in the browser and detects slide-like sections.
Open a single-file HTML deck, edit slides in your browser, and export the finished presentation without installing a desktop app.
Slide Sandbox
Localbrowser-only HTML deck polish
Active slide: Opening
selected block: h1 · safe to edit
Final polish after AI generation
Adjust copy, fix overflow, place images, and export a clean single-file deck without another prompt loop.
Core loop
Upload -> Edit -> Export
Workspace
Rail + canvas + inspector
Safety
Scripts removed on import/export
Problem
A browser can display the deck, but display mode does not help you make the last-mile edits that a presentation needs.
Single HTML files are easy to share, but hard for non-code editing.
Generated slide sections need page management and visual controls.
A practical editor should keep the file local and export a portable result.
Workflow
A clear sequence replaces the thin demo feel: open the HTML file, make precise slide edits, then export a portable deck.
The editor reads the file in the browser and detects slide-like sections.
Use thumbnails, canvas editing, formatting controls, and image tools.
Export the edited deck as a clean single-file HTML presentation.
Capabilities
The tool stays narrow: final visual polish for a generated HTML deck, not another AI presentation generator.
Select titles, bullets, captions, or labels and adjust copy, font size, emphasis, and color without touching code.
Drop in a local image, keep it embedded in the deck, resize it, and nudge it into place.
Add, duplicate, delete, and reorder slides directly from the thumbnail rail.
Reduce oversized text on the current slide when an AI-generated layout starts to overflow.
Select a slide block and copy or download it as a PNG for reuse in documents, posts, or messages.
Export a single-file HTML deck that preserves the edited layout and embedded images.
Example
The editor treats slide-like sections as pages, so a single HTML file becomes a usable deck workspace instead of a static preview.
Editing path
route-specific proof, not keyword swapping
Detect section, article, data-slide, and .slide containers.
Use thumbnails to move through the deck.
Download the edited HTML without installing a desktop app.
Comparison
The product has a narrow job: keep the AI draft intact while a human fixes what needs visual judgment.
Optimized for pages or code, not slide thumbnails and presentation polish.
Great for native decks, but importing HTML can break the design.
Keeps the HTML deck as the editing surface.
Use cases
The interface is built for the post-generation workflow: a usable draft exists, and now it needs controlled visual polish.
Open single HTML presentation files.
Edit section-based slides from AI output.
Insert local images and keep them embedded.
Export a clean deck for sharing.
FAQ
Clear boundaries matter: this is a local browser editor for HTML decks, not a cloud storage or PPTX conversion system.
Yes. Open a sample deck or upload a local HTML file, click into the slide canvas, and edit text in place.
Yes. The editor includes text size, color, bold, and italic controls for quick final polish.
Yes. Inserted images can be resized from the canvas and nudged from the formatting panel.
Yes. Claude decks that use section, article, data-slide, or slide-like containers are split into editable pages.
Yes. The first version focuses on single-file HTML decks from AI tools such as ChatGPT, Codex, Cursor, Gemini, and Claude.
The editor preserves the HTML structure and inline edits. Complex third-party scripts are removed for a safer single-file export.
Not in the first version. The product is intentionally positioned as a safer direct HTML editing workflow before any PPTX conversion step.
No. In this version, files are opened and edited in the browser. The landing page states this as a local-first workflow.
Open the workspace
The fastest validation path is one precise edit and one clean HTML export.