RFantibody icon

RFantibody

(8fe3114)

Design antibody and nanobody binders with an end-to-end RosettaCommons pipeline Learn more

Input

Inputs

Settings

0 credits

Output

Configure inputs to begin

Set options on the left, then click “Submit job” — or start from an example.

Influenza HA nanobody CDR design

What is RFantibody?

RFantibody is a structure-guided antibody and nanobody design pipeline built around an antibody-tuned version of RFdiffusion. It generates new CDR-mediated binding geometries against a chosen epitope, designs compatible loop sequences, and then filters the resulting complexes with an antibody-tuned RoseTTAFold2 model.

The method was introduced as a route to de novo, epitope-specific antibody design from structural input rather than immunization or random library discovery. In the published workflow, the computational design stage is followed by experimental screening, because the model can generate structurally accurate binders but still requires broad sampling to recover the strongest candidates.

How to use RFantibody online

ProteinIQ runs RFantibody on hosted GPU infrastructure, so the full three-stage pipeline can be launched from the browser without installing RosettaCommons dependencies locally.

The online interface accepts one target structure and one antibody or nanobody framework. The target can be uploaded as a PDB/ENT file or fetched from the RCSB. The framework must already be prepared in RFantibody's HLT format.

Inputs

InputDescription
Target antigen structureAntigen PDB or ENT structure, uploaded directly or fetched from the RCSB by PDB ID. Runtime and memory increase approximately quadratically with target size. For targets above about 500 residues, consider retaining the complete local secondary structure and roughly 10 Å around the intended epitope while avoiding unnecessary chain breaks.
HLT antibody frameworkAntibody or nanobody framework PDB in RFantibody HLT format. This is not a generic antibody structure file; it must use RFantibody chain conventions and CDR loop remarks.

HLT framework requirements

RequirementDescription
Heavy chainMust use chain ID H. For nanobodies, the single variable domain is treated as the heavy chain framework.
Light chainIf present, must use chain ID L. Nanobody frameworks omit this chain.
Chain orderProtein chains should appear in H then L order. In full HLT complexes, target chains are represented as T.
Loop remarksThe file must end with REMARK PDBinfo-LABEL annotations that mark the absolute residue indices of the CDR loops, for example REMARK PDBinfo-LABEL: 32 H1.
Accepted examplesnative example frameworks include the nanobody file h-NbBCII10.pdb and the antibody Fv file hu-4D5-8_Fv.pdb.

Generic antibody PDB files usually do not include those loop remarks or chain conventions. In the native RFantibody workflow, such structures are converted to HLT format before design.

Design settings

SettingDescription
Backbone designsNumber of backbone dock designs to generate in the RFdiffusion stage (1-10, default 10).
Sequences per backboneNumber of ProteinMPNN sequence variants to sample for each designed backbone (1-8, default 1).
Sequence temperatureProteinMPNN sampling temperature (0.1-1.0, default 0.1). Lower values bias toward more conservative loop sequences.
RF2 recyclesNumber of RoseTTAFold2 recycling iterations used during filtering (1-20, default 10).
Deterministic modeRequests deterministic sampling where supported, useful for reproducible pilot runs.

CDR loop ranges

SettingDescription
Design H1/H2/H3Toggles for heavy-chain CDR loop design. Enabled by default, matching H1:,H2:,H3: behavior.
H1/H2/H3 lengthOptional heavy-chain CDR length or length range, such as 7 or 5-8. Leave blank to design that loop at the native framework length.
Design L1/L2/L3Toggles for light-chain CDR loop design. Enabled by default; native skips these loops for nanobody frameworks without chain L.
L1/L2/L3 lengthOptional light-chain CDR length or length range for antibody frameworks. Leave blank to design the loop at the native framework length.

At least one loop must be enabled. To keep a loop fixed, turn off its design toggle. A blank length on an enabled loop does not skip the loop; it uses the native length syntax such as H1:.

Targeting

SettingDescription
Hotspot residuesComma-separated antigen residues such as B146,B170,B177. These residues bias the model toward a particular epitope. Bad hotspot definitions can produce undocked designs, so small pilot runs are usually preferable before scaling up.

Advanced settings

SettingDescription
Diffusion timestepsRFdiffusion denoising steps passed as --diffuser-t (default 50).
Final diffusion stepFinal RFdiffusion step passed as --final-step (default 1).
Omitted amino acidsProteinMPNN --omit-aas value (default CX).
ProteinMPNN noiseOptional ProteinMPNN --augment-eps coordinate noise. Leave blank to use the command-line default.
RF2 hotspot visibilityFraction of hotspot residues shown to RF2 during filtering (default 0.1).
RF2 random seedOptional RF2 seed. Leave blank for stochastic RF2, or enable deterministic mode to use seed 42.

Outputs

