8 Common Mistakes When Using AlphaFold Structures in Research (And How to Avoid Every One)

8 Common Mistakes When Using AlphaFold Structures in Research (And How to Avoid Every One)

AlphaFold structures are easy to get and tempting to use immediately. The mistakes that follow are equally easy to make — and they appear regularly enough in submitted manuscripts that reviewers now have a standard list of what to check. Here are the eight most consequential errors, with exact fixes for each.

Severity: Critical — invalidates conclusions High — significantly misleads Medium — weakens credibility
01
Critical
Trusting low-pLDDT regions as real structure

AlphaFold models the full protein sequence, including regions it knows it cannot predict well. Disordered loops, flexible linkers, and unstructured termini all receive predicted coordinates — but those coordinates are essentially arbitrary placeholders. The pLDDT score below 50 on these residues is AlphaFold’s explicit signal that the predicted position is not reliable.

The mistake: treating these coordinates as meaningful and using them for analysis. Drawing conclusions from the predicted conformation of a low-pLDDT loop. Designing mutations at low-pLDDT residues based on their predicted position. Running docking calculations where the binding site includes low-pLDDT residues. All of these build on coordinates that carry no structural information.

The fix
Load the PDB in PyMOL and immediately run spectrum b, blue_cyan_yellow_orange_red, minimum=50, maximum=100 to color by pLDDT. Any residue colored yellow, orange, or red is unreliable. Exclude these regions from all structural conclusions. Report which regions had pLDDT below your chosen threshold in your methods section.
02
Critical
Not checking PAE for multi-domain proteins

This is the most common AlphaFold mistake in published papers — and the hardest to catch without knowing to look for it. A protein can have excellent pLDDT throughout (every residue individually well-predicted) while the relative orientation of two domains is completely uncertain (high inter-domain PAE). The individual domains are reliably predicted; how they face each other is not.

Researchers who don’t check the PAE plot proceed to analyze the predicted domain interface, design mutations to disrupt it, or run docking calculations targeting a binding site that spans the domain boundary — all based on a domain arrangement that AlphaFold explicitly flagged as uncertain.

The fix
Download the JSON file alongside every AlphaFold PDB. Open the PAE plot — available on the AFDB protein page or generated automatically by ColabFold. Look for the off-diagonal blocks: dark blue indicates confident inter-domain positioning; light blue or white indicates uncertainty. If your region of interest spans two domains with high inter-domain PAE, do not draw conclusions about their relative arrangement without experimental validation.
03
Critical
Conflating confidence with accuracy

pLDDT is a confidence score — not an accuracy measurement. A region with pLDDT 90 is predicted confidently. It is not guaranteed to be within 1 Å of the true experimental structure. AlphaFold can be confidently wrong for proteins whose folds were poorly represented in its training data, for proteins that require cofactors or binding partners to adopt their functional conformation, or for regions where the evolutionary signal is misleading.

The mistake manifests as statements like “the high pLDDT of this region confirms the predicted structure is accurate” — which overstates what pLDDT means. Confidence and accuracy are correlated but not identical.

The fix
Use pLDDT as a filter (below 70 = unreliable) but not as proof of accuracy. When accuracy matters — for example, when specific atomic positions determine a mechanistic conclusion — validate against experimental data. Compare the AlphaFold model to the structure of a close homolog if one exists. Run MD simulation to check whether the predicted conformation is stable in a physical force field. Cite pLDDT values as confidence indicators, not accuracy guarantees.
04
Critical
Docking into a low-confidence binding site

The output of a docking calculation is only as good as the receptor structure used as input. If the binding site residues have pLDDT below 70, the binding pocket geometry is uncertain — loop conformations are arbitrary, side chain positions are unreliable, and the pocket volume and shape may bear little resemblance to the true binding site. Docking results from such a receptor are not meaningful predictions of binding — they are docking artifacts.

This mistake is particularly insidious because the docking software will generate plausible-looking scores and poses regardless of receptor quality. Nothing in the output signals that the receptor was problematic.

The fix
Before docking, calculate the mean pLDDT of binding site residues (residues within 5 Å of the predicted pocket center). If the mean is below 70, do not proceed without further validation — run MD simulation first to relax the structure, or consider homology modeling from a high-identity template in the relevant conformation. Report the binding site pLDDT in your methods section for every docking study using an AlphaFold receptor.
05
High
Ignoring the apo conformation problem

AlphaFold predicts the most thermodynamically stable conformation of the protein — typically the apo (unbound) state, not the ligand-bound, active, or induced-fit conformation. For many drug targets, these conformations differ substantially: kinases switch between DFG-in and DFG-out states, GPCRs open and close their binding cavity, nuclear receptors adopt different helix-12 positions depending on the ligand.

Using an AlphaFold apo model for docking without acknowledging this limitation means potentially docking into a binding site that is closed or collapsed in the apo state — giving misleading results for the biologically relevant bound conformation.

