Protocols and best practices for western blot quantification and analysis including band detection, normalization, and statistical methods.
npx skills add https://github.com/jaechang-hits/SciAgent-Skills --skill western-blot-quantification
Short Description: Comprehensive guide for quantifying and analyzing Western blot images with multiple experimental repetitions, including intensity measurement, normalization, statistical analysis, and visualization.
Authors: Ohagent Team
Version: 1.0
Last Updated: December 2025
License: CC BY 4.0
Commercial Use: ✅ Allowed
This guide provides a standardized workflow for analyzing Western blot images, particularly for experiments with multiple repetitions and conditions. The protocol covers band intensity detection, normalization procedures, statistical aggregation, and visualization best practices.
Western blot quantification cannot use raw band intensities, because total protein loaded per lane varies between samples (pipetting error, transfer efficiency, gel artifacts). A loading control is a protein assumed to be expressed at the same level across all samples (commonly GAPDH, β-actin, α-tubulin, or a total-protein stain such as Ponceau S / stain-free imaging). Dividing the target band intensity by the loading control intensity in the same lane yields a normalized value that corrects for these per-lane technical variations. The loading control must itself be unsaturated and within the linear dynamic range of the detection system.
When two related signals are measured in the same blot — for example a total form (SMAD2) and its phosphorylated form (PSMAD2) — a two-step normalization disentangles changes in protein abundance from changes in modification state. Step A normalizes the total protein to a housekeeping control (SMAD2_norm = SMAD2 / GAPDH); Step B normalizes the modified form to that loading-corrected total (PSMAD2_target = PSMAD2 / SMAD2_norm). This isolates the modification-specific signal from changes in expression of the underlying protein.
Each Western blot is one experimental observation; biological conclusions require biological replicates (independent experiments, not just multiple lanes from one gel). Aggregation steps: (1) normalize *within* each replicate, (2) compute fold-change relative to the within-replicate control (so the control is 1.0 by definition), (3) compute mean and dispersion (SD or SE) *across* replicates. Normalizing across replicates before computing fold-change inflates apparent effect size and confuses gel-to-gel variation with biological effect.
SD describes the spread of the underlying biological response across replicates and is appropriate when the question is "how variable is this effect?". SE (= SD / √n) describes the precision of the estimated mean and is appropriate when the question is "how confident are we in this mean value?". For typical n=3 western blot experiments, SD bars look larger than SE bars but communicate the underlying biology more honestly. Always state which error measure is plotted in the figure legend.
Western blot quantification decision tree
└── Single target protein measured?
├── Yes -> Single-step normalization: Target / LoadingControl (per lane)
│ └── Compute fold change vs control within each replicate
│ └── Aggregate mean +/- error across replicates
└── No, two related signals (e.g., total + modified form)
└── Two-step normalization
├── Step A: TotalForm_norm = TotalForm / LoadingControl (per lane)
└── Step B: ModifiedForm_target = ModifiedForm / TotalForm_norm
Error bar choice:
└── Reporting biological variability of the effect? -> SD
└── Reporting precision of the mean estimate? -> SE = SD / sqrt(n)
Experimental design choice:
└── Discrete treatments (control vs conditions) -> Multi-condition design + bar graph + ANOVA / t-tests
└── Same treatment over multiple time points -> Time course design + line graph; normalize to t0 control
└── Same treatment at multiple concentrations -> Dose response design + log-x line graph; fit EC50 / IC50
| Situation | Recommended choice | Rationale |
|-----------|--------------------|-----------|
| Quantifying total protein abundance changes | Single-step normalization (Target / LoadingControl) | One measurement per lane; loading control corrects total-protein loading |
| Quantifying post-translational modification (phosphorylation, ubiquitination) | Two-step normalization (Modified / Total_norm) | Isolates modification stoichiometry from changes in total protein expression |
| n = 3 replicates, biology-focused figure | Mean ± SD | Communicates the spread of the biological response |
| n = 3 replicates, statistical-precision figure | Mean ± SE | Communicates the precision of the mean estimate |
| Small fold changes (~1.5×) on noisy blots | Increase n to ≥ 4–6 and report SE with explicit n in legend | Low effect size requires more replicates for adequate statistical power |
| Comparing 4+ discrete conditions | Multi-condition design + ANOVA with post-hoc correction | Pairwise t-tests across many conditions inflate Type I error |
| Tracking the same effect over time | Time-course design, normalize to t = 0 within each replicate | Removes baseline drift between replicates |
| Determining potency (EC50 / IC50) | Dose-response design with log-spaced concentrations | Log spacing samples the sigmoidal response uniformly; nonlinear fit gives EC50 |
| Loading control band saturated | Re-image at lower exposure or dilute the lysate | Saturated bands violate the linear dynamic range and silently bias normalization |
| One outlier replicate with unusually high variability | Document and exclude with justification (e.g., transfer artifact) | Honest exclusion is preferable to a noisy mean; never silently drop data |
Objective: Identify ROIs and isolate individual bands in the Western blot image.
Key Considerations:
Tools: analyze_pixel_distribution, find_roi_from_image
Objective: Quantify band intensities for all detected bands.
Procedure:
Best Practices:
Objective: Normalize target protein intensities to account for loading variations.
Two-Step Normalization Process:
Calculate the relative intensity of the loading control protein:
SMAD2_norm = Intensity_SMAD2 / Intensity_GAPDH
This accounts for variations in total protein loading across samples.
Calculate the final normalized target protein intensity:
Target_value = Intensity_PSMAD2 / SMAD2_norm
This provides the normalized PSMAD2 intensity that accounts for both loading control and relative protein levels.
Alternative Normalization Methods:
Target_norm = Intensity_Target / Intensity_GAPDHTarget_norm = Intensity_Target / Intensity_TotalProteinObjective: Express results relative to a control condition.
Procedure:
Fold_Change = Target_value_condition / Target_value_control
Important Notes:
Objective: Combine data from multiple experimental repetitions.
Procedure:
Statistical Considerations:
Objective: Create clear, publication-ready visualizations.
Bar Graph Requirements:
Visualization Best Practices:
Verification Images:
wb_grid_verification.png)Problem: Some bands not detected or incorrectly identified
Solutions:
Problem: Large standard deviations or inconsistent results
Solutions:
Problem: Normalized values don't match expected biological response
Solutions:
Problem: High background affecting intensity measurements
Solutions:
Before finalizing analysis, verify:
Required Outputs:
psmad2_quantification.png)wb_grid_verification.pngFor a typical experiment with 3 repetitions and 4 conditions:
Loading Control Normalization:
Loading_norm = Intensity_LoadingControl / Intensity_Housekeeping
Target Normalization:
Target_norm = Intensity_Target / Loading_norm
Fold Change:
Fold_Change = Target_norm_condition / Target_norm_control
Statistics:
Mean = Σ(values) / n
SD = √[Σ(value - mean)² / (n-1)]
SE = SD / √n
lower_threshold and upper_threshold per image; manually verify the grid overlay before extracting intensities, and preserve correctly detected ROIs when adjusting parameters.Integration with protocols.io API for managing scientific protocols. This skill should be used when working with protocols.io to search, create, update, or publish protocols; manage protocol steps and materials; handle discussions and comments; organize workspaces; upload and manage files; or integrate protocols.io functionality into workflows. Applicable for protocol discovery, collaborative protocol development, experiment tracking, lab protocol management, and scientific documentation.
Analyzes job descriptions and generates tailored resumes that highlight relevant experience, skills, and achievements to maximize interview chances
Generate Excalidraw diagrams from natural language descriptions. Use when asked to "create a diagram", "make a flowchart", "visualize a process", "draw a system architecture", "create a mind map", or "generate an Excalidraw file". Supports flowcharts, relationship diagrams, mind maps, and system architecture diagrams. Outputs .excalidraw JSON files that can be opened directly in Excalidraw.
Build and distribute Expo development clients locally or via TestFlight
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Data structure for annotated matrices in single-cell analysis. Use when working with .h5ad files or integrating with the scverse ecosystem. This is the data format skill—for analysis workflows use scanpy; for probabilistic models use scvi-tools; for population-scale queries use cellxgene-census.
Benchling R&D platform integration. Access registry (DNA, proteins), inventory, ELN entries, workflows via API, build Benchling Apps, query Data Warehouse, for lab data management automation.
Comprehensive molecular biology toolkit. Use for sequence manipulation, file parsing (FASTA/GenBank/PDB), phylogenetics, and programmatic NCBI/PubMed access (Bio.Entrez). Best for batch processing, custom bioinformatics pipelines, BLAST automation. For quick lookups use gget; for multi-service integration use bioservices.
Take jaechang-hits/western-blot-quantification from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.