You finish preparing a molecular document, choose a file format, and send it to a collaborator—only to discover that the format does not carry the content they need. This is a common kind of workflow snag: “export” sounds like one universal action, but the result depends on what you want to save and which formats and exporters are available.
In SAMSON, exporters are extensions that write content from a document to files. They may support formats such as PDB or XYZ, as well as other formats. SAMSON includes default exporters for common structures and visualizations, and additional exporters can be added from SAMSON Connect.
Start with the handoff, not the filename
Before choosing an output format, identify what the next person—or the next step in your workflow—needs to receive. Are you sharing a molecular structure, a visualization, or another kind of document content? The intended use matters because an exporter writes document content in a supported format; the format name alone does not tell you whether the output is appropriate for every purpose.
A useful pre-export check is to answer three questions:
- What content needs to leave SAMSON? Be specific about what you expect the exported file to represent.
- What format does the recipient or downstream workflow require? Confirm this with the person or software that will use the file.
- Does SAMSON support exporting to that format? Check the supported-formats reference rather than assuming that a familiar file extension is available.
This small pause can prevent a frustrating loop of exporting, sharing, and then discovering that you and your collaborator had different expectations.
Check formats and exporters separately
The Supported formats page is the place to check which formats SAMSON can import and export. The Exporters reference explains the exporter extension family: the components responsible for writing document content to files.
These two questions are related, but they are not identical. A format list helps you check whether a format is supported; the exporter reference helps you understand what exporters do and where they fit. If the format you need is missing, SAMSON Connect is the place to look for additional exporters. If you still cannot find one, the documentation invites users to contact SAMSON.
Keep importing and exporting distinct
It is easy to treat file input and output as two sides of the same button. In SAMSON documentation, they belong to matching but distinct extension families: importers read files, while exporters write document content to files. When troubleshooting, check the direction you need. A format being relevant to importing does not, by itself, answer whether an exporter for your intended output is available; use the supported-formats reference to verify the capabilities you need.
If the right exporter is not available
There are two paths to consider. First, check SAMSON Connect for an exporter that supports the format you need. If you are interested in building an exporter yourself, the documentation points to Extending SAMSON and the guide to generating SAMSON Extensions. These resources are intended for adding or developing extension-based capabilities; they are a starting point, rather than a promise that a particular exporter already exists.
In short: define the content you need to hand off, confirm the recipient’s required format, verify export support, and then locate the relevant exporter. That simple sequence makes file sharing more predictable and gives you a clear next step if something is missing.
For the exporter reference and related links, learn more in the SAMSON documentation.
Note: SAMSON and all SAMSON Extensions are free for non-commercial use. Get SAMSON.