# PDB vs mmCIF vs PDBQT structure file formats

> PDB, PDBx/mmCIF and PDBQT all store 3D coordinates in ångströms, yet moving a complex between them drops numbering, bond orders, hydrogens or whole ligands. We measured how 30.7% of 2026 PDB entries already lack a legacy .pdb file, and followed EGFR bound to erlotinib (1M17) across mmCIF, PDB, PDBQT and MOL2.

## What is the difference between PDB, mmCIF and PDBQT?

PDB, PDBx/mmCIF (`.cif`) and PDBQT all store 3D atomic coordinates in ångströms, yet each serves a different job. PDB is the fixed-column archive format frozen in 2012, mmCIF is the Protein Data Bank's table format, and PDBQT is AutoDock's docking input format with partial charges, atom types and rotatable bonds. The [PDB viewer](/app/pdb-viewer) opens all three in the browser.

Many pipelines treat `.pdb` as universal and assume mmCIF matters only for giant ribosomes. In our query of the RCSB PDB Search API on November 19, 2026, **30.7%** of structures released in 2026 (5,013 of 16,347) have no `.pdb` file, and only 506 pass 99,999 atoms or 62 chains. Most are small X-ray complexes like WRN helicase (`10AJ`, 3,424 atoms) whose five-character ligand (`A1C4J`) cannot fit in three PDB columns.

Even when a structure fits every format, converting between them silently drops data. PDB loses dual numbering and bond orders, PDBQT removes nonpolar hydrogens and all bond records, and small-molecule formats such as MOL2 and [SDF](/guides/sdf-file) keep ligand chemistry while leaving out polymer chains and experimental metadata.

## How the PDB file format works and where it breaks

The PDB file format defines every field by character column inside an 80-character line, a punch-card layout frozen at version 3.30 on November 21, 2012. Because columns never move, anyone can read coordinates in a text editor, as [opening a PDB file](/guides/open-pdb-file) walks through column by column.

That fixed grid breaks quietly on ordinary proteins. Look at atom 1 of the EGFR kinase domain bound to erlotinib, PDB entry `1M17`:
```text
ATOM      1  N   GLY A 672      55.000   8.448  68.519  1.00101.99           N
```
Columns 55 to 60 hold occupancy (`1.00`) and columns 61 to 66 hold the B-factor (`101.99`). Because `101.99` fills all six characters, the two fields touch as `1.00101.99` with no space between them. That happens on 347 lines of `1M17.pdb`, so any script that splits PDB lines on whitespace breaks on the very first atom.

Those fixed widths also impose hard ceilings:

- Atom serials span columns 7 to 11, capping a model at 99,999 atoms.
- Chain IDs occupy column 22 alone, capping a file at 62 single-character names (A to Z, a to z, 0 to 9).
- Residue and ligand codes span columns 18 to 20, capping names at three characters.
- Residue numbers span columns 23 to 26 (`-999` to `9,999`), coordinates span eight characters (`-999.999` to `9999.999` Å), and B-factors stop at `999.99`.

Bond chemistry is missing too. `CONECT` lines list only bonded atom serials, with no column for single, double, triple or aromatic order. In `1M17.pdb`, erlotinib's terminal alkyne (`C1` to `C2`, 1.202 Å apart) reads `CONECT 2513 2514`, identical to a single bond.

Metadata fares little better. Resolution, missing loops (`REMARK 465`) and biological assembly transforms live in free-text `REMARK` blocks, and structure predictors reuse the B-factor column for [pLDDT](/guides/plddt) confidence instead of atomic mobility.

## Why mmCIF replaced PDB in the archive

PDBx/mmCIF replaces fixed columns with self-describing STAR tables: `data_` blocks, `category.item` names and whitespace-separated `loop_` rows. Every column's meaning sits above the table, so fields never collide and no counter has a width cap. Its full syntax and how it differs from small-molecule crystal files are covered in [small-molecule CIF and mmCIF](/guides/cif-file).

Here is atom 1 of EGFR in `1M17.cif`:
```text
ATOM   1    N N   . GLY A 1 7   ? 55.000  8.448   68.519 1.00 101.99 ? 672 GLY A N   1
```
Occupancy (`1.00`) and B-factor (`101.99`) sit cleanly apart, and the residue carries two numbers: `label_seq_id` is `7` along the 333-residue crystallized construct (residues 1 to 6 are disordered), while `auth_seq_id` is `672` in full-length human EGFR.

