Where Does Jmol Store Data?
Jmol saves molecular states as script files you choose, with prefs in Java storage. Keep scripts beside data files.
Last updated
Jmol keeps work in state script files you save by hand. Views, selections and measurements serialize into those scripts. Preferences ride in Java storage beside them.
Treat scripts as the project format. Data files stay where you loaded them from. Copy both when moving, since scripts reference data by path.
Where Jmol stores this, by platform
State scripts wherever saved (Java prefs beside them)
State scripts save wherever you choose. Prefs in Java storage. Copy scripts plus data files for full moves.
State scripts wherever saved (Java prefs beside them)
Same script-based workflow on every OS. Keep data paths stable when moving between machines.
State scripts wherever saved (Java prefs beside them)
Same script-based workflow. Check Java prefs location when versions differ.
Frequently asked questions
How do I move Jmol work?
Copy your saved state scripts plus any data files to the new machine. States reopen from wherever stored. Prefs rebuild from defaults when missing.
My view reset on reopen. Why?
Write the state to a script file from the app first. Views alone do not persist without saving. Keep scripts beside their data files.
Notice an outdated path? Let us know.