All help articles
Browse help topics
Document Library

HTML and ZIP upload requirements

Prepare a single HTML file or static website ZIP that HummingDeck can process, preview, and share reliably.

Updated August 17, 2026

Examples use sample data. Available controls may vary by plan, role, and product version.

HummingDeck can share a single HTML document or a multi-file static website packaged as a ZIP. The file must be self-contained enough to run from a normal static web server.

Choose single HTML or ZIP

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.

Plan: Starter and above

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.

Product exampleBased on the production HTML upload guidance

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.html at 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.
  • 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. Very large individual assets, 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

  1. Extract the ZIP into a clean folder.
  2. Serve that folder through a basic static web server.
  3. Open index.html from the server URL.
  4. Check every page, image, font, video, and link.
  5. Resize the browser to confirm the layout remains usable on phones.
  6. 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.