A z-score tells you how many standard deviations a value sits above or below the mean.

Subtract the mean from your value, then divide by the standard deviation. A z of 0 means the value is exactly average. A z of +2 means it is two standard deviations above the mean, which puts it around the 98th percentile. Negative z-scores sit below the mean. Because the result has no units, z-scores let you compare measurements taken on completely different scales, such as a test score against a height.

Rule of thumb: about 68% of values fall within z = ±1, 95% within ±2 and 99.7% within ±3. A |z| above 3 is conventionally treated as an outlier.

A z-score, also called a standard score, rewrites a measurement in terms of standard deviations from the mean. It answers a question the raw number cannot: is this value ordinary or unusual, given how spread out the data are? A height of 190 cm means nothing on its own. Told that adult male height averages 175 cm with a standard deviation of 7 cm, that becomes a z of +2.14, and now you know it sits above roughly 98% of men.

What this calculator reports:

• Z-score, the standard score itself, for a single value or for every value in a dataset.
• P-value, one-tailed and two-tailed, the probability of a value this extreme or more.
• Percentile rank, the percentage of a normal distribution falling below your value.
• Modified z-score, built from the median and MAD, which outliers cannot distort.
• Outlier flags at |z| > 3 and modified |z| > 3.5, the Iglewicz and Hoaglin threshold.
• Reverse lookup, giving the raw value that corresponds to any z or percentile you name.
• Z for a sample mean, using the standard error rather than the standard deviation.

A worked one-liner: a student scores 85 on a test where the class averaged 70 with a standard deviation of 10. Their z-score is (85 − 70) ÷ 10 = 1.5, placing them at about the 93rd percentile.

Who uses them: educators convert raw test marks to standard scores so results from different exams can be compared. Clinicians use z-scores for growth charts, bone density (the T-score is a z-score against a young-adult reference) and lab results. Finance uses them in the Altman Z-score for bankruptcy risk. Quality control flags parts beyond ±3 standard deviations. Machine learning standardises features to z-scores so that variables on different scales contribute equally.

4.1 Reading the z-score itself

The sign tells you the direction and the magnitude tells you the distance. A z of +1.5 means the value sits one and a half standard deviations above the mean; a z of −0.4 means it sits slightly below. Zero means exactly average. That is the entire interpretation, and it holds regardless of what you measured or what units you used.

The magnitude is what makes z-scores useful. Because the standard deviation sets the scale, a z of 2 means the same thing whether you are measuring reaction times in milliseconds or annual rainfall in millimetres: the value is unusually high for that particular distribution. This is what allows a student to compare their performance on a maths exam against their performance on an essay, even though the two marking schemes share nothing.

4.2 What the percentile actually claims

The percentile converts your z-score into a statement about position: the percentage of the distribution falling below your value. A z of 1.5 corresponds to roughly the 93rd percentile, meaning about 93% of a normal distribution lies below it.

That word normal is doing a great deal of work. The z-score itself is a pure arithmetic operation that requires no assumptions at all. The moment you convert it to a percentile or a p-value, you are assuming the data follow a normal distribution, because you are reading off the normal curve. If your data are skewed, the z-score remains a correct statement about standard deviations, but the percentile attached to it can be badly wrong. For income data, a z of 2 might correspond to the 95th percentile in reality rather than the 97.7th the normal curve predicts.

4.3 The p-value, and choosing a tail

The p-value is the probability of observing a value at least this extreme if the data really are normal with the mean and standard deviation you supplied. A two-tailed p-value counts both extremes: it answers "how likely is a value this far from the mean in either direction". A one-tailed p-value counts only one side.

Choose the tail before you see the data, not after. If your question is genuinely directional, such as "is this batch heavier than specification", a right-tailed test is appropriate. If you simply want to know whether the value is unusual, use two-tailed. Switching to a one-tailed test after seeing which direction the result went halves your p-value without any statistical justification, and it is one of the most common forms of unintentional p-hacking.

4.4 Why z-scores fail at outlier detection on small samples

This is the most important limitation on the page, and most calculators ignore it entirely. The standard advice is to flag any value with |z| > 3. The problem is circular: an extreme value inflates the standard deviation used to compute its own z-score, so it disguises itself.

