Claude and ChatGPT can produce a presentation, proposal, microsite, or interactive document as HTML. HummingDeck does not convert a conversation or preview URL directly. You need the final static output as one HTML file, a ZIP bundle, or an API upload.
Decide the output before prompting
Ask for a single HTML file when the project is small enough to embed all CSS, JavaScript, images, and fonts. Ask for a static website ZIP when the output has several assets or pages.
Create a deployment-ready, responsive HTML document that can run from one file on a static web server. Embed all CSS and JavaScript in the HTML. Embed essential images or replace them with lightweight inline SVG. Do not require npm, a build step, a local server, environment variables, authentication, or private API keys. Keep navigation and interactions usable on touch screens. Return the final .html file and nothing else.
Export this project as a deployment-ready static website ZIP for HummingDeck. Include one root-level index.html and all compiled dependencies. Use relative asset paths. Include every required image, font, stylesheet, script, and media file. Do not include source-only files that require npm or another build step. Preserve every page and link. Verify the extracted folder runs from a basic static web server. Keep the ZIP below 100 MB. Return only the ZIP.
Prepare an upload-ready HTML ZIP
Check the package before uploading so HummingDeck can process and preview it reliably.
Review the package requirements
- Place index.html at the ZIP root.
- Use browser-ready HTML, CSS, and JavaScript.
- Include local fonts, images, and other dependencies.
- Remove build steps and server-only code.
- Open index.html locally and verify every page and interaction.
Prompt for Claude or ChatGPT
Create a self-contained HTML presentation for upload to HummingDeck. Put index.html at the ZIP root, use relative paths for every local asset, include all required files, and remove build steps and server-only dependencies.
Add a HummingDeck handoff checklist
For a more reliable result, add these requirements to the original design prompt:
- The layout must work from 320 px phone widths through desktop screens.
- Buttons and links must have clear labels and usable touch targets.
- Navigation must not rely only on hover.
- Text must remain readable without browser zoom.
- Essential content must not depend on a remote service staying online.
- Page changes should update the visible state predictably.
- No secret, token, or private endpoint may appear in browser code.
Repair an invalid export
If the upload fails or the preview is blank, give the extracted file tree and browser-console errors back to the AI tool. Do not include credentials or private customer information.
Audit this static HTML export for HummingDeck. The package must have one clear root entry, use relative paths, include every required asset, and run without npm, a build step, environment variables, or a backend. Identify missing files and broken references. Return a corrected static ZIP below 100 MB. Do not add external dependencies unless they are essential and publicly accessible.
Upload through the product or API
Use the Document Library for a manual upload. API uploads are useful when an internal workflow generates many documents and should publish them automatically. Direct API access is a private pilot and must be enabled for the workspace first.
Review HTML and ZIP upload requirements before sending the final link to a recipient.