> ## Documentation Index > Fetch the complete documentation index at: https://www.integrate.io/docs/llms.txt > Use this file to discover all available pages before exploring further. # ETL: FTPS Destination > How to configure the FTPS destination component to write files to an FTPS server in your Integrate.io ETL pipeline. The FTPS destination writes pipeline output to any File Transfer Protocol Secure (FTPS) server. It supports CSV, TSV, JSON, Parquet, and Fixed width output formats, with optional compression and PGP encryption. Once your connection is set up, see [File Storage Options](/docs/etl/file-storage-options) for the full set of write options (output formats, compression, PGP, and more) shared across every file storage provider. ## Connection Setup See [FTPS Source](/docs/etl/using-components-ftps-source#connection-setup) for steps to create and configure an FTPS connection in Integrate.io ETL, including firewall allowlist requirements. *** ## Destination Configuration ### Connection Select your FTPS connection from the dropdown, or create a new one. ### Target Directory The path on the FTPS server where output files will be written. Paths must begin with `/`. Integrate.io prepends the slash automatically if omitted. One or more files are created in this directory. By default, the job fails if the directory already exists. Use [package variables](/docs/etl/using-and-setting-variables-in-your-packages) to generate unique directory names per run (e.g. `/output/${_JOB_ID}`). FTPS has no bucket or container field. The path is relative to the FTPS server root. *** ## FAQ **Which destination actions are available for FTPS?** All five destination actions are available: fail if exists, delete and recreate, replace files, copy to existing directory (with character encoding), and copy to new directory. **Can I write to a different FTPS server than the one I read from?** Yes. The source and destination components each have their own connection. You can use different servers, credentials, or paths. *** ## Related