The mathematics is unforgiving. With n observations, the largest possible z-score is (n − 1) ÷ √n. For n = 10 that ceiling is 2.85, so no value in a sample of ten can ever reach z = 3, however extreme it is. With n = 5 the maximum is 1.79. You could have a value a thousand times larger than the rest and the z-score rule would never flag it. This is why the calculator reports the theoretical maximum alongside your results whenever the sample is small.

4.5 The modified z-score, and when to use it

The fix is to replace the mean with the median and the standard deviation with the median absolute deviation, neither of which an outlier can distort. The modified z-score is 0.6745 times the deviation from the median, divided by the MAD. The constant 0.6745 is the 75th percentile of the standard normal, which rescales the MAD so the modified z is comparable to an ordinary z for normal data.

Iglewicz and Hoaglin recommend flagging values with a modified |z| above 3.5. Because it is built from robust components, it has no artificial ceiling and works on samples where the ordinary z-score is useless. When the two disagree, trust the modified version: a value flagged by the modified z but not by the ordinary z is almost always a genuine outlier that inflated the standard deviation enough to hide itself.

4.6 Sample versus population, and why it matters less than you think

Textbooks write the z-score with the Greek letters μ and σ, implying you know the true population values. In practice you almost never do, so you substitute the sample mean and sample standard deviation. Strictly this produces a slightly different quantity, and with small samples the resulting score follows a t-distribution rather than a normal one.

For most practical purposes the distinction matters less than the normality assumption does. If n is above about 30, the difference between using s and σ is small. If n is below 30 and you are computing a p-value for a sample mean, you should be using a t-test rather than a z-test. The calculator lets you choose the denominator so you can match whatever convention your course or software uses.

4.7 The difference between z for a value and z for a sample mean

These are two different calculations and confusing them is a common error. When you score an individual observation you divide by the standard deviation, because you are asking how unusual that one value is among individuals. When you score a sample mean you divide by the standard error, σ divided by the square root of n, because sample means vary far less than individual values do.

The practical consequence is that the same gap produces a much larger z-score for a mean. A sample mean two units above the population mean might give z = 0.2 as an individual value but z = 1.0 as a mean of 25 observations. Using the standard deviation when you should be using the standard error will make a real effect look unremarkable.

4.8 Reading the four charts

Chart 1 draws the standard normal curve with your z marked and the p-value region shaded, which is the figure most people picture when they think of a z-score. Chart 2 plots every observation as a z-score with reference lines at ±2 and ±3, so outliers are immediately visible. Chart 3 shows the raw distribution so you can judge whether the normality assumption behind the percentile is reasonable. Chart 4 is the cumulative normal curve, which is where the percentile is read from.

Chart 3 deserves particular attention. If the histogram is visibly skewed or has two peaks, the percentile and p-value from charts 1 and 4 are unreliable even though the z-score itself is still arithmetically correct.

4.9 What a z-score cannot tell you

It cannot tell you whether a value is wrong, only whether it is unusual. An extreme z-score might indicate a data-entry error, a faulty instrument, or the single most scientifically interesting observation in your dataset. The statistic cannot distinguish between them and neither should you without going back to the raw record.

It also carries no information about sample size, no measure of its own uncertainty, and no protection against a biased sample. And because it is computed from the mean and standard deviation, it inherits every weakness of those two statistics, including their sensitivity to skew.

4.10 Practical judgement

Compute the z-score, then ask two questions before you use the percentile. First, are the data plausibly normal? Check chart 3, and if the answer is no, report the z-score as a distance in standard deviations but not as a percentile. Second, is the sample large enough for the outlier rule to work? If n is under about 30, use the modified z-score instead. Report the mean, standard deviation and n alongside any z-score, because the same z means completely different things depending on the distribution it came from.

▶ Run the analysis above to auto-fill all five examples with your results.

