Model comparison · accepted catalogue facts 2026-11-22

R1 0528 vs DeepSeek V3.2

Neither model has both an equal-or-higher measured score and an equal-or-lower estimated price in this pair. Retaining your current model is a valid outcome.

Both models belong to the DeepSeek family. Inclusion does not recommend either model. This is a direct pair comparison; global frontier membership is not its verdict.

R1 0528

LMArena general · Elo · higher is better

Scale starts at 1040 Elo

1427.7

Balanced effective USD / 1M tokens · lower is better

$0.920/M

DeepSeek V3.2

LMArena general · Elo · higher is better

Scale starts at 1040 Elo

1424.6

Balanced effective USD / 1M tokens · lower is better

$0.394/M

In-Depth Analysis

R1 0528 vs DeepSeek V3.2: Measured Technical Breakdown

Comprehensive comparison across measured human-preference evaluation, effective production token costs, architectural limits, and migration trade-offs.

Measured Capability (LMArena)
R1 0528 leads by 3.1 Elo

R1 0528: 1427.7 ±5.65 · DeepSeek V3.2: 1424.6 ±3.47 Intervals overlap — not a guaranteed quality advantage

Cost Comparison Across Canonical Production Workloads

Rates represent effective cost per 1M tokens under standard token blends. Cached prompt reads are factored according to workload context reuse.

Workload & RatioR1 0528DeepSeek V3.2Cost DifferenceAdvantage
Balanced 3 tokens in per 1 out$0.920 /1M tokens$0.394 /1M tokens$0.526 (57% diff)DeepSeek V3.2 costs less
Summarise Huge input, tiny output$0.584 /1M tokens$0.252 /1M tokens$0.332 (57% diff)DeepSeek V3.2 costs less
Chat Long cached system prompt$1.17 /1M tokens$0.440 /1M tokens$0.732 (62% diff)DeepSeek V3.2 costs less
Code gen Output dominates$1.51 /1M tokens$0.574 /1M tokens$0.934 (62% diff)DeepSeek V3.2 costs less
Agentic Context replayed each turn$0.752 /1M tokens$0.269 /1M tokens$0.483 (64% diff)DeepSeek V3.2 costs less

Architectural & Operational Specifications

SpecificationR1 0528DeepSeek V3.2Operational Note
Context window163,840 tokens163,840 tokens—
Max output generation32,000 tokens147,456 tokensDeepSeek V3.2 allows longer single-turn completions
Base input price$0.500 / 1M tokens$0.259 / 1M tokensDeepSeek V3.2 input rate is cheaper
Base output price$2.18 / 1M tokens$0.800 / 1M tokensDeepSeek V3.2 output rate is cheaper
Cached input priceNot listed / standard rate$0.140 / 1M tokens—
Reasoning & thinking tokensSupported; standard ratesSupported; standard rates—
Input modalitiestexttext—
Tool calling / function useSupportedSupported—
Open weights & licenceProprietary (API-only)Open weights (mit)DeepSeek V3.2 allows independent hosting or local deployment
Provider & reseller marketDeepSeek · 3 provider offers (1.14× spread)DeepSeek · 4 provider offers (1.16× spread)—

When to Choose R1 0528

  • Higher measured general capability (1427.7 Elo on human evaluation).
  • Direct integration with DeepSeek tooling and API features.
Risks when moving from DeepSeek V3.2 → R1 0528:
  • Output limit: 147,456 → 32,000 tokens.

When to Choose DeepSeek V3.2

  • Higher maximum completion limit (147,456 tokens).
  • Open weights availability allows private self-hosting and on-premise execution.
  • Direct integration with DeepSeek tooling and API features.

Compare · model decision

Choose two or three models

Inspect the differences, estimate your workload and keep the evidence. All standard catalogue models are available, including unrated ones.

Catalogue facts
2026-11-22

2 / 3 selected · 0 requirements
Open public comparison link
Public workload and requirements

These settings are included in the share link. The fixed-request scenario and private evaluation data below are excluded.

