You have a molecular model ready to share, analyze elsewhere, or include in a downstream workflow. Then comes a deceptively simple question: Which file format should I use, and how do I know SAMSON can write it? Choosing the wrong format can mean an extra conversion step—or a file that does not contain what the next tool expects.
In SAMSON, an exporter is the extension that writes content from a document to a file. SAMSON includes default exporters for common structures and visualizations, and additional exporters can be added through SAMSON Connect. Examples of formats an exporter may write include PDB and XYZ, as well as other supported formats.
Start with the destination, not the extension
Before exporting, identify what the file is for. Are you sending a structure to a colleague, preparing input for another application, or saving a visualization? The receiving tool or person is usually the best guide to the format you need. If a workflow specifies a format, use that specification rather than choosing based only on familiarity.
Next, check SAMSON’s supported formats page. It lists formats SAMSON can import and export. Since a format being listed does not, by itself, tell you which direction is supported for your particular need, check that the relevant capability is export. This small check can prevent a common mix-up: being able to open a file format does not automatically mean the matching exporter is available.
Use the right term when troubleshooting
The distinction between importers and exporters is straightforward but useful:
- Importers read files into SAMSON.
- Exporters write document content from SAMSON to files.
If you can open a format but cannot find a way to save to it, look for an exporter rather than assuming the importer handles both tasks. The documentation has a separate reference for importers, which helps keep these two extension families clear.
A short pre-export check
- Confirm the required format. Check the instructions for the receiving application, collaborator, or workflow.
- Check export support. Consult the supported-formats list and verify that the format is available for writing.
- Find the corresponding exporter. SAMSON provides default exporters for common structures and visualizations; additional exporters may be available through SAMSON Connect.
- Validate the result for its intended use. After writing the file, check that the receiving application or collaborator can use it as expected. Format compatibility is part of a workflow, not just a filename choice.
This checklist is especially helpful when a project moves between tools. A file can be valid in one context yet still not meet the requirements of the next step. Checking the destination’s expectations before exporting is often easier than diagnosing a compatibility problem later.
When the exporter you need is missing
If the format you need is not available, first review the supported-formats page and the exporters offered through SAMSON Connect. If you still cannot find a suitable exporter, the documentation invites users to contact the SAMSON team.
For developers who want to create an exporter, the relevant next step is the guide to generating SAMSON Extensions. The broader Extending SAMSON reference explains how extensions add capabilities to the platform.
For the exporter reference and related guidance, see Exporters in the SAMSON documentation.
Note: SAMSON and all SAMSON Extensions are free for non-commercial use. Get SAMSON.