You finish preparing a molecular model, choose a filename, and export it—only to discover that the next tool in your workflow expects a different file format. This kind of handoff problem is often less about the model itself and more about choosing the right way to write it out.
In SAMSON, exporters are the extensions that save content from a document to files. They can write formats such as PDB or XYZ, among others. SAMSON includes default exporters for common structures and visualizations, and additional exporters can be added through SAMSON Connect.
Start with the receiving application
Before exporting, identify what the next step in your work requires. Are you sending a structure to another molecular modeling tool, preparing data for a visualization workflow, or archiving a result for later use? The answer helps narrow down which format to look for. A familiar extension is not enough by itself: confirm that the receiving application supports the format and that it suits the kind of content you intend to transfer.
For example, SAMSON’s documentation names PDB and XYZ as examples of formats an exporter may write. These examples are not a complete list, and the best choice depends on the requirements of the application or collaborator receiving the file. Check the current list of formats supported by SAMSON when you need to verify what can be imported or exported.
Keep “export” and “import” straight
A useful way to troubleshoot a file handoff is to separate the two directions of the exchange. An exporter writes content from a SAMSON document to a file. An importer is the corresponding extension family for reading files into SAMSON. If you can open a format but cannot find a way to write it out—or the reverse—you may be looking for the other kind of extension.
This distinction can save time when searching for a solution. The Importers reference covers extensions for reading files, while the exporters reference covers writing document content to files. The supported-formats page is the place to check the format list across both directions.
A quick pre-export checklist
- Confirm the destination. Find out which formats the next application or collaborator can use.
- Check SAMSON’s supported formats. Verify that the desired format is available for export, rather than assuming that support for reading a format also means it can be written.
- Look for the matching exporter. SAMSON provides default exporters, and more can be added from SAMSON Connect.
- Clarify the task. If your goal is to bring a file into SAMSON, look for an importer instead.
- Ask when a needed option is missing. The documentation invites users to contact SAMSON if an exporter is missing.
This reference is intentionally a lookup page, not a step-by-step guide to every export setting or format’s capabilities. If you need to build a custom exporter, the documentation points developers to generating SAMSON Extensions and the Extending SAMSON guide.
For the exporter reference and its related links, learn more in the SAMSON documentation.
Note: SAMSON and all SAMSON Extensions are free for non-commercial use. Get SAMSON.