To publish a website from Kimi, open the website preview, select Publish, complete publication, and copy the public link. Then open that address outside the editor to check the result. Kimi’s Build documentation confirms that a generated preview becomes publicly accessible after publishing.
The desktop web steps below start with a website you have already created. Keep the original project available: you will need it when you want to change the site or take it offline.
Find the website you want to publish
Check what you have open before looking for a publishing control.
| What you have | Your next step |
|---|---|
| Your website preview inside its original project | Review the intended version, then follow the publishing steps below. |
| A shared conversation | Find the original project you can edit. Someone else’s shared chat does not establish publishing access. |
| A standalone website address | Check whether it is already public. Return to the original project to manage it. |
| Downloaded code or a ZIP file | Use the original Kimi project to publish there, or prepare the files for compatible external hosting. |
Publish your website from Kimi
Check access and hosting costs first
Use the account that manages the project and check its publishing allowance before proceeding. Free chat access does not establish free website hosting.
Kimi’s English-language membership pricing guide currently describes China plans and identifies a separate cloud-service credit charge for published Agent websites. On the web, open your avatar, then Settings → Subscription, to inspect credits and recent usage. Check the publishing conditions for your account, and distinguish building and editing from ongoing hosting. The China plan table does not establish international pricing.
Also remove private test content, correct placeholder contact details, and make sure the main button does what its label promises. Publishing makes the chosen content available to visitors.
Complete the publishing flow
- Open your project. Sign in through Kimi Build, reopen the original conversation, and open the website preview.
- Choose the intended version. Read its content and check the layout before making it public.
- Select Publish. If your website panel exposes publishing through Share, open that panel and complete publication there.
- Wait for completion. Look for the published status, then use Copy Link or Open Website to get the public address.
The controls above follow Kimi’s website-panel documentation. Copy the address supplied by that panel; the browser’s address bar may still point to your conversation.
Check what visitors actually see
Open the copied website URL in a private window or another browser. This separates the visitor experience from your signed-in editing session.
- Check the content. Look for a distinctive heading or sentence from the version you intended to publish.
- Open important pages directly. Follow the navigation, copy a subpage address, and reload it in a new tab.
- Check a narrow screen. Read the text, open the menu, and confirm that buttons remain usable without horizontal scrolling.
- Try the main action. For a contact form, send a harmless test and check whether it reaches its destination. A success message alone is insufficient evidence.
- Check expected access. A public landing page should open as intended. A member area may require application login; distinguish that from being sent back to Kimi’s editor.
Kimi Build supports projects with databases and authentication. For those projects, verify the behavior you depend on: sign out and back in, revisit a saved test record, and confirm that another permitted user sees the correct information. Use test data you can safely remove afterward.
Update the published website
Make your changes in the original project. Review the new preview, then open Share and select Update when available. Recheck the public page afterward.
For a simple verification, change one visible sentence and look for it at the public address. If it appears only in the preview, check the publication controls before assuming the live site has updated.
After updating, check both the address shown in the publishing panel and any link you previously shared. This catches a version or address mismatch before visitors encounter it.
Change the address or use your own domain
Kimi documents a Custom URL option for changing the subdomain in an address such as yourname.ok.kimi.link. This is different from connecting a domain you own, such as example.com.
The documented custom-URL feature does not establish an owned-domain connection workflow. If an owned domain is essential, prepare the exported project for a host that supports it, as described below.
Take the site offline
Open Share, use the three-dot menu, and select Unpublish. Kimi’s publishing guide says the code and data remain in the project.
Recheck the former public address. The membership guide also identifies unpublishing as the action that stops the documented website cloud-service charge.
Publish exported Kimi files on another host
External hosting is useful when you need control of the hosting account or an owned domain. In Kimi, open All Files and download the project. Inspect what the download contains before choosing an upload method.
| Project type | What to prepare |
|---|---|
| Finished static files | The entry HTML page and all referenced stylesheets, scripts, images, and other assets. |
| A frontend project with a build process | Follow its setup instructions and identify the actual build output. A source folder is not automatically the folder to publish. |
| An application with a server, login, or database | Identify the required runtime, configuration, authentication, and data storage before selecting hosting. |
According to Kimi’s export FAQ, exported code does not carry Kimi account authentication or platform-managed database records to another host. Those dependencies need separate setup and data migration. Downloading the files does not complete that work.
Example: upload a finished static site to Cloudflare Pages
Use this route for a static site whose finished files are ready to serve. Complete any required build first. Check that the deployment root contains an index.html entry page and the referenced asset folders, rather than an extra enclosing project folder.
- Sign in to Cloudflare and open Workers & Pages.
- Select Create application → Get started → Drag and drop your files.
- Name the project and upload the finished site folder or ZIP. For a compiled frontend, use the actual build output.
- Complete the deployment using the displayed Deploy site or Save and Deploy action.
- Open the supplied
pages.devaddress and repeat the visitor checks above.
Cloudflare’s Direct Upload documentation covers this route. Dashboard drag-and-drop does not compile a Pages Functions folder, and a Direct Upload project cannot later be switched to Git integration. Choose a different deployment setup if either capability is required.
To publish a later revision, use Create a new deployment in that project and select the production environment. Editing the original Kimi project alone does not update a separately uploaded copy.
For an owned domain, open the Pages project’s Custom domains → Set up a domain flow. Follow Cloudflare’s custom-domain instructions: the requirements differ for a root domain and a subdomain. Complete the project setup before changing DNS, and verify the working domain afterward.
Fix a missing preview or failed publication
Keep the project, version, and affected URL together while diagnosing a problem. Start with the symptom you can reproduce.
| Symptom | What to check next |
|---|---|
| No Publish control | Confirm that you are in your editable website project and check the website panel’s Share controls. |
| No usable preview | Reopen the conversation. Kimi’s FAQ also identifies an incorrect internal project directory as a possible cause. |
| Publish fails | Keep the saved version, retry later, and send persistent failures through User Feedback with the version number. |
| The page is blank or interactions fail | Tell Kimi which URL and action fail. Ask it to inspect runtime errors, dependencies, and missing assets, then save a corrected version. |
| The public URL shows old content or a 404 | Compare it with the current publishing panel, check the published version, and confirm that the site has not been unpublished. |
For a missing preview, Kimi’s troubleshooting FAQ specifies /mnt/agents/output/app as the internal project location. You can ask:
“Check whether this website is saved in the project location required by Kimi Build. Preserve the existing files and data, correct the location if necessary, and save a version I can preview. Do not publish it yet.”
That location belongs to Kimi’s working environment. You do not need to create it on your computer. For a persistent issue, include the affected link, version, browser, and exact error in your feedback.
Questions after publication
Does the published Kimi link expire?
Kimi’s FAQ describes no scheduled expiry for a published link, unless the site is unpublished or its content is flagged. Continue to check the hosting conditions for your account; link validity does not establish free ongoing service.
Will publishing make the website appear in Google?
Publishing makes the site available online. Google still needs to discover and process its pages. Provide useful content, descriptive page titles, and working links, and keep intended public pages accessible. Google Search Essentials explains that meeting its requirements does not ensure that a page will be crawled, indexed, or served in search results.
Last checked: October 12, 2026.