Export & import
Back up sites as .nertia.json, restore content, or import from a URL.
nertia treats your site as portable data — layout, style, and content in one JSON file. Export is first-class, not an afterthought.
Export a site
- Go to Sites (
/sites). - Click Export in the toolbar.
- One site → downloads immediately.
- Multiple sites → pick which slug to export.
- Browser saves
{slug}.nertia.json.
What is in the file
| Field | Contents |
|---|---|
version | Export format version |
slug | Site address (e.g. my-biz) |
compositionId | Layout reference |
sections | Section instances (order, types, config) |
copy | All text fields keyed by binding |
skinId | Active style / design system |
ds | Token overrides |
Not included: billing, custom domain DNS state, analytics, form submission history, or account ownership. Moving a site to another nertia account is not supported today — export is for backup, versioning, and restore on the same slug.
Import a JSON export (restore)
Import replaces all content on an existing site. It does not create a new slug.
- Go to Sites → Import.
- Choose a
.nertia.jsonfile. - Confirm the dialog — Replace all content of "{slug}" with imported data?
- The file’s
slugmust match a site already in your account. Otherwise you see: No site "{slug}" in your account.
Typical uses: restore after experiments, sync from a dev copy, roll back to a saved snapshot.
Export my-biz.nertia.json → edit offline → Import (same slug my-biz)
Import from URL (new site)
Different flow — creates a new site.
- Sites → Import URL.
- Paste a website URL, or switch to Paste HTML.
- Set the slug (e.g.
acme→acme.nertia.ai). - Click Import Site.
- You land in the editor for the new site.
The importer extracts content, layout hints, and design signals from the page. Results vary by source site — always review sections and copy in the editor.
Compare the three paths
| Action | Where | Creates new slug? | Replaces existing? |
|---|---|---|---|
| Export | Sites toolbar | — | — (download only) |
| Import (JSON) | Sites toolbar | No | Yes — matching slug only |
| Import URL | Sites toolbar | Yes | No |
Style export (separate)
Exporting a style / design system from /styles workshop is separate from site export. Site JSON carries the skinId and ds tokens applied at export time — not the full style library definition.
Limits & honesty
- JSON import cannot rename a slug — create the site first, then import.
- URL import does not attach a custom domain or copy Stripe subscriptions.
- CLI and MCP can also read/write site data — see Tools for power users.
Quick reference
Backup: Sites → Export → {slug}.nertia.json
Restore: Sites → Import → confirm replace (slug must exist)
New site: Sites → Import URL → pick slug → editor