A molecular model can look ready to share and still be difficult to use outside the application where it was created. A collaborator may need a particular file format, a downstream tool may expect a different one, or you may simply be unsure whether the format you need is available. Choosing the right exporter is a small step that can prevent a frustrating handoff.
Start with the destination
Before exporting, ask what the recipient or next step actually needs. Is the file going to another molecular modeling tool, into a visualization workflow, or to a colleague who needs to inspect the structure? The answer helps narrow down which format to look for. SAMSON exporters write content from a document to files; examples of formats include PDB and XYZ, alongside other supported formats.
Rather than guessing based on a familiar file extension, check SAMSON’s supported formats page. It lists formats SAMSON can import and export, helping you establish whether a needed format is available before you plan a handoff.
Think of export as part of the workflow
A useful export decision has three parts: the content you intend to share, the format the next person or application can use, and a quick check that the resulting file serves its purpose. Being clear about the first two makes the third easier. For example, if a collaborator has asked for a particular format, use that requirement as your starting point rather than selecting a format simply because it is familiar.
After creating the file, verify it in the context where it will be used when possible. This is a practical handoff check, not a guarantee that every format carries every kind of information. If the recipient needs specific content, confirm that the chosen format and export meet that need.
Exporter or importer?
The distinction is simple, but easy to mix up: an exporter writes document content to a file; an importer reads a file into SAMSON. If you are trying to get work out of SAMSON, look for an exporter. If you are bringing an existing file into SAMSON, the matching extension family is importers. Keeping that direction in mind can save time when searching for help or an extension.
What if the format is missing?
SAMSON includes default exporters for common structures and visualizations, and additional exporters can be added from SAMSON Connect. If you do not find the exporter you need, the documentation suggests contacting the SAMSON team at contact@samson-connect.net.
If you are developing an exporter rather than looking for one to use, that is a different task: start with the documentation on generating SAMSON Extensions. The broader Extending SAMSON reference explains the extension family in context.
A quick handoff checklist
- Identify what the recipient or next application needs.
- Check the supported formats list for an appropriate export option.
- Use an exporter to write document content to a file; use an importer when bringing a file into SAMSON.
- If the required exporter is unavailable, check SAMSON Connect or contact the team.
- When possible, verify the exported file in its intended next step.
Good file handoffs begin with a clear requirement, not a guess at the extension. For more details, see the SAMSON Exporters reference.
Note: SAMSON and all SAMSON Extensions are free for non-commercial use. Get SAMSON.