> For the complete documentation index, see [llms.txt](https://docs.keyshade.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.keyshade.io/getting-started/importing-your-environment-variables.md).

# Importing your environment variables

Start importing your environment variables into Keyshade

Once your project is set up, the next step is to move your environment variables from `.env` file to Keyshade. There are two ways to do this:

1. Manually creating them one by one
2. Importing the entire `.env` file

We would be sticking with the second option as it is the most convenient way to import your environment variables.

## Import using CLI

1. Head over to your project directory
2. Run the following command:

   ```bash
   keyshade import
   ```
3. Specify the path of the `.env` file
4. Select your default workspace (eg. **My Workspace**)
5. Select the project we created in the previous step
6. Select the environment you want to import the environment variables to (eg. **Development**)
7. Confirm the secret and variable classification
8. Confirm the import

{% embed url="<https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FklyYIOuyG5AKyh2FIsOK%2Fuploads%2FjafRHirceDhGpaewKmQR%2Fimport%20using%20cli.mp4?alt=media&token=844e42f2-0708-4c5a-a397-d03eeda71ac5>" %}

## Import using the app

1. Head into the project
2. Click on **Import**
3. Select the `.env` file
4. Select the environment you want to import the environment variables to (eg. **Development**)
5. Confirm the secret and variable classification
6. Confirm the import

{% embed url="<https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FklyYIOuyG5AKyh2FIsOK%2Fuploads%2F0UZn6ujnCQAIJJJNW1lp%2Fimport%20using%20platform.mp4?alt=media&token=20261603-452a-40f1-b2d7-77032bb3153c>" %}

Now, you have your environment variables imported into Keyshade.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.keyshade.io/getting-started/importing-your-environment-variables.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.