The fix
Check the literature: is your target known to change conformation upon ligand binding? If yes, consider homology modeling from a template crystallized in the relevant conformation. If no homolog template exists in the right state, use ensemble docking with MD-generated receptor conformations, or explicitly acknowledge the apo-state limitation when reporting docking results. Always state in your methods whether your receptor was an AlphaFold apo model and what conformational states are known.
06
High
Skipping stereochemical quality assessment

AlphaFold models can contain geometric imperfections — non-ideal bond lengths and angles, Ramachandran outliers, steric clashes — especially in lower-confidence loop regions. These are not caught by looking at pLDDT. A region with pLDDT 75 can have a Ramachandran outlier; a region with pLDDT 85 can have a steric clash introduced during the prediction. These problems affect docking (incorrect binding site geometry), MD (simulation crashes or artifacts), and the credibility of any published structural figure.

The fix
Run every AlphaFold structure through MolProbity (molprobity.biochem.duke.edu) before any downstream use. Fix Ramachandran outliers in the binding site region. Run energy minimization before docking or MD to resolve steric clashes. Report MolProbity clashscore and Ramachandran statistics in your methods section — reviewers increasingly check for this explicitly when AlphaFold structures are used.
07
High
Using ipTM as proof of protein-protein interaction

AlphaFold-Multimer’s ipTM score measures confidence in the predicted interface geometry — not whether the proteins actually interact in biology. A high ipTM (above 0.75) means AlphaFold is confident about the predicted complex structure, given that the proteins are bound. It says nothing about whether they bind, with what affinity, under what conditions, or in which cellular context.

Conversely, a low ipTM does not prove the proteins don’t interact — they may bind transiently, weakly, or in a conformation AlphaFold couldn’t predict from sequence alone. Both directions of the misinterpretation appear in published papers.

The fix
Report ipTM as a structural confidence metric, not as interaction evidence. State clearly: “AlphaFold-Multimer predicted a complex with ipTM = 0.82, suggesting a high-confidence binding interface at [description].” Do not write “AlphaFold-Multimer confirms these proteins interact.” Interaction evidence requires biochemical or biophysical data: co-immunoprecipitation, pulldown, SPR, ITC, FRET, or other direct binding assays.
08
Medium
Not reporting confidence metrics in the methods section

Using an AlphaFold structure without reporting the pLDDT of the relevant regions in the methods section is the structural biology equivalent of using an antibody without citing its validation — it makes the work unreproducible and unverifiable. Reviewers at Nature, Science, PNAS, JACS, and most field-specific journals now routinely ask for pLDDT values, and increasingly for PAE information, when AlphaFold structures are used in docking, MD, or structure-function analysis.

This mistake doesn’t invalidate the science — but it triggers revision requests and signals to reviewers that the quality assessment was not performed rigorously.

The fix
Include in every AlphaFold methods statement: the AFDB version and model version used, the mean pLDDT of the binding site or region of interest, a statement about PAE for multi-domain proteins, which regions were excluded due to low confidence, and what quality checks were performed (MolProbity scores). A complete two-sentence statement covers all of this and takes five minutes to write.

Quick reference: all 8 mistakes

MistakeSeverityCore fix
Trusting low-pLDDT regionsCriticalColor by pLDDT; exclude residues < 70 from structural conclusions
Ignoring PAE for multi-domain proteinsCriticalCheck inter-domain PAE in JSON before analyzing domain interfaces
Conflating confidence with accuracyCriticalUse pLDDT as a filter, not proof of accuracy; validate against experiment
Docking into low-confidence sitesCriticalCalculate mean binding site pLDDT; require > 70 before docking
Ignoring apo conformationHighCheck if target changes conformation on binding; use relevant-state template
Skipping quality assessmentHighRun MolProbity on every AlphaFold structure before downstream use
Using ipTM as interaction proofHighipTM = structural confidence, not biological interaction evidence
Not reporting confidence metricsMediumInclude pLDDT, PAE assessment, and MolProbity scores in methods section
The pattern behind most of these mistakes
Six of the eight mistakes above are silent — AlphaFold generates a structure, the downstream tool runs successfully, and the results look plausible. Nothing signals that the analysis was built on uncertain coordinates. The only defense is systematic checking: pLDDT, PAE, stereochemical validation, conformation state awareness, and transparent reporting. Researchers who make these checks before every AlphaFold-based analysis are the ones whose papers pass review without revision requests on structural methodology.

The short version

AlphaFold is extraordinarily powerful — but only if used correctly. The most consequential mistakes all share a common cause: treating the predicted structure as if it were a crystal structure, with known accuracy, in the relevant conformation, with all regions equally reliable. It is none of those things. Check pLDDT before every analysis. Check PAE for every multi-domain protein. Validate confidence against experiment. Report all of it in your methods. These habits take minutes to develop and prevent the mistakes that cost months of revision.

Last updated on

Similar Posts

Leave a Reply

Your email address will not be published. Required fields are marked *