We invented a community-event poster, so no client assets or personal data were involved. Before submitting, we fixed six checks: an actual downloadable image; square dimensions; exact STAR NIGHT and FRIDAY 7 PM text; one telescope aimed at a crescent moon; requested colours; and no people, extra words or logos.

Create one square editorial poster image for a fictional community event. The exact main headline must be “STAR NIGHT”; a smaller line must read “FRIDAY 7 PM”. Show a single tabletop telescope pointed toward a crescent moon. Use an aubergine background and warm pale-yellow illustration, with a clean, high-contrast layout. No people, extra words, brand logos or watermarks. Make it suitable for a small social post and provide a downloadable image.

For your task, replace the fictional subject and exact strings. Preserve measurable requirements, especially text and output shape.

Our first request on 23 September produced a 1080 × 1080 PNG with both requested text lines. This is the unchanged first download, saved before any follow-up edit. The test conditions record the session settings and limits.

We did not test photorealistic images, print production, or the editability and cross-app compatibility of the design source Kimi also offered.

After saving the first PNG, we sent one follow-up in the same chat: change only the aubergine background to warm ivory, keep the layout and both text lines, and export the edit separately. Kimi supplied another 1080 × 1080 PNG. The two text lines, telescope and crescent remained in approximately the same positions when we inspected the downloaded file. We did not make a pixel-by-pixel source comparison.

In the image you just made, change only the aubergine background to warm ivory. Keep the layout, telescope, crescent moon and both text lines unchanged. Export the edited image separately.

The edit exposed a problem in our revision brief: we asked Kimi to change only the background to ivory and preserve the other elements. The retained pale-yellow lettering then blended into that lighter background. This is a readability problem in the result, but not evidence that Kimi ignored the requested change. The new background conflicted with the original high-contrast goal. For a real poster, allow the text colour to change with the background, or keep a darker background. Compare the revision at the size your audience will see before using it. We did not send that extra request, so a repaired version is not a tested result.

1. Compare against your brief. Read every word letter by letter, count objects and check exclusions. Our first file passed the two exact-string checks; that does not guarantee other prompts will.
2. Inspect at the size people will see. Shrink the preview to social-feed or thumbnail size. Text can be present but unreadable, as our ivory edit shows.
3. Open the exported file. Check format, dimensions and version. We checked both separate 1080 × 1080 PNGs, not just Kimi’s chat descriptions.
4. Check unwanted marks and usage rights. Look for accidental marks or borrowed imagery, and review current service terms and rights in any reference material you upload. A clean export alone does not establish commercial-use rights.
5. Keep versions. Save the first output before revising. Change one thing at a time when you need to identify what an edit did.

For a slide deck or Word document rather than a standalone image, use our separate Kimi Slides and Kimi Docs guides. Each output type needs different checks.

The official Kimi image tutorial describes Design for prompts, previews, export and reference-based changes. Kimi’s chat help separately points users to + → Plugin for image, audio or video generation with K3. We tested the dedicated Design route, not that plugin path. The Kimi models guide explains model choices; our API guide covers developer access. Image understanding, image creation in a consumer tool and image-generation API support must not be treated as interchangeable.

Kimi’s chat help says K3 use is billed by credits; our Design session did not show a per-request credit or dollar amount for either image request. We cannot say this workflow is always free or assign an image price from this test. Access, credits and controls may change or vary by account. Check your own account before a large run; see our Kimi pricing guide for plan context. We did not make a developer API request, buy credits or enable automatic top-up.