Upload or open a sample deck
Start from a local single-file HTML presentation or use the built-in sample to understand the workflow immediately.
Edit AI-generated HTML presentations visually without breaking the original design.
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
HTML slides from AI tools can look strong on the first pass, but small visual edits become expensive when every change requires another prompt or a risky PPTX conversion.
Prompting the AI again can rewrite sections that were already good.
PPTX conversion often flattens layout, fonts, spacing, or images.
Code editors are precise, but too slow for last-mile visual polish.
Workflow
A clear sequence replaces the thin demo feel: open the HTML file, make precise slide edits, then export a portable deck.
Start from a local single-file HTML presentation or use the built-in sample to understand the workflow immediately.
Click text, adjust styles, insert images, manage pages, and fix overflow from one desktop-grade workspace.
Download a portable edited deck as a single HTML file with embedded image edits.
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
Use the editor when the AI draft is structurally right but still needs human visual judgment before delivery.
Editing path
route-specific proof, not keyword swapping
Fix the slide title that wraps one word too early.
Nudge the screenshot into alignment without touching source code.
Export the revised deck as one clean HTML file.
Comparison
The product has a narrow job: keep the AI draft intact while a human fixes what needs visual judgment.
AI is useful for the first draft, but it is unreliable for tiny slide-level visual edits.
Converters can make files editable, but typography and spacing frequently drift.
Code keeps full control, but visual edits take too long when you only need the final 20%.
Edit the HTML presentation directly while preserving the design language that the AI already produced.
Use cases
The interface is built for the post-generation workflow: a usable draft exists, and now it needs controlled visual polish.
AI power users polishing Claude, ChatGPT, Cursor, Codex, or Gemini decks.
Trainers and course creators finishing workshop slides.
Consultants and product managers preparing client-facing decks quickly.
Knowledge creators turning structured content into slide-style HTML.
Developers who like HTML slides but need non-code editing for final polish.
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.