OutputDescription
Designed complexesFinal antibody-antigen or nanobody-antigen complexes in PDB format.
RFdiffusion score file.sc targeting table returned for hotspot-guided runs. mindist is the minimum hotspot-to-designed-loop Cβ distance, and averagemin is the mean nearest distance across hotspots; both are reported in Å.
Final score file.sc score table exported from the final RF2 quiver output. It includes interaction PAE, mean PAE, mean pLDDT, and Cα RMSD metrics in RFantibody's order.
Stage quiver filesRFdiffusion, ProteinMPNN, and RF2 quiver files for downstream inspection.
File tableDownloadable list of all generated design files.
Run logCurated campaign record with target size, selected-loop and hotspot counts, requested and produced candidates, and completed scientific phases. Budget-limited runs retain the same safe record.

How does RFantibody work?

RFantibody runs three design stages in sequence.

Antibody-tuned RFdiffusion

The first stage places a chosen framework against the target and redesigns the selected CDR loops. Rather than generating an arbitrary binder scaffold from scratch, this stage treats the framework as fixed context and focuses the generative step on loop-mediated docking and backbone creation around the target epitope.

ProteinMPNN sequence design

Once loop backbones have been generated, ProteinMPNN samples amino acid sequences compatible with each designed structure. In RFantibody, this step is used to populate the redesigned loops while preserving the broader framework context.

Antibody-tuned RF2 filtering

The final stage predicts the structures of the designed sequences in complex with the target and scores whether the intended interface appears self-consistent. This filtering stage is important because antibody design campaigns generally require broad sampling, and only a subset of computational designs retain the desired dock after structure prediction.

Interpreting results

RFantibody output is best treated as a candidate set rather than a final answer. Structural inspection still matters: plausible designs should maintain a well-packed interface, avoid obvious clashes, and keep the framework geometry reasonable outside the redesigned loops.

RFantibody's guidance recommends filtering designs with strong RF2 confidence and low disagreement between the design model and the RF2-predicted complex. In practice, RF2 pAE below roughly 10 Å and design-versus-prediction Cα RMSD below roughly 2 Å are used as minimal screening criteria before downstream experimental work or more detailed physics-based evaluation. For hotspot-guided runs, smaller mindist and averagemin values indicate that the generated CDR geometry landed closer to the requested epitope. Candidate numbers record generation order; they are not a score-based ranking.

Applications

  • Epitope-specific nanobody design: Generating VHH binders against structurally defined target surfaces.
  • Antibody variable-domain design: Designing scFv-like variable regions with both heavy- and light-chain CDR participation.
  • Targeted campaign exploration: Running pilot campaigns to compare hotspot definitions, loop ranges, or framework choices before large-scale screening.

Table of contents

Related tools

Proteo-R1

Proteo-R1

Exploratory antibody CDR co-design for antibody-antigen complexes using Proteo-R1 reasoning and raw diffusion. The standard online workflow does not include the framework structure-inpainting assets required for the published-quality target.

protein-designai-powered+5
BioPhi

BioPhi

Antibody humanization and humanness evaluation platform from Merck. Sapiens mode uses deep learning trained on the Observed Antibody Space (OAS) to humanize antibody sequences, while OASis mode evaluates humanness using 9-mer peptide search against human antibody databases.

sequence-designai-powered+3
BoltzGen

BoltzGen

BoltzGen uses generative diffusion models to design protein, peptide, nanobody, and Fab binders against protein and small-molecule targets.

binder-designai-powered+5
CoSiNE

CoSiNE

Simulate antibody affinity maturation, steer heavy-chain evolution with SARS-CoV binding predictors, constrain mutations to CDR or framework regions, and score paired-antibody variants with CoSiNE likelihoods and optional somatic-hypermutation correction.

sequence-designai-powered+3
DiffAb

DiffAb

AI-powered antibody CDR design using equivariant diffusion models. Generates complementarity-determining region (CDR) sequences and structures for antibody structures and antibody-antigen complexes. Supports single- and multi-CDR co-design, antibody optimization, fixed-backbone sequence design, and structure prediction.

protein-designdiffusion-model+5
PepMimic

PepMimic

PepMimic designs short peptides that mimic the binding interface of a known protein binder on its target. From a reference protein complex, a latent diffusion model generates peptide candidates constrained to the target interface, and each candidate is scored by interface-mimicry against the reference binder.

binder-designai-powered+4
Proteina-Complexa

Proteina-Complexa

Design protein binders against a target structure with NVIDIA BioNeMo's Proteina-Complexa generative pipeline.

binder-designprotein+3
PepMLM

PepMLM

Design linear peptide binders for target proteins using a target sequence-conditioned masked language model. PepMLM generates peptide sequences optimized to bind specific protein targets based on ESM-2 protein language modeling.

binder-designai-powered+5
EvoDiff

EvoDiff

EvoDiff is a diffusion-based protein sequence generation framework from Microsoft Research. ProteinIQ currently runs the EvoDiff-Seq OA_DM_38M model for unconditional protein generation, motif scaffolding, and user-sequence inpainting.

protein-designai-powered+3
Genie 3

Genie 3

Generate protein structures and scaffolds with Genie 3, an all-atom SE(3)-equivariant diffusion model. Genie 3 supports unconditional protein generation, motif scaffolding, and hotspot-targeted binder design.

protein-designdiffusion-model+5

Input

Inputs

Settings

0 credits

Output

Configure inputs to begin

Set options on the left, then click “Submit job” — or start from an example.

Influenza HA nanobody CDR design