A molecular model can look exactly right on screen and still create 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 the exported file may not contain the kind of content they need. Choosing an exporter is therefore not just a final click: it is part of planning a reliable handoff.
In SAMSON, exporters write content from the document to files. The available exporters can handle formats such as PDB and XYZ, among others. SAMSON includes default exporters for common structures and visualizations, and additional exporters can be added from SAMSON Connect.
Start with the recipient’s needs
Before exporting, ask what the file is for and where it will be used. A file intended for another person to inspect may have different requirements from one intended for a separate program or a later stage of a workflow. Ask the recipient which format they need, and whether they expect a structural file, a visualization, or another kind of document content.
This small check can prevent a common handoff problem: selecting a format because it is familiar, only to discover that it is not the format the next person or tool expects. If the recipient is unsure, agree on a format before sending the file rather than assuming that all formats preserve or represent content in the same way.
Check the format, then check the exporter
The Supported formats page is the place to check which formats SAMSON can import and export. Use it to narrow down the options, but keep the task in mind: importing and exporting are different operations, and an importer is not the extension that writes a file.
For writing a file, look for an exporter that supports the intended format. Exporters are the extension family responsible for saving document content to files. If you cannot find an exporter for the format you need, SAMSON’s documentation points users to contact@samson-connect.net to ask about missing exporters.
A simple pre-export checklist
- Identify the destination. Determine which person, application, or workflow will receive the file.
- Confirm the requested format. Check the supported-formats reference instead of guessing from a file extension you have seen before.
- Confirm that an exporter is available. Exporters write files; importers read them. If a suitable exporter is missing, check SAMSON Connect or contact the SAMSON team.
- Describe what you are sending. When handing off a file, name its format and purpose so the recipient knows what to expect.
- Keep the original document available. A useful general practice is to retain your working document alongside files prepared for exchange, so you can return to the source if a different output is requested.
When you need a new exporter
If your workflow depends on a format that is not available, there are two useful paths. First, check SAMSON Connect for an extension that may provide the exporter. If you are looking to build an exporter yourself, the documentation directs developers to the guide on generating SAMSON Extensions and the Documentation center. The Extending SAMSON page provides broader information about extension-based capabilities.
The key is to treat export as a communication step: clarify what the next person or tool needs, check that the format is supported for export, and choose the matching exporter. For more details, see the SAMSON Exporters reference.
Note: SAMSON and all SAMSON Extensions are free for non-commercial use. Get SAMSON.