Turn a ZIP file or folder into a live website

Choose the simplest input

Single HTML file, ZIP, or folder?

All three can become a website. Use the format that matches what you already have.

Only have one page? Read the focused guide to hosting an HTML file online.

The part that matters

Use a clean website ZIP structure

The homepage and its assets must be inside the archive. Relative paths keep those assets working after the site moves from your computer to the web.

my-website.zip
├── index.html
├── css/
│   └── styles.css
├── js/
│   └── app.js
└── images/
    └── logo.webp

my-project.zip
├── package.json
├── node_modules/
├── src/
└── .env

No Git workflow

Turn the ZIP into a live website in 3 steps

A simple static site can be online in a few minutes.

1. 1

   Prepare the finished website

   Use a folder that contains index.html, CSS, JavaScript, images, and fonts. If the project uses Vite, React, Vue, or another build tool, run its build command and use the finished dist or build folder instead of src.

2. 2

   Check the ZIP or folder

   Make sure index.html is easy to find, asset paths are relative, and private files such as .env are not included. GeminiLaunch also provides a free ZIP checker that runs in your browser.

3. 3

   Upload and publish

   Upload the ZIP or choose the folder in GeminiLaunch, give the site a name, and publish. The result is a public HTTPS website that opens in a browser, not a ZIP download page.

Free readiness check

Catch a blank website before you publish

GeminiLaunch can inspect a ZIP in your browser without uploading it. The tool looks for the mistakes that cause most blank or broken static websites.

Prepare this project as a static website ZIP.

The ZIP must contain:
- index.html as the homepage
- all CSS, JavaScript, images, and fonts
- relative asset paths
- the finished dist/build output, not src or node_modules

Remove .env files, secrets, server code, and unused source files.
The site should work when index.html is opened in a browser.

Static website boundary

What works from a ZIP—and what does not

A ZIP upload is ideal when the browser can run the finished website by itself. Server features need a different kind of host.

Fast troubleshooting

Fix the most common ZIP upload problems

Start with the file structure before changing the design or rebuilding the whole site.

Still seeing a white page? Follow the deeper blank ZIP website troubleshooting guide or the focused guide to uploading dist instead of src.

Start free, upgrade when the site has a job

Choose the plan around what happens next

The first publish can be free. Pay when you need to keep editing, use your own domain, protect a client preview, or measure traffic.

Questions

ZIP website hosting FAQ

Short answers to the questions people ask before uploading a website ZIP.

How do I turn a ZIP file into a website?

Put a browser-ready static website inside the ZIP, with index.html as the homepage. Upload the ZIP to a static website host such as GeminiLaunch. The host extracts the files and gives you a public HTTPS address that opens the website in a browser.

Can I turn a ZIP file into a website for free?

Yes. GeminiLaunch Free publishes up to 3 live sites on free GeminiLaunch subdomains and accepts website ZIP or folder uploads up to 5 MB per site. A free site stays as first published; editing and republishing start on Lite.

What should be inside a website ZIP?

Include index.html, plus every CSS, JavaScript, image, font, and other file used by the site. Keep links relative, preserve the folder structure, and leave out node_modules, .git, .env, source maps, and other files the public website does not need.

Can I upload a folder instead of making a ZIP?

Yes. GeminiLaunch accepts either a website folder or a ZIP. A folder is easier while you are still making changes. A ZIP is convenient when an AI tool or website builder already exported one file for you.

What is the difference between a single HTML file and a website ZIP?

Upload one HTML file when the page contains everything it needs or uses web-hosted assets. Use a ZIP when the website has separate CSS, JavaScript, images, fonts, or several HTML pages. The ZIP keeps those files and their paths together.

Why is my website blank after I upload the ZIP?

The usual causes are a missing index.html, an extra wrapper folder, uploading source files instead of the finished build, filename capitalization that does not match, or missing CSS, JavaScript, and image files. The free GeminiLaunch ZIP checker tests these problems in your browser.

Can I host a React, Vite, or Vue project from a ZIP?

Yes, if it has been built as a static website. Run the project build command, then ZIP and upload the finished dist or build output. Do not upload src, node_modules, or a project that still needs a server to run.

Will PHP, Node.js, a database, or API routes run from the ZIP?

No. ZIP website hosting serves static browser files. Client-side JavaScript works, but PHP, Node.js servers, databases, server-side rendering, authentication services, and private API code need a host that supports their runtime.

Is ZIP website hosting the same as sharing a ZIP file?

No. File sharing gives visitors the archive to download. ZIP website hosting extracts the archive and serves index.html, CSS, JavaScript, and images as a real website. Visitors open pages instead of downloading your files.

Can I update the website without changing its link?

Yes on a paid GeminiLaunch plan. Lite ($5/mo) is the lowest plan that allows editing and republishing at the same address. Free sites remain online as first published.

Can I use my own domain for a website uploaded as a ZIP?

Yes. Publish on a free subdomain first, then connect one custom domain on Lite ($5/mo), up to 5 on Pro ($15/mo), or unlimited domains on Scale. SSL is included.