Open the code editor
At the top of the Figma Make file, click Code. Figma says viewing and downloading code is available to people with a Full or Dev seat.
Limited-time offerPro & Max plans — 20% offSave 20% on monthly and yearly billing.
Save 20% on monthly and yearly billing.
Figma Make export hosting · Updated October 9, 2026
Downloaded a Figma Make prototype? Build the frontend and turn it into a browser link for client review, user testing, or mobile QA. The link shows the exported build, outside the Figma review flow.
Figma Make → Code → Download code → build the static frontend → HTMLShare → send the URL.
At the top of the Figma Make file, click Code. Figma says viewing and downloading code is available to people with a Full or Dev seat.
In the upper-right corner of the code editor, click Download code. The ZIP contains the files in that file explorer. App.tsx is the main file by default.
A self-contained HTML page can be uploaded as it is. A React project with package.json needs its dependencies installed and its production build run before a browser can load it.
Upload index.html plus the CSS, JavaScript, and images it references. Leave node_modules, secrets, and unbuilt source out of the archive.
Upload the files to HTMLShare, review the page yourself, then send the link. Reviewers open it in a browser. They do not need a Figma account for that preview.
The preview inside a Figma file is useful while you are still prompting. A client preview of the export is a separate URL that loads the files you built. Local changes to a download do not automatically return to the Make file.
If the download is HTML, CSS, and JavaScript that a browser can open with no compiler, keep those files together and upload them.
Figma's code editor selects App.tsx as the main file. That is source. Check package.json, install dependencies, and build before uploading the output.
If install or build fails, the archive may be missing a manifest, a dependency, or a config the imports expect. Fix that locally. Do not upload the broken source and hope the preview compiles it.
Read the scripts in the downloaded project. A typical npm React app looks like this:
npm install
npm run build
# Upload the generated files, often dist/If there is no package.json, do not invent a toolchain. Inspect the files and upload them only when a browser can already run them.
Send one URL for the real scrolling page, its breakpoints, and the interactions that survived the export. Ask the client to review the built page, not to join the Figma file.
Prompt, edit, and preview the prototype inside the Make file.
Boundary: The review stays in Figma. Code download is a snapshot of the file explorer, and local edits do not sync back on their own.
Publish a site with Figma's own website product.
Boundary: HTMLShare does not import a Figma file or replace Figma Sites.
Share the exported, browser-ready build for client review and phone QA.
Boundary: It serves the static files you upload. It does not build Make source or run a backend.
Uploading App.tsx and unbuilt imports produces a blank page or a download, not the prototype. Build first, then upload the output.
If npm install fails or imports point at packages that are not declared, add the missing dependencies in the local project and build again.
Keep the built asset folder next to index.html. Open an internal route directly only if the host is configured for that client-side app.
Supabase, private APIs, server functions, and secrets do not travel with a static upload. Review the interface, and keep those services on a host that can run them.
HTMLShare does not import from Figma, convert a design file, or sync later edits back into Make. Publish a new ZIP when the export changes.
FAQ
Open Code, download the ZIP, build the frontend if it is a React project, and upload the browser-ready files to HTMLShare. Share the preview URL.
Yes. Figma's help center says to click Download code in the upper-right of the code editor. Viewing and downloading requires a Full or Dev seat. The ZIP includes the files in the file explorer.
Only when it already contains browser-ready HTML and assets. If App.tsx and package.json are the main contents, build the project first.
Build it when the download is framework source. Skip the build only when the files are already static HTML, CSS, and JavaScript.
Yes for a static review link. Figma also documents pushing Make code to GitHub, which is a separate path for continued development.
Yes. Send the HTMLShare URL so the client can scroll, resize, and click the exported build in a normal browser.
The HTMLShare preview opens in a browser without a Figma login. Downloading the code from Figma itself still follows Figma's seat rules.
Open the preview URL on the phone or scan the QR code on the publish result. Check layout, tap targets, navigation, and scrolling there.
The ZIP is the code from the file explorer, not a guaranteed production build. Check for package.json, install dependencies, and run the project's build script. Fix missing packages before uploading.
No. Use it for a static export you already have. Figma Sites remains Figma's product for publishing a site from Figma.
Upload the static output and send one link for client review. Keep server functions and private APIs on a host that can run them.