1. Paste your numbers into the data column. Raw data mode opens first because it is what most people need. Enter your values comma-separated, exactly as the placeholder shows. The calculator works out the mean and standard deviation for you, then scores every observation. Leave the highlight box blank to standardise the whole dataset, or type a value to score just that one.
2. Or switch mode if you already have the summary statistics. I know the mean and SD is the classic textbook case where you enter the value, the mean and the standard deviation directly. Reverse works backwards from a z-score or percentile to a raw value. Z for a sample mean uses the standard error instead of the standard deviation. In every mode the standard deviation must be greater than zero, because dividing by zero leaves the z-score undefined.
3. Load a sample dataset to see how it behaves. Eight are built in, including a heart-rate set containing a genuine outlier and a ten-value set that demonstrates the small-sample ceiling. Selecting one replaces the data column immediately.
4. Add clusters to compare groups. Each gets its own mean, standard deviation and set of z-scores. Every column has its own Clear and Remove button, and Remove is disabled on the last remaining column.
5. Or upload a CSV. Open the upload panel inside the raw data tab and click the column names you want. Every column you click becomes its own cluster.
6. Choose your standard deviation type. Sample (n − 1) is correct unless you genuinely measured the whole population. This is the setting that makes Excel's STDEV.S and STDEV.P disagree.
7. Choose the p-value tail before you look at the result. Two-tailed asks whether the value is unusual in either direction; one-tailed commits to a direction. Deciding after seeing the data halves your p-value without justification.
8. Press Calculate Z-Score. Nothing is computed until you do, and changing any input clears the results so you never read stale numbers.
9. Read the colour bar and the warnings first. The bar shows instantly where your z sits against the empirical rule bands, and the warnings will tell you if your sample is too small for the |z| > 3 rule to be capable of firing at all.
10. Check chart 3 before trusting the percentile. The z-score is always arithmetically correct, but the percentile and p-value assume normality. If the histogram is visibly skewed, report the z-score as a distance and drop the percentile.

Excel can do every part of this: the mean, the standard deviation, the z-score itself, the percentile, the p-value, and the reverse lookup. There are two ways to write the z-score and three functions you need for the normal curve. Below is the whole workflow in ten steps, each with a picture of what your sheet should look like.

Step 1. Put your data in one column with a header in A1, and set aside a small block for the summary statistics.

Step 2. AVERAGE gives the mean, 53.1667. Select the whole data range, not just the rows you can see.

Step 3. STDEV.S uses n minus 1 and is the right choice for a sample. STDEV.P uses n and gives the smaller 5.4288. Pick one and stay with it.

Step 4. The manual formula. The dollar signs lock the mean and SD cells so you can drag the formula down the whole column without the references sliding.

Step 5. STANDARDIZE(x, mean, sd) does exactly the same thing and is easier to read. Both give -0.9112 for the value 48.

Step 6. NORM.S.DIST with TRUE returns the cumulative area, 0.9164, so the value sits at about the 92nd percentile. The FALSE argument returns the curve height instead, which is not what you want.

Step 7. The two-tailed p-value is 0.1671. The right-tail version drops the 2 and gives 0.0836. Decide which you need before you look at the number.

Step 8. Working backwards. NORM.S.INV turns a percentile into a z-score, then mean plus z times SD recovers the raw value, 62.4938.

Step 9. A flag column. Note that with n = 12 the largest possible z-score is only 3.18, so this rule can barely fire at all. Below n = 11 it can never fire.

Step 10. The robust alternative. Median with =MEDIAN(A2:A13), MAD with =MEDIAN(ABS(A2:A13-MEDIAN(A2:A13))) entered as an array formula, then flag anything above 3.5 in absolute value.

The formula cheat sheet

Five mistakes that catch people out

• Forgetting the dollar signs. Drag =(A2-E2)/E3 down and row 3 will divide by the wrong cells. Write $E$2 and $E$3.
• Using NORM.DIST instead of NORM.S.DIST. The S version is the standard normal and takes a z-score. The plain version needs the mean and SD as extra arguments.
• Passing FALSE to NORM.S.DIST. That returns the height of the curve, not the area, and the number will look plausible but be meaningless as a percentile.
• Mixing STDEV.S and STDEV.P across a workbook. The z-scores will not be comparable. Decide once.
• Applying the |z| > 3 rule to a short column. With 12 rows the largest attainable z is 3.18. With 8 rows it is 2.47. The rule silently never fires.

Base R does all of this with no packages at all. scale() standardises a vector, pnorm() converts a z-score to a cumulative probability, and qnorm() goes the other way. The script below computes every quantity on this page and draws one figure. Copy it whole and it will run.

# Z-Score Calculator in R (base R, no packages)

# ---- 1. Your data -----------------------------------------------------
x         <- c(52, 48, 55, 61, 47, 58, 50, 63, 45, 56, 54, 49)
highlight <- 61            # the value you want to score

# ---- 2. Mean and standard deviation -----------------------------------
n    <- length(x)
mean_x <- mean(x)
sd_x   <- sd(x)            # sample SD, divides by n - 1
# population SD if you need it:
# sd_pop <- sd(x) * sqrt((n - 1) / n)

