How to host a Figma Make project from GitHub

Figma offers two different publishing paths. Figma Sites lets you design and publish inside Figma, with an option to connect your own domain subject to current plan eligibility. Figma Make can push code to GitHub. If you want to deploy that repository outside Figma, you can connect it to Hostbrid Projects; first, understand how the sync works.

If you are unsure whether your project is static or needs a server, start by identifying what an AI-built website needs to run. This guide covers Figma Make’s code workflow, not exporting a Figma Sites file.

1. Check which Figma product you used

If you built the site in Figma Sites, start with Figma’s publishing flow and its guide to connecting a custom domain. A Figma Design file or prototype is not, by itself, a code repository ready to deploy.

If you worked in Figma Make, Figma’s current documentation lets you connect GitHub and create a repository for the project. That is the starting point for a Git-based host.

2. Push the Make project to GitHub

In your Make file, open Make settings → GitHub, connect an account or organisation, and create the repository from Make. Then use Push to… to send your changes. Figma’s current documentation says the integration creates the repository; it cannot target one you already created yourself. Changes flow from Make to GitHub in one direction and are pushed to the default branch.

Choose which tool will be the source of truth for your code. If you edit files directly on GitHub and later push again from Make, that push can overwrite those edits. Before continuing, confirm the latest change is on the repository branch and do not commit .env files, private keys or passwords.

Make pushes to GitHub’s default branch. Set that same branch as the production branch in Projects; otherwise, GitHub can receive the change without Projects publishing it.

3. Connect the repository in Projects

In the Hostbrid panel, open Projects → New project → Connect a repository and authorise GitHub if needed. Select the repository created by Figma Make. Projects starts a build and lets you check the production branch, install command, build command and output directory. The Projects guide explains each setting.

Do not assume Figma Make produces a static site. Check package.json, the README, environment variables and start command. If the repository produces static files, set the output directory created by the build. If it needs a Node process or Dockerfile, confirm that your Projects plan includes services and available quota; check the current plans and limits. Automatic detection helps, but it does not replace checking the result.

4. Test before connecting your domain

Open the temporary URL and check the homepage, direct entry to internal routes, images, mobile layout and forms. If the app uses Supabase, Firebase or another API, validate its URL, authentication, callbacks and permissions separately. Store server secrets in the service’s secure settings; VITE_ variables sent to the browser are public.

Projects publishes pushes to the configured production branch unless deployment is pinned to an earlier version. Check the build log and URL after each change. Connect your domain once the temporary version works and you know which services remain hosted by Figma or another provider. For React/Vite projects, also see how to publish React from Git.

Figma Make → GitHub → Projects is a documented route, not an automatic migration from Figma Sites or a guarantee that every app works without changes. Review Hostbrid Projects and confirm runtime, storage, database and plan limits before ordering.