Categories above `atom_site` hold the complete sequence (`_entity_poly`), biological assembly matrices (`_pdbx_struct_assembly`) and Chemical Component Dictionary links (`_chem_comp`). For `1M17`, that dictionary defines erlotinib (`AQ4`) with `C1` to `C2` explicitly marked `TRIP` (triple bond).

The wwPDB made PDBx/mmCIF the archive standard in 2014 and mandatory for crystallographic depositions in 2019. Across the whole [Protein Data Bank archive](/guides/rcsb-statistics), 17,318 of 263,567 experimental entries (6.6%) lacked a `.pdb` file on November 19, 2026. That overall figure hides how fast new releases shifted once five-character ligand codes began in December 2023 (Figure 1).

![Line chart comparing the share of newly released PDB entries with no legacy PDB file from 2015 to 2026 across X-ray crystallography, cryo-EM and all releases. Cryo-EM stays between 11.4 and 25.6 percent through 2026, while X-ray stays between 0.3 and 5.0 percent through 2023 before jumping to 15.7 percent in 2024, 35.4 percent in 2025 and 36.0 percent in 2026, pulling all releases to 30.7 percent.](/images/charts/pdb-mmcif-only-releases.webp "**Figure 1. Share of newly released PDB entries with no legacy PDB file, 2015 to 2026.** Current experimental entries in the RCSB PDB Search API with `pdbx_database_status.pdb_format_compatible` equal to `N`, grouped by initial release year (2026 covers January 1 through November 19, 2026). Our count from the RCSB Search API.")

From 2015 through 2023, cryo-EM led the mmCIF-only share (11.4% to 25.6%) while X-ray stayed at 0.3% to 5.0%. After three-character ligand codes ran out in late 2023, X-ray passed cryo-EM, climbing to 15.7% in 2024, 35.4% in 2025 and **36.0%** in 2026 (3,244 of 9,003 X-ray entries). Only 10 of those 3,244 X-ray entries exceed 99,999 atoms or 62 chains.

Forcing one of those entries into `.pdb` breaks its identifiers. When we converted `10AJ.cif` (WRN helicase with ligand `A1C4J`) to PDB with `gemmi`, `A1C4J` silently truncated to `A1C`, severing its dictionary link, and chain `A` fused with residue `1002` into `A1002`. On July 21, 2027, extended 12-character IDs such as `pdb_1000xxxx` end legacy `.pdb` files for all new depositions.

Co-folding predictors such as [Boltz-2](/app/boltz-2), [Protenix](/app/protenix) and [OpenFold3](/app/openfold-3) also write mmCIF natively. For huge assemblies, RCSB serves BinaryCIF (`.bcif`), a binary encoding of the same data model. On the 237,685-atom human 80S ribosome (`4V6X`), `4V6X.bcif.gz` is 3.02 MB versus 5.69 MB for `4V6X.cif.gz`; on small `1M17`, gzipped sizes are close (55.8 KB BinaryCIF, 59.7 KB PDB, 79.9 KB mmCIF).

## What PDBQT changes for molecular docking

A [PDBQT file](/guides/pdbqt-file) keeps PDB columns 1 to 66, then overwrites columns 67 to 76 with a partial charge (`Q`) and columns 78 to 79 with an AutoDock atom type (`T`), such as `A` for aromatic carbon, `OA` for acceptor oxygen and `HD` for donor hydrogen. The AutoDock Vina FAQ notes plainly that PDBQT is not a standard structure format.

Three alterations turn PDBQT into a one-way docking input rather than an archive format:

- Nonpolar hydrogens are merged into their parent carbons, leaving only polar hydrogens (`HD` on N, O or S). For erlotinib (`C22H23N3O4`), 22 of 23 hydrogens vanish, leaving 29 heavy atoms plus 1 aniline NH hydrogen.
- Bond records disappear completely. AutoDock neither reads nor writes `CONECT` lines, and receptor and ligand must sit in separate files (plus a `BEGIN_RES`/`END_RES` file for flexible side chains).
- Ligand atoms are reordered into a `ROOT`/`ENDROOT` and nested `BRANCH`/`ENDBRANCH` torsion tree, ending with `TORSDOF` for rotatable bonds.

