Docs
Start building
Code & Export

Self Hosting

Exported sites are plain static HTML: you can serve them from any static host. Here is what keeps working and what does not.

Hosting a website

Push it to GitHub, then serve the repository with any static host — GitHub Pages, Netlify, Cloudflare Pages, an S3 bucket, or your own web server. There is no build step: the files are the site.

What keeps working

  • Every page, its layout and its copy.
  • Photographs — they load from webforgia.com by their full address.

What changes when you host it yourself

  • Forms do not submit. The exported HTML has no form endpoint, so contact and newsletter sections are visual only. Point the forms at your own form service, or keep the site published on Webforgia to keep working forms.
  • Fonts fall back. Pages reference the typeface from /fonts/ on their own host. Copy the font files there, or the browser uses a system font.
  • No automatic HTTPS, domains or updates. Your host handles those, and later edits in Webforgia reach your copy only when you push again.

Running a cross-platform app

Terminal
unzip your-app.zip && cd your-app
npm install
npx expo start

Open it with the Expo Go app on a phone, or press w to run it in a browser. Building for the App Store or Google Play needs your own developer accounts — see Working With Exported Code.