Get Lifetime License (opens in new tab)

Export and deploy

What you get

Export produces an ordinary Next.js App Router project:

  • app/**/page.tsx pages, one folder per route
  • React components
  • Token-driven CSS
  • robots.txt, and a sitemap.xml when you have set a Public site URL
  • Your favicon, plus an Apple touch icon rendered from it
  • A package.json with everything needed to build, and a README.md

It builds with next build, deploys anywhere Next.js runs, and needs nothing from Qanvas to stay online. You can edit it by hand, add packages, or stop using Qanvas without breaking the site.

The export includes only your site: no conversation history, keys, logs or licence files.

The Export view

Open Export in the mode switcher.

Export details

The left deck shows:

  • Bundle archive name: the File name of the ZIP. It defaults to the project name; use letters, numbers and dashes only.
  • This export: the Project, Theme, number of Pages and Files, the Uncompressed size, and the Target (Next.js App Router).

Readiness

The centre card tells you whether the site is ready:

  • Ready to export: select Download ZIP.
  • Not ready to export: a page has a problem that would break the build, such as a missing title or a path used twice. Each issue is listed; fix it in Design and the button unlocks.
  • Not ready to publish: a setting the live site needs is missing.

Today the one publish setting is the Public site URL. Without it, the export has no sitemap.xml, no Sitemap line in robots.txt, no canonical URLs and no social share image. Select the button beside it to open the setting, or switch on Export without a public site URL to download anyway.

Qanvas also lists any broken links: links that point to a page or section that does not exist. You can still export, but those links will not work on the published site.

Run it on your computer

The Export view walks you through the same steps:

  1. Download & extract: unzip the archive into any folder.
  2. Open a terminal inside that folder.
  3. Run the dev server:
npm install && npm run dev

Select the copy button to copy the command. To check a production build instead:

npm install
npm run build
npm start

Deploy

The export is a standard Next.js project, so any host that runs Next.js works. A typical flow:

  1. Put the exported folder in a Git repository and push it to GitHub, GitLab or Bitbucket.
  2. Import the repository into your host (for example Vercel, Netlify, or your own Node.js server).
  3. Keep the host's default Next.js build settings (npm run build).

After that, re-export from Qanvas whenever you change the site and commit the updated files.

Ownership

Projects you export from Qanvas remain yours. The files your exported sites are built from are readable by design, because they are your output.