Those fields affect docking differently than they appear. Vina ignores user-supplied partial charges in its default scoring function (AutoDock4 uses them), yet missing polar hydrogens or altered torsion trees shift scores materially. Because PDB has no bond orders, Vina's docs warn against preparing ligands from `.pdb`: start from a protonated 3D SDF or MOL2, and keep in mind that a [docking score is not a binding affinity](/guides/docking-score-binding-energy-affinity).

## Where MOL2 and chemical formats fit

Tripos MOL2 sits between coordinate-only PDB files and cheminformatics connection tables. Built for SYBYL, it divides each molecule into tagged ASCII blocks (`@MOLECULE`, `@ATOM`, `@BOND`). Each atom stores 3D coordinates, a SYBYL atom type (`C.1` alkyne, `C.ar` aromatic, `N.am` amide, `O.co2` carboxylate) and a partial charge in column 9, with the charge method named in the header.

Unlike PDB and PDBQT, MOL2 writes explicit bond types (`1`, `2`, `3`, `ar`, `am`), so erlotinib's alkyne survives as `C.1` atoms joined by bond `3`. That suits force-field setup (AMBER Antechamber) and docking suites such as DOCK 6 and GOLD, and [PDB to MOL2](/app/pdb-to-mol2) writes SYBYL types from coordinate ligands.

The catch is that standard MOL2 has no formal-charge column and no polymer entity metadata. Parsers infer formal charges from atom types such as `N.4` or `O.co2` and bond valences, and toolkits often disagree on protonated heterocycles. SDF is safer for storing 3D small molecules because it records explicit bond orders and formal charges; [GNINA](/app/gnina) and [DiffDock](/app/diff-dock) read SDF directly without PDBQT conversion.

Two neighbouring format families handle tasks outside 3D coordinates. Line notations such as [SMILES](/guides/smiles-notation) (including canonical SMILES and SELFIES) and [InChI or InChIKey](/guides/inchi-inchikey-smiles-cas) drop coordinates for tables and database lookup, as compared across [chemical file formats](/guides/chemical-file-formats). On the visualization side, `.pse` and `.pml` files ([PyMOL file types](/guides/pymol-file-types)) save viewer scenes and scripts rather than portable coordinates.

## One complex across four structure formats

Entry `1M17` is the 2.6 Å crystal structure of the human EGFR kinase domain bound to erlotinib (`AQ4`, `C22H23N3O4`, 29 heavy atoms, 23 hydrogens and 10 rotatable bonds). Figure 2 lines up protein atom 1 (`Gly 672 N`) and erlotinib's terminal alkyne (`C1` to `C2`) across mmCIF, PDB, PDBQT and MOL2.

![Diagram comparing human EGFR bound to erlotinib (1M17) across four structure formats: PDBx/mmCIF with space-separated tokens, dual label 7 and auth 672 numbering and CCD triple bond TRIP; legacy PDB with fixed 80 columns, glued 1.00101.99 occupancy and B-factor, serial shifted plus one by TER and bond-orderless CONECT 2513 2514; PDBQT with columns 67 to 79 overwritten by partial charge Q and AutoDock type T, 22 of 23 ligand hydrogens merged away and a ten-torsion ROOT/BRANCH tree; and Tripos MOL2 with C.1 atom types, explicit bond order 3 and all 52 atoms but no formal-charge column.](/images/guides/pdb-vs-mmcif-vs-pdbqt/1m17-four-formats.webp "**Figure 2. Human EGFR kinase with erlotinib (1M17) across four structure formats.** Protein atom 1 (Gly 672 N) and erlotinib alkyne atom C1 (1.202 Å to C2) from `1M17.cif`, `1M17.pdb`, the RCSB Chemical Component Dictionary (`AQ4`) and RDKit Gasteiger partial charges. Field bar widths are schematic; record text and atom counts are real.")

