Before making major changes, deleting your website, or handing off content, creating a website backup allows you to keep a local copy of your important data. Kanorio compiles your exportable website content into a ZIP file—a format that bundles multiple files into a single, downloadable package.
This backup is designed for preserving and organizing your website content; it is not a website application that can be deployed directly to another host. Since different website builders use unique layouts and data structures, you will typically need to reorganize your content when migrating.
Need to revert a page or post you edited a few hours or days ago? You do not need to download a ZIP backup. Both the website editor and the blog post editor feature built-in that retains data for 30 days. Simply click any timestamp to preview it on the canvas and restore it to a draft with one click.
At Kanorio, website and data backups are categorized into two levels: "Self-service restoration and export" (which you can manage in the dashboard) and "Platform-level automated disaster recovery":
| Your needs or scenarios | Corresponding protection mechanism | Retention period and notes |
|---|---|---|
| You made a mistake on a page or post recently and want to revert to a previous version | (built into the editor) | All plans retain data for 30 days (the latest published version is kept indefinitely). You can preview directly on the canvas and revert a single page or the entire site draft with one click—no need to download ZIP files or wait for support. |
| You accidentally deleted an image, video, or PDF from the Media Library | Items are retained for 30 days after being moved to the trash. You can restore them with one click at any time during this period, and page references will be automatically recovered. | |
| You used AI to batch-fix SEO and want to revert to the original titles and descriptions | You can revert individual or batch changes with one click within 7 days of the correction. | |
| You accidentally deleted your website and want to recover it | After a website is deleted, it is archived for 60 days. During this period, the site owner can restore it with one click from the dashboard. | |
| You want to keep a full copy of your content and assets on your computer, or provide them to an engineer to rebuild the site | Create Website Backup (ZIP) and Export CSV (explained in this article) |
Regarding the scope of platform-level backups: Like most major multi-tenant cloud website builders, Kanorio's underlying daily encrypted backups and point-in-time restoration are designed to recover the entire platform service in the event of major infrastructure failure or catastrophic accidents. They cannot be used to roll back individual orders, contacts, or specific settings for a single website. For daily page edits, accidental file deletion, or site deletion, please use the self-service restoration tools in the table above, or regularly export your important contact lists and order CSVs for safekeeping.
Switch to the website you wish to back up in the dashboard and open "Website Settings" → "Website Management".
Under "Backup Website Data," select the content you wish to save, such as website content and settings, images, PDFs, audio, video, or digital product download files.
If you are unsure what to select, we recommend keeping all content. This ensures you have a comprehensive reference for future organization, migration, or repurposing.
Click "Create Backup." For websites with smaller data volumes, the download for the ZIP file will usually start immediately. For larger sites, the system will prepare the backup, and a download button will appear in the same location once it is ready.
You can continue using the dashboard while the backup is being prepared and return here later to check the progress.
Small websites usually download as a single ZIP file containing the site's content and assets. If the site is large or you only selected specific content, you may see multiple downloadable files, such as website content, images, PDFs, or videos.
Please store all downloaded files in the same folder. Backups prepared in the background are available for download for 7 days; after this period, you can create a new backup.
Depending on your selections, the backup may include:
Even if the same file is used in multiple places on the site, the backup typically only retains one copy to avoid duplicate downloads.
Kanorio is a platform-hosted website service, so you don't need to maintain servers, update software, or handle daily security settings yourself. However, this does not mean your content is locked into Kanorio.
If your brand decides to have an engineering team rebuild the site using a different framework, or if you want to explore Vibe Coding, AI Coding, or other self-development methods, this backup serves as a hand-off package for your content and assets.
Engineering teams can extract the following from the backup:
site/website.json: Website name, brand settings, and site-wide data.site/pages.json: Content structure for each page, drafts, published content, and page SEO settings.blog/posts/*.md: Blog posts that can be read and edited directly, along with structured post data.collections/schema.json and collections/<key>.json: Field definitions for collections and item data for each collection.seo/: SEO files like Sitemap and robots.txt to help maintain existing search settings.images/ and media ZIP: Website images, PDFs, audio, video, and other original assets included in the backup.commerce/products.json: Structured data for products, pricing plans, and digital content (does not include orders, customers, or payment records).JSON is a common structured data format for engineers, while Markdown is a format that can be opened with any standard text editor. These files allow engineering teams to focus their time on redesigning the site and its functionality rather than manually copying text, downloading images, or guessing the content structure from the old site.
This backup is not a website application that can be deployed directly. The new website will still require an engineering team to build the front-end, interactive features, database, login, payment, and third-party service integrations.
If your next destination is WordPress, WordPress-specific export formats are usually more direct. If you plan to use a non-WordPress framework or build from scratch, Kanorio's structured JSON, Markdown, and original assets are generally easier to organize and rebuild; however, they will still need to be adapted to the technical requirements of the new site and will not automatically transform into a new website.
If you are doing the opposite—moving old site articles into Kanorio—please use the "Import from other websites" feature in (by pasting the public article URL). This backup feature is for taking content out of Kanorio; the two are different.
The following data is not included in the website backup:
README.txt in the ZIP, read the instructions first; then open the JSON and Markdown files in folders like site and blog to confirm that important pages, posts, and settings are present.manifest.json in the backup, you can use it as a file list to check which content has been prepared or if there are items that need further verification.Do not delete your website just because the ZIP has been downloaded. Please ensure that the content you care about most can be opened on your own computer first.
Creating and downloading backups requires the "Backup Website Data" permission (Owners and Admins have this by default). Please confirm that you are viewing the correct website; if your role does not have this permission, you can request it or ask the website Owner or Admin to create the backup.
When there is a large amount of data, the system separates different types of content so you don't have to handle excessively large files at once. Please save all downloaded files in the same folder; each file can be downloaded individually.
Try downloading the same file again; if the backup is older than 7 days, please create a new one. If you still cannot find the content, check if manifest.json lists any hints, and Contact Us with your website name, file name, and a screenshot of the issue.
Usually, no. The backup preserves your content, images, settings, and assets, but different platforms use different layouts and data structures. You can use the files as a source for organization and migration, then process them according to the new platform's import methods.
Yes, you can hand it over to your engineering team or use it as a source of content and assets for self-development. JSON, Markdown, images, and media files can help you rebuild your new site; however, the backup is not deployable code, and new layouts, features, databases, and third-party services will still need to be created.
Website backups and store operation data are separate scopes. For orders, please go to Orders and Shipping Status; for customers, please go to Customer List and Subscriptions to download the required CSVs.
No. The platform's underlying daily encrypted backups and point-in-time restoration are designed for disaster recovery of the entire platform in the event of major cloud infrastructure failures. They cannot be used to roll back individual orders or contacts for a single website. We recommend exporting CSVs from Orders and Shipping Status or Customer List and Subscriptions before performing bulk cleanups. If you make a mistake on page or post content, you can use the Version History (which retains data for 30 days) to restore it yourself at any time.
| All plans allow you to download structured JSON, Markdown, and original image/video assets in a ZIP file for free. Order and customer lists can be exported separately as CSV files. |
| Protection against cloud server outages or major infrastructure incidents | Platform-level daily automated encrypted backups and disaster recovery (system-automated) | The platform performs daily off-site encrypted backups of the main database and website media files, stored in an isolated cloud backup environment separate from the production environment (database encrypted backups are retained for up to 90 days, with support for point-in-time recovery and regular restoration drills). |