ChimeraX Animation Tutorial: How to Build Clear Protein Movies with Scenes and Movie Maker

To make a ChimeraX protein movie, prepare the structure, start frame capture with movie record, run the motion, wait for its frames to finish and encode the recording with movie encode. Save those commands in a .cxc file so you can repeat the same sequence. The example below makes a full rotation with a specified output size and playback rate; saved views and scenes then let you build more focused shots.

A rotation shows the shape from different angles. It does not show molecular dynamics or establish a biological transition. This guide uses the current official command documentation; the recording example has not been verified by a completed local render. Its timing and presentation choices are illustrative.

If you already prepare still figures you will recognize the same principle here. Define the message first then build each shot around it. If your project also includes static panels or journal graphics, this pairs well with our guide to PDB to animation and our article on protein-ligand interaction visualization.

Use UCSF ChimeraX, a molecular structure and a writable output folder. The official release news lists version 1.12 as the production release available when this guide was updated on October 3, 2026. The scenes commands described here belong to the current documentation; older installations may not include them.

For a small, real input, the example uses PDB 1UBQ, an experimental human ubiquitin structure determined by X-ray diffraction. You can substitute your own validated structure after checking chains, missing residues and assembly choice. The editorial images on this page are conceptual illustrations, not renders of 1UBQ.

Save any work in your current session before trying an example. Start with only the intended structure displayed, so an unqualified turn does not rotate unrelated models too. The open command documentation covers fetching identifiers and running local command files.

A practical ucsf chimerax animation workflow rests on a few core capabilities. The movie command records image frames and encodes them into a video. Saved views let you store camera positions and restore them over a chosen number of frames. Scenes preserve a broader display state including model positions, display styles colors labels some map settings and background color. The fly command helps connect multiple named views along a smoother path.

Those tools matter because they separate planning from output. You can save a promising camera angle with view name, preserve a full visual setup with scenes save, test motion timing with view <name> <frames> or fly and only then record with the chimerax movie maker commands. That division makes iteration much faster than trying to improvise every movement in one pass.

The official tutorials also show that ChimeraX is comfortable with common molecular storytelling patterns: spin shots, ligand zone reveals, morphs between conformations, density inspection and even 360-degree output. In other words it is strong at showing structure, change and context. Your job is to pick the subset that advances the story.

The most common mistake in a chimerax animation tutorial workflow is recording too early. A smooth turn or morph can look impressive while still failing to answer the scientific question. Before you touch the record command write a simple shot list. Start with the global context, move to the functional region, isolate the key residues or ligand and finish on the mechanism or comparison that matters most.

For example a clean protein animation chimerax sequence might use four shots. Shot one establishes the whole assembly. Shot two narrows to one chain or domain. Shot three changes representation to highlight the active site. Shot four adds a conformational change, density map or ligand contact view. Each shot should have a visual purpose and a sentence-level takeaway.

This is also the point where accessibility pays off. High-contrast backgrounds, restrained color logic and readable labels make later editing easier. If the animation will support a paper, poster or video abstract you should align those choices across formats. Our guides to scientific figure accessibility and alt text and the rise of the video abstract are useful references when you move from screen capture to publication-ready communication.

The core of any chimerax scenes tutorial is understanding the difference between views and scenes. A saved view is mainly about orientation and camera-related state. A scene stores much more of what the audience actually sees such as style colors labels map display and background. In practice views are best for motion planning while scenes are best for visual checkpoints you may need to restore repeatedly during production.

A reliable workflow is to set your first framing then save both a named view and a scene. Repeat that for every major shot. After that test transitions with short frame counts. If the camera route is awkward, fix the saved views before you think about final export. If the display state is inconsistent, restore the relevant scene and clean it up there. This prevents the classic problem where the camera path works but colors labels or clipping differ between takes.

For multi-step movement use named views with fly or sequential view transitions. For display changes such as switching from ribbon to surface or revealing a ligand use scene restores or explicit commands paired with a short transition. This division keeps your motion readable and your state changes predictable. It is the most practical foundation for an efficient chimerax scenes tutorial workflow.

Scenes do not recreate models or model parts that you have closed or deleted. Keep the required objects in the session, and save the session along with the script. The current scenes documentation also warns that not every display property is saved.

The first four commands below fetch 1UBQ, hide atoms, show the backbone cartoon and fit the view. Preview those setup commands before making the movie, then start a fresh session when running the complete file to avoid loading the structure twice. Choose a writable output folder.

Create a plain-text file named spin.cxc. Put each command from the table on its own line, without the step numbers or explanations. Run it with File > Open in ChimeraX. These are documented steps; a complete local render was not verified.

At 30 frames per second, the 360-frame rotation occupies 12 seconds; the 30-frame final hold adds one second. That is planned frame arithmetic, not a biological timescale. The expected result is a 1280 by 720 MP4 named spin.mp4 containing the full rotation and a short stationary ending. Check the Log for the recorded frame count and encoding completion.

Opening a command file temporarily uses its containing folder as the working directory, so this relative output name is written beside spin.cxc. Use a new filename for another take. The movie reference describes output size and playback rate; the turn reference defines the angle as degrees per frame.

Good molecular animation is rarely about adding more motion. It is about removing ambiguity. Keep one dominant object in focus. Avoid rapid representation changes unless the switch itself carries meaning. Use silhouettes, lighting and background choices to increase depth perception only when they improve legibility. The official ChimeraX movie tutorials show how much clearer a structure can become after a careful lighting or style adjustment.

This is where a raw ucsf chimerax animation becomes presentation-ready. Check whether the viewer can still identify the ligand after a camera move. Make sure morphs are slow enough to reveal structural change. If you are showing maps or fit quality, avoid overwhelming the frame with too many overlays at once. Clear sequence beats maximal complexity almost every time.

If your project begins with predicted structures or mixed biomolecular assemblies, keep the visual logic consistent from analysis to animation. Our article on AlphaFold 3 complex visualization is helpful for turning model interpretation into a coherent story before you animate it.

If the movie stops before a turn or view transition finishes, check command timing before changing the encoder. Motion commands can return while the movement is still in progress, so the script needs a wait before the next operation. The wait reference explains when an explicit frame count is needed.

If transitions feel disorienting the saved positions are probably too different. Add an intermediate view or reduce the amount of change per shot. The fly command can help when you need to connect several viewpoints smoothly, but remember that view-based transitions and scene restores do different jobs. Use the right tool for the right problem instead of forcing one command to handle everything.

If the animation is technically correct but still weak as communication, the issue is usually narrative density. Too many labels, too many colors or too many simultaneous changes make the sequence hard to follow. Reduce the scene until each shot answers one question. Then build complexity only where it adds meaning. That same discipline improves graphical abstracts as well which is why our graphical abstract maker guide maps closely to good animation planning.