Antibody database (beta version)
Setup needed
URL / anon key placeholders not replaced.
Sign in
You'll be the lab admin and get a join code to share with your team.
Ask your lab admin for the code (shown in their Lab panel).
Why use Antibody.CiteZero
Free for academia, and your lab's data stays private.
You control what is shared. Identifiable lab data is never shown to other labs — only anonymised, aggregated results power the cross-lab search. Read our privacy policy.
Your lab's memory, in one place
Antibodies, protocols and experiments in one searchable record — with paper-ready methods text and tables in one click.
Reproducible and publication-ready
RRIDs, lot numbers and exact conditions captured at the bench — a methods section you can defend, and journal / reviewer RRID requirements met without archaeology.
Stop repeating what already failed
Negative results are recorded too, so no one in the lab burns a week re-running a condition that never worked.
Knowledge that outlives the people
See who ran what, and hand a new member a working protocol instead of a folder of files and a departed postdoc's notebook.
As more labs join, you'll also get cross-lab troubleshooting (which conditions failed elsewhere, not just in your lab), validated starting conditions to work from, and evidence-based antibody selection by target and application.
Set a new password
Join a different lab
You'll switch to that lab as a member. Experiments you already saved stay with your current lab.
Find an antibody
Search antibodies your lab has logged — by name or RRID, partial is fine (e.g. “iba” finds “anti-mouse Iba-1”). See prior conditions and pull a lab protocol into the form below. Other labs' data comes in a later version.
Start a new experiment?
Your current entry hasn't been saved.
Import your lab's antibodies and protocols
Not yet supported: photos/scans.
Before you upload — 5 things that make the import work
- Column headers in the first row, in English, one header per column. Headers in another language, or a blank header, can't be matched to a field.
- One antibody per row. Merged cells, or a header split across two rows, won't read correctly.
- Vendor and catalogue number in their own columns. This is how an antibody is identified — without both, rows can't be matched to the shared record or to other labs.
- Dilutions as a ratio —
1:1000, not1 to 1000or1000. Format the column as text in Excel, or it silently converts1:250into a time value. - Several sheets are fine — we read them all. Name them usefully (Primary, secondary, WB, IHC): we use the tab name to tell what's in it. Sheets that aren't antibody lists (protocol steps, supplier lists) are skipped, and we'll tell you which.
Nothing is saved until you review it. Anything we can't read is reported, never guessed.
We read the antibody table and the Methods section: the antibodies get the paper as a reference, and the Methods can become a protocol.
Lab protocols
Your lab's standard protocols (e.g. free-floating 40 µm vs slide-mounted, or brain vs tumor). Pick one per experiment.
Lab protocols are the lab's standard — only an admin edits, deletes or sets them as the default. Anyone can make a personal version (“Copy as mine”), which the whole lab can see but only you can change, and ask an admin to make it lab-wide. Each member can still set their own default for new experiments.
| Name | Applies to | Scope note | Uploaded by | Lab default | Actions |
|---|
Add a protocol
What does your lab use these for?
This records your lab's standard usage — it is not an experiment and isn't shared with other labs. When you later run one of these antibodies, the form pre-fills from here and asks you to score it.
Confirm the paper's reference
The antibodies from this paper will carry this reference in your database, so you can show where a condition was published. The DOI/PMID are read directly from the document; the rest is a suggestion — please correct anything that's wrong. Leave blank if the paper isn't published yet.
Here's what we found — import it?
Nothing has been saved yet. Review this, then import or cancel. If you import, you'll still confirm how each antibody is used on the next screen.
You already have protocols — reuse one, or add new?
Your lab runs the protocols below. If this upload is one you already have, reuse it — no re-extraction, and your experiments link to the existing one. If it's genuinely different, add it as new (name it so it's easy to tell apart). Multiple protocols per application are fine.
Export
Experiment summary (for your lab notebook)
Methods paragraph
Journal-style prose — paste into a manuscript or any ELN.
Table for ELN
Copies as a real table — paste into LabArchives, Benchling, RSpace and other rich-text ELNs. Falls back to tab-separated text.
Lab reagents database
Every non-antibody reagent your lab uses. Rows are pre-filled from your experiments (step + name) — complete vendor, cat #, lot, location and notes, then Save. Visible only to your lab. Anyone can add or edit; only a lab admin can delete (🔒).
| Step | Name | Vendor | Cat # | Lot | Location | Notes |
|---|
Lab antibody database
Antibodies your lab owns or has used. Application, dilution and protocol show how your lab uses each one — a * means that dilution came from an import and has not been scored in the app yet. Click a column header to sort. Identity (name/vendor/cat #/clone) is read-only here — it's a shared cross-lab record; edit it on the experiment form. You can edit location and notes for any, and + Add antibody to register one you own. Only a lab admin can delete (🔒).
| Name | Type | RRID | Application | Dilution | Protocol | Reference | Vendor | Cat # | Clone | Clonality | Conjugate | Host | Stock | Lot | Temp | Freezer | Box/rack | Position | Order link | Notes |
|---|
Experiment *
Links & references (private — visible only to you)
Where the raw data, images, or notebook entry live. Cloud/ELN https links are clickable; local paths are saved as a reference (browsers can't open local files). Never shared, pooled, or licensed.
| Type | URL / path |
|---|
Sample preparation
Fixation / processing (add steps)
| Method | Time | Unit | Temp |
|---|
Cryoprotection (fixed-frozen — before sectioning)
| Agent | Time | Unit | Temp |
|---|
Antigen retrieval (add steps)
| Method | Time | Unit | Temp |
|---|
Blocking (add steps)
| Agent | Time | Unit | Temp |
|---|
Primary antibody
Enter the RRID or at least the name. The RRID autofills the name & details and lets the system cross-reference your troubleshooting against other labs' data — so it's strongly preferred.
Concentrations tested *
| Dilution | Converted | Score | Adopted |
|---|
Secondary antibody
Concentrations tested *
| Dilution | Converted | Score | Adopted |
|---|
Additional antibody pairs (optional)
For multiplex experiments — each extra primary and its paired secondary, with their own concentrations. Sample prep, blocking, the staining pipeline, washes, and controls above are shared across all pairs.
Additional reagents (optional)
Tertiary or amplification reagents. Adding one creates its detail panel here and a step in the staining pipeline below.
Counterstains & labels
Non-antibody stains applied to all samples — DAPI/Hoechst (IF), hematoxylin/H&E (IHC), autofluorescence quenchers, mounting medium. These tend to be constant for a lab: set them once with Save as lab default and they auto-fill new experiments. Stage = when in the protocol they're applied; "wash after" records a wash step immediately after the stain.
Staining pipeline
Ordered steps after blocking. Each incubation can be followed by washes (buffer + conditions + repeats). Use +wash on a row to insert a wash after it.
| Step | Reagent / buffer | Time | Unit | Temp | Repeats |
|---|
Tertiary / amplification reagents (added in the section above) appear here automatically. Use +wash on any row to insert a wash after it.
Controls
| Type | What it was | Behaved? | Signal | n | Relates to |
|---|
Controls are logged, never assumed. Unstained, single-stain/compensation and FMO are the backbone of correct gating — seeded rows below are examples; edit or delete them to match what you actually ran.
| Control | Detail (e.g. which fluorophore) | Behaved? | n |
|---|
FACS sample preparation
How the single-cell / nuclei suspension was prepared before staining.
Dissociation & clean-up
| Mesh |
|---|
Fixation (required for intracellular staining; optional otherwise)
Permeabilization
Detection & panel *
What was measured: an antibody panel, viability/nuclei dyes, and/or endogenous reporters.
Antibody panel
| Marker * | Fluorophore * | Amount (µL/test) * | Compartment |
|---|
Tap ▸ on a marker for clone, vendor, catalog, lot & channel.
Viability dye
| Dye | Channel | Conc. | Fixable |
|---|
Nuclei / DNA dye
| Dye | Channel | Conc. |
|---|
Endogenous reporter
| Reporter | Channel | Note |
|---|
Instrument & gating
Purpose, cytometer, and how the target population was gated.
Outcome
Set each antibody's result. For ones that didn't fully work, tick the suspected cause — its own primary/secondary or a shared condition. Unticked items aren't blamed (not recorded as "working" either); "Don't know" flags it as ambiguous.
Two independent questions: did the experiment succeed (find/sort your population), and did the reagents stain cleanly. A perfect stain can still miss a rare population — and that must never be recorded as an antibody failure.
Reagent/staining quality only — not whether you found your population. This is the per-antibody signal other labs see.
You don't have to know the cause — once there's enough pooled data the system will also suggest whether it's likely the antibody/conditions or the experiment run.
Draft needs only the experiment name + primary RRID/name; offers a calendar reminder.
Lab databases & protocols
My lab's experiments
Click a column header to sort.
| Name | Type | User | Created | Modified | Status |
|---|