Move a Solo site to a static host

Open the free tool →

Last checked: 2026-10-18

This path hosts the tool's HTML as-is. Rebuilding in WordPress or Carrd is a copy-paste job instead.

Start from the tool ZIP

Unzip website-ready-to-host.zip. Stop when index.html sits next to images/ (and assets/ if styles were saved). Nested pages stay in folders such as about/index.html.
Double-click index.html and check that pictures load.
Host that folder (or the website ZIP). Never upload private-form-data-do-not-upload.zip.

Cloudflare Pages (Direct Upload)

Cloudflare accepts a zip file or a single folder. (Direct Upload)

Dashboard → Workers & Pages → Create application → Get started → Drag and drop your files.
Enter a project name.
Drop the folder that contains index.html, or drop website-ready-to-host.zip.
Deploy site (the doc also says Save and Deploy).

The site is at <project-name>.pages.dev. Later: open the project → Create a new deployment.

Drag and drop allows 1,000 files and 25 MiB per file. Wrangler allows 20,000 files. If you choose Direct Upload, you cannot switch that project to Git later.

Netlify Drop

Log in to Netlify first. Drop works without an account, but if you drop without signing in, the site is protected with a temporary password until you claim it. (Netlify Drop quickstart)

Log in at app.netlify.com/login.
Go to app.netlify.com/drop.
Drag the folder that contains index.html onto the drop zone.
If the project is private, use Make public after a successful production deploy. On credit-based plans, new projects can start private. (Project visibility)

Deploys under 50MB work best; files over 10MB may get stuck. To update: drop a new folder under Production deploys.

What carries over / what doesn't


Pages	Yes. `index.html` at the ZIP root, plus nested HTML.
Text	Yes. It is already in the HTML.
Images	Yes. Files in `images/`; HTML already points at them.
Styles / fonts	Yes, if the tool saved them under `assets/_next/`. Solo JS is stripped, so buttons that needed it will not run.
Forms	No. Static files cannot send Solo's form.
Form submissions	No. They are only in the private ZIP: `contact_form_submissions.csv`, `newsletter_submissions.csv`.

Custom domain

If you bought the domain through Solo Domains (not IONOS), move it to Name.com first. (Solo Shutdown FAQ)

Add the domain in the host before you change DNS.

Cloudflare Pages: project → Custom domains. A subdomain uses a CNAME to <your-site>.pages.dev. A bare domain (example.com) must be a zone in that Cloudflare account. Adding a CNAME without associating the domain in Pages leads to a 522. (Custom domains)
Netlify: project → Domain management → add a domain you already own. A subdomain uses a CNAME to your *.netlify.app site. Leave MX records alone if you use email on the domain. (External DNS)

FAQ

Which ZIP do I upload?

Only website-ready-to-host.zip, or the unzipped folder with index.html at the top. Never upload private-form-data-do-not-upload.zip.

Do I need to log in to Netlify before using Drop?

Yes, log in first. Drop works without an account, but if you drop without signing in, your project URL is protected with a temporary password until you claim it.

Is there a file limit on Cloudflare Pages drag and drop?

Yes. Cloudflare lists 1,000 files and 25 MiB per file for drag-and-drop uploads.

Will my Solo contact form work?

No. The tool strips Solo scripts, and a static host cannot send the form. Old submissions are in the private CSV ZIP.

What happens to my export when I use the free tool?

Your export stays in your browser. Public images and styles are downloaded through our server. We count anonymous page visits.

Sources

All fetched 2026-10-18.

Cloudflare: Pages Direct Upload · Pages custom domains
Netlify: Netlify Drop quickstart · Project visibility · Configure external DNS
Solo: Solo Shutdown FAQ
Tool: Site Export Rescue · Export guide

Not affiliated with Mozilla, Solo, Cloudflare or Netlify.

Your export stays in your browser. Public images and styles are downloaded through our server. We count anonymous page visits.