jnar — Journal of Negative & Applied Results

Technique hub

Flow cytometry protocols — versioned, with troubleshooting and fixes.

Flow cytometry measures markers on single cells one at a time. Most failures cluster in a few places: no or few events from fluidics and sample issues, high background from missing Fc block or dead cells, spillover spread that no amount of compensation can fix, and gating that drifts run to run. The flow cytometry protocols below keep those fixes visible — version by version.

Versioned & attributed protocols
Negative results recorded inline
Import your own with AI — first free

Step by step

A flow cytometry protocol, with the failure at each step.

The order matters more than any single reagent. For each step, here's what to do — and exactly where it tends to break.

  1. 1

    Prepare a clean single-cell suspension

    Dissociate, filter through 40–70 µm mesh, and count.

    Where this breaks Clumps and debris clog the fluidics and inflate doublets — most “no clean populations” problems start here, not at the cytometer.

  2. 2

    Stain viability before fixation

    Use an amine-reactive live/dead dye on unfixed cells, then wash.

    Where this breaks Dead cells bind antibody nonspecifically and read as false positives; staining viability after fixation kills the signal.

  3. 3

    Block Fc receptors

    Add Fc block to myeloid/B-cell–rich samples before the antibody cocktail.

    Where this breaks Skipping Fc block is the classic source of diffuse high background on CD16/CD32-bearing cells.

  4. 4

    Titrate and apply the surface panel

    Stain with titrated antibody amounts (not the vial’s default) in brilliant-stain buffer if using polymer dyes.

    Where this breaks Over-titre raises background and spillover spread; polymer-dye interactions without the right buffer create artifacts.

  5. 5

    Fix / permeabilize for intracellular targets

    Match the fix/perm kit to the target (transcription factor vs cytokine).

    Where this breaks The wrong perm reagent strips surface epitopes or fails to open the nucleus — intracellular signal vanishes.

  6. 6

    Acquire single-stain compensation controls

    Run single stains (beads or cells) for every fluorochrome, with a matched unstained control.

    Where this breaks Missing or mismatched controls make compensation impossible to compute correctly — the #1 root cause of “spreading” complaints.

  7. 7

    Acquire and gate

    Gate time → singlets (FSC-H vs FSC-A) → live → population of interest, on a consistent template.

    Where this breaks Inconsistent gates between runs are where reproducibility quietly leaks; an unversioned gating strategy can’t be audited.

Troubleshooting

Flow cytometry troubleshooting, grouped by where it fails.

Panel and staining, gating, and compensation fail in different ways. Find the symptom, see the likely cause, apply the fix — then record it in the protocol version so the next person doesn't relive it.

Panel & staining — no / few events, high background
Symptom Likely cause Fix
No events / very few events Clog, empty tube, sheath/sample pressure, or a dead sample Backflush, confirm the tube seats, check sheath levels, and verify viability before blaming the panel.
High diffuse background No Fc block, dead cells, or antibody over-titre Add Fc block, gate out dead cells, and titrate each antibody to its signal/background sweet spot.
Dim or missing positive population Degraded fluorochrome, wrong laser/filter, or under-staining Confirm the configuration detects that dye, protect tandems from light, and re-titrate up.
Gating
Symptom Likely cause Fix
Populations smear / no clean separation Doublets, debris, or no time gate Gate time → singlets (FSC-H vs FSC-A) → live first, before population gates.
Results drift run-to-run Gates redrawn by hand each session Lock a gating template and version it; record why a gate moved when it must.
Rare population disappears Too few events acquired or over-tight gates Acquire enough total events for the target frequency and validate gates on an FMO.
Compensation
Symptom Likely cause Fix
Spillover spread (smear into other channels) Bright dye spreading error — not fixable by more compensation Spread is intrinsic; redesign the panel so the spreading dye avoids your dim markers.
Over- / under-compensated populations Bad single-stain controls or carrier mismatch (beads vs cells) Use the same matrix as the sample, with a matched unstained control, and recompute.
Tandem dye looks wrong across days Tandem degradation / lot variation Compensate with the same lot you stained with, and record the lot in the protocol version.

Living fix history

Every fix stays attached to the protocol.

The reason a panel was re-titrated, the buffer that fixed background, the lot that ruined a tandem — on jnar that knowledge lives in the protocol's version history, not in someone's notebook. Each change records what broke, who fixed it, and why.

  • Panel, gating, and compensation changes tracked as precise diffs
  • Negative results — what didn't work — kept as first-class data
  • ORCID credit to the contributor on every integrated fix
Immunophenotyping · PBMC panel v4
FIX HISTORY
v4
Added Fc block step before cocktail
Cut CD16 background · L. Okafor
v3
Viability dye moved before fixation
Killed false-positive dead cells · M. Costa
v2
Re-titrated CD3 / CD8 down 2×
Reduced spillover spread · S. Haddad
v1
Initial published panel
J. Virtanen
− Stain viability after fixation
+ Stain viability on live cells, then fix

Have a flow cytometry protocol as a PDF?

Turn a methods PDF or doc into a structured, step-by-step protocol — panel, controls, and gating included. The AI drafts it; you edit and publish. Your first conversion is free.

Import a PDF →

FAQ

Flow cytometry troubleshooting, answered.

Why is my flow cytometry showing no cells / no events?

Start at the fluidics and the sample, not the panel. The usual causes are a clogged or unprimed line, a tube that isn’t seating, sheath/sample pressure issues, or a sample that was already dead before staining. Backflush, confirm the tube and pressures, and check viability before re-running the antibody cocktail.

How do I fix high background or spillover spread?

High background is usually missing Fc block, dead cells read as false positives, or antibody over-titre — block, gate out dead cells, and titrate down. Spillover spread is different: it’s an intrinsic spreading error from a bright dye and can’t be removed by adding compensation. The fix is panel design — keep the spreading dye away from your dim markers.

What causes compensation problems?

Almost always the controls. You need a single-stain control for every fluorochrome, a matched unstained control, and the same carrier as your sample (beads vs cells must match). Tandem dyes also drift by lot and over time, so compensate with the lot you actually stained with — and record that lot in the protocol version.

What's a reproducible flow cytometry gating strategy?

A gating strategy is reproducible when it’s fixed and auditable: gate time → singlets (FSC-H vs FSC-A) → live → population, from a locked template rather than hand-drawn each session. On jnar the gating strategy lives in a versioned protocol, so when a gate moves you can see who changed it and why.

Can I turn a flow cytometry protocol PDF into a structured protocol?

Yes. Import a methods PDF or doc into jnar and the AI drafts a structured, step-by-step protocol you can edit — panel, controls, gating, and all. Your first AI conversion is free. From there it carries a version history and a visible record of every fix.

What's shipped versus on the roadmap here?

Versioned protocols, the visible fix history, precise diffs, convergent contributions, and ORCID attribution are live today. The example panels and fix histories on this page are illustrative. We mark roadmap items as roadmap, never as features we already ship.

Have a flow cytometry method of your own?

Import it into jnar and start recording the fixes. Your first AI conversion is free.

Import a protocol →