Designers already ship files; hosting should respect that
If your deliverable is HTML/CSS—whether you wrote it, exported it from Webflow, or generated it from a Figma-to-HTML pipeline—you need a place to put those files on the public internet with HTTPS and a domain. You do not need to become a Node release engineer on day one. StaticHost is file-oriented: zip upload, optional GitHub, preview TLS immediately, custom-domain certificates after DNS verifies, rollback via deploy history.
It will not run npm for you, will not provide cPanel, will not host mailboxes, will not include a built-in CDN product, and will not forever-free host after a ~1 day trial. Plans start at Starter $9/mo (1 site, 2 GB).
Webflow (and similar) export path
- Export the site from the design tool as HTML/CSS/JS/assets.
- Unzip locally and open
index.htmlto spot-check. - Re-zip the contents so
index.htmlsits at the archive root—nested zip 404s. - Upload to StaticHost; open HTTPS preview.
- Fix asset paths if the export assumed a subfolder.
- Point the client domain when approved—custom domain.
CMS-driven Webflow features that need Webflow’s hosting will not keep working as dynamic CMS on a static export. Know what the export contains before promising the client parity.
Figma-to-HTML pipelines
Whether you use a plugin, Anima-style tools, or hand rebuild in code, the hosted artifact must be a coherent folder. Treat the tool output as a build: verify links, font files, and absolute vs relative paths. Grep for http:// before going live on HTTPS—mixed content.
Hand polish in a code editor is normal. Re-exporting from Figma later may overwrite polish—establish a source of truth (often the code after first export).
Interaction and routing
Microinteractions in JS are fine as static assets. Full app routers in history mode are not fine without files or hashes—SPA. Most marketing designs are multipage or single-page with anchors; keep them that way unless engineering owns the router decision.
Client review ritual
- Share StaticHost HTTPS preview (no DNS wait).
- Collect feedback.
- Redeploy; use rollback if a revision is worse.
- Cut DNS only for launch.
Pro ($30, 3 sites, 10 GB, staging) lets you keep staging and production for a picky brand launch. Scale ($65) / Business ($130) when you juggle many client properties—agencies.
What to refuse politely
- “Can we install WordPress on this so marketing can edit?” → Different host category for PHP; or introduce a headless CMS + rebuild workflow.
- “Can we have email @thedomain?” → Mail vendor, not StaticHost.
- “Can unknown routes open the main page like my old host?” → No; product is
=404.
Portfolio of your own
Designers need a portfolio too—static portfolio hosting. Keep it on Starter; put clients on separate sites as you upgrade tiers.
Handoff package naming
Name deliverables client-project-YYYYMMDD-static.zip with the flat root already verified. Include a one-line text file listing the primary CTA URL and form endpoint. Engineers should not have to reverse-engineer intent from leftover Webflow class names when the launch calendar is tight.
Worked example: Webflow export to client domain in five moves
You finished a five-page brochure in Webflow. The client owns northwind.example.
- Export; unzip; confirm pages and
css/js/images/sit besideindex.html. - Re-zip contents (not the outer folder). Upload to StaticHost on Pro so you can use staging.
- Open HTTPS staging preview; client comments on spacing. Adjust in Webflow or in the exported CSS—pick one source of truth—re-export/re-zip/redeploy staging.
- When approved, deploy the same artifact to production; add
northwind.example(+wwwif needed); create DNS records; wait for verification; wait for certificate. - Final pass on the custom domain: forms (third-party endpoint), fonts, and no
http://assets.
You did not run npm on StaticHost. You did not get mailboxes. You did get a reversible file host with HTTPS preview first—the order that prevents “DNS is live but CSS is missing” drama.
Failure table: designer exports on static hosts
| Symptom | Likely cause | Fix |
|---|---|---|
| Preview unstyled | Nested zip / wrong asset paths | Flatten; fix relative links |
| Fonts fallback to Arial | Font files omitted or hotlink blocked | Self-host fonts in the zip |
| CMS collection pages missing | Dynamic Webflow CMS not in export | Rebuild as static pages or keep Webflow host |
| Form does nothing useful | No endpoint | Form SaaS; StaticHost ≠ email |
| Client deep link 404 | Fancy router in export | Multipage files or hash; see SPA guide |
| Mixed content on HTTPS | http:// asset URLs | Grep and fix before launch |
| “Can you roll back?” panic | Overwrote without noting deploys | Use deploy history; name zips by date |
Extra procedure: designer–developer handoff sheet
Attach a short plain-text HANDOFF.txt in the zip:
Primary CTA: https://app.example.com/signup
Form endpoint: https://forms.example.com/...
Canonical host: www.example.com
Router notes: multipage HTML only (no history SPA)
Fonts: self-hosted in /fonts
Build date: 2026-08-31Engineers wiring CI later should replace zip uploads with artifact branches—but the contract stays the same: StaticHost serves prebuilt files, try_files $uri $uri/ =404, certificates after DNS verifies, plans $9/$30/$65/$130, no forever-free, no cPanel, no CDN product. Your job is a clean tree; their job is automation—not a surprise WordPress install.
Accessibility and export quality before the host sees anything
Hosting cannot fix low-contrast text, missing alt attributes, or buttons that are only <div onclick>. Before you zip for StaticHost, run through a short design QA that belongs to the craft, not the server:
- Every image that carries meaning has alt text in the HTML export.
- Focus states are visible on links and buttons.
- Hit areas are usable on mobile widths you actually preview.
- Motion respects
prefers-reduced-motionif you shipped heavy animation JS.
Then publish to HTTPS preview and re-check, because path bugs can hide CSS that contained your accessible focus styles. If a client demands a CMS after launch, do not promise WordPress on StaticHost; discuss headless content plus rebuild, or a PHP host. Your credibility comes from clean files and clear boundaries—zip discipline, preview-first review, DNS then cert—not from pretending the file host is a full design ops suite with mail and cPanel.
FAQ
Do I need GitHub?
No. Zip is designer-friendly. Git helps when developers join.
Can clients edit copy without me?
Not via a WP admin on this host. Options: you edit and redeploy; or a headless CMS with a build in CI you control.
Why fonts look wrong on preview?
Missing font files in the zip, or blocked hotlinks. Self-host font files in the project.
Is 2 GB enough for a brand site with video backgrounds?
Self-hosting large video is a smell; use a video host and keep the page light.
Will export from Webflow include forms that email?
Forms need endpoints. Wire them to a form provider; StaticHost will not send mail.