Skip to content
ModelCap

Head-to-head comparison

R1 0528 vs DeepSeek V3.2

R1 0528 (DeepSeek) and DeepSeek V3.2 (DeepSeek) compared on the ModelCap Index, API price, context window, provider availability, weight access and every public benchmark board they share. Figures are the same ones shown on the live rankings; nothing here is a hidden score.

Snapshot as of 7 November 2026

As of 7 November 2026, DeepSeek V3.2 holds the stronger ModelCap Index position (#82 vs #86); and DeepSeek V3.2 is 5.7× cheaper per output token ($0.38/1M vs $2.15/1M).

Which should you choose?

Choose R1 0528 if…

  • ModelCap publishes no field on which R1 0528 leads DeepSeek V3.2 for this pair.

Choose DeepSeek V3.2 if…

  • you want the stronger overall ModelCap Index position — #82 against #86 (60.6 vs 59.7 points).
  • API cost matters — $0.38/1M output tokens against $2.15/1M, about 5.7× cheaper.
  • your workload is prompt-heavy — input tokens cost $0.26/1M against $0.50/1M.
  • you want provider choice — 7 listed API providers against 3.
  • Arena text is your yardstick — 1425 against 1421.
  • Arena coding is your yardstick — 1475 against 1464.
  • you want the more recently listed model — DeepSeek V3.2 was listed 1 December 2025, R1 0528 28 May 2025.

R1 0528 vs DeepSeek V3.2: specs, pricing and context

Specification comparison of R1 0528 and DeepSeek V3.2
FieldR1 0528DeepSeekDeepSeek V3.2DeepSeek
ModelCap Index position#86#82
Index score59.760.6
EvidenceMeasuredMeasured
Input price / 1M tokens$0.50$0.26
Output price / 1M tokens$2.15$0.38
Context window164K tokens164K tokens
Declared route output cap33K147K
API providers listed37
Weight accessOpen weightsOpen weights
Input modalitiesTextText
First listed28 May 20251 December 2025
PublisherDeepSeekDeepSeek

Evidence: 2 public benchmark observations across 2 boards · 3 public benchmark observations across 3 boards. Prices are the lowest listed API offer per million tokens observed on the OpenRouter catalogue.

Benchmark scores: R1 0528 vs DeepSeek V3.2

Public benchmark boards where R1 0528 or DeepSeek V3.2 has a published result
BoardR1 0528DeepSeek V3.2Leads
Arena textArena (LMArena)14211416–1427Not reported14251421–1428Not reportedDeepSeek V3.2
Arena codingArena (LMArena)14641453–147514751469–1482ThinkingDeepSeek V3.2
ARC-AGI-2ARC Prize Foundation—4.0%Only one result
SWE-benchSWE-bench (Princeton / SWE-agent team)—70.0%HighOnly one result
WildClawBench OpenClawWildClawBench—34.0Only one result

Scores are the sources' own published figures for each model's best evaluated configuration; ModelCap never re-runs a benchmark.

Want a different pairing? Open the interactive comparison tool to swap either model for any current ranked language model.

R1 0528 vs DeepSeek V3.2: common questions

Is R1 0528 better than DeepSeek V3.2?

DeepSeek V3.2 ranks higher on the ModelCap Index as of 7 November 2026: #82 against #86. That is a capability ranking built from public benchmark evidence with published uncertainty; whether it is "better" for you also depends on price, context and where you can run it. Their published uncertainty intervals overlap, so the rank difference alone does not establish a reliable capability advantage for your workload.

Is R1 0528 cheaper than DeepSeek V3.2?

DeepSeek V3.2 is cheaper on output tokens: $0.38/1M against $2.15/1M. Input tokens are $0.50/1M for R1 0528 and $0.26/1M for DeepSeek V3.2. Prices are the lowest listed API offer ModelCap observed, in USD per million tokens. For 1,000 requests with 2,000 input and 500 output tokens each (2M input + 0.5M output), the listed-rate estimate is $2.08 for R1 0528 versus $0.71 for DeepSeek V3.2. DeepSeek V3.2 costs 65.8% less in this scenario. This excludes caching, batch discounts, prompt-length tiers, tool charges and retries; verify the selected endpoint before budgeting.

Which has the bigger context window, R1 0528 or DeepSeek V3.2?

Both publish a 164K-token context window. OpenRouter catalogue or provider-endpoint declaration. Limits can vary by provider and prompt length; a model-wide maximum has not been independently verified.

Which is better for coding, R1 0528 or DeepSeek V3.2?

Arena coding: R1 0528 1464, DeepSeek V3.2 1475 — DeepSeek V3.2 leads.

Are R1 0528 and DeepSeek V3.2 open-weight models?

R1 0528: Open weights. DeepSeek V3.2: Open weights. Open weights mean the checkpoint can be downloaded and self-hosted under its licence. A missing weight link does not identify every API or chat product that offers a model.

Where can I run R1 0528 and DeepSeek V3.2?

ModelCap currently lists 3 API providers for R1 0528 and 7 for DeepSeek V3.2, from the OpenRouter catalogue snapshot the site serves; each model page lists the providers and their prices.

How current is this R1 0528 vs DeepSeek V3.2 comparison?

Every figure and ModelCap Index position comes from the same published snapshot dated 7 November 2026. Publication and page updates happen separately; use the snapshot date shown on the page.

Explore further