> For the complete documentation index, see [llms.txt](https://help.besmart.software/t4i/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.besmart.software/t4i/commands-overview/be.smart-t4i/edit-settings/publisher/saving-files-using-relative-paths.md).

# Saving files using relative paths

The location for each published file type can be set in the *Output folde*r field.

<figure><img src="https://4060565498-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FL8qMZuBhZUXGRVospdct%2Fuploads%2FFgptpIUNFWnjykolhEF7%2Fimage.png?alt=media&amp;token=082ab987-6524-4e4e-af2d-7aa379b85801" alt=""><figcaption></figcaption></figure>

Different settings are possible, see below.

1. The *Output folder* field is empty (`<empty>`).
   * Files are published to default subdirectories based on the published file type, next to the original files.
2. The *Output folder* is fixed by a user (e.g., `C:\PDF`).
   * Files are published into the specified directory.
3. The *Output folder* = `.\`
   * Files are published in the same directory as the original (source) file.
4. The *Output folder* = `.\DIRECTORYNAME`
   * Files are published in a directory relative to the original (source) file.
5. The *Output folder* = `..\`
   * Files are published in a parent directory relative to the original (source) file.
6. The *Output folder* = `..\DIRECTORYNAME`
   * Files are published in the subdirectory of the parent directory relative to the original (source) file.

<figure><img src="https://4060565498-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FL8qMZuBhZUXGRVospdct%2Fuploads%2FuuE2Pi8llc1TFqr2m8mC%2Fimage.png?alt=media&amp;token=096cad66-c832-4836-af40-303ac5fa4422" alt=""><figcaption><p>Example of the Output folder file path settings</p></figcaption></figure>

{% hint style="info" %}
More info is available here: <https://learn.microsoft.com/en-us/dotnet/standard/io/file-path-formats>
{% endhint %}

## Example of saving files using relative paths

<figure><img src="https://4060565498-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FL8qMZuBhZUXGRVospdct%2Fuploads%2Fp0YIVwj4uUq53Tkpv6nf%2FSaving%20files%20using%20relative%20paths.gif?alt=media&amp;token=4b89d11d-1c98-44fe-b0e9-72afd2e8c182" alt=""><figcaption><p>Saving files using relative paths</p></figcaption></figure>


---

# 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://help.besmart.software/t4i/commands-overview/be.smart-t4i/edit-settings/publisher/saving-files-using-relative-paths.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.