> For the complete documentation index, see [llms.txt](https://academy.dnanexus.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://academy.dnanexus.com/interactivecloudcomputing/jupyterlab/utilizing-a-snapshot.md).

# Utilizing a Snapshot

Since the JupyterLab jobs are hosted on a temporary worker, you will either need to download the software packages every time you start a job, or to save a snapshot of the software environment. 

## What is a Snapshot?

* A snapshot saves the current software environment in the JupyterLab environment. 
* The purpose of the snapshot is to provide a reproducible environment for the JupyterLab jobs.  
* It sets up the environment every time you utilize the snapshot. You do not need to manage dependencies every time you open a JupyterLab job if you utilize a snapshot. 
* Snapshots are saved in the .Notebook\_Snapshots/ folder in the project space, and they have a .[tar.gz](http://tar.gz) file ending. 

## Creating a Snapshot

<figure><img src="/files/rHzNjGhG7WMPcvrw7pzf" alt=""><figcaption></figcaption></figure>

## Utilizing a Snapshot

Snapshots are used in the input section when setting up the JupyterLab Job.&#x20;

The input is highlighted in the figure below:&#x20;

<figure><img src="/files/bpHLnRUagH6ZfMHAI1LQ" alt=""><figcaption></figcaption></figure>

## Snapshot Best Practices

* Don't save data in your snapshot - it uses storage space and impacts costs.
* Snapshots can be large and take up storage space.&#x20;
* Make sure to rename the snapshot according to your organization's naming conventions: you can remember what they refer to when returning to the project in the future.