> For the complete documentation index, see [llms.txt](https://docs.duplicati.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.duplicati.com/backup-destinations/provider-specific-destinations/jottacloud-destination.md). # Jottacloud Destination This page describes the Jottacloud storage destination ## User interface
Jottacloud destination configuration
To configure the Jottacloud destination you need to pick a unique folder name for the backups, and then authorize Duplicati to work on your behalf. Simply click the "AuthID" link in the text field and the authentication process will start and fill out the "AuthID" when you are done. ## URL format for Commandline To use the [Jottacloud](https://jottacloud.com/) storage destination, you can use the following URL format: ``` jottacloud:/// ?authid= ``` To use Jottacloud you must first obtain an `AuthID` by using a Duplicati service to log in to Jottacloud and approve the access. See the [page on the OAuth Server](/duplicati-programs/oauth-server.md) for different ways to obtain an AuthID. ## Device and mount point Within Jottacloud, each machine registered is a device that can be used for storage, and within each device you an choose the mount point. By default, Duplicati will use the special device `Jotta` and the mount point `Archive`. If you need to store data on another device, you can use the options `--jottacloud-device` and `--jottacloud-mountpoint` to set the device and mount point. If you only set the device, the mount point will be set to `Duplicati`. ## Performance tuning If you need to tune the performance and resource usage to match your specific setup, you can adjust the two parameters: * `--jottacloud-threads`: The number of threads used to fetch chunks with * `--jottacloud-chunksize`: The size of chunks to download with each thread --- # 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.duplicati.com/backup-destinations/provider-specific-destinations/jottacloud-destination.md?ask=&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.