githubmirror/rclone

MANUAL.html
46 127 строк3 MB
Nick Craig-Wood
Version v1.68.2
15 ноя 2024, 15:20
15 ноя 2024, 15:20f2d16ab
<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml" lang="" xml:lang="">
<head>
  <meta charset="utf-8" />
  <meta name="generator" content="pandoc" />
  <meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes" />
  <meta name="author" content="Nick Craig-Wood" />
  <title>rclone(1) User Manual</title>
  <style>
    code{white-space: pre-wrap;}
    span.smallcaps{font-variant: small-caps;}
    span.underline{text-decoration: underline;}
    div.column{display: inline-block; vertical-align: top; width: 50%;}
    div.hanging-indent{margin-left: 1.5em; text-indent: -1.5em;}
    ul.task-list{list-style: none;}
    pre > code.sourceCode { white-space: pre; position: relative; }
    pre > code.sourceCode > span { display: inline-block; line-height: 1.25; }
    pre > code.sourceCode > span:empty { height: 1.2em; }
    code.sourceCode > span { color: inherit; text-decoration: inherit; }
    div.sourceCode { margin: 1em 0; }
    pre.sourceCode { margin: 0; }
    @media screen {
    div.sourceCode { overflow: auto; }
    }
    @media print {
    pre > code.sourceCode { white-space: pre-wrap; }
    pre > code.sourceCode > span { text-indent: -5em; padding-left: 5em; }
    }
    pre.numberSource code
      { counter-reset: source-line 0; }
    pre.numberSource code > span
      { position: relative; left: -4em; counter-increment: source-line; }
    pre.numberSource code > span > a:first-child::before
      { content: counter(source-line);
        position: relative; left: -1em; text-align: right; vertical-align: baseline;
        border: none; display: inline-block;
        -webkit-touch-callout: none; -webkit-user-select: none;
        -khtml-user-select: none; -moz-user-select: none;
        -ms-user-select: none; user-select: none;
        padding: 0 4px; width: 4em;
        color: #aaaaaa;
      }
    pre.numberSource { margin-left: 3em; border-left: 1px solid #aaaaaa;  padding-left: 4px; }
    div.sourceCode
      {   }
    @media screen {
    pre > code.sourceCode > span > a:first-child::before { text-decoration: underline; }
    }
    code span.al { color: #ff0000; font-weight: bold; } /* Alert */
    code span.an { color: #60a0b0; font-weight: bold; font-style: italic; } /* Annotation */
    code span.at { color: #7d9029; } /* Attribute */
    code span.bn { color: #40a070; } /* BaseN */
    code span.bu { } /* BuiltIn */
    code span.cf { color: #007020; font-weight: bold; } /* ControlFlow */
    code span.ch { color: #4070a0; } /* Char */
    code span.cn { color: #880000; } /* Constant */
    code span.co { color: #60a0b0; font-style: italic; } /* Comment */
    code span.cv { color: #60a0b0; font-weight: bold; font-style: italic; } /* CommentVar */
    code span.do { color: #ba2121; font-style: italic; } /* Documentation */
    code span.dt { color: #902000; } /* DataType */
    code span.dv { color: #40a070; } /* DecVal */
    code span.er { color: #ff0000; font-weight: bold; } /* Error */
    code span.ex { } /* Extension */
    code span.fl { color: #40a070; } /* Float */
    code span.fu { color: #06287e; } /* Function */
    code span.im { } /* Import */
    code span.in { color: #60a0b0; font-weight: bold; font-style: italic; } /* Information */
    code span.kw { color: #007020; font-weight: bold; } /* Keyword */
    code span.op { color: #666666; } /* Operator */
    code span.ot { color: #007020; } /* Other */
    code span.pp { color: #bc7a00; } /* Preprocessor */
    code span.sc { color: #4070a0; } /* SpecialChar */
    code span.ss { color: #bb6688; } /* SpecialString */
    code span.st { color: #4070a0; } /* String */
    code span.va { color: #19177c; } /* Variable */
    code span.vs { color: #4070a0; } /* VerbatimString */
    code span.wa { color: #60a0b0; font-weight: bold; font-style: italic; } /* Warning */
  </style>
</head>
<body>
<header id="title-block-header">
<h1 class="title">rclone(1) User Manual</h1>
<p class="author">Nick Craig-Wood</p>
<p class="date">Nov 15, 2024</p>
</header>
<h1 id="rclone-syncs-your-files-to-cloud-storage">Rclone syncs your files to cloud storage</h1>
<p><img width="50%" src="https://rclone.org/img/logo_on_light__horizontal_color.svg" alt="rclone logo" style="float:right; padding: 5px;" ></p>
<ul>
<li><a href="#about">About rclone</a></li>
<li><a href="#what">What can rclone do for you?</a></li>
<li><a href="#features">What features does rclone have?</a></li>
<li><a href="#providers">What providers does rclone support?</a></li>
<li><a href="https://rclone.org/downloads/">Download</a></li>
<li><a href="https://rclone.org/install/">Install</a></li>
<li><a href="https://rclone.org/donate/">Donate.</a></li>
</ul>
<h2 id="about">About rclone</h2>
<p>Rclone is a command-line program to manage files on cloud storage. It is a feature-rich alternative to cloud vendors' web storage interfaces. <a href="#providers">Over 70 cloud storage products</a> support rclone including S3 object stores, business &amp; consumer file storage services, as well as standard transfer protocols.</p>
<p>Rclone has powerful cloud equivalents to the unix commands rsync, cp, mv, mount, ls, ncdu, tree, rm, and cat. Rclone's familiar syntax includes shell pipeline support, and <code>--dry-run</code> protection. It is used at the command line, in scripts or via its <a href="/rc">API</a>.</p>
<p>Users call rclone <em>"The Swiss army knife of cloud storage"</em>, and <em>"Technology indistinguishable from magic"</em>.</p>
<p>Rclone really looks after your data. It preserves timestamps and verifies checksums at all times. Transfers over limited bandwidth; intermittent connections, or subject to quota can be restarted, from the last good file transferred. You can <a href="https://rclone.org/commands/rclone_check/">check</a> the integrity of your files. Where possible, rclone employs server-side transfers to minimise local bandwidth use and transfers from one provider to another without using local disk.</p>
<p>Virtual backends wrap local and cloud file systems to apply <a href="https://rclone.org/crypt/">encryption</a>, <a href="https://rclone.org/compress/">compression</a>, <a href="https://rclone.org/chunker/">chunking</a>, <a href="https://rclone.org/hasher/">hashing</a> and <a href="https://rclone.org/union/">joining</a>.</p>
<p>Rclone <a href="https://rclone.org/commands/rclone_mount/">mounts</a> any local, cloud or virtual filesystem as a disk on Windows, macOS, linux and FreeBSD, and also serves these over <a href="https://rclone.org/commands/rclone_serve_sftp/">SFTP</a>, <a href="https://rclone.org/commands/rclone_serve_http/">HTTP</a>, <a href="https://rclone.org/commands/rclone_serve_webdav/">WebDAV</a>, <a href="https://rclone.org/commands/rclone_serve_ftp/">FTP</a> and <a href="https://rclone.org/commands/rclone_serve_dlna/">DLNA</a>.</p>
<p>Rclone is mature, open-source software originally inspired by rsync and written in <a href="https://golang.org">Go</a>. The friendly support community is familiar with varied use cases. Official Ubuntu, Debian, Fedora, Brew and Chocolatey repos. include rclone. For the latest version <a href="https://rclone.org/downloads/">downloading from rclone.org</a> is recommended.</p>
<p>Rclone is widely used on Linux, Windows and Mac. Third-party developers create innovative backup, restore, GUI and business process solutions using the rclone command line or API.</p>
<p>Rclone does the heavy lifting of communicating with cloud storage.</p>
<h2 id="what">What can rclone do for you?</h2>
<p>Rclone helps you:</p>
<ul>
<li>Backup (and encrypt) files to cloud storage</li>
<li>Restore (and decrypt) files from cloud storage</li>
<li>Mirror cloud data to other cloud services or locally</li>
<li>Migrate data to the cloud, or between cloud storage vendors</li>
<li>Mount multiple, encrypted, cached or diverse cloud storage as a disk</li>
<li>Analyse and account for data held on cloud storage using <a href="https://rclone.org/commands/rclone_lsf/">lsf</a>, <a href="https://rclone.org/commands/rclone_lsjson/">ljson</a>, <a href="https://rclone.org/commands/rclone_size/">size</a>, <a href="https://rclone.org/commands/rclone_ncdu/">ncdu</a></li>
<li><a href="https://rclone.org/union/">Union</a> file systems together to present multiple local and/or cloud file systems as one</li>
</ul>
<h2 id="features">Features</h2>
<ul>
<li>Transfers
<ul>
<li>MD5, SHA1 hashes are checked at all times for file integrity</li>
<li>Timestamps are preserved on files</li>
<li>Operations can be restarted at any time</li>
<li>Can be to and from network, e.g. two different cloud providers</li>
<li>Can use multi-threaded downloads to local disk</li>
</ul></li>
<li><a href="https://rclone.org/commands/rclone_copy/">Copy</a> new or changed files to cloud storage</li>
<li><a href="https://rclone.org/commands/rclone_sync/">Sync</a> (one way) to make a directory identical</li>
<li><a href="https://rclone.org/bisync/">Bisync</a> (two way) to keep two directories in sync bidirectionally</li>
<li><a href="https://rclone.org/commands/rclone_move/">Move</a> files to cloud storage deleting the local after verification</li>
<li><a href="https://rclone.org/commands/rclone_check/">Check</a> hashes and for missing/extra files</li>
<li><a href="https://rclone.org/commands/rclone_mount/">Mount</a> your cloud storage as a network disk</li>
<li><a href="https://rclone.org/commands/rclone_serve/">Serve</a> local or remote files over <a href="https://rclone.org/commands/rclone_serve_http/">HTTP</a>/<a href="https://rclone.org/commands/rclone_serve_webdav/">WebDav</a>/<a href="https://rclone.org/commands/rclone_serve_ftp/">FTP</a>/<a href="https://rclone.org/commands/rclone_serve_sftp/">SFTP</a>/<a href="https://rclone.org/commands/rclone_serve_dlna/">DLNA</a></li>
<li>Experimental <a href="https://rclone.org/gui/">Web based GUI</a></li>
</ul>
<h2 id="providers">Supported providers</h2>
<p>(There are many others, built on standard protocols such as WebDAV or S3, that work out of the box.)</p>
<ul>
<li>1Fichier</li>
<li>Akamai Netstorage</li>
<li>Alibaba Cloud (Aliyun) Object Storage System (OSS)</li>
<li>Amazon S3</li>
<li>Backblaze B2</li>
<li>Box</li>
<li>Ceph</li>
<li>China Mobile Ecloud Elastic Object Storage (EOS)</li>
<li>Arvan Cloud Object Storage (AOS)</li>
<li>Citrix ShareFile</li>
<li>Cloudflare R2</li>
<li>DigitalOcean Spaces</li>
<li>Digi Storage</li>
<li>Dreamhost</li>
<li>Dropbox</li>
<li>Enterprise File Fabric</li>
<li>Fastmail Files</li>
<li>Files.com</li>
<li>FTP</li>
<li>Gofile</li>
<li>Google Cloud Storage</li>
<li>Google Drive</li>
<li>Google Photos</li>
<li>HDFS</li>
<li>Hetzner Storage Box</li>
<li>HiDrive</li>
<li>HTTP</li>
<li>ImageKit</li>
<li>Internet Archive</li>
<li>Jottacloud</li>
<li>IBM COS S3</li>
<li>IDrive e2</li>
<li>IONOS Cloud</li>
<li>Koofr</li>
<li>Leviia Object Storage</li>
<li>Liara Object Storage</li>
<li>Linkbox</li>
<li>Linode Object Storage</li>
<li>Magalu</li>
<li>Mail.ru Cloud</li>
<li>Memset Memstore</li>
<li>Mega</li>
<li>Memory</li>
<li>Microsoft Azure Blob Storage</li>
<li>Microsoft Azure Files Storage</li>
<li>Microsoft OneDrive</li>
<li>Minio</li>
<li>Nextcloud</li>
<li>OVH</li>
<li>Blomp Cloud Storage</li>
<li>OpenDrive</li>
<li>OpenStack Swift</li>
<li>Oracle Cloud Storage Swift</li>
<li>Oracle Object Storage</li>
<li>ownCloud</li>
<li>pCloud</li>
<li>Petabox</li>
<li>PikPak</li>
<li>Pixeldrain</li>
<li>premiumize.me</li>
<li>put.io</li>
<li>Proton Drive</li>
<li>QingStor</li>
<li>Qiniu Cloud Object Storage (Kodo)</li>
<li>Quatrix by Maytech</li>
<li>Rackspace Cloud Files</li>
<li>rsync.net</li>
<li>Scaleway</li>
<li>Seafile</li>
<li>Seagate Lyve Cloud</li>
<li>SeaweedFS</li>
<li>SFTP</li>
<li>Sia</li>
<li>SMB / CIFS</li>
<li>StackPath</li>
<li>Storj</li>
<li>Synology</li>
<li>SugarSync</li>
<li>Tencent Cloud Object Storage (COS)</li>
<li>Uloz.to</li>
<li>Uptobox</li>
<li>Wasabi</li>
<li>WebDAV</li>
<li>Yandex Disk</li>
<li>Zoho WorkDrive</li>
<li>The local filesystem</li>
</ul>
<h2 id="virtual-providers">Virtual providers</h2>
<p>These backends adapt or modify other storage providers:</p>
<ul>
<li>Alias: Rename existing remotes</li>
<li>Cache: Cache remotes (DEPRECATED)</li>
<li>Chunker: Split large files</li>
<li>Combine: Combine multiple remotes into a directory tree</li>
<li>Compress: Compress files</li>
<li>Crypt: Encrypt files</li>
<li>Hasher: Hash files</li>
<li>Union: Join multiple remotes to work together</li>
</ul>
<h2 id="links">Links</h2>
<ul>
<li><a href="https://rclone.org/">Home page</a></li>
<li><a href="https://github.com/rclone/rclone">GitHub project page for source and bug tracker</a></li>
<li><a href="https://forum.rclone.org">Rclone Forum</a></li>
<li><a href="https://rclone.org/downloads/">Downloads</a></li>
</ul>
<h1 id="install">Install</h1>
<p>Rclone is a Go program and comes as a single binary file.</p>
<h2 id="quickstart">Quickstart</h2>
<ul>
<li><a href="https://rclone.org/downloads/">Download</a> the relevant binary.</li>
<li>Extract the <code>rclone</code> executable, <code>rclone.exe</code> on Windows, from the archive.</li>
<li>Run <code>rclone config</code> to setup. See <a href="https://rclone.org/docs/">rclone config docs</a> for more details.</li>
<li>Optionally configure <a href="#autostart">automatic execution</a>.</li>
</ul>
<p>See below for some expanded Linux / macOS / Windows instructions.</p>
<p>See the <a href="https://rclone.org/docs/">usage</a> docs for how to use rclone, or run <code>rclone -h</code>.</p>
<p>Already installed rclone can be easily updated to the latest version using the <a href="https://rclone.org/commands/rclone_selfupdate/">rclone selfupdate</a> command.</p>
<p>See <a href="https://rclone.org/release_signing/">the release signing docs</a> for how to verify signatures on the release.</p>
<h2 id="script-installation">Script installation</h2>
<p>To install rclone on Linux/macOS/BSD systems, run:</p>
<pre><code>sudo -v ; curl https://rclone.org/install.sh | sudo bash</code></pre>
<p>For beta installation, run:</p>
<pre><code>sudo -v ; curl https://rclone.org/install.sh | sudo bash -s beta</code></pre>
<p>Note that this script checks the version of rclone installed first and won't re-download if not needed.</p>
<h2 id="linux">Linux installation</h2>
<h3 id="linux-precompiled">Precompiled binary</h3>
<p>Fetch and unpack</p>
<pre><code>curl -O https://downloads.rclone.org/rclone-current-linux-amd64.zip
unzip rclone-current-linux-amd64.zip
cd rclone-*-linux-amd64</code></pre>
<p>Copy binary file</p>
<pre><code>sudo cp rclone /usr/bin/
sudo chown root:root /usr/bin/rclone
sudo chmod 755 /usr/bin/rclone</code></pre>
<p>Install manpage</p>
<pre><code>sudo mkdir -p /usr/local/share/man/man1
sudo cp rclone.1 /usr/local/share/man/man1/
sudo mandb</code></pre>
<p>Run <code>rclone config</code> to setup. See <a href="https://rclone.org/docs/">rclone config docs</a> for more details.</p>
<pre><code>rclone config</code></pre>
<h2 id="macos">macOS installation</h2>
<h3 id="macos-brew">Installation with brew</h3>
<pre><code>brew install rclone</code></pre>
<p>NOTE: This version of rclone will not support <code>mount</code> any more (see <a href="https://github.com/rclone/rclone/issues/5373">#5373</a>). If mounting is wanted on macOS, either install a precompiled binary or enable the relevant option when <a href="#source">installing from source</a>.</p>
<p>Note that this is a third party installer not controlled by the rclone developers so it may be out of date. Its current version is as below.</p>
<p><a href="https://repology.org/project/rclone/versions"><img src="https://repology.org/badge/version-for-repo/homebrew/rclone.svg" alt="Homebrew package" /></a></p>
<h3 id="macos-macports">Installation with MacPorts</h3>
<p>On macOS, rclone can also be installed via <a href="https://www.macports.org">MacPorts</a>:</p>
<pre><code>sudo port install rclone</code></pre>
<p>Note that this is a third party installer not controlled by the rclone developers so it may be out of date. Its current version is as below.</p>
<p><a href="https://repology.org/project/rclone/versions"><img src="https://repology.org/badge/version-for-repo/macports/rclone.svg" alt="MacPorts port" /></a></p>
<p>More information <a href="https://ports.macports.org/port/rclone/">here</a>.</p>
<h3 id="macos-precompiled">Precompiled binary, using curl</h3>
<p>To avoid problems with macOS gatekeeper enforcing the binary to be signed and notarized it is enough to download with <code>curl</code>.</p>
<p>Download the latest version of rclone.</p>
<pre><code>cd &amp;&amp; curl -O https://downloads.rclone.org/rclone-current-osx-amd64.zip</code></pre>
<p>Unzip the download and cd to the extracted folder.</p>
<pre><code>unzip -a rclone-current-osx-amd64.zip &amp;&amp; cd rclone-*-osx-amd64</code></pre>
<p>Move rclone to your $PATH. You will be prompted for your password.</p>
<pre><code>sudo mkdir -p /usr/local/bin
sudo mv rclone /usr/local/bin/</code></pre>
<p>(the <code>mkdir</code> command is safe to run, even if the directory already exists).</p>
<p>Remove the leftover files.</p>
<pre><code>cd .. &amp;&amp; rm -rf rclone-*-osx-amd64 rclone-current-osx-amd64.zip</code></pre>
<p>Run <code>rclone config</code> to setup. See <a href="https://rclone.org/docs/">rclone config docs</a> for more details.</p>
<pre><code>rclone config</code></pre>
<h3 id="macos-precompiled-web">Precompiled binary, using a web browser</h3>
<p>When downloading a binary with a web browser, the browser will set the macOS gatekeeper quarantine attribute. Starting from Catalina, when attempting to run <code>rclone</code>, a pop-up will appear saying:</p>
<pre><code>&quot;rclone&quot; cannot be opened because the developer cannot be verified.
macOS cannot verify that this app is free from malware.</code></pre>
<p>The simplest fix is to run</p>
<pre><code>xattr -d com.apple.quarantine rclone</code></pre>
<h2 id="windows">Windows installation</h2>
<h3 id="windows-precompiled">Precompiled binary</h3>
<p>Fetch the correct binary for your processor type by clicking on these links. If not sure, use the first link.</p>
<ul>
<li><a href="https://downloads.rclone.org/rclone-current-windows-amd64.zip">Intel/AMD - 64 Bit</a></li>
<li><a href="https://downloads.rclone.org/rclone-current-windows-386.zip">Intel/AMD - 32 Bit</a></li>
<li><a href="https://downloads.rclone.org/rclone-current-windows-arm64.zip">ARM - 64 Bit</a></li>
</ul>
<p>Open this file in the Explorer and extract <code>rclone.exe</code>. Rclone is a portable executable so you can place it wherever is convenient.</p>
<p>Open a CMD window (or powershell) and run the binary. Note that rclone does not launch a GUI by default, it runs in the CMD Window.</p>
<ul>
<li>Run <code>rclone.exe config</code> to setup. See <a href="https://rclone.org/docs/">rclone config docs</a> for more details.</li>
<li>Optionally configure <a href="#autostart">automatic execution</a>.</li>
</ul>
<p>If you are planning to use the <a href="https://rclone.org/commands/rclone_mount/">rclone mount</a> feature then you will need to install the third party utility <a href="https://winfsp.dev/">WinFsp</a> also.</p>
<h3 id="windows-chocolatey">Windows package manager (Winget)</h3>
<p><a href="https://learn.microsoft.com/en-us/windows/package-manager/">Winget</a> comes pre-installed with the latest versions of Windows. If not, update the <a href="https://www.microsoft.com/p/app-installer/9nblggh4nns1">App Installer</a> package from the Microsoft store.</p>
<p>To install rclone</p>
<pre><code>winget install Rclone.Rclone</code></pre>
<p>To uninstall rclone</p>
<pre><code>winget uninstall Rclone.Rclone --force</code></pre>
<h3 id="windows-chocolatey">Chocolatey package manager</h3>
<p>Make sure you have <a href="https://chocolatey.org/">Choco</a> installed</p>
<pre><code>choco search rclone
choco install rclone</code></pre>
<p>This will install rclone on your Windows machine. If you are planning to use <a href="https://rclone.org/commands/rclone_mount/">rclone mount</a> then</p>
<pre><code>choco install winfsp</code></pre>
<p>will install that too.</p>
<p>Note that this is a third party installer not controlled by the rclone developers so it may be out of date. Its current version is as below.</p>
<p><a href="https://repology.org/project/rclone/versions"><img src="https://repology.org/badge/version-for-repo/chocolatey/rclone.svg" alt="Chocolatey package" /></a></p>
<h3 id="windows-scoop">Scoop package manager</h3>
<p>Make sure you have <a href="https://scoop.sh/">Scoop</a> installed</p>
<pre><code>scoop install rclone</code></pre>
<p>Note that this is a third party installer not controlled by the rclone developers so it may be out of date. Its current version is as below.</p>
<p><a href="https://repology.org/project/rclone/versions"><img src="https://repology.org/badge/version-for-repo/scoop/rclone.svg" alt="Scoop package" /></a></p>
<h2 id="package-manager">Package manager installation</h2>
<p>Many Linux, Windows, macOS and other OS distributions package and distribute rclone.</p>
<p>The distributed versions of rclone are often quite out of date and for this reason we recommend one of the other installation methods if possible.</p>
<p>You can get an idea of how up to date or not your OS distribution's package is here.</p>
<p><a href="https://repology.org/project/rclone/versions"><img src="https://repology.org/badge/vertical-allrepos/rclone.svg?columns=3" alt="Packaging status" /></a></p>
<h2 id="docker">Docker installation</h2>
<p>The rclone developers maintain a <a href="https://hub.docker.com/r/rclone/rclone">docker image for rclone</a>.</p>
<p>These images are built as part of the release process based on a minimal Alpine Linux.</p>
<p>The <code>:latest</code> tag will always point to the latest stable release. You can use the <code>:beta</code> tag to get the latest build from master. You can also use version tags, e.g. <code>:1.49.1</code>, <code>:1.49</code> or <code>:1</code>.</p>
<pre><code>$ docker pull rclone/rclone:latest
latest: Pulling from rclone/rclone
Digest: sha256:0e0ced72671989bb837fea8e88578b3fc48371aa45d209663683e24cfdaa0e11
...
$ docker run --rm rclone/rclone:latest version
rclone v1.49.1
- os/arch: linux/amd64
- go version: go1.12.9</code></pre>
<p>There are a few command line options to consider when starting an rclone Docker container from the rclone image.</p>
<ul>
<li><p>You need to mount the host rclone config dir at <code>/config/rclone</code> into the Docker container. Due to the fact that rclone updates tokens inside its config file, and that the update process involves a file rename, you need to mount the whole host rclone config dir, not just the single host rclone config file.</p></li>
<li><p>You need to mount a host data dir at <code>/data</code> into the Docker container.</p></li>
<li><p>By default, the rclone binary inside a Docker container runs with UID=0 (root). As a result, all files created in a run will have UID=0. If your config and data files reside on the host with a non-root UID:GID, you need to pass these on the container start command line.</p></li>
<li><p>If you want to access the RC interface (either via the API or the Web UI), it is required to set the <code>--rc-addr</code> to <code>:5572</code> in order to connect to it from outside the container. An explanation about why this is necessary is present <a href="https://web.archive.org/web/20200808071950/https://pythonspeed.com/articles/docker-connection-refused/">here</a>.</p>
<ul>
<li>NOTE: Users running this container with the docker network set to <code>host</code> should probably set it to listen to localhost only, with <code>127.0.0.1:5572</code> as the value for <code>--rc-addr</code></li>
</ul></li>
<li><p>It is possible to use <code>rclone mount</code> inside a userspace Docker container, and expose the resulting fuse mount to the host. The exact <code>docker run</code> options to do that might vary slightly between hosts. See, e.g. the discussion in this <a href="https://github.com/moby/moby/issues/9448">thread</a>.</p>
<p>You also need to mount the host <code>/etc/passwd</code> and <code>/etc/group</code> for fuse to work inside the container.</p></li>
</ul>
<p>Here are some commands tested on an Ubuntu 18.04.3 host:</p>
<pre><code># config on host at ~/.config/rclone/rclone.conf
# data on host at ~/data

# add a remote interactively
docker run --rm -it \
    --volume ~/.config/rclone:/config/rclone \
    --user $(id -u):$(id -g) \
    rclone/rclone \
    config

# make sure the config is ok by listing the remotes
docker run --rm \
    --volume ~/.config/rclone:/config/rclone \
    --user $(id -u):$(id -g) \
    rclone/rclone \
    listremotes

# perform mount inside Docker container, expose result to host
mkdir -p ~/data/mount
docker run --rm \
    --volume ~/.config/rclone:/config/rclone \
    --volume ~/data:/data:shared \
    --user $(id -u):$(id -g) \
    --volume /etc/passwd:/etc/passwd:ro --volume /etc/group:/etc/group:ro \
    --device /dev/fuse --cap-add SYS_ADMIN --security-opt apparmor:unconfined \
    rclone/rclone \
    mount dropbox:Photos /data/mount &amp;
ls ~/data/mount
kill %1</code></pre>
<h2 id="snap">Snap installation</h2>
<p><a href="https://snapcraft.io/rclone"><img src="https://snapcraft.io/static/images/badges/en/snap-store-black.svg" alt="Get it from the Snap Store" /></a></p>
<p>Make sure you have <a href="https://snapcraft.io/docs/installing-snapd">Snapd installed</a></p>
<div class="sourceCode" id="cb23"><pre class="sourceCode bash"><code class="sourceCode bash"><span id="cb23-1"><a href="#cb23-1" aria-hidden="true"></a>$ <span class="fu">sudo</span> snap install rclone</span></code></pre></div>
<p>Due to the strict confinement of Snap, rclone snap cannot access real /home/$USER/.config/rclone directory, default config path is as below.</p>
<ul>
<li>Default config directory:
<ul>
<li>/home/$USER/snap/rclone/current/.config/rclone</li>
</ul></li>
</ul>
<p>Note: Due to the strict confinement of Snap, <code>rclone mount</code> feature is <code>not</code> supported.</p>
<p>If mounting is wanted, either install a precompiled binary or enable the relevant option when <a href="#source">installing from source</a>.</p>
<p>Note that this is controlled by <a href="https://github.com/boukendesho/rclone-snap">community maintainer</a> not the rclone developers so it may be out of date. Its current version is as below.</p>
<p><a href="https://snapcraft.io/rclone"><img src="https://snapcraft.io/rclone/badge.svg" alt="rclone" /></a></p>
<h2 id="source">Source installation</h2>
<p>Make sure you have git and <a href="https://golang.org/">Go</a> installed. Go version 1.18 or newer is required, the latest release is recommended. You can get it from your package manager, or download it from <a href="https://golang.org/dl/">golang.org/dl</a>. Then you can run the following:</p>
<pre><code>git clone https://github.com/rclone/rclone.git
cd rclone
go build</code></pre>
<p>This will check out the rclone source in subfolder rclone, which you can later modify and send pull requests with. Then it will build the rclone executable in the same folder. As an initial check you can now run <code>./rclone version</code> (<code>.\rclone version</code> on Windows).</p>
<p>Note that on macOS and Windows the <a href="https://rclone.org/commands/rclone_mount/">mount</a> command will not be available unless you specify an additional build tag <code>cmount</code>.</p>
<pre><code>go build -tags cmount</code></pre>
<p>This assumes you have a GCC compatible C compiler (GCC or Clang) in your PATH, as it uses <a href="https://pkg.go.dev/cmd/cgo">cgo</a>. But on Windows, the <a href="https://github.com/winfsp/cgofuse">cgofuse</a> library that the cmount implementation is based on, also supports building <a href="https://github.com/golang/go/wiki/WindowsDLLs">without cgo</a>, i.e. by setting environment variable CGO_ENABLED to value 0 (static linking). This is how the official Windows release of rclone is being built, starting with version 1.59. It is still possible to build with cgo on Windows as well, by using the MinGW port of GCC, e.g. by installing it in a <a href="https://www.msys2.org">MSYS2</a> distribution (make sure you install it in the classic mingw64 subsystem, the ucrt64 version is not compatible).</p>
<p>Additionally, to build with mount on Windows, you must install the third party utility <a href="https://winfsp.dev/">WinFsp</a>, with the "Developer" feature selected. If building with cgo, you must also set environment variable CPATH pointing to the fuse include directory within the WinFsp installation (normally <code>C:\Program Files (x86)\WinFsp\inc\fuse</code>).</p>
<p>You may add arguments <code>-ldflags -s</code> to omit symbol table and debug information, making the executable file smaller, and <code>-trimpath</code> to remove references to local file system paths. The official rclone releases are built with both of these.</p>
<pre><code>go build -trimpath -ldflags -s -tags cmount</code></pre>
<p>If you want to customize the version string, as reported by the <code>rclone version</code> command, you can set one of the variables <code>fs.Version</code>, <code>fs.VersionTag</code> (to keep default suffix but customize the number), or <code>fs.VersionSuffix</code> (to keep default number but customize the suffix). This can be done from the build command, by adding to the <code>-ldflags</code> argument value as shown below.</p>
<pre><code>go build -trimpath -ldflags &quot;-s -X github.com/rclone/rclone/fs.Version=v9.9.9-test&quot; -tags cmount</code></pre>
<p>On Windows, the official executables also have the version information, as well as a file icon, embedded as binary resources. To get that with your own build you need to run the following command <strong>before</strong> the build command. It generates a Windows resource system object file, with extension .syso, e.g. <code>resource_windows_amd64.syso</code>, that will be automatically picked up by future build commands.</p>
<pre><code>go run bin/resource_windows.go</code></pre>
<p>The above command will generate a resource file containing version information based on the fs.Version variable in source at the time you run the command, which means if the value of this variable changes you need to re-run the command for it to be reflected in the version information. Also, if you override this version variable in the build command as described above, you need to do that also when generating the resource file, or else it will still use the value from the source.</p>
<pre><code>go run bin/resource_windows.go -version v9.9.9-test</code></pre>
<p>Instead of executing the <code>go build</code> command directly, you can run it via the Makefile. The default target changes the version suffix from "-DEV" to "-beta" followed by additional commit details, embeds version information binary resources on Windows, and copies the resulting rclone executable into your GOPATH bin folder (<code>$(go env GOPATH)/bin</code>, which corresponds to <code>~/go/bin/rclone</code> by default).</p>
<pre><code>make</code></pre>
<p>To include mount command on macOS and Windows with Makefile build:</p>
<pre><code>make GOTAGS=cmount</code></pre>
<p>There are other make targets that can be used for more advanced builds, such as cross-compiling for all supported os/architectures, and packaging results into release artifacts. See <a href="https://github.com/rclone/rclone/blob/master/Makefile">Makefile</a> and <a href="https://github.com/rclone/rclone/blob/master/bin/cross-compile.go">cross-compile.go</a> for details.</p>
<p>Another alternative method for source installation is to download the source, build and install rclone - all in one operation, as a regular Go package. The source will be stored it in the Go module cache, and the resulting executable will be in your GOPATH bin folder (<code>$(go env GOPATH)/bin</code>, which corresponds to <code>~/go/bin/rclone</code> by default).</p>
<pre><code>go install github.com/rclone/rclone@latest</code></pre>
<p>In some situations, rclone executable size might be too big for deployment in very restricted environments when all backends with large SDKs are included. To limit binary size unused backends can be commented out in <code>backends/all/all.go</code> and unused commands in <code>cmd/all/all.go</code> before building with <code>go build</code> or <code>make</code></p>
<h2 id="ansible">Ansible installation</h2>
<p>This can be done with <a href="https://github.com/stefangweichinger/ansible-rclone">Stefan Weichinger's ansible role</a>.</p>
<p>Instructions</p>
<ol type="1">
<li><code>git clone https://github.com/stefangweichinger/ansible-rclone.git</code> into your local roles-directory</li>
<li>add the role to the hosts you want rclone installed to:</li>
</ol>
<pre><code>    - hosts: rclone-hosts
      roles:
          - rclone</code></pre>
<h2 id="portable">Portable installation</h2>
<p>As mentioned <a href="https://rclone.org/install/#quickstart">above</a>, rclone is single executable (<code>rclone</code>, or <code>rclone.exe</code> on Windows) that you can download as a zip archive and extract into a location of your choosing. When executing different commands, it may create files in different locations, such as a configuration file and various temporary files. By default the locations for these are according to your operating system, e.g. configuration file in your user profile directory and temporary files in the standard temporary directory, but you can customize all of them, e.g. to make a completely self-contained, portable installation.</p>
<p>Run the <a href="https://rclone.org/commands/rclone_config_paths/">config paths</a> command to see the locations that rclone will use.</p>
<p>To override them set the corresponding options (as command-line arguments, or as <a href="https://rclone.org/docs/#environment-variables">environment variables</a>): - <a href="https://rclone.org/docs/#config-config-file">--config</a> - <a href="https://rclone.org/docs/#cache-dir-dir">--cache-dir</a> - <a href="https://rclone.org/docs/#temp-dir-dir">--temp-dir</a></p>
<h2 id="autostart">Autostart</h2>
<p>After installing and configuring rclone, as described above, you are ready to use rclone as an interactive command line utility. If your goal is to perform <em>periodic</em> operations, such as a regular <a href="https://rclone.org/commands/rclone_sync/">sync</a>, you will probably want to configure your rclone command in your operating system's scheduler. If you need to expose <em>service</em>-like features, such as <a href="https://rclone.org/rc/">remote control</a>, <a href="https://rclone.org/gui/">GUI</a>, <a href="https://rclone.org/commands/rclone_serve/">serve</a> or <a href="https://rclone.org/commands/rclone_mount/">mount</a>, you will often want an rclone command always running in the background, and configuring it to run in a service infrastructure may be a better option. Below are some alternatives on how to achieve this on different operating systems.</p>
<p>NOTE: Before setting up autorun it is highly recommended that you have tested your command manually from a Command Prompt first.</p>
<h3 id="autostart-on-windows">Autostart on Windows</h3>
<p>The most relevant alternatives for autostart on Windows are: - Run at user log on using the Startup folder - Run at user log on, at system startup or at schedule using Task Scheduler - Run at system startup using Windows service</p>
<h4 id="running-in-background">Running in background</h4>
<p>Rclone is a console application, so if not starting from an existing Command Prompt, e.g. when starting rclone.exe from a shortcut, it will open a Command Prompt window. When configuring rclone to run from task scheduler and windows service you are able to set it to run hidden in background. From rclone version 1.54 you can also make it run hidden from anywhere by adding option <code>--no-console</code> (it may still flash briefly when the program starts). Since rclone normally writes information and any error messages to the console, you must redirect this to a file to be able to see it. Rclone has a built-in option <code>--log-file</code> for that.</p>
<p>Example command to run a sync in background:</p>
<pre><code>c:\rclone\rclone.exe sync c:\files remote:/files --no-console --log-file c:\rclone\logs\sync_files.txt</code></pre>
<h4 id="user-account">User account</h4>
<p>As mentioned in the <a href="https://rclone.org/commands/rclone_mount/">mount</a> documentation, mounted drives created as Administrator are not visible to other accounts, not even the account that was elevated as Administrator. By running the mount command as the built-in <code>SYSTEM</code> user account, it will create drives accessible for everyone on the system. Both scheduled task and Windows service can be used to achieve this.</p>
<p>NOTE: Remember that when rclone runs as the <code>SYSTEM</code> user, the user profile that it sees will not be yours. This means that if you normally run rclone with configuration file in the default location, to be able to use the same configuration when running as the system user you must explicitly tell rclone where to find it with the <a href="https://rclone.org/docs/#config-config-file"><code>--config</code></a> option, or else it will look in the system users profile path (<code>C:\Windows\System32\config\systemprofile</code>). To test your command manually from a Command Prompt, you can run it with the <a href="https://docs.microsoft.com/en-us/sysinternals/downloads/psexec">PsExec</a> utility from Microsoft's Sysinternals suite, which takes option <code>-s</code> to execute commands as the <code>SYSTEM</code> user.</p>
<h4 id="start-from-startup-folder">Start from Startup folder</h4>
<p>To quickly execute an rclone command you can simply create a standard Windows Explorer shortcut for the complete rclone command you want to run. If you store this shortcut in the special "Startup" start-menu folder, Windows will automatically run it at login. To open this folder in Windows Explorer, enter path <code>%APPDATA%\Microsoft\Windows\Start Menu\Programs\Startup</code>, or <code>C:\ProgramData\Microsoft\Windows\Start Menu\Programs\StartUp</code> if you want the command to start for <em>every</em> user that logs in.</p>
<p>This is the easiest approach to autostarting of rclone, but it offers no functionality to set it to run as different user, or to set conditions or actions on certain events. Setting up a scheduled task as described below will often give you better results.</p>
<h4 id="start-from-task-scheduler">Start from Task Scheduler</h4>
<p>Task Scheduler is an administrative tool built into Windows, and it can be used to configure rclone to be started automatically in a highly configurable way, e.g. periodically on a schedule, on user log on, or at system startup. It can run be configured to run as the current user, or for a mount command that needs to be available to all users it can run as the <code>SYSTEM</code> user. For technical information, see https://docs.microsoft.com/windows/win32/taskschd/task-scheduler-start-page.</p>
<h4 id="run-as-service">Run as service</h4>
<p>For running rclone at system startup, you can create a Windows service that executes your rclone command, as an alternative to scheduled task configured to run at startup.</p>
<h5 id="mount-command-built-in-service-integration">Mount command built-in service integration</h5>
<p>For mount commands, rclone has a built-in Windows service integration via the third-party WinFsp library it uses. Registering as a regular Windows service easy, as you just have to execute the built-in PowerShell command <code>New-Service</code> (requires administrative privileges).</p>
<p>Example of a PowerShell command that creates a Windows service for mounting some <code>remote:/files</code> as drive letter <code>X:</code>, for <em>all</em> users (service will be running as the local system account):</p>
<pre><code>New-Service -Name Rclone -BinaryPathName &#39;c:\rclone\rclone.exe mount remote:/files X: --config c:\rclone\config\rclone.conf --log-file c:\rclone\logs\mount.txt&#39;</code></pre>
<p>The <a href="https://github.com/billziss-gh/winfsp/wiki/WinFsp-Service-Architecture">WinFsp service infrastructure</a> supports incorporating services for file system implementations, such as rclone, into its own launcher service, as kind of "child services". This has the additional advantage that it also implements a network provider that integrates into Windows standard methods for managing network drives. This is currently not officially supported by Rclone, but with WinFsp version 2019.3 B2 / v1.5B2 or later it should be possible through path rewriting as described <a href="https://github.com/rclone/rclone/issues/3340">here</a>.</p>
<h5 id="third-party-service-integration">Third-party service integration</h5>
<p>To Windows service running any rclone command, the excellent third-party utility <a href="http://nssm.cc">NSSM</a>, the "Non-Sucking Service Manager", can be used. It includes some advanced features such as adjusting process priority, defining process environment variables, redirect to file anything written to stdout, and customized response to different exit codes, with a GUI to configure everything from (although it can also be used from command line ).</p>
<p>There are also several other alternatives. To mention one more, <a href="https://github.com/winsw/winsw">WinSW</a>, "Windows Service Wrapper", is worth checking out. It requires .NET Framework, but it is preinstalled on newer versions of Windows, and it also provides alternative standalone distributions which includes necessary runtime (.NET 5). WinSW is a command-line only utility, where you have to manually create an XML file with service configuration. This may be a drawback for some, but it can also be an advantage as it is easy to back up and reuse the configuration settings, without having go through manual steps in a GUI. One thing to note is that by default it does not restart the service on error, one have to explicit enable this in the configuration file (via the "onfailure" parameter).</p>
<h3 id="autostart-on-linux">Autostart on Linux</h3>
<h4 id="start-as-a-service">Start as a service</h4>
<p>To always run rclone in background, relevant for mount commands etc, you can use systemd to set up rclone as a system or user service. Running as a system service ensures that it is run at startup even if the user it is running as has no active session. Running rclone as a user service ensures that it only starts after the configured user has logged into the system.</p>
<h4 id="run-periodically-from-cron">Run periodically from cron</h4>
<p>To run a periodic command, such as a copy/sync, you can set up a cron job.</p>
<h1 id="usage">Usage</h1>
<p>Rclone is a command line program to manage files on cloud storage. After <a href="https://rclone.org/downloads/">download</a> and <a href="/install">install</a>, continue here to learn how to use it: Initial <a href="#configure">configuration</a>, what the <a href="#basic-syntax">basic syntax</a> looks like, describes the various <a href="#subcommands">subcommands</a>, the various <a href="#options">options</a>, and more.</p>
<h2 id="configure">Configure</h2>
<p>First, you'll need to configure rclone. As the object storage systems have quite complicated authentication these are kept in a config file. (See the <a href="#config-config-file"><code>--config</code></a> entry for how to find the config file and choose its location.)</p>
<p>The easiest way to make the config is to run rclone with the config option:</p>
<pre><code>rclone config</code></pre>
<p>See the following for detailed instructions for</p>
<ul>
<li><a href="https://rclone.org/fichier/">1Fichier</a></li>
<li><a href="https://rclone.org/netstorage/">Akamai Netstorage</a></li>
<li><a href="https://rclone.org/alias/">Alias</a></li>
<li><a href="https://rclone.org/s3/">Amazon S3</a></li>
<li><a href="https://rclone.org/b2/">Backblaze B2</a></li>
<li><a href="https://rclone.org/box/">Box</a></li>
<li><a href="https://rclone.org/chunker/">Chunker</a> - transparently splits large files for other remotes</li>
<li><a href="https://rclone.org/sharefile/">Citrix ShareFile</a></li>
<li><a href="https://rclone.org/compress/">Compress</a></li>
<li><a href="https://rclone.org/combine/">Combine</a></li>
<li><a href="https://rclone.org/crypt/">Crypt</a> - to encrypt other remotes</li>
<li><a href="https://rclone.org/s3/#digitalocean-spaces">DigitalOcean Spaces</a></li>
<li><a href="https://rclone.org/koofr/#digi-storage">Digi Storage</a></li>
<li><a href="https://rclone.org/dropbox/">Dropbox</a></li>
<li><a href="https://rclone.org/filefabric/">Enterprise File Fabric</a></li>
<li><a href="https://rclone.org/filescom/">Files.com</a></li>
<li><a href="https://rclone.org/ftp/">FTP</a></li>
<li><a href="https://rclone.org/gofile/">Gofile</a></li>
<li><a href="https://rclone.org/googlecloudstorage/">Google Cloud Storage</a></li>
<li><a href="https://rclone.org/drive/">Google Drive</a></li>
<li><a href="https://rclone.org/googlephotos/">Google Photos</a></li>
<li><a href="https://rclone.org/hasher/">Hasher</a> - to handle checksums for other remotes</li>
<li><a href="https://rclone.org/hdfs/">HDFS</a></li>
<li><a href="https://rclone.org/sftp/#hetzner-storage-box">Hetzner Storage Box</a></li>
<li><a href="https://rclone.org/hidrive/">HiDrive</a></li>
<li><a href="https://rclone.org/http/">HTTP</a></li>
<li><a href="https://rclone.org/internetarchive/">Internet Archive</a></li>
<li><a href="https://rclone.org/jottacloud/">Jottacloud</a></li>
<li><a href="https://rclone.org/koofr/">Koofr</a></li>
<li><a href="https://rclone.org/linkbox/">Linkbox</a></li>
<li><a href="https://rclone.org/mailru/">Mail.ru Cloud</a></li>
<li><a href="https://rclone.org/mega/">Mega</a></li>
<li><a href="https://rclone.org/memory/">Memory</a></li>
<li><a href="https://rclone.org/azureblob/">Microsoft Azure Blob Storage</a></li>
<li><a href="https://rclone.org/azurefiles/">Microsoft Azure Files Storage</a></li>
<li><a href="https://rclone.org/onedrive/">Microsoft OneDrive</a></li>
<li><a href="https://rclone.org/swift/">OpenStack Swift / Rackspace Cloudfiles / Blomp Cloud Storage / Memset Memstore</a></li>
<li><a href="https://rclone.org/opendrive/">OpenDrive</a></li>
<li><a href="https://rclone.org/oracleobjectstorage/">Oracle Object Storage</a></li>
<li><a href="https://rclone.org/pcloud/">Pcloud</a></li>
<li><a href="https://rclone.org/pikpak/">PikPak</a></li>
<li><a href="https://rclone.org/pixeldrain/">Pixeldrain</a></li>
<li><a href="https://rclone.org/premiumizeme/">premiumize.me</a></li>
<li><a href="https://rclone.org/putio/">put.io</a></li>
<li><a href="https://rclone.org/protondrive/">Proton Drive</a></li>
<li><a href="https://rclone.org/qingstor/">QingStor</a></li>
<li><a href="https://rclone.org/quatrix/">Quatrix by Maytech</a></li>
<li><a href="https://rclone.org/sftp/#rsync-net">rsync.net</a></li>
<li><a href="https://rclone.org/seafile/">Seafile</a></li>
<li><a href="https://rclone.org/sftp/">SFTP</a></li>
<li><a href="https://rclone.org/sia/">Sia</a></li>
<li><a href="https://rclone.org/smb/">SMB</a></li>
<li><a href="https://rclone.org/storj/">Storj</a></li>
<li><a href="https://rclone.org/sugarsync/">SugarSync</a></li>
<li><a href="https://rclone.org/union/">Union</a></li>
<li><a href="https://rclone.org/ulozto/">Uloz.to</a></li>
<li><a href="https://rclone.org/uptobox/">Uptobox</a></li>
<li><a href="https://rclone.org/webdav/">WebDAV</a></li>
<li><a href="https://rclone.org/yandex/">Yandex Disk</a></li>
<li><a href="https://rclone.org/zoho/">Zoho WorkDrive</a></li>
<li><a href="https://rclone.org/local/">The local filesystem</a></li>
</ul>
<h2 id="basic-syntax">Basic syntax</h2>
<p>Rclone syncs a directory tree from one storage system to another.</p>
<p>Its syntax is like this</p>
<pre><code>rclone subcommand [options] &lt;parameters&gt; &lt;parameters...&gt;</code></pre>
<p>A <code>subcommand</code> is a the rclone operation required, (e.g. <code>sync</code>, <code>copy</code>, <code>ls</code>).</p>
<p>An <code>option</code> is a single letter flag (e.g. <code>-v</code>) or a group of single letter flags (e.g. <code>-Pv</code>) or a long flag (e.g. <code>--progress</code>). No options are required. Options can come after the <code>subcommand</code> or in between parameters too or on the end, but only global options can be used before the <code>subcommand</code>. Anything after a <code>--</code> option will not be interpreted as an option so if you need to add a parameter which starts with a <code>-</code> then put a <code>--</code> on its own first, eg</p>
<pre><code>rclone lsf -- -directory-starting-with-dash</code></pre>
<p>A <code>parameter</code> is usually a file path or <a href="#syntax-of-remote-paths">rclone remote</a>, eg <code>/path/to/file</code> or <code>remote:path/to/file</code> but it can be other things - the <code>subcommand</code> help will tell you what.</p>
<p>Source and destination paths are specified by the name you gave the storage system in the config file then the sub path, e.g. "drive:myfolder" to look at "myfolder" in Google drive.</p>
<p>You can define as many storage paths as you like in the config file.</p>
<p>Please use the <a href="#interactive"><code>--interactive</code>/<code>-i</code></a> flag while learning rclone to avoid accidental data loss.</p>
<h2 id="subcommands">Subcommands</h2>
<p>rclone uses a system of subcommands. For example</p>
<pre><code>rclone ls remote:path # lists a remote
rclone copy /local/path remote:path # copies /local/path to the remote
rclone sync --interactive /local/path remote:path # syncs /local/path to the remote</code></pre>
<h1 id="rclone-config">rclone config</h1>
<p>Enter an interactive configuration session.</p>
<h2 id="synopsis">Synopsis</h2>
<p>Enter an interactive configuration session where you can setup new remotes and manage existing ones. You may also set or remove a password to protect your configuration.</p>
<pre><code>rclone config [flags]</code></pre>
<h2 id="options">Options</h2>
<pre><code>  -h, --help   help for config</code></pre>
<p>See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
<h2 id="see-also">See Also</h2>
<ul>
<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
<li><a href="https://rclone.org/commands/rclone_config_create/">rclone config create</a> - Create a new remote with name, type and options.</li>
<li><a href="https://rclone.org/commands/rclone_config_delete/">rclone config delete</a> - Delete an existing remote.</li>
<li><a href="https://rclone.org/commands/rclone_config_disconnect/">rclone config disconnect</a> - Disconnects user from remote</li>
<li><a href="https://rclone.org/commands/rclone_config_dump/">rclone config dump</a> - Dump the config file as JSON.</li>
<li><a href="https://rclone.org/commands/rclone_config_edit/">rclone config edit</a> - Enter an interactive configuration session.</li>
<li><a href="https://rclone.org/commands/rclone_config_encryption/">rclone config encryption</a> - set, remove and check the encryption for the config file</li>
<li><a href="https://rclone.org/commands/rclone_config_file/">rclone config file</a> - Show path of configuration file in use.</li>
<li><a href="https://rclone.org/commands/rclone_config_password/">rclone config password</a> - Update password in an existing remote.</li>
<li><a href="https://rclone.org/commands/rclone_config_paths/">rclone config paths</a> - Show paths used for configuration, cache, temp etc.</li>
<li><a href="https://rclone.org/commands/rclone_config_providers/">rclone config providers</a> - List in JSON format all the providers and options.</li>
<li><a href="https://rclone.org/commands/rclone_config_reconnect/">rclone config reconnect</a> - Re-authenticates user with remote.</li>
<li><a href="https://rclone.org/commands/rclone_config_redacted/">rclone config redacted</a> - Print redacted (decrypted) config file, or the redacted config for a single remote.</li>
<li><a href="https://rclone.org/commands/rclone_config_show/">rclone config show</a> - Print (decrypted) config file, or the config for a single remote.</li>
<li><a href="https://rclone.org/commands/rclone_config_touch/">rclone config touch</a> - Ensure configuration file exists.</li>
<li><a href="https://rclone.org/commands/rclone_config_update/">rclone config update</a> - Update options in an existing remote.</li>
<li><a href="https://rclone.org/commands/rclone_config_userinfo/">rclone config userinfo</a> - Prints info about logged in user of remote.</li>
</ul>
<h1 id="rclone-copy">rclone copy</h1>
<p>Copy files from source to dest, skipping identical files.</p>
<h2 id="synopsis-1">Synopsis</h2>
<p>Copy the source to the destination. Does not transfer files that are identical on source and destination, testing by size and modification time or MD5SUM. Doesn't delete files from the destination. If you want to also delete files from destination, to make it match source, use the <a href="https://rclone.org/commands/rclone_sync/">sync</a> command instead.</p>
<p>Note that it is always the contents of the directory that is synced, not the directory itself. So when source:path is a directory, it's the contents of source:path that are copied, not the directory name and contents.</p>
<p>To copy single files, use the <a href="https://rclone.org/commands/rclone_copyto/">copyto</a> command instead.</p>
<p>If dest:path doesn't exist, it is created and the source:path contents go there.</p>
<p>For example</p>
<pre><code>rclone copy source:sourcepath dest:destpath</code></pre>
<p>Let's say there are two files in sourcepath</p>
<pre><code>sourcepath/one.txt
sourcepath/two.txt</code></pre>
<p>This copies them to</p>
<pre><code>destpath/one.txt
destpath/two.txt</code></pre>
<p>Not to</p>
<pre><code>destpath/sourcepath/one.txt
destpath/sourcepath/two.txt</code></pre>
<p>If you are familiar with <code>rsync</code>, rclone always works as if you had written a trailing <code>/</code> - meaning "copy the contents of this directory". This applies to all commands and whether you are talking about the source or destination.</p>
<p>See the <a href="https://rclone.org/docs/#no-traverse">--no-traverse</a> option for controlling whether rclone lists the destination directory or not. Supplying this option when copying a small number of files into a large destination can speed transfers up greatly.</p>
<p>For example, if you have many files in /path/to/src but only a few of them change every day, you can copy all the files which have changed recently very efficiently like this:</p>
<pre><code>rclone copy --max-age 24h --no-traverse /path/to/src remote:</code></pre>
<p>Rclone will sync the modification times of files and directories if the backend supports it. If metadata syncing is required then use the <code>--metadata</code> flag.</p>
<p>Note that the modification time and metadata for the root directory will <strong>not</strong> be synced. See https://github.com/rclone/rclone/issues/7652 for more info.</p>
<p><strong>Note</strong>: Use the <code>-P</code>/<code>--progress</code> flag to view real-time transfer statistics.</p>
<p><strong>Note</strong>: Use the <code>--dry-run</code> or the <code>--interactive</code>/<code>-i</code> flag to test without copying anything.</p>
<pre><code>rclone copy source:path dest:path [flags]</code></pre>
<h2 id="options-1">Options</h2>
<pre><code>      --create-empty-src-dirs   Create empty source dirs on destination after copy
  -h, --help                    help for copy</code></pre>
<p>Options shared with other commands are described next. See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
<h3 id="copy-options">Copy Options</h3>
<p>Flags for anything which can copy a file</p>
<pre><code>      --check-first                                 Do all the checks before starting transfers
  -c, --checksum                                    Check for changes with size &amp; checksum (if available, or fallback to size only)
      --compare-dest stringArray                    Include additional server-side paths during comparison
      --copy-dest stringArray                       Implies --compare-dest but also copies files from paths into destination
      --cutoff-mode HARD|SOFT|CAUTIOUS              Mode to stop transfers when reaching the max transfer limit HARD|SOFT|CAUTIOUS (default HARD)
      --ignore-case-sync                            Ignore case when synchronizing
      --ignore-checksum                             Skip post copy check of checksums
      --ignore-existing                             Skip all files that exist on destination
      --ignore-size                                 Ignore size when skipping use modtime or checksum
  -I, --ignore-times                                Don&#39;t skip items that match size and time - transfer all unconditionally
      --immutable                                   Do not modify files, fail if existing files have been modified
      --inplace                                     Download directly to destination file instead of atomic download to temp/rename
      --max-backlog int                             Maximum number of objects in sync or check backlog (default 10000)
      --max-duration Duration                       Maximum duration rclone will transfer data for (default 0s)
      --max-transfer SizeSuffix                     Maximum size of data to transfer (default off)
  -M, --metadata                                    If set, preserve metadata when copying objects
      --modify-window Duration                      Max time diff to be considered the same (default 1ns)
      --multi-thread-chunk-size SizeSuffix          Chunk size for multi-thread downloads / uploads, if not set by filesystem (default 64Mi)
      --multi-thread-cutoff SizeSuffix              Use multi-thread downloads for files above this size (default 256Mi)
      --multi-thread-streams int                    Number of streams to use for multi-thread downloads (default 4)
      --multi-thread-write-buffer-size SizeSuffix   In memory buffer size for writing when in multi-thread mode (default 128Ki)
      --no-check-dest                               Don&#39;t check the destination, copy regardless
      --no-traverse                                 Don&#39;t traverse destination file system on copy
      --no-update-dir-modtime                       Don&#39;t update directory modification times
      --no-update-modtime                           Don&#39;t update destination modtime if files identical
      --order-by string                             Instructions on how to order the transfers, e.g. &#39;size,descending&#39;
      --partial-suffix string                       Add partial-suffix to temporary file name when --inplace is not used (default &quot;.partial&quot;)
      --refresh-times                               Refresh the modtime of remote files
      --server-side-across-configs                  Allow server-side operations (e.g. copy) to work across different configs
      --size-only                                   Skip based on size only, not modtime or checksum
      --streaming-upload-cutoff SizeSuffix          Cutoff for switching to chunked upload if file size is unknown, upload starts after reaching cutoff or when file ends (default 100Ki)
  -u, --update                                      Skip files that are newer on the destination</code></pre>
<h3 id="important-options">Important Options</h3>
<p>Important flags useful for most commands</p>
<pre><code>  -n, --dry-run         Do a trial run with no permanent changes
  -i, --interactive     Enable interactive mode
  -v, --verbose count   Print lots more stuff (repeat for more)</code></pre>
<h3 id="filter-options">Filter Options</h3>
<p>Flags for filtering directory listings</p>
<pre><code>      --delete-excluded                     Delete files on dest excluded from sync
      --exclude stringArray                 Exclude files matching pattern
      --exclude-from stringArray            Read file exclude patterns from file (use - to read from stdin)
      --exclude-if-present stringArray      Exclude directories if filename is present
      --files-from stringArray              Read list of source-file names from file (use - to read from stdin)
      --files-from-raw stringArray          Read list of source-file names from file without any processing of lines (use - to read from stdin)
  -f, --filter stringArray                  Add a file filtering rule
      --filter-from stringArray             Read file filtering patterns from a file (use - to read from stdin)
      --ignore-case                         Ignore case in filters (case insensitive)
      --include stringArray                 Include files matching pattern
      --include-from stringArray            Read file include patterns from file (use - to read from stdin)
      --max-age Duration                    Only transfer files younger than this in s or suffix ms|s|m|h|d|w|M|y (default off)
      --max-depth int                       If set limits the recursion depth to this (default -1)
      --max-size SizeSuffix                 Only transfer files smaller than this in KiB or suffix B|K|M|G|T|P (default off)
      --metadata-exclude stringArray        Exclude metadatas matching pattern
      --metadata-exclude-from stringArray   Read metadata exclude patterns from file (use - to read from stdin)
      --metadata-filter stringArray         Add a metadata filtering rule
      --metadata-filter-from stringArray    Read metadata filtering patterns from a file (use - to read from stdin)
      --metadata-include stringArray        Include metadatas matching pattern
      --metadata-include-from stringArray   Read metadata include patterns from file (use - to read from stdin)
      --min-age Duration                    Only transfer files older than this in s or suffix ms|s|m|h|d|w|M|y (default off)
      --min-size SizeSuffix                 Only transfer files bigger than this in KiB or suffix B|K|M|G|T|P (default off)</code></pre>
<h3 id="listing-options">Listing Options</h3>
<p>Flags for listing directories</p>
<pre><code>      --default-time Time   Time to show if modtime is unknown for files and directories (default 2000-01-01T00:00:00Z)
      --fast-list           Use recursive list if available; uses more memory but fewer transactions</code></pre>
<h2 id="see-also-1">See Also</h2>
<ul>
<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
</ul>
<h1 id="rclone-sync">rclone sync</h1>
<p>Make source and dest identical, modifying destination only.</p>
<h2 id="synopsis-2">Synopsis</h2>
<p>Sync the source to the destination, changing the destination only. Doesn't transfer files that are identical on source and destination, testing by size and modification time or MD5SUM. Destination is updated to match source, including deleting files if necessary (except duplicate objects, see below). If you don't want to delete files from destination, use the <a href="https://rclone.org/commands/rclone_copy/">copy</a> command instead.</p>
<p><strong>Important</strong>: Since this can cause data loss, test first with the <code>--dry-run</code> or the <code>--interactive</code>/<code>-i</code> flag.</p>
<pre><code>rclone sync --interactive SOURCE remote:DESTINATION</code></pre>
<p>Note that files in the destination won't be deleted if there were any errors at any point. Duplicate objects (files with the same name, on those providers that support it) are also not yet handled.</p>
<p>It is always the contents of the directory that is synced, not the directory itself. So when source:path is a directory, it's the contents of source:path that are copied, not the directory name and contents. See extended explanation in the <a href="https://rclone.org/commands/rclone_copy/">copy</a> command if unsure.</p>
<p>If dest:path doesn't exist, it is created and the source:path contents go there.</p>
<p>It is not possible to sync overlapping remotes. However, you may exclude the destination from the sync with a filter rule or by putting an exclude-if-present file inside the destination directory and sync to a destination that is inside the source directory.</p>
<p>Rclone will sync the modification times of files and directories if the backend supports it. If metadata syncing is required then use the <code>--metadata</code> flag.</p>
<p>Note that the modification time and metadata for the root directory will <strong>not</strong> be synced. See https://github.com/rclone/rclone/issues/7652 for more info.</p>
<p><strong>Note</strong>: Use the <code>-P</code>/<code>--progress</code> flag to view real-time transfer statistics</p>
<p><strong>Note</strong>: Use the <code>rclone dedupe</code> command to deal with "Duplicate object/directory found in source/destination - ignoring" errors. See <a href="https://forum.rclone.org/t/sync-not-clearing-duplicates/14372">this forum post</a> for more info.</p>
<h1 id="logger-flags">Logger Flags</h1>
<p>The <code>--differ</code>, <code>--missing-on-dst</code>, <code>--missing-on-src</code>, <code>--match</code> and <code>--error</code> flags write paths, one per line, to the file name (or stdout if it is <code>-</code>) supplied. What they write is described in the help below. For example <code>--differ</code> will write all paths which are present on both the source and destination but different.</p>
<p>The <code>--combined</code> flag will write a file (or stdout) which contains all file paths with a symbol and then a space and then the path to tell you what happened to it. These are reminiscent of diff files.</p>
<ul>
<li><code>= path</code> means path was found in source and destination and was identical</li>
<li>`- path` means path was missing on the source, so only in the destination</li>
<li>`+ path` means path was missing on the destination, so only in the source</li>
<li>`* path` means path was present in source and destination but different.</li>
<li><code>! path</code> means there was an error reading or hashing the source or dest.</li>
</ul>
<p>The <code>--dest-after</code> flag writes a list file using the same format flags as <a href="https://rclone.org/commands/rclone_lsf/#synopsis"><code>lsf</code></a> (including <a href="https://rclone.org/commands/rclone_lsf/#synopsis">customizable options for hash, modtime, etc.</a>) Conceptually it is similar to rsync's <code>--itemize-changes</code>, but not identical -- it should output an accurate list of what will be on the destination after the sync.</p>
<p>Note that these logger flags have a few limitations, and certain scenarios are not currently supported:</p>
<ul>
<li><code>--max-duration</code> / <code>CutoffModeHard</code></li>
<li><code>--compare-dest</code> / <code>--copy-dest</code></li>
<li>server-side moves of an entire dir at once</li>
<li>High-level retries, because there would be duplicates (use <code>--retries 1</code> to disable)</li>
<li>Possibly some unusual error scenarios</li>
</ul>
<p>Note also that each file is logged during the sync, as opposed to after, so it is most useful as a predictor of what SHOULD happen to each file (which may or may not match what actually DID.)</p>
<pre><code>rclone sync source:path dest:path [flags]</code></pre>
<h2 id="options-2">Options</h2>
<pre><code>      --absolute                Put a leading / in front of path names
      --combined string         Make a combined report of changes to this file
      --create-empty-src-dirs   Create empty source dirs on destination after sync
      --csv                     Output in CSV format
      --dest-after string       Report all files that exist on the dest post-sync
      --differ string           Report all non-matching files to this file
  -d, --dir-slash               Append a slash to directory names (default true)
      --dirs-only               Only list directories
      --error string            Report all files with errors (hashing or reading) to this file
      --files-only              Only list files (default true)
  -F, --format string           Output format - see lsf help for details (default &quot;p&quot;)
      --hash h                  Use this hash when h is used in the format MD5|SHA-1|DropboxHash (default &quot;md5&quot;)
  -h, --help                    help for sync
      --match string            Report all matching files to this file
      --missing-on-dst string   Report all files missing from the destination to this file
      --missing-on-src string   Report all files missing from the source to this file
  -s, --separator string        Separator for the items in the format (default &quot;;&quot;)
  -t, --timeformat string       Specify a custom time format, or &#39;max&#39; for max precision supported by remote (default: 2006-01-02 15:04:05)</code></pre>
<p>Options shared with other commands are described next. See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
<h3 id="copy-options-1">Copy Options</h3>
<p>Flags for anything which can copy a file</p>
<pre><code>      --check-first                                 Do all the checks before starting transfers
  -c, --checksum                                    Check for changes with size &amp; checksum (if available, or fallback to size only)
      --compare-dest stringArray                    Include additional server-side paths during comparison
      --copy-dest stringArray                       Implies --compare-dest but also copies files from paths into destination
      --cutoff-mode HARD|SOFT|CAUTIOUS              Mode to stop transfers when reaching the max transfer limit HARD|SOFT|CAUTIOUS (default HARD)
      --ignore-case-sync                            Ignore case when synchronizing
      --ignore-checksum                             Skip post copy check of checksums
      --ignore-existing                             Skip all files that exist on destination
      --ignore-size                                 Ignore size when skipping use modtime or checksum
  -I, --ignore-times                                Don&#39;t skip items that match size and time - transfer all unconditionally
      --immutable                                   Do not modify files, fail if existing files have been modified
      --inplace                                     Download directly to destination file instead of atomic download to temp/rename
      --max-backlog int                             Maximum number of objects in sync or check backlog (default 10000)
      --max-duration Duration                       Maximum duration rclone will transfer data for (default 0s)
      --max-transfer SizeSuffix                     Maximum size of data to transfer (default off)
  -M, --metadata                                    If set, preserve metadata when copying objects
      --modify-window Duration                      Max time diff to be considered the same (default 1ns)
      --multi-thread-chunk-size SizeSuffix          Chunk size for multi-thread downloads / uploads, if not set by filesystem (default 64Mi)
      --multi-thread-cutoff SizeSuffix              Use multi-thread downloads for files above this size (default 256Mi)
      --multi-thread-streams int                    Number of streams to use for multi-thread downloads (default 4)
      --multi-thread-write-buffer-size SizeSuffix   In memory buffer size for writing when in multi-thread mode (default 128Ki)
      --no-check-dest                               Don&#39;t check the destination, copy regardless
      --no-traverse                                 Don&#39;t traverse destination file system on copy
      --no-update-dir-modtime                       Don&#39;t update directory modification times
      --no-update-modtime                           Don&#39;t update destination modtime if files identical
      --order-by string                             Instructions on how to order the transfers, e.g. &#39;size,descending&#39;
      --partial-suffix string                       Add partial-suffix to temporary file name when --inplace is not used (default &quot;.partial&quot;)
      --refresh-times                               Refresh the modtime of remote files
      --server-side-across-configs                  Allow server-side operations (e.g. copy) to work across different configs
      --size-only                                   Skip based on size only, not modtime or checksum
      --streaming-upload-cutoff SizeSuffix          Cutoff for switching to chunked upload if file size is unknown, upload starts after reaching cutoff or when file ends (default 100Ki)
  -u, --update                                      Skip files that are newer on the destination</code></pre>
<h3 id="sync-options">Sync Options</h3>
<p>Flags used for sync commands</p>
<pre><code>      --backup-dir string               Make backups into hierarchy based in DIR
      --delete-after                    When synchronizing, delete files on destination after transferring (default)
      --delete-before                   When synchronizing, delete files on destination before transferring
      --delete-during                   When synchronizing, delete files during transfer
      --fix-case                        Force rename of case insensitive dest to match source
      --ignore-errors                   Delete even if there are I/O errors
      --max-delete int                  When synchronizing, limit the number of deletes (default -1)
      --max-delete-size SizeSuffix      When synchronizing, limit the total size of deletes (default off)
      --suffix string                   Suffix to add to changed files
      --suffix-keep-extension           Preserve the extension when using --suffix
      --track-renames                   When synchronizing, track file renames and do a server-side move if possible
      --track-renames-strategy string   Strategies to use when synchronizing using track-renames hash|modtime|leaf (default &quot;hash&quot;)</code></pre>
<h3 id="important-options-1">Important Options</h3>
<p>Important flags useful for most commands</p>
<pre><code>  -n, --dry-run         Do a trial run with no permanent changes
  -i, --interactive     Enable interactive mode
  -v, --verbose count   Print lots more stuff (repeat for more)</code></pre>
<h3 id="filter-options-1">Filter Options</h3>
<p>Flags for filtering directory listings</p>
<pre><code>      --delete-excluded                     Delete files on dest excluded from sync
      --exclude stringArray                 Exclude files matching pattern
      --exclude-from stringArray            Read file exclude patterns from file (use - to read from stdin)
      --exclude-if-present stringArray      Exclude directories if filename is present
      --files-from stringArray              Read list of source-file names from file (use - to read from stdin)
      --files-from-raw stringArray          Read list of source-file names from file without any processing of lines (use - to read from stdin)
  -f, --filter stringArray                  Add a file filtering rule
      --filter-from stringArray             Read file filtering patterns from a file (use - to read from stdin)
      --ignore-case                         Ignore case in filters (case insensitive)
      --include stringArray                 Include files matching pattern
      --include-from stringArray            Read file include patterns from file (use - to read from stdin)
      --max-age Duration                    Only transfer files younger than this in s or suffix ms|s|m|h|d|w|M|y (default off)
      --max-depth int                       If set limits the recursion depth to this (default -1)
      --max-size SizeSuffix                 Only transfer files smaller than this in KiB or suffix B|K|M|G|T|P (default off)
      --metadata-exclude stringArray        Exclude metadatas matching pattern
      --metadata-exclude-from stringArray   Read metadata exclude patterns from file (use - to read from stdin)
      --metadata-filter stringArray         Add a metadata filtering rule
      --metadata-filter-from stringArray    Read metadata filtering patterns from a file (use - to read from stdin)
      --metadata-include stringArray        Include metadatas matching pattern
      --metadata-include-from stringArray   Read metadata include patterns from file (use - to read from stdin)
      --min-age Duration                    Only transfer files older than this in s or suffix ms|s|m|h|d|w|M|y (default off)
      --min-size SizeSuffix                 Only transfer files bigger than this in KiB or suffix B|K|M|G|T|P (default off)</code></pre>
<h3 id="listing-options-1">Listing Options</h3>
<p>Flags for listing directories</p>
<pre><code>      --default-time Time   Time to show if modtime is unknown for files and directories (default 2000-01-01T00:00:00Z)
      --fast-list           Use recursive list if available; uses more memory but fewer transactions</code></pre>
<h2 id="see-also-2">See Also</h2>
<ul>
<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
</ul>
<h1 id="rclone-move">rclone move</h1>
<p>Move files from source to dest.</p>
<h2 id="synopsis-3">Synopsis</h2>
<p>Moves the contents of the source directory to the destination directory. Rclone will error if the source and destination overlap and the remote does not support a server-side directory move operation.</p>
<p>To move single files, use the <a href="https://rclone.org/commands/rclone_moveto/">moveto</a> command instead.</p>
<p>If no filters are in use and if possible this will server-side move <code>source:path</code> into <code>dest:path</code>. After this <code>source:path</code> will no longer exist.</p>
<p>Otherwise for each file in <code>source:path</code> selected by the filters (if any) this will move it into <code>dest:path</code>. If possible a server-side move will be used, otherwise it will copy it (server-side if possible) into <code>dest:path</code> then delete the original (if no errors on copy) in <code>source:path</code>.</p>
<p>If you want to delete empty source directories after move, use the <code>--delete-empty-src-dirs</code> flag.</p>
<p>See the <a href="https://rclone.org/docs/#no-traverse">--no-traverse</a> option for controlling whether rclone lists the destination directory or not. Supplying this option when moving a small number of files into a large destination can speed transfers up greatly.</p>
<p>Rclone will sync the modification times of files and directories if the backend supports it. If metadata syncing is required then use the <code>--metadata</code> flag.</p>
<p>Note that the modification time and metadata for the root directory will <strong>not</strong> be synced. See https://github.com/rclone/rclone/issues/7652 for more info.</p>
<p><strong>Important</strong>: Since this can cause data loss, test first with the <code>--dry-run</code> or the <code>--interactive</code>/<code>-i</code> flag.</p>
<p><strong>Note</strong>: Use the <code>-P</code>/<code>--progress</code> flag to view real-time transfer statistics.</p>
<pre><code>rclone move source:path dest:path [flags]</code></pre>
<h2 id="options-3">Options</h2>
<pre><code>      --create-empty-src-dirs   Create empty source dirs on destination after move
      --delete-empty-src-dirs   Delete empty source dirs after move
  -h, --help                    help for move</code></pre>
<p>Options shared with other commands are described next. See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
<h3 id="copy-options-2">Copy Options</h3>
<p>Flags for anything which can copy a file</p>
<pre><code>      --check-first                                 Do all the checks before starting transfers
  -c, --checksum                                    Check for changes with size &amp; checksum (if available, or fallback to size only)
      --compare-dest stringArray                    Include additional server-side paths during comparison
      --copy-dest stringArray                       Implies --compare-dest but also copies files from paths into destination
      --cutoff-mode HARD|SOFT|CAUTIOUS              Mode to stop transfers when reaching the max transfer limit HARD|SOFT|CAUTIOUS (default HARD)
      --ignore-case-sync                            Ignore case when synchronizing
      --ignore-checksum                             Skip post copy check of checksums
      --ignore-existing                             Skip all files that exist on destination
      --ignore-size                                 Ignore size when skipping use modtime or checksum
  -I, --ignore-times                                Don&#39;t skip items that match size and time - transfer all unconditionally
      --immutable                                   Do not modify files, fail if existing files have been modified
      --inplace                                     Download directly to destination file instead of atomic download to temp/rename
      --max-backlog int                             Maximum number of objects in sync or check backlog (default 10000)
      --max-duration Duration                       Maximum duration rclone will transfer data for (default 0s)
      --max-transfer SizeSuffix                     Maximum size of data to transfer (default off)
  -M, --metadata                                    If set, preserve metadata when copying objects
      --modify-window Duration                      Max time diff to be considered the same (default 1ns)
      --multi-thread-chunk-size SizeSuffix          Chunk size for multi-thread downloads / uploads, if not set by filesystem (default 64Mi)
      --multi-thread-cutoff SizeSuffix              Use multi-thread downloads for files above this size (default 256Mi)
      --multi-thread-streams int                    Number of streams to use for multi-thread downloads (default 4)
      --multi-thread-write-buffer-size SizeSuffix   In memory buffer size for writing when in multi-thread mode (default 128Ki)
      --no-check-dest                               Don&#39;t check the destination, copy regardless
      --no-traverse                                 Don&#39;t traverse destination file system on copy
      --no-update-dir-modtime                       Don&#39;t update directory modification times
      --no-update-modtime                           Don&#39;t update destination modtime if files identical
      --order-by string                             Instructions on how to order the transfers, e.g. &#39;size,descending&#39;
      --partial-suffix string                       Add partial-suffix to temporary file name when --inplace is not used (default &quot;.partial&quot;)
      --refresh-times                               Refresh the modtime of remote files
      --server-side-across-configs                  Allow server-side operations (e.g. copy) to work across different configs
      --size-only                                   Skip based on size only, not modtime or checksum
      --streaming-upload-cutoff SizeSuffix          Cutoff for switching to chunked upload if file size is unknown, upload starts after reaching cutoff or when file ends (default 100Ki)
  -u, --update                                      Skip files that are newer on the destination</code></pre>
<h3 id="important-options-2">Important Options</h3>
<p>Important flags useful for most commands</p>
<pre><code>  -n, --dry-run         Do a trial run with no permanent changes
  -i, --interactive     Enable interactive mode
  -v, --verbose count   Print lots more stuff (repeat for more)</code></pre>
<h3 id="filter-options-2">Filter Options</h3>
<p>Flags for filtering directory listings</p>
<pre><code>      --delete-excluded                     Delete files on dest excluded from sync
      --exclude stringArray                 Exclude files matching pattern
      --exclude-from stringArray            Read file exclude patterns from file (use - to read from stdin)
      --exclude-if-present stringArray      Exclude directories if filename is present
      --files-from stringArray              Read list of source-file names from file (use - to read from stdin)
      --files-from-raw stringArray          Read list of source-file names from file without any processing of lines (use - to read from stdin)
  -f, --filter stringArray                  Add a file filtering rule
      --filter-from stringArray             Read file filtering patterns from a file (use - to read from stdin)
      --ignore-case                         Ignore case in filters (case insensitive)
      --include stringArray                 Include files matching pattern
      --include-from stringArray            Read file include patterns from file (use - to read from stdin)
      --max-age Duration                    Only transfer files younger than this in s or suffix ms|s|m|h|d|w|M|y (default off)
      --max-depth int                       If set limits the recursion depth to this (default -1)
      --max-size SizeSuffix                 Only transfer files smaller than this in KiB or suffix B|K|M|G|T|P (default off)
      --metadata-exclude stringArray        Exclude metadatas matching pattern
      --metadata-exclude-from stringArray   Read metadata exclude patterns from file (use - to read from stdin)
      --metadata-filter stringArray         Add a metadata filtering rule
      --metadata-filter-from stringArray    Read metadata filtering patterns from a file (use - to read from stdin)
      --metadata-include stringArray        Include metadatas matching pattern
      --metadata-include-from stringArray   Read metadata include patterns from file (use - to read from stdin)
      --min-age Duration                    Only transfer files older than this in s or suffix ms|s|m|h|d|w|M|y (default off)
      --min-size SizeSuffix                 Only transfer files bigger than this in KiB or suffix B|K|M|G|T|P (default off)</code></pre>
<h3 id="listing-options-2">Listing Options</h3>
<p>Flags for listing directories</p>
<pre><code>      --default-time Time   Time to show if modtime is unknown for files and directories (default 2000-01-01T00:00:00Z)
      --fast-list           Use recursive list if available; uses more memory but fewer transactions</code></pre>
<h2 id="see-also-3">See Also</h2>
<ul>
<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
</ul>
<h1 id="rclone-delete">rclone delete</h1>
<p>Remove the files in path.</p>
<h2 id="synopsis-4">Synopsis</h2>
<p>Remove the files in path. Unlike <a href="https://rclone.org/commands/rclone_purge/">purge</a> it obeys include/exclude filters so can be used to selectively delete files.</p>
<p><code>rclone delete</code> only deletes files but leaves the directory structure alone. If you want to delete a directory and all of its contents use the <a href="https://rclone.org/commands/rclone_purge/">purge</a> command.</p>
<p>If you supply the <code>--rmdirs</code> flag, it will remove all empty directories along with it. You can also use the separate command <a href="https://rclone.org/commands/rclone_rmdir/">rmdir</a> or <a href="https://rclone.org/commands/rclone_rmdirs/">rmdirs</a> to delete empty directories only.</p>
<p>For example, to delete all files bigger than 100 MiB, you may first want to check what would be deleted (use either):</p>
<pre><code>rclone --min-size 100M lsl remote:path
rclone --dry-run --min-size 100M delete remote:path</code></pre>
<p>Then proceed with the actual delete:</p>
<pre><code>rclone --min-size 100M delete remote:path</code></pre>
<p>That reads "delete everything with a minimum size of 100 MiB", hence delete all files bigger than 100 MiB.</p>
<p><strong>Important</strong>: Since this can cause data loss, test first with the <code>--dry-run</code> or the <code>--interactive</code>/<code>-i</code> flag.</p>
<pre><code>rclone delete remote:path [flags]</code></pre>
<h2 id="options-4">Options</h2>
<pre><code>  -h, --help     help for delete
      --rmdirs   rmdirs removes empty directories but leaves root intact</code></pre>
<p>Options shared with other commands are described next. See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
<h3 id="important-options-3">Important Options</h3>
<p>Important flags useful for most commands</p>
<pre><code>  -n, --dry-run         Do a trial run with no permanent changes
  -i, --interactive     Enable interactive mode
  -v, --verbose count   Print lots more stuff (repeat for more)</code></pre>
<h3 id="filter-options-3">Filter Options</h3>
<p>Flags for filtering directory listings</p>
<pre><code>      --delete-excluded                     Delete files on dest excluded from sync
      --exclude stringArray                 Exclude files matching pattern
      --exclude-from stringArray            Read file exclude patterns from file (use - to read from stdin)
      --exclude-if-present stringArray      Exclude directories if filename is present
      --files-from stringArray              Read list of source-file names from file (use - to read from stdin)
      --files-from-raw stringArray          Read list of source-file names from file without any processing of lines (use - to read from stdin)
  -f, --filter stringArray                  Add a file filtering rule
      --filter-from stringArray             Read file filtering patterns from a file (use - to read from stdin)
      --ignore-case                         Ignore case in filters (case insensitive)
      --include stringArray                 Include files matching pattern
      --include-from stringArray            Read file include patterns from file (use - to read from stdin)
      --max-age Duration                    Only transfer files younger than this in s or suffix ms|s|m|h|d|w|M|y (default off)
      --max-depth int                       If set limits the recursion depth to this (default -1)
      --max-size SizeSuffix                 Only transfer files smaller than this in KiB or suffix B|K|M|G|T|P (default off)
      --metadata-exclude stringArray        Exclude metadatas matching pattern
      --metadata-exclude-from stringArray   Read metadata exclude patterns from file (use - to read from stdin)
      --metadata-filter stringArray         Add a metadata filtering rule
      --metadata-filter-from stringArray    Read metadata filtering patterns from a file (use - to read from stdin)
      --metadata-include stringArray        Include metadatas matching pattern
      --metadata-include-from stringArray   Read metadata include patterns from file (use - to read from stdin)
      --min-age Duration                    Only transfer files older than this in s or suffix ms|s|m|h|d|w|M|y (default off)
      --min-size SizeSuffix                 Only transfer files bigger than this in KiB or suffix B|K|M|G|T|P (default off)</code></pre>
<h3 id="listing-options-3">Listing Options</h3>
<p>Flags for listing directories</p>
<pre><code>      --default-time Time   Time to show if modtime is unknown for files and directories (default 2000-01-01T00:00:00Z)
      --fast-list           Use recursive list if available; uses more memory but fewer transactions</code></pre>
<h2 id="see-also-4">See Also</h2>
<ul>
<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
</ul>
<h1 id="rclone-purge">rclone purge</h1>
<p>Remove the path and all of its contents.</p>
<h2 id="synopsis-5">Synopsis</h2>
<p>Remove the path and all of its contents. Note that this does not obey include/exclude filters - everything will be removed. Use the <a href="https://rclone.org/commands/rclone_delete/">delete</a> command if you want to selectively delete files. To delete empty directories only, use command <a href="https://rclone.org/commands/rclone_rmdir/">rmdir</a> or <a href="https://rclone.org/commands/rclone_rmdirs/">rmdirs</a>.</p>
<p><strong>Important</strong>: Since this can cause data loss, test first with the <code>--dry-run</code> or the <code>--interactive</code>/<code>-i</code> flag.</p>
<pre><code>rclone purge remote:path [flags]</code></pre>
<h2 id="options-5">Options</h2>
<pre><code>  -h, --help   help for purge</code></pre>
<p>Options shared with other commands are described next. See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
<h3 id="important-options-4">Important Options</h3>
<p>Important flags useful for most commands</p>
<pre><code>  -n, --dry-run         Do a trial run with no permanent changes
  -i, --interactive     Enable interactive mode
  -v, --verbose count   Print lots more stuff (repeat for more)</code></pre>
<h2 id="see-also-5">See Also</h2>
<ul>
<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
</ul>
<h1 id="rclone-mkdir">rclone mkdir</h1>
<p>Make the path if it doesn't already exist.</p>
<pre><code>rclone mkdir remote:path [flags]</code></pre>
<h2 id="options-6">Options</h2>
<pre><code>  -h, --help   help for mkdir</code></pre>
<p>Options shared with other commands are described next. See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
<h3 id="important-options-5">Important Options</h3>
<p>Important flags useful for most commands</p>
<pre><code>  -n, --dry-run         Do a trial run with no permanent changes
  -i, --interactive     Enable interactive mode
  -v, --verbose count   Print lots more stuff (repeat for more)</code></pre>
<h2 id="see-also-6">See Also</h2>
<ul>
<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
</ul>
<h1 id="rclone-rmdir">rclone rmdir</h1>
<p>Remove the empty directory at path.</p>
<h2 id="synopsis-6">Synopsis</h2>
<p>This removes empty directory given by path. Will not remove the path if it has any objects in it, not even empty subdirectories. Use command <a href="https://rclone.org/commands/rclone_rmdirs/">rmdirs</a> (or <a href="https://rclone.org/commands/rclone_delete/">delete</a> with option <code>--rmdirs</code>) to do that.</p>
<p>To delete a path and any objects in it, use <a href="https://rclone.org/commands/rclone_purge/">purge</a> command.</p>
<pre><code>rclone rmdir remote:path [flags]</code></pre>
<h2 id="options-7">Options</h2>
<pre><code>  -h, --help   help for rmdir</code></pre>
<p>Options shared with other commands are described next. See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
<h3 id="important-options-6">Important Options</h3>
<p>Important flags useful for most commands</p>
<pre><code>  -n, --dry-run         Do a trial run with no permanent changes
  -i, --interactive     Enable interactive mode
  -v, --verbose count   Print lots more stuff (repeat for more)</code></pre>
<h2 id="see-also-7">See Also</h2>
<ul>
<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
</ul>
<h1 id="rclone-check">rclone check</h1>
<p>Checks the files in the source and destination match.</p>
<h2 id="synopsis-7">Synopsis</h2>
<p>Checks the files in the source and destination match. It compares sizes and hashes (MD5 or SHA1) and logs a report of files that don't match. It doesn't alter the source or destination.</p>
<p>For the <a href="https://rclone.org/crypt/">crypt</a> remote there is a dedicated command, <a href="https://rclone.org/commands/rclone_cryptcheck/">cryptcheck</a>, that are able to check the checksums of the encrypted files.</p>
<p>If you supply the <code>--size-only</code> flag, it will only compare the sizes not the hashes as well. Use this for a quick check.</p>
<p>If you supply the <code>--download</code> flag, it will download the data from both remotes and check them against each other on the fly. This can be useful for remotes that don't support hashes or if you really want to check all the data.</p>
<p>If you supply the <code>--checkfile HASH</code> flag with a valid hash name, the <code>source:path</code> must point to a text file in the SUM format.</p>
<p>If you supply the <code>--one-way</code> flag, it will only check that files in the source match the files in the destination, not the other way around. This means that extra files in the destination that are not in the source will not be detected.</p>
<p>The <code>--differ</code>, <code>--missing-on-dst</code>, <code>--missing-on-src</code>, <code>--match</code> and <code>--error</code> flags write paths, one per line, to the file name (or stdout if it is <code>-</code>) supplied. What they write is described in the help below. For example <code>--differ</code> will write all paths which are present on both the source and destination but different.</p>
<p>The <code>--combined</code> flag will write a file (or stdout) which contains all file paths with a symbol and then a space and then the path to tell you what happened to it. These are reminiscent of diff files.</p>
<ul>
<li><code>= path</code> means path was found in source and destination and was identical</li>
<li>`- path` means path was missing on the source, so only in the destination</li>
<li>`+ path` means path was missing on the destination, so only in the source</li>
<li>`* path` means path was present in source and destination but different.</li>
<li><code>! path</code> means there was an error reading or hashing the source or dest.</li>
</ul>
<p>The default number of parallel checks is 8. See the <a href="https://rclone.org/docs/#checkers-n">--checkers=N</a> option for more information.</p>
<pre><code>rclone check source:path dest:path [flags]</code></pre>
<h2 id="options-8">Options</h2>
<pre><code>  -C, --checkfile string        Treat source:path as a SUM file with hashes of given type
      --combined string         Make a combined report of changes to this file
      --differ string           Report all non-matching files to this file
      --download                Check by downloading rather than with hash
      --error string            Report all files with errors (hashing or reading) to this file
  -h, --help                    help for check
      --match string            Report all matching files to this file
      --missing-on-dst string   Report all files missing from the destination to this file
      --missing-on-src string   Report all files missing from the source to this file
      --one-way                 Check one way only, source files must exist on remote</code></pre>
<p>Options shared with other commands are described next. See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
<h3 id="check-options">Check Options</h3>
<p>Flags used for check commands</p>
<pre><code>      --max-backlog int   Maximum number of objects in sync or check backlog (default 10000)</code></pre>
<h3 id="filter-options-4">Filter Options</h3>
<p>Flags for filtering directory listings</p>
<pre><code>      --delete-excluded                     Delete files on dest excluded from sync
      --exclude stringArray                 Exclude files matching pattern
      --exclude-from stringArray            Read file exclude patterns from file (use - to read from stdin)
      --exclude-if-present stringArray      Exclude directories if filename is present
      --files-from stringArray              Read list of source-file names from file (use - to read from stdin)
      --files-from-raw stringArray          Read list of source-file names from file without any processing of lines (use - to read from stdin)
  -f, --filter stringArray                  Add a file filtering rule
      --filter-from stringArray             Read file filtering patterns from a file (use - to read from stdin)
      --ignore-case                         Ignore case in filters (case insensitive)
      --include stringArray                 Include files matching pattern
      --include-from stringArray            Read file include patterns from file (use - to read from stdin)
      --max-age Duration                    Only transfer files younger than this in s or suffix ms|s|m|h|d|w|M|y (default off)
      --max-depth int                       If set limits the recursion depth to this (default -1)
      --max-size SizeSuffix                 Only transfer files smaller than this in KiB or suffix B|K|M|G|T|P (default off)
      --metadata-exclude stringArray        Exclude metadatas matching pattern
      --metadata-exclude-from stringArray   Read metadata exclude patterns from file (use - to read from stdin)
      --metadata-filter stringArray         Add a metadata filtering rule
      --metadata-filter-from stringArray    Read metadata filtering patterns from a file (use - to read from stdin)
      --metadata-include stringArray        Include metadatas matching pattern
      --metadata-include-from stringArray   Read metadata include patterns from file (use - to read from stdin)
      --min-age Duration                    Only transfer files older than this in s or suffix ms|s|m|h|d|w|M|y (default off)
      --min-size SizeSuffix                 Only transfer files bigger than this in KiB or suffix B|K|M|G|T|P (default off)</code></pre>
<h3 id="listing-options-4">Listing Options</h3>
<p>Flags for listing directories</p>
<pre><code>      --default-time Time   Time to show if modtime is unknown for files and directories (default 2000-01-01T00:00:00Z)
      --fast-list           Use recursive list if available; uses more memory but fewer transactions</code></pre>
<h2 id="see-also-8">See Also</h2>
<ul>
<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
</ul>
<h1 id="rclone-ls">rclone ls</h1>
<p>List the objects in the path with size and path.</p>
<h2 id="synopsis-8">Synopsis</h2>
<p>Lists the objects in the source path to standard output in a human readable format with size and path. Recurses by default.</p>
<p>Eg</p>
<pre><code>$ rclone ls swift:bucket
    60295 bevajer5jef
    90613 canole
    94467 diwogej7
    37600 fubuwic</code></pre>
<p>Any of the filtering options can be applied to this command.</p>
<p>There are several related list commands</p>
<ul>
<li><code>ls</code> to list size and path of objects only</li>
<li><code>lsl</code> to list modification time, size and path of objects only</li>
<li><code>lsd</code> to list directories only</li>
<li><code>lsf</code> to list objects and directories in easy to parse format</li>
<li><code>lsjson</code> to list objects and directories in JSON format</li>
</ul>
<p><code>ls</code>,<code>lsl</code>,<code>lsd</code> are designed to be human-readable. <code>lsf</code> is designed to be human and machine-readable. <code>lsjson</code> is designed to be machine-readable.</p>
<p>Note that <code>ls</code> and <code>lsl</code> recurse by default - use <code>--max-depth 1</code> to stop the recursion.</p>
<p>The other list commands <code>lsd</code>,<code>lsf</code>,<code>lsjson</code> do not recurse by default - use <code>-R</code> to make them recurse.</p>
<p>Listing a nonexistent directory will produce an error except for remotes which can't have empty directories (e.g. s3, swift, or gcs - the bucket-based remotes).</p>
<pre><code>rclone ls remote:path [flags]</code></pre>
<h2 id="options-9">Options</h2>
<pre><code>  -h, --help   help for ls</code></pre>
<p>Options shared with other commands are described next. See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
<h3 id="filter-options-5">Filter Options</h3>
<p>Flags for filtering directory listings</p>
<pre><code>      --delete-excluded                     Delete files on dest excluded from sync
      --exclude stringArray                 Exclude files matching pattern
      --exclude-from stringArray            Read file exclude patterns from file (use - to read from stdin)
      --exclude-if-present stringArray      Exclude directories if filename is present
      --files-from stringArray              Read list of source-file names from file (use - to read from stdin)
      --files-from-raw stringArray          Read list of source-file names from file without any processing of lines (use - to read from stdin)
  -f, --filter stringArray                  Add a file filtering rule
      --filter-from stringArray             Read file filtering patterns from a file (use - to read from stdin)
      --ignore-case                         Ignore case in filters (case insensitive)
      --include stringArray                 Include files matching pattern
      --include-from stringArray            Read file include patterns from file (use - to read from stdin)
      --max-age Duration                    Only transfer files younger than this in s or suffix ms|s|m|h|d|w|M|y (default off)
      --max-depth int                       If set limits the recursion depth to this (default -1)
      --max-size SizeSuffix                 Only transfer files smaller than this in KiB or suffix B|K|M|G|T|P (default off)
      --metadata-exclude stringArray        Exclude metadatas matching pattern
      --metadata-exclude-from stringArray   Read metadata exclude patterns from file (use - to read from stdin)
      --metadata-filter stringArray         Add a metadata filtering rule
      --metadata-filter-from stringArray    Read metadata filtering patterns from a file (use - to read from stdin)
      --metadata-include stringArray        Include metadatas matching pattern
      --metadata-include-from stringArray   Read metadata include patterns from file (use - to read from stdin)
      --min-age Duration                    Only transfer files older than this in s or suffix ms|s|m|h|d|w|M|y (default off)
      --min-size SizeSuffix                 Only transfer files bigger than this in KiB or suffix B|K|M|G|T|P (default off)</code></pre>
<h3 id="listing-options-5">Listing Options</h3>
<p>Flags for listing directories</p>
<pre><code>      --default-time Time   Time to show if modtime is unknown for files and directories (default 2000-01-01T00:00:00Z)
      --fast-list           Use recursive list if available; uses more memory but fewer transactions</code></pre>
<h2 id="see-also-9">See Also</h2>
<ul>
<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
</ul>
<h1 id="rclone-lsd">rclone lsd</h1>
<p>List all directories/containers/buckets in the path.</p>
<h2 id="synopsis-9">Synopsis</h2>
<p>Lists the directories in the source path to standard output. Does not recurse by default. Use the <code>-R</code> flag to recurse.</p>
<p>This command lists the total size of the directory (if known, -1 if not), the modification time (if known, the current time if not), the number of objects in the directory (if known, -1 if not) and the name of the directory, Eg</p>
<pre><code>$ rclone lsd swift:
      494000 2018-04-26 08:43:20     10000 10000files
          65 2018-04-26 08:43:20         1 1File</code></pre>
<p>Or</p>
<pre><code>$ rclone lsd drive:test
          -1 2016-10-17 17:41:53        -1 1000files
          -1 2017-01-03 14:40:54        -1 2500files
          -1 2017-07-08 14:39:28        -1 4000files</code></pre>
<p>If you just want the directory names use <code>rclone lsf --dirs-only</code>.</p>
<p>Any of the filtering options can be applied to this command.</p>
<p>There are several related list commands</p>
<ul>
<li><code>ls</code> to list size and path of objects only</li>
<li><code>lsl</code> to list modification time, size and path of objects only</li>
<li><code>lsd</code> to list directories only</li>
<li><code>lsf</code> to list objects and directories in easy to parse format</li>
<li><code>lsjson</code> to list objects and directories in JSON format</li>
</ul>
<p><code>ls</code>,<code>lsl</code>,<code>lsd</code> are designed to be human-readable. <code>lsf</code> is designed to be human and machine-readable. <code>lsjson</code> is designed to be machine-readable.</p>
<p>Note that <code>ls</code> and <code>lsl</code> recurse by default - use <code>--max-depth 1</code> to stop the recursion.</p>
<p>The other list commands <code>lsd</code>,<code>lsf</code>,<code>lsjson</code> do not recurse by default - use <code>-R</code> to make them recurse.</p>
<p>Listing a nonexistent directory will produce an error except for remotes which can't have empty directories (e.g. s3, swift, or gcs - the bucket-based remotes).</p>
<pre><code>rclone lsd remote:path [flags]</code></pre>
<h2 id="options-10">Options</h2>
<pre><code>  -h, --help        help for lsd
  -R, --recursive   Recurse into the listing</code></pre>
<p>Options shared with other commands are described next. See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
<h3 id="filter-options-6">Filter Options</h3>
<p>Flags for filtering directory listings</p>
<pre><code>      --delete-excluded                     Delete files on dest excluded from sync
      --exclude stringArray                 Exclude files matching pattern
      --exclude-from stringArray            Read file exclude patterns from file (use - to read from stdin)
      --exclude-if-present stringArray      Exclude directories if filename is present
      --files-from stringArray              Read list of source-file names from file (use - to read from stdin)
      --files-from-raw stringArray          Read list of source-file names from file without any processing of lines (use - to read from stdin)
  -f, --filter stringArray                  Add a file filtering rule
      --filter-from stringArray             Read file filtering patterns from a file (use - to read from stdin)
      --ignore-case                         Ignore case in filters (case insensitive)
      --include stringArray                 Include files matching pattern
      --include-from stringArray            Read file include patterns from file (use - to read from stdin)
      --max-age Duration                    Only transfer files younger than this in s or suffix ms|s|m|h|d|w|M|y (default off)
      --max-depth int                       If set limits the recursion depth to this (default -1)
      --max-size SizeSuffix                 Only transfer files smaller than this in KiB or suffix B|K|M|G|T|P (default off)
      --metadata-exclude stringArray        Exclude metadatas matching pattern
      --metadata-exclude-from stringArray   Read metadata exclude patterns from file (use - to read from stdin)
      --metadata-filter stringArray         Add a metadata filtering rule
      --metadata-filter-from stringArray    Read metadata filtering patterns from a file (use - to read from stdin)
      --metadata-include stringArray        Include metadatas matching pattern
      --metadata-include-from stringArray   Read metadata include patterns from file (use - to read from stdin)
      --min-age Duration                    Only transfer files older than this in s or suffix ms|s|m|h|d|w|M|y (default off)
      --min-size SizeSuffix                 Only transfer files bigger than this in KiB or suffix B|K|M|G|T|P (default off)</code></pre>
<h3 id="listing-options-6">Listing Options</h3>
<p>Flags for listing directories</p>
<pre><code>      --default-time Time   Time to show if modtime is unknown for files and directories (default 2000-01-01T00:00:00Z)
      --fast-list           Use recursive list if available; uses more memory but fewer transactions</code></pre>
<h2 id="see-also-10">See Also</h2>
<ul>
<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
</ul>
<h1 id="rclone-lsl">rclone lsl</h1>
<p>List the objects in path with modification time, size and path.</p>
<h2 id="synopsis-10">Synopsis</h2>
<p>Lists the objects in the source path to standard output in a human readable format with modification time, size and path. Recurses by default.</p>
<p>Eg</p>
<pre><code>$ rclone lsl swift:bucket
    60295 2016-06-25 18:55:41.062626927 bevajer5jef
    90613 2016-06-25 18:55:43.302607074 canole
    94467 2016-06-25 18:55:43.046609333 diwogej7
    37600 2016-06-25 18:55:40.814629136 fubuwic</code></pre>
<p>Any of the filtering options can be applied to this command.</p>
<p>There are several related list commands</p>
<ul>
<li><code>ls</code> to list size and path of objects only</li>
<li><code>lsl</code> to list modification time, size and path of objects only</li>
<li><code>lsd</code> to list directories only</li>
<li><code>lsf</code> to list objects and directories in easy to parse format</li>
<li><code>lsjson</code> to list objects and directories in JSON format</li>
</ul>
<p><code>ls</code>,<code>lsl</code>,<code>lsd</code> are designed to be human-readable. <code>lsf</code> is designed to be human and machine-readable. <code>lsjson</code> is designed to be machine-readable.</p>
<p>Note that <code>ls</code> and <code>lsl</code> recurse by default - use <code>--max-depth 1</code> to stop the recursion.</p>
<p>The other list commands <code>lsd</code>,<code>lsf</code>,<code>lsjson</code> do not recurse by default - use <code>-R</code> to make them recurse.</p>
<p>Listing a nonexistent directory will produce an error except for remotes which can't have empty directories (e.g. s3, swift, or gcs - the bucket-based remotes).</p>
<pre><code>rclone lsl remote:path [flags]</code></pre>
<h2 id="options-11">Options</h2>
<pre><code>  -h, --help   help for lsl</code></pre>
<p>Options shared with other commands are described next. See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
<h3 id="filter-options-7">Filter Options</h3>
<p>Flags for filtering directory listings</p>
<pre><code>      --delete-excluded                     Delete files on dest excluded from sync
      --exclude stringArray                 Exclude files matching pattern
      --exclude-from stringArray            Read file exclude patterns from file (use - to read from stdin)
      --exclude-if-present stringArray      Exclude directories if filename is present
      --files-from stringArray              Read list of source-file names from file (use - to read from stdin)
      --files-from-raw stringArray          Read list of source-file names from file without any processing of lines (use - to read from stdin)
  -f, --filter stringArray                  Add a file filtering rule
      --filter-from stringArray             Read file filtering patterns from a file (use - to read from stdin)
      --ignore-case                         Ignore case in filters (case insensitive)
      --include stringArray                 Include files matching pattern
      --include-from stringArray            Read file include patterns from file (use - to read from stdin)
      --max-age Duration                    Only transfer files younger than this in s or suffix ms|s|m|h|d|w|M|y (default off)
      --max-depth int                       If set limits the recursion depth to this (default -1)
      --max-size SizeSuffix                 Only transfer files smaller than this in KiB or suffix B|K|M|G|T|P (default off)
      --metadata-exclude stringArray        Exclude metadatas matching pattern
      --metadata-exclude-from stringArray   Read metadata exclude patterns from file (use - to read from stdin)
      --metadata-filter stringArray         Add a metadata filtering rule
      --metadata-filter-from stringArray    Read metadata filtering patterns from a file (use - to read from stdin)
      --metadata-include stringArray        Include metadatas matching pattern
      --metadata-include-from stringArray   Read metadata include patterns from file (use - to read from stdin)
      --min-age Duration                    Only transfer files older than this in s or suffix ms|s|m|h|d|w|M|y (default off)
      --min-size SizeSuffix                 Only transfer files bigger than this in KiB or suffix B|K|M|G|T|P (default off)</code></pre>
<h3 id="listing-options-7">Listing Options</h3>
<p>Flags for listing directories</p>
<pre><code>      --default-time Time   Time to show if modtime is unknown for files and directories (default 2000-01-01T00:00:00Z)
      --fast-list           Use recursive list if available; uses more memory but fewer transactions</code></pre>
<h2 id="see-also-11">See Also</h2>
<ul>
<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
</ul>
<h1 id="rclone-md5sum">rclone md5sum</h1>
<p>Produces an md5sum file for all the objects in the path.</p>
<h2 id="synopsis-11">Synopsis</h2>
<p>Produces an md5sum file for all the objects in the path. This is in the same format as the standard md5sum tool produces.</p>
<p>By default, the hash is requested from the remote. If MD5 is not supported by the remote, no hash will be returned. With the download flag, the file will be downloaded from the remote and hashed locally enabling MD5 for any remote.</p>
<p>For other algorithms, see the <a href="https://rclone.org/commands/rclone_hashsum/">hashsum</a> command. Running <code>rclone md5sum remote:path</code> is equivalent to running <code>rclone hashsum MD5 remote:path</code>.</p>
<p>This command can also hash data received on standard input (stdin), by not passing a remote:path, or by passing a hyphen as remote:path when there is data to read (if not, the hyphen will be treated literally, as a relative path).</p>
<pre><code>rclone md5sum remote:path [flags]</code></pre>
<h2 id="options-12">Options</h2>
<pre><code>      --base64               Output base64 encoded hashsum
  -C, --checkfile string     Validate hashes against a given SUM file instead of printing them
      --download             Download the file and hash it locally; if this flag is not specified, the hash is requested from the remote
  -h, --help                 help for md5sum
      --output-file string   Output hashsums to a file rather than the terminal</code></pre>
<p>Options shared with other commands are described next. See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
<h3 id="filter-options-8">Filter Options</h3>
<p>Flags for filtering directory listings</p>
<pre><code>      --delete-excluded                     Delete files on dest excluded from sync
      --exclude stringArray                 Exclude files matching pattern
      --exclude-from stringArray            Read file exclude patterns from file (use - to read from stdin)
      --exclude-if-present stringArray      Exclude directories if filename is present
      --files-from stringArray              Read list of source-file names from file (use - to read from stdin)
      --files-from-raw stringArray          Read list of source-file names from file without any processing of lines (use - to read from stdin)
  -f, --filter stringArray                  Add a file filtering rule
      --filter-from stringArray             Read file filtering patterns from a file (use - to read from stdin)
      --ignore-case                         Ignore case in filters (case insensitive)
      --include stringArray                 Include files matching pattern
      --include-from stringArray            Read file include patterns from file (use - to read from stdin)
      --max-age Duration                    Only transfer files younger than this in s or suffix ms|s|m|h|d|w|M|y (default off)
      --max-depth int                       If set limits the recursion depth to this (default -1)
      --max-size SizeSuffix                 Only transfer files smaller than this in KiB or suffix B|K|M|G|T|P (default off)
      --metadata-exclude stringArray        Exclude metadatas matching pattern
      --metadata-exclude-from stringArray   Read metadata exclude patterns from file (use - to read from stdin)
      --metadata-filter stringArray         Add a metadata filtering rule
      --metadata-filter-from stringArray    Read metadata filtering patterns from a file (use - to read from stdin)
      --metadata-include stringArray        Include metadatas matching pattern
      --metadata-include-from stringArray   Read metadata include patterns from file (use - to read from stdin)
      --min-age Duration                    Only transfer files older than this in s or suffix ms|s|m|h|d|w|M|y (default off)
      --min-size SizeSuffix                 Only transfer files bigger than this in KiB or suffix B|K|M|G|T|P (default off)</code></pre>
<h3 id="listing-options-8">Listing Options</h3>
<p>Flags for listing directories</p>
<pre><code>      --default-time Time   Time to show if modtime is unknown for files and directories (default 2000-01-01T00:00:00Z)
      --fast-list           Use recursive list if available; uses more memory but fewer transactions</code></pre>
<h2 id="see-also-12">See Also</h2>
<ul>
<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
</ul>
<h1 id="rclone-sha1sum">rclone sha1sum</h1>
<p>Produces an sha1sum file for all the objects in the path.</p>
<h2 id="synopsis-12">Synopsis</h2>
<p>Produces an sha1sum file for all the objects in the path. This is in the same format as the standard sha1sum tool produces.</p>
<p>By default, the hash is requested from the remote. If SHA-1 is not supported by the remote, no hash will be returned. With the download flag, the file will be downloaded from the remote and hashed locally enabling SHA-1 for any remote.</p>
<p>For other algorithms, see the <a href="https://rclone.org/commands/rclone_hashsum/">hashsum</a> command. Running <code>rclone sha1sum remote:path</code> is equivalent to running <code>rclone hashsum SHA1 remote:path</code>.</p>
<p>This command can also hash data received on standard input (stdin), by not passing a remote:path, or by passing a hyphen as remote:path when there is data to read (if not, the hyphen will be treated literally, as a relative path).</p>
<p>This command can also hash data received on STDIN, if not passing a remote:path.</p>
<pre><code>rclone sha1sum remote:path [flags]</code></pre>
<h2 id="options-13">Options</h2>
<pre><code>      --base64               Output base64 encoded hashsum
  -C, --checkfile string     Validate hashes against a given SUM file instead of printing them
      --download             Download the file and hash it locally; if this flag is not specified, the hash is requested from the remote
  -h, --help                 help for sha1sum
      --output-file string   Output hashsums to a file rather than the terminal</code></pre>
<p>Options shared with other commands are described next. See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
<h3 id="filter-options-9">Filter Options</h3>
<p>Flags for filtering directory listings</p>
<pre><code>      --delete-excluded                     Delete files on dest excluded from sync
      --exclude stringArray                 Exclude files matching pattern
      --exclude-from stringArray            Read file exclude patterns from file (use - to read from stdin)
      --exclude-if-present stringArray      Exclude directories if filename is present
      --files-from stringArray              Read list of source-file names from file (use - to read from stdin)
      --files-from-raw stringArray          Read list of source-file names from file without any processing of lines (use - to read from stdin)
  -f, --filter stringArray                  Add a file filtering rule
      --filter-from stringArray             Read file filtering patterns from a file (use - to read from stdin)
      --ignore-case                         Ignore case in filters (case insensitive)
      --include stringArray                 Include files matching pattern
      --include-from stringArray            Read file include patterns from file (use - to read from stdin)
      --max-age Duration                    Only transfer files younger than this in s or suffix ms|s|m|h|d|w|M|y (default off)
      --max-depth int                       If set limits the recursion depth to this (default -1)
      --max-size SizeSuffix                 Only transfer files smaller than this in KiB or suffix B|K|M|G|T|P (default off)
      --metadata-exclude stringArray        Exclude metadatas matching pattern
      --metadata-exclude-from stringArray   Read metadata exclude patterns from file (use - to read from stdin)
      --metadata-filter stringArray         Add a metadata filtering rule
      --metadata-filter-from stringArray    Read metadata filtering patterns from a file (use - to read from stdin)
      --metadata-include stringArray        Include metadatas matching pattern
      --metadata-include-from stringArray   Read metadata include patterns from file (use - to read from stdin)
      --min-age Duration                    Only transfer files older than this in s or suffix ms|s|m|h|d|w|M|y (default off)
      --min-size SizeSuffix                 Only transfer files bigger than this in KiB or suffix B|K|M|G|T|P (default off)</code></pre>
<h3 id="listing-options-9">Listing Options</h3>
<p>Flags for listing directories</p>
<pre><code>      --default-time Time   Time to show if modtime is unknown for files and directories (default 2000-01-01T00:00:00Z)
      --fast-list           Use recursive list if available; uses more memory but fewer transactions</code></pre>
<h2 id="see-also-13">See Also</h2>
<ul>
<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
</ul>
<h1 id="rclone-size">rclone size</h1>
<p>Prints the total size and number of objects in remote:path.</p>
<h2 id="synopsis-13">Synopsis</h2>
<p>Counts objects in the path and calculates the total size. Prints the result to standard output.</p>
<p>By default the output is in human-readable format, but shows values in both human-readable format as well as the raw numbers (global option <code>--human-readable</code> is not considered). Use option <code>--json</code> to format output as JSON instead.</p>
<p>Recurses by default, use <code>--max-depth 1</code> to stop the recursion.</p>
<p>Some backends do not always provide file sizes, see for example <a href="https://rclone.org/googlephotos/#size">Google Photos</a> and <a href="https://rclone.org/drive/#limitations-of-google-docs">Google Docs</a>. Rclone will then show a notice in the log indicating how many such files were encountered, and count them in as empty files in the output of the size command.</p>
<pre><code>rclone size remote:path [flags]</code></pre>
<h2 id="options-14">Options</h2>
<pre><code>  -h, --help   help for size
      --json   Format output as JSON</code></pre>
<p>Options shared with other commands are described next. See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
<h3 id="filter-options-10">Filter Options</h3>
<p>Flags for filtering directory listings</p>
<pre><code>      --delete-excluded                     Delete files on dest excluded from sync
      --exclude stringArray                 Exclude files matching pattern
      --exclude-from stringArray            Read file exclude patterns from file (use - to read from stdin)
      --exclude-if-present stringArray      Exclude directories if filename is present
      --files-from stringArray              Read list of source-file names from file (use - to read from stdin)
      --files-from-raw stringArray          Read list of source-file names from file without any processing of lines (use - to read from stdin)
  -f, --filter stringArray                  Add a file filtering rule
      --filter-from stringArray             Read file filtering patterns from a file (use - to read from stdin)
      --ignore-case                         Ignore case in filters (case insensitive)
      --include stringArray                 Include files matching pattern
      --include-from stringArray            Read file include patterns from file (use - to read from stdin)
      --max-age Duration                    Only transfer files younger than this in s or suffix ms|s|m|h|d|w|M|y (default off)
      --max-depth int                       If set limits the recursion depth to this (default -1)
      --max-size SizeSuffix                 Only transfer files smaller than this in KiB or suffix B|K|M|G|T|P (default off)
      --metadata-exclude stringArray        Exclude metadatas matching pattern
      --metadata-exclude-from stringArray   Read metadata exclude patterns from file (use - to read from stdin)
      --metadata-filter stringArray         Add a metadata filtering rule
      --metadata-filter-from stringArray    Read metadata filtering patterns from a file (use - to read from stdin)
      --metadata-include stringArray        Include metadatas matching pattern
      --metadata-include-from stringArray   Read metadata include patterns from file (use - to read from stdin)
      --min-age Duration                    Only transfer files older than this in s or suffix ms|s|m|h|d|w|M|y (default off)
      --min-size SizeSuffix                 Only transfer files bigger than this in KiB or suffix B|K|M|G|T|P (default off)</code></pre>
<h3 id="listing-options-10">Listing Options</h3>
<p>Flags for listing directories</p>
<pre><code>      --default-time Time   Time to show if modtime is unknown for files and directories (default 2000-01-01T00:00:00Z)
      --fast-list           Use recursive list if available; uses more memory but fewer transactions</code></pre>
<h2 id="see-also-14">See Also</h2>
<ul>
<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
</ul>
<h1 id="rclone-version">rclone version</h1>
<p>Show the version number.</p>
<h2 id="synopsis-14">Synopsis</h2>
<p>Show the rclone version number, the go version, the build target OS and architecture, the runtime OS and kernel version and bitness, build tags and the type of executable (static or dynamic).</p>
<p>For example:</p>
<pre><code>$ rclone version
rclone v1.55.0
- os/version: ubuntu 18.04 (64 bit)
- os/kernel: 4.15.0-136-generic (x86_64)
- os/type: linux
- os/arch: amd64
- go/version: go1.16
- go/linking: static
- go/tags: none</code></pre>
<p>Note: before rclone version 1.55 the os/type and os/arch lines were merged, and the "go/version" line was tagged as "go version".</p>
<p>If you supply the --check flag, then it will do an online check to compare your version with the latest release and the latest beta.</p>
<pre><code>$ rclone version --check
yours:  1.42.0.6
latest: 1.42          (released 2018-06-16)
beta:   1.42.0.5      (released 2018-06-17)</code></pre>
<p>Or</p>
<pre><code>$ rclone version --check
yours:  1.41
latest: 1.42          (released 2018-06-16)
  upgrade: https://downloads.rclone.org/v1.42
beta:   1.42.0.5      (released 2018-06-17)
  upgrade: https://beta.rclone.org/v1.42-005-g56e1e820</code></pre>
<pre><code>rclone version [flags]</code></pre>
<h2 id="options-15">Options</h2>
<pre><code>      --check   Check for new version
  -h, --help    help for version</code></pre>
<p>See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
<h2 id="see-also-15">See Also</h2>
<ul>
<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
</ul>
<h1 id="rclone-cleanup">rclone cleanup</h1>
<p>Clean up the remote if possible.</p>
<h2 id="synopsis-15">Synopsis</h2>
<p>Clean up the remote if possible. Empty the trash or delete old file versions. Not supported by all remotes.</p>
<pre><code>rclone cleanup remote:path [flags]</code></pre>
<h2 id="options-16">Options</h2>
<pre><code>  -h, --help   help for cleanup</code></pre>
<p>Options shared with other commands are described next. See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
<h3 id="important-options-7">Important Options</h3>
<p>Important flags useful for most commands</p>
<pre><code>  -n, --dry-run         Do a trial run with no permanent changes
  -i, --interactive     Enable interactive mode
  -v, --verbose count   Print lots more stuff (repeat for more)</code></pre>
<h2 id="see-also-16">See Also</h2>
<ul>
<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
</ul>
<h1 id="rclone-dedupe">rclone dedupe</h1>
<p>Interactively find duplicate filenames and delete/rename them.</p>
<h2 id="synopsis-16">Synopsis</h2>
<p>By default <code>dedupe</code> interactively finds files with duplicate names and offers to delete all but one or rename them to be different. This is known as deduping by name.</p>
<p>Deduping by name is only useful with a small group of backends (e.g. Google Drive, Opendrive) that can have duplicate file names. It can be run on wrapping backends (e.g. crypt) if they wrap a backend which supports duplicate file names.</p>
<p>However if <code>--by-hash</code> is passed in then dedupe will find files with duplicate hashes instead which will work on any backend which supports at least one hash. This can be used to find files with duplicate content. This is known as deduping by hash.</p>
<p>If deduping by name, first rclone will merge directories with the same name. It will do this iteratively until all the identically named directories have been merged.</p>
<p>Next, if deduping by name, for every group of duplicate file names / hashes, it will delete all but one identical file it finds without confirmation. This means that for most duplicated files the <code>dedupe</code> command will not be interactive.</p>
<p><code>dedupe</code> considers files to be identical if they have the same file path and the same hash. If the backend does not support hashes (e.g. crypt wrapping Google Drive) then they will never be found to be identical. If you use the <code>--size-only</code> flag then files will be considered identical if they have the same size (any hash will be ignored). This can be useful on crypt backends which do not support hashes.</p>
<p>Next rclone will resolve the remaining duplicates. Exactly which action is taken depends on the dedupe mode. By default, rclone will interactively query the user for each one.</p>
<p><strong>Important</strong>: Since this can cause data loss, test first with the <code>--dry-run</code> or the <code>--interactive</code>/<code>-i</code> flag.</p>
<p>Here is an example run.</p>
<p>Before - with duplicates</p>
<pre><code>$ rclone lsl drive:dupes
  6048320 2016-03-05 16:23:16.798000000 one.txt
  6048320 2016-03-05 16:23:11.775000000 one.txt
   564374 2016-03-05 16:23:06.731000000 one.txt
  6048320 2016-03-05 16:18:26.092000000 one.txt
  6048320 2016-03-05 16:22:46.185000000 two.txt
  1744073 2016-03-05 16:22:38.104000000 two.txt
   564374 2016-03-05 16:22:52.118000000 two.txt</code></pre>
<p>Now the <code>dedupe</code> session</p>
<pre><code>$ rclone dedupe drive:dupes
2016/03/05 16:24:37 Google drive root &#39;dupes&#39;: Looking for duplicates using interactive mode.
one.txt: Found 4 files with duplicate names
one.txt: Deleting 2/3 identical duplicates (MD5 &quot;1eedaa9fe86fd4b8632e2ac549403b36&quot;)
one.txt: 2 duplicates remain
  1:      6048320 bytes, 2016-03-05 16:23:16.798000000, MD5 1eedaa9fe86fd4b8632e2ac549403b36
  2:       564374 bytes, 2016-03-05 16:23:06.731000000, MD5 7594e7dc9fc28f727c42ee3e0749de81
s) Skip and do nothing
k) Keep just one (choose which in next step)
r) Rename all to be different (by changing file.jpg to file-1.jpg)
s/k/r&gt; k
Enter the number of the file to keep&gt; 1
one.txt: Deleted 1 extra copies
two.txt: Found 3 files with duplicate names
two.txt: 3 duplicates remain
  1:       564374 bytes, 2016-03-05 16:22:52.118000000, MD5 7594e7dc9fc28f727c42ee3e0749de81
  2:      6048320 bytes, 2016-03-05 16:22:46.185000000, MD5 1eedaa9fe86fd4b8632e2ac549403b36
  3:      1744073 bytes, 2016-03-05 16:22:38.104000000, MD5 851957f7fb6f0bc4ce76be966d336802
s) Skip and do nothing
k) Keep just one (choose which in next step)
r) Rename all to be different (by changing file.jpg to file-1.jpg)
s/k/r&gt; r
two-1.txt: renamed from: two.txt
two-2.txt: renamed from: two.txt
two-3.txt: renamed from: two.txt</code></pre>
<p>The result being</p>
<pre><code>$ rclone lsl drive:dupes
  6048320 2016-03-05 16:23:16.798000000 one.txt
   564374 2016-03-05 16:22:52.118000000 two-1.txt
  6048320 2016-03-05 16:22:46.185000000 two-2.txt
  1744073 2016-03-05 16:22:38.104000000 two-3.txt</code></pre>
<p>Dedupe can be run non interactively using the <code>--dedupe-mode</code> flag or by using an extra parameter with the same value</p>
<ul>
<li><code>--dedupe-mode interactive</code> - interactive as above.</li>
<li><code>--dedupe-mode skip</code> - removes identical files then skips anything left.</li>
<li><code>--dedupe-mode first</code> - removes identical files then keeps the first one.</li>
<li><code>--dedupe-mode newest</code> - removes identical files then keeps the newest one.</li>
<li><code>--dedupe-mode oldest</code> - removes identical files then keeps the oldest one.</li>
<li><code>--dedupe-mode largest</code> - removes identical files then keeps the largest one.</li>
<li><code>--dedupe-mode smallest</code> - removes identical files then keeps the smallest one.</li>
<li><code>--dedupe-mode rename</code> - removes identical files then renames the rest to be different.</li>
<li><code>--dedupe-mode list</code> - lists duplicate dirs and files only and changes nothing.</li>
</ul>
<p>For example, to rename all the identically named photos in your Google Photos directory, do</p>
<pre><code>rclone dedupe --dedupe-mode rename &quot;drive:Google Photos&quot;</code></pre>
<p>Or</p>
<pre><code>rclone dedupe rename &quot;drive:Google Photos&quot;</code></pre>
<pre><code>rclone dedupe [mode] remote:path [flags]</code></pre>
<h2 id="options-17">Options</h2>
<pre><code>      --by-hash              Find identical hashes rather than names
      --dedupe-mode string   Dedupe mode interactive|skip|first|newest|oldest|largest|smallest|rename (default &quot;interactive&quot;)
  -h, --help                 help for dedupe</code></pre>
<p>Options shared with other commands are described next. See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
<h3 id="important-options-8">Important Options</h3>
<p>Important flags useful for most commands</p>
<pre><code>  -n, --dry-run         Do a trial run with no permanent changes
  -i, --interactive     Enable interactive mode
  -v, --verbose count   Print lots more stuff (repeat for more)</code></pre>
<h2 id="see-also-17">See Also</h2>
<ul>
<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
</ul>
<h1 id="rclone-about">rclone about</h1>
<p>Get quota information from the remote.</p>
<h2 id="synopsis-17">Synopsis</h2>
<p>Prints quota information about a remote to standard output. The output is typically used, free, quota and trash contents.</p>
<p>E.g. Typical output from <code>rclone about remote:</code> is:</p>
<pre><code>Total:   17 GiB
Used:    7.444 GiB
Free:    1.315 GiB
Trashed: 100.000 MiB
Other:   8.241 GiB</code></pre>
<p>Where the fields are:</p>
<ul>
<li>Total: Total size available.</li>
<li>Used: Total size used.</li>
<li>Free: Total space available to this user.</li>
<li>Trashed: Total space used by trash.</li>
<li>Other: Total amount in other storage (e.g. Gmail, Google Photos).</li>
<li>Objects: Total number of objects in the storage.</li>
</ul>
<p>All sizes are in number of bytes.</p>
<p>Applying a <code>--full</code> flag to the command prints the bytes in full, e.g.</p>
<pre><code>Total:   18253611008
Used:    7993453766
Free:    1411001220
Trashed: 104857602
Other:   8849156022</code></pre>
<p>A <code>--json</code> flag generates conveniently machine-readable output, e.g.</p>
<pre><code>{
    &quot;total&quot;: 18253611008,
    &quot;used&quot;: 7993453766,
    &quot;trashed&quot;: 104857602,
    &quot;other&quot;: 8849156022,
    &quot;free&quot;: 1411001220
}</code></pre>
<p>Not all backends print all fields. Information is not included if it is not provided by a backend. Where the value is unlimited it is omitted.</p>
<p>Some backends does not support the <code>rclone about</code> command at all, see complete list in <a href="https://rclone.org/overview/#optional-features">documentation</a>.</p>
<pre><code>rclone about remote: [flags]</code></pre>
<h2 id="options-18">Options</h2>
<pre><code>      --full   Full numbers instead of human-readable
  -h, --help   help for about
      --json   Format output as JSON</code></pre>
<p>See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
<h2 id="see-also-18">See Also</h2>
<ul>
<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
</ul>
<h1 id="rclone-authorize">rclone authorize</h1>
<p>Remote authorization.</p>
<h2 id="synopsis-18">Synopsis</h2>
<p>Remote authorization. Used to authorize a remote or headless rclone from a machine with a browser - use as instructed by rclone config.</p>
<p>Use --auth-no-open-browser to prevent rclone to open auth link in default browser automatically.</p>
<p>Use --template to generate HTML output via a custom Go template. If a blank string is provided as an argument to this flag, the default template is used.</p>
<pre><code>rclone authorize [flags]</code></pre>
<h2 id="options-19">Options</h2>
<pre><code>      --auth-no-open-browser   Do not automatically open auth link in default browser
  -h, --help                   help for authorize
      --template string        The path to a custom Go template for generating HTML responses</code></pre>
<p>See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
<h2 id="see-also-19">See Also</h2>
<ul>
<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
</ul>
<h1 id="rclone-backend">rclone backend</h1>
<p>Run a backend-specific command.</p>
<h2 id="synopsis-19">Synopsis</h2>
<p>This runs a backend-specific command. The commands themselves (except for "help" and "features") are defined by the backends and you should see the backend docs for definitions.</p>
<p>You can discover what commands a backend implements by using</p>
<pre><code>rclone backend help remote:
rclone backend help &lt;backendname&gt;</code></pre>
<p>You can also discover information about the backend using (see <a href="https://rclone.org/rc/#operations-fsinfo">operations/fsinfo</a> in the remote control docs for more info).</p>
<pre><code>rclone backend features remote:</code></pre>
<p>Pass options to the backend command with -o. This should be key=value or key, e.g.:</p>
<pre><code>rclone backend stats remote:path stats -o format=json -o long</code></pre>
<p>Pass arguments to the backend by placing them on the end of the line</p>
<pre><code>rclone backend cleanup remote:path file1 file2 file3</code></pre>
<p>Note to run these commands on a running backend then see <a href="https://rclone.org/rc/#backend-command">backend/command</a> in the rc docs.</p>
<pre><code>rclone backend &lt;command&gt; remote:path [opts] &lt;args&gt; [flags]</code></pre>
<h2 id="options-20">Options</h2>
<pre><code>  -h, --help                 help for backend
      --json                 Always output in JSON format
  -o, --option stringArray   Option in the form name=value or name</code></pre>
<p>Options shared with other commands are described next. See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
<h3 id="important-options-9">Important Options</h3>
<p>Important flags useful for most commands</p>
<pre><code>  -n, --dry-run         Do a trial run with no permanent changes
  -i, --interactive     Enable interactive mode
  -v, --verbose count   Print lots more stuff (repeat for more)</code></pre>
<h2 id="see-also-20">See Also</h2>
<ul>
<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
</ul>
<h1 id="rclone-bisync">rclone bisync</h1>
<p>Perform bidirectional synchronization between two paths.</p>
<h2 id="synopsis-20">Synopsis</h2>
<p>Perform bidirectional synchronization between two paths.</p>
<p><a href="https://rclone.org/bisync/">Bisync</a> provides a bidirectional cloud sync solution in rclone. It retains the Path1 and Path2 filesystem listings from the prior run. On each successive run it will: - list files on Path1 and Path2, and check for changes on each side. Changes include <code>New</code>, <code>Newer</code>, <code>Older</code>, and <code>Deleted</code> files. - Propagate changes on Path1 to Path2, and vice-versa.</p>
<p>Bisync is <strong>in beta</strong> and is considered an <strong>advanced command</strong>, so use with care. Make sure you have read and understood the entire <a href="https://rclone.org/bisync">manual</a> (especially the <a href="https://rclone.org/bisync/#limitations">Limitations</a> section) before using, or data loss can result. Questions can be asked in the <a href="https://forum.rclone.org/">Rclone Forum</a>.</p>
<p>See <a href="https://rclone.org/bisync/">full bisync description</a> for details.</p>
<pre><code>rclone bisync remote1:path1 remote2:path2 [flags]</code></pre>
<h2 id="options-21">Options</h2>
<pre><code>      --backup-dir1 string                   --backup-dir for Path1. Must be a non-overlapping path on the same remote.
      --backup-dir2 string                   --backup-dir for Path2. Must be a non-overlapping path on the same remote.
      --check-access                         Ensure expected RCLONE_TEST files are found on both Path1 and Path2 filesystems, else abort.
      --check-filename string                Filename for --check-access (default: RCLONE_TEST)
      --check-sync string                    Controls comparison of final listings: true|false|only (default: true) (default &quot;true&quot;)
      --compare string                       Comma-separated list of bisync-specific compare options ex. &#39;size,modtime,checksum&#39; (default: &#39;size,modtime&#39;)
      --conflict-loser ConflictLoserAction   Action to take on the loser of a sync conflict (when there is a winner) or on both files (when there is no winner): , num, pathname, delete (default: num)
      --conflict-resolve string              Automatically resolve conflicts by preferring the version that is: none, path1, path2, newer, older, larger, smaller (default: none) (default &quot;none&quot;)
      --conflict-suffix string               Suffix to use when renaming a --conflict-loser. Can be either one string or two comma-separated strings to assign different suffixes to Path1/Path2. (default: &#39;conflict&#39;)
      --create-empty-src-dirs                Sync creation and deletion of empty directories. (Not compatible with --remove-empty-dirs)
      --download-hash                        Compute hash by downloading when otherwise unavailable. (warning: may be slow and use lots of data!)
      --filters-file string                  Read filtering patterns from a file
      --force                                Bypass --max-delete safety check and run the sync. Consider using with --verbose
  -h, --help                                 help for bisync
      --ignore-listing-checksum              Do not use checksums for listings (add --ignore-checksum to additionally skip post-copy checksum checks)
      --max-lock Duration                    Consider lock files older than this to be expired (default: 0 (never expire)) (minimum: 2m) (default 0s)
      --no-cleanup                           Retain working files (useful for troubleshooting and testing).
      --no-slow-hash                         Ignore listing checksums only on backends where they are slow
      --recover                              Automatically recover from interruptions without requiring --resync.
      --remove-empty-dirs                    Remove ALL empty directories at the final cleanup step.
      --resilient                            Allow future runs to retry after certain less-serious errors, instead of requiring --resync. Use at your own risk!
  -1, --resync                               Performs the resync run. Equivalent to --resync-mode path1. Consider using --verbose or --dry-run first.
      --resync-mode string                   During resync, prefer the version that is: path1, path2, newer, older, larger, smaller (default: path1 if --resync, otherwise none for no resync.) (default &quot;none&quot;)
      --slow-hash-sync-only                  Ignore slow checksums for listings and deltas, but still consider them during sync calls.
      --workdir string                       Use custom working dir - useful for testing. (default: {WORKDIR})</code></pre>
<p>Options shared with other commands are described next. See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
<h3 id="copy-options-3">Copy Options</h3>
<p>Flags for anything which can copy a file</p>
<pre><code>      --check-first                                 Do all the checks before starting transfers
  -c, --checksum                                    Check for changes with size &amp; checksum (if available, or fallback to size only)
      --compare-dest stringArray                    Include additional server-side paths during comparison
      --copy-dest stringArray                       Implies --compare-dest but also copies files from paths into destination
      --cutoff-mode HARD|SOFT|CAUTIOUS              Mode to stop transfers when reaching the max transfer limit HARD|SOFT|CAUTIOUS (default HARD)
      --ignore-case-sync                            Ignore case when synchronizing
      --ignore-checksum                             Skip post copy check of checksums
      --ignore-existing                             Skip all files that exist on destination
      --ignore-size                                 Ignore size when skipping use modtime or checksum
  -I, --ignore-times                                Don&#39;t skip items that match size and time - transfer all unconditionally
      --immutable                                   Do not modify files, fail if existing files have been modified
      --inplace                                     Download directly to destination file instead of atomic download to temp/rename
      --max-backlog int                             Maximum number of objects in sync or check backlog (default 10000)
      --max-duration Duration                       Maximum duration rclone will transfer data for (default 0s)
      --max-transfer SizeSuffix                     Maximum size of data to transfer (default off)
  -M, --metadata                                    If set, preserve metadata when copying objects
      --modify-window Duration                      Max time diff to be considered the same (default 1ns)
      --multi-thread-chunk-size SizeSuffix          Chunk size for multi-thread downloads / uploads, if not set by filesystem (default 64Mi)
      --multi-thread-cutoff SizeSuffix              Use multi-thread downloads for files above this size (default 256Mi)
      --multi-thread-streams int                    Number of streams to use for multi-thread downloads (default 4)
      --multi-thread-write-buffer-size SizeSuffix   In memory buffer size for writing when in multi-thread mode (default 128Ki)
      --no-check-dest                               Don&#39;t check the destination, copy regardless
      --no-traverse                                 Don&#39;t traverse destination file system on copy
      --no-update-dir-modtime                       Don&#39;t update directory modification times
      --no-update-modtime                           Don&#39;t update destination modtime if files identical
      --order-by string                             Instructions on how to order the transfers, e.g. &#39;size,descending&#39;
      --partial-suffix string                       Add partial-suffix to temporary file name when --inplace is not used (default &quot;.partial&quot;)
      --refresh-times                               Refresh the modtime of remote files
      --server-side-across-configs                  Allow server-side operations (e.g. copy) to work across different configs
      --size-only                                   Skip based on size only, not modtime or checksum
      --streaming-upload-cutoff SizeSuffix          Cutoff for switching to chunked upload if file size is unknown, upload starts after reaching cutoff or when file ends (default 100Ki)
  -u, --update                                      Skip files that are newer on the destination</code></pre>
<h3 id="important-options-10">Important Options</h3>
<p>Important flags useful for most commands</p>
<pre><code>  -n, --dry-run         Do a trial run with no permanent changes
  -i, --interactive     Enable interactive mode
  -v, --verbose count   Print lots more stuff (repeat for more)</code></pre>
<h3 id="filter-options-11">Filter Options</h3>
<p>Flags for filtering directory listings</p>
<pre><code>      --delete-excluded                     Delete files on dest excluded from sync
      --exclude stringArray                 Exclude files matching pattern
      --exclude-from stringArray            Read file exclude patterns from file (use - to read from stdin)
      --exclude-if-present stringArray      Exclude directories if filename is present
      --files-from stringArray              Read list of source-file names from file (use - to read from stdin)
      --files-from-raw stringArray          Read list of source-file names from file without any processing of lines (use - to read from stdin)
  -f, --filter stringArray                  Add a file filtering rule
      --filter-from stringArray             Read file filtering patterns from a file (use - to read from stdin)
      --ignore-case                         Ignore case in filters (case insensitive)
      --include stringArray                 Include files matching pattern
      --include-from stringArray            Read file include patterns from file (use - to read from stdin)
      --max-age Duration                    Only transfer files younger than this in s or suffix ms|s|m|h|d|w|M|y (default off)
      --max-depth int                       If set limits the recursion depth to this (default -1)
      --max-size SizeSuffix                 Only transfer files smaller than this in KiB or suffix B|K|M|G|T|P (default off)
      --metadata-exclude stringArray        Exclude metadatas matching pattern
      --metadata-exclude-from stringArray   Read metadata exclude patterns from file (use - to read from stdin)
      --metadata-filter stringArray         Add a metadata filtering rule
      --metadata-filter-from stringArray    Read metadata filtering patterns from a file (use - to read from stdin)
      --metadata-include stringArray        Include metadatas matching pattern
      --metadata-include-from stringArray   Read metadata include patterns from file (use - to read from stdin)
      --min-age Duration                    Only transfer files older than this in s or suffix ms|s|m|h|d|w|M|y (default off)
      --min-size SizeSuffix                 Only transfer files bigger than this in KiB or suffix B|K|M|G|T|P (default off)</code></pre>
<h2 id="see-also-21">See Also</h2>
<ul>
<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
</ul>
<h1 id="rclone-cat">rclone cat</h1>
<p>Concatenates any files and sends them to stdout.</p>
<h2 id="synopsis-21">Synopsis</h2>
<p>Sends any files to standard output.</p>
<p>You can use it like this to output a single file</p>
<pre><code>rclone cat remote:path/to/file</code></pre>
<p>Or like this to output any file in dir or its subdirectories.</p>
<pre><code>rclone cat remote:path/to/dir</code></pre>
<p>Or like this to output any .txt files in dir or its subdirectories.</p>
<pre><code>rclone --include &quot;*.txt&quot; cat remote:path/to/dir</code></pre>
<p>Use the <code>--head</code> flag to print characters only at the start, <code>--tail</code> for the end and <code>--offset</code> and <code>--count</code> to print a section in the middle. Note that if offset is negative it will count from the end, so <code>--offset -1 --count 1</code> is equivalent to <code>--tail 1</code>.</p>
<p>Use the <code>--separator</code> flag to print a separator value between files. Be sure to shell-escape special characters. For example, to print a newline between files, use:</p>
<ul>
<li><p>bash:</p>
<pre><code>rclone --include &quot;*.txt&quot; --separator $&#39;\n&#39; cat remote:path/to/dir</code></pre></li>
<li><p>powershell:</p>
<pre><code>rclone --include &quot;*.txt&quot; --separator &quot;`n&quot; cat remote:path/to/dir</code></pre></li>
</ul>
<pre><code>rclone cat remote:path [flags]</code></pre>
<h2 id="options-22">Options</h2>
<pre><code>      --count int          Only print N characters (default -1)
      --discard            Discard the output instead of printing
      --head int           Only print the first N characters
  -h, --help               help for cat
      --offset int         Start printing at offset N (or from end if -ve)
      --separator string   Separator to use between objects when printing multiple files
      --tail int           Only print the last N characters</code></pre>
<p>Options shared with other commands are described next. See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
<h3 id="filter-options-12">Filter Options</h3>
<p>Flags for filtering directory listings</p>
<pre><code>      --delete-excluded                     Delete files on dest excluded from sync
      --exclude stringArray                 Exclude files matching pattern
      --exclude-from stringArray            Read file exclude patterns from file (use - to read from stdin)
      --exclude-if-present stringArray      Exclude directories if filename is present
      --files-from stringArray              Read list of source-file names from file (use - to read from stdin)
      --files-from-raw stringArray          Read list of source-file names from file without any processing of lines (use - to read from stdin)
  -f, --filter stringArray                  Add a file filtering rule
      --filter-from stringArray             Read file filtering patterns from a file (use - to read from stdin)
      --ignore-case                         Ignore case in filters (case insensitive)
      --include stringArray                 Include files matching pattern
      --include-from stringArray            Read file include patterns from file (use - to read from stdin)
      --max-age Duration                    Only transfer files younger than this in s or suffix ms|s|m|h|d|w|M|y (default off)
      --max-depth int                       If set limits the recursion depth to this (default -1)
      --max-size SizeSuffix                 Only transfer files smaller than this in KiB or suffix B|K|M|G|T|P (default off)
      --metadata-exclude stringArray        Exclude metadatas matching pattern
      --metadata-exclude-from stringArray   Read metadata exclude patterns from file (use - to read from stdin)
      --metadata-filter stringArray         Add a metadata filtering rule
      --metadata-filter-from stringArray    Read metadata filtering patterns from a file (use - to read from stdin)
      --metadata-include stringArray        Include metadatas matching pattern
      --metadata-include-from stringArray   Read metadata include patterns from file (use - to read from stdin)
      --min-age Duration                    Only transfer files older than this in s or suffix ms|s|m|h|d|w|M|y (default off)
      --min-size SizeSuffix                 Only transfer files bigger than this in KiB or suffix B|K|M|G|T|P (default off)</code></pre>
<h3 id="listing-options-11">Listing Options</h3>
<p>Flags for listing directories</p>
<pre><code>      --default-time Time   Time to show if modtime is unknown for files and directories (default 2000-01-01T00:00:00Z)
      --fast-list           Use recursive list if available; uses more memory but fewer transactions</code></pre>
<h2 id="see-also-22">See Also</h2>
<ul>
<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
</ul>
<h1 id="rclone-checksum">rclone checksum</h1>
<p>Checks the files in the destination against a SUM file.</p>
<h2 id="synopsis-22">Synopsis</h2>
<p>Checks that hashsums of destination files match the SUM file. It compares hashes (MD5, SHA1, etc) and logs a report of files which don't match. It doesn't alter the file system.</p>
<p>The sumfile is treated as the source and the dst:path is treated as the destination for the purposes of the output.</p>
<p>If you supply the <code>--download</code> flag, it will download the data from the remote and calculate the content hash on the fly. This can be useful for remotes that don't support hashes or if you really want to check all the data.</p>
<p>Note that hash values in the SUM file are treated as case insensitive.</p>
<p>If you supply the <code>--one-way</code> flag, it will only check that files in the source match the files in the destination, not the other way around. This means that extra files in the destination that are not in the source will not be detected.</p>
<p>The <code>--differ</code>, <code>--missing-on-dst</code>, <code>--missing-on-src</code>, <code>--match</code> and <code>--error</code> flags write paths, one per line, to the file name (or stdout if it is <code>-</code>) supplied. What they write is described in the help below. For example <code>--differ</code> will write all paths which are present on both the source and destination but different.</p>
<p>The <code>--combined</code> flag will write a file (or stdout) which contains all file paths with a symbol and then a space and then the path to tell you what happened to it. These are reminiscent of diff files.</p>
<ul>
<li><code>= path</code> means path was found in source and destination and was identical</li>
<li>`- path` means path was missing on the source, so only in the destination</li>
<li>`+ path` means path was missing on the destination, so only in the source</li>
<li>`* path` means path was present in source and destination but different.</li>
<li><code>! path</code> means there was an error reading or hashing the source or dest.</li>
</ul>
<p>The default number of parallel checks is 8. See the <a href="https://rclone.org/docs/#checkers-n">--checkers=N</a> option for more information.</p>
<pre><code>rclone checksum &lt;hash&gt; sumfile dst:path [flags]</code></pre>
<h2 id="options-23">Options</h2>
<pre><code>      --combined string         Make a combined report of changes to this file
      --differ string           Report all non-matching files to this file
      --download                Check by hashing the contents
      --error string            Report all files with errors (hashing or reading) to this file
  -h, --help                    help for checksum
      --match string            Report all matching files to this file
      --missing-on-dst string   Report all files missing from the destination to this file
      --missing-on-src string   Report all files missing from the source to this file
      --one-way                 Check one way only, source files must exist on remote</code></pre>
<p>Options shared with other commands are described next. See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
<h3 id="filter-options-13">Filter Options</h3>
<p>Flags for filtering directory listings</p>
<pre><code>      --delete-excluded                     Delete files on dest excluded from sync
      --exclude stringArray                 Exclude files matching pattern
      --exclude-from stringArray            Read file exclude patterns from file (use - to read from stdin)
      --exclude-if-present stringArray      Exclude directories if filename is present
      --files-from stringArray              Read list of source-file names from file (use - to read from stdin)
      --files-from-raw stringArray          Read list of source-file names from file without any processing of lines (use - to read from stdin)
  -f, --filter stringArray                  Add a file filtering rule
      --filter-from stringArray             Read file filtering patterns from a file (use - to read from stdin)
      --ignore-case                         Ignore case in filters (case insensitive)
      --include stringArray                 Include files matching pattern
      --include-from stringArray            Read file include patterns from file (use - to read from stdin)
      --max-age Duration                    Only transfer files younger than this in s or suffix ms|s|m|h|d|w|M|y (default off)
      --max-depth int                       If set limits the recursion depth to this (default -1)
      --max-size SizeSuffix                 Only transfer files smaller than this in KiB or suffix B|K|M|G|T|P (default off)
      --metadata-exclude stringArray        Exclude metadatas matching pattern
      --metadata-exclude-from stringArray   Read metadata exclude patterns from file (use - to read from stdin)
      --metadata-filter stringArray         Add a metadata filtering rule
      --metadata-filter-from stringArray    Read metadata filtering patterns from a file (use - to read from stdin)
      --metadata-include stringArray        Include metadatas matching pattern
      --metadata-include-from stringArray   Read metadata include patterns from file (use - to read from stdin)
      --min-age Duration                    Only transfer files older than this in s or suffix ms|s|m|h|d|w|M|y (default off)
      --min-size SizeSuffix                 Only transfer files bigger than this in KiB or suffix B|K|M|G|T|P (default off)</code></pre>
<h3 id="listing-options-12">Listing Options</h3>
<p>Flags for listing directories</p>
<pre><code>      --default-time Time   Time to show if modtime is unknown for files and directories (default 2000-01-01T00:00:00Z)
      --fast-list           Use recursive list if available; uses more memory but fewer transactions</code></pre>
<h2 id="see-also-23">See Also</h2>
<ul>
<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
</ul>
<h1 id="rclone-completion">rclone completion</h1>
<p>Output completion script for a given shell.</p>
<h2 id="synopsis-23">Synopsis</h2>
<p>Generates a shell completion script for rclone. Run with <code>--help</code> to list the supported shells.</p>
<h2 id="options-24">Options</h2>
<pre><code>  -h, --help   help for completion</code></pre>
<p>See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
<h2 id="see-also-24">See Also</h2>
<ul>
<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
<li><a href="https://rclone.org/commands/rclone_completion_bash/">rclone completion bash</a> - Output bash completion script for rclone.</li>
<li><a href="https://rclone.org/commands/rclone_completion_fish/">rclone completion fish</a> - Output fish completion script for rclone.</li>
<li><a href="https://rclone.org/commands/rclone_completion_powershell/">rclone completion powershell</a> - Output powershell completion script for rclone.</li>
<li><a href="https://rclone.org/commands/rclone_completion_zsh/">rclone completion zsh</a> - Output zsh completion script for rclone.</li>
</ul>
<h1 id="rclone-completion-bash">rclone completion bash</h1>
<p>Output bash completion script for rclone.</p>
<h2 id="synopsis-24">Synopsis</h2>
<p>Generates a bash shell autocompletion script for rclone.</p>
<p>By default, when run without any arguments,</p>
<pre><code>rclone completion bash</code></pre>
<p>the generated script will be written to</p>
<pre><code>/etc/bash_completion.d/rclone</code></pre>
<p>and so rclone will probably need to be run as root, or with sudo.</p>
<p>If you supply a path to a file as the command line argument, then the generated script will be written to that file, in which case you should not need root privileges.</p>
<p>If output_file is "-", then the output will be written to stdout.</p>
<p>If you have installed the script into the default location, you can logout and login again to use the autocompletion script.</p>
<p>Alternatively, you can source the script directly</p>
<pre><code>. /path/to/my_bash_completion_scripts/rclone</code></pre>
<p>and the autocompletion functionality will be added to your current shell.</p>
<pre><code>rclone completion bash [output_file] [flags]</code></pre>
<h2 id="options-25">Options</h2>
<pre><code>  -h, --help   help for bash</code></pre>
<p>See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
<h2 id="see-also-25">See Also</h2>
<ul>
<li><a href="https://rclone.org/commands/rclone_completion/">rclone completion</a> - Output completion script for a given shell.</li>
</ul>
<h1 id="rclone-completion-fish">rclone completion fish</h1>
<p>Output fish completion script for rclone.</p>
<h2 id="synopsis-25">Synopsis</h2>
<p>Generates a fish autocompletion script for rclone.</p>
<p>This writes to /etc/fish/completions/rclone.fish by default so will probably need to be run with sudo or as root, e.g.</p>
<pre><code>sudo rclone completion fish</code></pre>
<p>Logout and login again to use the autocompletion scripts, or source them directly</p>
<pre><code>. /etc/fish/completions/rclone.fish</code></pre>
<p>If you supply a command line argument the script will be written there.</p>
<p>If output_file is "-", then the output will be written to stdout.</p>
<pre><code>rclone completion fish [output_file] [flags]</code></pre>
<h2 id="options-26">Options</h2>
<pre><code>  -h, --help   help for fish</code></pre>
<p>See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
<h2 id="see-also-26">See Also</h2>
<ul>
<li><a href="https://rclone.org/commands/rclone_completion/">rclone completion</a> - Output completion script for a given shell.</li>
</ul>
<h1 id="rclone-completion-powershell">rclone completion powershell</h1>
<p>Output powershell completion script for rclone.</p>
<h2 id="synopsis-26">Synopsis</h2>
<p>Generate the autocompletion script for powershell.</p>
<p>To load completions in your current shell session:</p>
<pre><code>rclone completion powershell | Out-String | Invoke-Expression</code></pre>
<p>To load completions for every new session, add the output of the above command to your powershell profile.</p>
<p>If output_file is "-" or missing, then the output will be written to stdout.</p>
<pre><code>rclone completion powershell [output_file] [flags]</code></pre>
<h2 id="options-27">Options</h2>
<pre><code>  -h, --help   help for powershell</code></pre>
<p>See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
<h2 id="see-also-27">See Also</h2>
<ul>
<li><a href="https://rclone.org/commands/rclone_completion/">rclone completion</a> - Output completion script for a given shell.</li>
</ul>
<h1 id="rclone-completion-zsh">rclone completion zsh</h1>
<p>Output zsh completion script for rclone.</p>
<h2 id="synopsis-27">Synopsis</h2>
<p>Generates a zsh autocompletion script for rclone.</p>
<p>This writes to /usr/share/zsh/vendor-completions/_rclone by default so will probably need to be run with sudo or as root, e.g.</p>
<pre><code>sudo rclone completion zsh</code></pre>
<p>Logout and login again to use the autocompletion scripts, or source them directly</p>
<pre><code>autoload -U compinit &amp;&amp; compinit</code></pre>
<p>If you supply a command line argument the script will be written there.</p>
<p>If output_file is "-", then the output will be written to stdout.</p>
<pre><code>rclone completion zsh [output_file] [flags]</code></pre>
<h2 id="options-28">Options</h2>
<pre><code>  -h, --help   help for zsh</code></pre>
<p>See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
<h2 id="see-also-28">See Also</h2>
<ul>
<li><a href="https://rclone.org/commands/rclone_completion/">rclone completion</a> - Output completion script for a given shell.</li>
</ul>
<h1 id="rclone-config-create">rclone config create</h1>
<p>Create a new remote with name, type and options.</p>
<h2 id="synopsis-28">Synopsis</h2>
<p>Create a new remote of <code>name</code> with <code>type</code> and options. The options should be passed in pairs of <code>key</code> <code>value</code> or as <code>key=value</code>.</p>
<p>For example, to make a swift remote of name myremote using auto config you would do:</p>
<pre><code>rclone config create myremote swift env_auth true
rclone config create myremote swift env_auth=true</code></pre>
<p>So for example if you wanted to configure a Google Drive remote but using remote authorization you would do this:</p>
<pre><code>rclone config create mydrive drive config_is_local=false</code></pre>
<p>Note that if the config process would normally ask a question the default is taken (unless <code>--non-interactive</code> is used). Each time that happens rclone will print or DEBUG a message saying how to affect the value taken.</p>
<p>If any of the parameters passed is a password field, then rclone will automatically obscure them if they aren't already obscured before putting them in the config file.</p>
<p><strong>NB</strong> If the password parameter is 22 characters or longer and consists only of base64 characters then rclone can get confused about whether the password is already obscured or not and put unobscured passwords into the config file. If you want to be 100% certain that the passwords get obscured then use the <code>--obscure</code> flag, or if you are 100% certain you are already passing obscured passwords then use <code>--no-obscure</code>. You can also set obscured passwords using the <code>rclone config password</code> command.</p>
<p>The flag <code>--non-interactive</code> is for use by applications that wish to configure rclone themselves, rather than using rclone's text based configuration questions. If this flag is set, and rclone needs to ask the user a question, a JSON blob will be returned with the question in it.</p>
<p>This will look something like (some irrelevant detail removed):</p>
<pre><code>{
    &quot;State&quot;: &quot;*oauth-islocal,teamdrive,,&quot;,
    &quot;Option&quot;: {
        &quot;Name&quot;: &quot;config_is_local&quot;,
        &quot;Help&quot;: &quot;Use web browser to automatically authenticate rclone with remote?\n * Say Y if the machine running rclone has a web browser you can use\n * Say N if running rclone on a (remote) machine without web browser access\nIf not sure try Y. If Y failed, try N.\n&quot;,
        &quot;Default&quot;: true,
        &quot;Examples&quot;: [
            {
                &quot;Value&quot;: &quot;true&quot;,
                &quot;Help&quot;: &quot;Yes&quot;
            },
            {
                &quot;Value&quot;: &quot;false&quot;,
                &quot;Help&quot;: &quot;No&quot;
            }
        ],
        &quot;Required&quot;: false,
        &quot;IsPassword&quot;: false,
        &quot;Type&quot;: &quot;bool&quot;,
        &quot;Exclusive&quot;: true,
    },
    &quot;Error&quot;: &quot;&quot;,
}</code></pre>
<p>The format of <code>Option</code> is the same as returned by <code>rclone config providers</code>. The question should be asked to the user and returned to rclone as the <code>--result</code> option along with the <code>--state</code> parameter.</p>
<p>The keys of <code>Option</code> are used as follows:</p>
<ul>
<li><code>Name</code> - name of variable - show to user</li>
<li><code>Help</code> - help text. Hard wrapped at 80 chars. Any URLs should be clicky.</li>
<li><code>Default</code> - default value - return this if the user just wants the default.</li>
<li><code>Examples</code> - the user should be able to choose one of these</li>
<li><code>Required</code> - the value should be non-empty</li>
<li><code>IsPassword</code> - the value is a password and should be edited as such</li>
<li><code>Type</code> - type of value, eg <code>bool</code>, <code>string</code>, <code>int</code> and others</li>
<li><code>Exclusive</code> - if set no free-form entry allowed only the <code>Examples</code></li>
<li>Irrelevant keys <code>Provider</code>, <code>ShortOpt</code>, <code>Hide</code>, <code>NoPrefix</code>, <code>Advanced</code></li>
</ul>
<p>If <code>Error</code> is set then it should be shown to the user at the same time as the question.</p>
<pre><code>rclone config update name --continue --state &quot;*oauth-islocal,teamdrive,,&quot; --result &quot;true&quot;</code></pre>
<p>Note that when using <code>--continue</code> all passwords should be passed in the clear (not obscured). Any default config values should be passed in with each invocation of <code>--continue</code>.</p>
<p>At the end of the non interactive process, rclone will return a result with <code>State</code> as empty string.</p>
<p>If <code>--all</code> is passed then rclone will ask all the config questions, not just the post config questions. Any parameters are used as defaults for questions as usual.</p>
<p>Note that <code>bin/config.py</code> in the rclone source implements this protocol as a readable demonstration.</p>
<pre><code>rclone config create name type [key value]* [flags]</code></pre>
<h2 id="options-29">Options</h2>
<pre><code>      --all               Ask the full set of config questions
      --continue          Continue the configuration process with an answer
  -h, --help              help for create
      --no-obscure        Force any passwords not to be obscured
      --non-interactive   Don&#39;t interact with user and return questions
      --obscure           Force any passwords to be obscured
      --result string     Result - use with --continue
      --state string      State - use with --continue</code></pre>
<p>See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
<h2 id="see-also-29">See Also</h2>
<ul>
<li><a href="https://rclone.org/commands/rclone_config/">rclone config</a> - Enter an interactive configuration session.</li>
</ul>
<h1 id="rclone-config-delete">rclone config delete</h1>
<p>Delete an existing remote.</p>
<pre><code>rclone config delete name [flags]</code></pre>
<h2 id="options-30">Options</h2>
<pre><code>  -h, --help   help for delete</code></pre>
<p>See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
<h2 id="see-also-30">See Also</h2>
<ul>
<li><a href="https://rclone.org/commands/rclone_config/">rclone config</a> - Enter an interactive configuration session.</li>
</ul>
<h1 id="rclone-config-disconnect">rclone config disconnect</h1>
<p>Disconnects user from remote</p>
<h2 id="synopsis-29">Synopsis</h2>
<p>This disconnects the remote: passed in to the cloud storage system.</p>
<p>This normally means revoking the oauth token.</p>
<p>To reconnect use "rclone config reconnect".</p>
<pre><code>rclone config disconnect remote: [flags]</code></pre>
<h2 id="options-31">Options</h2>
<pre><code>  -h, --help   help for disconnect</code></pre>
<p>See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
<h2 id="see-also-31">See Also</h2>
<ul>
<li><a href="https://rclone.org/commands/rclone_config/">rclone config</a> - Enter an interactive configuration session.</li>
</ul>
<h1 id="rclone-config-dump">rclone config dump</h1>
<p>Dump the config file as JSON.</p>
<pre><code>rclone config dump [flags]</code></pre>
<h2 id="options-32">Options</h2>
<pre><code>  -h, --help   help for dump</code></pre>
<p>See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
<h2 id="see-also-32">See Also</h2>
<ul>
<li><a href="https://rclone.org/commands/rclone_config/">rclone config</a> - Enter an interactive configuration session.</li>
</ul>
<h1 id="rclone-config-edit">rclone config edit</h1>
<p>Enter an interactive configuration session.</p>
<h2 id="synopsis-30">Synopsis</h2>
<p>Enter an interactive configuration session where you can setup new remotes and manage existing ones. You may also set or remove a password to protect your configuration.</p>
<pre><code>rclone config edit [flags]</code></pre>
<h2 id="options-33">Options</h2>
<pre><code>  -h, --help   help for edit</code></pre>
<p>See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
<h2 id="see-also-33">See Also</h2>
<ul>
<li><a href="https://rclone.org/commands/rclone_config/">rclone config</a> - Enter an interactive configuration session.</li>
</ul>
<h1 id="rclone-config-encryption">rclone config encryption</h1>
<p>set, remove and check the encryption for the config file</p>
<h2 id="synopsis-31">Synopsis</h2>
<p>This command sets, clears and checks the encryption for the config file using the subcommands below.</p>
<h2 id="options-34">Options</h2>
<pre><code>  -h, --help   help for encryption</code></pre>
<p>See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
<h2 id="see-also-34">See Also</h2>
<ul>
<li><a href="https://rclone.org/commands/rclone_config/">rclone config</a> - Enter an interactive configuration session.</li>
<li><a href="https://rclone.org/commands/rclone_config_encryption_check/">rclone config encryption check</a> - Check that the config file is encrypted</li>
<li><a href="https://rclone.org/commands/rclone_config_encryption_remove/">rclone config encryption remove</a> - Remove the config file encryption password</li>
<li><a href="https://rclone.org/commands/rclone_config_encryption_set/">rclone config encryption set</a> - Set or change the config file encryption password</li>
</ul>
<h1 id="rclone-config-encryption-check">rclone config encryption check</h1>
<p>Check that the config file is encrypted</p>
<h2 id="synopsis-32">Synopsis</h2>
<p>This checks the config file is encrypted and that you can decrypt it.</p>
<p>It will attempt to decrypt the config using the password you supply.</p>
<p>If decryption fails it will return a non-zero exit code if using <code>--password-command</code>, otherwise it will prompt again for the password.</p>
<p>If the config file is not encrypted it will return a non zero exit code.</p>
<pre><code>rclone config encryption check [flags]</code></pre>
<h2 id="options-35">Options</h2>
<pre><code>  -h, --help   help for check</code></pre>
<p>See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
<h2 id="see-also-35">See Also</h2>
<ul>
<li><a href="https://rclone.org/commands/rclone_config_encryption/">rclone config encryption</a> - set, remove and check the encryption for the config file</li>
</ul>
<h1 id="rclone-config-encryption-remove">rclone config encryption remove</h1>
<p>Remove the config file encryption password</p>
<h2 id="synopsis-33">Synopsis</h2>
<p>Remove the config file encryption password</p>
<p>This removes the config file encryption, returning it to un-encrypted.</p>
<p>If <code>--password-command</code> is in use, this will be called to supply the old config password.</p>
<p>If the config was not encrypted then no error will be returned and this command will do nothing.</p>
<pre><code>rclone config encryption remove [flags]</code></pre>
<h2 id="options-36">Options</h2>
<pre><code>  -h, --help   help for remove</code></pre>
<p>See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
<h2 id="see-also-36">See Also</h2>
<ul>
<li><a href="https://rclone.org/commands/rclone_config_encryption/">rclone config encryption</a> - set, remove and check the encryption for the config file</li>
</ul>
<h1 id="rclone-config-encryption-set">rclone config encryption set</h1>
<p>Set or change the config file encryption password</p>
<h2 id="synopsis-34">Synopsis</h2>
<p>This command sets or changes the config file encryption password.</p>
<p>If there was no config password set then it sets a new one, otherwise it changes the existing config password.</p>
<p>Note that if you are changing an encryption password using <code>--password-command</code> then this will be called once to decrypt the config using the old password and then again to read the new password to re-encrypt the config.</p>
<p>When <code>--password-command</code> is called to change the password then the environment variable <code>RCLONE_PASSWORD_CHANGE=1</code> will be set. So if changing passwords programatically you can use the environment variable to distinguish which password you must supply.</p>
<p>Alternatively you can remove the password first (with <code>rclone config encryption remove</code>), then set it again with this command which may be easier if you don't mind the unecrypted config file being on the disk briefly.</p>
<pre><code>rclone config encryption set [flags]</code></pre>
<h2 id="options-37">Options</h2>
<pre><code>  -h, --help   help for set</code></pre>
<p>See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
<h2 id="see-also-37">See Also</h2>
<ul>
<li><a href="https://rclone.org/commands/rclone_config_encryption/">rclone config encryption</a> - set, remove and check the encryption for the config file</li>
</ul>
<h1 id="rclone-config-file">rclone config file</h1>
<p>Show path of configuration file in use.</p>
<pre><code>rclone config file [flags]</code></pre>
<h2 id="options-38">Options</h2>
<pre><code>  -h, --help   help for file</code></pre>
<p>See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
<h2 id="see-also-38">See Also</h2>
<ul>
<li><a href="https://rclone.org/commands/rclone_config/">rclone config</a> - Enter an interactive configuration session.</li>
</ul>
<h1 id="rclone-config-password">rclone config password</h1>
<p>Update password in an existing remote.</p>
<h2 id="synopsis-35">Synopsis</h2>
<p>Update an existing remote's password. The password should be passed in pairs of <code>key</code> <code>password</code> or as <code>key=password</code>. The <code>password</code> should be passed in in clear (unobscured).</p>
<p>For example, to set password of a remote of name myremote you would do:</p>
<pre><code>rclone config password myremote fieldname mypassword
rclone config password myremote fieldname=mypassword</code></pre>
<p>This command is obsolete now that "config update" and "config create" both support obscuring passwords directly.</p>
<pre><code>rclone config password name [key value]+ [flags]</code></pre>
<h2 id="options-39">Options</h2>
<pre><code>  -h, --help   help for password</code></pre>
<p>See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
<h2 id="see-also-39">See Also</h2>
<ul>
<li><a href="https://rclone.org/commands/rclone_config/">rclone config</a> - Enter an interactive configuration session.</li>
</ul>
<h1 id="rclone-config-paths">rclone config paths</h1>
<p>Show paths used for configuration, cache, temp etc.</p>
<pre><code>rclone config paths [flags]</code></pre>
<h2 id="options-40">Options</h2>
<pre><code>  -h, --help   help for paths</code></pre>
<p>See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
<h2 id="see-also-40">See Also</h2>
<ul>
<li><a href="https://rclone.org/commands/rclone_config/">rclone config</a> - Enter an interactive configuration session.</li>
</ul>
<h1 id="rclone-config-providers">rclone config providers</h1>
<p>List in JSON format all the providers and options.</p>
<pre><code>rclone config providers [flags]</code></pre>
<h2 id="options-41">Options</h2>
<pre><code>  -h, --help   help for providers</code></pre>
<p>See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
<h2 id="see-also-41">See Also</h2>
<ul>
<li><a href="https://rclone.org/commands/rclone_config/">rclone config</a> - Enter an interactive configuration session.</li>
</ul>
<h1 id="rclone-config-reconnect">rclone config reconnect</h1>
<p>Re-authenticates user with remote.</p>
<h2 id="synopsis-36">Synopsis</h2>
<p>This reconnects remote: passed in to the cloud storage system.</p>
<p>To disconnect the remote use "rclone config disconnect".</p>
<p>This normally means going through the interactive oauth flow again.</p>
<pre><code>rclone config reconnect remote: [flags]</code></pre>
<h2 id="options-42">Options</h2>
<pre><code>  -h, --help   help for reconnect</code></pre>
<p>See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
<h2 id="see-also-42">See Also</h2>
<ul>
<li><a href="https://rclone.org/commands/rclone_config/">rclone config</a> - Enter an interactive configuration session.</li>
</ul>
<h1 id="rclone-config-redacted">rclone config redacted</h1>
<p>Print redacted (decrypted) config file, or the redacted config for a single remote.</p>
<h2 id="synopsis-37">Synopsis</h2>
<p>This prints a redacted copy of the config file, either the whole config file or for a given remote.</p>
<p>The config file will be redacted by replacing all passwords and other sensitive info with XXX.</p>
<p>This makes the config file suitable for posting online for support.</p>
<p>It should be double checked before posting as the redaction may not be perfect.</p>
<pre><code>rclone config redacted [&lt;remote&gt;] [flags]</code></pre>
<h2 id="options-43">Options</h2>
<pre><code>  -h, --help   help for redacted</code></pre>
<p>See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
<h2 id="see-also-43">See Also</h2>
<ul>
<li><a href="https://rclone.org/commands/rclone_config/">rclone config</a> - Enter an interactive configuration session.</li>
</ul>
<h1 id="rclone-config-show">rclone config show</h1>
<p>Print (decrypted) config file, or the config for a single remote.</p>
<pre><code>rclone config show [&lt;remote&gt;] [flags]</code></pre>
<h2 id="options-44">Options</h2>
<pre><code>  -h, --help   help for show</code></pre>
<p>See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
<h2 id="see-also-44">See Also</h2>
<ul>
<li><a href="https://rclone.org/commands/rclone_config/">rclone config</a> - Enter an interactive configuration session.</li>
</ul>
<h1 id="rclone-config-touch">rclone config touch</h1>
<p>Ensure configuration file exists.</p>
<pre><code>rclone config touch [flags]</code></pre>
<h2 id="options-45">Options</h2>
<pre><code>  -h, --help   help for touch</code></pre>
<p>See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
<h2 id="see-also-45">See Also</h2>
<ul>
<li><a href="https://rclone.org/commands/rclone_config/">rclone config</a> - Enter an interactive configuration session.</li>
</ul>
<h1 id="rclone-config-update">rclone config update</h1>
<p>Update options in an existing remote.</p>
<h2 id="synopsis-38">Synopsis</h2>
<p>Update an existing remote's options. The options should be passed in pairs of <code>key</code> <code>value</code> or as <code>key=value</code>.</p>
<p>For example, to update the env_auth field of a remote of name myremote you would do:</p>
<pre><code>rclone config update myremote env_auth true
rclone config update myremote env_auth=true</code></pre>
<p>If the remote uses OAuth the token will be updated, if you don't require this add an extra parameter thus:</p>
<pre><code>rclone config update myremote env_auth=true config_refresh_token=false</code></pre>
<p>Note that if the config process would normally ask a question the default is taken (unless <code>--non-interactive</code> is used). Each time that happens rclone will print or DEBUG a message saying how to affect the value taken.</p>
<p>If any of the parameters passed is a password field, then rclone will automatically obscure them if they aren't already obscured before putting them in the config file.</p>
<p><strong>NB</strong> If the password parameter is 22 characters or longer and consists only of base64 characters then rclone can get confused about whether the password is already obscured or not and put unobscured passwords into the config file. If you want to be 100% certain that the passwords get obscured then use the <code>--obscure</code> flag, or if you are 100% certain you are already passing obscured passwords then use <code>--no-obscure</code>. You can also set obscured passwords using the <code>rclone config password</code> command.</p>
<p>The flag <code>--non-interactive</code> is for use by applications that wish to configure rclone themselves, rather than using rclone's text based configuration questions. If this flag is set, and rclone needs to ask the user a question, a JSON blob will be returned with the question in it.</p>
<p>This will look something like (some irrelevant detail removed):</p>
<pre><code>{
    &quot;State&quot;: &quot;*oauth-islocal,teamdrive,,&quot;,
    &quot;Option&quot;: {
        &quot;Name&quot;: &quot;config_is_local&quot;,
        &quot;Help&quot;: &quot;Use web browser to automatically authenticate rclone with remote?\n * Say Y if the machine running rclone has a web browser you can use\n * Say N if running rclone on a (remote) machine without web browser access\nIf not sure try Y. If Y failed, try N.\n&quot;,
        &quot;Default&quot;: true,
        &quot;Examples&quot;: [
            {
                &quot;Value&quot;: &quot;true&quot;,
                &quot;Help&quot;: &quot;Yes&quot;
            },
            {
                &quot;Value&quot;: &quot;false&quot;,
                &quot;Help&quot;: &quot;No&quot;
            }
        ],
        &quot;Required&quot;: false,
        &quot;IsPassword&quot;: false,
        &quot;Type&quot;: &quot;bool&quot;,
        &quot;Exclusive&quot;: true,
    },
    &quot;Error&quot;: &quot;&quot;,
}</code></pre>
<p>The format of <code>Option</code> is the same as returned by <code>rclone config providers</code>. The question should be asked to the user and returned to rclone as the <code>--result</code> option along with the <code>--state</code> parameter.</p>
<p>The keys of <code>Option</code> are used as follows:</p>
<ul>
<li><code>Name</code> - name of variable - show to user</li>
<li><code>Help</code> - help text. Hard wrapped at 80 chars. Any URLs should be clicky.</li>
<li><code>Default</code> - default value - return this if the user just wants the default.</li>
<li><code>Examples</code> - the user should be able to choose one of these</li>
<li><code>Required</code> - the value should be non-empty</li>
<li><code>IsPassword</code> - the value is a password and should be edited as such</li>
<li><code>Type</code> - type of value, eg <code>bool</code>, <code>string</code>, <code>int</code> and others</li>
<li><code>Exclusive</code> - if set no free-form entry allowed only the <code>Examples</code></li>
<li>Irrelevant keys <code>Provider</code>, <code>ShortOpt</code>, <code>Hide</code>, <code>NoPrefix</code>, <code>Advanced</code></li>
</ul>
<p>If <code>Error</code> is set then it should be shown to the user at the same time as the question.</p>
<pre><code>rclone config update name --continue --state &quot;*oauth-islocal,teamdrive,,&quot; --result &quot;true&quot;</code></pre>
<p>Note that when using <code>--continue</code> all passwords should be passed in the clear (not obscured). Any default config values should be passed in with each invocation of <code>--continue</code>.</p>
<p>At the end of the non interactive process, rclone will return a result with <code>State</code> as empty string.</p>
<p>If <code>--all</code> is passed then rclone will ask all the config questions, not just the post config questions. Any parameters are used as defaults for questions as usual.</p>
<p>Note that <code>bin/config.py</code> in the rclone source implements this protocol as a readable demonstration.</p>
<pre><code>rclone config update name [key value]+ [flags]</code></pre>
<h2 id="options-46">Options</h2>
<pre><code>      --all               Ask the full set of config questions
      --continue          Continue the configuration process with an answer
  -h, --help              help for update
      --no-obscure        Force any passwords not to be obscured
      --non-interactive   Don&#39;t interact with user and return questions
      --obscure           Force any passwords to be obscured
      --result string     Result - use with --continue
      --state string      State - use with --continue</code></pre>
<p>See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
<h2 id="see-also-46">See Also</h2>
<ul>
<li><a href="https://rclone.org/commands/rclone_config/">rclone config</a> - Enter an interactive configuration session.</li>
</ul>
<h1 id="rclone-config-userinfo">rclone config userinfo</h1>
<p>Prints info about logged in user of remote.</p>
<h2 id="synopsis-39">Synopsis</h2>
<p>This prints the details of the person logged in to the cloud storage system.</p>
<pre><code>rclone config userinfo remote: [flags]</code></pre>
<h2 id="options-47">Options</h2>
<pre><code>  -h, --help   help for userinfo
      --json   Format output as JSON</code></pre>
<p>See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
<h2 id="see-also-47">See Also</h2>
<ul>
<li><a href="https://rclone.org/commands/rclone_config/">rclone config</a> - Enter an interactive configuration session.</li>
</ul>
<h1 id="rclone-copyto">rclone copyto</h1>
<p>Copy files from source to dest, skipping identical files.</p>
<h2 id="synopsis-40">Synopsis</h2>
<p>If source:path is a file or directory then it copies it to a file or directory named dest:path.</p>
<p>This can be used to upload single files to other than their current name. If the source is a directory then it acts exactly like the <a href="https://rclone.org/commands/rclone_copy/">copy</a> command.</p>
<p>So</p>
<pre><code>rclone copyto src dst</code></pre>
<p>where src and dst are rclone paths, either remote:path or /path/to/local or C:.</p>
<p>This will:</p>
<pre><code>if src is file
    copy it to dst, overwriting an existing file if it exists
if src is directory
    copy it to dst, overwriting existing files if they exist
    see copy command for full details</code></pre>
<p>This doesn't transfer files that are identical on src and dst, testing by size and modification time or MD5SUM. It doesn't delete files from the destination.</p>
<p><strong>Note</strong>: Use the <code>-P</code>/<code>--progress</code> flag to view real-time transfer statistics</p>
<pre><code>rclone copyto source:path dest:path [flags]</code></pre>
<h2 id="options-48">Options</h2>
<pre><code>  -h, --help   help for copyto</code></pre>
<p>Options shared with other commands are described next. See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
<h3 id="copy-options-4">Copy Options</h3>
<p>Flags for anything which can copy a file</p>
<pre><code>      --check-first                                 Do all the checks before starting transfers
  -c, --checksum                                    Check for changes with size &amp; checksum (if available, or fallback to size only)
      --compare-dest stringArray                    Include additional server-side paths during comparison
      --copy-dest stringArray                       Implies --compare-dest but also copies files from paths into destination
      --cutoff-mode HARD|SOFT|CAUTIOUS              Mode to stop transfers when reaching the max transfer limit HARD|SOFT|CAUTIOUS (default HARD)
      --ignore-case-sync                            Ignore case when synchronizing
      --ignore-checksum                             Skip post copy check of checksums
      --ignore-existing                             Skip all files that exist on destination
      --ignore-size                                 Ignore size when skipping use modtime or checksum
  -I, --ignore-times                                Don&#39;t skip items that match size and time - transfer all unconditionally
      --immutable                                   Do not modify files, fail if existing files have been modified
      --inplace                                     Download directly to destination file instead of atomic download to temp/rename
      --max-backlog int                             Maximum number of objects in sync or check backlog (default 10000)
      --max-duration Duration                       Maximum duration rclone will transfer data for (default 0s)
      --max-transfer SizeSuffix                     Maximum size of data to transfer (default off)
  -M, --metadata                                    If set, preserve metadata when copying objects
      --modify-window Duration                      Max time diff to be considered the same (default 1ns)
      --multi-thread-chunk-size SizeSuffix          Chunk size for multi-thread downloads / uploads, if not set by filesystem (default 64Mi)
      --multi-thread-cutoff SizeSuffix              Use multi-thread downloads for files above this size (default 256Mi)
      --multi-thread-streams int                    Number of streams to use for multi-thread downloads (default 4)
      --multi-thread-write-buffer-size SizeSuffix   In memory buffer size for writing when in multi-thread mode (default 128Ki)
      --no-check-dest                               Don&#39;t check the destination, copy regardless
      --no-traverse                                 Don&#39;t traverse destination file system on copy
      --no-update-dir-modtime                       Don&#39;t update directory modification times
      --no-update-modtime                           Don&#39;t update destination modtime if files identical
      --order-by string                             Instructions on how to order the transfers, e.g. &#39;size,descending&#39;
      --partial-suffix string                       Add partial-suffix to temporary file name when --inplace is not used (default &quot;.partial&quot;)
      --refresh-times                               Refresh the modtime of remote files
      --server-side-across-configs                  Allow server-side operations (e.g. copy) to work across different configs
      --size-only                                   Skip based on size only, not modtime or checksum
      --streaming-upload-cutoff SizeSuffix          Cutoff for switching to chunked upload if file size is unknown, upload starts after reaching cutoff or when file ends (default 100Ki)
  -u, --update                                      Skip files that are newer on the destination</code></pre>
<h3 id="important-options-11">Important Options</h3>
<p>Important flags useful for most commands</p>
<pre><code>  -n, --dry-run         Do a trial run with no permanent changes
  -i, --interactive     Enable interactive mode
  -v, --verbose count   Print lots more stuff (repeat for more)</code></pre>
<h3 id="filter-options-14">Filter Options</h3>
<p>Flags for filtering directory listings</p>
<pre><code>      --delete-excluded                     Delete files on dest excluded from sync
      --exclude stringArray                 Exclude files matching pattern
      --exclude-from stringArray            Read file exclude patterns from file (use - to read from stdin)
      --exclude-if-present stringArray      Exclude directories if filename is present
      --files-from stringArray              Read list of source-file names from file (use - to read from stdin)
      --files-from-raw stringArray          Read list of source-file names from file without any processing of lines (use - to read from stdin)
  -f, --filter stringArray                  Add a file filtering rule
      --filter-from stringArray             Read file filtering patterns from a file (use - to read from stdin)
      --ignore-case                         Ignore case in filters (case insensitive)
      --include stringArray                 Include files matching pattern
      --include-from stringArray            Read file include patterns from file (use - to read from stdin)
      --max-age Duration                    Only transfer files younger than this in s or suffix ms|s|m|h|d|w|M|y (default off)
      --max-depth int                       If set limits the recursion depth to this (default -1)
      --max-size SizeSuffix                 Only transfer files smaller than this in KiB or suffix B|K|M|G|T|P (default off)
      --metadata-exclude stringArray        Exclude metadatas matching pattern
      --metadata-exclude-from stringArray   Read metadata exclude patterns from file (use - to read from stdin)
      --metadata-filter stringArray         Add a metadata filtering rule
      --metadata-filter-from stringArray    Read metadata filtering patterns from a file (use - to read from stdin)
      --metadata-include stringArray        Include metadatas matching pattern
      --metadata-include-from stringArray   Read metadata include patterns from file (use - to read from stdin)
      --min-age Duration                    Only transfer files older than this in s or suffix ms|s|m|h|d|w|M|y (default off)
      --min-size SizeSuffix                 Only transfer files bigger than this in KiB or suffix B|K|M|G|T|P (default off)</code></pre>
<h3 id="listing-options-13">Listing Options</h3>
<p>Flags for listing directories</p>
<pre><code>      --default-time Time   Time to show if modtime is unknown for files and directories (default 2000-01-01T00:00:00Z)
      --fast-list           Use recursive list if available; uses more memory but fewer transactions</code></pre>
<h2 id="see-also-48">See Also</h2>
<ul>
<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
</ul>
<h1 id="rclone-copyurl">rclone copyurl</h1>
<p>Copy the contents of the URL supplied content to dest:path.</p>
<h2 id="synopsis-41">Synopsis</h2>
<p>Download a URL's content and copy it to the destination without saving it in temporary storage.</p>
<p>Setting <code>--auto-filename</code> will attempt to automatically determine the filename from the URL (after any redirections) and used in the destination path.</p>
<p>With <code>--auto-filename-header</code> in addition, if a specific filename is set in HTTP headers, it will be used instead of the name from the URL. With <code>--print-filename</code> in addition, the resulting file name will be printed.</p>
<p>Setting <code>--no-clobber</code> will prevent overwriting file on the destination if there is one with the same name.</p>
<p>Setting <code>--stdout</code> or making the output file name <code>-</code> will cause the output to be written to standard output.</p>
<h2 id="troublshooting">Troublshooting</h2>
<p>If you can't get <code>rclone copyurl</code> to work then here are some things you can try:</p>
<ul>
<li><code>--disable-http2</code> rclone will use HTTP2 if available - try disabling it</li>
<li><code>--bind 0.0.0.0</code> rclone will use IPv6 if available - try disabling it</li>
<li><code>--bind ::0</code> to disable IPv4</li>
<li><code>--user agent curl</code> - some sites have whitelists for curl's user-agent - try that</li>
<li>Make sure the site works with <code>curl</code> directly</li>
</ul>
<pre><code>rclone copyurl https://example.com dest:path [flags]</code></pre>
<h2 id="options-49">Options</h2>
<pre><code>  -a, --auto-filename     Get the file name from the URL and use it for destination file path
      --header-filename   Get the file name from the Content-Disposition header
  -h, --help              help for copyurl
      --no-clobber        Prevent overwriting file with same name
  -p, --print-filename    Print the resulting name from --auto-filename
      --stdout            Write the output to stdout rather than a file</code></pre>
<p>Options shared with other commands are described next. See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
<h3 id="important-options-12">Important Options</h3>
<p>Important flags useful for most commands</p>
<pre><code>  -n, --dry-run         Do a trial run with no permanent changes
  -i, --interactive     Enable interactive mode
  -v, --verbose count   Print lots more stuff (repeat for more)</code></pre>
<h2 id="see-also-49">See Also</h2>
<ul>
<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
</ul>
<h1 id="rclone-cryptcheck">rclone cryptcheck</h1>
<p>Cryptcheck checks the integrity of an encrypted remote.</p>
<h2 id="synopsis-42">Synopsis</h2>
<p>Checks a remote against a <a href="https://rclone.org/crypt/">crypted</a> remote. This is the equivalent of running rclone <a href="https://rclone.org/commands/rclone_check/">check</a>, but able to check the checksums of the encrypted remote.</p>
<p>For it to work the underlying remote of the cryptedremote must support some kind of checksum.</p>
<p>It works by reading the nonce from each file on the cryptedremote: and using that to encrypt each file on the remote:. It then checks the checksum of the underlying file on the cryptedremote: against the checksum of the file it has just encrypted.</p>
<p>Use it like this</p>
<pre><code>rclone cryptcheck /path/to/files encryptedremote:path</code></pre>
<p>You can use it like this also, but that will involve downloading all the files in remote:path.</p>
<pre><code>rclone cryptcheck remote:path encryptedremote:path</code></pre>
<p>After it has run it will log the status of the encryptedremote:.</p>
<p>If you supply the <code>--one-way</code> flag, it will only check that files in the source match the files in the destination, not the other way around. This means that extra files in the destination that are not in the source will not be detected.</p>
<p>The <code>--differ</code>, <code>--missing-on-dst</code>, <code>--missing-on-src</code>, <code>--match</code> and <code>--error</code> flags write paths, one per line, to the file name (or stdout if it is <code>-</code>) supplied. What they write is described in the help below. For example <code>--differ</code> will write all paths which are present on both the source and destination but different.</p>
<p>The <code>--combined</code> flag will write a file (or stdout) which contains all file paths with a symbol and then a space and then the path to tell you what happened to it. These are reminiscent of diff files.</p>
<ul>
<li><code>= path</code> means path was found in source and destination and was identical</li>
<li>`- path` means path was missing on the source, so only in the destination</li>
<li>`+ path` means path was missing on the destination, so only in the source</li>
<li>`* path` means path was present in source and destination but different.</li>
<li><code>! path</code> means there was an error reading or hashing the source or dest.</li>
</ul>
<p>The default number of parallel checks is 8. See the <a href="https://rclone.org/docs/#checkers-n">--checkers=N</a> option for more information.</p>
<pre><code>rclone cryptcheck remote:path cryptedremote:path [flags]</code></pre>
<h2 id="options-50">Options</h2>
<pre><code>      --combined string         Make a combined report of changes to this file
      --differ string           Report all non-matching files to this file
      --error string            Report all files with errors (hashing or reading) to this file
  -h, --help                    help for cryptcheck
      --match string            Report all matching files to this file
      --missing-on-dst string   Report all files missing from the destination to this file
      --missing-on-src string   Report all files missing from the source to this file
      --one-way                 Check one way only, source files must exist on remote</code></pre>
<p>Options shared with other commands are described next. See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
<h3 id="check-options-1">Check Options</h3>
<p>Flags used for check commands</p>
<pre><code>      --max-backlog int   Maximum number of objects in sync or check backlog (default 10000)</code></pre>
<h3 id="filter-options-15">Filter Options</h3>
<p>Flags for filtering directory listings</p>
<pre><code>      --delete-excluded                     Delete files on dest excluded from sync
      --exclude stringArray                 Exclude files matching pattern
      --exclude-from stringArray            Read file exclude patterns from file (use - to read from stdin)
      --exclude-if-present stringArray      Exclude directories if filename is present
      --files-from stringArray              Read list of source-file names from file (use - to read from stdin)
      --files-from-raw stringArray          Read list of source-file names from file without any processing of lines (use - to read from stdin)
  -f, --filter stringArray                  Add a file filtering rule
      --filter-from stringArray             Read file filtering patterns from a file (use - to read from stdin)
      --ignore-case                         Ignore case in filters (case insensitive)
      --include stringArray                 Include files matching pattern
      --include-from stringArray            Read file include patterns from file (use - to read from stdin)
      --max-age Duration                    Only transfer files younger than this in s or suffix ms|s|m|h|d|w|M|y (default off)
      --max-depth int                       If set limits the recursion depth to this (default -1)
      --max-size SizeSuffix                 Only transfer files smaller than this in KiB or suffix B|K|M|G|T|P (default off)
      --metadata-exclude stringArray        Exclude metadatas matching pattern
      --metadata-exclude-from stringArray   Read metadata exclude patterns from file (use - to read from stdin)
      --metadata-filter stringArray         Add a metadata filtering rule
      --metadata-filter-from stringArray    Read metadata filtering patterns from a file (use - to read from stdin)
      --metadata-include stringArray        Include metadatas matching pattern
      --metadata-include-from stringArray   Read metadata include patterns from file (use - to read from stdin)
      --min-age Duration                    Only transfer files older than this in s or suffix ms|s|m|h|d|w|M|y (default off)
      --min-size SizeSuffix                 Only transfer files bigger than this in KiB or suffix B|K|M|G|T|P (default off)</code></pre>
<h3 id="listing-options-14">Listing Options</h3>
<p>Flags for listing directories</p>
<pre><code>      --default-time Time   Time to show if modtime is unknown for files and directories (default 2000-01-01T00:00:00Z)
      --fast-list           Use recursive list if available; uses more memory but fewer transactions</code></pre>
<h2 id="see-also-50">See Also</h2>
<ul>
<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
</ul>
<h1 id="rclone-cryptdecode">rclone cryptdecode</h1>
<p>Cryptdecode returns unencrypted file names.</p>
<h2 id="synopsis-43">Synopsis</h2>
<p>Returns unencrypted file names when provided with a list of encrypted file names. List limit is 10 items.</p>
<p>If you supply the <code>--reverse</code> flag, it will return encrypted file names.</p>
<p>use it like this</p>
<pre><code>rclone cryptdecode encryptedremote: encryptedfilename1 encryptedfilename2

rclone cryptdecode --reverse encryptedremote: filename1 filename2</code></pre>
<p>Another way to accomplish this is by using the <code>rclone backend encode</code> (or <code>decode</code>) command. See the documentation on the <a href="https://rclone.org/crypt/">crypt</a> overlay for more info.</p>
<pre><code>rclone cryptdecode encryptedremote: encryptedfilename [flags]</code></pre>
<h2 id="options-51">Options</h2>
<pre><code>  -h, --help      help for cryptdecode
      --reverse   Reverse cryptdecode, encrypts filenames</code></pre>
<p>See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
<h2 id="see-also-51">See Also</h2>
<ul>
<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
</ul>
<h1 id="rclone-deletefile">rclone deletefile</h1>
<p>Remove a single file from remote.</p>
<h2 id="synopsis-44">Synopsis</h2>
<p>Remove a single file from remote. Unlike <code>delete</code> it cannot be used to remove a directory and it doesn't obey include/exclude filters - if the specified file exists, it will always be removed.</p>
<pre><code>rclone deletefile remote:path [flags]</code></pre>
<h2 id="options-52">Options</h2>
<pre><code>  -h, --help   help for deletefile</code></pre>
<p>Options shared with other commands are described next. See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
<h3 id="important-options-13">Important Options</h3>
<p>Important flags useful for most commands</p>
<pre><code>  -n, --dry-run         Do a trial run with no permanent changes
  -i, --interactive     Enable interactive mode
  -v, --verbose count   Print lots more stuff (repeat for more)</code></pre>
<h2 id="see-also-52">See Also</h2>
<ul>
<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
</ul>
<h1 id="rclone-gendocs">rclone gendocs</h1>
<p>Output markdown docs for rclone to the directory supplied.</p>
<h2 id="synopsis-45">Synopsis</h2>
<p>This produces markdown docs for the rclone commands to the directory supplied. These are in a format suitable for hugo to render into the rclone.org website.</p>
<pre><code>rclone gendocs output_directory [flags]</code></pre>
<h2 id="options-53">Options</h2>
<pre><code>  -h, --help   help for gendocs</code></pre>
<p>See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
<h2 id="see-also-53">See Also</h2>
<ul>
<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
</ul>
<h1 id="rclone-gitannex">rclone gitannex</h1>
<p>Speaks with git-annex over stdin/stdout.</p>
<h2 id="synopsis-46">Synopsis</h2>
<p>Rclone's <code>gitannex</code> subcommand enables <a href="https://git-annex.branchable.com/">git-annex</a> to store and retrieve content from an rclone remote. It is meant to be run by git-annex, not directly by users.</p>
<h2 id="installation-on-linux">Installation on Linux</h2>
<ol type="1">
<li><p>Skip this step if your version of git-annex is <a href="https://git-annex.branchable.com/news/version_10.20240430/">10.20240430</a> or newer. Otherwise, you must create a symlink somewhere on your PATH with a particular name. This symlink helps git-annex tell rclone it wants to run the "gitannex" subcommand.</p>
<div class="sourceCode" id="cb253"><pre class="sourceCode sh"><code class="sourceCode bash"><span id="cb253-1"><a href="#cb253-1" aria-hidden="true"></a><span class="co"># Create the helper symlink in &quot;$HOME/bin&quot;.</span></span>
<span id="cb253-2"><a href="#cb253-2" aria-hidden="true"></a><span class="fu">ln</span> -s <span class="st">&quot;</span><span class="va">$(</span><span class="ex">realpath</span> rclone<span class="va">)</span><span class="st">&quot;</span> <span class="st">&quot;</span><span class="va">$HOME</span><span class="st">/bin/git-annex-remote-rclone-builtin&quot;</span></span>
<span id="cb253-3"><a href="#cb253-3" aria-hidden="true"></a></span>
<span id="cb253-4"><a href="#cb253-4" aria-hidden="true"></a><span class="co"># Verify the new symlink is on your PATH.</span></span>
<span id="cb253-5"><a href="#cb253-5" aria-hidden="true"></a><span class="fu">which</span> git-annex-remote-rclone-builtin</span></code></pre></div></li>
<li><p>Add a new remote to your git-annex repo. This new remote will connect git-annex with the <code>rclone gitannex</code> subcommand.</p>
<p>Start by asking git-annex to describe the remote's available configuration parameters.</p>
<div class="sourceCode" id="cb254"><pre class="sourceCode sh"><code class="sourceCode bash"><span id="cb254-1"><a href="#cb254-1" aria-hidden="true"></a><span class="co"># If you skipped step 1:</span></span>
<span id="cb254-2"><a href="#cb254-2" aria-hidden="true"></a><span class="fu">git</span> annex initremote MyRemote type=rclone --whatelse</span>
<span id="cb254-3"><a href="#cb254-3" aria-hidden="true"></a></span>
<span id="cb254-4"><a href="#cb254-4" aria-hidden="true"></a><span class="co"># If you created a symlink in step 1:</span></span>
<span id="cb254-5"><a href="#cb254-5" aria-hidden="true"></a><span class="fu">git</span> annex initremote MyRemote type=external externaltype=rclone-builtin --whatelse</span></code></pre></div>
<blockquote>
<p><strong>NOTE</strong>: If you're porting an existing <a href="https://github.com/git-annex-remote-rclone/git-annex-remote-rclone">git-annex-remote-rclone</a> remote to use <code>rclone gitannex</code>, you can probably reuse the configuration parameters verbatim without renaming them. Check parameter synonyms with <code>--whatelse</code> as shown above.</p>
</blockquote>
<p>The following example creates a new git-annex remote named "MyRemote" that will use the rclone remote named "SomeRcloneRemote". That rclone remote must be one configured in your rclone.conf file, which can be located with <code>rclone config file</code>.</p>
<div class="sourceCode" id="cb255"><pre class="sourceCode sh"><code class="sourceCode bash"><span id="cb255-1"><a href="#cb255-1" aria-hidden="true"></a><span class="fu">git</span> annex initremote MyRemote         <span class="kw">\</span></span>
<span id="cb255-2"><a href="#cb255-2" aria-hidden="true"></a>    <span class="va">type=</span>external                     <span class="kw">\</span></span>
<span id="cb255-3"><a href="#cb255-3" aria-hidden="true"></a>    <span class="va">externaltype=</span>rclone-builtin       <span class="kw">\</span></span>
<span id="cb255-4"><a href="#cb255-4" aria-hidden="true"></a>    <span class="va">encryption=</span>none                   <span class="kw">\</span></span>
<span id="cb255-5"><a href="#cb255-5" aria-hidden="true"></a>    <span class="va">rcloneremotename=</span>SomeRcloneRemote <span class="kw">\</span></span>
<span id="cb255-6"><a href="#cb255-6" aria-hidden="true"></a>    <span class="va">rcloneprefix=</span>git-annex-content    <span class="kw">\</span></span>
<span id="cb255-7"><a href="#cb255-7" aria-hidden="true"></a>    <span class="va">rclonelayout=</span>nodir</span></code></pre></div></li>
<li><p>Before you trust this command with your precious data, be sure to <strong>test the remote</strong>. This command is very new and has not been tested on many rclone backends. Caveat emptor!</p>
<div class="sourceCode" id="cb256"><pre class="sourceCode sh"><code class="sourceCode bash"><span id="cb256-1"><a href="#cb256-1" aria-hidden="true"></a><span class="fu">git</span> annex testremote MyRemote</span></code></pre></div></li>
</ol>
<p>Happy annexing!</p>
<pre><code>rclone gitannex [flags]</code></pre>
<h2 id="options-54">Options</h2>
<pre><code>  -h, --help   help for gitannex</code></pre>
<p>See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
<h2 id="see-also-54">See Also</h2>
<ul>
<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
</ul>
<h1 id="rclone-hashsum">rclone hashsum</h1>
<p>Produces a hashsum file for all the objects in the path.</p>
<h2 id="synopsis-47">Synopsis</h2>
<p>Produces a hash file for all the objects in the path using the hash named. The output is in the same format as the standard md5sum/sha1sum tool.</p>
<p>By default, the hash is requested from the remote. If the hash is not supported by the remote, no hash will be returned. With the download flag, the file will be downloaded from the remote and hashed locally enabling any hash for any remote.</p>
<p>For the MD5 and SHA1 algorithms there are also dedicated commands, <a href="https://rclone.org/commands/rclone_md5sum/">md5sum</a> and <a href="https://rclone.org/commands/rclone_sha1sum/">sha1sum</a>.</p>
<p>This command can also hash data received on standard input (stdin), by not passing a remote:path, or by passing a hyphen as remote:path when there is data to read (if not, the hyphen will be treated literally, as a relative path).</p>
<p>Run without a hash to see the list of all supported hashes, e.g.</p>
<pre><code>$ rclone hashsum
Supported hashes are:
  * md5
  * sha1
  * whirlpool
  * crc32
  * sha256</code></pre>
<p>Then</p>
<pre><code>$ rclone hashsum MD5 remote:path</code></pre>
<p>Note that hash names are case insensitive and values are output in lower case.</p>
<pre><code>rclone hashsum [&lt;hash&gt; remote:path] [flags]</code></pre>
<h2 id="options-55">Options</h2>
<pre><code>      --base64               Output base64 encoded hashsum
  -C, --checkfile string     Validate hashes against a given SUM file instead of printing them
      --download             Download the file and hash it locally; if this flag is not specified, the hash is requested from the remote
  -h, --help                 help for hashsum
      --output-file string   Output hashsums to a file rather than the terminal</code></pre>
<p>Options shared with other commands are described next. See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
<h3 id="filter-options-16">Filter Options</h3>
<p>Flags for filtering directory listings</p>
<pre><code>      --delete-excluded                     Delete files on dest excluded from sync
      --exclude stringArray                 Exclude files matching pattern
      --exclude-from stringArray            Read file exclude patterns from file (use - to read from stdin)
      --exclude-if-present stringArray      Exclude directories if filename is present
      --files-from stringArray              Read list of source-file names from file (use - to read from stdin)
      --files-from-raw stringArray          Read list of source-file names from file without any processing of lines (use - to read from stdin)
  -f, --filter stringArray                  Add a file filtering rule
      --filter-from stringArray             Read file filtering patterns from a file (use - to read from stdin)
      --ignore-case                         Ignore case in filters (case insensitive)
      --include stringArray                 Include files matching pattern
      --include-from stringArray            Read file include patterns from file (use - to read from stdin)
      --max-age Duration                    Only transfer files younger than this in s or suffix ms|s|m|h|d|w|M|y (default off)
      --max-depth int                       If set limits the recursion depth to this (default -1)
      --max-size SizeSuffix                 Only transfer files smaller than this in KiB or suffix B|K|M|G|T|P (default off)
      --metadata-exclude stringArray        Exclude metadatas matching pattern
      --metadata-exclude-from stringArray   Read metadata exclude patterns from file (use - to read from stdin)
      --metadata-filter stringArray         Add a metadata filtering rule
      --metadata-filter-from stringArray    Read metadata filtering patterns from a file (use - to read from stdin)
      --metadata-include stringArray        Include metadatas matching pattern
      --metadata-include-from stringArray   Read metadata include patterns from file (use - to read from stdin)
      --min-age Duration                    Only transfer files older than this in s or suffix ms|s|m|h|d|w|M|y (default off)
      --min-size SizeSuffix                 Only transfer files bigger than this in KiB or suffix B|K|M|G|T|P (default off)</code></pre>
<h3 id="listing-options-15">Listing Options</h3>
<p>Flags for listing directories</p>
<pre><code>      --default-time Time   Time to show if modtime is unknown for files and directories (default 2000-01-01T00:00:00Z)
      --fast-list           Use recursive list if available; uses more memory but fewer transactions</code></pre>
<h2 id="see-also-55">See Also</h2>
<ul>
<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
</ul>
<h1 id="rclone-link">rclone link</h1>
<p>Generate public link to file/folder.</p>
<h2 id="synopsis-48">Synopsis</h2>
<p>Create, retrieve or remove a public link to the given file or folder.</p>
<pre><code>rclone link remote:path/to/file
rclone link remote:path/to/folder/
rclone link --unlink remote:path/to/folder/
rclone link --expire 1d remote:path/to/file</code></pre>
<p>If you supply the --expire flag, it will set the expiration time otherwise it will use the default (100 years). <strong>Note</strong> not all backends support the --expire flag - if the backend doesn't support it then the link returned won't expire.</p>
<p>Use the --unlink flag to remove existing public links to the file or folder. <strong>Note</strong> not all backends support "--unlink" flag - those that don't will just ignore it.</p>
<p>If successful, the last line of the output will contain the link. Exact capabilities depend on the remote, but the link will always by default be created with the least constraints – e.g. no expiry, no password protection, accessible without account.</p>
<pre><code>rclone link remote:path [flags]</code></pre>
<h2 id="options-56">Options</h2>
<pre><code>      --expire Duration   The amount of time that the link will be valid (default off)
  -h, --help              help for link
      --unlink            Remove existing public link to file/folder</code></pre>
<p>See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
<h2 id="see-also-56">See Also</h2>
<ul>
<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
</ul>
<h1 id="rclone-listremotes">rclone listremotes</h1>
<p>List all the remotes in the config file and defined in environment variables.</p>
<h2 id="synopsis-49">Synopsis</h2>
<p>Lists all the available remotes from the config file, or the remotes matching an optional filter.</p>
<p>Prints the result in human-readable format by default, and as a simple list of remote names, or if used with flag <code>--long</code> a tabular format including the remote names, types and descriptions. Using flag <code>--json</code> produces machine-readable output instead, which always includes all attributes - including the source (file or environment).</p>
<p>Result can be filtered by a filter argument which applies to all attributes, and/or filter flags specific for each attribute. The values must be specified according to regular rclone filtering pattern syntax.</p>
<pre><code>rclone listremotes [&lt;filter&gt;] [flags]</code></pre>
<h2 id="options-57">Options</h2>
<pre><code>      --description string   Filter remotes by description
  -h, --help                 help for listremotes
      --json                 Format output as JSON
      --long                 Show type and description in addition to name
      --name string          Filter remotes by name
      --order-by string      Instructions on how to order the result, e.g. &#39;type,name=descending&#39;
      --source string        Filter remotes by source, e.g. &#39;file&#39; or &#39;environment&#39;
      --type string          Filter remotes by type</code></pre>
<p>See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
<h2 id="see-also-57">See Also</h2>
<ul>
<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
</ul>
<h1 id="rclone-lsf">rclone lsf</h1>
<p>List directories and objects in remote:path formatted for parsing.</p>
<h2 id="synopsis-50">Synopsis</h2>
<p>List the contents of the source path (directories and objects) to standard output in a form which is easy to parse by scripts. By default this will just be the names of the objects and directories, one per line. The directories will have a / suffix.</p>
<p>Eg</p>
<pre><code>$ rclone lsf swift:bucket
bevajer5jef
canole
diwogej7
ferejej3gux/
fubuwic</code></pre>
<p>Use the <code>--format</code> option to control what gets listed. By default this is just the path, but you can use these parameters to control the output:</p>
<pre><code>p - path
s - size
t - modification time
h - hash
i - ID of object
o - Original ID of underlying object
m - MimeType of object if known
e - encrypted name
T - tier of storage if known, e.g. &quot;Hot&quot; or &quot;Cool&quot;
M - Metadata of object in JSON blob format, eg {&quot;key&quot;:&quot;value&quot;}</code></pre>
<p>So if you wanted the path, size and modification time, you would use <code>--format "pst"</code>, or maybe <code>--format "tsp"</code> to put the path last.</p>
<p>Eg</p>
<pre><code>$ rclone lsf  --format &quot;tsp&quot; swift:bucket
2016-06-25 18:55:41;60295;bevajer5jef
2016-06-25 18:55:43;90613;canole
2016-06-25 18:55:43;94467;diwogej7
2018-04-26 08:50:45;0;ferejej3gux/
2016-06-25 18:55:40;37600;fubuwic</code></pre>
<p>If you specify "h" in the format you will get the MD5 hash by default, use the <code>--hash</code> flag to change which hash you want. Note that this can be returned as an empty string if it isn't available on the object (and for directories), "ERROR" if there was an error reading it from the object and "UNSUPPORTED" if that object does not support that hash type.</p>
<p>For example, to emulate the md5sum command you can use</p>
<pre><code>rclone lsf -R --hash MD5 --format hp --separator &quot;  &quot; --files-only .</code></pre>
<p>Eg</p>
<pre><code>$ rclone lsf -R --hash MD5 --format hp --separator &quot;  &quot; --files-only swift:bucket
7908e352297f0f530b84a756f188baa3  bevajer5jef
cd65ac234e6fea5925974a51cdd865cc  canole
03b5341b4f234b9d984d03ad076bae91  diwogej7
8fd37c3810dd660778137ac3a66cc06d  fubuwic
99713e14a4c4ff553acaf1930fad985b  gixacuh7ku</code></pre>
<p>(Though "rclone md5sum ." is an easier way of typing this.)</p>
<p>By default the separator is ";" this can be changed with the <code>--separator</code> flag. Note that separators aren't escaped in the path so putting it last is a good strategy.</p>
<p>Eg</p>
<pre><code>$ rclone lsf  --separator &quot;,&quot; --format &quot;tshp&quot; swift:bucket
2016-06-25 18:55:41,60295,7908e352297f0f530b84a756f188baa3,bevajer5jef
2016-06-25 18:55:43,90613,cd65ac234e6fea5925974a51cdd865cc,canole
2016-06-25 18:55:43,94467,03b5341b4f234b9d984d03ad076bae91,diwogej7
2018-04-26 08:52:53,0,,ferejej3gux/
2016-06-25 18:55:40,37600,8fd37c3810dd660778137ac3a66cc06d,fubuwic</code></pre>
<p>You can output in CSV standard format. This will escape things in " if they contain ,</p>
<p>Eg</p>
<pre><code>$ rclone lsf --csv --files-only --format ps remote:path
test.log,22355
test.sh,449
&quot;this file contains a comma, in the file name.txt&quot;,6</code></pre>
<p>Note that the <code>--absolute</code> parameter is useful for making lists of files to pass to an rclone copy with the <code>--files-from-raw</code> flag.</p>
<p>For example, to find all the files modified within one day and copy those only (without traversing the whole directory structure):</p>
<pre><code>rclone lsf --absolute --files-only --max-age 1d /path/to/local &gt; new_files
rclone copy --files-from-raw new_files /path/to/local remote:path</code></pre>
<p>The default time format is <code>'2006-01-02 15:04:05'</code>. <a href="https://pkg.go.dev/time#pkg-constants">Other formats</a> can be specified with the <code>--time-format</code> flag. Examples:</p>
<pre><code>rclone lsf remote:path --format pt --time-format &#39;Jan 2, 2006 at 3:04pm (MST)&#39;
rclone lsf remote:path --format pt --time-format &#39;2006-01-02 15:04:05.000000000&#39;
rclone lsf remote:path --format pt --time-format &#39;2006-01-02T15:04:05.999999999Z07:00&#39;
rclone lsf remote:path --format pt --time-format RFC3339
rclone lsf remote:path --format pt --time-format DateOnly
rclone lsf remote:path --format pt --time-format max</code></pre>
<p><code>--time-format max</code> will automatically truncate '<code>2006-01-02 15:04:05.000000000</code>' to the maximum precision supported by the remote.</p>
<p>Any of the filtering options can be applied to this command.</p>
<p>There are several related list commands</p>
<ul>
<li><code>ls</code> to list size and path of objects only</li>
<li><code>lsl</code> to list modification time, size and path of objects only</li>
<li><code>lsd</code> to list directories only</li>
<li><code>lsf</code> to list objects and directories in easy to parse format</li>
<li><code>lsjson</code> to list objects and directories in JSON format</li>
</ul>
<p><code>ls</code>,<code>lsl</code>,<code>lsd</code> are designed to be human-readable. <code>lsf</code> is designed to be human and machine-readable. <code>lsjson</code> is designed to be machine-readable.</p>
<p>Note that <code>ls</code> and <code>lsl</code> recurse by default - use <code>--max-depth 1</code> to stop the recursion.</p>
<p>The other list commands <code>lsd</code>,<code>lsf</code>,<code>lsjson</code> do not recurse by default - use <code>-R</code> to make them recurse.</p>
<p>Listing a nonexistent directory will produce an error except for remotes which can't have empty directories (e.g. s3, swift, or gcs - the bucket-based remotes).</p>
<pre><code>rclone lsf remote:path [flags]</code></pre>
<h2 id="options-58">Options</h2>
<pre><code>      --absolute             Put a leading / in front of path names
      --csv                  Output in CSV format
  -d, --dir-slash            Append a slash to directory names (default true)
      --dirs-only            Only list directories
      --files-only           Only list files
  -F, --format string        Output format - see  help for details (default &quot;p&quot;)
      --hash h               Use this hash when h is used in the format MD5|SHA-1|DropboxHash (default &quot;md5&quot;)
  -h, --help                 help for lsf
  -R, --recursive            Recurse into the listing
  -s, --separator string     Separator for the items in the format (default &quot;;&quot;)
  -t, --time-format string   Specify a custom time format, or &#39;max&#39; for max precision supported by remote (default: 2006-01-02 15:04:05)</code></pre>
<p>Options shared with other commands are described next. See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
<h3 id="filter-options-17">Filter Options</h3>
<p>Flags for filtering directory listings</p>
<pre><code>      --delete-excluded                     Delete files on dest excluded from sync
      --exclude stringArray                 Exclude files matching pattern
      --exclude-from stringArray            Read file exclude patterns from file (use - to read from stdin)
      --exclude-if-present stringArray      Exclude directories if filename is present
      --files-from stringArray              Read list of source-file names from file (use - to read from stdin)
      --files-from-raw stringArray          Read list of source-file names from file without any processing of lines (use - to read from stdin)
  -f, --filter stringArray                  Add a file filtering rule
      --filter-from stringArray             Read file filtering patterns from a file (use - to read from stdin)
      --ignore-case                         Ignore case in filters (case insensitive)
      --include stringArray                 Include files matching pattern
      --include-from stringArray            Read file include patterns from file (use - to read from stdin)
      --max-age Duration                    Only transfer files younger than this in s or suffix ms|s|m|h|d|w|M|y (default off)
      --max-depth int                       If set limits the recursion depth to this (default -1)
      --max-size SizeSuffix                 Only transfer files smaller than this in KiB or suffix B|K|M|G|T|P (default off)
      --metadata-exclude stringArray        Exclude metadatas matching pattern
      --metadata-exclude-from stringArray   Read metadata exclude patterns from file (use - to read from stdin)
      --metadata-filter stringArray         Add a metadata filtering rule
      --metadata-filter-from stringArray    Read metadata filtering patterns from a file (use - to read from stdin)
      --metadata-include stringArray        Include metadatas matching pattern
      --metadata-include-from stringArray   Read metadata include patterns from file (use - to read from stdin)
      --min-age Duration                    Only transfer files older than this in s or suffix ms|s|m|h|d|w|M|y (default off)
      --min-size SizeSuffix                 Only transfer files bigger than this in KiB or suffix B|K|M|G|T|P (default off)</code></pre>
<h3 id="listing-options-16">Listing Options</h3>
<p>Flags for listing directories</p>
<pre><code>      --default-time Time   Time to show if modtime is unknown for files and directories (default 2000-01-01T00:00:00Z)
      --fast-list           Use recursive list if available; uses more memory but fewer transactions</code></pre>
<h2 id="see-also-58">See Also</h2>
<ul>
<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
</ul>
<h1 id="rclone-lsjson">rclone lsjson</h1>
<p>List directories and objects in the path in JSON format.</p>
<h2 id="synopsis-51">Synopsis</h2>
<p>List directories and objects in the path in JSON format.</p>
<p>The output is an array of Items, where each Item looks like this:</p>
<pre><code>{
  &quot;Hashes&quot; : {
     &quot;SHA-1&quot; : &quot;f572d396fae9206628714fb2ce00f72e94f2258f&quot;,
     &quot;MD5&quot; : &quot;b1946ac92492d2347c6235b4d2611184&quot;,
     &quot;DropboxHash&quot; : &quot;ecb65bb98f9d905b70458986c39fcbad7715e5f2fcc3b1f07767d7c83e2438cc&quot;
  },
  &quot;ID&quot;: &quot;y2djkhiujf83u33&quot;,
  &quot;OrigID&quot;: &quot;UYOJVTUW00Q1RzTDA&quot;,
  &quot;IsBucket&quot; : false,
  &quot;IsDir&quot; : false,
  &quot;MimeType&quot; : &quot;application/octet-stream&quot;,
  &quot;ModTime&quot; : &quot;2017-05-31T16:15:57.034468261+01:00&quot;,
  &quot;Name&quot; : &quot;file.txt&quot;,
  &quot;Encrypted&quot; : &quot;v0qpsdq8anpci8n929v3uu9338&quot;,
  &quot;EncryptedPath&quot; : &quot;kja9098349023498/v0qpsdq8anpci8n929v3uu9338&quot;,
  &quot;Path&quot; : &quot;full/path/goes/here/file.txt&quot;,
  &quot;Size&quot; : 6,
  &quot;Tier&quot; : &quot;hot&quot;,
}</code></pre>
<p>The exact set of properties included depends on the backend:</p>
<ul>
<li>The property IsBucket will only be included for bucket-based remotes, and only for directories that are buckets. It will always be omitted when value is not true.</li>
<li>Properties Encrypted and EncryptedPath will only be included for encrypted remotes, and (as mentioned below) only if the <code>--encrypted</code> option is set.</li>
</ul>
<p>Different options may also affect which properties are included:</p>
<ul>
<li>If <code>--hash</code> is not specified, the Hashes property will be omitted. The types of hash can be specified with the <code>--hash-type</code> parameter (which may be repeated). If <code>--hash-type</code> is set then it implies <code>--hash</code>.</li>
<li>If <code>--no-modtime</code> is specified then ModTime will be blank. This can speed things up on remotes where reading the ModTime takes an extra request (e.g. s3, swift).</li>
<li>If <code>--no-mimetype</code> is specified then MimeType will be blank. This can speed things up on remotes where reading the MimeType takes an extra request (e.g. s3, swift).</li>
<li>If <code>--encrypted</code> is not specified the Encrypted and EncryptedPath properties will be omitted - even for encrypted remotes.</li>
<li>If <code>--metadata</code> is set then an additional Metadata property will be returned. This will have <a href="https://rclone.org/docs/#metadata">metadata</a> in rclone standard format as a JSON object.</li>
</ul>
<p>The default is to list directories and files/objects, but this can be changed with the following options:</p>
<ul>
<li>If <code>--dirs-only</code> is specified then directories will be returned only, no files/objects.</li>
<li>If <code>--files-only</code> is specified then files will be returned only, no directories.</li>
</ul>
<p>If <code>--stat</code> is set then the the output is not an array of items, but instead a single JSON blob will be returned about the item pointed to. This will return an error if the item isn't found, however on bucket based backends (like s3, gcs, b2, azureblob etc) if the item isn't found it will return an empty directory, as it isn't possible to tell empty directories from missing directories there.</p>
<p>The Path field will only show folders below the remote path being listed. If "remote:path" contains the file "subfolder/file.txt", the Path for "file.txt" will be "subfolder/file.txt", not "remote:path/subfolder/file.txt". When used without <code>--recursive</code> the Path will always be the same as Name.</p>
<p>The time is in RFC3339 format with up to nanosecond precision. The number of decimal digits in the seconds will depend on the precision that the remote can hold the times, so if times are accurate to the nearest millisecond (e.g. Google Drive) then 3 digits will always be shown ("2017-05-31T16:15:57.034+01:00") whereas if the times are accurate to the nearest second (Dropbox, Box, WebDav, etc.) no digits will be shown ("2017-05-31T16:15:57+01:00").</p>
<p>The whole output can be processed as a JSON blob, or alternatively it can be processed line by line as each item is written on individual lines (except with <code>--stat</code>).</p>
<p>Any of the filtering options can be applied to this command.</p>
<p>There are several related list commands</p>
<ul>
<li><code>ls</code> to list size and path of objects only</li>
<li><code>lsl</code> to list modification time, size and path of objects only</li>
<li><code>lsd</code> to list directories only</li>
<li><code>lsf</code> to list objects and directories in easy to parse format</li>
<li><code>lsjson</code> to list objects and directories in JSON format</li>
</ul>
<p><code>ls</code>,<code>lsl</code>,<code>lsd</code> are designed to be human-readable. <code>lsf</code> is designed to be human and machine-readable. <code>lsjson</code> is designed to be machine-readable.</p>
<p>Note that <code>ls</code> and <code>lsl</code> recurse by default - use <code>--max-depth 1</code> to stop the recursion.</p>
<p>The other list commands <code>lsd</code>,<code>lsf</code>,<code>lsjson</code> do not recurse by default - use <code>-R</code> to make them recurse.</p>
<p>Listing a nonexistent directory will produce an error except for remotes which can't have empty directories (e.g. s3, swift, or gcs - the bucket-based remotes).</p>
<pre><code>rclone lsjson remote:path [flags]</code></pre>
<h2 id="options-59">Options</h2>
<pre><code>      --dirs-only               Show only directories in the listing
      --encrypted               Show the encrypted names
      --files-only              Show only files in the listing
      --hash                    Include hashes in the output (may take longer)
      --hash-type stringArray   Show only this hash type (may be repeated)
  -h, --help                    help for lsjson
  -M, --metadata                Add metadata to the listing
      --no-mimetype             Don&#39;t read the mime type (can speed things up)
      --no-modtime              Don&#39;t read the modification time (can speed things up)
      --original                Show the ID of the underlying Object
  -R, --recursive               Recurse into the listing
      --stat                    Just return the info for the pointed to file</code></pre>
<p>Options shared with other commands are described next. See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
<h3 id="filter-options-18">Filter Options</h3>
<p>Flags for filtering directory listings</p>
<pre><code>      --delete-excluded                     Delete files on dest excluded from sync
      --exclude stringArray                 Exclude files matching pattern
      --exclude-from stringArray            Read file exclude patterns from file (use - to read from stdin)
      --exclude-if-present stringArray      Exclude directories if filename is present
      --files-from stringArray              Read list of source-file names from file (use - to read from stdin)
      --files-from-raw stringArray          Read list of source-file names from file without any processing of lines (use - to read from stdin)
  -f, --filter stringArray                  Add a file filtering rule
      --filter-from stringArray             Read file filtering patterns from a file (use - to read from stdin)
      --ignore-case                         Ignore case in filters (case insensitive)
      --include stringArray                 Include files matching pattern
      --include-from stringArray            Read file include patterns from file (use - to read from stdin)
      --max-age Duration                    Only transfer files younger than this in s or suffix ms|s|m|h|d|w|M|y (default off)
      --max-depth int                       If set limits the recursion depth to this (default -1)
      --max-size SizeSuffix                 Only transfer files smaller than this in KiB or suffix B|K|M|G|T|P (default off)
      --metadata-exclude stringArray        Exclude metadatas matching pattern
      --metadata-exclude-from stringArray   Read metadata exclude patterns from file (use - to read from stdin)
      --metadata-filter stringArray         Add a metadata filtering rule
      --metadata-filter-from stringArray    Read metadata filtering patterns from a file (use - to read from stdin)
      --metadata-include stringArray        Include metadatas matching pattern
      --metadata-include-from stringArray   Read metadata include patterns from file (use - to read from stdin)
      --min-age Duration                    Only transfer files older than this in s or suffix ms|s|m|h|d|w|M|y (default off)
      --min-size SizeSuffix                 Only transfer files bigger than this in KiB or suffix B|K|M|G|T|P (default off)</code></pre>
<h3 id="listing-options-17">Listing Options</h3>
<p>Flags for listing directories</p>
<pre><code>      --default-time Time   Time to show if modtime is unknown for files and directories (default 2000-01-01T00:00:00Z)
      --fast-list           Use recursive list if available; uses more memory but fewer transactions</code></pre>
<h2 id="see-also-59">See Also</h2>
<ul>
<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
</ul>
<h1 id="rclone-mount">rclone mount</h1>
<p>Mount the remote as file system on a mountpoint.</p>
<h2 id="synopsis-52">Synopsis</h2>
<p>Rclone mount allows Linux, FreeBSD, macOS and Windows to mount any of Rclone's cloud storage systems as a file system with FUSE.</p>
<p>First set up your remote using <code>rclone config</code>. Check it works with <code>rclone ls</code> etc.</p>
<p>On Linux and macOS, you can run mount in either foreground or background (aka daemon) mode. Mount runs in foreground mode by default. Use the <code>--daemon</code> flag to force background mode. On Windows you can run mount in foreground only, the flag is ignored.</p>
<p>In background mode rclone acts as a generic Unix mount program: the main program starts, spawns background rclone process to setup and maintain the mount, waits until success or timeout and exits with appropriate code (killing the child process if it fails).</p>
<p>On Linux/macOS/FreeBSD start the mount like this, where <code>/path/to/local/mount</code> is an <strong>empty</strong> <strong>existing</strong> directory:</p>
<pre><code>rclone mount remote:path/to/files /path/to/local/mount</code></pre>
<p>On Windows you can start a mount in different ways. See <a href="#mounting-modes-on-windows">below</a> for details. If foreground mount is used interactively from a console window, rclone will serve the mount and occupy the console so another window should be used to work with the mount until rclone is interrupted e.g. by pressing Ctrl-C.</p>
<p>The following examples will mount to an automatically assigned drive, to specific drive letter <code>X:</code>, to path <code>C:\path\parent\mount</code> (where parent directory or drive must exist, and mount must <strong>not</strong> exist, and is not supported when <a href="#mounting-modes-on-windows">mounting as a network drive</a>), and the last example will mount as network share <code>\\cloud\remote</code> and map it to an automatically assigned drive:</p>
<pre><code>rclone mount remote:path/to/files *
rclone mount remote:path/to/files X:
rclone mount remote:path/to/files C:\path\parent\mount
rclone mount remote:path/to/files \\cloud\remote</code></pre>
<p>When the program ends while in foreground mode, either via Ctrl+C or receiving a SIGINT or SIGTERM signal, the mount should be automatically stopped.</p>
<p>When running in background mode the user will have to stop the mount manually:</p>
<pre><code># Linux
fusermount -u /path/to/local/mount
#... or on some systems
fusermount3 -u /path/to/local/mount
# OS X or Linux when using nfsmount
umount /path/to/local/mount</code></pre>
<p>The umount operation can fail, for example when the mountpoint is busy. When that happens, it is the user's responsibility to stop the mount manually.</p>
<p>The size of the mounted file system will be set according to information retrieved from the remote, the same as returned by the <a href="https://rclone.org/commands/rclone_about/">rclone about</a> command. Remotes with unlimited storage may report the used size only, then an additional 1 PiB of free space is assumed. If the remote does not <a href="https://rclone.org/overview/#optional-features">support</a> the about feature at all, then 1 PiB is set as both the total and the free size.</p>
<h2 id="installing-on-windows">Installing on Windows</h2>
<p>To run rclone mount on Windows, you will need to download and install <a href="http://www.secfs.net/winfsp/">WinFsp</a>.</p>
<p><a href="https://github.com/winfsp/winfsp">WinFsp</a> is an open-source Windows File System Proxy which makes it easy to write user space file systems for Windows. It provides a FUSE emulation layer which rclone uses combination with <a href="https://github.com/winfsp/cgofuse">cgofuse</a>. Both of these packages are by Bill Zissimopoulos who was very helpful during the implementation of rclone mount for Windows.</p>
<h3 id="mounting-modes-on-windows">Mounting modes on windows</h3>
<p>Unlike other operating systems, Microsoft Windows provides a different filesystem type for network and fixed drives. It optimises access on the assumption fixed disk drives are fast and reliable, while network drives have relatively high latency and less reliability. Some settings can also be differentiated between the two types, for example that Windows Explorer should just display icons and not create preview thumbnails for image and video files on network drives.</p>
<p>In most cases, rclone will mount the remote as a normal, fixed disk drive by default. However, you can also choose to mount it as a remote network drive, often described as a network share. If you mount an rclone remote using the default, fixed drive mode and experience unexpected program errors, freezes or other issues, consider mounting as a network drive instead.</p>
<p>When mounting as a fixed disk drive you can either mount to an unused drive letter, or to a path representing a <strong>nonexistent</strong> subdirectory of an <strong>existing</strong> parent directory or drive. Using the special value <code>*</code> will tell rclone to automatically assign the next available drive letter, starting with Z: and moving backward. Examples:</p>
<pre><code>rclone mount remote:path/to/files *
rclone mount remote:path/to/files X:
rclone mount remote:path/to/files C:\path\parent\mount
rclone mount remote:path/to/files X:</code></pre>
<p>Option <code>--volname</code> can be used to set a custom volume name for the mounted file system. The default is to use the remote name and path.</p>
<p>To mount as network drive, you can add option <code>--network-mode</code> to your mount command. Mounting to a directory path is not supported in this mode, it is a limitation Windows imposes on junctions, so the remote must always be mounted to a drive letter.</p>
<pre><code>rclone mount remote:path/to/files X: --network-mode</code></pre>
<p>A volume name specified with <code>--volname</code> will be used to create the network share path. A complete UNC path, such as <code>\\cloud\remote</code>, optionally with path <code>\\cloud\remote\madeup\path</code>, will be used as is. Any other string will be used as the share part, after a default prefix <code>\\server\</code>. If no volume name is specified then <code>\\server\share</code> will be used. You must make sure the volume name is unique when you are mounting more than one drive, or else the mount command will fail. The share name will treated as the volume label for the mapped drive, shown in Windows Explorer etc, while the complete <code>\\server\share</code> will be reported as the remote UNC path by <code>net use</code> etc, just like a normal network drive mapping.</p>
<p>If you specify a full network share UNC path with <code>--volname</code>, this will implicitly set the <code>--network-mode</code> option, so the following two examples have same result:</p>
<pre><code>rclone mount remote:path/to/files X: --network-mode
rclone mount remote:path/to/files X: --volname \\server\share</code></pre>
<p>You may also specify the network share UNC path as the mountpoint itself. Then rclone will automatically assign a drive letter, same as with <code>*</code> and use that as mountpoint, and instead use the UNC path specified as the volume name, as if it were specified with the <code>--volname</code> option. This will also implicitly set the <code>--network-mode</code> option. This means the following two examples have same result:</p>
<pre><code>rclone mount remote:path/to/files \\cloud\remote
rclone mount remote:path/to/files * --volname \\cloud\remote</code></pre>
<p>There is yet another way to enable network mode, and to set the share path, and that is to pass the "native" libfuse/WinFsp option directly: <code>--fuse-flag --VolumePrefix=\server\share</code>. Note that the path must be with just a single backslash prefix in this case.</p>
<p><em>Note:</em> In previous versions of rclone this was the only supported method.</p>
<p><a href="https://en.wikipedia.org/wiki/Drive_mapping">Read more about drive mapping</a></p>
<p>See also <a href="#limitations">Limitations</a> section below.</p>
<h3 id="windows-filesystem-permissions">Windows filesystem permissions</h3>
<p>The FUSE emulation layer on Windows must convert between the POSIX-based permission model used in FUSE, and the permission model used in Windows, based on access-control lists (ACL).</p>
<p>The mounted filesystem will normally get three entries in its access-control list (ACL), representing permissions for the POSIX permission scopes: Owner, group and others. By default, the owner and group will be taken from the current user, and the built-in group "Everyone" will be used to represent others. The user/group can be customized with FUSE options "UserName" and "GroupName", e.g. <code>-o UserName=user123 -o GroupName="Authenticated Users"</code>. The permissions on each entry will be set according to <a href="#options">options</a> <code>--dir-perms</code> and <code>--file-perms</code>, which takes a value in traditional Unix <a href="https://en.wikipedia.org/wiki/File-system_permissions#Numeric_notation">numeric notation</a>.</p>
<p>The default permissions corresponds to <code>--file-perms 0666 --dir-perms 0777</code>, i.e. read and write permissions to everyone. This means you will not be able to start any programs from the mount. To be able to do that you must add execute permissions, e.g. <code>--file-perms 0777 --dir-perms 0777</code> to add it to everyone. If the program needs to write files, chances are you will have to enable <a href="#vfs-file-caching">VFS File Caching</a> as well (see also <a href="#limitations">limitations</a>). Note that the default write permission have some restrictions for accounts other than the owner, specifically it lacks the "write extended attributes", as explained next.</p>
<p>The mapping of permissions is not always trivial, and the result you see in Windows Explorer may not be exactly like you expected. For example, when setting a value that includes write access for the group or others scope, this will be mapped to individual permissions "write attributes", "write data" and "append data", but not "write extended attributes". Windows will then show this as basic permission "Special" instead of "Write", because "Write" also covers the "write extended attributes" permission. When setting digit 0 for group or others, to indicate no permissions, they will still get individual permissions "read attributes", "read extended attributes" and "read permissions". This is done for compatibility reasons, e.g. to allow users without additional permissions to be able to read basic metadata about files like in Unix.</p>
<p>WinFsp 2021 (version 1.9) introduced a new FUSE option "FileSecurity", that allows the complete specification of file security descriptors using <a href="https://docs.microsoft.com/en-us/windows/win32/secauthz/security-descriptor-string-format">SDDL</a>. With this you get detailed control of the resulting permissions, compared to use of the POSIX permissions described above, and no additional permissions will be added automatically for compatibility with Unix. Some example use cases will following.</p>
<p>If you set POSIX permissions for only allowing access to the owner, using <code>--file-perms 0600 --dir-perms 0700</code>, the user group and the built-in "Everyone" group will still be given some special permissions, as described above. Some programs may then (incorrectly) interpret this as the file being accessible by everyone, for example an SSH client may warn about "unprotected private key file". You can work around this by specifying <code>-o FileSecurity="D:P(A;;FA;;;OW)"</code>, which sets file all access (FA) to the owner (OW), and nothing else.</p>
<p>When setting write permissions then, except for the owner, this does not include the "write extended attributes" permission, as mentioned above. This may prevent applications from writing to files, giving permission denied error instead. To set working write permissions for the built-in "Everyone" group, similar to what it gets by default but with the addition of the "write extended attributes", you can specify <code>-o FileSecurity="D:P(A;;FRFW;;;WD)"</code>, which sets file read (FR) and file write (FW) to everyone (WD). If file execute (FX) is also needed, then change to <code>-o FileSecurity="D:P(A;;FRFWFX;;;WD)"</code>, or set file all access (FA) to get full access permissions, including delete, with <code>-o FileSecurity="D:P(A;;FA;;;WD)"</code>.</p>
<h3 id="windows-caveats">Windows caveats</h3>
<p>Drives created as Administrator are not visible to other accounts, not even an account that was elevated to Administrator with the User Account Control (UAC) feature. A result of this is that if you mount to a drive letter from a Command Prompt run as Administrator, and then try to access the same drive from Windows Explorer (which does not run as Administrator), you will not be able to see the mounted drive.</p>
<p>If you don't need to access the drive from applications running with administrative privileges, the easiest way around this is to always create the mount from a non-elevated command prompt.</p>
<p>To make mapped drives available to the user account that created them regardless if elevated or not, there is a special Windows setting called <a href="https://docs.microsoft.com/en-us/troubleshoot/windows-client/networking/mapped-drives-not-available-from-elevated-command#detail-to-configure-the-enablelinkedconnections-registry-entry">linked connections</a> that can be enabled.</p>
<p>It is also possible to make a drive mount available to everyone on the system, by running the process creating it as the built-in SYSTEM account. There are several ways to do this: One is to use the command-line utility <a href="https://docs.microsoft.com/en-us/sysinternals/downloads/psexec">PsExec</a>, from Microsoft's Sysinternals suite, which has option <code>-s</code> to start processes as the SYSTEM account. Another alternative is to run the mount command from a Windows Scheduled Task, or a Windows Service, configured to run as the SYSTEM account. A third alternative is to use the <a href="https://github.com/winfsp/winfsp/wiki/WinFsp-Service-Architecture">WinFsp.Launcher infrastructure</a>). Read more in the <a href="https://rclone.org/install/">install documentation</a>. Note that when running rclone as another user, it will not use the configuration file from your profile unless you tell it to with the <a href="https://rclone.org/docs/#config-config-file"><code>--config</code></a> option. Note also that it is now the SYSTEM account that will have the owner permissions, and other accounts will have permissions according to the group or others scopes. As mentioned above, these will then not get the "write extended attributes" permission, and this may prevent writing to files. You can work around this with the FileSecurity option, see example above.</p>
<p>Note that mapping to a directory path, instead of a drive letter, does not suffer from the same limitations.</p>
<h2 id="mounting-on-macos">Mounting on macOS</h2>
<p>Mounting on macOS can be done either via <a href="https://rclone.org/commands/rclone_serve_nfs/">built-in NFS server</a>, <a href="https://osxfuse.github.io/">macFUSE</a> (also known as osxfuse) or <a href="https://www.fuse-t.org/">FUSE-T</a>. macFUSE is a traditional FUSE driver utilizing a macOS kernel extension (kext). FUSE-T is an alternative FUSE system which "mounts" via an NFSv4 local server.</p>
<h4 id="unicode-normalization">Unicode Normalization</h4>
<p>It is highly recommended to keep the default of <code>--no-unicode-normalization=false</code> for all <code>mount</code> and <code>serve</code> commands on macOS. For details, see <a href="https://rclone.org/commands/rclone_mount/#vfs-case-sensitivity">vfs-case-sensitivity</a>.</p>
<h3 id="nfs-mount">NFS mount</h3>
<p>This method spins up an NFS server using <a href="https://rclone.org/commands/rclone_serve_nfs/">serve nfs</a> command and mounts it to the specified mountpoint. If you run this in background mode using |--daemon|, you will need to send SIGTERM signal to the rclone process using |kill| command to stop the mount.</p>
<p>Note that <code>--nfs-cache-handle-limit</code> controls the maximum number of cached file handles stored by the <code>nfsmount</code> caching handler. This should not be set too low or you may experience errors when trying to access files. The default is 1000000, but consider lowering this limit if the server's system resource usage causes problems.</p>
<h3 id="macfuse-notes">macFUSE Notes</h3>
<p>If installing macFUSE using <a href="https://github.com/osxfuse/osxfuse/releases">dmg packages</a> from the website, rclone will locate the macFUSE libraries without any further intervention. If however, macFUSE is installed using the <a href="https://www.macports.org/">macports</a> package manager, the following addition steps are required.</p>
<pre><code>sudo mkdir /usr/local/lib
cd /usr/local/lib
sudo ln -s /opt/local/lib/libfuse.2.dylib</code></pre>
<h3 id="fuse-t-limitations-caveats-and-notes">FUSE-T Limitations, Caveats, and Notes</h3>
<p>There are some limitations, caveats, and notes about how it works. These are current as of FUSE-T version 1.0.14.</p>
<h4 id="modtime-update-on-read">ModTime update on read</h4>
<p>As per the <a href="https://github.com/macos-fuse-t/fuse-t/wiki#caveats">FUSE-T wiki</a>:</p>
<blockquote>
<p>File access and modification times cannot be set separately as it seems to be an issue with the NFS client which always modifies both. Can be reproduced with 'touch -m' and 'touch -a' commands</p>
</blockquote>
<p>This means that viewing files with various tools, notably macOS Finder, will cause rlcone to update the modification time of the file. This may make rclone upload a full new copy of the file.</p>
<h4 id="read-only-mounts">Read Only mounts</h4>
<p>When mounting with <code>--read-only</code>, attempts to write to files will fail <em>silently</em> as opposed to with a clear warning as in macFUSE.</p>
<h2 id="limitations">Limitations</h2>
<p>Without the use of <code>--vfs-cache-mode</code> this can only write files sequentially, it can only seek when reading. This means that many applications won't work with their files on an rclone mount without <code>--vfs-cache-mode writes</code> or <code>--vfs-cache-mode full</code>. See the <a href="#vfs-file-caching">VFS File Caching</a> section for more info. When using NFS mount on macOS, if you don't specify |--vfs-cache-mode| the mount point will be read-only.</p>
<p>The bucket-based remotes (e.g. Swift, S3, Google Compute Storage, B2) do not support the concept of empty directories, so empty directories will have a tendency to disappear once they fall out of the directory cache.</p>
<p>When <code>rclone mount</code> is invoked on Unix with <code>--daemon</code> flag, the main rclone program will wait for the background mount to become ready or until the timeout specified by the <code>--daemon-wait</code> flag. On Linux it can check mount status using ProcFS so the flag in fact sets <strong>maximum</strong> time to wait, while the real wait can be less. On macOS / BSD the time to wait is constant and the check is performed only at the end. We advise you to set wait time on macOS reasonably.</p>
<p>Only supported on Linux, FreeBSD, OS X and Windows at the moment.</p>
<h2 id="rclone-mount-vs-rclone-synccopy">rclone mount vs rclone sync/copy</h2>
<p>File systems expect things to be 100% reliable, whereas cloud storage systems are a long way from 100% reliable. The rclone sync/copy commands cope with this with lots of retries. However rclone mount can't use retries in the same way without making local copies of the uploads. Look at the <a href="#vfs-file-caching">VFS File Caching</a> for solutions to make mount more reliable.</p>
<h2 id="attribute-caching">Attribute caching</h2>
<p>You can use the flag <code>--attr-timeout</code> to set the time the kernel caches the attributes (size, modification time, etc.) for directory entries.</p>
<p>The default is <code>1s</code> which caches files just long enough to avoid too many callbacks to rclone from the kernel.</p>
<p>In theory 0s should be the correct value for filesystems which can change outside the control of the kernel. However this causes quite a few problems such as <a href="https://github.com/rclone/rclone/issues/2157">rclone using too much memory</a>, <a href="https://forum.rclone.org/t/rclone-1-39-vs-1-40-mount-issue/5112">rclone not serving files to samba</a> and <a href="https://github.com/rclone/rclone/issues/2095#issuecomment-371141147">excessive time listing directories</a>.</p>
<p>The kernel can cache the info about a file for the time given by <code>--attr-timeout</code>. You may see corruption if the remote file changes length during this window. It will show up as either a truncated file or a file with garbage on the end. With <code>--attr-timeout 1s</code> this is very unlikely but not impossible. The higher you set <code>--attr-timeout</code> the more likely it is. The default setting of "1s" is the lowest setting which mitigates the problems above.</p>
<p>If you set it higher (<code>10s</code> or <code>1m</code> say) then the kernel will call back to rclone less often making it more efficient, however there is more chance of the corruption issue above.</p>
<p>If files don't change on the remote outside of the control of rclone then there is no chance of corruption.</p>
<p>This is the same as setting the attr_timeout option in mount.fuse.</p>
<h2 id="filters">Filters</h2>
<p>Note that all the rclone filters can be used to select a subset of the files to be visible in the mount.</p>
<h2 id="systemd">systemd</h2>
<p>When running rclone mount as a systemd service, it is possible to use Type=notify. In this case the service will enter the started state after the mountpoint has been successfully set up. Units having the rclone mount service specified as a requirement will see all files and folders immediately in this mode.</p>
<p>Note that systemd runs mount units without any environment variables including <code>PATH</code> or <code>HOME</code>. This means that tilde (<code>~</code>) expansion will not work and you should provide <code>--config</code> and <code>--cache-dir</code> explicitly as absolute paths via rclone arguments. Since mounting requires the <code>fusermount</code> or <code>fusermount3</code> program, rclone will use the fallback PATH of <code>/bin:/usr/bin</code> in this scenario. Please ensure that <code>fusermount</code>/<code>fusermount3</code> is present on this PATH.</p>
<h2 id="rclone-as-unix-mount-helper">Rclone as Unix mount helper</h2>
<p>The core Unix program <code>/bin/mount</code> normally takes the <code>-t FSTYPE</code> argument then runs the <code>/sbin/mount.FSTYPE</code> helper program passing it mount options as <code>-o key=val,...</code> or <code>--opt=...</code>. Automount (classic or systemd) behaves in a similar way.</p>
<p>rclone by default expects GNU-style flags <code>--key val</code>. To run it as a mount helper you should symlink rclone binary to <code>/sbin/mount.rclone</code> and optionally <code>/usr/bin/rclonefs</code>, e.g. <code>ln -s /usr/bin/rclone /sbin/mount.rclone</code>. rclone will detect it and translate command-line arguments appropriately.</p>
<p>Now you can run classic mounts like this:</p>
<pre><code>mount sftp1:subdir /mnt/data -t rclone -o vfs_cache_mode=writes,sftp_key_file=/path/to/pem</code></pre>
<p>or create systemd mount units:</p>
<pre><code># /etc/systemd/system/mnt-data.mount
[Unit]
Description=Mount for /mnt/data
[Mount]
Type=rclone
What=sftp1:subdir
Where=/mnt/data
Options=rw,_netdev,allow_other,args2env,vfs-cache-mode=writes,config=/etc/rclone.conf,cache-dir=/var/rclone</code></pre>
<p>optionally accompanied by systemd automount unit</p>
<pre><code># /etc/systemd/system/mnt-data.automount
[Unit]
Description=AutoMount for /mnt/data
[Automount]
Where=/mnt/data
TimeoutIdleSec=600
[Install]
WantedBy=multi-user.target</code></pre>
<p>or add in <code>/etc/fstab</code> a line like</p>
<pre><code>sftp1:subdir /mnt/data rclone rw,noauto,nofail,_netdev,x-systemd.automount,args2env,vfs_cache_mode=writes,config=/etc/rclone.conf,cache_dir=/var/cache/rclone 0 0</code></pre>
<p>or use classic Automountd. Remember to provide explicit <code>config=...,cache-dir=...</code> as a workaround for mount units being run without <code>HOME</code>.</p>
<p>Rclone in the mount helper mode will split <code>-o</code> argument(s) by comma, replace <code>_</code> by <code>-</code> and prepend <code>--</code> to get the command-line flags. Options containing commas or spaces can be wrapped in single or double quotes. Any inner quotes inside outer quotes of the same type should be doubled.</p>
<p>Mount option syntax includes a few extra options treated specially:</p>
<ul>
<li><code>env.NAME=VALUE</code> will set an environment variable for the mount process. This helps with Automountd and Systemd.mount which don't allow setting custom environment for mount helpers. Typically you will use <code>env.HTTPS_PROXY=proxy.host:3128</code> or <code>env.HOME=/root</code></li>
<li><code>command=cmount</code> can be used to run <code>cmount</code> or any other rclone command rather than the default <code>mount</code>.</li>
<li><code>args2env</code> will pass mount options to the mount helper running in background via environment variables instead of command line arguments. This allows to hide secrets from such commands as <code>ps</code> or <code>pgrep</code>.</li>
<li><code>vv...</code> will be transformed into appropriate <code>--verbose=N</code></li>
<li>standard mount options like <code>x-systemd.automount</code>, <code>_netdev</code>, <code>nosuid</code> and alike are intended only for Automountd and ignored by rclone.</li>
</ul>
<h2 id="vfs---virtual-file-system">VFS - Virtual File System</h2>
<p>This command uses the VFS layer. This adapts the cloud storage objects that rclone uses into something which looks much more like a disk filing system.</p>
<p>Cloud storage objects have lots of properties which aren't like disk files - you can't extend them or write to the middle of them, so the VFS layer has to deal with that. Because there is no one right way of doing this there are various options explained below.</p>
<p>The VFS layer also implements a directory cache - this caches info about files and directories (but not the data) in memory.</p>
<h2 id="vfs-directory-cache">VFS Directory Cache</h2>
<p>Using the <code>--dir-cache-time</code> flag, you can control how long a directory should be considered up to date and not refreshed from the backend. Changes made through the VFS will appear immediately or invalidate the cache.</p>
<pre><code>--dir-cache-time duration   Time to cache directory entries for (default 5m0s)
--poll-interval duration    Time to wait between polling for changes. Must be smaller than dir-cache-time. Only on supported remotes. Set to 0 to disable (default 1m0s)</code></pre>
<p>However, changes made directly on the cloud storage by the web interface or a different copy of rclone will only be picked up once the directory cache expires if the backend configured does not support polling for changes. If the backend supports polling, changes will be picked up within the polling interval.</p>
<p>You can send a <code>SIGHUP</code> signal to rclone for it to flush all directory caches, regardless of how old they are. Assuming only one rclone instance is running, you can reset the cache like this:</p>
<pre><code>kill -SIGHUP $(pidof rclone)</code></pre>
<p>If you configure rclone with a <a href="/rc">remote control</a> then you can use rclone rc to flush the whole directory cache:</p>
<pre><code>rclone rc vfs/forget</code></pre>
<p>Or individual files or directories:</p>
<pre><code>rclone rc vfs/forget file=path/to/file dir=path/to/dir</code></pre>
<h2 id="vfs-file-buffering">VFS File Buffering</h2>
<p>The <code>--buffer-size</code> flag determines the amount of memory, that will be used to buffer data in advance.</p>
<p>Each open file will try to keep the specified amount of data in memory at all times. The buffered data is bound to one open file and won't be shared.</p>
<p>This flag is a upper limit for the used memory per open file. The buffer will only use memory for data that is downloaded but not not yet read. If the buffer is empty, only a small amount of memory will be used.</p>
<p>The maximum memory used by rclone for buffering can be up to <code>--buffer-size * open files</code>.</p>
<h2 id="vfs-file-caching">VFS File Caching</h2>
<p>These flags control the VFS file caching options. File caching is necessary to make the VFS layer appear compatible with a normal file system. It can be disabled at the cost of some compatibility.</p>
<p>For example you'll need to enable VFS caching if you want to read and write simultaneously to a file. See below for more details.</p>
<p>Note that the VFS cache is separate from the cache backend and you may find that you need one or the other or both.</p>
<pre><code>--cache-dir string                     Directory rclone will use for caching.
--vfs-cache-mode CacheMode             Cache mode off|minimal|writes|full (default off)
--vfs-cache-max-age duration           Max time since last access of objects in the cache (default 1h0m0s)
--vfs-cache-max-size SizeSuffix        Max total size of objects in the cache (default off)
--vfs-cache-min-free-space SizeSuffix  Target minimum free space on the disk containing the cache (default off)
--vfs-cache-poll-interval duration     Interval to poll the cache for stale objects (default 1m0s)
--vfs-write-back duration              Time to writeback files after last use when using cache (default 5s)</code></pre>
<p>If run with <code>-vv</code> rclone will print the location of the file cache. The files are stored in the user cache file area which is OS dependent but can be controlled with <code>--cache-dir</code> or setting the appropriate environment variable.</p>
<p>The cache has 4 different modes selected by <code>--vfs-cache-mode</code>. The higher the cache mode the more compatible rclone becomes at the cost of using disk space.</p>
<p>Note that files are written back to the remote only when they are closed and if they haven't been accessed for <code>--vfs-write-back</code> seconds. If rclone is quit or dies with files that haven't been uploaded, these will be uploaded next time rclone is run with the same flags.</p>
<p>If using <code>--vfs-cache-max-size</code> or <code>--vfs-cache-min-free-size</code> note that the cache may exceed these quotas for two reasons. Firstly because it is only checked every <code>--vfs-cache-poll-interval</code>. Secondly because open files cannot be evicted from the cache. When <code>--vfs-cache-max-size</code> or <code>--vfs-cache-min-free-size</code> is exceeded, rclone will attempt to evict the least accessed files from the cache first. rclone will start with files that haven't been accessed for the longest. This cache flushing strategy is efficient and more relevant files are likely to remain cached.</p>
<p>The <code>--vfs-cache-max-age</code> will evict files from the cache after the set time since last access has passed. The default value of 1 hour will start evicting files from cache that haven't been accessed for 1 hour. When a cached file is accessed the 1 hour timer is reset to 0 and will wait for 1 more hour before evicting. Specify the time with standard notation, s, m, h, d, w .</p>
<p>You <strong>should not</strong> run two copies of rclone using the same VFS cache with the same or overlapping remotes if using <code>--vfs-cache-mode &gt; off</code>. This can potentially cause data corruption if you do. You can work around this by giving each rclone its own cache hierarchy with <code>--cache-dir</code>. You don't need to worry about this if the remotes in use don't overlap.</p>
<h3 id="vfs-cache-mode-off">--vfs-cache-mode off</h3>
<p>In this mode (the default) the cache will read directly from the remote and write directly to the remote without caching anything on disk.</p>
<p>This will mean some operations are not possible</p>
<ul>
<li>Files can't be opened for both read AND write</li>
<li>Files opened for write can't be seeked</li>
<li>Existing files opened for write must have O_TRUNC set</li>
<li>Files open for read with O_TRUNC will be opened write only</li>
<li>Files open for write only will behave as if O_TRUNC was supplied</li>
<li>Open modes O_APPEND, O_TRUNC are ignored</li>
<li>If an upload fails it can't be retried</li>
</ul>
<h3 id="vfs-cache-mode-minimal">--vfs-cache-mode minimal</h3>
<p>This is very similar to "off" except that files opened for read AND write will be buffered to disk. This means that files opened for write will be a lot more compatible, but uses the minimal disk space.</p>
<p>These operations are not possible</p>
<ul>
<li>Files opened for write only can't be seeked</li>
<li>Existing files opened for write must have O_TRUNC set</li>
<li>Files opened for write only will ignore O_APPEND, O_TRUNC</li>
<li>If an upload fails it can't be retried</li>
</ul>
<h3 id="vfs-cache-mode-writes">--vfs-cache-mode writes</h3>
<p>In this mode files opened for read only are still read directly from the remote, write only and read/write files are buffered to disk first.</p>
<p>This mode should support all normal file system operations.</p>
<p>If an upload fails it will be retried at exponentially increasing intervals up to 1 minute.</p>
<h3 id="vfs-cache-mode-full">--vfs-cache-mode full</h3>
<p>In this mode all reads and writes are buffered to and from disk. When data is read from the remote this is buffered to disk as well.</p>
<p>In this mode the files in the cache will be sparse files and rclone will keep track of which bits of the files it has downloaded.</p>
<p>So if an application only reads the starts of each file, then rclone will only buffer the start of the file. These files will appear to be their full size in the cache, but they will be sparse files with only the data that has been downloaded present in them.</p>
<p>This mode should support all normal file system operations and is otherwise identical to <code>--vfs-cache-mode</code> writes.</p>
<p>When reading a file rclone will read <code>--buffer-size</code> plus <code>--vfs-read-ahead</code> bytes ahead. The <code>--buffer-size</code> is buffered in memory whereas the <code>--vfs-read-ahead</code> is buffered on disk.</p>
<p>When using this mode it is recommended that <code>--buffer-size</code> is not set too large and <code>--vfs-read-ahead</code> is set large if required.</p>
<p><strong>IMPORTANT</strong> not all file systems support sparse files. In particular FAT/exFAT do not. Rclone will perform very badly if the cache directory is on a filesystem which doesn't support sparse files and it will log an ERROR message if one is detected.</p>
<h3 id="fingerprinting">Fingerprinting</h3>
<p>Various parts of the VFS use fingerprinting to see if a local file copy has changed relative to a remote file. Fingerprints are made from:</p>
<ul>
<li>size</li>
<li>modification time</li>
<li>hash</li>
</ul>
<p>where available on an object.</p>
<p>On some backends some of these attributes are slow to read (they take an extra API call per object, or extra work per object).</p>
<p>For example <code>hash</code> is slow with the <code>local</code> and <code>sftp</code> backends as they have to read the entire file and hash it, and <code>modtime</code> is slow with the <code>s3</code>, <code>swift</code>, <code>ftp</code> and <code>qinqstor</code> backends because they need to do an extra API call to fetch it.</p>
<p>If you use the <code>--vfs-fast-fingerprint</code> flag then rclone will not include the slow operations in the fingerprint. This makes the fingerprinting less accurate but much faster and will improve the opening time of cached files.</p>
<p>If you are running a vfs cache over <code>local</code>, <code>s3</code> or <code>swift</code> backends then using this flag is recommended.</p>
<p>Note that if you change the value of this flag, the fingerprints of the files in the cache may be invalidated and the files will need to be downloaded again.</p>
<h2 id="vfs-chunked-reading">VFS Chunked Reading</h2>
<p>When rclone reads files from a remote it reads them in chunks. This means that rather than requesting the whole file rclone reads the chunk specified. This can reduce the used download quota for some remotes by requesting only chunks from the remote that are actually read, at the cost of an increased number of requests.</p>
<p>These flags control the chunking:</p>
<pre><code>--vfs-read-chunk-size SizeSuffix        Read the source objects in chunks (default 128M)
--vfs-read-chunk-size-limit SizeSuffix  Max chunk doubling size (default off)
--vfs-read-chunk-streams int            The number of parallel streams to read at once</code></pre>
<p>The chunking behaves differently depending on the <code>--vfs-read-chunk-streams</code> parameter.</p>
<h3 id="vfs-read-chunk-streams-0"><code>--vfs-read-chunk-streams</code> == 0</h3>
<p>Rclone will start reading a chunk of size <code>--vfs-read-chunk-size</code>, and then double the size for each read. When <code>--vfs-read-chunk-size-limit</code> is specified, and greater than <code>--vfs-read-chunk-size</code>, the chunk size for each open file will get doubled only until the specified value is reached. If the value is "off", which is the default, the limit is disabled and the chunk size will grow indefinitely.</p>
<p>With <code>--vfs-read-chunk-size 100M</code> and <code>--vfs-read-chunk-size-limit 0</code> the following parts will be downloaded: 0-100M, 100M-200M, 200M-300M, 300M-400M and so on. When <code>--vfs-read-chunk-size-limit 500M</code> is specified, the result would be 0-100M, 100M-300M, 300M-700M, 700M-1200M, 1200M-1700M and so on.</p>
<p>Setting <code>--vfs-read-chunk-size</code> to <code>0</code> or "off" disables chunked reading.</p>
<p>The chunks will not be buffered in memory.</p>
<h3 id="vfs-read-chunk-streams-0-1"><code>--vfs-read-chunk-streams</code> &gt; 0</h3>
<p>Rclone reads <code>--vfs-read-chunk-streams</code> chunks of size <code>--vfs-read-chunk-size</code> concurrently. The size for each read will stay constant.</p>
<p>This improves performance performance massively on high latency links or very high bandwidth links to high performance object stores.</p>
<p>Some experimentation will be needed to find the optimum values of <code>--vfs-read-chunk-size</code> and <code>--vfs-read-chunk-streams</code> as these will depend on the backend in use and the latency to the backend.</p>
<p>For high performance object stores (eg AWS S3) a reasonable place to start might be <code>--vfs-read-chunk-streams 16</code> and <code>--vfs-read-chunk-size 4M</code>. In testing with AWS S3 the performance scaled roughly as the <code>--vfs-read-chunk-streams</code> setting.</p>
<p>Similar settings should work for high latency links, but depending on the latency they may need more <code>--vfs-read-chunk-streams</code> in order to get the throughput.</p>
<h2 id="vfs-performance">VFS Performance</h2>
<p>These flags may be used to enable/disable features of the VFS for performance or other reasons. See also the <a href="#vfs-chunked-reading">chunked reading</a> feature.</p>
<p>In particular S3 and Swift benefit hugely from the <code>--no-modtime</code> flag (or use <code>--use-server-modtime</code> for a slightly different effect) as each read of the modification time takes a transaction.</p>
<pre><code>--no-checksum     Don&#39;t compare checksums on up/download.
--no-modtime      Don&#39;t read/write the modification time (can speed things up).
--no-seek         Don&#39;t allow seeking in files.
--read-only       Only allow read-only access.</code></pre>
<p>Sometimes rclone is delivered reads or writes out of order. Rather than seeking rclone will wait a short time for the in sequence read or write to come in. These flags only come into effect when not using an on disk cache file.</p>
<pre><code>--vfs-read-wait duration   Time to wait for in-sequence read before seeking (default 20ms)
--vfs-write-wait duration  Time to wait for in-sequence write before giving error (default 1s)</code></pre>
<p>When using VFS write caching (<code>--vfs-cache-mode</code> with value writes or full), the global flag <code>--transfers</code> can be set to adjust the number of parallel uploads of modified files from the cache (the related global flag <code>--checkers</code> has no effect on the VFS).</p>
<pre><code>--transfers int  Number of file transfers to run in parallel (default 4)</code></pre>
<h2 id="vfs-case-sensitivity">VFS Case Sensitivity</h2>
<p>Linux file systems are case-sensitive: two files can differ only by case, and the exact case must be used when opening a file.</p>
<p>File systems in modern Windows are case-insensitive but case-preserving: although existing files can be opened using any case, the exact case used to create the file is preserved and available for programs to query. It is not allowed for two files in the same directory to differ only by case.</p>
<p>Usually file systems on macOS are case-insensitive. It is possible to make macOS file systems case-sensitive but that is not the default.</p>
<p>The <code>--vfs-case-insensitive</code> VFS flag controls how rclone handles these two cases. If its value is "false", rclone passes file names to the remote as-is. If the flag is "true" (or appears without a value on the command line), rclone may perform a "fixup" as explained below.</p>
<p>The user may specify a file name to open/delete/rename/etc with a case different than what is stored on the remote. If an argument refers to an existing file with exactly the same name, then the case of the existing file on the disk will be used. However, if a file name with exactly the same name is not found but a name differing only by case exists, rclone will transparently fixup the name. This fixup happens only when an existing file is requested. Case sensitivity of file names created anew by rclone is controlled by the underlying remote.</p>
<p>Note that case sensitivity of the operating system running rclone (the target) may differ from case sensitivity of a file system presented by rclone (the source). The flag controls whether "fixup" is performed to satisfy the target.</p>
<p>If the flag is not provided on the command line, then its default value depends on the operating system where rclone runs: "true" on Windows and macOS, "false" otherwise. If the flag is provided without a value, then it is "true".</p>
<p>The <code>--no-unicode-normalization</code> flag controls whether a similar "fixup" is performed for filenames that differ but are <a href="https://en.wikipedia.org/wiki/Unicode_equivalence">canonically equivalent</a> with respect to unicode. Unicode normalization can be particularly helpful for users of macOS, which prefers form NFD instead of the NFC used by most other platforms. It is therefore highly recommended to keep the default of <code>false</code> on macOS, to avoid encoding compatibility issues.</p>
<p>In the (probably unlikely) event that a directory has multiple duplicate filenames after applying case and unicode normalization, the <code>--vfs-block-norm-dupes</code> flag allows hiding these duplicates. This comes with a performance tradeoff, as rclone will have to scan the entire directory for duplicates when listing a directory. For this reason, it is recommended to leave this disabled if not needed. However, macOS users may wish to consider using it, as otherwise, if a remote directory contains both NFC and NFD versions of the same filename, an odd situation will occur: both versions of the file will be visible in the mount, and both will appear to be editable, however, editing either version will actually result in only the NFD version getting edited under the hood. <code>--vfs-block- norm-dupes</code> prevents this confusion by detecting this scenario, hiding the duplicates, and logging an error, similar to how this is handled in <code>rclone sync</code>.</p>
<h2 id="vfs-disk-options">VFS Disk Options</h2>
<p>This flag allows you to manually set the statistics about the filing system. It can be useful when those statistics cannot be read correctly automatically.</p>
<pre><code>--vfs-disk-space-total-size    Manually set the total disk space size (example: 256G, default: -1)</code></pre>
<h2 id="alternate-report-of-used-bytes">Alternate report of used bytes</h2>
<p>Some backends, most notably S3, do not report the amount of bytes used. If you need this information to be available when running <code>df</code> on the filesystem, then pass the flag <code>--vfs-used-is-size</code> to rclone. With this flag set, instead of relying on the backend to report this information, rclone will scan the whole remote similar to <code>rclone size</code> and compute the total used space itself.</p>
<p><em>WARNING.</em> Contrary to <code>rclone size</code>, this flag ignores filters so that the result is accurate. However, this is very inefficient and may cost lots of API calls resulting in extra charges. Use it as a last resort and only with caching.</p>
<pre><code>rclone mount remote:path /path/to/mountpoint [flags]</code></pre>
<h2 id="options-60">Options</h2>
<pre><code>      --allow-non-empty                        Allow mounting over a non-empty directory (not supported on Windows)
      --allow-other                            Allow access to other users (not supported on Windows)
      --allow-root                             Allow access to root user (not supported on Windows)
      --async-read                             Use asynchronous reads (not supported on Windows) (default true)
      --attr-timeout Duration                  Time for which file/directory attributes are cached (default 1s)
      --daemon                                 Run mount in background and exit parent process (as background output is suppressed, use --log-file with --log-format=pid,... to monitor) (not supported on Windows)
      --daemon-timeout Duration                Time limit for rclone to respond to kernel (not supported on Windows) (default 0s)
      --daemon-wait Duration                   Time to wait for ready mount from daemon (maximum time on Linux, constant sleep time on OSX/BSD) (not supported on Windows) (default 1m0s)
      --debug-fuse                             Debug the FUSE internals - needs -v
      --default-permissions                    Makes kernel enforce access control based on the file mode (not supported on Windows)
      --devname string                         Set the device name - default is remote:path
      --dir-cache-time Duration                Time to cache directory entries for (default 5m0s)
      --dir-perms FileMode                     Directory permissions (default 777)
      --direct-io                              Use Direct IO, disables caching of data
      --file-perms FileMode                    File permissions (default 666)
      --fuse-flag stringArray                  Flags or arguments to be passed direct to libfuse/WinFsp (repeat if required)
      --gid uint32                             Override the gid field set by the filesystem (not supported on Windows) (default 1000)
  -h, --help                                   help for mount
      --max-read-ahead SizeSuffix              The number of bytes that can be prefetched for sequential reads (not supported on Windows) (default 128Ki)
      --mount-case-insensitive Tristate        Tell the OS the mount is case insensitive (true) or sensitive (false) regardless of the backend (auto) (default unset)
      --network-mode                           Mount as remote network drive, instead of fixed disk drive (supported on Windows only)
      --no-checksum                            Don&#39;t compare checksums on up/download
      --no-modtime                             Don&#39;t read/write the modification time (can speed things up)
      --no-seek                                Don&#39;t allow seeking in files
      --noappledouble                          Ignore Apple Double (._) and .DS_Store files (supported on OSX only) (default true)
      --noapplexattr                           Ignore all &quot;com.apple.*&quot; extended attributes (supported on OSX only)
  -o, --option stringArray                     Option for libfuse/WinFsp (repeat if required)
      --poll-interval Duration                 Time to wait between polling for changes, must be smaller than dir-cache-time and only on supported remotes (set 0 to disable) (default 1m0s)
      --read-only                              Only allow read-only access
      --uid uint32                             Override the uid field set by the filesystem (not supported on Windows) (default 1000)
      --umask FileMode                         Override the permission bits set by the filesystem (not supported on Windows) (default 002)
      --vfs-block-norm-dupes                   If duplicate filenames exist in the same directory (after normalization), log an error and hide the duplicates (may have a performance cost)
      --vfs-cache-max-age Duration             Max time since last access of objects in the cache (default 1h0m0s)
      --vfs-cache-max-size SizeSuffix          Max total size of objects in the cache (default off)
      --vfs-cache-min-free-space SizeSuffix    Target minimum free space on the disk containing the cache (default off)
      --vfs-cache-mode CacheMode               Cache mode off|minimal|writes|full (default off)
      --vfs-cache-poll-interval Duration       Interval to poll the cache for stale objects (default 1m0s)
      --vfs-case-insensitive                   If a file name not found, find a case insensitive match
      --vfs-disk-space-total-size SizeSuffix   Specify the total space of disk (default off)
      --vfs-fast-fingerprint                   Use fast (less accurate) fingerprints for change detection
      --vfs-read-ahead SizeSuffix              Extra read ahead over --buffer-size when using cache-mode full
      --vfs-read-chunk-size SizeSuffix         Read the source objects in chunks (default 128Mi)
      --vfs-read-chunk-size-limit SizeSuffix   If greater than --vfs-read-chunk-size, double the chunk size after each chunk read, until the limit is reached (&#39;off&#39; is unlimited) (default off)
      --vfs-read-chunk-streams int             The number of parallel streams to read at once
      --vfs-read-wait Duration                 Time to wait for in-sequence read before seeking (default 20ms)
      --vfs-refresh                            Refreshes the directory cache recursively in the background on start
      --vfs-used-is-size rclone size           Use the rclone size algorithm for Used size
      --vfs-write-back Duration                Time to writeback files after last use when using cache (default 5s)
      --vfs-write-wait Duration                Time to wait for in-sequence write before giving error (default 1s)
      --volname string                         Set the volume name (supported on Windows and OSX only)
      --write-back-cache                       Makes kernel buffer writes before sending them to rclone (without this, writethrough caching is used) (not supported on Windows)</code></pre>
<p>Options shared with other commands are described next. See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
<h3 id="filter-options-19">Filter Options</h3>
<p>Flags for filtering directory listings</p>
<pre><code>      --delete-excluded                     Delete files on dest excluded from sync
      --exclude stringArray                 Exclude files matching pattern
      --exclude-from stringArray            Read file exclude patterns from file (use - to read from stdin)
      --exclude-if-present stringArray      Exclude directories if filename is present
      --files-from stringArray              Read list of source-file names from file (use - to read from stdin)
      --files-from-raw stringArray          Read list of source-file names from file without any processing of lines (use - to read from stdin)
  -f, --filter stringArray                  Add a file filtering rule
      --filter-from stringArray             Read file filtering patterns from a file (use - to read from stdin)
      --ignore-case                         Ignore case in filters (case insensitive)
      --include stringArray                 Include files matching pattern
      --include-from stringArray            Read file include patterns from file (use - to read from stdin)
      --max-age Duration                    Only transfer files younger than this in s or suffix ms|s|m|h|d|w|M|y (default off)
      --max-depth int                       If set limits the recursion depth to this (default -1)
      --max-size SizeSuffix                 Only transfer files smaller than this in KiB or suffix B|K|M|G|T|P (default off)
      --metadata-exclude stringArray        Exclude metadatas matching pattern
      --metadata-exclude-from stringArray   Read metadata exclude patterns from file (use - to read from stdin)
      --metadata-filter stringArray         Add a metadata filtering rule
      --metadata-filter-from stringArray    Read metadata filtering patterns from a file (use - to read from stdin)
      --metadata-include stringArray        Include metadatas matching pattern
      --metadata-include-from stringArray   Read metadata include patterns from file (use - to read from stdin)
      --min-age Duration                    Only transfer files older than this in s or suffix ms|s|m|h|d|w|M|y (default off)
      --min-size SizeSuffix                 Only transfer files bigger than this in KiB or suffix B|K|M|G|T|P (default off)</code></pre>
<h2 id="see-also-60">See Also</h2>
<ul>
<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
</ul>
<h1 id="rclone-moveto">rclone moveto</h1>
<p>Move file or directory from source to dest.</p>
<h2 id="synopsis-53">Synopsis</h2>
<p>If source:path is a file or directory then it moves it to a file or directory named dest:path.</p>
<p>This can be used to rename files or upload single files to other than their existing name. If the source is a directory then it acts exactly like the <a href="https://rclone.org/commands/rclone_move/">move</a> command.</p>
<p>So</p>
<pre><code>rclone moveto src dst</code></pre>
<p>where src and dst are rclone paths, either remote:path or /path/to/local or C:.</p>
<p>This will:</p>
<pre><code>if src is file
    move it to dst, overwriting an existing file if it exists
if src is directory
    move it to dst, overwriting existing files if they exist
    see move command for full details</code></pre>
<p>This doesn't transfer files that are identical on src and dst, testing by size and modification time or MD5SUM. src will be deleted on successful transfer.</p>
<p><strong>Important</strong>: Since this can cause data loss, test first with the <code>--dry-run</code> or the <code>--interactive</code>/<code>-i</code> flag.</p>
<p><strong>Note</strong>: Use the <code>-P</code>/<code>--progress</code> flag to view real-time transfer statistics.</p>
<pre><code>rclone moveto source:path dest:path [flags]</code></pre>
<h2 id="options-61">Options</h2>
<pre><code>  -h, --help   help for moveto</code></pre>
<p>Options shared with other commands are described next. See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
<h3 id="copy-options-5">Copy Options</h3>
<p>Flags for anything which can copy a file</p>
<pre><code>      --check-first                                 Do all the checks before starting transfers
  -c, --checksum                                    Check for changes with size &amp; checksum (if available, or fallback to size only)
      --compare-dest stringArray                    Include additional server-side paths during comparison
      --copy-dest stringArray                       Implies --compare-dest but also copies files from paths into destination
      --cutoff-mode HARD|SOFT|CAUTIOUS              Mode to stop transfers when reaching the max transfer limit HARD|SOFT|CAUTIOUS (default HARD)
      --ignore-case-sync                            Ignore case when synchronizing
      --ignore-checksum                             Skip post copy check of checksums
      --ignore-existing                             Skip all files that exist on destination
      --ignore-size                                 Ignore size when skipping use modtime or checksum
  -I, --ignore-times                                Don&#39;t skip items that match size and time - transfer all unconditionally
      --immutable                                   Do not modify files, fail if existing files have been modified
      --inplace                                     Download directly to destination file instead of atomic download to temp/rename
      --max-backlog int                             Maximum number of objects in sync or check backlog (default 10000)
      --max-duration Duration                       Maximum duration rclone will transfer data for (default 0s)
      --max-transfer SizeSuffix                     Maximum size of data to transfer (default off)
  -M, --metadata                                    If set, preserve metadata when copying objects
      --modify-window Duration                      Max time diff to be considered the same (default 1ns)
      --multi-thread-chunk-size SizeSuffix          Chunk size for multi-thread downloads / uploads, if not set by filesystem (default 64Mi)
      --multi-thread-cutoff SizeSuffix              Use multi-thread downloads for files above this size (default 256Mi)
      --multi-thread-streams int                    Number of streams to use for multi-thread downloads (default 4)
      --multi-thread-write-buffer-size SizeSuffix   In memory buffer size for writing when in multi-thread mode (default 128Ki)
      --no-check-dest                               Don&#39;t check the destination, copy regardless
      --no-traverse                                 Don&#39;t traverse destination file system on copy
      --no-update-dir-modtime                       Don&#39;t update directory modification times
      --no-update-modtime                           Don&#39;t update destination modtime if files identical
      --order-by string                             Instructions on how to order the transfers, e.g. &#39;size,descending&#39;
      --partial-suffix string                       Add partial-suffix to temporary file name when --inplace is not used (default &quot;.partial&quot;)
      --refresh-times                               Refresh the modtime of remote files
      --server-side-across-configs                  Allow server-side operations (e.g. copy) to work across different configs
      --size-only                                   Skip based on size only, not modtime or checksum
      --streaming-upload-cutoff SizeSuffix          Cutoff for switching to chunked upload if file size is unknown, upload starts after reaching cutoff or when file ends (default 100Ki)
  -u, --update                                      Skip files that are newer on the destination</code></pre>
<h3 id="important-options-14">Important Options</h3>
<p>Important flags useful for most commands</p>
<pre><code>  -n, --dry-run         Do a trial run with no permanent changes
  -i, --interactive     Enable interactive mode
  -v, --verbose count   Print lots more stuff (repeat for more)</code></pre>
<h3 id="filter-options-20">Filter Options</h3>
<p>Flags for filtering directory listings</p>
<pre><code>      --delete-excluded                     Delete files on dest excluded from sync
      --exclude stringArray                 Exclude files matching pattern
      --exclude-from stringArray            Read file exclude patterns from file (use - to read from stdin)
      --exclude-if-present stringArray      Exclude directories if filename is present
      --files-from stringArray              Read list of source-file names from file (use - to read from stdin)
      --files-from-raw stringArray          Read list of source-file names from file without any processing of lines (use - to read from stdin)
  -f, --filter stringArray                  Add a file filtering rule
      --filter-from stringArray             Read file filtering patterns from a file (use - to read from stdin)
      --ignore-case                         Ignore case in filters (case insensitive)
      --include stringArray                 Include files matching pattern
      --include-from stringArray            Read file include patterns from file (use - to read from stdin)
      --max-age Duration                    Only transfer files younger than this in s or suffix ms|s|m|h|d|w|M|y (default off)
      --max-depth int                       If set limits the recursion depth to this (default -1)
      --max-size SizeSuffix                 Only transfer files smaller than this in KiB or suffix B|K|M|G|T|P (default off)
      --metadata-exclude stringArray        Exclude metadatas matching pattern
      --metadata-exclude-from stringArray   Read metadata exclude patterns from file (use - to read from stdin)
      --metadata-filter stringArray         Add a metadata filtering rule
      --metadata-filter-from stringArray    Read metadata filtering patterns from a file (use - to read from stdin)
      --metadata-include stringArray        Include metadatas matching pattern
      --metadata-include-from stringArray   Read metadata include patterns from file (use - to read from stdin)
      --min-age Duration                    Only transfer files older than this in s or suffix ms|s|m|h|d|w|M|y (default off)
      --min-size SizeSuffix                 Only transfer files bigger than this in KiB or suffix B|K|M|G|T|P (default off)</code></pre>
<h3 id="listing-options-18">Listing Options</h3>
<p>Flags for listing directories</p>
<pre><code>      --default-time Time   Time to show if modtime is unknown for files and directories (default 2000-01-01T00:00:00Z)
      --fast-list           Use recursive list if available; uses more memory but fewer transactions</code></pre>
<h2 id="see-also-61">See Also</h2>
<ul>
<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
</ul>
<h1 id="rclone-ncdu">rclone ncdu</h1>
<p>Explore a remote with a text based user interface.</p>
<h2 id="synopsis-54">Synopsis</h2>
<p>This displays a text based user interface allowing the navigation of a remote. It is most useful for answering the question - "What is using all my disk space?".</p>
<p>To make the user interface it first scans the entire remote given and builds an in memory representation. rclone ncdu can be used during this scanning phase and you will see it building up the directory structure as it goes along.</p>
<p>You can interact with the user interface using key presses, press '?' to toggle the help on and off. The supported keys are:</p>
<pre><code> ↑,↓ or k,j to Move
 →,l to enter
 ←,h to return
 g toggle graph
 c toggle counts
 a toggle average size in directory
 m toggle modified time
 u toggle human-readable format
 n,s,C,A,M sort by name,size,count,asize,mtime
 d delete file/directory
 v select file/directory
 V enter visual select mode
 D delete selected files/directories
 y copy current path to clipboard
 Y display current path
 ^L refresh screen (fix screen corruption)
 r recalculate file sizes
 ? to toggle help on and off
 ESC to close the menu box
 q/^c to quit</code></pre>
<p>Listed files/directories may be prefixed by a one-character flag, some of them combined with a description in brackets at end of line. These flags have the following meaning:</p>
<pre><code>e means this is an empty directory, i.e. contains no files (but
  may contain empty subdirectories)
~ means this is a directory where some of the files (possibly in
  subdirectories) have unknown size, and therefore the directory
  size may be underestimated (and average size inaccurate, as it
  is average of the files with known sizes).
. means an error occurred while reading a subdirectory, and
  therefore the directory size may be underestimated (and average
  size inaccurate)
! means an error occurred while reading this directory</code></pre>
<p>This an homage to the <a href="https://dev.yorhel.nl/ncdu">ncdu tool</a> but for rclone remotes. It is missing lots of features at the moment but is useful as it stands. Unlike ncdu it does not show excluded files.</p>
<p>Note that it might take some time to delete big files/directories. The UI won't respond in the meantime since the deletion is done synchronously.</p>
<p>For a non-interactive listing of the remote, see the <a href="https://rclone.org/commands/rclone_tree/">tree</a> command. To just get the total size of the remote you can also use the <a href="https://rclone.org/commands/rclone_size/">size</a> command.</p>
<pre><code>rclone ncdu remote:path [flags]</code></pre>
<h2 id="options-62">Options</h2>
<pre><code>  -h, --help   help for ncdu</code></pre>
<p>Options shared with other commands are described next. See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
<h3 id="filter-options-21">Filter Options</h3>
<p>Flags for filtering directory listings</p>
<pre><code>      --delete-excluded                     Delete files on dest excluded from sync
      --exclude stringArray                 Exclude files matching pattern
      --exclude-from stringArray            Read file exclude patterns from file (use - to read from stdin)
      --exclude-if-present stringArray      Exclude directories if filename is present
      --files-from stringArray              Read list of source-file names from file (use - to read from stdin)
      --files-from-raw stringArray          Read list of source-file names from file without any processing of lines (use - to read from stdin)
  -f, --filter stringArray                  Add a file filtering rule
      --filter-from stringArray             Read file filtering patterns from a file (use - to read from stdin)
      --ignore-case                         Ignore case in filters (case insensitive)
      --include stringArray                 Include files matching pattern
      --include-from stringArray            Read file include patterns from file (use - to read from stdin)
      --max-age Duration                    Only transfer files younger than this in s or suffix ms|s|m|h|d|w|M|y (default off)
      --max-depth int                       If set limits the recursion depth to this (default -1)
      --max-size SizeSuffix                 Only transfer files smaller than this in KiB or suffix B|K|M|G|T|P (default off)
      --metadata-exclude stringArray        Exclude metadatas matching pattern
      --metadata-exclude-from stringArray   Read metadata exclude patterns from file (use - to read from stdin)
      --metadata-filter stringArray         Add a metadata filtering rule
      --metadata-filter-from stringArray    Read metadata filtering patterns from a file (use - to read from stdin)
      --metadata-include stringArray        Include metadatas matching pattern
      --metadata-include-from stringArray   Read metadata include patterns from file (use - to read from stdin)
      --min-age Duration                    Only transfer files older than this in s or suffix ms|s|m|h|d|w|M|y (default off)
      --min-size SizeSuffix                 Only transfer files bigger than this in KiB or suffix B|K|M|G|T|P (default off)</code></pre>
<h3 id="listing-options-19">Listing Options</h3>
<p>Flags for listing directories</p>
<pre><code>      --default-time Time   Time to show if modtime is unknown for files and directories (default 2000-01-01T00:00:00Z)
      --fast-list           Use recursive list if available; uses more memory but fewer transactions</code></pre>
<h2 id="see-also-62">See Also</h2>
<ul>
<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
</ul>
<h1 id="rclone-nfsmount">rclone nfsmount</h1>
<p>Mount the remote as file system on a mountpoint.</p>
<h2 id="synopsis-55">Synopsis</h2>
<p>Rclone nfsmount allows Linux, FreeBSD, macOS and Windows to mount any of Rclone's cloud storage systems as a file system with FUSE.</p>
<p>First set up your remote using <code>rclone config</code>. Check it works with <code>rclone ls</code> etc.</p>
<p>On Linux and macOS, you can run mount in either foreground or background (aka daemon) mode. Mount runs in foreground mode by default. Use the <code>--daemon</code> flag to force background mode. On Windows you can run mount in foreground only, the flag is ignored.</p>
<p>In background mode rclone acts as a generic Unix mount program: the main program starts, spawns background rclone process to setup and maintain the mount, waits until success or timeout and exits with appropriate code (killing the child process if it fails).</p>
<p>On Linux/macOS/FreeBSD start the mount like this, where <code>/path/to/local/mount</code> is an <strong>empty</strong> <strong>existing</strong> directory:</p>
<pre><code>rclone nfsmount remote:path/to/files /path/to/local/mount</code></pre>
<p>On Windows you can start a mount in different ways. See <a href="#mounting-modes-on-windows">below</a> for details. If foreground mount is used interactively from a console window, rclone will serve the mount and occupy the console so another window should be used to work with the mount until rclone is interrupted e.g. by pressing Ctrl-C.</p>
<p>The following examples will mount to an automatically assigned drive, to specific drive letter <code>X:</code>, to path <code>C:\path\parent\mount</code> (where parent directory or drive must exist, and mount must <strong>not</strong> exist, and is not supported when <a href="#mounting-modes-on-windows">mounting as a network drive</a>), and the last example will mount as network share <code>\\cloud\remote</code> and map it to an automatically assigned drive:</p>
<pre><code>rclone nfsmount remote:path/to/files *
rclone nfsmount remote:path/to/files X:
rclone nfsmount remote:path/to/files C:\path\parent\mount
rclone nfsmount remote:path/to/files \\cloud\remote</code></pre>
<p>When the program ends while in foreground mode, either via Ctrl+C or receiving a SIGINT or SIGTERM signal, the mount should be automatically stopped.</p>
<p>When running in background mode the user will have to stop the mount manually:</p>
<pre><code># Linux
fusermount -u /path/to/local/mount
#... or on some systems
fusermount3 -u /path/to/local/mount
# OS X or Linux when using nfsmount
umount /path/to/local/mount</code></pre>
<p>The umount operation can fail, for example when the mountpoint is busy. When that happens, it is the user's responsibility to stop the mount manually.</p>
<p>The size of the mounted file system will be set according to information retrieved from the remote, the same as returned by the <a href="https://rclone.org/commands/rclone_about/">rclone about</a> command. Remotes with unlimited storage may report the used size only, then an additional 1 PiB of free space is assumed. If the remote does not <a href="https://rclone.org/overview/#optional-features">support</a> the about feature at all, then 1 PiB is set as both the total and the free size.</p>
<h2 id="installing-on-windows-1">Installing on Windows</h2>
<p>To run rclone nfsmount on Windows, you will need to download and install <a href="http://www.secfs.net/winfsp/">WinFsp</a>.</p>
<p><a href="https://github.com/winfsp/winfsp">WinFsp</a> is an open-source Windows File System Proxy which makes it easy to write user space file systems for Windows. It provides a FUSE emulation layer which rclone uses combination with <a href="https://github.com/winfsp/cgofuse">cgofuse</a>. Both of these packages are by Bill Zissimopoulos who was very helpful during the implementation of rclone nfsmount for Windows.</p>
<h3 id="mounting-modes-on-windows-1">Mounting modes on windows</h3>
<p>Unlike other operating systems, Microsoft Windows provides a different filesystem type for network and fixed drives. It optimises access on the assumption fixed disk drives are fast and reliable, while network drives have relatively high latency and less reliability. Some settings can also be differentiated between the two types, for example that Windows Explorer should just display icons and not create preview thumbnails for image and video files on network drives.</p>
<p>In most cases, rclone will mount the remote as a normal, fixed disk drive by default. However, you can also choose to mount it as a remote network drive, often described as a network share. If you mount an rclone remote using the default, fixed drive mode and experience unexpected program errors, freezes or other issues, consider mounting as a network drive instead.</p>
<p>When mounting as a fixed disk drive you can either mount to an unused drive letter, or to a path representing a <strong>nonexistent</strong> subdirectory of an <strong>existing</strong> parent directory or drive. Using the special value <code>*</code> will tell rclone to automatically assign the next available drive letter, starting with Z: and moving backward. Examples:</p>
<pre><code>rclone nfsmount remote:path/to/files *
rclone nfsmount remote:path/to/files X:
rclone nfsmount remote:path/to/files C:\path\parent\mount
rclone nfsmount remote:path/to/files X:</code></pre>
<p>Option <code>--volname</code> can be used to set a custom volume name for the mounted file system. The default is to use the remote name and path.</p>
<p>To mount as network drive, you can add option <code>--network-mode</code> to your nfsmount command. Mounting to a directory path is not supported in this mode, it is a limitation Windows imposes on junctions, so the remote must always be mounted to a drive letter.</p>
<pre><code>rclone nfsmount remote:path/to/files X: --network-mode</code></pre>
<p>A volume name specified with <code>--volname</code> will be used to create the network share path. A complete UNC path, such as <code>\\cloud\remote</code>, optionally with path <code>\\cloud\remote\madeup\path</code>, will be used as is. Any other string will be used as the share part, after a default prefix <code>\\server\</code>. If no volume name is specified then <code>\\server\share</code> will be used. You must make sure the volume name is unique when you are mounting more than one drive, or else the mount command will fail. The share name will treated as the volume label for the mapped drive, shown in Windows Explorer etc, while the complete <code>\\server\share</code> will be reported as the remote UNC path by <code>net use</code> etc, just like a normal network drive mapping.</p>
<p>If you specify a full network share UNC path with <code>--volname</code>, this will implicitly set the <code>--network-mode</code> option, so the following two examples have same result:</p>
<pre><code>rclone nfsmount remote:path/to/files X: --network-mode
rclone nfsmount remote:path/to/files X: --volname \\server\share</code></pre>
<p>You may also specify the network share UNC path as the mountpoint itself. Then rclone will automatically assign a drive letter, same as with <code>*</code> and use that as mountpoint, and instead use the UNC path specified as the volume name, as if it were specified with the <code>--volname</code> option. This will also implicitly set the <code>--network-mode</code> option. This means the following two examples have same result:</p>
<pre><code>rclone nfsmount remote:path/to/files \\cloud\remote
rclone nfsmount remote:path/to/files * --volname \\cloud\remote</code></pre>
<p>There is yet another way to enable network mode, and to set the share path, and that is to pass the "native" libfuse/WinFsp option directly: <code>--fuse-flag --VolumePrefix=\server\share</code>. Note that the path must be with just a single backslash prefix in this case.</p>
<p><em>Note:</em> In previous versions of rclone this was the only supported method.</p>
<p><a href="https://en.wikipedia.org/wiki/Drive_mapping">Read more about drive mapping</a></p>
<p>See also <a href="#limitations">Limitations</a> section below.</p>
<h3 id="windows-filesystem-permissions-1">Windows filesystem permissions</h3>
<p>The FUSE emulation layer on Windows must convert between the POSIX-based permission model used in FUSE, and the permission model used in Windows, based on access-control lists (ACL).</p>
<p>The mounted filesystem will normally get three entries in its access-control list (ACL), representing permissions for the POSIX permission scopes: Owner, group and others. By default, the owner and group will be taken from the current user, and the built-in group "Everyone" will be used to represent others. The user/group can be customized with FUSE options "UserName" and "GroupName", e.g. <code>-o UserName=user123 -o GroupName="Authenticated Users"</code>. The permissions on each entry will be set according to <a href="#options">options</a> <code>--dir-perms</code> and <code>--file-perms</code>, which takes a value in traditional Unix <a href="https://en.wikipedia.org/wiki/File-system_permissions#Numeric_notation">numeric notation</a>.</p>
<p>The default permissions corresponds to <code>--file-perms 0666 --dir-perms 0777</code>, i.e. read and write permissions to everyone. This means you will not be able to start any programs from the mount. To be able to do that you must add execute permissions, e.g. <code>--file-perms 0777 --dir-perms 0777</code> to add it to everyone. If the program needs to write files, chances are you will have to enable <a href="#vfs-file-caching">VFS File Caching</a> as well (see also <a href="#limitations">limitations</a>). Note that the default write permission have some restrictions for accounts other than the owner, specifically it lacks the "write extended attributes", as explained next.</p>
<p>The mapping of permissions is not always trivial, and the result you see in Windows Explorer may not be exactly like you expected. For example, when setting a value that includes write access for the group or others scope, this will be mapped to individual permissions "write attributes", "write data" and "append data", but not "write extended attributes". Windows will then show this as basic permission "Special" instead of "Write", because "Write" also covers the "write extended attributes" permission. When setting digit 0 for group or others, to indicate no permissions, they will still get individual permissions "read attributes", "read extended attributes" and "read permissions". This is done for compatibility reasons, e.g. to allow users without additional permissions to be able to read basic metadata about files like in Unix.</p>
<p>WinFsp 2021 (version 1.9) introduced a new FUSE option "FileSecurity", that allows the complete specification of file security descriptors using <a href="https://docs.microsoft.com/en-us/windows/win32/secauthz/security-descriptor-string-format">SDDL</a>. With this you get detailed control of the resulting permissions, compared to use of the POSIX permissions described above, and no additional permissions will be added automatically for compatibility with Unix. Some example use cases will following.</p>
<p>If you set POSIX permissions for only allowing access to the owner, using <code>--file-perms 0600 --dir-perms 0700</code>, the user group and the built-in "Everyone" group will still be given some special permissions, as described above. Some programs may then (incorrectly) interpret this as the file being accessible by everyone, for example an SSH client may warn about "unprotected private key file". You can work around this by specifying <code>-o FileSecurity="D:P(A;;FA;;;OW)"</code>, which sets file all access (FA) to the owner (OW), and nothing else.</p>
<p>When setting write permissions then, except for the owner, this does not include the "write extended attributes" permission, as mentioned above. This may prevent applications from writing to files, giving permission denied error instead. To set working write permissions for the built-in "Everyone" group, similar to what it gets by default but with the addition of the "write extended attributes", you can specify <code>-o FileSecurity="D:P(A;;FRFW;;;WD)"</code>, which sets file read (FR) and file write (FW) to everyone (WD). If file execute (FX) is also needed, then change to <code>-o FileSecurity="D:P(A;;FRFWFX;;;WD)"</code>, or set file all access (FA) to get full access permissions, including delete, with <code>-o FileSecurity="D:P(A;;FA;;;WD)"</code>.</p>
<h3 id="windows-caveats-1">Windows caveats</h3>
<p>Drives created as Administrator are not visible to other accounts, not even an account that was elevated to Administrator with the User Account Control (UAC) feature. A result of this is that if you mount to a drive letter from a Command Prompt run as Administrator, and then try to access the same drive from Windows Explorer (which does not run as Administrator), you will not be able to see the mounted drive.</p>
<p>If you don't need to access the drive from applications running with administrative privileges, the easiest way around this is to always create the mount from a non-elevated command prompt.</p>
<p>To make mapped drives available to the user account that created them regardless if elevated or not, there is a special Windows setting called <a href="https://docs.microsoft.com/en-us/troubleshoot/windows-client/networking/mapped-drives-not-available-from-elevated-command#detail-to-configure-the-enablelinkedconnections-registry-entry">linked connections</a> that can be enabled.</p>
<p>It is also possible to make a drive mount available to everyone on the system, by running the process creating it as the built-in SYSTEM account. There are several ways to do this: One is to use the command-line utility <a href="https://docs.microsoft.com/en-us/sysinternals/downloads/psexec">PsExec</a>, from Microsoft's Sysinternals suite, which has option <code>-s</code> to start processes as the SYSTEM account. Another alternative is to run the mount command from a Windows Scheduled Task, or a Windows Service, configured to run as the SYSTEM account. A third alternative is to use the <a href="https://github.com/winfsp/winfsp/wiki/WinFsp-Service-Architecture">WinFsp.Launcher infrastructure</a>). Read more in the <a href="https://rclone.org/install/">install documentation</a>. Note that when running rclone as another user, it will not use the configuration file from your profile unless you tell it to with the <a href="https://rclone.org/docs/#config-config-file"><code>--config</code></a> option. Note also that it is now the SYSTEM account that will have the owner permissions, and other accounts will have permissions according to the group or others scopes. As mentioned above, these will then not get the "write extended attributes" permission, and this may prevent writing to files. You can work around this with the FileSecurity option, see example above.</p>
<p>Note that mapping to a directory path, instead of a drive letter, does not suffer from the same limitations.</p>
<h2 id="mounting-on-macos-1">Mounting on macOS</h2>
<p>Mounting on macOS can be done either via <a href="https://rclone.org/commands/rclone_serve_nfs/">built-in NFS server</a>, <a href="https://osxfuse.github.io/">macFUSE</a> (also known as osxfuse) or <a href="https://www.fuse-t.org/">FUSE-T</a>. macFUSE is a traditional FUSE driver utilizing a macOS kernel extension (kext). FUSE-T is an alternative FUSE system which "mounts" via an NFSv4 local server.</p>
<h4 id="unicode-normalization-1">Unicode Normalization</h4>
<p>It is highly recommended to keep the default of <code>--no-unicode-normalization=false</code> for all <code>mount</code> and <code>serve</code> commands on macOS. For details, see <a href="https://rclone.org/commands/rclone_mount/#vfs-case-sensitivity">vfs-case-sensitivity</a>.</p>
<h3 id="nfs-mount-1">NFS mount</h3>
<p>This method spins up an NFS server using <a href="https://rclone.org/commands/rclone_serve_nfs/">serve nfs</a> command and mounts it to the specified mountpoint. If you run this in background mode using |--daemon|, you will need to send SIGTERM signal to the rclone process using |kill| command to stop the mount.</p>
<p>Note that <code>--nfs-cache-handle-limit</code> controls the maximum number of cached file handles stored by the <code>nfsmount</code> caching handler. This should not be set too low or you may experience errors when trying to access files. The default is 1000000, but consider lowering this limit if the server's system resource usage causes problems.</p>
<h3 id="macfuse-notes-1">macFUSE Notes</h3>
<p>If installing macFUSE using <a href="https://github.com/osxfuse/osxfuse/releases">dmg packages</a> from the website, rclone will locate the macFUSE libraries without any further intervention. If however, macFUSE is installed using the <a href="https://www.macports.org/">macports</a> package manager, the following addition steps are required.</p>
<pre><code>sudo mkdir /usr/local/lib
cd /usr/local/lib
sudo ln -s /opt/local/lib/libfuse.2.dylib</code></pre>
<h3 id="fuse-t-limitations-caveats-and-notes-1">FUSE-T Limitations, Caveats, and Notes</h3>
<p>There are some limitations, caveats, and notes about how it works. These are current as of FUSE-T version 1.0.14.</p>
<h4 id="modtime-update-on-read-1">ModTime update on read</h4>
<p>As per the <a href="https://github.com/macos-fuse-t/fuse-t/wiki#caveats">FUSE-T wiki</a>:</p>
<blockquote>
<p>File access and modification times cannot be set separately as it seems to be an issue with the NFS client which always modifies both. Can be reproduced with 'touch -m' and 'touch -a' commands</p>
</blockquote>
<p>This means that viewing files with various tools, notably macOS Finder, will cause rlcone to update the modification time of the file. This may make rclone upload a full new copy of the file.</p>
<h4 id="read-only-mounts-1">Read Only mounts</h4>
<p>When mounting with <code>--read-only</code>, attempts to write to files will fail <em>silently</em> as opposed to with a clear warning as in macFUSE.</p>
<h2 id="limitations-1">Limitations</h2>
<p>Without the use of <code>--vfs-cache-mode</code> this can only write files sequentially, it can only seek when reading. This means that many applications won't work with their files on an rclone mount without <code>--vfs-cache-mode writes</code> or <code>--vfs-cache-mode full</code>. See the <a href="#vfs-file-caching">VFS File Caching</a> section for more info. When using NFS mount on macOS, if you don't specify |--vfs-cache-mode| the mount point will be read-only.</p>
<p>The bucket-based remotes (e.g. Swift, S3, Google Compute Storage, B2) do not support the concept of empty directories, so empty directories will have a tendency to disappear once they fall out of the directory cache.</p>
<p>When <code>rclone mount</code> is invoked on Unix with <code>--daemon</code> flag, the main rclone program will wait for the background mount to become ready or until the timeout specified by the <code>--daemon-wait</code> flag. On Linux it can check mount status using ProcFS so the flag in fact sets <strong>maximum</strong> time to wait, while the real wait can be less. On macOS / BSD the time to wait is constant and the check is performed only at the end. We advise you to set wait time on macOS reasonably.</p>
<p>Only supported on Linux, FreeBSD, OS X and Windows at the moment.</p>
<h2 id="rclone-nfsmount-vs-rclone-synccopy">rclone nfsmount vs rclone sync/copy</h2>
<p>File systems expect things to be 100% reliable, whereas cloud storage systems are a long way from 100% reliable. The rclone sync/copy commands cope with this with lots of retries. However rclone nfsmount can't use retries in the same way without making local copies of the uploads. Look at the <a href="#vfs-file-caching">VFS File Caching</a> for solutions to make nfsmount more reliable.</p>
<h2 id="attribute-caching-1">Attribute caching</h2>
<p>You can use the flag <code>--attr-timeout</code> to set the time the kernel caches the attributes (size, modification time, etc.) for directory entries.</p>
<p>The default is <code>1s</code> which caches files just long enough to avoid too many callbacks to rclone from the kernel.</p>
<p>In theory 0s should be the correct value for filesystems which can change outside the control of the kernel. However this causes quite a few problems such as <a href="https://github.com/rclone/rclone/issues/2157">rclone using too much memory</a>, <a href="https://forum.rclone.org/t/rclone-1-39-vs-1-40-mount-issue/5112">rclone not serving files to samba</a> and <a href="https://github.com/rclone/rclone/issues/2095#issuecomment-371141147">excessive time listing directories</a>.</p>
<p>The kernel can cache the info about a file for the time given by <code>--attr-timeout</code>. You may see corruption if the remote file changes length during this window. It will show up as either a truncated file or a file with garbage on the end. With <code>--attr-timeout 1s</code> this is very unlikely but not impossible. The higher you set <code>--attr-timeout</code> the more likely it is. The default setting of "1s" is the lowest setting which mitigates the problems above.</p>
<p>If you set it higher (<code>10s</code> or <code>1m</code> say) then the kernel will call back to rclone less often making it more efficient, however there is more chance of the corruption issue above.</p>
<p>If files don't change on the remote outside of the control of rclone then there is no chance of corruption.</p>
<p>This is the same as setting the attr_timeout option in mount.fuse.</p>
<h2 id="filters-1">Filters</h2>
<p>Note that all the rclone filters can be used to select a subset of the files to be visible in the mount.</p>
<h2 id="systemd-1">systemd</h2>
<p>When running rclone nfsmount as a systemd service, it is possible to use Type=notify. In this case the service will enter the started state after the mountpoint has been successfully set up. Units having the rclone nfsmount service specified as a requirement will see all files and folders immediately in this mode.</p>
<p>Note that systemd runs mount units without any environment variables including <code>PATH</code> or <code>HOME</code>. This means that tilde (<code>~</code>) expansion will not work and you should provide <code>--config</code> and <code>--cache-dir</code> explicitly as absolute paths via rclone arguments. Since mounting requires the <code>fusermount</code> or <code>fusermount3</code> program, rclone will use the fallback PATH of <code>/bin:/usr/bin</code> in this scenario. Please ensure that <code>fusermount</code>/<code>fusermount3</code> is present on this PATH.</p>
<h2 id="rclone-as-unix-mount-helper-1">Rclone as Unix mount helper</h2>
<p>The core Unix program <code>/bin/mount</code> normally takes the <code>-t FSTYPE</code> argument then runs the <code>/sbin/mount.FSTYPE</code> helper program passing it mount options as <code>-o key=val,...</code> or <code>--opt=...</code>. Automount (classic or systemd) behaves in a similar way.</p>
<p>rclone by default expects GNU-style flags <code>--key val</code>. To run it as a mount helper you should symlink rclone binary to <code>/sbin/mount.rclone</code> and optionally <code>/usr/bin/rclonefs</code>, e.g. <code>ln -s /usr/bin/rclone /sbin/mount.rclone</code>. rclone will detect it and translate command-line arguments appropriately.</p>
<p>Now you can run classic mounts like this:</p>
<pre><code>mount sftp1:subdir /mnt/data -t rclone -o vfs_cache_mode=writes,sftp_key_file=/path/to/pem</code></pre>
<p>or create systemd mount units:</p>
<pre><code># /etc/systemd/system/mnt-data.mount
[Unit]
Description=Mount for /mnt/data
[Mount]
Type=rclone
What=sftp1:subdir
Where=/mnt/data
Options=rw,_netdev,allow_other,args2env,vfs-cache-mode=writes,config=/etc/rclone.conf,cache-dir=/var/rclone</code></pre>
<p>optionally accompanied by systemd automount unit</p>
<pre><code># /etc/systemd/system/mnt-data.automount
[Unit]
Description=AutoMount for /mnt/data
[Automount]
Where=/mnt/data
TimeoutIdleSec=600
[Install]
WantedBy=multi-user.target</code></pre>
<p>or add in <code>/etc/fstab</code> a line like</p>
<pre><code>sftp1:subdir /mnt/data rclone rw,noauto,nofail,_netdev,x-systemd.automount,args2env,vfs_cache_mode=writes,config=/etc/rclone.conf,cache_dir=/var/cache/rclone 0 0</code></pre>
<p>or use classic Automountd. Remember to provide explicit <code>config=...,cache-dir=...</code> as a workaround for mount units being run without <code>HOME</code>.</p>
<p>Rclone in the mount helper mode will split <code>-o</code> argument(s) by comma, replace <code>_</code> by <code>-</code> and prepend <code>--</code> to get the command-line flags. Options containing commas or spaces can be wrapped in single or double quotes. Any inner quotes inside outer quotes of the same type should be doubled.</p>
<p>Mount option syntax includes a few extra options treated specially:</p>
<ul>
<li><code>env.NAME=VALUE</code> will set an environment variable for the mount process. This helps with Automountd and Systemd.mount which don't allow setting custom environment for mount helpers. Typically you will use <code>env.HTTPS_PROXY=proxy.host:3128</code> or <code>env.HOME=/root</code></li>
<li><code>command=cmount</code> can be used to run <code>cmount</code> or any other rclone command rather than the default <code>mount</code>.</li>
<li><code>args2env</code> will pass mount options to the mount helper running in background via environment variables instead of command line arguments. This allows to hide secrets from such commands as <code>ps</code> or <code>pgrep</code>.</li>
<li><code>vv...</code> will be transformed into appropriate <code>--verbose=N</code></li>
<li>standard mount options like <code>x-systemd.automount</code>, <code>_netdev</code>, <code>nosuid</code> and alike are intended only for Automountd and ignored by rclone.</li>
</ul>
<h2 id="vfs---virtual-file-system-1">VFS - Virtual File System</h2>
<p>This command uses the VFS layer. This adapts the cloud storage objects that rclone uses into something which looks much more like a disk filing system.</p>
<p>Cloud storage objects have lots of properties which aren't like disk files - you can't extend them or write to the middle of them, so the VFS layer has to deal with that. Because there is no one right way of doing this there are various options explained below.</p>
<p>The VFS layer also implements a directory cache - this caches info about files and directories (but not the data) in memory.</p>
<h2 id="vfs-directory-cache-1">VFS Directory Cache</h2>
<p>Using the <code>--dir-cache-time</code> flag, you can control how long a directory should be considered up to date and not refreshed from the backend. Changes made through the VFS will appear immediately or invalidate the cache.</p>
<pre><code>--dir-cache-time duration   Time to cache directory entries for (default 5m0s)
--poll-interval duration    Time to wait between polling for changes. Must be smaller than dir-cache-time. Only on supported remotes. Set to 0 to disable (default 1m0s)</code></pre>
<p>However, changes made directly on the cloud storage by the web interface or a different copy of rclone will only be picked up once the directory cache expires if the backend configured does not support polling for changes. If the backend supports polling, changes will be picked up within the polling interval.</p>
<p>You can send a <code>SIGHUP</code> signal to rclone for it to flush all directory caches, regardless of how old they are. Assuming only one rclone instance is running, you can reset the cache like this:</p>
<pre><code>kill -SIGHUP $(pidof rclone)</code></pre>
<p>If you configure rclone with a <a href="/rc">remote control</a> then you can use rclone rc to flush the whole directory cache:</p>
<pre><code>rclone rc vfs/forget</code></pre>
<p>Or individual files or directories:</p>
<pre><code>rclone rc vfs/forget file=path/to/file dir=path/to/dir</code></pre>
<h2 id="vfs-file-buffering-1">VFS File Buffering</h2>
<p>The <code>--buffer-size</code> flag determines the amount of memory, that will be used to buffer data in advance.</p>
<p>Each open file will try to keep the specified amount of data in memory at all times. The buffered data is bound to one open file and won't be shared.</p>
<p>This flag is a upper limit for the used memory per open file. The buffer will only use memory for data that is downloaded but not not yet read. If the buffer is empty, only a small amount of memory will be used.</p>
<p>The maximum memory used by rclone for buffering can be up to <code>--buffer-size * open files</code>.</p>
<h2 id="vfs-file-caching-1">VFS File Caching</h2>
<p>These flags control the VFS file caching options. File caching is necessary to make the VFS layer appear compatible with a normal file system. It can be disabled at the cost of some compatibility.</p>
<p>For example you'll need to enable VFS caching if you want to read and write simultaneously to a file. See below for more details.</p>
<p>Note that the VFS cache is separate from the cache backend and you may find that you need one or the other or both.</p>
<pre><code>--cache-dir string                     Directory rclone will use for caching.
--vfs-cache-mode CacheMode             Cache mode off|minimal|writes|full (default off)
--vfs-cache-max-age duration           Max time since last access of objects in the cache (default 1h0m0s)
--vfs-cache-max-size SizeSuffix        Max total size of objects in the cache (default off)
--vfs-cache-min-free-space SizeSuffix  Target minimum free space on the disk containing the cache (default off)
--vfs-cache-poll-interval duration     Interval to poll the cache for stale objects (default 1m0s)
--vfs-write-back duration              Time to writeback files after last use when using cache (default 5s)</code></pre>
<p>If run with <code>-vv</code> rclone will print the location of the file cache. The files are stored in the user cache file area which is OS dependent but can be controlled with <code>--cache-dir</code> or setting the appropriate environment variable.</p>
<p>The cache has 4 different modes selected by <code>--vfs-cache-mode</code>. The higher the cache mode the more compatible rclone becomes at the cost of using disk space.</p>
<p>Note that files are written back to the remote only when they are closed and if they haven't been accessed for <code>--vfs-write-back</code> seconds. If rclone is quit or dies with files that haven't been uploaded, these will be uploaded next time rclone is run with the same flags.</p>
<p>If using <code>--vfs-cache-max-size</code> or <code>--vfs-cache-min-free-size</code> note that the cache may exceed these quotas for two reasons. Firstly because it is only checked every <code>--vfs-cache-poll-interval</code>. Secondly because open files cannot be evicted from the cache. When <code>--vfs-cache-max-size</code> or <code>--vfs-cache-min-free-size</code> is exceeded, rclone will attempt to evict the least accessed files from the cache first. rclone will start with files that haven't been accessed for the longest. This cache flushing strategy is efficient and more relevant files are likely to remain cached.</p>
<p>The <code>--vfs-cache-max-age</code> will evict files from the cache after the set time since last access has passed. The default value of 1 hour will start evicting files from cache that haven't been accessed for 1 hour. When a cached file is accessed the 1 hour timer is reset to 0 and will wait for 1 more hour before evicting. Specify the time with standard notation, s, m, h, d, w .</p>
<p>You <strong>should not</strong> run two copies of rclone using the same VFS cache with the same or overlapping remotes if using <code>--vfs-cache-mode &gt; off</code>. This can potentially cause data corruption if you do. You can work around this by giving each rclone its own cache hierarchy with <code>--cache-dir</code>. You don't need to worry about this if the remotes in use don't overlap.</p>
<h3 id="vfs-cache-mode-off-1">--vfs-cache-mode off</h3>
<p>In this mode (the default) the cache will read directly from the remote and write directly to the remote without caching anything on disk.</p>
<p>This will mean some operations are not possible</p>
<ul>
<li>Files can't be opened for both read AND write</li>
<li>Files opened for write can't be seeked</li>
<li>Existing files opened for write must have O_TRUNC set</li>
<li>Files open for read with O_TRUNC will be opened write only</li>
<li>Files open for write only will behave as if O_TRUNC was supplied</li>
<li>Open modes O_APPEND, O_TRUNC are ignored</li>
<li>If an upload fails it can't be retried</li>
</ul>
<h3 id="vfs-cache-mode-minimal-1">--vfs-cache-mode minimal</h3>
<p>This is very similar to "off" except that files opened for read AND write will be buffered to disk. This means that files opened for write will be a lot more compatible, but uses the minimal disk space.</p>
<p>These operations are not possible</p>
<ul>
<li>Files opened for write only can't be seeked</li>
<li>Existing files opened for write must have O_TRUNC set</li>
<li>Files opened for write only will ignore O_APPEND, O_TRUNC</li>
<li>If an upload fails it can't be retried</li>
</ul>
<h3 id="vfs-cache-mode-writes-1">--vfs-cache-mode writes</h3>
<p>In this mode files opened for read only are still read directly from the remote, write only and read/write files are buffered to disk first.</p>
<p>This mode should support all normal file system operations.</p>
<p>If an upload fails it will be retried at exponentially increasing intervals up to 1 minute.</p>
<h3 id="vfs-cache-mode-full-1">--vfs-cache-mode full</h3>
<p>In this mode all reads and writes are buffered to and from disk. When data is read from the remote this is buffered to disk as well.</p>
<p>In this mode the files in the cache will be sparse files and rclone will keep track of which bits of the files it has downloaded.</p>
<p>So if an application only reads the starts of each file, then rclone will only buffer the start of the file. These files will appear to be their full size in the cache, but they will be sparse files with only the data that has been downloaded present in them.</p>
<p>This mode should support all normal file system operations and is otherwise identical to <code>--vfs-cache-mode</code> writes.</p>
<p>When reading a file rclone will read <code>--buffer-size</code> plus <code>--vfs-read-ahead</code> bytes ahead. The <code>--buffer-size</code> is buffered in memory whereas the <code>--vfs-read-ahead</code> is buffered on disk.</p>
<p>When using this mode it is recommended that <code>--buffer-size</code> is not set too large and <code>--vfs-read-ahead</code> is set large if required.</p>
<p><strong>IMPORTANT</strong> not all file systems support sparse files. In particular FAT/exFAT do not. Rclone will perform very badly if the cache directory is on a filesystem which doesn't support sparse files and it will log an ERROR message if one is detected.</p>
<h3 id="fingerprinting-1">Fingerprinting</h3>
<p>Various parts of the VFS use fingerprinting to see if a local file copy has changed relative to a remote file. Fingerprints are made from:</p>
<ul>
<li>size</li>
<li>modification time</li>
<li>hash</li>
</ul>
<p>where available on an object.</p>
<p>On some backends some of these attributes are slow to read (they take an extra API call per object, or extra work per object).</p>
<p>For example <code>hash</code> is slow with the <code>local</code> and <code>sftp</code> backends as they have to read the entire file and hash it, and <code>modtime</code> is slow with the <code>s3</code>, <code>swift</code>, <code>ftp</code> and <code>qinqstor</code> backends because they need to do an extra API call to fetch it.</p>
<p>If you use the <code>--vfs-fast-fingerprint</code> flag then rclone will not include the slow operations in the fingerprint. This makes the fingerprinting less accurate but much faster and will improve the opening time of cached files.</p>
<p>If you are running a vfs cache over <code>local</code>, <code>s3</code> or <code>swift</code> backends then using this flag is recommended.</p>
<p>Note that if you change the value of this flag, the fingerprints of the files in the cache may be invalidated and the files will need to be downloaded again.</p>
<h2 id="vfs-chunked-reading-1">VFS Chunked Reading</h2>
<p>When rclone reads files from a remote it reads them in chunks. This means that rather than requesting the whole file rclone reads the chunk specified. This can reduce the used download quota for some remotes by requesting only chunks from the remote that are actually read, at the cost of an increased number of requests.</p>
<p>These flags control the chunking:</p>
<pre><code>--vfs-read-chunk-size SizeSuffix        Read the source objects in chunks (default 128M)
--vfs-read-chunk-size-limit SizeSuffix  Max chunk doubling size (default off)
--vfs-read-chunk-streams int            The number of parallel streams to read at once</code></pre>
<p>The chunking behaves differently depending on the <code>--vfs-read-chunk-streams</code> parameter.</p>
<h3 id="vfs-read-chunk-streams-0-2"><code>--vfs-read-chunk-streams</code> == 0</h3>
<p>Rclone will start reading a chunk of size <code>--vfs-read-chunk-size</code>, and then double the size for each read. When <code>--vfs-read-chunk-size-limit</code> is specified, and greater than <code>--vfs-read-chunk-size</code>, the chunk size for each open file will get doubled only until the specified value is reached. If the value is "off", which is the default, the limit is disabled and the chunk size will grow indefinitely.</p>
<p>With <code>--vfs-read-chunk-size 100M</code> and <code>--vfs-read-chunk-size-limit 0</code> the following parts will be downloaded: 0-100M, 100M-200M, 200M-300M, 300M-400M and so on. When <code>--vfs-read-chunk-size-limit 500M</code> is specified, the result would be 0-100M, 100M-300M, 300M-700M, 700M-1200M, 1200M-1700M and so on.</p>
<p>Setting <code>--vfs-read-chunk-size</code> to <code>0</code> or "off" disables chunked reading.</p>
<p>The chunks will not be buffered in memory.</p>
<h3 id="vfs-read-chunk-streams-0-3"><code>--vfs-read-chunk-streams</code> &gt; 0</h3>
<p>Rclone reads <code>--vfs-read-chunk-streams</code> chunks of size <code>--vfs-read-chunk-size</code> concurrently. The size for each read will stay constant.</p>
<p>This improves performance performance massively on high latency links or very high bandwidth links to high performance object stores.</p>
<p>Some experimentation will be needed to find the optimum values of <code>--vfs-read-chunk-size</code> and <code>--vfs-read-chunk-streams</code> as these will depend on the backend in use and the latency to the backend.</p>
<p>For high performance object stores (eg AWS S3) a reasonable place to start might be <code>--vfs-read-chunk-streams 16</code> and <code>--vfs-read-chunk-size 4M</code>. In testing with AWS S3 the performance scaled roughly as the <code>--vfs-read-chunk-streams</code> setting.</p>
<p>Similar settings should work for high latency links, but depending on the latency they may need more <code>--vfs-read-chunk-streams</code> in order to get the throughput.</p>
<h2 id="vfs-performance-1">VFS Performance</h2>
<p>These flags may be used to enable/disable features of the VFS for performance or other reasons. See also the <a href="#vfs-chunked-reading">chunked reading</a> feature.</p>
<p>In particular S3 and Swift benefit hugely from the <code>--no-modtime</code> flag (or use <code>--use-server-modtime</code> for a slightly different effect) as each read of the modification time takes a transaction.</p>
<pre><code>--no-checksum     Don&#39;t compare checksums on up/download.
--no-modtime      Don&#39;t read/write the modification time (can speed things up).
--no-seek         Don&#39;t allow seeking in files.
--read-only       Only allow read-only access.</code></pre>
<p>Sometimes rclone is delivered reads or writes out of order. Rather than seeking rclone will wait a short time for the in sequence read or write to come in. These flags only come into effect when not using an on disk cache file.</p>
<pre><code>--vfs-read-wait duration   Time to wait for in-sequence read before seeking (default 20ms)
--vfs-write-wait duration  Time to wait for in-sequence write before giving error (default 1s)</code></pre>
<p>When using VFS write caching (<code>--vfs-cache-mode</code> with value writes or full), the global flag <code>--transfers</code> can be set to adjust the number of parallel uploads of modified files from the cache (the related global flag <code>--checkers</code> has no effect on the VFS).</p>
<pre><code>--transfers int  Number of file transfers to run in parallel (default 4)</code></pre>
<h2 id="vfs-case-sensitivity-1">VFS Case Sensitivity</h2>
<p>Linux file systems are case-sensitive: two files can differ only by case, and the exact case must be used when opening a file.</p>
<p>File systems in modern Windows are case-insensitive but case-preserving: although existing files can be opened using any case, the exact case used to create the file is preserved and available for programs to query. It is not allowed for two files in the same directory to differ only by case.</p>
<p>Usually file systems on macOS are case-insensitive. It is possible to make macOS file systems case-sensitive but that is not the default.</p>
<p>The <code>--vfs-case-insensitive</code> VFS flag controls how rclone handles these two cases. If its value is "false", rclone passes file names to the remote as-is. If the flag is "true" (or appears without a value on the command line), rclone may perform a "fixup" as explained below.</p>
<p>The user may specify a file name to open/delete/rename/etc with a case different than what is stored on the remote. If an argument refers to an existing file with exactly the same name, then the case of the existing file on the disk will be used. However, if a file name with exactly the same name is not found but a name differing only by case exists, rclone will transparently fixup the name. This fixup happens only when an existing file is requested. Case sensitivity of file names created anew by rclone is controlled by the underlying remote.</p>
<p>Note that case sensitivity of the operating system running rclone (the target) may differ from case sensitivity of a file system presented by rclone (the source). The flag controls whether "fixup" is performed to satisfy the target.</p>
<p>If the flag is not provided on the command line, then its default value depends on the operating system where rclone runs: "true" on Windows and macOS, "false" otherwise. If the flag is provided without a value, then it is "true".</p>
<p>The <code>--no-unicode-normalization</code> flag controls whether a similar "fixup" is performed for filenames that differ but are <a href="https://en.wikipedia.org/wiki/Unicode_equivalence">canonically equivalent</a> with respect to unicode. Unicode normalization can be particularly helpful for users of macOS, which prefers form NFD instead of the NFC used by most other platforms. It is therefore highly recommended to keep the default of <code>false</code> on macOS, to avoid encoding compatibility issues.</p>
<p>In the (probably unlikely) event that a directory has multiple duplicate filenames after applying case and unicode normalization, the <code>--vfs-block-norm-dupes</code> flag allows hiding these duplicates. This comes with a performance tradeoff, as rclone will have to scan the entire directory for duplicates when listing a directory. For this reason, it is recommended to leave this disabled if not needed. However, macOS users may wish to consider using it, as otherwise, if a remote directory contains both NFC and NFD versions of the same filename, an odd situation will occur: both versions of the file will be visible in the mount, and both will appear to be editable, however, editing either version will actually result in only the NFD version getting edited under the hood. <code>--vfs-block- norm-dupes</code> prevents this confusion by detecting this scenario, hiding the duplicates, and logging an error, similar to how this is handled in <code>rclone sync</code>.</p>
<h2 id="vfs-disk-options-1">VFS Disk Options</h2>
<p>This flag allows you to manually set the statistics about the filing system. It can be useful when those statistics cannot be read correctly automatically.</p>
<pre><code>--vfs-disk-space-total-size    Manually set the total disk space size (example: 256G, default: -1)</code></pre>
<h2 id="alternate-report-of-used-bytes-1">Alternate report of used bytes</h2>
<p>Some backends, most notably S3, do not report the amount of bytes used. If you need this information to be available when running <code>df</code> on the filesystem, then pass the flag <code>--vfs-used-is-size</code> to rclone. With this flag set, instead of relying on the backend to report this information, rclone will scan the whole remote similar to <code>rclone size</code> and compute the total used space itself.</p>
<p><em>WARNING.</em> Contrary to <code>rclone size</code>, this flag ignores filters so that the result is accurate. However, this is very inefficient and may cost lots of API calls resulting in extra charges. Use it as a last resort and only with caching.</p>
<pre><code>rclone nfsmount remote:path /path/to/mountpoint [flags]</code></pre>
<h2 id="options-63">Options</h2>
<pre><code>      --addr string                            IPaddress:Port or :Port to bind server to
      --allow-non-empty                        Allow mounting over a non-empty directory (not supported on Windows)
      --allow-other                            Allow access to other users (not supported on Windows)
      --allow-root                             Allow access to root user (not supported on Windows)
      --async-read                             Use asynchronous reads (not supported on Windows) (default true)
      --attr-timeout Duration                  Time for which file/directory attributes are cached (default 1s)
      --daemon                                 Run mount in background and exit parent process (as background output is suppressed, use --log-file with --log-format=pid,... to monitor) (not supported on Windows)
      --daemon-timeout Duration                Time limit for rclone to respond to kernel (not supported on Windows) (default 0s)
      --daemon-wait Duration                   Time to wait for ready mount from daemon (maximum time on Linux, constant sleep time on OSX/BSD) (not supported on Windows) (default 1m0s)
      --debug-fuse                             Debug the FUSE internals - needs -v
      --default-permissions                    Makes kernel enforce access control based on the file mode (not supported on Windows)
      --devname string                         Set the device name - default is remote:path
      --dir-cache-time Duration                Time to cache directory entries for (default 5m0s)
      --dir-perms FileMode                     Directory permissions (default 777)
      --direct-io                              Use Direct IO, disables caching of data
      --file-perms FileMode                    File permissions (default 666)
      --fuse-flag stringArray                  Flags or arguments to be passed direct to libfuse/WinFsp (repeat if required)
      --gid uint32                             Override the gid field set by the filesystem (not supported on Windows) (default 1000)
  -h, --help                                   help for nfsmount
      --max-read-ahead SizeSuffix              The number of bytes that can be prefetched for sequential reads (not supported on Windows) (default 128Ki)
      --mount-case-insensitive Tristate        Tell the OS the mount is case insensitive (true) or sensitive (false) regardless of the backend (auto) (default unset)
      --network-mode                           Mount as remote network drive, instead of fixed disk drive (supported on Windows only)
      --nfs-cache-dir string                   The directory the NFS handle cache will use if set
      --nfs-cache-handle-limit int             max file handles cached simultaneously (min 5) (default 1000000)
      --nfs-cache-type memory|disk|symlink     Type of NFS handle cache to use (default memory)
      --no-checksum                            Don&#39;t compare checksums on up/download
      --no-modtime                             Don&#39;t read/write the modification time (can speed things up)
      --no-seek                                Don&#39;t allow seeking in files
      --noappledouble                          Ignore Apple Double (._) and .DS_Store files (supported on OSX only) (default true)
      --noapplexattr                           Ignore all &quot;com.apple.*&quot; extended attributes (supported on OSX only)
  -o, --option stringArray                     Option for libfuse/WinFsp (repeat if required)
      --poll-interval Duration                 Time to wait between polling for changes, must be smaller than dir-cache-time and only on supported remotes (set 0 to disable) (default 1m0s)
      --read-only                              Only allow read-only access
      --sudo                                   Use sudo to run the mount/umount commands as root.
      --uid uint32                             Override the uid field set by the filesystem (not supported on Windows) (default 1000)
      --umask FileMode                         Override the permission bits set by the filesystem (not supported on Windows) (default 002)
      --vfs-block-norm-dupes                   If duplicate filenames exist in the same directory (after normalization), log an error and hide the duplicates (may have a performance cost)
      --vfs-cache-max-age Duration             Max time since last access of objects in the cache (default 1h0m0s)
      --vfs-cache-max-size SizeSuffix          Max total size of objects in the cache (default off)
      --vfs-cache-min-free-space SizeSuffix    Target minimum free space on the disk containing the cache (default off)
      --vfs-cache-mode CacheMode               Cache mode off|minimal|writes|full (default off)
      --vfs-cache-poll-interval Duration       Interval to poll the cache for stale objects (default 1m0s)
      --vfs-case-insensitive                   If a file name not found, find a case insensitive match
      --vfs-disk-space-total-size SizeSuffix   Specify the total space of disk (default off)
      --vfs-fast-fingerprint                   Use fast (less accurate) fingerprints for change detection
      --vfs-read-ahead SizeSuffix              Extra read ahead over --buffer-size when using cache-mode full
      --vfs-read-chunk-size SizeSuffix         Read the source objects in chunks (default 128Mi)
      --vfs-read-chunk-size-limit SizeSuffix   If greater than --vfs-read-chunk-size, double the chunk size after each chunk read, until the limit is reached (&#39;off&#39; is unlimited) (default off)
      --vfs-read-chunk-streams int             The number of parallel streams to read at once
      --vfs-read-wait Duration                 Time to wait for in-sequence read before seeking (default 20ms)
      --vfs-refresh                            Refreshes the directory cache recursively in the background on start
      --vfs-used-is-size rclone size           Use the rclone size algorithm for Used size
      --vfs-write-back Duration                Time to writeback files after last use when using cache (default 5s)
      --vfs-write-wait Duration                Time to wait for in-sequence write before giving error (default 1s)
      --volname string                         Set the volume name (supported on Windows and OSX only)
      --write-back-cache                       Makes kernel buffer writes before sending them to rclone (without this, writethrough caching is used) (not supported on Windows)</code></pre>
<p>Options shared with other commands are described next. See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
<h3 id="filter-options-22">Filter Options</h3>
<p>Flags for filtering directory listings</p>
<pre><code>      --delete-excluded                     Delete files on dest excluded from sync
      --exclude stringArray                 Exclude files matching pattern
      --exclude-from stringArray            Read file exclude patterns from file (use - to read from stdin)
      --exclude-if-present stringArray      Exclude directories if filename is present
      --files-from stringArray              Read list of source-file names from file (use - to read from stdin)
      --files-from-raw stringArray          Read list of source-file names from file without any processing of lines (use - to read from stdin)
  -f, --filter stringArray                  Add a file filtering rule
      --filter-from stringArray             Read file filtering patterns from a file (use - to read from stdin)
      --ignore-case                         Ignore case in filters (case insensitive)
      --include stringArray                 Include files matching pattern
      --include-from stringArray            Read file include patterns from file (use - to read from stdin)
      --max-age Duration                    Only transfer files younger than this in s or suffix ms|s|m|h|d|w|M|y (default off)
      --max-depth int                       If set limits the recursion depth to this (default -1)
      --max-size SizeSuffix                 Only transfer files smaller than this in KiB or suffix B|K|M|G|T|P (default off)
      --metadata-exclude stringArray        Exclude metadatas matching pattern
      --metadata-exclude-from stringArray   Read metadata exclude patterns from file (use - to read from stdin)
      --metadata-filter stringArray         Add a metadata filtering rule
      --metadata-filter-from stringArray    Read metadata filtering patterns from a file (use - to read from stdin)
      --metadata-include stringArray        Include metadatas matching pattern
      --metadata-include-from stringArray   Read metadata include patterns from file (use - to read from stdin)
      --min-age Duration                    Only transfer files older than this in s or suffix ms|s|m|h|d|w|M|y (default off)
      --min-size SizeSuffix                 Only transfer files bigger than this in KiB or suffix B|K|M|G|T|P (default off)</code></pre>
<h2 id="see-also-63">See Also</h2>
<ul>
<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
</ul>
<h1 id="rclone-obscure">rclone obscure</h1>
<p>Obscure password for use in the rclone config file.</p>
<h2 id="synopsis-56">Synopsis</h2>
<p>In the rclone config file, human-readable passwords are obscured. Obscuring them is done by encrypting them and writing them out in base64. This is <strong>not</strong> a secure way of encrypting these passwords as rclone can decrypt them - it is to prevent "eyedropping" - namely someone seeing a password in the rclone config file by accident.</p>
<p>Many equally important things (like access tokens) are not obscured in the config file. However it is very hard to shoulder surf a 64 character hex token.</p>
<p>This command can also accept a password through STDIN instead of an argument by passing a hyphen as an argument. This will use the first line of STDIN as the password not including the trailing newline.</p>
<pre><code>echo &quot;secretpassword&quot; | rclone obscure -</code></pre>
<p>If there is no data on STDIN to read, rclone obscure will default to obfuscating the hyphen itself.</p>
<p>If you want to encrypt the config file then please use config file encryption - see <a href="https://rclone.org/commands/rclone_config/">rclone config</a> for more info.</p>
<pre><code>rclone obscure password [flags]</code></pre>
<h2 id="options-64">Options</h2>
<pre><code>  -h, --help   help for obscure</code></pre>
<p>See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
<h2 id="see-also-64">See Also</h2>
<ul>
<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
</ul>
<h1 id="rclone-rc">rclone rc</h1>
<p>Run a command against a running rclone.</p>
<h2 id="synopsis-57">Synopsis</h2>
<p>This runs a command against a running rclone. Use the <code>--url</code> flag to specify an non default URL to connect on. This can be either a ":port" which is taken to mean "http://localhost:port" or a "host:port" which is taken to mean "http://host:port"</p>
<p>A username and password can be passed in with <code>--user</code> and <code>--pass</code>.</p>
<p>Note that <code>--rc-addr</code>, <code>--rc-user</code>, <code>--rc-pass</code> will be read also for <code>--url</code>, <code>--user</code>, <code>--pass</code>.</p>
<p>The <code>--unix-socket</code> flag can be used to connect over a unix socket like this</p>
<pre><code># start server on /tmp/my.socket
rclone rcd --rc-addr unix:///tmp/my.socket
# Connect to it
rclone rc --unix-socket /tmp/my.socket core/stats</code></pre>
<p>Arguments should be passed in as parameter=value.</p>
<p>The result will be returned as a JSON object by default.</p>
<p>The <code>--json</code> parameter can be used to pass in a JSON blob as an input instead of key=value arguments. This is the only way of passing in more complicated values.</p>
<p>The <code>-o</code>/<code>--opt</code> option can be used to set a key "opt" with key, value options in the form <code>-o key=value</code> or <code>-o key</code>. It can be repeated as many times as required. This is useful for rc commands which take the "opt" parameter which by convention is a dictionary of strings.</p>
<pre><code>-o key=value -o key2</code></pre>
<p>Will place this in the "opt" value</p>
<pre><code>{&quot;key&quot;:&quot;value&quot;, &quot;key2&quot;,&quot;&quot;)</code></pre>
<p>The <code>-a</code>/<code>--arg</code> option can be used to set strings in the "arg" value. It can be repeated as many times as required. This is useful for rc commands which take the "arg" parameter which by convention is a list of strings.</p>
<pre><code>-a value -a value2</code></pre>
<p>Will place this in the "arg" value</p>
<pre><code>[&quot;value&quot;, &quot;value2&quot;]</code></pre>
<p>Use <code>--loopback</code> to connect to the rclone instance running <code>rclone rc</code>. This is very useful for testing commands without having to run an rclone rc server, e.g.:</p>
<pre><code>rclone rc --loopback operations/about fs=/</code></pre>
<p>Use <code>rclone rc</code> to see a list of all possible commands.</p>
<pre><code>rclone rc commands parameter [flags]</code></pre>
<h2 id="options-65">Options</h2>
<pre><code>  -a, --arg stringArray      Argument placed in the &quot;arg&quot; array
  -h, --help                 help for rc
      --json string          Input JSON - use instead of key=value args
      --loopback             If set connect to this rclone instance not via HTTP
      --no-output            If set, don&#39;t output the JSON result
  -o, --opt stringArray      Option in the form name=value or name placed in the &quot;opt&quot; array
      --pass string          Password to use to connect to rclone remote control
      --unix-socket string   Path to a unix domain socket to dial to, instead of opening a TCP connection directly
      --url string           URL to connect to rclone remote control (default &quot;http://localhost:5572/&quot;)
      --user string          Username to use to rclone remote control</code></pre>
<p>See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
<h2 id="see-also-65">See Also</h2>
<ul>
<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
</ul>
<h1 id="rclone-rcat">rclone rcat</h1>
<p>Copies standard input to file on remote.</p>
<h2 id="synopsis-58">Synopsis</h2>
<p>Reads from standard input (stdin) and copies it to a single remote file.</p>
<pre><code>echo &quot;hello world&quot; | rclone rcat remote:path/to/file
ffmpeg - | rclone rcat remote:path/to/file</code></pre>
<p>If the remote file already exists, it will be overwritten.</p>
<p>rcat will try to upload small files in a single request, which is usually more efficient than the streaming/chunked upload endpoints, which use multiple requests. Exact behaviour depends on the remote. What is considered a small file may be set through <code>--streaming-upload-cutoff</code>. Uploading only starts after the cutoff is reached or if the file ends before that. The data must fit into RAM. The cutoff needs to be small enough to adhere the limits of your remote, please see there. Generally speaking, setting this cutoff too high will decrease your performance.</p>
<p>Use the <code>--size</code> flag to preallocate the file in advance at the remote end and actually stream it, even if remote backend doesn't support streaming.</p>
<p><code>--size</code> should be the exact size of the input stream in bytes. If the size of the stream is different in length to the <code>--size</code> passed in then the transfer will likely fail.</p>
<p>Note that the upload cannot be retried because the data is not stored. If the backend supports multipart uploading then individual chunks can be retried. If you need to transfer a lot of data, you may be better off caching it locally and then <code>rclone move</code> it to the destination which can use retries.</p>
<pre><code>rclone rcat remote:path [flags]</code></pre>
<h2 id="options-66">Options</h2>
<pre><code>  -h, --help       help for rcat
      --size int   File size hint to preallocate (default -1)</code></pre>
<p>Options shared with other commands are described next. See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
<h3 id="important-options-15">Important Options</h3>
<p>Important flags useful for most commands</p>
<pre><code>  -n, --dry-run         Do a trial run with no permanent changes
  -i, --interactive     Enable interactive mode
  -v, --verbose count   Print lots more stuff (repeat for more)</code></pre>
<h2 id="see-also-66">See Also</h2>
<ul>
<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
</ul>
<h1 id="rclone-rcd">rclone rcd</h1>
<p>Run rclone listening to remote control commands only.</p>
<h2 id="synopsis-59">Synopsis</h2>
<p>This runs rclone so that it only listens to remote control commands.</p>
<p>This is useful if you are controlling rclone via the rc API.</p>
<p>If you pass in a path to a directory, rclone will serve that directory for GET requests on the URL passed in. It will also open the URL in the browser when rclone is run.</p>
<p>See the <a href="https://rclone.org/rc/">rc documentation</a> for more info on the rc flags.</p>
<h2 id="server-options">Server options</h2>
<p>Use <code>--rc-addr</code> to specify which IP address and port the server should listen on, eg <code>--rc-addr 1.2.3.4:8000</code> or <code>--rc-addr :8080</code> to listen to all IPs. By default it only listens on localhost. You can use port :0 to let the OS choose an available port.</p>
<p>If you set <code>--rc-addr</code> to listen on a public or LAN accessible IP address then using Authentication is advised - see the next section for info.</p>
<p>You can use a unix socket by setting the url to <code>unix:///path/to/socket</code> or just by using an absolute path name. Note that unix sockets bypass the authentication - this is expected to be done with file system permissions.</p>
<p><code>--rc-addr</code> may be repeated to listen on multiple IPs/ports/sockets. Socket activation, described further below, can also be used to accomplish the same.</p>
<p><code>--rc-server-read-timeout</code> and <code>--rc-server-write-timeout</code> can be used to control the timeouts on the server. Note that this is the total time for a transfer.</p>
<p><code>--rc-max-header-bytes</code> controls the maximum number of bytes the server will accept in the HTTP header.</p>
<p><code>--rc-baseurl</code> controls the URL prefix that rclone serves from. By default rclone will serve from the root. If you used <code>--rc-baseurl "/rclone"</code> then rclone would serve from a URL starting with "/rclone/". This is useful if you wish to proxy rclone serve. Rclone automatically inserts leading and trailing "/" on <code>--rc-baseurl</code>, so <code>--rc-baseurl "rclone"</code>, <code>--rc-baseurl "/rclone"</code> and <code>--rc-baseurl "/rclone/"</code> are all treated identically.</p>
<h3 id="tls-ssl">TLS (SSL)</h3>
<p>By default this will serve over http. If you want you can serve over https. You will need to supply the <code>--rc-cert</code> and <code>--rc-key</code> flags. If you wish to do client side certificate validation then you will need to supply <code>--rc-client-ca</code> also.</p>
<p><code>--rc-cert</code> should be a either a PEM encoded certificate or a concatenation of that with the CA certificate. <code>--krc-ey</code> should be the PEM encoded private key and <code>--rc-client-ca</code> should be the PEM encoded client certificate authority certificate.</p>
<p><code>--rc-min-tls-version</code> is minimum TLS version that is acceptable. Valid values are "tls1.0", "tls1.1", "tls1.2" and "tls1.3" (default "tls1.0").</p>
<h2 id="socket-activation">Socket activation</h2>
<p>Instead of the listening addresses specified above, rclone will listen to all FDs passed by the service manager, if any (and ignore any arguments passed by --rc-addr`).</p>
<p>This allows rclone to be a socket-activated service. It can be configured with .socket and .service unit files as described in https://www.freedesktop.org/software/systemd/man/latest/systemd.socket.html</p>
<p>Socket activation can be tested ad-hoc with the <code>systemd-socket-activate</code>command</p>
<pre><code>   systemd-socket-activate -l 8000 -- rclone serve</code></pre>
<p>This will socket-activate rclone on the first connection to port 8000 over TCP. ### Template</p>
<p><code>--rc-template</code> allows a user to specify a custom markup template for HTTP and WebDAV serve functions. The server exports the following markup to be used within the template to server pages:</p>
<table>
<colgroup>
<col style="width: 50%" />
<col style="width: 50%" />
</colgroup>
<thead>
<tr class="header">
<th style="text-align: left;">Parameter</th>
<th style="text-align: left;">Description</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td style="text-align: left;">.Name</td>
<td style="text-align: left;">The full path of a file/directory.</td>
</tr>
<tr class="even">
<td style="text-align: left;">.Title</td>
<td style="text-align: left;">Directory listing of .Name</td>
</tr>
<tr class="odd">
<td style="text-align: left;">.Sort</td>
<td style="text-align: left;">The current sort used. This is changeable via ?sort= parameter</td>
</tr>
<tr class="even">
<td style="text-align: left;"></td>
<td style="text-align: left;">Sort Options: namedirfirst,name,size,time (default namedirfirst)</td>
</tr>
<tr class="odd">
<td style="text-align: left;">.Order</td>
<td style="text-align: left;">The current ordering used. This is changeable via ?order= parameter</td>
</tr>
<tr class="even">
<td style="text-align: left;"></td>
<td style="text-align: left;">Order Options: asc,desc (default asc)</td>
</tr>
<tr class="odd">
<td style="text-align: left;">.Query</td>
<td style="text-align: left;">Currently unused.</td>
</tr>
<tr class="even">
<td style="text-align: left;">.Breadcrumb</td>
<td style="text-align: left;">Allows for creating a relative navigation</td>
</tr>
<tr class="odd">
<td style="text-align: left;">-- .Link</td>
<td style="text-align: left;">The relative to the root link of the Text.</td>
</tr>
<tr class="even">
<td style="text-align: left;">-- .Text</td>
<td style="text-align: left;">The Name of the directory.</td>
</tr>
<tr class="odd">
<td style="text-align: left;">.Entries</td>
<td style="text-align: left;">Information about a specific file/directory.</td>
</tr>
<tr class="even">
<td style="text-align: left;">-- .URL</td>
<td style="text-align: left;">The 'url' of an entry.</td>
</tr>
<tr class="odd">
<td style="text-align: left;">-- .Leaf</td>
<td style="text-align: left;">Currently same as 'URL' but intended to be 'just' the name.</td>
</tr>
<tr class="even">
<td style="text-align: left;">-- .IsDir</td>
<td style="text-align: left;">Boolean for if an entry is a directory or not.</td>
</tr>
<tr class="odd">
<td style="text-align: left;">-- .Size</td>
<td style="text-align: left;">Size in Bytes of the entry.</td>
</tr>
<tr class="even">
<td style="text-align: left;">-- .ModTime</td>
<td style="text-align: left;">The UTC timestamp of an entry.</td>
</tr>
</tbody>
</table>
<p>The server also makes the following functions available so that they can be used within the template. These functions help extend the options for dynamic rendering of HTML. They can be used to render HTML based on specific conditions.</p>
<table>
<colgroup>
<col style="width: 50%" />
<col style="width: 50%" />
</colgroup>
<thead>
<tr class="header">
<th style="text-align: left;">Function</th>
<th style="text-align: left;">Description</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td style="text-align: left;">afterEpoch</td>
<td style="text-align: left;">Returns the time since the epoch for the given time.</td>
</tr>
<tr class="even">
<td style="text-align: left;">contains</td>
<td style="text-align: left;">Checks whether a given substring is present or not in a given string.</td>
</tr>
<tr class="odd">
<td style="text-align: left;">hasPrefix</td>
<td style="text-align: left;">Checks whether the given string begins with the specified prefix.</td>
</tr>
<tr class="even">
<td style="text-align: left;">hasSuffix</td>
<td style="text-align: left;">Checks whether the given string end with the specified suffix.</td>
</tr>
</tbody>
</table>
<h3 id="authentication">Authentication</h3>
<p>By default this will serve files without needing a login.</p>
<p>You can either use an htpasswd file which can take lots of users, or set a single username and password with the <code>--rc-user</code> and <code>--rc-pass</code> flags.</p>
<p>If no static users are configured by either of the above methods, and client certificates are required by the <code>--client-ca</code> flag passed to the server, the client certificate common name will be considered as the username.</p>
<p>Use <code>--rc-htpasswd /path/to/htpasswd</code> to provide an htpasswd file. This is in standard apache format and supports MD5, SHA1 and BCrypt for basic authentication. Bcrypt is recommended.</p>
<p>To create an htpasswd file:</p>
<pre><code>touch htpasswd
htpasswd -B htpasswd user
htpasswd -B htpasswd anotherUser</code></pre>
<p>The password file can be updated while rclone is running.</p>
<p>Use <code>--rc-realm</code> to set the authentication realm.</p>
<p>Use <code>--rc-salt</code> to change the password hashing salt from the default.</p>
<pre><code>rclone rcd &lt;path to files to serve&gt;* [flags]</code></pre>
<h2 id="options-67">Options</h2>
<pre><code>  -h, --help   help for rcd</code></pre>
<p>Options shared with other commands are described next. See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
<h3 id="rc-options">RC Options</h3>
<p>Flags to control the Remote Control API</p>
<pre><code>      --rc                                 Enable the remote control server
      --rc-addr stringArray                IPaddress:Port or :Port to bind server to (default localhost:5572)
      --rc-allow-origin string             Origin which cross-domain request (CORS) can be executed from
      --rc-baseurl string                  Prefix for URLs - leave blank for root
      --rc-cert string                     TLS PEM key (concatenation of certificate and CA certificate)
      --rc-client-ca string                Client certificate authority to verify clients with
      --rc-enable-metrics                  Enable the Prometheus metrics path at the remote control server
      --rc-files string                    Path to local files to serve on the HTTP server
      --rc-htpasswd string                 A htpasswd file - if not provided no authentication is done
      --rc-job-expire-duration Duration    Expire finished async jobs older than this value (default 1m0s)
      --rc-job-expire-interval Duration    Interval to check for expired async jobs (default 10s)
      --rc-key string                      TLS PEM Private key
      --rc-max-header-bytes int            Maximum size of request header (default 4096)
      --rc-min-tls-version string          Minimum TLS version that is acceptable (default &quot;tls1.0&quot;)
      --rc-no-auth                         Don&#39;t require auth for certain methods
      --rc-pass string                     Password for authentication
      --rc-realm string                    Realm for authentication
      --rc-salt string                     Password hashing salt (default &quot;dlPL2MqE&quot;)
      --rc-serve                           Enable the serving of remote objects
      --rc-serve-no-modtime                Don&#39;t read the modification time (can speed things up)
      --rc-server-read-timeout Duration    Timeout for server reading data (default 1h0m0s)
      --rc-server-write-timeout Duration   Timeout for server writing data (default 1h0m0s)
      --rc-template string                 User-specified template
      --rc-user string                     User name for authentication
      --rc-web-fetch-url string            URL to fetch the releases for webgui (default &quot;https://api.github.com/repos/rclone/rclone-webui-react/releases/latest&quot;)
      --rc-web-gui                         Launch WebGUI on localhost
      --rc-web-gui-force-update            Force update to latest version of web gui
      --rc-web-gui-no-open-browser         Don&#39;t open the browser automatically
      --rc-web-gui-update                  Check and update to latest version of web gui</code></pre>
<h2 id="see-also-67">See Also</h2>
<ul>
<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
</ul>
<h1 id="rclone-rmdirs">rclone rmdirs</h1>
<p>Remove empty directories under the path.</p>
<h2 id="synopsis-60">Synopsis</h2>
<p>This recursively removes any empty directories (including directories that only contain empty directories), that it finds under the path. The root path itself will also be removed if it is empty, unless you supply the <code>--leave-root</code> flag.</p>
<p>Use command <a href="https://rclone.org/commands/rclone_rmdir/">rmdir</a> to delete just the empty directory given by path, not recurse.</p>
<p>This is useful for tidying up remotes that rclone has left a lot of empty directories in. For example the <a href="https://rclone.org/commands/rclone_delete/">delete</a> command will delete files but leave the directory structure (unless used with option <code>--rmdirs</code>).</p>
<p>This will delete <code>--checkers</code> directories concurrently so if you have thousands of empty directories consider increasing this number.</p>
<p>To delete a path and any objects in it, use the <a href="https://rclone.org/commands/rclone_purge/">purge</a> command.</p>
<pre><code>rclone rmdirs remote:path [flags]</code></pre>
<h2 id="options-68">Options</h2>
<pre><code>  -h, --help         help for rmdirs
      --leave-root   Do not remove root directory if empty</code></pre>
<p>Options shared with other commands are described next. See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
<h3 id="important-options-16">Important Options</h3>
<p>Important flags useful for most commands</p>
<pre><code>  -n, --dry-run         Do a trial run with no permanent changes
  -i, --interactive     Enable interactive mode
  -v, --verbose count   Print lots more stuff (repeat for more)</code></pre>
<h2 id="see-also-68">See Also</h2>
<ul>
<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
</ul>
<h1 id="rclone-selfupdate">rclone selfupdate</h1>
<p>Update the rclone binary.</p>
<h2 id="synopsis-61">Synopsis</h2>
<p>This command downloads the latest release of rclone and replaces the currently running binary. The download is verified with a hashsum and cryptographically signed signature; see <a href="https://rclone.org/release_signing/">the release signing docs</a> for details.</p>
<p>If used without flags (or with implied <code>--stable</code> flag), this command will install the latest stable release. However, some issues may be fixed (or features added) only in the latest beta release. In such cases you should run the command with the <code>--beta</code> flag, i.e. <code>rclone selfupdate --beta</code>. You can check in advance what version would be installed by adding the <code>--check</code> flag, then repeat the command without it when you are satisfied.</p>
<p>Sometimes the rclone team may recommend you a concrete beta or stable rclone release to troubleshoot your issue or add a bleeding edge feature. The <code>--version VER</code> flag, if given, will update to the concrete version instead of the latest one. If you omit micro version from <code>VER</code> (for example <code>1.53</code>), the latest matching micro version will be used.</p>
<p>Upon successful update rclone will print a message that contains a previous version number. You will need it if you later decide to revert your update for some reason. Then you'll have to note the previous version and run the following command: <code>rclone selfupdate [--beta] OLDVER</code>. If the old version contains only dots and digits (for example <code>v1.54.0</code>) then it's a stable release so you won't need the <code>--beta</code> flag. Beta releases have an additional information similar to <code>v1.54.0-beta.5111.06f1c0c61</code>. (if you are a developer and use a locally built rclone, the version number will end with <code>-DEV</code>, you will have to rebuild it as it obviously can't be distributed).</p>
<p>If you previously installed rclone via a package manager, the package may include local documentation or configure services. You may wish to update with the flag <code>--package deb</code> or <code>--package rpm</code> (whichever is correct for your OS) to update these too. This command with the default <code>--package zip</code> will update only the rclone executable so the local manual may become inaccurate after it.</p>
<p>The <a href="https://rclone.org/commands/rclone_mount/">rclone mount</a> command may or may not support extended FUSE options depending on the build and OS. <code>selfupdate</code> will refuse to update if the capability would be discarded.</p>
<p>Note: Windows forbids deletion of a currently running executable so this command will rename the old executable to 'rclone.old.exe' upon success.</p>
<p>Please note that this command was not available before rclone version 1.55. If it fails for you with the message <code>unknown command "selfupdate"</code> then you will need to update manually following the install instructions located at https://rclone.org/install/</p>
<pre><code>rclone selfupdate [flags]</code></pre>
<h2 id="options-69">Options</h2>
<pre><code>      --beta             Install beta release
      --check            Check for latest release, do not download
  -h, --help             help for selfupdate
      --output string    Save the downloaded binary at a given path (default: replace running binary)
      --package string   Package format: zip|deb|rpm (default: zip)
      --stable           Install stable release (this is the default)
      --version string   Install the given rclone version (default: latest)</code></pre>
<p>See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
<h2 id="see-also-69">See Also</h2>
<ul>
<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
</ul>
<h1 id="rclone-serve">rclone serve</h1>
<p>Serve a remote over a protocol.</p>
<h2 id="synopsis-62">Synopsis</h2>
<p>Serve a remote over a given protocol. Requires the use of a subcommand to specify the protocol, e.g.</p>
<pre><code>rclone serve http remote:</code></pre>
<p>Each subcommand has its own options which you can see in their help.</p>
<pre><code>rclone serve &lt;protocol&gt; [opts] &lt;remote&gt; [flags]</code></pre>
<h2 id="options-70">Options</h2>
<pre><code>  -h, --help   help for serve</code></pre>
<p>See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
<h2 id="see-also-70">See Also</h2>
<ul>
<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
<li><a href="https://rclone.org/commands/rclone_serve_dlna/">rclone serve dlna</a> - Serve remote:path over DLNA</li>
<li><a href="https://rclone.org/commands/rclone_serve_docker/">rclone serve docker</a> - Serve any remote on docker's volume plugin API.</li>
<li><a href="https://rclone.org/commands/rclone_serve_ftp/">rclone serve ftp</a> - Serve remote:path over FTP.</li>
<li><a href="https://rclone.org/commands/rclone_serve_http/">rclone serve http</a> - Serve the remote over HTTP.</li>
<li><a href="https://rclone.org/commands/rclone_serve_nfs/">rclone serve nfs</a> - Serve the remote as an NFS mount</li>
<li><a href="https://rclone.org/commands/rclone_serve_restic/">rclone serve restic</a> - Serve the remote for restic's REST API.</li>
<li><a href="https://rclone.org/commands/rclone_serve_s3/">rclone serve s3</a> - Serve remote:path over s3.</li>
<li><a href="https://rclone.org/commands/rclone_serve_sftp/">rclone serve sftp</a> - Serve the remote over SFTP.</li>
<li><a href="https://rclone.org/commands/rclone_serve_webdav/">rclone serve webdav</a> - Serve remote:path over WebDAV.</li>
</ul>
<h1 id="rclone-serve-dlna">rclone serve dlna</h1>
<p>Serve remote:path over DLNA</p>
<h2 id="synopsis-63">Synopsis</h2>
<p>Run a DLNA media server for media stored in an rclone remote. Many devices, such as the Xbox and PlayStation, can automatically discover this server in the LAN and play audio/video from it. VLC is also supported. Service discovery uses UDP multicast packets (SSDP) and will thus only work on LANs.</p>
<p>Rclone will list all files present in the remote, without filtering based on media formats or file extensions. Additionally, there is no media transcoding support. This means that some players might show files that they are not able to play back correctly.</p>
<p>Rclone will add external subtitle files (.srt) to videos if they have the same filename as the video file itself (except the extension), either in the same directory as the video, or in a "Subs" subdirectory.</p>
<h2 id="server-options-1">Server options</h2>
<p>Use <code>--addr</code> to specify which IP address and port the server should listen on, e.g. <code>--addr 1.2.3.4:8000</code> or <code>--addr :8080</code> to listen to all IPs.</p>
<p>Use <code>--name</code> to choose the friendly server name, which is by default "rclone (hostname)".</p>
<p>Use <code>--log-trace</code> in conjunction with <code>-vv</code> to enable additional debug logging of all UPNP traffic.</p>
<h2 id="vfs---virtual-file-system-2">VFS - Virtual File System</h2>
<p>This command uses the VFS layer. This adapts the cloud storage objects that rclone uses into something which looks much more like a disk filing system.</p>
<p>Cloud storage objects have lots of properties which aren't like disk files - you can't extend them or write to the middle of them, so the VFS layer has to deal with that. Because there is no one right way of doing this there are various options explained below.</p>
<p>The VFS layer also implements a directory cache - this caches info about files and directories (but not the data) in memory.</p>
<h2 id="vfs-directory-cache-2">VFS Directory Cache</h2>
<p>Using the <code>--dir-cache-time</code> flag, you can control how long a directory should be considered up to date and not refreshed from the backend. Changes made through the VFS will appear immediately or invalidate the cache.</p>
<pre><code>--dir-cache-time duration   Time to cache directory entries for (default 5m0s)
--poll-interval duration    Time to wait between polling for changes. Must be smaller than dir-cache-time. Only on supported remotes. Set to 0 to disable (default 1m0s)</code></pre>
<p>However, changes made directly on the cloud storage by the web interface or a different copy of rclone will only be picked up once the directory cache expires if the backend configured does not support polling for changes. If the backend supports polling, changes will be picked up within the polling interval.</p>
<p>You can send a <code>SIGHUP</code> signal to rclone for it to flush all directory caches, regardless of how old they are. Assuming only one rclone instance is running, you can reset the cache like this:</p>
<pre><code>kill -SIGHUP $(pidof rclone)</code></pre>
<p>If you configure rclone with a <a href="/rc">remote control</a> then you can use rclone rc to flush the whole directory cache:</p>
<pre><code>rclone rc vfs/forget</code></pre>
<p>Or individual files or directories:</p>
<pre><code>rclone rc vfs/forget file=path/to/file dir=path/to/dir</code></pre>
<h2 id="vfs-file-buffering-2">VFS File Buffering</h2>
<p>The <code>--buffer-size</code> flag determines the amount of memory, that will be used to buffer data in advance.</p>
<p>Each open file will try to keep the specified amount of data in memory at all times. The buffered data is bound to one open file and won't be shared.</p>
<p>This flag is a upper limit for the used memory per open file. The buffer will only use memory for data that is downloaded but not not yet read. If the buffer is empty, only a small amount of memory will be used.</p>
<p>The maximum memory used by rclone for buffering can be up to <code>--buffer-size * open files</code>.</p>
<h2 id="vfs-file-caching-2">VFS File Caching</h2>
<p>These flags control the VFS file caching options. File caching is necessary to make the VFS layer appear compatible with a normal file system. It can be disabled at the cost of some compatibility.</p>
<p>For example you'll need to enable VFS caching if you want to read and write simultaneously to a file. See below for more details.</p>
<p>Note that the VFS cache is separate from the cache backend and you may find that you need one or the other or both.</p>
<pre><code>--cache-dir string                     Directory rclone will use for caching.
--vfs-cache-mode CacheMode             Cache mode off|minimal|writes|full (default off)
--vfs-cache-max-age duration           Max time since last access of objects in the cache (default 1h0m0s)
--vfs-cache-max-size SizeSuffix        Max total size of objects in the cache (default off)
--vfs-cache-min-free-space SizeSuffix  Target minimum free space on the disk containing the cache (default off)
--vfs-cache-poll-interval duration     Interval to poll the cache for stale objects (default 1m0s)
--vfs-write-back duration              Time to writeback files after last use when using cache (default 5s)</code></pre>
<p>If run with <code>-vv</code> rclone will print the location of the file cache. The files are stored in the user cache file area which is OS dependent but can be controlled with <code>--cache-dir</code> or setting the appropriate environment variable.</p>
<p>The cache has 4 different modes selected by <code>--vfs-cache-mode</code>. The higher the cache mode the more compatible rclone becomes at the cost of using disk space.</p>
<p>Note that files are written back to the remote only when they are closed and if they haven't been accessed for <code>--vfs-write-back</code> seconds. If rclone is quit or dies with files that haven't been uploaded, these will be uploaded next time rclone is run with the same flags.</p>
<p>If using <code>--vfs-cache-max-size</code> or <code>--vfs-cache-min-free-size</code> note that the cache may exceed these quotas for two reasons. Firstly because it is only checked every <code>--vfs-cache-poll-interval</code>. Secondly because open files cannot be evicted from the cache. When <code>--vfs-cache-max-size</code> or <code>--vfs-cache-min-free-size</code> is exceeded, rclone will attempt to evict the least accessed files from the cache first. rclone will start with files that haven't been accessed for the longest. This cache flushing strategy is efficient and more relevant files are likely to remain cached.</p>
<p>The <code>--vfs-cache-max-age</code> will evict files from the cache after the set time since last access has passed. The default value of 1 hour will start evicting files from cache that haven't been accessed for 1 hour. When a cached file is accessed the 1 hour timer is reset to 0 and will wait for 1 more hour before evicting. Specify the time with standard notation, s, m, h, d, w .</p>
<p>You <strong>should not</strong> run two copies of rclone using the same VFS cache with the same or overlapping remotes if using <code>--vfs-cache-mode &gt; off</code>. This can potentially cause data corruption if you do. You can work around this by giving each rclone its own cache hierarchy with <code>--cache-dir</code>. You don't need to worry about this if the remotes in use don't overlap.</p>
<h3 id="vfs-cache-mode-off-2">--vfs-cache-mode off</h3>
<p>In this mode (the default) the cache will read directly from the remote and write directly to the remote without caching anything on disk.</p>
<p>This will mean some operations are not possible</p>
<ul>
<li>Files can't be opened for both read AND write</li>
<li>Files opened for write can't be seeked</li>
<li>Existing files opened for write must have O_TRUNC set</li>
<li>Files open for read with O_TRUNC will be opened write only</li>
<li>Files open for write only will behave as if O_TRUNC was supplied</li>
<li>Open modes O_APPEND, O_TRUNC are ignored</li>
<li>If an upload fails it can't be retried</li>
</ul>
<h3 id="vfs-cache-mode-minimal-2">--vfs-cache-mode minimal</h3>
<p>This is very similar to "off" except that files opened for read AND write will be buffered to disk. This means that files opened for write will be a lot more compatible, but uses the minimal disk space.</p>
<p>These operations are not possible</p>
<ul>
<li>Files opened for write only can't be seeked</li>
<li>Existing files opened for write must have O_TRUNC set</li>
<li>Files opened for write only will ignore O_APPEND, O_TRUNC</li>
<li>If an upload fails it can't be retried</li>
</ul>
<h3 id="vfs-cache-mode-writes-2">--vfs-cache-mode writes</h3>
<p>In this mode files opened for read only are still read directly from the remote, write only and read/write files are buffered to disk first.</p>
<p>This mode should support all normal file system operations.</p>
<p>If an upload fails it will be retried at exponentially increasing intervals up to 1 minute.</p>
<h3 id="vfs-cache-mode-full-2">--vfs-cache-mode full</h3>
<p>In this mode all reads and writes are buffered to and from disk. When data is read from the remote this is buffered to disk as well.</p>
<p>In this mode the files in the cache will be sparse files and rclone will keep track of which bits of the files it has downloaded.</p>
<p>So if an application only reads the starts of each file, then rclone will only buffer the start of the file. These files will appear to be their full size in the cache, but they will be sparse files with only the data that has been downloaded present in them.</p>
<p>This mode should support all normal file system operations and is otherwise identical to <code>--vfs-cache-mode</code> writes.</p>
<p>When reading a file rclone will read <code>--buffer-size</code> plus <code>--vfs-read-ahead</code> bytes ahead. The <code>--buffer-size</code> is buffered in memory whereas the <code>--vfs-read-ahead</code> is buffered on disk.</p>
<p>When using this mode it is recommended that <code>--buffer-size</code> is not set too large and <code>--vfs-read-ahead</code> is set large if required.</p>
<p><strong>IMPORTANT</strong> not all file systems support sparse files. In particular FAT/exFAT do not. Rclone will perform very badly if the cache directory is on a filesystem which doesn't support sparse files and it will log an ERROR message if one is detected.</p>
<h3 id="fingerprinting-2">Fingerprinting</h3>
<p>Various parts of the VFS use fingerprinting to see if a local file copy has changed relative to a remote file. Fingerprints are made from:</p>
<ul>
<li>size</li>
<li>modification time</li>
<li>hash</li>
</ul>
<p>where available on an object.</p>
<p>On some backends some of these attributes are slow to read (they take an extra API call per object, or extra work per object).</p>
<p>For example <code>hash</code> is slow with the <code>local</code> and <code>sftp</code> backends as they have to read the entire file and hash it, and <code>modtime</code> is slow with the <code>s3</code>, <code>swift</code>, <code>ftp</code> and <code>qinqstor</code> backends because they need to do an extra API call to fetch it.</p>
<p>If you use the <code>--vfs-fast-fingerprint</code> flag then rclone will not include the slow operations in the fingerprint. This makes the fingerprinting less accurate but much faster and will improve the opening time of cached files.</p>
<p>If you are running a vfs cache over <code>local</code>, <code>s3</code> or <code>swift</code> backends then using this flag is recommended.</p>
<p>Note that if you change the value of this flag, the fingerprints of the files in the cache may be invalidated and the files will need to be downloaded again.</p>
<h2 id="vfs-chunked-reading-2">VFS Chunked Reading</h2>
<p>When rclone reads files from a remote it reads them in chunks. This means that rather than requesting the whole file rclone reads the chunk specified. This can reduce the used download quota for some remotes by requesting only chunks from the remote that are actually read, at the cost of an increased number of requests.</p>
<p>These flags control the chunking:</p>
<pre><code>--vfs-read-chunk-size SizeSuffix        Read the source objects in chunks (default 128M)
--vfs-read-chunk-size-limit SizeSuffix  Max chunk doubling size (default off)
--vfs-read-chunk-streams int            The number of parallel streams to read at once</code></pre>
<p>The chunking behaves differently depending on the <code>--vfs-read-chunk-streams</code> parameter.</p>
<h3 id="vfs-read-chunk-streams-0-4"><code>--vfs-read-chunk-streams</code> == 0</h3>
<p>Rclone will start reading a chunk of size <code>--vfs-read-chunk-size</code>, and then double the size for each read. When <code>--vfs-read-chunk-size-limit</code> is specified, and greater than <code>--vfs-read-chunk-size</code>, the chunk size for each open file will get doubled only until the specified value is reached. If the value is "off", which is the default, the limit is disabled and the chunk size will grow indefinitely.</p>
<p>With <code>--vfs-read-chunk-size 100M</code> and <code>--vfs-read-chunk-size-limit 0</code> the following parts will be downloaded: 0-100M, 100M-200M, 200M-300M, 300M-400M and so on. When <code>--vfs-read-chunk-size-limit 500M</code> is specified, the result would be 0-100M, 100M-300M, 300M-700M, 700M-1200M, 1200M-1700M and so on.</p>
<p>Setting <code>--vfs-read-chunk-size</code> to <code>0</code> or "off" disables chunked reading.</p>
<p>The chunks will not be buffered in memory.</p>
<h3 id="vfs-read-chunk-streams-0-5"><code>--vfs-read-chunk-streams</code> &gt; 0</h3>
<p>Rclone reads <code>--vfs-read-chunk-streams</code> chunks of size <code>--vfs-read-chunk-size</code> concurrently. The size for each read will stay constant.</p>
<p>This improves performance performance massively on high latency links or very high bandwidth links to high performance object stores.</p>
<p>Some experimentation will be needed to find the optimum values of <code>--vfs-read-chunk-size</code> and <code>--vfs-read-chunk-streams</code> as these will depend on the backend in use and the latency to the backend.</p>
<p>For high performance object stores (eg AWS S3) a reasonable place to start might be <code>--vfs-read-chunk-streams 16</code> and <code>--vfs-read-chunk-size 4M</code>. In testing with AWS S3 the performance scaled roughly as the <code>--vfs-read-chunk-streams</code> setting.</p>
<p>Similar settings should work for high latency links, but depending on the latency they may need more <code>--vfs-read-chunk-streams</code> in order to get the throughput.</p>
<h2 id="vfs-performance-2">VFS Performance</h2>
<p>These flags may be used to enable/disable features of the VFS for performance or other reasons. See also the <a href="#vfs-chunked-reading">chunked reading</a> feature.</p>
<p>In particular S3 and Swift benefit hugely from the <code>--no-modtime</code> flag (or use <code>--use-server-modtime</code> for a slightly different effect) as each read of the modification time takes a transaction.</p>
<pre><code>--no-checksum     Don&#39;t compare checksums on up/download.
--no-modtime      Don&#39;t read/write the modification time (can speed things up).
--no-seek         Don&#39;t allow seeking in files.
--read-only       Only allow read-only access.</code></pre>
<p>Sometimes rclone is delivered reads or writes out of order. Rather than seeking rclone will wait a short time for the in sequence read or write to come in. These flags only come into effect when not using an on disk cache file.</p>
<pre><code>--vfs-read-wait duration   Time to wait for in-sequence read before seeking (default 20ms)
--vfs-write-wait duration  Time to wait for in-sequence write before giving error (default 1s)</code></pre>
<p>When using VFS write caching (<code>--vfs-cache-mode</code> with value writes or full), the global flag <code>--transfers</code> can be set to adjust the number of parallel uploads of modified files from the cache (the related global flag <code>--checkers</code> has no effect on the VFS).</p>
<pre><code>--transfers int  Number of file transfers to run in parallel (default 4)</code></pre>
<h2 id="vfs-case-sensitivity-2">VFS Case Sensitivity</h2>
<p>Linux file systems are case-sensitive: two files can differ only by case, and the exact case must be used when opening a file.</p>
<p>File systems in modern Windows are case-insensitive but case-preserving: although existing files can be opened using any case, the exact case used to create the file is preserved and available for programs to query. It is not allowed for two files in the same directory to differ only by case.</p>
<p>Usually file systems on macOS are case-insensitive. It is possible to make macOS file systems case-sensitive but that is not the default.</p>
<p>The <code>--vfs-case-insensitive</code> VFS flag controls how rclone handles these two cases. If its value is "false", rclone passes file names to the remote as-is. If the flag is "true" (or appears without a value on the command line), rclone may perform a "fixup" as explained below.</p>
<p>The user may specify a file name to open/delete/rename/etc with a case different than what is stored on the remote. If an argument refers to an existing file with exactly the same name, then the case of the existing file on the disk will be used. However, if a file name with exactly the same name is not found but a name differing only by case exists, rclone will transparently fixup the name. This fixup happens only when an existing file is requested. Case sensitivity of file names created anew by rclone is controlled by the underlying remote.</p>
<p>Note that case sensitivity of the operating system running rclone (the target) may differ from case sensitivity of a file system presented by rclone (the source). The flag controls whether "fixup" is performed to satisfy the target.</p>
<p>If the flag is not provided on the command line, then its default value depends on the operating system where rclone runs: "true" on Windows and macOS, "false" otherwise. If the flag is provided without a value, then it is "true".</p>
<p>The <code>--no-unicode-normalization</code> flag controls whether a similar "fixup" is performed for filenames that differ but are <a href="https://en.wikipedia.org/wiki/Unicode_equivalence">canonically equivalent</a> with respect to unicode. Unicode normalization can be particularly helpful for users of macOS, which prefers form NFD instead of the NFC used by most other platforms. It is therefore highly recommended to keep the default of <code>false</code> on macOS, to avoid encoding compatibility issues.</p>
<p>In the (probably unlikely) event that a directory has multiple duplicate filenames after applying case and unicode normalization, the <code>--vfs-block-norm-dupes</code> flag allows hiding these duplicates. This comes with a performance tradeoff, as rclone will have to scan the entire directory for duplicates when listing a directory. For this reason, it is recommended to leave this disabled if not needed. However, macOS users may wish to consider using it, as otherwise, if a remote directory contains both NFC and NFD versions of the same filename, an odd situation will occur: both versions of the file will be visible in the mount, and both will appear to be editable, however, editing either version will actually result in only the NFD version getting edited under the hood. <code>--vfs-block- norm-dupes</code> prevents this confusion by detecting this scenario, hiding the duplicates, and logging an error, similar to how this is handled in <code>rclone sync</code>.</p>
<h2 id="vfs-disk-options-2">VFS Disk Options</h2>
<p>This flag allows you to manually set the statistics about the filing system. It can be useful when those statistics cannot be read correctly automatically.</p>
<pre><code>--vfs-disk-space-total-size    Manually set the total disk space size (example: 256G, default: -1)</code></pre>
<h2 id="alternate-report-of-used-bytes-2">Alternate report of used bytes</h2>
<p>Some backends, most notably S3, do not report the amount of bytes used. If you need this information to be available when running <code>df</code> on the filesystem, then pass the flag <code>--vfs-used-is-size</code> to rclone. With this flag set, instead of relying on the backend to report this information, rclone will scan the whole remote similar to <code>rclone size</code> and compute the total used space itself.</p>
<p><em>WARNING.</em> Contrary to <code>rclone size</code>, this flag ignores filters so that the result is accurate. However, this is very inefficient and may cost lots of API calls resulting in extra charges. Use it as a last resort and only with caching.</p>
<pre><code>rclone serve dlna remote:path [flags]</code></pre>
<h2 id="options-71">Options</h2>
<pre><code>      --addr string                            The ip:port or :port to bind the DLNA http server to (default &quot;:7879&quot;)
      --announce-interval Duration             The interval between SSDP announcements (default 12m0s)
      --dir-cache-time Duration                Time to cache directory entries for (default 5m0s)
      --dir-perms FileMode                     Directory permissions (default 777)
      --file-perms FileMode                    File permissions (default 666)
      --gid uint32                             Override the gid field set by the filesystem (not supported on Windows) (default 1000)
  -h, --help                                   help for dlna
      --interface stringArray                  The interface to use for SSDP (repeat as necessary)
      --log-trace                              Enable trace logging of SOAP traffic
      --name string                            Name of DLNA server
      --no-checksum                            Don&#39;t compare checksums on up/download
      --no-modtime                             Don&#39;t read/write the modification time (can speed things up)
      --no-seek                                Don&#39;t allow seeking in files
      --poll-interval Duration                 Time to wait between polling for changes, must be smaller than dir-cache-time and only on supported remotes (set 0 to disable) (default 1m0s)
      --read-only                              Only allow read-only access
      --uid uint32                             Override the uid field set by the filesystem (not supported on Windows) (default 1000)
      --umask FileMode                         Override the permission bits set by the filesystem (not supported on Windows) (default 002)
      --vfs-block-norm-dupes                   If duplicate filenames exist in the same directory (after normalization), log an error and hide the duplicates (may have a performance cost)
      --vfs-cache-max-age Duration             Max time since last access of objects in the cache (default 1h0m0s)
      --vfs-cache-max-size SizeSuffix          Max total size of objects in the cache (default off)
      --vfs-cache-min-free-space SizeSuffix    Target minimum free space on the disk containing the cache (default off)
      --vfs-cache-mode CacheMode               Cache mode off|minimal|writes|full (default off)
      --vfs-cache-poll-interval Duration       Interval to poll the cache for stale objects (default 1m0s)
      --vfs-case-insensitive                   If a file name not found, find a case insensitive match
      --vfs-disk-space-total-size SizeSuffix   Specify the total space of disk (default off)
      --vfs-fast-fingerprint                   Use fast (less accurate) fingerprints for change detection
      --vfs-read-ahead SizeSuffix              Extra read ahead over --buffer-size when using cache-mode full
      --vfs-read-chunk-size SizeSuffix         Read the source objects in chunks (default 128Mi)
      --vfs-read-chunk-size-limit SizeSuffix   If greater than --vfs-read-chunk-size, double the chunk size after each chunk read, until the limit is reached (&#39;off&#39; is unlimited) (default off)
      --vfs-read-chunk-streams int             The number of parallel streams to read at once
      --vfs-read-wait Duration                 Time to wait for in-sequence read before seeking (default 20ms)
      --vfs-refresh                            Refreshes the directory cache recursively in the background on start
      --vfs-used-is-size rclone size           Use the rclone size algorithm for Used size
      --vfs-write-back Duration                Time to writeback files after last use when using cache (default 5s)
      --vfs-write-wait Duration                Time to wait for in-sequence write before giving error (default 1s)</code></pre>
<p>Options shared with other commands are described next. See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
<h3 id="filter-options-23">Filter Options</h3>
<p>Flags for filtering directory listings</p>
<pre><code>      --delete-excluded                     Delete files on dest excluded from sync
      --exclude stringArray                 Exclude files matching pattern
      --exclude-from stringArray            Read file exclude patterns from file (use - to read from stdin)
      --exclude-if-present stringArray      Exclude directories if filename is present
      --files-from stringArray              Read list of source-file names from file (use - to read from stdin)
      --files-from-raw stringArray          Read list of source-file names from file without any processing of lines (use - to read from stdin)
  -f, --filter stringArray                  Add a file filtering rule
      --filter-from stringArray             Read file filtering patterns from a file (use - to read from stdin)
      --ignore-case                         Ignore case in filters (case insensitive)
      --include stringArray                 Include files matching pattern
      --include-from stringArray            Read file include patterns from file (use - to read from stdin)
      --max-age Duration                    Only transfer files younger than this in s or suffix ms|s|m|h|d|w|M|y (default off)
      --max-depth int                       If set limits the recursion depth to this (default -1)
      --max-size SizeSuffix                 Only transfer files smaller than this in KiB or suffix B|K|M|G|T|P (default off)
      --metadata-exclude stringArray        Exclude metadatas matching pattern
      --metadata-exclude-from stringArray   Read metadata exclude patterns from file (use - to read from stdin)
      --metadata-filter stringArray         Add a metadata filtering rule
      --metadata-filter-from stringArray    Read metadata filtering patterns from a file (use - to read from stdin)
      --metadata-include stringArray        Include metadatas matching pattern
      --metadata-include-from stringArray   Read metadata include patterns from file (use - to read from stdin)
      --min-age Duration                    Only transfer files older than this in s or suffix ms|s|m|h|d|w|M|y (default off)
      --min-size SizeSuffix                 Only transfer files bigger than this in KiB or suffix B|K|M|G|T|P (default off)</code></pre>
<h2 id="see-also-71">See Also</h2>
<ul>
<li><a href="https://rclone.org/commands/rclone_serve/">rclone serve</a> - Serve a remote over a protocol.</li>
</ul>
<h1 id="rclone-serve-docker">rclone serve docker</h1>
<p>Serve any remote on docker's volume plugin API.</p>
<h2 id="synopsis-64">Synopsis</h2>
<p>This command implements the Docker volume plugin API allowing docker to use rclone as a data storage mechanism for various cloud providers. rclone provides <a href="/docker">docker volume plugin</a> based on it.</p>
<p>To create a docker plugin, one must create a Unix or TCP socket that Docker will look for when you use the plugin and then it listens for commands from docker daemon and runs the corresponding code when necessary. Docker plugins can run as a managed plugin under control of the docker daemon or as an independent native service. For testing, you can just run it directly from the command line, for example:</p>
<pre><code>sudo rclone serve docker --base-dir /tmp/rclone-volumes --socket-addr localhost:8787 -vv</code></pre>
<p>Running <code>rclone serve docker</code> will create the said socket, listening for commands from Docker to create the necessary Volumes. Normally you need not give the <code>--socket-addr</code> flag. The API will listen on the unix domain socket at <code>/run/docker/plugins/rclone.sock</code>. In the example above rclone will create a TCP socket and a small file <code>/etc/docker/plugins/rclone.spec</code> containing the socket address. We use <code>sudo</code> because both paths are writeable only by the root user.</p>
<p>If you later decide to change listening socket, the docker daemon must be restarted to reconnect to <code>/run/docker/plugins/rclone.sock</code> or parse new <code>/etc/docker/plugins/rclone.spec</code>. Until you restart, any volume related docker commands will timeout trying to access the old socket. Running directly is supported on <strong>Linux only</strong>, not on Windows or MacOS. This is not a problem with managed plugin mode described in details in the <a href="https://rclone.org/docker">full documentation</a>.</p>
<p>The command will create volume mounts under the path given by <code>--base-dir</code> (by default <code>/var/lib/docker-volumes/rclone</code> available only to root) and maintain the JSON formatted file <code>docker-plugin.state</code> in the rclone cache directory with book-keeping records of created and mounted volumes.</p>
<p>All mount and VFS options are submitted by the docker daemon via API, but you can also provide defaults on the command line as well as set path to the config file and cache directory or adjust logging verbosity.</p>
<h2 id="vfs---virtual-file-system-3">VFS - Virtual File System</h2>
<p>This command uses the VFS layer. This adapts the cloud storage objects that rclone uses into something which looks much more like a disk filing system.</p>
<p>Cloud storage objects have lots of properties which aren't like disk files - you can't extend them or write to the middle of them, so the VFS layer has to deal with that. Because there is no one right way of doing this there are various options explained below.</p>
<p>The VFS layer also implements a directory cache - this caches info about files and directories (but not the data) in memory.</p>
<h2 id="vfs-directory-cache-3">VFS Directory Cache</h2>
<p>Using the <code>--dir-cache-time</code> flag, you can control how long a directory should be considered up to date and not refreshed from the backend. Changes made through the VFS will appear immediately or invalidate the cache.</p>
<pre><code>--dir-cache-time duration   Time to cache directory entries for (default 5m0s)
--poll-interval duration    Time to wait between polling for changes. Must be smaller than dir-cache-time. Only on supported remotes. Set to 0 to disable (default 1m0s)</code></pre>
<p>However, changes made directly on the cloud storage by the web interface or a different copy of rclone will only be picked up once the directory cache expires if the backend configured does not support polling for changes. If the backend supports polling, changes will be picked up within the polling interval.</p>
<p>You can send a <code>SIGHUP</code> signal to rclone for it to flush all directory caches, regardless of how old they are. Assuming only one rclone instance is running, you can reset the cache like this:</p>
<pre><code>kill -SIGHUP $(pidof rclone)</code></pre>
<p>If you configure rclone with a <a href="/rc">remote control</a> then you can use rclone rc to flush the whole directory cache:</p>
<pre><code>rclone rc vfs/forget</code></pre>
<p>Or individual files or directories:</p>
<pre><code>rclone rc vfs/forget file=path/to/file dir=path/to/dir</code></pre>
<h2 id="vfs-file-buffering-3">VFS File Buffering</h2>
<p>The <code>--buffer-size</code> flag determines the amount of memory, that will be used to buffer data in advance.</p>
<p>Each open file will try to keep the specified amount of data in memory at all times. The buffered data is bound to one open file and won't be shared.</p>
<p>This flag is a upper limit for the used memory per open file. The buffer will only use memory for data that is downloaded but not not yet read. If the buffer is empty, only a small amount of memory will be used.</p>
<p>The maximum memory used by rclone for buffering can be up to <code>--buffer-size * open files</code>.</p>
<h2 id="vfs-file-caching-3">VFS File Caching</h2>
<p>These flags control the VFS file caching options. File caching is necessary to make the VFS layer appear compatible with a normal file system. It can be disabled at the cost of some compatibility.</p>
<p>For example you'll need to enable VFS caching if you want to read and write simultaneously to a file. See below for more details.</p>
<p>Note that the VFS cache is separate from the cache backend and you may find that you need one or the other or both.</p>
<pre><code>--cache-dir string                     Directory rclone will use for caching.
--vfs-cache-mode CacheMode             Cache mode off|minimal|writes|full (default off)
--vfs-cache-max-age duration           Max time since last access of objects in the cache (default 1h0m0s)
--vfs-cache-max-size SizeSuffix        Max total size of objects in the cache (default off)
--vfs-cache-min-free-space SizeSuffix  Target minimum free space on the disk containing the cache (default off)
--vfs-cache-poll-interval duration     Interval to poll the cache for stale objects (default 1m0s)
--vfs-write-back duration              Time to writeback files after last use when using cache (default 5s)</code></pre>
<p>If run with <code>-vv</code> rclone will print the location of the file cache. The files are stored in the user cache file area which is OS dependent but can be controlled with <code>--cache-dir</code> or setting the appropriate environment variable.</p>
<p>The cache has 4 different modes selected by <code>--vfs-cache-mode</code>. The higher the cache mode the more compatible rclone becomes at the cost of using disk space.</p>
<p>Note that files are written back to the remote only when they are closed and if they haven't been accessed for <code>--vfs-write-back</code> seconds. If rclone is quit or dies with files that haven't been uploaded, these will be uploaded next time rclone is run with the same flags.</p>
<p>If using <code>--vfs-cache-max-size</code> or <code>--vfs-cache-min-free-size</code> note that the cache may exceed these quotas for two reasons. Firstly because it is only checked every <code>--vfs-cache-poll-interval</code>. Secondly because open files cannot be evicted from the cache. When <code>--vfs-cache-max-size</code> or <code>--vfs-cache-min-free-size</code> is exceeded, rclone will attempt to evict the least accessed files from the cache first. rclone will start with files that haven't been accessed for the longest. This cache flushing strategy is efficient and more relevant files are likely to remain cached.</p>
<p>The <code>--vfs-cache-max-age</code> will evict files from the cache after the set time since last access has passed. The default value of 1 hour will start evicting files from cache that haven't been accessed for 1 hour. When a cached file is accessed the 1 hour timer is reset to 0 and will wait for 1 more hour before evicting. Specify the time with standard notation, s, m, h, d, w .</p>
<p>You <strong>should not</strong> run two copies of rclone using the same VFS cache with the same or overlapping remotes if using <code>--vfs-cache-mode &gt; off</code>. This can potentially cause data corruption if you do. You can work around this by giving each rclone its own cache hierarchy with <code>--cache-dir</code>. You don't need to worry about this if the remotes in use don't overlap.</p>
<h3 id="vfs-cache-mode-off-3">--vfs-cache-mode off</h3>
<p>In this mode (the default) the cache will read directly from the remote and write directly to the remote without caching anything on disk.</p>
<p>This will mean some operations are not possible</p>
<ul>
<li>Files can't be opened for both read AND write</li>
<li>Files opened for write can't be seeked</li>
<li>Existing files opened for write must have O_TRUNC set</li>
<li>Files open for read with O_TRUNC will be opened write only</li>
<li>Files open for write only will behave as if O_TRUNC was supplied</li>
<li>Open modes O_APPEND, O_TRUNC are ignored</li>
<li>If an upload fails it can't be retried</li>
</ul>
<h3 id="vfs-cache-mode-minimal-3">--vfs-cache-mode minimal</h3>
<p>This is very similar to "off" except that files opened for read AND write will be buffered to disk. This means that files opened for write will be a lot more compatible, but uses the minimal disk space.</p>
<p>These operations are not possible</p>
<ul>
<li>Files opened for write only can't be seeked</li>
<li>Existing files opened for write must have O_TRUNC set</li>
<li>Files opened for write only will ignore O_APPEND, O_TRUNC</li>
<li>If an upload fails it can't be retried</li>
</ul>
<h3 id="vfs-cache-mode-writes-3">--vfs-cache-mode writes</h3>
<p>In this mode files opened for read only are still read directly from the remote, write only and read/write files are buffered to disk first.</p>
<p>This mode should support all normal file system operations.</p>
<p>If an upload fails it will be retried at exponentially increasing intervals up to 1 minute.</p>
<h3 id="vfs-cache-mode-full-3">--vfs-cache-mode full</h3>
<p>In this mode all reads and writes are buffered to and from disk. When data is read from the remote this is buffered to disk as well.</p>
<p>In this mode the files in the cache will be sparse files and rclone will keep track of which bits of the files it has downloaded.</p>
<p>So if an application only reads the starts of each file, then rclone will only buffer the start of the file. These files will appear to be their full size in the cache, but they will be sparse files with only the data that has been downloaded present in them.</p>
<p>This mode should support all normal file system operations and is otherwise identical to <code>--vfs-cache-mode</code> writes.</p>
<p>When reading a file rclone will read <code>--buffer-size</code> plus <code>--vfs-read-ahead</code> bytes ahead. The <code>--buffer-size</code> is buffered in memory whereas the <code>--vfs-read-ahead</code> is buffered on disk.</p>
<p>When using this mode it is recommended that <code>--buffer-size</code> is not set too large and <code>--vfs-read-ahead</code> is set large if required.</p>
<p><strong>IMPORTANT</strong> not all file systems support sparse files. In particular FAT/exFAT do not. Rclone will perform very badly if the cache directory is on a filesystem which doesn't support sparse files and it will log an ERROR message if one is detected.</p>
<h3 id="fingerprinting-3">Fingerprinting</h3>
<p>Various parts of the VFS use fingerprinting to see if a local file copy has changed relative to a remote file. Fingerprints are made from:</p>
<ul>
<li>size</li>
<li>modification time</li>
<li>hash</li>
</ul>
<p>where available on an object.</p>
<p>On some backends some of these attributes are slow to read (they take an extra API call per object, or extra work per object).</p>
<p>For example <code>hash</code> is slow with the <code>local</code> and <code>sftp</code> backends as they have to read the entire file and hash it, and <code>modtime</code> is slow with the <code>s3</code>, <code>swift</code>, <code>ftp</code> and <code>qinqstor</code> backends because they need to do an extra API call to fetch it.</p>
<p>If you use the <code>--vfs-fast-fingerprint</code> flag then rclone will not include the slow operations in the fingerprint. This makes the fingerprinting less accurate but much faster and will improve the opening time of cached files.</p>
<p>If you are running a vfs cache over <code>local</code>, <code>s3</code> or <code>swift</code> backends then using this flag is recommended.</p>
<p>Note that if you change the value of this flag, the fingerprints of the files in the cache may be invalidated and the files will need to be downloaded again.</p>
<h2 id="vfs-chunked-reading-3">VFS Chunked Reading</h2>
<p>When rclone reads files from a remote it reads them in chunks. This means that rather than requesting the whole file rclone reads the chunk specified. This can reduce the used download quota for some remotes by requesting only chunks from the remote that are actually read, at the cost of an increased number of requests.</p>
<p>These flags control the chunking:</p>
<pre><code>--vfs-read-chunk-size SizeSuffix        Read the source objects in chunks (default 128M)
--vfs-read-chunk-size-limit SizeSuffix  Max chunk doubling size (default off)
--vfs-read-chunk-streams int            The number of parallel streams to read at once</code></pre>
<p>The chunking behaves differently depending on the <code>--vfs-read-chunk-streams</code> parameter.</p>
<h3 id="vfs-read-chunk-streams-0-6"><code>--vfs-read-chunk-streams</code> == 0</h3>
<p>Rclone will start reading a chunk of size <code>--vfs-read-chunk-size</code>, and then double the size for each read. When <code>--vfs-read-chunk-size-limit</code> is specified, and greater than <code>--vfs-read-chunk-size</code>, the chunk size for each open file will get doubled only until the specified value is reached. If the value is "off", which is the default, the limit is disabled and the chunk size will grow indefinitely.</p>
<p>With <code>--vfs-read-chunk-size 100M</code> and <code>--vfs-read-chunk-size-limit 0</code> the following parts will be downloaded: 0-100M, 100M-200M, 200M-300M, 300M-400M and so on. When <code>--vfs-read-chunk-size-limit 500M</code> is specified, the result would be 0-100M, 100M-300M, 300M-700M, 700M-1200M, 1200M-1700M and so on.</p>
<p>Setting <code>--vfs-read-chunk-size</code> to <code>0</code> or "off" disables chunked reading.</p>
<p>The chunks will not be buffered in memory.</p>
<h3 id="vfs-read-chunk-streams-0-7"><code>--vfs-read-chunk-streams</code> &gt; 0</h3>
<p>Rclone reads <code>--vfs-read-chunk-streams</code> chunks of size <code>--vfs-read-chunk-size</code> concurrently. The size for each read will stay constant.</p>
<p>This improves performance performance massively on high latency links or very high bandwidth links to high performance object stores.</p>
<p>Some experimentation will be needed to find the optimum values of <code>--vfs-read-chunk-size</code> and <code>--vfs-read-chunk-streams</code> as these will depend on the backend in use and the latency to the backend.</p>
<p>For high performance object stores (eg AWS S3) a reasonable place to start might be <code>--vfs-read-chunk-streams 16</code> and <code>--vfs-read-chunk-size 4M</code>. In testing with AWS S3 the performance scaled roughly as the <code>--vfs-read-chunk-streams</code> setting.</p>
<p>Similar settings should work for high latency links, but depending on the latency they may need more <code>--vfs-read-chunk-streams</code> in order to get the throughput.</p>
<h2 id="vfs-performance-3">VFS Performance</h2>
<p>These flags may be used to enable/disable features of the VFS for performance or other reasons. See also the <a href="#vfs-chunked-reading">chunked reading</a> feature.</p>
<p>In particular S3 and Swift benefit hugely from the <code>--no-modtime</code> flag (or use <code>--use-server-modtime</code> for a slightly different effect) as each read of the modification time takes a transaction.</p>
<pre><code>--no-checksum     Don&#39;t compare checksums on up/download.
--no-modtime      Don&#39;t read/write the modification time (can speed things up).
--no-seek         Don&#39;t allow seeking in files.
--read-only       Only allow read-only access.</code></pre>
<p>Sometimes rclone is delivered reads or writes out of order. Rather than seeking rclone will wait a short time for the in sequence read or write to come in. These flags only come into effect when not using an on disk cache file.</p>
<pre><code>--vfs-read-wait duration   Time to wait for in-sequence read before seeking (default 20ms)
--vfs-write-wait duration  Time to wait for in-sequence write before giving error (default 1s)</code></pre>
<p>When using VFS write caching (<code>--vfs-cache-mode</code> with value writes or full), the global flag <code>--transfers</code> can be set to adjust the number of parallel uploads of modified files from the cache (the related global flag <code>--checkers</code> has no effect on the VFS).</p>
<pre><code>--transfers int  Number of file transfers to run in parallel (default 4)</code></pre>
<h2 id="vfs-case-sensitivity-3">VFS Case Sensitivity</h2>
<p>Linux file systems are case-sensitive: two files can differ only by case, and the exact case must be used when opening a file.</p>
<p>File systems in modern Windows are case-insensitive but case-preserving: although existing files can be opened using any case, the exact case used to create the file is preserved and available for programs to query. It is not allowed for two files in the same directory to differ only by case.</p>
<p>Usually file systems on macOS are case-insensitive. It is possible to make macOS file systems case-sensitive but that is not the default.</p>
<p>The <code>--vfs-case-insensitive</code> VFS flag controls how rclone handles these two cases. If its value is "false", rclone passes file names to the remote as-is. If the flag is "true" (or appears without a value on the command line), rclone may perform a "fixup" as explained below.</p>
<p>The user may specify a file name to open/delete/rename/etc with a case different than what is stored on the remote. If an argument refers to an existing file with exactly the same name, then the case of the existing file on the disk will be used. However, if a file name with exactly the same name is not found but a name differing only by case exists, rclone will transparently fixup the name. This fixup happens only when an existing file is requested. Case sensitivity of file names created anew by rclone is controlled by the underlying remote.</p>
<p>Note that case sensitivity of the operating system running rclone (the target) may differ from case sensitivity of a file system presented by rclone (the source). The flag controls whether "fixup" is performed to satisfy the target.</p>
<p>If the flag is not provided on the command line, then its default value depends on the operating system where rclone runs: "true" on Windows and macOS, "false" otherwise. If the flag is provided without a value, then it is "true".</p>
<p>The <code>--no-unicode-normalization</code> flag controls whether a similar "fixup" is performed for filenames that differ but are <a href="https://en.wikipedia.org/wiki/Unicode_equivalence">canonically equivalent</a> with respect to unicode. Unicode normalization can be particularly helpful for users of macOS, which prefers form NFD instead of the NFC used by most other platforms. It is therefore highly recommended to keep the default of <code>false</code> on macOS, to avoid encoding compatibility issues.</p>
<p>In the (probably unlikely) event that a directory has multiple duplicate filenames after applying case and unicode normalization, the <code>--vfs-block-norm-dupes</code> flag allows hiding these duplicates. This comes with a performance tradeoff, as rclone will have to scan the entire directory for duplicates when listing a directory. For this reason, it is recommended to leave this disabled if not needed. However, macOS users may wish to consider using it, as otherwise, if a remote directory contains both NFC and NFD versions of the same filename, an odd situation will occur: both versions of the file will be visible in the mount, and both will appear to be editable, however, editing either version will actually result in only the NFD version getting edited under the hood. <code>--vfs-block- norm-dupes</code> prevents this confusion by detecting this scenario, hiding the duplicates, and logging an error, similar to how this is handled in <code>rclone sync</code>.</p>
<h2 id="vfs-disk-options-3">VFS Disk Options</h2>
<p>This flag allows you to manually set the statistics about the filing system. It can be useful when those statistics cannot be read correctly automatically.</p>
<pre><code>--vfs-disk-space-total-size    Manually set the total disk space size (example: 256G, default: -1)</code></pre>
<h2 id="alternate-report-of-used-bytes-3">Alternate report of used bytes</h2>
<p>Some backends, most notably S3, do not report the amount of bytes used. If you need this information to be available when running <code>df</code> on the filesystem, then pass the flag <code>--vfs-used-is-size</code> to rclone. With this flag set, instead of relying on the backend to report this information, rclone will scan the whole remote similar to <code>rclone size</code> and compute the total used space itself.</p>
<p><em>WARNING.</em> Contrary to <code>rclone size</code>, this flag ignores filters so that the result is accurate. However, this is very inefficient and may cost lots of API calls resulting in extra charges. Use it as a last resort and only with caching.</p>
<pre><code>rclone serve docker [flags]</code></pre>
<h2 id="options-72">Options</h2>
<pre><code>      --allow-non-empty                        Allow mounting over a non-empty directory (not supported on Windows)
      --allow-other                            Allow access to other users (not supported on Windows)
      --allow-root                             Allow access to root user (not supported on Windows)
      --async-read                             Use asynchronous reads (not supported on Windows) (default true)
      --attr-timeout Duration                  Time for which file/directory attributes are cached (default 1s)
      --base-dir string                        Base directory for volumes (default &quot;/var/lib/docker-volumes/rclone&quot;)
      --daemon                                 Run mount in background and exit parent process (as background output is suppressed, use --log-file with --log-format=pid,... to monitor) (not supported on Windows)
      --daemon-timeout Duration                Time limit for rclone to respond to kernel (not supported on Windows) (default 0s)
      --daemon-wait Duration                   Time to wait for ready mount from daemon (maximum time on Linux, constant sleep time on OSX/BSD) (not supported on Windows) (default 1m0s)
      --debug-fuse                             Debug the FUSE internals - needs -v
      --default-permissions                    Makes kernel enforce access control based on the file mode (not supported on Windows)
      --devname string                         Set the device name - default is remote:path
      --dir-cache-time Duration                Time to cache directory entries for (default 5m0s)
      --dir-perms FileMode                     Directory permissions (default 777)
      --direct-io                              Use Direct IO, disables caching of data
      --file-perms FileMode                    File permissions (default 666)
      --forget-state                           Skip restoring previous state
      --fuse-flag stringArray                  Flags or arguments to be passed direct to libfuse/WinFsp (repeat if required)
      --gid uint32                             Override the gid field set by the filesystem (not supported on Windows) (default 1000)
  -h, --help                                   help for docker
      --max-read-ahead SizeSuffix              The number of bytes that can be prefetched for sequential reads (not supported on Windows) (default 128Ki)
      --mount-case-insensitive Tristate        Tell the OS the mount is case insensitive (true) or sensitive (false) regardless of the backend (auto) (default unset)
      --network-mode                           Mount as remote network drive, instead of fixed disk drive (supported on Windows only)
      --no-checksum                            Don&#39;t compare checksums on up/download
      --no-modtime                             Don&#39;t read/write the modification time (can speed things up)
      --no-seek                                Don&#39;t allow seeking in files
      --no-spec                                Do not write spec file
      --noappledouble                          Ignore Apple Double (._) and .DS_Store files (supported on OSX only) (default true)
      --noapplexattr                           Ignore all &quot;com.apple.*&quot; extended attributes (supported on OSX only)
  -o, --option stringArray                     Option for libfuse/WinFsp (repeat if required)
      --poll-interval Duration                 Time to wait between polling for changes, must be smaller than dir-cache-time and only on supported remotes (set 0 to disable) (default 1m0s)
      --read-only                              Only allow read-only access
      --socket-addr string                     Address &lt;host:port&gt; or absolute path (default: /run/docker/plugins/rclone.sock)
      --socket-gid int                         GID for unix socket (default: current process GID) (default 1000)
      --uid uint32                             Override the uid field set by the filesystem (not supported on Windows) (default 1000)
      --umask FileMode                         Override the permission bits set by the filesystem (not supported on Windows) (default 002)
      --vfs-block-norm-dupes                   If duplicate filenames exist in the same directory (after normalization), log an error and hide the duplicates (may have a performance cost)
      --vfs-cache-max-age Duration             Max time since last access of objects in the cache (default 1h0m0s)
      --vfs-cache-max-size SizeSuffix          Max total size of objects in the cache (default off)
      --vfs-cache-min-free-space SizeSuffix    Target minimum free space on the disk containing the cache (default off)
      --vfs-cache-mode CacheMode               Cache mode off|minimal|writes|full (default off)
      --vfs-cache-poll-interval Duration       Interval to poll the cache for stale objects (default 1m0s)
      --vfs-case-insensitive                   If a file name not found, find a case insensitive match
      --vfs-disk-space-total-size SizeSuffix   Specify the total space of disk (default off)
      --vfs-fast-fingerprint                   Use fast (less accurate) fingerprints for change detection
      --vfs-read-ahead SizeSuffix              Extra read ahead over --buffer-size when using cache-mode full
      --vfs-read-chunk-size SizeSuffix         Read the source objects in chunks (default 128Mi)
      --vfs-read-chunk-size-limit SizeSuffix   If greater than --vfs-read-chunk-size, double the chunk size after each chunk read, until the limit is reached (&#39;off&#39; is unlimited) (default off)
      --vfs-read-chunk-streams int             The number of parallel streams to read at once
      --vfs-read-wait Duration                 Time to wait for in-sequence read before seeking (default 20ms)
      --vfs-refresh                            Refreshes the directory cache recursively in the background on start
      --vfs-used-is-size rclone size           Use the rclone size algorithm for Used size
      --vfs-write-back Duration                Time to writeback files after last use when using cache (default 5s)
      --vfs-write-wait Duration                Time to wait for in-sequence write before giving error (default 1s)
      --volname string                         Set the volume name (supported on Windows and OSX only)
      --write-back-cache                       Makes kernel buffer writes before sending them to rclone (without this, writethrough caching is used) (not supported on Windows)</code></pre>
<p>Options shared with other commands are described next. See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
<h3 id="filter-options-24">Filter Options</h3>
<p>Flags for filtering directory listings</p>
<pre><code>      --delete-excluded                     Delete files on dest excluded from sync
      --exclude stringArray                 Exclude files matching pattern
      --exclude-from stringArray            Read file exclude patterns from file (use - to read from stdin)
      --exclude-if-present stringArray      Exclude directories if filename is present
      --files-from stringArray              Read list of source-file names from file (use - to read from stdin)
      --files-from-raw stringArray          Read list of source-file names from file without any processing of lines (use - to read from stdin)
  -f, --filter stringArray                  Add a file filtering rule
      --filter-from stringArray             Read file filtering patterns from a file (use - to read from stdin)
      --ignore-case                         Ignore case in filters (case insensitive)
      --include stringArray                 Include files matching pattern
      --include-from stringArray            Read file include patterns from file (use - to read from stdin)
      --max-age Duration                    Only transfer files younger than this in s or suffix ms|s|m|h|d|w|M|y (default off)
      --max-depth int                       If set limits the recursion depth to this (default -1)
      --max-size SizeSuffix                 Only transfer files smaller than this in KiB or suffix B|K|M|G|T|P (default off)
      --metadata-exclude stringArray        Exclude metadatas matching pattern
      --metadata-exclude-from stringArray   Read metadata exclude patterns from file (use - to read from stdin)
      --metadata-filter stringArray         Add a metadata filtering rule
      --metadata-filter-from stringArray    Read metadata filtering patterns from a file (use - to read from stdin)
      --metadata-include stringArray        Include metadatas matching pattern
      --metadata-include-from stringArray   Read metadata include patterns from file (use - to read from stdin)
      --min-age Duration                    Only transfer files older than this in s or suffix ms|s|m|h|d|w|M|y (default off)
      --min-size SizeSuffix                 Only transfer files bigger than this in KiB or suffix B|K|M|G|T|P (default off)</code></pre>
<h2 id="see-also-72">See Also</h2>
<ul>
<li><a href="https://rclone.org/commands/rclone_serve/">rclone serve</a> - Serve a remote over a protocol.</li>
</ul>
<h1 id="rclone-serve-ftp">rclone serve ftp</h1>
<p>Serve remote:path over FTP.</p>
<h2 id="synopsis-65">Synopsis</h2>
<p>Run a basic FTP server to serve a remote over FTP protocol. This can be viewed with a FTP client or you can make a remote of type FTP to read and write it.</p>
<h2 id="server-options-2">Server options</h2>
<p>Use --addr to specify which IP address and port the server should listen on, e.g. --addr 1.2.3.4:8000 or --addr :8080 to listen to all IPs. By default it only listens on localhost. You can use port :0 to let the OS choose an available port.</p>
<p>If you set --addr to listen on a public or LAN accessible IP address then using Authentication is advised - see the next section for info.</p>
<h3 id="authentication-1">Authentication</h3>
<p>By default this will serve files without needing a login.</p>
<p>You can set a single username and password with the --user and --pass flags.</p>
<h2 id="vfs---virtual-file-system-4">VFS - Virtual File System</h2>
<p>This command uses the VFS layer. This adapts the cloud storage objects that rclone uses into something which looks much more like a disk filing system.</p>
<p>Cloud storage objects have lots of properties which aren't like disk files - you can't extend them or write to the middle of them, so the VFS layer has to deal with that. Because there is no one right way of doing this there are various options explained below.</p>
<p>The VFS layer also implements a directory cache - this caches info about files and directories (but not the data) in memory.</p>
<h2 id="vfs-directory-cache-4">VFS Directory Cache</h2>
<p>Using the <code>--dir-cache-time</code> flag, you can control how long a directory should be considered up to date and not refreshed from the backend. Changes made through the VFS will appear immediately or invalidate the cache.</p>
<pre><code>--dir-cache-time duration   Time to cache directory entries for (default 5m0s)
--poll-interval duration    Time to wait between polling for changes. Must be smaller than dir-cache-time. Only on supported remotes. Set to 0 to disable (default 1m0s)</code></pre>
<p>However, changes made directly on the cloud storage by the web interface or a different copy of rclone will only be picked up once the directory cache expires if the backend configured does not support polling for changes. If the backend supports polling, changes will be picked up within the polling interval.</p>
<p>You can send a <code>SIGHUP</code> signal to rclone for it to flush all directory caches, regardless of how old they are. Assuming only one rclone instance is running, you can reset the cache like this:</p>
<pre><code>kill -SIGHUP $(pidof rclone)</code></pre>
<p>If you configure rclone with a <a href="/rc">remote control</a> then you can use rclone rc to flush the whole directory cache:</p>
<pre><code>rclone rc vfs/forget</code></pre>
<p>Or individual files or directories:</p>
<pre><code>rclone rc vfs/forget file=path/to/file dir=path/to/dir</code></pre>
<h2 id="vfs-file-buffering-4">VFS File Buffering</h2>
<p>The <code>--buffer-size</code> flag determines the amount of memory, that will be used to buffer data in advance.</p>
<p>Each open file will try to keep the specified amount of data in memory at all times. The buffered data is bound to one open file and won't be shared.</p>
<p>This flag is a upper limit for the used memory per open file. The buffer will only use memory for data that is downloaded but not not yet read. If the buffer is empty, only a small amount of memory will be used.</p>
<p>The maximum memory used by rclone for buffering can be up to <code>--buffer-size * open files</code>.</p>
<h2 id="vfs-file-caching-4">VFS File Caching</h2>
<p>These flags control the VFS file caching options. File caching is necessary to make the VFS layer appear compatible with a normal file system. It can be disabled at the cost of some compatibility.</p>
<p>For example you'll need to enable VFS caching if you want to read and write simultaneously to a file. See below for more details.</p>
<p>Note that the VFS cache is separate from the cache backend and you may find that you need one or the other or both.</p>
<pre><code>--cache-dir string                     Directory rclone will use for caching.
--vfs-cache-mode CacheMode             Cache mode off|minimal|writes|full (default off)
--vfs-cache-max-age duration           Max time since last access of objects in the cache (default 1h0m0s)
--vfs-cache-max-size SizeSuffix        Max total size of objects in the cache (default off)
--vfs-cache-min-free-space SizeSuffix  Target minimum free space on the disk containing the cache (default off)
--vfs-cache-poll-interval duration     Interval to poll the cache for stale objects (default 1m0s)
--vfs-write-back duration              Time to writeback files after last use when using cache (default 5s)</code></pre>
<p>If run with <code>-vv</code> rclone will print the location of the file cache. The files are stored in the user cache file area which is OS dependent but can be controlled with <code>--cache-dir</code> or setting the appropriate environment variable.</p>
<p>The cache has 4 different modes selected by <code>--vfs-cache-mode</code>. The higher the cache mode the more compatible rclone becomes at the cost of using disk space.</p>
<p>Note that files are written back to the remote only when they are closed and if they haven't been accessed for <code>--vfs-write-back</code> seconds. If rclone is quit or dies with files that haven't been uploaded, these will be uploaded next time rclone is run with the same flags.</p>
<p>If using <code>--vfs-cache-max-size</code> or <code>--vfs-cache-min-free-size</code> note that the cache may exceed these quotas for two reasons. Firstly because it is only checked every <code>--vfs-cache-poll-interval</code>. Secondly because open files cannot be evicted from the cache. When <code>--vfs-cache-max-size</code> or <code>--vfs-cache-min-free-size</code> is exceeded, rclone will attempt to evict the least accessed files from the cache first. rclone will start with files that haven't been accessed for the longest. This cache flushing strategy is efficient and more relevant files are likely to remain cached.</p>
<p>The <code>--vfs-cache-max-age</code> will evict files from the cache after the set time since last access has passed. The default value of 1 hour will start evicting files from cache that haven't been accessed for 1 hour. When a cached file is accessed the 1 hour timer is reset to 0 and will wait for 1 more hour before evicting. Specify the time with standard notation, s, m, h, d, w .</p>
<p>You <strong>should not</strong> run two copies of rclone using the same VFS cache with the same or overlapping remotes if using <code>--vfs-cache-mode &gt; off</code>. This can potentially cause data corruption if you do. You can work around this by giving each rclone its own cache hierarchy with <code>--cache-dir</code>. You don't need to worry about this if the remotes in use don't overlap.</p>
<h3 id="vfs-cache-mode-off-4">--vfs-cache-mode off</h3>
<p>In this mode (the default) the cache will read directly from the remote and write directly to the remote without caching anything on disk.</p>
<p>This will mean some operations are not possible</p>
<ul>
<li>Files can't be opened for both read AND write</li>
<li>Files opened for write can't be seeked</li>
<li>Existing files opened for write must have O_TRUNC set</li>
<li>Files open for read with O_TRUNC will be opened write only</li>
<li>Files open for write only will behave as if O_TRUNC was supplied</li>
<li>Open modes O_APPEND, O_TRUNC are ignored</li>
<li>If an upload fails it can't be retried</li>
</ul>
<h3 id="vfs-cache-mode-minimal-4">--vfs-cache-mode minimal</h3>
<p>This is very similar to "off" except that files opened for read AND write will be buffered to disk. This means that files opened for write will be a lot more compatible, but uses the minimal disk space.</p>
<p>These operations are not possible</p>
<ul>
<li>Files opened for write only can't be seeked</li>
<li>Existing files opened for write must have O_TRUNC set</li>
<li>Files opened for write only will ignore O_APPEND, O_TRUNC</li>
<li>If an upload fails it can't be retried</li>
</ul>
<h3 id="vfs-cache-mode-writes-4">--vfs-cache-mode writes</h3>
<p>In this mode files opened for read only are still read directly from the remote, write only and read/write files are buffered to disk first.</p>
<p>This mode should support all normal file system operations.</p>
<p>If an upload fails it will be retried at exponentially increasing intervals up to 1 minute.</p>
<h3 id="vfs-cache-mode-full-4">--vfs-cache-mode full</h3>
<p>In this mode all reads and writes are buffered to and from disk. When data is read from the remote this is buffered to disk as well.</p>
<p>In this mode the files in the cache will be sparse files and rclone will keep track of which bits of the files it has downloaded.</p>
<p>So if an application only reads the starts of each file, then rclone will only buffer the start of the file. These files will appear to be their full size in the cache, but they will be sparse files with only the data that has been downloaded present in them.</p>
<p>This mode should support all normal file system operations and is otherwise identical to <code>--vfs-cache-mode</code> writes.</p>
<p>When reading a file rclone will read <code>--buffer-size</code> plus <code>--vfs-read-ahead</code> bytes ahead. The <code>--buffer-size</code> is buffered in memory whereas the <code>--vfs-read-ahead</code> is buffered on disk.</p>
<p>When using this mode it is recommended that <code>--buffer-size</code> is not set too large and <code>--vfs-read-ahead</code> is set large if required.</p>
<p><strong>IMPORTANT</strong> not all file systems support sparse files. In particular FAT/exFAT do not. Rclone will perform very badly if the cache directory is on a filesystem which doesn't support sparse files and it will log an ERROR message if one is detected.</p>
<h3 id="fingerprinting-4">Fingerprinting</h3>
<p>Various parts of the VFS use fingerprinting to see if a local file copy has changed relative to a remote file. Fingerprints are made from:</p>
<ul>
<li>size</li>
<li>modification time</li>
<li>hash</li>
</ul>
<p>where available on an object.</p>
<p>On some backends some of these attributes are slow to read (they take an extra API call per object, or extra work per object).</p>
<p>For example <code>hash</code> is slow with the <code>local</code> and <code>sftp</code> backends as they have to read the entire file and hash it, and <code>modtime</code> is slow with the <code>s3</code>, <code>swift</code>, <code>ftp</code> and <code>qinqstor</code> backends because they need to do an extra API call to fetch it.</p>
<p>If you use the <code>--vfs-fast-fingerprint</code> flag then rclone will not include the slow operations in the fingerprint. This makes the fingerprinting less accurate but much faster and will improve the opening time of cached files.</p>
<p>If you are running a vfs cache over <code>local</code>, <code>s3</code> or <code>swift</code> backends then using this flag is recommended.</p>
<p>Note that if you change the value of this flag, the fingerprints of the files in the cache may be invalidated and the files will need to be downloaded again.</p>
<h2 id="vfs-chunked-reading-4">VFS Chunked Reading</h2>
<p>When rclone reads files from a remote it reads them in chunks. This means that rather than requesting the whole file rclone reads the chunk specified. This can reduce the used download quota for some remotes by requesting only chunks from the remote that are actually read, at the cost of an increased number of requests.</p>
<p>These flags control the chunking:</p>
<pre><code>--vfs-read-chunk-size SizeSuffix        Read the source objects in chunks (default 128M)
--vfs-read-chunk-size-limit SizeSuffix  Max chunk doubling size (default off)
--vfs-read-chunk-streams int            The number of parallel streams to read at once</code></pre>
<p>The chunking behaves differently depending on the <code>--vfs-read-chunk-streams</code> parameter.</p>
<h3 id="vfs-read-chunk-streams-0-8"><code>--vfs-read-chunk-streams</code> == 0</h3>
<p>Rclone will start reading a chunk of size <code>--vfs-read-chunk-size</code>, and then double the size for each read. When <code>--vfs-read-chunk-size-limit</code> is specified, and greater than <code>--vfs-read-chunk-size</code>, the chunk size for each open file will get doubled only until the specified value is reached. If the value is "off", which is the default, the limit is disabled and the chunk size will grow indefinitely.</p>
<p>With <code>--vfs-read-chunk-size 100M</code> and <code>--vfs-read-chunk-size-limit 0</code> the following parts will be downloaded: 0-100M, 100M-200M, 200M-300M, 300M-400M and so on. When <code>--vfs-read-chunk-size-limit 500M</code> is specified, the result would be 0-100M, 100M-300M, 300M-700M, 700M-1200M, 1200M-1700M and so on.</p>
<p>Setting <code>--vfs-read-chunk-size</code> to <code>0</code> or "off" disables chunked reading.</p>
<p>The chunks will not be buffered in memory.</p>
<h3 id="vfs-read-chunk-streams-0-9"><code>--vfs-read-chunk-streams</code> &gt; 0</h3>
<p>Rclone reads <code>--vfs-read-chunk-streams</code> chunks of size <code>--vfs-read-chunk-size</code> concurrently. The size for each read will stay constant.</p>
<p>This improves performance performance massively on high latency links or very high bandwidth links to high performance object stores.</p>
<p>Some experimentation will be needed to find the optimum values of <code>--vfs-read-chunk-size</code> and <code>--vfs-read-chunk-streams</code> as these will depend on the backend in use and the latency to the backend.</p>
<p>For high performance object stores (eg AWS S3) a reasonable place to start might be <code>--vfs-read-chunk-streams 16</code> and <code>--vfs-read-chunk-size 4M</code>. In testing with AWS S3 the performance scaled roughly as the <code>--vfs-read-chunk-streams</code> setting.</p>
<p>Similar settings should work for high latency links, but depending on the latency they may need more <code>--vfs-read-chunk-streams</code> in order to get the throughput.</p>
<h2 id="vfs-performance-4">VFS Performance</h2>
<p>These flags may be used to enable/disable features of the VFS for performance or other reasons. See also the <a href="#vfs-chunked-reading">chunked reading</a> feature.</p>
<p>In particular S3 and Swift benefit hugely from the <code>--no-modtime</code> flag (or use <code>--use-server-modtime</code> for a slightly different effect) as each read of the modification time takes a transaction.</p>
<pre><code>--no-checksum     Don&#39;t compare checksums on up/download.
--no-modtime      Don&#39;t read/write the modification time (can speed things up).
--no-seek         Don&#39;t allow seeking in files.
--read-only       Only allow read-only access.</code></pre>
<p>Sometimes rclone is delivered reads or writes out of order. Rather than seeking rclone will wait a short time for the in sequence read or write to come in. These flags only come into effect when not using an on disk cache file.</p>
<pre><code>--vfs-read-wait duration   Time to wait for in-sequence read before seeking (default 20ms)
--vfs-write-wait duration  Time to wait for in-sequence write before giving error (default 1s)</code></pre>
<p>When using VFS write caching (<code>--vfs-cache-mode</code> with value writes or full), the global flag <code>--transfers</code> can be set to adjust the number of parallel uploads of modified files from the cache (the related global flag <code>--checkers</code> has no effect on the VFS).</p>
<pre><code>--transfers int  Number of file transfers to run in parallel (default 4)</code></pre>
<h2 id="vfs-case-sensitivity-4">VFS Case Sensitivity</h2>
<p>Linux file systems are case-sensitive: two files can differ only by case, and the exact case must be used when opening a file.</p>
<p>File systems in modern Windows are case-insensitive but case-preserving: although existing files can be opened using any case, the exact case used to create the file is preserved and available for programs to query. It is not allowed for two files in the same directory to differ only by case.</p>
<p>Usually file systems on macOS are case-insensitive. It is possible to make macOS file systems case-sensitive but that is not the default.</p>
<p>The <code>--vfs-case-insensitive</code> VFS flag controls how rclone handles these two cases. If its value is "false", rclone passes file names to the remote as-is. If the flag is "true" (or appears without a value on the command line), rclone may perform a "fixup" as explained below.</p>
<p>The user may specify a file name to open/delete/rename/etc with a case different than what is stored on the remote. If an argument refers to an existing file with exactly the same name, then the case of the existing file on the disk will be used. However, if a file name with exactly the same name is not found but a name differing only by case exists, rclone will transparently fixup the name. This fixup happens only when an existing file is requested. Case sensitivity of file names created anew by rclone is controlled by the underlying remote.</p>
<p>Note that case sensitivity of the operating system running rclone (the target) may differ from case sensitivity of a file system presented by rclone (the source). The flag controls whether "fixup" is performed to satisfy the target.</p>
<p>If the flag is not provided on the command line, then its default value depends on the operating system where rclone runs: "true" on Windows and macOS, "false" otherwise. If the flag is provided without a value, then it is "true".</p>
<p>The <code>--no-unicode-normalization</code> flag controls whether a similar "fixup" is performed for filenames that differ but are <a href="https://en.wikipedia.org/wiki/Unicode_equivalence">canonically equivalent</a> with respect to unicode. Unicode normalization can be particularly helpful for users of macOS, which prefers form NFD instead of the NFC used by most other platforms. It is therefore highly recommended to keep the default of <code>false</code> on macOS, to avoid encoding compatibility issues.</p>
<p>In the (probably unlikely) event that a directory has multiple duplicate filenames after applying case and unicode normalization, the <code>--vfs-block-norm-dupes</code> flag allows hiding these duplicates. This comes with a performance tradeoff, as rclone will have to scan the entire directory for duplicates when listing a directory. For this reason, it is recommended to leave this disabled if not needed. However, macOS users may wish to consider using it, as otherwise, if a remote directory contains both NFC and NFD versions of the same filename, an odd situation will occur: both versions of the file will be visible in the mount, and both will appear to be editable, however, editing either version will actually result in only the NFD version getting edited under the hood. <code>--vfs-block- norm-dupes</code> prevents this confusion by detecting this scenario, hiding the duplicates, and logging an error, similar to how this is handled in <code>rclone sync</code>.</p>
<h2 id="vfs-disk-options-4">VFS Disk Options</h2>
<p>This flag allows you to manually set the statistics about the filing system. It can be useful when those statistics cannot be read correctly automatically.</p>
<pre><code>--vfs-disk-space-total-size    Manually set the total disk space size (example: 256G, default: -1)</code></pre>
<h2 id="alternate-report-of-used-bytes-4">Alternate report of used bytes</h2>
<p>Some backends, most notably S3, do not report the amount of bytes used. If you need this information to be available when running <code>df</code> on the filesystem, then pass the flag <code>--vfs-used-is-size</code> to rclone. With this flag set, instead of relying on the backend to report this information, rclone will scan the whole remote similar to <code>rclone size</code> and compute the total used space itself.</p>
<p><em>WARNING.</em> Contrary to <code>rclone size</code>, this flag ignores filters so that the result is accurate. However, this is very inefficient and may cost lots of API calls resulting in extra charges. Use it as a last resort and only with caching.</p>
<h2 id="auth-proxy">Auth Proxy</h2>
<p>If you supply the parameter <code>--auth-proxy /path/to/program</code> then rclone will use that program to generate backends on the fly which then are used to authenticate incoming requests. This uses a simple JSON based protocol with input on STDIN and output on STDOUT.</p>
<p><strong>PLEASE NOTE:</strong> <code>--auth-proxy</code> and <code>--authorized-keys</code> cannot be used together, if <code>--auth-proxy</code> is set the authorized keys option will be ignored.</p>
<p>There is an example program <a href="https://github.com/rclone/rclone/blob/master/bin/test_proxy.py">bin/test_proxy.py</a> in the rclone source code.</p>
<p>The program's job is to take a <code>user</code> and <code>pass</code> on the input and turn those into the config for a backend on STDOUT in JSON format. This config will have any default parameters for the backend added, but it won't use configuration from environment variables or command line options - it is the job of the proxy program to make a complete config.</p>
<p>This config generated must have this extra parameter - <code>_root</code> - root to use for the backend</p>
<p>And it may have this parameter - <code>_obscure</code> - comma separated strings for parameters to obscure</p>
<p>If password authentication was used by the client, input to the proxy process (on STDIN) would look similar to this:</p>
<pre><code>{
    &quot;user&quot;: &quot;me&quot;,
    &quot;pass&quot;: &quot;mypassword&quot;
}</code></pre>
<p>If public-key authentication was used by the client, input to the proxy process (on STDIN) would look similar to this:</p>
<pre><code>{
    &quot;user&quot;: &quot;me&quot;,
    &quot;public_key&quot;: &quot;AAAAB3NzaC1yc2EAAAADAQABAAABAQDuwESFdAe14hVS6omeyX7edc...JQdf&quot;
}</code></pre>
<p>And as an example return this on STDOUT</p>
<pre><code>{
    &quot;type&quot;: &quot;sftp&quot;,
    &quot;_root&quot;: &quot;&quot;,
    &quot;_obscure&quot;: &quot;pass&quot;,
    &quot;user&quot;: &quot;me&quot;,
    &quot;pass&quot;: &quot;mypassword&quot;,
    &quot;host&quot;: &quot;sftp.example.com&quot;
}</code></pre>
<p>This would mean that an SFTP backend would be created on the fly for the <code>user</code> and <code>pass</code>/<code>public_key</code> returned in the output to the host given. Note that since <code>_obscure</code> is set to <code>pass</code>, rclone will obscure the <code>pass</code> parameter before creating the backend (which is required for sftp backends).</p>
<p>The program can manipulate the supplied <code>user</code> in any way, for example to make proxy to many different sftp backends, you could make the <code>user</code> be <code>user@example.com</code> and then set the <code>host</code> to <code>example.com</code> in the output and the user to <code>user</code>. For security you'd probably want to restrict the <code>host</code> to a limited list.</p>
<p>Note that an internal cache is keyed on <code>user</code> so only use that for configuration, don't use <code>pass</code> or <code>public_key</code>. This also means that if a user's password or public-key is changed the cache will need to expire (which takes 5 mins) before it takes effect.</p>
<p>This can be used to build general purpose proxies to any kind of backend that rclone supports.</p>
<pre><code>rclone serve ftp remote:path [flags]</code></pre>
<h2 id="options-73">Options</h2>
<pre><code>      --addr string                            IPaddress:Port or :Port to bind server to (default &quot;localhost:2121&quot;)
      --auth-proxy string                      A program to use to create the backend from the auth
      --cert string                            TLS PEM key (concatenation of certificate and CA certificate)
      --dir-cache-time Duration                Time to cache directory entries for (default 5m0s)
      --dir-perms FileMode                     Directory permissions (default 777)
      --file-perms FileMode                    File permissions (default 666)
      --gid uint32                             Override the gid field set by the filesystem (not supported on Windows) (default 1000)
  -h, --help                                   help for ftp
      --key string                             TLS PEM Private key
      --no-checksum                            Don&#39;t compare checksums on up/download
      --no-modtime                             Don&#39;t read/write the modification time (can speed things up)
      --no-seek                                Don&#39;t allow seeking in files
      --pass string                            Password for authentication (empty value allow every password)
      --passive-port string                    Passive port range to use (default &quot;30000-32000&quot;)
      --poll-interval Duration                 Time to wait between polling for changes, must be smaller than dir-cache-time and only on supported remotes (set 0 to disable) (default 1m0s)
      --public-ip string                       Public IP address to advertise for passive connections
      --read-only                              Only allow read-only access
      --uid uint32                             Override the uid field set by the filesystem (not supported on Windows) (default 1000)
      --umask FileMode                         Override the permission bits set by the filesystem (not supported on Windows) (default 002)
      --user string                            User name for authentication (default &quot;anonymous&quot;)
      --vfs-block-norm-dupes                   If duplicate filenames exist in the same directory (after normalization), log an error and hide the duplicates (may have a performance cost)
      --vfs-cache-max-age Duration             Max time since last access of objects in the cache (default 1h0m0s)
      --vfs-cache-max-size SizeSuffix          Max total size of objects in the cache (default off)
      --vfs-cache-min-free-space SizeSuffix    Target minimum free space on the disk containing the cache (default off)
      --vfs-cache-mode CacheMode               Cache mode off|minimal|writes|full (default off)
      --vfs-cache-poll-interval Duration       Interval to poll the cache for stale objects (default 1m0s)
      --vfs-case-insensitive                   If a file name not found, find a case insensitive match
      --vfs-disk-space-total-size SizeSuffix   Specify the total space of disk (default off)
      --vfs-fast-fingerprint                   Use fast (less accurate) fingerprints for change detection
      --vfs-read-ahead SizeSuffix              Extra read ahead over --buffer-size when using cache-mode full
      --vfs-read-chunk-size SizeSuffix         Read the source objects in chunks (default 128Mi)
      --vfs-read-chunk-size-limit SizeSuffix   If greater than --vfs-read-chunk-size, double the chunk size after each chunk read, until the limit is reached (&#39;off&#39; is unlimited) (default off)
      --vfs-read-chunk-streams int             The number of parallel streams to read at once
      --vfs-read-wait Duration                 Time to wait for in-sequence read before seeking (default 20ms)
      --vfs-refresh                            Refreshes the directory cache recursively in the background on start
      --vfs-used-is-size rclone size           Use the rclone size algorithm for Used size
      --vfs-write-back Duration                Time to writeback files after last use when using cache (default 5s)
      --vfs-write-wait Duration                Time to wait for in-sequence write before giving error (default 1s)</code></pre>
<p>Options shared with other commands are described next. See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
<h3 id="filter-options-25">Filter Options</h3>
<p>Flags for filtering directory listings</p>
<pre><code>      --delete-excluded                     Delete files on dest excluded from sync
      --exclude stringArray                 Exclude files matching pattern
      --exclude-from stringArray            Read file exclude patterns from file (use - to read from stdin)
      --exclude-if-present stringArray      Exclude directories if filename is present
      --files-from stringArray              Read list of source-file names from file (use - to read from stdin)
      --files-from-raw stringArray          Read list of source-file names from file without any processing of lines (use - to read from stdin)
  -f, --filter stringArray                  Add a file filtering rule
      --filter-from stringArray             Read file filtering patterns from a file (use - to read from stdin)
      --ignore-case                         Ignore case in filters (case insensitive)
      --include stringArray                 Include files matching pattern
      --include-from stringArray            Read file include patterns from file (use - to read from stdin)
      --max-age Duration                    Only transfer files younger than this in s or suffix ms|s|m|h|d|w|M|y (default off)
      --max-depth int                       If set limits the recursion depth to this (default -1)
      --max-size SizeSuffix                 Only transfer files smaller than this in KiB or suffix B|K|M|G|T|P (default off)
      --metadata-exclude stringArray        Exclude metadatas matching pattern
      --metadata-exclude-from stringArray   Read metadata exclude patterns from file (use - to read from stdin)
      --metadata-filter stringArray         Add a metadata filtering rule
      --metadata-filter-from stringArray    Read metadata filtering patterns from a file (use - to read from stdin)
      --metadata-include stringArray        Include metadatas matching pattern
      --metadata-include-from stringArray   Read metadata include patterns from file (use - to read from stdin)
      --min-age Duration                    Only transfer files older than this in s or suffix ms|s|m|h|d|w|M|y (default off)
      --min-size SizeSuffix                 Only transfer files bigger than this in KiB or suffix B|K|M|G|T|P (default off)</code></pre>
<h2 id="see-also-73">See Also</h2>
<ul>
<li><a href="https://rclone.org/commands/rclone_serve/">rclone serve</a> - Serve a remote over a protocol.</li>
</ul>
<h1 id="rclone-serve-http">rclone serve http</h1>
<p>Serve the remote over HTTP.</p>
<h2 id="synopsis-66">Synopsis</h2>
<p>Run a basic web server to serve a remote over HTTP. This can be viewed in a web browser or you can make a remote of type http read from it.</p>
<p>You can use the filter flags (e.g. <code>--include</code>, <code>--exclude</code>) to control what is served.</p>
<p>The server will log errors. Use <code>-v</code> to see access logs.</p>
<p><code>--bwlimit</code> will be respected for file transfers. Use <code>--stats</code> to control the stats printing.</p>
<h2 id="server-options-3">Server options</h2>
<p>Use <code>--addr</code> to specify which IP address and port the server should listen on, eg <code>--addr 1.2.3.4:8000</code> or <code>--addr :8080</code> to listen to all IPs. By default it only listens on localhost. You can use port :0 to let the OS choose an available port.</p>
<p>If you set <code>--addr</code> to listen on a public or LAN accessible IP address then using Authentication is advised - see the next section for info.</p>
<p>You can use a unix socket by setting the url to <code>unix:///path/to/socket</code> or just by using an absolute path name. Note that unix sockets bypass the authentication - this is expected to be done with file system permissions.</p>
<p><code>--addr</code> may be repeated to listen on multiple IPs/ports/sockets. Socket activation, described further below, can also be used to accomplish the same.</p>
<p><code>--server-read-timeout</code> and <code>--server-write-timeout</code> can be used to control the timeouts on the server. Note that this is the total time for a transfer.</p>
<p><code>--max-header-bytes</code> controls the maximum number of bytes the server will accept in the HTTP header.</p>
<p><code>--baseurl</code> controls the URL prefix that rclone serves from. By default rclone will serve from the root. If you used <code>--baseurl "/rclone"</code> then rclone would serve from a URL starting with "/rclone/". This is useful if you wish to proxy rclone serve. Rclone automatically inserts leading and trailing "/" on <code>--baseurl</code>, so <code>--baseurl "rclone"</code>, <code>--baseurl "/rclone"</code> and <code>--baseurl "/rclone/"</code> are all treated identically.</p>
<h3 id="tls-ssl-1">TLS (SSL)</h3>
<p>By default this will serve over http. If you want you can serve over https. You will need to supply the <code>--cert</code> and <code>--key</code> flags. If you wish to do client side certificate validation then you will need to supply <code>--client-ca</code> also.</p>
<p><code>--cert</code> should be a either a PEM encoded certificate or a concatenation of that with the CA certificate. <code>--key</code> should be the PEM encoded private key and <code>--client-ca</code> should be the PEM encoded client certificate authority certificate.</p>
<p><code>--min-tls-version</code> is minimum TLS version that is acceptable. Valid values are "tls1.0", "tls1.1", "tls1.2" and "tls1.3" (default "tls1.0").</p>
<h2 id="socket-activation-1">Socket activation</h2>
<p>Instead of the listening addresses specified above, rclone will listen to all FDs passed by the service manager, if any (and ignore any arguments passed by --addr`).</p>
<p>This allows rclone to be a socket-activated service. It can be configured with .socket and .service unit files as described in https://www.freedesktop.org/software/systemd/man/latest/systemd.socket.html</p>
<p>Socket activation can be tested ad-hoc with the <code>systemd-socket-activate</code>command</p>
<pre><code>   systemd-socket-activate -l 8000 -- rclone serve</code></pre>
<p>This will socket-activate rclone on the first connection to port 8000 over TCP. ### Template</p>
<p><code>--template</code> allows a user to specify a custom markup template for HTTP and WebDAV serve functions. The server exports the following markup to be used within the template to server pages:</p>
<table>
<colgroup>
<col style="width: 50%" />
<col style="width: 50%" />
</colgroup>
<thead>
<tr class="header">
<th style="text-align: left;">Parameter</th>
<th style="text-align: left;">Description</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td style="text-align: left;">.Name</td>
<td style="text-align: left;">The full path of a file/directory.</td>
</tr>
<tr class="even">
<td style="text-align: left;">.Title</td>
<td style="text-align: left;">Directory listing of .Name</td>
</tr>
<tr class="odd">
<td style="text-align: left;">.Sort</td>
<td style="text-align: left;">The current sort used. This is changeable via ?sort= parameter</td>
</tr>
<tr class="even">
<td style="text-align: left;"></td>
<td style="text-align: left;">Sort Options: namedirfirst,name,size,time (default namedirfirst)</td>
</tr>
<tr class="odd">
<td style="text-align: left;">.Order</td>
<td style="text-align: left;">The current ordering used. This is changeable via ?order= parameter</td>
</tr>
<tr class="even">
<td style="text-align: left;"></td>
<td style="text-align: left;">Order Options: asc,desc (default asc)</td>
</tr>
<tr class="odd">
<td style="text-align: left;">.Query</td>
<td style="text-align: left;">Currently unused.</td>
</tr>
<tr class="even">
<td style="text-align: left;">.Breadcrumb</td>
<td style="text-align: left;">Allows for creating a relative navigation</td>
</tr>
<tr class="odd">
<td style="text-align: left;">-- .Link</td>
<td style="text-align: left;">The relative to the root link of the Text.</td>
</tr>
<tr class="even">
<td style="text-align: left;">-- .Text</td>
<td style="text-align: left;">The Name of the directory.</td>
</tr>
<tr class="odd">
<td style="text-align: left;">.Entries</td>
<td style="text-align: left;">Information about a specific file/directory.</td>
</tr>
<tr class="even">
<td style="text-align: left;">-- .URL</td>
<td style="text-align: left;">The 'url' of an entry.</td>
</tr>
<tr class="odd">
<td style="text-align: left;">-- .Leaf</td>
<td style="text-align: left;">Currently same as 'URL' but intended to be 'just' the name.</td>
</tr>
<tr class="even">
<td style="text-align: left;">-- .IsDir</td>
<td style="text-align: left;">Boolean for if an entry is a directory or not.</td>
</tr>
<tr class="odd">
<td style="text-align: left;">-- .Size</td>
<td style="text-align: left;">Size in Bytes of the entry.</td>
</tr>
<tr class="even">
<td style="text-align: left;">-- .ModTime</td>
<td style="text-align: left;">The UTC timestamp of an entry.</td>
</tr>
</tbody>
</table>
<p>The server also makes the following functions available so that they can be used within the template. These functions help extend the options for dynamic rendering of HTML. They can be used to render HTML based on specific conditions.</p>
<table>
<colgroup>
<col style="width: 50%" />
<col style="width: 50%" />
</colgroup>
<thead>
<tr class="header">
<th style="text-align: left;">Function</th>
<th style="text-align: left;">Description</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td style="text-align: left;">afterEpoch</td>
<td style="text-align: left;">Returns the time since the epoch for the given time.</td>
</tr>
<tr class="even">
<td style="text-align: left;">contains</td>
<td style="text-align: left;">Checks whether a given substring is present or not in a given string.</td>
</tr>
<tr class="odd">
<td style="text-align: left;">hasPrefix</td>
<td style="text-align: left;">Checks whether the given string begins with the specified prefix.</td>
</tr>
<tr class="even">
<td style="text-align: left;">hasSuffix</td>
<td style="text-align: left;">Checks whether the given string end with the specified suffix.</td>
</tr>
</tbody>
</table>
<h3 id="authentication-2">Authentication</h3>
<p>By default this will serve files without needing a login.</p>
<p>You can either use an htpasswd file which can take lots of users, or set a single username and password with the <code>--user</code> and <code>--pass</code> flags.</p>
<p>If no static users are configured by either of the above methods, and client certificates are required by the <code>--client-ca</code> flag passed to the server, the client certificate common name will be considered as the username.</p>
<p>Use <code>--htpasswd /path/to/htpasswd</code> to provide an htpasswd file. This is in standard apache format and supports MD5, SHA1 and BCrypt for basic authentication. Bcrypt is recommended.</p>
<p>To create an htpasswd file:</p>
<pre><code>touch htpasswd
htpasswd -B htpasswd user
htpasswd -B htpasswd anotherUser</code></pre>
<p>The password file can be updated while rclone is running.</p>
<p>Use <code>--realm</code> to set the authentication realm.</p>
<p>Use <code>--salt</code> to change the password hashing salt from the default.</p>
<h2 id="vfs---virtual-file-system-5">VFS - Virtual File System</h2>
<p>This command uses the VFS layer. This adapts the cloud storage objects that rclone uses into something which looks much more like a disk filing system.</p>
<p>Cloud storage objects have lots of properties which aren't like disk files - you can't extend them or write to the middle of them, so the VFS layer has to deal with that. Because there is no one right way of doing this there are various options explained below.</p>
<p>The VFS layer also implements a directory cache - this caches info about files and directories (but not the data) in memory.</p>
<h2 id="vfs-directory-cache-5">VFS Directory Cache</h2>
<p>Using the <code>--dir-cache-time</code> flag, you can control how long a directory should be considered up to date and not refreshed from the backend. Changes made through the VFS will appear immediately or invalidate the cache.</p>
<pre><code>--dir-cache-time duration   Time to cache directory entries for (default 5m0s)
--poll-interval duration    Time to wait between polling for changes. Must be smaller than dir-cache-time. Only on supported remotes. Set to 0 to disable (default 1m0s)</code></pre>
<p>However, changes made directly on the cloud storage by the web interface or a different copy of rclone will only be picked up once the directory cache expires if the backend configured does not support polling for changes. If the backend supports polling, changes will be picked up within the polling interval.</p>
<p>You can send a <code>SIGHUP</code> signal to rclone for it to flush all directory caches, regardless of how old they are. Assuming only one rclone instance is running, you can reset the cache like this:</p>
<pre><code>kill -SIGHUP $(pidof rclone)</code></pre>
<p>If you configure rclone with a <a href="/rc">remote control</a> then you can use rclone rc to flush the whole directory cache:</p>
<pre><code>rclone rc vfs/forget</code></pre>
<p>Or individual files or directories:</p>
<pre><code>rclone rc vfs/forget file=path/to/file dir=path/to/dir</code></pre>
<h2 id="vfs-file-buffering-5">VFS File Buffering</h2>
<p>The <code>--buffer-size</code> flag determines the amount of memory, that will be used to buffer data in advance.</p>
<p>Each open file will try to keep the specified amount of data in memory at all times. The buffered data is bound to one open file and won't be shared.</p>
<p>This flag is a upper limit for the used memory per open file. The buffer will only use memory for data that is downloaded but not not yet read. If the buffer is empty, only a small amount of memory will be used.</p>
<p>The maximum memory used by rclone for buffering can be up to <code>--buffer-size * open files</code>.</p>
<h2 id="vfs-file-caching-5">VFS File Caching</h2>
<p>These flags control the VFS file caching options. File caching is necessary to make the VFS layer appear compatible with a normal file system. It can be disabled at the cost of some compatibility.</p>
<p>For example you'll need to enable VFS caching if you want to read and write simultaneously to a file. See below for more details.</p>
<p>Note that the VFS cache is separate from the cache backend and you may find that you need one or the other or both.</p>
<pre><code>--cache-dir string                     Directory rclone will use for caching.
--vfs-cache-mode CacheMode             Cache mode off|minimal|writes|full (default off)
--vfs-cache-max-age duration           Max time since last access of objects in the cache (default 1h0m0s)
--vfs-cache-max-size SizeSuffix        Max total size of objects in the cache (default off)
--vfs-cache-min-free-space SizeSuffix  Target minimum free space on the disk containing the cache (default off)
--vfs-cache-poll-interval duration     Interval to poll the cache for stale objects (default 1m0s)
--vfs-write-back duration              Time to writeback files after last use when using cache (default 5s)</code></pre>
<p>If run with <code>-vv</code> rclone will print the location of the file cache. The files are stored in the user cache file area which is OS dependent but can be controlled with <code>--cache-dir</code> or setting the appropriate environment variable.</p>
<p>The cache has 4 different modes selected by <code>--vfs-cache-mode</code>. The higher the cache mode the more compatible rclone becomes at the cost of using disk space.</p>
<p>Note that files are written back to the remote only when they are closed and if they haven't been accessed for <code>--vfs-write-back</code> seconds. If rclone is quit or dies with files that haven't been uploaded, these will be uploaded next time rclone is run with the same flags.</p>
<p>If using <code>--vfs-cache-max-size</code> or <code>--vfs-cache-min-free-size</code> note that the cache may exceed these quotas for two reasons. Firstly because it is only checked every <code>--vfs-cache-poll-interval</code>. Secondly because open files cannot be evicted from the cache. When <code>--vfs-cache-max-size</code> or <code>--vfs-cache-min-free-size</code> is exceeded, rclone will attempt to evict the least accessed files from the cache first. rclone will start with files that haven't been accessed for the longest. This cache flushing strategy is efficient and more relevant files are likely to remain cached.</p>
<p>The <code>--vfs-cache-max-age</code> will evict files from the cache after the set time since last access has passed. The default value of 1 hour will start evicting files from cache that haven't been accessed for 1 hour. When a cached file is accessed the 1 hour timer is reset to 0 and will wait for 1 more hour before evicting. Specify the time with standard notation, s, m, h, d, w .</p>
<p>You <strong>should not</strong> run two copies of rclone using the same VFS cache with the same or overlapping remotes if using <code>--vfs-cache-mode &gt; off</code>. This can potentially cause data corruption if you do. You can work around this by giving each rclone its own cache hierarchy with <code>--cache-dir</code>. You don't need to worry about this if the remotes in use don't overlap.</p>
<h3 id="vfs-cache-mode-off-5">--vfs-cache-mode off</h3>
<p>In this mode (the default) the cache will read directly from the remote and write directly to the remote without caching anything on disk.</p>
<p>This will mean some operations are not possible</p>
<ul>
<li>Files can't be opened for both read AND write</li>
<li>Files opened for write can't be seeked</li>
<li>Existing files opened for write must have O_TRUNC set</li>
<li>Files open for read with O_TRUNC will be opened write only</li>
<li>Files open for write only will behave as if O_TRUNC was supplied</li>
<li>Open modes O_APPEND, O_TRUNC are ignored</li>
<li>If an upload fails it can't be retried</li>
</ul>
<h3 id="vfs-cache-mode-minimal-5">--vfs-cache-mode minimal</h3>
<p>This is very similar to "off" except that files opened for read AND write will be buffered to disk. This means that files opened for write will be a lot more compatible, but uses the minimal disk space.</p>
<p>These operations are not possible</p>
<ul>
<li>Files opened for write only can't be seeked</li>
<li>Existing files opened for write must have O_TRUNC set</li>
<li>Files opened for write only will ignore O_APPEND, O_TRUNC</li>
<li>If an upload fails it can't be retried</li>
</ul>
<h3 id="vfs-cache-mode-writes-5">--vfs-cache-mode writes</h3>
<p>In this mode files opened for read only are still read directly from the remote, write only and read/write files are buffered to disk first.</p>
<p>This mode should support all normal file system operations.</p>
<p>If an upload fails it will be retried at exponentially increasing intervals up to 1 minute.</p>
<h3 id="vfs-cache-mode-full-5">--vfs-cache-mode full</h3>
<p>In this mode all reads and writes are buffered to and from disk. When data is read from the remote this is buffered to disk as well.</p>
<p>In this mode the files in the cache will be sparse files and rclone will keep track of which bits of the files it has downloaded.</p>
<p>So if an application only reads the starts of each file, then rclone will only buffer the start of the file. These files will appear to be their full size in the cache, but they will be sparse files with only the data that has been downloaded present in them.</p>
<p>This mode should support all normal file system operations and is otherwise identical to <code>--vfs-cache-mode</code> writes.</p>
<p>When reading a file rclone will read <code>--buffer-size</code> plus <code>--vfs-read-ahead</code> bytes ahead. The <code>--buffer-size</code> is buffered in memory whereas the <code>--vfs-read-ahead</code> is buffered on disk.</p>
<p>When using this mode it is recommended that <code>--buffer-size</code> is not set too large and <code>--vfs-read-ahead</code> is set large if required.</p>
<p><strong>IMPORTANT</strong> not all file systems support sparse files. In particular FAT/exFAT do not. Rclone will perform very badly if the cache directory is on a filesystem which doesn't support sparse files and it will log an ERROR message if one is detected.</p>
<h3 id="fingerprinting-5">Fingerprinting</h3>
<p>Various parts of the VFS use fingerprinting to see if a local file copy has changed relative to a remote file. Fingerprints are made from:</p>
<ul>
<li>size</li>
<li>modification time</li>
<li>hash</li>
</ul>
<p>where available on an object.</p>
<p>On some backends some of these attributes are slow to read (they take an extra API call per object, or extra work per object).</p>
<p>For example <code>hash</code> is slow with the <code>local</code> and <code>sftp</code> backends as they have to read the entire file and hash it, and <code>modtime</code> is slow with the <code>s3</code>, <code>swift</code>, <code>ftp</code> and <code>qinqstor</code> backends because they need to do an extra API call to fetch it.</p>
<p>If you use the <code>--vfs-fast-fingerprint</code> flag then rclone will not include the slow operations in the fingerprint. This makes the fingerprinting less accurate but much faster and will improve the opening time of cached files.</p>
<p>If you are running a vfs cache over <code>local</code>, <code>s3</code> or <code>swift</code> backends then using this flag is recommended.</p>
<p>Note that if you change the value of this flag, the fingerprints of the files in the cache may be invalidated and the files will need to be downloaded again.</p>
<h2 id="vfs-chunked-reading-5">VFS Chunked Reading</h2>
<p>When rclone reads files from a remote it reads them in chunks. This means that rather than requesting the whole file rclone reads the chunk specified. This can reduce the used download quota for some remotes by requesting only chunks from the remote that are actually read, at the cost of an increased number of requests.</p>
<p>These flags control the chunking:</p>
<pre><code>--vfs-read-chunk-size SizeSuffix        Read the source objects in chunks (default 128M)
--vfs-read-chunk-size-limit SizeSuffix  Max chunk doubling size (default off)
--vfs-read-chunk-streams int            The number of parallel streams to read at once</code></pre>
<p>The chunking behaves differently depending on the <code>--vfs-read-chunk-streams</code> parameter.</p>
<h3 id="vfs-read-chunk-streams-0-10"><code>--vfs-read-chunk-streams</code> == 0</h3>
<p>Rclone will start reading a chunk of size <code>--vfs-read-chunk-size</code>, and then double the size for each read. When <code>--vfs-read-chunk-size-limit</code> is specified, and greater than <code>--vfs-read-chunk-size</code>, the chunk size for each open file will get doubled only until the specified value is reached. If the value is "off", which is the default, the limit is disabled and the chunk size will grow indefinitely.</p>
<p>With <code>--vfs-read-chunk-size 100M</code> and <code>--vfs-read-chunk-size-limit 0</code> the following parts will be downloaded: 0-100M, 100M-200M, 200M-300M, 300M-400M and so on. When <code>--vfs-read-chunk-size-limit 500M</code> is specified, the result would be 0-100M, 100M-300M, 300M-700M, 700M-1200M, 1200M-1700M and so on.</p>
<p>Setting <code>--vfs-read-chunk-size</code> to <code>0</code> or "off" disables chunked reading.</p>
<p>The chunks will not be buffered in memory.</p>
<h3 id="vfs-read-chunk-streams-0-11"><code>--vfs-read-chunk-streams</code> &gt; 0</h3>
<p>Rclone reads <code>--vfs-read-chunk-streams</code> chunks of size <code>--vfs-read-chunk-size</code> concurrently. The size for each read will stay constant.</p>
<p>This improves performance performance massively on high latency links or very high bandwidth links to high performance object stores.</p>
<p>Some experimentation will be needed to find the optimum values of <code>--vfs-read-chunk-size</code> and <code>--vfs-read-chunk-streams</code> as these will depend on the backend in use and the latency to the backend.</p>
<p>For high performance object stores (eg AWS S3) a reasonable place to start might be <code>--vfs-read-chunk-streams 16</code> and <code>--vfs-read-chunk-size 4M</code>. In testing with AWS S3 the performance scaled roughly as the <code>--vfs-read-chunk-streams</code> setting.</p>
<p>Similar settings should work for high latency links, but depending on the latency they may need more <code>--vfs-read-chunk-streams</code> in order to get the throughput.</p>
<h2 id="vfs-performance-5">VFS Performance</h2>
<p>These flags may be used to enable/disable features of the VFS for performance or other reasons. See also the <a href="#vfs-chunked-reading">chunked reading</a> feature.</p>
<p>In particular S3 and Swift benefit hugely from the <code>--no-modtime</code> flag (or use <code>--use-server-modtime</code> for a slightly different effect) as each read of the modification time takes a transaction.</p>
<pre><code>--no-checksum     Don&#39;t compare checksums on up/download.
--no-modtime      Don&#39;t read/write the modification time (can speed things up).
--no-seek         Don&#39;t allow seeking in files.
--read-only       Only allow read-only access.</code></pre>
<p>Sometimes rclone is delivered reads or writes out of order. Rather than seeking rclone will wait a short time for the in sequence read or write to come in. These flags only come into effect when not using an on disk cache file.</p>
<pre><code>--vfs-read-wait duration   Time to wait for in-sequence read before seeking (default 20ms)
--vfs-write-wait duration  Time to wait for in-sequence write before giving error (default 1s)</code></pre>
<p>When using VFS write caching (<code>--vfs-cache-mode</code> with value writes or full), the global flag <code>--transfers</code> can be set to adjust the number of parallel uploads of modified files from the cache (the related global flag <code>--checkers</code> has no effect on the VFS).</p>
<pre><code>--transfers int  Number of file transfers to run in parallel (default 4)</code></pre>
<h2 id="vfs-case-sensitivity-5">VFS Case Sensitivity</h2>
<p>Linux file systems are case-sensitive: two files can differ only by case, and the exact case must be used when opening a file.</p>
<p>File systems in modern Windows are case-insensitive but case-preserving: although existing files can be opened using any case, the exact case used to create the file is preserved and available for programs to query. It is not allowed for two files in the same directory to differ only by case.</p>
<p>Usually file systems on macOS are case-insensitive. It is possible to make macOS file systems case-sensitive but that is not the default.</p>
<p>The <code>--vfs-case-insensitive</code> VFS flag controls how rclone handles these two cases. If its value is "false", rclone passes file names to the remote as-is. If the flag is "true" (or appears without a value on the command line), rclone may perform a "fixup" as explained below.</p>
<p>The user may specify a file name to open/delete/rename/etc with a case different than what is stored on the remote. If an argument refers to an existing file with exactly the same name, then the case of the existing file on the disk will be used. However, if a file name with exactly the same name is not found but a name differing only by case exists, rclone will transparently fixup the name. This fixup happens only when an existing file is requested. Case sensitivity of file names created anew by rclone is controlled by the underlying remote.</p>
<p>Note that case sensitivity of the operating system running rclone (the target) may differ from case sensitivity of a file system presented by rclone (the source). The flag controls whether "fixup" is performed to satisfy the target.</p>
<p>If the flag is not provided on the command line, then its default value depends on the operating system where rclone runs: "true" on Windows and macOS, "false" otherwise. If the flag is provided without a value, then it is "true".</p>
<p>The <code>--no-unicode-normalization</code> flag controls whether a similar "fixup" is performed for filenames that differ but are <a href="https://en.wikipedia.org/wiki/Unicode_equivalence">canonically equivalent</a> with respect to unicode. Unicode normalization can be particularly helpful for users of macOS, which prefers form NFD instead of the NFC used by most other platforms. It is therefore highly recommended to keep the default of <code>false</code> on macOS, to avoid encoding compatibility issues.</p>
<p>In the (probably unlikely) event that a directory has multiple duplicate filenames after applying case and unicode normalization, the <code>--vfs-block-norm-dupes</code> flag allows hiding these duplicates. This comes with a performance tradeoff, as rclone will have to scan the entire directory for duplicates when listing a directory. For this reason, it is recommended to leave this disabled if not needed. However, macOS users may wish to consider using it, as otherwise, if a remote directory contains both NFC and NFD versions of the same filename, an odd situation will occur: both versions of the file will be visible in the mount, and both will appear to be editable, however, editing either version will actually result in only the NFD version getting edited under the hood. <code>--vfs-block- norm-dupes</code> prevents this confusion by detecting this scenario, hiding the duplicates, and logging an error, similar to how this is handled in <code>rclone sync</code>.</p>
<h2 id="vfs-disk-options-5">VFS Disk Options</h2>
<p>This flag allows you to manually set the statistics about the filing system. It can be useful when those statistics cannot be read correctly automatically.</p>
<pre><code>--vfs-disk-space-total-size    Manually set the total disk space size (example: 256G, default: -1)</code></pre>
<h2 id="alternate-report-of-used-bytes-5">Alternate report of used bytes</h2>
<p>Some backends, most notably S3, do not report the amount of bytes used. If you need this information to be available when running <code>df</code> on the filesystem, then pass the flag <code>--vfs-used-is-size</code> to rclone. With this flag set, instead of relying on the backend to report this information, rclone will scan the whole remote similar to <code>rclone size</code> and compute the total used space itself.</p>
<p><em>WARNING.</em> Contrary to <code>rclone size</code>, this flag ignores filters so that the result is accurate. However, this is very inefficient and may cost lots of API calls resulting in extra charges. Use it as a last resort and only with caching.</p>
<h2 id="auth-proxy-1">Auth Proxy</h2>
<p>If you supply the parameter <code>--auth-proxy /path/to/program</code> then rclone will use that program to generate backends on the fly which then are used to authenticate incoming requests. This uses a simple JSON based protocol with input on STDIN and output on STDOUT.</p>
<p><strong>PLEASE NOTE:</strong> <code>--auth-proxy</code> and <code>--authorized-keys</code> cannot be used together, if <code>--auth-proxy</code> is set the authorized keys option will be ignored.</p>
<p>There is an example program <a href="https://github.com/rclone/rclone/blob/master/bin/test_proxy.py">bin/test_proxy.py</a> in the rclone source code.</p>
<p>The program's job is to take a <code>user</code> and <code>pass</code> on the input and turn those into the config for a backend on STDOUT in JSON format. This config will have any default parameters for the backend added, but it won't use configuration from environment variables or command line options - it is the job of the proxy program to make a complete config.</p>
<p>This config generated must have this extra parameter - <code>_root</code> - root to use for the backend</p>
<p>And it may have this parameter - <code>_obscure</code> - comma separated strings for parameters to obscure</p>
<p>If password authentication was used by the client, input to the proxy process (on STDIN) would look similar to this:</p>
<pre><code>{
    &quot;user&quot;: &quot;me&quot;,
    &quot;pass&quot;: &quot;mypassword&quot;
}</code></pre>
<p>If public-key authentication was used by the client, input to the proxy process (on STDIN) would look similar to this:</p>
<pre><code>{
    &quot;user&quot;: &quot;me&quot;,
    &quot;public_key&quot;: &quot;AAAAB3NzaC1yc2EAAAADAQABAAABAQDuwESFdAe14hVS6omeyX7edc...JQdf&quot;
}</code></pre>
<p>And as an example return this on STDOUT</p>
<pre><code>{
    &quot;type&quot;: &quot;sftp&quot;,
    &quot;_root&quot;: &quot;&quot;,
    &quot;_obscure&quot;: &quot;pass&quot;,
    &quot;user&quot;: &quot;me&quot;,
    &quot;pass&quot;: &quot;mypassword&quot;,
    &quot;host&quot;: &quot;sftp.example.com&quot;
}</code></pre>
<p>This would mean that an SFTP backend would be created on the fly for the <code>user</code> and <code>pass</code>/<code>public_key</code> returned in the output to the host given. Note that since <code>_obscure</code> is set to <code>pass</code>, rclone will obscure the <code>pass</code> parameter before creating the backend (which is required for sftp backends).</p>
<p>The program can manipulate the supplied <code>user</code> in any way, for example to make proxy to many different sftp backends, you could make the <code>user</code> be <code>user@example.com</code> and then set the <code>host</code> to <code>example.com</code> in the output and the user to <code>user</code>. For security you'd probably want to restrict the <code>host</code> to a limited list.</p>
<p>Note that an internal cache is keyed on <code>user</code> so only use that for configuration, don't use <code>pass</code> or <code>public_key</code>. This also means that if a user's password or public-key is changed the cache will need to expire (which takes 5 mins) before it takes effect.</p>
<p>This can be used to build general purpose proxies to any kind of backend that rclone supports.</p>
<pre><code>rclone serve http remote:path [flags]</code></pre>
<h2 id="options-74">Options</h2>
<pre><code>      --addr stringArray                       IPaddress:Port, :Port or [unix://]/path/to/socket to bind server to (default [127.0.0.1:8080])
      --allow-origin string                    Origin which cross-domain request (CORS) can be executed from
      --auth-proxy string                      A program to use to create the backend from the auth
      --baseurl string                         Prefix for URLs - leave blank for root
      --cert string                            TLS PEM key (concatenation of certificate and CA certificate)
      --client-ca string                       Client certificate authority to verify clients with
      --dir-cache-time Duration                Time to cache directory entries for (default 5m0s)
      --dir-perms FileMode                     Directory permissions (default 777)
      --file-perms FileMode                    File permissions (default 666)
      --gid uint32                             Override the gid field set by the filesystem (not supported on Windows) (default 1000)
  -h, --help                                   help for http
      --htpasswd string                        A htpasswd file - if not provided no authentication is done
      --key string                             TLS PEM Private key
      --max-header-bytes int                   Maximum size of request header (default 4096)
      --min-tls-version string                 Minimum TLS version that is acceptable (default &quot;tls1.0&quot;)
      --no-checksum                            Don&#39;t compare checksums on up/download
      --no-modtime                             Don&#39;t read/write the modification time (can speed things up)
      --no-seek                                Don&#39;t allow seeking in files
      --pass string                            Password for authentication
      --poll-interval Duration                 Time to wait between polling for changes, must be smaller than dir-cache-time and only on supported remotes (set 0 to disable) (default 1m0s)
      --read-only                              Only allow read-only access
      --realm string                           Realm for authentication
      --salt string                            Password hashing salt (default &quot;dlPL2MqE&quot;)
      --server-read-timeout Duration           Timeout for server reading data (default 1h0m0s)
      --server-write-timeout Duration          Timeout for server writing data (default 1h0m0s)
      --template string                        User-specified template
      --uid uint32                             Override the uid field set by the filesystem (not supported on Windows) (default 1000)
      --umask FileMode                         Override the permission bits set by the filesystem (not supported on Windows) (default 002)
      --user string                            User name for authentication
      --vfs-block-norm-dupes                   If duplicate filenames exist in the same directory (after normalization), log an error and hide the duplicates (may have a performance cost)
      --vfs-cache-max-age Duration             Max time since last access of objects in the cache (default 1h0m0s)
      --vfs-cache-max-size SizeSuffix          Max total size of objects in the cache (default off)
      --vfs-cache-min-free-space SizeSuffix    Target minimum free space on the disk containing the cache (default off)
      --vfs-cache-mode CacheMode               Cache mode off|minimal|writes|full (default off)
      --vfs-cache-poll-interval Duration       Interval to poll the cache for stale objects (default 1m0s)
      --vfs-case-insensitive                   If a file name not found, find a case insensitive match
      --vfs-disk-space-total-size SizeSuffix   Specify the total space of disk (default off)
      --vfs-fast-fingerprint                   Use fast (less accurate) fingerprints for change detection
      --vfs-read-ahead SizeSuffix              Extra read ahead over --buffer-size when using cache-mode full
      --vfs-read-chunk-size SizeSuffix         Read the source objects in chunks (default 128Mi)
      --vfs-read-chunk-size-limit SizeSuffix   If greater than --vfs-read-chunk-size, double the chunk size after each chunk read, until the limit is reached (&#39;off&#39; is unlimited) (default off)
      --vfs-read-chunk-streams int             The number of parallel streams to read at once
      --vfs-read-wait Duration                 Time to wait for in-sequence read before seeking (default 20ms)
      --vfs-refresh                            Refreshes the directory cache recursively in the background on start
      --vfs-used-is-size rclone size           Use the rclone size algorithm for Used size
      --vfs-write-back Duration                Time to writeback files after last use when using cache (default 5s)
      --vfs-write-wait Duration                Time to wait for in-sequence write before giving error (default 1s)</code></pre>
<p>Options shared with other commands are described next. See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
<h3 id="filter-options-26">Filter Options</h3>
<p>Flags for filtering directory listings</p>
<pre><code>      --delete-excluded                     Delete files on dest excluded from sync
      --exclude stringArray                 Exclude files matching pattern
      --exclude-from stringArray            Read file exclude patterns from file (use - to read from stdin)
      --exclude-if-present stringArray      Exclude directories if filename is present
      --files-from stringArray              Read list of source-file names from file (use - to read from stdin)
      --files-from-raw stringArray          Read list of source-file names from file without any processing of lines (use - to read from stdin)
  -f, --filter stringArray                  Add a file filtering rule
      --filter-from stringArray             Read file filtering patterns from a file (use - to read from stdin)
      --ignore-case                         Ignore case in filters (case insensitive)
      --include stringArray                 Include files matching pattern
      --include-from stringArray            Read file include patterns from file (use - to read from stdin)
      --max-age Duration                    Only transfer files younger than this in s or suffix ms|s|m|h|d|w|M|y (default off)
      --max-depth int                       If set limits the recursion depth to this (default -1)
      --max-size SizeSuffix                 Only transfer files smaller than this in KiB or suffix B|K|M|G|T|P (default off)
      --metadata-exclude stringArray        Exclude metadatas matching pattern
      --metadata-exclude-from stringArray   Read metadata exclude patterns from file (use - to read from stdin)
      --metadata-filter stringArray         Add a metadata filtering rule
      --metadata-filter-from stringArray    Read metadata filtering patterns from a file (use - to read from stdin)
      --metadata-include stringArray        Include metadatas matching pattern
      --metadata-include-from stringArray   Read metadata include patterns from file (use - to read from stdin)
      --min-age Duration                    Only transfer files older than this in s or suffix ms|s|m|h|d|w|M|y (default off)
      --min-size SizeSuffix                 Only transfer files bigger than this in KiB or suffix B|K|M|G|T|P (default off)</code></pre>
<h2 id="see-also-74">See Also</h2>
<ul>
<li><a href="https://rclone.org/commands/rclone_serve/">rclone serve</a> - Serve a remote over a protocol.</li>
</ul>
<h1 id="rclone-serve-nfs">rclone serve nfs</h1>
<p>Serve the remote as an NFS mount</p>
<h2 id="synopsis-67">Synopsis</h2>
<p>Create an NFS server that serves the given remote over the network.</p>
<p>This implements an NFSv3 server to serve any rclone remote via NFS.</p>
<p>The primary purpose for this command is to enable the <a href="https://rclone.org/commands/rclone_mount/">mount command</a> on recent macOS versions where installing FUSE is very cumbersome.</p>
<p>This server does not implement any authentication so any client will be able to access the data. To limit access, you can use <code>serve nfs</code> on the loopback address or rely on secure tunnels (such as SSH) or use firewalling.</p>
<p>For this reason, by default, a random TCP port is chosen and the loopback interface is used for the listening address by default; meaning that it is only available to the local machine. If you want other machines to access the NFS mount over local network, you need to specify the listening address and port using the <code>--addr</code> flag.</p>
<p>Modifying files through the NFS protocol requires VFS caching. Usually you will need to specify <code>--vfs-cache-mode</code> in order to be able to write to the mountpoint (<code>full</code> is recommended). If you don't specify VFS cache mode, the mount will be read-only.</p>
<p><code>--nfs-cache-type</code> controls the type of the NFS handle cache. By default this is <code>memory</code> where new handles will be randomly allocated when needed. These are stored in memory. If the server is restarted the handle cache will be lost and connected NFS clients will get stale handle errors.</p>
<p><code>--nfs-cache-type disk</code> uses an on disk NFS handle cache. Rclone hashes the path of the object and stores it in a file named after the hash. These hashes are stored on disk the directory controlled by <code>--cache-dir</code> or the exact directory may be specified with <code>--nfs-cache-dir</code>. Using this means that the NFS server can be restarted at will without affecting the connected clients.</p>
<p><code>--nfs-cache-type symlink</code> is similar to <code>--nfs-cache-type disk</code> in that it uses an on disk cache, but the cache entries are held as symlinks. Rclone will use the handle of the underlying file as the NFS handle which improves performance. This sort of cache can't be backed up and restored as the underlying handles will change. This is Linux only.</p>
<p><code>--nfs-cache-handle-limit</code> controls the maximum number of cached NFS handles stored by the caching handler. This should not be set too low or you may experience errors when trying to access files. The default is <code>1000000</code>, but consider lowering this limit if the server's system resource usage causes problems. This is only used by the <code>memory</code> type cache.</p>
<p>To serve NFS over the network use following command:</p>
<pre><code>rclone serve nfs remote: --addr 0.0.0.0:$PORT --vfs-cache-mode=full</code></pre>
<p>This specifies a port that can be used in the mount command. To mount the server under Linux/macOS, use the following command:</p>
<pre><code>mount -t nfs -o port=$PORT,mountport=$PORT,tcp $HOSTNAME:/ path/to/mountpoint</code></pre>
<p>Where <code>$PORT</code> is the same port number used in the <code>serve nfs</code> command and <code>$HOSTNAME</code> is the network address of the machine that <code>serve nfs</code> was run on.</p>
<p>This command is only available on Unix platforms.</p>
<h2 id="vfs---virtual-file-system-6">VFS - Virtual File System</h2>
<p>This command uses the VFS layer. This adapts the cloud storage objects that rclone uses into something which looks much more like a disk filing system.</p>
<p>Cloud storage objects have lots of properties which aren't like disk files - you can't extend them or write to the middle of them, so the VFS layer has to deal with that. Because there is no one right way of doing this there are various options explained below.</p>
<p>The VFS layer also implements a directory cache - this caches info about files and directories (but not the data) in memory.</p>
<h2 id="vfs-directory-cache-6">VFS Directory Cache</h2>
<p>Using the <code>--dir-cache-time</code> flag, you can control how long a directory should be considered up to date and not refreshed from the backend. Changes made through the VFS will appear immediately or invalidate the cache.</p>
<pre><code>--dir-cache-time duration   Time to cache directory entries for (default 5m0s)
--poll-interval duration    Time to wait between polling for changes. Must be smaller than dir-cache-time. Only on supported remotes. Set to 0 to disable (default 1m0s)</code></pre>
<p>However, changes made directly on the cloud storage by the web interface or a different copy of rclone will only be picked up once the directory cache expires if the backend configured does not support polling for changes. If the backend supports polling, changes will be picked up within the polling interval.</p>
<p>You can send a <code>SIGHUP</code> signal to rclone for it to flush all directory caches, regardless of how old they are. Assuming only one rclone instance is running, you can reset the cache like this:</p>
<pre><code>kill -SIGHUP $(pidof rclone)</code></pre>
<p>If you configure rclone with a <a href="/rc">remote control</a> then you can use rclone rc to flush the whole directory cache:</p>
<pre><code>rclone rc vfs/forget</code></pre>
<p>Or individual files or directories:</p>
<pre><code>rclone rc vfs/forget file=path/to/file dir=path/to/dir</code></pre>
<h2 id="vfs-file-buffering-6">VFS File Buffering</h2>
<p>The <code>--buffer-size</code> flag determines the amount of memory, that will be used to buffer data in advance.</p>
<p>Each open file will try to keep the specified amount of data in memory at all times. The buffered data is bound to one open file and won't be shared.</p>
<p>This flag is a upper limit for the used memory per open file. The buffer will only use memory for data that is downloaded but not not yet read. If the buffer is empty, only a small amount of memory will be used.</p>
<p>The maximum memory used by rclone for buffering can be up to <code>--buffer-size * open files</code>.</p>
<h2 id="vfs-file-caching-6">VFS File Caching</h2>
<p>These flags control the VFS file caching options. File caching is necessary to make the VFS layer appear compatible with a normal file system. It can be disabled at the cost of some compatibility.</p>
<p>For example you'll need to enable VFS caching if you want to read and write simultaneously to a file. See below for more details.</p>
<p>Note that the VFS cache is separate from the cache backend and you may find that you need one or the other or both.</p>
<pre><code>--cache-dir string                     Directory rclone will use for caching.
--vfs-cache-mode CacheMode             Cache mode off|minimal|writes|full (default off)
--vfs-cache-max-age duration           Max time since last access of objects in the cache (default 1h0m0s)
--vfs-cache-max-size SizeSuffix        Max total size of objects in the cache (default off)
--vfs-cache-min-free-space SizeSuffix  Target minimum free space on the disk containing the cache (default off)
--vfs-cache-poll-interval duration     Interval to poll the cache for stale objects (default 1m0s)
--vfs-write-back duration              Time to writeback files after last use when using cache (default 5s)</code></pre>
<p>If run with <code>-vv</code> rclone will print the location of the file cache. The files are stored in the user cache file area which is OS dependent but can be controlled with <code>--cache-dir</code> or setting the appropriate environment variable.</p>
<p>The cache has 4 different modes selected by <code>--vfs-cache-mode</code>. The higher the cache mode the more compatible rclone becomes at the cost of using disk space.</p>
<p>Note that files are written back to the remote only when they are closed and if they haven't been accessed for <code>--vfs-write-back</code> seconds. If rclone is quit or dies with files that haven't been uploaded, these will be uploaded next time rclone is run with the same flags.</p>
<p>If using <code>--vfs-cache-max-size</code> or <code>--vfs-cache-min-free-size</code> note that the cache may exceed these quotas for two reasons. Firstly because it is only checked every <code>--vfs-cache-poll-interval</code>. Secondly because open files cannot be evicted from the cache. When <code>--vfs-cache-max-size</code> or <code>--vfs-cache-min-free-size</code> is exceeded, rclone will attempt to evict the least accessed files from the cache first. rclone will start with files that haven't been accessed for the longest. This cache flushing strategy is efficient and more relevant files are likely to remain cached.</p>
<p>The <code>--vfs-cache-max-age</code> will evict files from the cache after the set time since last access has passed. The default value of 1 hour will start evicting files from cache that haven't been accessed for 1 hour. When a cached file is accessed the 1 hour timer is reset to 0 and will wait for 1 more hour before evicting. Specify the time with standard notation, s, m, h, d, w .</p>
<p>You <strong>should not</strong> run two copies of rclone using the same VFS cache with the same or overlapping remotes if using <code>--vfs-cache-mode &gt; off</code>. This can potentially cause data corruption if you do. You can work around this by giving each rclone its own cache hierarchy with <code>--cache-dir</code>. You don't need to worry about this if the remotes in use don't overlap.</p>
<h3 id="vfs-cache-mode-off-6">--vfs-cache-mode off</h3>
<p>In this mode (the default) the cache will read directly from the remote and write directly to the remote without caching anything on disk.</p>
<p>This will mean some operations are not possible</p>
<ul>
<li>Files can't be opened for both read AND write</li>
<li>Files opened for write can't be seeked</li>
<li>Existing files opened for write must have O_TRUNC set</li>
<li>Files open for read with O_TRUNC will be opened write only</li>
<li>Files open for write only will behave as if O_TRUNC was supplied</li>
<li>Open modes O_APPEND, O_TRUNC are ignored</li>
<li>If an upload fails it can't be retried</li>
</ul>
<h3 id="vfs-cache-mode-minimal-6">--vfs-cache-mode minimal</h3>
<p>This is very similar to "off" except that files opened for read AND write will be buffered to disk. This means that files opened for write will be a lot more compatible, but uses the minimal disk space.</p>
<p>These operations are not possible</p>
<ul>
<li>Files opened for write only can't be seeked</li>
<li>Existing files opened for write must have O_TRUNC set</li>
<li>Files opened for write only will ignore O_APPEND, O_TRUNC</li>
<li>If an upload fails it can't be retried</li>
</ul>
<h3 id="vfs-cache-mode-writes-6">--vfs-cache-mode writes</h3>
<p>In this mode files opened for read only are still read directly from the remote, write only and read/write files are buffered to disk first.</p>
<p>This mode should support all normal file system operations.</p>
<p>If an upload fails it will be retried at exponentially increasing intervals up to 1 minute.</p>
<h3 id="vfs-cache-mode-full-6">--vfs-cache-mode full</h3>
<p>In this mode all reads and writes are buffered to and from disk. When data is read from the remote this is buffered to disk as well.</p>
<p>In this mode the files in the cache will be sparse files and rclone will keep track of which bits of the files it has downloaded.</p>
<p>So if an application only reads the starts of each file, then rclone will only buffer the start of the file. These files will appear to be their full size in the cache, but they will be sparse files with only the data that has been downloaded present in them.</p>
<p>This mode should support all normal file system operations and is otherwise identical to <code>--vfs-cache-mode</code> writes.</p>
<p>When reading a file rclone will read <code>--buffer-size</code> plus <code>--vfs-read-ahead</code> bytes ahead. The <code>--buffer-size</code> is buffered in memory whereas the <code>--vfs-read-ahead</code> is buffered on disk.</p>
<p>When using this mode it is recommended that <code>--buffer-size</code> is not set too large and <code>--vfs-read-ahead</code> is set large if required.</p>
<p><strong>IMPORTANT</strong> not all file systems support sparse files. In particular FAT/exFAT do not. Rclone will perform very badly if the cache directory is on a filesystem which doesn't support sparse files and it will log an ERROR message if one is detected.</p>
<h3 id="fingerprinting-6">Fingerprinting</h3>
<p>Various parts of the VFS use fingerprinting to see if a local file copy has changed relative to a remote file. Fingerprints are made from:</p>
<ul>
<li>size</li>
<li>modification time</li>
<li>hash</li>
</ul>
<p>where available on an object.</p>
<p>On some backends some of these attributes are slow to read (they take an extra API call per object, or extra work per object).</p>
<p>For example <code>hash</code> is slow with the <code>local</code> and <code>sftp</code> backends as they have to read the entire file and hash it, and <code>modtime</code> is slow with the <code>s3</code>, <code>swift</code>, <code>ftp</code> and <code>qinqstor</code> backends because they need to do an extra API call to fetch it.</p>
<p>If you use the <code>--vfs-fast-fingerprint</code> flag then rclone will not include the slow operations in the fingerprint. This makes the fingerprinting less accurate but much faster and will improve the opening time of cached files.</p>
<p>If you are running a vfs cache over <code>local</code>, <code>s3</code> or <code>swift</code> backends then using this flag is recommended.</p>
<p>Note that if you change the value of this flag, the fingerprints of the files in the cache may be invalidated and the files will need to be downloaded again.</p>
<h2 id="vfs-chunked-reading-6">VFS Chunked Reading</h2>
<p>When rclone reads files from a remote it reads them in chunks. This means that rather than requesting the whole file rclone reads the chunk specified. This can reduce the used download quota for some remotes by requesting only chunks from the remote that are actually read, at the cost of an increased number of requests.</p>
<p>These flags control the chunking:</p>
<pre><code>--vfs-read-chunk-size SizeSuffix        Read the source objects in chunks (default 128M)
--vfs-read-chunk-size-limit SizeSuffix  Max chunk doubling size (default off)
--vfs-read-chunk-streams int            The number of parallel streams to read at once</code></pre>
<p>The chunking behaves differently depending on the <code>--vfs-read-chunk-streams</code> parameter.</p>
<h3 id="vfs-read-chunk-streams-0-12"><code>--vfs-read-chunk-streams</code> == 0</h3>
<p>Rclone will start reading a chunk of size <code>--vfs-read-chunk-size</code>, and then double the size for each read. When <code>--vfs-read-chunk-size-limit</code> is specified, and greater than <code>--vfs-read-chunk-size</code>, the chunk size for each open file will get doubled only until the specified value is reached. If the value is "off", which is the default, the limit is disabled and the chunk size will grow indefinitely.</p>
<p>With <code>--vfs-read-chunk-size 100M</code> and <code>--vfs-read-chunk-size-limit 0</code> the following parts will be downloaded: 0-100M, 100M-200M, 200M-300M, 300M-400M and so on. When <code>--vfs-read-chunk-size-limit 500M</code> is specified, the result would be 0-100M, 100M-300M, 300M-700M, 700M-1200M, 1200M-1700M and so on.</p>
<p>Setting <code>--vfs-read-chunk-size</code> to <code>0</code> or "off" disables chunked reading.</p>
<p>The chunks will not be buffered in memory.</p>
<h3 id="vfs-read-chunk-streams-0-13"><code>--vfs-read-chunk-streams</code> &gt; 0</h3>
<p>Rclone reads <code>--vfs-read-chunk-streams</code> chunks of size <code>--vfs-read-chunk-size</code> concurrently. The size for each read will stay constant.</p>
<p>This improves performance performance massively on high latency links or very high bandwidth links to high performance object stores.</p>
<p>Some experimentation will be needed to find the optimum values of <code>--vfs-read-chunk-size</code> and <code>--vfs-read-chunk-streams</code> as these will depend on the backend in use and the latency to the backend.</p>
<p>For high performance object stores (eg AWS S3) a reasonable place to start might be <code>--vfs-read-chunk-streams 16</code> and <code>--vfs-read-chunk-size 4M</code>. In testing with AWS S3 the performance scaled roughly as the <code>--vfs-read-chunk-streams</code> setting.</p>
<p>Similar settings should work for high latency links, but depending on the latency they may need more <code>--vfs-read-chunk-streams</code> in order to get the throughput.</p>
<h2 id="vfs-performance-6">VFS Performance</h2>
<p>These flags may be used to enable/disable features of the VFS for performance or other reasons. See also the <a href="#vfs-chunked-reading">chunked reading</a> feature.</p>
<p>In particular S3 and Swift benefit hugely from the <code>--no-modtime</code> flag (or use <code>--use-server-modtime</code> for a slightly different effect) as each read of the modification time takes a transaction.</p>
<pre><code>--no-checksum     Don&#39;t compare checksums on up/download.
--no-modtime      Don&#39;t read/write the modification time (can speed things up).
--no-seek         Don&#39;t allow seeking in files.
--read-only       Only allow read-only access.</code></pre>
<p>Sometimes rclone is delivered reads or writes out of order. Rather than seeking rclone will wait a short time for the in sequence read or write to come in. These flags only come into effect when not using an on disk cache file.</p>
<pre><code>--vfs-read-wait duration   Time to wait for in-sequence read before seeking (default 20ms)
--vfs-write-wait duration  Time to wait for in-sequence write before giving error (default 1s)</code></pre>
<p>When using VFS write caching (<code>--vfs-cache-mode</code> with value writes or full), the global flag <code>--transfers</code> can be set to adjust the number of parallel uploads of modified files from the cache (the related global flag <code>--checkers</code> has no effect on the VFS).</p>
<pre><code>--transfers int  Number of file transfers to run in parallel (default 4)</code></pre>
<h2 id="vfs-case-sensitivity-6">VFS Case Sensitivity</h2>
<p>Linux file systems are case-sensitive: two files can differ only by case, and the exact case must be used when opening a file.</p>
<p>File systems in modern Windows are case-insensitive but case-preserving: although existing files can be opened using any case, the exact case used to create the file is preserved and available for programs to query. It is not allowed for two files in the same directory to differ only by case.</p>
<p>Usually file systems on macOS are case-insensitive. It is possible to make macOS file systems case-sensitive but that is not the default.</p>
<p>The <code>--vfs-case-insensitive</code> VFS flag controls how rclone handles these two cases. If its value is "false", rclone passes file names to the remote as-is. If the flag is "true" (or appears without a value on the command line), rclone may perform a "fixup" as explained below.</p>
<p>The user may specify a file name to open/delete/rename/etc with a case different than what is stored on the remote. If an argument refers to an existing file with exactly the same name, then the case of the existing file on the disk will be used. However, if a file name with exactly the same name is not found but a name differing only by case exists, rclone will transparently fixup the name. This fixup happens only when an existing file is requested. Case sensitivity of file names created anew by rclone is controlled by the underlying remote.</p>
<p>Note that case sensitivity of the operating system running rclone (the target) may differ from case sensitivity of a file system presented by rclone (the source). The flag controls whether "fixup" is performed to satisfy the target.</p>
<p>If the flag is not provided on the command line, then its default value depends on the operating system where rclone runs: "true" on Windows and macOS, "false" otherwise. If the flag is provided without a value, then it is "true".</p>
<p>The <code>--no-unicode-normalization</code> flag controls whether a similar "fixup" is performed for filenames that differ but are <a href="https://en.wikipedia.org/wiki/Unicode_equivalence">canonically equivalent</a> with respect to unicode. Unicode normalization can be particularly helpful for users of macOS, which prefers form NFD instead of the NFC used by most other platforms. It is therefore highly recommended to keep the default of <code>false</code> on macOS, to avoid encoding compatibility issues.</p>
<p>In the (probably unlikely) event that a directory has multiple duplicate filenames after applying case and unicode normalization, the <code>--vfs-block-norm-dupes</code> flag allows hiding these duplicates. This comes with a performance tradeoff, as rclone will have to scan the entire directory for duplicates when listing a directory. For this reason, it is recommended to leave this disabled if not needed. However, macOS users may wish to consider using it, as otherwise, if a remote directory contains both NFC and NFD versions of the same filename, an odd situation will occur: both versions of the file will be visible in the mount, and both will appear to be editable, however, editing either version will actually result in only the NFD version getting edited under the hood. <code>--vfs-block- norm-dupes</code> prevents this confusion by detecting this scenario, hiding the duplicates, and logging an error, similar to how this is handled in <code>rclone sync</code>.</p>
<h2 id="vfs-disk-options-6">VFS Disk Options</h2>
<p>This flag allows you to manually set the statistics about the filing system. It can be useful when those statistics cannot be read correctly automatically.</p>
<pre><code>--vfs-disk-space-total-size    Manually set the total disk space size (example: 256G, default: -1)</code></pre>
<h2 id="alternate-report-of-used-bytes-6">Alternate report of used bytes</h2>
<p>Some backends, most notably S3, do not report the amount of bytes used. If you need this information to be available when running <code>df</code> on the filesystem, then pass the flag <code>--vfs-used-is-size</code> to rclone. With this flag set, instead of relying on the backend to report this information, rclone will scan the whole remote similar to <code>rclone size</code> and compute the total used space itself.</p>
<p><em>WARNING.</em> Contrary to <code>rclone size</code>, this flag ignores filters so that the result is accurate. However, this is very inefficient and may cost lots of API calls resulting in extra charges. Use it as a last resort and only with caching.</p>
<pre><code>rclone serve nfs remote:path [flags]</code></pre>
<h2 id="options-75">Options</h2>
<pre><code>      --addr string                            IPaddress:Port or :Port to bind server to
      --dir-cache-time Duration                Time to cache directory entries for (default 5m0s)
      --dir-perms FileMode                     Directory permissions (default 777)
      --file-perms FileMode                    File permissions (default 666)
      --gid uint32                             Override the gid field set by the filesystem (not supported on Windows) (default 1000)
  -h, --help                                   help for nfs
      --nfs-cache-dir string                   The directory the NFS handle cache will use if set
      --nfs-cache-handle-limit int             max file handles cached simultaneously (min 5) (default 1000000)
      --nfs-cache-type memory|disk|symlink     Type of NFS handle cache to use (default memory)
      --no-checksum                            Don&#39;t compare checksums on up/download
      --no-modtime                             Don&#39;t read/write the modification time (can speed things up)
      --no-seek                                Don&#39;t allow seeking in files
      --poll-interval Duration                 Time to wait between polling for changes, must be smaller than dir-cache-time and only on supported remotes (set 0 to disable) (default 1m0s)
      --read-only                              Only allow read-only access
      --uid uint32                             Override the uid field set by the filesystem (not supported on Windows) (default 1000)
      --umask FileMode                         Override the permission bits set by the filesystem (not supported on Windows) (default 002)
      --vfs-block-norm-dupes                   If duplicate filenames exist in the same directory (after normalization), log an error and hide the duplicates (may have a performance cost)
      --vfs-cache-max-age Duration             Max time since last access of objects in the cache (default 1h0m0s)
      --vfs-cache-max-size SizeSuffix          Max total size of objects in the cache (default off)
      --vfs-cache-min-free-space SizeSuffix    Target minimum free space on the disk containing the cache (default off)
      --vfs-cache-mode CacheMode               Cache mode off|minimal|writes|full (default off)
      --vfs-cache-poll-interval Duration       Interval to poll the cache for stale objects (default 1m0s)
      --vfs-case-insensitive                   If a file name not found, find a case insensitive match
      --vfs-disk-space-total-size SizeSuffix   Specify the total space of disk (default off)
      --vfs-fast-fingerprint                   Use fast (less accurate) fingerprints for change detection
      --vfs-read-ahead SizeSuffix              Extra read ahead over --buffer-size when using cache-mode full
      --vfs-read-chunk-size SizeSuffix         Read the source objects in chunks (default 128Mi)
      --vfs-read-chunk-size-limit SizeSuffix   If greater than --vfs-read-chunk-size, double the chunk size after each chunk read, until the limit is reached (&#39;off&#39; is unlimited) (default off)
      --vfs-read-chunk-streams int             The number of parallel streams to read at once
      --vfs-read-wait Duration                 Time to wait for in-sequence read before seeking (default 20ms)
      --vfs-refresh                            Refreshes the directory cache recursively in the background on start
      --vfs-used-is-size rclone size           Use the rclone size algorithm for Used size
      --vfs-write-back Duration                Time to writeback files after last use when using cache (default 5s)
      --vfs-write-wait Duration                Time to wait for in-sequence write before giving error (default 1s)</code></pre>
<p>Options shared with other commands are described next. See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
<h3 id="filter-options-27">Filter Options</h3>
<p>Flags for filtering directory listings</p>
<pre><code>      --delete-excluded                     Delete files on dest excluded from sync
      --exclude stringArray                 Exclude files matching pattern
      --exclude-from stringArray            Read file exclude patterns from file (use - to read from stdin)
      --exclude-if-present stringArray      Exclude directories if filename is present
      --files-from stringArray              Read list of source-file names from file (use - to read from stdin)
      --files-from-raw stringArray          Read list of source-file names from file without any processing of lines (use - to read from stdin)
  -f, --filter stringArray                  Add a file filtering rule
      --filter-from stringArray             Read file filtering patterns from a file (use - to read from stdin)
      --ignore-case                         Ignore case in filters (case insensitive)
      --include stringArray                 Include files matching pattern
      --include-from stringArray            Read file include patterns from file (use - to read from stdin)
      --max-age Duration                    Only transfer files younger than this in s or suffix ms|s|m|h|d|w|M|y (default off)
      --max-depth int                       If set limits the recursion depth to this (default -1)
      --max-size SizeSuffix                 Only transfer files smaller than this in KiB or suffix B|K|M|G|T|P (default off)
      --metadata-exclude stringArray        Exclude metadatas matching pattern
      --metadata-exclude-from stringArray   Read metadata exclude patterns from file (use - to read from stdin)
      --metadata-filter stringArray         Add a metadata filtering rule
      --metadata-filter-from stringArray    Read metadata filtering patterns from a file (use - to read from stdin)
      --metadata-include stringArray        Include metadatas matching pattern
      --metadata-include-from stringArray   Read metadata include patterns from file (use - to read from stdin)
      --min-age Duration                    Only transfer files older than this in s or suffix ms|s|m|h|d|w|M|y (default off)
      --min-size SizeSuffix                 Only transfer files bigger than this in KiB or suffix B|K|M|G|T|P (default off)</code></pre>
<h2 id="see-also-75">See Also</h2>
<ul>
<li><a href="https://rclone.org/commands/rclone_serve/">rclone serve</a> - Serve a remote over a protocol.</li>
</ul>
<h1 id="rclone-serve-restic">rclone serve restic</h1>
<p>Serve the remote for restic's REST API.</p>
<h2 id="synopsis-68">Synopsis</h2>
<p>Run a basic web server to serve a remote over restic's REST backend API over HTTP. This allows restic to use rclone as a data storage mechanism for cloud providers that restic does not support directly.</p>
<p><a href="https://restic.net/">Restic</a> is a command-line program for doing backups.</p>
<p>The server will log errors. Use -v to see access logs.</p>
<p><code>--bwlimit</code> will be respected for file transfers. Use <code>--stats</code> to control the stats printing.</p>
<h2 id="setting-up-rclone-for-use-by-restic">Setting up rclone for use by restic</h2>
<p>First <a href="https://rclone.org/docs/#configure">set up a remote for your chosen cloud provider</a>.</p>
<p>Once you have set up the remote, check it is working with, for example "rclone lsd remote:". You may have called the remote something other than "remote:" - just substitute whatever you called it in the following instructions.</p>
<p>Now start the rclone restic server</p>
<pre><code>rclone serve restic -v remote:backup</code></pre>
<p>Where you can replace "backup" in the above by whatever path in the remote you wish to use.</p>
<p>By default this will serve on "localhost:8080" you can change this with use of the <code>--addr</code> flag.</p>
<p>You might wish to start this server on boot.</p>
<p>Adding <code>--cache-objects=false</code> will cause rclone to stop caching objects returned from the List call. Caching is normally desirable as it speeds up downloading objects, saves transactions and uses very little memory.</p>
<h2 id="setting-up-restic-to-use-rclone">Setting up restic to use rclone</h2>
<p>Now you can <a href="http://restic.readthedocs.io/en/latest/030_preparing_a_new_repo.html#rest-server">follow the restic instructions</a> on setting up restic.</p>
<p>Note that you will need restic 0.8.2 or later to interoperate with rclone.</p>
<p>For the example above you will want to use "http://localhost:8080/" as the URL for the REST server.</p>
<p>For example:</p>
<pre><code>$ export RESTIC_REPOSITORY=rest:http://localhost:8080/
$ export RESTIC_PASSWORD=yourpassword
$ restic init
created restic backend 8b1a4b56ae at rest:http://localhost:8080/

Please note that knowledge of your password is required to access
the repository. Losing your password means that your data is
irrecoverably lost.
$ restic backup /path/to/files/to/backup
scan [/path/to/files/to/backup]
scanned 189 directories, 312 files in 0:00
[0:00] 100.00%  38.128 MiB / 38.128 MiB  501 / 501 items  0 errors  ETA 0:00
duration: 0:00
snapshot 45c8fdd8 saved</code></pre>
<h3 id="multiple-repositories">Multiple repositories</h3>
<p>Note that you can use the endpoint to host multiple repositories. Do this by adding a directory name or path after the URL. Note that these <strong>must</strong> end with /. Eg</p>
<pre><code>$ export RESTIC_REPOSITORY=rest:http://localhost:8080/user1repo/
# backup user1 stuff
$ export RESTIC_REPOSITORY=rest:http://localhost:8080/user2repo/
# backup user2 stuff</code></pre>
<h3 id="private-repositories">Private repositories</h3>
<p>The<code>--private-repos</code> flag can be used to limit users to repositories starting with a path of <code>/&lt;username&gt;/</code>.</p>
<h2 id="server-options-4">Server options</h2>
<p>Use <code>--addr</code> to specify which IP address and port the server should listen on, eg <code>--addr 1.2.3.4:8000</code> or <code>--addr :8080</code> to listen to all IPs. By default it only listens on localhost. You can use port :0 to let the OS choose an available port.</p>
<p>If you set <code>--addr</code> to listen on a public or LAN accessible IP address then using Authentication is advised - see the next section for info.</p>
<p>You can use a unix socket by setting the url to <code>unix:///path/to/socket</code> or just by using an absolute path name. Note that unix sockets bypass the authentication - this is expected to be done with file system permissions.</p>
<p><code>--addr</code> may be repeated to listen on multiple IPs/ports/sockets. Socket activation, described further below, can also be used to accomplish the same.</p>
<p><code>--server-read-timeout</code> and <code>--server-write-timeout</code> can be used to control the timeouts on the server. Note that this is the total time for a transfer.</p>
<p><code>--max-header-bytes</code> controls the maximum number of bytes the server will accept in the HTTP header.</p>
<p><code>--baseurl</code> controls the URL prefix that rclone serves from. By default rclone will serve from the root. If you used <code>--baseurl "/rclone"</code> then rclone would serve from a URL starting with "/rclone/". This is useful if you wish to proxy rclone serve. Rclone automatically inserts leading and trailing "/" on <code>--baseurl</code>, so <code>--baseurl "rclone"</code>, <code>--baseurl "/rclone"</code> and <code>--baseurl "/rclone/"</code> are all treated identically.</p>
<h3 id="tls-ssl-2">TLS (SSL)</h3>
<p>By default this will serve over http. If you want you can serve over https. You will need to supply the <code>--cert</code> and <code>--key</code> flags. If you wish to do client side certificate validation then you will need to supply <code>--client-ca</code> also.</p>
<p><code>--cert</code> should be a either a PEM encoded certificate or a concatenation of that with the CA certificate. <code>--key</code> should be the PEM encoded private key and <code>--client-ca</code> should be the PEM encoded client certificate authority certificate.</p>
<p><code>--min-tls-version</code> is minimum TLS version that is acceptable. Valid values are "tls1.0", "tls1.1", "tls1.2" and "tls1.3" (default "tls1.0").</p>
<h2 id="socket-activation-2">Socket activation</h2>
<p>Instead of the listening addresses specified above, rclone will listen to all FDs passed by the service manager, if any (and ignore any arguments passed by --addr`).</p>
<p>This allows rclone to be a socket-activated service. It can be configured with .socket and .service unit files as described in https://www.freedesktop.org/software/systemd/man/latest/systemd.socket.html</p>
<p>Socket activation can be tested ad-hoc with the <code>systemd-socket-activate</code>command</p>
<pre><code>   systemd-socket-activate -l 8000 -- rclone serve</code></pre>
<p>This will socket-activate rclone on the first connection to port 8000 over TCP. ### Authentication</p>
<p>By default this will serve files without needing a login.</p>
<p>You can either use an htpasswd file which can take lots of users, or set a single username and password with the <code>--user</code> and <code>--pass</code> flags.</p>
<p>If no static users are configured by either of the above methods, and client certificates are required by the <code>--client-ca</code> flag passed to the server, the client certificate common name will be considered as the username.</p>
<p>Use <code>--htpasswd /path/to/htpasswd</code> to provide an htpasswd file. This is in standard apache format and supports MD5, SHA1 and BCrypt for basic authentication. Bcrypt is recommended.</p>
<p>To create an htpasswd file:</p>
<pre><code>touch htpasswd
htpasswd -B htpasswd user
htpasswd -B htpasswd anotherUser</code></pre>
<p>The password file can be updated while rclone is running.</p>
<p>Use <code>--realm</code> to set the authentication realm.</p>
<p>Use <code>--salt</code> to change the password hashing salt from the default.</p>
<pre><code>rclone serve restic remote:path [flags]</code></pre>
<h2 id="options-76">Options</h2>
<pre><code>      --addr stringArray                IPaddress:Port, :Port or [unix://]/path/to/socket to bind server to (default [127.0.0.1:8080])
      --allow-origin string             Origin which cross-domain request (CORS) can be executed from
      --append-only                     Disallow deletion of repository data
      --baseurl string                  Prefix for URLs - leave blank for root
      --cache-objects                   Cache listed objects (default true)
      --cert string                     TLS PEM key (concatenation of certificate and CA certificate)
      --client-ca string                Client certificate authority to verify clients with
  -h, --help                            help for restic
      --htpasswd string                 A htpasswd file - if not provided no authentication is done
      --key string                      TLS PEM Private key
      --max-header-bytes int            Maximum size of request header (default 4096)
      --min-tls-version string          Minimum TLS version that is acceptable (default &quot;tls1.0&quot;)
      --pass string                     Password for authentication
      --private-repos                   Users can only access their private repo
      --realm string                    Realm for authentication
      --salt string                     Password hashing salt (default &quot;dlPL2MqE&quot;)
      --server-read-timeout Duration    Timeout for server reading data (default 1h0m0s)
      --server-write-timeout Duration   Timeout for server writing data (default 1h0m0s)
      --stdio                           Run an HTTP2 server on stdin/stdout
      --user string                     User name for authentication</code></pre>
<p>See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
<h2 id="see-also-76">See Also</h2>
<ul>
<li><a href="https://rclone.org/commands/rclone_serve/">rclone serve</a> - Serve a remote over a protocol.</li>
</ul>
<h1 id="rclone-serve-s3">rclone serve s3</h1>
<p>Serve remote:path over s3.</p>
<h2 id="synopsis-69">Synopsis</h2>
<p><code>serve s3</code> implements a basic s3 server that serves a remote via s3. This can be viewed with an s3 client, or you can make an <a href="https://rclone.org/s3/">s3 type remote</a> to read and write to it with rclone.</p>
<p><code>serve s3</code> is considered <strong>Experimental</strong> so use with care.</p>
<p>S3 server supports Signature Version 4 authentication. Just use <code>--auth-key accessKey,secretKey</code> and set the <code>Authorization</code> header correctly in the request. (See the <a href="https://docs.aws.amazon.com/general/latest/gr/signature-version-4.html">AWS docs</a>).</p>
<p><code>--auth-key</code> can be repeated for multiple auth pairs. If <code>--auth-key</code> is not provided then <code>serve s3</code> will allow anonymous access.</p>
<p>Please note that some clients may require HTTPS endpoints. See <a href="#ssl-tls">the SSL docs</a> for more information.</p>
<p>This command uses the <a href="#vfs-virtual-file-system">VFS directory cache</a>. All the functionality will work with <code>--vfs-cache-mode off</code>. Using <code>--vfs-cache-mode full</code> (or <code>writes</code>) can be used to cache objects locally to improve performance.</p>
<p>Use <code>--force-path-style=false</code> if you want to use the bucket name as a part of the hostname (such as mybucket.local)</p>
<p>Use <code>--etag-hash</code> if you want to change the hash uses for the <code>ETag</code>. Note that using anything other than <code>MD5</code> (the default) is likely to cause problems for S3 clients which rely on the Etag being the MD5.</p>
<h2 id="quickstart-1">Quickstart</h2>
<p>For a simple set up, to serve <code>remote:path</code> over s3, run the server like this:</p>
<pre><code>rclone serve s3 --auth-key ACCESS_KEY_ID,SECRET_ACCESS_KEY remote:path</code></pre>
<p>For example, to use a simple folder in the filesystem, run the server with a command like this:</p>
<pre><code>rclone serve s3 --auth-key ACCESS_KEY_ID,SECRET_ACCESS_KEY local:/path/to/folder</code></pre>
<p>The <code>rclone.conf</code> for the server could look like this:</p>
<pre><code>[local]
type = local</code></pre>
<p>The <code>local</code> configuration is optional though. If you run the server with a <code>remote:path</code> like <code>/path/to/folder</code> (without the <code>local:</code> prefix and without an <code>rclone.conf</code> file), rclone will fall back to a default configuration, which will be visible as a warning in the logs. But it will run nonetheless.</p>
<p>This will be compatible with an rclone (client) remote configuration which is defined like this:</p>
<pre><code>[serves3]
type = s3
provider = Rclone
endpoint = http://127.0.0.1:8080/
access_key_id = ACCESS_KEY_ID
secret_access_key = SECRET_ACCESS_KEY
use_multipart_uploads = false</code></pre>
<p>Note that setting <code>disable_multipart_uploads = true</code> is to work around <a href="#bugs">a bug</a> which will be fixed in due course.</p>
<h2 id="bugs">Bugs</h2>
<p>When uploading multipart files <code>serve s3</code> holds all the parts in memory (see <a href="https://github.com/rclone/rclone/issues/7453">#7453</a>). This is a limitaton of the library rclone uses for serving S3 and will hopefully be fixed at some point.</p>
<p>Multipart server side copies do not work (see <a href="https://github.com/rclone/rclone/issues/7454">#7454</a>). These take a very long time and eventually fail. The default threshold for multipart server side copies is 5G which is the maximum it can be, so files above this side will fail to be server side copied.</p>
<p>For a current list of <code>serve s3</code> bugs see the <a href="https://github.com/rclone/rclone/labels/serve%20s3">serve s3</a> bug category on GitHub.</p>
<h2 id="limitations-2">Limitations</h2>
<p><code>serve s3</code> will treat all directories in the root as buckets and ignore all files in the root. You can use <code>CreateBucket</code> to create folders under the root, but you can't create empty folders under other folders not in the root.</p>
<p>When using <code>PutObject</code> or <code>DeleteObject</code>, rclone will automatically create or clean up empty folders. If you don't want to clean up empty folders automatically, use <code>--no-cleanup</code>.</p>
<p>When using <code>ListObjects</code>, rclone will use <code>/</code> when the delimiter is empty. This reduces backend requests with no effect on most operations, but if the delimiter is something other than <code>/</code> and empty, rclone will do a full recursive search of the backend, which can take some time.</p>
<p>Versioning is not currently supported.</p>
<p>Metadata will only be saved in memory other than the rclone <code>mtime</code> metadata which will be set as the modification time of the file.</p>
<h2 id="supported-operations">Supported operations</h2>
<p><code>serve s3</code> currently supports the following operations.</p>
<ul>
<li>Bucket
<ul>
<li><code>ListBuckets</code></li>
<li><code>CreateBucket</code></li>
<li><code>DeleteBucket</code></li>
</ul></li>
<li>Object
<ul>
<li><code>HeadObject</code></li>
<li><code>ListObjects</code></li>
<li><code>GetObject</code></li>
<li><code>PutObject</code></li>
<li><code>DeleteObject</code></li>
<li><code>DeleteObjects</code></li>
<li><code>CreateMultipartUpload</code></li>
<li><code>CompleteMultipartUpload</code></li>
<li><code>AbortMultipartUpload</code></li>
<li><code>CopyObject</code></li>
<li><code>UploadPart</code></li>
</ul></li>
</ul>
<p>Other operations will return error <code>Unimplemented</code>.</p>
<h3 id="authentication-3">Authentication</h3>
<p>By default this will serve files without needing a login.</p>
<p>You can either use an htpasswd file which can take lots of users, or set a single username and password with the <code>--user</code> and <code>--pass</code> flags.</p>
<p>If no static users are configured by either of the above methods, and client certificates are required by the <code>--client-ca</code> flag passed to the server, the client certificate common name will be considered as the username.</p>
<p>Use <code>--htpasswd /path/to/htpasswd</code> to provide an htpasswd file. This is in standard apache format and supports MD5, SHA1 and BCrypt for basic authentication. Bcrypt is recommended.</p>
<p>To create an htpasswd file:</p>
<pre><code>touch htpasswd
htpasswd -B htpasswd user
htpasswd -B htpasswd anotherUser</code></pre>
<p>The password file can be updated while rclone is running.</p>
<p>Use <code>--realm</code> to set the authentication realm.</p>
<p>Use <code>--salt</code> to change the password hashing salt from the default.</p>
<h2 id="server-options-5">Server options</h2>
<p>Use <code>--addr</code> to specify which IP address and port the server should listen on, eg <code>--addr 1.2.3.4:8000</code> or <code>--addr :8080</code> to listen to all IPs. By default it only listens on localhost. You can use port :0 to let the OS choose an available port.</p>
<p>If you set <code>--addr</code> to listen on a public or LAN accessible IP address then using Authentication is advised - see the next section for info.</p>
<p>You can use a unix socket by setting the url to <code>unix:///path/to/socket</code> or just by using an absolute path name. Note that unix sockets bypass the authentication - this is expected to be done with file system permissions.</p>
<p><code>--addr</code> may be repeated to listen on multiple IPs/ports/sockets. Socket activation, described further below, can also be used to accomplish the same.</p>
<p><code>--server-read-timeout</code> and <code>--server-write-timeout</code> can be used to control the timeouts on the server. Note that this is the total time for a transfer.</p>
<p><code>--max-header-bytes</code> controls the maximum number of bytes the server will accept in the HTTP header.</p>
<p><code>--baseurl</code> controls the URL prefix that rclone serves from. By default rclone will serve from the root. If you used <code>--baseurl "/rclone"</code> then rclone would serve from a URL starting with "/rclone/". This is useful if you wish to proxy rclone serve. Rclone automatically inserts leading and trailing "/" on <code>--baseurl</code>, so <code>--baseurl "rclone"</code>, <code>--baseurl "/rclone"</code> and <code>--baseurl "/rclone/"</code> are all treated identically.</p>
<h3 id="tls-ssl-3">TLS (SSL)</h3>
<p>By default this will serve over http. If you want you can serve over https. You will need to supply the <code>--cert</code> and <code>--key</code> flags. If you wish to do client side certificate validation then you will need to supply <code>--client-ca</code> also.</p>
<p><code>--cert</code> should be a either a PEM encoded certificate or a concatenation of that with the CA certificate. <code>--key</code> should be the PEM encoded private key and <code>--client-ca</code> should be the PEM encoded client certificate authority certificate.</p>
<p><code>--min-tls-version</code> is minimum TLS version that is acceptable. Valid values are "tls1.0", "tls1.1", "tls1.2" and "tls1.3" (default "tls1.0").</p>
<h2 id="socket-activation-3">Socket activation</h2>
<p>Instead of the listening addresses specified above, rclone will listen to all FDs passed by the service manager, if any (and ignore any arguments passed by --addr`).</p>
<p>This allows rclone to be a socket-activated service. It can be configured with .socket and .service unit files as described in https://www.freedesktop.org/software/systemd/man/latest/systemd.socket.html</p>
<p>Socket activation can be tested ad-hoc with the <code>systemd-socket-activate</code>command</p>
<pre><code>   systemd-socket-activate -l 8000 -- rclone serve</code></pre>
<p>This will socket-activate rclone on the first connection to port 8000 over TCP. ## VFS - Virtual File System</p>
<p>This command uses the VFS layer. This adapts the cloud storage objects that rclone uses into something which looks much more like a disk filing system.</p>
<p>Cloud storage objects have lots of properties which aren't like disk files - you can't extend them or write to the middle of them, so the VFS layer has to deal with that. Because there is no one right way of doing this there are various options explained below.</p>
<p>The VFS layer also implements a directory cache - this caches info about files and directories (but not the data) in memory.</p>
<h2 id="vfs-directory-cache-7">VFS Directory Cache</h2>
<p>Using the <code>--dir-cache-time</code> flag, you can control how long a directory should be considered up to date and not refreshed from the backend. Changes made through the VFS will appear immediately or invalidate the cache.</p>
<pre><code>--dir-cache-time duration   Time to cache directory entries for (default 5m0s)
--poll-interval duration    Time to wait between polling for changes. Must be smaller than dir-cache-time. Only on supported remotes. Set to 0 to disable (default 1m0s)</code></pre>
<p>However, changes made directly on the cloud storage by the web interface or a different copy of rclone will only be picked up once the directory cache expires if the backend configured does not support polling for changes. If the backend supports polling, changes will be picked up within the polling interval.</p>
<p>You can send a <code>SIGHUP</code> signal to rclone for it to flush all directory caches, regardless of how old they are. Assuming only one rclone instance is running, you can reset the cache like this:</p>
<pre><code>kill -SIGHUP $(pidof rclone)</code></pre>
<p>If you configure rclone with a <a href="/rc">remote control</a> then you can use rclone rc to flush the whole directory cache:</p>
<pre><code>rclone rc vfs/forget</code></pre>
<p>Or individual files or directories:</p>
<pre><code>rclone rc vfs/forget file=path/to/file dir=path/to/dir</code></pre>
<h2 id="vfs-file-buffering-7">VFS File Buffering</h2>
<p>The <code>--buffer-size</code> flag determines the amount of memory, that will be used to buffer data in advance.</p>
<p>Each open file will try to keep the specified amount of data in memory at all times. The buffered data is bound to one open file and won't be shared.</p>
<p>This flag is a upper limit for the used memory per open file. The buffer will only use memory for data that is downloaded but not not yet read. If the buffer is empty, only a small amount of memory will be used.</p>
<p>The maximum memory used by rclone for buffering can be up to <code>--buffer-size * open files</code>.</p>
<h2 id="vfs-file-caching-7">VFS File Caching</h2>
<p>These flags control the VFS file caching options. File caching is necessary to make the VFS layer appear compatible with a normal file system. It can be disabled at the cost of some compatibility.</p>
<p>For example you'll need to enable VFS caching if you want to read and write simultaneously to a file. See below for more details.</p>
<p>Note that the VFS cache is separate from the cache backend and you may find that you need one or the other or both.</p>
<pre><code>--cache-dir string                     Directory rclone will use for caching.
--vfs-cache-mode CacheMode             Cache mode off|minimal|writes|full (default off)
--vfs-cache-max-age duration           Max time since last access of objects in the cache (default 1h0m0s)
--vfs-cache-max-size SizeSuffix        Max total size of objects in the cache (default off)
--vfs-cache-min-free-space SizeSuffix  Target minimum free space on the disk containing the cache (default off)
--vfs-cache-poll-interval duration     Interval to poll the cache for stale objects (default 1m0s)
--vfs-write-back duration              Time to writeback files after last use when using cache (default 5s)</code></pre>
<p>If run with <code>-vv</code> rclone will print the location of the file cache. The files are stored in the user cache file area which is OS dependent but can be controlled with <code>--cache-dir</code> or setting the appropriate environment variable.</p>
<p>The cache has 4 different modes selected by <code>--vfs-cache-mode</code>. The higher the cache mode the more compatible rclone becomes at the cost of using disk space.</p>
<p>Note that files are written back to the remote only when they are closed and if they haven't been accessed for <code>--vfs-write-back</code> seconds. If rclone is quit or dies with files that haven't been uploaded, these will be uploaded next time rclone is run with the same flags.</p>
<p>If using <code>--vfs-cache-max-size</code> or <code>--vfs-cache-min-free-size</code> note that the cache may exceed these quotas for two reasons. Firstly because it is only checked every <code>--vfs-cache-poll-interval</code>. Secondly because open files cannot be evicted from the cache. When <code>--vfs-cache-max-size</code> or <code>--vfs-cache-min-free-size</code> is exceeded, rclone will attempt to evict the least accessed files from the cache first. rclone will start with files that haven't been accessed for the longest. This cache flushing strategy is efficient and more relevant files are likely to remain cached.</p>
<p>The <code>--vfs-cache-max-age</code> will evict files from the cache after the set time since last access has passed. The default value of 1 hour will start evicting files from cache that haven't been accessed for 1 hour. When a cached file is accessed the 1 hour timer is reset to 0 and will wait for 1 more hour before evicting. Specify the time with standard notation, s, m, h, d, w .</p>
<p>You <strong>should not</strong> run two copies of rclone using the same VFS cache with the same or overlapping remotes if using <code>--vfs-cache-mode &gt; off</code>. This can potentially cause data corruption if you do. You can work around this by giving each rclone its own cache hierarchy with <code>--cache-dir</code>. You don't need to worry about this if the remotes in use don't overlap.</p>
<h3 id="vfs-cache-mode-off-7">--vfs-cache-mode off</h3>
<p>In this mode (the default) the cache will read directly from the remote and write directly to the remote without caching anything on disk.</p>
<p>This will mean some operations are not possible</p>
<ul>
<li>Files can't be opened for both read AND write</li>
<li>Files opened for write can't be seeked</li>
<li>Existing files opened for write must have O_TRUNC set</li>
<li>Files open for read with O_TRUNC will be opened write only</li>
<li>Files open for write only will behave as if O_TRUNC was supplied</li>
<li>Open modes O_APPEND, O_TRUNC are ignored</li>
<li>If an upload fails it can't be retried</li>
</ul>
<h3 id="vfs-cache-mode-minimal-7">--vfs-cache-mode minimal</h3>
<p>This is very similar to "off" except that files opened for read AND write will be buffered to disk. This means that files opened for write will be a lot more compatible, but uses the minimal disk space.</p>
<p>These operations are not possible</p>
<ul>
<li>Files opened for write only can't be seeked</li>
<li>Existing files opened for write must have O_TRUNC set</li>
<li>Files opened for write only will ignore O_APPEND, O_TRUNC</li>
<li>If an upload fails it can't be retried</li>
</ul>
<h3 id="vfs-cache-mode-writes-7">--vfs-cache-mode writes</h3>
<p>In this mode files opened for read only are still read directly from the remote, write only and read/write files are buffered to disk first.</p>
<p>This mode should support all normal file system operations.</p>
<p>If an upload fails it will be retried at exponentially increasing intervals up to 1 minute.</p>
<h3 id="vfs-cache-mode-full-7">--vfs-cache-mode full</h3>
<p>In this mode all reads and writes are buffered to and from disk. When data is read from the remote this is buffered to disk as well.</p>
<p>In this mode the files in the cache will be sparse files and rclone will keep track of which bits of the files it has downloaded.</p>
<p>So if an application only reads the starts of each file, then rclone will only buffer the start of the file. These files will appear to be their full size in the cache, but they will be sparse files with only the data that has been downloaded present in them.</p>
<p>This mode should support all normal file system operations and is otherwise identical to <code>--vfs-cache-mode</code> writes.</p>
<p>When reading a file rclone will read <code>--buffer-size</code> plus <code>--vfs-read-ahead</code> bytes ahead. The <code>--buffer-size</code> is buffered in memory whereas the <code>--vfs-read-ahead</code> is buffered on disk.</p>
<p>When using this mode it is recommended that <code>--buffer-size</code> is not set too large and <code>--vfs-read-ahead</code> is set large if required.</p>
<p><strong>IMPORTANT</strong> not all file systems support sparse files. In particular FAT/exFAT do not. Rclone will perform very badly if the cache directory is on a filesystem which doesn't support sparse files and it will log an ERROR message if one is detected.</p>
<h3 id="fingerprinting-7">Fingerprinting</h3>
<p>Various parts of the VFS use fingerprinting to see if a local file copy has changed relative to a remote file. Fingerprints are made from:</p>
<ul>
<li>size</li>
<li>modification time</li>
<li>hash</li>
</ul>
<p>where available on an object.</p>
<p>On some backends some of these attributes are slow to read (they take an extra API call per object, or extra work per object).</p>
<p>For example <code>hash</code> is slow with the <code>local</code> and <code>sftp</code> backends as they have to read the entire file and hash it, and <code>modtime</code> is slow with the <code>s3</code>, <code>swift</code>, <code>ftp</code> and <code>qinqstor</code> backends because they need to do an extra API call to fetch it.</p>
<p>If you use the <code>--vfs-fast-fingerprint</code> flag then rclone will not include the slow operations in the fingerprint. This makes the fingerprinting less accurate but much faster and will improve the opening time of cached files.</p>
<p>If you are running a vfs cache over <code>local</code>, <code>s3</code> or <code>swift</code> backends then using this flag is recommended.</p>
<p>Note that if you change the value of this flag, the fingerprints of the files in the cache may be invalidated and the files will need to be downloaded again.</p>
<h2 id="vfs-chunked-reading-7">VFS Chunked Reading</h2>
<p>When rclone reads files from a remote it reads them in chunks. This means that rather than requesting the whole file rclone reads the chunk specified. This can reduce the used download quota for some remotes by requesting only chunks from the remote that are actually read, at the cost of an increased number of requests.</p>
<p>These flags control the chunking:</p>
<pre><code>--vfs-read-chunk-size SizeSuffix        Read the source objects in chunks (default 128M)
--vfs-read-chunk-size-limit SizeSuffix  Max chunk doubling size (default off)
--vfs-read-chunk-streams int            The number of parallel streams to read at once</code></pre>
<p>The chunking behaves differently depending on the <code>--vfs-read-chunk-streams</code> parameter.</p>
<h3 id="vfs-read-chunk-streams-0-14"><code>--vfs-read-chunk-streams</code> == 0</h3>
<p>Rclone will start reading a chunk of size <code>--vfs-read-chunk-size</code>, and then double the size for each read. When <code>--vfs-read-chunk-size-limit</code> is specified, and greater than <code>--vfs-read-chunk-size</code>, the chunk size for each open file will get doubled only until the specified value is reached. If the value is "off", which is the default, the limit is disabled and the chunk size will grow indefinitely.</p>
<p>With <code>--vfs-read-chunk-size 100M</code> and <code>--vfs-read-chunk-size-limit 0</code> the following parts will be downloaded: 0-100M, 100M-200M, 200M-300M, 300M-400M and so on. When <code>--vfs-read-chunk-size-limit 500M</code> is specified, the result would be 0-100M, 100M-300M, 300M-700M, 700M-1200M, 1200M-1700M and so on.</p>
<p>Setting <code>--vfs-read-chunk-size</code> to <code>0</code> or "off" disables chunked reading.</p>
<p>The chunks will not be buffered in memory.</p>
<h3 id="vfs-read-chunk-streams-0-15"><code>--vfs-read-chunk-streams</code> &gt; 0</h3>
<p>Rclone reads <code>--vfs-read-chunk-streams</code> chunks of size <code>--vfs-read-chunk-size</code> concurrently. The size for each read will stay constant.</p>
<p>This improves performance performance massively on high latency links or very high bandwidth links to high performance object stores.</p>
<p>Some experimentation will be needed to find the optimum values of <code>--vfs-read-chunk-size</code> and <code>--vfs-read-chunk-streams</code> as these will depend on the backend in use and the latency to the backend.</p>
<p>For high performance object stores (eg AWS S3) a reasonable place to start might be <code>--vfs-read-chunk-streams 16</code> and <code>--vfs-read-chunk-size 4M</code>. In testing with AWS S3 the performance scaled roughly as the <code>--vfs-read-chunk-streams</code> setting.</p>
<p>Similar settings should work for high latency links, but depending on the latency they may need more <code>--vfs-read-chunk-streams</code> in order to get the throughput.</p>
<h2 id="vfs-performance-7">VFS Performance</h2>
<p>These flags may be used to enable/disable features of the VFS for performance or other reasons. See also the <a href="#vfs-chunked-reading">chunked reading</a> feature.</p>
<p>In particular S3 and Swift benefit hugely from the <code>--no-modtime</code> flag (or use <code>--use-server-modtime</code> for a slightly different effect) as each read of the modification time takes a transaction.</p>
<pre><code>--no-checksum     Don&#39;t compare checksums on up/download.
--no-modtime      Don&#39;t read/write the modification time (can speed things up).
--no-seek         Don&#39;t allow seeking in files.
--read-only       Only allow read-only access.</code></pre>
<p>Sometimes rclone is delivered reads or writes out of order. Rather than seeking rclone will wait a short time for the in sequence read or write to come in. These flags only come into effect when not using an on disk cache file.</p>
<pre><code>--vfs-read-wait duration   Time to wait for in-sequence read before seeking (default 20ms)
--vfs-write-wait duration  Time to wait for in-sequence write before giving error (default 1s)</code></pre>
<p>When using VFS write caching (<code>--vfs-cache-mode</code> with value writes or full), the global flag <code>--transfers</code> can be set to adjust the number of parallel uploads of modified files from the cache (the related global flag <code>--checkers</code> has no effect on the VFS).</p>
<pre><code>--transfers int  Number of file transfers to run in parallel (default 4)</code></pre>
<h2 id="vfs-case-sensitivity-7">VFS Case Sensitivity</h2>
<p>Linux file systems are case-sensitive: two files can differ only by case, and the exact case must be used when opening a file.</p>
<p>File systems in modern Windows are case-insensitive but case-preserving: although existing files can be opened using any case, the exact case used to create the file is preserved and available for programs to query. It is not allowed for two files in the same directory to differ only by case.</p>
<p>Usually file systems on macOS are case-insensitive. It is possible to make macOS file systems case-sensitive but that is not the default.</p>
<p>The <code>--vfs-case-insensitive</code> VFS flag controls how rclone handles these two cases. If its value is "false", rclone passes file names to the remote as-is. If the flag is "true" (or appears without a value on the command line), rclone may perform a "fixup" as explained below.</p>
<p>The user may specify a file name to open/delete/rename/etc with a case different than what is stored on the remote. If an argument refers to an existing file with exactly the same name, then the case of the existing file on the disk will be used. However, if a file name with exactly the same name is not found but a name differing only by case exists, rclone will transparently fixup the name. This fixup happens only when an existing file is requested. Case sensitivity of file names created anew by rclone is controlled by the underlying remote.</p>
<p>Note that case sensitivity of the operating system running rclone (the target) may differ from case sensitivity of a file system presented by rclone (the source). The flag controls whether "fixup" is performed to satisfy the target.</p>
<p>If the flag is not provided on the command line, then its default value depends on the operating system where rclone runs: "true" on Windows and macOS, "false" otherwise. If the flag is provided without a value, then it is "true".</p>
<p>The <code>--no-unicode-normalization</code> flag controls whether a similar "fixup" is performed for filenames that differ but are <a href="https://en.wikipedia.org/wiki/Unicode_equivalence">canonically equivalent</a> with respect to unicode. Unicode normalization can be particularly helpful for users of macOS, which prefers form NFD instead of the NFC used by most other platforms. It is therefore highly recommended to keep the default of <code>false</code> on macOS, to avoid encoding compatibility issues.</p>
<p>In the (probably unlikely) event that a directory has multiple duplicate filenames after applying case and unicode normalization, the <code>--vfs-block-norm-dupes</code> flag allows hiding these duplicates. This comes with a performance tradeoff, as rclone will have to scan the entire directory for duplicates when listing a directory. For this reason, it is recommended to leave this disabled if not needed. However, macOS users may wish to consider using it, as otherwise, if a remote directory contains both NFC and NFD versions of the same filename, an odd situation will occur: both versions of the file will be visible in the mount, and both will appear to be editable, however, editing either version will actually result in only the NFD version getting edited under the hood. <code>--vfs-block- norm-dupes</code> prevents this confusion by detecting this scenario, hiding the duplicates, and logging an error, similar to how this is handled in <code>rclone sync</code>.</p>
<h2 id="vfs-disk-options-7">VFS Disk Options</h2>
<p>This flag allows you to manually set the statistics about the filing system. It can be useful when those statistics cannot be read correctly automatically.</p>
<pre><code>--vfs-disk-space-total-size    Manually set the total disk space size (example: 256G, default: -1)</code></pre>
<h2 id="alternate-report-of-used-bytes-7">Alternate report of used bytes</h2>
<p>Some backends, most notably S3, do not report the amount of bytes used. If you need this information to be available when running <code>df</code> on the filesystem, then pass the flag <code>--vfs-used-is-size</code> to rclone. With this flag set, instead of relying on the backend to report this information, rclone will scan the whole remote similar to <code>rclone size</code> and compute the total used space itself.</p>
<p><em>WARNING.</em> Contrary to <code>rclone size</code>, this flag ignores filters so that the result is accurate. However, this is very inefficient and may cost lots of API calls resulting in extra charges. Use it as a last resort and only with caching.</p>
<pre><code>rclone serve s3 remote:path [flags]</code></pre>
<h2 id="options-77">Options</h2>
<pre><code>      --addr stringArray                       IPaddress:Port, :Port or [unix://]/path/to/socket to bind server to (default [127.0.0.1:8080])
      --allow-origin string                    Origin which cross-domain request (CORS) can be executed from
      --auth-key stringArray                   Set key pair for v4 authorization: access_key_id,secret_access_key
      --auth-proxy string                      A program to use to create the backend from the auth
      --baseurl string                         Prefix for URLs - leave blank for root
      --cert string                            TLS PEM key (concatenation of certificate and CA certificate)
      --client-ca string                       Client certificate authority to verify clients with
      --dir-cache-time Duration                Time to cache directory entries for (default 5m0s)
      --dir-perms FileMode                     Directory permissions (default 777)
      --etag-hash string                       Which hash to use for the ETag, or auto or blank for off (default &quot;MD5&quot;)
      --file-perms FileMode                    File permissions (default 666)
      --force-path-style                       If true use path style access if false use virtual hosted style (default true) (default true)
      --gid uint32                             Override the gid field set by the filesystem (not supported on Windows) (default 1000)
  -h, --help                                   help for s3
      --htpasswd string                        A htpasswd file - if not provided no authentication is done
      --key string                             TLS PEM Private key
      --max-header-bytes int                   Maximum size of request header (default 4096)
      --min-tls-version string                 Minimum TLS version that is acceptable (default &quot;tls1.0&quot;)
      --no-checksum                            Don&#39;t compare checksums on up/download
      --no-cleanup                             Not to cleanup empty folder after object is deleted
      --no-modtime                             Don&#39;t read/write the modification time (can speed things up)
      --no-seek                                Don&#39;t allow seeking in files
      --pass string                            Password for authentication
      --poll-interval Duration                 Time to wait between polling for changes, must be smaller than dir-cache-time and only on supported remotes (set 0 to disable) (default 1m0s)
      --read-only                              Only allow read-only access
      --realm string                           Realm for authentication
      --salt string                            Password hashing salt (default &quot;dlPL2MqE&quot;)
      --server-read-timeout Duration           Timeout for server reading data (default 1h0m0s)
      --server-write-timeout Duration          Timeout for server writing data (default 1h0m0s)
      --uid uint32                             Override the uid field set by the filesystem (not supported on Windows) (default 1000)
      --umask FileMode                         Override the permission bits set by the filesystem (not supported on Windows) (default 002)
      --user string                            User name for authentication
      --vfs-block-norm-dupes                   If duplicate filenames exist in the same directory (after normalization), log an error and hide the duplicates (may have a performance cost)
      --vfs-cache-max-age Duration             Max time since last access of objects in the cache (default 1h0m0s)
      --vfs-cache-max-size SizeSuffix          Max total size of objects in the cache (default off)
      --vfs-cache-min-free-space SizeSuffix    Target minimum free space on the disk containing the cache (default off)
      --vfs-cache-mode CacheMode               Cache mode off|minimal|writes|full (default off)
      --vfs-cache-poll-interval Duration       Interval to poll the cache for stale objects (default 1m0s)
      --vfs-case-insensitive                   If a file name not found, find a case insensitive match
      --vfs-disk-space-total-size SizeSuffix   Specify the total space of disk (default off)
      --vfs-fast-fingerprint                   Use fast (less accurate) fingerprints for change detection
      --vfs-read-ahead SizeSuffix              Extra read ahead over --buffer-size when using cache-mode full
      --vfs-read-chunk-size SizeSuffix         Read the source objects in chunks (default 128Mi)
      --vfs-read-chunk-size-limit SizeSuffix   If greater than --vfs-read-chunk-size, double the chunk size after each chunk read, until the limit is reached (&#39;off&#39; is unlimited) (default off)
      --vfs-read-chunk-streams int             The number of parallel streams to read at once
      --vfs-read-wait Duration                 Time to wait for in-sequence read before seeking (default 20ms)
      --vfs-refresh                            Refreshes the directory cache recursively in the background on start
      --vfs-used-is-size rclone size           Use the rclone size algorithm for Used size
      --vfs-write-back Duration                Time to writeback files after last use when using cache (default 5s)
      --vfs-write-wait Duration                Time to wait for in-sequence write before giving error (default 1s)</code></pre>
<p>Options shared with other commands are described next. See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
<h3 id="filter-options-28">Filter Options</h3>
<p>Flags for filtering directory listings</p>
<pre><code>      --delete-excluded                     Delete files on dest excluded from sync
      --exclude stringArray                 Exclude files matching pattern
      --exclude-from stringArray            Read file exclude patterns from file (use - to read from stdin)
      --exclude-if-present stringArray      Exclude directories if filename is present
      --files-from stringArray              Read list of source-file names from file (use - to read from stdin)
      --files-from-raw stringArray          Read list of source-file names from file without any processing of lines (use - to read from stdin)
  -f, --filter stringArray                  Add a file filtering rule
      --filter-from stringArray             Read file filtering patterns from a file (use - to read from stdin)
      --ignore-case                         Ignore case in filters (case insensitive)
      --include stringArray                 Include files matching pattern
      --include-from stringArray            Read file include patterns from file (use - to read from stdin)
      --max-age Duration                    Only transfer files younger than this in s or suffix ms|s|m|h|d|w|M|y (default off)
      --max-depth int                       If set limits the recursion depth to this (default -1)
      --max-size SizeSuffix                 Only transfer files smaller than this in KiB or suffix B|K|M|G|T|P (default off)
      --metadata-exclude stringArray        Exclude metadatas matching pattern
      --metadata-exclude-from stringArray   Read metadata exclude patterns from file (use - to read from stdin)
      --metadata-filter stringArray         Add a metadata filtering rule
      --metadata-filter-from stringArray    Read metadata filtering patterns from a file (use - to read from stdin)
      --metadata-include stringArray        Include metadatas matching pattern
      --metadata-include-from stringArray   Read metadata include patterns from file (use - to read from stdin)
      --min-age Duration                    Only transfer files older than this in s or suffix ms|s|m|h|d|w|M|y (default off)
      --min-size SizeSuffix                 Only transfer files bigger than this in KiB or suffix B|K|M|G|T|P (default off)</code></pre>
<h2 id="see-also-77">See Also</h2>
<ul>
<li><a href="https://rclone.org/commands/rclone_serve/">rclone serve</a> - Serve a remote over a protocol.</li>
</ul>
<h1 id="rclone-serve-sftp">rclone serve sftp</h1>
<p>Serve the remote over SFTP.</p>
<h2 id="synopsis-70">Synopsis</h2>
<p>Run an SFTP server to serve a remote over SFTP. This can be used with an SFTP client or you can make a remote of type <a href="/sftp">sftp</a> to use with it.</p>
<p>You can use the <a href="/filtering">filter</a> flags (e.g. <code>--include</code>, <code>--exclude</code>) to control what is served.</p>
<p>The server will respond to a small number of shell commands, mainly md5sum, sha1sum and df, which enable it to provide support for checksums and the about feature when accessed from an sftp remote.</p>
<p>Note that this server uses standard 32 KiB packet payload size, which means you must not configure the client to expect anything else, e.g. with the <a href="https://rclone.org/sftp/#sftp-chunk-size">chunk_size</a> option on an sftp remote.</p>
<p>The server will log errors. Use <code>-v</code> to see access logs.</p>
<p><code>--bwlimit</code> will be respected for file transfers. Use <code>--stats</code> to control the stats printing.</p>
<p>You must provide some means of authentication, either with <code>--user</code>/<code>--pass</code>, an authorized keys file (specify location with <code>--authorized-keys</code> - the default is the same as ssh), an <code>--auth-proxy</code>, or set the <code>--no-auth</code> flag for no authentication when logging in.</p>
<p>If you don't supply a host <code>--key</code> then rclone will generate rsa, ecdsa and ed25519 variants, and cache them for later use in rclone's cache directory (see <code>rclone help flags cache-dir</code>) in the "serve-sftp" directory.</p>
<p>By default the server binds to localhost:2022 - if you want it to be reachable externally then supply <code>--addr :2022</code> for example.</p>
<p>This also supports being run with socket activation, in which case it will listen on the first passed FD. It can be configured with .socket and .service unit files as described in https://www.freedesktop.org/software/systemd/man/latest/systemd.socket.html</p>
<p>Socket activation can be tested ad-hoc with the <code>systemd-socket-activate</code>command:</p>
<pre><code>systemd-socket-activate -l 2222 -- rclone serve sftp :local:vfs/</code></pre>
<p>This will socket-activate rclone on the first connection to port 2222 over TCP.</p>
<p>Note that the default of <code>--vfs-cache-mode off</code> is fine for the rclone sftp backend, but it may not be with other SFTP clients.</p>
<p>If <code>--stdio</code> is specified, rclone will serve SFTP over stdio, which can be used with sshd via ~/.ssh/authorized_keys, for example:</p>
<pre><code>restrict,command=&quot;rclone serve sftp --stdio ./photos&quot; ssh-rsa ...</code></pre>
<p>On the client you need to set <code>--transfers 1</code> when using <code>--stdio</code>. Otherwise multiple instances of the rclone server are started by OpenSSH which can lead to "corrupted on transfer" errors. This is the case because the client chooses indiscriminately which server to send commands to while the servers all have different views of the state of the filing system.</p>
<p>The "restrict" in authorized_keys prevents SHA1SUMs and MD5SUMs from being used. Omitting "restrict" and using <code>--sftp-path-override</code> to enable checksumming is possible but less secure and you could use the SFTP server provided by OpenSSH in this case.</p>
<h2 id="vfs---virtual-file-system-7">VFS - Virtual File System</h2>
<p>This command uses the VFS layer. This adapts the cloud storage objects that rclone uses into something which looks much more like a disk filing system.</p>
<p>Cloud storage objects have lots of properties which aren't like disk files - you can't extend them or write to the middle of them, so the VFS layer has to deal with that. Because there is no one right way of doing this there are various options explained below.</p>
<p>The VFS layer also implements a directory cache - this caches info about files and directories (but not the data) in memory.</p>
<h2 id="vfs-directory-cache-8">VFS Directory Cache</h2>
<p>Using the <code>--dir-cache-time</code> flag, you can control how long a directory should be considered up to date and not refreshed from the backend. Changes made through the VFS will appear immediately or invalidate the cache.</p>
<pre><code>--dir-cache-time duration   Time to cache directory entries for (default 5m0s)
--poll-interval duration    Time to wait between polling for changes. Must be smaller than dir-cache-time. Only on supported remotes. Set to 0 to disable (default 1m0s)</code></pre>
<p>However, changes made directly on the cloud storage by the web interface or a different copy of rclone will only be picked up once the directory cache expires if the backend configured does not support polling for changes. If the backend supports polling, changes will be picked up within the polling interval.</p>
<p>You can send a <code>SIGHUP</code> signal to rclone for it to flush all directory caches, regardless of how old they are. Assuming only one rclone instance is running, you can reset the cache like this:</p>
<pre><code>kill -SIGHUP $(pidof rclone)</code></pre>
<p>If you configure rclone with a <a href="/rc">remote control</a> then you can use rclone rc to flush the whole directory cache:</p>
<pre><code>rclone rc vfs/forget</code></pre>
<p>Or individual files or directories:</p>
<pre><code>rclone rc vfs/forget file=path/to/file dir=path/to/dir</code></pre>
<h2 id="vfs-file-buffering-8">VFS File Buffering</h2>
<p>The <code>--buffer-size</code> flag determines the amount of memory, that will be used to buffer data in advance.</p>
<p>Each open file will try to keep the specified amount of data in memory at all times. The buffered data is bound to one open file and won't be shared.</p>
<p>This flag is a upper limit for the used memory per open file. The buffer will only use memory for data that is downloaded but not not yet read. If the buffer is empty, only a small amount of memory will be used.</p>
<p>The maximum memory used by rclone for buffering can be up to <code>--buffer-size * open files</code>.</p>
<h2 id="vfs-file-caching-8">VFS File Caching</h2>
<p>These flags control the VFS file caching options. File caching is necessary to make the VFS layer appear compatible with a normal file system. It can be disabled at the cost of some compatibility.</p>
<p>For example you'll need to enable VFS caching if you want to read and write simultaneously to a file. See below for more details.</p>
<p>Note that the VFS cache is separate from the cache backend and you may find that you need one or the other or both.</p>
<pre><code>--cache-dir string                     Directory rclone will use for caching.
--vfs-cache-mode CacheMode             Cache mode off|minimal|writes|full (default off)
--vfs-cache-max-age duration           Max time since last access of objects in the cache (default 1h0m0s)
--vfs-cache-max-size SizeSuffix        Max total size of objects in the cache (default off)
--vfs-cache-min-free-space SizeSuffix  Target minimum free space on the disk containing the cache (default off)
--vfs-cache-poll-interval duration     Interval to poll the cache for stale objects (default 1m0s)
--vfs-write-back duration              Time to writeback files after last use when using cache (default 5s)</code></pre>
<p>If run with <code>-vv</code> rclone will print the location of the file cache. The files are stored in the user cache file area which is OS dependent but can be controlled with <code>--cache-dir</code> or setting the appropriate environment variable.</p>
<p>The cache has 4 different modes selected by <code>--vfs-cache-mode</code>. The higher the cache mode the more compatible rclone becomes at the cost of using disk space.</p>
<p>Note that files are written back to the remote only when they are closed and if they haven't been accessed for <code>--vfs-write-back</code> seconds. If rclone is quit or dies with files that haven't been uploaded, these will be uploaded next time rclone is run with the same flags.</p>
<p>If using <code>--vfs-cache-max-size</code> or <code>--vfs-cache-min-free-size</code> note that the cache may exceed these quotas for two reasons. Firstly because it is only checked every <code>--vfs-cache-poll-interval</code>. Secondly because open files cannot be evicted from the cache. When <code>--vfs-cache-max-size</code> or <code>--vfs-cache-min-free-size</code> is exceeded, rclone will attempt to evict the least accessed files from the cache first. rclone will start with files that haven't been accessed for the longest. This cache flushing strategy is efficient and more relevant files are likely to remain cached.</p>
<p>The <code>--vfs-cache-max-age</code> will evict files from the cache after the set time since last access has passed. The default value of 1 hour will start evicting files from cache that haven't been accessed for 1 hour. When a cached file is accessed the 1 hour timer is reset to 0 and will wait for 1 more hour before evicting. Specify the time with standard notation, s, m, h, d, w .</p>
<p>You <strong>should not</strong> run two copies of rclone using the same VFS cache with the same or overlapping remotes if using <code>--vfs-cache-mode &gt; off</code>. This can potentially cause data corruption if you do. You can work around this by giving each rclone its own cache hierarchy with <code>--cache-dir</code>. You don't need to worry about this if the remotes in use don't overlap.</p>
<h3 id="vfs-cache-mode-off-8">--vfs-cache-mode off</h3>
<p>In this mode (the default) the cache will read directly from the remote and write directly to the remote without caching anything on disk.</p>
<p>This will mean some operations are not possible</p>
<ul>
<li>Files can't be opened for both read AND write</li>
<li>Files opened for write can't be seeked</li>
<li>Existing files opened for write must have O_TRUNC set</li>
<li>Files open for read with O_TRUNC will be opened write only</li>
<li>Files open for write only will behave as if O_TRUNC was supplied</li>
<li>Open modes O_APPEND, O_TRUNC are ignored</li>
<li>If an upload fails it can't be retried</li>
</ul>
<h3 id="vfs-cache-mode-minimal-8">--vfs-cache-mode minimal</h3>
<p>This is very similar to "off" except that files opened for read AND write will be buffered to disk. This means that files opened for write will be a lot more compatible, but uses the minimal disk space.</p>
<p>These operations are not possible</p>
<ul>
<li>Files opened for write only can't be seeked</li>
<li>Existing files opened for write must have O_TRUNC set</li>
<li>Files opened for write only will ignore O_APPEND, O_TRUNC</li>
<li>If an upload fails it can't be retried</li>
</ul>
<h3 id="vfs-cache-mode-writes-8">--vfs-cache-mode writes</h3>
<p>In this mode files opened for read only are still read directly from the remote, write only and read/write files are buffered to disk first.</p>
<p>This mode should support all normal file system operations.</p>
<p>If an upload fails it will be retried at exponentially increasing intervals up to 1 minute.</p>
<h3 id="vfs-cache-mode-full-8">--vfs-cache-mode full</h3>
<p>In this mode all reads and writes are buffered to and from disk. When data is read from the remote this is buffered to disk as well.</p>
<p>In this mode the files in the cache will be sparse files and rclone will keep track of which bits of the files it has downloaded.</p>
<p>So if an application only reads the starts of each file, then rclone will only buffer the start of the file. These files will appear to be their full size in the cache, but they will be sparse files with only the data that has been downloaded present in them.</p>
<p>This mode should support all normal file system operations and is otherwise identical to <code>--vfs-cache-mode</code> writes.</p>
<p>When reading a file rclone will read <code>--buffer-size</code> plus <code>--vfs-read-ahead</code> bytes ahead. The <code>--buffer-size</code> is buffered in memory whereas the <code>--vfs-read-ahead</code> is buffered on disk.</p>
<p>When using this mode it is recommended that <code>--buffer-size</code> is not set too large and <code>--vfs-read-ahead</code> is set large if required.</p>
<p><strong>IMPORTANT</strong> not all file systems support sparse files. In particular FAT/exFAT do not. Rclone will perform very badly if the cache directory is on a filesystem which doesn't support sparse files and it will log an ERROR message if one is detected.</p>
<h3 id="fingerprinting-8">Fingerprinting</h3>
<p>Various parts of the VFS use fingerprinting to see if a local file copy has changed relative to a remote file. Fingerprints are made from:</p>
<ul>
<li>size</li>
<li>modification time</li>
<li>hash</li>
</ul>
<p>where available on an object.</p>
<p>On some backends some of these attributes are slow to read (they take an extra API call per object, or extra work per object).</p>
<p>For example <code>hash</code> is slow with the <code>local</code> and <code>sftp</code> backends as they have to read the entire file and hash it, and <code>modtime</code> is slow with the <code>s3</code>, <code>swift</code>, <code>ftp</code> and <code>qinqstor</code> backends because they need to do an extra API call to fetch it.</p>
<p>If you use the <code>--vfs-fast-fingerprint</code> flag then rclone will not include the slow operations in the fingerprint. This makes the fingerprinting less accurate but much faster and will improve the opening time of cached files.</p>
<p>If you are running a vfs cache over <code>local</code>, <code>s3</code> or <code>swift</code> backends then using this flag is recommended.</p>
<p>Note that if you change the value of this flag, the fingerprints of the files in the cache may be invalidated and the files will need to be downloaded again.</p>
<h2 id="vfs-chunked-reading-8">VFS Chunked Reading</h2>
<p>When rclone reads files from a remote it reads them in chunks. This means that rather than requesting the whole file rclone reads the chunk specified. This can reduce the used download quota for some remotes by requesting only chunks from the remote that are actually read, at the cost of an increased number of requests.</p>
<p>These flags control the chunking:</p>
<pre><code>--vfs-read-chunk-size SizeSuffix        Read the source objects in chunks (default 128M)
--vfs-read-chunk-size-limit SizeSuffix  Max chunk doubling size (default off)
--vfs-read-chunk-streams int            The number of parallel streams to read at once</code></pre>
<p>The chunking behaves differently depending on the <code>--vfs-read-chunk-streams</code> parameter.</p>
<h3 id="vfs-read-chunk-streams-0-16"><code>--vfs-read-chunk-streams</code> == 0</h3>
<p>Rclone will start reading a chunk of size <code>--vfs-read-chunk-size</code>, and then double the size for each read. When <code>--vfs-read-chunk-size-limit</code> is specified, and greater than <code>--vfs-read-chunk-size</code>, the chunk size for each open file will get doubled only until the specified value is reached. If the value is "off", which is the default, the limit is disabled and the chunk size will grow indefinitely.</p>
<p>With <code>--vfs-read-chunk-size 100M</code> and <code>--vfs-read-chunk-size-limit 0</code> the following parts will be downloaded: 0-100M, 100M-200M, 200M-300M, 300M-400M and so on. When <code>--vfs-read-chunk-size-limit 500M</code> is specified, the result would be 0-100M, 100M-300M, 300M-700M, 700M-1200M, 1200M-1700M and so on.</p>
<p>Setting <code>--vfs-read-chunk-size</code> to <code>0</code> or "off" disables chunked reading.</p>
<p>The chunks will not be buffered in memory.</p>
<h3 id="vfs-read-chunk-streams-0-17"><code>--vfs-read-chunk-streams</code> &gt; 0</h3>
<p>Rclone reads <code>--vfs-read-chunk-streams</code> chunks of size <code>--vfs-read-chunk-size</code> concurrently. The size for each read will stay constant.</p>
<p>This improves performance performance massively on high latency links or very high bandwidth links to high performance object stores.</p>
<p>Some experimentation will be needed to find the optimum values of <code>--vfs-read-chunk-size</code> and <code>--vfs-read-chunk-streams</code> as these will depend on the backend in use and the latency to the backend.</p>
<p>For high performance object stores (eg AWS S3) a reasonable place to start might be <code>--vfs-read-chunk-streams 16</code> and <code>--vfs-read-chunk-size 4M</code>. In testing with AWS S3 the performance scaled roughly as the <code>--vfs-read-chunk-streams</code> setting.</p>
<p>Similar settings should work for high latency links, but depending on the latency they may need more <code>--vfs-read-chunk-streams</code> in order to get the throughput.</p>
<h2 id="vfs-performance-8">VFS Performance</h2>
<p>These flags may be used to enable/disable features of the VFS for performance or other reasons. See also the <a href="#vfs-chunked-reading">chunked reading</a> feature.</p>
<p>In particular S3 and Swift benefit hugely from the <code>--no-modtime</code> flag (or use <code>--use-server-modtime</code> for a slightly different effect) as each read of the modification time takes a transaction.</p>
<pre><code>--no-checksum     Don&#39;t compare checksums on up/download.
--no-modtime      Don&#39;t read/write the modification time (can speed things up).
--no-seek         Don&#39;t allow seeking in files.
--read-only       Only allow read-only access.</code></pre>
<p>Sometimes rclone is delivered reads or writes out of order. Rather than seeking rclone will wait a short time for the in sequence read or write to come in. These flags only come into effect when not using an on disk cache file.</p>
<pre><code>--vfs-read-wait duration   Time to wait for in-sequence read before seeking (default 20ms)
--vfs-write-wait duration  Time to wait for in-sequence write before giving error (default 1s)</code></pre>
<p>When using VFS write caching (<code>--vfs-cache-mode</code> with value writes or full), the global flag <code>--transfers</code> can be set to adjust the number of parallel uploads of modified files from the cache (the related global flag <code>--checkers</code> has no effect on the VFS).</p>
<pre><code>--transfers int  Number of file transfers to run in parallel (default 4)</code></pre>
<h2 id="vfs-case-sensitivity-8">VFS Case Sensitivity</h2>
<p>Linux file systems are case-sensitive: two files can differ only by case, and the exact case must be used when opening a file.</p>
<p>File systems in modern Windows are case-insensitive but case-preserving: although existing files can be opened using any case, the exact case used to create the file is preserved and available for programs to query. It is not allowed for two files in the same directory to differ only by case.</p>
<p>Usually file systems on macOS are case-insensitive. It is possible to make macOS file systems case-sensitive but that is not the default.</p>
<p>The <code>--vfs-case-insensitive</code> VFS flag controls how rclone handles these two cases. If its value is "false", rclone passes file names to the remote as-is. If the flag is "true" (or appears without a value on the command line), rclone may perform a "fixup" as explained below.</p>
<p>The user may specify a file name to open/delete/rename/etc with a case different than what is stored on the remote. If an argument refers to an existing file with exactly the same name, then the case of the existing file on the disk will be used. However, if a file name with exactly the same name is not found but a name differing only by case exists, rclone will transparently fixup the name. This fixup happens only when an existing file is requested. Case sensitivity of file names created anew by rclone is controlled by the underlying remote.</p>
<p>Note that case sensitivity of the operating system running rclone (the target) may differ from case sensitivity of a file system presented by rclone (the source). The flag controls whether "fixup" is performed to satisfy the target.</p>
<p>If the flag is not provided on the command line, then its default value depends on the operating system where rclone runs: "true" on Windows and macOS, "false" otherwise. If the flag is provided without a value, then it is "true".</p>
<p>The <code>--no-unicode-normalization</code> flag controls whether a similar "fixup" is performed for filenames that differ but are <a href="https://en.wikipedia.org/wiki/Unicode_equivalence">canonically equivalent</a> with respect to unicode. Unicode normalization can be particularly helpful for users of macOS, which prefers form NFD instead of the NFC used by most other platforms. It is therefore highly recommended to keep the default of <code>false</code> on macOS, to avoid encoding compatibility issues.</p>
<p>In the (probably unlikely) event that a directory has multiple duplicate filenames after applying case and unicode normalization, the <code>--vfs-block-norm-dupes</code> flag allows hiding these duplicates. This comes with a performance tradeoff, as rclone will have to scan the entire directory for duplicates when listing a directory. For this reason, it is recommended to leave this disabled if not needed. However, macOS users may wish to consider using it, as otherwise, if a remote directory contains both NFC and NFD versions of the same filename, an odd situation will occur: both versions of the file will be visible in the mount, and both will appear to be editable, however, editing either version will actually result in only the NFD version getting edited under the hood. <code>--vfs-block- norm-dupes</code> prevents this confusion by detecting this scenario, hiding the duplicates, and logging an error, similar to how this is handled in <code>rclone sync</code>.</p>
<h2 id="vfs-disk-options-8">VFS Disk Options</h2>
<p>This flag allows you to manually set the statistics about the filing system. It can be useful when those statistics cannot be read correctly automatically.</p>
<pre><code>--vfs-disk-space-total-size    Manually set the total disk space size (example: 256G, default: -1)</code></pre>
<h2 id="alternate-report-of-used-bytes-8">Alternate report of used bytes</h2>
<p>Some backends, most notably S3, do not report the amount of bytes used. If you need this information to be available when running <code>df</code> on the filesystem, then pass the flag <code>--vfs-used-is-size</code> to rclone. With this flag set, instead of relying on the backend to report this information, rclone will scan the whole remote similar to <code>rclone size</code> and compute the total used space itself.</p>
<p><em>WARNING.</em> Contrary to <code>rclone size</code>, this flag ignores filters so that the result is accurate. However, this is very inefficient and may cost lots of API calls resulting in extra charges. Use it as a last resort and only with caching.</p>
<h2 id="auth-proxy-2">Auth Proxy</h2>
<p>If you supply the parameter <code>--auth-proxy /path/to/program</code> then rclone will use that program to generate backends on the fly which then are used to authenticate incoming requests. This uses a simple JSON based protocol with input on STDIN and output on STDOUT.</p>
<p><strong>PLEASE NOTE:</strong> <code>--auth-proxy</code> and <code>--authorized-keys</code> cannot be used together, if <code>--auth-proxy</code> is set the authorized keys option will be ignored.</p>
<p>There is an example program <a href="https://github.com/rclone/rclone/blob/master/bin/test_proxy.py">bin/test_proxy.py</a> in the rclone source code.</p>
<p>The program's job is to take a <code>user</code> and <code>pass</code> on the input and turn those into the config for a backend on STDOUT in JSON format. This config will have any default parameters for the backend added, but it won't use configuration from environment variables or command line options - it is the job of the proxy program to make a complete config.</p>
<p>This config generated must have this extra parameter - <code>_root</code> - root to use for the backend</p>
<p>And it may have this parameter - <code>_obscure</code> - comma separated strings for parameters to obscure</p>
<p>If password authentication was used by the client, input to the proxy process (on STDIN) would look similar to this:</p>
<pre><code>{
    &quot;user&quot;: &quot;me&quot;,
    &quot;pass&quot;: &quot;mypassword&quot;
}</code></pre>
<p>If public-key authentication was used by the client, input to the proxy process (on STDIN) would look similar to this:</p>
<pre><code>{
    &quot;user&quot;: &quot;me&quot;,
    &quot;public_key&quot;: &quot;AAAAB3NzaC1yc2EAAAADAQABAAABAQDuwESFdAe14hVS6omeyX7edc...JQdf&quot;
}</code></pre>
<p>And as an example return this on STDOUT</p>
<pre><code>{
    &quot;type&quot;: &quot;sftp&quot;,
    &quot;_root&quot;: &quot;&quot;,
    &quot;_obscure&quot;: &quot;pass&quot;,
    &quot;user&quot;: &quot;me&quot;,
    &quot;pass&quot;: &quot;mypassword&quot;,
    &quot;host&quot;: &quot;sftp.example.com&quot;
}</code></pre>
<p>This would mean that an SFTP backend would be created on the fly for the <code>user</code> and <code>pass</code>/<code>public_key</code> returned in the output to the host given. Note that since <code>_obscure</code> is set to <code>pass</code>, rclone will obscure the <code>pass</code> parameter before creating the backend (which is required for sftp backends).</p>
<p>The program can manipulate the supplied <code>user</code> in any way, for example to make proxy to many different sftp backends, you could make the <code>user</code> be <code>user@example.com</code> and then set the <code>host</code> to <code>example.com</code> in the output and the user to <code>user</code>. For security you'd probably want to restrict the <code>host</code> to a limited list.</p>
<p>Note that an internal cache is keyed on <code>user</code> so only use that for configuration, don't use <code>pass</code> or <code>public_key</code>. This also means that if a user's password or public-key is changed the cache will need to expire (which takes 5 mins) before it takes effect.</p>
<p>This can be used to build general purpose proxies to any kind of backend that rclone supports.</p>
<pre><code>rclone serve sftp remote:path [flags]</code></pre>
<h2 id="options-78">Options</h2>
<pre><code>      --addr string                            IPaddress:Port or :Port to bind server to (default &quot;localhost:2022&quot;)
      --auth-proxy string                      A program to use to create the backend from the auth
      --authorized-keys string                 Authorized keys file (default &quot;~/.ssh/authorized_keys&quot;)
      --dir-cache-time Duration                Time to cache directory entries for (default 5m0s)
      --dir-perms FileMode                     Directory permissions (default 777)
      --file-perms FileMode                    File permissions (default 666)
      --gid uint32                             Override the gid field set by the filesystem (not supported on Windows) (default 1000)
  -h, --help                                   help for sftp
      --key stringArray                        SSH private host key file (Can be multi-valued, leave blank to auto generate)
      --no-auth                                Allow connections with no authentication if set
      --no-checksum                            Don&#39;t compare checksums on up/download
      --no-modtime                             Don&#39;t read/write the modification time (can speed things up)
      --no-seek                                Don&#39;t allow seeking in files
      --pass string                            Password for authentication
      --poll-interval Duration                 Time to wait between polling for changes, must be smaller than dir-cache-time and only on supported remotes (set 0 to disable) (default 1m0s)
      --read-only                              Only allow read-only access
      --stdio                                  Run an sftp server on stdin/stdout
      --uid uint32                             Override the uid field set by the filesystem (not supported on Windows) (default 1000)
      --umask FileMode                         Override the permission bits set by the filesystem (not supported on Windows) (default 002)
      --user string                            User name for authentication
      --vfs-block-norm-dupes                   If duplicate filenames exist in the same directory (after normalization), log an error and hide the duplicates (may have a performance cost)
      --vfs-cache-max-age Duration             Max time since last access of objects in the cache (default 1h0m0s)
      --vfs-cache-max-size SizeSuffix          Max total size of objects in the cache (default off)
      --vfs-cache-min-free-space SizeSuffix    Target minimum free space on the disk containing the cache (default off)
      --vfs-cache-mode CacheMode               Cache mode off|minimal|writes|full (default off)
      --vfs-cache-poll-interval Duration       Interval to poll the cache for stale objects (default 1m0s)
      --vfs-case-insensitive                   If a file name not found, find a case insensitive match
      --vfs-disk-space-total-size SizeSuffix   Specify the total space of disk (default off)
      --vfs-fast-fingerprint                   Use fast (less accurate) fingerprints for change detection
      --vfs-read-ahead SizeSuffix              Extra read ahead over --buffer-size when using cache-mode full
      --vfs-read-chunk-size SizeSuffix         Read the source objects in chunks (default 128Mi)
      --vfs-read-chunk-size-limit SizeSuffix   If greater than --vfs-read-chunk-size, double the chunk size after each chunk read, until the limit is reached (&#39;off&#39; is unlimited) (default off)
      --vfs-read-chunk-streams int             The number of parallel streams to read at once
      --vfs-read-wait Duration                 Time to wait for in-sequence read before seeking (default 20ms)
      --vfs-refresh                            Refreshes the directory cache recursively in the background on start
      --vfs-used-is-size rclone size           Use the rclone size algorithm for Used size
      --vfs-write-back Duration                Time to writeback files after last use when using cache (default 5s)
      --vfs-write-wait Duration                Time to wait for in-sequence write before giving error (default 1s)</code></pre>
<p>Options shared with other commands are described next. See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
<h3 id="filter-options-29">Filter Options</h3>
<p>Flags for filtering directory listings</p>
<pre><code>      --delete-excluded                     Delete files on dest excluded from sync
      --exclude stringArray                 Exclude files matching pattern
      --exclude-from stringArray            Read file exclude patterns from file (use - to read from stdin)
      --exclude-if-present stringArray      Exclude directories if filename is present
      --files-from stringArray              Read list of source-file names from file (use - to read from stdin)
      --files-from-raw stringArray          Read list of source-file names from file without any processing of lines (use - to read from stdin)
  -f, --filter stringArray                  Add a file filtering rule
      --filter-from stringArray             Read file filtering patterns from a file (use - to read from stdin)
      --ignore-case                         Ignore case in filters (case insensitive)
      --include stringArray                 Include files matching pattern
      --include-from stringArray            Read file include patterns from file (use - to read from stdin)
      --max-age Duration                    Only transfer files younger than this in s or suffix ms|s|m|h|d|w|M|y (default off)
      --max-depth int                       If set limits the recursion depth to this (default -1)
      --max-size SizeSuffix                 Only transfer files smaller than this in KiB or suffix B|K|M|G|T|P (default off)
      --metadata-exclude stringArray        Exclude metadatas matching pattern
      --metadata-exclude-from stringArray   Read metadata exclude patterns from file (use - to read from stdin)
      --metadata-filter stringArray         Add a metadata filtering rule
      --metadata-filter-from stringArray    Read metadata filtering patterns from a file (use - to read from stdin)
      --metadata-include stringArray        Include metadatas matching pattern
      --metadata-include-from stringArray   Read metadata include patterns from file (use - to read from stdin)
      --min-age Duration                    Only transfer files older than this in s or suffix ms|s|m|h|d|w|M|y (default off)
      --min-size SizeSuffix                 Only transfer files bigger than this in KiB or suffix B|K|M|G|T|P (default off)</code></pre>
<h2 id="see-also-78">See Also</h2>
<ul>
<li><a href="https://rclone.org/commands/rclone_serve/">rclone serve</a> - Serve a remote over a protocol.</li>
</ul>
<h1 id="rclone-serve-webdav">rclone serve webdav</h1>
<p>Serve remote:path over WebDAV.</p>
<h2 id="synopsis-71">Synopsis</h2>
<p>Run a basic WebDAV server to serve a remote over HTTP via the WebDAV protocol. This can be viewed with a WebDAV client, through a web browser, or you can make a remote of type WebDAV to read and write it.</p>
<h2 id="webdav-options">WebDAV options</h2>
<h3 id="etag-hash">--etag-hash</h3>
<p>This controls the ETag header. Without this flag the ETag will be based on the ModTime and Size of the object.</p>
<p>If this flag is set to "auto" then rclone will choose the first supported hash on the backend or you can use a named hash such as "MD5" or "SHA-1". Use the <a href="https://rclone.org/commands/rclone_hashsum/">hashsum</a> command to see the full list.</p>
<h2 id="access-webdav-on-windows">Access WebDAV on Windows</h2>
<p>WebDAV shared folder can be mapped as a drive on Windows, however the default settings prevent it. Windows will fail to connect to the server using insecure Basic authentication. It will not even display any login dialog. Windows requires SSL / HTTPS connection to be used with Basic. If you try to connect via Add Network Location Wizard you will get the following error: "The folder you entered does not appear to be valid. Please choose another". However, you still can connect if you set the following registry key on a client machine: HKEY_LOCAL_MACHINEto 2. The BasicAuthLevel can be set to the following values: 0 - Basic authentication disabled 1 - Basic authentication enabled for SSL connections only 2 - Basic authentication enabled for SSL connections and for non-SSL connections If required, increase the FileSizeLimitInBytes to a higher value. Navigate to the Services interface, then restart the WebClient service.</p>
<h2 id="access-office-applications-on-webdav">Access Office applications on WebDAV</h2>
<p>Navigate to following registry HKEY_CURRENT_USER[14.0/15.0/16.0] Create a new DWORD BasicAuthLevel with value 2. 0 - Basic authentication disabled 1 - Basic authentication enabled for SSL connections only 2 - Basic authentication enabled for SSL and for non-SSL connections</p>
<p>https://learn.microsoft.com/en-us/office/troubleshoot/powerpoint/office-opens-blank-from-sharepoint</p>
<h2 id="serving-over-a-unix-socket">Serving over a unix socket</h2>
<p>You can serve the webdav on a unix socket like this:</p>
<pre><code>rclone serve webdav --addr unix:///tmp/my.socket remote:path</code></pre>
<p>and connect to it like this using rclone and the webdav backend:</p>
<pre><code>rclone --webdav-unix-socket /tmp/my.socket --webdav-url http://localhost lsf :webdav:</code></pre>
<p>Note that there is no authentication on http protocol - this is expected to be done by the permissions on the socket.</p>
<h2 id="server-options-6">Server options</h2>
<p>Use <code>--addr</code> to specify which IP address and port the server should listen on, eg <code>--addr 1.2.3.4:8000</code> or <code>--addr :8080</code> to listen to all IPs. By default it only listens on localhost. You can use port :0 to let the OS choose an available port.</p>
<p>If you set <code>--addr</code> to listen on a public or LAN accessible IP address then using Authentication is advised - see the next section for info.</p>
<p>You can use a unix socket by setting the url to <code>unix:///path/to/socket</code> or just by using an absolute path name. Note that unix sockets bypass the authentication - this is expected to be done with file system permissions.</p>
<p><code>--addr</code> may be repeated to listen on multiple IPs/ports/sockets. Socket activation, described further below, can also be used to accomplish the same.</p>
<p><code>--server-read-timeout</code> and <code>--server-write-timeout</code> can be used to control the timeouts on the server. Note that this is the total time for a transfer.</p>
<p><code>--max-header-bytes</code> controls the maximum number of bytes the server will accept in the HTTP header.</p>
<p><code>--baseurl</code> controls the URL prefix that rclone serves from. By default rclone will serve from the root. If you used <code>--baseurl "/rclone"</code> then rclone would serve from a URL starting with "/rclone/". This is useful if you wish to proxy rclone serve. Rclone automatically inserts leading and trailing "/" on <code>--baseurl</code>, so <code>--baseurl "rclone"</code>, <code>--baseurl "/rclone"</code> and <code>--baseurl "/rclone/"</code> are all treated identically.</p>
<h3 id="tls-ssl-4">TLS (SSL)</h3>
<p>By default this will serve over http. If you want you can serve over https. You will need to supply the <code>--cert</code> and <code>--key</code> flags. If you wish to do client side certificate validation then you will need to supply <code>--client-ca</code> also.</p>
<p><code>--cert</code> should be a either a PEM encoded certificate or a concatenation of that with the CA certificate. <code>--key</code> should be the PEM encoded private key and <code>--client-ca</code> should be the PEM encoded client certificate authority certificate.</p>
<p><code>--min-tls-version</code> is minimum TLS version that is acceptable. Valid values are "tls1.0", "tls1.1", "tls1.2" and "tls1.3" (default "tls1.0").</p>
<h2 id="socket-activation-4">Socket activation</h2>
<p>Instead of the listening addresses specified above, rclone will listen to all FDs passed by the service manager, if any (and ignore any arguments passed by --addr`).</p>
<p>This allows rclone to be a socket-activated service. It can be configured with .socket and .service unit files as described in https://www.freedesktop.org/software/systemd/man/latest/systemd.socket.html</p>
<p>Socket activation can be tested ad-hoc with the <code>systemd-socket-activate</code>command</p>
<pre><code>   systemd-socket-activate -l 8000 -- rclone serve</code></pre>
<p>This will socket-activate rclone on the first connection to port 8000 over TCP. ### Template</p>
<p><code>--template</code> allows a user to specify a custom markup template for HTTP and WebDAV serve functions. The server exports the following markup to be used within the template to server pages:</p>
<table>
<colgroup>
<col style="width: 50%" />
<col style="width: 50%" />
</colgroup>
<thead>
<tr class="header">
<th style="text-align: left;">Parameter</th>
<th style="text-align: left;">Description</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td style="text-align: left;">.Name</td>
<td style="text-align: left;">The full path of a file/directory.</td>
</tr>
<tr class="even">
<td style="text-align: left;">.Title</td>
<td style="text-align: left;">Directory listing of .Name</td>
</tr>
<tr class="odd">
<td style="text-align: left;">.Sort</td>
<td style="text-align: left;">The current sort used. This is changeable via ?sort= parameter</td>
</tr>
<tr class="even">
<td style="text-align: left;"></td>
<td style="text-align: left;">Sort Options: namedirfirst,name,size,time (default namedirfirst)</td>
</tr>
<tr class="odd">
<td style="text-align: left;">.Order</td>
<td style="text-align: left;">The current ordering used. This is changeable via ?order= parameter</td>
</tr>
<tr class="even">
<td style="text-align: left;"></td>
<td style="text-align: left;">Order Options: asc,desc (default asc)</td>
</tr>
<tr class="odd">
<td style="text-align: left;">.Query</td>
<td style="text-align: left;">Currently unused.</td>
</tr>
<tr class="even">
<td style="text-align: left;">.Breadcrumb</td>
<td style="text-align: left;">Allows for creating a relative navigation</td>
</tr>
<tr class="odd">
<td style="text-align: left;">-- .Link</td>
<td style="text-align: left;">The relative to the root link of the Text.</td>
</tr>
<tr class="even">
<td style="text-align: left;">-- .Text</td>
<td style="text-align: left;">The Name of the directory.</td>
</tr>
<tr class="odd">
<td style="text-align: left;">.Entries</td>
<td style="text-align: left;">Information about a specific file/directory.</td>
</tr>
<tr class="even">
<td style="text-align: left;">-- .URL</td>
<td style="text-align: left;">The 'url' of an entry.</td>
</tr>
<tr class="odd">
<td style="text-align: left;">-- .Leaf</td>
<td style="text-align: left;">Currently same as 'URL' but intended to be 'just' the name.</td>
</tr>
<tr class="even">
<td style="text-align: left;">-- .IsDir</td>
<td style="text-align: left;">Boolean for if an entry is a directory or not.</td>
</tr>
<tr class="odd">
<td style="text-align: left;">-- .Size</td>
<td style="text-align: left;">Size in Bytes of the entry.</td>
</tr>
<tr class="even">
<td style="text-align: left;">-- .ModTime</td>
<td style="text-align: left;">The UTC timestamp of an entry.</td>
</tr>
</tbody>
</table>
<p>The server also makes the following functions available so that they can be used within the template. These functions help extend the options for dynamic rendering of HTML. They can be used to render HTML based on specific conditions.</p>
<table>
<colgroup>
<col style="width: 50%" />
<col style="width: 50%" />
</colgroup>
<thead>
<tr class="header">
<th style="text-align: left;">Function</th>
<th style="text-align: left;">Description</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td style="text-align: left;">afterEpoch</td>
<td style="text-align: left;">Returns the time since the epoch for the given time.</td>
</tr>
<tr class="even">
<td style="text-align: left;">contains</td>
<td style="text-align: left;">Checks whether a given substring is present or not in a given string.</td>
</tr>
<tr class="odd">
<td style="text-align: left;">hasPrefix</td>
<td style="text-align: left;">Checks whether the given string begins with the specified prefix.</td>
</tr>
<tr class="even">
<td style="text-align: left;">hasSuffix</td>
<td style="text-align: left;">Checks whether the given string end with the specified suffix.</td>
</tr>
</tbody>
</table>
<h3 id="authentication-4">Authentication</h3>
<p>By default this will serve files without needing a login.</p>
<p>You can either use an htpasswd file which can take lots of users, or set a single username and password with the <code>--user</code> and <code>--pass</code> flags.</p>
<p>If no static users are configured by either of the above methods, and client certificates are required by the <code>--client-ca</code> flag passed to the server, the client certificate common name will be considered as the username.</p>
<p>Use <code>--htpasswd /path/to/htpasswd</code> to provide an htpasswd file. This is in standard apache format and supports MD5, SHA1 and BCrypt for basic authentication. Bcrypt is recommended.</p>
<p>To create an htpasswd file:</p>
<pre><code>touch htpasswd
htpasswd -B htpasswd user
htpasswd -B htpasswd anotherUser</code></pre>
<p>The password file can be updated while rclone is running.</p>
<p>Use <code>--realm</code> to set the authentication realm.</p>
<p>Use <code>--salt</code> to change the password hashing salt from the default.</p>
<h2 id="vfs---virtual-file-system-8">VFS - Virtual File System</h2>
<p>This command uses the VFS layer. This adapts the cloud storage objects that rclone uses into something which looks much more like a disk filing system.</p>
<p>Cloud storage objects have lots of properties which aren't like disk files - you can't extend them or write to the middle of them, so the VFS layer has to deal with that. Because there is no one right way of doing this there are various options explained below.</p>
<p>The VFS layer also implements a directory cache - this caches info about files and directories (but not the data) in memory.</p>
<h2 id="vfs-directory-cache-9">VFS Directory Cache</h2>
<p>Using the <code>--dir-cache-time</code> flag, you can control how long a directory should be considered up to date and not refreshed from the backend. Changes made through the VFS will appear immediately or invalidate the cache.</p>
<pre><code>--dir-cache-time duration   Time to cache directory entries for (default 5m0s)
--poll-interval duration    Time to wait between polling for changes. Must be smaller than dir-cache-time. Only on supported remotes. Set to 0 to disable (default 1m0s)</code></pre>
<p>However, changes made directly on the cloud storage by the web interface or a different copy of rclone will only be picked up once the directory cache expires if the backend configured does not support polling for changes. If the backend supports polling, changes will be picked up within the polling interval.</p>
<p>You can send a <code>SIGHUP</code> signal to rclone for it to flush all directory caches, regardless of how old they are. Assuming only one rclone instance is running, you can reset the cache like this:</p>
<pre><code>kill -SIGHUP $(pidof rclone)</code></pre>
<p>If you configure rclone with a <a href="/rc">remote control</a> then you can use rclone rc to flush the whole directory cache:</p>
<pre><code>rclone rc vfs/forget</code></pre>
<p>Or individual files or directories:</p>
<pre><code>rclone rc vfs/forget file=path/to/file dir=path/to/dir</code></pre>
<h2 id="vfs-file-buffering-9">VFS File Buffering</h2>
<p>The <code>--buffer-size</code> flag determines the amount of memory, that will be used to buffer data in advance.</p>
<p>Each open file will try to keep the specified amount of data in memory at all times. The buffered data is bound to one open file and won't be shared.</p>
<p>This flag is a upper limit for the used memory per open file. The buffer will only use memory for data that is downloaded but not not yet read. If the buffer is empty, only a small amount of memory will be used.</p>
<p>The maximum memory used by rclone for buffering can be up to <code>--buffer-size * open files</code>.</p>
<h2 id="vfs-file-caching-9">VFS File Caching</h2>
<p>These flags control the VFS file caching options. File caching is necessary to make the VFS layer appear compatible with a normal file system. It can be disabled at the cost of some compatibility.</p>
<p>For example you'll need to enable VFS caching if you want to read and write simultaneously to a file. See below for more details.</p>
<p>Note that the VFS cache is separate from the cache backend and you may find that you need one or the other or both.</p>
<pre><code>--cache-dir string                     Directory rclone will use for caching.
--vfs-cache-mode CacheMode             Cache mode off|minimal|writes|full (default off)
--vfs-cache-max-age duration           Max time since last access of objects in the cache (default 1h0m0s)
--vfs-cache-max-size SizeSuffix        Max total size of objects in the cache (default off)
--vfs-cache-min-free-space SizeSuffix  Target minimum free space on the disk containing the cache (default off)
--vfs-cache-poll-interval duration     Interval to poll the cache for stale objects (default 1m0s)
--vfs-write-back duration              Time to writeback files after last use when using cache (default 5s)</code></pre>
<p>If run with <code>-vv</code> rclone will print the location of the file cache. The files are stored in the user cache file area which is OS dependent but can be controlled with <code>--cache-dir</code> or setting the appropriate environment variable.</p>
<p>The cache has 4 different modes selected by <code>--vfs-cache-mode</code>. The higher the cache mode the more compatible rclone becomes at the cost of using disk space.</p>
<p>Note that files are written back to the remote only when they are closed and if they haven't been accessed for <code>--vfs-write-back</code> seconds. If rclone is quit or dies with files that haven't been uploaded, these will be uploaded next time rclone is run with the same flags.</p>
<p>If using <code>--vfs-cache-max-size</code> or <code>--vfs-cache-min-free-size</code> note that the cache may exceed these quotas for two reasons. Firstly because it is only checked every <code>--vfs-cache-poll-interval</code>. Secondly because open files cannot be evicted from the cache. When <code>--vfs-cache-max-size</code> or <code>--vfs-cache-min-free-size</code> is exceeded, rclone will attempt to evict the least accessed files from the cache first. rclone will start with files that haven't been accessed for the longest. This cache flushing strategy is efficient and more relevant files are likely to remain cached.</p>
<p>The <code>--vfs-cache-max-age</code> will evict files from the cache after the set time since last access has passed. The default value of 1 hour will start evicting files from cache that haven't been accessed for 1 hour. When a cached file is accessed the 1 hour timer is reset to 0 and will wait for 1 more hour before evicting. Specify the time with standard notation, s, m, h, d, w .</p>
<p>You <strong>should not</strong> run two copies of rclone using the same VFS cache with the same or overlapping remotes if using <code>--vfs-cache-mode &gt; off</code>. This can potentially cause data corruption if you do. You can work around this by giving each rclone its own cache hierarchy with <code>--cache-dir</code>. You don't need to worry about this if the remotes in use don't overlap.</p>
<h3 id="vfs-cache-mode-off-9">--vfs-cache-mode off</h3>
<p>In this mode (the default) the cache will read directly from the remote and write directly to the remote without caching anything on disk.</p>
<p>This will mean some operations are not possible</p>
<ul>
<li>Files can't be opened for both read AND write</li>
<li>Files opened for write can't be seeked</li>
<li>Existing files opened for write must have O_TRUNC set</li>
<li>Files open for read with O_TRUNC will be opened write only</li>
<li>Files open for write only will behave as if O_TRUNC was supplied</li>
<li>Open modes O_APPEND, O_TRUNC are ignored</li>
<li>If an upload fails it can't be retried</li>
</ul>
<h3 id="vfs-cache-mode-minimal-9">--vfs-cache-mode minimal</h3>
<p>This is very similar to "off" except that files opened for read AND write will be buffered to disk. This means that files opened for write will be a lot more compatible, but uses the minimal disk space.</p>
<p>These operations are not possible</p>
<ul>
<li>Files opened for write only can't be seeked</li>
<li>Existing files opened for write must have O_TRUNC set</li>
<li>Files opened for write only will ignore O_APPEND, O_TRUNC</li>
<li>If an upload fails it can't be retried</li>
</ul>
<h3 id="vfs-cache-mode-writes-9">--vfs-cache-mode writes</h3>
<p>In this mode files opened for read only are still read directly from the remote, write only and read/write files are buffered to disk first.</p>
<p>This mode should support all normal file system operations.</p>
<p>If an upload fails it will be retried at exponentially increasing intervals up to 1 minute.</p>
<h3 id="vfs-cache-mode-full-9">--vfs-cache-mode full</h3>
<p>In this mode all reads and writes are buffered to and from disk. When data is read from the remote this is buffered to disk as well.</p>
<p>In this mode the files in the cache will be sparse files and rclone will keep track of which bits of the files it has downloaded.</p>
<p>So if an application only reads the starts of each file, then rclone will only buffer the start of the file. These files will appear to be their full size in the cache, but they will be sparse files with only the data that has been downloaded present in them.</p>
<p>This mode should support all normal file system operations and is otherwise identical to <code>--vfs-cache-mode</code> writes.</p>
<p>When reading a file rclone will read <code>--buffer-size</code> plus <code>--vfs-read-ahead</code> bytes ahead. The <code>--buffer-size</code> is buffered in memory whereas the <code>--vfs-read-ahead</code> is buffered on disk.</p>
<p>When using this mode it is recommended that <code>--buffer-size</code> is not set too large and <code>--vfs-read-ahead</code> is set large if required.</p>
<p><strong>IMPORTANT</strong> not all file systems support sparse files. In particular FAT/exFAT do not. Rclone will perform very badly if the cache directory is on a filesystem which doesn't support sparse files and it will log an ERROR message if one is detected.</p>
<h3 id="fingerprinting-9">Fingerprinting</h3>
<p>Various parts of the VFS use fingerprinting to see if a local file copy has changed relative to a remote file. Fingerprints are made from:</p>
<ul>
<li>size</li>
<li>modification time</li>
<li>hash</li>
</ul>
<p>where available on an object.</p>
<p>On some backends some of these attributes are slow to read (they take an extra API call per object, or extra work per object).</p>
<p>For example <code>hash</code> is slow with the <code>local</code> and <code>sftp</code> backends as they have to read the entire file and hash it, and <code>modtime</code> is slow with the <code>s3</code>, <code>swift</code>, <code>ftp</code> and <code>qinqstor</code> backends because they need to do an extra API call to fetch it.</p>
<p>If you use the <code>--vfs-fast-fingerprint</code> flag then rclone will not include the slow operations in the fingerprint. This makes the fingerprinting less accurate but much faster and will improve the opening time of cached files.</p>
<p>If you are running a vfs cache over <code>local</code>, <code>s3</code> or <code>swift</code> backends then using this flag is recommended.</p>
<p>Note that if you change the value of this flag, the fingerprints of the files in the cache may be invalidated and the files will need to be downloaded again.</p>
<h2 id="vfs-chunked-reading-9">VFS Chunked Reading</h2>
<p>When rclone reads files from a remote it reads them in chunks. This means that rather than requesting the whole file rclone reads the chunk specified. This can reduce the used download quota for some remotes by requesting only chunks from the remote that are actually read, at the cost of an increased number of requests.</p>
<p>These flags control the chunking:</p>
<pre><code>--vfs-read-chunk-size SizeSuffix        Read the source objects in chunks (default 128M)
--vfs-read-chunk-size-limit SizeSuffix  Max chunk doubling size (default off)
--vfs-read-chunk-streams int            The number of parallel streams to read at once</code></pre>
<p>The chunking behaves differently depending on the <code>--vfs-read-chunk-streams</code> parameter.</p>
<h3 id="vfs-read-chunk-streams-0-18"><code>--vfs-read-chunk-streams</code> == 0</h3>
<p>Rclone will start reading a chunk of size <code>--vfs-read-chunk-size</code>, and then double the size for each read. When <code>--vfs-read-chunk-size-limit</code> is specified, and greater than <code>--vfs-read-chunk-size</code>, the chunk size for each open file will get doubled only until the specified value is reached. If the value is "off", which is the default, the limit is disabled and the chunk size will grow indefinitely.</p>
<p>With <code>--vfs-read-chunk-size 100M</code> and <code>--vfs-read-chunk-size-limit 0</code> the following parts will be downloaded: 0-100M, 100M-200M, 200M-300M, 300M-400M and so on. When <code>--vfs-read-chunk-size-limit 500M</code> is specified, the result would be 0-100M, 100M-300M, 300M-700M, 700M-1200M, 1200M-1700M and so on.</p>
<p>Setting <code>--vfs-read-chunk-size</code> to <code>0</code> or "off" disables chunked reading.</p>
<p>The chunks will not be buffered in memory.</p>
<h3 id="vfs-read-chunk-streams-0-19"><code>--vfs-read-chunk-streams</code> &gt; 0</h3>
<p>Rclone reads <code>--vfs-read-chunk-streams</code> chunks of size <code>--vfs-read-chunk-size</code> concurrently. The size for each read will stay constant.</p>
<p>This improves performance performance massively on high latency links or very high bandwidth links to high performance object stores.</p>
<p>Some experimentation will be needed to find the optimum values of <code>--vfs-read-chunk-size</code> and <code>--vfs-read-chunk-streams</code> as these will depend on the backend in use and the latency to the backend.</p>
<p>For high performance object stores (eg AWS S3) a reasonable place to start might be <code>--vfs-read-chunk-streams 16</code> and <code>--vfs-read-chunk-size 4M</code>. In testing with AWS S3 the performance scaled roughly as the <code>--vfs-read-chunk-streams</code> setting.</p>
<p>Similar settings should work for high latency links, but depending on the latency they may need more <code>--vfs-read-chunk-streams</code> in order to get the throughput.</p>
<h2 id="vfs-performance-9">VFS Performance</h2>
<p>These flags may be used to enable/disable features of the VFS for performance or other reasons. See also the <a href="#vfs-chunked-reading">chunked reading</a> feature.</p>
<p>In particular S3 and Swift benefit hugely from the <code>--no-modtime</code> flag (or use <code>--use-server-modtime</code> for a slightly different effect) as each read of the modification time takes a transaction.</p>
<pre><code>--no-checksum     Don&#39;t compare checksums on up/download.
--no-modtime      Don&#39;t read/write the modification time (can speed things up).
--no-seek         Don&#39;t allow seeking in files.
--read-only       Only allow read-only access.</code></pre>
<p>Sometimes rclone is delivered reads or writes out of order. Rather than seeking rclone will wait a short time for the in sequence read or write to come in. These flags only come into effect when not using an on disk cache file.</p>
<pre><code>--vfs-read-wait duration   Time to wait for in-sequence read before seeking (default 20ms)
--vfs-write-wait duration  Time to wait for in-sequence write before giving error (default 1s)</code></pre>
<p>When using VFS write caching (<code>--vfs-cache-mode</code> with value writes or full), the global flag <code>--transfers</code> can be set to adjust the number of parallel uploads of modified files from the cache (the related global flag <code>--checkers</code> has no effect on the VFS).</p>
<pre><code>--transfers int  Number of file transfers to run in parallel (default 4)</code></pre>
<h2 id="vfs-case-sensitivity-9">VFS Case Sensitivity</h2>
<p>Linux file systems are case-sensitive: two files can differ only by case, and the exact case must be used when opening a file.</p>
<p>File systems in modern Windows are case-insensitive but case-preserving: although existing files can be opened using any case, the exact case used to create the file is preserved and available for programs to query. It is not allowed for two files in the same directory to differ only by case.</p>
<p>Usually file systems on macOS are case-insensitive. It is possible to make macOS file systems case-sensitive but that is not the default.</p>
<p>The <code>--vfs-case-insensitive</code> VFS flag controls how rclone handles these two cases. If its value is "false", rclone passes file names to the remote as-is. If the flag is "true" (or appears without a value on the command line), rclone may perform a "fixup" as explained below.</p>
<p>The user may specify a file name to open/delete/rename/etc with a case different than what is stored on the remote. If an argument refers to an existing file with exactly the same name, then the case of the existing file on the disk will be used. However, if a file name with exactly the same name is not found but a name differing only by case exists, rclone will transparently fixup the name. This fixup happens only when an existing file is requested. Case sensitivity of file names created anew by rclone is controlled by the underlying remote.</p>
<p>Note that case sensitivity of the operating system running rclone (the target) may differ from case sensitivity of a file system presented by rclone (the source). The flag controls whether "fixup" is performed to satisfy the target.</p>
<p>If the flag is not provided on the command line, then its default value depends on the operating system where rclone runs: "true" on Windows and macOS, "false" otherwise. If the flag is provided without a value, then it is "true".</p>
<p>The <code>--no-unicode-normalization</code> flag controls whether a similar "fixup" is performed for filenames that differ but are <a href="https://en.wikipedia.org/wiki/Unicode_equivalence">canonically equivalent</a> with respect to unicode. Unicode normalization can be particularly helpful for users of macOS, which prefers form NFD instead of the NFC used by most other platforms. It is therefore highly recommended to keep the default of <code>false</code> on macOS, to avoid encoding compatibility issues.</p>
<p>In the (probably unlikely) event that a directory has multiple duplicate filenames after applying case and unicode normalization, the <code>--vfs-block-norm-dupes</code> flag allows hiding these duplicates. This comes with a performance tradeoff, as rclone will have to scan the entire directory for duplicates when listing a directory. For this reason, it is recommended to leave this disabled if not needed. However, macOS users may wish to consider using it, as otherwise, if a remote directory contains both NFC and NFD versions of the same filename, an odd situation will occur: both versions of the file will be visible in the mount, and both will appear to be editable, however, editing either version will actually result in only the NFD version getting edited under the hood. <code>--vfs-block- norm-dupes</code> prevents this confusion by detecting this scenario, hiding the duplicates, and logging an error, similar to how this is handled in <code>rclone sync</code>.</p>
<h2 id="vfs-disk-options-9">VFS Disk Options</h2>
<p>This flag allows you to manually set the statistics about the filing system. It can be useful when those statistics cannot be read correctly automatically.</p>
<pre><code>--vfs-disk-space-total-size    Manually set the total disk space size (example: 256G, default: -1)</code></pre>
<h2 id="alternate-report-of-used-bytes-9">Alternate report of used bytes</h2>
<p>Some backends, most notably S3, do not report the amount of bytes used. If you need this information to be available when running <code>df</code> on the filesystem, then pass the flag <code>--vfs-used-is-size</code> to rclone. With this flag set, instead of relying on the backend to report this information, rclone will scan the whole remote similar to <code>rclone size</code> and compute the total used space itself.</p>
<p><em>WARNING.</em> Contrary to <code>rclone size</code>, this flag ignores filters so that the result is accurate. However, this is very inefficient and may cost lots of API calls resulting in extra charges. Use it as a last resort and only with caching.</p>
<h2 id="auth-proxy-3">Auth Proxy</h2>
<p>If you supply the parameter <code>--auth-proxy /path/to/program</code> then rclone will use that program to generate backends on the fly which then are used to authenticate incoming requests. This uses a simple JSON based protocol with input on STDIN and output on STDOUT.</p>
<p><strong>PLEASE NOTE:</strong> <code>--auth-proxy</code> and <code>--authorized-keys</code> cannot be used together, if <code>--auth-proxy</code> is set the authorized keys option will be ignored.</p>
<p>There is an example program <a href="https://github.com/rclone/rclone/blob/master/bin/test_proxy.py">bin/test_proxy.py</a> in the rclone source code.</p>
<p>The program's job is to take a <code>user</code> and <code>pass</code> on the input and turn those into the config for a backend on STDOUT in JSON format. This config will have any default parameters for the backend added, but it won't use configuration from environment variables or command line options - it is the job of the proxy program to make a complete config.</p>
<p>This config generated must have this extra parameter - <code>_root</code> - root to use for the backend</p>
<p>And it may have this parameter - <code>_obscure</code> - comma separated strings for parameters to obscure</p>
<p>If password authentication was used by the client, input to the proxy process (on STDIN) would look similar to this:</p>
<pre><code>{
    &quot;user&quot;: &quot;me&quot;,
    &quot;pass&quot;: &quot;mypassword&quot;
}</code></pre>
<p>If public-key authentication was used by the client, input to the proxy process (on STDIN) would look similar to this:</p>
<pre><code>{
    &quot;user&quot;: &quot;me&quot;,
    &quot;public_key&quot;: &quot;AAAAB3NzaC1yc2EAAAADAQABAAABAQDuwESFdAe14hVS6omeyX7edc...JQdf&quot;
}</code></pre>
<p>And as an example return this on STDOUT</p>
<pre><code>{
    &quot;type&quot;: &quot;sftp&quot;,
    &quot;_root&quot;: &quot;&quot;,
    &quot;_obscure&quot;: &quot;pass&quot;,
    &quot;user&quot;: &quot;me&quot;,
    &quot;pass&quot;: &quot;mypassword&quot;,
    &quot;host&quot;: &quot;sftp.example.com&quot;
}</code></pre>
<p>This would mean that an SFTP backend would be created on the fly for the <code>user</code> and <code>pass</code>/<code>public_key</code> returned in the output to the host given. Note that since <code>_obscure</code> is set to <code>pass</code>, rclone will obscure the <code>pass</code> parameter before creating the backend (which is required for sftp backends).</p>
<p>The program can manipulate the supplied <code>user</code> in any way, for example to make proxy to many different sftp backends, you could make the <code>user</code> be <code>user@example.com</code> and then set the <code>host</code> to <code>example.com</code> in the output and the user to <code>user</code>. For security you'd probably want to restrict the <code>host</code> to a limited list.</p>
<p>Note that an internal cache is keyed on <code>user</code> so only use that for configuration, don't use <code>pass</code> or <code>public_key</code>. This also means that if a user's password or public-key is changed the cache will need to expire (which takes 5 mins) before it takes effect.</p>
<p>This can be used to build general purpose proxies to any kind of backend that rclone supports.</p>
<pre><code>rclone serve webdav remote:path [flags]</code></pre>
<h2 id="options-79">Options</h2>
<pre><code>      --addr stringArray                       IPaddress:Port, :Port or [unix://]/path/to/socket to bind server to (default [127.0.0.1:8080])
      --allow-origin string                    Origin which cross-domain request (CORS) can be executed from
      --auth-proxy string                      A program to use to create the backend from the auth
      --baseurl string                         Prefix for URLs - leave blank for root
      --cert string                            TLS PEM key (concatenation of certificate and CA certificate)
      --client-ca string                       Client certificate authority to verify clients with
      --dir-cache-time Duration                Time to cache directory entries for (default 5m0s)
      --dir-perms FileMode                     Directory permissions (default 777)
      --disable-dir-list                       Disable HTML directory list on GET request for a directory
      --etag-hash string                       Which hash to use for the ETag, or auto or blank for off
      --file-perms FileMode                    File permissions (default 666)
      --gid uint32                             Override the gid field set by the filesystem (not supported on Windows) (default 1000)
  -h, --help                                   help for webdav
      --htpasswd string                        A htpasswd file - if not provided no authentication is done
      --key string                             TLS PEM Private key
      --max-header-bytes int                   Maximum size of request header (default 4096)
      --min-tls-version string                 Minimum TLS version that is acceptable (default &quot;tls1.0&quot;)
      --no-checksum                            Don&#39;t compare checksums on up/download
      --no-modtime                             Don&#39;t read/write the modification time (can speed things up)
      --no-seek                                Don&#39;t allow seeking in files
      --pass string                            Password for authentication
      --poll-interval Duration                 Time to wait between polling for changes, must be smaller than dir-cache-time and only on supported remotes (set 0 to disable) (default 1m0s)
      --read-only                              Only allow read-only access
      --realm string                           Realm for authentication
      --salt string                            Password hashing salt (default &quot;dlPL2MqE&quot;)
      --server-read-timeout Duration           Timeout for server reading data (default 1h0m0s)
      --server-write-timeout Duration          Timeout for server writing data (default 1h0m0s)
      --template string                        User-specified template
      --uid uint32                             Override the uid field set by the filesystem (not supported on Windows) (default 1000)
      --umask FileMode                         Override the permission bits set by the filesystem (not supported on Windows) (default 002)
      --user string                            User name for authentication
      --vfs-block-norm-dupes                   If duplicate filenames exist in the same directory (after normalization), log an error and hide the duplicates (may have a performance cost)
      --vfs-cache-max-age Duration             Max time since last access of objects in the cache (default 1h0m0s)
      --vfs-cache-max-size SizeSuffix          Max total size of objects in the cache (default off)
      --vfs-cache-min-free-space SizeSuffix    Target minimum free space on the disk containing the cache (default off)
      --vfs-cache-mode CacheMode               Cache mode off|minimal|writes|full (default off)
      --vfs-cache-poll-interval Duration       Interval to poll the cache for stale objects (default 1m0s)
      --vfs-case-insensitive                   If a file name not found, find a case insensitive match
      --vfs-disk-space-total-size SizeSuffix   Specify the total space of disk (default off)
      --vfs-fast-fingerprint                   Use fast (less accurate) fingerprints for change detection
      --vfs-read-ahead SizeSuffix              Extra read ahead over --buffer-size when using cache-mode full
      --vfs-read-chunk-size SizeSuffix         Read the source objects in chunks (default 128Mi)
      --vfs-read-chunk-size-limit SizeSuffix   If greater than --vfs-read-chunk-size, double the chunk size after each chunk read, until the limit is reached (&#39;off&#39; is unlimited) (default off)
      --vfs-read-chunk-streams int             The number of parallel streams to read at once
      --vfs-read-wait Duration                 Time to wait for in-sequence read before seeking (default 20ms)
      --vfs-refresh                            Refreshes the directory cache recursively in the background on start
      --vfs-used-is-size rclone size           Use the rclone size algorithm for Used size
      --vfs-write-back Duration                Time to writeback files after last use when using cache (default 5s)
      --vfs-write-wait Duration                Time to wait for in-sequence write before giving error (default 1s)</code></pre>
<p>Options shared with other commands are described next. See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
<h3 id="filter-options-30">Filter Options</h3>
<p>Flags for filtering directory listings</p>
<pre><code>      --delete-excluded                     Delete files on dest excluded from sync
      --exclude stringArray                 Exclude files matching pattern
      --exclude-from stringArray            Read file exclude patterns from file (use - to read from stdin)
      --exclude-if-present stringArray      Exclude directories if filename is present
      --files-from stringArray              Read list of source-file names from file (use - to read from stdin)
      --files-from-raw stringArray          Read list of source-file names from file without any processing of lines (use - to read from stdin)
  -f, --filter stringArray                  Add a file filtering rule
      --filter-from stringArray             Read file filtering patterns from a file (use - to read from stdin)
      --ignore-case                         Ignore case in filters (case insensitive)
      --include stringArray                 Include files matching pattern
      --include-from stringArray            Read file include patterns from file (use - to read from stdin)
      --max-age Duration                    Only transfer files younger than this in s or suffix ms|s|m|h|d|w|M|y (default off)
      --max-depth int                       If set limits the recursion depth to this (default -1)
      --max-size SizeSuffix                 Only transfer files smaller than this in KiB or suffix B|K|M|G|T|P (default off)
      --metadata-exclude stringArray        Exclude metadatas matching pattern
      --metadata-exclude-from stringArray   Read metadata exclude patterns from file (use - to read from stdin)
      --metadata-filter stringArray         Add a metadata filtering rule
      --metadata-filter-from stringArray    Read metadata filtering patterns from a file (use - to read from stdin)
      --metadata-include stringArray        Include metadatas matching pattern
      --metadata-include-from stringArray   Read metadata include patterns from file (use - to read from stdin)
      --min-age Duration                    Only transfer files older than this in s or suffix ms|s|m|h|d|w|M|y (default off)
      --min-size SizeSuffix                 Only transfer files bigger than this in KiB or suffix B|K|M|G|T|P (default off)</code></pre>
<h2 id="see-also-79">See Also</h2>
<ul>
<li><a href="https://rclone.org/commands/rclone_serve/">rclone serve</a> - Serve a remote over a protocol.</li>
</ul>
<h1 id="rclone-settier">rclone settier</h1>
<p>Changes storage class/tier of objects in remote.</p>
<h2 id="synopsis-72">Synopsis</h2>
<p>Changes storage tier or class at remote if supported. Few cloud storage services provides different storage classes on objects, for example AWS S3 and Glacier, Azure Blob storage - Hot, Cool and Archive, Google Cloud Storage, Regional Storage, Nearline, Coldline etc.</p>
<p>Note that, certain tier changes make objects not available to access immediately. For example tiering to archive in azure blob storage makes objects in frozen state, user can restore by setting tier to Hot/Cool, similarly S3 to Glacier makes object inaccessible.true</p>
<p>You can use it to tier single object</p>
<pre><code>rclone settier Cool remote:path/file</code></pre>
<p>Or use rclone filters to set tier on only specific files</p>
<pre><code>rclone --include &quot;*.txt&quot; settier Hot remote:path/dir</code></pre>
<p>Or just provide remote directory and all files in directory will be tiered</p>
<pre><code>rclone settier tier remote:path/dir</code></pre>
<pre><code>rclone settier tier remote:path [flags]</code></pre>
<h2 id="options-80">Options</h2>
<pre><code>  -h, --help   help for settier</code></pre>
<p>See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
<h2 id="see-also-80">See Also</h2>
<ul>
<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
</ul>
<h1 id="rclone-test">rclone test</h1>
<p>Run a test command</p>
<h2 id="synopsis-73">Synopsis</h2>
<p>Rclone test is used to run test commands.</p>
<p>Select which test command you want with the subcommand, eg</p>
<pre><code>rclone test memory remote:</code></pre>
<p>Each subcommand has its own options which you can see in their help.</p>
<p><strong>NB</strong> Be careful running these commands, they may do strange things so reading their documentation first is recommended.</p>
<h2 id="options-81">Options</h2>
<pre><code>  -h, --help   help for test</code></pre>
<p>See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
<h2 id="see-also-81">See Also</h2>
<ul>
<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
<li><a href="https://rclone.org/commands/rclone_test_changenotify/">rclone test changenotify</a> - Log any change notify requests for the remote passed in.</li>
<li><a href="https://rclone.org/commands/rclone_test_histogram/">rclone test histogram</a> - Makes a histogram of file name characters.</li>
<li><a href="https://rclone.org/commands/rclone_test_info/">rclone test info</a> - Discovers file name or other limitations for paths.</li>
<li><a href="https://rclone.org/commands/rclone_test_makefile/">rclone test makefile</a> - Make files with random contents of the size given</li>
<li><a href="https://rclone.org/commands/rclone_test_makefiles/">rclone test makefiles</a> - Make a random file hierarchy in a directory</li>
<li><a href="https://rclone.org/commands/rclone_test_memory/">rclone test memory</a> - Load all the objects at remote:path into memory and report memory stats.</li>
</ul>
<h1 id="rclone-test-changenotify">rclone test changenotify</h1>
<p>Log any change notify requests for the remote passed in.</p>
<pre><code>rclone test changenotify remote: [flags]</code></pre>
<h2 id="options-82">Options</h2>
<pre><code>  -h, --help                     help for changenotify
      --poll-interval Duration   Time to wait between polling for changes (default 10s)</code></pre>
<p>See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
<h2 id="see-also-82">See Also</h2>
<ul>
<li><a href="https://rclone.org/commands/rclone_test/">rclone test</a> - Run a test command</li>
</ul>
<h1 id="rclone-test-histogram">rclone test histogram</h1>
<p>Makes a histogram of file name characters.</p>
<h2 id="synopsis-74">Synopsis</h2>
<p>This command outputs JSON which shows the histogram of characters used in filenames in the remote:path specified.</p>
<p>The data doesn't contain any identifying information but is useful for the rclone developers when developing filename compression.</p>
<pre><code>rclone test histogram [remote:path] [flags]</code></pre>
<h2 id="options-83">Options</h2>
<pre><code>  -h, --help   help for histogram</code></pre>
<p>See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
<h2 id="see-also-83">See Also</h2>
<ul>
<li><a href="https://rclone.org/commands/rclone_test/">rclone test</a> - Run a test command</li>
</ul>
<h1 id="rclone-test-info">rclone test info</h1>
<p>Discovers file name or other limitations for paths.</p>
<h2 id="synopsis-75">Synopsis</h2>
<p>Discovers what filenames and upload methods are possible to write to the paths passed in and how long they can be. It can take some time. It will write test files into the remote:path passed in. It outputs a bit of go code for each one.</p>
<p><strong>NB</strong> this can create undeletable files and other hazards - use with care</p>
<pre><code>rclone test info [remote:path]+ [flags]</code></pre>
<h2 id="options-84">Options</h2>
<pre><code>      --all                    Run all tests
      --check-base32768        Check can store all possible base32768 characters
      --check-control          Check control characters
      --check-length           Check max filename length
      --check-normalization    Check UTF-8 Normalization
      --check-streaming        Check uploads with indeterminate file size
  -h, --help                   help for info
      --keep-test-files        Keep test files after execution
      --upload-wait Duration   Wait after writing a file (default 0s)
      --write-json string      Write results to file</code></pre>
<p>See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
<h2 id="see-also-84">See Also</h2>
<ul>
<li><a href="https://rclone.org/commands/rclone_test/">rclone test</a> - Run a test command</li>
</ul>
<h1 id="rclone-test-makefile">rclone test makefile</h1>
<p>Make files with random contents of the size given</p>
<pre><code>rclone test makefile &lt;size&gt; [&lt;file&gt;]+ [flags]</code></pre>
<h2 id="options-85">Options</h2>
<pre><code>      --ascii      Fill files with random ASCII printable bytes only
      --chargen    Fill files with a ASCII chargen pattern
  -h, --help       help for makefile
      --pattern    Fill files with a periodic pattern
      --seed int   Seed for the random number generator (0 for random) (default 1)
      --sparse     Make the files sparse (appear to be filled with ASCII 0x00)
      --zero       Fill files with ASCII 0x00</code></pre>
<p>See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
<h2 id="see-also-85">See Also</h2>
<ul>
<li><a href="https://rclone.org/commands/rclone_test/">rclone test</a> - Run a test command</li>
</ul>
<h1 id="rclone-test-makefiles">rclone test makefiles</h1>
<p>Make a random file hierarchy in a directory</p>
<pre><code>rclone test makefiles &lt;dir&gt; [flags]</code></pre>
<h2 id="options-86">Options</h2>
<pre><code>      --ascii                      Fill files with random ASCII printable bytes only
      --chargen                    Fill files with a ASCII chargen pattern
      --files int                  Number of files to create (default 1000)
      --files-per-directory int    Average number of files per directory (default 10)
  -h, --help                       help for makefiles
      --max-depth int              Maximum depth of directory hierarchy (default 10)
      --max-file-size SizeSuffix   Maximum size of files to create (default 100)
      --max-name-length int        Maximum size of file names (default 12)
      --min-file-size SizeSuffix   Minimum size of file to create
      --min-name-length int        Minimum size of file names (default 4)
      --pattern                    Fill files with a periodic pattern
      --seed int                   Seed for the random number generator (0 for random) (default 1)
      --sparse                     Make the files sparse (appear to be filled with ASCII 0x00)
      --zero                       Fill files with ASCII 0x00</code></pre>
<p>See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
<h2 id="see-also-86">See Also</h2>
<ul>
<li><a href="https://rclone.org/commands/rclone_test/">rclone test</a> - Run a test command</li>
</ul>
<h1 id="rclone-test-memory">rclone test memory</h1>
<p>Load all the objects at remote:path into memory and report memory stats.</p>
<pre><code>rclone test memory remote:path [flags]</code></pre>
<h2 id="options-87">Options</h2>
<pre><code>  -h, --help   help for memory</code></pre>
<p>See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
<h2 id="see-also-87">See Also</h2>
<ul>
<li><a href="https://rclone.org/commands/rclone_test/">rclone test</a> - Run a test command</li>
</ul>
<h1 id="rclone-touch">rclone touch</h1>
<p>Create new file or change file modification time.</p>
<h2 id="synopsis-76">Synopsis</h2>
<p>Set the modification time on file(s) as specified by remote:path to have the current time.</p>
<p>If remote:path does not exist then a zero sized file will be created, unless <code>--no-create</code> or <code>--recursive</code> is provided.</p>
<p>If <code>--recursive</code> is used then recursively sets the modification time on all existing files that is found under the path. Filters are supported, and you can test with the <code>--dry-run</code> or the <code>--interactive</code>/<code>-i</code> flag.</p>
<p>If <code>--timestamp</code> is used then sets the modification time to that time instead of the current time. Times may be specified as one of:</p>
<ul>
<li>'YYMMDD' - e.g. 17.10.30</li>
<li>'YYYY-MM-DDTHH:MM:SS' - e.g. 2006-01-02T15:04:05</li>
<li>'YYYY-MM-DDTHH:MM:SS.SSS' - e.g. 2006-01-02T15:04:05.123456789</li>
</ul>
<p>Note that value of <code>--timestamp</code> is in UTC. If you want local time then add the <code>--localtime</code> flag.</p>
<pre><code>rclone touch remote:path [flags]</code></pre>
<h2 id="options-88">Options</h2>
<pre><code>  -h, --help               help for touch
      --localtime          Use localtime for timestamp, not UTC
  -C, --no-create          Do not create the file if it does not exist (implied with --recursive)
  -R, --recursive          Recursively touch all files
  -t, --timestamp string   Use specified time instead of the current time of day</code></pre>
<p>Options shared with other commands are described next. See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
<h3 id="important-options-17">Important Options</h3>
<p>Important flags useful for most commands</p>
<pre><code>  -n, --dry-run         Do a trial run with no permanent changes
  -i, --interactive     Enable interactive mode
  -v, --verbose count   Print lots more stuff (repeat for more)</code></pre>
<h3 id="filter-options-31">Filter Options</h3>
<p>Flags for filtering directory listings</p>
<pre><code>      --delete-excluded                     Delete files on dest excluded from sync
      --exclude stringArray                 Exclude files matching pattern
      --exclude-from stringArray            Read file exclude patterns from file (use - to read from stdin)
      --exclude-if-present stringArray      Exclude directories if filename is present
      --files-from stringArray              Read list of source-file names from file (use - to read from stdin)
      --files-from-raw stringArray          Read list of source-file names from file without any processing of lines (use - to read from stdin)
  -f, --filter stringArray                  Add a file filtering rule
      --filter-from stringArray             Read file filtering patterns from a file (use - to read from stdin)
      --ignore-case                         Ignore case in filters (case insensitive)
      --include stringArray                 Include files matching pattern
      --include-from stringArray            Read file include patterns from file (use - to read from stdin)
      --max-age Duration                    Only transfer files younger than this in s or suffix ms|s|m|h|d|w|M|y (default off)
      --max-depth int                       If set limits the recursion depth to this (default -1)
      --max-size SizeSuffix                 Only transfer files smaller than this in KiB or suffix B|K|M|G|T|P (default off)
      --metadata-exclude stringArray        Exclude metadatas matching pattern
      --metadata-exclude-from stringArray   Read metadata exclude patterns from file (use - to read from stdin)
      --metadata-filter stringArray         Add a metadata filtering rule
      --metadata-filter-from stringArray    Read metadata filtering patterns from a file (use - to read from stdin)
      --metadata-include stringArray        Include metadatas matching pattern
      --metadata-include-from stringArray   Read metadata include patterns from file (use - to read from stdin)
      --min-age Duration                    Only transfer files older than this in s or suffix ms|s|m|h|d|w|M|y (default off)
      --min-size SizeSuffix                 Only transfer files bigger than this in KiB or suffix B|K|M|G|T|P (default off)</code></pre>
<h3 id="listing-options-20">Listing Options</h3>
<p>Flags for listing directories</p>
<pre><code>      --default-time Time   Time to show if modtime is unknown for files and directories (default 2000-01-01T00:00:00Z)
      --fast-list           Use recursive list if available; uses more memory but fewer transactions</code></pre>
<h2 id="see-also-88">See Also</h2>
<ul>
<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
</ul>
<h1 id="rclone-tree">rclone tree</h1>
<p>List the contents of the remote in a tree like fashion.</p>
<h2 id="synopsis-77">Synopsis</h2>
<p>Lists the contents of a remote in a similar way to the unix tree command.</p>
<p>For example</p>
<pre><code>$ rclone tree remote:path
/
├── file1
├── file2
├── file3
└── subdir
    ├── file4
    └── file5

1 directories, 5 files</code></pre>
<p>You can use any of the filtering options with the tree command (e.g. <code>--include</code> and <code>--exclude</code>. You can also use <code>--fast-list</code>.</p>
<p>The tree command has many options for controlling the listing which are compatible with the tree command, for example you can include file sizes with <code>--size</code>. Note that not all of them have short options as they conflict with rclone's short options.</p>
<p>For a more interactive navigation of the remote see the <a href="https://rclone.org/commands/rclone_ncdu/">ncdu</a> command.</p>
<pre><code>rclone tree remote:path [flags]</code></pre>
<h2 id="options-89">Options</h2>
<pre><code>  -a, --all             All files are listed (list . files too)
  -d, --dirs-only       List directories only
      --dirsfirst       List directories before files (-U disables)
      --full-path       Print the full path prefix for each file
  -h, --help            help for tree
      --level int       Descend only level directories deep
  -D, --modtime         Print the date of last modification.
      --noindent        Don&#39;t print indentation lines
      --noreport        Turn off file/directory count at end of tree listing
  -o, --output string   Output to file instead of stdout
  -p, --protections     Print the protections for each file.
  -Q, --quote           Quote filenames with double quotes.
  -s, --size            Print the size in bytes of each file.
      --sort string     Select sort: name,version,size,mtime,ctime
      --sort-ctime      Sort files by last status change time
  -t, --sort-modtime    Sort files by last modification time
  -r, --sort-reverse    Reverse the order of the sort
  -U, --unsorted        Leave files unsorted
      --version         Sort files alphanumerically by version</code></pre>
<p>Options shared with other commands are described next. See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
<h3 id="filter-options-32">Filter Options</h3>
<p>Flags for filtering directory listings</p>
<pre><code>      --delete-excluded                     Delete files on dest excluded from sync
      --exclude stringArray                 Exclude files matching pattern
      --exclude-from stringArray            Read file exclude patterns from file (use - to read from stdin)
      --exclude-if-present stringArray      Exclude directories if filename is present
      --files-from stringArray              Read list of source-file names from file (use - to read from stdin)
      --files-from-raw stringArray          Read list of source-file names from file without any processing of lines (use - to read from stdin)
  -f, --filter stringArray                  Add a file filtering rule
      --filter-from stringArray             Read file filtering patterns from a file (use - to read from stdin)
      --ignore-case                         Ignore case in filters (case insensitive)
      --include stringArray                 Include files matching pattern
      --include-from stringArray            Read file include patterns from file (use - to read from stdin)
      --max-age Duration                    Only transfer files younger than this in s or suffix ms|s|m|h|d|w|M|y (default off)
      --max-depth int                       If set limits the recursion depth to this (default -1)
      --max-size SizeSuffix                 Only transfer files smaller than this in KiB or suffix B|K|M|G|T|P (default off)
      --metadata-exclude stringArray        Exclude metadatas matching pattern
      --metadata-exclude-from stringArray   Read metadata exclude patterns from file (use - to read from stdin)
      --metadata-filter stringArray         Add a metadata filtering rule
      --metadata-filter-from stringArray    Read metadata filtering patterns from a file (use - to read from stdin)
      --metadata-include stringArray        Include metadatas matching pattern
      --metadata-include-from stringArray   Read metadata include patterns from file (use - to read from stdin)
      --min-age Duration                    Only transfer files older than this in s or suffix ms|s|m|h|d|w|M|y (default off)
      --min-size SizeSuffix                 Only transfer files bigger than this in KiB or suffix B|K|M|G|T|P (default off)</code></pre>
<h3 id="listing-options-21">Listing Options</h3>
<p>Flags for listing directories</p>
<pre><code>      --default-time Time   Time to show if modtime is unknown for files and directories (default 2000-01-01T00:00:00Z)
      --fast-list           Use recursive list if available; uses more memory but fewer transactions</code></pre>
<h2 id="see-also-89">See Also</h2>
<ul>
<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
</ul>
<h2 id="copying-single-files">Copying single files</h2>
<p>rclone normally syncs or copies directories. However, if the source remote points to a file, rclone will just copy that file. The destination remote must point to a directory - rclone will give the error <code>Failed to create file system for "remote:file": is a file not a directory</code> if it isn't.</p>
<p>For example, suppose you have a remote with a file in called <code>test.jpg</code>, then you could copy just that file like this</p>
<pre><code>rclone copy remote:test.jpg /tmp/download</code></pre>
<p>The file <code>test.jpg</code> will be placed inside <code>/tmp/download</code>.</p>
<p>This is equivalent to specifying</p>
<pre><code>rclone copy --files-from /tmp/files remote: /tmp/download</code></pre>
<p>Where <code>/tmp/files</code> contains the single line</p>
<pre><code>test.jpg</code></pre>
<p>It is recommended to use <code>copy</code> when copying individual files, not <code>sync</code>. They have pretty much the same effect but <code>copy</code> will use a lot less memory.</p>
<h2 id="syntax-of-remote-paths">Syntax of remote paths</h2>
<p>The syntax of the paths passed to the rclone command are as follows.</p>
<h3 id="pathtodir">/path/to/dir</h3>
<p>This refers to the local file system.</p>
<p>On Windows <code>\</code> may be used instead of <code>/</code> in local paths <strong>only</strong>, non local paths must use <code>/</code>. See <a href="https://rclone.org/local/#paths-on-windows">local filesystem</a> documentation for more about Windows-specific paths.</p>
<p>These paths needn't start with a leading <code>/</code> - if they don't then they will be relative to the current directory.</p>
<h3 id="remotepathtodir">remote:path/to/dir</h3>
<p>This refers to a directory <code>path/to/dir</code> on <code>remote:</code> as defined in the config file (configured with <code>rclone config</code>).</p>
<h3 id="remotepathtodir-1">remote:/path/to/dir</h3>
<p>On most backends this is refers to the same directory as <code>remote:path/to/dir</code> and that format should be preferred. On a very small number of remotes (FTP, SFTP, Dropbox for business) this will refer to a different directory. On these, paths without a leading <code>/</code> will refer to your "home" directory and paths with a leading <code>/</code> will refer to the root.</p>
<h3 id="backendpathtodir">:backend:path/to/dir</h3>
<p>This is an advanced form for creating remotes on the fly. <code>backend</code> should be the name or prefix of a backend (the <code>type</code> in the config file) and all the configuration for the backend should be provided on the command line (or in environment variables).</p>
<p>Here are some examples:</p>
<pre><code>rclone lsd --http-url https://pub.rclone.org :http:</code></pre>
<p>To list all the directories in the root of <code>https://pub.rclone.org/</code>.</p>
<pre><code>rclone lsf --http-url https://example.com :http:path/to/dir</code></pre>
<p>To list files and directories in <code>https://example.com/path/to/dir/</code></p>
<pre><code>rclone copy --http-url https://example.com :http:path/to/dir /tmp/dir</code></pre>
<p>To copy files and directories in <code>https://example.com/path/to/dir</code> to <code>/tmp/dir</code>.</p>
<pre><code>rclone copy --sftp-host example.com :sftp:path/to/dir /tmp/dir</code></pre>
<p>To copy files and directories from <code>example.com</code> in the relative directory <code>path/to/dir</code> to <code>/tmp/dir</code> using sftp.</p>
<h3 id="connection-strings">Connection strings</h3>
<p>The above examples can also be written using a connection string syntax, so instead of providing the arguments as command line parameters <code>--http-url https://pub.rclone.org</code> they are provided as part of the remote specification as a kind of connection string.</p>
<pre><code>rclone lsd &quot;:http,url=&#39;https://pub.rclone.org&#39;:&quot;
rclone lsf &quot;:http,url=&#39;https://example.com&#39;:path/to/dir&quot;
rclone copy &quot;:http,url=&#39;https://example.com&#39;:path/to/dir&quot; /tmp/dir
rclone copy :sftp,host=example.com:path/to/dir /tmp/dir</code></pre>
<p>These can apply to modify existing remotes as well as create new remotes with the on the fly syntax. This example is equivalent to adding the <code>--drive-shared-with-me</code> parameter to the remote <code>gdrive:</code>.</p>
<pre><code>rclone lsf &quot;gdrive,shared_with_me:path/to/dir&quot;</code></pre>
<p>The major advantage to using the connection string style syntax is that it only applies to the remote, not to all the remotes of that type of the command line. A common confusion is this attempt to copy a file shared on google drive to the normal drive which <strong>does not work</strong> because the <code>--drive-shared-with-me</code> flag applies to both the source and the destination.</p>
<pre><code>rclone copy --drive-shared-with-me gdrive:shared-file.txt gdrive:</code></pre>
<p>However using the connection string syntax, this does work.</p>
<pre><code>rclone copy &quot;gdrive,shared_with_me:shared-file.txt&quot; gdrive:</code></pre>
<p>Note that the connection string only affects the options of the immediate backend. If for example gdriveCrypt is a crypt based on gdrive, then the following command <strong>will not work</strong> as intended, because <code>shared_with_me</code> is ignored by the crypt backend:</p>
<pre><code>rclone copy &quot;gdriveCrypt,shared_with_me:shared-file.txt&quot; gdriveCrypt:</code></pre>
<p>The connection strings have the following syntax</p>
<pre><code>remote,parameter=value,parameter2=value2:path/to/dir
:backend,parameter=value,parameter2=value2:path/to/dir</code></pre>
<p>If the <code>parameter</code> has a <code>:</code> or <code>,</code> then it must be placed in quotes <code>"</code> or <code>'</code>, so</p>
<pre><code>remote,parameter=&quot;colon:value&quot;,parameter2=&quot;comma,value&quot;:path/to/dir
:backend,parameter=&#39;colon:value&#39;,parameter2=&#39;comma,value&#39;:path/to/dir</code></pre>
<p>If a quoted value needs to include that quote, then it should be doubled, so</p>
<pre><code>remote,parameter=&quot;with&quot;&quot;quote&quot;,parameter2=&#39;with&#39;&#39;quote&#39;:path/to/dir</code></pre>
<p>This will make <code>parameter</code> be <code>with"quote</code> and <code>parameter2</code> be <code>with'quote</code>.</p>
<p>If you leave off the <code>=parameter</code> then rclone will substitute <code>=true</code> which works very well with flags. For example, to use s3 configured in the environment you could use:</p>
<pre><code>rclone lsd :s3,env_auth:</code></pre>
<p>Which is equivalent to</p>
<pre><code>rclone lsd :s3,env_auth=true:</code></pre>
<p>Note that on the command line you might need to surround these connection strings with <code>"</code> or <code>'</code> to stop the shell interpreting any special characters within them.</p>
<p>If you are a shell master then you'll know which strings are OK and which aren't, but if you aren't sure then enclose them in <code>"</code> and use <code>'</code> as the inside quote. This syntax works on all OSes.</p>
<pre><code>rclone copy &quot;:http,url=&#39;https://example.com&#39;:path/to/dir&quot; /tmp/dir</code></pre>
<p>On Linux/macOS some characters are still interpreted inside <code>"</code> strings in the shell (notably <code>\</code> and <code>$</code> and <code>"</code>) so if your strings contain those you can swap the roles of <code>"</code> and <code>'</code> thus. (This syntax does not work on Windows.)</p>
<pre><code>rclone copy &#39;:http,url=&quot;https://example.com&quot;:path/to/dir&#39; /tmp/dir</code></pre>
<h4 id="connection-strings-config-and-logging">Connection strings, config and logging</h4>
<p>If you supply extra configuration to a backend by command line flag, environment variable or connection string then rclone will add a suffix based on the hash of the config to the name of the remote, eg</p>
<pre><code>rclone -vv lsf --s3-chunk-size 20M s3:</code></pre>
<p>Has the log message</p>
<pre><code>DEBUG : s3: detected overridden config - adding &quot;{Srj1p}&quot; suffix to name</code></pre>
<p>This is so rclone can tell the modified remote apart from the unmodified remote when caching the backends.</p>
<p>This should only be noticeable in the logs.</p>
<p>This means that on the fly backends such as</p>
<pre><code>rclone -vv lsf :s3,env_auth:</code></pre>
<p>Will get their own names</p>
<pre><code>DEBUG : :s3: detected overridden config - adding &quot;{YTu53}&quot; suffix to name</code></pre>
<h3 id="valid-remote-names">Valid remote names</h3>
<p>Remote names are case sensitive, and must adhere to the following rules: - May contain number, letter, <code>_</code>, <code>-</code>, <code>.</code>, <code>+</code>, <code>@</code> and space. - May not start with <code>-</code> or space. - May not end with space.</p>
<p>Starting with rclone version 1.61, any Unicode numbers and letters are allowed, while in older versions it was limited to plain ASCII (0-9, A-Z, a-z). If you use the same rclone configuration from different shells, which may be configured with different character encoding, you must be cautious to use characters that are possible to write in all of them. This is mostly a problem on Windows, where the console traditionally uses a non-Unicode character set - defined by the so-called "code page".</p>
<p>Do not use single character names on Windows as it creates ambiguity with Windows drives' names, e.g.: remote called <code>C</code> is indistinguishable from <code>C</code> drive. Rclone will always assume that single letter name refers to a drive.</p>
<h2 id="quoting-and-the-shell">Quoting and the shell</h2>
<p>When you are typing commands to your computer you are using something called the command line shell. This interprets various characters in an OS specific way.</p>
<p>Here are some gotchas which may help users unfamiliar with the shell rules</p>
<h3 id="linux-osx">Linux / OSX</h3>
<p>If your names have spaces or shell metacharacters (e.g. <code>*</code>, <code>?</code>, <code>$</code>, <code>'</code>, <code>"</code>, etc.) then you must quote them. Use single quotes <code>'</code> by default.</p>
<pre><code>rclone copy &#39;Important files?&#39; remote:backup</code></pre>
<p>If you want to send a <code>'</code> you will need to use <code>"</code>, e.g.</p>
<pre><code>rclone copy &quot;O&#39;Reilly Reviews&quot; remote:backup</code></pre>
<p>The rules for quoting metacharacters are complicated and if you want the full details you'll have to consult the manual page for your shell.</p>
<h3 id="windows-1">Windows</h3>
<p>If your names have spaces in you need to put them in <code>"</code>, e.g.</p>
<pre><code>rclone copy &quot;E:\folder name\folder name\folder name&quot; remote:backup</code></pre>
<p>If you are using the root directory on its own then don't quote it (see <a href="https://github.com/rclone/rclone/issues/464">#464</a> for why), e.g.</p>
<pre><code>rclone copy E:\ remote:backup</code></pre>
<h2 id="copying-files-or-directories-with-in-the-names">Copying files or directories with <code>:</code> in the names</h2>
<p>rclone uses <code>:</code> to mark a remote name. This is, however, a valid filename component in non-Windows OSes. The remote name parser will only search for a <code>:</code> up to the first <code>/</code> so if you need to act on a file or directory like this then use the full path starting with a <code>/</code>, or use <code>./</code> as a current directory prefix.</p>
<p>So to sync a directory called <code>sync:me</code> to a remote called <code>remote:</code> use</p>
<pre><code>rclone sync --interactive ./sync:me remote:path</code></pre>
<p>or</p>
<pre><code>rclone sync --interactive /full/path/to/sync:me remote:path</code></pre>
<h2 id="server-side-copy">Server Side Copy</h2>
<p>Most remotes (but not all - see <a href="https://rclone.org/overview/#optional-features">the overview</a>) support server-side copy.</p>
<p>This means if you want to copy one folder to another then rclone won't download all the files and re-upload them; it will instruct the server to copy them in place.</p>
<p>Eg</p>
<pre><code>rclone copy s3:oldbucket s3:newbucket</code></pre>
<p>Will copy the contents of <code>oldbucket</code> to <code>newbucket</code> without downloading and re-uploading.</p>
<p>Remotes which don't support server-side copy <strong>will</strong> download and re-upload in this case.</p>
<p>Server side copies are used with <code>sync</code> and <code>copy</code> and will be identified in the log when using the <code>-v</code> flag. The <code>move</code> command may also use them if remote doesn't support server-side move directly. This is done by issuing a server-side copy then a delete which is much quicker than a download and re-upload.</p>
<p>Server side copies will only be attempted if the remote names are the same.</p>
<p>This can be used when scripting to make aged backups efficiently, e.g.</p>
<pre><code>rclone sync --interactive remote:current-backup remote:previous-backup
rclone sync --interactive /path/to/files remote:current-backup</code></pre>
<h2 id="metadata">Metadata support</h2>
<p>Metadata is data about a file (or directory) which isn't the contents of the file (or directory). Normally rclone only preserves the modification time and the content (MIME) type where possible.</p>
<p>Rclone supports preserving all the available metadata on files and directories when using the <code>--metadata</code> or <code>-M</code> flag.</p>
<p>Exactly what metadata is supported and what that support means depends on the backend. Backends that support metadata have a metadata section in their docs and are listed in the <a href="https://rclone.org/overview/#features">features table</a> (Eg <a href="https://rclone.org/local/#metadata">local</a>, <a href="/s3/#metadata">s3</a>)</p>
<p>Some backends don't support metadata, some only support metadata on files and some support metadata on both files and directories.</p>
<p>Rclone only supports a one-time sync of metadata. This means that metadata will be synced from the source object to the destination object only when the source object has changed and needs to be re-uploaded. If the metadata subsequently changes on the source object without changing the object itself then it won't be synced to the destination object. This is in line with the way rclone syncs <code>Content-Type</code> without the <code>--metadata</code> flag.</p>
<p>Using <code>--metadata</code> when syncing from local to local will preserve file attributes such as file mode, owner, extended attributes (not Windows).</p>
<p>Note that arbitrary metadata may be added to objects using the <code>--metadata-set key=value</code> flag when the object is first uploaded. This flag can be repeated as many times as necessary.</p>
<p>The <a href="#metadata-mapper">--metadata-mapper</a> flag can be used to pass the name of a program in which can transform metadata when it is being copied from source to destination.</p>
<p>Rclone supports <code>--metadata-set</code> and <code>--metadata-mapper</code> when doing sever side <code>Move</code> and server side <code>Copy</code>, but not when doing server side <code>DirMove</code> (renaming a directory) as this would involve recursing into the directory. Note that you can disable <code>DirMove</code> with <code>--disable DirMove</code> and rclone will revert back to using <code>Move</code> for each individual object where <code>--metadata-set</code> and <code>--metadata-mapper</code> are supported.</p>
<h3 id="types-of-metadata">Types of metadata</h3>
<p>Metadata is divided into two type. System metadata and User metadata.</p>
<p>Metadata which the backend uses itself is called system metadata. For example on the local backend the system metadata <code>uid</code> will store the user ID of the file when used on a unix based platform.</p>
<p>Arbitrary metadata is called user metadata and this can be set however is desired.</p>
<p>When objects are copied from backend to backend, they will attempt to interpret system metadata if it is supplied. Metadata may change from being user metadata to system metadata as objects are copied between different backends. For example copying an object from s3 sets the <code>content-type</code> metadata. In a backend which understands this (like <code>azureblob</code>) this will become the Content-Type of the object. In a backend which doesn't understand this (like the <code>local</code> backend) this will become user metadata. However should the local object be copied back to s3, the Content-Type will be set correctly.</p>
<h3 id="metadata-framework">Metadata framework</h3>
<p>Rclone implements a metadata framework which can read metadata from an object and write it to the object when (and only when) it is being uploaded.</p>
<p>This metadata is stored as a dictionary with string keys and string values.</p>
<p>There are some limits on the names of the keys (these may be clarified further in the future).</p>
<ul>
<li>must be lower case</li>
<li>may be <code>a-z</code> <code>0-9</code> containing <code>.</code> <code>-</code> or <code>_</code></li>
<li>length is backend dependent</li>
</ul>
<p>Each backend can provide system metadata that it understands. Some backends can also store arbitrary user metadata.</p>
<p>Where possible the key names are standardized, so, for example, it is possible to copy object metadata from s3 to azureblob for example and metadata will be translated appropriately.</p>
<p>Some backends have limits on the size of the metadata and rclone will give errors on upload if they are exceeded.</p>
<h3 id="metadata-preservation">Metadata preservation</h3>
<p>The goal of the implementation is to</p>
<ol type="1">
<li>Preserve metadata if at all possible</li>
<li>Interpret metadata if at all possible</li>
</ol>
<p>The consequences of 1 is that you can copy an S3 object to a local disk then back to S3 losslessly. Likewise you can copy a local file with file attributes and xattrs from local disk to s3 and back again losslessly.</p>
<p>The consequence of 2 is that you can copy an S3 object with metadata to Azureblob (say) and have the metadata appear on the Azureblob object also.</p>
<h3 id="standard-system-metadata">Standard system metadata</h3>
<p>Here is a table of standard system metadata which, if appropriate, a backend may implement.</p>
<table>
<colgroup>
<col style="width: 48%" />
<col style="width: 30%" />
<col style="width: 20%" />
</colgroup>
<thead>
<tr class="header">
<th>key</th>
<th>description</th>
<th>example</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td>mode</td>
<td>File type and mode: octal, unix style</td>
<td>0100664</td>
</tr>
<tr class="even">
<td>uid</td>
<td>User ID of owner: decimal number</td>
<td>500</td>
</tr>
<tr class="odd">
<td>gid</td>
<td>Group ID of owner: decimal number</td>
<td>500</td>
</tr>
<tr class="even">
<td>rdev</td>
<td>Device ID (if special file) =&gt; hexadecimal</td>
<td>0</td>
</tr>
<tr class="odd">
<td>atime</td>
<td>Time of last access: RFC 3339</td>
<td>2006-01-02T15:04:05.999999999Z07:00</td>
</tr>
<tr class="even">
<td>mtime</td>
<td>Time of last modification: RFC 3339</td>
<td>2006-01-02T15:04:05.999999999Z07:00</td>
</tr>
<tr class="odd">
<td>btime</td>
<td>Time of file creation (birth): RFC 3339</td>
<td>2006-01-02T15:04:05.999999999Z07:00</td>
</tr>
<tr class="even">
<td>utime</td>
<td>Time of file upload: RFC 3339</td>
<td>2006-01-02T15:04:05.999999999Z07:00</td>
</tr>
<tr class="odd">
<td>cache-control</td>
<td>Cache-Control header</td>
<td>no-cache</td>
</tr>
<tr class="even">
<td>content-disposition</td>
<td>Content-Disposition header</td>
<td>inline</td>
</tr>
<tr class="odd">
<td>content-encoding</td>
<td>Content-Encoding header</td>
<td>gzip</td>
</tr>
<tr class="even">
<td>content-language</td>
<td>Content-Language header</td>
<td>en-US</td>
</tr>
<tr class="odd">
<td>content-type</td>
<td>Content-Type header</td>
<td>text/plain</td>
</tr>
</tbody>
</table>
<p>The metadata keys <code>mtime</code> and <code>content-type</code> will take precedence if supplied in the metadata over reading the <code>Content-Type</code> or modification time of the source object.</p>
<p>Hashes are not included in system metadata as there is a well defined way of reading those already.</p>
<h2 id="options-90">Options</h2>
<p>Rclone has a number of options to control its behaviour.</p>
<p>Options that take parameters can have the values passed in two ways, <code>--option=value</code> or <code>--option value</code>. However boolean (true/false) options behave slightly differently to the other options in that <code>--boolean</code> sets the option to <code>true</code> and the absence of the flag sets it to <code>false</code>. It is also possible to specify <code>--boolean=false</code> or <code>--boolean=true</code>. Note that <code>--boolean false</code> is not valid - this is parsed as <code>--boolean</code> and the <code>false</code> is parsed as an extra command line argument for rclone.</p>
<h3 id="time-option">Time or duration options</h3>
<p>TIME or DURATION options can be specified as a duration string or a time string.</p>
<p>A duration string is a possibly signed sequence of decimal numbers, each with optional fraction and a unit suffix, such as "300ms", "-1.5h" or "2h45m". Default units are seconds or the following abbreviations are valid:</p>
<ul>
<li><code>ms</code> - Milliseconds</li>
<li><code>s</code> - Seconds</li>
<li><code>m</code> - Minutes</li>
<li><code>h</code> - Hours</li>
<li><code>d</code> - Days</li>
<li><code>w</code> - Weeks</li>
<li><code>M</code> - Months</li>
<li><code>y</code> - Years</li>
</ul>
<p>These can also be specified as an absolute time in the following formats:</p>
<ul>
<li>RFC3339 - e.g. <code>2006-01-02T15:04:05Z</code> or <code>2006-01-02T15:04:05+07:00</code></li>
<li>ISO8601 Date and time, local timezone - <code>2006-01-02T15:04:05</code></li>
<li>ISO8601 Date and time, local timezone - <code>2006-01-02 15:04:05</code></li>
<li>ISO8601 Date - <code>2006-01-02</code> (YYYY-MM-DD)</li>
</ul>
<h3 id="size-option">Size options</h3>
<p>Options which use SIZE use KiB (multiples of 1024 bytes) by default. However, a suffix of <code>B</code> for Byte, <code>K</code> for KiB, <code>M</code> for MiB, <code>G</code> for GiB, <code>T</code> for TiB and <code>P</code> for PiB may be used. These are the binary units, e.g. 1, 2**10, 2**20, 2**30 respectively.</p>
<h3 id="backup-dirdir">--backup-dir=DIR</h3>
<p>When using <code>sync</code>, <code>copy</code> or <code>move</code> any files which would have been overwritten or deleted are moved in their original hierarchy into this directory.</p>
<p>If <code>--suffix</code> is set, then the moved files will have the suffix added to them. If there is a file with the same path (after the suffix has been added) in DIR, then it will be overwritten.</p>
<p>The remote in use must support server-side move or copy and you must use the same remote as the destination of the sync. The backup directory must not overlap the destination directory without it being excluded by a filter rule.</p>
<p>For example</p>
<pre><code>rclone sync --interactive /path/to/local remote:current --backup-dir remote:old</code></pre>
<p>will sync <code>/path/to/local</code> to <code>remote:current</code>, but for any files which would have been updated or deleted will be stored in <code>remote:old</code>.</p>
<p>If running rclone from a script you might want to use today's date as the directory name passed to <code>--backup-dir</code> to store the old files, or you might want to pass <code>--suffix</code> with today's date.</p>
<p>See <code>--compare-dest</code> and <code>--copy-dest</code>.</p>
<h3 id="bind-string">--bind string</h3>
<p>Local address to bind to for outgoing connections. This can be an IPv4 address (1.2.3.4), an IPv6 address (1234::789A) or host name. If the host name doesn't resolve or resolves to more than one IP address it will give an error.</p>
<p>You can use <code>--bind 0.0.0.0</code> to force rclone to use IPv4 addresses and <code>--bind ::0</code> to force rclone to use IPv6 addresses.</p>
<h3 id="bwlimitbandwidth_spec">--bwlimit=BANDWIDTH_SPEC</h3>
<p>This option controls the bandwidth limit. For example</p>
<pre><code>--bwlimit 10M</code></pre>
<p>would mean limit the upload and download bandwidth to 10 MiB/s. <strong>NB</strong> this is <strong>bytes</strong> per second not <strong>bits</strong> per second. To use a single limit, specify the desired bandwidth in KiB/s, or use a suffix B|K|M|G|T|P. The default is <code>0</code> which means to not limit bandwidth.</p>
<p>The upload and download bandwidth can be specified separately, as <code>--bwlimit UP:DOWN</code>, so</p>
<pre><code>--bwlimit 10M:100k</code></pre>
<p>would mean limit the upload bandwidth to 10 MiB/s and the download bandwidth to 100 KiB/s. Either limit can be "off" meaning no limit, so to just limit the upload bandwidth you would use</p>
<pre><code>--bwlimit 10M:off</code></pre>
<p>this would limit the upload bandwidth to 10 MiB/s but the download bandwidth would be unlimited.</p>
<p>When specified as above the bandwidth limits last for the duration of run of the rclone binary.</p>
<p>It is also possible to specify a "timetable" of limits, which will cause certain limits to be applied at certain times. To specify a timetable, format your entries as <code>WEEKDAY-HH:MM,BANDWIDTH WEEKDAY-HH:MM,BANDWIDTH...</code> where: <code>WEEKDAY</code> is optional element.</p>
<ul>
<li><code>BANDWIDTH</code> can be a single number, e.g.<code>100k</code> or a pair of numbers for upload:download, e.g.<code>10M:1M</code>.</li>
<li><code>WEEKDAY</code> can be written as the whole word or only using the first 3 characters. It is optional.</li>
<li><code>HH:MM</code> is an hour from 00:00 to 23:59.</li>
</ul>
<p>Entries can be separated by spaces or semicolons.</p>
<p><strong>Note:</strong> Semicolons can be used as separators instead of spaces to avoid parsing issues in environments like Docker.</p>
<p>An example of a typical timetable to avoid link saturation during daytime working hours could be:</p>
<p>Using spaces as separators: <code>--bwlimit "08:00,512k 12:00,10M 13:00,512k 18:00,30M 23:00,off"</code></p>
<p>Using semicolons as separators: <code>--bwlimit "08:00,512k;12:00,10M;13:00,512k;18:00,30M;23:00,off"</code></p>
<p>In these examples, the transfer bandwidth will be set to 512 KiB/s at 8am every day. At noon, it will rise to 10 MiB/s, and drop back to 512 KiB/sec at 1pm. At 6pm, the bandwidth limit will be set to 30 MiB/s, and at 11pm it will be completely disabled (full speed). Anything between 11pm and 8am will remain unlimited.</p>
<p>An example of timetable with <code>WEEKDAY</code> could be:</p>
<p>Using spaces as separators: <code>--bwlimit "Mon-00:00,512 Fri-23:59,10M Sat-10:00,1M Sun-20:00,off"</code></p>
<p>Using semicolons as separators: <code>--bwlimit "Mon-00:00,512;Fri-23:59,10M;Sat-10:00,1M;Sun-20:00,off"</code></p>
<p>It means that, the transfer bandwidth will be set to 512 KiB/s on Monday. It will rise to 10 MiB/s before the end of Friday. At 10:00 on Saturday it will be set to 1 MiB/s. From 20:00 on Sunday it will be unlimited.</p>
<p>Timeslots without <code>WEEKDAY</code> are extended to the whole week. So this example:</p>
<p><code>--bwlimit "Mon-00:00,512 12:00,1M Sun-20:00,off"</code></p>
<p>Is equivalent to this:</p>
<p><code>--bwlimit "Mon-00:00,512Mon-12:00,1M Tue-12:00,1M Wed-12:00,1M Thu-12:00,1M Fri-12:00,1M Sat-12:00,1M Sun-12:00,1M Sun-20:00,off"</code></p>
<p>Bandwidth limit apply to the data transfer for all backends. For most backends the directory listing bandwidth is also included (exceptions being the non HTTP backends, <code>ftp</code>, <code>sftp</code> and <code>storj</code>).</p>
<p>Note that the units are <strong>Byte/s</strong>, not <strong>bit/s</strong>. Typically connections are measured in bit/s - to convert divide by 8. For example, let's say you have a 10 Mbit/s connection and you wish rclone to use half of it - 5 Mbit/s. This is 5/8 = 0.625 MiB/s so you would use a <code>--bwlimit 0.625M</code> parameter for rclone.</p>
<p>On Unix systems (Linux, macOS, …) the bandwidth limiter can be toggled by sending a <code>SIGUSR2</code> signal to rclone. This allows to remove the limitations of a long running rclone transfer and to restore it back to the value specified with <code>--bwlimit</code> quickly when needed. Assuming there is only one rclone instance running, you can toggle the limiter like this:</p>
<pre><code>kill -SIGUSR2 $(pidof rclone)</code></pre>
<p>If you configure rclone with a <a href="/rc">remote control</a> then you can use change the bwlimit dynamically:</p>
<pre><code>rclone rc core/bwlimit rate=1M</code></pre>
<h3 id="bwlimit-filebandwidth_spec">--bwlimit-file=BANDWIDTH_SPEC</h3>
<p>This option controls per file bandwidth limit. For the options see the <code>--bwlimit</code> flag.</p>
<p>For example use this to allow no transfers to be faster than 1 MiB/s</p>
<pre><code>--bwlimit-file 1M</code></pre>
<p>This can be used in conjunction with <code>--bwlimit</code>.</p>
<p>Note that if a schedule is provided the file will use the schedule in effect at the start of the transfer.</p>
<h3 id="buffer-sizesize">--buffer-size=SIZE</h3>
<p>Use this sized buffer to speed up file transfers. Each <code>--transfer</code> will use this much memory for buffering.</p>
<p>When using <code>mount</code> or <code>cmount</code> each open file descriptor will use this much memory for buffering. See the <a href="https://rclone.org/commands/rclone_mount/#file-buffering">mount</a> documentation for more details.</p>
<p>Set to <code>0</code> to disable the buffering for the minimum memory usage.</p>
<p>Note that the memory allocation of the buffers is influenced by the <a href="#use-mmap">--use-mmap</a> flag.</p>
<h3 id="cache-dirdir">--cache-dir=DIR</h3>
<p>Specify the directory rclone will use for caching, to override the default.</p>
<p>Default value is depending on operating system: - Windows <code>%LocalAppData%\rclone</code>, if <code>LocalAppData</code> is defined. - macOS <code>$HOME/Library/Caches/rclone</code> if <code>HOME</code> is defined. - Unix <code>$XDG_CACHE_HOME/rclone</code> if <code>XDG_CACHE_HOME</code> is defined, else <code>$HOME/.cache/rclone</code> if <code>HOME</code> is defined. - Fallback (on all OS) to <code>$TMPDIR/rclone</code>, where <code>TMPDIR</code> is the value from <a href="#temp-dir-dir">--temp-dir</a>.</p>
<p>You can use the <a href="https://rclone.org/commands/rclone_config_paths/">config paths</a> command to see the current value.</p>
<p>Cache directory is heavily used by the <a href="https://rclone.org/commands/rclone_mount/#vfs-file-caching">VFS File Caching</a> mount feature, but also by <a href="https://rclone.org/commands/rclone_serve/">serve</a>, <a href="/gui">GUI</a> and other parts of rclone.</p>
<h3 id="check-first">--check-first</h3>
<p>If this flag is set then in a <code>sync</code>, <code>copy</code> or <code>move</code>, rclone will do all the checks to see whether files need to be transferred before doing any of the transfers. Normally rclone would start running transfers as soon as possible.</p>
<p>This flag can be useful on IO limited systems where transfers interfere with checking.</p>
<p>It can also be useful to ensure perfect ordering when using <code>--order-by</code>.</p>
<p>If both <code>--check-first</code> and <code>--order-by</code> are set when doing <code>rclone move</code> then rclone will use the transfer thread to delete source files which don't need transferring. This will enable perfect ordering of the transfers and deletes but will cause the transfer stats to have more items in than expected.</p>
<p>Using this flag can use more memory as it effectively sets <code>--max-backlog</code> to infinite. This means that all the info on the objects to transfer is held in memory before the transfers start.</p>
<h3 id="checkersn">--checkers=N</h3>
<p>Originally controlling just the number of file checkers to run in parallel, e.g. by <code>rclone copy</code>. Now a fairly universal parallelism control used by <code>rclone</code> in several places.</p>
<p>Note: checkers do the equality checking of files during a sync. For some storage systems (e.g. S3, Swift, Dropbox) this can take a significant amount of time so they are run in parallel.</p>
<p>The default is to run 8 checkers in parallel. However, in case of slow-reacting backends you may need to lower (rather than increase) this default by setting <code>--checkers</code> to 4 or less threads. This is especially advised if you are experiencing backend server crashes during file checking phase (e.g. on subsequent or top-up backups where little or no file copying is done and checking takes up most of the time). Increase this setting only with utmost care, while monitoring your server health and file checking throughput.</p>
<h3 id="c---checksum">-c, --checksum</h3>
<p>Normally rclone will look at modification time and size of files to see if they are equal. If you set this flag then rclone will check the file hash and size to determine if files are equal.</p>
<p>This is useful when the remote doesn't support setting modified time and a more accurate sync is desired than just checking the file size.</p>
<p>This is very useful when transferring between remotes which store the same hash type on the object, e.g. Drive and Swift. For details of which remotes support which hash type see the table in the <a href="https://rclone.org/overview/">overview section</a>.</p>
<p>Eg <code>rclone --checksum sync s3:/bucket swift:/bucket</code> would run much quicker than without the <code>--checksum</code> flag.</p>
<p>When using this flag, rclone won't update mtimes of remote files if they are incorrect as it would normally.</p>
<h3 id="color-when">--color WHEN</h3>
<p>Specify when colors (and other ANSI codes) should be added to the output.</p>
<p><code>AUTO</code> (default) only allows ANSI codes when the output is a terminal</p>
<p><code>NEVER</code> never allow ANSI codes</p>
<p><code>ALWAYS</code> always add ANSI codes, regardless of the output format (terminal or file)</p>
<h3 id="compare-destdir">--compare-dest=DIR</h3>
<p>When using <code>sync</code>, <code>copy</code> or <code>move</code> DIR is checked in addition to the destination for files. If a file identical to the source is found that file is NOT copied from source. This is useful to copy just files that have changed since the last backup.</p>
<p>You must use the same remote as the destination of the sync. The compare directory must not overlap the destination directory.</p>
<p>See <code>--copy-dest</code> and <code>--backup-dir</code>.</p>
<h3 id="configconfig_file">--config=CONFIG_FILE</h3>
<p>Specify the location of the rclone configuration file, to override the default. E.g. <code>rclone config --config="rclone.conf"</code>.</p>
<p>The exact default is a bit complex to describe, due to changes introduced through different versions of rclone while preserving backwards compatibility, but in most cases it is as simple as:</p>
<ul>
<li><code>%APPDATA%/rclone/rclone.conf</code> on Windows</li>
<li><code>~/.config/rclone/rclone.conf</code> on other</li>
</ul>
<p>The complete logic is as follows: Rclone will look for an existing configuration file in any of the following locations, in priority order:</p>
<ol type="1">
<li><code>rclone.conf</code> (in program directory, where rclone executable is)</li>
<li><code>%APPDATA%/rclone/rclone.conf</code> (only on Windows)</li>
<li><code>$XDG_CONFIG_HOME/rclone/rclone.conf</code> (on all systems, including Windows)</li>
<li><code>~/.config/rclone/rclone.conf</code> (see below for explanation of ~ symbol)</li>
<li><code>~/.rclone.conf</code></li>
</ol>
<p>If no existing configuration file is found, then a new one will be created in the following location:</p>
<ul>
<li>On Windows: Location 2 listed above, except in the unlikely event that <code>APPDATA</code> is not defined, then location 4 is used instead.</li>
<li>On Unix: Location 3 if <code>XDG_CONFIG_HOME</code> is defined, else location 4.</li>
<li>Fallback to location 5 (on all OS), when the rclone directory cannot be created, but if also a home directory was not found then path <code>.rclone.conf</code> relative to current working directory will be used as a final resort.</li>
</ul>
<p>The <code>~</code> symbol in paths above represent the home directory of the current user on any OS, and the value is defined as following:</p>
<ul>
<li>On Windows: <code>%HOME%</code> if defined, else <code>%USERPROFILE%</code>, or else <code>%HOMEDRIVE%\%HOMEPATH%</code>.</li>
<li>On Unix: <code>$HOME</code> if defined, else by looking up current user in OS-specific user database (e.g. passwd file), or else use the result from shell command <code>cd &amp;&amp; pwd</code>.</li>
</ul>
<p>If you run <code>rclone config file</code> you will see where the default location is for you.</p>
<p>The fact that an existing file <code>rclone.conf</code> in the same directory as the rclone executable is always preferred, means that it is easy to run in "portable" mode by downloading rclone executable to a writable directory and then create an empty file <code>rclone.conf</code> in the same directory.</p>
<p>If the location is set to empty string <code>""</code> or path to a file with name <code>notfound</code>, or the os null device represented by value <code>NUL</code> on Windows and <code>/dev/null</code> on Unix systems, then rclone will keep the config file in memory only.</p>
<p>The file format is basic <a href="https://en.wikipedia.org/wiki/INI_file#Format">INI</a>: Sections of text, led by a <code>[section]</code> header and followed by <code>key=value</code> entries on separate lines. In rclone each remote is represented by its own section, where the section name defines the name of the remote. Options are specified as the <code>key=value</code> entries, where the key is the option name without the <code>--backend-</code> prefix, in lowercase and with <code>_</code> instead of <code>-</code>. E.g. option <code>--mega-hard-delete</code> corresponds to key <code>hard_delete</code>. Only backend options can be specified. A special, and required, key <code>type</code> identifies the <a href="https://rclone.org/overview/">storage system</a>, where the value is the internal lowercase name as returned by command <code>rclone help backends</code>. Comments are indicated by <code>;</code> or <code>#</code> at the beginning of a line.</p>
<p>Example:</p>
<pre><code>[megaremote]
type = mega
user = you@example.com
pass = PDPcQVVjVtzFY-GTdDFozqBhTdsPg3qH</code></pre>
<p>Note that passwords are in <a href="https://rclone.org/commands/rclone_obscure/">obscured</a> form. Also, many storage systems uses token-based authentication instead of passwords, and this requires additional steps. It is easier, and safer, to use the interactive command <code>rclone config</code> instead of manually editing the configuration file.</p>
<p>The configuration file will typically contain login information, and should therefore have restricted permissions so that only the current user can read it. Rclone tries to ensure this when it writes the file. You may also choose to <a href="#configuration-encryption">encrypt</a> the file.</p>
<p>When token-based authentication are used, the configuration file must be writable, because rclone needs to update the tokens inside it.</p>
<p>To reduce risk of corrupting an existing configuration file, rclone will not write directly to it when saving changes. Instead it will first write to a new, temporary, file. If a configuration file already existed, it will (on Unix systems) try to mirror its permissions to the new file. Then it will rename the existing file to a temporary name as backup. Next, rclone will rename the new file to the correct name, before finally cleaning up by deleting the backup file.</p>
<p>If the configuration file path used by rclone is a symbolic link, then this will be evaluated and rclone will write to the resolved path, instead of overwriting the symbolic link. Temporary files used in the process (described above) will be written to the same parent directory as that of the resolved configuration file, but if this directory is also a symbolic link it will not be resolved and the temporary files will be written to the location of the directory symbolic link.</p>
<h3 id="contimeouttime">--contimeout=TIME</h3>
<p>Set the connection timeout. This should be in go time format which looks like <code>5s</code> for 5 seconds, <code>10m</code> for 10 minutes, or <code>3h30m</code>.</p>
<p>The connection timeout is the amount of time rclone will wait for a connection to go through to a remote object storage system. It is <code>1m</code> by default.</p>
<h3 id="copy-destdir">--copy-dest=DIR</h3>
<p>When using <code>sync</code>, <code>copy</code> or <code>move</code> DIR is checked in addition to the destination for files. If a file identical to the source is found that file is server-side copied from DIR to the destination. This is useful for incremental backup.</p>
<p>The remote in use must support server-side copy and you must use the same remote as the destination of the sync. The compare directory must not overlap the destination directory.</p>
<p>See <code>--compare-dest</code> and <code>--backup-dir</code>.</p>
<h3 id="dedupe-mode-mode">--dedupe-mode MODE</h3>
<p>Mode to run dedupe command in. One of <code>interactive</code>, <code>skip</code>, <code>first</code>, <code>newest</code>, <code>oldest</code>, <code>rename</code>. The default is <code>interactive</code>.<br />
See the dedupe command for more information as to what these options mean.</p>
<h3 id="default-time-time">--default-time TIME</h3>
<p>If a file or directory does have a modification time rclone can read then rclone will display this fixed time instead.</p>
<p>The default is <code>2000-01-01 00:00:00 UTC</code>. This can be configured in any of the ways shown in <a href="#time-option">the time or duration options</a>.</p>
<p>For example <code>--default-time 2020-06-01</code> to set the default time to the 1st of June 2020 or <code>--default-time 0s</code> to set the default time to the time rclone started up.</p>
<h3 id="disable-featurefeature...">--disable FEATURE,FEATURE,...</h3>
<p>This disables a comma separated list of optional features. For example to disable server-side move and server-side copy use:</p>
<pre><code>--disable move,copy</code></pre>
<p>The features can be put in any case.</p>
<p>To see a list of which features can be disabled use:</p>
<pre><code>--disable help</code></pre>
<p>The features a remote has can be seen in JSON format with:</p>
<pre><code>rclone backend features remote:</code></pre>
<p>See the overview <a href="https://rclone.org/overview/#features">features</a> and <a href="https://rclone.org/overview/#optional-features">optional features</a> to get an idea of which feature does what.</p>
<p>Note that some features can be set to <code>true</code> if they are <code>true</code>/<code>false</code> feature flag features by prefixing them with <code>!</code>. For example the <code>CaseInsensitive</code> feature can be forced to <code>false</code> with <code>--disable CaseInsensitive</code> and forced to <code>true</code> with <code>--disable '!CaseInsensitive'</code>. In general it isn't a good idea doing this but it may be useful in extremis.</p>
<p>(Note that <code>!</code> is a shell command which you will need to escape with single quotes or a backslash on unix like platforms.)</p>
<p>This flag can be useful for debugging and in exceptional circumstances (e.g. Google Drive limiting the total volume of Server Side Copies to 100 GiB/day).</p>
<h3 id="disable-http2">--disable-http2</h3>
<p>This stops rclone from trying to use HTTP/2 if available. This can sometimes speed up transfers due to a <a href="https://github.com/golang/go/issues/37373">problem in the Go standard library</a>.</p>
<h3 id="dscp-value">--dscp VALUE</h3>
<p>Specify a DSCP value or name to use in connections. This could help QoS system to identify traffic class. BE, EF, DF, LE, CSx and AFxx are allowed.</p>
<p>See the description of <a href="https://en.wikipedia.org/wiki/Differentiated_services">differentiated services</a> to get an idea of this field. Setting this to 1 (LE) to identify the flow to SCAVENGER class can avoid occupying too much bandwidth in a network with DiffServ support (<a href="https://tools.ietf.org/html/rfc8622">RFC 8622</a>).</p>
<p>For example, if you configured QoS on router to handle LE properly. Running:</p>
<pre><code>rclone copy --dscp LE from:/from to:/to</code></pre>
<p>would make the priority lower than usual internet flows.</p>
<p>This option has no effect on Windows (see <a href="https://github.com/golang/go/issues/42728">golang/go#42728</a>).</p>
<h3 id="n---dry-run">-n, --dry-run</h3>
<p>Do a trial run with no permanent changes. Use this to see what rclone would do without actually doing it. Useful when setting up the <code>sync</code> command which deletes files in the destination.</p>
<h3 id="expect-continue-timeouttime">--expect-continue-timeout=TIME</h3>
<p>This specifies the amount of time to wait for a server's first response headers after fully writing the request headers if the request has an "Expect: 100-continue" header. Not all backends support using this.</p>
<p>Zero means no timeout and causes the body to be sent immediately, without waiting for the server to approve. This time does not include the time to send the request header.</p>
<p>The default is <code>1s</code>. Set to <code>0</code> to disable.</p>
<h3 id="error-on-no-transfer">--error-on-no-transfer</h3>
<p>By default, rclone will exit with return code 0 if there were no errors.</p>
<p>This option allows rclone to return exit code 9 if no files were transferred between the source and destination. This allows using rclone in scripts, and triggering follow-on actions if data was copied, or skipping if not.</p>
<p>NB: Enabling this option turns a usually non-fatal error into a potentially fatal one - please check and adjust your scripts accordingly!</p>
<h3 id="fix-case">--fix-case</h3>
<p>Normally, a sync to a case insensitive dest (such as macOS / Windows) will not result in a matching filename if the source and dest filenames have casing differences but are otherwise identical. For example, syncing <code>hello.txt</code> to <code>HELLO.txt</code> will normally result in the dest filename remaining <code>HELLO.txt</code>. If <code>--fix-case</code> is set, then <code>HELLO.txt</code> will be renamed to <code>hello.txt</code> to match the source.</p>
<p>NB: - directory names with incorrect casing will also be fixed - <code>--fix-case</code> will be ignored if <code>--immutable</code> is set - using <code>--local-case-sensitive</code> instead is not advisable; it will cause <code>HELLO.txt</code> to get deleted! - the old dest filename must not be excluded by filters. Be especially careful with <a href="https://rclone.org/filtering/#files-from-read-list-of-source-file-names"><code>--files-from</code></a>, which does not respect <a href="https://rclone.org/filtering/#ignore-case-make-searches-case-insensitive"><code>--ignore-case</code></a>! - on remotes that do not support server-side move, <code>--fix-case</code> will require downloading the file and re-uploading it. To avoid this, do not use <code>--fix-case</code>.</p>
<h3 id="fs-cache-expire-durationtime">--fs-cache-expire-duration=TIME</h3>
<p>When using rclone via the API rclone caches created remotes for 5 minutes by default in the "fs cache". This means that if you do repeated actions on the same remote then rclone won't have to build it again from scratch, which makes it more efficient.</p>
<p>This flag sets the time that the remotes are cached for. If you set it to <code>0</code> (or negative) then rclone won't cache the remotes at all.</p>
<p>Note that if you use some flags, eg <code>--backup-dir</code> and if this is set to <code>0</code> rclone may build two remotes (one for the source or destination and one for the <code>--backup-dir</code> where it may have only built one before.</p>
<h3 id="fs-cache-expire-intervaltime">--fs-cache-expire-interval=TIME</h3>
<p>This controls how often rclone checks for cached remotes to expire. See the <code>--fs-cache-expire-duration</code> documentation above for more info. The default is 60s, set to 0 to disable expiry.</p>
<h3 id="header">--header</h3>
<p>Add an HTTP header for all transactions. The flag can be repeated to add multiple headers.</p>
<p>If you want to add headers only for uploads use <code>--header-upload</code> and if you want to add headers only for downloads use <code>--header-download</code>.</p>
<p>This flag is supported for all HTTP based backends even those not supported by <code>--header-upload</code> and <code>--header-download</code> so may be used as a workaround for those with care.</p>
<pre><code>rclone ls remote:test --header &quot;X-Rclone: Foo&quot; --header &quot;X-LetMeIn: Yes&quot;</code></pre>
<h3 id="header-download">--header-download</h3>
<p>Add an HTTP header for all download transactions. The flag can be repeated to add multiple headers.</p>
<pre><code>rclone sync --interactive s3:test/src ~/dst --header-download &quot;X-Amz-Meta-Test: Foo&quot; --header-download &quot;X-Amz-Meta-Test2: Bar&quot;</code></pre>
<p>See the GitHub issue <a href="https://github.com/rclone/rclone/issues/59">here</a> for currently supported backends.</p>
<h3 id="header-upload">--header-upload</h3>
<p>Add an HTTP header for all upload transactions. The flag can be repeated to add multiple headers.</p>
<pre><code>rclone sync --interactive ~/src s3:test/dst --header-upload &quot;Content-Disposition: attachment; filename=&#39;cool.html&#39;&quot; --header-upload &quot;X-Amz-Meta-Test: FooBar&quot;</code></pre>
<p>See the GitHub issue <a href="https://github.com/rclone/rclone/issues/59">here</a> for currently supported backends.</p>
<h3 id="human-readable">--human-readable</h3>
<p>Rclone commands output values for sizes (e.g. number of bytes) and counts (e.g. number of files) either as <em>raw</em> numbers, or in <em>human-readable</em> format.</p>
<p>In human-readable format the values are scaled to larger units, indicated with a suffix shown after the value, and rounded to three decimals. Rclone consistently uses binary units (powers of 2) for sizes and decimal units (powers of 10) for counts. The unit prefix for size is according to IEC standard notation, e.g. <code>Ki</code> for kibi. Used with byte unit, <code>1 KiB</code> means 1024 Byte. In list type of output, only the unit prefix appended to the value (e.g. <code>9.762Ki</code>), while in more textual output the full unit is shown (e.g. <code>9.762 KiB</code>). For counts the SI standard notation is used, e.g. prefix <code>k</code> for kilo. Used with file counts, <code>1k</code> means 1000 files.</p>
<p>The various <a href="https://rclone.org/commands/rclone_ls/">list</a> commands output raw numbers by default. Option <code>--human-readable</code> will make them output values in human-readable format instead (with the short unit prefix).</p>
<p>The <a href="https://rclone.org/commands/rclone_about/">about</a> command outputs human-readable by default, with a command-specific option <code>--full</code> to output the raw numbers instead.</p>
<p>Command <a href="https://rclone.org/commands/rclone_size/">size</a> outputs both human-readable and raw numbers in the same output.</p>
<p>The <a href="https://rclone.org/commands/rclone_tree/">tree</a> command also considers <code>--human-readable</code>, but it will not use the exact same notation as the other commands: It rounds to one decimal, and uses single letter suffix, e.g. <code>K</code> instead of <code>Ki</code>. The reason for this is that it relies on an external library.</p>
<p>The interactive command <a href="https://rclone.org/commands/rclone_ncdu/">ncdu</a> shows human-readable by default, and responds to key <code>u</code> for toggling human-readable format.</p>
<h3 id="ignore-case-sync">--ignore-case-sync</h3>
<p>Using this option will cause rclone to ignore the case of the files when synchronizing so files will not be copied/synced when the existing filenames are the same, even if the casing is different.</p>
<h3 id="ignore-checksum">--ignore-checksum</h3>
<p>Normally rclone will check that the checksums of transferred files match, and give an error "corrupted on transfer" if they don't.</p>
<p>You can use this option to skip that check. You should only use it if you have had the "corrupted on transfer" error message and you are sure you might want to transfer potentially corrupted data.</p>
<h3 id="ignore-existing">--ignore-existing</h3>
<p>Using this option will make rclone unconditionally skip all files that exist on the destination, no matter the content of these files.</p>
<p>While this isn't a generally recommended option, it can be useful in cases where your files change due to encryption. However, it cannot correct partial transfers in case a transfer was interrupted.</p>
<p>When performing a <code>move</code>/<code>moveto</code> command, this flag will leave skipped files in the source location unchanged when a file with the same name exists on the destination.</p>
<h3 id="ignore-size">--ignore-size</h3>
<p>Normally rclone will look at modification time and size of files to see if they are equal. If you set this flag then rclone will check only the modification time. If <code>--checksum</code> is set then it only checks the checksum.</p>
<p>It will also cause rclone to skip verifying the sizes are the same after transfer.</p>
<p>This can be useful for transferring files to and from OneDrive which occasionally misreports the size of image files (see <a href="https://github.com/rclone/rclone/issues/399">#399</a> for more info).</p>
<h3 id="i---ignore-times">-I, --ignore-times</h3>
<p>Using this option will cause rclone to unconditionally upload all files regardless of the state of files on the destination.</p>
<p>Normally rclone would skip any files that have the same modification time and are the same size (or have the same checksum if using <code>--checksum</code>).</p>
<h3 id="immutable">--immutable</h3>
<p>Treat source and destination files as immutable and disallow modification.</p>
<p>With this option set, files will be created and deleted as requested, but existing files will never be updated. If an existing file does not match between the source and destination, rclone will give the error <code>Source and destination exist but do not match: immutable file modified</code>.</p>
<p>Note that only commands which transfer files (e.g. <code>sync</code>, <code>copy</code>, <code>move</code>) are affected by this behavior, and only modification is disallowed. Files may still be deleted explicitly (e.g. <code>delete</code>, <code>purge</code>) or implicitly (e.g. <code>sync</code>, <code>move</code>). Use <code>copy --immutable</code> if it is desired to avoid deletion as well as modification.</p>
<p>This can be useful as an additional layer of protection for immutable or append-only data sets (notably backup archives), where modification implies corruption and should not be propagated.</p>
<h3 id="inplace">--inplace</h3>
<p>The <code>--inplace</code> flag changes the behaviour of rclone when uploading files to some backends (backends with the <code>PartialUploads</code> feature flag set) such as:</p>
<ul>
<li>local</li>
<li>ftp</li>
<li>sftp</li>
<li>pcloud</li>
</ul>
<p>Without <code>--inplace</code> (the default) rclone will first upload to a temporary file with an extension like this, where <code>XXXXXX</code> represents a hash of the source file's fingerprint and <code>.partial</code> is <a href="#partial-suffix">--partial-suffix</a> value (<code>.partial</code> by default).</p>
<pre><code>original-file-name.XXXXXX.partial</code></pre>
<p>(rclone will make sure the final name is no longer than 100 characters by truncating the <code>original-file-name</code> part if necessary).</p>
<p>When the upload is complete, rclone will rename the <code>.partial</code> file to the correct name, overwriting any existing file at that point. If the upload fails then the <code>.partial</code> file will be deleted.</p>
<p>This prevents other users of the backend from seeing partially uploaded files in their new names and prevents overwriting the old file until the new one is completely uploaded.</p>
<p>If the <code>--inplace</code> flag is supplied, rclone will upload directly to the final name without creating a <code>.partial</code> file.</p>
<p>This means that an incomplete file will be visible in the directory listings while the upload is in progress and any existing files will be overwritten as soon as the upload starts. If the transfer fails then the file will be deleted. This can cause data loss of the existing file if the transfer fails.</p>
<p>Note that on the local file system if you don't use <code>--inplace</code> hard links (Unix only) will be broken. And if you do use <code>--inplace</code> you won't be able to update in use executables.</p>
<p>Note also that versions of rclone prior to v1.63.0 behave as if the <code>--inplace</code> flag is always supplied.</p>
<h3 id="interactive">-i, --interactive</h3>
<p>This flag can be used to tell rclone that you wish a manual confirmation before destructive operations.</p>
<p>It is <strong>recommended</strong> that you use this flag while learning rclone especially with <code>rclone sync</code>.</p>
<p>For example</p>
<pre><code>$ rclone delete --interactive /tmp/dir
rclone: delete &quot;important-file.txt&quot;?
y) Yes, this is OK (default)
n) No, skip this
s) Skip all delete operations with no more questions
!) Do all delete operations with no more questions
q) Exit rclone now.
y/n/s/!/q&gt; n</code></pre>
<p>The options mean</p>
<ul>
<li><code>y</code>: <strong>Yes</strong>, this operation should go ahead. You can also press Return for this to happen. You'll be asked every time unless you choose <code>s</code> or <code>!</code>.</li>
<li><code>n</code>: <strong>No</strong>, do not do this operation. You'll be asked every time unless you choose <code>s</code> or <code>!</code>.</li>
<li><code>s</code>: <strong>Skip</strong> all the following operations of this type with no more questions. This takes effect until rclone exits. If there are any different kind of operations you'll be prompted for them.</li>
<li><code>!</code>: <strong>Do all</strong> the following operations with no more questions. Useful if you've decided that you don't mind rclone doing that kind of operation. This takes effect until rclone exits . If there are any different kind of operations you'll be prompted for them.</li>
<li><code>q</code>: <strong>Quit</strong> rclone now, just in case!</li>
</ul>
<h3 id="leave-root">--leave-root</h3>
<p>During rmdirs it will not remove root directory, even if it's empty.</p>
<h3 id="log-filefile">--log-file=FILE</h3>
<p>Log all of rclone's output to FILE. This is not active by default. This can be useful for tracking down problems with syncs in combination with the <code>-v</code> flag. See the <a href="#logging">Logging section</a> for more info.</p>
<p>If FILE exists then rclone will append to it.</p>
<p>Note that if you are using the <code>logrotate</code> program to manage rclone's logs, then you should use the <code>copytruncate</code> option as rclone doesn't have a signal to rotate logs.</p>
<h3 id="log-format-list">--log-format LIST</h3>
<p>Comma separated list of log format options. Accepted options are <code>date</code>, <code>time</code>, <code>microseconds</code>, <code>pid</code>, <code>longfile</code>, <code>shortfile</code>, <code>UTC</code>. Any other keywords will be silently ignored. <code>pid</code> will tag log messages with process identifier which useful with <code>rclone mount --daemon</code>. Other accepted options are explained in the <a href="https://pkg.go.dev/log#pkg-constants">go documentation</a>. The default log format is "<code>date</code>,<code>time</code>".</p>
<h3 id="log-level-level">--log-level LEVEL</h3>
<p>This sets the log level for rclone. The default log level is <code>NOTICE</code>.</p>
<p><code>DEBUG</code> is equivalent to <code>-vv</code>. It outputs lots of debug info - useful for bug reports and really finding out what rclone is doing.</p>
<p><code>INFO</code> is equivalent to <code>-v</code>. It outputs information about each transfer and prints stats once a minute by default.</p>
<p><code>NOTICE</code> is the default log level if no logging flags are supplied. It outputs very little when things are working normally. It outputs warnings and significant events.</p>
<p><code>ERROR</code> is equivalent to <code>-q</code>. It only outputs error messages.</p>
<h3 id="use-json-log">--use-json-log</h3>
<p>This switches the log format to JSON for rclone. The fields of json log are level, msg, source, time.</p>
<h3 id="low-level-retries-number">--low-level-retries NUMBER</h3>
<p>This controls the number of low level retries rclone does.</p>
<p>A low level retry is used to retry a failing operation - typically one HTTP request. This might be uploading a chunk of a big file for example. You will see low level retries in the log with the <code>-v</code> flag.</p>
<p>This shouldn't need to be changed from the default in normal operations. However, if you get a lot of low level retries you may wish to reduce the value so rclone moves on to a high level retry (see the <code>--retries</code> flag) quicker.</p>
<p>Disable low level retries with <code>--low-level-retries 1</code>.</p>
<h3 id="max-backlogn">--max-backlog=N</h3>
<p>This is the maximum allowable backlog of files in a sync/copy/move queued for being checked or transferred.</p>
<p>This can be set arbitrarily large. It will only use memory when the queue is in use. Note that it will use in the order of N KiB of memory when the backlog is in use.</p>
<p>Setting this large allows rclone to calculate how many files are pending more accurately, give a more accurate estimated finish time and make <code>--order-by</code> work more accurately.</p>
<p>Setting this small will make rclone more synchronous to the listings of the remote which may be desirable.</p>
<p>Setting this to a negative number will make the backlog as large as possible.</p>
<h3 id="max-deleten">--max-delete=N</h3>
<p>This tells rclone not to delete more than N files. If that limit is exceeded then a fatal error will be generated and rclone will stop the operation in progress.</p>
<h3 id="max-delete-sizesize">--max-delete-size=SIZE</h3>
<p>Rclone will stop deleting files when the total size of deletions has reached the size specified. It defaults to off.</p>
<p>If that limit is exceeded then a fatal error will be generated and rclone will stop the operation in progress.</p>
<h3 id="max-depthn">--max-depth=N</h3>
<p>This modifies the recursion depth for all the commands except purge.</p>
<p>So if you do <code>rclone --max-depth 1 ls remote:path</code> you will see only the files in the top level directory. Using <code>--max-depth 2</code> means you will see all the files in first two directory levels and so on.</p>
<p>For historical reasons the <code>lsd</code> command defaults to using a <code>--max-depth</code> of 1 - you can override this with the command line flag.</p>
<p>You can use this command to disable recursion (with <code>--max-depth 1</code>).</p>
<p>Note that if you use this with <code>sync</code> and <code>--delete-excluded</code> the files not recursed through are considered excluded and will be deleted on the destination. Test first with <code>--dry-run</code> if you are not sure what will happen.</p>
<h3 id="max-durationtime">--max-duration=TIME</h3>
<p>Rclone will stop transferring when it has run for the duration specified. Defaults to off.</p>
<p>When the limit is reached all transfers will stop immediately. Use <code>--cutoff-mode</code> to modify this behaviour.</p>
<p>Rclone will exit with exit code 10 if the duration limit is reached.</p>
<h3 id="max-transfersize">--max-transfer=SIZE</h3>
<p>Rclone will stop transferring when it has reached the size specified. Defaults to off.</p>
<p>When the limit is reached all transfers will stop immediately. Use <code>--cutoff-mode</code> to modify this behaviour.</p>
<p>Rclone will exit with exit code 8 if the transfer limit is reached.</p>
<h3 id="cutoff-modehardsoftcautious">--cutoff-mode=hard|soft|cautious</h3>
<p>This modifies the behavior of <code>--max-transfer</code> and <code>--max-duration</code> Defaults to <code>--cutoff-mode=hard</code>.</p>
<p>Specifying <code>--cutoff-mode=hard</code> will stop transferring immediately when Rclone reaches the limit.</p>
<p>Specifying <code>--cutoff-mode=soft</code> will stop starting new transfers when Rclone reaches the limit.</p>
<p>Specifying <code>--cutoff-mode=cautious</code> will try to prevent Rclone from reaching the limit. Only applicable for <code>--max-transfer</code></p>
<h2 id="m---metadata">-M, --metadata</h2>
<p>Setting this flag enables rclone to copy the metadata from the source to the destination. For local backends this is ownership, permissions, xattr etc. See the <a href="#metadata">metadata section</a> for more info.</p>
<h3 id="metadata-mapper">--metadata-mapper SpaceSepList</h3>
<p>If you supply the parameter <code>--metadata-mapper /path/to/program</code> then rclone will use that program to map metadata from source object to destination object.</p>
<p>The argument to this flag should be a command with an optional space separated list of arguments. If one of the arguments has a space in then enclose it in <code>"</code>, if you want a literal <code>"</code> in an argument then enclose the argument in <code>"</code> and double the <code>"</code>. See <a href="https://godoc.org/encoding/csv">CSV encoding</a> for more info.</p>
<pre><code>--metadata-mapper &quot;python bin/test_metadata_mapper.py&quot;
--metadata-mapper &#39;python bin/test_metadata_mapper.py &quot;argument with a space&quot;&#39;
--metadata-mapper &#39;python bin/test_metadata_mapper.py &quot;argument with &quot;&quot;two&quot;&quot; quotes&quot;&#39;</code></pre>
<p>This uses a simple JSON based protocol with input on STDIN and output on STDOUT. This will be called for every file and directory copied and may be called concurrently.</p>
<p>The program's job is to take a metadata blob on the input and turn it into a metadata blob on the output suitable for the destination backend.</p>
<p>Input to the program (via STDIN) might look like this. This provides some context for the <code>Metadata</code> which may be important.</p>
<ul>
<li><code>SrcFs</code> is the config string for the remote that the object is currently on.</li>
<li><code>SrcFsType</code> is the name of the source backend.</li>
<li><code>DstFs</code> is the config string for the remote that the object is being copied to</li>
<li><code>DstFsType</code> is the name of the destination backend.</li>
<li><code>Remote</code> is the path of the object relative to the root.</li>
<li><code>Size</code>, <code>MimeType</code>, <code>ModTime</code> are attributes of the object.</li>
<li><code>IsDir</code> is <code>true</code> if this is a directory (not yet implemented).</li>
<li><code>ID</code> is the source <code>ID</code> of the object if known.</li>
<li><code>Metadata</code> is the backend specific metadata as described in the backend docs.</li>
</ul>
<div class="sourceCode" id="cb598"><pre class="sourceCode json"><code class="sourceCode json"><span id="cb598-1"><a href="#cb598-1" aria-hidden="true"></a><span class="fu">{</span></span>
<span id="cb598-2"><a href="#cb598-2" aria-hidden="true"></a>    <span class="dt">&quot;SrcFs&quot;</span><span class="fu">:</span> <span class="st">&quot;gdrive:&quot;</span><span class="fu">,</span></span>
<span id="cb598-3"><a href="#cb598-3" aria-hidden="true"></a>    <span class="dt">&quot;SrcFsType&quot;</span><span class="fu">:</span> <span class="st">&quot;drive&quot;</span><span class="fu">,</span></span>
<span id="cb598-4"><a href="#cb598-4" aria-hidden="true"></a>    <span class="dt">&quot;DstFs&quot;</span><span class="fu">:</span> <span class="st">&quot;newdrive:user&quot;</span><span class="fu">,</span></span>
<span id="cb598-5"><a href="#cb598-5" aria-hidden="true"></a>    <span class="dt">&quot;DstFsType&quot;</span><span class="fu">:</span> <span class="st">&quot;onedrive&quot;</span><span class="fu">,</span></span>
<span id="cb598-6"><a href="#cb598-6" aria-hidden="true"></a>    <span class="dt">&quot;Remote&quot;</span><span class="fu">:</span> <span class="st">&quot;test.txt&quot;</span><span class="fu">,</span></span>
<span id="cb598-7"><a href="#cb598-7" aria-hidden="true"></a>    <span class="dt">&quot;Size&quot;</span><span class="fu">:</span> <span class="dv">6</span><span class="fu">,</span></span>
<span id="cb598-8"><a href="#cb598-8" aria-hidden="true"></a>    <span class="dt">&quot;MimeType&quot;</span><span class="fu">:</span> <span class="st">&quot;text/plain; charset=utf-8&quot;</span><span class="fu">,</span></span>
<span id="cb598-9"><a href="#cb598-9" aria-hidden="true"></a>    <span class="dt">&quot;ModTime&quot;</span><span class="fu">:</span> <span class="st">&quot;2022-10-11T17:53:10.286745272+01:00&quot;</span><span class="fu">,</span></span>
<span id="cb598-10"><a href="#cb598-10" aria-hidden="true"></a>    <span class="dt">&quot;IsDir&quot;</span><span class="fu">:</span> <span class="kw">false</span><span class="fu">,</span></span>
<span id="cb598-11"><a href="#cb598-11" aria-hidden="true"></a>    <span class="dt">&quot;ID&quot;</span><span class="fu">:</span> <span class="st">&quot;xyz&quot;</span><span class="fu">,</span></span>
<span id="cb598-12"><a href="#cb598-12" aria-hidden="true"></a>    <span class="dt">&quot;Metadata&quot;</span><span class="fu">:</span> <span class="fu">{</span></span>
<span id="cb598-13"><a href="#cb598-13" aria-hidden="true"></a>        <span class="dt">&quot;btime&quot;</span><span class="fu">:</span> <span class="st">&quot;2022-10-11T16:53:11Z&quot;</span><span class="fu">,</span></span>
<span id="cb598-14"><a href="#cb598-14" aria-hidden="true"></a>        <span class="dt">&quot;content-type&quot;</span><span class="fu">:</span> <span class="st">&quot;text/plain; charset=utf-8&quot;</span><span class="fu">,</span></span>
<span id="cb598-15"><a href="#cb598-15" aria-hidden="true"></a>        <span class="dt">&quot;mtime&quot;</span><span class="fu">:</span> <span class="st">&quot;2022-10-11T17:53:10.286745272+01:00&quot;</span><span class="fu">,</span></span>
<span id="cb598-16"><a href="#cb598-16" aria-hidden="true"></a>        <span class="dt">&quot;owner&quot;</span><span class="fu">:</span> <span class="st">&quot;user1@domain1.com&quot;</span><span class="fu">,</span></span>
<span id="cb598-17"><a href="#cb598-17" aria-hidden="true"></a>        <span class="dt">&quot;permissions&quot;</span><span class="fu">:</span> <span class="st">&quot;...&quot;</span><span class="fu">,</span></span>
<span id="cb598-18"><a href="#cb598-18" aria-hidden="true"></a>        <span class="dt">&quot;description&quot;</span><span class="fu">:</span> <span class="st">&quot;my nice file&quot;</span><span class="fu">,</span></span>
<span id="cb598-19"><a href="#cb598-19" aria-hidden="true"></a>        <span class="dt">&quot;starred&quot;</span><span class="fu">:</span> <span class="st">&quot;false&quot;</span></span>
<span id="cb598-20"><a href="#cb598-20" aria-hidden="true"></a>    <span class="fu">}</span></span>
<span id="cb598-21"><a href="#cb598-21" aria-hidden="true"></a><span class="fu">}</span></span></code></pre></div>
<p>The program should then modify the input as desired and send it to STDOUT. The returned <code>Metadata</code> field will be used in its entirety for the destination object. Any other fields will be ignored. Note in this example we translate user names and permissions and add something to the description:</p>
<div class="sourceCode" id="cb599"><pre class="sourceCode json"><code class="sourceCode json"><span id="cb599-1"><a href="#cb599-1" aria-hidden="true"></a><span class="fu">{</span></span>
<span id="cb599-2"><a href="#cb599-2" aria-hidden="true"></a>    <span class="dt">&quot;Metadata&quot;</span><span class="fu">:</span> <span class="fu">{</span></span>
<span id="cb599-3"><a href="#cb599-3" aria-hidden="true"></a>        <span class="dt">&quot;btime&quot;</span><span class="fu">:</span> <span class="st">&quot;2022-10-11T16:53:11Z&quot;</span><span class="fu">,</span></span>
<span id="cb599-4"><a href="#cb599-4" aria-hidden="true"></a>        <span class="dt">&quot;content-type&quot;</span><span class="fu">:</span> <span class="st">&quot;text/plain; charset=utf-8&quot;</span><span class="fu">,</span></span>
<span id="cb599-5"><a href="#cb599-5" aria-hidden="true"></a>        <span class="dt">&quot;mtime&quot;</span><span class="fu">:</span> <span class="st">&quot;2022-10-11T17:53:10.286745272+01:00&quot;</span><span class="fu">,</span></span>
<span id="cb599-6"><a href="#cb599-6" aria-hidden="true"></a>        <span class="dt">&quot;owner&quot;</span><span class="fu">:</span> <span class="st">&quot;user1@domain2.com&quot;</span><span class="fu">,</span></span>
<span id="cb599-7"><a href="#cb599-7" aria-hidden="true"></a>        <span class="dt">&quot;permissions&quot;</span><span class="fu">:</span> <span class="st">&quot;...&quot;</span><span class="fu">,</span></span>
<span id="cb599-8"><a href="#cb599-8" aria-hidden="true"></a>        <span class="dt">&quot;description&quot;</span><span class="fu">:</span> <span class="st">&quot;my nice file [migrated from domain1]&quot;</span><span class="fu">,</span></span>
<span id="cb599-9"><a href="#cb599-9" aria-hidden="true"></a>        <span class="dt">&quot;starred&quot;</span><span class="fu">:</span> <span class="st">&quot;false&quot;</span></span>
<span id="cb599-10"><a href="#cb599-10" aria-hidden="true"></a>    <span class="fu">}</span></span>
<span id="cb599-11"><a href="#cb599-11" aria-hidden="true"></a><span class="fu">}</span></span></code></pre></div>
<p>Metadata can be removed here too.</p>
<p>An example python program might look something like this to implement the above transformations.</p>
<div class="sourceCode" id="cb600"><pre class="sourceCode python"><code class="sourceCode python"><span id="cb600-1"><a href="#cb600-1" aria-hidden="true"></a><span class="im">import</span> sys, json</span>
<span id="cb600-2"><a href="#cb600-2" aria-hidden="true"></a></span>
<span id="cb600-3"><a href="#cb600-3" aria-hidden="true"></a>i <span class="op">=</span> json.load(sys.stdin)</span>
<span id="cb600-4"><a href="#cb600-4" aria-hidden="true"></a>metadata <span class="op">=</span> i[<span class="st">&quot;Metadata&quot;</span>]</span>
<span id="cb600-5"><a href="#cb600-5" aria-hidden="true"></a><span class="co"># Add tag to description</span></span>
<span id="cb600-6"><a href="#cb600-6" aria-hidden="true"></a><span class="cf">if</span> <span class="st">&quot;description&quot;</span> <span class="kw">in</span> metadata:</span>
<span id="cb600-7"><a href="#cb600-7" aria-hidden="true"></a>    metadata[<span class="st">&quot;description&quot;</span>] <span class="op">+=</span> <span class="st">&quot; [migrated from domain1]&quot;</span></span>
<span id="cb600-8"><a href="#cb600-8" aria-hidden="true"></a><span class="cf">else</span>:</span>
<span id="cb600-9"><a href="#cb600-9" aria-hidden="true"></a>    metadata[<span class="st">&quot;description&quot;</span>] <span class="op">=</span> <span class="st">&quot;[migrated from domain1]&quot;</span></span>
<span id="cb600-10"><a href="#cb600-10" aria-hidden="true"></a><span class="co"># Modify owner</span></span>
<span id="cb600-11"><a href="#cb600-11" aria-hidden="true"></a><span class="cf">if</span> <span class="st">&quot;owner&quot;</span> <span class="kw">in</span> metadata:</span>
<span id="cb600-12"><a href="#cb600-12" aria-hidden="true"></a>    metadata[<span class="st">&quot;owner&quot;</span>] <span class="op">=</span> metadata[<span class="st">&quot;owner&quot;</span>].replace(<span class="st">&quot;domain1.com&quot;</span>, <span class="st">&quot;domain2.com&quot;</span>)</span>
<span id="cb600-13"><a href="#cb600-13" aria-hidden="true"></a>o <span class="op">=</span> { <span class="st">&quot;Metadata&quot;</span>: metadata }</span>
<span id="cb600-14"><a href="#cb600-14" aria-hidden="true"></a>json.dump(o, sys.stdout, indent<span class="op">=</span><span class="st">&quot;</span><span class="ch">\t</span><span class="st">&quot;</span>)</span></code></pre></div>
<p>You can find this example (slightly expanded) in the rclone source code at <a href="https://github.com/rclone/rclone/blob/master/bin/test_metadata_mapper.py">bin/test_metadata_mapper.py</a>.</p>
<p>If you want to see the input to the metadata mapper and the output returned from it in the log you can use <code>-vv --dump mapper</code>.</p>
<p>See the <a href="#metadata">metadata section</a> for more info.</p>
<h3 id="metadata-set-keyvalue">--metadata-set key=value</h3>
<p>Add metadata <code>key</code> = <code>value</code> when uploading. This can be repeated as many times as required. See the <a href="#metadata">metadata section</a> for more info.</p>
<h3 id="modify-windowtime">--modify-window=TIME</h3>
<p>When checking whether a file has been modified, this is the maximum allowed time difference that a file can have and still be considered equivalent.</p>
<p>The default is <code>1ns</code> unless this is overridden by a remote. For example OS X only stores modification times to the nearest second so if you are reading and writing to an OS X filing system this will be <code>1s</code> by default.</p>
<p>This command line flag allows you to override that computed default.</p>
<h3 id="multi-thread-write-buffer-sizesize">--multi-thread-write-buffer-size=SIZE</h3>
<p>When transferring with multiple threads, rclone will buffer SIZE bytes in memory before writing to disk for each thread.</p>
<p>This can improve performance if the underlying filesystem does not deal well with a lot of small writes in different positions of the file, so if you see transfers being limited by disk write speed, you might want to experiment with different values. Specially for magnetic drives and remote file systems a higher value can be useful.</p>
<p>Nevertheless, the default of <code>128k</code> should be fine for almost all use cases, so before changing it ensure that network is not really your bottleneck.</p>
<p>As a final hint, size is not the only factor: block size (or similar concept) can have an impact. In one case, we observed that exact multiples of 16k performed much better than other values.</p>
<h3 id="multi-thread-chunk-sizesizesuffix">--multi-thread-chunk-size=SizeSuffix</h3>
<p>Normally the chunk size for multi thread transfers is set by the backend. However some backends such as <code>local</code> and <code>smb</code> (which implement <code>OpenWriterAt</code> but not <code>OpenChunkWriter</code>) don't have a natural chunk size.</p>
<p>In this case the value of this option is used (default 64Mi).</p>
<h3 id="multi-thread-cutoff">--multi-thread-cutoff=SIZE</h3>
<p>When transferring files above SIZE to capable backends, rclone will use multiple threads to transfer the file (default 256M).</p>
<p>Capable backends are marked in the <a href="https://rclone.org/overview/#optional-features">overview</a> as <code>MultithreadUpload</code>. (They need to implement either the <code>OpenWriterAt</code> or <code>OpenChunkWriter</code> internal interfaces). These include include, <code>local</code>, <code>s3</code>, <code>azureblob</code>, <code>b2</code>, <code>oracleobjectstorage</code> and <code>smb</code> at the time of writing.</p>
<p>On the local disk, rclone preallocates the file (using <code>fallocate(FALLOC_FL_KEEP_SIZE)</code> on unix or <code>NTSetInformationFile</code> on Windows both of which takes no time) then each thread writes directly into the file at the correct place. This means that rclone won't create fragmented or sparse files and there won't be any assembly time at the end of the transfer.</p>
<p>The number of threads used to transfer is controlled by <code>--multi-thread-streams</code>.</p>
<p>Use <code>-vv</code> if you wish to see info about the threads.</p>
<p>This will work with the <code>sync</code>/<code>copy</code>/<code>move</code> commands and friends <code>copyto</code>/<code>moveto</code>. Multi thread transfers will be used with <code>rclone mount</code> and <code>rclone serve</code> if <code>--vfs-cache-mode</code> is set to <code>writes</code> or above.</p>
<p><strong>NB</strong> that this <strong>only</strong> works with supported backends as the destination but will work with any backend as the source.</p>
<p><strong>NB</strong> that multi-thread copies are disabled for local to local copies as they are faster without unless <code>--multi-thread-streams</code> is set explicitly.</p>
<p><strong>NB</strong> on Windows using multi-thread transfers to the local disk will cause the resulting files to be <a href="https://en.wikipedia.org/wiki/Sparse_file">sparse</a>. Use <code>--local-no-sparse</code> to disable sparse files (which may cause long delays at the start of transfers) or disable multi-thread transfers with <code>--multi-thread-streams 0</code></p>
<h3 id="multi-thread-streamsn">--multi-thread-streams=N</h3>
<p>When using multi thread transfers (see above <code>--multi-thread-cutoff</code>) this sets the number of streams to use. Set to <code>0</code> to disable multi thread transfers (Default 4).</p>
<p>If the backend has a <code>--backend-upload-concurrency</code> setting (eg <code>--s3-upload-concurrency</code>) then this setting will be used as the number of transfers instead if it is larger than the value of <code>--multi-thread-streams</code> or <code>--multi-thread-streams</code> isn't set.</p>
<h3 id="no-check-dest">--no-check-dest</h3>
<p>The <code>--no-check-dest</code> can be used with <code>move</code> or <code>copy</code> and it causes rclone not to check the destination at all when copying files.</p>
<p>This means that:</p>
<ul>
<li>the destination is not listed minimising the API calls</li>
<li>files are always transferred</li>
<li>this can cause duplicates on remotes which allow it (e.g. Google Drive)</li>
<li><code>--retries 1</code> is recommended otherwise you'll transfer everything again on a retry</li>
</ul>
<p>This flag is useful to minimise the transactions if you know that none of the files are on the destination.</p>
<p>This is a specialized flag which should be ignored by most users!</p>
<h3 id="no-gzip-encoding">--no-gzip-encoding</h3>
<p>Don't set <code>Accept-Encoding: gzip</code>. This means that rclone won't ask the server for compressed files automatically. Useful if you've set the server to return files with <code>Content-Encoding: gzip</code> but you uploaded compressed files.</p>
<p>There is no need to set this in normal operation, and doing so will decrease the network transfer efficiency of rclone.</p>
<h3 id="no-traverse">--no-traverse</h3>
<p>The <code>--no-traverse</code> flag controls whether the destination file system is traversed when using the <code>copy</code> or <code>move</code> commands. <code>--no-traverse</code> is not compatible with <code>sync</code> and will be ignored if you supply it with <code>sync</code>.</p>
<p>If you are only copying a small number of files (or are filtering most of the files) and/or have a large number of files on the destination then <code>--no-traverse</code> will stop rclone listing the destination and save time.</p>
<p>However, if you are copying a large number of files, especially if you are doing a copy where lots of the files under consideration haven't changed and won't need copying then you shouldn't use <code>--no-traverse</code>.</p>
<p>See <a href="https://rclone.org/commands/rclone_copy/">rclone copy</a> for an example of how to use it.</p>
<h3 id="no-unicode-normalization">--no-unicode-normalization</h3>
<p>Don't normalize unicode characters in filenames during the sync routine.</p>
<p>Sometimes, an operating system will store filenames containing unicode parts in their decomposed form (particularly macOS). Some cloud storage systems will then recompose the unicode, resulting in duplicate files if the data is ever copied back to a local filesystem.</p>
<p>Using this flag will disable that functionality, treating each unicode character as unique. For example, by default é and é will be normalized into the same character. With <code>--no-unicode-normalization</code> they will be treated as unique characters.</p>
<h3 id="no-update-modtime">--no-update-modtime</h3>
<p>When using this flag, rclone won't update modification times of remote files if they are incorrect as it would normally.</p>
<p>This can be used if the remote is being synced with another tool also (e.g. the Google Drive client).</p>
<h3 id="no-update-dir-modtime">--no-update-dir-modtime</h3>
<p>When using this flag, rclone won't update modification times of remote directories if they are incorrect as it would normally.</p>
<h3 id="order-by-string">--order-by string</h3>
<p>The <code>--order-by</code> flag controls the order in which files in the backlog are processed in <code>rclone sync</code>, <code>rclone copy</code> and <code>rclone move</code>.</p>
<p>The order by string is constructed like this. The first part describes what aspect is being measured:</p>
<ul>
<li><code>size</code> - order by the size of the files</li>
<li><code>name</code> - order by the full path of the files</li>
<li><code>modtime</code> - order by the modification date of the files</li>
</ul>
<p>This can have a modifier appended with a comma:</p>
<ul>
<li><code>ascending</code> or <code>asc</code> - order so that the smallest (or oldest) is processed first</li>
<li><code>descending</code> or <code>desc</code> - order so that the largest (or newest) is processed first</li>
<li><code>mixed</code> - order so that the smallest is processed first for some threads and the largest for others</li>
</ul>
<p>If the modifier is <code>mixed</code> then it can have an optional percentage (which defaults to <code>50</code>), e.g. <code>size,mixed,25</code> which means that 25% of the threads should be taking the smallest items and 75% the largest. The threads which take the smallest first will always take the smallest first and likewise the largest first threads. The <code>mixed</code> mode can be useful to minimise the transfer time when you are transferring a mixture of large and small files - the large files are guaranteed upload threads and bandwidth and the small files will be processed continuously.</p>
<p>If no modifier is supplied then the order is <code>ascending</code>.</p>
<p>For example</p>
<ul>
<li><code>--order-by size,desc</code> - send the largest files first</li>
<li><code>--order-by modtime,ascending</code> - send the oldest files first</li>
<li><code>--order-by name</code> - send the files with alphabetically by path first</li>
</ul>
<p>If the <code>--order-by</code> flag is not supplied or it is supplied with an empty string then the default ordering will be used which is as scanned. With <code>--checkers 1</code> this is mostly alphabetical, however with the default <code>--checkers 8</code> it is somewhat random.</p>
<h4 id="limitations-3">Limitations</h4>
<p>The <code>--order-by</code> flag does not do a separate pass over the data. This means that it may transfer some files out of the order specified if</p>
<ul>
<li>there are no files in the backlog or the source has not been fully scanned yet</li>
<li>there are more than <a href="#max-backlog-n">--max-backlog</a> files in the backlog</li>
</ul>
<p>Rclone will do its best to transfer the best file it has so in practice this should not cause a problem. Think of <code>--order-by</code> as being more of a best efforts flag rather than a perfect ordering.</p>
<p>If you want perfect ordering then you will need to specify <a href="#check-first">--check-first</a> which will find all the files which need transferring first before transferring any.</p>
<h3 id="partial-suffix">--partial-suffix</h3>
<p>When <a href="#inplace">--inplace</a> is not used, it causes rclone to use the <code>--partial-suffix</code> as suffix for temporary files.</p>
<p>Suffix length limit is 16 characters.</p>
<p>The default is <code>.partial</code>.</p>
<h3 id="password-command">--password-command SpaceSepList</h3>
<p>This flag supplies a program which should supply the config password when run. This is an alternative to rclone prompting for the password or setting the <code>RCLONE_CONFIG_PASS</code> variable. It is also used when setting the config password for the first time.</p>
<p>The argument to this should be a command with a space separated list of arguments. If one of the arguments has a space in then enclose it in <code>"</code>, if you want a literal <code>"</code> in an argument then enclose the argument in <code>"</code> and double the <code>"</code>. See <a href="https://godoc.org/encoding/csv">CSV encoding</a> for more info.</p>
<p>Eg</p>
<pre><code>--password-command &quot;echo hello&quot;
--password-command &#39;echo &quot;hello with space&quot;&#39;
--password-command &#39;echo &quot;hello with &quot;&quot;quotes&quot;&quot; and space&quot;&#39;</code></pre>
<p>Note that when changing the configuration password the environment variable <code>RCLONE_PASSWORD_CHANGE=1</code> will be set. This can be used to distinguish initial decryption of the config file from the new password.</p>
<p>See the <a href="#configuration-encryption">Configuration Encryption</a> for more info.</p>
<p>See a <a href="https://github.com/rclone/rclone/wiki/Windows-Powershell-use-rclone-password-command-for-Config-file-password">Windows PowerShell example on the Wiki</a>.</p>
<h3 id="p---progress">-P, --progress</h3>
<p>This flag makes rclone update the stats in a static block in the terminal providing a realtime overview of the transfer.</p>
<p>Any log messages will scroll above the static block. Log messages will push the static block down to the bottom of the terminal where it will stay.</p>
<p>Normally this is updated every 500mS but this period can be overridden with the <code>--stats</code> flag.</p>
<p>This can be used with the <code>--stats-one-line</code> flag for a simpler display.</p>
<p>To change the display length of filenames (for different terminal widths), see the <code>--stats-file-name-length</code> option. The default output is formatted for 80 character wide terminals.</p>
<p>Note: On Windows until <a href="https://github.com/Azure/go-ansiterm/issues/26">this bug</a> is fixed all non-ASCII characters will be replaced with <code>.</code> when <code>--progress</code> is in use.</p>
<h3 id="progress-terminal-title">--progress-terminal-title</h3>
<p>This flag, when used with <code>-P/--progress</code>, will print the string <code>ETA: %s</code> to the terminal title.</p>
<h3 id="q---quiet">-q, --quiet</h3>
<p>This flag will limit rclone's output to error messages only.</p>
<h3 id="refresh-times">--refresh-times</h3>
<p>The <code>--refresh-times</code> flag can be used to update modification times of existing files when they are out of sync on backends which don't support hashes.</p>
<p>This is useful if you uploaded files with the incorrect timestamps and you now wish to correct them.</p>
<p>This flag is <strong>only</strong> useful for destinations which don't support hashes (e.g. <code>crypt</code>).</p>
<p>This can be used any of the sync commands <code>sync</code>, <code>copy</code> or <code>move</code>.</p>
<p>To use this flag you will need to be doing a modification time sync (so not using <code>--size-only</code> or <code>--checksum</code>). The flag will have no effect when using <code>--size-only</code> or <code>--checksum</code>.</p>
<p>If this flag is used when rclone comes to upload a file it will check to see if there is an existing file on the destination. If this file matches the source with size (and checksum if available) but has a differing timestamp then instead of re-uploading it, rclone will update the timestamp on the destination file. If the checksum does not match rclone will upload the new file. If the checksum is absent (e.g. on a <code>crypt</code> backend) then rclone will update the timestamp.</p>
<p>Note that some remotes can't set the modification time without re-uploading the file so this flag is less useful on them.</p>
<p>Normally if you are doing a modification time sync rclone will update modification times without <code>--refresh-times</code> provided that the remote supports checksums <strong>and</strong> the checksums match on the file. However if the checksums are absent then rclone will upload the file rather than setting the timestamp as this is the safe behaviour.</p>
<h3 id="retries-int">--retries int</h3>
<p>Retry the entire sync if it fails this many times it fails (default 3).</p>
<p>Some remotes can be unreliable and a few retries help pick up the files which didn't get transferred because of errors.</p>
<p>Disable retries with <code>--retries 1</code>.</p>
<h3 id="retries-sleeptime">--retries-sleep=TIME</h3>
<p>This sets the interval between each retry specified by <code>--retries</code></p>
<p>The default is <code>0</code>. Use <code>0</code> to disable.</p>
<h3 id="server-side-across-configs">--server-side-across-configs</h3>
<p>Allow server-side operations (e.g. copy or move) to work across different configurations.</p>
<p>This can be useful if you wish to do a server-side copy or move between two remotes which use the same backend but are configured differently.</p>
<p>Note that this isn't enabled by default because it isn't easy for rclone to tell if it will work between any two configurations.</p>
<h3 id="size-only">--size-only</h3>
<p>Normally rclone will look at modification time and size of files to see if they are equal. If you set this flag then rclone will check only the size.</p>
<p>This can be useful transferring files from Dropbox which have been modified by the desktop sync client which doesn't set checksums of modification times in the same way as rclone.</p>
<h3 id="statstime">--stats=TIME</h3>
<p>Commands which transfer data (<code>sync</code>, <code>copy</code>, <code>copyto</code>, <code>move</code>, <code>moveto</code>) will print data transfer stats at regular intervals to show their progress.</p>
<p>This sets the interval.</p>
<p>The default is <code>1m</code>. Use <code>0</code> to disable.</p>
<p>If you set the stats interval then all commands can show stats. This can be useful when running other commands, <code>check</code> or <code>mount</code> for example.</p>
<p>Stats are logged at <code>INFO</code> level by default which means they won't show at default log level <code>NOTICE</code>. Use <code>--stats-log-level NOTICE</code> or <code>-v</code> to make them show. See the <a href="#logging">Logging section</a> for more info on log levels.</p>
<p>Note that on macOS you can send a SIGINFO (which is normally ctrl-T in the terminal) to make the stats print immediately.</p>
<h3 id="stats-file-name-length-integer">--stats-file-name-length integer</h3>
<p>By default, the <code>--stats</code> output will truncate file names and paths longer than 40 characters. This is equivalent to providing <code>--stats-file-name-length 40</code>. Use <code>--stats-file-name-length 0</code> to disable any truncation of file names printed by stats.</p>
<h3 id="stats-log-level-string">--stats-log-level string</h3>
<p>Log level to show <code>--stats</code> output at. This can be <code>DEBUG</code>, <code>INFO</code>, <code>NOTICE</code>, or <code>ERROR</code>. The default is <code>INFO</code>. This means at the default level of logging which is <code>NOTICE</code> the stats won't show - if you want them to then use <code>--stats-log-level NOTICE</code>. See the <a href="#logging">Logging section</a> for more info on log levels.</p>
<h3 id="stats-one-line">--stats-one-line</h3>
<p>When this is specified, rclone condenses the stats into a single line showing the most important stats only.</p>
<h3 id="stats-one-line-date">--stats-one-line-date</h3>
<p>When this is specified, rclone enables the single-line stats and prepends the display with a date string. The default is <code>2006/01/02 15:04:05 -</code></p>
<h3 id="stats-one-line-date-format">--stats-one-line-date-format</h3>
<p>When this is specified, rclone enables the single-line stats and prepends the display with a user-supplied date string. The date string MUST be enclosed in quotes. Follow <a href="https://golang.org/pkg/time/#Time.Format">golang specs</a> for date formatting syntax.</p>
<h3 id="stats-unitbitsbytes">--stats-unit=bits|bytes</h3>
<p>By default, data transfer rates will be printed in bytes per second.</p>
<p>This option allows the data rate to be printed in bits per second.</p>
<p>Data transfer volume will still be reported in bytes.</p>
<p>The rate is reported as a binary unit, not SI unit. So 1 Mbit/s equals 1,048,576 bit/s and not 1,000,000 bit/s.</p>
<p>The default is <code>bytes</code>.</p>
<h3 id="suffixsuffix">--suffix=SUFFIX</h3>
<p>When using <code>sync</code>, <code>copy</code> or <code>move</code> any files which would have been overwritten or deleted will have the suffix added to them. If there is a file with the same path (after the suffix has been added), then it will be overwritten.</p>
<p>The remote in use must support server-side move or copy and you must use the same remote as the destination of the sync.</p>
<p>This is for use with files to add the suffix in the current directory or with <code>--backup-dir</code>. See <code>--backup-dir</code> for more info.</p>
<p>For example</p>
<pre><code>rclone copy --interactive /path/to/local/file remote:current --suffix .bak</code></pre>
<p>will copy <code>/path/to/local</code> to <code>remote:current</code>, but for any files which would have been updated or deleted have .bak added.</p>
<p>If using <code>rclone sync</code> with <code>--suffix</code> and without <code>--backup-dir</code> then it is recommended to put a filter rule in excluding the suffix otherwise the <code>sync</code> will delete the backup files.</p>
<pre><code>rclone sync --interactive /path/to/local/file remote:current --suffix .bak --exclude &quot;*.bak&quot;</code></pre>
<h3 id="suffix-keep-extension">--suffix-keep-extension</h3>
<p>When using <code>--suffix</code>, setting this causes rclone put the SUFFIX before the extension of the files that it backs up rather than after.</p>
<p>So let's say we had <code>--suffix -2019-01-01</code>, without the flag <code>file.txt</code> would be backed up to <code>file.txt-2019-01-01</code> and with the flag it would be backed up to <code>file-2019-01-01.txt</code>. This can be helpful to make sure the suffixed files can still be opened.</p>
<p>If a file has two (or more) extensions and the second (or subsequent) extension is recognised as a valid mime type, then the suffix will go before that extension. So <code>file.tar.gz</code> would be backed up to <code>file-2019-01-01.tar.gz</code> whereas <code>file.badextension.gz</code> would be backed up to <code>file.badextension-2019-01-01.gz</code>.</p>
<h3 id="syslog">--syslog</h3>
<p>On capable OSes (not Windows or Plan9) send all log output to syslog.</p>
<p>This can be useful for running rclone in a script or <code>rclone mount</code>.</p>
<h3 id="syslog-facility-string">--syslog-facility string</h3>
<p>If using <code>--syslog</code> this sets the syslog facility (e.g. <code>KERN</code>, <code>USER</code>). See <code>man syslog</code> for a list of possible facilities. The default facility is <code>DAEMON</code>.</p>
<h3 id="temp-dirdir">--temp-dir=DIR</h3>
<p>Specify the directory rclone will use for temporary files, to override the default. Make sure the directory exists and have accessible permissions.</p>
<p>By default the operating system's temp directory will be used: - On Unix systems, <code>$TMPDIR</code> if non-empty, else <code>/tmp</code>. - On Windows, the first non-empty value from <code>%TMP%</code>, <code>%TEMP%</code>, <code>%USERPROFILE%</code>, or the Windows directory.</p>
<p>When overriding the default with this option, the specified path will be set as value of environment variable <code>TMPDIR</code> on Unix systems and <code>TMP</code> and <code>TEMP</code> on Windows.</p>
<p>You can use the <a href="https://rclone.org/commands/rclone_config_paths/">config paths</a> command to see the current value.</p>
<h3 id="tpslimit-float">--tpslimit float</h3>
<p>Limit transactions per second to this number. Default is 0 which is used to mean unlimited transactions per second.</p>
<p>A transaction is roughly defined as an API call; its exact meaning will depend on the backend. For HTTP based backends it is an HTTP PUT/GET/POST/etc and its response. For FTP/SFTP it is a round trip transaction over TCP.</p>
<p>For example, to limit rclone to 10 transactions per second use <code>--tpslimit 10</code>, or to 1 transaction every 2 seconds use <code>--tpslimit 0.5</code>.</p>
<p>Use this when the number of transactions per second from rclone is causing a problem with the cloud storage provider (e.g. getting you banned or rate limited).</p>
<p>This can be very useful for <code>rclone mount</code> to control the behaviour of applications using it.</p>
<p>This limit applies to all HTTP based backends and to the FTP and SFTP backends. It does not apply to the local backend or the Storj backend.</p>
<p>See also <code>--tpslimit-burst</code>.</p>
<h3 id="tpslimit-burst-int">--tpslimit-burst int</h3>
<p>Max burst of transactions for <code>--tpslimit</code> (default <code>1</code>).</p>
<p>Normally <code>--tpslimit</code> will do exactly the number of transaction per second specified. However if you supply <code>--tps-burst</code> then rclone can save up some transactions from when it was idle giving a burst of up to the parameter supplied.</p>
<p>For example if you provide <code>--tpslimit-burst 10</code> then if rclone has been idle for more than 10*<code>--tpslimit</code> then it can do 10 transactions very quickly before they are limited again.</p>
<p>This may be used to increase performance of <code>--tpslimit</code> without changing the long term average number of transactions per second.</p>
<h3 id="track-renames">--track-renames</h3>
<p>By default, rclone doesn't keep track of renamed files, so if you rename a file locally then sync it to a remote, rclone will delete the old file on the remote and upload a new copy.</p>
<p>An rclone sync with <code>--track-renames</code> runs like a normal sync, but keeps track of objects which exist in the destination but not in the source (which would normally be deleted), and which objects exist in the source but not the destination (which would normally be transferred). These objects are then candidates for renaming.</p>
<p>After the sync, rclone matches up the source only and destination only objects using the <code>--track-renames-strategy</code> specified and either renames the destination object or transfers the source and deletes the destination object. <code>--track-renames</code> is stateless like all of rclone's syncs.</p>
<p>To use this flag the destination must support server-side copy or server-side move, and to use a hash based <code>--track-renames-strategy</code> (the default) the source and the destination must have a compatible hash.</p>
<p>If the destination does not support server-side copy or move, rclone will fall back to the default behaviour and log an error level message to the console.</p>
<p>Encrypted destinations are not currently supported by <code>--track-renames</code> if <code>--track-renames-strategy</code> includes <code>hash</code>.</p>
<p>Note that <code>--track-renames</code> is incompatible with <code>--no-traverse</code> and that it uses extra memory to keep track of all the rename candidates.</p>
<p>Note also that <code>--track-renames</code> is incompatible with <code>--delete-before</code> and will select <code>--delete-after</code> instead of <code>--delete-during</code>.</p>
<h3 id="track-renames-strategy-hashmodtimeleafsize">--track-renames-strategy (hash,modtime,leaf,size)</h3>
<p>This option changes the file matching criteria for <code>--track-renames</code>.</p>
<p>The matching is controlled by a comma separated selection of these tokens:</p>
<ul>
<li><code>modtime</code> - the modification time of the file - not supported on all backends</li>
<li><code>hash</code> - the hash of the file contents - not supported on all backends</li>
<li><code>leaf</code> - the name of the file not including its directory name</li>
<li><code>size</code> - the size of the file (this is always enabled)</li>
</ul>
<p>The default option is <code>hash</code>.</p>
<p>Using <code>--track-renames-strategy modtime,leaf</code> would match files based on modification time, the leaf of the file name and the size only.</p>
<p>Using <code>--track-renames-strategy modtime</code> or <code>leaf</code> can enable <code>--track-renames</code> support for encrypted destinations.</p>
<p>Note that the <code>hash</code> strategy is not supported with encrypted destinations.</p>
<h3 id="delete-beforeduringafter">--delete-(before,during,after)</h3>
<p>This option allows you to specify when files on your destination are deleted when you sync folders.</p>
<p>Specifying the value <code>--delete-before</code> will delete all files present on the destination, but not on the source <em>before</em> starting the transfer of any new or updated files. This uses two passes through the file systems, one for the deletions and one for the copies.</p>
<p>Specifying <code>--delete-during</code> will delete files while checking and uploading files. This is the fastest option and uses the least memory.</p>
<p>Specifying <code>--delete-after</code> (the default value) will delay deletion of files until all new/updated files have been successfully transferred. The files to be deleted are collected in the copy pass then deleted after the copy pass has completed successfully. The files to be deleted are held in memory so this mode may use more memory. This is the safest mode as it will only delete files if there have been no errors subsequent to that. If there have been errors before the deletions start then you will get the message <code>not deleting files as there were IO errors</code>.</p>
<h3 id="fast-list">--fast-list</h3>
<p>When doing anything which involves a directory listing (e.g. <code>sync</code>, <code>copy</code>, <code>ls</code> - in fact nearly every command), rclone has different strategies to choose from.</p>
<p>The basic strategy is to list one directory and processes it before using more directory lists to process any subdirectories. This is a mandatory backend feature, called <code>List</code>, which means it is supported by all backends. This strategy uses small amount of memory, and because it can be parallelised it is fast for operations involving processing of the list results.</p>
<p>Some backends provide the support for an alternative strategy, where all files beneath a directory can be listed in one (or a small number) of transactions. Rclone supports this alternative strategy through an optional backend feature called <a href="https://rclone.org/overview/#listr"><code>ListR</code></a>. You can see in the storage system overview documentation's <a href="https://rclone.org/overview/#optional-features">optional features</a> section which backends it is enabled for (these tend to be the bucket-based ones, e.g. S3, B2, GCS, Swift). This strategy requires fewer transactions for highly recursive operations, which is important on backends where this is charged or heavily rate limited. It may be faster (due to fewer transactions) or slower (because it can't be parallelized) depending on different parameters, and may require more memory if rclone has to keep the whole listing in memory.</p>
<p>Which listing strategy rclone picks for a given operation is complicated, but in general it tries to choose the best possible. It will prefer <code>ListR</code> in situations where it doesn't need to store the listed files in memory, e.g. for unlimited recursive <code>ls</code> command variants. In other situations it will prefer <code>List</code>, e.g. for <code>sync</code> and <code>copy</code>, where it needs to keep the listed files in memory, and is performing operations on them where parallelization may be a huge advantage.</p>
<p>Rclone is not able to take all relevant parameters into account for deciding the best strategy, and therefore allows you to influence the choice in two ways: You can stop rclone from using <code>ListR</code> by disabling the feature, using the <a href="#disable-feature-feature">--disable</a> option (<code>--disable ListR</code>), or you can allow rclone to use <code>ListR</code> where it would normally choose not to do so due to higher memory usage, using the <code>--fast-list</code> option. Rclone should always produce identical results either way. Using <code>--disable ListR</code> or <code>--fast-list</code> on a remote which doesn't support <code>ListR</code> does nothing, rclone will just ignore it.</p>
<p>A rule of thumb is that if you pay for transactions and can fit your entire sync listing into memory, then <code>--fast-list</code> is recommended. If you have a very big sync to do, then don't use <code>--fast-list</code>, otherwise you will run out of memory. Run some tests and compare before you decide, and if in doubt then just leave the default, let rclone decide, i.e. not use <code>--fast-list</code>.</p>
<h3 id="timeouttime">--timeout=TIME</h3>
<p>This sets the IO idle timeout. If a transfer has started but then becomes idle for this long it is considered broken and disconnected.</p>
<p>The default is <code>5m</code>. Set to <code>0</code> to disable.</p>
<h3 id="transfersn">--transfers=N</h3>
<p>The number of file transfers to run in parallel. It can sometimes be useful to set this to a smaller number if the remote is giving a lot of timeouts or bigger if you have lots of bandwidth and a fast remote.</p>
<p>The default is to run 4 file transfers in parallel.</p>
<p>Look at --multi-thread-streams if you would like to control single file transfers.</p>
<h3 id="u---update">-u, --update</h3>
<p>This forces rclone to skip any files which exist on the destination and have a modified time that is newer than the source file.</p>
<p>This can be useful in avoiding needless transfers when transferring to a remote which doesn't support modification times directly (or when using <code>--use-server-modtime</code> to avoid extra API calls) as it is more accurate than a <code>--size-only</code> check and faster than using <code>--checksum</code>. On such remotes (or when using <code>--use-server-modtime</code>) the time checked will be the uploaded time.</p>
<p>If an existing destination file has a modification time older than the source file's, it will be updated if the sizes are different. If the sizes are the same, it will be updated if the checksum is different or not available.</p>
<p>If an existing destination file has a modification time equal (within the computed modify window) to the source file's, it will be updated if the sizes are different. The checksum will not be checked in this case unless the <code>--checksum</code> flag is provided.</p>
<p>In all other cases the file will not be updated.</p>
<p>Consider using the <code>--modify-window</code> flag to compensate for time skews between the source and the backend, for backends that do not support mod times, and instead use uploaded times. However, if the backend does not support checksums, note that syncing or copying within the time skew window may still result in additional transfers for safety.</p>
<h3 id="use-mmap">--use-mmap</h3>
<p>If this flag is set then rclone will use anonymous memory allocated by mmap on Unix based platforms and VirtualAlloc on Windows for its transfer buffers (size controlled by <code>--buffer-size</code>). Memory allocated like this does not go on the Go heap and can be returned to the OS immediately when it is finished with.</p>
<p>If this flag is not set then rclone will allocate and free the buffers using the Go memory allocator which may use more memory as memory pages are returned less aggressively to the OS.</p>
<p>It is possible this does not work well on all platforms so it is disabled by default; in the future it may be enabled by default.</p>
<h3 id="use-server-modtime">--use-server-modtime</h3>
<p>Some object-store backends (e.g, Swift, S3) do not preserve file modification times (modtime). On these backends, rclone stores the original modtime as additional metadata on the object. By default it will make an API call to retrieve the metadata when the modtime is needed by an operation.</p>
<p>Use this flag to disable the extra API call and rely instead on the server's modified time. In cases such as a local to remote sync using <code>--update</code>, knowing the local file is newer than the time it was last uploaded to the remote is sufficient. In those cases, this flag can speed up the process and reduce the number of API calls necessary.</p>
<p>Using this flag on a sync operation without also using <code>--update</code> would cause all files modified at any time other than the last upload time to be uploaded again, which is probably not what you want.</p>
<h3 id="v--vv---verbose">-v, -vv, --verbose</h3>
<p>With <code>-v</code> rclone will tell you about each file that is transferred and a small number of significant events.</p>
<p>With <code>-vv</code> rclone will become very verbose telling you about every file it considers and transfers. Please send bug reports with a log with this setting.</p>
<p>When setting verbosity as an environment variable, use <code>RCLONE_VERBOSE=1</code> or <code>RCLONE_VERBOSE=2</code> for <code>-v</code> and <code>-vv</code> respectively.</p>
<h3 id="v---version">-V, --version</h3>
<p>Prints the version number</p>
<h2 id="ssltls-options">SSL/TLS options</h2>
<p>The outgoing SSL/TLS connections rclone makes can be controlled with these options. For example this can be very useful with the HTTP or WebDAV backends. Rclone HTTP servers have their own set of configuration for SSL/TLS which you can find in their documentation.</p>
<h3 id="ca-cert-stringarray">--ca-cert stringArray</h3>
<p>This loads the PEM encoded certificate authority certificates and uses it to verify the certificates of the servers rclone connects to.</p>
<p>If you have generated certificates signed with a local CA then you will need this flag to connect to servers using those certificates.</p>
<h3 id="client-cert-string">--client-cert string</h3>
<p>This loads the PEM encoded client side certificate.</p>
<p>This is used for <a href="https://en.wikipedia.org/wiki/Mutual_authentication">mutual TLS authentication</a>.</p>
<p>The <code>--client-key</code> flag is required too when using this.</p>
<h3 id="client-key-string">--client-key string</h3>
<p>This loads the PEM encoded client side private key used for mutual TLS authentication. Used in conjunction with <code>--client-cert</code>.</p>
<h3 id="no-check-certificatetruefalse">--no-check-certificate=true/false</h3>
<p><code>--no-check-certificate</code> controls whether a client verifies the server's certificate chain and host name. If <code>--no-check-certificate</code> is true, TLS accepts any certificate presented by the server and any host name in that certificate. In this mode, TLS is susceptible to man-in-the-middle attacks.</p>
<p>This option defaults to <code>false</code>.</p>
<p><strong>This should be used only for testing.</strong></p>
<h2 id="configuration-encryption">Configuration Encryption</h2>
<p>Your configuration file contains information for logging in to your cloud services. This means that you should keep your <code>rclone.conf</code> file in a secure location.</p>
<p>If you are in an environment where that isn't possible, you can add a password to your configuration. This means that you will have to supply the password every time you start rclone.</p>
<p>To add a password to your rclone configuration, execute <code>rclone config</code>.</p>
<pre><code>&gt;rclone config
Current remotes:

e) Edit existing remote
n) New remote
d) Delete remote
s) Set configuration password
q) Quit config
e/n/d/s/q&gt;</code></pre>
<p>Go into <code>s</code>, Set configuration password:</p>
<pre><code>e/n/d/s/q&gt; s
Your configuration is not encrypted.
If you add a password, you will protect your login information to cloud services.
a) Add Password
q) Quit to main menu
a/q&gt; a
Enter NEW configuration password:
password:
Confirm NEW password:
password:
Password set
Your configuration is encrypted.
c) Change Password
u) Unencrypt configuration
q) Quit to main menu
c/u/q&gt;</code></pre>
<p>Your configuration is now encrypted, and every time you start rclone you will have to supply the password. See below for details. In the same menu, you can change the password or completely remove encryption from your configuration.</p>
<p>There is no way to recover the configuration if you lose your password.</p>
<p>You can also use</p>
<ul>
<li><a href="https://rclone.org/commands/rclone_config_encryption_set/">rclone config encryption set</a> to set the config encryption directly</li>
<li><a href="https://rclone.org/commands/rclone_config_encryption_remove/">rclone config encryption remove</a> to remove it</li>
<li><a href="https://rclone.org/commands/rclone_config_encryption_check/">rclone config encryption check</a> to check that it is encrypted properly.</li>
</ul>
<p>rclone uses <a href="https://godoc.org/golang.org/x/crypto/nacl/secretbox">nacl secretbox</a> which in turn uses XSalsa20 and Poly1305 to encrypt and authenticate your configuration with secret-key cryptography. The password is SHA-256 hashed, which produces the key for secretbox. The hashed password is not stored.</p>
<p>While this provides very good security, we do not recommend storing your encrypted rclone configuration in public if it contains sensitive information, maybe except if you use a very strong password.</p>
<p>If it is safe in your environment, you can set the <code>RCLONE_CONFIG_PASS</code> environment variable to contain your password, in which case it will be used for decrypting the configuration.</p>
<p>You can set this for a session from a script. For unix like systems save this to a file called <code>set-rclone-password</code>:</p>
<pre><code>#!/bin/echo Source this file don&#39;t run it

read -s RCLONE_CONFIG_PASS
export RCLONE_CONFIG_PASS</code></pre>
<p>Then source the file when you want to use it. From the shell you would do <code>source set-rclone-password</code>. It will then ask you for the password and set it in the environment variable.</p>
<p>An alternate means of supplying the password is to provide a script which will retrieve the password and print on standard output. This script should have a fully specified path name and not rely on any environment variables. The script is supplied either via <a href="#password-command"><code>--password-command="..."</code></a> command line argument or via the <code>RCLONE_PASSWORD_COMMAND</code> environment variable.</p>
<p>One useful example of this is using the <code>passwordstore</code> application to retrieve the password:</p>
<pre><code>export RCLONE_PASSWORD_COMMAND=&quot;pass rclone/config&quot;</code></pre>
<p>If the <code>passwordstore</code> password manager holds the password for the rclone configuration, using the script method means the password is primarily protected by the <code>passwordstore</code> system, and is never embedded in the clear in scripts, nor available for examination using the standard commands available. It is quite possible with long running rclone sessions for copies of passwords to be innocently captured in log files or terminal scroll buffers, etc. Using the script method of supplying the password enhances the security of the config password considerably.</p>
<p>If you are running rclone inside a script, unless you are using the <code>--password-command</code> method, you might want to disable password prompts. To do that, pass the parameter <code>--ask-password=false</code> to rclone. This will make rclone fail instead of asking for a password if <code>RCLONE_CONFIG_PASS</code> doesn't contain a valid password, and <code>--password-command</code> has not been supplied.</p>
<p>Whenever running commands that may be affected by options in a configuration file, rclone will look for an existing file according to the rules described <a href="#config-config-file">above</a>, and load any it finds. If an encrypted file is found, this includes decrypting it, with the possible consequence of a password prompt. When executing a command line that you know are not actually using anything from such a configuration file, you can avoid it being loaded by overriding the location, e.g. with one of the documented special values for memory-only configuration. Since only backend options can be stored in configuration files, this is normally unnecessary for commands that do not operate on backends, e.g. <code>completion</code>. However, it will be relevant for commands that do operate on backends in general, but are used without referencing a stored remote, e.g. listing local filesystem paths, or <a href="#connection-strings">connection strings</a>: <code>rclone --config="" ls .</code></p>
<h2 id="configuration-encryption-cheatsheet">Configuration Encryption Cheatsheet</h2>
<p>You can quickly apply a configuration encryption without plain-text at rest or transfer. Detailed instructions for popular OSes:</p>
<h3 id="mac">Mac</h3>
<ul>
<li>Generate and store a password</li>
</ul>
<p><code>security add-generic-password -a rclone -s config -w $(openssl rand -base64 40)</code></p>
<ul>
<li>Add the retrieval instruction to your .zprofile / .profile</li>
</ul>
<p><code>export RCLONE_PASSWORD_COMMAND="/usr/bin/security find-generic-password -a rclone -s config -w"</code></p>
<h3 id="linux-1">Linux</h3>
<ul>
<li>Prerequisite</li>
</ul>
<p>Linux doesn't come with a default password manager. Let's install the "pass" utility using a package manager, e.g. <code>apt install pass</code>, <code>yum install pass</code>, <a href="https://www.passwordstore.org/#download">etc.</a>; then initialize a password store:</p>
<p><code>pass init rclone</code></p>
<ul>
<li>Generate and store a password</li>
</ul>
<p><code>echo $(openssl rand -base64 40) | pass insert -m rclone/config</code></p>
<ul>
<li>Add the retrieval instruction</li>
</ul>
<p><code>export RCLONE_PASSWORD_COMMAND="/usr/bin/pass rclone/config"</code></p>
<h3 id="windows-2">Windows</h3>
<ul>
<li>Generate and store a password</li>
</ul>
<p><code>New-Object -TypeName PSCredential -ArgumentList "rclone", (ConvertTo-SecureString -String ([System.Web.Security.Membership]::GeneratePassword(40, 10)) -AsPlainText -Force) | Export-Clixml -Path "rclone-credential.xml"</code></p>
<ul>
<li>Add the password retrieval instruction</li>
</ul>
<p><code>[Environment]::SetEnvironmentVariable("RCLONE_PASSWORD_COMMAND", "[System.Runtime.InteropServices.Marshal]::PtrToStringAuto([System.Runtime.InteropServices.Marshal]::SecureStringToBSTR((Import-Clixml -Path "rclone-credential.xml").Password))")</code></p>
<h3 id="encrypt-the-config-file-all-systems">Encrypt the config file (all systems)</h3>
<ul>
<li><p>Execute <code>rclone config</code> -&gt; <code>s</code></p></li>
<li><p>Add/update the password from previous steps</p></li>
</ul>
<h2 id="developer-options">Developer options</h2>
<p>These options are useful when developing or debugging rclone. There are also some more remote specific options which aren't documented here which are used for testing. These start with remote name e.g. <code>--drive-test-option</code> - see the docs for the remote in question.</p>
<h3 id="cpuprofilefile">--cpuprofile=FILE</h3>
<p>Write CPU profile to file. This can be analysed with <code>go tool pprof</code>.</p>
<h4 id="dump-flagflagflag">--dump flag,flag,flag</h4>
<p>The <code>--dump</code> flag takes a comma separated list of flags to dump info about.</p>
<p>Note that some headers including <code>Accept-Encoding</code> as shown may not be correct in the request and the response may not show <code>Content-Encoding</code> if the go standard libraries auto gzip encoding was in effect. In this case the body of the request will be gunzipped before showing it.</p>
<p>The available flags are:</p>
<h4 id="dump-headers">--dump headers</h4>
<p>Dump HTTP headers with <code>Authorization:</code> lines removed. May still contain sensitive info. Can be very verbose. Useful for debugging only.</p>
<p>Use <code>--dump auth</code> if you do want the <code>Authorization:</code> headers.</p>
<h4 id="dump-bodies">--dump bodies</h4>
<p>Dump HTTP headers and bodies - may contain sensitive info. Can be very verbose. Useful for debugging only.</p>
<p>Note that the bodies are buffered in memory so don't use this for enormous files.</p>
<h4 id="dump-requests">--dump requests</h4>
<p>Like <code>--dump bodies</code> but dumps the request bodies and the response headers. Useful for debugging download problems.</p>
<h4 id="dump-responses">--dump responses</h4>
<p>Like <code>--dump bodies</code> but dumps the response bodies and the request headers. Useful for debugging upload problems.</p>
<h4 id="dump-auth">--dump auth</h4>
<p>Dump HTTP headers - will contain sensitive info such as <code>Authorization:</code> headers - use <code>--dump headers</code> to dump without <code>Authorization:</code> headers. Can be very verbose. Useful for debugging only.</p>
<h4 id="dump-filters">--dump filters</h4>
<p>Dump the filters to the output. Useful to see exactly what include and exclude options are filtering on.</p>
<h4 id="dump-goroutines">--dump goroutines</h4>
<p>This dumps a list of the running go-routines at the end of the command to standard output.</p>
<h4 id="dump-openfiles">--dump openfiles</h4>
<p>This dumps a list of the open files at the end of the command. It uses the <code>lsof</code> command to do that so you'll need that installed to use it.</p>
<h4 id="dump-mapper">--dump mapper</h4>
<p>This shows the JSON blobs being sent to the program supplied with <code>--metadata-mapper</code> and received from it. It can be useful for debugging the metadata mapper interface.</p>
<h3 id="memprofilefile">--memprofile=FILE</h3>
<p>Write memory profile to file. This can be analysed with <code>go tool pprof</code>.</p>
<h2 id="filtering">Filtering</h2>
<p>For the filtering options</p>
<ul>
<li><code>--delete-excluded</code></li>
<li><code>--filter</code></li>
<li><code>--filter-from</code></li>
<li><code>--exclude</code></li>
<li><code>--exclude-from</code></li>
<li><code>--exclude-if-present</code></li>
<li><code>--include</code></li>
<li><code>--include-from</code></li>
<li><code>--files-from</code></li>
<li><code>--files-from-raw</code></li>
<li><code>--min-size</code></li>
<li><code>--max-size</code></li>
<li><code>--min-age</code></li>
<li><code>--max-age</code></li>
<li><code>--dump filters</code></li>
<li><code>--metadata-include</code></li>
<li><code>--metadata-include-from</code></li>
<li><code>--metadata-exclude</code></li>
<li><code>--metadata-exclude-from</code></li>
<li><code>--metadata-filter</code></li>
<li><code>--metadata-filter-from</code></li>
</ul>
<p>See the <a href="https://rclone.org/filtering/">filtering section</a>.</p>
<h2 id="remote-control">Remote control</h2>
<p>For the remote control options and for instructions on how to remote control rclone</p>
<ul>
<li><code>--rc</code></li>
<li>and anything starting with <code>--rc-</code></li>
</ul>
<p>See <a href="https://rclone.org/rc/">the remote control section</a>.</p>
<h2 id="logging">Logging</h2>
<p>rclone has 4 levels of logging, <code>ERROR</code>, <code>NOTICE</code>, <code>INFO</code> and <code>DEBUG</code>.</p>
<p>By default, rclone logs to standard error. This means you can redirect standard error and still see the normal output of rclone commands (e.g. <code>rclone ls</code>).</p>
<p>By default, rclone will produce <code>Error</code> and <code>Notice</code> level messages.</p>
<p>If you use the <code>-q</code> flag, rclone will only produce <code>Error</code> messages.</p>
<p>If you use the <code>-v</code> flag, rclone will produce <code>Error</code>, <code>Notice</code> and <code>Info</code> messages.</p>
<p>If you use the <code>-vv</code> flag, rclone will produce <code>Error</code>, <code>Notice</code>, <code>Info</code> and <code>Debug</code> messages.</p>
<p>You can also control the log levels with the <code>--log-level</code> flag.</p>
<p>If you use the <code>--log-file=FILE</code> option, rclone will redirect <code>Error</code>, <code>Info</code> and <code>Debug</code> messages along with standard error to FILE.</p>
<p>If you use the <code>--syslog</code> flag then rclone will log to syslog and the <code>--syslog-facility</code> control which facility it uses.</p>
<p>Rclone prefixes all log messages with their level in capitals, e.g. INFO which makes it easy to grep the log file for different kinds of information.</p>
<h2 id="metrics">Metrics</h2>
<p>Rclone can publish metrics in the OpenMetrics/Prometheus format.</p>
<p>To enable the metrics endpoint, use the <code>--metrics-addr</code> flag. Metrics can also be published on the <code>--rc-addr</code> port if the <code>--rc</code> flag and <code>--rc-enable-metrics</code> flags are supplied or if using rclone rcd <code>--rc-enable-metrics</code></p>
<p>Rclone provides extensive configuration options for the metrics HTTP endpoint. These settings are grouped under the Metrics section and have a prefix <code>--metrics-*</code>.</p>
<p>When metrics are enabled with <code>--rc-enable-metrics</code>, they will be published on the same port as the rc API. In this case, the <code>--metrics-*</code> flags will be ignored, and the HTTP endpoint configuration will be managed by the <code>--rc-*</code> parameters.</p>
<h2 id="exit-code">Exit Code</h2>
<p>If any errors occur during the command execution, rclone will exit with a non-zero exit code. This allows scripts to detect when rclone operations have failed.</p>
<p>During the startup phase, rclone will exit immediately if an error is detected in the configuration. There will always be a log message immediately before exiting.</p>
<p>When rclone is running it will accumulate errors as it goes along, and only exit with a non-zero exit code if (after retries) there were still failed transfers. For every error counted there will be a high priority log message (visible with <code>-q</code>) showing the message and which file caused the problem. A high priority message is also shown when starting a retry so the user can see that any previous error messages may not be valid after the retry. If rclone has done a retry it will log a high priority message if the retry was successful.</p>
<h3 id="list-of-exit-codes">List of exit codes</h3>
<ul>
<li><code>0</code> - success</li>
<li><code>1</code> - Syntax or usage error</li>
<li><code>2</code> - Error not otherwise categorised</li>
<li><code>3</code> - Directory not found</li>
<li><code>4</code> - File not found</li>
<li><code>5</code> - Temporary error (one that more retries might fix) (Retry errors)</li>
<li><code>6</code> - Less serious errors (like 461 errors from dropbox) (NoRetry errors)</li>
<li><code>7</code> - Fatal error (one that more retries won't fix, like account suspended) (Fatal errors)</li>
<li><code>8</code> - Transfer exceeded - limit set by --max-transfer reached</li>
<li><code>9</code> - Operation successful, but no files transferred (Requires <a href="#error-on-no-transfer"><code>--error-on-no-transfer</code></a>)</li>
<li><code>10</code> - Duration exceeded - limit set by --max-duration reached</li>
</ul>
<h2 id="environment-variables">Environment Variables</h2>
<p>Rclone can be configured entirely using environment variables. These can be used to set defaults for options or config file entries.</p>
<h3 id="options-91">Options</h3>
<p>Every option in rclone can have its default set by environment variable.</p>
<p>To find the name of the environment variable, first, take the long option name, strip the leading <code>--</code>, change <code>-</code> to <code>_</code>, make upper case and prepend <code>RCLONE_</code>.</p>
<p>For example, to always set <code>--stats 5s</code>, set the environment variable <code>RCLONE_STATS=5s</code>. If you set stats on the command line this will override the environment variable setting.</p>
<p>Or to always use the trash in drive <code>--drive-use-trash</code>, set <code>RCLONE_DRIVE_USE_TRASH=true</code>.</p>
<p>Verbosity is slightly different, the environment variable equivalent of <code>--verbose</code> or <code>-v</code> is <code>RCLONE_VERBOSE=1</code>, or for <code>-vv</code>, <code>RCLONE_VERBOSE=2</code>.</p>
<p>The same parser is used for the options and the environment variables so they take exactly the same form.</p>
<p>The options set by environment variables can be seen with the <code>-vv</code> flag, e.g. <code>rclone version -vv</code>.</p>
<p>Options that can appear multiple times (type <code>stringArray</code>) are treated slighly differently as environment variables can only be defined once. In order to allow a simple mechanism for adding one or many items, the input is treated as a <a href="https://godoc.org/encoding/csv">CSV encoded</a> string. For example</p>
<table>
<colgroup>
<col style="width: 52%" />
<col style="width: 47%" />
</colgroup>
<thead>
<tr class="header">
<th>Environment Variable</th>
<th>Equivalent options</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td><code>RCLONE_EXCLUDE="*.jpg"</code></td>
<td><code>--exclude "*.jpg"</code></td>
</tr>
<tr class="even">
<td><code>RCLONE_EXCLUDE="*.jpg,*.png"</code></td>
<td><code>--exclude "*.jpg"</code> <code>--exclude "*.png"</code></td>
</tr>
<tr class="odd">
<td><code>RCLONE_EXCLUDE='"*.jpg","*.png"'</code></td>
<td><code>--exclude "*.jpg"</code> <code>--exclude "*.png"</code></td>
</tr>
<tr class="even">
<td><code>RCLONE_EXCLUDE='"/directory with comma , in it /**"'</code></td>
<td>`--exclude "/directory with comma , in it /**"</td>
</tr>
</tbody>
</table>
<p>If <code>stringArray</code> options are defined as environment variables <strong>and</strong> options on the command line then all the values will be used.</p>
<h3 id="config-file">Config file</h3>
<p>You can set defaults for values in the config file on an individual remote basis. The names of the config items are documented in the page for each backend.</p>
<p>To find the name of the environment variable, you need to set, take <code>RCLONE_CONFIG_</code> + name of remote + <code>_</code> + name of config file option and make it all uppercase. Note one implication here is the remote's name must be convertible into a valid environment variable name, so it can only contain letters, digits, or the <code>_</code> (underscore) character.</p>
<p>For example, to configure an S3 remote named <code>mys3:</code> without a config file (using unix ways of setting environment variables):</p>
<pre><code>$ export RCLONE_CONFIG_MYS3_TYPE=s3
$ export RCLONE_CONFIG_MYS3_ACCESS_KEY_ID=XXX
$ export RCLONE_CONFIG_MYS3_SECRET_ACCESS_KEY=XXX
$ rclone lsd mys3:
          -1 2016-09-21 12:54:21        -1 my-bucket
$ rclone listremotes | grep mys3
mys3:</code></pre>
<p>Note that if you want to create a remote using environment variables you must create the <code>..._TYPE</code> variable as above.</p>
<p>Note that the name of a remote created using environment variable is case insensitive, in contrast to regular remotes stored in config file as documented <a href="#valid-remote-names">above</a>. You must write the name in uppercase in the environment variable, but as seen from example above it will be listed and can be accessed in lowercase, while you can also refer to the same remote in uppercase:</p>
<pre><code>$ rclone lsd mys3:
          -1 2016-09-21 12:54:21        -1 my-bucket
$ rclone lsd MYS3:
          -1 2016-09-21 12:54:21        -1 my-bucket</code></pre>
<p>Note that you can only set the options of the immediate backend, so RCLONE_CONFIG_MYS3CRYPT_ACCESS_KEY_ID has no effect, if myS3Crypt is a crypt remote based on an S3 remote. However RCLONE_S3_ACCESS_KEY_ID will set the access key of all remotes using S3, including myS3Crypt.</p>
<p>Note also that now rclone has <a href="#connection-strings">connection strings</a>, it is probably easier to use those instead which makes the above example</p>
<pre><code>rclone lsd :s3,access_key_id=XXX,secret_access_key=XXX:</code></pre>
<h3 id="precedence">Precedence</h3>
<p>The various different methods of backend configuration are read in this order and the first one with a value is used.</p>
<ul>
<li>Parameters in connection strings, e.g. <code>myRemote,skip_links:</code></li>
<li>Flag values as supplied on the command line, e.g. <code>--skip-links</code></li>
<li>Remote specific environment vars, e.g. <code>RCLONE_CONFIG_MYREMOTE_SKIP_LINKS</code> (see above).</li>
<li>Backend-specific environment vars, e.g. <code>RCLONE_LOCAL_SKIP_LINKS</code>.</li>
<li>Backend generic environment vars, e.g. <code>RCLONE_SKIP_LINKS</code>.</li>
<li>Config file, e.g. <code>skip_links = true</code>.</li>
<li>Default values, e.g. <code>false</code> - these can't be changed.</li>
</ul>
<p>So if both <code>--skip-links</code> is supplied on the command line and an environment variable <code>RCLONE_LOCAL_SKIP_LINKS</code> is set, the command line flag will take preference.</p>
<p>The backend configurations set by environment variables can be seen with the <code>-vv</code> flag, e.g. <code>rclone about myRemote: -vv</code>.</p>
<p>For non backend configuration the order is as follows:</p>
<ul>
<li>Flag values as supplied on the command line, e.g. <code>--stats 5s</code>.</li>
<li>Environment vars, e.g. <code>RCLONE_STATS=5s</code>.</li>
<li>Default values, e.g. <code>1m</code> - these can't be changed.</li>
</ul>
<h3 id="other-environment-variables">Other environment variables</h3>
<ul>
<li><code>RCLONE_CONFIG_PASS</code> set to contain your config file password (see <a href="#configuration-encryption">Configuration Encryption</a> section)</li>
<li><code>HTTP_PROXY</code>, <code>HTTPS_PROXY</code> and <code>NO_PROXY</code> (or the lowercase versions thereof).
<ul>
<li><code>HTTPS_PROXY</code> takes precedence over <code>HTTP_PROXY</code> for https requests.</li>
<li>The environment values may be either a complete URL or a "host[:port]" for, in which case the "http" scheme is assumed.</li>
</ul></li>
<li><code>USER</code> and <code>LOGNAME</code> values are used as fallbacks for current username. The primary method for looking up username is OS-specific: Windows API on Windows, real user ID in /etc/passwd on Unix systems. In the documentation the current username is simply referred to as <code>$USER</code>.</li>
<li><code>RCLONE_CONFIG_DIR</code> - rclone <strong>sets</strong> this variable for use in config files and sub processes to point to the directory holding the config file.</li>
</ul>
<p>The options set by environment variables can be seen with the <code>-vv</code> and <code>--log-level=DEBUG</code> flags, e.g. <code>rclone version -vv</code>.</p>
<h1 id="configuring-rclone-on-a-remote-headless-machine">Configuring rclone on a remote / headless machine</h1>
<p>Some of the configurations (those involving oauth2) require an Internet connected web browser.</p>
<p>If you are trying to set rclone up on a remote or headless box with no browser available on it (e.g. a NAS or a server in a datacenter) then you will need to use an alternative means of configuration. There are two ways of doing it, described below.</p>
<h2 id="configuring-using-rclone-authorize">Configuring using rclone authorize</h2>
<p>On the headless box run <code>rclone</code> config but answer <code>N</code> to the <code>Use auto config?</code> question.</p>
<pre><code>Use auto config?
 * Say Y if not sure
 * Say N if you are working on a remote or headless machine

y) Yes (default)
n) No
y/n&gt; n

Option config_token.
For this to work, you will need rclone available on a machine that has
a web browser available.
For more help and alternate methods see: https://rclone.org/remote_setup/
Execute the following on the machine with the web browser (same rclone
version recommended):
    rclone authorize &quot;onedrive&quot;
Then paste the result.
Enter a value.
config_token&gt;</code></pre>
<p>Then on your main desktop machine</p>
<pre><code>rclone authorize &quot;onedrive&quot;
If your browser doesn&#39;t open automatically go to the following link: http://127.0.0.1:53682/auth
Log in and authorize rclone for access
Waiting for code...
Got code
Paste the following into your remote machine ---&gt;
SECRET_TOKEN
&lt;---End paste</code></pre>
<p>Then back to the headless box, paste in the code</p>
<pre><code>config_token&gt; SECRET_TOKEN
--------------------
[acd12]
client_id = 
client_secret = 
token = SECRET_TOKEN
--------------------
y) Yes this is OK
e) Edit this remote
d) Delete this remote
y/e/d&gt;</code></pre>
<h2 id="configuring-by-copying-the-config-file">Configuring by copying the config file</h2>
<p>Rclone stores all of its config in a single configuration file. This can easily be copied to configure a remote rclone.</p>
<p>So first configure rclone on your desktop machine with</p>
<pre><code>rclone config</code></pre>
<p>to set up the config file.</p>
<p>Find the config file by running <code>rclone config file</code>, for example</p>
<pre><code>$ rclone config file
Configuration file is stored at:
/home/user/.rclone.conf</code></pre>
<p>Now transfer it to the remote box (scp, cut paste, ftp, sftp, etc.) and place it in the correct place (use <code>rclone config file</code> on the remote box to find out where).</p>
<h2 id="configuring-using-ssh-tunnel">Configuring using SSH Tunnel</h2>
<p>Linux and MacOS users can utilize SSH Tunnel to redirect the headless box port 53682 to local machine by using the following command:</p>
<pre><code>ssh -L localhost:53682:localhost:53682 username@remote_server</code></pre>
<p>Then on the headless box run <code>rclone config</code> and answer <code>Y</code> to the <code>Use auto config?</code> question.</p>
<pre><code>Use auto config?
 * Say Y if not sure
 * Say N if you are working on a remote or headless machine

y) Yes (default)
n) No
y/n&gt; y</code></pre>
<p>Then copy and paste the auth url <code>http://127.0.0.1:53682/auth?state=xxxxxxxxxxxx</code> to the browser on your local machine, complete the auth and it is done.</p>
<h1 id="filtering-includes-and-excludes">Filtering, includes and excludes</h1>
<p>Filter flags determine which files rclone <code>sync</code>, <code>move</code>, <code>ls</code>, <code>lsl</code>, <code>md5sum</code>, <code>sha1sum</code>, <code>size</code>, <code>delete</code>, <code>check</code> and similar commands apply to.</p>
<p>They are specified in terms of path/file name patterns; path/file lists; file age and size, or presence of a file in a directory. Bucket based remotes without the concept of directory apply filters to object key, age and size in an analogous way.</p>
<p>Rclone <code>purge</code> does not obey filters.</p>
<p>To test filters without risk of damage to data, apply them to <code>rclone ls</code>, or with the <code>--dry-run</code> and <code>-vv</code> flags.</p>
<p>Rclone filter patterns can only be used in filter command line options, not in the specification of a remote.</p>
<p>E.g. <code>rclone copy "remote:dir*.jpg" /path/to/dir</code> does not have a filter effect. <code>rclone copy remote:dir /path/to/dir --include "*.jpg"</code> does.</p>
<p><strong>Important</strong> Avoid mixing any two of <code>--include...</code>, <code>--exclude...</code> or <code>--filter...</code> flags in an rclone command. The results might not be what you expect. Instead use a <code>--filter...</code> flag.</p>
<h2 id="patterns-for-matching-pathfile-names">Patterns for matching path/file names</h2>
<h3 id="patterns">Pattern syntax</h3>
<p>Here is a formal definition of the pattern syntax, <a href="#examples">examples</a> are below.</p>
<p>Rclone matching rules follow a glob style:</p>
<pre><code>*         matches any sequence of non-separator (/) characters
**        matches any sequence of characters including / separators
?         matches any single non-separator (/) character
[ [ ! ] { character-range } ]
          character class (must be non-empty)
{ pattern-list }
          pattern alternatives
{{ regexp }}
          regular expression to match
c         matches character c (c != *, **, ?, \, [, {, })
\c        matches reserved character c (c = *, **, ?, \, [, {, }) or character class</code></pre>
<p>character-range:</p>
<pre><code>c         matches character c (c != \, -, ])
\c        matches reserved character c (c = \, -, ])
lo - hi   matches character c for lo &lt;= c &lt;= hi</code></pre>
<p>pattern-list:</p>
<pre><code>pattern { , pattern }
          comma-separated (without spaces) patterns</code></pre>
<p>character classes (see <a href="https://golang.org/pkg/regexp/syntax/">Go regular expression reference</a>) include:</p>
<pre><code>Named character classes (e.g. [\d], [^\d], [\D], [^\D])
Perl character classes (e.g. \s, \S, \w, \W)
ASCII character classes (e.g. [[:alnum:]], [[:alpha:]], [[:punct:]], [[:xdigit:]])</code></pre>
<p>regexp for advanced users to insert a regular expression - see <a href="#regexp">below</a> for more info:</p>
<pre><code>Any re2 regular expression not containing `}}`</code></pre>
<p>If the filter pattern starts with a <code>/</code> then it only matches at the top level of the directory tree, <strong>relative to the root of the remote</strong> (not necessarily the root of the drive). If it does not start with <code>/</code> then it is matched starting at the <strong>end of the path/file name</strong> but it only matches a complete path element - it must match from a <code>/</code> separator or the beginning of the path/file.</p>
<pre><code>file.jpg   - matches &quot;file.jpg&quot;
           - matches &quot;directory/file.jpg&quot;
           - doesn&#39;t match &quot;afile.jpg&quot;
           - doesn&#39;t match &quot;directory/afile.jpg&quot;
/file.jpg  - matches &quot;file.jpg&quot; in the root directory of the remote
           - doesn&#39;t match &quot;afile.jpg&quot;
           - doesn&#39;t match &quot;directory/file.jpg&quot;</code></pre>
<p>The top level of the remote might not be the top level of the drive.</p>
<p>E.g. for a Microsoft Windows local directory structure</p>
<pre><code>F:
├── bkp
├── data
│   ├── excl
│   │   ├── 123.jpg
│   │   └── 456.jpg
│   ├── incl
│   │   └── document.pdf</code></pre>
<p>To copy the contents of folder <code>data</code> into folder <code>bkp</code> excluding the contents of subfolder <code>excl</code>the following command treats <code>F:\data</code> and <code>F:\bkp</code> as top level for filtering.</p>
<p><code>rclone copy F:\data\ F:\bkp\ --exclude=/excl/**</code></p>
<p><strong>Important</strong> Use <code>/</code> in path/file name patterns and not <code>\</code> even if running on Microsoft Windows.</p>
<p>Simple patterns are case sensitive unless the <code>--ignore-case</code> flag is used.</p>
<p>Without <code>--ignore-case</code> (default)</p>
<pre><code>potato - matches &quot;potato&quot;
       - doesn&#39;t match &quot;POTATO&quot;</code></pre>
<p>With <code>--ignore-case</code></p>
<pre><code>potato - matches &quot;potato&quot;
       - matches &quot;POTATO&quot;</code></pre>
<h2 id="regexp">Using regular expressions in filter patterns</h2>
<p>The syntax of filter patterns is glob style matching (like <code>bash</code> uses) to make things easy for users. However this does not provide absolute control over the matching, so for advanced users rclone also provides a regular expression syntax.</p>
<p>The regular expressions used are as defined in the <a href="https://golang.org/pkg/regexp/syntax/">Go regular expression reference</a>. Regular expressions should be enclosed in <code>{{</code> <code>}}</code>. They will match only the last path segment if the glob doesn't start with <code>/</code> or the whole path name if it does. Note that rclone does not attempt to parse the supplied regular expression, meaning that using any regular expression filter will prevent rclone from using <a href="#directory_filter">directory filter rules</a>, as it will instead check every path against the supplied regular expression(s).</p>
<p>Here is how the <code>{{regexp}}</code> is transformed into an full regular expression to match the entire path:</p>
<pre><code>{{regexp}}  becomes (^|/)(regexp)$
/{{regexp}} becomes ^(regexp)$</code></pre>
<p>Regexp syntax can be mixed with glob syntax, for example</p>
<pre><code>*.{{jpe?g}} to match file.jpg, file.jpeg but not file.png</code></pre>
<p>You can also use regexp flags - to set case insensitive, for example</p>
<pre><code>*.{{(?i)jpg}} to match file.jpg, file.JPG but not file.png</code></pre>
<p>Be careful with wildcards in regular expressions - you don't want them to match path separators normally. To match any file name starting with <code>start</code> and ending with <code>end</code> write</p>
<pre><code>{{start[^/]*end\.jpg}}</code></pre>
<p>Not</p>
<pre><code>{{start.*end\.jpg}}</code></pre>
<p>Which will match a directory called <code>start</code> with a file called <code>end.jpg</code> in it as the <code>.*</code> will match <code>/</code> characters.</p>
<p>Note that you can use <code>-vv --dump filters</code> to show the filter patterns in regexp format - rclone implements the glob patterns by transforming them into regular expressions.</p>
<h2 id="examples">Filter pattern examples</h2>
<table>
<thead>
<tr class="header">
<th>Description</th>
<th>Pattern</th>
<th>Matches</th>
<th>Does not match</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td>Wildcard</td>
<td><code>*.jpg</code></td>
<td><code>/file.jpg</code></td>
<td><code>/file.png</code></td>
</tr>
<tr class="even">
<td></td>
<td></td>
<td><code>/dir/file.jpg</code></td>
<td><code>/dir/file.png</code></td>
</tr>
<tr class="odd">
<td>Rooted</td>
<td><code>/*.jpg</code></td>
<td><code>/file.jpg</code></td>
<td><code>/file.png</code></td>
</tr>
<tr class="even">
<td></td>
<td></td>
<td><code>/file2.jpg</code></td>
<td><code>/dir/file.jpg</code></td>
</tr>
<tr class="odd">
<td>Alternates</td>
<td><code>*.{jpg,png}</code></td>
<td><code>/file.jpg</code></td>
<td><code>/file.gif</code></td>
</tr>
<tr class="even">
<td></td>
<td></td>
<td><code>/dir/file.png</code></td>
<td><code>/dir/file.gif</code></td>
</tr>
<tr class="odd">
<td>Path Wildcard</td>
<td><code>dir/**</code></td>
<td><code>/dir/anyfile</code></td>
<td><code>file.png</code></td>
</tr>
<tr class="even">
<td></td>
<td></td>
<td><code>/subdir/dir/subsubdir/anyfile</code></td>
<td><code>/subdir/file.png</code></td>
</tr>
<tr class="odd">
<td>Any Char</td>
<td><code>*.t?t</code></td>
<td><code>/file.txt</code></td>
<td><code>/file.qxt</code></td>
</tr>
<tr class="even">
<td></td>
<td></td>
<td><code>/dir/file.tzt</code></td>
<td><code>/dir/file.png</code></td>
</tr>
<tr class="odd">
<td>Range</td>
<td><code>*.[a-z]</code></td>
<td><code>/file.a</code></td>
<td><code>/file.0</code></td>
</tr>
<tr class="even">
<td></td>
<td></td>
<td><code>/dir/file.b</code></td>
<td><code>/dir/file.1</code></td>
</tr>
<tr class="odd">
<td>Escape</td>
<td><code>*.\?\?\?</code></td>
<td><code>/file.???</code></td>
<td><code>/file.abc</code></td>
</tr>
<tr class="even">
<td></td>
<td></td>
<td><code>/dir/file.???</code></td>
<td><code>/dir/file.def</code></td>
</tr>
<tr class="odd">
<td>Class</td>
<td><code>*.\d\d\d</code></td>
<td><code>/file.012</code></td>
<td><code>/file.abc</code></td>
</tr>
<tr class="even">
<td></td>
<td></td>
<td><code>/dir/file.345</code></td>
<td><code>/dir/file.def</code></td>
</tr>
<tr class="odd">
<td>Regexp</td>
<td><code>*.{{jpe?g}}</code></td>
<td><code>/file.jpeg</code></td>
<td><code>/file.png</code></td>
</tr>
<tr class="even">
<td></td>
<td></td>
<td><code>/dir/file.jpg</code></td>
<td><code>/dir/file.jpeeg</code></td>
</tr>
<tr class="odd">
<td>Rooted Regexp</td>
<td><code>/{{.*\.jpe?g}}</code></td>
<td><code>/file.jpeg</code></td>
<td><code>/file.png</code></td>
</tr>
<tr class="even">
<td></td>
<td></td>
<td><code>/file.jpg</code></td>
<td><code>/dir/file.jpg</code></td>
</tr>
</tbody>
</table>
<h2 id="how-filter-rules-work">How filter rules are applied to files</h2>
<p>Rclone path/file name filters are made up of one or more of the following flags:</p>
<ul>
<li><code>--include</code></li>
<li><code>--include-from</code></li>
<li><code>--exclude</code></li>
<li><code>--exclude-from</code></li>
<li><code>--filter</code></li>
<li><code>--filter-from</code></li>
</ul>
<p>There can be more than one instance of individual flags.</p>
<p>Rclone internally uses a combined list of all the include and exclude rules. The order in which rules are processed can influence the result of the filter.</p>
<p>All flags of the same type are processed together in the order above, regardless of what order the different types of flags are included on the command line.</p>
<p>Multiple instances of the same flag are processed from left to right according to their position in the command line.</p>
<p>To mix up the order of processing includes and excludes use <code>--filter...</code> flags.</p>
<p>Within <code>--include-from</code>, <code>--exclude-from</code> and <code>--filter-from</code> flags rules are processed from top to bottom of the referenced file.</p>
<p>If there is an <code>--include</code> or <code>--include-from</code> flag specified, rclone implies a <code>- **</code> rule which it adds to the bottom of the internal rule list. Specifying a <code>+</code> rule with a <code>--filter...</code> flag does not imply that rule.</p>
<p>Each path/file name passed through rclone is matched against the combined filter list. At first match to a rule the path/file name is included or excluded and no further filter rules are processed for that path/file.</p>
<p>If rclone does not find a match, after testing against all rules (including the implied rule if appropriate), the path/file name is included.</p>
<p>Any path/file included at that stage is processed by the rclone command.</p>
<p><code>--files-from</code> and <code>--files-from-raw</code> flags over-ride and cannot be combined with other filter options.</p>
<p>To see the internal combined rule list, in regular expression form, for a command add the <code>--dump filters</code> flag. Running an rclone command with <code>--dump filters</code> and <code>-vv</code> flags lists the internal filter elements and shows how they are applied to each source path/file. There is not currently a means provided to pass regular expression filter options into rclone directly though character class filter rules contain character classes. <a href="https://golang.org/pkg/regexp/syntax/">Go regular expression reference</a></p>
<h3 id="directory_filter">How filter rules are applied to directories</h3>
<p>Rclone commands are applied to path/file names not directories. The entire contents of a directory can be matched to a filter by the pattern <code>directory/*</code> or recursively by <code>directory/**</code>.</p>
<p>Directory filter rules are defined with a closing <code>/</code> separator.</p>
<p>E.g. <code>/directory/subdirectory/</code> is an rclone directory filter rule.</p>
<p>Rclone commands can use directory filter rules to determine whether they recurse into subdirectories. This potentially optimises access to a remote by avoiding listing unnecessary directories. Whether optimisation is desirable depends on the specific filter rules and source remote content.</p>
<p>If any <a href="#regexp">regular expression filters</a> are in use, then no directory recursion optimisation is possible, as rclone must check every path against the supplied regular expression(s).</p>
<p>Directory recursion optimisation occurs if either:</p>
<ul>
<li><p>A source remote does not support the rclone <code>ListR</code> primitive. local, sftp, Microsoft OneDrive and WebDAV do not support <code>ListR</code>. Google Drive and most bucket type storage do. <a href="https://rclone.org/overview/#optional-features">Full list</a></p></li>
<li><p>On other remotes (those that support <code>ListR</code>), if the rclone command is not naturally recursive, and provided it is not run with the <code>--fast-list</code> flag. <code>ls</code>, <code>lsf -R</code> and <code>size</code> are naturally recursive but <code>sync</code>, <code>copy</code> and <code>move</code> are not.</p></li>
<li><p>Whenever the <code>--disable ListR</code> flag is applied to an rclone command.</p></li>
</ul>
<p>Rclone commands imply directory filter rules from path/file filter rules. To view the directory filter rules rclone has implied for a command specify the <code>--dump filters</code> flag.</p>
<p>E.g. for an include rule</p>
<pre><code>/a/*.jpg</code></pre>
<p>Rclone implies the directory include rule</p>
<pre><code>/a/</code></pre>
<p>Directory filter rules specified in an rclone command can limit the scope of an rclone command but path/file filters still have to be specified.</p>
<p>E.g. <code>rclone ls remote: --include /directory/</code> will not match any files. Because it is an <code>--include</code> option the <code>--exclude **</code> rule is implied, and the <code>/directory/</code> pattern serves only to optimise access to the remote by ignoring everything outside of that directory.</p>
<p>E.g. <code>rclone ls remote: --filter-from filter-list.txt</code> with a file <code>filter-list.txt</code>:</p>
<pre><code>- /dir1/
- /dir2/
+ *.pdf
- **</code></pre>
<p>All files in directories <code>dir1</code> or <code>dir2</code> or their subdirectories are completely excluded from the listing. Only files of suffix <code>pdf</code> in the root of <code>remote:</code> or its subdirectories are listed. The <code>- **</code> rule prevents listing of any path/files not previously matched by the rules above.</p>
<p>Option <code>exclude-if-present</code> creates a directory exclude rule based on the presence of a file in a directory and takes precedence over other rclone directory filter rules.</p>
<p>When using pattern list syntax, if a pattern item contains either <code>/</code> or <code>**</code>, then rclone will not able to imply a directory filter rule from this pattern list.</p>
<p>E.g. for an include rule</p>
<pre><code>{dir1/**,dir2/**}</code></pre>
<p>Rclone will match files below directories <code>dir1</code> or <code>dir2</code> only, but will not be able to use this filter to exclude a directory <code>dir3</code> from being traversed.</p>
<p>Directory recursion optimisation may affect performance, but normally not the result. One exception to this is sync operations with option <code>--create-empty-src-dirs</code>, where any traversed empty directories will be created. With the pattern list example <code>{dir1/**,dir2/**}</code> above, this would create an empty directory <code>dir3</code> on destination (when it exists on source). Changing the filter to <code>{dir1,dir2}/**</code>, or splitting it into two include rules <code>--include dir1/** --include dir2/**</code>, will match the same files while also filtering directories, with the result that an empty directory <code>dir3</code> will no longer be created.</p>
<h3 id="exclude---exclude-files-matching-pattern"><code>--exclude</code> - Exclude files matching pattern</h3>
<p>Excludes path/file names from an rclone command based on a single exclude rule.</p>
<p>This flag can be repeated. See above for the order filter flags are processed in.</p>
<p><code>--exclude</code> should not be used with <code>--include</code>, <code>--include-from</code>, <code>--filter</code> or <code>--filter-from</code> flags.</p>
<p><code>--exclude</code> has no effect when combined with <code>--files-from</code> or <code>--files-from-raw</code> flags.</p>
<p>E.g. <code>rclone ls remote: --exclude *.bak</code> excludes all .bak files from listing.</p>
<p>E.g. <code>rclone size remote: --exclude "/dir/**"</code> returns the total size of all files on <code>remote:</code> excluding those in root directory <code>dir</code> and sub directories.</p>
<p>E.g. on Microsoft Windows <code>rclone ls remote: --exclude "*\[{JP,KR,HK}\]*"</code> lists the files in <code>remote:</code> without <code>[JP]</code> or <code>[KR]</code> or <code>[HK]</code> in their name. Quotes prevent the shell from interpreting the <code>\</code> characters.<code>\</code> characters escape the <code>[</code> and <code>]</code> so an rclone filter treats them literally rather than as a character-range. The <code>{</code> and <code>}</code> define an rclone pattern list. For other operating systems single quotes are required ie <code>rclone ls remote: --exclude '*\[{JP,KR,HK}\]*'</code></p>
<h3 id="exclude-from---read-exclude-patterns-from-file"><code>--exclude-from</code> - Read exclude patterns from file</h3>
<p>Excludes path/file names from an rclone command based on rules in a named file. The file contains a list of remarks and pattern rules.</p>
<p>For an example <code>exclude-file.txt</code>:</p>
<pre><code># a sample exclude rule file
*.bak
file2.jpg</code></pre>
<p><code>rclone ls remote: --exclude-from exclude-file.txt</code> lists the files on <code>remote:</code> except those named <code>file2.jpg</code> or with a suffix <code>.bak</code>. That is equivalent to <code>rclone ls remote: --exclude file2.jpg --exclude "*.bak"</code>.</p>
<p>This flag can be repeated. See above for the order filter flags are processed in.</p>
<p>The <code>--exclude-from</code> flag is useful where multiple exclude filter rules are applied to an rclone command.</p>
<p><code>--exclude-from</code> should not be used with <code>--include</code>, <code>--include-from</code>, <code>--filter</code> or <code>--filter-from</code> flags.</p>
<p><code>--exclude-from</code> has no effect when combined with <code>--files-from</code> or <code>--files-from-raw</code> flags.</p>
<p><code>--exclude-from</code> followed by <code>-</code> reads filter rules from standard input.</p>
<h3 id="include---include-files-matching-pattern"><code>--include</code> - Include files matching pattern</h3>
<p>Adds a single include rule based on path/file names to an rclone command.</p>
<p>This flag can be repeated. See above for the order filter flags are processed in.</p>
<p><code>--include</code> has no effect when combined with <code>--files-from</code> or <code>--files-from-raw</code> flags.</p>
<p><code>--include</code> implies <code>--exclude **</code> at the end of an rclone internal filter list. Therefore if you mix <code>--include</code> and <code>--include-from</code> flags with <code>--exclude</code>, <code>--exclude-from</code>, <code>--filter</code> or <code>--filter-from</code>, you must use include rules for all the files you want in the include statement. For more flexibility use the <code>--filter-from</code> flag.</p>
<p>E.g. <code>rclone ls remote: --include "*.{png,jpg}"</code> lists the files on <code>remote:</code> with suffix <code>.png</code> and <code>.jpg</code>. All other files are excluded.</p>
<p>E.g. multiple rclone copy commands can be combined with <code>--include</code> and a pattern-list.</p>
<pre><code>rclone copy /vol1/A remote:A
rclone copy /vol1/B remote:B</code></pre>
<p>is equivalent to:</p>
<pre><code>rclone copy /vol1 remote: --include &quot;{A,B}/**&quot;</code></pre>
<p>E.g. <code>rclone ls remote:/wheat --include "??[^[:punct:]]*"</code> lists the files <code>remote:</code> directory <code>wheat</code> (and subdirectories) whose third character is not punctuation. This example uses an <a href="https://golang.org/pkg/regexp/syntax/">ASCII character class</a>.</p>
<h3 id="include-from---read-include-patterns-from-file"><code>--include-from</code> - Read include patterns from file</h3>
<p>Adds path/file names to an rclone command based on rules in a named file. The file contains a list of remarks and pattern rules.</p>
<p>For an example <code>include-file.txt</code>:</p>
<pre><code># a sample include rule file
*.jpg
file2.avi</code></pre>
<p><code>rclone ls remote: --include-from include-file.txt</code> lists the files on <code>remote:</code> with name <code>file2.avi</code> or suffix <code>.jpg</code>. That is equivalent to <code>rclone ls remote: --include file2.avi --include "*.jpg"</code>.</p>
<p>This flag can be repeated. See above for the order filter flags are processed in.</p>
<p>The <code>--include-from</code> flag is useful where multiple include filter rules are applied to an rclone command.</p>
<p><code>--include-from</code> implies <code>--exclude **</code> at the end of an rclone internal filter list. Therefore if you mix <code>--include</code> and <code>--include-from</code> flags with <code>--exclude</code>, <code>--exclude-from</code>, <code>--filter</code> or <code>--filter-from</code>, you must use include rules for all the files you want in the include statement. For more flexibility use the <code>--filter-from</code> flag.</p>
<p><code>--exclude-from</code> has no effect when combined with <code>--files-from</code> or <code>--files-from-raw</code> flags.</p>
<p><code>--exclude-from</code> followed by <code>-</code> reads filter rules from standard input.</p>
<h3 id="filter---add-a-file-filtering-rule"><code>--filter</code> - Add a file-filtering rule</h3>
<p>Specifies path/file names to an rclone command, based on a single include or exclude rule, in <code>+</code> or <code>-</code> format.</p>
<p>This flag can be repeated. See above for the order filter flags are processed in.</p>
<p><code>--filter +</code> differs from <code>--include</code>. In the case of <code>--include</code> rclone implies an <code>--exclude *</code> rule which it adds to the bottom of the internal rule list. <code>--filter...+</code> does not imply that rule.</p>
<p><code>--filter</code> has no effect when combined with <code>--files-from</code> or <code>--files-from-raw</code> flags.</p>
<p><code>--filter</code> should not be used with <code>--include</code>, <code>--include-from</code>, <code>--exclude</code> or <code>--exclude-from</code> flags.</p>
<p>E.g. <code>rclone ls remote: --filter "- *.bak"</code> excludes all <code>.bak</code> files from a list of <code>remote:</code>.</p>
<h3 id="filter-from---read-filtering-patterns-from-a-file"><code>--filter-from</code> - Read filtering patterns from a file</h3>
<p>Adds path/file names to an rclone command based on rules in a named file. The file contains a list of remarks and pattern rules. Include rules start with <code>+</code> and exclude rules with <code>-</code>. <code>!</code> clears existing rules. Rules are processed in the order they are defined.</p>
<p>This flag can be repeated. See above for the order filter flags are processed in.</p>
<p>Arrange the order of filter rules with the most restrictive first and work down.</p>
<p>Lines starting with # or ; are ignored, and can be used to write comments. Inline comments are not supported. <em>Use <code>-vv --dump filters</code> to see how they appear in the final regexp.</em></p>
<p>E.g. for <code>filter-file.txt</code>:</p>
<pre><code># a sample filter rule file
- secret*.jpg
+ *.jpg
+ *.png
+ file2.avi
- /dir/tmp/** # WARNING! This text will be treated as part of the path.
- /dir/Trash/**
+ /dir/**
# exclude everything else
- *</code></pre>
<p><code>rclone ls remote: --filter-from filter-file.txt</code> lists the path/files on <code>remote:</code> including all <code>jpg</code> and <code>png</code> files, excluding any matching <code>secret*.jpg</code> and including <code>file2.avi</code>. It also includes everything in the directory <code>dir</code> at the root of <code>remote</code>, except <code>remote:dir/Trash</code> which it excludes. Everything else is excluded.</p>
<p>E.g. for an alternative <code>filter-file.txt</code>:</p>
<pre><code>- secret*.jpg
+ *.jpg
+ *.png
+ file2.avi
- *</code></pre>
<p>Files <code>file1.jpg</code>, <code>file3.png</code> and <code>file2.avi</code> are listed whilst <code>secret17.jpg</code> and files without the suffix <code>.jpg</code> or <code>.png</code> are excluded.</p>
<p>E.g. for an alternative <code>filter-file.txt</code>:</p>
<pre><code>+ *.jpg
+ *.gif
!
+ 42.doc
- *</code></pre>
<p>Only file 42.doc is listed. Prior rules are cleared by the <code>!</code>.</p>
<h3 id="files-from---read-list-of-source-file-names"><code>--files-from</code> - Read list of source-file names</h3>
<p>Adds path/files to an rclone command from a list in a named file. Rclone processes the path/file names in the order of the list, and no others.</p>
<p>Other filter flags (<code>--include</code>, <code>--include-from</code>, <code>--exclude</code>, <code>--exclude-from</code>, <code>--filter</code> and <code>--filter-from</code>) are ignored when <code>--files-from</code> is used.</p>
<p><code>--files-from</code> expects a list of files as its input. Leading or trailing whitespace is stripped from the input lines. Lines starting with <code>#</code> or <code>;</code> are ignored.</p>
<p>Rclone commands with a <code>--files-from</code> flag traverse the remote, treating the names in <code>--files-from</code> as a set of filters.</p>
<p>If the <code>--no-traverse</code> and <code>--files-from</code> flags are used together an rclone command does not traverse the remote. Instead it addresses each path/file named in the file individually. For each path/file name, that requires typically 1 API call. This can be efficient for a short <code>--files-from</code> list and a remote containing many files.</p>
<p>Rclone commands do not error if any names in the <code>--files-from</code> file are missing from the source remote.</p>
<p>The <code>--files-from</code> flag can be repeated in a single rclone command to read path/file names from more than one file. The files are read from left to right along the command line.</p>
<p>Paths within the <code>--files-from</code> file are interpreted as starting with the root specified in the rclone command. Leading <code>/</code> separators are ignored. See <a href="#files-from-raw-read-list-of-source-file-names-without-any-processing">--files-from-raw</a> if you need the input to be processed in a raw manner.</p>
<p>E.g. for a file <code>files-from.txt</code>:</p>
<pre><code># comment
file1.jpg
subdir/file2.jpg</code></pre>
<p><code>rclone copy --files-from files-from.txt /home/me/pics remote:pics</code> copies the following, if they exist, and only those files.</p>
<pre><code>/home/me/pics/file1.jpg        → remote:pics/file1.jpg
/home/me/pics/subdir/file2.jpg → remote:pics/subdir/file2.jpg</code></pre>
<p>E.g. to copy the following files referenced by their absolute paths:</p>
<pre><code>/home/user1/42
/home/user1/dir/ford
/home/user2/prefect</code></pre>
<p>First find a common subdirectory - in this case <code>/home</code> and put the remaining files in <code>files-from.txt</code> with or without leading <code>/</code>, e.g.</p>
<pre><code>user1/42
user1/dir/ford
user2/prefect</code></pre>
<p>Then copy these to a remote:</p>
<pre><code>rclone copy --files-from files-from.txt /home remote:backup</code></pre>
<p>The three files are transferred as follows:</p>
<pre><code>/home/user1/42       → remote:backup/user1/important
/home/user1/dir/ford → remote:backup/user1/dir/file
/home/user2/prefect  → remote:backup/user2/stuff</code></pre>
<p>Alternatively if <code>/</code> is chosen as root <code>files-from.txt</code> will be:</p>
<pre><code>/home/user1/42
/home/user1/dir/ford
/home/user2/prefect</code></pre>
<p>The copy command will be:</p>
<pre><code>rclone copy --files-from files-from.txt / remote:backup</code></pre>
<p>Then there will be an extra <code>home</code> directory on the remote:</p>
<pre><code>/home/user1/42       → remote:backup/home/user1/42
/home/user1/dir/ford → remote:backup/home/user1/dir/ford
/home/user2/prefect  → remote:backup/home/user2/prefect</code></pre>
<h3 id="files-from-raw---read-list-of-source-file-names-without-any-processing"><code>--files-from-raw</code> - Read list of source-file names without any processing</h3>
<p>This flag is the same as <code>--files-from</code> except that input is read in a raw manner. Lines with leading / trailing whitespace, and lines starting with <code>;</code> or <code>#</code> are read without any processing. <a href="https://rclone.org/commands/rclone_lsf/">rclone lsf</a> has a compatible format that can be used to export file lists from remotes for input to <code>--files-from-raw</code>.</p>
<h3 id="ignore-case---make-searches-case-insensitive"><code>--ignore-case</code> - make searches case insensitive</h3>
<p>By default, rclone filter patterns are case sensitive. The <code>--ignore-case</code> flag makes all of the filters patterns on the command line case insensitive.</p>
<p>E.g. <code>--include "zaphod.txt"</code> does not match a file <code>Zaphod.txt</code>. With <code>--ignore-case</code> a match is made.</p>
<h2 id="quoting-shell-metacharacters">Quoting shell metacharacters</h2>
<p>Rclone commands with filter patterns containing shell metacharacters may not as work as expected in your shell and may require quoting.</p>
<p>E.g. linux, OSX (<code>*</code> metacharacter)</p>
<ul>
<li><code>--include \*.jpg</code></li>
<li><code>--include '*.jpg'</code></li>
<li><code>--include='*.jpg'</code></li>
</ul>
<p>Microsoft Windows expansion is done by the command, not shell, so <code>--include *.jpg</code> does not require quoting.</p>
<p>If the rclone error <code>Command .... needs .... arguments maximum: you provided .... non flag arguments:</code> is encountered, the cause is commonly spaces within the name of a remote or flag value. The fix then is to quote values containing spaces.</p>
<h2 id="other-filters">Other filters</h2>
<h3 id="min-size---dont-transfer-any-file-smaller-than-this"><code>--min-size</code> - Don't transfer any file smaller than this</h3>
<p>Controls the minimum size file within the scope of an rclone command. Default units are <code>KiB</code> but abbreviations <code>B</code>, <code>K</code>, <code>M</code>, <code>G</code>, <code>T</code> or <code>P</code> are valid.</p>
<p>E.g. <code>rclone ls remote: --min-size 50k</code> lists files on <code>remote:</code> of 50 KiB size or larger.</p>
<p>See <a href="https://rclone.org/docs/#size-option">the size option docs</a> for more info.</p>
<h3 id="max-size---dont-transfer-any-file-larger-than-this"><code>--max-size</code> - Don't transfer any file larger than this</h3>
<p>Controls the maximum size file within the scope of an rclone command. Default units are <code>KiB</code> but abbreviations <code>B</code>, <code>K</code>, <code>M</code>, <code>G</code>, <code>T</code> or <code>P</code> are valid.</p>
<p>E.g. <code>rclone ls remote: --max-size 1G</code> lists files on <code>remote:</code> of 1 GiB size or smaller.</p>
<p>See <a href="https://rclone.org/docs/#size-option">the size option docs</a> for more info.</p>
<h3 id="max-age---dont-transfer-any-file-older-than-this"><code>--max-age</code> - Don't transfer any file older than this</h3>
<p>Controls the maximum age of files within the scope of an rclone command.</p>
<p><code>--max-age</code> applies only to files and not to directories.</p>
<p>E.g. <code>rclone ls remote: --max-age 2d</code> lists files on <code>remote:</code> of 2 days old or less.</p>
<p>See <a href="https://rclone.org/docs/#time-option">the time option docs</a> for valid formats.</p>
<h3 id="min-age---dont-transfer-any-file-younger-than-this"><code>--min-age</code> - Don't transfer any file younger than this</h3>
<p>Controls the minimum age of files within the scope of an rclone command. (see <code>--max-age</code> for valid formats)</p>
<p><code>--min-age</code> applies only to files and not to directories.</p>
<p>E.g. <code>rclone ls remote: --min-age 2d</code> lists files on <code>remote:</code> of 2 days old or more.</p>
<p>See <a href="https://rclone.org/docs/#time-option">the time option docs</a> for valid formats.</p>
<h2 id="other-flags">Other flags</h2>
<h3 id="delete-excluded---delete-files-on-dest-excluded-from-sync"><code>--delete-excluded</code> - Delete files on dest excluded from sync</h3>
<p><strong>Important</strong> this flag is dangerous to your data - use with <code>--dry-run</code> and <code>-v</code> first.</p>
<p>In conjunction with <code>rclone sync</code>, <code>--delete-excluded</code> deletes any files on the destination which are excluded from the command.</p>
<p>E.g. the scope of <code>rclone sync --interactive A: B:</code> can be restricted:</p>
<pre><code>rclone --min-size 50k --delete-excluded sync A: B:</code></pre>
<p>All files on <code>B:</code> which are less than 50 KiB are deleted because they are excluded from the rclone sync command.</p>
<h3 id="dump-filters---dump-the-filters-to-the-output"><code>--dump filters</code> - dump the filters to the output</h3>
<p>Dumps the defined filters to standard output in regular expression format.</p>
<p>Useful for debugging.</p>
<h2 id="exclude-directory-based-on-a-file">Exclude directory based on a file</h2>
<p>The <code>--exclude-if-present</code> flag controls whether a directory is within the scope of an rclone command based on the presence of a named file within it. The flag can be repeated to check for multiple file names, presence of any of them will exclude the directory.</p>
<p>This flag has a priority over other filter flags.</p>
<p>E.g. for the following directory structure:</p>
<pre><code>dir1/file1
dir1/dir2/file2
dir1/dir2/dir3/file3
dir1/dir2/dir3/.ignore</code></pre>
<p>The command <code>rclone ls --exclude-if-present .ignore dir1</code> does not list <code>dir3</code>, <code>file3</code> or <code>.ignore</code>.</p>
<h2 id="metadata">Metadata filters</h2>
<p>The metadata filters work in a very similar way to the normal file name filters, except they match <a href="https://rclone.org/docs/#metadata">metadata</a> on the object.</p>
<p>The metadata should be specified as <code>key=value</code> patterns. This may be wildcarded using the normal <a href="#patterns">filter patterns</a> or <a href="#regexp">regular expressions</a>.</p>
<p>For example if you wished to list only local files with a mode of <code>100664</code> you could do that with:</p>
<pre><code>rclone lsf -M --files-only --metadata-include &quot;mode=100664&quot; .</code></pre>
<p>Or if you wished to show files with an <code>atime</code>, <code>mtime</code> or <code>btime</code> at a given date:</p>
<pre><code>rclone lsf -M --files-only --metadata-include &quot;[abm]time=2022-12-16*&quot; .</code></pre>
<p>Like file filtering, metadata filtering only applies to files not to directories.</p>
<p>The filters can be applied using these flags.</p>
<ul>
<li><code>--metadata-include</code> - Include metadatas matching pattern</li>
<li><code>--metadata-include-from</code> - Read metadata include patterns from file (use - to read from stdin)</li>
<li><code>--metadata-exclude</code> - Exclude metadatas matching pattern</li>
<li><code>--metadata-exclude-from</code> - Read metadata exclude patterns from file (use - to read from stdin)</li>
<li><code>--metadata-filter</code> - Add a metadata filtering rule</li>
<li><code>--metadata-filter-from</code> - Read metadata filtering patterns from a file (use - to read from stdin)</li>
</ul>
<p>Each flag can be repeated. See the section on <a href="#how-filter-rules-work">how filter rules are applied</a> for more details - these flags work in an identical way to the file name filtering flags, but instead of file name patterns have metadata patterns.</p>
<h2 id="common-pitfalls">Common pitfalls</h2>
<p>The most frequent filter support issues on the <a href="https://forum.rclone.org/">rclone forum</a> are:</p>
<ul>
<li>Not using paths relative to the root of the remote</li>
<li>Not using <code>/</code> to match from the root of a remote</li>
<li>Not using <code>**</code> to match the contents of a directory</li>
</ul>
<h1 id="gui-experimental">GUI (Experimental)</h1>
<p>Rclone can serve a web based GUI (graphical user interface). This is somewhat experimental at the moment so things may be subject to change.</p>
<p>Run this command in a terminal and rclone will download and then display the GUI in a web browser.</p>
<pre><code>rclone rcd --rc-web-gui</code></pre>
<p>This will produce logs like this and rclone needs to continue to run to serve the GUI:</p>
<pre><code>2019/08/25 11:40:14 NOTICE: A new release for gui is present at https://github.com/rclone/rclone-webui-react/releases/download/v0.0.6/currentbuild.zip
2019/08/25 11:40:14 NOTICE: Downloading webgui binary. Please wait. [Size: 3813937, Path :  /home/USER/.cache/rclone/webgui/v0.0.6.zip]
2019/08/25 11:40:16 NOTICE: Unzipping
2019/08/25 11:40:16 NOTICE: Serving remote control on http://127.0.0.1:5572/</code></pre>
<p>This assumes you are running rclone locally on your machine. It is possible to separate the rclone and the GUI - see below for details.</p>
<p>If you wish to check for updates then you can add <code>--rc-web-gui-update</code> to the command line.</p>
<p>If you find your GUI broken, you may force it to update by add <code>--rc-web-gui-force-update</code>.</p>
<p>By default, rclone will open your browser. Add <code>--rc-web-gui-no-open-browser</code> to disable this feature.</p>
<h2 id="using-the-gui">Using the GUI</h2>
<p>Once the GUI opens, you will be looking at the dashboard which has an overall overview.</p>
<p>On the left hand side you will see a series of view buttons you can click on:</p>
<ul>
<li>Dashboard - main overview</li>
<li>Configs - examine and create new configurations</li>
<li>Explorer - view, download and upload files to the cloud storage systems</li>
<li>Backend - view or alter the backend config</li>
<li>Log out</li>
</ul>
<p>(More docs and walkthrough video to come!)</p>
<h2 id="how-it-works">How it works</h2>
<p>When you run the <code>rclone rcd --rc-web-gui</code> this is what happens</p>
<ul>
<li>Rclone starts but only runs the remote control API ("rc").</li>
<li>The API is bound to localhost with an auto-generated username and password.</li>
<li>If the API bundle is missing then rclone will download it.</li>
<li>rclone will start serving the files from the API bundle over the same port as the API</li>
<li>rclone will open the browser with a <code>login_token</code> so it can log straight in.</li>
</ul>
<h2 id="advanced-use">Advanced use</h2>
<p>The <code>rclone rcd</code> may use any of the <a href="https://rclone.org/rc/#supported-parameters">flags documented on the rc page</a>.</p>
<p>The flag <code>--rc-web-gui</code> is shorthand for</p>
<ul>
<li>Download the web GUI if necessary</li>
<li>Check we are using some authentication</li>
<li><code>--rc-user gui</code></li>
<li><code>--rc-pass &lt;random password&gt;</code></li>
<li><code>--rc-serve</code></li>
</ul>
<p>These flags can be overridden as desired.</p>
<p>See also the <a href="https://rclone.org/commands/rclone_rcd/">rclone rcd documentation</a>.</p>
<h3 id="example-running-a-public-gui">Example: Running a public GUI</h3>
<p>For example the GUI could be served on a public port over SSL using an htpasswd file using the following flags:</p>
<ul>
<li><code>--rc-web-gui</code></li>
<li><code>--rc-addr :443</code></li>
<li><code>--rc-htpasswd /path/to/htpasswd</code></li>
<li><code>--rc-cert /path/to/ssl.crt</code></li>
<li><code>--rc-key /path/to/ssl.key</code></li>
</ul>
<h3 id="example-running-a-gui-behind-a-proxy">Example: Running a GUI behind a proxy</h3>
<p>If you want to run the GUI behind a proxy at <code>/rclone</code> you could use these flags:</p>
<ul>
<li><code>--rc-web-gui</code></li>
<li><code>--rc-baseurl rclone</code></li>
<li><code>--rc-htpasswd /path/to/htpasswd</code></li>
</ul>
<p>Or instead of htpasswd if you just want a single user and password:</p>
<ul>
<li><code>--rc-user me</code></li>
<li><code>--rc-pass mypassword</code></li>
</ul>
<h2 id="project">Project</h2>
<p>The GUI is being developed in the: <a href="https://github.com/rclone/rclone-webui-react">rclone/rclone-webui-react repository</a>.</p>
<p>Bug reports and contributions are very welcome :-)</p>
<p>If you have questions then please ask them on the <a href="https://forum.rclone.org/">rclone forum</a>.</p>
<h1 id="remote-controlling-rclone-with-its-api">Remote controlling rclone with its API</h1>
<p>If rclone is run with the <code>--rc</code> flag then it starts an HTTP server which can be used to remote control rclone using its API.</p>
<p>You can either use the <a href="#api-rc">rc</a> command to access the API or <a href="#api-http">use HTTP directly</a>.</p>
<p>If you just want to run a remote control then see the <a href="https://rclone.org/commands/rclone_rcd/">rcd</a> command.</p>
<h2 id="supported-parameters">Supported parameters</h2>
<h3 id="rc">--rc</h3>
<p>Flag to start the http server listen on remote requests</p>
<h3 id="rc-addrip">--rc-addr=IP</h3>
<p>IPaddress:Port or :Port to bind server to. (default "localhost:5572")</p>
<h3 id="rc-certkey">--rc-cert=KEY</h3>
<p>SSL PEM key (concatenation of certificate and CA certificate)</p>
<h3 id="rc-client-capath">--rc-client-ca=PATH</h3>
<p>Client certificate authority to verify clients with</p>
<h3 id="rc-htpasswdpath">--rc-htpasswd=PATH</h3>
<p>htpasswd file - if not provided no authentication is done</p>
<h3 id="rc-keypath">--rc-key=PATH</h3>
<p>SSL PEM Private key</p>
<h3 id="rc-max-header-bytesvalue">--rc-max-header-bytes=VALUE</h3>
<p>Maximum size of request header (default 4096)</p>
<h3 id="rc-min-tls-versionvalue">--rc-min-tls-version=VALUE</h3>
<p>The minimum TLS version that is acceptable. Valid values are "tls1.0", "tls1.1", "tls1.2" and "tls1.3" (default "tls1.0").</p>
<h3 id="rc-uservalue">--rc-user=VALUE</h3>
<p>User name for authentication.</p>
<h3 id="rc-passvalue">--rc-pass=VALUE</h3>
<p>Password for authentication.</p>
<h3 id="rc-realmvalue">--rc-realm=VALUE</h3>
<p>Realm for authentication (default "rclone")</p>
<h3 id="rc-server-read-timeoutduration">--rc-server-read-timeout=DURATION</h3>
<p>Timeout for server reading data (default 1h0m0s)</p>
<h3 id="rc-server-write-timeoutduration">--rc-server-write-timeout=DURATION</h3>
<p>Timeout for server writing data (default 1h0m0s)</p>
<h3 id="rc-serve">--rc-serve</h3>
<p>Enable the serving of remote objects via the HTTP interface. This means objects will be accessible at http://127.0.0.1:5572/ by default, so you can browse to http://127.0.0.1:5572/ or http://127.0.0.1:5572/* to see a listing of the remotes. Objects may be requested from remotes using this syntax http://127.0.0.1:5572/[remote:path]/path/to/object</p>
<p>Default Off.</p>
<h3 id="rc-serve-no-modtime">--rc-serve-no-modtime</h3>
<p>Set this flag to skip reading the modification time (can speed things up).</p>
<p>Default Off.</p>
<h3 id="rc-files-pathtodirectory">--rc-files /path/to/directory</h3>
<p>Path to local files to serve on the HTTP server.</p>
<p>If this is set then rclone will serve the files in that directory. It will also open the root in the web browser if specified. This is for implementing browser based GUIs for rclone functions.</p>
<p>If <code>--rc-user</code> or <code>--rc-pass</code> is set then the URL that is opened will have the authorization in the URL in the <code>http://user:pass@localhost/</code> style.</p>
<p>Default Off.</p>
<h3 id="rc-enable-metrics">--rc-enable-metrics</h3>
<p>Enable OpenMetrics/Prometheus compatible endpoint at <code>/metrics</code>. If more control over the metrics is desired (for example running it on a different port or with different auth) then endpoint can be enabled with the <code>--metrics-*</code> flags instead.</p>
<p>Default Off.</p>
<h3 id="rc-web-gui">--rc-web-gui</h3>
<p>Set this flag to serve the default web gui on the same port as rclone.</p>
<p>Default Off.</p>
<h3 id="rc-allow-origin">--rc-allow-origin</h3>
<p>Set the allowed Access-Control-Allow-Origin for rc requests.</p>
<p>Can be used with --rc-web-gui if the rclone is running on different IP than the web-gui.</p>
<p>Default is IP address on which rc is running.</p>
<h3 id="rc-web-fetch-url">--rc-web-fetch-url</h3>
<p>Set the URL to fetch the rclone-web-gui files from.</p>
<p>Default https://api.github.com/repos/rclone/rclone-webui-react/releases/latest.</p>
<h3 id="rc-web-gui-update">--rc-web-gui-update</h3>
<p>Set this flag to check and update rclone-webui-react from the rc-web-fetch-url.</p>
<p>Default Off.</p>
<h3 id="rc-web-gui-force-update">--rc-web-gui-force-update</h3>
<p>Set this flag to force update rclone-webui-react from the rc-web-fetch-url.</p>
<p>Default Off.</p>
<h3 id="rc-web-gui-no-open-browser">--rc-web-gui-no-open-browser</h3>
<p>Set this flag to disable opening browser automatically when using web-gui.</p>
<p>Default Off.</p>
<h3 id="rc-job-expire-durationduration">--rc-job-expire-duration=DURATION</h3>
<p>Expire finished async jobs older than DURATION (default 60s).</p>
<h3 id="rc-job-expire-intervalduration">--rc-job-expire-interval=DURATION</h3>
<p>Interval duration to check for expired async jobs (default 10s).</p>
<h3 id="rc-no-auth">--rc-no-auth</h3>
<p>By default rclone will require authorisation to have been set up on the rc interface in order to use any methods which access any rclone remotes. Eg <code>operations/list</code> is denied as it involved creating a remote as is <code>sync/copy</code>.</p>
<p>If this is set then no authorisation will be required on the server to use these methods. The alternative is to use <code>--rc-user</code> and <code>--rc-pass</code> and use these credentials in the request.</p>
<p>Default Off.</p>
<h3 id="rc-baseurl">--rc-baseurl</h3>
<p>Prefix for URLs.</p>
<p>Default is root</p>
<h3 id="rc-template">--rc-template</h3>
<p>User-specified template.</p>
<h2 id="api-rc">Accessing the remote control via the rclone rc command</h2>
<p>Rclone itself implements the remote control protocol in its <code>rclone rc</code> command.</p>
<p>You can use it like this</p>
<pre><code>$ rclone rc rc/noop param1=one param2=two
{
    &quot;param1&quot;: &quot;one&quot;,
    &quot;param2&quot;: &quot;two&quot;
}</code></pre>
<p>Run <code>rclone rc</code> on its own to see the help for the installed remote control commands.</p>
<h2 id="json-input">JSON input</h2>
<p><code>rclone rc</code> also supports a <code>--json</code> flag which can be used to send more complicated input parameters.</p>
<pre><code>$ rclone rc --json &#39;{ &quot;p1&quot;: [1,&quot;2&quot;,null,4], &quot;p2&quot;: { &quot;a&quot;:1, &quot;b&quot;:2 } }&#39; rc/noop
{
    &quot;p1&quot;: [
        1,
        &quot;2&quot;,
        null,
        4
    ],
    &quot;p2&quot;: {
        &quot;a&quot;: 1,
        &quot;b&quot;: 2
    }
}</code></pre>
<p>If the parameter being passed is an object then it can be passed as a JSON string rather than using the <code>--json</code> flag which simplifies the command line.</p>
<pre><code>rclone rc operations/list fs=/tmp remote=test opt=&#39;{&quot;showHash&quot;: true}&#39;</code></pre>
<p>Rather than</p>
<pre><code>rclone rc operations/list --json &#39;{&quot;fs&quot;: &quot;/tmp&quot;, &quot;remote&quot;: &quot;test&quot;, &quot;opt&quot;: {&quot;showHash&quot;: true}}&#39;</code></pre>
<h2 id="special-parameters">Special parameters</h2>
<p>The rc interface supports some special parameters which apply to <strong>all</strong> commands. These start with <code>_</code> to show they are different.</p>
<h3 id="running-asynchronous-jobs-with-_async-true">Running asynchronous jobs with _async = true</h3>
<p>Each rc call is classified as a job and it is assigned its own id. By default jobs are executed immediately as they are created or synchronously.</p>
<p>If <code>_async</code> has a true value when supplied to an rc call then it will return immediately with a job id and the task will be run in the background. The <code>job/status</code> call can be used to get information of the background job. The job can be queried for up to 1 minute after it has finished.</p>
<p>It is recommended that potentially long running jobs, e.g. <code>sync/sync</code>, <code>sync/copy</code>, <code>sync/move</code>, <code>operations/purge</code> are run with the <code>_async</code> flag to avoid any potential problems with the HTTP request and response timing out.</p>
<p>Starting a job with the <code>_async</code> flag:</p>
<pre><code>$ rclone rc --json &#39;{ &quot;p1&quot;: [1,&quot;2&quot;,null,4], &quot;p2&quot;: { &quot;a&quot;:1, &quot;b&quot;:2 }, &quot;_async&quot;: true }&#39; rc/noop
{
    &quot;jobid&quot;: 2
}</code></pre>
<p>Query the status to see if the job has finished. For more information on the meaning of these return parameters see the <code>job/status</code> call.</p>
<pre><code>$ rclone rc --json &#39;{ &quot;jobid&quot;:2 }&#39; job/status
{
    &quot;duration&quot;: 0.000124163,
    &quot;endTime&quot;: &quot;2018-10-27T11:38:07.911245881+01:00&quot;,
    &quot;error&quot;: &quot;&quot;,
    &quot;finished&quot;: true,
    &quot;id&quot;: 2,
    &quot;output&quot;: {
        &quot;_async&quot;: true,
        &quot;p1&quot;: [
            1,
            &quot;2&quot;,
            null,
            4
        ],
        &quot;p2&quot;: {
            &quot;a&quot;: 1,
            &quot;b&quot;: 2
        }
    },
    &quot;startTime&quot;: &quot;2018-10-27T11:38:07.911121728+01:00&quot;,
    &quot;success&quot;: true
}</code></pre>
<p><code>job/list</code> can be used to show the running or recently completed jobs</p>
<pre><code>$ rclone rc job/list
{
    &quot;jobids&quot;: [
        2
    ]
}</code></pre>
<h3 id="setting-config-flags-with-_config">Setting config flags with _config</h3>
<p>If you wish to set config (the equivalent of the global flags) for the duration of an rc call only then pass in the <code>_config</code> parameter.</p>
<p>This should be in the same format as the <code>config</code> key returned by <a href="#options-get">options/get</a>.</p>
<p>For example, if you wished to run a sync with the <code>--checksum</code> parameter, you would pass this parameter in your JSON blob.</p>
<pre><code>&quot;_config&quot;:{&quot;CheckSum&quot;: true}</code></pre>
<p>If using <code>rclone rc</code> this could be passed as</p>
<pre><code>rclone rc sync/sync ... _config=&#39;{&quot;CheckSum&quot;: true}&#39;</code></pre>
<p>Any config parameters you don't set will inherit the global defaults which were set with command line flags or environment variables.</p>
<p>Note that it is possible to set some values as strings or integers - see <a href="#data-types">data types</a> for more info. Here is an example setting the equivalent of <code>--buffer-size</code> in string or integer format.</p>
<pre><code>&quot;_config&quot;:{&quot;BufferSize&quot;: &quot;42M&quot;}
&quot;_config&quot;:{&quot;BufferSize&quot;: 44040192}</code></pre>
<p>If you wish to check the <code>_config</code> assignment has worked properly then calling <code>options/local</code> will show what the value got set to.</p>
<h3 id="setting-filter-flags-with-_filter">Setting filter flags with _filter</h3>
<p>If you wish to set filters for the duration of an rc call only then pass in the <code>_filter</code> parameter.</p>
<p>This should be in the same format as the <code>filter</code> key returned by <a href="#options-get">options/get</a>.</p>
<p>For example, if you wished to run a sync with these flags</p>
<pre><code>--max-size 1M --max-age 42s --include &quot;a&quot; --include &quot;b&quot;</code></pre>
<p>you would pass this parameter in your JSON blob.</p>
<pre><code>&quot;_filter&quot;:{&quot;MaxSize&quot;:&quot;1M&quot;, &quot;IncludeRule&quot;:[&quot;a&quot;,&quot;b&quot;], &quot;MaxAge&quot;:&quot;42s&quot;}</code></pre>
<p>If using <code>rclone rc</code> this could be passed as</p>
<pre><code>rclone rc ... _filter=&#39;{&quot;MaxSize&quot;:&quot;1M&quot;, &quot;IncludeRule&quot;:[&quot;a&quot;,&quot;b&quot;], &quot;MaxAge&quot;:&quot;42s&quot;}&#39;</code></pre>
<p>Any filter parameters you don't set will inherit the global defaults which were set with command line flags or environment variables.</p>
<p>Note that it is possible to set some values as strings or integers - see <a href="#data-types">data types</a> for more info. Here is an example setting the equivalent of <code>--buffer-size</code> in string or integer format.</p>
<pre><code>&quot;_filter&quot;:{&quot;MinSize&quot;: &quot;42M&quot;}
&quot;_filter&quot;:{&quot;MinSize&quot;: 44040192}</code></pre>
<p>If you wish to check the <code>_filter</code> assignment has worked properly then calling <code>options/local</code> will show what the value got set to.</p>
<h3 id="assigning-operations-to-groups-with-_group-value">Assigning operations to groups with _group = value</h3>
<p>Each rc call has its own stats group for tracking its metrics. By default grouping is done by the composite group name from prefix <code>job/</code> and id of the job like so <code>job/1</code>.</p>
<p>If <code>_group</code> has a value then stats for that request will be grouped under that value. This allows caller to group stats under their own name.</p>
<p>Stats for specific group can be accessed by passing <code>group</code> to <code>core/stats</code>:</p>
<pre><code>$ rclone rc --json &#39;{ &quot;group&quot;: &quot;job/1&quot; }&#39; core/stats
{
    &quot;speed&quot;: 12345
    ...
}</code></pre>
<h2 id="data-types">Data types</h2>
<p>When the API returns types, these will mostly be straight forward integer, string or boolean types.</p>
<p>However some of the types returned by the <a href="#options-get">options/get</a> call and taken by the <a href="#options-set">options/set</a> calls as well as the <code>vfsOpt</code>, <code>mountOpt</code> and the <code>_config</code> parameters.</p>
<ul>
<li><code>Duration</code> - these are returned as an integer duration in nanoseconds. They may be set as an integer, or they may be set with time string, eg "5s". See the <a href="https://rclone.org/docs/#options">options section</a> for more info.</li>
<li><code>Size</code> - these are returned as an integer number of bytes. They may be set as an integer or they may be set with a size suffix string, eg "10M". See the <a href="https://rclone.org/docs/#options">options section</a> for more info.</li>
<li>Enumerated type (such as <code>CutoffMode</code>, <code>DumpFlags</code>, <code>LogLevel</code>, <code>VfsCacheMode</code> - these will be returned as an integer and may be set as an integer but more conveniently they can be set as a string, eg "HARD" for <code>CutoffMode</code> or <code>DEBUG</code> for <code>LogLevel</code>.</li>
<li><code>BandwidthSpec</code> - this will be set and returned as a string, eg "1M".</li>
</ul>
<h3 id="option-blocks">Option blocks</h3>
<p>The calls <a href="#options-info">options/info</a> (for the main config) and <a href="#config-providers">config/providers</a> (for the backend config) may be used to get information on the rclone configuration options. This can be used to build user interfaces for displaying and setting any rclone option.</p>
<p>These consist of arrays of <code>Option</code> blocks. These have the following format. Each block describes a single option.</p>
<table>
<colgroup>
<col style="width: 19%" />
<col style="width: 16%" />
<col style="width: 27%" />
<col style="width: 36%" />
</colgroup>
<thead>
<tr class="header">
<th>Field</th>
<th>Type</th>
<th>Optional</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td>Name</td>
<td>string</td>
<td>N</td>
<td>name of the option in snake_case</td>
</tr>
<tr class="even">
<td>FieldName</td>
<td>string</td>
<td>N</td>
<td>name of the field used in the rc - if blank use Name</td>
</tr>
<tr class="odd">
<td>Help</td>
<td>string</td>
<td>N</td>
<td>help, started with a single sentence on a single line</td>
</tr>
<tr class="even">
<td>Groups</td>
<td>string</td>
<td>Y</td>
<td>groups this option belongs to - comma separated string for options classification</td>
</tr>
<tr class="odd">
<td>Provider</td>
<td>string</td>
<td>Y</td>
<td>set to filter on provider</td>
</tr>
<tr class="even">
<td>Default</td>
<td>any</td>
<td>N</td>
<td>default value, if set (and not to nil or "") then Required does nothing</td>
</tr>
<tr class="odd">
<td>Value</td>
<td>any</td>
<td>N</td>
<td>value to be set by flags</td>
</tr>
<tr class="even">
<td>Examples</td>
<td>Examples</td>
<td>Y</td>
<td>predefined values that can be selected from list (multiple-choice option)</td>
</tr>
<tr class="odd">
<td>ShortOpt</td>
<td>string</td>
<td>Y</td>
<td>the short command line option for this</td>
</tr>
<tr class="even">
<td>Hide</td>
<td>Visibility</td>
<td>N</td>
<td>if non zero, this option is hidden from the configurator or the command line</td>
</tr>
<tr class="odd">
<td>Required</td>
<td>bool</td>
<td>N</td>
<td>this option is required, meaning value cannot be empty unless there is a default</td>
</tr>
<tr class="even">
<td>IsPassword</td>
<td>bool</td>
<td>N</td>
<td>set if the option is a password</td>
</tr>
<tr class="odd">
<td>NoPrefix</td>
<td>bool</td>
<td>N</td>
<td>set if the option for this should not use the backend prefix</td>
</tr>
<tr class="even">
<td>Advanced</td>
<td>bool</td>
<td>N</td>
<td>set if this is an advanced config option</td>
</tr>
<tr class="odd">
<td>Exclusive</td>
<td>bool</td>
<td>N</td>
<td>set if the answer can only be one of the examples (empty string allowed unless Required or Default is set)</td>
</tr>
<tr class="even">
<td>Sensitive</td>
<td>bool</td>
<td>N</td>
<td>set if this option should be redacted when using <code>rclone config redacted</code></td>
</tr>
</tbody>
</table>
<p>An example of this might be the <code>--log-level</code> flag. Note that the <code>Name</code> of the option becomes the command line flag with <code>_</code> replaced with <code>-</code>.</p>
<pre><code>{
    &quot;Advanced&quot;: false,
    &quot;Default&quot;: 5,
    &quot;DefaultStr&quot;: &quot;NOTICE&quot;,
    &quot;Examples&quot;: [
        {
            &quot;Help&quot;: &quot;&quot;,
            &quot;Value&quot;: &quot;EMERGENCY&quot;
        },
        {
            &quot;Help&quot;: &quot;&quot;,
            &quot;Value&quot;: &quot;ALERT&quot;
        },
        ...
    ],
    &quot;Exclusive&quot;: true,
    &quot;FieldName&quot;: &quot;LogLevel&quot;,
    &quot;Groups&quot;: &quot;Logging&quot;,
    &quot;Help&quot;: &quot;Log level DEBUG|INFO|NOTICE|ERROR&quot;,
    &quot;Hide&quot;: 0,
    &quot;IsPassword&quot;: false,
    &quot;Name&quot;: &quot;log_level&quot;,
    &quot;NoPrefix&quot;: true,
    &quot;Required&quot;: true,
    &quot;Sensitive&quot;: false,
    &quot;Type&quot;: &quot;LogLevel&quot;,
    &quot;Value&quot;: null,
    &quot;ValueStr&quot;: &quot;NOTICE&quot;
},</code></pre>
<p>Note that the <code>Help</code> may be multiple lines separated by <code>\n</code>. The first line will always be a short sentence and this is the sentence shown when running <code>rclone help flags</code>.</p>
<h2 id="specifying-remotes-to-work-on">Specifying remotes to work on</h2>
<p>Remotes are specified with the <code>fs=</code>, <code>srcFs=</code>, <code>dstFs=</code> parameters depending on the command being used.</p>
<p>The parameters can be a string as per the rest of rclone, eg <code>s3:bucket/path</code> or <code>:sftp:/my/dir</code>. They can also be specified as JSON blobs.</p>
<p>If specifying a JSON blob it should be a object mapping strings to strings. These values will be used to configure the remote. There are 3 special values which may be set:</p>
<ul>
<li><code>type</code> - set to <code>type</code> to specify a remote called <code>:type:</code></li>
<li><code>_name</code> - set to <code>name</code> to specify a remote called <code>name:</code></li>
<li><code>_root</code> - sets the root of the remote - may be empty</li>
</ul>
<p>One of <code>_name</code> or <code>type</code> should normally be set. If the <code>local</code> backend is desired then <code>type</code> should be set to <code>local</code>. If <code>_root</code> isn't specified then it defaults to the root of the remote.</p>
<p>For example this JSON is equivalent to <code>remote:/tmp</code></p>
<pre><code>{
    &quot;_name&quot;: &quot;remote&quot;,
    &quot;_root&quot;: &quot;/tmp&quot;
}</code></pre>
<p>And this is equivalent to <code>:sftp,host='example.com':/tmp</code></p>
<pre><code>{
    &quot;type&quot;: &quot;sftp&quot;,
    &quot;host&quot;: &quot;example.com&quot;,
    &quot;_root&quot;: &quot;/tmp&quot;
}</code></pre>
<p>And this is equivalent to <code>/tmp/dir</code></p>
<pre><code>{
    type = &quot;local&quot;,
    _root = &quot;/tmp/dir&quot;
}</code></pre>
<h2 id="supported-commands">Supported commands</h2>
<h3 id="backend-command">backend/command: Runs a backend command.</h3>
<p>This takes the following parameters:</p>
<ul>
<li>command - a string with the command name</li>
<li>fs - a remote name string e.g. "drive:"</li>
<li>arg - a list of arguments for the backend command</li>
<li>opt - a map of string to string of options</li>
</ul>
<p>Returns:</p>
<ul>
<li>result - result from the backend command</li>
</ul>
<p>Example:</p>
<pre><code>rclone rc backend/command command=noop fs=. -o echo=yes -o blue -a path1 -a path2</code></pre>
<p>Returns</p>
<pre><code>{
    &quot;result&quot;: {
        &quot;arg&quot;: [
            &quot;path1&quot;,
            &quot;path2&quot;
        ],
        &quot;name&quot;: &quot;noop&quot;,
        &quot;opt&quot;: {
            &quot;blue&quot;: &quot;&quot;,
            &quot;echo&quot;: &quot;yes&quot;
        }
    }
}</code></pre>
<p>Note that this is the direct equivalent of using this "backend" command:</p>
<pre><code>rclone backend noop . -o echo=yes -o blue path1 path2</code></pre>
<p>Note that arguments must be preceded by the "-a" flag</p>
<p>See the <a href="https://rclone.org/commands/rclone_backend/">backend</a> command for more information.</p>
<p><strong>Authentication is required for this call.</strong></p>
<h3 id="cache-expire">cache/expire: Purge a remote from cache</h3>
<p>Purge a remote from the cache backend. Supports either a directory or a file. Params: - remote = path to remote (required) - withData = true/false to delete cached data (chunks) as well (optional)</p>
<p>Eg</p>
<pre><code>rclone rc cache/expire remote=path/to/sub/folder/
rclone rc cache/expire remote=/ withData=true</code></pre>
<h3 id="cache-fetch">cache/fetch: Fetch file chunks</h3>
<p>Ensure the specified file chunks are cached on disk.</p>
<p>The chunks= parameter specifies the file chunks to check. It takes a comma separated list of array slice indices. The slice indices are similar to Python slices: start[:end]</p>
<p>start is the 0 based chunk number from the beginning of the file to fetch inclusive. end is 0 based chunk number from the beginning of the file to fetch exclusive. Both values can be negative, in which case they count from the back of the file. The value "-5:" represents the last 5 chunks of a file.</p>
<p>Some valid examples are: ":5,-5:" -&gt; the first and last five chunks "0,-2" -&gt; the first and the second last chunk "0:10" -&gt; the first ten chunks</p>
<p>Any parameter with a key that starts with "file" can be used to specify files to fetch, e.g.</p>
<pre><code>rclone rc cache/fetch chunks=0 file=hello file2=home/goodbye</code></pre>
<p>File names will automatically be encrypted when the a crypt remote is used on top of the cache.</p>
<h3 id="cache-stats">cache/stats: Get cache stats</h3>
<p>Show statistics for the cache remote.</p>
<h3 id="config-create">config/create: create the config for a remote.</h3>
<p>This takes the following parameters:</p>
<ul>
<li>name - name of remote</li>
<li>parameters - a map of { "key": "value" } pairs</li>
<li>type - type of the new remote</li>
<li>opt - a dictionary of options to control the configuration
<ul>
<li>obscure - declare passwords are plain and need obscuring</li>
<li>noObscure - declare passwords are already obscured and don't need obscuring</li>
<li>nonInteractive - don't interact with a user, return questions</li>
<li>continue - continue the config process with an answer</li>
<li>all - ask all the config questions not just the post config ones</li>
<li>state - state to restart with - used with continue</li>
<li>result - result to restart with - used with continue</li>
</ul></li>
</ul>
<p>See the <a href="https://rclone.org/commands/rclone_config_create/">config create</a> command for more information on the above.</p>
<p><strong>Authentication is required for this call.</strong></p>
<h3 id="config-delete">config/delete: Delete a remote in the config file.</h3>
<p>Parameters:</p>
<ul>
<li>name - name of remote to delete</li>
</ul>
<p>See the <a href="https://rclone.org/commands/rclone_config_delete/">config delete</a> command for more information on the above.</p>
<p><strong>Authentication is required for this call.</strong></p>
<h3 id="config-dump">config/dump: Dumps the config file.</h3>
<p>Returns a JSON object: - key: value</p>
<p>Where keys are remote names and values are the config parameters.</p>
<p>See the <a href="https://rclone.org/commands/rclone_config_dump/">config dump</a> command for more information on the above.</p>
<p><strong>Authentication is required for this call.</strong></p>
<h3 id="config-get">config/get: Get a remote in the config file.</h3>
<p>Parameters:</p>
<ul>
<li>name - name of remote to get</li>
</ul>
<p>See the <a href="https://rclone.org/commands/rclone_config_dump/">config dump</a> command for more information on the above.</p>
<p><strong>Authentication is required for this call.</strong></p>
<h3 id="config-listremotes">config/listremotes: Lists the remotes in the config file and defined in environment variables.</h3>
<p>Returns - remotes - array of remote names</p>
<p>See the <a href="https://rclone.org/commands/rclone_listremotes/">listremotes</a> command for more information on the above.</p>
<p><strong>Authentication is required for this call.</strong></p>
<h3 id="config-password">config/password: password the config for a remote.</h3>
<p>This takes the following parameters:</p>
<ul>
<li>name - name of remote</li>
<li>parameters - a map of { "key": "value" } pairs</li>
</ul>
<p>See the <a href="https://rclone.org/commands/rclone_config_password/">config password</a> command for more information on the above.</p>
<p><strong>Authentication is required for this call.</strong></p>
<h3 id="config-paths">config/paths: Reads the config file path and other important paths.</h3>
<p>Returns a JSON object with the following keys:</p>
<ul>
<li>config: path to config file</li>
<li>cache: path to root of cache directory</li>
<li>temp: path to root of temporary directory</li>
</ul>
<p>Eg</p>
<pre><code>{
    &quot;cache&quot;: &quot;/home/USER/.cache/rclone&quot;,
    &quot;config&quot;: &quot;/home/USER/.rclone.conf&quot;,
    &quot;temp&quot;: &quot;/tmp&quot;
}</code></pre>
<p>See the <a href="https://rclone.org/commands/rclone_config_paths/">config paths</a> command for more information on the above.</p>
<p><strong>Authentication is required for this call.</strong></p>
<h3 id="config-providers">config/providers: Shows how providers are configured in the config file.</h3>
<p>Returns a JSON object: - providers - array of objects</p>
<p>See the <a href="https://rclone.org/commands/rclone_config_providers/">config providers</a> command for more information on the above.</p>
<p>Note that the Options blocks are in the same format as returned by "options/info". They are described in the <a href="#option-blocks">option blocks</a> section.</p>
<p><strong>Authentication is required for this call.</strong></p>
<h3 id="config-setpath">config/setpath: Set the path of the config file</h3>
<p>Parameters:</p>
<ul>
<li>path - path to the config file to use</li>
</ul>
<p><strong>Authentication is required for this call.</strong></p>
<h3 id="config-update">config/update: update the config for a remote.</h3>
<p>This takes the following parameters:</p>
<ul>
<li>name - name of remote</li>
<li>parameters - a map of { "key": "value" } pairs</li>
<li>opt - a dictionary of options to control the configuration
<ul>
<li>obscure - declare passwords are plain and need obscuring</li>
<li>noObscure - declare passwords are already obscured and don't need obscuring</li>
<li>nonInteractive - don't interact with a user, return questions</li>
<li>continue - continue the config process with an answer</li>
<li>all - ask all the config questions not just the post config ones</li>
<li>state - state to restart with - used with continue</li>
<li>result - result to restart with - used with continue</li>
</ul></li>
</ul>
<p>See the <a href="https://rclone.org/commands/rclone_config_update/">config update</a> command for more information on the above.</p>
<p><strong>Authentication is required for this call.</strong></p>
<h3 id="core-bwlimit">core/bwlimit: Set the bandwidth limit.</h3>
<p>This sets the bandwidth limit to the string passed in. This should be a single bandwidth limit entry or a pair of upload:download bandwidth.</p>
<p>Eg</p>
<pre><code>rclone rc core/bwlimit rate=off
{
    &quot;bytesPerSecond&quot;: -1,
    &quot;bytesPerSecondTx&quot;: -1,
    &quot;bytesPerSecondRx&quot;: -1,
    &quot;rate&quot;: &quot;off&quot;
}
rclone rc core/bwlimit rate=1M
{
    &quot;bytesPerSecond&quot;: 1048576,
    &quot;bytesPerSecondTx&quot;: 1048576,
    &quot;bytesPerSecondRx&quot;: 1048576,
    &quot;rate&quot;: &quot;1M&quot;
}
rclone rc core/bwlimit rate=1M:100k
{
    &quot;bytesPerSecond&quot;: 1048576,
    &quot;bytesPerSecondTx&quot;: 1048576,
    &quot;bytesPerSecondRx&quot;: 131072,
    &quot;rate&quot;: &quot;1M&quot;
}</code></pre>
<p>If the rate parameter is not supplied then the bandwidth is queried</p>
<pre><code>rclone rc core/bwlimit
{
    &quot;bytesPerSecond&quot;: 1048576,
    &quot;bytesPerSecondTx&quot;: 1048576,
    &quot;bytesPerSecondRx&quot;: 1048576,
    &quot;rate&quot;: &quot;1M&quot;
}</code></pre>
<p>The format of the parameter is exactly the same as passed to --bwlimit except only one bandwidth may be specified.</p>
<p>In either case "rate" is returned as a human-readable string, and "bytesPerSecond" is returned as a number.</p>
<h3 id="core-command">core/command: Run a rclone terminal command over rc.</h3>
<p>This takes the following parameters:</p>
<ul>
<li>command - a string with the command name.</li>
<li>arg - a list of arguments for the backend command.</li>
<li>opt - a map of string to string of options.</li>
<li>returnType - one of ("COMBINED_OUTPUT", "STREAM", "STREAM_ONLY_STDOUT", "STREAM_ONLY_STDERR").
<ul>
<li>Defaults to "COMBINED_OUTPUT" if not set.</li>
<li>The STREAM returnTypes will write the output to the body of the HTTP message.</li>
<li>The COMBINED_OUTPUT will write the output to the "result" parameter.</li>
</ul></li>
</ul>
<p>Returns:</p>
<ul>
<li>result - result from the backend command.
<ul>
<li>Only set when using returnType "COMBINED_OUTPUT".</li>
</ul></li>
<li>error - set if rclone exits with an error code.</li>
<li>returnType - one of ("COMBINED_OUTPUT", "STREAM", "STREAM_ONLY_STDOUT", "STREAM_ONLY_STDERR").</li>
</ul>
<p>Example:</p>
<pre><code>rclone rc core/command command=ls -a mydrive:/ -o max-depth=1
rclone rc core/command -a ls -a mydrive:/ -o max-depth=1</code></pre>
<p>Returns:</p>
<pre><code>{
    &quot;error&quot;: false,
    &quot;result&quot;: &quot;&lt;Raw command line output&gt;&quot;
}

OR
{
    &quot;error&quot;: true,
    &quot;result&quot;: &quot;&lt;Raw command line output&gt;&quot;
}
</code></pre>
<p><strong>Authentication is required for this call.</strong></p>
<h3 id="core-du">core/du: Returns disk usage of a locally attached disk.</h3>
<p>This returns the disk usage for the local directory passed in as dir.</p>
<p>If the directory is not passed in, it defaults to the directory pointed to by --cache-dir.</p>
<ul>
<li>dir - string (optional)</li>
</ul>
<p>Returns:</p>
<pre><code>{
    &quot;dir&quot;: &quot;/&quot;,
    &quot;info&quot;: {
        &quot;Available&quot;: 361769115648,
        &quot;Free&quot;: 361785892864,
        &quot;Total&quot;: 982141468672
    }
}</code></pre>
<h3 id="core-gc">core/gc: Runs a garbage collection.</h3>
<p>This tells the go runtime to do a garbage collection run. It isn't necessary to call this normally, but it can be useful for debugging memory problems.</p>
<h3 id="core-group-list">core/group-list: Returns list of stats.</h3>
<p>This returns list of stats groups currently in memory.</p>
<p>Returns the following values:</p>
<pre><code>{
    &quot;groups&quot;:  an array of group names:
        [
            &quot;group1&quot;,
            &quot;group2&quot;,
            ...
        ]
}</code></pre>
<h3 id="core-memstats">core/memstats: Returns the memory statistics</h3>
<p>This returns the memory statistics of the running program. What the values mean are explained in the go docs: https://golang.org/pkg/runtime/#MemStats</p>
<p>The most interesting values for most people are:</p>
<ul>
<li>HeapAlloc - this is the amount of memory rclone is actually using</li>
<li>HeapSys - this is the amount of memory rclone has obtained from the OS</li>
<li>Sys - this is the total amount of memory requested from the OS
<ul>
<li>It is virtual memory so may include unused memory</li>
</ul></li>
</ul>
<h3 id="core-obscure">core/obscure: Obscures a string passed in.</h3>
<p>Pass a clear string and rclone will obscure it for the config file: - clear - string</p>
<p>Returns: - obscured - string</p>
<h3 id="core-pid">core/pid: Return PID of current process</h3>
<p>This returns PID of current process. Useful for stopping rclone process.</p>
<h3 id="core-quit">core/quit: Terminates the app.</h3>
<p>(Optional) Pass an exit code to be used for terminating the app: - exitCode - int</p>
<h3 id="core-stats">core/stats: Returns stats about current transfers.</h3>
<p>This returns all available stats:</p>
<pre><code>rclone rc core/stats</code></pre>
<p>If group is not provided then summed up stats for all groups will be returned.</p>
<p>Parameters</p>
<ul>
<li>group - name of the stats group (string)</li>
</ul>
<p>Returns the following values:</p>
<pre><code>{
    &quot;bytes&quot;: total transferred bytes since the start of the group,
    &quot;checks&quot;: number of files checked,
    &quot;deletes&quot; : number of files deleted,
    &quot;elapsedTime&quot;: time in floating point seconds since rclone was started,
    &quot;errors&quot;: number of errors,
    &quot;eta&quot;: estimated time in seconds until the group completes,
    &quot;fatalError&quot;: boolean whether there has been at least one fatal error,
    &quot;lastError&quot;: last error string,
    &quot;renames&quot; : number of files renamed,
    &quot;retryError&quot;: boolean showing whether there has been at least one non-NoRetryError,
        &quot;serverSideCopies&quot;: number of server side copies done,
        &quot;serverSideCopyBytes&quot;: number bytes server side copied,
        &quot;serverSideMoves&quot;: number of server side moves done,
        &quot;serverSideMoveBytes&quot;: number bytes server side moved,
    &quot;speed&quot;: average speed in bytes per second since start of the group,
    &quot;totalBytes&quot;: total number of bytes in the group,
    &quot;totalChecks&quot;: total number of checks in the group,
    &quot;totalTransfers&quot;: total number of transfers in the group,
    &quot;transferTime&quot; : total time spent on running jobs,
    &quot;transfers&quot;: number of transferred files,
    &quot;transferring&quot;: an array of currently active file transfers:
        [
            {
                &quot;bytes&quot;: total transferred bytes for this file,
                &quot;eta&quot;: estimated time in seconds until file transfer completion
                &quot;name&quot;: name of the file,
                &quot;percentage&quot;: progress of the file transfer in percent,
                &quot;speed&quot;: average speed over the whole transfer in bytes per second,
                &quot;speedAvg&quot;: current speed in bytes per second as an exponentially weighted moving average,
                &quot;size&quot;: size of the file in bytes
            }
        ],
    &quot;checking&quot;: an array of names of currently active file checks
        []
}</code></pre>
<p>Values for "transferring", "checking" and "lastError" are only assigned if data is available. The value for "eta" is null if an eta cannot be determined.</p>
<h3 id="core-stats-delete">core/stats-delete: Delete stats group.</h3>
<p>This deletes entire stats group.</p>
<p>Parameters</p>
<ul>
<li>group - name of the stats group (string)</li>
</ul>
<h3 id="core-stats-reset">core/stats-reset: Reset stats.</h3>
<p>This clears counters, errors and finished transfers for all stats or specific stats group if group is provided.</p>
<p>Parameters</p>
<ul>
<li>group - name of the stats group (string)</li>
</ul>
<h3 id="core-transferred">core/transferred: Returns stats about completed transfers.</h3>
<p>This returns stats about completed transfers:</p>
<pre><code>rclone rc core/transferred</code></pre>
<p>If group is not provided then completed transfers for all groups will be returned.</p>
<p>Note only the last 100 completed transfers are returned.</p>
<p>Parameters</p>
<ul>
<li>group - name of the stats group (string)</li>
</ul>
<p>Returns the following values:</p>
<pre><code>{
    &quot;transferred&quot;:  an array of completed transfers (including failed ones):
        [
            {
                &quot;name&quot;: name of the file,
                &quot;size&quot;: size of the file in bytes,
                &quot;bytes&quot;: total transferred bytes for this file,
                &quot;checked&quot;: if the transfer is only checked (skipped, deleted),
                &quot;timestamp&quot;: integer representing millisecond unix epoch,
                &quot;error&quot;: string description of the error (empty if successful),
                &quot;jobid&quot;: id of the job that this transfer belongs to
            }
        ]
}</code></pre>
<h3 id="core-version">core/version: Shows the current version of rclone and the go runtime.</h3>
<p>This shows the current version of go and the go runtime:</p>
<ul>
<li>version - rclone version, e.g. "v1.53.0"</li>
<li>decomposed - version number as [major, minor, patch]</li>
<li>isGit - boolean - true if this was compiled from the git version</li>
<li>isBeta - boolean - true if this is a beta version</li>
<li>os - OS in use as according to Go</li>
<li>arch - cpu architecture in use according to Go</li>
<li>goVersion - version of Go runtime in use</li>
<li>linking - type of rclone executable (static or dynamic)</li>
<li>goTags - space separated build tags or "none"</li>
</ul>
<h3 id="debug-set-block-profile-rate">debug/set-block-profile-rate: Set runtime.SetBlockProfileRate for blocking profiling.</h3>
<p>SetBlockProfileRate controls the fraction of goroutine blocking events that are reported in the blocking profile. The profiler aims to sample an average of one blocking event per rate nanoseconds spent blocked.</p>
<p>To include every blocking event in the profile, pass rate = 1. To turn off profiling entirely, pass rate &lt;= 0.</p>
<p>After calling this you can use this to see the blocking profile:</p>
<pre><code>go tool pprof http://localhost:5572/debug/pprof/block</code></pre>
<p>Parameters:</p>
<ul>
<li>rate - int</li>
</ul>
<h3 id="debug-set-gc-percent">debug/set-gc-percent: Call runtime/debug.SetGCPercent for setting the garbage collection target percentage.</h3>
<p>SetGCPercent sets the garbage collection target percentage: a collection is triggered when the ratio of freshly allocated data to live data remaining after the previous collection reaches this percentage. SetGCPercent returns the previous setting. The initial setting is the value of the GOGC environment variable at startup, or 100 if the variable is not set.</p>
<p>This setting may be effectively reduced in order to maintain a memory limit. A negative percentage effectively disables garbage collection, unless the memory limit is reached.</p>
<p>See https://pkg.go.dev/runtime/debug#SetMemoryLimit for more details.</p>
<p>Parameters:</p>
<ul>
<li>gc-percent - int</li>
</ul>
<h3 id="debug-set-mutex-profile-fraction">debug/set-mutex-profile-fraction: Set runtime.SetMutexProfileFraction for mutex profiling.</h3>
<p>SetMutexProfileFraction controls the fraction of mutex contention events that are reported in the mutex profile. On average 1/rate events are reported. The previous rate is returned.</p>
<p>To turn off profiling entirely, pass rate 0. To just read the current rate, pass rate &lt; 0. (For n&gt;1 the details of sampling may change.)</p>
<p>Once this is set you can look use this to profile the mutex contention:</p>
<pre><code>go tool pprof http://localhost:5572/debug/pprof/mutex</code></pre>
<p>Parameters:</p>
<ul>
<li>rate - int</li>
</ul>
<p>Results:</p>
<ul>
<li>previousRate - int</li>
</ul>
<h3 id="debug-set-soft-memory-limit">debug/set-soft-memory-limit: Call runtime/debug.SetMemoryLimit for setting a soft memory limit for the runtime.</h3>
<p>SetMemoryLimit provides the runtime with a soft memory limit.</p>
<p>The runtime undertakes several processes to try to respect this memory limit, including adjustments to the frequency of garbage collections and returning memory to the underlying system more aggressively. This limit will be respected even if GOGC=off (or, if SetGCPercent(-1) is executed).</p>
<p>The input limit is provided as bytes, and includes all memory mapped, managed, and not released by the Go runtime. Notably, it does not account for space used by the Go binary and memory external to Go, such as memory managed by the underlying system on behalf of the process, or memory managed by non-Go code inside the same process. Examples of excluded memory sources include: OS kernel memory held on behalf of the process, memory allocated by C code, and memory mapped by syscall.Mmap (because it is not managed by the Go runtime).</p>
<p>A zero limit or a limit that's lower than the amount of memory used by the Go runtime may cause the garbage collector to run nearly continuously. However, the application may still make progress.</p>
<p>The memory limit is always respected by the Go runtime, so to effectively disable this behavior, set the limit very high. math.MaxInt64 is the canonical value for disabling the limit, but values much greater than the available memory on the underlying system work just as well.</p>
<p>See https://go.dev/doc/gc-guide for a detailed guide explaining the soft memory limit in more detail, as well as a variety of common use-cases and scenarios.</p>
<p>SetMemoryLimit returns the previously set memory limit. A negative input does not adjust the limit, and allows for retrieval of the currently set memory limit.</p>
<p>Parameters:</p>
<ul>
<li>mem-limit - int</li>
</ul>
<h3 id="fscache-clear">fscache/clear: Clear the Fs cache.</h3>
<p>This clears the fs cache. This is where remotes created from backends are cached for a short while to make repeated rc calls more efficient.</p>
<p>If you change the parameters of a backend then you may want to call this to clear an existing remote out of the cache before re-creating it.</p>
<p><strong>Authentication is required for this call.</strong></p>
<h3 id="fscache-entries">fscache/entries: Returns the number of entries in the fs cache.</h3>
<p>This returns the number of entries in the fs cache.</p>
<p>Returns - entries - number of items in the cache</p>
<p><strong>Authentication is required for this call.</strong></p>
<h3 id="job-list">job/list: Lists the IDs of the running jobs</h3>
<p>Parameters: None.</p>
<p>Results:</p>
<ul>
<li>executeId - string id of rclone executing (change after restart)</li>
<li>jobids - array of integer job ids (starting at 1 on each restart)</li>
</ul>
<h3 id="job-status">job/status: Reads the status of the job ID</h3>
<p>Parameters:</p>
<ul>
<li>jobid - id of the job (integer).</li>
</ul>
<p>Results:</p>
<ul>
<li>finished - boolean</li>
<li>duration - time in seconds that the job ran for</li>
<li>endTime - time the job finished (e.g. "2018-10-26T18:50:20.528746884+01:00")</li>
<li>error - error from the job or empty string for no error</li>
<li>finished - boolean whether the job has finished or not</li>
<li>id - as passed in above</li>
<li>startTime - time the job started (e.g. "2018-10-26T18:50:20.528336039+01:00")</li>
<li>success - boolean - true for success false otherwise</li>
<li>output - output of the job as would have been returned if called synchronously</li>
<li>progress - output of the progress related to the underlying job</li>
</ul>
<h3 id="job-stop">job/stop: Stop the running job</h3>
<p>Parameters:</p>
<ul>
<li>jobid - id of the job (integer).</li>
</ul>
<h3 id="job-stopgroup">job/stopgroup: Stop all running jobs in a group</h3>
<p>Parameters:</p>
<ul>
<li>group - name of the group (string).</li>
</ul>
<h3 id="mount-listmounts">mount/listmounts: Show current mount points</h3>
<p>This shows currently mounted points, which can be used for performing an unmount.</p>
<p>This takes no parameters and returns</p>
<ul>
<li>mountPoints: list of current mount points</li>
</ul>
<p>Eg</p>
<pre><code>rclone rc mount/listmounts</code></pre>
<p><strong>Authentication is required for this call.</strong></p>
<h3 id="mount-mount">mount/mount: Create a new mount point</h3>
<p>rclone allows Linux, FreeBSD, macOS and Windows to mount any of Rclone's cloud storage systems as a file system with FUSE.</p>
<p>If no mountType is provided, the priority is given as follows: 1. mount 2.cmount 3.mount2</p>
<p>This takes the following parameters:</p>
<ul>
<li>fs - a remote path to be mounted (required)</li>
<li>mountPoint: valid path on the local machine (required)</li>
<li>mountType: one of the values (mount, cmount, mount2) specifies the mount implementation to use</li>
<li>mountOpt: a JSON object with Mount options in.</li>
<li>vfsOpt: a JSON object with VFS options in.</li>
</ul>
<p>Example:</p>
<pre><code>rclone rc mount/mount fs=mydrive: mountPoint=/home/&lt;user&gt;/mountPoint
rclone rc mount/mount fs=mydrive: mountPoint=/home/&lt;user&gt;/mountPoint mountType=mount
rclone rc mount/mount fs=TestDrive: mountPoint=/mnt/tmp vfsOpt=&#39;{&quot;CacheMode&quot;: 2}&#39; mountOpt=&#39;{&quot;AllowOther&quot;: true}&#39;</code></pre>
<p>The vfsOpt are as described in options/get and can be seen in the the "vfs" section when running and the mountOpt can be seen in the "mount" section:</p>
<pre><code>rclone rc options/get</code></pre>
<p><strong>Authentication is required for this call.</strong></p>
<h3 id="mount-types">mount/types: Show all possible mount types</h3>
<p>This shows all possible mount types and returns them as a list.</p>
<p>This takes no parameters and returns</p>
<ul>
<li>mountTypes: list of mount types</li>
</ul>
<p>The mount types are strings like "mount", "mount2", "cmount" and can be passed to mount/mount as the mountType parameter.</p>
<p>Eg</p>
<pre><code>rclone rc mount/types</code></pre>
<p><strong>Authentication is required for this call.</strong></p>
<h3 id="mount-unmount">mount/unmount: Unmount selected active mount</h3>
<p>rclone allows Linux, FreeBSD, macOS and Windows to mount any of Rclone's cloud storage systems as a file system with FUSE.</p>
<p>This takes the following parameters:</p>
<ul>
<li>mountPoint: valid path on the local machine where the mount was created (required)</li>
</ul>
<p>Example:</p>
<pre><code>rclone rc mount/unmount mountPoint=/home/&lt;user&gt;/mountPoint</code></pre>
<p><strong>Authentication is required for this call.</strong></p>
<h3 id="mount-unmountall">mount/unmountall: Unmount all active mounts</h3>
<p>rclone allows Linux, FreeBSD, macOS and Windows to mount any of Rclone's cloud storage systems as a file system with FUSE.</p>
<p>This takes no parameters and returns error if unmount does not succeed.</p>
<p>Eg</p>
<pre><code>rclone rc mount/unmountall</code></pre>
<p><strong>Authentication is required for this call.</strong></p>
<h3 id="operations-about">operations/about: Return the space used on the remote</h3>
<p>This takes the following parameters:</p>
<ul>
<li>fs - a remote name string e.g. "drive:"</li>
</ul>
<p>The result is as returned from rclone about --json</p>
<p>See the <a href="https://rclone.org/commands/rclone_about/">about</a> command for more information on the above.</p>
<p><strong>Authentication is required for this call.</strong></p>
<h3 id="operations-check">operations/check: check the source and destination are the same</h3>
<p>Checks the files in the source and destination match. It compares sizes and hashes and logs a report of files that don't match. It doesn't alter the source or destination.</p>
<p>This takes the following parameters:</p>
<ul>
<li>srcFs - a remote name string e.g. "drive:" for the source, "/" for local filesystem</li>
<li>dstFs - a remote name string e.g. "drive2:" for the destination, "/" for local filesystem</li>
<li>download - check by downloading rather than with hash</li>
<li>checkFileHash - treat checkFileFs:checkFileRemote as a SUM file with hashes of given type</li>
<li>checkFileFs - treat checkFileFs:checkFileRemote as a SUM file with hashes of given type</li>
<li>checkFileRemote - treat checkFileFs:checkFileRemote as a SUM file with hashes of given type</li>
<li>oneWay - check one way only, source files must exist on remote</li>
<li>combined - make a combined report of changes (default false)</li>
<li>missingOnSrc - report all files missing from the source (default true)</li>
<li>missingOnDst - report all files missing from the destination (default true)</li>
<li>match - report all matching files (default false)</li>
<li>differ - report all non-matching files (default true)</li>
<li>error - report all files with errors (hashing or reading) (default true)</li>
</ul>
<p>If you supply the download flag, it will download the data from both remotes and check them against each other on the fly. This can be useful for remotes that don't support hashes or if you really want to check all the data.</p>
<p>If you supply the size-only global flag, it will only compare the sizes not the hashes as well. Use this for a quick check.</p>
<p>If you supply the checkFileHash option with a valid hash name, the checkFileFs:checkFileRemote must point to a text file in the SUM format. This treats the checksum file as the source and dstFs as the destination. Note that srcFs is not used and should not be supplied in this case.</p>
<p>Returns:</p>
<ul>
<li>success - true if no error, false otherwise</li>
<li>status - textual summary of check, OK or text string</li>
<li>hashType - hash used in check, may be missing</li>
<li>combined - array of strings of combined report of changes</li>
<li>missingOnSrc - array of strings of all files missing from the source</li>
<li>missingOnDst - array of strings of all files missing from the destination</li>
<li>match - array of strings of all matching files</li>
<li>differ - array of strings of all non-matching files</li>
<li>error - array of strings of all files with errors (hashing or reading)</li>
</ul>
<p><strong>Authentication is required for this call.</strong></p>
<h3 id="operations-cleanup">operations/cleanup: Remove trashed files in the remote or path</h3>
<p>This takes the following parameters:</p>
<ul>
<li>fs - a remote name string e.g. "drive:"</li>
</ul>
<p>See the <a href="https://rclone.org/commands/rclone_cleanup/">cleanup</a> command for more information on the above.</p>
<p><strong>Authentication is required for this call.</strong></p>
<h3 id="operations-copyfile">operations/copyfile: Copy a file from source remote to destination remote</h3>
<p>This takes the following parameters:</p>
<ul>
<li>srcFs - a remote name string e.g. "drive:" for the source, "/" for local filesystem</li>
<li>srcRemote - a path within that remote e.g. "file.txt" for the source</li>
<li>dstFs - a remote name string e.g. "drive2:" for the destination, "/" for local filesystem</li>
<li>dstRemote - a path within that remote e.g. "file2.txt" for the destination</li>
</ul>
<p><strong>Authentication is required for this call.</strong></p>
<h3 id="operations-copyurl">operations/copyurl: Copy the URL to the object</h3>
<p>This takes the following parameters:</p>
<ul>
<li>fs - a remote name string e.g. "drive:"</li>
<li>remote - a path within that remote e.g. "dir"</li>
<li>url - string, URL to read from</li>
<li>autoFilename - boolean, set to true to retrieve destination file name from url</li>
</ul>
<p>See the <a href="https://rclone.org/commands/rclone_copyurl/">copyurl</a> command for more information on the above.</p>
<p><strong>Authentication is required for this call.</strong></p>
<h3 id="operations-delete">operations/delete: Remove files in the path</h3>
<p>This takes the following parameters:</p>
<ul>
<li>fs - a remote name string e.g. "drive:"</li>
</ul>
<p>See the <a href="https://rclone.org/commands/rclone_delete/">delete</a> command for more information on the above.</p>
<p><strong>Authentication is required for this call.</strong></p>
<h3 id="operations-deletefile">operations/deletefile: Remove the single file pointed to</h3>
<p>This takes the following parameters:</p>
<ul>
<li>fs - a remote name string e.g. "drive:"</li>
<li>remote - a path within that remote e.g. "dir"</li>
</ul>
<p>See the <a href="https://rclone.org/commands/rclone_deletefile/">deletefile</a> command for more information on the above.</p>
<p><strong>Authentication is required for this call.</strong></p>
<h3 id="operations-fsinfo">operations/fsinfo: Return information about the remote</h3>
<p>This takes the following parameters:</p>
<ul>
<li>fs - a remote name string e.g. "drive:"</li>
</ul>
<p>This returns info about the remote passed in;</p>
<pre><code>{
        // optional features and whether they are available or not
        &quot;Features&quot;: {
                &quot;About&quot;: true,
                &quot;BucketBased&quot;: false,
                &quot;BucketBasedRootOK&quot;: false,
                &quot;CanHaveEmptyDirectories&quot;: true,
                &quot;CaseInsensitive&quot;: false,
                &quot;ChangeNotify&quot;: false,
                &quot;CleanUp&quot;: false,
                &quot;Command&quot;: true,
                &quot;Copy&quot;: false,
                &quot;DirCacheFlush&quot;: false,
                &quot;DirMove&quot;: true,
                &quot;Disconnect&quot;: false,
                &quot;DuplicateFiles&quot;: false,
                &quot;GetTier&quot;: false,
                &quot;IsLocal&quot;: true,
                &quot;ListR&quot;: false,
                &quot;MergeDirs&quot;: false,
                &quot;MetadataInfo&quot;: true,
                &quot;Move&quot;: true,
                &quot;OpenWriterAt&quot;: true,
                &quot;PublicLink&quot;: false,
                &quot;Purge&quot;: true,
                &quot;PutStream&quot;: true,
                &quot;PutUnchecked&quot;: false,
                &quot;ReadMetadata&quot;: true,
                &quot;ReadMimeType&quot;: false,
                &quot;ServerSideAcrossConfigs&quot;: false,
                &quot;SetTier&quot;: false,
                &quot;SetWrapper&quot;: false,
                &quot;Shutdown&quot;: false,
                &quot;SlowHash&quot;: true,
                &quot;SlowModTime&quot;: false,
                &quot;UnWrap&quot;: false,
                &quot;UserInfo&quot;: false,
                &quot;UserMetadata&quot;: true,
                &quot;WrapFs&quot;: false,
                &quot;WriteMetadata&quot;: true,
                &quot;WriteMimeType&quot;: false
        },
        // Names of hashes available
        &quot;Hashes&quot;: [
                &quot;md5&quot;,
                &quot;sha1&quot;,
                &quot;whirlpool&quot;,
                &quot;crc32&quot;,
                &quot;sha256&quot;,
                &quot;dropbox&quot;,
                &quot;mailru&quot;,
                &quot;quickxor&quot;
        ],
        &quot;Name&quot;: &quot;local&quot;,        // Name as created
        &quot;Precision&quot;: 1,         // Precision of timestamps in ns
        &quot;Root&quot;: &quot;/&quot;,            // Path as created
        &quot;String&quot;: &quot;Local file system at /&quot;, // how the remote will appear in logs
        // Information about the system metadata for this backend
        &quot;MetadataInfo&quot;: {
                &quot;System&quot;: {
                        &quot;atime&quot;: {
                                &quot;Help&quot;: &quot;Time of last access&quot;,
                                &quot;Type&quot;: &quot;RFC 3339&quot;,
                                &quot;Example&quot;: &quot;2006-01-02T15:04:05.999999999Z07:00&quot;
                        },
                        &quot;btime&quot;: {
                                &quot;Help&quot;: &quot;Time of file birth (creation)&quot;,
                                &quot;Type&quot;: &quot;RFC 3339&quot;,
                                &quot;Example&quot;: &quot;2006-01-02T15:04:05.999999999Z07:00&quot;
                        },
                        &quot;gid&quot;: {
                                &quot;Help&quot;: &quot;Group ID of owner&quot;,
                                &quot;Type&quot;: &quot;decimal number&quot;,
                                &quot;Example&quot;: &quot;500&quot;
                        },
                        &quot;mode&quot;: {
                                &quot;Help&quot;: &quot;File type and mode&quot;,
                                &quot;Type&quot;: &quot;octal, unix style&quot;,
                                &quot;Example&quot;: &quot;0100664&quot;
                        },
                        &quot;mtime&quot;: {
                                &quot;Help&quot;: &quot;Time of last modification&quot;,
                                &quot;Type&quot;: &quot;RFC 3339&quot;,
                                &quot;Example&quot;: &quot;2006-01-02T15:04:05.999999999Z07:00&quot;
                        },
                        &quot;rdev&quot;: {
                                &quot;Help&quot;: &quot;Device ID (if special file)&quot;,
                                &quot;Type&quot;: &quot;hexadecimal&quot;,
                                &quot;Example&quot;: &quot;1abc&quot;
                        },
                        &quot;uid&quot;: {
                                &quot;Help&quot;: &quot;User ID of owner&quot;,
                                &quot;Type&quot;: &quot;decimal number&quot;,
                                &quot;Example&quot;: &quot;500&quot;
                        }
                },
                &quot;Help&quot;: &quot;Textual help string\n&quot;
        }
}</code></pre>
<p>This command does not have a command line equivalent so use this instead:</p>
<pre><code>rclone rc --loopback operations/fsinfo fs=remote:</code></pre>
<h3 id="operations-hashsum">operations/hashsum: Produces a hashsum file for all the objects in the path.</h3>
<p>Produces a hash file for all the objects in the path using the hash named. The output is in the same format as the standard md5sum/sha1sum tool.</p>
<p>This takes the following parameters:</p>
<ul>
<li>fs - a remote name string e.g. "drive:" for the source, "/" for local filesystem
<ul>
<li>this can point to a file and just that file will be returned in the listing.</li>
</ul></li>
<li>hashType - type of hash to be used</li>
<li>download - check by downloading rather than with hash (boolean)</li>
<li>base64 - output the hashes in base64 rather than hex (boolean)</li>
</ul>
<p>If you supply the download flag, it will download the data from the remote and create the hash on the fly. This can be useful for remotes that don't support the given hash or if you really want to check all the data.</p>
<p>Note that if you wish to supply a checkfile to check hashes against the current files then you should use operations/check instead of operations/hashsum.</p>
<p>Returns:</p>
<ul>
<li>hashsum - array of strings of the hashes</li>
<li>hashType - type of hash used</li>
</ul>
<p>Example:</p>
<pre><code>$ rclone rc --loopback operations/hashsum fs=bin hashType=MD5 download=true base64=true
{
    &quot;hashType&quot;: &quot;md5&quot;,
    &quot;hashsum&quot;: [
        &quot;WTSVLpuiXyJO_kGzJerRLg==  backend-versions.sh&quot;,
        &quot;v1b_OlWCJO9LtNq3EIKkNQ==  bisect-go-rclone.sh&quot;,
        &quot;VHbmHzHh4taXzgag8BAIKQ==  bisect-rclone.sh&quot;,
    ]
}</code></pre>
<p>See the <a href="https://rclone.org/commands/rclone_hashsum/">hashsum</a> command for more information on the above.</p>
<p><strong>Authentication is required for this call.</strong></p>
<h3 id="operations-list">operations/list: List the given remote and path in JSON format</h3>
<p>This takes the following parameters:</p>
<ul>
<li>fs - a remote name string e.g. "drive:"</li>
<li>remote - a path within that remote e.g. "dir"</li>
<li>opt - a dictionary of options to control the listing (optional)
<ul>
<li>recurse - If set recurse directories</li>
<li>noModTime - If set return modification time</li>
<li>showEncrypted - If set show decrypted names</li>
<li>showOrigIDs - If set show the IDs for each item if known</li>
<li>showHash - If set return a dictionary of hashes</li>
<li>noMimeType - If set don't show mime types</li>
<li>dirsOnly - If set only show directories</li>
<li>filesOnly - If set only show files</li>
<li>metadata - If set return metadata of objects also</li>
<li>hashTypes - array of strings of hash types to show if showHash set</li>
</ul></li>
</ul>
<p>Returns:</p>
<ul>
<li>list
<ul>
<li>This is an array of objects as described in the lsjson command</li>
</ul></li>
</ul>
<p>See the <a href="https://rclone.org/commands/rclone_lsjson/">lsjson</a> command for more information on the above and examples.</p>
<p><strong>Authentication is required for this call.</strong></p>
<h3 id="operations-mkdir">operations/mkdir: Make a destination directory or container</h3>
<p>This takes the following parameters:</p>
<ul>
<li>fs - a remote name string e.g. "drive:"</li>
<li>remote - a path within that remote e.g. "dir"</li>
</ul>
<p>See the <a href="https://rclone.org/commands/rclone_mkdir/">mkdir</a> command for more information on the above.</p>
<p><strong>Authentication is required for this call.</strong></p>
<h3 id="operations-movefile">operations/movefile: Move a file from source remote to destination remote</h3>
<p>This takes the following parameters:</p>
<ul>
<li>srcFs - a remote name string e.g. "drive:" for the source, "/" for local filesystem</li>
<li>srcRemote - a path within that remote e.g. "file.txt" for the source</li>
<li>dstFs - a remote name string e.g. "drive2:" for the destination, "/" for local filesystem</li>
<li>dstRemote - a path within that remote e.g. "file2.txt" for the destination</li>
</ul>
<p><strong>Authentication is required for this call.</strong></p>
<h3 id="operations-publiclink">operations/publiclink: Create or retrieve a public link to the given file or folder.</h3>
<p>This takes the following parameters:</p>
<ul>
<li>fs - a remote name string e.g. "drive:"</li>
<li>remote - a path within that remote e.g. "dir"</li>
<li>unlink - boolean - if set removes the link rather than adding it (optional)</li>
<li>expire - string - the expiry time of the link e.g. "1d" (optional)</li>
</ul>
<p>Returns:</p>
<ul>
<li>url - URL of the resource</li>
</ul>
<p>See the <a href="https://rclone.org/commands/rclone_link/">link</a> command for more information on the above.</p>
<p><strong>Authentication is required for this call.</strong></p>
<h3 id="operations-purge">operations/purge: Remove a directory or container and all of its contents</h3>
<p>This takes the following parameters:</p>
<ul>
<li>fs - a remote name string e.g. "drive:"</li>
<li>remote - a path within that remote e.g. "dir"</li>
</ul>
<p>See the <a href="https://rclone.org/commands/rclone_purge/">purge</a> command for more information on the above.</p>
<p><strong>Authentication is required for this call.</strong></p>
<h3 id="operations-rmdir">operations/rmdir: Remove an empty directory or container</h3>
<p>This takes the following parameters:</p>
<ul>
<li>fs - a remote name string e.g. "drive:"</li>
<li>remote - a path within that remote e.g. "dir"</li>
</ul>
<p>See the <a href="https://rclone.org/commands/rclone_rmdir/">rmdir</a> command for more information on the above.</p>
<p><strong>Authentication is required for this call.</strong></p>
<h3 id="operations-rmdirs">operations/rmdirs: Remove all the empty directories in the path</h3>
<p>This takes the following parameters:</p>
<ul>
<li>fs - a remote name string e.g. "drive:"</li>
<li>remote - a path within that remote e.g. "dir"</li>
<li>leaveRoot - boolean, set to true not to delete the root</li>
</ul>
<p>See the <a href="https://rclone.org/commands/rclone_rmdirs/">rmdirs</a> command for more information on the above.</p>
<p><strong>Authentication is required for this call.</strong></p>
<h3 id="operations-settier">operations/settier: Changes storage tier or class on all files in the path</h3>
<p>This takes the following parameters:</p>
<ul>
<li>fs - a remote name string e.g. "drive:"</li>
</ul>
<p>See the <a href="https://rclone.org/commands/rclone_settier/">settier</a> command for more information on the above.</p>
<p><strong>Authentication is required for this call.</strong></p>
<h3 id="operations-settierfile">operations/settierfile: Changes storage tier or class on the single file pointed to</h3>
<p>This takes the following parameters:</p>
<ul>
<li>fs - a remote name string e.g. "drive:"</li>
<li>remote - a path within that remote e.g. "dir"</li>
</ul>
<p>See the <a href="https://rclone.org/commands/rclone_settierfile/">settierfile</a> command for more information on the above.</p>
<p><strong>Authentication is required for this call.</strong></p>
<h3 id="operations-size">operations/size: Count the number of bytes and files in remote</h3>
<p>This takes the following parameters:</p>
<ul>
<li>fs - a remote name string e.g. "drive:path/to/dir"</li>
</ul>
<p>Returns:</p>
<ul>
<li>count - number of files</li>
<li>bytes - number of bytes in those files</li>
</ul>
<p>See the <a href="https://rclone.org/commands/rclone_size/">size</a> command for more information on the above.</p>
<p><strong>Authentication is required for this call.</strong></p>
<h3 id="operations-stat">operations/stat: Give information about the supplied file or directory</h3>
<p>This takes the following parameters</p>
<ul>
<li>fs - a remote name string eg "drive:"</li>
<li>remote - a path within that remote eg "dir"</li>
<li>opt - a dictionary of options to control the listing (optional)
<ul>
<li>see operations/list for the options</li>
</ul></li>
</ul>
<p>The result is</p>
<ul>
<li>item - an object as described in the lsjson command. Will be null if not found.</li>
</ul>
<p>Note that if you are only interested in files then it is much more efficient to set the filesOnly flag in the options.</p>
<p>See the <a href="https://rclone.org/commands/rclone_lsjson/">lsjson</a> command for more information on the above and examples.</p>
<p><strong>Authentication is required for this call.</strong></p>
<h3 id="operations-uploadfile">operations/uploadfile: Upload file using multiform/form-data</h3>
<p>This takes the following parameters:</p>
<ul>
<li>fs - a remote name string e.g. "drive:"</li>
<li>remote - a path within that remote e.g. "dir"</li>
<li>each part in body represents a file to be uploaded</li>
</ul>
<p>See the <a href="https://rclone.org/commands/rclone_uploadfile/">uploadfile</a> command for more information on the above.</p>
<p><strong>Authentication is required for this call.</strong></p>
<h3 id="options-blocks">options/blocks: List all the option blocks</h3>
<p>Returns: - options - a list of the options block names</p>
<h3 id="options-get">options/get: Get all the global options</h3>
<p>Returns an object where keys are option block names and values are an object with the current option values in.</p>
<p>Parameters:</p>
<ul>
<li>blocks: optional string of comma separated blocks to include
<ul>
<li>all are included if this is missing or ""</li>
</ul></li>
</ul>
<p>Note that these are the global options which are unaffected by use of the _config and _filter parameters. If you wish to read the parameters set in _config then use options/config and for _filter use options/filter.</p>
<p>This shows the internal names of the option within rclone which should map to the external options very easily with a few exceptions.</p>
<h3 id="options-info">options/info: Get info about all the global options</h3>
<p>Returns an object where keys are option block names and values are an array of objects with info about each options.</p>
<p>Parameters:</p>
<ul>
<li>blocks: optional string of comma separated blocks to include
<ul>
<li>all are included if this is missing or ""</li>
</ul></li>
</ul>
<p>These objects are in the same format as returned by "config/providers". They are described in the <a href="#option-blocks">option blocks</a> section.</p>
<h3 id="options-local">options/local: Get the currently active config for this call</h3>
<p>Returns an object with the keys "config" and "filter". The "config" key contains the local config and the "filter" key contains the local filters.</p>
<p>Note that these are the local options specific to this rc call. If _config was not supplied then they will be the global options. Likewise with "_filter".</p>
<p>This call is mostly useful for seeing if _config and _filter passing is working.</p>
<p>This shows the internal names of the option within rclone which should map to the external options very easily with a few exceptions.</p>
<h3 id="options-set">options/set: Set an option</h3>
<p>Parameters:</p>
<ul>
<li>option block name containing an object with
<ul>
<li>key: value</li>
</ul></li>
</ul>
<p>Repeated as often as required.</p>
<p>Only supply the options you wish to change. If an option is unknown it will be silently ignored. Not all options will have an effect when changed like this.</p>
<p>For example:</p>
<p>This sets DEBUG level logs (-vv) (these can be set by number or string)</p>
<pre><code>rclone rc options/set --json &#39;{&quot;main&quot;: {&quot;LogLevel&quot;: &quot;DEBUG&quot;}}&#39;
rclone rc options/set --json &#39;{&quot;main&quot;: {&quot;LogLevel&quot;: 8}}&#39;</code></pre>
<p>And this sets INFO level logs (-v)</p>
<pre><code>rclone rc options/set --json &#39;{&quot;main&quot;: {&quot;LogLevel&quot;: &quot;INFO&quot;}}&#39;</code></pre>
<p>And this sets NOTICE level logs (normal without -v)</p>
<pre><code>rclone rc options/set --json &#39;{&quot;main&quot;: {&quot;LogLevel&quot;: &quot;NOTICE&quot;}}&#39;</code></pre>
<h3 id="pluginsctl-addPlugin">pluginsctl/addPlugin: Add a plugin using url</h3>
<p>Used for adding a plugin to the webgui.</p>
<p>This takes the following parameters:</p>
<ul>
<li>url - http url of the github repo where the plugin is hosted (http://github.com/rclone/rclone-webui-react).</li>
</ul>
<p>Example:</p>
<p>rclone rc pluginsctl/addPlugin</p>
<p><strong>Authentication is required for this call.</strong></p>
<h3 id="pluginsctl-getPluginsForType">pluginsctl/getPluginsForType: Get plugins with type criteria</h3>
<p>This shows all possible plugins by a mime type.</p>
<p>This takes the following parameters:</p>
<ul>
<li>type - supported mime type by a loaded plugin e.g. (video/mp4, audio/mp3).</li>
<li>pluginType - filter plugins based on their type e.g. (DASHBOARD, FILE_HANDLER, TERMINAL).</li>
</ul>
<p>Returns:</p>
<ul>
<li>loadedPlugins - list of current production plugins.</li>
<li>testPlugins - list of temporarily loaded development plugins, usually running on a different server.</li>
</ul>
<p>Example:</p>
<p>rclone rc pluginsctl/getPluginsForType type=video/mp4</p>
<p><strong>Authentication is required for this call.</strong></p>
<h3 id="pluginsctl-listPlugins">pluginsctl/listPlugins: Get the list of currently loaded plugins</h3>
<p>This allows you to get the currently enabled plugins and their details.</p>
<p>This takes no parameters and returns:</p>
<ul>
<li>loadedPlugins - list of current production plugins.</li>
<li>testPlugins - list of temporarily loaded development plugins, usually running on a different server.</li>
</ul>
<p>E.g.</p>
<p>rclone rc pluginsctl/listPlugins</p>
<p><strong>Authentication is required for this call.</strong></p>
<h3 id="pluginsctl-listTestPlugins">pluginsctl/listTestPlugins: Show currently loaded test plugins</h3>
<p>Allows listing of test plugins with the rclone.test set to true in package.json of the plugin.</p>
<p>This takes no parameters and returns:</p>
<ul>
<li>loadedTestPlugins - list of currently available test plugins.</li>
</ul>
<p>E.g.</p>
<pre><code>rclone rc pluginsctl/listTestPlugins</code></pre>
<p><strong>Authentication is required for this call.</strong></p>
<h3 id="pluginsctl-removePlugin">pluginsctl/removePlugin: Remove a loaded plugin</h3>
<p>This allows you to remove a plugin using it's name.</p>
<p>This takes parameters:</p>
<ul>
<li>name - name of the plugin in the format <code>author</code>/<code>plugin_name</code>.</li>
</ul>
<p>E.g.</p>
<p>rclone rc pluginsctl/removePlugin name=rclone/video-plugin</p>
<p><strong>Authentication is required for this call.</strong></p>
<h3 id="pluginsctl-removeTestPlugin">pluginsctl/removeTestPlugin: Remove a test plugin</h3>
<p>This allows you to remove a plugin using it's name.</p>
<p>This takes the following parameters:</p>
<ul>
<li>name - name of the plugin in the format <code>author</code>/<code>plugin_name</code>.</li>
</ul>
<p>Example:</p>
<pre><code>rclone rc pluginsctl/removeTestPlugin name=rclone/rclone-webui-react</code></pre>
<p><strong>Authentication is required for this call.</strong></p>
<h3 id="rc-error">rc/error: This returns an error</h3>
<p>This returns an error with the input as part of its error string. Useful for testing error handling.</p>
<h3 id="rc-list">rc/list: List all the registered remote control commands</h3>
<p>This lists all the registered remote control commands as a JSON map in the commands response.</p>
<h3 id="rc-noop">rc/noop: Echo the input to the output parameters</h3>
<p>This echoes the input parameters to the output parameters for testing purposes. It can be used to check that rclone is still alive and to check that parameter passing is working properly.</p>
<h3 id="rc-noopauth">rc/noopauth: Echo the input to the output parameters requiring auth</h3>
<p>This echoes the input parameters to the output parameters for testing purposes. It can be used to check that rclone is still alive and to check that parameter passing is working properly.</p>
<p><strong>Authentication is required for this call.</strong></p>
<h3 id="sync-bisync">sync/bisync: Perform bidirectional synchronization between two paths.</h3>
<p>This takes the following parameters</p>
<ul>
<li>path1 - a remote directory string e.g. <code>drive:path1</code></li>
<li>path2 - a remote directory string e.g. <code>drive:path2</code></li>
<li>dryRun - dry-run mode</li>
<li>resync - performs the resync run</li>
<li>checkAccess - abort if RCLONE_TEST files are not found on both filesystems</li>
<li>checkFilename - file name for checkAccess (default: RCLONE_TEST)</li>
<li>maxDelete - abort sync if percentage of deleted files is above this threshold (default: 50)</li>
<li>force - Bypass maxDelete safety check and run the sync</li>
<li>checkSync - <code>true</code> by default, <code>false</code> disables comparison of final listings, <code>only</code> will skip sync, only compare listings from the last run</li>
<li>createEmptySrcDirs - Sync creation and deletion of empty directories. (Not compatible with --remove-empty-dirs)</li>
<li>removeEmptyDirs - remove empty directories at the final cleanup step</li>
<li>filtersFile - read filtering patterns from a file</li>
<li>ignoreListingChecksum - Do not use checksums for listings</li>
<li>resilient - Allow future runs to retry after certain less-serious errors, instead of requiring resync. Use at your own risk!</li>
<li>workdir - server directory for history files (default: <code>~/.cache/rclone/bisync</code>)</li>
<li>backupdir1 - --backup-dir for Path1. Must be a non-overlapping path on the same remote.</li>
<li>backupdir2 - --backup-dir for Path2. Must be a non-overlapping path on the same remote.</li>
<li>noCleanup - retain working files</li>
</ul>
<p>See <a href="https://rclone.org/commands/rclone_bisync/">bisync command help</a> and <a href="https://rclone.org/bisync/">full bisync description</a> for more information.</p>
<p><strong>Authentication is required for this call.</strong></p>
<h3 id="sync-copy">sync/copy: copy a directory from source remote to destination remote</h3>
<p>This takes the following parameters:</p>
<ul>
<li>srcFs - a remote name string e.g. "drive:src" for the source</li>
<li>dstFs - a remote name string e.g. "drive:dst" for the destination</li>
<li>createEmptySrcDirs - create empty src directories on destination if set</li>
</ul>
<p>See the <a href="https://rclone.org/commands/rclone_copy/">copy</a> command for more information on the above.</p>
<p><strong>Authentication is required for this call.</strong></p>
<h3 id="sync-move">sync/move: move a directory from source remote to destination remote</h3>
<p>This takes the following parameters:</p>
<ul>
<li>srcFs - a remote name string e.g. "drive:src" for the source</li>
<li>dstFs - a remote name string e.g. "drive:dst" for the destination</li>
<li>createEmptySrcDirs - create empty src directories on destination if set</li>
<li>deleteEmptySrcDirs - delete empty src directories if set</li>
</ul>
<p>See the <a href="https://rclone.org/commands/rclone_move/">move</a> command for more information on the above.</p>
<p><strong>Authentication is required for this call.</strong></p>
<h3 id="sync-sync">sync/sync: sync a directory from source remote to destination remote</h3>
<p>This takes the following parameters:</p>
<ul>
<li>srcFs - a remote name string e.g. "drive:src" for the source</li>
<li>dstFs - a remote name string e.g. "drive:dst" for the destination</li>
<li>createEmptySrcDirs - create empty src directories on destination if set</li>
</ul>
<p>See the <a href="https://rclone.org/commands/rclone_sync/">sync</a> command for more information on the above.</p>
<p><strong>Authentication is required for this call.</strong></p>
<h3 id="vfs-forget">vfs/forget: Forget files or directories in the directory cache.</h3>
<p>This forgets the paths in the directory cache causing them to be re-read from the remote when needed.</p>
<p>If no paths are passed in then it will forget all the paths in the directory cache.</p>
<pre><code>rclone rc vfs/forget</code></pre>
<p>Otherwise pass files or dirs in as file=path or dir=path. Any parameter key starting with file will forget that file and any starting with dir will forget that dir, e.g.</p>
<pre><code>rclone rc vfs/forget file=hello file2=goodbye dir=home/junk</code></pre>
<p>This command takes an "fs" parameter. If this parameter is not supplied and if there is only one VFS in use then that VFS will be used. If there is more than one VFS in use then the "fs" parameter must be supplied.</p>
<h3 id="vfs-list">vfs/list: List active VFSes.</h3>
<p>This lists the active VFSes.</p>
<p>It returns a list under the key "vfses" where the values are the VFS names that could be passed to the other VFS commands in the "fs" parameter.</p>
<h3 id="vfs-poll-interval">vfs/poll-interval: Get the status or update the value of the poll-interval option.</h3>
<p>Without any parameter given this returns the current status of the poll-interval setting.</p>
<p>When the interval=duration parameter is set, the poll-interval value is updated and the polling function is notified. Setting interval=0 disables poll-interval.</p>
<pre><code>rclone rc vfs/poll-interval interval=5m</code></pre>
<p>The timeout=duration parameter can be used to specify a time to wait for the current poll function to apply the new value. If timeout is less or equal 0, which is the default, wait indefinitely.</p>
<p>The new poll-interval value will only be active when the timeout is not reached.</p>
<p>If poll-interval is updated or disabled temporarily, some changes might not get picked up by the polling function, depending on the used remote.</p>
<p>This command takes an "fs" parameter. If this parameter is not supplied and if there is only one VFS in use then that VFS will be used. If there is more than one VFS in use then the "fs" parameter must be supplied.</p>
<h3 id="vfs-queue">vfs/queue: Queue info for a VFS.</h3>
<p>This returns info about the upload queue for the selected VFS.</p>
<p>This is only useful if <code>--vfs-cache-mode</code> &gt; off. If you call it when the <code>--vfs-cache-mode</code> is off, it will return an empty result.</p>
<pre><code>{
    &quot;queued&quot;: // an array of files queued for upload
    [
        {
            &quot;name&quot;:      &quot;file&quot;,   // string: name (full path) of the file,
            &quot;id&quot;:        123,      // integer: id of this item in the queue,
            &quot;size&quot;:      79,       // integer: size of the file in bytes
            &quot;expiry&quot;:    1.5       // float: time until file is eligible for transfer, lowest goes first
            &quot;tries&quot;:     1,        // integer: number of times we have tried to upload
            &quot;delay&quot;:     5.0,      // float: seconds between upload attempts
            &quot;uploading&quot;: false,    // boolean: true if item is being uploaded
        },
   ],
}</code></pre>
<p>The <code>expiry</code> time is the time until the file is elegible for being uploaded in floating point seconds. This may go negative. As rclone only transfers <code>--transfers</code> files at once, only the lowest <code>--transfers</code> expiry times will have <code>uploading</code> as <code>true</code>. So there may be files with negative expiry times for which <code>uploading</code> is <code>false</code>.</p>
<p>This command takes an "fs" parameter. If this parameter is not supplied and if there is only one VFS in use then that VFS will be used. If there is more than one VFS in use then the "fs" parameter must be supplied.</p>
<h3 id="vfs-queue-set-expiry">vfs/queue-set-expiry: Set the expiry time for an item queued for upload.</h3>
<p>Use this to adjust the <code>expiry</code> time for an item in the upload queue. You will need to read the <code>id</code> of the item using <code>vfs/queue</code> before using this call.</p>
<p>You can then set <code>expiry</code> to a floating point number of seconds from now when the item is eligible for upload. If you want the item to be uploaded as soon as possible then set it to a large negative number (eg -1000000000). If you want the upload of the item to be delayed for a long time then set it to a large positive number.</p>
<p>Setting the <code>expiry</code> of an item which has already has started uploading will have no effect - the item will carry on being uploaded.</p>
<p>This will return an error if called with <code>--vfs-cache-mode</code> off or if the <code>id</code> passed is not found.</p>
<p>This takes the following parameters</p>
<ul>
<li><code>fs</code> - select the VFS in use (optional)</li>
<li><code>id</code> - a numeric ID as returned from <code>vfs/queue</code></li>
<li><code>expiry</code> - a new expiry time as floating point seconds</li>
</ul>
<p>This returns an empty result on success, or an error.</p>
<p>This command takes an "fs" parameter. If this parameter is not supplied and if there is only one VFS in use then that VFS will be used. If there is more than one VFS in use then the "fs" parameter must be supplied.</p>
<h3 id="vfs-refresh">vfs/refresh: Refresh the directory cache.</h3>
<p>This reads the directories for the specified paths and freshens the directory cache.</p>
<p>If no paths are passed in then it will refresh the root directory.</p>
<pre><code>rclone rc vfs/refresh</code></pre>
<p>Otherwise pass directories in as dir=path. Any parameter key starting with dir will refresh that directory, e.g.</p>
<pre><code>rclone rc vfs/refresh dir=home/junk dir2=data/misc</code></pre>
<p>If the parameter recursive=true is given the whole directory tree will get refreshed. This refresh will use --fast-list if enabled.</p>
<p>This command takes an "fs" parameter. If this parameter is not supplied and if there is only one VFS in use then that VFS will be used. If there is more than one VFS in use then the "fs" parameter must be supplied.</p>
<h3 id="vfs-stats">vfs/stats: Stats for a VFS.</h3>
<p>This returns stats for the selected VFS.</p>
<pre><code>{
    // Status of the disk cache - only present if --vfs-cache-mode &gt; off
    &quot;diskCache&quot;: {
        &quot;bytesUsed&quot;: 0,
        &quot;erroredFiles&quot;: 0,
        &quot;files&quot;: 0,
        &quot;hashType&quot;: 1,
        &quot;outOfSpace&quot;: false,
        &quot;path&quot;: &quot;/home/user/.cache/rclone/vfs/local/mnt/a&quot;,
        &quot;pathMeta&quot;: &quot;/home/user/.cache/rclone/vfsMeta/local/mnt/a&quot;,
        &quot;uploadsInProgress&quot;: 0,
        &quot;uploadsQueued&quot;: 0
    },
    &quot;fs&quot;: &quot;/mnt/a&quot;,
    &quot;inUse&quot;: 1,
    // Status of the in memory metadata cache
    &quot;metadataCache&quot;: {
        &quot;dirs&quot;: 1,
        &quot;files&quot;: 0
    },
    // Options as returned by options/get
    &quot;opt&quot;: {
        &quot;CacheMaxAge&quot;: 3600000000000,
        // ...
        &quot;WriteWait&quot;: 1000000000
    }
}</code></pre>
<p>This command takes an "fs" parameter. If this parameter is not supplied and if there is only one VFS in use then that VFS will be used. If there is more than one VFS in use then the "fs" parameter must be supplied.</p>
<h2 id="api-http">Accessing the remote control via HTTP</h2>
<p>Rclone implements a simple HTTP based protocol.</p>
<p>Each endpoint takes an JSON object and returns a JSON object or an error. The JSON objects are essentially a map of string names to values.</p>
<p>All calls must made using POST.</p>
<p>The input objects can be supplied using URL parameters, POST parameters or by supplying "Content-Type: application/json" and a JSON blob in the body. There are examples of these below using <code>curl</code>.</p>
<p>The response will be a JSON blob in the body of the response. This is formatted to be reasonably human-readable.</p>
<h3 id="error-returns">Error returns</h3>
<p>If an error occurs then there will be an HTTP error status (e.g. 500) and the body of the response will contain a JSON encoded error object, e.g.</p>
<pre><code>{
    &quot;error&quot;: &quot;Expecting string value for key \&quot;remote\&quot; (was float64)&quot;,
    &quot;input&quot;: {
        &quot;fs&quot;: &quot;/tmp&quot;,
        &quot;remote&quot;: 3
    },
    &quot;status&quot;: 400
    &quot;path&quot;: &quot;operations/rmdir&quot;,
}</code></pre>
<p>The keys in the error response are - error - error string - input - the input parameters to the call - status - the HTTP status code - path - the path of the call</p>
<h3 id="cors">CORS</h3>
<p>The sever implements basic CORS support and allows all origins for that. The response to a preflight OPTIONS request will echo the requested "Access-Control-Request-Headers" back.</p>
<h3 id="using-post-with-url-parameters-only">Using POST with URL parameters only</h3>
<pre><code>curl -X POST &#39;http://localhost:5572/rc/noop?potato=1&amp;sausage=2&#39;</code></pre>
<p>Response</p>
<pre><code>{
    &quot;potato&quot;: &quot;1&quot;,
    &quot;sausage&quot;: &quot;2&quot;
}</code></pre>
<p>Here is what an error response looks like:</p>
<pre><code>curl -X POST &#39;http://localhost:5572/rc/error?potato=1&amp;sausage=2&#39;</code></pre>
<pre><code>{
    &quot;error&quot;: &quot;arbitrary error on input map[potato:1 sausage:2]&quot;,
    &quot;input&quot;: {
        &quot;potato&quot;: &quot;1&quot;,
        &quot;sausage&quot;: &quot;2&quot;
    }
}</code></pre>
<p>Note that curl doesn't return errors to the shell unless you use the <code>-f</code> option</p>
<pre><code>$ curl -f -X POST &#39;http://localhost:5572/rc/error?potato=1&amp;sausage=2&#39;
curl: (22) The requested URL returned error: 400 Bad Request
$ echo $?
22</code></pre>
<h3 id="using-post-with-a-form">Using POST with a form</h3>
<pre><code>curl --data &quot;potato=1&quot; --data &quot;sausage=2&quot; http://localhost:5572/rc/noop</code></pre>
<p>Response</p>
<pre><code>{
    &quot;potato&quot;: &quot;1&quot;,
    &quot;sausage&quot;: &quot;2&quot;
}</code></pre>
<p>Note that you can combine these with URL parameters too with the POST parameters taking precedence.</p>
<pre><code>curl --data &quot;potato=1&quot; --data &quot;sausage=2&quot; &quot;http://localhost:5572/rc/noop?rutabaga=3&amp;sausage=4&quot;</code></pre>
<p>Response</p>
<pre><code>{
    &quot;potato&quot;: &quot;1&quot;,
    &quot;rutabaga&quot;: &quot;3&quot;,
    &quot;sausage&quot;: &quot;4&quot;
}
</code></pre>
<h3 id="using-post-with-a-json-blob">Using POST with a JSON blob</h3>
<pre><code>curl -H &quot;Content-Type: application/json&quot; -X POST -d &#39;{&quot;potato&quot;:2,&quot;sausage&quot;:1}&#39; http://localhost:5572/rc/noop</code></pre>
<p>response</p>
<pre><code>{
    &quot;password&quot;: &quot;xyz&quot;,
    &quot;username&quot;: &quot;xyz&quot;
}</code></pre>
<p>This can be combined with URL parameters too if required. The JSON blob takes precedence.</p>
<pre><code>curl -H &quot;Content-Type: application/json&quot; -X POST -d &#39;{&quot;potato&quot;:2,&quot;sausage&quot;:1}&#39; &#39;http://localhost:5572/rc/noop?rutabaga=3&amp;potato=4&#39;</code></pre>
<pre><code>{
    &quot;potato&quot;: 2,
    &quot;rutabaga&quot;: &quot;3&quot;,
    &quot;sausage&quot;: 1
}</code></pre>
<h2 id="debugging-rclone-with-pprof">Debugging rclone with pprof</h2>
<p>If you use the <code>--rc</code> flag this will also enable the use of the go profiling tools on the same port.</p>
<p>To use these, first <a href="https://golang.org/doc/install">install go</a>.</p>
<h3 id="debugging-memory-use">Debugging memory use</h3>
<p>To profile rclone's memory use you can run:</p>
<pre><code>go tool pprof -web http://localhost:5572/debug/pprof/heap</code></pre>
<p>This should open a page in your browser showing what is using what memory.</p>
<p>You can also use the <code>-text</code> flag to produce a textual summary</p>
<pre><code>$ go tool pprof -text http://localhost:5572/debug/pprof/heap
Showing nodes accounting for 1537.03kB, 100% of 1537.03kB total
      flat  flat%   sum%        cum   cum%
 1024.03kB 66.62% 66.62%  1024.03kB 66.62%  github.com/rclone/rclone/vendor/golang.org/x/net/http2/hpack.addDecoderNode
     513kB 33.38%   100%      513kB 33.38%  net/http.newBufioWriterSize
         0     0%   100%  1024.03kB 66.62%  github.com/rclone/rclone/cmd/all.init
         0     0%   100%  1024.03kB 66.62%  github.com/rclone/rclone/cmd/serve.init
         0     0%   100%  1024.03kB 66.62%  github.com/rclone/rclone/cmd/serve/restic.init
         0     0%   100%  1024.03kB 66.62%  github.com/rclone/rclone/vendor/golang.org/x/net/http2.init
         0     0%   100%  1024.03kB 66.62%  github.com/rclone/rclone/vendor/golang.org/x/net/http2/hpack.init
         0     0%   100%  1024.03kB 66.62%  github.com/rclone/rclone/vendor/golang.org/x/net/http2/hpack.init.0
         0     0%   100%  1024.03kB 66.62%  main.init
         0     0%   100%      513kB 33.38%  net/http.(*conn).readRequest
         0     0%   100%      513kB 33.38%  net/http.(*conn).serve
         0     0%   100%  1024.03kB 66.62%  runtime.main</code></pre>
<h3 id="debugging-go-routine-leaks">Debugging go routine leaks</h3>
<p>Memory leaks are most often caused by go routine leaks keeping memory alive which should have been garbage collected.</p>
<p>See all active go routines using</p>
<pre><code>curl http://localhost:5572/debug/pprof/goroutine?debug=1</code></pre>
<p>Or go to http://localhost:5572/debug/pprof/goroutine?debug=1 in your browser.</p>
<h3 id="other-profiles-to-look-at">Other profiles to look at</h3>
<p>You can see a summary of profiles available at http://localhost:5572/debug/pprof/</p>
<p>Here is how to use some of them:</p>
<ul>
<li>Memory: <code>go tool pprof http://localhost:5572/debug/pprof/heap</code></li>
<li>Go routines: <code>curl http://localhost:5572/debug/pprof/goroutine?debug=1</code></li>
<li>30-second CPU profile: <code>go tool pprof http://localhost:5572/debug/pprof/profile</code></li>
<li>5-second execution trace: <code>wget http://localhost:5572/debug/pprof/trace?seconds=5</code></li>
<li>Goroutine blocking profile
<ul>
<li>Enable first with: <code>rclone rc debug/set-block-profile-rate rate=1</code> (<a href="#debug-set-block-profile-rate">docs</a>)</li>
<li><code>go tool pprof http://localhost:5572/debug/pprof/block</code></li>
</ul></li>
<li>Contended mutexes:
<ul>
<li>Enable first with: <code>rclone rc debug/set-mutex-profile-fraction rate=1</code> (<a href="#debug-set-mutex-profile-fraction">docs</a>)</li>
<li><code>go tool pprof http://localhost:5572/debug/pprof/mutex</code></li>
</ul></li>
</ul>
<p>See the <a href="https://golang.org/pkg/net/http/pprof/">net/http/pprof docs</a> for more info on how to use the profiling and for a general overview see <a href="https://blog.golang.org/profiling-go-programs">the Go team's blog post on profiling go programs</a>.</p>
<p>The profiling hook is <a href="https://stackoverflow.com/q/26545159/164234">zero overhead unless it is used</a>.</p>
<h1 id="overview-of-cloud-storage-systems">Overview of cloud storage systems</h1>
<p>Each cloud storage system is slightly different. Rclone attempts to provide a unified interface to them, but some underlying differences show through.</p>
<h2 id="features-1">Features</h2>
<p>Here is an overview of the major features of each cloud storage system.</p>
<table>
<thead>
<tr class="header">
<th>Name</th>
<th style="text-align: center;">Hash</th>
<th style="text-align: center;">ModTime</th>
<th style="text-align: center;">Case Insensitive</th>
<th style="text-align: center;">Duplicate Files</th>
<th style="text-align: center;">MIME Type</th>
<th style="text-align: center;">Metadata</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td>1Fichier</td>
<td style="text-align: center;">Whirlpool</td>
<td style="text-align: center;">-</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">R</td>
<td style="text-align: center;">-</td>
</tr>
<tr class="even">
<td>Akamai Netstorage</td>
<td style="text-align: center;">MD5, SHA256</td>
<td style="text-align: center;">R/W</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">R</td>
<td style="text-align: center;">-</td>
</tr>
<tr class="odd">
<td>Amazon S3 (or S3 compatible)</td>
<td style="text-align: center;">MD5</td>
<td style="text-align: center;">R/W</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">R/W</td>
<td style="text-align: center;">RWU</td>
</tr>
<tr class="even">
<td>Backblaze B2</td>
<td style="text-align: center;">SHA1</td>
<td style="text-align: center;">R/W</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">R/W</td>
<td style="text-align: center;">-</td>
</tr>
<tr class="odd">
<td>Box</td>
<td style="text-align: center;">SHA1</td>
<td style="text-align: center;">R/W</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">-</td>
<td style="text-align: center;">-</td>
</tr>
<tr class="even">
<td>Citrix ShareFile</td>
<td style="text-align: center;">MD5</td>
<td style="text-align: center;">R/W</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">-</td>
<td style="text-align: center;">-</td>
</tr>
<tr class="odd">
<td>Dropbox</td>
<td style="text-align: center;">DBHASH ¹</td>
<td style="text-align: center;">R</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">-</td>
<td style="text-align: center;">-</td>
</tr>
<tr class="even">
<td>Enterprise File Fabric</td>
<td style="text-align: center;">-</td>
<td style="text-align: center;">R/W</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">R/W</td>
<td style="text-align: center;">-</td>
</tr>
<tr class="odd">
<td>Files.com</td>
<td style="text-align: center;">MD5, CRC32</td>
<td style="text-align: center;">DR/W</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">R</td>
<td style="text-align: center;">-</td>
</tr>
<tr class="even">
<td>FTP</td>
<td style="text-align: center;">-</td>
<td style="text-align: center;">R/W ¹⁰</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">-</td>
<td style="text-align: center;">-</td>
</tr>
<tr class="odd">
<td>Gofile</td>
<td style="text-align: center;">MD5</td>
<td style="text-align: center;">DR/W</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">R</td>
<td style="text-align: center;">-</td>
</tr>
<tr class="even">
<td>Google Cloud Storage</td>
<td style="text-align: center;">MD5</td>
<td style="text-align: center;">R/W</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">R/W</td>
<td style="text-align: center;">-</td>
</tr>
<tr class="odd">
<td>Google Drive</td>
<td style="text-align: center;">MD5, SHA1, SHA256</td>
<td style="text-align: center;">DR/W</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">R/W</td>
<td style="text-align: center;">DRWU</td>
</tr>
<tr class="even">
<td>Google Photos</td>
<td style="text-align: center;">-</td>
<td style="text-align: center;">-</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">R</td>
<td style="text-align: center;">-</td>
</tr>
<tr class="odd">
<td>HDFS</td>
<td style="text-align: center;">-</td>
<td style="text-align: center;">R/W</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">-</td>
<td style="text-align: center;">-</td>
</tr>
<tr class="even">
<td>HiDrive</td>
<td style="text-align: center;">HiDrive ¹²</td>
<td style="text-align: center;">R/W</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">-</td>
<td style="text-align: center;">-</td>
</tr>
<tr class="odd">
<td>HTTP</td>
<td style="text-align: center;">-</td>
<td style="text-align: center;">R</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">R</td>
<td style="text-align: center;">-</td>
</tr>
<tr class="even">
<td>Internet Archive</td>
<td style="text-align: center;">MD5, SHA1, CRC32</td>
<td style="text-align: center;">R/W ¹¹</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">-</td>
<td style="text-align: center;">RWU</td>
</tr>
<tr class="odd">
<td>Jottacloud</td>
<td style="text-align: center;">MD5</td>
<td style="text-align: center;">R/W</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">R</td>
<td style="text-align: center;">RW</td>
</tr>
<tr class="even">
<td>Koofr</td>
<td style="text-align: center;">MD5</td>
<td style="text-align: center;">-</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">-</td>
<td style="text-align: center;">-</td>
</tr>
<tr class="odd">
<td>Linkbox</td>
<td style="text-align: center;">-</td>
<td style="text-align: center;">R</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">-</td>
<td style="text-align: center;">-</td>
</tr>
<tr class="even">
<td>Mail.ru Cloud</td>
<td style="text-align: center;">Mailru ⁶</td>
<td style="text-align: center;">R/W</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">-</td>
<td style="text-align: center;">-</td>
</tr>
<tr class="odd">
<td>Mega</td>
<td style="text-align: center;">-</td>
<td style="text-align: center;">-</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">-</td>
<td style="text-align: center;">-</td>
</tr>
<tr class="even">
<td>Memory</td>
<td style="text-align: center;">MD5</td>
<td style="text-align: center;">R/W</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">-</td>
<td style="text-align: center;">-</td>
</tr>
<tr class="odd">
<td>Microsoft Azure Blob Storage</td>
<td style="text-align: center;">MD5</td>
<td style="text-align: center;">R/W</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">R/W</td>
<td style="text-align: center;">-</td>
</tr>
<tr class="even">
<td>Microsoft Azure Files Storage</td>
<td style="text-align: center;">MD5</td>
<td style="text-align: center;">R/W</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">R/W</td>
<td style="text-align: center;">-</td>
</tr>
<tr class="odd">
<td>Microsoft OneDrive</td>
<td style="text-align: center;">QuickXorHash ⁵</td>
<td style="text-align: center;">DR/W</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">R</td>
<td style="text-align: center;">DRW</td>
</tr>
<tr class="even">
<td>OpenDrive</td>
<td style="text-align: center;">MD5</td>
<td style="text-align: center;">R/W</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Partial ⁸</td>
<td style="text-align: center;">-</td>
<td style="text-align: center;">-</td>
</tr>
<tr class="odd">
<td>OpenStack Swift</td>
<td style="text-align: center;">MD5</td>
<td style="text-align: center;">R/W</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">R/W</td>
<td style="text-align: center;">-</td>
</tr>
<tr class="even">
<td>Oracle Object Storage</td>
<td style="text-align: center;">MD5</td>
<td style="text-align: center;">R/W</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">R/W</td>
<td style="text-align: center;">-</td>
</tr>
<tr class="odd">
<td>pCloud</td>
<td style="text-align: center;">MD5, SHA1 ⁷</td>
<td style="text-align: center;">R/W</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">W</td>
<td style="text-align: center;">-</td>
</tr>
<tr class="even">
<td>PikPak</td>
<td style="text-align: center;">MD5</td>
<td style="text-align: center;">R</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">R</td>
<td style="text-align: center;">-</td>
</tr>
<tr class="odd">
<td>Pixeldrain</td>
<td style="text-align: center;">SHA256</td>
<td style="text-align: center;">R/W</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">R</td>
<td style="text-align: center;">RW</td>
</tr>
<tr class="even">
<td>premiumize.me</td>
<td style="text-align: center;">-</td>
<td style="text-align: center;">-</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">R</td>
<td style="text-align: center;">-</td>
</tr>
<tr class="odd">
<td>put.io</td>
<td style="text-align: center;">CRC-32</td>
<td style="text-align: center;">R/W</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">R</td>
<td style="text-align: center;">-</td>
</tr>
<tr class="even">
<td>Proton Drive</td>
<td style="text-align: center;">SHA1</td>
<td style="text-align: center;">R/W</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">R</td>
<td style="text-align: center;">-</td>
</tr>
<tr class="odd">
<td>QingStor</td>
<td style="text-align: center;">MD5</td>
<td style="text-align: center;">- ⁹</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">R/W</td>
<td style="text-align: center;">-</td>
</tr>
<tr class="even">
<td>Quatrix by Maytech</td>
<td style="text-align: center;">-</td>
<td style="text-align: center;">R/W</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">-</td>
<td style="text-align: center;">-</td>
</tr>
<tr class="odd">
<td>Seafile</td>
<td style="text-align: center;">-</td>
<td style="text-align: center;">-</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">-</td>
<td style="text-align: center;">-</td>
</tr>
<tr class="even">
<td>SFTP</td>
<td style="text-align: center;">MD5, SHA1 ²</td>
<td style="text-align: center;">DR/W</td>
<td style="text-align: center;">Depends</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">-</td>
<td style="text-align: center;">-</td>
</tr>
<tr class="odd">
<td>Sia</td>
<td style="text-align: center;">-</td>
<td style="text-align: center;">-</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">-</td>
<td style="text-align: center;">-</td>
</tr>
<tr class="even">
<td>SMB</td>
<td style="text-align: center;">-</td>
<td style="text-align: center;">R/W</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">-</td>
<td style="text-align: center;">-</td>
</tr>
<tr class="odd">
<td>SugarSync</td>
<td style="text-align: center;">-</td>
<td style="text-align: center;">-</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">-</td>
<td style="text-align: center;">-</td>
</tr>
<tr class="even">
<td>Storj</td>
<td style="text-align: center;">-</td>
<td style="text-align: center;">R</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">-</td>
<td style="text-align: center;">-</td>
</tr>
<tr class="odd">
<td>Uloz.to</td>
<td style="text-align: center;">MD5, SHA256 ¹³</td>
<td style="text-align: center;">-</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">-</td>
<td style="text-align: center;">-</td>
</tr>
<tr class="even">
<td>Uptobox</td>
<td style="text-align: center;">-</td>
<td style="text-align: center;">-</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">-</td>
<td style="text-align: center;">-</td>
</tr>
<tr class="odd">
<td>WebDAV</td>
<td style="text-align: center;">MD5, SHA1 ³</td>
<td style="text-align: center;">R ⁴</td>
<td style="text-align: center;">Depends</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">-</td>
<td style="text-align: center;">-</td>
</tr>
<tr class="even">
<td>Yandex Disk</td>
<td style="text-align: center;">MD5</td>
<td style="text-align: center;">R/W</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">R</td>
<td style="text-align: center;">-</td>
</tr>
<tr class="odd">
<td>Zoho WorkDrive</td>
<td style="text-align: center;">-</td>
<td style="text-align: center;">-</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">-</td>
<td style="text-align: center;">-</td>
</tr>
<tr class="even">
<td>The local filesystem</td>
<td style="text-align: center;">All</td>
<td style="text-align: center;">DR/W</td>
<td style="text-align: center;">Depends</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">-</td>
<td style="text-align: center;">DRWU</td>
</tr>
</tbody>
</table>
<p>¹ Dropbox supports <a href="https://www.dropbox.com/developers/reference/content-hash">its own custom hash</a>. This is an SHA256 sum of all the 4 MiB block SHA256s.</p>
<p>² SFTP supports checksums if the same login has shell access and <code>md5sum</code> or <code>sha1sum</code> as well as <code>echo</code> are in the remote's PATH.</p>
<p>³ WebDAV supports hashes when used with Fastmail Files, Owncloud and Nextcloud only.</p>
<p>⁴ WebDAV supports modtimes when used with Fastmail Files, Owncloud and Nextcloud only.</p>
<p>⁵ <a href="https://docs.microsoft.com/en-us/onedrive/developer/code-snippets/quickxorhash">QuickXorHash</a> is Microsoft's own hash.</p>
<p>⁶ Mail.ru uses its own modified SHA1 hash</p>
<p>⁷ pCloud only supports SHA1 (not MD5) in its EU region</p>
<p>⁸ Opendrive does not support creation of duplicate files using their web client interface or other stock clients, but the underlying storage platform has been determined to allow duplicate files, and it is possible to create them with <code>rclone</code>. It may be that this is a mistake or an unsupported feature.</p>
<p>⁹ QingStor does not support SetModTime for objects bigger than 5 GiB.</p>
<p>¹⁰ FTP supports modtimes for the major FTP servers, and also others if they advertised required protocol extensions. See <a href="https://rclone.org/ftp/#modification-times">this</a> for more details.</p>
<p>¹¹ Internet Archive requires option <code>wait_archive</code> to be set to a non-zero value for full modtime support.</p>
<p>¹² HiDrive supports <a href="https://static.hidrive.com/dev/0001">its own custom hash</a>. It combines SHA1 sums for each 4 KiB block hierarchically to a single top-level sum.</p>
<p>¹³ Uloz.to provides server-calculated MD5 hash upon file upload. MD5 and SHA256 hashes are client-calculated and stored as metadata fields.</p>
<h3 id="hash">Hash</h3>
<p>The cloud storage system supports various hash types of the objects. The hashes are used when transferring data as an integrity check and can be specifically used with the <code>--checksum</code> flag in syncs and in the <code>check</code> command.</p>
<p>To use the verify checksums when transferring between cloud storage systems they must support a common hash type.</p>
<h3 id="modtime">ModTime</h3>
<p>Almost all cloud storage systems store some sort of timestamp on objects, but several of them not something that is appropriate to use for syncing. E.g. some backends will only write a timestamp that represents the time of the upload. To be relevant for syncing it should be able to store the modification time of the source object. If this is not the case, rclone will only check the file size by default, though can be configured to check the file hash (with the <code>--checksum</code> flag). Ideally it should also be possible to change the timestamp of an existing file without having to re-upload it.</p>
<table>
<colgroup>
<col style="width: 27%" />
<col style="width: 72%" />
</colgroup>
<thead>
<tr class="header">
<th>Key</th>
<th>Explanation</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td><code>-</code></td>
<td>ModTimes not supported - times likely the upload time</td>
</tr>
<tr class="even">
<td><code>R</code></td>
<td>ModTimes supported on files but can't be changed without re-upload</td>
</tr>
<tr class="odd">
<td><code>R/W</code></td>
<td>Read and Write ModTimes fully supported on files</td>
</tr>
<tr class="even">
<td><code>DR</code></td>
<td>ModTimes supported on files and directories but can't be changed without re-upload</td>
</tr>
<tr class="odd">
<td><code>DR/W</code></td>
<td>Read and Write ModTimes fully supported on files and directories</td>
</tr>
</tbody>
</table>
<p>Storage systems with a <code>-</code> in the ModTime column, means the modification read on objects is not the modification time of the file when uploaded. It is most likely the time the file was uploaded, or possibly something else (like the time the picture was taken in Google Photos).</p>
<p>Storage systems with a <code>R</code> (for read-only) in the ModTime column, means the it keeps modification times on objects, and updates them when uploading objects, but it does not support changing only the modification time (<code>SetModTime</code> operation) without re-uploading, possibly not even without deleting existing first. Some operations in rclone, such as <code>copy</code> and <code>sync</code> commands, will automatically check for <code>SetModTime</code> support and re-upload if necessary to keep the modification times in sync. Other commands will not work without <code>SetModTime</code> support, e.g. <code>touch</code> command on an existing file will fail, and changes to modification time only on a files in a <code>mount</code> will be silently ignored.</p>
<p>Storage systems with <code>R/W</code> (for read/write) in the ModTime column, means they do also support modtime-only operations.</p>
<p>Storage systems with <code>D</code> in the ModTime column means that the following symbols apply to directories as well as files.</p>
<h3 id="case-insensitive">Case Insensitive</h3>
<p>If a cloud storage systems is case sensitive then it is possible to have two files which differ only in case, e.g. <code>file.txt</code> and <code>FILE.txt</code>. If a cloud storage system is case insensitive then that isn't possible.</p>
<p>This can cause problems when syncing between a case insensitive system and a case sensitive system. The symptom of this is that no matter how many times you run the sync it never completes fully.</p>
<p>The local filesystem and SFTP may or may not be case sensitive depending on OS.</p>
<ul>
<li>Windows - usually case insensitive, though case is preserved</li>
<li>OSX - usually case insensitive, though it is possible to format case sensitive</li>
<li>Linux - usually case sensitive, but there are case insensitive file systems (e.g. FAT formatted USB keys)</li>
</ul>
<p>Most of the time this doesn't cause any problems as people tend to avoid files whose name differs only by case even on case sensitive systems.</p>
<h3 id="duplicate-files">Duplicate files</h3>
<p>If a cloud storage system allows duplicate files then it can have two objects with the same name.</p>
<p>This confuses rclone greatly when syncing - use the <code>rclone dedupe</code> command to rename or remove duplicates.</p>
<h3 id="restricted-filenames">Restricted filenames</h3>
<p>Some cloud storage systems might have restrictions on the characters that are usable in file or directory names. When <code>rclone</code> detects such a name during a file upload, it will transparently replace the restricted characters with similar looking Unicode characters. To handle the different sets of restricted characters for different backends, rclone uses something it calls <a href="#encoding">encoding</a>.</p>
<p>This process is designed to avoid ambiguous file names as much as possible and allow to move files between many cloud storage systems transparently.</p>
<p>The name shown by <code>rclone</code> to the user or during log output will only contain a minimal set of <a href="#restricted-characters">replaced characters</a> to ensure correct formatting and not necessarily the actual name used on the cloud storage.</p>
<p>This transformation is reversed when downloading a file or parsing <code>rclone</code> arguments. For example, when uploading a file named <code>my file?.txt</code> to Onedrive, it will be displayed as <code>my file?.txt</code> on the console, but stored as <code>my file？.txt</code> to Onedrive (the <code>?</code> gets replaced by the similar looking <code>？</code> character, the so-called "fullwidth question mark"). The reverse transformation allows to read a file <code>unusual/name.txt</code> from Google Drive, by passing the name <code>unusual／name.txt</code> on the command line (the <code>/</code> needs to be replaced by the similar looking <code>／</code> character).</p>
<h4 id="restricted-filenames-caveats">Caveats</h4>
<p>The filename encoding system works well in most cases, at least where file names are written in English or similar languages. You might not even notice it: It just works. In some cases it may lead to issues, though. E.g. when file names are written in Chinese, or Japanese, where it is always the Unicode fullwidth variants of the punctuation marks that are used.</p>
<p>On Windows, the characters <code>:</code>, <code>*</code> and <code>?</code> are examples of restricted characters. If these are used in filenames on a remote that supports it, Rclone will transparently convert them to their fullwidth Unicode variants <code>＊</code>, <code>？</code> and <code>：</code> when downloading to Windows, and back again when uploading. This way files with names that are not allowed on Windows can still be stored.</p>
<p>However, if you have files on your Windows system originally with these same Unicode characters in their names, they will be included in the same conversion process. E.g. if you create a file in your Windows filesystem with name <code>Test：1.jpg</code>, where <code>：</code> is the Unicode fullwidth colon symbol, and use rclone to upload it to Google Drive, which supports regular <code>:</code> (halfwidth question mark), rclone will replace the fullwidth <code>:</code> with the halfwidth <code>:</code> and store the file as <code>Test:1.jpg</code> in Google Drive. Since both Windows and Google Drive allows the name <code>Test：1.jpg</code>, it would probably be better if rclone just kept the name as is in this case.</p>
<p>With the opposite situation; if you have a file named <code>Test:1.jpg</code>, in your Google Drive, e.g. uploaded from a Linux system where <code>:</code> is valid in file names. Then later use rclone to copy this file to your Windows computer you will notice that on your local disk it gets renamed to <code>Test：1.jpg</code>. The original filename is not legal on Windows, due to the <code>:</code>, and rclone therefore renames it to make the copy possible. That is all good. However, this can also lead to an issue: If you already had a <em>different</em> file named <code>Test：1.jpg</code> on Windows, and then use rclone to copy either way. Rclone will then treat the file originally named <code>Test:1.jpg</code> on Google Drive and the file originally named <code>Test：1.jpg</code> on Windows as the same file, and replace the contents from one with the other.</p>
<p>Its virtually impossible to handle all cases like these correctly in all situations, but by customizing the <a href="#encoding">encoding option</a>, changing the set of characters that rclone should convert, you should be able to create a configuration that works well for your specific situation. See also the <a href="https://rclone.org/overview/#encoding-example-windows">example</a> below.</p>
<p>(Windows was used as an example of a file system with many restricted characters, and Google drive a storage system with few.)</p>
<h4 id="restricted-characters">Default restricted characters</h4>
<p>The table below shows the characters that are replaced by default.</p>
<p>When a replacement character is found in a filename, this character will be escaped with the <code>‛</code> character to avoid ambiguous file names. (e.g. a file named <code>␀.txt</code> would shown as <code>‛␀.txt</code>)</p>
<p>Each cloud storage backend can use a different set of characters, which will be specified in the documentation for each backend.</p>
<table>
<thead>
<tr class="header">
<th>Character</th>
<th style="text-align: center;">Value</th>
<th style="text-align: center;">Replacement</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td>NUL</td>
<td style="text-align: center;">0x00</td>
<td style="text-align: center;">␀</td>
</tr>
<tr class="even">
<td>SOH</td>
<td style="text-align: center;">0x01</td>
<td style="text-align: center;">␁</td>
</tr>
<tr class="odd">
<td>STX</td>
<td style="text-align: center;">0x02</td>
<td style="text-align: center;">␂</td>
</tr>
<tr class="even">
<td>ETX</td>
<td style="text-align: center;">0x03</td>
<td style="text-align: center;">␃</td>
</tr>
<tr class="odd">
<td>EOT</td>
<td style="text-align: center;">0x04</td>
<td style="text-align: center;">␄</td>
</tr>
<tr class="even">
<td>ENQ</td>
<td style="text-align: center;">0x05</td>
<td style="text-align: center;">␅</td>
</tr>
<tr class="odd">
<td>ACK</td>
<td style="text-align: center;">0x06</td>
<td style="text-align: center;">␆</td>
</tr>
<tr class="even">
<td>BEL</td>
<td style="text-align: center;">0x07</td>
<td style="text-align: center;">␇</td>
</tr>
<tr class="odd">
<td>BS</td>
<td style="text-align: center;">0x08</td>
<td style="text-align: center;">␈</td>
</tr>
<tr class="even">
<td>HT</td>
<td style="text-align: center;">0x09</td>
<td style="text-align: center;">␉</td>
</tr>
<tr class="odd">
<td>LF</td>
<td style="text-align: center;">0x0A</td>
<td style="text-align: center;">␊</td>
</tr>
<tr class="even">
<td>VT</td>
<td style="text-align: center;">0x0B</td>
<td style="text-align: center;">␋</td>
</tr>
<tr class="odd">
<td>FF</td>
<td style="text-align: center;">0x0C</td>
<td style="text-align: center;">␌</td>
</tr>
<tr class="even">
<td>CR</td>
<td style="text-align: center;">0x0D</td>
<td style="text-align: center;">␍</td>
</tr>
<tr class="odd">
<td>SO</td>
<td style="text-align: center;">0x0E</td>
<td style="text-align: center;">␎</td>
</tr>
<tr class="even">
<td>SI</td>
<td style="text-align: center;">0x0F</td>
<td style="text-align: center;">␏</td>
</tr>
<tr class="odd">
<td>DLE</td>
<td style="text-align: center;">0x10</td>
<td style="text-align: center;">␐</td>
</tr>
<tr class="even">
<td>DC1</td>
<td style="text-align: center;">0x11</td>
<td style="text-align: center;">␑</td>
</tr>
<tr class="odd">
<td>DC2</td>
<td style="text-align: center;">0x12</td>
<td style="text-align: center;">␒</td>
</tr>
<tr class="even">
<td>DC3</td>
<td style="text-align: center;">0x13</td>
<td style="text-align: center;">␓</td>
</tr>
<tr class="odd">
<td>DC4</td>
<td style="text-align: center;">0x14</td>
<td style="text-align: center;">␔</td>
</tr>
<tr class="even">
<td>NAK</td>
<td style="text-align: center;">0x15</td>
<td style="text-align: center;">␕</td>
</tr>
<tr class="odd">
<td>SYN</td>
<td style="text-align: center;">0x16</td>
<td style="text-align: center;">␖</td>
</tr>
<tr class="even">
<td>ETB</td>
<td style="text-align: center;">0x17</td>
<td style="text-align: center;">␗</td>
</tr>
<tr class="odd">
<td>CAN</td>
<td style="text-align: center;">0x18</td>
<td style="text-align: center;">␘</td>
</tr>
<tr class="even">
<td>EM</td>
<td style="text-align: center;">0x19</td>
<td style="text-align: center;">␙</td>
</tr>
<tr class="odd">
<td>SUB</td>
<td style="text-align: center;">0x1A</td>
<td style="text-align: center;">␚</td>
</tr>
<tr class="even">
<td>ESC</td>
<td style="text-align: center;">0x1B</td>
<td style="text-align: center;">␛</td>
</tr>
<tr class="odd">
<td>FS</td>
<td style="text-align: center;">0x1C</td>
<td style="text-align: center;">␜</td>
</tr>
<tr class="even">
<td>GS</td>
<td style="text-align: center;">0x1D</td>
<td style="text-align: center;">␝</td>
</tr>
<tr class="odd">
<td>RS</td>
<td style="text-align: center;">0x1E</td>
<td style="text-align: center;">␞</td>
</tr>
<tr class="even">
<td>US</td>
<td style="text-align: center;">0x1F</td>
<td style="text-align: center;">␟</td>
</tr>
<tr class="odd">
<td>/</td>
<td style="text-align: center;">0x2F</td>
<td style="text-align: center;">／</td>
</tr>
<tr class="even">
<td>DEL</td>
<td style="text-align: center;">0x7F</td>
<td style="text-align: center;">␡</td>
</tr>
</tbody>
</table>
<p>The default encoding will also encode these file names as they are problematic with many cloud storage systems.</p>
<table>
<thead>
<tr class="header">
<th>File name</th>
<th style="text-align: center;">Replacement</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td>.</td>
<td style="text-align: center;">．</td>
</tr>
<tr class="even">
<td>..</td>
<td style="text-align: center;">．．</td>
</tr>
</tbody>
</table>
<h4 id="invalid-utf8">Invalid UTF-8 bytes</h4>
<p>Some backends only support a sequence of well formed UTF-8 bytes as file or directory names.</p>
<p>In this case all invalid UTF-8 bytes will be replaced with a quoted representation of the byte value to allow uploading a file to such a backend. For example, the invalid byte <code>0xFE</code> will be encoded as <code>‛FE</code>.</p>
<p>A common source of invalid UTF-8 bytes are local filesystems, that store names in a different encoding than UTF-8 or UTF-16, like latin1. See the <a href="https://rclone.org/local/#filenames">local filenames</a> section for details.</p>
<h4 id="encoding">Encoding option</h4>
<p>Most backends have an encoding option, specified as a flag <code>--backend-encoding</code> where <code>backend</code> is the name of the backend, or as a config parameter <code>encoding</code> (you'll need to select the Advanced config in <code>rclone config</code> to see it).</p>
<p>This will have default value which encodes and decodes characters in such a way as to preserve the maximum number of characters (see above).</p>
<p>However this can be incorrect in some scenarios, for example if you have a Windows file system with Unicode fullwidth characters <code>＊</code>, <code>？</code> or <code>：</code>, that you want to remain as those characters on the remote rather than being translated to regular (halfwidth) <code>*</code>, <code>?</code> and <code>:</code>.</p>
<p>The <code>--backend-encoding</code> flags allow you to change that. You can disable the encoding completely with <code>--backend-encoding Raw</code> or set <code>encoding = Raw</code> in the config file.</p>
<p>Encoding takes a comma separated list of encodings. You can see the list of all possible values by passing an invalid value to this flag, e.g. <code>--local-encoding "help"</code>. The command <code>rclone help flags encoding</code> will show you the defaults for the backends.</p>
<table>
<colgroup>
<col style="width: 31%" />
<col style="width: 34%" />
<col style="width: 34%" />
</colgroup>
<thead>
<tr class="header">
<th>Encoding</th>
<th>Characters</th>
<th>Encoded as</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td>Asterisk</td>
<td><code>*</code></td>
<td><code>＊</code></td>
</tr>
<tr class="even">
<td>BackQuote</td>
<td><code>`</code></td>
<td><code>｀</code></td>
</tr>
<tr class="odd">
<td>BackSlash</td>
<td><code>\</code></td>
<td><code>＼</code></td>
</tr>
<tr class="even">
<td>Colon</td>
<td><code>:</code></td>
<td><code>：</code></td>
</tr>
<tr class="odd">
<td>CrLf</td>
<td>CR 0x0D, LF 0x0A</td>
<td><code>␍</code>, <code>␊</code></td>
</tr>
<tr class="even">
<td>Ctl</td>
<td>All control characters 0x00-0x1F</td>
<td><code>␀␁␂␃␄␅␆␇␈␉␊␋␌␍␎␏␐␑␒␓␔␕␖␗␘␙␚␛␜␝␞␟</code></td>
</tr>
<tr class="odd">
<td>Del</td>
<td>DEL 0x7F</td>
<td><code>␡</code></td>
</tr>
<tr class="even">
<td>Dollar</td>
<td><code>$</code></td>
<td><code>＄</code></td>
</tr>
<tr class="odd">
<td>Dot</td>
<td><code>.</code> or <code>..</code> as entire string</td>
<td><code>．</code>, <code>．．</code></td>
</tr>
<tr class="even">
<td>DoubleQuote</td>
<td><code>"</code></td>
<td><code>＂</code></td>
</tr>
<tr class="odd">
<td>Exclamation</td>
<td><code>!</code></td>
<td><code>！</code></td>
</tr>
<tr class="even">
<td>Hash</td>
<td><code>#</code></td>
<td><code>＃</code></td>
</tr>
<tr class="odd">
<td>InvalidUtf8</td>
<td>An invalid UTF-8 character (e.g. latin1)</td>
<td><code>�</code></td>
</tr>
<tr class="even">
<td>LeftCrLfHtVt</td>
<td>CR 0x0D, LF 0x0A, HT 0x09, VT 0x0B on the left of a string</td>
<td><code>␍</code>, <code>␊</code>, <code>␉</code>, <code>␋</code></td>
</tr>
<tr class="odd">
<td>LeftPeriod</td>
<td><code>.</code> on the left of a string</td>
<td><code>.</code></td>
</tr>
<tr class="even">
<td>LeftSpace</td>
<td>SPACE on the left of a string</td>
<td><code>␠</code></td>
</tr>
<tr class="odd">
<td>LeftTilde</td>
<td><code>~</code> on the left of a string</td>
<td><code>～</code></td>
</tr>
<tr class="even">
<td>LtGt</td>
<td><code>&lt;</code>, <code>&gt;</code></td>
<td><code>＜</code>, <code>＞</code></td>
</tr>
<tr class="odd">
<td>None ¹</td>
<td>NUL 0x00</td>
<td>␀</td>
</tr>
<tr class="even">
<td>Percent</td>
<td><code>%</code></td>
<td><code>％</code></td>
</tr>
<tr class="odd">
<td>Pipe</td>
<td>|</td>
<td><code>｜</code></td>
</tr>
<tr class="even">
<td>Question</td>
<td><code>?</code></td>
<td><code>？</code></td>
</tr>
<tr class="odd">
<td>RightCrLfHtVt</td>
<td>CR 0x0D, LF 0x0A, HT 0x09, VT 0x0B on the right of a string</td>
<td><code>␍</code>, <code>␊</code>, <code>␉</code>, <code>␋</code></td>
</tr>
<tr class="even">
<td>RightPeriod</td>
<td><code>.</code> on the right of a string</td>
<td><code>.</code></td>
</tr>
<tr class="odd">
<td>RightSpace</td>
<td>SPACE on the right of a string</td>
<td><code>␠</code></td>
</tr>
<tr class="even">
<td>Semicolon</td>
<td><code>;</code></td>
<td><code>；</code></td>
</tr>
<tr class="odd">
<td>SingleQuote</td>
<td><code>'</code></td>
<td><code>＇</code></td>
</tr>
<tr class="even">
<td>Slash</td>
<td><code>/</code></td>
<td><code>／</code></td>
</tr>
<tr class="odd">
<td>SquareBracket</td>
<td><code>[</code>, <code>]</code></td>
<td><code>［</code>, <code>］</code></td>
</tr>
</tbody>
</table>
<p>¹ Encoding from NUL 0x00 to ␀ is always implicit except when using Raw. It was previously incorrectly documented as disabling encoding, and to maintain backward compatibility, its behavior has not been changed.</p>
<h5 id="encoding-example-ftp">Encoding example: FTP</h5>
<p>To take a specific example, the FTP backend's default encoding is</p>
<pre><code>--ftp-encoding &quot;Slash,Del,Ctl,RightSpace,Dot&quot;</code></pre>
<p>However, let's say the FTP server is running on Windows and can't have any of the invalid Windows characters in file names. You are backing up Linux servers to this FTP server which do have those characters in file names. So you would add the Windows set which are</p>
<pre><code>Slash,LtGt,DoubleQuote,Colon,Question,Asterisk,Pipe,BackSlash,Ctl,RightSpace,RightPeriod,InvalidUtf8,Dot</code></pre>
<p>to the existing ones, giving:</p>
<pre><code>Slash,LtGt,DoubleQuote,Colon,Question,Asterisk,Pipe,BackSlash,Ctl,RightSpace,RightPeriod,InvalidUtf8,Dot,Del,RightSpace</code></pre>
<p>This can be specified using the <code>--ftp-encoding</code> flag or using an <code>encoding</code> parameter in the config file.</p>
<h5 id="encoding-example-windows">Encoding example: Windows</h5>
<p>As a nother example, take a Windows system where there is a file with name <code>Test：1.jpg</code>, where <code>：</code> is the Unicode fullwidth colon symbol. When using rclone to copy this to a remote which supports <code>:</code>, the regular (halfwidth) colon (such as Google Drive), you will notice that the file gets renamed to <code>Test:1.jpg</code>.</p>
<p>To avoid this you can change the set of characters rclone should convert for the local filesystem, using command-line argument <code>--local-encoding</code>. Rclone's default behavior on Windows corresponds to</p>
<pre><code>--local-encoding &quot;Slash,LtGt,DoubleQuote,Colon,Question,Asterisk,Pipe,BackSlash,Ctl,RightSpace,RightPeriod,InvalidUtf8,Dot&quot;</code></pre>
<p>If you want to use fullwidth characters <code>：</code>, <code>＊</code> and <code>？</code> in your filenames without rclone changing them when uploading to a remote, then set the same as the default value but without <code>Colon,Question,Asterisk</code>:</p>
<pre><code>--local-encoding &quot;Slash,LtGt,DoubleQuote,Pipe,BackSlash,Ctl,RightSpace,RightPeriod,InvalidUtf8,Dot&quot;</code></pre>
<p>Alternatively, you can disable the conversion of any characters with <code>--local-encoding Raw</code>.</p>
<p>Instead of using command-line argument <code>--local-encoding</code>, you may also set it as <a href="https://rclone.org/docs/#environment-variables">environment variable</a> <code>RCLONE_LOCAL_ENCODING</code>, or <a href="https://rclone.org/docs/#configure">configure</a> a remote of type <code>local</code> in your config, and set the <code>encoding</code> option there.</p>
<p>The risk by doing this is that if you have a filename with the regular (halfwidth) <code>:</code>, <code>*</code> and <code>?</code> in your cloud storage, and you try to download it to your Windows filesystem, this will fail. These characters are not valid in filenames on Windows, and you have told rclone not to work around this by converting them to valid fullwidth variants.</p>
<h3 id="mime-type">MIME Type</h3>
<p>MIME types (also known as media types) classify types of documents using a simple text classification, e.g. <code>text/html</code> or <code>application/pdf</code>.</p>
<p>Some cloud storage systems support reading (<code>R</code>) the MIME type of objects and some support writing (<code>W</code>) the MIME type of objects.</p>
<p>The MIME type can be important if you are serving files directly to HTTP from the storage system.</p>
<p>If you are copying from a remote which supports reading (<code>R</code>) to a remote which supports writing (<code>W</code>) then rclone will preserve the MIME types. Otherwise they will be guessed from the extension, or the remote itself may assign the MIME type.</p>
<h3 id="metadata-1">Metadata</h3>
<p>Backends may or may support reading or writing metadata. They may support reading and writing system metadata (metadata intrinsic to that backend) and/or user metadata (general purpose metadata).</p>
<p>The levels of metadata support are</p>
<table>
<colgroup>
<col style="width: 27%" />
<col style="width: 72%" />
</colgroup>
<thead>
<tr class="header">
<th>Key</th>
<th>Explanation</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td><code>R</code></td>
<td>Read only System Metadata on files only</td>
</tr>
<tr class="even">
<td><code>RW</code></td>
<td>Read and write System Metadata on files only</td>
</tr>
<tr class="odd">
<td><code>RWU</code></td>
<td>Read and write System Metadata and read and write User Metadata on files only</td>
</tr>
<tr class="even">
<td><code>DR</code></td>
<td>Read only System Metadata on files and directories</td>
</tr>
<tr class="odd">
<td><code>DRW</code></td>
<td>Read and write System Metadata on files and directories</td>
</tr>
<tr class="even">
<td><code>DRWU</code></td>
<td>Read and write System Metadata and read and write User Metadata on files and directories</td>
</tr>
</tbody>
</table>
<p>See <a href="https://rclone.org/docs/#metadata">the metadata docs</a> for more info.</p>
<h2 id="optional-features">Optional Features</h2>
<p>All rclone remotes support a base command set. Other features depend upon backend-specific capabilities.</p>
<table style="width:100%;">
<colgroup>
<col style="width: 20%" />
<col style="width: 5%" />
<col style="width: 4%" />
<col style="width: 4%" />
<col style="width: 6%" />
<col style="width: 6%" />
<col style="width: 5%" />
<col style="width: 10%" />
<col style="width: 13%" />
<col style="width: 10%" />
<col style="width: 5%" />
<col style="width: 7%" />
</colgroup>
<thead>
<tr class="header">
<th>Name</th>
<th style="text-align: center;">Purge</th>
<th style="text-align: center;">Copy</th>
<th style="text-align: center;">Move</th>
<th style="text-align: center;">DirMove</th>
<th style="text-align: center;">CleanUp</th>
<th style="text-align: center;">ListR</th>
<th style="text-align: center;">StreamUpload</th>
<th style="text-align: left;">MultithreadUpload</th>
<th style="text-align: center;">LinkSharing</th>
<th style="text-align: center;">About</th>
<th style="text-align: center;">EmptyDir</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td>1Fichier</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: left;">No</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">Yes</td>
</tr>
<tr class="even">
<td>Akamai Netstorage</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: left;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">Yes</td>
</tr>
<tr class="odd">
<td>Amazon S3 (or S3 compatible)</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: left;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
</tr>
<tr class="even">
<td>Backblaze B2</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: left;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
</tr>
<tr class="odd">
<td>Box</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: left;">No</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
</tr>
<tr class="even">
<td>Citrix ShareFile</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: left;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">Yes</td>
</tr>
<tr class="odd">
<td>Dropbox</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: left;">No</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
</tr>
<tr class="even">
<td>Enterprise File Fabric</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: left;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">Yes</td>
</tr>
<tr class="odd">
<td>Files.com</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: left;">No</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">Yes</td>
</tr>
<tr class="even">
<td>FTP</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: left;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">Yes</td>
</tr>
<tr class="odd">
<td>Gofile</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: left;">No</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
</tr>
<tr class="even">
<td>Google Cloud Storage</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: left;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
</tr>
<tr class="odd">
<td>Google Drive</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: left;">No</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
</tr>
<tr class="even">
<td>Google Photos</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: left;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
</tr>
<tr class="odd">
<td>HDFS</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: left;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
</tr>
<tr class="even">
<td>HiDrive</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: left;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">Yes</td>
</tr>
<tr class="odd">
<td>HTTP</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: left;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">Yes</td>
</tr>
<tr class="even">
<td>ImageKit</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: left;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">Yes</td>
</tr>
<tr class="odd">
<td>Internet Archive</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">No</td>
<td style="text-align: left;">No</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">No</td>
</tr>
<tr class="even">
<td>Jottacloud</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">No</td>
<td style="text-align: left;">No</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
</tr>
<tr class="odd">
<td>Koofr</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: left;">No</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
</tr>
<tr class="even">
<td>Mail.ru Cloud</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: left;">No</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
</tr>
<tr class="odd">
<td>Mega</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: left;">No</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
</tr>
<tr class="even">
<td>Memory</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: left;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
</tr>
<tr class="odd">
<td>Microsoft Azure Blob Storage</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: left;">Yes</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
</tr>
<tr class="even">
<td>Microsoft Azure Files Storage</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: left;">Yes</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
</tr>
<tr class="odd">
<td>Microsoft OneDrive</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes ⁵</td>
<td style="text-align: center;">No</td>
<td style="text-align: left;">No</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
</tr>
<tr class="even">
<td>OpenDrive</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: left;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">Yes</td>
</tr>
<tr class="odd">
<td>OpenStack Swift</td>
<td style="text-align: center;">Yes ¹</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: left;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">No</td>
</tr>
<tr class="even">
<td>Oracle Object Storage</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: left;">Yes</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
</tr>
<tr class="odd">
<td>pCloud</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: left;">No</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
</tr>
<tr class="even">
<td>PikPak</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: left;">No</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
</tr>
<tr class="odd">
<td>Pixeldrain</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: left;">No</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
</tr>
<tr class="even">
<td>premiumize.me</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: left;">No</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
</tr>
<tr class="odd">
<td>put.io</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: left;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
</tr>
<tr class="even">
<td>Proton Drive</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: left;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
</tr>
<tr class="odd">
<td>QingStor</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">No</td>
<td style="text-align: left;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
</tr>
<tr class="even">
<td>Quatrix by Maytech</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: left;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
</tr>
<tr class="odd">
<td>Seafile</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: left;">No</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
</tr>
<tr class="even">
<td>SFTP</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">Yes ⁴</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: left;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
</tr>
<tr class="odd">
<td>Sia</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: left;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">Yes</td>
</tr>
<tr class="even">
<td>SMB</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: left;">Yes</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">Yes</td>
</tr>
<tr class="odd">
<td>SugarSync</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: left;">No</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">Yes</td>
</tr>
<tr class="even">
<td>Storj</td>
<td style="text-align: center;">Yes ²</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: left;">No</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
</tr>
<tr class="odd">
<td>Uloz.to</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: left;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">Yes</td>
</tr>
<tr class="even">
<td>Uptobox</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: left;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
</tr>
<tr class="odd">
<td>WebDAV</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">Yes ³</td>
<td style="text-align: left;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
</tr>
<tr class="even">
<td>Yandex Disk</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: left;">No</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
</tr>
<tr class="odd">
<td>Zoho WorkDrive</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: left;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
</tr>
<tr class="even">
<td>The local filesystem</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: left;">Yes</td>
<td style="text-align: center;">No</td>
<td style="text-align: center;">Yes</td>
<td style="text-align: center;">Yes</td>
</tr>
</tbody>
</table>
<p>¹ Note Swift implements this in order to delete directory markers but it doesn't actually have a quicker way of deleting files other than deleting them individually.</p>
<p>² Storj implements this efficiently only for entire buckets. If purging a directory inside a bucket, files are deleted individually.</p>
<p>³ StreamUpload is not supported with Nextcloud</p>
<p>⁴ Use the <code>--sftp-copy-is-hardlink</code> flag to enable.</p>
<p>⁵ Use the <code>--onedrive-delta</code> flag to enable.</p>
<h3 id="purge">Purge</h3>
<p>This deletes a directory quicker than just deleting all the files in the directory.</p>
<h3 id="copy">Copy</h3>
<p>Used when copying an object to and from the same remote. This known as a server-side copy so you can copy a file without downloading it and uploading it again. It is used if you use <code>rclone copy</code> or <code>rclone move</code> if the remote doesn't support <code>Move</code> directly.</p>
<p>If the server doesn't support <code>Copy</code> directly then for copy operations the file is downloaded then re-uploaded.</p>
<h3 id="move">Move</h3>
<p>Used when moving/renaming an object on the same remote. This is known as a server-side move of a file. This is used in <code>rclone move</code> if the server doesn't support <code>DirMove</code>.</p>
<p>If the server isn't capable of <code>Move</code> then rclone simulates it with <code>Copy</code> then delete. If the server doesn't support <code>Copy</code> then rclone will download the file and re-upload it.</p>
<h3 id="dirmove">DirMove</h3>
<p>This is used to implement <code>rclone move</code> to move a directory if possible. If it isn't then it will use <code>Move</code> on each file (which falls back to <code>Copy</code> then download and upload - see <code>Move</code> section).</p>
<h3 id="cleanup">CleanUp</h3>
<p>This is used for emptying the trash for a remote by <code>rclone cleanup</code>.</p>
<p>If the server can't do <code>CleanUp</code> then <code>rclone cleanup</code> will return an error.</p>
<p>‡‡ Note that while Box implements this it has to delete every file individually so it will be slower than emptying the trash via the WebUI</p>
<h3 id="listr">ListR</h3>
<p>The remote supports a recursive list to list all the contents beneath a directory quickly. This enables the <code>--fast-list</code> flag to work. See the <a href="https://rclone.org/docs/#fast-list">rclone docs</a> for more details.</p>
<h3 id="streamupload">StreamUpload</h3>
<p>Some remotes allow files to be uploaded without knowing the file size in advance. This allows certain operations to work without spooling the file to local disk first, e.g. <code>rclone rcat</code>.</p>
<h3 id="multithreadupload">MultithreadUpload</h3>
<p>Some remotes allow transfers to the remote to be sent as chunks in parallel. If this is supported then rclone will use multi-thread copying to transfer files much faster.</p>
<h3 id="linksharing">LinkSharing</h3>
<p>Sets the necessary permissions on a file or folder and prints a link that allows others to access them, even if they don't have an account on the particular cloud provider.</p>
<h3 id="about-1">About</h3>
<p>Rclone <code>about</code> prints quota information for a remote. Typical output includes bytes used, free, quota and in trash.</p>
<p>If a remote lacks about capability <code>rclone about remote:</code>returns an error.</p>
<p>Backends without about capability cannot determine free space for an rclone mount, or use policy <code>mfs</code> (most free space) as a member of an rclone union remote.</p>
<p>See <a href="https://rclone.org/commands/rclone_about/">rclone about command</a></p>
<h3 id="emptydir">EmptyDir</h3>
<p>The remote supports empty directories. See <a href="https://rclone.org/bugs/#limitations">Limitations</a> for details. Most Object/Bucket-based remotes do not support this.</p>
<h1 id="global-flags">Global Flags</h1>
<p>This describes the global flags available to every rclone command split into groups.</p>
<h2 id="copy-1">Copy</h2>
<p>Flags for anything which can copy a file.</p>
<pre><code>      --check-first                                 Do all the checks before starting transfers
  -c, --checksum                                    Check for changes with size &amp; checksum (if available, or fallback to size only)
      --compare-dest stringArray                    Include additional server-side paths during comparison
      --copy-dest stringArray                       Implies --compare-dest but also copies files from paths into destination
      --cutoff-mode HARD|SOFT|CAUTIOUS              Mode to stop transfers when reaching the max transfer limit HARD|SOFT|CAUTIOUS (default HARD)
      --ignore-case-sync                            Ignore case when synchronizing
      --ignore-checksum                             Skip post copy check of checksums
      --ignore-existing                             Skip all files that exist on destination
      --ignore-size                                 Ignore size when skipping use modtime or checksum
  -I, --ignore-times                                Don&#39;t skip items that match size and time - transfer all unconditionally
      --immutable                                   Do not modify files, fail if existing files have been modified
      --inplace                                     Download directly to destination file instead of atomic download to temp/rename
      --max-backlog int                             Maximum number of objects in sync or check backlog (default 10000)
      --max-duration Duration                       Maximum duration rclone will transfer data for (default 0s)
      --max-transfer SizeSuffix                     Maximum size of data to transfer (default off)
  -M, --metadata                                    If set, preserve metadata when copying objects
      --modify-window Duration                      Max time diff to be considered the same (default 1ns)
      --multi-thread-chunk-size SizeSuffix          Chunk size for multi-thread downloads / uploads, if not set by filesystem (default 64Mi)
      --multi-thread-cutoff SizeSuffix              Use multi-thread downloads for files above this size (default 256Mi)
      --multi-thread-streams int                    Number of streams to use for multi-thread downloads (default 4)
      --multi-thread-write-buffer-size SizeSuffix   In memory buffer size for writing when in multi-thread mode (default 128Ki)
      --no-check-dest                               Don&#39;t check the destination, copy regardless
      --no-traverse                                 Don&#39;t traverse destination file system on copy
      --no-update-dir-modtime                       Don&#39;t update directory modification times
      --no-update-modtime                           Don&#39;t update destination modtime if files identical
      --order-by string                             Instructions on how to order the transfers, e.g. &#39;size,descending&#39;
      --partial-suffix string                       Add partial-suffix to temporary file name when --inplace is not used (default &quot;.partial&quot;)
      --refresh-times                               Refresh the modtime of remote files
      --server-side-across-configs                  Allow server-side operations (e.g. copy) to work across different configs
      --size-only                                   Skip based on size only, not modtime or checksum
      --streaming-upload-cutoff SizeSuffix          Cutoff for switching to chunked upload if file size is unknown, upload starts after reaching cutoff or when file ends (default 100Ki)
  -u, --update                                      Skip files that are newer on the destination</code></pre>
<h2 id="sync">Sync</h2>
<p>Flags used for sync commands.</p>
<pre><code>      --backup-dir string               Make backups into hierarchy based in DIR
      --delete-after                    When synchronizing, delete files on destination after transferring (default)
      --delete-before                   When synchronizing, delete files on destination before transferring
      --delete-during                   When synchronizing, delete files during transfer
      --fix-case                        Force rename of case insensitive dest to match source
      --ignore-errors                   Delete even if there are I/O errors
      --max-delete int                  When synchronizing, limit the number of deletes (default -1)
      --max-delete-size SizeSuffix      When synchronizing, limit the total size of deletes (default off)
      --suffix string                   Suffix to add to changed files
      --suffix-keep-extension           Preserve the extension when using --suffix
      --track-renames                   When synchronizing, track file renames and do a server-side move if possible
      --track-renames-strategy string   Strategies to use when synchronizing using track-renames hash|modtime|leaf (default &quot;hash&quot;)</code></pre>
<h2 id="important">Important</h2>
<p>Important flags useful for most commands.</p>
<pre><code>  -n, --dry-run         Do a trial run with no permanent changes
  -i, --interactive     Enable interactive mode
  -v, --verbose count   Print lots more stuff (repeat for more)</code></pre>
<h2 id="check">Check</h2>
<p>Flags used for check commands.</p>
<pre><code>      --max-backlog int   Maximum number of objects in sync or check backlog (default 10000)</code></pre>
<h2 id="networking">Networking</h2>
<p>Flags for general networking and HTTP stuff.</p>
<pre><code>      --bind string                        Local address to bind to for outgoing connections, IPv4, IPv6 or name
      --bwlimit BwTimetable                Bandwidth limit in KiB/s, or use suffix B|K|M|G|T|P or a full timetable
      --bwlimit-file BwTimetable           Bandwidth limit per file in KiB/s, or use suffix B|K|M|G|T|P or a full timetable
      --ca-cert stringArray                CA certificate used to verify servers
      --client-cert string                 Client SSL certificate (PEM) for mutual TLS auth
      --client-key string                  Client SSL private key (PEM) for mutual TLS auth
      --contimeout Duration                Connect timeout (default 1m0s)
      --disable-http-keep-alives           Disable HTTP keep-alives and use each connection once
      --disable-http2                      Disable HTTP/2 in the global transport
      --dscp string                        Set DSCP value to connections, value or name, e.g. CS1, LE, DF, AF21
      --expect-continue-timeout Duration   Timeout when using expect / 100-continue in HTTP (default 1s)
      --header stringArray                 Set HTTP header for all transactions
      --header-download stringArray        Set HTTP header for download transactions
      --header-upload stringArray          Set HTTP header for upload transactions
      --no-check-certificate               Do not verify the server SSL certificate (insecure)
      --no-gzip-encoding                   Don&#39;t set Accept-Encoding: gzip
      --timeout Duration                   IO idle timeout (default 5m0s)
      --tpslimit float                     Limit HTTP transactions per second to this
      --tpslimit-burst int                 Max burst of transactions for --tpslimit (default 1)
      --use-cookies                        Enable session cookiejar
      --user-agent string                  Set the user-agent to a specified string (default &quot;rclone/v1.68.2&quot;)</code></pre>
<h2 id="performance">Performance</h2>
<p>Flags helpful for increasing performance.</p>
<pre><code>      --buffer-size SizeSuffix   In memory buffer size when reading files for each --transfer (default 16Mi)
      --checkers int             Number of checkers to run in parallel (default 8)
      --transfers int            Number of file transfers to run in parallel (default 4)</code></pre>
<h2 id="config">Config</h2>
<p>Flags for general configuration of rclone.</p>
<pre><code>      --ask-password                        Allow prompt for password for encrypted configuration (default true)
      --auto-confirm                        If enabled, do not request console confirmation
      --cache-dir string                    Directory rclone will use for caching (default &quot;$HOME/.cache/rclone&quot;)
      --color AUTO|NEVER|ALWAYS             When to show colors (and other ANSI codes) AUTO|NEVER|ALWAYS (default AUTO)
      --config string                       Config file (default &quot;$HOME/.config/rclone/rclone.conf&quot;)
      --default-time Time                   Time to show if modtime is unknown for files and directories (default 2000-01-01T00:00:00Z)
      --disable string                      Disable a comma separated list of features (use --disable help to see a list)
  -n, --dry-run                             Do a trial run with no permanent changes
      --error-on-no-transfer                Sets exit code 9 if no files are transferred, useful in scripts
      --fs-cache-expire-duration Duration   Cache remotes for this long (0 to disable caching) (default 5m0s)
      --fs-cache-expire-interval Duration   Interval to check for expired remotes (default 1m0s)
      --human-readable                      Print numbers in a human-readable format, sizes with suffix Ki|Mi|Gi|Ti|Pi
  -i, --interactive                         Enable interactive mode
      --kv-lock-time Duration               Maximum time to keep key-value database locked by process (default 1s)
      --low-level-retries int               Number of low level retries to do (default 10)
      --no-console                          Hide console window (supported on Windows only)
      --no-unicode-normalization            Don&#39;t normalize unicode characters in filenames
      --password-command SpaceSepList       Command for supplying password for encrypted configuration
      --retries int                         Retry operations this many times if they fail (default 3)
      --retries-sleep Duration              Interval between retrying operations if they fail, e.g. 500ms, 60s, 5m (0 to disable) (default 0s)
      --temp-dir string                     Directory rclone will use for temporary files (default &quot;/tmp&quot;)
      --use-mmap                            Use mmap allocator (see docs)
      --use-server-modtime                  Use server modified time instead of object metadata</code></pre>
<h2 id="debugging">Debugging</h2>
<p>Flags for developers.</p>
<pre><code>      --cpuprofile string   Write cpu profile to file
      --dump DumpFlags      List of items to dump from: headers, bodies, requests, responses, auth, filters, goroutines, openfiles, mapper
      --dump-bodies         Dump HTTP headers and bodies - may contain sensitive info
      --dump-headers        Dump HTTP headers - may contain sensitive info
      --memprofile string   Write memory profile to file</code></pre>
<h2 id="filter">Filter</h2>
<p>Flags for filtering directory listings.</p>
<pre><code>      --delete-excluded                     Delete files on dest excluded from sync
      --exclude stringArray                 Exclude files matching pattern
      --exclude-from stringArray            Read file exclude patterns from file (use - to read from stdin)
      --exclude-if-present stringArray      Exclude directories if filename is present
      --files-from stringArray              Read list of source-file names from file (use - to read from stdin)
      --files-from-raw stringArray          Read list of source-file names from file without any processing of lines (use - to read from stdin)
  -f, --filter stringArray                  Add a file filtering rule
      --filter-from stringArray             Read file filtering patterns from a file (use - to read from stdin)
      --ignore-case                         Ignore case in filters (case insensitive)
      --include stringArray                 Include files matching pattern
      --include-from stringArray            Read file include patterns from file (use - to read from stdin)
      --max-age Duration                    Only transfer files younger than this in s or suffix ms|s|m|h|d|w|M|y (default off)
      --max-depth int                       If set limits the recursion depth to this (default -1)
      --max-size SizeSuffix                 Only transfer files smaller than this in KiB or suffix B|K|M|G|T|P (default off)
      --metadata-exclude stringArray        Exclude metadatas matching pattern
      --metadata-exclude-from stringArray   Read metadata exclude patterns from file (use - to read from stdin)
      --metadata-filter stringArray         Add a metadata filtering rule
      --metadata-filter-from stringArray    Read metadata filtering patterns from a file (use - to read from stdin)
      --metadata-include stringArray        Include metadatas matching pattern
      --metadata-include-from stringArray   Read metadata include patterns from file (use - to read from stdin)
      --min-age Duration                    Only transfer files older than this in s or suffix ms|s|m|h|d|w|M|y (default off)
      --min-size SizeSuffix                 Only transfer files bigger than this in KiB or suffix B|K|M|G|T|P (default off)</code></pre>
<h2 id="listing">Listing</h2>
<p>Flags for listing directories.</p>
<pre><code>      --default-time Time   Time to show if modtime is unknown for files and directories (default 2000-01-01T00:00:00Z)
      --fast-list           Use recursive list if available; uses more memory but fewer transactions</code></pre>
<h2 id="logging-1">Logging</h2>
<p>Flags for logging and statistics.</p>
<pre><code>      --log-file string                     Log everything to this file
      --log-format string                   Comma separated list of log format options (default &quot;date,time&quot;)
      --log-level LogLevel                  Log level DEBUG|INFO|NOTICE|ERROR (default NOTICE)
      --log-systemd                         Activate systemd integration for the logger
      --max-stats-groups int                Maximum number of stats groups to keep in memory, on max oldest is discarded (default 1000)
  -P, --progress                            Show progress during transfer
      --progress-terminal-title             Show progress on the terminal title (requires -P/--progress)
  -q, --quiet                               Print as little stuff as possible
      --stats Duration                      Interval between printing stats, e.g. 500ms, 60s, 5m (0 to disable) (default 1m0s)
      --stats-file-name-length int          Max file name length in stats (0 for no limit) (default 45)
      --stats-log-level LogLevel            Log level to show --stats output DEBUG|INFO|NOTICE|ERROR (default INFO)
      --stats-one-line                      Make the stats fit on one line
      --stats-one-line-date                 Enable --stats-one-line and add current date/time prefix
      --stats-one-line-date-format string   Enable --stats-one-line-date and use custom formatted date: Enclose date string in double quotes (&quot;), see https://golang.org/pkg/time/#Time.Format
      --stats-unit string                   Show data rate in stats as either &#39;bits&#39; or &#39;bytes&#39; per second (default &quot;bytes&quot;)
      --syslog                              Use Syslog for logging
      --syslog-facility string              Facility for syslog, e.g. KERN,USER (default &quot;DAEMON&quot;)
      --use-json-log                        Use json log format
  -v, --verbose count                       Print lots more stuff (repeat for more)</code></pre>
<h2 id="metadata-2">Metadata</h2>
<p>Flags to control metadata.</p>
<pre><code>  -M, --metadata                            If set, preserve metadata when copying objects
      --metadata-exclude stringArray        Exclude metadatas matching pattern
      --metadata-exclude-from stringArray   Read metadata exclude patterns from file (use - to read from stdin)
      --metadata-filter stringArray         Add a metadata filtering rule
      --metadata-filter-from stringArray    Read metadata filtering patterns from a file (use - to read from stdin)
      --metadata-include stringArray        Include metadatas matching pattern
      --metadata-include-from stringArray   Read metadata include patterns from file (use - to read from stdin)
      --metadata-mapper SpaceSepList        Program to run to transforming metadata before upload
      --metadata-set stringArray            Add metadata key=value when uploading</code></pre>
<h2 id="rc-1">RC</h2>
<p>Flags to control the Remote Control API.</p>
<pre><code>      --rc                                 Enable the remote control server
      --rc-addr stringArray                IPaddress:Port or :Port to bind server to (default localhost:5572)
      --rc-allow-origin string             Origin which cross-domain request (CORS) can be executed from
      --rc-baseurl string                  Prefix for URLs - leave blank for root
      --rc-cert string                     TLS PEM key (concatenation of certificate and CA certificate)
      --rc-client-ca string                Client certificate authority to verify clients with
      --rc-enable-metrics                  Enable the Prometheus metrics path at the remote control server
      --rc-files string                    Path to local files to serve on the HTTP server
      --rc-htpasswd string                 A htpasswd file - if not provided no authentication is done
      --rc-job-expire-duration Duration    Expire finished async jobs older than this value (default 1m0s)
      --rc-job-expire-interval Duration    Interval to check for expired async jobs (default 10s)
      --rc-key string                      TLS PEM Private key
      --rc-max-header-bytes int            Maximum size of request header (default 4096)
      --rc-min-tls-version string          Minimum TLS version that is acceptable (default &quot;tls1.0&quot;)
      --rc-no-auth                         Don&#39;t require auth for certain methods
      --rc-pass string                     Password for authentication
      --rc-realm string                    Realm for authentication
      --rc-salt string                     Password hashing salt (default &quot;dlPL2MqE&quot;)
      --rc-serve                           Enable the serving of remote objects
      --rc-serve-no-modtime                Don&#39;t read the modification time (can speed things up)
      --rc-server-read-timeout Duration    Timeout for server reading data (default 1h0m0s)
      --rc-server-write-timeout Duration   Timeout for server writing data (default 1h0m0s)
      --rc-template string                 User-specified template
      --rc-user string                     User name for authentication
      --rc-web-fetch-url string            URL to fetch the releases for webgui (default &quot;https://api.github.com/repos/rclone/rclone-webui-react/releases/latest&quot;)
      --rc-web-gui                         Launch WebGUI on localhost
      --rc-web-gui-force-update            Force update to latest version of web gui
      --rc-web-gui-no-open-browser         Don&#39;t open the browser automatically
      --rc-web-gui-update                  Check and update to latest version of web gui</code></pre>
<h2 id="metrics-1">Metrics</h2>
<p>Flags to control the Metrics HTTP endpoint..</p>
<pre><code>      --metrics-addr stringArray                IPaddress:Port or :Port to bind metrics server to
      --metrics-allow-origin string             Origin which cross-domain request (CORS) can be executed from
      --metrics-baseurl string                  Prefix for URLs - leave blank for root
      --metrics-cert string                     TLS PEM key (concatenation of certificate and CA certificate)
      --metrics-client-ca string                Client certificate authority to verify clients with
      --metrics-htpasswd string                 A htpasswd file - if not provided no authentication is done
      --metrics-key string                      TLS PEM Private key
      --metrics-max-header-bytes int            Maximum size of request header (default 4096)
      --metrics-min-tls-version string          Minimum TLS version that is acceptable (default &quot;tls1.0&quot;)
      --metrics-pass string                     Password for authentication
      --metrics-realm string                    Realm for authentication
      --metrics-salt string                     Password hashing salt (default &quot;dlPL2MqE&quot;)
      --metrics-server-read-timeout Duration    Timeout for server reading data (default 1h0m0s)
      --metrics-server-write-timeout Duration   Timeout for server writing data (default 1h0m0s)
      --metrics-template string                 User-specified template
      --metrics-user string                     User name for authentication
      --rc-enable-metrics                       Enable the Prometheus metrics path at the remote control server</code></pre>
<h2 id="backend">Backend</h2>
<p>Backend-only flags (these can be set in the config file also).</p>
<pre><code>      --alias-description string                            Description of the remote
      --alias-remote string                                 Remote or path to alias
      --azureblob-access-tier string                        Access tier of blob: hot, cool, cold or archive
      --azureblob-account string                            Azure Storage Account Name
      --azureblob-archive-tier-delete                       Delete archive tier blobs before overwriting
      --azureblob-chunk-size SizeSuffix                     Upload chunk size (default 4Mi)
      --azureblob-client-certificate-password string        Password for the certificate file (optional) (obscured)
      --azureblob-client-certificate-path string            Path to a PEM or PKCS12 certificate file including the private key
      --azureblob-client-id string                          The ID of the client in use
      --azureblob-client-secret string                      One of the service principal&#39;s client secrets
      --azureblob-client-send-certificate-chain             Send the certificate chain when using certificate auth
      --azureblob-delete-snapshots string                   Set to specify how to deal with snapshots on blob deletion
      --azureblob-description string                        Description of the remote
      --azureblob-directory-markers                         Upload an empty object with a trailing slash when a new directory is created
      --azureblob-disable-checksum                          Don&#39;t store MD5 checksum with object metadata
      --azureblob-encoding Encoding                         The encoding for the backend (default Slash,BackSlash,Del,Ctl,RightPeriod,InvalidUtf8)
      --azureblob-endpoint string                           Endpoint for the service
      --azureblob-env-auth                                  Read credentials from runtime (environment variables, CLI or MSI)
      --azureblob-key string                                Storage Account Shared Key
      --azureblob-list-chunk int                            Size of blob list (default 5000)
      --azureblob-msi-client-id string                      Object ID of the user-assigned MSI to use, if any
      --azureblob-msi-mi-res-id string                      Azure resource ID of the user-assigned MSI to use, if any
      --azureblob-msi-object-id string                      Object ID of the user-assigned MSI to use, if any
      --azureblob-no-check-container                        If set, don&#39;t attempt to check the container exists or create it
      --azureblob-no-head-object                            If set, do not do HEAD before GET when getting objects
      --azureblob-password string                           The user&#39;s password (obscured)
      --azureblob-public-access string                      Public access level of a container: blob or container
      --azureblob-sas-url string                            SAS URL for container level access only
      --azureblob-service-principal-file string             Path to file containing credentials for use with a service principal
      --azureblob-tenant string                             ID of the service principal&#39;s tenant. Also called its directory ID
      --azureblob-upload-concurrency int                    Concurrency for multipart uploads (default 16)
      --azureblob-upload-cutoff string                      Cutoff for switching to chunked upload (&lt;= 256 MiB) (deprecated)
      --azureblob-use-emulator                              Uses local storage emulator if provided as &#39;true&#39;
      --azureblob-use-msi                                   Use a managed service identity to authenticate (only works in Azure)
      --azureblob-username string                           User name (usually an email address)
      --azurefiles-account string                           Azure Storage Account Name
      --azurefiles-chunk-size SizeSuffix                    Upload chunk size (default 4Mi)
      --azurefiles-client-certificate-password string       Password for the certificate file (optional) (obscured)
      --azurefiles-client-certificate-path string           Path to a PEM or PKCS12 certificate file including the private key
      --azurefiles-client-id string                         The ID of the client in use
      --azurefiles-client-secret string                     One of the service principal&#39;s client secrets
      --azurefiles-client-send-certificate-chain            Send the certificate chain when using certificate auth
      --azurefiles-connection-string string                 Azure Files Connection String
      --azurefiles-description string                       Description of the remote
      --azurefiles-encoding Encoding                        The encoding for the backend (default Slash,LtGt,DoubleQuote,Colon,Question,Asterisk,Pipe,BackSlash,Del,Ctl,RightPeriod,InvalidUtf8,Dot)
      --azurefiles-endpoint string                          Endpoint for the service
      --azurefiles-env-auth                                 Read credentials from runtime (environment variables, CLI or MSI)
      --azurefiles-key string                               Storage Account Shared Key
      --azurefiles-max-stream-size SizeSuffix               Max size for streamed files (default 10Gi)
      --azurefiles-msi-client-id string                     Object ID of the user-assigned MSI to use, if any
      --azurefiles-msi-mi-res-id string                     Azure resource ID of the user-assigned MSI to use, if any
      --azurefiles-msi-object-id string                     Object ID of the user-assigned MSI to use, if any
      --azurefiles-password string                          The user&#39;s password (obscured)
      --azurefiles-sas-url string                           SAS URL
      --azurefiles-service-principal-file string            Path to file containing credentials for use with a service principal
      --azurefiles-share-name string                        Azure Files Share Name
      --azurefiles-tenant string                            ID of the service principal&#39;s tenant. Also called its directory ID
      --azurefiles-upload-concurrency int                   Concurrency for multipart uploads (default 16)
      --azurefiles-use-msi                                  Use a managed service identity to authenticate (only works in Azure)
      --azurefiles-username string                          User name (usually an email address)
      --b2-account string                                   Account ID or Application Key ID
      --b2-chunk-size SizeSuffix                            Upload chunk size (default 96Mi)
      --b2-copy-cutoff SizeSuffix                           Cutoff for switching to multipart copy (default 4Gi)
      --b2-description string                               Description of the remote
      --b2-disable-checksum                                 Disable checksums for large (&gt; upload cutoff) files
      --b2-download-auth-duration Duration                  Time before the public link authorization token will expire in s or suffix ms|s|m|h|d (default 1w)
      --b2-download-url string                              Custom endpoint for downloads
      --b2-encoding Encoding                                The encoding for the backend (default Slash,BackSlash,Del,Ctl,InvalidUtf8,Dot)
      --b2-endpoint string                                  Endpoint for the service
      --b2-hard-delete                                      Permanently delete files on remote removal, otherwise hide files
      --b2-key string                                       Application Key
      --b2-lifecycle int                                    Set the number of days deleted files should be kept when creating a bucket
      --b2-test-mode string                                 A flag string for X-Bz-Test-Mode header for debugging
      --b2-upload-concurrency int                           Concurrency for multipart uploads (default 4)
      --b2-upload-cutoff SizeSuffix                         Cutoff for switching to chunked upload (default 200Mi)
      --b2-version-at Time                                  Show file versions as they were at the specified time (default off)
      --b2-versions                                         Include old versions in directory listings
      --box-access-token string                             Box App Primary Access Token
      --box-auth-url string                                 Auth server URL
      --box-box-config-file string                          Box App config.json location
      --box-box-sub-type string                              (default &quot;user&quot;)
      --box-client-id string                                OAuth Client Id
      --box-client-secret string                            OAuth Client Secret
      --box-commit-retries int                              Max number of times to try committing a multipart file (default 100)
      --box-description string                              Description of the remote
      --box-encoding Encoding                               The encoding for the backend (default Slash,BackSlash,Del,Ctl,RightSpace,InvalidUtf8,Dot)
      --box-impersonate string                              Impersonate this user ID when using a service account
      --box-list-chunk int                                  Size of listing chunk 1-1000 (default 1000)
      --box-owned-by string                                 Only show items owned by the login (email address) passed in
      --box-root-folder-id string                           Fill in for rclone to use a non root folder as its starting point
      --box-token string                                    OAuth Access Token as a JSON blob
      --box-token-url string                                Token server url
      --box-upload-cutoff SizeSuffix                        Cutoff for switching to multipart upload (&gt;= 50 MiB) (default 50Mi)
      --cache-chunk-clean-interval Duration                 How often should the cache perform cleanups of the chunk storage (default 1m0s)
      --cache-chunk-no-memory                               Disable the in-memory cache for storing chunks during streaming
      --cache-chunk-path string                             Directory to cache chunk files (default &quot;$HOME/.cache/rclone/cache-backend&quot;)
      --cache-chunk-size SizeSuffix                         The size of a chunk (partial file data) (default 5Mi)
      --cache-chunk-total-size SizeSuffix                   The total size that the chunks can take up on the local disk (default 10Gi)
      --cache-db-path string                                Directory to store file structure metadata DB (default &quot;$HOME/.cache/rclone/cache-backend&quot;)
      --cache-db-purge                                      Clear all the cached data for this remote on start
      --cache-db-wait-time Duration                         How long to wait for the DB to be available - 0 is unlimited (default 1s)
      --cache-description string                            Description of the remote
      --cache-info-age Duration                             How long to cache file structure information (directory listings, file size, times, etc.) (default 6h0m0s)
      --cache-plex-insecure string                          Skip all certificate verification when connecting to the Plex server
      --cache-plex-password string                          The password of the Plex user (obscured)
      --cache-plex-url string                               The URL of the Plex server
      --cache-plex-username string                          The username of the Plex user
      --cache-read-retries int                              How many times to retry a read from a cache storage (default 10)
      --cache-remote string                                 Remote to cache
      --cache-rps int                                       Limits the number of requests per second to the source FS (-1 to disable) (default -1)
      --cache-tmp-upload-path string                        Directory to keep temporary files until they are uploaded
      --cache-tmp-wait-time Duration                        How long should files be stored in local cache before being uploaded (default 15s)
      --cache-workers int                                   How many workers should run in parallel to download chunks (default 4)
      --cache-writes                                        Cache file data on writes through the FS
      --chunker-chunk-size SizeSuffix                       Files larger than chunk size will be split in chunks (default 2Gi)
      --chunker-description string                          Description of the remote
      --chunker-fail-hard                                   Choose how chunker should handle files with missing or invalid chunks
      --chunker-hash-type string                            Choose how chunker handles hash sums (default &quot;md5&quot;)
      --chunker-remote string                               Remote to chunk/unchunk
      --combine-description string                          Description of the remote
      --combine-upstreams SpaceSepList                      Upstreams for combining
      --compress-description string                         Description of the remote
      --compress-level int                                  GZIP compression level (-2 to 9) (default -1)
      --compress-mode string                                Compression mode (default &quot;gzip&quot;)
      --compress-ram-cache-limit SizeSuffix                 Some remotes don&#39;t allow the upload of files with unknown size (default 20Mi)
      --compress-remote string                              Remote to compress
  -L, --copy-links                                          Follow symlinks and copy the pointed to item
      --crypt-description string                            Description of the remote
      --crypt-directory-name-encryption                     Option to either encrypt directory names or leave them intact (default true)
      --crypt-filename-encoding string                      How to encode the encrypted filename to text string (default &quot;base32&quot;)
      --crypt-filename-encryption string                    How to encrypt the filenames (default &quot;standard&quot;)
      --crypt-no-data-encryption                            Option to either encrypt file data or leave it unencrypted
      --crypt-pass-bad-blocks                               If set this will pass bad blocks through as all 0
      --crypt-password string                               Password or pass phrase for encryption (obscured)
      --crypt-password2 string                              Password or pass phrase for salt (obscured)
      --crypt-remote string                                 Remote to encrypt/decrypt
      --crypt-server-side-across-configs                    Deprecated: use --server-side-across-configs instead
      --crypt-show-mapping                                  For all files listed show how the names encrypt
      --crypt-strict-names                                  If set, this will raise an error when crypt comes across a filename that can&#39;t be decrypted
      --crypt-suffix string                                 If this is set it will override the default suffix of &quot;.bin&quot; (default &quot;.bin&quot;)
      --drive-acknowledge-abuse                             Set to allow files which return cannotDownloadAbusiveFile to be downloaded
      --drive-allow-import-name-change                      Allow the filetype to change when uploading Google docs
      --drive-auth-owner-only                               Only consider files owned by the authenticated user
      --drive-auth-url string                               Auth server URL
      --drive-chunk-size SizeSuffix                         Upload chunk size (default 8Mi)
      --drive-client-id string                              Google Application Client Id
      --drive-client-secret string                          OAuth Client Secret
      --drive-copy-shortcut-content                         Server side copy contents of shortcuts instead of the shortcut
      --drive-description string                            Description of the remote
      --drive-disable-http2                                 Disable drive using http2 (default true)
      --drive-encoding Encoding                             The encoding for the backend (default InvalidUtf8)
      --drive-env-auth                                      Get IAM credentials from runtime (environment variables or instance meta data if no env vars)
      --drive-export-formats string                         Comma separated list of preferred formats for downloading Google docs (default &quot;docx,xlsx,pptx,svg&quot;)
      --drive-fast-list-bug-fix                             Work around a bug in Google Drive listing (default true)
      --drive-formats string                                Deprecated: See export_formats
      --drive-impersonate string                            Impersonate this user when using a service account
      --drive-import-formats string                         Comma separated list of preferred formats for uploading Google docs
      --drive-keep-revision-forever                         Keep new head revision of each file forever
      --drive-list-chunk int                                Size of listing chunk 100-1000, 0 to disable (default 1000)
      --drive-metadata-labels Bits                          Control whether labels should be read or written in metadata (default off)
      --drive-metadata-owner Bits                           Control whether owner should be read or written in metadata (default read)
      --drive-metadata-permissions Bits                     Control whether permissions should be read or written in metadata (default off)
      --drive-pacer-burst int                               Number of API calls to allow without sleeping (default 100)
      --drive-pacer-min-sleep Duration                      Minimum time to sleep between API calls (default 100ms)
      --drive-resource-key string                           Resource key for accessing a link-shared file
      --drive-root-folder-id string                         ID of the root folder
      --drive-scope string                                  Comma separated list of scopes that rclone should use when requesting access from drive
      --drive-server-side-across-configs                    Deprecated: use --server-side-across-configs instead
      --drive-service-account-credentials string            Service Account Credentials JSON blob
      --drive-service-account-file string                   Service Account Credentials JSON file path
      --drive-shared-with-me                                Only show files that are shared with me
      --drive-show-all-gdocs                                Show all Google Docs including non-exportable ones in listings
      --drive-size-as-quota                                 Show sizes as storage quota usage, not actual size
      --drive-skip-checksum-gphotos                         Skip checksums on Google photos and videos only
      --drive-skip-dangling-shortcuts                       If set skip dangling shortcut files
      --drive-skip-gdocs                                    Skip google documents in all listings
      --drive-skip-shortcuts                                If set skip shortcut files
      --drive-starred-only                                  Only show files that are starred
      --drive-stop-on-download-limit                        Make download limit errors be fatal
      --drive-stop-on-upload-limit                          Make upload limit errors be fatal
      --drive-team-drive string                             ID of the Shared Drive (Team Drive)
      --drive-token string                                  OAuth Access Token as a JSON blob
      --drive-token-url string                              Token server url
      --drive-trashed-only                                  Only show files that are in the trash
      --drive-upload-cutoff SizeSuffix                      Cutoff for switching to chunked upload (default 8Mi)
      --drive-use-created-date                              Use file created date instead of modified date
      --drive-use-shared-date                               Use date file was shared instead of modified date
      --drive-use-trash                                     Send files to the trash instead of deleting permanently (default true)
      --drive-v2-download-min-size SizeSuffix               If Object&#39;s are greater, use drive v2 API to download (default off)
      --dropbox-auth-url string                             Auth server URL
      --dropbox-batch-commit-timeout Duration               Max time to wait for a batch to finish committing (default 10m0s)
      --dropbox-batch-mode string                           Upload file batching sync|async|off (default &quot;sync&quot;)
      --dropbox-batch-size int                              Max number of files in upload batch
      --dropbox-batch-timeout Duration                      Max time to allow an idle upload batch before uploading (default 0s)
      --dropbox-chunk-size SizeSuffix                       Upload chunk size (&lt; 150Mi) (default 48Mi)
      --dropbox-client-id string                            OAuth Client Id
      --dropbox-client-secret string                        OAuth Client Secret
      --dropbox-description string                          Description of the remote
      --dropbox-encoding Encoding                           The encoding for the backend (default Slash,BackSlash,Del,RightSpace,InvalidUtf8,Dot)
      --dropbox-impersonate string                          Impersonate this user when using a business account
      --dropbox-pacer-min-sleep Duration                    Minimum time to sleep between API calls (default 10ms)
      --dropbox-root-namespace string                       Specify a different Dropbox namespace ID to use as the root for all paths
      --dropbox-shared-files                                Instructs rclone to work on individual shared files
      --dropbox-shared-folders                              Instructs rclone to work on shared folders
      --dropbox-token string                                OAuth Access Token as a JSON blob
      --dropbox-token-url string                            Token server url
      --fichier-api-key string                              Your API Key, get it from https://1fichier.com/console/params.pl
      --fichier-cdn                                         Set if you wish to use CDN download links
      --fichier-description string                          Description of the remote
      --fichier-encoding Encoding                           The encoding for the backend (default Slash,LtGt,DoubleQuote,SingleQuote,BackQuote,Dollar,BackSlash,Del,Ctl,LeftSpace,RightSpace,InvalidUtf8,Dot)
      --fichier-file-password string                        If you want to download a shared file that is password protected, add this parameter (obscured)
      --fichier-folder-password string                      If you want to list the files in a shared folder that is password protected, add this parameter (obscured)
      --fichier-shared-folder string                        If you want to download a shared folder, add this parameter
      --filefabric-description string                       Description of the remote
      --filefabric-encoding Encoding                        The encoding for the backend (default Slash,Del,Ctl,InvalidUtf8,Dot)
      --filefabric-permanent-token string                   Permanent Authentication Token
      --filefabric-root-folder-id string                    ID of the root folder
      --filefabric-token string                             Session Token
      --filefabric-token-expiry string                      Token expiry time
      --filefabric-url string                               URL of the Enterprise File Fabric to connect to
      --filefabric-version string                           Version read from the file fabric
      --filescom-api-key string                             The API key used to authenticate with Files.com
      --filescom-description string                         Description of the remote
      --filescom-encoding Encoding                          The encoding for the backend (default Slash,BackSlash,Del,Ctl,RightSpace,RightCrLfHtVt,InvalidUtf8,Dot)
      --filescom-password string                            The password used to authenticate with Files.com (obscured)
      --filescom-site string                                Your site subdomain (e.g. mysite) or custom domain (e.g. myfiles.customdomain.com)
      --filescom-username string                            The username used to authenticate with Files.com
      --ftp-ask-password                                    Allow asking for FTP password when needed
      --ftp-close-timeout Duration                          Maximum time to wait for a response to close (default 1m0s)
      --ftp-concurrency int                                 Maximum number of FTP simultaneous connections, 0 for unlimited
      --ftp-description string                              Description of the remote
      --ftp-disable-epsv                                    Disable using EPSV even if server advertises support
      --ftp-disable-mlsd                                    Disable using MLSD even if server advertises support
      --ftp-disable-tls13                                   Disable TLS 1.3 (workaround for FTP servers with buggy TLS)
      --ftp-disable-utf8                                    Disable using UTF-8 even if server advertises support
      --ftp-encoding Encoding                               The encoding for the backend (default Slash,Del,Ctl,RightSpace,Dot)
      --ftp-explicit-tls                                    Use Explicit FTPS (FTP over TLS)
      --ftp-force-list-hidden                               Use LIST -a to force listing of hidden files and folders. This will disable the use of MLSD
      --ftp-host string                                     FTP host to connect to
      --ftp-idle-timeout Duration                           Max time before closing idle connections (default 1m0s)
      --ftp-no-check-certificate                            Do not verify the TLS certificate of the server
      --ftp-pass string                                     FTP password (obscured)
      --ftp-port int                                        FTP port number (default 21)
      --ftp-shut-timeout Duration                           Maximum time to wait for data connection closing status (default 1m0s)
      --ftp-socks-proxy string                              Socks 5 proxy host
      --ftp-tls                                             Use Implicit FTPS (FTP over TLS)
      --ftp-tls-cache-size int                              Size of TLS session cache for all control and data connections (default 32)
      --ftp-user string                                     FTP username (default &quot;$USER&quot;)
      --ftp-writing-mdtm                                    Use MDTM to set modification time (VsFtpd quirk)
      --gcs-anonymous                                       Access public buckets and objects without credentials
      --gcs-auth-url string                                 Auth server URL
      --gcs-bucket-acl string                               Access Control List for new buckets
      --gcs-bucket-policy-only                              Access checks should use bucket-level IAM policies
      --gcs-client-id string                                OAuth Client Id
      --gcs-client-secret string                            OAuth Client Secret
      --gcs-decompress                                      If set this will decompress gzip encoded objects
      --gcs-description string                              Description of the remote
      --gcs-directory-markers                               Upload an empty object with a trailing slash when a new directory is created
      --gcs-encoding Encoding                               The encoding for the backend (default Slash,CrLf,InvalidUtf8,Dot)
      --gcs-endpoint string                                 Endpoint for the service
      --gcs-env-auth                                        Get GCP IAM credentials from runtime (environment variables or instance meta data if no env vars)
      --gcs-location string                                 Location for the newly created buckets
      --gcs-no-check-bucket                                 If set, don&#39;t attempt to check the bucket exists or create it
      --gcs-object-acl string                               Access Control List for new objects
      --gcs-project-number string                           Project number
      --gcs-service-account-file string                     Service Account Credentials JSON file path
      --gcs-storage-class string                            The storage class to use when storing objects in Google Cloud Storage
      --gcs-token string                                    OAuth Access Token as a JSON blob
      --gcs-token-url string                                Token server url
      --gcs-user-project string                             User project
      --gofile-access-token string                          API Access token
      --gofile-account-id string                            Account ID
      --gofile-description string                           Description of the remote
      --gofile-encoding Encoding                            The encoding for the backend (default Slash,LtGt,DoubleQuote,Colon,Question,Asterisk,Pipe,BackSlash,Del,Ctl,LeftPeriod,RightPeriod,InvalidUtf8,Dot,Exclamation)
      --gofile-list-chunk int                               Number of items to list in each call (default 1000)
      --gofile-root-folder-id string                        ID of the root folder
      --gphotos-auth-url string                             Auth server URL
      --gphotos-batch-commit-timeout Duration               Max time to wait for a batch to finish committing (default 10m0s)
      --gphotos-batch-mode string                           Upload file batching sync|async|off (default &quot;sync&quot;)
      --gphotos-batch-size int                              Max number of files in upload batch
      --gphotos-batch-timeout Duration                      Max time to allow an idle upload batch before uploading (default 0s)
      --gphotos-client-id string                            OAuth Client Id
      --gphotos-client-secret string                        OAuth Client Secret
      --gphotos-description string                          Description of the remote
      --gphotos-encoding Encoding                           The encoding for the backend (default Slash,CrLf,InvalidUtf8,Dot)
      --gphotos-include-archived                            Also view and download archived media
      --gphotos-read-only                                   Set to make the Google Photos backend read only
      --gphotos-read-size                                   Set to read the size of media items
      --gphotos-start-year int                              Year limits the photos to be downloaded to those which are uploaded after the given year (default 2000)
      --gphotos-token string                                OAuth Access Token as a JSON blob
      --gphotos-token-url string                            Token server url
      --hasher-auto-size SizeSuffix                         Auto-update checksum for files smaller than this size (disabled by default)
      --hasher-description string                           Description of the remote
      --hasher-hashes CommaSepList                          Comma separated list of supported checksum types (default md5,sha1)
      --hasher-max-age Duration                             Maximum time to keep checksums in cache (0 = no cache, off = cache forever) (default off)
      --hasher-remote string                                Remote to cache checksums for (e.g. myRemote:path)
      --hdfs-data-transfer-protection string                Kerberos data transfer protection: authentication|integrity|privacy
      --hdfs-description string                             Description of the remote
      --hdfs-encoding Encoding                              The encoding for the backend (default Slash,Colon,Del,Ctl,InvalidUtf8,Dot)
      --hdfs-namenode CommaSepList                          Hadoop name nodes and ports
      --hdfs-service-principal-name string                  Kerberos service principal name for the namenode
      --hdfs-username string                                Hadoop user name
      --hidrive-auth-url string                             Auth server URL
      --hidrive-chunk-size SizeSuffix                       Chunksize for chunked uploads (default 48Mi)
      --hidrive-client-id string                            OAuth Client Id
      --hidrive-client-secret string                        OAuth Client Secret
      --hidrive-description string                          Description of the remote
      --hidrive-disable-fetching-member-count               Do not fetch number of objects in directories unless it is absolutely necessary
      --hidrive-encoding Encoding                           The encoding for the backend (default Slash,Dot)
      --hidrive-endpoint string                             Endpoint for the service (default &quot;https://api.hidrive.strato.com/2.1&quot;)
      --hidrive-root-prefix string                          The root/parent folder for all paths (default &quot;/&quot;)
      --hidrive-scope-access string                         Access permissions that rclone should use when requesting access from HiDrive (default &quot;rw&quot;)
      --hidrive-scope-role string                           User-level that rclone should use when requesting access from HiDrive (default &quot;user&quot;)
      --hidrive-token string                                OAuth Access Token as a JSON blob
      --hidrive-token-url string                            Token server url
      --hidrive-upload-concurrency int                      Concurrency for chunked uploads (default 4)
      --hidrive-upload-cutoff SizeSuffix                    Cutoff/Threshold for chunked uploads (default 96Mi)
      --http-description string                             Description of the remote
      --http-headers CommaSepList                           Set HTTP headers for all transactions
      --http-no-escape                                      Do not escape URL metacharacters in path names
      --http-no-head                                        Don&#39;t use HEAD requests
      --http-no-slash                                       Set this if the site doesn&#39;t end directories with /
      --http-url string                                     URL of HTTP host to connect to
      --imagekit-description string                         Description of the remote
      --imagekit-encoding Encoding                          The encoding for the backend (default Slash,LtGt,DoubleQuote,Dollar,Question,Hash,Percent,BackSlash,Del,Ctl,InvalidUtf8,Dot,SquareBracket)
      --imagekit-endpoint string                            You can find your ImageKit.io URL endpoint in your [dashboard](https://imagekit.io/dashboard/developer/api-keys)
      --imagekit-only-signed Restrict unsigned image URLs   If you have configured Restrict unsigned image URLs in your dashboard settings, set this to true
      --imagekit-private-key string                         You can find your ImageKit.io private key in your [dashboard](https://imagekit.io/dashboard/developer/api-keys)
      --imagekit-public-key string                          You can find your ImageKit.io public key in your [dashboard](https://imagekit.io/dashboard/developer/api-keys)
      --imagekit-upload-tags string                         Tags to add to the uploaded files, e.g. &quot;tag1,tag2&quot;
      --imagekit-versions                                   Include old versions in directory listings
      --internetarchive-access-key-id string                IAS3 Access Key
      --internetarchive-description string                  Description of the remote
      --internetarchive-disable-checksum                    Don&#39;t ask the server to test against MD5 checksum calculated by rclone (default true)
      --internetarchive-encoding Encoding                   The encoding for the backend (default Slash,LtGt,CrLf,Del,Ctl,InvalidUtf8,Dot)
      --internetarchive-endpoint string                     IAS3 Endpoint (default &quot;https://s3.us.archive.org&quot;)
      --internetarchive-front-endpoint string               Host of InternetArchive Frontend (default &quot;https://archive.org&quot;)
      --internetarchive-secret-access-key string            IAS3 Secret Key (password)
      --internetarchive-wait-archive Duration               Timeout for waiting the server&#39;s processing tasks (specifically archive and book_op) to finish (default 0s)
      --jottacloud-auth-url string                          Auth server URL
      --jottacloud-client-id string                         OAuth Client Id
      --jottacloud-client-secret string                     OAuth Client Secret
      --jottacloud-description string                       Description of the remote
      --jottacloud-encoding Encoding                        The encoding for the backend (default Slash,LtGt,DoubleQuote,Colon,Question,Asterisk,Pipe,Del,Ctl,InvalidUtf8,Dot)
      --jottacloud-hard-delete                              Delete files permanently rather than putting them into the trash
      --jottacloud-md5-memory-limit SizeSuffix              Files bigger than this will be cached on disk to calculate the MD5 if required (default 10Mi)
      --jottacloud-no-versions                              Avoid server side versioning by deleting files and recreating files instead of overwriting them
      --jottacloud-token string                             OAuth Access Token as a JSON blob
      --jottacloud-token-url string                         Token server url
      --jottacloud-trashed-only                             Only show files that are in the trash
      --jottacloud-upload-resume-limit SizeSuffix           Files bigger than this can be resumed if the upload fail&#39;s (default 10Mi)
      --koofr-description string                            Description of the remote
      --koofr-encoding Encoding                             The encoding for the backend (default Slash,BackSlash,Del,Ctl,InvalidUtf8,Dot)
      --koofr-endpoint string                               The Koofr API endpoint to use
      --koofr-mountid string                                Mount ID of the mount to use
      --koofr-password string                               Your password for rclone generate one at https://app.koofr.net/app/admin/preferences/password (obscured)
      --koofr-provider string                               Choose your storage provider
      --koofr-setmtime                                      Does the backend support setting modification time (default true)
      --koofr-user string                                   Your user name
      --linkbox-description string                          Description of the remote
      --linkbox-token string                                Token from https://www.linkbox.to/admin/account
  -l, --links                                               Translate symlinks to/from regular files with a &#39;.rclonelink&#39; extension
      --local-case-insensitive                              Force the filesystem to report itself as case insensitive
      --local-case-sensitive                                Force the filesystem to report itself as case sensitive
      --local-description string                            Description of the remote
      --local-encoding Encoding                             The encoding for the backend (default Slash,Dot)
      --local-no-check-updated                              Don&#39;t check to see if the files change during upload
      --local-no-clone                                      Disable reflink cloning for server-side copies
      --local-no-preallocate                                Disable preallocation of disk space for transferred files
      --local-no-set-modtime                                Disable setting modtime
      --local-no-sparse                                     Disable sparse files for multi-thread downloads
      --local-nounc                                         Disable UNC (long path names) conversion on Windows
      --local-time-type mtime|atime|btime|ctime             Set what kind of time is returned (default mtime)
      --local-unicode-normalization                         Apply unicode NFC normalization to paths and filenames
      --local-zero-size-links                               Assume the Stat size of links is zero (and read them instead) (deprecated)
      --mailru-auth-url string                              Auth server URL
      --mailru-check-hash                                   What should copy do if file checksum is mismatched or invalid (default true)
      --mailru-client-id string                             OAuth Client Id
      --mailru-client-secret string                         OAuth Client Secret
      --mailru-description string                           Description of the remote
      --mailru-encoding Encoding                            The encoding for the backend (default Slash,LtGt,DoubleQuote,Colon,Question,Asterisk,Pipe,BackSlash,Del,Ctl,InvalidUtf8,Dot)
      --mailru-pass string                                  Password (obscured)
      --mailru-speedup-enable                               Skip full upload if there is another file with same data hash (default true)
      --mailru-speedup-file-patterns string                 Comma separated list of file name patterns eligible for speedup (put by hash) (default &quot;*.mkv,*.avi,*.mp4,*.mp3,*.zip,*.gz,*.rar,*.pdf&quot;)
      --mailru-speedup-max-disk SizeSuffix                  This option allows you to disable speedup (put by hash) for large files (default 3Gi)
      --mailru-speedup-max-memory SizeSuffix                Files larger than the size given below will always be hashed on disk (default 32Mi)
      --mailru-token string                                 OAuth Access Token as a JSON blob
      --mailru-token-url string                             Token server url
      --mailru-user string                                  User name (usually email)
      --mega-debug                                          Output more debug from Mega
      --mega-description string                             Description of the remote
      --mega-encoding Encoding                              The encoding for the backend (default Slash,InvalidUtf8,Dot)
      --mega-hard-delete                                    Delete files permanently rather than putting them into the trash
      --mega-pass string                                    Password (obscured)
      --mega-use-https                                      Use HTTPS for transfers
      --mega-user string                                    User name
      --memory-description string                           Description of the remote
      --netstorage-account string                           Set the NetStorage account name
      --netstorage-description string                       Description of the remote
      --netstorage-host string                              Domain+path of NetStorage host to connect to
      --netstorage-protocol string                          Select between HTTP or HTTPS protocol (default &quot;https&quot;)
      --netstorage-secret string                            Set the NetStorage account secret/G2O key for authentication (obscured)
  -x, --one-file-system                                     Don&#39;t cross filesystem boundaries (unix/macOS only)
      --onedrive-access-scopes SpaceSepList                 Set scopes to be requested by rclone (default Files.Read Files.ReadWrite Files.Read.All Files.ReadWrite.All Sites.Read.All offline_access)
      --onedrive-auth-url string                            Auth server URL
      --onedrive-av-override                                Allows download of files the server thinks has a virus
      --onedrive-chunk-size SizeSuffix                      Chunk size to upload files with - must be multiple of 320k (327,680 bytes) (default 10Mi)
      --onedrive-client-id string                           OAuth Client Id
      --onedrive-client-secret string                       OAuth Client Secret
      --onedrive-delta                                      If set rclone will use delta listing to implement recursive listings
      --onedrive-description string                         Description of the remote
      --onedrive-drive-id string                            The ID of the drive to use
      --onedrive-drive-type string                          The type of the drive (personal | business | documentLibrary)
      --onedrive-encoding Encoding                          The encoding for the backend (default Slash,LtGt,DoubleQuote,Colon,Question,Asterisk,Pipe,BackSlash,Del,Ctl,LeftSpace,LeftTilde,RightSpace,RightPeriod,InvalidUtf8,Dot)
      --onedrive-expose-onenote-files                       Set to make OneNote files show up in directory listings
      --onedrive-hard-delete                                Permanently delete files on removal
      --onedrive-hash-type string                           Specify the hash in use for the backend (default &quot;auto&quot;)
      --onedrive-link-password string                       Set the password for links created by the link command
      --onedrive-link-scope string                          Set the scope of the links created by the link command (default &quot;anonymous&quot;)
      --onedrive-link-type string                           Set the type of the links created by the link command (default &quot;view&quot;)
      --onedrive-list-chunk int                             Size of listing chunk (default 1000)
      --onedrive-metadata-permissions Bits                  Control whether permissions should be read or written in metadata (default off)
      --onedrive-no-versions                                Remove all versions on modifying operations
      --onedrive-region string                              Choose national cloud region for OneDrive (default &quot;global&quot;)
      --onedrive-root-folder-id string                      ID of the root folder
      --onedrive-server-side-across-configs                 Deprecated: use --server-side-across-configs instead
      --onedrive-token string                               OAuth Access Token as a JSON blob
      --onedrive-token-url string                           Token server url
      --oos-attempt-resume-upload                           If true attempt to resume previously started multipart upload for the object
      --oos-chunk-size SizeSuffix                           Chunk size to use for uploading (default 5Mi)
      --oos-compartment string                              Object storage compartment OCID
      --oos-config-file string                              Path to OCI config file (default &quot;~/.oci/config&quot;)
      --oos-config-profile string                           Profile name inside the oci config file (default &quot;Default&quot;)
      --oos-copy-cutoff SizeSuffix                          Cutoff for switching to multipart copy (default 4.656Gi)
      --oos-copy-timeout Duration                           Timeout for copy (default 1m0s)
      --oos-description string                              Description of the remote
      --oos-disable-checksum                                Don&#39;t store MD5 checksum with object metadata
      --oos-encoding Encoding                               The encoding for the backend (default Slash,InvalidUtf8,Dot)
      --oos-endpoint string                                 Endpoint for Object storage API
      --oos-leave-parts-on-error                            If true avoid calling abort upload on a failure, leaving all successfully uploaded parts for manual recovery
      --oos-max-upload-parts int                            Maximum number of parts in a multipart upload (default 10000)
      --oos-namespace string                                Object storage namespace
      --oos-no-check-bucket                                 If set, don&#39;t attempt to check the bucket exists or create it
      --oos-provider string                                 Choose your Auth Provider (default &quot;env_auth&quot;)
      --oos-region string                                   Object storage Region
      --oos-sse-customer-algorithm string                   If using SSE-C, the optional header that specifies &quot;AES256&quot; as the encryption algorithm
      --oos-sse-customer-key string                         To use SSE-C, the optional header that specifies the base64-encoded 256-bit encryption key to use to
      --oos-sse-customer-key-file string                    To use SSE-C, a file containing the base64-encoded string of the AES-256 encryption key associated
      --oos-sse-customer-key-sha256 string                  If using SSE-C, The optional header that specifies the base64-encoded SHA256 hash of the encryption
      --oos-sse-kms-key-id string                           if using your own master key in vault, this header specifies the
      --oos-storage-tier string                             The storage class to use when storing new objects in storage. https://docs.oracle.com/en-us/iaas/Content/Object/Concepts/understandingstoragetiers.htm (default &quot;Standard&quot;)
      --oos-upload-concurrency int                          Concurrency for multipart uploads (default 10)
      --oos-upload-cutoff SizeSuffix                        Cutoff for switching to chunked upload (default 200Mi)
      --opendrive-chunk-size SizeSuffix                     Files will be uploaded in chunks this size (default 10Mi)
      --opendrive-description string                        Description of the remote
      --opendrive-encoding Encoding                         The encoding for the backend (default Slash,LtGt,DoubleQuote,Colon,Question,Asterisk,Pipe,BackSlash,LeftSpace,LeftCrLfHtVt,RightSpace,RightCrLfHtVt,InvalidUtf8,Dot)
      --opendrive-password string                           Password (obscured)
      --opendrive-username string                           Username
      --pcloud-auth-url string                              Auth server URL
      --pcloud-client-id string                             OAuth Client Id
      --pcloud-client-secret string                         OAuth Client Secret
      --pcloud-description string                           Description of the remote
      --pcloud-encoding Encoding                            The encoding for the backend (default Slash,BackSlash,Del,Ctl,InvalidUtf8,Dot)
      --pcloud-hostname string                              Hostname to connect to (default &quot;api.pcloud.com&quot;)
      --pcloud-password string                              Your pcloud password (obscured)
      --pcloud-root-folder-id string                        Fill in for rclone to use a non root folder as its starting point (default &quot;d0&quot;)
      --pcloud-token string                                 OAuth Access Token as a JSON blob
      --pcloud-token-url string                             Token server url
      --pcloud-username string                              Your pcloud username
      --pikpak-chunk-size SizeSuffix                        Chunk size for multipart uploads (default 5Mi)
      --pikpak-description string                           Description of the remote
      --pikpak-device-id string                             Device ID used for authorization
      --pikpak-encoding Encoding                            The encoding for the backend (default Slash,LtGt,DoubleQuote,Colon,Question,Asterisk,Pipe,BackSlash,Ctl,LeftSpace,RightSpace,RightPeriod,InvalidUtf8,Dot)
      --pikpak-hash-memory-limit SizeSuffix                 Files bigger than this will be cached on disk to calculate hash if required (default 10Mi)
      --pikpak-pass string                                  Pikpak password (obscured)
      --pikpak-root-folder-id string                        ID of the root folder
      --pikpak-trashed-only                                 Only show files that are in the trash
      --pikpak-upload-concurrency int                       Concurrency for multipart uploads (default 5)
      --pikpak-use-trash                                    Send files to the trash instead of deleting permanently (default true)
      --pikpak-user string                                  Pikpak username
      --pikpak-user-agent string                            HTTP user agent for pikpak (default &quot;Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:129.0) Gecko/20100101 Firefox/129.0&quot;)
      --pixeldrain-api-key string                           API key for your pixeldrain account
      --pixeldrain-api-url string                           The API endpoint to connect to. In the vast majority of cases it&#39;s fine to leave (default &quot;https://pixeldrain.com/api&quot;)
      --pixeldrain-description string                       Description of the remote
      --pixeldrain-root-folder-id string                    Root of the filesystem to use (default &quot;me&quot;)
      --premiumizeme-auth-url string                        Auth server URL
      --premiumizeme-client-id string                       OAuth Client Id
      --premiumizeme-client-secret string                   OAuth Client Secret
      --premiumizeme-description string                     Description of the remote
      --premiumizeme-encoding Encoding                      The encoding for the backend (default Slash,DoubleQuote,BackSlash,Del,Ctl,InvalidUtf8,Dot)
      --premiumizeme-token string                           OAuth Access Token as a JSON blob
      --premiumizeme-token-url string                       Token server url
      --protondrive-2fa string                              The 2FA code
      --protondrive-app-version string                      The app version string (default &quot;macos-drive@1.0.0-alpha.1+rclone&quot;)
      --protondrive-description string                      Description of the remote
      --protondrive-enable-caching                          Caches the files and folders metadata to reduce API calls (default true)
      --protondrive-encoding Encoding                       The encoding for the backend (default Slash,LeftSpace,RightSpace,InvalidUtf8,Dot)
      --protondrive-mailbox-password string                 The mailbox password of your two-password proton account (obscured)
      --protondrive-original-file-size                      Return the file size before encryption (default true)
      --protondrive-password string                         The password of your proton account (obscured)
      --protondrive-replace-existing-draft                  Create a new revision when filename conflict is detected
      --protondrive-username string                         The username of your proton account
      --putio-auth-url string                               Auth server URL
      --putio-client-id string                              OAuth Client Id
      --putio-client-secret string                          OAuth Client Secret
      --putio-description string                            Description of the remote
      --putio-encoding Encoding                             The encoding for the backend (default Slash,BackSlash,Del,Ctl,InvalidUtf8,Dot)
      --putio-token string                                  OAuth Access Token as a JSON blob
      --putio-token-url string                              Token server url
      --qingstor-access-key-id string                       QingStor Access Key ID
      --qingstor-chunk-size SizeSuffix                      Chunk size to use for uploading (default 4Mi)
      --qingstor-connection-retries int                     Number of connection retries (default 3)
      --qingstor-description string                         Description of the remote
      --qingstor-encoding Encoding                          The encoding for the backend (default Slash,Ctl,InvalidUtf8)
      --qingstor-endpoint string                            Enter an endpoint URL to connection QingStor API
      --qingstor-env-auth                                   Get QingStor credentials from runtime
      --qingstor-secret-access-key string                   QingStor Secret Access Key (password)
      --qingstor-upload-concurrency int                     Concurrency for multipart uploads (default 1)
      --qingstor-upload-cutoff SizeSuffix                   Cutoff for switching to chunked upload (default 200Mi)
      --qingstor-zone string                                Zone to connect to
      --quatrix-api-key string                              API key for accessing Quatrix account
      --quatrix-description string                          Description of the remote
      --quatrix-effective-upload-time string                Wanted upload time for one chunk (default &quot;4s&quot;)
      --quatrix-encoding Encoding                           The encoding for the backend (default Slash,BackSlash,Del,Ctl,InvalidUtf8,Dot)
      --quatrix-hard-delete                                 Delete files permanently rather than putting them into the trash
      --quatrix-host string                                 Host name of Quatrix account
      --quatrix-maximal-summary-chunk-size SizeSuffix       The maximal summary for all chunks. It should not be less than &#39;transfers&#39;*&#39;minimal_chunk_size&#39; (default 95.367Mi)
      --quatrix-minimal-chunk-size SizeSuffix               The minimal size for one chunk (default 9.537Mi)
      --quatrix-skip-project-folders                        Skip project folders in operations
      --s3-access-key-id string                             AWS Access Key ID
      --s3-acl string                                       Canned ACL used when creating buckets and storing or copying objects
      --s3-bucket-acl string                                Canned ACL used when creating buckets
      --s3-chunk-size SizeSuffix                            Chunk size to use for uploading (default 5Mi)
      --s3-copy-cutoff SizeSuffix                           Cutoff for switching to multipart copy (default 4.656Gi)
      --s3-decompress                                       If set this will decompress gzip encoded objects
      --s3-description string                               Description of the remote
      --s3-directory-markers                                Upload an empty object with a trailing slash when a new directory is created
      --s3-disable-checksum                                 Don&#39;t store MD5 checksum with object metadata
      --s3-disable-http2                                    Disable usage of http2 for S3 backends
      --s3-download-url string                              Custom endpoint for downloads
      --s3-encoding Encoding                                The encoding for the backend (default Slash,InvalidUtf8,Dot)
      --s3-endpoint string                                  Endpoint for S3 API
      --s3-env-auth                                         Get AWS credentials from runtime (environment variables or EC2/ECS meta data if no env vars)
      --s3-force-path-style                                 If true use path style access if false use virtual hosted style (default true)
      --s3-leave-parts-on-error                             If true avoid calling abort upload on a failure, leaving all successfully uploaded parts on S3 for manual recovery
      --s3-list-chunk int                                   Size of listing chunk (response list for each ListObject S3 request) (default 1000)
      --s3-list-url-encode Tristate                         Whether to url encode listings: true/false/unset (default unset)
      --s3-list-version int                                 Version of ListObjects to use: 1,2 or 0 for auto
      --s3-location-constraint string                       Location constraint - must be set to match the Region
      --s3-max-upload-parts int                             Maximum number of parts in a multipart upload (default 10000)
      --s3-might-gzip Tristate                              Set this if the backend might gzip objects (default unset)
      --s3-no-check-bucket                                  If set, don&#39;t attempt to check the bucket exists or create it
      --s3-no-head                                          If set, don&#39;t HEAD uploaded objects to check integrity
      --s3-no-head-object                                   If set, do not do HEAD before GET when getting objects
      --s3-no-system-metadata                               Suppress setting and reading of system metadata
      --s3-profile string                                   Profile to use in the shared credentials file
      --s3-provider string                                  Choose your S3 provider
      --s3-region string                                    Region to connect to
      --s3-requester-pays                                   Enables requester pays option when interacting with S3 bucket
      --s3-sdk-log-mode Bits                                Set to debug the SDK (default Off)
      --s3-secret-access-key string                         AWS Secret Access Key (password)
      --s3-server-side-encryption string                    The server-side encryption algorithm used when storing this object in S3
      --s3-session-token string                             An AWS session token
      --s3-shared-credentials-file string                   Path to the shared credentials file
      --s3-sse-customer-algorithm string                    If using SSE-C, the server-side encryption algorithm used when storing this object in S3
      --s3-sse-customer-key string                          To use SSE-C you may provide the secret encryption key used to encrypt/decrypt your data
      --s3-sse-customer-key-base64 string                   If using SSE-C you must provide the secret encryption key encoded in base64 format to encrypt/decrypt your data
      --s3-sse-customer-key-md5 string                      If using SSE-C you may provide the secret encryption key MD5 checksum (optional)
      --s3-sse-kms-key-id string                            If using KMS ID you must provide the ARN of Key
      --s3-storage-class string                             The storage class to use when storing new objects in S3
      --s3-upload-concurrency int                           Concurrency for multipart uploads and copies (default 4)
      --s3-upload-cutoff SizeSuffix                         Cutoff for switching to chunked upload (default 200Mi)
      --s3-use-accelerate-endpoint                          If true use the AWS S3 accelerated endpoint
      --s3-use-accept-encoding-gzip Accept-Encoding: gzip   Whether to send Accept-Encoding: gzip header (default unset)
      --s3-use-already-exists Tristate                      Set if rclone should report BucketAlreadyExists errors on bucket creation (default unset)
      --s3-use-dual-stack                                   If true use AWS S3 dual-stack endpoint (IPv6 support)
      --s3-use-multipart-etag Tristate                      Whether to use ETag in multipart uploads for verification (default unset)
      --s3-use-multipart-uploads Tristate                   Set if rclone should use multipart uploads (default unset)
      --s3-use-presigned-request                            Whether to use a presigned request or PutObject for single part uploads
      --s3-use-unsigned-payload Tristate                    Whether to use an unsigned payload in PutObject (default unset)
      --s3-v2-auth                                          If true use v2 authentication
      --s3-version-at Time                                  Show file versions as they were at the specified time (default off)
      --s3-version-deleted                                  Show deleted file markers when using versions
      --s3-versions                                         Include old versions in directory listings
      --seafile-2fa                                         Two-factor authentication (&#39;true&#39; if the account has 2FA enabled)
      --seafile-create-library                              Should rclone create a library if it doesn&#39;t exist
      --seafile-description string                          Description of the remote
      --seafile-encoding Encoding                           The encoding for the backend (default Slash,DoubleQuote,BackSlash,Ctl,InvalidUtf8)
      --seafile-library string                              Name of the library
      --seafile-library-key string                          Library password (for encrypted libraries only) (obscured)
      --seafile-pass string                                 Password (obscured)
      --seafile-url string                                  URL of seafile host to connect to
      --seafile-user string                                 User name (usually email address)
      --sftp-ask-password                                   Allow asking for SFTP password when needed
      --sftp-chunk-size SizeSuffix                          Upload and download chunk size (default 32Ki)
      --sftp-ciphers SpaceSepList                           Space separated list of ciphers to be used for session encryption, ordered by preference
      --sftp-concurrency int                                The maximum number of outstanding requests for one file (default 64)
      --sftp-connections int                                Maximum number of SFTP simultaneous connections, 0 for unlimited
      --sftp-copy-is-hardlink                               Set to enable server side copies using hardlinks
      --sftp-description string                             Description of the remote
      --sftp-disable-concurrent-reads                       If set don&#39;t use concurrent reads
      --sftp-disable-concurrent-writes                      If set don&#39;t use concurrent writes
      --sftp-disable-hashcheck                              Disable the execution of SSH commands to determine if remote file hashing is available
      --sftp-host string                                    SSH host to connect to
      --sftp-host-key-algorithms SpaceSepList               Space separated list of host key algorithms, ordered by preference
      --sftp-idle-timeout Duration                          Max time before closing idle connections (default 1m0s)
      --sftp-key-exchange SpaceSepList                      Space separated list of key exchange algorithms, ordered by preference
      --sftp-key-file string                                Path to PEM-encoded private key file
      --sftp-key-file-pass string                           The passphrase to decrypt the PEM-encoded private key file (obscured)
      --sftp-key-pem string                                 Raw PEM-encoded private key
      --sftp-key-use-agent                                  When set forces the usage of the ssh-agent
      --sftp-known-hosts-file string                        Optional path to known_hosts file
      --sftp-macs SpaceSepList                              Space separated list of MACs (message authentication code) algorithms, ordered by preference
      --sftp-md5sum-command string                          The command used to read md5 hashes
      --sftp-pass string                                    SSH password, leave blank to use ssh-agent (obscured)
      --sftp-path-override string                           Override path used by SSH shell commands
      --sftp-port int                                       SSH port number (default 22)
      --sftp-pubkey-file string                             Optional path to public key file
      --sftp-server-command string                          Specifies the path or command to run a sftp server on the remote host
      --sftp-set-env SpaceSepList                           Environment variables to pass to sftp and commands
      --sftp-set-modtime                                    Set the modified time on the remote if set (default true)
      --sftp-sha1sum-command string                         The command used to read sha1 hashes
      --sftp-shell-type string                              The type of SSH shell on remote server, if any
      --sftp-skip-links                                     Set to skip any symlinks and any other non regular files
      --sftp-socks-proxy string                             Socks 5 proxy host
      --sftp-ssh SpaceSepList                               Path and arguments to external ssh binary
      --sftp-subsystem string                               Specifies the SSH2 subsystem on the remote host (default &quot;sftp&quot;)
      --sftp-use-fstat                                      If set use fstat instead of stat
      --sftp-use-insecure-cipher                            Enable the use of insecure ciphers and key exchange methods
      --sftp-user string                                    SSH username (default &quot;$USER&quot;)
      --sharefile-auth-url string                           Auth server URL
      --sharefile-chunk-size SizeSuffix                     Upload chunk size (default 64Mi)
      --sharefile-client-id string                          OAuth Client Id
      --sharefile-client-secret string                      OAuth Client Secret
      --sharefile-description string                        Description of the remote
      --sharefile-encoding Encoding                         The encoding for the backend (default Slash,LtGt,DoubleQuote,Colon,Question,Asterisk,Pipe,BackSlash,Ctl,LeftSpace,LeftPeriod,RightSpace,RightPeriod,InvalidUtf8,Dot)
      --sharefile-endpoint string                           Endpoint for API calls
      --sharefile-root-folder-id string                     ID of the root folder
      --sharefile-token string                              OAuth Access Token as a JSON blob
      --sharefile-token-url string                          Token server url
      --sharefile-upload-cutoff SizeSuffix                  Cutoff for switching to multipart upload (default 128Mi)
      --sia-api-password string                             Sia Daemon API Password (obscured)
      --sia-api-url string                                  Sia daemon API URL, like http://sia.daemon.host:9980 (default &quot;http://127.0.0.1:9980&quot;)
      --sia-description string                              Description of the remote
      --sia-encoding Encoding                               The encoding for the backend (default Slash,Question,Hash,Percent,Del,Ctl,InvalidUtf8,Dot)
      --sia-user-agent string                               Siad User Agent (default &quot;Sia-Agent&quot;)
      --skip-links                                          Don&#39;t warn about skipped symlinks
      --smb-case-insensitive                                Whether the server is configured to be case-insensitive (default true)
      --smb-description string                              Description of the remote
      --smb-domain string                                   Domain name for NTLM authentication (default &quot;WORKGROUP&quot;)
      --smb-encoding Encoding                               The encoding for the backend (default Slash,LtGt,DoubleQuote,Colon,Question,Asterisk,Pipe,BackSlash,Ctl,RightSpace,RightPeriod,InvalidUtf8,Dot)
      --smb-hide-special-share                              Hide special shares (e.g. print$) which users aren&#39;t supposed to access (default true)
      --smb-host string                                     SMB server hostname to connect to
      --smb-idle-timeout Duration                           Max time before closing idle connections (default 1m0s)
      --smb-pass string                                     SMB password (obscured)
      --smb-port int                                        SMB port number (default 445)
      --smb-spn string                                      Service principal name
      --smb-user string                                     SMB username (default &quot;$USER&quot;)
      --storj-access-grant string                           Access grant
      --storj-api-key string                                API key
      --storj-description string                            Description of the remote
      --storj-passphrase string                             Encryption passphrase
      --storj-provider string                               Choose an authentication method (default &quot;existing&quot;)
      --storj-satellite-address string                      Satellite address (default &quot;us1.storj.io&quot;)
      --sugarsync-access-key-id string                      Sugarsync Access Key ID
      --sugarsync-app-id string                             Sugarsync App ID
      --sugarsync-authorization string                      Sugarsync authorization
      --sugarsync-authorization-expiry string               Sugarsync authorization expiry
      --sugarsync-deleted-id string                         Sugarsync deleted folder id
      --sugarsync-description string                        Description of the remote
      --sugarsync-encoding Encoding                         The encoding for the backend (default Slash,Ctl,InvalidUtf8,Dot)
      --sugarsync-hard-delete                               Permanently delete files if true
      --sugarsync-private-access-key string                 Sugarsync Private Access Key
      --sugarsync-refresh-token string                      Sugarsync refresh token
      --sugarsync-root-id string                            Sugarsync root id
      --sugarsync-user string                               Sugarsync user
      --swift-application-credential-id string              Application Credential ID (OS_APPLICATION_CREDENTIAL_ID)
      --swift-application-credential-name string            Application Credential Name (OS_APPLICATION_CREDENTIAL_NAME)
      --swift-application-credential-secret string          Application Credential Secret (OS_APPLICATION_CREDENTIAL_SECRET)
      --swift-auth string                                   Authentication URL for server (OS_AUTH_URL)
      --swift-auth-token string                             Auth Token from alternate authentication - optional (OS_AUTH_TOKEN)
      --swift-auth-version int                              AuthVersion - optional - set to (1,2,3) if your auth URL has no version (ST_AUTH_VERSION)
      --swift-chunk-size SizeSuffix                         Above this size files will be chunked (default 5Gi)
      --swift-description string                            Description of the remote
      --swift-domain string                                 User domain - optional (v3 auth) (OS_USER_DOMAIN_NAME)
      --swift-encoding Encoding                             The encoding for the backend (default Slash,InvalidUtf8)
      --swift-endpoint-type string                          Endpoint type to choose from the service catalogue (OS_ENDPOINT_TYPE) (default &quot;public&quot;)
      --swift-env-auth                                      Get swift credentials from environment variables in standard OpenStack form
      --swift-fetch-until-empty-page                        When paginating, always fetch unless we received an empty page
      --swift-key string                                    API key or password (OS_PASSWORD)
      --swift-leave-parts-on-error                          If true avoid calling abort upload on a failure
      --swift-no-chunk                                      Don&#39;t chunk files during streaming upload
      --swift-no-large-objects                              Disable support for static and dynamic large objects
      --swift-partial-page-fetch-threshold int              When paginating, fetch if the current page is within this percentage of the limit
      --swift-region string                                 Region name - optional (OS_REGION_NAME)
      --swift-storage-policy string                         The storage policy to use when creating a new container
      --swift-storage-url string                            Storage URL - optional (OS_STORAGE_URL)
      --swift-tenant string                                 Tenant name - optional for v1 auth, this or tenant_id required otherwise (OS_TENANT_NAME or OS_PROJECT_NAME)
      --swift-tenant-domain string                          Tenant domain - optional (v3 auth) (OS_PROJECT_DOMAIN_NAME)
      --swift-tenant-id string                              Tenant ID - optional for v1 auth, this or tenant required otherwise (OS_TENANT_ID)
      --swift-use-segments-container Tristate               Choose destination for large object segments (default unset)
      --swift-user string                                   User name to log in (OS_USERNAME)
      --swift-user-id string                                User ID to log in - optional - most swift systems use user and leave this blank (v3 auth) (OS_USER_ID)
      --ulozto-app-token string                             The application token identifying the app. An app API key can be either found in the API
      --ulozto-description string                           Description of the remote
      --ulozto-encoding Encoding                            The encoding for the backend (default Slash,BackSlash,Del,Ctl,InvalidUtf8,Dot)
      --ulozto-list-page-size int                           The size of a single page for list commands. 1-500 (default 500)
      --ulozto-password string                              The password for the user (obscured)
      --ulozto-root-folder-slug string                      If set, rclone will use this folder as the root folder for all operations. For example,
      --ulozto-username string                              The username of the principal to operate as
      --union-action-policy string                          Policy to choose upstream on ACTION category (default &quot;epall&quot;)
      --union-cache-time int                                Cache time of usage and free space (in seconds) (default 120)
      --union-create-policy string                          Policy to choose upstream on CREATE category (default &quot;epmfs&quot;)
      --union-description string                            Description of the remote
      --union-min-free-space SizeSuffix                     Minimum viable free space for lfs/eplfs policies (default 1Gi)
      --union-search-policy string                          Policy to choose upstream on SEARCH category (default &quot;ff&quot;)
      --union-upstreams string                              List of space separated upstreams
      --uptobox-access-token string                         Your access token
      --uptobox-description string                          Description of the remote
      --uptobox-encoding Encoding                           The encoding for the backend (default Slash,LtGt,DoubleQuote,BackQuote,Del,Ctl,LeftSpace,InvalidUtf8,Dot)
      --uptobox-private                                     Set to make uploaded files private
      --webdav-bearer-token string                          Bearer token instead of user/pass (e.g. a Macaroon)
      --webdav-bearer-token-command string                  Command to run to get a bearer token
      --webdav-description string                           Description of the remote
      --webdav-encoding string                              The encoding for the backend
      --webdav-headers CommaSepList                         Set HTTP headers for all transactions
      --webdav-nextcloud-chunk-size SizeSuffix              Nextcloud upload chunk size (default 10Mi)
      --webdav-owncloud-exclude-mounts                      Exclude ownCloud mounted storages
      --webdav-owncloud-exclude-shares                      Exclude ownCloud shares
      --webdav-pacer-min-sleep Duration                     Minimum time to sleep between API calls (default 10ms)
      --webdav-pass string                                  Password (obscured)
      --webdav-unix-socket string                           Path to a unix domain socket to dial to, instead of opening a TCP connection directly
      --webdav-url string                                   URL of http host to connect to
      --webdav-user string                                  User name
      --webdav-vendor string                                Name of the WebDAV site/service/software you are using
      --yandex-auth-url string                              Auth server URL
      --yandex-client-id string                             OAuth Client Id
      --yandex-client-secret string                         OAuth Client Secret
      --yandex-description string                           Description of the remote
      --yandex-encoding Encoding                            The encoding for the backend (default Slash,Del,Ctl,InvalidUtf8,Dot)
      --yandex-hard-delete                                  Delete files permanently rather than putting them into the trash
      --yandex-spoof-ua                                     Set the user agent to match an official version of the yandex disk client. May help with upload performance (default true)
      --yandex-token string                                 OAuth Access Token as a JSON blob
      --yandex-token-url string                             Token server url
      --zoho-auth-url string                                Auth server URL
      --zoho-client-id string                               OAuth Client Id
      --zoho-client-secret string                           OAuth Client Secret
      --zoho-description string                             Description of the remote
      --zoho-encoding Encoding                              The encoding for the backend (default Del,Ctl,InvalidUtf8)
      --zoho-region string                                  Zoho region to connect to
      --zoho-token string                                   OAuth Access Token as a JSON blob
      --zoho-token-url string                               Token server url</code></pre>
<h1 id="docker-volume-plugin">Docker Volume Plugin</h1>
<h2 id="introduction">Introduction</h2>
<p>Docker 1.9 has added support for creating <a href="https://docs.docker.com/storage/volumes/">named volumes</a> via <a href="https://docs.docker.com/engine/reference/commandline/volume_create/">command-line interface</a> and mounting them in containers as a way to share data between them. Since Docker 1.10 you can create named volumes with <a href="https://docs.docker.com/compose/">Docker Compose</a> by descriptions in <a href="https://docs.docker.com/compose/compose-file/compose-file-v2/#volume-configuration-reference">docker-compose.yml</a> files for use by container groups on a single host. As of Docker 1.12 volumes are supported by <a href="https://docs.docker.com/engine/swarm/key-concepts/">Docker Swarm</a> included with Docker Engine and created from descriptions in <a href="https://docs.docker.com/compose/compose-file/compose-file-v3/#volume-configuration-reference">swarm compose v3</a> files for use with <em>swarm stacks</em> across multiple cluster nodes.</p>
<p><a href="https://docs.docker.com/engine/extend/plugins_volume/">Docker Volume Plugins</a> augment the default <code>local</code> volume driver included in Docker with stateful volumes shared across containers and hosts. Unlike local volumes, your data will <em>not</em> be deleted when such volume is removed. Plugins can run managed by the docker daemon, as a native system service (under systemd, <em>sysv</em> or <em>upstart</em>) or as a standalone executable. Rclone can run as docker volume plugin in all these modes. It interacts with the local docker daemon via <a href="https://docs.docker.com/engine/extend/plugin_api/">plugin API</a> and handles mounting of remote file systems into docker containers so it must run on the same host as the docker daemon or on every Swarm node.</p>
<h2 id="getting-started">Getting started</h2>
<p>In the first example we will use the <a href="https://rclone.org/sftp/">SFTP</a> rclone volume with Docker engine on a standalone Ubuntu machine.</p>
<p>Start from <a href="https://docs.docker.com/engine/install/">installing Docker</a> on the host.</p>
<p>The <em>FUSE</em> driver is a prerequisite for rclone mounting and should be installed on host:</p>
<pre><code>sudo apt-get -y install fuse</code></pre>
<p>Create two directories required by rclone docker plugin:</p>
<pre><code>sudo mkdir -p /var/lib/docker-plugins/rclone/config
sudo mkdir -p /var/lib/docker-plugins/rclone/cache</code></pre>
<p>Install the managed rclone docker plugin for your architecture (here <code>amd64</code>):</p>
<pre><code>docker plugin install rclone/docker-volume-rclone:amd64 args=&quot;-v&quot; --alias rclone --grant-all-permissions
docker plugin list</code></pre>
<p>Create your <a href="https://rclone.org/sftp/#standard-options">SFTP volume</a>:</p>
<pre><code>docker volume create firstvolume -d rclone -o type=sftp -o sftp-host=_hostname_ -o sftp-user=_username_ -o sftp-pass=_password_ -o allow-other=true</code></pre>
<p>Note that since all options are static, you don't even have to run <code>rclone config</code> or create the <code>rclone.conf</code> file (but the <code>config</code> directory should still be present). In the simplest case you can use <code>localhost</code> as <em>hostname</em> and your SSH credentials as <em>username</em> and <em>password</em>. You can also change the remote path to your home directory on the host, for example <code>-o path=/home/username</code>.</p>
<p>Time to create a test container and mount the volume into it:</p>
<pre><code>docker run --rm -it -v firstvolume:/mnt --workdir /mnt ubuntu:latest bash</code></pre>
<p>If all goes well, you will enter the new container and change right to the mounted SFTP remote. You can type <code>ls</code> to list the mounted directory or otherwise play with it. Type <code>exit</code> when you are done. The container will stop but the volume will stay, ready to be reused. When it's not needed anymore, remove it:</p>
<pre><code>docker volume list
docker volume remove firstvolume</code></pre>
<p>Now let us try <strong>something more elaborate</strong>: <a href="https://rclone.org/drive/">Google Drive</a> volume on multi-node Docker Swarm.</p>
<p>You should start from installing Docker and FUSE, creating plugin directories and installing rclone plugin on <em>every</em> swarm node. Then <a href="https://docs.docker.com/engine/swarm/swarm-mode/">setup the Swarm</a>.</p>
<p>Google Drive volumes need an access token which can be setup via web browser and will be periodically renewed by rclone. The managed plugin cannot run a browser so we will use a technique similar to the <a href="https://rclone.org/remote_setup/">rclone setup on a headless box</a>.</p>
<p>Run <a href="https://rclone.org/commands/rclone_config_create/">rclone config</a> on <em>another</em> machine equipped with <em>web browser</em> and graphical user interface. Create the <a href="https://rclone.org/drive/#standard-options">Google Drive remote</a>. When done, transfer the resulting <code>rclone.conf</code> to the Swarm cluster and save as <code>/var/lib/docker-plugins/rclone/config/rclone.conf</code> on <em>every</em> node. By default this location is accessible only to the root user so you will need appropriate privileges. The resulting config will look like this:</p>
<pre><code>[gdrive]
type = drive
scope = drive
drive_id = 1234567...
root_folder_id = 0Abcd...
token = {&quot;access_token&quot;:...}</code></pre>
<p>Now create the file named <code>example.yml</code> with a swarm stack description like this:</p>
<pre><code>version: &#39;3&#39;
services:
  heimdall:
    image: linuxserver/heimdall:latest
    ports: [8080:80]
    volumes: [configdata:/config]
volumes:
  configdata:
    driver: rclone
    driver_opts:
      remote: &#39;gdrive:heimdall&#39;
      allow_other: &#39;true&#39;
      vfs_cache_mode: full
      poll_interval: 0</code></pre>
<p>and run the stack:</p>
<pre><code>docker stack deploy example -c ./example.yml</code></pre>
<p>After a few seconds docker will spread the parsed stack description over cluster, create the <code>example_heimdall</code> service on port <em>8080</em>, run service containers on one or more cluster nodes and request the <code>example_configdata</code> volume from rclone plugins on the node hosts. You can use the following commands to confirm results:</p>
<pre><code>docker service ls
docker service ps example_heimdall
docker volume ls</code></pre>
<p>Point your browser to <code>http://cluster.host.address:8080</code> and play with the service. Stop it with <code>docker stack remove example</code> when you are done. Note that the <code>example_configdata</code> volume(s) created on demand at the cluster nodes will not be automatically removed together with the stack but stay for future reuse. You can remove them manually by invoking the <code>docker volume remove example_configdata</code> command on every node.</p>
<h2 id="creating-volumes-via-cli">Creating Volumes via CLI</h2>
<p>Volumes can be created with <a href="https://docs.docker.com/engine/reference/commandline/volume_create/">docker volume create</a>. Here are a few examples:</p>
<pre><code>docker volume create vol1 -d rclone -o remote=storj: -o vfs-cache-mode=full
docker volume create vol2 -d rclone -o remote=:storj,access_grant=xxx:heimdall
docker volume create vol3 -d rclone -o type=storj -o path=heimdall -o storj-access-grant=xxx -o poll-interval=0</code></pre>
<p>Note the <code>-d rclone</code> flag that tells docker to request volume from the rclone driver. This works even if you installed managed driver by its full name <code>rclone/docker-volume-rclone</code> because you provided the <code>--alias rclone</code> option.</p>
<p>Volumes can be inspected as follows:</p>
<pre><code>docker volume list
docker volume inspect vol1</code></pre>
<h2 id="volume-configuration">Volume Configuration</h2>
<p>Rclone flags and volume options are set via the <code>-o</code> flag to the <code>docker volume create</code> command. They include backend-specific parameters as well as mount and <em>VFS</em> options. Also there are a few special <code>-o</code> options: <code>remote</code>, <code>fs</code>, <code>type</code>, <code>path</code>, <code>mount-type</code> and <code>persist</code>.</p>
<p><code>remote</code> determines an existing remote name from the config file, with trailing colon and optionally with a remote path. See the full syntax in the <a href="https://rclone.org/docs/#syntax-of-remote-paths">rclone documentation</a>. This option can be aliased as <code>fs</code> to prevent confusion with the <em>remote</em> parameter of such backends as <em>crypt</em> or <em>alias</em>.</p>
<p>The <code>remote=:backend:dir/subdir</code> syntax can be used to create <a href="https://rclone.org/docs/#backend-path-to-dir">on-the-fly (config-less) remotes</a>, while the <code>type</code> and <code>path</code> options provide a simpler alternative for this. Using two split options</p>
<pre><code>-o type=backend -o path=dir/subdir</code></pre>
<p>is equivalent to the combined syntax</p>
<pre><code>-o remote=:backend:dir/subdir</code></pre>
<p>but is arguably easier to parameterize in scripts. The <code>path</code> part is optional.</p>
<p><a href="https://rclone.org/commands/rclone_serve_docker/#options">Mount and VFS options</a> as well as <a href="https://rclone.org/flags/#backend-flags">backend parameters</a> are named like their twin command-line flags without the <code>--</code> CLI prefix. Optionally you can use underscores instead of dashes in option names. For example, <code>--vfs-cache-mode full</code> becomes <code>-o vfs-cache-mode=full</code> or <code>-o vfs_cache_mode=full</code>. Boolean CLI flags without value will gain the <code>true</code> value, e.g. <code>--allow-other</code> becomes <code>-o allow-other=true</code> or <code>-o allow_other=true</code>.</p>
<p>Please note that you can provide parameters only for the backend immediately referenced by the backend type of mounted <code>remote</code>. If this is a wrapping backend like <em>alias, chunker or crypt</em>, you cannot provide options for the referred to remote or backend. This limitation is imposed by the rclone connection string parser. The only workaround is to feed plugin with <code>rclone.conf</code> or configure plugin arguments (see below).</p>
<h2 id="special-volume-options">Special Volume Options</h2>
<p><code>mount-type</code> determines the mount method and in general can be one of: <code>mount</code>, <code>cmount</code>, or <code>mount2</code>. This can be aliased as <code>mount_type</code>. It should be noted that the managed rclone docker plugin currently does not support the <code>cmount</code> method and <code>mount2</code> is rarely needed. This option defaults to the first found method, which is usually <code>mount</code> so you generally won't need it.</p>
<p><code>persist</code> is a reserved boolean (true/false) option. In future it will allow to persist on-the-fly remotes in the plugin <code>rclone.conf</code> file.</p>
<h2 id="connection-strings-1">Connection Strings</h2>
<p>The <code>remote</code> value can be extended with <a href="https://rclone.org/docs/#connection-strings">connection strings</a> as an alternative way to supply backend parameters. This is equivalent to the <code>-o</code> backend options with one <em>syntactic difference</em>. Inside connection string the backend prefix must be dropped from parameter names but in the <code>-o param=value</code> array it must be present. For instance, compare the following option array</p>
<pre><code>-o remote=:sftp:/home -o sftp-host=localhost</code></pre>
<p>with equivalent connection string:</p>
<pre><code>-o remote=:sftp,host=localhost:/home</code></pre>
<p>This difference exists because flag options <code>-o key=val</code> include not only backend parameters but also mount/VFS flags and possibly other settings. Also it allows to discriminate the <code>remote</code> option from the <code>crypt-remote</code> (or similarly named backend parameters) and arguably simplifies scripting due to clearer value substitution.</p>
<h2 id="using-with-swarm-or-compose">Using with Swarm or Compose</h2>
<p>Both <em>Docker Swarm</em> and <em>Docker Compose</em> use <a href="http://yaml.org/spec/1.2/spec.html">YAML</a>-formatted text files to describe groups (stacks) of containers, their properties, networks and volumes. <em>Compose</em> uses the <a href="https://docs.docker.com/compose/compose-file/compose-file-v2/#volume-configuration-reference">compose v2</a> format, <em>Swarm</em> uses the <a href="https://docs.docker.com/compose/compose-file/compose-file-v3/#volume-configuration-reference">compose v3</a> format. They are mostly similar, differences are explained in the <a href="https://docs.docker.com/compose/compose-file/compose-versioning/#upgrading">docker documentation</a>.</p>
<p>Volumes are described by the children of the top-level <code>volumes:</code> node. Each of them should be named after its volume and have at least two elements, the self-explanatory <code>driver: rclone</code> value and the <code>driver_opts:</code> structure playing the same role as <code>-o key=val</code> CLI flags:</p>
<pre><code>volumes:
  volume_name_1:
    driver: rclone
    driver_opts:
      remote: &#39;gdrive:&#39;
      allow_other: &#39;true&#39;
      vfs_cache_mode: full
      token: &#39;{&quot;type&quot;: &quot;borrower&quot;, &quot;expires&quot;: &quot;2021-12-31&quot;}&#39;
      poll_interval: 0</code></pre>
<p>Notice a few important details: - YAML prefers <code>_</code> in option names instead of <code>-</code>. - YAML treats single and double quotes interchangeably. Simple strings and integers can be left unquoted. - Boolean values must be quoted like <code>'true'</code> or <code>"false"</code> because these two words are reserved by YAML. - The filesystem string is keyed with <code>remote</code> (or with <code>fs</code>). Normally you can omit quotes here, but if the string ends with colon, you <strong>must</strong> quote it like <code>remote: "storage_box:"</code>. - YAML is picky about surrounding braces in values as this is in fact another <a href="http://yaml.org/spec/1.2/spec.html#id2790832">syntax for key/value mappings</a>. For example, JSON access tokens usually contain double quotes and surrounding braces, so you must put them in single quotes.</p>
<h2 id="installing-as-managed-plugin">Installing as Managed Plugin</h2>
<p>Docker daemon can install plugins from an image registry and run them managed. We maintain the <a href="https://hub.docker.com/p/rclone/docker-volume-rclone/">docker-volume-rclone</a> plugin image on <a href="https://hub.docker.com">Docker Hub</a>.</p>
<p>Rclone volume plugin requires <strong>Docker Engine &gt;= 19.03.15</strong></p>
<p>The plugin requires presence of two directories on the host before it can be installed. Note that plugin will <strong>not</strong> create them automatically. By default they must exist on host at the following locations (though you can tweak the paths): - <code>/var/lib/docker-plugins/rclone/config</code> is reserved for the <code>rclone.conf</code> config file and <strong>must</strong> exist even if it's empty and the config file is not present. - <code>/var/lib/docker-plugins/rclone/cache</code> holds the plugin state file as well as optional VFS caches.</p>
<p>You can <a href="https://docs.docker.com/engine/reference/commandline/plugin_install/">install managed plugin</a> with default settings as follows:</p>
<pre><code>docker plugin install rclone/docker-volume-rclone:amd64 --grant-all-permissions --alias rclone</code></pre>
<p>The <code>:amd64</code> part of the image specification after colon is called a <em>tag</em>. Usually you will want to install the latest plugin for your architecture. In this case the tag will just name it, like <code>amd64</code> above. The following plugin architectures are currently available: - <code>amd64</code> - <code>arm64</code> - <code>arm-v7</code></p>
<p>Sometimes you might want a concrete plugin version, not the latest one. Then you should use image tag in the form <code>:ARCHITECTURE-VERSION</code>. For example, to install plugin version <code>v1.56.2</code> on architecture <code>arm64</code> you will use tag <code>arm64-1.56.2</code> (note the removed <code>v</code>) so the full image specification becomes <code>rclone/docker-volume-rclone:arm64-1.56.2</code>.</p>
<p>We also provide the <code>latest</code> plugin tag, but since docker does not support multi-architecture plugins as of the time of this writing, this tag is currently an <strong>alias for <code>amd64</code></strong>. By convention the <code>latest</code> tag is the default one and can be omitted, thus both <code>rclone/docker-volume-rclone:latest</code> and just <code>rclone/docker-volume-rclone</code> will refer to the latest plugin release for the <code>amd64</code> platform.</p>
<p>Also the <code>amd64</code> part can be omitted from the versioned rclone plugin tags. For example, rclone image reference <code>rclone/docker-volume-rclone:amd64-1.56.2</code> can be abbreviated as <code>rclone/docker-volume-rclone:1.56.2</code> for convenience. However, for non-intel architectures you still have to use the full tag as <code>amd64</code> or <code>latest</code> will fail to start.</p>
<p>Managed plugin is in fact a special container running in a namespace separate from normal docker containers. Inside it runs the <code>rclone serve docker</code> command. The config and cache directories are bind-mounted into the container at start. The docker daemon connects to a unix socket created by the command inside the container. The command creates on-demand remote mounts right inside, then docker machinery propagates them through kernel mount namespaces and bind-mounts into requesting user containers.</p>
<p>You can tweak a few plugin settings after installation when it's disabled (not in use), for instance:</p>
<pre><code>docker plugin disable rclone
docker plugin set rclone RCLONE_VERBOSE=2 config=/etc/rclone args=&quot;--vfs-cache-mode=writes --allow-other&quot;
docker plugin enable rclone
docker plugin inspect rclone</code></pre>
<p>Note that if docker refuses to disable the plugin, you should find and remove all active volumes connected with it as well as containers and swarm services that use them. This is rather tedious so please carefully plan in advance.</p>
<p>You can tweak the following settings: <code>args</code>, <code>config</code>, <code>cache</code>, <code>HTTP_PROXY</code>, <code>HTTPS_PROXY</code>, <code>NO_PROXY</code> and <code>RCLONE_VERBOSE</code>. It's <em>your</em> task to keep plugin settings in sync across swarm cluster nodes.</p>
<p><code>args</code> sets command-line arguments for the <code>rclone serve docker</code> command (<em>none</em> by default). Arguments should be separated by space so you will normally want to put them in quotes on the <a href="https://docs.docker.com/engine/reference/commandline/plugin_set/">docker plugin set</a> command line. Both <a href="https://rclone.org/commands/rclone_serve_docker/#options">serve docker flags</a> and <a href="https://rclone.org/flags/">generic rclone flags</a> are supported, including backend parameters that will be used as defaults for volume creation. Note that plugin will fail (due to <a href="https://github.com/moby/moby/blob/v20.10.7/plugin/v2/plugin.go#L195">this docker bug</a>) if the <code>args</code> value is empty. Use e.g. <code>args="-v"</code> as a workaround.</p>
<p><code>config=/host/dir</code> sets alternative host location for the config directory. Plugin will look for <code>rclone.conf</code> here. It's not an error if the config file is not present but the directory must exist. Please note that plugin can periodically rewrite the config file, for example when it renews storage access tokens. Keep this in mind and try to avoid races between the plugin and other instances of rclone on the host that might try to change the config simultaneously resulting in corrupted <code>rclone.conf</code>. You can also put stuff like private key files for SFTP remotes in this directory. Just note that it's bind-mounted inside the plugin container at the predefined path <code>/data/config</code>. For example, if your key file is named <code>sftp-box1.key</code> on the host, the corresponding volume config option should read <code>-o sftp-key-file=/data/config/sftp-box1.key</code>.</p>
<p><code>cache=/host/dir</code> sets alternative host location for the <em>cache</em> directory. The plugin will keep VFS caches here. Also it will create and maintain the <code>docker-plugin.state</code> file in this directory. When the plugin is restarted or reinstalled, it will look in this file to recreate any volumes that existed previously. However, they will not be re-mounted into consuming containers after restart. Usually this is not a problem as the docker daemon normally will restart affected user containers after failures, daemon restarts or host reboots.</p>
<p><code>RCLONE_VERBOSE</code> sets plugin verbosity from <code>0</code> (errors only, by default) to <code>2</code> (debugging). Verbosity can be also tweaked via <code>args="-v [-v] ..."</code>. Since arguments are more generic, you will rarely need this setting. The plugin output by default feeds the docker daemon log on local host. Log entries are reflected as <em>errors</em> in the docker log but retain their actual level assigned by rclone in the encapsulated message string.</p>
<p><code>HTTP_PROXY</code>, <code>HTTPS_PROXY</code>, <code>NO_PROXY</code> customize the plugin proxy settings.</p>
<p>You can set custom plugin options right when you install it, <em>in one go</em>:</p>
<pre><code>docker plugin remove rclone
docker plugin install rclone/docker-volume-rclone:amd64 \
       --alias rclone --grant-all-permissions \
       args=&quot;-v --allow-other&quot; config=/etc/rclone
docker plugin inspect rclone</code></pre>
<h2 id="healthchecks">Healthchecks</h2>
<p>The docker plugin volume protocol doesn't provide a way for plugins to inform the docker daemon that a volume is (un-)available. As a workaround you can setup a healthcheck to verify that the mount is responding, for example:</p>
<pre><code>services:
  my_service:
    image: my_image
    healthcheck:
      test: ls /path/to/rclone/mount || exit 1
      interval: 1m
      timeout: 15s
      retries: 3
      start_period: 15s</code></pre>
<h2 id="running-plugin-under-systemd">Running Plugin under Systemd</h2>
<p>In most cases you should prefer managed mode. Moreover, MacOS and Windows do not support native Docker plugins. Please use managed mode on these systems. Proceed further only if you are on Linux.</p>
<p>First, <a href="https://rclone.org/install/">install rclone</a>. You can just run it (type <code>rclone serve docker</code> and hit enter) for the test.</p>
<p>Install <em>FUSE</em>:</p>
<pre><code>sudo apt-get -y install fuse</code></pre>
<p>Download two systemd configuration files: <a href="https://raw.githubusercontent.com/rclone/rclone/master/contrib/docker-plugin/systemd/docker-volume-rclone.service">docker-volume-rclone.service</a> and <a href="https://raw.githubusercontent.com/rclone/rclone/master/contrib/docker-plugin/systemd/docker-volume-rclone.socket">docker-volume-rclone.socket</a>.</p>
<p>Put them to the <code>/etc/systemd/system/</code> directory:</p>
<pre><code>cp docker-volume-plugin.service /etc/systemd/system/
cp docker-volume-plugin.socket  /etc/systemd/system/</code></pre>
<p>Please note that all commands in this section must be run as <em>root</em> but we omit <code>sudo</code> prefix for brevity. Now create directories required by the service:</p>
<pre><code>mkdir -p /var/lib/docker-volumes/rclone
mkdir -p /var/lib/docker-plugins/rclone/config
mkdir -p /var/lib/docker-plugins/rclone/cache</code></pre>
<p>Run the docker plugin service in the socket activated mode:</p>
<pre><code>systemctl daemon-reload
systemctl start docker-volume-rclone.service
systemctl enable docker-volume-rclone.socket
systemctl start docker-volume-rclone.socket
systemctl restart docker</code></pre>
<p>Or run the service directly: - run <code>systemctl daemon-reload</code> to let systemd pick up new config - run <code>systemctl enable docker-volume-rclone.service</code> to make the new service start automatically when you power on your machine. - run <code>systemctl start docker-volume-rclone.service</code> to start the service now. - run <code>systemctl restart docker</code> to restart docker daemon and let it detect the new plugin socket. Note that this step is not needed in managed mode where docker knows about plugin state changes.</p>
<p>The two methods are equivalent from the user perspective, but I personally prefer socket activation.</p>
<h2 id="troubleshooting">Troubleshooting</h2>
<p>You can <a href="https://docs.docker.com/engine/extend/#debugging-plugins">see managed plugin settings</a> with</p>
<pre><code>docker plugin list
docker plugin inspect rclone</code></pre>
<p>Note that docker (including latest 20.10.7) will not show actual values of <code>args</code>, just the defaults.</p>
<p>Use <code>journalctl --unit docker</code> to see managed plugin output as part of the docker daemon log. Note that docker reflects plugin lines as <em>errors</em> but their actual level can be seen from encapsulated message string.</p>
<p>You will usually install the latest version of managed plugin for your platform. Use the following commands to print the actual installed version:</p>
<pre><code>PLUGID=$(docker plugin list --no-trunc | awk &#39;/rclone/{print$1}&#39;)
sudo runc --root /run/docker/runtime-runc/plugins.moby exec $PLUGID rclone version</code></pre>
<p>You can even use <code>runc</code> to run shell inside the plugin container:</p>
<pre><code>sudo runc --root /run/docker/runtime-runc/plugins.moby exec --tty $PLUGID bash</code></pre>
<p>Also you can use curl to check the plugin socket connectivity:</p>
<pre><code>docker plugin list --no-trunc
PLUGID=123abc...
sudo curl -H Content-Type:application/json -XPOST -d {} --unix-socket /run/docker/plugins/$PLUGID/rclone.sock http://localhost/Plugin.Activate</code></pre>
<p>though this is rarely needed.</p>
<h2 id="caveats">Caveats</h2>
<p>Finally I'd like to mention a <em>caveat with updating volume settings</em>. Docker CLI does not have a dedicated command like <code>docker volume update</code>. It may be tempting to invoke <code>docker volume create</code> with updated options on existing volume, but there is a gotcha. The command will do nothing, it won't even return an error. I hope that docker maintainers will fix this some day. In the meantime be aware that you must remove your volume before recreating it with new settings:</p>
<pre><code>docker volume remove my_vol
docker volume create my_vol -d rclone -o opt1=new_val1 ...</code></pre>
<p>and verify that settings did update:</p>
<pre><code>docker volume list
docker volume inspect my_vol</code></pre>
<p>If docker refuses to remove the volume, you should find containers or swarm services that use it and stop them first.</p>
<h2 id="bisync">Bisync</h2>
<p><code>bisync</code> is <strong>in beta</strong> and is considered an <strong>advanced command</strong>, so use with care. Make sure you have read and understood the entire <a href="https://rclone.org/bisync">manual</a> (especially the <a href="#limitations">Limitations</a> section) before using, or data loss can result. Questions can be asked in the <a href="https://forum.rclone.org/">Rclone Forum</a>.</p>
<h2 id="getting-started">Getting started</h2>
<ul>
<li><a href="https://rclone.org/install/">Install rclone</a> and setup your remotes.</li>
<li>Bisync will create its working directory at <code>~/.cache/rclone/bisync</code> on Linux, <code>/Users/yourusername/Library/Caches/rclone/bisync</code> on Mac, or <code>C:\Users\MyLogin\AppData\Local\rclone\bisync</code> on Windows. Make sure that this location is writable.</li>
<li>Run bisync with the <code>--resync</code> flag, specifying the paths to the local and remote sync directory roots.</li>
<li>For successive sync runs, leave off the <code>--resync</code> flag. (<strong>Important!</strong>)</li>
<li>Consider using a <a href="#filtering">filters file</a> for excluding unnecessary files and directories from the sync.</li>
<li>Consider setting up the <a href="#check-access">--check-access</a> feature for safety.</li>
<li>On Linux or Mac, consider setting up a <a href="#cron">crontab entry</a>. bisync can safely run in concurrent cron jobs thanks to lock files it maintains.</li>
</ul>
<p>For example, your first command might look like this:</p>
<pre><code>rclone bisync remote1:path1 remote2:path2 --create-empty-src-dirs --compare size,modtime,checksum --slow-hash-sync-only --resilient -MvP --drive-skip-gdocs --fix-case --resync --dry-run</code></pre>
<p>If all looks good, run it again without <code>--dry-run</code>. After that, remove <code>--resync</code> as well.</p>
<p>Here is a typical run log (with timestamps removed for clarity):</p>
<pre><code>rclone bisync /testdir/path1/ /testdir/path2/ --verbose
INFO  : Synching Path1 &quot;/testdir/path1/&quot; with Path2 &quot;/testdir/path2/&quot;
INFO  : Path1 checking for diffs
INFO  : - Path1    File is new                         - file11.txt
INFO  : - Path1    File is newer                       - file2.txt
INFO  : - Path1    File is newer                       - file5.txt
INFO  : - Path1    File is newer                       - file7.txt
INFO  : - Path1    File was deleted                    - file4.txt
INFO  : - Path1    File was deleted                    - file6.txt
INFO  : - Path1    File was deleted                    - file8.txt
INFO  : Path1:    7 changes:    1 new,    3 newer,    0 older,    3 deleted
INFO  : Path2 checking for diffs
INFO  : - Path2    File is new                         - file10.txt
INFO  : - Path2    File is newer                       - file1.txt
INFO  : - Path2    File is newer                       - file5.txt
INFO  : - Path2    File is newer                       - file6.txt
INFO  : - Path2    File was deleted                    - file3.txt
INFO  : - Path2    File was deleted                    - file7.txt
INFO  : - Path2    File was deleted                    - file8.txt
INFO  : Path2:    7 changes:    1 new,    3 newer,    0 older,    3 deleted
INFO  : Applying changes
INFO  : - Path1    Queue copy to Path2                 - /testdir/path2/file11.txt
INFO  : - Path1    Queue copy to Path2                 - /testdir/path2/file2.txt
INFO  : - Path2    Queue delete                        - /testdir/path2/file4.txt
NOTICE: - WARNING  New or changed in both paths        - file5.txt
NOTICE: - Path1    Renaming Path1 copy                 - /testdir/path1/file5.txt..path1
NOTICE: - Path1    Queue copy to Path2                 - /testdir/path2/file5.txt..path1
NOTICE: - Path2    Renaming Path2 copy                 - /testdir/path2/file5.txt..path2
NOTICE: - Path2    Queue copy to Path1                 - /testdir/path1/file5.txt..path2
INFO  : - Path2    Queue copy to Path1                 - /testdir/path1/file6.txt
INFO  : - Path1    Queue copy to Path2                 - /testdir/path2/file7.txt
INFO  : - Path2    Queue copy to Path1                 - /testdir/path1/file1.txt
INFO  : - Path2    Queue copy to Path1                 - /testdir/path1/file10.txt
INFO  : - Path1    Queue delete                        - /testdir/path1/file3.txt
INFO  : - Path2    Do queued copies to                 - Path1
INFO  : - Path1    Do queued copies to                 - Path2
INFO  : -          Do queued deletes on                - Path1
INFO  : -          Do queued deletes on                - Path2
INFO  : Updating listings
INFO  : Validating listings for Path1 &quot;/testdir/path1/&quot; vs Path2 &quot;/testdir/path2/&quot;
INFO  : Bisync successful</code></pre>
<h2 id="command-line-syntax">Command line syntax</h2>
<pre><code>$ rclone bisync --help
Usage:
  rclone bisync remote1:path1 remote2:path2 [flags]

Positional arguments:
  Path1, Path2  Local path, or remote storage with &#39;:&#39; plus optional path.
                Type &#39;rclone listremotes&#39; for list of configured remotes.

Optional Flags:
      --backup-dir1 string                   --backup-dir for Path1. Must be a non-overlapping path on the same remote.
      --backup-dir2 string                   --backup-dir for Path2. Must be a non-overlapping path on the same remote.
      --check-access                         Ensure expected RCLONE_TEST files are found on both Path1 and Path2 filesystems, else abort.
      --check-filename string                Filename for --check-access (default: RCLONE_TEST)
      --check-sync string                    Controls comparison of final listings: true|false|only (default: true) (default &quot;true&quot;)
      --compare string                       Comma-separated list of bisync-specific compare options ex. &#39;size,modtime,checksum&#39; (default: &#39;size,modtime&#39;)
      --conflict-loser ConflictLoserAction   Action to take on the loser of a sync conflict (when there is a winner) or on both files (when there is no winner): , num, pathname, delete (default: num)
      --conflict-resolve string              Automatically resolve conflicts by preferring the version that is: none, path1, path2, newer, older, larger, smaller (default: none) (default &quot;none&quot;)
      --conflict-suffix string               Suffix to use when renaming a --conflict-loser. Can be either one string or two comma-separated strings to assign different suffixes to Path1/Path2. (default: &#39;conflict&#39;)
      --create-empty-src-dirs                Sync creation and deletion of empty directories. (Not compatible with --remove-empty-dirs)
      --download-hash                        Compute hash by downloading when otherwise unavailable. (warning: may be slow and use lots of data!)
      --filters-file string                  Read filtering patterns from a file
      --force                                Bypass --max-delete safety check and run the sync. Consider using with --verbose
  -h, --help                                 help for bisync
      --ignore-listing-checksum              Do not use checksums for listings (add --ignore-checksum to additionally skip post-copy checksum checks)
      --max-lock Duration                    Consider lock files older than this to be expired (default: 0 (never expire)) (minimum: 2m) (default 0s)
      --no-cleanup                           Retain working files (useful for troubleshooting and testing).
      --no-slow-hash                         Ignore listing checksums only on backends where they are slow
      --recover                              Automatically recover from interruptions without requiring --resync.
      --remove-empty-dirs                    Remove ALL empty directories at the final cleanup step.
      --resilient                            Allow future runs to retry after certain less-serious errors, instead of requiring --resync. Use at your own risk!
  -1, --resync                               Performs the resync run. Equivalent to --resync-mode path1. Consider using --verbose or --dry-run first.
      --resync-mode string                   During resync, prefer the version that is: path1, path2, newer, older, larger, smaller (default: path1 if --resync, otherwise none for no resync.) (default &quot;none&quot;)
      --retries int                          Retry operations this many times if they fail (requires --resilient). (default 3)
      --retries-sleep Duration               Interval between retrying operations if they fail, e.g. 500ms, 60s, 5m (0 to disable) (default 0s)
      --slow-hash-sync-only                  Ignore slow checksums for listings and deltas, but still consider them during sync calls.
      --workdir string                       Use custom working dir - useful for testing. (default: {WORKDIR})
      --max-delete PERCENT                   Safety check on maximum percentage of deleted files allowed. If exceeded, the bisync run will abort. (default: 50%)
  -n, --dry-run                              Go through the motions - No files are copied/deleted.
  -v, --verbose                              Increases logging verbosity. May be specified more than once for more details.</code></pre>
<p>Arbitrary rclone flags may be specified on the <a href="https://rclone.org/commands/rclone_bisync/">bisync command line</a>, for example <code>rclone bisync ./testdir/path1/ gdrive:testdir/path2/ --drive-skip-gdocs -v -v --timeout 10s</code> Note that interactions of various rclone flags with bisync process flow has not been fully tested yet.</p>
<h3 id="paths">Paths</h3>
<p>Path1 and Path2 arguments may be references to any mix of local directory paths (absolute or relative), UNC paths (<code>//server/share/path</code>), Windows drive paths (with a drive letter and <code>:</code>) or configured <a href="https://rclone.org/docs/#syntax-of-remote-paths">remotes</a> with optional subdirectory paths. Cloud references are distinguished by having a <code>:</code> in the argument (see <a href="#windows">Windows support</a> below).</p>
<p>Path1 and Path2 are treated equally, in that neither has priority for file changes (except during <a href="#resync"><code>--resync</code></a>), and access efficiency does not change whether a remote is on Path1 or Path2.</p>
<p>The listings in bisync working directory (default: <code>~/.cache/rclone/bisync</code>) are named based on the Path1 and Path2 arguments so that separate syncs to individual directories within the tree may be set up, e.g.: <code>path_to_local_tree..dropbox_subdir.lst</code>.</p>
<p>Any empty directories after the sync on both the Path1 and Path2 filesystems are not deleted by default, unless <code>--create-empty-src-dirs</code> is specified. If the <code>--remove-empty-dirs</code> flag is specified, then both paths will have ALL empty directories purged as the last step in the process.</p>
<h2 id="command-line-flags">Command-line flags</h2>
<h3 id="resync">--resync</h3>
<p>This will effectively make both Path1 and Path2 filesystems contain a matching superset of all files. By default, Path2 files that do not exist in Path1 will be copied to Path1, and the process will then copy the Path1 tree to Path2.</p>
<p>The <code>--resync</code> sequence is roughly equivalent to the following (but see <a href="#resync-mode"><code>--resync-mode</code></a> for other options):</p>
<pre><code>rclone copy Path2 Path1 --ignore-existing [--create-empty-src-dirs]
rclone copy Path1 Path2 [--create-empty-src-dirs]</code></pre>
<p>The base directories on both Path1 and Path2 filesystems must exist or bisync will fail. This is required for safety - that bisync can verify that both paths are valid.</p>
<p>When using <code>--resync</code>, a newer version of a file on the Path2 filesystem will (by default) be overwritten by the Path1 filesystem version. (Note that this is <a href="https://github.com/rclone/rclone/issues/5681#issuecomment-938761815">NOT entirely symmetrical</a>, and more symmetrical options can be specified with the <a href="#resync-mode"><code>--resync-mode</code></a> flag.) Carefully evaluate deltas using <a href="https://rclone.org/flags/#non-backend-flags">--dry-run</a>.</p>
<p>For a resync run, one of the paths may be empty (no files in the path tree). The resync run should result in files on both paths, else a normal non-resync run will fail.</p>
<p>For a non-resync run, either path being empty (no files in the tree) fails with <code>Empty current PathN listing. Cannot sync to an empty directory: X.pathN.lst</code> This is a safety check that an unexpected empty path does not result in deleting <strong>everything</strong> in the other path.</p>
<p>Note that <code>--resync</code> implies <code>--resync-mode path1</code> unless a different <a href="#resync-mode"><code>--resync-mode</code></a> is explicitly specified. It is not necessary to use both the <code>--resync</code> and <code>--resync-mode</code> flags -- either one is sufficient without the other.</p>
<p><strong>Note:</strong> <code>--resync</code> (including <code>--resync-mode</code>) should only be used under three specific (rare) circumstances: 1. It is your <em>first</em> bisync run (between these two paths) 2. You've just made changes to your bisync settings (such as editing the contents of your <code>--filters-file</code>) 3. There was an error on the prior run, and as a result, bisync now requires <code>--resync</code> to recover</p>
<p>The rest of the time, you should <em>omit</em> <code>--resync</code>. The reason is because <code>--resync</code> will only <em>copy</em> (not <em>sync</em>) each side to the other. Therefore, if you included <code>--resync</code> for every bisync run, it would never be possible to delete a file -- the deleted file would always keep reappearing at the end of every run (because it's being copied from the other side where it still exists). Similarly, renaming a file would always result in a duplicate copy (both old and new name) on both sides.</p>
<p>If you find that frequent interruptions from #3 are an issue, rather than automatically running <code>--resync</code>, the recommended alternative is to use the <a href="#resilient"><code>--resilient</code></a>, <a href="#recover"><code>--recover</code></a>, and <a href="#conflict-resolve"><code>--conflict-resolve</code></a> flags, (along with <a href="#graceful-shutdown">Graceful Shutdown</a> mode, when needed) for a very robust "set-it-and-forget-it" bisync setup that can automatically bounce back from almost any interruption it might encounter. Consider adding something like the following:</p>
<pre><code>--resilient --recover --max-lock 2m --conflict-resolve newer</code></pre>
<h3 id="resync-mode">--resync-mode CHOICE</h3>
<p>In the event that a file differs on both sides during a <code>--resync</code>, <code>--resync-mode</code> controls which version will overwrite the other. The supported options are similar to <a href="#conflict-resolve"><code>--conflict-resolve</code></a>. For all of the following options, the version that is kept is referred to as the "winner", and the version that is overwritten (deleted) is referred to as the "loser". The options are named after the "winner":</p>
<ul>
<li><code>path1</code> - (the default) - the version from Path1 is unconditionally considered the winner (regardless of <code>modtime</code> and <code>size</code>, if any). This can be useful if one side is more trusted or up-to-date than the other, at the time of the <code>--resync</code>.</li>
<li><code>path2</code> - same as <code>path1</code>, except the path2 version is considered the winner.</li>
<li><code>newer</code> - the newer file (by <code>modtime</code>) is considered the winner, regardless of which side it came from. This may result in having a mix of some winners from Path1, and some winners from Path2. (The implementation is analogous to running <code>rclone copy --update</code> in both directions.)</li>
<li><code>older</code> - same as <code>newer</code>, except the older file is considered the winner, and the newer file is considered the loser.</li>
<li><code>larger</code> - the larger file (by <code>size</code>) is considered the winner (regardless of <code>modtime</code>, if any). This can be a useful option for remotes without <code>modtime</code> support, or with the kinds of files (such as logs) that tend to grow but not shrink, over time.</li>
<li><code>smaller</code> - the smaller file (by <code>size</code>) is considered the winner (regardless of <code>modtime</code>, if any).</li>
</ul>
<p>For all of the above options, note the following: - If either of the underlying remotes lacks support for the chosen method, it will be ignored and will fall back to the default of <code>path1</code>. (For example, if <code>--resync-mode newer</code> is set, but one of the paths uses a remote that doesn't support <code>modtime</code>.) - If a winner can't be determined because the chosen method's attribute is missing or equal, it will be ignored, and bisync will instead try to determine whether the files differ by looking at the other <code>--compare</code> methods in effect. (For example, if <code>--resync-mode newer</code> is set, but the Path1 and Path2 modtimes are identical, bisync will compare the sizes.) If bisync concludes that they differ, preference is given to whichever is the "source" at that moment. (In practice, this gives a slight advantage to Path2, as the 2to1 copy comes before the 1to2 copy.) If the files <em>do not</em> differ, nothing is copied (as both sides are already correct). - These options apply only to files that exist on both sides (with the same name and relative path). Files that exist <em>only</em> on one side and not the other are <em>always</em> copied to the other, during <code>--resync</code> (this is one of the main differences between resync and non-resync runs.). - <code>--conflict-resolve</code>, <code>--conflict-loser</code>, and <code>--conflict-suffix</code> do not apply during <code>--resync</code>, and unlike these flags, nothing is renamed during <code>--resync</code>. When a file differs on both sides during <code>--resync</code>, one version always overwrites the other (much like in <code>rclone copy</code>.) (Consider using <a href="#backup-dir1-and-backup-dir2"><code>--backup-dir</code></a> to retain a backup of the losing version.) - Unlike for <code>--conflict-resolve</code>, <code>--resync-mode none</code> is not a valid option (or rather, it will be interpreted as "no resync", unless <code>--resync</code> has also been specified, in which case it will be ignored.) - Winners and losers are decided at the individual file-level only (there is not currently an option to pick an entire winning directory atomically, although the <code>path1</code> and <code>path2</code> options typically produce a similar result.) - To maintain backward-compatibility, the <code>--resync</code> flag implies <code>--resync-mode path1</code> unless a different <code>--resync-mode</code> is explicitly specified. Similarly, all <code>--resync-mode</code> options (except <code>none</code>) imply <code>--resync</code>, so it is not necessary to use both the <code>--resync</code> and <code>--resync-mode</code> flags simultaneously -- either one is sufficient without the other.</p>
<h3 id="check-access">--check-access</h3>
<p>Access check files are an additional safety measure against data loss. bisync will ensure it can find matching <code>RCLONE_TEST</code> files in the same places in the Path1 and Path2 filesystems. <code>RCLONE_TEST</code> files are not generated automatically. For <code>--check-access</code> to succeed, you must first either: <strong>A)</strong> Place one or more <code>RCLONE_TEST</code> files in both systems, or <strong>B)</strong> Set <code>--check-filename</code> to a filename already in use in various locations throughout your sync'd fileset. Recommended methods for <strong>A)</strong> include: * <code>rclone touch Path1/RCLONE_TEST</code> (create a new file) * <code>rclone copyto Path1/RCLONE_TEST Path2/RCLONE_TEST</code> (copy an existing file) * <code>rclone copy Path1/RCLONE_TEST Path2/RCLONE_TEST  --include "RCLONE_TEST"</code> (copy multiple files at once, recursively) * create the files manually (outside of rclone) * run <code>bisync</code> once <em>without</em> <code>--check-access</code> to set matching files on both filesystems will also work, but is not preferred, due to potential for user error (you are temporarily disabling the safety feature).</p>
<p>Note that <code>--check-access</code> is still enforced on <code>--resync</code>, so <code>bisync --resync --check-access</code> will not work as a method of initially setting the files (this is to ensure that bisync can't <a href="https://forum.rclone.org/t/bisync-bugs-and-feature-requests/37636#:~:text=3.%20%2D%2Dcheck%2Daccess%20doesn%27t%20always%20fail%20when%20it%20should">inadvertently circumvent its own safety switch</a>.)</p>
<p>Time stamps and file contents for <code>RCLONE_TEST</code> files are not important, just the names and locations. If you have symbolic links in your sync tree it is recommended to place <code>RCLONE_TEST</code> files in the linked-to directory tree to protect against bisync assuming a bunch of deleted files if the linked-to tree should not be accessible. See also the <a href="--check-filename">--check-filename</a> flag.</p>
<h3 id="check-filename">--check-filename</h3>
<p>Name of the file(s) used in access health validation. The default <code>--check-filename</code> is <code>RCLONE_TEST</code>. One or more files having this filename must exist, synchronized between your source and destination filesets, in order for <code>--check-access</code> to succeed. See <a href="#check-access">--check-access</a> for additional details.</p>
<h3 id="compare">--compare</h3>
<p>As of <code>v1.66</code>, bisync fully supports comparing based on any combination of size, modtime, and checksum (lifting the prior restriction on backends without modtime support.)</p>
<p>By default (without the <code>--compare</code> flag), bisync inherits the same comparison options as <code>sync</code> (that is: <code>size</code> and <code>modtime</code> by default, unless modified with flags such as <a href="https://rclone.org/docs/#c-checksum"><code>--checksum</code></a> or <a href="/docs/#size-only"><code>--size-only</code></a>.)</p>
<p>If the <code>--compare</code> flag is set, it will override these defaults. This can be useful if you wish to compare based on combinations not currently supported in <code>sync</code>, such as comparing all three of <code>size</code> AND <code>modtime</code> AND <code>checksum</code> simultaneously (or just <code>modtime</code> AND <code>checksum</code>).</p>
<p><code>--compare</code> takes a comma-separated list, with the currently supported values being <code>size</code>, <code>modtime</code>, and <code>checksum</code>. For example, if you want to compare size and checksum, but not modtime, you would do:</p>
<pre><code>--compare size,checksum</code></pre>
<p>Or if you want to compare all three:</p>
<pre><code>--compare size,modtime,checksum</code></pre>
<p><code>--compare</code> overrides any conflicting flags. For example, if you set the conflicting flags <code>--compare checksum --size-only</code>, <code>--size-only</code> will be ignored, and bisync will compare checksum and not size. To avoid confusion, it is recommended to use <em>either</em> <code>--compare</code> or the normal <code>sync</code> flags, but not both.</p>
<p>If <code>--compare</code> includes <code>checksum</code> and both remotes support checksums but have no hash types in common with each other, checksums will be considered <em>only</em> for comparisons within the same side (to determine what has changed since the prior sync), but not for comparisons against the opposite side. If one side supports checksums and the other does not, checksums will only be considered on the side that supports them.</p>
<p>When comparing with <code>checksum</code> and/or <code>size</code> without <code>modtime</code>, bisync cannot determine whether a file is <code>newer</code> or <code>older</code> -- only whether it is <code>changed</code> or <code>unchanged</code>. (If it is <code>changed</code> on both sides, bisync still does the standard equality-check to avoid declaring a sync conflict unless it absolutely has to.)</p>
<p>It is recommended to do a <code>--resync</code> when changing <code>--compare</code> settings, as otherwise your prior listing files may not contain the attributes you wish to compare (for example, they will not have stored checksums if you were not previously comparing checksums.)</p>
<h3 id="ignore-listing-checksum">--ignore-listing-checksum</h3>
<p>When <code>--checksum</code> or <code>--compare checksum</code> is set, bisync will retrieve (or generate) checksums (for backends that support them) when creating the listings for both paths, and store the checksums in the listing files. <code>--ignore-listing-checksum</code> will disable this behavior, which may speed things up considerably, especially on backends (such as <a href="https://rclone.org/local/">local</a>) where hashes must be computed on the fly instead of retrieved. Please note the following:</p>
<ul>
<li>As of <code>v1.66</code>, <code>--ignore-listing-checksum</code> is now automatically set when neither <code>--checksum</code> nor <code>--compare checksum</code> are in use (as the checksums would not be used for anything.)</li>
<li><code>--ignore-listing-checksum</code> is NOT the same as <a href="https://rclone.org/docs/#ignore-checksum"><code>--ignore-checksum</code></a>, and you may wish to use one or the other, or both. In a nutshell: <code>--ignore-listing-checksum</code> controls whether checksums are considered when scanning for diffs, while <code>--ignore-checksum</code> controls whether checksums are considered during the copy/sync operations that follow, if there ARE diffs.</li>
<li>Unless <code>--ignore-listing-checksum</code> is passed, bisync currently computes hashes for one path <em>even when there's no common hash with the other path</em> (for example, a <a href="https://rclone.org/crypt/#modification-times-and-hashes">crypt</a> remote.) This can still be beneficial, as the hashes will still be used to detect changes within the same side (if <code>--checksum</code> or <code>--compare checksum</code> is set), even if they can't be used to compare against the opposite side.</li>
<li>If you wish to ignore listing checksums <em>only</em> on remotes where they are slow to compute, consider using <a href="#no-slow-hash"><code>--no-slow-hash</code></a> (or <a href="#slow-hash-sync-only"><code>--slow-hash-sync-only</code></a>) instead of <code>--ignore-listing-checksum</code>.</li>
<li>If <code>--ignore-listing-checksum</code> is used simultaneously with <code>--compare checksum</code> (or <code>--checksum</code>), checksums will be ignored for bisync deltas, but still considered during the sync operations that follow (if deltas are detected based on modtime and/or size.)</li>
</ul>
<h3 id="no-slow-hash">--no-slow-hash</h3>
<p>On some remotes (notably <code>local</code>), checksums can dramatically slow down a bisync run, because hashes cannot be stored and need to be computed in real-time when they are requested. On other remotes (such as <code>drive</code>), they add practically no time at all. The <code>--no-slow-hash</code> flag will automatically skip checksums on remotes where they are slow, while still comparing them on others (assuming <a href="#compare"><code>--compare</code></a> includes <code>checksum</code>.) This can be useful when one of your bisync paths is slow but you still want to check checksums on the other, for a more robust sync.</p>
<h3 id="slow-hash-sync-only">--slow-hash-sync-only</h3>
<p>Same as <a href="#no-slow-hash"><code>--no-slow-hash</code></a>, except slow hashes are still considered during sync calls. They are still NOT considered for determining deltas, nor or they included in listings. They are also skipped during <code>--resync</code>. The main use case for this flag is when you have a large number of files, but relatively few of them change from run to run -- so you don't want to check your entire tree every time (it would take too long), but you still want to consider checksums for the smaller group of files for which a <code>modtime</code> or <code>size</code> change was detected. Keep in mind that this speed savings comes with a safety trade-off: if a file's content were to change without a change to its <code>modtime</code> or <code>size</code>, bisync would not detect it, and it would not be synced.</p>
<p><code>--slow-hash-sync-only</code> is only useful if both remotes share a common hash type (if they don't, bisync will automatically fall back to <code>--no-slow-hash</code>.) Both <code>--no-slow-hash</code> and <code>--slow-hash-sync-only</code> have no effect without <code>--compare checksum</code> (or <code>--checksum</code>).</p>
<h3 id="download-hash">--download-hash</h3>
<p>If <code>--download-hash</code> is set, bisync will use best efforts to obtain an MD5 checksum by downloading and computing on-the-fly, when checksums are not otherwise available (for example, a remote that doesn't support them.) Note that since rclone has to download the entire file, this may dramatically slow down your bisync runs, and is also likely to use a lot of data, so it is probably not practical for bisync paths with a large total file size. However, it can be a good option for syncing small-but-important files with maximum accuracy (for example, a source code repo on a <code>crypt</code> remote.) An additional advantage over methods like <a href="https://rclone.org/commands/rclone_cryptcheck/"><code>cryptcheck</code></a> is that the original file is not required for comparison (for example, <code>--download-hash</code> can be used to bisync two different crypt remotes with different passwords.)</p>
<p>When <code>--download-hash</code> is set, bisync still looks for more efficient checksums first, and falls back to downloading only when none are found. It takes priority over conflicting flags such as <code>--no-slow-hash</code>. <code>--download-hash</code> is not suitable for <a href="#gdocs">Google Docs</a> and other files of unknown size, as their checksums would change from run to run (due to small variances in the internals of the generated export file.) Therefore, bisync automatically skips <code>--download-hash</code> for files with a size less than 0.</p>
<p>See also: <a href="https://rclone.org/hasher/"><code>Hasher</code></a> backend, <a href="https://rclone.org/commands/rclone_cryptcheck/"><code>cryptcheck</code></a> command, <a href="https://rclone.org/commands/rclone_check/"><code>rclone check --download</code></a> option, <a href="https://rclone.org/commands/rclone_md5sum/"><code>md5sum</code></a> command</p>
<h3 id="max-delete">--max-delete</h3>
<p>As a safety check, if greater than the <code>--max-delete</code> percent of files were deleted on either the Path1 or Path2 filesystem, then bisync will abort with a warning message, without making any changes. The default <code>--max-delete</code> is <code>50%</code>. One way to trigger this limit is to rename a directory that contains more than half of your files. This will appear to bisync as a bunch of deleted files and a bunch of new files. This safety check is intended to block bisync from deleting all of the files on both filesystems due to a temporary network access issue, or if the user had inadvertently deleted the files on one side or the other. To force the sync, either set a different delete percentage limit, e.g. <code>--max-delete 75</code> (allows up to 75% deletion), or use <code>--force</code> to bypass the check.</p>
<p>Also see the <a href="#all-files-changed">all files changed</a> check.</p>
<h3 id="filters-file">--filters-file</h3>
<p>By using rclone filter features you can exclude file types or directory sub-trees from the sync. See the <a href="#filtering">bisync filters</a> section and generic <a href="https://rclone.org/filtering/#filter-from-read-filtering-patterns-from-a-file">--filter-from</a> documentation. An <a href="#example-filters-file">example filters file</a> contains filters for non-allowed files for synching with Dropbox.</p>
<p>If you make changes to your filters file then bisync requires a run with <code>--resync</code>. This is a safety feature, which prevents existing files on the Path1 and/or Path2 side from seeming to disappear from view (since they are excluded in the new listings), which would fool bisync into seeing them as deleted (as compared to the prior run listings), and then bisync would proceed to delete them for real.</p>
<p>To block this from happening, bisync calculates an MD5 hash of the filters file and stores the hash in a <code>.md5</code> file in the same place as your filters file. On the next run with <code>--filters-file</code> set, bisync re-calculates the MD5 hash of the current filters file and compares it to the hash stored in the <code>.md5</code> file. If they don't match, the run aborts with a critical error and thus forces you to do a <code>--resync</code>, likely avoiding a disaster.</p>
<h3 id="conflict-resolve">--conflict-resolve CHOICE</h3>
<p>In bisync, a "conflict" is a file that is <em>new</em> or <em>changed</em> on <em>both sides</em> (relative to the prior run) AND is <em>not currently identical</em> on both sides. <code>--conflict-resolve</code> controls how bisync handles such a scenario. The currently supported options are:</p>
<ul>
<li><code>none</code> - (the default) - do not attempt to pick a winner, keep and rename both files according to <a href="#conflict-loser"><code>--conflict-loser</code></a> and <a href="#conflict-suffix"><code>--conflict-suffix</code></a> settings. For example, with the default settings, <code>file.txt</code> on Path1 is renamed <code>file.txt.conflict1</code> and <code>file.txt</code> on Path2 is renamed <code>file.txt.conflict2</code>. Both are copied to the opposite path during the run, so both sides end up with a copy of both files. (As <code>none</code> is the default, it is not necessary to specify <code>--conflict-resolve none</code> -- you can just omit the flag.)</li>
<li><code>newer</code> - the newer file (by <code>modtime</code>) is considered the winner and is copied without renaming. The older file (the "loser") is handled according to <code>--conflict-loser</code> and <code>--conflict-suffix</code> settings (either renamed or deleted.) For example, if <code>file.txt</code> on Path1 is newer than <code>file.txt</code> on Path2, the result on both sides (with other default settings) will be <code>file.txt</code> (winner from Path1) and <code>file.txt.conflict1</code> (loser from Path2).</li>
<li><code>older</code> - same as <code>newer</code>, except the older file is considered the winner, and the newer file is considered the loser.</li>
<li><code>larger</code> - the larger file (by <code>size</code>) is considered the winner (regardless of <code>modtime</code>, if any).</li>
<li><code>smaller</code> - the smaller file (by <code>size</code>) is considered the winner (regardless of <code>modtime</code>, if any).</li>
<li><code>path1</code> - the version from Path1 is unconditionally considered the winner (regardless of <code>modtime</code> and <code>size</code>, if any). This can be useful if one side is usually more trusted or up-to-date than the other.</li>
<li><code>path2</code> - same as <code>path1</code>, except the path2 version is considered the winner.</li>
</ul>
<p>For all of the above options, note the following: - If either of the underlying remotes lacks support for the chosen method, it will be ignored and fall back to <code>none</code>. (For example, if <code>--conflict-resolve newer</code> is set, but one of the paths uses a remote that doesn't support <code>modtime</code>.) - If a winner can't be determined because the chosen method's attribute is missing or equal, it will be ignored and fall back to <code>none</code>. (For example, if <code>--conflict-resolve newer</code> is set, but the Path1 and Path2 modtimes are identical, even if the sizes may differ.) - If the file's content is currently identical on both sides, it is not considered a "conflict", even if new or changed on both sides since the prior sync. (For example, if you made a change on one side and then synced it to the other side by other means.) Therefore, none of the conflict resolution flags apply in this scenario. - The conflict resolution flags do not apply during a <code>--resync</code>, as there is no "prior run" to speak of (but see <a href="#resync-mode"><code>--resync-mode</code></a> for similar options.)</p>
<h3 id="conflict-loser">--conflict-loser CHOICE</h3>
<p><code>--conflict-loser</code> determines what happens to the "loser" of a sync conflict (when <a href="#conflict-resolve"><code>--conflict-resolve</code></a> determines a winner) or to both files (when there is no winner.) The currently supported options are:</p>
<ul>
<li><code>num</code> - (the default) - auto-number the conflicts by automatically appending the next available number to the <code>--conflict-suffix</code>, in chronological order. For example, with the default settings, the first conflict for <code>file.txt</code> will be renamed <code>file.txt.conflict1</code>. If <code>file.txt.conflict1</code> already exists, <code>file.txt.conflict2</code> will be used instead (etc., up to a maximum of 9223372036854775807 conflicts.)</li>
<li><code>pathname</code> - rename the conflicts according to which side they came from, which was the default behavior prior to <code>v1.66</code>. For example, with <code>--conflict-suffix path</code>, <code>file.txt</code> from Path1 will be renamed <code>file.txt.path1</code>, and <code>file.txt</code> from Path2 will be renamed <code>file.txt.path2</code>. If two non-identical suffixes are provided (ex. <code>--conflict-suffix cloud,local</code>), the trailing digit is omitted. Importantly, note that with <code>pathname</code>, there is no auto-numbering beyond <code>2</code>, so if <code>file.txt.path2</code> somehow already exists, it will be overwritten. Using a dynamic date variable in your <code>--conflict-suffix</code> (see below) is one possible way to avoid this. Note also that conflicts-of-conflicts are possible, if the original conflict is not manually resolved -- for example, if for some reason you edited <code>file.txt.path1</code> on both sides, and those edits were different, the result would be <code>file.txt.path1.path1</code> and <code>file.txt.path1.path2</code> (in addition to <code>file.txt.path2</code>.)</li>
<li><code>delete</code> - keep the winner only and delete the loser, instead of renaming it. If a winner cannot be determined (see <code>--conflict-resolve</code> for details on how this could happen), <code>delete</code> is ignored and the default <code>num</code> is used instead (i.e. both versions are kept and renamed, and neither is deleted.) <code>delete</code> is inherently the most destructive option, so use it only with care.</li>
</ul>
<p>For all of the above options, note that if a winner cannot be determined (see <code>--conflict-resolve</code> for details on how this could happen), or if <code>--conflict-resolve</code> is not in use, <em>both</em> files will be renamed.</p>
<h3 id="conflict-suffix">--conflict-suffix STRING[,STRING]</h3>
<p><code>--conflict-suffix</code> controls the suffix that is appended when bisync renames a <a href="#conflict-loser"><code>--conflict-loser</code></a> (default: <code>conflict</code>). <code>--conflict-suffix</code> will accept either one string or two comma-separated strings to assign different suffixes to Path1 vs. Path2. This may be helpful later in identifying the source of the conflict. (For example, <code>--conflict-suffix dropboxconflict,laptopconflict</code>)</p>
<p>With <code>--conflict-loser num</code>, a number is always appended to the suffix. With <code>--conflict-loser pathname</code>, a number is appended only when one suffix is specified (or when two identical suffixes are specified.) i.e. with <code>--conflict-loser pathname</code>, all of the following would produce exactly the same result:</p>
<pre><code>--conflict-suffix path
--conflict-suffix path,path
--conflict-suffix path1,path2</code></pre>
<p>Suffixes may be as short as 1 character. By default, the suffix is appended after any other extensions (ex. <code>file.jpg.conflict1</code>), however, this can be changed with the <a href="https://rclone.org/docs/#suffix-keep-extension"><code>--suffix-keep-extension</code></a> flag (i.e. to instead result in <code>file.conflict1.jpg</code>).</p>
<p><code>--conflict-suffix</code> supports several <em>dynamic date variables</em> when enclosed in curly braces as globs. This can be helpful to track the date and/or time that each conflict was handled by bisync. For example:</p>
<pre><code>--conflict-suffix {DateOnly}-conflict
// result: myfile.txt.2006-01-02-conflict1</code></pre>
<p>All of the formats described <a href="https://pkg.go.dev/time#pkg-constants">here</a> and <a href="https://pkg.go.dev/time#example-Time.Format">here</a> are supported, but take care to ensure that your chosen format does not use any characters that are illegal on your remotes (for example, macOS does not allow colons in filenames, and slashes are also best avoided as they are often interpreted as directory separators.) To address this particular issue, an additional <code>{MacFriendlyTime}</code> (or just <code>{mac}</code>) option is supported, which results in <code>2006-01-02 0304PM</code>.</p>
<p>Note that <code>--conflict-suffix</code> is entirely separate from rclone's main <a href="https://rclone.org/docs/#suffix-suffix"><code>--sufix</code></a> flag. This is intentional, as users may wish to use both flags simultaneously, if also using <a href="#backup-dir1-and-backup-dir2"><code>--backup-dir</code></a>.</p>
<p>Finally, note that the default in bisync prior to <code>v1.66</code> was to rename conflicts with <code>..path1</code> and <code>..path2</code> (with two periods, and <code>path</code> instead of <code>conflict</code>.) Bisync now defaults to a single dot instead of a double dot, but additional dots can be added by including them in the specified suffix string. For example, for behavior equivalent to the previous default, use:</p>
<pre><code>[--conflict-resolve none] --conflict-loser pathname --conflict-suffix .path</code></pre>
<h3 id="check-sync">--check-sync</h3>
<p>Enabled by default, the check-sync function checks that all of the same files exist in both the Path1 and Path2 history listings. This <em>check-sync</em> integrity check is performed at the end of the sync run by default. Any untrapped failing copy/deletes between the two paths might result in differences between the two listings and in the untracked file content differences between the two paths. A resync run would correct the error.</p>
<p>Note that the default-enabled integrity check locally executes a load of both the final Path1 and Path2 listings, and thus adds to the run time of a sync. Using <code>--check-sync=false</code> will disable it and may significantly reduce the sync run times for very large numbers of files.</p>
<p>The check may be run manually with <code>--check-sync=only</code>. It runs only the integrity check and terminates without actually synching.</p>
<p>Note that currently, <code>--check-sync</code> <strong>only checks listing snapshots and NOT the actual files on the remotes.</strong> Note also that the listing snapshots will not know about any changes that happened during or after the latest bisync run, as those will be discovered on the next run. Therefore, while listings should always match <em>each other</em> at the end of a bisync run, it is <em>expected</em> that they will not match the underlying remotes, nor will the remotes match each other, if there were changes during or after the run. This is normal, and any differences will be detected and synced on the next run.</p>
<p>For a robust integrity check of the current state of the remotes (as opposed to just their listing snapshots), consider using <a href="commands/rclone_check/"><code>check</code></a> (or <a href="https://rclone.org/commands/rclone_cryptcheck/"><code>cryptcheck</code></a>, if at least one path is a <code>crypt</code> remote) instead of <code>--check-sync</code>, keeping in mind that differences are expected if files changed during or after your last bisync run.</p>
<p>For example, a possible sequence could look like this:</p>
<ol type="1">
<li>Normally scheduled bisync run:</li>
</ol>
<pre><code>rclone bisync Path1 Path2 -MPc --check-access --max-delete 10 --filters-file /path/to/filters.txt -v --no-cleanup --ignore-listing-checksum --disable ListR --checkers=16 --drive-pacer-min-sleep=10ms --create-empty-src-dirs --resilient</code></pre>
<ol start="2" type="1">
<li>Periodic independent integrity check (perhaps scheduled nightly or weekly):</li>
</ol>
<pre><code>rclone check -MvPc Path1 Path2 --filter-from /path/to/filters.txt</code></pre>
<ol start="3" type="1">
<li>If diffs are found, you have some choices to correct them. If one side is more up-to-date and you want to make the other side match it, you could run:</li>
</ol>
<pre><code>rclone sync Path1 Path2 --filter-from /path/to/filters.txt --create-empty-src-dirs -MPc -v</code></pre>
<p>(or switch Path1 and Path2 to make Path2 the source-of-truth)</p>
<p>Or, if neither side is totally up-to-date, you could run a <code>--resync</code> to bring them back into agreement (but remember that this could cause deleted files to re-appear.)</p>
<p>*Note also that <code>rclone check</code> does not currently include empty directories, so if you want to know if any empty directories are out of sync, consider alternatively running the above <code>rclone sync</code> command with <code>--dry-run</code> added.</p>
<p>See also: <a href="#concurrent-modifications">Concurrent modifications</a>, <a href="#resilient"><code>--resilient</code></a></p>
<h3 id="resilient">--resilient</h3>
<p><strong><em>Caution: this is an experimental feature. Use at your own risk!</em></strong></p>
<p>By default, most errors or interruptions will cause bisync to abort and require <a href="#resync"><code>--resync</code></a> to recover. This is a safety feature, to prevent bisync from running again until a user checks things out. However, in some cases, bisync can go too far and enforce a lockout when one isn't actually necessary, like for certain less-serious errors that might resolve themselves on the next run. When <code>--resilient</code> is specified, bisync tries its best to recover and self-correct, and only requires <code>--resync</code> as a last resort when a human's involvement is absolutely necessary. The intended use case is for running bisync as a background process (such as via scheduled <a href="#cron">cron</a>).</p>
<p>When using <code>--resilient</code> mode, bisync will still report the error and abort, however it will not lock out future runs -- allowing the possibility of retrying at the next normally scheduled time, without requiring a <code>--resync</code> first. Examples of such retryable errors include access test failures, missing listing files, and filter change detections. These safety features will still prevent the <em>current</em> run from proceeding -- the difference is that if conditions have improved by the time of the <em>next</em> run, that next run will be allowed to proceed. Certain more serious errors will still enforce a <code>--resync</code> lockout, even in <code>--resilient</code> mode, to prevent data loss.</p>
<p>Behavior of <code>--resilient</code> may change in a future version. (See also: <a href="#recover"><code>--recover</code></a>, <a href="#max-lock"><code>--max-lock</code></a>, <a href="#graceful-shutdown">Graceful Shutdown</a>)</p>
<h3 id="recover">--recover</h3>
<p>If <code>--recover</code> is set, in the event of a sudden interruption or other un-graceful shutdown, bisync will attempt to automatically recover on the next run, instead of requiring <code>--resync</code>. Bisync is able to recover robustly by keeping one "backup" listing at all times, representing the state of both paths after the last known successful sync. Bisync can then compare the current state with this snapshot to determine which changes it needs to retry. Changes that were synced after this snapshot (during the run that was later interrupted) will appear to bisync as if they are "new or changed on both sides", but in most cases this is not a problem, as bisync will simply do its usual "equality check" and learn that no action needs to be taken on these files, since they are already identical on both sides.</p>
<p>In the rare event that a file is synced successfully during a run that later aborts, and then that same file changes AGAIN before the next run, bisync will think it is a sync conflict, and handle it accordingly. (From bisync's perspective, the file has changed on both sides since the last trusted sync, and the files on either side are not currently identical.) Therefore, <code>--recover</code> carries with it a slightly increased chance of having conflicts -- though in practice this is pretty rare, as the conditions required to cause it are quite specific. This risk can be reduced by using bisync's <a href="#graceful-shutdown">"Graceful Shutdown"</a> mode (triggered by sending <code>SIGINT</code> or <code>Ctrl+C</code>), when you have the choice, instead of forcing a sudden termination.</p>
<p><code>--recover</code> and <code>--resilient</code> are similar, but distinct -- the main difference is that <code>--resilient</code> is about <em>retrying</em>, while <code>--recover</code> is about <em>recovering</em>. Most users will probably want both. <code>--resilient</code> allows retrying when bisync has chosen to abort itself due to safety features such as failing <code>--check-access</code> or detecting a filter change. <code>--resilient</code> does not cover external interruptions such as a user shutting down their computer in the middle of a sync -- that is what <code>--recover</code> is for.</p>
<h3 id="max-lock">--max-lock</h3>
<p>Bisync uses <a href="#lock-file">lock files</a> as a safety feature to prevent interference from other bisync runs while it is running. Bisync normally removes these lock files at the end of a run, but if bisync is abruptly interrupted, these files will be left behind. By default, they will lock out all future runs, until the user has a chance to manually check things out and remove the lock. As an alternative, <code>--max-lock</code> can be used to make them automatically expire after a certain period of time, so that future runs are not locked out forever, and auto-recovery is possible. <code>--max-lock</code> can be any duration <code>2m</code> or greater (or <code>0</code> to disable). If set, lock files older than this will be considered "expired", and future runs will be allowed to disregard them and proceed. (Note that the <code>--max-lock</code> duration must be set by the process that left the lock file -- not the later one interpreting it.)</p>
<p>If set, bisync will also "renew" these lock files every <code>--max-lock minus one minute</code> throughout a run, for extra safety. (For example, with <code>--max-lock 5m</code>, bisync would renew the lock file (for another 5 minutes) every 4 minutes until the run has completed.) In other words, it should not be possible for a lock file to pass its expiration time while the process that created it is still running -- and you can therefore be reasonably sure that any <em>expired</em> lock file you may find was left there by an interrupted run, not one that is still running and just taking awhile.</p>
<p>If <code>--max-lock</code> is <code>0</code> or not set, the default is that lock files will never expire, and will block future runs (of these same two bisync paths) indefinitely.</p>
<p>For maximum resilience from disruptions, consider setting a relatively short duration like <code>--max-lock 2m</code> along with <a href="#resilient"><code>--resilient</code></a> and <a href="#recover"><code>--recover</code></a>, and a relatively frequent <a href="#cron">cron schedule</a>. The result will be a very robust "set-it-and-forget-it" bisync run that can automatically bounce back from almost any interruption it might encounter, without requiring the user to get involved and run a <code>--resync</code>. (See also: <a href="#graceful-shutdown">Graceful Shutdown</a> mode)</p>
<h3 id="backup-dir1-and---backup-dir2">--backup-dir1 and --backup-dir2</h3>
<p>As of <code>v1.66</code>, <a href="https://rclone.org/docs/#backup-dir-dir"><code>--backup-dir</code></a> is supported in bisync. Because <code>--backup-dir</code> must be a non-overlapping path on the same remote, Bisync has introduced new <code>--backup-dir1</code> and <code>--backup-dir2</code> flags to support separate backup-dirs for <code>Path1</code> and <code>Path2</code> (bisyncing between different remotes with <code>--backup-dir</code> would not otherwise be possible.) <code>--backup-dir1</code> and <code>--backup-dir2</code> can use different remotes from each other, but <code>--backup-dir1</code> must use the same remote as <code>Path1</code>, and <code>--backup-dir2</code> must use the same remote as <code>Path2</code>. Each backup directory must not overlap its respective bisync Path without being excluded by a filter rule.</p>
<p>The standard <code>--backup-dir</code> will also work, if both paths use the same remote (but note that deleted files from both paths would be mixed together in the same dir). If either <code>--backup-dir1</code> and <code>--backup-dir2</code> are set, they will override <code>--backup-dir</code>.</p>
<p>Example:</p>
<pre><code>rclone bisync /Users/someuser/some/local/path/Bisync gdrive:Bisync --backup-dir1 /Users/someuser/some/local/path/BackupDir --backup-dir2 gdrive:BackupDir --suffix -2023-08-26 --suffix-keep-extension --check-access --max-delete 10 --filters-file /Users/someuser/some/local/path/bisync_filters.txt --no-cleanup --ignore-listing-checksum --checkers=16 --drive-pacer-min-sleep=10ms --create-empty-src-dirs --resilient -MvP --drive-skip-gdocs --fix-case</code></pre>
<p>In this example, if the user deletes a file in <code>/Users/someuser/some/local/path/Bisync</code>, bisync will propagate the delete to the other side by moving the corresponding file from <code>gdrive:Bisync</code> to <code>gdrive:BackupDir</code>. If the user deletes a file from <code>gdrive:Bisync</code>, bisync moves it from <code>/Users/someuser/some/local/path/Bisync</code> to <code>/Users/someuser/some/local/path/BackupDir</code>.</p>
<p>In the event of a <a href="#conflict-loser">rename due to a sync conflict</a>, the rename is not considered a delete, unless a previous conflict with the same name already exists and would get overwritten.</p>
<p>See also: <a href="https://rclone.org/docs/#suffix-suffix"><code>--suffix</code></a>, <a href="https://rclone.org/docs/#suffix-keep-extension"><code>--suffix-keep-extension</code></a></p>
<h2 id="operation">Operation</h2>
<h3 id="runtime-flow-details">Runtime flow details</h3>
<p>bisync retains the listings of the <code>Path1</code> and <code>Path2</code> filesystems from the prior run. On each successive run it will:</p>
<ul>
<li>list files on <code>path1</code> and <code>path2</code>, and check for changes on each side. Changes include <code>New</code>, <code>Newer</code>, <code>Older</code>, and <code>Deleted</code> files.</li>
<li>Propagate changes on <code>path1</code> to <code>path2</code>, and vice-versa.</li>
</ul>
<h3 id="safety-measures">Safety measures</h3>
<ul>
<li>Lock file prevents multiple simultaneous runs when taking a while. This can be particularly useful if bisync is run by cron scheduler.</li>
<li>Handle change conflicts non-destructively by creating <code>.conflict1</code>, <code>.conflict2</code>, etc. file versions, according to <a href="#conflict-resolve"><code>--conflict-resolve</code></a>, <a href="#conflict-loser"><code>--conflict-loser</code></a>, and <a href="#conflict-suffix"><code>--conflict-suffix</code></a> settings.</li>
<li>File system access health check using <code>RCLONE_TEST</code> files (see the <code>--check-access</code> flag).</li>
<li>Abort on excessive deletes - protects against a failed listing being interpreted as all the files were deleted. See the <code>--max-delete</code> and <code>--force</code> flags.</li>
<li>If something evil happens, bisync goes into a safe state to block damage by later runs. (See <a href="#error-handling">Error Handling</a>)</li>
</ul>
<h3 id="normal-sync-checks">Normal sync checks</h3>
<table>
<colgroup>
<col style="width: 12%" />
<col style="width: 40%" />
<col style="width: 22%" />
<col style="width: 25%" />
</colgroup>
<thead>
<tr class="header">
<th>Type</th>
<th>Description</th>
<th>Result</th>
<th>Implementation</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td>Path2 new</td>
<td>File is new on Path2, does not exist on Path1</td>
<td>Path2 version survives</td>
<td><code>rclone copy</code> Path2 to Path1</td>
</tr>
<tr class="even">
<td>Path2 newer</td>
<td>File is newer on Path2, unchanged on Path1</td>
<td>Path2 version survives</td>
<td><code>rclone copy</code> Path2 to Path1</td>
</tr>
<tr class="odd">
<td>Path2 deleted</td>
<td>File is deleted on Path2, unchanged on Path1</td>
<td>File is deleted</td>
<td><code>rclone delete</code> Path1</td>
</tr>
<tr class="even">
<td>Path1 new</td>
<td>File is new on Path1, does not exist on Path2</td>
<td>Path1 version survives</td>
<td><code>rclone copy</code> Path1 to Path2</td>
</tr>
<tr class="odd">
<td>Path1 newer</td>
<td>File is newer on Path1, unchanged on Path2</td>
<td>Path1 version survives</td>
<td><code>rclone copy</code> Path1 to Path2</td>
</tr>
<tr class="even">
<td>Path1 older</td>
<td>File is older on Path1, unchanged on Path2</td>
<td><em>Path1 version survives</em></td>
<td><code>rclone copy</code> Path1 to Path2</td>
</tr>
<tr class="odd">
<td>Path2 older</td>
<td>File is older on Path2, unchanged on Path1</td>
<td><em>Path2 version survives</em></td>
<td><code>rclone copy</code> Path2 to Path1</td>
</tr>
<tr class="even">
<td>Path1 deleted</td>
<td>File no longer exists on Path1</td>
<td>File is deleted</td>
<td><code>rclone delete</code> Path2</td>
</tr>
</tbody>
</table>
<h3 id="unusual-sync-checks">Unusual sync checks</h3>
<table>
<colgroup>
<col style="width: 24%" />
<col style="width: 30%" />
<col style="width: 27%" />
<col style="width: 17%" />
</colgroup>
<thead>
<tr class="header">
<th>Type</th>
<th>Description</th>
<th>Result</th>
<th>Implementation</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td>Path1 new/changed AND Path2 new/changed AND Path1 == Path2</td>
<td>File is new/changed on Path1 AND new/changed on Path2 AND Path1 version is currently identical to Path2</td>
<td>No change</td>
<td>None</td>
</tr>
<tr class="even">
<td>Path1 new AND Path2 new</td>
<td>File is new on Path1 AND new on Path2 (and Path1 version is NOT identical to Path2)</td>
<td>Conflicts handled according to <a href="#conflict-resolve"><code>--conflict-resolve</code></a> &amp; <a href="#conflict-loser"><code>--conflict-loser</code></a> settings</td>
<td>default: <code>rclone copy</code> renamed <code>Path2.conflict2</code> file to Path1, <code>rclone copy</code> renamed <code>Path1.conflict1</code> file to Path2</td>
</tr>
<tr class="odd">
<td>Path2 newer AND Path1 changed</td>
<td>File is newer on Path2 AND also changed (newer/older/size) on Path1 (and Path1 version is NOT identical to Path2)</td>
<td>Conflicts handled according to <a href="#conflict-resolve"><code>--conflict-resolve</code></a> &amp; <a href="#conflict-loser"><code>--conflict-loser</code></a> settings</td>
<td>default: <code>rclone copy</code> renamed <code>Path2.conflict2</code> file to Path1, <code>rclone copy</code> renamed <code>Path1.conflict1</code> file to Path2</td>
</tr>
<tr class="even">
<td>Path2 newer AND Path1 deleted</td>
<td>File is newer on Path2 AND also deleted on Path1</td>
<td>Path2 version survives</td>
<td><code>rclone copy</code> Path2 to Path1</td>
</tr>
<tr class="odd">
<td>Path2 deleted AND Path1 changed</td>
<td>File is deleted on Path2 AND changed (newer/older/size) on Path1</td>
<td>Path1 version survives</td>
<td><code>rclone copy</code> Path1 to Path2</td>
</tr>
<tr class="even">
<td>Path1 deleted AND Path2 changed</td>
<td>File is deleted on Path1 AND changed (newer/older/size) on Path2</td>
<td>Path2 version survives</td>
<td><code>rclone copy</code> Path2 to Path1</td>
</tr>
</tbody>
</table>
<p>As of <code>rclone v1.64</code>, bisync is now better at detecting <em>false positive</em> sync conflicts, which would previously have resulted in unnecessary renames and duplicates. Now, when bisync comes to a file that it wants to rename (because it is new/changed on both sides), it first checks whether the Path1 and Path2 versions are currently <em>identical</em> (using the same underlying function as <a href="commands/rclone_check/"><code>check</code></a>.) If bisync concludes that the files are identical, it will skip them and move on. Otherwise, it will create renamed duplicates, as before. This behavior also <a href="https://forum.rclone.org/t/bisync-bugs-and-feature-requests/37636#:~:text=Renamed%20directories">improves the experience of renaming directories</a>, as a <code>--resync</code> is no longer required, so long as the same change has been made on both sides.</p>
<h3 id="all-files-changed">All files changed check</h3>
<p>If <em>all</em> prior existing files on either of the filesystems have changed (e.g. timestamps have changed due to changing the system's timezone) then bisync will abort without making any changes. Any new files are not considered for this check. You could use <code>--force</code> to force the sync (whichever side has the changed timestamp files wins). Alternately, a <code>--resync</code> may be used (Path1 versions will be pushed to Path2). Consider the situation carefully and perhaps use <code>--dry-run</code> before you commit to the changes.</p>
<h3 id="modification-times">Modification times</h3>
<p>By default, bisync compares files by modification time and size. If you or your application should change the content of a file without changing the modification time and size, then bisync will <em>not</em> notice the change, and thus will not copy it to the other side. As an alternative, consider comparing by checksum (if your remotes support it). See <a href="#compare"><code>--compare</code></a> for details.</p>
<h3 id="error-handling">Error handling</h3>
<p>Certain bisync critical errors, such as file copy/move failing, will result in a bisync lockout of following runs. The lockout is asserted because the sync status and history of the Path1 and Path2 filesystems cannot be trusted, so it is safer to block any further changes until someone checks things out. The recovery is to do a <code>--resync</code> again.</p>
<p>It is recommended to use <code>--resync --dry-run --verbose</code> initially and <em>carefully</em> review what changes will be made before running the <code>--resync</code> without <code>--dry-run</code>.</p>
<p>Most of these events come up due to an error status from an internal call. On such a critical error the <code>{...}.path1.lst</code> and <code>{...}.path2.lst</code> listing files are renamed to extension <code>.lst-err</code>, which blocks any future bisync runs (since the normal <code>.lst</code> files are not found). Bisync keeps them under <code>bisync</code> subdirectory of the rclone cache directory, typically at <code>${HOME}/.cache/rclone/bisync/</code> on Linux.</p>
<p>Some errors are considered temporary and re-running the bisync is not blocked. The <em>critical return</em> blocks further bisync runs.</p>
<p>See also: <a href="#resilient"><code>--resilient</code></a>, <a href="#recover"><code>--recover</code></a>, <a href="#max-lock"><code>--max-lock</code></a>, <a href="#graceful-shutdown">Graceful Shutdown</a></p>
<h3 id="lock-file">Lock file</h3>
<p>When bisync is running, a lock file is created in the bisync working directory, typically at <code>~/.cache/rclone/bisync/PATH1..PATH2.lck</code> on Linux. If bisync should crash or hang, the lock file will remain in place and block any further runs of bisync <em>for the same paths</em>. Delete the lock file as part of debugging the situation. The lock file effectively blocks follow-on (e.g., scheduled by <em>cron</em>) runs when the prior invocation is taking a long time. The lock file contains <em>PID</em> of the blocking process, which may help in debug. Lock files can be set to automatically expire after a certain amount of time, using the <a href="#max-lock"><code>--max-lock</code></a> flag.</p>
<p><strong>Note</strong> that while concurrent bisync runs are allowed, <em>be very cautious</em> that there is no overlap in the trees being synched between concurrent runs, lest there be replicated files, deleted files and general mayhem.</p>
<h3 id="return-codes">Return codes</h3>
<p><code>rclone bisync</code> returns the following codes to calling program: - <code>0</code> on a successful run, - <code>1</code> for a non-critical failing run (a rerun may be successful), - <code>2</code> for a critically aborted run (requires a <code>--resync</code> to recover).</p>
<h3 id="graceful-shutdown">Graceful Shutdown</h3>
<p>Bisync has a "Graceful Shutdown" mode which is activated by sending <code>SIGINT</code> or pressing <code>Ctrl+C</code> during a run. Once triggered, bisync will use best efforts to exit cleanly before the timer runs out. If bisync is in the middle of transferring files, it will attempt to cleanly empty its queue by finishing what it has started but not taking more. If it cannot do so within 30 seconds, it will cancel the in-progress transfers at that point and then give itself a maximum of 60 seconds to wrap up, save its state for next time, and exit. With the <code>-vP</code> flags you will see constant status updates and a final confirmation of whether or not the graceful shutdown was successful.</p>
<p>At any point during the "Graceful Shutdown" sequence, a second <code>SIGINT</code> or <code>Ctrl+C</code> will trigger an immediate, un-graceful exit, which will leave things in a messier state. Usually a robust recovery will still be possible if using <a href="#recover"><code>--recover</code></a> mode, otherwise you will need to do a <code>--resync</code>.</p>
<p>If you plan to use Graceful Shutdown mode, it is recommended to use <a href="#resilient"><code>--resilient</code></a> and <a href="#recover"><code>--recover</code></a>, and it is important to NOT use <a href="https://rclone.org/docs/#inplace"><code>--inplace</code></a>, otherwise you risk leaving partially-written files on one side, which may be confused for real files on the next run. Note also that in the event of an abrupt interruption, a <a href="#lock-file">lock file</a> will be left behind to block concurrent runs. You will need to delete it before you can proceed with the next run (or wait for it to expire on its own, if using <code>--max-lock</code>.)</p>
<h2 id="limitations-4">Limitations</h2>
<h3 id="supported-backends">Supported backends</h3>
<p>Bisync is considered <em>BETA</em> and has been tested with the following backends: - Local filesystem - Google Drive - Dropbox - OneDrive - S3 - SFTP - Yandex Disk - Crypt</p>
<p>It has not been fully tested with other services yet. If it works, or sorta works, please let us know and we'll update the list. Run the test suite to check for proper operation as described below.</p>
<p>The first release of <code>rclone bisync</code> required both underlying backends to support modification times, and refused to run otherwise. This limitation has been lifted as of <code>v1.66</code>, as bisync now supports comparing checksum and/or size instead of (or in addition to) modtime. See <a href="#compare"><code>--compare</code></a> for details.</p>
<h3 id="concurrent-modifications">Concurrent modifications</h3>
<p>When using <strong>Local, FTP or SFTP</strong> remotes with <a href="https://rclone.org/docs/#inplace"><code>--inplace</code></a>, rclone does not create <em>temporary</em> files at the destination when copying, and thus if the connection is lost the created file may be corrupt, which will likely propagate back to the original path on the next sync, resulting in data loss. It is therefore recommended to <em>omit</em> <code>--inplace</code>.</p>
<p>Files that <strong>change during</strong> a bisync run may result in data loss. Prior to <code>rclone v1.66</code>, this was commonly seen in highly dynamic environments, where the filesystem was getting hammered by running processes during the sync. As of <code>rclone v1.66</code>, bisync was redesigned to use a "snapshot" model, greatly reducing the risks from changes during a sync. Changes that are not detected during the current sync will now be detected during the following sync, and will no longer cause the entire run to throw a critical error. There is additionally a mechanism to mark files as needing to be internally rechecked next time, for added safety. It should therefore no longer be necessary to sync only at quiet times -- however, note that an error can still occur if a file happens to change at the exact moment it's being read/written by bisync (same as would happen in <code>rclone sync</code>.) (See also: <a href="https://rclone.org/docs/#ignore-checksum"><code>--ignore-checksum</code></a>, <a href="https://rclone.org/local/#local-no-check-updated"><code>--local-no-check-updated</code></a>)</p>
<h3 id="empty-directories">Empty directories</h3>
<p>By default, new/deleted empty directories on one path are <em>not</em> propagated to the other side. This is because bisync (and rclone) natively works on files, not directories. However, this can be changed with the <code>--create-empty-src-dirs</code> flag, which works in much the same way as in <a href="https://rclone.org/commands/rclone_sync/"><code>sync</code></a> and <a href="https://rclone.org/commands/rclone_copy/"><code>copy</code></a>. When used, empty directories created or deleted on one side will also be created or deleted on the other side. The following should be noted: * <code>--create-empty-src-dirs</code> is not compatible with <code>--remove-empty-dirs</code>. Use only one or the other (or neither). * It is not recommended to switch back and forth between <code>--create-empty-src-dirs</code> and the default (no <code>--create-empty-src-dirs</code>) without running <code>--resync</code>. This is because it may appear as though all directories (not just the empty ones) were created/deleted, when actually you've just toggled between making them visible/invisible to bisync. It looks scarier than it is, but it's still probably best to stick to one or the other, and use <code>--resync</code> when you need to switch.</p>
<h3 id="renamed-directories">Renamed directories</h3>
<p>By default, renaming a folder on the Path1 side results in deleting all files on the Path2 side and then copying all files again from Path1 to Path2. Bisync sees this as all files in the old directory name as deleted and all files in the new directory name as new.</p>
<p>A recommended solution is to use <a href="https://rclone.org/docs/#track-renames"><code>--track-renames</code></a>, which is now supported in bisync as of <code>rclone v1.66</code>. Note that <code>--track-renames</code> is not available during <code>--resync</code>, as <code>--resync</code> does not delete anything (<code>--track-renames</code> only supports <code>sync</code>, not <code>copy</code>.)</p>
<p>Otherwise, the most effective and efficient method of renaming a directory is to rename it to the same name on both sides. (As of <code>rclone v1.64</code>, a <code>--resync</code> is no longer required after doing so, as bisync will automatically detect that Path1 and Path2 are in agreement.)</p>
<h3 id="fast-list-used-by-default"><code>--fast-list</code> used by default</h3>
<p>Unlike most other rclone commands, bisync uses <a href="https://rclone.org/docs/#fast-list"><code>--fast-list</code></a> by default, for backends that support it. In many cases this is desirable, however, there are some scenarios in which bisync could be faster <em>without</em> <code>--fast-list</code>, and there is also a <a href="https://github.com/rclone/rclone/commit/cbf3d4356135814921382dd3285d859d15d0aa77">known issue concerning Google Drive users with many empty directories</a>. For now, the recommended way to avoid using <code>--fast-list</code> is to add <code>--disable ListR</code> to all bisync commands. The default behavior may change in a future version.</p>
<h3 id="case-sensitivity">Case (and unicode) sensitivity</h3>
<p>As of <code>v1.66</code>, case and unicode form differences no longer cause critical errors, and normalization (when comparing between filesystems) is handled according to the same flags and defaults as <code>rclone sync</code>. See the following options (all of which are supported by bisync) to control this behavior more granularly: - <a href="https://rclone.org/docs/#fix-case"><code>--fix-case</code></a> - <a href="https://rclone.org/docs/#ignore-case-sync"><code>--ignore-case-sync</code></a> - <a href="https://rclone.org/docs/#no-unicode-normalization"><code>--no-unicode-normalization</code></a> - <a href="https://rclone.org/local/#local-unicode-normalization"><code>--local-unicode-normalization</code></a> and <a href="https://rclone.org/local/#local-case-sensitive"><code>--local-case-sensitive</code></a> (caution: these are normally not what you want.)</p>
<p>Note that in the (probably rare) event that <code>--fix-case</code> is used AND a file is new/changed on both sides AND the checksums match AND the filename case does not match, the Path1 filename is considered the winner, for the purposes of <code>--fix-case</code> (Path2 will be renamed to match it).</p>
<h2 id="windows">Windows support</h2>
<p>Bisync has been tested on Windows 8.1, Windows 10 Pro 64-bit and on Windows GitHub runners.</p>
<p>Drive letters are allowed, including drive letters mapped to network drives (<code>rclone bisync J:\localsync GDrive:</code>). If a drive letter is omitted, the shell current drive is the default. Drive letters are a single character follows by <code>:</code>, so cloud names must be more than one character long.</p>
<p>Absolute paths (with or without a drive letter), and relative paths (with or without a drive letter) are supported.</p>
<p>Working directory is created at <code>C:\Users\MyLogin\AppData\Local\rclone\bisync</code>.</p>
<p>Note that bisync output may show a mix of forward <code>/</code> and back <code>\</code> slashes.</p>
<p>Be careful of case independent directory and file naming on Windows vs. case dependent Linux</p>
<h2 id="filtering">Filtering</h2>
<p>See <a href="https://rclone.org/filtering/">filtering documentation</a> for how filter rules are written and interpreted.</p>
<p>Bisync's <a href="#filters-file"><code>--filters-file</code></a> flag slightly extends the rclone's <a href="https://rclone.org/filtering/#filter-from-read-filtering-patterns-from-a-file">--filter-from</a> filtering mechanism. For a given bisync run you may provide <em>only one</em> <code>--filters-file</code>. The <code>--include*</code>, <code>--exclude*</code>, and <code>--filter</code> flags are also supported.</p>
<h3 id="how-to-filter-directories">How to filter directories</h3>
<p>Filtering portions of the directory tree is a critical feature for synching.</p>
<p>Examples of directory trees (always beneath the Path1/Path2 root level) you may want to exclude from your sync: - Directory trees containing only software build intermediate files. - Directory trees containing application temporary files and data such as the Windows <code>C:\Users\MyLogin\AppData\</code> tree. - Directory trees containing files that are large, less important, or are getting thrashed continuously by ongoing processes.</p>
<p>On the other hand, there may be only select directories that you actually want to sync, and exclude all others. See the <a href="#include-filters">Example include-style filters for Windows user directories</a> below.</p>
<h3 id="filters-file-writing-guidelines">Filters file writing guidelines</h3>
<ol type="1">
<li>Begin with excluding directory trees:
<ul>
<li>e.g. `- /AppData/`</li>
<li><code>**</code> on the end is not necessary. Once a given directory level is excluded then everything beneath it won't be looked at by rclone.</li>
<li>Exclude such directories that are unneeded, are big, dynamically thrashed, or where there may be access permission issues.</li>
<li>Excluding such dirs first will make rclone operations (much) faster.</li>
<li>Specific files may also be excluded, as with the Dropbox exclusions example below.</li>
</ul></li>
<li>Decide if it's easier (or cleaner) to:
<ul>
<li>Include select directories and therefore <em>exclude everything else</em> -- or --</li>
<li>Exclude select directories and therefore <em>include everything else</em></li>
</ul></li>
<li>Include select directories:
<ul>
<li>Add lines like: `+ /Documents/PersonalFiles/**` to select which directories to include in the sync.</li>
<li><code>**</code> on the end specifies to include the full depth of the specified tree.</li>
<li>With Include-style filters, files at the Path1/Path2 root are not included. They may be included with `+ /*`.</li>
<li>Place RCLONE_TEST files within these included directory trees. They will only be looked for in these directory trees.</li>
<li>Finish by excluding everything else by adding `- **` at the end of the filters file.</li>
<li>Disregard step 4.</li>
</ul></li>
<li>Exclude select directories:
<ul>
<li>Add more lines like in step 1. For example: <code>-/Desktop/tempfiles/</code>, or `- /testdir/<code>.    Again, a</code>**` on the end is not necessary.</li>
<li>Do <em>not</em> add a `- **` in the file. Without this line, everything will be included that has not been explicitly excluded.</li>
<li>Disregard step 3.</li>
</ul></li>
</ol>
<p>A few rules for the syntax of a filter file expanding on <a href="https://rclone.org/filtering/">filtering documentation</a>:</p>
<ul>
<li>Lines may start with spaces and tabs - rclone strips leading whitespace.</li>
<li>If the first non-whitespace character is a <code>#</code> then the line is a comment and will be ignored.</li>
<li>Blank lines are ignored.</li>
<li>The first non-whitespace character on a filter line must be a <code>+</code> or <code>-</code>.</li>
<li>Exactly 1 space is allowed between the <code>+/-</code> and the path term.</li>
<li>Only forward slashes (<code>/</code>) are used in path terms, even on Windows.</li>
<li>The rest of the line is taken as the path term. Trailing whitespace is taken literally, and probably is an error.</li>
</ul>
<h3 id="include-filters">Example include-style filters for Windows user directories</h3>
<p>This Windows <em>include-style</em> example is based on the sync root (Path1) set to <code>C:\Users\MyLogin</code>. The strategy is to select specific directories to be synched with a network drive (Path2).</p>
<ul>
<li>`- /AppData/` excludes an entire tree of Windows stored stuff that need not be synched. In my case, AppData has &gt;11 GB of stuff I don't care about, and there are some subdirectories beneath AppData that are not accessible to my user login, resulting in bisync critical aborts.</li>
<li>Windows creates cache files starting with both upper and lowercase <code>NTUSER</code> at <code>C:\Users\MyLogin</code>. These files may be dynamic, locked, and are generally <em>don't care</em>.</li>
<li>There are just a few directories with <em>my</em> data that I do want synched, in the form of `+ /<path><code>. By selecting only the directory trees I   want to avoid the dozen plus directories that various apps make   at</code>C:`.</li>
<li>Include files in the root of the sync point, <code>C:\Users\MyLogin</code>, by adding the `+ /*` line.</li>
<li>This is an Include-style filters file, therefore it ends with `- **` which excludes everything not explicitly included.</li>
</ul>
<pre><code>- /AppData/
- NTUSER*
- ntuser*
+ /Documents/Family/**
+ /Documents/Sketchup/**
+ /Documents/Microcapture_Photo/**
+ /Documents/Microcapture_Video/**
+ /Desktop/**
+ /Pictures/**
+ /*
- **</code></pre>
<p>Note also that Windows implements several "library" links such as <code>C:\Users\MyLogin\My Documents\My Music</code> pointing to <code>C:\Users\MyLogin\Music</code>. rclone sees these as links, so you must add <code>--links</code> to the bisync command line if you which to follow these links. I find that I get permission errors in trying to follow the links, so I don't include the rclone <code>--links</code> flag, but then you get lots of <code>Can't follow symlink…</code> noise from rclone about not following the links. This noise can be quashed by adding <code>--quiet</code> to the bisync command line.</p>
<h2 id="exclude-filters">Example exclude-style filters files for use with Dropbox</h2>
<ul>
<li>Dropbox disallows synching the listed temporary and configuration/data files. The `- <filename>` filters exclude these files where ever they may occur in the sync tree. Consider adding similar exclusions for file types you don't need to sync, such as core dump and software build files.</li>
<li>bisync testing creates <code>/testdir/</code> at the top level of the sync tree, and usually deletes the tree after the test. If a normal sync should run while the <code>/testdir/</code> tree exists the <code>--check-access</code> phase may fail due to unbalanced RCLONE_TEST files. The `- /testdir/` filter blocks this tree from being synched. You don't need this exclusion if you are not doing bisync development testing.</li>
<li>Everything else beneath the Path1/Path2 root will be synched.</li>
<li>RCLONE_TEST files may be placed anywhere within the tree, including the root.</li>
</ul>
<h3 id="example-filters-file">Example filters file for Dropbox</h3>
<pre><code># Filter file for use with bisync
# See https://rclone.org/filtering/ for filtering rules
# NOTICE: If you make changes to this file you MUST do a --resync run.
#         Run with --dry-run to see what changes will be made.

# Dropbox won&#39;t sync some files so filter them away here.
# See https://help.dropbox.com/installs-integrations/sync-uploads/files-not-syncing
- .dropbox.attr
- ~*.tmp
- ~$*
- .~*
- desktop.ini
- .dropbox

# Used for bisync testing, so excluded from normal runs
- /testdir/

# Other example filters
#- /TiBU/
#- /Photos/</code></pre>
<h3 id="how---check-access-handles-filters">How --check-access handles filters</h3>
<p>At the start of a bisync run, listings are gathered for Path1 and Path2 while using the user's <code>--filters-file</code>. During the check access phase, bisync scans these listings for <code>RCLONE_TEST</code> files. Any <code>RCLONE_TEST</code> files hidden by the <code>--filters-file</code> are <em>not</em> in the listings and thus not checked during the check access phase.</p>
<h2 id="troubleshooting">Troubleshooting</h2>
<h3 id="reading-bisync-logs">Reading bisync logs</h3>
<p>Here are two normal runs. The first one has a newer file on the remote. The second has no deltas between local and remote.</p>
<pre><code>2021/05/16 00:24:38 INFO  : Synching Path1 &quot;/path/to/local/tree/&quot; with Path2 &quot;dropbox:/&quot;
2021/05/16 00:24:38 INFO  : Path1 checking for diffs
2021/05/16 00:24:38 INFO  : - Path1    File is new                         - file.txt
2021/05/16 00:24:38 INFO  : Path1:    1 changes:    1 new,    0 newer,    0 older,    0 deleted
2021/05/16 00:24:38 INFO  : Path2 checking for diffs
2021/05/16 00:24:38 INFO  : Applying changes
2021/05/16 00:24:38 INFO  : - Path1    Queue copy to Path2                 - dropbox:/file.txt
2021/05/16 00:24:38 INFO  : - Path1    Do queued copies to                 - Path2
2021/05/16 00:24:38 INFO  : Updating listings
2021/05/16 00:24:38 INFO  : Validating listings for Path1 &quot;/path/to/local/tree/&quot; vs Path2 &quot;dropbox:/&quot;
2021/05/16 00:24:38 INFO  : Bisync successful

2021/05/16 00:36:52 INFO  : Synching Path1 &quot;/path/to/local/tree/&quot; with Path2 &quot;dropbox:/&quot;
2021/05/16 00:36:52 INFO  : Path1 checking for diffs
2021/05/16 00:36:52 INFO  : Path2 checking for diffs
2021/05/16 00:36:52 INFO  : No changes found
2021/05/16 00:36:52 INFO  : Updating listings
2021/05/16 00:36:52 INFO  : Validating listings for Path1 &quot;/path/to/local/tree/&quot; vs Path2 &quot;dropbox:/&quot;
2021/05/16 00:36:52 INFO  : Bisync successful</code></pre>
<h3 id="dry-run-oddity">Dry run oddity</h3>
<p>The <code>--dry-run</code> messages may indicate that it would try to delete some files. For example, if a file is new on Path2 and does not exist on Path1 then it would normally be copied to Path1, but with <code>--dry-run</code> enabled those copies don't happen, which leads to the attempted delete on Path2, blocked again by --dry-run: <code>... Not deleting as --dry-run</code>.</p>
<p>This whole confusing situation is an artifact of the <code>--dry-run</code> flag. Scrutinize the proposed deletes carefully, and if the files would have been copied to Path1 then the threatened deletes on Path2 may be disregarded.</p>
<h3 id="retries">Retries</h3>
<p>Rclone has built-in retries. If you run with <code>--verbose</code> you'll see error and retry messages such as shown below. This is usually not a bug. If at the end of the run, you see <code>Bisync successful</code> and not <code>Bisync critical error</code> or <code>Bisync aborted</code> then the run was successful, and you can ignore the error messages.</p>
<p>The following run shows an intermittent fail. Lines <em>5</em> and _6- are low-level messages. Line <em>6</em> is a bubbled-up <em>warning</em> message, conveying the error. Rclone normally retries failing commands, so there may be numerous such messages in the log.</p>
<p>Since there are no final error/warning messages on line <em>7</em>, rclone has recovered from failure after a retry, and the overall sync was successful.</p>
<pre><code>1: 2021/05/14 00:44:12 INFO  : Synching Path1 &quot;/path/to/local/tree&quot; with Path2 &quot;dropbox:&quot;
2: 2021/05/14 00:44:12 INFO  : Path1 checking for diffs
3: 2021/05/14 00:44:12 INFO  : Path2 checking for diffs
4: 2021/05/14 00:44:12 INFO  : Path2:  113 changes:   22 new,    0 newer,    0 older,   91 deleted
5: 2021/05/14 00:44:12 ERROR : /path/to/local/tree/objects/af: error listing: unexpected end of JSON input
6: 2021/05/14 00:44:12 NOTICE: WARNING  listing try 1 failed.                 - dropbox:
7: 2021/05/14 00:44:12 INFO  : Bisync successful</code></pre>
<p>This log shows a <em>Critical failure</em> which requires a <code>--resync</code> to recover from. See the <a href="#error-handling">Runtime Error Handling</a> section.</p>
<pre><code>2021/05/12 00:49:40 INFO  : Google drive root &#39;&#39;: Waiting for checks to finish
2021/05/12 00:49:40 INFO  : Google drive root &#39;&#39;: Waiting for transfers to finish
2021/05/12 00:49:40 INFO  : Google drive root &#39;&#39;: not deleting files as there were IO errors
2021/05/12 00:49:40 ERROR : Attempt 3/3 failed with 3 errors and: not deleting files as there were IO errors
2021/05/12 00:49:40 ERROR : Failed to sync: not deleting files as there were IO errors
2021/05/12 00:49:40 NOTICE: WARNING  rclone sync try 3 failed.           - /path/to/local/tree/
2021/05/12 00:49:40 ERROR : Bisync aborted. Must run --resync to recover.</code></pre>
<h3 id="denied-downloads-of-infected-or-abusive-files">Denied downloads of "infected" or "abusive" files</h3>
<p>Google Drive has a filter for certain file types (<code>.exe</code>, <code>.apk</code>, et cetera) that by default cannot be copied from Google Drive to the local filesystem. If you are having problems, run with <code>--verbose</code> to see specifically which files are generating complaints. If the error is <code>This file has been identified as malware or spam and cannot be downloaded</code>, consider using the flag <a href="https://rclone.org/drive/#drive-acknowledge-abuse">--drive-acknowledge-abuse</a>.</p>
<h3 id="gdocs">Google Docs (and other files of unknown size)</h3>
<p>As of <code>v1.66</code>, <a href="https://rclone.org/drive/#import-export-of-google-documents">Google Docs</a> (including Google Sheets, Slides, etc.) are now supported in bisync, subject to the same options, defaults, and limitations as in <code>rclone sync</code>. When bisyncing drive with non-drive backends, the drive -&gt; non-drive direction is controlled by <a href="https://rclone.org/drive/#drive-export-formats"><code>--drive-export-formats</code></a> (default <code>"docx,xlsx,pptx,svg"</code>) and the non-drive -&gt; drive direction is controlled by <a href="https://rclone.org/drive/#drive-import-formats"><code>--drive-import-formats</code></a> (default none.)</p>
<p>For example, with the default export/import formats, a Google Sheet on the drive side will be synced to an <code>.xlsx</code> file on the non-drive side. In the reverse direction, <code>.xlsx</code> files with filenames that match an existing Google Sheet will be synced to that Google Sheet, while <code>.xlsx</code> files that do NOT match an existing Google Sheet will be copied to drive as normal <code>.xlsx</code> files (without conversion to Sheets, although the Google Drive web browser UI may still give you the option to open it as one.)</p>
<p>If <code>--drive-import-formats</code> is set (it's not, by default), then all of the specified formats will be converted to Google Docs, if there is no existing Google Doc with a matching name. Caution: such conversion can be quite lossy, and in most cases it's probably not what you want!</p>
<p>To bisync Google Docs as URL shortcut links (in a manner similar to "Drive for Desktop"), use: <code>--drive-export-formats url</code> (or <a href="https://rclone.org/drive/#exportformats:~:text=available%20Google%20Documents.-,Extension,macOS,-Standard%20options">alternatives</a>.)</p>
<p>Note that these link files cannot be edited on the non-drive side -- you will get errors if you try to sync an edited link file back to drive. They CAN be deleted (it will result in deleting the corresponding Google Doc.) If you create a <code>.url</code> file on the non-drive side that does not match an existing Google Doc, bisyncing it will just result in copying the literal <code>.url</code> file over to drive (no Google Doc will be created.) So, as a general rule of thumb, think of them as read-only placeholders on the non-drive side, and make all your changes on the drive side.</p>
<p>Likewise, even with other export-formats, it is best to only move/rename Google Docs on the drive side. This is because otherwise, bisync will interpret this as a file deleted and another created, and accordingly, it will delete the Google Doc and create a new file at the new path. (Whether or not that new file is a Google Doc depends on <code>--drive-import-formats</code>.)</p>
<p>Lastly, take note that all Google Docs on the drive side have a size of <code>-1</code> and no checksum. Therefore, they cannot be reliably synced with the <code>--checksum</code> or <code>--size-only</code> flags. (To be exact: they will still get created/deleted, and bisync's delta engine will notice changes and queue them for syncing, but the underlying sync function will consider them identical and skip them.) To work around this, use the default (modtime and size) instead of <code>--checksum</code> or <code>--size-only</code>.</p>
<p>To ignore Google Docs entirely, use <a href="https://rclone.org/drive/#drive-skip-gdocs"><code>--drive-skip-gdocs</code></a>.</p>
<h2 id="usage-examples">Usage examples</h2>
<h3 id="cron">Cron</h3>
<p>Rclone does not yet have a built-in capability to monitor the local file system for changes and must be blindly run periodically. On Windows this can be done using a <em>Task Scheduler</em>, on Linux you can use <em>Cron</em> which is described below.</p>
<p>The 1st example runs a sync every 5 minutes between a local directory and an OwnCloud server, with output logged to a runlog file:</p>
<pre><code># Minute (0-59)
#      Hour (0-23)
#           Day of Month (1-31)
#                Month (1-12 or Jan-Dec)
#                     Day of Week (0-6 or Sun-Sat)
#                         Command
  */5  *    *    *    *   /path/to/rclone bisync /local/files MyCloud: --check-access --filters-file /path/to/bysync-filters.txt --log-file /path/to//bisync.log</code></pre>
<p>See <a href="https://www.man7.org/linux/man-pages/man1/crontab.1p.html#INPUT_FILES">crontab syntax</a> for the details of crontab time interval expressions.</p>
<p>If you run <code>rclone bisync</code> as a cron job, redirect stdout/stderr to a file. The 2nd example runs a sync to Dropbox every hour and logs all stdout (via the <code>&gt;&gt;</code>) and stderr (via <code>2&gt;&amp;1</code>) to a log file.</p>
<pre><code>0 * * * * /path/to/rclone bisync /path/to/local/dropbox Dropbox: --check-access --filters-file /home/user/filters.txt &gt;&gt; /path/to/logs/dropbox-run.log 2&gt;&amp;1</code></pre>
<h3 id="sharing-an-encrypted-folder-tree-between-hosts">Sharing an encrypted folder tree between hosts</h3>
<p>bisync can keep a local folder in sync with a cloud service, but what if you have some highly sensitive files to be synched?</p>
<p>Usage of a cloud service is for exchanging both routine and sensitive personal files between one's home network, one's personal notebook when on the road, and with one's work computer. The routine data is not sensitive. For the sensitive data, configure an rclone <a href="https://rclone.org/crypt/">crypt remote</a> to point to a subdirectory within the local disk tree that is bisync'd to Dropbox, and then set up an bisync for this local crypt directory to a directory outside of the main sync tree.</p>
<h3 id="linux-server-setup">Linux server setup</h3>
<ul>
<li><code>/path/to/DBoxroot</code> is the root of my local sync tree. There are numerous subdirectories.</li>
<li><code>/path/to/DBoxroot/crypt</code> is the root subdirectory for files that are encrypted. This local directory target is setup as an rclone crypt remote named <code>Dropcrypt:</code>. See <a href="#rclone-conf-snippet">rclone.conf</a> snippet below.</li>
<li><code>/path/to/my/unencrypted/files</code> is the root of my sensitive files - not encrypted, not within the tree synched to Dropbox.</li>
<li>To sync my local unencrypted files with the encrypted Dropbox versions I manually run <code>bisync /path/to/my/unencrypted/files DropCrypt:</code>. This step could be bundled into a script to run before and after the full Dropbox tree sync in the last step, thus actively keeping the sensitive files in sync.</li>
<li><code>bisync /path/to/DBoxroot Dropbox:</code> runs periodically via cron, keeping my full local sync tree in sync with Dropbox.</li>
</ul>
<h3 id="windows-notebook-setup">Windows notebook setup</h3>
<ul>
<li>The Dropbox client runs keeping the local tree <code>C:\Users\MyLogin\Dropbox</code> always in sync with Dropbox. I could have used <code>rclone bisync</code> instead.</li>
<li>A separate directory tree at <code>C:\Users\MyLogin\Documents\DropLocal</code> hosts the tree of unencrypted files/folders.</li>
<li>To sync my local unencrypted files with the encrypted Dropbox versions I manually run the following command: <code>rclone bisync C:\Users\MyLogin\Documents\DropLocal Dropcrypt:</code>.</li>
<li>The Dropbox client then syncs the changes with Dropbox.</li>
</ul>
<h3 id="rclone-conf-snippet">rclone.conf snippet</h3>
<pre><code>[Dropbox]
type = dropbox
...

[Dropcrypt]
type = crypt
remote = /path/to/DBoxroot/crypt          # on the Linux server
remote = C:\Users\MyLogin\Dropbox\crypt   # on the Windows notebook
filename_encryption = standard
directory_name_encryption = true
password = ...
...</code></pre>
<h2 id="testing">Testing</h2>
<p>You should read this section only if you are developing for rclone. You need to have rclone source code locally to work with bisync tests.</p>
<p>Bisync has a dedicated test framework implemented in the <code>bisync_test.go</code> file located in the rclone source tree. The test suite is based on the <code>go test</code> command. Series of tests are stored in subdirectories below the <code>cmd/bisync/testdata</code> directory. Individual tests can be invoked by their directory name, e.g. <code>go test . -case basic -remote local -remote2 gdrive: -v</code></p>
<p>Tests will make a temporary folder on remote and purge it afterwards. If during test run there are intermittent errors and rclone retries, these errors will be captured and flagged as invalid MISCOMPAREs. Rerunning the test will let it pass. Consider such failures as noise.</p>
<h3 id="test-command-syntax">Test command syntax</h3>
<pre><code>usage: go test ./cmd/bisync [options...]

Options:
  -case NAME        Name(s) of the test case(s) to run. Multiple names should
                    be separated by commas. You can remove the `test_` prefix
                    and replace `_` by `-` in test name for convenience.
                    If not `all`, the name(s) should map to a directory under
                    `./cmd/bisync/testdata`.
                    Use `all` to run all tests (default: all)
  -remote PATH1     `local` or name of cloud service with `:` (default: local)
  -remote2 PATH2    `local` or name of cloud service with `:` (default: local)
  -no-compare       Disable comparing test results with the golden directory
                    (default: compare)
  -no-cleanup       Disable cleanup of Path1 and Path2 testdirs.
                    Useful for troubleshooting. (default: cleanup)
  -golden           Store results in the golden directory (default: false)
                    This flag can be used with multiple tests.
  -debug            Print debug messages
  -stop-at NUM      Stop test after given step number. (default: run to the end)
                    Implies `-no-compare` and `-no-cleanup`, if the test really
                    ends prematurely. Only meaningful for a single test case.
  -refresh-times    Force refreshing the target modtime, useful for Dropbox
                    (default: false)
  -verbose          Run tests verbosely</code></pre>
<p>Note: unlike rclone flags which must be prefixed by double dash (<code>--</code>), the test command flags can be equally prefixed by a single <code>-</code> or double dash.</p>
<h3 id="running-tests">Running tests</h3>
<ul>
<li><code>go test . -case basic -remote local -remote2 local</code> runs the <code>test_basic</code> test case using only the local filesystem, synching one local directory with another local directory. Test script output is to the console, while commands within scenario.txt have their output sent to the <code>.../workdir/test.log</code> file, which is finally compared to the golden copy.</li>
<li>The first argument after <code>go test</code> should be a relative name of the directory containing bisync source code. If you run tests right from there, the argument will be <code>.</code> (current directory) as in most examples below. If you run bisync tests from the rclone source directory, the command should be <code>go test ./cmd/bisync ...</code>.</li>
<li>The test engine will mangle rclone output to ensure comparability with golden listings and logs.</li>
<li>Test scenarios are located in <code>./cmd/bisync/testdata</code>. The test <code>-case</code> argument should match the full name of a subdirectory under that directory. Every test subdirectory name on disk must start with <code>test_</code>, this prefix can be omitted on command line for brevity. Also, underscores in the name can be replaced by dashes for convenience.</li>
<li><code>go test . -remote local -remote2 local -case all</code> runs all tests.</li>
<li>Path1 and Path2 may either be the keyword <code>local</code> or may be names of configured cloud services. <code>go test . -remote gdrive: -remote2 dropbox: -case basic</code> will run the test between these two services, without transferring any files to the local filesystem.</li>
<li>Test run stdout and stderr console output may be directed to a file, e.g. <code>go test . -remote gdrive: -remote2 local -case all &gt; runlog.txt 2&gt;&amp;1</code></li>
</ul>
<h3 id="test-execution-flow">Test execution flow</h3>
<ol type="1">
<li>The base setup in the <code>initial</code> directory of the testcase is applied on the Path1 and Path2 filesystems (via rclone copy the initial directory to Path1, then rclone sync Path1 to Path2).</li>
<li>The commands in the scenario.txt file are applied, with output directed to the <code>test.log</code> file in the test working directory. Typically, the first actual command in the <code>scenario.txt</code> file is to do a <code>--resync</code>, which establishes the baseline <code>{...}.path1.lst</code> and <code>{...}.path2.lst</code> files in the test working directory (<code>.../workdir/</code> relative to the temporary test directory). Various commands and listing snapshots are done within the test.</li>
<li>Finally, the contents of the test working directory are compared to the contents of the testcase's golden directory.</li>
</ol>
<h3 id="notes-about-testing">Notes about testing</h3>
<ul>
<li>Test cases are in individual directories beneath <code>./cmd/bisync/testdata</code>. A command line reference to a test is understood to reference a directory beneath <code>testdata</code>. For example, <code>go test ./cmd/bisync -case dry-run -remote gdrive: -remote2 local</code> refers to the test case in <code>./cmd/bisync/testdata/test_dry_run</code>.</li>
<li>The test working directory is located at <code>.../workdir</code> relative to a temporary test directory, usually under <code>/tmp</code> on Linux.</li>
<li>The local test sync tree is created at a temporary directory named like <code>bisync.XXX</code> under system temporary directory.</li>
<li>The remote test sync tree is located at a temporary directory under <code>&lt;remote:&gt;/bisync.XXX/</code>.</li>
<li><code>path1</code> and/or <code>path2</code> subdirectories are created in a temporary directory under the respective local or cloud test remote.</li>
<li>By default, the Path1 and Path2 test dirs and workdir will be deleted after each test run. The <code>-no-cleanup</code> flag disables purging these directories when validating and debugging a given test. These directories will be flushed before running another test, independent of the <code>-no-cleanup</code> usage.</li>
<li>You will likely want to add `- /testdir/<code>to your normal   bisync</code>--filters-file<code>so that normal syncs do not attempt to sync   the test temporary directories, which may have</code>RCLONE_TEST<code>miscompares   in some testcases which would otherwise trip the</code>--check-access<code>system.   The</code>--check-access<code>mechanism is hard-coded to ignore</code>RCLONE_TEST<code>files beneath</code>bisync/testdata`, so the test cases may reside on the synched tree even if there are check file mismatches in the test tree.</li>
<li>Some Dropbox tests can fail, notably printing the following message: <code>src and dst identical but can't set mod time without deleting and re-uploading</code> This is expected and happens due to the way Dropbox handles modification times. You should use the <code>-refresh-times</code> test flag to make up for this.</li>
<li>If Dropbox tests hit request limit for you and print error message <code>too_many_requests/...: Too many requests or write operations.</code> then follow the <a href="https://rclone.org/dropbox/#get-your-own-dropbox-app-id">Dropbox App ID instructions</a>.</li>
</ul>
<h3 id="updating-golden-results">Updating golden results</h3>
<p>Sometimes even a slight change in the bisync source can cause little changes spread around many log files. Updating them manually would be a nightmare.</p>
<p>The <code>-golden</code> flag will store the <code>test.log</code> and <code>*.lst</code> listings from each test case into respective golden directories. Golden results will automatically contain generic strings instead of local or cloud paths which means that they should match when run with a different cloud service.</p>
<p>Your normal workflow might be as follows: 1. Git-clone the rclone sources locally 2. Modify bisync source and check that it builds 3. Run the whole test suite <code>go test ./cmd/bisync -remote local</code> 4. If some tests show log difference, recheck them individually, e.g.: <code>go test ./cmd/bisync -remote local -case basic</code> 5. If you are convinced with the difference, goldenize all tests at once: <code>go test ./cmd/bisync -remote local -golden</code> 6. Use word diff: <code>git diff --word-diff ./cmd/bisync/testdata/</code>. Please note that normal line-level diff is generally useless here. 7. Check the difference <em>carefully</em>! 8. Commit the change (<code>git commit</code>) <em>only</em> if you are sure. If unsure, save your code changes then wipe the log diffs from git: <code>git reset [--hard]</code>.</p>
<h3 id="structure-of-test-scenarios">Structure of test scenarios</h3>
<ul>
<li><code>&lt;testname&gt;/initial/</code> contains a tree of files that will be set as the initial condition on both Path1 and Path2 testdirs.</li>
<li><code>&lt;testname&gt;/modfiles/</code> contains files that will be used to modify the Path1 and/or Path2 filesystems.</li>
<li><code>&lt;testname&gt;/golden/</code> contains the expected content of the test working directory (<code>workdir</code>) at the completion of the testcase.</li>
<li><code>&lt;testname&gt;/scenario.txt</code> contains the body of the test, in the form of various commands to modify files, run bisync, and snapshot listings. Output from these commands is captured to <code>.../workdir/test.log</code> for comparison to the golden files.</li>
</ul>
<h3 id="supported-test-commands">Supported test commands</h3>
<ul>
<li><code>test &lt;some message&gt;</code> Print the line to the console and to the <code>test.log</code>: <code>test sync is working correctly with options x, y, z</code></li>
<li><code>copy-listings &lt;prefix&gt;</code> Save a copy of all <code>.lst</code> listings in the test working directory with the specified prefix: <code>save-listings exclude-pass-run</code></li>
<li><code>move-listings &lt;prefix&gt;</code> Similar to <code>copy-listings</code> but removes the source</li>
<li><code>purge-children &lt;dir&gt;</code> This will delete all child files and purge all child subdirs under given directory but keep the parent intact. This behavior is important for tests with Google Drive because removing and re-creating the parent would change its ID.</li>
<li><code>delete-file &lt;file&gt;</code> Delete a single file.</li>
<li><code>delete-glob &lt;dir&gt; &lt;pattern&gt;</code> Delete a group of files located one level deep in the given directory with names matching a given glob pattern.</li>
<li><code>touch-glob YYYY-MM-DD &lt;dir&gt; &lt;pattern&gt;</code> Change modification time on a group of files.</li>
<li><code>touch-copy YYYY-MM-DD &lt;source-file&gt; &lt;dest-dir&gt;</code> Change file modification time then copy it to destination.</li>
<li><code>copy-file &lt;source-file&gt; &lt;dest-dir&gt;</code> Copy a single file to given directory.</li>
<li><code>copy-as &lt;source-file&gt; &lt;dest-file&gt;</code> Similar to above but destination must include both directory and the new file name at destination.</li>
<li><code>copy-dir &lt;src&gt; &lt;dst&gt;</code> and <code>sync-dir &lt;src&gt; &lt;dst&gt;</code> Copy/sync a directory. Equivalent of <code>rclone copy</code> and <code>rclone sync</code>.</li>
<li><code>list-dirs &lt;dir&gt;</code> Equivalent to <code>rclone lsf -R --dirs-only &lt;dir&gt;</code></li>
<li><code>bisync [options]</code> Runs bisync against <code>-remote</code> and <code>-remote2</code>.</li>
</ul>
<h3 id="supported-substitution-terms">Supported substitution terms</h3>
<ul>
<li><code>{testdir/}</code> - the root dir of the testcase</li>
<li><code>{datadir/}</code> - the <code>modfiles</code> dir under the testcase root</li>
<li><code>{workdir/}</code> - the temporary test working directory</li>
<li><code>{path1/}</code> - the root of the Path1 test directory tree</li>
<li><code>{path2/}</code> - the root of the Path2 test directory tree</li>
<li><code>{session}</code> - base name of the test listings</li>
<li><code>{/}</code> - OS-specific path separator</li>
<li><code>{spc}</code>, <code>{tab}</code>, <code>{eol}</code> - whitespace</li>
<li><code>{chr:HH}</code> - raw byte with given hexadecimal code</li>
</ul>
<p>Substitution results of the terms named like <code>{dir/}</code> will end with <code>/</code> (or backslash on Windows), so it is not necessary to include slash in the usage, for example <code>delete-file {path1/}file1.txt</code>.</p>
<h2 id="benchmarks">Benchmarks</h2>
<p><em>This section is work in progress.</em></p>
<p>Here are a few data points for scale, execution times, and memory usage.</p>
<p>The first set of data was taken between a local disk to Dropbox. The <a href="https://speedtest.net">speedtest.net</a> download speed was ~170 Mbps, and upload speed was ~10 Mbps. 500 files (~9.5 MB each) had been already synched. 50 files were added in a new directory, each ~9.5 MB, ~475 MB total.</p>
<table>
<colgroup>
<col style="width: 33%" />
<col style="width: 50%" />
<col style="width: 16%" />
</colgroup>
<thead>
<tr class="header">
<th>Change</th>
<th>Operations and times</th>
<th>Overall run time</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td>500 files synched (nothing to move)</td>
<td>1x listings for Path1 &amp; Path2</td>
<td>1.5 sec</td>
</tr>
<tr class="even">
<td>500 files synched with --check-access</td>
<td>1x listings for Path1 &amp; Path2</td>
<td>1.5 sec</td>
</tr>
<tr class="odd">
<td>50 new files on remote</td>
<td>Queued 50 copies down: 27 sec</td>
<td>29 sec</td>
</tr>
<tr class="even">
<td>Moved local dir</td>
<td>Queued 50 copies up: 410 sec, 50 deletes up: 9 sec</td>
<td>421 sec</td>
</tr>
<tr class="odd">
<td>Moved remote dir</td>
<td>Queued 50 copies down: 31 sec, 50 deletes down: &lt;1 sec</td>
<td>33 sec</td>
</tr>
<tr class="even">
<td>Delete local dir</td>
<td>Queued 50 deletes up: 9 sec</td>
<td>13 sec</td>
</tr>
</tbody>
</table>
<p>This next data is from a user's application. They had ~400GB of data over 1.96 million files being sync'ed between a Windows local disk and some remote cloud. The file full path length was on average 35 characters (which factors into load time and RAM required).</p>
<ul>
<li>Loading the prior listing into memory (1.96 million files, listing file size 140 MB) took ~30 sec and occupied about 1 GB of RAM.</li>
<li>Getting a fresh listing of the local file system (producing the 140 MB output file) took about XXX sec.</li>
<li>Getting a fresh listing of the remote file system (producing the 140 MB output file) took about XXX sec. The network download speed was measured at XXX Mb/s.</li>
<li>Once the prior and current Path1 and Path2 listings were loaded (a total of four to be loaded, two at a time), determining the deltas was pretty quick (a few seconds for this test case), and the transfer time for any files to be copied was dominated by the network bandwidth.</li>
</ul>
<h2 id="references">References</h2>
<p>rclone's bisync implementation was derived from the <a href="https://github.com/cjnaz/rclonesync-V2">rclonesync-V2</a> project, including documentation and test mechanisms, with <span class="citation" data-cites="cjnaz">[@cjnaz]</span>(https://github.com/cjnaz)'s full support and encouragement.</p>
<p><code>rclone bisync</code> is similar in nature to a range of other projects:</p>
<ul>
<li><a href="https://github.com/bcpierce00/unison">unison</a></li>
<li><a href="https://github.com/syncthing/syncthing">syncthing</a></li>
<li><a href="https://github.com/cjnaz/rclonesync-V2">cjnaz/rclonesync</a></li>
<li><a href="https://github.com/ConorWilliams/rsinc">ConorWilliams/rsinc</a></li>
<li><a href="https://github.com/Jwink3101/syncrclone">jwink3101/syncrclone</a></li>
<li><a href="https://github.com/DavideRossi/upback">DavideRossi/upback</a></li>
</ul>
<p>Bisync adopts the differential synchronization technique, which is based on keeping history of changes performed by both synchronizing sides. See the <em>Dual Shadow Method</em> section in <a href="https://neil.fraser.name/writing/sync/">Neil Fraser's article</a>.</p>
<p>Also note a number of academic publications by <a href="http://www.cis.upenn.edu/%7Ebcpierce/papers/index.shtml#File%20Synchronization">Benjamin Pierce</a> about <em>Unison</em> and synchronization in general.</p>
<h2 id="changelog">Changelog</h2>
<h3 id="v1.68"><code>v1.68</code></h3>
<ul>
<li>Fixed an issue affecting backends that round modtimes to a lower precision.</li>
</ul>
<h3 id="v1.67"><code>v1.67</code></h3>
<ul>
<li>Added integration tests against all backends.</li>
</ul>
<h3 id="v1.66"><code>v1.66</code></h3>
<ul>
<li>Copies and deletes are now handled in one operation instead of two</li>
<li><code>--track-renames</code> and <code>--backup-dir</code> are now supported</li>
<li>Partial uploads known issue on <code>local</code>/<code>ftp</code>/<code>sftp</code> has been resolved (unless using <code>--inplace</code>)</li>
<li>Final listings are now generated from sync results, to avoid needing to re-list</li>
<li>Bisync is now much more resilient to changes that happen during a bisync run, and far less prone to critical errors / undetected changes</li>
<li>Bisync is now capable of rolling a file listing back in cases of uncertainty, essentially marking the file as needing to be rechecked next time.</li>
<li>A few basic terminal colors are now supported, controllable with <a href="https://rclone.org/docs/#color-when"><code>--color</code></a> (<code>AUTO</code>|<code>NEVER</code>|<code>ALWAYS</code>)</li>
<li>Initial listing snapshots of Path1 and Path2 are now generated concurrently, using the same "march" infrastructure as <code>check</code> and <code>sync</code>, for performance improvements and less <a href="https://forum.rclone.org/t/bisync-bugs-and-feature-requests/37636#:~:text=4.%20Listings%20should%20alternate%20between%20paths%20to%20minimize%20errors">risk of error</a>.</li>
<li>Fixed handling of unicode normalization and case insensitivity, support for <a href="https://rclone.org/docs/#fix-case"><code>--fix-case</code></a>, <a href="/docs/#ignore-case-sync"><code>--ignore-case-sync</code></a>, <a href="/docs/#no-unicode-normalization"><code>--no-unicode-normalization</code></a></li>
<li><code>--resync</code> is now much more efficient (especially for users of <code>--create-empty-src-dirs</code>)</li>
<li>Google Docs (and other files of unknown size) are now supported (with the same options as in <code>sync</code>)</li>
<li>Equality checks before a sync conflict rename now fall back to <code>cryptcheck</code> (when possible) or <code>--download</code>, instead of of <code>--size-only</code>, when <code>check</code> is not available.</li>
<li>Bisync no longer fails to find the correct listing file when configs are overridden with backend-specific flags.</li>
<li>Bisync now fully supports comparing based on any combination of size, modtime, and checksum, lifting the prior restriction on backends without modtime support.</li>
<li>Bisync now supports a "Graceful Shutdown" mode to cleanly cancel a run early without requiring <code>--resync</code>.</li>
<li>New <code>--recover</code> flag allows robust recovery in the event of interruptions, without requiring <code>--resync</code>.</li>
<li>A new <code>--max-lock</code> setting allows lock files to automatically renew and expire, for better automatic recovery when a run is interrupted.</li>
<li>Bisync now supports auto-resolving sync conflicts and customizing rename behavior with new <a href="#conflict-resolve"><code>--conflict-resolve</code></a>, <a href="#conflict-loser"><code>--conflict-loser</code></a>, and <a href="#conflict-suffix"><code>--conflict-suffix</code></a> flags.</li>
<li>A new <a href="#resync-mode"><code>--resync-mode</code></a> flag allows more control over which version of a file gets kept during a <code>--resync</code>.</li>
<li>Bisync now supports <a href="https://rclone.org/docs/#retries-int"><code>--retries</code></a> and <a href="/docs/#retries-sleep-time"><code>--retries-sleep</code></a> (when <a href="#resilient"><code>--resilient</code></a> is set.)</li>
</ul>
<h3 id="v1.64"><code>v1.64</code></h3>
<ul>
<li>Fixed an <a href="https://forum.rclone.org/t/bisync-bugs-and-feature-requests/37636#:~:text=1.%20Dry%20runs%20are%20not%20completely%20dry">issue</a> causing dry runs to inadvertently commit filter changes</li>
<li>Fixed an <a href="https://forum.rclone.org/t/bisync-bugs-and-feature-requests/37636#:~:text=2.%20%2D%2Dresync%20deletes%20data%2C%20contrary%20to%20docs">issue</a> causing <code>--resync</code> to erroneously delete empty folders and duplicate files unique to Path2</li>
<li><code>--check-access</code> is now enforced during <code>--resync</code>, preventing data loss in <a href="https://forum.rclone.org/t/bisync-bugs-and-feature-requests/37636#:~:text=%2D%2Dcheck%2Daccess%20doesn%27t%20always%20fail%20when%20it%20should">certain user error scenarios</a></li>
<li>Fixed an <a href="https://forum.rclone.org/t/bisync-bugs-and-feature-requests/37636#:~:text=5.%20Bisync%20reads%20files%20in%20excluded%20directories%20during%20delete%20operations">issue</a> causing bisync to consider more files than necessary due to overbroad filters during delete operations</li>
<li><a href="https://forum.rclone.org/t/bisync-bugs-and-feature-requests/37636#:~:text=1.%20Identical%20files%20should%20be%20left%20alone%2C%20even%20if%20new/newer/changed%20on%20both%20sides">Improved detection of false positive change conflicts</a> (identical files are now left alone instead of renamed)</li>
<li>Added <a href="https://forum.rclone.org/t/bisync-bugs-and-feature-requests/37636#:~:text=3.%20Bisync%20should%20create/delete%20empty%20directories%20as%20sync%20does%2C%20when%20%2D%2Dcreate%2Dempty%2Dsrc%2Ddirs%20is%20passed">support for <code>--create-empty-src-dirs</code></a></li>
<li>Added experimental <code>--resilient</code> mode to allow <a href="https://forum.rclone.org/t/bisync-bugs-and-feature-requests/37636#:~:text=2.%20Bisync%20should%20be%20more%20resilient%20to%20self%2Dcorrectable%20errors">recovery from self-correctable errors</a></li>
<li>Added <a href="https://forum.rclone.org/t/bisync-bugs-and-feature-requests/37636#:~:text=6.%20%2D%2Dignore%2Dchecksum%20should%20be%20split%20into%20two%20flags%20for%20separate%20purposes">new <code>--ignore-listing-checksum</code> flag</a> to distinguish from <code>--ignore-checksum</code></li>
<li><a href="https://forum.rclone.org/t/bisync-bugs-and-feature-requests/37636#:~:text=6.%20Deletes%20take%20several%20times%20longer%20than%20copies">Performance improvements</a> for large remotes</li>
<li>Documentation and testing improvements</li>
</ul>
<h1 id="release-signing">Release signing</h1>
<p>The hashes of the binary artefacts of the rclone release are signed with a public PGP/GPG key. This can be verified manually as described below.</p>
<p>The same mechanism is also used by <a href="https://rclone.org/commands/rclone_selfupdate/">rclone selfupdate</a> to verify that the release has not been tampered with before the new update is installed. This checks the SHA256 hash and the signature with a public key compiled into the rclone binary.</p>
<h2 id="release-signing-key">Release signing key</h2>
<p>You may obtain the release signing key from:</p>
<ul>
<li>From <a href="/KEYS">KEYS</a> on this website - this file contains all past signing keys also.</li>
<li>The git repository hosted on GitHub - https://github.com/rclone/rclone/blob/master/docs/content/KEYS</li>
<li><code>gpg --keyserver hkps://keys.openpgp.org --search nick@craig-wood.com</code></li>
<li><code>gpg --keyserver hkps://keyserver.ubuntu.com --search nick@craig-wood.com</code></li>
<li>https://www.craig-wood.com/nick/pub/pgp-key.txt</li>
</ul>
<p>After importing the key, verify that the fingerprint of one of the keys matches: <code>FBF737ECE9F8AB18604BD2AC93935E02FF3B54FA</code> as this key is used for signing.</p>
<p>We recommend that you cross-check the fingerprint shown above through the domains listed below. By cross-checking the integrity of the fingerprint across multiple domains you can be confident that you obtained the correct key.</p>
<ul>
<li>The <a href="https://github.com/rclone/rclone/blob/master/docs/content/release_signing.md">source for this page on GitHub</a>.</li>
<li>Through DNS <code>dig key.rclone.org txt</code></li>
</ul>
<p>If you find anything that doesn't not match, please contact the developers at once.</p>
<h2 id="how-to-verify-the-release">How to verify the release</h2>
<p>In the release directory you will see the release files and some files called <code>MD5SUMS</code>, <code>SHA1SUMS</code> and <code>SHA256SUMS</code>.</p>
<pre><code>$ rclone lsf --http-url https://downloads.rclone.org/v1.63.1 :http:
MD5SUMS
SHA1SUMS
SHA256SUMS
rclone-v1.63.1-freebsd-386.zip
rclone-v1.63.1-freebsd-amd64.zip
...
rclone-v1.63.1-windows-arm64.zip
rclone-v1.63.1.tar.gz
version.txt</code></pre>
<p>The <code>MD5SUMS</code>, <code>SHA1SUMS</code> and <code>SHA256SUMS</code> contain hashes of the binary files in the release directory along with a signature.</p>
<p>For example:</p>
<pre><code>$ rclone cat --http-url https://downloads.rclone.org/v1.63.1 :http:SHA256SUMS
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

f6d1b2d7477475ce681bdce8cb56f7870f174cb6b2a9ac5d7b3764296ea4a113  rclone-v1.63.1-freebsd-386.zip
7266febec1f01a25d6575de51c44ddf749071a4950a6384e4164954dff7ac37e  rclone-v1.63.1-freebsd-amd64.zip
...
66ca083757fb22198309b73879831ed2b42309892394bf193ff95c75dff69c73  rclone-v1.63.1-windows-amd64.zip
bbb47c16882b6c5f2e8c1b04229378e28f68734c613321ef0ea2263760f74cd0  rclone-v1.63.1-windows-arm64.zip
-----BEGIN PGP SIGNATURE-----

iF0EARECAB0WIQT79zfs6firGGBL0qyTk14C/ztU+gUCZLVKJQAKCRCTk14C/ztU
+pZuAJ0XJ+QWLP/3jCtkmgcgc4KAwd/rrwCcCRZQ7E+oye1FPY46HOVzCFU3L7g=
=8qrL
-----END PGP SIGNATURE-----</code></pre>
<h3 id="download-the-files">Download the files</h3>
<p>The first step is to download the binary and SUMs file and verify that the SUMs you have downloaded match. Here we download <code>rclone-v1.63.1-windows-amd64.zip</code> - choose the binary (or binaries) appropriate to your architecture. We've also chosen the <code>SHA256SUMS</code> as these are the most secure. You could verify the other types of hash also for extra security. <code>rclone selfupdate</code> verifies just the <code>SHA256SUMS</code>.</p>
<pre><code>$ mkdir /tmp/check
$ cd /tmp/check
$ rclone copy --http-url https://downloads.rclone.org/v1.63.1 :http:SHA256SUMS .
$ rclone copy --http-url https://downloads.rclone.org/v1.63.1 :http:rclone-v1.63.1-windows-amd64.zip .</code></pre>
<h3 id="verify-the-signatures">Verify the signatures</h3>
<p>First verify the signatures on the SHA256 file.</p>
<p>Import the key. See above for ways to verify this key is correct.</p>
<pre><code>$ gpg --keyserver keyserver.ubuntu.com --receive-keys FBF737ECE9F8AB18604BD2AC93935E02FF3B54FA
gpg: key 93935E02FF3B54FA: public key &quot;Nick Craig-Wood &lt;nick@craig-wood.com&gt;&quot; imported
gpg: Total number processed: 1
gpg:               imported: 1</code></pre>
<p>Then check the signature:</p>
<pre><code>$ gpg --verify SHA256SUMS 
gpg: Signature made Mon 17 Jul 2023 15:03:17 BST
gpg:                using DSA key FBF737ECE9F8AB18604BD2AC93935E02FF3B54FA
gpg: Good signature from &quot;Nick Craig-Wood &lt;nick@craig-wood.com&gt;&quot; [ultimate]</code></pre>
<p>Verify the signature was good and is using the fingerprint shown above.</p>
<p>Repeat for <code>MD5SUMS</code> and <code>SHA1SUMS</code> if desired.</p>
<h3 id="verify-the-hashes">Verify the hashes</h3>
<p>Now that we know the signatures on the hashes are OK we can verify the binaries match the hashes, completing the verification.</p>
<pre><code>$ sha256sum -c SHA256SUMS 2&gt;&amp;1 | grep OK
rclone-v1.63.1-windows-amd64.zip: OK</code></pre>
<p>Or do the check with rclone</p>
<pre><code>$ rclone hashsum sha256 -C SHA256SUMS rclone-v1.63.1-windows-amd64.zip 
2023/09/11 10:53:58 NOTICE: SHA256SUMS: improperly formatted checksum line 0
2023/09/11 10:53:58 NOTICE: SHA256SUMS: improperly formatted checksum line 1
2023/09/11 10:53:58 NOTICE: SHA256SUMS: improperly formatted checksum line 49
2023/09/11 10:53:58 NOTICE: SHA256SUMS: 4 warning(s) suppressed...
= rclone-v1.63.1-windows-amd64.zip
2023/09/11 10:53:58 NOTICE: Local file system at /tmp/check: 0 differences found
2023/09/11 10:53:58 NOTICE: Local file system at /tmp/check: 1 matching files</code></pre>
<h3 id="verify-signatures-and-hashes-together">Verify signatures and hashes together</h3>
<p>You can verify the signatures and hashes in one command line like this:</p>
<pre><code>$ h=$(gpg --decrypt SHA256SUMS) &amp;&amp; echo &quot;$h&quot; | sha256sum - -c --ignore-missing
gpg: Signature made Mon 17 Jul 2023 15:03:17 BST
gpg:                using DSA key FBF737ECE9F8AB18604BD2AC93935E02FF3B54FA
gpg: Good signature from &quot;Nick Craig-Wood &lt;nick@craig-wood.com&gt;&quot; [ultimate]
gpg:                 aka &quot;Nick Craig-Wood &lt;nick@memset.com&gt;&quot; [unknown]
rclone-v1.63.1-windows-amd64.zip: OK</code></pre>
<h1 id="fichier">1Fichier</h1>
<p>This is a backend for the <a href="https://1fichier.com">1fichier</a> cloud storage service. Note that a Premium subscription is required to use the API.</p>
<p>Paths are specified as <code>remote:path</code></p>
<p>Paths may be as deep as required, e.g. <code>remote:directory/subdirectory</code>.</p>
<h2 id="configuration">Configuration</h2>
<p>The initial setup for 1Fichier involves getting the API key from the website which you need to do in your browser.</p>
<p>Here is an example of how to make a remote called <code>remote</code>. First run:</p>
<pre><code> rclone config</code></pre>
<p>This will guide you through an interactive setup process:</p>
<pre><code>No remotes found, make a new one?
n) New remote
s) Set configuration password
q) Quit config
n/s/q&gt; n
name&gt; remote
Type of storage to configure.
Enter a string value. Press Enter for the default (&quot;&quot;).
Choose a number from below, or type in your own value
[snip]
XX / 1Fichier
   \ &quot;fichier&quot;
[snip]
Storage&gt; fichier
** See help for fichier backend at: https://rclone.org/fichier/ **

Your API Key, get it from https://1fichier.com/console/params.pl
Enter a string value. Press Enter for the default (&quot;&quot;).
api_key&gt; example_key

Edit advanced config? (y/n)
y) Yes
n) No
y/n&gt; 
Remote config
Configuration complete.
Options:
- type: fichier
- api_key: example_key
Keep this &quot;remote&quot; remote?
y) Yes this is OK
e) Edit this remote
d) Delete this remote
y/e/d&gt; y</code></pre>
<p>Once configured you can then use <code>rclone</code> like this,</p>
<p>List directories in top level of your 1Fichier account</p>
<pre><code>rclone lsd remote:</code></pre>
<p>List all the files in your 1Fichier account</p>
<pre><code>rclone ls remote:</code></pre>
<p>To copy a local directory to a 1Fichier directory called backup</p>
<pre><code>rclone copy /home/source remote:backup</code></pre>
<h3 id="modification-times-and-hashes">Modification times and hashes</h3>
<p>1Fichier does not support modification times. It supports the Whirlpool hash algorithm.</p>
<h3 id="duplicated-files">Duplicated files</h3>
<p>1Fichier can have two files with exactly the same name and path (unlike a normal file system).</p>
<p>Duplicated files cause problems with the syncing and you will see messages in the log about duplicates.</p>
<h3 id="restricted-filename-characters">Restricted filename characters</h3>
<p>In addition to the <a href="https://rclone.org/overview/#restricted-characters">default restricted characters set</a> the following characters are also replaced:</p>
<table>
<thead>
<tr class="header">
<th>Character</th>
<th style="text-align: center;">Value</th>
<th style="text-align: center;">Replacement</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td>\</td>
<td style="text-align: center;">0x5C</td>
<td style="text-align: center;">＼</td>
</tr>
<tr class="even">
<td>&lt;</td>
<td style="text-align: center;">0x3C</td>
<td style="text-align: center;">＜</td>
</tr>
<tr class="odd">
<td>&gt;</td>
<td style="text-align: center;">0x3E</td>
<td style="text-align: center;">＞</td>
</tr>
<tr class="even">
<td>"</td>
<td style="text-align: center;">0x22</td>
<td style="text-align: center;">＂</td>
</tr>
<tr class="odd">
<td>$</td>
<td style="text-align: center;">0x24</td>
<td style="text-align: center;">＄</td>
</tr>
<tr class="even">
<td>`</td>
<td style="text-align: center;">0x60</td>
<td style="text-align: center;">｀</td>
</tr>
<tr class="odd">
<td>'</td>
<td style="text-align: center;">0x27</td>
<td style="text-align: center;">＇</td>
</tr>
</tbody>
</table>
<p>File names can also not start or end with the following characters. These only get replaced if they are the first or last character in the name:</p>
<table>
<thead>
<tr class="header">
<th>Character</th>
<th style="text-align: center;">Value</th>
<th style="text-align: center;">Replacement</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td>SP</td>
<td style="text-align: center;">0x20</td>
<td style="text-align: center;">␠</td>
</tr>
</tbody>
</table>
<p>Invalid UTF-8 bytes will also be <a href="https://rclone.org/overview/#invalid-utf8">replaced</a>, as they can't be used in JSON strings.</p>
<h3 id="standard-options">Standard options</h3>
<p>Here are the Standard options specific to fichier (1Fichier).</p>
<h4 id="fichier-api-key">--fichier-api-key</h4>
<p>Your API Key, get it from https://1fichier.com/console/params.pl.</p>
<p>Properties:</p>
<ul>
<li>Config: api_key</li>
<li>Env Var: RCLONE_FICHIER_API_KEY</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h3 id="advanced-options">Advanced options</h3>
<p>Here are the Advanced options specific to fichier (1Fichier).</p>
<h4 id="fichier-shared-folder">--fichier-shared-folder</h4>
<p>If you want to download a shared folder, add this parameter.</p>
<p>Properties:</p>
<ul>
<li>Config: shared_folder</li>
<li>Env Var: RCLONE_FICHIER_SHARED_FOLDER</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="fichier-file-password">--fichier-file-password</h4>
<p>If you want to download a shared file that is password protected, add this parameter.</p>
<p><strong>NB</strong> Input to this must be obscured - see <a href="https://rclone.org/commands/rclone_obscure/">rclone obscure</a>.</p>
<p>Properties:</p>
<ul>
<li>Config: file_password</li>
<li>Env Var: RCLONE_FICHIER_FILE_PASSWORD</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="fichier-folder-password">--fichier-folder-password</h4>
<p>If you want to list the files in a shared folder that is password protected, add this parameter.</p>
<p><strong>NB</strong> Input to this must be obscured - see <a href="https://rclone.org/commands/rclone_obscure/">rclone obscure</a>.</p>
<p>Properties:</p>
<ul>
<li>Config: folder_password</li>
<li>Env Var: RCLONE_FICHIER_FOLDER_PASSWORD</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="fichier-cdn">--fichier-cdn</h4>
<p>Set if you wish to use CDN download links.</p>
<p>Properties:</p>
<ul>
<li>Config: cdn</li>
<li>Env Var: RCLONE_FICHIER_CDN</li>
<li>Type: bool</li>
<li>Default: false</li>
</ul>
<h4 id="fichier-encoding">--fichier-encoding</h4>
<p>The encoding for the backend.</p>
<p>See the <a href="https://rclone.org/overview/#encoding">encoding section in the overview</a> for more info.</p>
<p>Properties:</p>
<ul>
<li>Config: encoding</li>
<li>Env Var: RCLONE_FICHIER_ENCODING</li>
<li>Type: Encoding</li>
<li>Default: Slash,LtGt,DoubleQuote,SingleQuote,BackQuote,Dollar,BackSlash,Del,Ctl,LeftSpace,RightSpace,InvalidUtf8,Dot</li>
</ul>
<h4 id="fichier-description">--fichier-description</h4>
<p>Description of the remote.</p>
<p>Properties:</p>
<ul>
<li>Config: description</li>
<li>Env Var: RCLONE_FICHIER_DESCRIPTION</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h2 id="limitations-5">Limitations</h2>
<p><code>rclone about</code> is not supported by the 1Fichier backend. Backends without this capability cannot determine free space for an rclone mount or use policy <code>mfs</code> (most free space) as a member of an rclone union remote.</p>
<p>See <a href="https://rclone.org/overview/#optional-features">List of backends that do not support rclone about</a> and <a href="https://rclone.org/commands/rclone_about/">rclone about</a></p>
<h1 id="alias">Alias</h1>
<p>The <code>alias</code> remote provides a new name for another remote.</p>
<p>Paths may be as deep as required or a local path, e.g. <code>remote:directory/subdirectory</code> or <code>/directory/subdirectory</code>.</p>
<p>During the initial setup with <code>rclone config</code> you will specify the target remote. The target remote can either be a local path or another remote.</p>
<p>Subfolders can be used in target remote. Assume an alias remote named <code>backup</code> with the target <code>mydrive:private/backup</code>. Invoking <code>rclone mkdir backup:desktop</code> is exactly the same as invoking <code>rclone mkdir mydrive:private/backup/desktop</code>.</p>
<p>There will be no special handling of paths containing <code>..</code> segments. Invoking <code>rclone mkdir backup:../desktop</code> is exactly the same as invoking <code>rclone mkdir mydrive:private/backup/../desktop</code>. The empty path is not allowed as a remote. To alias the current directory use <code>.</code> instead.</p>
<p>The target remote can also be a <a href="https://rclone.org/docs/#connection-strings">connection string</a>. This can be used to modify the config of a remote for different uses, e.g. the alias <code>myDriveTrash</code> with the target remote <code>myDrive,trashed_only:</code> can be used to only show the trashed files in <code>myDrive</code>.</p>
<h2 id="configuration-1">Configuration</h2>
<p>Here is an example of how to make an alias called <code>remote</code> for local folder. First run:</p>
<pre><code> rclone config</code></pre>
<p>This will guide you through an interactive setup process:</p>
<pre><code>No remotes found, make a new one?
n) New remote
s) Set configuration password
q) Quit config
n/s/q&gt; n
name&gt; remote
Type of storage to configure.
Choose a number from below, or type in your own value
[snip]
XX / Alias for an existing remote
   \ &quot;alias&quot;
[snip]
Storage&gt; alias
Remote or path to alias.
Can be &quot;myremote:path/to/dir&quot;, &quot;myremote:bucket&quot;, &quot;myremote:&quot; or &quot;/local/path&quot;.
remote&gt; /mnt/storage/backup
Remote config
Configuration complete.
Options:
- type: alias
- remote: /mnt/storage/backup
Keep this &quot;remote&quot; remote?
y) Yes this is OK
e) Edit this remote
d) Delete this remote
y/e/d&gt; y
Current remotes:

Name                 Type
====                 ====
remote               alias

e) Edit existing remote
n) New remote
d) Delete remote
r) Rename remote
c) Copy remote
s) Set configuration password
q) Quit config
e/n/d/r/c/s/q&gt; q</code></pre>
<p>Once configured you can then use <code>rclone</code> like this,</p>
<p>List directories in top level in <code>/mnt/storage/backup</code></p>
<pre><code>rclone lsd remote:</code></pre>
<p>List all the files in <code>/mnt/storage/backup</code></p>
<pre><code>rclone ls remote:</code></pre>
<p>Copy another local directory to the alias directory called source</p>
<pre><code>rclone copy /home/source remote:source</code></pre>
<h3 id="standard-options-1">Standard options</h3>
<p>Here are the Standard options specific to alias (Alias for an existing remote).</p>
<h4 id="alias-remote">--alias-remote</h4>
<p>Remote or path to alias.</p>
<p>Can be "myremote:path/to/dir", "myremote:bucket", "myremote:" or "/local/path".</p>
<p>Properties:</p>
<ul>
<li>Config: remote</li>
<li>Env Var: RCLONE_ALIAS_REMOTE</li>
<li>Type: string</li>
<li>Required: true</li>
</ul>
<h3 id="advanced-options-1">Advanced options</h3>
<p>Here are the Advanced options specific to alias (Alias for an existing remote).</p>
<h4 id="alias-description">--alias-description</h4>
<p>Description of the remote.</p>
<p>Properties:</p>
<ul>
<li>Config: description</li>
<li>Env Var: RCLONE_ALIAS_DESCRIPTION</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h1 id="amazon-s3-storage-providers">Amazon S3 Storage Providers</h1>
<p>The S3 backend can be used with a number of different providers:</p>
<ul>
<li>AWS S3</li>
<li>Alibaba Cloud (Aliyun) Object Storage System (OSS)</li>
<li>Ceph</li>
<li>China Mobile Ecloud Elastic Object Storage (EOS)</li>
<li>Cloudflare R2</li>
<li>Arvan Cloud Object Storage (AOS)</li>
<li>DigitalOcean Spaces</li>
<li>Dreamhost</li>
<li>GCS</li>
<li>Huawei OBS</li>
<li>IBM COS S3</li>
<li>IDrive e2</li>
<li>IONOS Cloud</li>
<li>Leviia Object Storage</li>
<li>Liara Object Storage</li>
<li>Linode Object Storage</li>
<li>Magalu Object Storage</li>
<li>Minio</li>
<li>Petabox</li>
<li>Qiniu Cloud Object Storage (Kodo)</li>
<li>RackCorp Object Storage</li>
<li>Rclone Serve S3</li>
<li>Scaleway</li>
<li>Seagate Lyve Cloud</li>
<li>SeaweedFS</li>
<li>StackPath</li>
<li>Storj</li>
<li>Synology C2 Object Storage</li>
<li>Tencent Cloud Object Storage (COS)</li>
<li>Wasabi</li>
</ul>
<p>Paths are specified as <code>remote:bucket</code> (or <code>remote:</code> for the <code>lsd</code> command.) You may put subdirectories in too, e.g. <code>remote:bucket/path/to/dir</code>.</p>
<p>Once you have made a remote (see the provider specific section above) you can use it like this:</p>
<p>See all buckets</p>
<pre><code>rclone lsd remote:</code></pre>
<p>Make a new bucket</p>
<pre><code>rclone mkdir remote:bucket</code></pre>
<p>List the contents of a bucket</p>
<pre><code>rclone ls remote:bucket</code></pre>
<p>Sync <code>/home/local/directory</code> to the remote bucket, deleting any excess files in the bucket.</p>
<pre><code>rclone sync --interactive /home/local/directory remote:bucket</code></pre>
<h2 id="configuration-2">Configuration</h2>
<p>Here is an example of making an s3 configuration for the AWS S3 provider. Most applies to the other providers as well, any differences are described <a href="#providers">below</a>.</p>
<p>First run</p>
<pre><code>rclone config</code></pre>
<p>This will guide you through an interactive setup process.</p>
<pre><code>No remotes found, make a new one?
n) New remote
s) Set configuration password
q) Quit config
n/s/q&gt; n
name&gt; remote
Type of storage to configure.
Choose a number from below, or type in your own value
[snip]
XX / Amazon S3 Compliant Storage Providers including AWS, ...
   \ &quot;s3&quot;
[snip]
Storage&gt; s3
Choose your S3 provider.
Choose a number from below, or type in your own value
 1 / Amazon Web Services (AWS) S3
   \ &quot;AWS&quot;
 2 / Ceph Object Storage
   \ &quot;Ceph&quot;
 3 / DigitalOcean Spaces
   \ &quot;DigitalOcean&quot;
 4 / Dreamhost DreamObjects
   \ &quot;Dreamhost&quot;
 5 / IBM COS S3
   \ &quot;IBMCOS&quot;
 6 / Minio Object Storage
   \ &quot;Minio&quot;
 7 / Wasabi Object Storage
   \ &quot;Wasabi&quot;
 8 / Any other S3 compatible provider
   \ &quot;Other&quot;
provider&gt; 1
Get AWS credentials from runtime (environment variables or EC2/ECS meta data if no env vars). Only applies if access_key_id and secret_access_key is blank.
Choose a number from below, or type in your own value
 1 / Enter AWS credentials in the next step
   \ &quot;false&quot;
 2 / Get AWS credentials from the environment (env vars or IAM)
   \ &quot;true&quot;
env_auth&gt; 1
AWS Access Key ID - leave blank for anonymous access or runtime credentials.
access_key_id&gt; XXX
AWS Secret Access Key (password) - leave blank for anonymous access or runtime credentials.
secret_access_key&gt; YYY
Region to connect to.
Choose a number from below, or type in your own value
   / The default endpoint - a good choice if you are unsure.
 1 | US Region, Northern Virginia, or Pacific Northwest.
   | Leave location constraint empty.
   \ &quot;us-east-1&quot;
   / US East (Ohio) Region
 2 | Needs location constraint us-east-2.
   \ &quot;us-east-2&quot;
   / US West (Oregon) Region
 3 | Needs location constraint us-west-2.
   \ &quot;us-west-2&quot;
   / US West (Northern California) Region
 4 | Needs location constraint us-west-1.
   \ &quot;us-west-1&quot;
   / Canada (Central) Region
 5 | Needs location constraint ca-central-1.
   \ &quot;ca-central-1&quot;
   / EU (Ireland) Region
 6 | Needs location constraint EU or eu-west-1.
   \ &quot;eu-west-1&quot;
   / EU (London) Region
 7 | Needs location constraint eu-west-2.
   \ &quot;eu-west-2&quot;
   / EU (Frankfurt) Region
 8 | Needs location constraint eu-central-1.
   \ &quot;eu-central-1&quot;
   / Asia Pacific (Singapore) Region
 9 | Needs location constraint ap-southeast-1.
   \ &quot;ap-southeast-1&quot;
   / Asia Pacific (Sydney) Region
10 | Needs location constraint ap-southeast-2.
   \ &quot;ap-southeast-2&quot;
   / Asia Pacific (Tokyo) Region
11 | Needs location constraint ap-northeast-1.
   \ &quot;ap-northeast-1&quot;
   / Asia Pacific (Seoul)
12 | Needs location constraint ap-northeast-2.
   \ &quot;ap-northeast-2&quot;
   / Asia Pacific (Mumbai)
13 | Needs location constraint ap-south-1.
   \ &quot;ap-south-1&quot;
   / Asia Pacific (Hong Kong) Region
14 | Needs location constraint ap-east-1.
   \ &quot;ap-east-1&quot;
   / South America (Sao Paulo) Region
15 | Needs location constraint sa-east-1.
   \ &quot;sa-east-1&quot;
region&gt; 1
Endpoint for S3 API.
Leave blank if using AWS to use the default endpoint for the region.
endpoint&gt;
Location constraint - must be set to match the Region. Used when creating buckets only.
Choose a number from below, or type in your own value
 1 / Empty for US Region, Northern Virginia, or Pacific Northwest.
   \ &quot;&quot;
 2 / US East (Ohio) Region.
   \ &quot;us-east-2&quot;
 3 / US West (Oregon) Region.
   \ &quot;us-west-2&quot;
 4 / US West (Northern California) Region.
   \ &quot;us-west-1&quot;
 5 / Canada (Central) Region.
   \ &quot;ca-central-1&quot;
 6 / EU (Ireland) Region.
   \ &quot;eu-west-1&quot;
 7 / EU (London) Region.
   \ &quot;eu-west-2&quot;
 8 / EU Region.
   \ &quot;EU&quot;
 9 / Asia Pacific (Singapore) Region.
   \ &quot;ap-southeast-1&quot;
10 / Asia Pacific (Sydney) Region.
   \ &quot;ap-southeast-2&quot;
11 / Asia Pacific (Tokyo) Region.
   \ &quot;ap-northeast-1&quot;
12 / Asia Pacific (Seoul)
   \ &quot;ap-northeast-2&quot;
13 / Asia Pacific (Mumbai)
   \ &quot;ap-south-1&quot;
14 / Asia Pacific (Hong Kong)
   \ &quot;ap-east-1&quot;
15 / South America (Sao Paulo) Region.
   \ &quot;sa-east-1&quot;
location_constraint&gt; 1
Canned ACL used when creating buckets and/or storing objects in S3.
For more info visit https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html#canned-acl
Choose a number from below, or type in your own value
 1 / Owner gets FULL_CONTROL. No one else has access rights (default).
   \ &quot;private&quot;
 2 / Owner gets FULL_CONTROL. The AllUsers group gets READ access.
   \ &quot;public-read&quot;
   / Owner gets FULL_CONTROL. The AllUsers group gets READ and WRITE access.
 3 | Granting this on a bucket is generally not recommended.
   \ &quot;public-read-write&quot;
 4 / Owner gets FULL_CONTROL. The AuthenticatedUsers group gets READ access.
   \ &quot;authenticated-read&quot;
   / Object owner gets FULL_CONTROL. Bucket owner gets READ access.
 5 | If you specify this canned ACL when creating a bucket, Amazon S3 ignores it.
   \ &quot;bucket-owner-read&quot;
   / Both the object owner and the bucket owner get FULL_CONTROL over the object.
 6 | If you specify this canned ACL when creating a bucket, Amazon S3 ignores it.
   \ &quot;bucket-owner-full-control&quot;
acl&gt; 1
The server-side encryption algorithm used when storing this object in S3.
Choose a number from below, or type in your own value
 1 / None
   \ &quot;&quot;
 2 / AES256
   \ &quot;AES256&quot;
server_side_encryption&gt; 1
The storage class to use when storing objects in S3.
Choose a number from below, or type in your own value
 1 / Default
   \ &quot;&quot;
 2 / Standard storage class
   \ &quot;STANDARD&quot;
 3 / Reduced redundancy storage class
   \ &quot;REDUCED_REDUNDANCY&quot;
 4 / Standard Infrequent Access storage class
   \ &quot;STANDARD_IA&quot;
 5 / One Zone Infrequent Access storage class
   \ &quot;ONEZONE_IA&quot;
 6 / Glacier storage class
   \ &quot;GLACIER&quot;
 7 / Glacier Deep Archive storage class
   \ &quot;DEEP_ARCHIVE&quot;
 8 / Intelligent-Tiering storage class
   \ &quot;INTELLIGENT_TIERING&quot;
 9 / Glacier Instant Retrieval storage class
   \ &quot;GLACIER_IR&quot;
storage_class&gt; 1
Remote config
Configuration complete.
Options:
- type: s3
- provider: AWS
- env_auth: false
- access_key_id: XXX
- secret_access_key: YYY
- region: us-east-1
- endpoint:
- location_constraint:
- acl: private
- server_side_encryption:
- storage_class:
Keep this &quot;remote&quot; remote?
y) Yes this is OK
e) Edit this remote
d) Delete this remote
y/e/d&gt;</code></pre>
<h3 id="modification-times-and-hashes-1">Modification times and hashes</h3>
<h4 id="modification-times-1">Modification times</h4>
<p>The modified time is stored as metadata on the object as <code>X-Amz-Meta-Mtime</code> as floating point since the epoch, accurate to 1 ns.</p>
<p>If the modification time needs to be updated rclone will attempt to perform a server side copy to update the modification if the object can be copied in a single part. In the case the object is larger than 5Gb or is in Glacier or Glacier Deep Archive storage the object will be uploaded rather than copied.</p>
<p>Note that reading this from the object takes an additional <code>HEAD</code> request as the metadata isn't returned in object listings.</p>
<h4 id="hashes">Hashes</h4>
<p>For small objects which weren't uploaded as multipart uploads (objects sized below <code>--s3-upload-cutoff</code> if uploaded with rclone) rclone uses the <code>ETag:</code> header as an MD5 checksum.</p>
<p>However for objects which were uploaded as multipart uploads or with server side encryption (SSE-AWS or SSE-C) the <code>ETag</code> header is no longer the MD5 sum of the data, so rclone adds an additional piece of metadata <code>X-Amz-Meta-Md5chksum</code> which is a base64 encoded MD5 hash (in the same format as is required for <code>Content-MD5</code>). You can use base64 -d and hexdump to check this value manually:</p>
<pre><code>echo &#39;VWTGdNx3LyXQDfA0e2Edxw==&#39; | base64 -d | hexdump</code></pre>
<p>or you can use <code>rclone check</code> to verify the hashes are OK.</p>
<p>For large objects, calculating this hash can take some time so the addition of this hash can be disabled with <code>--s3-disable-checksum</code>. This will mean that these objects do not have an MD5 checksum.</p>
<p>Note that reading this from the object takes an additional <code>HEAD</code> request as the metadata isn't returned in object listings.</p>
<h3 id="reducing-costs">Reducing costs</h3>
<h4 id="avoiding-head-requests-to-read-the-modification-time">Avoiding HEAD requests to read the modification time</h4>
<p>By default, rclone will use the modification time of objects stored in S3 for syncing. This is stored in object metadata which unfortunately takes an extra HEAD request to read which can be expensive (in time and money).</p>
<p>The modification time is used by default for all operations that require checking the time a file was last updated. It allows rclone to treat the remote more like a true filesystem, but it is inefficient on S3 because it requires an extra API call to retrieve the metadata.</p>
<p>The extra API calls can be avoided when syncing (using <code>rclone sync</code> or <code>rclone copy</code>) in a few different ways, each with its own tradeoffs.</p>
<ul>
<li><code>--size-only</code>
<ul>
<li>Only checks the size of files.</li>
<li>Uses no extra transactions.</li>
<li>If the file doesn't change size then rclone won't detect it has changed.</li>
<li><code>rclone sync --size-only /path/to/source s3:bucket</code></li>
</ul></li>
<li><code>--checksum</code>
<ul>
<li>Checks the size and MD5 checksum of files.</li>
<li>Uses no extra transactions.</li>
<li>The most accurate detection of changes possible.</li>
<li>Will cause the source to read an MD5 checksum which, if it is a local disk, will cause lots of disk activity.</li>
<li>If the source and destination are both S3 this is the <strong>recommended</strong> flag to use for maximum efficiency.</li>
<li><code>rclone sync --checksum /path/to/source s3:bucket</code></li>
</ul></li>
<li><code>--update --use-server-modtime</code>
<ul>
<li>Uses no extra transactions.</li>
<li>Modification time becomes the time the object was uploaded.</li>
<li>For many operations this is sufficient to determine if it needs uploading.</li>
<li>Using <code>--update</code> along with <code>--use-server-modtime</code>, avoids the extra API call and uploads files whose local modification time is newer than the time it was last uploaded.</li>
<li>Files created with timestamps in the past will be missed by the sync.</li>
<li><code>rclone sync --update --use-server-modtime /path/to/source s3:bucket</code></li>
</ul></li>
</ul>
<p>These flags can and should be used in combination with <code>--fast-list</code> - see below.</p>
<p>If using <code>rclone mount</code> or any command using the VFS (eg <code>rclone serve</code>) commands then you might want to consider using the VFS flag <code>--no-modtime</code> which will stop rclone reading the modification time for every object. You could also use <code>--use-server-modtime</code> if you are happy with the modification times of the objects being the time of upload.</p>
<h4 id="avoiding-get-requests-to-read-directory-listings">Avoiding GET requests to read directory listings</h4>
<p>Rclone's default directory traversal is to process each directory individually. This takes one API call per directory. Using the <code>--fast-list</code> flag will read all info about the objects into memory first using a smaller number of API calls (one per 1000 objects). See the <a href="https://rclone.org/docs/#fast-list">rclone docs</a> for more details.</p>
<pre><code>rclone sync --fast-list --checksum /path/to/source s3:bucket</code></pre>
<p><code>--fast-list</code> trades off API transactions for memory use. As a rough guide rclone uses 1k of memory per object stored, so using <code>--fast-list</code> on a sync of a million objects will use roughly 1 GiB of RAM.</p>
<p>If you are only copying a small number of files into a big repository then using <code>--no-traverse</code> is a good idea. This finds objects directly instead of through directory listings. You can do a "top-up" sync very cheaply by using <code>--max-age</code> and <code>--no-traverse</code> to copy only recent files, eg</p>
<pre><code>rclone copy --max-age 24h --no-traverse /path/to/source s3:bucket</code></pre>
<p>You'd then do a full <code>rclone sync</code> less often.</p>
<p>Note that <code>--fast-list</code> isn't required in the top-up sync.</p>
<h4 id="avoiding-head-requests-after-put">Avoiding HEAD requests after PUT</h4>
<p>By default, rclone will HEAD every object it uploads. It does this to check the object got uploaded correctly.</p>
<p>You can disable this with the <a href="#s3-no-head">--s3-no-head</a> option - see there for more details.</p>
<p>Setting this flag increases the chance for undetected upload failures.</p>
<h3 id="increasing-performance">Increasing performance</h3>
<h4 id="using-server-side-copy">Using server-side copy</h4>
<p>If you are copying objects between S3 buckets in the same region, you should use server-side copy. This is much faster than downloading and re-uploading the objects, as no data is transferred.</p>
<p>For rclone to use server-side copy, you must use the same remote for the source and destination.</p>
<pre><code>rclone copy s3:source-bucket s3:destination-bucket</code></pre>
<p>When using server-side copy, the performance is limited by the rate at which rclone issues API requests to S3. See below for how to increase the number of API requests rclone makes.</p>
<h4 id="increasing-the-rate-of-api-requests">Increasing the rate of API requests</h4>
<p>You can increase the rate of API requests to S3 by increasing the parallelism using <code>--transfers</code> and <code>--checkers</code> options.</p>
<p>Rclone uses a very conservative defaults for these settings, as not all providers support high rates of requests. Depending on your provider, you can increase significantly the number of transfers and checkers.</p>
<p>For example, with AWS S3, if you can increase the number of checkers to values like 200. If you are doing a server-side copy, you can also increase the number of transfers to 200.</p>
<pre><code>rclone sync --transfers 200 --checkers 200 --checksum s3:source-bucket s3:destination-bucket</code></pre>
<p>You will need to experiment with these values to find the optimal settings for your setup.</p>
<h3 id="versions">Versions</h3>
<p>When bucket versioning is enabled (this can be done with rclone with the <a href="#versioning"><code>rclone backend versioning</code></a> command) when rclone uploads a new version of a file it creates a <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/Versioning.html">new version of it</a> Likewise when you delete a file, the old version will be marked hidden and still be available.</p>
<p>Old versions of files, where available, are visible using the <a href="#s3-versions"><code>--s3-versions</code></a> flag.</p>
<p>It is also possible to view a bucket as it was at a certain point in time, using the <a href="#s3-version-at"><code>--s3-version-at</code></a> flag. This will show the file versions as they were at that time, showing files that have been deleted afterwards, and hiding files that were created since.</p>
<p>If you wish to remove all the old versions then you can use the <a href="#cleanup-hidden"><code>rclone backend cleanup-hidden remote:bucket</code></a> command which will delete all the old hidden versions of files, leaving the current ones intact. You can also supply a path and only old versions under that path will be deleted, e.g. <code>rclone backend cleanup-hidden remote:bucket/path/to/stuff</code>.</p>
<p>When you <code>purge</code> a bucket, the current and the old versions will be deleted then the bucket will be deleted.</p>
<p>However <code>delete</code> will cause the current versions of the files to become hidden old versions.</p>
<p>Here is a session showing the listing and retrieval of an old version followed by a <code>cleanup</code> of the old versions.</p>
<p>Show current version and all the versions with <code>--s3-versions</code> flag.</p>
<pre><code>$ rclone -q ls s3:cleanup-test
        9 one.txt

$ rclone -q --s3-versions ls s3:cleanup-test
        9 one.txt
        8 one-v2016-07-04-141032-000.txt
       16 one-v2016-07-04-141003-000.txt
       15 one-v2016-07-02-155621-000.txt</code></pre>
<p>Retrieve an old version</p>
<pre><code>$ rclone -q --s3-versions copy s3:cleanup-test/one-v2016-07-04-141003-000.txt /tmp

$ ls -l /tmp/one-v2016-07-04-141003-000.txt
-rw-rw-r-- 1 ncw ncw 16 Jul  2 17:46 /tmp/one-v2016-07-04-141003-000.txt</code></pre>
<p>Clean up all the old versions and show that they've gone.</p>
<pre><code>$ rclone -q backend cleanup-hidden s3:cleanup-test

$ rclone -q ls s3:cleanup-test
        9 one.txt

$ rclone -q --s3-versions ls s3:cleanup-test
        9 one.txt</code></pre>
<h4 id="versions-naming-caveat">Versions naming caveat</h4>
<p>When using <code>--s3-versions</code> flag rclone is relying on the file name to work out whether the objects are versions or not. Versions' names are created by inserting timestamp between file name and its extension.</p>
<pre><code>        9 file.txt
        8 file-v2023-07-17-161032-000.txt
       16 file-v2023-06-15-141003-000.txt</code></pre>
<p>If there are real files present with the same names as versions, then behaviour of <code>--s3-versions</code> can be unpredictable.</p>
<h3 id="cleanup-1">Cleanup</h3>
<p>If you run <code>rclone cleanup s3:bucket</code> then it will remove all pending multipart uploads older than 24 hours. You can use the <code>--interactive</code>/<code>i</code> or <code>--dry-run</code> flag to see exactly what it will do. If you want more control over the expiry date then run <code>rclone backend cleanup s3:bucket -o max-age=1h</code> to expire all uploads older than one hour. You can use <code>rclone backend list-multipart-uploads s3:bucket</code> to see the pending multipart uploads.</p>
<h3 id="restricted-filename-characters-1">Restricted filename characters</h3>
<p>S3 allows any valid UTF-8 string as a key.</p>
<p>Invalid UTF-8 bytes will be <a href="https://rclone.org/overview/#invalid-utf8">replaced</a>, as they can't be used in XML.</p>
<p>The following characters are replaced since these are problematic when dealing with the REST API:</p>
<table>
<thead>
<tr class="header">
<th>Character</th>
<th style="text-align: center;">Value</th>
<th style="text-align: center;">Replacement</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td>NUL</td>
<td style="text-align: center;">0x00</td>
<td style="text-align: center;">␀</td>
</tr>
<tr class="even">
<td>/</td>
<td style="text-align: center;">0x2F</td>
<td style="text-align: center;">／</td>
</tr>
</tbody>
</table>
<p>The encoding will also encode these file names as they don't seem to work with the SDK properly:</p>
<table>
<thead>
<tr class="header">
<th>File name</th>
<th style="text-align: center;">Replacement</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td>.</td>
<td style="text-align: center;">．</td>
</tr>
<tr class="even">
<td>..</td>
<td style="text-align: center;">．．</td>
</tr>
</tbody>
</table>
<h3 id="multipart-uploads">Multipart uploads</h3>
<p>rclone supports multipart uploads with S3 which means that it can upload files bigger than 5 GiB.</p>
<p>Note that files uploaded <em>both</em> with multipart upload <em>and</em> through crypt remotes do not have MD5 sums.</p>
<p>rclone switches from single part uploads to multipart uploads at the point specified by <code>--s3-upload-cutoff</code>. This can be a maximum of 5 GiB and a minimum of 0 (ie always upload multipart files).</p>
<p>The chunk sizes used in the multipart upload are specified by <code>--s3-chunk-size</code> and the number of chunks uploaded concurrently is specified by <code>--s3-upload-concurrency</code>.</p>
<p>Multipart uploads will use <code>--transfers</code> * <code>--s3-upload-concurrency</code> * <code>--s3-chunk-size</code> extra memory. Single part uploads to not use extra memory.</p>
<p>Single part transfers can be faster than multipart transfers or slower depending on your latency from S3 - the more latency, the more likely single part transfers will be faster.</p>
<p>Increasing <code>--s3-upload-concurrency</code> will increase throughput (8 would be a sensible value) and increasing <code>--s3-chunk-size</code> also increases throughput (16M would be sensible). Increasing either of these will use more memory. The default values are high enough to gain most of the possible performance without using too much memory.</p>
<h3 id="buckets-and-regions">Buckets and Regions</h3>
<p>With Amazon S3 you can list buckets (<code>rclone lsd</code>) using any region, but you can only access the content of a bucket from the region it was created in. If you attempt to access a bucket from the wrong region, you will get an error, <code>incorrect region, the bucket is not in 'XXX' region</code>.</p>
<h3 id="authentication-5">Authentication</h3>
<p>There are a number of ways to supply <code>rclone</code> with a set of AWS credentials, with and without using the environment.</p>
<p>The different authentication methods are tried in this order:</p>
<ul>
<li>Directly in the rclone configuration file (<code>env_auth = false</code> in the config file):
<ul>
<li><code>access_key_id</code> and <code>secret_access_key</code> are required.</li>
<li><code>session_token</code> can be optionally set when using AWS STS.</li>
</ul></li>
<li>Runtime configuration (<code>env_auth = true</code> in the config file):
<ul>
<li>Export the following environment variables before running <code>rclone</code>:
<ul>
<li>Access Key ID: <code>AWS_ACCESS_KEY_ID</code> or <code>AWS_ACCESS_KEY</code></li>
<li>Secret Access Key: <code>AWS_SECRET_ACCESS_KEY</code> or <code>AWS_SECRET_KEY</code></li>
<li>Session Token: <code>AWS_SESSION_TOKEN</code> (optional)</li>
</ul></li>
<li>Or, use a <a href="https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-files.html">named profile</a>:
<ul>
<li>Profile files are standard files used by AWS CLI tools</li>
<li>By default it will use the profile in your home directory (e.g. <code>~/.aws/credentials</code> on unix based systems) file and the "default" profile, to change set these environment variables or config keys:
<ul>
<li><code>AWS_SHARED_CREDENTIALS_FILE</code> to control which file or the <code>shared_credentials_file</code> config key.</li>
<li><code>AWS_PROFILE</code> to control which profile to use or the <code>profile</code> config key.</li>
</ul></li>
</ul></li>
<li>Or, run <code>rclone</code> in an ECS task with an IAM role (AWS only).</li>
<li>Or, run <code>rclone</code> on an EC2 instance with an IAM role (AWS only).</li>
<li>Or, run <code>rclone</code> in an EKS pod with an IAM role that is associated with a service account (AWS only).</li>
<li>Or, use <a href="https://docs.aws.amazon.com/sdkref/latest/guide/feature-process-credentials.html">process credentials</a> to read config from an external program.</li>
</ul></li>
</ul>
<p>With <code>env_auth = true</code> rclone (which uses the SDK for Go v2) should support <a href="https://docs.aws.amazon.com/sdkref/latest/guide/standardized-credentials.html">all authentication methods</a> that the <code>aws</code> CLI tool does and the other AWS SDKs.</p>
<p>If none of these option actually end up providing <code>rclone</code> with AWS credentials then S3 interaction will be non-authenticated (see the <a href="#anonymous-access">anonymous access</a> section for more info).</p>
<h3 id="s3-permissions">S3 Permissions</h3>
<p>When using the <code>sync</code> subcommand of <code>rclone</code> the following minimum permissions are required to be available on the bucket being written to:</p>
<ul>
<li><code>ListBucket</code></li>
<li><code>DeleteObject</code></li>
<li><code>GetObject</code></li>
<li><code>PutObject</code></li>
<li><code>PutObjectACL</code></li>
<li><code>CreateBucket</code> (unless using <a href="#s3-no-check-bucket">s3-no-check-bucket</a>)</li>
</ul>
<p>When using the <code>lsd</code> subcommand, the <code>ListAllMyBuckets</code> permission is required.</p>
<p>Example policy:</p>
<pre><code>{
    &quot;Version&quot;: &quot;2012-10-17&quot;,
    &quot;Statement&quot;: [
        {
            &quot;Effect&quot;: &quot;Allow&quot;,
            &quot;Principal&quot;: {
                &quot;AWS&quot;: &quot;arn:aws:iam::USER_SID:user/USER_NAME&quot;
            },
            &quot;Action&quot;: [
                &quot;s3:ListBucket&quot;,
                &quot;s3:DeleteObject&quot;,
                &quot;s3:GetObject&quot;,
                &quot;s3:PutObject&quot;,
                &quot;s3:PutObjectAcl&quot;
            ],
            &quot;Resource&quot;: [
              &quot;arn:aws:s3:::BUCKET_NAME/*&quot;,
              &quot;arn:aws:s3:::BUCKET_NAME&quot;
            ]
        },
        {
            &quot;Effect&quot;: &quot;Allow&quot;,
            &quot;Action&quot;: &quot;s3:ListAllMyBuckets&quot;,
            &quot;Resource&quot;: &quot;arn:aws:s3:::*&quot;
        }
    ]
}</code></pre>
<p>Notes on above:</p>
<ol type="1">
<li>This is a policy that can be used when creating bucket. It assumes that <code>USER_NAME</code> has been created.</li>
<li>The Resource entry must include both resource ARNs, as one implies the bucket and the other implies the bucket's objects.</li>
<li>When using <a href="#s3-no-check-bucket">s3-no-check-bucket</a> and the bucket already exsits, the <code>"arn:aws:s3:::BUCKET_NAME"</code> doesn't have to be included.</li>
</ol>
<p>For reference, <a href="https://gist.github.com/ebridges/ebfc9042dd7c756cd101cfa807b7ae2b">here's an Ansible script</a> that will generate one or more buckets that will work with <code>rclone sync</code>.</p>
<h3 id="key-management-system-kms">Key Management System (KMS)</h3>
<p>If you are using server-side encryption with KMS then you must make sure rclone is configured with <code>server_side_encryption = aws:kms</code> otherwise you will find you can't transfer small objects - these will create checksum errors.</p>
<h3 id="glacier-and-glacier-deep-archive">Glacier and Glacier Deep Archive</h3>
<p>You can upload objects using the glacier storage class or transition them to glacier using a <a href="http://docs.aws.amazon.com/AmazonS3/latest/user-guide/create-lifecycle.html">lifecycle policy</a>. The bucket can still be synced or copied into normally, but if rclone tries to access data from the glacier storage class you will see an error like below.</p>
<pre><code>2017/09/11 19:07:43 Failed to sync: failed to open source object: Object in GLACIER, restore first: path/to/file</code></pre>
<p>In this case you need to <a href="http://docs.aws.amazon.com/AmazonS3/latest/user-guide/restore-archived-objects.html">restore</a> the object(s) in question before using rclone.</p>
<p>Note that rclone only speaks the S3 API it does not speak the Glacier Vault API, so rclone cannot directly access Glacier Vaults.</p>
<h3 id="object-lock-enabled-s3-bucket">Object-lock enabled S3 bucket</h3>
<p>According to AWS's <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/object-lock-overview.html#object-lock-permission">documentation on S3 Object Lock</a>:</p>
<blockquote>
<p>If you configure a default retention period on a bucket, requests to upload objects in such a bucket must include the Content-MD5 header.</p>
</blockquote>
<p>As mentioned in the <a href="#modification-times-and-hashes">Modification times and hashes</a> section, small files that are not uploaded as multipart, use a different tag, causing the upload to fail. A simple solution is to set the <code>--s3-upload-cutoff 0</code> and force all the files to be uploaded as multipart.</p>
<h3 id="standard-options-2">Standard options</h3>
<p>Here are the Standard options specific to s3 (Amazon S3 Compliant Storage Providers including AWS, Alibaba, ArvanCloud, Ceph, ChinaMobile, Cloudflare, DigitalOcean, Dreamhost, GCS, HuaweiOBS, IBMCOS, IDrive, IONOS, LyveCloud, Leviia, Liara, Linode, Magalu, Minio, Netease, Petabox, RackCorp, Rclone, Scaleway, SeaweedFS, StackPath, Storj, Synology, TencentCOS, Wasabi, Qiniu and others).</p>
<h4 id="s3-provider">--s3-provider</h4>
<p>Choose your S3 provider.</p>
<p>Properties:</p>
<ul>
<li>Config: provider</li>
<li>Env Var: RCLONE_S3_PROVIDER</li>
<li>Type: string</li>
<li>Required: false</li>
<li>Examples:
<ul>
<li>"AWS"
<ul>
<li>Amazon Web Services (AWS) S3</li>
</ul></li>
<li>"Alibaba"
<ul>
<li>Alibaba Cloud Object Storage System (OSS) formerly Aliyun</li>
</ul></li>
<li>"ArvanCloud"
<ul>
<li>Arvan Cloud Object Storage (AOS)</li>
</ul></li>
<li>"Ceph"
<ul>
<li>Ceph Object Storage</li>
</ul></li>
<li>"ChinaMobile"
<ul>
<li>China Mobile Ecloud Elastic Object Storage (EOS)</li>
</ul></li>
<li>"Cloudflare"
<ul>
<li>Cloudflare R2 Storage</li>
</ul></li>
<li>"DigitalOcean"
<ul>
<li>DigitalOcean Spaces</li>
</ul></li>
<li>"Dreamhost"
<ul>
<li>Dreamhost DreamObjects</li>
</ul></li>
<li>"GCS"
<ul>
<li>Google Cloud Storage</li>
</ul></li>
<li>"HuaweiOBS"
<ul>
<li>Huawei Object Storage Service</li>
</ul></li>
<li>"IBMCOS"
<ul>
<li>IBM COS S3</li>
</ul></li>
<li>"IDrive"
<ul>
<li>IDrive e2</li>
</ul></li>
<li>"IONOS"
<ul>
<li>IONOS Cloud</li>
</ul></li>
<li>"LyveCloud"
<ul>
<li>Seagate Lyve Cloud</li>
</ul></li>
<li>"Leviia"
<ul>
<li>Leviia Object Storage</li>
</ul></li>
<li>"Liara"
<ul>
<li>Liara Object Storage</li>
</ul></li>
<li>"Linode"
<ul>
<li>Linode Object Storage</li>
</ul></li>
<li>"Magalu"
<ul>
<li>Magalu Object Storage</li>
</ul></li>
<li>"Minio"
<ul>
<li>Minio Object Storage</li>
</ul></li>
<li>"Netease"
<ul>
<li>Netease Object Storage (NOS)</li>
</ul></li>
<li>"Petabox"
<ul>
<li>Petabox Object Storage</li>
</ul></li>
<li>"RackCorp"
<ul>
<li>RackCorp Object Storage</li>
</ul></li>
<li>"Rclone"
<ul>
<li>Rclone S3 Server</li>
</ul></li>
<li>"Scaleway"
<ul>
<li>Scaleway Object Storage</li>
</ul></li>
<li>"SeaweedFS"
<ul>
<li>SeaweedFS S3</li>
</ul></li>
<li>"StackPath"
<ul>
<li>StackPath Object Storage</li>
</ul></li>
<li>"Storj"
<ul>
<li>Storj (S3 Compatible Gateway)</li>
</ul></li>
<li>"Synology"
<ul>
<li>Synology C2 Object Storage</li>
</ul></li>
<li>"TencentCOS"
<ul>
<li>Tencent Cloud Object Storage (COS)</li>
</ul></li>
<li>"Wasabi"
<ul>
<li>Wasabi Object Storage</li>
</ul></li>
<li>"Qiniu"
<ul>
<li>Qiniu Object Storage (Kodo)</li>
</ul></li>
<li>"Other"
<ul>
<li>Any other S3 compatible provider</li>
</ul></li>
</ul></li>
</ul>
<h4 id="s3-env-auth">--s3-env-auth</h4>
<p>Get AWS credentials from runtime (environment variables or EC2/ECS meta data if no env vars).</p>
<p>Only applies if access_key_id and secret_access_key is blank.</p>
<p>Properties:</p>
<ul>
<li>Config: env_auth</li>
<li>Env Var: RCLONE_S3_ENV_AUTH</li>
<li>Type: bool</li>
<li>Default: false</li>
<li>Examples:
<ul>
<li>"false"
<ul>
<li>Enter AWS credentials in the next step.</li>
</ul></li>
<li>"true"
<ul>
<li>Get AWS credentials from the environment (env vars or IAM).</li>
</ul></li>
</ul></li>
</ul>
<h4 id="s3-access-key-id">--s3-access-key-id</h4>
<p>AWS Access Key ID.</p>
<p>Leave blank for anonymous access or runtime credentials.</p>
<p>Properties:</p>
<ul>
<li>Config: access_key_id</li>
<li>Env Var: RCLONE_S3_ACCESS_KEY_ID</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="s3-secret-access-key">--s3-secret-access-key</h4>
<p>AWS Secret Access Key (password).</p>
<p>Leave blank for anonymous access or runtime credentials.</p>
<p>Properties:</p>
<ul>
<li>Config: secret_access_key</li>
<li>Env Var: RCLONE_S3_SECRET_ACCESS_KEY</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="s3-region">--s3-region</h4>
<p>Region to connect to.</p>
<p>Properties:</p>
<ul>
<li>Config: region</li>
<li>Env Var: RCLONE_S3_REGION</li>
<li>Provider: AWS</li>
<li>Type: string</li>
<li>Required: false</li>
<li>Examples:
<ul>
<li>"us-east-1"
<ul>
<li>The default endpoint - a good choice if you are unsure.</li>
<li>US Region, Northern Virginia, or Pacific Northwest.</li>
<li>Leave location constraint empty.</li>
</ul></li>
<li>"us-east-2"
<ul>
<li>US East (Ohio) Region.</li>
<li>Needs location constraint us-east-2.</li>
</ul></li>
<li>"us-west-1"
<ul>
<li>US West (Northern California) Region.</li>
<li>Needs location constraint us-west-1.</li>
</ul></li>
<li>"us-west-2"
<ul>
<li>US West (Oregon) Region.</li>
<li>Needs location constraint us-west-2.</li>
</ul></li>
<li>"ca-central-1"
<ul>
<li>Canada (Central) Region.</li>
<li>Needs location constraint ca-central-1.</li>
</ul></li>
<li>"eu-west-1"
<ul>
<li>EU (Ireland) Region.</li>
<li>Needs location constraint EU or eu-west-1.</li>
</ul></li>
<li>"eu-west-2"
<ul>
<li>EU (London) Region.</li>
<li>Needs location constraint eu-west-2.</li>
</ul></li>
<li>"eu-west-3"
<ul>
<li>EU (Paris) Region.</li>
<li>Needs location constraint eu-west-3.</li>
</ul></li>
<li>"eu-north-1"
<ul>
<li>EU (Stockholm) Region.</li>
<li>Needs location constraint eu-north-1.</li>
</ul></li>
<li>"eu-south-1"
<ul>
<li>EU (Milan) Region.</li>
<li>Needs location constraint eu-south-1.</li>
</ul></li>
<li>"eu-central-1"
<ul>
<li>EU (Frankfurt) Region.</li>
<li>Needs location constraint eu-central-1.</li>
</ul></li>
<li>"ap-southeast-1"
<ul>
<li>Asia Pacific (Singapore) Region.</li>
<li>Needs location constraint ap-southeast-1.</li>
</ul></li>
<li>"ap-southeast-2"
<ul>
<li>Asia Pacific (Sydney) Region.</li>
<li>Needs location constraint ap-southeast-2.</li>
</ul></li>
<li>"ap-northeast-1"
<ul>
<li>Asia Pacific (Tokyo) Region.</li>
<li>Needs location constraint ap-northeast-1.</li>
</ul></li>
<li>"ap-northeast-2"
<ul>
<li>Asia Pacific (Seoul).</li>
<li>Needs location constraint ap-northeast-2.</li>
</ul></li>
<li>"ap-northeast-3"
<ul>
<li>Asia Pacific (Osaka-Local).</li>
<li>Needs location constraint ap-northeast-3.</li>
</ul></li>
<li>"ap-south-1"
<ul>
<li>Asia Pacific (Mumbai).</li>
<li>Needs location constraint ap-south-1.</li>
</ul></li>
<li>"ap-east-1"
<ul>
<li>Asia Pacific (Hong Kong) Region.</li>
<li>Needs location constraint ap-east-1.</li>
</ul></li>
<li>"sa-east-1"
<ul>
<li>South America (Sao Paulo) Region.</li>
<li>Needs location constraint sa-east-1.</li>
</ul></li>
<li>"il-central-1"
<ul>
<li>Israel (Tel Aviv) Region.</li>
<li>Needs location constraint il-central-1.</li>
</ul></li>
<li>"me-south-1"
<ul>
<li>Middle East (Bahrain) Region.</li>
<li>Needs location constraint me-south-1.</li>
</ul></li>
<li>"af-south-1"
<ul>
<li>Africa (Cape Town) Region.</li>
<li>Needs location constraint af-south-1.</li>
</ul></li>
<li>"cn-north-1"
<ul>
<li>China (Beijing) Region.</li>
<li>Needs location constraint cn-north-1.</li>
</ul></li>
<li>"cn-northwest-1"
<ul>
<li>China (Ningxia) Region.</li>
<li>Needs location constraint cn-northwest-1.</li>
</ul></li>
<li>"us-gov-east-1"
<ul>
<li>AWS GovCloud (US-East) Region.</li>
<li>Needs location constraint us-gov-east-1.</li>
</ul></li>
<li>"us-gov-west-1"
<ul>
<li>AWS GovCloud (US) Region.</li>
<li>Needs location constraint us-gov-west-1.</li>
</ul></li>
</ul></li>
</ul>
<h4 id="s3-endpoint">--s3-endpoint</h4>
<p>Endpoint for S3 API.</p>
<p>Leave blank if using AWS to use the default endpoint for the region.</p>
<p>Properties:</p>
<ul>
<li>Config: endpoint</li>
<li>Env Var: RCLONE_S3_ENDPOINT</li>
<li>Provider: AWS</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="s3-location-constraint">--s3-location-constraint</h4>
<p>Location constraint - must be set to match the Region.</p>
<p>Used when creating buckets only.</p>
<p>Properties:</p>
<ul>
<li>Config: location_constraint</li>
<li>Env Var: RCLONE_S3_LOCATION_CONSTRAINT</li>
<li>Provider: AWS</li>
<li>Type: string</li>
<li>Required: false</li>
<li>Examples:
<ul>
<li>""
<ul>
<li>Empty for US Region, Northern Virginia, or Pacific Northwest</li>
</ul></li>
<li>"us-east-2"
<ul>
<li>US East (Ohio) Region</li>
</ul></li>
<li>"us-west-1"
<ul>
<li>US West (Northern California) Region</li>
</ul></li>
<li>"us-west-2"
<ul>
<li>US West (Oregon) Region</li>
</ul></li>
<li>"ca-central-1"
<ul>
<li>Canada (Central) Region</li>
</ul></li>
<li>"eu-west-1"
<ul>
<li>EU (Ireland) Region</li>
</ul></li>
<li>"eu-west-2"
<ul>
<li>EU (London) Region</li>
</ul></li>
<li>"eu-west-3"
<ul>
<li>EU (Paris) Region</li>
</ul></li>
<li>"eu-north-1"
<ul>
<li>EU (Stockholm) Region</li>
</ul></li>
<li>"eu-south-1"
<ul>
<li>EU (Milan) Region</li>
</ul></li>
<li>"EU"
<ul>
<li>EU Region</li>
</ul></li>
<li>"ap-southeast-1"
<ul>
<li>Asia Pacific (Singapore) Region</li>
</ul></li>
<li>"ap-southeast-2"
<ul>
<li>Asia Pacific (Sydney) Region</li>
</ul></li>
<li>"ap-northeast-1"
<ul>
<li>Asia Pacific (Tokyo) Region</li>
</ul></li>
<li>"ap-northeast-2"
<ul>
<li>Asia Pacific (Seoul) Region</li>
</ul></li>
<li>"ap-northeast-3"
<ul>
<li>Asia Pacific (Osaka-Local) Region</li>
</ul></li>
<li>"ap-south-1"
<ul>
<li>Asia Pacific (Mumbai) Region</li>
</ul></li>
<li>"ap-east-1"
<ul>
<li>Asia Pacific (Hong Kong) Region</li>
</ul></li>
<li>"sa-east-1"
<ul>
<li>South America (Sao Paulo) Region</li>
</ul></li>
<li>"il-central-1"
<ul>
<li>Israel (Tel Aviv) Region</li>
</ul></li>
<li>"me-south-1"
<ul>
<li>Middle East (Bahrain) Region</li>
</ul></li>
<li>"af-south-1"
<ul>
<li>Africa (Cape Town) Region</li>
</ul></li>
<li>"cn-north-1"
<ul>
<li>China (Beijing) Region</li>
</ul></li>
<li>"cn-northwest-1"
<ul>
<li>China (Ningxia) Region</li>
</ul></li>
<li>"us-gov-east-1"
<ul>
<li>AWS GovCloud (US-East) Region</li>
</ul></li>
<li>"us-gov-west-1"
<ul>
<li>AWS GovCloud (US) Region</li>
</ul></li>
</ul></li>
</ul>
<h4 id="s3-acl">--s3-acl</h4>
<p>Canned ACL used when creating buckets and storing or copying objects.</p>
<p>This ACL is used for creating objects and if bucket_acl isn't set, for creating buckets too.</p>
<p>For more info visit https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html#canned-acl</p>
<p>Note that this ACL is applied when server-side copying objects as S3 doesn't copy the ACL from the source but rather writes a fresh one.</p>
<p>If the acl is an empty string then no X-Amz-Acl: header is added and the default (private) will be used.</p>
<p>Properties:</p>
<ul>
<li>Config: acl</li>
<li>Env Var: RCLONE_S3_ACL</li>
<li>Provider: !Storj,Synology,Cloudflare</li>
<li>Type: string</li>
<li>Required: false</li>
<li>Examples:
<ul>
<li>"default"
<ul>
<li>Owner gets Full_CONTROL.</li>
<li>No one else has access rights (default).</li>
</ul></li>
<li>"private"
<ul>
<li>Owner gets FULL_CONTROL.</li>
<li>No one else has access rights (default).</li>
</ul></li>
<li>"public-read"
<ul>
<li>Owner gets FULL_CONTROL.</li>
<li>The AllUsers group gets READ access.</li>
</ul></li>
<li>"public-read-write"
<ul>
<li>Owner gets FULL_CONTROL.</li>
<li>The AllUsers group gets READ and WRITE access.</li>
<li>Granting this on a bucket is generally not recommended.</li>
</ul></li>
<li>"authenticated-read"
<ul>
<li>Owner gets FULL_CONTROL.</li>
<li>The AuthenticatedUsers group gets READ access.</li>
</ul></li>
<li>"bucket-owner-read"
<ul>
<li>Object owner gets FULL_CONTROL.</li>
<li>Bucket owner gets READ access.</li>
<li>If you specify this canned ACL when creating a bucket, Amazon S3 ignores it.</li>
</ul></li>
<li>"bucket-owner-full-control"
<ul>
<li>Both the object owner and the bucket owner get FULL_CONTROL over the object.</li>
<li>If you specify this canned ACL when creating a bucket, Amazon S3 ignores it.</li>
</ul></li>
<li>"private"
<ul>
<li>Owner gets FULL_CONTROL.</li>
<li>No one else has access rights (default).</li>
<li>This acl is available on IBM Cloud (Infra), IBM Cloud (Storage), On-Premise COS.</li>
</ul></li>
<li>"public-read"
<ul>
<li>Owner gets FULL_CONTROL.</li>
<li>The AllUsers group gets READ access.</li>
<li>This acl is available on IBM Cloud (Infra), IBM Cloud (Storage), On-Premise IBM COS.</li>
</ul></li>
<li>"public-read-write"
<ul>
<li>Owner gets FULL_CONTROL.</li>
<li>The AllUsers group gets READ and WRITE access.</li>
<li>This acl is available on IBM Cloud (Infra), On-Premise IBM COS.</li>
</ul></li>
<li>"authenticated-read"
<ul>
<li>Owner gets FULL_CONTROL.</li>
<li>The AuthenticatedUsers group gets READ access.</li>
<li>Not supported on Buckets.</li>
<li>This acl is available on IBM Cloud (Infra) and On-Premise IBM COS.</li>
</ul></li>
</ul></li>
</ul>
<h4 id="s3-server-side-encryption">--s3-server-side-encryption</h4>
<p>The server-side encryption algorithm used when storing this object in S3.</p>
<p>Properties:</p>
<ul>
<li>Config: server_side_encryption</li>
<li>Env Var: RCLONE_S3_SERVER_SIDE_ENCRYPTION</li>
<li>Provider: AWS,Ceph,ChinaMobile,Minio</li>
<li>Type: string</li>
<li>Required: false</li>
<li>Examples:
<ul>
<li>""
<ul>
<li>None</li>
</ul></li>
<li>"AES256"
<ul>
<li>AES256</li>
</ul></li>
<li>"aws:kms"
<ul>
<li>aws:kms</li>
</ul></li>
</ul></li>
</ul>
<h4 id="s3-sse-kms-key-id">--s3-sse-kms-key-id</h4>
<p>If using KMS ID you must provide the ARN of Key.</p>
<p>Properties:</p>
<ul>
<li>Config: sse_kms_key_id</li>
<li>Env Var: RCLONE_S3_SSE_KMS_KEY_ID</li>
<li>Provider: AWS,Ceph,Minio</li>
<li>Type: string</li>
<li>Required: false</li>
<li>Examples:
<ul>
<li>""
<ul>
<li>None</li>
</ul></li>
<li>"arn:aws:kms:us-east-1:*"
<ul>
<li>arn:aws:kms:*</li>
</ul></li>
</ul></li>
</ul>
<h4 id="s3-storage-class">--s3-storage-class</h4>
<p>The storage class to use when storing new objects in S3.</p>
<p>Properties:</p>
<ul>
<li>Config: storage_class</li>
<li>Env Var: RCLONE_S3_STORAGE_CLASS</li>
<li>Provider: AWS</li>
<li>Type: string</li>
<li>Required: false</li>
<li>Examples:
<ul>
<li>""
<ul>
<li>Default</li>
</ul></li>
<li>"STANDARD"
<ul>
<li>Standard storage class</li>
</ul></li>
<li>"REDUCED_REDUNDANCY"
<ul>
<li>Reduced redundancy storage class</li>
</ul></li>
<li>"STANDARD_IA"
<ul>
<li>Standard Infrequent Access storage class</li>
</ul></li>
<li>"ONEZONE_IA"
<ul>
<li>One Zone Infrequent Access storage class</li>
</ul></li>
<li>"GLACIER"
<ul>
<li>Glacier storage class</li>
</ul></li>
<li>"DEEP_ARCHIVE"
<ul>
<li>Glacier Deep Archive storage class</li>
</ul></li>
<li>"INTELLIGENT_TIERING"
<ul>
<li>Intelligent-Tiering storage class</li>
</ul></li>
<li>"GLACIER_IR"
<ul>
<li>Glacier Instant Retrieval storage class</li>
</ul></li>
</ul></li>
</ul>
<h3 id="advanced-options-2">Advanced options</h3>
<p>Here are the Advanced options specific to s3 (Amazon S3 Compliant Storage Providers including AWS, Alibaba, ArvanCloud, Ceph, ChinaMobile, Cloudflare, DigitalOcean, Dreamhost, GCS, HuaweiOBS, IBMCOS, IDrive, IONOS, LyveCloud, Leviia, Liara, Linode, Magalu, Minio, Netease, Petabox, RackCorp, Rclone, Scaleway, SeaweedFS, StackPath, Storj, Synology, TencentCOS, Wasabi, Qiniu and others).</p>
<h4 id="s3-bucket-acl">--s3-bucket-acl</h4>
<p>Canned ACL used when creating buckets.</p>
<p>For more info visit https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html#canned-acl</p>
<p>Note that this ACL is applied when only when creating buckets. If it isn't set then "acl" is used instead.</p>
<p>If the "acl" and "bucket_acl" are empty strings then no X-Amz-Acl: header is added and the default (private) will be used.</p>
<p>Properties:</p>
<ul>
<li>Config: bucket_acl</li>
<li>Env Var: RCLONE_S3_BUCKET_ACL</li>
<li>Type: string</li>
<li>Required: false</li>
<li>Examples:
<ul>
<li>"private"
<ul>
<li>Owner gets FULL_CONTROL.</li>
<li>No one else has access rights (default).</li>
</ul></li>
<li>"public-read"
<ul>
<li>Owner gets FULL_CONTROL.</li>
<li>The AllUsers group gets READ access.</li>
</ul></li>
<li>"public-read-write"
<ul>
<li>Owner gets FULL_CONTROL.</li>
<li>The AllUsers group gets READ and WRITE access.</li>
<li>Granting this on a bucket is generally not recommended.</li>
</ul></li>
<li>"authenticated-read"
<ul>
<li>Owner gets FULL_CONTROL.</li>
<li>The AuthenticatedUsers group gets READ access.</li>
</ul></li>
</ul></li>
</ul>
<h4 id="s3-requester-pays">--s3-requester-pays</h4>
<p>Enables requester pays option when interacting with S3 bucket.</p>
<p>Properties:</p>
<ul>
<li>Config: requester_pays</li>
<li>Env Var: RCLONE_S3_REQUESTER_PAYS</li>
<li>Provider: AWS</li>
<li>Type: bool</li>
<li>Default: false</li>
</ul>
<h4 id="s3-sse-customer-algorithm">--s3-sse-customer-algorithm</h4>
<p>If using SSE-C, the server-side encryption algorithm used when storing this object in S3.</p>
<p>Properties:</p>
<ul>
<li>Config: sse_customer_algorithm</li>
<li>Env Var: RCLONE_S3_SSE_CUSTOMER_ALGORITHM</li>
<li>Provider: AWS,Ceph,ChinaMobile,Minio</li>
<li>Type: string</li>
<li>Required: false</li>
<li>Examples:
<ul>
<li>""
<ul>
<li>None</li>
</ul></li>
<li>"AES256"
<ul>
<li>AES256</li>
</ul></li>
</ul></li>
</ul>
<h4 id="s3-sse-customer-key">--s3-sse-customer-key</h4>
<p>To use SSE-C you may provide the secret encryption key used to encrypt/decrypt your data.</p>
<p>Alternatively you can provide --sse-customer-key-base64.</p>
<p>Properties:</p>
<ul>
<li>Config: sse_customer_key</li>
<li>Env Var: RCLONE_S3_SSE_CUSTOMER_KEY</li>
<li>Provider: AWS,Ceph,ChinaMobile,Minio</li>
<li>Type: string</li>
<li>Required: false</li>
<li>Examples:
<ul>
<li>""
<ul>
<li>None</li>
</ul></li>
</ul></li>
</ul>
<h4 id="s3-sse-customer-key-base64">--s3-sse-customer-key-base64</h4>
<p>If using SSE-C you must provide the secret encryption key encoded in base64 format to encrypt/decrypt your data.</p>
<p>Alternatively you can provide --sse-customer-key.</p>
<p>Properties:</p>
<ul>
<li>Config: sse_customer_key_base64</li>
<li>Env Var: RCLONE_S3_SSE_CUSTOMER_KEY_BASE64</li>
<li>Provider: AWS,Ceph,ChinaMobile,Minio</li>
<li>Type: string</li>
<li>Required: false</li>
<li>Examples:
<ul>
<li>""
<ul>
<li>None</li>
</ul></li>
</ul></li>
</ul>
<h4 id="s3-sse-customer-key-md5">--s3-sse-customer-key-md5</h4>
<p>If using SSE-C you may provide the secret encryption key MD5 checksum (optional).</p>
<p>If you leave it blank, this is calculated automatically from the sse_customer_key provided.</p>
<p>Properties:</p>
<ul>
<li>Config: sse_customer_key_md5</li>
<li>Env Var: RCLONE_S3_SSE_CUSTOMER_KEY_MD5</li>
<li>Provider: AWS,Ceph,ChinaMobile,Minio</li>
<li>Type: string</li>
<li>Required: false</li>
<li>Examples:
<ul>
<li>""
<ul>
<li>None</li>
</ul></li>
</ul></li>
</ul>
<h4 id="s3-upload-cutoff">--s3-upload-cutoff</h4>
<p>Cutoff for switching to chunked upload.</p>
<p>Any files larger than this will be uploaded in chunks of chunk_size. The minimum is 0 and the maximum is 5 GiB.</p>
<p>Properties:</p>
<ul>
<li>Config: upload_cutoff</li>
<li>Env Var: RCLONE_S3_UPLOAD_CUTOFF</li>
<li>Type: SizeSuffix</li>
<li>Default: 200Mi</li>
</ul>
<h4 id="s3-chunk-size">--s3-chunk-size</h4>
<p>Chunk size to use for uploading.</p>
<p>When uploading files larger than upload_cutoff or files with unknown size (e.g. from "rclone rcat" or uploaded with "rclone mount" or google photos or google docs) they will be uploaded as multipart uploads using this chunk size.</p>
<p>Note that "--s3-upload-concurrency" chunks of this size are buffered in memory per transfer.</p>
<p>If you are transferring large files over high-speed links and you have enough memory, then increasing this will speed up the transfers.</p>
<p>Rclone will automatically increase the chunk size when uploading a large file of known size to stay below the 10,000 chunks limit.</p>
<p>Files of unknown size are uploaded with the configured chunk_size. Since the default chunk size is 5 MiB and there can be at most 10,000 chunks, this means that by default the maximum size of a file you can stream upload is 48 GiB. If you wish to stream upload larger files then you will need to increase chunk_size.</p>
<p>Increasing the chunk size decreases the accuracy of the progress statistics displayed with "-P" flag. Rclone treats chunk as sent when it's buffered by the AWS SDK, when in fact it may still be uploading. A bigger chunk size means a bigger AWS SDK buffer and progress reporting more deviating from the truth.</p>
<p>Properties:</p>
<ul>
<li>Config: chunk_size</li>
<li>Env Var: RCLONE_S3_CHUNK_SIZE</li>
<li>Type: SizeSuffix</li>
<li>Default: 5Mi</li>
</ul>
<h4 id="s3-max-upload-parts">--s3-max-upload-parts</h4>
<p>Maximum number of parts in a multipart upload.</p>
<p>This option defines the maximum number of multipart chunks to use when doing a multipart upload.</p>
<p>This can be useful if a service does not support the AWS S3 specification of 10,000 chunks.</p>
<p>Rclone will automatically increase the chunk size when uploading a large file of a known size to stay below this number of chunks limit.</p>
<p>Properties:</p>
<ul>
<li>Config: max_upload_parts</li>
<li>Env Var: RCLONE_S3_MAX_UPLOAD_PARTS</li>
<li>Type: int</li>
<li>Default: 10000</li>
</ul>
<h4 id="s3-copy-cutoff">--s3-copy-cutoff</h4>
<p>Cutoff for switching to multipart copy.</p>
<p>Any files larger than this that need to be server-side copied will be copied in chunks of this size.</p>
<p>The minimum is 0 and the maximum is 5 GiB.</p>
<p>Properties:</p>
<ul>
<li>Config: copy_cutoff</li>
<li>Env Var: RCLONE_S3_COPY_CUTOFF</li>
<li>Type: SizeSuffix</li>
<li>Default: 4.656Gi</li>
</ul>
<h4 id="s3-disable-checksum">--s3-disable-checksum</h4>
<p>Don't store MD5 checksum with object metadata.</p>
<p>Normally rclone will calculate the MD5 checksum of the input before uploading it so it can add it to metadata on the object. This is great for data integrity checking but can cause long delays for large files to start uploading.</p>
<p>Properties:</p>
<ul>
<li>Config: disable_checksum</li>
<li>Env Var: RCLONE_S3_DISABLE_CHECKSUM</li>
<li>Type: bool</li>
<li>Default: false</li>
</ul>
<h4 id="s3-shared-credentials-file">--s3-shared-credentials-file</h4>
<p>Path to the shared credentials file.</p>
<p>If env_auth = true then rclone can use a shared credentials file.</p>
<p>If this variable is empty rclone will look for the "AWS_SHARED_CREDENTIALS_FILE" env variable. If the env value is empty it will default to the current user's home directory.</p>
<pre><code>Linux/OSX: &quot;$HOME/.aws/credentials&quot;
Windows:   &quot;%USERPROFILE%\.aws\credentials&quot;</code></pre>
<p>Properties:</p>
<ul>
<li>Config: shared_credentials_file</li>
<li>Env Var: RCLONE_S3_SHARED_CREDENTIALS_FILE</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="s3-profile">--s3-profile</h4>
<p>Profile to use in the shared credentials file.</p>
<p>If env_auth = true then rclone can use a shared credentials file. This variable controls which profile is used in that file.</p>
<p>If empty it will default to the environment variable "AWS_PROFILE" or "default" if that environment variable is also not set.</p>
<p>Properties:</p>
<ul>
<li>Config: profile</li>
<li>Env Var: RCLONE_S3_PROFILE</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="s3-session-token">--s3-session-token</h4>
<p>An AWS session token.</p>
<p>Properties:</p>
<ul>
<li>Config: session_token</li>
<li>Env Var: RCLONE_S3_SESSION_TOKEN</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="s3-upload-concurrency">--s3-upload-concurrency</h4>
<p>Concurrency for multipart uploads and copies.</p>
<p>This is the number of chunks of the same file that are uploaded concurrently for multipart uploads and copies.</p>
<p>If you are uploading small numbers of large files over high-speed links and these uploads do not fully utilize your bandwidth, then increasing this may help to speed up the transfers.</p>
<p>Properties:</p>
<ul>
<li>Config: upload_concurrency</li>
<li>Env Var: RCLONE_S3_UPLOAD_CONCURRENCY</li>
<li>Type: int</li>
<li>Default: 4</li>
</ul>
<h4 id="s3-force-path-style">--s3-force-path-style</h4>
<p>If true use path style access if false use virtual hosted style.</p>
<p>If this is true (the default) then rclone will use path style access, if false then rclone will use virtual path style. See <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingBucket.html#access-bucket-intro">the AWS S3 docs</a> for more info.</p>
<p>Some providers (e.g. AWS, Aliyun OSS, Netease COS, or Tencent COS) require this set to false - rclone will do this automatically based on the provider setting.</p>
<p>Note that if your bucket isn't a valid DNS name, i.e. has '.' or '_' in, you'll need to set this to true.</p>
<p>Properties:</p>
<ul>
<li>Config: force_path_style</li>
<li>Env Var: RCLONE_S3_FORCE_PATH_STYLE</li>
<li>Type: bool</li>
<li>Default: true</li>
</ul>
<h4 id="s3-v2-auth">--s3-v2-auth</h4>
<p>If true use v2 authentication.</p>
<p>If this is false (the default) then rclone will use v4 authentication. If it is set then rclone will use v2 authentication.</p>
<p>Use this only if v4 signatures don't work, e.g. pre Jewel/v10 CEPH.</p>
<p>Properties:</p>
<ul>
<li>Config: v2_auth</li>
<li>Env Var: RCLONE_S3_V2_AUTH</li>
<li>Type: bool</li>
<li>Default: false</li>
</ul>
<h4 id="s3-use-dual-stack">--s3-use-dual-stack</h4>
<p>If true use AWS S3 dual-stack endpoint (IPv6 support).</p>
<p>See <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/dual-stack-endpoints.html">AWS Docs on Dualstack Endpoints</a></p>
<p>Properties:</p>
<ul>
<li>Config: use_dual_stack</li>
<li>Env Var: RCLONE_S3_USE_DUAL_STACK</li>
<li>Type: bool</li>
<li>Default: false</li>
</ul>
<h4 id="s3-use-accelerate-endpoint">--s3-use-accelerate-endpoint</h4>
<p>If true use the AWS S3 accelerated endpoint.</p>
<p>See: <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/transfer-acceleration-examples.html">AWS S3 Transfer acceleration</a></p>
<p>Properties:</p>
<ul>
<li>Config: use_accelerate_endpoint</li>
<li>Env Var: RCLONE_S3_USE_ACCELERATE_ENDPOINT</li>
<li>Provider: AWS</li>
<li>Type: bool</li>
<li>Default: false</li>
</ul>
<h4 id="s3-leave-parts-on-error">--s3-leave-parts-on-error</h4>
<p>If true avoid calling abort upload on a failure, leaving all successfully uploaded parts on S3 for manual recovery.</p>
<p>It should be set to true for resuming uploads across different sessions.</p>
<p>WARNING: Storing parts of an incomplete multipart upload counts towards space usage on S3 and will add additional costs if not cleaned up.</p>
<p>Properties:</p>
<ul>
<li>Config: leave_parts_on_error</li>
<li>Env Var: RCLONE_S3_LEAVE_PARTS_ON_ERROR</li>
<li>Provider: AWS</li>
<li>Type: bool</li>
<li>Default: false</li>
</ul>
<h4 id="s3-list-chunk">--s3-list-chunk</h4>
<p>Size of listing chunk (response list for each ListObject S3 request).</p>
<p>This option is also known as "MaxKeys", "max-items", or "page-size" from the AWS S3 specification. Most services truncate the response list to 1000 objects even if requested more than that. In AWS S3 this is a global maximum and cannot be changed, see <a href="https://docs.aws.amazon.com/cli/latest/reference/s3/ls.html">AWS S3</a>. In Ceph, this can be increased with the "rgw list buckets max chunk" option.</p>
<p>Properties:</p>
<ul>
<li>Config: list_chunk</li>
<li>Env Var: RCLONE_S3_LIST_CHUNK</li>
<li>Type: int</li>
<li>Default: 1000</li>
</ul>
<h4 id="s3-list-version">--s3-list-version</h4>
<p>Version of ListObjects to use: 1,2 or 0 for auto.</p>
<p>When S3 originally launched it only provided the ListObjects call to enumerate objects in a bucket.</p>
<p>However in May 2016 the ListObjectsV2 call was introduced. This is much higher performance and should be used if at all possible.</p>
<p>If set to the default, 0, rclone will guess according to the provider set which list objects method to call. If it guesses wrong, then it may be set manually here.</p>
<p>Properties:</p>
<ul>
<li>Config: list_version</li>
<li>Env Var: RCLONE_S3_LIST_VERSION</li>
<li>Type: int</li>
<li>Default: 0</li>
</ul>
<h4 id="s3-list-url-encode">--s3-list-url-encode</h4>
<p>Whether to url encode listings: true/false/unset</p>
<p>Some providers support URL encoding listings and where this is available this is more reliable when using control characters in file names. If this is set to unset (the default) then rclone will choose according to the provider setting what to apply, but you can override rclone's choice here.</p>
<p>Properties:</p>
<ul>
<li>Config: list_url_encode</li>
<li>Env Var: RCLONE_S3_LIST_URL_ENCODE</li>
<li>Type: Tristate</li>
<li>Default: unset</li>
</ul>
<h4 id="s3-no-check-bucket">--s3-no-check-bucket</h4>
<p>If set, don't attempt to check the bucket exists or create it.</p>
<p>This can be useful when trying to minimise the number of transactions rclone does if you know the bucket exists already.</p>
<p>It can also be needed if the user you are using does not have bucket creation permissions. Before v1.52.0 this would have passed silently due to a bug.</p>
<p>Properties:</p>
<ul>
<li>Config: no_check_bucket</li>
<li>Env Var: RCLONE_S3_NO_CHECK_BUCKET</li>
<li>Type: bool</li>
<li>Default: false</li>
</ul>
<h4 id="s3-no-head">--s3-no-head</h4>
<p>If set, don't HEAD uploaded objects to check integrity.</p>
<p>This can be useful when trying to minimise the number of transactions rclone does.</p>
<p>Setting it means that if rclone receives a 200 OK message after uploading an object with PUT then it will assume that it got uploaded properly.</p>
<p>In particular it will assume:</p>
<ul>
<li>the metadata, including modtime, storage class and content type was as uploaded</li>
<li>the size was as uploaded</li>
</ul>
<p>It reads the following items from the response for a single part PUT:</p>
<ul>
<li>the MD5SUM</li>
<li>The uploaded date</li>
</ul>
<p>For multipart uploads these items aren't read.</p>
<p>If an source object of unknown length is uploaded then rclone <strong>will</strong> do a HEAD request.</p>
<p>Setting this flag increases the chance for undetected upload failures, in particular an incorrect size, so it isn't recommended for normal operation. In practice the chance of an undetected upload failure is very small even with this flag.</p>
<p>Properties:</p>
<ul>
<li>Config: no_head</li>
<li>Env Var: RCLONE_S3_NO_HEAD</li>
<li>Type: bool</li>
<li>Default: false</li>
</ul>
<h4 id="s3-no-head-object">--s3-no-head-object</h4>
<p>If set, do not do HEAD before GET when getting objects.</p>
<p>Properties:</p>
<ul>
<li>Config: no_head_object</li>
<li>Env Var: RCLONE_S3_NO_HEAD_OBJECT</li>
<li>Type: bool</li>
<li>Default: false</li>
</ul>
<h4 id="s3-encoding">--s3-encoding</h4>
<p>The encoding for the backend.</p>
<p>See the <a href="https://rclone.org/overview/#encoding">encoding section in the overview</a> for more info.</p>
<p>Properties:</p>
<ul>
<li>Config: encoding</li>
<li>Env Var: RCLONE_S3_ENCODING</li>
<li>Type: Encoding</li>
<li>Default: Slash,InvalidUtf8,Dot</li>
</ul>
<h4 id="s3-memory-pool-flush-time">--s3-memory-pool-flush-time</h4>
<p>How often internal memory buffer pools will be flushed. (no longer used)</p>
<p>Properties:</p>
<ul>
<li>Config: memory_pool_flush_time</li>
<li>Env Var: RCLONE_S3_MEMORY_POOL_FLUSH_TIME</li>
<li>Type: Duration</li>
<li>Default: 1m0s</li>
</ul>
<h4 id="s3-memory-pool-use-mmap">--s3-memory-pool-use-mmap</h4>
<p>Whether to use mmap buffers in internal memory pool. (no longer used)</p>
<p>Properties:</p>
<ul>
<li>Config: memory_pool_use_mmap</li>
<li>Env Var: RCLONE_S3_MEMORY_POOL_USE_MMAP</li>
<li>Type: bool</li>
<li>Default: false</li>
</ul>
<h4 id="s3-disable-http2">--s3-disable-http2</h4>
<p>Disable usage of http2 for S3 backends.</p>
<p>There is currently an unsolved issue with the s3 (specifically minio) backend and HTTP/2. HTTP/2 is enabled by default for the s3 backend but can be disabled here. When the issue is solved this flag will be removed.</p>
<p>See: https://github.com/rclone/rclone/issues/4673, https://github.com/rclone/rclone/issues/3631</p>
<p>Properties:</p>
<ul>
<li>Config: disable_http2</li>
<li>Env Var: RCLONE_S3_DISABLE_HTTP2</li>
<li>Type: bool</li>
<li>Default: false</li>
</ul>
<h4 id="s3-download-url">--s3-download-url</h4>
<p>Custom endpoint for downloads. This is usually set to a CloudFront CDN URL as AWS S3 offers cheaper egress for data downloaded through the CloudFront network.</p>
<p>Properties:</p>
<ul>
<li>Config: download_url</li>
<li>Env Var: RCLONE_S3_DOWNLOAD_URL</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="s3-directory-markers">--s3-directory-markers</h4>
<p>Upload an empty object with a trailing slash when a new directory is created</p>
<p>Empty folders are unsupported for bucket based remotes, this option creates an empty object ending with "/", to persist the folder.</p>
<p>Properties:</p>
<ul>
<li>Config: directory_markers</li>
<li>Env Var: RCLONE_S3_DIRECTORY_MARKERS</li>
<li>Type: bool</li>
<li>Default: false</li>
</ul>
<h4 id="s3-use-multipart-etag">--s3-use-multipart-etag</h4>
<p>Whether to use ETag in multipart uploads for verification</p>
<p>This should be true, false or left unset to use the default for the provider.</p>
<p>Properties:</p>
<ul>
<li>Config: use_multipart_etag</li>
<li>Env Var: RCLONE_S3_USE_MULTIPART_ETAG</li>
<li>Type: Tristate</li>
<li>Default: unset</li>
</ul>
<h4 id="s3-use-unsigned-payload">--s3-use-unsigned-payload</h4>
<p>Whether to use an unsigned payload in PutObject</p>
<p>Rclone has to avoid the AWS SDK seeking the body when calling PutObject. The AWS provider can add checksums in the trailer to avoid seeking but other providers can't.</p>
<p>This should be true, false or left unset to use the default for the provider.</p>
<p>Properties:</p>
<ul>
<li>Config: use_unsigned_payload</li>
<li>Env Var: RCLONE_S3_USE_UNSIGNED_PAYLOAD</li>
<li>Type: Tristate</li>
<li>Default: unset</li>
</ul>
<h4 id="s3-use-presigned-request">--s3-use-presigned-request</h4>
<p>Whether to use a presigned request or PutObject for single part uploads</p>
<p>If this is false rclone will use PutObject from the AWS SDK to upload an object.</p>
<p>Versions of rclone &lt; 1.59 use presigned requests to upload a single part object and setting this flag to true will re-enable that functionality. This shouldn't be necessary except in exceptional circumstances or for testing.</p>
<p>Properties:</p>
<ul>
<li>Config: use_presigned_request</li>
<li>Env Var: RCLONE_S3_USE_PRESIGNED_REQUEST</li>
<li>Type: bool</li>
<li>Default: false</li>
</ul>
<h4 id="s3-versions">--s3-versions</h4>
<p>Include old versions in directory listings.</p>
<p>Properties:</p>
<ul>
<li>Config: versions</li>
<li>Env Var: RCLONE_S3_VERSIONS</li>
<li>Type: bool</li>
<li>Default: false</li>
</ul>
<h4 id="s3-version-at">--s3-version-at</h4>
<p>Show file versions as they were at the specified time.</p>
<p>The parameter should be a date, "2006-01-02", datetime "2006-01-02 15:04:05" or a duration for that long ago, eg "100d" or "1h".</p>
<p>Note that when using this no file write operations are permitted, so you can't upload files or delete them.</p>
<p>See <a href="https://rclone.org/docs/#time-option">the time option docs</a> for valid formats.</p>
<p>Properties:</p>
<ul>
<li>Config: version_at</li>
<li>Env Var: RCLONE_S3_VERSION_AT</li>
<li>Type: Time</li>
<li>Default: off</li>
</ul>
<h4 id="s3-version-deleted">--s3-version-deleted</h4>
<p>Show deleted file markers when using versions.</p>
<p>This shows deleted file markers in the listing when using versions. These will appear as 0 size files. The only operation which can be performed on them is deletion.</p>
<p>Deleting a delete marker will reveal the previous version.</p>
<p>Deleted files will always show with a timestamp.</p>
<p>Properties:</p>
<ul>
<li>Config: version_deleted</li>
<li>Env Var: RCLONE_S3_VERSION_DELETED</li>
<li>Type: bool</li>
<li>Default: false</li>
</ul>
<h4 id="s3-decompress">--s3-decompress</h4>
<p>If set this will decompress gzip encoded objects.</p>
<p>It is possible to upload objects to S3 with "Content-Encoding: gzip" set. Normally rclone will download these files as compressed objects.</p>
<p>If this flag is set then rclone will decompress these files with "Content-Encoding: gzip" as they are received. This means that rclone can't check the size and hash but the file contents will be decompressed.</p>
<p>Properties:</p>
<ul>
<li>Config: decompress</li>
<li>Env Var: RCLONE_S3_DECOMPRESS</li>
<li>Type: bool</li>
<li>Default: false</li>
</ul>
<h4 id="s3-might-gzip">--s3-might-gzip</h4>
<p>Set this if the backend might gzip objects.</p>
<p>Normally providers will not alter objects when they are downloaded. If an object was not uploaded with <code>Content-Encoding: gzip</code> then it won't be set on download.</p>
<p>However some providers may gzip objects even if they weren't uploaded with <code>Content-Encoding: gzip</code> (eg Cloudflare).</p>
<p>A symptom of this would be receiving errors like</p>
<pre><code>ERROR corrupted on transfer: sizes differ NNN vs MMM</code></pre>
<p>If you set this flag and rclone downloads an object with Content-Encoding: gzip set and chunked transfer encoding, then rclone will decompress the object on the fly.</p>
<p>If this is set to unset (the default) then rclone will choose according to the provider setting what to apply, but you can override rclone's choice here.</p>
<p>Properties:</p>
<ul>
<li>Config: might_gzip</li>
<li>Env Var: RCLONE_S3_MIGHT_GZIP</li>
<li>Type: Tristate</li>
<li>Default: unset</li>
</ul>
<h4 id="s3-use-accept-encoding-gzip">--s3-use-accept-encoding-gzip</h4>
<p>Whether to send <code>Accept-Encoding: gzip</code> header.</p>
<p>By default, rclone will append <code>Accept-Encoding: gzip</code> to the request to download compressed objects whenever possible.</p>
<p>However some providers such as Google Cloud Storage may alter the HTTP headers, breaking the signature of the request.</p>
<p>A symptom of this would be receiving errors like</p>
<pre><code>SignatureDoesNotMatch: The request signature we calculated does not match the signature you provided.</code></pre>
<p>In this case, you might want to try disabling this option.</p>
<p>Properties:</p>
<ul>
<li>Config: use_accept_encoding_gzip</li>
<li>Env Var: RCLONE_S3_USE_ACCEPT_ENCODING_GZIP</li>
<li>Type: Tristate</li>
<li>Default: unset</li>
</ul>
<h4 id="s3-no-system-metadata">--s3-no-system-metadata</h4>
<p>Suppress setting and reading of system metadata</p>
<p>Properties:</p>
<ul>
<li>Config: no_system_metadata</li>
<li>Env Var: RCLONE_S3_NO_SYSTEM_METADATA</li>
<li>Type: bool</li>
<li>Default: false</li>
</ul>
<h4 id="s3-sts-endpoint">--s3-sts-endpoint</h4>
<p>Endpoint for STS (deprecated).</p>
<p>Leave blank if using AWS to use the default endpoint for the region.</p>
<p>Properties:</p>
<ul>
<li>Config: sts_endpoint</li>
<li>Env Var: RCLONE_S3_STS_ENDPOINT</li>
<li>Provider: AWS</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="s3-use-already-exists">--s3-use-already-exists</h4>
<p>Set if rclone should report BucketAlreadyExists errors on bucket creation.</p>
<p>At some point during the evolution of the s3 protocol, AWS started returning an <code>AlreadyOwnedByYou</code> error when attempting to create a bucket that the user already owned, rather than a <code>BucketAlreadyExists</code> error.</p>
<p>Unfortunately exactly what has been implemented by s3 clones is a little inconsistent, some return <code>AlreadyOwnedByYou</code>, some return <code>BucketAlreadyExists</code> and some return no error at all.</p>
<p>This is important to rclone because it ensures the bucket exists by creating it on quite a lot of operations (unless <code>--s3-no-check-bucket</code> is used).</p>
<p>If rclone knows the provider can return <code>AlreadyOwnedByYou</code> or returns no error then it can report <code>BucketAlreadyExists</code> errors when the user attempts to create a bucket not owned by them. Otherwise rclone ignores the <code>BucketAlreadyExists</code> error which can lead to confusion.</p>
<p>This should be automatically set correctly for all providers rclone knows about - please make a bug report if not.</p>
<p>Properties:</p>
<ul>
<li>Config: use_already_exists</li>
<li>Env Var: RCLONE_S3_USE_ALREADY_EXISTS</li>
<li>Type: Tristate</li>
<li>Default: unset</li>
</ul>
<h4 id="s3-use-multipart-uploads">--s3-use-multipart-uploads</h4>
<p>Set if rclone should use multipart uploads.</p>
<p>You can change this if you want to disable the use of multipart uploads. This shouldn't be necessary in normal operation.</p>
<p>This should be automatically set correctly for all providers rclone knows about - please make a bug report if not.</p>
<p>Properties:</p>
<ul>
<li>Config: use_multipart_uploads</li>
<li>Env Var: RCLONE_S3_USE_MULTIPART_UPLOADS</li>
<li>Type: Tristate</li>
<li>Default: unset</li>
</ul>
<h4 id="s3-sdk-log-mode">--s3-sdk-log-mode</h4>
<p>Set to debug the SDK</p>
<p>This can be set to a comma separated list of the following functions:</p>
<ul>
<li><code>Signing</code></li>
<li><code>Retries</code></li>
<li><code>Request</code></li>
<li><code>RequestWithBody</code></li>
<li><code>Response</code></li>
<li><code>ResponseWithBody</code></li>
<li><code>DeprecatedUsage</code></li>
<li><code>RequestEventMessage</code></li>
<li><code>ResponseEventMessage</code></li>
</ul>
<p>Use <code>Off</code> to disable and <code>All</code> to set all log levels. You will need to use <code>-vv</code> to see the debug level logs.</p>
<p>Properties:</p>
<ul>
<li>Config: sdk_log_mode</li>
<li>Env Var: RCLONE_S3_SDK_LOG_MODE</li>
<li>Type: Bits</li>
<li>Default: Off</li>
</ul>
<h4 id="s3-description">--s3-description</h4>
<p>Description of the remote.</p>
<p>Properties:</p>
<ul>
<li>Config: description</li>
<li>Env Var: RCLONE_S3_DESCRIPTION</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h3 id="metadata-3">Metadata</h3>
<p>User metadata is stored as x-amz-meta- keys. S3 metadata keys are case insensitive and are always returned in lower case.</p>
<p>Here are the possible system metadata items for the s3 backend.</p>
<table>
<colgroup>
<col style="width: 15%" />
<col style="width: 15%" />
<col style="width: 15%" />
<col style="width: 23%" />
<col style="width: 28%" />
</colgroup>
<thead>
<tr class="header">
<th>Name</th>
<th>Help</th>
<th>Type</th>
<th>Example</th>
<th>Read Only</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td>btime</td>
<td>Time of file birth (creation) read from Last-Modified header</td>
<td>RFC 3339</td>
<td>2006-01-02T15:04:05.999999999Z07:00</td>
<td><strong>Y</strong></td>
</tr>
<tr class="even">
<td>cache-control</td>
<td>Cache-Control header</td>
<td>string</td>
<td>no-cache</td>
<td>N</td>
</tr>
<tr class="odd">
<td>content-disposition</td>
<td>Content-Disposition header</td>
<td>string</td>
<td>inline</td>
<td>N</td>
</tr>
<tr class="even">
<td>content-encoding</td>
<td>Content-Encoding header</td>
<td>string</td>
<td>gzip</td>
<td>N</td>
</tr>
<tr class="odd">
<td>content-language</td>
<td>Content-Language header</td>
<td>string</td>
<td>en-US</td>
<td>N</td>
</tr>
<tr class="even">
<td>content-type</td>
<td>Content-Type header</td>
<td>string</td>
<td>text/plain</td>
<td>N</td>
</tr>
<tr class="odd">
<td>mtime</td>
<td>Time of last modification, read from rclone metadata</td>
<td>RFC 3339</td>
<td>2006-01-02T15:04:05.999999999Z07:00</td>
<td>N</td>
</tr>
<tr class="even">
<td>tier</td>
<td>Tier of the object</td>
<td>string</td>
<td>GLACIER</td>
<td><strong>Y</strong></td>
</tr>
</tbody>
</table>
<p>See the <a href="https://rclone.org/docs/#metadata">metadata</a> docs for more info.</p>
<h2 id="backend-commands">Backend commands</h2>
<p>Here are the commands specific to the s3 backend.</p>
<p>Run them with</p>
<pre><code>rclone backend COMMAND remote:</code></pre>
<p>The help below will explain what arguments each command takes.</p>
<p>See the <a href="https://rclone.org/commands/rclone_backend/">backend</a> command for more info on how to pass options and arguments.</p>
<p>These can be run on a running backend using the rc command <a href="https://rclone.org/rc/#backend-command">backend/command</a>.</p>
<h3 id="restore">restore</h3>
<p>Restore objects from GLACIER or INTELLIGENT-TIERING archive tier</p>
<pre><code>rclone backend restore remote: [options] [&lt;arguments&gt;+]</code></pre>
<p>This command can be used to restore one or more objects from GLACIER to normal storage or from INTELLIGENT-TIERING Archive Access / Deep Archive Access tier to the Frequent Access tier.</p>
<p>Usage Examples:</p>
<pre><code>rclone backend restore s3:bucket/path/to/object -o priority=PRIORITY -o lifetime=DAYS
rclone backend restore s3:bucket/path/to/directory -o priority=PRIORITY -o lifetime=DAYS
rclone backend restore s3:bucket -o priority=PRIORITY -o lifetime=DAYS
rclone backend restore s3:bucket/path/to/directory -o priority=PRIORITY</code></pre>
<p>This flag also obeys the filters. Test first with --interactive/-i or --dry-run flags</p>
<pre><code>rclone --interactive backend restore --include &quot;*.txt&quot; s3:bucket/path -o priority=Standard -o lifetime=1</code></pre>
<p>All the objects shown will be marked for restore, then</p>
<pre><code>rclone backend restore --include &quot;*.txt&quot; s3:bucket/path -o priority=Standard -o lifetime=1</code></pre>
<p>It returns a list of status dictionaries with Remote and Status keys. The Status will be OK if it was successful or an error message if not.</p>
<pre><code>[
    {
        &quot;Status&quot;: &quot;OK&quot;,
        &quot;Remote&quot;: &quot;test.txt&quot;
    },
    {
        &quot;Status&quot;: &quot;OK&quot;,
        &quot;Remote&quot;: &quot;test/file4.txt&quot;
    }
]</code></pre>
<p>Options:</p>
<ul>
<li>"description": The optional description for the job.</li>
<li>"lifetime": Lifetime of the active copy in days, ignored for INTELLIGENT-TIERING storage</li>
<li>"priority": Priority of restore: Standard|Expedited|Bulk</li>
</ul>
<h3 id="restore-status">restore-status</h3>
<p>Show the restore status for objects being restored from GLACIER or INTELLIGENT-TIERING storage</p>
<pre><code>rclone backend restore-status remote: [options] [&lt;arguments&gt;+]</code></pre>
<p>This command can be used to show the status for objects being restored from GLACIER to normal storage or from INTELLIGENT-TIERING Archive Access / Deep Archive Access tier to the Frequent Access tier.</p>
<p>Usage Examples:</p>
<pre><code>rclone backend restore-status s3:bucket/path/to/object
rclone backend restore-status s3:bucket/path/to/directory
rclone backend restore-status -o all s3:bucket/path/to/directory</code></pre>
<p>This command does not obey the filters.</p>
<p>It returns a list of status dictionaries.</p>
<pre><code>[
    {
        &quot;Remote&quot;: &quot;file.txt&quot;,
        &quot;VersionID&quot;: null,
        &quot;RestoreStatus&quot;: {
            &quot;IsRestoreInProgress&quot;: true,
            &quot;RestoreExpiryDate&quot;: &quot;2023-09-06T12:29:19+01:00&quot;
        },
        &quot;StorageClass&quot;: &quot;GLACIER&quot;
    },
    {
        &quot;Remote&quot;: &quot;test.pdf&quot;,
        &quot;VersionID&quot;: null,
        &quot;RestoreStatus&quot;: {
            &quot;IsRestoreInProgress&quot;: false,
            &quot;RestoreExpiryDate&quot;: &quot;2023-09-06T12:29:19+01:00&quot;
        },
        &quot;StorageClass&quot;: &quot;DEEP_ARCHIVE&quot;
    },
    {
        &quot;Remote&quot;: &quot;test.gz&quot;,
        &quot;VersionID&quot;: null,
        &quot;RestoreStatus&quot;: {
            &quot;IsRestoreInProgress&quot;: true,
            &quot;RestoreExpiryDate&quot;: &quot;null&quot;
        },
        &quot;StorageClass&quot;: &quot;INTELLIGENT_TIERING&quot;
    }
]</code></pre>
<p>Options:</p>
<ul>
<li>"all": if set then show all objects, not just ones with restore status</li>
</ul>
<h3 id="list-multipart-uploads">list-multipart-uploads</h3>
<p>List the unfinished multipart uploads</p>
<pre><code>rclone backend list-multipart-uploads remote: [options] [&lt;arguments&gt;+]</code></pre>
<p>This command lists the unfinished multipart uploads in JSON format.</p>
<pre><code>rclone backend list-multipart s3:bucket/path/to/object</code></pre>
<p>It returns a dictionary of buckets with values as lists of unfinished multipart uploads.</p>
<p>You can call it with no bucket in which case it lists all bucket, with a bucket or with a bucket and path.</p>
<pre><code>{
  &quot;rclone&quot;: [
    {
      &quot;Initiated&quot;: &quot;2020-06-26T14:20:36Z&quot;,
      &quot;Initiator&quot;: {
        &quot;DisplayName&quot;: &quot;XXX&quot;,
        &quot;ID&quot;: &quot;arn:aws:iam::XXX:user/XXX&quot;
      },
      &quot;Key&quot;: &quot;KEY&quot;,
      &quot;Owner&quot;: {
        &quot;DisplayName&quot;: null,
        &quot;ID&quot;: &quot;XXX&quot;
      },
      &quot;StorageClass&quot;: &quot;STANDARD&quot;,
      &quot;UploadId&quot;: &quot;XXX&quot;
    }
  ],
  &quot;rclone-1000files&quot;: [],
  &quot;rclone-dst&quot;: []
}</code></pre>
<h3 id="cleanup-2">cleanup</h3>
<p>Remove unfinished multipart uploads.</p>
<pre><code>rclone backend cleanup remote: [options] [&lt;arguments&gt;+]</code></pre>
<p>This command removes unfinished multipart uploads of age greater than max-age which defaults to 24 hours.</p>
<p>Note that you can use --interactive/-i or --dry-run with this command to see what it would do.</p>
<pre><code>rclone backend cleanup s3:bucket/path/to/object
rclone backend cleanup -o max-age=7w s3:bucket/path/to/object</code></pre>
<p>Durations are parsed as per the rest of rclone, 2h, 7d, 7w etc.</p>
<p>Options:</p>
<ul>
<li>"max-age": Max age of upload to delete</li>
</ul>
<h3 id="cleanup-hidden">cleanup-hidden</h3>
<p>Remove old versions of files.</p>
<pre><code>rclone backend cleanup-hidden remote: [options] [&lt;arguments&gt;+]</code></pre>
<p>This command removes any old hidden versions of files on a versions enabled bucket.</p>
<p>Note that you can use --interactive/-i or --dry-run with this command to see what it would do.</p>
<pre><code>rclone backend cleanup-hidden s3:bucket/path/to/dir</code></pre>
<h3 id="versioning">versioning</h3>
<p>Set/get versioning support for a bucket.</p>
<pre><code>rclone backend versioning remote: [options] [&lt;arguments&gt;+]</code></pre>
<p>This command sets versioning support if a parameter is passed and then returns the current versioning status for the bucket supplied.</p>
<pre><code>rclone backend versioning s3:bucket # read status only
rclone backend versioning s3:bucket Enabled
rclone backend versioning s3:bucket Suspended</code></pre>
<p>It may return "Enabled", "Suspended" or "Unversioned". Note that once versioning has been enabled the status can't be set back to "Unversioned".</p>
<h3 id="set">set</h3>
<p>Set command for updating the config parameters.</p>
<pre><code>rclone backend set remote: [options] [&lt;arguments&gt;+]</code></pre>
<p>This set command can be used to update the config parameters for a running s3 backend.</p>
<p>Usage Examples:</p>
<pre><code>rclone backend set s3: [-o opt_name=opt_value] [-o opt_name2=opt_value2]
rclone rc backend/command command=set fs=s3: [-o opt_name=opt_value] [-o opt_name2=opt_value2]
rclone rc backend/command command=set fs=s3: -o session_token=X -o access_key_id=X -o secret_access_key=X</code></pre>
<p>The option keys are named as they are in the config file.</p>
<p>This rebuilds the connection to the s3 backend when it is called with the new parameters. Only new parameters need be passed as the values will default to those currently in use.</p>
<p>It doesn't return anything.</p>
<h3 id="anonymous-access">Anonymous access to public buckets</h3>
<p>If you want to use rclone to access a public bucket, configure with a blank <code>access_key_id</code> and <code>secret_access_key</code>. Your config should end up looking like this:</p>
<pre><code>[anons3]
type = s3
provider = AWS</code></pre>
<p>Then use it as normal with the name of the public bucket, e.g.</p>
<pre><code>rclone lsd anons3:1000genomes</code></pre>
<p>You will be able to list and copy data but not upload it.</p>
<p>You can also do this entirely on the command line</p>
<pre><code>rclone lsd :s3,provider=AWS:1000genomes</code></pre>
<h2 id="providers-1">Providers</h2>
<h3 id="aws-s3">AWS S3</h3>
<p>This is the provider used as main example and described in the <a href="#configuration">configuration</a> section above.</p>
<h3 id="aws-snowball-edge">AWS Snowball Edge</h3>
<p><a href="https://aws.amazon.com/snowball/">AWS Snowball</a> is a hardware appliance used for transferring bulk data back to AWS. Its main software interface is S3 object storage.</p>
<p>To use rclone with AWS Snowball Edge devices, configure as standard for an 'S3 Compatible Service'.</p>
<p>If using rclone pre v1.59 be sure to set <code>upload_cutoff = 0</code> otherwise you will run into authentication header issues as the snowball device does not support query parameter based authentication.</p>
<p>With rclone v1.59 or later setting <code>upload_cutoff</code> should not be necessary.</p>
<p>eg.</p>
<pre><code>[snowball]
type = s3
provider = Other
access_key_id = YOUR_ACCESS_KEY
secret_access_key = YOUR_SECRET_KEY
endpoint = http://[IP of Snowball]:8080
upload_cutoff = 0</code></pre>
<h3 id="ceph">Ceph</h3>
<p><a href="https://ceph.com/">Ceph</a> is an open-source, unified, distributed storage system designed for excellent performance, reliability and scalability. It has an S3 compatible object storage interface.</p>
<p>To use rclone with Ceph, configure as above but leave the region blank and set the endpoint. You should end up with something like this in your config:</p>
<pre><code>[ceph]
type = s3
provider = Ceph
env_auth = false
access_key_id = XXX
secret_access_key = YYY
region =
endpoint = https://ceph.endpoint.example.com
location_constraint =
acl =
server_side_encryption =
storage_class =</code></pre>
<p>If you are using an older version of CEPH (e.g. 10.2.x Jewel) and a version of rclone before v1.59 then you may need to supply the parameter <code>--s3-upload-cutoff 0</code> or put this in the config file as <code>upload_cutoff 0</code> to work around a bug which causes uploading of small files to fail.</p>
<p>Note also that Ceph sometimes puts <code>/</code> in the passwords it gives users. If you read the secret access key using the command line tools you will get a JSON blob with the <code>/</code> escaped as <code>\/</code>. Make sure you only write <code>/</code> in the secret access key.</p>
<p>Eg the dump from Ceph looks something like this (irrelevant keys removed).</p>
<pre><code>{
    &quot;user_id&quot;: &quot;xxx&quot;,
    &quot;display_name&quot;: &quot;xxxx&quot;,
    &quot;keys&quot;: [
        {
            &quot;user&quot;: &quot;xxx&quot;,
            &quot;access_key&quot;: &quot;xxxxxx&quot;,
            &quot;secret_key&quot;: &quot;xxxxxx\/xxxx&quot;
        }
    ],
}</code></pre>
<p>Because this is a json dump, it is encoding the <code>/</code> as <code>\/</code>, so if you use the secret key as <code>xxxxxx/xxxx</code> it will work fine.</p>
<h3 id="cloudflare-r2">Cloudflare R2</h3>
<p><a href="https://blog.cloudflare.com/r2-open-beta/">Cloudflare R2</a> Storage allows developers to store large amounts of unstructured data without the costly egress bandwidth fees associated with typical cloud storage services.</p>
<p>Here is an example of making a Cloudflare R2 configuration. First run:</p>
<pre><code>rclone config</code></pre>
<p>This will guide you through an interactive setup process.</p>
<p>Note that all buckets are private, and all are stored in the same "auto" region. It is necessary to use Cloudflare workers to share the content of a bucket publicly.</p>
<pre><code>No remotes found, make a new one?
n) New remote
s) Set configuration password
q) Quit config
n/s/q&gt; n
name&gt; r2
Option Storage.
Type of storage to configure.
Choose a number from below, or type in your own value.
...
XX / Amazon S3 Compliant Storage Providers including AWS, Alibaba, Ceph, China Mobile, Cloudflare, ArvanCloud, DigitalOcean, Dreamhost, Huawei OBS, IBM COS, Lyve Cloud, Minio, Magalu, Netease, RackCorp, Scaleway, SeaweedFS, StackPath, Storj, Synology, Tencent COS and Wasabi
   \ (s3)
...
Storage&gt; s3
Option provider.
Choose your S3 provider.
Choose a number from below, or type in your own value.
Press Enter to leave empty.
...
XX / Cloudflare R2 Storage
   \ (Cloudflare)
...
provider&gt; Cloudflare
Option env_auth.
Get AWS credentials from runtime (environment variables or EC2/ECS meta data if no env vars).
Only applies if access_key_id and secret_access_key is blank.
Choose a number from below, or type in your own boolean value (true or false).
Press Enter for the default (false).
 1 / Enter AWS credentials in the next step.
   \ (false)
 2 / Get AWS credentials from the environment (env vars or IAM).
   \ (true)
env_auth&gt; 1
Option access_key_id.
AWS Access Key ID.
Leave blank for anonymous access or runtime credentials.
Enter a value. Press Enter to leave empty.
access_key_id&gt; ACCESS_KEY
Option secret_access_key.
AWS Secret Access Key (password).
Leave blank for anonymous access or runtime credentials.
Enter a value. Press Enter to leave empty.
secret_access_key&gt; SECRET_ACCESS_KEY
Option region.
Region to connect to.
Choose a number from below, or type in your own value.
Press Enter to leave empty.
 1 / R2 buckets are automatically distributed across Cloudflare&#39;s data centers for low latency.
   \ (auto)
region&gt; 1
Option endpoint.
Endpoint for S3 API.
Required when using an S3 clone.
Enter a value. Press Enter to leave empty.
endpoint&gt; https://ACCOUNT_ID.r2.cloudflarestorage.com
Edit advanced config?
y) Yes
n) No (default)
y/n&gt; n
--------------------
y) Yes this is OK (default)
e) Edit this remote
d) Delete this remote
y/e/d&gt; y</code></pre>
<p>This will leave your config looking something like:</p>
<pre><code>[r2]
type = s3
provider = Cloudflare
access_key_id = ACCESS_KEY
secret_access_key = SECRET_ACCESS_KEY
region = auto
endpoint = https://ACCOUNT_ID.r2.cloudflarestorage.com
acl = private</code></pre>
<p>Now run <code>rclone lsf r2:</code> to see your buckets and <code>rclone lsf r2:bucket</code> to look within a bucket.</p>
<p>For R2 tokens with the "Object Read &amp; Write" permission, you may also need to add <code>no_check_bucket = true</code> for object uploads to work correctly.</p>
<p>Note that Cloudflare decompresses files uploaded with <code>Content-Encoding: gzip</code> by default which is a deviation from what AWS does. If this is causing a problem then upload the files with <code>--header-upload "Cache-Control: no-transform"</code></p>
<h3 id="dreamhost">Dreamhost</h3>
<p>Dreamhost <a href="https://www.dreamhost.com/cloud/storage/">DreamObjects</a> is an object storage system based on CEPH.</p>
<p>To use rclone with Dreamhost, configure as above but leave the region blank and set the endpoint. You should end up with something like this in your config:</p>
<pre><code>[dreamobjects]
type = s3
provider = DreamHost
env_auth = false
access_key_id = your_access_key
secret_access_key = your_secret_key
region =
endpoint = objects-us-west-1.dream.io
location_constraint =
acl = private
server_side_encryption =
storage_class =</code></pre>
<h3 id="google-cloud-storage">Google Cloud Storage</h3>
<p><a href="https://cloud.google.com/storage/docs">GoogleCloudStorage</a> is an <a href="https://cloud.google.com/storage/docs/interoperability">S3-interoperable</a> object storage service from Google Cloud Platform.</p>
<p>To connect to Google Cloud Storage you will need an access key and secret key. These can be retrieved by creating an <a href="https://cloud.google.com/storage/docs/authentication/managing-hmackeys">HMAC key</a>.</p>
<pre><code>[gs]
type = s3
provider = GCS
access_key_id = your_access_key
secret_access_key = your_secret_key
endpoint = https://storage.googleapis.com</code></pre>
<p><strong>Note</strong> that <code>--s3-versions</code> does not work with GCS when it needs to do directory paging. Rclone will return the error:</p>
<pre><code>s3 protocol error: received versions listing with IsTruncated set with no NextKeyMarker</code></pre>
<p>This is Google bug <a href="https://issuetracker.google.com/u/0/issues/312292516">#312292516</a>.</p>
<h3 id="digitalocean-spaces">DigitalOcean Spaces</h3>
<p><a href="https://www.digitalocean.com/products/object-storage/">Spaces</a> is an <a href="https://developers.digitalocean.com/documentation/spaces/">S3-interoperable</a> object storage service from cloud provider DigitalOcean.</p>
<p>To connect to DigitalOcean Spaces you will need an access key and secret key. These can be retrieved on the "<a href="https://cloud.digitalocean.com/settings/api/tokens">Applications &amp; API</a>" page of the DigitalOcean control panel. They will be needed when prompted by <code>rclone config</code> for your <code>access_key_id</code> and <code>secret_access_key</code>.</p>
<p>When prompted for a <code>region</code> or <code>location_constraint</code>, press enter to use the default value. The region must be included in the <code>endpoint</code> setting (e.g. <code>nyc3.digitaloceanspaces.com</code>). The default values can be used for other settings.</p>
<p>Going through the whole process of creating a new remote by running <code>rclone config</code>, each prompt should be answered as shown below:</p>
<pre><code>Storage&gt; s3
env_auth&gt; 1
access_key_id&gt; YOUR_ACCESS_KEY
secret_access_key&gt; YOUR_SECRET_KEY
region&gt;
endpoint&gt; nyc3.digitaloceanspaces.com
location_constraint&gt;
acl&gt;
storage_class&gt;</code></pre>
<p>The resulting configuration file should look like:</p>
<pre><code>[spaces]
type = s3
provider = DigitalOcean
env_auth = false
access_key_id = YOUR_ACCESS_KEY
secret_access_key = YOUR_SECRET_KEY
region =
endpoint = nyc3.digitaloceanspaces.com
location_constraint =
acl =
server_side_encryption =
storage_class =</code></pre>
<p>Once configured, you can create a new Space and begin copying files. For example:</p>
<pre><code>rclone mkdir spaces:my-new-space
rclone copy /path/to/files spaces:my-new-space</code></pre>
<h3 id="huawei-obs">Huawei OBS</h3>
<p>Object Storage Service (OBS) provides stable, secure, efficient, and easy-to-use cloud storage that lets you store virtually any volume of unstructured data in any format and access it from anywhere.</p>
<p>OBS provides an S3 interface, you can copy and modify the following configuration and add it to your rclone configuration file.</p>
<pre><code>[obs]
type = s3
provider = HuaweiOBS
access_key_id = your-access-key-id
secret_access_key = your-secret-access-key
region = af-south-1
endpoint = obs.af-south-1.myhuaweicloud.com
acl = private</code></pre>
<p>Or you can also configure via the interactive command line:</p>
<pre><code>No remotes found, make a new one?
n) New remote
s) Set configuration password
q) Quit config
n/s/q&gt; n
name&gt; obs
Option Storage.
Type of storage to configure.
Choose a number from below, or type in your own value.
[snip]
XX / Amazon S3 Compliant Storage Providers including AWS, ...
   \ (s3)
[snip]
Storage&gt; s3
Option provider.
Choose your S3 provider.
Choose a number from below, or type in your own value.
Press Enter to leave empty.
[snip]
 9 / Huawei Object Storage Service
   \ (HuaweiOBS)
[snip]
provider&gt; 9
Option env_auth.
Get AWS credentials from runtime (environment variables or EC2/ECS meta data if no env vars).
Only applies if access_key_id and secret_access_key is blank.
Choose a number from below, or type in your own boolean value (true or false).
Press Enter for the default (false).
 1 / Enter AWS credentials in the next step.
   \ (false)
 2 / Get AWS credentials from the environment (env vars or IAM).
   \ (true)
env_auth&gt; 1
Option access_key_id.
AWS Access Key ID.
Leave blank for anonymous access or runtime credentials.
Enter a value. Press Enter to leave empty.
access_key_id&gt; your-access-key-id
Option secret_access_key.
AWS Secret Access Key (password).
Leave blank for anonymous access or runtime credentials.
Enter a value. Press Enter to leave empty.
secret_access_key&gt; your-secret-access-key
Option region.
Region to connect to.
Choose a number from below, or type in your own value.
Press Enter to leave empty.
 1 / AF-Johannesburg
   \ (af-south-1)
 2 / AP-Bangkok
   \ (ap-southeast-2)
[snip]
region&gt; 1
Option endpoint.
Endpoint for OBS API.
Choose a number from below, or type in your own value.
Press Enter to leave empty.
 1 / AF-Johannesburg
   \ (obs.af-south-1.myhuaweicloud.com)
 2 / AP-Bangkok
   \ (obs.ap-southeast-2.myhuaweicloud.com)
[snip]
endpoint&gt; 1
Option acl.
Canned ACL used when creating buckets and storing or copying objects.
This ACL is used for creating objects and if bucket_acl isn&#39;t set, for creating buckets too.
For more info visit https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html#canned-acl
Note that this ACL is applied when server-side copying objects as S3
doesn&#39;t copy the ACL from the source but rather writes a fresh one.
Choose a number from below, or type in your own value.
Press Enter to leave empty.
   / Owner gets FULL_CONTROL.
 1 | No one else has access rights (default).
   \ (private)
[snip]
acl&gt; 1
Edit advanced config?
y) Yes
n) No (default)
y/n&gt;
--------------------
[obs]
type = s3
provider = HuaweiOBS
access_key_id = your-access-key-id
secret_access_key = your-secret-access-key
region = af-south-1
endpoint = obs.af-south-1.myhuaweicloud.com
acl = private
--------------------
y) Yes this is OK (default)
e) Edit this remote
d) Delete this remote
y/e/d&gt; y
Current remotes:

Name                 Type
====                 ====
obs                  s3

e) Edit existing remote
n) New remote
d) Delete remote
r) Rename remote
c) Copy remote
s) Set configuration password
q) Quit config
e/n/d/r/c/s/q&gt; q</code></pre>
<h3 id="ibm-cos-s3">IBM COS (S3)</h3>
<p>Information stored with IBM Cloud Object Storage is encrypted and dispersed across multiple geographic locations, and accessed through an implementation of the S3 API. This service makes use of the distributed storage technologies provided by IBM’s Cloud Object Storage System (formerly Cleversafe). For more information visit: (http://www.ibm.com/cloud/object-storage)</p>
<p>To configure access to IBM COS S3, follow the steps below:</p>
<ol type="1">
<li>Run rclone config and select n for a new remote.</li>
</ol>
<pre><code>    2018/02/14 14:13:11 NOTICE: Config file &quot;C:\\Users\\a\\.config\\rclone\\rclone.conf&quot; not found - using defaults
    No remotes found, make a new one?
    n) New remote
    s) Set configuration password
    q) Quit config
    n/s/q&gt; n</code></pre>
<ol start="2" type="1">
<li>Enter the name for the configuration</li>
</ol>
<pre><code>    name&gt; &lt;YOUR NAME&gt;</code></pre>
<ol start="3" type="1">
<li>Select "s3" storage.</li>
</ol>
<pre><code>Choose a number from below, or type in your own value
[snip]
XX / Amazon S3 Compliant Storage Providers including AWS, ...
   \ &quot;s3&quot;
[snip]
Storage&gt; s3</code></pre>
<ol start="4" type="1">
<li>Select IBM COS as the S3 Storage Provider.</li>
</ol>
<pre><code>Choose the S3 provider.
Choose a number from below, or type in your own value
     1 / Choose this option to configure Storage to AWS S3
       \ &quot;AWS&quot;
     2 / Choose this option to configure Storage to Ceph Systems
     \ &quot;Ceph&quot;
     3 /  Choose this option to configure Storage to Dreamhost
     \ &quot;Dreamhost&quot;
   4 / Choose this option to the configure Storage to IBM COS S3
     \ &quot;IBMCOS&quot;
     5 / Choose this option to the configure Storage to Minio
     \ &quot;Minio&quot;
     Provider&gt;4</code></pre>
<ol start="5" type="1">
<li>Enter the Access Key and Secret.</li>
</ol>
<pre><code>    AWS Access Key ID - leave blank for anonymous access or runtime credentials.
    access_key_id&gt; &lt;&gt;
    AWS Secret Access Key (password) - leave blank for anonymous access or runtime credentials.
    secret_access_key&gt; &lt;&gt;</code></pre>
<ol start="6" type="1">
<li>Specify the endpoint for IBM COS. For Public IBM COS, choose from the option below. For On Premise IBM COS, enter an endpoint address.</li>
</ol>
<pre><code>    Endpoint for IBM COS S3 API.
    Specify if using an IBM COS On Premise.
    Choose a number from below, or type in your own value
     1 / US Cross Region Endpoint
       \ &quot;s3-api.us-geo.objectstorage.softlayer.net&quot;
     2 / US Cross Region Dallas Endpoint
       \ &quot;s3-api.dal.us-geo.objectstorage.softlayer.net&quot;
     3 / US Cross Region Washington DC Endpoint
       \ &quot;s3-api.wdc-us-geo.objectstorage.softlayer.net&quot;
     4 / US Cross Region San Jose Endpoint
       \ &quot;s3-api.sjc-us-geo.objectstorage.softlayer.net&quot;
     5 / US Cross Region Private Endpoint
       \ &quot;s3-api.us-geo.objectstorage.service.networklayer.com&quot;
     6 / US Cross Region Dallas Private Endpoint
       \ &quot;s3-api.dal-us-geo.objectstorage.service.networklayer.com&quot;
     7 / US Cross Region Washington DC Private Endpoint
       \ &quot;s3-api.wdc-us-geo.objectstorage.service.networklayer.com&quot;
     8 / US Cross Region San Jose Private Endpoint
       \ &quot;s3-api.sjc-us-geo.objectstorage.service.networklayer.com&quot;
     9 / US Region East Endpoint
       \ &quot;s3.us-east.objectstorage.softlayer.net&quot;
    10 / US Region East Private Endpoint
       \ &quot;s3.us-east.objectstorage.service.networklayer.com&quot;
    11 / US Region South Endpoint
[snip]
    34 / Toronto Single Site Private Endpoint
       \ &quot;s3.tor01.objectstorage.service.networklayer.com&quot;
    endpoint&gt;1</code></pre>
<ol start="7" type="1">
<li>Specify a IBM COS Location Constraint. The location constraint must match endpoint when using IBM Cloud Public. For on-prem COS, do not make a selection from this list, hit enter</li>
</ol>
<pre><code>     1 / US Cross Region Standard
       \ &quot;us-standard&quot;
     2 / US Cross Region Vault
       \ &quot;us-vault&quot;
     3 / US Cross Region Cold
       \ &quot;us-cold&quot;
     4 / US Cross Region Flex
       \ &quot;us-flex&quot;
     5 / US East Region Standard
       \ &quot;us-east-standard&quot;
     6 / US East Region Vault
       \ &quot;us-east-vault&quot;
     7 / US East Region Cold
       \ &quot;us-east-cold&quot;
     8 / US East Region Flex
       \ &quot;us-east-flex&quot;
     9 / US South Region Standard
       \ &quot;us-south-standard&quot;
    10 / US South Region Vault
       \ &quot;us-south-vault&quot;
[snip]
    32 / Toronto Flex
       \ &quot;tor01-flex&quot;
location_constraint&gt;1</code></pre>
<ol start="9" type="1">
<li>Specify a canned ACL. IBM Cloud (Storage) supports "public-read" and "private". IBM Cloud(Infra) supports all the canned ACLs. On-Premise COS supports all the canned ACLs.</li>
</ol>
<pre><code>Canned ACL used when creating buckets and/or storing objects in S3.
For more info visit https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html#canned-acl
Choose a number from below, or type in your own value
      1 / Owner gets FULL_CONTROL. No one else has access rights (default). This acl is available on IBM Cloud (Infra), IBM Cloud (Storage), On-Premise COS
      \ &quot;private&quot;
      2  / Owner gets FULL_CONTROL. The AllUsers group gets READ access. This acl is available on IBM Cloud (Infra), IBM Cloud (Storage), On-Premise IBM COS
      \ &quot;public-read&quot;
      3 / Owner gets FULL_CONTROL. The AllUsers group gets READ and WRITE access. This acl is available on IBM Cloud (Infra), On-Premise IBM COS
      \ &quot;public-read-write&quot;
      4  / Owner gets FULL_CONTROL. The AuthenticatedUsers group gets READ access. Not supported on Buckets. This acl is available on IBM Cloud (Infra) and On-Premise IBM COS
      \ &quot;authenticated-read&quot;
acl&gt; 1</code></pre>
<ol start="12" type="1">
<li>Review the displayed configuration and accept to save the "remote" then quit. The config file should look like this</li>
</ol>
<pre><code>    [xxx]
    type = s3
    Provider = IBMCOS
    access_key_id = xxx
    secret_access_key = yyy
    endpoint = s3-api.us-geo.objectstorage.softlayer.net
    location_constraint = us-standard
    acl = private</code></pre>
<ol start="13" type="1">
<li>Execute rclone commands</li>
</ol>
<pre><code>    1)  Create a bucket.
        rclone mkdir IBM-COS-XREGION:newbucket
    2)  List available buckets.
        rclone lsd IBM-COS-XREGION:
        -1 2017-11-08 21:16:22        -1 test
        -1 2018-02-14 20:16:39        -1 newbucket
    3)  List contents of a bucket.
        rclone ls IBM-COS-XREGION:newbucket
        18685952 test.exe
    4)  Copy a file from local to remote.
        rclone copy /Users/file.txt IBM-COS-XREGION:newbucket
    5)  Copy a file from remote to local.
        rclone copy IBM-COS-XREGION:newbucket/file.txt .
    6)  Delete a file on remote.
        rclone delete IBM-COS-XREGION:newbucket/file.txt</code></pre>
<h3 id="idrive-e2">IDrive e2</h3>
<p>Here is an example of making an <a href="https://www.idrive.com/e2/">IDrive e2</a> configuration. First run:</p>
<pre><code>rclone config</code></pre>
<p>This will guide you through an interactive setup process.</p>
<pre><code>No remotes found, make a new one?
n) New remote
s) Set configuration password
q) Quit config
n/s/q&gt; n

Enter name for new remote.
name&gt; e2

Option Storage.
Type of storage to configure.
Choose a number from below, or type in your own value.
[snip]
XX / Amazon S3 Compliant Storage Providers including AWS, ...
   \ (s3)
[snip]
Storage&gt; s3

Option provider.
Choose your S3 provider.
Choose a number from below, or type in your own value.
Press Enter to leave empty.
[snip]
XX / IDrive e2
   \ (IDrive)
[snip]
provider&gt; IDrive

Option env_auth.
Get AWS credentials from runtime (environment variables or EC2/ECS meta data if no env vars).
Only applies if access_key_id and secret_access_key is blank.
Choose a number from below, or type in your own boolean value (true or false).
Press Enter for the default (false).
 1 / Enter AWS credentials in the next step.
   \ (false)
 2 / Get AWS credentials from the environment (env vars or IAM).
   \ (true)
env_auth&gt; 

Option access_key_id.
AWS Access Key ID.
Leave blank for anonymous access or runtime credentials.
Enter a value. Press Enter to leave empty.
access_key_id&gt; YOUR_ACCESS_KEY

Option secret_access_key.
AWS Secret Access Key (password).
Leave blank for anonymous access or runtime credentials.
Enter a value. Press Enter to leave empty.
secret_access_key&gt; YOUR_SECRET_KEY

Option acl.
Canned ACL used when creating buckets and storing or copying objects.
This ACL is used for creating objects and if bucket_acl isn&#39;t set, for creating buckets too.
For more info visit https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html#canned-acl
Note that this ACL is applied when server-side copying objects as S3
doesn&#39;t copy the ACL from the source but rather writes a fresh one.
Choose a number from below, or type in your own value.
Press Enter to leave empty.
   / Owner gets FULL_CONTROL.
 1 | No one else has access rights (default).
   \ (private)
   / Owner gets FULL_CONTROL.
 2 | The AllUsers group gets READ access.
   \ (public-read)
   / Owner gets FULL_CONTROL.
 3 | The AllUsers group gets READ and WRITE access.
   | Granting this on a bucket is generally not recommended.
   \ (public-read-write)
   / Owner gets FULL_CONTROL.
 4 | The AuthenticatedUsers group gets READ access.
   \ (authenticated-read)
   / Object owner gets FULL_CONTROL.
 5 | Bucket owner gets READ access.
   | If you specify this canned ACL when creating a bucket, Amazon S3 ignores it.
   \ (bucket-owner-read)
   / Both the object owner and the bucket owner get FULL_CONTROL over the object.
 6 | If you specify this canned ACL when creating a bucket, Amazon S3 ignores it.
   \ (bucket-owner-full-control)
acl&gt; 

Edit advanced config?
y) Yes
n) No (default)
y/n&gt; 

Configuration complete.
Options:
- type: s3
- provider: IDrive
- access_key_id: YOUR_ACCESS_KEY
- secret_access_key: YOUR_SECRET_KEY
- endpoint: q9d9.la12.idrivee2-5.com
Keep this &quot;e2&quot; remote?
y) Yes this is OK (default)
e) Edit this remote
d) Delete this remote
y/e/d&gt; y</code></pre>
<h3 id="ionos">IONOS Cloud</h3>
<p><a href="https://cloud.ionos.com/storage/object-storage">IONOS S3 Object Storage</a> is a service offered by IONOS for storing and accessing unstructured data. To connect to the service, you will need an access key and a secret key. These can be found in the <a href="https://dcd.ionos.com/">Data Center Designer</a>, by selecting <strong>Manager resources</strong> &gt; <strong>Object Storage Key Manager</strong>.</p>
<p>Here is an example of a configuration. First, run <code>rclone config</code>. This will walk you through an interactive setup process. Type <code>n</code> to add the new remote, and then enter a name:</p>
<pre><code>Enter name for new remote.
name&gt; ionos-fra</code></pre>
<p>Type <code>s3</code> to choose the connection type:</p>
<pre><code>Option Storage.
Type of storage to configure.
Choose a number from below, or type in your own value.
[snip]
XX / Amazon S3 Compliant Storage Providers including AWS, ...
   \ (s3)
[snip]
Storage&gt; s3</code></pre>
<p>Type <code>IONOS</code>:</p>
<pre><code>Option provider.
Choose your S3 provider.
Choose a number from below, or type in your own value.
Press Enter to leave empty.
[snip]
XX / IONOS Cloud
   \ (IONOS)
[snip]
provider&gt; IONOS</code></pre>
<p>Press Enter to choose the default option <code>Enter AWS credentials in the next step</code>:</p>
<pre><code>Option env_auth.
Get AWS credentials from runtime (environment variables or EC2/ECS meta data if no env vars).
Only applies if access_key_id and secret_access_key is blank.
Choose a number from below, or type in your own boolean value (true or false).
Press Enter for the default (false).
 1 / Enter AWS credentials in the next step.
   \ (false)
 2 / Get AWS credentials from the environment (env vars or IAM).
   \ (true)
env_auth&gt;</code></pre>
<p>Enter your Access Key and Secret key. These can be retrieved in the <a href="https://dcd.ionos.com/">Data Center Designer</a>, click on the menu “Manager resources” / "Object Storage Key Manager".</p>
<pre><code>Option access_key_id.
AWS Access Key ID.
Leave blank for anonymous access or runtime credentials.
Enter a value. Press Enter to leave empty.
access_key_id&gt; YOUR_ACCESS_KEY

Option secret_access_key.
AWS Secret Access Key (password).
Leave blank for anonymous access or runtime credentials.
Enter a value. Press Enter to leave empty.
secret_access_key&gt; YOUR_SECRET_KEY</code></pre>
<p>Choose the region where your bucket is located:</p>
<pre><code>Option region.
Region where your bucket will be created and your data stored.
Choose a number from below, or type in your own value.
Press Enter to leave empty.
 1 / Frankfurt, Germany
   \ (de)
 2 / Berlin, Germany
   \ (eu-central-2)
 3 / Logrono, Spain
   \ (eu-south-2)
region&gt; 2</code></pre>
<p>Choose the endpoint from the same region:</p>
<pre><code>Option endpoint.
Endpoint for IONOS S3 Object Storage.
Specify the endpoint from the same region.
Choose a number from below, or type in your own value.
Press Enter to leave empty.
 1 / Frankfurt, Germany
   \ (s3-eu-central-1.ionoscloud.com)
 2 / Berlin, Germany
   \ (s3-eu-central-2.ionoscloud.com)
 3 / Logrono, Spain
   \ (s3-eu-south-2.ionoscloud.com)
endpoint&gt; 1</code></pre>
<p>Press Enter to choose the default option or choose the desired ACL setting:</p>
<pre><code>Option acl.
Canned ACL used when creating buckets and storing or copying objects.
This ACL is used for creating objects and if bucket_acl isn&#39;t set, for creating buckets too.
For more info visit https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html#canned-acl
Note that this ACL is applied when server-side copying objects as S3
doesn&#39;t copy the ACL from the source but rather writes a fresh one.
Choose a number from below, or type in your own value.
Press Enter to leave empty.
   / Owner gets FULL_CONTROL.
 1 | No one else has access rights (default).
   \ (private)
   / Owner gets FULL_CONTROL.
[snip]
acl&gt;</code></pre>
<p>Press Enter to skip the advanced config:</p>
<pre><code>Edit advanced config?
y) Yes
n) No (default)
y/n&gt;</code></pre>
<p>Press Enter to save the configuration, and then <code>q</code> to quit the configuration process:</p>
<pre><code>Configuration complete.
Options:
- type: s3
- provider: IONOS
- access_key_id: YOUR_ACCESS_KEY
- secret_access_key: YOUR_SECRET_KEY
- endpoint: s3-eu-central-1.ionoscloud.com
Keep this &quot;ionos-fra&quot; remote?
y) Yes this is OK (default)
e) Edit this remote
d) Delete this remote
y/e/d&gt; y</code></pre>
<p>Done! Now you can try some commands (for macOS, use <code>./rclone</code> instead of <code>rclone</code>).</p>
<ol type="1">
<li>Create a bucket (the name must be unique within the whole IONOS S3)</li>
</ol>
<pre><code>rclone mkdir ionos-fra:my-bucket</code></pre>
<ol start="2" type="1">
<li>List available buckets</li>
</ol>
<pre><code>rclone lsd ionos-fra:</code></pre>
<ol start="4" type="1">
<li>Copy a file from local to remote</li>
</ol>
<pre><code>rclone copy /Users/file.txt ionos-fra:my-bucket</code></pre>
<ol start="3" type="1">
<li>List contents of a bucket</li>
</ol>
<pre><code>rclone ls ionos-fra:my-bucket</code></pre>
<ol start="5" type="1">
<li>Copy a file from remote to local</li>
</ol>
<pre><code>rclone copy ionos-fra:my-bucket/file.txt</code></pre>
<h3 id="minio">Minio</h3>
<p><a href="https://minio.io/">Minio</a> is an object storage server built for cloud application developers and devops.</p>
<p>It is very easy to install and provides an S3 compatible server which can be used by rclone.</p>
<p>To use it, install Minio following the instructions <a href="https://docs.minio.io/docs/minio-quickstart-guide">here</a>.</p>
<p>When it configures itself Minio will print something like this</p>
<pre><code>Endpoint:  http://192.168.1.106:9000  http://172.23.0.1:9000
AccessKey: USWUXHGYZQYFYFFIT3RE
SecretKey: MOJRH0mkL1IPauahWITSVvyDrQbEEIwljvmxdq03
Region:    us-east-1
SQS ARNs:  arn:minio:sqs:us-east-1:1:redis arn:minio:sqs:us-east-1:2:redis

Browser Access:
   http://192.168.1.106:9000  http://172.23.0.1:9000

Command-line Access: https://docs.minio.io/docs/minio-client-quickstart-guide
   $ mc config host add myminio http://192.168.1.106:9000 USWUXHGYZQYFYFFIT3RE MOJRH0mkL1IPauahWITSVvyDrQbEEIwljvmxdq03

Object API (Amazon S3 compatible):
   Go:         https://docs.minio.io/docs/golang-client-quickstart-guide
   Java:       https://docs.minio.io/docs/java-client-quickstart-guide
   Python:     https://docs.minio.io/docs/python-client-quickstart-guide
   JavaScript: https://docs.minio.io/docs/javascript-client-quickstart-guide
   .NET:       https://docs.minio.io/docs/dotnet-client-quickstart-guide

Drive Capacity: 26 GiB Free, 165 GiB Total</code></pre>
<p>These details need to go into <code>rclone config</code> like this. Note that it is important to put the region in as stated above.</p>
<pre><code>env_auth&gt; 1
access_key_id&gt; USWUXHGYZQYFYFFIT3RE
secret_access_key&gt; MOJRH0mkL1IPauahWITSVvyDrQbEEIwljvmxdq03
region&gt; us-east-1
endpoint&gt; http://192.168.1.106:9000
location_constraint&gt;
server_side_encryption&gt;</code></pre>
<p>Which makes the config file look like this</p>
<pre><code>[minio]
type = s3
provider = Minio
env_auth = false
access_key_id = USWUXHGYZQYFYFFIT3RE
secret_access_key = MOJRH0mkL1IPauahWITSVvyDrQbEEIwljvmxdq03
region = us-east-1
endpoint = http://192.168.1.106:9000
location_constraint =
server_side_encryption =</code></pre>
<p>So once set up, for example, to copy files into a bucket</p>
<pre><code>rclone copy /path/to/files minio:bucket</code></pre>
<h3 id="qiniu">Qiniu Cloud Object Storage (Kodo)</h3>
<p><a href="https://www.qiniu.com/en/products/kodo">Qiniu Cloud Object Storage (Kodo)</a>, a completely independent-researched core technology which is proven by repeated customer experience has occupied absolute leading market leader position. Kodo can be widely applied to mass data management.</p>
<p>To configure access to Qiniu Kodo, follow the steps below:</p>
<ol type="1">
<li>Run <code>rclone config</code> and select <code>n</code> for a new remote.</li>
</ol>
<pre><code>rclone config
No remotes found, make a new one?
n) New remote
s) Set configuration password
q) Quit config
n/s/q&gt; n</code></pre>
<ol start="2" type="1">
<li>Give the name of the configuration. For example, name it 'qiniu'.</li>
</ol>
<pre><code>name&gt; qiniu</code></pre>
<ol start="3" type="1">
<li>Select <code>s3</code> storage.</li>
</ol>
<pre><code>Choose a number from below, or type in your own value
[snip]
XX / Amazon S3 Compliant Storage Providers including AWS, ...
   \ (s3)
[snip]
Storage&gt; s3</code></pre>
<ol start="4" type="1">
<li>Select <code>Qiniu</code> provider.</li>
</ol>
<pre><code>Choose a number from below, or type in your own value
1 / Amazon Web Services (AWS) S3
   \ &quot;AWS&quot;
[snip]
22 / Qiniu Object Storage (Kodo)
   \ (Qiniu)
[snip]
provider&gt; Qiniu</code></pre>
<ol start="5" type="1">
<li>Enter your SecretId and SecretKey of Qiniu Kodo.</li>
</ol>
<pre><code>Get AWS credentials from runtime (environment variables or EC2/ECS meta data if no env vars).
Only applies if access_key_id and secret_access_key is blank.
Enter a boolean value (true or false). Press Enter for the default (&quot;false&quot;).
Choose a number from below, or type in your own value
 1 / Enter AWS credentials in the next step
   \ &quot;false&quot;
 2 / Get AWS credentials from the environment (env vars or IAM)
   \ &quot;true&quot;
env_auth&gt; 1
AWS Access Key ID.
Leave blank for anonymous access or runtime credentials.
Enter a string value. Press Enter for the default (&quot;&quot;).
access_key_id&gt; AKIDxxxxxxxxxx
AWS Secret Access Key (password)
Leave blank for anonymous access or runtime credentials.
Enter a string value. Press Enter for the default (&quot;&quot;).
secret_access_key&gt; xxxxxxxxxxx</code></pre>
<ol start="6" type="1">
<li>Select endpoint for Qiniu Kodo. This is the standard endpoint for different region.</li>
</ol>
<pre><code>   / The default endpoint - a good choice if you are unsure.
 1 | East China Region 1.
   | Needs location constraint cn-east-1.
   \ (cn-east-1)
   / East China Region 2.
 2 | Needs location constraint cn-east-2.
   \ (cn-east-2)
   / North China Region 1.
 3 | Needs location constraint cn-north-1.
   \ (cn-north-1)
   / South China Region 1.
 4 | Needs location constraint cn-south-1.
   \ (cn-south-1)
   / North America Region.
 5 | Needs location constraint us-north-1.
   \ (us-north-1)
   / Southeast Asia Region 1.
 6 | Needs location constraint ap-southeast-1.
   \ (ap-southeast-1)
   / Northeast Asia Region 1.
 7 | Needs location constraint ap-northeast-1.
   \ (ap-northeast-1)
[snip]
endpoint&gt; 1

Option endpoint.
Endpoint for Qiniu Object Storage.
Choose a number from below, or type in your own value.
Press Enter to leave empty.
 1 / East China Endpoint 1
   \ (s3-cn-east-1.qiniucs.com)
 2 / East China Endpoint 2
   \ (s3-cn-east-2.qiniucs.com)
 3 / North China Endpoint 1
   \ (s3-cn-north-1.qiniucs.com)
 4 / South China Endpoint 1
   \ (s3-cn-south-1.qiniucs.com)
 5 / North America Endpoint 1
   \ (s3-us-north-1.qiniucs.com)
 6 / Southeast Asia Endpoint 1
   \ (s3-ap-southeast-1.qiniucs.com)
 7 / Northeast Asia Endpoint 1
   \ (s3-ap-northeast-1.qiniucs.com)
endpoint&gt; 1

Option location_constraint.
Location constraint - must be set to match the Region.
Used when creating buckets only.
Choose a number from below, or type in your own value.
Press Enter to leave empty.
 1 / East China Region 1
   \ (cn-east-1)
 2 / East China Region 2
   \ (cn-east-2)
 3 / North China Region 1
   \ (cn-north-1)
 4 / South China Region 1
   \ (cn-south-1)
 5 / North America Region 1
   \ (us-north-1)
 6 / Southeast Asia Region 1
   \ (ap-southeast-1)
 7 / Northeast Asia Region 1
   \ (ap-northeast-1)
location_constraint&gt; 1</code></pre>
<ol start="7" type="1">
<li>Choose acl and storage class.</li>
</ol>
<pre><code>Note that this ACL is applied when server-side copying objects as S3
doesn&#39;t copy the ACL from the source but rather writes a fresh one.
Enter a string value. Press Enter for the default (&quot;&quot;).
Choose a number from below, or type in your own value
   / Owner gets FULL_CONTROL.
 1 | No one else has access rights (default).
   \ (private)
   / Owner gets FULL_CONTROL.
 2 | The AllUsers group gets READ access.
   \ (public-read)
[snip]
acl&gt; 2
The storage class to use when storing new objects in Tencent COS.
Enter a string value. Press Enter for the default (&quot;&quot;).
Choose a number from below, or type in your own value
 1 / Standard storage class
   \ (STANDARD)
 2 / Infrequent access storage mode
   \ (LINE)
 3 / Archive storage mode
   \ (GLACIER)
 4 / Deep archive storage mode
   \ (DEEP_ARCHIVE)
[snip]
storage_class&gt; 1
Edit advanced config? (y/n)
y) Yes
n) No (default)
y/n&gt; n
Remote config
--------------------
[qiniu]
- type: s3
- provider: Qiniu
- access_key_id: xxx
- secret_access_key: xxx
- region: cn-east-1
- endpoint: s3-cn-east-1.qiniucs.com
- location_constraint: cn-east-1
- acl: public-read
- storage_class: STANDARD
--------------------
y) Yes this is OK (default)
e) Edit this remote
d) Delete this remote
y/e/d&gt; y
Current remotes:

Name                 Type
====                 ====
qiniu                s3</code></pre>
<h3 id="RackCorp">RackCorp</h3>
<p><a href="https://www.rackcorp.com/storage/s3storage">RackCorp Object Storage</a> is an S3 compatible object storage platform from your friendly cloud provider RackCorp. The service is fast, reliable, well priced and located in many strategic locations unserviced by others, to ensure you can maintain data sovereignty.</p>
<p>Before you can use RackCorp Object Storage, you'll need to "<a href="https://www.rackcorp.com/signup">sign up</a>" for an account on our "<a href="https://portal.rackcorp.com">portal</a>". Next you can create an <code>access key</code>, a <code>secret key</code> and <code>buckets</code>, in your location of choice with ease. These details are required for the next steps of configuration, when <code>rclone config</code> asks for your <code>access_key_id</code> and <code>secret_access_key</code>.</p>
<p>Your config should end up looking a bit like this:</p>
<pre><code>[RCS3-demo-config]
type = s3
provider = RackCorp
env_auth = true
access_key_id = YOURACCESSKEY
secret_access_key = YOURSECRETACCESSKEY
region = au-nsw
endpoint = s3.rackcorp.com
location_constraint = au-nsw</code></pre>
<h3 id="rclone">Rclone Serve S3</h3>
<p>Rclone can serve any remote over the S3 protocol. For details see the <a href="https://rclone.org/commands/rclone_serve_http/">rclone serve s3</a> documentation.</p>
<p>For example, to serve <code>remote:path</code> over s3, run the server like this:</p>
<pre><code>rclone serve s3 --auth-key ACCESS_KEY_ID,SECRET_ACCESS_KEY remote:path</code></pre>
<p>This will be compatible with an rclone remote which is defined like this:</p>
<pre><code>[serves3]
type = s3
provider = Rclone
endpoint = http://127.0.0.1:8080/
access_key_id = ACCESS_KEY_ID
secret_access_key = SECRET_ACCESS_KEY
use_multipart_uploads = false</code></pre>
<p>Note that setting <code>disable_multipart_uploads = true</code> is to work around <a href="https://rclone.org/commands/rclone_serve_http/#bugs">a bug</a> which will be fixed in due course.</p>
<h3 id="scaleway">Scaleway</h3>
<p><a href="https://www.scaleway.com/object-storage/">Scaleway</a> The Object Storage platform allows you to store anything from backups, logs and web assets to documents and photos. Files can be dropped from the Scaleway console or transferred through our API and CLI or using any S3-compatible tool.</p>
<p>Scaleway provides an S3 interface which can be configured for use with rclone like this:</p>
<pre><code>[scaleway]
type = s3
provider = Scaleway
env_auth = false
endpoint = s3.nl-ams.scw.cloud
access_key_id = SCWXXXXXXXXXXXXXX
secret_access_key = 1111111-2222-3333-44444-55555555555555
region = nl-ams
location_constraint = nl-ams
acl = private
upload_cutoff = 5M
chunk_size = 5M
copy_cutoff = 5M</code></pre>
<p><a href="https://www.scaleway.com/en/glacier-cold-storage/">Scaleway Glacier</a> is the low-cost S3 Glacier alternative from Scaleway and it works the same way as on S3 by accepting the "GLACIER" <code>storage_class</code>. So you can configure your remote with the <code>storage_class = GLACIER</code> option to upload directly to Scaleway Glacier. Don't forget that in this state you can't read files back after, you will need to restore them to "STANDARD" storage_class first before being able to read them (see "restore" section above)</p>
<h3 id="lyve">Seagate Lyve Cloud</h3>
<p><a href="https://www.seagate.com/gb/en/services/cloud/storage/">Seagate Lyve Cloud</a> is an S3 compatible object storage platform from <a href="https://seagate.com/">Seagate</a> intended for enterprise use.</p>
<p>Here is a config run through for a remote called <code>remote</code> - you may choose a different name of course. Note that to create an access key and secret key you will need to create a service account first.</p>
<pre><code>$ rclone config
No remotes found, make a new one?
n) New remote
s) Set configuration password
q) Quit config
n/s/q&gt; n
name&gt; remote</code></pre>
<p>Choose <code>s3</code> backend</p>
<pre><code>Type of storage to configure.
Choose a number from below, or type in your own value.
[snip]
XX / Amazon S3 Compliant Storage Providers including AWS, ...
   \ (s3)
[snip]
Storage&gt; s3</code></pre>
<p>Choose <code>LyveCloud</code> as S3 provider</p>
<pre><code>Choose your S3 provider.
Choose a number from below, or type in your own value.
Press Enter to leave empty.
[snip]
XX / Seagate Lyve Cloud
   \ (LyveCloud)
[snip]
provider&gt; LyveCloud</code></pre>
<p>Take the default (just press enter) to enter access key and secret in the config file.</p>
<pre><code>Get AWS credentials from runtime (environment variables or EC2/ECS meta data if no env vars).
Only applies if access_key_id and secret_access_key is blank.
Choose a number from below, or type in your own boolean value (true or false).
Press Enter for the default (false).
 1 / Enter AWS credentials in the next step.
   \ (false)
 2 / Get AWS credentials from the environment (env vars or IAM).
   \ (true)
env_auth&gt;</code></pre>
<pre><code>AWS Access Key ID.
Leave blank for anonymous access or runtime credentials.
Enter a value. Press Enter to leave empty.
access_key_id&gt; XXX</code></pre>
<pre><code>AWS Secret Access Key (password).
Leave blank for anonymous access or runtime credentials.
Enter a value. Press Enter to leave empty.
secret_access_key&gt; YYY</code></pre>
<p>Leave region blank</p>
<pre><code>Region to connect to.
Leave blank if you are using an S3 clone and you don&#39;t have a region.
Choose a number from below, or type in your own value.
Press Enter to leave empty.
   / Use this if unsure.
 1 | Will use v4 signatures and an empty region.
   \ ()
   / Use this only if v4 signatures don&#39;t work.
 2 | E.g. pre Jewel/v10 CEPH.
   \ (other-v2-signature)
region&gt;</code></pre>
<p>Choose an endpoint from the list</p>
<pre><code>Endpoint for S3 API.
Required when using an S3 clone.
Choose a number from below, or type in your own value.
Press Enter to leave empty.
 1 / Seagate Lyve Cloud US East 1 (Virginia)
   \ (s3.us-east-1.lyvecloud.seagate.com)
 2 / Seagate Lyve Cloud US West 1 (California)
   \ (s3.us-west-1.lyvecloud.seagate.com)
 3 / Seagate Lyve Cloud AP Southeast 1 (Singapore)
   \ (s3.ap-southeast-1.lyvecloud.seagate.com)
endpoint&gt; 1</code></pre>
<p>Leave location constraint blank</p>
<pre><code>Location constraint - must be set to match the Region.
Leave blank if not sure. Used when creating buckets only.
Enter a value. Press Enter to leave empty.
location_constraint&gt;</code></pre>
<p>Choose default ACL (<code>private</code>).</p>
<pre><code>Canned ACL used when creating buckets and storing or copying objects.
This ACL is used for creating objects and if bucket_acl isn&#39;t set, for creating buckets too.
For more info visit https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html#canned-acl
Note that this ACL is applied when server-side copying objects as S3
doesn&#39;t copy the ACL from the source but rather writes a fresh one.
Choose a number from below, or type in your own value.
Press Enter to leave empty.
   / Owner gets FULL_CONTROL.
 1 | No one else has access rights (default).
   \ (private)
[snip]
acl&gt;</code></pre>
<p>And the config file should end up looking like this:</p>
<pre><code>[remote]
type = s3
provider = LyveCloud
access_key_id = XXX
secret_access_key = YYY
endpoint = s3.us-east-1.lyvecloud.seagate.com</code></pre>
<h3 id="seaweedfs">SeaweedFS</h3>
<p><a href="https://github.com/chrislusf/seaweedfs/">SeaweedFS</a> is a distributed storage system for blobs, objects, files, and data lake, with O(1) disk seek and a scalable file metadata store. It has an S3 compatible object storage interface. SeaweedFS can also act as a <a href="https://github.com/chrislusf/seaweedfs/wiki/Gateway-to-Remote-Object-Storage">gateway to remote S3 compatible object store</a> to cache data and metadata with asynchronous write back, for fast local speed and minimize access cost.</p>
<p>Assuming the SeaweedFS are configured with <code>weed shell</code> as such:</p>
<pre><code>&gt; s3.bucket.create -name foo
&gt; s3.configure -access_key=any -secret_key=any -buckets=foo -user=me -actions=Read,Write,List,Tagging,Admin -apply
{
  &quot;identities&quot;: [
    {
      &quot;name&quot;: &quot;me&quot;,
      &quot;credentials&quot;: [
        {
          &quot;accessKey&quot;: &quot;any&quot;,
          &quot;secretKey&quot;: &quot;any&quot;
        }
      ],
      &quot;actions&quot;: [
        &quot;Read:foo&quot;,
        &quot;Write:foo&quot;,
        &quot;List:foo&quot;,
        &quot;Tagging:foo&quot;,
        &quot;Admin:foo&quot;
      ]
    }
  ]
}</code></pre>
<p>To use rclone with SeaweedFS, above configuration should end up with something like this in your config:</p>
<pre><code>[seaweedfs_s3]
type = s3
provider = SeaweedFS
access_key_id = any
secret_access_key = any
endpoint = localhost:8333</code></pre>
<p>So once set up, for example to copy files into a bucket</p>
<pre><code>rclone copy /path/to/files seaweedfs_s3:foo</code></pre>
<h3 id="wasabi">Wasabi</h3>
<p><a href="https://wasabi.com">Wasabi</a> is a cloud-based object storage service for a broad range of applications and use cases. Wasabi is designed for individuals and organizations that require a high-performance, reliable, and secure data storage infrastructure at minimal cost.</p>
<p>Wasabi provides an S3 interface which can be configured for use with rclone like this.</p>
<pre><code>No remotes found, make a new one?
n) New remote
s) Set configuration password
n/s&gt; n
name&gt; wasabi
Type of storage to configure.
Choose a number from below, or type in your own value
[snip]
XX / Amazon S3 (also Dreamhost, Ceph, ChinaMobile, ArvanCloud, Minio, Liara)
   \ &quot;s3&quot;
[snip]
Storage&gt; s3
Get AWS credentials from runtime (environment variables or EC2/ECS meta data if no env vars). Only applies if access_key_id and secret_access_key is blank.
Choose a number from below, or type in your own value
 1 / Enter AWS credentials in the next step
   \ &quot;false&quot;
 2 / Get AWS credentials from the environment (env vars or IAM)
   \ &quot;true&quot;
env_auth&gt; 1
AWS Access Key ID - leave blank for anonymous access or runtime credentials.
access_key_id&gt; YOURACCESSKEY
AWS Secret Access Key (password) - leave blank for anonymous access or runtime credentials.
secret_access_key&gt; YOURSECRETACCESSKEY
Region to connect to.
Choose a number from below, or type in your own value
   / The default endpoint - a good choice if you are unsure.
 1 | US Region, Northern Virginia, or Pacific Northwest.
   | Leave location constraint empty.
   \ &quot;us-east-1&quot;
[snip]
region&gt; us-east-1
Endpoint for S3 API.
Leave blank if using AWS to use the default endpoint for the region.
Specify if using an S3 clone such as Ceph.
endpoint&gt; s3.wasabisys.com
Location constraint - must be set to match the Region. Used when creating buckets only.
Choose a number from below, or type in your own value
 1 / Empty for US Region, Northern Virginia, or Pacific Northwest.
   \ &quot;&quot;
[snip]
location_constraint&gt;
Canned ACL used when creating buckets and/or storing objects in S3.
For more info visit https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html#canned-acl
Choose a number from below, or type in your own value
 1 / Owner gets FULL_CONTROL. No one else has access rights (default).
   \ &quot;private&quot;
[snip]
acl&gt;
The server-side encryption algorithm used when storing this object in S3.
Choose a number from below, or type in your own value
 1 / None
   \ &quot;&quot;
 2 / AES256
   \ &quot;AES256&quot;
server_side_encryption&gt;
The storage class to use when storing objects in S3.
Choose a number from below, or type in your own value
 1 / Default
   \ &quot;&quot;
 2 / Standard storage class
   \ &quot;STANDARD&quot;
 3 / Reduced redundancy storage class
   \ &quot;REDUCED_REDUNDANCY&quot;
 4 / Standard Infrequent Access storage class
   \ &quot;STANDARD_IA&quot;
storage_class&gt;
Remote config
--------------------
[wasabi]
env_auth = false
access_key_id = YOURACCESSKEY
secret_access_key = YOURSECRETACCESSKEY
region = us-east-1
endpoint = s3.wasabisys.com
location_constraint =
acl =
server_side_encryption =
storage_class =
--------------------
y) Yes this is OK
e) Edit this remote
d) Delete this remote
y/e/d&gt; y</code></pre>
<p>This will leave the config file looking like this.</p>
<pre><code>[wasabi]
type = s3
provider = Wasabi
env_auth = false
access_key_id = YOURACCESSKEY
secret_access_key = YOURSECRETACCESSKEY
region =
endpoint = s3.wasabisys.com
location_constraint =
acl =
server_side_encryption =
storage_class =</code></pre>
<h3 id="alibaba-oss">Alibaba OSS</h3>
<p>Here is an example of making an <a href="https://www.alibabacloud.com/product/oss/">Alibaba Cloud (Aliyun) OSS</a> configuration. First run:</p>
<pre><code>rclone config</code></pre>
<p>This will guide you through an interactive setup process.</p>
<pre><code>No remotes found, make a new one?
n) New remote
s) Set configuration password
q) Quit config
n/s/q&gt; n
name&gt; oss
Type of storage to configure.
Enter a string value. Press Enter for the default (&quot;&quot;).
Choose a number from below, or type in your own value
[snip]
XX / Amazon S3 Compliant Storage Providers including AWS, ...
   \ &quot;s3&quot;
[snip]
Storage&gt; s3
Choose your S3 provider.
Enter a string value. Press Enter for the default (&quot;&quot;).
Choose a number from below, or type in your own value
 1 / Amazon Web Services (AWS) S3
   \ &quot;AWS&quot;
 2 / Alibaba Cloud Object Storage System (OSS) formerly Aliyun
   \ &quot;Alibaba&quot;
 3 / Ceph Object Storage
   \ &quot;Ceph&quot;
[snip]
provider&gt; Alibaba
Get AWS credentials from runtime (environment variables or EC2/ECS meta data if no env vars).
Only applies if access_key_id and secret_access_key is blank.
Enter a boolean value (true or false). Press Enter for the default (&quot;false&quot;).
Choose a number from below, or type in your own value
 1 / Enter AWS credentials in the next step
   \ &quot;false&quot;
 2 / Get AWS credentials from the environment (env vars or IAM)
   \ &quot;true&quot;
env_auth&gt; 1
AWS Access Key ID.
Leave blank for anonymous access or runtime credentials.
Enter a string value. Press Enter for the default (&quot;&quot;).
access_key_id&gt; accesskeyid
AWS Secret Access Key (password)
Leave blank for anonymous access or runtime credentials.
Enter a string value. Press Enter for the default (&quot;&quot;).
secret_access_key&gt; secretaccesskey
Endpoint for OSS API.
Enter a string value. Press Enter for the default (&quot;&quot;).
Choose a number from below, or type in your own value
 1 / East China 1 (Hangzhou)
   \ &quot;oss-cn-hangzhou.aliyuncs.com&quot;
 2 / East China 2 (Shanghai)
   \ &quot;oss-cn-shanghai.aliyuncs.com&quot;
 3 / North China 1 (Qingdao)
   \ &quot;oss-cn-qingdao.aliyuncs.com&quot;
[snip]
endpoint&gt; 1
Canned ACL used when creating buckets and storing or copying objects.

Note that this ACL is applied when server-side copying objects as S3
doesn&#39;t copy the ACL from the source but rather writes a fresh one.
Enter a string value. Press Enter for the default (&quot;&quot;).
Choose a number from below, or type in your own value
 1 / Owner gets FULL_CONTROL. No one else has access rights (default).
   \ &quot;private&quot;
 2 / Owner gets FULL_CONTROL. The AllUsers group gets READ access.
   \ &quot;public-read&quot;
   / Owner gets FULL_CONTROL. The AllUsers group gets READ and WRITE access.
[snip]
acl&gt; 1
The storage class to use when storing new objects in OSS.
Enter a string value. Press Enter for the default (&quot;&quot;).
Choose a number from below, or type in your own value
 1 / Default
   \ &quot;&quot;
 2 / Standard storage class
   \ &quot;STANDARD&quot;
 3 / Archive storage mode.
   \ &quot;GLACIER&quot;
 4 / Infrequent access storage mode.
   \ &quot;STANDARD_IA&quot;
storage_class&gt; 1
Edit advanced config? (y/n)
y) Yes
n) No
y/n&gt; n
Remote config
--------------------
[oss]
type = s3
provider = Alibaba
env_auth = false
access_key_id = accesskeyid
secret_access_key = secretaccesskey
endpoint = oss-cn-hangzhou.aliyuncs.com
acl = private
storage_class = Standard
--------------------
y) Yes this is OK
e) Edit this remote
d) Delete this remote
y/e/d&gt; y</code></pre>
<h3 id="china-mobile-ecloud-eos">China Mobile Ecloud Elastic Object Storage (EOS)</h3>
<p>Here is an example of making an <a href="https:///ecloud.10086.cn/home/product-introduction/eos/">China Mobile Ecloud Elastic Object Storage (EOS)</a> configuration. First run:</p>
<pre><code>rclone config</code></pre>
<p>This will guide you through an interactive setup process.</p>
<pre><code>No remotes found, make a new one?
n) New remote
s) Set configuration password
q) Quit config
n/s/q&gt; n
name&gt; ChinaMobile
Option Storage.
Type of storage to configure.
Choose a number from below, or type in your own value.
 ...
XX / Amazon S3 Compliant Storage Providers including AWS, ...
   \ (s3)
 ...
Storage&gt; s3
Option provider.
Choose your S3 provider.
Choose a number from below, or type in your own value.
Press Enter to leave empty.
 ...
 4 / China Mobile Ecloud Elastic Object Storage (EOS)
   \ (ChinaMobile)
 ...
provider&gt; ChinaMobile
Option env_auth.
Get AWS credentials from runtime (environment variables or EC2/ECS meta data if no env vars).
Only applies if access_key_id and secret_access_key is blank.
Choose a number from below, or type in your own boolean value (true or false).
Press Enter for the default (false).
 1 / Enter AWS credentials in the next step.
   \ (false)
 2 / Get AWS credentials from the environment (env vars or IAM).
   \ (true)
env_auth&gt;
Option access_key_id.
AWS Access Key ID.
Leave blank for anonymous access or runtime credentials.
Enter a value. Press Enter to leave empty.
access_key_id&gt; accesskeyid
Option secret_access_key.
AWS Secret Access Key (password).
Leave blank for anonymous access or runtime credentials.
Enter a value. Press Enter to leave empty.
secret_access_key&gt; secretaccesskey
Option endpoint.
Endpoint for China Mobile Ecloud Elastic Object Storage (EOS) API.
Choose a number from below, or type in your own value.
Press Enter to leave empty.
   / The default endpoint - a good choice if you are unsure.
 1 | East China (Suzhou)
   \ (eos-wuxi-1.cmecloud.cn)
 2 / East China (Jinan)
   \ (eos-jinan-1.cmecloud.cn)
 3 / East China (Hangzhou)
   \ (eos-ningbo-1.cmecloud.cn)
 4 / East China (Shanghai-1)
   \ (eos-shanghai-1.cmecloud.cn)
 5 / Central China (Zhengzhou)
   \ (eos-zhengzhou-1.cmecloud.cn)
 6 / Central China (Changsha-1)
   \ (eos-hunan-1.cmecloud.cn)
 7 / Central China (Changsha-2)
   \ (eos-zhuzhou-1.cmecloud.cn)
 8 / South China (Guangzhou-2)
   \ (eos-guangzhou-1.cmecloud.cn)
 9 / South China (Guangzhou-3)
   \ (eos-dongguan-1.cmecloud.cn)
10 / North China (Beijing-1)
   \ (eos-beijing-1.cmecloud.cn)
11 / North China (Beijing-2)
   \ (eos-beijing-2.cmecloud.cn)
12 / North China (Beijing-3)
   \ (eos-beijing-4.cmecloud.cn)
13 / North China (Huhehaote)
   \ (eos-huhehaote-1.cmecloud.cn)
14 / Southwest China (Chengdu)
   \ (eos-chengdu-1.cmecloud.cn)
15 / Southwest China (Chongqing)
   \ (eos-chongqing-1.cmecloud.cn)
16 / Southwest China (Guiyang)
   \ (eos-guiyang-1.cmecloud.cn)
17 / Nouthwest China (Xian)
   \ (eos-xian-1.cmecloud.cn)
18 / Yunnan China (Kunming)
   \ (eos-yunnan.cmecloud.cn)
19 / Yunnan China (Kunming-2)
   \ (eos-yunnan-2.cmecloud.cn)
20 / Tianjin China (Tianjin)
   \ (eos-tianjin-1.cmecloud.cn)
21 / Jilin China (Changchun)
   \ (eos-jilin-1.cmecloud.cn)
22 / Hubei China (Xiangyan)
   \ (eos-hubei-1.cmecloud.cn)
23 / Jiangxi China (Nanchang)
   \ (eos-jiangxi-1.cmecloud.cn)
24 / Gansu China (Lanzhou)
   \ (eos-gansu-1.cmecloud.cn)
25 / Shanxi China (Taiyuan)
   \ (eos-shanxi-1.cmecloud.cn)
26 / Liaoning China (Shenyang)
   \ (eos-liaoning-1.cmecloud.cn)
27 / Hebei China (Shijiazhuang)
   \ (eos-hebei-1.cmecloud.cn)
28 / Fujian China (Xiamen)
   \ (eos-fujian-1.cmecloud.cn)
29 / Guangxi China (Nanning)
   \ (eos-guangxi-1.cmecloud.cn)
30 / Anhui China (Huainan)
   \ (eos-anhui-1.cmecloud.cn)
endpoint&gt; 1
Option location_constraint.
Location constraint - must match endpoint.
Used when creating buckets only.
Choose a number from below, or type in your own value.
Press Enter to leave empty.
 1 / East China (Suzhou)
   \ (wuxi1)
 2 / East China (Jinan)
   \ (jinan1)
 3 / East China (Hangzhou)
   \ (ningbo1)
 4 / East China (Shanghai-1)
   \ (shanghai1)
 5 / Central China (Zhengzhou)
   \ (zhengzhou1)
 6 / Central China (Changsha-1)
   \ (hunan1)
 7 / Central China (Changsha-2)
   \ (zhuzhou1)
 8 / South China (Guangzhou-2)
   \ (guangzhou1)
 9 / South China (Guangzhou-3)
   \ (dongguan1)
10 / North China (Beijing-1)
   \ (beijing1)
11 / North China (Beijing-2)
   \ (beijing2)
12 / North China (Beijing-3)
   \ (beijing4)
13 / North China (Huhehaote)
   \ (huhehaote1)
14 / Southwest China (Chengdu)
   \ (chengdu1)
15 / Southwest China (Chongqing)
   \ (chongqing1)
16 / Southwest China (Guiyang)
   \ (guiyang1)
17 / Nouthwest China (Xian)
   \ (xian1)
18 / Yunnan China (Kunming)
   \ (yunnan)
19 / Yunnan China (Kunming-2)
   \ (yunnan2)
20 / Tianjin China (Tianjin)
   \ (tianjin1)
21 / Jilin China (Changchun)
   \ (jilin1)
22 / Hubei China (Xiangyan)
   \ (hubei1)
23 / Jiangxi China (Nanchang)
   \ (jiangxi1)
24 / Gansu China (Lanzhou)
   \ (gansu1)
25 / Shanxi China (Taiyuan)
   \ (shanxi1)
26 / Liaoning China (Shenyang)
   \ (liaoning1)
27 / Hebei China (Shijiazhuang)
   \ (hebei1)
28 / Fujian China (Xiamen)
   \ (fujian1)
29 / Guangxi China (Nanning)
   \ (guangxi1)
30 / Anhui China (Huainan)
   \ (anhui1)
location_constraint&gt; 1
Option acl.
Canned ACL used when creating buckets and storing or copying objects.
This ACL is used for creating objects and if bucket_acl isn&#39;t set, for creating buckets too.
For more info visit https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html#canned-acl
Note that this ACL is applied when server-side copying objects as S3
doesn&#39;t copy the ACL from the source but rather writes a fresh one.
Choose a number from below, or type in your own value.
Press Enter to leave empty.
   / Owner gets FULL_CONTROL.
 1 | No one else has access rights (default).
   \ (private)
   / Owner gets FULL_CONTROL.
 2 | The AllUsers group gets READ access.
   \ (public-read)
   / Owner gets FULL_CONTROL.
 3 | The AllUsers group gets READ and WRITE access.
   | Granting this on a bucket is generally not recommended.
   \ (public-read-write)
   / Owner gets FULL_CONTROL.
 4 | The AuthenticatedUsers group gets READ access.
   \ (authenticated-read)
   / Object owner gets FULL_CONTROL.
acl&gt; private
Option server_side_encryption.
The server-side encryption algorithm used when storing this object in S3.
Choose a number from below, or type in your own value.
Press Enter to leave empty.
 1 / None
   \ ()
 2 / AES256
   \ (AES256)
server_side_encryption&gt;
Option storage_class.
The storage class to use when storing new objects in ChinaMobile.
Choose a number from below, or type in your own value.
Press Enter to leave empty.
 1 / Default
   \ ()
 2 / Standard storage class
   \ (STANDARD)
 3 / Archive storage mode
   \ (GLACIER)
 4 / Infrequent access storage mode
   \ (STANDARD_IA)
storage_class&gt;
Edit advanced config?
y) Yes
n) No (default)
y/n&gt; n
--------------------
[ChinaMobile]
type = s3
provider = ChinaMobile
access_key_id = accesskeyid
secret_access_key = secretaccesskey
endpoint = eos-wuxi-1.cmecloud.cn
location_constraint = wuxi1
acl = private
--------------------
y) Yes this is OK (default)
e) Edit this remote
d) Delete this remote
y/e/d&gt; y</code></pre>
<h3 id="leviia">Leviia Cloud Object Storage</h3>
<p><a href="https://www.leviia.com/object-storage/">Leviia Object Storage</a>, backup and secure your data in a 100% French cloud, independent of GAFAM..</p>
<p>To configure access to Leviia, follow the steps below:</p>
<ol type="1">
<li>Run <code>rclone config</code> and select <code>n</code> for a new remote.</li>
</ol>
<pre><code>rclone config
No remotes found, make a new one?
n) New remote
s) Set configuration password
q) Quit config
n/s/q&gt; n</code></pre>
<ol start="2" type="1">
<li>Give the name of the configuration. For example, name it 'leviia'.</li>
</ol>
<pre><code>name&gt; leviia</code></pre>
<ol start="3" type="1">
<li>Select <code>s3</code> storage.</li>
</ol>
<pre><code>Choose a number from below, or type in your own value
[snip]
XX / Amazon S3 Compliant Storage Providers including AWS, ...
   \ (s3)
[snip]
Storage&gt; s3</code></pre>
<ol start="4" type="1">
<li>Select <code>Leviia</code> provider.</li>
</ol>
<pre><code>Choose a number from below, or type in your own value
1 / Amazon Web Services (AWS) S3
   \ &quot;AWS&quot;
[snip]
15 / Leviia Object Storage
   \ (Leviia)
[snip]
provider&gt; Leviia</code></pre>
<ol start="5" type="1">
<li>Enter your SecretId and SecretKey of Leviia.</li>
</ol>
<pre><code>Get AWS credentials from runtime (environment variables or EC2/ECS meta data if no env vars).
Only applies if access_key_id and secret_access_key is blank.
Enter a boolean value (true or false). Press Enter for the default (&quot;false&quot;).
Choose a number from below, or type in your own value
 1 / Enter AWS credentials in the next step
   \ &quot;false&quot;
 2 / Get AWS credentials from the environment (env vars or IAM)
   \ &quot;true&quot;
env_auth&gt; 1
AWS Access Key ID.
Leave blank for anonymous access or runtime credentials.
Enter a string value. Press Enter for the default (&quot;&quot;).
access_key_id&gt; ZnIx.xxxxxxxxxxxxxxx
AWS Secret Access Key (password)
Leave blank for anonymous access or runtime credentials.
Enter a string value. Press Enter for the default (&quot;&quot;).
secret_access_key&gt; xxxxxxxxxxx</code></pre>
<ol start="6" type="1">
<li>Select endpoint for Leviia.</li>
</ol>
<pre><code>   / The default endpoint
 1 | Leviia.
   \ (s3.leviia.com)
[snip]
endpoint&gt; 1</code></pre>
<ol start="7" type="1">
<li>Choose acl.</li>
</ol>
<pre><code>Note that this ACL is applied when server-side copying objects as S3
doesn&#39;t copy the ACL from the source but rather writes a fresh one.
Enter a string value. Press Enter for the default (&quot;&quot;).
Choose a number from below, or type in your own value
   / Owner gets FULL_CONTROL.
 1 | No one else has access rights (default).
   \ (private)
   / Owner gets FULL_CONTROL.
 2 | The AllUsers group gets READ access.
   \ (public-read)
[snip]
acl&gt; 1
Edit advanced config? (y/n)
y) Yes
n) No (default)
y/n&gt; n
Remote config
--------------------
[leviia]
- type: s3
- provider: Leviia
- access_key_id: ZnIx.xxxxxxx
- secret_access_key: xxxxxxxx
- endpoint: s3.leviia.com
- acl: private
--------------------
y) Yes this is OK (default)
e) Edit this remote
d) Delete this remote
y/e/d&gt; y
Current remotes:

Name                 Type
====                 ====
leviia                s3</code></pre>
<h3 id="liara-cloud">Liara</h3>
<p>Here is an example of making a <a href="https://liara.ir/landing/object-storage">Liara Object Storage</a> configuration. First run:</p>
<pre><code>rclone config</code></pre>
<p>This will guide you through an interactive setup process.</p>
<pre><code>No remotes found, make a new one?
n) New remote
s) Set configuration password
n/s&gt; n
name&gt; Liara
Type of storage to configure.
Choose a number from below, or type in your own value
[snip]
XX / Amazon S3 (also Dreamhost, Ceph, ChinaMobile, ArvanCloud, Liara, Minio)
   \ &quot;s3&quot;
[snip]
Storage&gt; s3
Get AWS credentials from runtime (environment variables or EC2/ECS meta data if no env vars). Only applies if access_key_id and secret_access_key is blank.
Choose a number from below, or type in your own value
 1 / Enter AWS credentials in the next step
   \ &quot;false&quot;
 2 / Get AWS credentials from the environment (env vars or IAM)
   \ &quot;true&quot;
env_auth&gt; 1
AWS Access Key ID - leave blank for anonymous access or runtime credentials.
access_key_id&gt; YOURACCESSKEY
AWS Secret Access Key (password) - leave blank for anonymous access or runtime credentials.
secret_access_key&gt; YOURSECRETACCESSKEY
Region to connect to.
Choose a number from below, or type in your own value
   / The default endpoint
 1 | US Region, Northern Virginia, or Pacific Northwest.
   | Leave location constraint empty.
   \ &quot;us-east-1&quot;
[snip]
region&gt;
Endpoint for S3 API.
Leave blank if using Liara to use the default endpoint for the region.
Specify if using an S3 clone such as Ceph.
endpoint&gt; storage.iran.liara.space
Canned ACL used when creating buckets and/or storing objects in S3.
For more info visit https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html#canned-acl
Choose a number from below, or type in your own value
 1 / Owner gets FULL_CONTROL. No one else has access rights (default).
   \ &quot;private&quot;
[snip]
acl&gt;
The server-side encryption algorithm used when storing this object in S3.
Choose a number from below, or type in your own value
 1 / None
   \ &quot;&quot;
 2 / AES256
   \ &quot;AES256&quot;
server_side_encryption&gt;
The storage class to use when storing objects in S3.
Choose a number from below, or type in your own value
 1 / Default
   \ &quot;&quot;
 2 / Standard storage class
   \ &quot;STANDARD&quot;
storage_class&gt;
Remote config
--------------------
[Liara]
env_auth = false
access_key_id = YOURACCESSKEY
secret_access_key = YOURSECRETACCESSKEY
endpoint = storage.iran.liara.space
location_constraint =
acl =
server_side_encryption =
storage_class =
--------------------
y) Yes this is OK
e) Edit this remote
d) Delete this remote
y/e/d&gt; y</code></pre>
<p>This will leave the config file looking like this.</p>
<pre><code>[Liara]
type = s3
provider = Liara
env_auth = false
access_key_id = YOURACCESSKEY
secret_access_key = YOURSECRETACCESSKEY
region =
endpoint = storage.iran.liara.space
location_constraint =
acl =
server_side_encryption =
storage_class =</code></pre>
<h3 id="linode">Linode</h3>
<p>Here is an example of making a <a href="https://www.linode.com/products/object-storage/">Linode Object Storage</a> configuration. First run:</p>
<pre><code>rclone config</code></pre>
<p>This will guide you through an interactive setup process.</p>
<pre><code>No remotes found, make a new one?
n) New remote
s) Set configuration password
q) Quit config
n/s/q&gt; n

Enter name for new remote.
name&gt; linode

Option Storage.
Type of storage to configure.
Choose a number from below, or type in your own value.
[snip]
XX / Amazon S3 Compliant Storage Providers including AWS, ...Linode, ...and others
   \ (s3)
[snip]
Storage&gt; s3

Option provider.
Choose your S3 provider.
Choose a number from below, or type in your own value.
Press Enter to leave empty.
[snip]
XX / Linode Object Storage
   \ (Linode)
[snip]
provider&gt; Linode

Option env_auth.
Get AWS credentials from runtime (environment variables or EC2/ECS meta data if no env vars).
Only applies if access_key_id and secret_access_key is blank.
Choose a number from below, or type in your own boolean value (true or false).
Press Enter for the default (false).
 1 / Enter AWS credentials in the next step.
   \ (false)
 2 / Get AWS credentials from the environment (env vars or IAM).
   \ (true)
env_auth&gt; 

Option access_key_id.
AWS Access Key ID.
Leave blank for anonymous access or runtime credentials.
Enter a value. Press Enter to leave empty.
access_key_id&gt; ACCESS_KEY

Option secret_access_key.
AWS Secret Access Key (password).
Leave blank for anonymous access or runtime credentials.
Enter a value. Press Enter to leave empty.
secret_access_key&gt; SECRET_ACCESS_KEY

Option endpoint.
Endpoint for Linode Object Storage API.
Choose a number from below, or type in your own value.
Press Enter to leave empty.
 1 / Atlanta, GA (USA), us-southeast-1
   \ (us-southeast-1.linodeobjects.com)
 2 / Chicago, IL (USA), us-ord-1
   \ (us-ord-1.linodeobjects.com)
 3 / Frankfurt (Germany), eu-central-1
   \ (eu-central-1.linodeobjects.com)
 4 / Milan (Italy), it-mil-1
   \ (it-mil-1.linodeobjects.com)
 5 / Newark, NJ (USA), us-east-1
   \ (us-east-1.linodeobjects.com)
 6 / Paris (France), fr-par-1
   \ (fr-par-1.linodeobjects.com)
 7 / Seattle, WA (USA), us-sea-1
   \ (us-sea-1.linodeobjects.com)
 8 / Singapore ap-south-1
   \ (ap-south-1.linodeobjects.com)
 9 / Stockholm (Sweden), se-sto-1
   \ (se-sto-1.linodeobjects.com)
10 / Washington, DC, (USA), us-iad-1
   \ (us-iad-1.linodeobjects.com)
endpoint&gt; 3

Option acl.
Canned ACL used when creating buckets and storing or copying objects.
This ACL is used for creating objects and if bucket_acl isn&#39;t set, for creating buckets too.
For more info visit https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html#canned-acl
Note that this ACL is applied when server-side copying objects as S3
doesn&#39;t copy the ACL from the source but rather writes a fresh one.
If the acl is an empty string then no X-Amz-Acl: header is added and
the default (private) will be used.
Choose a number from below, or type in your own value.
Press Enter to leave empty.
   / Owner gets FULL_CONTROL.
 1 | No one else has access rights (default).
   \ (private)
[snip]
acl&gt; 

Edit advanced config?
y) Yes
n) No (default)
y/n&gt; n

Configuration complete.
Options:
- type: s3
- provider: Linode
- access_key_id: ACCESS_KEY
- secret_access_key: SECRET_ACCESS_KEY
- endpoint: eu-central-1.linodeobjects.com
Keep this &quot;linode&quot; remote?
y) Yes this is OK (default)
e) Edit this remote
d) Delete this remote
y/e/d&gt; y</code></pre>
<p>This will leave the config file looking like this.</p>
<pre><code>[linode]
type = s3
provider = Linode
access_key_id = ACCESS_KEY
secret_access_key = SECRET_ACCESS_KEY
endpoint = eu-central-1.linodeobjects.com</code></pre>
<h3 id="magalu">Magalu</h3>
<p>Here is an example of making a <a href="https://magalu.cloud/object-storage/">Magalu Object Storage</a> configuration. First run:</p>
<pre><code>rclone config</code></pre>
<p>This will guide you through an interactive setup process.</p>
<pre><code>No remotes found, make a new one?
n) New remote
s) Set configuration password
q) Quit config
n/s/q&gt; n

Enter name for new remote.
name&gt; magalu

Option Storage.
Type of storage to configure.
Choose a number from below, or type in your own value.
[snip]
XX / Amazon S3 Compliant Storage Providers including AWS, ...Magalu, ...and others
   \ (s3)
[snip]
Storage&gt; s3

Option provider.
Choose your S3 provider.
Choose a number from below, or type in your own value.
Press Enter to leave empty.
[snip]
XX / Magalu Object Storage
   \ (Magalu)
[snip]
provider&gt; Magalu

Option env_auth.
Get AWS credentials from runtime (environment variables or EC2/ECS meta data if no env vars).
Only applies if access_key_id and secret_access_key is blank.
Choose a number from below, or type in your own boolean value (true or false).
Press Enter for the default (false).
 1 / Enter AWS credentials in the next step.
   \ (false)
 2 / Get AWS credentials from the environment (env vars or IAM).
   \ (true)
env_auth&gt; 1

Option access_key_id.
AWS Access Key ID.
Leave blank for anonymous access or runtime credentials.
Enter a value. Press Enter to leave empty.
access_key_id&gt; ACCESS_KEY

Option secret_access_key.
AWS Secret Access Key (password).
Leave blank for anonymous access or runtime credentials.
Enter a value. Press Enter to leave empty.
secret_access_key&gt; SECRET_ACCESS_KEY

Option endpoint.
Endpoint for Magalu Object Storage API.
Choose a number from below, or type in your own value.
Press Enter to leave empty.
 1 / São Paulo, SP (BR), br-se1
   \ (br-se1.magaluobjects.com)
 2 / Fortaleza, CE (BR), br-ne1
   \ (br-ne1.magaluobjects.com)
endpoint&gt; 2

Option acl.
Canned ACL used when creating buckets and storing or copying objects.
This ACL is used for creating objects and if bucket_acl isn&#39;t set, for creating buckets too.
For more info visit https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html#canned-acl
Note that this ACL is applied when server-side copying objects as S3
doesn&#39;t copy the ACL from the source but rather writes a fresh one.
If the acl is an empty string then no X-Amz-Acl: header is added and
the default (private) will be used.
Choose a number from below, or type in your own value.
Press Enter to leave empty.
   / Owner gets FULL_CONTROL.
 1 | No one else has access rights (default).
   \ (private)
[snip]
acl&gt; 

Edit advanced config?
y) Yes
n) No (default)
y/n&gt; n

Configuration complete.
Options:
- type: s3
- provider: magalu
- access_key_id: ACCESS_KEY
- secret_access_key: SECRET_ACCESS_KEY
- endpoint: br-ne1.magaluobjects.com
Keep this &quot;magalu&quot; remote?
y) Yes this is OK (default)
e) Edit this remote
d) Delete this remote
y/e/d&gt; y</code></pre>
<p>This will leave the config file looking like this.</p>
<pre><code>[magalu]
type = s3
provider = Magalu
access_key_id = ACCESS_KEY
secret_access_key = SECRET_ACCESS_KEY
endpoint = br-ne1.magaluobjects.com</code></pre>
<h3 id="arvan-cloud">ArvanCloud</h3>
<p><a href="https://www.arvancloud.com/en/products/cloud-storage">ArvanCloud</a> ArvanCloud Object Storage goes beyond the limited traditional file storage. It gives you access to backup and archived files and allows sharing. Files like profile image in the app, images sent by users or scanned documents can be stored securely and easily in our Object Storage service.</p>
<p>ArvanCloud provides an S3 interface which can be configured for use with rclone like this.</p>
<pre><code>No remotes found, make a new one?
n) New remote
s) Set configuration password
n/s&gt; n
name&gt; ArvanCloud
Type of storage to configure.
Choose a number from below, or type in your own value
[snip]
XX / Amazon S3 (also Dreamhost, Ceph, ChinaMobile, ArvanCloud, Liara, Minio)
   \ &quot;s3&quot;
[snip]
Storage&gt; s3
Get AWS credentials from runtime (environment variables or EC2/ECS meta data if no env vars). Only applies if access_key_id and secret_access_key is blank.
Choose a number from below, or type in your own value
 1 / Enter AWS credentials in the next step
   \ &quot;false&quot;
 2 / Get AWS credentials from the environment (env vars or IAM)
   \ &quot;true&quot;
env_auth&gt; 1
AWS Access Key ID - leave blank for anonymous access or runtime credentials.
access_key_id&gt; YOURACCESSKEY
AWS Secret Access Key (password) - leave blank for anonymous access or runtime credentials.
secret_access_key&gt; YOURSECRETACCESSKEY
Region to connect to.
Choose a number from below, or type in your own value
   / The default endpoint - a good choice if you are unsure.
 1 | US Region, Northern Virginia, or Pacific Northwest.
   | Leave location constraint empty.
   \ &quot;us-east-1&quot;
[snip]
region&gt; 
Endpoint for S3 API.
Leave blank if using ArvanCloud to use the default endpoint for the region.
Specify if using an S3 clone such as Ceph.
endpoint&gt; s3.arvanstorage.com
Location constraint - must be set to match the Region. Used when creating buckets only.
Choose a number from below, or type in your own value
 1 / Empty for Iran-Tehran Region.
   \ &quot;&quot;
[snip]
location_constraint&gt;
Canned ACL used when creating buckets and/or storing objects in S3.
For more info visit https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html#canned-acl
Choose a number from below, or type in your own value
 1 / Owner gets FULL_CONTROL. No one else has access rights (default).
   \ &quot;private&quot;
[snip]
acl&gt;
The server-side encryption algorithm used when storing this object in S3.
Choose a number from below, or type in your own value
 1 / None
   \ &quot;&quot;
 2 / AES256
   \ &quot;AES256&quot;
server_side_encryption&gt;
The storage class to use when storing objects in S3.
Choose a number from below, or type in your own value
 1 / Default
   \ &quot;&quot;
 2 / Standard storage class
   \ &quot;STANDARD&quot;
storage_class&gt;
Remote config
--------------------
[ArvanCloud]
env_auth = false
access_key_id = YOURACCESSKEY
secret_access_key = YOURSECRETACCESSKEY
region = ir-thr-at1
endpoint = s3.arvanstorage.com
location_constraint =
acl =
server_side_encryption =
storage_class =
--------------------
y) Yes this is OK
e) Edit this remote
d) Delete this remote
y/e/d&gt; y</code></pre>
<p>This will leave the config file looking like this.</p>
<pre><code>[ArvanCloud]
type = s3
provider = ArvanCloud
env_auth = false
access_key_id = YOURACCESSKEY
secret_access_key = YOURSECRETACCESSKEY
region =
endpoint = s3.arvanstorage.com
location_constraint =
acl =
server_side_encryption =
storage_class =</code></pre>
<h3 id="tencent-cos">Tencent COS</h3>
<p><a href="https://intl.cloud.tencent.com/product/cos">Tencent Cloud Object Storage (COS)</a> is a distributed storage service offered by Tencent Cloud for unstructured data. It is secure, stable, massive, convenient, low-delay and low-cost.</p>
<p>To configure access to Tencent COS, follow the steps below:</p>
<ol type="1">
<li>Run <code>rclone config</code> and select <code>n</code> for a new remote.</li>
</ol>
<pre><code>rclone config
No remotes found, make a new one?
n) New remote
s) Set configuration password
q) Quit config
n/s/q&gt; n</code></pre>
<ol start="2" type="1">
<li>Give the name of the configuration. For example, name it 'cos'.</li>
</ol>
<pre><code>name&gt; cos</code></pre>
<ol start="3" type="1">
<li>Select <code>s3</code> storage.</li>
</ol>
<pre><code>Choose a number from below, or type in your own value
[snip]
XX / Amazon S3 Compliant Storage Providers including AWS, ...
   \ &quot;s3&quot;
[snip]
Storage&gt; s3</code></pre>
<ol start="4" type="1">
<li>Select <code>TencentCOS</code> provider.</li>
</ol>
<pre><code>Choose a number from below, or type in your own value
1 / Amazon Web Services (AWS) S3
   \ &quot;AWS&quot;
[snip]
11 / Tencent Cloud Object Storage (COS)
   \ &quot;TencentCOS&quot;
[snip]
provider&gt; TencentCOS</code></pre>
<ol start="5" type="1">
<li>Enter your SecretId and SecretKey of Tencent Cloud.</li>
</ol>
<pre><code>Get AWS credentials from runtime (environment variables or EC2/ECS meta data if no env vars).
Only applies if access_key_id and secret_access_key is blank.
Enter a boolean value (true or false). Press Enter for the default (&quot;false&quot;).
Choose a number from below, or type in your own value
 1 / Enter AWS credentials in the next step
   \ &quot;false&quot;
 2 / Get AWS credentials from the environment (env vars or IAM)
   \ &quot;true&quot;
env_auth&gt; 1
AWS Access Key ID.
Leave blank for anonymous access or runtime credentials.
Enter a string value. Press Enter for the default (&quot;&quot;).
access_key_id&gt; AKIDxxxxxxxxxx
AWS Secret Access Key (password)
Leave blank for anonymous access or runtime credentials.
Enter a string value. Press Enter for the default (&quot;&quot;).
secret_access_key&gt; xxxxxxxxxxx</code></pre>
<ol start="6" type="1">
<li>Select endpoint for Tencent COS. This is the standard endpoint for different region.</li>
</ol>
<pre><code> 1 / Beijing Region.
   \ &quot;cos.ap-beijing.myqcloud.com&quot;
 2 / Nanjing Region.
   \ &quot;cos.ap-nanjing.myqcloud.com&quot;
 3 / Shanghai Region.
   \ &quot;cos.ap-shanghai.myqcloud.com&quot;
 4 / Guangzhou Region.
   \ &quot;cos.ap-guangzhou.myqcloud.com&quot;
[snip]
endpoint&gt; 4</code></pre>
<ol start="7" type="1">
<li>Choose acl and storage class.</li>
</ol>
<pre><code>Note that this ACL is applied when server-side copying objects as S3
doesn&#39;t copy the ACL from the source but rather writes a fresh one.
Enter a string value. Press Enter for the default (&quot;&quot;).
Choose a number from below, or type in your own value
 1 / Owner gets Full_CONTROL. No one else has access rights (default).
   \ &quot;default&quot;
[snip]
acl&gt; 1
The storage class to use when storing new objects in Tencent COS.
Enter a string value. Press Enter for the default (&quot;&quot;).
Choose a number from below, or type in your own value
 1 / Default
   \ &quot;&quot;
[snip]
storage_class&gt; 1
Edit advanced config? (y/n)
y) Yes
n) No (default)
y/n&gt; n
Remote config
--------------------
[cos]
type = s3
provider = TencentCOS
env_auth = false
access_key_id = xxx
secret_access_key = xxx
endpoint = cos.ap-guangzhou.myqcloud.com
acl = default
--------------------
y) Yes this is OK (default)
e) Edit this remote
d) Delete this remote
y/e/d&gt; y
Current remotes:

Name                 Type
====                 ====
cos                  s3</code></pre>
<h3 id="netease-nos">Netease NOS</h3>
<p>For Netease NOS configure as per the configurator <code>rclone config</code> setting the provider <code>Netease</code>. This will automatically set <code>force_path_style = false</code> which is necessary for it to run properly.</p>
<h3 id="petabox">Petabox</h3>
<p>Here is an example of making a <a href="https://petabox.io/">Petabox</a> configuration. First run:</p>
<div class="sourceCode" id="cb969"><pre class="sourceCode bash"><code class="sourceCode bash"><span id="cb969-1"><a href="#cb969-1" aria-hidden="true"></a><span class="ex">rclone</span> config</span></code></pre></div>
<p>This will guide you through an interactive setup process.</p>
<pre><code>No remotes found, make a new one?
n) New remote
s) Set configuration password
n/s&gt; n

Enter name for new remote.
name&gt; My Petabox Storage

Option Storage.
Type of storage to configure.
Choose a number from below, or type in your own value.
[snip]
XX / Amazon S3 Compliant Storage Providers including AWS, ...
   \ &quot;s3&quot;
[snip]
Storage&gt; s3

Option provider.
Choose your S3 provider.
Choose a number from below, or type in your own value.
Press Enter to leave empty.
[snip]
XX / Petabox Object Storage
   \ (Petabox)
[snip]
provider&gt; Petabox

Option env_auth.
Get AWS credentials from runtime (environment variables or EC2/ECS meta data if no env vars).
Only applies if access_key_id and secret_access_key is blank.
Choose a number from below, or type in your own boolean value (true or false).
Press Enter for the default (false).
 1 / Enter AWS credentials in the next step.
   \ (false)
 2 / Get AWS credentials from the environment (env vars or IAM).
   \ (true)
env_auth&gt; 1

Option access_key_id.
AWS Access Key ID.
Leave blank for anonymous access or runtime credentials.
Enter a value. Press Enter to leave empty.
access_key_id&gt; YOUR_ACCESS_KEY_ID

Option secret_access_key.
AWS Secret Access Key (password).
Leave blank for anonymous access or runtime credentials.
Enter a value. Press Enter to leave empty.
secret_access_key&gt; YOUR_SECRET_ACCESS_KEY

Option region.
Region where your bucket will be created and your data stored.
Choose a number from below, or type in your own value.
Press Enter to leave empty.
 1 / US East (N. Virginia)
   \ (us-east-1)
 2 / Europe (Frankfurt)
   \ (eu-central-1)
 3 / Asia Pacific (Singapore)
   \ (ap-southeast-1)
 4 / Middle East (Bahrain)
   \ (me-south-1)
 5 / South America (São Paulo)
   \ (sa-east-1)
region&gt; 1

Option endpoint.
Endpoint for Petabox S3 Object Storage.
Specify the endpoint from the same region.
Choose a number from below, or type in your own value.
 1 / US East (N. Virginia)
   \ (s3.petabox.io)
 2 / US East (N. Virginia)
   \ (s3.us-east-1.petabox.io)
 3 / Europe (Frankfurt)
   \ (s3.eu-central-1.petabox.io)
 4 / Asia Pacific (Singapore)
   \ (s3.ap-southeast-1.petabox.io)
 5 / Middle East (Bahrain)
   \ (s3.me-south-1.petabox.io)
 6 / South America (São Paulo)
   \ (s3.sa-east-1.petabox.io)
endpoint&gt; 1

Option acl.
Canned ACL used when creating buckets and storing or copying objects.
This ACL is used for creating objects and if bucket_acl isn&#39;t set, for creating buckets too.
For more info visit https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html#canned-acl
Note that this ACL is applied when server-side copying objects as S3
doesn&#39;t copy the ACL from the source but rather writes a fresh one.
If the acl is an empty string then no X-Amz-Acl: header is added and
the default (private) will be used.
Choose a number from below, or type in your own value.
Press Enter to leave empty.
   / Owner gets FULL_CONTROL.
 1 | No one else has access rights (default).
   \ (private)
   / Owner gets FULL_CONTROL.
 2 | The AllUsers group gets READ access.
   \ (public-read)
   / Owner gets FULL_CONTROL.
 3 | The AllUsers group gets READ and WRITE access.
   | Granting this on a bucket is generally not recommended.
   \ (public-read-write)
   / Owner gets FULL_CONTROL.
 4 | The AuthenticatedUsers group gets READ access.
   \ (authenticated-read)
   / Object owner gets FULL_CONTROL.
 5 | Bucket owner gets READ access.
   | If you specify this canned ACL when creating a bucket, Amazon S3 ignores it.
   \ (bucket-owner-read)
   / Both the object owner and the bucket owner get FULL_CONTROL over the object.
 6 | If you specify this canned ACL when creating a bucket, Amazon S3 ignores it.
   \ (bucket-owner-full-control)
acl&gt; 1

Edit advanced config?
y) Yes
n) No (default)
y/n&gt; No

Configuration complete.
Options:
- type: s3
- provider: Petabox
- access_key_id: YOUR_ACCESS_KEY_ID
- secret_access_key: YOUR_SECRET_ACCESS_KEY
- region: us-east-1
- endpoint: s3.petabox.io
Keep this &quot;My Petabox Storage&quot; remote?
y) Yes this is OK (default)
e) Edit this remote
d) Delete this remote
y/e/d&gt; y</code></pre>
<p>This will leave the config file looking like this.</p>
<pre><code>[My Petabox Storage]
type = s3
provider = Petabox
access_key_id = YOUR_ACCESS_KEY_ID
secret_access_key = YOUR_SECRET_ACCESS_KEY
region = us-east-1
endpoint = s3.petabox.io</code></pre>
<h3 id="storj">Storj</h3>
<p>Storj is a decentralized cloud storage which can be used through its native protocol or an S3 compatible gateway.</p>
<p>The S3 compatible gateway is configured using <code>rclone config</code> with a type of <code>s3</code> and with a provider name of <code>Storj</code>. Here is an example run of the configurator.</p>
<pre><code>Type of storage to configure.
Storage&gt; s3
Get AWS credentials from runtime (environment variables or EC2/ECS meta data if no env vars).
Only applies if access_key_id and secret_access_key is blank.
Choose a number from below, or type in your own boolean value (true or false).
Press Enter for the default (false).
 1 / Enter AWS credentials in the next step.
   \ (false)
 2 / Get AWS credentials from the environment (env vars or IAM).
   \ (true)
env_auth&gt; 1
Option access_key_id.
AWS Access Key ID.
Leave blank for anonymous access or runtime credentials.
Enter a value. Press Enter to leave empty.
access_key_id&gt; XXXX (as shown when creating the access grant)
Option secret_access_key.
AWS Secret Access Key (password).
Leave blank for anonymous access or runtime credentials.
Enter a value. Press Enter to leave empty.
secret_access_key&gt; XXXX (as shown when creating the access grant)
Option endpoint.
Endpoint of the Shared Gateway.
Choose a number from below, or type in your own value.
Press Enter to leave empty.
 1 / EU1 Shared Gateway
   \ (gateway.eu1.storjshare.io)
 2 / US1 Shared Gateway
   \ (gateway.us1.storjshare.io)
 3 / Asia-Pacific Shared Gateway
   \ (gateway.ap1.storjshare.io)
endpoint&gt; 1 (as shown when creating the access grant)
Edit advanced config?
y) Yes
n) No (default)
y/n&gt; n</code></pre>
<p>Note that s3 credentials are generated when you <a href="https://docs.storj.io/dcs/api-reference/s3-compatible-gateway#usage">create an access grant</a>.</p>
<h4 id="backend-quirks">Backend quirks</h4>
<ul>
<li><code>--chunk-size</code> is forced to be 64 MiB or greater. This will use more memory than the default of 5 MiB.</li>
<li>Server side copy is disabled as it isn't currently supported in the gateway.</li>
<li>GetTier and SetTier are not supported.</li>
</ul>
<h4 id="backend-bugs">Backend bugs</h4>
<p>Due to <a href="https://github.com/storj/gateway-mt/issues/39">issue #39</a> uploading multipart files via the S3 gateway causes them to lose their metadata. For rclone's purpose this means that the modification time is not stored, nor is any MD5SUM (if one is available from the source).</p>
<p>This has the following consequences:</p>
<ul>
<li>Using <code>rclone rcat</code> will fail as the medatada doesn't match after upload</li>
<li>Uploading files with <code>rclone mount</code> will fail for the same reason
<ul>
<li>This can worked around by using <code>--vfs-cache-mode writes</code> or <code>--vfs-cache-mode full</code> or setting <code>--s3-upload-cutoff</code> large</li>
</ul></li>
<li>Files uploaded via a multipart upload won't have their modtimes
<ul>
<li>This will mean that <code>rclone sync</code> will likely keep trying to upload files bigger than <code>--s3-upload-cutoff</code></li>
<li>This can be worked around with <code>--checksum</code> or <code>--size-only</code> or setting <code>--s3-upload-cutoff</code> large</li>
<li>The maximum value for <code>--s3-upload-cutoff</code> is 5GiB though</li>
</ul></li>
</ul>
<p>One general purpose workaround is to set <code>--s3-upload-cutoff 5G</code>. This means that rclone will upload files smaller than 5GiB as single parts. Note that this can be set in the config file with <code>upload_cutoff = 5G</code> or configured in the advanced settings. If you regularly transfer files larger than 5G then using <code>--checksum</code> or <code>--size-only</code> in <code>rclone sync</code> is the recommended workaround.</p>
<h4 id="comparison-with-the-native-protocol">Comparison with the native protocol</h4>
<p>Use the <a href="/storj">the native protocol</a> to take advantage of client-side encryption as well as to achieve the best possible download performance. Uploads will be erasure-coded locally, thus a 1gb upload will result in 2.68gb of data being uploaded to storage nodes across the network.</p>
<p>Use this backend and the S3 compatible Hosted Gateway to increase upload performance and reduce the load on your systems and network. Uploads will be encrypted and erasure-coded server-side, thus a 1GB upload will result in only in 1GB of data being uploaded to storage nodes across the network.</p>
<p>For more detailed comparison please check the documentation of the <a href="/storj">storj</a> backend.</p>
<h2 id="memory-usage-memory">Memory usage {memory}</h2>
<p>The most common cause of rclone using lots of memory is a single directory with millions of files in. Despite s3 not really having the concepts of directories, rclone does the sync on a directory by directory basis to be compatible with normal filing systems.</p>
<p>Rclone loads each directory into memory as rclone objects. Each rclone object takes 0.5k-1k of memory, so approximately 1GB per 1,000,000 files, and the sync for that directory does not begin until it is entirely loaded in memory. So the sync can take a long time to start for large directories.</p>
<p>To sync a directory with 100,000,000 files in you would need approximately 100 GB of memory. At some point the amount of memory becomes difficult to provide so there is <a href="https://github.com/rclone/rclone/wiki/Big-syncs-with-millions-of-files">a workaround for this</a> which involves a bit of scripting.</p>
<p>At some point rclone will gain a sync mode which is effectively this workaround but built in to rclone.</p>
<h2 id="limitations-6">Limitations</h2>
<p><code>rclone about</code> is not supported by the S3 backend. Backends without this capability cannot determine free space for an rclone mount or use policy <code>mfs</code> (most free space) as a member of an rclone union remote.</p>
<p>See <a href="https://rclone.org/overview/#optional-features">List of backends that do not support rclone about</a> and <a href="https://rclone.org/commands/rclone_about/">rclone about</a></p>
<h3 id="synology-c2">Synology C2 Object Storage</h3>
<p><a href="https://c2.synology.com/en-global/object-storage/overview">Synology C2 Object Storage</a> provides a secure, S3-compatible, and cost-effective cloud storage solution without API request, download fees, and deletion penalty.</p>
<p>The S3 compatible gateway is configured using <code>rclone config</code> with a type of <code>s3</code> and with a provider name of <code>Synology</code>. Here is an example run of the configurator.</p>
<p>First run:</p>
<pre><code>rclone config</code></pre>
<p>This will guide you through an interactive setup process.</p>
<pre><code>No remotes found, make a new one?
n) New remote
s) Set configuration password
q) Quit config

n/s/q&gt; n

Enter name for new remote.1
name&gt; syno

Type of storage to configure.
Enter a string value. Press Enter for the default (&quot;&quot;).
Choose a number from below, or type in your own value

XX / Amazon S3 Compliant Storage Providers including AWS, ...
   \ &quot;s3&quot;

Storage&gt; s3

Choose your S3 provider.
Enter a string value. Press Enter for the default (&quot;&quot;).
Choose a number from below, or type in your own value
 24 / Synology C2 Object Storage
   \ (Synology)

provider&gt; Synology

Get AWS credentials from runtime (environment variables or EC2/ECS meta data if no env vars).
Only applies if access_key_id and secret_access_key is blank.
Enter a boolean value (true or false). Press Enter for the default (&quot;false&quot;).
Choose a number from below, or type in your own value
 1 / Enter AWS credentials in the next step
   \ &quot;false&quot;
 2 / Get AWS credentials from the environment (env vars or IAM)
   \ &quot;true&quot;

env_auth&gt; 1

AWS Access Key ID.
Leave blank for anonymous access or runtime credentials.
Enter a string value. Press Enter for the default (&quot;&quot;).

access_key_id&gt; accesskeyid

AWS Secret Access Key (password)
Leave blank for anonymous access or runtime credentials.
Enter a string value. Press Enter for the default (&quot;&quot;).

secret_access_key&gt; secretaccesskey

Region where your data stored.
Choose a number from below, or type in your own value.
Press Enter to leave empty.
 1 / Europe Region 1
   \ (eu-001)
 2 / Europe Region 2
   \ (eu-002)
 3 / US Region 1
   \ (us-001)
 4 / US Region 2
   \ (us-002)
 5 / Asia (Taiwan)
   \ (tw-001)

region &gt; 1

Option endpoint.
Endpoint for Synology C2 Object Storage API.
Choose a number from below, or type in your own value.
Press Enter to leave empty.
 1 / EU Endpoint 1
   \ (eu-001.s3.synologyc2.net)
 2 / US Endpoint 1
   \ (us-001.s3.synologyc2.net)
 3 / TW Endpoint 1
   \ (tw-001.s3.synologyc2.net)

endpoint&gt; 1

Option location_constraint.
Location constraint - must be set to match the Region.
Leave blank if not sure. Used when creating buckets only.
Enter a value. Press Enter to leave empty.
location_constraint&gt;

Edit advanced config? (y/n)
y) Yes
n) No
y/n&gt; y

Option no_check_bucket.
If set, don&#39;t attempt to check the bucket exists or create it.
This can be useful when trying to minimise the number of transactions
rclone does if you know the bucket exists already.
It can also be needed if the user you are using does not have bucket
creation permissions. Before v1.52.0 this would have passed silently
due to a bug.
Enter a boolean value (true or false). Press Enter for the default (true).

no_check_bucket&gt; true

Configuration complete.
Options:
- type: s3
- provider: Synology
- region: eu-001
- endpoint: eu-001.s3.synologyc2.net
- no_check_bucket: true
Keep this &quot;syno&quot; remote?
y) Yes this is OK (default)
e) Edit this remote
d) Delete this remote

y/e/d&gt; y</code></pre>
<h1 id="backblaze-b2">Backblaze B2</h1>
<p>B2 is <a href="https://www.backblaze.com/cloud-storage">Backblaze's cloud storage system</a>.</p>
<p>Paths are specified as <code>remote:bucket</code> (or <code>remote:</code> for the <code>lsd</code> command.) You may put subdirectories in too, e.g. <code>remote:bucket/path/to/dir</code>.</p>
<h2 id="configuration-3">Configuration</h2>
<p>Here is an example of making a b2 configuration. First run</p>
<pre><code>rclone config</code></pre>
<p>This will guide you through an interactive setup process. To authenticate you will either need your Account ID (a short hex number) and Master Application Key (a long hex number) OR an Application Key, which is the recommended method. See below for further details on generating and using an Application Key.</p>
<pre><code>No remotes found, make a new one?
n) New remote
q) Quit config
n/q&gt; n
name&gt; remote
Type of storage to configure.
Choose a number from below, or type in your own value
[snip]
XX / Backblaze B2
   \ &quot;b2&quot;
[snip]
Storage&gt; b2
Account ID or Application Key ID
account&gt; 123456789abc
Application Key
key&gt; 0123456789abcdef0123456789abcdef0123456789
Endpoint for the service - leave blank normally.
endpoint&gt;
Remote config
Configuration complete.
Options:
- type: b2
- account: 123456789abc
- key: 0123456789abcdef0123456789abcdef0123456789
- endpoint:
Keep this &quot;remote&quot; remote?
y) Yes this is OK
e) Edit this remote
d) Delete this remote
y/e/d&gt; y</code></pre>
<p>This remote is called <code>remote</code> and can now be used like this</p>
<p>See all buckets</p>
<pre><code>rclone lsd remote:</code></pre>
<p>Create a new bucket</p>
<pre><code>rclone mkdir remote:bucket</code></pre>
<p>List the contents of a bucket</p>
<pre><code>rclone ls remote:bucket</code></pre>
<p>Sync <code>/home/local/directory</code> to the remote bucket, deleting any excess files in the bucket.</p>
<pre><code>rclone sync --interactive /home/local/directory remote:bucket</code></pre>
<h3 id="application-keys">Application Keys</h3>
<p>B2 supports multiple <a href="https://www.backblaze.com/docs/cloud-storage-application-keys">Application Keys for different access permission to B2 Buckets</a>.</p>
<p>You can use these with rclone too; you will need to use rclone version 1.43 or later.</p>
<p>Follow Backblaze's docs to create an Application Key with the required permission and add the <code>applicationKeyId</code> as the <code>account</code> and the <code>Application Key</code> itself as the <code>key</code>.</p>
<p>Note that you must put the <em>applicationKeyId</em> as the <code>account</code> – you can't use the master Account ID. If you try then B2 will return 401 errors.</p>
<h3 id="fast-list-1">--fast-list</h3>
<p>This remote supports <code>--fast-list</code> which allows you to use fewer transactions in exchange for more memory. See the <a href="https://rclone.org/docs/#fast-list">rclone docs</a> for more details.</p>
<h3 id="modification-times-2">Modification times</h3>
<p>The modification time is stored as metadata on the object as <code>X-Bz-Info-src_last_modified_millis</code> as milliseconds since 1970-01-01 in the Backblaze standard. Other tools should be able to use this as a modified time.</p>
<p>Modified times are used in syncing and are fully supported. Note that if a modification time needs to be updated on an object then it will create a new version of the object.</p>
<h3 id="restricted-filename-characters-2">Restricted filename characters</h3>
<p>In addition to the <a href="https://rclone.org/overview/#restricted-characters">default restricted characters set</a> the following characters are also replaced:</p>
<table>
<thead>
<tr class="header">
<th>Character</th>
<th style="text-align: center;">Value</th>
<th style="text-align: center;">Replacement</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td>\</td>
<td style="text-align: center;">0x5C</td>
<td style="text-align: center;">＼</td>
</tr>
</tbody>
</table>
<p>Invalid UTF-8 bytes will also be <a href="https://rclone.org/overview/#invalid-utf8">replaced</a>, as they can't be used in JSON strings.</p>
<p>Note that in 2020-05 Backblaze started allowing  characters in file names. Rclone hasn't changed its encoding as this could cause syncs to re-transfer files. If you want rclone not to replace  then see the <code>--b2-encoding</code> flag below and remove the <code>BackSlash</code> from the string. This can be set in the config.</p>
<h3 id="sha1-checksums">SHA1 checksums</h3>
<p>The SHA1 checksums of the files are checked on upload and download and will be used in the syncing process.</p>
<p>Large files (bigger than the limit in <code>--b2-upload-cutoff</code>) which are uploaded in chunks will store their SHA1 on the object as <code>X-Bz-Info-large_file_sha1</code> as recommended by Backblaze.</p>
<p>For a large file to be uploaded with an SHA1 checksum, the source needs to support SHA1 checksums. The local disk supports SHA1 checksums so large file transfers from local disk will have an SHA1. See <a href="https://rclone.org/overview/#features">the overview</a> for exactly which remotes support SHA1.</p>
<p>Sources which don't support SHA1, in particular <code>crypt</code> will upload large files without SHA1 checksums. This may be fixed in the future (see <a href="https://github.com/rclone/rclone/issues/1767">#1767</a>).</p>
<p>Files sizes below <code>--b2-upload-cutoff</code> will always have an SHA1 regardless of the source.</p>
<h3 id="transfers">Transfers</h3>
<p>Backblaze recommends that you do lots of transfers simultaneously for maximum speed. In tests from my SSD equipped laptop the optimum setting is about <code>--transfers 32</code> though higher numbers may be used for a slight speed improvement. The optimum number for you may vary depending on your hardware, how big the files are, how much you want to load your computer, etc. The default of <code>--transfers 4</code> is definitely too low for Backblaze B2 though.</p>
<p>Note that uploading big files (bigger than 200 MiB by default) will use a 96 MiB RAM buffer by default. There can be at most <code>--transfers</code> of these in use at any moment, so this sets the upper limit on the memory used.</p>
<h3 id="versions-1">Versions</h3>
<p>The default setting of B2 is to keep old versions of files. This means when rclone uploads a new version of a file it creates a <a href="https://www.backblaze.com/docs/cloud-storage-file-versions">new version of it</a>. Likewise when you delete a file, the old version will be marked hidden and still be available.</p>
<p>Whether B2 keeps old versions of files or not can be adjusted on a per bucket basis using the "Lifecycle settings" on the B2 control panel or when creating the bucket using the <a href="#b2-lifecycle">--b2-lifecycle</a> flag or after creation using the <a href="#lifecycle">rclone backend lifecycle</a> command.</p>
<p>You may opt in to a "hard delete" of files with the <code>--b2-hard-delete</code> flag which permanently removes files on deletion instead of hiding them.</p>
<p>Old versions of files, where available, are visible using the <code>--b2-versions</code> flag.</p>
<p>It is also possible to view a bucket as it was at a certain point in time, using the <code>--b2-version-at</code> flag. This will show the file versions as they were at that time, showing files that have been deleted afterwards, and hiding files that were created since.</p>
<p>If you wish to remove all the old versions, and unfinished large file uploads, then you can use the <code>rclone cleanup remote:bucket</code> command which will delete all the old versions of files, leaving the current ones intact. You can also supply a path and only old versions under that path will be deleted, e.g. <code>rclone cleanup remote:bucket/path/to/stuff</code>.</p>
<p>Note that <code>cleanup</code> will remove partially uploaded files from the bucket if they are more than a day old. If you want more control over the expiry date then run <code>rclone backend cleanup b2:bucket -o max-age=1h</code> to remove all unfinished large file uploads older than one hour, leaving old versions intact.</p>
<p>If you wish to remove all the old versions, leaving current files and unfinished large files intact, then you can use the <a href="#cleanup-hidden"><code>rclone backend cleanup-hidden remote:bucket</code></a> command. You can also supply a path and only old versions under that path will be deleted, e.g. <code>rclone backend cleanup-hidden remote:bucket/path/to/stuff</code>.</p>
<p>When you <code>purge</code> a bucket, the current and the old versions will be deleted then the bucket will be deleted.</p>
<p>However <code>delete</code> will cause the current versions of the files to become hidden old versions.</p>
<p>Here is a session showing the listing and retrieval of an old version followed by a <code>cleanup</code> of the old versions.</p>
<p>Show current version and all the versions with <code>--b2-versions</code> flag.</p>
<pre><code>$ rclone -q ls b2:cleanup-test
        9 one.txt

$ rclone -q --b2-versions ls b2:cleanup-test
        9 one.txt
        8 one-v2016-07-04-141032-000.txt
       16 one-v2016-07-04-141003-000.txt
       15 one-v2016-07-02-155621-000.txt</code></pre>
<p>Retrieve an old version</p>
<pre><code>$ rclone -q --b2-versions copy b2:cleanup-test/one-v2016-07-04-141003-000.txt /tmp

$ ls -l /tmp/one-v2016-07-04-141003-000.txt
-rw-rw-r-- 1 ncw ncw 16 Jul  2 17:46 /tmp/one-v2016-07-04-141003-000.txt</code></pre>
<p>Clean up all the old versions and show that they've gone.</p>
<pre><code>$ rclone -q cleanup b2:cleanup-test

$ rclone -q ls b2:cleanup-test
        9 one.txt

$ rclone -q --b2-versions ls b2:cleanup-test
        9 one.txt</code></pre>
<h4 id="versions-naming-caveat-1">Versions naming caveat</h4>
<p>When using <code>--b2-versions</code> flag rclone is relying on the file name to work out whether the objects are versions or not. Versions' names are created by inserting timestamp between file name and its extension.</p>
<pre><code>        9 file.txt
        8 file-v2023-07-17-161032-000.txt
       16 file-v2023-06-15-141003-000.txt</code></pre>
<p>If there are real files present with the same names as versions, then behaviour of <code>--b2-versions</code> can be unpredictable.</p>
<h3 id="data-usage">Data usage</h3>
<p>It is useful to know how many requests are sent to the server in different scenarios.</p>
<p>All copy commands send the following 4 requests:</p>
<pre><code>/b2api/v1/b2_authorize_account
/b2api/v1/b2_create_bucket
/b2api/v1/b2_list_buckets
/b2api/v1/b2_list_file_names</code></pre>
<p>The <code>b2_list_file_names</code> request will be sent once for every 1k files in the remote path, providing the checksum and modification time of the listed files. As of version 1.33 issue <a href="https://github.com/rclone/rclone/issues/818">#818</a> causes extra requests to be sent when using B2 with Crypt. When a copy operation does not require any files to be uploaded, no more requests will be sent.</p>
<p>Uploading files that do not require chunking, will send 2 requests per file upload:</p>
<pre><code>/b2api/v1/b2_get_upload_url
/b2api/v1/b2_upload_file/</code></pre>
<p>Uploading files requiring chunking, will send 2 requests (one each to start and finish the upload) and another 2 requests for each chunk:</p>
<pre><code>/b2api/v1/b2_start_large_file
/b2api/v1/b2_get_upload_part_url
/b2api/v1/b2_upload_part/
/b2api/v1/b2_finish_large_file</code></pre>
<h4 id="versions-2">Versions</h4>
<p>Versions can be viewed with the <code>--b2-versions</code> flag. When it is set rclone will show and act on older versions of files. For example</p>
<p>Listing without <code>--b2-versions</code></p>
<pre><code>$ rclone -q ls b2:cleanup-test
        9 one.txt</code></pre>
<p>And with</p>
<pre><code>$ rclone -q --b2-versions ls b2:cleanup-test
        9 one.txt
        8 one-v2016-07-04-141032-000.txt
       16 one-v2016-07-04-141003-000.txt
       15 one-v2016-07-02-155621-000.txt</code></pre>
<p>Showing that the current version is unchanged but older versions can be seen. These have the UTC date that they were uploaded to the server to the nearest millisecond appended to them.</p>
<p>Note that when using <code>--b2-versions</code> no file write operations are permitted, so you can't upload files or delete them.</p>
<h3 id="b2-and-rclone-link">B2 and rclone link</h3>
<p>Rclone supports generating file share links for private B2 buckets. They can either be for a file for example:</p>
<pre><code>./rclone link B2:bucket/path/to/file.txt
https://f002.backblazeb2.com/file/bucket/path/to/file.txt?Authorization=xxxxxxxx
</code></pre>
<p>or if run on a directory you will get:</p>
<pre><code>./rclone link B2:bucket/path
https://f002.backblazeb2.com/file/bucket/path?Authorization=xxxxxxxx</code></pre>
<p>you can then use the authorization token (the part of the url from the <code>?Authorization=</code> on) on any file path under that directory. For example:</p>
<pre><code>https://f002.backblazeb2.com/file/bucket/path/to/file1?Authorization=xxxxxxxx
https://f002.backblazeb2.com/file/bucket/path/file2?Authorization=xxxxxxxx
https://f002.backblazeb2.com/file/bucket/path/folder/file3?Authorization=xxxxxxxx
</code></pre>
<h3 id="standard-options-3">Standard options</h3>
<p>Here are the Standard options specific to b2 (Backblaze B2).</p>
<h4 id="b2-account">--b2-account</h4>
<p>Account ID or Application Key ID.</p>
<p>Properties:</p>
<ul>
<li>Config: account</li>
<li>Env Var: RCLONE_B2_ACCOUNT</li>
<li>Type: string</li>
<li>Required: true</li>
</ul>
<h4 id="b2-key">--b2-key</h4>
<p>Application Key.</p>
<p>Properties:</p>
<ul>
<li>Config: key</li>
<li>Env Var: RCLONE_B2_KEY</li>
<li>Type: string</li>
<li>Required: true</li>
</ul>
<h4 id="b2-hard-delete">--b2-hard-delete</h4>
<p>Permanently delete files on remote removal, otherwise hide files.</p>
<p>Properties:</p>
<ul>
<li>Config: hard_delete</li>
<li>Env Var: RCLONE_B2_HARD_DELETE</li>
<li>Type: bool</li>
<li>Default: false</li>
</ul>
<h3 id="advanced-options-3">Advanced options</h3>
<p>Here are the Advanced options specific to b2 (Backblaze B2).</p>
<h4 id="b2-endpoint">--b2-endpoint</h4>
<p>Endpoint for the service.</p>
<p>Leave blank normally.</p>
<p>Properties:</p>
<ul>
<li>Config: endpoint</li>
<li>Env Var: RCLONE_B2_ENDPOINT</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="b2-test-mode">--b2-test-mode</h4>
<p>A flag string for X-Bz-Test-Mode header for debugging.</p>
<p>This is for debugging purposes only. Setting it to one of the strings below will cause b2 to return specific errors:</p>
<ul>
<li>"fail_some_uploads"</li>
<li>"expire_some_account_authorization_tokens"</li>
<li>"force_cap_exceeded"</li>
</ul>
<p>These will be set in the "X-Bz-Test-Mode" header which is documented in the <a href="https://www.backblaze.com/docs/cloud-storage-integration-checklist">b2 integrations checklist</a>.</p>
<p>Properties:</p>
<ul>
<li>Config: test_mode</li>
<li>Env Var: RCLONE_B2_TEST_MODE</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="b2-versions">--b2-versions</h4>
<p>Include old versions in directory listings.</p>
<p>Note that when using this no file write operations are permitted, so you can't upload files or delete them.</p>
<p>Properties:</p>
<ul>
<li>Config: versions</li>
<li>Env Var: RCLONE_B2_VERSIONS</li>
<li>Type: bool</li>
<li>Default: false</li>
</ul>
<h4 id="b2-version-at">--b2-version-at</h4>
<p>Show file versions as they were at the specified time.</p>
<p>Note that when using this no file write operations are permitted, so you can't upload files or delete them.</p>
<p>Properties:</p>
<ul>
<li>Config: version_at</li>
<li>Env Var: RCLONE_B2_VERSION_AT</li>
<li>Type: Time</li>
<li>Default: off</li>
</ul>
<h4 id="b2-upload-cutoff">--b2-upload-cutoff</h4>
<p>Cutoff for switching to chunked upload.</p>
<p>Files above this size will be uploaded in chunks of "--b2-chunk-size".</p>
<p>This value should be set no larger than 4.657 GiB (== 5 GB).</p>
<p>Properties:</p>
<ul>
<li>Config: upload_cutoff</li>
<li>Env Var: RCLONE_B2_UPLOAD_CUTOFF</li>
<li>Type: SizeSuffix</li>
<li>Default: 200Mi</li>
</ul>
<h4 id="b2-copy-cutoff">--b2-copy-cutoff</h4>
<p>Cutoff for switching to multipart copy.</p>
<p>Any files larger than this that need to be server-side copied will be copied in chunks of this size.</p>
<p>The minimum is 0 and the maximum is 4.6 GiB.</p>
<p>Properties:</p>
<ul>
<li>Config: copy_cutoff</li>
<li>Env Var: RCLONE_B2_COPY_CUTOFF</li>
<li>Type: SizeSuffix</li>
<li>Default: 4Gi</li>
</ul>
<h4 id="b2-chunk-size">--b2-chunk-size</h4>
<p>Upload chunk size.</p>
<p>When uploading large files, chunk the file into this size.</p>
<p>Must fit in memory. These chunks are buffered in memory and there might a maximum of "--transfers" chunks in progress at once.</p>
<p>5,000,000 Bytes is the minimum size.</p>
<p>Properties:</p>
<ul>
<li>Config: chunk_size</li>
<li>Env Var: RCLONE_B2_CHUNK_SIZE</li>
<li>Type: SizeSuffix</li>
<li>Default: 96Mi</li>
</ul>
<h4 id="b2-upload-concurrency">--b2-upload-concurrency</h4>
<p>Concurrency for multipart uploads.</p>
<p>This is the number of chunks of the same file that are uploaded concurrently.</p>
<p>Note that chunks are stored in memory and there may be up to "--transfers" * "--b2-upload-concurrency" chunks stored at once in memory.</p>
<p>Properties:</p>
<ul>
<li>Config: upload_concurrency</li>
<li>Env Var: RCLONE_B2_UPLOAD_CONCURRENCY</li>
<li>Type: int</li>
<li>Default: 4</li>
</ul>
<h4 id="b2-disable-checksum">--b2-disable-checksum</h4>
<p>Disable checksums for large (&gt; upload cutoff) files.</p>
<p>Normally rclone will calculate the SHA1 checksum of the input before uploading it so it can add it to metadata on the object. This is great for data integrity checking but can cause long delays for large files to start uploading.</p>
<p>Properties:</p>
<ul>
<li>Config: disable_checksum</li>
<li>Env Var: RCLONE_B2_DISABLE_CHECKSUM</li>
<li>Type: bool</li>
<li>Default: false</li>
</ul>
<h4 id="b2-download-url">--b2-download-url</h4>
<p>Custom endpoint for downloads.</p>
<p>This is usually set to a Cloudflare CDN URL as Backblaze offers free egress for data downloaded through the Cloudflare network. Rclone works with private buckets by sending an "Authorization" header. If the custom endpoint rewrites the requests for authentication, e.g., in Cloudflare Workers, this header needs to be handled properly. Leave blank if you want to use the endpoint provided by Backblaze.</p>
<p>The URL provided here SHOULD have the protocol and SHOULD NOT have a trailing slash or specify the /file/bucket subpath as rclone will request files with "{download_url}/file/{bucket_name}/{path}".</p>
<p>Example: &gt; https://mysubdomain.mydomain.tld (No trailing "/", "file" or "bucket")</p>
<p>Properties:</p>
<ul>
<li>Config: download_url</li>
<li>Env Var: RCLONE_B2_DOWNLOAD_URL</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="b2-download-auth-duration">--b2-download-auth-duration</h4>
<p>Time before the public link authorization token will expire in s or suffix ms|s|m|h|d.</p>
<p>This is used in combination with "rclone link" for making files accessible to the public and sets the duration before the download authorization token will expire.</p>
<p>The minimum value is 1 second. The maximum value is one week.</p>
<p>Properties:</p>
<ul>
<li>Config: download_auth_duration</li>
<li>Env Var: RCLONE_B2_DOWNLOAD_AUTH_DURATION</li>
<li>Type: Duration</li>
<li>Default: 1w</li>
</ul>
<h4 id="b2-memory-pool-flush-time">--b2-memory-pool-flush-time</h4>
<p>How often internal memory buffer pools will be flushed. (no longer used)</p>
<p>Properties:</p>
<ul>
<li>Config: memory_pool_flush_time</li>
<li>Env Var: RCLONE_B2_MEMORY_POOL_FLUSH_TIME</li>
<li>Type: Duration</li>
<li>Default: 1m0s</li>
</ul>
<h4 id="b2-memory-pool-use-mmap">--b2-memory-pool-use-mmap</h4>
<p>Whether to use mmap buffers in internal memory pool. (no longer used)</p>
<p>Properties:</p>
<ul>
<li>Config: memory_pool_use_mmap</li>
<li>Env Var: RCLONE_B2_MEMORY_POOL_USE_MMAP</li>
<li>Type: bool</li>
<li>Default: false</li>
</ul>
<h4 id="b2-lifecycle">--b2-lifecycle</h4>
<p>Set the number of days deleted files should be kept when creating a bucket.</p>
<p>On bucket creation, this parameter is used to create a lifecycle rule for the entire bucket.</p>
<p>If lifecycle is 0 (the default) it does not create a lifecycle rule so the default B2 behaviour applies. This is to create versions of files on delete and overwrite and to keep them indefinitely.</p>
<p>If lifecycle is &gt;0 then it creates a single rule setting the number of days before a file that is deleted or overwritten is deleted permanently. This is known as daysFromHidingToDeleting in the b2 docs.</p>
<p>The minimum value for this parameter is 1 day.</p>
<p>You can also enable hard_delete in the config also which will mean deletions won't cause versions but overwrites will still cause versions to be made.</p>
<p>See: <a href="#lifecycle">rclone backend lifecycle</a> for setting lifecycles after bucket creation.</p>
<p>Properties:</p>
<ul>
<li>Config: lifecycle</li>
<li>Env Var: RCLONE_B2_LIFECYCLE</li>
<li>Type: int</li>
<li>Default: 0</li>
</ul>
<h4 id="b2-encoding">--b2-encoding</h4>
<p>The encoding for the backend.</p>
<p>See the <a href="https://rclone.org/overview/#encoding">encoding section in the overview</a> for more info.</p>
<p>Properties:</p>
<ul>
<li>Config: encoding</li>
<li>Env Var: RCLONE_B2_ENCODING</li>
<li>Type: Encoding</li>
<li>Default: Slash,BackSlash,Del,Ctl,InvalidUtf8,Dot</li>
</ul>
<h4 id="b2-description">--b2-description</h4>
<p>Description of the remote.</p>
<p>Properties:</p>
<ul>
<li>Config: description</li>
<li>Env Var: RCLONE_B2_DESCRIPTION</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h2 id="backend-commands-1">Backend commands</h2>
<p>Here are the commands specific to the b2 backend.</p>
<p>Run them with</p>
<pre><code>rclone backend COMMAND remote:</code></pre>
<p>The help below will explain what arguments each command takes.</p>
<p>See the <a href="https://rclone.org/commands/rclone_backend/">backend</a> command for more info on how to pass options and arguments.</p>
<p>These can be run on a running backend using the rc command <a href="https://rclone.org/rc/#backend-command">backend/command</a>.</p>
<h3 id="lifecycle">lifecycle</h3>
<p>Read or set the lifecycle for a bucket</p>
<pre><code>rclone backend lifecycle remote: [options] [&lt;arguments&gt;+]</code></pre>
<p>This command can be used to read or set the lifecycle for a bucket.</p>
<p>Usage Examples:</p>
<p>To show the current lifecycle rules:</p>
<pre><code>rclone backend lifecycle b2:bucket</code></pre>
<p>This will dump something like this showing the lifecycle rules.</p>
<pre><code>[
    {
        &quot;daysFromHidingToDeleting&quot;: 1,
        &quot;daysFromUploadingToHiding&quot;: null,
        &quot;fileNamePrefix&quot;: &quot;&quot;
    }
]</code></pre>
<p>If there are no lifecycle rules (the default) then it will just return [].</p>
<p>To reset the current lifecycle rules:</p>
<pre><code>rclone backend lifecycle b2:bucket -o daysFromHidingToDeleting=30
rclone backend lifecycle b2:bucket -o daysFromUploadingToHiding=5 -o daysFromHidingToDeleting=1</code></pre>
<p>This will run and then print the new lifecycle rules as above.</p>
<p>Rclone only lets you set lifecycles for the whole bucket with the fileNamePrefix = "".</p>
<p>You can't disable versioning with B2. The best you can do is to set the daysFromHidingToDeleting to 1 day. You can enable hard_delete in the config also which will mean deletions won't cause versions but overwrites will still cause versions to be made.</p>
<pre><code>rclone backend lifecycle b2:bucket -o daysFromHidingToDeleting=1</code></pre>
<p>See: https://www.backblaze.com/docs/cloud-storage-lifecycle-rules</p>
<p>Options:</p>
<ul>
<li>"daysFromHidingToDeleting": After a file has been hidden for this many days it is deleted. 0 is off.</li>
<li>"daysFromUploadingToHiding": This many days after uploading a file is hidden</li>
</ul>
<h3 id="cleanup-3">cleanup</h3>
<p>Remove unfinished large file uploads.</p>
<pre><code>rclone backend cleanup remote: [options] [&lt;arguments&gt;+]</code></pre>
<p>This command removes unfinished large file uploads of age greater than max-age, which defaults to 24 hours.</p>
<p>Note that you can use --interactive/-i or --dry-run with this command to see what it would do.</p>
<pre><code>rclone backend cleanup b2:bucket/path/to/object
rclone backend cleanup -o max-age=7w b2:bucket/path/to/object</code></pre>
<p>Durations are parsed as per the rest of rclone, 2h, 7d, 7w etc.</p>
<p>Options:</p>
<ul>
<li>"max-age": Max age of upload to delete</li>
</ul>
<h3 id="cleanup-hidden-1">cleanup-hidden</h3>
<p>Remove old versions of files.</p>
<pre><code>rclone backend cleanup-hidden remote: [options] [&lt;arguments&gt;+]</code></pre>
<p>This command removes any old hidden versions of files.</p>
<p>Note that you can use --interactive/-i or --dry-run with this command to see what it would do.</p>
<pre><code>rclone backend cleanup-hidden b2:bucket/path/to/dir</code></pre>
<h2 id="limitations-7">Limitations</h2>
<p><code>rclone about</code> is not supported by the B2 backend. Backends without this capability cannot determine free space for an rclone mount or use policy <code>mfs</code> (most free space) as a member of an rclone union remote.</p>
<p>See <a href="https://rclone.org/overview/#optional-features">List of backends that do not support rclone about</a> and <a href="https://rclone.org/commands/rclone_about/">rclone about</a></p>
<h1 id="box">Box</h1>
<p>Paths are specified as <code>remote:path</code></p>
<p>Paths may be as deep as required, e.g. <code>remote:directory/subdirectory</code>.</p>
<p>The initial setup for Box involves getting a token from Box which you can do either in your browser, or with a config.json downloaded from Box to use JWT authentication. <code>rclone config</code> walks you through it.</p>
<h2 id="configuration-4">Configuration</h2>
<p>Here is an example of how to make a remote called <code>remote</code>. First run:</p>
<pre><code> rclone config</code></pre>
<p>This will guide you through an interactive setup process:</p>
<pre><code>No remotes found, make a new one?
n) New remote
s) Set configuration password
q) Quit config
n/s/q&gt; n
name&gt; remote
Type of storage to configure.
Choose a number from below, or type in your own value
[snip]
XX / Box
   \ &quot;box&quot;
[snip]
Storage&gt; box
Box App Client Id - leave blank normally.
client_id&gt; 
Box App Client Secret - leave blank normally.
client_secret&gt;
Box App config.json location
Leave blank normally.
Enter a string value. Press Enter for the default (&quot;&quot;).
box_config_file&gt;
Box App Primary Access Token
Leave blank normally.
Enter a string value. Press Enter for the default (&quot;&quot;).
access_token&gt;

Enter a string value. Press Enter for the default (&quot;user&quot;).
Choose a number from below, or type in your own value
 1 / Rclone should act on behalf of a user
   \ &quot;user&quot;
 2 / Rclone should act on behalf of a service account
   \ &quot;enterprise&quot;
box_sub_type&gt;
Remote config
Use web browser to automatically authenticate rclone with remote?
 * Say Y if the machine running rclone has a web browser you can use
 * Say N if running rclone on a (remote) machine without web browser access
If not sure try Y. If Y failed, try N.
y) Yes
n) No
y/n&gt; y
If your browser doesn&#39;t open automatically go to the following link: http://127.0.0.1:53682/auth
Log in and authorize rclone for access
Waiting for code...
Got code
Configuration complete.
Options:
- type: box
- client_id:
- client_secret:
- token: {&quot;access_token&quot;:&quot;XXX&quot;,&quot;token_type&quot;:&quot;bearer&quot;,&quot;refresh_token&quot;:&quot;XXX&quot;,&quot;expiry&quot;:&quot;XXX&quot;}
Keep this &quot;remote&quot; remote?
y) Yes this is OK
e) Edit this remote
d) Delete this remote
y/e/d&gt; y</code></pre>
<p>See the <a href="https://rclone.org/remote_setup/">remote setup docs</a> for how to set it up on a machine with no Internet browser available.</p>
<p>Note that rclone runs a webserver on your local machine to collect the token as returned from Box. This only runs from the moment it opens your browser to the moment you get back the verification code. This is on <code>http://127.0.0.1:53682/</code> and this it may require you to unblock it temporarily if you are running a host firewall.</p>
<p>Once configured you can then use <code>rclone</code> like this,</p>
<p>List directories in top level of your Box</p>
<pre><code>rclone lsd remote:</code></pre>
<p>List all the files in your Box</p>
<pre><code>rclone ls remote:</code></pre>
<p>To copy a local directory to an Box directory called backup</p>
<pre><code>rclone copy /home/source remote:backup</code></pre>
<h3 id="using-rclone-with-an-enterprise-account-with-sso">Using rclone with an Enterprise account with SSO</h3>
<p>If you have an "Enterprise" account type with Box with single sign on (SSO), you need to create a password to use Box with rclone. This can be done at your Enterprise Box account by going to Settings, "Account" Tab, and then set the password in the "Authentication" field.</p>
<p>Once you have done this, you can setup your Enterprise Box account using the same procedure detailed above in the, using the password you have just set.</p>
<h3 id="invalid-refresh-token">Invalid refresh token</h3>
<p>According to the <a href="https://developer.box.com/v2.0/docs/oauth-20#section-6-using-the-access-and-refresh-tokens">box docs</a>:</p>
<blockquote>
<p>Each refresh_token is valid for one use in 60 days.</p>
</blockquote>
<p>This means that if you</p>
<ul>
<li>Don't use the box remote for 60 days</li>
<li>Copy the config file with a box refresh token in and use it in two places</li>
<li>Get an error on a token refresh</li>
</ul>
<p>then rclone will return an error which includes the text <code>Invalid refresh token</code>.</p>
<p>To fix this you will need to use oauth2 again to update the refresh token. You can use the methods in <a href="https://rclone.org/remote_setup/">the remote setup docs</a>, bearing in mind that if you use the copy the config file method, you should not use that remote on the computer you did the authentication on.</p>
<p>Here is how to do it.</p>
<pre><code>$ rclone config
Current remotes:

Name                 Type
====                 ====
remote               box

e) Edit existing remote
n) New remote
d) Delete remote
r) Rename remote
c) Copy remote
s) Set configuration password
q) Quit config
e/n/d/r/c/s/q&gt; e
Choose a number from below, or type in an existing value
 1 &gt; remote
remote&gt; remote
Configuration complete.
Options:
- type: box
- token: {&quot;access_token&quot;:&quot;XXX&quot;,&quot;token_type&quot;:&quot;bearer&quot;,&quot;refresh_token&quot;:&quot;XXX&quot;,&quot;expiry&quot;:&quot;2017-07-08T23:40:08.059167677+01:00&quot;}
Keep this &quot;remote&quot; remote?
Edit remote
Value &quot;client_id&quot; = &quot;&quot;
Edit? (y/n)&gt;
y) Yes
n) No
y/n&gt; n
Value &quot;client_secret&quot; = &quot;&quot;
Edit? (y/n)&gt;
y) Yes
n) No
y/n&gt; n
Remote config
Already have a token - refresh?
y) Yes
n) No
y/n&gt; y
Use web browser to automatically authenticate rclone with remote?
 * Say Y if the machine running rclone has a web browser you can use
 * Say N if running rclone on a (remote) machine without web browser access
If not sure try Y. If Y failed, try N.
y) Yes
n) No
y/n&gt; y
If your browser doesn&#39;t open automatically go to the following link: http://127.0.0.1:53682/auth
Log in and authorize rclone for access
Waiting for code...
Got code
Configuration complete.
Options:
- type: box
- token: {&quot;access_token&quot;:&quot;YYY&quot;,&quot;token_type&quot;:&quot;bearer&quot;,&quot;refresh_token&quot;:&quot;YYY&quot;,&quot;expiry&quot;:&quot;2017-07-23T12:22:29.259137901+01:00&quot;}
Keep this &quot;remote&quot; remote?
y) Yes this is OK
e) Edit this remote
d) Delete this remote
y/e/d&gt; y</code></pre>
<h3 id="modification-times-and-hashes-2">Modification times and hashes</h3>
<p>Box allows modification times to be set on objects accurate to 1 second. These will be used to detect whether objects need syncing or not.</p>
<p>Box supports SHA1 type hashes, so you can use the <code>--checksum</code> flag.</p>
<h3 id="restricted-filename-characters-3">Restricted filename characters</h3>
<p>In addition to the <a href="https://rclone.org/overview/#restricted-characters">default restricted characters set</a> the following characters are also replaced:</p>
<table>
<thead>
<tr class="header">
<th>Character</th>
<th style="text-align: center;">Value</th>
<th style="text-align: center;">Replacement</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td>\</td>
<td style="text-align: center;">0x5C</td>
<td style="text-align: center;">＼</td>
</tr>
</tbody>
</table>
<p>File names can also not end with the following characters. These only get replaced if they are the last character in the name:</p>
<table>
<thead>
<tr class="header">
<th>Character</th>
<th style="text-align: center;">Value</th>
<th style="text-align: center;">Replacement</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td>SP</td>
<td style="text-align: center;">0x20</td>
<td style="text-align: center;">␠</td>
</tr>
</tbody>
</table>
<p>Invalid UTF-8 bytes will also be <a href="https://rclone.org/overview/#invalid-utf8">replaced</a>, as they can't be used in JSON strings.</p>
<h3 id="transfers-1">Transfers</h3>
<p>For files above 50 MiB rclone will use a chunked transfer. Rclone will upload up to <code>--transfers</code> chunks at the same time (shared among all the multipart uploads). Chunks are buffered in memory and are normally 8 MiB so increasing <code>--transfers</code> will increase memory use.</p>
<h3 id="deleting-files">Deleting files</h3>
<p>Depending on the enterprise settings for your user, the item will either be actually deleted from Box or moved to the trash.</p>
<p>Emptying the trash is supported via the rclone however cleanup command however this deletes every trashed file and folder individually so it may take a very long time. Emptying the trash via the WebUI does not have this limitation so it is advised to empty the trash via the WebUI.</p>
<h3 id="root-folder-id">Root folder ID</h3>
<p>You can set the <code>root_folder_id</code> for rclone. This is the directory (identified by its <code>Folder ID</code>) that rclone considers to be the root of your Box drive.</p>
<p>Normally you will leave this blank and rclone will determine the correct root to use itself.</p>
<p>However you can set this to restrict rclone to a specific folder hierarchy.</p>
<p>In order to do this you will have to find the <code>Folder ID</code> of the directory you wish rclone to display. This will be the last segment of the URL when you open the relevant folder in the Box web interface.</p>
<p>So if the folder you want rclone to use has a URL which looks like <code>https://app.box.com/folder/11xxxxxxxxx8</code> in the browser, then you use <code>11xxxxxxxxx8</code> as the <code>root_folder_id</code> in the config.</p>
<h3 id="standard-options-4">Standard options</h3>
<p>Here are the Standard options specific to box (Box).</p>
<h4 id="box-client-id">--box-client-id</h4>
<p>OAuth Client Id.</p>
<p>Leave blank normally.</p>
<p>Properties:</p>
<ul>
<li>Config: client_id</li>
<li>Env Var: RCLONE_BOX_CLIENT_ID</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="box-client-secret">--box-client-secret</h4>
<p>OAuth Client Secret.</p>
<p>Leave blank normally.</p>
<p>Properties:</p>
<ul>
<li>Config: client_secret</li>
<li>Env Var: RCLONE_BOX_CLIENT_SECRET</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="box-box-config-file">--box-box-config-file</h4>
<p>Box App config.json location</p>
<p>Leave blank normally.</p>
<p>Leading <code>~</code> will be expanded in the file name as will environment variables such as <code>${RCLONE_CONFIG_DIR}</code>.</p>
<p>Properties:</p>
<ul>
<li>Config: box_config_file</li>
<li>Env Var: RCLONE_BOX_BOX_CONFIG_FILE</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="box-access-token">--box-access-token</h4>
<p>Box App Primary Access Token</p>
<p>Leave blank normally.</p>
<p>Properties:</p>
<ul>
<li>Config: access_token</li>
<li>Env Var: RCLONE_BOX_ACCESS_TOKEN</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="box-box-sub-type">--box-box-sub-type</h4>
<p>Properties:</p>
<ul>
<li>Config: box_sub_type</li>
<li>Env Var: RCLONE_BOX_BOX_SUB_TYPE</li>
<li>Type: string</li>
<li>Default: "user"</li>
<li>Examples:
<ul>
<li>"user"
<ul>
<li>Rclone should act on behalf of a user.</li>
</ul></li>
<li>"enterprise"
<ul>
<li>Rclone should act on behalf of a service account.</li>
</ul></li>
</ul></li>
</ul>
<h3 id="advanced-options-4">Advanced options</h3>
<p>Here are the Advanced options specific to box (Box).</p>
<h4 id="box-token">--box-token</h4>
<p>OAuth Access Token as a JSON blob.</p>
<p>Properties:</p>
<ul>
<li>Config: token</li>
<li>Env Var: RCLONE_BOX_TOKEN</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="box-auth-url">--box-auth-url</h4>
<p>Auth server URL.</p>
<p>Leave blank to use the provider defaults.</p>
<p>Properties:</p>
<ul>
<li>Config: auth_url</li>
<li>Env Var: RCLONE_BOX_AUTH_URL</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="box-token-url">--box-token-url</h4>
<p>Token server url.</p>
<p>Leave blank to use the provider defaults.</p>
<p>Properties:</p>
<ul>
<li>Config: token_url</li>
<li>Env Var: RCLONE_BOX_TOKEN_URL</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="box-root-folder-id">--box-root-folder-id</h4>
<p>Fill in for rclone to use a non root folder as its starting point.</p>
<p>Properties:</p>
<ul>
<li>Config: root_folder_id</li>
<li>Env Var: RCLONE_BOX_ROOT_FOLDER_ID</li>
<li>Type: string</li>
<li>Default: "0"</li>
</ul>
<h4 id="box-upload-cutoff">--box-upload-cutoff</h4>
<p>Cutoff for switching to multipart upload (&gt;= 50 MiB).</p>
<p>Properties:</p>
<ul>
<li>Config: upload_cutoff</li>
<li>Env Var: RCLONE_BOX_UPLOAD_CUTOFF</li>
<li>Type: SizeSuffix</li>
<li>Default: 50Mi</li>
</ul>
<h4 id="box-commit-retries">--box-commit-retries</h4>
<p>Max number of times to try committing a multipart file.</p>
<p>Properties:</p>
<ul>
<li>Config: commit_retries</li>
<li>Env Var: RCLONE_BOX_COMMIT_RETRIES</li>
<li>Type: int</li>
<li>Default: 100</li>
</ul>
<h4 id="box-list-chunk">--box-list-chunk</h4>
<p>Size of listing chunk 1-1000.</p>
<p>Properties:</p>
<ul>
<li>Config: list_chunk</li>
<li>Env Var: RCLONE_BOX_LIST_CHUNK</li>
<li>Type: int</li>
<li>Default: 1000</li>
</ul>
<h4 id="box-owned-by">--box-owned-by</h4>
<p>Only show items owned by the login (email address) passed in.</p>
<p>Properties:</p>
<ul>
<li>Config: owned_by</li>
<li>Env Var: RCLONE_BOX_OWNED_BY</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="box-impersonate">--box-impersonate</h4>
<p>Impersonate this user ID when using a service account.</p>
<p>Setting this flag allows rclone, when using a JWT service account, to act on behalf of another user by setting the as-user header.</p>
<p>The user ID is the Box identifier for a user. User IDs can found for any user via the GET /users endpoint, which is only available to admins, or by calling the GET /users/me endpoint with an authenticated user session.</p>
<p>See: https://developer.box.com/guides/authentication/jwt/as-user/</p>
<p>Properties:</p>
<ul>
<li>Config: impersonate</li>
<li>Env Var: RCLONE_BOX_IMPERSONATE</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="box-encoding">--box-encoding</h4>
<p>The encoding for the backend.</p>
<p>See the <a href="https://rclone.org/overview/#encoding">encoding section in the overview</a> for more info.</p>
<p>Properties:</p>
<ul>
<li>Config: encoding</li>
<li>Env Var: RCLONE_BOX_ENCODING</li>
<li>Type: Encoding</li>
<li>Default: Slash,BackSlash,Del,Ctl,RightSpace,InvalidUtf8,Dot</li>
</ul>
<h4 id="box-description">--box-description</h4>
<p>Description of the remote.</p>
<p>Properties:</p>
<ul>
<li>Config: description</li>
<li>Env Var: RCLONE_BOX_DESCRIPTION</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h2 id="limitations-8">Limitations</h2>
<p>Note that Box is case insensitive so you can't have a file called "Hello.doc" and one called "hello.doc".</p>
<p>Box file names can't have the <code>\</code> character in. rclone maps this to and from an identical looking unicode equivalent <code>＼</code> (U+FF3C Fullwidth Reverse Solidus).</p>
<p>Box only supports filenames up to 255 characters in length.</p>
<p>Box has <a href="https://developer.box.com/guides/api-calls/permissions-and-errors/rate-limits/">API rate limits</a> that sometimes reduce the speed of rclone.</p>
<p><code>rclone about</code> is not supported by the Box backend. Backends without this capability cannot determine free space for an rclone mount or use policy <code>mfs</code> (most free space) as a member of an rclone union remote.</p>
<p>See <a href="https://rclone.org/overview/#optional-features">List of backends that do not support rclone about</a> and <a href="https://rclone.org/commands/rclone_about/">rclone about</a></p>
<h2 id="get-your-own-box-app-id">Get your own Box App ID</h2>
<p>Here is how to create your own Box App ID for rclone:</p>
<ol type="1">
<li><p>Go to the <a href="https://app.box.com/developers/console">Box Developer Console</a> and login, then click <code>My Apps</code> on the sidebar. Click <code>Create New App</code> and select <code>Custom App</code>.</p></li>
<li><p>In the first screen on the box that pops up, you can pretty much enter whatever you want. The <code>App Name</code> can be whatever. For <code>Purpose</code> choose automation to avoid having to fill out anything else. Click <code>Next</code>.</p></li>
<li><p>In the second screen of the creation screen, select <code>User Authentication (OAuth 2.0)</code>. Then click <code>Create App</code>.</p></li>
<li><p>You should now be on the <code>Configuration</code> tab of your new app. If not, click on it at the top of the webpage. Copy down <code>Client ID</code> and <code>Client Secret</code>, you'll need those for rclone.</p></li>
<li><p>Under "OAuth 2.0 Redirect URI", add <code>http://127.0.0.1:53682/</code></p></li>
<li><p>For <code>Application Scopes</code>, select <code>Read all files and folders stored in Box</code> and <code>Write all files and folders stored in box</code> (assuming you want to do both). Leave others unchecked. Click <code>Save Changes</code> at the top right.</p></li>
</ol>
<h1 id="cache">Cache</h1>
<p>The <code>cache</code> remote wraps another existing remote and stores file structure and its data for long running tasks like <code>rclone mount</code>.</p>
<h2 id="status">Status</h2>
<p>The cache backend code is working but it currently doesn't have a maintainer so there are <a href="https://github.com/rclone/rclone/issues?q=is%3Aopen+is%3Aissue+label%3Abug+label%3A%22Remote%3A+Cache%22">outstanding bugs</a> which aren't getting fixed.</p>
<p>The cache backend is due to be phased out in favour of the VFS caching layer eventually which is more tightly integrated into rclone.</p>
<p>Until this happens we recommend only using the cache backend if you find you can't work without it. There are many docs online describing the use of the cache backend to minimize API hits and by-and-large these are out of date and the cache backend isn't needed in those scenarios any more.</p>
<h2 id="configuration-5">Configuration</h2>
<p>To get started you just need to have an existing remote which can be configured with <code>cache</code>.</p>
<p>Here is an example of how to make a remote called <code>test-cache</code>. First run:</p>
<pre><code> rclone config</code></pre>
<p>This will guide you through an interactive setup process:</p>
<pre><code>No remotes found, make a new one?
n) New remote
r) Rename remote
c) Copy remote
s) Set configuration password
q) Quit config
n/r/c/s/q&gt; n
name&gt; test-cache
Type of storage to configure.
Choose a number from below, or type in your own value
[snip]
XX / Cache a remote
   \ &quot;cache&quot;
[snip]
Storage&gt; cache
Remote to cache.
Normally should contain a &#39;:&#39; and a path, e.g. &quot;myremote:path/to/dir&quot;,
&quot;myremote:bucket&quot; or maybe &quot;myremote:&quot; (not recommended).
remote&gt; local:/test
Optional: The URL of the Plex server
plex_url&gt; http://127.0.0.1:32400
Optional: The username of the Plex user
plex_username&gt; dummyusername
Optional: The password of the Plex user
y) Yes type in my own password
g) Generate random password
n) No leave this optional password blank
y/g/n&gt; y
Enter the password:
password:
Confirm the password:
password:
The size of a chunk. Lower value good for slow connections but can affect seamless reading.
Default: 5M
Choose a number from below, or type in your own value
 1 / 1 MiB
   \ &quot;1M&quot;
 2 / 5 MiB
   \ &quot;5M&quot;
 3 / 10 MiB
   \ &quot;10M&quot;
chunk_size&gt; 2
How much time should object info (file size, file hashes, etc.) be stored in cache. Use a very high value if you don&#39;t plan on changing the source FS from outside the cache.
Accepted units are: &quot;s&quot;, &quot;m&quot;, &quot;h&quot;.
Default: 5m
Choose a number from below, or type in your own value
 1 / 1 hour
   \ &quot;1h&quot;
 2 / 24 hours
   \ &quot;24h&quot;
 3 / 24 hours
   \ &quot;48h&quot;
info_age&gt; 2
The maximum size of stored chunks. When the storage grows beyond this size, the oldest chunks will be deleted.
Default: 10G
Choose a number from below, or type in your own value
 1 / 500 MiB
   \ &quot;500M&quot;
 2 / 1 GiB
   \ &quot;1G&quot;
 3 / 10 GiB
   \ &quot;10G&quot;
chunk_total_size&gt; 3
Remote config
--------------------
[test-cache]
remote = local:/test
plex_url = http://127.0.0.1:32400
plex_username = dummyusername
plex_password = *** ENCRYPTED ***
chunk_size = 5M
info_age = 48h
chunk_total_size = 10G</code></pre>
<p>You can then use it like this,</p>
<p>List directories in top level of your drive</p>
<pre><code>rclone lsd test-cache:</code></pre>
<p>List all the files in your drive</p>
<pre><code>rclone ls test-cache:</code></pre>
<p>To start a cached mount</p>
<pre><code>rclone mount --allow-other test-cache: /var/tmp/test-cache</code></pre>
<h3 id="write-features">Write Features</h3>
<h3 id="offline-uploading">Offline uploading</h3>
<p>In an effort to make writing through cache more reliable, the backend now supports this feature which can be activated by specifying a <code>cache-tmp-upload-path</code>.</p>
<p>A files goes through these states when using this feature:</p>
<ol type="1">
<li>An upload is started (usually by copying a file on the cache remote)</li>
<li>When the copy to the temporary location is complete the file is part of the cached remote and looks and behaves like any other file (reading included)</li>
<li>After <code>cache-tmp-wait-time</code> passes and the file is next in line, <code>rclone move</code> is used to move the file to the cloud provider</li>
<li>Reading the file still works during the upload but most modifications on it will be prohibited</li>
<li>Once the move is complete the file is unlocked for modifications as it becomes as any other regular file</li>
<li>If the file is being read through <code>cache</code> when it's actually deleted from the temporary path then <code>cache</code> will simply swap the source to the cloud provider without interrupting the reading (small blip can happen though)</li>
</ol>
<p>Files are uploaded in sequence and only one file is uploaded at a time. Uploads will be stored in a queue and be processed based on the order they were added. The queue and the temporary storage is persistent across restarts but can be cleared on startup with the <code>--cache-db-purge</code> flag.</p>
<h3 id="write-support">Write Support</h3>
<p>Writes are supported through <code>cache</code>. One caveat is that a mounted cache remote does not add any retry or fallback mechanism to the upload operation. This will depend on the implementation of the wrapped remote. Consider using <code>Offline uploading</code> for reliable writes.</p>
<p>One special case is covered with <code>cache-writes</code> which will cache the file data at the same time as the upload when it is enabled making it available from the cache store immediately once the upload is finished.</p>
<h3 id="read-features">Read Features</h3>
<h4 id="multiple-connections">Multiple connections</h4>
<p>To counter the high latency between a local PC where rclone is running and cloud providers, the cache remote can split multiple requests to the cloud provider for smaller file chunks and combines them together locally where they can be available almost immediately before the reader usually needs them.</p>
<p>This is similar to buffering when media files are played online. Rclone will stay around the current marker but always try its best to stay ahead and prepare the data before.</p>
<h4 id="plex-integration">Plex Integration</h4>
<p>There is a direct integration with Plex which allows cache to detect during reading if the file is in playback or not. This helps cache to adapt how it queries the cloud provider depending on what is needed for.</p>
<p>Scans will have a minimum amount of workers (1) while in a confirmed playback cache will deploy the configured number of workers.</p>
<p>This integration opens the doorway to additional performance improvements which will be explored in the near future.</p>
<p><strong>Note:</strong> If Plex options are not configured, <code>cache</code> will function with its configured options without adapting any of its settings.</p>
<p>How to enable? Run <code>rclone config</code> and add all the Plex options (endpoint, username and password) in your remote and it will be automatically enabled.</p>
<p>Affected settings: - <code>cache-workers</code>: <em>Configured value</em> during confirmed playback or <em>1</em> all the other times</p>
<h5 id="certificate-validation">Certificate Validation</h5>
<p>When the Plex server is configured to only accept secure connections, it is possible to use <code>.plex.direct</code> URLs to ensure certificate validation succeeds. These URLs are used by Plex internally to connect to the Plex server securely.</p>
<p>The format for these URLs is the following:</p>
<p><code>https://ip-with-dots-replaced.server-hash.plex.direct:32400/</code></p>
<p>The <code>ip-with-dots-replaced</code> part can be any IPv4 address, where the dots have been replaced with dashes, e.g. <code>127.0.0.1</code> becomes <code>127-0-0-1</code>.</p>
<p>To get the <code>server-hash</code> part, the easiest way is to visit</p>
<p>https://plex.tv/api/resources?includeHttps=1&amp;X-Plex-Token=your-plex-token</p>
<p>This page will list all the available Plex servers for your account with at least one <code>.plex.direct</code> link for each. Copy one URL and replace the IP address with the desired address. This can be used as the <code>plex_url</code> value.</p>
<h3 id="known-issues">Known issues</h3>
<h4 id="mount-and---dir-cache-time">Mount and --dir-cache-time</h4>
<p>--dir-cache-time controls the first layer of directory caching which works at the mount layer. Being an independent caching mechanism from the <code>cache</code> backend, it will manage its own entries based on the configured time.</p>
<p>To avoid getting in a scenario where dir cache has obsolete data and cache would have the correct one, try to set <code>--dir-cache-time</code> to a lower time than <code>--cache-info-age</code>. Default values are already configured in this way.</p>
<h4 id="windows-support---experimental">Windows support - Experimental</h4>
<p>There are a couple of issues with Windows <code>mount</code> functionality that still require some investigations. It should be considered as experimental thus far as fixes come in for this OS.</p>
<p>Most of the issues seem to be related to the difference between filesystems on Linux flavors and Windows as cache is heavily dependent on them.</p>
<p>Any reports or feedback on how cache behaves on this OS is greatly appreciated.</p>
<ul>
<li>https://github.com/rclone/rclone/issues/1935</li>
<li>https://github.com/rclone/rclone/issues/1907</li>
<li>https://github.com/rclone/rclone/issues/1834</li>
</ul>
<h4 id="risk-of-throttling">Risk of throttling</h4>
<p>Future iterations of the cache backend will make use of the pooling functionality of the cloud provider to synchronize and at the same time make writing through it more tolerant to failures.</p>
<p>There are a couple of enhancements in track to add these but in the meantime there is a valid concern that the expiring cache listings can lead to cloud provider throttles or bans due to repeated queries on it for very large mounts.</p>
<p>Some recommendations: - don't use a very small interval for entry information (<code>--cache-info-age</code>) - while writes aren't yet optimised, you can still write through <code>cache</code> which gives you the advantage of adding the file in the cache at the same time if configured to do so.</p>
<p>Future enhancements:</p>
<ul>
<li>https://github.com/rclone/rclone/issues/1937</li>
<li>https://github.com/rclone/rclone/issues/1936</li>
</ul>
<h4 id="cache-and-crypt">cache and crypt</h4>
<p>One common scenario is to keep your data encrypted in the cloud provider using the <code>crypt</code> remote. <code>crypt</code> uses a similar technique to wrap around an existing remote and handles this translation in a seamless way.</p>
<p>There is an issue with wrapping the remotes in this order: <strong>cloud remote</strong> -&gt; <strong>crypt</strong> -&gt; <strong>cache</strong></p>
<p>During testing, I experienced a lot of bans with the remotes in this order. I suspect it might be related to how crypt opens files on the cloud provider which makes it think we're downloading the full file instead of small chunks. Organizing the remotes in this order yields better results: <strong>cloud remote</strong> -&gt; <strong>cache</strong> -&gt; <strong>crypt</strong></p>
<h4 id="absolute-remote-paths">absolute remote paths</h4>
<p><code>cache</code> can not differentiate between relative and absolute paths for the wrapped remote. Any path given in the <code>remote</code> config setting and on the command line will be passed to the wrapped remote as is, but for storing the chunks on disk the path will be made relative by removing any leading <code>/</code> character.</p>
<p>This behavior is irrelevant for most backend types, but there are backends where a leading <code>/</code> changes the effective directory, e.g. in the <code>sftp</code> backend paths starting with a <code>/</code> are relative to the root of the SSH server and paths without are relative to the user home directory. As a result <code>sftp:bin</code> and <code>sftp:/bin</code> will share the same cache folder, even if they represent a different directory on the SSH server.</p>
<h3 id="cache-and-remote-control---rc">Cache and Remote Control (--rc)</h3>
<p>Cache supports the new <code>--rc</code> mode in rclone and can be remote controlled through the following end points: By default, the listener is disabled if you do not add the flag.</p>
<h3 id="rc-cacheexpire">rc cache/expire</h3>
<p>Purge a remote from the cache backend. Supports either a directory or a file. It supports both encrypted and unencrypted file names if cache is wrapped by crypt.</p>
<p>Params: - <strong>remote</strong> = path to remote <strong>(required)</strong> - <strong>withData</strong> = true/false to delete cached data (chunks) as well <em>(optional, false by default)</em></p>
<h3 id="standard-options-5">Standard options</h3>
<p>Here are the Standard options specific to cache (Cache a remote).</p>
<h4 id="cache-remote">--cache-remote</h4>
<p>Remote to cache.</p>
<p>Normally should contain a ':' and a path, e.g. "myremote:path/to/dir", "myremote:bucket" or maybe "myremote:" (not recommended).</p>
<p>Properties:</p>
<ul>
<li>Config: remote</li>
<li>Env Var: RCLONE_CACHE_REMOTE</li>
<li>Type: string</li>
<li>Required: true</li>
</ul>
<h4 id="cache-plex-url">--cache-plex-url</h4>
<p>The URL of the Plex server.</p>
<p>Properties:</p>
<ul>
<li>Config: plex_url</li>
<li>Env Var: RCLONE_CACHE_PLEX_URL</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="cache-plex-username">--cache-plex-username</h4>
<p>The username of the Plex user.</p>
<p>Properties:</p>
<ul>
<li>Config: plex_username</li>
<li>Env Var: RCLONE_CACHE_PLEX_USERNAME</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="cache-plex-password">--cache-plex-password</h4>
<p>The password of the Plex user.</p>
<p><strong>NB</strong> Input to this must be obscured - see <a href="https://rclone.org/commands/rclone_obscure/">rclone obscure</a>.</p>
<p>Properties:</p>
<ul>
<li>Config: plex_password</li>
<li>Env Var: RCLONE_CACHE_PLEX_PASSWORD</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="cache-chunk-size">--cache-chunk-size</h4>
<p>The size of a chunk (partial file data).</p>
<p>Use lower numbers for slower connections. If the chunk size is changed, any downloaded chunks will be invalid and cache-chunk-path will need to be cleared or unexpected EOF errors will occur.</p>
<p>Properties:</p>
<ul>
<li>Config: chunk_size</li>
<li>Env Var: RCLONE_CACHE_CHUNK_SIZE</li>
<li>Type: SizeSuffix</li>
<li>Default: 5Mi</li>
<li>Examples:
<ul>
<li>"1M"
<ul>
<li>1 MiB</li>
</ul></li>
<li>"5M"
<ul>
<li>5 MiB</li>
</ul></li>
<li>"10M"
<ul>
<li>10 MiB</li>
</ul></li>
</ul></li>
</ul>
<h4 id="cache-info-age">--cache-info-age</h4>
<p>How long to cache file structure information (directory listings, file size, times, etc.). If all write operations are done through the cache then you can safely make this value very large as the cache store will also be updated in real time.</p>
<p>Properties:</p>
<ul>
<li>Config: info_age</li>
<li>Env Var: RCLONE_CACHE_INFO_AGE</li>
<li>Type: Duration</li>
<li>Default: 6h0m0s</li>
<li>Examples:
<ul>
<li>"1h"
<ul>
<li>1 hour</li>
</ul></li>
<li>"24h"
<ul>
<li>24 hours</li>
</ul></li>
<li>"48h"
<ul>
<li>48 hours</li>
</ul></li>
</ul></li>
</ul>
<h4 id="cache-chunk-total-size">--cache-chunk-total-size</h4>
<p>The total size that the chunks can take up on the local disk.</p>
<p>If the cache exceeds this value then it will start to delete the oldest chunks until it goes under this value.</p>
<p>Properties:</p>
<ul>
<li>Config: chunk_total_size</li>
<li>Env Var: RCLONE_CACHE_CHUNK_TOTAL_SIZE</li>
<li>Type: SizeSuffix</li>
<li>Default: 10Gi</li>
<li>Examples:
<ul>
<li>"500M"
<ul>
<li>500 MiB</li>
</ul></li>
<li>"1G"
<ul>
<li>1 GiB</li>
</ul></li>
<li>"10G"
<ul>
<li>10 GiB</li>
</ul></li>
</ul></li>
</ul>
<h3 id="advanced-options-5">Advanced options</h3>
<p>Here are the Advanced options specific to cache (Cache a remote).</p>
<h4 id="cache-plex-token">--cache-plex-token</h4>
<p>The plex token for authentication - auto set normally.</p>
<p>Properties:</p>
<ul>
<li>Config: plex_token</li>
<li>Env Var: RCLONE_CACHE_PLEX_TOKEN</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="cache-plex-insecure">--cache-plex-insecure</h4>
<p>Skip all certificate verification when connecting to the Plex server.</p>
<p>Properties:</p>
<ul>
<li>Config: plex_insecure</li>
<li>Env Var: RCLONE_CACHE_PLEX_INSECURE</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="cache-db-path">--cache-db-path</h4>
<p>Directory to store file structure metadata DB.</p>
<p>The remote name is used as the DB file name.</p>
<p>Properties:</p>
<ul>
<li>Config: db_path</li>
<li>Env Var: RCLONE_CACHE_DB_PATH</li>
<li>Type: string</li>
<li>Default: "$HOME/.cache/rclone/cache-backend"</li>
</ul>
<h4 id="cache-chunk-path">--cache-chunk-path</h4>
<p>Directory to cache chunk files.</p>
<p>Path to where partial file data (chunks) are stored locally. The remote name is appended to the final path.</p>
<p>This config follows the "--cache-db-path". If you specify a custom location for "--cache-db-path" and don't specify one for "--cache-chunk-path" then "--cache-chunk-path" will use the same path as "--cache-db-path".</p>
<p>Properties:</p>
<ul>
<li>Config: chunk_path</li>
<li>Env Var: RCLONE_CACHE_CHUNK_PATH</li>
<li>Type: string</li>
<li>Default: "$HOME/.cache/rclone/cache-backend"</li>
</ul>
<h4 id="cache-db-purge">--cache-db-purge</h4>
<p>Clear all the cached data for this remote on start.</p>
<p>Properties:</p>
<ul>
<li>Config: db_purge</li>
<li>Env Var: RCLONE_CACHE_DB_PURGE</li>
<li>Type: bool</li>
<li>Default: false</li>
</ul>
<h4 id="cache-chunk-clean-interval">--cache-chunk-clean-interval</h4>
<p>How often should the cache perform cleanups of the chunk storage.</p>
<p>The default value should be ok for most people. If you find that the cache goes over "cache-chunk-total-size" too often then try to lower this value to force it to perform cleanups more often.</p>
<p>Properties:</p>
<ul>
<li>Config: chunk_clean_interval</li>
<li>Env Var: RCLONE_CACHE_CHUNK_CLEAN_INTERVAL</li>
<li>Type: Duration</li>
<li>Default: 1m0s</li>
</ul>
<h4 id="cache-read-retries">--cache-read-retries</h4>
<p>How many times to retry a read from a cache storage.</p>
<p>Since reading from a cache stream is independent from downloading file data, readers can get to a point where there's no more data in the cache. Most of the times this can indicate a connectivity issue if cache isn't able to provide file data anymore.</p>
<p>For really slow connections, increase this to a point where the stream is able to provide data but your experience will be very stuttering.</p>
<p>Properties:</p>
<ul>
<li>Config: read_retries</li>
<li>Env Var: RCLONE_CACHE_READ_RETRIES</li>
<li>Type: int</li>
<li>Default: 10</li>
</ul>
<h4 id="cache-workers">--cache-workers</h4>
<p>How many workers should run in parallel to download chunks.</p>
<p>Higher values will mean more parallel processing (better CPU needed) and more concurrent requests on the cloud provider. This impacts several aspects like the cloud provider API limits, more stress on the hardware that rclone runs on but it also means that streams will be more fluid and data will be available much more faster to readers.</p>
<p><strong>Note</strong>: If the optional Plex integration is enabled then this setting will adapt to the type of reading performed and the value specified here will be used as a maximum number of workers to use.</p>
<p>Properties:</p>
<ul>
<li>Config: workers</li>
<li>Env Var: RCLONE_CACHE_WORKERS</li>
<li>Type: int</li>
<li>Default: 4</li>
</ul>
<h4 id="cache-chunk-no-memory">--cache-chunk-no-memory</h4>
<p>Disable the in-memory cache for storing chunks during streaming.</p>
<p>By default, cache will keep file data during streaming in RAM as well to provide it to readers as fast as possible.</p>
<p>This transient data is evicted as soon as it is read and the number of chunks stored doesn't exceed the number of workers. However, depending on other settings like "cache-chunk-size" and "cache-workers" this footprint can increase if there are parallel streams too (multiple files being read at the same time).</p>
<p>If the hardware permits it, use this feature to provide an overall better performance during streaming but it can also be disabled if RAM is not available on the local machine.</p>
<p>Properties:</p>
<ul>
<li>Config: chunk_no_memory</li>
<li>Env Var: RCLONE_CACHE_CHUNK_NO_MEMORY</li>
<li>Type: bool</li>
<li>Default: false</li>
</ul>
<h4 id="cache-rps">--cache-rps</h4>
<p>Limits the number of requests per second to the source FS (-1 to disable).</p>
<p>This setting places a hard limit on the number of requests per second that cache will be doing to the cloud provider remote and try to respect that value by setting waits between reads.</p>
<p>If you find that you're getting banned or limited on the cloud provider through cache and know that a smaller number of requests per second will allow you to work with it then you can use this setting for that.</p>
<p>A good balance of all the other settings should make this setting useless but it is available to set for more special cases.</p>
<p><strong>NOTE</strong>: This will limit the number of requests during streams but other API calls to the cloud provider like directory listings will still pass.</p>
<p>Properties:</p>
<ul>
<li>Config: rps</li>
<li>Env Var: RCLONE_CACHE_RPS</li>
<li>Type: int</li>
<li>Default: -1</li>
</ul>
<h4 id="cache-writes">--cache-writes</h4>
<p>Cache file data on writes through the FS.</p>
<p>If you need to read files immediately after you upload them through cache you can enable this flag to have their data stored in the cache store at the same time during upload.</p>
<p>Properties:</p>
<ul>
<li>Config: writes</li>
<li>Env Var: RCLONE_CACHE_WRITES</li>
<li>Type: bool</li>
<li>Default: false</li>
</ul>
<h4 id="cache-tmp-upload-path">--cache-tmp-upload-path</h4>
<p>Directory to keep temporary files until they are uploaded.</p>
<p>This is the path where cache will use as a temporary storage for new files that need to be uploaded to the cloud provider.</p>
<p>Specifying a value will enable this feature. Without it, it is completely disabled and files will be uploaded directly to the cloud provider</p>
<p>Properties:</p>
<ul>
<li>Config: tmp_upload_path</li>
<li>Env Var: RCLONE_CACHE_TMP_UPLOAD_PATH</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="cache-tmp-wait-time">--cache-tmp-wait-time</h4>
<p>How long should files be stored in local cache before being uploaded.</p>
<p>This is the duration that a file must wait in the temporary location <em>cache-tmp-upload-path</em> before it is selected for upload.</p>
<p>Note that only one file is uploaded at a time and it can take longer to start the upload if a queue formed for this purpose.</p>
<p>Properties:</p>
<ul>
<li>Config: tmp_wait_time</li>
<li>Env Var: RCLONE_CACHE_TMP_WAIT_TIME</li>
<li>Type: Duration</li>
<li>Default: 15s</li>
</ul>
<h4 id="cache-db-wait-time">--cache-db-wait-time</h4>
<p>How long to wait for the DB to be available - 0 is unlimited.</p>
<p>Only one process can have the DB open at any one time, so rclone waits for this duration for the DB to become available before it gives an error.</p>
<p>If you set it to 0 then it will wait forever.</p>
<p>Properties:</p>
<ul>
<li>Config: db_wait_time</li>
<li>Env Var: RCLONE_CACHE_DB_WAIT_TIME</li>
<li>Type: Duration</li>
<li>Default: 1s</li>
</ul>
<h4 id="cache-description">--cache-description</h4>
<p>Description of the remote.</p>
<p>Properties:</p>
<ul>
<li>Config: description</li>
<li>Env Var: RCLONE_CACHE_DESCRIPTION</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h2 id="backend-commands-2">Backend commands</h2>
<p>Here are the commands specific to the cache backend.</p>
<p>Run them with</p>
<pre><code>rclone backend COMMAND remote:</code></pre>
<p>The help below will explain what arguments each command takes.</p>
<p>See the <a href="https://rclone.org/commands/rclone_backend/">backend</a> command for more info on how to pass options and arguments.</p>
<p>These can be run on a running backend using the rc command <a href="https://rclone.org/rc/#backend-command">backend/command</a>.</p>
<h3 id="stats">stats</h3>
<p>Print stats on the cache backend in JSON format.</p>
<pre><code>rclone backend stats remote: [options] [&lt;arguments&gt;+]</code></pre>
<h1 id="chunker">Chunker</h1>
<p>The <code>chunker</code> overlay transparently splits large files into smaller chunks during upload to wrapped remote and transparently assembles them back when the file is downloaded. This allows to effectively overcome size limits imposed by storage providers.</p>
<h2 id="configuration-6">Configuration</h2>
<p>To use it, first set up the underlying remote following the configuration instructions for that remote. You can also use a local pathname instead of a remote.</p>
<p>First check your chosen remote is working - we'll call it <code>remote:path</code> here. Note that anything inside <code>remote:path</code> will be chunked and anything outside won't. This means that if you are using a bucket-based remote (e.g. S3, B2, swift) then you should probably put the bucket in the remote <code>s3:bucket</code>.</p>
<p>Now configure <code>chunker</code> using <code>rclone config</code>. We will call this one <code>overlay</code> to separate it from the <code>remote</code> itself.</p>
<pre><code>No remotes found, make a new one?
n) New remote
s) Set configuration password
q) Quit config
n/s/q&gt; n
name&gt; overlay
Type of storage to configure.
Choose a number from below, or type in your own value
[snip]
XX / Transparently chunk/split large files
   \ &quot;chunker&quot;
[snip]
Storage&gt; chunker
Remote to chunk/unchunk.
Normally should contain a &#39;:&#39; and a path, e.g. &quot;myremote:path/to/dir&quot;,
&quot;myremote:bucket&quot; or maybe &quot;myremote:&quot; (not recommended).
Enter a string value. Press Enter for the default (&quot;&quot;).
remote&gt; remote:path
Files larger than chunk size will be split in chunks.
Enter a size with suffix K,M,G,T. Press Enter for the default (&quot;2G&quot;).
chunk_size&gt; 100M
Choose how chunker handles hash sums. All modes but &quot;none&quot; require metadata.
Enter a string value. Press Enter for the default (&quot;md5&quot;).
Choose a number from below, or type in your own value
 1 / Pass any hash supported by wrapped remote for non-chunked files, return nothing otherwise
   \ &quot;none&quot;
 2 / MD5 for composite files
   \ &quot;md5&quot;
 3 / SHA1 for composite files
   \ &quot;sha1&quot;
 4 / MD5 for all files
   \ &quot;md5all&quot;
 5 / SHA1 for all files
   \ &quot;sha1all&quot;
 6 / Copying a file to chunker will request MD5 from the source falling back to SHA1 if unsupported
   \ &quot;md5quick&quot;
 7 / Similar to &quot;md5quick&quot; but prefers SHA1 over MD5
   \ &quot;sha1quick&quot;
hash_type&gt; md5
Edit advanced config? (y/n)
y) Yes
n) No
y/n&gt; n
Remote config
--------------------
[overlay]
type = chunker
remote = remote:bucket
chunk_size = 100M
hash_type = md5
--------------------
y) Yes this is OK
e) Edit this remote
d) Delete this remote
y/e/d&gt; y</code></pre>
<h3 id="specifying-the-remote">Specifying the remote</h3>
<p>In normal use, make sure the remote has a <code>:</code> in. If you specify the remote without a <code>:</code> then rclone will use a local directory of that name. So if you use a remote of <code>/path/to/secret/files</code> then rclone will chunk stuff in that directory. If you use a remote of <code>name</code> then rclone will put files in a directory called <code>name</code> in the current directory.</p>
<h3 id="chunking">Chunking</h3>
<p>When rclone starts a file upload, chunker checks the file size. If it doesn't exceed the configured chunk size, chunker will just pass the file to the wrapped remote (however, see caveat below). If a file is large, chunker will transparently cut data in pieces with temporary names and stream them one by one, on the fly. Each data chunk will contain the specified number of bytes, except for the last one which may have less data. If file size is unknown in advance (this is called a streaming upload), chunker will internally create a temporary copy, record its size and repeat the above process.</p>
<p>When upload completes, temporary chunk files are finally renamed. This scheme guarantees that operations can be run in parallel and look from outside as atomic. A similar method with hidden temporary chunks is used for other operations (copy/move/rename, etc.). If an operation fails, hidden chunks are normally destroyed, and the target composite file stays intact.</p>
<p>When a composite file download is requested, chunker transparently assembles it by concatenating data chunks in order. As the split is trivial one could even manually concatenate data chunks together to obtain the original content.</p>
<p>When the <code>list</code> rclone command scans a directory on wrapped remote, the potential chunk files are accounted for, grouped and assembled into composite directory entries. Any temporary chunks are hidden.</p>
<p>List and other commands can sometimes come across composite files with missing or invalid chunks, e.g. shadowed by like-named directory or another file. This usually means that wrapped file system has been directly tampered with or damaged. If chunker detects a missing chunk it will by default print warning, skip the whole incomplete group of chunks but proceed with current command. You can set the <code>--chunker-fail-hard</code> flag to have commands abort with error message in such cases.</p>
<p><strong>Caveat</strong>: As it is now, chunker will always create a temporary file in the backend and then rename it, even if the file is below the chunk threshold. This will result in unnecessary API calls and can severely restrict throughput when handling transfers primarily composed of small files on some backends (e.g. Box). A workaround to this issue is to use chunker only for files above the chunk threshold via <code>--min-size</code> and then perform a separate call without chunker on the remaining files.</p>
<h4 id="chunk-names">Chunk names</h4>
<p>The default chunk name format is <code>*.rclone_chunk.###</code>, hence by default chunk names are <code>BIG_FILE_NAME.rclone_chunk.001</code>, <code>BIG_FILE_NAME.rclone_chunk.002</code> etc. You can configure another name format using the <code>name_format</code> configuration file option. The format uses asterisk <code>*</code> as a placeholder for the base file name and one or more consecutive hash characters <code>#</code> as a placeholder for sequential chunk number. There must be one and only one asterisk. The number of consecutive hash characters defines the minimum length of a string representing a chunk number. If decimal chunk number has less digits than the number of hashes, it is left-padded by zeros. If the decimal string is longer, it is left intact. By default numbering starts from 1 but there is another option that allows user to start from 0, e.g. for compatibility with legacy software.</p>
<p>For example, if name format is <code>big_*-##.part</code> and original file name is <code>data.txt</code> and numbering starts from 0, then the first chunk will be named <code>big_data.txt-00.part</code>, the 99th chunk will be <code>big_data.txt-98.part</code> and the 302nd chunk will become <code>big_data.txt-301.part</code>.</p>
<p>Note that <code>list</code> assembles composite directory entries only when chunk names match the configured format and treats non-conforming file names as normal non-chunked files.</p>
<p>When using <code>norename</code> transactions, chunk names will additionally have a unique file version suffix. For example, <code>BIG_FILE_NAME.rclone_chunk.001_bp562k</code>.</p>
<h3 id="metadata-4">Metadata</h3>
<p>Besides data chunks chunker will by default create metadata object for a composite file. The object is named after the original file. Chunker allows user to disable metadata completely (the <code>none</code> format). Note that metadata is normally not created for files smaller than the configured chunk size. This may change in future rclone releases.</p>
<h4 id="simple-json-metadata-format">Simple JSON metadata format</h4>
<p>This is the default format. It supports hash sums and chunk validation for composite files. Meta objects carry the following fields:</p>
<ul>
<li><code>ver</code> - version of format, currently <code>1</code></li>
<li><code>size</code> - total size of composite file</li>
<li><code>nchunks</code> - number of data chunks in file</li>
<li><code>md5</code> - MD5 hashsum of composite file (if present)</li>
<li><code>sha1</code> - SHA1 hashsum (if present)</li>
<li><code>txn</code> - identifies current version of the file</li>
</ul>
<p>There is no field for composite file name as it's simply equal to the name of meta object on the wrapped remote. Please refer to respective sections for details on hashsums and modified time handling.</p>
<h4 id="no-metadata">No metadata</h4>
<p>You can disable meta objects by setting the meta format option to <code>none</code>. In this mode chunker will scan directory for all files that follow configured chunk name format, group them by detecting chunks with the same base name and show group names as virtual composite files. This method is more prone to missing chunk errors (especially missing last chunk) than format with metadata enabled.</p>
<h3 id="hashsums">Hashsums</h3>
<p>Chunker supports hashsums only when a compatible metadata is present. Hence, if you choose metadata format of <code>none</code>, chunker will report hashsum as <code>UNSUPPORTED</code>.</p>
<p>Please note that by default metadata is stored only for composite files. If a file is smaller than configured chunk size, chunker will transparently redirect hash requests to wrapped remote, so support depends on that. You will see the empty string as a hashsum of requested type for small files if the wrapped remote doesn't support it.</p>
<p>Many storage backends support MD5 and SHA1 hash types, so does chunker. With chunker you can choose one or another but not both. MD5 is set by default as the most supported type. Since chunker keeps hashes for composite files and falls back to the wrapped remote hash for non-chunked ones, we advise you to choose the same hash type as supported by wrapped remote so that your file listings look coherent.</p>
<p>If your storage backend does not support MD5 or SHA1 but you need consistent file hashing, configure chunker with <code>md5all</code> or <code>sha1all</code>. These two modes guarantee given hash for all files. If wrapped remote doesn't support it, chunker will then add metadata to all files, even small. However, this can double the amount of small files in storage and incur additional service charges. You can even use chunker to force md5/sha1 support in any other remote at expense of sidecar meta objects by setting e.g. <code>hash_type=sha1all</code> to force hashsums and <code>chunk_size=1P</code> to effectively disable chunking.</p>
<p>Normally, when a file is copied to chunker controlled remote, chunker will ask the file source for compatible file hash and revert to on-the-fly calculation if none is found. This involves some CPU overhead but provides a guarantee that given hashsum is available. Also, chunker will reject a server-side copy or move operation if source and destination hashsum types are different resulting in the extra network bandwidth, too. In some rare cases this may be undesired, so chunker provides two optional choices: <code>sha1quick</code> and <code>md5quick</code>. If the source does not support primary hash type and the quick mode is enabled, chunker will try to fall back to the secondary type. This will save CPU and bandwidth but can result in empty hashsums at destination. Beware of consequences: the <code>sync</code> command will revert (sometimes silently) to time/size comparison if compatible hashsums between source and target are not found.</p>
<h3 id="modification-times-3">Modification times</h3>
<p>Chunker stores modification times using the wrapped remote so support depends on that. For a small non-chunked file the chunker overlay simply manipulates modification time of the wrapped remote file. For a composite file with metadata chunker will get and set modification time of the metadata object on the wrapped remote. If file is chunked but metadata format is <code>none</code> then chunker will use modification time of the first data chunk.</p>
<h3 id="migrations">Migrations</h3>
<p>The idiomatic way to migrate to a different chunk size, hash type, transaction style or chunk naming scheme is to:</p>
<ul>
<li>Collect all your chunked files under a directory and have your chunker remote point to it.</li>
<li>Create another directory (most probably on the same cloud storage) and configure a new remote with desired metadata format, hash type, chunk naming etc.</li>
<li>Now run <code>rclone sync --interactive oldchunks: newchunks:</code> and all your data will be transparently converted in transfer. This may take some time, yet chunker will try server-side copy if possible.</li>
<li>After checking data integrity you may remove configuration section of the old remote.</li>
</ul>
<p>If rclone gets killed during a long operation on a big composite file, hidden temporary chunks may stay in the directory. They will not be shown by the <code>list</code> command but will eat up your account quota. Please note that the <code>deletefile</code> command deletes only active chunks of a file. As a workaround, you can use remote of the wrapped file system to see them. An easy way to get rid of hidden garbage is to copy littered directory somewhere using the chunker remote and purge the original directory. The <code>copy</code> command will copy only active chunks while the <code>purge</code> will remove everything including garbage.</p>
<h3 id="caveats-and-limitations">Caveats and Limitations</h3>
<p>Chunker requires wrapped remote to support server-side <code>move</code> (or <code>copy</code> + <code>delete</code>) operations, otherwise it will explicitly refuse to start. This is because it internally renames temporary chunk files to their final names when an operation completes successfully.</p>
<p>Chunker encodes chunk number in file name, so with default <code>name_format</code> setting it adds 17 characters. Also chunker adds 7 characters of temporary suffix during operations. Many file systems limit base file name without path by 255 characters. Using rclone's crypt remote as a base file system limits file name by 143 characters. Thus, maximum name length is 231 for most files and 119 for chunker-over-crypt. A user in need can change name format to e.g. <code>*.rcc##</code> and save 10 characters (provided at most 99 chunks per file).</p>
<p>Note that a move implemented using the copy-and-delete method may incur double charging with some cloud storage providers.</p>
<p>Chunker will not automatically rename existing chunks when you run <code>rclone config</code> on a live remote and change the chunk name format. Beware that in result of this some files which have been treated as chunks before the change can pop up in directory listings as normal files and vice versa. The same warning holds for the chunk size. If you desperately need to change critical chunking settings, you should run data migration as described above.</p>
<p>If wrapped remote is case insensitive, the chunker overlay will inherit that property (so you can't have a file called "Hello.doc" and "hello.doc" in the same directory).</p>
<p>Chunker included in rclone releases up to <code>v1.54</code> can sometimes fail to detect metadata produced by recent versions of rclone. We recommend users to keep rclone up-to-date to avoid data corruption.</p>
<p>Changing <code>transactions</code> is dangerous and requires explicit migration.</p>
<h3 id="standard-options-6">Standard options</h3>
<p>Here are the Standard options specific to chunker (Transparently chunk/split large files).</p>
<h4 id="chunker-remote">--chunker-remote</h4>
<p>Remote to chunk/unchunk.</p>
<p>Normally should contain a ':' and a path, e.g. "myremote:path/to/dir", "myremote:bucket" or maybe "myremote:" (not recommended).</p>
<p>Properties:</p>
<ul>
<li>Config: remote</li>
<li>Env Var: RCLONE_CHUNKER_REMOTE</li>
<li>Type: string</li>
<li>Required: true</li>
</ul>
<h4 id="chunker-chunk-size">--chunker-chunk-size</h4>
<p>Files larger than chunk size will be split in chunks.</p>
<p>Properties:</p>
<ul>
<li>Config: chunk_size</li>
<li>Env Var: RCLONE_CHUNKER_CHUNK_SIZE</li>
<li>Type: SizeSuffix</li>
<li>Default: 2Gi</li>
</ul>
<h4 id="chunker-hash-type">--chunker-hash-type</h4>
<p>Choose how chunker handles hash sums.</p>
<p>All modes but "none" require metadata.</p>
<p>Properties:</p>
<ul>
<li>Config: hash_type</li>
<li>Env Var: RCLONE_CHUNKER_HASH_TYPE</li>
<li>Type: string</li>
<li>Default: "md5"</li>
<li>Examples:
<ul>
<li>"none"
<ul>
<li>Pass any hash supported by wrapped remote for non-chunked files.</li>
<li>Return nothing otherwise.</li>
</ul></li>
<li>"md5"
<ul>
<li>MD5 for composite files.</li>
</ul></li>
<li>"sha1"
<ul>
<li>SHA1 for composite files.</li>
</ul></li>
<li>"md5all"
<ul>
<li>MD5 for all files.</li>
</ul></li>
<li>"sha1all"
<ul>
<li>SHA1 for all files.</li>
</ul></li>
<li>"md5quick"
<ul>
<li>Copying a file to chunker will request MD5 from the source.</li>
<li>Falling back to SHA1 if unsupported.</li>
</ul></li>
<li>"sha1quick"
<ul>
<li>Similar to "md5quick" but prefers SHA1 over MD5.</li>
</ul></li>
</ul></li>
</ul>
<h3 id="advanced-options-6">Advanced options</h3>
<p>Here are the Advanced options specific to chunker (Transparently chunk/split large files).</p>
<h4 id="chunker-name-format">--chunker-name-format</h4>
<p>String format of chunk file names.</p>
<p>The two placeholders are: base file name (*) and chunk number (#...). There must be one and only one asterisk and one or more consecutive hash characters. If chunk number has less digits than the number of hashes, it is left-padded by zeros. If there are more digits in the number, they are left as is. Possible chunk files are ignored if their name does not match given format.</p>
<p>Properties:</p>
<ul>
<li>Config: name_format</li>
<li>Env Var: RCLONE_CHUNKER_NAME_FORMAT</li>
<li>Type: string</li>
<li>Default: "*.rclone_chunk.###"</li>
</ul>
<h4 id="chunker-start-from">--chunker-start-from</h4>
<p>Minimum valid chunk number. Usually 0 or 1.</p>
<p>By default chunk numbers start from 1.</p>
<p>Properties:</p>
<ul>
<li>Config: start_from</li>
<li>Env Var: RCLONE_CHUNKER_START_FROM</li>
<li>Type: int</li>
<li>Default: 1</li>
</ul>
<h4 id="chunker-meta-format">--chunker-meta-format</h4>
<p>Format of the metadata object or "none".</p>
<p>By default "simplejson". Metadata is a small JSON file named after the composite file.</p>
<p>Properties:</p>
<ul>
<li>Config: meta_format</li>
<li>Env Var: RCLONE_CHUNKER_META_FORMAT</li>
<li>Type: string</li>
<li>Default: "simplejson"</li>
<li>Examples:
<ul>
<li>"none"
<ul>
<li>Do not use metadata files at all.</li>
<li>Requires hash type "none".</li>
</ul></li>
<li>"simplejson"
<ul>
<li>Simple JSON supports hash sums and chunk validation.</li>
<li></li>
<li>It has the following fields: ver, size, nchunks, md5, sha1.</li>
</ul></li>
</ul></li>
</ul>
<h4 id="chunker-fail-hard">--chunker-fail-hard</h4>
<p>Choose how chunker should handle files with missing or invalid chunks.</p>
<p>Properties:</p>
<ul>
<li>Config: fail_hard</li>
<li>Env Var: RCLONE_CHUNKER_FAIL_HARD</li>
<li>Type: bool</li>
<li>Default: false</li>
<li>Examples:
<ul>
<li>"true"
<ul>
<li>Report errors and abort current command.</li>
</ul></li>
<li>"false"
<ul>
<li>Warn user, skip incomplete file and proceed.</li>
</ul></li>
</ul></li>
</ul>
<h4 id="chunker-transactions">--chunker-transactions</h4>
<p>Choose how chunker should handle temporary files during transactions.</p>
<p>Properties:</p>
<ul>
<li>Config: transactions</li>
<li>Env Var: RCLONE_CHUNKER_TRANSACTIONS</li>
<li>Type: string</li>
<li>Default: "rename"</li>
<li>Examples:
<ul>
<li>"rename"
<ul>
<li>Rename temporary files after a successful transaction.</li>
</ul></li>
<li>"norename"
<ul>
<li>Leave temporary file names and write transaction ID to metadata file.</li>
<li>Metadata is required for no rename transactions (meta format cannot be "none").</li>
<li>If you are using norename transactions you should be careful not to downgrade Rclone</li>
<li>as older versions of Rclone don't support this transaction style and will misinterpret</li>
<li>files manipulated by norename transactions.</li>
<li>This method is EXPERIMENTAL, don't use on production systems.</li>
</ul></li>
<li>"auto"
<ul>
<li>Rename or norename will be used depending on capabilities of the backend.</li>
<li>If meta format is set to "none", rename transactions will always be used.</li>
<li>This method is EXPERIMENTAL, don't use on production systems.</li>
</ul></li>
</ul></li>
</ul>
<h4 id="chunker-description">--chunker-description</h4>
<p>Description of the remote.</p>
<p>Properties:</p>
<ul>
<li>Config: description</li>
<li>Env Var: RCLONE_CHUNKER_DESCRIPTION</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h1 id="citrix-sharefile">Citrix ShareFile</h1>
<p><a href="https://sharefile.com">Citrix ShareFile</a> is a secure file sharing and transfer service aimed as business.</p>
<h2 id="configuration-7">Configuration</h2>
<p>The initial setup for Citrix ShareFile involves getting a token from Citrix ShareFile which you can in your browser. <code>rclone config</code> walks you through it.</p>
<p>Here is an example of how to make a remote called <code>remote</code>. First run:</p>
<pre><code> rclone config</code></pre>
<p>This will guide you through an interactive setup process:</p>
<pre><code>No remotes found, make a new one?
n) New remote
s) Set configuration password
q) Quit config
n/s/q&gt; n
name&gt; remote
Type of storage to configure.
Enter a string value. Press Enter for the default (&quot;&quot;).
Choose a number from below, or type in your own value
XX / Citrix Sharefile
   \ &quot;sharefile&quot;
Storage&gt; sharefile
** See help for sharefile backend at: https://rclone.org/sharefile/ **

ID of the root folder

Leave blank to access &quot;Personal Folders&quot;.  You can use one of the
standard values here or any folder ID (long hex number ID).
Enter a string value. Press Enter for the default (&quot;&quot;).
Choose a number from below, or type in your own value
 1 / Access the Personal Folders. (Default)
   \ &quot;&quot;
 2 / Access the Favorites folder.
   \ &quot;favorites&quot;
 3 / Access all the shared folders.
   \ &quot;allshared&quot;
 4 / Access all the individual connectors.
   \ &quot;connectors&quot;
 5 / Access the home, favorites, and shared folders as well as the connectors.
   \ &quot;top&quot;
root_folder_id&gt; 
Edit advanced config? (y/n)
y) Yes
n) No
y/n&gt; n
Remote config
Use web browser to automatically authenticate rclone with remote?
 * Say Y if the machine running rclone has a web browser you can use
 * Say N if running rclone on a (remote) machine without web browser access
If not sure try Y. If Y failed, try N.
y) Yes
n) No
y/n&gt; y
If your browser doesn&#39;t open automatically go to the following link: http://127.0.0.1:53682/auth?state=XXX
Log in and authorize rclone for access
Waiting for code...
Got code
Configuration complete.
Options:
- type: sharefile
- endpoint: https://XXX.sharefile.com
- token: {&quot;access_token&quot;:&quot;XXX&quot;,&quot;token_type&quot;:&quot;bearer&quot;,&quot;refresh_token&quot;:&quot;XXX&quot;,&quot;expiry&quot;:&quot;2019-09-30T19:41:45.878561877+01:00&quot;}
Keep this &quot;remote&quot; remote?
y) Yes this is OK
e) Edit this remote
d) Delete this remote
y/e/d&gt; y</code></pre>
<p>See the <a href="https://rclone.org/remote_setup/">remote setup docs</a> for how to set it up on a machine with no Internet browser available.</p>
<p>Note that rclone runs a webserver on your local machine to collect the token as returned from Citrix ShareFile. This only runs from the moment it opens your browser to the moment you get back the verification code. This is on <code>http://127.0.0.1:53682/</code> and this it may require you to unblock it temporarily if you are running a host firewall.</p>
<p>Once configured you can then use <code>rclone</code> like this,</p>
<p>List directories in top level of your ShareFile</p>
<pre><code>rclone lsd remote:</code></pre>
<p>List all the files in your ShareFile</p>
<pre><code>rclone ls remote:</code></pre>
<p>To copy a local directory to an ShareFile directory called backup</p>
<pre><code>rclone copy /home/source remote:backup</code></pre>
<p>Paths may be as deep as required, e.g. <code>remote:directory/subdirectory</code>.</p>
<h3 id="modification-times-and-hashes-3">Modification times and hashes</h3>
<p>ShareFile allows modification times to be set on objects accurate to 1 second. These will be used to detect whether objects need syncing or not.</p>
<p>ShareFile supports MD5 type hashes, so you can use the <code>--checksum</code> flag.</p>
<h3 id="transfers-2">Transfers</h3>
<p>For files above 128 MiB rclone will use a chunked transfer. Rclone will upload up to <code>--transfers</code> chunks at the same time (shared among all the multipart uploads). Chunks are buffered in memory and are normally 64 MiB so increasing <code>--transfers</code> will increase memory use.</p>
<h3 id="restricted-filename-characters-4">Restricted filename characters</h3>
<p>In addition to the <a href="https://rclone.org/overview/#restricted-characters">default restricted characters set</a> the following characters are also replaced:</p>
<table>
<thead>
<tr class="header">
<th>Character</th>
<th style="text-align: center;">Value</th>
<th style="text-align: center;">Replacement</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td>\</td>
<td style="text-align: center;">0x5C</td>
<td style="text-align: center;">＼</td>
</tr>
<tr class="even">
<td>*</td>
<td style="text-align: center;">0x2A</td>
<td style="text-align: center;">＊</td>
</tr>
<tr class="odd">
<td>&lt;</td>
<td style="text-align: center;">0x3C</td>
<td style="text-align: center;">＜</td>
</tr>
<tr class="even">
<td>&gt;</td>
<td style="text-align: center;">0x3E</td>
<td style="text-align: center;">＞</td>
</tr>
<tr class="odd">
<td>?</td>
<td style="text-align: center;">0x3F</td>
<td style="text-align: center;">？</td>
</tr>
<tr class="even">
<td>:</td>
<td style="text-align: center;">0x3A</td>
<td style="text-align: center;">：</td>
</tr>
<tr class="odd">
<td>|</td>
<td style="text-align: center;">0x7C</td>
<td style="text-align: center;">｜</td>
</tr>
<tr class="even">
<td>"</td>
<td style="text-align: center;">0x22</td>
<td style="text-align: center;">＂</td>
</tr>
</tbody>
</table>
<p>File names can also not start or end with the following characters. These only get replaced if they are the first or last character in the name:</p>
<table>
<thead>
<tr class="header">
<th>Character</th>
<th style="text-align: center;">Value</th>
<th style="text-align: center;">Replacement</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td>SP</td>
<td style="text-align: center;">0x20</td>
<td style="text-align: center;">␠</td>
</tr>
<tr class="even">
<td>.</td>
<td style="text-align: center;">0x2E</td>
<td style="text-align: center;">．</td>
</tr>
</tbody>
</table>
<p>Invalid UTF-8 bytes will also be <a href="https://rclone.org/overview/#invalid-utf8">replaced</a>, as they can't be used in JSON strings.</p>
<h3 id="standard-options-7">Standard options</h3>
<p>Here are the Standard options specific to sharefile (Citrix Sharefile).</p>
<h4 id="sharefile-client-id">--sharefile-client-id</h4>
<p>OAuth Client Id.</p>
<p>Leave blank normally.</p>
<p>Properties:</p>
<ul>
<li>Config: client_id</li>
<li>Env Var: RCLONE_SHAREFILE_CLIENT_ID</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="sharefile-client-secret">--sharefile-client-secret</h4>
<p>OAuth Client Secret.</p>
<p>Leave blank normally.</p>
<p>Properties:</p>
<ul>
<li>Config: client_secret</li>
<li>Env Var: RCLONE_SHAREFILE_CLIENT_SECRET</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="sharefile-root-folder-id">--sharefile-root-folder-id</h4>
<p>ID of the root folder.</p>
<p>Leave blank to access "Personal Folders". You can use one of the standard values here or any folder ID (long hex number ID).</p>
<p>Properties:</p>
<ul>
<li>Config: root_folder_id</li>
<li>Env Var: RCLONE_SHAREFILE_ROOT_FOLDER_ID</li>
<li>Type: string</li>
<li>Required: false</li>
<li>Examples:
<ul>
<li>""
<ul>
<li>Access the Personal Folders (default).</li>
</ul></li>
<li>"favorites"
<ul>
<li>Access the Favorites folder.</li>
</ul></li>
<li>"allshared"
<ul>
<li>Access all the shared folders.</li>
</ul></li>
<li>"connectors"
<ul>
<li>Access all the individual connectors.</li>
</ul></li>
<li>"top"
<ul>
<li>Access the home, favorites, and shared folders as well as the connectors.</li>
</ul></li>
</ul></li>
</ul>
<h3 id="advanced-options-7">Advanced options</h3>
<p>Here are the Advanced options specific to sharefile (Citrix Sharefile).</p>
<h4 id="sharefile-token">--sharefile-token</h4>
<p>OAuth Access Token as a JSON blob.</p>
<p>Properties:</p>
<ul>
<li>Config: token</li>
<li>Env Var: RCLONE_SHAREFILE_TOKEN</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="sharefile-auth-url">--sharefile-auth-url</h4>
<p>Auth server URL.</p>
<p>Leave blank to use the provider defaults.</p>
<p>Properties:</p>
<ul>
<li>Config: auth_url</li>
<li>Env Var: RCLONE_SHAREFILE_AUTH_URL</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="sharefile-token-url">--sharefile-token-url</h4>
<p>Token server url.</p>
<p>Leave blank to use the provider defaults.</p>
<p>Properties:</p>
<ul>
<li>Config: token_url</li>
<li>Env Var: RCLONE_SHAREFILE_TOKEN_URL</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="sharefile-upload-cutoff">--sharefile-upload-cutoff</h4>
<p>Cutoff for switching to multipart upload.</p>
<p>Properties:</p>
<ul>
<li>Config: upload_cutoff</li>
<li>Env Var: RCLONE_SHAREFILE_UPLOAD_CUTOFF</li>
<li>Type: SizeSuffix</li>
<li>Default: 128Mi</li>
</ul>
<h4 id="sharefile-chunk-size">--sharefile-chunk-size</h4>
<p>Upload chunk size.</p>
<p>Must a power of 2 &gt;= 256k.</p>
<p>Making this larger will improve performance, but note that each chunk is buffered in memory one per transfer.</p>
<p>Reducing this will reduce memory usage but decrease performance.</p>
<p>Properties:</p>
<ul>
<li>Config: chunk_size</li>
<li>Env Var: RCLONE_SHAREFILE_CHUNK_SIZE</li>
<li>Type: SizeSuffix</li>
<li>Default: 64Mi</li>
</ul>
<h4 id="sharefile-endpoint">--sharefile-endpoint</h4>
<p>Endpoint for API calls.</p>
<p>This is usually auto discovered as part of the oauth process, but can be set manually to something like: https://XXX.sharefile.com</p>
<p>Properties:</p>
<ul>
<li>Config: endpoint</li>
<li>Env Var: RCLONE_SHAREFILE_ENDPOINT</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="sharefile-encoding">--sharefile-encoding</h4>
<p>The encoding for the backend.</p>
<p>See the <a href="https://rclone.org/overview/#encoding">encoding section in the overview</a> for more info.</p>
<p>Properties:</p>
<ul>
<li>Config: encoding</li>
<li>Env Var: RCLONE_SHAREFILE_ENCODING</li>
<li>Type: Encoding</li>
<li>Default: Slash,LtGt,DoubleQuote,Colon,Question,Asterisk,Pipe,BackSlash,Ctl,LeftSpace,LeftPeriod,RightSpace,RightPeriod,InvalidUtf8,Dot</li>
</ul>
<h4 id="sharefile-description">--sharefile-description</h4>
<p>Description of the remote.</p>
<p>Properties:</p>
<ul>
<li>Config: description</li>
<li>Env Var: RCLONE_SHAREFILE_DESCRIPTION</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h2 id="limitations-9">Limitations</h2>
<p>Note that ShareFile is case insensitive so you can't have a file called "Hello.doc" and one called "hello.doc".</p>
<p>ShareFile only supports filenames up to 256 characters in length.</p>
<p><code>rclone about</code> is not supported by the Citrix ShareFile backend. Backends without this capability cannot determine free space for an rclone mount or use policy <code>mfs</code> (most free space) as a member of an rclone union remote.</p>
<p>See <a href="https://rclone.org/overview/#optional-features">List of backends that do not support rclone about</a> and <a href="https://rclone.org/commands/rclone_about/">rclone about</a></p>
<h1 id="crypt">Crypt</h1>
<p>Rclone <code>crypt</code> remotes encrypt and decrypt other remotes.</p>
<p>A remote of type <code>crypt</code> does not access a <a href="https://rclone.org/overview/">storage system</a> directly, but instead wraps another remote, which in turn accesses the storage system. This is similar to how <a href="https://rclone.org/alias/">alias</a>, <a href="https://rclone.org/union/">union</a>, <a href="https://rclone.org/chunker/">chunker</a> and a few others work. It makes the usage very flexible, as you can add a layer, in this case an encryption layer, on top of any other backend, even in multiple layers. Rclone's functionality can be used as with any other remote, for example you can <a href="https://rclone.org/commands/rclone_mount/">mount</a> a crypt remote.</p>
<p>Accessing a storage system through a crypt remote realizes client-side encryption, which makes it safe to keep your data in a location you do not trust will not get compromised. When working against the <code>crypt</code> remote, rclone will automatically encrypt (before uploading) and decrypt (after downloading) on your local system as needed on the fly, leaving the data encrypted at rest in the wrapped remote. If you access the storage system using an application other than rclone, or access the wrapped remote directly using rclone, there will not be any encryption/decryption: Downloading existing content will just give you the encrypted (scrambled) format, and anything you upload will <em>not</em> become encrypted.</p>
<p>The encryption is a secret-key encryption (also called symmetric key encryption) algorithm, where a password (or pass phrase) is used to generate real encryption key. The password can be supplied by user, or you may chose to let rclone generate one. It will be stored in the configuration file, in a lightly obscured form. If you are in an environment where you are not able to keep your configuration secured, you should add <a href="https://rclone.org/docs/#configuration-encryption">configuration encryption</a> as protection. As long as you have this configuration file, you will be able to decrypt your data. Without the configuration file, as long as you remember the password (or keep it in a safe place), you can re-create the configuration and gain access to the existing data. You may also configure a corresponding remote in a different installation to access the same data. See below for guidance to <a href="#changing-password">changing password</a>.</p>
<p>Encryption uses <a href="https://en.wikipedia.org/wiki/Salt_(cryptography)">cryptographic salt</a>, to permute the encryption key so that the same string may be encrypted in different ways. When configuring the crypt remote it is optional to enter a salt, or to let rclone generate a unique salt. If omitted, rclone uses a built-in unique string. Normally in cryptography, the salt is stored together with the encrypted content, and do not have to be memorized by the user. This is not the case in rclone, because rclone does not store any additional information on the remotes. Use of custom salt is effectively a second password that must be memorized.</p>
<p><a href="#file-encryption">File content</a> encryption is performed using <a href="https://godoc.org/golang.org/x/crypto/nacl/secretbox">NaCl SecretBox</a>, based on XSalsa20 cipher and Poly1305 for integrity. <a href="#name-encryption">Names</a> (file- and directory names) are also encrypted by default, but this has some implications and is therefore possible to be turned off.</p>
<h2 id="configuration-8">Configuration</h2>
<p>Here is an example of how to make a remote called <code>secret</code>.</p>
<p>To use <code>crypt</code>, first set up the underlying remote. Follow the <code>rclone config</code> instructions for the specific backend.</p>
<p>Before configuring the crypt remote, check the underlying remote is working. In this example the underlying remote is called <code>remote</code>. We will configure a path <code>path</code> within this remote to contain the encrypted content. Anything inside <code>remote:path</code> will be encrypted and anything outside will not.</p>
<p>Configure <code>crypt</code> using <code>rclone config</code>. In this example the <code>crypt</code> remote is called <code>secret</code>, to differentiate it from the underlying <code>remote</code>.</p>
<p>When you are done you can use the crypt remote named <code>secret</code> just as you would with any other remote, e.g. <code>rclone copy D:\docs secret:\docs</code>, and rclone will encrypt and decrypt as needed on the fly. If you access the wrapped remote <code>remote:path</code> directly you will bypass the encryption, and anything you read will be in encrypted form, and anything you write will be unencrypted. To avoid issues it is best to configure a dedicated path for encrypted content, and access it exclusively through a crypt remote.</p>
<pre><code>No remotes found, make a new one?
n) New remote
s) Set configuration password
q) Quit config
n/s/q&gt; n
name&gt; secret
Type of storage to configure.
Enter a string value. Press Enter for the default (&quot;&quot;).
Choose a number from below, or type in your own value
[snip]
XX / Encrypt/Decrypt a remote
   \ &quot;crypt&quot;
[snip]
Storage&gt; crypt
** See help for crypt backend at: https://rclone.org/crypt/ **

Remote to encrypt/decrypt.
Normally should contain a &#39;:&#39; and a path, eg &quot;myremote:path/to/dir&quot;,
&quot;myremote:bucket&quot; or maybe &quot;myremote:&quot; (not recommended).
Enter a string value. Press Enter for the default (&quot;&quot;).
remote&gt; remote:path
How to encrypt the filenames.
Enter a string value. Press Enter for the default (&quot;standard&quot;).
Choose a number from below, or type in your own value.
   / Encrypt the filenames.
 1 | See the docs for the details.
   \ &quot;standard&quot;
 2 / Very simple filename obfuscation.
   \ &quot;obfuscate&quot;
   / Don&#39;t encrypt the file names.
 3 | Adds a &quot;.bin&quot; extension only.
   \ &quot;off&quot;
filename_encryption&gt;
Option to either encrypt directory names or leave them intact.

NB If filename_encryption is &quot;off&quot; then this option will do nothing.
Enter a boolean value (true or false). Press Enter for the default (&quot;true&quot;).
Choose a number from below, or type in your own value
 1 / Encrypt directory names.
   \ &quot;true&quot;
 2 / Don&#39;t encrypt directory names, leave them intact.
   \ &quot;false&quot;
directory_name_encryption&gt;
Password or pass phrase for encryption.
y) Yes type in my own password
g) Generate random password
y/g&gt; y
Enter the password:
password:
Confirm the password:
password:
Password or pass phrase for salt. Optional but recommended.
Should be different to the previous password.
y) Yes type in my own password
g) Generate random password
n) No leave this optional password blank (default)
y/g/n&gt; g
Password strength in bits.
64 is just about memorable
128 is secure
1024 is the maximum
Bits&gt; 128
Your password is: JAsJvRcgR-_veXNfy_sGmQ
Use this password? Please note that an obscured version of this
password (and not the password itself) will be stored under your
configuration file, so keep this generated password in a safe place.
y) Yes (default)
n) No
y/n&gt;
Edit advanced config? (y/n)
y) Yes
n) No (default)
y/n&gt;
Remote config
--------------------
[secret]
type = crypt
remote = remote:path
password = *** ENCRYPTED ***
password2 = *** ENCRYPTED ***
--------------------
y) Yes this is OK (default)
e) Edit this remote
d) Delete this remote
y/e/d&gt;</code></pre>
<p><strong>Important</strong> The crypt password stored in <code>rclone.conf</code> is lightly obscured. That only protects it from cursory inspection. It is not secure unless <a href="https://rclone.org/docs/#configuration-encryption">configuration encryption</a> of <code>rclone.conf</code> is specified.</p>
<p>A long passphrase is recommended, or <code>rclone config</code> can generate a random one.</p>
<p>The obscured password is created using AES-CTR with a static key. The IV (nonce) is stored verbatim at the beginning of the obscured password. This static key is shared between all versions of rclone.</p>
<p>If you reconfigure rclone with the same passwords/passphrases elsewhere it will be compatible, but the obscured version will be different due to the different salt.</p>
<p>Rclone does not encrypt</p>
<ul>
<li>file length - this can be calculated within 16 bytes</li>
<li>modification time - used for syncing</li>
</ul>
<h3 id="specifying-the-remote-1">Specifying the remote</h3>
<p>When configuring the remote to encrypt/decrypt, you may specify any string that rclone accepts as a source/destination of other commands.</p>
<p>The primary use case is to specify the path into an already configured remote (e.g. <code>remote:path/to/dir</code> or <code>remote:bucket</code>), such that data in a remote untrusted location can be stored encrypted.</p>
<p>You may also specify a local filesystem path, such as <code>/path/to/dir</code> on Linux, <code>C:\path\to\dir</code> on Windows. By creating a crypt remote pointing to such a local filesystem path, you can use rclone as a utility for pure local file encryption, for example to keep encrypted files on a removable USB drive.</p>
<p><strong>Note</strong>: A string which do not contain a <code>:</code> will by rclone be treated as a relative path in the local filesystem. For example, if you enter the name <code>remote</code> without the trailing <code>:</code>, it will be treated as a subdirectory of the current directory with name "remote".</p>
<p>If a path <code>remote:path/to/dir</code> is specified, rclone stores encrypted files in <code>path/to/dir</code> on the remote. With file name encryption, files saved to <code>secret:subdir/subfile</code> are stored in the unencrypted path <code>path/to/dir</code> but the <code>subdir/subpath</code> element is encrypted.</p>
<p>The path you specify does not have to exist, rclone will create it when needed.</p>
<p>If you intend to use the wrapped remote both directly for keeping unencrypted content, as well as through a crypt remote for encrypted content, it is recommended to point the crypt remote to a separate directory within the wrapped remote. If you use a bucket-based storage system (e.g. Swift, S3, Google Compute Storage, B2) it is generally advisable to wrap the crypt remote around a specific bucket (<code>s3:bucket</code>). If wrapping around the entire root of the storage (<code>s3:</code>), and use the optional file name encryption, rclone will encrypt the bucket name.</p>
<h3 id="changing-password">Changing password</h3>
<p>Should the password, or the configuration file containing a lightly obscured form of the password, be compromised, you need to re-encrypt your data with a new password. Since rclone uses secret-key encryption, where the encryption key is generated directly from the password kept on the client, it is not possible to change the password/key of already encrypted content. Just changing the password configured for an existing crypt remote means you will no longer able to decrypt any of the previously encrypted content. The only possibility is to re-upload everything via a crypt remote configured with your new password.</p>
<p>Depending on the size of your data, your bandwidth, storage quota etc, there are different approaches you can take: - If you have everything in a different location, for example on your local system, you could remove all of the prior encrypted files, change the password for your configured crypt remote (or delete and re-create the crypt configuration), and then re-upload everything from the alternative location. - If you have enough space on the storage system you can create a new crypt remote pointing to a separate directory on the same backend, and then use rclone to copy everything from the original crypt remote to the new, effectively decrypting everything on the fly using the old password and re-encrypting using the new password. When done, delete the original crypt remote directory and finally the rclone crypt configuration with the old password. All data will be streamed from the storage system and back, so you will get half the bandwidth and be charged twice if you have upload and download quota on the storage system.</p>
<p><strong>Note</strong>: A security problem related to the random password generator was fixed in rclone version 1.53.3 (released 2020-11-19). Passwords generated by rclone config in version 1.49.0 (released 2019-08-26) to 1.53.2 (released 2020-10-26) are not considered secure and should be changed. If you made up your own password, or used rclone version older than 1.49.0 or newer than 1.53.2 to generate it, you are <em>not</em> affected by this issue. See <a href="https://github.com/rclone/rclone/issues/4783">issue #4783</a> for more details, and a tool you can use to check if you are affected.</p>
<h3 id="example">Example</h3>
<p>Create the following file structure using "standard" file name encryption.</p>
<pre><code>plaintext/
├── file0.txt
├── file1.txt
└── subdir
    ├── file2.txt
    ├── file3.txt
    └── subsubdir
        └── file4.txt</code></pre>
<p>Copy these to the remote, and list them</p>
<pre><code>$ rclone -q copy plaintext secret:
$ rclone -q ls secret:
        7 file1.txt
        6 file0.txt
        8 subdir/file2.txt
       10 subdir/subsubdir/file4.txt
        9 subdir/file3.txt</code></pre>
<p>The crypt remote looks like</p>
<pre><code>$ rclone -q ls remote:path
       55 hagjclgavj2mbiqm6u6cnjjqcg
       54 v05749mltvv1tf4onltun46gls
       57 86vhrsv86mpbtd3a0akjuqslj8/dlj7fkq4kdq72emafg7a7s41uo
       58 86vhrsv86mpbtd3a0akjuqslj8/7uu829995du6o42n32otfhjqp4/b9pausrfansjth5ob3jkdqd4lc
       56 86vhrsv86mpbtd3a0akjuqslj8/8njh1sk437gttmep3p70g81aps</code></pre>
<p>The directory structure is preserved</p>
<pre><code>$ rclone -q ls secret:subdir
        8 file2.txt
        9 file3.txt
       10 subsubdir/file4.txt</code></pre>
<p>Without file name encryption <code>.bin</code> extensions are added to underlying names. This prevents the cloud provider attempting to interpret file content.</p>
<pre><code>$ rclone -q ls remote:path
       54 file0.txt.bin
       57 subdir/file3.txt.bin
       56 subdir/file2.txt.bin
       58 subdir/subsubdir/file4.txt.bin
       55 file1.txt.bin</code></pre>
<h3 id="file-name-encryption-modes">File name encryption modes</h3>
<p>Off</p>
<ul>
<li>doesn't hide file names or directory structure</li>
<li>allows for longer file names (~246 characters)</li>
<li>can use sub paths and copy single files</li>
</ul>
<p>Standard</p>
<ul>
<li>file names encrypted</li>
<li>file names can't be as long (~143 characters)</li>
<li>can use sub paths and copy single files</li>
<li>directory structure visible</li>
<li>identical files names will have identical uploaded names</li>
<li>can use shortcuts to shorten the directory recursion</li>
</ul>
<p>Obfuscation</p>
<p>This is a simple "rotate" of the filename, with each file having a rot distance based on the filename. Rclone stores the distance at the beginning of the filename. A file called "hello" may become "53.jgnnq".</p>
<p>Obfuscation is not a strong encryption of filenames, but hinders automated scanning tools picking up on filename patterns. It is an intermediate between "off" and "standard" which allows for longer path segment names.</p>
<p>There is a possibility with some unicode based filenames that the obfuscation is weak and may map lower case characters to upper case equivalents.</p>
<p>Obfuscation cannot be relied upon for strong protection.</p>
<ul>
<li>file names very lightly obfuscated</li>
<li>file names can be longer than standard encryption</li>
<li>can use sub paths and copy single files</li>
<li>directory structure visible</li>
<li>identical files names will have identical uploaded names</li>
</ul>
<p>Cloud storage systems have limits on file name length and total path length which rclone is more likely to breach using "Standard" file name encryption. Where file names are 143 or fewer characters in length issues should not be encountered, irrespective of cloud storage provider.</p>
<p>An experimental advanced option <code>filename_encoding</code> is now provided to address this problem to a certain degree. For cloud storage systems with case sensitive file names (e.g. Google Drive), <code>base64</code> can be used to reduce file name length. For cloud storage systems using UTF-16 to store file names internally (e.g. OneDrive, Dropbox, Box), <code>base32768</code> can be used to drastically reduce file name length.</p>
<p>An alternative, future rclone file name encryption mode may tolerate backend provider path length limits.</p>
<h3 id="directory-name-encryption">Directory name encryption</h3>
<p>Crypt offers the option of encrypting dir names or leaving them intact. There are two options:</p>
<p>True</p>
<p>Encrypts the whole file path including directory names Example: <code>1/12/123.txt</code> is encrypted to <code>p0e52nreeaj0a5ea7s64m4j72s/l42g6771hnv3an9cgc8cr2n1ng/qgm4avr35m5loi1th53ato71v0</code></p>
<p>False</p>
<p>Only encrypts file names, skips directory names Example: <code>1/12/123.txt</code> is encrypted to <code>1/12/qgm4avr35m5loi1th53ato71v0</code></p>
<h3 id="modification-times-and-hashes-4">Modification times and hashes</h3>
<p>Crypt stores modification times using the underlying remote so support depends on that.</p>
<p>Hashes are not stored for crypt. However the data integrity is protected by an extremely strong crypto authenticator.</p>
<p>Use the <code>rclone cryptcheck</code> command to check the integrity of an encrypted remote instead of <code>rclone check</code> which can't check the checksums properly.</p>
<h3 id="standard-options-8">Standard options</h3>
<p>Here are the Standard options specific to crypt (Encrypt/Decrypt a remote).</p>
<h4 id="crypt-remote">--crypt-remote</h4>
<p>Remote to encrypt/decrypt.</p>
<p>Normally should contain a ':' and a path, e.g. "myremote:path/to/dir", "myremote:bucket" or maybe "myremote:" (not recommended).</p>
<p>Properties:</p>
<ul>
<li>Config: remote</li>
<li>Env Var: RCLONE_CRYPT_REMOTE</li>
<li>Type: string</li>
<li>Required: true</li>
</ul>
<h4 id="crypt-filename-encryption">--crypt-filename-encryption</h4>
<p>How to encrypt the filenames.</p>
<p>Properties:</p>
<ul>
<li>Config: filename_encryption</li>
<li>Env Var: RCLONE_CRYPT_FILENAME_ENCRYPTION</li>
<li>Type: string</li>
<li>Default: "standard"</li>
<li>Examples:
<ul>
<li>"standard"
<ul>
<li>Encrypt the filenames.</li>
<li>See the docs for the details.</li>
</ul></li>
<li>"obfuscate"
<ul>
<li>Very simple filename obfuscation.</li>
</ul></li>
<li>"off"
<ul>
<li>Don't encrypt the file names.</li>
<li>Adds a ".bin", or "suffix" extension only.</li>
</ul></li>
</ul></li>
</ul>
<h4 id="crypt-directory-name-encryption">--crypt-directory-name-encryption</h4>
<p>Option to either encrypt directory names or leave them intact.</p>
<p>NB If filename_encryption is "off" then this option will do nothing.</p>
<p>Properties:</p>
<ul>
<li>Config: directory_name_encryption</li>
<li>Env Var: RCLONE_CRYPT_DIRECTORY_NAME_ENCRYPTION</li>
<li>Type: bool</li>
<li>Default: true</li>
<li>Examples:
<ul>
<li>"true"
<ul>
<li>Encrypt directory names.</li>
</ul></li>
<li>"false"
<ul>
<li>Don't encrypt directory names, leave them intact.</li>
</ul></li>
</ul></li>
</ul>
<h4 id="crypt-password">--crypt-password</h4>
<p>Password or pass phrase for encryption.</p>
<p><strong>NB</strong> Input to this must be obscured - see <a href="https://rclone.org/commands/rclone_obscure/">rclone obscure</a>.</p>
<p>Properties:</p>
<ul>
<li>Config: password</li>
<li>Env Var: RCLONE_CRYPT_PASSWORD</li>
<li>Type: string</li>
<li>Required: true</li>
</ul>
<h4 id="crypt-password2">--crypt-password2</h4>
<p>Password or pass phrase for salt.</p>
<p>Optional but recommended. Should be different to the previous password.</p>
<p><strong>NB</strong> Input to this must be obscured - see <a href="https://rclone.org/commands/rclone_obscure/">rclone obscure</a>.</p>
<p>Properties:</p>
<ul>
<li>Config: password2</li>
<li>Env Var: RCLONE_CRYPT_PASSWORD2</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h3 id="advanced-options-8">Advanced options</h3>
<p>Here are the Advanced options specific to crypt (Encrypt/Decrypt a remote).</p>
<h4 id="crypt-server-side-across-configs">--crypt-server-side-across-configs</h4>
<p>Deprecated: use --server-side-across-configs instead.</p>
<p>Allow server-side operations (e.g. copy) to work across different crypt configs.</p>
<p>Normally this option is not what you want, but if you have two crypts pointing to the same backend you can use it.</p>
<p>This can be used, for example, to change file name encryption type without re-uploading all the data. Just make two crypt backends pointing to two different directories with the single changed parameter and use rclone move to move the files between the crypt remotes.</p>
<p>Properties:</p>
<ul>
<li>Config: server_side_across_configs</li>
<li>Env Var: RCLONE_CRYPT_SERVER_SIDE_ACROSS_CONFIGS</li>
<li>Type: bool</li>
<li>Default: false</li>
</ul>
<h4 id="crypt-show-mapping">--crypt-show-mapping</h4>
<p>For all files listed show how the names encrypt.</p>
<p>If this flag is set then for each file that the remote is asked to list, it will log (at level INFO) a line stating the decrypted file name and the encrypted file name.</p>
<p>This is so you can work out which encrypted names are which decrypted names just in case you need to do something with the encrypted file names, or for debugging purposes.</p>
<p>Properties:</p>
<ul>
<li>Config: show_mapping</li>
<li>Env Var: RCLONE_CRYPT_SHOW_MAPPING</li>
<li>Type: bool</li>
<li>Default: false</li>
</ul>
<h4 id="crypt-no-data-encryption">--crypt-no-data-encryption</h4>
<p>Option to either encrypt file data or leave it unencrypted.</p>
<p>Properties:</p>
<ul>
<li>Config: no_data_encryption</li>
<li>Env Var: RCLONE_CRYPT_NO_DATA_ENCRYPTION</li>
<li>Type: bool</li>
<li>Default: false</li>
<li>Examples:
<ul>
<li>"true"
<ul>
<li>Don't encrypt file data, leave it unencrypted.</li>
</ul></li>
<li>"false"
<ul>
<li>Encrypt file data.</li>
</ul></li>
</ul></li>
</ul>
<h4 id="crypt-pass-bad-blocks">--crypt-pass-bad-blocks</h4>
<p>If set this will pass bad blocks through as all 0.</p>
<p>This should not be set in normal operation, it should only be set if trying to recover an encrypted file with errors and it is desired to recover as much of the file as possible.</p>
<p>Properties:</p>
<ul>
<li>Config: pass_bad_blocks</li>
<li>Env Var: RCLONE_CRYPT_PASS_BAD_BLOCKS</li>
<li>Type: bool</li>
<li>Default: false</li>
</ul>
<h4 id="crypt-strict-names">--crypt-strict-names</h4>
<p>If set, this will raise an error when crypt comes across a filename that can't be decrypted.</p>
<p>(By default, rclone will just log a NOTICE and continue as normal.) This can happen if encrypted and unencrypted files are stored in the same directory (which is not recommended.) It may also indicate a more serious problem that should be investigated.</p>
<p>Properties:</p>
<ul>
<li>Config: strict_names</li>
<li>Env Var: RCLONE_CRYPT_STRICT_NAMES</li>
<li>Type: bool</li>
<li>Default: false</li>
</ul>
<h4 id="crypt-filename-encoding">--crypt-filename-encoding</h4>
<p>How to encode the encrypted filename to text string.</p>
<p>This option could help with shortening the encrypted filename. The suitable option would depend on the way your remote count the filename length and if it's case sensitive.</p>
<p>Properties:</p>
<ul>
<li>Config: filename_encoding</li>
<li>Env Var: RCLONE_CRYPT_FILENAME_ENCODING</li>
<li>Type: string</li>
<li>Default: "base32"</li>
<li>Examples:
<ul>
<li>"base32"
<ul>
<li>Encode using base32. Suitable for all remote.</li>
</ul></li>
<li>"base64"
<ul>
<li>Encode using base64. Suitable for case sensitive remote.</li>
</ul></li>
<li>"base32768"
<ul>
<li>Encode using base32768. Suitable if your remote counts UTF-16 or</li>
<li>Unicode codepoint instead of UTF-8 byte length. (Eg. Onedrive, Dropbox)</li>
</ul></li>
</ul></li>
</ul>
<h4 id="crypt-suffix">--crypt-suffix</h4>
<p>If this is set it will override the default suffix of ".bin".</p>
<p>Setting suffix to "none" will result in an empty suffix. This may be useful when the path length is critical.</p>
<p>Properties:</p>
<ul>
<li>Config: suffix</li>
<li>Env Var: RCLONE_CRYPT_SUFFIX</li>
<li>Type: string</li>
<li>Default: ".bin"</li>
</ul>
<h4 id="crypt-description">--crypt-description</h4>
<p>Description of the remote.</p>
<p>Properties:</p>
<ul>
<li>Config: description</li>
<li>Env Var: RCLONE_CRYPT_DESCRIPTION</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h3 id="metadata-5">Metadata</h3>
<p>Any metadata supported by the underlying remote is read and written.</p>
<p>See the <a href="https://rclone.org/docs/#metadata">metadata</a> docs for more info.</p>
<h2 id="backend-commands-3">Backend commands</h2>
<p>Here are the commands specific to the crypt backend.</p>
<p>Run them with</p>
<pre><code>rclone backend COMMAND remote:</code></pre>
<p>The help below will explain what arguments each command takes.</p>
<p>See the <a href="https://rclone.org/commands/rclone_backend/">backend</a> command for more info on how to pass options and arguments.</p>
<p>These can be run on a running backend using the rc command <a href="https://rclone.org/rc/#backend-command">backend/command</a>.</p>
<h3 id="encode">encode</h3>
<p>Encode the given filename(s)</p>
<pre><code>rclone backend encode remote: [options] [&lt;arguments&gt;+]</code></pre>
<p>This encodes the filenames given as arguments returning a list of strings of the encoded results.</p>
<p>Usage Example:</p>
<pre><code>rclone backend encode crypt: file1 [file2...]
rclone rc backend/command command=encode fs=crypt: file1 [file2...]</code></pre>
<h3 id="decode">decode</h3>
<p>Decode the given filename(s)</p>
<pre><code>rclone backend decode remote: [options] [&lt;arguments&gt;+]</code></pre>
<p>This decodes the filenames given as arguments returning a list of strings of the decoded results. It will return an error if any of the inputs are invalid.</p>
<p>Usage Example:</p>
<pre><code>rclone backend decode crypt: encryptedfile1 [encryptedfile2...]
rclone rc backend/command command=decode fs=crypt: encryptedfile1 [encryptedfile2...]</code></pre>
<h2 id="backing-up-an-encrypted-remote">Backing up an encrypted remote</h2>
<p>If you wish to backup an encrypted remote, it is recommended that you use <code>rclone sync</code> on the encrypted files, and make sure the passwords are the same in the new encrypted remote.</p>
<p>This will have the following advantages</p>
<ul>
<li><code>rclone sync</code> will check the checksums while copying</li>
<li>you can use <code>rclone check</code> between the encrypted remotes</li>
<li>you don't decrypt and encrypt unnecessarily</li>
</ul>
<p>For example, let's say you have your original remote at <code>remote:</code> with the encrypted version at <code>eremote:</code> with path <code>remote:crypt</code>. You would then set up the new remote <code>remote2:</code> and then the encrypted version <code>eremote2:</code> with path <code>remote2:crypt</code> using the same passwords as <code>eremote:</code>.</p>
<p>To sync the two remotes you would do</p>
<pre><code>rclone sync --interactive remote:crypt remote2:crypt</code></pre>
<p>And to check the integrity you would do</p>
<pre><code>rclone check remote:crypt remote2:crypt</code></pre>
<h2 id="file-formats">File formats</h2>
<h3 id="file-encryption">File encryption</h3>
<p>Files are encrypted 1:1 source file to destination object. The file has a header and is divided into chunks.</p>
<h4 id="header-1">Header</h4>
<ul>
<li>8 bytes magic string <code>RCLONE\x00\x00</code></li>
<li>24 bytes Nonce (IV)</li>
</ul>
<p>The initial nonce is generated from the operating systems crypto strong random number generator. The nonce is incremented for each chunk read making sure each nonce is unique for each block written. The chance of a nonce being reused is minuscule. If you wrote an exabyte of data (10¹⁸ bytes) you would have a probability of approximately 2×10⁻³² of re-using a nonce.</p>
<h4 id="chunk">Chunk</h4>
<p>Each chunk will contain 64 KiB of data, except for the last one which may have less data. The data chunk is in standard NaCl SecretBox format. SecretBox uses XSalsa20 and Poly1305 to encrypt and authenticate messages.</p>
<p>Each chunk contains:</p>
<ul>
<li>16 Bytes of Poly1305 authenticator</li>
<li>1 - 65536 bytes XSalsa20 encrypted data</li>
</ul>
<p>64k chunk size was chosen as the best performing chunk size (the authenticator takes too much time below this and the performance drops off due to cache effects above this). Note that these chunks are buffered in memory so they can't be too big.</p>
<p>This uses a 32 byte (256 bit key) key derived from the user password.</p>
<h4 id="examples-1">Examples</h4>
<p>1 byte file will encrypt to</p>
<ul>
<li>32 bytes header</li>
<li>17 bytes data chunk</li>
</ul>
<p>49 bytes total</p>
<p>1 MiB (1048576 bytes) file will encrypt to</p>
<ul>
<li>32 bytes header</li>
<li>16 chunks of 65568 bytes</li>
</ul>
<p>1049120 bytes total (a 0.05% overhead). This is the overhead for big files.</p>
<h3 id="name-encryption">Name encryption</h3>
<p>File names are encrypted segment by segment - the path is broken up into <code>/</code> separated strings and these are encrypted individually.</p>
<p>File segments are padded using PKCS#7 to a multiple of 16 bytes before encryption.</p>
<p>They are then encrypted with EME using AES with 256 bit key. EME (ECB-Mix-ECB) is a wide-block encryption mode presented in the 2003 paper "A Parallelizable Enciphering Mode" by Halevi and Rogaway.</p>
<p>This makes for deterministic encryption which is what we want - the same filename must encrypt to the same thing otherwise we can't find it on the cloud storage system.</p>
<p>This means that</p>
<ul>
<li>filenames with the same name will encrypt the same</li>
<li>filenames which start the same won't have a common prefix</li>
</ul>
<p>This uses a 32 byte key (256 bits) and a 16 byte (128 bits) IV both of which are derived from the user password.</p>
<p>After encryption they are written out using a modified version of standard <code>base32</code> encoding as described in RFC4648. The standard encoding is modified in two ways:</p>
<ul>
<li>it becomes lower case (no-one likes upper case filenames!)</li>
<li>we strip the padding character <code>=</code></li>
</ul>
<p><code>base32</code> is used rather than the more efficient <code>base64</code> so rclone can be used on case insensitive remotes (e.g. Windows, Box, Dropbox, Onedrive etc).</p>
<h3 id="key-derivation">Key derivation</h3>
<p>Rclone uses <code>scrypt</code> with parameters <code>N=16384, r=8, p=1</code> with an optional user supplied salt (password2) to derive the 32+32+16 = 80 bytes of key material required. If the user doesn't supply a salt then rclone uses an internal one.</p>
<p><code>scrypt</code> makes it impractical to mount a dictionary attack on rclone encrypted data. For full protection against this you should always use a salt.</p>
<h2 id="see-also-90">SEE ALSO</h2>
<ul>
<li><a href="https://rclone.org/commands/rclone_cryptdecode/">rclone cryptdecode</a> - Show forward/reverse mapping of encrypted filenames</li>
</ul>
<h1 id="compress">Compress</h1>
<h2 id="warning">Warning</h2>
<p>This remote is currently <strong>experimental</strong>. Things may break and data may be lost. Anything you do with this remote is at your own risk. Please understand the risks associated with using experimental code and don't use this remote in critical applications.</p>
<p>The <code>Compress</code> remote adds compression to another remote. It is best used with remotes containing many large compressible files.</p>
<h2 id="configuration-9">Configuration</h2>
<p>To use this remote, all you need to do is specify another remote and a compression mode to use:</p>
<pre><code>Current remotes:

Name                 Type
====                 ====
remote_to_press      sometype

e) Edit existing remote
$ rclone config
n) New remote
d) Delete remote
r) Rename remote
c) Copy remote
s) Set configuration password
q) Quit config
e/n/d/r/c/s/q&gt; n
name&gt; compress
...
 8 / Compress a remote
   \ &quot;compress&quot;
...
Storage&gt; compress
** See help for compress backend at: https://rclone.org/compress/ **

Remote to compress.
Enter a string value. Press Enter for the default (&quot;&quot;).
remote&gt; remote_to_press:subdir 
Compression mode.
Enter a string value. Press Enter for the default (&quot;gzip&quot;).
Choose a number from below, or type in your own value
 1 / Gzip compression balanced for speed and compression strength.
   \ &quot;gzip&quot;
compression_mode&gt; gzip
Edit advanced config? (y/n)
y) Yes
n) No (default)
y/n&gt; n
Remote config
--------------------
[compress]
type = compress
remote = remote_to_press:subdir
compression_mode = gzip
--------------------
y) Yes this is OK (default)
e) Edit this remote
d) Delete this remote
y/e/d&gt; y</code></pre>
<h3 id="compression-modes">Compression Modes</h3>
<p>Currently only gzip compression is supported. It provides a decent balance between speed and size and is well supported by other applications. Compression strength can further be configured via an advanced setting where 0 is no compression and 9 is strongest compression.</p>
<h3 id="file-types">File types</h3>
<p>If you open a remote wrapped by compress, you will see that there are many files with an extension corresponding to the compression algorithm you chose. These files are standard files that can be opened by various archive programs, but they have some hidden metadata that allows them to be used by rclone. While you may download and decompress these files at will, do <strong>not</strong> manually delete or rename files. Files without correct metadata files will not be recognized by rclone.</p>
<h3 id="file-names">File names</h3>
<p>The compressed files will be named <code>*.###########.gz</code> where <code>*</code> is the base file and the <code>#</code> part is base64 encoded size of the uncompressed file. The file names should not be changed by anything other than the rclone compression backend.</p>
<h3 id="standard-options-9">Standard options</h3>
<p>Here are the Standard options specific to compress (Compress a remote).</p>
<h4 id="compress-remote">--compress-remote</h4>
<p>Remote to compress.</p>
<p>Properties:</p>
<ul>
<li>Config: remote</li>
<li>Env Var: RCLONE_COMPRESS_REMOTE</li>
<li>Type: string</li>
<li>Required: true</li>
</ul>
<h4 id="compress-mode">--compress-mode</h4>
<p>Compression mode.</p>
<p>Properties:</p>
<ul>
<li>Config: mode</li>
<li>Env Var: RCLONE_COMPRESS_MODE</li>
<li>Type: string</li>
<li>Default: "gzip"</li>
<li>Examples:
<ul>
<li>"gzip"
<ul>
<li>Standard gzip compression with fastest parameters.</li>
</ul></li>
</ul></li>
</ul>
<h3 id="advanced-options-9">Advanced options</h3>
<p>Here are the Advanced options specific to compress (Compress a remote).</p>
<h4 id="compress-level">--compress-level</h4>
<p>GZIP compression level (-2 to 9).</p>
<p>Generally -1 (default, equivalent to 5) is recommended. Levels 1 to 9 increase compression at the cost of speed. Going past 6 generally offers very little return.</p>
<p>Level -2 uses Huffman encoding only. Only use if you know what you are doing. Level 0 turns off compression.</p>
<p>Properties:</p>
<ul>
<li>Config: level</li>
<li>Env Var: RCLONE_COMPRESS_LEVEL</li>
<li>Type: int</li>
<li>Default: -1</li>
</ul>
<h4 id="compress-ram-cache-limit">--compress-ram-cache-limit</h4>
<p>Some remotes don't allow the upload of files with unknown size. In this case the compressed file will need to be cached to determine it's size.</p>
<p>Files smaller than this limit will be cached in RAM, files larger than this limit will be cached on disk.</p>
<p>Properties:</p>
<ul>
<li>Config: ram_cache_limit</li>
<li>Env Var: RCLONE_COMPRESS_RAM_CACHE_LIMIT</li>
<li>Type: SizeSuffix</li>
<li>Default: 20Mi</li>
</ul>
<h4 id="compress-description">--compress-description</h4>
<p>Description of the remote.</p>
<p>Properties:</p>
<ul>
<li>Config: description</li>
<li>Env Var: RCLONE_COMPRESS_DESCRIPTION</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h3 id="metadata-6">Metadata</h3>
<p>Any metadata supported by the underlying remote is read and written.</p>
<p>See the <a href="https://rclone.org/docs/#metadata">metadata</a> docs for more info.</p>
<h1 id="combine">Combine</h1>
<p>The <code>combine</code> backend joins remotes together into a single directory tree.</p>
<p>For example you might have a remote for images on one provider:</p>
<pre><code>$ rclone tree s3:imagesbucket
/
├── image1.jpg
└── image2.jpg</code></pre>
<p>And a remote for files on another:</p>
<pre><code>$ rclone tree drive:important/files
/
├── file1.txt
└── file2.txt</code></pre>
<p>The <code>combine</code> backend can join these together into a synthetic directory structure like this:</p>
<pre><code>$ rclone tree combined:
/
├── files
│   ├── file1.txt
│   └── file2.txt
└── images
    ├── image1.jpg
    └── image2.jpg</code></pre>
<p>You'd do this by specifying an <code>upstreams</code> parameter in the config like this</p>
<pre><code>upstreams = images=s3:imagesbucket files=drive:important/files</code></pre>
<p>During the initial setup with <code>rclone config</code> you will specify the upstreams remotes as a space separated list. The upstream remotes can either be a local paths or other remotes.</p>
<h2 id="configuration-10">Configuration</h2>
<p>Here is an example of how to make a combine called <code>remote</code> for the example above. First run:</p>
<pre><code> rclone config</code></pre>
<p>This will guide you through an interactive setup process:</p>
<pre><code>No remotes found, make a new one?
n) New remote
s) Set configuration password
q) Quit config
n/s/q&gt; n
name&gt; remote
Option Storage.
Type of storage to configure.
Choose a number from below, or type in your own value.
...
XX / Combine several remotes into one
   \ (combine)
...
Storage&gt; combine
Option upstreams.
Upstreams for combining
These should be in the form
    dir=remote:path dir2=remote2:path
Where before the = is specified the root directory and after is the remote to
put there.
Embedded spaces can be added using quotes
    &quot;dir=remote:path with space&quot; &quot;dir2=remote2:path with space&quot;
Enter a fs.SpaceSepList value.
upstreams&gt; images=s3:imagesbucket files=drive:important/files
Configuration complete.
Options:
- type: combine
- upstreams: images=s3:imagesbucket files=drive:important/files
Keep this &quot;remote&quot; remote?
y) Yes this is OK (default)
e) Edit this remote
d) Delete this remote
y/e/d&gt; y</code></pre>
<h3 id="configuring-for-google-drive-shared-drives">Configuring for Google Drive Shared Drives</h3>
<p>Rclone has a convenience feature for making a combine backend for all the shared drives you have access to.</p>
<p>Assuming your main (non shared drive) Google drive remote is called <code>drive:</code> you would run</p>
<pre><code>rclone backend -o config drives drive:</code></pre>
<p>This would produce something like this:</p>
<pre><code>[My Drive]
type = alias
remote = drive,team_drive=0ABCDEF-01234567890,root_folder_id=:

[Test Drive]
type = alias
remote = drive,team_drive=0ABCDEFabcdefghijkl,root_folder_id=:

[AllDrives]
type = combine
upstreams = &quot;My Drive=My Drive:&quot; &quot;Test Drive=Test Drive:&quot;</code></pre>
<p>If you then add that config to your config file (find it with <code>rclone config file</code>) then you can access all the shared drives in one place with the <code>AllDrives:</code> remote.</p>
<p>See <a href="https://rclone.org/drive/#drives">the Google Drive docs</a> for full info.</p>
<h3 id="standard-options-10">Standard options</h3>
<p>Here are the Standard options specific to combine (Combine several remotes into one).</p>
<h4 id="combine-upstreams">--combine-upstreams</h4>
<p>Upstreams for combining</p>
<p>These should be in the form</p>
<pre><code>dir=remote:path dir2=remote2:path</code></pre>
<p>Where before the = is specified the root directory and after is the remote to put there.</p>
<p>Embedded spaces can be added using quotes</p>
<pre><code>&quot;dir=remote:path with space&quot; &quot;dir2=remote2:path with space&quot;</code></pre>
<p>Properties:</p>
<ul>
<li>Config: upstreams</li>
<li>Env Var: RCLONE_COMBINE_UPSTREAMS</li>
<li>Type: SpaceSepList</li>
<li>Default:</li>
</ul>
<h3 id="advanced-options-10">Advanced options</h3>
<p>Here are the Advanced options specific to combine (Combine several remotes into one).</p>
<h4 id="combine-description">--combine-description</h4>
<p>Description of the remote.</p>
<p>Properties:</p>
<ul>
<li>Config: description</li>
<li>Env Var: RCLONE_COMBINE_DESCRIPTION</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h3 id="metadata-7">Metadata</h3>
<p>Any metadata supported by the underlying remote is read and written.</p>
<p>See the <a href="https://rclone.org/docs/#metadata">metadata</a> docs for more info.</p>
<h1 id="dropbox">Dropbox</h1>
<p>Paths are specified as <code>remote:path</code></p>
<p>Dropbox paths may be as deep as required, e.g. <code>remote:directory/subdirectory</code>.</p>
<h2 id="configuration-11">Configuration</h2>
<p>The initial setup for dropbox involves getting a token from Dropbox which you need to do in your browser. <code>rclone config</code> walks you through it.</p>
<p>Here is an example of how to make a remote called <code>remote</code>. First run:</p>
<pre><code> rclone config</code></pre>
<p>This will guide you through an interactive setup process:</p>
<pre><code>n) New remote
d) Delete remote
q) Quit config
e/n/d/q&gt; n
name&gt; remote
Type of storage to configure.
Choose a number from below, or type in your own value
[snip]
XX / Dropbox
   \ &quot;dropbox&quot;
[snip]
Storage&gt; dropbox
Dropbox App Key - leave blank normally.
app_key&gt;
Dropbox App Secret - leave blank normally.
app_secret&gt;
Remote config
Please visit:
https://www.dropbox.com/1/oauth2/authorize?client_id=XXXXXXXXXXXXXXX&amp;response_type=code
Enter the code: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX_XXXXXXXXXX
Configuration complete.
Options:
- type: dropbox
- app_key:
- app_secret:
- token: XXXXXXXXXXXXXXXXXXXXXXXXXXXXX_XXXX_XXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Keep this &quot;remote&quot; remote?
y) Yes this is OK
e) Edit this remote
d) Delete this remote
y/e/d&gt; y</code></pre>
<p>See the <a href="https://rclone.org/remote_setup/">remote setup docs</a> for how to set it up on a machine with no Internet browser available.</p>
<p>Note that rclone runs a webserver on your local machine to collect the token as returned from Dropbox. This only runs from the moment it opens your browser to the moment you get back the verification code. This is on <code>http://127.0.0.1:53682/</code> and it may require you to unblock it temporarily if you are running a host firewall, or use manual mode.</p>
<p>You can then use it like this,</p>
<p>List directories in top level of your dropbox</p>
<pre><code>rclone lsd remote:</code></pre>
<p>List all the files in your dropbox</p>
<pre><code>rclone ls remote:</code></pre>
<p>To copy a local directory to a dropbox directory called backup</p>
<pre><code>rclone copy /home/source remote:backup</code></pre>
<h3 id="dropbox-for-business">Dropbox for business</h3>
<p>Rclone supports Dropbox for business and Team Folders.</p>
<p>When using Dropbox for business <code>remote:</code> and <code>remote:path/to/file</code> will refer to your personal folder.</p>
<p>If you wish to see Team Folders you must use a leading <code>/</code> in the path, so <code>rclone lsd remote:/</code> will refer to the root and show you all Team Folders and your User Folder.</p>
<p>You can then use team folders like this <code>remote:/TeamFolder</code> and <code>remote:/TeamFolder/path/to/file</code>.</p>
<p>A leading <code>/</code> for a Dropbox personal account will do nothing, but it will take an extra HTTP transaction so it should be avoided.</p>
<h3 id="modification-times-and-hashes-5">Modification times and hashes</h3>
<p>Dropbox supports modified times, but the only way to set a modification time is to re-upload the file.</p>
<p>This means that if you uploaded your data with an older version of rclone which didn't support the v2 API and modified times, rclone will decide to upload all your old data to fix the modification times. If you don't want this to happen use <code>--size-only</code> or <code>--checksum</code> flag to stop it.</p>
<p>Dropbox supports <a href="https://www.dropbox.com/developers/reference/content-hash">its own hash type</a> which is checked for all transfers.</p>
<h3 id="restricted-filename-characters-5">Restricted filename characters</h3>
<table>
<thead>
<tr class="header">
<th>Character</th>
<th style="text-align: center;">Value</th>
<th style="text-align: center;">Replacement</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td>NUL</td>
<td style="text-align: center;">0x00</td>
<td style="text-align: center;">␀</td>
</tr>
<tr class="even">
<td>/</td>
<td style="text-align: center;">0x2F</td>
<td style="text-align: center;">／</td>
</tr>
<tr class="odd">
<td>DEL</td>
<td style="text-align: center;">0x7F</td>
<td style="text-align: center;">␡</td>
</tr>
<tr class="even">
<td>\</td>
<td style="text-align: center;">0x5C</td>
<td style="text-align: center;">＼</td>
</tr>
</tbody>
</table>
<p>File names can also not end with the following characters. These only get replaced if they are the last character in the name:</p>
<table>
<thead>
<tr class="header">
<th>Character</th>
<th style="text-align: center;">Value</th>
<th style="text-align: center;">Replacement</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td>SP</td>
<td style="text-align: center;">0x20</td>
<td style="text-align: center;">␠</td>
</tr>
</tbody>
</table>
<p>Invalid UTF-8 bytes will also be <a href="https://rclone.org/overview/#invalid-utf8">replaced</a>, as they can't be used in JSON strings.</p>
<h3 id="batch-mode">Batch mode uploads</h3>
<p>Using batch mode uploads is very important for performance when using the Dropbox API. See <a href="https://developers.dropbox.com/dbx-performance-guide">the dropbox performance guide</a> for more info.</p>
<p>There are 3 modes rclone can use for uploads.</p>
<h4 id="dropbox-batch-mode-off">--dropbox-batch-mode off</h4>
<p>In this mode rclone will not use upload batching. This was the default before rclone v1.55. It has the disadvantage that it is very likely to encounter <code>too_many_requests</code> errors like this</p>
<pre><code>NOTICE: too_many_requests/.: Too many requests or write operations. Trying again in 15 seconds.</code></pre>
<p>When rclone receives these it has to wait for 15s or sometimes 300s before continuing which really slows down transfers.</p>
<p>This will happen especially if <code>--transfers</code> is large, so this mode isn't recommended except for compatibility or investigating problems.</p>
<h4 id="dropbox-batch-mode-sync">--dropbox-batch-mode sync</h4>
<p>In this mode rclone will batch up uploads to the size specified by <code>--dropbox-batch-size</code> and commit them together.</p>
<p>Using this mode means you can use a much higher <code>--transfers</code> parameter (32 or 64 works fine) without receiving <code>too_many_requests</code> errors.</p>
<p>This mode ensures full data integrity.</p>
<p>Note that there may be a pause when quitting rclone while rclone finishes up the last batch using this mode.</p>
<h4 id="dropbox-batch-mode-async">--dropbox-batch-mode async</h4>
<p>In this mode rclone will batch up uploads to the size specified by <code>--dropbox-batch-size</code> and commit them together.</p>
<p>However it will not wait for the status of the batch to be returned to the caller. This means rclone can use a much bigger batch size (much bigger than <code>--transfers</code>), at the cost of not being able to check the status of the upload.</p>
<p>This provides the maximum possible upload speed especially with lots of small files, however rclone can't check the file got uploaded properly using this mode.</p>
<p>If you are using this mode then using "rclone check" after the transfer completes is recommended. Or you could do an initial transfer with <code>--dropbox-batch-mode async</code> then do a final transfer with <code>--dropbox-batch-mode sync</code> (the default).</p>
<p>Note that there may be a pause when quitting rclone while rclone finishes up the last batch using this mode.</p>
<h3 id="standard-options-11">Standard options</h3>
<p>Here are the Standard options specific to dropbox (Dropbox).</p>
<h4 id="dropbox-client-id">--dropbox-client-id</h4>
<p>OAuth Client Id.</p>
<p>Leave blank normally.</p>
<p>Properties:</p>
<ul>
<li>Config: client_id</li>
<li>Env Var: RCLONE_DROPBOX_CLIENT_ID</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="dropbox-client-secret">--dropbox-client-secret</h4>
<p>OAuth Client Secret.</p>
<p>Leave blank normally.</p>
<p>Properties:</p>
<ul>
<li>Config: client_secret</li>
<li>Env Var: RCLONE_DROPBOX_CLIENT_SECRET</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h3 id="advanced-options-11">Advanced options</h3>
<p>Here are the Advanced options specific to dropbox (Dropbox).</p>
<h4 id="dropbox-token">--dropbox-token</h4>
<p>OAuth Access Token as a JSON blob.</p>
<p>Properties:</p>
<ul>
<li>Config: token</li>
<li>Env Var: RCLONE_DROPBOX_TOKEN</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="dropbox-auth-url">--dropbox-auth-url</h4>
<p>Auth server URL.</p>
<p>Leave blank to use the provider defaults.</p>
<p>Properties:</p>
<ul>
<li>Config: auth_url</li>
<li>Env Var: RCLONE_DROPBOX_AUTH_URL</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="dropbox-token-url">--dropbox-token-url</h4>
<p>Token server url.</p>
<p>Leave blank to use the provider defaults.</p>
<p>Properties:</p>
<ul>
<li>Config: token_url</li>
<li>Env Var: RCLONE_DROPBOX_TOKEN_URL</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="dropbox-chunk-size">--dropbox-chunk-size</h4>
<p>Upload chunk size (&lt; 150Mi).</p>
<p>Any files larger than this will be uploaded in chunks of this size.</p>
<p>Note that chunks are buffered in memory (one at a time) so rclone can deal with retries. Setting this larger will increase the speed slightly (at most 10% for 128 MiB in tests) at the cost of using more memory. It can be set smaller if you are tight on memory.</p>
<p>Properties:</p>
<ul>
<li>Config: chunk_size</li>
<li>Env Var: RCLONE_DROPBOX_CHUNK_SIZE</li>
<li>Type: SizeSuffix</li>
<li>Default: 48Mi</li>
</ul>
<h4 id="dropbox-impersonate">--dropbox-impersonate</h4>
<p>Impersonate this user when using a business account.</p>
<p>Note that if you want to use impersonate, you should make sure this flag is set when running "rclone config" as this will cause rclone to request the "members.read" scope which it won't normally. This is needed to lookup a members email address into the internal ID that dropbox uses in the API.</p>
<p>Using the "members.read" scope will require a Dropbox Team Admin to approve during the OAuth flow.</p>
<p>You will have to use your own App (setting your own client_id and client_secret) to use this option as currently rclone's default set of permissions doesn't include "members.read". This can be added once v1.55 or later is in use everywhere.</p>
<p>Properties:</p>
<ul>
<li>Config: impersonate</li>
<li>Env Var: RCLONE_DROPBOX_IMPERSONATE</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="dropbox-shared-files">--dropbox-shared-files</h4>
<p>Instructs rclone to work on individual shared files.</p>
<p>In this mode rclone's features are extremely limited - only list (ls, lsl, etc.) operations and read operations (e.g. downloading) are supported in this mode. All other operations will be disabled.</p>
<p>Properties:</p>
<ul>
<li>Config: shared_files</li>
<li>Env Var: RCLONE_DROPBOX_SHARED_FILES</li>
<li>Type: bool</li>
<li>Default: false</li>
</ul>
<h4 id="dropbox-shared-folders">--dropbox-shared-folders</h4>
<p>Instructs rclone to work on shared folders.</p>
<p>When this flag is used with no path only the List operation is supported and all available shared folders will be listed. If you specify a path the first part will be interpreted as the name of shared folder. Rclone will then try to mount this shared to the root namespace. On success shared folder rclone proceeds normally. The shared folder is now pretty much a normal folder and all normal operations are supported.</p>
<p>Note that we don't unmount the shared folder afterwards so the --dropbox-shared-folders can be omitted after the first use of a particular shared folder.</p>
<p>See also --dropbox-root-namespace for an alternative way to work with shared folders.</p>
<p>Properties:</p>
<ul>
<li>Config: shared_folders</li>
<li>Env Var: RCLONE_DROPBOX_SHARED_FOLDERS</li>
<li>Type: bool</li>
<li>Default: false</li>
</ul>
<h4 id="dropbox-pacer-min-sleep">--dropbox-pacer-min-sleep</h4>
<p>Minimum time to sleep between API calls.</p>
<p>Properties:</p>
<ul>
<li>Config: pacer_min_sleep</li>
<li>Env Var: RCLONE_DROPBOX_PACER_MIN_SLEEP</li>
<li>Type: Duration</li>
<li>Default: 10ms</li>
</ul>
<h4 id="dropbox-encoding">--dropbox-encoding</h4>
<p>The encoding for the backend.</p>
<p>See the <a href="https://rclone.org/overview/#encoding">encoding section in the overview</a> for more info.</p>
<p>Properties:</p>
<ul>
<li>Config: encoding</li>
<li>Env Var: RCLONE_DROPBOX_ENCODING</li>
<li>Type: Encoding</li>
<li>Default: Slash,BackSlash,Del,RightSpace,InvalidUtf8,Dot</li>
</ul>
<h4 id="dropbox-root-namespace">--dropbox-root-namespace</h4>
<p>Specify a different Dropbox namespace ID to use as the root for all paths.</p>
<p>Properties:</p>
<ul>
<li>Config: root_namespace</li>
<li>Env Var: RCLONE_DROPBOX_ROOT_NAMESPACE</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="dropbox-batch-mode">--dropbox-batch-mode</h4>
<p>Upload file batching sync|async|off.</p>
<p>This sets the batch mode used by rclone.</p>
<p>For full info see <a href="https://rclone.org/dropbox/#batch-mode">the main docs</a></p>
<p>This has 3 possible values</p>
<ul>
<li>off - no batching</li>
<li>sync - batch uploads and check completion (default)</li>
<li>async - batch upload and don't check completion</li>
</ul>
<p>Rclone will close any outstanding batches when it exits which may make a delay on quit.</p>
<p>Properties:</p>
<ul>
<li>Config: batch_mode</li>
<li>Env Var: RCLONE_DROPBOX_BATCH_MODE</li>
<li>Type: string</li>
<li>Default: "sync"</li>
</ul>
<h4 id="dropbox-batch-size">--dropbox-batch-size</h4>
<p>Max number of files in upload batch.</p>
<p>This sets the batch size of files to upload. It has to be less than 1000.</p>
<p>By default this is 0 which means rclone will calculate the batch size depending on the setting of batch_mode.</p>
<ul>
<li>batch_mode: async - default batch_size is 100</li>
<li>batch_mode: sync - default batch_size is the same as --transfers</li>
<li>batch_mode: off - not in use</li>
</ul>
<p>Rclone will close any outstanding batches when it exits which may make a delay on quit.</p>
<p>Setting this is a great idea if you are uploading lots of small files as it will make them a lot quicker. You can use --transfers 32 to maximise throughput.</p>
<p>Properties:</p>
<ul>
<li>Config: batch_size</li>
<li>Env Var: RCLONE_DROPBOX_BATCH_SIZE</li>
<li>Type: int</li>
<li>Default: 0</li>
</ul>
<h4 id="dropbox-batch-timeout">--dropbox-batch-timeout</h4>
<p>Max time to allow an idle upload batch before uploading.</p>
<p>If an upload batch is idle for more than this long then it will be uploaded.</p>
<p>The default for this is 0 which means rclone will choose a sensible default based on the batch_mode in use.</p>
<ul>
<li>batch_mode: async - default batch_timeout is 10s</li>
<li>batch_mode: sync - default batch_timeout is 500ms</li>
<li>batch_mode: off - not in use</li>
</ul>
<p>Properties:</p>
<ul>
<li>Config: batch_timeout</li>
<li>Env Var: RCLONE_DROPBOX_BATCH_TIMEOUT</li>
<li>Type: Duration</li>
<li>Default: 0s</li>
</ul>
<h4 id="dropbox-batch-commit-timeout">--dropbox-batch-commit-timeout</h4>
<p>Max time to wait for a batch to finish committing</p>
<p>Properties:</p>
<ul>
<li>Config: batch_commit_timeout</li>
<li>Env Var: RCLONE_DROPBOX_BATCH_COMMIT_TIMEOUT</li>
<li>Type: Duration</li>
<li>Default: 10m0s</li>
</ul>
<h4 id="dropbox-description">--dropbox-description</h4>
<p>Description of the remote.</p>
<p>Properties:</p>
<ul>
<li>Config: description</li>
<li>Env Var: RCLONE_DROPBOX_DESCRIPTION</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h2 id="limitations-10">Limitations</h2>
<p>Note that Dropbox is case insensitive so you can't have a file called "Hello.doc" and one called "hello.doc".</p>
<p>There are some file names such as <code>thumbs.db</code> which Dropbox can't store. There is a full list of them in the <a href="https://www.dropbox.com/en/help/145">"Ignored Files" section of this document</a>. Rclone will issue an error message <code>File name disallowed - not uploading</code> if it attempts to upload one of those file names, but the sync won't fail.</p>
<p>Some errors may occur if you try to sync copyright-protected files because Dropbox has its own <a href="https://techcrunch.com/2014/03/30/how-dropbox-knows-when-youre-sharing-copyrighted-stuff-without-actually-looking-at-your-stuff/">copyright detector</a> that prevents this sort of file being downloaded. This will return the error <code>ERROR : /path/to/your/file: Failed to copy: failed to open source object: path/restricted_content/.</code></p>
<p>If you have more than 10,000 files in a directory then <code>rclone purge dropbox:dir</code> will return the error <code>Failed to purge: There are too many files involved in this operation</code>. As a work-around do an <code>rclone delete dropbox:dir</code> followed by an <code>rclone rmdir dropbox:dir</code>.</p>
<p>When using <code>rclone link</code> you'll need to set <code>--expire</code> if using a non-personal account otherwise the visibility may not be correct. (Note that <code>--expire</code> isn't supported on personal accounts). See the <a href="https://forum.rclone.org/t/rclone-link-dropbox-permissions/23211">forum discussion</a> and the <a href="https://github.com/dropbox/dropbox-sdk-go-unofficial/issues/75">dropbox SDK issue</a>.</p>
<h2 id="get-your-own-dropbox-app-id">Get your own Dropbox App ID</h2>
<p>When you use rclone with Dropbox in its default configuration you are using rclone's App ID. This is shared between all the rclone users.</p>
<p>Here is how to create your own Dropbox App ID for rclone:</p>
<ol type="1">
<li><p>Log into the <a href="https://www.dropbox.com/developers/apps/create">Dropbox App console</a> with your Dropbox Account (It need not to be the same account as the Dropbox you want to access)</p></li>
<li><p>Choose an API =&gt; Usually this should be <code>Dropbox API</code></p></li>
<li><p>Choose the type of access you want to use =&gt; <code>Full Dropbox</code> or <code>App Folder</code>. If you want to use Team Folders, <code>Full Dropbox</code> is required (<a href="https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/How-to-create-team-folder-inside-my-app-s-folder/m-p/601005/highlight/true#M27911">see here</a>).</p></li>
<li><p>Name your App. The app name is global, so you can't use <code>rclone</code> for example</p></li>
<li><p>Click the button <code>Create App</code></p></li>
<li><p>Switch to the <code>Permissions</code> tab. Enable at least the following permissions: <code>account_info.read</code>, <code>files.metadata.write</code>, <code>files.content.write</code>, <code>files.content.read</code>, <code>sharing.write</code>. The <code>files.metadata.read</code> and <code>sharing.read</code> checkboxes will be marked too. Click <code>Submit</code></p></li>
<li><p>Switch to the <code>Settings</code> tab. Fill <code>OAuth2 - Redirect URIs</code> as <code>http://localhost:53682/</code> and click on <code>Add</code></p></li>
<li><p>Find the <code>App key</code> and <code>App secret</code> values on the <code>Settings</code> tab. Use these values in rclone config to add a new remote or edit an existing remote. The <code>App key</code> setting corresponds to <code>client_id</code> in rclone config, the <code>App secret</code> corresponds to <code>client_secret</code></p></li>
</ol>
<h1 id="enterprise-file-fabric">Enterprise File Fabric</h1>
<p>This backend supports <a href="https://storagemadeeasy.com/about/">Storage Made Easy's Enterprise File Fabric™</a> which provides a software solution to integrate and unify File and Object Storage accessible through a global file system.</p>
<h2 id="configuration-12">Configuration</h2>
<p>The initial setup for the Enterprise File Fabric backend involves getting a token from the Enterprise File Fabric which you need to do in your browser. <code>rclone config</code> walks you through it.</p>
<p>Here is an example of how to make a remote called <code>remote</code>. First run:</p>
<pre><code> rclone config</code></pre>
<p>This will guide you through an interactive setup process:</p>
<pre><code>No remotes found, make a new one?
n) New remote
s) Set configuration password
q) Quit config
n/s/q&gt; n
name&gt; remote
Type of storage to configure.
Enter a string value. Press Enter for the default (&quot;&quot;).
Choose a number from below, or type in your own value
[snip]
XX / Enterprise File Fabric
   \ &quot;filefabric&quot;
[snip]
Storage&gt; filefabric
** See help for filefabric backend at: https://rclone.org/filefabric/ **

URL of the Enterprise File Fabric to connect to
Enter a string value. Press Enter for the default (&quot;&quot;).
Choose a number from below, or type in your own value
 1 / Storage Made Easy US
   \ &quot;https://storagemadeeasy.com&quot;
 2 / Storage Made Easy EU
   \ &quot;https://eu.storagemadeeasy.com&quot;
 3 / Connect to your Enterprise File Fabric
   \ &quot;https://yourfabric.smestorage.com&quot;
url&gt; https://yourfabric.smestorage.com/
ID of the root folder
Leave blank normally.

Fill in to make rclone start with directory of a given ID.

Enter a string value. Press Enter for the default (&quot;&quot;).
root_folder_id&gt; 
Permanent Authentication Token

A Permanent Authentication Token can be created in the Enterprise File
Fabric, on the users Dashboard under Security, there is an entry
you&#39;ll see called &quot;My Authentication Tokens&quot;. Click the Manage button
to create one.

These tokens are normally valid for several years.

For more info see: https://docs.storagemadeeasy.com/organisationcloud/api-tokens

Enter a string value. Press Enter for the default (&quot;&quot;).
permanent_token&gt; xxxxxxxxxxxxxxx-xxxxxxxxxxxxxxxx
Edit advanced config? (y/n)
y) Yes
n) No (default)
y/n&gt; n
Remote config
Configuration complete.
Options:
- type: filefabric
- url: https://yourfabric.smestorage.com/
- permanent_token: xxxxxxxxxxxxxxx-xxxxxxxxxxxxxxxx
Keep this &quot;remote&quot; remote?
y) Yes this is OK (default)
e) Edit this remote
d) Delete this remote
y/e/d&gt; y</code></pre>
<p>Once configured you can then use <code>rclone</code> like this,</p>
<p>List directories in top level of your Enterprise File Fabric</p>
<pre><code>rclone lsd remote:</code></pre>
<p>List all the files in your Enterprise File Fabric</p>
<pre><code>rclone ls remote:</code></pre>
<p>To copy a local directory to an Enterprise File Fabric directory called backup</p>
<pre><code>rclone copy /home/source remote:backup</code></pre>
<h3 id="modification-times-and-hashes-6">Modification times and hashes</h3>
<p>The Enterprise File Fabric allows modification times to be set on files accurate to 1 second. These will be used to detect whether objects need syncing or not.</p>
<p>The Enterprise File Fabric does not support any data hashes at this time.</p>
<h3 id="restricted-filename-characters-6">Restricted filename characters</h3>
<p>The <a href="https://rclone.org/overview/#restricted-characters">default restricted characters set</a> will be replaced.</p>
<p>Invalid UTF-8 bytes will also be <a href="https://rclone.org/overview/#invalid-utf8">replaced</a>, as they can't be used in JSON strings.</p>
<h3 id="empty-files">Empty files</h3>
<p>Empty files aren't supported by the Enterprise File Fabric. Rclone will therefore upload an empty file as a single space with a mime type of <code>application/vnd.rclone.empty.file</code> and files with that mime type are treated as empty.</p>
<h3 id="root-folder-id-1">Root folder ID</h3>
<p>You can set the <code>root_folder_id</code> for rclone. This is the directory (identified by its <code>Folder ID</code>) that rclone considers to be the root of your Enterprise File Fabric.</p>
<p>Normally you will leave this blank and rclone will determine the correct root to use itself.</p>
<p>However you can set this to restrict rclone to a specific folder hierarchy.</p>
<p>In order to do this you will have to find the <code>Folder ID</code> of the directory you wish rclone to display. These aren't displayed in the web interface, but you can use <code>rclone lsf</code> to find them, for example</p>
<pre><code>$ rclone lsf --dirs-only -Fip --csv filefabric:
120673758,Burnt PDFs/
120673759,My Quick Uploads/
120673755,My Syncs/
120673756,My backups/
120673757,My contacts/
120673761,S3 Storage/</code></pre>
<p>The ID for "S3 Storage" would be <code>120673761</code>.</p>
<h3 id="standard-options-12">Standard options</h3>
<p>Here are the Standard options specific to filefabric (Enterprise File Fabric).</p>
<h4 id="filefabric-url">--filefabric-url</h4>
<p>URL of the Enterprise File Fabric to connect to.</p>
<p>Properties:</p>
<ul>
<li>Config: url</li>
<li>Env Var: RCLONE_FILEFABRIC_URL</li>
<li>Type: string</li>
<li>Required: true</li>
<li>Examples:
<ul>
<li>"https://storagemadeeasy.com"
<ul>
<li>Storage Made Easy US</li>
</ul></li>
<li>"https://eu.storagemadeeasy.com"
<ul>
<li>Storage Made Easy EU</li>
</ul></li>
<li>"https://yourfabric.smestorage.com"
<ul>
<li>Connect to your Enterprise File Fabric</li>
</ul></li>
</ul></li>
</ul>
<h4 id="filefabric-root-folder-id">--filefabric-root-folder-id</h4>
<p>ID of the root folder.</p>
<p>Leave blank normally.</p>
<p>Fill in to make rclone start with directory of a given ID.</p>
<p>Properties:</p>
<ul>
<li>Config: root_folder_id</li>
<li>Env Var: RCLONE_FILEFABRIC_ROOT_FOLDER_ID</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="filefabric-permanent-token">--filefabric-permanent-token</h4>
<p>Permanent Authentication Token.</p>
<p>A Permanent Authentication Token can be created in the Enterprise File Fabric, on the users Dashboard under Security, there is an entry you'll see called "My Authentication Tokens". Click the Manage button to create one.</p>
<p>These tokens are normally valid for several years.</p>
<p>For more info see: https://docs.storagemadeeasy.com/organisationcloud/api-tokens</p>
<p>Properties:</p>
<ul>
<li>Config: permanent_token</li>
<li>Env Var: RCLONE_FILEFABRIC_PERMANENT_TOKEN</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h3 id="advanced-options-12">Advanced options</h3>
<p>Here are the Advanced options specific to filefabric (Enterprise File Fabric).</p>
<h4 id="filefabric-token">--filefabric-token</h4>
<p>Session Token.</p>
<p>This is a session token which rclone caches in the config file. It is usually valid for 1 hour.</p>
<p>Don't set this value - rclone will set it automatically.</p>
<p>Properties:</p>
<ul>
<li>Config: token</li>
<li>Env Var: RCLONE_FILEFABRIC_TOKEN</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="filefabric-token-expiry">--filefabric-token-expiry</h4>
<p>Token expiry time.</p>
<p>Don't set this value - rclone will set it automatically.</p>
<p>Properties:</p>
<ul>
<li>Config: token_expiry</li>
<li>Env Var: RCLONE_FILEFABRIC_TOKEN_EXPIRY</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="filefabric-version">--filefabric-version</h4>
<p>Version read from the file fabric.</p>
<p>Don't set this value - rclone will set it automatically.</p>
<p>Properties:</p>
<ul>
<li>Config: version</li>
<li>Env Var: RCLONE_FILEFABRIC_VERSION</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="filefabric-encoding">--filefabric-encoding</h4>
<p>The encoding for the backend.</p>
<p>See the <a href="https://rclone.org/overview/#encoding">encoding section in the overview</a> for more info.</p>
<p>Properties:</p>
<ul>
<li>Config: encoding</li>
<li>Env Var: RCLONE_FILEFABRIC_ENCODING</li>
<li>Type: Encoding</li>
<li>Default: Slash,Del,Ctl,InvalidUtf8,Dot</li>
</ul>
<h4 id="filefabric-description">--filefabric-description</h4>
<p>Description of the remote.</p>
<p>Properties:</p>
<ul>
<li>Config: description</li>
<li>Env Var: RCLONE_FILEFABRIC_DESCRIPTION</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h1 id="files.com">Files.com</h1>
<p><a href="https://www.files.com/">Files.com</a> is a cloud storage service that provides a secure and easy way to store and share files.</p>
<p>The initial setup for filescom involves authenticating with your Files.com account. You can do this by providing your site subdomain, username, and password. Alternatively, you can authenticate using an API Key from <a href="https://www.files.com/docs/sdk-and-apis/api-keys/">Files.com</a>. <code>rclone config</code> walks you through it.</p>
<h2 id="configuration-13">Configuration</h2>
<p>Here is an example of how to make a remote called <code>remote</code>. First run:</p>
<pre><code>rclone config</code></pre>
<p>This will guide you through an interactive setup process:</p>
<pre><code>No remotes found, make a new one?
n) New remote
s) Set configuration password
q) Quit config
n/s/q&gt; n

Enter name for new remote.
name&gt; remote

Option Storage.
Type of storage to configure.
Choose a number from below, or type in your own value.
[snip]
XX / Files.com
  \ &quot;filescom&quot;
[snip]
Storage&gt; filescom

Option site.
Your site subdomain (e.g. mysite) or custom domain (e.g. myfiles.customdomain.com)
Enter a value. Press Enter to leave empty.
site&gt; mysite

Option username.
The username used to authenticate with Files.com.
Enter a value. Press Enter to leave empty.
username&gt; user

Option password.
The password used to authenticate with Files.com.
Choose an alternative below. Press Enter for the default (n).
y) Yes, type in my own password
g) Generate random password
n) No, leave this optional password blank (default)
y/g/n&gt; y
Enter the password:
password:
Confirm the password:
password:

Edit advanced config?
y) Yes
n) No (default)
y/n&gt; n

Configuration complete.
Options:
- type: filescom
- site: mysite
- username: user
- password: *** ENCRYPTED ***
Keep this &quot;remote&quot; remote?
y) Yes this is OK (default)
e) Edit this remote
d) Delete this remote
y/e/d&gt; y</code></pre>
<p>Once configured you can use rclone.</p>
<p>See all files in the top level:</p>
<pre><code>rclone lsf remote:</code></pre>
<p>Make a new directory in the root:</p>
<pre><code>rclone mkdir remote:dir</code></pre>
<p>Recursively List the contents:</p>
<pre><code>rclone ls remote:</code></pre>
<p>Sync <code>/home/local/directory</code> to the remote directory, deleting any excess files in the directory.</p>
<pre><code>rclone sync --interactive /home/local/directory remote:dir</code></pre>
<h3 id="standard-options-13">Standard options</h3>
<p>Here are the Standard options specific to filescom (Files.com).</p>
<h4 id="filescom-site">--filescom-site</h4>
<p>Your site subdomain (e.g. mysite) or custom domain (e.g. myfiles.customdomain.com).</p>
<p>Properties:</p>
<ul>
<li>Config: site</li>
<li>Env Var: RCLONE_FILESCOM_SITE</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="filescom-username">--filescom-username</h4>
<p>The username used to authenticate with Files.com.</p>
<p>Properties:</p>
<ul>
<li>Config: username</li>
<li>Env Var: RCLONE_FILESCOM_USERNAME</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="filescom-password">--filescom-password</h4>
<p>The password used to authenticate with Files.com.</p>
<p><strong>NB</strong> Input to this must be obscured - see <a href="https://rclone.org/commands/rclone_obscure/">rclone obscure</a>.</p>
<p>Properties:</p>
<ul>
<li>Config: password</li>
<li>Env Var: RCLONE_FILESCOM_PASSWORD</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h3 id="advanced-options-13">Advanced options</h3>
<p>Here are the Advanced options specific to filescom (Files.com).</p>
<h4 id="filescom-api-key">--filescom-api-key</h4>
<p>The API key used to authenticate with Files.com.</p>
<p>Properties:</p>
<ul>
<li>Config: api_key</li>
<li>Env Var: RCLONE_FILESCOM_API_KEY</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="filescom-encoding">--filescom-encoding</h4>
<p>The encoding for the backend.</p>
<p>See the <a href="https://rclone.org/overview/#encoding">encoding section in the overview</a> for more info.</p>
<p>Properties:</p>
<ul>
<li>Config: encoding</li>
<li>Env Var: RCLONE_FILESCOM_ENCODING</li>
<li>Type: Encoding</li>
<li>Default: Slash,BackSlash,Del,Ctl,RightSpace,RightCrLfHtVt,InvalidUtf8,Dot</li>
</ul>
<h4 id="filescom-description">--filescom-description</h4>
<p>Description of the remote.</p>
<p>Properties:</p>
<ul>
<li>Config: description</li>
<li>Env Var: RCLONE_FILESCOM_DESCRIPTION</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h1 id="ftp">FTP</h1>
<p>FTP is the File Transfer Protocol. Rclone FTP support is provided using the <a href="https://godoc.org/github.com/jlaffaye/ftp">github.com/jlaffaye/ftp</a> package.</p>
<p><a href="#limitations">Limitations of Rclone's FTP backend</a></p>
<p>Paths are specified as <code>remote:path</code>. If the path does not begin with a <code>/</code> it is relative to the home directory of the user. An empty path <code>remote:</code> refers to the user's home directory.</p>
<h2 id="configuration-14">Configuration</h2>
<p>To create an FTP configuration named <code>remote</code>, run</p>
<pre><code>rclone config</code></pre>
<p>Rclone config guides you through an interactive setup process. A minimal rclone FTP remote definition only requires host, username and password. For an anonymous FTP server, see <a href="#anonymous-ftp">below</a>.</p>
<pre><code>No remotes found, make a new one?
n) New remote
r) Rename remote
c) Copy remote
s) Set configuration password
q) Quit config
n/r/c/s/q&gt; n
name&gt; remote
Type of storage to configure.
Enter a string value. Press Enter for the default (&quot;&quot;).
Choose a number from below, or type in your own value
[snip]
XX / FTP
   \ &quot;ftp&quot;
[snip]
Storage&gt; ftp
** See help for ftp backend at: https://rclone.org/ftp/ **

FTP host to connect to
Enter a string value. Press Enter for the default (&quot;&quot;).
Choose a number from below, or type in your own value
 1 / Connect to ftp.example.com
   \ &quot;ftp.example.com&quot;
host&gt; ftp.example.com
FTP username
Enter a string value. Press Enter for the default (&quot;$USER&quot;).
user&gt; 
FTP port number
Enter a signed integer. Press Enter for the default (21).
port&gt; 
FTP password
y) Yes type in my own password
g) Generate random password
y/g&gt; y
Enter the password:
password:
Confirm the password:
password:
Use FTP over TLS (Implicit)
Enter a boolean value (true or false). Press Enter for the default (&quot;false&quot;).
tls&gt; 
Use FTP over TLS (Explicit)
Enter a boolean value (true or false). Press Enter for the default (&quot;false&quot;).
explicit_tls&gt; 
Remote config
Configuration complete.
Options:
- type: ftp
- host: ftp.example.com
- pass: *** ENCRYPTED ***
Keep this &quot;remote&quot; remote?
y) Yes this is OK
e) Edit this remote
d) Delete this remote
y/e/d&gt; y</code></pre>
<p>To see all directories in the home directory of <code>remote</code></p>
<pre><code>rclone lsd remote:</code></pre>
<p>Make a new directory</p>
<pre><code>rclone mkdir remote:path/to/directory</code></pre>
<p>List the contents of a directory</p>
<pre><code>rclone ls remote:path/to/directory</code></pre>
<p>Sync <code>/home/local/directory</code> to the remote directory, deleting any excess files in the directory.</p>
<pre><code>rclone sync --interactive /home/local/directory remote:directory</code></pre>
<h3 id="anonymous-ftp">Anonymous FTP</h3>
<p>When connecting to a FTP server that allows anonymous login, you can use the special "anonymous" username. Traditionally, this user account accepts any string as a password, although it is common to use either the password "anonymous" or "guest". Some servers require the use of a valid e-mail address as password.</p>
<p>Using <a href="#backend-path-to-dir">on-the-fly</a> or <a href="https://rclone.org/docs/#connection-strings">connection string</a> remotes makes it easy to access such servers, without requiring any configuration in advance. The following are examples of that:</p>
<pre><code>rclone lsf :ftp: --ftp-host=speedtest.tele2.net --ftp-user=anonymous --ftp-pass=$(rclone obscure dummy)
rclone lsf :ftp,host=speedtest.tele2.net,user=anonymous,pass=$(rclone obscure dummy):</code></pre>
<p>The above examples work in Linux shells and in PowerShell, but not Windows Command Prompt. They execute the <a href="https://rclone.org/commands/rclone_obscure/">rclone obscure</a> command to create a password string in the format required by the <a href="#ftp-pass">pass</a> option. The following examples are exactly the same, except use an already obscured string representation of the same password "dummy", and therefore works even in Windows Command Prompt:</p>
<pre><code>rclone lsf :ftp: --ftp-host=speedtest.tele2.net --ftp-user=anonymous --ftp-pass=IXs2wc8OJOz7SYLBk47Ji1rHTmxM
rclone lsf :ftp,host=speedtest.tele2.net,user=anonymous,pass=IXs2wc8OJOz7SYLBk47Ji1rHTmxM:</code></pre>
<h3 id="implicit-tls">Implicit TLS</h3>
<p>Rlone FTP supports implicit FTP over TLS servers (FTPS). This has to be enabled in the FTP backend config for the remote, or with <a href="#ftp-tls"><code>--ftp-tls</code></a>. The default FTPS port is <code>990</code>, not <code>21</code> and can be set with <a href="#ftp-port"><code>--ftp-port</code></a>.</p>
<h3 id="restricted-filename-characters-7">Restricted filename characters</h3>
<p>In addition to the <a href="https://rclone.org/overview/#restricted-characters">default restricted characters set</a> the following characters are also replaced:</p>
<p>File names cannot end with the following characters. Replacement is limited to the last character in a file name:</p>
<table>
<thead>
<tr class="header">
<th>Character</th>
<th style="text-align: center;">Value</th>
<th style="text-align: center;">Replacement</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td>SP</td>
<td style="text-align: center;">0x20</td>
<td style="text-align: center;">␠</td>
</tr>
</tbody>
</table>
<p>Not all FTP servers can have all characters in file names, for example:</p>
<table>
<thead>
<tr class="header">
<th>FTP Server</th>
<th style="text-align: center;">Forbidden characters</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td>proftpd</td>
<td style="text-align: center;"><code>*</code></td>
</tr>
<tr class="even">
<td>pureftpd</td>
<td style="text-align: center;"><code>\ [ ]</code></td>
</tr>
</tbody>
</table>
<p>This backend's interactive configuration wizard provides a selection of sensible encoding settings for major FTP servers: ProFTPd, PureFTPd, VsFTPd. Just hit a selection number when prompted.</p>
<h3 id="standard-options-14">Standard options</h3>
<p>Here are the Standard options specific to ftp (FTP).</p>
<h4 id="ftp-host">--ftp-host</h4>
<p>FTP host to connect to.</p>
<p>E.g. "ftp.example.com".</p>
<p>Properties:</p>
<ul>
<li>Config: host</li>
<li>Env Var: RCLONE_FTP_HOST</li>
<li>Type: string</li>
<li>Required: true</li>
</ul>
<h4 id="ftp-user">--ftp-user</h4>
<p>FTP username.</p>
<p>Properties:</p>
<ul>
<li>Config: user</li>
<li>Env Var: RCLONE_FTP_USER</li>
<li>Type: string</li>
<li>Default: "$USER"</li>
</ul>
<h4 id="ftp-port">--ftp-port</h4>
<p>FTP port number.</p>
<p>Properties:</p>
<ul>
<li>Config: port</li>
<li>Env Var: RCLONE_FTP_PORT</li>
<li>Type: int</li>
<li>Default: 21</li>
</ul>
<h4 id="ftp-pass">--ftp-pass</h4>
<p>FTP password.</p>
<p><strong>NB</strong> Input to this must be obscured - see <a href="https://rclone.org/commands/rclone_obscure/">rclone obscure</a>.</p>
<p>Properties:</p>
<ul>
<li>Config: pass</li>
<li>Env Var: RCLONE_FTP_PASS</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="ftp-tls">--ftp-tls</h4>
<p>Use Implicit FTPS (FTP over TLS).</p>
<p>When using implicit FTP over TLS the client connects using TLS right from the start which breaks compatibility with non-TLS-aware servers. This is usually served over port 990 rather than port 21. Cannot be used in combination with explicit FTPS.</p>
<p>Properties:</p>
<ul>
<li>Config: tls</li>
<li>Env Var: RCLONE_FTP_TLS</li>
<li>Type: bool</li>
<li>Default: false</li>
</ul>
<h4 id="ftp-explicit-tls">--ftp-explicit-tls</h4>
<p>Use Explicit FTPS (FTP over TLS).</p>
<p>When using explicit FTP over TLS the client explicitly requests security from the server in order to upgrade a plain text connection to an encrypted one. Cannot be used in combination with implicit FTPS.</p>
<p>Properties:</p>
<ul>
<li>Config: explicit_tls</li>
<li>Env Var: RCLONE_FTP_EXPLICIT_TLS</li>
<li>Type: bool</li>
<li>Default: false</li>
</ul>
<h3 id="advanced-options-14">Advanced options</h3>
<p>Here are the Advanced options specific to ftp (FTP).</p>
<h4 id="ftp-concurrency">--ftp-concurrency</h4>
<p>Maximum number of FTP simultaneous connections, 0 for unlimited.</p>
<p>Note that setting this is very likely to cause deadlocks so it should be used with care.</p>
<p>If you are doing a sync or copy then make sure concurrency is one more than the sum of <code>--transfers</code> and <code>--checkers</code>.</p>
<p>If you use <code>--check-first</code> then it just needs to be one more than the maximum of <code>--checkers</code> and <code>--transfers</code>.</p>
<p>So for <code>concurrency 3</code> you'd use <code>--checkers 2 --transfers 2 --check-first</code> or <code>--checkers 1 --transfers 1</code>.</p>
<p>Properties:</p>
<ul>
<li>Config: concurrency</li>
<li>Env Var: RCLONE_FTP_CONCURRENCY</li>
<li>Type: int</li>
<li>Default: 0</li>
</ul>
<h4 id="ftp-no-check-certificate">--ftp-no-check-certificate</h4>
<p>Do not verify the TLS certificate of the server.</p>
<p>Properties:</p>
<ul>
<li>Config: no_check_certificate</li>
<li>Env Var: RCLONE_FTP_NO_CHECK_CERTIFICATE</li>
<li>Type: bool</li>
<li>Default: false</li>
</ul>
<h4 id="ftp-disable-epsv">--ftp-disable-epsv</h4>
<p>Disable using EPSV even if server advertises support.</p>
<p>Properties:</p>
<ul>
<li>Config: disable_epsv</li>
<li>Env Var: RCLONE_FTP_DISABLE_EPSV</li>
<li>Type: bool</li>
<li>Default: false</li>
</ul>
<h4 id="ftp-disable-mlsd">--ftp-disable-mlsd</h4>
<p>Disable using MLSD even if server advertises support.</p>
<p>Properties:</p>
<ul>
<li>Config: disable_mlsd</li>
<li>Env Var: RCLONE_FTP_DISABLE_MLSD</li>
<li>Type: bool</li>
<li>Default: false</li>
</ul>
<h4 id="ftp-disable-utf8">--ftp-disable-utf8</h4>
<p>Disable using UTF-8 even if server advertises support.</p>
<p>Properties:</p>
<ul>
<li>Config: disable_utf8</li>
<li>Env Var: RCLONE_FTP_DISABLE_UTF8</li>
<li>Type: bool</li>
<li>Default: false</li>
</ul>
<h4 id="ftp-writing-mdtm">--ftp-writing-mdtm</h4>
<p>Use MDTM to set modification time (VsFtpd quirk)</p>
<p>Properties:</p>
<ul>
<li>Config: writing_mdtm</li>
<li>Env Var: RCLONE_FTP_WRITING_MDTM</li>
<li>Type: bool</li>
<li>Default: false</li>
</ul>
<h4 id="ftp-force-list-hidden">--ftp-force-list-hidden</h4>
<p>Use LIST -a to force listing of hidden files and folders. This will disable the use of MLSD.</p>
<p>Properties:</p>
<ul>
<li>Config: force_list_hidden</li>
<li>Env Var: RCLONE_FTP_FORCE_LIST_HIDDEN</li>
<li>Type: bool</li>
<li>Default: false</li>
</ul>
<h4 id="ftp-idle-timeout">--ftp-idle-timeout</h4>
<p>Max time before closing idle connections.</p>
<p>If no connections have been returned to the connection pool in the time given, rclone will empty the connection pool.</p>
<p>Set to 0 to keep connections indefinitely.</p>
<p>Properties:</p>
<ul>
<li>Config: idle_timeout</li>
<li>Env Var: RCLONE_FTP_IDLE_TIMEOUT</li>
<li>Type: Duration</li>
<li>Default: 1m0s</li>
</ul>
<h4 id="ftp-close-timeout">--ftp-close-timeout</h4>
<p>Maximum time to wait for a response to close.</p>
<p>Properties:</p>
<ul>
<li>Config: close_timeout</li>
<li>Env Var: RCLONE_FTP_CLOSE_TIMEOUT</li>
<li>Type: Duration</li>
<li>Default: 1m0s</li>
</ul>
<h4 id="ftp-tls-cache-size">--ftp-tls-cache-size</h4>
<p>Size of TLS session cache for all control and data connections.</p>
<p>TLS cache allows to resume TLS sessions and reuse PSK between connections. Increase if default size is not enough resulting in TLS resumption errors. Enabled by default. Use 0 to disable.</p>
<p>Properties:</p>
<ul>
<li>Config: tls_cache_size</li>
<li>Env Var: RCLONE_FTP_TLS_CACHE_SIZE</li>
<li>Type: int</li>
<li>Default: 32</li>
</ul>
<h4 id="ftp-disable-tls13">--ftp-disable-tls13</h4>
<p>Disable TLS 1.3 (workaround for FTP servers with buggy TLS)</p>
<p>Properties:</p>
<ul>
<li>Config: disable_tls13</li>
<li>Env Var: RCLONE_FTP_DISABLE_TLS13</li>
<li>Type: bool</li>
<li>Default: false</li>
</ul>
<h4 id="ftp-shut-timeout">--ftp-shut-timeout</h4>
<p>Maximum time to wait for data connection closing status.</p>
<p>Properties:</p>
<ul>
<li>Config: shut_timeout</li>
<li>Env Var: RCLONE_FTP_SHUT_TIMEOUT</li>
<li>Type: Duration</li>
<li>Default: 1m0s</li>
</ul>
<h4 id="ftp-ask-password">--ftp-ask-password</h4>
<p>Allow asking for FTP password when needed.</p>
<p>If this is set and no password is supplied then rclone will ask for a password</p>
<p>Properties:</p>
<ul>
<li>Config: ask_password</li>
<li>Env Var: RCLONE_FTP_ASK_PASSWORD</li>
<li>Type: bool</li>
<li>Default: false</li>
</ul>
<h4 id="ftp-socks-proxy">--ftp-socks-proxy</h4>
<p>Socks 5 proxy host.</p>
<pre><code>    Supports the format user:pass@host:port, user@host:port, host:port.
    
    Example:
    
        myUser:myPass@localhost:9005
    </code></pre>
<p>Properties:</p>
<ul>
<li>Config: socks_proxy</li>
<li>Env Var: RCLONE_FTP_SOCKS_PROXY</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="ftp-encoding">--ftp-encoding</h4>
<p>The encoding for the backend.</p>
<p>See the <a href="https://rclone.org/overview/#encoding">encoding section in the overview</a> for more info.</p>
<p>Properties:</p>
<ul>
<li>Config: encoding</li>
<li>Env Var: RCLONE_FTP_ENCODING</li>
<li>Type: Encoding</li>
<li>Default: Slash,Del,Ctl,RightSpace,Dot</li>
<li>Examples:
<ul>
<li>"Asterisk,Ctl,Dot,Slash"
<ul>
<li>ProFTPd can't handle '*' in file names</li>
</ul></li>
<li>"BackSlash,Ctl,Del,Dot,RightSpace,Slash,SquareBracket"
<ul>
<li>PureFTPd can't handle '[]' or '*' in file names</li>
</ul></li>
<li>"Ctl,LeftPeriod,Slash"
<ul>
<li>VsFTPd can't handle file names starting with dot</li>
</ul></li>
</ul></li>
</ul>
<h4 id="ftp-description">--ftp-description</h4>
<p>Description of the remote.</p>
<p>Properties:</p>
<ul>
<li>Config: description</li>
<li>Env Var: RCLONE_FTP_DESCRIPTION</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h2 id="limitations-11">Limitations</h2>
<p>FTP servers acting as rclone remotes must support <code>passive</code> mode. The mode cannot be configured as <code>passive</code> is the only supported one. Rclone's FTP implementation is not compatible with <code>active</code> mode as <a href="https://github.com/jlaffaye/ftp/issues/29">the library it uses doesn't support it</a>. This will likely never be supported due to security concerns.</p>
<p>Rclone's FTP backend does not support any checksums but can compare file sizes.</p>
<p><code>rclone about</code> is not supported by the FTP backend. Backends without this capability cannot determine free space for an rclone mount or use policy <code>mfs</code> (most free space) as a member of an rclone union remote.</p>
<p>See <a href="https://rclone.org/overview/#optional-features">List of backends that do not support rclone about</a> and <a href="https://rclone.org/commands/rclone_about/">rclone about</a></p>
<p>The implementation of : <code>--dump headers</code>, <code>--dump bodies</code>, <code>--dump auth</code> for debugging isn't the same as for rclone HTTP based backends - it has less fine grained control.</p>
<p><code>--timeout</code> isn't supported (but <code>--contimeout</code> is).</p>
<p><code>--bind</code> isn't supported.</p>
<p>Rclone's FTP backend could support server-side move but does not at present.</p>
<p>The <code>ftp_proxy</code> environment variable is not currently supported.</p>
<h3 id="modification-times-4">Modification times</h3>
<p>File modification time (timestamps) is supported to 1 second resolution for major FTP servers: ProFTPd, PureFTPd, VsFTPd, and FileZilla FTP server. The <code>VsFTPd</code> server has non-standard implementation of time related protocol commands and needs a special configuration setting: <code>writing_mdtm = true</code>.</p>
<p>Support for precise file time with other FTP servers varies depending on what protocol extensions they advertise. If all the <code>MLSD</code>, <code>MDTM</code> and <code>MFTM</code> extensions are present, rclone will use them together to provide precise time. Otherwise the times you see on the FTP server through rclone are those of the last file upload.</p>
<p>You can use the following command to check whether rclone can use precise time with your FTP server: <code>rclone backend features your_ftp_remote:</code> (the trailing colon is important). Look for the number in the line tagged by <code>Precision</code> designating the remote time precision expressed as nanoseconds. A value of <code>1000000000</code> means that file time precision of 1 second is available. A value of <code>3153600000000000000</code> (or another large number) means "unsupported".</p>
<h1 id="gofile">Gofile</h1>
<p><a href="https://gofile.io">Gofile</a> is a content storage and distribution platform. Its aim is to provide as much service as possible for free or at a very low price.</p>
<p>The initial setup for Gofile involves logging in to the web interface and going to the "My Profile" section. Copy the "Account API token" for use in the config file.</p>
<p>Note that if you wish to connect rclone to Gofile you will need a premium account.</p>
<h2 id="configuration-15">Configuration</h2>
<p>Here is an example of how to make a remote called <code>remote</code>. First run:</p>
<pre><code> rclone config</code></pre>
<p>This will guide you through an interactive setup process:</p>
<pre><code>No remotes found, make a new one?
n) New remote
s) Set configuration password
q) Quit config
n/s/q&gt; n

Enter name for new remote.
name&gt; remote

Option Storage.
Type of storage to configure.
Choose a number from below, or type in your own value.
XX / Gofile
   \ (gofile)
Storage&gt; gofile

Option access_token.
API Access token
You can get this from the web control panel.
Enter a value. Press Enter to leave empty.
access_token&gt; YOURACCESSTOKEN

Edit advanced config?
y) Yes
n) No (default)
y/n&gt; n

Configuration complete.
Options:
- type: gofile
- access_token: YOURACCESSTOKEN
Keep this &quot;remote&quot; remote?
y) Yes this is OK (default)
e) Edit this remote
d) Delete this remote
y/e/d&gt; y</code></pre>
<p>Once configured you can then use <code>rclone</code> like this,</p>
<p>List directories and files in the top level of your Gofile</p>
<pre><code>rclone lsf remote:</code></pre>
<p>To copy a local directory to an Gofile directory called backup</p>
<pre><code>rclone copy /home/source remote:backup</code></pre>
<h3 id="modification-times-and-hashes-7">Modification times and hashes</h3>
<p>Gofile supports modification times with a resolution of 1 second.</p>
<p>Gofile supports MD5 hashes, so you can use the <code>--checksum</code> flag.</p>
<h3 id="restricted-filename-characters-8">Restricted filename characters</h3>
<p>In addition to the <a href="https://rclone.org/overview/#restricted-characters">default restricted characters set</a> the following characters are also replaced:</p>
<table>
<thead>
<tr class="header">
<th>Character</th>
<th style="text-align: center;">Value</th>
<th style="text-align: center;">Replacement</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td>!</td>
<td style="text-align: center;">0x21</td>
<td style="text-align: center;">！</td>
</tr>
<tr class="even">
<td>"</td>
<td style="text-align: center;">0x22</td>
<td style="text-align: center;">＂</td>
</tr>
<tr class="odd">
<td>*</td>
<td style="text-align: center;">0x2A</td>
<td style="text-align: center;">＊</td>
</tr>
<tr class="even">
<td>:</td>
<td style="text-align: center;">0x3A</td>
<td style="text-align: center;">：</td>
</tr>
<tr class="odd">
<td>&lt;</td>
<td style="text-align: center;">0x3C</td>
<td style="text-align: center;">＜</td>
</tr>
<tr class="even">
<td>&gt;</td>
<td style="text-align: center;">0x3E</td>
<td style="text-align: center;">＞</td>
</tr>
<tr class="odd">
<td>?</td>
<td style="text-align: center;">0x3F</td>
<td style="text-align: center;">？</td>
</tr>
<tr class="even">
<td>\</td>
<td style="text-align: center;">0x5C</td>
<td style="text-align: center;">＼</td>
</tr>
<tr class="odd">
<td>|</td>
<td style="text-align: center;">0x7C</td>
<td style="text-align: center;">｜</td>
</tr>
</tbody>
</table>
<p>File names can also not start or end with the following characters. These only get replaced if they are the first or last character in the name:</p>
<table>
<thead>
<tr class="header">
<th>Character</th>
<th style="text-align: center;">Value</th>
<th style="text-align: center;">Replacement</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td>.</td>
<td style="text-align: center;">0x2E</td>
<td style="text-align: center;">．</td>
</tr>
</tbody>
</table>
<p>Invalid UTF-8 bytes will also be <a href="https://rclone.org/overview/#invalid-utf8">replaced</a>, as they can't be used in JSON strings.</p>
<h3 id="public-links">Public Links</h3>
<p>Gofile supports <code>rclone link</code> to make public links to files or directories. If you specify a directory it will download as a <code>zip</code> file. You can use the <code>--expire</code> flag to specify the time the link should be valid. Note that <code>rclone link --unlink</code> removes all the public links for a file.</p>
<h3 id="root-folder-id-2">Root folder ID</h3>
<p>You can set the <code>root_folder_id</code> for rclone. This is the directory (identified by its <code>Folder ID</code>) that rclone considers to be the root of your Gofile drive.</p>
<p>Normally you will leave this blank and rclone will determine the correct root to use itself and fill in the value in the config file.</p>
<p>However you can set this to restrict rclone to a specific folder hierarchy.</p>
<p>In order to do this you will have to find the <code>Folder ID</code> of the directory you wish rclone to display.</p>
<p>You can do this with rclone</p>
<pre><code>$ rclone lsf -Fip --dirs-only remote:
d6341f53-ee65-4f29-9f59-d11e8070b2a0;Files/
f4f5c9b8-6ece-478b-b03e-4538edfe5a1c;Photos/
d50e356c-29ca-4b27-a3a7-494d91026e04;Videos/</code></pre>
<p>The ID to use is the part before the <code>;</code> so you could set</p>
<pre><code>root_folder_id = d6341f53-ee65-4f29-9f59-d11e8070b2a0</code></pre>
<p>To restrict rclone to the <code>Files</code> directory.</p>
<h3 id="standard-options-15">Standard options</h3>
<p>Here are the Standard options specific to gofile (Gofile).</p>
<h4 id="gofile-access-token">--gofile-access-token</h4>
<p>API Access token</p>
<p>You can get this from the web control panel.</p>
<p>Properties:</p>
<ul>
<li>Config: access_token</li>
<li>Env Var: RCLONE_GOFILE_ACCESS_TOKEN</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h3 id="advanced-options-15">Advanced options</h3>
<p>Here are the Advanced options specific to gofile (Gofile).</p>
<h4 id="gofile-root-folder-id">--gofile-root-folder-id</h4>
<p>ID of the root folder</p>
<p>Leave this blank normally, rclone will fill it in automatically.</p>
<p>If you want rclone to be restricted to a particular folder you can fill it in - see the docs for more info.</p>
<p>Properties:</p>
<ul>
<li>Config: root_folder_id</li>
<li>Env Var: RCLONE_GOFILE_ROOT_FOLDER_ID</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="gofile-account-id">--gofile-account-id</h4>
<p>Account ID</p>
<p>Leave this blank normally, rclone will fill it in automatically.</p>
<p>Properties:</p>
<ul>
<li>Config: account_id</li>
<li>Env Var: RCLONE_GOFILE_ACCOUNT_ID</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="gofile-list-chunk">--gofile-list-chunk</h4>
<p>Number of items to list in each call</p>
<p>Properties:</p>
<ul>
<li>Config: list_chunk</li>
<li>Env Var: RCLONE_GOFILE_LIST_CHUNK</li>
<li>Type: int</li>
<li>Default: 1000</li>
</ul>
<h4 id="gofile-encoding">--gofile-encoding</h4>
<p>The encoding for the backend.</p>
<p>See the <a href="https://rclone.org/overview/#encoding">encoding section in the overview</a> for more info.</p>
<p>Properties:</p>
<ul>
<li>Config: encoding</li>
<li>Env Var: RCLONE_GOFILE_ENCODING</li>
<li>Type: Encoding</li>
<li>Default: Slash,LtGt,DoubleQuote,Colon,Question,Asterisk,Pipe,BackSlash,Del,Ctl,LeftPeriod,RightPeriod,InvalidUtf8,Dot,Exclamation</li>
</ul>
<h4 id="gofile-description">--gofile-description</h4>
<p>Description of the remote.</p>
<p>Properties:</p>
<ul>
<li>Config: description</li>
<li>Env Var: RCLONE_GOFILE_DESCRIPTION</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h2 id="limitations-12">Limitations</h2>
<p>Gofile only supports filenames up to 255 characters in length, where a character is a unicode character.</p>
<p>Directories should not be cached for more than 24h otherwise files in the directory may not be downloadable. In practice this means when using a VFS based rclone command such as <code>rclone mount</code> you should make sure <code>--dir-cache-time</code> is less than <code>24h</code>.</p>
<p>Note that Gofile is currently limited to a total of 100,000 items. If you attempt to upload more than that you will get <code>error-limit-100000</code>. This limit may be lifted in the future.</p>
<h3 id="duplicated-files-1">Duplicated files</h3>
<p>Gofile is capable of having files with duplicated file names. For instance two files called <code>hello.txt</code> in the same directory.</p>
<p>Rclone cannot sync that to a normal file system but it can be fixed with the <code>rclone dedupe</code> command.</p>
<p>Duplicated files cause problems with the syncing and you will see messages in the log about duplicates.</p>
<p>Use <code>rclone dedupe</code> to fix duplicated files.</p>
<h1 id="google-cloud-storage-1">Google Cloud Storage</h1>
<p>Paths are specified as <code>remote:bucket</code> (or <code>remote:</code> for the <code>lsd</code> command.) You may put subdirectories in too, e.g. <code>remote:bucket/path/to/dir</code>.</p>
<h2 id="configuration-16">Configuration</h2>
<p>The initial setup for google cloud storage involves getting a token from Google Cloud Storage which you need to do in your browser. <code>rclone config</code> walks you through it.</p>
<p>Here is an example of how to make a remote called <code>remote</code>. First run:</p>
<pre><code> rclone config</code></pre>
<p>This will guide you through an interactive setup process:</p>
<pre><code>n) New remote
d) Delete remote
q) Quit config
e/n/d/q&gt; n
name&gt; remote
Type of storage to configure.
Choose a number from below, or type in your own value
[snip]
XX / Google Cloud Storage (this is not Google Drive)
   \ &quot;google cloud storage&quot;
[snip]
Storage&gt; google cloud storage
Google Application Client Id - leave blank normally.
client_id&gt;
Google Application Client Secret - leave blank normally.
client_secret&gt;
Project number optional - needed only for list/create/delete buckets - see your developer console.
project_number&gt; 12345678
Service Account Credentials JSON file path - needed only if you want use SA instead of interactive login.
service_account_file&gt;
Access Control List for new objects.
Choose a number from below, or type in your own value
 1 / Object owner gets OWNER access, and all Authenticated Users get READER access.
   \ &quot;authenticatedRead&quot;
 2 / Object owner gets OWNER access, and project team owners get OWNER access.
   \ &quot;bucketOwnerFullControl&quot;
 3 / Object owner gets OWNER access, and project team owners get READER access.
   \ &quot;bucketOwnerRead&quot;
 4 / Object owner gets OWNER access [default if left blank].
   \ &quot;private&quot;
 5 / Object owner gets OWNER access, and project team members get access according to their roles.
   \ &quot;projectPrivate&quot;
 6 / Object owner gets OWNER access, and all Users get READER access.
   \ &quot;publicRead&quot;
object_acl&gt; 4
Access Control List for new buckets.
Choose a number from below, or type in your own value
 1 / Project team owners get OWNER access, and all Authenticated Users get READER access.
   \ &quot;authenticatedRead&quot;
 2 / Project team owners get OWNER access [default if left blank].
   \ &quot;private&quot;
 3 / Project team members get access according to their roles.
   \ &quot;projectPrivate&quot;
 4 / Project team owners get OWNER access, and all Users get READER access.
   \ &quot;publicRead&quot;
 5 / Project team owners get OWNER access, and all Users get WRITER access.
   \ &quot;publicReadWrite&quot;
bucket_acl&gt; 2
Location for the newly created buckets.
Choose a number from below, or type in your own value
 1 / Empty for default location (US).
   \ &quot;&quot;
 2 / Multi-regional location for Asia.
   \ &quot;asia&quot;
 3 / Multi-regional location for Europe.
   \ &quot;eu&quot;
 4 / Multi-regional location for United States.
   \ &quot;us&quot;
 5 / Taiwan.
   \ &quot;asia-east1&quot;
 6 / Tokyo.
   \ &quot;asia-northeast1&quot;
 7 / Singapore.
   \ &quot;asia-southeast1&quot;
 8 / Sydney.
   \ &quot;australia-southeast1&quot;
 9 / Belgium.
   \ &quot;europe-west1&quot;
10 / London.
   \ &quot;europe-west2&quot;
11 / Iowa.
   \ &quot;us-central1&quot;
12 / South Carolina.
   \ &quot;us-east1&quot;
13 / Northern Virginia.
   \ &quot;us-east4&quot;
14 / Oregon.
   \ &quot;us-west1&quot;
location&gt; 12
The storage class to use when storing objects in Google Cloud Storage.
Choose a number from below, or type in your own value
 1 / Default
   \ &quot;&quot;
 2 / Multi-regional storage class
   \ &quot;MULTI_REGIONAL&quot;
 3 / Regional storage class
   \ &quot;REGIONAL&quot;
 4 / Nearline storage class
   \ &quot;NEARLINE&quot;
 5 / Coldline storage class
   \ &quot;COLDLINE&quot;
 6 / Durable reduced availability storage class
   \ &quot;DURABLE_REDUCED_AVAILABILITY&quot;
storage_class&gt; 5
Remote config
Use web browser to automatically authenticate rclone with remote?
 * Say Y if the machine running rclone has a web browser you can use
 * Say N if running rclone on a (remote) machine without web browser access
If not sure try Y. If Y failed, try N.
y) Yes
n) No
y/n&gt; y
If your browser doesn&#39;t open automatically go to the following link: http://127.0.0.1:53682/auth
Log in and authorize rclone for access
Waiting for code...
Got code
Configuration complete.
Options:
- type: google cloud storage
- client_id:
- client_secret:
- token: {&quot;AccessToken&quot;:&quot;xxxx.xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx&quot;,&quot;RefreshToken&quot;:&quot;x/xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx_xxxxxxxxx&quot;,&quot;Expiry&quot;:&quot;2014-07-17T20:49:14.929208288+01:00&quot;,&quot;Extra&quot;:null}
- project_number: 12345678
- object_acl: private
- bucket_acl: private
Keep this &quot;remote&quot; remote?
y) Yes this is OK
e) Edit this remote
d) Delete this remote
y/e/d&gt; y</code></pre>
<p>See the <a href="https://rclone.org/remote_setup/">remote setup docs</a> for how to set it up on a machine with no Internet browser available.</p>
<p>Note that rclone runs a webserver on your local machine to collect the token as returned from Google if using web browser to automatically authenticate. This only runs from the moment it opens your browser to the moment you get back the verification code. This is on <code>http://127.0.0.1:53682/</code> and this it may require you to unblock it temporarily if you are running a host firewall, or use manual mode.</p>
<p>This remote is called <code>remote</code> and can now be used like this</p>
<p>See all the buckets in your project</p>
<pre><code>rclone lsd remote:</code></pre>
<p>Make a new bucket</p>
<pre><code>rclone mkdir remote:bucket</code></pre>
<p>List the contents of a bucket</p>
<pre><code>rclone ls remote:bucket</code></pre>
<p>Sync <code>/home/local/directory</code> to the remote bucket, deleting any excess files in the bucket.</p>
<pre><code>rclone sync --interactive /home/local/directory remote:bucket</code></pre>
<h3 id="service-account-support">Service Account support</h3>
<p>You can set up rclone with Google Cloud Storage in an unattended mode, i.e. not tied to a specific end-user Google account. This is useful when you want to synchronise files onto machines that don't have actively logged-in users, for example build machines.</p>
<p>To get credentials for Google Cloud Platform <a href="https://cloud.google.com/iam/docs/service-accounts">IAM Service Accounts</a>, please head to the <a href="https://console.cloud.google.com/permissions/serviceaccounts">Service Account</a> section of the Google Developer Console. Service Accounts behave just like normal <code>User</code> permissions in <a href="https://cloud.google.com/storage/docs/access-control">Google Cloud Storage ACLs</a>, so you can limit their access (e.g. make them read only). After creating an account, a JSON file containing the Service Account's credentials will be downloaded onto your machines. These credentials are what rclone will use for authentication.</p>
<p>To use a Service Account instead of OAuth2 token flow, enter the path to your Service Account credentials at the <code>service_account_file</code> prompt and rclone won't use the browser based authentication flow. If you'd rather stuff the contents of the credentials file into the rclone config file, you can set <code>service_account_credentials</code> with the actual contents of the file instead, or set the equivalent environment variable.</p>
<h3 id="anonymous-access-1">Anonymous Access</h3>
<p>For downloads of objects that permit public access you can configure rclone to use anonymous access by setting <code>anonymous</code> to <code>true</code>. With unauthorized access you can't write or create files but only read or list those buckets and objects that have public read access.</p>
<h3 id="application-default-credentials">Application Default Credentials</h3>
<p>If no other source of credentials is provided, rclone will fall back to <a href="https://cloud.google.com/video-intelligence/docs/common/auth#authenticating_with_application_default_credentials">Application Default Credentials</a> this is useful both when you already have configured authentication for your developer account, or in production when running on a google compute host. Note that if running in docker, you may need to run additional commands on your google compute machine - <a href="https://cloud.google.com/container-registry/docs/advanced-authentication#gcloud_as_a_docker_credential_helper">see this page</a>.</p>
<p>Note that in the case application default credentials are used, there is no need to explicitly configure a project number.</p>
<h3 id="fast-list-2">--fast-list</h3>
<p>This remote supports <code>--fast-list</code> which allows you to use fewer transactions in exchange for more memory. See the <a href="https://rclone.org/docs/#fast-list">rclone docs</a> for more details.</p>
<h3 id="custom-upload-headers">Custom upload headers</h3>
<p>You can set custom upload headers with the <code>--header-upload</code> flag. Google Cloud Storage supports the headers as described in the <a href="https://cloud.google.com/storage/docs/gsutil/addlhelp/WorkingWithObjectMetadata">working with metadata documentation</a></p>
<ul>
<li>Cache-Control</li>
<li>Content-Disposition</li>
<li>Content-Encoding</li>
<li>Content-Language</li>
<li>Content-Type</li>
<li>X-Goog-Storage-Class</li>
<li>X-Goog-Meta-</li>
</ul>
<p>Eg <code>--header-upload "Content-Type text/potato"</code></p>
<p>Note that the last of these is for setting custom metadata in the form <code>--header-upload "x-goog-meta-key: value"</code></p>
<h3 id="modification-times-5">Modification times</h3>
<p>Google Cloud Storage stores md5sum natively. Google's <a href="https://cloud.google.com/storage/docs/gsutil">gsutil</a> tool stores modification time with one-second precision as <code>goog-reserved-file-mtime</code> in file metadata.</p>
<p>To ensure compatibility with gsutil, rclone stores modification time in 2 separate metadata entries. <code>mtime</code> uses RFC3339 format with one-nanosecond precision. <code>goog-reserved-file-mtime</code> uses Unix timestamp format with one-second precision. To get modification time from object metadata, rclone reads the metadata in the following order: <code>mtime</code>, <code>goog-reserved-file-mtime</code>, object updated time.</p>
<p>Note that rclone's default modify window is 1ns. Files uploaded by gsutil only contain timestamps with one-second precision. If you use rclone to sync files previously uploaded by gsutil, rclone will attempt to update modification time for all these files. To avoid these possibly unnecessary updates, use <code>--modify-window 1s</code>.</p>
<h3 id="restricted-filename-characters-9">Restricted filename characters</h3>
<table>
<thead>
<tr class="header">
<th>Character</th>
<th style="text-align: center;">Value</th>
<th style="text-align: center;">Replacement</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td>NUL</td>
<td style="text-align: center;">0x00</td>
<td style="text-align: center;">␀</td>
</tr>
<tr class="even">
<td>LF</td>
<td style="text-align: center;">0x0A</td>
<td style="text-align: center;">␊</td>
</tr>
<tr class="odd">
<td>CR</td>
<td style="text-align: center;">0x0D</td>
<td style="text-align: center;">␍</td>
</tr>
<tr class="even">
<td>/</td>
<td style="text-align: center;">0x2F</td>
<td style="text-align: center;">／</td>
</tr>
</tbody>
</table>
<p>Invalid UTF-8 bytes will also be <a href="https://rclone.org/overview/#invalid-utf8">replaced</a>, as they can't be used in JSON strings.</p>
<h3 id="standard-options-16">Standard options</h3>
<p>Here are the Standard options specific to google cloud storage (Google Cloud Storage (this is not Google Drive)).</p>
<h4 id="gcs-client-id">--gcs-client-id</h4>
<p>OAuth Client Id.</p>
<p>Leave blank normally.</p>
<p>Properties:</p>
<ul>
<li>Config: client_id</li>
<li>Env Var: RCLONE_GCS_CLIENT_ID</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="gcs-client-secret">--gcs-client-secret</h4>
<p>OAuth Client Secret.</p>
<p>Leave blank normally.</p>
<p>Properties:</p>
<ul>
<li>Config: client_secret</li>
<li>Env Var: RCLONE_GCS_CLIENT_SECRET</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="gcs-project-number">--gcs-project-number</h4>
<p>Project number.</p>
<p>Optional - needed only for list/create/delete buckets - see your developer console.</p>
<p>Properties:</p>
<ul>
<li>Config: project_number</li>
<li>Env Var: RCLONE_GCS_PROJECT_NUMBER</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="gcs-user-project">--gcs-user-project</h4>
<p>User project.</p>
<p>Optional - needed only for requester pays.</p>
<p>Properties:</p>
<ul>
<li>Config: user_project</li>
<li>Env Var: RCLONE_GCS_USER_PROJECT</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="gcs-service-account-file">--gcs-service-account-file</h4>
<p>Service Account Credentials JSON file path.</p>
<p>Leave blank normally. Needed only if you want use SA instead of interactive login.</p>
<p>Leading <code>~</code> will be expanded in the file name as will environment variables such as <code>${RCLONE_CONFIG_DIR}</code>.</p>
<p>Properties:</p>
<ul>
<li>Config: service_account_file</li>
<li>Env Var: RCLONE_GCS_SERVICE_ACCOUNT_FILE</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="gcs-service-account-credentials">--gcs-service-account-credentials</h4>
<p>Service Account Credentials JSON blob.</p>
<p>Leave blank normally. Needed only if you want use SA instead of interactive login.</p>
<p>Properties:</p>
<ul>
<li>Config: service_account_credentials</li>
<li>Env Var: RCLONE_GCS_SERVICE_ACCOUNT_CREDENTIALS</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="gcs-anonymous">--gcs-anonymous</h4>
<p>Access public buckets and objects without credentials.</p>
<p>Set to 'true' if you just want to download files and don't configure credentials.</p>
<p>Properties:</p>
<ul>
<li>Config: anonymous</li>
<li>Env Var: RCLONE_GCS_ANONYMOUS</li>
<li>Type: bool</li>
<li>Default: false</li>
</ul>
<h4 id="gcs-object-acl">--gcs-object-acl</h4>
<p>Access Control List for new objects.</p>
<p>Properties:</p>
<ul>
<li>Config: object_acl</li>
<li>Env Var: RCLONE_GCS_OBJECT_ACL</li>
<li>Type: string</li>
<li>Required: false</li>
<li>Examples:
<ul>
<li>"authenticatedRead"
<ul>
<li>Object owner gets OWNER access.</li>
<li>All Authenticated Users get READER access.</li>
</ul></li>
<li>"bucketOwnerFullControl"
<ul>
<li>Object owner gets OWNER access.</li>
<li>Project team owners get OWNER access.</li>
</ul></li>
<li>"bucketOwnerRead"
<ul>
<li>Object owner gets OWNER access.</li>
<li>Project team owners get READER access.</li>
</ul></li>
<li>"private"
<ul>
<li>Object owner gets OWNER access.</li>
<li>Default if left blank.</li>
</ul></li>
<li>"projectPrivate"
<ul>
<li>Object owner gets OWNER access.</li>
<li>Project team members get access according to their roles.</li>
</ul></li>
<li>"publicRead"
<ul>
<li>Object owner gets OWNER access.</li>
<li>All Users get READER access.</li>
</ul></li>
</ul></li>
</ul>
<h4 id="gcs-bucket-acl">--gcs-bucket-acl</h4>
<p>Access Control List for new buckets.</p>
<p>Properties:</p>
<ul>
<li>Config: bucket_acl</li>
<li>Env Var: RCLONE_GCS_BUCKET_ACL</li>
<li>Type: string</li>
<li>Required: false</li>
<li>Examples:
<ul>
<li>"authenticatedRead"
<ul>
<li>Project team owners get OWNER access.</li>
<li>All Authenticated Users get READER access.</li>
</ul></li>
<li>"private"
<ul>
<li>Project team owners get OWNER access.</li>
<li>Default if left blank.</li>
</ul></li>
<li>"projectPrivate"
<ul>
<li>Project team members get access according to their roles.</li>
</ul></li>
<li>"publicRead"
<ul>
<li>Project team owners get OWNER access.</li>
<li>All Users get READER access.</li>
</ul></li>
<li>"publicReadWrite"
<ul>
<li>Project team owners get OWNER access.</li>
<li>All Users get WRITER access.</li>
</ul></li>
</ul></li>
</ul>
<h4 id="gcs-bucket-policy-only">--gcs-bucket-policy-only</h4>
<p>Access checks should use bucket-level IAM policies.</p>
<p>If you want to upload objects to a bucket with Bucket Policy Only set then you will need to set this.</p>
<p>When it is set, rclone:</p>
<ul>
<li>ignores ACLs set on buckets</li>
<li>ignores ACLs set on objects</li>
<li>creates buckets with Bucket Policy Only set</li>
</ul>
<p>Docs: https://cloud.google.com/storage/docs/bucket-policy-only</p>
<p>Properties:</p>
<ul>
<li>Config: bucket_policy_only</li>
<li>Env Var: RCLONE_GCS_BUCKET_POLICY_ONLY</li>
<li>Type: bool</li>
<li>Default: false</li>
</ul>
<h4 id="gcs-location">--gcs-location</h4>
<p>Location for the newly created buckets.</p>
<p>Properties:</p>
<ul>
<li>Config: location</li>
<li>Env Var: RCLONE_GCS_LOCATION</li>
<li>Type: string</li>
<li>Required: false</li>
<li>Examples:
<ul>
<li>""
<ul>
<li>Empty for default location (US)</li>
</ul></li>
<li>"asia"
<ul>
<li>Multi-regional location for Asia</li>
</ul></li>
<li>"eu"
<ul>
<li>Multi-regional location for Europe</li>
</ul></li>
<li>"us"
<ul>
<li>Multi-regional location for United States</li>
</ul></li>
<li>"asia-east1"
<ul>
<li>Taiwan</li>
</ul></li>
<li>"asia-east2"
<ul>
<li>Hong Kong</li>
</ul></li>
<li>"asia-northeast1"
<ul>
<li>Tokyo</li>
</ul></li>
<li>"asia-northeast2"
<ul>
<li>Osaka</li>
</ul></li>
<li>"asia-northeast3"
<ul>
<li>Seoul</li>
</ul></li>
<li>"asia-south1"
<ul>
<li>Mumbai</li>
</ul></li>
<li>"asia-south2"
<ul>
<li>Delhi</li>
</ul></li>
<li>"asia-southeast1"
<ul>
<li>Singapore</li>
</ul></li>
<li>"asia-southeast2"
<ul>
<li>Jakarta</li>
</ul></li>
<li>"australia-southeast1"
<ul>
<li>Sydney</li>
</ul></li>
<li>"australia-southeast2"
<ul>
<li>Melbourne</li>
</ul></li>
<li>"europe-north1"
<ul>
<li>Finland</li>
</ul></li>
<li>"europe-west1"
<ul>
<li>Belgium</li>
</ul></li>
<li>"europe-west2"
<ul>
<li>London</li>
</ul></li>
<li>"europe-west3"
<ul>
<li>Frankfurt</li>
</ul></li>
<li>"europe-west4"
<ul>
<li>Netherlands</li>
</ul></li>
<li>"europe-west6"
<ul>
<li>Zürich</li>
</ul></li>
<li>"europe-central2"
<ul>
<li>Warsaw</li>
</ul></li>
<li>"us-central1"
<ul>
<li>Iowa</li>
</ul></li>
<li>"us-east1"
<ul>
<li>South Carolina</li>
</ul></li>
<li>"us-east4"
<ul>
<li>Northern Virginia</li>
</ul></li>
<li>"us-west1"
<ul>
<li>Oregon</li>
</ul></li>
<li>"us-west2"
<ul>
<li>California</li>
</ul></li>
<li>"us-west3"
<ul>
<li>Salt Lake City</li>
</ul></li>
<li>"us-west4"
<ul>
<li>Las Vegas</li>
</ul></li>
<li>"northamerica-northeast1"
<ul>
<li>Montréal</li>
</ul></li>
<li>"northamerica-northeast2"
<ul>
<li>Toronto</li>
</ul></li>
<li>"southamerica-east1"
<ul>
<li>São Paulo</li>
</ul></li>
<li>"southamerica-west1"
<ul>
<li>Santiago</li>
</ul></li>
<li>"asia1"
<ul>
<li>Dual region: asia-northeast1 and asia-northeast2.</li>
</ul></li>
<li>"eur4"
<ul>
<li>Dual region: europe-north1 and europe-west4.</li>
</ul></li>
<li>"nam4"
<ul>
<li>Dual region: us-central1 and us-east1.</li>
</ul></li>
</ul></li>
</ul>
<h4 id="gcs-storage-class">--gcs-storage-class</h4>
<p>The storage class to use when storing objects in Google Cloud Storage.</p>
<p>Properties:</p>
<ul>
<li>Config: storage_class</li>
<li>Env Var: RCLONE_GCS_STORAGE_CLASS</li>
<li>Type: string</li>
<li>Required: false</li>
<li>Examples:
<ul>
<li>""
<ul>
<li>Default</li>
</ul></li>
<li>"MULTI_REGIONAL"
<ul>
<li>Multi-regional storage class</li>
</ul></li>
<li>"REGIONAL"
<ul>
<li>Regional storage class</li>
</ul></li>
<li>"NEARLINE"
<ul>
<li>Nearline storage class</li>
</ul></li>
<li>"COLDLINE"
<ul>
<li>Coldline storage class</li>
</ul></li>
<li>"ARCHIVE"
<ul>
<li>Archive storage class</li>
</ul></li>
<li>"DURABLE_REDUCED_AVAILABILITY"
<ul>
<li>Durable reduced availability storage class</li>
</ul></li>
</ul></li>
</ul>
<h4 id="gcs-env-auth">--gcs-env-auth</h4>
<p>Get GCP IAM credentials from runtime (environment variables or instance meta data if no env vars).</p>
<p>Only applies if service_account_file and service_account_credentials is blank.</p>
<p>Properties:</p>
<ul>
<li>Config: env_auth</li>
<li>Env Var: RCLONE_GCS_ENV_AUTH</li>
<li>Type: bool</li>
<li>Default: false</li>
<li>Examples:
<ul>
<li>"false"
<ul>
<li>Enter credentials in the next step.</li>
</ul></li>
<li>"true"
<ul>
<li>Get GCP IAM credentials from the environment (env vars or IAM).</li>
</ul></li>
</ul></li>
</ul>
<h3 id="advanced-options-16">Advanced options</h3>
<p>Here are the Advanced options specific to google cloud storage (Google Cloud Storage (this is not Google Drive)).</p>
<h4 id="gcs-token">--gcs-token</h4>
<p>OAuth Access Token as a JSON blob.</p>
<p>Properties:</p>
<ul>
<li>Config: token</li>
<li>Env Var: RCLONE_GCS_TOKEN</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="gcs-auth-url">--gcs-auth-url</h4>
<p>Auth server URL.</p>
<p>Leave blank to use the provider defaults.</p>
<p>Properties:</p>
<ul>
<li>Config: auth_url</li>
<li>Env Var: RCLONE_GCS_AUTH_URL</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="gcs-token-url">--gcs-token-url</h4>
<p>Token server url.</p>
<p>Leave blank to use the provider defaults.</p>
<p>Properties:</p>
<ul>
<li>Config: token_url</li>
<li>Env Var: RCLONE_GCS_TOKEN_URL</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="gcs-directory-markers">--gcs-directory-markers</h4>
<p>Upload an empty object with a trailing slash when a new directory is created</p>
<p>Empty folders are unsupported for bucket based remotes, this option creates an empty object ending with "/", to persist the folder.</p>
<p>Properties:</p>
<ul>
<li>Config: directory_markers</li>
<li>Env Var: RCLONE_GCS_DIRECTORY_MARKERS</li>
<li>Type: bool</li>
<li>Default: false</li>
</ul>
<h4 id="gcs-no-check-bucket">--gcs-no-check-bucket</h4>
<p>If set, don't attempt to check the bucket exists or create it.</p>
<p>This can be useful when trying to minimise the number of transactions rclone does if you know the bucket exists already.</p>
<p>Properties:</p>
<ul>
<li>Config: no_check_bucket</li>
<li>Env Var: RCLONE_GCS_NO_CHECK_BUCKET</li>
<li>Type: bool</li>
<li>Default: false</li>
</ul>
<h4 id="gcs-decompress">--gcs-decompress</h4>
<p>If set this will decompress gzip encoded objects.</p>
<p>It is possible to upload objects to GCS with "Content-Encoding: gzip" set. Normally rclone will download these files as compressed objects.</p>
<p>If this flag is set then rclone will decompress these files with "Content-Encoding: gzip" as they are received. This means that rclone can't check the size and hash but the file contents will be decompressed.</p>
<p>Properties:</p>
<ul>
<li>Config: decompress</li>
<li>Env Var: RCLONE_GCS_DECOMPRESS</li>
<li>Type: bool</li>
<li>Default: false</li>
</ul>
<h4 id="gcs-endpoint">--gcs-endpoint</h4>
<p>Endpoint for the service.</p>
<p>Leave blank normally.</p>
<p>Properties:</p>
<ul>
<li>Config: endpoint</li>
<li>Env Var: RCLONE_GCS_ENDPOINT</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="gcs-encoding">--gcs-encoding</h4>
<p>The encoding for the backend.</p>
<p>See the <a href="https://rclone.org/overview/#encoding">encoding section in the overview</a> for more info.</p>
<p>Properties:</p>
<ul>
<li>Config: encoding</li>
<li>Env Var: RCLONE_GCS_ENCODING</li>
<li>Type: Encoding</li>
<li>Default: Slash,CrLf,InvalidUtf8,Dot</li>
</ul>
<h4 id="gcs-description">--gcs-description</h4>
<p>Description of the remote.</p>
<p>Properties:</p>
<ul>
<li>Config: description</li>
<li>Env Var: RCLONE_GCS_DESCRIPTION</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h2 id="limitations-13">Limitations</h2>
<p><code>rclone about</code> is not supported by the Google Cloud Storage backend. Backends without this capability cannot determine free space for an rclone mount or use policy <code>mfs</code> (most free space) as a member of an rclone union remote.</p>
<p>See <a href="https://rclone.org/overview/#optional-features">List of backends that do not support rclone about</a> and <a href="https://rclone.org/commands/rclone_about/">rclone about</a></p>
<h1 id="google-drive">Google Drive</h1>
<p>Paths are specified as <code>drive:path</code></p>
<p>Drive paths may be as deep as required, e.g. <code>drive:directory/subdirectory</code>.</p>
<h2 id="configuration-17">Configuration</h2>
<p>The initial setup for drive involves getting a token from Google drive which you need to do in your browser. <code>rclone config</code> walks you through it.</p>
<p>Here is an example of how to make a remote called <code>remote</code>. First run:</p>
<pre><code> rclone config</code></pre>
<p>This will guide you through an interactive setup process:</p>
<pre><code>No remotes found, make a new one?
n) New remote
r) Rename remote
c) Copy remote
s) Set configuration password
q) Quit config
n/r/c/s/q&gt; n
name&gt; remote
Type of storage to configure.
Choose a number from below, or type in your own value
[snip]
XX / Google Drive
   \ &quot;drive&quot;
[snip]
Storage&gt; drive
Google Application Client Id - leave blank normally.
client_id&gt;
Google Application Client Secret - leave blank normally.
client_secret&gt;
Scope that rclone should use when requesting access from drive.
Choose a number from below, or type in your own value
 1 / Full access all files, excluding Application Data Folder.
   \ &quot;drive&quot;
 2 / Read-only access to file metadata and file contents.
   \ &quot;drive.readonly&quot;
   / Access to files created by rclone only.
 3 | These are visible in the drive website.
   | File authorization is revoked when the user deauthorizes the app.
   \ &quot;drive.file&quot;
   / Allows read and write access to the Application Data folder.
 4 | This is not visible in the drive website.
   \ &quot;drive.appfolder&quot;
   / Allows read-only access to file metadata but
 5 | does not allow any access to read or download file content.
   \ &quot;drive.metadata.readonly&quot;
scope&gt; 1
Service Account Credentials JSON file path - needed only if you want use SA instead of interactive login.
service_account_file&gt;
Remote config
Use web browser to automatically authenticate rclone with remote?
 * Say Y if the machine running rclone has a web browser you can use
 * Say N if running rclone on a (remote) machine without web browser access
If not sure try Y. If Y failed, try N.
y) Yes
n) No
y/n&gt; y
If your browser doesn&#39;t open automatically go to the following link: http://127.0.0.1:53682/auth
Log in and authorize rclone for access
Waiting for code...
Got code
Configure this as a Shared Drive (Team Drive)?
y) Yes
n) No
y/n&gt; n
Configuration complete.
Options:
type: drive
- client_id:
- client_secret:
- scope: drive
- root_folder_id:
- service_account_file:
- token: {&quot;access_token&quot;:&quot;XXX&quot;,&quot;token_type&quot;:&quot;Bearer&quot;,&quot;refresh_token&quot;:&quot;XXX&quot;,&quot;expiry&quot;:&quot;2014-03-16T13:57:58.955387075Z&quot;}
Keep this &quot;remote&quot; remote?
y) Yes this is OK
e) Edit this remote
d) Delete this remote
y/e/d&gt; y</code></pre>
<p>See the <a href="https://rclone.org/remote_setup/">remote setup docs</a> for how to set it up on a machine with no Internet browser available.</p>
<p>Note that rclone runs a webserver on your local machine to collect the token as returned from Google if using web browser to automatically authenticate. This only runs from the moment it opens your browser to the moment you get back the verification code. This is on <code>http://127.0.0.1:53682/</code> and it may require you to unblock it temporarily if you are running a host firewall, or use manual mode.</p>
<p>You can then use it like this,</p>
<p>List directories in top level of your drive</p>
<pre><code>rclone lsd remote:</code></pre>
<p>List all the files in your drive</p>
<pre><code>rclone ls remote:</code></pre>
<p>To copy a local directory to a drive directory called backup</p>
<pre><code>rclone copy /home/source remote:backup</code></pre>
<h3 id="scopes">Scopes</h3>
<p>Rclone allows you to select which scope you would like for rclone to use. This changes what type of token is granted to rclone. <a href="https://developers.google.com/drive/v3/web/about-auth">The scopes are defined here</a>.</p>
<p>A comma-separated list is allowed e.g. <code>drive.readonly,drive.file</code>.</p>
<p>The scope are</p>
<h4 id="drive">drive</h4>
<p>This is the default scope and allows full access to all files, except for the Application Data Folder (see below).</p>
<p>Choose this one if you aren't sure.</p>
<h4 id="drive.readonly">drive.readonly</h4>
<p>This allows read only access to all files. Files may be listed and downloaded but not uploaded, renamed or deleted.</p>
<h4 id="drive.file">drive.file</h4>
<p>With this scope rclone can read/view/modify only those files and folders it creates.</p>
<p>So if you uploaded files to drive via the web interface (or any other means) they will not be visible to rclone.</p>
<p>This can be useful if you are using rclone to backup data and you want to be sure confidential data on your drive is not visible to rclone.</p>
<p>Files created with this scope are visible in the web interface.</p>
<h4 id="drive.appfolder">drive.appfolder</h4>
<p>This gives rclone its own private area to store files. Rclone will not be able to see any other files on your drive and you won't be able to see rclone's files from the web interface either.</p>
<h4 id="drive.metadata.readonly">drive.metadata.readonly</h4>
<p>This allows read only access to file names only. It does not allow rclone to download or upload data, or rename or delete files or directories.</p>
<h3 id="root-folder-id-3">Root folder ID</h3>
<p>This option has been moved to the advanced section. You can set the <code>root_folder_id</code> for rclone. This is the directory (identified by its <code>Folder ID</code>) that rclone considers to be the root of your drive.</p>
<p>Normally you will leave this blank and rclone will determine the correct root to use itself.</p>
<p>However you can set this to restrict rclone to a specific folder hierarchy or to access data within the "Computers" tab on the drive web interface (where files from Google's Backup and Sync desktop program go).</p>
<p>In order to do this you will have to find the <code>Folder ID</code> of the directory you wish rclone to display. This will be the last segment of the URL when you open the relevant folder in the drive web interface.</p>
<p>So if the folder you want rclone to use has a URL which looks like <code>https://drive.google.com/drive/folders/1XyfxxxxxxxxxxxxxxxxxxxxxxxxxKHCh</code> in the browser, then you use <code>1XyfxxxxxxxxxxxxxxxxxxxxxxxxxKHCh</code> as the <code>root_folder_id</code> in the config.</p>
<p><strong>NB</strong> folders under the "Computers" tab seem to be read only (drive gives a 500 error) when using rclone.</p>
<p>There doesn't appear to be an API to discover the folder IDs of the "Computers" tab - please contact us if you know otherwise!</p>
<p>Note also that rclone can't access any data under the "Backups" tab on the google drive web interface yet.</p>
<h3 id="service-account-support-1">Service Account support</h3>
<p>You can set up rclone with Google Drive in an unattended mode, i.e. not tied to a specific end-user Google account. This is useful when you want to synchronise files onto machines that don't have actively logged-in users, for example build machines.</p>
<p>To use a Service Account instead of OAuth2 token flow, enter the path to your Service Account credentials at the <code>service_account_file</code> prompt during <code>rclone config</code> and rclone won't use the browser based authentication flow. If you'd rather stuff the contents of the credentials file into the rclone config file, you can set <code>service_account_credentials</code> with the actual contents of the file instead, or set the equivalent environment variable.</p>
<h4 id="use-case---google-workspace-account-and-individual-drive">Use case - Google Workspace account and individual Drive</h4>
<p>Let's say that you are the administrator of a Google Workspace. The goal is to read or write data on an individual's Drive account, who IS a member of the domain. We'll call the domain <strong>example.com</strong>, and the user <strong>foo@example.com</strong>.</p>
<p>There's a few steps we need to go through to accomplish this:</p>
<h5 id="create-a-service-account-for-example.com">1. Create a service account for example.com</h5>
<ul>
<li>To create a service account and obtain its credentials, go to the <a href="https://console.developers.google.com">Google Developer Console</a>.</li>
<li>You must have a project - create one if you don't and make sure you are on the selected project.</li>
<li>Then go to "IAM &amp; admin" -&gt; "Service Accounts".</li>
<li>Use the "Create Service Account" button. Fill in "Service account name" and "Service account ID" with something that identifies your client.</li>
<li>Select "Create And Continue". Step 2 and 3 are optional.</li>
<li>Click on the newly created service account</li>
<li>Click "Keys" and then "Add Key" and then "Create new key"</li>
<li>Choose type "JSON" and click create</li>
<li>This will download a small JSON file that rclone will use for authentication.</li>
</ul>
<p>If you ever need to remove access, press the "Delete service account key" button.</p>
<h5 id="allowing-api-access-to-example.com-google-drive">2. Allowing API access to example.com Google Drive</h5>
<ul>
<li>Go to example.com's <a href="https://admin.google.com">Workspace Admin Console</a></li>
<li>Go into "Security" (or use the search bar)</li>
<li>Select "Access and data control" and then "API controls"</li>
<li>Click "Manage domain-wide delegation"</li>
<li>Click "Add new"</li>
<li>In the "Client ID" field enter the service account's "Client ID" - this can be found in the Developer Console under "IAM &amp; Admin" -&gt; "Service Accounts", then "View Client ID" for the newly created service account. It is a ~21 character numerical string.</li>
<li>In the next field, "OAuth Scopes", enter <code>https://www.googleapis.com/auth/drive</code> to grant read/write access to Google Drive specifically. You can also use <code>https://www.googleapis.com/auth/drive.readonly</code> for read only access.</li>
<li>Click "Authorise"</li>
</ul>
<h5 id="configure-rclone-assuming-a-new-install">3. Configure rclone, assuming a new install</h5>
<pre><code>rclone config

n/s/q&gt; n         # New
name&gt;gdrive      # Gdrive is an example name
Storage&gt;         # Type drive
client_id&gt;       # Can be left blank
client_secret&gt;   # Can be left blank
scope&gt;           # Select the scope use used in step 2
root_folder_id&gt;  # Can be left blank
service_account_file&gt; /home/foo/myJSONfile.json # Path to the JSON file you downloaded in step 1.
y/n&gt;             # Auto config, n
</code></pre>
<h5 id="verify-that-its-working">4. Verify that it's working</h5>
<ul>
<li><code>rclone -v --drive-impersonate foo@example.com lsf gdrive:backup</code></li>
<li>The arguments do:
<ul>
<li><code>-v</code> - verbose logging</li>
<li><code>--drive-impersonate foo@example.com</code> - this is what does the magic, pretending to be user foo.</li>
<li><code>lsf</code> - list files in a parsing friendly way</li>
<li><code>gdrive:backup</code> - use the remote called gdrive, work in the folder named backup.</li>
</ul></li>
</ul>
<p>Note: in case you configured a specific root folder on gdrive and rclone is unable to access the contents of that folder when using <code>--drive-impersonate</code>, do this instead: - in the gdrive web interface, share your root folder with the user/email of the new Service Account you created/selected at step 1 - use rclone without specifying the <code>--drive-impersonate</code> option, like this: <code>rclone -v lsf gdrive:backup</code></p>
<h3 id="shared-drives-team-drives">Shared drives (team drives)</h3>
<p>If you want to configure the remote to point to a Google Shared Drive (previously known as Team Drives) then answer <code>y</code> to the question <code>Configure this as a Shared Drive (Team Drive)?</code>.</p>
<p>This will fetch the list of Shared Drives from google and allow you to configure which one you want to use. You can also type in a Shared Drive ID if you prefer.</p>
<p>For example:</p>
<pre><code>Configure this as a Shared Drive (Team Drive)?
y) Yes
n) No
y/n&gt; y
Fetching Shared Drive list...
Choose a number from below, or type in your own value
 1 / Rclone Test
   \ &quot;xxxxxxxxxxxxxxxxxxxx&quot;
 2 / Rclone Test 2
   \ &quot;yyyyyyyyyyyyyyyyyyyy&quot;
 3 / Rclone Test 3
   \ &quot;zzzzzzzzzzzzzzzzzzzz&quot;
Enter a Shared Drive ID&gt; 1
Configuration complete.
Options:
- type: drive
- client_id:
- client_secret:
- token: {&quot;AccessToken&quot;:&quot;xxxx.x.xxxxx_xxxxxxxxxxx_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx&quot;,&quot;RefreshToken&quot;:&quot;1/xxxxxxxxxxxxxxxx_xxxxxxxxxxxxxxxxxxxxxxxxxx&quot;,&quot;Expiry&quot;:&quot;2014-03-16T13:57:58.955387075Z&quot;,&quot;Extra&quot;:null}
- team_drive: xxxxxxxxxxxxxxxxxxxx
Keep this &quot;remote&quot; remote?
y) Yes this is OK
e) Edit this remote
d) Delete this remote
y/e/d&gt; y</code></pre>
<h3 id="fast-list-3">--fast-list</h3>
<p>This remote supports <code>--fast-list</code> which allows you to use fewer transactions in exchange for more memory. See the <a href="https://rclone.org/docs/#fast-list">rclone docs</a> for more details.</p>
<p>It does this by combining multiple <code>list</code> calls into a single API request.</p>
<p>This works by combining many <code>'%s' in parents</code> filters into one expression. To list the contents of directories a, b and c, the following requests will be send by the regular <code>List</code> function:</p>
<pre><code>trashed=false and &#39;a&#39; in parents
trashed=false and &#39;b&#39; in parents
trashed=false and &#39;c&#39; in parents</code></pre>
<p>These can now be combined into a single request:</p>
<pre><code>trashed=false and (&#39;a&#39; in parents or &#39;b&#39; in parents or &#39;c&#39; in parents)</code></pre>
<p>The implementation of <code>ListR</code> will put up to 50 <code>parents</code> filters into one request. It will use the <code>--checkers</code> value to specify the number of requests to run in parallel.</p>
<p>In tests, these batch requests were up to 20x faster than the regular method. Running the following command against different sized folders gives:</p>
<pre><code>rclone lsjson -vv -R --checkers=6 gdrive:folder</code></pre>
<p>small folder (220 directories, 700 files):</p>
<ul>
<li>without <code>--fast-list</code>: 38s</li>
<li>with <code>--fast-list</code>: 10s</li>
</ul>
<p>large folder (10600 directories, 39000 files):</p>
<ul>
<li>without <code>--fast-list</code>: 22:05 min</li>
<li>with <code>--fast-list</code>: 58s</li>
</ul>
<h3 id="modification-times-and-hashes-8">Modification times and hashes</h3>
<p>Google drive stores modification times accurate to 1 ms.</p>
<p>Hash algorithms MD5, SHA1 and SHA256 are supported. Note, however, that a small fraction of files uploaded may not have SHA1 or SHA256 hashes especially if they were uploaded before 2018.</p>
<h3 id="restricted-filename-characters-10">Restricted filename characters</h3>
<p>Only Invalid UTF-8 bytes will be <a href="https://rclone.org/overview/#invalid-utf8">replaced</a>, as they can't be used in JSON strings.</p>
<p>In contrast to other backends, <code>/</code> can also be used in names and <code>.</code> or <code>..</code> are valid names.</p>
<h3 id="revisions">Revisions</h3>
<p>Google drive stores revisions of files. When you upload a change to an existing file to google drive using rclone it will create a new revision of that file.</p>
<p>Revisions follow the standard google policy which at time of writing was</p>
<ul>
<li>They are deleted after 30 days or 100 revisions (whatever comes first).</li>
<li>They do not count towards a user storage quota.</li>
</ul>
<h3 id="deleting-files-1">Deleting files</h3>
<p>By default rclone will send all files to the trash when deleting files. If deleting them permanently is required then use the <code>--drive-use-trash=false</code> flag, or set the equivalent environment variable.</p>
<h3 id="shortcuts">Shortcuts</h3>
<p>In March 2020 Google introduced a new feature in Google Drive called <a href="https://support.google.com/drive/answer/9700156">drive shortcuts</a> (<a href="https://developers.google.com/drive/api/v3/shortcuts">API</a>). These will (by September 2020) <a href="https://cloud.google.com/blog/products/g-suite/simplifying-google-drives-folder-structure-and-sharing-models">replace the ability for files or folders to be in multiple folders at once</a>.</p>
<p>Shortcuts are files that link to other files on Google Drive somewhat like a symlink in unix, except they point to the underlying file data (e.g. the inode in unix terms) so they don't break if the source is renamed or moved about.</p>
<p>By default rclone treats these as follows.</p>
<p>For shortcuts pointing to files:</p>
<ul>
<li>When listing a file shortcut appears as the destination file.</li>
<li>When downloading the contents of the destination file is downloaded.</li>
<li>When updating shortcut file with a non shortcut file, the shortcut is removed then a new file is uploaded in place of the shortcut.</li>
<li>When server-side moving (renaming) the shortcut is renamed, not the destination file.</li>
<li>When server-side copying the shortcut is copied, not the contents of the shortcut. (unless <code>--drive-copy-shortcut-content</code> is in use in which case the contents of the shortcut gets copied).</li>
<li>When deleting the shortcut is deleted not the linked file.</li>
<li>When setting the modification time, the modification time of the linked file will be set.</li>
</ul>
<p>For shortcuts pointing to folders:</p>
<ul>
<li>When listing the shortcut appears as a folder and that folder will contain the contents of the linked folder appear (including any sub folders)</li>
<li>When downloading the contents of the linked folder and sub contents are downloaded</li>
<li>When uploading to a shortcut folder the file will be placed in the linked folder</li>
<li>When server-side moving (renaming) the shortcut is renamed, not the destination folder</li>
<li>When server-side copying the contents of the linked folder is copied, not the shortcut.</li>
<li>When deleting with <code>rclone rmdir</code> or <code>rclone purge</code> the shortcut is deleted not the linked folder.</li>
<li><strong>NB</strong> When deleting with <code>rclone remove</code> or <code>rclone mount</code> the contents of the linked folder will be deleted.</li>
</ul>
<p>The <a href="https://rclone.org/commands/rclone_backend/">rclone backend</a> command can be used to create shortcuts.</p>
<p>Shortcuts can be completely ignored with the <code>--drive-skip-shortcuts</code> flag or the corresponding <code>skip_shortcuts</code> configuration setting.</p>
<p>If you have shortcuts that lead to an infinite recursion in your drive (e.g. a shortcut pointing to a parent folder), <code>skip_shortcuts</code> might be mandatory to be able to copy the drive.</p>
<h3 id="emptying-trash">Emptying trash</h3>
<p>If you wish to empty your trash you can use the <code>rclone cleanup remote:</code> command which will permanently delete all your trashed files. This command does not take any path arguments.</p>
<p>Note that Google Drive takes some time (minutes to days) to empty the trash even though the command returns within a few seconds. No output is echoed, so there will be no confirmation even using -v or -vv.</p>
<h3 id="quota-information">Quota information</h3>
<p>To view your current quota you can use the <code>rclone about remote:</code> command which will display your usage limit (quota), the usage in Google Drive, the size of all files in the Trash and the space used by other Google services such as Gmail. This command does not take any path arguments.</p>
<h4 id="importexport-of-google-documents">Import/Export of google documents</h4>
<p>Google documents can be exported from and uploaded to Google Drive.</p>
<p>When rclone downloads a Google doc it chooses a format to download depending upon the <code>--drive-export-formats</code> setting. By default the export formats are <code>docx,xlsx,pptx,svg</code> which are a sensible default for an editable document.</p>
<p>When choosing a format, rclone runs down the list provided in order and chooses the first file format the doc can be exported as from the list. If the file can't be exported to a format on the formats list, then rclone will choose a format from the default list.</p>
<p>If you prefer an archive copy then you might use <code>--drive-export-formats pdf</code>, or if you prefer openoffice/libreoffice formats you might use <code>--drive-export-formats ods,odt,odp</code>.</p>
<p>Note that rclone adds the extension to the google doc, so if it is called <code>My Spreadsheet</code> on google docs, it will be exported as <code>My Spreadsheet.xlsx</code> or <code>My Spreadsheet.pdf</code> etc.</p>
<p>When importing files into Google Drive, rclone will convert all files with an extension in <code>--drive-import-formats</code> to their associated document type. rclone will not convert any files by default, since the conversion is lossy process.</p>
<p>The conversion must result in a file with the same extension when the <code>--drive-export-formats</code> rules are applied to the uploaded document.</p>
<p>Here are some examples for allowed and prohibited conversions.</p>
<table>
<thead>
<tr class="header">
<th>export-formats</th>
<th>import-formats</th>
<th>Upload Ext</th>
<th>Document Ext</th>
<th>Allowed</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td>odt</td>
<td>odt</td>
<td>odt</td>
<td>odt</td>
<td>Yes</td>
</tr>
<tr class="even">
<td>odt</td>
<td>docx,odt</td>
<td>odt</td>
<td>odt</td>
<td>Yes</td>
</tr>
<tr class="odd">
<td></td>
<td>docx</td>
<td>docx</td>
<td>docx</td>
<td>Yes</td>
</tr>
<tr class="even">
<td></td>
<td>odt</td>
<td>odt</td>
<td>docx</td>
<td>No</td>
</tr>
<tr class="odd">
<td>odt,docx</td>
<td>docx,odt</td>
<td>docx</td>
<td>odt</td>
<td>No</td>
</tr>
<tr class="even">
<td>docx,odt</td>
<td>docx,odt</td>
<td>docx</td>
<td>docx</td>
<td>Yes</td>
</tr>
<tr class="odd">
<td>docx,odt</td>
<td>docx,odt</td>
<td>odt</td>
<td>docx</td>
<td>No</td>
</tr>
</tbody>
</table>
<p>This limitation can be disabled by specifying <code>--drive-allow-import-name-change</code>. When using this flag, rclone can convert multiple files types resulting in the same document type at once, e.g. with <code>--drive-import-formats docx,odt,txt</code>, all files having these extension would result in a document represented as a docx file. This brings the additional risk of overwriting a document, if multiple files have the same stem. Many rclone operations will not handle this name change in any way. They assume an equal name when copying files and might copy the file again or delete them when the name changes.</p>
<p>Here are the possible export extensions with their corresponding mime types. Most of these can also be used for importing, but there more that are not listed here. Some of these additional ones might only be available when the operating system provides the correct MIME type entries.</p>
<p>This list can be changed by Google Drive at any time and might not represent the currently available conversions.</p>
<table>
<colgroup>
<col style="width: 28%" />
<col style="width: 34%" />
<col style="width: 37%" />
</colgroup>
<thead>
<tr class="header">
<th>Extension</th>
<th>Mime Type</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td>bmp</td>
<td>image/bmp</td>
<td>Windows Bitmap format</td>
</tr>
<tr class="even">
<td>csv</td>
<td>text/csv</td>
<td>Standard CSV format for Spreadsheets</td>
</tr>
<tr class="odd">
<td>doc</td>
<td>application/msword</td>
<td>Classic Word file</td>
</tr>
<tr class="even">
<td>docx</td>
<td>application/vnd.openxmlformats-officedocument.wordprocessingml.document</td>
<td>Microsoft Office Document</td>
</tr>
<tr class="odd">
<td>epub</td>
<td>application/epub+zip</td>
<td>E-book format</td>
</tr>
<tr class="even">
<td>html</td>
<td>text/html</td>
<td>An HTML Document</td>
</tr>
<tr class="odd">
<td>jpg</td>
<td>image/jpeg</td>
<td>A JPEG Image File</td>
</tr>
<tr class="even">
<td>json</td>
<td>application/vnd.google-apps.script+json</td>
<td>JSON Text Format for Google Apps scripts</td>
</tr>
<tr class="odd">
<td>odp</td>
<td>application/vnd.oasis.opendocument.presentation</td>
<td>Openoffice Presentation</td>
</tr>
<tr class="even">
<td>ods</td>
<td>application/vnd.oasis.opendocument.spreadsheet</td>
<td>Openoffice Spreadsheet</td>
</tr>
<tr class="odd">
<td>ods</td>
<td>application/x-vnd.oasis.opendocument.spreadsheet</td>
<td>Openoffice Spreadsheet</td>
</tr>
<tr class="even">
<td>odt</td>
<td>application/vnd.oasis.opendocument.text</td>
<td>Openoffice Document</td>
</tr>
<tr class="odd">
<td>pdf</td>
<td>application/pdf</td>
<td>Adobe PDF Format</td>
</tr>
<tr class="even">
<td>pjpeg</td>
<td>image/pjpeg</td>
<td>Progressive JPEG Image</td>
</tr>
<tr class="odd">
<td>png</td>
<td>image/png</td>
<td>PNG Image Format</td>
</tr>
<tr class="even">
<td>pptx</td>
<td>application/vnd.openxmlformats-officedocument.presentationml.presentation</td>
<td>Microsoft Office Powerpoint</td>
</tr>
<tr class="odd">
<td>rtf</td>
<td>application/rtf</td>
<td>Rich Text Format</td>
</tr>
<tr class="even">
<td>svg</td>
<td>image/svg+xml</td>
<td>Scalable Vector Graphics Format</td>
</tr>
<tr class="odd">
<td>tsv</td>
<td>text/tab-separated-values</td>
<td>Standard TSV format for spreadsheets</td>
</tr>
<tr class="even">
<td>txt</td>
<td>text/plain</td>
<td>Plain Text</td>
</tr>
<tr class="odd">
<td>wmf</td>
<td>application/x-msmetafile</td>
<td>Windows Meta File</td>
</tr>
<tr class="even">
<td>xls</td>
<td>application/vnd.ms-excel</td>
<td>Classic Excel file</td>
</tr>
<tr class="odd">
<td>xlsx</td>
<td>application/vnd.openxmlformats-officedocument.spreadsheetml.sheet</td>
<td>Microsoft Office Spreadsheet</td>
</tr>
<tr class="even">
<td>zip</td>
<td>application/zip</td>
<td>A ZIP file of HTML, Images CSS</td>
</tr>
</tbody>
</table>
<p>Google documents can also be exported as link files. These files will open a browser window for the Google Docs website of that document when opened. The link file extension has to be specified as a <code>--drive-export-formats</code> parameter. They will match all available Google Documents.</p>
<table>
<thead>
<tr class="header">
<th>Extension</th>
<th>Description</th>
<th>OS Support</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td>desktop</td>
<td>freedesktop.org specified desktop entry</td>
<td>Linux</td>
</tr>
<tr class="even">
<td>link.html</td>
<td>An HTML Document with a redirect</td>
<td>All</td>
</tr>
<tr class="odd">
<td>url</td>
<td>INI style link file</td>
<td>macOS, Windows</td>
</tr>
<tr class="even">
<td>webloc</td>
<td>macOS specific XML format</td>
<td>macOS</td>
</tr>
</tbody>
</table>
<h3 id="standard-options-17">Standard options</h3>
<p>Here are the Standard options specific to drive (Google Drive).</p>
<h4 id="drive-client-id">--drive-client-id</h4>
<p>Google Application Client Id Setting your own is recommended. See https://rclone.org/drive/#making-your-own-client-id for how to create your own. If you leave this blank, it will use an internal key which is low performance.</p>
<p>Properties:</p>
<ul>
<li>Config: client_id</li>
<li>Env Var: RCLONE_DRIVE_CLIENT_ID</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="drive-client-secret">--drive-client-secret</h4>
<p>OAuth Client Secret.</p>
<p>Leave blank normally.</p>
<p>Properties:</p>
<ul>
<li>Config: client_secret</li>
<li>Env Var: RCLONE_DRIVE_CLIENT_SECRET</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="drive-scope">--drive-scope</h4>
<p>Comma separated list of scopes that rclone should use when requesting access from drive.</p>
<p>Properties:</p>
<ul>
<li>Config: scope</li>
<li>Env Var: RCLONE_DRIVE_SCOPE</li>
<li>Type: string</li>
<li>Required: false</li>
<li>Examples:
<ul>
<li>"drive"
<ul>
<li>Full access all files, excluding Application Data Folder.</li>
</ul></li>
<li>"drive.readonly"
<ul>
<li>Read-only access to file metadata and file contents.</li>
</ul></li>
<li>"drive.file"
<ul>
<li>Access to files created by rclone only.</li>
<li>These are visible in the drive website.</li>
<li>File authorization is revoked when the user deauthorizes the app.</li>
</ul></li>
<li>"drive.appfolder"
<ul>
<li>Allows read and write access to the Application Data folder.</li>
<li>This is not visible in the drive website.</li>
</ul></li>
<li>"drive.metadata.readonly"
<ul>
<li>Allows read-only access to file metadata but</li>
<li>does not allow any access to read or download file content.</li>
</ul></li>
</ul></li>
</ul>
<h4 id="drive-service-account-file">--drive-service-account-file</h4>
<p>Service Account Credentials JSON file path.</p>
<p>Leave blank normally. Needed only if you want use SA instead of interactive login.</p>
<p>Leading <code>~</code> will be expanded in the file name as will environment variables such as <code>${RCLONE_CONFIG_DIR}</code>.</p>
<p>Properties:</p>
<ul>
<li>Config: service_account_file</li>
<li>Env Var: RCLONE_DRIVE_SERVICE_ACCOUNT_FILE</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="drive-alternate-export">--drive-alternate-export</h4>
<p>Deprecated: No longer needed.</p>
<p>Properties:</p>
<ul>
<li>Config: alternate_export</li>
<li>Env Var: RCLONE_DRIVE_ALTERNATE_EXPORT</li>
<li>Type: bool</li>
<li>Default: false</li>
</ul>
<h3 id="advanced-options-17">Advanced options</h3>
<p>Here are the Advanced options specific to drive (Google Drive).</p>
<h4 id="drive-token">--drive-token</h4>
<p>OAuth Access Token as a JSON blob.</p>
<p>Properties:</p>
<ul>
<li>Config: token</li>
<li>Env Var: RCLONE_DRIVE_TOKEN</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="drive-auth-url">--drive-auth-url</h4>
<p>Auth server URL.</p>
<p>Leave blank to use the provider defaults.</p>
<p>Properties:</p>
<ul>
<li>Config: auth_url</li>
<li>Env Var: RCLONE_DRIVE_AUTH_URL</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="drive-token-url">--drive-token-url</h4>
<p>Token server url.</p>
<p>Leave blank to use the provider defaults.</p>
<p>Properties:</p>
<ul>
<li>Config: token_url</li>
<li>Env Var: RCLONE_DRIVE_TOKEN_URL</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="drive-root-folder-id">--drive-root-folder-id</h4>
<p>ID of the root folder. Leave blank normally.</p>
<p>Fill in to access "Computers" folders (see docs), or for rclone to use a non root folder as its starting point.</p>
<p>Properties:</p>
<ul>
<li>Config: root_folder_id</li>
<li>Env Var: RCLONE_DRIVE_ROOT_FOLDER_ID</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="drive-service-account-credentials">--drive-service-account-credentials</h4>
<p>Service Account Credentials JSON blob.</p>
<p>Leave blank normally. Needed only if you want use SA instead of interactive login.</p>
<p>Properties:</p>
<ul>
<li>Config: service_account_credentials</li>
<li>Env Var: RCLONE_DRIVE_SERVICE_ACCOUNT_CREDENTIALS</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="drive-team-drive">--drive-team-drive</h4>
<p>ID of the Shared Drive (Team Drive).</p>
<p>Properties:</p>
<ul>
<li>Config: team_drive</li>
<li>Env Var: RCLONE_DRIVE_TEAM_DRIVE</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="drive-auth-owner-only">--drive-auth-owner-only</h4>
<p>Only consider files owned by the authenticated user.</p>
<p>Properties:</p>
<ul>
<li>Config: auth_owner_only</li>
<li>Env Var: RCLONE_DRIVE_AUTH_OWNER_ONLY</li>
<li>Type: bool</li>
<li>Default: false</li>
</ul>
<h4 id="drive-use-trash">--drive-use-trash</h4>
<p>Send files to the trash instead of deleting permanently.</p>
<p>Defaults to true, namely sending files to the trash. Use <code>--drive-use-trash=false</code> to delete files permanently instead.</p>
<p>Properties:</p>
<ul>
<li>Config: use_trash</li>
<li>Env Var: RCLONE_DRIVE_USE_TRASH</li>
<li>Type: bool</li>
<li>Default: true</li>
</ul>
<h4 id="drive-copy-shortcut-content">--drive-copy-shortcut-content</h4>
<p>Server side copy contents of shortcuts instead of the shortcut.</p>
<p>When doing server side copies, normally rclone will copy shortcuts as shortcuts.</p>
<p>If this flag is used then rclone will copy the contents of shortcuts rather than shortcuts themselves when doing server side copies.</p>
<p>Properties:</p>
<ul>
<li>Config: copy_shortcut_content</li>
<li>Env Var: RCLONE_DRIVE_COPY_SHORTCUT_CONTENT</li>
<li>Type: bool</li>
<li>Default: false</li>
</ul>
<h4 id="drive-skip-gdocs">--drive-skip-gdocs</h4>
<p>Skip google documents in all listings.</p>
<p>If given, gdocs practically become invisible to rclone.</p>
<p>Properties:</p>
<ul>
<li>Config: skip_gdocs</li>
<li>Env Var: RCLONE_DRIVE_SKIP_GDOCS</li>
<li>Type: bool</li>
<li>Default: false</li>
</ul>
<h4 id="drive-show-all-gdocs">--drive-show-all-gdocs</h4>
<p>Show all Google Docs including non-exportable ones in listings.</p>
<p>If you try a server side copy on a Google Form without this flag, you will get this error:</p>
<pre><code>No export formats found for &quot;application/vnd.google-apps.form&quot;</code></pre>
<p>However adding this flag will allow the form to be server side copied.</p>
<p>Note that rclone doesn't add extensions to the Google Docs file names in this mode.</p>
<p>Do <strong>not</strong> use this flag when trying to download Google Docs - rclone will fail to download them.</p>
<p>Properties:</p>
<ul>
<li>Config: show_all_gdocs</li>
<li>Env Var: RCLONE_DRIVE_SHOW_ALL_GDOCS</li>
<li>Type: bool</li>
<li>Default: false</li>
</ul>
<h4 id="drive-skip-checksum-gphotos">--drive-skip-checksum-gphotos</h4>
<p>Skip checksums on Google photos and videos only.</p>
<p>Use this if you get checksum errors when transferring Google photos or videos.</p>
<p>Setting this flag will cause Google photos and videos to return a blank checksums.</p>
<p>Google photos are identified by being in the "photos" space.</p>
<p>Corrupted checksums are caused by Google modifying the image/video but not updating the checksum.</p>
<p>Properties:</p>
<ul>
<li>Config: skip_checksum_gphotos</li>
<li>Env Var: RCLONE_DRIVE_SKIP_CHECKSUM_GPHOTOS</li>
<li>Type: bool</li>
<li>Default: false</li>
</ul>
<h4 id="drive-shared-with-me">--drive-shared-with-me</h4>
<p>Only show files that are shared with me.</p>
<p>Instructs rclone to operate on your "Shared with me" folder (where Google Drive lets you access the files and folders others have shared with you).</p>
<p>This works both with the "list" (lsd, lsl, etc.) and the "copy" commands (copy, sync, etc.), and with all other commands too.</p>
<p>Properties:</p>
<ul>
<li>Config: shared_with_me</li>
<li>Env Var: RCLONE_DRIVE_SHARED_WITH_ME</li>
<li>Type: bool</li>
<li>Default: false</li>
</ul>
<h4 id="drive-trashed-only">--drive-trashed-only</h4>
<p>Only show files that are in the trash.</p>
<p>This will show trashed files in their original directory structure.</p>
<p>Properties:</p>
<ul>
<li>Config: trashed_only</li>
<li>Env Var: RCLONE_DRIVE_TRASHED_ONLY</li>
<li>Type: bool</li>
<li>Default: false</li>
</ul>
<h4 id="drive-starred-only">--drive-starred-only</h4>
<p>Only show files that are starred.</p>
<p>Properties:</p>
<ul>
<li>Config: starred_only</li>
<li>Env Var: RCLONE_DRIVE_STARRED_ONLY</li>
<li>Type: bool</li>
<li>Default: false</li>
</ul>
<h4 id="drive-formats">--drive-formats</h4>
<p>Deprecated: See export_formats.</p>
<p>Properties:</p>
<ul>
<li>Config: formats</li>
<li>Env Var: RCLONE_DRIVE_FORMATS</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="drive-export-formats">--drive-export-formats</h4>
<p>Comma separated list of preferred formats for downloading Google docs.</p>
<p>Properties:</p>
<ul>
<li>Config: export_formats</li>
<li>Env Var: RCLONE_DRIVE_EXPORT_FORMATS</li>
<li>Type: string</li>
<li>Default: "docx,xlsx,pptx,svg"</li>
</ul>
<h4 id="drive-import-formats">--drive-import-formats</h4>
<p>Comma separated list of preferred formats for uploading Google docs.</p>
<p>Properties:</p>
<ul>
<li>Config: import_formats</li>
<li>Env Var: RCLONE_DRIVE_IMPORT_FORMATS</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="drive-allow-import-name-change">--drive-allow-import-name-change</h4>
<p>Allow the filetype to change when uploading Google docs.</p>
<p>E.g. file.doc to file.docx. This will confuse sync and reupload every time.</p>
<p>Properties:</p>
<ul>
<li>Config: allow_import_name_change</li>
<li>Env Var: RCLONE_DRIVE_ALLOW_IMPORT_NAME_CHANGE</li>
<li>Type: bool</li>
<li>Default: false</li>
</ul>
<h4 id="drive-use-created-date">--drive-use-created-date</h4>
<p>Use file created date instead of modified date.</p>
<p>Useful when downloading data and you want the creation date used in place of the last modified date.</p>
<p><strong>WARNING</strong>: This flag may have some unexpected consequences.</p>
<p>When uploading to your drive all files will be overwritten unless they haven't been modified since their creation. And the inverse will occur while downloading. This side effect can be avoided by using the "--checksum" flag.</p>
<p>This feature was implemented to retain photos capture date as recorded by google photos. You will first need to check the "Create a Google Photos folder" option in your google drive settings. You can then copy or move the photos locally and use the date the image was taken (created) set as the modification date.</p>
<p>Properties:</p>
<ul>
<li>Config: use_created_date</li>
<li>Env Var: RCLONE_DRIVE_USE_CREATED_DATE</li>
<li>Type: bool</li>
<li>Default: false</li>
</ul>
<h4 id="drive-use-shared-date">--drive-use-shared-date</h4>
<p>Use date file was shared instead of modified date.</p>
<p>Note that, as with "--drive-use-created-date", this flag may have unexpected consequences when uploading/downloading files.</p>
<p>If both this flag and "--drive-use-created-date" are set, the created date is used.</p>
<p>Properties:</p>
<ul>
<li>Config: use_shared_date</li>
<li>Env Var: RCLONE_DRIVE_USE_SHARED_DATE</li>
<li>Type: bool</li>
<li>Default: false</li>
</ul>
<h4 id="drive-list-chunk">--drive-list-chunk</h4>
<p>Size of listing chunk 100-1000, 0 to disable.</p>
<p>Properties:</p>
<ul>
<li>Config: list_chunk</li>
<li>Env Var: RCLONE_DRIVE_LIST_CHUNK</li>
<li>Type: int</li>
<li>Default: 1000</li>
</ul>
<h4 id="drive-impersonate">--drive-impersonate</h4>
<p>Impersonate this user when using a service account.</p>
<p>Properties:</p>
<ul>
<li>Config: impersonate</li>
<li>Env Var: RCLONE_DRIVE_IMPERSONATE</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="drive-upload-cutoff">--drive-upload-cutoff</h4>
<p>Cutoff for switching to chunked upload.</p>
<p>Properties:</p>
<ul>
<li>Config: upload_cutoff</li>
<li>Env Var: RCLONE_DRIVE_UPLOAD_CUTOFF</li>
<li>Type: SizeSuffix</li>
<li>Default: 8Mi</li>
</ul>
<h4 id="drive-chunk-size">--drive-chunk-size</h4>
<p>Upload chunk size.</p>
<p>Must a power of 2 &gt;= 256k.</p>
<p>Making this larger will improve performance, but note that each chunk is buffered in memory one per transfer.</p>
<p>Reducing this will reduce memory usage but decrease performance.</p>
<p>Properties:</p>
<ul>
<li>Config: chunk_size</li>
<li>Env Var: RCLONE_DRIVE_CHUNK_SIZE</li>
<li>Type: SizeSuffix</li>
<li>Default: 8Mi</li>
</ul>
<h4 id="drive-acknowledge-abuse">--drive-acknowledge-abuse</h4>
<p>Set to allow files which return cannotDownloadAbusiveFile to be downloaded.</p>
<p>If downloading a file returns the error "This file has been identified as malware or spam and cannot be downloaded" with the error code "cannotDownloadAbusiveFile" then supply this flag to rclone to indicate you acknowledge the risks of downloading the file and rclone will download it anyway.</p>
<p>Note that if you are using service account it will need Manager permission (not Content Manager) to for this flag to work. If the SA does not have the right permission, Google will just ignore the flag.</p>
<p>Properties:</p>
<ul>
<li>Config: acknowledge_abuse</li>
<li>Env Var: RCLONE_DRIVE_ACKNOWLEDGE_ABUSE</li>
<li>Type: bool</li>
<li>Default: false</li>
</ul>
<h4 id="drive-keep-revision-forever">--drive-keep-revision-forever</h4>
<p>Keep new head revision of each file forever.</p>
<p>Properties:</p>
<ul>
<li>Config: keep_revision_forever</li>
<li>Env Var: RCLONE_DRIVE_KEEP_REVISION_FOREVER</li>
<li>Type: bool</li>
<li>Default: false</li>
</ul>
<h4 id="drive-size-as-quota">--drive-size-as-quota</h4>
<p>Show sizes as storage quota usage, not actual size.</p>
<p>Show the size of a file as the storage quota used. This is the current version plus any older versions that have been set to keep forever.</p>
<p><strong>WARNING</strong>: This flag may have some unexpected consequences.</p>
<p>It is not recommended to set this flag in your config - the recommended usage is using the flag form --drive-size-as-quota when doing rclone ls/lsl/lsf/lsjson/etc only.</p>
<p>If you do use this flag for syncing (not recommended) then you will need to use --ignore size also.</p>
<p>Properties:</p>
<ul>
<li>Config: size_as_quota</li>
<li>Env Var: RCLONE_DRIVE_SIZE_AS_QUOTA</li>
<li>Type: bool</li>
<li>Default: false</li>
</ul>
<h4 id="drive-v2-download-min-size">--drive-v2-download-min-size</h4>
<p>If Object's are greater, use drive v2 API to download.</p>
<p>Properties:</p>
<ul>
<li>Config: v2_download_min_size</li>
<li>Env Var: RCLONE_DRIVE_V2_DOWNLOAD_MIN_SIZE</li>
<li>Type: SizeSuffix</li>
<li>Default: off</li>
</ul>
<h4 id="drive-pacer-min-sleep">--drive-pacer-min-sleep</h4>
<p>Minimum time to sleep between API calls.</p>
<p>Properties:</p>
<ul>
<li>Config: pacer_min_sleep</li>
<li>Env Var: RCLONE_DRIVE_PACER_MIN_SLEEP</li>
<li>Type: Duration</li>
<li>Default: 100ms</li>
</ul>
<h4 id="drive-pacer-burst">--drive-pacer-burst</h4>
<p>Number of API calls to allow without sleeping.</p>
<p>Properties:</p>
<ul>
<li>Config: pacer_burst</li>
<li>Env Var: RCLONE_DRIVE_PACER_BURST</li>
<li>Type: int</li>
<li>Default: 100</li>
</ul>
<h4 id="drive-server-side-across-configs">--drive-server-side-across-configs</h4>
<p>Deprecated: use --server-side-across-configs instead.</p>
<p>Allow server-side operations (e.g. copy) to work across different drive configs.</p>
<p>This can be useful if you wish to do a server-side copy between two different Google drives. Note that this isn't enabled by default because it isn't easy to tell if it will work between any two configurations.</p>
<p>Properties:</p>
<ul>
<li>Config: server_side_across_configs</li>
<li>Env Var: RCLONE_DRIVE_SERVER_SIDE_ACROSS_CONFIGS</li>
<li>Type: bool</li>
<li>Default: false</li>
</ul>
<h4 id="drive-disable-http2">--drive-disable-http2</h4>
<p>Disable drive using http2.</p>
<p>There is currently an unsolved issue with the google drive backend and HTTP/2. HTTP/2 is therefore disabled by default for the drive backend but can be re-enabled here. When the issue is solved this flag will be removed.</p>
<p>See: https://github.com/rclone/rclone/issues/3631</p>
<p>Properties:</p>
<ul>
<li>Config: disable_http2</li>
<li>Env Var: RCLONE_DRIVE_DISABLE_HTTP2</li>
<li>Type: bool</li>
<li>Default: true</li>
</ul>
<h4 id="drive-stop-on-upload-limit">--drive-stop-on-upload-limit</h4>
<p>Make upload limit errors be fatal.</p>
<p>At the time of writing it is only possible to upload 750 GiB of data to Google Drive a day (this is an undocumented limit). When this limit is reached Google Drive produces a slightly different error message. When this flag is set it causes these errors to be fatal. These will stop the in-progress sync.</p>
<p>Note that this detection is relying on error message strings which Google don't document so it may break in the future.</p>
<p>See: https://github.com/rclone/rclone/issues/3857</p>
<p>Properties:</p>
<ul>
<li>Config: stop_on_upload_limit</li>
<li>Env Var: RCLONE_DRIVE_STOP_ON_UPLOAD_LIMIT</li>
<li>Type: bool</li>
<li>Default: false</li>
</ul>
<h4 id="drive-stop-on-download-limit">--drive-stop-on-download-limit</h4>
<p>Make download limit errors be fatal.</p>
<p>At the time of writing it is only possible to download 10 TiB of data from Google Drive a day (this is an undocumented limit). When this limit is reached Google Drive produces a slightly different error message. When this flag is set it causes these errors to be fatal. These will stop the in-progress sync.</p>
<p>Note that this detection is relying on error message strings which Google don't document so it may break in the future.</p>
<p>Properties:</p>
<ul>
<li>Config: stop_on_download_limit</li>
<li>Env Var: RCLONE_DRIVE_STOP_ON_DOWNLOAD_LIMIT</li>
<li>Type: bool</li>
<li>Default: false</li>
</ul>
<h4 id="drive-skip-shortcuts">--drive-skip-shortcuts</h4>
<p>If set skip shortcut files.</p>
<p>Normally rclone dereferences shortcut files making them appear as if they are the original file (see <a href="#shortcuts">the shortcuts section</a>). If this flag is set then rclone will ignore shortcut files completely.</p>
<p>Properties:</p>
<ul>
<li>Config: skip_shortcuts</li>
<li>Env Var: RCLONE_DRIVE_SKIP_SHORTCUTS</li>
<li>Type: bool</li>
<li>Default: false</li>
</ul>
<h4 id="drive-skip-dangling-shortcuts">--drive-skip-dangling-shortcuts</h4>
<p>If set skip dangling shortcut files.</p>
<p>If this is set then rclone will not show any dangling shortcuts in listings.</p>
<p>Properties:</p>
<ul>
<li>Config: skip_dangling_shortcuts</li>
<li>Env Var: RCLONE_DRIVE_SKIP_DANGLING_SHORTCUTS</li>
<li>Type: bool</li>
<li>Default: false</li>
</ul>
<h4 id="drive-resource-key">--drive-resource-key</h4>
<p>Resource key for accessing a link-shared file.</p>
<p>If you need to access files shared with a link like this</p>
<pre><code>https://drive.google.com/drive/folders/XXX?resourcekey=YYY&amp;usp=sharing</code></pre>
<p>Then you will need to use the first part "XXX" as the "root_folder_id" and the second part "YYY" as the "resource_key" otherwise you will get 404 not found errors when trying to access the directory.</p>
<p>See: https://developers.google.com/drive/api/guides/resource-keys</p>
<p>This resource key requirement only applies to a subset of old files.</p>
<p>Note also that opening the folder once in the web interface (with the user you've authenticated rclone with) seems to be enough so that the resource key is not needed.</p>
<p>Properties:</p>
<ul>
<li>Config: resource_key</li>
<li>Env Var: RCLONE_DRIVE_RESOURCE_KEY</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="drive-fast-list-bug-fix">--drive-fast-list-bug-fix</h4>
<p>Work around a bug in Google Drive listing.</p>
<p>Normally rclone will work around a bug in Google Drive when using --fast-list (ListR) where the search "(A in parents) or (B in parents)" returns nothing sometimes. See #3114, #4289 and https://issuetracker.google.com/issues/149522397</p>
<p>Rclone detects this by finding no items in more than one directory when listing and retries them as lists of individual directories.</p>
<p>This means that if you have a lot of empty directories rclone will end up listing them all individually and this can take many more API calls.</p>
<p>This flag allows the work-around to be disabled. This is <strong>not</strong> recommended in normal use - only if you have a particular case you are having trouble with like many empty directories.</p>
<p>Properties:</p>
<ul>
<li>Config: fast_list_bug_fix</li>
<li>Env Var: RCLONE_DRIVE_FAST_LIST_BUG_FIX</li>
<li>Type: bool</li>
<li>Default: true</li>
</ul>
<h4 id="drive-metadata-owner">--drive-metadata-owner</h4>
<p>Control whether owner should be read or written in metadata.</p>
<p>Owner is a standard part of the file metadata so is easy to read. But it isn't always desirable to set the owner from the metadata.</p>
<p>Note that you can't set the owner on Shared Drives, and that setting ownership will generate an email to the new owner (this can't be disabled), and you can't transfer ownership to someone outside your organization.</p>
<p>Properties:</p>
<ul>
<li>Config: metadata_owner</li>
<li>Env Var: RCLONE_DRIVE_METADATA_OWNER</li>
<li>Type: Bits</li>
<li>Default: read</li>
<li>Examples:
<ul>
<li>"off"
<ul>
<li>Do not read or write the value</li>
</ul></li>
<li>"read"
<ul>
<li>Read the value only</li>
</ul></li>
<li>"write"
<ul>
<li>Write the value only</li>
</ul></li>
<li>"failok"
<ul>
<li>If writing fails log errors only, don't fail the transfer</li>
</ul></li>
<li>"read,write"
<ul>
<li>Read and Write the value.</li>
</ul></li>
</ul></li>
</ul>
<h4 id="drive-metadata-permissions">--drive-metadata-permissions</h4>
<p>Control whether permissions should be read or written in metadata.</p>
<p>Reading permissions metadata from files can be done quickly, but it isn't always desirable to set the permissions from the metadata.</p>
<p>Note that rclone drops any inherited permissions on Shared Drives and any owner permission on My Drives as these are duplicated in the owner metadata.</p>
<p>Properties:</p>
<ul>
<li>Config: metadata_permissions</li>
<li>Env Var: RCLONE_DRIVE_METADATA_PERMISSIONS</li>
<li>Type: Bits</li>
<li>Default: off</li>
<li>Examples:
<ul>
<li>"off"
<ul>
<li>Do not read or write the value</li>
</ul></li>
<li>"read"
<ul>
<li>Read the value only</li>
</ul></li>
<li>"write"
<ul>
<li>Write the value only</li>
</ul></li>
<li>"failok"
<ul>
<li>If writing fails log errors only, don't fail the transfer</li>
</ul></li>
<li>"read,write"
<ul>
<li>Read and Write the value.</li>
</ul></li>
</ul></li>
</ul>
<h4 id="drive-metadata-labels">--drive-metadata-labels</h4>
<p>Control whether labels should be read or written in metadata.</p>
<p>Reading labels metadata from files takes an extra API transaction and will slow down listings. It isn't always desirable to set the labels from the metadata.</p>
<p>The format of labels is documented in the drive API documentation at https://developers.google.com/drive/api/reference/rest/v3/Label - rclone just provides a JSON dump of this format.</p>
<p>When setting labels, the label and fields must already exist - rclone will not create them. This means that if you are transferring labels from two different accounts you will have to create the labels in advance and use the metadata mapper to translate the IDs between the two accounts.</p>
<p>Properties:</p>
<ul>
<li>Config: metadata_labels</li>
<li>Env Var: RCLONE_DRIVE_METADATA_LABELS</li>
<li>Type: Bits</li>
<li>Default: off</li>
<li>Examples:
<ul>
<li>"off"
<ul>
<li>Do not read or write the value</li>
</ul></li>
<li>"read"
<ul>
<li>Read the value only</li>
</ul></li>
<li>"write"
<ul>
<li>Write the value only</li>
</ul></li>
<li>"failok"
<ul>
<li>If writing fails log errors only, don't fail the transfer</li>
</ul></li>
<li>"read,write"
<ul>
<li>Read and Write the value.</li>
</ul></li>
</ul></li>
</ul>
<h4 id="drive-encoding">--drive-encoding</h4>
<p>The encoding for the backend.</p>
<p>See the <a href="https://rclone.org/overview/#encoding">encoding section in the overview</a> for more info.</p>
<p>Properties:</p>
<ul>
<li>Config: encoding</li>
<li>Env Var: RCLONE_DRIVE_ENCODING</li>
<li>Type: Encoding</li>
<li>Default: InvalidUtf8</li>
</ul>
<h4 id="drive-env-auth">--drive-env-auth</h4>
<p>Get IAM credentials from runtime (environment variables or instance meta data if no env vars).</p>
<p>Only applies if service_account_file and service_account_credentials is blank.</p>
<p>Properties:</p>
<ul>
<li>Config: env_auth</li>
<li>Env Var: RCLONE_DRIVE_ENV_AUTH</li>
<li>Type: bool</li>
<li>Default: false</li>
<li>Examples:
<ul>
<li>"false"
<ul>
<li>Enter credentials in the next step.</li>
</ul></li>
<li>"true"
<ul>
<li>Get GCP IAM credentials from the environment (env vars or IAM).</li>
</ul></li>
</ul></li>
</ul>
<h4 id="drive-description">--drive-description</h4>
<p>Description of the remote.</p>
<p>Properties:</p>
<ul>
<li>Config: description</li>
<li>Env Var: RCLONE_DRIVE_DESCRIPTION</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h3 id="metadata-8">Metadata</h3>
<p>User metadata is stored in the properties field of the drive object.</p>
<p>Metadata is supported on files and directories.</p>
<p>Here are the possible system metadata items for the drive backend.</p>
<table>
<colgroup>
<col style="width: 15%" />
<col style="width: 15%" />
<col style="width: 15%" />
<col style="width: 23%" />
<col style="width: 28%" />
</colgroup>
<thead>
<tr class="header">
<th>Name</th>
<th>Help</th>
<th>Type</th>
<th>Example</th>
<th>Read Only</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td>btime</td>
<td>Time of file birth (creation) with mS accuracy. Note that this is only writable on fresh uploads - it can't be written for updates.</td>
<td>RFC 3339</td>
<td>2006-01-02T15:04:05.999Z07:00</td>
<td>N</td>
</tr>
<tr class="even">
<td>content-type</td>
<td>The MIME type of the file.</td>
<td>string</td>
<td>text/plain</td>
<td>N</td>
</tr>
<tr class="odd">
<td>copy-requires-writer-permission</td>
<td>Whether the options to copy, print, or download this file, should be disabled for readers and commenters.</td>
<td>boolean</td>
<td>true</td>
<td>N</td>
</tr>
<tr class="even">
<td>description</td>
<td>A short description of the file.</td>
<td>string</td>
<td>Contract for signing</td>
<td>N</td>
</tr>
<tr class="odd">
<td>folder-color-rgb</td>
<td>The color for a folder or a shortcut to a folder as an RGB hex string.</td>
<td>string</td>
<td>881133</td>
<td>N</td>
</tr>
<tr class="even">
<td>labels</td>
<td>Labels attached to this file in a JSON dump of Googled drive format. Enable with --drive-metadata-labels.</td>
<td>JSON</td>
<td>[]</td>
<td>N</td>
</tr>
<tr class="odd">
<td>mtime</td>
<td>Time of last modification with mS accuracy.</td>
<td>RFC 3339</td>
<td>2006-01-02T15:04:05.999Z07:00</td>
<td>N</td>
</tr>
<tr class="even">
<td>owner</td>
<td>The owner of the file. Usually an email address. Enable with --drive-metadata-owner.</td>
<td>string</td>
<td>user@example.com</td>
<td>N</td>
</tr>
<tr class="odd">
<td>permissions</td>
<td>Permissions in a JSON dump of Google drive format. On shared drives these will only be present if they aren't inherited. Enable with --drive-metadata-permissions.</td>
<td>JSON</td>
<td>{}</td>
<td>N</td>
</tr>
<tr class="even">
<td>starred</td>
<td>Whether the user has starred the file.</td>
<td>boolean</td>
<td>false</td>
<td>N</td>
</tr>
<tr class="odd">
<td>viewed-by-me</td>
<td>Whether the file has been viewed by this user.</td>
<td>boolean</td>
<td>true</td>
<td><strong>Y</strong></td>
</tr>
<tr class="even">
<td>writers-can-share</td>
<td>Whether users with only writer permission can modify the file's permissions. Not populated and ignored when setting for items in shared drives.</td>
<td>boolean</td>
<td>false</td>
<td>N</td>
</tr>
</tbody>
</table>
<p>See the <a href="https://rclone.org/docs/#metadata">metadata</a> docs for more info.</p>
<h2 id="backend-commands-4">Backend commands</h2>
<p>Here are the commands specific to the drive backend.</p>
<p>Run them with</p>
<pre><code>rclone backend COMMAND remote:</code></pre>
<p>The help below will explain what arguments each command takes.</p>
<p>See the <a href="https://rclone.org/commands/rclone_backend/">backend</a> command for more info on how to pass options and arguments.</p>
<p>These can be run on a running backend using the rc command <a href="https://rclone.org/rc/#backend-command">backend/command</a>.</p>
<h3 id="get">get</h3>
<p>Get command for fetching the drive config parameters</p>
<pre><code>rclone backend get remote: [options] [&lt;arguments&gt;+]</code></pre>
<p>This is a get command which will be used to fetch the various drive config parameters</p>
<p>Usage Examples:</p>
<pre><code>rclone backend get drive: [-o service_account_file] [-o chunk_size]
rclone rc backend/command command=get fs=drive: [-o service_account_file] [-o chunk_size]</code></pre>
<p>Options:</p>
<ul>
<li>"chunk_size": show the current upload chunk size</li>
<li>"service_account_file": show the current service account file</li>
</ul>
<h3 id="set-1">set</h3>
<p>Set command for updating the drive config parameters</p>
<pre><code>rclone backend set remote: [options] [&lt;arguments&gt;+]</code></pre>
<p>This is a set command which will be used to update the various drive config parameters</p>
<p>Usage Examples:</p>
<pre><code>rclone backend set drive: [-o service_account_file=sa.json] [-o chunk_size=67108864]
rclone rc backend/command command=set fs=drive: [-o service_account_file=sa.json] [-o chunk_size=67108864]</code></pre>
<p>Options:</p>
<ul>
<li>"chunk_size": update the current upload chunk size</li>
<li>"service_account_file": update the current service account file</li>
</ul>
<h3 id="shortcut">shortcut</h3>
<p>Create shortcuts from files or directories</p>
<pre><code>rclone backend shortcut remote: [options] [&lt;arguments&gt;+]</code></pre>
<p>This command creates shortcuts from files or directories.</p>
<p>Usage:</p>
<pre><code>rclone backend shortcut drive: source_item destination_shortcut
rclone backend shortcut drive: source_item -o target=drive2: destination_shortcut</code></pre>
<p>In the first example this creates a shortcut from the "source_item" which can be a file or a directory to the "destination_shortcut". The "source_item" and the "destination_shortcut" should be relative paths from "drive:"</p>
<p>In the second example this creates a shortcut from the "source_item" relative to "drive:" to the "destination_shortcut" relative to "drive2:". This may fail with a permission error if the user authenticated with "drive2:" can't read files from "drive:".</p>
<p>Options:</p>
<ul>
<li>"target": optional target remote for the shortcut destination</li>
</ul>
<h3 id="drives">drives</h3>
<p>List the Shared Drives available to this account</p>
<pre><code>rclone backend drives remote: [options] [&lt;arguments&gt;+]</code></pre>
<p>This command lists the Shared Drives (Team Drives) available to this account.</p>
<p>Usage:</p>
<pre><code>rclone backend [-o config] drives drive:</code></pre>
<p>This will return a JSON list of objects like this</p>
<pre><code>[
    {
        &quot;id&quot;: &quot;0ABCDEF-01234567890&quot;,
        &quot;kind&quot;: &quot;drive#teamDrive&quot;,
        &quot;name&quot;: &quot;My Drive&quot;
    },
    {
        &quot;id&quot;: &quot;0ABCDEFabcdefghijkl&quot;,
        &quot;kind&quot;: &quot;drive#teamDrive&quot;,
        &quot;name&quot;: &quot;Test Drive&quot;
    }
]</code></pre>
<p>With the -o config parameter it will output the list in a format suitable for adding to a config file to make aliases for all the drives found and a combined drive.</p>
<pre><code>[My Drive]
type = alias
remote = drive,team_drive=0ABCDEF-01234567890,root_folder_id=:

[Test Drive]
type = alias
remote = drive,team_drive=0ABCDEFabcdefghijkl,root_folder_id=:

[AllDrives]
type = combine
upstreams = &quot;My Drive=My Drive:&quot; &quot;Test Drive=Test Drive:&quot;</code></pre>
<p>Adding this to the rclone config file will cause those team drives to be accessible with the aliases shown. Any illegal characters will be substituted with "_" and duplicate names will have numbers suffixed. It will also add a remote called AllDrives which shows all the shared drives combined into one directory tree.</p>
<h3 id="untrash">untrash</h3>
<p>Untrash files and directories</p>
<pre><code>rclone backend untrash remote: [options] [&lt;arguments&gt;+]</code></pre>
<p>This command untrashes all the files and directories in the directory passed in recursively.</p>
<p>Usage:</p>
<p>This takes an optional directory to trash which make this easier to use via the API.</p>
<pre><code>rclone backend untrash drive:directory
rclone backend --interactive untrash drive:directory subdir</code></pre>
<p>Use the --interactive/-i or --dry-run flag to see what would be restored before restoring it.</p>
<p>Result:</p>
<pre><code>{
    &quot;Untrashed&quot;: 17,
    &quot;Errors&quot;: 0
}</code></pre>
<h3 id="copyid">copyid</h3>
<p>Copy files by ID</p>
<pre><code>rclone backend copyid remote: [options] [&lt;arguments&gt;+]</code></pre>
<p>This command copies files by ID</p>
<p>Usage:</p>
<pre><code>rclone backend copyid drive: ID path
rclone backend copyid drive: ID1 path1 ID2 path2</code></pre>
<p>It copies the drive file with ID given to the path (an rclone path which will be passed internally to rclone copyto). The ID and path pairs can be repeated.</p>
<p>The path should end with a / to indicate copy the file as named to this directory. If it doesn't end with a / then the last path component will be used as the file name.</p>
<p>If the destination is a drive backend then server-side copying will be attempted if possible.</p>
<p>Use the --interactive/-i or --dry-run flag to see what would be copied before copying.</p>
<h3 id="exportformats">exportformats</h3>
<p>Dump the export formats for debug purposes</p>
<pre><code>rclone backend exportformats remote: [options] [&lt;arguments&gt;+]</code></pre>
<h3 id="importformats">importformats</h3>
<p>Dump the import formats for debug purposes</p>
<pre><code>rclone backend importformats remote: [options] [&lt;arguments&gt;+]</code></pre>
<h3 id="query">query</h3>
<p>List files using Google Drive query language</p>
<pre><code>rclone backend query remote: [options] [&lt;arguments&gt;+]</code></pre>
<p>This command lists files based on a query</p>
<p>Usage:</p>
<pre><code>rclone backend query drive: query</code></pre>
<p>The query syntax is documented at <a href="https://developers.google.com/drive/api/guides/ref-search-terms">Google Drive Search query terms and operators</a>.</p>
<p>For example:</p>
<pre><code>rclone backend query drive: &quot;&#39;0ABc9DEFGHIJKLMNop0QRatUVW3X&#39; in parents and name contains &#39;foo&#39;&quot;</code></pre>
<p>If the query contains literal ' or  characters, these need to be escaped with  characters. "'" becomes "'" and "" becomes "\", for example to match a file named "foo ' .txt":</p>
<pre><code>rclone backend query drive: &quot;name = &#39;foo \&#39; \\\.txt&#39;&quot;</code></pre>
<p>The result is a JSON array of matches, for example:</p>
<pre><code>[
{
    &quot;createdTime&quot;: &quot;2017-06-29T19:58:28.537Z&quot;,
    &quot;id&quot;: &quot;0AxBe_CDEF4zkGHI4d0FjYko2QkD&quot;,
    &quot;md5Checksum&quot;: &quot;68518d16be0c6fbfab918be61d658032&quot;,
    &quot;mimeType&quot;: &quot;text/plain&quot;,
    &quot;modifiedTime&quot;: &quot;2024-02-02T10:40:02.874Z&quot;,
    &quot;name&quot;: &quot;foo &#39; \\.txt&quot;,
    &quot;parents&quot;: [
        &quot;0BxAe_BCDE4zkFGZpcWJGek0xbzC&quot;
    ],
    &quot;resourceKey&quot;: &quot;0-ABCDEFGHIXJQpIGqBJq3MC&quot;,
    &quot;sha1Checksum&quot;: &quot;8f284fa768bfb4e45d076a579ab3905ab6bfa893&quot;,
    &quot;size&quot;: &quot;311&quot;,
    &quot;webViewLink&quot;: &quot;https://drive.google.com/file/d/0AxBe_CDEF4zkGHI4d0FjYko2QkD/view?usp=drivesdk\u0026resourcekey=0-ABCDEFGHIXJQpIGqBJq3MC&quot;
}
]</code></pre>
<h2 id="limitations-14">Limitations</h2>
<p>Drive has quite a lot of rate limiting. This causes rclone to be limited to transferring about 2 files per second only. Individual files may be transferred much faster at 100s of MiB/s but lots of small files can take a long time.</p>
<p>Server side copies are also subject to a separate rate limit. If you see User rate limit exceeded errors, wait at least 24 hours and retry. You can disable server-side copies with <code>--disable copy</code> to download and upload the files if you prefer.</p>
<h3 id="limitations-of-google-docs">Limitations of Google Docs</h3>
<p>Google docs will appear as size -1 in <code>rclone ls</code>, <code>rclone ncdu</code> etc, and as size 0 in anything which uses the VFS layer, e.g. <code>rclone mount</code> and <code>rclone serve</code>. When calculating directory totals, e.g. in <code>rclone size</code> and <code>rclone ncdu</code>, they will be counted in as empty files.</p>
<p>This is because rclone can't find out the size of the Google docs without downloading them.</p>
<p>Google docs will transfer correctly with <code>rclone sync</code>, <code>rclone copy</code> etc as rclone knows to ignore the size when doing the transfer.</p>
<p>However an unfortunate consequence of this is that you may not be able to download Google docs using <code>rclone mount</code>. If it doesn't work you will get a 0 sized file. If you try again the doc may gain its correct size and be downloadable. Whether it will work on not depends on the application accessing the mount and the OS you are running - experiment to find out if it does work for you!</p>
<h3 id="duplicated-files-2">Duplicated files</h3>
<p>Sometimes, for no reason I've been able to track down, drive will duplicate a file that rclone uploads. Drive unlike all the other remotes can have duplicated files.</p>
<p>Duplicated files cause problems with the syncing and you will see messages in the log about duplicates.</p>
<p>Use <code>rclone dedupe</code> to fix duplicated files.</p>
<p>Note that this isn't just a problem with rclone, even Google Photos on Android duplicates files on drive sometimes.</p>
<h3 id="rclone-appears-to-be-re-copying-files-it-shouldnt">Rclone appears to be re-copying files it shouldn't</h3>
<p>The most likely cause of this is the duplicated file issue above - run <code>rclone dedupe</code> and check your logs for duplicate object or directory messages.</p>
<p>This can also be caused by a delay/caching on google drive's end when comparing directory listings. Specifically with team drives used in combination with --fast-list. Files that were uploaded recently may not appear on the directory list sent to rclone when using --fast-list.</p>
<p>Waiting a moderate period of time between attempts (estimated to be approximately 1 hour) and/or not using --fast-list both seem to be effective in preventing the problem.</p>
<h3 id="sha1-or-sha256-hashes-may-be-missing">SHA1 or SHA256 hashes may be missing</h3>
<p>All files have MD5 hashes, but a small fraction of files uploaded may not have SHA1 or SHA256 hashes especially if they were uploaded before 2018.</p>
<h2 id="making-your-own-client_id">Making your own client_id</h2>
<p>When you use rclone with Google drive in its default configuration you are using rclone's client_id. This is shared between all the rclone users. There is a global rate limit on the number of queries per second that each client_id can do set by Google. rclone already has a high quota and I will continue to make sure it is high enough by contacting Google.</p>
<p>It is strongly recommended to use your own client ID as the default rclone ID is heavily used. If you have multiple services running, it is recommended to use an API key for each service. The default Google quota is 10 transactions per second so it is recommended to stay under that number as if you use more than that, it will cause rclone to rate limit and make things slower.</p>
<p>Here is how to create your own Google Drive client ID for rclone:</p>
<ol type="1">
<li><p>Log into the <a href="https://console.developers.google.com/">Google API Console</a> with your Google account. It doesn't matter what Google account you use. (It need not be the same account as the Google Drive you want to access)</p></li>
<li><p>Select a project or create a new project.</p></li>
<li><p>Under "ENABLE APIS AND SERVICES" search for "Drive", and enable the "Google Drive API".</p></li>
<li><p>Click "Credentials" in the left-side panel (not "Create credentials", which opens the wizard).</p></li>
<li><p>If you already configured an "Oauth Consent Screen", then skip to the next step; if not, click on "CONFIGURE CONSENT SCREEN" button (near the top right corner of the right panel), then select "External" and click on "CREATE"; on the next screen, enter an "Application name" ("rclone" is OK); enter "User Support Email" (your own email is OK); enter "Developer Contact Email" (your own email is OK); then click on "Save" (all other data is optional). You will also have to add <a href="https://developers.google.com/drive/api/guides/api-specific-auth">some scopes</a>, including</p></li>
</ol>
<ul>
<li><code>https://www.googleapis.com/auth/docs</code></li>
<li><code>https://www.googleapis.com/auth/drive</code> in order to be able to edit, create and delete files with RClone.</li>
<li><code>https://www.googleapis.com/auth/drive.metadata.readonly</code> which you may also want to add.</li>
<li>If you want to add all at once, comma separated it would be <code>https://www.googleapis.com/auth/docs,https://www.googleapis.com/auth/drive,https://www.googleapis.com/auth/drive.metadata.readonly</code>.</li>
</ul>
<ol start="6" type="1">
<li><p>After adding scopes, click "Save and continue" to add test users. Be sure to add your own account to the test users. Once you've added yourself as a test user and saved the changes, click again on "Credentials" on the left panel to go back to the "Credentials" screen.</p>
<p>(PS: if you are a GSuite user, you could also select "Internal" instead of "External" above, but this will restrict API use to Google Workspace users in your organisation).</p></li>
<li><p>Click on the "+ CREATE CREDENTIALS" button at the top of the screen, then select "OAuth client ID".</p></li>
<li><p>Choose an application type of "Desktop app" and click "Create". (the default name is fine)</p></li>
<li><p>It will show you a client ID and client secret. Make a note of these.</p>
<p>(If you selected "External" at Step 5 continue to Step 10. If you chose "Internal" you don't need to publish and can skip straight to Step 11 but your destination drive must be part of the same Google Workspace.)</p></li>
<li><p>Go to "Oauth consent screen" and then click "PUBLISH APP" button and confirm. You will also want to add yourself as a test user.</p></li>
<li><p>Provide the noted client ID and client secret to rclone.</p></li>
</ol>
<p>Be aware that, due to the "enhanced security" recently introduced by Google, you are theoretically expected to "submit your app for verification" and then wait a few weeks(!) for their response; in practice, you can go right ahead and use the client ID and client secret with rclone, the only issue will be a very scary confirmation screen shown when you connect via your browser for rclone to be able to get its token-id (but as this only happens during the remote configuration, it's not such a big deal). Keeping the application in "Testing" will work as well, but the limitation is that any grants will expire after a week, which can be annoying to refresh constantly. If, for whatever reason, a short grant time is not a problem, then keeping the application in testing mode would also be sufficient.</p>
<p>(Thanks to <span class="citation" data-cites="balazer">@balazer</span> on github for these instructions.)</p>
<p>Sometimes, creation of an OAuth consent in Google API Console fails due to an error message “The request failed because changes to one of the field of the resource is not supported”. As a convenient workaround, the necessary Google Drive API key can be created on the <a href="https://developers.google.com/drive/api/v3/quickstart/python">Python Quickstart</a> page. Just push the Enable the Drive API button to receive the Client ID and Secret. Note that it will automatically create a new project in the API Console.</p>
<h1 id="google-photos">Google Photos</h1>
<p>The rclone backend for <a href="https://www.google.com/photos/about/">Google Photos</a> is a specialized backend for transferring photos and videos to and from Google Photos.</p>
<p><strong>NB</strong> The Google Photos API which rclone uses has quite a few limitations, so please read the <a href="#limitations">limitations section</a> carefully to make sure it is suitable for your use.</p>
<h2 id="configuration-18">Configuration</h2>
<p>The initial setup for google cloud storage involves getting a token from Google Photos which you need to do in your browser. <code>rclone config</code> walks you through it.</p>
<p>Here is an example of how to make a remote called <code>remote</code>. First run:</p>
<pre><code> rclone config</code></pre>
<p>This will guide you through an interactive setup process:</p>
<pre><code>No remotes found, make a new one?
n) New remote
s) Set configuration password
q) Quit config
n/s/q&gt; n
name&gt; remote
Type of storage to configure.
Enter a string value. Press Enter for the default (&quot;&quot;).
Choose a number from below, or type in your own value
[snip]
XX / Google Photos
   \ &quot;google photos&quot;
[snip]
Storage&gt; google photos
** See help for google photos backend at: https://rclone.org/googlephotos/ **

Google Application Client Id
Leave blank normally.
Enter a string value. Press Enter for the default (&quot;&quot;).
client_id&gt; 
Google Application Client Secret
Leave blank normally.
Enter a string value. Press Enter for the default (&quot;&quot;).
client_secret&gt; 
Set to make the Google Photos backend read only.

If you choose read only then rclone will only request read only access
to your photos, otherwise rclone will request full access.
Enter a boolean value (true or false). Press Enter for the default (&quot;false&quot;).
read_only&gt; 
Edit advanced config? (y/n)
y) Yes
n) No
y/n&gt; n
Remote config
Use web browser to automatically authenticate rclone with remote?
 * Say Y if the machine running rclone has a web browser you can use
 * Say N if running rclone on a (remote) machine without web browser access
If not sure try Y. If Y failed, try N.
y) Yes
n) No
y/n&gt; y
If your browser doesn&#39;t open automatically go to the following link: http://127.0.0.1:53682/auth
Log in and authorize rclone for access
Waiting for code...
Got code

*** IMPORTANT: All media items uploaded to Google Photos with rclone
*** are stored in full resolution at original quality.  These uploads
*** will count towards storage in your Google Account.

Configuration complete.
Options:
- type: google photos
- token: {&quot;access_token&quot;:&quot;XXX&quot;,&quot;token_type&quot;:&quot;Bearer&quot;,&quot;refresh_token&quot;:&quot;XXX&quot;,&quot;expiry&quot;:&quot;2019-06-28T17:38:04.644930156+01:00&quot;}
Keep this &quot;remote&quot; remote?
y) Yes this is OK
e) Edit this remote
d) Delete this remote
y/e/d&gt; y</code></pre>
<p>See the <a href="https://rclone.org/remote_setup/">remote setup docs</a> for how to set it up on a machine with no Internet browser available.</p>
<p>Note that rclone runs a webserver on your local machine to collect the token as returned from Google if using web browser to automatically authenticate. This only runs from the moment it opens your browser to the moment you get back the verification code. This is on <code>http://127.0.0.1:53682/</code> and this may require you to unblock it temporarily if you are running a host firewall, or use manual mode.</p>
<p>This remote is called <code>remote</code> and can now be used like this</p>
<p>See all the albums in your photos</p>
<pre><code>rclone lsd remote:album</code></pre>
<p>Make a new album</p>
<pre><code>rclone mkdir remote:album/newAlbum</code></pre>
<p>List the contents of an album</p>
<pre><code>rclone ls remote:album/newAlbum</code></pre>
<p>Sync <code>/home/local/images</code> to the Google Photos, removing any excess files in the album.</p>
<pre><code>rclone sync --interactive /home/local/image remote:album/newAlbum</code></pre>
<h3 id="layout">Layout</h3>
<p>As Google Photos is not a general purpose cloud storage system, the backend is laid out to help you navigate it.</p>
<p>The directories under <code>media</code> show different ways of categorizing the media. Each file will appear multiple times. So if you want to make a backup of your google photos you might choose to backup <code>remote:media/by-month</code>. (<strong>NB</strong> <code>remote:media/by-day</code> is rather slow at the moment so avoid for syncing.)</p>
<p>Note that all your photos and videos will appear somewhere under <code>media</code>, but they may not appear under <code>album</code> unless you've put them into albums.</p>
<pre><code>/
- upload
    - file1.jpg
    - file2.jpg
    - ...
- media
    - all
        - file1.jpg
        - file2.jpg
        - ...
    - by-year
        - 2000
            - file1.jpg
            - ...
        - 2001
            - file2.jpg
            - ...
        - ...
    - by-month
        - 2000
            - 2000-01
                - file1.jpg
                - ...
            - 2000-02
                - file2.jpg
                - ...
        - ...
    - by-day
        - 2000
            - 2000-01-01
                - file1.jpg
                - ...
            - 2000-01-02
                - file2.jpg
                - ...
        - ...
- album
    - album name
    - album name/sub
- shared-album
    - album name
    - album name/sub
- feature
    - favorites
        - file1.jpg
        - file2.jpg</code></pre>
<p>There are two writable parts of the tree, the <code>upload</code> directory and sub directories of the <code>album</code> directory.</p>
<p>The <code>upload</code> directory is for uploading files you don't want to put into albums. This will be empty to start with and will contain the files you've uploaded for one rclone session only, becoming empty again when you restart rclone. The use case for this would be if you have a load of files you just want to once off dump into Google Photos. For repeated syncing, uploading to <code>album</code> will work better.</p>
<p>Directories within the <code>album</code> directory are also writeable and you may create new directories (albums) under <code>album</code>. If you copy files with a directory hierarchy in there then rclone will create albums with the <code>/</code> character in them. For example if you do</p>
<pre><code>rclone copy /path/to/images remote:album/images</code></pre>
<p>and the images directory contains</p>
<pre><code>images
    - file1.jpg
    dir
        file2.jpg
    dir2
        dir3
            file3.jpg</code></pre>
<p>Then rclone will create the following albums with the following files in</p>
<ul>
<li>images
<ul>
<li>file1.jpg</li>
</ul></li>
<li>images/dir
<ul>
<li>file2.jpg</li>
</ul></li>
<li>images/dir2/dir3
<ul>
<li>file3.jpg</li>
</ul></li>
</ul>
<p>This means that you can use the <code>album</code> path pretty much like a normal filesystem and it is a good target for repeated syncing.</p>
<p>The <code>shared-album</code> directory shows albums shared with you or by you. This is similar to the Sharing tab in the Google Photos web interface.</p>
<h3 id="standard-options-18">Standard options</h3>
<p>Here are the Standard options specific to google photos (Google Photos).</p>
<h4 id="gphotos-client-id">--gphotos-client-id</h4>
<p>OAuth Client Id.</p>
<p>Leave blank normally.</p>
<p>Properties:</p>
<ul>
<li>Config: client_id</li>
<li>Env Var: RCLONE_GPHOTOS_CLIENT_ID</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="gphotos-client-secret">--gphotos-client-secret</h4>
<p>OAuth Client Secret.</p>
<p>Leave blank normally.</p>
<p>Properties:</p>
<ul>
<li>Config: client_secret</li>
<li>Env Var: RCLONE_GPHOTOS_CLIENT_SECRET</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="gphotos-read-only">--gphotos-read-only</h4>
<p>Set to make the Google Photos backend read only.</p>
<p>If you choose read only then rclone will only request read only access to your photos, otherwise rclone will request full access.</p>
<p>Properties:</p>
<ul>
<li>Config: read_only</li>
<li>Env Var: RCLONE_GPHOTOS_READ_ONLY</li>
<li>Type: bool</li>
<li>Default: false</li>
</ul>
<h3 id="advanced-options-18">Advanced options</h3>
<p>Here are the Advanced options specific to google photos (Google Photos).</p>
<h4 id="gphotos-token">--gphotos-token</h4>
<p>OAuth Access Token as a JSON blob.</p>
<p>Properties:</p>
<ul>
<li>Config: token</li>
<li>Env Var: RCLONE_GPHOTOS_TOKEN</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="gphotos-auth-url">--gphotos-auth-url</h4>
<p>Auth server URL.</p>
<p>Leave blank to use the provider defaults.</p>
<p>Properties:</p>
<ul>
<li>Config: auth_url</li>
<li>Env Var: RCLONE_GPHOTOS_AUTH_URL</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="gphotos-token-url">--gphotos-token-url</h4>
<p>Token server url.</p>
<p>Leave blank to use the provider defaults.</p>
<p>Properties:</p>
<ul>
<li>Config: token_url</li>
<li>Env Var: RCLONE_GPHOTOS_TOKEN_URL</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="gphotos-read-size">--gphotos-read-size</h4>
<p>Set to read the size of media items.</p>
<p>Normally rclone does not read the size of media items since this takes another transaction. This isn't necessary for syncing. However rclone mount needs to know the size of files in advance of reading them, so setting this flag when using rclone mount is recommended if you want to read the media.</p>
<p>Properties:</p>
<ul>
<li>Config: read_size</li>
<li>Env Var: RCLONE_GPHOTOS_READ_SIZE</li>
<li>Type: bool</li>
<li>Default: false</li>
</ul>
<h4 id="gphotos-start-year">--gphotos-start-year</h4>
<p>Year limits the photos to be downloaded to those which are uploaded after the given year.</p>
<p>Properties:</p>
<ul>
<li>Config: start_year</li>
<li>Env Var: RCLONE_GPHOTOS_START_YEAR</li>
<li>Type: int</li>
<li>Default: 2000</li>
</ul>
<h4 id="gphotos-include-archived">--gphotos-include-archived</h4>
<p>Also view and download archived media.</p>
<p>By default, rclone does not request archived media. Thus, when syncing, archived media is not visible in directory listings or transferred.</p>
<p>Note that media in albums is always visible and synced, no matter their archive status.</p>
<p>With this flag, archived media are always visible in directory listings and transferred.</p>
<p>Without this flag, archived media will not be visible in directory listings and won't be transferred.</p>
<p>Properties:</p>
<ul>
<li>Config: include_archived</li>
<li>Env Var: RCLONE_GPHOTOS_INCLUDE_ARCHIVED</li>
<li>Type: bool</li>
<li>Default: false</li>
</ul>
<h4 id="gphotos-encoding">--gphotos-encoding</h4>
<p>The encoding for the backend.</p>
<p>See the <a href="https://rclone.org/overview/#encoding">encoding section in the overview</a> for more info.</p>
<p>Properties:</p>
<ul>
<li>Config: encoding</li>
<li>Env Var: RCLONE_GPHOTOS_ENCODING</li>
<li>Type: Encoding</li>
<li>Default: Slash,CrLf,InvalidUtf8,Dot</li>
</ul>
<h4 id="gphotos-batch-mode">--gphotos-batch-mode</h4>
<p>Upload file batching sync|async|off.</p>
<p>This sets the batch mode used by rclone.</p>
<p>This has 3 possible values</p>
<ul>
<li>off - no batching</li>
<li>sync - batch uploads and check completion (default)</li>
<li>async - batch upload and don't check completion</li>
</ul>
<p>Rclone will close any outstanding batches when it exits which may make a delay on quit.</p>
<p>Properties:</p>
<ul>
<li>Config: batch_mode</li>
<li>Env Var: RCLONE_GPHOTOS_BATCH_MODE</li>
<li>Type: string</li>
<li>Default: "sync"</li>
</ul>
<h4 id="gphotos-batch-size">--gphotos-batch-size</h4>
<p>Max number of files in upload batch.</p>
<p>This sets the batch size of files to upload. It has to be less than 50.</p>
<p>By default this is 0 which means rclone will calculate the batch size depending on the setting of batch_mode.</p>
<ul>
<li>batch_mode: async - default batch_size is 50</li>
<li>batch_mode: sync - default batch_size is the same as --transfers</li>
<li>batch_mode: off - not in use</li>
</ul>
<p>Rclone will close any outstanding batches when it exits which may make a delay on quit.</p>
<p>Setting this is a great idea if you are uploading lots of small files as it will make them a lot quicker. You can use --transfers 32 to maximise throughput.</p>
<p>Properties:</p>
<ul>
<li>Config: batch_size</li>
<li>Env Var: RCLONE_GPHOTOS_BATCH_SIZE</li>
<li>Type: int</li>
<li>Default: 0</li>
</ul>
<h4 id="gphotos-batch-timeout">--gphotos-batch-timeout</h4>
<p>Max time to allow an idle upload batch before uploading.</p>
<p>If an upload batch is idle for more than this long then it will be uploaded.</p>
<p>The default for this is 0 which means rclone will choose a sensible default based on the batch_mode in use.</p>
<ul>
<li>batch_mode: async - default batch_timeout is 10s</li>
<li>batch_mode: sync - default batch_timeout is 1s</li>
<li>batch_mode: off - not in use</li>
</ul>
<p>Properties:</p>
<ul>
<li>Config: batch_timeout</li>
<li>Env Var: RCLONE_GPHOTOS_BATCH_TIMEOUT</li>
<li>Type: Duration</li>
<li>Default: 0s</li>
</ul>
<h4 id="gphotos-batch-commit-timeout">--gphotos-batch-commit-timeout</h4>
<p>Max time to wait for a batch to finish committing</p>
<p>Properties:</p>
<ul>
<li>Config: batch_commit_timeout</li>
<li>Env Var: RCLONE_GPHOTOS_BATCH_COMMIT_TIMEOUT</li>
<li>Type: Duration</li>
<li>Default: 10m0s</li>
</ul>
<h4 id="gphotos-description">--gphotos-description</h4>
<p>Description of the remote.</p>
<p>Properties:</p>
<ul>
<li>Config: description</li>
<li>Env Var: RCLONE_GPHOTOS_DESCRIPTION</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h2 id="limitations-15">Limitations</h2>
<p>Only images and videos can be uploaded. If you attempt to upload non videos or images or formats that Google Photos doesn't understand, rclone will upload the file, then Google Photos will give an error when it is put turned into a media item.</p>
<p>Note that all media items uploaded to Google Photos through the API are stored in full resolution at "original quality" and <strong>will</strong> count towards your storage quota in your Google Account. The API does <strong>not</strong> offer a way to upload in "high quality" mode..</p>
<p><code>rclone about</code> is not supported by the Google Photos backend. Backends without this capability cannot determine free space for an rclone mount or use policy <code>mfs</code> (most free space) as a member of an rclone union remote.</p>
<p>See <a href="https://rclone.org/overview/#optional-features">List of backends that do not support rclone about</a> See <a href="https://rclone.org/commands/rclone_about/">rclone about</a></p>
<h3 id="downloading-images">Downloading Images</h3>
<p>When Images are downloaded this strips EXIF location (according to the docs and my tests). This is a limitation of the Google Photos API and is covered by <a href="https://issuetracker.google.com/issues/112096115">bug #112096115</a>.</p>
<p><strong>The current google API does not allow photos to be downloaded at original resolution. This is very important if you are, for example, relying on "Google Photos" as a backup of your photos. You will not be able to use rclone to redownload original images. You could use 'google takeout' to recover the original photos as a last resort</strong></p>
<h3 id="downloading-videos">Downloading Videos</h3>
<p>When videos are downloaded they are downloaded in a really compressed version of the video compared to downloading it via the Google Photos web interface. This is covered by <a href="https://issuetracker.google.com/issues/113672044">bug #113672044</a>.</p>
<h3 id="duplicates">Duplicates</h3>
<p>If a file name is duplicated in a directory then rclone will add the file ID into its name. So two files called <code>file.jpg</code> would then appear as <code>file {123456}.jpg</code> and <code>file {ABCDEF}.jpg</code> (the actual IDs are a lot longer alas!).</p>
<p>If you upload the same image (with the same binary data) twice then Google Photos will deduplicate it. However it will retain the filename from the first upload which may confuse rclone. For example if you uploaded an image to <code>upload</code> then uploaded the same image to <code>album/my_album</code> the filename of the image in <code>album/my_album</code> will be what it was uploaded with initially, not what you uploaded it with to <code>album</code>. In practise this shouldn't cause too many problems.</p>
<h3 id="modification-times-6">Modification times</h3>
<p>The date shown of media in Google Photos is the creation date as determined by the EXIF information, or the upload date if that is not known.</p>
<p>This is not changeable by rclone and is not the modification date of the media on local disk. This means that rclone cannot use the dates from Google Photos for syncing purposes.</p>
<h3 id="size">Size</h3>
<p>The Google Photos API does not return the size of media. This means that when syncing to Google Photos, rclone can only do a file existence check.</p>
<p>It is possible to read the size of the media, but this needs an extra HTTP HEAD request per media item so is <strong>very slow</strong> and uses up a lot of transactions. This can be enabled with the <code>--gphotos-read-size</code> option or the <code>read_size = true</code> config parameter.</p>
<p>If you want to use the backend with <code>rclone mount</code> you may need to enable this flag (depending on your OS and application using the photos) otherwise you may not be able to read media off the mount. You'll need to experiment to see if it works for you without the flag.</p>
<h3 id="albums">Albums</h3>
<p>Rclone can only upload files to albums it created. This is a <a href="https://developers.google.com/photos/library/guides/manage-albums">limitation of the Google Photos API</a>.</p>
<p>Rclone can remove files it uploaded from albums it created only.</p>
<h3 id="deleting-files-2">Deleting files</h3>
<p>Rclone can remove files from albums it created, but note that the Google Photos API does not allow media to be deleted permanently so this media will still remain. See <a href="https://issuetracker.google.com/issues/109759781">bug #109759781</a>.</p>
<p>Rclone cannot delete files anywhere except under <code>album</code>.</p>
<h3 id="deleting-albums">Deleting albums</h3>
<p>The Google Photos API does not support deleting albums - see <a href="https://issuetracker.google.com/issues/135714733">bug #135714733</a>.</p>
<h1 id="hasher">Hasher</h1>
<p>Hasher is a special overlay backend to create remotes which handle checksums for other remotes. It's main functions include: - Emulate hash types unimplemented by backends - Cache checksums to help with slow hashing of large local or (S)FTP files - Warm up checksum cache from external SUM files</p>
<h2 id="getting-started-1">Getting started</h2>
<p>To use Hasher, first set up the underlying remote following the configuration instructions for that remote. You can also use a local pathname instead of a remote. Check that your base remote is working.</p>
<p>Let's call the base remote <code>myRemote:path</code> here. Note that anything inside <code>myRemote:path</code> will be handled by hasher and anything outside won't. This means that if you are using a bucket based remote (S3, B2, Swift) then you should put the bucket in the remote <code>s3:bucket</code>.</p>
<p>Now proceed to interactive or manual configuration.</p>
<h3 id="interactive-configuration">Interactive configuration</h3>
<p>Run <code>rclone config</code>:</p>
<pre><code>No remotes found, make a new one?
n) New remote
s) Set configuration password
q) Quit config
n/s/q&gt; n
name&gt; Hasher1
Type of storage to configure.
Choose a number from below, or type in your own value
[snip]
XX / Handle checksums for other remotes
   \ &quot;hasher&quot;
[snip]
Storage&gt; hasher
Remote to cache checksums for, like myremote:mypath.
Enter a string value. Press Enter for the default (&quot;&quot;).
remote&gt; myRemote:path
Comma separated list of supported checksum types.
Enter a string value. Press Enter for the default (&quot;md5,sha1&quot;).
hashsums&gt; md5
Maximum time to keep checksums in cache. 0 = no cache, off = cache forever.
max_age&gt; off
Edit advanced config? (y/n)
y) Yes
n) No
y/n&gt; n
Remote config
--------------------
[Hasher1]
type = hasher
remote = myRemote:path
hashsums = md5
max_age = off
--------------------
y) Yes this is OK
e) Edit this remote
d) Delete this remote
y/e/d&gt; y</code></pre>
<h3 id="manual-configuration">Manual configuration</h3>
<p>Run <code>rclone config path</code> to see the path of current active config file, usually <code>YOURHOME/.config/rclone/rclone.conf</code>. Open it in your favorite text editor, find section for the base remote and create new section for hasher like in the following examples:</p>
<pre><code>[Hasher1]
type = hasher
remote = myRemote:path
hashes = md5
max_age = off

[Hasher2]
type = hasher
remote = /local/path
hashes = dropbox,sha1
max_age = 24h</code></pre>
<p>Hasher takes basically the following parameters: - <code>remote</code> is required, - <code>hashes</code> is a comma separated list of supported checksums (by default <code>md5,sha1</code>), - <code>max_age</code> - maximum time to keep a checksum value in the cache, <code>0</code> will disable caching completely, <code>off</code> will cache "forever" (that is until the files get changed).</p>
<p>Make sure the <code>remote</code> has <code>:</code> (colon) in. If you specify the remote without a colon then rclone will use a local directory of that name. So if you use a remote of <code>/local/path</code> then rclone will handle hashes for that directory. If you use <code>remote = name</code> literally then rclone will put files <strong>in a directory called <code>name</code> located under current directory</strong>.</p>
<h2 id="usage-1">Usage</h2>
<h3 id="basic-operations">Basic operations</h3>
<p>Now you can use it as <code>Hasher2:subdir/file</code> instead of base remote. Hasher will transparently update cache with new checksums when a file is fully read or overwritten, like:</p>
<pre><code>rclone copy External:path/file Hasher:dest/path

rclone cat Hasher:path/to/file &gt; /dev/null</code></pre>
<p>The way to refresh <strong>all</strong> cached checksums (even unsupported by the base backend) for a subtree is to <strong>re-download</strong> all files in the subtree. For example, use <code>hashsum --download</code> using <strong>any</strong> supported hashsum on the command line (we just care to re-read):</p>
<pre><code>rclone hashsum MD5 --download Hasher:path/to/subtree &gt; /dev/null

rclone backend dump Hasher:path/to/subtree</code></pre>
<p>You can print or drop hashsum cache using custom backend commands:</p>
<pre><code>rclone backend dump Hasher:dir/subdir

rclone backend drop Hasher:</code></pre>
<h3 id="pre-seed-from-a-sum-file">Pre-Seed from a SUM File</h3>
<p>Hasher supports two backend commands: generic SUM file <code>import</code> and faster but less consistent <code>stickyimport</code>.</p>
<pre><code>rclone backend import Hasher:dir/subdir SHA1 /path/to/SHA1SUM [--checkers 4]</code></pre>
<p>Instead of SHA1 it can be any hash supported by the remote. The last argument can point to either a local or an <code>other-remote:path</code> text file in SUM format. The command will parse the SUM file, then walk down the path given by the first argument, snapshot current fingerprints and fill in the cache entries correspondingly. - Paths in the SUM file are treated as relative to <code>hasher:dir/subdir</code>. - The command will <strong>not</strong> check that supplied values are correct. You <strong>must know</strong> what you are doing. - This is a one-time action. The SUM file will not get "attached" to the remote. Cache entries can still be overwritten later, should the object's fingerprint change. - The tree walk can take long depending on the tree size. You can increase <code>--checkers</code> to make it faster. Or use <code>stickyimport</code> if you don't care about fingerprints and consistency.</p>
<pre><code>rclone backend stickyimport hasher:path/to/data sha1 remote:/path/to/sum.sha1</code></pre>
<p><code>stickyimport</code> is similar to <code>import</code> but works much faster because it does not need to stat existing files and skips initial tree walk. Instead of binding cache entries to file fingerprints it creates <em>sticky</em> entries bound to the file name alone ignoring size, modification time etc. Such hash entries can be replaced only by <code>purge</code>, <code>delete</code>, <code>backend drop</code> or by full re-read/re-write of the files.</p>
<h2 id="configuration-reference">Configuration reference</h2>
<h3 id="standard-options-19">Standard options</h3>
<p>Here are the Standard options specific to hasher (Better checksums for other remotes).</p>
<h4 id="hasher-remote">--hasher-remote</h4>
<p>Remote to cache checksums for (e.g. myRemote:path).</p>
<p>Properties:</p>
<ul>
<li>Config: remote</li>
<li>Env Var: RCLONE_HASHER_REMOTE</li>
<li>Type: string</li>
<li>Required: true</li>
</ul>
<h4 id="hasher-hashes">--hasher-hashes</h4>
<p>Comma separated list of supported checksum types.</p>
<p>Properties:</p>
<ul>
<li>Config: hashes</li>
<li>Env Var: RCLONE_HASHER_HASHES</li>
<li>Type: CommaSepList</li>
<li>Default: md5,sha1</li>
</ul>
<h4 id="hasher-max-age">--hasher-max-age</h4>
<p>Maximum time to keep checksums in cache (0 = no cache, off = cache forever).</p>
<p>Properties:</p>
<ul>
<li>Config: max_age</li>
<li>Env Var: RCLONE_HASHER_MAX_AGE</li>
<li>Type: Duration</li>
<li>Default: off</li>
</ul>
<h3 id="advanced-options-19">Advanced options</h3>
<p>Here are the Advanced options specific to hasher (Better checksums for other remotes).</p>
<h4 id="hasher-auto-size">--hasher-auto-size</h4>
<p>Auto-update checksum for files smaller than this size (disabled by default).</p>
<p>Properties:</p>
<ul>
<li>Config: auto_size</li>
<li>Env Var: RCLONE_HASHER_AUTO_SIZE</li>
<li>Type: SizeSuffix</li>
<li>Default: 0</li>
</ul>
<h4 id="hasher-description">--hasher-description</h4>
<p>Description of the remote.</p>
<p>Properties:</p>
<ul>
<li>Config: description</li>
<li>Env Var: RCLONE_HASHER_DESCRIPTION</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h3 id="metadata-9">Metadata</h3>
<p>Any metadata supported by the underlying remote is read and written.</p>
<p>See the <a href="https://rclone.org/docs/#metadata">metadata</a> docs for more info.</p>
<h2 id="backend-commands-5">Backend commands</h2>
<p>Here are the commands specific to the hasher backend.</p>
<p>Run them with</p>
<pre><code>rclone backend COMMAND remote:</code></pre>
<p>The help below will explain what arguments each command takes.</p>
<p>See the <a href="https://rclone.org/commands/rclone_backend/">backend</a> command for more info on how to pass options and arguments.</p>
<p>These can be run on a running backend using the rc command <a href="https://rclone.org/rc/#backend-command">backend/command</a>.</p>
<h3 id="drop">drop</h3>
<p>Drop cache</p>
<pre><code>rclone backend drop remote: [options] [&lt;arguments&gt;+]</code></pre>
<p>Completely drop checksum cache. Usage Example: rclone backend drop hasher:</p>
<h3 id="dump">dump</h3>
<p>Dump the database</p>
<pre><code>rclone backend dump remote: [options] [&lt;arguments&gt;+]</code></pre>
<p>Dump cache records covered by the current remote</p>
<h3 id="fulldump">fulldump</h3>
<p>Full dump of the database</p>
<pre><code>rclone backend fulldump remote: [options] [&lt;arguments&gt;+]</code></pre>
<p>Dump all cache records in the database</p>
<h3 id="import">import</h3>
<p>Import a SUM file</p>
<pre><code>rclone backend import remote: [options] [&lt;arguments&gt;+]</code></pre>
<p>Amend hash cache from a SUM file and bind checksums to files by size/time. Usage Example: rclone backend import hasher:subdir md5 /path/to/sum.md5</p>
<h3 id="stickyimport">stickyimport</h3>
<p>Perform fast import of a SUM file</p>
<pre><code>rclone backend stickyimport remote: [options] [&lt;arguments&gt;+]</code></pre>
<p>Fill hash cache from a SUM file without verifying file fingerprints. Usage Example: rclone backend stickyimport hasher:subdir md5 remote:path/to/sum.md5</p>
<h2 id="implementation-details-advanced">Implementation details (advanced)</h2>
<p>This section explains how various rclone operations work on a hasher remote.</p>
<p><strong>Disclaimer. This section describes current implementation which can change in future rclone versions!.</strong></p>
<h3 id="hashsum-command">Hashsum command</h3>
<p>The <code>rclone hashsum</code> (or <code>md5sum</code> or <code>sha1sum</code>) command will:</p>
<ol type="1">
<li>if requested hash is supported by lower level, just pass it.</li>
<li>if object size is below <code>auto_size</code> then download object and calculate <em>requested</em> hashes on the fly.</li>
<li>if unsupported and the size is big enough, build object <code>fingerprint</code> (including size, modtime if supported, first-found <em>other</em> hash if any).</li>
<li>if the strict match is found in cache for the requested remote, return the stored hash.</li>
<li>if remote found but fingerprint mismatched, then purge the entry and proceed to step 6.</li>
<li>if remote not found or had no requested hash type or after step 5: download object, calculate all <em>supported</em> hashes on the fly and store in cache; return requested hash.</li>
</ol>
<h3 id="other-operations">Other operations</h3>
<ul>
<li>any time a hash is requested, follow the logic from 1-4 from <code>hashsum</code> above</li>
<li>whenever a file is uploaded or downloaded <strong>in full</strong>, capture the stream to calculate all supported hashes on the fly and update database</li>
<li>server-side <code>move</code> will update keys of existing cache entries</li>
<li><code>deletefile</code> will remove a single cache entry</li>
<li><code>purge</code> will remove all cache entries under the purged path</li>
</ul>
<p>Note that setting <code>max_age = 0</code> will disable checksum caching completely.</p>
<p>If you set <code>max_age = off</code>, checksums in cache will never age, unless you fully rewrite or delete the file.</p>
<h3 id="cache-storage">Cache storage</h3>
<p>Cached checksums are stored as <code>bolt</code> database files under rclone cache directory, usually <code>~/.cache/rclone/kv/</code>. Databases are maintained one per <em>base</em> backend, named like <code>BaseRemote~hasher.bolt</code>. Checksums for multiple <code>alias</code>-es into a single base backend will be stored in the single database. All local paths are treated as aliases into the <code>local</code> backend (unless encrypted or chunked) and stored in <code>~/.cache/rclone/kv/local~hasher.bolt</code>. Databases can be shared between multiple rclone processes.</p>
<h1 id="hdfs">HDFS</h1>
<p><a href="https://hadoop.apache.org/docs/stable/hadoop-project-dist/hadoop-hdfs/HdfsDesign.html">HDFS</a> is a distributed file-system, part of the <a href="https://hadoop.apache.org/">Apache Hadoop</a> framework.</p>
<p>Paths are specified as <code>remote:</code> or <code>remote:path/to/dir</code>.</p>
<h2 id="configuration-19">Configuration</h2>
<p>Here is an example of how to make a remote called <code>remote</code>. First run:</p>
<pre><code> rclone config</code></pre>
<p>This will guide you through an interactive setup process:</p>
<pre><code>No remotes found, make a new one?
n) New remote
s) Set configuration password
q) Quit config
n/s/q&gt; n
name&gt; remote
Type of storage to configure.
Enter a string value. Press Enter for the default (&quot;&quot;).
Choose a number from below, or type in your own value
[skip]
XX / Hadoop distributed file system
   \ &quot;hdfs&quot;
[skip]
Storage&gt; hdfs
** See help for hdfs backend at: https://rclone.org/hdfs/ **

hadoop name node and port
Enter a string value. Press Enter for the default (&quot;&quot;).
Choose a number from below, or type in your own value
 1 / Connect to host namenode at port 8020
   \ &quot;namenode:8020&quot;
namenode&gt; namenode.hadoop:8020
hadoop user name
Enter a string value. Press Enter for the default (&quot;&quot;).
Choose a number from below, or type in your own value
 1 / Connect to hdfs as root
   \ &quot;root&quot;
username&gt; root
Edit advanced config? (y/n)
y) Yes
n) No (default)
y/n&gt; n
Remote config
Configuration complete.
Options:
- type: hdfs
- namenode: namenode.hadoop:8020
- username: root
Keep this &quot;remote&quot; remote?
y) Yes this is OK (default)
e) Edit this remote
d) Delete this remote
y/e/d&gt; y
Current remotes:

Name                 Type
====                 ====
hadoop               hdfs

e) Edit existing remote
n) New remote
d) Delete remote
r) Rename remote
c) Copy remote
s) Set configuration password
q) Quit config
e/n/d/r/c/s/q&gt; q</code></pre>
<p>This remote is called <code>remote</code> and can now be used like this</p>
<p>See all the top level directories</p>
<pre><code>rclone lsd remote:</code></pre>
<p>List the contents of a directory</p>
<pre><code>rclone ls remote:directory</code></pre>
<p>Sync the remote <code>directory</code> to <code>/home/local/directory</code>, deleting any excess files.</p>
<pre><code>rclone sync --interactive remote:directory /home/local/directory</code></pre>
<h3 id="setting-up-your-own-hdfs-instance-for-testing">Setting up your own HDFS instance for testing</h3>
<p>You may start with a <a href="https://hadoop.apache.org/docs/stable/hadoop-project-dist/hadoop-common/SingleCluster.html">manual setup</a> or use the docker image from the tests:</p>
<p>If you want to build the docker image</p>
<pre><code>git clone https://github.com/rclone/rclone.git
cd rclone/fstest/testserver/images/test-hdfs
docker build --rm -t rclone/test-hdfs .</code></pre>
<p>Or you can just use the latest one pushed</p>
<pre><code>docker run --rm --name &quot;rclone-hdfs&quot; -p 127.0.0.1:9866:9866 -p 127.0.0.1:8020:8020 --hostname &quot;rclone-hdfs&quot; rclone/test-hdfs</code></pre>
<p><strong>NB</strong> it need few seconds to startup.</p>
<p>For this docker image the remote needs to be configured like this:</p>
<pre><code>[remote]
type = hdfs
namenode = 127.0.0.1:8020
username = root</code></pre>
<p>You can stop this image with <code>docker kill rclone-hdfs</code> (<strong>NB</strong> it does not use volumes, so all data uploaded will be lost.)</p>
<h3 id="modification-times-7">Modification times</h3>
<p>Time accurate to 1 second is stored.</p>
<h3 id="checksum">Checksum</h3>
<p>No checksums are implemented.</p>
<h3 id="usage-information">Usage information</h3>
<p>You can use the <code>rclone about remote:</code> command which will display filesystem size and current usage.</p>
<h3 id="restricted-filename-characters-11">Restricted filename characters</h3>
<p>In addition to the <a href="https://rclone.org/overview/#restricted-characters">default restricted characters set</a> the following characters are also replaced:</p>
<table>
<thead>
<tr class="header">
<th>Character</th>
<th style="text-align: center;">Value</th>
<th style="text-align: center;">Replacement</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td>:</td>
<td style="text-align: center;">0x3A</td>
<td style="text-align: center;">：</td>
</tr>
</tbody>
</table>
<p>Invalid UTF-8 bytes will also be <a href="https://rclone.org/overview/#invalid-utf8">replaced</a>.</p>
<h3 id="standard-options-20">Standard options</h3>
<p>Here are the Standard options specific to hdfs (Hadoop distributed file system).</p>
<h4 id="hdfs-namenode">--hdfs-namenode</h4>
<p>Hadoop name nodes and ports.</p>
<p>E.g. "namenode-1:8020,namenode-2:8020,..." to connect to host namenodes at port 8020.</p>
<p>Properties:</p>
<ul>
<li>Config: namenode</li>
<li>Env Var: RCLONE_HDFS_NAMENODE</li>
<li>Type: CommaSepList</li>
<li>Default:</li>
</ul>
<h4 id="hdfs-username">--hdfs-username</h4>
<p>Hadoop user name.</p>
<p>Properties:</p>
<ul>
<li>Config: username</li>
<li>Env Var: RCLONE_HDFS_USERNAME</li>
<li>Type: string</li>
<li>Required: false</li>
<li>Examples:
<ul>
<li>"root"
<ul>
<li>Connect to hdfs as root.</li>
</ul></li>
</ul></li>
</ul>
<h3 id="advanced-options-20">Advanced options</h3>
<p>Here are the Advanced options specific to hdfs (Hadoop distributed file system).</p>
<h4 id="hdfs-service-principal-name">--hdfs-service-principal-name</h4>
<p>Kerberos service principal name for the namenode.</p>
<p>Enables KERBEROS authentication. Specifies the Service Principal Name (SERVICE/FQDN) for the namenode. E.g. "hdfs/namenode.hadoop.docker" for namenode running as service 'hdfs' with FQDN 'namenode.hadoop.docker'.</p>
<p>Properties:</p>
<ul>
<li>Config: service_principal_name</li>
<li>Env Var: RCLONE_HDFS_SERVICE_PRINCIPAL_NAME</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="hdfs-data-transfer-protection">--hdfs-data-transfer-protection</h4>
<p>Kerberos data transfer protection: authentication|integrity|privacy.</p>
<p>Specifies whether or not authentication, data signature integrity checks, and wire encryption are required when communicating with the datanodes. Possible values are 'authentication', 'integrity' and 'privacy'. Used only with KERBEROS enabled.</p>
<p>Properties:</p>
<ul>
<li>Config: data_transfer_protection</li>
<li>Env Var: RCLONE_HDFS_DATA_TRANSFER_PROTECTION</li>
<li>Type: string</li>
<li>Required: false</li>
<li>Examples:
<ul>
<li>"privacy"
<ul>
<li>Ensure authentication, integrity and encryption enabled.</li>
</ul></li>
</ul></li>
</ul>
<h4 id="hdfs-encoding">--hdfs-encoding</h4>
<p>The encoding for the backend.</p>
<p>See the <a href="https://rclone.org/overview/#encoding">encoding section in the overview</a> for more info.</p>
<p>Properties:</p>
<ul>
<li>Config: encoding</li>
<li>Env Var: RCLONE_HDFS_ENCODING</li>
<li>Type: Encoding</li>
<li>Default: Slash,Colon,Del,Ctl,InvalidUtf8,Dot</li>
</ul>
<h4 id="hdfs-description">--hdfs-description</h4>
<p>Description of the remote.</p>
<p>Properties:</p>
<ul>
<li>Config: description</li>
<li>Env Var: RCLONE_HDFS_DESCRIPTION</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h2 id="limitations-16">Limitations</h2>
<ul>
<li>No server-side <code>Move</code> or <code>DirMove</code>.</li>
<li>Checksums not implemented.</li>
</ul>
<h1 id="hidrive">HiDrive</h1>
<p>Paths are specified as <code>remote:path</code></p>
<p>Paths may be as deep as required, e.g. <code>remote:directory/subdirectory</code>.</p>
<p>The initial setup for hidrive involves getting a token from HiDrive which you need to do in your browser. <code>rclone config</code> walks you through it.</p>
<h2 id="configuration-20">Configuration</h2>
<p>Here is an example of how to make a remote called <code>remote</code>. First run:</p>
<pre><code> rclone config</code></pre>
<p>This will guide you through an interactive setup process:</p>
<pre><code>No remotes found - make a new one
n) New remote
s) Set configuration password
q) Quit config
n/s/q&gt; n
name&gt; remote
Type of storage to configure.
Choose a number from below, or type in your own value
[snip]
XX / HiDrive
   \ &quot;hidrive&quot;
[snip]
Storage&gt; hidrive
OAuth Client Id - Leave blank normally.
client_id&gt;
OAuth Client Secret - Leave blank normally.
client_secret&gt;
Access permissions that rclone should use when requesting access from HiDrive.
Leave blank normally.
scope_access&gt;
Edit advanced config?
y/n&gt; n
Use web browser to automatically authenticate rclone with remote?
 * Say Y if the machine running rclone has a web browser you can use
 * Say N if running rclone on a (remote) machine without web browser access
If not sure try Y. If Y failed, try N.
y/n&gt; y
If your browser doesn&#39;t open automatically go to the following link: http://127.0.0.1:53682/auth?state=xxxxxxxxxxxxxxxxxxxxxx
Log in and authorize rclone for access
Waiting for code...
Got code
Configuration complete.
Options:
- type: hidrive
- token: {&quot;access_token&quot;:&quot;xxxxxxxxxxxxxxxxxxxx&quot;,&quot;token_type&quot;:&quot;Bearer&quot;,&quot;refresh_token&quot;:&quot;xxxxxxxxxxxxxxxxxxxxxxx&quot;,&quot;expiry&quot;:&quot;xxxxxxxxxxxxxxxxxxxxxxx&quot;}
Keep this &quot;remote&quot; remote?
y) Yes this is OK (default)
e) Edit this remote
d) Delete this remote
y/e/d&gt; y</code></pre>
<p><strong>You should be aware that OAuth-tokens can be used to access your account and hence should not be shared with other persons.</strong> See the <a href="#keeping-your-tokens-safe">below section</a> for more information.</p>
<p>See the <a href="https://rclone.org/remote_setup/">remote setup docs</a> for how to set it up on a machine with no Internet browser available.</p>
<p>Note that rclone runs a webserver on your local machine to collect the token as returned from HiDrive. This only runs from the moment it opens your browser to the moment you get back the verification code. The webserver runs on <code>http://127.0.0.1:53682/</code>. If local port <code>53682</code> is protected by a firewall you may need to temporarily unblock the firewall to complete authorization.</p>
<p>Once configured you can then use <code>rclone</code> like this,</p>
<p>List directories in top level of your HiDrive root folder</p>
<pre><code>rclone lsd remote:</code></pre>
<p>List all the files in your HiDrive filesystem</p>
<pre><code>rclone ls remote:</code></pre>
<p>To copy a local directory to a HiDrive directory called backup</p>
<pre><code>rclone copy /home/source remote:backup</code></pre>
<h3 id="keeping-your-tokens-safe">Keeping your tokens safe</h3>
<p>Any OAuth-tokens will be stored by rclone in the remote's configuration file as unencrypted text. Anyone can use a valid refresh-token to access your HiDrive filesystem without knowing your password. Therefore you should make sure no one else can access your configuration.</p>
<p>It is possible to encrypt rclone's configuration file. You can find information on securing your configuration file by viewing the <a href="https://rclone.org/docs/#configuration-encryption">configuration encryption docs</a>.</p>
<h3 id="invalid-refresh-token-1">Invalid refresh token</h3>
<p>As can be verified <a href="https://developer.hidrive.com/basics-flows/">here</a>, each <code>refresh_token</code> (for Native Applications) is valid for 60 days. If used to access HiDrivei, its validity will be automatically extended.</p>
<p>This means that if you</p>
<ul>
<li>Don't use the HiDrive remote for 60 days</li>
</ul>
<p>then rclone will return an error which includes a text that implies the refresh token is <em>invalid</em> or <em>expired</em>.</p>
<p>To fix this you will need to authorize rclone to access your HiDrive account again.</p>
<p>Using</p>
<pre><code>rclone config reconnect remote:</code></pre>
<p>the process is very similar to the process of initial setup exemplified before.</p>
<h3 id="modification-times-and-hashes-9">Modification times and hashes</h3>
<p>HiDrive allows modification times to be set on objects accurate to 1 second.</p>
<p>HiDrive supports <a href="https://static.hidrive.com/dev/0001">its own hash type</a> which is used to verify the integrity of file contents after successful transfers.</p>
<h3 id="restricted-filename-characters-12">Restricted filename characters</h3>
<p>HiDrive cannot store files or folders that include <code>/</code> (0x2F) or null-bytes (0x00) in their name. Any other characters can be used in the names of files or folders. Additionally, files or folders cannot be named either of the following: <code>.</code> or <code>..</code></p>
<p>Therefore rclone will automatically replace these characters, if files or folders are stored or accessed with such names.</p>
<p>You can read about how this filename encoding works in general <a href="overview/#restricted-filenames">here</a>.</p>
<p>Keep in mind that HiDrive only supports file or folder names with a length of 255 characters or less.</p>
<h3 id="transfers-3">Transfers</h3>
<p>HiDrive limits file sizes per single request to a maximum of 2 GiB. To allow storage of larger files and allow for better upload performance, the hidrive backend will use a chunked transfer for files larger than 96 MiB. Rclone will upload multiple parts/chunks of the file at the same time. Chunks in the process of being uploaded are buffered in memory, so you may want to restrict this behaviour on systems with limited resources.</p>
<p>You can customize this behaviour using the following options:</p>
<ul>
<li><code>chunk_size</code>: size of file parts</li>
<li><code>upload_cutoff</code>: files larger or equal to this in size will use a chunked transfer</li>
<li><code>upload_concurrency</code>: number of file-parts to upload at the same time</li>
</ul>
<p>See the below section about configuration options for more details.</p>
<h3 id="root-folder">Root folder</h3>
<p>You can set the root folder for rclone. This is the directory that rclone considers to be the root of your HiDrive.</p>
<p>Usually, you will leave this blank, and rclone will use the root of the account.</p>
<p>However, you can set this to restrict rclone to a specific folder hierarchy.</p>
<p>This works by prepending the contents of the <code>root_prefix</code> option to any paths accessed by rclone. For example, the following two ways to access the home directory are equivalent:</p>
<pre><code>rclone lsd --hidrive-root-prefix=&quot;/users/test/&quot; remote:path

rclone lsd remote:/users/test/path</code></pre>
<p>See the below section about configuration options for more details.</p>
<h3 id="directory-member-count">Directory member count</h3>
<p>By default, rclone will know the number of directory members contained in a directory. For example, <code>rclone lsd</code> uses this information.</p>
<p>The acquisition of this information will result in additional time costs for HiDrive's API. When dealing with large directory structures, it may be desirable to circumvent this time cost, especially when this information is not explicitly needed. For this, the <code>disable_fetching_member_count</code> option can be used.</p>
<p>See the below section about configuration options for more details.</p>
<h3 id="standard-options-21">Standard options</h3>
<p>Here are the Standard options specific to hidrive (HiDrive).</p>
<h4 id="hidrive-client-id">--hidrive-client-id</h4>
<p>OAuth Client Id.</p>
<p>Leave blank normally.</p>
<p>Properties:</p>
<ul>
<li>Config: client_id</li>
<li>Env Var: RCLONE_HIDRIVE_CLIENT_ID</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="hidrive-client-secret">--hidrive-client-secret</h4>
<p>OAuth Client Secret.</p>
<p>Leave blank normally.</p>
<p>Properties:</p>
<ul>
<li>Config: client_secret</li>
<li>Env Var: RCLONE_HIDRIVE_CLIENT_SECRET</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="hidrive-scope-access">--hidrive-scope-access</h4>
<p>Access permissions that rclone should use when requesting access from HiDrive.</p>
<p>Properties:</p>
<ul>
<li>Config: scope_access</li>
<li>Env Var: RCLONE_HIDRIVE_SCOPE_ACCESS</li>
<li>Type: string</li>
<li>Default: "rw"</li>
<li>Examples:
<ul>
<li>"rw"
<ul>
<li>Read and write access to resources.</li>
</ul></li>
<li>"ro"
<ul>
<li>Read-only access to resources.</li>
</ul></li>
</ul></li>
</ul>
<h3 id="advanced-options-21">Advanced options</h3>
<p>Here are the Advanced options specific to hidrive (HiDrive).</p>
<h4 id="hidrive-token">--hidrive-token</h4>
<p>OAuth Access Token as a JSON blob.</p>
<p>Properties:</p>
<ul>
<li>Config: token</li>
<li>Env Var: RCLONE_HIDRIVE_TOKEN</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="hidrive-auth-url">--hidrive-auth-url</h4>
<p>Auth server URL.</p>
<p>Leave blank to use the provider defaults.</p>
<p>Properties:</p>
<ul>
<li>Config: auth_url</li>
<li>Env Var: RCLONE_HIDRIVE_AUTH_URL</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="hidrive-token-url">--hidrive-token-url</h4>
<p>Token server url.</p>
<p>Leave blank to use the provider defaults.</p>
<p>Properties:</p>
<ul>
<li>Config: token_url</li>
<li>Env Var: RCLONE_HIDRIVE_TOKEN_URL</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="hidrive-scope-role">--hidrive-scope-role</h4>
<p>User-level that rclone should use when requesting access from HiDrive.</p>
<p>Properties:</p>
<ul>
<li>Config: scope_role</li>
<li>Env Var: RCLONE_HIDRIVE_SCOPE_ROLE</li>
<li>Type: string</li>
<li>Default: "user"</li>
<li>Examples:
<ul>
<li>"user"
<ul>
<li>User-level access to management permissions.</li>
<li>This will be sufficient in most cases.</li>
</ul></li>
<li>"admin"
<ul>
<li>Extensive access to management permissions.</li>
</ul></li>
<li>"owner"
<ul>
<li>Full access to management permissions.</li>
</ul></li>
</ul></li>
</ul>
<h4 id="hidrive-root-prefix">--hidrive-root-prefix</h4>
<p>The root/parent folder for all paths.</p>
<p>Fill in to use the specified folder as the parent for all paths given to the remote. This way rclone can use any folder as its starting point.</p>
<p>Properties:</p>
<ul>
<li>Config: root_prefix</li>
<li>Env Var: RCLONE_HIDRIVE_ROOT_PREFIX</li>
<li>Type: string</li>
<li>Default: "/"</li>
<li>Examples:
<ul>
<li>"/"
<ul>
<li>The topmost directory accessible by rclone.</li>
<li>This will be equivalent with "root" if rclone uses a regular HiDrive user account.</li>
</ul></li>
<li>"root"
<ul>
<li>The topmost directory of the HiDrive user account</li>
</ul></li>
<li>""
<ul>
<li>This specifies that there is no root-prefix for your paths.</li>
<li>When using this you will always need to specify paths to this remote with a valid parent e.g. "remote:/path/to/dir" or "remote:root/path/to/dir".</li>
</ul></li>
</ul></li>
</ul>
<h4 id="hidrive-endpoint">--hidrive-endpoint</h4>
<p>Endpoint for the service.</p>
<p>This is the URL that API-calls will be made to.</p>
<p>Properties:</p>
<ul>
<li>Config: endpoint</li>
<li>Env Var: RCLONE_HIDRIVE_ENDPOINT</li>
<li>Type: string</li>
<li>Default: "https://api.hidrive.strato.com/2.1"</li>
</ul>
<h4 id="hidrive-disable-fetching-member-count">--hidrive-disable-fetching-member-count</h4>
<p>Do not fetch number of objects in directories unless it is absolutely necessary.</p>
<p>Requests may be faster if the number of objects in subdirectories is not fetched.</p>
<p>Properties:</p>
<ul>
<li>Config: disable_fetching_member_count</li>
<li>Env Var: RCLONE_HIDRIVE_DISABLE_FETCHING_MEMBER_COUNT</li>
<li>Type: bool</li>
<li>Default: false</li>
</ul>
<h4 id="hidrive-chunk-size">--hidrive-chunk-size</h4>
<p>Chunksize for chunked uploads.</p>
<p>Any files larger than the configured cutoff (or files of unknown size) will be uploaded in chunks of this size.</p>
<p>The upper limit for this is 2147483647 bytes (about 2.000Gi). That is the maximum amount of bytes a single upload-operation will support. Setting this above the upper limit or to a negative value will cause uploads to fail.</p>
<p>Setting this to larger values may increase the upload speed at the cost of using more memory. It can be set to smaller values smaller to save on memory.</p>
<p>Properties:</p>
<ul>
<li>Config: chunk_size</li>
<li>Env Var: RCLONE_HIDRIVE_CHUNK_SIZE</li>
<li>Type: SizeSuffix</li>
<li>Default: 48Mi</li>
</ul>
<h4 id="hidrive-upload-cutoff">--hidrive-upload-cutoff</h4>
<p>Cutoff/Threshold for chunked uploads.</p>
<p>Any files larger than this will be uploaded in chunks of the configured chunksize.</p>
<p>The upper limit for this is 2147483647 bytes (about 2.000Gi). That is the maximum amount of bytes a single upload-operation will support. Setting this above the upper limit will cause uploads to fail.</p>
<p>Properties:</p>
<ul>
<li>Config: upload_cutoff</li>
<li>Env Var: RCLONE_HIDRIVE_UPLOAD_CUTOFF</li>
<li>Type: SizeSuffix</li>
<li>Default: 96Mi</li>
</ul>
<h4 id="hidrive-upload-concurrency">--hidrive-upload-concurrency</h4>
<p>Concurrency for chunked uploads.</p>
<p>This is the upper limit for how many transfers for the same file are running concurrently. Setting this above to a value smaller than 1 will cause uploads to deadlock.</p>
<p>If you are uploading small numbers of large files over high-speed links and these uploads do not fully utilize your bandwidth, then increasing this may help to speed up the transfers.</p>
<p>Properties:</p>
<ul>
<li>Config: upload_concurrency</li>
<li>Env Var: RCLONE_HIDRIVE_UPLOAD_CONCURRENCY</li>
<li>Type: int</li>
<li>Default: 4</li>
</ul>
<h4 id="hidrive-encoding">--hidrive-encoding</h4>
<p>The encoding for the backend.</p>
<p>See the <a href="https://rclone.org/overview/#encoding">encoding section in the overview</a> for more info.</p>
<p>Properties:</p>
<ul>
<li>Config: encoding</li>
<li>Env Var: RCLONE_HIDRIVE_ENCODING</li>
<li>Type: Encoding</li>
<li>Default: Slash,Dot</li>
</ul>
<h4 id="hidrive-description">--hidrive-description</h4>
<p>Description of the remote.</p>
<p>Properties:</p>
<ul>
<li>Config: description</li>
<li>Env Var: RCLONE_HIDRIVE_DESCRIPTION</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h2 id="limitations-17">Limitations</h2>
<h3 id="symbolic-links">Symbolic links</h3>
<p>HiDrive is able to store symbolic links (<em>symlinks</em>) by design, for example, when unpacked from a zip archive.</p>
<p>There exists no direct mechanism to manage native symlinks in remotes. As such this implementation has chosen to ignore any native symlinks present in the remote. rclone will not be able to access or show any symlinks stored in the hidrive-remote. This means symlinks cannot be individually removed, copied, or moved, except when removing, copying, or moving the parent folder.</p>
<p><em>This does not affect the <code>.rclonelink</code>-files that rclone uses to encode and store symbolic links.</em></p>
<h3 id="sparse-files">Sparse files</h3>
<p>It is possible to store sparse files in HiDrive.</p>
<p>Note that copying a sparse file will expand the holes into null-byte (0x00) regions that will then consume disk space. Likewise, when downloading a sparse file, the resulting file will have null-byte regions in the place of file holes.</p>
<h1 id="http">HTTP</h1>
<p>The HTTP remote is a read only remote for reading files of a webserver. The webserver should provide file listings which rclone will read and turn into a remote. This has been tested with common webservers such as Apache/Nginx/Caddy and will likely work with file listings from most web servers. (If it doesn't then please file an issue, or send a pull request!)</p>
<p>Paths are specified as <code>remote:</code> or <code>remote:path</code>.</p>
<p>The <code>remote:</code> represents the configured <a href="#http-url">url</a>, and any path following it will be resolved relative to this url, according to the URL standard. This means with remote url <code>https://beta.rclone.org/branch</code> and path <code>fix</code>, the resolved URL will be <code>https://beta.rclone.org/branch/fix</code>, while with path <code>/fix</code> the resolved URL will be <code>https://beta.rclone.org/fix</code> as the absolute path is resolved from the root of the domain.</p>
<p>If the path following the <code>remote:</code> ends with <code>/</code> it will be assumed to point to a directory. If the path does not end with <code>/</code>, then a HEAD request is sent and the response used to decide if it it is treated as a file or a directory (run with <code>-vv</code> to see details). When <a href="#http-no-head">--http-no-head</a> is specified, a path without ending <code>/</code> is always assumed to be a file. If rclone incorrectly assumes the path is a file, the solution is to specify the path with ending <code>/</code>. When you know the path is a directory, ending it with <code>/</code> is always better as it avoids the initial HEAD request.</p>
<p>To just download a single file it is easier to use <a href="https://rclone.org/commands/rclone_copyurl/">copyurl</a>.</p>
<h2 id="configuration-21">Configuration</h2>
<p>Here is an example of how to make a remote called <code>remote</code>. First run:</p>
<pre><code> rclone config</code></pre>
<p>This will guide you through an interactive setup process:</p>
<pre><code>No remotes found, make a new one?
n) New remote
s) Set configuration password
q) Quit config
n/s/q&gt; n
name&gt; remote
Type of storage to configure.
Choose a number from below, or type in your own value
[snip]
XX / HTTP
   \ &quot;http&quot;
[snip]
Storage&gt; http
URL of http host to connect to
Choose a number from below, or type in your own value
 1 / Connect to example.com
   \ &quot;https://example.com&quot;
url&gt; https://beta.rclone.org
Remote config
Configuration complete.
Options:
- type: http
- url: https://beta.rclone.org
Keep this &quot;remote&quot; remote?
y) Yes this is OK
e) Edit this remote
d) Delete this remote
y/e/d&gt; y
Current remotes:

Name                 Type
====                 ====
remote               http

e) Edit existing remote
n) New remote
d) Delete remote
r) Rename remote
c) Copy remote
s) Set configuration password
q) Quit config
e/n/d/r/c/s/q&gt; q</code></pre>
<p>This remote is called <code>remote</code> and can now be used like this</p>
<p>See all the top level directories</p>
<pre><code>rclone lsd remote:</code></pre>
<p>List the contents of a directory</p>
<pre><code>rclone ls remote:directory</code></pre>
<p>Sync the remote <code>directory</code> to <code>/home/local/directory</code>, deleting any excess files.</p>
<pre><code>rclone sync --interactive remote:directory /home/local/directory</code></pre>
<h3 id="read-only">Read only</h3>
<p>This remote is read only - you can't upload files to an HTTP server.</p>
<h3 id="modification-times-8">Modification times</h3>
<p>Most HTTP servers store time accurate to 1 second.</p>
<h3 id="checksum-1">Checksum</h3>
<p>No checksums are stored.</p>
<h3 id="usage-without-a-config-file">Usage without a config file</h3>
<p>Since the http remote only has one config parameter it is easy to use without a config file:</p>
<pre><code>rclone lsd --http-url https://beta.rclone.org :http:</code></pre>
<p>or:</p>
<pre><code>rclone lsd :http,url=&#39;https://beta.rclone.org&#39;:</code></pre>
<h3 id="standard-options-22">Standard options</h3>
<p>Here are the Standard options specific to http (HTTP).</p>
<h4 id="http-url">--http-url</h4>
<p>URL of HTTP host to connect to.</p>
<p>E.g. "https://example.com", or "https://user:pass@example.com" to use a username and password.</p>
<p>Properties:</p>
<ul>
<li>Config: url</li>
<li>Env Var: RCLONE_HTTP_URL</li>
<li>Type: string</li>
<li>Required: true</li>
</ul>
<h4 id="http-no-escape">--http-no-escape</h4>
<p>Do not escape URL metacharacters in path names.</p>
<p>Properties:</p>
<ul>
<li>Config: no_escape</li>
<li>Env Var: RCLONE_HTTP_NO_ESCAPE</li>
<li>Type: bool</li>
<li>Default: false</li>
</ul>
<h3 id="advanced-options-22">Advanced options</h3>
<p>Here are the Advanced options specific to http (HTTP).</p>
<h4 id="http-headers">--http-headers</h4>
<p>Set HTTP headers for all transactions.</p>
<p>Use this to set additional HTTP headers for all transactions.</p>
<p>The input format is comma separated list of key,value pairs. Standard <a href="https://godoc.org/encoding/csv">CSV encoding</a> may be used.</p>
<p>For example, to set a Cookie use 'Cookie,name=value', or '"Cookie","name=value"'.</p>
<p>You can set multiple headers, e.g. '"Cookie","name=value","Authorization","xxx"'.</p>
<p>Properties:</p>
<ul>
<li>Config: headers</li>
<li>Env Var: RCLONE_HTTP_HEADERS</li>
<li>Type: CommaSepList</li>
<li>Default:</li>
</ul>
<h4 id="http-no-slash">--http-no-slash</h4>
<p>Set this if the site doesn't end directories with /.</p>
<p>Use this if your target website does not use / on the end of directories.</p>
<p>A / on the end of a path is how rclone normally tells the difference between files and directories. If this flag is set, then rclone will treat all files with Content-Type: text/html as directories and read URLs from them rather than downloading them.</p>
<p>Note that this may cause rclone to confuse genuine HTML files with directories.</p>
<p>Properties:</p>
<ul>
<li>Config: no_slash</li>
<li>Env Var: RCLONE_HTTP_NO_SLASH</li>
<li>Type: bool</li>
<li>Default: false</li>
</ul>
<h4 id="http-no-head">--http-no-head</h4>
<p>Don't use HEAD requests.</p>
<p>HEAD requests are mainly used to find file sizes in dir listing. If your site is being very slow to load then you can try this option. Normally rclone does a HEAD request for each potential file in a directory listing to:</p>
<ul>
<li>find its size</li>
<li>check it really exists</li>
<li>check to see if it is a directory</li>
</ul>
<p>If you set this option, rclone will not do the HEAD request. This will mean that directory listings are much quicker, but rclone won't have the times or sizes of any files, and some files that don't exist may be in the listing.</p>
<p>Properties:</p>
<ul>
<li>Config: no_head</li>
<li>Env Var: RCLONE_HTTP_NO_HEAD</li>
<li>Type: bool</li>
<li>Default: false</li>
</ul>
<h4 id="http-description">--http-description</h4>
<p>Description of the remote.</p>
<p>Properties:</p>
<ul>
<li>Config: description</li>
<li>Env Var: RCLONE_HTTP_DESCRIPTION</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h2 id="backend-commands-6">Backend commands</h2>
<p>Here are the commands specific to the http backend.</p>
<p>Run them with</p>
<pre><code>rclone backend COMMAND remote:</code></pre>
<p>The help below will explain what arguments each command takes.</p>
<p>See the <a href="https://rclone.org/commands/rclone_backend/">backend</a> command for more info on how to pass options and arguments.</p>
<p>These can be run on a running backend using the rc command <a href="https://rclone.org/rc/#backend-command">backend/command</a>.</p>
<h3 id="set-2">set</h3>
<p>Set command for updating the config parameters.</p>
<pre><code>rclone backend set remote: [options] [&lt;arguments&gt;+]</code></pre>
<p>This set command can be used to update the config parameters for a running http backend.</p>
<p>Usage Examples:</p>
<pre><code>rclone backend set remote: [-o opt_name=opt_value] [-o opt_name2=opt_value2]
rclone rc backend/command command=set fs=remote: [-o opt_name=opt_value] [-o opt_name2=opt_value2]
rclone rc backend/command command=set fs=remote: -o url=https://example.com</code></pre>
<p>The option keys are named as they are in the config file.</p>
<p>This rebuilds the connection to the http backend when it is called with the new parameters. Only new parameters need be passed as the values will default to those currently in use.</p>
<p>It doesn't return anything.</p>
<h2 id="limitations-18">Limitations</h2>
<p><code>rclone about</code> is not supported by the HTTP backend. Backends without this capability cannot determine free space for an rclone mount or use policy <code>mfs</code> (most free space) as a member of an rclone union remote.</p>
<p>See <a href="https://rclone.org/overview/#optional-features">List of backends that do not support rclone about</a> and <a href="https://rclone.org/commands/rclone_about/">rclone about</a></p>
<h1 id="imagekit">ImageKit</h1>
<p>This is a backend for the <a href="https://imagekit.io/">ImageKit.io</a> storage service.</p>
<h4 id="about-imagekit">About ImageKit</h4>
<p><a href="https://imagekit.io/">ImageKit.io</a> provides real-time image and video optimizations, transformations, and CDN delivery. Over 1,000 businesses and 70,000 developers trust ImageKit with their images and videos on the web.</p>
<h4 id="accounts-pricing">Accounts &amp; Pricing</h4>
<p>To use this backend, you need to <a href="https://imagekit.io/registration/">create an account</a> on ImageKit. Start with a free plan with generous usage limits. Then, as your requirements grow, upgrade to a plan that best fits your needs. See <a href="https://imagekit.io/plans">the pricing details</a>.</p>
<h2 id="configuration-22">Configuration</h2>
<p>Here is an example of making an imagekit configuration.</p>
<p>Firstly create a <a href="https://imagekit.io/">ImageKit.io</a> account and choose a plan.</p>
<p>You will need to log in and get the <code>publicKey</code> and <code>privateKey</code> for your account from the developer section.</p>
<p>Now run</p>
<pre><code>rclone config</code></pre>
<p>This will guide you through an interactive setup process:</p>
<pre><code>No remotes found, make a new one?
n) New remote
s) Set configuration password
q) Quit config
n/s/q&gt; n

Enter the name for the new remote.
name&gt; imagekit-media-library

Option Storage.
Type of storage to configure.
Choose a number from below, or type in your own value.
[snip]
XX / ImageKit.io
\ (imagekit)
[snip]
Storage&gt; imagekit
  
Option endpoint.
You can find your ImageKit.io URL endpoint in your [dashboard](https://imagekit.io/dashboard/developer/api-keys)
Enter a value.
endpoint&gt; https://ik.imagekit.io/imagekit_id  

Option public_key.
You can find your ImageKit.io public key in your [dashboard](https://imagekit.io/dashboard/developer/api-keys)
Enter a value.
public_key&gt; public_****************************

Option private_key.
You can find your ImageKit.io private key in your [dashboard](https://imagekit.io/dashboard/developer/api-keys)
Enter a value.
private_key&gt; private_****************************

Edit advanced config?
y) Yes
n) No (default)
y/n&gt; n

Configuration complete.
Options:
- type: imagekit
- endpoint: https://ik.imagekit.io/imagekit_id
- public_key: public_****************************
- private_key: private_****************************

Keep this &quot;imagekit-media-library&quot; remote?
y) Yes this is OK (default)
e) Edit this remote
d) Delete this remote
y/e/d&gt; y</code></pre>
<p>List directories in the top level of your Media Library</p>
<pre><code>rclone lsd imagekit-media-library:</code></pre>
<p>Make a new directory.</p>
<pre><code>rclone mkdir imagekit-media-library:directory</code></pre>
<p>List the contents of a directory.</p>
<pre><code>rclone ls imagekit-media-library:directory</code></pre>
<h3 id="modified-time-and-hashes">Modified time and hashes</h3>
<p>ImageKit does not support modification times or hashes yet.</p>
<h3 id="checksums">Checksums</h3>
<p>No checksums are supported.</p>
<h3 id="standard-options-23">Standard options</h3>
<p>Here are the Standard options specific to imagekit (ImageKit.io).</p>
<h4 id="imagekit-endpoint">--imagekit-endpoint</h4>
<p>You can find your ImageKit.io URL endpoint in your <a href="https://imagekit.io/dashboard/developer/api-keys">dashboard</a></p>
<p>Properties:</p>
<ul>
<li>Config: endpoint</li>
<li>Env Var: RCLONE_IMAGEKIT_ENDPOINT</li>
<li>Type: string</li>
<li>Required: true</li>
</ul>
<h4 id="imagekit-public-key">--imagekit-public-key</h4>
<p>You can find your ImageKit.io public key in your <a href="https://imagekit.io/dashboard/developer/api-keys">dashboard</a></p>
<p>Properties:</p>
<ul>
<li>Config: public_key</li>
<li>Env Var: RCLONE_IMAGEKIT_PUBLIC_KEY</li>
<li>Type: string</li>
<li>Required: true</li>
</ul>
<h4 id="imagekit-private-key">--imagekit-private-key</h4>
<p>You can find your ImageKit.io private key in your <a href="https://imagekit.io/dashboard/developer/api-keys">dashboard</a></p>
<p>Properties:</p>
<ul>
<li>Config: private_key</li>
<li>Env Var: RCLONE_IMAGEKIT_PRIVATE_KEY</li>
<li>Type: string</li>
<li>Required: true</li>
</ul>
<h3 id="advanced-options-23">Advanced options</h3>
<p>Here are the Advanced options specific to imagekit (ImageKit.io).</p>
<h4 id="imagekit-only-signed">--imagekit-only-signed</h4>
<p>If you have configured <code>Restrict unsigned image URLs</code> in your dashboard settings, set this to true.</p>
<p>Properties:</p>
<ul>
<li>Config: only_signed</li>
<li>Env Var: RCLONE_IMAGEKIT_ONLY_SIGNED</li>
<li>Type: bool</li>
<li>Default: false</li>
</ul>
<h4 id="imagekit-versions">--imagekit-versions</h4>
<p>Include old versions in directory listings.</p>
<p>Properties:</p>
<ul>
<li>Config: versions</li>
<li>Env Var: RCLONE_IMAGEKIT_VERSIONS</li>
<li>Type: bool</li>
<li>Default: false</li>
</ul>
<h4 id="imagekit-upload-tags">--imagekit-upload-tags</h4>
<p>Tags to add to the uploaded files, e.g. "tag1,tag2".</p>
<p>Properties:</p>
<ul>
<li>Config: upload_tags</li>
<li>Env Var: RCLONE_IMAGEKIT_UPLOAD_TAGS</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="imagekit-encoding">--imagekit-encoding</h4>
<p>The encoding for the backend.</p>
<p>See the <a href="https://rclone.org/overview/#encoding">encoding section in the overview</a> for more info.</p>
<p>Properties:</p>
<ul>
<li>Config: encoding</li>
<li>Env Var: RCLONE_IMAGEKIT_ENCODING</li>
<li>Type: Encoding</li>
<li>Default: Slash,LtGt,DoubleQuote,Dollar,Question,Hash,Percent,BackSlash,Del,Ctl,InvalidUtf8,Dot,SquareBracket</li>
</ul>
<h4 id="imagekit-description">--imagekit-description</h4>
<p>Description of the remote.</p>
<p>Properties:</p>
<ul>
<li>Config: description</li>
<li>Env Var: RCLONE_IMAGEKIT_DESCRIPTION</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h3 id="metadata-10">Metadata</h3>
<p>Any metadata supported by the underlying remote is read and written.</p>
<p>Here are the possible system metadata items for the imagekit backend.</p>
<table>
<colgroup>
<col style="width: 15%" />
<col style="width: 15%" />
<col style="width: 15%" />
<col style="width: 23%" />
<col style="width: 28%" />
</colgroup>
<thead>
<tr class="header">
<th>Name</th>
<th>Help</th>
<th>Type</th>
<th>Example</th>
<th>Read Only</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td>aws-tags</td>
<td>AI generated tags by AWS Rekognition associated with the image</td>
<td>string</td>
<td>tag1,tag2</td>
<td><strong>Y</strong></td>
</tr>
<tr class="even">
<td>btime</td>
<td>Time of file birth (creation) read from Last-Modified header</td>
<td>RFC 3339</td>
<td>2006-01-02T15:04:05.999999999Z07:00</td>
<td><strong>Y</strong></td>
</tr>
<tr class="odd">
<td>custom-coordinates</td>
<td>Custom coordinates of the file</td>
<td>string</td>
<td>0,0,100,100</td>
<td><strong>Y</strong></td>
</tr>
<tr class="even">
<td>file-type</td>
<td>Type of the file</td>
<td>string</td>
<td>image</td>
<td><strong>Y</strong></td>
</tr>
<tr class="odd">
<td>google-tags</td>
<td>AI generated tags by Google Cloud Vision associated with the image</td>
<td>string</td>
<td>tag1,tag2</td>
<td><strong>Y</strong></td>
</tr>
<tr class="even">
<td>has-alpha</td>
<td>Whether the image has alpha channel or not</td>
<td>bool</td>
<td></td>
<td><strong>Y</strong></td>
</tr>
<tr class="odd">
<td>height</td>
<td>Height of the image or video in pixels</td>
<td>int</td>
<td></td>
<td><strong>Y</strong></td>
</tr>
<tr class="even">
<td>is-private-file</td>
<td>Whether the file is private or not</td>
<td>bool</td>
<td></td>
<td><strong>Y</strong></td>
</tr>
<tr class="odd">
<td>size</td>
<td>Size of the object in bytes</td>
<td>int64</td>
<td></td>
<td><strong>Y</strong></td>
</tr>
<tr class="even">
<td>tags</td>
<td>Tags associated with the file</td>
<td>string</td>
<td>tag1,tag2</td>
<td><strong>Y</strong></td>
</tr>
<tr class="odd">
<td>width</td>
<td>Width of the image or video in pixels</td>
<td>int</td>
<td></td>
<td><strong>Y</strong></td>
</tr>
</tbody>
</table>
<p>See the <a href="https://rclone.org/docs/#metadata">metadata</a> docs for more info.</p>
<h1 id="internet-archive">Internet Archive</h1>
<p>The Internet Archive backend utilizes Items on <a href="https://archive.org/">archive.org</a></p>
<p>Refer to <a href="https://archive.org/services/docs/api/ias3.html">IAS3 API documentation</a> for the API this backend uses.</p>
<p>Paths are specified as <code>remote:bucket</code> (or <code>remote:</code> for the <code>lsd</code> command.) You may put subdirectories in too, e.g. <code>remote:item/path/to/dir</code>.</p>
<p>Unlike S3, listing up all items uploaded by you isn't supported.</p>
<p>Once you have made a remote, you can use it like this:</p>
<p>Make a new item</p>
<pre><code>rclone mkdir remote:item</code></pre>
<p>List the contents of a item</p>
<pre><code>rclone ls remote:item</code></pre>
<p>Sync <code>/home/local/directory</code> to the remote item, deleting any excess files in the item.</p>
<pre><code>rclone sync --interactive /home/local/directory remote:item</code></pre>
<h2 id="notes">Notes</h2>
<p>Because of Internet Archive's architecture, it enqueues write operations (and extra post-processings) in a per-item queue. You can check item's queue at https://catalogd.archive.org/history/item-name-here . Because of that, all uploads/deletes will not show up immediately and takes some time to be available. The per-item queue is enqueued to an another queue, Item Deriver Queue. <a href="https://catalogd.archive.org/catalog.php?whereami=1">You can check the status of Item Deriver Queue here.</a> This queue has a limit, and it may block you from uploading, or even deleting. You should avoid uploading a lot of small files for better behavior.</p>
<p>You can optionally wait for the server's processing to finish, by setting non-zero value to <code>wait_archive</code> key. By making it wait, rclone can do normal file comparison. Make sure to set a large enough value (e.g. <code>30m0s</code> for smaller files) as it can take a long time depending on server's queue.</p>
<h2 id="about-metadata">About metadata</h2>
<p>This backend supports setting, updating and reading metadata of each file. The metadata will appear as file metadata on Internet Archive. However, some fields are reserved by both Internet Archive and rclone.</p>
<p>The following are reserved by Internet Archive: - <code>name</code> - <code>source</code> - <code>size</code> - <code>md5</code> - <code>crc32</code> - <code>sha1</code> - <code>format</code> - <code>old_version</code> - <code>viruscheck</code> - <code>summation</code></p>
<p>Trying to set values to these keys is ignored with a warning. Only setting <code>mtime</code> is an exception. Doing so make it the identical behavior as setting ModTime.</p>
<p>rclone reserves all the keys starting with <code>rclone-</code>. Setting value for these keys will give you warnings, but values are set according to request.</p>
<p>If there are multiple values for a key, only the first one is returned. This is a limitation of rclone, that supports one value per one key. It can be triggered when you did a server-side copy.</p>
<p>Reading metadata will also provide custom (non-standard nor reserved) ones.</p>
<h2 id="filtering-auto-generated-files">Filtering auto generated files</h2>
<p>The Internet Archive automatically creates metadata files after upload. These can cause problems when doing an <code>rclone sync</code> as rclone will try, and fail, to delete them. These metadata files are not changeable, as they are created by the Internet Archive automatically.</p>
<p>These auto-created files can be excluded from the sync using <a href="https://rclone.org/filtering/#metadata">metadata filtering</a>.</p>
<pre><code>rclone sync ... --metadata-exclude &quot;source=metadata&quot; --metadata-exclude &quot;format=Metadata&quot;</code></pre>
<p>Which excludes from the sync any files which have the <code>source=metadata</code> or <code>format=Metadata</code> flags which are added to Internet Archive auto-created files.</p>
<h2 id="configuration-23">Configuration</h2>
<p>Here is an example of making an internetarchive configuration. Most applies to the other providers as well, any differences are described <a href="#providers">below</a>.</p>
<p>First run</p>
<pre><code>rclone config</code></pre>
<p>This will guide you through an interactive setup process.</p>
<pre><code>No remotes found, make a new one?
n) New remote
s) Set configuration password
q) Quit config
n/s/q&gt; n
name&gt; remote
Option Storage.
Type of storage to configure.
Choose a number from below, or type in your own value.
XX / InternetArchive Items
   \ (internetarchive)
Storage&gt; internetarchive
Option access_key_id.
IAS3 Access Key.
Leave blank for anonymous access.
You can find one here: https://archive.org/account/s3.php
Enter a value. Press Enter to leave empty.
access_key_id&gt; XXXX
Option secret_access_key.
IAS3 Secret Key (password).
Leave blank for anonymous access.
Enter a value. Press Enter to leave empty.
secret_access_key&gt; XXXX
Edit advanced config?
y) Yes
n) No (default)
y/n&gt; y
Option endpoint.
IAS3 Endpoint.
Leave blank for default value.
Enter a string value. Press Enter for the default (https://s3.us.archive.org).
endpoint&gt; 
Option front_endpoint.
Host of InternetArchive Frontend.
Leave blank for default value.
Enter a string value. Press Enter for the default (https://archive.org).
front_endpoint&gt; 
Option disable_checksum.
Don&#39;t store MD5 checksum with object metadata.
Normally rclone will calculate the MD5 checksum of the input before
uploading it so it can ask the server to check the object against checksum.
This is great for data integrity checking but can cause long delays for
large files to start uploading.
Enter a boolean value (true or false). Press Enter for the default (true).
disable_checksum&gt; true
Option encoding.
The encoding for the backend.
See the [encoding section in the overview](https://rclone.org/overview/#encoding) for more info.
Enter a encoder.MultiEncoder value. Press Enter for the default (Slash,Question,Hash,Percent,Del,Ctl,InvalidUtf8,Dot).
encoding&gt; 
Edit advanced config?
y) Yes
n) No (default)
y/n&gt; n
Configuration complete.
Options:
- type: internetarchive
- access_key_id: XXXX
- secret_access_key: XXXX
Keep this &quot;remote&quot; remote?
y) Yes this is OK (default)
e) Edit this remote
d) Delete this remote
y/e/d&gt; y</code></pre>
<h3 id="standard-options-24">Standard options</h3>
<p>Here are the Standard options specific to internetarchive (Internet Archive).</p>
<h4 id="internetarchive-access-key-id">--internetarchive-access-key-id</h4>
<p>IAS3 Access Key.</p>
<p>Leave blank for anonymous access. You can find one here: https://archive.org/account/s3.php</p>
<p>Properties:</p>
<ul>
<li>Config: access_key_id</li>
<li>Env Var: RCLONE_INTERNETARCHIVE_ACCESS_KEY_ID</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="internetarchive-secret-access-key">--internetarchive-secret-access-key</h4>
<p>IAS3 Secret Key (password).</p>
<p>Leave blank for anonymous access.</p>
<p>Properties:</p>
<ul>
<li>Config: secret_access_key</li>
<li>Env Var: RCLONE_INTERNETARCHIVE_SECRET_ACCESS_KEY</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h3 id="advanced-options-24">Advanced options</h3>
<p>Here are the Advanced options specific to internetarchive (Internet Archive).</p>
<h4 id="internetarchive-endpoint">--internetarchive-endpoint</h4>
<p>IAS3 Endpoint.</p>
<p>Leave blank for default value.</p>
<p>Properties:</p>
<ul>
<li>Config: endpoint</li>
<li>Env Var: RCLONE_INTERNETARCHIVE_ENDPOINT</li>
<li>Type: string</li>
<li>Default: "https://s3.us.archive.org"</li>
</ul>
<h4 id="internetarchive-front-endpoint">--internetarchive-front-endpoint</h4>
<p>Host of InternetArchive Frontend.</p>
<p>Leave blank for default value.</p>
<p>Properties:</p>
<ul>
<li>Config: front_endpoint</li>
<li>Env Var: RCLONE_INTERNETARCHIVE_FRONT_ENDPOINT</li>
<li>Type: string</li>
<li>Default: "https://archive.org"</li>
</ul>
<h4 id="internetarchive-disable-checksum">--internetarchive-disable-checksum</h4>
<p>Don't ask the server to test against MD5 checksum calculated by rclone. Normally rclone will calculate the MD5 checksum of the input before uploading it so it can ask the server to check the object against checksum. This is great for data integrity checking but can cause long delays for large files to start uploading.</p>
<p>Properties:</p>
<ul>
<li>Config: disable_checksum</li>
<li>Env Var: RCLONE_INTERNETARCHIVE_DISABLE_CHECKSUM</li>
<li>Type: bool</li>
<li>Default: true</li>
</ul>
<h4 id="internetarchive-wait-archive">--internetarchive-wait-archive</h4>
<p>Timeout for waiting the server's processing tasks (specifically archive and book_op) to finish. Only enable if you need to be guaranteed to be reflected after write operations. 0 to disable waiting. No errors to be thrown in case of timeout.</p>
<p>Properties:</p>
<ul>
<li>Config: wait_archive</li>
<li>Env Var: RCLONE_INTERNETARCHIVE_WAIT_ARCHIVE</li>
<li>Type: Duration</li>
<li>Default: 0s</li>
</ul>
<h4 id="internetarchive-encoding">--internetarchive-encoding</h4>
<p>The encoding for the backend.</p>
<p>See the <a href="https://rclone.org/overview/#encoding">encoding section in the overview</a> for more info.</p>
<p>Properties:</p>
<ul>
<li>Config: encoding</li>
<li>Env Var: RCLONE_INTERNETARCHIVE_ENCODING</li>
<li>Type: Encoding</li>
<li>Default: Slash,LtGt,CrLf,Del,Ctl,InvalidUtf8,Dot</li>
</ul>
<h4 id="internetarchive-description">--internetarchive-description</h4>
<p>Description of the remote.</p>
<p>Properties:</p>
<ul>
<li>Config: description</li>
<li>Env Var: RCLONE_INTERNETARCHIVE_DESCRIPTION</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h3 id="metadata-11">Metadata</h3>
<p>Metadata fields provided by Internet Archive. If there are multiple values for a key, only the first one is returned. This is a limitation of Rclone, that supports one value per one key.</p>
<p>Owner is able to add custom keys. Metadata feature grabs all the keys including them.</p>
<p>Here are the possible system metadata items for the internetarchive backend.</p>
<table>
<colgroup>
<col style="width: 15%" />
<col style="width: 15%" />
<col style="width: 15%" />
<col style="width: 23%" />
<col style="width: 28%" />
</colgroup>
<thead>
<tr class="header">
<th>Name</th>
<th>Help</th>
<th>Type</th>
<th>Example</th>
<th>Read Only</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td>crc32</td>
<td>CRC32 calculated by Internet Archive</td>
<td>string</td>
<td>01234567</td>
<td><strong>Y</strong></td>
</tr>
<tr class="even">
<td>format</td>
<td>Name of format identified by Internet Archive</td>
<td>string</td>
<td>Comma-Separated Values</td>
<td><strong>Y</strong></td>
</tr>
<tr class="odd">
<td>md5</td>
<td>MD5 hash calculated by Internet Archive</td>
<td>string</td>
<td>01234567012345670123456701234567</td>
<td><strong>Y</strong></td>
</tr>
<tr class="even">
<td>mtime</td>
<td>Time of last modification, managed by Rclone</td>
<td>RFC 3339</td>
<td>2006-01-02T15:04:05.999999999Z</td>
<td><strong>Y</strong></td>
</tr>
<tr class="odd">
<td>name</td>
<td>Full file path, without the bucket part</td>
<td>filename</td>
<td>backend/internetarchive/internetarchive.go</td>
<td><strong>Y</strong></td>
</tr>
<tr class="even">
<td>old_version</td>
<td>Whether the file was replaced and moved by keep-old-version flag</td>
<td>boolean</td>
<td>true</td>
<td><strong>Y</strong></td>
</tr>
<tr class="odd">
<td>rclone-ia-mtime</td>
<td>Time of last modification, managed by Internet Archive</td>
<td>RFC 3339</td>
<td>2006-01-02T15:04:05.999999999Z</td>
<td>N</td>
</tr>
<tr class="even">
<td>rclone-mtime</td>
<td>Time of last modification, managed by Rclone</td>
<td>RFC 3339</td>
<td>2006-01-02T15:04:05.999999999Z</td>
<td>N</td>
</tr>
<tr class="odd">
<td>rclone-update-track</td>
<td>Random value used by Rclone for tracking changes inside Internet Archive</td>
<td>string</td>
<td>aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa</td>
<td>N</td>
</tr>
<tr class="even">
<td>sha1</td>
<td>SHA1 hash calculated by Internet Archive</td>
<td>string</td>
<td>0123456701234567012345670123456701234567</td>
<td><strong>Y</strong></td>
</tr>
<tr class="odd">
<td>size</td>
<td>File size in bytes</td>
<td>decimal number</td>
<td>123456</td>
<td><strong>Y</strong></td>
</tr>
<tr class="even">
<td>source</td>
<td>The source of the file</td>
<td>string</td>
<td>original</td>
<td><strong>Y</strong></td>
</tr>
<tr class="odd">
<td>summation</td>
<td>Check https://forum.rclone.org/t/31922 for how it is used</td>
<td>string</td>
<td>md5</td>
<td><strong>Y</strong></td>
</tr>
<tr class="even">
<td>viruscheck</td>
<td>The last time viruscheck process was run for the file (?)</td>
<td>unixtime</td>
<td>1654191352</td>
<td><strong>Y</strong></td>
</tr>
</tbody>
</table>
<p>See the <a href="https://rclone.org/docs/#metadata">metadata</a> docs for more info.</p>
<h1 id="jottacloud">Jottacloud</h1>
<p>Jottacloud is a cloud storage service provider from a Norwegian company, using its own datacenters in Norway. In addition to the official service at <a href="https://www.jottacloud.com/">jottacloud.com</a>, it also provides white-label solutions to different companies, such as: * Telia * Telia Cloud (cloud.telia.se) * Telia Sky (sky.telia.no) * Tele2 * Tele2 Cloud (mittcloud.tele2.se) * Onlime * Onlime Cloud Storage (onlime.dk) * Elkjøp (with subsidiaries): * Elkjøp Cloud (cloud.elkjop.no) * Elgiganten Sweden (cloud.elgiganten.se) * Elgiganten Denmark (cloud.elgiganten.dk) * Giganti Cloud (cloud.gigantti.fi) * ELKO Cloud (cloud.elko.is)</p>
<p>Most of the white-label versions are supported by this backend, although may require different authentication setup - described below.</p>
<p>Paths are specified as <code>remote:path</code></p>
<p>Paths may be as deep as required, e.g. <code>remote:directory/subdirectory</code>.</p>
<h2 id="authentication-types">Authentication types</h2>
<p>Some of the whitelabel versions uses a different authentication method than the official service, and you have to choose the correct one when setting up the remote.</p>
<h3 id="standard-authentication">Standard authentication</h3>
<p>The standard authentication method used by the official service (jottacloud.com), as well as some of the whitelabel services, requires you to generate a single-use personal login token from the account security settings in the service's web interface. Log in to your account, go to "Settings" and then "Security", or use the direct link presented to you by rclone when configuring the remote: <a href="https://www.jottacloud.com/web/secure" class="uri">https://www.jottacloud.com/web/secure</a>. Scroll down to the section "Personal login token", and click the "Generate" button. Note that if you are using a whitelabel service you probably can't use the direct link, you need to find the same page in their dedicated web interface, and also it may be in a different location than described above.</p>
<p>To access your account from multiple instances of rclone, you need to configure each of them with a separate personal login token. E.g. you create a Jottacloud remote with rclone in one location, and copy the configuration file to a second location where you also want to run rclone and access the same remote. Then you need to replace the token for one of them, using the <a href="https://rclone.org/commands/rclone_config_reconnect/">config reconnect</a> command, which requires you to generate a new personal login token and supply as input. If you do not do this, the token may easily end up being invalidated, resulting in both instances failing with an error message something along the lines of:</p>
<pre><code>oauth2: cannot fetch token: 400 Bad Request
Response: {&quot;error&quot;:&quot;invalid_grant&quot;,&quot;error_description&quot;:&quot;Stale token&quot;}</code></pre>
<p>When this happens, you need to replace the token as described above to be able to use your remote again.</p>
<p>All personal login tokens you have taken into use will be listed in the web interface under "My logged in devices", and from the right side of that list you can click the "X" button to revoke individual tokens.</p>
<h3 id="legacy-authentication">Legacy authentication</h3>
<p>If you are using one of the whitelabel versions (e.g. from Elkjøp) you may not have the option to generate a CLI token. In this case you'll have to use the legacy authentication. To do this select yes when the setup asks for legacy authentication and enter your username and password. The rest of the setup is identical to the default setup.</p>
<h3 id="telia-cloud-authentication">Telia Cloud authentication</h3>
<p>Similar to other whitelabel versions Telia Cloud doesn't offer the option of creating a CLI token, and additionally uses a separate authentication flow where the username is generated internally. To setup rclone to use Telia Cloud, choose Telia Cloud authentication in the setup. The rest of the setup is identical to the default setup.</p>
<h3 id="tele2-cloud-authentication">Tele2 Cloud authentication</h3>
<p>As Tele2-Com Hem merger was completed this authentication can be used for former Com Hem Cloud and Tele2 Cloud customers as no support for creating a CLI token exists, and additionally uses a separate authentication flow where the username is generated internally. To setup rclone to use Tele2 Cloud, choose Tele2 Cloud authentication in the setup. The rest of the setup is identical to the default setup.</p>
<h3 id="onlime-cloud-storage-authentication">Onlime Cloud Storage authentication</h3>
<p>Onlime has sold access to Jottacloud proper, while providing localized support to Danish Customers, but have recently set up their own hosting, transferring their customers from Jottacloud servers to their own ones.</p>
<p>This, of course, necessitates using their servers for authentication, but otherwise functionality and architecture seems equivalent to Jottacloud.</p>
<p>To setup rclone to use Onlime Cloud Storage, choose Onlime Cloud authentication in the setup. The rest of the setup is identical to the default setup.</p>
<h2 id="configuration-24">Configuration</h2>
<p>Here is an example of how to make a remote called <code>remote</code> with the default setup. First run:</p>
<pre><code>rclone config</code></pre>
<p>This will guide you through an interactive setup process:</p>
<pre><code>No remotes found, make a new one?
n) New remote
s) Set configuration password
q) Quit config
n/s/q&gt; n
name&gt; remote
Option Storage.
Type of storage to configure.
Choose a number from below, or type in your own value.
[snip]
XX / Jottacloud
   \ (jottacloud)
[snip]
Storage&gt; jottacloud
Edit advanced config?
y) Yes
n) No (default)
y/n&gt; n
Option config_type.
Select authentication type.
Choose a number from below, or type in an existing string value.
Press Enter for the default (standard).
   / Standard authentication.
 1 | Use this if you&#39;re a normal Jottacloud user.
   \ (standard)
   / Legacy authentication.
 2 | This is only required for certain whitelabel versions of Jottacloud and not recommended for normal users.
   \ (legacy)
   / Telia Cloud authentication.
 3 | Use this if you are using Telia Cloud.
   \ (telia)
   / Tele2 Cloud authentication.
 4 | Use this if you are using Tele2 Cloud.
   \ (tele2)
   / Onlime Cloud authentication.
 5 | Use this if you are using Onlime Cloud.
   \ (onlime)
config_type&gt; 1
Personal login token.
Generate here: https://www.jottacloud.com/web/secure
Login Token&gt; &lt;your token here&gt;
Use a non-standard device/mountpoint?
Choosing no, the default, will let you access the storage used for the archive
section of the official Jottacloud client. If you instead want to access the
sync or the backup section, for example, you must choose yes.
y) Yes
n) No (default)
y/n&gt; y
Option config_device.
The device to use. In standard setup the built-in Jotta device is used,
which contains predefined mountpoints for archive, sync etc. All other devices
are treated as backup devices by the official Jottacloud client. You may create
a new by entering a unique name.
Choose a number from below, or type in your own string value.
Press Enter for the default (DESKTOP-3H31129).
 1 &gt; DESKTOP-3H31129
 2 &gt; Jotta
config_device&gt; 2
Option config_mountpoint.
The mountpoint to use for the built-in device Jotta.
The standard setup is to use the Archive mountpoint. Most other mountpoints
have very limited support in rclone and should generally be avoided.
Choose a number from below, or type in an existing string value.
Press Enter for the default (Archive).
 1 &gt; Archive
 2 &gt; Shared
 3 &gt; Sync
config_mountpoint&gt; 1
Configuration complete.
Options:
- type: jottacloud
- configVersion: 1
- client_id: jottacli
- client_secret:
- tokenURL: https://id.jottacloud.com/auth/realms/jottacloud/protocol/openid-connect/token
- token: {........}
- username: 2940e57271a93d987d6f8a21
- device: Jotta
- mountpoint: Archive
Keep this &quot;remote&quot; remote?
y) Yes this is OK (default)
e) Edit this remote
d) Delete this remote
y/e/d&gt; y</code></pre>
<p>Once configured you can then use <code>rclone</code> like this,</p>
<p>List directories in top level of your Jottacloud</p>
<pre><code>rclone lsd remote:</code></pre>
<p>List all the files in your Jottacloud</p>
<pre><code>rclone ls remote:</code></pre>
<p>To copy a local directory to an Jottacloud directory called backup</p>
<pre><code>rclone copy /home/source remote:backup</code></pre>
<h3 id="devices-and-mountpoints">Devices and Mountpoints</h3>
<p>The official Jottacloud client registers a device for each computer you install it on, and shows them in the backup section of the user interface. For each folder you select for backup it will create a mountpoint within this device. A built-in device called Jotta is special, and contains mountpoints Archive, Sync and some others, used for corresponding features in official clients.</p>
<p>With rclone you'll want to use the standard Jotta/Archive device/mountpoint in most cases. However, you may for example want to access files from the sync or backup functionality provided by the official clients, and rclone therefore provides the option to select other devices and mountpoints during config.</p>
<p>You are allowed to create new devices and mountpoints. All devices except the built-in Jotta device are treated as backup devices by official Jottacloud clients, and the mountpoints on them are individual backup sets.</p>
<p>With the built-in Jotta device, only existing, built-in, mountpoints can be selected. In addition to the mentioned Archive and Sync, it may contain several other mountpoints such as: Latest, Links, Shared and Trash. All of these are special mountpoints with a different internal representation than the "regular" mountpoints. Rclone will only to a very limited degree support them. Generally you should avoid these, unless you know what you are doing.</p>
<h3 id="fast-list-4">--fast-list</h3>
<p>This backend supports <code>--fast-list</code> which allows you to use fewer transactions in exchange for more memory. See the <a href="https://rclone.org/docs/#fast-list">rclone docs</a> for more details.</p>
<p>Note that the implementation in Jottacloud always uses only a single API request to get the entire list, so for large folders this could lead to long wait time before the first results are shown.</p>
<p>Note also that with rclone version 1.58 and newer, information about <a href="https://rclone.org/overview/#mime-type">MIME types</a> and metadata item <a href="#metadata">utime</a> are not available when using <code>--fast-list</code>.</p>
<h3 id="modification-times-and-hashes-10">Modification times and hashes</h3>
<p>Jottacloud allows modification times to be set on objects accurate to 1 second. These will be used to detect whether objects need syncing or not.</p>
<p>Jottacloud supports MD5 type hashes, so you can use the <code>--checksum</code> flag.</p>
<p>Note that Jottacloud requires the MD5 hash before upload so if the source does not have an MD5 checksum then the file will be cached temporarily on disk (in location given by <a href="https://rclone.org/docs/#temp-dir-dir">--temp-dir</a>) before it is uploaded. Small files will be cached in memory - see the <a href="#jottacloud-md5-memory-limit">--jottacloud-md5-memory-limit</a> flag. When uploading from local disk the source checksum is always available, so this does not apply. Starting with rclone version 1.52 the same is true for encrypted remotes (in older versions the crypt backend would not calculate hashes for uploads from local disk, so the Jottacloud backend had to do it as described above).</p>
<h3 id="restricted-filename-characters-13">Restricted filename characters</h3>
<p>In addition to the <a href="https://rclone.org/overview/#restricted-characters">default restricted characters set</a> the following characters are also replaced:</p>
<table>
<thead>
<tr class="header">
<th>Character</th>
<th style="text-align: center;">Value</th>
<th style="text-align: center;">Replacement</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td>"</td>
<td style="text-align: center;">0x22</td>
<td style="text-align: center;">＂</td>
</tr>
<tr class="even">
<td>*</td>
<td style="text-align: center;">0x2A</td>
<td style="text-align: center;">＊</td>
</tr>
<tr class="odd">
<td>:</td>
<td style="text-align: center;">0x3A</td>
<td style="text-align: center;">：</td>
</tr>
<tr class="even">
<td>&lt;</td>
<td style="text-align: center;">0x3C</td>
<td style="text-align: center;">＜</td>
</tr>
<tr class="odd">
<td>&gt;</td>
<td style="text-align: center;">0x3E</td>
<td style="text-align: center;">＞</td>
</tr>
<tr class="even">
<td>?</td>
<td style="text-align: center;">0x3F</td>
<td style="text-align: center;">？</td>
</tr>
<tr class="odd">
<td>|</td>
<td style="text-align: center;">0x7C</td>
<td style="text-align: center;">｜</td>
</tr>
</tbody>
</table>
<p>Invalid UTF-8 bytes will also be <a href="https://rclone.org/overview/#invalid-utf8">replaced</a>, as they can't be used in XML strings.</p>
<h3 id="deleting-files-3">Deleting files</h3>
<p>By default, rclone will send all files to the trash when deleting files. They will be permanently deleted automatically after 30 days. You may bypass the trash and permanently delete files immediately by using the <a href="#jottacloud-hard-delete">--jottacloud-hard-delete</a> flag, or set the equivalent environment variable. Emptying the trash is supported by the <a href="https://rclone.org/commands/rclone_cleanup/">cleanup</a> command.</p>
<h3 id="versions-3">Versions</h3>
<p>Jottacloud supports file versioning. When rclone uploads a new version of a file it creates a new version of it. Currently rclone only supports retrieving the current version but older versions can be accessed via the Jottacloud Website.</p>
<p>Versioning can be disabled by <code>--jottacloud-no-versions</code> option. This is achieved by deleting the remote file prior to uploading a new version. If the upload the fails no version of the file will be available in the remote.</p>
<h3 id="quota-information-1">Quota information</h3>
<p>To view your current quota you can use the <code>rclone about remote:</code> command which will display your usage limit (unless it is unlimited) and the current usage.</p>
<h3 id="standard-options-25">Standard options</h3>
<p>Here are the Standard options specific to jottacloud (Jottacloud).</p>
<h4 id="jottacloud-client-id">--jottacloud-client-id</h4>
<p>OAuth Client Id.</p>
<p>Leave blank normally.</p>
<p>Properties:</p>
<ul>
<li>Config: client_id</li>
<li>Env Var: RCLONE_JOTTACLOUD_CLIENT_ID</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="jottacloud-client-secret">--jottacloud-client-secret</h4>
<p>OAuth Client Secret.</p>
<p>Leave blank normally.</p>
<p>Properties:</p>
<ul>
<li>Config: client_secret</li>
<li>Env Var: RCLONE_JOTTACLOUD_CLIENT_SECRET</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h3 id="advanced-options-25">Advanced options</h3>
<p>Here are the Advanced options specific to jottacloud (Jottacloud).</p>
<h4 id="jottacloud-token">--jottacloud-token</h4>
<p>OAuth Access Token as a JSON blob.</p>
<p>Properties:</p>
<ul>
<li>Config: token</li>
<li>Env Var: RCLONE_JOTTACLOUD_TOKEN</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="jottacloud-auth-url">--jottacloud-auth-url</h4>
<p>Auth server URL.</p>
<p>Leave blank to use the provider defaults.</p>
<p>Properties:</p>
<ul>
<li>Config: auth_url</li>
<li>Env Var: RCLONE_JOTTACLOUD_AUTH_URL</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="jottacloud-token-url">--jottacloud-token-url</h4>
<p>Token server url.</p>
<p>Leave blank to use the provider defaults.</p>
<p>Properties:</p>
<ul>
<li>Config: token_url</li>
<li>Env Var: RCLONE_JOTTACLOUD_TOKEN_URL</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="jottacloud-md5-memory-limit">--jottacloud-md5-memory-limit</h4>
<p>Files bigger than this will be cached on disk to calculate the MD5 if required.</p>
<p>Properties:</p>
<ul>
<li>Config: md5_memory_limit</li>
<li>Env Var: RCLONE_JOTTACLOUD_MD5_MEMORY_LIMIT</li>
<li>Type: SizeSuffix</li>
<li>Default: 10Mi</li>
</ul>
<h4 id="jottacloud-trashed-only">--jottacloud-trashed-only</h4>
<p>Only show files that are in the trash.</p>
<p>This will show trashed files in their original directory structure.</p>
<p>Properties:</p>
<ul>
<li>Config: trashed_only</li>
<li>Env Var: RCLONE_JOTTACLOUD_TRASHED_ONLY</li>
<li>Type: bool</li>
<li>Default: false</li>
</ul>
<h4 id="jottacloud-hard-delete">--jottacloud-hard-delete</h4>
<p>Delete files permanently rather than putting them into the trash.</p>
<p>Properties:</p>
<ul>
<li>Config: hard_delete</li>
<li>Env Var: RCLONE_JOTTACLOUD_HARD_DELETE</li>
<li>Type: bool</li>
<li>Default: false</li>
</ul>
<h4 id="jottacloud-upload-resume-limit">--jottacloud-upload-resume-limit</h4>
<p>Files bigger than this can be resumed if the upload fail's.</p>
<p>Properties:</p>
<ul>
<li>Config: upload_resume_limit</li>
<li>Env Var: RCLONE_JOTTACLOUD_UPLOAD_RESUME_LIMIT</li>
<li>Type: SizeSuffix</li>
<li>Default: 10Mi</li>
</ul>
<h4 id="jottacloud-no-versions">--jottacloud-no-versions</h4>
<p>Avoid server side versioning by deleting files and recreating files instead of overwriting them.</p>
<p>Properties:</p>
<ul>
<li>Config: no_versions</li>
<li>Env Var: RCLONE_JOTTACLOUD_NO_VERSIONS</li>
<li>Type: bool</li>
<li>Default: false</li>
</ul>
<h4 id="jottacloud-encoding">--jottacloud-encoding</h4>
<p>The encoding for the backend.</p>
<p>See the <a href="https://rclone.org/overview/#encoding">encoding section in the overview</a> for more info.</p>
<p>Properties:</p>
<ul>
<li>Config: encoding</li>
<li>Env Var: RCLONE_JOTTACLOUD_ENCODING</li>
<li>Type: Encoding</li>
<li>Default: Slash,LtGt,DoubleQuote,Colon,Question,Asterisk,Pipe,Del,Ctl,InvalidUtf8,Dot</li>
</ul>
<h4 id="jottacloud-description">--jottacloud-description</h4>
<p>Description of the remote.</p>
<p>Properties:</p>
<ul>
<li>Config: description</li>
<li>Env Var: RCLONE_JOTTACLOUD_DESCRIPTION</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h3 id="metadata-12">Metadata</h3>
<p>Jottacloud has limited support for metadata, currently an extended set of timestamps.</p>
<p>Here are the possible system metadata items for the jottacloud backend.</p>
<table>
<colgroup>
<col style="width: 15%" />
<col style="width: 15%" />
<col style="width: 15%" />
<col style="width: 23%" />
<col style="width: 28%" />
</colgroup>
<thead>
<tr class="header">
<th>Name</th>
<th>Help</th>
<th>Type</th>
<th>Example</th>
<th>Read Only</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td>btime</td>
<td>Time of file birth (creation), read from rclone metadata</td>
<td>RFC 3339</td>
<td>2006-01-02T15:04:05.999999999Z07:00</td>
<td>N</td>
</tr>
<tr class="even">
<td>content-type</td>
<td>MIME type, also known as media type</td>
<td>string</td>
<td>text/plain</td>
<td><strong>Y</strong></td>
</tr>
<tr class="odd">
<td>mtime</td>
<td>Time of last modification, read from rclone metadata</td>
<td>RFC 3339</td>
<td>2006-01-02T15:04:05.999999999Z07:00</td>
<td>N</td>
</tr>
<tr class="even">
<td>utime</td>
<td>Time of last upload, when current revision was created, generated by backend</td>
<td>RFC 3339</td>
<td>2006-01-02T15:04:05.999999999Z07:00</td>
<td><strong>Y</strong></td>
</tr>
</tbody>
</table>
<p>See the <a href="https://rclone.org/docs/#metadata">metadata</a> docs for more info.</p>
<h2 id="limitations-19">Limitations</h2>
<p>Note that Jottacloud is case insensitive so you can't have a file called "Hello.doc" and one called "hello.doc".</p>
<p>There are quite a few characters that can't be in Jottacloud file names. Rclone will map these names to and from an identical looking unicode equivalent. For example if a file has a ? in it will be mapped to ？ instead.</p>
<p>Jottacloud only supports filenames up to 255 characters in length.</p>
<h2 id="troubleshooting-1">Troubleshooting</h2>
<p>Jottacloud exhibits some inconsistent behaviours regarding deleted files and folders which may cause Copy, Move and DirMove operations to previously deleted paths to fail. Emptying the trash should help in such cases.</p>
<h1 id="koofr">Koofr</h1>
<p>Paths are specified as <code>remote:path</code></p>
<p>Paths may be as deep as required, e.g. <code>remote:directory/subdirectory</code>.</p>
<h2 id="configuration-25">Configuration</h2>
<p>The initial setup for Koofr involves creating an application password for rclone. You can do that by opening the Koofr <a href="https://app.koofr.net/app/admin/preferences/password">web application</a>, giving the password a nice name like <code>rclone</code> and clicking on generate.</p>
<p>Here is an example of how to make a remote called <code>koofr</code>. First run:</p>
<pre><code> rclone config</code></pre>
<p>This will guide you through an interactive setup process:</p>
<pre><code>No remotes found, make a new one?
n) New remote
s) Set configuration password
q) Quit config
n/s/q&gt; n
name&gt; koofr
Option Storage.
Type of storage to configure.
Choose a number from below, or type in your own value.
[snip]
22 / Koofr, Digi Storage and other Koofr-compatible storage providers
   \ (koofr)
[snip]
Storage&gt; koofr
Option provider.
Choose your storage provider.
Choose a number from below, or type in your own value.
Press Enter to leave empty.
 1 / Koofr, https://app.koofr.net/
   \ (koofr)
 2 / Digi Storage, https://storage.rcs-rds.ro/
   \ (digistorage)
 3 / Any other Koofr API compatible storage service
   \ (other)
provider&gt; 1    
Option user.
Your user name.
Enter a value.
user&gt; USERNAME
Option password.
Your password for rclone (generate one at https://app.koofr.net/app/admin/preferences/password).
Choose an alternative below.
y) Yes, type in my own password
g) Generate random password
y/g&gt; y
Enter the password:
password:
Confirm the password:
password:
Edit advanced config?
y) Yes
n) No (default)
y/n&gt; n
Remote config
--------------------
[koofr]
type = koofr
provider = koofr
user = USERNAME
password = *** ENCRYPTED ***
--------------------
y) Yes this is OK (default)
e) Edit this remote
d) Delete this remote
y/e/d&gt; y</code></pre>
<p>You can choose to edit advanced config in order to enter your own service URL if you use an on-premise or white label Koofr instance, or choose an alternative mount instead of your primary storage.</p>
<p>Once configured you can then use <code>rclone</code> like this,</p>
<p>List directories in top level of your Koofr</p>
<pre><code>rclone lsd koofr:</code></pre>
<p>List all the files in your Koofr</p>
<pre><code>rclone ls koofr:</code></pre>
<p>To copy a local directory to an Koofr directory called backup</p>
<pre><code>rclone copy /home/source koofr:backup</code></pre>
<h3 id="restricted-filename-characters-14">Restricted filename characters</h3>
<p>In addition to the <a href="https://rclone.org/overview/#restricted-characters">default restricted characters set</a> the following characters are also replaced:</p>
<table>
<thead>
<tr class="header">
<th>Character</th>
<th style="text-align: center;">Value</th>
<th style="text-align: center;">Replacement</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td>\</td>
<td style="text-align: center;">0x5C</td>
<td style="text-align: center;">＼</td>
</tr>
</tbody>
</table>
<p>Invalid UTF-8 bytes will also be <a href="https://rclone.org/overview/#invalid-utf8">replaced</a>, as they can't be used in XML strings.</p>
<h3 id="standard-options-26">Standard options</h3>
<p>Here are the Standard options specific to koofr (Koofr, Digi Storage and other Koofr-compatible storage providers).</p>
<h4 id="koofr-provider">--koofr-provider</h4>
<p>Choose your storage provider.</p>
<p>Properties:</p>
<ul>
<li>Config: provider</li>
<li>Env Var: RCLONE_KOOFR_PROVIDER</li>
<li>Type: string</li>
<li>Required: false</li>
<li>Examples:
<ul>
<li>"koofr"
<ul>
<li>Koofr, https://app.koofr.net/</li>
</ul></li>
<li>"digistorage"
<ul>
<li>Digi Storage, https://storage.rcs-rds.ro/</li>
</ul></li>
<li>"other"
<ul>
<li>Any other Koofr API compatible storage service</li>
</ul></li>
</ul></li>
</ul>
<h4 id="koofr-endpoint">--koofr-endpoint</h4>
<p>The Koofr API endpoint to use.</p>
<p>Properties:</p>
<ul>
<li>Config: endpoint</li>
<li>Env Var: RCLONE_KOOFR_ENDPOINT</li>
<li>Provider: other</li>
<li>Type: string</li>
<li>Required: true</li>
</ul>
<h4 id="koofr-user">--koofr-user</h4>
<p>Your user name.</p>
<p>Properties:</p>
<ul>
<li>Config: user</li>
<li>Env Var: RCLONE_KOOFR_USER</li>
<li>Type: string</li>
<li>Required: true</li>
</ul>
<h4 id="koofr-password">--koofr-password</h4>
<p>Your password for rclone generate one at https://app.koofr.net/app/admin/preferences/password.</p>
<p><strong>NB</strong> Input to this must be obscured - see <a href="https://rclone.org/commands/rclone_obscure/">rclone obscure</a>.</p>
<p>Properties:</p>
<ul>
<li>Config: password</li>
<li>Env Var: RCLONE_KOOFR_PASSWORD</li>
<li>Provider: koofr</li>
<li>Type: string</li>
<li>Required: true</li>
</ul>
<h3 id="advanced-options-26">Advanced options</h3>
<p>Here are the Advanced options specific to koofr (Koofr, Digi Storage and other Koofr-compatible storage providers).</p>
<h4 id="koofr-mountid">--koofr-mountid</h4>
<p>Mount ID of the mount to use.</p>
<p>If omitted, the primary mount is used.</p>
<p>Properties:</p>
<ul>
<li>Config: mountid</li>
<li>Env Var: RCLONE_KOOFR_MOUNTID</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="koofr-setmtime">--koofr-setmtime</h4>
<p>Does the backend support setting modification time.</p>
<p>Set this to false if you use a mount ID that points to a Dropbox or Amazon Drive backend.</p>
<p>Properties:</p>
<ul>
<li>Config: setmtime</li>
<li>Env Var: RCLONE_KOOFR_SETMTIME</li>
<li>Type: bool</li>
<li>Default: true</li>
</ul>
<h4 id="koofr-encoding">--koofr-encoding</h4>
<p>The encoding for the backend.</p>
<p>See the <a href="https://rclone.org/overview/#encoding">encoding section in the overview</a> for more info.</p>
<p>Properties:</p>
<ul>
<li>Config: encoding</li>
<li>Env Var: RCLONE_KOOFR_ENCODING</li>
<li>Type: Encoding</li>
<li>Default: Slash,BackSlash,Del,Ctl,InvalidUtf8,Dot</li>
</ul>
<h4 id="koofr-description">--koofr-description</h4>
<p>Description of the remote.</p>
<p>Properties:</p>
<ul>
<li>Config: description</li>
<li>Env Var: RCLONE_KOOFR_DESCRIPTION</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h2 id="limitations-20">Limitations</h2>
<p>Note that Koofr is case insensitive so you can't have a file called "Hello.doc" and one called "hello.doc".</p>
<h2 id="providers-2">Providers</h2>
<h3 id="koofr-1">Koofr</h3>
<p>This is the original <a href="https://koofr.eu">Koofr</a> storage provider used as main example and described in the <a href="#configuration">configuration</a> section above.</p>
<h3 id="digi-storage">Digi Storage</h3>
<p><a href="https://www.digi.ro/servicii/online/digi-storage">Digi Storage</a> is a cloud storage service run by <a href="https://www.digi.ro/">Digi.ro</a> that provides a Koofr API.</p>
<p>Here is an example of how to make a remote called <code>ds</code>. First run:</p>
<pre><code> rclone config</code></pre>
<p>This will guide you through an interactive setup process:</p>
<pre><code>No remotes found, make a new one?
n) New remote
s) Set configuration password
q) Quit config
n/s/q&gt; n
name&gt; ds
Option Storage.
Type of storage to configure.
Choose a number from below, or type in your own value.
[snip]
22 / Koofr, Digi Storage and other Koofr-compatible storage providers
   \ (koofr)
[snip]
Storage&gt; koofr
Option provider.
Choose your storage provider.
Choose a number from below, or type in your own value.
Press Enter to leave empty.
 1 / Koofr, https://app.koofr.net/
   \ (koofr)
 2 / Digi Storage, https://storage.rcs-rds.ro/
   \ (digistorage)
 3 / Any other Koofr API compatible storage service
   \ (other)
provider&gt; 2
Option user.
Your user name.
Enter a value.
user&gt; USERNAME
Option password.
Your password for rclone (generate one at https://storage.rcs-rds.ro/app/admin/preferences/password).
Choose an alternative below.
y) Yes, type in my own password
g) Generate random password
y/g&gt; y
Enter the password:
password:
Confirm the password:
password:
Edit advanced config?
y) Yes
n) No (default)
y/n&gt; n
--------------------
[ds]
type = koofr
provider = digistorage
user = USERNAME
password = *** ENCRYPTED ***
--------------------
y) Yes this is OK (default)
e) Edit this remote
d) Delete this remote
y/e/d&gt; y</code></pre>
<h3 id="other">Other</h3>
<p>You may also want to use another, public or private storage provider that runs a Koofr API compatible service, by simply providing the base URL to connect to.</p>
<p>Here is an example of how to make a remote called <code>other</code>. First run:</p>
<pre><code> rclone config</code></pre>
<p>This will guide you through an interactive setup process:</p>
<pre><code>No remotes found, make a new one?
n) New remote
s) Set configuration password
q) Quit config
n/s/q&gt; n
name&gt; other
Option Storage.
Type of storage to configure.
Choose a number from below, or type in your own value.
[snip]
22 / Koofr, Digi Storage and other Koofr-compatible storage providers
   \ (koofr)
[snip]
Storage&gt; koofr
Option provider.
Choose your storage provider.
Choose a number from below, or type in your own value.
Press Enter to leave empty.
 1 / Koofr, https://app.koofr.net/
   \ (koofr)
 2 / Digi Storage, https://storage.rcs-rds.ro/
   \ (digistorage)
 3 / Any other Koofr API compatible storage service
   \ (other)
provider&gt; 3
Option endpoint.
The Koofr API endpoint to use.
Enter a value.
endpoint&gt; https://koofr.other.org
Option user.
Your user name.
Enter a value.
user&gt; USERNAME
Option password.
Your password for rclone (generate one at your service&#39;s settings page).
Choose an alternative below.
y) Yes, type in my own password
g) Generate random password
y/g&gt; y
Enter the password:
password:
Confirm the password:
password:
Edit advanced config?
y) Yes
n) No (default)
y/n&gt; n
--------------------
[other]
type = koofr
provider = other
endpoint = https://koofr.other.org
user = USERNAME
password = *** ENCRYPTED ***
--------------------
y) Yes this is OK (default)
e) Edit this remote
d) Delete this remote
y/e/d&gt; y</code></pre>
<h1 id="linkbox">Linkbox</h1>
<p>Linkbox is <a href="https://linkbox.to/">a private cloud drive</a>.</p>
<h2 id="configuration-26">Configuration</h2>
<p>Here is an example of making a remote for Linkbox.</p>
<p>First run:</p>
<pre><code> rclone config</code></pre>
<p>This will guide you through an interactive setup process:</p>
<pre><code>No remotes found, make a new one?
n) New remote
s) Set configuration password
q) Quit config
n/s/q&gt; n

Enter name for new remote.
name&gt; remote

Option Storage.
Type of storage to configure.
Choose a number from below, or type in your own value.
XX / Linkbox
   \ (linkbox)
Storage&gt; XX

Option token.
Token from https://www.linkbox.to/admin/account
Enter a value.
token&gt; testFromCLToken

Configuration complete.
Options:
- type: linkbox
- token: XXXXXXXXXXX
Keep this &quot;linkbox&quot; remote?
y) Yes this is OK (default)
e) Edit this remote
d) Delete this remote
y/e/d&gt; y
</code></pre>
<h3 id="standard-options-27">Standard options</h3>
<p>Here are the Standard options specific to linkbox (Linkbox).</p>
<h4 id="linkbox-token">--linkbox-token</h4>
<p>Token from https://www.linkbox.to/admin/account</p>
<p>Properties:</p>
<ul>
<li>Config: token</li>
<li>Env Var: RCLONE_LINKBOX_TOKEN</li>
<li>Type: string</li>
<li>Required: true</li>
</ul>
<h3 id="advanced-options-27">Advanced options</h3>
<p>Here are the Advanced options specific to linkbox (Linkbox).</p>
<h4 id="linkbox-description">--linkbox-description</h4>
<p>Description of the remote.</p>
<p>Properties:</p>
<ul>
<li>Config: description</li>
<li>Env Var: RCLONE_LINKBOX_DESCRIPTION</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h2 id="limitations-21">Limitations</h2>
<p>Invalid UTF-8 bytes will also be <a href="https://rclone.org/overview/#invalid-utf8">replaced</a>, as they can't be used in JSON strings.</p>
<h1 id="mail.ru-cloud">Mail.ru Cloud</h1>
<p><a href="https://cloud.mail.ru/">Mail.ru Cloud</a> is a cloud storage provided by a Russian internet company <a href="https://mail.ru">Mail.Ru Group</a>. The official desktop client is <a href="https://disk-o.cloud/en">Disk-O:</a>, available on Windows and Mac OS.</p>
<h2 id="features-highlights">Features highlights</h2>
<ul>
<li>Paths may be as deep as required, e.g. <code>remote:directory/subdirectory</code></li>
<li>Files have a <code>last modified time</code> property, directories don't</li>
<li>Deleted files are by default moved to the trash</li>
<li>Files and directories can be shared via public links</li>
<li>Partial uploads or streaming are not supported, file size must be known before upload</li>
<li>Maximum file size is limited to 2G for a free account, unlimited for paid accounts</li>
<li>Storage keeps hash for all files and performs transparent deduplication, the hash algorithm is a modified SHA1</li>
<li>If a particular file is already present in storage, one can quickly submit file hash instead of long file upload (this optimization is supported by rclone)</li>
</ul>
<h2 id="configuration-27">Configuration</h2>
<p>Here is an example of making a mailru configuration.</p>
<p>First create a Mail.ru Cloud account and choose a tariff.</p>
<p>You will need to log in and create an app password for rclone. Rclone <strong>will not work</strong> with your normal username and password - it will give an error like <code>oauth2: server response missing access_token</code>.</p>
<ul>
<li>Click on your user icon in the top right</li>
<li>Go to Security / "Пароль и безопасность"</li>
<li>Click password for apps / "Пароли для внешних приложений"</li>
<li>Add the password - give it a name - eg "rclone"</li>
<li>Copy the password and use this password below - your normal login password won't work.</li>
</ul>
<p>Now run</p>
<pre><code>rclone config</code></pre>
<p>This will guide you through an interactive setup process:</p>
<pre><code>No remotes found, make a new one?
n) New remote
s) Set configuration password
q) Quit config
n/s/q&gt; n
name&gt; remote
Type of storage to configure.
Type of storage to configure.
Enter a string value. Press Enter for the default (&quot;&quot;).
Choose a number from below, or type in your own value
[snip]
XX / Mail.ru Cloud
   \ &quot;mailru&quot;
[snip]
Storage&gt; mailru
User name (usually email)
Enter a string value. Press Enter for the default (&quot;&quot;).
user&gt; username@mail.ru
Password

This must be an app password - rclone will not work with your normal
password. See the Configuration section in the docs for how to make an
app password.
y) Yes type in my own password
g) Generate random password
y/g&gt; y
Enter the password:
password:
Confirm the password:
password:
Skip full upload if there is another file with same data hash.
This feature is called &quot;speedup&quot; or &quot;put by hash&quot;. It is especially efficient
in case of generally available files like popular books, video or audio clips
[snip]
Enter a boolean value (true or false). Press Enter for the default (&quot;true&quot;).
Choose a number from below, or type in your own value
 1 / Enable
   \ &quot;true&quot;
 2 / Disable
   \ &quot;false&quot;
speedup_enable&gt; 1
Edit advanced config? (y/n)
y) Yes
n) No
y/n&gt; n
Remote config
Configuration complete.
Options:
- type: mailru
- user: username@mail.ru
- pass: *** ENCRYPTED ***
- speedup_enable: true
Keep this &quot;remote&quot; remote?
y) Yes this is OK
e) Edit this remote
d) Delete this remote
y/e/d&gt; y</code></pre>
<p>Configuration of this backend does not require a local web browser. You can use the configured backend as shown below:</p>
<p>See top level directories</p>
<pre><code>rclone lsd remote:</code></pre>
<p>Make a new directory</p>
<pre><code>rclone mkdir remote:directory</code></pre>
<p>List the contents of a directory</p>
<pre><code>rclone ls remote:directory</code></pre>
<p>Sync <code>/home/local/directory</code> to the remote path, deleting any excess files in the path.</p>
<pre><code>rclone sync --interactive /home/local/directory remote:directory</code></pre>
<h3 id="modification-times-and-hashes-11">Modification times and hashes</h3>
<p>Files support a modification time attribute with up to 1 second precision. Directories do not have a modification time, which is shown as "Jan 1 1970".</p>
<p>File hashes are supported, with a custom Mail.ru algorithm based on SHA1. If file size is less than or equal to the SHA1 block size (20 bytes), its hash is simply its data right-padded with zero bytes. Hashes of a larger file is computed as a SHA1 of the file data bytes concatenated with a decimal representation of the data length.</p>
<h3 id="emptying-trash-1">Emptying Trash</h3>
<p>Removing a file or directory actually moves it to the trash, which is not visible to rclone but can be seen in a web browser. The trashed file still occupies part of total quota. If you wish to empty your trash and free some quota, you can use the <code>rclone cleanup remote:</code> command, which will permanently delete all your trashed files. This command does not take any path arguments.</p>
<h3 id="quota-information-2">Quota information</h3>
<p>To view your current quota you can use the <code>rclone about remote:</code> command which will display your usage limit (quota) and the current usage.</p>
<h3 id="restricted-filename-characters-15">Restricted filename characters</h3>
<p>In addition to the <a href="https://rclone.org/overview/#restricted-characters">default restricted characters set</a> the following characters are also replaced:</p>
<table>
<thead>
<tr class="header">
<th>Character</th>
<th style="text-align: center;">Value</th>
<th style="text-align: center;">Replacement</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td>"</td>
<td style="text-align: center;">0x22</td>
<td style="text-align: center;">＂</td>
</tr>
<tr class="even">
<td>*</td>
<td style="text-align: center;">0x2A</td>
<td style="text-align: center;">＊</td>
</tr>
<tr class="odd">
<td>:</td>
<td style="text-align: center;">0x3A</td>
<td style="text-align: center;">：</td>
</tr>
<tr class="even">
<td>&lt;</td>
<td style="text-align: center;">0x3C</td>
<td style="text-align: center;">＜</td>
</tr>
<tr class="odd">
<td>&gt;</td>
<td style="text-align: center;">0x3E</td>
<td style="text-align: center;">＞</td>
</tr>
<tr class="even">
<td>?</td>
<td style="text-align: center;">0x3F</td>
<td style="text-align: center;">？</td>
</tr>
<tr class="odd">
<td>\</td>
<td style="text-align: center;">0x5C</td>
<td style="text-align: center;">＼</td>
</tr>
<tr class="even">
<td>|</td>
<td style="text-align: center;">0x7C</td>
<td style="text-align: center;">｜</td>
</tr>
</tbody>
</table>
<p>Invalid UTF-8 bytes will also be <a href="https://rclone.org/overview/#invalid-utf8">replaced</a>, as they can't be used in JSON strings.</p>
<h3 id="standard-options-28">Standard options</h3>
<p>Here are the Standard options specific to mailru (Mail.ru Cloud).</p>
<h4 id="mailru-client-id">--mailru-client-id</h4>
<p>OAuth Client Id.</p>
<p>Leave blank normally.</p>
<p>Properties:</p>
<ul>
<li>Config: client_id</li>
<li>Env Var: RCLONE_MAILRU_CLIENT_ID</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="mailru-client-secret">--mailru-client-secret</h4>
<p>OAuth Client Secret.</p>
<p>Leave blank normally.</p>
<p>Properties:</p>
<ul>
<li>Config: client_secret</li>
<li>Env Var: RCLONE_MAILRU_CLIENT_SECRET</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="mailru-user">--mailru-user</h4>
<p>User name (usually email).</p>
<p>Properties:</p>
<ul>
<li>Config: user</li>
<li>Env Var: RCLONE_MAILRU_USER</li>
<li>Type: string</li>
<li>Required: true</li>
</ul>
<h4 id="mailru-pass">--mailru-pass</h4>
<p>Password.</p>
<p>This must be an app password - rclone will not work with your normal password. See the Configuration section in the docs for how to make an app password.</p>
<p><strong>NB</strong> Input to this must be obscured - see <a href="https://rclone.org/commands/rclone_obscure/">rclone obscure</a>.</p>
<p>Properties:</p>
<ul>
<li>Config: pass</li>
<li>Env Var: RCLONE_MAILRU_PASS</li>
<li>Type: string</li>
<li>Required: true</li>
</ul>
<h4 id="mailru-speedup-enable">--mailru-speedup-enable</h4>
<p>Skip full upload if there is another file with same data hash.</p>
<p>This feature is called "speedup" or "put by hash". It is especially efficient in case of generally available files like popular books, video or audio clips, because files are searched by hash in all accounts of all mailru users. It is meaningless and ineffective if source file is unique or encrypted. Please note that rclone may need local memory and disk space to calculate content hash in advance and decide whether full upload is required. Also, if rclone does not know file size in advance (e.g. in case of streaming or partial uploads), it will not even try this optimization.</p>
<p>Properties:</p>
<ul>
<li>Config: speedup_enable</li>
<li>Env Var: RCLONE_MAILRU_SPEEDUP_ENABLE</li>
<li>Type: bool</li>
<li>Default: true</li>
<li>Examples:
<ul>
<li>"true"
<ul>
<li>Enable</li>
</ul></li>
<li>"false"
<ul>
<li>Disable</li>
</ul></li>
</ul></li>
</ul>
<h3 id="advanced-options-28">Advanced options</h3>
<p>Here are the Advanced options specific to mailru (Mail.ru Cloud).</p>
<h4 id="mailru-token">--mailru-token</h4>
<p>OAuth Access Token as a JSON blob.</p>
<p>Properties:</p>
<ul>
<li>Config: token</li>
<li>Env Var: RCLONE_MAILRU_TOKEN</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="mailru-auth-url">--mailru-auth-url</h4>
<p>Auth server URL.</p>
<p>Leave blank to use the provider defaults.</p>
<p>Properties:</p>
<ul>
<li>Config: auth_url</li>
<li>Env Var: RCLONE_MAILRU_AUTH_URL</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="mailru-token-url">--mailru-token-url</h4>
<p>Token server url.</p>
<p>Leave blank to use the provider defaults.</p>
<p>Properties:</p>
<ul>
<li>Config: token_url</li>
<li>Env Var: RCLONE_MAILRU_TOKEN_URL</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="mailru-speedup-file-patterns">--mailru-speedup-file-patterns</h4>
<p>Comma separated list of file name patterns eligible for speedup (put by hash).</p>
<p>Patterns are case insensitive and can contain '*' or '?' meta characters.</p>
<p>Properties:</p>
<ul>
<li>Config: speedup_file_patterns</li>
<li>Env Var: RCLONE_MAILRU_SPEEDUP_FILE_PATTERNS</li>
<li>Type: string</li>
<li>Default: "<em>.mkv,</em>.avi,<em>.mp4,</em>.mp3,<em>.zip,</em>.gz,<em>.rar,</em>.pdf"</li>
<li>Examples:
<ul>
<li>""
<ul>
<li>Empty list completely disables speedup (put by hash).</li>
</ul></li>
<li>"*"
<ul>
<li>All files will be attempted for speedup.</li>
</ul></li>
<li>"<em>.mkv,</em>.avi,<em>.mp4,</em>.mp3"
<ul>
<li>Only common audio/video files will be tried for put by hash.</li>
</ul></li>
<li>"<em>.zip,</em>.gz,<em>.rar,</em>.pdf"
<ul>
<li>Only common archives or PDF books will be tried for speedup.</li>
</ul></li>
</ul></li>
</ul>
<h4 id="mailru-speedup-max-disk">--mailru-speedup-max-disk</h4>
<p>This option allows you to disable speedup (put by hash) for large files.</p>
<p>Reason is that preliminary hashing can exhaust your RAM or disk space.</p>
<p>Properties:</p>
<ul>
<li>Config: speedup_max_disk</li>
<li>Env Var: RCLONE_MAILRU_SPEEDUP_MAX_DISK</li>
<li>Type: SizeSuffix</li>
<li>Default: 3Gi</li>
<li>Examples:
<ul>
<li>"0"
<ul>
<li>Completely disable speedup (put by hash).</li>
</ul></li>
<li>"1G"
<ul>
<li>Files larger than 1Gb will be uploaded directly.</li>
</ul></li>
<li>"3G"
<ul>
<li>Choose this option if you have less than 3Gb free on local disk.</li>
</ul></li>
</ul></li>
</ul>
<h4 id="mailru-speedup-max-memory">--mailru-speedup-max-memory</h4>
<p>Files larger than the size given below will always be hashed on disk.</p>
<p>Properties:</p>
<ul>
<li>Config: speedup_max_memory</li>
<li>Env Var: RCLONE_MAILRU_SPEEDUP_MAX_MEMORY</li>
<li>Type: SizeSuffix</li>
<li>Default: 32Mi</li>
<li>Examples:
<ul>
<li>"0"
<ul>
<li>Preliminary hashing will always be done in a temporary disk location.</li>
</ul></li>
<li>"32M"
<ul>
<li>Do not dedicate more than 32Mb RAM for preliminary hashing.</li>
</ul></li>
<li>"256M"
<ul>
<li>You have at most 256Mb RAM free for hash calculations.</li>
</ul></li>
</ul></li>
</ul>
<h4 id="mailru-check-hash">--mailru-check-hash</h4>
<p>What should copy do if file checksum is mismatched or invalid.</p>
<p>Properties:</p>
<ul>
<li>Config: check_hash</li>
<li>Env Var: RCLONE_MAILRU_CHECK_HASH</li>
<li>Type: bool</li>
<li>Default: true</li>
<li>Examples:
<ul>
<li>"true"
<ul>
<li>Fail with error.</li>
</ul></li>
<li>"false"
<ul>
<li>Ignore and continue.</li>
</ul></li>
</ul></li>
</ul>
<h4 id="mailru-user-agent">--mailru-user-agent</h4>
<p>HTTP user agent used internally by client.</p>
<p>Defaults to "rclone/VERSION" or "--user-agent" provided on command line.</p>
<p>Properties:</p>
<ul>
<li>Config: user_agent</li>
<li>Env Var: RCLONE_MAILRU_USER_AGENT</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="mailru-quirks">--mailru-quirks</h4>
<p>Comma separated list of internal maintenance flags.</p>
<p>This option must not be used by an ordinary user. It is intended only to facilitate remote troubleshooting of backend issues. Strict meaning of flags is not documented and not guaranteed to persist between releases. Quirks will be removed when the backend grows stable. Supported quirks: atomicmkdir binlist unknowndirs</p>
<p>Properties:</p>
<ul>
<li>Config: quirks</li>
<li>Env Var: RCLONE_MAILRU_QUIRKS</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="mailru-encoding">--mailru-encoding</h4>
<p>The encoding for the backend.</p>
<p>See the <a href="https://rclone.org/overview/#encoding">encoding section in the overview</a> for more info.</p>
<p>Properties:</p>
<ul>
<li>Config: encoding</li>
<li>Env Var: RCLONE_MAILRU_ENCODING</li>
<li>Type: Encoding</li>
<li>Default: Slash,LtGt,DoubleQuote,Colon,Question,Asterisk,Pipe,BackSlash,Del,Ctl,InvalidUtf8,Dot</li>
</ul>
<h4 id="mailru-description">--mailru-description</h4>
<p>Description of the remote.</p>
<p>Properties:</p>
<ul>
<li>Config: description</li>
<li>Env Var: RCLONE_MAILRU_DESCRIPTION</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h2 id="limitations-22">Limitations</h2>
<p>File size limits depend on your account. A single file size is limited by 2G for a free account and unlimited for paid tariffs. Please refer to the Mail.ru site for the total uploaded size limits.</p>
<p>Note that Mailru is case insensitive so you can't have a file called "Hello.doc" and one called "hello.doc".</p>
<h1 id="mega">Mega</h1>
<p><a href="https://mega.nz/">Mega</a> is a cloud storage and file hosting service known for its security feature where all files are encrypted locally before they are uploaded. This prevents anyone (including employees of Mega) from accessing the files without knowledge of the key used for encryption.</p>
<p>This is an rclone backend for Mega which supports the file transfer features of Mega using the same client side encryption.</p>
<p>Paths are specified as <code>remote:path</code></p>
<p>Paths may be as deep as required, e.g. <code>remote:directory/subdirectory</code>.</p>
<h2 id="configuration-28">Configuration</h2>
<p>Here is an example of how to make a remote called <code>remote</code>. First run:</p>
<pre><code> rclone config</code></pre>
<p>This will guide you through an interactive setup process:</p>
<pre><code>No remotes found, make a new one?
n) New remote
s) Set configuration password
q) Quit config
n/s/q&gt; n
name&gt; remote
Type of storage to configure.
Choose a number from below, or type in your own value
[snip]
XX / Mega
   \ &quot;mega&quot;
[snip]
Storage&gt; mega
User name
user&gt; you@example.com
Password.
y) Yes type in my own password
g) Generate random password
n) No leave this optional password blank
y/g/n&gt; y
Enter the password:
password:
Confirm the password:
password:
Remote config
Configuration complete.
Options:
- type: mega
- user: you@example.com
- pass: *** ENCRYPTED ***
Keep this &quot;remote&quot; remote?
y) Yes this is OK
e) Edit this remote
d) Delete this remote
y/e/d&gt; y</code></pre>
<p><strong>NOTE:</strong> The encryption keys need to have been already generated after a regular login via the browser, otherwise attempting to use the credentials in <code>rclone</code> will fail.</p>
<p>Once configured you can then use <code>rclone</code> like this,</p>
<p>List directories in top level of your Mega</p>
<pre><code>rclone lsd remote:</code></pre>
<p>List all the files in your Mega</p>
<pre><code>rclone ls remote:</code></pre>
<p>To copy a local directory to an Mega directory called backup</p>
<pre><code>rclone copy /home/source remote:backup</code></pre>
<h3 id="modification-times-and-hashes-12">Modification times and hashes</h3>
<p>Mega does not support modification times or hashes yet.</p>
<h3 id="restricted-filename-characters-16">Restricted filename characters</h3>
<table>
<thead>
<tr class="header">
<th>Character</th>
<th style="text-align: center;">Value</th>
<th style="text-align: center;">Replacement</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td>NUL</td>
<td style="text-align: center;">0x00</td>
<td style="text-align: center;">␀</td>
</tr>
<tr class="even">
<td>/</td>
<td style="text-align: center;">0x2F</td>
<td style="text-align: center;">／</td>
</tr>
</tbody>
</table>
<p>Invalid UTF-8 bytes will also be <a href="https://rclone.org/overview/#invalid-utf8">replaced</a>, as they can't be used in JSON strings.</p>
<h3 id="duplicated-files-3">Duplicated files</h3>
<p>Mega can have two files with exactly the same name and path (unlike a normal file system).</p>
<p>Duplicated files cause problems with the syncing and you will see messages in the log about duplicates.</p>
<p>Use <code>rclone dedupe</code> to fix duplicated files.</p>
<h3 id="failure-to-log-in">Failure to log-in</h3>
<h4 id="object-not-found">Object not found</h4>
<p>If you are connecting to your Mega remote for the first time, to test access and synchronization, you may receive an error such as</p>
<pre><code>Failed to create file system for &quot;my-mega-remote:&quot;: 
couldn&#39;t login: Object (typically, node or user) not found</code></pre>
<p>The diagnostic steps often recommended in the <a href="https://forum.rclone.org/search?q=mega">rclone forum</a> start with the <strong>MEGAcmd</strong> utility. Note that this refers to the official C++ command from https://github.com/meganz/MEGAcmd and not the go language built command from t3rm1n4l/megacmd that is no longer maintained.</p>
<p>Follow the instructions for installing MEGAcmd and try accessing your remote as they recommend. You can establish whether or not you can log in using MEGAcmd, and obtain diagnostic information to help you, and search or work with others in the forum.</p>
<pre><code>MEGA CMD&gt; login me@example.com
Password:
Fetching nodes ...
Loading transfers from local cache
Login complete as me@example.com
me@example.com:/$ </code></pre>
<p>Note that some have found issues with passwords containing special characters. If you can not log on with rclone, but MEGAcmd logs on just fine, then consider changing your password temporarily to pure alphanumeric characters, in case that helps.</p>
<h4 id="repeated-commands-blocks-access">Repeated commands blocks access</h4>
<p>Mega remotes seem to get blocked (reject logins) under "heavy use". We haven't worked out the exact blocking rules but it seems to be related to fast paced, successive rclone commands.</p>
<p>For example, executing this command 90 times in a row <code>rclone link remote:file</code> will cause the remote to become "blocked". This is not an abnormal situation, for example if you wish to get the public links of a directory with hundred of files... After more or less a week, the remote will remote accept rclone logins normally again.</p>
<p>You can mitigate this issue by mounting the remote it with <code>rclone mount</code>. This will log-in when mounting and a log-out when unmounting only. You can also run <code>rclone rcd</code> and then use <code>rclone rc</code> to run the commands over the API to avoid logging in each time.</p>
<p>Rclone does not currently close mega sessions (you can see them in the web interface), however closing the sessions does not solve the issue.</p>
<p>If you space rclone commands by 3 seconds it will avoid blocking the remote. We haven't identified the exact blocking rules, so perhaps one could execute the command 80 times without waiting and avoid blocking by waiting 3 seconds, then continuing...</p>
<p>Note that this has been observed by trial and error and might not be set in stone.</p>
<p>Other tools seem not to produce this blocking effect, as they use a different working approach (state-based, using sessionIDs instead of log-in) which isn't compatible with the current stateless rclone approach.</p>
<p>Note that once blocked, the use of other tools (such as megacmd) is not a sure workaround: following megacmd login times have been observed in succession for blocked remote: 7 minutes, 20 min, 30min, 30 min, 30min. Web access looks unaffected though.</p>
<p>Investigation is continuing in relation to workarounds based on timeouts, pacers, retrials and tpslimits - if you discover something relevant, please post on the forum.</p>
<p>So, if rclone was working nicely and suddenly you are unable to log-in and you are sure the user and the password are correct, likely you have got the remote blocked for a while.</p>
<h3 id="standard-options-29">Standard options</h3>
<p>Here are the Standard options specific to mega (Mega).</p>
<h4 id="mega-user">--mega-user</h4>
<p>User name.</p>
<p>Properties:</p>
<ul>
<li>Config: user</li>
<li>Env Var: RCLONE_MEGA_USER</li>
<li>Type: string</li>
<li>Required: true</li>
</ul>
<h4 id="mega-pass">--mega-pass</h4>
<p>Password.</p>
<p><strong>NB</strong> Input to this must be obscured - see <a href="https://rclone.org/commands/rclone_obscure/">rclone obscure</a>.</p>
<p>Properties:</p>
<ul>
<li>Config: pass</li>
<li>Env Var: RCLONE_MEGA_PASS</li>
<li>Type: string</li>
<li>Required: true</li>
</ul>
<h3 id="advanced-options-29">Advanced options</h3>
<p>Here are the Advanced options specific to mega (Mega).</p>
<h4 id="mega-debug">--mega-debug</h4>
<p>Output more debug from Mega.</p>
<p>If this flag is set (along with -vv) it will print further debugging information from the mega backend.</p>
<p>Properties:</p>
<ul>
<li>Config: debug</li>
<li>Env Var: RCLONE_MEGA_DEBUG</li>
<li>Type: bool</li>
<li>Default: false</li>
</ul>
<h4 id="mega-hard-delete">--mega-hard-delete</h4>
<p>Delete files permanently rather than putting them into the trash.</p>
<p>Normally the mega backend will put all deletions into the trash rather than permanently deleting them. If you specify this then rclone will permanently delete objects instead.</p>
<p>Properties:</p>
<ul>
<li>Config: hard_delete</li>
<li>Env Var: RCLONE_MEGA_HARD_DELETE</li>
<li>Type: bool</li>
<li>Default: false</li>
</ul>
<h4 id="mega-use-https">--mega-use-https</h4>
<p>Use HTTPS for transfers.</p>
<p>MEGA uses plain text HTTP connections by default. Some ISPs throttle HTTP connections, this causes transfers to become very slow. Enabling this will force MEGA to use HTTPS for all transfers. HTTPS is normally not necessary since all data is already encrypted anyway. Enabling it will increase CPU usage and add network overhead.</p>
<p>Properties:</p>
<ul>
<li>Config: use_https</li>
<li>Env Var: RCLONE_MEGA_USE_HTTPS</li>
<li>Type: bool</li>
<li>Default: false</li>
</ul>
<h4 id="mega-encoding">--mega-encoding</h4>
<p>The encoding for the backend.</p>
<p>See the <a href="https://rclone.org/overview/#encoding">encoding section in the overview</a> for more info.</p>
<p>Properties:</p>
<ul>
<li>Config: encoding</li>
<li>Env Var: RCLONE_MEGA_ENCODING</li>
<li>Type: Encoding</li>
<li>Default: Slash,InvalidUtf8,Dot</li>
</ul>
<h4 id="mega-description">--mega-description</h4>
<p>Description of the remote.</p>
<p>Properties:</p>
<ul>
<li>Config: description</li>
<li>Env Var: RCLONE_MEGA_DESCRIPTION</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h3 id="process-killed">Process <code>killed</code></h3>
<p>On accounts with large files or something else, memory usage can significantly increase when executing list/sync instructions. When running on cloud providers (like AWS with EC2), check if the instance type has sufficient memory/CPU to execute the commands. Use the resource monitoring tools to inspect after sending the commands. Look <a href="https://forum.rclone.org/t/rclone-with-mega-appears-to-work-only-in-some-accounts/40233/4">at this issue</a>.</p>
<h2 id="limitations-23">Limitations</h2>
<p>This backend uses the <a href="https://github.com/t3rm1n4l/go-mega">go-mega go library</a> which is an opensource go library implementing the Mega API. There doesn't appear to be any documentation for the mega protocol beyond the <a href="https://github.com/meganz/sdk">mega C++ SDK</a> source code so there are likely quite a few errors still remaining in this library.</p>
<p>Mega allows duplicate files which may confuse rclone.</p>
<h1 id="memory">Memory</h1>
<p>The memory backend is an in RAM backend. It does not persist its data - use the local backend for that.</p>
<p>The memory backend behaves like a bucket-based remote (e.g. like s3). Because it has no parameters you can just use it with the <code>:memory:</code> remote name.</p>
<h2 id="configuration-29">Configuration</h2>
<p>You can configure it as a remote like this with <code>rclone config</code> too if you want to:</p>
<pre><code>No remotes found, make a new one?
n) New remote
s) Set configuration password
q) Quit config
n/s/q&gt; n
name&gt; remote
Type of storage to configure.
Enter a string value. Press Enter for the default (&quot;&quot;).
Choose a number from below, or type in your own value
[snip]
XX / Memory
   \ &quot;memory&quot;
[snip]
Storage&gt; memory
** See help for memory backend at: https://rclone.org/memory/ **

Remote config

Configuration complete.
Options:
- type: memory
Keep this &quot;remote&quot; remote?
y) Yes this is OK (default)
e) Edit this remote
d) Delete this remote
y/e/d&gt; y</code></pre>
<p>Because the memory backend isn't persistent it is most useful for testing or with an rclone server or rclone mount, e.g.</p>
<pre><code>rclone mount :memory: /mnt/tmp
rclone serve webdav :memory:
rclone serve sftp :memory:</code></pre>
<h3 id="modification-times-and-hashes-13">Modification times and hashes</h3>
<p>The memory backend supports MD5 hashes and modification times accurate to 1 nS.</p>
<h3 id="restricted-filename-characters-17">Restricted filename characters</h3>
<p>The memory backend replaces the <a href="https://rclone.org/overview/#restricted-characters">default restricted characters set</a>.</p>
<h3 id="advanced-options-30">Advanced options</h3>
<p>Here are the Advanced options specific to memory (In memory object storage system.).</p>
<h4 id="memory-description">--memory-description</h4>
<p>Description of the remote.</p>
<p>Properties:</p>
<ul>
<li>Config: description</li>
<li>Env Var: RCLONE_MEMORY_DESCRIPTION</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h1 id="akamai-netstorage">Akamai NetStorage</h1>
<p>Paths are specified as <code>remote:</code> You may put subdirectories in too, e.g. <code>remote:/path/to/dir</code>. If you have a CP code you can use that as the folder after the domain such as &lt;domain&gt;/&lt;cpcode&gt;/&lt;internal directories within cpcode&gt;.</p>
<p>For example, this is commonly configured with or without a CP code: * <strong>With a CP code</strong>. <code>[your-domain-prefix]-nsu.akamaihd.net/123456/subdirectory/</code> * <strong>Without a CP code</strong>. <code>[your-domain-prefix]-nsu.akamaihd.net</code></p>
<p>See all buckets rclone lsd remote: The initial setup for Netstorage involves getting an account and secret. Use <code>rclone config</code> to walk you through the setup process.</p>
<h2 id="configuration-30">Configuration</h2>
<p>Here's an example of how to make a remote called <code>ns1</code>.</p>
<ol type="1">
<li>To begin the interactive configuration process, enter this command:</li>
</ol>
<pre><code>rclone config</code></pre>
<ol start="2" type="1">
<li>Type <code>n</code> to create a new remote.</li>
</ol>
<pre><code>n) New remote
d) Delete remote
q) Quit config
e/n/d/q&gt; n</code></pre>
<ol start="3" type="1">
<li>For this example, enter <code>ns1</code> when you reach the name&gt; prompt.</li>
</ol>
<pre><code>name&gt; ns1</code></pre>
<ol start="4" type="1">
<li>Enter <code>netstorage</code> as the type of storage to configure.</li>
</ol>
<pre><code>Type of storage to configure.
Enter a string value. Press Enter for the default (&quot;&quot;).
Choose a number from below, or type in your own value
XX / NetStorage
   \ &quot;netstorage&quot;
Storage&gt; netstorage</code></pre>
<ol start="5" type="1">
<li>Select between the HTTP or HTTPS protocol. Most users should choose HTTPS, which is the default. HTTP is provided primarily for debugging purposes.</li>
</ol>
<pre><code>Enter a string value. Press Enter for the default (&quot;&quot;).
Choose a number from below, or type in your own value
 1 / HTTP protocol
   \ &quot;http&quot;
 2 / HTTPS protocol
   \ &quot;https&quot;
protocol&gt; 1</code></pre>
<ol start="6" type="1">
<li>Specify your NetStorage host, CP code, and any necessary content paths using this format: <code>&lt;domain&gt;/&lt;cpcode&gt;/&lt;content&gt;/</code></li>
</ol>
<pre><code>Enter a string value. Press Enter for the default (&quot;&quot;).
host&gt; baseball-nsu.akamaihd.net/123456/content/</code></pre>
<ol start="7" type="1">
<li>Set the netstorage account name</li>
</ol>
<pre><code>Enter a string value. Press Enter for the default (&quot;&quot;).
account&gt; username</code></pre>
<ol start="8" type="1">
<li>Set the Netstorage account secret/G2O key which will be used for authentication purposes. Select the <code>y</code> option to set your own password then enter your secret. Note: The secret is stored in the <code>rclone.conf</code> file with hex-encoded encryption.</li>
</ol>
<pre><code>y) Yes type in my own password
g) Generate random password
y/g&gt; y
Enter the password:
password:
Confirm the password:
password:</code></pre>
<ol start="9" type="1">
<li>View the summary and confirm your remote configuration.</li>
</ol>
<pre><code>[ns1]
type = netstorage
protocol = http
host = baseball-nsu.akamaihd.net/123456/content/
account = username
secret = *** ENCRYPTED ***
--------------------
y) Yes this is OK (default)
e) Edit this remote
d) Delete this remote
y/e/d&gt; y</code></pre>
<p>This remote is called <code>ns1</code> and can now be used.</p>
<h2 id="example-operations">Example operations</h2>
<p>Get started with rclone and NetStorage with these examples. For additional rclone commands, visit https://rclone.org/commands/.</p>
<h3 id="see-contents-of-a-directory-in-your-project">See contents of a directory in your project</h3>
<pre><code>rclone lsd ns1:/974012/testing/</code></pre>
<h3 id="sync-the-contents-local-with-remote">Sync the contents local with remote</h3>
<pre><code>rclone sync . ns1:/974012/testing/</code></pre>
<h3 id="upload-local-content-to-remote">Upload local content to remote</h3>
<pre><code>rclone copy notes.txt ns1:/974012/testing/</code></pre>
<h3 id="delete-content-on-remote">Delete content on remote</h3>
<pre><code>rclone delete ns1:/974012/testing/notes.txt</code></pre>
<h3 id="move-or-copy-content-between-cp-codes.">Move or copy content between CP codes.</h3>
<p>Your credentials must have access to two CP codes on the same remote. You can't perform operations between different remotes.</p>
<pre><code>rclone move ns1:/974012/testing/notes.txt ns1:/974450/testing2/</code></pre>
<h2 id="features-2">Features</h2>
<h3 id="symlink-support">Symlink Support</h3>
<p>The Netstorage backend changes the rclone <code>--links, -l</code> behavior. When uploading, instead of creating the .rclonelink file, use the "symlink" API in order to create the corresponding symlink on the remote. The .rclonelink file will not be created, the upload will be intercepted and only the symlink file that matches the source file name with no suffix will be created on the remote.</p>
<p>This will effectively allow commands like copy/copyto, move/moveto and sync to upload from local to remote and download from remote to local directories with symlinks. Due to internal rclone limitations, it is not possible to upload an individual symlink file to any remote backend. You can always use the "backend symlink" command to create a symlink on the NetStorage server, refer to "symlink" section below.</p>
<p>Individual symlink files on the remote can be used with the commands like "cat" to print the destination name, or "delete" to delete symlink, or copy, copy/to and move/moveto to download from the remote to local. Note: individual symlink files on the remote should be specified including the suffix .rclonelink.</p>
<p><strong>Note</strong>: No file with the suffix .rclonelink should ever exist on the server since it is not possible to actually upload/create a file with .rclonelink suffix with rclone, it can only exist if it is manually created through a non-rclone method on the remote.</p>
<h3 id="implicit-vs.-explicit-directories">Implicit vs. Explicit Directories</h3>
<p>With NetStorage, directories can exist in one of two forms:</p>
<ol type="1">
<li><strong>Explicit Directory</strong>. This is an actual, physical directory that you have created in a storage group.</li>
<li><strong>Implicit Directory</strong>. This refers to a directory within a path that has not been physically created. For example, during upload of a file, nonexistent subdirectories can be specified in the target path. NetStorage creates these as "implicit." While the directories aren't physically created, they exist implicitly and the noted path is connected with the uploaded file.</li>
</ol>
<p>Rclone will intercept all file uploads and mkdir commands for the NetStorage remote and will explicitly issue the mkdir command for each directory in the uploading path. This will help with the interoperability with the other Akamai services such as SFTP and the Content Management Shell (CMShell). Rclone will not guarantee correctness of operations with implicit directories which might have been created as a result of using an upload API directly.</p>
<h3 id="fast-list-listr-support"><code>--fast-list</code> / ListR support</h3>
<p>NetStorage remote supports the ListR feature by using the "list" NetStorage API action to return a lexicographical list of all objects within the specified CP code, recursing into subdirectories as they're encountered.</p>
<ul>
<li><p><strong>Rclone will use the ListR method for some commands by default</strong>. Commands such as <code>lsf -R</code> will use ListR by default. To disable this, include the <code>--disable listR</code> option to use the non-recursive method of listing objects.</p></li>
<li><p><strong>Rclone will not use the ListR method for some commands</strong>. Commands such as <code>sync</code> don't use ListR by default. To force using the ListR method, include the <code>--fast-list</code> option.</p></li>
</ul>
<p>There are pros and cons of using the ListR method, refer to <a href="https://rclone.org/docs/#fast-list">rclone documentation</a>. In general, the sync command over an existing deep tree on the remote will run faster with the "--fast-list" flag but with extra memory usage as a side effect. It might also result in higher CPU utilization but the whole task can be completed faster.</p>
<p><strong>Note</strong>: There is a known limitation that "lsf -R" will display number of files in the directory and directory size as -1 when ListR method is used. The workaround is to pass "--disable listR" flag if these numbers are important in the output.</p>
<h3 id="purge-1">Purge</h3>
<p>NetStorage remote supports the purge feature by using the "quick-delete" NetStorage API action. The quick-delete action is disabled by default for security reasons and can be enabled for the account through the Akamai portal. Rclone will first try to use quick-delete action for the purge command and if this functionality is disabled then will fall back to a standard delete method.</p>
<p><strong>Note</strong>: Read the <a href="https://learn.akamai.com/en-us/webhelp/netstorage/netstorage-http-api-developer-guide/GUID-15836617-9F50-405A-833C-EA2556756A30.html">NetStorage Usage API</a> for considerations when using "quick-delete". In general, using quick-delete method will not delete the tree immediately and objects targeted for quick-delete may still be accessible.</p>
<h3 id="standard-options-30">Standard options</h3>
<p>Here are the Standard options specific to netstorage (Akamai NetStorage).</p>
<h4 id="netstorage-host">--netstorage-host</h4>
<p>Domain+path of NetStorage host to connect to.</p>
<p>Format should be <code>&lt;domain&gt;/&lt;internal folders&gt;</code></p>
<p>Properties:</p>
<ul>
<li>Config: host</li>
<li>Env Var: RCLONE_NETSTORAGE_HOST</li>
<li>Type: string</li>
<li>Required: true</li>
</ul>
<h4 id="netstorage-account">--netstorage-account</h4>
<p>Set the NetStorage account name</p>
<p>Properties:</p>
<ul>
<li>Config: account</li>
<li>Env Var: RCLONE_NETSTORAGE_ACCOUNT</li>
<li>Type: string</li>
<li>Required: true</li>
</ul>
<h4 id="netstorage-secret">--netstorage-secret</h4>
<p>Set the NetStorage account secret/G2O key for authentication.</p>
<p>Please choose the 'y' option to set your own password then enter your secret.</p>
<p><strong>NB</strong> Input to this must be obscured - see <a href="https://rclone.org/commands/rclone_obscure/">rclone obscure</a>.</p>
<p>Properties:</p>
<ul>
<li>Config: secret</li>
<li>Env Var: RCLONE_NETSTORAGE_SECRET</li>
<li>Type: string</li>
<li>Required: true</li>
</ul>
<h3 id="advanced-options-31">Advanced options</h3>
<p>Here are the Advanced options specific to netstorage (Akamai NetStorage).</p>
<h4 id="netstorage-protocol">--netstorage-protocol</h4>
<p>Select between HTTP or HTTPS protocol.</p>
<p>Most users should choose HTTPS, which is the default. HTTP is provided primarily for debugging purposes.</p>
<p>Properties:</p>
<ul>
<li>Config: protocol</li>
<li>Env Var: RCLONE_NETSTORAGE_PROTOCOL</li>
<li>Type: string</li>
<li>Default: "https"</li>
<li>Examples:
<ul>
<li>"http"
<ul>
<li>HTTP protocol</li>
</ul></li>
<li>"https"
<ul>
<li>HTTPS protocol</li>
</ul></li>
</ul></li>
</ul>
<h4 id="netstorage-description">--netstorage-description</h4>
<p>Description of the remote.</p>
<p>Properties:</p>
<ul>
<li>Config: description</li>
<li>Env Var: RCLONE_NETSTORAGE_DESCRIPTION</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h2 id="backend-commands-7">Backend commands</h2>
<p>Here are the commands specific to the netstorage backend.</p>
<p>Run them with</p>
<pre><code>rclone backend COMMAND remote:</code></pre>
<p>The help below will explain what arguments each command takes.</p>
<p>See the <a href="https://rclone.org/commands/rclone_backend/">backend</a> command for more info on how to pass options and arguments.</p>
<p>These can be run on a running backend using the rc command <a href="https://rclone.org/rc/#backend-command">backend/command</a>.</p>
<h3 id="du">du</h3>
<p>Return disk usage information for a specified directory</p>
<pre><code>rclone backend du remote: [options] [&lt;arguments&gt;+]</code></pre>
<p>The usage information returned, includes the targeted directory as well as all files stored in any sub-directories that may exist.</p>
<h3 id="symlink">symlink</h3>
<p>You can create a symbolic link in ObjectStore with the symlink action.</p>
<pre><code>rclone backend symlink remote: [options] [&lt;arguments&gt;+]</code></pre>
<p>The desired path location (including applicable sub-directories) ending in the object that will be the target of the symlink (for example, /links/mylink). Include the file extension for the object, if applicable. <code>rclone backend symlink &lt;src&gt; &lt;path&gt;</code></p>
<h1 id="microsoft-azure-blob-storage">Microsoft Azure Blob Storage</h1>
<p>Paths are specified as <code>remote:container</code> (or <code>remote:</code> for the <code>lsd</code> command.) You may put subdirectories in too, e.g. <code>remote:container/path/to/dir</code>.</p>
<h2 id="configuration-31">Configuration</h2>
<p>Here is an example of making a Microsoft Azure Blob Storage configuration. For a remote called <code>remote</code>. First run:</p>
<pre><code> rclone config</code></pre>
<p>This will guide you through an interactive setup process:</p>
<pre><code>No remotes found, make a new one?
n) New remote
s) Set configuration password
q) Quit config
n/s/q&gt; n
name&gt; remote
Type of storage to configure.
Choose a number from below, or type in your own value
[snip]
XX / Microsoft Azure Blob Storage
   \ &quot;azureblob&quot;
[snip]
Storage&gt; azureblob
Storage Account Name
account&gt; account_name
Storage Account Key
key&gt; base64encodedkey==
Endpoint for the service - leave blank normally.
endpoint&gt; 
Remote config
Configuration complete.
Options:
- type: azureblob
- account: account_name
- key: base64encodedkey==
- endpoint:
Keep this &quot;remote&quot; remote?
y) Yes this is OK
e) Edit this remote
d) Delete this remote
y/e/d&gt; y</code></pre>
<p>See all containers</p>
<pre><code>rclone lsd remote:</code></pre>
<p>Make a new container</p>
<pre><code>rclone mkdir remote:container</code></pre>
<p>List the contents of a container</p>
<pre><code>rclone ls remote:container</code></pre>
<p>Sync <code>/home/local/directory</code> to the remote container, deleting any excess files in the container.</p>
<pre><code>rclone sync --interactive /home/local/directory remote:container</code></pre>
<h3 id="fast-list-5">--fast-list</h3>
<p>This remote supports <code>--fast-list</code> which allows you to use fewer transactions in exchange for more memory. See the <a href="https://rclone.org/docs/#fast-list">rclone docs</a> for more details.</p>
<h3 id="modification-times-and-hashes-14">Modification times and hashes</h3>
<p>The modification time is stored as metadata on the object with the <code>mtime</code> key. It is stored using RFC3339 Format time with nanosecond precision. The metadata is supplied during directory listings so there is no performance overhead to using it.</p>
<p>If you wish to use the Azure standard <code>LastModified</code> time stored on the object as the modified time, then use the <code>--use-server-modtime</code> flag. Note that rclone can't set <code>LastModified</code>, so using the <code>--update</code> flag when syncing is recommended if using <code>--use-server-modtime</code>.</p>
<p>MD5 hashes are stored with blobs. However blobs that were uploaded in chunks only have an MD5 if the source remote was capable of MD5 hashes, e.g. the local disk.</p>
<h3 id="performance-1">Performance</h3>
<p>When uploading large files, increasing the value of <code>--azureblob-upload-concurrency</code> will increase performance at the cost of using more memory. The default of 16 is set quite conservatively to use less memory. It maybe be necessary raise it to 64 or higher to fully utilize a 1 GBit/s link with a single file transfer.</p>
<h3 id="restricted-filename-characters-18">Restricted filename characters</h3>
<p>In addition to the <a href="https://rclone.org/overview/#restricted-characters">default restricted characters set</a> the following characters are also replaced:</p>
<table>
<thead>
<tr class="header">
<th>Character</th>
<th style="text-align: center;">Value</th>
<th style="text-align: center;">Replacement</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td>/</td>
<td style="text-align: center;">0x2F</td>
<td style="text-align: center;">／</td>
</tr>
<tr class="even">
<td>\</td>
<td style="text-align: center;">0x5C</td>
<td style="text-align: center;">＼</td>
</tr>
</tbody>
</table>
<p>File names can also not end with the following characters. These only get replaced if they are the last character in the name:</p>
<table>
<thead>
<tr class="header">
<th>Character</th>
<th style="text-align: center;">Value</th>
<th style="text-align: center;">Replacement</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td>.</td>
<td style="text-align: center;">0x2E</td>
<td style="text-align: center;">．</td>
</tr>
</tbody>
</table>
<p>Invalid UTF-8 bytes will also be <a href="https://rclone.org/overview/#invalid-utf8">replaced</a>, as they can't be used in JSON strings.</p>
<h3 id="authentication">Authentication</h3>
<p>There are a number of ways of supplying credentials for Azure Blob Storage. Rclone tries them in the order of the sections below.</p>
<h4 id="env-auth">Env Auth</h4>
<p>If the <code>env_auth</code> config parameter is <code>true</code> then rclone will pull credentials from the environment or runtime.</p>
<p>It tries these authentication methods in this order:</p>
<ol type="1">
<li>Environment Variables</li>
<li>Managed Service Identity Credentials</li>
<li>Azure CLI credentials (as used by the az tool)</li>
</ol>
<p>These are described in the following sections</p>
<h5 id="env-auth-1.-environment-variables">Env Auth: 1. Environment Variables</h5>
<p>If <code>env_auth</code> is set and environment variables are present rclone authenticates a service principal with a secret or certificate, or a user with a password, depending on which environment variable are set. It reads configuration from these variables, in the following order:</p>
<ol type="1">
<li>Service principal with client secret
<ul>
<li><code>AZURE_TENANT_ID</code>: ID of the service principal's tenant. Also called its "directory" ID.</li>
<li><code>AZURE_CLIENT_ID</code>: the service principal's client ID</li>
<li><code>AZURE_CLIENT_SECRET</code>: one of the service principal's client secrets</li>
</ul></li>
<li>Service principal with certificate
<ul>
<li><code>AZURE_TENANT_ID</code>: ID of the service principal's tenant. Also called its "directory" ID.</li>
<li><code>AZURE_CLIENT_ID</code>: the service principal's client ID</li>
<li><code>AZURE_CLIENT_CERTIFICATE_PATH</code>: path to a PEM or PKCS12 certificate file including the private key.</li>
<li><code>AZURE_CLIENT_CERTIFICATE_PASSWORD</code>: (optional) password for the certificate file.</li>
<li><code>AZURE_CLIENT_SEND_CERTIFICATE_CHAIN</code>: (optional) Specifies whether an authentication request will include an x5c header to support subject name / issuer based authentication. When set to "true" or "1", authentication requests include the x5c header.</li>
</ul></li>
<li>User with username and password
<ul>
<li><code>AZURE_TENANT_ID</code>: (optional) tenant to authenticate in. Defaults to "organizations".</li>
<li><code>AZURE_CLIENT_ID</code>: client ID of the application the user will authenticate to</li>
<li><code>AZURE_USERNAME</code>: a username (usually an email address)</li>
<li><code>AZURE_PASSWORD</code>: the user's password</li>
</ul></li>
<li>Workload Identity
<ul>
<li><code>AZURE_TENANT_ID</code>: Tenant to authenticate in.</li>
<li><code>AZURE_CLIENT_ID</code>: Client ID of the application the user will authenticate to.</li>
<li><code>AZURE_FEDERATED_TOKEN_FILE</code>: Path to projected service account token file.</li>
<li><code>AZURE_AUTHORITY_HOST</code>: Authority of an Azure Active Directory endpoint (default: login.microsoftonline.com).</li>
</ul></li>
</ol>
<h5 id="env-auth-2.-managed-service-identity-credentials">Env Auth: 2. Managed Service Identity Credentials</h5>
<p>When using Managed Service Identity if the VM(SS) on which this program is running has a system-assigned identity, it will be used by default. If the resource has no system-assigned but exactly one user-assigned identity, the user-assigned identity will be used by default.</p>
<p>If the resource has multiple user-assigned identities you will need to unset <code>env_auth</code> and set <code>use_msi</code> instead. See the <a href="#use_msi"><code>use_msi</code> section</a>.</p>
<h5 id="env-auth-3.-azure-cli-credentials-as-used-by-the-az-tool">Env Auth: 3. Azure CLI credentials (as used by the az tool)</h5>
<p>Credentials created with the <code>az</code> tool can be picked up using <code>env_auth</code>.</p>
<p>For example if you were to login with a service principal like this:</p>
<pre><code>az login --service-principal -u XXX -p XXX --tenant XXX</code></pre>
<p>Then you could access rclone resources like this:</p>
<pre><code>rclone lsf :azureblob,env_auth,account=ACCOUNT:CONTAINER</code></pre>
<p>Or</p>
<pre><code>rclone lsf --azureblob-env-auth --azureblob-account=ACCOUNT :azureblob:CONTAINER</code></pre>
<p>Which is analogous to using the <code>az</code> tool:</p>
<pre><code>az storage blob list --container-name CONTAINER --account-name ACCOUNT --auth-mode login</code></pre>
<h4 id="account-and-shared-key">Account and Shared Key</h4>
<p>This is the most straight forward and least flexible way. Just fill in the <code>account</code> and <code>key</code> lines and leave the rest blank.</p>
<h4 id="sas-url">SAS URL</h4>
<p>This can be an account level SAS URL or container level SAS URL.</p>
<p>To use it leave <code>account</code> and <code>key</code> blank and fill in <code>sas_url</code>.</p>
<p>An account level SAS URL or container level SAS URL can be obtained from the Azure portal or the Azure Storage Explorer. To get a container level SAS URL right click on a container in the Azure Blob explorer in the Azure portal.</p>
<p>If you use a container level SAS URL, rclone operations are permitted only on a particular container, e.g.</p>
<pre><code>rclone ls azureblob:container</code></pre>
<p>You can also list the single container from the root. This will only show the container specified by the SAS URL.</p>
<pre><code>$ rclone lsd azureblob:
container/</code></pre>
<p>Note that you can't see or access any other containers - this will fail</p>
<pre><code>rclone ls azureblob:othercontainer</code></pre>
<p>Container level SAS URLs are useful for temporarily allowing third parties access to a single container or putting credentials into an untrusted environment such as a CI build server.</p>
<h4 id="service-principal-with-client-secret">Service principal with client secret</h4>
<p>If these variables are set, rclone will authenticate with a service principal with a client secret.</p>
<ul>
<li><code>tenant</code>: ID of the service principal's tenant. Also called its "directory" ID.</li>
<li><code>client_id</code>: the service principal's client ID</li>
<li><code>client_secret</code>: one of the service principal's client secrets</li>
</ul>
<p>The credentials can also be placed in a file using the <code>service_principal_file</code> configuration option.</p>
<h4 id="service-principal-with-certificate">Service principal with certificate</h4>
<p>If these variables are set, rclone will authenticate with a service principal with certificate.</p>
<ul>
<li><code>tenant</code>: ID of the service principal's tenant. Also called its "directory" ID.</li>
<li><code>client_id</code>: the service principal's client ID</li>
<li><code>client_certificate_path</code>: path to a PEM or PKCS12 certificate file including the private key.</li>
<li><code>client_certificate_password</code>: (optional) password for the certificate file.</li>
<li><code>client_send_certificate_chain</code>: (optional) Specifies whether an authentication request will include an x5c header to support subject name / issuer based authentication. When set to "true" or "1", authentication requests include the x5c header.</li>
</ul>
<p><strong>NB</strong> <code>client_certificate_password</code> must be obscured - see <a href="https://rclone.org/commands/rclone_obscure/">rclone obscure</a>.</p>
<h4 id="user-with-username-and-password">User with username and password</h4>
<p>If these variables are set, rclone will authenticate with username and password.</p>
<ul>
<li><code>tenant</code>: (optional) tenant to authenticate in. Defaults to "organizations".</li>
<li><code>client_id</code>: client ID of the application the user will authenticate to</li>
<li><code>username</code>: a username (usually an email address)</li>
<li><code>password</code>: the user's password</li>
</ul>
<p>Microsoft doesn't recommend this kind of authentication, because it's less secure than other authentication flows. This method is not interactive, so it isn't compatible with any form of multi-factor authentication, and the application must already have user or admin consent. This credential can only authenticate work and school accounts; it can't authenticate Microsoft accounts.</p>
<p><strong>NB</strong> <code>password</code> must be obscured - see <a href="https://rclone.org/commands/rclone_obscure/">rclone obscure</a>.</p>
<h4 id="use_msi">Managed Service Identity Credentials</h4>
<p>If <code>use_msi</code> is set then managed service identity credentials are used. This authentication only works when running in an Azure service. <code>env_auth</code> needs to be unset to use this.</p>
<p>However if you have multiple user identities to choose from these must be explicitly specified using exactly one of the <code>msi_object_id</code>, <code>msi_client_id</code>, or <code>msi_mi_res_id</code> parameters.</p>
<p>If none of <code>msi_object_id</code>, <code>msi_client_id</code>, or <code>msi_mi_res_id</code> is set, this is is equivalent to using <code>env_auth</code>.</p>
<h4 id="anonymous">Anonymous</h4>
<p>If you want to access resources with public anonymous access then set <code>account</code> only. You can do this without making an rclone config:</p>
<pre><code>rclone lsf :azureblob,account=ACCOUNT:CONTAINER</code></pre>
<h3 id="standard-options-31">Standard options</h3>
<p>Here are the Standard options specific to azureblob (Microsoft Azure Blob Storage).</p>
<h4 id="azureblob-account">--azureblob-account</h4>
<p>Azure Storage Account Name.</p>
<p>Set this to the Azure Storage Account Name in use.</p>
<p>Leave blank to use SAS URL or Emulator, otherwise it needs to be set.</p>
<p>If this is blank and if env_auth is set it will be read from the environment variable <code>AZURE_STORAGE_ACCOUNT_NAME</code> if possible.</p>
<p>Properties:</p>
<ul>
<li>Config: account</li>
<li>Env Var: RCLONE_AZUREBLOB_ACCOUNT</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="azureblob-env-auth">--azureblob-env-auth</h4>
<p>Read credentials from runtime (environment variables, CLI or MSI).</p>
<p>See the <a href="/azureblob#authentication">authentication docs</a> for full info.</p>
<p>Properties:</p>
<ul>
<li>Config: env_auth</li>
<li>Env Var: RCLONE_AZUREBLOB_ENV_AUTH</li>
<li>Type: bool</li>
<li>Default: false</li>
</ul>
<h4 id="azureblob-key">--azureblob-key</h4>
<p>Storage Account Shared Key.</p>
<p>Leave blank to use SAS URL or Emulator.</p>
<p>Properties:</p>
<ul>
<li>Config: key</li>
<li>Env Var: RCLONE_AZUREBLOB_KEY</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="azureblob-sas-url">--azureblob-sas-url</h4>
<p>SAS URL for container level access only.</p>
<p>Leave blank if using account/key or Emulator.</p>
<p>Properties:</p>
<ul>
<li>Config: sas_url</li>
<li>Env Var: RCLONE_AZUREBLOB_SAS_URL</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="azureblob-tenant">--azureblob-tenant</h4>
<p>ID of the service principal's tenant. Also called its directory ID.</p>
<p>Set this if using - Service principal with client secret - Service principal with certificate - User with username and password</p>
<p>Properties:</p>
<ul>
<li>Config: tenant</li>
<li>Env Var: RCLONE_AZUREBLOB_TENANT</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="azureblob-client-id">--azureblob-client-id</h4>
<p>The ID of the client in use.</p>
<p>Set this if using - Service principal with client secret - Service principal with certificate - User with username and password</p>
<p>Properties:</p>
<ul>
<li>Config: client_id</li>
<li>Env Var: RCLONE_AZUREBLOB_CLIENT_ID</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="azureblob-client-secret">--azureblob-client-secret</h4>
<p>One of the service principal's client secrets</p>
<p>Set this if using - Service principal with client secret</p>
<p>Properties:</p>
<ul>
<li>Config: client_secret</li>
<li>Env Var: RCLONE_AZUREBLOB_CLIENT_SECRET</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="azureblob-client-certificate-path">--azureblob-client-certificate-path</h4>
<p>Path to a PEM or PKCS12 certificate file including the private key.</p>
<p>Set this if using - Service principal with certificate</p>
<p>Properties:</p>
<ul>
<li>Config: client_certificate_path</li>
<li>Env Var: RCLONE_AZUREBLOB_CLIENT_CERTIFICATE_PATH</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="azureblob-client-certificate-password">--azureblob-client-certificate-password</h4>
<p>Password for the certificate file (optional).</p>
<p>Optionally set this if using - Service principal with certificate</p>
<p>And the certificate has a password.</p>
<p><strong>NB</strong> Input to this must be obscured - see <a href="https://rclone.org/commands/rclone_obscure/">rclone obscure</a>.</p>
<p>Properties:</p>
<ul>
<li>Config: client_certificate_password</li>
<li>Env Var: RCLONE_AZUREBLOB_CLIENT_CERTIFICATE_PASSWORD</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h3 id="advanced-options-32">Advanced options</h3>
<p>Here are the Advanced options specific to azureblob (Microsoft Azure Blob Storage).</p>
<h4 id="azureblob-client-send-certificate-chain">--azureblob-client-send-certificate-chain</h4>
<p>Send the certificate chain when using certificate auth.</p>
<p>Specifies whether an authentication request will include an x5c header to support subject name / issuer based authentication. When set to true, authentication requests include the x5c header.</p>
<p>Optionally set this if using - Service principal with certificate</p>
<p>Properties:</p>
<ul>
<li>Config: client_send_certificate_chain</li>
<li>Env Var: RCLONE_AZUREBLOB_CLIENT_SEND_CERTIFICATE_CHAIN</li>
<li>Type: bool</li>
<li>Default: false</li>
</ul>
<h4 id="azureblob-username">--azureblob-username</h4>
<p>User name (usually an email address)</p>
<p>Set this if using - User with username and password</p>
<p>Properties:</p>
<ul>
<li>Config: username</li>
<li>Env Var: RCLONE_AZUREBLOB_USERNAME</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="azureblob-password">--azureblob-password</h4>
<p>The user's password</p>
<p>Set this if using - User with username and password</p>
<p><strong>NB</strong> Input to this must be obscured - see <a href="https://rclone.org/commands/rclone_obscure/">rclone obscure</a>.</p>
<p>Properties:</p>
<ul>
<li>Config: password</li>
<li>Env Var: RCLONE_AZUREBLOB_PASSWORD</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="azureblob-service-principal-file">--azureblob-service-principal-file</h4>
<p>Path to file containing credentials for use with a service principal.</p>
<p>Leave blank normally. Needed only if you want to use a service principal instead of interactive login.</p>
<pre><code>$ az ad sp create-for-rbac --name &quot;&lt;name&gt;&quot; \
  --role &quot;Storage Blob Data Owner&quot; \
  --scopes &quot;/subscriptions/&lt;subscription&gt;/resourceGroups/&lt;resource-group&gt;/providers/Microsoft.Storage/storageAccounts/&lt;storage-account&gt;/blobServices/default/containers/&lt;container&gt;&quot; \
  &gt; azure-principal.json</code></pre>
<p>See <a href="https://docs.microsoft.com/en-us/cli/azure/create-an-azure-service-principal-azure-cli">"Create an Azure service principal"</a> and <a href="https://docs.microsoft.com/en-us/azure/storage/common/storage-auth-aad-rbac-cli">"Assign an Azure role for access to blob data"</a> pages for more details.</p>
<p>It may be more convenient to put the credentials directly into the rclone config file under the <code>client_id</code>, <code>tenant</code> and <code>client_secret</code> keys instead of setting <code>service_principal_file</code>.</p>
<p>Properties:</p>
<ul>
<li>Config: service_principal_file</li>
<li>Env Var: RCLONE_AZUREBLOB_SERVICE_PRINCIPAL_FILE</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="azureblob-use-msi">--azureblob-use-msi</h4>
<p>Use a managed service identity to authenticate (only works in Azure).</p>
<p>When true, use a <a href="https://docs.microsoft.com/en-us/azure/active-directory/managed-identities-azure-resources/">managed service identity</a> to authenticate to Azure Storage instead of a SAS token or account key.</p>
<p>If the VM(SS) on which this program is running has a system-assigned identity, it will be used by default. If the resource has no system-assigned but exactly one user-assigned identity, the user-assigned identity will be used by default. If the resource has multiple user-assigned identities, the identity to use must be explicitly specified using exactly one of the msi_object_id, msi_client_id, or msi_mi_res_id parameters.</p>
<p>Properties:</p>
<ul>
<li>Config: use_msi</li>
<li>Env Var: RCLONE_AZUREBLOB_USE_MSI</li>
<li>Type: bool</li>
<li>Default: false</li>
</ul>
<h4 id="azureblob-msi-object-id">--azureblob-msi-object-id</h4>
<p>Object ID of the user-assigned MSI to use, if any.</p>
<p>Leave blank if msi_client_id or msi_mi_res_id specified.</p>
<p>Properties:</p>
<ul>
<li>Config: msi_object_id</li>
<li>Env Var: RCLONE_AZUREBLOB_MSI_OBJECT_ID</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="azureblob-msi-client-id">--azureblob-msi-client-id</h4>
<p>Object ID of the user-assigned MSI to use, if any.</p>
<p>Leave blank if msi_object_id or msi_mi_res_id specified.</p>
<p>Properties:</p>
<ul>
<li>Config: msi_client_id</li>
<li>Env Var: RCLONE_AZUREBLOB_MSI_CLIENT_ID</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="azureblob-msi-mi-res-id">--azureblob-msi-mi-res-id</h4>
<p>Azure resource ID of the user-assigned MSI to use, if any.</p>
<p>Leave blank if msi_client_id or msi_object_id specified.</p>
<p>Properties:</p>
<ul>
<li>Config: msi_mi_res_id</li>
<li>Env Var: RCLONE_AZUREBLOB_MSI_MI_RES_ID</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="azureblob-use-emulator">--azureblob-use-emulator</h4>
<p>Uses local storage emulator if provided as 'true'.</p>
<p>Leave blank if using real azure storage endpoint.</p>
<p>Properties:</p>
<ul>
<li>Config: use_emulator</li>
<li>Env Var: RCLONE_AZUREBLOB_USE_EMULATOR</li>
<li>Type: bool</li>
<li>Default: false</li>
</ul>
<h4 id="azureblob-endpoint">--azureblob-endpoint</h4>
<p>Endpoint for the service.</p>
<p>Leave blank normally.</p>
<p>Properties:</p>
<ul>
<li>Config: endpoint</li>
<li>Env Var: RCLONE_AZUREBLOB_ENDPOINT</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="azureblob-upload-cutoff">--azureblob-upload-cutoff</h4>
<p>Cutoff for switching to chunked upload (&lt;= 256 MiB) (deprecated).</p>
<p>Properties:</p>
<ul>
<li>Config: upload_cutoff</li>
<li>Env Var: RCLONE_AZUREBLOB_UPLOAD_CUTOFF</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="azureblob-chunk-size">--azureblob-chunk-size</h4>
<p>Upload chunk size.</p>
<p>Note that this is stored in memory and there may be up to "--transfers" * "--azureblob-upload-concurrency" chunks stored at once in memory.</p>
<p>Properties:</p>
<ul>
<li>Config: chunk_size</li>
<li>Env Var: RCLONE_AZUREBLOB_CHUNK_SIZE</li>
<li>Type: SizeSuffix</li>
<li>Default: 4Mi</li>
</ul>
<h4 id="azureblob-upload-concurrency">--azureblob-upload-concurrency</h4>
<p>Concurrency for multipart uploads.</p>
<p>This is the number of chunks of the same file that are uploaded concurrently.</p>
<p>If you are uploading small numbers of large files over high-speed links and these uploads do not fully utilize your bandwidth, then increasing this may help to speed up the transfers.</p>
<p>In tests, upload speed increases almost linearly with upload concurrency. For example to fill a gigabit pipe it may be necessary to raise this to 64. Note that this will use more memory.</p>
<p>Note that chunks are stored in memory and there may be up to "--transfers" * "--azureblob-upload-concurrency" chunks stored at once in memory.</p>
<p>Properties:</p>
<ul>
<li>Config: upload_concurrency</li>
<li>Env Var: RCLONE_AZUREBLOB_UPLOAD_CONCURRENCY</li>
<li>Type: int</li>
<li>Default: 16</li>
</ul>
<h4 id="azureblob-list-chunk">--azureblob-list-chunk</h4>
<p>Size of blob list.</p>
<p>This sets the number of blobs requested in each listing chunk. Default is the maximum, 5000. "List blobs" requests are permitted 2 minutes per megabyte to complete. If an operation is taking longer than 2 minutes per megabyte on average, it will time out ( <a href="https://docs.microsoft.com/en-us/rest/api/storageservices/setting-timeouts-for-blob-service-operations#exceptions-to-default-timeout-interval">source</a> ). This can be used to limit the number of blobs items to return, to avoid the time out.</p>
<p>Properties:</p>
<ul>
<li>Config: list_chunk</li>
<li>Env Var: RCLONE_AZUREBLOB_LIST_CHUNK</li>
<li>Type: int</li>
<li>Default: 5000</li>
</ul>
<h4 id="azureblob-access-tier">--azureblob-access-tier</h4>
<p>Access tier of blob: hot, cool, cold or archive.</p>
<p>Archived blobs can be restored by setting access tier to hot, cool or cold. Leave blank if you intend to use default access tier, which is set at account level</p>
<p>If there is no "access tier" specified, rclone doesn't apply any tier. rclone performs "Set Tier" operation on blobs while uploading, if objects are not modified, specifying "access tier" to new one will have no effect. If blobs are in "archive tier" at remote, trying to perform data transfer operations from remote will not be allowed. User should first restore by tiering blob to "Hot", "Cool" or "Cold".</p>
<p>Properties:</p>
<ul>
<li>Config: access_tier</li>
<li>Env Var: RCLONE_AZUREBLOB_ACCESS_TIER</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="azureblob-archive-tier-delete">--azureblob-archive-tier-delete</h4>
<p>Delete archive tier blobs before overwriting.</p>
<p>Archive tier blobs cannot be updated. So without this flag, if you attempt to update an archive tier blob, then rclone will produce the error:</p>
<pre><code>can&#39;t update archive tier blob without --azureblob-archive-tier-delete</code></pre>
<p>With this flag set then before rclone attempts to overwrite an archive tier blob, it will delete the existing blob before uploading its replacement. This has the potential for data loss if the upload fails (unlike updating a normal blob) and also may cost more since deleting archive tier blobs early may be chargable.</p>
<p>Properties:</p>
<ul>
<li>Config: archive_tier_delete</li>
<li>Env Var: RCLONE_AZUREBLOB_ARCHIVE_TIER_DELETE</li>
<li>Type: bool</li>
<li>Default: false</li>
</ul>
<h4 id="azureblob-disable-checksum">--azureblob-disable-checksum</h4>
<p>Don't store MD5 checksum with object metadata.</p>
<p>Normally rclone will calculate the MD5 checksum of the input before uploading it so it can add it to metadata on the object. This is great for data integrity checking but can cause long delays for large files to start uploading.</p>
<p>Properties:</p>
<ul>
<li>Config: disable_checksum</li>
<li>Env Var: RCLONE_AZUREBLOB_DISABLE_CHECKSUM</li>
<li>Type: bool</li>
<li>Default: false</li>
</ul>
<h4 id="azureblob-memory-pool-flush-time">--azureblob-memory-pool-flush-time</h4>
<p>How often internal memory buffer pools will be flushed. (no longer used)</p>
<p>Properties:</p>
<ul>
<li>Config: memory_pool_flush_time</li>
<li>Env Var: RCLONE_AZUREBLOB_MEMORY_POOL_FLUSH_TIME</li>
<li>Type: Duration</li>
<li>Default: 1m0s</li>
</ul>
<h4 id="azureblob-memory-pool-use-mmap">--azureblob-memory-pool-use-mmap</h4>
<p>Whether to use mmap buffers in internal memory pool. (no longer used)</p>
<p>Properties:</p>
<ul>
<li>Config: memory_pool_use_mmap</li>
<li>Env Var: RCLONE_AZUREBLOB_MEMORY_POOL_USE_MMAP</li>
<li>Type: bool</li>
<li>Default: false</li>
</ul>
<h4 id="azureblob-encoding">--azureblob-encoding</h4>
<p>The encoding for the backend.</p>
<p>See the <a href="https://rclone.org/overview/#encoding">encoding section in the overview</a> for more info.</p>
<p>Properties:</p>
<ul>
<li>Config: encoding</li>
<li>Env Var: RCLONE_AZUREBLOB_ENCODING</li>
<li>Type: Encoding</li>
<li>Default: Slash,BackSlash,Del,Ctl,RightPeriod,InvalidUtf8</li>
</ul>
<h4 id="azureblob-public-access">--azureblob-public-access</h4>
<p>Public access level of a container: blob or container.</p>
<p>Properties:</p>
<ul>
<li>Config: public_access</li>
<li>Env Var: RCLONE_AZUREBLOB_PUBLIC_ACCESS</li>
<li>Type: string</li>
<li>Required: false</li>
<li>Examples:
<ul>
<li>""
<ul>
<li>The container and its blobs can be accessed only with an authorized request.</li>
<li>It's a default value.</li>
</ul></li>
<li>"blob"
<ul>
<li>Blob data within this container can be read via anonymous request.</li>
</ul></li>
<li>"container"
<ul>
<li>Allow full public read access for container and blob data.</li>
</ul></li>
</ul></li>
</ul>
<h4 id="azureblob-directory-markers">--azureblob-directory-markers</h4>
<p>Upload an empty object with a trailing slash when a new directory is created</p>
<p>Empty folders are unsupported for bucket based remotes, this option creates an empty object ending with "/", to persist the folder.</p>
<p>This object also has the metadata "hdi_isfolder = true" to conform to the Microsoft standard.</p>
<p>Properties:</p>
<ul>
<li>Config: directory_markers</li>
<li>Env Var: RCLONE_AZUREBLOB_DIRECTORY_MARKERS</li>
<li>Type: bool</li>
<li>Default: false</li>
</ul>
<h4 id="azureblob-no-check-container">--azureblob-no-check-container</h4>
<p>If set, don't attempt to check the container exists or create it.</p>
<p>This can be useful when trying to minimise the number of transactions rclone does if you know the container exists already.</p>
<p>Properties:</p>
<ul>
<li>Config: no_check_container</li>
<li>Env Var: RCLONE_AZUREBLOB_NO_CHECK_CONTAINER</li>
<li>Type: bool</li>
<li>Default: false</li>
</ul>
<h4 id="azureblob-no-head-object">--azureblob-no-head-object</h4>
<p>If set, do not do HEAD before GET when getting objects.</p>
<p>Properties:</p>
<ul>
<li>Config: no_head_object</li>
<li>Env Var: RCLONE_AZUREBLOB_NO_HEAD_OBJECT</li>
<li>Type: bool</li>
<li>Default: false</li>
</ul>
<h4 id="azureblob-delete-snapshots">--azureblob-delete-snapshots</h4>
<p>Set to specify how to deal with snapshots on blob deletion.</p>
<p>Properties:</p>
<ul>
<li>Config: delete_snapshots</li>
<li>Env Var: RCLONE_AZUREBLOB_DELETE_SNAPSHOTS</li>
<li>Type: string</li>
<li>Required: false</li>
<li>Choices:
<ul>
<li>""
<ul>
<li>By default, the delete operation fails if a blob has snapshots</li>
</ul></li>
<li>"include"
<ul>
<li>Specify 'include' to remove the root blob and all its snapshots</li>
</ul></li>
<li>"only"
<ul>
<li>Specify 'only' to remove only the snapshots but keep the root blob.</li>
</ul></li>
</ul></li>
</ul>
<h4 id="azureblob-description">--azureblob-description</h4>
<p>Description of the remote.</p>
<p>Properties:</p>
<ul>
<li>Config: description</li>
<li>Env Var: RCLONE_AZUREBLOB_DESCRIPTION</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h3 id="custom-upload-headers-1">Custom upload headers</h3>
<p>You can set custom upload headers with the <code>--header-upload</code> flag.</p>
<ul>
<li>Cache-Control</li>
<li>Content-Disposition</li>
<li>Content-Encoding</li>
<li>Content-Language</li>
<li>Content-Type</li>
</ul>
<p>Eg <code>--header-upload "Content-Type: text/potato"</code></p>
<h2 id="limitations-24">Limitations</h2>
<p>MD5 sums are only uploaded with chunked files if the source has an MD5 sum. This will always be the case for a local to azure copy.</p>
<p><code>rclone about</code> is not supported by the Microsoft Azure Blob storage backend. Backends without this capability cannot determine free space for an rclone mount or use policy <code>mfs</code> (most free space) as a member of an rclone union remote.</p>
<p>See <a href="https://rclone.org/overview/#optional-features">List of backends that do not support rclone about</a> and <a href="https://rclone.org/commands/rclone_about/">rclone about</a></p>
<h2 id="azure-storage-emulator-support">Azure Storage Emulator Support</h2>
<p>You can run rclone with the storage emulator (usually <em>azurite</em>).</p>
<p>To do this, just set up a new remote with <code>rclone config</code> following the instructions in the introduction and set <code>use_emulator</code> in the advanced settings as <code>true</code>. You do not need to provide a default account name nor an account key. But you can override them in the <code>account</code> and <code>key</code> options. (Prior to v1.61 they were hard coded to <em>azurite</em>'s <code>devstoreaccount1</code>.)</p>
<p>Also, if you want to access a storage emulator instance running on a different machine, you can override the <code>endpoint</code> parameter in the advanced settings, setting it to <code>http(s)://&lt;host&gt;:&lt;port&gt;/devstoreaccount1</code> (e.g. <code>http://10.254.2.5:10000/devstoreaccount1</code>).</p>
<h1 id="microsoft-azure-files-storage">Microsoft Azure Files Storage</h1>
<p>Paths are specified as <code>remote:</code> You may put subdirectories in too, e.g. <code>remote:path/to/dir</code>.</p>
<h2 id="configuration-32">Configuration</h2>
<p>Here is an example of making a Microsoft Azure Files Storage configuration. For a remote called <code>remote</code>. First run:</p>
<pre><code> rclone config</code></pre>
<p>This will guide you through an interactive setup process:</p>
<pre><code>No remotes found, make a new one?
n) New remote
s) Set configuration password
q) Quit config
n/s/q&gt; n
name&gt; remote
Type of storage to configure.
Choose a number from below, or type in your own value
[snip]
XX / Microsoft Azure Files Storage
   \ &quot;azurefiles&quot;
[snip]

Option account.
Azure Storage Account Name.
Set this to the Azure Storage Account Name in use.
Leave blank to use SAS URL or connection string, otherwise it needs to be set.
If this is blank and if env_auth is set it will be read from the
environment variable `AZURE_STORAGE_ACCOUNT_NAME` if possible.
Enter a value. Press Enter to leave empty.
account&gt; account_name

Option share_name.
Azure Files Share Name.
This is required and is the name of the share to access.
Enter a value. Press Enter to leave empty.
share_name&gt; share_name

Option env_auth.
Read credentials from runtime (environment variables, CLI or MSI).
See the [authentication docs](/azurefiles#authentication) for full info.
Enter a boolean value (true or false). Press Enter for the default (false).
env_auth&gt; 

Option key.
Storage Account Shared Key.
Leave blank to use SAS URL or connection string.
Enter a value. Press Enter to leave empty.
key&gt; base64encodedkey==

Option sas_url.
SAS URL.
Leave blank if using account/key or connection string.
Enter a value. Press Enter to leave empty.
sas_url&gt; 

Option connection_string.
Azure Files Connection String.
Enter a value. Press Enter to leave empty.
connection_string&gt; 
[snip]

Configuration complete.
Options:
- type: azurefiles
- account: account_name
- share_name: share_name
- key: base64encodedkey==
Keep this &quot;remote&quot; remote?
y) Yes this is OK (default)
e) Edit this remote
d) Delete this remote
y/e/d&gt; </code></pre>
<p>Once configured you can use rclone.</p>
<p>See all files in the top level:</p>
<pre><code>rclone lsf remote:</code></pre>
<p>Make a new directory in the root:</p>
<pre><code>rclone mkdir remote:dir</code></pre>
<p>Recursively List the contents:</p>
<pre><code>rclone ls remote:</code></pre>
<p>Sync <code>/home/local/directory</code> to the remote directory, deleting any excess files in the directory.</p>
<pre><code>rclone sync --interactive /home/local/directory remote:dir</code></pre>
<h3 id="modified-time">Modified time</h3>
<p>The modified time is stored as Azure standard <code>LastModified</code> time on files</p>
<h3 id="performance-2">Performance</h3>
<p>When uploading large files, increasing the value of <code>--azurefiles-upload-concurrency</code> will increase performance at the cost of using more memory. The default of 16 is set quite conservatively to use less memory. It maybe be necessary raise it to 64 or higher to fully utilize a 1 GBit/s link with a single file transfer.</p>
<h3 id="restricted-filename-characters-19">Restricted filename characters</h3>
<p>In addition to the <a href="https://rclone.org/overview/#restricted-characters">default restricted characters set</a> the following characters are also replaced:</p>
<table>
<thead>
<tr class="header">
<th>Character</th>
<th style="text-align: center;">Value</th>
<th style="text-align: center;">Replacement</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td>"</td>
<td style="text-align: center;">0x22</td>
<td style="text-align: center;">＂</td>
</tr>
<tr class="even">
<td>*</td>
<td style="text-align: center;">0x2A</td>
<td style="text-align: center;">＊</td>
</tr>
<tr class="odd">
<td>:</td>
<td style="text-align: center;">0x3A</td>
<td style="text-align: center;">：</td>
</tr>
<tr class="even">
<td>&lt;</td>
<td style="text-align: center;">0x3C</td>
<td style="text-align: center;">＜</td>
</tr>
<tr class="odd">
<td>&gt;</td>
<td style="text-align: center;">0x3E</td>
<td style="text-align: center;">＞</td>
</tr>
<tr class="even">
<td>?</td>
<td style="text-align: center;">0x3F</td>
<td style="text-align: center;">？</td>
</tr>
<tr class="odd">
<td>\</td>
<td style="text-align: center;">0x5C</td>
<td style="text-align: center;">＼</td>
</tr>
<tr class="even">
<td>|</td>
<td style="text-align: center;">0x7C</td>
<td style="text-align: center;">｜</td>
</tr>
</tbody>
</table>
<p>File names can also not end with the following characters. These only get replaced if they are the last character in the name:</p>
<table>
<thead>
<tr class="header">
<th>Character</th>
<th style="text-align: center;">Value</th>
<th style="text-align: center;">Replacement</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td>.</td>
<td style="text-align: center;">0x2E</td>
<td style="text-align: center;">．</td>
</tr>
</tbody>
</table>
<p>Invalid UTF-8 bytes will also be <a href="https://rclone.org/overview/#invalid-utf8">replaced</a>, as they can't be used in JSON strings.</p>
<h3 id="hashes-1">Hashes</h3>
<p>MD5 hashes are stored with files. Not all files will have MD5 hashes as these have to be uploaded with the file.</p>
<h3 id="authentication">Authentication</h3>
<p>There are a number of ways of supplying credentials for Azure Files Storage. Rclone tries them in the order of the sections below.</p>
<h4 id="env-auth-1">Env Auth</h4>
<p>If the <code>env_auth</code> config parameter is <code>true</code> then rclone will pull credentials from the environment or runtime.</p>
<p>It tries these authentication methods in this order:</p>
<ol type="1">
<li>Environment Variables</li>
<li>Managed Service Identity Credentials</li>
<li>Azure CLI credentials (as used by the az tool)</li>
</ol>
<p>These are described in the following sections</p>
<h5 id="env-auth-1.-environment-variables-1">Env Auth: 1. Environment Variables</h5>
<p>If <code>env_auth</code> is set and environment variables are present rclone authenticates a service principal with a secret or certificate, or a user with a password, depending on which environment variable are set. It reads configuration from these variables, in the following order:</p>
<ol type="1">
<li>Service principal with client secret
<ul>
<li><code>AZURE_TENANT_ID</code>: ID of the service principal's tenant. Also called its "directory" ID.</li>
<li><code>AZURE_CLIENT_ID</code>: the service principal's client ID</li>
<li><code>AZURE_CLIENT_SECRET</code>: one of the service principal's client secrets</li>
</ul></li>
<li>Service principal with certificate
<ul>
<li><code>AZURE_TENANT_ID</code>: ID of the service principal's tenant. Also called its "directory" ID.</li>
<li><code>AZURE_CLIENT_ID</code>: the service principal's client ID</li>
<li><code>AZURE_CLIENT_CERTIFICATE_PATH</code>: path to a PEM or PKCS12 certificate file including the private key.</li>
<li><code>AZURE_CLIENT_CERTIFICATE_PASSWORD</code>: (optional) password for the certificate file.</li>
<li><code>AZURE_CLIENT_SEND_CERTIFICATE_CHAIN</code>: (optional) Specifies whether an authentication request will include an x5c header to support subject name / issuer based authentication. When set to "true" or "1", authentication requests include the x5c header.</li>
</ul></li>
<li>User with username and password
<ul>
<li><code>AZURE_TENANT_ID</code>: (optional) tenant to authenticate in. Defaults to "organizations".</li>
<li><code>AZURE_CLIENT_ID</code>: client ID of the application the user will authenticate to</li>
<li><code>AZURE_USERNAME</code>: a username (usually an email address)</li>
<li><code>AZURE_PASSWORD</code>: the user's password</li>
</ul></li>
<li>Workload Identity
<ul>
<li><code>AZURE_TENANT_ID</code>: Tenant to authenticate in.</li>
<li><code>AZURE_CLIENT_ID</code>: Client ID of the application the user will authenticate to.</li>
<li><code>AZURE_FEDERATED_TOKEN_FILE</code>: Path to projected service account token file.</li>
<li><code>AZURE_AUTHORITY_HOST</code>: Authority of an Azure Active Directory endpoint (default: login.microsoftonline.com).</li>
</ul></li>
</ol>
<h5 id="env-auth-2.-managed-service-identity-credentials-1">Env Auth: 2. Managed Service Identity Credentials</h5>
<p>When using Managed Service Identity if the VM(SS) on which this program is running has a system-assigned identity, it will be used by default. If the resource has no system-assigned but exactly one user-assigned identity, the user-assigned identity will be used by default.</p>
<p>If the resource has multiple user-assigned identities you will need to unset <code>env_auth</code> and set <code>use_msi</code> instead. See the <a href="#use_msi"><code>use_msi</code> section</a>.</p>
<h5 id="env-auth-3.-azure-cli-credentials-as-used-by-the-az-tool-1">Env Auth: 3. Azure CLI credentials (as used by the az tool)</h5>
<p>Credentials created with the <code>az</code> tool can be picked up using <code>env_auth</code>.</p>
<p>For example if you were to login with a service principal like this:</p>
<pre><code>az login --service-principal -u XXX -p XXX --tenant XXX</code></pre>
<p>Then you could access rclone resources like this:</p>
<pre><code>rclone lsf :azurefiles,env_auth,account=ACCOUNT:</code></pre>
<p>Or</p>
<pre><code>rclone lsf --azurefiles-env-auth --azurefiles-account=ACCOUNT :azurefiles:</code></pre>
<h4 id="account-and-shared-key-1">Account and Shared Key</h4>
<p>This is the most straight forward and least flexible way. Just fill in the <code>account</code> and <code>key</code> lines and leave the rest blank.</p>
<h4 id="sas-url-1">SAS URL</h4>
<p>To use it leave <code>account</code>, <code>key</code> and <code>connection_string</code> blank and fill in <code>sas_url</code>.</p>
<h4 id="connection-string">Connection String</h4>
<p>To use it leave <code>account</code>, <code>key</code> and "sas_url" blank and fill in <code>connection_string</code>.</p>
<h4 id="service-principal-with-client-secret-1">Service principal with client secret</h4>
<p>If these variables are set, rclone will authenticate with a service principal with a client secret.</p>
<ul>
<li><code>tenant</code>: ID of the service principal's tenant. Also called its "directory" ID.</li>
<li><code>client_id</code>: the service principal's client ID</li>
<li><code>client_secret</code>: one of the service principal's client secrets</li>
</ul>
<p>The credentials can also be placed in a file using the <code>service_principal_file</code> configuration option.</p>
<h4 id="service-principal-with-certificate-1">Service principal with certificate</h4>
<p>If these variables are set, rclone will authenticate with a service principal with certificate.</p>
<ul>
<li><code>tenant</code>: ID of the service principal's tenant. Also called its "directory" ID.</li>
<li><code>client_id</code>: the service principal's client ID</li>
<li><code>client_certificate_path</code>: path to a PEM or PKCS12 certificate file including the private key.</li>
<li><code>client_certificate_password</code>: (optional) password for the certificate file.</li>
<li><code>client_send_certificate_chain</code>: (optional) Specifies whether an authentication request will include an x5c header to support subject name / issuer based authentication. When set to "true" or "1", authentication requests include the x5c header.</li>
</ul>
<p><strong>NB</strong> <code>client_certificate_password</code> must be obscured - see <a href="https://rclone.org/commands/rclone_obscure/">rclone obscure</a>.</p>
<h4 id="user-with-username-and-password-1">User with username and password</h4>
<p>If these variables are set, rclone will authenticate with username and password.</p>
<ul>
<li><code>tenant</code>: (optional) tenant to authenticate in. Defaults to "organizations".</li>
<li><code>client_id</code>: client ID of the application the user will authenticate to</li>
<li><code>username</code>: a username (usually an email address)</li>
<li><code>password</code>: the user's password</li>
</ul>
<p>Microsoft doesn't recommend this kind of authentication, because it's less secure than other authentication flows. This method is not interactive, so it isn't compatible with any form of multi-factor authentication, and the application must already have user or admin consent. This credential can only authenticate work and school accounts; it can't authenticate Microsoft accounts.</p>
<p><strong>NB</strong> <code>password</code> must be obscured - see <a href="https://rclone.org/commands/rclone_obscure/">rclone obscure</a>.</p>
<h4 id="use_msi">Managed Service Identity Credentials</h4>
<p>If <code>use_msi</code> is set then managed service identity credentials are used. This authentication only works when running in an Azure service. <code>env_auth</code> needs to be unset to use this.</p>
<p>However if you have multiple user identities to choose from these must be explicitly specified using exactly one of the <code>msi_object_id</code>, <code>msi_client_id</code>, or <code>msi_mi_res_id</code> parameters.</p>
<p>If none of <code>msi_object_id</code>, <code>msi_client_id</code>, or <code>msi_mi_res_id</code> is set, this is is equivalent to using <code>env_auth</code>.</p>
<h3 id="standard-options-32">Standard options</h3>
<p>Here are the Standard options specific to azurefiles (Microsoft Azure Files).</p>
<h4 id="azurefiles-account">--azurefiles-account</h4>
<p>Azure Storage Account Name.</p>
<p>Set this to the Azure Storage Account Name in use.</p>
<p>Leave blank to use SAS URL or connection string, otherwise it needs to be set.</p>
<p>If this is blank and if env_auth is set it will be read from the environment variable <code>AZURE_STORAGE_ACCOUNT_NAME</code> if possible.</p>
<p>Properties:</p>
<ul>
<li>Config: account</li>
<li>Env Var: RCLONE_AZUREFILES_ACCOUNT</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="azurefiles-share-name">--azurefiles-share-name</h4>
<p>Azure Files Share Name.</p>
<p>This is required and is the name of the share to access.</p>
<p>Properties:</p>
<ul>
<li>Config: share_name</li>
<li>Env Var: RCLONE_AZUREFILES_SHARE_NAME</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="azurefiles-env-auth">--azurefiles-env-auth</h4>
<p>Read credentials from runtime (environment variables, CLI or MSI).</p>
<p>See the <a href="/azurefiles#authentication">authentication docs</a> for full info.</p>
<p>Properties:</p>
<ul>
<li>Config: env_auth</li>
<li>Env Var: RCLONE_AZUREFILES_ENV_AUTH</li>
<li>Type: bool</li>
<li>Default: false</li>
</ul>
<h4 id="azurefiles-key">--azurefiles-key</h4>
<p>Storage Account Shared Key.</p>
<p>Leave blank to use SAS URL or connection string.</p>
<p>Properties:</p>
<ul>
<li>Config: key</li>
<li>Env Var: RCLONE_AZUREFILES_KEY</li>
<li>Type: string</li>
<li>Required: false</li>
</ul>
<h4 id="azurefiles-sas-url">--azurefiles-sas-url</h4>
<p>SAS URL.</p>
<p>Leave blank if using account/key or connection string.</p>
<p>Properties:</p>
<ul>
<li>Config: sas_url</li