A molecular model can look ready to share and still be difficult to use outside the application. The stumbling block is often not the structure itself, but choosing a file format that fits the next step. A collaborator may need a structure for another modeling tool; a visualization workflow may expect a different kind of file. Exporting is therefore more than saving: it is the handoff between your document and the software or person that will use it next.
Start with the destination
Before exporting, ask what the file needs to do. Will someone inspect or edit a molecular structure? Is the file intended for a visualization workflow? Which formats can the receiving application read? These questions help narrow the choice before you create a file.
SAMSON exporters write content from a document to files. The available formats include common options such as PDB and XYZ, alongside other supported formats. The right choice depends on the receiving workflow; a familiar extension is not, by itself, a guarantee that the file is suitable for every purpose.
A short checklist for a cleaner handoff
- Identify the next application or workflow. If another person or tool will use the file, check which formats it accepts instead of guessing.
- Check SAMSON’s supported formats. Use the format reference to see which formats SAMSON can import and export. This helps distinguish a format that is available from one that is appropriate for your handoff.
- Think about what you are exporting. Exporters save content from the document. Consider what the recipient actually needs, rather than assuming that every part of your working document belongs in the delivered file.
- Keep the format’s purpose in mind. PDB and XYZ are examples of formats an exporter may write, but format choice should follow the needs of the next step, not simply the file extension you recognize.
- Make the handoff understandable. Use a clear filename and tell the recipient which format you supplied and what they should use it for. This small bit of context can prevent unnecessary back-and-forth.
Exporters and importers are different jobs
The names are easy to mix up. An exporter writes document content to a file. An importer reads a file into SAMSON. They are matching extension families, but the question you are asking determines which reference to consult: “How do I write this out?” points to exporters; “How do I bring this file in?” points to importers.
When checking whether a format is suitable, it can help to consider both directions. A format may be listed as supported for importing, exporting, or both. Consult the supported-formats reference rather than assuming that support in one direction means support in the other.
When the format you need is missing
If the needed exporter is not available, SAMSON’s extension ecosystem offers another route: additional exporters can be added from SAMSON Connect. If you are looking to create an exporter yourself, the documentation points to the extension-development resources, including the guide to generating SAMSON Extensions. For a missing exporter you need but do not plan to develop, the documentation suggests contacting the SAMSON team.
A useful final check
Before sending a file, confirm that its format matches the recipient’s workflow and that you have described the file clearly. If you are unsure which formats are available, start with Supported formats. For the exporter reference, extension options, and related guidance, learn more in the SAMSON Exporters documentation.
Note: SAMSON and all SAMSON Extensions are free for non-commercial use. Get SAMSON.
