A molecular model can look ready to share in SAMSON and still be difficult for someone else to use if it is saved in an unsuitable format. The recipient may need a particular file type, or you may simply be unsure which part of SAMSON’s file-handling tools to look for. A useful first step is to separate two tasks: importing reads a file into SAMSON; exporting writes document content out to a file.
Start with the recipient’s needs
Before choosing an exporter, find out what the next person—or the next step in your workflow—expects. Is there a required file format? Is the file intended to be opened in another application, or is it being passed to a colleague? These questions help narrow your search without assuming that one format is right for every situation.
SAMSON includes default exporters for common structures and visualizations. For example, the documentation names PDB and XYZ as formats an exporter may write. These examples are not a complete format list: check the Supported formats page to see which formats SAMSON can import and export. If you have a specific destination in mind, confirm that its requirements match a format available for export.
Find the right extension
In SAMSON, an exporter is part of the extension family that saves document content to files. If the format you need is supported, the corresponding export capability may be available by default or through an extension from SAMSON Connect. The key point is that “export” describes the direction of the operation, while the format tells you how the resulting file is represented.
If you are looking through documentation or extension listings, use that distinction to avoid a common detour: an importer is for reading files, not writing them. The Importers reference covers the matching extension family for bringing files into SAMSON. If your immediate goal is to save a file, begin with exporters and the supported-format list instead.
A simple pre-export checklist
- Identify the requirement. Write down the exact format requested by the receiving application, collaborator, or workflow.
- Check support. Consult the format reference and look specifically for export support.
- Look for the exporter. SAMSON provides default exporters for common structures and visualizations, and additional exporters can be added from SAMSON Connect.
- Keep the direction straight. Exporters write files; importers read them. If you are trying to save, importer documentation is unlikely to answer the right question.
- Ask when a format is missing. If you cannot find the exporter you need, the documentation invites users to contact the SAMSON team at contact@samson-connect.net.
This checklist is especially helpful when a project moves between people or tools. Rather than choosing a familiar extension by habit, you can establish the required format first, verify that it is supported for export, and then find the appropriate exporter. That small check can prevent an avoidable round of re-saving or clarification later.
When you need something beyond the available exporters
If you are a developer and need to create an exporter, the documentation points to the guide for generating SAMSON Extensions. The broader Extending SAMSON reference explains how extension-based capabilities fit into the platform. These are useful starting points when the format you need is not covered by an existing exporter; they do not replace checking the supported-format list first.
For the complete reference, including links to related pages, visit the SAMSON Exporters documentation.
Note: SAMSON and all SAMSON Extensions are free for non-commercial use. Get SAMSON.