A ↔ B

Neither model has both an equal-or-higher measured score and an equal-or-lower estimated price in this pair. Retaining your current model is a valid outcome.

Estimated blend: 75% input, 25% output; 0% cached input. Base context tier. Prompt length selects the billing tier. An unlisted cache-read rate uses that tier’s full input rate in this blend; missing required input or output rates prevent an estimate. The fixed-request estimate below validates actual context and output limits and requires a published cache-read rate when cache hits are assumed.

What changes between these models

Quality first, then estimated price. LMArena scores are human-preference measurements, not a benchmark of your application. A missing score is unrated.

  • R1 0528 · Meets the stated model requirements
  • DeepSeek V3.2 · Meets the stated model requirements
Material differences and unknown evidence. Deltas compare each model with model A. Unknown facts remain visible.
Measured factA R1 0528B DeepSeek V3.2
LMArena general score (Elo)1,427.71,424.6Δ vs A: -3.1 Elo
Score interval half-width (± Elo)5.653.47Δ vs A: -2.18 Elo
LMArena document score (Elo)UnknownUnknown
Estimated effective USD / 1M tokens$0.92$0.39425Δ vs A: -0.52575 USD/M
Base input USD / 1M tokens$0.5$0.259Δ vs A: -0.241 USD/M
Base output USD / 1M tokens$2.18$0.8Δ vs A: -1.38 USD/M
Base cached-input USD / 1M tokensUnknown$0.14
Output limit (tokens)32,000147,456Δ vs A: +115,456 tokens
Open weightsUnknownSupported
Recorded licenceUnknownmit
Distinct sellers in the catalogue34Δ vs A: +1
Recorded retirement dateUnknownUnknown
8 shared measured facts
Shared measured facts. Deltas compare each model with model A. Unknown facts remain visible.
Measured factA R1 0528B DeepSeek V3.2
Benchmark reasoning effortdefaultdefault
Context window (tokens)163,840163,840Δ vs A: 0 tokens
Input modalitiestexttext
Tool useSupportedSupportedΔ vs A: 0
ReasoningSupportedSupportedΔ vs A: 0
Model providerDeepSeekDeepSeek
Serving precision differs across offersSupportedSupportedΔ vs A: 0
Retirement evidenceNone announced; not a guaranteeNone announced; not a guarantee

Provider counts and precision flags describe catalogue offers. They do not establish the precision, availability, region, tool behaviour or limits of your chosen endpoint. Open each model’s provider table before switching.

Complete price ladders and billing conditions

R1 0528

Rates below are USD per 1M tokens. A threshold selects that whole input/output rate pair.

Input-token thresholdInputOutputCached input
Base, up to and including first threshold$0.5$2.18Unknown

DeepSeek V3.2

Rates below are USD per 1M tokens. A threshold selects that whole input/output rate pair.

Input-token thresholdInputOutputCached input
Base, up to and including first threshold$0.259$0.8$0.14
Migration preflight · compare each candidate with model A

Keeping R1 0528 is a valid decision. No pairwise comparison certifies a drop-in replacement.

R1 0528 → DeepSeek V3.2

No known model-capability loss

  • Provider endpoint, serving precision, availability and task success need your own verification. Catalogue model capabilities do not certify an endpoint.
Check alternatives to R1 0528

Estimate a fixed request shape

Private to this tab unless you save locally or explicitly export private details. These are estimates, not observed invoices. Cross-model token counts and task success are assumptions.

0.1 extra attempts means 10 extra full attempts per 100 requests. Cache writes, tool charges, taxes and unlisted charges are excluded.

  • R1 0528Estimated total: $2.09 1,000 full attempts · base rates
  • DeepSeek V3.2Estimated total: $0.918 1,000 full attempts · base rates
Prompt and output sensitivity · sampled scenarios

Every point recalculates the entire request shape. Tier-boundary samples include one token below, at and above each threshold. Ordering between samples is not guaranteed. Lowest known cost excludes unknown estimates and is not a replacement recommendation.

