HummingDeck can display a single HTML document or a static website packaged as a ZIP in the browser. It can also share a ZIP as a download-only archive for recipients to open on their own device.
Choose how to share the ZIP
Choose Preview in browser for a ZIP containing an HTML presentation or static website. This option requires an eligible paid plan and follows the package requirements below.
Choose Download only for an archive that recipients should save and open locally, including a password-protected or encrypted ZIP. This option is available on every plan within the normal document and file-size limits. It does not require index.html, and HummingDeck does not extract or preview the archive.
If the contents must be encrypted before reaching cloud storage, encrypt the ZIP on your device before uploading and give the password to recipients separately. Choosing Download only does not encrypt an unprotected archive. See Upload and manage documents.
Choose single HTML or ZIP
The rest of this article applies to browser previews.
Use a single .html file when all styles, scripts, images, and fonts are embedded in that file. Use a ZIP when the experience depends on separate CSS, JavaScript, images, fonts, video, or other assets.
For a single-file example, watch how to share an HTML file as a link. It shows the upload, a Personal Link, the recipient's browser view, and, on Starter and above, recorded visits and viewing time.
A single HTML file can include its own Print or Save as PDF button. It opens the recipient's browser print dialog, where they can print or save a PDF using the document's print layout. The button works regardless of the Share Link's Allow downloads setting, which controls HummingDeck's original-file download action. Browser printing does not create a download entry in Activity.
A single HTML file can also save a recipient's progress, such as assessment answers or calculator inputs, with the browser's localStorage or sessionStorage. Each Share Link keeps its own saved data in the recipient's browser, and the data is not sent to HummingDeck or to you. Data in localStorage stays for 30 days after its last change. Data in sessionStorage is cleared when the tab closes. Each document can save up to about 1 MB.
The browser upload limit is 100 MB. API document uploads have a separate 30 MB limit.
ZIP structure
The safest package has one root-level index.html file and relative asset paths.
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.
Good references look like assets/logo.svg, ./styles.css, or images/hero.webp. Avoid paths tied to your computer, such as a local desktop folder. Do not assume a build tool or package manager will run after upload. Upload compiled output, not source code that still needs a build step.
Package requirements
- Include a clear entry page, normally
index.htmlat the ZIP root. - Include every required local asset in the ZIP.
- Use relative links between HTML, CSS, JavaScript, images, fonts, and media.
- Keep the complete archive below 100 MB.
- Keep the root
index.htmlentry at or below 12 MB. - Keep each other text asset at or below 5 MB and each binary asset at or below 25 MB.
- Export a static result that works without a server-side application.
- Keep filenames and paths straightforward. Avoid duplicate paths or ambiguous entry files.
- Test the extracted folder from a local static web server before uploading.
HummingDeck accepts common web assets, including HTML, CSS, JavaScript, JSON, SVG, web images, web fonts, audio, and video. Unsupported archive entries may be skipped. Excessive file counts, unsafe paths, or unusually compressed archives can be rejected.
External services and scripts
Remote resources can fail because of network rules, provider restrictions, content security policy, authentication, or a changed URL. Bundle important visual assets whenever licensing permits. Do not depend on a private API, logged-in browser session, or a local development server.
Some third-party video and interactive embeds work only when their provider allows framing. Test the recipient link, not only the owner preview.
Test before sending
- Extract the ZIP into a clean folder.
- Serve that folder through a basic static web server.
- Open
index.htmlfrom the server URL. - Check every page, image, font, video, and link.
- Resize the browser to confirm the layout remains usable on phones.
- Upload to HummingDeck and test the final share link in a private browser window.
For AI-generated exports, use the prompts in Create HTML with Claude or ChatGPT.