Kimi / Practical slides guide
How to create a presentation with Kimi Slides
To make a presentation with Kimi Slides, open the official Slides page and describe your audience, slide count, source facts and preferred design. Review the generated slides, correct anything that changes your meaning, then export the deck. Open the downloaded file in the app you will present from and check it again.
This guide covers the browser-based Slides service on kimi.ai. Our five-slide example passed all 13 source-content checks online and in the later PPTX download. The file contained native text objects, but we have not tested editing and saving it in desktop PowerPoint. See the original result and download checks.
By China AI Chat Team · Guide revised 27 September 2026 · First deck tested 23 September 2026 · Export and visual follow-up 25 September 2026 (UTC) · Our research and testing method
1. Create the deck from a clear brief
Start with a short brief that gives each slide a clear purpose. Kimi’s Slides user guide describes preset and custom styles as well as uploaded references. For a first deck, keep the design simple so you can concentrate on checking the content.
- Choose the presentation task. Start from the official Slides page. Decide who will see the deck and what they should be able to do after it. If you have a source document, use only material you are allowed to upload.
- Specify structure and constraints. Give the number of slides, the job of each slide, the audience, a simple visual direction and any facts that must survive unchanged. Say whether Kimi may browse for new information. For a fact-bound brief, explicitly prohibit invented names, figures and contact details.
- Send one request and wait for the result card. Our request opened a Kimi chat and returned an Edit and download card. The card opens the generated presentation for review.
- Open the card and inspect every slide. Read the actual text in the editor, not just Kimi’s completion message. Check whether the title, timing, numbers, exceptions and final call to action match your source.
Providing only a broad topic gives Kimi room to research and fill gaps. Its own guide says to provide rich source material and an explicit no-search instruction if you do not want supplemental information. For a company deck, medical presentation or financial proposal, verify every external claim and your right to use uploaded material before you present it.
A copyable brief pattern
Use this short pattern for your own content. Replace the bracketed material with facts you have checked:
Create [number] slides for [audience and purpose]. Use only the source facts below. Slide 1: [title and context]. Slides 2–[number]: [one job for each slide]. Use [brief visual direction]. Preserve every date, figure, condition and restriction exactly. Do not browse or invent missing names, statistics, links or contact details. If a required fact is absent, leave it out rather than guessing. Source facts: [verified facts].We used a longer exact version for the test below; it is available in the records section. A detailed brief can reduce ambiguity, but it does not remove the need to inspect the output.
2. Review the content and layout
- Compare against the source, not the prompt alone. Read each slide beside the approved document or notes. For dates, units, money and eligibility conditions, check the full phrase. For example, a registration deadline and a warning that walk-ins are not guaranteed a place are separate conditions. Keeping the date while dropping the warning changes what visitors are being told.
- Inspect the real slide canvas. Open every slide at a readable zoom or presentation size. Watch for clipped text, low contrast, tiny labels, image rights, unexpected icons and crowded tables. Check both the overall slide and its smaller labels; readable body text does not guarantee that every detail is legible.
- Fix small errors in the online editor. Kimi’s official guide describes adjusting text and layout in the editor and using follow-up instructions for larger changes. Make one specific correction at a time, then inspect the changed slide and any shared theme elements again. We did not perform a revision in this test.
- Save and check the final format separately. An editor preview is not proof that a locally exported deck will look or behave the same in PowerPoint, Keynote or LibreOffice. Reopen the actual file in the software you plan to use and check slide count, fonts, text editability, images and speaker notes where relevant.
For a deck based on private client or employee material, review Kimi’s privacy policy and your organisation’s upload rules first. Our test used fictional details only.
3. Export the deck and open the actual file
In our editor, Export opened a Download panel with Slides, Image and PDF choices and an Embed fonts switch. Kimi’s user guide documents local presentation export and says it can be edited online. The help overview calls its downloadable presentation an editable PPTX. Open your own exported file to check both its appearance and what you can edit.
- Open the result card and select Export.
- Choose Slides for a presentation file you intend to edit, or PDF/Image for a fixed copy. These were the labels in our tested editor. Review the font-embedding choice if the deck uses nonstandard fonts.
- Select Download, wait for completion, and locate the file in your browser’s downloads.
- Open the file locally. Confirm there are the expected slides and that the content you need to change is selectable as text. Check spacing and fonts in the app you will present from.
In our follow-up, the same five-slide project downloaded as a PPTX after earlier attempts produced no file. The successful attempt used Embed fonts off; this does not establish the cause of the earlier failures. The file checks below distinguish preserved text and layout from an untested desktop PowerPoint edit-and-save workflow.
If export or opening does not work
| What you see | Next action |
|---|---|
| “Export started”, but no file | Check your browser’s download list for a pending, failed or blocked item and its saved location. Try exporting the same project in an ordinary supported browser. Avoid generating the whole deck again just to retry a download. |
| Repeated failure with font embedding on | Try one export with Embed fonts off, then check fonts in the destination app. This was the setting of our successful attempt; it is not a confirmed diagnosis or guaranteed fix. |
| A file arrives but will not open | Confirm that you received a presentation file, not just an online project or preview. Record the error and check the file in software that supports PPTX; contact Kimi support if a fresh export still fails. |
| Text looks different or selects as one picture | Check the selected export format and inspect individual objects in your presentation app. PDF/image output serves a different purpose from editable text. Fix and recheck a copy before using it publicly. |
Before presenting, open the final file on the app and device you will use, and inspect every slide after font substitutions or edits. This small text-and-shape deck cannot predict every export.
Does Kimi Slides need a paid plan or an API key?
Our signed-in Moderato account completed this one browser request without an API key or a payment prompt. That does not establish free-plan availability or a fixed cost per deck. Kimi says its membership features, including Slides, share a credit pool and usage depends on the work performed; our request’s credit deduction was not visible. Check the live account balance and Kimi’s credit rules, or see our Kimi pricing guide. The Kimi API is a separate developer service, not required for this consumer workflow.
What our first Kimi Slides result contained
We sent one request using a wholly fictional Willow Bay Repair Café volunteer briefing. The prompt required exactly five English slides, a white/dark/green design, no web research and no invented contacts or sponsors. Before sending it, we wrote down 13 content checks covering slide count, the event facts and prohibited additions. Kimi returned an online project that opened in its Slides editor, showing 1 / 5 slides. We inspected the text exposed for all five slides. There was no second prompt or human correction.
| Slide | Requested job | Visible first result |
|---|---|---|
| 1 | Event, date, time and venue | Willow Bay Repair Café; 12 November 2026; 18:00–20:00; Community Room, Willow Bay Library. |
| 2 | Programme | Doors 18:00; safety briefing 18:20; stations 18:30–19:45; close 20:00. |
| 3 | Stations and volunteer cover | Textiles, bicycles and small electronics; 8 volunteers; no mains-powered appliance repairs. |
| 4 | Visitor capacity and registration | 40 visitors; free entry; registration closes 10 November 2026; walk-ins cannot be promised a place. |
| 5 | Visitor checklist | Main entrance ramp under repair; visitors needing step-free access should use the South Entrance; bring a reusable water bottle because drinking water is not provided. |
All 13 predeclared content checks matched the visible editor text in this single attempt, including the absence of a fabricated phone number, organiser, sponsor, website or extra policy. This was one deck built from supplied facts. The result does not measure general accuracy or research quality, and the original check did not verify an exported file. We subsequently checked the same deck’s downloaded file; see the 25 September follow-up. A deck can still have unreadable text, awkward hierarchy or broken fonts even when its extracted words are correct.
The online editor showed a white/dark/green design. On 25 September, we reopened the unchanged project and inspected all five slides in Chrome’s online presentation view. The main text was readable, with no observed clipping or overlap at the tested size. This does not establish readability from the back of a room or rendering in desktop PowerPoint. The complete visible slide transcript and frozen source are available for comparison.
What survived in the downloaded PPTX?
On 25 September, we downloaded the original five-slide project as a PPTX in Chrome with Embed fonts off, without regenerating or editing it. Earlier attempts had produced export notices but no matching local file. We could not establish why those attempts failed; turning font embedding off is not a guaranteed fix.
The downloaded file passed all 13 content checks and contained 50 native text objects. That supports structural editability, but we did not test a manual edit, save and reopen in desktop PowerPoint. The table separates the checks we completed from the work still untested.
| Check | What we verified | What it means for you |
|---|---|---|
| File and slide count | The received PPTX opened as a valid ZIP package with five slide parts; its archive integrity check found no bad member. | A completed export notice is not enough. Locate the actual file and check the expected slide count. |
| Facts and conditions | The same 13 source-content checks matched the exported slide text, including the registration deadline, walk-in caveat and South Entrance instruction. | Recheck the exported content against your source, especially exceptions and restrictions. |
| Text objects | The file contained 50 native text objects across five slides, rather than flattened slide pictures. | This supports structural editability. We did not perform a manual edit, save and reopen in desktop PowerPoint. |
| Fonts | Text declared Arial. No font files were embedded in the successful export. | If you export without embedding, check how your destination app handles the declared font. |
| Local visual preview | We rendered the downloaded file with OpenAI Artifact Tool and inspected all five slides at 1280 × 720. Main content was readable, with no observed clipping or overlap. | These are local rendered previews, not a Microsoft PowerPoint compatibility test. Placement differed slightly from Kimi’s online view. |
Download the original PPTX and follow-up evidence (ZIP) to inspect this fictional example yourself. The file is unmodified. The package also includes the file-inspection record, all five online screenshots and five separately labelled local previews. We did not test photos, complex charts, animations, or a desktop edit-and-save round trip.
Exact prompt, source facts and first-result record
Test conditions and export-attempt history
The first deck was generated on 23 September 2026 in the signed-in kimi.ai Slides page. The visible style was Freestyle, the model selector said K3 High and the account displayed Moderato. The exact underlying model version and request cost were not exposed. Preset and custom styles, uploaded references and subsequent editing are documented options; they were not tested here.
We sent one prompt. Generation included Kimi’s own internal steps, with no corrective message or regeneration from us. The editor displayed an Edit control, but we made no manual edit. The original in-app browser showed the deck at 12% zoom. On 25 September, we reopened the unchanged project for the online presentation and local-file checks.
25 September follow-up: we reopened the original five-slide project without regenerating or editing it. One export with Embed fonts on in the in-app browser and one in Chrome produced an export-started notice, but no matching local file was found at those checks. A further Chrome attempt with Embed fonts off delivered a 15,270-byte PPTX. This sequence does not prove that font embedding caused the earlier failures or that switching it off will fix every download.
The two failed in-app exports on September 23 remain in the record. The successful follow-up used the same deck, with no new generation.
The successful file contained no embedded fonts. Local previews were rendered with OpenAI Artifact Tool, not desktop PowerPoint. Photos, complex charts, animations and a desktop edit-and-save round trip remain untested.
The fictional brief, frozen checks, exact prompt, editor-text transcript and test-limit record are in our Kimi Slides test records (ZIP). That original 23 September package contains no PPTX. The separate 25 September export supplement contains the later downloaded file and its inspection record, preserving the earlier outcome. It contains no account credential or real person’s event data.
Read the exact prompt used in the one-request test
Create exactly five English slides for a volunteer briefing using only the fictional source notes below. The audience is volunteers who will welcome visitors. Keep the slides concise and readable. Use a clean white background, dark text and one restrained green accent. Do not browse the web or add images, statistics, contact details, sponsors or policies that are not in the notes. Preserve every date, time, number and condition exactly. Make the final slide a visitor checklist. Produce an editable presentation if that is available in this workflow.
Slide 1: event title, date, time and venue.
Slide 2: programme and exact times.
Slide 3: three repair stations, volunteer count and the no-mains-repair restriction.
Slide 4: visitor capacity, free entry, registration deadline and the walk-in condition.
Slide 5: step-free entrance and what visitors should bring.
Fictional source notes:
Willow Bay Repair Café volunteer briefing. Date and time: 12 November 2026, 18:00–20:00. Venue: Community Room, Willow Bay Library. Capacity: 40 visitors. Entry is free, but registration closes on 10 November 2026. Walk-ins cannot be promised a place. There are 8 volunteers. Stations: textiles, bicycles and small electronics. No mains-powered appliance repairs. Programme: doors open at 18:00; safety briefing at 18:20; stations operate from 18:30 to 19:45; close at 20:00. The main entrance ramp is under repair. Visitors needing step-free access should use the South Entrance. Visitors should bring a reusable water bottle; drinking water is not provided. No contact telephone number, named organiser, sponsor or website is provided.This record can help you prepare a clear brief and a checklist for your own presentation. It does not prove repeatability or measure Kimi against another product. For a general introduction to the assistant and its distinct tasks, see our Kimi overview. If you find a changed control or a reproducible error, contact China AI Chat Team; we will review a correction.
Sources: the Slides user guide, help overview and credit rules were rechecked on 27 September 2026. The product tests remain dated 23 and 25 September; this revision adds no new generation or export test. Kimi Slides user guide, Kimi Slides help overview, and Kimi credit rules. Our own observed outcome is documented separately in the records. Recheck this page if Kimi changes the Slides editor, export formats, account access or credit policy.