z <- (x - mean_x) / sd_x   # or simply: z <- as.vector(scale(x))

# ---- 3. Percentile and p-value ----------------------------------------
z_hi  <- (highlight - mean_x) / sd_x
pct   <- pnorm(z_hi) * 100
p_two <- 2 * (1 - pnorm(abs(z_hi)))
p_rt  <- 1 - pnorm(z_hi)   # right tail only

# ---- 4. Robust modified z-score (Iglewicz & Hoaglin 1993) -------------
med   <- median(x)
mad_x <- median(abs(x - med))          # raw MAD, not R's mad() which rescales
mod_z <- if (mad_x > 0) 0.6745 * (x - med) / mad_x else rep(0, n)

z_ceiling <- (n - 1) / sqrt(n)         # largest |z| any value can reach

cat(sprintf("n = %d   mean = %.4f   SD = %.4f\n", n, mean_x, sd_x))
cat(sprintf("z for %g = %.4f\n", highlight, z_hi))
cat(sprintf("percentile = %.2f%%   two-tailed p = %.4f\n", pct, p_two))
cat(sprintf("max possible |z| at n=%d is %.2f\n", n, z_ceiling))
cat("outliers |z|>3       :", x[abs(z) > 3], "\n")
cat("outliers |mod z|>3.5 :", x[abs(mod_z) > 3.5], "\n")

# ---- 5. One figure ----------------------------------------------------
grid <- seq(-4, 4, length.out = 600)
plot(grid, dnorm(grid), type = "l", lwd = 2, col = "#0f766e",
     xlab = "z-score (standard deviations from the mean)",
     ylab = "density", bty = "n",
     main = sprintf("Z-Score Summary   n=%d, mean=%.2f, SD=%.2f",
                    n, mean_x, sd_x))

# shade the two tails beyond |z_hi|
tail_r <- grid[grid >=  abs(z_hi)]
tail_l <- grid[grid <= -abs(z_hi)]
polygon(c(tail_r, rev(tail_r)), c(dnorm(tail_r), rep(0, length(tail_r))),
        col = adjustcolor("#f59e0b", 0.45), border = NA)
polygon(c(tail_l, rev(tail_l)), c(dnorm(tail_l), rep(0, length(tail_l))),
        col = adjustcolor("#f59e0b", 0.45), border = NA)

abline(v = z_hi, col = "#7c3aed", lwd = 2.2)
abline(v = c(-3, -2, 2, 3), col = "#94a3b8", lty = 3)
points(z, rep(-0.012, n), pch = 19, col = "#0ea5e9", xpd = NA)

legend("topright", bty = "n", cex = 0.85,
       legend = c(sprintf("z = %.3f  (%.1fth pct)", z_hi, pct),
                  sprintf("two-tailed p = %.4f", p_two),
                  "your data as z-scores"),
       col = c("#7c3aed", "#f59e0b", "#0ea5e9"),
       lwd = c(2.2, 6, NA), pch = c(NA, NA, 19))

What the script prints

Line-by-line explanation

• Block 1 holds the only two things you change: your vector and the value you want to score. Everything below is generic.
• Block 2 computes the mean and the sample standard deviation. The commented line shows the population conversion, because R will not do it for you. scale(x) is the idiomatic shortcut but returns a matrix, so as.vector() is needed if you want a plain numeric vector back.
• Block 3 converts the highlighted z to a percentile with pnorm() and to p-values. Note that pnorm() is the direct equivalent of Excel's NORM.S.DIST(z, TRUE), and qnorm() is NORM.S.INV.
• Block 4 builds the robust version. Be careful here: R's built-in mad() already multiplies by 1.4826, so feeding it into the 0.6745 formula would double-scale the result. The script computes the raw median absolute deviation directly to avoid that.
• Block 5 draws a single figure containing everything: the standard normal curve, the shaded p-value region, a vertical line at your z, dotted guides at ±2 and ±3, and every observation plotted along the bottom as a z-score. xpd = NA lets those points sit below the axis without being clipped.

Useful one-liners

NumPy computes the z-scores, SciPy supplies the normal distribution, and Matplotlib draws the figure. The script below was run before being published, so the printed output shown underneath is real, not typed by hand.

# Z-Score Calculator in Python
# Computes z-scores, percentiles and p-values, and draws one summary figure.
import numpy as np
import matplotlib.pyplot as plt
from scipy import stats

