<p>Perhaps you are looking for the backup function</p>

<blockquote>
  <p>File -> Backup...</p>
</blockquote>

<p>and to restore the settings</p>

<blockquote>
  <p>File->Restore...</p>
</blockquote>

CC BY-SA 3.0
2014-09-05T15:10:51.623Z
Yes, this is what I was looking for.
Aaron
CC BY-SA 3.0
2014-09-05T12:12:12.883Z
2014-09-05T12:12:12.883Z
samcarter_is_at_topanswers.xyz
<p>After fooling around with a FITS file(s) (e.g. setting scale, changing color) is it possible to save the session such that there is a file associated with all those tweaks the next time I open it up? </p>

<p>Save and Save Image just seem to keep whatever I set it to, but when I load those new saved files back into ds9 the settings are all back to whatever default load settings I have enabled.</p>

<p>I would also like to be able to do this if I have FITS files loaded into multiple frames so I don't have to go through the process of loading each individual image.</p>

CC BY-SA 3.0
2014-09-05T06:12:40.410Z
Did you try to `export`?
Py-ser
<observational-astronomy><software><ds9>
Save current state in ds9?
Aaron
# Save current state in ds9?

(Asked by: username_0 on 2014-09-05)

After fooling around with a FITS file(s) (e.g. setting scale, changing color) is it possible to save the session such that there is a file associated with all those tweaks the next time I open it up?

Save and Save Image just seem to keep whatever I set it to, but when I load those new saved files back into ds9 the settings are all back to whatever default load settings I have enabled.

I would also like to be able to do this if I have FITS files loaded into multiple frames so I don't have to go through the process of loading each individual image.

**Tags:** observational-astronomy, software, ds9

> **Comments:**
> **username_1**: Did you try to `export`?  

---

## 1 answers

### Answer by username_2 on 2014-09-05. Score: 3 | Accepted answer

Perhaps you are looking for the backup function

> File -> Backup...

and to restore the settings

> File->Restore...

> **Comments:**
> **username_0**: Yes, this is what I was looking for.  

---

