A molecular model can look right in your workspace and still cause friction when it is time to share it. A collaborator may need a particular file format, a downstream tool may expect a different one, or you may simply be unsure which part of SAMSON handles writing files. These are small uncertainties, but sorting them out early can save time and prevent avoidable back-and-forth.
In SAMSON, exporters are the extensions that save content from a document to files. Depending on the available exporter, the output may be in a format such as PDB or XYZ, or another supported format. SAMSON includes default exporters for common structures and visualizations, and additional exporters can be added through SAMSON Connect.
Start with the file your next step needs
Before exporting, ask the person or software receiving the file what format it can use. “A structure file” is not always a precise enough requirement: the receiving workflow may call for PDB, XYZ, or another specific format. Checking this first is often easier than exporting several alternatives and asking someone else to figure out which one works.
If you are choosing between formats, consult SAMSON’s supported formats reference. It lists formats SAMSON can import and export, helping you check whether the format you need is available. Keep in mind that the required format depends on the next tool or person in your workflow—not just on what is familiar to you.
Know which extension family you need
A simple way to remember the distinction is: importers read files into SAMSON; exporters write document content out to files. If your problem is opening a file, look at the importers reference. If your goal is saving content from a SAMSON document in a file format, look at exporters.
This distinction is useful when searching for an extension. It also helps when describing a problem to a colleague: “I need an exporter for this output format” is more specific than “I need help with files.”
A short pre-export checklist
- Confirm the destination. Identify the software, service, or collaborator that will receive the file.
- Ask for the required format. Do not assume that two tools support the same formats simply because both work with molecular structures.
- Check SAMSON’s format list. Use the supported-formats reference to see whether the format is available for export.
- Look for the relevant exporter. SAMSON has default exporters, and additional exporter extensions may be available through SAMSON Connect.
- Check the result in its intended context. When possible, confirm that the receiving workflow can open the file and that it contains what you intended to share. A file being created does not, by itself, confirm that it meets every downstream requirement.
What if the exporter is missing?
If the format you need is not available, first check the supported-formats page and SAMSON Connect for available extensions. If you still cannot find a suitable exporter, the documentation suggests contacting the SAMSON team at contact@samson-connect.net.
If you want to build an exporter yourself, the exporter reference points to the documentation for generating SAMSON Extensions and the Documentation center. For broader guidance on adding or developing extension-based capabilities, see Extending SAMSON.
The practical takeaway: decide what the receiving workflow needs, check whether SAMSON supports that format, and use the exporter extension family for writing files. For the complete reference, see SAMSON Exporters.
Note: SAMSON and all SAMSON Extensions are free for non-commercial use. Get SAMSON.