# ---- 1. Your data -----------------------------------------------------
x = np.array([52, 48, 55, 61, 47, 58, 50, 63, 45, 56, 54, 49], dtype=float)
highlight = 61.0          # the value you want to score

# ---- 2. Mean and standard deviation -----------------------------------
n    = x.size
mean = x.mean()
sd   = x.std(ddof=1)      # ddof=1 = sample SD. Use ddof=0 for population
z    = (x - mean) / sd

# ---- 3. Percentile and p-value for the highlighted value --------------
z_hi  = (highlight - mean) / sd
pct   = stats.norm.cdf(z_hi) * 100
p_two = 2 * (1 - stats.norm.cdf(abs(z_hi)))

# ---- 4. Robust modified z-score (Iglewicz and Hoaglin 1993) -----------
med   = np.median(x)
mad   = np.median(np.abs(x - med))
mod_z = 0.6745 * (x - med) / mad if mad > 0 else np.zeros_like(x)

z_ceiling = (n - 1) / np.sqrt(n)   # largest |z| any value can reach

print(f"n = {n}   mean = {mean:.4f}   SD = {sd:.4f}")
print(f"z for {highlight:g} = {z_hi:.4f}")
print(f"percentile = {pct:.2f}%   two-tailed p = {p_two:.4f}")
print(f"max possible |z| at n={n} is {z_ceiling:.2f}")
print("outliers |z|>3      :", x[np.abs(z) > 3].tolist())
print("outliers |mod z|>3.5:", x[np.abs(mod_z) > 3.5].tolist())

# ---- 5. One figure ----------------------------------------------------
fig, ax = plt.subplots(figsize=(9, 5))
grid = np.linspace(-4, 4, 600)
ax.plot(grid, stats.norm.pdf(grid), color="#0f766e", lw=2)
ax.fill_between(grid, stats.norm.pdf(grid), where=np.abs(grid) >= abs(z_hi),
                color="#f59e0b", alpha=.45,
                label=f"two-tailed p = {p_two:.4f}")
ax.axvline(z_hi, color="#7c3aed", lw=2.2,
           label=f"z = {z_hi:.3f}  ({pct:.1f}th pct)")
ax.scatter(z, np.full_like(z, -0.012), s=46, color="#0ea5e9",
           zorder=3, clip_on=False, label="your data as z-scores")
for b in (-3, -2, 2, 3):
    ax.axvline(b, color="#94a3b8", ls=":", lw=1)
ax.set_xlabel("z-score (standard deviations from the mean)")
ax.set_ylabel("density")
ax.set_title(f"Z-Score Summary   n={n}, mean={mean:.2f}, SD={sd:.2f}")
ax.legend(frameon=False, fontsize=9)
ax.spines[["top", "right"]].set_visible(False)
fig.tight_layout()
fig.savefig("z_score_summary.png", dpi=150)
plt.show()

Actual output from running the script

n = 12   mean = 53.1667   SD = 5.6702
z for 61 = 1.3815
percentile = 91.64%   two-tailed p = 0.1671
max possible |z| at n=12 is 3.18
outliers |z|>3      : []
outliers |mod z|>3.5: []

These are the same numbers the R script produces and the same numbers the calculator at the top of this page produces, which is a useful sanity check whenever you port an analysis between tools.

Line-by-line explanation

• Block 1 is the only part you edit. Setting dtype=float avoids integer division surprises if you later divide the array.
• Block 2 computes the mean and the sample standard deviation, then vectorises the z-score across the whole array in one line. NumPy broadcasting means no loop is needed.
• Block 3 uses stats.norm.cdf, the direct equivalent of R's pnorm() and Excel's NORM.S.DIST(z, TRUE). For the reverse direction use stats.norm.ppf(0.95), which returns 1.6449.
• Block 4 builds the robust modified z-score. The guard on mad > 0 matters: if more than half your values are identical the MAD is zero and the formula would divide by zero.
• Block 5 draws the single summary figure. fill_between with a where mask shades both tails in one call, clip_on=False lets the data points sit just below the axis, and hiding the top and right spines keeps the plot publication-ready.

Useful one-liners

11.1 Standard normal table, negative z-scores

Find your z-score to one decimal place down the left column, then read across to the second decimal place. The number in the cell is the area to the left of that z, which is the percentile expressed as a proportion.

11.2 Standard normal table, positive z-scores

