> 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="/files/70R5kpMUE9qiFpbJCRrv" 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="/files/lbN9djFKNfVK6CNIPa3S" 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="/files/sRSPwfhPaTFbxGjBgMKf" 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.besmart.software/t4i/commands-overview/be.smart-t4i/edit-settings/publisher/saving-files-using-relative-paths.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.