Kimi Slides is no longer framed as a one-prompt shortcut
Kimi’s original pitch for Slides was familiar: give the product a topic, a paragraph, or a document and receive a structured presentation. Its current Slides materials still include that route. The visible change is what can now be carried into the deck with it.
Kimi’s Help Center now documents enhanced reference-image replication and custom-template support alongside the text and document flow. Its product page lists four starting points—text, documents, images, and templates—and says the resulting presentation can remain editable rather than ending as a flat visual. The current help material also records a more specific change: the former Visual mode has been discontinued, with generation now routed through Kimi’s K3 engine.
That turns a request from “make slides about this” into a more practical question: what part of the work should survive the trip into the deck?
| Earlier starting point | Current documented starting point | What is meant to carry forward |
|---|---|---|
| A topic or pasted text | Text to slides | The argument, sequence, and first-draft copy |
| A document to summarize | Documents to slides | Source material and its structure |
| A visual reference kept outside the tool | Images to slides | A reference layout, visual direction, or captured page |
| A separate company master | Templates to branded slides | The PowerPoint template’s layout, font, and grid system |
The distinction matters most when a team is not starting from a blank page. A weekly update may already exist as a Word file. A sales group may have a slide master that cannot be casually replaced. A designer may have one reference page whose hierarchy is worth retaining. In those cases, the useful input is not merely the subject of the presentation; it is the material that already carries decisions.
The change is about the handoff, not just the generation button
Kimi’s current help documentation describes Slides as part of a broader Office-output path: the agent can produce Word, PDF, Excel, and Slides files. Within Slides itself, the documented path now runs from supplied material to a generated deck, then to online editing or export.
That is a different workflow from using a chat answer as raw material for a presentation. A chat response still needs someone to decide what becomes a slide, choose a visual system, and place it into the file that will be reviewed. Kimi Slides is positioned to make that conversion inside the same product family, while keeping an editable presentation at the end of it.
The current documentation makes three points especially consequential:
- Kimi says it can build from PDF, Word, PowerPoint, Excel, text, and images, rather than only a written prompt.
- It describes reference-image restoration and uploaded PowerPoint templates as supported starting points, which gives existing visual material a route into generation.
- It says text, images, shapes, charts, and diagrams can be edited after generation, with presentation, PowerPoint, Google Slides, and PNG handoff options documented on the product page.
Those are product claims, not a promise that every imported file will arrive intact. A company should still check the exact master, fonts, page count, data, and approval requirements in the deck it receives. But the product boundary is clearer than it was when the task began with a sentence alone.
The K3 engine replaces an earlier mode split
Kimi’s earlier help material described an Adaptive route for research-led, structured delivery and a Visual route powered by Nano Banana Pro. The current troubleshooting guidance says the Visual mode has been discontinued in favour of the K3-powered engine. That is a product change, not a quality ranking between two choices.
For a user, the practical implication is simpler than the former mode names: the starting material now carries more of the decision. A written brief can supply the story; a document can supply the source; a reference image or template can supply the visual system. The K3 engine is the documented current generation path across those choices.
For an ordinary team, the useful result is not simply that AI makes a presentation. It is a cleaner decision about where to begin: text when the story is missing; a document when the source is already written; a reference or template when the visual system has already been chosen.
What has not changed
Kimi Slides remains a presentation generator, not a substitute for the person who owns the message. The current product materials describe editable output and several export routes, but they do not eliminate review of source accuracy, brand requirements, spacing, or the final presentation file.
The update is therefore modest but useful: Kimi Slides is becoming less like a one-off deck generator and more like a conversion layer between the materials a team already has and the editable presentation it needs next.
Discussion
0 replies