Same reading method. For example z = 1.38 gives 0.9162, so about 91.6% of the distribution lies below that value.

11.3 The empirical rule

11.4 Common critical values

11.5 The maximum possible z-score by sample size

This is the table nobody prints, and it is the reason the |z| > 3 outlier rule fails so often. The largest z-score attainable in a sample of n is (n − 1) divided by the square root of n, no matter how extreme the value is.

Below n = 11 the ordinary z-score rule is mathematically incapable of flagging anything. Use the modified z-score with a threshold of 3.5 instead.

11.6 Z-scores, percentiles and everyday equivalents

11.7 Z-score to p-value quick reference

11.8 Area between the mean and z

Some textbooks print the table this way instead. Each cell gives the area between 0 and z, which is simply the cumulative area minus 0.5. If your course uses this style, the value for z = 1.96 is 0.4750 rather than 0.9750.

11.9 Right-tail areas, the one-tailed p-value table

Each cell is the area to the right of z, which is exactly the one-tailed p-value. Double it for a two-tailed test. This is the table to use when you are testing a directional hypothesis.

11.10 Z-scores converted to other standardised scales

Almost every named score system is a z-score in disguise, rescaled to avoid decimals and negative numbers. This table shows the conversions, so you can move between them without recomputing anything.

Conversion formulas: T = 50 + 10z, IQ = 100 + 15z, SAT section = 500 + 100z, GRE section = 150 + 8.75z, stanine = 5 + 2z rounded and clipped to 1-9, sten = 5.5 + 2z rounded and clipped to 1-10.

11.11 How rare is that z-score?

Percentages are hard to feel. This table restates the same probabilities as "one in how many", which is usually more intuitive when you are deciding whether an observation is worth investigating.

The five sigma standard used in particle physics corresponds to a one-sided probability of about 1 in 3.5 million. Six sigma manufacturing allows for a 1.5 sigma process drift, so in practice it targets about 3.4 defects per million rather than the 1 in a billion the raw table implies.

11.12 Sample size and the standard error

When you score a sample mean rather than a single value, the denominator is the standard error. This table shows how quickly it shrinks, and why quadrupling your sample only halves your uncertainty.

Read the last column as: with n = 25 a 95% interval reaches 0.392 standard deviations either side of the sample mean. Going from n = 25 to n = 100 halves that to 0.196, which is why sample size has diminishing returns.

11.13 The same calculation in five packages

11.14 Choosing an outlier method

11.15 Reading the sign and size at a glance

These frequencies apply to a normal distribution only. On skewed data, values with |z| above 3 can be entirely common, which is why chart 3 in the results section matters before you use this table.

Every number below was computed with the calculator on this page, using the sample standard deviation and a two-tailed p-value unless stated otherwise. Each example has its own colour and its own figure showing where the value falls on the normal curve. Paste any dataset into the tool and you will reproduce the result exactly.

A z-score is only as good as the mean and standard deviation behind it, and both are easy to compromise before you ever open a calculator. This is the protocol that keeps them honest.

1. Define the reference population before you collect anything. A z-score answers "unusual compared with what". Compared with this year's cohort, or all cohorts? Compared with this machine, or the whole production line? The answer determines which mean and SD you should be using, and it cannot be decided afterwards.
2. Decide whether you have a population or a sample. If you measured every unit that exists in your defined population, use the population SD. In almost every real study you have a sample, so use n minus 1.
3. Use a single measurement protocol throughout. Same instrument, same units, same operator instructions, same time of day where it matters. Mixing two measurement methods inflates the SD and shrinks every z-score, which quietly hides genuine outliers.
4. Record raw values, never rounded ones. Rounding to the nearest whole number before computing an SD can shift z-scores in the second decimal place. Round at the reporting stage only.
5. Log every exclusion at the moment it happens. Instrument failure, protocol violation, participant withdrawal. Write down what and why. Reviewers will compare your stated n against your reported one.
6. Aim for n of at least 30 if outlier screening is a goal. Below that the |z| > 3 rule is mathematically hobbled by the ceiling. If a small sample is unavoidable, plan to use the modified z-score and say so in your methods.
7. Check for the units trap. Z-scores are unitless, which is their strength, but the mean and SD must come from data in one consistent unit. One row in grams among a column of kilograms will not throw an error, it will just produce a spectacular false outlier.
8. Screen for normality before you rely on percentiles. A histogram and a Q-Q plot take thirty seconds. If the data are clearly skewed, plan to report the z-score as a distance in standard deviations and drop the percentile claim.
9. Keep the raw data file untouched. Do all cleaning in a script or a copy so that any z-score can be traced back to the original record. When a value is flagged, you will want to look at the original entry.
10. Store the mean, SD and n alongside the z-scores. A column of z-scores with no record of what standardised them is uninterpretable and cannot be back-transformed.

