Box-Cox Transformations: Model First, Transformation Second

The Box-Cox transformation is often used as a preprocessing ritual:

1. inspect a skewed response;
2. choose a transformation;
3. make the histogram look more normal;
4. run the original analysis.

That sequence misses the point of the method.

Box and Cox introduced a family of transformed regression models and a likelihood-based way to compare them.

The transformation is part of the model.

It changes the scale on which the conditional mean is specified and therefore changes the interpretation of coefficients and hypotheses.

The Box-Cox family

For a positive response $y>0$, a common Box-Cox transformation is

The limit as $\lambda\to0$ is

Special cases include approximately:

The original method includes scaling conventions so likelihoods for different $\lambda$ values are comparable.

That detail matters.

What model is being assumed?

The classical Box-Cox regression assumes that, for some transformation parameter $\lambda$,

with

under the model.

So the target is not

find a transformation that makes $Y$ normal.

The target is closer to

find a response scale on which the conditional mean is adequately modeled by the chosen linear predictor and the residual variance is approximately homogeneous and Gaussian enough for the intended likelihood analysis.

The residual structure is the object of interest.

Raw-response normality is usually irrelevant

Suppose

The marginal distribution of $Y$ can be strongly skewed even if

has well-behaved Gaussian errors.

Testing the raw outcome for normality before fitting the regression answers the wrong question.

Conditional modeling matters.

Positivity is not optional

The standard Box-Cox family requires

A common workaround is to add a constant:

That is not innocuous.

Different choices of $c$ can produce different fitted transformations, especially when values are close to zero.

If zero or negative values are scientifically meaningful, a shifted Box-Cox transformation should be justified explicitly or another model family should be used.

A transformation should not erase the meaning of zero.

Choosing lambda by likelihood

For each candidate $\lambda$, fit the transformed model and compute the corresponding profile likelihood.

Then choose

A likelihood interval for $\lambda$ is often more informative than the single optimum.

If values near

and

fit almost equally well, reporting three decimal places for $\hat\lambda$ is false precision.

Interpretability can justify choosing a nearby simple value such as 0, 1/2, or 1 when the likelihood supports it.

The Jacobian matters

A transformation changes the density scale.

If

then

Likelihood comparison across transformation parameters must include this change-of-variable term, or use an equivalent scaled formulation.

Simply fitting ordinary least squares after many arbitrary transforms and comparing residual sums of squares can give the wrong comparison.

Transformations change hypotheses

Suppose the original scientific question concerns the arithmetic mean difference

After a log transformation, a linear model targets

on the transformed scale.

A coefficient difference there is naturally multiplicative after exponentiation.

For a simple log-linear model,

the quantity

is associated with a ratio on a geometric-mean or median-like scale under the model, not automatically a ratio of arithmetic means.

The scientific estimand has changed.

Back-transformation is not as simple as exponentiating the fitted mean

If

then

In general,

Under a homoskedastic Gaussian log model,

we have

That extra term is retransformation bias correction.

For other transformations or heteroskedastic errors, the correction is more complicated.

Outliers are not a reason to transform automatically

A monotone transformation can reduce the numerical leverage of large observations.

That does not tell us whether those observations are errors, valid extremes, or evidence that the model is wrong.

The sequence should be:

1. verify the observation;
2. understand the mechanism;
3. assess influence;
4. choose a model appropriate to the data-generating process.

Transformation is not data cleaning.

Variance stabilization

Box-Cox can be useful when variance scales systematically with the mean.

Suppose approximately

A power transformation can sometimes make residual variability more nearly constant.

But if the mean-variance relationship has a known stochastic origin, a generalized linear model may be more natural.

For counts, for example, a Poisson or negative-binomial model uses the count distribution directly rather than trying to make counts Gaussian.

GLMs are not merely “methods for non-normal residuals”

A generalized linear model specifies:

1. a response distribution from the exponential family;
2. a mean $\mu_i$;
3. a link function

The link transforms the mean, not the observed response.

That is conceptually different from transforming $Y$ and fitting Gaussian least squares.

Choosing between Box-Cox and a GLM is therefore a modeling decision, not two interchangeable normalization tricks.

Comparing transformed models

Prediction error on the transformed scale is not directly comparable with prediction error on the original scale.

If the operational loss is measured in euros, kilograms, or minutes, validation should return predictions to that scale and evaluate the relevant loss there.

Likewise, $R^2$ values from different response transformations do not answer the same variance-explained question.

Model comparison must match the scientific and operational scale.

A reproducible example

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
from __future__ import annotations

import numpy as np
from scipy import stats

rng = np.random.default_rng(2026)

x: np.ndarray = rng.uniform(
    0.0,
    2.0,
    size=500,
)

noise: np.ndarray = rng.normal(
    loc=0.0,
    scale=0.35,
    size=x.size,
)

y: np.ndarray = np.exp(
    1.0 + 0.8 * x + noise
)

transformed, lambda_hat = stats.boxcox(y)

print(f"lambda = {lambda_hat:.3f}")
print(
    "corr(log(y), x) =",
    np.corrcoef(
        np.log(y),
        x,
    )[0, 1],
)

Because the data-generating process is log-linear, the estimated Box-Cox parameter should typically be near zero.

The example works because we know the generating mechanism.

With real data, diagnostics and subject-matter interpretation remain necessary.

Conclusion

Box-Cox is not a test for whether data are normal.

It is a family of transformed statistical models.

The sequence should be

A transformation is justified only if the transformed model answers a question we actually want answered.

References

• Box, G. E. P., & Cox, D. R. (1964). An analysis of transformations. Journal of the Royal Statistical Society: Series B, 26(2), 211–243. https://doi.org/10.1111/j.2517-6161.1964.tb00553.x
• McCullagh, P., & Nelder, J. A. (1989). Generalized Linear Models (2nd ed.). Chapman & Hall.
• Carroll, R. J., & Ruppert, D. (1988). Transformation and Weighting in Regression. Chapman & Hall.