# 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
## Utilizing a Snapshot
Snapshots are used in the input section when setting up the JupyterLab Job.
The input is highlighted in the figure below:
## 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.
* 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.
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://academy.dnanexus.com/interactivecloudcomputing/jupyterlab/utilizing-a-snapshot.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.