Use a z-score when

• You need to compare measurements on different scales. This is the original purpose. Height in centimetres against weight in kilograms, an essay mark against a maths mark, revenue in one currency against another.
• You want a percentile from a roughly normal distribution. Test scores, measurement error, biological measurements within a defined group.
• You are standardising features before modelling. Regularised regression, k-nearest neighbours, principal component analysis, neural networks and anything using gradient descent all behave badly when features have wildly different scales.
• You are screening a reasonably large sample for outliers. Above about n = 30 the ordinary rule becomes usable, though the modified version is still safer.
• The population mean and SD are genuinely known. Standardised tests, published growth charts, calibrated instruments. This is the case textbooks assume and the case where the percentile is most trustworthy.
• You need a cut-off from a percentile. The reverse direction: what value marks the top 5%, what stock level covers 95% of demand.

Do not use a z-score when

• The data are strongly skewed and you want a percentile. Income, waiting times, species abundance, insurance claims. The z-score is still a valid distance but the normal percentile attached to it will be wrong. Use the empirical percentile rank instead.
• The sample is small and you are hunting outliers. Below n = 11 the |z| > 3 rule cannot fire at all. Use the modified z-score.
• The data are ordinal. Likert responses, rankings, categories with an order. The mean and SD of an ordinal scale are not well defined, so neither is the z-score.
• The standard deviation is zero or near zero. If every value is identical the z-score is undefined. If they are nearly identical, tiny differences become enormous z-scores.
• You are testing a sample mean with an estimated SD and a small n. That is a t-test, not a z-test. The t-distribution has heavier tails and gives more honest p-values below about n = 30.
• The distribution has two peaks. A bimodal dataset has a mean sitting in the empty valley between the groups, so every z-score is measured from a value that no observation resembles.
• You want to say something about the reliability of the estimate. A z-score carries no uncertainty of its own and no information about sample size. Use a confidence interval for that.

What to use instead

What the z-score assumes

Limitations you should state in a write-up

• The percentile depends entirely on normality. The z-score does not, and the two are often conflated. Be explicit about which claim you are making.
• The mean and SD are not robust. A single extreme value moves both, so every z-score in the dataset shifts because of one observation.
• The ceiling on small samples is a hard mathematical limit, not a statistical convention. It cannot be argued around.
• A z-score carries no uncertainty. It is a point description with no confidence interval attached and no sensitivity to sample size.
• Standardising does not fix skew. It shifts and rescales the distribution but leaves its shape untouched. A skewed variable is still skewed after standardising.
• Comparability requires a shared reference. Two z-scores computed against different populations are not directly comparable, however similar the numbers look.
• Extreme z-scores are not evidence of error. They flag values worth inspecting, nothing more. The decision to exclude is a scientific judgement, not a statistical one.

The z-score is one of the smallest ideas in statistics and one of the most widely used. Subtract the mean, divide by the standard deviation, and you have converted a measurement in any unit into a position on a common scale. That single operation is what lets an exam mark be compared with an essay grade, a machine tolerance with a laboratory assay, and a height measurement with a weight measurement. It is the reason standardisation appears in almost every statistical method that combines variables.

Its interpretation is equally compact. The sign gives the direction, the magnitude gives the distance in standard deviations, and the empirical rule supplies rough landmarks: about 68% of a normal distribution lies within one standard deviation of the mean, about 95% within two, about 99.7% within three. A z of 2 is therefore uncommon and a z of 3 is rare, in a normal distribution.

That last qualification is where most misuse begins. The z-score itself assumes nothing, but the moment you convert it into a percentile or a p-value you are reading off the normal curve, and if your data are skewed those numbers are wrong even though the z-score is right. Check a histogram before you quote a percentile. If the shape is not roughly symmetric, report the z-score as a distance and use an empirical percentile rank instead.

