GPT Image output_compression: OpenAI has it, Sume returns 400
OpenAI lets jpeg and webp take output_compression 0-100. Sume's docs say it is not served in v1 and sending it returns 400 unsupported_parameter.

On OpenAI's API, output_compression takes 0-100 for jpeg and webp output. On Sume it is in the schema but "not served in v1": sending it returns 400 unsupported_parameter. Choose output_format (png, jpeg, webp or svg) and compress the file on your side if you need a smaller size.
OpenAI's behavior is from its image generation guide; Sume's from the Image API docs and the generation code, read 2026-09-30.
What does OpenAI say about output_compression?
The guide says that with jpeg or webp you can specify output_compression to control the compression level (0-100%), and gives output_compression=50 as the example.
What does Sume do with it?
The docs list output_compression and seed as schema fields that no model advertises yet. The code rejects them with the message "No image model advertises this parameter in v1."
| Parameter | OpenAI guide | Sume docs |
|---|---|---|
| output_format | png, jpeg, webp | png, jpeg, webp, or svg |
| output_compression | 0-100 for jpeg and webp | Not served in v1; 400 unsupported_parameter |
| seed | Not covered here | Not served in v1 |
How do I still get a smaller image?
Request output_format: "webp" or "jpeg", then recompress after download with your own tooling. The format options are covered in PNG, JPEG or WebP output.
Will this change?
The wording is "in v1" and "no model advertises them yet", so the answer lives in the model's supported_parameters from GET /v1/images/models. If a model starts listing output_compression, that descriptor is the signal; do not rely on this post for later dates.
Sources
Related posts
More in Developers
- Rotating a webhook secret during a gradual deployment
Sume signs with both the new and old secret for 24 hours after rotation, so two receiver versions can run side by side. Upgrade the verifier first, then rotate.
- Grok Imagine first and last frame: keyframes on xAI only
xAI takes up to 4 timestamped keyframes for Grok Imagine video. Sume's grok-imagine-video-1.5 row takes one start image and rejects an end frame.
- Grok Imagine: how many images per request, xAI vs Sume
xAI's image API takes n from 1 to 10 per request. Sume's catalog code gives Grok a maximum of 1, so send one image per call and loop for more.
- Grok Imagine video length: 1-15 s on xAI, 4-15 s on Sume
xAI allows 1 to 15 seconds for grok-imagine-video-1.5. Sume's catalog row allows 4 to 15, so a 2-second clip needs another id such as wan-3.0.
Written by Sume