Even atom serial numbers diverge on the same complex: `1M17.pdb` gives serial `2512` to the chain `A` `TER` line, so erlotinib's `C1` is atom `2513` in PDB and `_atom_site.id` `2512` in mmCIF. Moving down the figure, each downstream export preserves coordinates while trading away a different layer of chemistry or metadata. Table 1 puts those trade-offs side by side.

  <caption><strong>Table 1. Technical comparison of PDB, PDBx/mmCIF, PDBQT and Tripos MOL2.</strong> Specifications from wwPDB PDB format 3.30, Westbrook et al. (2022), AutoDock 4.2.6 user guide and Tripos MOL2 (SYBYL 7.1).</caption>
  <thead>
    <tr>
      <th scope="col">Property</th>
      <th scope="col">PDB (`.pdb`)</th>
      <th scope="col">PDBx/mmCIF (`.cif`)</th>
      <th scope="col">PDBQT (`.pdbqt`)</th>
      <th scope="col">Tripos MOL2 (`.mol2`)</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td>Size and ID limits</td>
      <td>99,999 atoms, 62 chains, 3-char ligands, 4-char PDB IDs</td>
      <td>No atom, chain, ligand-code or ID length limit</td>
      <td>Inherits PDB column caps; separate receptor and ligand files</td>
      <td>No fixed atom limit; designed for small molecules</td>
    </tr>
    <tr>
      <td>Field layout</td>
      <td>Fixed 80-character columns; values can touch</td>
      <td>Whitespace-separated named `loop_` tables</td>
      <td>Fixed PDB columns 1 to 66, plus `Q` (67 to 76) and `T` (78 to 79)</td>
      <td>Tagged `@&lt;TRIPOS&gt;` sections, whitespace-separated</td>
    </tr>
    <tr>
      <td>Bond orders</td>
      <td>None; `CONECT` lists bonded pairs only</td>
      <td>Explicit for ligands via CCD (`_chem_comp_bond`)</td>
      <td>None; `CONECT` ignored and omitted</td>
      <td>Explicit (`1`, `2`, `3`, `ar`, `am`)</td>
    </tr>
    <tr>
      <td>Hydrogens and charges</td>
      <td>Usually omitted in X-ray; 2-char formal charge column</td>
      <td>Explicit when modelled; `_atom_site.pdbx_formal_charge`</td>
      <td>Polar H (`HD`) only; per-atom partial charge `Q`</td>
      <td>Usually all H; partial charge column, no formal-charge column</td>
    </tr>
    <tr>
      <td>Macromolecular metadata</td>
      <td>Free-text `REMARK`; author numbering only</td>
      <td>Structured entities, assemblies, `label_` and `auth_` numbering</td>
      <td>None; `ROOT`/`BRANCH`/`TORSDOF` torsion tree instead</td>
      <td>Substructure IDs only; no entity or assembly tables</td>
    </tr>
    <tr>
      <td>Typical software</td>
      <td>Legacy MD, older scripts, all viewers</td>
      <td>RCSB PDB, Mol*, PyMOL, ChimeraX, Boltz-2, gemmi</td>
      <td>AutoDock4, AutoDock Vina, Meeko</td>
      <td>Antechamber/AMBER, DOCK 6, GOLD, Open Babel</td>
    </tr>
  </tbody>

## Which structure format should you use?

Match the file to the stage of your pipeline rather than defaulting to `.pdb`. Table 2 lists the right starting format for each task, its blind spot and the check that catches problems before a run.

  <caption><strong>Table 2. Choosing a structure file format by task.</strong> Recommended starting format, main blind spot and cheap check before running downstream software.</caption>
  <thead>
    <tr>
      <th scope="col">Task</th>
      <th scope="col">Start with</th>
      <th scope="col">What it cannot carry</th>
      <th scope="col">Check first</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td>Download an archive structure, view in 3D or save a prediction</td>
      <td>PDBx/mmCIF (or BinaryCIF for large assemblies)</td>
      <td>Nothing from the archive; older scripts may lack an mmCIF parser</td>
      <td>Whether your tool reads `auth_seq_id` or `label_seq_id`</td>
    </tr>
    <tr>
      <td>Feed a legacy MD setup or script that insists on `.pdb`</td>
      <td>PDB exported from mmCIF</td>
      <td>Entity tables, `label_` numbering, >99,999 atoms, >62 chains, 5-char ligands</td>
      <td>No truncated ligand codes, missing loops or glued `1.00101.99` columns</td>
    </tr>
    <tr>
      <td>Dock a small molecule in AutoDock Vina</td>
      <td>PDBQT (receptor from repaired mmCIF/PDB; ligand from 3D SDF)</td>
      <td>Bond orders and nonpolar hydrogens</td>
      <td>Polar hydrogens (`HD`), protonation state and `TORSDOF` count</td>
    </tr>
    <tr>
      <td>Set up small-molecule force-field parameters or SYBYL docking</td>
      <td>MOL2 alongside a 3D SDF</td>
      <td>Explicit formal charges and polymer entity metadata</td>
      <td>Inferred formal charges on amines, carboxylates and heterocycles</td>
    </tr>
    <tr>
      <td>Archive docked poses or a full complex for reuse</td>
      <td>mmCIF for the protein, 3D SDF for the ligand</td>
      <td>Vina's torsion tree (regenerate from SDF when re-docking)</td>
      <td>Bond orders and stereochemistry survived export from PDBQT</td>
    </tr>
  </tbody>