The second failure is subtler and far more common: using the |z| > 3 rule to find outliers in a small sample. The largest z-score attainable in a sample of n is (n − 1) divided by the square root of n. With ten observations that ceiling is 2.85, so the rule cannot fire no matter how extreme a value is. Worse, an outlier inflates the standard deviation used to compute its own z-score, disguising itself even when the sample is large enough. Example 4 on this page shows exactly that: a heart rate of 180 among readings in the 120s gives an ordinary z of 3.68, barely past the threshold, while the modified z-score built from the median and MAD returns 16.05. Whenever you are screening for outliers, particularly below about n = 30, use the modified z-score with a threshold of 3.5.

Three further habits will keep your results defensible. Decide sample or population once and stay with it, because the difference between STDEV.S and STDEV.P propagates through every number downstream and is the usual reason two people get slightly different answers. Choose your p-value tail before you look at the data, not after. And always report the mean, standard deviation and n alongside any z-score, because the same z means entirely different things depending on the distribution it came from, and without those three numbers nobody, including you in six months, can reconstruct what you did.

Used with those caveats, the z-score remains what it has been since Fisher and Pearson formalised it: the simplest honest way to say how unusual a number is.

1. Iglewicz, B., & Hoaglin, D. C. (1993). How to Detect and Handle Outliers. ASQC Quality Press. asq.org
2. Shiffler, R. E. (1988). Maximum Z scores and outliers. The American Statistician, 42(1), 79-80. doi.org/10.1080/00031305.1988.10475530
3. Leys, C., Ley, C., Klein, O., Bernard, P., & Licata, L. (2013). Detecting outliers: Do not use standard deviation around the mean, use absolute deviation around the median. Journal of Experimental Social Psychology, 49(4), 764-766. doi.org/10.1016/j.jesp.2013.03.013
4. Rousseeuw, P. J., & Croux, C. (1993). Alternatives to the median absolute deviation. Journal of the American Statistical Association, 88(424), 1273-1283. doi.org/10.1080/01621459.1993.10476408
5. Grubbs, F. E. (1969). Procedures for detecting outlying observations in samples. Technometrics, 11(1), 1-21. doi.org/10.1080/00401706.1969.10490657
6. Tukey, J. W. (1977). Exploratory Data Analysis. Addison-Wesley. archive.org
7. Moore, D. S., McCabe, G. P., & Craig, B. A. (2021). Introduction to the Practice of Statistics (10th ed.). W. H. Freeman. macmillanlearning.com
8. Field, A. (2024). Discovering Statistics Using IBM SPSS Statistics (6th ed.). SAGE. sagepub.com
9. Barnett, V., & Lewis, T. (1994). Outliers in Statistical Data (3rd ed.). Wiley. wiley.com
10. Abramowitz, M., & Stegun, I. A. (1964). Handbook of Mathematical Functions. National Bureau of Standards. personal.math.ubc.ca
11. Press, W. H., Teukolsky, S. A., Vetterling, W. T., & Flannery, B. P. (2007). Numerical Recipes: The Art of Scientific Computing (3rd ed.). Cambridge University Press. numerical.recipes
12. Acklam, P. J. (2003). An algorithm for computing the inverse normal cumulative distribution function. Archived notes
13. Wicklin, R. (2011). What is a z-score? What is a p-value? SAS Blogs, The DO Loop. blogs.sas.com
14. Wilkinson, L., & the Task Force on Statistical Inference (1999). Statistical methods in psychology journals: Guidelines and explanations. American Psychologist, 54(8), 594-604. doi.org/10.1037/0003-066X.54.8.594
15. American Psychological Association (2020). Publication Manual of the American Psychological Association (7th ed.). apastyle.apa.org
16. Ghasemi, A., & Zahediasl, S. (2012). Normality tests for statistical analysis: A guide for non-statisticians. International Journal of Endocrinology and Metabolism, 10(2), 486-489. doi.org/10.5812/ijem.3505
17. Kuhn, M., & Johnson, K. (2019). Feature Engineering and Selection: A Practical Approach for Predictive Models. CRC Press. bookdown.org/max/FES
18. Pedregosa, F., et al. (2011). Scikit-learn: Machine learning in Python. Journal of Machine Learning Research, 12, 2825-2830. jmlr.org
19. Virtanen, P., et al. (2020). SciPy 1.0: Fundamental algorithms for scientific computing in Python. Nature Methods, 17, 261-272. doi.org/10.1038/s41592-019-0686-2
20. R Core Team (2024). R: A Language and Environment for Statistical Computing. R Foundation for Statistical Computing. r-project.org