Biological Magnetic Resonance Data Bank

A Repository for Data from NMR Spectroscopy on Proteins, Peptides, Nucleic Acids, and other Biomolecules
Member of WWPDB

BMRB Deposition Systems

For depositing NMR data (not structures) to BMRB:

New, significantly improved, BMRBDep deposition system.

Traditional ADIT-NMR system.

BMRB accepts the following kinds of data:

(Click on the links above for complete listings.)

Note that unfinished depositions started before 2016 are not available on the current ADIT-NMR server. They have been archived and can be migrated to it, please contact for details.

SMSDep: Small Molecule Structure Deposition system
Only those structures which are too small for the PDB to accept may be deposited here. Please read the PDB entry requirements page for the precise purpose and criteria for the SMSDep system.

The prefered file format for NMR data files is NMR-STAR, a Self-defining Text Archival and Retrieval format (STAR). STARch is a software tool that can convert data files from various formats, including PIPP, XEASY, and tab-delimited files generated from common spreadsheets into NMR-STAR format.

Individual data files along with the information you enter about your study will be collated into a single NMR-STAR file. An excellent example of an NMR-STAR file with a number of types of data is entry 4267: Apo-HNGAL Human Neutrophil Gelatinase-Associated Lipocalin.

Time domain data (raw spectral data) is uploaded separately via ftp. Please see the instructions on how to upload time domain data.

To submit additional or corrected data for an existing BMRB entry, please send the file(s) as e-mail attachment to BMRB annotators:, or to BMRB help alias: Large datasets can be uploaded via FTP using the same procedure as for the timedomain data.

Note that the above applies to NMR structure depositions submitted via OneDep system as well. Once you have deposited an NMR structure to OneDep and received the BMRB ID, please use the above methods to send us additional data not collected by the OneDep system.

Pre-deposition data validation services

wwPDB ValidationService will check your model and experimental files prior to submitting a structure to wwPDB.

Protein Structure Validation Suite (PSVS) is a useful tool for the assesment of protein structures generated by NMR and X-ray methods. PSVS is broadly applicable for structure quality assessment in structure biology projects.

iCing Validation Package is part of the Common Interface for NMR structure Generation (CING) package.

CheckShift - Chemical Shift Reference Check at Center of Applied Molecular Engineering, the University of Salzburg, Austria. It works on NMR-STAR 2.1, SHIFTX or TALOS files.

Format conversion tools

STARch file converter: converts data files in various formats to NMR-STAR 3.1 for upload to ADIT-NMR.
Input formats include NMRView, PIPP, Sparky, XEASY, as well as tab- and comma-delimited.

NMR-STAR template generator: produces NMR-STAR 3.1 formatted tables for NMR data.
(Use these as examples of NMR-STAR data files.)

Ambiguity code assignment interface: simplifies assignment of chemical shift ambiguity codes.

Format Converter from PDBe: a set of Python scripts that can read NMR data files and output them into a number of different formats. Here is an introduction to its usage and the download page.

NMR-STAR to other formats: converts NMR-STAR 3.1 chemical shift tables to Sparky, NMRPipe/TALOS, XEASY, or NMR-STAR 2.1.

Conversion tools donated by the NMR community

tab2bmrb: convert chemical shift tables between publication format and NMR-STAR 2.1 format. Also included are tools to calculate random coil chemical shifts and NMR experimental pulse lengths for experiments dependent on 3JHN(CA)HA coupling constants.

FELIX to NMR-STAR: software for converting FELIX chemical shift files to NMR-STAR 2.1 format.

PIPP to NMR-STAR: software for converting PIPP chemical shift files to NMR-STAR 2.1 format.

NMR-STAR to TALOS+: script for converting chemical shift tables in BMRB entries to TALOS+ input files.

CYANA to XPLOR: script for converting CYANA formatted files to XPLOR/CNS/PDB files.

Reference information about atom nomenclature, standard chemical shifts, indirect chemical shift references, etc.

Submitting pulse programs.

ASCII text files containing pulse sequences, text files describing the experiments, and other ancillary files can be submitted by anonymous ftp to "". Please place the files in the incoming/pulse_sequence directory and notify BMRB by e-mail ( that a pulse sequence has been deposited. Please indicate in the e-mail the names of all the files included in the submission.

  • Required:
  • Brief title for the pulse sequence.
  • Suggested location for the pulse sequence in the library.
  • Concise description of what the pulse sequence is intended to provide.
  • Spectrometer manufacturer and model(s) on which the pulse sequence is known to operate.
  • Pulse sequence with phase cycling as an ASCII text file.
  • Literature reference, if appropriate.
  • Name(s) of author(s).

This information can be included as comments in the file containing the pulse sequence.

  • Optional:
  • File containing a figure describing the pulse sequence. Please indicate the format of the file (postscript, GIF, MPEG, etc.).
  • Files containing parameter lists used to execute the pulse sequence (shaped pulses, gradient programs, frequency lists, delay lists, etc.).

Sample Minimal Submission
Sample Fancy Submission

Submitting software and macros.

ASCII text files containing the software macro can be submitted by anonymous ftp to "". Please place the files in the incoming/macro_definition directory and notify BMRB by e-mail ( that a program macro has been deposited. Please include the following information in the e-mail:

  • Required:
  • Brief title for the processing macro.
  • Suggested location or category for the macro in the library.
  • Concise description of what the data processing macro is intended to provide.
  • Software vendor, software product, and software version number compatible with the macro.
  • A literature reference, if appropriate.
  • The name(s) of the author(s) of the macro.

The above information can be included as comments in the file containing the macro.

  • Optional:
  • If control parameters or other information required for the macro to function is contained in ancillary files, please supply an example of those files.
  • E-mail address, telephone number, or other contact information, if you are willing to provide assistance.