Vary input; hold output, requests, cache and retries fixed.
Input tokensR1 0528DeepSeek V3.2Coverage
2,000$2.09$0.918Lowest knownAll computed
4,096$3.138$1.460864Lowest knownAll computed
32,768$17.474$8.886912Lowest knownAll computed
131,072$66.626$34.347648Lowest knownAll computed
Vary output; hold input, requests, cache and retries fixed.
Output tokensR1 0528DeepSeek V3.2
128$1.27904$0.6204
2,048$5.46464$2.1564
8,192$18.85856$7.0716

Bring your observed evaluation results

JSON is parsed locally. Prompts, filenames, individual responses and extra fields are not retained. Import only aggregate measurements for selected models. Task/version labels do not establish that two evaluations used the same dataset.

Expected format
[{"model":"provider/exact-model-id","task":"support-answer","version":"rubric-1","attempts":100,"successes":84,"costUsd":2.4,"latencyMs":950}]

Use the exact catalogue ID. Replace the example values with observed measurements. Omit costUsd or latencyMs when they are unknown. No public score is inferred from these observations.

Keep the decision and its evidence

A portable record retains selected facts, complete tier ladders, public requirements and the publication manifest. It also embeds the full permitted public catalogue to verify the input artifact checksum. Files are larger for this reason (up to 2 MB); local storage is limited to 12 records. Team review is local to this browser; there is no hosted collaboration.

Saving is opt-in and includes private review fields. Shared comparison links never include them. Version 1 Check references remain separate and are not overwritten or guessed into this format.

Saved local decisions · 0

No version 2 decision records are stored in this browser.

Questions this page answers

Is R1 0528 a better-and-cheaper replacement for DeepSeek V3.2?

Neither model has both an equal-or-higher measured score and an equal-or-lower estimated price in this pair. Retaining your current model is a valid outcome.

Which model is higher rated: R1 0528 or DeepSeek V3.2?

R1 0528 scores higher on LMArena general (1427.7 ±5.7) compared to DeepSeek V3.2 (1424.6 ±3.5), a margin of 3.1 Elo points. However, because the 95% confidence intervals overlap, this does not establish an unconditional superiority across all tasks.

Which model is more cost-effective: R1 0528 or DeepSeek V3.2?

On a standard balanced workload (3 prompt tokens per 1 generated token), DeepSeek V3.2 costs $0.394 per 1M tokens versus $0.920 for R1 0528. R1 0528 is approximately 2.3× the price of DeepSeek V3.2. Base input rates are $0.500 for R1 0528 and $0.259 for DeepSeek V3.2; base output rates are $2.18 for R1 0528 and $0.800 for DeepSeek V3.2.

How do their context windows and generation limits compare?

Both R1 0528 and DeepSeek V3.2 provide an identical 163,840-token context window. Maximum output generation limits are 32,000 tokens for R1 0528 and 147,456 tokens for DeepSeek V3.2.

What capabilities are lost when switching between R1 0528 and DeepSeek V3.2?

Switching from R1 0528 to DeepSeek V3.2 causes no detected architectural capability loss. Conversely, moving from DeepSeek V3.2 to R1 0528 involves: Output limit: 147,456 → 32,000 tokens. Run test suites on your specific prompt templates and tool declarations before cutting over production traffic.

Can R1 0528 or DeepSeek V3.2 be self-hosted or deployed privately?

DeepSeek V3.2 provides open weights, enabling self-hosting on private GPU infrastructure, local quantization, and private data pipelines. Managed inference is also offered across third-party API providers (3 for R1 0528, 4 for DeepSeek V3.2).

What is included in this comparison?

Accepted model capabilities, context and output limits, complete price-tier ladders, independent LMArena measurements and missing evidence. Provider endpoint precision and application success still need verification.

Can I compare a different workload or keep a decision record?

Yes. Change the public workload, prompt length and requirements in the comparison workspace. Fixed-request scenarios, aggregate evaluations and review notes stay local unless explicitly exported.

Evidence & Ask