Source

Dhariwal and Nichol (2021), LIT-699 — ARXIV-2105.05233. The recommendation comes from that paper’s tables, not from the metric’s definition.

The metric’s own paper is not held here. Precision and recall for generative models are Kynkäänniemi et al.’s (2019) definitions — the fraction of samples falling in the data manifold, and the fraction of data falling in the sample manifold — and 1904.06991 was looked at in the 2026-09-23 metric-definition sweep and declined on the grounds that it was “not load-bearing on anything”. This practice is what makes it load-bearing, so that decline has expired and the paper is the next thing this line wants.

What to do

If your generator has a knob that trades fidelity for diversity — a guidance scale, a truncation level, a sampling temperature, a rejection threshold — then:

  1. Report precision and recall beside FID, at the knob value you are reporting.
  2. State the knob’s value. A number without it is unreproducible, because the knob moves FID more than most contributions do.
  3. Do not read a single FID as a fidelity claim. FID is a distance between distributions; it falls both when samples get better and when coverage gets better, and rises when either does at the other’s expense.

Why a single FID cannot answer the question

FID depends on fidelity and diversity together. On a knob that trades them, it is therefore non-monotonic: it improves while the cheaper of the two is still being bought and worsens once the trade starts costing more than it returns. The paper states this directly — “since FID and sFID depend on both diversity and fidelity, their best values are obtained at an intermediate point” — and the interior optimum is why a model tuned to its best FID is neither the highest-fidelity nor the most diverse version of itself.

The consequence is that two models can be ranked oppositely by FID and by precision, and that is not a pathological case. It is what the paper’s own headline comparison does, at all three resolutions it ran:

ImageNetmodelFID ↓Prec ↑Rec ↑
128BigGAN-deep6.020.860.35
128ADM-G2.970.780.59
256BigGAN-deep6.950.870.28
256ADM-G4.590.820.52
512BigGAN-deep8.430.880.29
512ADM-G7.720.870.42

A paper titled Diffusion Models Beat GANs on Image Synthesis reports, in its main table, that GANs have higher precision at every resolution it tested. The title is a claim about FID and coverage. Both readings are defensible and the three columns are what tells them apart; the one column does not.

Conditions

The knob has to exist for this to bite. Comparing two models with no fidelity/diversity control is the ordinary case, and there FID’s error bar and sample count matter more — SOTA-307 for the seed variance, SOTA-383 for the sample count.

Precision and recall do not escape the feature space, and they are not computed in FID’s. Two separate facts, and v1 of this practice collapsed them into a false one. The metric’s features are VGG-16 activations after the second fully connected layer (LIT-703); FID’s are Inception-v3. So it is a different ImageNet classifier, not the same one — and it is still not a second opinion on FID’s feature space, because that paper’s Figure 3c finds Inception-v3 features give “substantially similar” results. Two ImageNet classifiers agreeing is what SOTA-337 exists to warn about. This practice answers “which side of the trade”; SOTA-337 answers “is the measurement trustworthy”, and it covers all three metrics.

Fix k and the sample count, and do not compare across them. k = 3 and 50 000 samples are the conventional defaults, and k is not innocuous: higher values raise both precision and recall “in a fairly consistent fashion” until they saturate at 1.0 and 0.0. A precision of 0.86 at one k against 0.82 at another is not a comparison, for the same reason two FIDs at different guidance weights are not one.

Two metrics make model selection multi-objective, so “the best checkpoint” stops being defined. With FID alone you take the best snapshot. With precision and recall, snapshots of one run span a range of tradeoffs, so LIT-703 reports the Pareto frontier — the minimal subset guaranteed to contain the optimum for whatever tradeoff you turn out to want — rather than assuming one. Do that instead of picking a snapshot by either column. This is where the practice costs something real, and it interacts with SOTA-307: that practice asks for an error bar over seeds, and a frontier over two objectives is what an error bar becomes when there are two of them.

Low on both is a third outcome, not a middle. Appendix G lowers the sampling temperature two different ways and gets low precision and low recall together, with blurry samples — a knob that is not on the trade curve at all. Two columns detect that; FID alone reports it as a worse model without saying why.

Upsampling is the counter-example that makes the practice useful. It raises precision at roughly constant recall (0.69→0.72 and 0.73→0.75 at 256 and 512), which guidance cannot do at any scale. A single FID cannot distinguish “moved along the trade” from “moved off it”; that distinction is the reason the paper combines the two techniques rather than choosing between them.

Relation to what the record already says

  • SOTA-307 — FID’s variance across seeds. This practice is about what FID measures, not how noisy it is.
  • SOTA-383 — fix the sample count before comparing. Orthogonal and both apply.
  • SOTA-337 — when an ImageNet network is in the loop, confirm in another feature space. That is about FID’s bias; this is about its composition.
  • THEORY-095 — no unbiased estimator of FID exists. Also about the estimator, not the quantity.
  • SOTA-424 — choose the guidance weight by which metric you are willing to lose. That practice names FID and IS because its source’s sweep reports those two; precision and recall are the pair that name the trade’s two ends directly, and this is where they come from.