> For the complete documentation index, see [llms.txt](https://docs.pentaho.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pentaho.com/pdia-data-integration/9.3-data-integration/data-integration-perspective-in-the-pdi-client/work-with-transformations-cp/save-a-transformation.md).

# Save a transformation

The method you use to save a transformation depends on if you are using PDI locally on your machine or if you are connected to a repository. If you are connected to a repository, you are remotely saving your file on the Pentaho Server. Optionally, you can save a transformation on a Virtual File System (VFS).

## On your local machine

Follow these instructions to save a transformation on your local machine.

1. In the PDI client, perform one of the following actions:
   * Select **File** > **Save** or **File** > **Save as**.
   * Click the **Save current file** icon in the toolbar.
   * Hold down the CTRL S keys.\
     If you are saving your transformation for the first time, the Save As window appears.
2. Specify the transformation's name in the window and select the location.
3. Press the Enter key or click **Save**.

   The transformation is saved.

The window closes when your transformation is saved.

## In the Pentaho Repository

Follow these instructions to save a transformation to the Pentaho Repository.

1. Verify that you are [connected to a repository](https://docs.pentaho.com/pdia-data-integration/9.3-data-integration/use-a-pentaho-repository-in-pdi.md), which establishes remote access to the Pentaho Server.
2. In the PDI client, perform one of the following actions:
   * Select **File** > **Save** or **File** > **Save as**.
   * Click the **Save current file** icon in the toolbar.
   * Hold down the CTRL S keys.\
     If you are saving your transformation for the first time, the Save repository browser window appears.
3. Navigate to the repository folder where you want to save your transformation.
4. Specify the transformation's name in the **File name** field.
5. Press the Enter key or click **Save**.

The window closes when your transformation is saved.

## On Virtual File Systems

From the menu bar in the PDI client, select **File** > **Open URL** to save a PDI transformation on a Virtual File System (VFS). See [Connecting to Virtual File Systems](https://docs.pentaho.com/pdia-data-integration/9.3-data-integration/data-integration-perspective-in-the-pdi-client/virtual-file-system-browser.md) for details.


---

# 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.pentaho.com/pdia-data-integration/9.3-data-integration/data-integration-perspective-in-the-pdi-client/work-with-transformations-cp/save-a-transformation.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.
