To export code from Kimi Websites, open the website’s conversation, open All Files, and use the download control to save the project files to your computer. This is the route described in the official Build guide.
Last verified: October 12, 2026.
Kimi’s current documentation calls the website builder Kimi Build. The steps below follow its documented workflow, with checks for the revision, downloaded files, and services your project needs outside Kimi.
You can export an existing project without rebuilding it. Downloading obtains files for editing or deployment; publishing makes the site accessible online through Kimi. The Build overview documents these as separate actions.
How to download your Kimi website project
1. Open the original website conversation
Sign in to Kimi Build and reopen the conversation where the website was created. Work from the completed project’s conversation so you can access its version cards and files.
If you only have a shared website URL, ask its creator for the source package or appropriate project access. Viewing the published page does not establish access to the original project files.
2. Confirm which version you want
Identify the saved revision you intend to export. Open its preview and note one recognizable change, such as a revised heading, an added page, or a corrected link.
The version and preview documentation describes downloads for different versions. However, do not assume that changing the preview automatically changes every file offered in All Files. Confirm that the package represents the revision you want.
Restore rolls the project back to a historical version. Use it when you intend a rollback; it is not a step to take automatically just to obtain an older download.
3. Open All Files and identify the project package
Open the All Files card in the conversation and inspect the available files. The Preview / Code switch can help you inspect source code and the file tree, but viewing code alone does not save the project to your device.
Kimi’s full-stack documentation describes downloadable ZIP deliverables containing project code, including frontend and backend code where applicable. Identify the package that belongs to your chosen version.
For a complete handoff, download the complete project package when offered. If you use an individual-file download, keep in mind that the selected file may depend on other files in the project.
4. Download and locate the actual file
Use the download control in the file panel. Then open your browser’s download history and locate the saved file on your computer. Check that the download completed and that you can open the archive or file.
An archive filename mentioned in Kimi’s answer is not enough to confirm a successful export. If several packages or folders appear and their relationship is unclear, ask Kimi to identify the correct one before downloading a mixture of revisions.
5. Extract into a separate folder
Extract a ZIP into a new local folder and retain the original archive as a backup. Keep the exported directory structure intact. Moving an HTML file away from its stylesheets, scripts, or images can break the references between them.
Label your local folder with the project and revision so a later download does not overwrite the copy you have already checked.
A prompt for a clearer export or developer handoff
If the file list is confusing or the package lacks useful instructions, identify the saved version you want in the conversation, then use this suggested request. It asks Kimi to package existing work and document its requirements.
Prepare a downloadable source-code handoff for the saved website version I just identified. First state which version and project files you will package. If you cannot match those files to the requested revision, explain the uncertainty and ask me to confirm before proceeding. Preserve the website's source, design, and behavior. Do not regenerate it, publish it, restore another version, or install or update dependencies. Create a separate package containing the source files, required local assets, existing dependency manifests and lockfiles, and safe configuration examples needed to edit and run this version. Exclude real passwords, tokens, private credentials, and personal database records. Use placeholders in configuration examples. Identify remote assets and services that are not bundled. Add HANDOFF.md with: - The exported version and how it was identified. - The project type and entry point. - Prerequisites and run/build instructions supported by the actual project configuration. - Required backend, authentication, database, and other services. - Missing files, omitted data, and unresolved setup requirements. Expose the package as an actual downloadable file. Describe what it contains and report anything you could not include. Do not claim that an untested local run or migration succeeded.
This is a request template. After downloading, inspect the package and its handoff notes yourself. A generated checklist or a statement that the ZIP is ready does not confirm that the correct files are inside.
Check the files before choosing a local startup method
Open the extracted folder in a code editor and read any README or handoff notes. The files determine how to run the site; the fact that Kimi generated it does not establish a universal setup.
| What you find | What to do next |
|---|---|
| A self-contained HTML file | Open the extracted file in a browser and check its behavior. Confirm that it really contains everything it needs. |
| HTML with separate CSS, JavaScript, and image folders | Keep the structure intact. Check linked paths and use a local HTTP server if the project requires one. |
| Framework source with a package manifest and dependency files | Read the declared runtime, package manager, dependencies, and scripts. Follow the project’s own installation and startup instructions. |
| Server code or dependencies on authentication, APIs, or a database | Identify and configure those services before expecting the entire application to work locally. |
As MDN’s local-server guide explains, some examples fail when opened through file:// because they need HTTP requests or server-side processing. A local server can address the file-loading requirement, but a static-file server does not replace an application backend.
For a project with package.json
Inspect package.json in a text editor. Its scripts and dependencies help identify the project’s tooling. Use its README and existing dependency files to establish the intended package manager and runtime.
If the project uses npm and npm is installed, open a terminal in the project’s package folder and list its available scripts:
npm runThe npm command documentation confirms that running this without a script name lists the defined scripts. Check that list before using a command such as npm run dev or npm run build. The appropriate command and output directory depend on the project.
If instructions are missing or contradict the files, ask for corrected handoff notes before installing a different framework or changing dependencies.
Verify the exported copy
- Revision: confirm that the recognizable change you noted in Kimi appears in the local copy.
- Files and assets: check the main pages, styles, scripts, and images, including any references to remote resources.
- Behavior: try the main controls, navigation, and a narrow browser layout. Record the specific action that fails.
- Saved data: where relevant, reload the page and check whether information persists through the storage mechanism the project actually uses.
- Reproducibility: confirm that the documented startup procedure works from the extracted folder, with required services configured.
These are checks to perform on your project. If you correct the website in Kimi afterward, download the corrected revision into a separate folder and repeat the affected checks.
What does not automatically transfer with the code?
Exporting application code does not automatically move Kimi’s managed services or stored records. The self-deployment FAQ identifies two important boundaries:
- Kimi account login: the platform-provided sign-in capability cannot simply be used unchanged on your own host. A project relying on it needs an appropriate replacement authentication setup.
- Platform-managed database data: those records are not included in the code export, and the exported project does not automatically connect to your own database. You need a database setup and a separate data migration.
Use our Kimi website publishing guide to distinguish managed publishing from hosting an exported copy.
Backend source can therefore be included while the service it depends on still needs configuration. Keep a code backup and a data backup as separate deliverables.
Also check for external images, fonts, API endpoints, and configuration values. A file that references an online resource has not necessarily bundled that resource. Document what must remain available or be replaced before moving the site to another host.
Can you export Kimi code directly to GitHub?
The documented Kimi workflow is download through All Files. Although the official FAQ’s question mentions GitHub, its answer confirms local download; it does not establish a native repository-export or synchronization feature.
After reviewing the package, you can add the extracted source to your own repository. For a small project in an existing repository, GitHub’s browser-upload instructions use Add file → Upload files, followed by reviewing and committing the changes. Add the extracted project files when you want the source to be individually editable and tracked.
For an ongoing development workflow, follow GitHub’s guide to adding locally hosted code. Review files before committing so passwords, tokens, and private configuration are excluded.
If you encounter the kimi export terminal command, the Kimi Code reference describes a session archive for sharing or diagnostics. That archive is a different deliverable from the website source package covered here.
Does downloading the code require payment?
Kimi advertises free trial credits for website generation. Its public export instructions describe the download route without specifying a separate download fee, an export allowance, or a paid export gate. Check any restriction shown for your account; the documentation alone does not establish unlimited free exports.
If Kimi performs additional agent work to revise or prepare a package, that work falls under its usage-based credit rules. Treat generation and repair work, downloading existing files, and hosting elsewhere as separate cost questions.
Fix common Kimi website export problems
First identify where the failure occurs: the Kimi project, the download, the extracted files, or the local runtime. This keeps a packaging problem from turning into an unnecessary website rebuild.
| Problem | What to check |
|---|---|
| All Files or the download control is missing | Reopen the original completed website conversation. Check its file and version cards. If the expected package is absent, ask Kimi to identify and expose the downloadable project. |
| Kimi printed a path but no file downloaded | A path such as /mnt/agents/output/app/ refers to Kimi’s agent environment. Open the actual file panel and use its download control; the printed path is not a folder on your computer. |
| The archive contains an older revision | Compare the exported files with the intended version’s recognizable change. Request a package for that saved revision without overwriting the copy you already have. |
| Images, styling, or scripts are missing | Check whether all project folders were extracted together, whether the referenced paths exist, and whether any resources still depend on remote URLs. |
| The local page is blank or its controls fail | Check the project’s runtime instructions and exact error. Determine whether it needs a local HTTP server, a build step, missing dependencies, or an application backend. |
| Project files appear to be lost in Kimi | Preserve any downloaded copies. The official FAQ describes recovery from historical snapshots; identify the intended version before requesting recovery. |
For Kimi-side file or preview issues, consult the official troubleshooting guidance. If recovery or download still fails, report the conversation or project reference, intended version, browser, and exact symptom through Kimi’s support channel. Keep your available exports while the issue is investigated.