# How do I determine where assets will be published?

> The final path combines the Transport's Server Directory, the Destination's Directory, and the asset's folder path in the Site.

URL: https://www.hannonhill.com/cascadecms/latest/articles/content-authoring/publishing/how-do-i-determine-where-assets-will-be-published.html
category: Content Authoring
article-type: reference
content-kind: faq
release-availability: all
tags: publishing
updated: 2026-10-06

Cascade CMS works out where to place files by combining three values:

- The [Transport](https://www.hannonhill.com/cascadecms/latest/articles/content-authoring/publishing/transports.html)'s **Server Directory**. If blank, the FTP/FTPS/SFTP user's home directory is used.
- The [Destination](https://www.hannonhill.com/cascadecms/latest/articles/content-authoring/publishing/destinations.html)'s **Directory**.
- The folder path of your asset within the Site.

## Worked example

Given this setup:

- DestinationA has a **Directory** of `www.example.com` and uses TransportA.
- TransportA has a **Server Directory** of `/var/web`.
- A file in the same Site sits at `/about/our-team.png`.

Combining the Transport's Server Directory with the Destination's Directory gives `/var/web/www.example.com` as the Site's root directory. Appending the file's own location produces the final publish path:

```bash
/var/web/www.example.com/about/our-team.png
```

> Changing Transport or Destination directories can have serious consequences for your live websites. Do not change them without consulting your CMS and web server administrators.