Before You Convert: A Practical Guide to Molecular File Formats

A familiar frustration in molecular modeling: a file opens, but the next step—sharing it, exporting it, or combining it with another dataset—reveals that the format does not support the operation you need. “Supported” does not always mean both readable and writable. Checking those two capabilities separately can save time and help you choose a reliable route through your workflow.

SAMSON supports formats for molecular structures, trajectories, meshes, images, and more. Its format reference marks whether each listed format can be read, written, or both. Here is a practical way to use that information.

Start with the operation, not just the extension

Before opening a file, ask two questions: do you need to bring data into SAMSON, take data out, or both? For example, MMTF and MOLDEN are listed as readable, with no write support shown. GZ is listed for reading only. By contrast, PDB, MOL2, SDF, and XYZ are listed for both reading and writing as molecular structures.

That distinction matters when planning a round trip. If you need to edit a structure and export it again, a format that is only readable may not be a suitable final output. Consider exporting to a format with write support, while checking that it preserves the information your next tool needs.

Choose a structure format for the job

  • PDB: A standard option for molecular structures. The reference also lists read aliases such as ENT, VDB, PDB1, and PDB2.
  • CIF: Supports crystallographic information, including macromolecular CIF (mmCIF). The listed write option is specifically PDBx/mmCIF.
  • SDF: Supports V2000 and V3000; MOL and SD are listed as read aliases.
  • SMI: SMILES can be read and written. The documentation also points to the SMILES Manager extension for reading and generating SMILES.
  • GRO and TOP: GROMACS structure and topology formats are listed for reading. Writing TOP is associated with GROMACS Wizard, rather than being indicated as a general built-in write operation.

These distinctions are useful when exchanging files: check both the format and any notes beside its read/write status. Some capabilities depend on an extension, so confirm that the extension named in the reference is available for your workflow.

Treat trajectories as a separate compatibility check

A structure file and a trajectory file serve different roles, so check the trajectory table separately. SAMSON lists read and write support for formats including DCD, AMBER NetCDF (NC), TRR, and XTC. Other listed formats, such as TNG, TRJ, and LAMMPSTRJ, are marked for reading without write support.

One particularly useful detail: the reference notes that PARM7/PRMTOP is an AMBER topology file used when loading AMBER NetCDF trajectories. If your trajectory workflow involves NC files, note that the topology file may be part of the input you need—not just the trajectory itself.

Check extension-dependent formats before relying on them

PDBQT read and write support is attributed to AutoDock Vina Extended, which can also load PDBQT files from docking projects done using that extension. The GROMACS Wizard extension can generate GROMACS project files. DNA origami formats—including ADN, ADNPART, JSON, and PLY in the listed uses—are supported by the Adenita extension.

A simple habit helps avoid surprises: make a short checklist of the file you have, the operation you need, and any named extension. If export matters, verify write support before building the rest of your workflow around that format. For formats not listed, SAMSON extensions may provide additional options; the documentation also explains how to request or develop importers and exporters.

For the full format tables and extension notes, see the SAMSON supported formats reference.

Note: SAMSON and all SAMSON Extensions are free for non-commercial use. Get SAMSON.

Comments are closed.