grok-imagine-image-quality retirement on November 2, Explained Simply
What grok-imagine-image-quality retirement on November 2 is, what it does well, and what it costs — released 2026-09-01 by xAI.
- The replacement will use a "low" quality setting, but it will actually cost you less per image.
Want a heads-up when Grok updates?
We email you the moment a new Grok version drops — plus plain-English release notes like these. No spam.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
If you're a developer who uses xAI's tools to generate images, this update matters to you. xAI is phasing out an older image-generation model and automatically shifting its users to a newer, cheaper setup. You won't have to rewrite your code to make this switch, but the quality of your generated images will change.
What it does well
This automatic switch is designed to make the transition easier for developers. It keeps the exact same request and response shape (meaning the way your code sends prompts and receives image data stays the same), so your apps won't break. It also lowers the cost for every image you generate.
How it compares
Compared to the retired model, the new model serving the requests (grok-imagine-image-2.0) will run on a "low" quality setting instead of the higher quality you used to get. However, xAI's original grok-imagine-image (1.0) is completely unaffected by this change and will continue to work exactly as it did before.
What it costs and what it can handle
The main detail to know is that the per-image price will be lower. The replacement model will be set to a "low" quality level.
Worth knowing
The biggest catch is the drop in visual quality. Because the replacement model will be locked to a "low" quality setting, your generated images might not look as sharp or detailed as they did before. If you aren't happy with the low quality, you might need to check out the migration guide to update your code and use a different setup.
This is our plain-language summary. Read the complete, official notes on the Grok official changelog ↗.
