Configuring the export directory

By default, Site Designer asks you where to export every time you run an export. If you always export to the same folder — a Git repository, a Netlify drop folder, or a deployment directory — you can set a persistent default to skip that prompt entirely.

Setting a default export directory

1. Go to Settings → Export.
2. Under Default Export Directory, click Browse and select your target folder.
3. Click Save.

From this point on, every export goes to that folder without a dialog. Site Designer overwrites the existing files on each export — unchanged files are replaced, and files from previous exports that no longer exist in the project are left in place (they are not deleted automatically).

Changing or removing the default

To change the default: go to Settings → Export and click Browse again to choose a new folder.

To remove the default (revert to always asking): click the Clear button next to the path field. Site Designer will prompt for a location on every export again.

Why a persistent export directory matters

Git-based workflows

If your export folder is a local Git repository, your workflow becomes:

1. Design in Site Designer.
2. Export (one click, no dialog).
3. git add . && git commit -m "…" && git push.
4. Netlify or Vercel auto-deploys on push.

This is the closest thing to a CI/CD pipeline available without a build server.

Netlify drag-and-drop

Netlify allows you to deploy by dropping a folder onto their dashboard. Set your export directory to a dedicated deploy folder, export, then drag that folder to the Netlify dashboard.

GitHub Pages

Set the export directory to the docs/ folder (or root) of a GitHub Pages repository. Export, then push. GitHub Pages serves the latest committed HTML automatically.

Asset path options

Two path modes are available in Settings → Export → Asset Paths: