// head_to_head

GPT-5.2 vs GPT-5.3-Codex

Published LiveBench scores across all seven categories, live list pricing, context windows, and the measured cost of a point of capability — for both models, side by side.

OpenRouter + LiveBenchAll comparisonsFull leaderboard

GPT-5.2 and GPT-5.3-Codex are priced within ~10% of each other.

GPT-5.3-Codex does not have a published LiveBench run, so this comparison covers price, context and declared capabilities only. A missing score means "not evaluated", not "worse" — the right way to separate these two is an eval on your own workload.

openai

GPT-5.2

Blended / 1M
$4.81
Context
400K
Released
Dec 10, 2025
Overall score
74.6
reasoningtool callingfile inputimage inputprompt caching

openai

GPT-5.3-Codex

Blended / 1M
$4.81
Context
400K
Released
Feb 24, 2026
Overall score
Not evaluated
reasoningtool callingimage inputfile inputprompt caching

Specs and pricing

MetricGPT-5.2GPT-5.3-Codex
LiveBench overall

Mean of the seven LiveBench category scores, 0–100. Higher is better.

74.6
Cost per point

Measured benchmark spend divided by overall score — dollars per point of capability.

$0.1289
Blended price / 1M

3:1 input:output mix, the usual shape of production traffic.

$4.81$4.81
Input price / 1M$1.75$1.75
Output price / 1M$14.00$14.00
Cached input / 1M

Price of an input token served from the prompt cache, where the provider publishes one.

$0.175$0.175
Context window400K400K
Max output tokens128K128K

Benchmarks by category

An overall score averages away the thing you probably care about. These are the seven LiveBench categories scored separately — GPT-5.2 on top, GPT-5.3-Codex below, both out of 100.

Agentic coding
50.3
Coding
76.1
Reasoning
83.2
Mathematics
93.2
Data analysis
78.2
Language
79.8
Instruction following
61.8

What each one costs to run

Per-token prices are hard to feel. These are monthly list costs for both models across five workload shapes, using each provider's published cached-input rate where there is one.

WorkloadGPT-5.2GPT-5.3-Codex
Support chatbot

1.2K in / 400 out × 200K requests

$1,427/mo$1,427/mo
RAG assistant

8K in / 600 out × 100K requests

$1,610/mo$1,610/mo
Coding agent

40K in / 4K out × 20K requests

$1,638/mo$1,638/mo
Document extraction

20K in / 1.5K out × 50K requests

$2,721/mo$2,721/mo
Bulk classification

500 in / 20 out × 5M requests

$4,988/mo$4,988/mo
Run these two through the cost calculator

GPT-5.2 vs GPT-5.3-Codex FAQ

Which is better, GPT-5.2 or GPT-5.3-Codex?

GPT-5.2 and GPT-5.3-Codex are priced within ~10% of each other. GPT-5.3-Codex does not have a published LiveBench run, so this comparison covers price, context and declared capabilities only. A missing score means "not evaluated", not "worse" — the right way to separate these two is an eval on your own workload.

Is GPT-5.2 cheaper than GPT-5.3-Codex?

They cost about the same. Both land near $4.81 per million tokens on a 3:1 input:output blend, so price is unlikely to be the deciding factor between them.

Does GPT-5.2 or GPT-5.3-Codex have a bigger context window?

They are effectively the same — 400K for GPT-5.2 and 400K for GPT-5.3-Codex.

Do GPT-5.2 and GPT-5.3-Codex support prompt caching?

Both publish a cached-input rate: $0.175 per million for GPT-5.2 and $0.175 for GPT-5.3-Codex, against full input rates of $1.75 and $1.75. On a workload with a long stable prefix — a system prompt, a tool schema, a retrieved corpus — that changes the economics more than the headline price does.

Related comparisons

How these numbers are produced

  • Price — provider list price from OpenRouter, refreshed every 15 minutes. “Blended” is a 3:1 input:output mix.
  • ScoresLiveBench release 2026-06-25, using their own category map. Each model shows its strongest published run. A blank means “not evaluated”, never “bad”.
  • Cost per point — the measured dollars LiveBench spent on the run, divided by the score it earned.
  • “Win” — awarded only past a threshold: one full point on a benchmark score, 10% on a price, 25% on a context window. Anything tighter reports as a tie, because effort settings alone move a LiveBench score by more than that.

Published benchmarks rank models on someone else's tasks. Before committing, see LLM & agent evaluation for building an eval on your own.