gpt-image-1.5 vs GPT Image 2
Which one, when — curated verdict, not a benchmark table
Input costs the same $5 per million on both and output is within a rounding error ($32 against $30), so price is not the reason to choose. gpt-image-2 widens the frame: arbitrary sizes with edges up to 3840x2160 in multiples of 16 at ratios up to 3:1, against a fixed 1024x1024 / 1536x1024 / 1024x1536 / auto set on gpt-image-1.5. Pick gpt-image-1.5 only if you want text back alongside the image — it lists text among its outputs where gpt-image-2 is image-out only; otherwise take the resolutions.
Pricing
| gpt-image-1.5 | GPT Image 2 | Δ | |
|---|---|---|---|
| Input / 1M tokens | $5 | $5 | = |
| Output / 1M tokens | $32 | $30 | 1.1× |
Rates from the live catalog at build time; each model page carries the current card.
Where they sit — output price per 1M tokens across all 8 image-generation models on this billing unit (log scale)
Specs
| gpt-image-1.5 | GPT Image 2 | |
|---|---|---|
| Input modalities | text image | text image |
| Output modalities | text image | image |
| Released | 2026-02-10 | 2026-04-21 |
| Output sizes |
|
|
| Input modes | text-to-image, image edit with mask inpainting | text-to-image, image edit with mask inpainting |
| Images per request | 10 | 10 |
| Formats | png, jpeg, webp | png, jpeg, webp |
| Notes | 1024x1024 / 1024x1536 / 1536x1024, quality low/medium/high edits endpoint supported better instruction following than gpt-image-1 | Flexible resolutions: edges up to 3840px in multiples of 16, ratio <=3:1, ~0.65-8.3MP total (incl. 4K 3840x2160) editing with mask inpainting all image inputs processed at high fidelity significantly improved text rendering (precise placement can still struggle) |
Specs are transcribed from each vendor’s documentation; a row a vendor does not publish is left out rather than inferred. Full sources: gpt-image-1.5 · GPT Image 2
One prompt, both models — measured through the gateway
One prompt, one request per model, no retries and no cherry-picking — the first result each model returned. Neither size nor duration was pinned: each model used its own default, because a request shaped to fit all of them would flatter none. Files here are re-encoded for the web, so judge composition and prompt adherence, not compression.
Switch between them with one line
Both ids are in every tab below — the highlighted pair of lines is the only edit. Same endpoint, same key, same request shape.
from openai import OpenAI
client = OpenAI(
base_url="https://synthorai.io/v1",
api_key="sk-syn-...",
)
resp = client.images.generate(
model="gpt-image-1.5",
# model="gpt-image-2", # uncomment this line, comment the one above
prompt="a watercolor lighthouse at dawn",
size="1024x1024",
)
print(resp.data[0].b64_json[:80])import OpenAI from "openai";
const client = new OpenAI({
baseURL: "https://synthorai.io/v1",
apiKey: "sk-syn-...",
});
const resp = await client.images.generate({
model: "gpt-image-1.5",
// model: "gpt-image-2", // uncomment this line, comment the one above
prompt: "a watercolor lighthouse at dawn",
size: "1024x1024",
});
console.log(resp.data?.[0]?.b64_json?.slice(0, 80));curl https://synthorai.io/v1/images/generations \
-H "Authorization: Bearer sk-syn-..." \
-H "Content-Type: application/json" \
-d '{
"model": "gpt-image-1.5",
# "model": "gpt-image-2", # uncomment this line, comment the one above
"prompt": "a watercolor lighthouse at dawn",
"size": "1024x1024"
}'package main
import (
"context"
"fmt"
"github.com/openai/openai-go/v3"
"github.com/openai/openai-go/v3/option"
)
func main() {
client := openai.NewClient(
option.WithBaseURL("https://synthorai.io/v1"),
option.WithAPIKey("sk-syn-..."),
)
resp, _ := client.Images.Generate(context.TODO(), openai.ImageGenerateParams{
Model: "gpt-image-1.5",
// Model: "gpt-image-2", // uncomment this line, comment the one above
Prompt: "a watercolor lighthouse at dawn",
Size: "1024x1024",
})
fmt.Println(resp.Data[0].B64JSON[:80])
}import com.openai.client.OpenAIClient;
import com.openai.client.okhttp.OpenAIOkHttpClient;
import com.openai.models.images.*;
OpenAIClient client = OpenAIOkHttpClient.builder()
.baseUrl("https://synthorai.io/v1")
.apiKey("sk-syn-...")
.build();
ImagesResponse resp = client.images().generate(
ImageGenerateParams.builder()
.model("gpt-image-1.5")
// .model("gpt-image-2") // uncomment this line, comment the one above
.prompt("a watercolor lighthouse at dawn")
.size("1024x1024")
.build());
System.out.println(resp.data().orElseThrow().get(0).b64Json().orElseThrow().substring(0, 80));FAQ
Which is cheaper, gpt-image-1.5 or GPT Image 2?
They list the same input / 1m tokens ($5), so price does not decide this one — see the specs and capabilities below.
Can I A/B test gpt-image-1.5 against GPT Image 2 without two integrations?
Yes. Both are served through the same OpenAI-compatible endpoint with one API key — switching is a one-line model-string change, so you can route a fraction of traffic to each and compare bills directly.
Does the price change with image size?
It depends on how the model bills. Per-image models charge the same regardless of prompt or output size; token-billed models scale with the resolution you render, so a 4K image costs a multiple of a small one. The table above shows which applies to each.