Grok Imagine added 21:9 and 5:2 to its image API
xAI's August 28 developer entry says that image generation and editing accept 21:9 for cinematic widescreen and 5:2 for wide banners. Both are explicit aspect_ratio values. The same entry added auto quality for grok-imagine-image-2.0 and raised the API's source-image limit for edits from three to five. With quality omitted, the entry says auto currently serves low for generation and medium for editing. August 28 developer notes · Image generation guide · Prompting guide for generation and edits
The August 7 announcement introduced Imagine Image 2.0 as Quality Mode on Grok web, iOS and Android, alongside API availability. The launch page illustrates nine framing options, through 2:1. The subsequent developer entry establishes the two extra API values. xAI's migration guide lists both among the capabilities 2.0 adds over the legacy grok-imagine-image-quality slug. The November 2 redirect to 2.0 low was a later API change. August 7 model announcement · API migration guide
Measured generation and editing
| Requested ratio | 1k output | 2k output |
|---|---|---|
21:9 | 1568×672 | 3136×1344 |
5:2 | 1600×640 | 3200×1280 |
- Generation, October 9. ArgoLink sent one text-to-image request per ratio and tier using
grok-imagine-image-2.0on its own generations endpoint. The same landscape prompt was used across the matrix. The four target combinations returned the dimensions above. The article publishes dimensions and methodology. Target image bytes and request receipts are unavailable. ArgoLink output table and methods - Editing, September 15. YM2API's Chinese operator guide dates the results to September 15. The English guide carries a September 17 update date. The operator used the same single reference with
grok-imagine-image-2.0,quality=mediumandn=1on its own edits endpoint. It reports the same dimensions, with JPEG at 1k and PNG at 2k. The guide supplies dimensions, encoding and setup. The exact reference dimensions and raw wide edits are unavailable. Original guide, section 6 · English guide, section 3
The two reports demonstrate the measured frame shape on the operators' gateways. They leave direct xAI response files, visual preservation across edits and outcomes for finished banners or cinematic stills unverified.
Release-period discussion
The August 21–September 11 public search found no Reddit submission showing an API run with either new ratio. On August 26, Taranaga reported consumer image sizes and compared them with a separate 3:2 API size. On September 7, an OpenClaw issue identified both new ratios as missing from the integration's image metadata. It cites xAI's API notes for expected support and supplies no completed wide-ratio run. Reddit discussion · OpenClaw issue