AI CompendiumA public chart of the language
Home / Training & Inference / Checkpoint
Training & Inference

Checkpoint

also called Weights snapshot, Model snapshot

A saved copy of a model’s weights at one point in training or post-training.

Definition

A complete saved copy of a model’s weights at a particular moment — after a training run, after a round of post-training, or after fine-tuning. The checkpoint is the thing you actually serve, download or evaluate: the architecture may stay the same while the weights change, so two checkpoints of the “same” model can behave differently.

The practical trap is the name. Vendors serve updated checkpoints under the same model alias, so the same alias in September and in October can be different weights with different benchmark scores, latency and output length. When you compare results over time — or reproduce someone else’s — the dated checkpoint matters more than the model name. Pin the checkpoint or the dated release when you can; when you cannot, record the date you ran the eval.

DeepSeek’s October 2026 refresh is the textbook case: V4.1-Flash-1017 shipped October 17 under the existing deepseek-flash alias, with vendor-reported gains — 77.0 on DeepSWE v1.1, up from 74.2 — and shorter outputs. The weights are MIT-licensed on Hugging Face, so self-hosters can pin the exact dated release; API callers get whatever the alias currently serves. The same pattern ran three months earlier, when the 0731 checkpoint superseded the V4-Flash preview with architecture unchanged and gains from re-post-training.

How people use it
Explaining why the same prompt got a different answer this month.
"The alias did not change, but the checkpoint did. Check the dated release before assuming the model regressed — or improved."
Worked example

The benchmark that moved

A team’s eval suite shows a sudden jump on a model they did not change.

Before celebrating — or filing a bug — check whether the provider refreshed the checkpoint behind the alias. If the vendor publishes dated releases, re-run the suite against the pinned old checkpoint to separate a real capability change from a serving change.

Avoid

Quoting a benchmark for a model name without the checkpoint date. The number may belong to weights nobody serves any more.

Sources
Related terms