Membrane Annotation

Explore protein structure and topology in membrane context.

Target

Advanced options

Use your own target structure or add a binder complex.

Custom target structure
no file chosen
Already a full target–binder complex? Choose its target chain and tick its binder chains here.
Binder complex
Annotate the full receptor above, then add a binder to the existing structure. Paste or upload the binder + target fragment below; the shared target residues align the binder onto the full receptor.
Annotate a topology example to see a matching binder.
no file chosen
Load the full target, then paste or upload a complex to align its binder.
Add a binder to inspect contacts in the current view.
Interaction lines:
Downloads

Session

Session files include your structure and annotations. Opening a session recomputes its assessment.

Browser settings

Public UniProt, AlphaFold and structure downloads are cached locally for 7 days (64 MB maximum), with retrieval time and content hash. Uploaded structures and email addresses are not stored in this cache.

How it works

Learn how topology, membrane placement and result checks work.

Membrane protein topology: the types
The diagrams distinguish α-helical spans from transmembrane β-strands. For helical proteins, topology is described by how many times the chain crosses, which side the N terminus is on, and whether it was made with a cleavable signal peptide. The classical single-pass types follow from them. The type of the protein on screen is outlined in red. Each card links to a human example in UniProt. “Out” includes the lumen of the ER or a vesicle; “in” means cytoplasmic.
Excluded from automatic placement and correction: mixed α/β transmembrane annotations, such as Perforin-2 (MPEG1). They remain available for annotation only; placement needs a topology and structure for the same membrane-inserted state.
TypeSpansN terminusSignal peptideC terminusHow this page decides
I1outyes, cleavedinUniProt "Single-pass type I"; otherwise N out + curated SIGNAL
II1inno (signal anchor)outUniProt "type II"; otherwise N in and the span not at the C terminus
III1outno (reverse signal anchor)inUniProt "type III"; otherwise N out and no SIGNAL
IV1, at the C terminusinnoout (a few residues)UniProt "type IV"; otherwise the span ends within 50 residues of the C terminus, N in
Multi-pass (helical)≥ 2in or outsometimesparity of the span countnumber of curated TRANSMEM segments; N side from the flanking topological domain
β-barrel / poreβ-strands, counted per chainsides from curated topology; the barrel may need several subunitsUniProt TRANSMEM features described as "Beta stranded"
GPI / lipid / peripheral0anchored without crossingUniProt keyword, LIPID feature or subcellular-location topology
What the page reports for every target (the line under the protein's name): the type; which side the N and C termini are on (extracellular / out or cytoplasmic / in); the number of spans and their positions; the signal peptide and its range; re-entrant segments. Every one of these comes from curated UniProt data. UniProt's own statement is reported first; where the page's own derivation disagrees, both are shown. None of it is read from the structure. The signal peptide is drawn in green in the sequence, the domain bar and the 3D view: it is cleaved during biogenesis and is not part of the mature protein.
The workflow, step by step
  1. Input. A UniProt accession loads the AlphaFold model; a PDB ID loads the experimental mmCIF from RCSB and its UniProt entry via SIFTS; an uploaded or pasted structure uses the accession box, if filled, as its topology source.
  2. Class and route. Curated UniProt data decides what kind of membrane protein this is (single-pass type I–IV, multi-pass, GPI, lipid-anchored, peripheral, soluble) and which method handles it. A protein UniProt says is not a membrane protein gets no membrane.
  3. Topology. The curated spans, topological domains and signal peptide are mapped onto the structure's residues by canonical sequence position.
  4. Membrane frame. Our own deterministic solver finds the bilayer normal, centre and thickness: from the curated spans where there are any, otherwise from the hydrophobic surface alone. Without a curated span, a slab is kept only if the residues it exposes to lipid are hydrophobic and uncharged; otherwise no membrane is drawn.
  5. Membrane type, thickness and tilt. The bilayer's hydrophobic thickness depends on the compartment. The page takes the membrane from UniProt's first subcellular location, or from the membrane menu in Colour & display, and uses the OPM average thickness for that membrane (Pogozheva et al. 2013): plasma membrane 33.5 Å, ER 30.2 Å, mitochondrial inner 28.6 Å, bacterial inner 30.2 Å, Gram-positive plasma 31.6 Å. Golgi (32.2 Å) is the ER value plus the ER→Golgi difference measured by Mitra et al. (2004), because OPM has no Golgi average. For a single-spanning protein, a helix of L residues is 1.5·L Å long. If that is longer than the bilayer, the helix is tilted until it fits: cos θ = D / 1.5·L. A 27-residue span tilts 42° in the ER and 34° in the plasma membrane; a 20-residue span stays upright. The direction of the tilt is whichever keeps the soluble domains out of the core. The thickness and tilt are written beside the membrane in the 3D view. Choosing fitted to the structure switches this off.
  6. Placed in membrane. One rigid rotation and translation of every atom puts the membrane horizontal with the outside up. Nothing is refolded.
  7. Corrected. For a single-pass protein whose model puts domains on the wrong side or inside the bilayer: trim the signal peptide and low-confidence termini; turn the connector torsions (articulated motion); if that is not enough, place the domain as a rigid body and close the connector (CCD); put the termini back and swing them clear of the core; relieve low-confidence regions still in the core. Bond lengths and angles are preserved throughout.
  8. Checks. Every model is checked for domains on the wrong side, atoms in the core, contacts across the membrane, spans that do not cross and more, before and after correction.
  9. Outputs. The placed and corrected structures, any selected part (a domain, the signal peptide, a span, a residue range), the annotation record (JSON), a report and the segments (TSV).
What this output does not say
    Additional tools

    Explore molecular context, uncertainty and external reference tools.

    Method and provenance

    Correction and assessment

    Run an annotation to view correction and assessment details.

    Topology evidence

    Run an annotation to view topology evidence and its sources.

    Membrane frame, sign and placement

    Run an annotation to view the membrane frame, sign and placement.

    Surface patches and clearance

    Run an annotation to view surface patches and clearance.

    References

    Each reference states how it is used: browser software, imported data, an implemented method, an optional integration, or context only. These labels describe the webpage's capabilities; the inputs and provenance determine what was used for a particular result.

    Used here: software and data

    These are integrated into the webpage; the selected input and display determine which resources are used.

    Used here: implemented methods

    These references credit methods or parameter values implemented or adapted in the app. They are not all separate software packages.

    Membrane placement, correction and structural-test thresholds are InXBio implementations described in Method and provenance. The cited methods provide their basis; they do not independently validate the resulting coordinates.

    Optional tools and reference imports

    Used when the corresponding prediction, example, file import or local cross-check is requested and available.

    Further context only

    Related resources for comparison, external analysis or downstream work. They do not generate the webpage's browser result.

    Cite Membrane Annotation

    A publication describing InXBio Membrane Annotation is in preparation. We welcome your feedback.

    For publications: report InXBio Membrane Annotation v1, its saved build identifier, input accessions and versions, and the settings used.

    Cite the software, data and methods actually used in your workflow, including any optional tools or imported results; cite context-only resources as related work. For PDB and binder examples, also cite the original structure or dataset.

    Save the assessment and provenance from Downloads to document the run. Software licence notices.