Skip to content

Create & connect

Publish and export a Build project

Publish a selected Build version, update site details, or export project files to HTML, ZIP, or GitHub.

Build versions and the public site are separate. Publishing makes one selected version available at an address shown in the Publish panel. Later Build answers and manual saves create versions but do not replace the public site until you publish the version you want. You need a verified email to publish.

Download and GitHub export are separate from publishing and are available on paid plans only. A site address is a Neurothread-provided subdomain displayed by the app; custom domains are not offered in this workflow. Review your project carefully before making it public.

Publish when you are ready to share a working browser app. Use Publish this version to change the code served by a site that is already published. Use Save changes for site details such as its address, title, description, and sharing options; that action does not publish another project version. Use Download for a local copy, or GitHub export to create or update a repository through your connected GitHub app.

  1. Open Your app and select the Build version you have tested. Check its preview and version title; a newly generated or manually saved version is not automatically public.
  2. Choose Publish. Review the available address, title, optional description, and any sharing controls. The address is checked for availability as you edit it. Use only a slug the app reports as available.
  3. Verify your email if prompted. Review the published-site terms and choose Publish. When the operation succeeds, copy the site URL from the panel and open it in a separate tab to check the public result.
  4. To update the code later, select the version you want in the workspace and open the site panel. If it says the site shows another version, select Publish this version. Confirm that the public site displays the newly selected code.
  5. To change only metadata or sharing settings, edit the address, title, description, or available options and choose Save changes. Do not use this button when your goal is to publish another code version.
  6. To take the site offline, choose Unpublish and confirm. The app warns that the address will stop working; check the project and current site status in the panel afterward.
  7. For a portable copy, choose Download and select Single file (.html) or Project files (.zip). For GitHub, choose GitHub, enter a repository name, choose whether it is private, and export. Connect GitHub in Settings → Connected apps first.

You have checked version 4 on mobile and desktop and want to share it. Select version 4, open Publish, choose an available address, review the title and description, and publish. Later, you save version 5 while improving the form. The live site remains on version 4 until you select version 5 and choose Publish this version. If you only correct the site description, choose Save changes instead; the code remains version 4.

The site URL opens the published code, not your editing panel. Keep using Build branches to experiment without changing the live site; publish the version you intend to serve when it is ready. Downloaded files can be opened or stored outside Neurothread. GitHub export uses your connected GitHub integration to create a repository or update the repository already associated with the project; it is not a substitute for checking repository visibility and contents.

Publishing requires verified email, a valid available slug, and room under the current plan’s published-site limit. The app reports whether an address is available; slugs must be 3–40 lowercase letters, numbers, or hyphens, without a hyphen at either end, and some addresses are reserved. Free sites keep the Neurothread bar, allow remixing, and stay out of search engines. Paid plans expose the controls to hide the badge, turn off remixing, and allow indexing. Download and GitHub export are paid-only; the app shows the feature wall if your plan does not include them. Current plan details can change, so check pricing. Published pages are public: do not include API keys, passwords, private customer information, or other secrets in project files or client-side code. Build projects are browser-side apps, not server-side services.

  • Publish asks for email verification: use the verification link sent to your email or choose the resend option shown in the panel.
  • The address is taken, reserved, or invalid: follow the panel’s message or suggestions and wait for the availability check before publishing.
  • The wrong code appears on the live site: select the intended version and choose Publish this version. Save changes only saves site details.
  • The site is under review or not displayed: read the status shown in the Publish panel; a site may be reviewed before it is served.
  • Download or GitHub is blocked: these exports require a paid plan. For GitHub, also connect an account that provides the required repository and file tools.
  • GitHub export fails: reconnect GitHub in Settings → Connected apps, check repository naming, and try again. A repository conflict may require choosing another name.