Forge Guide › Exporting and hosting
Exporting and hosting
Export gives you a plain static site. No build step, no framework, no editor metadata - just the files a web server needs.
Export options
| Option | Produces | Use when |
|---|---|---|
| Export website | A zip with the full folder structure | You are publishing a real site |
| Export this page | One self-contained HTML file | You want to email or attach a single file |
| Save project | A .forge.json file | You want to keep editing later |
The zip looks like this:
your-project/
index.html
about.html
css/
style.css
forge.css
js/
blocks.js
assets/
hero.png
What gets stripped
Everything the editor added for its own use:
data-fx-idattributes used to map the canvas to the model- The canvas runtime script
- Editor-only CSS such as the empty-container outlines
- Generated
fx-classes that no rule uses any more
That last one matters over a long editing session. If you style an element and later remove the style, the class it created is dead weight; export removes it rather than shipping it.
Checking the output
Unzip and open index.html directly in a browser. Because everything is relative, it works
from the filesystem without a server. If it looks right there, it will look right hosted.
The single-file export inlines your CSS and embeds images as data URLs. It is convenient for sharing but larger than the folder version, so use the zip for anything you actually publish.
Hosting it for free
A static site can be hosted free on several services. In each case you are uploading the contents of the unzipped folder.
Cloudflare Pages
Create a project, choose direct upload, and drag the folder in. Free, fast, and includes HTTPS and a custom domain.
Netlify
Drag the folder onto the Sites page. It deploys immediately and gives you a URL you can rename.
GitHub Pages
Commit the files to a repository and enable Pages in the settings. Best if you want version history alongside hosting.
Editing again later
Two routes back in. Import the exported folder, which works like importing any site - or save a
.forge.json project file before you export and reopen that, which additionally restores your
pages, breakpoints, components and assets exactly as you left them.
For anything you expect to revisit, save the project file. The exported folder is the deliverable; the project file is your working copy.