Quick answer: To prepare a website ZIP for HubSpot theme conversion, include the website’s actual HTML pages and every local file those pages depend on, including CSS, JavaScript, images, fonts and icons. Keep folders organized, remove unrelated files from the working copy, and never include private credentials.

Why ZIP preparation matters

Many conversion problems begin before the conversion process: a stylesheet is missing, an image points to a folder outside the ZIP, or the archive contains several old versions of the same page. A clean source package makes page selection easier and gives the conversion workflow a better chance of resolving local references correctly.

Recommended ZIP structure

There is no single folder layout that every website must use. The important point is consistency: HTML pages should reference assets that are included in the archive, and the original relative paths should remain understandable.

website-source/
  index.html
  about.html
  services.html
  contact.html
  assets/
    css/
    js/
    images/
    fonts/

This is an example structure, not a required naming convention. Your existing site may use different folder names. Preserve the paths that the HTML actually references.

Pre-upload checklist

• HTML: identify the real pages and confirm that each file opens in a browser.
• CSS: include the stylesheets and any imported CSS files.
• JavaScript: include scripts used for menus, sliders and interface behavior.
• Images: include logos, backgrounds, icons and page imagery in their referenced folders.
• Fonts: include licensed font files and verify their CSS paths.
• Links: check that local navigation points to pages included in the package.
• Archive: open the ZIP once before upload to ensure it is not corrupted or nested inside an unnecessary extra folder.

What should you leave out?

Do not put passwords, API keys, access tokens, database exports, customer data or private business documents into a theme ZIP. Also consider excluding old backups, duplicate exports, operating-system metadata and unrelated documentation from the working copy. Keep a separate untouched backup outside the upload package.

Check external dependencies

A source ZIP may rely on externally hosted libraries, video embeds, web fonts, analytics scripts or form providers. Write down those dependencies. A browser preview may display a page even when some services are unavailable or blocked in the preview environment. Test them again after the theme is uploaded into HubSpot.

Use a source preview before conversion

Open the homepage and at least one inner page in a browser. Look for missing images, broken styles and console errors. If the original files already have problems, fix or document them before conversion so that you do not confuse source issues with conversion issues.

Frequently asked questions

Should I ZIP the whole project folder?

Usually, yes, when the folder contains the site pages and their assets. Avoid placing unrelated backups or confidential files in that folder. Preserve the relative directory structure.

Can I upload a ZIP that contains another ZIP?

A nested archive makes the source harder to inspect and may prevent the converter from finding the HTML pages. Extract the actual website files and create a clean ZIP from the source folder.

Do I need to rename every file?

No. Do not rename assets unless you also update every reference to them. Keeping existing paths intact is often safer.

Ready to prepare your files? Once your source ZIP passes this checklist, open the DigiThinker HTML to HubSpot tool, select the pages you want and review its warnings before downloading the theme package.