Blog
Back to Blog

How to Verify Western Blot Signal Is in the Linear Range

If you're quantifying a western blot without first confirming that your signal sits within the linear dynamic range of your detection system, your fold-change numbers are made up. Not approximately correct — potentially off by 2–5× or more. A saturated band and a truly upregulated band can look identical on film or on a short exposure, and no amount of careful normalization downstream can rescue data collected outside the linear range.

The fix is straightforward: run a loading series, plot signal vs. protein amount, and confirm your experimental samples fall within the linear portion of that curve. This post walks through exactly how to do that, what "linear" actually means for different detection methods, and the common mistakes that quietly wreck quantification even when people think they're being careful.

Why Linear Range Matters (With Numbers)

Detection systems have a floor (background noise) and a ceiling (signal saturation). Between those two limits, doubling the amount of protein on the membrane should roughly double the signal intensity. That's the linear dynamic range, and it varies enormously by detection method:

The practical consequence: on film, a true 10-fold increase in protein might read as a 3-fold increase because the high-abundance signal is compressed into the saturated plateau. You'd report a statistically significant but biologically wrong number. Reviewers and journals increasingly ask for linear range verification for exactly this reason (Bhatt et al., 2024, multiple journal guidelines since ~2015).

How to Run a Linear Range Validation

You only need to do this once per antibody–detection system combination (and again if you change imager, substrate, or antibody lot). Here's the protocol:

  1. Prepare a two-fold dilution series of your lysate. Use a sample you know expresses the target. Load 5–7 lanes: e.g., 2.5, 5, 10, 20, 40, and 80 µg total protein. Some people use a 1.5× series for finer resolution, but 2× steps are usually enough.

  2. Run and transfer as normal. Don't change anything about your protocol — you're validating the system as you actually use it.

  3. Detect and image without saturating the acquisition. On a ChemiDoc or Azure, use the auto-exposure or signal accumulation mode, but then also check a shorter exposure. In Image Lab (Bio-Rad), saturated pixels show up as red in the "Highlight Saturated Pixels" overlay. In Image Studio (LI-COR), check the intensity display. If any pixel in your band is at the maximum value (65,535 for a 16-bit image, 255 for 8-bit), that image is saturated and cannot be used for quantification.

  4. Quantify band intensities. Draw equal-sized ROIs around each band, subtract local background using a method you'll use consistently (e.g., rolling ball, lane-edge average, or a blank region of the membrane). Record the background-subtracted integrated intensity for each lane.

  5. Plot intensity (y-axis) vs. protein loaded (x-axis). Fit a linear regression to the data points. Calculate R².

  6. Assess linearity. An R² ≥ 0.98 across the range is a reasonable threshold for most experimental purposes. More importantly, look at the residuals — a high R² can still hide systematic curvature. If your highest one or two points sag below the regression line, you've found the saturation ceiling. If your lowest point sits above the line, you're in the noise floor. Your experimental samples must fall within the protein amounts that are on the linear portion of this curve.

What "good enough" looks like

For most targets of interest (the protein you're actually measuring fold changes for), you want your experimental band intensities to sit between roughly 10% and 80% of the detector's maximum. Loading controls like GAPDH and beta-actin are the ones most likely to be saturated — they're highly abundant, and people load enough protein to see their low-abundance target, which pushes the housekeeping gene signal into the ceiling. This is why total protein normalization (TPN) with Ponceau S, stain-free gels, or REVERT is gaining traction: TPN uses the aggregate signal of many proteins across a wide intensity range, making it less susceptible to single-band saturation (Aldridge et al., 2008; Gassmann et al., 2009).

Common Mistakes That Undermine Linear Range

Validating the loading control but not the target (or vice versa). Both signals need to be in range. A saturated GAPDH band divided into a linear-range target band produces a ratio that's systematically wrong — your normalized values will be compressed toward 1.0, masking real differences.

Using a single exposure and assuming it's fine. ECL signal decays. An image captured at 30 seconds may be linear; the same membrane at 5 minutes may be saturated for abundant targets. If you're using ECL, capture a series of exposures and pick the one where your bands of interest are in range. Better yet, switch to NIR fluorescence if quantification is the priority.

Confusing "no red pixels" with "in the linear range." The saturation warning in imaging software tells you when individual pixels hit the detector ceiling. But signal can be non-linear before pixel saturation occurs — the last 10–20% of the dynamic range often curves. The only way to know is the loading series.

Ignoring the issue for "relative" quantification. People sometimes argue that if all samples are treated the same, relative comparisons are still valid even without linear range confirmation. This is only true if all samples are on the same point of the saturation curve, which you can't know without checking. If your control samples are at 20% of max and your treated samples are at 90% of max, a 4.5-fold real difference (90/20) might read as 2.5-fold because the 90% point is already compressing.

Running the validation on a different membrane or day. Transfer efficiency, antibody activity, and substrate freshness all vary. Ideally, include two or three lanes of your dilution series on the same gel as your experimental samples. At minimum, run the validation under identical conditions.

A Worked Example

Suppose you're measuring phospho-ERK in response to EGF stimulation, normalized to total ERK. You load 20 µg per lane for your experimental samples. You run a separate validation blot with 5, 10, 20, 40, 80 µg of unstimulated lysate:

µg loaded p-ERK intensity Total ERK intensity
5 1,200 8,500
10 2,450 17,200
20 4,800 33,000
40 9,100 58,000
80 12,500 62,000

p-ERK: Linear from 5–40 µg (R² = 0.998). At 80 µg, the signal falls below the predicted value (~18,200 expected vs. 12,500 observed) — classic saturation.

Total ERK: Linear from 5–20 µg (R² = 0.999). At 40 µg it's already curving, and at 80 µg it's clearly saturated (expected ~132,000 vs. 62,000 observed).

Your experimental samples at 20 µg are within the linear range for p-ERK, but total ERK is right at the edge. If EGF stimulation increases total ERK expression at all, some treated lanes could push past linearity. You might consider dropping to 15 µg per lane, or using a less abundant normalizer.

This is the kind of thing that takes 20 minutes to plot but saves you from retracting a figure.

Check linearity without the spreadsheet. VoilaBlot measures band intensities in your browser and flags when signals approach saturation — no software install, and your image never leaves your machine.

Try VoilaBlot →

What to Report in Your Paper

Reviewers — and increasingly, journals — want to see evidence of linear range validation. At minimum:

If you're using film, be honest about it. Some reviewers will push back on quantification from film, and they're not wrong — but if film is all you have, at least show that your band intensities on the digitized film image fall within a validated range. Scan at high resolution (600 dpi minimum), save as TIFF, and quantify the scanned image rather than trying to eyeball differences.

The Short Version

Run a dilution series. Plot signal vs. protein. Confirm your experimental samples land on the straight part of the line. Do this for both your target protein and your normalizer. It takes one extra blot and 30 minutes of analysis, and it's the difference between quantitative data and expensive guesswork.

References