Keep two source-of-truth files for every complex: the archive mmCIF for the macromolecule and a protonated 3D SDF for the ligand. Treat `.pdb`, `.pdbqt` and `.mol2` as disposable exports generated right before the program that demands them, repairing missing loops with [PDBFixer](/app/pdb-fixer) and receptor hydrogens with [PDB2PQR](/app/pdb2pqr) before docking.

## Structure file tools on ProteinIQ

Fetch and inspect the archive structure first, repair missing atoms or protonation second, and convert to docking or cheminformatics formats last.

- [PDB viewer](/app/pdb-viewer): inspect PDB, mmCIF, PDBQT, MOL2 and SDF files together in the browser
- [PDB download](/app/pdb-download): fetch archive mmCIF or legacy PDB files by accession
- [PDB to CIF](/app/pdb-to-cif): convert legacy PDB files to mmCIF locally without uploading
- [PDBFixer](/app/pdb-fixer): rebuild missing residues and atoms before simulation or [molecular docking](/use-cases/molecular-docking)
- [SDF to PDBQT](/app/sdf-to-pdbqt) and [PDBQT to SDF](/app/pdbqt-to-sdf): prepare ligands for [AutoDock Vina](/app/autodock-vina) and export docked poses back to SDF
- [Open Babel](/app/open-babel): convert between mmCIF, PDB, MOL2, SDF and PDBQT when a tool expects another format

## Frequently asked questions

### What is the difference between PDB and CIF files?

PDB is a frozen fixed-column format capped at 99,999 atoms, 62 chains and three-character ligand codes. PDBx/mmCIF (`.cif`) stores the same 3D coordinates in whitespace-separated named tables with no size caps, dual `label_` and `auth_` numbering and Chemical Component Dictionary bond definitions.

### Why do some PDB entries have no legacy PDB file?

The wwPDB omits legacy `.pdb` files when an entry passes any fixed-column ceiling: more than 99,999 atoms, more than 62 chains, multi-character chain IDs, B-factors above 999.99 or five-character ligand codes. In 2026 through November 19, 30.7% of new releases (5,013 of 16,347) lacked a `.pdb` file, and from July 21, 2027 all new entries will be mmCIF-only.

### Can I convert mmCIF to PDB without losing data?

Not without losing metadata. When a structure fits under 99,999 atoms, 62 single-character chains and three-character residue codes, `gemmi` or [Open Babel](/app/open-babel) keeps coordinates and author numbering while dropping entity tables, `label_` numbering and assembly matrices. Above those limits, conversion fails or truncates identifiers so they no longer match the archive.

### What is the difference between PDB and PDBQT?

PDBQT keeps PDB columns 1 to 66, writes a partial charge (`Q`) and AutoDock atom type (`T`) into columns 67 to 79, merges away nonpolar hydrogens, drops `CONECT` records and reorders ligand atoms into a `ROOT`/`BRANCH`/`TORSDOF` torsion tree. PDB is a general coordinate file; PDBQT is an input and output format built specifically for AutoDock and AutoDock Vina.

### When should I use a MOL2 file instead of PDB or SDF?

Use Tripos MOL2 when software expects hybridization-aware SYBYL atom types (such as `C.1` or `C.ar`) and partial charges alongside explicit bond orders, as in AMBER Antechamber, DOCK 6 and GOLD. Because standard MOL2 has no formal-charge column, keep a 3D SDF as your primary small-molecule file and export MOL2 when needed.
