A molecular structure can be accurate and still be difficult to read. Atoms, bonds, chains, ligands, and waters may all compete for attention in the same viewport. The useful question is not simply how to make a molecule look attractive, but which details should be visible together so the structure answers the question you are asking.
In SAMSON, a practical way to tackle visual clutter is to build a view in layers: use a visual model to emphasize the overall fold, keep a second representation for selected details, and hide nodes that are not relevant to the current view. This approach is especially helpful when you want to show a ligand in context, inspect selected chains, or prepare a figure without losing the underlying structural information.
Start with the selection, not the representation
Before adding a visual model, decide what it should apply to. SAMSON applies a newly added visual model to the current selection—or to the whole document if nothing is selected. So, if you want a representation on just one chain or molecule, select that target first and check that unrelated nodes are not also selected. If you want the model applied throughout the document, clear the selection.
Then open Visualization > Visual model, or use Ctrl/Cmd + Shift + V, and choose a representation such as Ribbons for secondary structure. The new visual model appears as a node in the document. You can hide the original structural model in the Document view if its default balls-and-sticks display makes the result too busy.

The key advantage of keeping representations as separate visual models is that you can adjust their visibility independently. For example, a ribbon view can communicate the protein fold while a Licorice model can retain a more detailed view of selected atoms. Multiple visual models can be applied to the same nodes, so you can choose which layer to show as your question changes.
Reduce clutter without removing context
Use the Document view to hide nodes you do not need in the viewport: uncheck a chain, residue, visual model, or other supported node, and check it again to show it. Hiding a parent node also hides its descendants. That makes it convenient to temporarily remove a whole chain, but remember that a descendant can still be made visible while its parent is hidden. If a checkbox appears ticked while you expect a parent to be hidden, a visible descendant may be the reason.
You can also select nodes in the Document view or viewport and use the context toolbar’s Visibility section to change visibility for the selection. This is useful when working with several selected chains, rather than toggling each one individually. If you are unsure what you have selected, pause before applying a visual model: selection scope determines where that model is added.
Use transparency to keep a second layer in view
Hiding is not always the best choice. For supported nodes—including structural models, folders, labels, meshes, and many visual models—you can select the node and adjust its transparency in the Inspector. A semi-transparent structural model can provide context behind an opaque secondary-structure representation, instead of forcing you to choose between the two.
This is useful when the overall shape matters, but you also want to see what lies within or behind it. Transparency is available only for some node types, so if the setting is not available for a selected node, use visibility or a different representation instead.
Finish the view for its audience
Once the representation and visibility are working, use a visual preset for a quick coordinated starting point, or adjust rendering effects such as lighting, fog, shadows, and ambient occlusion in Visualization > Options. For a reusable combination of representations and color schemes, explore visual presets; for more control over palettes, see the Colorizing guide.
When the view is ready, capture it with F10 to save to the configured capture folder, Ctrl/Cmd + F10 to choose where to save, or Shift + F10 to copy the capture to the clipboard. A good final check is to ask whether every visible layer contributes useful information—and whether any hidden layer would be helpful to restore for context.
For more workflows and examples, see the SAMSON Visualizing guide.
Note: SAMSON and all SAMSON Extensions are free for non-commercial use. Get SAMSON.
