Kimi · Practical workflow
How to export code from Kimi Websites
Use the project’s All files panel to download the files you can deploy or edit yourself. Our timer example shows the controls, file structure and checks that matter.
By China AI Chat Team · Tested 18 September 2026 · Official guidance checked 29 September 2026 · Independent guide
Where is the code download?
Open the website conversation in Kimi, then open the All files card. In our test, the panel offered Download all files, individual file downloads, and a downloadable ZIP that Kimi had created for the project.
A path such as /mnt/agents/output/focus-break-timer.zip in the assistant’s answer refers to its working environment. It is not a folder already present on your computer. Use the file panel’s actual download control to obtain the file.
Download your website files in six steps
- Create or open a website task. Describe the page, its behavior and the deliverable files. A small static project is easier to inspect than an application with accounts and a database.
- Wait for a completed version. Our task produced a Focus Break Timer V1 card, a README file and an All files card. Check the preview before exporting.
- Open All files. The file tree lets you select a file and inspect supported source formats. We opened the HTML and JavaScript source before relying on the generated description.
- Choose your download. Use Download all files for the available project files. If the assistant created a specific ZIP, select it and use Download. Individual files also had their own download controls in our session. Confirm that the file appears in your browser’s downloads before moving on.
- Extract the archive on your device. Keep related files together. For our plain HTML example, index.html references styles.css and app.js; moving only the HTML file will leave those references incomplete.
- Follow the project’s README. A static project can often open directly in a browser. A framework project may require dependencies, a build command and a server. Read its files instead of assuming every Kimi export uses the same setup.
The official Websites FAQ also points users to All Files for local downloads. The labels and file layout above are the ones observed in our session.
Our example: Focus Break Timer
We asked for a small English timer with editable work and break durations, Start, Pause and Reset buttons, and a break switch. The test used a paid account; it does not establish free-plan access. See the account settings and test limits.
Read the exact project prompt
Build a small English website called Focus Break Timer as a code-export demonstration. A single page: editable work minutes (default 25) and break minutes (default 5), Start, Pause and Reset buttons, a visible countdown, and a switch to start a break. Use plain HTML, CSS and JavaScript with no external dependencies, login, database, analytics or network requests. Include accessible labels and mobile layout. Deliver the complete downloadable project with index.html, styles.css, app.js and README.md, including local run instructions. Keep it in preview; do not publish it publicly.
Kimi packaged four project files in focus-break-timer.zip. Keep them together after extraction:
| File | What it does |
|---|---|
index.html | The page you open. It loads the stylesheet and JavaScript using relative paths. |
styles.css | The timer’s appearance and responsive layout. |
app.js | The countdown, buttons and work/break switching. |
README.md | The project description and local run instructions. |
When we selected the ZIP, the viewer said it could not preview that file type and offered a Download button. Clicking it produced a Downloaded notification. A ZIP does not have to be previewable in the browser to have a download control.
What we verified
| Check | Observed result |
|---|---|
| Completed deliverable | Version V1, four source filenames and a ZIP visible |
| Source access | HTML and JavaScript readable in the file viewer |
| Start and Pause | Countdown ran and then showed Paused |
| Reset | Loaded 01:00 after the work-minutes field was set to 1 |
| Break switch | Changed the timer to Break and 05:00 |
| ZIP download | Download action completed with a Downloaded notification |
| Independent local archive check | Completed: ZIP integrity checked, four expected files extracted, and the unmodified project opened on a separate local server |
| Local timer checks | Start, Pause, Reset and break switching worked; a one-minute break reached zero and displayed its completion message |
| Mobile layout | Checked at a 375px viewport without horizontal page overflow |
Try the exported timer on your computer
Download the original four timer source files (ZIP, 8 KB). This package contains the unchanged V1 source files, repackaged by ChinaAI on September 26 with provenance notes and hashes. It is not the original Kimi ZIP or the later V2 update.
- Extract the ZIP, then open the
focus-break-timerfolder. - Keep
index.html,styles.cssandapp.jstogether. The README offers openingindex.htmlin a browser; our recorded local test used a local web server. - To follow the server route, open a terminal in that folder. If Python 3 is installed, run:
Then open http://127.0.0.1:8000/ on that computer.python3 -m http.server 8000 --bind 127.0.0.1 - Try Start, Pause and Reset. To check a changed duration, set the minutes, press Reset and then Start. Switch to a break and check its displayed duration too.
If python3 is not recognized, the README’s direct-open route avoids needing a server for this dependency-free example. On Windows with the Python launcher installed, the equivalent command is py -3 -m http.server 8000 --bind 127.0.0.1. These commands adapt the README using Python’s documented bind option to keep the preview on your computer; they were not rerun for this revision. Stop the server with Ctrl+C when finished. This previews your files locally; publishing a public website is a separate step.
Test conditions and export record — 18 September 2026
The browser session showed Websites, K3 and High; the account displayed Moderato. We used its existing paid access without buying a new plan or API balance.
The All files panel also showed both a focus-break-timer folder and an app folder containing the four project filenames. That was this task’s output layout, not a universal Kimi folder convention. Selecting the packaged ZIP avoids guessing which loose files belong together.
We inspected the JavaScript’s timer logic: it calculated remaining time from timestamps, and its reset action read the configured duration. We did not complete a long-duration timing or background-tab reliability test.
The original downloaded ZIP passed an independent integrity check, and its four extracted files ran unchanged on a separate local server. The results table describes that one static project. They do not establish that every Kimi export, backend integration or hosting configuration will work. The export test was not repeated for this September 29 revision.
Your checks after downloading
- Confirm the archive contains the files named in the README.
- Open or run the extracted project using its documented instructions.
- Test its main controls, keyboard access and a narrow mobile layout.
- Look for missing assets, broken relative paths, placeholder data and required environment variables.
- For interactive sites, verify that data still saves after a reload and that any required backend is available.
What does not automatically move with exported code?
According to Kimi’s website export FAQ, platform-provided Kimi login and the managed cloud database do not migrate simply by downloading the code. A site that depends on those services needs an appropriate authentication and data setup on its new host.
That is why our first example avoided login, databases, analytics and external dependencies. It narrows the export check to source files and browser behavior. A full-stack application needs a separate deployment review.
Downloading and publishing are separate actions. During this export test, we kept the example in Kimi’s preview and did not use Publish. A private preview or a downloaded project is not the same as a public website.
Ready to share your website? In a follow-up test, we published this timer, updated its live version and took it offline again. Follow our tested Kimi website publishing guide for the steps and observed results.
Common questions
Can I export to GitHub directly?
We verified the file-download route. We did not test a GitHub integration. After downloading and reviewing your files, you can manage them in your own repository using your usual development workflow.
Does a paid Kimi subscription include API credit?
Do not assume that browser membership, Kimi Code access and public API billing are interchangeable. Use our Kimi pricing guide to distinguish the products, and the Kimi API guide for developer integration.
Is the CLI export command the same thing?
No. The Kimi Code command reference describes a session-export operation that can include conversation records and diagnostic logs. This guide concerns website project files from the consumer browser interface.
There is no download button where the answer says the ZIP is
Open All files instead of treating a printed server path as a download link. If the promised archive is absent, ask Kimi to package the completed project and expose it as a downloadable file. Check the actual file list again before assuming the export succeeded.
Evidence: our Kimi Websites session on 18 September 2026, visible source files, preview interactions, the downloaded ZIP and independent local checks of the extracted project. Official guidance checked 29 September 2026: Websites FAQ and feature overview. Testing methodology · Report a correction.