From 510ac341e193976171d29b8aeb81a30a37cfd2a1 Mon Sep 17 00:00:00 2001
From: Nick Craig-Wood <nick@craig-wood.com>
Date: Wed, 2 Sep 2020 16:59:04 +0100
Subject: [PATCH] Version v1.53.0

---
 MANUAL.html                                  | 19840 ++++++------
 MANUAL.md                                    |  3375 +-
 MANUAL.txt                                   | 21661 +++++++------
 docs/content/amazonclouddrive.md             |    19 +-
 docs/content/b2.md                           |    34 +
 docs/content/box.md                          |    46 +-
 docs/content/cache.md                        |     2 +
 docs/content/changelog.md                    |   177 +
 docs/content/commands/rclone.md              |     4 +-
 docs/content/commands/rclone_check.md        |    34 +-
 docs/content/commands/rclone_copy.md         |     4 +-
 docs/content/commands/rclone_cryptcheck.md   |    33 +-
 docs/content/commands/rclone_dedupe.md       |    53 +-
 docs/content/commands/rclone_delete.md       |     3 +
 docs/content/commands/rclone_link.md         |    27 +-
 docs/content/commands/rclone_mount.md        |   165 +-
 docs/content/commands/rclone_move.md         |     2 +-
 docs/content/commands/rclone_moveto.md       |     2 +-
 docs/content/commands/rclone_obscure.md      |    27 +-
 docs/content/commands/rclone_purge.md        |     3 +
 docs/content/commands/rclone_serve_dlna.md   |   173 +-
 docs/content/commands/rclone_serve_ftp.md    |   165 +-
 docs/content/commands/rclone_serve_http.md   |   165 +-
 docs/content/commands/rclone_serve_sftp.md   |   165 +-
 docs/content/commands/rclone_serve_webdav.md |   165 +-
 docs/content/commands/rclone_sync.md         |     4 +-
 docs/content/commands/rclone_touch.md        |     1 +
 docs/content/commands/rclone_tree.md         |     2 +-
 docs/content/crypt.md                        |    22 +
 docs/content/drive.md                        |   120 +-
 docs/content/dropbox.md                      |    33 +-
 docs/content/flags.md                        |   125 +-
 docs/content/ftp.md                          |     8 +-
 docs/content/googlecloudstorage.md           |    46 +-
 docs/content/googlephotos.md                 |    33 +-
 docs/content/hubic.md                        |    33 +-
 docs/content/jottacloud.md                   |    10 -
 docs/content/koofr.md                        |     2 +
 docs/content/local.md                        |    32 +
 docs/content/mailru.md                       |     2 +
 docs/content/mega.md                         |     2 +
 docs/content/onedrive.md                     |    54 +-
 docs/content/opendrive.md                    |     2 +
 docs/content/pcloud.md                       |    52 +-
 docs/content/rc.md                           |   209 +-
 docs/content/s3.md                           |   362 +-
 docs/content/seafile.md                      |     4 +
 docs/content/sftp.md                         |    31 +-
 docs/content/webdav.md                       |     2 +
 docs/content/yandex.md                       |    37 +-
 rclone.1                                     | 27761 ++++++++---------
 51 files changed, 39713 insertions(+), 35620 deletions(-)

diff --git a/MANUAL.html b/MANUAL.html
index 5a1bde26c..65a06a1a2 100644
--- a/MANUAL.html
+++ b/MANUAL.html
@@ -5,7 +5,6 @@
   <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" />
-  <meta name="dcterms.date" content="2020-05-27" />
   <title>rclone(1) User Manual</title>
   <style type="text/css">
       code{white-space: pre-wrap;}
@@ -18,31 +17,31 @@
 <header id="title-block-header">
 <h1 class="title">rclone(1) User Manual</h1>
 <p class="author">Nick Craig-Wood</p>
-<p class="date">May 27, 2020</p>
+<p class="date">Sep 02, 2020</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="#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 40 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 can be used at the command line, in scripts or via its <a href="/rc">API</a>.</p>
-<p>Users have called 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 your data 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 your local disk.</p>
+<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 40 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/cache/">caching</a>, <a href="https://rclone.org/chunker/">chunking</a> and <a href="https://rclone.org/union/">joining</a>.</p>
-<p>Rclone can <a href="https://rclone.org/commands/rclone_mount/">mount</a> any local, cloud or virtual filesystem as a disk on Windows, macOS, linux and FreeBSD, and also serve 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 <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 are 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 have built innovative backup, restore, GUI and business process solutions using the rclone command line or API.</p>
-<p>Let rclone do the heavy lifting of communicating with cloud storage.</p>
-<h2 id="what">What can rclone do for you</h2>
-<p>Rclone can help you:</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>
@@ -71,7 +70,7 @@
 <li>Experimental <a href="https://rclone.org/gui/">Web based GUI</a></li>
 </ul>
 <h2 id="providers">Supported providers</h2>
-<p>(There are many other providers, built on standard protocols such as WebDAV or S3, that work out of the box.)</p>
+<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>Alibaba Cloud (Aliyun) Object Storage System (OSS)</li>
@@ -146,7 +145,7 @@
 <pre><code>curl https://rclone.org/install.sh | sudo bash</code></pre>
 <p>For beta installation, run:</p>
 <pre><code>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>
+<p>Note that this script checks the version of rclone installed first and won't re-download if not needed.</p>
 <h2 id="linux-installation-from-precompiled-binary">Linux installation from precompiled binary</h2>
 <p>Fetch and unpack</p>
 <pre><code>curl -O https://downloads.rclone.org/rclone-current-linux-amd64.zip
@@ -200,7 +199,11 @@ rclone v1.49.1
 <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>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>
+<li>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>.
+<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>
@@ -228,16 +231,19 @@ docker run --rm \
 ls ~/data/mount
 kill %1</code></pre>
 <h2 id="install-from-source">Install from source</h2>
-<p>Make sure you have at least <a href="https://golang.org/">Go</a> 1.7 installed. <a href="https://golang.org/dl/">Download go</a> if necessary. The latest release is recommended. Then</p>
+<p>Make sure you have at least <a href="https://golang.org/">Go</a> 1.11 installed. <a href="https://golang.org/dl/">Download go</a> if necessary. The latest release is recommended. Then</p>
 <pre><code>git clone https://github.com/rclone/rclone.git
 cd rclone
 go build
 ./rclone version</code></pre>
-<p>You can also build and install rclone in the <a href="https://github.com/golang/go/wiki/GOPATH">GOPATH</a> (which defaults to <code>~/go</code>) with:</p>
-<pre><code>go get -u -v github.com/rclone/rclone</code></pre>
-<p>and this will build the binary in <code>$GOPATH/bin</code> (<code>~/go/bin/rclone</code> by default) after downloading the source to <code>$GOPATH/src/github.com/rclone/rclone</code> (<code>~/go/src/github.com/rclone/rclone</code> by default).</p>
+<p>This will leave you a checked out version of rclone you can modify and send pull requests with. If you use <code>make</code> instead of <code>go build</code> then the rclone build will have the correct version information in it.</p>
+<p>You can also build the latest stable rclone with:</p>
+<pre><code>go get github.com/rclone/rclone</code></pre>
+<p>or the latest version (equivalent to the beta) with</p>
+<pre><code>go get github.com/rclone/rclone@master</code></pre>
+<p>These will build the binary in <code>$(go env GOPATH)/bin</code> (<code>~/go/bin/rclone</code> by default) after downloading the source to the go module cache. Note - do <strong>not</strong> use the <code>-u</code> flag here. This causes go to try to update the depencencies that rclone uses and sometimes these don't work with the current version of rclone.</p>
 <h2 id="installation-with-ansible">Installation with Ansible</h2>
-<p>This can be done with <a href="https://github.com/stefangweichinger/ansible-rclone">Stefan Weichinger’s ansible role</a>.</p>
+<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>
@@ -247,7 +253,7 @@ go build
       roles:
           - rclone</code></pre>
 <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 <code>--config</code> entry for how to find the config file and choose its location.)</p>
+<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 <code>--config</code> 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>
@@ -296,13 +302,14 @@ go build
 <p>Rclone syncs a directory tree from one storage system to another.</p>
 <p>Its syntax is like this</p>
 <pre><code>Syntax: [options] subcommand &lt;parameters&gt; &lt;parameters...&gt;</code></pre>
-<p>Source and destination paths are specified by the name you gave the storage system in the config file then the sub path, eg “drive:myfolder” to look at “myfolder” in Google drive.</p>
+<p>Source and destination paths are specified by the name you gave the storage system in the config file then the sub path, eg "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>-i</code> / <code>--interactive</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 /local/path remote:path # syncs /local/path to the remote</code></pre>
+rclone sync -i /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>
@@ -330,12 +337,12 @@ rclone sync /local/path remote:path # syncs /local/path to the remote</code></pr
 <h1 id="rclone-copy">rclone copy</h1>
 <p>Copy files from source to dest, skipping already copied</p>
 <h2 id="synopsis-1">Synopsis</h2>
-<p>Copy the source to the destination. Doesn’t transfer unchanged files, testing by size and modification time or MD5SUM. Doesn’t delete files from the destination.</p>
-<p>Note that it is always the contents of the directory that is synced, not the directory 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>If dest:path doesn’t exist, it is created and the source:path contents go there.</p>
+<p>Copy the source to the destination. Doesn't transfer unchanged files, testing by size and modification time or MD5SUM. Doesn't delete files from the destination.</p>
+<p>Note that it is always the contents of the directory that is synced, not the directory 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>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>
+<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>
@@ -344,11 +351,12 @@ 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 / - 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>If you are familiar with <code>rsync</code>, rclone always works as if you had written a trailing / - 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><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>-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
@@ -361,11 +369,12 @@ destpath/sourcepath/two.txt</code></pre>
 <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 unchanged files, testing by size and modification time or MD5SUM. Destination is updated to match source, including deleting files if necessary.</p>
-<p><strong>Important</strong>: Since this can cause data loss, test first with the <code>--dry-run</code> flag to see exactly what would be copied and deleted.</p>
-<p>Note that files in the destination won’t be deleted if there were any errors at any point.</p>
-<p>It is always the contents of the directory that is synced, not the directory 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 <code>copy</code> command above if unsure.</p>
-<p>If dest:path doesn’t exist, it is created and the source:path contents go there.</p>
+<p>Sync the source to the destination, changing the destination only. Doesn't transfer unchanged files, testing by size and modification time or MD5SUM. Destination is updated to match source, including deleting files if necessary.</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 -i SOURCE remote:DESTINATION</code></pre>
+<p>Note that files in the destination won't be deleted if there were any errors at any point.</p>
+<p>It is always the contents of the directory that is synced, not the directory 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 <code>copy</code> command above if unsure.</p>
+<p>If dest:path doesn't exist, it is created and the source:path contents go there.</p>
 <p><strong>Note</strong>: Use the <code>-P</code>/<code>--progress</code> flag to view real-time transfer statistics</p>
 <pre><code>rclone sync source:path dest:path [flags]</code></pre>
 <h2 id="options-2">Options</h2>
@@ -382,9 +391,9 @@ destpath/sourcepath/two.txt</code></pre>
 <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>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 –delete-empty-src-dirs 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><strong>Important</strong>: Since this can cause data loss, test first with the –dry-run flag.</p>
+<p>If you want to delete empty source directories after move, use the --delete-empty-src-dirs 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><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>
@@ -401,14 +410,15 @@ destpath/sourcepath/two.txt</code></pre>
 <h2 id="synopsis-4">Synopsis</h2>
 <p>Remove the files in path. Unlike <code>purge</code> it obeys include/exclude filters so can be used to selectively delete files.</p>
 <p><code>rclone delete</code> only deletes objects but leaves the directory structure alone. If you want to delete a directory and all of its contents use <code>rclone purge</code></p>
-<p>If you supply the –rmdirs flag, it will remove all empty directories along with it.</p>
+<p>If you supply the --rmdirs flag, it will remove all empty directories along with it.</p>
 <p>Eg delete all files bigger than 100MBytes</p>
 <p>Check what would be deleted first (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 delete</p>
 <pre><code>rclone --min-size 100M delete remote:path</code></pre>
-<p>That reads “delete everything with a minimum size of 100 MB”, hence delete all files bigger than 100MBytes.</p>
+<p>That reads "delete everything with a minimum size of 100 MB", hence delete all files bigger than 100MBytes.</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
@@ -422,6 +432,7 @@ rclone --dry-run --min-size 100M delete remote:path</code></pre>
 <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 <code>delete</code> if you want to selectively delete files.</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>
@@ -431,9 +442,9 @@ rclone --dry-run --min-size 100M delete remote:path</code></pre>
 <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>
+<p>Make the path if it doesn't already exist.</p>
 <h2 id="synopsis-6">Synopsis</h2>
-<p>Make the path if it doesn’t already exist.</p>
+<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>
@@ -445,7 +456,7 @@ rclone --dry-run --min-size 100M delete remote:path</code></pre>
 <h1 id="rclone-rmdir">rclone rmdir</h1>
 <p>Remove the path if empty.</p>
 <h2 id="synopsis-7">Synopsis</h2>
-<p>Remove the path. Note that you can’t remove a path with objects in it, use purge for that.</p>
+<p>Remove the path. Note that you can't remove a path with objects in it, use purge for that.</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>
@@ -457,15 +468,29 @@ rclone --dry-run --min-size 100M delete remote:path</code></pre>
 <h1 id="rclone-check">rclone check</h1>
 <p>Checks the files in the source and destination match.</p>
 <h2 id="synopsis-8">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 which don’t match. It doesn’t alter the source or destination.</p>
-<p>If you supply the –size-only flag, it will only compare the sizes not the hashes as well. Use this for a quick check.</p>
-<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 –one-way flag, it will only check that files in source match the files in destination, not the other way around. Meaning extra files in destination that are not in the source will not trigger an error.</p>
+<p>Checks the files in the source and destination match. It compares sizes and hashes (MD5 or SHA1) and logs a report of files which don't match. It doesn't alter the source or destination.</p>
+<p>If you supply the --size-only flag, it will only compare the sizes not the hashes as well. Use this for a quick check.</p>
+<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 <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>--src-only</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><code>- path</code> means path was missing on the source, so only in the destination</li>
+<li><code>+ path</code> means path was missing on the destination, so only in the source</li>
+<li><code>* path</code> 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>
 <pre><code>rclone check source:path dest:path [flags]</code></pre>
 <h2 id="options-8">Options</h2>
-<pre><code>      --download   Check by downloading rather than with hash.
-  -h, --help       help for check
-      --one-way    Check one way only, source files must exist on remote</code></pre>
+<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 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>See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
 <h2 id="see-also-8">SEE ALSO</h2>
 <ul>
@@ -491,9 +516,9 @@ rclone --dry-run --min-size 100M delete remote:path</code></pre>
 <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 “–max-depth 1” 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 “-R” to make them recurse.</p>
-<p>Listing a non existent directory will produce an error except for remotes which can’t have empty directories (eg s3, swift, gcs, etc - the bucket based remotes).</p>
+<p>Note that <code>ls</code> and <code>lsl</code> recurse by default - use "--max-depth 1" 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 "-R" to make them recurse.</p>
+<p>Listing a non existent directory will produce an error except for remotes which can't have empty directories (eg s3, swift, gcs, etc - 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>
@@ -515,7 +540,7 @@ rclone --dry-run --min-size 100M delete remote:path</code></pre>
           -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 “rclone lsf –dirs-only”.</p>
+<p>If you just want the directory names use "rclone lsf --dirs-only".</p>
 <p>Any of the filtering options can be applied to this command.</p>
 <p>There are several related list commands</p>
 <ul>
@@ -526,9 +551,9 @@ rclone --dry-run --min-size 100M delete remote:path</code></pre>
 <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 “–max-depth 1” 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 “-R” to make them recurse.</p>
-<p>Listing a non existent directory will produce an error except for remotes which can’t have empty directories (eg s3, swift, gcs, etc - the bucket based remotes).</p>
+<p>Note that <code>ls</code> and <code>lsl</code> recurse by default - use "--max-depth 1" 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 "-R" to make them recurse.</p>
+<p>Listing a non existent directory will produce an error except for remotes which can't have empty directories (eg s3, swift, gcs, etc - 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
@@ -558,9 +583,9 @@ rclone --dry-run --min-size 100M delete remote:path</code></pre>
 <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 “–max-depth 1” 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 “-R” to make them recurse.</p>
-<p>Listing a non existent directory will produce an error except for remotes which can’t have empty directories (eg s3, swift, gcs, etc - the bucket based remotes).</p>
+<p>Note that <code>ls</code> and <code>lsl</code> recurse by default - use "--max-depth 1" 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 "-R" to make them recurse.</p>
+<p>Listing a non existent directory will produce an error except for remotes which can't have empty directories (eg s3, swift, gcs, etc - 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>
@@ -615,7 +640,7 @@ rclone --dry-run --min-size 100M delete remote:path</code></pre>
 rclone v1.41
 - os/arch: linux/amd64
 - go version: go1.10</code></pre>
-<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>
+<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)
@@ -649,11 +674,14 @@ beta:   1.42.0.5      (released 2018-06-17)
 <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 files and delete/rename them.</p>
+<p>Interactively find duplicate filenames and delete/rename them.</p>
 <h2 id="synopsis-17">Synopsis</h2>
-<p>By default <code>dedupe</code> interactively finds duplicate files and offers to delete all but one or rename them to be different. Only useful with Google Drive which can have duplicate file names.</p>
-<p>In the first pass it will merge directories with the same name. It will do this iteratively until all the identical directories have been merged.</p>
-<p>The <code>dedupe</code> command will delete all but one of any identical (same md5sum) files it finds without confirmation. This means that for most duplicated files the <code>dedupe</code> command will not be interactive. You can use <code>--dry-run</code> to see what would happen without doing anything.</p>
+<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.</p>
+<p>This is only useful with backends like Google Drive which can have duplicate file names. It can be run on wrapping backends (eg crypt) if they wrap a backend which supports duplicate file names.</p>
+<p>In the first pass it will merge directories with the same name. It will do this iteratively until all the identically named directories have been merged.</p>
+<p>In the second pass, for every group of duplicate file names, it will delete all but one identical files 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 hash. If the backend does not support hashes (eg 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><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
@@ -667,22 +695,22 @@ beta:   1.42.0.5      (released 2018-06-17)
 <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 duplicates - deleting identical copies
-one.txt: Deleting 2/3 identical duplicates (md5sum &quot;1eedaa9fe86fd4b8632e2ac549403b36&quot;)
+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, md5sum 1eedaa9fe86fd4b8632e2ac549403b36
-  2:       564374 bytes, 2016-03-05 16:23:06.731000000, md5sum 7594e7dc9fc28f727c42ee3e0749de81
+  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 duplicates - deleting identical copies
+two.txt: Found 3 files with duplicates names
 two.txt: 3 duplicates remain
-  1:       564374 bytes, 2016-03-05 16:22:52.118000000, md5sum 7594e7dc9fc28f727c42ee3e0749de81
-  2:      6048320 bytes, 2016-03-05 16:22:46.185000000, md5sum 1eedaa9fe86fd4b8632e2ac549403b36
-  3:      1744073 bytes, 2016-03-05 16:22:38.104000000, md5sum 851957f7fb6f0bc4ce76be966d336802
+  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)
@@ -740,13 +768,13 @@ Other:   8.241G</code></pre>
 <li>Objects: total number of objects in the storage</li>
 </ul>
 <p>Note that not all the backends provide all the fields - they will be missing if they are not known for that backend. Where it is known that the value is unlimited the value will also be omitted.</p>
-<p>Use the –full flag to see the numbers written out in full, eg</p>
+<p>Use the --full flag to see the numbers written out in full, eg</p>
 <pre><code>Total:   18253611008
 Used:    7993453766
 Free:    1411001220
 Trashed: 104857602
 Other:   8849156022</code></pre>
-<p>Use the –json flag for a computer readable output, eg</p>
+<p>Use the --json flag for a computer readable output, eg</p>
 <pre><code>{
     &quot;total&quot;: 18253611008,
     &quot;used&quot;: 7993453766,
@@ -768,7 +796,7 @@ Other:   8849156022</code></pre>
 <p>Remote authorization.</p>
 <h2 id="synopsis-19">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 the –auth-no-open-browser to prevent rclone to open auth link in default browser automatically.</p>
+<p>Use the --auth-no-open-browser to prevent rclone to open auth link in default browser automatically.</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
@@ -781,7 +809,7 @@ Other:   8849156022</code></pre>
 <h1 id="rclone-backend">rclone backend</h1>
 <p>Run a backend specific command.</p>
 <h2 id="synopsis-20">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>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>
@@ -812,7 +840,7 @@ rclone backend help &lt;backendname&gt;</code></pre>
 <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 –head flag to print characters only at the start, –tail for the end and –offset and –count to print a section in the middle. Note that if offset is negative it will count from the end, so –offset -1 –count 1 is equivalent to –tail 1.</p>
+<p>Use the --head flag to print characters only at the start, --tail for the end and --offset and --count to print a section in the middle. Note that if offset is negative it will count from the end, so --offset -1 --count 1 is equivalent to --tail 1.</p>
 <pre><code>rclone cat remote:path [flags]</code></pre>
 <h2 id="options-21">Options</h2>
 <pre><code>      --count int    Only print N characters. (default -1)
@@ -833,8 +861,8 @@ rclone backend help &lt;backendname&gt;</code></pre>
 <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</code></pre>
 <p>Note that if the config process would normally ask a question the default is taken. Each time that happens rclone will print 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 “–obscure” flag, or if you are 100% certain you are already passing obscured passwords then use “–no-obscure”. You can also set osbscured passwords using the “rclone config password” command.</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 "--obscure" flag, or if you are 100% certain you are already passing obscured passwords then use "--no-obscure". You can also set osbscured passwords using the "rclone config password" command.</p>
 <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>
 <pre><code>rclone config create `name` `type` [`key` `value`]* [flags]</code></pre>
@@ -864,7 +892,7 @@ rclone backend help &lt;backendname&gt;</code></pre>
 <h2 id="synopsis-24">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>
+<p>To reconnect use "rclone config reconnect".</p>
 <pre><code>rclone config disconnect remote: [flags]</code></pre>
 <h2 id="options-24">Options</h2>
 <pre><code>  -h, --help   help for disconnect</code></pre>
@@ -912,10 +940,10 @@ rclone backend help &lt;backendname&gt;</code></pre>
 <h1 id="rclone-config-password">rclone config password</h1>
 <p>Update password in an existing remote.</p>
 <h2 id="synopsis-28">Synopsis</h2>
-<p>Update an existing remote’s password. The password should be passed in pairs of <code>key</code> <code>value</code>.</p>
+<p>Update an existing remote's password. The password should be passed in pairs of <code>key</code> <code>value</code>.</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</code></pre>
-<p>This command is obsolete now that “config update” and “config create” both support obscuring passwords directly.</p>
+<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-28">Options</h2>
 <pre><code>  -h, --help   help for password</code></pre>
@@ -940,7 +968,7 @@ rclone backend help &lt;backendname&gt;</code></pre>
 <p>Re-authenticates user with remote.</p>
 <h2 id="synopsis-30">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>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-30">Options</h2>
@@ -965,12 +993,12 @@ rclone backend help &lt;backendname&gt;</code></pre>
 <h1 id="rclone-config-update">rclone config update</h1>
 <p>Update options in an existing remote.</p>
 <h2 id="synopsis-32">Synopsis</h2>
-<p>Update an existing remote’s options. The options should be passed in in pairs of <code>key</code> <code>value</code>.</p>
+<p>Update an existing remote's options. The options should be passed in in pairs of <code>key</code> <code>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 swift env_auth true</code></pre>
-<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 “–obscure” flag, or if you are 100% certain you are already passing obscured passwords then use “–no-obscure”. You can also set osbscured passwords using the “rclone config password” command.</p>
-<p>If the remote uses OAuth the token will be updated, if you don’t require this add an extra parameter thus:</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 "--obscure" flag, or if you are 100% certain you are already passing obscured passwords then use "--no-obscure". You can also set osbscured passwords using the "rclone config password" command.</p>
+<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 swift env_auth true config_refresh_token false</code></pre>
 <pre><code>rclone config update `name` [`key` `value`]+ [flags]</code></pre>
 <h2 id="options-32">Options</h2>
@@ -1009,7 +1037,7 @@ rclone backend help &lt;backendname&gt;</code></pre>
 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 unchanged files, testing by size and modification time or MD5SUM. It doesn’t delete files from the destination.</p>
+<p>This doesn't transfer unchanged files, 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-34">Options</h2>
@@ -1022,10 +1050,10 @@ if src is directory
 <h1 id="rclone-copyurl">rclone copyurl</h1>
 <p>Copy url content to dest.</p>
 <h2 id="synopsis-35">Synopsis</h2>
-<p>Download a URL’s content and copy it to the destination without saving it in temporary storage.</p>
-<p>Setting –auto-filename will cause the file name to be retrieved from the from URL (after any redirections) and used in the destination path.</p>
-<p>Setting –no-clobber will prevent overwriting file on the destination if there is one with the same name.</p>
-<p>Setting –stdout or making the output file name “-” will cause the output to be written to standard output.</p>
+<p>Download a URL's content and copy it to the destination without saving it in temporary storage.</p>
+<p>Setting --auto-filename will cause the file name to be retrieved from the from URL (after any redirections) and used in the destination path.</p>
+<p>Setting --no-clobber will prevent overwriting file on the destination if there is one with the same name.</p>
+<p>Setting --stdout or making the output file name "-" will cause the output to be written to standard output.</p>
 <pre><code>rclone copyurl https://example.com dest:path [flags]</code></pre>
 <h2 id="options-35">Options</h2>
 <pre><code>  -a, --auto-filename   Get the file name from the URL and use it for destination file path
@@ -1048,11 +1076,26 @@ if src is directory
 <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 –one-way flag, it will only check that files in source match the files in destination, not the other way around. Meaning extra files in destination that are not in the source will not trigger an error.</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>--src-only</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><code>- path</code> means path was missing on the source, so only in the destination</li>
+<li><code>+ path</code> means path was missing on the destination, so only in the source</li>
+<li><code>* path</code> 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>
 <pre><code>rclone cryptcheck remote:path cryptedremote:path [flags]</code></pre>
 <h2 id="options-36">Options</h2>
-<pre><code>  -h, --help      help for cryptcheck
-      --one-way   Check one way only, source files must exist on destination</code></pre>
+<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>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>
@@ -1062,7 +1105,7 @@ if src is directory
 <p>Cryptdecode returns unencrypted file names.</p>
 <h2 id="synopsis-37">Synopsis</h2>
 <p>rclone cryptdecode returns unencrypted file names when provided with a list of encrypted file names. List limit is 10 items.</p>
-<p>If you supply the –reverse flag, it will return encrypted file names.</p>
+<p>If you supply the --reverse flag, it will return encrypted file names.</p>
 <p>use it like this</p>
 <pre><code>rclone cryptdecode encryptedremote: encryptedfilename1 encryptedfilename2
 
@@ -1079,7 +1122,7 @@ rclone cryptdecode --reverse encryptedremote: filename1 filename2</code></pre>
 <h1 id="rclone-deletefile">rclone deletefile</h1>
 <p>Remove a single file from remote.</p>
 <h2 id="synopsis-38">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>
+<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-38">Options</h2>
 <pre><code>  -h, --help   help for deletefile</code></pre>
@@ -1091,7 +1134,7 @@ rclone cryptdecode --reverse encryptedremote: filename1 filename2</code></pre>
 <h1 id="rclone-genautocomplete">rclone genautocomplete</h1>
 <p>Output completion script for a given shell.</p>
 <h2 id="synopsis-39">Synopsis</h2>
-<p>Generates a shell completion script for rclone. Run with –help to list the supported shells.</p>
+<p>Generates a shell completion script for rclone. Run with --help to list the supported shells.</p>
 <h2 id="options-39">Options</h2>
 <pre><code>  -h, --help   help for genautocomplete</code></pre>
 <p>See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
@@ -1190,13 +1233,19 @@ Supported hashes are:
 <h1 id="rclone-link">rclone link</h1>
 <p>Generate public link to file/folder.</p>
 <h2 id="synopsis-45">Synopsis</h2>
-<p>rclone link will create or retrieve a public link to the given file or folder.</p>
+<p>rclone link will 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/</code></pre>
-<p>If successful, the last line of the output will contain the link. Exact capabilities depend on the remote, but the link will always be created with the least constraints – e.g. no expiry, no password protection, accessible without account.</p>
+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-45">Options</h2>
-<pre><code>  -h, --help   help for link</code></pre>
+<pre><code>      --expire Duration   The amount of time that the link will be valid (default 100y)
+  -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-45">SEE ALSO</h2>
 <ul>
@@ -1227,7 +1276,7 @@ canole
 diwogej7
 ferejej3gux/
 fubuwic</code></pre>
-<p>Use the –format option to control what gets listed. By default this is just the path, but you can use these parameters to control the output:</p>
+<p>Use the --format 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
@@ -1237,7 +1286,7 @@ o - Original ID of underlying object
 m - MimeType of object if known
 e - encrypted name
 T - tier of storage if known, eg &quot;Hot&quot; or &quot;Cool&quot;</code></pre>
-<p>So if you wanted the path, size and modification time, you would use –format “pst”, or maybe –format “tsp” to put the path last.</p>
+<p>So if you wanted the path, size and modification time, you would use --format "pst", or maybe --format "tsp" 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
@@ -1245,7 +1294,7 @@ T - tier of storage if known, eg &quot;Hot&quot; or &quot;Cool&quot;</code></pre
 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 “–hash” 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>If you specify "h" in the format you will get the MD5 hash by default, use the "--hash" 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>
@@ -1255,8 +1304,8 @@ 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 –separator flag. Note that separators aren’t escaped in the path so putting it last is a good strategy.</p>
+<p>(Though "rclone md5sum ." is an easier way of typing this.)</p>
+<p>By default the separator is ";" this can be changed with the --separator 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
@@ -1270,7 +1319,7 @@ cd65ac234e6fea5925974a51cdd865cc  canole
 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 –absolute parameter is useful for making lists of files to pass to an rclone copy with the –files-from-raw flag.</p>
+<p>Note that the --absolute parameter is useful for making lists of files to pass to an rclone copy with the --files-from-raw 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>
@@ -1284,9 +1333,9 @@ rclone copy --files-from-raw new_files /path/to/local remote:path</code></pre>
 <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 “–max-depth 1” 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 “-R” to make them recurse.</p>
-<p>Listing a non existent directory will produce an error except for remotes which can’t have empty directories (eg s3, swift, gcs, etc - the bucket based remotes).</p>
+<p>Note that <code>ls</code> and <code>lsl</code> recurse by default - use "--max-depth 1" 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 "-R" to make them recurse.</p>
+<p>Listing a non existent directory will produce an error except for remotes which can't have empty directories (eg s3, swift, gcs, etc - the bucket based remotes).</p>
 <pre><code>rclone lsf remote:path [flags]</code></pre>
 <h2 id="options-47">Options</h2>
 <pre><code>      --absolute           Put a leading / in front of path names.
@@ -1309,16 +1358,16 @@ rclone copy --files-from-raw new_files /path/to/local remote:path</code></pre>
 <h2 id="synopsis-48">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>
-<p>{ “Hashes” : { “SHA-1” : “f572d396fae9206628714fb2ce00f72e94f2258f”, “MD5” : “b1946ac92492d2347c6235b4d2611184”, “DropboxHash” : “ecb65bb98f9d905b70458986c39fcbad7715e5f2fcc3b1f07767d7c83e2438cc” }, “ID”: “y2djkhiujf83u33”, “OrigID”: “UYOJVTUW00Q1RzTDA”, “IsBucket” : false, “IsDir” : false, “MimeType” : “application/octet-stream”, “ModTime” : “2017-05-31T16:15:57.034468261+01:00”, “Name” : “file.txt”, “Encrypted” : “v0qpsdq8anpci8n929v3uu9338”, “EncryptedPath” : “kja9098349023498/v0qpsdq8anpci8n929v3uu9338”, “Path” : “full/path/goes/here/file.txt”, “Size” : 6, “Tier” : “hot”, }</p>
-<p>If –hash is not specified the Hashes property won’t be emitted. The types of hash can be specified with the –hash-type parameter (which may be repeated). If –hash-type is set then it implies –hash.</p>
-<p>If –no-modtime is specified then ModTime will be blank. This can speed things up on remotes where reading the ModTime takes an extra request (eg s3, swift).</p>
-<p>If –no-mimetype is specified then MimeType will be blank. This can speed things up on remotes where reading the MimeType takes an extra request (eg s3, swift).</p>
-<p>If –encrypted is not specified the Encrypted won’t be emitted.</p>
-<p>If –dirs-only is not specified files in addition to directories are returned</p>
-<p>If –files-only is not specified directories in addition to the files will be returned.</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 –recursive the Path will always be the same as Name.</p>
-<p>If the directory is a bucket in a bucket based backend, then “IsBucket” will be set to true. This key won’t be present unless it is “true”.</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 (eg 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>{ "Hashes" : { "SHA-1" : "f572d396fae9206628714fb2ce00f72e94f2258f", "MD5" : "b1946ac92492d2347c6235b4d2611184", "DropboxHash" : "ecb65bb98f9d905b70458986c39fcbad7715e5f2fcc3b1f07767d7c83e2438cc" }, "ID": "y2djkhiujf83u33", "OrigID": "UYOJVTUW00Q1RzTDA", "IsBucket" : false, "IsDir" : false, "MimeType" : "application/octet-stream", "ModTime" : "2017-05-31T16:15:57.034468261+01:00", "Name" : "file.txt", "Encrypted" : "v0qpsdq8anpci8n929v3uu9338", "EncryptedPath" : "kja9098349023498/v0qpsdq8anpci8n929v3uu9338", "Path" : "full/path/goes/here/file.txt", "Size" : 6, "Tier" : "hot", }</p>
+<p>If --hash is not specified the Hashes property won't be emitted. The types of hash can be specified with the --hash-type parameter (which may be repeated). If --hash-type is set then it implies --hash.</p>
+<p>If --no-modtime is specified then ModTime will be blank. This can speed things up on remotes where reading the ModTime takes an extra request (eg s3, swift).</p>
+<p>If --no-mimetype is specified then MimeType will be blank. This can speed things up on remotes where reading the MimeType takes an extra request (eg s3, swift).</p>
+<p>If --encrypted is not specified the Encrypted won't be emitted.</p>
+<p>If --dirs-only is not specified files in addition to directories are returned</p>
+<p>If --files-only is not specified directories in addition to the files will be returned.</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 --recursive the Path will always be the same as Name.</p>
+<p>If the directory is a bucket in a bucket based backend, then "IsBucket" will be set to true. This key won't be present unless it is "true".</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 (eg 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 one to a line.</p>
 <p>Any of the filtering options can be applied to this command.</p>
 <p>There are several related list commands</p>
@@ -1330,9 +1379,9 @@ rclone copy --files-from-raw new_files /path/to/local remote:path</code></pre>
 <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 “–max-depth 1” 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 “-R” to make them recurse.</p>
-<p>Listing a non existent directory will produce an error except for remotes which can’t have empty directories (eg s3, swift, gcs, etc - the bucket based remotes).</p>
+<p>Note that <code>ls</code> and <code>lsl</code> recurse by default - use "--max-depth 1" 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 "-R" to make them recurse.</p>
+<p>Listing a non existent directory will produce an error except for remotes which can't have empty directories (eg s3, swift, gcs, etc - the bucket based remotes).</p>
 <pre><code>rclone lsjson remote:path [flags]</code></pre>
 <h2 id="options-48">Options</h2>
 <pre><code>      --dirs-only               Show only directories in the listing.
@@ -1353,9 +1402,9 @@ rclone copy --files-from-raw new_files /path/to/local remote:path</code></pre>
 <h1 id="rclone-mount">rclone mount</h1>
 <p>Mount the remote as file system on a mountpoint.</p>
 <h2 id="synopsis-49">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>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>You can either run mount in foreground mode or background (daemon) mode. Mount runs in foreground mode by default, use the –daemon flag to specify background mode mode. Background mode is only supported on Linux and OSX, you can only run mount in foreground mode on Windows.</p>
+<p>You can either run mount in foreground mode or background (daemon) mode. Mount runs in foreground mode by default, use the --daemon flag to specify background mode mode. Background mode is only supported on Linux and OSX, you can only run mount in foreground mode on Windows.</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>Or on Windows like this where <code>X:</code> is an unused drive letter or use a path to <strong>non-existent</strong> directory.</p>
@@ -1363,7 +1412,7 @@ rclone copy --files-from-raw new_files /path/to/local remote:path</code></pre>
 rclone mount remote:path/to/files C:\path\to\nonexistent\directory</code></pre>
 <p>When running in background mode the user will have to stop the mount manually (specified below).</p>
 <p>When the program ends while in foreground mode, either via Ctrl+C or receiving a SIGINT or SIGTERM signal, the mount is automatically stopped.</p>
-<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 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>Stopping the mount manually:</p>
 <pre><code># Linux
 fusermount -u /path/to/local/mount
@@ -1379,95 +1428,119 @@ umount /path/to/local/mount</code></pre>
 <p>By default, rclone will mount the remote as a normal drive. However, you can also mount it as a <strong>Network Drive</strong> (or <strong>Network Share</strong>, as mentioned in some places)</p>
 <p>Unlike other systems, Windows provides a different filesystem type for network drives. Windows and other programs treat the network drives and fixed/removable drives differently: In network drives, many I/O operations are optimized, as the high latency and low reliability (compared to a normal drive) of a network is expected.</p>
 <p>Although many people prefer network shares to be mounted as normal system drives, this might cause some issues, such as programs not working as expected or freezes and errors while operating with the mounted remote in Windows Explorer. If you experience any of those, consider mounting rclone remotes as network shares, as Windows expects normal drives to be fast and reliable, while cloud storage is far from that. See also <a href="#limitations">Limitations</a> section below for more info</p>
-<p>Add “–fuse-flag –VolumePrefix=” to your “mount” command, <strong>replacing “share” with any other name of your choice if you are mounting more than one remote</strong>. Otherwise, the mountpoints will conflict and your mounted filesystems will overlap.</p>
+<p>Add "--fuse-flag --VolumePrefix=" to your "mount" command, <strong>replacing "share" with any other name of your choice if you are mounting more than one remote</strong>. Otherwise, the mountpoints will conflict and your mounted filesystems will overlap.</p>
 <p><a href="https://en.wikipedia.org/wiki/Drive_mapping">Read more about drive mapping</a></p>
 <h2 id="limitations">Limitations</h2>
-<p>Without the use of “–vfs-cache-mode” 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 “–vfs-cache-mode writes” or “–vfs-cache-mode full”. See the <a href="#file-caching">File Caching</a> section for more info.</p>
+<p>Without the use of "--vfs-cache-mode" 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 "--vfs-cache-mode writes" or "--vfs-cache-mode full". See the <a href="#file-caching">File Caching</a> section for more info.</p>
 <p>The bucket based remotes (eg Swift, S3, Google Compute Storage, B2, Hubic) 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>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="#file-caching">file caching</a> for solutions to make mount more reliable.</p>
+<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="#file-caching">file caching</a> for solutions to make mount more reliable.</p>
 <h2 id="attribute-caching">Attribute caching</h2>
-<p>You can use the flag –attr-timeout to set the time the kernel caches the attributes (size, modification time etc) for directory entries.</p>
-<p>The default is “1s” which caches files just long enough to avoid too many callbacks to rclone from the kernel.</p>
+<p>You can use the flag --attr-timeout to set the time the kernel caches the attributes (size, modification time etc) for directory entries.</p>
+<p>The default is "1s" 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 “–attr-timeout”. 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 “–attr-timeout 1s” this is very unlikely but not impossible. The higher you set “–attr-timeout” 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 (‘10s’ or ‘1m’ 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>The kernel can cache the info about a file for the time given by "--attr-timeout". 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 "--attr-timeout 1s" this is very unlikely but not impossible. The higher you set "--attr-timeout" 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 ('10s' or '1m' 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>
 <h2 id="chunked-reading">chunked reading</h2>
-<p>–vfs-read-chunk-size will enable reading the source objects in parts. 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>When –vfs-read-chunk-size-limit is also specified and greater than –vfs-read-chunk-size, the chunk size for each open file will get doubled for each chunk read, until the specified value is reached. A value of -1 will disable the limit and the chunk size will grow indefinitely.</p>
-<p>With –vfs-read-chunk-size 100M and –vfs-read-chunk-size-limit 0 the following parts will be downloaded: 0-100M, 100M-200M, 200M-300M, 300M-400M and so on. When –vfs-read-chunk-size-limit 500M is specified, the result would be 0-100M, 100M-300M, 300M-700M, 700M-1200M, 1200M-1700M and so on.</p>
-<p>Chunked reading will only work with –vfs-cache-mode &lt; full, as the file will always be copied to the vfs cache before opening with –vfs-cache-mode full.</p>
-<h2 id="directory-cache">Directory Cache</h2>
-<p>Using the <code>--dir-cache-time</code> flag, you can set how long a directory should be considered up to date and not refreshed from the backend. Changes made locally in the mount may appear immediately or invalidate the cache. However, changes done on the remote will only be picked up once the cache expires if the backend configured does not support polling for changes. If the backend supports polling, changes will be picked up on within the polling interval.</p>
-<p>Alternatively, 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>
+<p>--vfs-read-chunk-size will enable reading the source objects in parts. 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>When --vfs-read-chunk-size-limit is also specified and greater than --vfs-read-chunk-size, the chunk size for each open file will get doubled for each chunk read, until the specified value is reached. A value of -1 will disable the limit and the chunk size will grow indefinitely.</p>
+<p>With --vfs-read-chunk-size 100M and --vfs-read-chunk-size-limit 0 the following parts will be downloaded: 0-100M, 100M-200M, 200M-300M, 300M-400M and so on. When --vfs-read-chunk-size-limit 500M is specified, the result would be 0-100M, 100M-300M, 300M-700M, 700M-1200M, 1200M-1700M and so on.</p>
+<p>Chunked reading will only work with --vfs-cache-mode &lt; full, as the file will always be copied to the vfs cache before opening with --vfs-cache-mode full.</p>
+<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 mount 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.</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="file-buffering">File Buffering</h2>
+<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 descriptor will try to keep the specified amount of data in memory at all times. The buffered data is bound to one file descriptor and won’t be shared between multiple open file descriptors of the same file.</p>
-<p>This flag is a upper limit for the used memory per file descriptor. 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. The maximum memory used by rclone for buffering can be up to <code>--buffer-size * open files</code>.</p>
-<h2 id="file-caching">File Caching</h2>
-<p>These flags control the VFS file caching options. The VFS layer is used by rclone mount to make a cloud storage system work more like a normal file system.</p>
-<p>You’ll need to enable VFS caching if you want, for example, to read and write simultaneously to a file. See below for more details.</p>
-<p>Note that the VFS cache works in addition to the cache backend and you may find that you need one or the other or both.</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 age of objects in the cache. (default 1h0m0s)
---vfs-cache-mode string              Cache mode off|minimal|writes|full (default &quot;off&quot;)
+--vfs-cache-max-size SizeSuffix      Max total size of objects in the cache. (default off)
 --vfs-cache-poll-interval duration   Interval to poll the cache for stale objects. (default 1m0s)
---vfs-cache-max-size int             Max total size of objects in the cache. (default off)</code></pre>
+--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 so if rclone is quit or dies with open files then these won’t get written back to the remote. However they will still be in the on disk cache.</p>
-<p>If using –vfs-cache-max-size note that the cache may exceed this size for two reasons. Firstly because it is only checked every –vfs-cache-poll-interval. Secondly because open files cannot be evicted from the cache.</p>
-<h3 id="vfs-cache-mode-off">–vfs-cache-mode off</h3>
-<p>In this mode the cache will read directly from the remote and write directly to the remote without caching anything on disk.</p>
+<p>Note that files are written back to the remote only when they are closed and if they haven't been accessed for --vfs-write-back second. 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 --vfs-cache-max-size note that the cache may exceed this size for two reasons. Firstly because it is only checked every --vfs-cache-poll-interval. Secondly because open files cannot be evicted from the cache.</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>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>
+<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 disks. This means that files opened for write will be a lot more compatible, but uses the minimal disk space.</p>
+<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>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>
+<li>If an upload fails it can't be retried</li>
 </ul>
-<h3 id="vfs-cache-mode-writes">–vfs-cache-mode writes</h3>
+<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 up to –low-level-retries times.</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 a file is opened for read it will be downloaded in its entirety first.</p>
-<p>This may be appropriate for your needs, or you may prefer to look at the cache backend which does a much more sophisticated job of caching, including caching directory hierarchies and chunks of files.</p>
-<p>In this mode, unlike the others, when a file is written to the disk, it will be kept on the disk after it is written to the remote. It will be purged on a schedule according to <code>--vfs-cache-max-age</code>.</p>
-<p>This mode should support all normal file system operations.</p>
-<p>If an upload or download fails it will be retried up to –low-level-retries times.</p>
-<h2 id="case-sensitivity">Case Sensitivity</h2>
+<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 dowloaded.</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 --vfs-cache-mode writes.</p>
+<p>When reading a file rclone will read --buffer-size plus --vfs-read-ahead bytes ahead. The --buffer-size is buffered in memory whereas the --vfs-read-ahead is buffered on disk.</p>
+<p>When using this mode it is recommended that --buffer-size is not set too big and --vfs-read-ahead is set large if required.</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.</p>
+<p>In particular S3 and Swift benefit hugely from the --no-modtime flag (or use --use-server-modtime 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       Mount read-only.</code></pre>
+<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 is advantageous because some cloud providers account for reads being all the data requested, not all the data delivered.</p>
+<p>Rclone will keep doubling the chunk size requested starting at --vfs-read-chunk-size with a maximum of --vfs-read-chunk-size-limit unless it is set to "off" in which case there will be no limit.</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 &quot;off&quot;)</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>
+<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>Windows is not like most other operating systems supported by rclone. 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>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 “–vfs-case-insensitive” mount flag controls how rclone handles these two cases. If its value is “false”, rclone passes file names to the mounted file system as is. If the flag is “true” (or appears without a value on command line), rclone may perform a “fixup” as explained below.</p>
+<p>The "--vfs-case-insensitive" mount flag controls how rclone handles these two cases. If its value is "false", rclone passes file names to the mounted file system as-is. If the flag is "true" (or appears without a value on 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 mounted file system. 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 an underlying mounted file system.</p>
-<p>Note that case sensitivity of the operating system running rclone (the target) may differ from case sensitivity of a file system mounted by rclone (the source). The flag controls whether “fixup” is performed to satisfy the target.</p>
-<p>If the flag is not provided on 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>Note that case sensitivity of the operating system running rclone (the target) may differ from case sensitivity of a file system mounted 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>
 <pre><code>rclone mount remote:path /path/to/mountpoint [flags]</code></pre>
 <h2 id="options-49">Options</h2>
 <pre><code>      --allow-non-empty                        Allow mounting over a non-empty directory (not Windows).
@@ -1499,9 +1572,11 @@ umount /path/to/local/mount</code></pre>
       --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-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 128M)
       --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-wait duration                 Time to wait for in-sequence read before seeking. (default 20ms)
+      --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 (not supported by all OSes).
       --write-back-cache                       Makes kernel buffer writes before sending them to rclone. Without this, writethrough caching is used.</code></pre>
@@ -1524,8 +1599,8 @@ umount /path/to/local/mount</code></pre>
 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 unchanged files, 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 –dry-run flag.</p>
+<p>This doesn't transfer unchanged files, 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-50">Options</h2>
@@ -1538,9 +1613,9 @@ if src is directory
 <h1 id="rclone-ncdu">rclone ncdu</h1>
 <p>Explore a remote with a text based user interface.</p>
 <h2 id="synopsis-51">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>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>Here are the keys - press ‘?’ to toggle the help on and off</p>
+<p>Here are the keys - press '?' to toggle the help on and off</p>
 <pre><code> ↑,↓ or k,j to Move
  →,l to enter
  ←,h to return
@@ -1554,7 +1629,7 @@ if src is directory
  ? to toggle help on and off
  q/ESC/c-C to quit</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.</p>
-<p>Note that it might take some time to delete big files/folders. The UI won’t respond in the meantime since the deletion is done synchronously.</p>
+<p>Note that it might take some time to delete big files/folders. The UI won't respond in the meantime since the deletion is done synchronously.</p>
 <pre><code>rclone ncdu remote:path [flags]</code></pre>
 <h2 id="options-51">Options</h2>
 <pre><code>  -h, --help   help for ncdu</code></pre>
@@ -1564,9 +1639,14 @@ if src is directory
 <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.conf</p>
+<p>Obscure password for use in the rclone config file</p>
 <h2 id="synopsis-52">Synopsis</h2>
-<p>Obscure password for use in the rclone.conf</p>
+<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. Example:</p>
+<p>echo "secretpassword" | rclone obscure -</p>
+<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-52">Options</h2>
 <pre><code>  -h, --help   help for obscure</code></pre>
@@ -1578,23 +1658,23 @@ if src is directory
 <h1 id="rclone-rc">rclone rc</h1>
 <p>Run a command against a running rclone.</p>
 <h2 id="synopsis-53">Synopsis</h2>
-<p>This runs a command against a running rclone. Use the –url 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 –user and –pass.</p>
-<p>Note that –rc-addr, –rc-user, –rc-pass will be read also for –url, –user, –pass.</p>
+<p>This runs a command against a running rclone. Use the --url 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 --user and --pass.</p>
+<p>Note that --rc-addr, --rc-user, --rc-pass will be read also for --url, --user, --pass.</p>
 <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 –json 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 -o/–opt option can be used to set a key “opt” with key, value options in the form “-o key=value” or “-o key”. 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>
+<p>The --json 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 -o/--opt option can be used to set a key "opt" with key, value options in the form "-o key=value" or "-o key". 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>
+<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 -a/–arg 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>
+<p>The -a/--arg 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>
+<p>Will place this in the "arg" value</p>
 <pre><code>[&quot;value&quot;, &quot;value2&quot;]</code></pre>
-<p>Use –loopback to connect to the rclone instance running “rclone rc”. This is very useful for testing commands without having to run an rclone rc server, eg:</p>
+<p>Use --loopback to connect to the rclone instance running "rclone rc". This is very useful for testing commands without having to run an rclone rc server, eg:</p>
 <pre><code>rclone rc --loopback operations/about fs=/</code></pre>
-<p>Use “rclone rc” to see a list of all possible commands.</p>
+<p>Use "rclone rc" to see a list of all possible commands.</p>
 <pre><code>rclone rc commands parameter [flags]</code></pre>
 <h2 id="options-53">Options</h2>
 <pre><code>  -a, --arg stringArray   Argument placed in the &quot;arg&quot; array.
@@ -1619,7 +1699,7 @@ if src is directory
 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>Note that the upload can also not be retried because the data is not kept around until the upload succeeds. If you need to transfer a lot of data, you’re better off caching locally and then <code>rclone move</code> it to the destination.</p>
+<p>Note that the upload can also not be retried because the data is not kept around until the upload succeeds. If you need to transfer a lot of data, you're better off caching locally and then <code>rclone move</code> it to the destination.</p>
 <pre><code>rclone rcat remote:path [flags]</code></pre>
 <h2 id="options-54">Options</h2>
 <pre><code>  -h, --help   help for rcat</code></pre>
@@ -1647,7 +1727,7 @@ ffmpeg - | rclone rcat remote:path/to/file</code></pre>
 <p>Remove empty directories under the path.</p>
 <h2 id="synopsis-56">Synopsis</h2>
 <p>This removes any empty directories (or directories that only contain empty directories) under the path that it finds, including the path if it has nothing in.</p>
-<p>If you supply the –leave-root flag, it will not remove the root directory.</p>
+<p>If you supply the --leave-root flag, it will not remove the root directory.</p>
 <p>This is useful for tidying up remotes that rclone has left a lot of empty directories in.</p>
 <pre><code>rclone rmdirs remote:path [flags]</code></pre>
 <h2 id="options-56">Options</h2>
@@ -1674,7 +1754,7 @@ ffmpeg - | rclone rcat remote:path/to/file</code></pre>
 <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_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_restic/">rclone serve restic</a> - Serve the remote for restic’s REST API.</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_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>
@@ -1684,73 +1764,97 @@ ffmpeg - | rclone rcat remote:path/to/file</code></pre>
 <p>rclone serve dlna is 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>
 <h2 id="server-options">Server options</h2>
-<p>Use –addr to specify which IP address and port the server should listen on, eg –addr 1.2.3.4:8000 or –addr :8080 to listen to all IPs.</p>
-<p>Use –name to choose the friendly server name, which is by default “rclone (hostname)”.</p>
-<p>Use –log-trace in conjunction with -vv to enable additional debug logging of all UPNP traffic.</p>
-<h2 id="directory-cache-1">Directory Cache</h2>
-<p>Using the <code>--dir-cache-time</code> flag, you can set how long a directory should be considered up to date and not refreshed from the backend. Changes made locally in the mount may appear immediately or invalidate the cache. However, changes done on the remote will only be picked up once the cache expires if the backend configured does not support polling for changes. If the backend supports polling, changes will be picked up on within the polling interval.</p>
-<p>Alternatively, 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>
+<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.</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-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 mount 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.</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="file-buffering-1">File Buffering</h2>
+<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 descriptor will try to keep the specified amount of data in memory at all times. The buffered data is bound to one file descriptor and won’t be shared between multiple open file descriptors of the same file.</p>
-<p>This flag is a upper limit for the used memory per file descriptor. 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. The maximum memory used by rclone for buffering can be up to <code>--buffer-size * open files</code>.</p>
-<h2 id="file-caching-1">File Caching</h2>
-<p>These flags control the VFS file caching options. The VFS layer is used by rclone mount to make a cloud storage system work more like a normal file system.</p>
-<p>You’ll need to enable VFS caching if you want, for example, to read and write simultaneously to a file. See below for more details.</p>
-<p>Note that the VFS cache works in addition to the cache backend and you may find that you need one or the other or both.</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 age of objects in the cache. (default 1h0m0s)
---vfs-cache-mode string              Cache mode off|minimal|writes|full (default &quot;off&quot;)
+--vfs-cache-max-size SizeSuffix      Max total size of objects in the cache. (default off)
 --vfs-cache-poll-interval duration   Interval to poll the cache for stale objects. (default 1m0s)
---vfs-cache-max-size int             Max total size of objects in the cache. (default off)</code></pre>
+--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 so if rclone is quit or dies with open files then these won’t get written back to the remote. However they will still be in the on disk cache.</p>
-<p>If using –vfs-cache-max-size note that the cache may exceed this size for two reasons. Firstly because it is only checked every –vfs-cache-poll-interval. Secondly because open files cannot be evicted from the cache.</p>
-<h3 id="vfs-cache-mode-off-1">–vfs-cache-mode off</h3>
-<p>In this mode the cache will read directly from the remote and write directly to the remote without caching anything on disk.</p>
+<p>Note that files are written back to the remote only when they are closed and if they haven't been accessed for --vfs-write-back second. 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 --vfs-cache-max-size note that the cache may exceed this size for two reasons. Firstly because it is only checked every --vfs-cache-poll-interval. Secondly because open files cannot be evicted from the cache.</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>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>
+<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 disks. This means that files opened for write will be a lot more compatible, but uses the minimal disk space.</p>
+<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>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>
+<li>If an upload fails it can't be retried</li>
 </ul>
-<h3 id="vfs-cache-mode-writes-1">–vfs-cache-mode writes</h3>
+<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 up to –low-level-retries times.</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 a file is opened for read it will be downloaded in its entirety first.</p>
-<p>This may be appropriate for your needs, or you may prefer to look at the cache backend which does a much more sophisticated job of caching, including caching directory hierarchies and chunks of files.</p>
-<p>In this mode, unlike the others, when a file is written to the disk, it will be kept on the disk after it is written to the remote. It will be purged on a schedule according to <code>--vfs-cache-max-age</code>.</p>
-<p>This mode should support all normal file system operations.</p>
-<p>If an upload or download fails it will be retried up to –low-level-retries times.</p>
-<h2 id="case-sensitivity-1">Case Sensitivity</h2>
+<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 dowloaded.</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 --vfs-cache-mode writes.</p>
+<p>When reading a file rclone will read --buffer-size plus --vfs-read-ahead bytes ahead. The --buffer-size is buffered in memory whereas the --vfs-read-ahead is buffered on disk.</p>
+<p>When using this mode it is recommended that --buffer-size is not set too big and --vfs-read-ahead is set large if required.</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.</p>
+<p>In particular S3 and Swift benefit hugely from the --no-modtime flag (or use --use-server-modtime 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       Mount read-only.</code></pre>
+<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 is advantageous because some cloud providers account for reads being all the data requested, not all the data delivered.</p>
+<p>Rclone will keep doubling the chunk size requested starting at --vfs-read-chunk-size with a maximum of --vfs-read-chunk-size-limit unless it is set to "off" in which case there will be no limit.</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 &quot;off&quot;)</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>
+<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>Windows is not like most other operating systems supported by rclone. 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>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 “–vfs-case-insensitive” mount flag controls how rclone handles these two cases. If its value is “false”, rclone passes file names to the mounted file system as is. If the flag is “true” (or appears without a value on command line), rclone may perform a “fixup” as explained below.</p>
+<p>The "--vfs-case-insensitive" mount flag controls how rclone handles these two cases. If its value is "false", rclone passes file names to the mounted file system as-is. If the flag is "true" (or appears without a value on 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 mounted file system. 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 an underlying mounted file system.</p>
-<p>Note that case sensitivity of the operating system running rclone (the target) may differ from case sensitivity of a file system mounted by rclone (the source). The flag controls whether “fixup” is performed to satisfy the target.</p>
-<p>If the flag is not provided on 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>Note that case sensitivity of the operating system running rclone (the target) may differ from case sensitivity of a file system mounted 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>
 <pre><code>rclone serve dlna remote:path [flags]</code></pre>
 <h2 id="options-58">Options</h2>
 <pre><code>      --addr string                            ip:port or :port to bind the DLNA http server to. (default &quot;:7879&quot;)
@@ -1773,9 +1877,11 @@ ffmpeg - | rclone rcat remote:path/to/file</code></pre>
       --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-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 128M)
       --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-wait duration                 Time to wait for in-sequence read before seeking. (default 20ms)
+      --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>See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
 <h2 id="see-also-58">SEE ALSO</h2>
@@ -1787,80 +1893,104 @@ ffmpeg - | rclone rcat remote:path/to/file</code></pre>
 <h2 id="synopsis-59">Synopsis</h2>
 <p>rclone serve ftp implements a basic ftp server to serve the 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-1">Server options</h2>
-<p>Use –addr to specify which IP address and port the server should listen on, eg –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>
+<p>Use --addr to specify which IP address and port the server should listen on, eg --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">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="directory-cache-2">Directory Cache</h2>
-<p>Using the <code>--dir-cache-time</code> flag, you can set how long a directory should be considered up to date and not refreshed from the backend. Changes made locally in the mount may appear immediately or invalidate the cache. However, changes done on the remote will only be picked up once the cache expires if the backend configured does not support polling for changes. If the backend supports polling, changes will be picked up on within the polling interval.</p>
-<p>Alternatively, 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>
+<p>You can set a single username and password with the --user and --pass flags.</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 mount 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.</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="file-buffering-2">File Buffering</h2>
+<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 descriptor will try to keep the specified amount of data in memory at all times. The buffered data is bound to one file descriptor and won’t be shared between multiple open file descriptors of the same file.</p>
-<p>This flag is a upper limit for the used memory per file descriptor. 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. The maximum memory used by rclone for buffering can be up to <code>--buffer-size * open files</code>.</p>
-<h2 id="file-caching-2">File Caching</h2>
-<p>These flags control the VFS file caching options. The VFS layer is used by rclone mount to make a cloud storage system work more like a normal file system.</p>
-<p>You’ll need to enable VFS caching if you want, for example, to read and write simultaneously to a file. See below for more details.</p>
-<p>Note that the VFS cache works in addition to the cache backend and you may find that you need one or the other or both.</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 age of objects in the cache. (default 1h0m0s)
---vfs-cache-mode string              Cache mode off|minimal|writes|full (default &quot;off&quot;)
+--vfs-cache-max-size SizeSuffix      Max total size of objects in the cache. (default off)
 --vfs-cache-poll-interval duration   Interval to poll the cache for stale objects. (default 1m0s)
---vfs-cache-max-size int             Max total size of objects in the cache. (default off)</code></pre>
+--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 so if rclone is quit or dies with open files then these won’t get written back to the remote. However they will still be in the on disk cache.</p>
-<p>If using –vfs-cache-max-size note that the cache may exceed this size for two reasons. Firstly because it is only checked every –vfs-cache-poll-interval. Secondly because open files cannot be evicted from the cache.</p>
-<h3 id="vfs-cache-mode-off-2">–vfs-cache-mode off</h3>
-<p>In this mode the cache will read directly from the remote and write directly to the remote without caching anything on disk.</p>
+<p>Note that files are written back to the remote only when they are closed and if they haven't been accessed for --vfs-write-back second. 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 --vfs-cache-max-size note that the cache may exceed this size for two reasons. Firstly because it is only checked every --vfs-cache-poll-interval. Secondly because open files cannot be evicted from the cache.</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>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>
+<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 disks. This means that files opened for write will be a lot more compatible, but uses the minimal disk space.</p>
+<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>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>
+<li>If an upload fails it can't be retried</li>
 </ul>
-<h3 id="vfs-cache-mode-writes-2">–vfs-cache-mode writes</h3>
+<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 up to –low-level-retries times.</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 a file is opened for read it will be downloaded in its entirety first.</p>
-<p>This may be appropriate for your needs, or you may prefer to look at the cache backend which does a much more sophisticated job of caching, including caching directory hierarchies and chunks of files.</p>
-<p>In this mode, unlike the others, when a file is written to the disk, it will be kept on the disk after it is written to the remote. It will be purged on a schedule according to <code>--vfs-cache-max-age</code>.</p>
-<p>This mode should support all normal file system operations.</p>
-<p>If an upload or download fails it will be retried up to –low-level-retries times.</p>
-<h2 id="case-sensitivity-2">Case Sensitivity</h2>
+<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 dowloaded.</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 --vfs-cache-mode writes.</p>
+<p>When reading a file rclone will read --buffer-size plus --vfs-read-ahead bytes ahead. The --buffer-size is buffered in memory whereas the --vfs-read-ahead is buffered on disk.</p>
+<p>When using this mode it is recommended that --buffer-size is not set too big and --vfs-read-ahead is set large if required.</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.</p>
+<p>In particular S3 and Swift benefit hugely from the --no-modtime flag (or use --use-server-modtime 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       Mount read-only.</code></pre>
+<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 is advantageous because some cloud providers account for reads being all the data requested, not all the data delivered.</p>
+<p>Rclone will keep doubling the chunk size requested starting at --vfs-read-chunk-size with a maximum of --vfs-read-chunk-size-limit unless it is set to "off" in which case there will be no limit.</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 &quot;off&quot;)</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>
+<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>Windows is not like most other operating systems supported by rclone. 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>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 “–vfs-case-insensitive” mount flag controls how rclone handles these two cases. If its value is “false”, rclone passes file names to the mounted file system as is. If the flag is “true” (or appears without a value on command line), rclone may perform a “fixup” as explained below.</p>
+<p>The "--vfs-case-insensitive" mount flag controls how rclone handles these two cases. If its value is "false", rclone passes file names to the mounted file system as-is. If the flag is "true" (or appears without a value on 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 mounted file system. 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 an underlying mounted file system.</p>
-<p>Note that case sensitivity of the operating system running rclone (the target) may differ from case sensitivity of a file system mounted by rclone (the source). The flag controls whether “fixup” is performed to satisfy the target.</p>
-<p>If the flag is not provided on 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>Note that case sensitivity of the operating system running rclone (the target) may differ from case sensitivity of a file system mounted 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>
 <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 protocl 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/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>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>
@@ -1883,8 +2013,8 @@ ffmpeg - | rclone rcat remote:path/to/file</code></pre>
     &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>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-59">Options</h2>
@@ -1911,9 +2041,11 @@ ffmpeg - | rclone rcat remote:path/to/file</code></pre>
       --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-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 128M)
       --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-wait duration                 Time to wait for in-sequence read before seeking. (default 20ms)
+      --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>See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
 <h2 id="see-also-59">SEE ALSO</h2>
@@ -1924,16 +2056,16 @@ ffmpeg - | rclone rcat remote:path/to/file</code></pre>
 <p>Serve the remote over HTTP.</p>
 <h2 id="synopsis-60">Synopsis</h2>
 <p>rclone serve http implements a basic web server to serve the 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 (eg –include, –exclude) to control what is served.</p>
+<p>You can use the filter flags (eg --include, --exclude) to control what is served.</p>
 <p>The server will log errors. Use -v to see access logs.</p>
-<p>–bwlimit will be respected for file transfers. Use –stats to control the stats printing.</p>
+<p>--bwlimit will be respected for file transfers. Use --stats to control the stats printing.</p>
 <h2 id="server-options-2">Server options</h2>
-<p>Use –addr to specify which IP address and port the server should listen on, eg –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>
-<p>–server-read-timeout and –server-write-timeout can be used to control the timeouts on the server. Note that this is the total time for a transfer.</p>
-<p>–max-header-bytes controls the maximum number of bytes the server will accept in the HTTP header.</p>
-<p>–baseurl controls the URL prefix that rclone serves from. By default rclone will serve from the root. If you used –baseurl “/rclone” 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 –baseurl, so –baseurl “rclone”, –baseurl “/rclone” and –baseurl “/rclone/” are all treated identically.</p>
-<p>–template 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>
+<p>Use --addr to specify which IP address and port the server should listen on, eg --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>
+<p>--server-read-timeout and --server-write-timeout can be used to control the timeouts on the server. Note that this is the total time for a transfer.</p>
+<p>--max-header-bytes controls the maximum number of bytes the server will accept in the HTTP header.</p>
+<p>--baseurl controls the URL prefix that rclone serves from. By default rclone will serve from the root. If you used --baseurl "/rclone" 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 --baseurl, so --baseurl "rclone", --baseurl "/rclone" and --baseurl "/rclone/" are all treated identically.</p>
+<p>--template 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%" />
@@ -1979,11 +2111,11 @@ ffmpeg - | rclone rcat remote:path/to/file</code></pre>
 <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;">-- .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;">-- .Text</td>
 <td style="text-align: left;">The Name of the directory.</td>
 </tr>
 <tr class="odd">
@@ -1991,104 +2123,128 @@ ffmpeg - | rclone rcat remote:path/to/file</code></pre>
 <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>
+<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>
+<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;">-- .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</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;">-- .ModTime</td>
 <td style="text-align: left;">The UTC timestamp of an entry.</td>
 </tr>
 </tbody>
 </table>
 <h3 id="authentication-1">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 –user and –pass flags.</p>
-<p>Use –htpasswd /path/to/htpasswd 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>You can either use an htpasswd file which can take lots of users, or set a single username and password with the --user and --pass flags.</p>
+<p>Use --htpasswd /path/to/htpasswd 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 –realm to set the authentication realm.</p>
+<p>Use --realm to set the authentication realm.</p>
 <h3 id="ssltls">SSL/TLS</h3>
-<p>By default this will serve over http. If you want you can serve over https. You will need to supply the –cert and –key flags. If you wish to do client side certificate validation then you will need to supply –client-ca also.</p>
-<p>–cert should be either a PEM encoded certificate or a concatenation of that with the CA certificate. –key should be the PEM encoded private key and –client-ca should be the PEM encoded client certificate authority certificate.</p>
-<h2 id="directory-cache-3">Directory Cache</h2>
-<p>Using the <code>--dir-cache-time</code> flag, you can set how long a directory should be considered up to date and not refreshed from the backend. Changes made locally in the mount may appear immediately or invalidate the cache. However, changes done on the remote will only be picked up once the cache expires if the backend configured does not support polling for changes. If the backend supports polling, changes will be picked up on within the polling interval.</p>
-<p>Alternatively, 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>
+<p>By default this will serve over http. If you want you can serve over https. You will need to supply the --cert and --key flags. If you wish to do client side certificate validation then you will need to supply --client-ca also.</p>
+<p>--cert should be either a PEM encoded certificate or a concatenation of that with the CA certificate. --key should be the PEM encoded private key and --client-ca should be the PEM encoded client certificate authority certificate.</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 mount 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.</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="file-buffering-3">File Buffering</h2>
+<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 descriptor will try to keep the specified amount of data in memory at all times. The buffered data is bound to one file descriptor and won’t be shared between multiple open file descriptors of the same file.</p>
-<p>This flag is a upper limit for the used memory per file descriptor. 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. The maximum memory used by rclone for buffering can be up to <code>--buffer-size * open files</code>.</p>
-<h2 id="file-caching-3">File Caching</h2>
-<p>These flags control the VFS file caching options. The VFS layer is used by rclone mount to make a cloud storage system work more like a normal file system.</p>
-<p>You’ll need to enable VFS caching if you want, for example, to read and write simultaneously to a file. See below for more details.</p>
-<p>Note that the VFS cache works in addition to the cache backend and you may find that you need one or the other or both.</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 age of objects in the cache. (default 1h0m0s)
---vfs-cache-mode string              Cache mode off|minimal|writes|full (default &quot;off&quot;)
+--vfs-cache-max-size SizeSuffix      Max total size of objects in the cache. (default off)
 --vfs-cache-poll-interval duration   Interval to poll the cache for stale objects. (default 1m0s)
---vfs-cache-max-size int             Max total size of objects in the cache. (default off)</code></pre>
+--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 so if rclone is quit or dies with open files then these won’t get written back to the remote. However they will still be in the on disk cache.</p>
-<p>If using –vfs-cache-max-size note that the cache may exceed this size for two reasons. Firstly because it is only checked every –vfs-cache-poll-interval. Secondly because open files cannot be evicted from the cache.</p>
-<h3 id="vfs-cache-mode-off-3">–vfs-cache-mode off</h3>
-<p>In this mode the cache will read directly from the remote and write directly to the remote without caching anything on disk.</p>
+<p>Note that files are written back to the remote only when they are closed and if they haven't been accessed for --vfs-write-back second. 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 --vfs-cache-max-size note that the cache may exceed this size for two reasons. Firstly because it is only checked every --vfs-cache-poll-interval. Secondly because open files cannot be evicted from the cache.</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>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>
+<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 disks. This means that files opened for write will be a lot more compatible, but uses the minimal disk space.</p>
+<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>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>
+<li>If an upload fails it can't be retried</li>
 </ul>
-<h3 id="vfs-cache-mode-writes-3">–vfs-cache-mode writes</h3>
+<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 up to –low-level-retries times.</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 a file is opened for read it will be downloaded in its entirety first.</p>
-<p>This may be appropriate for your needs, or you may prefer to look at the cache backend which does a much more sophisticated job of caching, including caching directory hierarchies and chunks of files.</p>
-<p>In this mode, unlike the others, when a file is written to the disk, it will be kept on the disk after it is written to the remote. It will be purged on a schedule according to <code>--vfs-cache-max-age</code>.</p>
-<p>This mode should support all normal file system operations.</p>
-<p>If an upload or download fails it will be retried up to –low-level-retries times.</p>
-<h2 id="case-sensitivity-3">Case Sensitivity</h2>
+<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 dowloaded.</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 --vfs-cache-mode writes.</p>
+<p>When reading a file rclone will read --buffer-size plus --vfs-read-ahead bytes ahead. The --buffer-size is buffered in memory whereas the --vfs-read-ahead is buffered on disk.</p>
+<p>When using this mode it is recommended that --buffer-size is not set too big and --vfs-read-ahead is set large if required.</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.</p>
+<p>In particular S3 and Swift benefit hugely from the --no-modtime flag (or use --use-server-modtime 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       Mount read-only.</code></pre>
+<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 is advantageous because some cloud providers account for reads being all the data requested, not all the data delivered.</p>
+<p>Rclone will keep doubling the chunk size requested starting at --vfs-read-chunk-size with a maximum of --vfs-read-chunk-size-limit unless it is set to "off" in which case there will be no limit.</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 &quot;off&quot;)</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>
+<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>Windows is not like most other operating systems supported by rclone. 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>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 “–vfs-case-insensitive” mount flag controls how rclone handles these two cases. If its value is “false”, rclone passes file names to the mounted file system as is. If the flag is “true” (or appears without a value on command line), rclone may perform a “fixup” as explained below.</p>
+<p>The "--vfs-case-insensitive" mount flag controls how rclone handles these two cases. If its value is "false", rclone passes file names to the mounted file system as-is. If the flag is "true" (or appears without a value on 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 mounted file system. 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 an underlying mounted file system.</p>
-<p>Note that case sensitivity of the operating system running rclone (the target) may differ from case sensitivity of a file system mounted by rclone (the source). The flag controls whether “fixup” is performed to satisfy the target.</p>
-<p>If the flag is not provided on 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>Note that case sensitivity of the operating system running rclone (the target) may differ from case sensitivity of a file system mounted 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>
 <pre><code>rclone serve http remote:path [flags]</code></pre>
 <h2 id="options-60">Options</h2>
 <pre><code>      --addr string                            IPaddress:Port or :Port to bind server to. (default &quot;localhost:8080&quot;)
@@ -2121,9 +2277,11 @@ htpasswd -B htpasswd anotherUser</code></pre>
       --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-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 128M)
       --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-wait duration                 Time to wait for in-sequence read before seeking. (default 20ms)
+      --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>See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
 <h2 id="see-also-60">SEE ALSO</h2>
@@ -2131,24 +2289,24 @@ htpasswd -B htpasswd anotherUser</code></pre>
 <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>
+<p>Serve the remote for restic's REST API.</p>
 <h2 id="synopsis-61">Synopsis</h2>
-<p>rclone serve restic implements 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>rclone serve restic implements 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>–bwlimit will be respected for file transfers. Use –stats to control the stats printing.</p>
+<p>--bwlimit will be respected for file transfers. Use --stats 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>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 “–addr” flag.</p>
+<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 "--addr" flag.</p>
 <p>You might wish to start this server on boot.</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 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
@@ -2171,14 +2329,14 @@ snapshot 45c8fdd8 saved</code></pre>
 $ export RESTIC_REPOSITORY=rest:http://localhost:8080/user2repo/
 # backup user2 stuff</code></pre>
 <h3 id="private-repositories">Private repositories</h3>
-<p>The “–private-repos” flag can be used to limit users to repositories starting with a path of <code>/&lt;username&gt;/</code>.</p>
+<p>The "--private-repos" flag can be used to limit users to repositories starting with a path of <code>/&lt;username&gt;/</code>.</p>
 <h2 id="server-options-3">Server options</h2>
-<p>Use –addr to specify which IP address and port the server should listen on, eg –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>
-<p>–server-read-timeout and –server-write-timeout can be used to control the timeouts on the server. Note that this is the total time for a transfer.</p>
-<p>–max-header-bytes controls the maximum number of bytes the server will accept in the HTTP header.</p>
-<p>–baseurl controls the URL prefix that rclone serves from. By default rclone will serve from the root. If you used –baseurl “/rclone” 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 –baseurl, so –baseurl “rclone”, –baseurl “/rclone” and –baseurl “/rclone/” are all treated identically.</p>
-<p>–template 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>
+<p>Use --addr to specify which IP address and port the server should listen on, eg --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>
+<p>--server-read-timeout and --server-write-timeout can be used to control the timeouts on the server. Note that this is the total time for a transfer.</p>
+<p>--max-header-bytes controls the maximum number of bytes the server will accept in the HTTP header.</p>
+<p>--baseurl controls the URL prefix that rclone serves from. By default rclone will serve from the root. If you used --baseurl "/rclone" 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 --baseurl, so --baseurl "rclone", --baseurl "/rclone" and --baseurl "/rclone/" are all treated identically.</p>
+<p>--template 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%" />
@@ -2224,11 +2382,11 @@ $ export RESTIC_REPOSITORY=rest:http://localhost:8080/user2repo/
 <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;">-- .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;">-- .Text</td>
 <td style="text-align: left;">The Name of the directory.</td>
 </tr>
 <tr class="odd">
@@ -2236,40 +2394,40 @@ $ export RESTIC_REPOSITORY=rest:http://localhost:8080/user2repo/
 <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>
+<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>
+<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;">-- .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</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;">-- .ModTime</td>
 <td style="text-align: left;">The UTC timestamp of an entry.</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 –user and –pass flags.</p>
-<p>Use –htpasswd /path/to/htpasswd 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>You can either use an htpasswd file which can take lots of users, or set a single username and password with the --user and --pass flags.</p>
+<p>Use --htpasswd /path/to/htpasswd 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 –realm to set the authentication realm.</p>
+<p>Use --realm to set the authentication realm.</p>
 <h3 id="ssltls-1">SSL/TLS</h3>
-<p>By default this will serve over http. If you want you can serve over https. You will need to supply the –cert and –key flags. If you wish to do client side certificate validation then you will need to supply –client-ca also.</p>
-<p>–cert should be either a PEM encoded certificate or a concatenation of that with the CA certificate. –key should be the PEM encoded private key and –client-ca should be the PEM encoded client certificate authority certificate.</p>
+<p>By default this will serve over http. If you want you can serve over https. You will need to supply the --cert and --key flags. If you wish to do client side certificate validation then you will need to supply --client-ca also.</p>
+<p>--cert should be either a PEM encoded certificate or a concatenation of that with the CA certificate. --key should be the PEM encoded private key and --client-ca should be the PEM encoded client certificate authority certificate.</p>
 <pre><code>rclone serve restic remote:path [flags]</code></pre>
 <h2 id="options-61">Options</h2>
 <pre><code>      --addr string                     IPaddress:Port or :Port to bind server to. (default &quot;localhost:8080&quot;)
@@ -2298,83 +2456,107 @@ htpasswd -B htpasswd anotherUser</code></pre>
 <p>Serve the remote over SFTP.</p>
 <h2 id="synopsis-62">Synopsis</h2>
 <p>rclone serve sftp implements an SFTP server to serve the remote over SFTP. This can be used with an SFTP client or you can make a remote of type sftp to use with it.</p>
-<p>You can use the filter flags (eg –include, –exclude) to control what is served.</p>
+<p>You can use the filter flags (eg --include, --exclude) to control what is served.</p>
 <p>The server will log errors. Use -v to see access logs.</p>
-<p>–bwlimit will be respected for file transfers. Use –stats to control the stats printing.</p>
-<p>You must provide some means of authentication, either with –user/–pass, an authorized keys file (specify location with –authorized-keys - the default is the same as ssh), an –auth-proxy, or set the –no-auth flag for no authentication when logging in.</p>
+<p>--bwlimit will be respected for file transfers. Use --stats to control the stats printing.</p>
+<p>You must provide some means of authentication, either with --user/--pass, an authorized keys file (specify location with --authorized-keys - the default is the same as ssh), an --auth-proxy, or set the --no-auth flag for no authentication when logging in.</p>
 <p>Note that this also implements a small number of shell commands so that it can provide md5sum/sha1sum/df information for the rclone sftp backend. This means that is can support SHA1SUMs, MD5SUMs and the about command when paired with the rclone sftp backend.</p>
-<p>If you don’t supply a –key then rclone will generate one and cache it for later use.</p>
-<p>By default the server binds to localhost:2022 - if you want it to be reachable externally then supply “–addr :2022” for example.</p>
-<p>Note that the default of “–vfs-cache-mode off” is fine for the rclone sftp backend, but it may not be with other SFTP clients.</p>
-<h2 id="directory-cache-4">Directory Cache</h2>
-<p>Using the <code>--dir-cache-time</code> flag, you can set how long a directory should be considered up to date and not refreshed from the backend. Changes made locally in the mount may appear immediately or invalidate the cache. However, changes done on the remote will only be picked up once the cache expires if the backend configured does not support polling for changes. If the backend supports polling, changes will be picked up on within the polling interval.</p>
-<p>Alternatively, 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>
+<p>If you don't supply a --key then rclone will generate one and cache it for later use.</p>
+<p>By default the server binds to localhost:2022 - if you want it to be reachable externally then supply "--addr :2022" for example.</p>
+<p>Note that the default of "--vfs-cache-mode off" is fine for the rclone sftp backend, but it may not be with other SFTP clients.</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 mount 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.</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="file-buffering-4">File Buffering</h2>
+<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 descriptor will try to keep the specified amount of data in memory at all times. The buffered data is bound to one file descriptor and won’t be shared between multiple open file descriptors of the same file.</p>
-<p>This flag is a upper limit for the used memory per file descriptor. 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. The maximum memory used by rclone for buffering can be up to <code>--buffer-size * open files</code>.</p>
-<h2 id="file-caching-4">File Caching</h2>
-<p>These flags control the VFS file caching options. The VFS layer is used by rclone mount to make a cloud storage system work more like a normal file system.</p>
-<p>You’ll need to enable VFS caching if you want, for example, to read and write simultaneously to a file. See below for more details.</p>
-<p>Note that the VFS cache works in addition to the cache backend and you may find that you need one or the other or both.</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 age of objects in the cache. (default 1h0m0s)
---vfs-cache-mode string              Cache mode off|minimal|writes|full (default &quot;off&quot;)
+--vfs-cache-max-size SizeSuffix      Max total size of objects in the cache. (default off)
 --vfs-cache-poll-interval duration   Interval to poll the cache for stale objects. (default 1m0s)
---vfs-cache-max-size int             Max total size of objects in the cache. (default off)</code></pre>
+--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 so if rclone is quit or dies with open files then these won’t get written back to the remote. However they will still be in the on disk cache.</p>
-<p>If using –vfs-cache-max-size note that the cache may exceed this size for two reasons. Firstly because it is only checked every –vfs-cache-poll-interval. Secondly because open files cannot be evicted from the cache.</p>
-<h3 id="vfs-cache-mode-off-4">–vfs-cache-mode off</h3>
-<p>In this mode the cache will read directly from the remote and write directly to the remote without caching anything on disk.</p>
+<p>Note that files are written back to the remote only when they are closed and if they haven't been accessed for --vfs-write-back second. 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 --vfs-cache-max-size note that the cache may exceed this size for two reasons. Firstly because it is only checked every --vfs-cache-poll-interval. Secondly because open files cannot be evicted from the cache.</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>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>
+<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 disks. This means that files opened for write will be a lot more compatible, but uses the minimal disk space.</p>
+<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>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>
+<li>If an upload fails it can't be retried</li>
 </ul>
-<h3 id="vfs-cache-mode-writes-4">–vfs-cache-mode writes</h3>
+<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 up to –low-level-retries times.</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 a file is opened for read it will be downloaded in its entirety first.</p>
-<p>This may be appropriate for your needs, or you may prefer to look at the cache backend which does a much more sophisticated job of caching, including caching directory hierarchies and chunks of files.</p>
-<p>In this mode, unlike the others, when a file is written to the disk, it will be kept on the disk after it is written to the remote. It will be purged on a schedule according to <code>--vfs-cache-max-age</code>.</p>
-<p>This mode should support all normal file system operations.</p>
-<p>If an upload or download fails it will be retried up to –low-level-retries times.</p>
-<h2 id="case-sensitivity-4">Case Sensitivity</h2>
+<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 dowloaded.</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 --vfs-cache-mode writes.</p>
+<p>When reading a file rclone will read --buffer-size plus --vfs-read-ahead bytes ahead. The --buffer-size is buffered in memory whereas the --vfs-read-ahead is buffered on disk.</p>
+<p>When using this mode it is recommended that --buffer-size is not set too big and --vfs-read-ahead is set large if required.</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.</p>
+<p>In particular S3 and Swift benefit hugely from the --no-modtime flag (or use --use-server-modtime 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       Mount read-only.</code></pre>
+<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 is advantageous because some cloud providers account for reads being all the data requested, not all the data delivered.</p>
+<p>Rclone will keep doubling the chunk size requested starting at --vfs-read-chunk-size with a maximum of --vfs-read-chunk-size-limit unless it is set to "off" in which case there will be no limit.</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 &quot;off&quot;)</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>
+<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>Windows is not like most other operating systems supported by rclone. 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>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 “–vfs-case-insensitive” mount flag controls how rclone handles these two cases. If its value is “false”, rclone passes file names to the mounted file system as is. If the flag is “true” (or appears without a value on command line), rclone may perform a “fixup” as explained below.</p>
+<p>The "--vfs-case-insensitive" mount flag controls how rclone handles these two cases. If its value is "false", rclone passes file names to the mounted file system as-is. If the flag is "true" (or appears without a value on 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 mounted file system. 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 an underlying mounted file system.</p>
-<p>Note that case sensitivity of the operating system running rclone (the target) may differ from case sensitivity of a file system mounted by rclone (the source). The flag controls whether “fixup” is performed to satisfy the target.</p>
-<p>If the flag is not provided on 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>Note that case sensitivity of the operating system running rclone (the target) may differ from case sensitivity of a file system mounted 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>
 <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 protocl 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/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>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>
@@ -2397,8 +2579,8 @@ htpasswd -B htpasswd anotherUser</code></pre>
     &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>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-62">Options</h2>
@@ -2426,9 +2608,11 @@ htpasswd -B htpasswd anotherUser</code></pre>
       --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-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 128M)
       --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-wait duration                 Time to wait for in-sequence read before seeking. (default 20ms)
+      --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>See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
 <h2 id="see-also-62">SEE ALSO</h2>
@@ -2440,17 +2624,17 @@ htpasswd -B htpasswd anotherUser</code></pre>
 <h2 id="synopsis-63">Synopsis</h2>
 <p>rclone serve webdav implements a basic webdav server to serve the 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>
+<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”.</p>
-<p>Use “rclone hashsum” to see the full list.</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".</p>
+<p>Use "rclone hashsum" to see the full list.</p>
 <h2 id="server-options-4">Server options</h2>
-<p>Use –addr to specify which IP address and port the server should listen on, eg –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>
-<p>–server-read-timeout and –server-write-timeout can be used to control the timeouts on the server. Note that this is the total time for a transfer.</p>
-<p>–max-header-bytes controls the maximum number of bytes the server will accept in the HTTP header.</p>
-<p>–baseurl controls the URL prefix that rclone serves from. By default rclone will serve from the root. If you used –baseurl “/rclone” 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 –baseurl, so –baseurl “rclone”, –baseurl “/rclone” and –baseurl “/rclone/” are all treated identically.</p>
-<p>–template 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>
+<p>Use --addr to specify which IP address and port the server should listen on, eg --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>
+<p>--server-read-timeout and --server-write-timeout can be used to control the timeouts on the server. Note that this is the total time for a transfer.</p>
+<p>--max-header-bytes controls the maximum number of bytes the server will accept in the HTTP header.</p>
+<p>--baseurl controls the URL prefix that rclone serves from. By default rclone will serve from the root. If you used --baseurl "/rclone" 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 --baseurl, so --baseurl "rclone", --baseurl "/rclone" and --baseurl "/rclone/" are all treated identically.</p>
+<p>--template 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%" />
@@ -2496,11 +2680,11 @@ htpasswd -B htpasswd anotherUser</code></pre>
 <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;">-- .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;">-- .Text</td>
 <td style="text-align: left;">The Name of the directory.</td>
 </tr>
 <tr class="odd">
@@ -2508,109 +2692,133 @@ htpasswd -B htpasswd anotherUser</code></pre>
 <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>
+<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>
+<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;">-- .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</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;">-- .ModTime</td>
 <td style="text-align: left;">The UTC timestamp of an entry.</td>
 </tr>
 </tbody>
 </table>
 <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 –user and –pass flags.</p>
-<p>Use –htpasswd /path/to/htpasswd 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>You can either use an htpasswd file which can take lots of users, or set a single username and password with the --user and --pass flags.</p>
+<p>Use --htpasswd /path/to/htpasswd 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 –realm to set the authentication realm.</p>
+<p>Use --realm to set the authentication realm.</p>
 <h3 id="ssltls-2">SSL/TLS</h3>
-<p>By default this will serve over http. If you want you can serve over https. You will need to supply the –cert and –key flags. If you wish to do client side certificate validation then you will need to supply –client-ca also.</p>
-<p>–cert should be either a PEM encoded certificate or a concatenation of that with the CA certificate. –key should be the PEM encoded private key and –client-ca should be the PEM encoded client certificate authority certificate.</p>
-<h2 id="directory-cache-5">Directory Cache</h2>
-<p>Using the <code>--dir-cache-time</code> flag, you can set how long a directory should be considered up to date and not refreshed from the backend. Changes made locally in the mount may appear immediately or invalidate the cache. However, changes done on the remote will only be picked up once the cache expires if the backend configured does not support polling for changes. If the backend supports polling, changes will be picked up on within the polling interval.</p>
-<p>Alternatively, 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>
+<p>By default this will serve over http. If you want you can serve over https. You will need to supply the --cert and --key flags. If you wish to do client side certificate validation then you will need to supply --client-ca also.</p>
+<p>--cert should be either a PEM encoded certificate or a concatenation of that with the CA certificate. --key should be the PEM encoded private key and --client-ca should be the PEM encoded client certificate authority certificate.</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 mount 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.</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="file-buffering-5">File Buffering</h2>
+<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 descriptor will try to keep the specified amount of data in memory at all times. The buffered data is bound to one file descriptor and won’t be shared between multiple open file descriptors of the same file.</p>
-<p>This flag is a upper limit for the used memory per file descriptor. 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. The maximum memory used by rclone for buffering can be up to <code>--buffer-size * open files</code>.</p>
-<h2 id="file-caching-5">File Caching</h2>
-<p>These flags control the VFS file caching options. The VFS layer is used by rclone mount to make a cloud storage system work more like a normal file system.</p>
-<p>You’ll need to enable VFS caching if you want, for example, to read and write simultaneously to a file. See below for more details.</p>
-<p>Note that the VFS cache works in addition to the cache backend and you may find that you need one or the other or both.</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 age of objects in the cache. (default 1h0m0s)
---vfs-cache-mode string              Cache mode off|minimal|writes|full (default &quot;off&quot;)
+--vfs-cache-max-size SizeSuffix      Max total size of objects in the cache. (default off)
 --vfs-cache-poll-interval duration   Interval to poll the cache for stale objects. (default 1m0s)
---vfs-cache-max-size int             Max total size of objects in the cache. (default off)</code></pre>
+--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 so if rclone is quit or dies with open files then these won’t get written back to the remote. However they will still be in the on disk cache.</p>
-<p>If using –vfs-cache-max-size note that the cache may exceed this size for two reasons. Firstly because it is only checked every –vfs-cache-poll-interval. Secondly because open files cannot be evicted from the cache.</p>
-<h3 id="vfs-cache-mode-off-5">–vfs-cache-mode off</h3>
-<p>In this mode the cache will read directly from the remote and write directly to the remote without caching anything on disk.</p>
+<p>Note that files are written back to the remote only when they are closed and if they haven't been accessed for --vfs-write-back second. 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 --vfs-cache-max-size note that the cache may exceed this size for two reasons. Firstly because it is only checked every --vfs-cache-poll-interval. Secondly because open files cannot be evicted from the cache.</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>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>
+<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 disks. This means that files opened for write will be a lot more compatible, but uses the minimal disk space.</p>
+<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>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>
+<li>If an upload fails it can't be retried</li>
 </ul>
-<h3 id="vfs-cache-mode-writes-5">–vfs-cache-mode writes</h3>
+<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 up to –low-level-retries times.</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 a file is opened for read it will be downloaded in its entirety first.</p>
-<p>This may be appropriate for your needs, or you may prefer to look at the cache backend which does a much more sophisticated job of caching, including caching directory hierarchies and chunks of files.</p>
-<p>In this mode, unlike the others, when a file is written to the disk, it will be kept on the disk after it is written to the remote. It will be purged on a schedule according to <code>--vfs-cache-max-age</code>.</p>
-<p>This mode should support all normal file system operations.</p>
-<p>If an upload or download fails it will be retried up to –low-level-retries times.</p>
-<h2 id="case-sensitivity-5">Case Sensitivity</h2>
+<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 dowloaded.</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 --vfs-cache-mode writes.</p>
+<p>When reading a file rclone will read --buffer-size plus --vfs-read-ahead bytes ahead. The --buffer-size is buffered in memory whereas the --vfs-read-ahead is buffered on disk.</p>
+<p>When using this mode it is recommended that --buffer-size is not set too big and --vfs-read-ahead is set large if required.</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.</p>
+<p>In particular S3 and Swift benefit hugely from the --no-modtime flag (or use --use-server-modtime 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       Mount read-only.</code></pre>
+<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 is advantageous because some cloud providers account for reads being all the data requested, not all the data delivered.</p>
+<p>Rclone will keep doubling the chunk size requested starting at --vfs-read-chunk-size with a maximum of --vfs-read-chunk-size-limit unless it is set to "off" in which case there will be no limit.</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 &quot;off&quot;)</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>
+<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>Windows is not like most other operating systems supported by rclone. 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>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 “–vfs-case-insensitive” mount flag controls how rclone handles these two cases. If its value is “false”, rclone passes file names to the mounted file system as is. If the flag is “true” (or appears without a value on command line), rclone may perform a “fixup” as explained below.</p>
+<p>The "--vfs-case-insensitive" mount flag controls how rclone handles these two cases. If its value is "false", rclone passes file names to the mounted file system as-is. If the flag is "true" (or appears without a value on 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 mounted file system. 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 an underlying mounted file system.</p>
-<p>Note that case sensitivity of the operating system running rclone (the target) may differ from case sensitivity of a file system mounted by rclone (the source). The flag controls whether “fixup” is performed to satisfy the target.</p>
-<p>If the flag is not provided on 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>Note that case sensitivity of the operating system running rclone (the target) may differ from case sensitivity of a file system mounted 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>
 <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 protocl 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/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>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>
@@ -2633,8 +2841,8 @@ htpasswd -B htpasswd anotherUser</code></pre>
     &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>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-63">Options</h2>
@@ -2671,9 +2879,11 @@ htpasswd -B htpasswd anotherUser</code></pre>
       --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-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 128M)
       --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-wait duration                 Time to wait for in-sequence read before seeking. (default 20ms)
+      --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>See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
 <h2 id="see-also-63">SEE ALSO</h2>
@@ -2703,13 +2913,14 @@ htpasswd -B htpasswd anotherUser</code></pre>
 <p>Create new file or change file modification time.</p>
 <h2 id="synopsis-65">Synopsis</h2>
 <p>Set the modification time on object(s) as specified by remote:path to have the current time.</p>
-<p>If remote:path does not exist then a zero sized object will be created unless the –no-create flag is provided.</p>
-<p>If –timestamp is used then it will set the modification time to that time instead of the current time. Times may be specified as one of:</p>
+<p>If remote:path does not exist then a zero sized object will be created unless the --no-create flag is provided.</p>
+<p>If --timestamp is used then it will set the modification time to that time instead of the current time. Times may be specified as one of:</p>
 <ul>
-<li>‘YYMMDD’ - eg. 17.10.30</li>
-<li>‘YYYY-MM-DDTHH:MM:SS’ - eg. 2006-01-02T15:04:05</li>
+<li>'YYMMDD' - eg. 17.10.30</li>
+<li>'YYYY-MM-DDTHH:MM:SS' - eg. 2006-01-02T15:04:05</li>
+<li>'YYYY-MM-DDTHH:MM:SS.SSS' - eg. 2006-01-02T15:04:05.123456789</li>
 </ul>
-<p>Note that –timestamp is in UTC if you want local time then add the –localtime flag.</p>
+<p>Note that --timestamp is in UTC if you want local time then add the --localtime flag.</p>
 <pre><code>rclone touch remote:path [flags]</code></pre>
 <h2 id="options-65">Options</h2>
 <pre><code>  -h, --help               help for touch
@@ -2736,8 +2947,8 @@ htpasswd -B htpasswd anotherUser</code></pre>
     └── file5
 
 1 directories, 5 files</code></pre>
-<p>You can use any of the filtering options with the tree command (eg –include and –exclude). You can also use –fast-list.</p>
-<p>The tree command has many options for controlling the listing which are compatible with the tree command. Note that not all of them have short options as they conflict with rclone’s short options.</p>
+<p>You can use any of the filtering options with the tree command (eg --include and --exclude). You can also use --fast-list.</p>
+<p>The tree command has many options for controlling the listing which are compatible with the tree command. Note that not all of them have short options as they conflict with rclone's short options.</p>
 <pre><code>rclone tree remote:path [flags]</code></pre>
 <h2 id="options-66">Options</h2>
 <pre><code>  -a, --all             All files are listed (list . files too).
@@ -2749,7 +2960,7 @@ htpasswd -B htpasswd anotherUser</code></pre>
       --human           Print the size in a more human readable way.
       --level int       Descend only level directories deep.
   -D, --modtime         Print the date of last modification.
-  -i, --noindent        Don&#39;t print indentation lines.
+      --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.
@@ -2767,7 +2978,7 @@ htpasswd -B htpasswd anotherUser</code></pre>
 <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>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>
@@ -2781,11 +2992,11 @@ htpasswd -B htpasswd anotherUser</code></pre>
 <h3 id="pathtodir">/path/to/dir</h3>
 <p>This refers to the local file system.</p>
 <p>On Windows only <code>\</code> may be used instead of <code>/</code> in local paths <strong>only</strong>, non local paths must use <code>/</code>.</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>
+<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>
+<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>
@@ -2797,6 +3008,11 @@ htpasswd -B htpasswd anotherUser</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="valid-remote-names">Valid remote names</h3>
+<ul>
+<li>Remote names may only contain 0-9, A-Z ,a-z ,_ , - and space.</li>
+<li>Remote names may not start with -.</li>
+</ul>
 <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>
@@ -2805,51 +3021,51 @@ htpasswd -B htpasswd anotherUser</code></pre>
 <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>, eg</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>
+<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">Windows</h3>
 <p>If your names have spaces in you need to put them in <code>"</code>, eg</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), eg</p>
+<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), eg</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 ./sync:me remote:path</code></pre>
+<pre><code>rclone sync -i ./sync:me remote:path</code></pre>
 <p>or</p>
-<pre><code>rclone sync /full/path/to/sync:me remote:path</code></pre>
+<pre><code>rclone sync -i /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>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>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, eg</p>
-<pre><code>rclone sync remote:current-backup remote:previous-backup
-rclone sync /path/to/files remote:current-backup</code></pre>
+<pre><code>rclone sync -i remote:current-backup remote:previous-backup
+rclone sync -i /path/to/files remote:current-backup</code></pre>
 <h2 id="options-67">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>
-<p>Options which use TIME use the go time parser. 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”. Valid time units are “ns”, “us” (or “µs”), “ms”, “s”, “m”, “h”.</p>
+<p>Options which use TIME use the go time parser. 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". Valid time units are "ns", "us" (or "µs"), "ms", "s", "m", "h".</p>
 <p>Options which use SIZE use kByte by default. However, a suffix of <code>b</code> for bytes, <code>k</code> for kBytes, <code>M</code> for MBytes, <code>G</code> for GBytes, <code>T</code> for TBytes and <code>P</code> for PBytes may be used. These are the binary units, eg 1, 2**10, 2**20, 2**30 respectively.</p>
-<h3 id="backup-dirdir">–backup-dir=DIR</h3>
+<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.</p>
 <p>For example</p>
-<pre><code>rclone sync /path/to/local remote:current --backup-dir remote:old</code></pre>
+<pre><code>rclone sync -i /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>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>
-<h3 id="bwlimitbandwidth_spec">–bwlimit=BANDWIDTH_SPEC</h3>
+<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>
+<h3 id="bwlimitbandwidth_spec">--bwlimit=BANDWIDTH_SPEC</h3>
 <p>This option controls the bandwidth limit. Limits can be specified in two ways: As a single limit, or as a timetable.</p>
 <p>Single limits last for the duration of the session. To use a single limit, specify the desired bandwidth in kBytes/s, or use a suffix b|k|M|G. The default is <code>0</code> which means to not limit bandwidth.</p>
 <p>For example, to limit bandwidth usage to 10 MBytes/s use <code>--bwlimit 10M</code></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. It could be written as whole world or only using 3 first characters. <code>HH:MM</code> is an hour from 00:00 to 23:59.</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. It could be written as whole world or only using 3 first characters. <code>HH:MM</code> is an hour from 00:00 to 23:59.</p>
 <p>An example of a typical timetable to avoid link saturation during daytime working hours could be:</p>
 <p><code>--bwlimit "08:00,512 12:00,10M 13:00,512 18:00,30M 23:00,off"</code></p>
 <p>In this example, the transfer bandwidth will be every day set to 512kBytes/sec at 8am. At noon, it will raise to 10Mbytes/s, and drop back to 512kBytes/sec at 1pm. At 6pm, the bandwidth limit will be set to 30MBytes/s, and at 11pm it will be completely disabled (full speed). Anything between 11pm and 8am will remain unlimited.</p>
@@ -2860,50 +3076,56 @@ rclone sync /path/to/files remote:current-backup</code></pre>
 <p><code>--bwlimit "Mon-00:00,512 12:00,1M Sun-20:00,off"</code></p>
 <p>Is equal 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 limits only apply to the data transfer. They don’t apply to the bandwidth of the directory listings etc.</p>
-<p>Note that the units are Bytes/s, not Bits/s. Typically connections are measured in Bits/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.625MByte/s so you would use a <code>--bwlimit 0.625M</code> parameter for rclone.</p>
+<p>Bandwidth limits only apply to the data transfer. They don't apply to the bandwidth of the directory listings etc.</p>
+<p>Note that the units are Bytes/s, not Bits/s. Typically connections are measured in Bits/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.625MByte/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="buffer-sizesize">–buffer-size=SIZE</h3>
+<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 1MByte/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="check-first">–check-first</h3>
+<p>Note that the memory allocation of the buffers is influenced by the <a href="#use-mmap">--use-mmap</a> flag.</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>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>
+<h3 id="checkersn">--checkers=N</h3>
 <p>The number of checkers to run in parallel. Checkers do the equality checking of files during a sync. For some storage systems (eg 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.</p>
-<h3 id="c-checksum">-c, –checksum</h3>
+<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 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, eg 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="compare-destdir">–compare-dest=DIR</h3>
+<p>When using this flag, rclone won't update mtimes of remote files if they are incorrect as it would normally.</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>
+<h3 id="configconfig_file">--config=CONFIG_FILE</h3>
 <p>Specify the location of the rclone config file.</p>
 <p>Normally the config file is in your home directory as a file called <code>.config/rclone/rclone.conf</code> (or <code>.rclone.conf</code> if created with an older version). If <code>$XDG_CONFIG_HOME</code> is set it will be at <code>$XDG_CONFIG_HOME/rclone/rclone.conf</code>.</p>
 <p>If there is a file <code>rclone.conf</code> in the same directory as the rclone executable it will be preferred. This file must be created manually for Rclone to use it, it will never be created automatically.</p>
 <p>If you run <code>rclone config file</code> you will see where the default location is for you.</p>
 <p>Use this flag to override the config location, eg <code>rclone --config=".myconfig" .config</code>.</p>
-<h3 id="contimeouttime">–contimeout=TIME</h3>
+<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>
+<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>
+<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>. See the dedupe command for more information as to what these options mean.</p>
-<h3 id="disable-featurefeature">–disable FEATURE,FEATURE,…</h3>
+<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>
@@ -2911,111 +3133,131 @@ rclone sync /path/to/files remote:current-backup</code></pre>
 <pre><code>--disable help</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>This flag can be useful for debugging and in exceptional circumstances (eg Google Drive limiting the total volume of Server Side Copies to 100GB/day).</p>
-<h3 id="n-dry-run">-n, –dry-run</h3>
+<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>
+<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>
+<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="header">–header</h3>
+<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>
+<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 s3:test/src ~/dst --header-download &quot;X-Amz-Meta-Test: Foo&quot; --header-download &quot;X-Amz-Meta-Test2: Bar&quot;</code></pre>
+<pre><code>rclone sync -i 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>
+<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 ~/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>
+<pre><code>rclone sync -i ~/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="ignore-case-sync">–ignore-case-sync</h3>
+<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>
+<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>
-<h3 id="ignore-size">–ignore-size</h3>
+<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>
+<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>
+<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>
+<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>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>
-<h2 id="leave-root">–leave-root</h2>
-<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>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. <code>date</code>, <code>time</code>, <code>microseconds</code>, <code>longfile</code>, <code>shortfile</code>, <code>UTC</code>. The default is “<code>date</code>,<code>time</code>”.</p>
-<h3 id="log-level-level">–log-level LEVEL</h3>
+<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 -i /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>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. <code>date</code>, <code>time</code>, <code>microseconds</code>, <code>longfile</code>, <code>shortfile</code>, <code>UTC</code>. The default 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>
+<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>
+<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>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>
+<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 kB 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>
+<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-depthn">–max-depth=N</h3>
+<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>
+<h3 id="max-durationtime">--max-duration=TIME</h3>
 <p>Rclone will stop scheduling new transfers when it has run for the duration specified.</p>
 <p>Defaults to off.</p>
 <p>When the limit is reached any existing transfers will complete.</p>
-<p>Rclone won’t exit with an error if the transfer limit is reached.</p>
-<h3 id="max-transfersize">–max-transfer=SIZE</h3>
+<p>Rclone won't exit with an error if the transfer 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.</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>
+<h3 id="cutoff-modehardsoftcautious">--cutoff-mode=hard|soft|cautious</h3>
 <p>This modifies the behavior of <code>--max-transfer</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.</p>
-<h3 id="modify-windowtime">–modify-window=TIME</h3>
+<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-cutoffsize">–multi-thread-cutoff=SIZE</h3>
+<h3 id="multi-thread-cutoffsize">--multi-thread-cutoff=SIZE</h3>
 <p>When downloading files to the local backend above this size, rclone will use multiple threads to download the file (default 250M).</p>
-<p>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>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 download 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 downloads 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 for a local destination but will work with any 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 downloads 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 downloads) or disable multi-thread downloads with <code>--multi-thread-streams 0</code></p>
-<h3 id="multi-thread-streamsn">–multi-thread-streams=N</h3>
+<h3 id="multi-thread-streamsn">--multi-thread-streams=N</h3>
 <p>When using multi thread downloads (see above <code>--multi-thread-cutoff</code>) this sets the maximum number of streams to use. Set to <code>0</code> to disable multi thread downloads (Default 4).</p>
 <p>Exactly how many streams rclone uses for the download depends on the size of the file. To calculate the number of download streams Rclone divides the size of the file by the <code>--multi-thread-cutoff</code> and rounds up, up to the maximum set with <code>--multi-thread-streams</code>.</p>
 <p>So if <code>--multi-thread-cutoff 250MB</code> and <code>--multi-thread-streams 4</code> are in effect (the defaults):</p>
@@ -3025,33 +3267,33 @@ rclone sync /path/to/files remote:current-backup</code></pre>
 <li>500MB..750MB files will be downloaded with 3 streams</li>
 <li>750MB+ files will be downloaded with 4 streams</li>
 </ul>
-<h3 id="no-check-dest">–no-check-dest</h3>
+<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 (eg Google Drive)</li>
-<li><code>--retries 1</code> is recommended otherwise you’ll transfer everything again on a retry</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>
+<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>
+<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>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>
+<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 é 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>
+<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 (eg the Google Drive client).</p>
-<h3 id="order-by-string">–order-by string</h3>
+<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>
@@ -3078,10 +3320,10 @@ rclone sync /path/to/files remote:current-backup</code></pre>
 <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>
+<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>
-<h3 id="password-command-spaceseplist">–password-command SpaceSepList</h3>
+<h3 id="password-command-spaceseplist">--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.</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>
@@ -3090,88 +3332,109 @@ rclone sync /path/to/files remote:current-backup</code></pre>
 --password-command echo &quot;hello with &quot;&quot;quotes&quot;&quot; and space&quot;</code></pre>
 <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>
+<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>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="q-quiet">-q, –quiet</h3>
-<p>This flag will limit rclone’s output to error messages only.</p>
-<h3 id="retries-int">–retries int</h3>
+<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 (eg <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 (eg 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>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>
+<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="size-only">–size-only</h3>
+<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>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>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>
+<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>
+<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>
+<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>
+<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>
+<h3 id="stats-unitbitsbytes">--stats-unit=bits|bytes</h3>
 <p>By default, data transfer rates will be printed in bytes/second.</p>
 <p>This option allows the data rate to be printed in bits/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 bits/s and not 1,000,000 bits/s.</p>
 <p>The default is <code>bytes</code>.</p>
-<h3 id="suffixsuffix">–suffix=SUFFIX</h3>
+<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 sync /path/to/local/file remote:current --suffix .bak</code></pre>
+<pre><code>rclone sync -i /path/to/local/file remote:current --suffix .bak</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 have .bak added.</p>
-<h3 id="suffix-keep-extension">–suffix-keep-extension</h3>
+<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>
-<h3 id="syslog">–syslog</h3>
+<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>
+<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>
+<h3 id="syslog-facility-string">--syslog-facility string</h3>
 <p>If using <code>--syslog</code> this sets the syslog facility (eg <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="tpslimit-float">–tpslimit float</h3>
+<h3 id="tpslimit-float">--tpslimit float</h3>
 <p>Limit HTTP transactions per second to this. Default is 0 which is used to mean unlimited transactions per second.</p>
 <p>For example to limit rclone to 10 HTTP 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 (eg 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>See also <code>--tpslimit-burst</code>.</p>
-<h3 id="tpslimit-burst-int">–tpslimit-burst int</h3>
+<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>
+<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>If you use this flag, and the remote supports server side copy or server side move, and the source and destination have a compatible hash, then this will track renames during <code>sync</code> operations and perform renaming server-side.</p>
 <p>Files will be matched by size and hash - if both match then a rename will be considered.</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. Note: Encrypted destinations are not supported by <code>--track-renames</code>.</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-hashmodtime">–track-renames-strategy (hash,modtime)</h3>
-<p>This option changes the matching criteria for <code>--track-renames</code> to match by any combination of modtime, hash, size. Matching by size is always enabled no matter what option is selected here. This also means that it enables <code>--track-renames</code> support for encrypted destinations. If nothing is specified, the default option is matching by hashes.</p>
-<h3 id="delete-beforeduringafter">–delete-(before,during,after)</h3>
+<h3 id="track-renames-strategy-hashmodtimeleafsize">--track-renames-strategy (hash,modtime,leaf,size)</h3>
+<p>This option changes the 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>So 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>If nothing is specified, the default option is matching by <code>hash</code>es.</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>
+<h3 id="fast-list">--fast-list</h3>
 <p>When doing anything which involves a directory listing (eg <code>sync</code>, <code>copy</code>, <code>ls</code> - in fact nearly every command), rclone normally lists a directory and processes it before using more directory lists to process any subdirectories. This can be parallelised and works very quickly using the least amount of memory.</p>
 <p>However, some remotes have a way of listing all files beneath a directory in one (or a small number) of transactions. These tend to be the bucket based remotes (eg S3, B2, GCS, Swift, Hubic).</p>
 <p>If you use the <code>--fast-list</code> flag then rclone will use this method for listing directories. This will have the following consequences for the listing:</p>
@@ -3179,54 +3442,54 @@ rclone sync /path/to/files remote:current-backup</code></pre>
 <li>It <strong>will</strong> use fewer transactions (important if you pay for them)</li>
 <li>It <strong>will</strong> use more memory. Rclone has to load the whole listing into memory.</li>
 <li>It <em>may</em> be faster because it uses fewer transactions</li>
-<li>It <em>may</em> be slower because it can’t be parallelized</li>
+<li>It <em>may</em> be slower because it can't be parallelized</li>
 </ul>
 <p>rclone should always give identical results with and without <code>--fast-list</code>.</p>
-<p>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.</p>
-<p>If you use <code>--fast-list</code> on a remote which doesn’t support it, then rclone will just ignore it.</p>
-<h3 id="timeouttime">–timeout=TIME</h3>
+<p>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.</p>
+<p>If you use <code>--fast-list</code> on a remote which doesn't support it, then rclone will just ignore it.</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>
+<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>
-<h3 id="u-update">-u, –update</h3>
+<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 when transferring to a remote which doesn’t support mod 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>.</p>
-<p>If an existing destination file has a modification time equal (within the computed modify window precision) to the source file’s, it will be updated if the sizes are different. If <code>--checksum</code> is set then rclone will update the destination if the checksums differ too.</p>
+<p>This can be useful when transferring to a remote which doesn't support mod 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>.</p>
+<p>If an existing destination file has a modification time equal (within the computed modify window precision) to the source file's, it will be updated if the sizes are different. If <code>--checksum</code> is set then rclone will update the destination if the checksums differ too.</p>
 <p>If an existing destination file is older than the source file then it will be updated if the size or checksum differs from the source file.</p>
-<p>On remotes which don’t support mod time directly (or when using <code>--use-server-modtime</code>) the time checked will be the uploaded time. This means that if uploading to one of these remotes, rclone will skip any files which exist on the destination and have an uploaded time that is newer than the modification time of the source file.</p>
-<h3 id="use-mmap">–use-mmap</h3>
+<p>On remotes which don't support mod time directly (or when using <code>--use-server-modtime</code>) the time checked will be the uploaded time. This means that if uploading to one of these remotes, rclone will skip any files which exist on the destination and have an uploaded time that is newer than the modification time of the source file.</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>
+<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>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>
+<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>
-<h3 id="v-version">-V, –version</h3>
+<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-string">–ca-cert string</h3>
+<h3 id="ca-cert-string">--ca-cert string</h3>
 <p>This loads the PEM encoded certificate authority certificate 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>
+<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>
+<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>
+<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>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:
@@ -3269,34 +3532,34 @@ export RCLONE_CONFIG_PASS</code></pre>
 <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>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>
 <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 eg <code>--drive-test-option</code> - see the docs for the remote in question.</p>
-<h3 id="cpuprofilefile">–cpuprofile=FILE</h3>
+<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 eg <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>
+<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>
+<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>
+<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>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>
+<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>
+<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>
+<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>
+<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>
-<h3 id="memprofilefile">–memprofile=FILE</h3>
+<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>
+<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>
@@ -3348,8 +3611,8 @@ export RCLONE_CONFIG_PASS</code></pre>
 <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>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</li>
 </ul>
 <h2 id="environment-variables">Environment Variables</h2>
@@ -3372,14 +3635,31 @@ $ rclone lsd MYS3:
 $ 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>
+<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>Flag values as supplied on the command line, eg <code>--drive-use-trash</code>.</li>
+<li>Remote specific environment vars, eg <code>RCLONE_CONFIG_MYREMOTE_USE_TRASH</code> (see above).</li>
+<li>Backend specific environment vars, eg <code>RCLONE_DRIVE_USE_TRASH</code>.</li>
+<li>Config file, eg <code>use_trash = false</code>.</li>
+<li>Default values, eg <code>true</code> - these can't be changed.</li>
+</ul>
+<p>So if both <code>--drive-use-trash</code> is supplied on the config line and an environment variable <code>RCLONE_DRIVE_USE_TRASH</code> is set, the command line flag will take preference.</p>
+<p>For non backend configuration the order is as follows:</p>
+<ul>
+<li>Flag values as supplied on the command line, eg <code>--stats 5s</code>.</li>
+<li>Environment vars, eg <code>RCLONE_STATS=5s</code>.</li>
+<li>Default values, eg <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>
+<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>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>
 <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>
@@ -3442,8 +3722,8 @@ Configuration file is stored at:
 <p>The filters are applied for the <code>copy</code>, <code>sync</code>, <code>move</code>, <code>ls</code>, <code>lsl</code>, <code>md5sum</code>, <code>sha1sum</code>, <code>size</code>, <code>delete</code> and <code>check</code> operations. Note that <code>purge</code> does not obey the filters.</p>
 <p>Each path as it passes through rclone is matched against the include and exclude rules like <code>--include</code>, <code>--exclude</code>, <code>--include-from</code>, <code>--exclude-from</code>, <code>--filter</code>, or <code>--filter-from</code>. The simplest way to try them out is using the <code>ls</code> command, or <code>--dry-run</code> together with <code>-v</code>. <code>--filter-from</code>, <code>--exclude-from</code>, <code>--include-from</code>, <code>--files-from</code>, <code>--files-from-raw</code> understand <code>-</code> as a file name to mean read from standard input.</p>
 <h2 id="patterns">Patterns</h2>
-<p>The patterns used to match files for inclusion or exclusion are based on “file globs” as used by the unix shell.</p>
-<p>If the 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 local drive). If it doesn’t start with <code>/</code> then it is matched starting at the <strong>end of the path</strong>, but it will only match a complete path element:</p>
+<p>The patterns used to match files for inclusion or exclusion are based on "file globs" as used by the unix shell.</p>
+<p>If the 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 local drive). If it doesn't start with <code>/</code> then it is matched starting at the <strong>end of the path</strong>, but it will only match a complete path element:</p>
 <pre><code>file.jpg  - matches &quot;file.jpg&quot;
           - matches &quot;directory/file.jpg&quot;
           - doesn&#39;t match &quot;afile.jpg&quot;
@@ -3485,7 +3765,7 @@ Configuration file is stored at:
 <p>With <code>--ignore-case</code></p>
 <pre><code>potato - matches &quot;potato&quot;
        - matches &quot;POTATO&quot;</code></pre>
-<p>Note also that rclone filter globs can only be used in one of the filter command line flags, not in the specification of the remote, so <code>rclone copy "remote:dir*.jpg" /path/to/dir</code> won’t work - what is required is <code>rclone --include "*.jpg" copy remote:dir /path/to/dir</code></p>
+<p>Note also that rclone filter globs can only be used in one of the filter command line flags, not in the specification of the remote, so <code>rclone copy "remote:dir*.jpg" /path/to/dir</code> won't work - what is required is <code>rclone --include "*.jpg" copy remote:dir /path/to/dir</code></p>
 <h3 id="directories">Directories</h3>
 <p>Rclone keeps track of directories that could match any file patterns.</p>
 <p>Eg if you add the include rule</p>
@@ -3493,9 +3773,9 @@ Configuration file is stored at:
 <p>Rclone will synthesize the directory include rule</p>
 <pre><code>/a/</code></pre>
 <p>If you put any rules which end in <code>/</code> then it will only match directories.</p>
-<p>Directory matches are <strong>only</strong> used to optimise directory access patterns - you must still match the files that you want to match. Directory matches won’t optimise anything on bucket based remotes (eg s3, swift, google compute storage, b2) which don’t have a concept of directory.</p>
+<p>Directory matches are <strong>only</strong> used to optimise directory access patterns - you must still match the files that you want to match. Directory matches won't optimise anything on bucket based remotes (eg s3, swift, google compute storage, b2) which don't have a concept of directory.</p>
 <h3 id="differences-between-rsync-and-rclone-patterns">Differences between rsync and rclone patterns</h3>
-<p>Rclone implements bash style <code>{a,b,c}</code> glob matching which rsync doesn’t.</p>
+<p>Rclone implements bash style <code>{a,b,c}</code> glob matching which rsync doesn't.</p>
 <p>Rclone always does a wildcard match so <code>\</code> must always escape a <code>\</code>.</p>
 <h2 id="how-the-rules-are-used">How the rules are used</h2>
 <p>Rclone maintains a combined list of include rules and exclude rules.</p>
@@ -3553,7 +3833,7 @@ file2.jpg</code></pre>
 <p>Add a single include rule with <code>--include</code>.</p>
 <p>This flag can be repeated. See above for the order the flags are processed in.</p>
 <p>Eg <code>--include *.{png,jpg}</code> to include all <code>png</code> and <code>jpg</code> files in the backup and no others.</p>
-<p>This adds an implicit <code>--exclude *</code> at the very end of the filter list. This means you can mix <code>--include</code> and <code>--include-from</code> with the other filters (eg <code>--exclude</code>) but you must include all the files you want in the include statement. If this doesn’t provide enough flexibility then you must use <code>--filter-from</code>.</p>
+<p>This adds an implicit <code>--exclude *</code> at the very end of the filter list. This means you can mix <code>--include</code> and <code>--include-from</code> with the other filters (eg <code>--exclude</code>) but you must include all the files you want in the include statement. If this doesn't provide enough flexibility then you must use <code>--filter-from</code>.</p>
 <h3 id="include-from---read-include-patterns-from-file"><code>--include-from</code> - Read include patterns from file</h3>
 <p>Add include rules from a file.</p>
 <p>This flag can be repeated. See above for the order the flags are processed in.</p>
@@ -3564,7 +3844,7 @@ file2.jpg</code></pre>
 file2.avi</code></pre>
 <p>Then use as <code>--include-from include-file.txt</code>. This will sync all <code>jpg</code>, <code>png</code> files and <code>file2.avi</code>.</p>
 <p>This is useful if you have a lot of rules.</p>
-<p>This adds an implicit <code>--exclude *</code> at the very end of the filter list. This means you can mix <code>--include</code> and <code>--include-from</code> with the other filters (eg <code>--exclude</code>) but you must include all the files you want in the include statement. If this doesn’t provide enough flexibility then you must use <code>--filter-from</code>.</p>
+<p>This adds an implicit <code>--exclude *</code> at the very end of the filter list. This means you can mix <code>--include</code> and <code>--include-from</code> with the other filters (eg <code>--exclude</code>) but you must include all the files you want in the include statement. If this doesn't provide enough flexibility then you must use <code>--filter-from</code>.</p>
 <h3 id="filter---add-a-file-filtering-rule"><code>--filter</code> - Add a file-filtering rule</h3>
 <p>This can be used to add a single include or exclude rule. Include rules start with <code>+</code> and exclude rules start with <code>-</code>. A special rule called <code>!</code> can be used to clear the existing rules.</p>
 <p>This flag can be repeated. See above for the order the flags are processed in.</p>
@@ -3590,7 +3870,7 @@ file2.avi</code></pre>
 <p>Rclone will traverse the file system if you use <code>--files-from</code>, effectively using the files in <code>--files-from</code> as a set of filters. Rclone will not error if any of the files are missing.</p>
 <p>If you use <code>--no-traverse</code> as well as <code>--files-from</code> then rclone will not traverse the destination file system, it will find each file individually using approximately 1 API call. This can be more efficient for small lists of files.</p>
 <p>This option can be repeated to read from more than one file. These are read in the order that they are placed on the command line.</p>
-<p>Paths within the <code>--files-from</code> file will be interpreted as starting with the root specified in the command. Leading <code>/</code> characters 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>Paths within the <code>--files-from</code> file will be interpreted as starting with the root specified in the command. Leading <code>/</code> characters 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>For example, suppose you had <code>files-from.txt</code> with this content:</p>
 <pre><code># comment
 file1.jpg
@@ -3600,11 +3880,11 @@ subdir/file2.jpg</code></pre>
 <p>This will transfer these files only (if they exist)</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>To take a more complicated example, let’s say you had a few files you want to back up regularly with these absolute paths:</p>
+<p>To take a more complicated example, let's say you had a few files you want to back up regularly with these absolute paths:</p>
 <pre><code>/home/user1/important
 /home/user1/dir/file
 /home/user2/stuff</code></pre>
-<p>To copy these you’d 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>, eg</p>
+<p>To copy these you'd 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>, eg</p>
 <pre><code>user1/important
 user1/dir/file
 user2/stuff</code></pre>
@@ -3626,13 +3906,13 @@ user2/stuff</code></pre>
 /home/user2/stuff     → remote:backup/home/user2/stuff</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 option is same as <code>--files-from</code> with the only difference being that the input is read in a raw manner. This means that 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, which can then be used as an input to <code>--files-from-raw</code>.</p>
-<h3 id="min-size---dont-transfer-any-file-smaller-than-this"><code>--min-size</code> - Don’t transfer any file smaller than this</h3>
+<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>This option controls the minimum size file which will be transferred. This defaults to <code>kBytes</code> but a suffix of <code>k</code>, <code>M</code>, or <code>G</code> can be used.</p>
 <p>For example <code>--min-size 50k</code> means no files smaller than 50kByte will be transferred.</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>
+<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>This option controls the maximum size file which will be transferred. This defaults to <code>kBytes</code> but a suffix of <code>k</code>, <code>M</code>, or <code>G</code> can be used.</p>
 <p>For example <code>--max-size 1G</code> means no files larger than 1GByte will be transferred.</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>
+<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>This option controls the maximum age of files to transfer. Give in seconds or with a suffix of:</p>
 <ul>
 <li><code>ms</code> - Milliseconds</li>
@@ -3647,19 +3927,19 @@ user2/stuff</code></pre>
 <p>For example <code>--max-age 2d</code> means no files older than 2 days will be transferred.</p>
 <p>This can also be an absolute time in one of these formats</p>
 <ul>
-<li>RFC3339 - eg “2006-01-02T15:04:05Z07:00”</li>
-<li>ISO8601 Date and time, local timezone - “2006-01-02T15:04:05”</li>
-<li>ISO8601 Date and time, local timezone - “2006-01-02 15:04:05”</li>
-<li>ISO8601 Date - “2006-01-02” (YYYY-MM-DD)</li>
+<li>RFC3339 - eg "2006-01-02T15:04:05Z07:00"</li>
+<li>ISO8601 Date and time, local timezone - "2006-01-02T15:04:05"</li>
+<li>ISO8601 Date and time, local timezone - "2006-01-02 15:04:05"</li>
+<li>ISO8601 Date - "2006-01-02" (YYYY-MM-DD)</li>
 </ul>
-<h3 id="min-age---dont-transfer-any-file-younger-than-this"><code>--min-age</code> - Don’t transfer any file younger than this</h3>
+<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>This option controls the minimum age of files to transfer. Give in seconds or with a suffix (see <code>--max-age</code> for list of suffixes)</p>
 <p>For example <code>--min-age 2d</code> means no files younger than 2 days will be transferred.</p>
 <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 - use with <code>--dry-run</code> and <code>-v</code> first.</p>
 <p>When doing <code>rclone sync</code> this will delete any files which are excluded from the sync on the destination.</p>
 <p>If for example you did a sync from <code>A</code> to <code>B</code> without the <code>--min-size 50k</code> flag</p>
-<pre><code>rclone sync A: B:</code></pre>
+<pre><code>rclone sync -i A: B:</code></pre>
 <p>Then you repeated it like this with the <code>--delete-excluded</code></p>
 <pre><code>rclone --min-size 50k --delete-excluded sync A: B:</code></pre>
 <p>This would delete all files on <code>B</code> which are less than 50 kBytes as these are now excluded from the sync.</p>
@@ -3690,8 +3970,8 @@ dir1/dir2/file2
 dir1/dir2/dir3/file3
 dir1/dir2/dir3/.ignore</code></pre>
 <p>You can exclude <code>dir3</code> from sync by running the following command:</p>
-<pre><code>rclone sync --exclude-if-present .ignore dir1 remote:backup</code></pre>
-<p>Currently only one filename is supported, i.e. <code>--exclude-if-present</code> should not be used multiple times.</p>
+<pre><code>rclone sync -i --exclude-if-present .ignore dir1 remote:backup</code></pre>
+<p>Currently only one filename is supported, i.e. <code>--exclude-if-present</code> should not be used multiple times.</p>
 <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>
@@ -3719,7 +3999,7 @@ dir1/dir2/dir3/.ignore</code></pre>
 <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>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>
@@ -3766,65 +4046,65 @@ dir1/dir2/dir3/.ignore</code></pre>
 <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>If you just want to run a remote control then see the <a href="https://rclone.org/commands/rclone_rcd/">rcd command</a>.</p>
 <h2 id="supported-parameters">Supported parameters</h2>
-<h3 id="rc">–rc</h3>
+<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>
+<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>
+<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>
+<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>
+<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>
+<h3 id="rc-max-header-bytesvalue">--rc-max-header-bytes=VALUE</h3>
 <p>Maximum size of request header (default 4096)</p>
-<h3 id="rc-uservalue">–rc-user=VALUE</h3>
+<h3 id="rc-uservalue">--rc-user=VALUE</h3>
 <p>User name for authentication.</p>
-<h3 id="rc-passvalue">–rc-pass=VALUE</h3>
+<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>
+<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>
+<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>
+<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-files-pathtodirectory">–rc-files /path/to/directory</h3>
+<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>
+<h3 id="rc-enable-metrics">--rc-enable-metrics</h3>
 <p>Enable OpenMetrics/Prometheus compatible endpoint at <code>/metrics</code>.</p>
 <p>Default Off.</p>
-<h3 id="rc-web-gui">–rc-web-gui</h3>
+<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>
+<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>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>
+<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>
+<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>
+<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>
+<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>
+<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>
+<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>
+<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>
@@ -3837,6 +4117,7 @@ dir1/dir2/dir3/.ignore</code></pre>
     &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
 {
@@ -3851,6 +4132,10 @@ dir1/dir2/dir3/.ignore</code></pre>
         &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>
@@ -3907,7 +4192,7 @@ dir1/dir2/dir3/.ignore</code></pre>
 <p>This takes the following parameters</p>
 <ul>
 <li>command - a string with the command name</li>
-<li>fs - a remote name string eg “drive:”</li>
+<li>fs - a remote name string eg "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>
@@ -3931,9 +4216,9 @@ dir1/dir2/dir3/.ignore</code></pre>
         }
     }
 }</code></pre>
-<p>Note that this is the direct equivalent of using this “backend” command:</p>
+<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>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>
@@ -3944,9 +4229,9 @@ 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, eg</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, eg</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>
@@ -3955,7 +4240,7 @@ rclone rc cache/expire remote=/ withData=true</code></pre>
 <p>This takes the following parameters</p>
 <ul>
 <li>name - name of remote</li>
-<li>parameters - a map of { “key”: “value” } pairs</li>
+<li>parameters - a map of { "key": "value" } pairs</li>
 <li>type - type of the new remote</li>
 <li>obscure - optional bool - forces obscuring of passwords</li>
 <li>noObscure - optional bool - forces passwords not to be obscured</li>
@@ -3989,7 +4274,7 @@ rclone rc cache/expire remote=/ withData=true</code></pre>
 <p>This takes the following parameters</p>
 <ul>
 <li>name - name of remote</li>
-<li>parameters - a map of { “key”: “value” } pairs</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 command</a> command for more information on the above.</p>
 <p><strong>Authentication is required for this call.</strong></p>
@@ -4001,7 +4286,7 @@ rclone rc cache/expire remote=/ withData=true</code></pre>
 <p>This takes the following parameters</p>
 <ul>
 <li>name - name of remote</li>
-<li>parameters - a map of { “key”: “value” } pairs</li>
+<li>parameters - a map of { "key": "value" } pairs</li>
 <li>obscure - optional bool - forces obscuring of passwords</li>
 <li>noObscure - optional bool - forces passwords not to be obscured</li>
 </ul>
@@ -4026,8235 +4311,8118 @@ rclone rc core/bwlimit rate=1M
     &quot;bytesPerSecond&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-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;speed&quot;: average speed in bytes/sec since start of the process,
-    &quot;bytes&quot;: total transferred bytes since the start of the process,
-    &quot;errors&quot;: number of errors,
-    &quot;fatalError&quot;: whether there has been at least one FatalError,
-    &quot;retryError&quot;: whether there has been at least one non-NoRetryError,
-    &quot;checks&quot;: number of checked files,
-    &quot;transfers&quot;: number of transferred files,
-    &quot;deletes&quot; : number of deleted files,
-    &quot;renames&quot; : number of renamed files,
-    &quot;elapsedTime&quot;: time in seconds since the start of the process,
-    &quot;lastError&quot;: last occurred error,
-    &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;: speed in bytes/sec,
-                &quot;speedAvg&quot;: speed in bytes/sec 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, eg “v1.44”</li>
-<li>decomposed - version number as [major, minor, patch, subpatch]
-<ul>
-<li>note patch and subpatch will be 999 for a git compiled version</li>
-</ul></li>
-<li>isGit - boolean - true if this was compiled from the git 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>
-</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-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="job-list">job/list: Lists the IDs of the running jobs</h3>
-<p>Parameters - None</p>
-<p>Results</p>
-<ul>
-<li>jobids - array of integer job ids</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 (eg “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 (eg “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="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>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>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>
-</ul>
-<p>Eg</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</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 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 the following parameters</p>
-<ul>
-<li>mountPoint: valid path on the local machine where the mount was created (required)</li>
-</ul>
-<p>Eg</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="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 eg “drive:”</li>
-</ul>
-<p>The result is as returned from rclone about –json</p>
-<p>See the <a href="https://rclone.org/commands/rclone_size/">about command</a> command for more information on the above.</p>
-<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 eg “drive:”</li>
-</ul>
-<p>See the <a href="https://rclone.org/commands/rclone_cleanup/">cleanup command</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 eg “drive:” for the source</li>
-<li>srcRemote - a path within that remote eg “file.txt” for the source</li>
-<li>dstFs - a remote name string eg “drive2:” for the destination</li>
-<li>dstRemote - a path within that remote eg “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 eg “drive:”</li>
-<li>remote - a path within that remote eg “dir”</li>
-<li>url - string, URL to read from</li>
-<li>autoFilename - boolean, set to true to retrieve destination file name from url See the <a href="https://rclone.org/commands/rclone_copyurl/">copyurl command</a> command for more information on the above.</li>
-</ul>
-<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 eg “drive:”</li>
-</ul>
-<p>See the <a href="https://rclone.org/commands/rclone_delete/">delete command</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 eg “drive:”</li>
-<li>remote - a path within that remote eg “dir”</li>
-</ul>
-<p>See the <a href="https://rclone.org/commands/rclone_deletefile/">deletefile command</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 eg “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;CanHaveEmptyDirectories&quot;: true,
-        &quot;CaseInsensitive&quot;: false,
-        &quot;ChangeNotify&quot;: false,
-        &quot;CleanUp&quot;: false,
-        &quot;Copy&quot;: false,
-        &quot;DirCacheFlush&quot;: false,
-        &quot;DirMove&quot;: true,
-        &quot;DuplicateFiles&quot;: false,
-        &quot;GetTier&quot;: false,
-        &quot;ListR&quot;: false,
-        &quot;MergeDirs&quot;: false,
-        &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;ReadMimeType&quot;: false,
-        &quot;ServerSideAcrossConfigs&quot;: false,
-        &quot;SetTier&quot;: false,
-        &quot;SetWrapper&quot;: false,
-        &quot;UnWrap&quot;: false,
-        &quot;WrapFs&quot;: false,
-        &quot;WriteMimeType&quot;: false
-    },
-    // Names of hashes available
-    &quot;Hashes&quot;: [
-        &quot;MD5&quot;,
-        &quot;SHA-1&quot;,
-        &quot;DropboxHash&quot;,
-        &quot;QuickXorHash&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
-}</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-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 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>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>
-</ul></li>
-</ul>
-<p>The result is</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 command</a> 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 eg “drive:”</li>
-<li>remote - a path within that remote eg “dir”</li>
-</ul>
-<p>See the <a href="https://rclone.org/commands/rclone_mkdir/">mkdir command</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 eg “drive:” for the source</li>
-<li>srcRemote - a path within that remote eg “file.txt” for the source</li>
-<li>dstFs - a remote name string eg “drive2:” for the destination</li>
-<li>dstRemote - a path within that remote eg “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 eg “drive:”</li>
-<li>remote - a path within that remote eg “dir”</li>
+<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>
 </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 command</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 eg “drive:”</li>
-<li>remote - a path within that remote eg “dir”</li>
-</ul>
-<p>See the <a href="https://rclone.org/commands/rclone_purge/">purge command</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 eg “drive:”</li>
-<li>remote - a path within that remote eg “dir”</li>
-</ul>
-<p>See the <a href="https://rclone.org/commands/rclone_rmdir/">rmdir command</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 eg “drive:”</li>
-<li>remote - a path within that remote eg “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 command</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 eg “drive:path/to/dir”</li>
+<li>result - result from the backend command</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>For 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>
-<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 command</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 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>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)</p>
-<pre><code>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;: 7}}&#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;: 6}}&#39;</code></pre>
-<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-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 eg “drive:src” for the source</li>
-<li>dstFs - a remote name string eg “drive:dst” for the destination</li>
-</ul>
-<p>See the <a href="https://rclone.org/commands/rclone_copy/">copy command</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 eg “drive:src” for the source</li>
-<li>dstFs - a remote name string eg “drive:dst” for the destination</li>
-<li>deleteEmptySrcDirs - delete empty src directories if set</li>
-</ul>
-<p>See the <a href="https://rclone.org/commands/rclone_move/">move command</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 eg “drive:src” for the source</li>
-<li>dstFs - a remote name string eg “drive:dst” for the destination</li>
-</ul>
-<p>See the <a href="https://rclone.org/commands/rclone_sync/">sync command</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, eg</p>
-<pre><code>rclone rc vfs/forget file=hello file2=goodbye dir=home/junk</code></pre>
-<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>
-<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, eg</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>
-<h2 id="accessing-the-remote-control-via-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 (eg 500) and the body of the response will contain a JSON encoded error object, eg</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;
+    &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;
+}
+
+**Authentication is required for this call.**
+
+### core/gc: Runs a garbage collection. {#core-gc}
+
+This tells the go runtime to do a garbage collection run.  It isn&#39;t
+necessary to call this normally, but it can be useful for debugging
+memory problems.
+
+### core/group-list: Returns list of stats. {#core-group-list}
+
+This returns list of stats groups currently in memory. 
+
+Returns the following values:</code></pre>
+<p>{ "groups": an array of group names: [ "group1", "group2", ... ] }</p>
+<pre><code>
+### core/memstats: Returns the memory statistics {#core-memstats}
+
+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
+
+The most interesting values for most people are:
+
+* HeapAlloc: This is the amount of memory rclone is actually using
+* HeapSys: This is the amount of memory rclone has obtained from the OS
+* Sys: this is the total amount of memory requested from the OS
+  * It is virtual memory so may include unused memory
+
+### core/obscure: Obscures a string passed in. {#core-obscure}
+
+Pass a clear string and rclone will obscure it for the config file:
+- clear - string
+
+Returns
+- obscured - string
+
+### core/pid: Return PID of current process {#core-pid}
+
+This returns PID of current process.
+Useful for stopping rclone process.
+
+### core/quit: Terminates the app. {#core-quit}
+
+(optional) Pass an exit code to be used for terminating the app:
+- exitCode - int
+
+### core/stats: Returns stats about current transfers. {#core-stats}
+
+This returns all available stats:
+
+    rclone rc core/stats
+
+If group is not provided then summed up stats for all groups will be
+returned.
+
+Parameters
+
+- group - name of the stats group (string)
+
+Returns the following values:
 </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>
-</tr>
-</thead>
-<tbody>
-<tr class="odd">
-<td>1Fichier</td>
-<td style="text-align: center;">Whirlpool</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;">R</td>
-</tr>
-<tr class="even">
-<td>Amazon Drive</td>
-<td style="text-align: center;">MD5</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;">R</td>
-</tr>
-<tr class="odd">
-<td>Amazon S3</td>
-<td style="text-align: center;">MD5</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;">R/W</td>
-</tr>
-<tr class="even">
-<td>Backblaze B2</td>
-<td style="text-align: center;">SHA1</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;">R/W</td>
-</tr>
-<tr class="odd">
-<td>Box</td>
-<td style="text-align: center;">SHA1</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;">-</td>
-</tr>
-<tr class="even">
-<td>Citrix ShareFile</td>
-<td style="text-align: center;">MD5</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;">-</td>
-</tr>
-<tr class="odd">
-<td>Dropbox</td>
-<td style="text-align: center;">DBHASH †</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;">-</td>
-</tr>
-<tr class="even">
-<td>FTP</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;">No</td>
-<td style="text-align: center;">-</td>
-</tr>
-<tr class="odd">
-<td>Google Cloud Storage</td>
-<td style="text-align: center;">MD5</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;">R/W</td>
-</tr>
-<tr class="even">
-<td>Google Drive</td>
-<td style="text-align: center;">MD5</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;">R/W</td>
-</tr>
-<tr class="odd">
-<td>Google Photos</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;">Yes</td>
-<td style="text-align: center;">R</td>
-</tr>
-<tr class="even">
-<td>HTTP</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;">No</td>
-<td style="text-align: center;">R</td>
-</tr>
-<tr class="odd">
-<td>Hubic</td>
-<td style="text-align: center;">MD5</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;">R/W</td>
-</tr>
-<tr class="even">
-<td>Jottacloud</td>
-<td style="text-align: center;">MD5</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;">R/W</td>
-</tr>
-<tr class="odd">
-<td>Koofr</td>
-<td style="text-align: center;">MD5</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;">-</td>
-</tr>
-<tr class="even">
-<td>Mail.ru Cloud</td>
-<td style="text-align: center;">Mailru ‡‡‡</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;">-</td>
-</tr>
-<tr class="odd">
-<td>Mega</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;">Yes</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;">Yes</td>
-<td style="text-align: center;">No</td>
-<td style="text-align: center;">No</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;">Yes</td>
-<td style="text-align: center;">No</td>
-<td style="text-align: center;">No</td>
-<td style="text-align: center;">R/W</td>
-</tr>
-<tr class="even">
-<td>Microsoft OneDrive</td>
-<td style="text-align: center;">SHA1 ‡‡</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;">R</td>
-</tr>
-<tr class="odd">
-<td>OpenDrive</td>
-<td style="text-align: center;">MD5</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;">-</td>
-</tr>
-<tr class="even">
-<td>OpenStack Swift</td>
-<td style="text-align: center;">MD5</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;">R/W</td>
-</tr>
-<tr class="odd">
-<td>pCloud</td>
-<td style="text-align: center;">MD5, SHA1</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;">W</td>
-</tr>
-<tr class="even">
-<td>premiumize.me</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;">No</td>
-<td style="text-align: center;">R</td>
-</tr>
-<tr class="odd">
-<td>put.io</td>
-<td style="text-align: center;">CRC-32</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;">R</td>
-</tr>
-<tr class="even">
-<td>QingStor</td>
-<td style="text-align: center;">MD5</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;">R/W</td>
-</tr>
-<tr class="odd">
-<td>Seafile</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;">No</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;">Yes</td>
-<td style="text-align: center;">Depends</td>
-<td style="text-align: center;">No</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;">No</td>
-<td style="text-align: center;">No</td>
-<td style="text-align: center;">No</td>
-<td style="text-align: center;">-</td>
-</tr>
-<tr class="even">
-<td>Tardigrade</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;">No</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;">Yes †††</td>
-<td style="text-align: center;">Depends</td>
-<td style="text-align: center;">No</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;">Yes</td>
-<td style="text-align: center;">No</td>
-<td style="text-align: center;">No</td>
-<td style="text-align: center;">R/W</td>
-</tr>
-<tr class="odd">
-<td>The local filesystem</td>
-<td style="text-align: center;">All</td>
-<td style="text-align: center;">Yes</td>
-<td style="text-align: center;">Depends</td>
-<td style="text-align: center;">No</td>
-<td style="text-align: center;">-</td>
-</tr>
-</tbody>
-</table>
-<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>
-<p>† Note that 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 4MB 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 Owncloud and Nextcloud only.</p>
-<p>††† WebDAV supports modtimes when used with Owncloud and Nextcloud only.</p>
-<p>‡‡ Microsoft OneDrive Personal supports SHA1 hashes, whereas OneDrive for business and SharePoint server support Microsoft’s own <a href="https://docs.microsoft.com/en-us/onedrive/developer/code-snippets/quickxorhash">QuickXorHash</a>.</p>
-<p>‡‡‡ Mail.ru uses its own modified SHA1 hash</p>
-<h3 id="modtime">ModTime</h3>
-<p>The cloud storage system supports setting modification times on objects. If it does then this enables a using the modification times as part of the sync. If not then only the size will be checked by default, though the MD5SUM can be checked with the <code>--checksum</code> flag.</p>
-<p>All cloud storage systems support some kind of date on the object and these will be set when transferring from the cloud storage system.</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, eg <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 (eg 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.</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 will be displayed as <code>my file?.txt</code> on the console, but stored as <code>my file？.txt</code> (the <code>?</code> gets replaced by the similar looking <code>？</code> character) to Onedrive. 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> (the <code>/</code> needs to be replaced by the similar looking <code>／</code> character) on the command line.</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 options, 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 characters such as <code>＊</code> and <code>？</code> that you want to remain as those characters on the remote rather than being translated to <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 None</code> or set <code>encoding = None</code> in the config file.</p>
-<p>Encoding takes a comma separated list of encodings. You can see the list of all available characters by passing an invalid value to this flag, eg <code>--local-encoding "help"</code> and <code>rclone help flags encoding</code> will show you the defaults for the backends.</p>
-<table>
-<thead>
-<tr class="header">
-<th>Encoding</th>
-<th>Characters</th>
-</tr>
-</thead>
-<tbody>
-<tr class="odd">
-<td>Asterisk</td>
-<td><code>*</code></td>
-</tr>
-<tr class="even">
-<td>BackQuote</td>
-<td><code>`</code></td>
-</tr>
-<tr class="odd">
-<td>BackSlash</td>
-<td><code>\</code></td>
-</tr>
-<tr class="even">
-<td>Colon</td>
-<td><code>:</code></td>
-</tr>
-<tr class="odd">
-<td>CrLf</td>
-<td>CR 0x0D, LF 0x0A</td>
-</tr>
-<tr class="even">
-<td>Ctl</td>
-<td>All control characters 0x00-0x1F</td>
-</tr>
-<tr class="odd">
-<td>Del</td>
-<td>DEL 0x7F</td>
-</tr>
-<tr class="even">
-<td>Dollar</td>
-<td><code>$</code></td>
-</tr>
-<tr class="odd">
-<td>Dot</td>
-<td><code>.</code></td>
-</tr>
-<tr class="even">
-<td>DoubleQuote</td>
-<td><code>"</code></td>
-</tr>
-<tr class="odd">
-<td>Hash</td>
-<td><code>#</code></td>
-</tr>
-<tr class="even">
-<td>InvalidUtf8</td>
-<td>An invalid UTF-8 character (eg latin1)</td>
-</tr>
-<tr class="odd">
-<td>LeftCrLfHtVt</td>
-<td>CR 0x0D, LF 0x0A,HT 0x09, VT 0x0B on the left of a string</td>
-</tr>
-<tr class="even">
-<td>LeftPeriod</td>
-<td><code>.</code> on the left of a string</td>
-</tr>
-<tr class="odd">
-<td>LeftSpace</td>
-<td>SPACE on the left of a string</td>
-</tr>
-<tr class="even">
-<td>LeftTilde</td>
-<td><code>~</code> on the left of a string</td>
-</tr>
-<tr class="odd">
-<td>LtGt</td>
-<td><code>&lt;</code>, <code>&gt;</code></td>
-</tr>
-<tr class="even">
-<td>None</td>
-<td>No characters are encoded</td>
-</tr>
-<tr class="odd">
-<td>Percent</td>
-<td><code>%</code></td>
-</tr>
-<tr class="even">
-<td>Pipe</td>
-<td>|</td>
-</tr>
-<tr class="odd">
-<td>Question</td>
-<td><code>?</code></td>
-</tr>
-<tr class="even">
-<td>RightCrLfHtVt</td>
-<td>CR 0x0D, LF 0x0A, HT 0x09, VT 0x0B on the right of a string</td>
-</tr>
-<tr class="odd">
-<td>RightPeriod</td>
-<td><code>.</code> on the right of a string</td>
-</tr>
-<tr class="even">
-<td>RightSpace</td>
-<td>SPACE on the right of a string</td>
-</tr>
-<tr class="odd">
-<td>SingleQuote</td>
-<td><code>'</code></td>
-</tr>
-<tr class="even">
-<td>Slash</td>
-<td><code>/</code></td>
-</tr>
-</tbody>
-</table>
-<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>
-<p>Or let’s say you have a Windows server but you want to preserve <code>＊</code> and <code>？</code>, you would then have this as the encoding (the Windows encoding minus <code>Asterisk</code> and <code>Question</code>).</p>
-<pre><code>Slash,LtGt,DoubleQuote,Colon,Pipe,BackSlash,Ctl,RightSpace,RightPeriod,InvalidUtf8,Dot</code></pre>
-<p>This can be specified using the <code>--local-encoding</code> flag or using an <code>encoding</code> parameter in the config file.</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, eg <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>
-<h2 id="optional-features">Optional Features</h2>
-<p>All the remotes support a basic set of features, but there are some optional features supported by some remotes used to make some operations more efficient.</p>
-<table>
-<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: 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;">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: center;">No</td>
-<td style="text-align: center;">Yes</td>
-</tr>
-<tr class="even">
-<td>Amazon 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;">No <a href="https://github.com/rclone/rclone/issues/575">#575</a></td>
-<td style="text-align: center;">No</td>
-<td style="text-align: center;">No</td>
-<td style="text-align: center;">No <a href="https://github.com/rclone/rclone/issues/2178">#2178</a></td>
-<td style="text-align: center;">No</td>
-<td style="text-align: center;">Yes</td>
-</tr>
-<tr class="odd">
-<td>Amazon S3</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: center;">No <a href="https://github.com/rclone/rclone/issues/2178">#2178</a></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: 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;">No <a href="https://github.com/rclone/rclone/issues/575">#575</a></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;">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;">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>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 <a href="https://github.com/rclone/rclone/issues/575">#575</a></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;">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: center;">No <a href="https://github.com/rclone/rclone/issues/2178">#2178</a></td>
-<td style="text-align: center;">No</td>
-<td style="text-align: center;">Yes</td>
-</tr>
-<tr class="odd">
-<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: center;">No <a href="https://github.com/rclone/rclone/issues/2178">#2178</a></td>
-<td style="text-align: center;">No</td>
-<td style="text-align: center;">No</td>
-</tr>
-<tr class="even">
-<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: center;">Yes</td>
-<td style="text-align: center;">Yes</td>
-<td style="text-align: center;">Yes</td>
-</tr>
-<tr class="odd">
-<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: center;">No</td>
-<td style="text-align: center;">No</td>
-<td style="text-align: center;">No</td>
-</tr>
-<tr class="even">
-<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: center;">No <a href="https://github.com/rclone/rclone/issues/2178">#2178</a></td>
-<td style="text-align: center;">No</td>
-<td style="text-align: center;">Yes</td>
-</tr>
-<tr class="odd">
-<td>Hubic</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: center;">No <a href="https://github.com/rclone/rclone/issues/2178">#2178</a></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: center;">Yes</td>
-<td style="text-align: center;">Yes</td>
-<td style="text-align: center;">Yes</td>
-</tr>
-<tr class="odd">
-<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: center;">Yes</td>
-<td style="text-align: center;">Yes</td>
-<td style="text-align: center;">Yes</td>
-</tr>
-<tr class="even">
-<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: center;">No <a href="https://github.com/rclone/rclone/issues/2178">#2178</a></td>
-<td style="text-align: center;">Yes</td>
-<td style="text-align: center;">Yes</td>
-</tr>
-<tr class="odd">
-<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: center;">No</td>
-<td style="text-align: center;">No</td>
-<td style="text-align: center;">No</td>
-</tr>
-<tr class="even">
-<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: center;">No <a href="https://github.com/rclone/rclone/issues/2178">#2178</a></td>
-<td style="text-align: center;">No</td>
-<td style="text-align: center;">No</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;">No <a href="https://github.com/rclone/rclone/issues/575">#575</a></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>
-</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: 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: center;">No <a href="https://github.com/rclone/rclone/issues/2178">#2178</a></td>
-<td style="text-align: center;">Yes</td>
-<td style="text-align: center;">No</td>
-</tr>
-<tr class="even">
-<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: center;">No <a href="https://github.com/rclone/rclone/issues/2178">#2178</a></td>
-<td style="text-align: center;">Yes</td>
-<td style="text-align: center;">Yes</td>
-</tr>
-<tr class="odd">
-<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: center;">Yes</td>
-<td style="text-align: center;">Yes</td>
-<td style="text-align: center;">Yes</td>
-</tr>
-<tr class="even">
-<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: center;">No <a href="https://github.com/rclone/rclone/issues/2178">#2178</a></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: center;">No <a href="https://github.com/rclone/rclone/issues/2178">#2178</a></td>
-<td style="text-align: center;">No</td>
-<td style="text-align: center;">No</td>
-</tr>
-<tr class="even">
-<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: center;">Yes</td>
-<td style="text-align: center;">Yes</td>
-<td style="text-align: center;">Yes</td>
-</tr>
-<tr class="odd">
-<td>SFTP</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: center;">No <a href="https://github.com/rclone/rclone/issues/2178">#2178</a></td>
-<td style="text-align: center;">Yes</td>
-<td style="text-align: center;">Yes</td>
-</tr>
-<tr class="even">
-<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: center;">Yes</td>
-<td style="text-align: center;">No</td>
-<td style="text-align: center;">Yes</td>
-</tr>
-<tr class="odd">
-<td>Tardigrade</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: center;">No</td>
-<td style="text-align: center;">No</td>
-<td style="text-align: center;">No</td>
-</tr>
-<tr class="even">
-<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: center;">No <a href="https://github.com/rclone/rclone/issues/2178">#2178</a></td>
-<td style="text-align: center;">Yes</td>
-<td style="text-align: center;">Yes</td>
-</tr>
-<tr class="odd">
-<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: center;">Yes</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;">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: center;">No</td>
-<td style="text-align: center;">Yes</td>
-<td style="text-align: center;">Yes</td>
-</tr>
-</tbody>
-</table>
-<h3 id="purge">Purge</h3>
-<p>This deletes a directory quicker than just deleting all the files in the directory.</p>
-<p>† Note Swift, Hubic, and Tardigrade implement this in order to delete directory markers but they don’t actually have a quicker way of deleting files other than deleting them individually.</p>
-<p>‡ StreamUpload is not supported with Nextcloud</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>
-<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="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>This is used to fetch quota information from the remote, like bytes used/free/quota and bytes used in the trash.</p>
-<p>This is also used to return the space used, available for <code>rclone mount</code>.</p>
-<p>If the server can’t do <code>About</code> then <code>rclone about</code> will return an error.</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 two groups, non backend and backend flags.</p>
-<h2 id="non-backend-flags">Non Backend Flags</h2>
-<p>These flags are available for every command.</p>
-<pre><code>      --ask-password                         Allow prompt for password for encrypted configuration. (default true)
-      --auto-confirm                         If enabled, do not request console confirmation.
-      --backup-dir string                    Make backups into hierarchy based in DIR.
-      --bind string                          Local address to bind to for outgoing connections, IPv4, IPv6 or name.
-      --buffer-size SizeSuffix               In memory buffer size when reading files for each --transfer. (default 16M)
-      --bwlimit BwTimetable                  Bandwidth limit in kBytes/s, or use suffix b|k|M|G or a full timetable.
-      --ca-cert string                       CA certificate used to verify servers
-      --cache-dir string                     Directory rclone will use for caching. (default &quot;$HOME/.cache/rclone&quot;)
-      --check-first                          Do all the checks before starting transfers.
-      --checkers int                         Number of checkers to run in parallel. (default 8)
-  -c, --checksum                             Skip based on checksum (if available) &amp; size, not mod-time &amp; size
-      --client-cert string                   Client SSL certificate (PEM) for mutual TLS auth
-      --client-key string                    Client SSL private key (PEM) for mutual TLS auth
-      --compare-dest string                  Include additional server-side path during comparison.
-      --config string                        Config file. (default &quot;$HOME/.config/rclone/rclone.conf&quot;)
-      --contimeout duration                  Connect timeout (default 1m0s)
-      --copy-dest string                     Implies --compare-dest but also copies files from path into destination.
-      --cpuprofile string                    Write cpu profile to file
-      --cutoff-mode string                   Mode to stop transfers when reaching the max transfer limit HARD|SOFT|CAUTIOUS (default &quot;HARD&quot;)
-      --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
-      --delete-excluded                      Delete files on dest excluded from sync
-      --disable string                       Disable a comma separated list of features.  Use help to see a list.
-  -n, --dry-run                              Do a trial run with no permanent changes
-      --dump DumpFlags                       List of items to dump from: headers,bodies,requests,responses,auth,filters,goroutines,openfiles
-      --dump-bodies                          Dump HTTP headers and bodies - may contain sensitive info
-      --dump-headers                         Dump HTTP headers - may contain sensitive info
-      --error-on-no-transfer                 Sets exit code 9 if no files are transferred, useful in scripts
-      --exclude stringArray                  Exclude files matching pattern
-      --exclude-from stringArray             Read exclude patterns from file (use - to read from stdin)
-      --exclude-if-present string            Exclude directories if filename is present
-      --expect-continue-timeout duration     Timeout when using expect / 100-continue in HTTP (default 1s)
-      --fast-list                            Use recursive list if available. Uses more memory but fewer transactions.
-      --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 filtering patterns from a file (use - to read from stdin)
-      --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
-      --ignore-case                          Ignore case in filters (case insensitive)
-      --ignore-case-sync                     Ignore case when synchronizing
-      --ignore-checksum                      Skip post copy check of checksums.
-      --ignore-errors                        delete even if there are I/O errors
-      --ignore-existing                      Skip all files that exist on destination
-      --ignore-size                          Ignore size when skipping use mod-time or checksum.
-  -I, --ignore-times                         Don&#39;t skip files that match size and time - transfer all files
-      --immutable                            Do not modify files. Fail if existing files have been modified.
-      --include stringArray                  Include files matching pattern
-      --include-from stringArray             Read include patterns from file (use - to read from stdin)
-      --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 string                     Log level DEBUG|INFO|NOTICE|ERROR (default &quot;NOTICE&quot;)
-      --low-level-retries int                Number of low level retries to do. (default 10)
-      --max-age Duration                     Only transfer files younger than this in s or suffix ms|s|m|h|d|w|M|y (default off)
-      --max-backlog int                      Maximum number of objects in sync or check backlog. (default 10000)
-      --max-delete int                       When synchronizing, limit the number of deletes (default -1)
-      --max-depth int                        If set limits the recursion depth to this. (default -1)
-      --max-duration duration                Maximum duration rclone will transfer data for.
-      --max-size SizeSuffix                  Only transfer files smaller than this in k or suffix b|k|M|G (default off)
-      --max-stats-groups int                 Maximum number of stats groups to keep in memory. On max oldest is discarded. (default 1000)
-      --max-transfer SizeSuffix              Maximum size of data to transfer. (default off)
-      --memprofile string                    Write memory profile to file
-      --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 k or suffix b|k|M|G (default off)
-      --modify-window duration               Max time diff to be considered the same (default 1ns)
-      --multi-thread-cutoff SizeSuffix       Use multi-thread downloads for files above this size. (default 250M)
-      --multi-thread-streams int             Max number of streams to use for multi-thread downloads. (default 4)
-      --no-check-certificate                 Do not verify the server SSL certificate. Insecure.
-      --no-check-dest                        Don&#39;t check the destination, copy regardless.
-      --no-gzip-encoding                     Don&#39;t set Accept-Encoding: gzip.
-      --no-traverse                          Don&#39;t traverse destination file system on copy.
-      --no-unicode-normalization             Don&#39;t normalize unicode characters in filenames.
-      --no-update-modtime                    Don&#39;t update destination mod-time if files identical.
-      --order-by string                      Instructions on how to order the transfers, eg &#39;size,descending&#39;
-      --password-command SpaceSepList        Command for supplying password for encrypted configuration.
-  -P, --progress                             Show progress during transfer.
-  -q, --quiet                                Print as little stuff as possible
-      --rc                                   Enable the remote control server.
-      --rc-addr string                       IPaddress:Port or :Port to bind server to. (default &quot;localhost:5572&quot;)
-      --rc-allow-origin string               Set the allowed origin for CORS.
-      --rc-baseurl string                    Prefix for URLs - leave blank for root.
-      --rc-cert string                       SSL PEM key (concatenation of certificate and CA certificate)
-      --rc-client-ca string                  Client certificate authority to verify clients with
-      --rc-enable-metrics                    Enable prometheus metrics on /metrics
-      --rc-files string                      Path to local files to serve on the HTTP server.
-      --rc-htpasswd string                   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                        SSL PEM Private key
-      --rc-max-header-bytes int              Maximum size of request header (default 4096)
-      --rc-no-auth                           Don&#39;t require auth for certain methods.
-      --rc-pass string                       Password for authentication.
-      --rc-realm string                      realm for authentication (default &quot;rclone&quot;)
-      --rc-serve                             Enable the serving of remote objects.
-      --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
-      --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)
-      --size-only                            Skip based on size only, not mod-time or checksum
-      --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 string               Log level to show --stats output DEBUG|INFO|NOTICE|ERROR (default &quot;INFO&quot;)
-      --stats-one-line                       Make the stats fit on one line.
-      --stats-one-line-date                  Enables --stats-one-line and add current date/time prefix.
-      --stats-one-line-date-format string    Enables --stats-one-line-date and uses 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;/s (default &quot;bytes&quot;)
-      --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 100k)
-      --suffix string                        Suffix to add to changed files.
-      --suffix-keep-extension                Preserve the extension when using --suffix.
-      --syslog                               Use Syslog for logging
-      --syslog-facility string               Facility for syslog, eg KERN,USER,... (default &quot;DAEMON&quot;)
-      --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)
-      --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 (default &quot;hash&quot;)
-      --transfers int                        Number of file transfers to run in parallel. (default 4)
-  -u, --update                               Skip files that are newer on the destination.
-      --use-cookies                          Enable session cookiejar.
-      --use-json-log                         Use json log format.
-      --use-mmap                             Use mmap allocator (see docs).
-      --use-server-modtime                   Use server modified time instead of object metadata
-      --user-agent string                    Set the user-agent to a specified string. The default is rclone/ version (default &quot;rclone/v1.52.0&quot;)
-  -v, --verbose count                        Print lots more stuff (repeat for more)</code></pre>
-<h2 id="backend-flags">Backend Flags</h2>
-<p>These flags are available for every command. They control the backends and may be set in the config file.</p>
-<pre><code>      --acd-auth-url string                                      Auth server URL.
-      --acd-client-id string                                     Amazon Application Client ID.
-      --acd-client-secret string                                 Amazon Application Client Secret.
-      --acd-encoding MultiEncoder                                This sets the encoding for the backend. (default Slash,InvalidUtf8,Dot)
-      --acd-templink-threshold SizeSuffix                        Files &gt;= this size will be downloaded via their tempLink. (default 9G)
-      --acd-token-url string                                     Token server url.
-      --acd-upload-wait-per-gb Duration                          Additional time per GB to wait after a failed complete upload to see if it appears. (default 3m0s)
-      --alias-remote string                                      Remote or path to alias.
-      --azureblob-access-tier string                             Access tier of blob: hot, cool or archive.
-      --azureblob-account string                                 Storage Account Name (leave blank to use SAS URL or Emulator)
-      --azureblob-chunk-size SizeSuffix                          Upload chunk size (&lt;= 100MB). (default 4M)
-      --azureblob-disable-checksum                               Don&#39;t store MD5 checksum with object metadata.
-      --azureblob-encoding MultiEncoder                          This sets the encoding for the backend. (default Slash,BackSlash,Del,Ctl,RightPeriod,InvalidUtf8)
-      --azureblob-endpoint string                                Endpoint for the service
-      --azureblob-key string                                     Storage Account Key (leave blank to use SAS URL or Emulator)
-      --azureblob-list-chunk int                                 Size of blob list. (default 5000)
-      --azureblob-memory-pool-flush-time Duration                How often internal memory buffer pools will be flushed. (default 1m0s)
-      --azureblob-memory-pool-use-mmap                           Whether to use mmap buffers in internal memory pool.
-      --azureblob-sas-url string                                 SAS URL for container level access only
-      --azureblob-upload-cutoff SizeSuffix                       Cutoff for switching to chunked upload (&lt;= 256MB). (default 256M)
-      --azureblob-use-emulator                                   Uses local storage emulator if provided as &#39;true&#39; (leave blank if using real azure storage endpoint)
-      --b2-account string                                        Account ID or Application Key ID
-      --b2-chunk-size SizeSuffix                                 Upload chunk size. Must fit in memory. (default 96M)
-      --b2-disable-checksum                                      Disable checksums for large (&gt; upload cutoff) files
-      --b2-download-auth-duration Duration                       Time before the 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 MultiEncoder                                 This sets 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-test-mode string                                      A flag string for X-Bz-Test-Mode header for debugging.
-      --b2-upload-cutoff SizeSuffix                              Cutoff for switching to chunked upload. (default 200M)
-      --b2-versions                                              Include old versions in directory listings.
-      --box-box-config-file string                               Box App config.json location
-      --box-box-sub-type string                                   (default &quot;user&quot;)
-      --box-client-id string                                     Box App Client Id.
-      --box-client-secret string                                 Box App Client Secret
-      --box-commit-retries int                                   Max number of times to try committing a multipart file. (default 100)
-      --box-encoding MultiEncoder                                This sets the encoding for the backend. (default Slash,BackSlash,Del,Ctl,RightSpace,InvalidUtf8,Dot)
-      --box-root-folder-id string                                Fill in for rclone to use a non root folder as its starting point.
-      --box-upload-cutoff SizeSuffix                             Cutoff for switching to multipart upload (&gt;= 50MB). (default 50M)
-      --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 5M)
-      --cache-chunk-total-size SizeSuffix                        The total size that the chunks can take up on the local disk. (default 10G)
-      --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-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
-      --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 2G)
-      --chunker-fail-hard                                        Choose how chunker should handle files with missing or invalid chunks.
-      --chunker-hash-type string                                 Choose how chunker handles hash sums. All modes but &quot;none&quot; require metadata. (default &quot;md5&quot;)
-      --chunker-meta-format string                               Format of the metadata object or &quot;none&quot;. By default &quot;simplejson&quot;. (default &quot;simplejson&quot;)
-      --chunker-name-format string                               String format of chunk file names. (default &quot;*.rclone_chunk.###&quot;)
-      --chunker-remote string                                    Remote to chunk/unchunk.
-      --chunker-start-from int                                   Minimum valid chunk number. Usually 0 or 1. (default 1)
-  -L, --copy-links                                               Follow symlinks and copy the pointed to item.
-      --crypt-directory-name-encryption                          Option to either encrypt directory names or leave them intact. (default true)
-      --crypt-filename-encryption string                         How to encrypt the filenames. (default &quot;standard&quot;)
-      --crypt-password string                                    Password or pass phrase for encryption.
-      --crypt-password2 string                                   Password or pass phrase for salt. Optional but recommended.
-      --crypt-remote string                                      Remote to encrypt/decrypt.
-      --crypt-show-mapping                                       For all files listed show how the names encrypt.
-      --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 (e.g. file.doc to file.docx). This will confuse sync and reupload every time.
-      --drive-alternate-export                                   Use alternate export URLs for google documents export.,
-      --drive-auth-owner-only                                    Only consider files owned by the authenticated user.
-      --drive-chunk-size SizeSuffix                              Upload chunk size. Must a power of 2 &gt;= 256k. (default 8M)
-      --drive-client-id string                                   Google Application Client Id
-      --drive-client-secret string                               Google Application Client Secret
-      --drive-disable-http2                                      Disable drive using http2 (default true)
-      --drive-encoding MultiEncoder                              This sets the encoding for the backend. (default InvalidUtf8)
-      --drive-export-formats string                              Comma separated list of preferred formats for downloading Google docs. (default &quot;docx,xlsx,pptx,svg&quot;)
-      --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-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-root-folder-id string                              ID of the root folder
-      --drive-scope string                                       Scope that rclone should use when requesting access from drive.
-      --drive-server-side-across-configs                         Allow server side operations (eg copy) to work across different drive configs.
-      --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-size-as-quota                                      Show sizes as storage quota usage, not actual size.
-      --drive-skip-checksum-gphotos                              Skip MD5 checksum on Google photos and videos only.
-      --drive-skip-gdocs                                         Skip google documents in all listings.
-      --drive-skip-shortcuts                                     If set skip shortcut files
-      --drive-stop-on-upload-limit                               Make upload limit errors be fatal
-      --drive-team-drive string                                  ID of the Team Drive
-      --drive-trashed-only                                       Only show files that are in the trash.
-      --drive-upload-cutoff SizeSuffix                           Cutoff for switching to chunked upload (default 8M)
-      --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-chunk-size SizeSuffix                            Upload chunk size. (&lt; 150M). (default 48M)
-      --dropbox-client-id string                                 Dropbox App Client Id
-      --dropbox-client-secret string                             Dropbox App Client Secret
-      --dropbox-encoding MultiEncoder                            This sets the encoding for the backend. (default Slash,BackSlash,Del,RightSpace,InvalidUtf8,Dot)
-      --dropbox-impersonate string                               Impersonate this user when using a business account.
-      --fichier-api-key string                                   Your API Key, get it from https://1fichier.com/console/params.pl
-      --fichier-encoding MultiEncoder                            This sets the encoding for the backend. (default Slash,LtGt,DoubleQuote,SingleQuote,BackQuote,Dollar,BackSlash,Del,Ctl,LeftSpace,RightSpace,InvalidUtf8,Dot)
-      --fichier-shared-folder string                             If you want to download a shared folder, add this parameter
-      --ftp-concurrency int                                      Maximum number of FTP simultaneous connections, 0 for unlimited
-      --ftp-disable-epsv                                         Disable using EPSV even if server advertises support
-      --ftp-encoding MultiEncoder                                This sets the encoding for the backend. (default Slash,Del,Ctl,RightSpace,Dot)
-      --ftp-host string                                          FTP host to connect to
-      --ftp-no-check-certificate                                 Do not verify the TLS certificate of the server
-      --ftp-pass string                                          FTP password
-      --ftp-port string                                          FTP port, leave blank to use default (21)
-      --ftp-tls                                                  Use FTP over TLS (Implicit)
-      --ftp-user string                                          FTP username, leave blank for current username, $USER
-      --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                                     Google Application Client Id
-      --gcs-client-secret string                                 Google Application Client Secret
-      --gcs-encoding MultiEncoder                                This sets the encoding for the backend. (default Slash,CrLf,InvalidUtf8,Dot)
-      --gcs-location string                                      Location for the newly created buckets.
-      --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.
-      --gphotos-client-id string                                 Google Application Client Id
-      --gphotos-client-secret string                             Google Application Client Secret
-      --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)
-      --http-headers CommaSepList                                Set HTTP headers for all transactions
-      --http-no-head                                             Don&#39;t use HEAD requests to find file sizes in dir listing
-      --http-no-slash                                            Set this if the site doesn&#39;t end directories with /
-      --http-url string                                          URL of http host to connect to
-      --hubic-chunk-size SizeSuffix                              Above this size files will be chunked into a _segments container. (default 5G)
-      --hubic-client-id string                                   Hubic Client Id
-      --hubic-client-secret string                               Hubic Client Secret
-      --hubic-encoding MultiEncoder                              This sets the encoding for the backend. (default Slash,InvalidUtf8)
-      --hubic-no-chunk                                           Don&#39;t chunk files during streaming upload.
-      --jottacloud-encoding MultiEncoder                         This sets 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 10M)
-      --jottacloud-trashed-only                                  Only show files that are in the trash.
-      --jottacloud-unlink                                        Remove existing public link to file/folder with link command rather than creating.
-      --jottacloud-upload-resume-limit SizeSuffix                Files bigger than this can be resumed if the upload fail&#39;s. (default 10M)
-      --koofr-encoding MultiEncoder                              This sets the encoding for the backend. (default Slash,BackSlash,Del,Ctl,InvalidUtf8,Dot)
-      --koofr-endpoint string                                    The Koofr API endpoint to use (default &quot;https://app.koofr.net&quot;)
-      --koofr-mountid string                                     Mount ID of the mount to use. If omitted, the primary mount is used.
-      --koofr-password string                                    Your Koofr password for rclone (generate one at https://app.koofr.net/app/admin/preferences/password)
-      --koofr-setmtime                                           Does the backend support setting modification time. Set this to false if you use a mount ID that points to a Dropbox or Amazon Drive backend. (default true)
-      --koofr-user string                                        Your Koofr user name
-  -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-encoding MultiEncoder                              This sets 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-sparse                                          Disable sparse files for multi-thread downloads
-      --local-no-unicode-normalization                           Don&#39;t apply unicode normalization to paths and filenames (Deprecated)
-      --local-nounc string                                       Disable UNC (long path names) conversion on Windows
-      --mailru-check-hash                                        What should copy do if file checksum is mismatched or invalid (default true)
-      --mailru-encoding MultiEncoder                             This sets the encoding for the backend. (default Slash,LtGt,DoubleQuote,Colon,Question,Asterisk,Pipe,BackSlash,Del,Ctl,InvalidUtf8,Dot)
-      --mailru-pass string                                       Password
-      --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 3G)
-      --mailru-speedup-max-memory SizeSuffix                     Files larger than the size given below will always be hashed on disk. (default 32M)
-      --mailru-user string                                       User name (usually email)
-      --mega-debug                                               Output more debug from Mega.
-      --mega-encoding MultiEncoder                               This sets 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.
-      --mega-user string                                         User name
-  -x, --one-file-system                                          Don&#39;t cross filesystem boundaries (unix/macOS only).
-      --onedrive-chunk-size SizeSuffix                           Chunk size to upload files with - must be multiple of 320k (327,680 bytes). (default 10M)
-      --onedrive-client-id string                                Microsoft App Client Id
-      --onedrive-client-secret string                            Microsoft App Client Secret
-      --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 MultiEncoder                           This sets the encoding for the backend. (default Slash,LtGt,DoubleQuote,Colon,Question,Asterisk,Pipe,Hash,Percent,BackSlash,Del,Ctl,LeftSpace,LeftTilde,RightSpace,RightPeriod,InvalidUtf8,Dot)
-      --onedrive-expose-onenote-files                            Set to make OneNote files show up in directory listings.
-      --onedrive-server-side-across-configs                      Allow server side operations (eg copy) to work across different onedrive configs.
-      --opendrive-chunk-size SizeSuffix                          Files will be uploaded in chunks this size. (default 10M)
-      --opendrive-encoding MultiEncoder                          This sets the encoding for the backend. (default Slash,LtGt,DoubleQuote,Colon,Question,Asterisk,Pipe,BackSlash,LeftSpace,LeftCrLfHtVt,RightSpace,RightCrLfHtVt,InvalidUtf8,Dot)
-      --opendrive-password string                                Password.
-      --opendrive-username string                                Username
-      --pcloud-client-id string                                  Pcloud App Client Id
-      --pcloud-client-secret string                              Pcloud App Client Secret
-      --pcloud-encoding MultiEncoder                             This sets the encoding for the backend. (default Slash,BackSlash,Del,Ctl,InvalidUtf8,Dot)
-      --pcloud-root-folder-id string                             Fill in for rclone to use a non root folder as its starting point. (default &quot;d0&quot;)
-      --premiumizeme-encoding MultiEncoder                       This sets the encoding for the backend. (default Slash,DoubleQuote,BackSlash,Del,Ctl,InvalidUtf8,Dot)
-      --putio-encoding MultiEncoder                              This sets the encoding for the backend. (default Slash,BackSlash,Del,Ctl,InvalidUtf8,Dot)
-      --qingstor-access-key-id string                            QingStor Access Key ID
-      --qingstor-chunk-size SizeSuffix                           Chunk size to use for uploading. (default 4M)
-      --qingstor-connection-retries int                          Number of connection retries. (default 3)
-      --qingstor-encoding MultiEncoder                           This sets 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. Only applies if access_key_id and secret_access_key is blank.
-      --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 200M)
-      --qingstor-zone string                                     Zone to connect to.
-      --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 5M)
-      --s3-copy-cutoff SizeSuffix                                Cutoff for switching to multipart copy (default 5G)
-      --s3-disable-checksum                                      Don&#39;t store MD5 checksum with object metadata
-      --s3-encoding MultiEncoder                                 This sets 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-location-constraint string                            Location constraint - must be set to match the Region.
-      --s3-memory-pool-flush-time Duration                       How often internal memory buffer pools will be flushed. (default 1m0s)
-      --s3-memory-pool-use-mmap                                  Whether to use mmap buffers in internal memory pool.
-      --s3-provider string                                       Choose your S3 provider.
-      --s3-region string                                         Region to connect to.
-      --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-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                               If using SSE-C you must provide the secret encryption key used to encrypt/decrypt your data.
-      --s3-sse-customer-key-md5 string                           If using SSE-C you must provide the secret encryption key MD5 checksum.
-      --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. (default 4)
-      --s3-upload-cutoff SizeSuffix                              Cutoff for switching to chunked upload (default 200M)
-      --s3-use-accelerate-endpoint                               If true use the AWS S3 accelerated endpoint.
-      --s3-v2-auth                                               If true use v2 authentication.
-      --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-encoding MultiEncoder                            This sets the encoding for the backend. (default Slash,DoubleQuote,BackSlash,Ctl,InvalidUtf8)
-      --seafile-library string                                   Name of the library. Leave blank to access all non-encrypted libraries.
-      --seafile-library-key string                               Library password (for encrypted libraries only). Leave blank if you pass it through the command line.
-      --seafile-pass string                                      Password
-      --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-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-key-file string                                     Path to PEM-encoded private key file, leave blank or set key-use-agent to use ssh-agent.
-      --sftp-key-file-pass string                                The passphrase to decrypt the PEM-encoded private key file.
-      --sftp-key-pem string                                      Raw PEM-encoded private key, If specified, will override key_file parameter.
-      --sftp-key-use-agent                                       When set forces the usage of the ssh-agent.
-      --sftp-md5sum-command string                               The command used to read md5 hashes. Leave blank for autodetect.
-      --sftp-pass string                                         SSH password, leave blank to use ssh-agent.
-      --sftp-path-override string                                Override path used by SSH connection.
-      --sftp-port string                                         SSH port, leave blank to use default (22)
-      --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. Leave blank for autodetect.
-      --sftp-skip-links                                          Set to skip any symlinks and any other non regular files.
-      --sftp-use-insecure-cipher                                 Enable the use of insecure ciphers and key exchange methods.
-      --sftp-user string                                         SSH username, leave blank for current username, ncw
-      --sharefile-chunk-size SizeSuffix                          Upload chunk size. Must a power of 2 &gt;= 256k. (default 64M)
-      --sharefile-encoding MultiEncoder                          This sets 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-upload-cutoff SizeSuffix                       Cutoff for switching to multipart upload. (default 128M)
-      --skip-links                                               Don&#39;t warn about skipped symlinks.
-      --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-encoding MultiEncoder                          This sets 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 into a _segments container. (default 5G)
-      --swift-domain string                                      User domain - optional (v3 auth) (OS_USER_DOMAIN_NAME)
-      --swift-encoding MultiEncoder                              This sets 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-key string                                         API key or password (OS_PASSWORD).
-      --swift-no-chunk                                           Don&#39;t chunk files during streaming upload.
-      --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-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).
-      --tardigrade-access-grant string                           Access Grant.
-      --tardigrade-api-key string                                API Key.
-      --tardigrade-passphrase string                             Encryption Passphrase. To access existing objects enter passphrase used for uploading.
-      --tardigrade-provider string                               Choose an authentication method. (default &quot;existing&quot;)
-      --tardigrade-satellite-address &lt;nodeid&gt;@&lt;address&gt;:&lt;port&gt;   Satellite Address. Custom satellite address should match the format: &lt;nodeid&gt;@&lt;address&gt;:&lt;port&gt;. (default &quot;us-central-1.tardigrade.io&quot;)
-      --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). This option is only useful when a path preserving policy is used. (default 120)
-      --union-create-policy string                               Policy to choose upstream on CREATE category. (default &quot;epmfs&quot;)
-      --union-search-policy string                               Policy to choose upstream on SEARCH category. (default &quot;ff&quot;)
-      --union-upstreams string                                   List of space separated upstreams.
-      --webdav-bearer-token string                               Bearer token instead of user/pass (eg a Macaroon)
-      --webdav-bearer-token-command string                       Command to run to get a bearer token
-      --webdav-pass string                                       Password.
-      --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-client-id string                                  Yandex Client Id
-      --yandex-client-secret string                              Yandex Client Secret
-      --yandex-encoding MultiEncoder                             This sets the encoding for the backend. (default Slash,Del,Ctl,InvalidUtf8,Dot)
-      --yandex-unlink                                            Remove existing public link to file/folder with link command rather than creating.</code></pre>
-<h2 id="fichier">1Fichier</h2>
-<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, eg <code>remote:directory/subdirectory</code>.</p>
-<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/ **
+<p>{ "speed": average speed in bytes/sec since start of the process, "bytes": total transferred bytes since the start of the process, "errors": number of errors, "fatalError": whether there has been at least one FatalError, "retryError": whether there has been at least one non-NoRetryError, "checks": number of checked files, "transfers": number of transferred files, "deletes" : number of deleted files, "renames" : number of renamed files, "transferTime" : total time spent on running jobs, "elapsedTime": time in seconds since the start of the process, "lastError": last occurred error, "transferring": an array of currently active file transfers: [ { "bytes": total transferred bytes for this file, "eta": estimated time in seconds until file transfer completion "name": name of the file, "percentage": progress of the file transfer in percent, "speed": average speed over the whole transfer in bytes/sec, "speedAvg": current speed in bytes/sec as an exponentially weighted moving average, "size": size of the file in bytes } ], "checking": an array of names of currently active file checks [] }</p>
+<pre><code>Values for &quot;transferring&quot;, &quot;checking&quot; and &quot;lastError&quot; are only assigned if data is available.
+The value for &quot;eta&quot; is null if an eta cannot be determined.
+
+### core/stats-delete: Delete stats group. {#core-stats-delete}
+
+This deletes entire stats group
+
+Parameters
+
+- group - name of the stats group (string)
+
+### core/stats-reset: Reset stats. {#core-stats-reset}
+
+This clears counters, errors and finished transfers for all stats or specific 
+stats group if group is provided.
+
+Parameters
+
+- group - name of the stats group (string)
+
+### core/transferred: Returns stats about completed transfers. {#core-transferred}
+
+This returns stats about completed transfers:
+
+    rclone rc core/transferred
+
+If group is not provided then completed transfers for all groups will be
+returned.
+
+Note only the last 100 completed transfers are returned.
+
+Parameters
+
+- group - name of the stats group (string)
+
+Returns the following values:</code></pre>
+<p>{ "transferred": an array of completed transfers (including failed ones): [ { "name": name of the file, "size": size of the file in bytes, "bytes": total transferred bytes for this file, "checked": if the transfer is only checked (skipped, deleted), "timestamp": integer representing millisecond unix epoch, "error": string description of the error (empty if successful), "jobid": id of the job that this transfer belongs to } ] }</p>
+<pre><code>
+### core/version: Shows the current version of rclone and the go runtime. {#core-version}
+
+This shows the current version of go and the go runtime
+
+- version - rclone version, eg &quot;v1.53.0&quot;
+- decomposed - version number as [major, minor, patch]
+- isGit - boolean - true if this was compiled from the git version
+- isBeta - boolean - true if this is a beta version
+- os - OS in use as according to Go
+- arch - cpu architecture in use according to Go
+- goVersion - version of Go runtime in use
+
+### debug/set-block-profile-rate: Set runtime.SetBlockProfileRate for blocking profiling. {#debug-set-block-profile-rate}
+
+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.
+
+To include every blocking event in the profile, pass rate = 1. To turn
+off profiling entirely, pass rate &lt;= 0.
+
+After calling this you can use this to see the blocking profile:
+
+    go tool pprof http://localhost:5572/debug/pprof/block
+
+Parameters
+
+- rate - int
+
+### debug/set-mutex-profile-fraction: Set runtime.SetMutexProfileFraction for mutex profiling. {#debug-set-mutex-profile-fraction}
+
+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.
+
+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.)
+
+Once this is set you can look use this to profile the mutex contention:
+
+    go tool pprof http://localhost:5572/debug/pprof/mutex
+
+Parameters
+
+- rate - int
+
+Results
+
+- previousRate - int
+
+### job/list: Lists the IDs of the running jobs {#job-list}
+
+Parameters - None
+
+Results
+
+- jobids - array of integer job ids
+
+### job/status: Reads the status of the job ID {#job-status}
+
+Parameters
+
+- jobid - id of the job (integer)
+
+Results
+
+- finished - boolean
+- duration - time in seconds that the job ran for
+- endTime - time the job finished (eg &quot;2018-10-26T18:50:20.528746884+01:00&quot;)
+- error - error from the job or empty string for no error
+- finished - boolean whether the job has finished or not
+- id - as passed in above
+- startTime - time the job started (eg &quot;2018-10-26T18:50:20.528336039+01:00&quot;)
+- success - boolean - true for success false otherwise
+- output - output of the job as would have been returned if called synchronously
+- progress - output of the progress related to the underlying job
+
+### job/stop: Stop the running job {#job-stop}
+
+Parameters
+
+- jobid - id of the job (integer)
+
+### mount/listmounts: Show current mount points {#mount-listmounts}
+
+This shows currently mounted points, which can be used for performing an unmount
+
+This takes no parameters and returns
+
+- mountPoints: list of current mount points
+
+Eg
+
+    rclone rc mount/listmounts
+
+**Authentication is required for this call.**
+
+### mount/mount: Create a new mount point {#mount-mount}
+
+rclone allows Linux, FreeBSD, macOS and Windows to mount any of
+Rclone&#39;s cloud storage systems as a file system with FUSE.
+
+If no mountType is provided, the priority is given as follows: 1. mount 2.cmount 3.mount2
+
+This takes the following parameters
+
+- fs - a remote path to be mounted (required)
+- mountPoint: valid path on the local machine (required)
+- mountType: One of the values (mount, cmount, mount2) specifies the mount implementation to use
+- mountOpt: a JSON object with Mount options in.
+- vfsOpt: a JSON object with VFS options in.
+
+Eg
+
+    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;
+
+The vfsOpt are as described in options/get and can be seen in the the
+&quot;vfs&quot; section when running and the mountOpt can be seen in the &quot;mount&quot; section.
+
+    rclone rc options/get
+
+**Authentication is required for this call.**
+
+### mount/types: Show all possible mount types {#mount-types}
+
+This shows all possible mount types and returns them as a list.
+
+This takes no parameters and returns
+
+- mountTypes: list of mount types
+
+The mount types are strings like &quot;mount&quot;, &quot;mount2&quot;, &quot;cmount&quot; and can
+be passed to mount/mount as the mountType parameter.
+
+Eg
+
+    rclone rc mount/types
+
+**Authentication is required for this call.**
+
+### mount/unmount: Unmount selected active mount {#mount-unmount}
+
+rclone allows Linux, FreeBSD, macOS and Windows to
+mount any of Rclone&#39;s cloud storage systems as a file system with
+FUSE.
+
+This takes the following parameters
+
+- mountPoint: valid path on the local machine where the mount was created (required)
+
+Eg
+
+    rclone rc mount/unmount mountPoint=/home/&lt;user&gt;/mountPoint
+
+**Authentication is required for this call.**
+
+### mount/unmountall: Show current mount points {#mount-unmountall}
+
+This shows currently mounted points, which can be used for performing an unmount
+
+This takes no parameters and returns error if unmount does not succeed.
+
+Eg
+
+    rclone rc mount/unmountall
+
+**Authentication is required for this call.**
+
+### operations/about: Return the space used on the remote {#operations-about}
+
+This takes the following parameters
+
+- fs - a remote name string eg &quot;drive:&quot;
+
+The result is as returned from rclone about --json
+
+See the [about command](https://rclone.org/commands/rclone_size/) command for more information on the above.
+
+**Authentication is required for this call.**
+
+### operations/cleanup: Remove trashed files in the remote or path {#operations-cleanup}
+
+This takes the following parameters
+
+- fs - a remote name string eg &quot;drive:&quot;
+
+See the [cleanup command](https://rclone.org/commands/rclone_cleanup/) command for more information on the above.
+
+**Authentication is required for this call.**
+
+### operations/copyfile: Copy a file from source remote to destination remote {#operations-copyfile}
+
+This takes the following parameters
+
+- srcFs - a remote name string eg &quot;drive:&quot; for the source
+- srcRemote - a path within that remote eg &quot;file.txt&quot; for the source
+- dstFs - a remote name string eg &quot;drive2:&quot; for the destination
+- dstRemote - a path within that remote eg &quot;file2.txt&quot; for the destination
+
+**Authentication is required for this call.**
+
+### operations/copyurl: Copy the URL to the object {#operations-copyurl}
+
+This takes the following parameters
+
+- fs - a remote name string eg &quot;drive:&quot;
+- remote - a path within that remote eg &quot;dir&quot;
+- url - string, URL to read from
+ - autoFilename - boolean, set to true to retrieve destination file name from url
+See the [copyurl command](https://rclone.org/commands/rclone_copyurl/) command for more information on the above.
+
+**Authentication is required for this call.**
+
+### operations/delete: Remove files in the path {#operations-delete}
+
+This takes the following parameters
+
+- fs - a remote name string eg &quot;drive:&quot;
+
+See the [delete command](https://rclone.org/commands/rclone_delete/) command for more information on the above.
+
+**Authentication is required for this call.**
+
+### operations/deletefile: Remove the single file pointed to {#operations-deletefile}
+
+This takes the following parameters
+
+- fs - a remote name string eg &quot;drive:&quot;
+- remote - a path within that remote eg &quot;dir&quot;
+
+See the [deletefile command](https://rclone.org/commands/rclone_deletefile/) command for more information on the above.
+
+**Authentication is required for this call.**
+
+### operations/fsinfo: Return information about the remote {#operations-fsinfo}
+
+This takes the following parameters
+
+- fs - a remote name string eg &quot;drive:&quot;
+
+This returns info about the remote passed in;
+</code></pre>
+<p>{ // optional features and whether they are available or not "Features": { "About": true, "BucketBased": false, "CanHaveEmptyDirectories": true, "CaseInsensitive": false, "ChangeNotify": false, "CleanUp": false, "Copy": false, "DirCacheFlush": false, "DirMove": true, "DuplicateFiles": false, "GetTier": false, "ListR": false, "MergeDirs": false, "Move": true, "OpenWriterAt": true, "PublicLink": false, "Purge": true, "PutStream": true, "PutUnchecked": false, "ReadMimeType": false, "ServerSideAcrossConfigs": false, "SetTier": false, "SetWrapper": false, "UnWrap": false, "WrapFs": false, "WriteMimeType": false }, // Names of hashes available "Hashes": [ "MD5", "SHA-1", "DropboxHash", "QuickXorHash" ], "Name": "local", // Name as created "Precision": 1, // Precision of timestamps in ns "Root": "/", // Path as created "String": "Local file system at /" // how the remote will appear in logs }</p>
+<pre><code>
+This command does not have a command line equivalent so use this instead:
+
+    rclone rc --loopback operations/fsinfo fs=remote:
+
+### operations/list: List the given remote and path in JSON format {#operations-list}
+
+This takes the following parameters
+
+- fs - a remote name string eg &quot;drive:&quot;
+- remote - a path within that remote eg &quot;dir&quot;
+- opt - a dictionary of options to control the listing (optional)
+    - recurse - If set recurse directories
+    - noModTime - If set return modification time
+    - showEncrypted -  If set show decrypted names
+    - showOrigIDs - If set show the IDs for each item if known
+    - showHash - If set return a dictionary of hashes
+
+The result is
+
+- list
+    - This is an array of objects as described in the lsjson command
+
+See the [lsjson command](https://rclone.org/commands/rclone_lsjson/) for more information on the above and examples.
+
+**Authentication is required for this call.**
+
+### operations/mkdir: Make a destination directory or container {#operations-mkdir}
+
+This takes the following parameters
+
+- fs - a remote name string eg &quot;drive:&quot;
+- remote - a path within that remote eg &quot;dir&quot;
+
+See the [mkdir command](https://rclone.org/commands/rclone_mkdir/) command for more information on the above.
+
+**Authentication is required for this call.**
+
+### operations/movefile: Move a file from source remote to destination remote {#operations-movefile}
+
+This takes the following parameters
+
+- srcFs - a remote name string eg &quot;drive:&quot; for the source
+- srcRemote - a path within that remote eg &quot;file.txt&quot; for the source
+- dstFs - a remote name string eg &quot;drive2:&quot; for the destination
+- dstRemote - a path within that remote eg &quot;file2.txt&quot; for the destination
+
+**Authentication is required for this call.**
+
+### operations/publiclink: Create or retrieve a public link to the given file or folder. {#operations-publiclink}
+
+This takes the following parameters
+
+- fs - a remote name string eg &quot;drive:&quot;
+- remote - a path within that remote eg &quot;dir&quot;
+- unlink - boolean - if set removes the link rather than adding it (optional)
+- expire - string - the expiry time of the link eg &quot;1d&quot; (optional)
+
+Returns
+
+- url - URL of the resource
+
+See the [link command](https://rclone.org/commands/rclone_link/) command for more information on the above.
+
+**Authentication is required for this call.**
+
+### operations/purge: Remove a directory or container and all of its contents {#operations-purge}
+
+This takes the following parameters
+
+- fs - a remote name string eg &quot;drive:&quot;
+- remote - a path within that remote eg &quot;dir&quot;
+
+See the [purge command](https://rclone.org/commands/rclone_purge/) command for more information on the above.
+
+**Authentication is required for this call.**
+
+### operations/rmdir: Remove an empty directory or container {#operations-rmdir}
+
+This takes the following parameters
+
+- fs - a remote name string eg &quot;drive:&quot;
+- remote - a path within that remote eg &quot;dir&quot;
+
+See the [rmdir command](https://rclone.org/commands/rclone_rmdir/) command for more information on the above.
+
+**Authentication is required for this call.**
+
+### operations/rmdirs: Remove all the empty directories in the path {#operations-rmdirs}
+
+This takes the following parameters
+
+- fs - a remote name string eg &quot;drive:&quot;
+- remote - a path within that remote eg &quot;dir&quot;
+- leaveRoot - boolean, set to true not to delete the root
+
+See the [rmdirs command](https://rclone.org/commands/rclone_rmdirs/) command for more information on the above.
+
+**Authentication is required for this call.**
+
+### operations/size: Count the number of bytes and files in remote {#operations-size}
+
+This takes the following parameters
+
+- fs - a remote name string eg &quot;drive:path/to/dir&quot;
+
+Returns
+
+- count - number of files
+- bytes - number of bytes in those files
+
+See the [size command](https://rclone.org/commands/rclone_size/) command for more information on the above.
+
+**Authentication is required for this call.**
+
+### operations/uploadfile: Upload file using multiform/form-data {#operations-uploadfile}
+
+This takes the following parameters
+
+- fs - a remote name string eg &quot;drive:&quot;
+- remote - a path within that remote eg &quot;dir&quot;
+- each part in body represents a file to be uploaded
+See the [uploadfile command](https://rclone.org/commands/rclone_uploadfile/) command for more information on the above.
+
+**Authentication is required for this call.**
+
+### options/blocks: List all the option blocks {#options-blocks}
+
+Returns
+- options - a list of the options block names
+
+### options/get: Get all the options {#options-get}
+
+Returns an object where keys are option block names and values are an
+object with the current option values in.
+
+This shows the internal names of the option within rclone which should
+map to the external options very easily with a few exceptions.
+
+### options/set: Set an option {#options-set}
+
+Parameters
+
+- option block name containing an object with
+  - key: value
+
+Repeated as often as required.
+
+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.
+
+For example:
+
+This sets DEBUG level logs (-vv)
+
+    rclone rc options/set --json &#39;{&quot;main&quot;: {&quot;LogLevel&quot;: 8}}&#39;
+
+And this sets INFO level logs (-v)
+
+    rclone rc options/set --json &#39;{&quot;main&quot;: {&quot;LogLevel&quot;: 7}}&#39;
+
+And this sets NOTICE level logs (normal without -v)
+
+    rclone rc options/set --json &#39;{&quot;main&quot;: {&quot;LogLevel&quot;: 6}}&#39;
+
+### pluginsctl/addPlugin: Add a plugin using url {#pluginsctl-addPlugin}
+
+used for adding a plugin to the webgui
+
+This takes the following parameters
+
+- url: http url of the github repo where the plugin is hosted (http://github.com/rclone/rclone-webui-react)
+
+Eg
+
+   rclone rc pluginsctl/addPlugin
+
+**Authentication is required for this call.**
+
+### pluginsctl/getPluginsForType: Get plugins with type criteria {#pluginsctl-getPluginsForType}
+
+This shows all possible plugins by a mime type
+
+This takes the following parameters
+
+- type: supported mime type by a loaded plugin eg (video/mp4, audio/mp3)
+- pluginType: filter plugins based on their type eg (DASHBOARD, FILE_HANDLER, TERMINAL) 
+
+and returns
+
+- loadedPlugins: list of current production plugins
+- testPlugins: list of temporarily loaded development plugins, usually running on a different server.
+
+Eg
+
+   rclone rc pluginsctl/getPluginsForType type=video/mp4
+
+**Authentication is required for this call.**
+
+### pluginsctl/listPlugins: Get the list of currently loaded plugins {#pluginsctl-listPlugins}
+
+This allows you to get the currently enabled plugins and their details.
+
+This takes no parameters and returns
+
+- loadedPlugins: list of current production plugins
+- testPlugins: list of temporarily loaded development plugins, usually running on a different server.
+
+Eg
+
+   rclone rc pluginsctl/listPlugins
+
+**Authentication is required for this call.**
+
+### pluginsctl/listTestPlugins: Show currently loaded test plugins {#pluginsctl-listTestPlugins}
+
+allows listing of test plugins with the rclone.test set to true in package.json of the plugin
+
+This takes no parameters and returns
+
+- loadedTestPlugins: list of currently available test plugins
+
+Eg
+
+    rclone rc pluginsctl/listTestPlugins
+
+**Authentication is required for this call.**
+
+### pluginsctl/removePlugin: Remove a loaded plugin {#pluginsctl-removePlugin}
+
+This allows you to remove a plugin using it&#39;s name
+
+This takes parameters
+
+- name: name of the plugin in the format &lt;author&gt;/&lt;plugin_name&gt;
+
+Eg
+
+   rclone rc pluginsctl/removePlugin name=rclone/video-plugin
+
+**Authentication is required for this call.**
+
+### pluginsctl/removeTestPlugin: Remove  a test plugin {#pluginsctl-removeTestPlugin}
+
+This allows you to remove a plugin using it&#39;s name
+
+This takes the following parameters
+
+- name: name of the plugin in the format &lt;author&gt;/&lt;plugin_name&gt;
+
+Eg
+
+    rclone rc pluginsctl/removeTestPlugin name=rclone/rclone-webui-react
+
+**Authentication is required for this call.**
+
+### rc/error: This returns an error {#rc-error}
+
+This returns an error with the input as part of its error string.
+Useful for testing error handling.
+
+### rc/list: List all the registered remote control commands {#rc-list}
+
+This lists all the registered remote control commands as a JSON map in
+the commands response.
+
+### rc/noop: Echo the input to the output parameters {#rc-noop}
+
+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.
+
+### rc/noopauth: Echo the input to the output parameters requiring auth {#rc-noopauth}
+
+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.
+
+**Authentication is required for this call.**
+
+### sync/copy: copy a directory from source remote to destination remote {#sync-copy}
+
+This takes the following parameters
+
+- srcFs - a remote name string eg &quot;drive:src&quot; for the source
+- dstFs - a remote name string eg &quot;drive:dst&quot; for the destination
+
+
+See the [copy command](https://rclone.org/commands/rclone_copy/) command for more information on the above.
+
+**Authentication is required for this call.**
+
+### sync/move: move a directory from source remote to destination remote {#sync-move}
+
+This takes the following parameters
+
+- srcFs - a remote name string eg &quot;drive:src&quot; for the source
+- dstFs - a remote name string eg &quot;drive:dst&quot; for the destination
+- deleteEmptySrcDirs - delete empty src directories if set
+
+
+See the [move command](https://rclone.org/commands/rclone_move/) command for more information on the above.
+
+**Authentication is required for this call.**
+
+### sync/sync: sync a directory from source remote to destination remote {#sync-sync}
+
+This takes the following parameters
+
+- srcFs - a remote name string eg &quot;drive:src&quot; for the source
+- dstFs - a remote name string eg &quot;drive:dst&quot; for the destination
+
+
+See the [sync command](https://rclone.org/commands/rclone_sync/) command for more information on the above.
+
+**Authentication is required for this call.**
+
+### vfs/forget: Forget files or directories in the directory cache. {#vfs-forget}
+
+This forgets the paths in the directory cache causing them to be
+re-read from the remote when needed.
+
+If no paths are passed in then it will forget all the paths in the
+directory cache.
+
+    rclone rc vfs/forget
+
+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, eg
+
+    rclone rc vfs/forget file=hello file2=goodbye dir=home/junk
+ 
+This command takes an &quot;fs&quot; 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 &quot;fs&quot; parameter
+must be supplied.
+
+### vfs/list: List active VFSes. {#vfs-list}
+
+This lists the active VFSes.
+
+It returns a list under the key &quot;vfses&quot; where the values are the VFS
+names that could be passed to the other VFS commands in the &quot;fs&quot;
+parameter.
+
+### vfs/poll-interval: Get the status or update the value of the poll-interval option. {#vfs-poll-interval}
+
+Without any parameter given this returns the current status of the
+poll-interval setting.
+
+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.
+
+    rclone rc vfs/poll-interval interval=5m
+
+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.
+
+The new poll-interval value will only be active when the timeout is
+not reached.
+
+If poll-interval is updated or disabled temporarily, some changes
+might not get picked up by the polling function, depending on the
+used remote.
+ 
+This command takes an &quot;fs&quot; 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 &quot;fs&quot; parameter
+must be supplied.
+
+### vfs/refresh: Refresh the directory cache. {#vfs-refresh}
+
+This reads the directories for the specified paths and freshens the
+directory cache.
+
+If no paths are passed in then it will refresh the root directory.
+
+    rclone rc vfs/refresh
+
+Otherwise pass directories in as dir=path. Any parameter key
+starting with dir will refresh that directory, eg
+
+    rclone rc vfs/refresh dir=home/junk dir2=data/misc
+
+If the parameter recursive=true is given the whole directory tree
+will get refreshed. This refresh will use --fast-list if enabled.
+ 
+This command takes an &quot;fs&quot; 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 &quot;fs&quot; parameter
+must be supplied.
+
+
+
+## Accessing the remote control via HTTP
+
+Rclone implements a simple HTTP based protocol.
+
+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.
+
+All calls must made using POST.
+
+The input objects can be supplied using URL parameters, POST
+parameters or by supplying &quot;Content-Type: application/json&quot; and a JSON
+blob in the body.  There are examples of these below using `curl`.
+
+The response will be a JSON blob in the body of the response.  This is
+formatted to be reasonably human readable.
+
+### Error returns
+
+If an error occurs then there will be an HTTP error status (eg 500)
+and the body of the response will contain a JSON encoded error object,
+eg
+</code></pre>
+<p>{ "error": "Expecting string value for key "remote" (was float64)", "input": { "fs": "/tmp", "remote": 3 }, "status": 400 "path": "operations/rmdir", }</p>
+<pre><code>
+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
+
+### CORS
+
+The sever implements basic CORS support and allows all origins for that.
+The response to a preflight OPTIONS request will echo the requested &quot;Access-Control-Request-Headers&quot; back.
+
+### Using POST with URL parameters only
+</code></pre>
+<p>curl -X POST 'http://localhost:5572/rc/noop?potato=1&amp;sausage=2'</p>
+<pre><code>
+Response
+</code></pre>
+<p>{ "potato": "1", "sausage": "2" }</p>
+<pre><code>
+Here is what an error response looks like:
+</code></pre>
+<p>curl -X POST 'http://localhost:5572/rc/error?potato=1&amp;sausage=2'</p>
+<pre><code></code></pre>
+<p>{ "error": "arbitrary error on input map[potato:1 sausage:2]", "input": { "potato": "1", "sausage": "2" } }</p>
+<pre><code>
+Note that curl doesn&#39;t return errors to the shell unless you use the `-f` option
+</code></pre>
+<p>$ curl -f -X POST 'http://localhost:5572/rc/error?potato=1&amp;sausage=2' curl: (22) The requested URL returned error: 400 Bad Request $ echo $? 22</p>
+<pre><code>
+### Using POST with a form
+</code></pre>
+<p>curl --data "potato=1" --data "sausage=2" http://localhost:5572/rc/noop</p>
+<pre><code>
+Response
+</code></pre>
+<p>{ "potato": "1", "sausage": "2" }</p>
+<pre><code>
+Note that you can combine these with URL parameters too with the POST
+parameters taking precedence.
+</code></pre>
+<p>curl --data "potato=1" --data "sausage=2" "http://localhost:5572/rc/noop?rutabaga=3&amp;sausage=4"</p>
+<pre><code>
+Response
+</code></pre>
+<p>{ "potato": "1", "rutabaga": "3", "sausage": "4" }</p>
+<pre><code>
+### Using POST with a JSON blob
+</code></pre>
+<p>curl -H "Content-Type: application/json" -X POST -d '{"potato":2,"sausage":1}' http://localhost:5572/rc/noop</p>
+<pre><code>
+response
+</code></pre>
+<p>{ "password": "xyz", "username": "xyz" }</p>
+<pre><code>
+This can be combined with URL parameters too if required.  The JSON
+blob takes precedence.
+</code></pre>
+<p>curl -H "Content-Type: application/json" -X POST -d '{"potato":2,"sausage":1}' 'http://localhost:5572/rc/noop?rutabaga=3&amp;potato=4'</p>
+<pre><code></code></pre>
+<p>{ "potato": 2, "rutabaga": "3", "sausage": 1 }</p>
+<pre><code>
+## Debugging rclone with pprof ##
+
+If you use the `--rc` flag this will also enable the use of the go
+profiling tools on the same port.
+
+To use these, first [install go](https://golang.org/doc/install).
+
+### Debugging memory use
+
+To profile rclone&#39;s memory use you can run:
+
+    go tool pprof -web http://localhost:5572/debug/pprof/heap
+
+This should open a page in your browser showing what is using what
+memory.
+
+You can also use the `-text` flag to produce a textual summary
+</code></pre>
+<p>$ 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.(<em>conn).readRequest 0 0% 100% 513kB 33.38% net/http.(</em>conn).serve 0 0% 100% 1024.03kB 66.62% runtime.main</p>
+<pre><code>
+### Debugging go routine leaks
+
+Memory leaks are most often caused by go routine leaks keeping memory
+alive which should have been garbage collected.
+
+See all active go routines using
+
+    curl http://localhost:5572/debug/pprof/goroutine?debug=1
+
+Or go to http://localhost:5572/debug/pprof/goroutine?debug=1 in your browser.
+
+### Other profiles to look at
+
+You can see a summary of profiles available at http://localhost:5572/debug/pprof/
+
+Here is how to use some of them:
+
+- Memory: `go tool pprof http://localhost:5572/debug/pprof/heap`
+- Go routines: `curl http://localhost:5572/debug/pprof/goroutine?debug=1`
+- 30-second CPU profile: `go tool pprof http://localhost:5572/debug/pprof/profile`
+- 5-second execution trace: `wget http://localhost:5572/debug/pprof/trace?seconds=5`
+- Goroutine blocking profile
+    - Enable first with: `rclone rc debug/set-block-profile-rate rate=1` ([docs](#debug/set-block-profile-rate))
+    - `go tool pprof http://localhost:5572/debug/pprof/block`
+- Contended mutexes:
+    - Enable first with: `rclone rc debug/set-mutex-profile-fraction rate=1` ([docs](#debug/set-mutex-profile-fraction))
+    - `go tool pprof http://localhost:5572/debug/pprof/mutex`
+
+See the [net/http/pprof docs](https://golang.org/pkg/net/http/pprof/)
+for more info on how to use the profiling and for a general overview
+see [the Go team&#39;s blog post on profiling go programs](https://blog.golang.org/profiling-go-programs).
+
+The profiling hook is [zero overhead unless it is used](https://stackoverflow.com/q/26545159/164234).
+
+# Overview of cloud storage systems #
+
+Each cloud storage system is slightly different.  Rclone attempts to
+provide a unified interface to them, but some underlying differences
+show through.
+
+## Features ##
+
+Here is an overview of the major features of each cloud storage system.
+
+| Name                         | Hash        | ModTime | Case Insensitive | Duplicate Files | MIME Type |
+| ---------------------------- |:-----------:|:-------:|:----------------:|:---------------:|:---------:|
+| 1Fichier                     | Whirlpool   | No      | No               | Yes             | R         |
+| Amazon Drive                 | MD5         | No      | Yes              | No              | R         |
+| Amazon S3                    | MD5         | Yes     | No               | No              | R/W       |
+| Backblaze B2                 | SHA1        | Yes     | No               | No              | R/W       |
+| Box                          | SHA1        | Yes     | Yes              | No              | -         |
+| Citrix ShareFile             | MD5         | Yes     | Yes              | No              | -         |
+| Dropbox                      | DBHASH †    | Yes     | Yes              | No              | -         |
+| FTP                          | -           | No      | No               | No              | -         |
+| Google Cloud Storage         | MD5         | Yes     | No               | No              | R/W       |
+| Google Drive                 | MD5         | Yes     | No               | Yes             | R/W       |
+| Google Photos                | -           | No      | No               | Yes             | R         |
+| HTTP                         | -           | No      | No               | No              | R         |
+| Hubic                        | MD5         | Yes     | No               | No              | R/W       |
+| Jottacloud                   | MD5         | Yes     | Yes              | No              | R/W       |
+| Koofr                        | MD5         | No      | Yes              | No              | -         |
+| Mail.ru Cloud                | Mailru ‡‡‡  | Yes     | Yes              | No              | -         |
+| Mega                         | -           | No      | No               | Yes             | -         |
+| Memory                       | MD5         | Yes     | No               | No              | -         |
+| Microsoft Azure Blob Storage | MD5         | Yes     | No               | No              | R/W       |
+| Microsoft OneDrive           | SHA1 ‡‡     | Yes     | Yes              | No              | R         |
+| OpenDrive                    | MD5         | Yes     | Yes              | Partial \*      | -         |
+| OpenStack Swift              | MD5         | Yes     | No               | No              | R/W       |
+| pCloud                       | MD5, SHA1   | Yes     | No               | No              | W         |
+| premiumize.me                | -           | No      | Yes              | No              | R         |
+| put.io                       | CRC-32      | Yes     | No               | Yes             | R         |
+| QingStor                     | MD5         | No      | No               | No              | R/W       |
+| Seafile                      | -           | No      | No               | No              | -         |
+| SFTP                         | MD5, SHA1 ‡ | Yes     | Depends          | No              | -         |
+| SugarSync                    | -           | No      | No               | No              | -         |
+| Tardigrade                   | -           | Yes     | No               | No              | -         |
+| WebDAV                       | MD5, SHA1 ††| Yes ††† | Depends          | No              | -         |
+| Yandex Disk                  | MD5         | Yes     | No               | No              | R/W       |
+| The local filesystem         | All         | Yes     | Depends          | No              | -         |
+
+### Hash ###
+
+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 `--checksum` flag in syncs and in
+the `check` command.
+
+To use the verify checksums when transferring between cloud storage
+systems they must support a common hash type.
+
+† Note that Dropbox supports [its own custom
+hash](https://www.dropbox.com/developers/reference/content-hash).
+This is an SHA256 sum of all the 4MB block SHA256s.
+
+‡ SFTP supports checksums if the same login has shell access and `md5sum`
+or `sha1sum` as well as `echo` are in the remote&#39;s PATH.
+
+†† WebDAV supports hashes when used with Owncloud and Nextcloud only.
+
+††† WebDAV supports modtimes when used with Owncloud and Nextcloud only.
+
+‡‡ Microsoft OneDrive Personal supports SHA1 hashes, whereas OneDrive
+for business and SharePoint server support Microsoft&#39;s own
+[QuickXorHash](https://docs.microsoft.com/en-us/onedrive/developer/code-snippets/quickxorhash).
+
+‡‡‡ Mail.ru uses its own modified SHA1 hash
+
+### ModTime ###
+
+The cloud storage system supports setting modification times on
+objects.  If it does then this enables a using the modification times
+as part of the sync.  If not then only the size will be checked by
+default, though the MD5SUM can be checked with the `--checksum` flag.
+
+All cloud storage systems support some kind of date on the object and
+these will be set when transferring from the cloud storage system.
+
+### Case Insensitive ###
+
+If a cloud storage systems is case sensitive then it is possible to
+have two files which differ only in case, eg `file.txt` and
+`FILE.txt`.  If a cloud storage system is case insensitive then that
+isn&#39;t possible.
+
+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.
+
+The local filesystem and SFTP may or may not be case sensitive
+depending on OS.
+
+  * Windows - usually case insensitive, though case is preserved
+  * OSX - usually case insensitive, though it is possible to format case sensitive
+  * Linux - usually case sensitive, but there are case insensitive file systems (eg FAT formatted USB keys)
+
+Most of the time this doesn&#39;t cause any problems as people tend to
+avoid files whose name differs only by case even on case sensitive
+systems.
+
+### Duplicate files ###
+
+If a cloud storage system allows duplicate files then it can have two
+objects with the same name.
+
+This confuses rclone greatly when syncing - use the `rclone dedupe`
+command to rename or remove duplicates.
+
+\* 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 `rclone`.  It may be that this is a
+mistake or an unsupported feature.
+
+### Restricted filenames ###
+
+Some cloud storage systems might have restrictions on the characters
+that are usable in file or directory names.
+When `rclone` detects such a name during a file upload, it will
+transparently replace the restricted characters with similar looking
+Unicode characters.
+
+This process is designed to avoid ambiguous file names as much as
+possible and allow to move files between many cloud storage systems
+transparently.
+
+The name shown by `rclone` to the user or during log output will only
+contain a minimal set of [replaced characters](#restricted-characters)
+to ensure correct formatting and not necessarily the actual name used
+on the cloud storage.
+
+This transformation is reversed when downloading a file or parsing
+`rclone` arguments.
+For example, when uploading a file named `my file?.txt` to Onedrive
+will be displayed as `my file?.txt` on the console, but stored as
+`my file？.txt` (the `?` gets replaced by the similar looking `？`
+character) to Onedrive.
+The reverse transformation allows to read a file`unusual/name.txt`
+from Google Drive, by passing the name `unusual／name.txt` (the `/` needs
+to be replaced by the similar looking `／` character) on the command line.
+
+#### Default restricted characters {#restricted-characters}
+
+The table below shows the characters that are replaced by default.
+
+When a replacement character is found in a filename, this character
+will be escaped with the `‛` character to avoid ambiguous file names.
+(e.g. a file named `␀.txt` would shown as `‛␀.txt`)
+
+Each cloud storage backend can use a different set of characters,
+which will be specified in the documentation for each backend.
+
+| Character | Value | Replacement |
+| --------- |:-----:|:-----------:|
+| NUL       | 0x00  | ␀           |
+| SOH       | 0x01  | ␁           |
+| STX       | 0x02  | ␂           |
+| ETX       | 0x03  | ␃           |
+| EOT       | 0x04  | ␄           |
+| ENQ       | 0x05  | ␅           |
+| ACK       | 0x06  | ␆           |
+| BEL       | 0x07  | ␇           |
+| BS        | 0x08  | ␈           |
+| HT        | 0x09  | ␉           |
+| LF        | 0x0A  | ␊           |
+| VT        | 0x0B  | ␋           |
+| FF        | 0x0C  | ␌           |
+| CR        | 0x0D  | ␍           |
+| SO        | 0x0E  | ␎           |
+| SI        | 0x0F  | ␏           |
+| DLE       | 0x10  | ␐           |
+| DC1       | 0x11  | ␑           |
+| DC2       | 0x12  | ␒           |
+| DC3       | 0x13  | ␓           |
+| DC4       | 0x14  | ␔           |
+| NAK       | 0x15  | ␕           |
+| SYN       | 0x16  | ␖           |
+| ETB       | 0x17  | ␗           |
+| CAN       | 0x18  | ␘           |
+| EM        | 0x19  | ␙           |
+| SUB       | 0x1A  | ␚           |
+| ESC       | 0x1B  | ␛           |
+| FS        | 0x1C  | ␜           |
+| GS        | 0x1D  | ␝           |
+| RS        | 0x1E  | ␞           |
+| US        | 0x1F  | ␟           |
+| /         | 0x2F  | ／           |
+| DEL       | 0x7F  | ␡           |
+
+The default encoding will also encode these file names as they are
+problematic with many cloud storage systems.
+
+| File name | Replacement |
+| --------- |:-----------:|
+| .         | ．          |
+| ..        | ．．         |
+
+#### Invalid UTF-8 bytes {#invalid-utf8}
+
+Some backends only support a sequence of well formed UTF-8 bytes
+as file or directory names.
+
+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 `0xFE` will be encoded as `‛FE`.
+
+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
+[local filenames](https://rclone.org/local/#filenames) section for details.
+
+#### Encoding option {#encoding}
+
+Most backends have an encoding options, specified as a flag
+`--backend-encoding` where `backend` is the name of the backend, or as
+a config parameter `encoding` (you&#39;ll need to select the Advanced
+config in `rclone config` to see it).
+
+This will have default value which encodes and decodes characters in
+such a way as to preserve the maximum number of characters (see
+above).
+
+However this can be incorrect in some scenarios, for example if you
+have a Windows file system with characters such as `＊` and `？` that
+you want to remain as those characters on the remote rather than being
+translated to `*` and `?`.
+
+The `--backend-encoding` flags allow you to change that. You can
+disable the encoding completely with `--backend-encoding None` or set
+`encoding = None` in the config file.
+
+Encoding takes a comma separated list of encodings. You can see the
+list of all available characters by passing an invalid value to this
+flag, eg `--local-encoding &quot;help&quot;` and `rclone help flags encoding`
+will show you the defaults for the backends.
+
+| Encoding  | Characters |
+| --------- | ---------- |
+| Asterisk | `*` |
+| BackQuote | `` ` `` |
+| BackSlash | `\` |
+| Colon | `:` |
+| CrLf | CR 0x0D, LF 0x0A |
+| Ctl | All control characters 0x00-0x1F |
+| Del | DEL 0x7F |
+| Dollar | `$` |
+| Dot | `.` |
+| DoubleQuote | `&quot;` |
+| Hash | `#` |
+| InvalidUtf8 | An invalid UTF-8 character (eg latin1) |
+| LeftCrLfHtVt | CR 0x0D, LF 0x0A,HT 0x09, VT 0x0B on the left of a string |
+| LeftPeriod | `.` on the left of a string |
+| LeftSpace | SPACE on the left of a string |
+| LeftTilde | `~` on the left of a string |
+| LtGt | `&lt;`, `&gt;` |
+| None | No characters are encoded |
+| Percent | `%` |
+| Pipe | \| |
+| Question | `?` |
+| RightCrLfHtVt | CR 0x0D, LF 0x0A, HT 0x09, VT 0x0B on the right of a string |
+| RightPeriod | `.` on the right of a string |
+| RightSpace | SPACE on the right of a string |
+| SingleQuote | `&#39;` |
+| Slash | `/` |
+
+To take a specific example, the FTP backend&#39;s default encoding is
+
+    --ftp-encoding &quot;Slash,Del,Ctl,RightSpace,Dot&quot;
+
+However, let&#39;s say the FTP server is running on Windows and can&#39;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
+
+    Slash,LtGt,DoubleQuote,Colon,Question,Asterisk,Pipe,BackSlash,Ctl,RightSpace,RightPeriod,InvalidUtf8,Dot
+
+to the existing ones, giving:
+
+    Slash,LtGt,DoubleQuote,Colon,Question,Asterisk,Pipe,BackSlash,Ctl,RightSpace,RightPeriod,InvalidUtf8,Dot,Del,RightSpace
+
+This can be specified using the `--ftp-encoding` flag or using an `encoding` parameter in the config file.
+
+Or let&#39;s say you have a Windows server but you want to preserve `＊`
+and `？`, you would then have this as the encoding (the Windows
+encoding minus `Asterisk` and `Question`).
+
+    Slash,LtGt,DoubleQuote,Colon,Pipe,BackSlash,Ctl,RightSpace,RightPeriod,InvalidUtf8,Dot
+
+This can be specified using the `--local-encoding` flag or using an
+`encoding` parameter in the config file.
+
+### MIME Type ###
+
+MIME types (also known as media types) classify types of documents
+using a simple text classification, eg `text/html` or
+`application/pdf`.
+
+Some cloud storage systems support reading (`R`) the MIME type of
+objects and some support writing (`W`) the MIME type of objects.
+
+The MIME type can be important if you are serving files directly to
+HTTP from the storage system.
+
+If you are copying from a remote which supports reading (`R`) to a
+remote which supports writing (`W`) then rclone will preserve the MIME
+types.  Otherwise they will be guessed from the extension, or the
+remote itself may assign the MIME type.
+
+## Optional Features ##
+
+All the remotes support a basic set of features, but there are some
+optional features supported by some remotes used to make some
+operations more efficient.
+
+| Name                         | Purge | Copy | Move | DirMove | CleanUp | ListR | StreamUpload | LinkSharing | About | EmptyDir |
+| ---------------------------- |:-----:|:----:|:----:|:-------:|:-------:|:-----:|:------------:|:------------:|:-----:| :------: |
+| 1Fichier                     | No    | No   | No   | No      | No      | No    | No           | No           |   No  |  Yes |
+| Amazon Drive                 | Yes   | No   | Yes  | Yes     | No [#575](https://github.com/rclone/rclone/issues/575) | No  | No  | No [#2178](https://github.com/rclone/rclone/issues/2178) | No  | Yes |
+| Amazon S3                    | No    | Yes  | No   | No      | Yes     | Yes   | Yes          | No [#2178](https://github.com/rclone/rclone/issues/2178) | No  | No |
+| Backblaze B2                 | No    | Yes  | No   | No      | Yes     | Yes   | Yes          | Yes          | No  | No |
+| Box                          | Yes   | Yes  | Yes  | Yes     | Yes ‡‡  | No    | Yes          | Yes          | No  | Yes |
+| Citrix ShareFile             | Yes   | Yes  | Yes  | Yes     | No      | No    | Yes          | No          | No  | Yes |
+| Dropbox                      | Yes   | Yes  | Yes  | Yes     | No [#575](https://github.com/rclone/rclone/issues/575) | No  | Yes | Yes | Yes | Yes |
+| FTP                          | No    | No   | Yes  | Yes     | No      | No    | Yes          | No [#2178](https://github.com/rclone/rclone/issues/2178) | No  | Yes |
+| Google Cloud Storage         | Yes   | Yes  | No   | No      | No      | Yes   | Yes          | No [#2178](https://github.com/rclone/rclone/issues/2178) | No  | No |
+| Google Drive                 | Yes   | Yes  | Yes  | Yes     | Yes     | Yes   | Yes          | Yes         | Yes | Yes |
+| Google Photos                | No    | No   | No   | No      | No      | No    | No           | No          | No | No |
+| HTTP                         | No    | No   | No   | No      | No      | No    | No           | No [#2178](https://github.com/rclone/rclone/issues/2178) | No  | Yes |
+| Hubic                        | Yes † | Yes  | No   | No      | No      | Yes   | Yes          | No [#2178](https://github.com/rclone/rclone/issues/2178) | Yes | No |
+| Jottacloud                   | Yes   | Yes  | Yes  | Yes     | Yes     | Yes   | No           | Yes                                                   | Yes | Yes |
+| Mail.ru Cloud                | Yes   | Yes  | Yes  | Yes     | Yes     | No    | No           | Yes                                                   | Yes | Yes |
+| Mega                         | Yes   | No   | Yes  | Yes     | Yes     | No    | No           | No [#2178](https://github.com/rclone/rclone/issues/2178) | Yes | Yes |
+| Memory                       | No    | Yes  | No   | No      | No      | Yes   | Yes          | No          | No | No |
+| Microsoft Azure Blob Storage | Yes   | Yes  | No   | No      | No      | Yes   | Yes          | No [#2178](https://github.com/rclone/rclone/issues/2178) | No  | No |
+| Microsoft OneDrive           | Yes   | Yes  | Yes  | Yes     | Yes     | No    | No           | Yes | Yes | Yes |
+| OpenDrive                    | Yes   | Yes  | Yes  | Yes     | No      | No    | No           | No                                                    | No  | Yes |
+| OpenStack Swift              | Yes † | Yes  | No   | No      | No      | Yes   | Yes          | No [#2178](https://github.com/rclone/rclone/issues/2178) | Yes | No |
+| pCloud                       | Yes   | Yes  | Yes  | Yes     | Yes     | No    | No           | Yes | Yes | Yes |
+| premiumize.me                | Yes   | No   | Yes  | Yes     | No      | No    | No           | Yes         | Yes | Yes |
+| put.io                       | Yes   | No   | Yes  | Yes     | Yes     | No    | Yes          | No [#2178](https://github.com/rclone/rclone/issues/2178) | Yes | Yes |
+| QingStor                     | No    | Yes  | No   | No      | Yes     | Yes   | No           | No [#2178](https://github.com/rclone/rclone/issues/2178) | No  | No |
+| Seafile                      | Yes   | Yes  | Yes  | Yes     | Yes     | Yes   | Yes          | Yes         | Yes | Yes |
+| SFTP                         | No    | No   | Yes  | Yes     | No      | No    | Yes          | No [#2178](https://github.com/rclone/rclone/issues/2178) | Yes  | Yes |
+| SugarSync                    | Yes   | Yes  | Yes  | Yes     | No      | No    | Yes          | Yes         | No  | Yes |
+| Tardigrade                   | Yes † | No   | No   | No      | No      | Yes   | Yes          | No          | No  | No  |
+| WebDAV                       | Yes   | Yes  | Yes  | Yes     | No      | No    | Yes ‡        | No [#2178](https://github.com/rclone/rclone/issues/2178) | Yes  | Yes |
+| Yandex Disk                  | Yes   | Yes  | Yes  | Yes     | Yes     | No    | Yes          | Yes         | Yes | Yes |
+| The local filesystem         | Yes   | No   | Yes  | Yes     | No      | No    | Yes          | No          | Yes | Yes |
+
+### Purge ###
+
+This deletes a directory quicker than just deleting all the files in
+the directory.
+
+† Note Swift, Hubic, and Tardigrade implement this in order to delete
+directory markers but they don&#39;t actually have a quicker way of deleting
+files other than deleting them individually.
+
+‡ StreamUpload is not supported with Nextcloud
+
+### Copy ###
+
+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 `rclone copy` or
+`rclone move` if the remote doesn&#39;t support `Move` directly.
+
+If the server doesn&#39;t support `Copy` directly then for copy operations
+the file is downloaded then re-uploaded.
+
+### Move ###
+
+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 `rclone move` if the
+server doesn&#39;t support `DirMove`.
+
+If the server isn&#39;t capable of `Move` then rclone simulates it with
+`Copy` then delete.  If the server doesn&#39;t support `Copy` then rclone
+will download the file and re-upload it.
+
+### DirMove ###
+
+This is used to implement `rclone move` to move a directory if
+possible.  If it isn&#39;t then it will use `Move` on each file (which
+falls back to `Copy` then download and upload - see `Move` section).
+
+### CleanUp ###
+
+This is used for emptying the trash for a remote by `rclone cleanup`.
+
+If the server can&#39;t do `CleanUp` then `rclone cleanup` will return an
+error.
+
+‡‡ Note that while Box implements this it has to delete every file
+idividually so it will be slower than emptying the trash via the WebUI
+
+### ListR ###
+
+The remote supports a recursive list to list all the contents beneath
+a directory quickly.  This enables the `--fast-list` flag to work.
+See the [rclone docs](https://rclone.org/docs/#fast-list) for more details.
+
+### StreamUpload ###
+
+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. `rclone rcat`.
+
+### LinkSharing ###
+
+Sets the necessary permissions on a file or folder and prints a link
+that allows others to access them, even if they don&#39;t have an account
+on the particular cloud provider.
+
+### About ###
+
+This is used to fetch quota information from the remote, like bytes
+used/free/quota and bytes used in the trash.
+
+This is also used to return the space used, available for `rclone mount`.
+
+If the server can&#39;t do `About` then `rclone about` will return an
+error.
+
+### EmptyDir ###
+
+The remote supports empty directories. See [Limitations](https://rclone.org/bugs/#limitations)
+ for details. Most Object/Bucket based remotes do not support this.
+
+# Global Flags
+
+This describes the global flags available to every rclone command
+split into two groups, non backend and backend flags.
+
+## Non Backend Flags
+
+These flags are available for every command.
+</code></pre>
+<pre><code>  --ask-password                         Allow prompt for password for encrypted configuration. (default true)
+  --auto-confirm                         If enabled, do not request console confirmation.
+  --backup-dir string                    Make backups into hierarchy based in DIR.
+  --bind string                          Local address to bind to for outgoing connections, IPv4, IPv6 or name.
+  --buffer-size SizeSuffix               In memory buffer size when reading files for each --transfer. (default 16M)
+  --bwlimit BwTimetable                  Bandwidth limit in kBytes/s, or use suffix b|k|M|G or a full timetable.
+  --bwlimit-file BwTimetable             Bandwidth limit per file in kBytes/s, or use suffix b|k|M|G or a full timetable.
+  --ca-cert string                       CA certificate used to verify servers
+  --cache-dir string                     Directory rclone will use for caching. (default &quot;$HOME/.cache/rclone&quot;)
+  --check-first                          Do all the checks before starting transfers.
+  --checkers int                         Number of checkers to run in parallel. (default 8)</code></pre>
+<p>-c, --checksum Skip based on checksum (if available) &amp; size, not mod-time &amp; size --client-cert string Client SSL certificate (PEM) for mutual TLS auth --client-key string Client SSL private key (PEM) for mutual TLS auth --compare-dest string Include additional server-side path during comparison. --config string Config file. (default "$HOME/.config/rclone/rclone.conf") --contimeout duration Connect timeout (default 1m0s) --copy-dest string Implies --compare-dest but also copies files from path into destination. --cpuprofile string Write cpu profile to file --cutoff-mode string Mode to stop transfers when reaching the max transfer limit HARD|SOFT|CAUTIOUS (default "HARD") --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 --delete-excluded Delete files on dest excluded from sync --disable string Disable a comma separated list of features. Use help to see a list. -n, --dry-run Do a trial run with no permanent changes --dump DumpFlags List of items to dump from: headers,bodies,requests,responses,auth,filters,goroutines,openfiles --dump-bodies Dump HTTP headers and bodies - may contain sensitive info --dump-headers Dump HTTP headers - may contain sensitive info --error-on-no-transfer Sets exit code 9 if no files are transferred, useful in scripts --exclude stringArray Exclude files matching pattern --exclude-from stringArray Read exclude patterns from file (use - to read from stdin) --exclude-if-present string Exclude directories if filename is present --expect-continue-timeout duration Timeout when using expect / 100-continue in HTTP (default 1s) --fast-list Use recursive list if available. Uses more memory but fewer transactions. --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 filtering patterns from a file (use - to read from stdin) --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 --ignore-case Ignore case in filters (case insensitive) --ignore-case-sync Ignore case when synchronizing --ignore-checksum Skip post copy check of checksums. --ignore-errors delete even if there are I/O errors --ignore-existing Skip all files that exist on destination --ignore-size Ignore size when skipping use mod-time or checksum. -I, --ignore-times Don't skip files that match size and time - transfer all files --immutable Do not modify files. Fail if existing files have been modified. --include stringArray Include files matching pattern --include-from stringArray Read include patterns from file (use - to read from stdin) -i, --interactive Enable interactive mode --log-file string Log everything to this file --log-format string Comma separated list of log format options (default "date,time") --log-level string Log level DEBUG|INFO|NOTICE|ERROR (default "NOTICE") --low-level-retries int Number of low level retries to do. (default 10) --max-age Duration Only transfer files younger than this in s or suffix ms|s|m|h|d|w|M|y (default off) --max-backlog int Maximum number of objects in sync or check backlog. (default 10000) --max-delete int When synchronizing, limit the number of deletes (default -1) --max-depth int If set limits the recursion depth to this. (default -1) --max-duration duration Maximum duration rclone will transfer data for. --max-size SizeSuffix Only transfer files smaller than this in k or suffix b|k|M|G (default off) --max-stats-groups int Maximum number of stats groups to keep in memory. On max oldest is discarded. (default 1000) --max-transfer SizeSuffix Maximum size of data to transfer. (default off) --memprofile string Write memory profile to file --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 k or suffix b|k|M|G (default off) --modify-window duration Max time diff to be considered the same (default 1ns) --multi-thread-cutoff SizeSuffix Use multi-thread downloads for files above this size. (default 250M) --multi-thread-streams int Max number of streams to use for multi-thread downloads. (default 4) --no-check-certificate Do not verify the server SSL certificate. Insecure. --no-check-dest Don't check the destination, copy regardless. --no-gzip-encoding Don't set Accept-Encoding: gzip. --no-traverse Don't traverse destination file system on copy. --no-unicode-normalization Don't normalize unicode characters in filenames. --no-update-modtime Don't update destination mod-time if files identical. --order-by string Instructions on how to order the transfers, eg 'size,descending' --password-command SpaceSepList Command for supplying password for encrypted configuration. -P, --progress Show progress during transfer. -q, --quiet Print as little stuff as possible --rc Enable the remote control server. --rc-addr string IPaddress:Port or :Port to bind server to. (default "localhost:5572") --rc-allow-origin string Set the allowed origin for CORS. --rc-baseurl string Prefix for URLs - leave blank for root. --rc-cert string SSL PEM key (concatenation of certificate and CA certificate) --rc-client-ca string Client certificate authority to verify clients with --rc-enable-metrics Enable prometheus metrics on /metrics --rc-files string Path to local files to serve on the HTTP server. --rc-htpasswd string 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 SSL PEM Private key --rc-max-header-bytes int Maximum size of request header (default 4096) --rc-no-auth Don't require auth for certain methods. --rc-pass string Password for authentication. --rc-realm string realm for authentication (default "rclone") --rc-serve Enable the serving of remote objects. --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 "https://api.github.com/repos/rclone/rclone-webui-react/releases/latest") --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't open the browser automatically --rc-web-gui-update Check and update to latest version of web gui --refresh-times Refresh the modtime of remote files. --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) --size-only Skip based on size only, not mod-time or checksum --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 string 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 Enables --stats-one-line and add current date/time prefix. --stats-one-line-date-format string Enables --stats-one-line-date and uses custom formatted date. Enclose date string in double quotes ("). See https://golang.org/pkg/time/#Time.Format --stats-unit string Show data rate in stats as either 'bits' or 'bytes'/s (default "bytes") --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 100k) --suffix string Suffix to add to changed files. --suffix-keep-extension Preserve the extension when using --suffix. --syslog Use Syslog for logging --syslog-facility string Facility for syslog, eg KERN,USER,... (default "DAEMON") --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) --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 "hash") --transfers int Number of file transfers to run in parallel. (default 4) -u, --update Skip files that are newer on the destination. --use-cookies Enable session cookiejar. --use-json-log Use json log format. --use-mmap Use mmap allocator (see docs). --use-server-modtime Use server modified time instead of object metadata --user-agent string Set the user-agent to a specified string. The default is rclone/ version (default "rclone/v1.53.0") -v, --verbose count Print lots more stuff (repeat for more)</p>
+<pre><code>
+## Backend Flags
+
+These flags are available for every command. They control the backends
+and may be set in the config file.
+</code></pre>
+<pre><code>  --acd-auth-url string                                      Auth server URL.
+  --acd-client-id string                                     OAuth Client Id
+  --acd-client-secret string                                 OAuth Client Secret
+  --acd-encoding MultiEncoder                                This sets the encoding for the backend. (default Slash,InvalidUtf8,Dot)
+  --acd-templink-threshold SizeSuffix                        Files &gt;= this size will be downloaded via their tempLink. (default 9G)
+  --acd-token string                                         OAuth Access Token as a JSON blob.
+  --acd-token-url string                                     Token server url.
+  --acd-upload-wait-per-gb Duration                          Additional time per GB to wait after a failed complete upload to see if it appears. (default 3m0s)
+  --alias-remote string                                      Remote or path to alias.
+  --azureblob-access-tier string                             Access tier of blob: hot, cool or archive.
+  --azureblob-account string                                 Storage Account Name (leave blank to use SAS URL or Emulator)
+  --azureblob-chunk-size SizeSuffix                          Upload chunk size (&lt;= 100MB). (default 4M)
+  --azureblob-disable-checksum                               Don&#39;t store MD5 checksum with object metadata.
+  --azureblob-encoding MultiEncoder                          This sets the encoding for the backend. (default Slash,BackSlash,Del,Ctl,RightPeriod,InvalidUtf8)
+  --azureblob-endpoint string                                Endpoint for the service
+  --azureblob-key string                                     Storage Account Key (leave blank to use SAS URL or Emulator)
+  --azureblob-list-chunk int                                 Size of blob list. (default 5000)
+  --azureblob-memory-pool-flush-time Duration                How often internal memory buffer pools will be flushed. (default 1m0s)
+  --azureblob-memory-pool-use-mmap                           Whether to use mmap buffers in internal memory pool.
+  --azureblob-sas-url string                                 SAS URL for container level access only
+  --azureblob-upload-cutoff SizeSuffix                       Cutoff for switching to chunked upload (&lt;= 256MB). (default 256M)
+  --azureblob-use-emulator                                   Uses local storage emulator if provided as &#39;true&#39; (leave blank if using real azure storage endpoint)
+  --b2-account string                                        Account ID or Application Key ID
+  --b2-chunk-size SizeSuffix                                 Upload chunk size. Must fit in memory. (default 96M)
+  --b2-copy-cutoff SizeSuffix                                Cutoff for switching to multipart copy (default 4G)
+  --b2-disable-checksum                                      Disable checksums for large (&gt; upload cutoff) files
+  --b2-download-auth-duration Duration                       Time before the 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 MultiEncoder                                 This sets 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-memory-pool-flush-time Duration                       How often internal memory buffer pools will be flushed. (default 1m0s)
+  --b2-memory-pool-use-mmap                                  Whether to use mmap buffers in internal memory pool.
+  --b2-test-mode string                                      A flag string for X-Bz-Test-Mode header for debugging.
+  --b2-upload-cutoff SizeSuffix                              Cutoff for switching to chunked upload. (default 200M)
+  --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-encoding MultiEncoder                                This sets the encoding for the backend. (default Slash,BackSlash,Del,Ctl,RightSpace,InvalidUtf8,Dot)
+  --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;= 50MB). (default 50M)
+  --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 5M)
+  --cache-chunk-total-size SizeSuffix                        The total size that the chunks can take up on the local disk. (default 10G)
+  --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-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 2G)
+  --chunker-fail-hard                                        Choose how chunker should handle files with missing or invalid chunks.
+  --chunker-hash-type string                                 Choose how chunker handles hash sums. All modes but &quot;none&quot; require metadata. (default &quot;md5&quot;)
+  --chunker-meta-format string                               Format of the metadata object or &quot;none&quot;. By default &quot;simplejson&quot;. (default &quot;simplejson&quot;)
+  --chunker-name-format string                               String format of chunk file names. (default &quot;*.rclone_chunk.###&quot;)
+  --chunker-remote string                                    Remote to chunk/unchunk.
+  --chunker-start-from int                                   Minimum valid chunk number. Usually 0 or 1. (default 1)</code></pre>
+-L, --copy-links Follow symlinks and copy the pointed to item. --crypt-directory-name-encryption Option to either encrypt directory names or leave them intact. (default true) --crypt-filename-encryption string How to encrypt the filenames. (default "standard") --crypt-password string Password or pass phrase for encryption. (obscured) --crypt-password2 string Password or pass phrase for salt. Optional but recommended. (obscured) --crypt-remote string Remote to encrypt/decrypt. --crypt-server-side-across-configs Allow server side operations (eg copy) to work across different crypt configs. --crypt-show-mapping For all files listed show how the names encrypt. --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 (e.g. file.doc to file.docx). This will confuse sync and reupload every time. --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. Must a power of 2 &gt;= 256k. (default 8M) --drive-client-id string OAuth Client Id --drive-client-secret string OAuth Client Secret --drive-disable-http2 Disable drive using http2 (default true) --drive-encoding MultiEncoder This sets the encoding for the backend. (default InvalidUtf8) --drive-export-formats string Comma separated list of preferred formats for downloading Google docs. (default "docx,xlsx,pptx,svg") --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-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-root-folder-id string ID of the root folder --drive-scope string Scope that rclone should use when requesting access from drive. --drive-server-side-across-configs Allow server side operations (eg copy) to work across different drive configs. --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-size-as-quota Show sizes as storage quota usage, not actual size. --drive-skip-checksum-gphotos Skip MD5 checksum on Google photos and videos only. --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-upload-limit Make upload limit errors be fatal --drive-team-drive string ID of the 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 8M) --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's are greater, use drive v2 API to download. (default off) --dropbox-auth-url string Auth server URL. --dropbox-chunk-size SizeSuffix Upload chunk size. (&lt; 150M). (default 48M) --dropbox-client-id string OAuth Client Id --dropbox-client-secret string OAuth Client Secret --dropbox-encoding MultiEncoder This sets the encoding for the backend. (default Slash,BackSlash,Del,RightSpace,InvalidUtf8,Dot) --dropbox-impersonate string Impersonate this user when using a business account. --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-encoding MultiEncoder This sets the encoding for the backend. (default Slash,LtGt,DoubleQuote,SingleQuote,BackQuote,Dollar,BackSlash,Del,Ctl,LeftSpace,RightSpace,InvalidUtf8,Dot) --fichier-shared-folder string If you want to download a shared folder, add this parameter --ftp-concurrency int Maximum number of FTP simultaneous connections, 0 for unlimited --ftp-disable-epsv Disable using EPSV even if server advertises support --ftp-encoding MultiEncoder This sets the encoding for the backend. (default Slash,Del,Ctl,RightSpace,Dot) --ftp-explicit-tls Use FTP over TLS (Explicit) --ftp-host string FTP host to connect to --ftp-no-check-certificate Do not verify the TLS certificate of the server --ftp-pass string FTP password (obscured) --ftp-port string FTP port, leave blank to use default (21) --ftp-tls Use FTPS over TLS (Implicit) --ftp-user string FTP username, leave blank for current username, $USER --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-encoding MultiEncoder This sets the encoding for the backend. (default Slash,CrLf,InvalidUtf8,Dot) --gcs-location string Location for the newly created buckets. --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. --gphotos-auth-url string Auth server URL. --gphotos-client-id string OAuth Client Id --gphotos-client-secret string OAuth Client Secret --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. --http-headers CommaSepList Set HTTP headers for all transactions --http-no-head Don't use HEAD requests to find file sizes in dir listing --http-no-slash Set this if the site doesn't end directories with / --http-url string URL of http host to connect to --hubic-auth-url string Auth server URL. --hubic-chunk-size SizeSuffix Above this size files will be chunked into a _segments container. (default 5G) --hubic-client-id string OAuth Client Id --hubic-client-secret string OAuth Client Secret --hubic-encoding MultiEncoder This sets the encoding for the backend. (default Slash,InvalidUtf8) --hubic-no-chunk Don't chunk files during streaming upload. --hubic-token string OAuth Access Token as a JSON blob. --hubic-token-url string Token server url. --jottacloud-encoding MultiEncoder This sets 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 10M) --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's. (default 10M) --koofr-encoding MultiEncoder This sets the encoding for the backend. (default Slash,BackSlash,Del,Ctl,InvalidUtf8,Dot) --koofr-endpoint string The Koofr API endpoint to use (default "https://app.koofr.net") --koofr-mountid string Mount ID of the mount to use. If omitted, the primary mount is used. --koofr-password string Your Koofr password for rclone (generate one at https://app.koofr.net/app/admin/preferences/password) (obscured) --koofr-setmtime Does the backend support setting modification time. Set this to false if you use a mount ID that points to a Dropbox or Amazon Drive backend. (default true) --koofr-user string Your Koofr user name -l, --links Translate symlinks to/from regular files with a '.rclonelink' 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-encoding MultiEncoder This sets the encoding for the backend. (default Slash,Dot) --local-no-check-updated Don't check to see if the files change during upload --local-no-set-modtime Disable setting modtime --local-no-sparse Disable sparse files for multi-thread downloads --local-no-unicode-normalization Don't apply unicode normalization to paths and filenames (Deprecated) --local-nounc string Disable UNC (long path names) conversion on Windows --mailru-check-hash What should copy do if file checksum is mismatched or invalid (default true) --mailru-encoding MultiEncoder This sets 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 "<em>.mkv,</em>.avi,<em>.mp4,</em>.mp3,<em>.zip,</em>.gz,<em>.rar,</em>.pdf") --mailru-speedup-max-disk SizeSuffix This option allows you to disable speedup (put by hash) for large files (default 3G) --mailru-speedup-max-memory SizeSuffix Files larger than the size given below will always be hashed on disk. (default 32M) --mailru-user string User name (usually email) --mega-debug Output more debug from Mega. --mega-encoding MultiEncoder This sets 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-user string User name -x, --one-file-system Don't cross filesystem boundaries (unix/macOS only). --onedrive-auth-url string Auth server URL. --onedrive-chunk-size SizeSuffix Chunk size to upload files with - must be multiple of 320k (327,680 bytes). (default 10M) --onedrive-client-id string OAuth Client Id --onedrive-client-secret string OAuth Client Secret --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 MultiEncoder This sets the encoding for the backend. (default Slash,LtGt,DoubleQuote,Colon,Question,Asterisk,Pipe,Hash,Percent,BackSlash,Del,Ctl,LeftSpace,LeftTilde,RightSpace,RightPeriod,InvalidUtf8,Dot) --onedrive-expose-onenote-files Set to make OneNote files show up in directory listings. --onedrive-no-versions Remove all versions on modifying operations --onedrive-server-side-across-configs Allow server side operations (eg copy) to work across different onedrive configs. --onedrive-token string OAuth Access Token as a JSON blob. --onedrive-token-url string Token server url. --opendrive-chunk-size SizeSuffix Files will be uploaded in chunks this size. (default 10M) --opendrive-encoding MultiEncoder This sets 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-encoding MultiEncoder This sets the encoding for the backend. (default Slash,BackSlash,Del,Ctl,InvalidUtf8,Dot) --pcloud-hostname string Hostname to connect to. (default "api.pcloud.com") --pcloud-root-folder-id string Fill in for rclone to use a non root folder as its starting point. (default "d0") --pcloud-token string OAuth Access Token as a JSON blob. --pcloud-token-url string Token server url. --premiumizeme-encoding MultiEncoder This sets the encoding for the backend. (default Slash,DoubleQuote,BackSlash,Del,Ctl,InvalidUtf8,Dot) --putio-encoding MultiEncoder This sets the encoding for the backend. (default Slash,BackSlash,Del,Ctl,InvalidUtf8,Dot) --qingstor-access-key-id string QingStor Access Key ID --qingstor-chunk-size SizeSuffix Chunk size to use for uploading. (default 4M) --qingstor-connection-retries int Number of connection retries. (default 3) --qingstor-encoding MultiEncoder This sets 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. Only applies if access_key_id and secret_access_key is blank. --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 200M) --qingstor-zone string Zone to connect to. --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 5M) --s3-copy-cutoff SizeSuffix Cutoff for switching to multipart copy (default 4.656G) --s3-disable-checksum Don't store MD5 checksum with object metadata --s3-encoding MultiEncoder This sets 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-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-memory-pool-flush-time Duration How often internal memory buffer pools will be flushed. (default 1m0s) --s3-memory-pool-use-mmap Whether to use mmap buffers in internal memory pool. --s3-no-check-bucket If set don't attempt to check the bucket exists or create it --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-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 If using SSE-C you must provide the secret encryption key used to encrypt/decrypt your data. --s3-sse-customer-key-md5 string If using SSE-C you must provide the secret encryption key MD5 checksum. --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. (default 4) --s3-upload-cutoff SizeSuffix Cutoff for switching to chunked upload (default 200M) --s3-use-accelerate-endpoint If true use the AWS S3 accelerated endpoint. --s3-v2-auth If true use v2 authentication. --seafile-2fa Two-factor authentication ('true' if the account has 2FA enabled) --seafile-create-library Should rclone create a library if it doesn't exist --seafile-encoding MultiEncoder This sets the encoding for the backend. (default Slash,DoubleQuote,BackSlash,Ctl,InvalidUtf8) --seafile-library string Name of the library. Leave blank to access all non-encrypted libraries. --seafile-library-key string Library password (for encrypted libraries only). Leave blank if you pass it through the command line. (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-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-key-file string Path to PEM-encoded private key file, leave blank or set key-use-agent to use ssh-agent. --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, If specified, will override key_file parameter. --sftp-key-use-agent When set forces the usage of the ssh-agent. --sftp-md5sum-command string The command used to read md5 hashes. Leave blank for autodetect. --sftp-pass string SSH password, leave blank to use ssh-agent. (obscured) --sftp-path-override string Override path used by SSH connection. --sftp-port string SSH port, leave blank to use default (22) --sftp-server-command string Specifies the path or command to run a sftp server on the remote host. --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. Leave blank for autodetect. --sftp-skip-links Set to skip any symlinks and any other non regular files. --sftp-subsystem string Specifies the SSH2 subsystem on the remote host. (default "sftp") --sftp-use-insecure-cipher Enable the use of insecure ciphers and key exchange methods. --sftp-user string SSH username, leave blank for current username, ncw --sharefile-chunk-size SizeSuffix Upload chunk size. Must a power of 2 &gt;= 256k. (default 64M) --sharefile-encoding MultiEncoder This sets 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-upload-cutoff SizeSuffix Cutoff for switching to multipart upload. (default 128M) --skip-links Don't warn about skipped symlinks. --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-encoding MultiEncoder This sets 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 into a _segments container. (default 5G) --swift-domain string User domain - optional (v3 auth) (OS_USER_DOMAIN_NAME) --swift-encoding MultiEncoder This sets the encoding for the backend. (default Slash,InvalidUtf8) --swift-endpoint-type string Endpoint type to choose from the service catalogue (OS_ENDPOINT_TYPE) (default "public") --swift-env-auth Get swift credentials from environment variables in standard OpenStack form. --swift-key string API key or password (OS_PASSWORD). --swift-no-chunk Don't chunk files during streaming upload. --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-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). --tardigrade-access-grant string Access Grant. --tardigrade-api-key string API Key. --tardigrade-passphrase string Encryption Passphrase. To access existing objects enter passphrase used for uploading. --tardigrade-provider string Choose an authentication method. (default "existing") --tardigrade-satellite-address <nodeid>@
+<address>
+:<port> Satellite Address. Custom satellite address should match the format: <nodeid>@
+<address>
+<p>:<port>. (default "us-central-1.tardigrade.io") --union-action-policy string Policy to choose upstream on ACTION category. (default "epall") --union-cache-time int Cache time of usage and free space (in seconds). This option is only useful when a path preserving policy is used. (default 120) --union-create-policy string Policy to choose upstream on CREATE category. (default "epmfs") --union-search-policy string Policy to choose upstream on SEARCH category. (default "ff") --union-upstreams string List of space separated upstreams. --webdav-bearer-token string Bearer token instead of user/pass (eg a Macaroon) --webdav-bearer-token-command string Command to run to get a bearer token --webdav-pass string Password. (obscured) --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-encoding MultiEncoder This sets the encoding for the backend. (default Slash,Del,Ctl,InvalidUtf8,Dot) --yandex-token string OAuth Access Token as a JSON blob. --yandex-token-url string Token server url.</p>
+<pre><code>
+ 1Fichier
+-----------------------------------------
+
+This is a backend for the [1fichier](https://1fichier.com) cloud
+storage service. Note that a Premium subscription is required to use
+the API.
+
+Paths are specified as `remote:path`
+
+Paths may be as deep as required, eg `remote:directory/subdirectory`.
+
+The initial setup for 1Fichier involves getting the API key from the website which you
+need to do in your browser.
+
+Here is an example of how to make a remote called `remote`.  First run:
+
+     rclone config
+
+This will guide you through an interactive setup process:
+</code></pre>
+<p>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 (""). Choose a number from below, or type in your own value [snip] XX / 1Fichier  "fichier" [snip] Storage&gt; fichier ** See help for fichier backend at: https://rclone.org/fichier/ **</p>
+<p>Your API Key, get it from https://1fichier.com/console/params.pl Enter a string value. Press Enter for the default (""). api_key&gt; example_key</p>
+<p>Edit advanced config? (y/n) y) Yes n) No y/n&gt; Remote config -------------------- [remote] type = fichier api_key = example_key -------------------- y) Yes this is OK e) Edit this remote d) Delete this remote y/e/d&gt; y</p>
+<pre><code>
+Once configured you can then use `rclone` like this,
+
+List directories in top level of your 1Fichier account
+
+    rclone lsd remote:
+
+List all the files in your 1Fichier account
+
+    rclone ls remote:
+
+To copy a local directory to a 1Fichier directory called backup
+
+    rclone copy /home/source remote:backup
+
+### Modified time and hashes ###
+
+1Fichier does not support modification times. It supports the Whirlpool hash algorithm.
+
+### Duplicated files ###
+
+1Fichier can have two files with exactly the same name and path (unlike a
+normal file system).
+
+Duplicated files cause problems with the syncing and you will see
+messages in the log about duplicates.
+
+#### Restricted filename characters
+
+In addition to the [default restricted characters set](https://rclone.org/overview/#restricted-characters)
+the following characters are also replaced:
+
+| Character | Value | Replacement |
+| --------- |:-----:|:-----------:|
+| \         | 0x5C  | ＼           |
+| &lt;         | 0x3C  | ＜           |
+| &gt;         | 0x3E  | ＞           |
+| &quot;         | 0x22  | ＂           |
+| $         | 0x24  | ＄           |
+| `         | 0x60  | ｀           |
+| &#39;         | 0x27  | ＇           |
+
+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:
+
+| Character | Value | Replacement |
+| --------- |:-----:|:-----------:|
+| SP        | 0x20  | ␠           |
+
+Invalid UTF-8 bytes will also be [replaced](https://rclone.org/overview/#invalid-utf8),
+as they can&#39;t be used in JSON strings.
+
+
+### Standard Options
+
+Here are the standard options specific to fichier (1Fichier).
+
+#### --fichier-api-key
 
 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
---------------------
-[remote]
-type = fichier
-api_key = example_key
---------------------
-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="modified-time-and-hashes">Modified time 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>
-<h4 id="restricted-filename-characters">Restricted filename characters</h4>
-<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>
-<ul>
-<li>Config: api_key</li>
-<li>Env Var: RCLONE_FICHIER_API_KEY</li>
-<li>Type: string</li>
-<li>Default: ""</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>
-<ul>
-<li>Config: shared_folder</li>
-<li>Env Var: RCLONE_FICHIER_SHARED_FOLDER</li>
-<li>Type: string</li>
-<li>Default: ""</li>
-</ul>
-<h4 id="fichier-encoding">–fichier-encoding</h4>
-<p>This sets 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>
-<ul>
-<li>Config: encoding</li>
-<li>Env Var: RCLONE_FICHIER_ENCODING</li>
-<li>Type: MultiEncoder</li>
-<li>Default: Slash,LtGt,DoubleQuote,SingleQuote,BackQuote,Dollar,BackSlash,Del,Ctl,LeftSpace,RightSpace,InvalidUtf8,Dot</li>
-</ul>
-<h2 id="alias">Alias</h2>
-<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, eg <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>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
+- Config:      api_key
+- Env Var:     RCLONE_FICHIER_API_KEY
+- Type:        string
+- Default:     &quot;&quot;
+
+### Advanced Options
+
+Here are the advanced options specific to fichier (1Fichier).
+
+#### --fichier-shared-folder
+
+If you want to download a shared folder, add this parameter
+
+- Config:      shared_folder
+- Env Var:     RCLONE_FICHIER_SHARED_FOLDER
+- Type:        string
+- Default:     &quot;&quot;
+
+#### --fichier-encoding
+
+This sets the encoding for the backend.
+
+See: the [encoding section in the overview](https://rclone.org/overview/#encoding) for more info.
+
+- Config:      encoding
+- Env Var:     RCLONE_FICHIER_ENCODING
+- Type:        MultiEncoder
+- Default:     Slash,LtGt,DoubleQuote,SingleQuote,BackQuote,Dollar,BackSlash,Del,Ctl,LeftSpace,RightSpace,InvalidUtf8,Dot
+
+
+
+ Alias
+-----------------------------------------
+
+The `alias` remote provides a new name for another remote.
+
+Paths may be as deep as required or a local path, 
+eg `remote:directory/subdirectory` or `/directory/subdirectory`.
+
+During the initial setup with `rclone config` you will specify the target
+remote. The target remote can either be a local path or another remote.
+
+Subfolders can be used in target remote. Assume an alias remote named `backup`
+with the target `mydrive:private/backup`. Invoking `rclone mkdir backup:desktop`
+is exactly the same as invoking `rclone mkdir mydrive:private/backup/desktop`.
+
+There will be no special handling of paths containing `..` segments.
+Invoking `rclone mkdir backup:../desktop` is exactly the same as invoking
+`rclone mkdir mydrive:private/backup/../desktop`.
+The empty path is not allowed as a remote. To alias the current directory
+use `.` instead.
+
+Here is an example of how to make an alias called `remote` for local folder.
+First run:
+
+     rclone config
+
+This will guide you through an interactive setup process:
+</code></pre>
+<p>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  "alias" [snip] Storage&gt; alias Remote or path to alias. Can be "myremote:path/to/dir", "myremote:bucket", "myremote:" or "/local/path". remote&gt; /mnt/storage/backup Remote config -------------------- [remote] remote = /mnt/storage/backup -------------------- y) Yes this is OK e) Edit this remote d) Delete this remote y/e/d&gt; y Current remotes:</p>
+<p>Name Type ==== ==== remote alias</p>
+<ol start="5" type="a">
+<li>Edit existing remote</li>
+<li>New remote</li>
+<li>Delete remote</li>
+<li>Rename remote</li>
+<li>Copy remote</li>
+<li>Set configuration password</li>
+<li>Quit config e/n/d/r/c/s/q&gt; q</li>
+</ol>
+<pre><code>
+Once configured you can then use `rclone` like this,
+
+List directories in top level in `/mnt/storage/backup`
+
+    rclone lsd remote:
+
+List all the files in `/mnt/storage/backup`
+
+    rclone ls remote:
+
+Copy another local directory to the alias directory called source
+
+    rclone copy /home/source remote:source
+
+
+### Standard Options
+
+Here are the standard options specific to alias (Alias for an existing remote).
+
+#### --alias-remote
+
 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
---------------------
-[remote]
-remote = /mnt/storage/backup
---------------------
-y) Yes this is OK
-e) Edit this remote
-d) Delete this remote
-y/e/d&gt; y
-Current remotes:
 
-Name                 Type
-====                 ====
-remote               alias
+- Config:      remote
+- Env Var:     RCLONE_ALIAS_REMOTE
+- Type:        string
+- Default:     &quot;&quot;
+
+
+
+ Amazon Drive
+-----------------------------------------
+
+Amazon Drive, formerly known as Amazon Cloud Drive, is a cloud storage
+service run by Amazon for consumers.
+
+## Status
+
+**Important:** rclone supports Amazon Drive only if you have your own
+set of API keys. Unfortunately the [Amazon Drive developer
+program](https://developer.amazon.com/amazon-drive) is now closed to
+new entries so if you don&#39;t already have your own set of keys you will
+not be able to use rclone with Amazon Drive.
+
+For the history on why rclone no longer has a set of Amazon Drive API
+keys see [the forum](https://forum.rclone.org/t/rclone-has-been-banned-from-amazon-drive/2314).
+
+If you happen to know anyone who works at Amazon then please ask them
+to re-instate rclone into the Amazon Drive developer program - thanks!
+
+## Setup
+
+The initial setup for Amazon Drive involves getting a token from
+Amazon which you need to do in your browser.  `rclone config` walks
+you through it.
+
+The configuration process for Amazon Drive may involve using an [oauth
+proxy](https://github.com/ncw/oauthproxy). This is used to keep the
+Amazon credentials out of the source code.  The proxy runs in Google&#39;s
+very secure App Engine environment and doesn&#39;t store any credentials
+which pass through it.
+
+Since rclone doesn&#39;t currently have its own Amazon Drive credentials
+so you will either need to have your own `client_id` and
+`client_secret` with Amazon Drive, or use a third party oauth proxy
+in which case you will need to enter `client_id`, `client_secret`,
+`auth_url` and `token_url`.
+
+Note also if you are not using Amazon&#39;s `auth_url` and `token_url`,
+(ie you filled in something for those) then if setting up on a remote
+machine you can only use the [copying the config method of
+configuration](https://rclone.org/remote_setup/#configuring-by-copying-the-config-file)
+- `rclone authorize` will not work.
+
+Here is an example of how to make a remote called `remote`.  First run:
+
+     rclone config
+
+This will guide you through an interactive setup process:
+</code></pre>
+<p>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 / Amazon Drive  "amazon cloud drive" [snip] Storage&gt; amazon cloud drive Amazon Application Client Id - required. client_id&gt; your client ID goes here Amazon Application Client Secret - required. client_secret&gt; your client secret goes here Auth server URL - leave blank to use Amazon's. auth_url&gt; Optional auth URL Token server url - leave blank to use Amazon's. token_url&gt; Optional token URL Remote config Make sure your Redirect URL is set to "http://127.0.0.1:53682/" in your custom config. Use auto config? * Say Y if not sure * Say N if you are working on a remote or headless machine y) Yes n) No y/n&gt; y If your browser doesn'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 -------------------- [remote] client_id = your client ID goes here client_secret = your client secret goes here auth_url = Optional auth URL token_url = Optional token URL token = {"access_token":"xxxxxxxxxxxxxxxxxxxxxxx","token_type":"bearer","refresh_token":"xxxxxxxxxxxxxxxxxx","expiry":"2015-09-06T16:07:39.658438471+01:00"} -------------------- y) Yes this is OK e) Edit this remote d) Delete this remote y/e/d&gt; y</p>
+<pre><code>
+See the [remote setup docs](https://rclone.org/remote_setup/) for how to set it up on a
+machine with no Internet browser available.
+
+Note that rclone runs a webserver on your local machine to collect the
+token as returned from Amazon. This only runs from the moment it
+opens your browser to the moment you get back the verification
+code.  This is on `http://127.0.0.1:53682/` and this it may require
+you to unblock it temporarily if you are running a host firewall.
+
+Once configured you can then use `rclone` like this,
+
+List directories in top level of your Amazon Drive
+
+    rclone lsd remote:
+
+List all the files in your Amazon Drive
+
+    rclone ls remote:
+
+To copy a local directory to an Amazon Drive directory called backup
+
+    rclone copy /home/source remote:backup
+
+### Modified time and MD5SUMs ###
+
+Amazon Drive doesn&#39;t allow modification times to be changed via
+the API so these won&#39;t be accurate or used for syncing.
+
+It does store MD5SUMs so for a more accurate sync, you can use the
+`--checksum` flag.
+
+#### Restricted filename characters
+
+| Character | Value | Replacement |
+| --------- |:-----:|:-----------:|
+| NUL       | 0x00  | ␀           |
+| /         | 0x2F  | ／          |
+
+Invalid UTF-8 bytes will also be [replaced](https://rclone.org/overview/#invalid-utf8),
+as they can&#39;t be used in JSON strings.
+
+### Deleting files ###
+
+Any files you delete with rclone will end up in the trash.  Amazon
+don&#39;t provide an API to permanently delete files, nor to empty the
+trash, so you will have to do that with one of Amazon&#39;s apps or via
+the Amazon Drive website. As of November 17, 2016, files are 
+automatically deleted by Amazon from the trash after 30 days.
+
+### Using with non `.com` Amazon accounts ###
+
+Let&#39;s say you usually use `amazon.co.uk`. When you authenticate with
+rclone it will take you to an `amazon.com` page to log in.  Your
+`amazon.co.uk` email and password should work here just fine.
+
+
+### Standard Options
+
+Here are the standard options specific to amazon cloud drive (Amazon Drive).
+
+#### --acd-client-id
+
+OAuth Client Id
+Leave blank normally.
+
+- Config:      client_id
+- Env Var:     RCLONE_ACD_CLIENT_ID
+- Type:        string
+- Default:     &quot;&quot;
+
+#### --acd-client-secret
+
+OAuth Client Secret
+Leave blank normally.
+
+- Config:      client_secret
+- Env Var:     RCLONE_ACD_CLIENT_SECRET
+- Type:        string
+- Default:     &quot;&quot;
+
+### Advanced Options
+
+Here are the advanced options specific to amazon cloud drive (Amazon Drive).
+
+#### --acd-token
+
+OAuth Access Token as a JSON blob.
+
+- Config:      token
+- Env Var:     RCLONE_ACD_TOKEN
+- Type:        string
+- Default:     &quot;&quot;
+
+#### --acd-auth-url
+
+Auth server URL.
+Leave blank to use the provider defaults.
+
+- Config:      auth_url
+- Env Var:     RCLONE_ACD_AUTH_URL
+- Type:        string
+- Default:     &quot;&quot;
+
+#### --acd-token-url
+
+Token server url.
+Leave blank to use the provider defaults.
+
+- Config:      token_url
+- Env Var:     RCLONE_ACD_TOKEN_URL
+- Type:        string
+- Default:     &quot;&quot;
+
+#### --acd-checkpoint
+
+Checkpoint for internal polling (debug).
+
+- Config:      checkpoint
+- Env Var:     RCLONE_ACD_CHECKPOINT
+- Type:        string
+- Default:     &quot;&quot;
+
+#### --acd-upload-wait-per-gb
+
+Additional time per GB to wait after a failed complete upload to see if it appears.
+
+Sometimes Amazon Drive gives an error when a file has been fully
+uploaded but the file appears anyway after a little while.  This
+happens sometimes for files over 1GB in size and nearly every time for
+files bigger than 10GB. This parameter controls the time rclone waits
+for the file to appear.
+
+The default value for this parameter is 3 minutes per GB, so by
+default it will wait 3 minutes for every GB uploaded to see if the
+file appears.
+
+You can disable this feature by setting it to 0. This may cause
+conflict errors as rclone retries the failed upload but the file will
+most likely appear correctly eventually.
+
+These values were determined empirically by observing lots of uploads
+of big files for a range of file sizes.
+
+Upload with the &quot;-v&quot; flag to see more info about what rclone is doing
+in this situation.
+
+- Config:      upload_wait_per_gb
+- Env Var:     RCLONE_ACD_UPLOAD_WAIT_PER_GB
+- Type:        Duration
+- Default:     3m0s
+
+#### --acd-templink-threshold
+
+Files &gt;= this size will be downloaded via their tempLink.
+
+Files this size or more will be downloaded via their &quot;tempLink&quot;. This
+is to work around a problem with Amazon Drive which blocks downloads
+of files bigger than about 10GB.  The default for this is 9GB which
+shouldn&#39;t need to be changed.
+
+To download files above this threshold, rclone requests a &quot;tempLink&quot;
+which downloads the file through a temporary URL directly from the
+underlying S3 storage.
+
+- Config:      templink_threshold
+- Env Var:     RCLONE_ACD_TEMPLINK_THRESHOLD
+- Type:        SizeSuffix
+- Default:     9G
+
+#### --acd-encoding
+
+This sets the encoding for the backend.
+
+See: the [encoding section in the overview](https://rclone.org/overview/#encoding) for more info.
+
+- Config:      encoding
+- Env Var:     RCLONE_ACD_ENCODING
+- Type:        MultiEncoder
+- Default:     Slash,InvalidUtf8,Dot
+
+
+
+### Limitations ###
+
+Note that Amazon Drive is case insensitive so you can&#39;t have a
+file called &quot;Hello.doc&quot; and one called &quot;hello.doc&quot;.
+
+Amazon Drive has rate limiting so you may notice errors in the
+sync (429 errors).  rclone will automatically retry the sync up to 3
+times by default (see `--retries` flag) which should hopefully work
+around this problem.
+
+Amazon Drive has an internal limit of file sizes that can be uploaded
+to the service. This limit is not officially published, but all files
+larger than this will fail.
+
+At the time of writing (Jan 2016) is in the area of 50GB per file.
+This means that larger files are likely to fail.
+
+Unfortunately there is no way for rclone to see that this failure is
+because of file size, so it will retry the operation, as any other
+failure. To avoid this problem, use `--max-size 50000M` option to limit
+the maximum size of uploaded files. Note that `--max-size` does not split
+files into segments, it only ignores files over this size.
+
+ Amazon S3 Storage Providers
+--------------------------------------------------------
+
+The S3 backend can be used with a number of different providers:
+
+
+- AWS S3
+- Alibaba Cloud (Aliyun) Object Storage System (OSS)
+- Ceph
+- DigitalOcean Spaces
+- Dreamhost
+- IBM COS S3
+- Minio
+- Scaleway
+- StackPath
+- Wasabi
+
+
+Paths are specified as `remote:bucket` (or `remote:` for the `lsd`
+command.)  You may put subdirectories in too, eg `remote:bucket/path/to/dir`.
+
+Once you have made a remote (see the provider specific section above)
+you can use it like this:
+
+See all buckets
+
+    rclone lsd remote:
+
+Make a new bucket
+
+    rclone mkdir remote:bucket
+
+List the contents of a bucket
+
+    rclone ls remote:bucket
+
+Sync `/home/local/directory` to the remote bucket, deleting any excess
+files in the bucket.
+
+    rclone sync -i /home/local/directory remote:bucket
+
+## AWS S3 {#amazon-s3}
+
+Here is an example of making an s3 configuration.  First run
+
+    rclone config
+
+This will guide you through an interactive setup process.
+</code></pre>
+<p>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 (AWS, Ceph, Dreamhost, IBM COS, Minio)  "s3" [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  "AWS" 2 / Ceph Object Storage  "Ceph" 3 / Digital Ocean Spaces  "DigitalOcean" 4 / Dreamhost DreamObjects  "Dreamhost" 5 / IBM COS S3  "IBMCOS" 6 / Minio Object Storage  "Minio" 7 / Wasabi Object Storage  "Wasabi" 8 / Any other S3 compatible provider  "Other" 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  "false" 2 / Get AWS credentials from the environment (env vars or IAM)  "true" 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.  "us-east-1" / US East (Ohio) Region 2 | Needs location constraint us-east-2.  "us-east-2" / US West (Oregon) Region 3 | Needs location constraint us-west-2.  "us-west-2" / US West (Northern California) Region 4 | Needs location constraint us-west-1.  "us-west-1" / Canada (Central) Region 5 | Needs location constraint ca-central-1.  "ca-central-1" / EU (Ireland) Region 6 | Needs location constraint EU or eu-west-1.  "eu-west-1" / EU (London) Region 7 | Needs location constraint eu-west-2.  "eu-west-2" / EU (Frankfurt) Region 8 | Needs location constraint eu-central-1.  "eu-central-1" / Asia Pacific (Singapore) Region 9 | Needs location constraint ap-southeast-1.  "ap-southeast-1" / Asia Pacific (Sydney) Region 10 | Needs location constraint ap-southeast-2.  "ap-southeast-2" / Asia Pacific (Tokyo) Region 11 | Needs location constraint ap-northeast-1.  "ap-northeast-1" / Asia Pacific (Seoul) 12 | Needs location constraint ap-northeast-2.  "ap-northeast-2" / Asia Pacific (Mumbai) 13 | Needs location constraint ap-south-1.  "ap-south-1" / Asia Patific (Hong Kong) Region 14 | Needs location constraint ap-east-1.  "ap-east-1" / South America (Sao Paulo) Region 15 | Needs location constraint sa-east-1.  "sa-east-1" 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.  "" 2 / US East (Ohio) Region.  "us-east-2" 3 / US West (Oregon) Region.  "us-west-2" 4 / US West (Northern California) Region.  "us-west-1" 5 / Canada (Central) Region.  "ca-central-1" 6 / EU (Ireland) Region.  "eu-west-1" 7 / EU (London) Region.  "eu-west-2" 8 / EU Region.  "EU" 9 / Asia Pacific (Singapore) Region.  "ap-southeast-1" 10 / Asia Pacific (Sydney) Region.  "ap-southeast-2" 11 / Asia Pacific (Tokyo) Region.  "ap-northeast-1" 12 / Asia Pacific (Seoul)  "ap-northeast-2" 13 / Asia Pacific (Mumbai)  "ap-south-1" 14 / Asia Pacific (Hong Kong)  "ap-east-1" 15 / South America (Sao Paulo) Region.  "sa-east-1" 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).  "private" 2 / Owner gets FULL_CONTROL. The AllUsers group gets READ access.  "public-read" / Owner gets FULL_CONTROL. The AllUsers group gets READ and WRITE access. 3 | Granting this on a bucket is generally not recommended.  "public-read-write" 4 / Owner gets FULL_CONTROL. The AuthenticatedUsers group gets READ access.  "authenticated-read" / 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.  "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 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  "" 2 / AES256  "AES256" 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  "" 2 / Standard storage class  "STANDARD" 3 / Reduced redundancy storage class  "REDUCED_REDUNDANCY" 4 / Standard Infrequent Access storage class  "STANDARD_IA" 5 / One Zone Infrequent Access storage class  "ONEZONE_IA" 6 / Glacier storage class  "GLACIER" 7 / Glacier Deep Archive storage class  "DEEP_ARCHIVE" 8 / Intelligent-Tiering storage class  "INTELLIGENT_TIERING" storage_class&gt; 1 Remote config -------------------- [remote] 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 = -------------------- y) Yes this is OK e) Edit this remote d) Delete this remote y/e/d&gt;</p>
+<pre><code>
+### --fast-list ###
+
+This remote supports `--fast-list` which allows you to use fewer
+transactions in exchange for more memory. See the [rclone
+docs](https://rclone.org/docs/#fast-list) for more details.
+
+### --update and --use-server-modtime ###
+
+As noted below, the modified time is stored on metadata on the object. It 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 because it requires an extra API call to retrieve the
+metadata.
+
+For many operations, the time the object was last uploaded to the remote is
+sufficient to determine if it is &quot;dirty&quot;. By using `--update` along with
+`--use-server-modtime`, you can avoid the extra API call and simply upload
+files whose local modtime is newer than the time it was last uploaded.
+
+### Modified time ###
+
+The modified time is stored as metadata on the object as
+`X-Amz-Meta-Mtime` as floating point since the epoch accurate to 1 ns.
+
+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.
+
+### Cleanup ###
+
+If you run `rclone cleanup s3:bucket` then it will remove all pending
+multipart uploads older than 24 hours. You can use the `-i` flag to
+see exactly what it will do. If you want more control over the expiry
+date then run `rclone backend cleanup s3:bucket -o max-age=1h` to
+expire all uploads older than one hour. You can use `rclone backend
+list-multipart-uploads s3:bucket` to see the pending multipart
+uploads.
+
+#### Restricted filename characters
+
+S3 allows any valid UTF-8 string as a key.
+
+Invalid UTF-8 bytes will be [replaced](https://rclone.org/overview/#invalid-utf8), as
+they can&#39;t be used in XML.
+
+The following characters are replaced since these are problematic when
+dealing with the REST API:
+
+| Character | Value | Replacement |
+| --------- |:-----:|:-----------:|
+| NUL       | 0x00  | ␀           |
+| /         | 0x2F  | ／           |
+
+The encoding will also encode these file names as they don&#39;t seem to
+work with the SDK properly:
+
+| File name | Replacement |
+| --------- |:-----------:|
+| .         | ．          |
+| ..        | ．．         |
+
+### Multipart uploads ###
+
+rclone supports multipart uploads with S3 which means that it can
+upload files bigger than 5GB.
+
+Note that files uploaded *both* with multipart upload *and* through
+crypt remotes do not have MD5 sums.
+
+rclone switches from single part uploads to multipart uploads at the
+point specified by `--s3-upload-cutoff`.  This can be a maximum of 5GB
+and a minimum of 0 (ie always upload multipart files).
+
+The chunk sizes used in the multipart upload are specified by
+`--s3-chunk-size` and the number of chunks uploaded concurrently is
+specified by `--s3-upload-concurrency`.
+
+Multipart uploads will use `--transfers` * `--s3-upload-concurrency` *
+`--s3-chunk-size` extra memory.  Single part uploads to not use extra
+memory.
+
+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.
+
+Increasing `--s3-upload-concurrency` will increase throughput (8 would
+be a sensible value) and increasing `--s3-chunk-size` 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.
+
+
+### Buckets and Regions ###
+
+With Amazon S3 you can list buckets (`rclone lsd`) 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, `incorrect region, the bucket is not in &#39;XXX&#39;
+region`.
+
+### Authentication ###
+
+There are a number of ways to supply `rclone` with a set of AWS
+credentials, with and without using the environment.
+
+The different authentication methods are tried in this order:
+
+ - Directly in the rclone configuration file (`env_auth = false` in the config file):
+   - `access_key_id` and `secret_access_key` are required.
+   - `session_token` can be optionally set when using AWS STS.
+ - Runtime configuration (`env_auth = true` in the config file):
+   - Export the following environment variables before running `rclone`:
+     - Access Key ID: `AWS_ACCESS_KEY_ID` or `AWS_ACCESS_KEY`
+     - Secret Access Key: `AWS_SECRET_ACCESS_KEY` or `AWS_SECRET_KEY`
+     - Session Token: `AWS_SESSION_TOKEN` (optional)
+   - Or, use a [named profile](https://docs.aws.amazon.com/cli/latest/userguide/cli-multiple-profiles.html):
+     - Profile files are standard files used by AWS CLI tools
+     - By default it will use the profile in your home directory (eg `~/.aws/credentials` on unix based systems) file and the &quot;default&quot; profile, to change set these environment variables:
+         - `AWS_SHARED_CREDENTIALS_FILE` to control which file.
+         - `AWS_PROFILE` to control which profile to use.
+   - Or, run `rclone` in an ECS task with an IAM role (AWS only).
+   - Or, run `rclone` on an EC2 instance with an IAM role (AWS only).
+   - Or, run `rclone` in an EKS pod with an IAM role that is associated with a service account (AWS only).
+
+If none of these option actually end up providing `rclone` with AWS
+credentials then S3 interaction will be non-authenticated (see below).
+
+### S3 Permissions ###
+
+When using the `sync` subcommand of `rclone` the following minimum
+permissions are required to be available on the bucket being written to:
+
+* `ListBucket`
+* `DeleteObject`
+* `GetObject`
+* `PutObject`
+* `PutObjectACL`
+
+When using the `lsd` subcommand, the `ListAllMyBuckets` permission is required.
+
+Example policy:
+</code></pre>
+<p>{ "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Principal": { "AWS": "arn:aws:iam::USER_SID:user/USER_NAME" }, "Action": [ "s3:ListBucket", "s3:DeleteObject", "s3:GetObject", "s3:PutObject", "s3:PutObjectAcl" ], "Resource": [ "arn:aws:s3:::BUCKET_NAME/*", "arn:aws:s3:::BUCKET_NAME" ] }, { "Effect": "Allow", "Action": "s3:ListAllMyBuckets", "Resource": "arn:aws:s3:::*" }<br />
+] }</p>
+<pre><code>
+Notes on above:
+
+1. This is a policy that can be used when creating bucket. It assumes
+   that `USER_NAME` has been created.
+2. The Resource entry must include both resource ARNs, as one implies
+   the bucket and the other implies the bucket&#39;s objects.
+
+For reference, [here&#39;s an Ansible script](https://gist.github.com/ebridges/ebfc9042dd7c756cd101cfa807b7ae2b)
+that will generate one or more buckets that will work with `rclone sync`.
+
+### Key Management System (KMS) ###
+
+If you are using server side encryption with KMS then you will find
+you can&#39;t transfer small objects.  As a work-around you can use the
+`--ignore-checksum` flag.
+
+A proper fix is being worked on in [issue #1824](https://github.com/rclone/rclone/issues/1824).
+
+### Glacier and Glacier Deep Archive ###
+
+You can upload objects using the glacier storage class or transition them to glacier using a [lifecycle policy](http://docs.aws.amazon.com/AmazonS3/latest/user-guide/create-lifecycle.html).
+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.
+
+    2017/09/11 19:07:43 Failed to sync: failed to open source object: Object in GLACIER, restore first: path/to/file
+
+In this case you need to [restore](http://docs.aws.amazon.com/AmazonS3/latest/user-guide/restore-archived-objects.html)
+the object(s) in question before using rclone.
+
+Note that rclone only speaks the S3 API it does not speak the Glacier
+Vault API, so rclone cannot directly access Glacier Vaults.
+
+
+### Standard Options
+
+Here are the standard options specific to s3 (Amazon S3 Compliant Storage Provider (AWS, Alibaba, Ceph, Digital Ocean, Dreamhost, IBM COS, Minio, etc)).
+
+#### --s3-provider
 
-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. Can be “myremote:path/to/dir”, “myremote:bucket”, “myremote:” or “/local/path”.</p>
-<ul>
-<li>Config: remote</li>
-<li>Env Var: RCLONE_ALIAS_REMOTE</li>
-<li>Type: string</li>
-<li>Default: ""</li>
-</ul>
-<h2 id="amazon-drive">Amazon Drive</h2>
-<p>Amazon Drive, formerly known as Amazon Cloud Drive, is a cloud storage service run by Amazon for consumers.</p>
-<h2 id="status">Status</h2>
-<p><strong>Important:</strong> rclone supports Amazon Drive only if you have your own set of API keys. Unfortunately the <a href="https://developer.amazon.com/amazon-drive">Amazon Drive developer program</a> is now closed to new entries so if you don’t already have your own set of keys you will not be able to use rclone with Amazon Drive.</p>
-<p>For the history on why rclone no longer has a set of Amazon Drive API keys see <a href="https://forum.rclone.org/t/rclone-has-been-banned-from-amazon-drive/2314">the forum</a>.</p>
-<p>If you happen to know anyone who works at Amazon then please ask them to re-instate rclone into the Amazon Drive developer program - thanks!</p>
-<h2 id="setup">Setup</h2>
-<p>The initial setup for Amazon Drive involves getting a token from Amazon which you need to do in your browser. <code>rclone config</code> walks you through it.</p>
-<p>The configuration process for Amazon Drive may involve using an <a href="https://github.com/ncw/oauthproxy">oauth proxy</a>. This is used to keep the Amazon credentials out of the source code. The proxy runs in Google’s very secure App Engine environment and doesn’t store any credentials which pass through it.</p>
-<p>Since rclone doesn’t currently have its own Amazon Drive credentials so you will either need to have your own <code>client_id</code> and <code>client_secret</code> with Amazon Drive, or use a third party oauth proxy in which case you will need to enter <code>client_id</code>, <code>client_secret</code>, <code>auth_url</code> and <code>token_url</code>.</p>
-<p>Note also if you are not using Amazon’s <code>auth_url</code> and <code>token_url</code>, (ie you filled in something for those) then if setting up on a remote machine you can only use the <a href="https://rclone.org/remote_setup/#configuring-by-copying-the-config-file">copying the config method of configuration</a> - <code>rclone authorize</code> will not work.</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 / Amazon Drive
-   \ &quot;amazon cloud drive&quot;
-[snip]
-Storage&gt; amazon cloud drive
-Amazon Application Client Id - required.
-client_id&gt; your client ID goes here
-Amazon Application Client Secret - required.
-client_secret&gt; your client secret goes here
-Auth server URL - leave blank to use Amazon&#39;s.
-auth_url&gt; Optional auth URL
-Token server url - leave blank to use Amazon&#39;s.
-token_url&gt; Optional token URL
-Remote config
-Make sure your Redirect URL is set to &quot;http://127.0.0.1:53682/&quot; in your custom config.
-Use auto config?
- * Say Y if not sure
- * Say N if you are working on a remote or headless machine
-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
---------------------
-[remote]
-client_id = your client ID goes here
-client_secret = your client secret goes here
-auth_url = Optional auth URL
-token_url = Optional token URL
-token = {&quot;access_token&quot;:&quot;xxxxxxxxxxxxxxxxxxxxxxx&quot;,&quot;token_type&quot;:&quot;bearer&quot;,&quot;refresh_token&quot;:&quot;xxxxxxxxxxxxxxxxxx&quot;,&quot;expiry&quot;:&quot;2015-09-06T16:07:39.658438471+01:00&quot;}
---------------------
-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 Amazon. 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 Amazon Drive</p>
-<pre><code>rclone lsd remote:</code></pre>
-<p>List all the files in your Amazon Drive</p>
-<pre><code>rclone ls remote:</code></pre>
-<p>To copy a local directory to an Amazon Drive directory called backup</p>
-<pre><code>rclone copy /home/source remote:backup</code></pre>
-<h3 id="modified-time-and-md5sums">Modified time and MD5SUMs</h3>
-<p>Amazon Drive doesn’t allow modification times to be changed via the API so these won’t be accurate or used for syncing.</p>
-<p>It does store MD5SUMs so for a more accurate sync, you can use the <code>--checksum</code> flag.</p>
-<h4 id="restricted-filename-characters-1">Restricted filename characters</h4>
-<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="deleting-files">Deleting files</h3>
-<p>Any files you delete with rclone will end up in the trash. Amazon don’t provide an API to permanently delete files, nor to empty the trash, so you will have to do that with one of Amazon’s apps or via the Amazon Drive website. As of November 17, 2016, files are automatically deleted by Amazon from the trash after 30 days.</p>
-<h3 id="using-with-non-.com-amazon-accounts">Using with non <code>.com</code> Amazon accounts</h3>
-<p>Let’s say you usually use <code>amazon.co.uk</code>. When you authenticate with rclone it will take you to an <code>amazon.com</code> page to log in. Your <code>amazon.co.uk</code> email and password should work here just fine.</p>
-<h3 id="standard-options-2">Standard Options</h3>
-<p>Here are the standard options specific to amazon cloud drive (Amazon Drive).</p>
-<h4 id="acd-client-id">–acd-client-id</h4>
-<p>Amazon Application Client ID.</p>
-<ul>
-<li>Config: client_id</li>
-<li>Env Var: RCLONE_ACD_CLIENT_ID</li>
-<li>Type: string</li>
-<li>Default: ""</li>
-</ul>
-<h4 id="acd-client-secret">–acd-client-secret</h4>
-<p>Amazon Application Client Secret.</p>
-<ul>
-<li>Config: client_secret</li>
-<li>Env Var: RCLONE_ACD_CLIENT_SECRET</li>
-<li>Type: string</li>
-<li>Default: ""</li>
-</ul>
-<h3 id="advanced-options-1">Advanced Options</h3>
-<p>Here are the advanced options specific to amazon cloud drive (Amazon Drive).</p>
-<h4 id="acd-auth-url">–acd-auth-url</h4>
-<p>Auth server URL. Leave blank to use Amazon’s.</p>
-<ul>
-<li>Config: auth_url</li>
-<li>Env Var: RCLONE_ACD_AUTH_URL</li>
-<li>Type: string</li>
-<li>Default: ""</li>
-</ul>
-<h4 id="acd-token-url">–acd-token-url</h4>
-<p>Token server url. leave blank to use Amazon’s.</p>
-<ul>
-<li>Config: token_url</li>
-<li>Env Var: RCLONE_ACD_TOKEN_URL</li>
-<li>Type: string</li>
-<li>Default: ""</li>
-</ul>
-<h4 id="acd-checkpoint">–acd-checkpoint</h4>
-<p>Checkpoint for internal polling (debug).</p>
-<ul>
-<li>Config: checkpoint</li>
-<li>Env Var: RCLONE_ACD_CHECKPOINT</li>
-<li>Type: string</li>
-<li>Default: ""</li>
-</ul>
-<h4 id="acd-upload-wait-per-gb">–acd-upload-wait-per-gb</h4>
-<p>Additional time per GB to wait after a failed complete upload to see if it appears.</p>
-<p>Sometimes Amazon Drive gives an error when a file has been fully uploaded but the file appears anyway after a little while. This happens sometimes for files over 1GB in size and nearly every time for files bigger than 10GB. This parameter controls the time rclone waits for the file to appear.</p>
-<p>The default value for this parameter is 3 minutes per GB, so by default it will wait 3 minutes for every GB uploaded to see if the file appears.</p>
-<p>You can disable this feature by setting it to 0. This may cause conflict errors as rclone retries the failed upload but the file will most likely appear correctly eventually.</p>
-<p>These values were determined empirically by observing lots of uploads of big files for a range of file sizes.</p>
-<p>Upload with the “-v” flag to see more info about what rclone is doing in this situation.</p>
-<ul>
-<li>Config: upload_wait_per_gb</li>
-<li>Env Var: RCLONE_ACD_UPLOAD_WAIT_PER_GB</li>
-<li>Type: Duration</li>
-<li>Default: 3m0s</li>
-</ul>
-<h4 id="acd-templink-threshold">–acd-templink-threshold</h4>
-<p>Files &gt;= this size will be downloaded via their tempLink.</p>
-<p>Files this size or more will be downloaded via their “tempLink”. This is to work around a problem with Amazon Drive which blocks downloads of files bigger than about 10GB. The default for this is 9GB which shouldn’t need to be changed.</p>
-<p>To download files above this threshold, rclone requests a “tempLink” which downloads the file through a temporary URL directly from the underlying S3 storage.</p>
-<ul>
-<li>Config: templink_threshold</li>
-<li>Env Var: RCLONE_ACD_TEMPLINK_THRESHOLD</li>
-<li>Type: SizeSuffix</li>
-<li>Default: 9G</li>
-</ul>
-<h4 id="acd-encoding">–acd-encoding</h4>
-<p>This sets 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>
-<ul>
-<li>Config: encoding</li>
-<li>Env Var: RCLONE_ACD_ENCODING</li>
-<li>Type: MultiEncoder</li>
-<li>Default: Slash,InvalidUtf8,Dot</li>
-</ul>
-<h3 id="limitations-2">Limitations</h3>
-<p>Note that Amazon Drive is case insensitive so you can’t have a file called “Hello.doc” and one called “hello.doc”.</p>
-<p>Amazon Drive has rate limiting so you may notice errors in the sync (429 errors). rclone will automatically retry the sync up to 3 times by default (see <code>--retries</code> flag) which should hopefully work around this problem.</p>
-<p>Amazon Drive has an internal limit of file sizes that can be uploaded to the service. This limit is not officially published, but all files larger than this will fail.</p>
-<p>At the time of writing (Jan 2016) is in the area of 50GB per file. This means that larger files are likely to fail.</p>
-<p>Unfortunately there is no way for rclone to see that this failure is because of file size, so it will retry the operation, as any other failure. To avoid this problem, use <code>--max-size 50000M</code> option to limit the maximum size of uploaded files. Note that <code>--max-size</code> does not split files into segments, it only ignores files over this size.</p>
-<h2 id="amazon-s3-storage-providers">Amazon S3 Storage Providers</h2>
-<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>DigitalOcean Spaces</li>
-<li>Dreamhost</li>
-<li>IBM COS S3</li>
-<li>Minio</li>
-<li>Scaleway</li>
-<li>StackPath</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, eg <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 /home/local/directory remote:bucket</code></pre>
-<h2 id="amazon-s3">AWS S3</h2>
-<p>Here is an example of making an s3 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; remote
-Type of storage to configure.
-Choose a number from below, or type in your own value
-[snip]
-XX / Amazon S3 Compliant Storage Providers (AWS, Ceph, Dreamhost, IBM COS, Minio)
-   \ &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 / Digital Ocean 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 Patific (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;
-storage_class&gt; 1
-Remote config
---------------------
-[remote]
-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 = 
---------------------
-y) Yes this is OK
-e) Edit this remote
-d) Delete this remote
-y/e/d&gt; </code></pre>
-<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="update-and-use-server-modtime">–update and –use-server-modtime</h3>
-<p>As noted below, the modified time is stored on metadata on the object. It 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 because it requires an extra API call to retrieve the metadata.</p>
-<p>For many operations, the time the object was last uploaded to the remote is sufficient to determine if it is “dirty”. By using <code>--update</code> along with <code>--use-server-modtime</code>, you can avoid the extra API call and simply upload files whose local modtime is newer than the time it was last uploaded.</p>
-<h3 id="modified-time">Modified time</h3>
-<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>
-<h4 id="restricted-filename-characters-2">Restricted filename characters</h4>
-<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 5GB.</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 5GB 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-4">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-multiple-profiles.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 (eg <code>~/.aws/credentials</code> on unix based systems) file and the “default” profile, to change set these environment variables:
-<ul>
-<li><code>AWS_SHARED_CREDENTIALS_FILE</code> to control which file.</li>
-<li><code>AWS_PROFILE</code> to control which profile to use.</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>
-</ul></li>
-</ul>
-<p>If none of these option actually end up providing <code>rclone</code> with AWS credentials then S3 interaction will be non-authenticated (see below).</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>
-</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>
-</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 will find you can’t transfer small objects. As a work-around you can use the <code>--ignore-checksum</code> flag.</p>
-<p>A proper fix is being worked on in <a href="https://github.com/rclone/rclone/issues/1824">issue #1824</a>.</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="standard-options-3">Standard Options</h3>
-<p>Here are the standard options specific to s3 (Amazon S3 Compliant Storage Provider (AWS, Alibaba, Ceph, Digital Ocean, Dreamhost, IBM COS, Minio, etc)).</p>
-<h4 id="s3-provider">–s3-provider</h4>
-<p>Choose your S3 provider.</p>
-<ul>
-<li>Config: provider</li>
-<li>Env Var: RCLONE_S3_PROVIDER</li>
-<li>Type: string</li>
-<li>Default: ""</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>“Ceph”
-<ul>
-<li>Ceph Object Storage</li>
-</ul></li>
-<li>“DigitalOcean”
-<ul>
-<li>Digital Ocean Spaces</li>
-</ul></li>
-<li>“Dreamhost”
-<ul>
-<li>Dreamhost DreamObjects</li>
-</ul></li>
-<li>“IBMCOS”
-<ul>
-<li>IBM COS S3</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>“StackPath”
-<ul>
-<li>StackPath Object Storage</li>
-</ul></li>
-<li>“Wasabi”
-<ul>
-<li>Wasabi Object Storage</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). Only applies if access_key_id and secret_access_key is blank.</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. Leave blank for anonymous access or runtime credentials.</p>
-<ul>
-<li>Config: access_key_id</li>
-<li>Env Var: RCLONE_S3_ACCESS_KEY_ID</li>
-<li>Type: string</li>
-<li>Default: ""</li>
-</ul>
-<h4 id="s3-secret-access-key">–s3-secret-access-key</h4>
-<p>AWS Secret Access Key (password) Leave blank for anonymous access or runtime credentials.</p>
-<ul>
-<li>Config: secret_access_key</li>
-<li>Env Var: RCLONE_S3_SECRET_ACCESS_KEY</li>
-<li>Type: string</li>
-<li>Default: ""</li>
-</ul>
-<h4 id="s3-region">–s3-region</h4>
-<p>Region to connect to.</p>
-<ul>
-<li>Config: region</li>
-<li>Env Var: RCLONE_S3_REGION</li>
-<li>Type: string</li>
-<li>Default: ""</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-2”
-<ul>
-<li>US West (Oregon) Region</li>
-<li>Needs location constraint us-west-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>“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-north-1”
-<ul>
-<li>EU (Stockholm) Region</li>
-<li>Needs location constraint eu-north-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-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 Patific (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>
-</ul></li>
-</ul>
-<h4 id="s3-region-1">–s3-region</h4>
-<p>Region to connect to. Leave blank if you are using an S3 clone and you don’t have a region.</p>
-<ul>
-<li>Config: region</li>
-<li>Env Var: RCLONE_S3_REGION</li>
-<li>Type: string</li>
-<li>Default: ""</li>
-<li>Examples:
-<ul>
-<li>""
-<ul>
-<li>Use this if unsure. Will use v4 signatures and an empty region.</li>
-</ul></li>
-<li>“other-v2-signature”
-<ul>
-<li>Use this only if v4 signatures don’t work, eg pre Jewel/v10 CEPH.</li>
-</ul></li>
-</ul></li>
-</ul>
-<h4 id="s3-endpoint">–s3-endpoint</h4>
-<p>Endpoint for S3 API. Leave blank if using AWS to use the default endpoint for the region.</p>
-<ul>
-<li>Config: endpoint</li>
-<li>Env Var: RCLONE_S3_ENDPOINT</li>
-<li>Type: string</li>
-<li>Default: ""</li>
-</ul>
-<h4 id="s3-endpoint-1">–s3-endpoint</h4>
-<p>Endpoint for IBM COS S3 API. Specify if using an IBM COS On Premise.</p>
-<ul>
-<li>Config: endpoint</li>
-<li>Env Var: RCLONE_S3_ENDPOINT</li>
-<li>Type: string</li>
-<li>Default: ""</li>
-<li>Examples:
-<ul>
-<li>“s3-api.us-geo.objectstorage.softlayer.net”
-<ul>
-<li>US Cross Region Endpoint</li>
-</ul></li>
-<li>“s3-api.dal.us-geo.objectstorage.softlayer.net”
-<ul>
-<li>US Cross Region Dallas Endpoint</li>
-</ul></li>
-<li>“s3-api.wdc-us-geo.objectstorage.softlayer.net”
-<ul>
-<li>US Cross Region Washington DC Endpoint</li>
-</ul></li>
-<li>“s3-api.sjc-us-geo.objectstorage.softlayer.net”
-<ul>
-<li>US Cross Region San Jose Endpoint</li>
-</ul></li>
-<li>“s3-api.us-geo.objectstorage.service.networklayer.com”
-<ul>
-<li>US Cross Region Private Endpoint</li>
-</ul></li>
-<li>“s3-api.dal-us-geo.objectstorage.service.networklayer.com”
-<ul>
-<li>US Cross Region Dallas Private Endpoint</li>
-</ul></li>
-<li>“s3-api.wdc-us-geo.objectstorage.service.networklayer.com”
-<ul>
-<li>US Cross Region Washington DC Private Endpoint</li>
-</ul></li>
-<li>“s3-api.sjc-us-geo.objectstorage.service.networklayer.com”
-<ul>
-<li>US Cross Region San Jose Private Endpoint</li>
-</ul></li>
-<li>“s3.us-east.objectstorage.softlayer.net”
-<ul>
-<li>US Region East Endpoint</li>
-</ul></li>
-<li>“s3.us-east.objectstorage.service.networklayer.com”
-<ul>
-<li>US Region East Private Endpoint</li>
-</ul></li>
-<li>“s3.us-south.objectstorage.softlayer.net”
-<ul>
-<li>US Region South Endpoint</li>
-</ul></li>
-<li>“s3.us-south.objectstorage.service.networklayer.com”
-<ul>
-<li>US Region South Private Endpoint</li>
-</ul></li>
-<li>“s3.eu-geo.objectstorage.softlayer.net”
-<ul>
-<li>EU Cross Region Endpoint</li>
-</ul></li>
-<li>“s3.fra-eu-geo.objectstorage.softlayer.net”
-<ul>
-<li>EU Cross Region Frankfurt Endpoint</li>
-</ul></li>
-<li>“s3.mil-eu-geo.objectstorage.softlayer.net”
-<ul>
-<li>EU Cross Region Milan Endpoint</li>
-</ul></li>
-<li>“s3.ams-eu-geo.objectstorage.softlayer.net”
-<ul>
-<li>EU Cross Region Amsterdam Endpoint</li>
-</ul></li>
-<li>“s3.eu-geo.objectstorage.service.networklayer.com”
-<ul>
-<li>EU Cross Region Private Endpoint</li>
-</ul></li>
-<li>“s3.fra-eu-geo.objectstorage.service.networklayer.com”
-<ul>
-<li>EU Cross Region Frankfurt Private Endpoint</li>
-</ul></li>
-<li>“s3.mil-eu-geo.objectstorage.service.networklayer.com”
-<ul>
-<li>EU Cross Region Milan Private Endpoint</li>
-</ul></li>
-<li>“s3.ams-eu-geo.objectstorage.service.networklayer.com”
-<ul>
-<li>EU Cross Region Amsterdam Private Endpoint</li>
-</ul></li>
-<li>“s3.eu-gb.objectstorage.softlayer.net”
-<ul>
-<li>Great Britain Endpoint</li>
-</ul></li>
-<li>“s3.eu-gb.objectstorage.service.networklayer.com”
-<ul>
-<li>Great Britain Private Endpoint</li>
-</ul></li>
-<li>“s3.ap-geo.objectstorage.softlayer.net”
-<ul>
-<li>APAC Cross Regional Endpoint</li>
-</ul></li>
-<li>“s3.tok-ap-geo.objectstorage.softlayer.net”
-<ul>
-<li>APAC Cross Regional Tokyo Endpoint</li>
-</ul></li>
-<li>“s3.hkg-ap-geo.objectstorage.softlayer.net”
-<ul>
-<li>APAC Cross Regional HongKong Endpoint</li>
-</ul></li>
-<li>“s3.seo-ap-geo.objectstorage.softlayer.net”
-<ul>
-<li>APAC Cross Regional Seoul Endpoint</li>
-</ul></li>
-<li>“s3.ap-geo.objectstorage.service.networklayer.com”
-<ul>
-<li>APAC Cross Regional Private Endpoint</li>
-</ul></li>
-<li>“s3.tok-ap-geo.objectstorage.service.networklayer.com”
-<ul>
-<li>APAC Cross Regional Tokyo Private Endpoint</li>
-</ul></li>
-<li>“s3.hkg-ap-geo.objectstorage.service.networklayer.com”
-<ul>
-<li>APAC Cross Regional HongKong Private Endpoint</li>
-</ul></li>
-<li>“s3.seo-ap-geo.objectstorage.service.networklayer.com”
-<ul>
-<li>APAC Cross Regional Seoul Private Endpoint</li>
-</ul></li>
-<li>“s3.mel01.objectstorage.softlayer.net”
-<ul>
-<li>Melbourne Single Site Endpoint</li>
-</ul></li>
-<li>“s3.mel01.objectstorage.service.networklayer.com”
-<ul>
-<li>Melbourne Single Site Private Endpoint</li>
-</ul></li>
-<li>“s3.tor01.objectstorage.softlayer.net”
-<ul>
-<li>Toronto Single Site Endpoint</li>
-</ul></li>
-<li>“s3.tor01.objectstorage.service.networklayer.com”
-<ul>
-<li>Toronto Single Site Private Endpoint</li>
-</ul></li>
-</ul></li>
-</ul>
-<h4 id="s3-endpoint-2">–s3-endpoint</h4>
-<p>Endpoint for OSS API.</p>
-<ul>
-<li>Config: endpoint</li>
-<li>Env Var: RCLONE_S3_ENDPOINT</li>
-<li>Type: string</li>
-<li>Default: ""</li>
-<li>Examples:
-<ul>
-<li>“oss-cn-hangzhou.aliyuncs.com”
-<ul>
-<li>East China 1 (Hangzhou)</li>
-</ul></li>
-<li>“oss-cn-shanghai.aliyuncs.com”
-<ul>
-<li>East China 2 (Shanghai)</li>
-</ul></li>
-<li>“oss-cn-qingdao.aliyuncs.com”
-<ul>
-<li>North China 1 (Qingdao)</li>
-</ul></li>
-<li>“oss-cn-beijing.aliyuncs.com”
-<ul>
-<li>North China 2 (Beijing)</li>
-</ul></li>
-<li>“oss-cn-zhangjiakou.aliyuncs.com”
-<ul>
-<li>North China 3 (Zhangjiakou)</li>
-</ul></li>
-<li>“oss-cn-huhehaote.aliyuncs.com”
-<ul>
-<li>North China 5 (Huhehaote)</li>
-</ul></li>
-<li>“oss-cn-shenzhen.aliyuncs.com”
-<ul>
-<li>South China 1 (Shenzhen)</li>
-</ul></li>
-<li>“oss-cn-hongkong.aliyuncs.com”
-<ul>
-<li>Hong Kong (Hong Kong)</li>
-</ul></li>
-<li>“oss-us-west-1.aliyuncs.com”
-<ul>
-<li>US West 1 (Silicon Valley)</li>
-</ul></li>
-<li>“oss-us-east-1.aliyuncs.com”
-<ul>
-<li>US East 1 (Virginia)</li>
-</ul></li>
-<li>“oss-ap-southeast-1.aliyuncs.com”
-<ul>
-<li>Southeast Asia Southeast 1 (Singapore)</li>
-</ul></li>
-<li>“oss-ap-southeast-2.aliyuncs.com”
-<ul>
-<li>Asia Pacific Southeast 2 (Sydney)</li>
-</ul></li>
-<li>“oss-ap-southeast-3.aliyuncs.com”
-<ul>
-<li>Southeast Asia Southeast 3 (Kuala Lumpur)</li>
-</ul></li>
-<li>“oss-ap-southeast-5.aliyuncs.com”
-<ul>
-<li>Asia Pacific Southeast 5 (Jakarta)</li>
-</ul></li>
-<li>“oss-ap-northeast-1.aliyuncs.com”
-<ul>
-<li>Asia Pacific Northeast 1 (Japan)</li>
-</ul></li>
-<li>“oss-ap-south-1.aliyuncs.com”
-<ul>
-<li>Asia Pacific South 1 (Mumbai)</li>
-</ul></li>
-<li>“oss-eu-central-1.aliyuncs.com”
-<ul>
-<li>Central Europe 1 (Frankfurt)</li>
-</ul></li>
-<li>“oss-eu-west-1.aliyuncs.com”
-<ul>
-<li>West Europe (London)</li>
-</ul></li>
-<li>“oss-me-east-1.aliyuncs.com”
-<ul>
-<li>Middle East 1 (Dubai)</li>
-</ul></li>
-</ul></li>
-</ul>
-<h4 id="s3-endpoint-3">–s3-endpoint</h4>
-<p>Endpoint for StackPath Object Storage.</p>
-<ul>
-<li>Config: endpoint</li>
-<li>Env Var: RCLONE_S3_ENDPOINT</li>
-<li>Type: string</li>
-<li>Default: ""</li>
-<li>Examples:
-<ul>
-<li>“s3.us-east-2.stackpathstorage.com”
-<ul>
-<li>US East Endpoint</li>
-</ul></li>
-<li>“s3.us-west-1.stackpathstorage.com”
-<ul>
-<li>US West Endpoint</li>
-</ul></li>
-<li>“s3.eu-central-1.stackpathstorage.com”
-<ul>
-<li>EU Endpoint</li>
-</ul></li>
-</ul></li>
-</ul>
-<h4 id="s3-endpoint-4">–s3-endpoint</h4>
-<p>Endpoint for S3 API. Required when using an S3 clone.</p>
-<ul>
-<li>Config: endpoint</li>
-<li>Env Var: RCLONE_S3_ENDPOINT</li>
-<li>Type: string</li>
-<li>Default: ""</li>
-<li>Examples:
-<ul>
-<li>“objects-us-east-1.dream.io”
-<ul>
-<li>Dream Objects endpoint</li>
-</ul></li>
-<li>“nyc3.digitaloceanspaces.com”
-<ul>
-<li>Digital Ocean Spaces New York 3</li>
-</ul></li>
-<li>“ams3.digitaloceanspaces.com”
-<ul>
-<li>Digital Ocean Spaces Amsterdam 3</li>
-</ul></li>
-<li>“sgp1.digitaloceanspaces.com”
-<ul>
-<li>Digital Ocean Spaces Singapore 1</li>
-</ul></li>
-<li>“s3.wasabisys.com”
-<ul>
-<li>Wasabi US East endpoint</li>
-</ul></li>
-<li>“s3.us-west-1.wasabisys.com”
-<ul>
-<li>Wasabi US West endpoint</li>
-</ul></li>
-<li>“s3.eu-central-1.wasabisys.com”
-<ul>
-<li>Wasabi EU Central endpoint</li>
-</ul></li>
-</ul></li>
-</ul>
-<h4 id="s3-location-constraint">–s3-location-constraint</h4>
-<p>Location constraint - must be set to match the Region. Used when creating buckets only.</p>
-<ul>
-<li>Config: location_constraint</li>
-<li>Env Var: RCLONE_S3_LOCATION_CONSTRAINT</li>
-<li>Type: string</li>
-<li>Default: ""</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-2”
-<ul>
-<li>US West (Oregon) Region.</li>
-</ul></li>
-<li>“us-west-1”
-<ul>
-<li>US West (Northern California) 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-north-1”
-<ul>
-<li>EU (Stockholm) 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)</li>
-</ul></li>
-<li>“ap-south-1”
-<ul>
-<li>Asia Pacific (Mumbai)</li>
-</ul></li>
-<li>“ap-east-1”
-<ul>
-<li>Asia Pacific (Hong Kong)</li>
-</ul></li>
-<li>“sa-east-1”
-<ul>
-<li>South America (Sao Paulo) Region.</li>
-</ul></li>
-</ul></li>
-</ul>
-<h4 id="s3-location-constraint-1">–s3-location-constraint</h4>
-<p>Location constraint - must match endpoint when using IBM Cloud Public. For on-prem COS, do not make a selection from this list, hit enter</p>
-<ul>
-<li>Config: location_constraint</li>
-<li>Env Var: RCLONE_S3_LOCATION_CONSTRAINT</li>
-<li>Type: string</li>
-<li>Default: ""</li>
-<li>Examples:
-<ul>
-<li>“us-standard”
-<ul>
-<li>US Cross Region Standard</li>
-</ul></li>
-<li>“us-vault”
-<ul>
-<li>US Cross Region Vault</li>
-</ul></li>
-<li>“us-cold”
-<ul>
-<li>US Cross Region Cold</li>
-</ul></li>
-<li>“us-flex”
-<ul>
-<li>US Cross Region Flex</li>
-</ul></li>
-<li>“us-east-standard”
-<ul>
-<li>US East Region Standard</li>
-</ul></li>
-<li>“us-east-vault”
-<ul>
-<li>US East Region Vault</li>
-</ul></li>
-<li>“us-east-cold”
-<ul>
-<li>US East Region Cold</li>
-</ul></li>
-<li>“us-east-flex”
-<ul>
-<li>US East Region Flex</li>
-</ul></li>
-<li>“us-south-standard”
-<ul>
-<li>US South Region Standard</li>
-</ul></li>
-<li>“us-south-vault”
-<ul>
-<li>US South Region Vault</li>
-</ul></li>
-<li>“us-south-cold”
-<ul>
-<li>US South Region Cold</li>
-</ul></li>
-<li>“us-south-flex”
-<ul>
-<li>US South Region Flex</li>
-</ul></li>
-<li>“eu-standard”
-<ul>
-<li>EU Cross Region Standard</li>
-</ul></li>
-<li>“eu-vault”
-<ul>
-<li>EU Cross Region Vault</li>
-</ul></li>
-<li>“eu-cold”
-<ul>
-<li>EU Cross Region Cold</li>
-</ul></li>
-<li>“eu-flex”
-<ul>
-<li>EU Cross Region Flex</li>
-</ul></li>
-<li>“eu-gb-standard”
-<ul>
-<li>Great Britain Standard</li>
-</ul></li>
-<li>“eu-gb-vault”
-<ul>
-<li>Great Britain Vault</li>
-</ul></li>
-<li>“eu-gb-cold”
-<ul>
-<li>Great Britain Cold</li>
-</ul></li>
-<li>“eu-gb-flex”
-<ul>
-<li>Great Britain Flex</li>
-</ul></li>
-<li>“ap-standard”
-<ul>
-<li>APAC Standard</li>
-</ul></li>
-<li>“ap-vault”
-<ul>
-<li>APAC Vault</li>
-</ul></li>
-<li>“ap-cold”
-<ul>
-<li>APAC Cold</li>
-</ul></li>
-<li>“ap-flex”
-<ul>
-<li>APAC Flex</li>
-</ul></li>
-<li>“mel01-standard”
-<ul>
-<li>Melbourne Standard</li>
-</ul></li>
-<li>“mel01-vault”
-<ul>
-<li>Melbourne Vault</li>
-</ul></li>
-<li>“mel01-cold”
-<ul>
-<li>Melbourne Cold</li>
-</ul></li>
-<li>“mel01-flex”
-<ul>
-<li>Melbourne Flex</li>
-</ul></li>
-<li>“tor01-standard”
-<ul>
-<li>Toronto Standard</li>
-</ul></li>
-<li>“tor01-vault”
-<ul>
-<li>Toronto Vault</li>
-</ul></li>
-<li>“tor01-cold”
-<ul>
-<li>Toronto Cold</li>
-</ul></li>
-<li>“tor01-flex”
-<ul>
-<li>Toronto Flex</li>
-</ul></li>
-</ul></li>
-</ul>
-<h4 id="s3-location-constraint-2">–s3-location-constraint</h4>
-<p>Location constraint - must be set to match the Region. Leave blank if not sure. Used when creating buckets only.</p>
-<ul>
-<li>Config: location_constraint</li>
-<li>Env Var: RCLONE_S3_LOCATION_CONSTRAINT</li>
-<li>Type: string</li>
-<li>Default: ""</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>
-<ul>
-<li>Config: acl</li>
-<li>Env Var: RCLONE_S3_ACL</li>
-<li>Type: string</li>
-<li>Default: ""</li>
-<li>Examples:
-<ul>
-<li>“private”
-<ul>
-<li>Owner gets FULL_CONTROL. No one else has access rights (default).</li>
-</ul></li>
-<li>“public-read”
-<ul>
-<li>Owner gets FULL_CONTROL. The AllUsers group gets READ access.</li>
-</ul></li>
-<li>“public-read-write”
-<ul>
-<li>Owner gets FULL_CONTROL. 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. The AuthenticatedUsers group gets READ access.</li>
-</ul></li>
-<li>“bucket-owner-read”
-<ul>
-<li>Object owner gets FULL_CONTROL. 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. No one else has access rights (default). 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. The AllUsers group gets READ access. 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. The AllUsers group gets READ and WRITE access. This acl is available on IBM Cloud (Infra), On-Premise IBM COS</li>
-</ul></li>
-<li>“authenticated-read”
-<ul>
-<li>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</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>
-<ul>
-<li>Config: server_side_encryption</li>
-<li>Env Var: RCLONE_S3_SERVER_SIDE_ENCRYPTION</li>
-<li>Type: string</li>
-<li>Default: ""</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>
-<ul>
-<li>Config: sse_kms_key_id</li>
-<li>Env Var: RCLONE_S3_SSE_KMS_KEY_ID</li>
-<li>Type: string</li>
-<li>Default: ""</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>
-<ul>
-<li>Config: storage_class</li>
-<li>Env Var: RCLONE_S3_STORAGE_CLASS</li>
-<li>Type: string</li>
-<li>Default: ""</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>
-</ul></li>
-</ul>
-<h4 id="s3-storage-class-1">–s3-storage-class</h4>
-<p>The storage class to use when storing new objects in OSS.</p>
-<ul>
-<li>Config: storage_class</li>
-<li>Env Var: RCLONE_S3_STORAGE_CLASS</li>
-<li>Type: string</li>
-<li>Default: ""</li>
-<li>Examples:
-<ul>
-<li>""
-<ul>
-<li>Default</li>
-</ul></li>
-<li>“STANDARD”
-<ul>
-<li>Standard storage class</li>
-</ul></li>
-<li>“GLACIER”
-<ul>
-<li>Archive storage mode.</li>
-</ul></li>
-<li>“STANDARD_IA”
-<ul>
-<li>Infrequent access storage mode.</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 Provider (AWS, Alibaba, Ceph, Digital Ocean, Dreamhost, IBM COS, Minio, etc)).</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>
-<ul>
-<li>Config: bucket_acl</li>
-<li>Env Var: RCLONE_S3_BUCKET_ACL</li>
-<li>Type: string</li>
-<li>Default: ""</li>
-<li>Examples:
-<ul>
-<li>“private”
-<ul>
-<li>Owner gets FULL_CONTROL. No one else has access rights (default).</li>
-</ul></li>
-<li>“public-read”
-<ul>
-<li>Owner gets FULL_CONTROL. The AllUsers group gets READ access.</li>
-</ul></li>
-<li>“public-read-write”
-<ul>
-<li>Owner gets FULL_CONTROL. 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. The AuthenticatedUsers group gets READ access.</li>
-</ul></li>
-</ul></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>
-<ul>
-<li>Config: sse_customer_algorithm</li>
-<li>Env Var: RCLONE_S3_SSE_CUSTOMER_ALGORITHM</li>
-<li>Type: string</li>
-<li>Default: ""</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>If using SSE-C you must provide the secret encryption key used to encrypt/decrypt your data.</p>
-<ul>
-<li>Config: sse_customer_key</li>
-<li>Env Var: RCLONE_S3_SSE_CUSTOMER_KEY</li>
-<li>Type: string</li>
-<li>Default: ""</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 must provide the secret encryption key MD5 checksum.</p>
-<ul>
-<li>Config: sse_customer_key_md5</li>
-<li>Env Var: RCLONE_S3_SSE_CUSTOMER_KEY_MD5</li>
-<li>Type: string</li>
-<li>Default: ""</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 5GB.</p>
-<ul>
-<li>Config: upload_cutoff</li>
-<li>Env Var: RCLONE_S3_UPLOAD_CUTOFF</li>
-<li>Type: SizeSuffix</li>
-<li>Default: 200M</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 (eg 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 5MB and there can be at most 10,000 chunks, this means that by default the maximum size of file you can stream upload is 48GB. If you wish to stream upload larger files then you will need to increase chunk_size.</p>
-<ul>
-<li>Config: chunk_size</li>
-<li>Env Var: RCLONE_S3_CHUNK_SIZE</li>
-<li>Type: SizeSuffix</li>
-<li>Default: 5M</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 5GB.</p>
-<ul>
-<li>Config: copy_cutoff</li>
-<li>Env Var: RCLONE_S3_COPY_CUTOFF</li>
-<li>Type: SizeSuffix</li>
-<li>Default: 5G</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>
-<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-session-token">–s3-session-token</h4>
-<p>An AWS session token</p>
-<ul>
-<li>Config: session_token</li>
-<li>Env Var: RCLONE_S3_SESSION_TOKEN</li>
-<li>Type: string</li>
-<li>Default: ""</li>
-</ul>
-<h4 id="s3-upload-concurrency">–s3-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 file over high speed link and these uploads do not fully utilize your bandwidth, then increasing this may help to speed up the transfers.</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 (eg AWS, Aliyun OSS or Netease COS) require this set to false - rclone will do this automatically based on the provider setting.</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, eg pre Jewel/v10 CEPH.</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-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>
-<ul>
-<li>Config: use_accelerate_endpoint</li>
-<li>Env Var: RCLONE_S3_USE_ACCELERATE_ENDPOINT</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>
-<ul>
-<li>Config: leave_parts_on_error</li>
-<li>Env Var: RCLONE_S3_LEAVE_PARTS_ON_ERROR</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>
-<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-encoding">–s3-encoding</h4>
-<p>This sets 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>
-<ul>
-<li>Config: encoding</li>
-<li>Env Var: RCLONE_S3_ENCODING</li>
-<li>Type: MultiEncoder</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. Uploads which requires additional buffers (f.e multipart) will use memory pool for allocations. This option controls how often unused buffers will be removed from the pool.</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.</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>
-<h3 id="anonymous-access-to-public-buckets">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
-env_auth = false
-access_key_id = 
-secret_access_key = 
-region = us-east-1
-endpoint = 
-location_constraint = 
-acl = private
-server_side_encryption = 
-storage_class = </code></pre>
-<p>Then use it as normal with the name of the public bucket, eg</p>
-<pre><code>rclone lsd anons3:1000genomes</code></pre>
-<p>You will be able to list and copy data but not upload it.</p>
-<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, eg 10.2.x Jewel, 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="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="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="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
-    1 / Alias for an existing remote
-    \ &quot;alias&quot;
-    2 / Amazon Drive
-    \ &quot;amazon cloud drive&quot;
-    3 / Amazon S3 Complaint Storage Providers (Dreamhost, Ceph, Minio, IBM COS)
-    \ &quot;s3&quot;
-    4 / Backblaze B2
-    \ &quot;b2&quot;
-[snip]
-    23 / http Connection
-    \ &quot;http&quot;
-Storage&gt; 3</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 enpoint 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 (Strorage) 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="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
+- Config:      provider
+- Env Var:     RCLONE_S3_PROVIDER
+- Type:        string
+- Default:     &quot;&quot;
+- Examples:
+    - &quot;AWS&quot;
+        - Amazon Web Services (AWS) S3
+    - &quot;Alibaba&quot;
+        - Alibaba Cloud Object Storage System (OSS) formerly Aliyun
+    - &quot;Ceph&quot;
+        - Ceph Object Storage
+    - &quot;DigitalOcean&quot;
+        - Digital Ocean Spaces
+    - &quot;Dreamhost&quot;
+        - Dreamhost DreamObjects
+    - &quot;IBMCOS&quot;
+        - IBM COS S3
+    - &quot;Minio&quot;
+        - Minio Object Storage
+    - &quot;Netease&quot;
+        - Netease Object Storage (NOS)
+    - &quot;Scaleway&quot;
+        - Scaleway Object Storage
+    - &quot;StackPath&quot;
+        - StackPath Object Storage
+    - &quot;Wasabi&quot;
+        - Wasabi Object Storage
+    - &quot;Other&quot;
+        - Any other S3 compatible provider
 
-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
+#### --s3-env-auth
 
-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="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
-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 =
-acl = private
-force_path_style = false
-server_side_encryption =
-storage_class =</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, 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; 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]
- 4 / Amazon S3 Compliant Storage Provider (AWS, Alibaba, Ceph, Digital Ocean, Dreamhost, IBM COS, Minio, etc)
-   \ &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
+
+- Config:      env_auth
+- Env Var:     RCLONE_S3_ENV_AUTH
+- Type:        bool
+- Default:     false
+- Examples:
+    - &quot;false&quot;
+        - Enter AWS credentials in the next step
+    - &quot;true&quot;
+        - Get AWS credentials from the environment (env vars or IAM)
+
+#### --s3-access-key-id
+
 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
+
+- Config:      access_key_id
+- Env Var:     RCLONE_S3_ACCESS_KEY_ID
+- Type:        string
+- Default:     &quot;&quot;
+
+#### --s3-secret-access-key
+
 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
+
+- Config:      secret_access_key
+- Env Var:     RCLONE_S3_SECRET_ACCESS_KEY
+- Type:        string
+- Default:     &quot;&quot;
+
+#### --s3-region
+
+Region to connect to.
+
+- Config:      region
+- Env Var:     RCLONE_S3_REGION
+- Type:        string
+- Default:     &quot;&quot;
+- Examples:
+    - &quot;us-east-1&quot;
+        - The default endpoint - a good choice if you are unsure.
+        - US Region, Northern Virginia or Pacific Northwest.
+        - Leave location constraint empty.
+    - &quot;us-east-2&quot;
+        - US East (Ohio) Region
+        - Needs location constraint us-east-2.
+    - &quot;us-west-2&quot;
+        - US West (Oregon) Region
+        - Needs location constraint us-west-2.
+    - &quot;us-west-1&quot;
+        - US West (Northern California) Region
+        - Needs location constraint us-west-1.
+    - &quot;ca-central-1&quot;
+        - Canada (Central) Region
+        - Needs location constraint ca-central-1.
+    - &quot;eu-west-1&quot;
+        - EU (Ireland) Region
+        - Needs location constraint EU or eu-west-1.
+    - &quot;eu-west-2&quot;
+        - EU (London) Region
+        - Needs location constraint eu-west-2.
+    - &quot;eu-north-1&quot;
+        - EU (Stockholm) Region
+        - Needs location constraint eu-north-1.
+    - &quot;eu-central-1&quot;
+        - EU (Frankfurt) Region
+        - Needs location constraint eu-central-1.
+    - &quot;ap-southeast-1&quot;
+        - Asia Pacific (Singapore) Region
+        - Needs location constraint ap-southeast-1.
+    - &quot;ap-southeast-2&quot;
+        - Asia Pacific (Sydney) Region
+        - Needs location constraint ap-southeast-2.
+    - &quot;ap-northeast-1&quot;
+        - Asia Pacific (Tokyo) Region
+        - Needs location constraint ap-northeast-1.
+    - &quot;ap-northeast-2&quot;
+        - Asia Pacific (Seoul)
+        - Needs location constraint ap-northeast-2.
+    - &quot;ap-south-1&quot;
+        - Asia Pacific (Mumbai)
+        - Needs location constraint ap-south-1.
+    - &quot;ap-east-1&quot;
+        - Asia Patific (Hong Kong) Region
+        - Needs location constraint ap-east-1.
+    - &quot;sa-east-1&quot;
+        - South America (Sao Paulo) Region
+        - Needs location constraint sa-east-1.
+
+#### --s3-region
+
+Region to connect to.
+
+- Config:      region
+- Env Var:     RCLONE_S3_REGION
+- Type:        string
+- Default:     &quot;&quot;
+- Examples:
+    - &quot;nl-ams&quot;
+        - Amsterdam, The Netherlands
+    - &quot;fr-par&quot;
+        - Paris, France
+
+#### --s3-region
+
+Region to connect to.
+Leave blank if you are using an S3 clone and you don&#39;t have a region.
+
+- Config:      region
+- Env Var:     RCLONE_S3_REGION
+- Type:        string
+- Default:     &quot;&quot;
+- Examples:
+    - &quot;&quot;
+        - Use this if unsure. Will use v4 signatures and an empty region.
+    - &quot;other-v2-signature&quot;
+        - Use this only if v4 signatures don&#39;t work, eg pre Jewel/v10 CEPH.
+
+#### --s3-endpoint
+
+Endpoint for S3 API.
+Leave blank if using AWS to use the default endpoint for the region.
+
+- Config:      endpoint
+- Env Var:     RCLONE_S3_ENDPOINT
+- Type:        string
+- Default:     &quot;&quot;
+
+#### --s3-endpoint
+
+Endpoint for IBM COS S3 API.
+Specify if using an IBM COS On Premise.
+
+- Config:      endpoint
+- Env Var:     RCLONE_S3_ENDPOINT
+- Type:        string
+- Default:     &quot;&quot;
+- Examples:
+    - &quot;s3.us.cloud-object-storage.appdomain.cloud&quot;
+        - US Cross Region Endpoint
+    - &quot;s3.dal.us.cloud-object-storage.appdomain.cloud&quot;
+        - US Cross Region Dallas Endpoint
+    - &quot;s3.wdc.us.cloud-object-storage.appdomain.cloud&quot;
+        - US Cross Region Washington DC Endpoint
+    - &quot;s3.sjc.us.cloud-object-storage.appdomain.cloud&quot;
+        - US Cross Region San Jose Endpoint
+    - &quot;s3.private.us.cloud-object-storage.appdomain.cloud&quot;
+        - US Cross Region Private Endpoint
+    - &quot;s3.private.dal.us.cloud-object-storage.appdomain.cloud&quot;
+        - US Cross Region Dallas Private Endpoint
+    - &quot;s3.private.wdc.us.cloud-object-storage.appdomain.cloud&quot;
+        - US Cross Region Washington DC Private Endpoint
+    - &quot;s3.private.sjc.us.cloud-object-storage.appdomain.cloud&quot;
+        - US Cross Region San Jose Private Endpoint
+    - &quot;s3.us-east.cloud-object-storage.appdomain.cloud&quot;
+        - US Region East Endpoint
+    - &quot;s3.private.us-east.cloud-object-storage.appdomain.cloud&quot;
+        - US Region East Private Endpoint
+    - &quot;s3.us-south.cloud-object-storage.appdomain.cloud&quot;
+        - US Region South Endpoint
+    - &quot;s3.private.us-south.cloud-object-storage.appdomain.cloud&quot;
+        - US Region South Private Endpoint
+    - &quot;s3.eu.cloud-object-storage.appdomain.cloud&quot;
+        - EU Cross Region Endpoint
+    - &quot;s3.fra.eu.cloud-object-storage.appdomain.cloud&quot;
+        - EU Cross Region Frankfurt Endpoint
+    - &quot;s3.mil.eu.cloud-object-storage.appdomain.cloud&quot;
+        - EU Cross Region Milan Endpoint
+    - &quot;s3.ams.eu.cloud-object-storage.appdomain.cloud&quot;
+        - EU Cross Region Amsterdam Endpoint
+    - &quot;s3.private.eu.cloud-object-storage.appdomain.cloud&quot;
+        - EU Cross Region Private Endpoint
+    - &quot;s3.private.fra.eu.cloud-object-storage.appdomain.cloud&quot;
+        - EU Cross Region Frankfurt Private Endpoint
+    - &quot;s3.private.mil.eu.cloud-object-storage.appdomain.cloud&quot;
+        - EU Cross Region Milan Private Endpoint
+    - &quot;s3.private.ams.eu.cloud-object-storage.appdomain.cloud&quot;
+        - EU Cross Region Amsterdam Private Endpoint
+    - &quot;s3.eu-gb.cloud-object-storage.appdomain.cloud&quot;
+        - Great Britain Endpoint
+    - &quot;s3.private.eu-gb.cloud-object-storage.appdomain.cloud&quot;
+        - Great Britain Private Endpoint
+    - &quot;s3.eu-de.cloud-object-storage.appdomain.cloud&quot;
+        - EU Region DE Endpoint
+    - &quot;s3.private.eu-de.cloud-object-storage.appdomain.cloud&quot;
+        - EU Region DE Private Endpoint
+    - &quot;s3.ap.cloud-object-storage.appdomain.cloud&quot;
+        - APAC Cross Regional Endpoint
+    - &quot;s3.tok.ap.cloud-object-storage.appdomain.cloud&quot;
+        - APAC Cross Regional Tokyo Endpoint
+    - &quot;s3.hkg.ap.cloud-object-storage.appdomain.cloud&quot;
+        - APAC Cross Regional HongKong Endpoint
+    - &quot;s3.seo.ap.cloud-object-storage.appdomain.cloud&quot;
+        - APAC Cross Regional Seoul Endpoint
+    - &quot;s3.private.ap.cloud-object-storage.appdomain.cloud&quot;
+        - APAC Cross Regional Private Endpoint
+    - &quot;s3.private.tok.ap.cloud-object-storage.appdomain.cloud&quot;
+        - APAC Cross Regional Tokyo Private Endpoint
+    - &quot;s3.private.hkg.ap.cloud-object-storage.appdomain.cloud&quot;
+        - APAC Cross Regional HongKong Private Endpoint
+    - &quot;s3.private.seo.ap.cloud-object-storage.appdomain.cloud&quot;
+        - APAC Cross Regional Seoul Private Endpoint
+    - &quot;s3.jp-tok.cloud-object-storage.appdomain.cloud&quot;
+        - APAC Region Japan Endpoint
+    - &quot;s3.private.jp-tok.cloud-object-storage.appdomain.cloud&quot;
+        - APAC Region Japan Private Endpoint
+    - &quot;s3.au-syd.cloud-object-storage.appdomain.cloud&quot;
+        - APAC Region Australia Endpoint
+    - &quot;s3.private.au-syd.cloud-object-storage.appdomain.cloud&quot;
+        - APAC Region Australia Private Endpoint
+    - &quot;s3.ams03.cloud-object-storage.appdomain.cloud&quot;
+        - Amsterdam Single Site Endpoint
+    - &quot;s3.private.ams03.cloud-object-storage.appdomain.cloud&quot;
+        - Amsterdam Single Site Private Endpoint
+    - &quot;s3.che01.cloud-object-storage.appdomain.cloud&quot;
+        - Chennai Single Site Endpoint
+    - &quot;s3.private.che01.cloud-object-storage.appdomain.cloud&quot;
+        - Chennai Single Site Private Endpoint
+    - &quot;s3.mel01.cloud-object-storage.appdomain.cloud&quot;
+        - Melbourne Single Site Endpoint
+    - &quot;s3.private.mel01.cloud-object-storage.appdomain.cloud&quot;
+        - Melbourne Single Site Private Endpoint
+    - &quot;s3.osl01.cloud-object-storage.appdomain.cloud&quot;
+        - Oslo Single Site Endpoint
+    - &quot;s3.private.osl01.cloud-object-storage.appdomain.cloud&quot;
+        - Oslo Single Site Private Endpoint
+    - &quot;s3.tor01.cloud-object-storage.appdomain.cloud&quot;
+        - Toronto Single Site Endpoint
+    - &quot;s3.private.tor01.cloud-object-storage.appdomain.cloud&quot;
+        - Toronto Single Site Private Endpoint
+    - &quot;s3.seo01.cloud-object-storage.appdomain.cloud&quot;
+        - Seoul Single Site Endpoint
+    - &quot;s3.private.seo01.cloud-object-storage.appdomain.cloud&quot;
+        - Seoul Single Site Private Endpoint
+    - &quot;s3.mon01.cloud-object-storage.appdomain.cloud&quot;
+        - Montreal Single Site Endpoint
+    - &quot;s3.private.mon01.cloud-object-storage.appdomain.cloud&quot;
+        - Montreal Single Site Private Endpoint
+    - &quot;s3.mex01.cloud-object-storage.appdomain.cloud&quot;
+        - Mexico Single Site Endpoint
+    - &quot;s3.private.mex01.cloud-object-storage.appdomain.cloud&quot;
+        - Mexico Single Site Private Endpoint
+    - &quot;s3.sjc04.cloud-object-storage.appdomain.cloud&quot;
+        - San Jose Single Site Endpoint
+    - &quot;s3.private.sjc04.cloud-object-storage.appdomain.cloud&quot;
+        - San Jose Single Site Private Endpoint
+    - &quot;s3.mil01.cloud-object-storage.appdomain.cloud&quot;
+        - Milan Single Site Endpoint
+    - &quot;s3.private.mil01.cloud-object-storage.appdomain.cloud&quot;
+        - Milan Single Site Private Endpoint
+    - &quot;s3.hkg02.cloud-object-storage.appdomain.cloud&quot;
+        - Hong Kong Single Site Endpoint
+    - &quot;s3.private.hkg02.cloud-object-storage.appdomain.cloud&quot;
+        - Hong Kong Single Site Private Endpoint
+    - &quot;s3.par01.cloud-object-storage.appdomain.cloud&quot;
+        - Paris Single Site Endpoint
+    - &quot;s3.private.par01.cloud-object-storage.appdomain.cloud&quot;
+        - Paris Single Site Private Endpoint
+    - &quot;s3.sng01.cloud-object-storage.appdomain.cloud&quot;
+        - Singapore Single Site Endpoint
+    - &quot;s3.private.sng01.cloud-object-storage.appdomain.cloud&quot;
+        - Singapore Single Site Private Endpoint
+
+#### --s3-endpoint
+
 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
+
+- Config:      endpoint
+- Env Var:     RCLONE_S3_ENDPOINT
+- Type:        string
+- Default:     &quot;&quot;
+- Examples:
+    - &quot;oss-cn-hangzhou.aliyuncs.com&quot;
+        - East China 1 (Hangzhou)
+    - &quot;oss-cn-shanghai.aliyuncs.com&quot;
+        - East China 2 (Shanghai)
+    - &quot;oss-cn-qingdao.aliyuncs.com&quot;
+        - North China 1 (Qingdao)
+    - &quot;oss-cn-beijing.aliyuncs.com&quot;
+        - North China 2 (Beijing)
+    - &quot;oss-cn-zhangjiakou.aliyuncs.com&quot;
+        - North China 3 (Zhangjiakou)
+    - &quot;oss-cn-huhehaote.aliyuncs.com&quot;
+        - North China 5 (Huhehaote)
+    - &quot;oss-cn-shenzhen.aliyuncs.com&quot;
+        - South China 1 (Shenzhen)
+    - &quot;oss-cn-hongkong.aliyuncs.com&quot;
+        - Hong Kong (Hong Kong)
+    - &quot;oss-us-west-1.aliyuncs.com&quot;
+        - US West 1 (Silicon Valley)
+    - &quot;oss-us-east-1.aliyuncs.com&quot;
+        - US East 1 (Virginia)
+    - &quot;oss-ap-southeast-1.aliyuncs.com&quot;
+        - Southeast Asia Southeast 1 (Singapore)
+    - &quot;oss-ap-southeast-2.aliyuncs.com&quot;
+        - Asia Pacific Southeast 2 (Sydney)
+    - &quot;oss-ap-southeast-3.aliyuncs.com&quot;
+        - Southeast Asia Southeast 3 (Kuala Lumpur)
+    - &quot;oss-ap-southeast-5.aliyuncs.com&quot;
+        - Asia Pacific Southeast 5 (Jakarta)
+    - &quot;oss-ap-northeast-1.aliyuncs.com&quot;
+        - Asia Pacific Northeast 1 (Japan)
+    - &quot;oss-ap-south-1.aliyuncs.com&quot;
+        - Asia Pacific South 1 (Mumbai)
+    - &quot;oss-eu-central-1.aliyuncs.com&quot;
+        - Central Europe 1 (Frankfurt)
+    - &quot;oss-eu-west-1.aliyuncs.com&quot;
+        - West Europe (London)
+    - &quot;oss-me-east-1.aliyuncs.com&quot;
+        - Middle East 1 (Dubai)
+
+#### --s3-endpoint
+
+Endpoint for Scaleway Object Storage.
+
+- Config:      endpoint
+- Env Var:     RCLONE_S3_ENDPOINT
+- Type:        string
+- Default:     &quot;&quot;
+- Examples:
+    - &quot;s3.nl-ams.scw.cloud&quot;
+        - Amsterdam Endpoint
+    - &quot;s3.fr-par.scw.cloud&quot;
+        - Paris Endpoint
+
+#### --s3-endpoint
+
+Endpoint for StackPath Object Storage.
+
+- Config:      endpoint
+- Env Var:     RCLONE_S3_ENDPOINT
+- Type:        string
+- Default:     &quot;&quot;
+- Examples:
+    - &quot;s3.us-east-2.stackpathstorage.com&quot;
+        - US East Endpoint
+    - &quot;s3.us-west-1.stackpathstorage.com&quot;
+        - US West Endpoint
+    - &quot;s3.eu-central-1.stackpathstorage.com&quot;
+        - EU Endpoint
+
+#### --s3-endpoint
+
+Endpoint for S3 API.
+Required when using an S3 clone.
+
+- Config:      endpoint
+- Env Var:     RCLONE_S3_ENDPOINT
+- Type:        string
+- Default:     &quot;&quot;
+- Examples:
+    - &quot;objects-us-east-1.dream.io&quot;
+        - Dream Objects endpoint
+    - &quot;nyc3.digitaloceanspaces.com&quot;
+        - Digital Ocean Spaces New York 3
+    - &quot;ams3.digitaloceanspaces.com&quot;
+        - Digital Ocean Spaces Amsterdam 3
+    - &quot;sgp1.digitaloceanspaces.com&quot;
+        - Digital Ocean Spaces Singapore 1
+    - &quot;s3.wasabisys.com&quot;
+        - Wasabi US East endpoint
+    - &quot;s3.us-west-1.wasabisys.com&quot;
+        - Wasabi US West endpoint
+    - &quot;s3.eu-central-1.wasabisys.com&quot;
+        - Wasabi EU Central endpoint
+
+#### --s3-location-constraint
+
+Location constraint - must be set to match the Region.
+Used when creating buckets only.
+
+- Config:      location_constraint
+- Env Var:     RCLONE_S3_LOCATION_CONSTRAINT
+- Type:        string
+- Default:     &quot;&quot;
+- Examples:
+    - &quot;&quot;
+        - Empty for US Region, Northern Virginia or Pacific Northwest.
+    - &quot;us-east-2&quot;
+        - US East (Ohio) Region.
+    - &quot;us-west-2&quot;
+        - US West (Oregon) Region.
+    - &quot;us-west-1&quot;
+        - US West (Northern California) Region.
+    - &quot;ca-central-1&quot;
+        - Canada (Central) Region.
+    - &quot;eu-west-1&quot;
+        - EU (Ireland) Region.
+    - &quot;eu-west-2&quot;
+        - EU (London) Region.
+    - &quot;eu-north-1&quot;
+        - EU (Stockholm) Region.
+    - &quot;EU&quot;
+        - EU Region.
+    - &quot;ap-southeast-1&quot;
+        - Asia Pacific (Singapore) Region.
+    - &quot;ap-southeast-2&quot;
+        - Asia Pacific (Sydney) Region.
+    - &quot;ap-northeast-1&quot;
+        - Asia Pacific (Tokyo) Region.
+    - &quot;ap-northeast-2&quot;
+        - Asia Pacific (Seoul)
+    - &quot;ap-south-1&quot;
+        - Asia Pacific (Mumbai)
+    - &quot;ap-east-1&quot;
+        - Asia Pacific (Hong Kong)
+    - &quot;sa-east-1&quot;
+        - South America (Sao Paulo) Region.
+
+#### --s3-location-constraint
+
+Location constraint - must match endpoint when using IBM Cloud Public.
+For on-prem COS, do not make a selection from this list, hit enter
+
+- Config:      location_constraint
+- Env Var:     RCLONE_S3_LOCATION_CONSTRAINT
+- Type:        string
+- Default:     &quot;&quot;
+- Examples:
+    - &quot;us-standard&quot;
+        - US Cross Region Standard
+    - &quot;us-vault&quot;
+        - US Cross Region Vault
+    - &quot;us-cold&quot;
+        - US Cross Region Cold
+    - &quot;us-flex&quot;
+        - US Cross Region Flex
+    - &quot;us-east-standard&quot;
+        - US East Region Standard
+    - &quot;us-east-vault&quot;
+        - US East Region Vault
+    - &quot;us-east-cold&quot;
+        - US East Region Cold
+    - &quot;us-east-flex&quot;
+        - US East Region Flex
+    - &quot;us-south-standard&quot;
+        - US South Region Standard
+    - &quot;us-south-vault&quot;
+        - US South Region Vault
+    - &quot;us-south-cold&quot;
+        - US South Region Cold
+    - &quot;us-south-flex&quot;
+        - US South Region Flex
+    - &quot;eu-standard&quot;
+        - EU Cross Region Standard
+    - &quot;eu-vault&quot;
+        - EU Cross Region Vault
+    - &quot;eu-cold&quot;
+        - EU Cross Region Cold
+    - &quot;eu-flex&quot;
+        - EU Cross Region Flex
+    - &quot;eu-gb-standard&quot;
+        - Great Britain Standard
+    - &quot;eu-gb-vault&quot;
+        - Great Britain Vault
+    - &quot;eu-gb-cold&quot;
+        - Great Britain Cold
+    - &quot;eu-gb-flex&quot;
+        - Great Britain Flex
+    - &quot;ap-standard&quot;
+        - APAC Standard
+    - &quot;ap-vault&quot;
+        - APAC Vault
+    - &quot;ap-cold&quot;
+        - APAC Cold
+    - &quot;ap-flex&quot;
+        - APAC Flex
+    - &quot;mel01-standard&quot;
+        - Melbourne Standard
+    - &quot;mel01-vault&quot;
+        - Melbourne Vault
+    - &quot;mel01-cold&quot;
+        - Melbourne Cold
+    - &quot;mel01-flex&quot;
+        - Melbourne Flex
+    - &quot;tor01-standard&quot;
+        - Toronto Standard
+    - &quot;tor01-vault&quot;
+        - Toronto Vault
+    - &quot;tor01-cold&quot;
+        - Toronto Cold
+    - &quot;tor01-flex&quot;
+        - Toronto Flex
+
+#### --s3-location-constraint
+
+Location constraint - must be set to match the Region.
+Leave blank if not sure. Used when creating buckets only.
+
+- Config:      location_constraint
+- Env Var:     RCLONE_S3_LOCATION_CONSTRAINT
+- Type:        string
+- Default:     &quot;&quot;
+
+#### --s3-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.
-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
+
+- Config:      acl
+- Env Var:     RCLONE_S3_ACL
+- Type:        string
+- Default:     &quot;&quot;
+- Examples:
+    - &quot;private&quot;
+        - Owner gets FULL_CONTROL. No one else has access rights (default).
+    - &quot;public-read&quot;
+        - Owner gets FULL_CONTROL. The AllUsers group gets READ access.
+    - &quot;public-read-write&quot;
+        - Owner gets FULL_CONTROL. The AllUsers group gets READ and WRITE access.
+        - Granting this on a bucket is generally not recommended.
+    - &quot;authenticated-read&quot;
+        - Owner gets FULL_CONTROL. The AuthenticatedUsers group gets READ access.
+    - &quot;bucket-owner-read&quot;
+        - Object owner gets FULL_CONTROL. Bucket owner gets READ access.
+        - If you specify this canned ACL when creating a bucket, Amazon S3 ignores it.
+    - &quot;bucket-owner-full-control&quot;
+        - Both the object owner and the bucket owner get FULL_CONTROL over the object.
+        - If you specify this canned ACL when creating a bucket, Amazon S3 ignores it.
+    - &quot;private&quot;
+        - 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;public-read&quot;
+        - 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-write&quot;
+        - 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;authenticated-read&quot;
+        - 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
+
+#### --s3-server-side-encryption
+
+The server-side encryption algorithm used when storing this object in S3.
+
+- Config:      server_side_encryption
+- Env Var:     RCLONE_S3_SERVER_SIDE_ENCRYPTION
+- Type:        string
+- Default:     &quot;&quot;
+- Examples:
+    - &quot;&quot;
+        - None
+    - &quot;AES256&quot;
+        - AES256
+    - &quot;aws:kms&quot;
+        - aws:kms
+
+#### --s3-sse-kms-key-id
+
+If using KMS ID you must provide the ARN of Key.
+
+- Config:      sse_kms_key_id
+- Env Var:     RCLONE_S3_SSE_KMS_KEY_ID
+- Type:        string
+- Default:     &quot;&quot;
+- Examples:
+    - &quot;&quot;
+        - None
+    - &quot;arn:aws:kms:us-east-1:*&quot;
+        - arn:aws:kms:*
+
+#### --s3-storage-class
+
+The storage class to use when storing new objects in S3.
+
+- Config:      storage_class
+- Env Var:     RCLONE_S3_STORAGE_CLASS
+- Type:        string
+- Default:     &quot;&quot;
+- Examples:
+    - &quot;&quot;
+        - Default
+    - &quot;STANDARD&quot;
+        - Standard storage class
+    - &quot;REDUCED_REDUNDANCY&quot;
+        - Reduced redundancy storage class
+    - &quot;STANDARD_IA&quot;
+        - Standard Infrequent Access storage class
+    - &quot;ONEZONE_IA&quot;
+        - One Zone Infrequent Access storage class
+    - &quot;GLACIER&quot;
+        - Glacier storage class
+    - &quot;DEEP_ARCHIVE&quot;
+        - Glacier Deep Archive storage class
+    - &quot;INTELLIGENT_TIERING&quot;
+        - Intelligent-Tiering storage class
+
+#### --s3-storage-class
+
 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="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>
-<h2 id="backblaze-b2">Backblaze B2</h2>
-<p>B2 is <a href="https://www.backblaze.com/b2/">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, eg <code>remote:bucket/path/to/dir</code>.</p>
-<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
---------------------
-[remote]
-account = 123456789abc
-key = 0123456789abcdef0123456789abcdef0123456789
-endpoint =
---------------------
-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 /home/local/directory remote:bucket</code></pre>
-<h3 id="application-keys">Application Keys</h3>
-<p>B2 supports multiple <a href="https://www.backblaze.com/b2/docs/application_keys.html">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-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="modified-time-1">Modified time</h3>
-<p>The modified 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>
-<h4 id="restricted-filename-characters-3">Restricted filename characters</h4>
-<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>
-<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 MB by default) will use a 96 MB 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">Versions</h3>
-<p>When rclone uploads a new version of a file it creates a <a href="https://www.backblaze.com/b2/docs/file_versions.html">new version of it</a>. Likewise when you delete a file, the old version will be marked hidden and still be available. Conversely, you may opt in to a “hard delete” of files with the <code>--b2-hard-delete</code> flag which would permanently remove the file instead of hiding it.</p>
-<p>Old versions of files, where available, are visible using the <code>--b2-versions</code> flag.</p>
-<p><strong>NB</strong> Note that <code>--b2-versions</code> does not work with crypt at the moment <a href="https://github.com/rclone/rclone/issues/1627">#1627</a>. Using <a href="https://rclone.org/docs/#backup-dir-dir">–backup-dir</a> with rclone is the recommended way of working around this.</p>
-<p>If you wish to remove all the old versions 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, eg <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.</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
+- Config:      storage_class
+- Env Var:     RCLONE_S3_STORAGE_CLASS
+- Type:        string
+- Default:     &quot;&quot;
+- Examples:
+    - &quot;&quot;
+        - Default
+    - &quot;STANDARD&quot;
+        - Standard storage class
+    - &quot;GLACIER&quot;
+        - Archive storage mode.
+    - &quot;STANDARD_IA&quot;
+        - Infrequent access storage mode.
 
-$ 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
+#### --s3-storage-class
 
-$ rclone -q ls b2:cleanup-test
-        9 one.txt
+The storage class to use when storing new objects in S3.
 
-$ rclone -q --b2-versions ls b2:cleanup-test
-        9 one.txt</code></pre>
-<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-1">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
+- Config:      storage_class
+- Env Var:     RCLONE_S3_STORAGE_CLASS
+- Type:        string
+- Default:     &quot;&quot;
+- Examples:
+    - &quot;&quot;
+        - Default
+    - &quot;STANDARD&quot;
+        - The Standard class for any upload; suitable for on-demand content like streaming or CDN.
+    - &quot;GLACIER&quot;
+        - Archived storage; prices are lower, but it needs to be restored first to be accessed.
+
+### Advanced Options
+
+Here are the advanced options specific to s3 (Amazon S3 Compliant Storage Provider (AWS, Alibaba, Ceph, Digital Ocean, Dreamhost, IBM COS, Minio, etc)).
+
+#### --s3-bucket-acl
+
+Canned ACL used when creating buckets.
+
+For more info visit https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html#canned-acl
+
+Note that this ACL is applied when only when creating buckets.  If it
+isn&#39;t set then &quot;acl&quot; is used instead.
+
+- Config:      bucket_acl
+- Env Var:     RCLONE_S3_BUCKET_ACL
+- Type:        string
+- Default:     &quot;&quot;
+- Examples:
+    - &quot;private&quot;
+        - Owner gets FULL_CONTROL. No one else has access rights (default).
+    - &quot;public-read&quot;
+        - Owner gets FULL_CONTROL. The AllUsers group gets READ access.
+    - &quot;public-read-write&quot;
+        - Owner gets FULL_CONTROL. The AllUsers group gets READ and WRITE access.
+        - Granting this on a bucket is generally not recommended.
+    - &quot;authenticated-read&quot;
+        - Owner gets FULL_CONTROL. The AuthenticatedUsers group gets READ access.
+
+#### --s3-sse-customer-algorithm
+
+If using SSE-C, the server-side encryption algorithm used when storing this object in S3.
+
+- Config:      sse_customer_algorithm
+- Env Var:     RCLONE_S3_SSE_CUSTOMER_ALGORITHM
+- Type:        string
+- Default:     &quot;&quot;
+- Examples:
+    - &quot;&quot;
+        - None
+    - &quot;AES256&quot;
+        - AES256
+
+#### --s3-sse-customer-key
+
+If using SSE-C you must provide the secret encryption key used to encrypt/decrypt your data.
+
+- Config:      sse_customer_key
+- Env Var:     RCLONE_S3_SSE_CUSTOMER_KEY
+- Type:        string
+- Default:     &quot;&quot;
+- Examples:
+    - &quot;&quot;
+        - None
+
+#### --s3-sse-customer-key-md5
+
+If using SSE-C you must provide the secret encryption key MD5 checksum.
+
+- Config:      sse_customer_key_md5
+- Env Var:     RCLONE_S3_SSE_CUSTOMER_KEY_MD5
+- Type:        string
+- Default:     &quot;&quot;
+- Examples:
+    - &quot;&quot;
+        - None
+
+#### --s3-upload-cutoff
+
+Cutoff for switching to chunked upload
+
+Any files larger than this will be uploaded in chunks of chunk_size.
+The minimum is 0 and the maximum is 5GB.
+
+- Config:      upload_cutoff
+- Env Var:     RCLONE_S3_UPLOAD_CUTOFF
+- Type:        SizeSuffix
+- Default:     200M
+
+#### --s3-chunk-size
+
+Chunk size to use for uploading.
+
+When uploading files larger than upload_cutoff or files with unknown
+size (eg from &quot;rclone rcat&quot; or uploaded with &quot;rclone mount&quot; or google
+photos or google docs) they will be uploaded as multipart uploads
+using this chunk size.
+
+Note that &quot;--s3-upload-concurrency&quot; chunks of this size are buffered
+in memory per transfer.
+
+If you are transferring large files over high speed links and you have
+enough memory, then increasing this will speed up the transfers.
+
+Rclone will automatically increase the chunk size when uploading a
+large file of known size to stay below the 10,000 chunks limit.
+
+Files of unknown size are uploaded with the configured
+chunk_size. Since the default chunk size is 5MB and there can be at
+most 10,000 chunks, this means that by default the maximum size of
+file you can stream upload is 48GB.  If you wish to stream upload
+larger files then you will need to increase chunk_size.
+
+- Config:      chunk_size
+- Env Var:     RCLONE_S3_CHUNK_SIZE
+- Type:        SizeSuffix
+- Default:     5M
+
+#### --s3-max-upload-parts
+
+Maximum number of parts in a multipart upload.
+
+This option defines the maximum number of multipart chunks to use
+when doing a multipart upload.
+
+This can be useful if a service does not support the AWS S3
+specification of 10,000 chunks.
+
+Rclone will automatically increase the chunk size when uploading a
+large file of a known size to stay below this number of chunks limit.
+
+
+- Config:      max_upload_parts
+- Env Var:     RCLONE_S3_MAX_UPLOAD_PARTS
+- Type:        int
+- Default:     10000
+
+#### --s3-copy-cutoff
+
+Cutoff for switching to multipart copy
+
+Any files larger than this that need to be server side copied will be
+copied in chunks of this size.
+
+The minimum is 0 and the maximum is 5GB.
+
+- Config:      copy_cutoff
+- Env Var:     RCLONE_S3_COPY_CUTOFF
+- Type:        SizeSuffix
+- Default:     4.656G
+
+#### --s3-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 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.
+
+- Config:      disable_checksum
+- Env Var:     RCLONE_S3_DISABLE_CHECKSUM
+- Type:        bool
+- Default:     false
+
+#### --s3-shared-credentials-file
+
+Path to the shared credentials file
+
+If env_auth = true then rclone can use a shared credentials file.
+
+If this variable is empty rclone will look for the
+&quot;AWS_SHARED_CREDENTIALS_FILE&quot; env variable. If the env value is empty
+it will default to the current user&#39;s home directory.
+
+    Linux/OSX: &quot;$HOME/.aws/credentials&quot;
+    Windows:   &quot;%USERPROFILE%\.aws\credentials&quot;
+
+
+- Config:      shared_credentials_file
+- Env Var:     RCLONE_S3_SHARED_CREDENTIALS_FILE
+- Type:        string
+- Default:     &quot;&quot;
+
+#### --s3-profile
+
+Profile to use in the shared credentials file
+
+If env_auth = true then rclone can use a shared credentials file. This
+variable controls which profile is used in that file.
+
+If empty it will default to the environment variable &quot;AWS_PROFILE&quot; or
+&quot;default&quot; if that environment variable is also not set.
+
+
+- Config:      profile
+- Env Var:     RCLONE_S3_PROFILE
+- Type:        string
+- Default:     &quot;&quot;
+
+#### --s3-session-token
+
+An AWS session token
+
+- Config:      session_token
+- Env Var:     RCLONE_S3_SESSION_TOKEN
+- Type:        string
+- Default:     &quot;&quot;
+
+#### --s3-upload-concurrency
+
+Concurrency for multipart uploads.
+
+This is the number of chunks of the same file that are uploaded
+concurrently.
+
+If you are uploading small numbers of large file over high speed link
+and these uploads do not fully utilize your bandwidth, then increasing
+this may help to speed up the transfers.
+
+- Config:      upload_concurrency
+- Env Var:     RCLONE_S3_UPLOAD_CONCURRENCY
+- Type:        int
+- Default:     4
+
+#### --s3-force-path-style
+
+If true use path style access if false use virtual hosted style.
+
+If this is true (the default) then rclone will use path style access,
+if false then rclone will use virtual path style. See [the AWS S3
+docs](https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingBucket.html#access-bucket-intro)
+for more info.
+
+Some providers (eg AWS, Aliyun OSS or Netease COS) require this set to
+false - rclone will do this automatically based on the provider
+setting.
+
+- Config:      force_path_style
+- Env Var:     RCLONE_S3_FORCE_PATH_STYLE
+- Type:        bool
+- Default:     true
+
+#### --s3-v2-auth
+
+If true use v2 authentication.
+
+If this is false (the default) then rclone will use v4 authentication.
+If it is set then rclone will use v2 authentication.
+
+Use this only if v4 signatures don&#39;t work, eg pre Jewel/v10 CEPH.
+
+- Config:      v2_auth
+- Env Var:     RCLONE_S3_V2_AUTH
+- Type:        bool
+- Default:     false
+
+#### --s3-use-accelerate-endpoint
+
+If true use the AWS S3 accelerated endpoint.
+
+See: [AWS S3 Transfer acceleration](https://docs.aws.amazon.com/AmazonS3/latest/dev/transfer-acceleration-examples.html)
+
+- Config:      use_accelerate_endpoint
+- Env Var:     RCLONE_S3_USE_ACCELERATE_ENDPOINT
+- Type:        bool
+- Default:     false
+
+#### --s3-leave-parts-on-error
+
+If true avoid calling abort upload on a failure, leaving all successfully uploaded parts on S3 for manual recovery.
+
+It should be set to true for resuming uploads across different sessions.
+
+WARNING: Storing parts of an incomplete multipart upload counts towards space usage on S3 and will add additional costs if not cleaned up.
+
+
+- Config:      leave_parts_on_error
+- Env Var:     RCLONE_S3_LEAVE_PARTS_ON_ERROR
+- Type:        bool
+- Default:     false
+
+#### --s3-list-chunk
+
+Size of listing chunk (response list for each ListObject S3 request).
+
+This option is also known as &quot;MaxKeys&quot;, &quot;max-items&quot;, or &quot;page-size&quot; 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 [AWS S3](https://docs.aws.amazon.com/cli/latest/reference/s3/ls.html).
+In Ceph, this can be increased with the &quot;rgw list buckets max chunk&quot; option.
+
+
+- Config:      list_chunk
+- Env Var:     RCLONE_S3_LIST_CHUNK
+- Type:        int
+- Default:     1000
+
+#### --s3-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.
+
+
+- Config:      no_check_bucket
+- Env Var:     RCLONE_S3_NO_CHECK_BUCKET
+- Type:        bool
+- Default:     false
+
+#### --s3-encoding
+
+This sets the encoding for the backend.
+
+See: the [encoding section in the overview](https://rclone.org/overview/#encoding) for more info.
+
+- Config:      encoding
+- Env Var:     RCLONE_S3_ENCODING
+- Type:        MultiEncoder
+- Default:     Slash,InvalidUtf8,Dot
+
+#### --s3-memory-pool-flush-time
+
+How often internal memory buffer pools will be flushed.
+Uploads which requires additional buffers (f.e multipart) will use memory pool for allocations.
+This option controls how often unused buffers will be removed from the pool.
+
+- Config:      memory_pool_flush_time
+- Env Var:     RCLONE_S3_MEMORY_POOL_FLUSH_TIME
+- Type:        Duration
+- Default:     1m0s
+
+#### --s3-memory-pool-use-mmap
+
+Whether to use mmap buffers in internal memory pool.
+
+- Config:      memory_pool_use_mmap
+- Env Var:     RCLONE_S3_MEMORY_POOL_USE_MMAP
+- Type:        bool
+- Default:     false
+
+### Backend commands
+
+Here are the commands specific to the s3 backend.
+
+Run them with
+
+    rclone backend COMMAND remote:
+
+The help below will explain what arguments each command takes.
+
+See [the &quot;rclone backend&quot; command](https://rclone.org/commands/rclone_backend/) for more
+info on how to pass options and arguments.
+
+These can be run on a running backend using the rc command
+[backend/command](https://rclone.org/rc/#backend/command).
+
+#### restore
+
+Restore objects from GLACIER to normal storage
+
+    rclone backend restore remote: [options] [&lt;arguments&gt;+]
+
+This command can be used to restore one or more objects from GLACIER
+to normal storage.
+
+Usage Examples:
+
+    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]
+
+This flag also obeys the filters. Test first with -i/--interactive or --dry-run flags
+
+    rclone -i backend restore --include &quot;*.txt&quot; s3:bucket/path -o priority=Standard
+
+All the objects shown will be marked for restore, then
+
+    rclone backend restore --include &quot;*.txt&quot; s3:bucket/path -o priority=Standard
+
+It returns a list of status dictionaries with Remote and Status
+keys. The Status will be OK if it was successfull or an error message
+if not.
+
+    [
+        {
+            &quot;Status&quot;: &quot;OK&quot;,
+            &quot;Path&quot;: &quot;test.txt&quot;
+        },
+        {
+            &quot;Status&quot;: &quot;OK&quot;,
+            &quot;Path&quot;: &quot;test/file4.txt&quot;
+        }
+    ]
+
+
+
+Options:
+
+- &quot;description&quot;: The optional description for the job.
+- &quot;lifetime&quot;: Lifetime of the active copy in days
+- &quot;priority&quot;: Priority of restore: Standard|Expedited|Bulk
+
+#### list-multipart-uploads
+
+List the unfinished multipart uploads
+
+    rclone backend list-multipart-uploads remote: [options] [&lt;arguments&gt;+]
+
+This command lists the unfinished multipart uploads in JSON format.
+
+    rclone backend list-multipart s3:bucket/path/to/object
+
+It returns a dictionary of buckets with values as lists of unfinished
+multipart uploads.
+
+You can call it with no bucket in which case it lists all bucket, with
+a bucket or with a bucket and path.
+
+    {
+      &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;: []
+    }
+
+
+
+#### cleanup
+
+Remove unfinished multipart uploads.
+
+    rclone backend cleanup remote: [options] [&lt;arguments&gt;+]
+
+This command removes unfinished multipart uploads of age greater than
+max-age which defaults to 24 hours.
+
+Note that you can use -i/--dry-run with this command to see what it
+would do.
+
+    rclone backend cleanup s3:bucket/path/to/object
+    rclone backend cleanup -o max-age=7w s3:bucket/path/to/object
+
+Durations are parsed as per the rest of rclone, 2h, 7d, 7w etc.
+
+
+Options:
+
+- &quot;max-age&quot;: Max age of upload to delete
+
+
+
+### Anonymous access to public buckets ###
+
+If you want to use rclone to access a public bucket, configure with a
+blank `access_key_id` and `secret_access_key`.  Your config should end
+up looking like this:
 </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
+<p>[anons3] type = s3 provider = AWS env_auth = false access_key_id = secret_access_key = region = us-east-1 endpoint = location_constraint = acl = private server_side_encryption = storage_class =</p>
+<pre><code>
+Then use it as normal with the name of the public bucket, eg
+
+    rclone lsd anons3:1000genomes
+
+You will be able to list and copy data but not upload it.
+
+### Ceph ###
+
+[Ceph](https://ceph.com/) is an open source unified, distributed
+storage system designed for excellent performance, reliability and
+scalability.  It has an S3 compatible object storage interface.
+
+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:
+
 </code></pre>
-<h3 id="standard-options-4">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>
-<ul>
-<li>Config: account</li>
-<li>Env Var: RCLONE_B2_ACCOUNT</li>
-<li>Type: string</li>
-<li>Default: ""</li>
-</ul>
-<h4 id="b2-key">–b2-key</h4>
-<p>Application Key</p>
-<ul>
-<li>Config: key</li>
-<li>Env Var: RCLONE_B2_KEY</li>
-<li>Type: string</li>
-<li>Default: ""</li>
-</ul>
-<h4 id="b2-hard-delete">–b2-hard-delete</h4>
-<p>Permanently delete files on remote removal, otherwise hide files.</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. Leave blank normally.</p>
-<ul>
-<li>Config: endpoint</li>
-<li>Env Var: RCLONE_B2_ENDPOINT</li>
-<li>Type: string</li>
-<li>Default: ""</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/b2/docs/integration_checklist.html">b2 integrations checklist</a>.</p>
-<ul>
-<li>Config: test_mode</li>
-<li>Env Var: RCLONE_B2_TEST_MODE</li>
-<li>Type: string</li>
-<li>Default: ""</li>
-</ul>
-<h4 id="b2-versions">–b2-versions</h4>
-<p>Include old versions in directory listings. Note that when using this no file write operations are permitted, so you can’t upload files or delete them.</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-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.657GiB (== 5GB).</p>
-<ul>
-<li>Config: upload_cutoff</li>
-<li>Env Var: RCLONE_B2_UPLOAD_CUTOFF</li>
-<li>Type: SizeSuffix</li>
-<li>Default: 200M</li>
-</ul>
-<h4 id="b2-chunk-size">–b2-chunk-size</h4>
-<p>Upload chunk size. Must fit in memory.</p>
-<p>When uploading large files, chunk the file into this size. Note that these chunks are buffered in memory and there might a maximum of “–transfers” chunks in progress at once. 5,000,000 Bytes is the minimum size.</p>
-<ul>
-<li>Config: chunk_size</li>
-<li>Env Var: RCLONE_B2_CHUNK_SIZE</li>
-<li>Type: SizeSuffix</li>
-<li>Default: 96M</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>
-<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. This is probably only useful for a public bucket. Leave blank if you want to use the endpoint provided by Backblaze.</p>
-<ul>
-<li>Config: download_url</li>
-<li>Env Var: RCLONE_B2_DOWNLOAD_URL</li>
-<li>Type: string</li>
-<li>Default: ""</li>
-</ul>
-<h4 id="b2-download-auth-duration">–b2-download-auth-duration</h4>
-<p>Time before the authorization token will expire in s or suffix ms|s|m|h|d.</p>
-<p>The duration before the download authorization token will expire. The minimum value is 1 second. The maximum value is one week.</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-encoding">–b2-encoding</h4>
-<p>This sets 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>
-<ul>
-<li>Config: encoding</li>
-<li>Env Var: RCLONE_B2_ENCODING</li>
-<li>Type: MultiEncoder</li>
-<li>Default: Slash,BackSlash,Del,Ctl,InvalidUtf8,Dot</li>
-</ul>
-<h2 id="box">Box</h2>
-<p>Paths are specified as <code>remote:path</code></p>
-<p>Paths may be as deep as required, eg <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>
-<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
+<p>[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 =</p>
+<pre><code>
+If you are using an older version of CEPH, eg 10.2.x Jewel, then you
+may need to supply the parameter `--s3-upload-cutoff 0` or put this in
+the config file as `upload_cutoff 0` to work around a bug which causes
+uploading of small files to fail.
+
+Note also that Ceph sometimes puts `/` 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 `/` escaped as `\/`.  Make sure you
+only write `/` in the secret access key.
+
+Eg the dump from Ceph looks something like this (irrelevant keys
+removed).
+</code></pre>
+<p>{ "user_id": "xxx", "display_name": "xxxx", "keys": [ { "user": "xxx", "access_key": "xxxxxx", "secret_key": "xxxxxx/xxxx" } ], }</p>
+<pre><code>
+Because this is a json dump, it is encoding the `/` as `\/`, so if you
+use the secret key as `xxxxxx/xxxx`  it will work fine.
+
+### Dreamhost ###
+
+Dreamhost [DreamObjects](https://www.dreamhost.com/cloud/storage/) is
+an object storage system based on CEPH.
+
+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:
+</code></pre>
+<p>[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 =</p>
+<pre><code>
+### DigitalOcean Spaces ###
+
+[Spaces](https://www.digitalocean.com/products/object-storage/) is an [S3-interoperable](https://developers.digitalocean.com/documentation/spaces/) object storage service from cloud provider DigitalOcean.
+
+To connect to DigitalOcean Spaces you will need an access key and secret key. These can be retrieved on the &quot;[Applications &amp; API](https://cloud.digitalocean.com/settings/api/tokens)&quot; page of the DigitalOcean control panel. They will be needed when prompted by `rclone config` for your `access_key_id` and `secret_access_key`.
+
+When prompted for a `region` or `location_constraint`, press enter to use the default value. The region must be included in the `endpoint` setting (e.g. `nyc3.digitaloceanspaces.com`). The default values can be used for other settings.
+
+Going through the whole process of creating a new remote by running `rclone config`, each prompt should be answered as shown below:
+</code></pre>
+<p>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;</p>
+<pre><code>
+The resulting configuration file should look like:
+</code></pre>
+<p>[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 =</p>
+<pre><code>
+Once configured, you can create a new Space and begin copying files. For example:
+</code></pre>
+<p>rclone mkdir spaces:my-new-space rclone copy /path/to/files spaces:my-new-space</p>
+<pre><code>
+### IBM COS (S3) ###
+
+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)
+
+To configure access to IBM COS S3, follow the steps below:
+
+1. Run rclone config and select n for a new remote.</code></pre>
+<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
-name&gt; remote
-Type of storage to configure.
+n/s/q&gt; n</code></pre>
+<pre><code>
+2. Enter the name for the configuration</code></pre>
+<pre><code>name&gt; &lt;YOUR NAME&gt;</code></pre>
+<pre><code>
+3. Select &quot;s3&quot; storage.</code></pre>
+<p>Choose a number from below, or type in your own value 1 / Alias for an existing remote  "alias" 2 / Amazon Drive  "amazon cloud drive" 3 / Amazon S3 Complaint Storage Providers (Dreamhost, Ceph, Minio, IBM COS)  "s3" 4 / Backblaze B2  "b2" [snip] 23 / http Connection  "http" Storage&gt; 3</p>
+<pre><code>
+4. Select IBM COS as the S3 Storage Provider.</code></pre>
+<p>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  "AWS" 2 / Choose this option to configure Storage to Ceph Systems  "Ceph" 3 / Choose this option to configure Storage to Dreamhost  "Dreamhost" 4 / Choose this option to the configure Storage to IBM COS S3  "IBMCOS" 5 / Choose this option to the configure Storage to Minio  "Minio" Provider&gt;4</p>
+<pre><code>
+5. Enter the Access Key and Secret.</code></pre>
+<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>
+<pre><code>
+6. Specify the endpoint for IBM COS. For Public IBM COS, choose from the option below. For On Premise IBM COS, enter an enpoint address.</code></pre>
+<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
-[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;
+ 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</code></pre>
+<p>[snip] 34 / Toronto Single Site Private Endpoint  "s3.tor01.objectstorage.service.networklayer.com" endpoint&gt;1</p>
+<pre><code>
+
+7. 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</code></pre>
+<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;</code></pre>
+<p>[snip] 32 / Toronto Flex  "tor01-flex" location_constraint&gt;1</p>
+<pre><code>
+9. Specify a canned ACL. IBM Cloud (Strorage) supports &quot;public-read&quot; and &quot;private&quot;. IBM Cloud(Infra) supports all the canned ACLs. On-Premise COS supports all the canned ACLs.</code></pre>
+<p>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  "private" 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  "public-read" 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  "public-read-write" 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  "authenticated-read" acl&gt; 1</p>
+<pre><code>
+
+12. Review the displayed configuration and accept to save the &quot;remote&quot; then quit. The config file should look like this</code></pre>
+<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>
+<pre><code>
+13. Execute rclone commands</code></pre>
+<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>
+<pre><code>
+### Minio ###
+
+[Minio](https://minio.io/) is an object storage server built for cloud application developers and devops.
+
+It is very easy to install and provides an S3 compatible server which can be used by rclone.
+
+To use it, install Minio following the instructions [here](https://docs.minio.io/docs/minio-quickstart-guide).
+
+When it configures itself Minio will print something like this
+</code></pre>
+<p>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</p>
+<p>Browser Access: http://192.168.1.106:9000 http://172.23.0.1:9000</p>
+<p>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</p>
+<p>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</p>
+<p>Drive Capacity: 26 GiB Free, 165 GiB Total</p>
+<pre><code>
+These details need to go into `rclone config` like this.  Note that it
+is important to put the region in as stated above.
+</code></pre>
+<p>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;</p>
+<pre><code>
+Which makes the config file look like this
+</code></pre>
+<p>[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 =</p>
+<pre><code>
+So once set up, for example to copy files into a bucket
+</code></pre>
+<p>rclone copy /path/to/files minio:bucket</p>
+<pre><code>
+### Scaleway {#scaleway}
+
+[Scaleway](https://www.scaleway.com/object-storage/) 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.
+
+Scaleway provides an S3 interface which can be configured for use with rclone like this:
+</code></pre>
+<p>[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 = acl = private server_side_encryption = storage_class =</p>
+<pre><code>
+### Wasabi ###
+
+[Wasabi](https://wasabi.com) 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.
+
+Wasabi provides an S3 interface which can be configured for use with
+rclone like this.
+</code></pre>
+<p>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, Minio)  "s3" [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  "false" 2 / Get AWS credentials from the environment (env vars or IAM)  "true" 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.  "us-east-1" [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.  "" [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).  "private" [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  "" 2 / AES256  "AES256" 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  "" 2 / Standard storage class  "STANDARD" 3 / Reduced redundancy storage class  "REDUCED_REDUNDANCY" 4 / Standard Infrequent Access storage class  "STANDARD_IA" 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</p>
+<pre><code>
+This will leave the config file looking like this.
+</code></pre>
+<p>[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 =</p>
+<pre><code>
+### Alibaba OSS {#alibaba-oss}
+
+Here is an example of making an [Alibaba Cloud (Aliyun) OSS](https://www.alibabacloud.com/product/oss/)
+configuration.  First run:
+
+    rclone config
+
+This will guide you through an interactive setup process.
+</code></pre>
+<p>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 (""). Choose a number from below, or type in your own value [snip] 4 / Amazon S3 Compliant Storage Provider (AWS, Alibaba, Ceph, Digital Ocean, Dreamhost, IBM COS, Minio, etc)  "s3" [snip] Storage&gt; s3 Choose your S3 provider. Enter a string value. Press Enter for the default (""). Choose a number from below, or type in your own value 1 / Amazon Web Services (AWS) S3  "AWS" 2 / Alibaba Cloud Object Storage System (OSS) formerly Aliyun  "Alibaba" 3 / Ceph Object Storage  "Ceph" [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 ("false"). Choose a number from below, or type in your own value 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 AWS Access Key ID. Leave blank for anonymous access or runtime credentials. Enter a string value. Press Enter for the default (""). 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 (""). secret_access_key&gt; secretaccesskey Endpoint for OSS API. Enter a string value. Press Enter for the default (""). Choose a number from below, or type in your own value 1 / East China 1 (Hangzhou)  "oss-cn-hangzhou.aliyuncs.com" 2 / East China 2 (Shanghai)  "oss-cn-shanghai.aliyuncs.com" 3 / North China 1 (Qingdao)  "oss-cn-qingdao.aliyuncs.com" [snip] endpoint&gt; 1 Canned ACL used when creating buckets and storing or copying objects.</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. Enter a string value. Press Enter for the default (""). Choose a number from below, or type in your own value 1 / Owner gets FULL_CONTROL. No one else has access rights (default).  "private" 2 / Owner gets FULL_CONTROL. The AllUsers group gets READ access.  "public-read" / 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 (""). Choose a number from below, or type in your own value 1 / Default  "" 2 / Standard storage class  "STANDARD" 3 / Archive storage mode.  "GLACIER" 4 / Infrequent access storage mode.  "STANDARD_IA" 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</p>
+<pre><code>
+### Netease NOS  ###
+
+For Netease NOS configure as per the configurator `rclone config`
+setting the provider `Netease`.  This will automatically set
+`force_path_style = false` which is necessary for it to run properly.
+
+ Backblaze B2
+----------------------------------------
+
+B2 is [Backblaze&#39;s cloud storage system](https://www.backblaze.com/b2/).
+
+Paths are specified as `remote:bucket` (or `remote:` for the `lsd`
+command.)  You may put subdirectories in too, eg `remote:bucket/path/to/dir`.
+
+Here is an example of making a b2 configuration.  First run
+
+    rclone config
+
+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.
+</code></pre>
+<p>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  "b2" [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 -------------------- [remote] account = 123456789abc key = 0123456789abcdef0123456789abcdef0123456789 endpoint = -------------------- y) Yes this is OK e) Edit this remote d) Delete this remote y/e/d&gt; y</p>
+<pre><code>
+This remote is called `remote` and can now be used like this
+
+See all buckets
+
+    rclone lsd remote:
+
+Create a new bucket
+
+    rclone mkdir remote:bucket
+
+List the contents of a bucket
+
+    rclone ls remote:bucket
+
+Sync `/home/local/directory` to the remote bucket, deleting any
+excess files in the bucket.
+
+    rclone sync -i /home/local/directory remote:bucket
+
+### Application Keys ###
+
+B2 supports multiple [Application Keys for different access permission
+to B2 Buckets](https://www.backblaze.com/b2/docs/application_keys.html).
+
+You can use these with rclone too; you will need to use rclone version 1.43
+or later.
+
+Follow Backblaze&#39;s docs to create an Application Key with the required
+permission and add the `applicationKeyId` as the `account` and the
+`Application Key` itself as the `key`.
+
+Note that you must put the _applicationKeyId_ as the `account` – you
+can&#39;t use the master Account ID.  If you try then B2 will return 401
+errors.
+
+### --fast-list ###
+
+This remote supports `--fast-list` which allows you to use fewer
+transactions in exchange for more memory. See the [rclone
+docs](https://rclone.org/docs/#fast-list) for more details.
+
+### Modified time ###
+
+The modified time is stored as metadata on the object as
+`X-Bz-Info-src_last_modified_millis` as milliseconds since 1970-01-01
+in the Backblaze standard.  Other tools should be able to use this as
+a modified time.
+
+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.
+
+#### Restricted filename characters
+
+In addition to the [default restricted characters set](https://rclone.org/overview/#restricted-characters)
+the following characters are also replaced:
+
+| Character | Value | Replacement |
+| --------- |:-----:|:-----------:|
+| \         | 0x5C  | ＼           |
+
+Invalid UTF-8 bytes will also be [replaced](https://rclone.org/overview/#invalid-utf8),
+as they can&#39;t be used in JSON strings.
+
+Note that in 2020-05 Backblaze started allowing \ characters in file
+names. Rclone hasn&#39;t changed its encoding as this could cause syncs to
+re-transfer files. If you want rclone not to replace \ then see the
+`--b2-encoding` flag below and remove the `BackSlash` from the
+string. This can be set in the config.
+
+### SHA1 checksums ###
+
+The SHA1 checksums of the files are checked on upload and download and
+will be used in the syncing process.
+
+Large files (bigger than the limit in `--b2-upload-cutoff`) which are
+uploaded in chunks will store their SHA1 on the object as
+`X-Bz-Info-large_file_sha1` as recommended by Backblaze.
+
+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 [the overview](https://rclone.org/overview/#features) for exactly which remotes
+support SHA1.
+
+Sources which don&#39;t support SHA1, in particular `crypt` will upload
+large files without SHA1 checksums.  This may be fixed in the future
+(see [#1767](https://github.com/rclone/rclone/issues/1767)).
+
+Files sizes below `--b2-upload-cutoff` will always have an SHA1
+regardless of the source.
+
+### Transfers ###
+
+Backblaze recommends that you do lots of transfers simultaneously for
+maximum speed.  In tests from my SSD equipped laptop the optimum
+setting is about `--transfers 32` 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 `--transfers 4` is
+definitely too low for Backblaze B2 though.
+
+Note that uploading big files (bigger than 200 MB by default) will use
+a 96 MB RAM buffer by default.  There can be at most `--transfers` of
+these in use at any moment, so this sets the upper limit on the memory
+used.
+
+### Versions ###
+
+When rclone uploads a new version of a file it creates a [new version
+of it](https://www.backblaze.com/b2/docs/file_versions.html).
+Likewise when you delete a file, the old version will be marked hidden
+and still be available.  Conversely, you may opt in to a &quot;hard delete&quot;
+of files with the `--b2-hard-delete` flag which would permanently remove
+the file instead of hiding it.
+
+Old versions of files, where available, are visible using the 
+`--b2-versions` flag.
+
+**NB** Note that `--b2-versions` does not work with crypt at the
+moment [#1627](https://github.com/rclone/rclone/issues/1627). Using
+[--backup-dir](https://rclone.org/docs/#backup-dir-dir) with rclone is the recommended
+way of working around this.
+
+If you wish to remove all the old versions then you can use the
+`rclone cleanup remote:bucket` 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,
+eg `rclone cleanup remote:bucket/path/to/stuff`.
+
+Note that `cleanup` will remove partially uploaded files from the bucket
+if they are more than a day old.
+
+When you `purge` a bucket, the current and the old versions will be
+deleted then the bucket will be deleted.
+
+However `delete` will cause the current versions of the files to
+become hidden old versions.
+
+Here is a session showing the listing and retrieval of an old
+version followed by a `cleanup` of the old versions.
+
+Show current version and all the versions with `--b2-versions` flag.
+</code></pre>
+<p>$ rclone -q ls b2:cleanup-test 9 one.txt</p>
+<p>$ 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</p>
+<pre><code>
+Retrieve an old version
+</code></pre>
+<p>$ rclone -q --b2-versions copy b2:cleanup-test/one-v2016-07-04-141003-000.txt /tmp</p>
+<p>$ 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</p>
+<pre><code>
+Clean up all the old versions and show that they&#39;ve gone.
+</code></pre>
+<p>$ rclone -q cleanup b2:cleanup-test</p>
+<p>$ rclone -q ls b2:cleanup-test 9 one.txt</p>
+<p>$ rclone -q --b2-versions ls b2:cleanup-test 9 one.txt</p>
+<pre><code>
+### Data usage ###
+
+It is useful to know how many requests are sent to the server in different scenarios.
+
+All copy commands send the following 4 requests:
+</code></pre>
+<p>/b2api/v1/b2_authorize_account /b2api/v1/b2_create_bucket /b2api/v1/b2_list_buckets /b2api/v1/b2_list_file_names</p>
+<pre><code>
+The `b2_list_file_names` 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
+[#818](https://github.com/rclone/rclone/issues/818) 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.
+
+Uploading files that do not require chunking, will send 2 requests per
+file upload:
+</code></pre>
+<p>/b2api/v1/b2_get_upload_url /b2api/v1/b2_upload_file/</p>
+<pre><code>
+Uploading files requiring chunking, will send 2 requests (one each to
+start and finish the upload) and another 2 requests for each chunk:
+</code></pre>
+<p>/b2api/v1/b2_start_large_file /b2api/v1/b2_get_upload_part_url /b2api/v1/b2_upload_part/ /b2api/v1/b2_finish_large_file</p>
+<pre><code>
+#### Versions ####
+
+Versions can be viewed with the `--b2-versions` flag. When it is set
+rclone will show and act on older versions of files.  For example
+
+Listing without `--b2-versions`
+</code></pre>
+<p>$ rclone -q ls b2:cleanup-test 9 one.txt</p>
+<pre><code>
+And with
+</code></pre>
+<p>$ 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</p>
+<pre><code>
+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.
+
+Note that when using `--b2-versions` no file write operations are
+permitted, so you can&#39;t upload files or delete them.
+
+### B2 and rclone link ###
+
+Rclone supports generating file share links for private B2 buckets.
+They can either be for a file for example:
+</code></pre>
+<p>./rclone link B2:bucket/path/to/file.txt https://f002.backblazeb2.com/file/bucket/path/to/file.txt?Authorization=xxxxxxxx</p>
+<pre><code>
+or if run on a directory you will get:
+</code></pre>
+<p>./rclone link B2:bucket/path https://f002.backblazeb2.com/file/bucket/path?Authorization=xxxxxxxx</p>
+<pre><code>
+you can then use the authorization token (the part of the url from the
+ `?Authorization=` on) on any file path under that directory. For example:
+</code></pre>
+<p>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</p>
+<pre><code>
+
+### Standard Options
+
+Here are the standard options specific to b2 (Backblaze B2).
+
+#### --b2-account
+
+Account ID or Application Key ID
+
+- Config:      account
+- Env Var:     RCLONE_B2_ACCOUNT
+- Type:        string
+- Default:     &quot;&quot;
+
+#### --b2-key
+
+Application Key
+
+- Config:      key
+- Env Var:     RCLONE_B2_KEY
+- Type:        string
+- Default:     &quot;&quot;
+
+#### --b2-hard-delete
+
+Permanently delete files on remote removal, otherwise hide files.
+
+- Config:      hard_delete
+- Env Var:     RCLONE_B2_HARD_DELETE
+- Type:        bool
+- Default:     false
+
+### Advanced Options
+
+Here are the advanced options specific to b2 (Backblaze B2).
+
+#### --b2-endpoint
+
+Endpoint for the service.
+Leave blank normally.
+
+- Config:      endpoint
+- Env Var:     RCLONE_B2_ENDPOINT
+- Type:        string
+- Default:     &quot;&quot;
+
+#### --b2-test-mode
+
+A flag string for X-Bz-Test-Mode header for debugging.
+
+This is for debugging purposes only. Setting it to one of the strings
+below will cause b2 to return specific errors:
+
+  * &quot;fail_some_uploads&quot;
+  * &quot;expire_some_account_authorization_tokens&quot;
+  * &quot;force_cap_exceeded&quot;
+
+These will be set in the &quot;X-Bz-Test-Mode&quot; header which is documented
+in the [b2 integrations checklist](https://www.backblaze.com/b2/docs/integration_checklist.html).
+
+- Config:      test_mode
+- Env Var:     RCLONE_B2_TEST_MODE
+- Type:        string
+- Default:     &quot;&quot;
+
+#### --b2-versions
+
+Include old versions in directory listings.
+Note that when using this no file write operations are permitted,
+so you can&#39;t upload files or delete them.
+
+- Config:      versions
+- Env Var:     RCLONE_B2_VERSIONS
+- Type:        bool
+- Default:     false
+
+#### --b2-upload-cutoff
+
+Cutoff for switching to chunked upload.
+
+Files above this size will be uploaded in chunks of &quot;--b2-chunk-size&quot;.
+
+This value should be set no larger than 4.657GiB (== 5GB).
+
+- Config:      upload_cutoff
+- Env Var:     RCLONE_B2_UPLOAD_CUTOFF
+- Type:        SizeSuffix
+- Default:     200M
+
+#### --b2-copy-cutoff
+
+Cutoff for switching to multipart copy
+
+Any files larger than this that need to be server side copied will be
+copied in chunks of this size.
+
+The minimum is 0 and the maximum is 4.6GB.
+
+- Config:      copy_cutoff
+- Env Var:     RCLONE_B2_COPY_CUTOFF
+- Type:        SizeSuffix
+- Default:     4G
+
+#### --b2-chunk-size
+
+Upload chunk size. Must fit in memory.
+
+When uploading large files, chunk the file into this size.  Note that
+these chunks are buffered in memory and there might a maximum of
+&quot;--transfers&quot; chunks in progress at once.  5,000,000 Bytes is the
+minimum size.
+
+- Config:      chunk_size
+- Env Var:     RCLONE_B2_CHUNK_SIZE
+- Type:        SizeSuffix
+- Default:     96M
+
+#### --b2-disable-checksum
+
+Disable checksums for large (&gt; upload cutoff) files
+
+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.
+
+- Config:      disable_checksum
+- Env Var:     RCLONE_B2_DISABLE_CHECKSUM
+- Type:        bool
+- Default:     false
+
+#### --b2-download-url
+
+Custom endpoint for downloads.
+
+This is usually set to a Cloudflare CDN URL as Backblaze offers
+free egress for data downloaded through the Cloudflare network.
+This is probably only useful for a public bucket.
+Leave blank if you want to use the endpoint provided by Backblaze.
+
+- Config:      download_url
+- Env Var:     RCLONE_B2_DOWNLOAD_URL
+- Type:        string
+- Default:     &quot;&quot;
+
+#### --b2-download-auth-duration
+
+Time before the authorization token will expire in s or suffix ms|s|m|h|d.
+
+The duration before the download authorization token will expire.
+The minimum value is 1 second. The maximum value is one week.
+
+- Config:      download_auth_duration
+- Env Var:     RCLONE_B2_DOWNLOAD_AUTH_DURATION
+- Type:        Duration
+- Default:     1w
+
+#### --b2-memory-pool-flush-time
+
+How often internal memory buffer pools will be flushed.
+Uploads which requires additional buffers (f.e multipart) will use memory pool for allocations.
+This option controls how often unused buffers will be removed from the pool.
+
+- Config:      memory_pool_flush_time
+- Env Var:     RCLONE_B2_MEMORY_POOL_FLUSH_TIME
+- Type:        Duration
+- Default:     1m0s
+
+#### --b2-memory-pool-use-mmap
+
+Whether to use mmap buffers in internal memory pool.
+
+- Config:      memory_pool_use_mmap
+- Env Var:     RCLONE_B2_MEMORY_POOL_USE_MMAP
+- Type:        bool
+- Default:     false
+
+#### --b2-encoding
+
+This sets the encoding for the backend.
+
+See: the [encoding section in the overview](https://rclone.org/overview/#encoding) for more info.
+
+- Config:      encoding
+- Env Var:     RCLONE_B2_ENCODING
+- Type:        MultiEncoder
+- Default:     Slash,BackSlash,Del,Ctl,InvalidUtf8,Dot
+
+
+
+ Box
+-----------------------------------------
+
+Paths are specified as `remote:path`
+
+Paths may be as deep as required, eg `remote:directory/subdirectory`.
+
+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.  `rclone config` walks you through it.
+
+Here is an example of how to make a remote called `remote`.  First run:
+
+     rclone config
+
+This will guide you through an interactive setup process:
+</code></pre>
+<p>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  "box" [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 (""). box_config_file&gt; Box App Primary Access Token Leave blank normally. Enter a string value. Press Enter for the default (""). access_token&gt;</p>
+<p>Enter a string value. Press Enter for the default ("user"). Choose a number from below, or type in your own value 1 / Rclone should act on behalf of a user  "user" 2 / Rclone should act on behalf of a service account  "enterprise" box_sub_type&gt; Remote config Use auto config? * Say Y if not sure * Say N if you are working on a remote or headless machine y) Yes n) No y/n&gt; y If your browser doesn'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 -------------------- [remote] client_id = client_secret = token = {"access_token":"XXX","token_type":"bearer","refresh_token":"XXX","expiry":"XXX"} -------------------- y) Yes this is OK e) Edit this remote d) Delete this remote y/e/d&gt; y</p>
+<pre><code>
+See the [remote setup docs](https://rclone.org/remote_setup/) for how to set it up on a
+machine with no Internet browser available.
+
+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 `http://127.0.0.1:53682/` and this it may require you to unblock
+it temporarily if you are running a host firewall.
+
+Once configured you can then use `rclone` like this,
+
+List directories in top level of your Box
+
+    rclone lsd remote:
+
+List all the files in your Box
+
+    rclone ls remote:
+
+To copy a local directory to an Box directory called backup
+
+    rclone copy /home/source remote:backup
+
+### Using rclone with an Enterprise account with SSO ###
+
+If you have an &quot;Enterprise&quot; 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, &quot;Account&quot;
+Tab, and then set the password in the &quot;Authentication&quot; field.
+
+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.
+
+### Invalid refresh token ###
+
+According to the [box docs](https://developer.box.com/v2.0/docs/oauth-20#section-6-using-the-access-and-refresh-tokens):
+
+&gt; Each refresh_token is valid for one use in 60 days.
+
+This means that if you
+
+  * Don&#39;t use the box remote for 60 days
+  * Copy the config file with a box refresh token in and use it in two places
+  * Get an error on a token refresh
+
+then rclone will return an error which includes the text `Invalid
+refresh token`.
+
+To fix this you will need to use oauth2 again to update the refresh
+token.  You can use the methods in [the remote setup
+docs](https://rclone.org/remote_setup/), 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.
+
+Here is how to do it.
+</code></pre>
+<p>$ rclone config Current remotes:</p>
+<p>Name Type ==== ==== remote box</p>
+<ol start="5" type="a">
+<li>Edit existing remote</li>
+<li>New remote</li>
+<li>Delete remote</li>
+<li>Rename remote</li>
+<li>Copy remote</li>
+<li>Set configuration password</li>
+<li>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 -------------------- [remote] type = box token = {"access_token":"XXX","token_type":"bearer","refresh_token":"XXX","expiry":"2017-07-08T23:40:08.059167677+01:00"} -------------------- Edit remote Value "client_id" = "" Edit? (y/n)&gt;</li>
+<li>Yes</li>
+<li>No y/n&gt; n Value "client_secret" = "" Edit? (y/n)&gt;</li>
+<li>Yes</li>
+<li>No y/n&gt; n Remote config Already have a token - refresh?</li>
+<li>Yes</li>
+<li>No y/n&gt; y Use auto config?</li>
+</ol>
+<ul>
+<li>Say Y if not sure</li>
+<li>Say N if you are working on a remote or headless machine</li>
+</ul>
+<ol start="25" type="a">
+<li>Yes</li>
+<li>No y/n&gt; y If your browser doesn'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 -------------------- [remote] type = box token = {"access_token":"YYY","token_type":"bearer","refresh_token":"YYY","expiry":"2017-07-23T12:22:29.259137901+01:00"} --------------------</li>
+<li>Yes this is OK</li>
+<li>Edit this remote</li>
+<li>Delete this remote y/e/d&gt; y</li>
+</ol>
+<pre><code>
+### Modified time and hashes ###
+
+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.
+
+Box supports SHA1 type hashes, so you can use the `--checksum`
+flag.
+
+#### Restricted filename characters
+
+In addition to the [default restricted characters set](https://rclone.org/overview/#restricted-characters)
+the following characters are also replaced:
+
+| Character | Value | Replacement |
+| --------- |:-----:|:-----------:|
+| \         | 0x5C  | ＼           |
+
+File names can also not end with the following characters.
+These only get replaced if they are the last character in the name:
+
+| Character | Value | Replacement |
+| --------- |:-----:|:-----------:|
+| SP        | 0x20  | ␠           |
+
+Invalid UTF-8 bytes will also be [replaced](https://rclone.org/overview/#invalid-utf8),
+as they can&#39;t be used in JSON strings.
+
+### Transfers ###
+
+For files above 50MB rclone will use a chunked transfer.  Rclone will
+upload up to `--transfers` chunks at the same time (shared among all
+the multipart uploads).  Chunks are buffered in memory and are
+normally 8MB so increasing `--transfers` will increase memory use.
+
+### Deleting files ###
+
+Depending on the enterprise settings for your user, the item will
+either be actually deleted from Box or moved to the trash.
+
+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.
+
+### Root folder ID ###
+
+You can set the `root_folder_id` for rclone.  This is the directory
+(identified by its `Folder ID`) that rclone considers to be the root
+of your Box drive.
+
+Normally you will leave this blank and rclone will determine the
+correct root to use itself.
+
+However you can set this to restrict rclone to a specific folder
+hierarchy.
+
+In order to do this you will have to find the `Folder ID` 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.
+
+So if the folder you want rclone to use has a URL which looks like
+`https://app.box.com/folder/11xxxxxxxxx8`
+in the browser, then you use `11xxxxxxxxx8` as
+the `root_folder_id` in the config.
+
+
+### Standard Options
+
+Here are the standard options specific to box (Box).
+
+#### --box-client-id
+
+OAuth Client Id
+Leave blank normally.
+
+- Config:      client_id
+- Env Var:     RCLONE_BOX_CLIENT_ID
+- Type:        string
+- Default:     &quot;&quot;
+
+#### --box-client-secret
+
+OAuth Client Secret
+Leave blank normally.
+
+- Config:      client_secret
+- Env Var:     RCLONE_BOX_CLIENT_SECRET
+- Type:        string
+- Default:     &quot;&quot;
+
+#### --box-box-config-file
+
 Box App config.json location
 Leave blank normally.
-Enter a string value. Press Enter for the default (&quot;&quot;).
-config_json&gt;
-&#39;enterprise&#39; or &#39;user&#39; depending on the type of token being requested.
-Enter a string value. Press Enter for the default (&quot;user&quot;).
-box_sub_type&gt;
-Remote config
-Use auto config?
- * Say Y if not sure
- * Say N if you are working on a remote or headless machine
-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
---------------------
-[remote]
-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;}
---------------------
-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
+Leading `~` will be expanded in the file name as will environment variables such as `${RCLONE_CONFIG_DIR}`.
+
+
+- Config:      box_config_file
+- Env Var:     RCLONE_BOX_BOX_CONFIG_FILE
+- Type:        string
+- Default:     &quot;&quot;
+
+#### --box-access-token
+
+Box App Primary Access Token
+Leave blank normally.
+
+- Config:      access_token
+- Env Var:     RCLONE_BOX_ACCESS_TOKEN
+- Type:        string
+- Default:     &quot;&quot;
+
+#### --box-box-sub-type
+
+
+
+- Config:      box_sub_type
+- Env Var:     RCLONE_BOX_BOX_SUB_TYPE
+- Type:        string
+- Default:     &quot;user&quot;
+- Examples:
+    - &quot;user&quot;
+        - Rclone should act on behalf of a user
+    - &quot;enterprise&quot;
+        - Rclone should act on behalf of a service account
+
+### Advanced Options
+
+Here are the advanced options specific to box (Box).
+
+#### --box-token
+
+OAuth Access Token as a JSON blob.
+
+- Config:      token
+- Env Var:     RCLONE_BOX_TOKEN
+- Type:        string
+- Default:     &quot;&quot;
+
+#### --box-auth-url
+
+Auth server URL.
+Leave blank to use the provider defaults.
+
+- Config:      auth_url
+- Env Var:     RCLONE_BOX_AUTH_URL
+- Type:        string
+- Default:     &quot;&quot;
+
+#### --box-token-url
+
+Token server url.
+Leave blank to use the provider defaults.
+
+- Config:      token_url
+- Env Var:     RCLONE_BOX_TOKEN_URL
+- Type:        string
+- Default:     &quot;&quot;
+
+#### --box-root-folder-id
+
+Fill in for rclone to use a non root folder as its starting point.
+
+- Config:      root_folder_id
+- Env Var:     RCLONE_BOX_ROOT_FOLDER_ID
+- Type:        string
+- Default:     &quot;0&quot;
+
+#### --box-upload-cutoff
+
+Cutoff for switching to multipart upload (&gt;= 50MB).
+
+- Config:      upload_cutoff
+- Env Var:     RCLONE_BOX_UPLOAD_CUTOFF
+- Type:        SizeSuffix
+- Default:     50M
+
+#### --box-commit-retries
+
+Max number of times to try committing a multipart file.
+
+- Config:      commit_retries
+- Env Var:     RCLONE_BOX_COMMIT_RETRIES
+- Type:        int
+- Default:     100
+
+#### --box-encoding
+
+This sets the encoding for the backend.
+
+See: the [encoding section in the overview](https://rclone.org/overview/#encoding) for more info.
+
+- Config:      encoding
+- Env Var:     RCLONE_BOX_ENCODING
+- Type:        MultiEncoder
+- Default:     Slash,BackSlash,Del,Ctl,RightSpace,InvalidUtf8,Dot
+
+
+
+### Limitations ###
+
+Note that Box is case insensitive so you can&#39;t have a file called
+&quot;Hello.doc&quot; and one called &quot;hello.doc&quot;.
+
+Box file names can&#39;t have the `\` character in.  rclone maps this to
+and from an identical looking unicode equivalent `＼`.
+
+Box only supports filenames up to 255 characters in length.
+
+ Cache (BETA)
+-----------------------------------------
+
+The `cache` remote wraps another existing remote and stores file structure
+and its data for long running tasks like `rclone mount`.
+
+## Status
+
+The cache backend code is working but it currently doesn&#39;t
+have a maintainer so there are [outstanding bugs](https://github.com/rclone/rclone/issues?q=is%3Aopen+is%3Aissue+label%3Abug+label%3A%22Remote%3A+Cache%22) which aren&#39;t getting fixed.
+
+The cache backend is due to be phased out in favour of the VFS caching
+layer eventually which is more tightly integrated into rclone.
+
+Until this happens we recommend only using the cache backend if you
+find you can&#39;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&#39;t needed in those
+scenarios any more.
+
+## Setup
+
+To get started you just need to have an existing remote which can be configured
+with `cache`.
+
+Here is an example of how to make a remote called `test-cache`.  First run:
+
+     rclone config
+
+This will guide you through an interactive setup process:
+</code></pre>
+<p>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  "cache" [snip] Storage&gt; cache Remote to cache. Normally should contain a ':' and a path, eg "myremote:path/to/dir", "myremote:bucket" or maybe "myremote:" (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 / 1MB  "1m" 2 / 5 MB  "5M" 3 / 10 MB  "10M" 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't plan on changing the source FS from outside the cache. Accepted units are: "s", "m", "h". Default: 5m Choose a number from below, or type in your own value 1 / 1 hour  "1h" 2 / 24 hours  "24h" 3 / 24 hours  "48h" 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 MB  "500M" 2 / 1 GB  "1G" 3 / 10 GB  "10G" 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</p>
+<pre><code>
+You can then use it like this,
+
+List directories in top level of your drive
+
+    rclone lsd test-cache:
+
+List all the files in your drive
+
+    rclone ls test-cache:
+
+To start a cached mount
+
+    rclone mount --allow-other test-cache: /var/tmp/test-cache
+
+### Write Features ###
+
+### Offline uploading ###
+
+In an effort to make writing through cache more reliable, the backend 
+now supports this feature which can be activated by specifying a
+`cache-tmp-upload-path`.
+
+A files goes through these states when using this feature:
+
+1. An upload is started (usually by copying a file on the cache remote)
+2. 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)
+3. After `cache-tmp-wait-time` passes and the file is next in line, `rclone move` 
+is used to move the file to the cloud provider
+4. Reading the file still works during the upload but most modifications on it will be prohibited
+5. Once the move is complete the file is unlocked for modifications as it
+becomes as any other regular file
+6. If the file is being read through `cache` when it&#39;s actually
+deleted from the temporary path then `cache` will simply swap the source
+to the cloud provider without interrupting the reading (small blip can happen though)
+
+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 `--cache-db-purge` flag.
+
+### Write Support ###
+
+Writes are supported through `cache`.
+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 `Offline uploading` for reliable writes.
+
+One special case is covered with `cache-writes` 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.
+
+### Read Features ###
+
+#### Multiple connections ####
+
+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.
+
+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.
+
+#### Plex Integration ####
+
+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.
+
+Scans will have a minimum amount of workers (1) while in a confirmed playback cache
+will deploy the configured number of workers.
+
+This integration opens the doorway to additional performance improvements
+which will be explored in the near future.
+
+**Note:** If Plex options are not configured, `cache` will function with its
+configured options without adapting any of its settings.
+
+How to enable? Run `rclone config` and add all the Plex options (endpoint, username
+and password) in your remote and it will be automatically enabled.
+
+Affected settings:
+- `cache-workers`: _Configured value_ during confirmed playback or _1_ all the other times
+
+##### Certificate Validation #####
+
+When the Plex server is configured to only accept secure connections, it is
+possible to use `.plex.direct` URLs to ensure certificate validation succeeds.
+These URLs are used by Plex internally to connect to the Plex server securely.
+
+The format for these URLs is the following:
+
+https://ip-with-dots-replaced.server-hash.plex.direct:32400/
+
+The `ip-with-dots-replaced` part can be any IPv4 address, where the dots
+have been replaced with dashes, e.g. `127.0.0.1` becomes `127-0-0-1`.
+
+To get the `server-hash` part, the easiest way is to visit
+
+https://plex.tv/api/resources?includeHttps=1&amp;X-Plex-Token=your-plex-token
+
+This page will list all the available Plex servers for your account
+with at least one `.plex.direct` link for each. Copy one URL and replace
+the IP address with the desired address. This can be used as the
+`plex_url` value.
+
+### Known issues ###
+
+#### Mount and --dir-cache-time ####
+
+--dir-cache-time controls the first layer of directory caching which works at the mount layer.
+Being an independent caching mechanism from the `cache` backend, it will manage its own entries
+based on the configured time.
+
+To avoid getting in a scenario where dir cache has obsolete data and cache would have the correct
+one, try to set `--dir-cache-time` to a lower time than `--cache-info-age`. Default values are
+already configured in this way. 
+
+#### Windows support - Experimental ####
+
+There are a couple of issues with Windows `mount` functionality that still require some investigations.
+It should be considered as experimental thus far as fixes come in for this OS.
+
+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.
+
+Any reports or feedback on how cache behaves on this OS is greatly appreciated.
+ 
+- https://github.com/rclone/rclone/issues/1935
+- https://github.com/rclone/rclone/issues/1907
+- https://github.com/rclone/rclone/issues/1834 
+
+#### Risk of throttling ####
+
+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. 
+
+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.
+
+Some recommendations:
+- don&#39;t use a very small interval for entry information (`--cache-info-age`)
+- while writes aren&#39;t yet optimised, you can still write through `cache` which gives you the advantage
+of adding the file in the cache at the same time if configured to do so.
+
+Future enhancements:
+
+- https://github.com/rclone/rclone/issues/1937
+- https://github.com/rclone/rclone/issues/1936 
+
+#### cache and crypt ####
+
+One common scenario is to keep your data encrypted in the cloud provider
+using the `crypt` remote. `crypt` uses a similar technique to wrap around
+an existing remote and handles this translation in a seamless way.
+
+There is an issue with wrapping the remotes in this order:
+**cloud remote** -&gt; **crypt** -&gt; **cache**
+
+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&#39;re downloading the full file instead of small chunks.
+Organizing the remotes in this order yields better results:
+**cloud remote** -&gt; **cache** -&gt; **crypt**
+
+#### absolute remote paths ####
+
+`cache` can not differentiate between relative and absolute paths for the wrapped remote.
+Any path given in the `remote` 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 `/` character.
+
+This behavior is irrelevant for most backend types, but there are backends where a leading `/`
+changes the effective directory, e.g. in the `sftp` backend paths starting with a `/` are
+relative to the root of the SSH server and paths without are relative to the user home directory.
+As a result `sftp:bin` and `sftp:/bin` will share the same cache folder, even if they represent
+a different directory on the SSH server.
+
+### Cache and Remote Control (--rc) ###
+Cache supports the new `--rc` 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.
+
+### rc cache/expire
+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.
+
+Params:
+  - **remote** = path to remote **(required)**
+  - **withData** = true/false to delete cached data (chunks) as well _(optional, false by default)_
+
+
+### Standard Options
+
+Here are the standard options specific to cache (Cache a remote).
+
+#### --cache-remote
 
-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
---------------------
-[remote]
-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;}
---------------------
-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 auto config?
- * Say Y if not sure
- * Say N if you are working on a remote or headless machine
-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
---------------------
-[remote]
-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;}
---------------------
-y) Yes this is OK
-e) Edit this remote
-d) Delete this remote
-y/e/d&gt; y</code></pre>
-<h3 id="modified-time-and-hashes-1">Modified time 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>
-<h4 id="restricted-filename-characters-4">Restricted filename characters</h4>
-<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 50MB 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 8MB so increasing <code>--transfers</code> will increase memory use.</p>
-<h3 id="deleting-files-1">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>
-<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-5">Standard Options</h3>
-<p>Here are the standard options specific to box (Box).</p>
-<h4 id="box-client-id">–box-client-id</h4>
-<p>Box App Client Id. Leave blank normally.</p>
-<ul>
-<li>Config: client_id</li>
-<li>Env Var: RCLONE_BOX_CLIENT_ID</li>
-<li>Type: string</li>
-<li>Default: ""</li>
-</ul>
-<h4 id="box-client-secret">–box-client-secret</h4>
-<p>Box App Client Secret Leave blank normally.</p>
-<ul>
-<li>Config: client_secret</li>
-<li>Env Var: RCLONE_BOX_CLIENT_SECRET</li>
-<li>Type: string</li>
-<li>Default: ""</li>
-</ul>
-<h4 id="box-box-config-file">–box-box-config-file</h4>
-<p>Box App config.json location Leave blank normally.</p>
-<ul>
-<li>Config: box_config_file</li>
-<li>Env Var: RCLONE_BOX_BOX_CONFIG_FILE</li>
-<li>Type: string</li>
-<li>Default: ""</li>
-</ul>
-<h4 id="box-box-sub-type">–box-box-sub-type</h4>
-<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-root-folder-id">–box-root-folder-id</h4>
-<p>Fill in for rclone to use a non root folder as its starting point.</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;= 50MB).</p>
-<ul>
-<li>Config: upload_cutoff</li>
-<li>Env Var: RCLONE_BOX_UPLOAD_CUTOFF</li>
-<li>Type: SizeSuffix</li>
-<li>Default: 50M</li>
-</ul>
-<h4 id="box-commit-retries">–box-commit-retries</h4>
-<p>Max number of times to try committing a multipart file.</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-encoding">–box-encoding</h4>
-<p>This sets 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>
-<ul>
-<li>Config: encoding</li>
-<li>Env Var: RCLONE_BOX_ENCODING</li>
-<li>Type: MultiEncoder</li>
-<li>Default: Slash,BackSlash,Del,Ctl,RightSpace,InvalidUtf8,Dot</li>
-</ul>
-<h3 id="limitations-3">Limitations</h3>
-<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>.</p>
-<p>Box only supports filenames up to 255 characters in length.</p>
-<h2 id="cache-beta">Cache (BETA)</h2>
-<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-1">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="setup-1">Setup</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, eg &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 / 1MB
-   \ &quot;1m&quot;
- 2 / 5 MB
-   \ &quot;5M&quot;
- 3 / 10 MB
-   \ &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 MB
-   \ &quot;500M&quot;
- 2 / 1 GB
-   \ &quot;1G&quot;
- 3 / 10 GB
-   \ &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>https://ip-with-dots-replaced.server-hash.plex.direct:32400/</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-6">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. Normally should contain a ‘:’ and a path, eg “myremote:path/to/dir”, “myremote:bucket” or maybe “myremote:” (not recommended).</p>
-<ul>
-<li>Config: remote</li>
-<li>Env Var: RCLONE_CACHE_REMOTE</li>
-<li>Type: string</li>
-<li>Default: ""</li>
-</ul>
-<h4 id="cache-plex-url">–cache-plex-url</h4>
-<p>The URL of the Plex server</p>
-<ul>
-<li>Config: plex_url</li>
-<li>Env Var: RCLONE_CACHE_PLEX_URL</li>
-<li>Type: string</li>
-<li>Default: ""</li>
-</ul>
-<h4 id="cache-plex-username">–cache-plex-username</h4>
-<p>The username of the Plex user</p>
-<ul>
-<li>Config: plex_username</li>
-<li>Env Var: RCLONE_CACHE_PLEX_USERNAME</li>
-<li>Type: string</li>
-<li>Default: ""</li>
-</ul>
-<h4 id="cache-plex-password">–cache-plex-password</h4>
-<p>The password of the Plex user</p>
-<ul>
-<li>Config: plex_password</li>
-<li>Env Var: RCLONE_CACHE_PLEX_PASSWORD</li>
-<li>Type: string</li>
-<li>Default: ""</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>
-<ul>
-<li>Config: chunk_size</li>
-<li>Env Var: RCLONE_CACHE_CHUNK_SIZE</li>
-<li>Type: SizeSuffix</li>
-<li>Default: 5M</li>
-<li>Examples:
-<ul>
-<li>“1m”
-<ul>
-<li>1MB</li>
-</ul></li>
-<li>“5M”
-<ul>
-<li>5 MB</li>
-</ul></li>
-<li>“10M”
-<ul>
-<li>10 MB</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>
-<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>
-<ul>
-<li>Config: chunk_total_size</li>
-<li>Env Var: RCLONE_CACHE_CHUNK_TOTAL_SIZE</li>
-<li>Type: SizeSuffix</li>
-<li>Default: 10G</li>
-<li>Examples:
-<ul>
-<li>“500M”
-<ul>
-<li>500 MB</li>
-</ul></li>
-<li>“1G”
-<ul>
-<li>1 GB</li>
-</ul></li>
-<li>“10G”
-<ul>
-<li>10 GB</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>
-<ul>
-<li>Config: plex_token</li>
-<li>Env Var: RCLONE_CACHE_PLEX_TOKEN</li>
-<li>Type: string</li>
-<li>Default: ""</li>
-</ul>
-<h4 id="cache-plex-insecure">–cache-plex-insecure</h4>
-<p>Skip all certificate verification when connecting to the Plex server</p>
-<ul>
-<li>Config: plex_insecure</li>
-<li>Env Var: RCLONE_CACHE_PLEX_INSECURE</li>
-<li>Type: string</li>
-<li>Default: ""</li>
-</ul>
-<h4 id="cache-db-path">–cache-db-path</h4>
-<p>Directory to store file structure metadata DB. The remote name is used as the DB file name.</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>
-<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>
-<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. 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>
-<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>
-<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>
-<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>
-<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>
-<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>
-<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>
-<ul>
-<li>Config: tmp_upload_path</li>
-<li>Env Var: RCLONE_CACHE_TMP_UPLOAD_PATH</li>
-<li>Type: string</li>
-<li>Default: ""</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>
-<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>
-<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>
-<h3 id="backend-commands">Backend commands</h3>
-<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 <a href="https://rclone.org/commands/rclone_backend/">the “rclone backend” command</a> 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>
-<h4 id="stats">stats</h4>
-<p>Print stats on the cache backend in JSON format.</p>
-<pre><code>rclone backend stats remote: [options] [&lt;arguments&gt;+]</code></pre>
-<h2 id="chunker-beta">Chunker (BETA)</h2>
-<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>
-<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 (eg 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
+
+- Config:      remote
+- Env Var:     RCLONE_CACHE_REMOTE
+- Type:        string
+- Default:     &quot;&quot;
+
+#### --cache-plex-url
+
+The URL of the Plex server
+
+- Config:      plex_url
+- Env Var:     RCLONE_CACHE_PLEX_URL
+- Type:        string
+- Default:     &quot;&quot;
+
+#### --cache-plex-username
+
+The username of the Plex user
+
+- Config:      plex_username
+- Env Var:     RCLONE_CACHE_PLEX_USERNAME
+- Type:        string
+- Default:     &quot;&quot;
+
+#### --cache-plex-password
+
+The password of the Plex user
+
+**NB** Input to this must be obscured - see [rclone obscure](https://rclone.org/commands/rclone_obscure/).
+
+- Config:      plex_password
+- Env Var:     RCLONE_CACHE_PLEX_PASSWORD
+- Type:        string
+- Default:     &quot;&quot;
+
+#### --cache-chunk-size
+
+The size of a chunk (partial file data).
+
+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.
+
+- Config:      chunk_size
+- Env Var:     RCLONE_CACHE_CHUNK_SIZE
+- Type:        SizeSuffix
+- Default:     5M
+- Examples:
+    - &quot;1m&quot;
+        - 1MB
+    - &quot;5M&quot;
+        - 5 MB
+    - &quot;10M&quot;
+        - 10 MB
+
+#### --cache-info-age
+
+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.
+
+- Config:      info_age
+- Env Var:     RCLONE_CACHE_INFO_AGE
+- Type:        Duration
+- Default:     6h0m0s
+- Examples:
+    - &quot;1h&quot;
+        - 1 hour
+    - &quot;24h&quot;
+        - 24 hours
+    - &quot;48h&quot;
+        - 48 hours
+
+#### --cache-chunk-total-size
+
+The total size that the chunks can take up on the local disk.
+
+If the cache exceeds this value then it will start to delete the
+oldest chunks until it goes under this value.
+
+- Config:      chunk_total_size
+- Env Var:     RCLONE_CACHE_CHUNK_TOTAL_SIZE
+- Type:        SizeSuffix
+- Default:     10G
+- Examples:
+    - &quot;500M&quot;
+        - 500 MB
+    - &quot;1G&quot;
+        - 1 GB
+    - &quot;10G&quot;
+        - 10 GB
+
+### Advanced Options
+
+Here are the advanced options specific to cache (Cache a remote).
+
+#### --cache-plex-token
+
+The plex token for authentication - auto set normally
+
+- Config:      plex_token
+- Env Var:     RCLONE_CACHE_PLEX_TOKEN
+- Type:        string
+- Default:     &quot;&quot;
+
+#### --cache-plex-insecure
+
+Skip all certificate verification when connecting to the Plex server
+
+- Config:      plex_insecure
+- Env Var:     RCLONE_CACHE_PLEX_INSECURE
+- Type:        string
+- Default:     &quot;&quot;
+
+#### --cache-db-path
+
+Directory to store file structure metadata DB.
+The remote name is used as the DB file name.
+
+- Config:      db_path
+- Env Var:     RCLONE_CACHE_DB_PATH
+- Type:        string
+- Default:     &quot;$HOME/.cache/rclone/cache-backend&quot;
+
+#### --cache-chunk-path
+
+Directory to cache chunk files.
+
+Path to where partial file data (chunks) are stored locally. The remote
+name is appended to the final path.
+
+This config follows the &quot;--cache-db-path&quot;. If you specify a custom
+location for &quot;--cache-db-path&quot; and don&#39;t specify one for &quot;--cache-chunk-path&quot;
+then &quot;--cache-chunk-path&quot; will use the same path as &quot;--cache-db-path&quot;.
+
+- Config:      chunk_path
+- Env Var:     RCLONE_CACHE_CHUNK_PATH
+- Type:        string
+- Default:     &quot;$HOME/.cache/rclone/cache-backend&quot;
+
+#### --cache-db-purge
+
+Clear all the cached data for this remote on start.
+
+- Config:      db_purge
+- Env Var:     RCLONE_CACHE_DB_PURGE
+- Type:        bool
+- Default:     false
+
+#### --cache-chunk-clean-interval
+
+How often should the cache perform cleanups of the chunk storage.
+The default value should be ok for most people. If you find that the
+cache goes over &quot;cache-chunk-total-size&quot; too often then try to lower
+this value to force it to perform cleanups more often.
+
+- Config:      chunk_clean_interval
+- Env Var:     RCLONE_CACHE_CHUNK_CLEAN_INTERVAL
+- Type:        Duration
+- Default:     1m0s
+
+#### --cache-read-retries
+
+How many times to retry a read from a cache storage.
+
+Since reading from a cache stream is independent from downloading file
+data, readers can get to a point where there&#39;s no more data in the
+cache.  Most of the times this can indicate a connectivity issue if
+cache isn&#39;t able to provide file data anymore.
+
+For really slow connections, increase this to a point where the stream is
+able to provide data but your experience will be very stuttering.
+
+- Config:      read_retries
+- Env Var:     RCLONE_CACHE_READ_RETRIES
+- Type:        int
+- Default:     10
+
+#### --cache-workers
+
+How many workers should run in parallel to download chunks.
+
+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.
+
+**Note**: 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.
+
+- Config:      workers
+- Env Var:     RCLONE_CACHE_WORKERS
+- Type:        int
+- Default:     4
+
+#### --cache-chunk-no-memory
+
+Disable the in-memory cache for storing chunks during streaming.
+
+By default, cache will keep file data during streaming in RAM as well
+to provide it to readers as fast as possible.
+
+This transient data is evicted as soon as it is read and the number of
+chunks stored doesn&#39;t exceed the number of workers. However, depending
+on other settings like &quot;cache-chunk-size&quot; and &quot;cache-workers&quot; this footprint
+can increase if there are parallel streams too (multiple files being read
+at the same time).
+
+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.
+
+- Config:      chunk_no_memory
+- Env Var:     RCLONE_CACHE_CHUNK_NO_MEMORY
+- Type:        bool
+- Default:     false
+
+#### --cache-rps
+
+Limits the number of requests per second to the source FS (-1 to disable)
+
+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.
+
+If you find that you&#39;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.
+
+A good balance of all the other settings should make this setting
+useless but it is available to set for more special cases.
+
+**NOTE**: This will limit the number of requests during streams but
+other API calls to the cloud provider like directory listings will
+still pass.
+
+- Config:      rps
+- Env Var:     RCLONE_CACHE_RPS
+- Type:        int
+- Default:     -1
+
+#### --cache-writes
+
+Cache file data on writes through the FS
+
+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.
+
+- Config:      writes
+- Env Var:     RCLONE_CACHE_WRITES
+- Type:        bool
+- Default:     false
+
+#### --cache-tmp-upload-path
+
+Directory to keep temporary files until they are uploaded.
+
+This is the path where cache will use as a temporary storage for new
+files that need to be uploaded to the cloud provider.
+
+Specifying a value will enable this feature. Without it, it is
+completely disabled and files will be uploaded directly to the cloud
+provider
+
+- Config:      tmp_upload_path
+- Env Var:     RCLONE_CACHE_TMP_UPLOAD_PATH
+- Type:        string
+- Default:     &quot;&quot;
+
+#### --cache-tmp-wait-time
+
+How long should files be stored in local cache before being uploaded
+
+This is the duration that a file must wait in the temporary location
+_cache-tmp-upload-path_ before it is selected for upload.
+
+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.
+
+- Config:      tmp_wait_time
+- Env Var:     RCLONE_CACHE_TMP_WAIT_TIME
+- Type:        Duration
+- Default:     15s
+
+#### --cache-db-wait-time
+
+How long to wait for the DB to be available - 0 is unlimited
+
+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.
+
+If you set it to 0 then it will wait forever.
+
+- Config:      db_wait_time
+- Env Var:     RCLONE_CACHE_DB_WAIT_TIME
+- Type:        Duration
+- Default:     1s
+
+### Backend commands
+
+Here are the commands specific to the cache backend.
+
+Run them with
+
+    rclone backend COMMAND remote:
+
+The help below will explain what arguments each command takes.
+
+See [the &quot;rclone backend&quot; command](https://rclone.org/commands/rclone_backend/) for more
+info on how to pass options and arguments.
+
+These can be run on a running backend using the rc command
+[backend/command](https://rclone.org/rc/#backend/command).
+
+#### stats
+
+Print stats on the cache backend in JSON format.
+
+    rclone backend stats remote: [options] [&lt;arguments&gt;+]
+
+
+
+Chunker (BETA)
+----------------------------------------
+
+The `chunker` 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.
+
+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.
+
+First check your chosen remote is working - we&#39;ll call it `remote:path` here.
+Note that anything inside `remote:path` will be chunked and anything outside
+won&#39;t. This means that if you are using a bucket based remote (eg S3, B2, swift)
+then you should probably put the bucket in the remote `s3:bucket`.
+
+Now configure `chunker` using `rclone config`. We will call this one `overlay`
+to separate it from the `remote` itself.
+</code></pre>
+<p>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  "chunker" [snip] Storage&gt; chunker Remote to chunk/unchunk. Normally should contain a ':' and a path, eg "myremote:path/to/dir", "myremote:bucket" or maybe "myremote:" (not recommended). Enter a string value. Press Enter for the default (""). 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 ("2G"). chunk_size&gt; 100M Choose how chunker handles hash sums. All modes but "none" require metadata. Enter a string value. Press Enter for the default ("md5"). 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  "none" 2 / MD5 for composite files  "md5" 3 / SHA1 for composite files  "sha1" 4 / MD5 for all files  "md5all" 5 / SHA1 for all files  "sha1all" 6 / Copying a file to chunker will request MD5 from the source falling back to SHA1 if unsupported  "md5quick" 7 / Similar to "md5quick" but prefers SHA1 over MD5  "sha1quick" 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</p>
+<pre><code>
+### Specifying the remote
+
+In normal use, make sure the remote has a `:` in. If you specify the remote
+without a `:` then rclone will use a local directory of that name.
+So if you use a remote of `/path/to/secret/files` then rclone will
+chunk stuff in that directory. If you use a remote of `name` then rclone
+will put files in a directory called `name` in the current directory.
+
+
+### Chunking
+
+When rclone starts a file upload, chunker checks the file size. If it
+doesn&#39;t exceed the configured chunk size, chunker will just pass the file
+to the wrapped remote. 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.
+
+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.
+
+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.
+
+When the `list` 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.
+
+List and other commands can sometimes come across composite files with
+missing or invalid chunks, eg. 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 `--chunker-fail-hard` flag to have commands abort with
+error message in such cases.
+
+
+#### Chunk names
+
+The default chunk name format is `*.rclone_chunk.###`, hence by default
+chunk names are `BIG_FILE_NAME.rclone_chunk.001`,
+`BIG_FILE_NAME.rclone_chunk.002` etc. You can configure another name format
+using the `name_format` configuration file option. The format uses asterisk
+`*` as a placeholder for the base file name and one or more consecutive
+hash characters `#` 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, eg. for compatibility with legacy software.
+
+For example, if name format is `big_*-##.part` and original file name is
+`data.txt` and numbering starts from 0, then the first chunk will be named
+`big_data.txt-00.part`, the 99th chunk will be `big_data.txt-98.part`
+and the 302nd chunk will become `big_data.txt-301.part`.
+
+Note that `list` assembles composite directory entries only when chunk names
+match the configured format and treats non-conforming file names as normal
+non-chunked files.
+
+
+### Metadata
+
+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 `none` format).
+Note that metadata is normally not created for files smaller than the
+configured chunk size. This may change in future rclone releases.
+
+#### Simple JSON metadata format
+
+This is the default format. It supports hash sums and chunk validation
+for composite files. Meta objects carry the following fields:
+
+- `ver`     - version of format, currently `1`
+- `size`    - total size of composite file
+- `nchunks` - number of data chunks in file
+- `md5`     - MD5 hashsum of composite file (if present)
+- `sha1`    - SHA1 hashsum (if present)
+
+There is no field for composite file name as it&#39;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.
+
+#### No metadata
+
+You can disable meta objects by setting the meta format option to `none`.
+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.
+
+
+### Hashsums
+
+Chunker supports hashsums only when a compatible metadata is present.
+Hence, if you choose metadata format of `none`, chunker will report hashsum
+as `UNSUPPORTED`.
+
+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&#39;t support it.
+
+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.
+
+If your storage backend does not support MD5 or SHA1 but you need consistent
+file hashing, configure chunker with `md5all` or `sha1all`. These two modes
+guarantee given hash for all files. If wrapped remote doesn&#39;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 eg. `chunk_type=sha1all`
+to force hashsums and `chunk_size=1P` to effectively disable chunking.
+
+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: `sha1quick` and `md5quick`. 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 `sync` command will
+revert (sometimes silently) to time/size comparison if compatible hashsums
+between source and target are not found.
+
+
+### Modified time
+
+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 `none` then chunker will
+use modification time of the first data chunk.
+
+
+### Migrations
+
+The idiomatic way to migrate to a different chunk size, hash type or
+chunk naming scheme is to:
+
+- Collect all your chunked files under a directory and have your
+  chunker remote point to it.
+- Create another directory (most probably on the same cloud storage)
+  and configure a new remote with desired metadata format,
+  hash type, chunk naming etc.
+- Now run `rclone sync -i oldchunks: newchunks:` and all your data
+  will be transparently converted in transfer.
+  This may take some time, yet chunker will try server-side
+  copy if possible.
+- After checking data integrity you may remove configuration section
+  of the old remote.
+
+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 `list` command but will eat up your account quota.
+Please note that the `deletefile` 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 `copy` command will copy only active chunks while the `purge` will
+remove everything including garbage.
+
+
+### Caveats and Limitations
+
+Chunker requires wrapped remote to support server side `move` (or `copy` +
+`delete`) 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.
+
+Chunker encodes chunk number in file name, so with default `name_format`
+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&#39;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
+eg. `*.rcc##` and save 10 characters (provided at most 99 chunks per file).
+
+Note that a move implemented using the copy-and-delete method may incur
+double charging with some cloud storage providers.
+
+Chunker will not automatically rename existing chunks when you run
+`rclone config` 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.
+
+If wrapped remote is case insensitive, the chunker overlay will inherit
+that property (so you can&#39;t have a file called &quot;Hello.doc&quot; and &quot;hello.doc&quot;
+in the same directory).
+
+
+
+### Standard Options
+
+Here are the standard options specific to chunker (Transparently chunk/split large files).
+
+#### --chunker-remote
+
 Remote to chunk/unchunk.
 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
+
+- Config:      remote
+- Env Var:     RCLONE_CHUNKER_REMOTE
+- Type:        string
+- Default:     &quot;&quot;
+
+#### --chunker-chunk-size
+
 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
+
+- Config:      chunk_size
+- Env Var:     RCLONE_CHUNKER_CHUNK_SIZE
+- Type:        SizeSuffix
+- Default:     2G
+
+#### --chunker-hash-type
+
 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. 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, eg. 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>
-<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, eg. 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>
-<h3 id="metadata">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>
-</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 eg. <code>chunk_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="modified-time-2">Modified time</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 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 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 eg. <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>
-<h3 id="standard-options-7">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. Normally should contain a ‘:’ and a path, eg “myremote:path/to/dir”, “myremote:bucket” or maybe “myremote:” (not recommended).</p>
-<ul>
-<li>Config: remote</li>
-<li>Env Var: RCLONE_CHUNKER_REMOTE</li>
-<li>Type: string</li>
-<li>Default: ""</li>
-</ul>
-<h4 id="chunker-chunk-size">–chunker-chunk-size</h4>
-<p>Files larger than chunk size will be split in chunks.</p>
-<ul>
-<li>Config: chunk_size</li>
-<li>Env Var: RCLONE_CHUNKER_CHUNK_SIZE</li>
-<li>Type: SizeSuffix</li>
-<li>Default: 2G</li>
-</ul>
-<h4 id="chunker-hash-type">–chunker-hash-type</h4>
-<p>Choose how chunker handles hash sums. All modes but “none” require metadata.</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, 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 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. 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>
-<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. By default chunk numbers start from 1.</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”. By default “simplejson”. Metadata is a small JSON file named after the composite file.</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. Requires hash type “none”.</li>
-</ul></li>
-<li>“simplejson”
-<ul>
-<li>Simple JSON supports hash sums and chunk validation.</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>
-<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>
-<h2 id="citrix-sharefile">Citrix ShareFile</h2>
-<p><a href="https://sharefile.com">Citrix ShareFile</a> is a secure file sharing and transfer service aimed as business.</p>
-<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/ **
+
+- Config:      hash_type
+- Env Var:     RCLONE_CHUNKER_HASH_TYPE
+- Type:        string
+- Default:     &quot;md5&quot;
+- Examples:
+    - &quot;none&quot;
+        - Pass any hash supported by wrapped remote for non-chunked files, return nothing otherwise
+    - &quot;md5&quot;
+        - MD5 for composite files
+    - &quot;sha1&quot;
+        - SHA1 for composite files
+    - &quot;md5all&quot;
+        - MD5 for all files
+    - &quot;sha1all&quot;
+        - SHA1 for all files
+    - &quot;md5quick&quot;
+        - Copying a file to chunker will request MD5 from the source falling back to SHA1 if unsupported
+    - &quot;sha1quick&quot;
+        - Similar to &quot;md5quick&quot; but prefers SHA1 over MD5
+
+### Advanced Options
+
+Here are the advanced options specific to chunker (Transparently chunk/split large files).
+
+#### --chunker-name-format
+
+String format of chunk file names.
+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.
+
+- Config:      name_format
+- Env Var:     RCLONE_CHUNKER_NAME_FORMAT
+- Type:        string
+- Default:     &quot;*.rclone_chunk.###&quot;
+
+#### --chunker-start-from
+
+Minimum valid chunk number. Usually 0 or 1.
+By default chunk numbers start from 1.
+
+- Config:      start_from
+- Env Var:     RCLONE_CHUNKER_START_FROM
+- Type:        int
+- Default:     1
+
+#### --chunker-meta-format
+
+Format of the metadata object or &quot;none&quot;. By default &quot;simplejson&quot;.
+Metadata is a small JSON file named after the composite file.
+
+- Config:      meta_format
+- Env Var:     RCLONE_CHUNKER_META_FORMAT
+- Type:        string
+- Default:     &quot;simplejson&quot;
+- Examples:
+    - &quot;none&quot;
+        - Do not use metadata files at all. Requires hash type &quot;none&quot;.
+    - &quot;simplejson&quot;
+        - Simple JSON supports hash sums and chunk validation.
+        - It has the following fields: ver, size, nchunks, md5, sha1.
+
+#### --chunker-fail-hard
+
+Choose how chunker should handle files with missing or invalid chunks.
+
+- Config:      fail_hard
+- Env Var:     RCLONE_CHUNKER_FAIL_HARD
+- Type:        bool
+- Default:     false
+- Examples:
+    - &quot;true&quot;
+        - Report errors and abort current command.
+    - &quot;false&quot;
+        - Warn user, skip incomplete file and proceed.
+
+
+
+##  Citrix ShareFile
+
+[Citrix ShareFile](https://sharefile.com) is a secure file sharing and transfer service aimed as business.
+
+The initial setup for Citrix ShareFile involves getting a token from
+Citrix ShareFile which you can in your browser.  `rclone config` walks you
+through it.
+
+Here is an example of how to make a remote called `remote`.  First run:
+
+     rclone config
+
+This will guide you through an interactive setup process:
+</code></pre>
+<p>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 (""). Choose a number from below, or type in your own value XX / Citrix Sharefile  "sharefile" Storage&gt; sharefile ** See help for sharefile backend at: https://rclone.org/sharefile/ **</p>
+<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). Enter a string value. Press Enter for the default (""). Choose a number from below, or type in your own value 1 / Access the Personal Folders. (Default)  "" 2 / Access the Favorites folder.  "favorites" 3 / Access all the shared folders.  "allshared" 4 / Access all the individual connectors.  "connectors" 5 / Access the home, favorites, and shared folders as well as the connectors.  "top" root_folder_id&gt; Edit advanced config? (y/n) y) Yes n) No y/n&gt; n Remote config Use auto config? * Say Y if not sure * Say N if you are working on a remote or headless machine y) Yes n) No y/n&gt; y If your browser doesn'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 -------------------- [remote] type = sharefile endpoint = https://XXX.sharefile.com token = {"access_token":"XXX","token_type":"bearer","refresh_token":"XXX","expiry":"2019-09-30T19:41:45.878561877+01:00"} -------------------- y) Yes this is OK e) Edit this remote d) Delete this remote y/e/d&gt; y</p>
+<pre><code>
+See the [remote setup docs](https://rclone.org/remote_setup/) for how to set it up on a
+machine with no Internet browser available.
+
+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 `http://127.0.0.1:53682/` and this it may require you to unblock
+it temporarily if you are running a host firewall.
+
+Once configured you can then use `rclone` like this,
+
+List directories in top level of your ShareFile
+
+    rclone lsd remote:
+
+List all the files in your ShareFile
+
+    rclone ls remote:
+
+To copy a local directory to an ShareFile directory called backup
+
+    rclone copy /home/source remote:backup
+
+Paths may be as deep as required, eg `remote:directory/subdirectory`.
+
+### Modified time and hashes ###
+
+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.
+
+ShareFile supports MD5 type hashes, so you can use the `--checksum`
+flag.
+
+### Transfers ###
+
+For files above 128MB rclone will use a chunked transfer.  Rclone will
+upload up to `--transfers` chunks at the same time (shared among all
+the multipart uploads).  Chunks are buffered in memory and are
+normally 64MB so increasing `--transfers` will increase memory use.
+
+### Limitations ###
+
+Note that ShareFile is case insensitive so you can&#39;t have a file called
+&quot;Hello.doc&quot; and one called &quot;hello.doc&quot;.
+
+ShareFile only supports filenames up to 256 characters in length.
+
+#### Restricted filename characters
+
+In addition to the [default restricted characters set](https://rclone.org/overview/#restricted-characters)
+the following characters are also replaced:
+
+| Character | Value | Replacement |
+| --------- |:-----:|:-----------:|
+| \\        | 0x5C  | ＼           |
+| *         | 0x2A  | ＊           |
+| &lt;         | 0x3C  | ＜           |
+| &gt;         | 0x3E  | ＞           |
+| ?         | 0x3F  | ？           |
+| :         | 0x3A  | ：           |
+| \|        | 0x7C  | ｜           |
+| &quot;         | 0x22  | ＂           |
+
+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:
+
+| Character | Value | Replacement |
+| --------- |:-----:|:-----------:|
+| SP        | 0x20  | ␠           |
+| .         | 0x2E  | ．           |
+
+Invalid UTF-8 bytes will also be [replaced](https://rclone.org/overview/#invalid-utf8),
+as they can&#39;t be used in JSON strings.
+
+
+### Standard Options
+
+Here are the standard options specific to sharefile (Citrix Sharefile).
+
+#### --sharefile-root-folder-id
 
 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 auto config?
- * Say Y if not sure
- * Say N if you are working on a remote or headless machine
-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
---------------------
-[remote]
-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;}
---------------------
-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, eg <code>remote:directory/subdirectory</code>.</p>
-<h3 id="modified-time-and-hashes-2">Modified time 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 128MB 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 64MB so increasing <code>--transfers</code> will increase memory use.</p>
-<h3 id="limitations-4">Limitations</h3>
-<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>
-<h4 id="restricted-filename-characters-5">Restricted filename characters</h4>
-<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-8">Standard Options</h3>
-<p>Here are the standard options specific to sharefile (Citrix Sharefile).</p>
-<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>
-<ul>
-<li>Config: root_folder_id</li>
-<li>Env Var: RCLONE_SHAREFILE_ROOT_FOLDER_ID</li>
-<li>Type: string</li>
-<li>Default: ""</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-upload-cutoff">–sharefile-upload-cutoff</h4>
-<p>Cutoff for switching to multipart upload.</p>
-<ul>
-<li>Config: upload_cutoff</li>
-<li>Env Var: RCLONE_SHAREFILE_UPLOAD_CUTOFF</li>
-<li>Type: SizeSuffix</li>
-<li>Default: 128M</li>
-</ul>
-<h4 id="sharefile-chunk-size">–sharefile-chunk-size</h4>
-<p>Upload chunk size. 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>
-<ul>
-<li>Config: chunk_size</li>
-<li>Env Var: RCLONE_SHAREFILE_CHUNK_SIZE</li>
-<li>Type: SizeSuffix</li>
-<li>Default: 64M</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>
-<ul>
-<li>Config: endpoint</li>
-<li>Env Var: RCLONE_SHAREFILE_ENDPOINT</li>
-<li>Type: string</li>
-<li>Default: ""</li>
-</ul>
-<h4 id="sharefile-encoding">–sharefile-encoding</h4>
-<p>This sets 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>
-<ul>
-<li>Config: encoding</li>
-<li>Env Var: RCLONE_SHAREFILE_ENCODING</li>
-<li>Type: MultiEncoder</li>
-<li>Default: Slash,LtGt,DoubleQuote,Colon,Question,Asterisk,Pipe,BackSlash,Ctl,LeftSpace,LeftPeriod,RightSpace,RightPeriod,InvalidUtf8,Dot</li>
-</ul>
-<h2 id="crypt">Crypt</h2>
-<p>The <code>crypt</code> remote encrypts and decrypts another remote.</p>
-<p>To use it first set up the underlying remote following the config instructions for that remote. You can also use a local pathname instead of a remote which will encrypt and decrypt from that directory which might be useful for encrypting onto a USB stick for example.</p>
-<p>First check your chosen remote is working - we’ll call it <code>remote:path</code> in these docs. Note that anything inside <code>remote:path</code> will be encrypted and anything outside won’t. This means that if you are using a bucket based remote (eg S3, B2, swift) then you should probably put the bucket in the remote <code>s3:bucket</code>. If you just use <code>s3:</code> then rclone will make encrypted bucket names too (if using file name encryption) which may or may not be what you want.</p>
-<p>Now configure <code>crypt</code> using <code>rclone config</code>. We will call this one <code>secret</code> to differentiate it from the <code>remote</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; secret
-Type of storage to configure.
-Choose a number from below, or type in your own value
-[snip]
-XX / Encrypt/Decrypt a remote
-   \ &quot;crypt&quot;
-[snip]
-Storage&gt; crypt
+
+- Config:      root_folder_id
+- Env Var:     RCLONE_SHAREFILE_ROOT_FOLDER_ID
+- Type:        string
+- Default:     &quot;&quot;
+- Examples:
+    - &quot;&quot;
+        - Access the Personal Folders. (Default)
+    - &quot;favorites&quot;
+        - Access the Favorites folder.
+    - &quot;allshared&quot;
+        - Access all the shared folders.
+    - &quot;connectors&quot;
+        - Access all the individual connectors.
+    - &quot;top&quot;
+        - Access the home, favorites, and shared folders as well as the connectors.
+
+### Advanced Options
+
+Here are the advanced options specific to sharefile (Citrix Sharefile).
+
+#### --sharefile-upload-cutoff
+
+Cutoff for switching to multipart upload.
+
+- Config:      upload_cutoff
+- Env Var:     RCLONE_SHAREFILE_UPLOAD_CUTOFF
+- Type:        SizeSuffix
+- Default:     128M
+
+#### --sharefile-chunk-size
+
+Upload chunk size. Must a power of 2 &gt;= 256k.
+
+Making this larger will improve performance, but note that each chunk
+is buffered in memory one per transfer.
+
+Reducing this will reduce memory usage but decrease performance.
+
+- Config:      chunk_size
+- Env Var:     RCLONE_SHAREFILE_CHUNK_SIZE
+- Type:        SizeSuffix
+- Default:     64M
+
+#### --sharefile-endpoint
+
+Endpoint for API calls.
+
+This is usually auto discovered as part of the oauth process, but can
+be set manually to something like: https://XXX.sharefile.com
+
+
+- Config:      endpoint
+- Env Var:     RCLONE_SHAREFILE_ENDPOINT
+- Type:        string
+- Default:     &quot;&quot;
+
+#### --sharefile-encoding
+
+This sets the encoding for the backend.
+
+See: the [encoding section in the overview](https://rclone.org/overview/#encoding) for more info.
+
+- Config:      encoding
+- Env Var:     RCLONE_SHAREFILE_ENCODING
+- Type:        MultiEncoder
+- Default:     Slash,LtGt,DoubleQuote,Colon,Question,Asterisk,Pipe,BackSlash,Ctl,LeftSpace,LeftPeriod,RightSpace,RightPeriod,InvalidUtf8,Dot
+
+
+
+Crypt
+----------------------------------------
+
+The `crypt` remote encrypts and decrypts another remote.
+
+To use it first set up the underlying remote following the config
+instructions for that remote.  You can also use a local pathname
+instead of a remote which will encrypt and decrypt from that directory
+which might be useful for encrypting onto a USB stick for example.
+
+First check your chosen remote is working - we&#39;ll call it
+`remote:path` in these docs.  Note that anything inside `remote:path`
+will be encrypted and anything outside won&#39;t.  This means that if you
+are using a bucket based remote (eg S3, B2, swift) then you should
+probably put the bucket in the remote `s3:bucket`. If you just use
+`s3:` then rclone will make encrypted bucket names too (if using file
+name encryption) which may or may not be what you want.
+
+Now configure `crypt` using `rclone config`. We will call this one
+`secret` to differentiate it from the `remote`.
+</code></pre>
+<p>No remotes found - make a new one n) New remote s) Set configuration password q) Quit config n/s/q&gt; n<br />
+name&gt; secret Type of storage to configure. Choose a number from below, or type in your own value [snip] XX / Encrypt/Decrypt a remote  "crypt" [snip] Storage&gt; crypt Remote to encrypt/decrypt. Normally should contain a ':' and a path, eg "myremote:path/to/dir", "myremote:bucket" or maybe "myremote:" (not recommended). remote&gt; remote:path How to encrypt the filenames. Choose a number from below, or type in your own value 1 / Don't encrypt the file names. Adds a ".bin" extension only.  "off" 2 / Encrypt the filenames see the docs for the details.  "standard" 3 / Very simple filename obfuscation.  "obfuscate" filename_encryption&gt; 2 Option to either encrypt directory names or leave them intact. Choose a number from below, or type in your own value 1 / Encrypt directory names.  "true" 2 / Don't encrypt directory names, leave them intact.  "false" filename_encryption&gt; 1 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 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? y) Yes n) No y/n&gt; y Remote config -------------------- [secret] remote = remote:path filename_encryption = standard password = *** ENCRYPTED <strong><em> password2 = </em></strong> ENCRYPTED *** -------------------- y) Yes this is OK e) Edit this remote d) Delete this remote y/e/d&gt; y</p>
+<pre><code>
+**Important** The password is stored in the config file is lightly
+obscured so it isn&#39;t immediately obvious what it is.  It is in no way
+secure unless you use config file encryption.
+
+A long passphrase is recommended, or you can use a random one.
+
+The obscured password is created by using AES-CTR with a static key, with
+the salt stored verbatim at the beginning of the obscured password. This
+static key is shared by between all versions of rclone.
+
+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.
+
+Note that rclone does not encrypt
+
+  * file length - this can be calculated within 16 bytes
+  * modification time - used for syncing
+
+## Specifying the remote ##
+
+In normal use, make sure the remote has a `:` in. If you specify the
+remote without a `:` then rclone will use a local directory of that
+name.  So if you use a remote of `/path/to/secret/files` then rclone
+will encrypt stuff to that directory.  If you use a remote of `name`
+then rclone will put files in a directory called `name` in the current
+directory.
+
+If you specify the remote as `remote:path/to/dir` then rclone will
+store encrypted files in `path/to/dir` on the remote. If you are using
+file name encryption, then when you save files to
+`secret:subdir/subfile` this will store them in the unencrypted path
+`path/to/dir` but the `subdir/subpath` bit will be encrypted.
+
+Note that unless you want encrypted bucket names (which are difficult
+to manage because you won&#39;t know what directory they represent in web
+interfaces etc), you should probably specify a bucket, eg
+`remote:secretbucket` when using bucket based remotes such as S3,
+Swift, Hubic, B2, GCS.
+
+## Example ##
+
+To test I made a little directory of files using &quot;standard&quot; file name
+encryption.
+</code></pre>
+<p>plaintext/ ├── file0.txt ├── file1.txt └── subdir ├── file2.txt ├── file3.txt └── subsubdir └── file4.txt</p>
+<pre><code>
+Copy these to the remote and list them back
+</code></pre>
+<p>$ 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</p>
+<pre><code>
+Now see what that looked like when encrypted
+</code></pre>
+<p>$ rclone -q ls remote:path 55 hagjclgavj2mbiqm6u6cnjjqcg 54 v05749mltvv1tf4onltun46gls 57 86vhrsv86mpbtd3a0akjuqslj8/dlj7fkq4kdq72emafg7a7s41uo 58 86vhrsv86mpbtd3a0akjuqslj8/7uu829995du6o42n32otfhjqp4/b9pausrfansjth5ob3jkdqd4lc 56 86vhrsv86mpbtd3a0akjuqslj8/8njh1sk437gttmep3p70g81aps</p>
+<pre><code>
+Note that this retains the directory structure which means you can do this
+</code></pre>
+<p>$ rclone -q ls secret:subdir 8 file2.txt 9 file3.txt 10 subsubdir/file4.txt</p>
+<pre><code>
+If don&#39;t use file name encryption then the remote will look like this
+- note the `.bin` extensions added to prevent the cloud provider
+attempting to interpret the data.
+</code></pre>
+<p>$ 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</p>
+<pre><code>
+### File name encryption modes ###
+
+Here are some of the features of the file name encryption modes
+
+Off
+
+  * doesn&#39;t hide file names or directory structure
+  * allows for longer file names (~246 characters)
+  * can use sub paths and copy single files
+
+Standard
+
+  * file names encrypted
+  * file names can&#39;t be as long (~143 characters)
+  * can use sub paths and copy single files
+  * directory structure visible
+  * identical files names will have identical uploaded names
+  * can use shortcuts to shorten the directory recursion
+
+Obfuscation
+
+This is a simple &quot;rotate&quot; of the filename, with each file having a rot
+distance based on the filename. We store the distance at the beginning
+of the filename. So a file called &quot;hello&quot; may become &quot;53.jgnnq&quot;.
+
+This is not a strong encryption of filenames, but it may stop automated
+scanning tools from picking up on filename patterns. As such it&#39;s an
+intermediate between &quot;off&quot; and &quot;standard&quot;. The advantage is that it
+allows for longer path segment names.
+
+There is a possibility with some unicode based filenames that the
+obfuscation is weak and may map lower case characters to upper case
+equivalents.  You can not rely on this for strong protection.
+
+  * file names very lightly obfuscated
+  * file names can be longer than standard encryption
+  * can use sub paths and copy single files
+  * directory structure visible
+  * identical files names will have identical uploaded names
+
+Cloud storage systems have various limits on file name length and
+total path length which you are more likely to hit using &quot;Standard&quot;
+file name encryption.  If you keep your file names to below 156
+characters in length then you should be OK on all providers.
+
+There may be an even more secure file name encryption mode in the
+future which will address the long file name problem.
+
+### Directory name encryption ###
+Crypt offers the option of encrypting dir names or leaving them intact.
+There are two options:
+
+True
+
+Encrypts the whole file path including directory names
+Example:
+`1/12/123.txt` is encrypted to
+`p0e52nreeaj0a5ea7s64m4j72s/l42g6771hnv3an9cgc8cr2n1ng/qgm4avr35m5loi1th53ato71v0`
+
+False
+
+Only encrypts file names, skips directory names
+Example:
+`1/12/123.txt` is encrypted to
+`1/12/qgm4avr35m5loi1th53ato71v0`
+
+
+### Modified time and hashes ###
+
+Crypt stores modification times using the underlying remote so support
+depends on that.
+
+Hashes are not stored for crypt.  However the data integrity is
+protected by an extremely strong crypto authenticator.
+
+Note that you should use the `rclone cryptcheck` command to check the
+integrity of a crypted remote instead of `rclone check` which can&#39;t
+check the checksums properly.
+
+
+### Standard Options
+
+Here are the standard options specific to crypt (Encrypt/Decrypt a remote).
+
+#### --crypt-remote
+
 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).
-remote&gt; remote:path
+
+- Config:      remote
+- Env Var:     RCLONE_CRYPT_REMOTE
+- Type:        string
+- Default:     &quot;&quot;
+
+#### --crypt-filename-encryption
+
 How to encrypt the filenames.
-Choose a number from below, or type in your own value
- 1 / Don&#39;t encrypt the file names.  Adds a &quot;.bin&quot; extension only.
-   \ &quot;off&quot;
- 2 / Encrypt the filenames see the docs for the details.
-   \ &quot;standard&quot;
- 3 / Very simple filename obfuscation.
-   \ &quot;obfuscate&quot;
-filename_encryption&gt; 2
+
+- Config:      filename_encryption
+- Env Var:     RCLONE_CRYPT_FILENAME_ENCRYPTION
+- Type:        string
+- Default:     &quot;standard&quot;
+- Examples:
+    - &quot;standard&quot;
+        - Encrypt the filenames see the docs for the details.
+    - &quot;obfuscate&quot;
+        - Very simple filename obfuscation.
+    - &quot;off&quot;
+        - Don&#39;t encrypt the file names.  Adds a &quot;.bin&quot; extension only.
+
+#### --crypt-directory-name-encryption
+
 Option to either encrypt directory names or leave them intact.
-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;
-filename_encryption&gt; 1
+
+NB If filename_encryption is &quot;off&quot; then this option will do nothing.
+
+- Config:      directory_name_encryption
+- Env Var:     RCLONE_CRYPT_DIRECTORY_NAME_ENCRYPTION
+- Type:        bool
+- Default:     true
+- Examples:
+    - &quot;true&quot;
+        - Encrypt directory names.
+    - &quot;false&quot;
+        - Don&#39;t encrypt directory names, leave them intact.
+
+#### --crypt-password
+
 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:
+
+**NB** Input to this must be obscured - see [rclone obscure](https://rclone.org/commands/rclone_obscure/).
+
+- Config:      password
+- Env Var:     RCLONE_CRYPT_PASSWORD
+- Type:        string
+- Default:     &quot;&quot;
+
+#### --crypt-password2
+
 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
-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?
-y) Yes
-n) No
-y/n&gt; y
-Remote config
---------------------
-[secret]
-remote = remote:path
-filename_encryption = standard
-password = *** ENCRYPTED ***
-password2 = *** ENCRYPTED ***
---------------------
-y) Yes this is OK
-e) Edit this remote
-d) Delete this remote
-y/e/d&gt; y</code></pre>
-<p><strong>Important</strong> The password is stored in the config file is lightly obscured so it isn’t immediately obvious what it is. It is in no way secure unless you use config file encryption.</p>
-<p>A long passphrase is recommended, or you can use a random one.</p>
-<p>The obscured password is created by using AES-CTR with a static key, with the salt stored verbatim at the beginning of the obscured password. This static key is shared by 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>Note that 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>
-<h2 id="specifying-the-remote-1">Specifying the remote</h2>
-<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 encrypt stuff to 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>
-<p>If you specify the remote as <code>remote:path/to/dir</code> then rclone will store encrypted files in <code>path/to/dir</code> on the remote. If you are using file name encryption, then when you save files to <code>secret:subdir/subfile</code> this will store them in the unencrypted path <code>path/to/dir</code> but the <code>subdir/subpath</code> bit will be encrypted.</p>
-<p>Note that unless you want encrypted bucket names (which are difficult to manage because you won’t know what directory they represent in web interfaces etc), you should probably specify a bucket, eg <code>remote:secretbucket</code> when using bucket based remotes such as S3, Swift, Hubic, B2, GCS.</p>
-<h2 id="example">Example</h2>
-<p>To test I made a little directory of files 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 back</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>Now see what that looked like when encrypted</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>Note that this retains the directory structure which means you can do this</p>
-<pre><code>$ rclone -q ls secret:subdir
-        8 file2.txt
-        9 file3.txt
-       10 subsubdir/file4.txt</code></pre>
-<p>If don’t use file name encryption then the remote will look like this - note the <code>.bin</code> extensions added to prevent the cloud provider attempting to interpret the data.</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>Here are some of the features of the file name encryption modes</p>
-<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. We store the distance at the beginning of the filename. So a file called “hello” may become “53.jgnnq”.</p>
-<p>This is not a strong encryption of filenames, but it may stop automated scanning tools from picking up on filename patterns. As such it’s an intermediate between “off” and “standard”. The advantage is that it 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. You can not rely on this 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 various limits on file name length and total path length which you are more likely to hit using “Standard” file name encryption. If you keep your file names to below 156 characters in length then you should be OK on all providers.</p>
-<p>There may be an even more secure file name encryption mode in the future which will address the long file name problem.</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="modified-time-and-hashes-3">Modified time 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>Note that you should use the <code>rclone cryptcheck</code> command to check the integrity of a crypted remote instead of <code>rclone check</code> which can’t check the checksums properly.</p>
-<h3 id="standard-options-9">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. Normally should contain a ‘:’ and a path, eg “myremote:path/to/dir”, “myremote:bucket” or maybe “myremote:” (not recommended).</p>
-<ul>
-<li>Config: remote</li>
-<li>Env Var: RCLONE_CRYPT_REMOTE</li>
-<li>Type: string</li>
-<li>Default: ""</li>
-</ul>
-<h4 id="crypt-filename-encryption">–crypt-filename-encryption</h4>
-<p>How to encrypt the filenames.</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 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. Adds a “.bin” 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>
-<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>
-<ul>
-<li>Config: password</li>
-<li>Env Var: RCLONE_CRYPT_PASSWORD</li>
-<li>Type: string</li>
-<li>Default: ""</li>
-</ul>
-<h4 id="crypt-password2">–crypt-password2</h4>
-<p>Password or pass phrase for salt. Optional but recommended. Should be different to the previous password.</p>
-<ul>
-<li>Config: password2</li>
-<li>Env Var: RCLONE_CRYPT_PASSWORD2</li>
-<li>Type: string</li>
-<li>Default: ""</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-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>
-<ul>
-<li>Config: show_mapping</li>
-<li>Env Var: RCLONE_CRYPT_SHOW_MAPPING</li>
-<li>Type: bool</li>
-<li>Default: false</li>
-</ul>
-<h3 id="backend-commands-1">Backend commands</h3>
-<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 <a href="https://rclone.org/commands/rclone_backend/">the “rclone backend” command</a> 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>
-<h4 id="encode">encode</h4>
-<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>
-<h4 id="decode">decode</h4>
-<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-a-crypted-remote">Backing up a crypted remote</h2>
-<p>If you wish to backup a crypted 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 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 re-used 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 64kB 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">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>1MB (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 (eg Windows, Amazon Drive).</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="dropbox">Dropbox</h2>
-<p>Paths are specified as <code>remote:path</code></p>
-<p>Dropbox paths may be as deep as required, eg <code>remote:directory/subdirectory</code>.</p>
-<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
---------------------
-[remote]
-app_key =
-app_secret =
-token = XXXXXXXXXXXXXXXXXXXXXXXXXXXXX_XXXX_XXXXXXXXXXXXXXXXXXXXXXXXXXXXX
---------------------
-y) Yes this is OK
-e) Edit this remote
-d) Delete this remote
-y/e/d&gt; y</code></pre>
-<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="modified-time-and-hashes-4">Modified time 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>
-<h4 id="restricted-filename-characters-6">Restricted filename characters</h4>
-<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="standard-options-10">Standard Options</h3>
-<p>Here are the standard options specific to dropbox (Dropbox).</p>
-<h4 id="dropbox-client-id">–dropbox-client-id</h4>
-<p>Dropbox App Client Id Leave blank normally.</p>
-<ul>
-<li>Config: client_id</li>
-<li>Env Var: RCLONE_DROPBOX_CLIENT_ID</li>
-<li>Type: string</li>
-<li>Default: ""</li>
-</ul>
-<h4 id="dropbox-client-secret">–dropbox-client-secret</h4>
-<p>Dropbox App Client Secret Leave blank normally.</p>
-<ul>
-<li>Config: client_secret</li>
-<li>Env Var: RCLONE_DROPBOX_CLIENT_SECRET</li>
-<li>Type: string</li>
-<li>Default: ""</li>
-</ul>
-<h3 id="advanced-options-9">Advanced Options</h3>
-<p>Here are the advanced options specific to dropbox (Dropbox).</p>
-<h4 id="dropbox-chunk-size">–dropbox-chunk-size</h4>
-<p>Upload chunk size. (&lt; 150M).</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 128MB in tests) at the cost of using more memory. It can be set smaller if you are tight on memory.</p>
-<ul>
-<li>Config: chunk_size</li>
-<li>Env Var: RCLONE_DROPBOX_CHUNK_SIZE</li>
-<li>Type: SizeSuffix</li>
-<li>Default: 48M</li>
-</ul>
-<h4 id="dropbox-impersonate">–dropbox-impersonate</h4>
-<p>Impersonate this user when using a business account.</p>
-<ul>
-<li>Config: impersonate</li>
-<li>Env Var: RCLONE_DROPBOX_IMPERSONATE</li>
-<li>Type: string</li>
-<li>Default: ""</li>
-</ul>
-<h4 id="dropbox-encoding">–dropbox-encoding</h4>
-<p>This sets 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>
-<ul>
-<li>Config: encoding</li>
-<li>Env Var: RCLONE_DROPBOX_ENCODING</li>
-<li>Type: MultiEncoder</li>
-<li>Default: Slash,BackSlash,Del,RightSpace,InvalidUtf8,Dot</li>
-</ul>
-<h3 id="limitations-5">Limitations</h3>
-<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>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>
-<h3 id="get-your-own-dropbox-app-id">Get your own Dropbox App ID</h3>
-<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></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>Fill <code>Redirect URIs</code> as <code>http://localhost:53682/</code></p></li>
-<li><p>Find the <code>App key</code> and <code>App secret</code> Use these values in rclone config to add a new remote or edit an existing remote.</p></li>
+
+**NB** Input to this must be obscured - see [rclone obscure](https://rclone.org/commands/rclone_obscure/).
+
+- Config:      password2
+- Env Var:     RCLONE_CRYPT_PASSWORD2
+- Type:        string
+- Default:     &quot;&quot;
+
+### Advanced Options
+
+Here are the advanced options specific to crypt (Encrypt/Decrypt a remote).
+
+#### --crypt-server-side-across-configs
+
+Allow server side operations (eg copy) to work across different crypt configs.
+
+Normally this option is not what you want, but if you have two crypts
+pointing to the same backend you can use it.
+
+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.
+
+- Config:      server_side_across_configs
+- Env Var:     RCLONE_CRYPT_SERVER_SIDE_ACROSS_CONFIGS
+- Type:        bool
+- Default:     false
+
+#### --crypt-show-mapping
+
+For all files listed show how the names encrypt.
+
+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.
+
+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.
+
+- Config:      show_mapping
+- Env Var:     RCLONE_CRYPT_SHOW_MAPPING
+- Type:        bool
+- Default:     false
+
+### Backend commands
+
+Here are the commands specific to the crypt backend.
+
+Run them with
+
+    rclone backend COMMAND remote:
+
+The help below will explain what arguments each command takes.
+
+See [the &quot;rclone backend&quot; command](https://rclone.org/commands/rclone_backend/) for more
+info on how to pass options and arguments.
+
+These can be run on a running backend using the rc command
+[backend/command](https://rclone.org/rc/#backend/command).
+
+#### encode
+
+Encode the given filename(s)
+
+    rclone backend encode remote: [options] [&lt;arguments&gt;+]
+
+This encodes the filenames given as arguments returning a list of
+strings of the encoded results.
+
+Usage Example:
+
+    rclone backend encode crypt: file1 [file2...]
+    rclone rc backend/command command=encode fs=crypt: file1 [file2...]
+
+
+#### decode
+
+Decode the given filename(s)
+
+    rclone backend decode remote: [options] [&lt;arguments&gt;+]
+
+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.
+
+Usage Example:
+
+    rclone backend decode crypt: encryptedfile1 [encryptedfile2...]
+    rclone rc backend/command command=decode fs=crypt: encryptedfile1 [encryptedfile2...]
+
+
+
+
+## Backing up a crypted remote ##
+
+If you wish to backup a crypted remote, it is recommended that you use
+`rclone sync` on the encrypted files, and make sure the passwords are
+the same in the new encrypted remote.
+
+This will have the following advantages
+
+  * `rclone sync` will check the checksums while copying
+  * you can use `rclone check` between the encrypted remotes
+  * you don&#39;t decrypt and encrypt unnecessarily
+
+For example, let&#39;s say you have your original remote at `remote:` with
+the encrypted version at `eremote:` with path `remote:crypt`.  You
+would then set up the new remote `remote2:` and then the encrypted
+version `eremote2:` with path `remote2:crypt` using the same passwords
+as `eremote:`.
+
+To sync the two remotes you would do
+
+    rclone sync -i remote:crypt remote2:crypt
+
+And to check the integrity you would do
+
+    rclone check remote:crypt remote2:crypt
+
+## File formats ##
+
+### File encryption ###
+
+Files are encrypted 1:1 source file to destination object.  The file
+has a header and is divided into chunks.
+
+#### Header ####
+
+  * 8 bytes magic string `RCLONE\x00\x00`
+  * 24 bytes Nonce (IV)
+
+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 re-used 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.
+
+#### Chunk ####
+
+Each chunk will contain 64kB 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.
+
+Each chunk contains:
+
+  * 16 Bytes of Poly1305 authenticator
+  * 1 - 65536 bytes XSalsa20 encrypted data
+
+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&#39;t be too big.
+
+This uses a 32 byte (256 bit key) key derived from the user password.
+
+#### Examples ####
+
+1 byte file will encrypt to
+
+  * 32 bytes header
+  * 17 bytes data chunk
+
+49 bytes total
+
+1MB (1048576 bytes) file will encrypt to
+
+  * 32 bytes header
+  * 16 chunks of 65568 bytes
+
+1049120 bytes total (a 0.05% overhead).  This is the overhead for big
+files.
+
+### Name encryption ###
+
+File names are encrypted segment by segment - the path is broken up
+into `/` separated strings and these are encrypted individually.
+
+File segments are padded using PKCS#7 to a multiple of 16 bytes
+before encryption.
+
+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 &quot;A Parallelizable Enciphering Mode&quot; by Halevi and Rogaway.
+
+This makes for deterministic encryption which is what we want - the
+same filename must encrypt to the same thing otherwise we can&#39;t find
+it on the cloud storage system.
+
+This means that
+
+  * filenames with the same name will encrypt the same
+  * filenames which start the same won&#39;t have a common prefix
+
+This uses a 32 byte key (256 bits) and a 16 byte (128 bits) IV both of
+which are derived from the user password.
+
+After encryption they are written out using a modified version of
+standard `base32` encoding as described in RFC4648.  The standard
+encoding is modified in two ways:
+
+  * it becomes lower case (no-one likes upper case filenames!)
+  * we strip the padding character `=`
+
+`base32` is used rather than the more efficient `base64` so rclone can be
+used on case insensitive remotes (eg Windows, Amazon Drive).
+
+### Key derivation ###
+
+Rclone uses `scrypt` with parameters `N=16384, r=8, p=1` with an
+optional user supplied salt (password2) to derive the 32+32+16 = 80
+bytes of key material required.  If the user doesn&#39;t supply a salt
+then rclone uses an internal one.
+
+`scrypt` makes it impractical to mount a dictionary attack on rclone
+encrypted data.  For full protection against this you should always use
+a salt.
+
+ Dropbox
+---------------------------------
+
+Paths are specified as `remote:path`
+
+Dropbox paths may be as deep as required, eg
+`remote:directory/subdirectory`.
+
+The initial setup for dropbox involves getting a token from Dropbox
+which you need to do in your browser.  `rclone config` walks you
+through it.
+
+Here is an example of how to make a remote called `remote`.  First run:
+
+     rclone config
+
+This will guide you through an interactive setup process:
+</code></pre>
+<ol start="14" type="a">
+<li>New remote</li>
+<li>Delete remote</li>
+<li>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  "dropbox" [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 -------------------- [remote] app_key = app_secret = token = XXXXXXXXXXXXXXXXXXXXXXXXXXXXX_XXXX_XXXXXXXXXXXXXXXXXXXXXXXXXXXXX --------------------</li>
+<li>Yes this is OK</li>
+<li>Edit this remote</li>
+<li>Delete this remote y/e/d&gt; y</li>
 </ol>
-<h2 id="ftp">FTP</h2>
-<p>FTP is the File Transfer Protocol. FTP support is provided using the <a href="https://godoc.org/github.com/jlaffaye/ftp">github.com/jlaffaye/ftp</a> package.</p>
-<p>Here is an example of making an FTP configuration. First run</p>
-<pre><code>rclone config</code></pre>
-<p>This will guide you through an interactive setup process. An FTP remote only needs a host together with and a username and a password. With anonymous FTP server, you will need to use <code>anonymous</code> as username and your email address as the password.</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 Connection
-   \ &quot;ftp&quot;
-[snip]
-Storage&gt; ftp
-** See help for ftp backend at: https://rclone.org/ftp/ **
+<pre><code>
+You can then use it like this,
+
+List directories in top level of your dropbox
+
+    rclone lsd remote:
+
+List all the files in your dropbox
+
+    rclone ls remote:
+
+To copy a local directory to a dropbox directory called backup
+
+    rclone copy /home/source remote:backup
+
+### Dropbox for business ###
+
+Rclone supports Dropbox for business and Team Folders.
+
+When using Dropbox for business `remote:` and `remote:path/to/file`
+will refer to your personal folder.
+
+If you wish to see Team Folders you must use a leading `/` in the
+path, so `rclone lsd remote:/` will refer to the root and show you all
+Team Folders and your User Folder.
+
+You can then use team folders like this `remote:/TeamFolder` and
+`remote:/TeamFolder/path/to/file`.
+
+A leading `/` for a Dropbox personal account will do nothing, but it
+will take an extra HTTP transaction so it should be avoided.
+
+### Modified time and Hashes ###
+
+Dropbox supports modified times, but the only way to set a
+modification time is to re-upload the file.
+
+This means that if you uploaded your data with an older version of
+rclone which didn&#39;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&#39;t want this to happen use `--size-only` or `--checksum` flag
+to stop it.
+
+Dropbox supports [its own hash
+type](https://www.dropbox.com/developers/reference/content-hash) which
+is checked for all transfers.
+
+#### Restricted filename characters
+
+| Character | Value | Replacement |
+| --------- |:-----:|:-----------:|
+| NUL       | 0x00  | ␀           |
+| /         | 0x2F  | ／           |
+| DEL       | 0x7F  | ␡           |
+| \         | 0x5C  | ＼           |
+
+File names can also not end with the following characters.
+These only get replaced if they are the last character in the name:
+
+| Character | Value | Replacement |
+| --------- |:-----:|:-----------:|
+| SP        | 0x20  | ␠           |
+
+Invalid UTF-8 bytes will also be [replaced](https://rclone.org/overview/#invalid-utf8),
+as they can&#39;t be used in JSON strings.
+
+
+### Standard Options
+
+Here are the standard options specific to dropbox (Dropbox).
+
+#### --dropbox-client-id
+
+OAuth Client Id
+Leave blank normally.
+
+- Config:      client_id
+- Env Var:     RCLONE_DROPBOX_CLIENT_ID
+- Type:        string
+- Default:     &quot;&quot;
+
+#### --dropbox-client-secret
+
+OAuth Client Secret
+Leave blank normally.
+
+- Config:      client_secret
+- Env Var:     RCLONE_DROPBOX_CLIENT_SECRET
+- Type:        string
+- Default:     &quot;&quot;
+
+### Advanced Options
+
+Here are the advanced options specific to dropbox (Dropbox).
+
+#### --dropbox-token
+
+OAuth Access Token as a JSON blob.
+
+- Config:      token
+- Env Var:     RCLONE_DROPBOX_TOKEN
+- Type:        string
+- Default:     &quot;&quot;
+
+#### --dropbox-auth-url
+
+Auth server URL.
+Leave blank to use the provider defaults.
+
+- Config:      auth_url
+- Env Var:     RCLONE_DROPBOX_AUTH_URL
+- Type:        string
+- Default:     &quot;&quot;
+
+#### --dropbox-token-url
+
+Token server url.
+Leave blank to use the provider defaults.
+
+- Config:      token_url
+- Env Var:     RCLONE_DROPBOX_TOKEN_URL
+- Type:        string
+- Default:     &quot;&quot;
+
+#### --dropbox-chunk-size
+
+Upload chunk size. (&lt; 150M).
+
+Any files larger than this will be uploaded in chunks of this size.
+
+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 128MB in tests) at the cost of using more
+memory.  It can be set smaller if you are tight on memory.
+
+- Config:      chunk_size
+- Env Var:     RCLONE_DROPBOX_CHUNK_SIZE
+- Type:        SizeSuffix
+- Default:     48M
+
+#### --dropbox-impersonate
+
+Impersonate this user when using a business account.
+
+- Config:      impersonate
+- Env Var:     RCLONE_DROPBOX_IMPERSONATE
+- Type:        string
+- Default:     &quot;&quot;
+
+#### --dropbox-encoding
+
+This sets the encoding for the backend.
+
+See: the [encoding section in the overview](https://rclone.org/overview/#encoding) for more info.
+
+- Config:      encoding
+- Env Var:     RCLONE_DROPBOX_ENCODING
+- Type:        MultiEncoder
+- Default:     Slash,BackSlash,Del,RightSpace,InvalidUtf8,Dot
+
+
+
+### Limitations ###
+
+Note that Dropbox is case insensitive so you can&#39;t have a file called
+&quot;Hello.doc&quot; and one called &quot;hello.doc&quot;.
+
+There are some file names such as `thumbs.db` which Dropbox can&#39;t
+store.  There is a full list of them in the [&quot;Ignored Files&quot; section
+of this document](https://www.dropbox.com/en/help/145).  Rclone will
+issue an error message `File name disallowed - not uploading` if it
+attempts to upload one of those file names, but the sync won&#39;t fail.
+
+Some errors may occur if you try to sync copyright-protected files
+because Dropbox has its own [copyright detector](https://techcrunch.com/2014/03/30/how-dropbox-knows-when-youre-sharing-copyrighted-stuff-without-actually-looking-at-your-stuff/) that
+prevents this sort of file being downloaded. This will return the error `ERROR :
+/path/to/your/file: Failed to copy: failed to open source object:
+path/restricted_content/.`
+
+If you have more than 10,000 files in a directory then `rclone purge
+dropbox:dir` will return the error `Failed to purge: There are too
+many files involved in this operation`.  As a work-around do an
+`rclone delete dropbox:dir` followed by an `rclone rmdir dropbox:dir`.
+
+### Get your own Dropbox App ID ###
+
+When you use rclone with Dropbox in its default configuration you are using rclone&#39;s App ID. This is shared between all the rclone users.
+
+Here is how to create your own Dropbox App ID for rclone:
+
+1. Log into the [Dropbox App console](https://www.dropbox.com/developers/apps/create) with your Dropbox Account (It need not
+to be the same account as the Dropbox you want to access)
+
+2. Choose an API =&gt; Usually this should be `Dropbox API`
+
+3. Choose the type of access you want to use =&gt; `Full Dropbox` or `App Folder`
+
+4. Name your App. The app name is global, so you can&#39;t use `rclone` for example
+
+5. Click the button `Create App`
+
+5. Fill `Redirect URIs` as `http://localhost:53682/`
+
+6. Find the `App key` and `App secret` Use these values in rclone config to add a new remote or edit an existing remote.
+
+ FTP
+------------------------------
+
+FTP is the File Transfer Protocol. FTP support is provided using the
+[github.com/jlaffaye/ftp](https://godoc.org/github.com/jlaffaye/ftp)
+package.
+
+Paths are specified as `remote:path`. If the path does not begin with
+a `/` it is relative to the home directory of the user.  An empty path
+`remote:` refers to the user&#39;s home directory.
+
+Here is an example of making an FTP configuration.  First run
+
+    rclone config
+
+This will guide you through an interactive setup process. An FTP remote only
+needs a host together with and a username and a password. With anonymous FTP
+server, you will need to use `anonymous` as username and your email address as
+the password.
+</code></pre>
+<p>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 (""). Choose a number from below, or type in your own value [snip] XX / FTP Connection  "ftp" [snip] Storage&gt; ftp ** See help for ftp backend at: https://rclone.org/ftp/ **</p>
+<p>FTP host to connect to Enter a string value. Press Enter for the default (""). Choose a number from below, or type in your own value 1 / Connect to ftp.example.com  "ftp.example.com" host&gt; ftp.example.com FTP username, leave blank for current username, ncw Enter a string value. Press Enter for the default (""). user&gt; FTP port, leave blank to use default (21) Enter a string value. Press Enter for the default (""). 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 ("false"). tls&gt; Use FTP over TLS (Explicit) Enter a boolean value (true or false). Press Enter for the default ("false"). explicit_tls&gt; Remote config -------------------- [remote] type = ftp host = ftp.example.com pass = *** ENCRYPTED *** -------------------- y) Yes this is OK e) Edit this remote d) Delete this remote y/e/d&gt; y</p>
+<pre><code>
+This remote is called `remote` and can now be used like this
+
+See all directories in the home directory
+
+    rclone lsd remote:
+
+Make a new directory
+
+    rclone mkdir remote:path/to/directory
+
+List the contents of a directory
+
+    rclone ls remote:path/to/directory
+
+Sync `/home/local/directory` to the remote directory, deleting any
+excess files in the directory.
+
+    rclone sync -i /home/local/directory remote:directory
+
+### Modified time ###
+
+FTP does not support modified times.  Any times you see on the server
+will be time of upload.
+
+### Checksums ###
+
+FTP does not support any checksums.
+
+### Usage without a config file ###
+
+An example how to use the ftp remote without a config file:
+
+    rclone lsf :ftp: --ftp-host=speedtest.tele2.net --ftp-user=anonymous --ftp-pass=`rclone obscure dummy`
+
+#### Restricted filename characters
+
+In addition to the [default restricted characters set](https://rclone.org/overview/#restricted-characters)
+the following characters are also replaced:
+
+File names can also not end with the following characters.
+These only get replaced if they are the last character in the name:
+
+| Character | Value | Replacement |
+| --------- |:-----:|:-----------:|
+| SP        | 0x20  | ␠           |
+
+Note that not all FTP servers can have all characters in file names, for example:
+
+| FTP Server| Forbidden characters |
+| --------- |:--------------------:|
+| proftpd   | `*`                  |
+| pureftpd  | `\ [ ]`              |
+
+### Implicit TLS ###
+
+FTP supports implicit FTP over TLS servers (FTPS). This has to be enabled
+in the config for the remote. The default FTPS port is `990` so the
+port will likely have to be explicitly set in the config for the remote.
+
+
+### Standard Options
+
+Here are the standard options specific to ftp (FTP Connection).
+
+#### --ftp-host
 
 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, leave blank for current username, ncw
-Enter a string value. Press Enter for the default (&quot;&quot;).
-user&gt; 
-FTP port, leave blank to use default (21)
-Enter a string value. Press Enter for the default (&quot;&quot;).
-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; 
-Remote config
---------------------
-[remote]
-type = ftp
-host = ftp.example.com
-pass = *** ENCRYPTED ***
---------------------
-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 directories in the home directory</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 /home/local/directory remote:directory</code></pre>
-<h3 id="modified-time-3">Modified time</h3>
-<p>FTP does not support modified times. Any times you see on the server will be time of upload.</p>
-<h3 id="checksums">Checksums</h3>
-<p>FTP does not support any checksums.</p>
-<h3 id="usage-without-a-config-file">Usage without a config file</h3>
-<p>An example how to use the ftp remote without a config file:</p>
-<pre><code>rclone lsf :ftp: --ftp-host=speedtest.tele2.net --ftp-user=anonymous --ftp-pass=`rclone obscure dummy`</code></pre>
-<h4 id="restricted-filename-characters-7">Restricted filename characters</h4>
-<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 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>Note that 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>
-<h3 id="implicit-tls">Implicit TLS</h3>
-<p>FTP supports implicit FTP over TLS servers (FTPS). This has to be enabled in the config for the remote. The default FTPS port is <code>990</code> so the port will likely have to be explicitly set in the config for the remote.</p>
-<h3 id="standard-options-11">Standard Options</h3>
-<p>Here are the standard options specific to ftp (FTP Connection).</p>
-<h4 id="ftp-host">–ftp-host</h4>
-<p>FTP host to connect to</p>
-<ul>
-<li>Config: host</li>
-<li>Env Var: RCLONE_FTP_HOST</li>
-<li>Type: string</li>
-<li>Default: ""</li>
-<li>Examples:
-<ul>
-<li>“ftp.example.com”
-<ul>
-<li>Connect to ftp.example.com</li>
-</ul></li>
-</ul></li>
-</ul>
-<h4 id="ftp-user">–ftp-user</h4>
-<p>FTP username, leave blank for current username, $USER</p>
-<ul>
-<li>Config: user</li>
-<li>Env Var: RCLONE_FTP_USER</li>
-<li>Type: string</li>
-<li>Default: ""</li>
-</ul>
-<h4 id="ftp-port">–ftp-port</h4>
-<p>FTP port, leave blank to use default (21)</p>
-<ul>
-<li>Config: port</li>
-<li>Env Var: RCLONE_FTP_PORT</li>
-<li>Type: string</li>
-<li>Default: ""</li>
-</ul>
-<h4 id="ftp-pass">–ftp-pass</h4>
-<p>FTP password</p>
-<ul>
-<li>Config: pass</li>
-<li>Env Var: RCLONE_FTP_PASS</li>
-<li>Type: string</li>
-<li>Default: ""</li>
-</ul>
-<h4 id="ftp-tls">–ftp-tls</h4>
-<p>Use FTP over TLS (Implicit)</p>
-<ul>
-<li>Config: tls</li>
-<li>Env Var: RCLONE_FTP_TLS</li>
-<li>Type: bool</li>
-<li>Default: false</li>
-</ul>
-<h3 id="advanced-options-10">Advanced Options</h3>
-<p>Here are the advanced options specific to ftp (FTP Connection).</p>
-<h4 id="ftp-concurrency">–ftp-concurrency</h4>
-<p>Maximum number of FTP simultaneous connections, 0 for unlimited</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>
-<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>
-<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-encoding">–ftp-encoding</h4>
-<p>This sets 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>
-<ul>
-<li>Config: encoding</li>
-<li>Env Var: RCLONE_FTP_ENCODING</li>
-<li>Type: MultiEncoder</li>
-<li>Default: Slash,Del,Ctl,RightSpace,Dot</li>
-</ul>
-<h3 id="limitations-6">Limitations</h3>
-<p>Note that since FTP isn’t HTTP based the following flags don’t work with it: <code>--dump-headers</code>, <code>--dump-bodies</code>, <code>--dump-auth</code></p>
-<p>Note that <code>--timeout</code> isn’t supported (but <code>--contimeout</code> is).</p>
-<p>Note that <code>--bind</code> isn’t supported.</p>
-<p>FTP could support server side move but doesn’t yet.</p>
-<p>Note that the ftp backend does not support the <code>ftp_proxy</code> environment variable yet.</p>
-<p>Note that while implicit FTP over TLS is supported, explicit FTP over TLS is not.</p>
-<h2 id="google-cloud-storage">Google Cloud Storage</h2>
-<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, eg <code>remote:bucket/path/to/dir</code>.</p>
-<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 auto config?
- * Say Y if not sure
- * Say N if you are working on a remote or headless machine or Y didn&#39;t work
-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
---------------------
-[remote]
-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
---------------------
-y) Yes this is OK
-e) Edit this remote
-d) Delete this remote
-y/e/d&gt; y</code></pre>
-<p>Note that rclone runs a webserver on your local machine to collect the token as returned from Google if you use auto config mode. 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 /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="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-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>
-<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-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="modified-time-4">Modified time</h3>
-<p>Google google cloud storage stores md5sums natively and rclone stores modification times as metadata on the object, under the “mtime” key in RFC3339 format accurate to 1ns.</p>
-<h4 id="restricted-filename-characters-8">Restricted filename characters</h4>
-<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-12">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>Google Application Client Id Leave blank normally.</p>
-<ul>
-<li>Config: client_id</li>
-<li>Env Var: RCLONE_GCS_CLIENT_ID</li>
-<li>Type: string</li>
-<li>Default: ""</li>
-</ul>
-<h4 id="gcs-client-secret">–gcs-client-secret</h4>
-<p>Google Application Client Secret Leave blank normally.</p>
-<ul>
-<li>Config: client_secret</li>
-<li>Env Var: RCLONE_GCS_CLIENT_SECRET</li>
-<li>Type: string</li>
-<li>Default: ""</li>
-</ul>
-<h4 id="gcs-project-number">–gcs-project-number</h4>
-<p>Project number. Optional - needed only for list/create/delete buckets - see your developer console.</p>
-<ul>
-<li>Config: project_number</li>
-<li>Env Var: RCLONE_GCS_PROJECT_NUMBER</li>
-<li>Type: string</li>
-<li>Default: ""</li>
-</ul>
-<h4 id="gcs-service-account-file">–gcs-service-account-file</h4>
-<p>Service Account Credentials JSON file path Leave blank normally. Needed only if you want use SA instead of interactive login.</p>
-<ul>
-<li>Config: service_account_file</li>
-<li>Env Var: RCLONE_GCS_SERVICE_ACCOUNT_FILE</li>
-<li>Type: string</li>
-<li>Default: ""</li>
-</ul>
-<h4 id="gcs-service-account-credentials">–gcs-service-account-credentials</h4>
-<p>Service Account Credentials JSON blob Leave blank normally. Needed only if you want use SA instead of interactive login.</p>
-<ul>
-<li>Config: service_account_credentials</li>
-<li>Env Var: RCLONE_GCS_SERVICE_ACCOUNT_CREDENTIALS</li>
-<li>Type: string</li>
-<li>Default: ""</li>
-</ul>
-<h4 id="gcs-object-acl">–gcs-object-acl</h4>
-<p>Access Control List for new objects.</p>
-<ul>
-<li>Config: object_acl</li>
-<li>Env Var: RCLONE_GCS_OBJECT_ACL</li>
-<li>Type: string</li>
-<li>Default: ""</li>
-<li>Examples:
-<ul>
-<li>“authenticatedRead”
-<ul>
-<li>Object owner gets OWNER access, and all Authenticated Users get READER access.</li>
-</ul></li>
-<li>“bucketOwnerFullControl”
-<ul>
-<li>Object owner gets OWNER access, and project team owners get OWNER access.</li>
-</ul></li>
-<li>“bucketOwnerRead”
-<ul>
-<li>Object owner gets OWNER access, and project team owners get READER access.</li>
-</ul></li>
-<li>“private”
-<ul>
-<li>Object owner gets OWNER access [default if left blank].</li>
-</ul></li>
-<li>“projectPrivate”
-<ul>
-<li>Object owner gets OWNER access, and project team members get access according to their roles.</li>
-</ul></li>
-<li>“publicRead”
-<ul>
-<li>Object owner gets OWNER access, and 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>
-<ul>
-<li>Config: bucket_acl</li>
-<li>Env Var: RCLONE_GCS_BUCKET_ACL</li>
-<li>Type: string</li>
-<li>Default: ""</li>
-<li>Examples:
-<ul>
-<li>“authenticatedRead”
-<ul>
-<li>Project team owners get OWNER access, and all Authenticated Users get READER access.</li>
-</ul></li>
-<li>“private”
-<ul>
-<li>Project team owners get OWNER access [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, and all Users get READER access.</li>
-</ul></li>
-<li>“publicReadWrite”
-<ul>
-<li>Project team owners get OWNER access, and 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>
-<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>
-<ul>
-<li>Config: location</li>
-<li>Env Var: RCLONE_GCS_LOCATION</li>
-<li>Type: string</li>
-<li>Default: ""</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-south1”
-<ul>
-<li>Mumbai.</li>
-</ul></li>
-<li>“asia-southeast1”
-<ul>
-<li>Singapore.</li>
-</ul></li>
-<li>“australia-southeast1”
-<ul>
-<li>Sydney.</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>“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>
-</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>
-<ul>
-<li>Config: storage_class</li>
-<li>Env Var: RCLONE_GCS_STORAGE_CLASS</li>
-<li>Type: string</li>
-<li>Default: ""</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>
-<h3 id="advanced-options-11">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-encoding">–gcs-encoding</h4>
-<p>This sets 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>
-<ul>
-<li>Config: encoding</li>
-<li>Env Var: RCLONE_GCS_ENCODING</li>
-<li>Type: MultiEncoder</li>
-<li>Default: Slash,CrLf,InvalidUtf8,Dot</li>
-</ul>
-<h2 id="google-drive">Google Drive</h2>
-<p>Paths are specified as <code>drive:path</code></p>
-<p>Drive paths may be as deep as required, eg <code>drive:directory/subdirectory</code>.</p>
-<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
-ID of the root folder - leave blank normally.  Fill in to access &quot;Computers&quot; folders. (see docs).
-root_folder_id&gt; 
-Service Account Credentials JSON file path - needed only if you want use SA instead of interactive login.
-service_account_file&gt;
-Remote config
-Use auto config?
- * Say Y if not sure
- * Say N if you are working on a remote or headless machine or Y didn&#39;t work
-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 team drive?
-y) Yes
-n) No
-y/n&gt; n
---------------------
-[remote]
-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;}
---------------------
-y) Yes this is OK
-e) Edit this remote
-d) Delete this remote
-y/e/d&gt; y</code></pre>
-<p>Note that rclone runs a webserver on your local machine to collect the token as returned from Google if you use auto config mode. 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>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>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-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 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-appsg-suite-account-and-individual-drive">Use case - Google Apps/G-suite account and individual Drive</h4>
-<p>Let’s say that you are the administrator of a Google Apps (old) or G-suite account. The goal is to store 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.</li>
-<li>Then go to “IAM &amp; admin” -&gt; “Service Accounts”.</li>
-<li>Use the “Create Credentials” button. Fill in “Service account name” with something that identifies your client. “Role” can be empty.</li>
-<li>Tick “Furnish a new private key” - select “Key type JSON”.</li>
-<li>Tick “Enable G Suite Domain-wide Delegation”. This option makes “impersonation” possible, as documented here: <a href="https://developers.google.com/identity/protocols/OAuth2ServiceAccount#delegatingauthority">Delegating domain-wide authority to the service account</a></li>
-<li>These credentials are what rclone will use for authentication. If you ever need to remove access, press the “Delete service account key” button.</li>
-</ul>
-<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 admin console</li>
-<li>Go into “Security” (or use the search bar)</li>
-<li>Select “Show more” and then “Advanced settings”</li>
-<li>Select “Manage API client access” in the “Authentication” section</li>
-<li>In the “Client Name” 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, “One or More API Scopes”, enter <code>https://www.googleapis.com/auth/drive</code> to grant access to Google Drive specifically.</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;         # Select the number shown for Google Drive
-client_id&gt;       # Can be left blank
-client_secret&gt;   # Can be left blank
-scope&gt;           # Select your scope, 1 for example
-root_folder_id&gt;  # Can be left blank
-service_account_file&gt; /home/foo/myJSONfile.json # This is where the JSON file goes!
-y/n&gt;             # Auto config, y
+- Config:      host
+- Env Var:     RCLONE_FTP_HOST
+- Type:        string
+- Default:     &quot;&quot;
+- Examples:
+    - &quot;ftp.example.com&quot;
+        - Connect to ftp.example.com
+
+#### --ftp-user
+
+FTP username, leave blank for current username, $USER
+
+- Config:      user
+- Env Var:     RCLONE_FTP_USER
+- Type:        string
+- Default:     &quot;&quot;
+
+#### --ftp-port
+
+FTP port, leave blank to use default (21)
+
+- Config:      port
+- Env Var:     RCLONE_FTP_PORT
+- Type:        string
+- Default:     &quot;&quot;
+
+#### --ftp-pass
+
+FTP password
+
+**NB** Input to this must be obscured - see [rclone obscure](https://rclone.org/commands/rclone_obscure/).
+
+- Config:      pass
+- Env Var:     RCLONE_FTP_PASS
+- Type:        string
+- Default:     &quot;&quot;
+
+#### --ftp-tls
+
+Use FTPS over TLS (Implicit)
+When using implicit FTP over TLS the client will connect using TLS
+right from the start, which in turn breaks the compatibility with
+non-TLS-aware servers. This is usually served over port 990 rather
+than port 21. Cannot be used in combination with explicit FTP.
+
+- Config:      tls
+- Env Var:     RCLONE_FTP_TLS
+- Type:        bool
+- Default:     false
+
+#### --ftp-explicit-tls
+
+Use FTP over TLS (Explicit)
+When using explicit FTP over TLS the client explicitly request
+security from the server in order to upgrade a plain text connection
+to an encrypted one. Cannot be used in combination with implicit FTP.
+
+- Config:      explicit_tls
+- Env Var:     RCLONE_FTP_EXPLICIT_TLS
+- Type:        bool
+- Default:     false
+
+### Advanced Options
+
+Here are the advanced options specific to ftp (FTP Connection).
+
+#### --ftp-concurrency
+
+Maximum number of FTP simultaneous connections, 0 for unlimited
+
+- Config:      concurrency
+- Env Var:     RCLONE_FTP_CONCURRENCY
+- Type:        int
+- Default:     0
+
+#### --ftp-no-check-certificate
+
+Do not verify the TLS certificate of the server
+
+- Config:      no_check_certificate
+- Env Var:     RCLONE_FTP_NO_CHECK_CERTIFICATE
+- Type:        bool
+- Default:     false
+
+#### --ftp-disable-epsv
+
+Disable using EPSV even if server advertises support
+
+- Config:      disable_epsv
+- Env Var:     RCLONE_FTP_DISABLE_EPSV
+- Type:        bool
+- Default:     false
+
+#### --ftp-encoding
+
+This sets the encoding for the backend.
+
+See: the [encoding section in the overview](https://rclone.org/overview/#encoding) for more info.
+
+- Config:      encoding
+- Env Var:     RCLONE_FTP_ENCODING
+- Type:        MultiEncoder
+- Default:     Slash,Del,Ctl,RightSpace,Dot
+
+
+
+### Limitations ###
+
+Note that FTP does have its own implementation of : `--dump headers`,
+`--dump bodies`, `--dump auth` for debugging which isn&#39;t the same as
+the HTTP based backends - it has less fine grained control.
+
+Note that `--timeout` isn&#39;t supported (but `--contimeout` is).
+
+Note that `--bind` isn&#39;t supported.
+
+FTP could support server side move but doesn&#39;t yet.
+
+Note that the ftp backend does not support the `ftp_proxy` environment
+variable yet.
+
+ Google Cloud Storage
+-------------------------------------------------
+
+Paths are specified as `remote:bucket` (or `remote:` for the `lsd`
+command.)  You may put subdirectories in too, eg `remote:bucket/path/to/dir`.
+
+The initial setup for google cloud storage involves getting a token from Google Cloud Storage
+which you need to do in your browser.  `rclone config` walks you
+through it.
+
+Here is an example of how to make a remote called `remote`.  First run:
+
+     rclone config
+
+This will guide you through an interactive setup process:
 </code></pre>
-<h5 id="verify-that-its-working">4. Verify that it’s working</h5>
+<ol start="14" type="a">
+<li>New remote</li>
+<li>Delete remote</li>
+<li>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)  "google cloud storage" [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.  "authenticatedRead" 2 / Object owner gets OWNER access, and project team owners get OWNER access.  "bucketOwnerFullControl" 3 / Object owner gets OWNER access, and project team owners get READER access.  "bucketOwnerRead" 4 / Object owner gets OWNER access [default if left blank].  "private" 5 / Object owner gets OWNER access, and project team members get access according to their roles.  "projectPrivate" 6 / Object owner gets OWNER access, and all Users get READER access.  "publicRead" 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.  "authenticatedRead" 2 / Project team owners get OWNER access [default if left blank].  "private" 3 / Project team members get access according to their roles.  "projectPrivate" 4 / Project team owners get OWNER access, and all Users get READER access.  "publicRead" 5 / Project team owners get OWNER access, and all Users get WRITER access.  "publicReadWrite" 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).  "" 2 / Multi-regional location for Asia.  "asia" 3 / Multi-regional location for Europe.  "eu" 4 / Multi-regional location for United States.  "us" 5 / Taiwan.  "asia-east1" 6 / Tokyo.  "asia-northeast1" 7 / Singapore.  "asia-southeast1" 8 / Sydney.  "australia-southeast1" 9 / Belgium.  "europe-west1" 10 / London.  "europe-west2" 11 / Iowa.  "us-central1" 12 / South Carolina.  "us-east1" 13 / Northern Virginia.  "us-east4" 14 / Oregon.  "us-west1" 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  "" 2 / Multi-regional storage class  "MULTI_REGIONAL" 3 / Regional storage class  "REGIONAL" 4 / Nearline storage class  "NEARLINE" 5 / Coldline storage class  "COLDLINE" 6 / Durable reduced availability storage class  "DURABLE_REDUCED_AVAILABILITY" storage_class&gt; 5 Remote config Use auto config?</li>
+</ol>
 <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>
+<li>Say Y if not sure</li>
+<li>Say N if you are working on a remote or headless machine or Y didn't work</li>
 </ul>
-<h3 id="team-drives">Team drives</h3>
-<p>If you want to configure the remote to point to a Google Team Drive then answer <code>y</code> to the question <code>Configure this as a team drive?</code>.</p>
-<p>This will fetch the list of Team Drives from google and allow you to configure which one you want to use. You can also type in a team drive ID if you prefer.</p>
-<p>For example:</p>
-<pre><code>Configure this as a team drive?
-y) Yes
-n) No
-y/n&gt; y
-Fetching team 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 Team Drive ID&gt; 1
---------------------
-[remote]
-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
---------------------
-y) Yes this is OK
-e) Edit this remote
-d) Delete this remote
-y/e/d&gt; y</code></pre>
-<h3 id="fast-list-4">–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="modified-time-5">Modified time</h3>
-<p>Google drive stores modification times accurate to 1 ms.</p>
-<h4 id="restricted-filename-characters-9">Restricted filename characters</h4>
-<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-2">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 (eg the inode in unix terms) so they don’t break if the source is renamed or moved about.</p>
-<p>Be 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.</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>It isn’t currently possible to create shortcuts with rclone.</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>
-<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, eg 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>
+<ol start="25" type="a">
+<li>Yes</li>
+<li>No y/n&gt; y If your browser doesn'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 -------------------- [remote] type = google cloud storage client_id = client_secret = token = {"AccessToken":"xxxx.xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx","RefreshToken":"x/xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx_xxxxxxxxx","Expiry":"2014-07-17T20:49:14.929208288+01:00","Extra":null} project_number = 12345678 object_acl = private bucket_acl = private --------------------</li>
+<li>Yes this is OK</li>
+<li>Edit this remote</li>
+<li>Delete this remote y/e/d&gt; y</li>
+</ol>
+<pre><code>
+Note that rclone runs a webserver on your local machine to collect the
+token as returned from Google if you use auto config mode. This only
+runs from the moment it opens your browser to the moment you get back
+the verification code.  This is on `http://127.0.0.1:53682/` and this
+it may require you to unblock it temporarily if you are running a host
+firewall, or use manual mode.
+
+This remote is called `remote` and can now be used like this
+
+See all the buckets in your project
+
+    rclone lsd remote:
+
+Make a new bucket
+
+    rclone mkdir remote:bucket
+
+List the contents of a bucket
+
+    rclone ls remote:bucket
+
+Sync `/home/local/directory` to the remote bucket, deleting any excess
+files in the bucket.
+
+    rclone sync -i /home/local/directory remote:bucket
+
+### Service Account support ###
+
+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&#39;t have
+actively logged-in users, for example build machines.
+
+To get credentials for Google Cloud Platform
+[IAM Service Accounts](https://cloud.google.com/iam/docs/service-accounts),
+please head to the
+[Service Account](https://console.cloud.google.com/permissions/serviceaccounts)
+section of the Google Developer Console. Service Accounts behave just
+like normal `User` permissions in
+[Google Cloud Storage ACLs](https://cloud.google.com/storage/docs/access-control),
+so you can limit their access (e.g. make them read only). After
+creating an account, a JSON file containing the Service Account&#39;s
+credentials will be downloaded onto your machines. These credentials
+are what rclone will use for authentication.
+
+To use a Service Account instead of OAuth2 token flow, enter the path
+to your Service Account credentials at the `service_account_file`
+prompt and rclone won&#39;t use the browser based authentication
+flow. If you&#39;d rather stuff the contents of the credentials file into
+the rclone config file, you can set `service_account_credentials` with
+the actual contents of the file instead, or set the equivalent
+environment variable.
+
+### Anonymous Access ###
+
+For downloads of objects that permit public access you can configure rclone
+to use anonymous access by setting `anonymous` to `true`.
+With unauthorized access you can&#39;t write or create files but only read or list
+those buckets and objects that have public read access.
+
+### Application Default Credentials ###
+
+If no other source of credentials is provided, rclone will fall back
+to
+[Application Default Credentials](https://cloud.google.com/video-intelligence/docs/common/auth#authenticating_with_application_default_credentials)
+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 -
+[see this page](https://cloud.google.com/container-registry/docs/advanced-authentication#gcloud_as_a_docker_credential_helper).
+
+Note that in the case application default credentials are used, there
+is no need to explicitly configure a project number.
+
+### --fast-list ###
+
+This remote supports `--fast-list` which allows you to use fewer
+transactions in exchange for more memory. See the [rclone
+docs](https://rclone.org/docs/#fast-list) for more details.
+
+### Custom upload headers ###
+
+You can set custom upload headers with the `--header-upload`
+flag. Google Cloud Storage supports the headers as described in the
+[working with metadata documentation](https://cloud.google.com/storage/docs/gsutil/addlhelp/WorkingWithObjectMetadata)
+
+- Cache-Control
+- Content-Disposition
+- Content-Encoding
+- Content-Language
+- Content-Type
+- X-Goog-Meta-
+
+Eg `--header-upload &quot;Content-Type text/potato&quot;`
+
+Note that the last of these is for setting custom metadata in the form
+`--header-upload &quot;x-goog-meta-key: value&quot;`
+
+### Modified time ###
+
+Google google cloud storage stores md5sums natively and rclone stores
+modification times as metadata on the object, under the &quot;mtime&quot; key in
+RFC3339 format accurate to 1ns.
+
+#### Restricted filename characters
+
+| Character | Value | Replacement |
+| --------- |:-----:|:-----------:|
+| NUL       | 0x00  | ␀           |
+| LF        | 0x0A  | ␊           |
+| CR        | 0x0D  | ␍           |
+| /         | 0x2F  | ／          |
+
+Invalid UTF-8 bytes will also be [replaced](https://rclone.org/overview/#invalid-utf8),
+as they can&#39;t be used in JSON strings.
+
+
+### Standard Options
+
+Here are the standard options specific to google cloud storage (Google Cloud Storage (this is not Google Drive)).
+
+#### --gcs-client-id
+
+OAuth Client Id
+Leave blank normally.
+
+- Config:      client_id
+- Env Var:     RCLONE_GCS_CLIENT_ID
+- Type:        string
+- Default:     &quot;&quot;
+
+#### --gcs-client-secret
+
+OAuth Client Secret
+Leave blank normally.
+
+- Config:      client_secret
+- Env Var:     RCLONE_GCS_CLIENT_SECRET
+- Type:        string
+- Default:     &quot;&quot;
+
+#### --gcs-project-number
+
+Project number.
+Optional - needed only for list/create/delete buckets - see your developer console.
+
+- Config:      project_number
+- Env Var:     RCLONE_GCS_PROJECT_NUMBER
+- Type:        string
+- Default:     &quot;&quot;
+
+#### --gcs-service-account-file
+
+Service Account Credentials JSON file path
+Leave blank normally.
+Needed only if you want use SA instead of interactive login.
+
+Leading `~` will be expanded in the file name as will environment variables such as `${RCLONE_CONFIG_DIR}`.
+
+
+- Config:      service_account_file
+- Env Var:     RCLONE_GCS_SERVICE_ACCOUNT_FILE
+- Type:        string
+- Default:     &quot;&quot;
+
+#### --gcs-service-account-credentials
+
+Service Account Credentials JSON blob
+Leave blank normally.
+Needed only if you want use SA instead of interactive login.
+
+- Config:      service_account_credentials
+- Env Var:     RCLONE_GCS_SERVICE_ACCOUNT_CREDENTIALS
+- Type:        string
+- Default:     &quot;&quot;
+
+#### --gcs-anonymous
+
+Access public buckets and objects without credentials
+Set to &#39;true&#39; if you just want to download files and don&#39;t configure credentials.
+
+- Config:      anonymous
+- Env Var:     RCLONE_GCS_ANONYMOUS
+- Type:        bool
+- Default:     false
+
+#### --gcs-object-acl
+
+Access Control List for new objects.
+
+- Config:      object_acl
+- Env Var:     RCLONE_GCS_OBJECT_ACL
+- Type:        string
+- Default:     &quot;&quot;
+- Examples:
+    - &quot;authenticatedRead&quot;
+        - Object owner gets OWNER access, and all Authenticated Users get READER access.
+    - &quot;bucketOwnerFullControl&quot;
+        - Object owner gets OWNER access, and project team owners get OWNER access.
+    - &quot;bucketOwnerRead&quot;
+        - Object owner gets OWNER access, and project team owners get READER access.
+    - &quot;private&quot;
+        - Object owner gets OWNER access [default if left blank].
+    - &quot;projectPrivate&quot;
+        - Object owner gets OWNER access, and project team members get access according to their roles.
+    - &quot;publicRead&quot;
+        - Object owner gets OWNER access, and all Users get READER access.
+
+#### --gcs-bucket-acl
+
+Access Control List for new buckets.
+
+- Config:      bucket_acl
+- Env Var:     RCLONE_GCS_BUCKET_ACL
+- Type:        string
+- Default:     &quot;&quot;
+- Examples:
+    - &quot;authenticatedRead&quot;
+        - Project team owners get OWNER access, and all Authenticated Users get READER access.
+    - &quot;private&quot;
+        - Project team owners get OWNER access [default if left blank].
+    - &quot;projectPrivate&quot;
+        - Project team members get access according to their roles.
+    - &quot;publicRead&quot;
+        - Project team owners get OWNER access, and all Users get READER access.
+    - &quot;publicReadWrite&quot;
+        - Project team owners get OWNER access, and all Users get WRITER access.
+
+#### --gcs-bucket-policy-only
+
+Access checks should use bucket-level IAM policies.
+
+If you want to upload objects to a bucket with Bucket Policy Only set
+then you will need to set this.
+
+When it is set, rclone:
+
+- ignores ACLs set on buckets
+- ignores ACLs set on objects
+- creates buckets with Bucket Policy Only set
+
+Docs: https://cloud.google.com/storage/docs/bucket-policy-only
+
+
+- Config:      bucket_policy_only
+- Env Var:     RCLONE_GCS_BUCKET_POLICY_ONLY
+- Type:        bool
+- Default:     false
+
+#### --gcs-location
+
+Location for the newly created buckets.
+
+- Config:      location
+- Env Var:     RCLONE_GCS_LOCATION
+- Type:        string
+- Default:     &quot;&quot;
+- Examples:
+    - &quot;&quot;
+        - Empty for default location (US).
+    - &quot;asia&quot;
+        - Multi-regional location for Asia.
+    - &quot;eu&quot;
+        - Multi-regional location for Europe.
+    - &quot;us&quot;
+        - Multi-regional location for United States.
+    - &quot;asia-east1&quot;
+        - Taiwan.
+    - &quot;asia-east2&quot;
+        - Hong Kong.
+    - &quot;asia-northeast1&quot;
+        - Tokyo.
+    - &quot;asia-south1&quot;
+        - Mumbai.
+    - &quot;asia-southeast1&quot;
+        - Singapore.
+    - &quot;australia-southeast1&quot;
+        - Sydney.
+    - &quot;europe-north1&quot;
+        - Finland.
+    - &quot;europe-west1&quot;
+        - Belgium.
+    - &quot;europe-west2&quot;
+        - London.
+    - &quot;europe-west3&quot;
+        - Frankfurt.
+    - &quot;europe-west4&quot;
+        - Netherlands.
+    - &quot;us-central1&quot;
+        - Iowa.
+    - &quot;us-east1&quot;
+        - South Carolina.
+    - &quot;us-east4&quot;
+        - Northern Virginia.
+    - &quot;us-west1&quot;
+        - Oregon.
+    - &quot;us-west2&quot;
+        - California.
+
+#### --gcs-storage-class
+
+The storage class to use when storing objects in Google Cloud Storage.
+
+- Config:      storage_class
+- Env Var:     RCLONE_GCS_STORAGE_CLASS
+- Type:        string
+- Default:     &quot;&quot;
+- Examples:
+    - &quot;&quot;
+        - Default
+    - &quot;MULTI_REGIONAL&quot;
+        - Multi-regional storage class
+    - &quot;REGIONAL&quot;
+        - Regional storage class
+    - &quot;NEARLINE&quot;
+        - Nearline storage class
+    - &quot;COLDLINE&quot;
+        - Coldline storage class
+    - &quot;ARCHIVE&quot;
+        - Archive storage class
+    - &quot;DURABLE_REDUCED_AVAILABILITY&quot;
+        - Durable reduced availability storage class
+
+### Advanced Options
+
+Here are the advanced options specific to google cloud storage (Google Cloud Storage (this is not Google Drive)).
+
+#### --gcs-token
+
+OAuth Access Token as a JSON blob.
+
+- Config:      token
+- Env Var:     RCLONE_GCS_TOKEN
+- Type:        string
+- Default:     &quot;&quot;
+
+#### --gcs-auth-url
+
+Auth server URL.
+Leave blank to use the provider defaults.
+
+- Config:      auth_url
+- Env Var:     RCLONE_GCS_AUTH_URL
+- Type:        string
+- Default:     &quot;&quot;
+
+#### --gcs-token-url
+
+Token server url.
+Leave blank to use the provider defaults.
+
+- Config:      token_url
+- Env Var:     RCLONE_GCS_TOKEN_URL
+- Type:        string
+- Default:     &quot;&quot;
+
+#### --gcs-encoding
+
+This sets the encoding for the backend.
+
+See: the [encoding section in the overview](https://rclone.org/overview/#encoding) for more info.
+
+- Config:      encoding
+- Env Var:     RCLONE_GCS_ENCODING
+- Type:        MultiEncoder
+- Default:     Slash,CrLf,InvalidUtf8,Dot
+
+
+
+ Google Drive
+-----------------------------------------
+
+Paths are specified as `drive:path`
+
+Drive paths may be as deep as required, eg `drive:directory/subdirectory`.
+
+The initial setup for drive involves getting a token from Google drive
+which you need to do in your browser.  `rclone config` walks you
+through it.
+
+Here is an example of how to make a remote called `remote`.  First run:
+
+     rclone config
+
+This will guide you through an interactive setup process:
+</code></pre>
+<p>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  "drive" [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.  "drive" 2 / Read-only access to file metadata and file contents.  "drive.readonly" / 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.  "drive.file" / Allows read and write access to the Application Data folder. 4 | This is not visible in the drive website.  "drive.appfolder" / Allows read-only access to file metadata but 5 | does not allow any access to read or download file content.  "drive.metadata.readonly" scope&gt; 1 ID of the root folder - leave blank normally. Fill in to access "Computers" folders. (see docs). root_folder_id&gt; Service Account Credentials JSON file path - needed only if you want use SA instead of interactive login. service_account_file&gt; Remote config Use auto config? * Say Y if not sure * Say N if you are working on a remote or headless machine or Y didn't work y) Yes n) No y/n&gt; y If your browser doesn'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 team drive? y) Yes n) No y/n&gt; n -------------------- [remote] client_id = client_secret = scope = drive root_folder_id = service_account_file = token = {"access_token":"XXX","token_type":"Bearer","refresh_token":"XXX","expiry":"2014-03-16T13:57:58.955387075Z"} -------------------- y) Yes this is OK e) Edit this remote d) Delete this remote y/e/d&gt; y</p>
+<pre><code>
+Note that rclone runs a webserver on your local machine to collect the
+token as returned from Google if you use auto config mode. This only
+runs from the moment it opens your browser to the moment you get back
+the verification code.  This is on `http://127.0.0.1:53682/` and this
+it may require you to unblock it temporarily if you are running a host
+firewall, or use manual mode.
+
+You can then use it like this,
+
+List directories in top level of your drive
+
+    rclone lsd remote:
+
+List all the files in your drive
+
+    rclone ls remote:
+
+To copy a local directory to a drive directory called backup
+
+    rclone copy /home/source remote:backup
+
+### Scopes ###
+
+Rclone allows you to select which scope you would like for rclone to
+use.  This changes what type of token is granted to rclone.  [The
+scopes are defined
+here](https://developers.google.com/drive/v3/web/about-auth).
+
+The scope are
+
+#### drive ####
+
+This is the default scope and allows full access to all files, except
+for the Application Data Folder (see below).
+
+Choose this one if you aren&#39;t sure.
+
+#### drive.readonly ####
+
+This allows read only access to all files.  Files may be listed and
+downloaded but not uploaded, renamed or deleted.
+
+#### drive.file ####
+
+With this scope rclone can read/view/modify only those files and
+folders it creates.
+
+So if you uploaded files to drive via the web interface (or any other
+means) they will not be visible to rclone.
+
+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.
+
+Files created with this scope are visible in the web interface.
+
+#### drive.appfolder ####
+
+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&#39;t be able
+to see rclone&#39;s files from the web interface either.
+
+#### drive.metadata.readonly ####
+
+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.
+
+### Root folder ID ###
+
+You can set the `root_folder_id` for rclone.  This is the directory
+(identified by its `Folder ID`) that rclone considers to be the root
+of your drive.
+
+Normally you will leave this blank and rclone will determine the
+correct root to use itself.
+
+However you can set this to restrict rclone to a specific folder
+hierarchy or to access data within the &quot;Computers&quot; tab on the drive
+web interface (where files from Google&#39;s Backup and Sync desktop
+program go).
+
+In order to do this you will have to find the `Folder ID` 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.
+
+So if the folder you want rclone to use has a URL which looks like
+`https://drive.google.com/drive/folders/1XyfxxxxxxxxxxxxxxxxxxxxxxxxxKHCh`
+in the browser, then you use `1XyfxxxxxxxxxxxxxxxxxxxxxxxxxKHCh` as
+the `root_folder_id` in the config.
+
+**NB** folders under the &quot;Computers&quot; tab seem to be read only (drive
+gives a 500 error) when using rclone.
+
+There doesn&#39;t appear to be an API to discover the folder IDs of the
+&quot;Computers&quot; tab - please contact us if you know otherwise!
+
+Note also that rclone can&#39;t access any data under the &quot;Backups&quot; tab on
+the google drive web interface yet.
+
+### Service Account support ###
+
+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&#39;t have
+actively logged-in users, for example build machines.
+
+To use a Service Account instead of OAuth2 token flow, enter the path
+to your Service Account credentials at the `service_account_file`
+prompt during `rclone config` and rclone won&#39;t use the browser based
+authentication flow. If you&#39;d rather stuff the contents of the
+credentials file into the rclone config file, you can set
+`service_account_credentials` with the actual contents of the file
+instead, or set the equivalent environment variable.
+
+#### Use case - Google Apps/G-suite account and individual Drive ####
+
+Let&#39;s say that you are the administrator of a Google Apps (old) or
+G-suite account.
+The goal is to store data on an individual&#39;s Drive account, who IS
+a member of the domain.
+We&#39;ll call the domain **example.com**, and the user
+**foo@example.com**.
+
+There&#39;s a few steps we need to go through to accomplish this:
+
+##### 1. Create a service account for example.com #####
+  - To create a service account and obtain its credentials, go to the
+[Google Developer Console](https://console.developers.google.com).
+  - You must have a project - create one if you don&#39;t.
+  - Then go to &quot;IAM &amp; admin&quot; -&gt; &quot;Service Accounts&quot;.
+  - Use the &quot;Create Credentials&quot; button. Fill in &quot;Service account name&quot;
+with something that identifies your client. &quot;Role&quot; can be empty.
+  - Tick &quot;Furnish a new private key&quot; - select &quot;Key type JSON&quot;.
+  - Tick &quot;Enable G Suite Domain-wide Delegation&quot;. This option makes
+&quot;impersonation&quot; possible, as documented here:
+[Delegating domain-wide authority to the service account](https://developers.google.com/identity/protocols/OAuth2ServiceAccount#delegatingauthority)
+  - These credentials are what rclone will use for authentication.
+If you ever need to remove access, press the &quot;Delete service
+account key&quot; button.
+
+##### 2. Allowing API access to example.com Google Drive #####
+  - Go to example.com&#39;s admin console
+  - Go into &quot;Security&quot; (or use the search bar)
+  - Select &quot;Show more&quot; and then &quot;Advanced settings&quot;
+  - Select &quot;Manage API client access&quot; in the &quot;Authentication&quot; section
+  - In the &quot;Client Name&quot; field enter the service account&#39;s
+&quot;Client ID&quot; - this can be found in the Developer Console under
+&quot;IAM &amp; Admin&quot; -&gt; &quot;Service Accounts&quot;, then &quot;View Client ID&quot; for
+the newly created service account.
+It is a ~21 character numerical string.
+  - In the next field, &quot;One or More API Scopes&quot;, enter
+`https://www.googleapis.com/auth/drive`
+to grant access to Google Drive specifically.
+
+##### 3. Configure rclone, assuming a new install #####
+</code></pre>
+<p>rclone config</p>
+<p>n/s/q&gt; n # New name&gt;gdrive # Gdrive is an example name Storage&gt; # Select the number shown for Google Drive client_id&gt; # Can be left blank client_secret&gt; # Can be left blank scope&gt; # Select your scope, 1 for example root_folder_id&gt; # Can be left blank service_account_file&gt; /home/foo/myJSONfile.json # This is where the JSON file goes! y/n&gt; # Auto config, y</p>
+<pre><code>
+##### 4. Verify that it&#39;s working #####
+  - `rclone -v --drive-impersonate foo@example.com lsf gdrive:backup`
+  - The arguments do:
+    - `-v` - verbose logging
+    - `--drive-impersonate foo@example.com` - this is what does
+the magic, pretending to be user foo.
+    - `lsf` - list files in a parsing friendly way
+    - `gdrive:backup` - use the remote called gdrive, work in
+the folder named backup.
+
+Note: in case you configured a specific root folder on gdrive and rclone is unable to access the contents of that folder when using `--drive-impersonate`, 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 `--drive-impersonate` option, like this:
+        `rclone -v foo@example.com lsf gdrive:backup`
+
+
+### Team drives ###
+
+If you want to configure the remote to point to a Google Team Drive
+then answer `y` to the question `Configure this as a team drive?`.
+
+This will fetch the list of Team Drives from google and allow you to
+configure which one you want to use.  You can also type in a team
+drive ID if you prefer.
+
+For example:
+</code></pre>
+<p>Configure this as a team drive? y) Yes n) No y/n&gt; y Fetching team drive list... Choose a number from below, or type in your own value 1 / Rclone Test  "xxxxxxxxxxxxxxxxxxxx" 2 / Rclone Test 2  "yyyyyyyyyyyyyyyyyyyy" 3 / Rclone Test 3  "zzzzzzzzzzzzzzzzzzzz" Enter a Team Drive ID&gt; 1 -------------------- [remote] client_id = client_secret = token = {"AccessToken":"xxxx.x.xxxxx_xxxxxxxxxxx_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx","RefreshToken":"1/xxxxxxxxxxxxxxxx_xxxxxxxxxxxxxxxxxxxxxxxxxx","Expiry":"2014-03-16T13:57:58.955387075Z","Extra":null} team_drive = xxxxxxxxxxxxxxxxxxxx -------------------- y) Yes this is OK e) Edit this remote d) Delete this remote y/e/d&gt; y</p>
+<pre><code>
+### --fast-list ###
+
+This remote supports `--fast-list` which allows you to use fewer
+transactions in exchange for more memory. See the [rclone
+docs](https://rclone.org/docs/#fast-list) for more details.
+
+It does this by combining multiple `list` calls into a single API request.
+
+This works by combining many `&#39;%s&#39; in parents` filters into one expression.
+To list the contents of directories a, b and c, the following requests will be send by the regular `List` function:</code></pre>
+<p>trashed=false and 'a' in parents trashed=false and 'b' in parents trashed=false and 'c' in parents</p>
+<pre><code>These can now be combined into a single request:</code></pre>
+<p>trashed=false and ('a' in parents or 'b' in parents or 'c' in parents)</p>
+<pre><code>
+The implementation of `ListR` will put up to 50 `parents` filters into one request.
+It will  use the `--checkers` value to specify the number of requests to run in parallel.
+
+In tests, these batch requests were up to 20x faster than the regular method.
+Running the following command against different sized folders gives:</code></pre>
+<p>rclone lsjson -vv -R --checkers=6 gdrive:folder</p>
+<pre><code>
+small folder (220 directories, 700 files):
+
+- without `--fast-list`: 38s
+- with `--fast-list`: 10s
+
+large folder (10600 directories, 39000 files):
+
+- without `--fast-list`: 22:05 min
+- with `--fast-list`: 58s
+
+### Modified time ###
+
+Google drive stores modification times accurate to 1 ms.
+
+#### Restricted filename characters
+
+Only Invalid UTF-8 bytes will be [replaced](https://rclone.org/overview/#invalid-utf8),
+as they can&#39;t be used in JSON strings.
+
+In contrast to other backends, `/` can also be used in names and `.`
+or `..` are valid names.
+
+### Revisions ###
+
+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.
+
+Revisions follow the standard google policy which at time of writing
+was
+
+  * They are deleted after 30 days or 100 revisions (whatever comes first).
+  * They do not count towards a user storage quota.
+
+### Deleting files ###
+
+By default rclone will send all files to the trash when deleting
+files.  If deleting them permanently is required then use the
+`--drive-use-trash=false` flag, or set the equivalent environment
+variable.
+
+### Shortcuts ###
+
+In March 2020 Google introduced a new feature in Google Drive called
+[drive shortcuts](https://support.google.com/drive/answer/9700156)
+([API](https://developers.google.com/drive/api/v3/shortcuts)). These
+will (by September 2020) [replace the ability for files or folders to
+be in multiple folders at once](https://cloud.google.com/blog/products/g-suite/simplifying-google-drives-folder-structure-and-sharing-models).
+
+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
+(eg the inode in unix terms) so they don&#39;t break if the source is
+renamed or moved about.
+
+Be default rclone treats these as follows.
+
+For shortcuts pointing to files:
+
+- When listing a file shortcut appears as the destination file.
+- When downloading the contents of the destination file is downloaded.
+- When updating shortcut file with a non shortcut file, the shortcut is removed then a new file is uploaded in place of the shortcut.
+- When server side moving (renaming) the shortcut is renamed, not the destination file.
+- When server side copying the shortcut is copied, not the contents of the shortcut.
+- When deleting the shortcut is deleted not the linked file.
+- When setting the modification time, the modification time of the linked file will be set.
+
+For shortcuts pointing to folders:
+
+- When listing the shortcut appears as a folder and that folder will contain the contents of the linked folder appear (including any sub folders)
+- When downloading the contents of the linked folder and sub contents are downloaded
+- When uploading to a shortcut folder the file will be placed in the linked folder
+- When server side moving (renaming) the shortcut is renamed, not the destination folder
+- When server side copying the contents of the linked folder is copied, not the shortcut.
+- When deleting with `rclone rmdir` or `rclone purge` the shortcut is deleted not the linked folder.
+- **NB** When deleting with `rclone remove` or `rclone mount` the contents of the linked folder will be deleted.
+
+The [rclone backend](https://rclone.org/commands/rclone_backend/) command can be used to create shortcuts.  
+
+Shortcuts can be completely ignored with the `--drive-skip-shortcuts` flag
+or the corresponding `skip_shortcuts` configuration setting.
+
+### Emptying trash ###
+
+If you wish to empty your trash you can use the `rclone cleanup remote:`
+command which will permanently delete all your trashed files. This command
+does not take any path arguments.
+
+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.
+
+### Quota information ###
+
+To view your current quota you can use the `rclone about remote:`
+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.
+
+#### Import/Export of google documents ####
+
+Google documents can be exported from and uploaded to Google Drive.
+
+When rclone downloads a Google doc it chooses a format to download
+depending upon the `--drive-export-formats` setting.
+By default the export formats are `docx,xlsx,pptx,svg` which are a
+sensible default for an editable document.
+
+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&#39;t be exported to a format on the formats list,
+then rclone will choose a format from the default list.
+
+If you prefer an archive copy then you might use `--drive-export-formats
+pdf`, or if you prefer openoffice/libreoffice formats you might use
+`--drive-export-formats ods,odt,odp`.
+
+Note that rclone adds the extension to the google doc, so if it is
+called `My Spreadsheet` on google docs, it will be exported as `My
+Spreadsheet.xlsx` or `My Spreadsheet.pdf` etc.
+
+When importing files into Google Drive, rclone will convert all
+files with an extension in `--drive-import-formats` to their
+associated document type.
+rclone will not convert any files by default, since the conversion
+is lossy process.
+
+The conversion must result in a file with the same extension when
+the `--drive-export-formats` rules are applied to the uploaded document.
+
+Here are some examples for allowed and prohibited conversions.
+
+| export-formats | import-formats | Upload Ext | Document Ext | Allowed |
+| -------------- | -------------- | ---------- | ------------ | ------- |
+| odt | odt | odt | odt | Yes |
+| odt | docx,odt | odt | odt | Yes |
+|  | docx | docx | docx | Yes |
+|  | odt | odt | docx | No |
+| odt,docx | docx,odt | docx | odt | No |
+| docx,odt | docx,odt | docx | docx | Yes |
+| docx,odt | docx,odt | odt | docx | No |
+
+This limitation can be disabled by specifying `--drive-allow-import-name-change`.
+When using this flag, rclone can convert multiple files types resulting
+in the same document type at once, eg with `--drive-import-formats docx,odt,txt`,
+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. 
+
+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.
+
+This list can be changed by Google Drive at any time and might not
+represent the currently available conversions.
+
+| Extension | Mime Type | Description |
+| --------- |-----------| ------------|
+| csv  | text/csv | Standard CSV format for Spreadsheets |
+| docx | application/vnd.openxmlformats-officedocument.wordprocessingml.document | Microsoft Office Document |
+| epub | application/epub+zip | E-book format |
+| html | text/html | An HTML Document |
+| jpg  | image/jpeg | A JPEG Image File |
+| json | application/vnd.google-apps.script+json | JSON Text Format |
+| odp  | application/vnd.oasis.opendocument.presentation | Openoffice Presentation |
+| ods  | application/vnd.oasis.opendocument.spreadsheet | Openoffice Spreadsheet |
+| ods  | application/x-vnd.oasis.opendocument.spreadsheet | Openoffice Spreadsheet |
+| odt  | application/vnd.oasis.opendocument.text | Openoffice Document |
+| pdf  | application/pdf | Adobe PDF Format |
+| png  | image/png | PNG Image Format|
+| pptx | application/vnd.openxmlformats-officedocument.presentationml.presentation | Microsoft Office Powerpoint |
+| rtf  | application/rtf | Rich Text Format |
+| svg  | image/svg+xml | Scalable Vector Graphics Format |
+| tsv  | text/tab-separated-values | Standard TSV format for spreadsheets |
+| txt  | text/plain | Plain Text |
+| xlsx | application/vnd.openxmlformats-officedocument.spreadsheetml.sheet | Microsoft Office Spreadsheet |
+| zip  | application/zip | A ZIP file of HTML, Images CSS |
+
+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
+`--drive-export-formats` parameter. They will match all available
+Google Documents.
+
+| Extension | Description | OS Support |
+| --------- | ----------- | ---------- |
+| desktop | freedesktop.org specified desktop entry | Linux |
+| link.html | An HTML Document with a redirect | All |
+| url | INI style link file | macOS, Windows |
+| webloc | macOS specific XML format | macOS |
+
+
+### Standard Options
+
+Here are the standard options specific to drive (Google Drive).
+
+#### --drive-client-id
+
+OAuth Client Id
+Leave blank normally.
+
+- Config:      client_id
+- Env Var:     RCLONE_DRIVE_CLIENT_ID
+- Type:        string
+- Default:     &quot;&quot;
+
+#### --drive-client-secret
+
+OAuth Client Secret
+Leave blank normally.
+
+- Config:      client_secret
+- Env Var:     RCLONE_DRIVE_CLIENT_SECRET
+- Type:        string
+- Default:     &quot;&quot;
+
+#### --drive-scope
+
+Scope that rclone should use when requesting access from drive.
+
+- Config:      scope
+- Env Var:     RCLONE_DRIVE_SCOPE
+- Type:        string
+- Default:     &quot;&quot;
+- Examples:
+    - &quot;drive&quot;
+        - Full access all files, excluding Application Data Folder.
+    - &quot;drive.readonly&quot;
+        - Read-only access to file metadata and file contents.
+    - &quot;drive.file&quot;
+        - Access to files created by rclone only.
+        - These are visible in the drive website.
+        - File authorization is revoked when the user deauthorizes the app.
+    - &quot;drive.appfolder&quot;
+        - Allows read and write access to the Application Data folder.
+        - This is not visible in the drive website.
+    - &quot;drive.metadata.readonly&quot;
+        - Allows read-only access to file metadata but
+        - does not allow any access to read or download file content.
+
+#### --drive-root-folder-id
+
+ID of the root folder
+Leave blank normally.
+
+Fill in to access &quot;Computers&quot; folders (see docs), or for rclone to use
+a non root folder as its starting point.
+
+
+- Config:      root_folder_id
+- Env Var:     RCLONE_DRIVE_ROOT_FOLDER_ID
+- Type:        string
+- Default:     &quot;&quot;
+
+#### --drive-service-account-file
+
+Service Account Credentials JSON file path 
+Leave blank normally.
+Needed only if you want use SA instead of interactive login.
+
+Leading `~` will be expanded in the file name as will environment variables such as `${RCLONE_CONFIG_DIR}`.
+
+
+- Config:      service_account_file
+- Env Var:     RCLONE_DRIVE_SERVICE_ACCOUNT_FILE
+- Type:        string
+- Default:     &quot;&quot;
+
+#### --drive-alternate-export
+
+Deprecated: no longer needed
+
+- Config:      alternate_export
+- Env Var:     RCLONE_DRIVE_ALTERNATE_EXPORT
+- Type:        bool
+- Default:     false
+
+### Advanced Options
+
+Here are the advanced options specific to drive (Google Drive).
+
+#### --drive-token
+
+OAuth Access Token as a JSON blob.
+
+- Config:      token
+- Env Var:     RCLONE_DRIVE_TOKEN
+- Type:        string
+- Default:     &quot;&quot;
+
+#### --drive-auth-url
+
+Auth server URL.
+Leave blank to use the provider defaults.
+
+- Config:      auth_url
+- Env Var:     RCLONE_DRIVE_AUTH_URL
+- Type:        string
+- Default:     &quot;&quot;
+
+#### --drive-token-url
+
+Token server url.
+Leave blank to use the provider defaults.
+
+- Config:      token_url
+- Env Var:     RCLONE_DRIVE_TOKEN_URL
+- Type:        string
+- Default:     &quot;&quot;
+
+#### --drive-service-account-credentials
+
+Service Account Credentials JSON blob
+Leave blank normally.
+Needed only if you want use SA instead of interactive login.
+
+- Config:      service_account_credentials
+- Env Var:     RCLONE_DRIVE_SERVICE_ACCOUNT_CREDENTIALS
+- Type:        string
+- Default:     &quot;&quot;
+
+#### --drive-team-drive
+
+ID of the Team Drive
+
+- Config:      team_drive
+- Env Var:     RCLONE_DRIVE_TEAM_DRIVE
+- Type:        string
+- Default:     &quot;&quot;
+
+#### --drive-auth-owner-only
+
+Only consider files owned by the authenticated user.
+
+- Config:      auth_owner_only
+- Env Var:     RCLONE_DRIVE_AUTH_OWNER_ONLY
+- Type:        bool
+- Default:     false
+
+#### --drive-use-trash
+
+Send files to the trash instead of deleting permanently.
+Defaults to true, namely sending files to the trash.
+Use `--drive-use-trash=false` to delete files permanently instead.
+
+- Config:      use_trash
+- Env Var:     RCLONE_DRIVE_USE_TRASH
+- Type:        bool
+- Default:     true
+
+#### --drive-skip-gdocs
+
+Skip google documents in all listings.
+If given, gdocs practically become invisible to rclone.
+
+- Config:      skip_gdocs
+- Env Var:     RCLONE_DRIVE_SKIP_GDOCS
+- Type:        bool
+- Default:     false
+
+#### --drive-skip-checksum-gphotos
+
+Skip MD5 checksum on Google photos and videos only.
+
+Use this if you get checksum errors when transferring Google photos or
+videos.
+
+Setting this flag will cause Google photos and videos to return a
+blank MD5 checksum.
+
+Google photos are identified by being in the &quot;photos&quot; space.
+
+Corrupted checksums are caused by Google modifying the image/video but
+not updating the checksum.
+
+- Config:      skip_checksum_gphotos
+- Env Var:     RCLONE_DRIVE_SKIP_CHECKSUM_GPHOTOS
+- Type:        bool
+- Default:     false
+
+#### --drive-shared-with-me
+
+Only show files that are shared with me.
+
+Instructs rclone to operate on your &quot;Shared with me&quot; folder (where
+Google Drive lets you access the files and folders others have shared
+with you).
+
+This works both with the &quot;list&quot; (lsd, lsl, etc) and the &quot;copy&quot;
+commands (copy, sync, etc), and with all other commands too.
+
+- Config:      shared_with_me
+- Env Var:     RCLONE_DRIVE_SHARED_WITH_ME
+- Type:        bool
+- Default:     false
+
+#### --drive-trashed-only
+
+Only show files that are in the trash.
+This will show trashed files in their original directory structure.
+
+- Config:      trashed_only
+- Env Var:     RCLONE_DRIVE_TRASHED_ONLY
+- Type:        bool
+- Default:     false
+
+#### --drive-starred-only
+
+Only show files that are starred.
+
+- Config:      starred_only
+- Env Var:     RCLONE_DRIVE_STARRED_ONLY
+- Type:        bool
+- Default:     false
+
+#### --drive-formats
+
+Deprecated: see export_formats
+
+- Config:      formats
+- Env Var:     RCLONE_DRIVE_FORMATS
+- Type:        string
+- Default:     &quot;&quot;
+
+#### --drive-export-formats
+
+Comma separated list of preferred formats for downloading Google docs.
+
+- Config:      export_formats
+- Env Var:     RCLONE_DRIVE_EXPORT_FORMATS
+- Type:        string
+- Default:     &quot;docx,xlsx,pptx,svg&quot;
+
+#### --drive-import-formats
+
+Comma separated list of preferred formats for uploading Google docs.
+
+- Config:      import_formats
+- Env Var:     RCLONE_DRIVE_IMPORT_FORMATS
+- Type:        string
+- Default:     &quot;&quot;
+
+#### --drive-allow-import-name-change
+
+Allow the filetype to change when uploading Google docs (e.g. file.doc to file.docx). This will confuse sync and reupload every time.
+
+- Config:      allow_import_name_change
+- Env Var:     RCLONE_DRIVE_ALLOW_IMPORT_NAME_CHANGE
+- Type:        bool
+- Default:     false
+
+#### --drive-use-created-date
+
+Use file created date instead of modified date.,
+
+Useful when downloading data and you want the creation date used in
+place of the last modified date.
+
+**WARNING**: This flag may have some unexpected consequences.
+
+When uploading to your drive all files will be overwritten unless they
+haven&#39;t been modified since their creation. And the inverse will occur
+while downloading.  This side effect can be avoided by using the
+&quot;--checksum&quot; flag.
+
+This feature was implemented to retain photos capture date as recorded
+by google photos. You will first need to check the &quot;Create a Google
+Photos folder&quot; 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.
+
+- Config:      use_created_date
+- Env Var:     RCLONE_DRIVE_USE_CREATED_DATE
+- Type:        bool
+- Default:     false
+
+#### --drive-use-shared-date
+
+Use date file was shared instead of modified date.
+
+Note that, as with &quot;--drive-use-created-date&quot;, this flag may have
+unexpected consequences when uploading/downloading files.
+
+If both this flag and &quot;--drive-use-created-date&quot; are set, the created
+date is used.
+
+- Config:      use_shared_date
+- Env Var:     RCLONE_DRIVE_USE_SHARED_DATE
+- Type:        bool
+- Default:     false
+
+#### --drive-list-chunk
+
+Size of listing chunk 100-1000. 0 to disable.
+
+- Config:      list_chunk
+- Env Var:     RCLONE_DRIVE_LIST_CHUNK
+- Type:        int
+- Default:     1000
+
+#### --drive-impersonate
+
+Impersonate this user when using a service account.
+
+- Config:      impersonate
+- Env Var:     RCLONE_DRIVE_IMPERSONATE
+- Type:        string
+- Default:     &quot;&quot;
+
+#### --drive-upload-cutoff
+
+Cutoff for switching to chunked upload
+
+- Config:      upload_cutoff
+- Env Var:     RCLONE_DRIVE_UPLOAD_CUTOFF
+- Type:        SizeSuffix
+- Default:     8M
+
+#### --drive-chunk-size
+
+Upload chunk size. Must a power of 2 &gt;= 256k.
+
+Making this larger will improve performance, but note that each chunk
+is buffered in memory one per transfer.
+
+Reducing this will reduce memory usage but decrease performance.
+
+- Config:      chunk_size
+- Env Var:     RCLONE_DRIVE_CHUNK_SIZE
+- Type:        SizeSuffix
+- Default:     8M
+
+#### --drive-acknowledge-abuse
+
+Set to allow files which return cannotDownloadAbusiveFile to be downloaded.
+
+If downloading a file returns the error &quot;This file has been identified
+as malware or spam and cannot be downloaded&quot; with the error code
+&quot;cannotDownloadAbusiveFile&quot; then supply this flag to rclone to
+indicate you acknowledge the risks of downloading the file and rclone
+will download it anyway.
+
+- Config:      acknowledge_abuse
+- Env Var:     RCLONE_DRIVE_ACKNOWLEDGE_ABUSE
+- Type:        bool
+- Default:     false
+
+#### --drive-keep-revision-forever
+
+Keep new head revision of each file forever.
+
+- Config:      keep_revision_forever
+- Env Var:     RCLONE_DRIVE_KEEP_REVISION_FOREVER
+- Type:        bool
+- Default:     false
+
+#### --drive-size-as-quota
+
+Show sizes as storage quota usage, not actual size.
+
+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.
+
+**WARNING**: This flag may have some unexpected consequences.
+
+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.
+
+If you do use this flag for syncing (not recommended) then you will
+need to use --ignore size also.
+
+- Config:      size_as_quota
+- Env Var:     RCLONE_DRIVE_SIZE_AS_QUOTA
+- Type:        bool
+- Default:     false
+
+#### --drive-v2-download-min-size
+
+If Object&#39;s are greater, use drive v2 API to download.
+
+- Config:      v2_download_min_size
+- Env Var:     RCLONE_DRIVE_V2_DOWNLOAD_MIN_SIZE
+- Type:        SizeSuffix
+- Default:     off
+
+#### --drive-pacer-min-sleep
+
+Minimum time to sleep between API calls.
+
+- Config:      pacer_min_sleep
+- Env Var:     RCLONE_DRIVE_PACER_MIN_SLEEP
+- Type:        Duration
+- Default:     100ms
+
+#### --drive-pacer-burst
+
+Number of API calls to allow without sleeping.
+
+- Config:      pacer_burst
+- Env Var:     RCLONE_DRIVE_PACER_BURST
+- Type:        int
+- Default:     100
+
+#### --drive-server-side-across-configs
+
+Allow server side operations (eg copy) to work across different drive configs.
+
+This can be useful if you wish to do a server side copy between two
+different Google drives.  Note that this isn&#39;t enabled by default
+because it isn&#39;t easy to tell if it will work between any two
+configurations.
+
+- Config:      server_side_across_configs
+- Env Var:     RCLONE_DRIVE_SERVER_SIDE_ACROSS_CONFIGS
+- Type:        bool
+- Default:     false
+
+#### --drive-disable-http2
+
+Disable drive using http2
+
+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.
+
+See: https://github.com/rclone/rclone/issues/3631
+
+
+
+- Config:      disable_http2
+- Env Var:     RCLONE_DRIVE_DISABLE_HTTP2
+- Type:        bool
+- Default:     true
+
+#### --drive-stop-on-upload-limit
+
+Make upload limit errors be fatal
+
+At the time of writing it is only possible to upload 750GB 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.
+
+Note that this detection is relying on error message strings which
+Google don&#39;t document so it may break in the future.
+
+See: https://github.com/rclone/rclone/issues/3857
+
+
+- Config:      stop_on_upload_limit
+- Env Var:     RCLONE_DRIVE_STOP_ON_UPLOAD_LIMIT
+- Type:        bool
+- Default:     false
+
+#### --drive-skip-shortcuts
+
+If set skip shortcut files
+
+Normally rclone dereferences shortcut files making them appear as if
+they are the original file (see [the shortcuts section](#shortcuts)).
+If this flag is set then rclone will ignore shortcut files completely.
+
+
+- Config:      skip_shortcuts
+- Env Var:     RCLONE_DRIVE_SKIP_SHORTCUTS
+- Type:        bool
+- Default:     false
+
+#### --drive-encoding
+
+This sets the encoding for the backend.
+
+See: the [encoding section in the overview](https://rclone.org/overview/#encoding) for more info.
+
+- Config:      encoding
+- Env Var:     RCLONE_DRIVE_ENCODING
+- Type:        MultiEncoder
+- Default:     InvalidUtf8
+
+### Backend commands
+
+Here are the commands specific to the drive backend.
+
+Run them with
+
+    rclone backend COMMAND remote:
+
+The help below will explain what arguments each command takes.
+
+See [the &quot;rclone backend&quot; command](https://rclone.org/commands/rclone_backend/) for more
+info on how to pass options and arguments.
+
+These can be run on a running backend using the rc command
+[backend/command](https://rclone.org/rc/#backend/command).
+
+#### get
+
+Get command for fetching the drive config parameters
+
+    rclone backend get remote: [options] [&lt;arguments&gt;+]
+
+This is a get command which will be used to fetch the various drive config parameters
+
+Usage Examples:
+
+    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]
+
+
+Options:
+
+- &quot;chunk_size&quot;: show the current upload chunk size
+- &quot;service_account_file&quot;: show the current service account file
+
+#### set
+
+Set command for updating the drive config parameters
+
+    rclone backend set remote: [options] [&lt;arguments&gt;+]
+
+This is a set command which will be used to update the various drive config parameters
+
+Usage Examples:
+
+    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]
+
+
+Options:
+
+- &quot;chunk_size&quot;: update the current upload chunk size
+- &quot;service_account_file&quot;: update the current service account file
+
+#### shortcut
+
+Create shortcuts from files or directories
+
+    rclone backend shortcut remote: [options] [&lt;arguments&gt;+]
+
+This command creates shortcuts from files or directories.
+
+Usage:
+
+    rclone backend shortcut drive: source_item destination_shortcut
+    rclone backend shortcut drive: source_item -o target=drive2: destination_shortcut
+
+In the first example this creates a shortcut from the &quot;source_item&quot;
+which can be a file or a directory to the &quot;destination_shortcut&quot;. The
+&quot;source_item&quot; and the &quot;destination_shortcut&quot; should be relative paths
+from &quot;drive:&quot;
+
+In the second example this creates a shortcut from the &quot;source_item&quot;
+relative to &quot;drive:&quot; to the &quot;destination_shortcut&quot; relative to
+&quot;drive2:&quot;. This may fail with a permission error if the user
+authenticated with &quot;drive2:&quot; can&#39;t read files from &quot;drive:&quot;.
+
+
+Options:
+
+- &quot;target&quot;: optional target remote for the shortcut destination
+
+#### drives
+
+List the shared drives available to this account
+
+    rclone backend drives remote: [options] [&lt;arguments&gt;+]
+
+This command lists the shared drives (teamdrives) available to this
+account.
+
+Usage:
+
+    rclone backend drives drive:
+
+This will return a JSON list of objects like this
+
+    [
+        {
+            &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;
+        }
+    ]
+
+
+
+#### untrash
+
+Untrash files and directories
+
+    rclone backend untrash remote: [options] [&lt;arguments&gt;+]
+
+This command untrashes all the files and directories in the directory
+passed in recursively.
+
+Usage:
+
+This takes an optional directory to trash which make this easier to
+use via the API.
+
+    rclone backend untrash drive:directory
+    rclone backend -i untrash drive:directory subdir
+
+Use the -i flag to see what would be restored before restoring it.
+
+Result:
+
+    {
+        &quot;Untrashed&quot;: 17,
+        &quot;Errors&quot;: 0
+    }
+
+
+
+
+### Limitations ###
+
+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 MBytes/s but lots of
+small files can take a long time.
+
+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 `--disable copy` to download
+and upload the files if you prefer.
+
+#### Limitations of Google Docs ####
+
+Google docs will appear as size -1 in `rclone ls` and as size 0 in
+anything which uses the VFS layer, eg `rclone mount`, `rclone serve`.
+
+This is because rclone can&#39;t find out the size of the Google docs
+without downloading them.
+
+Google docs will transfer correctly with `rclone sync`, `rclone copy`
+etc as rclone knows to ignore the size when doing the transfer.
+
+However an unfortunate consequence of this is that you may not be able
+to download Google docs using `rclone mount`. If it doesn&#39;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!
+
+### Duplicated files ###
+
+Sometimes, for no reason I&#39;ve been able to track down, drive will
+duplicate a file that rclone uploads.  Drive unlike all the other
+remotes can have duplicated files.
+
+Duplicated files cause problems with the syncing and you will see
+messages in the log about duplicates.
+
+Use `rclone dedupe` to fix duplicated files.
+
+Note that this isn&#39;t just a problem with rclone, even Google Photos on
+Android duplicates files on drive sometimes.
+
+### Rclone appears to be re-copying files it shouldn&#39;t ###
+
+The most likely cause of this is the duplicated file issue above - run
+`rclone dedupe` and check your logs for duplicate object or directory
+messages.
+
+This can also be caused by a delay/caching on google drive&#39;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.
+
+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.
+
+### Making your own client_id ###
+
+When you use rclone with Google drive in its default configuration you
+are using rclone&#39;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.
+
+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.
+
+Here is how to create your own Google Drive client ID for rclone:
+
+1. Log into the [Google API
+Console](https://console.developers.google.com/) with your Google
+account. It doesn&#39;t matter what Google account you use. (It need not
+be the same account as the Google Drive you want to access)
+
+2. Select a project or create a new project.
+
+3. Under &quot;ENABLE APIS AND SERVICES&quot; search for &quot;Drive&quot;, and enable the
+&quot;Google Drive API&quot;.
+
+4. Click &quot;Credentials&quot; in the left-side panel (not &quot;Create
+credentials&quot;, which opens the wizard), then &quot;Create credentials&quot;
+
+5. If you already configured an &quot;Oauth Consent Screen&quot;, then skip
+to the next step; if not, click on &quot;CONFIGURE CONSENT SCREEN&quot; button 
+(near the top right corner of the right panel), then select &quot;External&quot;
+and click on &quot;CREATE&quot;; on the next screen, enter an &quot;Application name&quot;
+(&quot;rclone&quot; is OK) then click on &quot;Save&quot; (all other data is optional). 
+Click again on &quot;Credentials&quot; on the left panel to go back to the 
+&quot;Credentials&quot; screen.
+
+(PS: if you are a GSuite user, you could also select &quot;Internal&quot; instead
+of &quot;External&quot; above, but this has not been tested/documented so far). 
+
+6.  Click on the &quot;+ CREATE CREDENTIALS&quot; button at the top of the screen,
+then select &quot;OAuth client ID&quot;.
+
+7. Choose an application type of &quot;Desktop app&quot; if you using a Google account or &quot;Other&quot; if 
+you using a GSuite account and click &quot;Create&quot;. (the default name is fine)
+
+8. It will show you a client ID and client secret.  Use these values
+in rclone config to add a new remote or edit an existing remote.
+
+Be aware that, due to the &quot;enhanced security&quot; recently introduced by
+Google, you are theoretically expected to &quot;submit your app for verification&quot;
+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&#39;s not such a big deal). 
+
+(Thanks to @balazer on github for these instructions.)
+
+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
+[Python Quickstart](https://developers.google.com/drive/api/v3/quickstart/python) 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.
+
+ Google Photos
+-------------------------------------------------
+
+The rclone backend for [Google Photos](https://www.google.com/photos/about/) is
+a specialized backend for transferring photos and videos to and from
+Google Photos.
+
+**NB** The Google Photos API which rclone uses has quite a few
+limitations, so please read the [limitations section](#limitations)
+carefully to make sure it is suitable for your use.
+
+## Configuring Google Photos
+
+The initial setup for google cloud storage involves getting a token from Google Photos
+which you need to do in your browser.  `rclone config` walks you
+through it.
+
+Here is an example of how to make a remote called `remote`.  First run:
+
+     rclone config
+
+This will guide you through an interactive setup process:
+</code></pre>
+<p>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 (""). Choose a number from below, or type in your own value [snip] XX / Google Photos  "google photos" [snip] Storage&gt; google photos ** See help for google photos backend at: https://rclone.org/googlephotos/ **</p>
+<p>Google Application Client Id Leave blank normally. Enter a string value. Press Enter for the default (""). client_id&gt; Google Application Client Secret Leave blank normally. Enter a string value. Press Enter for the default (""). client_secret&gt; 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. Enter a boolean value (true or false). Press Enter for the default ("false"). read_only&gt; Edit advanced config? (y/n) y) Yes n) No y/n&gt; n Remote config Use auto config? * Say Y if not sure * Say N if you are working on a remote or headless machine y) Yes n) No y/n&gt; y If your browser doesn'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</p>
+<p>*** 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.</p>
+<table style="width:29%;">
 <colgroup>
-<col style="width: 28%" />
-<col style="width: 34%" />
-<col style="width: 37%" />
+<col style="width: 29%" />
 </colgroup>
 <thead>
 <tr class="header">
-<th>Extension</th>
-<th>Mime Type</th>
-<th>Description</th>
+<th style="text-align: left;">[remote] type = google photos token = {"access_token":"XXX","token_type":"Bearer","refresh_token":"XXX","expiry":"2019-06-28T17:38:04.644930156+01:00"}</th>
 </tr>
 </thead>
 <tbody>
 <tr class="odd">
-<td>csv</td>
-<td>text/csv</td>
-<td>Standard CSV format for Spreadsheets</td>
+<td style="text-align: left;">y) Yes this is OK e) Edit this remote d) Delete this remote y/e/d&gt; y ```</td>
 </tr>
 <tr class="even">
-<td>docx</td>
-<td>application/vnd.openxmlformats-officedocument.wordprocessingml.document</td>
-<td>Microsoft Office Document</td>
+<td style="text-align: left;">Note that rclone runs a webserver on your local machine to collect the token as returned from Google if you use auto config mode. 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.</td>
 </tr>
 <tr class="odd">
-<td>epub</td>
-<td>application/epub+zip</td>
-<td>E-book format</td>
+<td style="text-align: left;">This remote is called <code>remote</code> and can now be used like this</td>
 </tr>
 <tr class="even">
-<td>html</td>
-<td>text/html</td>
-<td>An HTML Document</td>
+<td style="text-align: left;">See all the albums in your photos</td>
 </tr>
 <tr class="odd">
-<td>jpg</td>
-<td>image/jpeg</td>
-<td>A JPEG Image File</td>
+<td style="text-align: left;">rclone lsd remote:album</td>
 </tr>
 <tr class="even">
-<td>json</td>
-<td>application/vnd.google-apps.script+json</td>
-<td>JSON Text Format</td>
+<td style="text-align: left;">Make a new album</td>
 </tr>
 <tr class="odd">
-<td>odp</td>
-<td>application/vnd.oasis.opendocument.presentation</td>
-<td>Openoffice Presentation</td>
+<td style="text-align: left;">rclone mkdir remote:album/newAlbum</td>
 </tr>
 <tr class="even">
-<td>ods</td>
-<td>application/vnd.oasis.opendocument.spreadsheet</td>
-<td>Openoffice Spreadsheet</td>
+<td style="text-align: left;">List the contents of an album</td>
 </tr>
 <tr class="odd">
-<td>ods</td>
-<td>application/x-vnd.oasis.opendocument.spreadsheet</td>
-<td>Openoffice Spreadsheet</td>
+<td style="text-align: left;">rclone ls remote:album/newAlbum</td>
 </tr>
 <tr class="even">
-<td>odt</td>
-<td>application/vnd.oasis.opendocument.text</td>
-<td>Openoffice Document</td>
+<td style="text-align: left;">Sync <code>/home/local/images</code> to the Google Photos, removing any excess files in the album.</td>
 </tr>
 <tr class="odd">
-<td>pdf</td>
-<td>application/pdf</td>
-<td>Adobe PDF Format</td>
+<td style="text-align: left;">rclone sync -i /home/local/image remote:album/newAlbum</td>
 </tr>
 <tr class="even">
-<td>png</td>
-<td>image/png</td>
-<td>PNG Image Format</td>
+<td style="text-align: left;">## Layout</td>
 </tr>
 <tr class="odd">
-<td>pptx</td>
-<td>application/vnd.openxmlformats-officedocument.presentationml.presentation</td>
-<td>Microsoft Office Powerpoint</td>
+<td style="text-align: left;">As Google Photos is not a general purpose cloud storage system the backend is laid out to help you navigate it.</td>
 </tr>
 <tr class="even">
-<td>rtf</td>
-<td>application/rtf</td>
-<td>Rich Text Format</td>
+<td style="text-align: left;">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.)</td>
 </tr>
 <tr class="odd">
-<td>svg</td>
-<td>image/svg+xml</td>
-<td>Scalable Vector Graphics Format</td>
+<td style="text-align: left;">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.</td>
 </tr>
 <tr class="even">
-<td>tsv</td>
-<td>text/tab-separated-values</td>
-<td>Standard TSV format for spreadsheets</td>
+<td style="text-align: left;"><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></td>
 </tr>
 <tr class="odd">
-<td>txt</td>
-<td>text/plain</td>
-<td>Plain Text</td>
+<td style="text-align: left;">There are two writable parts of the tree, the <code>upload</code> directory and sub directories of the <code>album</code> directory.</td>
 </tr>
 <tr class="even">
-<td>xlsx</td>
-<td>application/vnd.openxmlformats-officedocument.spreadsheetml.sheet</td>
-<td>Microsoft Office Spreadsheet</td>
+<td style="text-align: left;">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.</td>
 </tr>
 <tr class="odd">
-<td>zip</td>
-<td>application/zip</td>
-<td>A ZIP file of HTML, Images CSS</td>
+<td style="text-align: left;">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</td>
+</tr>
+<tr class="even">
+<td style="text-align: left;">rclone copy /path/to/images remote:album/images</td>
+</tr>
+<tr class="odd">
+<td style="text-align: left;">and the images directory contains</td>
+</tr>
+<tr class="even">
+<td style="text-align: left;"><code>images - file1.jpg dir file2.jpg dir2 dir3 file3.jpg</code></td>
+</tr>
+<tr class="odd">
+<td style="text-align: left;">Then rclone will create the following albums with the following files in</td>
+</tr>
+<tr class="even">
+<td style="text-align: left;">- images - file1.jpg - images/dir - file2.jpg - images/dir2/dir3 - file3.jpg</td>
+</tr>
+<tr class="odd">
+<td style="text-align: left;">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.</td>
+</tr>
+<tr class="even">
+<td style="text-align: left;">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.</td>
+</tr>
+<tr class="odd">
+<td style="text-align: left;">## Limitations</td>
+</tr>
+<tr class="even">
+<td style="text-align: left;">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.</td>
+</tr>
+<tr class="odd">
+<td style="text-align: left;">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..</td>
+</tr>
+<tr class="even">
+<td style="text-align: left;">### Downloading Images</td>
+</tr>
+<tr class="odd">
+<td style="text-align: left;">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>.</td>
+</tr>
+<tr class="even">
+<td style="text-align: left;"><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></td>
+</tr>
+<tr class="odd">
+<td style="text-align: left;">### Downloading Videos</td>
+</tr>
+<tr class="even">
+<td style="text-align: left;">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>.</td>
+</tr>
+<tr class="odd">
+<td style="text-align: left;">### Duplicates</td>
+</tr>
+<tr class="even">
+<td style="text-align: left;">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!).</td>
+</tr>
+<tr class="odd">
+<td style="text-align: left;">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.</td>
+</tr>
+<tr class="even">
+<td style="text-align: left;">### Modified time</td>
+</tr>
+<tr class="odd">
+<td style="text-align: left;">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.</td>
+</tr>
+<tr class="even">
+<td style="text-align: left;">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.</td>
+</tr>
+<tr class="odd">
+<td style="text-align: left;">### Size</td>
+</tr>
+<tr class="even">
+<td style="text-align: left;">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.</td>
+</tr>
+<tr class="odd">
+<td style="text-align: left;">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.</td>
+</tr>
+<tr class="even">
+<td style="text-align: left;">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.</td>
+</tr>
+<tr class="odd">
+<td style="text-align: left;">### Albums</td>
+</tr>
+<tr class="even">
+<td style="text-align: left;">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>.</td>
+</tr>
+<tr class="odd">
+<td style="text-align: left;">Rclone can remove files it uploaded from albums it created only.</td>
+</tr>
+<tr class="even">
+<td style="text-align: left;">### Deleting files</td>
+</tr>
+<tr class="odd">
+<td style="text-align: left;">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>.</td>
+</tr>
+<tr class="even">
+<td style="text-align: left;">Rclone cannot delete files anywhere except under <code>album</code>.</td>
+</tr>
+<tr class="odd">
+<td style="text-align: left;">### Deleting albums</td>
+</tr>
+<tr class="even">
+<td style="text-align: left;">The Google Photos API does not support deleting albums - see <a href="https://issuetracker.google.com/issues/135714733">bug #135714733</a>.</td>
+</tr>
+<tr class="odd">
+<td style="text-align: left;">### Standard Options</td>
+</tr>
+<tr class="even">
+<td style="text-align: left;">Here are the standard options specific to google photos (Google Photos).</td>
+</tr>
+<tr class="odd">
+<td style="text-align: left;">#### --gphotos-client-id</td>
+</tr>
+<tr class="even">
+<td style="text-align: left;">OAuth Client Id Leave blank normally.</td>
+</tr>
+<tr class="odd">
+<td style="text-align: left;">- Config: client_id - Env Var: RCLONE_GPHOTOS_CLIENT_ID - Type: string - Default: ""</td>
+</tr>
+<tr class="even">
+<td style="text-align: left;">#### --gphotos-client-secret</td>
+</tr>
+<tr class="odd">
+<td style="text-align: left;">OAuth Client Secret Leave blank normally.</td>
+</tr>
+<tr class="even">
+<td style="text-align: left;">- Config: client_secret - Env Var: RCLONE_GPHOTOS_CLIENT_SECRET - Type: string - Default: ""</td>
+</tr>
+<tr class="odd">
+<td style="text-align: left;">#### --gphotos-read-only</td>
+</tr>
+<tr class="even">
+<td style="text-align: left;">Set to make the Google Photos backend read only.</td>
+</tr>
+<tr class="odd">
+<td style="text-align: left;">If you choose read only then rclone will only request read only access to your photos, otherwise rclone will request full access.</td>
+</tr>
+<tr class="even">
+<td style="text-align: left;">- Config: read_only - Env Var: RCLONE_GPHOTOS_READ_ONLY - Type: bool - Default: false</td>
+</tr>
+<tr class="odd">
+<td style="text-align: left;">### Advanced Options</td>
+</tr>
+<tr class="even">
+<td style="text-align: left;">Here are the advanced options specific to google photos (Google Photos).</td>
+</tr>
+<tr class="odd">
+<td style="text-align: left;">#### --gphotos-token</td>
+</tr>
+<tr class="even">
+<td style="text-align: left;">OAuth Access Token as a JSON blob.</td>
+</tr>
+<tr class="odd">
+<td style="text-align: left;">- Config: token - Env Var: RCLONE_GPHOTOS_TOKEN - Type: string - Default: ""</td>
+</tr>
+<tr class="even">
+<td style="text-align: left;">#### --gphotos-auth-url</td>
+</tr>
+<tr class="odd">
+<td style="text-align: left;">Auth server URL. Leave blank to use the provider defaults.</td>
+</tr>
+<tr class="even">
+<td style="text-align: left;">- Config: auth_url - Env Var: RCLONE_GPHOTOS_AUTH_URL - Type: string - Default: ""</td>
+</tr>
+<tr class="odd">
+<td style="text-align: left;">#### --gphotos-token-url</td>
+</tr>
+<tr class="even">
+<td style="text-align: left;">Token server url. Leave blank to use the provider defaults.</td>
+</tr>
+<tr class="odd">
+<td style="text-align: left;">- Config: token_url - Env Var: RCLONE_GPHOTOS_TOKEN_URL - Type: string - Default: ""</td>
+</tr>
+<tr class="even">
+<td style="text-align: left;">#### --gphotos-read-size</td>
+</tr>
+<tr class="odd">
+<td style="text-align: left;">Set to read the size of media items.</td>
+</tr>
+<tr class="even">
+<td style="text-align: left;">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.</td>
+</tr>
+<tr class="odd">
+<td style="text-align: left;">- Config: read_size - Env Var: RCLONE_GPHOTOS_READ_SIZE - Type: bool - Default: false</td>
+</tr>
+<tr class="even">
+<td style="text-align: left;">#### --gphotos-start-year</td>
+</tr>
+<tr class="odd">
+<td style="text-align: left;">Year limits the photos to be downloaded to those which are uploaded after the given year</td>
+</tr>
+<tr class="even">
+<td style="text-align: left;">- Config: start_year - Env Var: RCLONE_GPHOTOS_START_YEAR - Type: int - Default: 2000</td>
+</tr>
+<tr class="odd">
+<td style="text-align: left;">HTTP</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-13">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>
-<ul>
-<li>Config: client_id</li>
-<li>Env Var: RCLONE_DRIVE_CLIENT_ID</li>
-<li>Type: string</li>
-<li>Default: ""</li>
-</ul>
-<h4 id="drive-client-secret">–drive-client-secret</h4>
-<p>Google Application Client Secret Setting your own is recommended.</p>
-<ul>
-<li>Config: client_secret</li>
-<li>Env Var: RCLONE_DRIVE_CLIENT_SECRET</li>
-<li>Type: string</li>
-<li>Default: ""</li>
-</ul>
-<h4 id="drive-scope">–drive-scope</h4>
-<p>Scope that rclone should use when requesting access from drive.</p>
-<ul>
-<li>Config: scope</li>
-<li>Env Var: RCLONE_DRIVE_SCOPE</li>
-<li>Type: string</li>
-<li>Default: ""</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-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>Note that if this is blank, the first time rclone runs it will fill it in with the ID of the root folder.</p>
-<ul>
-<li>Config: root_folder_id</li>
-<li>Env Var: RCLONE_DRIVE_ROOT_FOLDER_ID</li>
-<li>Type: string</li>
-<li>Default: ""</li>
-</ul>
-<h4 id="drive-service-account-file">–drive-service-account-file</h4>
-<p>Service Account Credentials JSON file path Leave blank normally. Needed only if you want use SA instead of interactive login.</p>
-<ul>
-<li>Config: service_account_file</li>
-<li>Env Var: RCLONE_DRIVE_SERVICE_ACCOUNT_FILE</li>
-<li>Type: string</li>
-<li>Default: ""</li>
-</ul>
-<h3 id="advanced-options-12">Advanced Options</h3>
-<p>Here are the advanced options specific to drive (Google Drive).</p>
-<h4 id="drive-service-account-credentials">–drive-service-account-credentials</h4>
-<p>Service Account Credentials JSON blob Leave blank normally. Needed only if you want use SA instead of interactive login.</p>
-<ul>
-<li>Config: service_account_credentials</li>
-<li>Env Var: RCLONE_DRIVE_SERVICE_ACCOUNT_CREDENTIALS</li>
-<li>Type: string</li>
-<li>Default: ""</li>
-</ul>
-<h4 id="drive-team-drive">–drive-team-drive</h4>
-<p>ID of the Team Drive</p>
-<ul>
-<li>Config: team_drive</li>
-<li>Env Var: RCLONE_DRIVE_TEAM_DRIVE</li>
-<li>Type: string</li>
-<li>Default: ""</li>
-</ul>
-<h4 id="drive-auth-owner-only">–drive-auth-owner-only</h4>
-<p>Only consider files owned by the authenticated user.</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. Defaults to true, namely sending files to the trash. Use <code>--drive-use-trash=false</code> to delete files permanently instead.</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-skip-gdocs">–drive-skip-gdocs</h4>
-<p>Skip google documents in all listings. If given, gdocs practically become invisible to rclone.</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-skip-checksum-gphotos">–drive-skip-checksum-gphotos</h4>
-<p>Skip MD5 checksum 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 MD5 checksum.</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>
-<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>
-<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. This will show trashed files in their original directory structure.</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-formats">–drive-formats</h4>
-<p>Deprecated: see export_formats</p>
-<ul>
-<li>Config: formats</li>
-<li>Env Var: RCLONE_DRIVE_FORMATS</li>
-<li>Type: string</li>
-<li>Default: ""</li>
-</ul>
-<h4 id="drive-export-formats">–drive-export-formats</h4>
-<p>Comma separated list of preferred formats for downloading Google docs.</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>
-<ul>
-<li>Config: import_formats</li>
-<li>Env Var: RCLONE_DRIVE_IMPORT_FORMATS</li>
-<li>Type: string</li>
-<li>Default: ""</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 (e.g. file.doc to file.docx). This will confuse sync and reupload every time.</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>
-<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>
-<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>
-<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>
-<ul>
-<li>Config: impersonate</li>
-<li>Env Var: RCLONE_DRIVE_IMPERSONATE</li>
-<li>Type: string</li>
-<li>Default: ""</li>
-</ul>
-<h4 id="drive-alternate-export">–drive-alternate-export</h4>
-<p>Use alternate export URLs for google documents export.,</p>
-<p>If this option is set this instructs rclone to use an alternate set of export URLs for drive documents. Users have reported that the official export URLs can’t export large documents, whereas these unofficial ones can.</p>
-<p>See rclone issue <a href="https://github.com/rclone/rclone/issues/2243">#2243</a> for background, <a href="https://issuetracker.google.com/issues/36761333">this google drive issue</a> and <a href="https://www.labnol.org/internet/direct-links-for-google-drive/28356/">this helpful post</a>.</p>
-<ul>
-<li>Config: alternate_export</li>
-<li>Env Var: RCLONE_DRIVE_ALTERNATE_EXPORT</li>
-<li>Type: bool</li>
-<li>Default: false</li>
-</ul>
-<h4 id="drive-upload-cutoff">–drive-upload-cutoff</h4>
-<p>Cutoff for switching to chunked upload</p>
-<ul>
-<li>Config: upload_cutoff</li>
-<li>Env Var: RCLONE_DRIVE_UPLOAD_CUTOFF</li>
-<li>Type: SizeSuffix</li>
-<li>Default: 8M</li>
-</ul>
-<h4 id="drive-chunk-size">–drive-chunk-size</h4>
-<p>Upload chunk size. 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>
-<ul>
-<li>Config: chunk_size</li>
-<li>Env Var: RCLONE_DRIVE_CHUNK_SIZE</li>
-<li>Type: SizeSuffix</li>
-<li>Default: 8M</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>
-<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>
-<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>
-<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>
-<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>
-<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>
-<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>Allow server side operations (eg 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>
-<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>
-<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 750GB 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>
-<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-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>
-<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-encoding">–drive-encoding</h4>
-<p>This sets 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>
-<ul>
-<li>Config: encoding</li>
-<li>Env Var: RCLONE_DRIVE_ENCODING</li>
-<li>Type: MultiEncoder</li>
-<li>Default: InvalidUtf8</li>
-</ul>
-<h3 id="backend-commands-2">Backend commands</h3>
-<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 <a href="https://rclone.org/commands/rclone_backend/">the “rclone backend” command</a> 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>
-<h4 id="get">get</h4>
-<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>
-<h4 id="set">set</h4>
-<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>
-<h4 id="shortcut">shortcut</h4>
-<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="limitations-7">Limitations</h3>
-<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 MBytes/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>
-<h4 id="limitations-of-google-docs">Limitations of Google Docs</h4>
-<p>Google docs will appear as size -1 in <code>rclone ls</code> and as size 0 in anything which uses the VFS layer, eg <code>rclone mount</code>, <code>rclone serve</code>.</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-1">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="making-your-own-client_id">Making your own client_id</h3>
-<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), then “Create credentials”</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) then click on “Save” (all other data is optional). Click again on “Credentials” on the left panel to go back to the “Credentials” screen.</p></li>
-</ol>
-<p>(PS: if you are a GSuite user, you could also select “Internal” instead of “External” above, but this has not been tested/documented so far).</p>
-<ol start="6" type="1">
-<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” if you using a Google account or “Other” if you using a GSuite account and click “Create”. (the default name is fine)</p></li>
-<li><p>It will show you a client ID and client secret. Use these values in rclone config to add a new remote or edit an existing remote.</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).</p>
-<p>(Thanks to <span class="citation" data-cites="balazer">@balazer</span> on github for these instructions.)</p>
-<h2 id="google-photos">Google Photos</h2>
-<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="configuring-google-photos">Configuring Google Photos</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 auto config?
- * Say Y if not sure
- * Say N if you are working on a remote or headless machine
-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.
-
---------------------
-[remote]
-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;}
---------------------
-y) Yes this is OK
-e) Edit this remote
-d) Delete this remote
-y/e/d&gt; y</code></pre>
-<p>Note that rclone runs a webserver on your local machine to collect the token as returned from Google if you use auto config mode. 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 /home/local/image remote:album/newAlbum</code></pre>
-<h2 id="layout">Layout</h2>
-<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>
-<h2 id="limitations-8">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>
-<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="modified-time-6">Modified time</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-3">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>
-<h3 id="standard-options-14">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>Google Application Client Id Leave blank normally.</p>
-<ul>
-<li>Config: client_id</li>
-<li>Env Var: RCLONE_GPHOTOS_CLIENT_ID</li>
-<li>Type: string</li>
-<li>Default: ""</li>
-</ul>
-<h4 id="gphotos-client-secret">–gphotos-client-secret</h4>
-<p>Google Application Client Secret Leave blank normally.</p>
-<ul>
-<li>Config: client_secret</li>
-<li>Env Var: RCLONE_GPHOTOS_CLIENT_SECRET</li>
-<li>Type: string</li>
-<li>Default: ""</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>
-<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-13">Advanced Options</h3>
-<p>Here are the advanced options specific to google photos (Google Photos).</p>
-<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>
-<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>
-<ul>
-<li>Config: start_year</li>
-<li>Env Var: RCLONE_GPHOTOS_START_YEAR</li>
-<li>Type: int</li>
-<li>Default: 2000</li>
-</ul>
-<h2 id="http">HTTP</h2>
-<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>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/to/dir</code>.</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>
@@ -12306,19 +12474,19 @@ e/n/d/r/c/s/q&gt; q</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 remote:directory /home/local/directory</code></pre>
+<pre><code>rclone sync -i 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="modified-time-7">Modified time</h3>
+<p>This remote is read only - you can't upload files to an HTTP server.</p>
+<h3 id="modified-time">Modified time</h3>
 <p>Most HTTP servers store time accurate to 1 second.</p>
 <h3 id="checksum">Checksum</h3>
 <p>No checksums are stored.</p>
-<h3 id="usage-without-a-config-file-1">Usage without a config file</h3>
+<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>
-<h3 id="standard-options-15">Standard Options</h3>
+<h3 id="standard-options">Standard Options</h3>
 <p>Here are the standard options specific to http (http Connection).</p>
-<h4 id="http-url">–http-url</h4>
+<h4 id="http-url">--http-url</h4>
 <p>URL of http host to connect to</p>
 <ul>
 <li>Config: url</li>
@@ -12327,32 +12495,32 @@ e/n/d/r/c/s/q&gt; q</code></pre>
 <li>Default: ""</li>
 <li>Examples:
 <ul>
-<li>“https://example.com”
+<li>"https://example.com"
 <ul>
 <li>Connect to example.com</li>
 </ul></li>
-<li>“https://user:pass@example.com”
+<li>"https://user:pass@example.com"
 <ul>
 <li>Connect to example.com using a username and password</li>
 </ul></li>
 </ul></li>
 </ul>
-<h3 id="advanced-options-14">Advanced Options</h3>
+<h3 id="advanced-options">Advanced Options</h3>
 <p>Here are the advanced options specific to http (http Connection).</p>
-<h4 id="http-headers">–http-headers</h4>
+<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, eg ‘“Cookie”,“name=value”,“Authorization”,“xxx”’.</p>
+<p>For example to set a Cookie use 'Cookie,name=value', or '"Cookie","name=value"'.</p>
+<p>You can set multiple headers, eg '"Cookie","name=value","Authorization","xxx"'.</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>
+<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>
@@ -12362,8 +12530,8 @@ e/n/d/r/c/s/q&gt; q</code></pre>
 <li>Type: bool</li>
 <li>Default: false</li>
 </ul>
-<h4 id="http-no-head">–http-no-head</h4>
-<p>Don’t use HEAD requests to find file sizes in dir listing</p>
+<h4 id="http-no-head">--http-no-head</h4>
+<p>Don't use HEAD requests to find file sizes in dir listing</p>
 <p>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>
@@ -12373,8 +12541,8 @@ e/n/d/r/c/s/q&gt; q</code></pre>
 <p>If you set this option, rclone will not do the HEAD request. This will mean</p>
 <ul>
 <li>directory listings are much quicker</li>
-<li>rclone won’t have the times or sizes of any files</li>
-<li><p>some files that don’t exist may be in the listing</p></li>
+<li>rclone won't have the times or sizes of any files</li>
+<li><p>some files that don't exist may be in the listing</p></li>
 <li>Config: no_head</li>
 <li>Env Var: RCLONE_HTTP_NO_HEAD</li>
 <li>Type: bool</li>
@@ -12434,33 +12602,57 @@ y/e/d&gt; y</code></pre>
 <pre><code>rclone copy /home/source remote:backup</code></pre>
 <p>If you want the directory to be visible in the official <em>Hubic browser</em>, you need to copy your files to the <code>default</code> directory</p>
 <pre><code>rclone copy /home/source remote:default/backup</code></pre>
-<h3 id="fast-list-5">–fast-list</h3>
+<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="modified-time-8">Modified time</h3>
+<h3 id="modified-time-1">Modified time</h3>
 <p>The modified time is stored as metadata on the object as <code>X-Object-Meta-Mtime</code> as floating point since the epoch accurate to 1 ns.</p>
 <p>This is a de facto standard (used in the official python-swiftclient amongst others) for storing the modification time for an object.</p>
 <p>Note that Hubic wraps the Swift backend, so most of the properties of are the same.</p>
-<h3 id="standard-options-16">Standard Options</h3>
+<h3 id="standard-options-1">Standard Options</h3>
 <p>Here are the standard options specific to hubic (Hubic).</p>
-<h4 id="hubic-client-id">–hubic-client-id</h4>
-<p>Hubic Client Id Leave blank normally.</p>
+<h4 id="hubic-client-id">--hubic-client-id</h4>
+<p>OAuth Client Id Leave blank normally.</p>
 <ul>
 <li>Config: client_id</li>
 <li>Env Var: RCLONE_HUBIC_CLIENT_ID</li>
 <li>Type: string</li>
 <li>Default: ""</li>
 </ul>
-<h4 id="hubic-client-secret">–hubic-client-secret</h4>
-<p>Hubic Client Secret Leave blank normally.</p>
+<h4 id="hubic-client-secret">--hubic-client-secret</h4>
+<p>OAuth Client Secret Leave blank normally.</p>
 <ul>
 <li>Config: client_secret</li>
 <li>Env Var: RCLONE_HUBIC_CLIENT_SECRET</li>
 <li>Type: string</li>
 <li>Default: ""</li>
 </ul>
-<h3 id="advanced-options-15">Advanced Options</h3>
+<h3 id="advanced-options-1">Advanced Options</h3>
 <p>Here are the advanced options specific to hubic (Hubic).</p>
-<h4 id="hubic-chunk-size">–hubic-chunk-size</h4>
+<h4 id="hubic-token">--hubic-token</h4>
+<p>OAuth Access Token as a JSON blob.</p>
+<ul>
+<li>Config: token</li>
+<li>Env Var: RCLONE_HUBIC_TOKEN</li>
+<li>Type: string</li>
+<li>Default: ""</li>
+</ul>
+<h4 id="hubic-auth-url">--hubic-auth-url</h4>
+<p>Auth server URL. Leave blank to use the provider defaults.</p>
+<ul>
+<li>Config: auth_url</li>
+<li>Env Var: RCLONE_HUBIC_AUTH_URL</li>
+<li>Type: string</li>
+<li>Default: ""</li>
+</ul>
+<h4 id="hubic-token-url">--hubic-token-url</h4>
+<p>Token server url. Leave blank to use the provider defaults.</p>
+<ul>
+<li>Config: token_url</li>
+<li>Env Var: RCLONE_HUBIC_TOKEN_URL</li>
+<li>Type: string</li>
+<li>Default: ""</li>
+</ul>
+<h4 id="hubic-chunk-size">--hubic-chunk-size</h4>
 <p>Above this size files will be chunked into a _segments container.</p>
 <p>Above this size files will be chunked into a _segments container. The default for this is 5GB which is its maximum value.</p>
 <ul>
@@ -12469,8 +12661,8 @@ y/e/d&gt; y</code></pre>
 <li>Type: SizeSuffix</li>
 <li>Default: 5G</li>
 </ul>
-<h4 id="hubic-no-chunk">–hubic-no-chunk</h4>
-<p>Don’t chunk files during streaming upload.</p>
+<h4 id="hubic-no-chunk">--hubic-no-chunk</h4>
+<p>Don't chunk files during streaming upload.</p>
 <p>When doing streaming uploads (eg using rcat or mount) setting this flag will cause the swift backend to not upload chunked files.</p>
 <p>This will limit the maximum upload size to 5GB. However non chunked files are easier to deal with and have an MD5SUM.</p>
 <p>Rclone will still chunk files bigger than chunk_size when doing normal copy operations.</p>
@@ -12480,7 +12672,7 @@ y/e/d&gt; y</code></pre>
 <li>Type: bool</li>
 <li>Default: false</li>
 </ul>
-<h4 id="hubic-encoding">–hubic-encoding</h4>
+<h4 id="hubic-encoding">--hubic-encoding</h4>
 <p>This sets 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>
 <ul>
@@ -12489,17 +12681,20 @@ y/e/d&gt; y</code></pre>
 <li>Type: MultiEncoder</li>
 <li>Default: Slash,InvalidUtf8</li>
 </ul>
-<h3 id="limitations-9">Limitations</h3>
+<h3 id="limitations-2">Limitations</h3>
 <p>This uses the normal OpenStack Swift mechanism to refresh the Swift API credentials and ignores the expires field returned by the Hubic API.</p>
-<p>The Swift API doesn’t return a correct MD5SUM for segmented files (Dynamic or Static Large Objects) so rclone won’t check or use the MD5SUM for these.</p>
+<p>The Swift API doesn't return a correct MD5SUM for segmented files (Dynamic or Static Large Objects) so rclone won't check or use the MD5SUM for these.</p>
 <h2 id="jottacloud">Jottacloud</h2>
 <p>Jottacloud is a cloud storage service provider from a Norwegian company, using its own datacenters in Norway.</p>
 <p>In addition to the official service at <a href="https://www.jottacloud.com/">jottacloud.com</a>, there are also several whitelabel versions which should work with this backend.</p>
 <p>Paths are specified as <code>remote:path</code></p>
 <p>Paths may be as deep as required, eg <code>remote:directory/subdirectory</code>.</p>
-<h2 id="setup-2">Setup</h2>
+<h2 id="setup">Setup</h2>
+<h3 id="default-setup">Default Setup</h3>
 <p>To configure Jottacloud you will need to generate a personal security token in the Jottacloud web interface. You will the option to do in your <a href="https://www.jottacloud.com/web/secure">account security settings</a> (for whitelabel version you need to find this page in its web interface). Note that the web interface may refer to this token as a JottaCli token.</p>
-<p>Here is an example of how to make a remote called <code>remote</code>. First run:</p>
+<h3 id="legacy-setup">Legacy Setup</h3>
+<p>If you are using one of the whitelabel versions (Elgiganten, Com Hem Cloud) you may not have the option to generate a CLI token. In this case you'll have to use the legacy authentification. To to this select yes when the setup asks for legacy authentification and enter your username and password. The rest of the setup is identical to the default setup.</p>
+<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
@@ -12507,7 +12702,7 @@ n) New remote
 s) Set configuration password
 q) Quit config
 n/s/q&gt; n
-name&gt; jotta
+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
@@ -12523,6 +12718,11 @@ y) Yes
 n) No
 y/n&gt; n
 Remote config
+Use legacy authentification?.
+This is only required for certain whitelabel versions of Jottacloud and not recommended for normal users.
+y) Yes
+n) No (default)
+y/n&gt; n
 
 Generate a personal login token here: https://www.jottacloud.com/web/secure
 Login Token&gt; &lt;your token here&gt;
@@ -12535,9 +12735,8 @@ y/n&gt; y
 Please select the device to use. Normally this will be Jotta
 Choose a number from below, or type in an existing value
  1 &gt; DESKTOP-3H31129
- 2 &gt; fla1
- 3 &gt; Jotta
-Devices&gt; 3
+ 2 &gt; Jotta
+Devices&gt; 2
 Please select the mountpoint to user. Normally this will be Archive
 Choose a number from below, or type in an existing value
  1 &gt; Archive
@@ -12548,7 +12747,6 @@ Mountpoints&gt; 1
 --------------------
 [jotta]
 type = jottacloud
-user = 0xC4KE@gmail.com
 token = {........}
 device = Jotta
 mountpoint = Archive
@@ -12566,16 +12764,16 @@ y/e/d&gt; y</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 then creates a mountpoint for each folder you select for Backup. The web interface uses a special device called Jotta for the Archive and Sync mountpoints. In most cases you’ll want to use the Jotta/Archive device/mountpoint, however if you want to access files uploaded by any of the official clients rclone provides the option to select other devices and mountpoints during config.</p>
-<p>The built-in Jotta device may also contain several other mountpoints, such as: Latest, Links, Shared and Trash. 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-6">–fast-list</h3>
+<p>The official Jottacloud client registers a device for each computer you install it on, and then creates a mountpoint for each folder you select for Backup. The web interface uses a special device called Jotta for the Archive and Sync mountpoints. In most cases you'll want to use the Jotta/Archive device/mountpoint, however if you want to access files uploaded by any of the official clients rclone provides the option to select other devices and mountpoints during config.</p>
+<p>The built-in Jotta device may also contain several other mountpoints, such as: Latest, Links, Shared and Trash. 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-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>
 <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>
-<h3 id="modified-time-and-hashes-5">Modified time and hashes</h3>
+<h3 id="modified-time-and-hashes">Modified time 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 (wherever the <code>TMPDIR</code> environment variable points to) 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.</p>
-<h4 id="restricted-filename-characters-10">Restricted filename characters</h4>
+<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 (wherever the <code>TMPDIR</code> environment variable points to) 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.</p>
+<h4 id="restricted-filename-characters">Restricted filename characters</h4>
 <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>
@@ -12623,16 +12821,16 @@ y/e/d&gt; y</code></pre>
 </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-4">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-2">Versions</h3>
+<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">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">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>
-<h3 id="quota-information-1">Quota information</h3>
+<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 (unless it is unlimited) and the current usage.</p>
-<h3 id="advanced-options-16">Advanced Options</h3>
+<h3 id="advanced-options-2">Advanced Options</h3>
 <p>Here are the advanced options specific to jottacloud (Jottacloud).</p>
-<h4 id="jottacloud-md5-memory-limit">–jottacloud-md5-memory-limit</h4>
+<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>
 <ul>
 <li>Config: md5_memory_limit</li>
@@ -12640,7 +12838,7 @@ y/e/d&gt; y</code></pre>
 <li>Type: SizeSuffix</li>
 <li>Default: 10M</li>
 </ul>
-<h4 id="jottacloud-trashed-only">–jottacloud-trashed-only</h4>
+<h4 id="jottacloud-trashed-only">--jottacloud-trashed-only</h4>
 <p>Only show files that are in the trash. This will show trashed files in their original directory structure.</p>
 <ul>
 <li>Config: trashed_only</li>
@@ -12648,7 +12846,7 @@ y/e/d&gt; y</code></pre>
 <li>Type: bool</li>
 <li>Default: false</li>
 </ul>
-<h4 id="jottacloud-hard-delete">–jottacloud-hard-delete</h4>
+<h4 id="jottacloud-hard-delete">--jottacloud-hard-delete</h4>
 <p>Delete files permanently rather than putting them into the trash.</p>
 <ul>
 <li>Config: hard_delete</li>
@@ -12656,23 +12854,15 @@ y/e/d&gt; y</code></pre>
 <li>Type: bool</li>
 <li>Default: false</li>
 </ul>
-<h4 id="jottacloud-unlink">–jottacloud-unlink</h4>
-<p>Remove existing public link to file/folder with link command rather than creating. Default is false, meaning link command will create or retrieve public link.</p>
-<ul>
-<li>Config: unlink</li>
-<li>Env Var: RCLONE_JOTTACLOUD_UNLINK</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>
+<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>
 <ul>
 <li>Config: upload_resume_limit</li>
 <li>Env Var: RCLONE_JOTTACLOUD_UPLOAD_RESUME_LIMIT</li>
 <li>Type: SizeSuffix</li>
 <li>Default: 10M</li>
 </ul>
-<h4 id="jottacloud-encoding">–jottacloud-encoding</h4>
+<h4 id="jottacloud-encoding">--jottacloud-encoding</h4>
 <p>This sets 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>
 <ul>
@@ -12681,9 +12871,9 @@ y/e/d&gt; y</code></pre>
 <li>Type: MultiEncoder</li>
 <li>Default: Slash,LtGt,DoubleQuote,Colon,Question,Asterisk,Pipe,Del,Ctl,InvalidUtf8,Dot</li>
 </ul>
-<h3 id="limitations-10">Limitations</h3>
-<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>
+<h3 id="limitations-3">Limitations</h3>
+<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>
 <h3 id="troubleshooting">Troubleshooting</h3>
 <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>
@@ -12745,7 +12935,7 @@ y/e/d&gt; y</code></pre>
 <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 remote:backup</code></pre>
-<h4 id="restricted-filename-characters-11">Restricted filename characters</h4>
+<h4 id="restricted-filename-characters-1">Restricted filename characters</h4>
 <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>
@@ -12763,10 +12953,10 @@ y/e/d&gt; y</code></pre>
 </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-17">Standard Options</h3>
+<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-2">Standard Options</h3>
 <p>Here are the standard options specific to koofr (Koofr).</p>
-<h4 id="koofr-user">–koofr-user</h4>
+<h4 id="koofr-user">--koofr-user</h4>
 <p>Your Koofr user name</p>
 <ul>
 <li>Config: user</li>
@@ -12774,25 +12964,26 @@ y/e/d&gt; y</code></pre>
 <li>Type: string</li>
 <li>Default: ""</li>
 </ul>
-<h4 id="koofr-password">–koofr-password</h4>
+<h4 id="koofr-password">--koofr-password</h4>
 <p>Your Koofr 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>
 <ul>
 <li>Config: password</li>
 <li>Env Var: RCLONE_KOOFR_PASSWORD</li>
 <li>Type: string</li>
 <li>Default: ""</li>
 </ul>
-<h3 id="advanced-options-17">Advanced Options</h3>
+<h3 id="advanced-options-3">Advanced Options</h3>
 <p>Here are the advanced options specific to koofr (Koofr).</p>
-<h4 id="koofr-endpoint">–koofr-endpoint</h4>
+<h4 id="koofr-endpoint">--koofr-endpoint</h4>
 <p>The Koofr API endpoint to use</p>
 <ul>
 <li>Config: endpoint</li>
 <li>Env Var: RCLONE_KOOFR_ENDPOINT</li>
 <li>Type: string</li>
-<li>Default: “https://app.koofr.net”</li>
+<li>Default: "https://app.koofr.net"</li>
 </ul>
-<h4 id="koofr-mountid">–koofr-mountid</h4>
+<h4 id="koofr-mountid">--koofr-mountid</h4>
 <p>Mount ID of the mount to use. If omitted, the primary mount is used.</p>
 <ul>
 <li>Config: mountid</li>
@@ -12800,7 +12991,7 @@ y/e/d&gt; y</code></pre>
 <li>Type: string</li>
 <li>Default: ""</li>
 </ul>
-<h4 id="koofr-setmtime">–koofr-setmtime</h4>
+<h4 id="koofr-setmtime">--koofr-setmtime</h4>
 <p>Does the backend support setting modification time. Set this to false if you use a mount ID that points to a Dropbox or Amazon Drive backend.</p>
 <ul>
 <li>Config: setmtime</li>
@@ -12808,7 +12999,7 @@ y/e/d&gt; y</code></pre>
 <li>Type: bool</li>
 <li>Default: true</li>
 </ul>
-<h4 id="koofr-encoding">–koofr-encoding</h4>
+<h4 id="koofr-encoding">--koofr-encoding</h4>
 <p>This sets 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>
 <ul>
@@ -12817,15 +13008,15 @@ y/e/d&gt; y</code></pre>
 <li>Type: MultiEncoder</li>
 <li>Default: Slash,BackSlash,Del,Ctl,InvalidUtf8,Dot</li>
 </ul>
-<h3 id="limitations-11">Limitations</h3>
-<p>Note that Koofr is case insensitive so you can’t have a file called “Hello.doc” and one called “hello.doc”.</p>
+<h3 id="limitations-4">Limitations</h3>
+<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="mail.ru-cloud">Mail.ru Cloud</h2>
 <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/">Disk-O:</a>, available only on Windows. (Please note that official sites are in Russian)</p>
 <p>Currently it is recommended to disable 2FA on Mail.ru accounts intended for rclone until it gets eventually implemented.</p>
 <h3 id="features-highlights">Features highlights</h3>
 <ul>
 <li>Paths may be as deep as required, eg <code>remote:directory/subdirectory</code></li>
-<li>Files have a <code>last modified time</code> property, directories don’t</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>
@@ -12898,16 +13089,16 @@ y/e/d&gt; y</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 /home/local/directory remote:directory</code></pre>
-<h3 id="modified-time-9">Modified time</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>
+<pre><code>rclone sync -i /home/local/directory remote:directory</code></pre>
+<h3 id="modified-time-2">Modified time</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>
 <h3 id="hash-checksums">Hash checksums</h3>
 <p>Hash sums use 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. Hash sum of a larger file is computed as a SHA1 sum of the file data bytes concatenated with a decimal representation of the data length.</p>
-<h3 id="emptying-trash-1">Emptying Trash</h3>
+<h3 id="emptying-trash">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>
+<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 (quota) and the current usage.</p>
-<h4 id="restricted-filename-characters-12">Restricted filename characters</h4>
+<h4 id="restricted-filename-characters-2">Restricted filename characters</h4>
 <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>
@@ -12960,13 +13151,13 @@ y/e/d&gt; y</code></pre>
 </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="limitations-12">Limitations</h3>
+<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="limitations-5">Limitations</h3>
 <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>
-<h3 id="standard-options-18">Standard Options</h3>
+<p>Note that Mailru is case insensitive so you can't have a file called "Hello.doc" and one called "hello.doc".</p>
+<h3 id="standard-options-3">Standard Options</h3>
 <p>Here are the standard options specific to mailru (Mail.ru Cloud).</p>
-<h4 id="mailru-user">–mailru-user</h4>
+<h4 id="mailru-user">--mailru-user</h4>
 <p>User name (usually email)</p>
 <ul>
 <li>Config: user</li>
@@ -12974,16 +13165,17 @@ y/e/d&gt; y</code></pre>
 <li>Type: string</li>
 <li>Default: ""</li>
 </ul>
-<h4 id="mailru-pass">–mailru-pass</h4>
+<h4 id="mailru-pass">--mailru-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>
 <ul>
 <li>Config: pass</li>
 <li>Env Var: RCLONE_MAILRU_PASS</li>
 <li>Type: string</li>
 <li>Default: ""</li>
 </ul>
-<h4 id="mailru-speedup-enable">–mailru-speedup-enable</h4>
-<p>Skip full upload if there is another file with same data hash. 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. 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>
+<h4 id="mailru-speedup-enable">--mailru-speedup-enable</h4>
+<p>Skip full upload if there is another file with same data hash. 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. 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>
 <ul>
 <li>Config: speedup_enable</li>
 <li>Env Var: RCLONE_MAILRU_SPEEDUP_ENABLE</li>
@@ -12991,25 +13183,25 @@ y/e/d&gt; y</code></pre>
 <li>Default: true</li>
 <li>Examples:
 <ul>
-<li>“true”
+<li>"true"
 <ul>
 <li>Enable</li>
 </ul></li>
-<li>“false”
+<li>"false"
 <ul>
 <li>Disable</li>
 </ul></li>
 </ul></li>
 </ul>
-<h3 id="advanced-options-18">Advanced Options</h3>
+<h3 id="advanced-options-4">Advanced Options</h3>
 <p>Here are the advanced options specific to mailru (Mail.ru Cloud).</p>
-<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). Patterns are case insensitive and can contain ’*’ or ‘?’ meta characters.</p>
+<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). Patterns are case insensitive and can contain '*' or '?' meta characters.</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>Default: "<em>.mkv,</em>.avi,<em>.mp4,</em>.mp3,<em>.zip,</em>.gz,<em>.rar,</em>.pdf"</li>
 <li>Examples:
 <ul>
 <li>""
@@ -13020,17 +13212,17 @@ y/e/d&gt; y</code></pre>
 <ul>
 <li>All files will be attempted for speedup.</li>
 </ul></li>
-<li>“<em>.mkv,</em>.avi,<em>.mp4,</em>.mp3”
+<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”
+<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>
+<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 (because preliminary hashing can exhaust you RAM or disk space)</p>
 <ul>
 <li>Config: speedup_max_disk</li>
@@ -13039,21 +13231,21 @@ y/e/d&gt; y</code></pre>
 <li>Default: 3G</li>
 <li>Examples:
 <ul>
-<li>“0”
+<li>"0"
 <ul>
 <li>Completely disable speedup (put by hash).</li>
 </ul></li>
-<li>“1G”
+<li>"1G"
 <ul>
 <li>Files larger than 1Gb will be uploaded directly.</li>
 </ul></li>
-<li>“3G”
+<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>
+<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>
 <ul>
 <li>Config: speedup_max_memory</li>
@@ -13062,21 +13254,21 @@ y/e/d&gt; y</code></pre>
 <li>Default: 32M</li>
 <li>Examples:
 <ul>
-<li>“0”
+<li>"0"
 <ul>
 <li>Preliminary hashing will always be done in a temporary disk location.</li>
 </ul></li>
-<li>“32M”
+<li>"32M"
 <ul>
 <li>Do not dedicate more than 32Mb RAM for preliminary hashing.</li>
 </ul></li>
-<li>“256M”
+<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>
+<h4 id="mailru-check-hash">--mailru-check-hash</h4>
 <p>What should copy do if file checksum is mismatched or invalid</p>
 <ul>
 <li>Config: check_hash</li>
@@ -13085,25 +13277,25 @@ y/e/d&gt; y</code></pre>
 <li>Default: true</li>
 <li>Examples:
 <ul>
-<li>“true”
+<li>"true"
 <ul>
 <li>Fail with error.</li>
 </ul></li>
-<li>“false”
+<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. Defaults to “rclone/VERSION” or “–user-agent” provided on command line.</p>
+<h4 id="mailru-user-agent">--mailru-user-agent</h4>
+<p>HTTP user agent used internally by client. Defaults to "rclone/VERSION" or "--user-agent" provided on command line.</p>
 <ul>
 <li>Config: user_agent</li>
 <li>Env Var: RCLONE_MAILRU_USER_AGENT</li>
 <li>Type: string</li>
 <li>Default: ""</li>
 </ul>
-<h4 id="mailru-quirks">–mailru-quirks</h4>
+<h4 id="mailru-quirks">--mailru-quirks</h4>
 <p>Comma separated list of internal maintenance flags. 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 gzip insecure retry400</p>
 <ul>
 <li>Config: quirks</li>
@@ -13111,7 +13303,7 @@ y/e/d&gt; y</code></pre>
 <li>Type: string</li>
 <li>Default: ""</li>
 </ul>
-<h4 id="mailru-encoding">–mailru-encoding</h4>
+<h4 id="mailru-encoding">--mailru-encoding</h4>
 <p>This sets 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>
 <ul>
@@ -13171,9 +13363,9 @@ y/e/d&gt; y</code></pre>
 <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="modified-time-and-hashes-6">Modified time and hashes</h3>
+<h3 id="modified-time-and-hashes-1">Modified time and hashes</h3>
 <p>Mega does not support modification times or hashes yet.</p>
-<h4 id="restricted-filename-characters-13">Restricted filename characters</h4>
+<h4 id="restricted-filename-characters-3">Restricted filename characters</h4>
 <table>
 <thead>
 <tr class="header">
@@ -13195,25 +13387,25 @@ y/e/d&gt; y</code></pre>
 </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-2">Duplicated files</h3>
+<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">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>
-<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>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>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>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-19">Standard Options</h3>
+<h3 id="standard-options-4">Standard Options</h3>
 <p>Here are the standard options specific to mega (Mega).</p>
-<h4 id="mega-user">–mega-user</h4>
+<h4 id="mega-user">--mega-user</h4>
 <p>User name</p>
 <ul>
 <li>Config: user</li>
@@ -13221,17 +13413,18 @@ y/e/d&gt; y</code></pre>
 <li>Type: string</li>
 <li>Default: ""</li>
 </ul>
-<h4 id="mega-pass">–mega-pass</h4>
+<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>
 <ul>
 <li>Config: pass</li>
 <li>Env Var: RCLONE_MEGA_PASS</li>
 <li>Type: string</li>
 <li>Default: ""</li>
 </ul>
-<h3 id="advanced-options-19">Advanced Options</h3>
+<h3 id="advanced-options-5">Advanced Options</h3>
 <p>Here are the advanced options specific to mega (Mega).</p>
-<h4 id="mega-debug">–mega-debug</h4>
+<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>
 <ul>
@@ -13240,7 +13433,7 @@ y/e/d&gt; y</code></pre>
 <li>Type: bool</li>
 <li>Default: false</li>
 </ul>
-<h4 id="mega-hard-delete">–mega-hard-delete</h4>
+<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>
 <ul>
@@ -13249,7 +13442,7 @@ y/e/d&gt; y</code></pre>
 <li>Type: bool</li>
 <li>Default: false</li>
 </ul>
-<h4 id="mega-encoding">–mega-encoding</h4>
+<h4 id="mega-encoding">--mega-encoding</h4>
 <p>This sets 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>
 <ul>
@@ -13258,8 +13451,8 @@ y/e/d&gt; y</code></pre>
 <li>Type: MultiEncoder</li>
 <li>Default: Slash,InvalidUtf8,Dot</li>
 </ul>
-<h3 id="limitations-13">Limitations</h3>
-<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>
+<h3 id="limitations-6">Limitations</h3>
+<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>
 <h2 id="memory">Memory</h2>
 <p>The memory backend is an in RAM backend. It does not persist its data - use the local backend for that.</p>
@@ -13291,13 +13484,13 @@ 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, eg</p>
+<p>Because the memory backend isn't persistent it is most useful for testing or with an rclone server or rclone mount, eg</p>
 <pre><code>rclone mount :memory: /mnt/tmp
 rclone serve webdav :memory:
 rclone serve sftp :memory:</code></pre>
-<h3 id="modified-time-and-hashes-7">Modified time and hashes</h3>
+<h3 id="modified-time-and-hashes-2">Modified time and hashes</h3>
 <p>The memory backend supports MD5 hashes and modification times accurate to 1 nS.</p>
-<h4 id="restricted-filename-characters-14">Restricted filename characters</h4>
+<h4 id="restricted-filename-characters-4">Restricted filename characters</h4>
 <p>The memory backend replaces the <a href="https://rclone.org/overview/#restricted-characters">default restricted characters set</a>.</p>
 <h2 id="microsoft-azure-blob-storage">Microsoft Azure Blob Storage</h2>
 <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, eg <code>remote:container/path/to/dir</code>.</p>
@@ -13341,12 +13534,12 @@ y/e/d&gt; y</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 /home/local/directory remote:container</code></pre>
-<h3 id="fast-list-7">–fast-list</h3>
+<pre><code>rclone sync -i /home/local/directory remote:container</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>
-<h3 id="modified-time-10">Modified time</h3>
+<h3 id="modified-time-3">Modified time</h3>
 <p>The modified 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 overhead to using it.</p>
-<h3 id="restricted-filename-characters-15">Restricted filename characters</h3>
+<h3 id="restricted-filename-characters-5">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>
@@ -13386,7 +13579,7 @@ y/e/d&gt; y</code></pre>
 </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>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">Hashes</h3>
 <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, eg the local disk.</p>
 <h3 id="authenticating-with-azure-blob-storage">Authenticating with Azure Blob Storage</h3>
@@ -13402,17 +13595,17 @@ y/e/d&gt; y</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>
+<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>
-<h3 id="multipart-uploads-1">Multipart uploads</h3>
+<h3 id="multipart-uploads">Multipart uploads</h3>
 <p>Rclone supports multipart uploads with Azure Blob storage. Files bigger than 256MB will be uploaded using chunked upload by default.</p>
 <p>The files will be uploaded in parallel in 4MB chunks (by default). Note that these chunks are buffered in memory and there may be up to <code>--transfers</code> of them being uploaded at once.</p>
-<p>Files can’t be split into more than 50,000 chunks so by default, so the largest file that can be uploaded with 4MB chunk size is 195GB. Above this rclone will double the chunk size until it creates less than 50,000 chunks. By default this will mean a maximum file size of 3.2TB can be uploaded. This can be raised to 5TB using <code>--azureblob-chunk-size 100M</code>.</p>
-<p>Note that rclone doesn’t commit the block list until the end of the upload which means that there is a limit of 9.5TB of multipart uploads in progress as Azure won’t allow more than that amount of uncommitted blocks.</p>
-<h3 id="standard-options-20">Standard Options</h3>
+<p>Files can't be split into more than 50,000 chunks so by default, so the largest file that can be uploaded with 4MB chunk size is 195GB. Above this rclone will double the chunk size until it creates less than 50,000 chunks. By default this will mean a maximum file size of 3.2TB can be uploaded. This can be raised to 5TB using <code>--azureblob-chunk-size 100M</code>.</p>
+<p>Note that rclone doesn't commit the block list until the end of the upload which means that there is a limit of 9.5TB of multipart uploads in progress as Azure won't allow more than that amount of uncommitted blocks.</p>
+<h3 id="standard-options-5">Standard Options</h3>
 <p>Here are the standard options specific to azureblob (Microsoft Azure Blob Storage).</p>
-<h4 id="azureblob-account">–azureblob-account</h4>
+<h4 id="azureblob-account">--azureblob-account</h4>
 <p>Storage Account Name (leave blank to use SAS URL or Emulator)</p>
 <ul>
 <li>Config: account</li>
@@ -13420,7 +13613,7 @@ container/</code></pre>
 <li>Type: string</li>
 <li>Default: ""</li>
 </ul>
-<h4 id="azureblob-key">–azureblob-key</h4>
+<h4 id="azureblob-key">--azureblob-key</h4>
 <p>Storage Account Key (leave blank to use SAS URL or Emulator)</p>
 <ul>
 <li>Config: key</li>
@@ -13428,7 +13621,7 @@ container/</code></pre>
 <li>Type: string</li>
 <li>Default: ""</li>
 </ul>
-<h4 id="azureblob-sas-url">–azureblob-sas-url</h4>
+<h4 id="azureblob-sas-url">--azureblob-sas-url</h4>
 <p>SAS URL for container level access only (leave blank if using account/key or Emulator)</p>
 <ul>
 <li>Config: sas_url</li>
@@ -13436,17 +13629,17 @@ container/</code></pre>
 <li>Type: string</li>
 <li>Default: ""</li>
 </ul>
-<h4 id="azureblob-use-emulator">–azureblob-use-emulator</h4>
-<p>Uses local storage emulator if provided as ‘true’ (leave blank if using real azure storage endpoint)</p>
+<h4 id="azureblob-use-emulator">--azureblob-use-emulator</h4>
+<p>Uses local storage emulator if provided as 'true' (leave blank if using real azure storage endpoint)</p>
 <ul>
 <li>Config: use_emulator</li>
 <li>Env Var: RCLONE_AZUREBLOB_USE_EMULATOR</li>
 <li>Type: bool</li>
 <li>Default: false</li>
 </ul>
-<h3 id="advanced-options-20">Advanced Options</h3>
+<h3 id="advanced-options-6">Advanced Options</h3>
 <p>Here are the advanced options specific to azureblob (Microsoft Azure Blob Storage).</p>
-<h4 id="azureblob-endpoint">–azureblob-endpoint</h4>
+<h4 id="azureblob-endpoint">--azureblob-endpoint</h4>
 <p>Endpoint for the service Leave blank normally.</p>
 <ul>
 <li>Config: endpoint</li>
@@ -13454,7 +13647,7 @@ container/</code></pre>
 <li>Type: string</li>
 <li>Default: ""</li>
 </ul>
-<h4 id="azureblob-upload-cutoff">–azureblob-upload-cutoff</h4>
+<h4 id="azureblob-upload-cutoff">--azureblob-upload-cutoff</h4>
 <p>Cutoff for switching to chunked upload (&lt;= 256MB).</p>
 <ul>
 <li>Config: upload_cutoff</li>
@@ -13462,36 +13655,36 @@ container/</code></pre>
 <li>Type: SizeSuffix</li>
 <li>Default: 256M</li>
 </ul>
-<h4 id="azureblob-chunk-size">–azureblob-chunk-size</h4>
+<h4 id="azureblob-chunk-size">--azureblob-chunk-size</h4>
 <p>Upload chunk size (&lt;= 100MB).</p>
-<p>Note that this is stored in memory and there may be up to “–transfers” chunks stored at once in memory.</p>
+<p>Note that this is stored in memory and there may be up to "--transfers" chunks stored at once in memory.</p>
 <ul>
 <li>Config: chunk_size</li>
 <li>Env Var: RCLONE_AZUREBLOB_CHUNK_SIZE</li>
 <li>Type: SizeSuffix</li>
 <li>Default: 4M</li>
 </ul>
-<h4 id="azureblob-list-chunk">–azureblob-list-chunk</h4>
+<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>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>
 <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>
+<h4 id="azureblob-access-tier">--azureblob-access-tier</h4>
 <p>Access tier of blob: hot, cool or archive.</p>
 <p>Archived blobs can be restored by setting access tier to hot or cool. 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” or “Cool”.</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" or "Cool".</p>
 <ul>
 <li>Config: access_tier</li>
 <li>Env Var: RCLONE_AZUREBLOB_ACCESS_TIER</li>
 <li>Type: string</li>
 <li>Default: ""</li>
 </ul>
-<h4 id="azureblob-disable-checksum">–azureblob-disable-checksum</h4>
-<p>Don’t store MD5 checksum with object metadata.</p>
+<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>
 <ul>
 <li>Config: disable_checksum</li>
@@ -13499,7 +13692,7 @@ container/</code></pre>
 <li>Type: bool</li>
 <li>Default: false</li>
 </ul>
-<h4 id="azureblob-memory-pool-flush-time">–azureblob-memory-pool-flush-time</h4>
+<h4 id="azureblob-memory-pool-flush-time">--azureblob-memory-pool-flush-time</h4>
 <p>How often internal memory buffer pools will be flushed. Uploads which requires additional buffers (f.e multipart) will use memory pool for allocations. This option controls how often unused buffers will be removed from the pool.</p>
 <ul>
 <li>Config: memory_pool_flush_time</li>
@@ -13507,7 +13700,7 @@ container/</code></pre>
 <li>Type: Duration</li>
 <li>Default: 1m0s</li>
 </ul>
-<h4 id="azureblob-memory-pool-use-mmap">–azureblob-memory-pool-use-mmap</h4>
+<h4 id="azureblob-memory-pool-use-mmap">--azureblob-memory-pool-use-mmap</h4>
 <p>Whether to use mmap buffers in internal memory pool.</p>
 <ul>
 <li>Config: memory_pool_use_mmap</li>
@@ -13515,7 +13708,7 @@ container/</code></pre>
 <li>Type: bool</li>
 <li>Default: false</li>
 </ul>
-<h4 id="azureblob-encoding">–azureblob-encoding</h4>
+<h4 id="azureblob-encoding">--azureblob-encoding</h4>
 <p>This sets 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>
 <ul>
@@ -13524,7 +13717,7 @@ container/</code></pre>
 <li>Type: MultiEncoder</li>
 <li>Default: Slash,BackSlash,Del,Ctl,RightPeriod,InvalidUtf8</li>
 </ul>
-<h3 id="limitations-14">Limitations</h3>
+<h3 id="limitations-7">Limitations</h3>
 <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>
 <h3 id="azure-storage-emulator-support">Azure Storage Emulator Support</h3>
 <p>You can test rclone with storage emulator locally, to do this make sure azure storage emulator installed locally and set up a new remote with <code>rclone config</code> follow instructions described in introduction, set <code>use_emulator</code> config as <code>true</code>, you do not need to provide default account name or key if using emulator.</p>
@@ -13616,10 +13809,10 @@ y/e/d&gt; y</code></pre>
 <p>To copy a local directory to an OneDrive directory called backup</p>
 <pre><code>rclone copy /home/source remote:backup</code></pre>
 <h3 id="getting-your-own-client-id-and-key">Getting your own Client ID and Key</h3>
-<p>You can use your own Client ID if the default (<code>client_id</code> left blank) one doesn’t work for you or you see lots of throttling. The default Client ID and Key is shared by all rclone users when performing requests.</p>
+<p>You can use your own Client ID if the default (<code>client_id</code> left blank) one doesn't work for you or you see lots of throttling. The default Client ID and Key is shared by all rclone users when performing requests.</p>
 <p>If you are having problems with them (E.g., seeing a lot of throttling), you can get your own Client ID and Key by following the steps below:</p>
 <ol type="1">
-<li>Open https://portal.azure.com/#blade/Microsoft_AAD_RegisteredApps/ApplicationsListBlade, then click <code>New registration</code>.</li>
+<li>Open https://portal.azure.com/#blade/Microsoft_AAD_RegisteredApps/ApplicationsListBlade and then click <code>New registration</code>.</li>
 <li>Enter a name for your app, choose account type <code>Accounts in any organizational directory (Any Azure AD directory - Multitenant) and personal Microsoft accounts (e.g. Skype, Xbox)</code>, select <code>Web</code> in <code>Redirect URI</code> Enter <code>http://localhost:53682/</code> and click Register. Copy and keep the <code>Application (client) ID</code> under the app name for later use.</li>
 <li>Under <code>manage</code> select <code>Certificates &amp; secrets</code>, click <code>New client secret</code>. Copy and keep that secret for later use.</li>
 <li>Under <code>manage</code> select <code>API permissions</code>, click <code>Add a permission</code> and select <code>Microsoft Graph</code> then select <code>delegated permissions</code>.</li>
@@ -13630,7 +13823,7 @@ y/e/d&gt; y</code></pre>
 <p>OneDrive 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>OneDrive personal supports SHA1 type hashes. OneDrive for business and Sharepoint Server support <a href="https://docs.microsoft.com/en-us/onedrive/developer/code-snippets/quickxorhash">QuickXorHash</a>.</p>
 <p>For all types of OneDrive you can use the <code>--checksum</code> flag.</p>
-<h3 id="restricted-filename-characters-16">Restricted filename characters</h3>
+<h3 id="restricted-filename-characters-6">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>
@@ -13737,30 +13930,54 @@ y/e/d&gt; y</code></pre>
 </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="deleting-files-5">Deleting files</h3>
-<p>Any files you delete with rclone will end up in the trash. Microsoft doesn’t provide an API to permanently delete files, nor to empty the trash, so you will have to do that with one of Microsoft’s apps or via the OneDrive website.</p>
-<h3 id="standard-options-21">Standard Options</h3>
+<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="deleting-files-1">Deleting files</h3>
+<p>Any files you delete with rclone will end up in the trash. Microsoft doesn't provide an API to permanently delete files, nor to empty the trash, so you will have to do that with one of Microsoft's apps or via the OneDrive website.</p>
+<h3 id="standard-options-6">Standard Options</h3>
 <p>Here are the standard options specific to onedrive (Microsoft OneDrive).</p>
-<h4 id="onedrive-client-id">–onedrive-client-id</h4>
-<p>Microsoft App Client Id Leave blank normally.</p>
+<h4 id="onedrive-client-id">--onedrive-client-id</h4>
+<p>OAuth Client Id Leave blank normally.</p>
 <ul>
 <li>Config: client_id</li>
 <li>Env Var: RCLONE_ONEDRIVE_CLIENT_ID</li>
 <li>Type: string</li>
 <li>Default: ""</li>
 </ul>
-<h4 id="onedrive-client-secret">–onedrive-client-secret</h4>
-<p>Microsoft App Client Secret Leave blank normally.</p>
+<h4 id="onedrive-client-secret">--onedrive-client-secret</h4>
+<p>OAuth Client Secret Leave blank normally.</p>
 <ul>
 <li>Config: client_secret</li>
 <li>Env Var: RCLONE_ONEDRIVE_CLIENT_SECRET</li>
 <li>Type: string</li>
 <li>Default: ""</li>
 </ul>
-<h3 id="advanced-options-21">Advanced Options</h3>
+<h3 id="advanced-options-7">Advanced Options</h3>
 <p>Here are the advanced options specific to onedrive (Microsoft OneDrive).</p>
-<h4 id="onedrive-chunk-size">–onedrive-chunk-size</h4>
+<h4 id="onedrive-token">--onedrive-token</h4>
+<p>OAuth Access Token as a JSON blob.</p>
+<ul>
+<li>Config: token</li>
+<li>Env Var: RCLONE_ONEDRIVE_TOKEN</li>
+<li>Type: string</li>
+<li>Default: ""</li>
+</ul>
+<h4 id="onedrive-auth-url">--onedrive-auth-url</h4>
+<p>Auth server URL. Leave blank to use the provider defaults.</p>
+<ul>
+<li>Config: auth_url</li>
+<li>Env Var: RCLONE_ONEDRIVE_AUTH_URL</li>
+<li>Type: string</li>
+<li>Default: ""</li>
+</ul>
+<h4 id="onedrive-token-url">--onedrive-token-url</h4>
+<p>Token server url. Leave blank to use the provider defaults.</p>
+<ul>
+<li>Config: token_url</li>
+<li>Env Var: RCLONE_ONEDRIVE_TOKEN_URL</li>
+<li>Type: string</li>
+<li>Default: ""</li>
+</ul>
+<h4 id="onedrive-chunk-size">--onedrive-chunk-size</h4>
 <p>Chunk size to upload files with - must be multiple of 320k (327,680 bytes).</p>
 <p>Above this size files will be chunked - must be multiple of 320k (327,680 bytes) and should not exceed 250M (262,144,000 bytes) else you may encounter "Microsoft.SharePoint.Client.InvalidClientQueryException: The request message is too big." Note that the chunks will be buffered into memory.</p>
 <ul>
@@ -13769,7 +13986,7 @@ y/e/d&gt; y</code></pre>
 <li>Type: SizeSuffix</li>
 <li>Default: 10M</li>
 </ul>
-<h4 id="onedrive-drive-id">–onedrive-drive-id</h4>
+<h4 id="onedrive-drive-id">--onedrive-drive-id</h4>
 <p>The ID of the drive to use</p>
 <ul>
 <li>Config: drive_id</li>
@@ -13777,7 +13994,7 @@ y/e/d&gt; y</code></pre>
 <li>Type: string</li>
 <li>Default: ""</li>
 </ul>
-<h4 id="onedrive-drive-type">–onedrive-drive-type</h4>
+<h4 id="onedrive-drive-type">--onedrive-drive-type</h4>
 <p>The type of the drive ( personal | business | documentLibrary )</p>
 <ul>
 <li>Config: drive_type</li>
@@ -13785,25 +14002,37 @@ y/e/d&gt; y</code></pre>
 <li>Type: string</li>
 <li>Default: ""</li>
 </ul>
-<h4 id="onedrive-expose-onenote-files">–onedrive-expose-onenote-files</h4>
+<h4 id="onedrive-expose-onenote-files">--onedrive-expose-onenote-files</h4>
 <p>Set to make OneNote files show up in directory listings.</p>
-<p>By default rclone will hide OneNote files in directory listings because operations like “Open” and “Update” won’t work on them. But this behaviour may also prevent you from deleting them. If you want to delete OneNote files or otherwise want them to show up in directory listing, set this option.</p>
+<p>By default rclone will hide OneNote files in directory listings because operations like "Open" and "Update" won't work on them. But this behaviour may also prevent you from deleting them. If you want to delete OneNote files or otherwise want them to show up in directory listing, set this option.</p>
 <ul>
 <li>Config: expose_onenote_files</li>
 <li>Env Var: RCLONE_ONEDRIVE_EXPOSE_ONENOTE_FILES</li>
 <li>Type: bool</li>
 <li>Default: false</li>
 </ul>
-<h4 id="onedrive-server-side-across-configs">–onedrive-server-side-across-configs</h4>
+<h4 id="onedrive-server-side-across-configs">--onedrive-server-side-across-configs</h4>
 <p>Allow server side operations (eg copy) to work across different onedrive configs.</p>
-<p>This can be useful if you wish to do a server side copy between two different Onedrives. 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>This can be useful if you wish to do a server side copy between two different Onedrives. Note that this isn't enabled by default because it isn't easy to tell if it will work between any two configurations.</p>
 <ul>
 <li>Config: server_side_across_configs</li>
 <li>Env Var: RCLONE_ONEDRIVE_SERVER_SIDE_ACROSS_CONFIGS</li>
 <li>Type: bool</li>
 <li>Default: false</li>
 </ul>
-<h4 id="onedrive-encoding">–onedrive-encoding</h4>
+<h4 id="onedrive-no-versions">--onedrive-no-versions</h4>
+<p>Remove all versions on modifying operations</p>
+<p>Onedrive for business creates versions when rclone uploads new files overwriting an existing one and when it sets the modification time.</p>
+<p>These versions take up space out of the quota.</p>
+<p>This flag checks for versions after file upload and setting modification time and removes all but the last version.</p>
+<p><strong>NB</strong> Onedrive personal can't currently delete versions so don't use this flag there.</p>
+<ul>
+<li>Config: no_versions</li>
+<li>Env Var: RCLONE_ONEDRIVE_NO_VERSIONS</li>
+<li>Type: bool</li>
+<li>Default: false</li>
+</ul>
+<h4 id="onedrive-encoding">--onedrive-encoding</h4>
 <p>This sets 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>
 <ul>
@@ -13812,59 +14041,70 @@ y/e/d&gt; y</code></pre>
 <li>Type: MultiEncoder</li>
 <li>Default: Slash,LtGt,DoubleQuote,Colon,Question,Asterisk,Pipe,Hash,Percent,BackSlash,Del,Ctl,LeftSpace,LeftTilde,RightSpace,RightPeriod,InvalidUtf8,Dot</li>
 </ul>
-<h3 id="limitations-15">Limitations</h3>
+<h3 id="limitations-8">Limitations</h3>
+<p>If you don't use rclone for 90 days the refresh token will expire. This will result in authorization problems. This is easy to fix by running the <code>rclone config reconnect remote:</code> command to get a new token and refresh token.</p>
 <h4 id="naming">Naming</h4>
-<p>Note that OneDrive 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 OneDrive file names. These can’t occur on Windows platforms, but on non-Windows platforms they are common. Rclone will map these names to and from an identical looking unicode equivalent. For example if a file has a <code>?</code> in it will be mapped to <code>？</code> instead.</p>
+<p>Note that OneDrive 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 OneDrive file names. These can't occur on Windows platforms, but on non-Windows platforms they are common. Rclone will map these names to and from an identical looking unicode equivalent. For example if a file has a <code>?</code> in it will be mapped to <code>？</code> instead.</p>
 <h4 id="file-sizes">File sizes</h4>
-<p>The largest allowed file sizes are 15GB for OneDrive for Business and 100GB for OneDrive Personal (Updated 19 May 2020). Source: https://support.office.com/en-us/article/upload-photos-and-files-to-onedrive-b00ad3fe-6643-4b16-9212-de00ef02b586</p>
+<p>The largest allowed file size is 100GB for both OneDrive Personal and OneDrive for Business <a href="https://support.microsoft.com/en-us/office/invalid-file-names-and-file-types-in-onedrive-and-sharepoint-64883a5d-228e-48f5-b3d2-eb39e07630fa?ui=en-us&amp;rs=en-us&amp;ad=us#individualfilesize">(Updated 17 June 2020)</a>.</p>
 <h4 id="path-length">Path length</h4>
 <p>The entire path, including the file name, must contain fewer than 400 characters for OneDrive, OneDrive for Business and SharePoint Online. If you are encrypting file and folder names with rclone, you may want to pay attention to this limitation because the encrypted names are typically longer than the original ones.</p>
 <h4 id="number-of-files">Number of files</h4>
 <p>OneDrive seems to be OK with at least 50,000 files in a folder, but at 100,000 rclone will get errors listing the directory like <code>couldn’t list files: UnknownError:</code>. See <a href="https://github.com/rclone/rclone/issues/2707">#2707</a> for more info.</p>
 <p>An official document about the limitations for different types of OneDrive can be found <a href="https://support.office.com/en-us/article/invalid-file-names-and-file-types-in-onedrive-onedrive-for-business-and-sharepoint-64883a5d-228e-48f5-b3d2-eb39e07630fa">here</a>.</p>
-<h3 id="versioning-issue">Versioning issue</h3>
-<p>Every change in OneDrive causes the service to create a new version. This counts against a users quota. For example changing the modification time of a file creates a second version, so the file is using twice the space.</p>
-<p>The <code>copy</code> is the only rclone command affected by this as we copy the file and then afterwards set the modification time to match the source file.</p>
-<p><strong>Note</strong>: Starting October 2018, users will no longer be able to disable versioning by default. This is because Microsoft has brought an <a href="https://techcommunity.microsoft.com/t5/Microsoft-OneDrive-Blog/New-Updates-to-OneDrive-and-SharePoint-Team-Site-Versioning/ba-p/204390">update</a> to the mechanism. To change this new default setting, a PowerShell command is required to be run by a SharePoint admin. If you are an admin, you can run these commands in PowerShell to change that setting:</p>
+<h3 id="versions-1">Versions</h3>
+<p>Every change in a file OneDrive causes the service to create a new version of the the file. This counts against a users quota. For example changing the modification time of a file creates a second version, so the file apparently uses twice the space.</p>
+<p>For example the <code>copy</code> command is affected by this as rclone copies the file and then afterwards sets the modification time to match the source file which uses another version.</p>
+<p>You can use the <code>rclone cleanup</code> command (see below) to remove all old versions.</p>
+<p>Or you can set the <code>no_versions</code> parameter to <code>true</code> and rclone will remove versions after operations which create new versions. This takes extra transactions so only enable it if you need it.</p>
+<p><strong>Note</strong> At the time of writing Onedrive Personal creates versions (but not for setting the modification time) but the API for removing them returns "API not found" so cleanup and <code>no_versions</code> should not be used on Onedrive Personal.</p>
+<h3 id="disabling-versioning">Disabling versioning</h3>
+<p>Starting October 2018, users will no longer be able to disable versioning by default. This is because Microsoft has brought an <a href="https://techcommunity.microsoft.com/t5/Microsoft-OneDrive-Blog/New-Updates-to-OneDrive-and-SharePoint-Team-Site-Versioning/ba-p/204390">update</a> to the mechanism. To change this new default setting, a PowerShell command is required to be run by a SharePoint admin. If you are an admin, you can run these commands in PowerShell to change that setting:</p>
 <ol type="1">
-<li><code>Install-Module -Name Microsoft.Online.SharePoint.PowerShell</code> (in case you haven’t installed this already)</li>
+<li><code>Install-Module -Name Microsoft.Online.SharePoint.PowerShell</code> (in case you haven't installed this already)</li>
 <li><code>Import-Module Microsoft.Online.SharePoint.PowerShell -DisableNameChecking</code></li>
 <li><code>Connect-SPOService -Url https://YOURSITE-admin.sharepoint.com -Credential YOU@YOURSITE.COM</code> (replacing <code>YOURSITE</code>, <code>YOU</code>, <code>YOURSITE.COM</code> with the actual values; this will prompt for your credentials)</li>
 <li><code>Set-SPOTenant -EnableMinimumVersionRequirement $False</code></li>
 <li><code>Disconnect-SPOService</code> (to disconnect from the server)</li>
 </ol>
-<p><em>Below are the steps for normal users to disable versioning. If you don’t see the “No Versioning” option, make sure the above requirements are met.</em></p>
+<p><em>Below are the steps for normal users to disable versioning. If you don't see the "No Versioning" option, make sure the above requirements are met.</em></p>
 <p>User <a href="https://github.com/Weropol">Weropol</a> has found a method to disable versioning on OneDrive</p>
 <ol type="1">
 <li>Open the settings menu by clicking on the gear symbol at the top of the OneDrive Business page.</li>
 <li>Click Site settings.</li>
 <li>Once on the Site settings page, navigate to Site Administration &gt; Site libraries and lists.</li>
-<li>Click Customize “Documents”.</li>
+<li>Click Customize "Documents".</li>
 <li>Click General Settings &gt; Versioning Settings.</li>
 <li>Under Document Version History select the option No versioning. Note: This will disable the creation of new file versions, but will not remove any previous versions. Your documents are safe.</li>
 <li>Apply the changes by clicking OK.</li>
-<li>Use rclone to upload or modify files. (I also use the –no-update-modtime flag)</li>
+<li>Use rclone to upload or modify files. (I also use the --no-update-modtime flag)</li>
 <li>Restore the versioning settings after using rclone. (Optional)</li>
 </ol>
+<h3 id="cleanup">Cleanup</h3>
+<p>OneDrive supports <code>rclone cleanup</code> which causes rclone to look through every file under the path supplied and delete all version but the current version. Because this involves traversing all the files, then querying each file for versions it can be quite slow. Rclone does <code>--checkers</code> tests in parallel. The command also supports <code>-i</code> which is a great way to see what it would do.</p>
+<pre><code>rclone cleanup -i remote:path/subdir # interactively remove all old version for path/subdir
+rclone cleanup remote:path/subdir    # unconditionally remove all old version for path/subdir</code></pre>
+<p><strong>NB</strong> Onedrive personal can't currently delete versions</p>
 <h3 id="troubleshooting-1">Troubleshooting</h3>
 <h4 id="unexpected-file-sizehash-differences-on-sharepoint">Unexpected file size/hash differences on Sharepoint</h4>
-<p>It is a <a href="https://github.com/OneDrive/onedrive-api-docs/issues/935#issuecomment-441741631">known</a> issue that Sharepoint (not OneDrive or OneDrive for Business) silently modifies uploaded files, mainly Office files (.docx, .xlsx, etc.), causing file size and hash checks to fail. To use rclone with such affected files on Sharepoint, you may disable these checks with the following command line arguments:</p>
+<p>It is a <a href="https://github.com/OneDrive/onedrive-api-docs/issues/935#issuecomment-441741631">known</a> issue that Sharepoint (not OneDrive or OneDrive for Business) silently modifies uploaded files, mainly Office files (.docx, .xlsx, etc.), causing file size and hash checks to fail. There are also other situations that will cause OneDrive to report inconsistent file sizes. To use rclone with such affected files on Sharepoint, you may disable these checks with the following command line arguments:</p>
 <pre><code>--ignore-checksum --ignore-size</code></pre>
-<h4 id="replacingdeleting-existing-files-on-sharepoint-gets-item-not-found">Replacing/deleting existing files on Sharepoint gets “item not found”</h4>
-<p>It is a <a href="https://github.com/OneDrive/onedrive-api-docs/issues/1068">known</a> issue that Sharepoint (not OneDrive or OneDrive for Business) may return “item not found” errors when users try to replace or delete uploaded files; this seems to mainly affect Office files (.docx, .xlsx, etc.). As a workaround, you may use the <code>--backup-dir &lt;BACKUP_DIR&gt;</code> command line argument so rclone moves the files to be replaced/deleted into a given backup directory (instead of directly replacing/deleting them). For example, to instruct rclone to move the files into the directory <code>rclone-backup-dir</code> on backend <code>mysharepoint</code>, you may use:</p>
+<p>Alternatively, if you have write access to the OneDrive files, it may be possible to fix this problem for certain files, by attempting the steps below. Open the web interface for <a href="https://onedrive.live.com">OneDrive</a> and find the affected files (which will be in the error messages/log for rclone). Simply click on each of these files, causing OneDrive to open them on the web. This will cause each file to be converted in place to a format that is functionally equivalent but which will no longer trigger the size discrepancy. Once all problematic files are converted you will no longer need the ignore options above.</p>
+<h4 id="replacingdeleting-existing-files-on-sharepoint-gets-item-not-found">Replacing/deleting existing files on Sharepoint gets "item not found"</h4>
+<p>It is a <a href="https://github.com/OneDrive/onedrive-api-docs/issues/1068">known</a> issue that Sharepoint (not OneDrive or OneDrive for Business) may return "item not found" errors when users try to replace or delete uploaded files; this seems to mainly affect Office files (.docx, .xlsx, etc.). As a workaround, you may use the <code>--backup-dir &lt;BACKUP_DIR&gt;</code> command line argument so rclone moves the files to be replaced/deleted into a given backup directory (instead of directly replacing/deleting them). For example, to instruct rclone to move the files into the directory <code>rclone-backup-dir</code> on backend <code>mysharepoint</code>, you may use:</p>
 <pre><code>--backup-dir mysharepoint:rclone-backup-dir</code></pre>
 <h4 id="access_denied-aadsts65005">access_denied (AADSTS65005)</h4>
 <pre><code>Error: access_denied
 Code: AADSTS65005
 Description: Using application &#39;rclone&#39; is currently not supported for your organization [YOUR_ORGANIZATION] because it is in an unmanaged state. An administrator needs to claim ownership of the company by DNS validation of [YOUR_ORGANIZATION] before the application rclone can be provisioned.</code></pre>
-<p>This means that rclone can’t use the OneDrive for Business API with your account. You can’t do much about it, maybe write an email to your admins.</p>
+<p>This means that rclone can't use the OneDrive for Business API with your account. You can't do much about it, maybe write an email to your admins.</p>
 <p>However, there are other ways to interact with your OneDrive account. Have a look at the webdav backend: https://rclone.org/webdav/#sharepoint</p>
 <h4 id="invalid_grant-aadsts50076">invalid_grant (AADSTS50076)</h4>
 <pre><code>Error: invalid_grant
 Code: AADSTS50076
 Description: Due to a configuration change made by your administrator, or because you moved to a new location, you must use multi-factor authentication to access &#39;...&#39;.</code></pre>
-<p>If you see the error above after enabling multi-factor authentication for your account, you can fix it by refreshing your OAuth refresh token. To do that, run <code>rclone config</code>, and choose to edit your OneDrive backend. Then, you don’t need to actually make any changes until you reach this question: <code>Already have a token - refresh?</code>. For this question, answer <code>y</code> and go through the process to refresh your token, just like the first time the backend is configured. After this, rclone should work again for this backend.</p>
+<p>If you see the error above after enabling multi-factor authentication for your account, you can fix it by refreshing your OAuth refresh token. To do that, run <code>rclone config</code>, and choose to edit your OneDrive backend. Then, you don't need to actually make any changes until you reach this question: <code>Already have a token - refresh?</code>. For this question, answer <code>y</code> and go through the process to refresh your token, just like the first time the backend is configured. After this, rclone should work again for this backend.</p>
 <h2 id="opendrive">OpenDrive</h2>
 <p>Paths are specified as <code>remote:path</code></p>
 <p>Paths may be as deep as required, eg <code>remote:directory/subdirectory</code>.</p>
@@ -13908,9 +14148,9 @@ y/e/d&gt; y</code></pre>
 <pre><code>rclone ls remote:</code></pre>
 <p>To copy a local directory to an OpenDrive directory called backup</p>
 <pre><code>rclone copy /home/source remote:backup</code></pre>
-<h3 id="modified-time-and-md5sums-1">Modified time and MD5SUMs</h3>
+<h3 id="modified-time-and-md5sums">Modified time and MD5SUMs</h3>
 <p>OpenDrive 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>
-<h4 id="restricted-filename-characters-17">Restricted filename characters</h4>
+<h4 id="restricted-filename-characters-7">Restricted filename characters</h4>
 <table>
 <thead>
 <tr class="header">
@@ -14009,10 +14249,10 @@ y/e/d&gt; y</code></pre>
 </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-22">Standard Options</h3>
+<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 opendrive (OpenDrive).</p>
-<h4 id="opendrive-username">–opendrive-username</h4>
+<h4 id="opendrive-username">--opendrive-username</h4>
 <p>Username</p>
 <ul>
 <li>Config: username</li>
@@ -14020,17 +14260,18 @@ y/e/d&gt; y</code></pre>
 <li>Type: string</li>
 <li>Default: ""</li>
 </ul>
-<h4 id="opendrive-password">–opendrive-password</h4>
+<h4 id="opendrive-password">--opendrive-password</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>
 <ul>
 <li>Config: password</li>
 <li>Env Var: RCLONE_OPENDRIVE_PASSWORD</li>
 <li>Type: string</li>
 <li>Default: ""</li>
 </ul>
-<h3 id="advanced-options-22">Advanced Options</h3>
+<h3 id="advanced-options-8">Advanced Options</h3>
 <p>Here are the advanced options specific to opendrive (OpenDrive).</p>
-<h4 id="opendrive-encoding">–opendrive-encoding</h4>
+<h4 id="opendrive-encoding">--opendrive-encoding</h4>
 <p>This sets 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>
 <ul>
@@ -14039,7 +14280,7 @@ y/e/d&gt; y</code></pre>
 <li>Type: MultiEncoder</li>
 <li>Default: Slash,LtGt,DoubleQuote,Colon,Question,Asterisk,Pipe,BackSlash,LeftSpace,LeftCrLfHtVt,RightSpace,RightCrLfHtVt,InvalidUtf8,Dot</li>
 </ul>
-<h4 id="opendrive-chunk-size">–opendrive-chunk-size</h4>
+<h4 id="opendrive-chunk-size">--opendrive-chunk-size</h4>
 <p>Files will be uploaded in chunks this size.</p>
 <p>Note that these chunks are buffered in memory so increasing them will increase memory use.</p>
 <ul>
@@ -14048,9 +14289,9 @@ y/e/d&gt; y</code></pre>
 <li>Type: SizeSuffix</li>
 <li>Default: 10M</li>
 </ul>
-<h3 id="limitations-16">Limitations</h3>
-<p>Note that OpenDrive 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 OpenDrive file names. These can’t occur on Windows platforms, but on non-Windows platforms they are common. Rclone will map these names to and from an identical looking unicode equivalent. For example if a file has a <code>?</code> in it will be mapped to <code>？</code> instead.</p>
+<h3 id="limitations-9">Limitations</h3>
+<p>Note that OpenDrive 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 OpenDrive file names. These can't occur on Windows platforms, but on non-Windows platforms they are common. Rclone will map these names to and from an identical looking unicode equivalent. For example if a file has a <code>?</code> in it will be mapped to <code>？</code> instead.</p>
 <h2 id="qingstor">QingStor</h2>
 <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, eg <code>remote:bucket/path/to/dir</code>.</p>
 <p>Here is an example of making an QingStor configuration. First run</p>
@@ -14119,15 +14360,15 @@ y/e/d&gt; y</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 /home/local/directory remote:bucket</code></pre>
-<h3 id="fast-list-8">–fast-list</h3>
+<pre><code>rclone sync -i /home/local/directory remote:bucket</code></pre>
+<h3 id="fast-list-4">--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="multipart-uploads-2">Multipart uploads</h3>
-<p>rclone supports multipart uploads with QingStor which means that it can upload files bigger than 5GB. Note that files uploaded with multipart upload don’t have an MD5SUM.</p>
+<h3 id="multipart-uploads-1">Multipart uploads</h3>
+<p>rclone supports multipart uploads with QingStor which means that it can upload files bigger than 5GB. Note that files uploaded with multipart upload don't have an MD5SUM.</p>
 <p>Note that incomplete multipart uploads older than 24 hours can be removed with <code>rclone cleanup remote:bucket</code> just for one bucket <code>rclone cleanup remote:</code> for all buckets. QingStor does not ever remove incomplete multipart uploads so it may be necessary to run this from time to time.</p>
 <h3 id="buckets-and-zone">Buckets and Zone</h3>
 <p>With QingStor you can list buckets (<code>rclone lsd</code>) using any zone, but you can only access the content of a bucket from the zone it was created in. If you attempt to access a bucket from the wrong zone, you will get an error, <code>incorrect zone, the bucket is not in 'XXX' zone</code>.</p>
-<h3 id="authentication-5">Authentication</h3>
+<h3 id="authentication-4">Authentication</h3>
 <p>There are two ways to supply <code>rclone</code> with a set of QingStor credentials. In order of precedence:</p>
 <ul>
 <li>Directly in the rclone configuration file (as configured by <code>rclone config</code>)
@@ -14144,12 +14385,12 @@ y/e/d&gt; y</code></pre>
 </ul></li>
 </ul></li>
 </ul>
-<h3 id="restricted-filename-characters-18">Restricted filename characters</h3>
+<h3 id="restricted-filename-characters-8">Restricted filename characters</h3>
 <p>The control characters 0x00-0x1F and / are replaced as in the <a href="https://rclone.org/overview/#restricted-characters">default restricted characters set</a>. Note that 0x7F is not 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="standard-options-23">Standard Options</h3>
+<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-8">Standard Options</h3>
 <p>Here are the standard options specific to qingstor (QingCloud Object Storage).</p>
-<h4 id="qingstor-env-auth">–qingstor-env-auth</h4>
+<h4 id="qingstor-env-auth">--qingstor-env-auth</h4>
 <p>Get QingStor credentials from runtime. Only applies if access_key_id and secret_access_key is blank.</p>
 <ul>
 <li>Config: env_auth</li>
@@ -14158,17 +14399,17 @@ y/e/d&gt; y</code></pre>
 <li>Default: false</li>
 <li>Examples:
 <ul>
-<li>“false”
+<li>"false"
 <ul>
 <li>Enter QingStor credentials in the next step</li>
 </ul></li>
-<li>“true”
+<li>"true"
 <ul>
 <li>Get QingStor credentials from the environment (env vars or IAM)</li>
 </ul></li>
 </ul></li>
 </ul>
-<h4 id="qingstor-access-key-id">–qingstor-access-key-id</h4>
+<h4 id="qingstor-access-key-id">--qingstor-access-key-id</h4>
 <p>QingStor Access Key ID Leave blank for anonymous access or runtime credentials.</p>
 <ul>
 <li>Config: access_key_id</li>
@@ -14176,7 +14417,7 @@ y/e/d&gt; y</code></pre>
 <li>Type: string</li>
 <li>Default: ""</li>
 </ul>
-<h4 id="qingstor-secret-access-key">–qingstor-secret-access-key</h4>
+<h4 id="qingstor-secret-access-key">--qingstor-secret-access-key</h4>
 <p>QingStor Secret Access Key (password) Leave blank for anonymous access or runtime credentials.</p>
 <ul>
 <li>Config: secret_access_key</li>
@@ -14184,16 +14425,16 @@ y/e/d&gt; y</code></pre>
 <li>Type: string</li>
 <li>Default: ""</li>
 </ul>
-<h4 id="qingstor-endpoint">–qingstor-endpoint</h4>
-<p>Enter an endpoint URL to connection QingStor API. Leave blank will use the default value “https://qingstor.com:443”</p>
+<h4 id="qingstor-endpoint">--qingstor-endpoint</h4>
+<p>Enter an endpoint URL to connection QingStor API. Leave blank will use the default value "https://qingstor.com:443"</p>
 <ul>
 <li>Config: endpoint</li>
 <li>Env Var: RCLONE_QINGSTOR_ENDPOINT</li>
 <li>Type: string</li>
 <li>Default: ""</li>
 </ul>
-<h4 id="qingstor-zone">–qingstor-zone</h4>
-<p>Zone to connect to. Default is “pek3a”.</p>
+<h4 id="qingstor-zone">--qingstor-zone</h4>
+<p>Zone to connect to. Default is "pek3a".</p>
 <ul>
 <li>Config: zone</li>
 <li>Env Var: RCLONE_QINGSTOR_ZONE</li>
@@ -14201,26 +14442,26 @@ y/e/d&gt; y</code></pre>
 <li>Default: ""</li>
 <li>Examples:
 <ul>
-<li>“pek3a”
+<li>"pek3a"
 <ul>
 <li>The Beijing (China) Three Zone</li>
 <li>Needs location constraint pek3a.</li>
 </ul></li>
-<li>“sh1a”
+<li>"sh1a"
 <ul>
 <li>The Shanghai (China) First Zone</li>
 <li>Needs location constraint sh1a.</li>
 </ul></li>
-<li>“gd2a”
+<li>"gd2a"
 <ul>
 <li>The Guangdong (China) Second Zone</li>
 <li>Needs location constraint gd2a.</li>
 </ul></li>
 </ul></li>
 </ul>
-<h3 id="advanced-options-23">Advanced Options</h3>
+<h3 id="advanced-options-9">Advanced Options</h3>
 <p>Here are the advanced options specific to qingstor (QingCloud Object Storage).</p>
-<h4 id="qingstor-connection-retries">–qingstor-connection-retries</h4>
+<h4 id="qingstor-connection-retries">--qingstor-connection-retries</h4>
 <p>Number of connection retries.</p>
 <ul>
 <li>Config: connection_retries</li>
@@ -14228,7 +14469,7 @@ y/e/d&gt; y</code></pre>
 <li>Type: int</li>
 <li>Default: 3</li>
 </ul>
-<h4 id="qingstor-upload-cutoff">–qingstor-upload-cutoff</h4>
+<h4 id="qingstor-upload-cutoff">--qingstor-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 5GB.</p>
 <ul>
@@ -14237,10 +14478,10 @@ y/e/d&gt; y</code></pre>
 <li>Type: SizeSuffix</li>
 <li>Default: 200M</li>
 </ul>
-<h4 id="qingstor-chunk-size">–qingstor-chunk-size</h4>
+<h4 id="qingstor-chunk-size">--qingstor-chunk-size</h4>
 <p>Chunk size to use for uploading.</p>
 <p>When uploading files larger than upload_cutoff they will be uploaded as multipart uploads using this chunk size.</p>
-<p>Note that “–qingstor-upload-concurrency” chunks of this size are buffered in memory per transfer.</p>
+<p>Note that "--qingstor-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>
 <ul>
 <li>Config: chunk_size</li>
@@ -14248,7 +14489,7 @@ y/e/d&gt; y</code></pre>
 <li>Type: SizeSuffix</li>
 <li>Default: 4M</li>
 </ul>
-<h4 id="qingstor-upload-concurrency">–qingstor-upload-concurrency</h4>
+<h4 id="qingstor-upload-concurrency">--qingstor-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>NB if you set this to &gt; 1 then the checksums of multpart uploads become corrupted (the uploads themselves are not corrupted though).</p>
@@ -14259,7 +14500,7 @@ y/e/d&gt; y</code></pre>
 <li>Type: int</li>
 <li>Default: 1</li>
 </ul>
-<h4 id="qingstor-encoding">–qingstor-encoding</h4>
+<h4 id="qingstor-encoding">--qingstor-encoding</h4>
 <p>This sets 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>
 <ul>
@@ -14377,7 +14618,7 @@ y/e/d&gt; y</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 /home/local/directory remote:container</code></pre>
+<pre><code>rclone sync -i /home/local/directory remote:container</code></pre>
 <h3 id="configuration-from-an-openstack-credentials-file">Configuration from an OpenStack credentials file</h3>
 <p>An OpenStack credentials file typically looks something something like this (without the comments)</p>
 <pre><code>export OS_AUTH_URL=https://a.provider.net/v2.0
@@ -14402,21 +14643,21 @@ tenant = $OS_TENANT_NAME</code></pre>
 <p>When you run through the config, make sure you choose <code>true</code> for <code>env_auth</code> and leave everything else blank.</p>
 <p>rclone will then set any empty config parameters from the environment using standard OpenStack environment variables. There is <a href="https://godoc.org/github.com/ncw/swift#Connection.ApplyEnvironment">a list of the variables</a> in the docs for the swift library.</p>
 <h3 id="using-an-alternate-authentication-method">Using an alternate authentication method</h3>
-<p>If your OpenStack installation uses a non-standard authentication method that might not be yet supported by rclone or the underlying swift library, you can authenticate externally (e.g. calling manually the <code>openstack</code> commands to get a token). Then, you just need to pass the two configuration variables <code>auth_token</code> and <code>storage_url</code>. If they are both provided, the other variables are ignored. rclone will not try to authenticate but instead assume it is already authenticated and use these two variables to access the OpenStack installation.</p>
+<p>If your OpenStack installation uses a non-standard authentication method that might not be yet supported by rclone or the underlying swift library, you can authenticate externally (e.g. calling manually the <code>openstack</code> commands to get a token). Then, you just need to pass the two configuration variables <code>auth_token</code> and <code>storage_url</code>. If they are both provided, the other variables are ignored. rclone will not try to authenticate but instead assume it is already authenticated and use these two variables to access the OpenStack installation.</p>
 <h4 id="using-rclone-without-a-config-file">Using rclone without a config file</h4>
 <p>You can use rclone with swift without a config file, if desired, like this:</p>
 <pre><code>source openstack-credentials-file
 export RCLONE_CONFIG_MYREMOTE_TYPE=swift
 export RCLONE_CONFIG_MYREMOTE_ENV_AUTH=true
 rclone lsd myremote:</code></pre>
-<h3 id="fast-list-9">–fast-list</h3>
+<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="update-and-use-server-modtime-1">–update and –use-server-modtime</h3>
+<h3 id="update-and---use-server-modtime">--update and --use-server-modtime</h3>
 <p>As noted below, the modified time is stored on metadata on the object. It 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 because it requires an extra API call to retrieve the metadata.</p>
-<p>For many operations, the time the object was last uploaded to the remote is sufficient to determine if it is “dirty”. By using <code>--update</code> along with <code>--use-server-modtime</code>, you can avoid the extra API call and simply upload files whose local modtime is newer than the time it was last uploaded.</p>
-<h3 id="standard-options-24">Standard Options</h3>
+<p>For many operations, the time the object was last uploaded to the remote is sufficient to determine if it is "dirty". By using <code>--update</code> along with <code>--use-server-modtime</code>, you can avoid the extra API call and simply upload files whose local modtime is newer than the time it was last uploaded.</p>
+<h3 id="standard-options-9">Standard Options</h3>
 <p>Here are the standard options specific to swift (OpenStack Swift (Rackspace Cloud Files, Memset Memstore, OVH)).</p>
-<h4 id="swift-env-auth">–swift-env-auth</h4>
+<h4 id="swift-env-auth">--swift-env-auth</h4>
 <p>Get swift credentials from environment variables in standard OpenStack form.</p>
 <ul>
 <li>Config: env_auth</li>
@@ -14425,17 +14666,17 @@ rclone lsd myremote:</code></pre>
 <li>Default: false</li>
 <li>Examples:
 <ul>
-<li>“false”
+<li>"false"
 <ul>
 <li>Enter swift credentials in the next step</li>
 </ul></li>
-<li>“true”
+<li>"true"
 <ul>
 <li>Get swift credentials from environment vars. Leave other fields blank if using this.</li>
 </ul></li>
 </ul></li>
 </ul>
-<h4 id="swift-user">–swift-user</h4>
+<h4 id="swift-user">--swift-user</h4>
 <p>User name to log in (OS_USERNAME).</p>
 <ul>
 <li>Config: user</li>
@@ -14443,7 +14684,7 @@ rclone lsd myremote:</code></pre>
 <li>Type: string</li>
 <li>Default: ""</li>
 </ul>
-<h4 id="swift-key">–swift-key</h4>
+<h4 id="swift-key">--swift-key</h4>
 <p>API key or password (OS_PASSWORD).</p>
 <ul>
 <li>Config: key</li>
@@ -14451,7 +14692,7 @@ rclone lsd myremote:</code></pre>
 <li>Type: string</li>
 <li>Default: ""</li>
 </ul>
-<h4 id="swift-auth">–swift-auth</h4>
+<h4 id="swift-auth">--swift-auth</h4>
 <p>Authentication URL for server (OS_AUTH_URL).</p>
 <ul>
 <li>Config: auth</li>
@@ -14460,33 +14701,33 @@ rclone lsd myremote:</code></pre>
 <li>Default: ""</li>
 <li>Examples:
 <ul>
-<li>“https://auth.api.rackspacecloud.com/v1.0”
+<li>"https://auth.api.rackspacecloud.com/v1.0"
 <ul>
 <li>Rackspace US</li>
 </ul></li>
-<li>“https://lon.auth.api.rackspacecloud.com/v1.0”
+<li>"https://lon.auth.api.rackspacecloud.com/v1.0"
 <ul>
 <li>Rackspace UK</li>
 </ul></li>
-<li>“https://identity.api.rackspacecloud.com/v2.0”
+<li>"https://identity.api.rackspacecloud.com/v2.0"
 <ul>
 <li>Rackspace v2</li>
 </ul></li>
-<li>“https://auth.storage.memset.com/v1.0”
+<li>"https://auth.storage.memset.com/v1.0"
 <ul>
 <li>Memset Memstore UK</li>
 </ul></li>
-<li>“https://auth.storage.memset.com/v2.0”
+<li>"https://auth.storage.memset.com/v2.0"
 <ul>
 <li>Memset Memstore UK v2</li>
 </ul></li>
-<li>“https://auth.cloud.ovh.net/v3”
+<li>"https://auth.cloud.ovh.net/v3"
 <ul>
 <li>OVH</li>
 </ul></li>
 </ul></li>
 </ul>
-<h4 id="swift-user-id">–swift-user-id</h4>
+<h4 id="swift-user-id">--swift-user-id</h4>
 <p>User ID to log in - optional - most swift systems use user and leave this blank (v3 auth) (OS_USER_ID).</p>
 <ul>
 <li>Config: user_id</li>
@@ -14494,7 +14735,7 @@ rclone lsd myremote:</code></pre>
 <li>Type: string</li>
 <li>Default: ""</li>
 </ul>
-<h4 id="swift-domain">–swift-domain</h4>
+<h4 id="swift-domain">--swift-domain</h4>
 <p>User domain - optional (v3 auth) (OS_USER_DOMAIN_NAME)</p>
 <ul>
 <li>Config: domain</li>
@@ -14502,7 +14743,7 @@ rclone lsd myremote:</code></pre>
 <li>Type: string</li>
 <li>Default: ""</li>
 </ul>
-<h4 id="swift-tenant">–swift-tenant</h4>
+<h4 id="swift-tenant">--swift-tenant</h4>
 <p>Tenant name - optional for v1 auth, this or tenant_id required otherwise (OS_TENANT_NAME or OS_PROJECT_NAME)</p>
 <ul>
 <li>Config: tenant</li>
@@ -14510,7 +14751,7 @@ rclone lsd myremote:</code></pre>
 <li>Type: string</li>
 <li>Default: ""</li>
 </ul>
-<h4 id="swift-tenant-id">–swift-tenant-id</h4>
+<h4 id="swift-tenant-id">--swift-tenant-id</h4>
 <p>Tenant ID - optional for v1 auth, this or tenant required otherwise (OS_TENANT_ID)</p>
 <ul>
 <li>Config: tenant_id</li>
@@ -14518,7 +14759,7 @@ rclone lsd myremote:</code></pre>
 <li>Type: string</li>
 <li>Default: ""</li>
 </ul>
-<h4 id="swift-tenant-domain">–swift-tenant-domain</h4>
+<h4 id="swift-tenant-domain">--swift-tenant-domain</h4>
 <p>Tenant domain - optional (v3 auth) (OS_PROJECT_DOMAIN_NAME)</p>
 <ul>
 <li>Config: tenant_domain</li>
@@ -14526,7 +14767,7 @@ rclone lsd myremote:</code></pre>
 <li>Type: string</li>
 <li>Default: ""</li>
 </ul>
-<h4 id="swift-region">–swift-region</h4>
+<h4 id="swift-region">--swift-region</h4>
 <p>Region name - optional (OS_REGION_NAME)</p>
 <ul>
 <li>Config: region</li>
@@ -14534,7 +14775,7 @@ rclone lsd myremote:</code></pre>
 <li>Type: string</li>
 <li>Default: ""</li>
 </ul>
-<h4 id="swift-storage-url">–swift-storage-url</h4>
+<h4 id="swift-storage-url">--swift-storage-url</h4>
 <p>Storage URL - optional (OS_STORAGE_URL)</p>
 <ul>
 <li>Config: storage_url</li>
@@ -14542,7 +14783,7 @@ rclone lsd myremote:</code></pre>
 <li>Type: string</li>
 <li>Default: ""</li>
 </ul>
-<h4 id="swift-auth-token">–swift-auth-token</h4>
+<h4 id="swift-auth-token">--swift-auth-token</h4>
 <p>Auth Token from alternate authentication - optional (OS_AUTH_TOKEN)</p>
 <ul>
 <li>Config: auth_token</li>
@@ -14550,7 +14791,7 @@ rclone lsd myremote:</code></pre>
 <li>Type: string</li>
 <li>Default: ""</li>
 </ul>
-<h4 id="swift-application-credential-id">–swift-application-credential-id</h4>
+<h4 id="swift-application-credential-id">--swift-application-credential-id</h4>
 <p>Application Credential ID (OS_APPLICATION_CREDENTIAL_ID)</p>
 <ul>
 <li>Config: application_credential_id</li>
@@ -14558,7 +14799,7 @@ rclone lsd myremote:</code></pre>
 <li>Type: string</li>
 <li>Default: ""</li>
 </ul>
-<h4 id="swift-application-credential-name">–swift-application-credential-name</h4>
+<h4 id="swift-application-credential-name">--swift-application-credential-name</h4>
 <p>Application Credential Name (OS_APPLICATION_CREDENTIAL_NAME)</p>
 <ul>
 <li>Config: application_credential_name</li>
@@ -14566,7 +14807,7 @@ rclone lsd myremote:</code></pre>
 <li>Type: string</li>
 <li>Default: ""</li>
 </ul>
-<h4 id="swift-application-credential-secret">–swift-application-credential-secret</h4>
+<h4 id="swift-application-credential-secret">--swift-application-credential-secret</h4>
 <p>Application Credential Secret (OS_APPLICATION_CREDENTIAL_SECRET)</p>
 <ul>
 <li>Config: application_credential_secret</li>
@@ -14574,7 +14815,7 @@ rclone lsd myremote:</code></pre>
 <li>Type: string</li>
 <li>Default: ""</li>
 </ul>
-<h4 id="swift-auth-version">–swift-auth-version</h4>
+<h4 id="swift-auth-version">--swift-auth-version</h4>
 <p>AuthVersion - optional - set to (1,2,3) if your auth URL has no version (ST_AUTH_VERSION)</p>
 <ul>
 <li>Config: auth_version</li>
@@ -14582,30 +14823,30 @@ rclone lsd myremote:</code></pre>
 <li>Type: int</li>
 <li>Default: 0</li>
 </ul>
-<h4 id="swift-endpoint-type">–swift-endpoint-type</h4>
+<h4 id="swift-endpoint-type">--swift-endpoint-type</h4>
 <p>Endpoint type to choose from the service catalogue (OS_ENDPOINT_TYPE)</p>
 <ul>
 <li>Config: endpoint_type</li>
 <li>Env Var: RCLONE_SWIFT_ENDPOINT_TYPE</li>
 <li>Type: string</li>
-<li>Default: “public”</li>
+<li>Default: "public"</li>
 <li>Examples:
 <ul>
-<li>“public”
+<li>"public"
 <ul>
 <li>Public (default, choose this if not sure)</li>
 </ul></li>
-<li>“internal”
+<li>"internal"
 <ul>
 <li>Internal (use internal service net)</li>
 </ul></li>
-<li>“admin”
+<li>"admin"
 <ul>
 <li>Admin</li>
 </ul></li>
 </ul></li>
 </ul>
-<h4 id="swift-storage-policy">–swift-storage-policy</h4>
+<h4 id="swift-storage-policy">--swift-storage-policy</h4>
 <p>The storage policy to use when creating a new container</p>
 <p>This applies the specified storage policy when creating a new container. The policy cannot be changed afterwards. The allowed configuration values and their meaning depend on your Swift storage provider.</p>
 <ul>
@@ -14619,19 +14860,19 @@ rclone lsd myremote:</code></pre>
 <ul>
 <li>Default</li>
 </ul></li>
-<li>“pcs”
+<li>"pcs"
 <ul>
 <li>OVH Public Cloud Storage</li>
 </ul></li>
-<li>“pca”
+<li>"pca"
 <ul>
 <li>OVH Public Cloud Archive</li>
 </ul></li>
 </ul></li>
 </ul>
-<h3 id="advanced-options-24">Advanced Options</h3>
+<h3 id="advanced-options-10">Advanced Options</h3>
 <p>Here are the advanced options specific to swift (OpenStack Swift (Rackspace Cloud Files, Memset Memstore, OVH)).</p>
-<h4 id="swift-chunk-size">–swift-chunk-size</h4>
+<h4 id="swift-chunk-size">--swift-chunk-size</h4>
 <p>Above this size files will be chunked into a _segments container.</p>
 <p>Above this size files will be chunked into a _segments container. The default for this is 5GB which is its maximum value.</p>
 <ul>
@@ -14640,8 +14881,8 @@ rclone lsd myremote:</code></pre>
 <li>Type: SizeSuffix</li>
 <li>Default: 5G</li>
 </ul>
-<h4 id="swift-no-chunk">–swift-no-chunk</h4>
-<p>Don’t chunk files during streaming upload.</p>
+<h4 id="swift-no-chunk">--swift-no-chunk</h4>
+<p>Don't chunk files during streaming upload.</p>
 <p>When doing streaming uploads (eg using rcat or mount) setting this flag will cause the swift backend to not upload chunked files.</p>
 <p>This will limit the maximum upload size to 5GB. However non chunked files are easier to deal with and have an MD5SUM.</p>
 <p>Rclone will still chunk files bigger than chunk_size when doing normal copy operations.</p>
@@ -14651,7 +14892,7 @@ rclone lsd myremote:</code></pre>
 <li>Type: bool</li>
 <li>Default: false</li>
 </ul>
-<h4 id="swift-encoding">–swift-encoding</h4>
+<h4 id="swift-encoding">--swift-encoding</h4>
 <p>This sets 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>
 <ul>
@@ -14660,10 +14901,10 @@ rclone lsd myremote:</code></pre>
 <li>Type: MultiEncoder</li>
 <li>Default: Slash,InvalidUtf8</li>
 </ul>
-<h3 id="modified-time-11">Modified time</h3>
+<h3 id="modified-time-4">Modified time</h3>
 <p>The modified time is stored as metadata on the object as <code>X-Object-Meta-Mtime</code> as floating point since the epoch accurate to 1 ns.</p>
 <p>This is a de facto standard (used in the official python-swiftclient amongst others) for storing the modification time for an object.</p>
-<h3 id="restricted-filename-characters-19">Restricted filename characters</h3>
+<h3 id="restricted-filename-characters-9">Restricted filename characters</h3>
 <table>
 <thead>
 <tr class="header">
@@ -14685,15 +14926,15 @@ rclone lsd myremote:</code></pre>
 </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="limitations-17">Limitations</h3>
-<p>The Swift API doesn’t return a correct MD5SUM for segmented files (Dynamic or Static Large Objects) so rclone won’t check or use the MD5SUM for these.</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="limitations-10">Limitations</h3>
+<p>The Swift API doesn't return a correct MD5SUM for segmented files (Dynamic or Static Large Objects) so rclone won't check or use the MD5SUM for these.</p>
 <h3 id="troubleshooting-2">Troubleshooting</h3>
-<h4 id="rclone-gives-failed-to-create-file-system-for-remote-bad-request">Rclone gives Failed to create file system for “remote:”: Bad Request</h4>
-<p>Due to an oddity of the underlying swift library, it gives a “Bad Request” error rather than a more sensible error when the authentication fails for Swift.</p>
+<h4 id="rclone-gives-failed-to-create-file-system-for-remote-bad-request">Rclone gives Failed to create file system for "remote:": Bad Request</h4>
+<p>Due to an oddity of the underlying swift library, it gives a "Bad Request" error rather than a more sensible error when the authentication fails for Swift.</p>
 <p>So this most likely means your username / password is wrong. You can investigate further with the <code>--dump-bodies</code> flag.</p>
-<p>This may also be caused by specifying the region when you shouldn’t have (eg OVH).</p>
-<h4 id="rclone-gives-failed-to-create-file-system-response-didnt-have-storage-url-and-auth-token">Rclone gives Failed to create file system: Response didn’t have storage url and auth token</h4>
+<p>This may also be caused by specifying the region when you shouldn't have (eg OVH).</p>
+<h4 id="rclone-gives-failed-to-create-file-system-response-didnt-have-storage-url-and-auth-token">Rclone gives Failed to create file system: Response didn't have storage url and auth token</h4>
 <p>This is most likely caused by forgetting to specify your tenant when setting up a swift remote.</p>
 <h2 id="pcloud">pCloud</h2>
 <p>Paths are specified as <code>remote:path</code></p>
@@ -14749,10 +14990,10 @@ y/e/d&gt; y</code></pre>
 <pre><code>rclone ls remote:</code></pre>
 <p>To copy a local directory to an pCloud directory called backup</p>
 <pre><code>rclone copy /home/source remote:backup</code></pre>
-<h3 id="modified-time-and-hashes-8">Modified time and hashes</h3>
+<h3 id="modified-time-and-hashes-3">Modified time and hashes</h3>
 <p>pCloud allows modification times to be set on objects accurate to 1 second. These will be used to detect whether objects need syncing or not. In order to set a Modification time pCloud requires the object be re-uploaded.</p>
 <p>pCloud supports MD5 and SHA1 type hashes, so you can use the <code>--checksum</code> flag.</p>
-<h4 id="restricted-filename-characters-20">Restricted filename characters</h4>
+<h4 id="restricted-filename-characters-10">Restricted filename characters</h4>
 <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>
@@ -14770,36 +15011,60 @@ y/e/d&gt; y</code></pre>
 </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="deleting-files-6">Deleting files</h3>
+<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="deleting-files-2">Deleting files</h3>
 <p>Deleted files will be moved to the trash. Your subscription level will determine how long items stay in the trash. <code>rclone cleanup</code> can be used to empty the trash.</p>
-<h3 id="root-folder-id-2">Root folder ID</h3>
+<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 pCloud 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 <code>folder</code> field of the URL when you open the relevant folder in the pCloud web interface.</p>
 <p>So if the folder you want rclone to use has a URL which looks like <code>https://my.pcloud.com/#page=filemanager&amp;folder=5xxxxxxxx8&amp;tpl=foldergrid</code> in the browser, then you use <code>5xxxxxxxx8</code> as the <code>root_folder_id</code> in the config.</p>
-<h3 id="standard-options-25">Standard Options</h3>
+<h3 id="standard-options-10">Standard Options</h3>
 <p>Here are the standard options specific to pcloud (Pcloud).</p>
-<h4 id="pcloud-client-id">–pcloud-client-id</h4>
-<p>Pcloud App Client Id Leave blank normally.</p>
+<h4 id="pcloud-client-id">--pcloud-client-id</h4>
+<p>OAuth Client Id Leave blank normally.</p>
 <ul>
 <li>Config: client_id</li>
 <li>Env Var: RCLONE_PCLOUD_CLIENT_ID</li>
 <li>Type: string</li>
 <li>Default: ""</li>
 </ul>
-<h4 id="pcloud-client-secret">–pcloud-client-secret</h4>
-<p>Pcloud App Client Secret Leave blank normally.</p>
+<h4 id="pcloud-client-secret">--pcloud-client-secret</h4>
+<p>OAuth Client Secret Leave blank normally.</p>
 <ul>
 <li>Config: client_secret</li>
 <li>Env Var: RCLONE_PCLOUD_CLIENT_SECRET</li>
 <li>Type: string</li>
 <li>Default: ""</li>
 </ul>
-<h3 id="advanced-options-25">Advanced Options</h3>
+<h3 id="advanced-options-11">Advanced Options</h3>
 <p>Here are the advanced options specific to pcloud (Pcloud).</p>
-<h4 id="pcloud-encoding">–pcloud-encoding</h4>
+<h4 id="pcloud-token">--pcloud-token</h4>
+<p>OAuth Access Token as a JSON blob.</p>
+<ul>
+<li>Config: token</li>
+<li>Env Var: RCLONE_PCLOUD_TOKEN</li>
+<li>Type: string</li>
+<li>Default: ""</li>
+</ul>
+<h4 id="pcloud-auth-url">--pcloud-auth-url</h4>
+<p>Auth server URL. Leave blank to use the provider defaults.</p>
+<ul>
+<li>Config: auth_url</li>
+<li>Env Var: RCLONE_PCLOUD_AUTH_URL</li>
+<li>Type: string</li>
+<li>Default: ""</li>
+</ul>
+<h4 id="pcloud-token-url">--pcloud-token-url</h4>
+<p>Token server url. Leave blank to use the provider defaults.</p>
+<ul>
+<li>Config: token_url</li>
+<li>Env Var: RCLONE_PCLOUD_TOKEN_URL</li>
+<li>Type: string</li>
+<li>Default: ""</li>
+</ul>
+<h4 id="pcloud-encoding">--pcloud-encoding</h4>
 <p>This sets 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>
 <ul>
@@ -14808,13 +15073,33 @@ y/e/d&gt; y</code></pre>
 <li>Type: MultiEncoder</li>
 <li>Default: Slash,BackSlash,Del,Ctl,InvalidUtf8,Dot</li>
 </ul>
-<h4 id="pcloud-root-folder-id">–pcloud-root-folder-id</h4>
+<h4 id="pcloud-root-folder-id">--pcloud-root-folder-id</h4>
 <p>Fill in for rclone to use a non root folder as its starting point.</p>
 <ul>
 <li>Config: root_folder_id</li>
 <li>Env Var: RCLONE_PCLOUD_ROOT_FOLDER_ID</li>
 <li>Type: string</li>
-<li>Default: “d0”</li>
+<li>Default: "d0"</li>
+</ul>
+<h4 id="pcloud-hostname">--pcloud-hostname</h4>
+<p>Hostname to connect to.</p>
+<p>This is normally set when rclone initially does the oauth connection, however you will need to set it by hand if you are using remote config with rclone authorize.</p>
+<ul>
+<li>Config: hostname</li>
+<li>Env Var: RCLONE_PCLOUD_HOSTNAME</li>
+<li>Type: string</li>
+<li>Default: "api.pcloud.com"</li>
+<li>Examples:
+<ul>
+<li>"api.pcloud.com"
+<ul>
+<li>Original/US region</li>
+</ul></li>
+<li>"eapi.pcloud.com"
+<ul>
+<li>EU region</li>
+</ul></li>
+</ul></li>
 </ul>
 <h2 id="premiumize.me">premiumize.me</h2>
 <p>Paths are specified as <code>remote:path</code></p>
@@ -14868,9 +15153,9 @@ y/e/d&gt; </code></pre>
 <pre><code>rclone ls remote:</code></pre>
 <p>To copy a local directory to an premiumize.me directory called backup</p>
 <pre><code>rclone copy /home/source remote:backup</code></pre>
-<h3 id="modified-time-and-hashes-9">Modified time and hashes</h3>
+<h3 id="modified-time-and-hashes-4">Modified time and hashes</h3>
 <p>premiumize.me does not support modification times or hashes, therefore syncing will default to <code>--size-only</code> checking. Note that using <code>--update</code> will work.</p>
-<h4 id="restricted-filename-characters-21">Restricted filename characters</h4>
+<h4 id="restricted-filename-characters-11">Restricted filename characters</h4>
 <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>
@@ -14893,10 +15178,10 @@ y/e/d&gt; </code></pre>
 </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-26">Standard Options</h3>
+<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-11">Standard Options</h3>
 <p>Here are the standard options specific to premiumizeme (premiumize.me).</p>
-<h4 id="premiumizeme-api-key">–premiumizeme-api-key</h4>
+<h4 id="premiumizeme-api-key">--premiumizeme-api-key</h4>
 <p>API Key.</p>
 <p>This is not normally used - use oauth instead.</p>
 <ul>
@@ -14905,9 +15190,9 @@ y/e/d&gt; </code></pre>
 <li>Type: string</li>
 <li>Default: ""</li>
 </ul>
-<h3 id="advanced-options-26">Advanced Options</h3>
+<h3 id="advanced-options-12">Advanced Options</h3>
 <p>Here are the advanced options specific to premiumizeme (premiumize.me).</p>
-<h4 id="premiumizeme-encoding">–premiumizeme-encoding</h4>
+<h4 id="premiumizeme-encoding">--premiumizeme-encoding</h4>
 <p>This sets 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>
 <ul>
@@ -14916,9 +15201,9 @@ y/e/d&gt; </code></pre>
 <li>Type: MultiEncoder</li>
 <li>Default: Slash,DoubleQuote,BackSlash,Del,Ctl,InvalidUtf8,Dot</li>
 </ul>
-<h3 id="limitations-18">Limitations</h3>
-<p>Note that premiumize.me is case insensitive so you can’t have a file called “Hello.doc” and one called “hello.doc”.</p>
-<p>premiumize.me file names can’t have the <code>\</code> or <code>"</code> characters in. rclone maps these to and from an identical looking unicode equivalents <code>＼</code> and <code>＂</code></p>
+<h3 id="limitations-11">Limitations</h3>
+<p>Note that premiumize.me is case insensitive so you can't have a file called "Hello.doc" and one called "hello.doc".</p>
+<p>premiumize.me file names can't have the <code>\</code> or <code>"</code> characters in. rclone maps these to and from an identical looking unicode equivalents <code>＼</code> and <code>＂</code></p>
 <p>premiumize.me only supports filenames up to 255 characters in length.</p>
 <h2 id="put.io">put.io</h2>
 <p>Paths are specified as <code>remote:path</code></p>
@@ -14985,7 +15270,7 @@ e/n/d/r/c/s/q&gt; q</code></pre>
 <pre><code>rclone ls remote:</code></pre>
 <p>To copy a local directory to a put.io directory called backup</p>
 <pre><code>rclone copy /home/source remote:backup</code></pre>
-<h4 id="restricted-filename-characters-22">Restricted filename characters</h4>
+<h4 id="restricted-filename-characters-12">Restricted filename characters</h4>
 <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>
@@ -15003,10 +15288,10 @@ e/n/d/r/c/s/q&gt; q</code></pre>
 </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="advanced-options-27">Advanced Options</h3>
+<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="advanced-options-13">Advanced Options</h3>
 <p>Here are the advanced options specific to putio (Put.io).</p>
-<h4 id="putio-encoding">–putio-encoding</h4>
+<h4 id="putio-encoding">--putio-encoding</h4>
 <p>This sets 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>
 <ul>
@@ -15018,7 +15303,7 @@ e/n/d/r/c/s/q&gt; q</code></pre>
 <h2 id="seafile">Seafile</h2>
 <p>This is a backend for the <a href="https://www.seafile.com/">Seafile</a> storage service: - It works with both the free community edition or the professional edition. - Seafile versions 6.x and 7.x are all supported. - Encrypted libraries are also supported. - It supports 2FA enabled users</p>
 <h3 id="root-mode-vs-library-mode">Root mode vs Library mode</h3>
-<p>There are two distinct modes you can setup your remote: - you point your remote to the <strong>root of the server</strong>, meaning you don’t specify a library during the configuration: Paths are specified as <code>remote:library</code>. You may put subdirectories in too, eg <code>remote:library/path/to/dir</code>. - you point your remote to a specific library during the configuration: Paths are specified as <code>remote:path/to/dir</code>. <strong>This is the recommended mode when using encrypted libraries</strong>. (<em>This mode is possibly slightly faster than the root mode</em>)</p>
+<p>There are two distinct modes you can setup your remote: - you point your remote to the <strong>root of the server</strong>, meaning you don't specify a library during the configuration: Paths are specified as <code>remote:library</code>. You may put subdirectories in too, eg <code>remote:library/path/to/dir</code>. - you point your remote to a specific library during the configuration: Paths are specified as <code>remote:path/to/dir</code>. <strong>This is the recommended mode when using encrypted libraries</strong>. (<em>This mode is possibly slightly faster than the root mode</em>)</p>
 <h3 id="configuration-in-root-mode">Configuration in root mode</h3>
 <p>Here is an example of making a seafile configuration for a user with <strong>no</strong> two-factor authentication. First run</p>
 <pre><code>rclone config</code></pre>
@@ -15086,7 +15371,7 @@ 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>seafile</code>. It’s pointing to the root of your seafile server and can now be used like this:</p>
+<p>This remote is called <code>seafile</code>. It's pointing to the root of your seafile server and can now be used like this:</p>
 <p>See all libraries</p>
 <pre><code>rclone lsd seafile:</code></pre>
 <p>Create a new library</p>
@@ -15094,9 +15379,9 @@ y/e/d&gt; y</code></pre>
 <p>List the contents of a library</p>
 <pre><code>rclone ls seafile:library</code></pre>
 <p>Sync <code>/home/local/directory</code> to the remote library, deleting any excess files in the library.</p>
-<pre><code>rclone sync /home/local/directory seafile:library</code></pre>
+<pre><code>rclone sync -i /home/local/directory seafile:library</code></pre>
 <h3 id="configuration-in-library-mode">Configuration in library mode</h3>
-<p>Here’s an example of a configuration in library mode with a user that has the two-factor authentication enabled. Your 2FA code will be asked at the end of the configuration, and will attempt to authenticate you:</p>
+<p>Here's an example of a configuration in library mode with a user that has the two-factor authentication enabled. Your 2FA code will be asked at the end of the configuration, and will attempt to authenticate you:</p>
 <pre><code>No remotes found - make a new one
 n) New remote
 s) Set configuration password
@@ -15164,7 +15449,7 @@ y) Yes this is OK (default)
 e) Edit this remote
 d) Delete this remote
 y/e/d&gt; y</code></pre>
-<p>You’ll notice your password is blank in the configuration. It’s because we only need the password to authenticate you once.</p>
+<p>You'll notice your password is blank in the configuration. It's because we only need the password to authenticate you once.</p>
 <p>You specified <code>My Library</code> during the configuration. The root of the remote is pointing at the root of the library <code>My Library</code>:</p>
 <p>See all files in the library:</p>
 <pre><code>rclone lsd seafile:</code></pre>
@@ -15173,10 +15458,10 @@ y/e/d&gt; y</code></pre>
 <p>List the contents of a directory</p>
 <pre><code>rclone ls seafile:directory</code></pre>
 <p>Sync <code>/home/local/directory</code> to the remote library, deleting any excess files in the library.</p>
-<pre><code>rclone sync /home/local/directory seafile:</code></pre>
-<h3 id="fast-list-10">–fast-list</h3>
+<pre><code>rclone sync -i /home/local/directory seafile:</code></pre>
+<h3 id="fast-list-6">--fast-list</h3>
 <p>Seafile version 7+ 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. Please note this is not supported on seafile server version 6.x</p>
-<h4 id="restricted-filename-characters-23">Restricted filename characters</h4>
+<h4 id="restricted-filename-characters-13">Restricted filename characters</h4>
 <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>
@@ -15204,7 +15489,7 @@ y/e/d&gt; y</code></pre>
 </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>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="seafile-and-rclone-link">Seafile and rclone link</h3>
 <p>Rclone supports generating share links for non-encrypted libraries only. They can either be for a file or a directory:</p>
 <pre><code>rclone link seafile:seafile-tutorial.doc
@@ -15216,10 +15501,10 @@ http://my.seafile.server/d/9ea2455f6f55478bbb0d/</code></pre>
 <p>Please note a share link is unique for each file or directory. If you run a link command on a file/dir that has already been shared, you will get the exact same link.</p>
 <h3 id="compatibility">Compatibility</h3>
 <p>It has been actively tested using the <a href="https://github.com/haiwen/seafile-docker">seafile docker image</a> of these versions: - 6.3.4 community edition - 7.0.5 community edition - 7.1.3 community edition</p>
-<p>Versions below 6.0 are not supported. Versions between 6.0 and 6.3 haven’t been tested and might not work properly.</p>
-<h3 id="standard-options-27">Standard Options</h3>
+<p>Versions below 6.0 are not supported. Versions between 6.0 and 6.3 haven't been tested and might not work properly.</p>
+<h3 id="standard-options-12">Standard Options</h3>
 <p>Here are the standard options specific to seafile (seafile).</p>
-<h4 id="seafile-url">–seafile-url</h4>
+<h4 id="seafile-url">--seafile-url</h4>
 <p>URL of seafile host to connect to</p>
 <ul>
 <li>Config: url</li>
@@ -15228,13 +15513,13 @@ http://my.seafile.server/d/9ea2455f6f55478bbb0d/</code></pre>
 <li>Default: ""</li>
 <li>Examples:
 <ul>
-<li>“https://cloud.seafile.com/”
+<li>"https://cloud.seafile.com/"
 <ul>
 <li>Connect to cloud.seafile.com</li>
 </ul></li>
 </ul></li>
 </ul>
-<h4 id="seafile-user">–seafile-user</h4>
+<h4 id="seafile-user">--seafile-user</h4>
 <p>User name (usually email address)</p>
 <ul>
 <li>Config: user</li>
@@ -15242,23 +15527,24 @@ http://my.seafile.server/d/9ea2455f6f55478bbb0d/</code></pre>
 <li>Type: string</li>
 <li>Default: ""</li>
 </ul>
-<h4 id="seafile-pass">–seafile-pass</h4>
+<h4 id="seafile-pass">--seafile-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>
 <ul>
 <li>Config: pass</li>
 <li>Env Var: RCLONE_SEAFILE_PASS</li>
 <li>Type: string</li>
 <li>Default: ""</li>
 </ul>
-<h4 id="seafile-2fa">–seafile-2fa</h4>
-<p>Two-factor authentication (‘true’ if the account has 2FA enabled)</p>
+<h4 id="seafile-2fa">--seafile-2fa</h4>
+<p>Two-factor authentication ('true' if the account has 2FA enabled)</p>
 <ul>
 <li>Config: 2fa</li>
 <li>Env Var: RCLONE_SEAFILE_2FA</li>
 <li>Type: bool</li>
 <li>Default: false</li>
 </ul>
-<h4 id="seafile-library">–seafile-library</h4>
+<h4 id="seafile-library">--seafile-library</h4>
 <p>Name of the library. Leave blank to access all non-encrypted libraries.</p>
 <ul>
 <li>Config: library</li>
@@ -15266,15 +15552,16 @@ http://my.seafile.server/d/9ea2455f6f55478bbb0d/</code></pre>
 <li>Type: string</li>
 <li>Default: ""</li>
 </ul>
-<h4 id="seafile-library-key">–seafile-library-key</h4>
+<h4 id="seafile-library-key">--seafile-library-key</h4>
 <p>Library password (for encrypted libraries only). Leave blank if you pass it through the command line.</p>
+<p><strong>NB</strong> Input to this must be obscured - see <a href="https://rclone.org/commands/rclone_obscure/">rclone obscure</a>.</p>
 <ul>
 <li>Config: library_key</li>
 <li>Env Var: RCLONE_SEAFILE_LIBRARY_KEY</li>
 <li>Type: string</li>
 <li>Default: ""</li>
 </ul>
-<h4 id="seafile-auth-token">–seafile-auth-token</h4>
+<h4 id="seafile-auth-token">--seafile-auth-token</h4>
 <p>Authentication token</p>
 <ul>
 <li>Config: auth_token</li>
@@ -15282,17 +15569,17 @@ http://my.seafile.server/d/9ea2455f6f55478bbb0d/</code></pre>
 <li>Type: string</li>
 <li>Default: ""</li>
 </ul>
-<h3 id="advanced-options-28">Advanced Options</h3>
+<h3 id="advanced-options-14">Advanced Options</h3>
 <p>Here are the advanced options specific to seafile (seafile).</p>
-<h4 id="seafile-create-library">–seafile-create-library</h4>
-<p>Should rclone create a library if it doesn’t exist</p>
+<h4 id="seafile-create-library">--seafile-create-library</h4>
+<p>Should rclone create a library if it doesn't exist</p>
 <ul>
 <li>Config: create_library</li>
 <li>Env Var: RCLONE_SEAFILE_CREATE_LIBRARY</li>
 <li>Type: bool</li>
 <li>Default: false</li>
 </ul>
-<h4 id="seafile-encoding">–seafile-encoding</h4>
+<h4 id="seafile-encoding">--seafile-encoding</h4>
 <p>This sets 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>
 <ul>
@@ -15309,7 +15596,7 @@ http://my.seafile.server/d/9ea2455f6f55478bbb0d/</code></pre>
 <li>rsync.net</li>
 </ul>
 <p>SFTP runs over SSH v2 and is installed as standard with most modern SSH installations.</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>
+<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>
 <p>"Note that some SFTP servers will need the leading / - Synology is a good example of this. rsync.net, on the other hand, requires users to OMIT the leading /.</p>
 <p>Here is an example of making an SFTP configuration. First run</p>
 <pre><code>rclone config</code></pre>
@@ -15364,7 +15651,7 @@ y/e/d&gt; y</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 /home/local/directory remote:directory</code></pre>
+<pre><code>rclone sync -i /home/local/directory remote:directory</code></pre>
 <h3 id="ssh-authentication">SSH Authentication</h3>
 <p>The SFTP remote supports three authentication methods:</p>
 <ul>
@@ -15373,11 +15660,11 @@ y/e/d&gt; y</code></pre>
 <li>ssh-agent</li>
 </ul>
 <p>Key files should be PEM-encoded private key files. For instance <code>/home/$USER/.ssh/id_rsa</code>. Only unencrypted OpenSSH or PEM encrypted files are supported.</p>
-<p>The key file can be specified in either an external file (key_file) or contained within the rclone config file (key_pem). If using key_pem in the config file, the entry should be on a single line with new line (‘’ or ‘’) separating lines. i.e. </p>
-<p>key_pem = —–BEGIN RSA PRIVATE KEY—–0gAMbMbaSsd—–END RSA PRIVATE KEY—–</p>
+<p>The key file can be specified in either an external file (key_file) or contained within the rclone config file (key_pem). If using key_pem in the config file, the entry should be on a single line with new line ('' or '') separating lines. i.e.</p>
+<p>key_pem = -----BEGIN RSA PRIVATE KEY-----0gAMbMbaSsd-----END RSA PRIVATE KEY-----</p>
 <p>This will generate it correctly for key_pem for use in the config:</p>
 <pre><code>awk &#39;{printf &quot;%s\\n&quot;, $0}&#39; &lt; ~/.ssh/id_rsa</code></pre>
-<p>If you don’t specify <code>pass</code>, <code>key_file</code>, or <code>key_pem</code> then rclone will attempt to contact an ssh-agent.</p>
+<p>If you don't specify <code>pass</code>, <code>key_file</code>, or <code>key_pem</code> then rclone will attempt to contact an ssh-agent.</p>
 <p>You can also specify <code>key_use_agent</code> to force the usage of an ssh-agent. In this case <code>key_file</code> or <code>key_pem</code> can also be specified to force the usage of a specific key in the ssh-agent.</p>
 <p>Using an ssh-agent is the only way to load encrypted OpenSSH keys at the moment.</p>
 <p>If you set the <code>--sftp-ask-password</code> option, rclone will prompt for a password when needed and no password has been configured.</p>
@@ -15387,13 +15674,13 @@ y/e/d&gt; y</code></pre>
 <p>And then at the end of the session</p>
 <pre><code>eval `ssh-agent -k`</code></pre>
 <p>These commands can be used in scripts of course.</p>
-<h3 id="modified-time-12">Modified time</h3>
+<h3 id="modified-time-5">Modified time</h3>
 <p>Modified times are stored on the server to 1 second precision.</p>
 <p>Modified times are used in syncing and are fully supported.</p>
 <p>Some SFTP servers disable setting/modifying the file modification time after upload (for example, certain configurations of ProFTPd with mod_sftp). If you are using one of these servers, you can set the option <code>set_modtime = false</code> in your RClone backend configuration to disable this behaviour.</p>
-<h3 id="standard-options-28">Standard Options</h3>
+<h3 id="standard-options-13">Standard Options</h3>
 <p>Here are the standard options specific to sftp (SSH/SFTP Connection).</p>
-<h4 id="sftp-host">–sftp-host</h4>
+<h4 id="sftp-host">--sftp-host</h4>
 <p>SSH host to connect to</p>
 <ul>
 <li>Config: host</li>
@@ -15402,13 +15689,13 @@ y/e/d&gt; y</code></pre>
 <li>Default: ""</li>
 <li>Examples:
 <ul>
-<li>“example.com”
+<li>"example.com"
 <ul>
 <li>Connect to example.com</li>
 </ul></li>
 </ul></li>
 </ul>
-<h4 id="sftp-user">–sftp-user</h4>
+<h4 id="sftp-user">--sftp-user</h4>
 <p>SSH username, leave blank for current username, ncw</p>
 <ul>
 <li>Config: user</li>
@@ -15416,7 +15703,7 @@ y/e/d&gt; y</code></pre>
 <li>Type: string</li>
 <li>Default: ""</li>
 </ul>
-<h4 id="sftp-port">–sftp-port</h4>
+<h4 id="sftp-port">--sftp-port</h4>
 <p>SSH port, leave blank to use default (22)</p>
 <ul>
 <li>Config: port</li>
@@ -15424,15 +15711,16 @@ y/e/d&gt; y</code></pre>
 <li>Type: string</li>
 <li>Default: ""</li>
 </ul>
-<h4 id="sftp-pass">–sftp-pass</h4>
+<h4 id="sftp-pass">--sftp-pass</h4>
 <p>SSH password, leave blank to use ssh-agent.</p>
+<p><strong>NB</strong> Input to this must be obscured - see <a href="https://rclone.org/commands/rclone_obscure/">rclone obscure</a>.</p>
 <ul>
 <li>Config: pass</li>
 <li>Env Var: RCLONE_SFTP_PASS</li>
 <li>Type: string</li>
 <li>Default: ""</li>
 </ul>
-<h4 id="sftp-key-pem">–sftp-key-pem</h4>
+<h4 id="sftp-key-pem">--sftp-key-pem</h4>
 <p>Raw PEM-encoded private key, If specified, will override key_file parameter.</p>
 <ul>
 <li>Config: key_pem</li>
@@ -15440,33 +15728,35 @@ y/e/d&gt; y</code></pre>
 <li>Type: string</li>
 <li>Default: ""</li>
 </ul>
-<h4 id="sftp-key-file">–sftp-key-file</h4>
+<h4 id="sftp-key-file">--sftp-key-file</h4>
 <p>Path to PEM-encoded private key file, leave blank or set key-use-agent to use ssh-agent.</p>
+<p>Leading <code>~</code> will be expanded in the file name as will environment variables such as <code>${RCLONE_CONFIG_DIR}</code>.</p>
 <ul>
 <li>Config: key_file</li>
 <li>Env Var: RCLONE_SFTP_KEY_FILE</li>
 <li>Type: string</li>
 <li>Default: ""</li>
 </ul>
-<h4 id="sftp-key-file-pass">–sftp-key-file-pass</h4>
+<h4 id="sftp-key-file-pass">--sftp-key-file-pass</h4>
 <p>The passphrase to decrypt the PEM-encoded private key file.</p>
-<p>Only PEM encrypted key files (old OpenSSH format) are supported. Encrypted keys in the new OpenSSH format can’t be used.</p>
+<p>Only PEM encrypted key files (old OpenSSH format) are supported. Encrypted keys in the new OpenSSH format can't be used.</p>
+<p><strong>NB</strong> Input to this must be obscured - see <a href="https://rclone.org/commands/rclone_obscure/">rclone obscure</a>.</p>
 <ul>
 <li>Config: key_file_pass</li>
 <li>Env Var: RCLONE_SFTP_KEY_FILE_PASS</li>
 <li>Type: string</li>
 <li>Default: ""</li>
 </ul>
-<h4 id="sftp-key-use-agent">–sftp-key-use-agent</h4>
+<h4 id="sftp-key-use-agent">--sftp-key-use-agent</h4>
 <p>When set forces the usage of the ssh-agent.</p>
-<p>When key-file is also set, the “.pub” file of the specified key-file is read and only the associated key is requested from the ssh-agent. This allows to avoid <code>Too many authentication failures for *username*</code> errors when the ssh-agent contains many keys.</p>
+<p>When key-file is also set, the ".pub" file of the specified key-file is read and only the associated key is requested from the ssh-agent. This allows to avoid <code>Too many authentication failures for *username*</code> errors when the ssh-agent contains many keys.</p>
 <ul>
 <li>Config: key_use_agent</li>
 <li>Env Var: RCLONE_SFTP_KEY_USE_AGENT</li>
 <li>Type: bool</li>
 <li>Default: false</li>
 </ul>
-<h4 id="sftp-use-insecure-cipher">–sftp-use-insecure-cipher</h4>
+<h4 id="sftp-use-insecure-cipher">--sftp-use-insecure-cipher</h4>
 <p>Enable the use of insecure ciphers and key exchange methods.</p>
 <p>This enables the use of the following insecure ciphers and key exchange methods:</p>
 <ul>
@@ -15485,17 +15775,17 @@ y/e/d&gt; y</code></pre>
 <li>Default: false</li>
 <li>Examples:
 <ul>
-<li>“false”
+<li>"false"
 <ul>
 <li>Use default Cipher list.</li>
 </ul></li>
-<li>“true”
+<li>"true"
 <ul>
 <li>Enables the use of the aes128-cbc cipher and diffie-hellman-group-exchange-sha256, diffie-hellman-group-exchange-sha1 key exchange.</li>
 </ul></li>
 </ul></li>
 </ul>
-<h4 id="sftp-disable-hashcheck">–sftp-disable-hashcheck</h4>
+<h4 id="sftp-disable-hashcheck">--sftp-disable-hashcheck</h4>
 <p>Disable the execution of SSH commands to determine if remote file hashing is available. Leave blank or set to false to enable hashing (recommended), set to true to disable hashing.</p>
 <ul>
 <li>Config: disable_hashcheck</li>
@@ -15503,9 +15793,9 @@ y/e/d&gt; y</code></pre>
 <li>Type: bool</li>
 <li>Default: false</li>
 </ul>
-<h3 id="advanced-options-29">Advanced Options</h3>
+<h3 id="advanced-options-15">Advanced Options</h3>
 <p>Here are the advanced options specific to sftp (SSH/SFTP Connection).</p>
-<h4 id="sftp-ask-password">–sftp-ask-password</h4>
+<h4 id="sftp-ask-password">--sftp-ask-password</h4>
 <p>Allow asking for SFTP password when needed.</p>
 <p>If this is set and no password is supplied then rclone will: - ask for a password - not contact the ssh agent</p>
 <ul>
@@ -15514,12 +15804,12 @@ y/e/d&gt; y</code></pre>
 <li>Type: bool</li>
 <li>Default: false</li>
 </ul>
-<h4 id="sftp-path-override">–sftp-path-override</h4>
+<h4 id="sftp-path-override">--sftp-path-override</h4>
 <p>Override path used by SSH connection.</p>
 <p>This allows checksum calculation when SFTP and SSH paths are different. This issue affects among others Synology NAS boxes.</p>
 <p>Shared folders can be found in directories representing volumes</p>
 <pre><code>rclone sync /home/local/directory remote:/directory --ssh-path-override /volume2/directory</code></pre>
-<p>Home directory can be found in a shared folder called “home”</p>
+<p>Home directory can be found in a shared folder called "home"</p>
 <pre><code>rclone sync /home/local/directory remote:/home/directory --ssh-path-override /volume1/homes/USER/directory</code></pre>
 <ul>
 <li>Config: path_override</li>
@@ -15527,7 +15817,7 @@ y/e/d&gt; y</code></pre>
 <li>Type: string</li>
 <li>Default: ""</li>
 </ul>
-<h4 id="sftp-set-modtime">–sftp-set-modtime</h4>
+<h4 id="sftp-set-modtime">--sftp-set-modtime</h4>
 <p>Set the modified time on the remote if set.</p>
 <ul>
 <li>Config: set_modtime</li>
@@ -15535,7 +15825,7 @@ y/e/d&gt; y</code></pre>
 <li>Type: bool</li>
 <li>Default: true</li>
 </ul>
-<h4 id="sftp-md5sum-command">–sftp-md5sum-command</h4>
+<h4 id="sftp-md5sum-command">--sftp-md5sum-command</h4>
 <p>The command used to read md5 hashes. Leave blank for autodetect.</p>
 <ul>
 <li>Config: md5sum_command</li>
@@ -15543,7 +15833,7 @@ y/e/d&gt; y</code></pre>
 <li>Type: string</li>
 <li>Default: ""</li>
 </ul>
-<h4 id="sftp-sha1sum-command">–sftp-sha1sum-command</h4>
+<h4 id="sftp-sha1sum-command">--sftp-sha1sum-command</h4>
 <p>The command used to read sha1 hashes. Leave blank for autodetect.</p>
 <ul>
 <li>Config: sha1sum_command</li>
@@ -15551,7 +15841,7 @@ y/e/d&gt; y</code></pre>
 <li>Type: string</li>
 <li>Default: ""</li>
 </ul>
-<h4 id="sftp-skip-links">–sftp-skip-links</h4>
+<h4 id="sftp-skip-links">--sftp-skip-links</h4>
 <p>Set to skip any symlinks and any other non regular files.</p>
 <ul>
 <li>Config: skip_links</li>
@@ -15559,21 +15849,38 @@ y/e/d&gt; y</code></pre>
 <li>Type: bool</li>
 <li>Default: false</li>
 </ul>
-<h3 id="limitations-19">Limitations</h3>
-<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. This remote checksumming (file hashing) is recommended and enabled by default. Disabling the checksumming may be required if you are connecting to SFTP servers which are not under your control, and to which the execution of remote commands is prohibited. Set the configuration option <code>disable_hashcheck</code> to <code>true</code> to disable checksumming.</p>
-<p>SFTP also supports <code>about</code> if the same login has shell access and <code>df</code> are in the remote’s PATH. <code>about</code> will return the total space, free space, and used space on the remote for the disk of the specified path on the remote or, if not set, the disk of the root on the remote. <code>about</code> will fail if it does not have shell access or if <code>df</code> is not in the remote’s PATH.</p>
-<p>Note that some SFTP servers (eg Synology) the paths are different for SSH and SFTP so the hashes can’t be calculated properly. For them using <code>disable_hashcheck</code> is a good idea.</p>
-<p>The only ssh agent supported under Windows is Putty’s pageant.</p>
+<h4 id="sftp-subsystem">--sftp-subsystem</h4>
+<p>Specifies the SSH2 subsystem on the remote host.</p>
+<ul>
+<li>Config: subsystem</li>
+<li>Env Var: RCLONE_SFTP_SUBSYSTEM</li>
+<li>Type: string</li>
+<li>Default: "sftp"</li>
+</ul>
+<h4 id="sftp-server-command">--sftp-server-command</h4>
+<p>Specifies the path or command to run a sftp server on the remote host.</p>
+<p>The subsystem option is ignored when server_command is defined.</p>
+<ul>
+<li>Config: server_command</li>
+<li>Env Var: RCLONE_SFTP_SERVER_COMMAND</li>
+<li>Type: string</li>
+<li>Default: ""</li>
+</ul>
+<h3 id="limitations-12">Limitations</h3>
+<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. This remote checksumming (file hashing) is recommended and enabled by default. Disabling the checksumming may be required if you are connecting to SFTP servers which are not under your control, and to which the execution of remote commands is prohibited. Set the configuration option <code>disable_hashcheck</code> to <code>true</code> to disable checksumming.</p>
+<p>SFTP also supports <code>about</code> if the same login has shell access and <code>df</code> are in the remote's PATH. <code>about</code> will return the total space, free space, and used space on the remote for the disk of the specified path on the remote or, if not set, the disk of the root on the remote. <code>about</code> will fail if it does not have shell access or if <code>df</code> is not in the remote's PATH.</p>
+<p>Note that some SFTP servers (eg Synology) the paths are different for SSH and SFTP so the hashes can't be calculated properly. For them using <code>disable_hashcheck</code> is a good idea.</p>
+<p>The only ssh agent supported under Windows is Putty's pageant.</p>
 <p>The Go SSH library disables the use of the aes128-cbc cipher by default, due to security concerns. This can be re-enabled on a per-connection basis by setting the <code>use_insecure_cipher</code> setting in the configuration file to <code>true</code>. Further details on the insecurity of this cipher can be found [in this paper] (http://www.isg.rhul.ac.uk/~kp/SandPfinal.pdf).</p>
-<p>SFTP isn’t supported under plan9 until <a href="https://github.com/pkg/sftp/issues/156">this issue</a> is fixed.</p>
-<p>Note that since SFTP isn’t HTTP based the following flags don’t work with it: <code>--dump-headers</code>, <code>--dump-bodies</code>, <code>--dump-auth</code></p>
-<p>Note that <code>--timeout</code> isn’t supported (but <code>--contimeout</code> is).</p>
+<p>SFTP isn't supported under plan9 until <a href="https://github.com/pkg/sftp/issues/156">this issue</a> is fixed.</p>
+<p>Note that since SFTP isn't HTTP based the following flags don't work with it: <code>--dump-headers</code>, <code>--dump-bodies</code>, <code>--dump-auth</code></p>
+<p>Note that <code>--timeout</code> isn't supported (but <code>--contimeout</code> is).</p>
 <h2 id="c14">C14</h2>
 <p>C14 is supported through the SFTP backend.</p>
-<p>See <a href="https://www.online.net/en/storage/c14-cold-storage">C14’s documentation</a></p>
+<p>See <a href="https://www.online.net/en/storage/c14-cold-storage">C14's documentation</a></p>
 <h2 id="rsync-net">rsync.net</h2>
 <p>rsync.net is supported through the SFTP backend.</p>
-<p>See <a href="https://www.rsync.net/products/rclone.html">rsync.net’s documentation of rclone examples</a>.</p>
+<p>See <a href="https://www.rsync.net/products/rclone.html">rsync.net's documentation of rclone examples</a>.</p>
 <h2 id="sugarsync">SugarSync</h2>
 <p><a href="https://sugarsync.com">SugarSync</a> is a cloud service that enables active synchronization of files across computers and other devices for file backup, access, syncing, and sharing.</p>
 <p>The initial setup for SugarSync involves getting a token from SugarSync which you can do with rclone. <code>rclone config</code> walks you through it.</p>
@@ -15629,55 +15936,55 @@ y) Yes this is OK (default)
 e) Edit this remote
 d) Delete this remote
 y/e/d&gt; y</code></pre>
-<p>Note that the config asks for your email and password but doesn’t store them, it only uses them to get the initial token.</p>
+<p>Note that the config asks for your email and password but doesn't store them, it only uses them to get the initial token.</p>
 <p>Once configured you can then use <code>rclone</code> like this,</p>
 <p>List directories (sync folders) in top level of your SugarSync</p>
 <pre><code>rclone lsd remote:</code></pre>
-<p>List all the files in your SugarSync folder “Test”</p>
+<p>List all the files in your SugarSync folder "Test"</p>
 <pre><code>rclone ls remote:Test</code></pre>
 <p>To copy a local directory to an SugarSync folder called backup</p>
 <pre><code>rclone copy /home/source remote:backup</code></pre>
 <p>Paths are specified as <code>remote:path</code></p>
 <p>Paths may be as deep as required, eg <code>remote:directory/subdirectory</code>.</p>
-<p><strong>NB</strong> you can’t create files in the top level folder you have to create a folder, which rclone will create as a “Sync Folder” with SugarSync.</p>
-<h3 id="modified-time-and-hashes-10">Modified time and hashes</h3>
+<p><strong>NB</strong> you can't create files in the top level folder you have to create a folder, which rclone will create as a "Sync Folder" with SugarSync.</p>
+<h3 id="modified-time-and-hashes-5">Modified time and hashes</h3>
 <p>SugarSync does not support modification times or hashes, therefore syncing will default to <code>--size-only</code> checking. Note that using <code>--update</code> will work as rclone can read the time files were uploaded.</p>
-<h4 id="restricted-filename-characters-24">Restricted filename characters</h4>
+<h4 id="restricted-filename-characters-14">Restricted filename characters</h4>
 <p>SugarSync replaces the <a href="https://rclone.org/overview/#restricted-characters">default restricted characters set</a> except for DEL.</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 XML strings.</p>
-<h3 id="deleting-files-7">Deleting files</h3>
-<p>Deleted files will be moved to the “Deleted items” folder by default.</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 XML strings.</p>
+<h3 id="deleting-files-3">Deleting files</h3>
+<p>Deleted files will be moved to the "Deleted items" folder by default.</p>
 <p>However you can supply the flag <code>--sugarsync-hard-delete</code> or set the config parameter <code>hard_delete = true</code> if you would like files to be deleted straight away.</p>
-<h3 id="standard-options-29">Standard Options</h3>
+<h3 id="standard-options-14">Standard Options</h3>
 <p>Here are the standard options specific to sugarsync (Sugarsync).</p>
-<h4 id="sugarsync-app-id">–sugarsync-app-id</h4>
+<h4 id="sugarsync-app-id">--sugarsync-app-id</h4>
 <p>Sugarsync App ID.</p>
-<p>Leave blank to use rclone’s.</p>
+<p>Leave blank to use rclone's.</p>
 <ul>
 <li>Config: app_id</li>
 <li>Env Var: RCLONE_SUGARSYNC_APP_ID</li>
 <li>Type: string</li>
 <li>Default: ""</li>
 </ul>
-<h4 id="sugarsync-access-key-id">–sugarsync-access-key-id</h4>
+<h4 id="sugarsync-access-key-id">--sugarsync-access-key-id</h4>
 <p>Sugarsync Access Key ID.</p>
-<p>Leave blank to use rclone’s.</p>
+<p>Leave blank to use rclone's.</p>
 <ul>
 <li>Config: access_key_id</li>
 <li>Env Var: RCLONE_SUGARSYNC_ACCESS_KEY_ID</li>
 <li>Type: string</li>
 <li>Default: ""</li>
 </ul>
-<h4 id="sugarsync-private-access-key">–sugarsync-private-access-key</h4>
+<h4 id="sugarsync-private-access-key">--sugarsync-private-access-key</h4>
 <p>Sugarsync Private Access Key</p>
-<p>Leave blank to use rclone’s.</p>
+<p>Leave blank to use rclone's.</p>
 <ul>
 <li>Config: private_access_key</li>
 <li>Env Var: RCLONE_SUGARSYNC_PRIVATE_ACCESS_KEY</li>
 <li>Type: string</li>
 <li>Default: ""</li>
 </ul>
-<h4 id="sugarsync-hard-delete">–sugarsync-hard-delete</h4>
+<h4 id="sugarsync-hard-delete">--sugarsync-hard-delete</h4>
 <p>Permanently delete files if true otherwise put them in the deleted files.</p>
 <ul>
 <li>Config: hard_delete</li>
@@ -15685,9 +15992,9 @@ y/e/d&gt; y</code></pre>
 <li>Type: bool</li>
 <li>Default: false</li>
 </ul>
-<h3 id="advanced-options-30">Advanced Options</h3>
+<h3 id="advanced-options-16">Advanced Options</h3>
 <p>Here are the advanced options specific to sugarsync (Sugarsync).</p>
-<h4 id="sugarsync-refresh-token">–sugarsync-refresh-token</h4>
+<h4 id="sugarsync-refresh-token">--sugarsync-refresh-token</h4>
 <p>Sugarsync refresh token</p>
 <p>Leave blank normally, will be auto configured by rclone.</p>
 <ul>
@@ -15696,7 +16003,7 @@ y/e/d&gt; y</code></pre>
 <li>Type: string</li>
 <li>Default: ""</li>
 </ul>
-<h4 id="sugarsync-authorization">–sugarsync-authorization</h4>
+<h4 id="sugarsync-authorization">--sugarsync-authorization</h4>
 <p>Sugarsync authorization</p>
 <p>Leave blank normally, will be auto configured by rclone.</p>
 <ul>
@@ -15705,7 +16012,7 @@ y/e/d&gt; y</code></pre>
 <li>Type: string</li>
 <li>Default: ""</li>
 </ul>
-<h4 id="sugarsync-authorization-expiry">–sugarsync-authorization-expiry</h4>
+<h4 id="sugarsync-authorization-expiry">--sugarsync-authorization-expiry</h4>
 <p>Sugarsync authorization expiry</p>
 <p>Leave blank normally, will be auto configured by rclone.</p>
 <ul>
@@ -15714,7 +16021,7 @@ y/e/d&gt; y</code></pre>
 <li>Type: string</li>
 <li>Default: ""</li>
 </ul>
-<h4 id="sugarsync-user">–sugarsync-user</h4>
+<h4 id="sugarsync-user">--sugarsync-user</h4>
 <p>Sugarsync user</p>
 <p>Leave blank normally, will be auto configured by rclone.</p>
 <ul>
@@ -15723,7 +16030,7 @@ y/e/d&gt; y</code></pre>
 <li>Type: string</li>
 <li>Default: ""</li>
 </ul>
-<h4 id="sugarsync-root-id">–sugarsync-root-id</h4>
+<h4 id="sugarsync-root-id">--sugarsync-root-id</h4>
 <p>Sugarsync root id</p>
 <p>Leave blank normally, will be auto configured by rclone.</p>
 <ul>
@@ -15732,7 +16039,7 @@ y/e/d&gt; y</code></pre>
 <li>Type: string</li>
 <li>Default: ""</li>
 </ul>
-<h4 id="sugarsync-deleted-id">–sugarsync-deleted-id</h4>
+<h4 id="sugarsync-deleted-id">--sugarsync-deleted-id</h4>
 <p>Sugarsync deleted folder id</p>
 <p>Leave blank normally, will be auto configured by rclone.</p>
 <ul>
@@ -15741,7 +16048,7 @@ y/e/d&gt; y</code></pre>
 <li>Type: string</li>
 <li>Default: ""</li>
 </ul>
-<h4 id="sugarsync-encoding">–sugarsync-encoding</h4>
+<h4 id="sugarsync-encoding">--sugarsync-encoding</h4>
 <p>This sets 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>
 <ul>
@@ -15752,7 +16059,7 @@ y/e/d&gt; y</code></pre>
 </ul>
 <h2 id="tardigrade">Tardigrade</h2>
 <p><a href="https://tardigrade.io">Tardigrade</a> is an encrypted, secure, and cost-effective object storage service that enables you to store, back up, and archive large amounts of data in a decentralized manner.</p>
-<h2 id="setup-3">Setup</h2>
+<h2 id="setup-1">Setup</h2>
 <p>To make a new Tardigrade configuration you need one of the following: * Access Grant that someone else shared with you. * <a href="https://documentation.tardigrade.io/getting-started/uploading-your-first-object/create-an-api-key">API Key</a> of a Tardigrade project you are a member of.</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>
@@ -15853,7 +16160,7 @@ y/e/d&gt; y</code></pre>
 <p>Paths are specified as <code>remote:bucket</code> (or <code>remote:</code> for the <code>lsf</code> command.) You may put subdirectories in too, eg <code>remote:bucket/path/to/dir</code>.</p>
 <p>Once configured you can then use <code>rclone</code> like this.</p>
 <h3 id="create-a-new-bucket">Create a new bucket</h3>
-<p>Use the <code>mkdir</code> command to create new bucket, e.g. <code>bucket</code>.</p>
+<p>Use the <code>mkdir</code> command to create new bucket, e.g. <code>bucket</code>.</p>
 <pre><code>rclone mkdir remote:bucket</code></pre>
 <h3 id="list-all-buckets">List all buckets</h3>
 <p>Use the <code>lsf</code> command to list all buckets.</p>
@@ -15867,7 +16174,7 @@ y/e/d&gt; y</code></pre>
 <h3 id="upload-objects">Upload objects</h3>
 <p>Use the <code>copy</code> command to upload an object.</p>
 <pre><code>rclone copy --progress /home/local/directory/file.ext remote:bucket/path/to/dir/</code></pre>
-<p>The <code>--progress</code> flag is for displaying progress information. Remove it if you don’t need this information.</p>
+<p>The <code>--progress</code> flag is for displaying progress information. Remove it if you don't need this information.</p>
 <p>Use a folder in the local path to upload all its objects.</p>
 <pre><code>rclone copy --progress /home/local/directory/ remote:bucket/path/to/dir/</code></pre>
 <p>Only modified files will be copied.</p>
@@ -15881,7 +16188,7 @@ y/e/d&gt; y</code></pre>
 <h3 id="download-objects">Download objects</h3>
 <p>Use the <code>copy</code> command to download an object.</p>
 <pre><code>rclone copy --progress remote:bucket/path/to/dir/file.ext /home/local/directory/</code></pre>
-<p>The <code>--progress</code> flag is for displaying progress information. Remove it if you don’t need this information.</p>
+<p>The <code>--progress</code> flag is for displaying progress information. Remove it if you don't need this information.</p>
 <p>Use a folder in the remote path to download all its objects.</p>
 <pre><code>rclone copy --progress remote:bucket/path/to/dir/ /home/local/directory/</code></pre>
 <h3 id="delete-objects">Delete objects</h3>
@@ -15894,37 +16201,37 @@ y/e/d&gt; y</code></pre>
 <pre><code>rclone size remote:bucket/path/to/dir/</code></pre>
 <h3 id="sync-two-locations">Sync two Locations</h3>
 <p>Use the <code>sync</code> command to sync the source to the destination, changing the destination only, deleting any excess files.</p>
-<pre><code>rclone sync --progress /home/local/directory/ remote:bucket/path/to/dir/</code></pre>
-<p>The <code>--progress</code> flag is for displaying progress information. Remove it if you don’t need this information.</p>
+<pre><code>rclone sync -i --progress /home/local/directory/ remote:bucket/path/to/dir/</code></pre>
+<p>The <code>--progress</code> flag is for displaying progress information. Remove it if you don't need this information.</p>
 <p>Since this can cause data loss, test first with the <code>--dry-run</code> flag to see exactly what would be copied and deleted.</p>
 <p>The sync can be done also from Tardigrade to the local file system.</p>
-<pre><code>rclone sync --progress remote:bucket/path/to/dir/ /home/local/directory/</code></pre>
+<pre><code>rclone sync -i --progress remote:bucket/path/to/dir/ /home/local/directory/</code></pre>
 <p>Or between two Tardigrade buckets.</p>
-<pre><code>rclone sync --progress remote-us:bucket/path/to/dir/ remote-europe:bucket/path/to/dir/</code></pre>
+<pre><code>rclone sync -i --progress remote-us:bucket/path/to/dir/ remote-europe:bucket/path/to/dir/</code></pre>
 <p>Or even between another cloud storage and Tardigrade.</p>
-<pre><code>rclone sync --progress s3:bucket/path/to/dir/ tardigrade:bucket/path/to/dir/</code></pre>
-<h3 id="standard-options-30">Standard Options</h3>
+<pre><code>rclone sync -i --progress s3:bucket/path/to/dir/ tardigrade:bucket/path/to/dir/</code></pre>
+<h3 id="standard-options-15">Standard Options</h3>
 <p>Here are the standard options specific to tardigrade (Tardigrade Decentralized Cloud Storage).</p>
-<h4 id="tardigrade-provider">–tardigrade-provider</h4>
+<h4 id="tardigrade-provider">--tardigrade-provider</h4>
 <p>Choose an authentication method.</p>
 <ul>
 <li>Config: provider</li>
 <li>Env Var: RCLONE_TARDIGRADE_PROVIDER</li>
 <li>Type: string</li>
-<li>Default: “existing”</li>
+<li>Default: "existing"</li>
 <li>Examples:
 <ul>
-<li>“existing”
+<li>"existing"
 <ul>
 <li>Use an existing access grant.</li>
 </ul></li>
-<li>“new”
+<li>"new"
 <ul>
 <li>Create a new access grant from satellite address, API key, and passphrase.</li>
 </ul></li>
 </ul></li>
 </ul>
-<h4 id="tardigrade-access-grant">–tardigrade-access-grant</h4>
+<h4 id="tardigrade-access-grant">--tardigrade-access-grant</h4>
 <p>Access Grant.</p>
 <ul>
 <li>Config: access_grant</li>
@@ -15932,30 +16239,30 @@ y/e/d&gt; y</code></pre>
 <li>Type: string</li>
 <li>Default: ""</li>
 </ul>
-<h4 id="tardigrade-satellite-address">–tardigrade-satellite-address</h4>
+<h4 id="tardigrade-satellite-address">--tardigrade-satellite-address</h4>
 <p>Satellite Address. Custom satellite address should match the format: <code>&lt;nodeid&gt;@&lt;address&gt;:&lt;port&gt;</code>.</p>
 <ul>
 <li>Config: satellite_address</li>
 <li>Env Var: RCLONE_TARDIGRADE_SATELLITE_ADDRESS</li>
 <li>Type: string</li>
-<li>Default: “us-central-1.tardigrade.io”</li>
+<li>Default: "us-central-1.tardigrade.io"</li>
 <li>Examples:
 <ul>
-<li>“us-central-1.tardigrade.io”
+<li>"us-central-1.tardigrade.io"
 <ul>
 <li>US Central 1</li>
 </ul></li>
-<li>“europe-west-1.tardigrade.io”
+<li>"europe-west-1.tardigrade.io"
 <ul>
 <li>Europe West 1</li>
 </ul></li>
-<li>“asia-east-1.tardigrade.io”
+<li>"asia-east-1.tardigrade.io"
 <ul>
 <li>Asia East 1</li>
 </ul></li>
 </ul></li>
 </ul>
-<h4 id="tardigrade-api-key">–tardigrade-api-key</h4>
+<h4 id="tardigrade-api-key">--tardigrade-api-key</h4>
 <p>API Key.</p>
 <ul>
 <li>Config: api_key</li>
@@ -15963,7 +16270,7 @@ y/e/d&gt; y</code></pre>
 <li>Type: string</li>
 <li>Default: ""</li>
 </ul>
-<h4 id="tardigrade-passphrase">–tardigrade-passphrase</h4>
+<h4 id="tardigrade-passphrase">--tardigrade-passphrase</h4>
 <p>Encryption Passphrase. To access existing objects enter passphrase used for uploading.</p>
 <ul>
 <li>Config: passphrase</li>
@@ -16135,7 +16442,7 @@ y/e/d&gt; y</code></pre>
 </tr>
 </tbody>
 </table>
-<h3 id="setup-4">Setup</h3>
+<h3 id="setup-2">Setup</h3>
 <p>Here is an example of how to make a union called <code>remote</code> for local folders. First run:</p>
 <pre><code> rclone config</code></pre>
 <p>This will guide you through an interactive setup process:</p>
@@ -16199,41 +16506,41 @@ e/n/d/r/c/s/q&gt; q</code></pre>
 <pre><code>rclone ls remote:</code></pre>
 <p>Copy another local directory to the union directory called source, which will be placed into <code>C:\dir3</code></p>
 <pre><code>rclone copy C:\source remote:source</code></pre>
-<h3 id="standard-options-31">Standard Options</h3>
+<h3 id="standard-options-16">Standard Options</h3>
 <p>Here are the standard options specific to union (Union merges the contents of several upstream fs).</p>
-<h4 id="union-upstreams">–union-upstreams</h4>
-<p>List of space separated upstreams. Can be ‘upstreama:test/dir upstreamb:’, ‘“upstreama:test/space:ro dir” upstreamb:’, etc.</p>
+<h4 id="union-upstreams">--union-upstreams</h4>
+<p>List of space separated upstreams. Can be 'upstreama:test/dir upstreamb:', '"upstreama:test/space:ro dir" upstreamb:', etc.</p>
 <ul>
 <li>Config: upstreams</li>
 <li>Env Var: RCLONE_UNION_UPSTREAMS</li>
 <li>Type: string</li>
 <li>Default: ""</li>
 </ul>
-<h4 id="union-action-policy">–union-action-policy</h4>
+<h4 id="union-action-policy">--union-action-policy</h4>
 <p>Policy to choose upstream on ACTION category.</p>
 <ul>
 <li>Config: action_policy</li>
 <li>Env Var: RCLONE_UNION_ACTION_POLICY</li>
 <li>Type: string</li>
-<li>Default: “epall”</li>
+<li>Default: "epall"</li>
 </ul>
-<h4 id="union-create-policy">–union-create-policy</h4>
+<h4 id="union-create-policy">--union-create-policy</h4>
 <p>Policy to choose upstream on CREATE category.</p>
 <ul>
 <li>Config: create_policy</li>
 <li>Env Var: RCLONE_UNION_CREATE_POLICY</li>
 <li>Type: string</li>
-<li>Default: “epmfs”</li>
+<li>Default: "epmfs"</li>
 </ul>
-<h4 id="union-search-policy">–union-search-policy</h4>
+<h4 id="union-search-policy">--union-search-policy</h4>
 <p>Policy to choose upstream on SEARCH category.</p>
 <ul>
 <li>Config: search_policy</li>
 <li>Env Var: RCLONE_UNION_SEARCH_POLICY</li>
 <li>Type: string</li>
-<li>Default: “ff”</li>
+<li>Default: "ff"</li>
 </ul>
-<h4 id="union-cache-time">–union-cache-time</h4>
+<h4 id="union-cache-time">--union-cache-time</h4>
 <p>Cache time of usage and free space (in seconds). This option is only useful when a path preserving policy is used.</p>
 <ul>
 <li>Config: cache_time</li>
@@ -16311,12 +16618,12 @@ y/e/d&gt; y</code></pre>
 <pre><code>rclone ls remote:</code></pre>
 <p>To copy a local directory to an WebDAV directory called backup</p>
 <pre><code>rclone copy /home/source remote:backup</code></pre>
-<h3 id="modified-time-and-hashes-11">Modified time and hashes</h3>
+<h3 id="modified-time-and-hashes-6">Modified time and hashes</h3>
 <p>Plain WebDAV does not support modified times. However when used with Owncloud or Nextcloud rclone will support modified times.</p>
 <p>Likewise plain WebDAV does not support hashes, however when used with Owncloud or Nextcloud rclone will support SHA1 and MD5 hashes. Depending on the exact version of Owncloud or Nextcloud hashes may appear on all objects, or only on objects which had a hash uploaded with them.</p>
-<h3 id="standard-options-32">Standard Options</h3>
+<h3 id="standard-options-17">Standard Options</h3>
 <p>Here are the standard options specific to webdav (Webdav).</p>
-<h4 id="webdav-url">–webdav-url</h4>
+<h4 id="webdav-url">--webdav-url</h4>
 <p>URL of http host to connect to</p>
 <ul>
 <li>Config: url</li>
@@ -16325,13 +16632,13 @@ y/e/d&gt; y</code></pre>
 <li>Default: ""</li>
 <li>Examples:
 <ul>
-<li>“https://example.com”
+<li>"https://example.com"
 <ul>
 <li>Connect to example.com</li>
 </ul></li>
 </ul></li>
 </ul>
-<h4 id="webdav-vendor">–webdav-vendor</h4>
+<h4 id="webdav-vendor">--webdav-vendor</h4>
 <p>Name of the Webdav site/service/software you are using</p>
 <ul>
 <li>Config: vendor</li>
@@ -16340,25 +16647,25 @@ y/e/d&gt; y</code></pre>
 <li>Default: ""</li>
 <li>Examples:
 <ul>
-<li>“nextcloud”
+<li>"nextcloud"
 <ul>
 <li>Nextcloud</li>
 </ul></li>
-<li>“owncloud”
+<li>"owncloud"
 <ul>
 <li>Owncloud</li>
 </ul></li>
-<li>“sharepoint”
+<li>"sharepoint"
 <ul>
 <li>Sharepoint</li>
 </ul></li>
-<li>“other”
+<li>"other"
 <ul>
 <li>Other site/service or software</li>
 </ul></li>
 </ul></li>
 </ul>
-<h4 id="webdav-user">–webdav-user</h4>
+<h4 id="webdav-user">--webdav-user</h4>
 <p>User name</p>
 <ul>
 <li>Config: user</li>
@@ -16366,15 +16673,16 @@ y/e/d&gt; y</code></pre>
 <li>Type: string</li>
 <li>Default: ""</li>
 </ul>
-<h4 id="webdav-pass">–webdav-pass</h4>
+<h4 id="webdav-pass">--webdav-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>
 <ul>
 <li>Config: pass</li>
 <li>Env Var: RCLONE_WEBDAV_PASS</li>
 <li>Type: string</li>
 <li>Default: ""</li>
 </ul>
-<h4 id="webdav-bearer-token">–webdav-bearer-token</h4>
+<h4 id="webdav-bearer-token">--webdav-bearer-token</h4>
 <p>Bearer token instead of user/pass (eg a Macaroon)</p>
 <ul>
 <li>Config: bearer_token</li>
@@ -16382,9 +16690,9 @@ y/e/d&gt; y</code></pre>
 <li>Type: string</li>
 <li>Default: ""</li>
 </ul>
-<h3 id="advanced-options-31">Advanced Options</h3>
+<h3 id="advanced-options-17">Advanced Options</h3>
 <p>Here are the advanced options specific to webdav (Webdav).</p>
-<h4 id="webdav-bearer-token-command">–webdav-bearer-token-command</h4>
+<h4 id="webdav-bearer-token-command">--webdav-bearer-token-command</h4>
 <p>Command to run to get a bearer token</p>
 <ul>
 <li>Config: bearer_token_command</li>
@@ -16401,13 +16709,13 @@ y/e/d&gt; y</code></pre>
 <p>This is configured in an identical way to Owncloud. Note that Nextcloud does not support streaming of files (<code>rcat</code>) whereas Owncloud does. This <a href="https://github.com/nextcloud/nextcloud-snap/issues/365">may be fixed</a> in the future.</p>
 <h3 id="sharepoint">Sharepoint</h3>
 <p>Rclone can be used with Sharepoint provided by OneDrive for Business or Office365 Education Accounts. This feature is only needed for a few of these Accounts, mostly Office365 Education ones. These accounts are sometimes not verified by the domain owner <a href="https://github.com/rclone/rclone/issues/1975">github#1975</a></p>
-<p>This means that these accounts can’t be added using the official API (other Accounts should work with the “onedrive” option). However, it is possible to access them using webdav.</p>
-<p>To use a sharepoint remote with rclone, add it like this: First, you need to get your remote’s URL:</p>
+<p>This means that these accounts can't be added using the official API (other Accounts should work with the "onedrive" option). However, it is possible to access them using webdav.</p>
+<p>To use a sharepoint remote with rclone, add it like this: First, you need to get your remote's URL:</p>
 <ul>
 <li>Go <a href="https://onedrive.live.com/about/en-us/signin/">here</a> to open your OneDrive or to sign in</li>
 <li>Now take a look at your address bar, the URL should look like this: <code>https://[YOUR-DOMAIN]-my.sharepoint.com/personal/[YOUR-EMAIL]/_layouts/15/onedrive.aspx</code></li>
 </ul>
-<p>You’ll only need this URL up to the email address. After that, you’ll most likely want to add “/Documents”. That subdirectory contains the actual data stored on your OneDrive.</p>
+<p>You'll only need this URL up to the email address. After that, you'll most likely want to add "/Documents". That subdirectory contains the actual data stored on your OneDrive.</p>
 <p>Add the remote to rclone like this: Configure the <code>url</code> as <code>https://[YOUR-DOMAIN]-my.sharepoint.com/personal/[YOUR-EMAIL]/Documents</code> and use your normal account email and password for <code>user</code> and <code>pass</code>. If you have 2FA enabled, you have to generate an app password. Set the <code>vendor</code> to <code>sharepoint</code>.</p>
 <p>Your config file should look like this:</p>
 <pre><code>[sharepoint]
@@ -16417,12 +16725,12 @@ vendor = other
 user = YourEmailAddress
 pass = encryptedpassword</code></pre>
 <h4 id="required-flags-for-sharepoint">Required Flags for SharePoint</h4>
-<p>As SharePoint does some special things with uploaded documents, you won’t be able to use the documents size or the documents hash to compare if a file has been changed since the upload / which file is newer.</p>
-<p>For Rclone calls copying files (especially Office files such as .docx, .xlsx, etc.) from/to SharePoint (like copy, sync, etc.), you should append these flags to ensure Rclone uses the “Last Modified” datetime property to compare your documents:</p>
+<p>As SharePoint does some special things with uploaded documents, you won't be able to use the documents size or the documents hash to compare if a file has been changed since the upload / which file is newer.</p>
+<p>For Rclone calls copying files (especially Office files such as .docx, .xlsx, etc.) from/to SharePoint (like copy, sync, etc.), you should append these flags to ensure Rclone uses the "Last Modified" datetime property to compare your documents:</p>
 <pre><code>--ignore-size --ignore-checksum --update</code></pre>
 <h3 id="dcache">dCache</h3>
 <p>dCache is a storage system that supports many protocols and authentication/authorisation schemes. For WebDAV clients, it allows users to authenticate with username and password (BASIC), X.509, Kerberos, and various bearer tokens, including <a href="https://www.dcache.org/manuals/workshop-2017-05-29-Umea/000-Final/anupam_macaroons_v02.pdf">Macaroons</a> and <a href="https://en.wikipedia.org/wiki/OpenID_Connect">OpenID-Connect</a> access tokens.</p>
-<p>Configure as normal using the <code>other</code> type. Don’t enter a username or password, instead enter your Macaroon as the <code>bearer_token</code>.</p>
+<p>Configure as normal using the <code>other</code> type. Don't enter a username or password, instead enter your Macaroon as the <code>bearer_token</code>.</p>
 <p>The config will end up looking something like this.</p>
 <pre><code>[dcache]
 type = webdav
@@ -16441,7 +16749,7 @@ eyJraWQ[...]QFXDt0
 paul@celebrimbor:~$</code></pre>
 <p><strong>Note</strong> Before the <code>oidc-token</code> command will work, the refresh token must be loaded into the oidc agent. This is done with the <code>oidc-add</code> command (e.g., <code>oidc-add XDC</code>). This is typically done once per login session. Full details on this and how to register oidc-agent with your OIDC Provider are provided in the <a href="https://indigo-dc.gitbooks.io/oidc-agent/">oidc-agent documentation</a>.</p>
 <p>The rclone <code>bearer_token_command</code> configuration option is used to fetch the access token from oidc-agent.</p>
-<p>Configure as a normal WebDAV endpoint, using the ‘other’ vendor, leaving the username and password empty. When prompted, choose to edit the advanced config and enter the command to get a bearer token (e.g., <code>oidc-agent XDC</code>).</p>
+<p>Configure as a normal WebDAV endpoint, using the 'other' vendor, leaving the username and password empty. When prompted, choose to edit the advanced config and enter the command to get a bearer token (e.g., <code>oidc-agent XDC</code>).</p>
 <p>The following example config shows a WebDAV endpoint that uses oidc-agent to supply an access token from the <em>XDC</em> OIDC Provider.</p>
 <pre><code>[dcache]
 type = webdav
@@ -16500,50 +16808,66 @@ y/e/d&gt; y</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 /home/local/directory remote:directory</code></pre>
+<pre><code>rclone sync -i /home/local/directory remote:directory</code></pre>
 <p>Yandex paths may be as deep as required, eg <code>remote:directory/subdirectory</code>.</p>
-<h3 id="modified-time-13">Modified time</h3>
+<h3 id="modified-time-6">Modified time</h3>
 <p>Modified times are supported and are stored accurate to 1 ns in custom metadata called <code>rclone_modified</code> in RFC3339 with nanoseconds format.</p>
 <h3 id="md5-checksums">MD5 checksums</h3>
 <p>MD5 checksums are natively supported by Yandex Disk.</p>
-<h3 id="emptying-trash-2">Emptying Trash</h3>
+<h3 id="emptying-trash-1">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>
-<h3 id="quota-information-3">Quota information</h3>
+<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>
-<h4 id="restricted-filename-characters-25">Restricted filename characters</h4>
+<h4 id="restricted-filename-characters-15">Restricted filename characters</h4>
 <p>The <a href="https://rclone.org/overview/#restricted-characters">default restricted characters set</a> are 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="limitations-20">Limitations</h3>
-<p>When uploading very large files (bigger than about 5GB) you will need to increase the <code>--timeout</code> parameter. This is because Yandex pauses (perhaps to calculate the MD5SUM for the entire file) before returning confirmation that the file has been uploaded. The default handling of timeouts in rclone is to assume a 5 minute pause is an error and close the connection - you’ll see <code>net/http: timeout awaiting response headers</code> errors in the logs if this is happening. Setting the timeout to twice the max size of file in GB should be enough, so if you want to upload a 30GB file set a timeout of <code>2 * 30 = 60m</code>, that is <code>--timeout 60m</code>.</p>
-<h3 id="standard-options-33">Standard Options</h3>
+<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="limitations-13">Limitations</h3>
+<p>When uploading very large files (bigger than about 5GB) you will need to increase the <code>--timeout</code> parameter. This is because Yandex pauses (perhaps to calculate the MD5SUM for the entire file) before returning confirmation that the file has been uploaded. The default handling of timeouts in rclone is to assume a 5 minute pause is an error and close the connection - you'll see <code>net/http: timeout awaiting response headers</code> errors in the logs if this is happening. Setting the timeout to twice the max size of file in GB should be enough, so if you want to upload a 30GB file set a timeout of <code>2 * 30 = 60m</code>, that is <code>--timeout 60m</code>.</p>
+<h3 id="standard-options-18">Standard Options</h3>
 <p>Here are the standard options specific to yandex (Yandex Disk).</p>
-<h4 id="yandex-client-id">–yandex-client-id</h4>
-<p>Yandex Client Id Leave blank normally.</p>
+<h4 id="yandex-client-id">--yandex-client-id</h4>
+<p>OAuth Client Id Leave blank normally.</p>
 <ul>
 <li>Config: client_id</li>
 <li>Env Var: RCLONE_YANDEX_CLIENT_ID</li>
 <li>Type: string</li>
 <li>Default: ""</li>
 </ul>
-<h4 id="yandex-client-secret">–yandex-client-secret</h4>
-<p>Yandex Client Secret Leave blank normally.</p>
+<h4 id="yandex-client-secret">--yandex-client-secret</h4>
+<p>OAuth Client Secret Leave blank normally.</p>
 <ul>
 <li>Config: client_secret</li>
 <li>Env Var: RCLONE_YANDEX_CLIENT_SECRET</li>
 <li>Type: string</li>
 <li>Default: ""</li>
 </ul>
-<h3 id="advanced-options-32">Advanced Options</h3>
+<h3 id="advanced-options-18">Advanced Options</h3>
 <p>Here are the advanced options specific to yandex (Yandex Disk).</p>
-<h4 id="yandex-unlink">–yandex-unlink</h4>
-<p>Remove existing public link to file/folder with link command rather than creating. Default is false, meaning link command will create or retrieve public link.</p>
+<h4 id="yandex-token">--yandex-token</h4>
+<p>OAuth Access Token as a JSON blob.</p>
 <ul>
-<li>Config: unlink</li>
-<li>Env Var: RCLONE_YANDEX_UNLINK</li>
-<li>Type: bool</li>
-<li>Default: false</li>
+<li>Config: token</li>
+<li>Env Var: RCLONE_YANDEX_TOKEN</li>
+<li>Type: string</li>
+<li>Default: ""</li>
 </ul>
-<h4 id="yandex-encoding">–yandex-encoding</h4>
+<h4 id="yandex-auth-url">--yandex-auth-url</h4>
+<p>Auth server URL. Leave blank to use the provider defaults.</p>
+<ul>
+<li>Config: auth_url</li>
+<li>Env Var: RCLONE_YANDEX_AUTH_URL</li>
+<li>Type: string</li>
+<li>Default: ""</li>
+</ul>
+<h4 id="yandex-token-url">--yandex-token-url</h4>
+<p>Token server url. Leave blank to use the provider defaults.</p>
+<ul>
+<li>Config: token_url</li>
+<li>Env Var: RCLONE_YANDEX_TOKEN_URL</li>
+<li>Type: string</li>
+<li>Default: ""</li>
+</ul>
+<h4 id="yandex-encoding">--yandex-encoding</h4>
 <p>This sets 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>
 <ul>
@@ -16554,17 +16878,17 @@ y/e/d&gt; y</code></pre>
 </ul>
 <h2 id="local-filesystem">Local Filesystem</h2>
 <p>Local paths are specified as normal filesystem paths, eg <code>/path/to/wherever</code>, so</p>
-<pre><code>rclone sync /home/source /tmp/destination</code></pre>
+<pre><code>rclone sync -i /home/source /tmp/destination</code></pre>
 <p>Will sync <code>/home/source</code> to <code>/tmp/destination</code></p>
 <p>These can be configured into the config file for consistencies sake, but it is probably easier not to.</p>
-<h3 id="modified-time-14">Modified time</h3>
+<h3 id="modified-time-7">Modified time</h3>
 <p>Rclone reads and writes the modified time using an accuracy determined by the OS. Typically this is 1ns on Linux, 10 ns on Windows and 1 Second on OS X.</p>
 <h3 id="filenames">Filenames</h3>
 <p>Filenames should be encoded in UTF-8 on disk. This is the normal case for Windows and OS X.</p>
-<p>There is a bit more uncertainty in the Linux world, but new distributions will have UTF-8 encoded files names. If you are using an old Linux filesystem with non UTF-8 file names (eg latin1) then you can use the <code>convmv</code> tool to convert the filesystem to UTF-8. This tool is available in most distributions’ package managers.</p>
+<p>There is a bit more uncertainty in the Linux world, but new distributions will have UTF-8 encoded files names. If you are using an old Linux filesystem with non UTF-8 file names (eg latin1) then you can use the <code>convmv</code> tool to convert the filesystem to UTF-8. This tool is available in most distributions' package managers.</p>
 <p>If an invalid (non-UTF8) filename is read, the invalid characters will be replaced with a quoted representation of the invalid bytes. The name <code>gro\xdf</code> will be transferred as <code>gro‛DF</code>. <code>rclone</code> will emit a debug message in this case (use <code>-v</code> to see), eg</p>
 <pre><code>Local file system at .: Replacing invalid UTF-8 characters in &quot;gro\xdf&quot;</code></pre>
-<h4 id="restricted-characters-1">Restricted characters</h4>
+<h4 id="restricted-characters">Restricted characters</h4>
 <p>On non Windows platforms the following characters are replaced when handling file names.</p>
 <table>
 <thead>
@@ -16826,7 +17150,7 @@ y/e/d&gt; y</code></pre>
 </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 converted to UTF-16.</p>
+<p>Invalid UTF-8 bytes will also be <a href="https://rclone.org/overview/#invalid-utf8">replaced</a>, as they can't be converted to UTF-16.</p>
 <h3 id="long-paths-on-windows">Long paths on Windows</h3>
 <p>Rclone handles long paths automatically, by converting all paths to long <a href="https://msdn.microsoft.com/en-us/library/windows/desktop/aa365247(v=vs.85).aspx#maxpath">UNC paths</a> which allows paths up to 32,767 characters.</p>
 <p>This is why you will see that your paths, for instance <code>c:\files</code> is converted to the UNC path <code>\\?\c:\files</code> in the output, and <code>\\server\share</code> is converted to <code>\\?\UNC\server\share</code>.</p>
@@ -16863,9 +17187,9 @@ nounc = true</code></pre>
         6 two/three
         6 b/two
         6 b/one</code></pre>
-<h4 id="links--l">–links, -l</h4>
+<h4 id="links--l">--links, -l</h4>
 <p>Normally rclone will ignore symlinks or junction points (which behave like symlinks under Windows).</p>
-<p>If you supply this flag then rclone will copy symbolic links from the local storage, and store them as text files, with a ‘.rclonelink’ suffix in the remote storage.</p>
+<p>If you supply this flag then rclone will copy symbolic links from the local storage, and store them as text files, with a '.rclonelink' suffix in the remote storage.</p>
 <p>The text file will contain the target of the symbolic link (see example).</p>
 <p>This flag applies to all commands.</p>
 <p>For example, supposing you have a directory structure like this</p>
@@ -16873,9 +17197,9 @@ nounc = true</code></pre>
 /tmp/a
 ├── file1 -&gt; ./file4
 └── file2 -&gt; /home/user/file3</code></pre>
-<p>Copying the entire directory with ‘-l’</p>
+<p>Copying the entire directory with '-l'</p>
 <pre><code>$ rclone copyto -l /tmp/a/file1 remote:/tmp/a/</code></pre>
-<p>The remote files are created with a ‘.rclonelink’ suffix</p>
+<p>The remote files are created with a '.rclonelink' suffix</p>
 <pre><code>$ rclone ls remote:/tmp/a
        5 file1.rclonelink
       14 file2.rclonelink</code></pre>
@@ -16885,14 +17209,14 @@ nounc = true</code></pre>
 
 $ rclone cat remote:/tmp/a/file2.rclonelink
 /home/user/file3</code></pre>
-<p>Copying them back with ‘-l’</p>
+<p>Copying them back with '-l'</p>
 <pre><code>$ rclone copyto -l remote:/tmp/a/ /tmp/b/
 
 $ tree /tmp/b
 /tmp/b
 ├── file1 -&gt; ./file4
 └── file2 -&gt; /home/user/file3</code></pre>
-<p>However, if copied back without ‘-l’</p>
+<p>However, if copied back without '-l'</p>
 <pre><code>$ rclone copyto remote:/tmp/a/ /tmp/b/
 
 $ tree /tmp/b
@@ -16900,7 +17224,7 @@ $ tree /tmp/b
 ├── file1.rclonelink
 └── file2.rclonelink</code></pre>
 <p>Note that this flag is incompatible with <code>-copy-links</code> / <code>-L</code>.</p>
-<h3 id="restricting-filesystems-with-one-file-system">Restricting filesystems with –one-file-system</h3>
+<h3 id="restricting-filesystems-with---one-file-system">Restricting filesystems with --one-file-system</h3>
 <p>Normally rclone will recurse through filesystems as mounted.</p>
 <p>However if you set <code>--one-file-system</code> or <code>-x</code> this tells rclone to stay in the filesystem specified by the root and not to recurse into different file systems.</p>
 <p>For example if you have a directory hierarchy like this</p>
@@ -16921,10 +17245,10 @@ $ tree /tmp/b
         0 file1
         0 file2</code></pre>
 <p><strong>NB</strong> Rclone (like most unix tools such as <code>du</code>, <code>rsync</code> and <code>tar</code>) treats a bind mount to the same device as being on the same filesystem.</p>
-<p><strong>NB</strong> This flag is only available on Unix based systems. On systems where it isn’t supported (eg Windows) it will be ignored.</p>
-<h3 id="standard-options-34">Standard Options</h3>
+<p><strong>NB</strong> This flag is only available on Unix based systems. On systems where it isn't supported (eg Windows) it will be ignored.</p>
+<h3 id="standard-options-19">Standard Options</h3>
 <p>Here are the standard options specific to local (Local Disk).</p>
-<h4 id="local-nounc">–local-nounc</h4>
+<h4 id="local-nounc">--local-nounc</h4>
 <p>Disable UNC (long path names) conversion on Windows</p>
 <ul>
 <li>Config: nounc</li>
@@ -16933,15 +17257,15 @@ $ tree /tmp/b
 <li>Default: ""</li>
 <li>Examples:
 <ul>
-<li>“true”
+<li>"true"
 <ul>
 <li>Disables long file names</li>
 </ul></li>
 </ul></li>
 </ul>
-<h3 id="advanced-options-33">Advanced Options</h3>
+<h3 id="advanced-options-19">Advanced Options</h3>
 <p>Here are the advanced options specific to local (Local Disk).</p>
-<h4 id="copy-links--l">–copy-links / -L</h4>
+<h4 id="copy-links--l">--copy-links / -L</h4>
 <p>Follow symlinks and copy the pointed to item.</p>
 <ul>
 <li>Config: copy_links</li>
@@ -16949,24 +17273,24 @@ $ tree /tmp/b
 <li>Type: bool</li>
 <li>Default: false</li>
 </ul>
-<h4 id="links--l-1">–links / -l</h4>
-<p>Translate symlinks to/from regular files with a ‘.rclonelink’ extension</p>
+<h4 id="links--l-1">--links / -l</h4>
+<p>Translate symlinks to/from regular files with a '.rclonelink' extension</p>
 <ul>
 <li>Config: links</li>
 <li>Env Var: RCLONE_LOCAL_LINKS</li>
 <li>Type: bool</li>
 <li>Default: false</li>
 </ul>
-<h4 id="skip-links">–skip-links</h4>
-<p>Don’t warn about skipped symlinks. This flag disables warning messages on skipped symlinks or junction points, as you explicitly acknowledge that they should be skipped.</p>
+<h4 id="skip-links">--skip-links</h4>
+<p>Don't warn about skipped symlinks. This flag disables warning messages on skipped symlinks or junction points, as you explicitly acknowledge that they should be skipped.</p>
 <ul>
 <li>Config: skip_links</li>
 <li>Env Var: RCLONE_LOCAL_SKIP_LINKS</li>
 <li>Type: bool</li>
 <li>Default: false</li>
 </ul>
-<h4 id="local-no-unicode-normalization">–local-no-unicode-normalization</h4>
-<p>Don’t apply unicode normalization to paths and filenames (Deprecated)</p>
+<h4 id="local-no-unicode-normalization">--local-no-unicode-normalization</h4>
+<p>Don't apply unicode normalization to paths and filenames (Deprecated)</p>
 <p>This flag is deprecated now. Rclone no longer normalizes unicode file names, but it compares them with unicode normalization in the sync routine instead.</p>
 <ul>
 <li>Config: no_unicode_normalization</li>
@@ -16974,25 +17298,31 @@ $ tree /tmp/b
 <li>Type: bool</li>
 <li>Default: false</li>
 </ul>
-<h4 id="local-no-check-updated">–local-no-check-updated</h4>
-<p>Don’t check to see if the files change during upload</p>
-<p>Normally rclone checks the size and modification time of files as they are being uploaded and aborts with a message which starts “can’t copy - source file is being updated” if the file changes during upload.</p>
+<h4 id="local-no-check-updated">--local-no-check-updated</h4>
+<p>Don't check to see if the files change during upload</p>
+<p>Normally rclone checks the size and modification time of files as they are being uploaded and aborts with a message which starts "can't copy - source file is being updated" if the file changes during upload.</p>
 <p>However on some file systems this modification time check may fail (eg <a href="https://github.com/rclone/rclone/issues/2206">Glusterfs #2206</a>) so this check can be disabled with this flag.</p>
+<p>If this flag is set, rclone will use its best efforts to transfer a file which is being updated. If the file is only having things appended to it (eg a log) then rclone will transfer the log file with the size it had the first time rclone saw it.</p>
+<p>If the file is being modified throughout (not just appended to) then the transfer may fail with a hash check failure.</p>
+<p>In detail, once the file has had stat() called on it for the first time we:</p>
 <ul>
+<li>Only transfer the size that stat gave</li>
+<li>Only checksum the size that stat gave</li>
+<li><p>Don't update the stat info for the file</p></li>
 <li>Config: no_check_updated</li>
 <li>Env Var: RCLONE_LOCAL_NO_CHECK_UPDATED</li>
 <li>Type: bool</li>
-<li>Default: false</li>
+<li><p>Default: false</p></li>
 </ul>
-<h4 id="one-file-system--x">–one-file-system / -x</h4>
-<p>Don’t cross filesystem boundaries (unix/macOS only).</p>
+<h4 id="one-file-system--x">--one-file-system / -x</h4>
+<p>Don't cross filesystem boundaries (unix/macOS only).</p>
 <ul>
 <li>Config: one_file_system</li>
 <li>Env Var: RCLONE_LOCAL_ONE_FILE_SYSTEM</li>
 <li>Type: bool</li>
 <li>Default: false</li>
 </ul>
-<h4 id="local-case-sensitive">–local-case-sensitive</h4>
+<h4 id="local-case-sensitive">--local-case-sensitive</h4>
 <p>Force the filesystem to report itself as case sensitive.</p>
 <p>Normally the local backend declares itself as case insensitive on Windows/macOS and case sensitive for everything else. Use this flag to override the default choice.</p>
 <ul>
@@ -17001,7 +17331,7 @@ $ tree /tmp/b
 <li>Type: bool</li>
 <li>Default: false</li>
 </ul>
-<h4 id="local-case-insensitive">–local-case-insensitive</h4>
+<h4 id="local-case-insensitive">--local-case-insensitive</h4>
 <p>Force the filesystem to report itself as case insensitive</p>
 <p>Normally the local backend declares itself as case insensitive on Windows/macOS and case sensitive for everything else. Use this flag to override the default choice.</p>
 <ul>
@@ -17010,7 +17340,7 @@ $ tree /tmp/b
 <li>Type: bool</li>
 <li>Default: false</li>
 </ul>
-<h4 id="local-no-sparse">–local-no-sparse</h4>
+<h4 id="local-no-sparse">--local-no-sparse</h4>
 <p>Disable sparse files for multi-thread downloads</p>
 <p>On Windows platforms rclone will make sparse files when doing multi-thread downloads. This avoids long pauses on large files where the OS zeros the file. However sparse files may be undesirable as they cause disk fragmentation and can be slow to work with.</p>
 <ul>
@@ -17019,7 +17349,16 @@ $ tree /tmp/b
 <li>Type: bool</li>
 <li>Default: false</li>
 </ul>
-<h4 id="local-encoding">–local-encoding</h4>
+<h4 id="local-no-set-modtime">--local-no-set-modtime</h4>
+<p>Disable setting modtime</p>
+<p>Normally rclone updates modification time of files after they are done uploading. This can cause permissions issues on Linux platforms when the user rclone is running as does not own the file uploaded, such as when copying to a CIFS mount owned by another user. If this option is enabled, rclone will no longer update the modtime after copying a file.</p>
+<ul>
+<li>Config: no_set_modtime</li>
+<li>Env Var: RCLONE_LOCAL_NO_SET_MODTIME</li>
+<li>Type: bool</li>
+<li>Default: false</li>
+</ul>
+<h4 id="local-encoding">--local-encoding</h4>
 <p>This sets 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>
 <ul>
@@ -17028,12 +17367,12 @@ $ tree /tmp/b
 <li>Type: MultiEncoder</li>
 <li>Default: Slash,Dot</li>
 </ul>
-<h3 id="backend-commands-3">Backend commands</h3>
+<h3 id="backend-commands">Backend commands</h3>
 <p>Here are the commands specific to the local 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 <a href="https://rclone.org/commands/rclone_backend/">the “rclone backend” command</a> for more info on how to pass options and arguments.</p>
+<p>See <a href="https://rclone.org/commands/rclone_backend/">the "rclone backend" command</a> 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>
 <h4 id="noop">noop</h4>
 <p>A null operation for testing backend commands</p>
@@ -17041,10 +17380,391 @@ $ tree /tmp/b
 <p>This is a test command which has some options you can try to change the output.</p>
 <p>Options:</p>
 <ul>
-<li>“echo”: echo the input arguments</li>
-<li>“error”: return an error based on option value</li>
+<li>"echo": echo the input arguments</li>
+<li>"error": return an error based on option value</li>
 </ul>
 <h1 id="changelog">Changelog</h1>
+<h2 id="v1.53.0---2020-09-02">v1.53.0 - 2020-09-02</h2>
+<p><a href="https://github.com/rclone/rclone/compare/v1.52.0...v1.53.0">See commits</a></p>
+<ul>
+<li>New Features
+<ul>
+<li>The <a href="https://rclone.org/commands/rclone_mount/#vfs-virtual-file-system">VFS layer</a> was heavily reworked for this release - see below for more details</li>
+<li>Interactive mode <a href="https://rclone.org/docs/#interactive">-i/--interactive</a> for destructive operations (fishbullet)</li>
+<li>Add <a href="https://rclone.org/docs/#bwlimit-file-bandwidth-spec">--bwlimit-file</a> flag to limit speeds of individual file transfers (Nick Craig-Wood)</li>
+<li>Transfers are sorted by start time in the stats and progress output (Max Sum)</li>
+<li>Make sure backends expand <code>~</code> and environment vars in file names they use (Nick Craig-Wood)</li>
+<li>Add <a href="https://rclone.org/docs/#refresh-times">--refresh-times</a> flag to set modtimes on hashless backends (Nick Craig-Wood)</li>
+<li>build
+<ul>
+<li>Remove vendor directory in favour of Go modules (Nick Craig-Wood)</li>
+<li>Build with go1.15.x by default (Nick Craig-Wood)</li>
+<li>Drop macOS 386 build as it is no longer supported by go1.15 (Nick Craig-Wood)</li>
+<li>Add ARMv7 to the supported builds (Nick Craig-Wood)</li>
+<li>Enable <code>rclone cmount</code> on macOS (Nick Craig-Wood)</li>
+<li>Make rclone build with gccgo (Nick Craig-Wood)</li>
+<li>Make rclone build with wasm (Nick Craig-Wood)</li>
+<li>Change beta numbering to be semver compatible (Nick Craig-Wood)</li>
+<li>Add file properties and icon to Windows executable (albertony)</li>
+<li>Add experimental interface for integrating rclone into browsers (Nick Craig-Wood)</li>
+</ul></li>
+<li>lib: Add file name compression (Klaus Post)</li>
+<li>rc
+<ul>
+<li>Allow installation and use of plugins and test plugins with rclone-webui (Chaitanya Bankanhal)</li>
+<li>Add reverse proxy pluginsHandler for serving plugins (Chaitanya Bankanhal)</li>
+<li>Add <code>mount/listmounts</code> option for listing current mounts (Chaitanya Bankanhal)</li>
+<li>Add <code>operations/uploadfile</code> to upload a file through rc using encoding multipart/form-data (Chaitanya Bankanhal)</li>
+<li>Add <code>core/copmmand</code> to execute rclone terminal commands. (Chaitanya Bankanhal)</li>
+</ul></li>
+<li><code>rclone check</code>
+<ul>
+<li>Add reporting of filenames for same/missing/changed (Nick Craig-Wood)</li>
+<li>Make check command obey <code>--dry-run</code>/<code>-i</code>/<code>--interactive</code> (Nick Craig-Wood)</li>
+<li>Make check do <code>--checkers</code> files concurrently (Nick Craig-Wood)</li>
+<li>Retry downloads if they fail when using the <code>--download</code> flag (Nick Craig-Wood)</li>
+<li>Make it show stats by default (Nick Craig-Wood)</li>
+</ul></li>
+<li><code>rclone obscure</code>: Allow obscure command to accept password on STDIN (David Ibarra)</li>
+<li><code>rclone config</code>
+<ul>
+<li>Set RCLONE_CONFIG_DIR for use in config files and subprocesses (Nick Craig-Wood)</li>
+<li>Reject remote names starting with a dash. (jtagcat)</li>
+</ul></li>
+<li><code>rclone cryptcheck</code>: Add reporting of filenames for same/missing/changed (Nick Craig-Wood)</li>
+<li><code>rclone dedupe</code>: Make it obey the <code>--size-only</code> flag for duplicate detection (Nick Craig-Wood)</li>
+<li><code>rclone link</code>: Add <code>--expire</code> and <code>--unlink</code> flags (Roman Kredentser)</li>
+<li><code>rclone mkdir</code>: Warn when using mkdir on remotes which can't have empty directories (Nick Craig-Wood)</li>
+<li><code>rclone rc</code>: Allow JSON parameters to simplify command line usage (Nick Craig-Wood)</li>
+<li><code>rclone serve ftp</code>
+<ul>
+<li>Don't compile on &lt; go1.13 after dependency update (Nick Craig-Wood)</li>
+<li>Add error message if auth proxy fails (Nick Craig-Wood)</li>
+<li>Use refactored goftp.io/server library for binary shrink (Nick Craig-Wood)</li>
+</ul></li>
+<li><code>rclone serve restic</code>: Expose interfaces so that rclone can be used as a library from within restic (Jack)</li>
+<li><code>rclone sync</code>: Add <code>--track-renames-strategy leaf</code> (Nick Craig-Wood)</li>
+<li><code>rclone touch</code>: Add ability to set nanosecond resolution times (Nick Craig-Wood)</li>
+<li><code>rclone tree</code>: Remove <code>-i</code> shorthand for <code>--noindent</code> as it conflicts with <code>-i</code>/<code>--interactive</code> (Nick Craig-Wood)</li>
+</ul></li>
+<li>Bug Fixes
+<ul>
+<li>accounting
+<ul>
+<li>Fix documentation for <code>speed</code>/<code>speedAvg</code> (Nick Craig-Wood)</li>
+<li>Fix elapsed time not show actual time since beginning (Chaitanya Bankanhal)</li>
+<li>Fix deadlock in stats printing (Nick Craig-Wood)</li>
+</ul></li>
+<li>build
+<ul>
+<li>Fix file handle leak in GitHub release tool (Garrett Squire)</li>
+</ul></li>
+<li><code>rclone check</code>: Fix successful retries with <code>--download</code> counting errors (Nick Craig-Wood)</li>
+<li><code>rclone dedupe</code>: Fix logging to be easier to understand (Nick Craig-Wood)</li>
+</ul></li>
+<li>Mount
+<ul>
+<li>Warn macOS users that mount implementation is changing (Nick Craig-Wood)
+<ul>
+<li>to test the new implementation use <code>rclone cmount</code> instead of <code>rclone mount</code></li>
+<li>this is because the library rclone uses has dropped macOS support</li>
+</ul></li>
+<li>rc interface
+<ul>
+<li>Add call for unmount all (Chaitanya Bankanhal)</li>
+<li>Make <code>mount/mount</code> remote control take vfsOpt option (Nick Craig-Wood)</li>
+<li>Add mountOpt to <code>mount/mount</code> (Nick Craig-Wood)</li>
+<li>Add VFS and Mount options to <code>mount/listmounts</code> (Nick Craig-Wood)</li>
+</ul></li>
+<li>Catch panics in cgofuse initialization and turn into error messages (Nick Craig-Wood)</li>
+<li>Always supply stat information in Readdir (Nick Craig-Wood)</li>
+<li>Add support for reading unknown length files using direct IO (Windows) (Nick Craig-Wood)</li>
+<li>Fix On Windows don't add <code>-o uid/gid=-1</code> if user supplies <code>-o uid/gid</code>. (Nick Craig-Wood)</li>
+<li>Fix macOS losing directory contents in cmount (Nick Craig-Wood)</li>
+<li>Fix volume name broken in recent refactor (Nick Craig-Wood)</li>
+</ul></li>
+<li>VFS
+<ul>
+<li>Implement partial reads for <code>--vfs-cache-mode full</code> (Nick Craig-Wood)</li>
+<li>Add <code>--vfs-writeback</code> option to delay writes back to cloud storage (Nick Craig-Wood)</li>
+<li>Add <code>--vfs-read-ahead</code> parameter for use with <code>--vfs-cache-mode full</code> (Nick Craig-Wood)</li>
+<li>Restart pending uploads on restart of the cache (Nick Craig-Wood)</li>
+<li>Support synchronous cache space recovery upon ENOSPC (Leo Luan)</li>
+<li>Allow ReadAt and WriteAt to run concurrently with themselves (Nick Craig-Wood)</li>
+<li>Change modtime of file before upload to current (Rob Calistri)</li>
+<li>Recommend <code>--vfs-cache-modes writes</code> on backends which can't stream (Nick Craig-Wood)</li>
+<li>Add an optional <code>fs</code> parameter to vfs rc methods (Nick Craig-Wood)</li>
+<li>Fix errors when using &gt; 260 char files in the cache in Windows (Nick Craig-Wood)</li>
+<li>Fix renaming of items while they are being uploaded (Nick Craig-Wood)</li>
+<li>Fix very high load caused by slow directory listings (Nick Craig-Wood)</li>
+<li>Fix renamed files not being uploaded with <code>--vfs-cache-mode minimal</code> (Nick Craig-Wood)</li>
+<li>Fix directory locking caused by slow directory listings (Nick Craig-Wood)</li>
+<li>Fix saving from chrome without <code>--vfs-cache-mode writes</code> (Nick Craig-Wood)</li>
+</ul></li>
+<li>Local
+<ul>
+<li>Add <code>--local-no-updated</code> to provide a consistent view of changing objects (Nick Craig-Wood)</li>
+<li>Add <code>--local-no-set-modtime</code> option to prevent modtime changes (tyhuber1)</li>
+<li>Fix race conditions updating and reading Object metadata (Nick Craig-Wood)</li>
+</ul></li>
+<li>Cache
+<ul>
+<li>Make any created backends be cached to fix rc problems (Nick Craig-Wood)</li>
+<li>Fix dedupe on caches wrapping drives (Nick Craig-Wood)</li>
+</ul></li>
+<li>Crypt
+<ul>
+<li>Add <code>--crypt-server-side-across-configs</code> flag (Nick Craig-Wood)</li>
+<li>Make any created backends be cached to fix rc problems (Nick Craig-Wood)</li>
+</ul></li>
+<li>Alias
+<ul>
+<li>Make any created backends be cached to fix rc problems (Nick Craig-Wood)</li>
+</ul></li>
+<li>Azure Blob
+<ul>
+<li>Don't compile on &lt; go1.13 after dependency update (Nick Craig-Wood)</li>
+</ul></li>
+<li>B2
+<ul>
+<li>Implement server side copy for files &gt; 5GB (Nick Craig-Wood)</li>
+<li>Cancel in progress multipart uploads and copies on rclone exit (Nick Craig-Wood)</li>
+<li>Note that b2's encoding now allows  but rclone's hasn't changed (Nick Craig-Wood)</li>
+<li>Fix transfers when using download_url (Nick Craig-Wood)</li>
+</ul></li>
+<li>Box
+<ul>
+<li>Implement rclone cleanup (buengese)</li>
+<li>Cancel in progress multipart uploads and copies on rclone exit (Nick Craig-Wood)</li>
+<li>Allow authentication with access token (David)</li>
+</ul></li>
+<li>Chunker
+<ul>
+<li>Make any created backends be cached to fix rc problems (Nick Craig-Wood)</li>
+</ul></li>
+<li>Drive
+<ul>
+<li>Add <code>rclone backend drives</code> to list shared drives (teamdrives) (Nick Craig-Wood)</li>
+<li>Implement <code>rclone backend untrash</code> (Nick Craig-Wood)</li>
+<li>Work around drive bug which didn't set modtime of copied docs (Nick Craig-Wood)</li>
+<li>Added <code>--drive-starred-only</code> to only show starred files (Jay McEntire)</li>
+<li>Deprecate <code>--drive-alternate-export</code> as it is no longer needed (themylogin)</li>
+<li>Fix duplication of Google docs on server side copy (Nick Craig-Wood)</li>
+<li>Fix "panic: send on closed channel" when recycling dir entries (Nick Craig-Wood)</li>
+</ul></li>
+<li>Dropbox
+<ul>
+<li>Add copyright detector info in limitations section in the docs (Alex Guerrero)</li>
+<li>Fix <code>rclone link</code> by removing expires parameter (Nick Craig-Wood)</li>
+</ul></li>
+<li>Fichier
+<ul>
+<li>Detect Flood detected: IP Locked error and sleep for 30s (Nick Craig-Wood)</li>
+</ul></li>
+<li>FTP
+<ul>
+<li>Add explicit TLS support (Heiko Bornholdt)</li>
+<li>Add support for <code>--dump bodies</code> and <code>--dump auth</code> for debugging (Nick Craig-Wood)</li>
+<li>Fix interoperation with pure-ftpd (Nick Craig-Wood)</li>
+</ul></li>
+<li>Google Cloud Storage
+<ul>
+<li>Add support for anonymous access (Kai Lüke)</li>
+</ul></li>
+<li>Jottacloud
+<ul>
+<li>Bring back legacy authentification for use with whitelabel versions (buengese)</li>
+<li>Switch to new api root - also implement a very ugly workaround for the DirMove failures (buengese)</li>
+</ul></li>
+<li>Onedrive
+<ul>
+<li>Rework cancel of multipart uploads on rclone exit (Nick Craig-Wood)</li>
+<li>Implement rclone cleanup (Nick Craig-Wood)</li>
+<li>Add <code>--onedrive-no-versions</code> flag to remove old versions (Nick Craig-Wood)</li>
+</ul></li>
+<li>Pcloud
+<ul>
+<li>Implement <code>rclone link</code> for public link creation (buengese)</li>
+</ul></li>
+<li>Qingstor
+<ul>
+<li>Cancel in progress multipart uploads on rclone exit (Nick Craig-Wood)</li>
+</ul></li>
+<li>S3
+<ul>
+<li>Preserve metadata when doing multipart copy (Nick Craig-Wood)</li>
+<li>Cancel in progress multipart uploads and copies on rclone exit (Nick Craig-Wood)</li>
+<li>Add <code>rclone link</code> for public link sharing (Roman Kredentser)</li>
+<li>Add <code>rclone backend restore</code> command to restore objects from GLACIER (Nick Craig-Wood)</li>
+<li>Add <code>rclone cleanup</code> and <code>rclone backend cleanup</code> to clean unfinished multipart uploads (Nick Craig-Wood)</li>
+<li>Add <code>rclone backend list-multipart-uploads</code> to list unfinished multipart uploads (Nick Craig-Wood)</li>
+<li>Add <code>--s3-max-upload-parts</code> support (Kamil Trzciński)</li>
+<li>Add <code>--s3-no-check-bucket</code> for minimising rclone transactions and perms (Nick Craig-Wood)</li>
+<li>Add <code>--s3-profile</code> and <code>--s3-shared-credentials-file</code> options (Nick Craig-Wood)</li>
+<li>Use regional s3 us-east-1 endpoint (David)</li>
+<li>Add Scaleway provider (Vincent Feltz)</li>
+<li>Update IBM COS endpoints (Egor Margineanu)</li>
+<li>Reduce the default <code>--s3-copy-cutoff</code> to &lt; 5GB for Backblaze S3 compatibility (Nick Craig-Wood)</li>
+<li>Fix detection of bucket existing (Nick Craig-Wood)</li>
+</ul></li>
+<li>SFTP
+<ul>
+<li>Use the absolute path instead of the relative path for listing for improved compatibility (Nick Craig-Wood)</li>
+<li>Add <code>--sftp-subsystem</code> and <code>--sftp-server-command</code> options (aus)</li>
+</ul></li>
+<li>Swift
+<ul>
+<li>Fix dangling large objects breaking the listing (Nick Craig-Wood)</li>
+<li>Fix purge not deleting directory markers (Nick Craig-Wood)</li>
+<li>Fix update multipart object removing all of its own parts (Nick Craig-Wood)</li>
+<li>Fix missing hash from object returned from upload (Nick Craig-Wood)</li>
+</ul></li>
+<li>Tardigrade
+<ul>
+<li>Upgrade to uplink v1.2.0 (Kaloyan Raev)</li>
+</ul></li>
+<li>Union
+<ul>
+<li>Fix writing with the all policy (Nick Craig-Wood)</li>
+</ul></li>
+<li>WebDAV
+<ul>
+<li>Fix directory creation with 4shared (Nick Craig-Wood)</li>
+</ul></li>
+</ul>
+<h2 id="v1.52.3---2020-08-07">v1.52.3 - 2020-08-07</h2>
+<p><a href="https://github.com/rclone/rclone/compare/v1.52.2...v1.52.3">See commits</a></p>
+<ul>
+<li>Bug Fixes
+<ul>
+<li>docs
+<ul>
+<li>Disable smart typography (eg en-dash) in MANUAL.* and man page (Nick Craig-Wood)</li>
+<li>Update install.md to reflect minimum Go version (Evan Harris)</li>
+<li>Update install from source instructions (Nick Craig-Wood)</li>
+<li>make_manual: Support SOURCE_DATE_EPOCH (Morten Linderud)</li>
+</ul></li>
+<li>log: Fix --use-json-log going to stderr not --log-file on Windows (Nick Craig-Wood)</li>
+<li>serve dlna: Fix file list on Samsung Series 6+ TVs (Matteo Pietro Dazzi)</li>
+<li>sync: Fix deadlock with --track-renames-strategy modtime (Nick Craig-Wood)</li>
+</ul></li>
+<li>Cache
+<ul>
+<li>Fix moveto/copyto remote:file remote:file2 (Nick Craig-Wood)</li>
+</ul></li>
+<li>Drive
+<ul>
+<li>Stop using root_folder_id as a cache (Nick Craig-Wood)</li>
+<li>Make dangling shortcuts appear in listings (Nick Craig-Wood)</li>
+<li>Drop "Disabling ListR" messages down to debug (Nick Craig-Wood)</li>
+<li>Workaround and policy for Google Drive API (Dmitry Ustalov)</li>
+</ul></li>
+<li>FTP
+<ul>
+<li>Add note to docs about home vs root directory selection (Nick Craig-Wood)</li>
+</ul></li>
+<li>Onedrive
+<ul>
+<li>Fix reverting to Copy when Move would have worked (Nick Craig-Wood)</li>
+<li>Avoid comma rendered in URL in onedrive.md (Kevin)</li>
+</ul></li>
+<li>Pcloud
+<ul>
+<li>Fix oauth on European region "eapi.pcloud.com" (Nick Craig-Wood)</li>
+</ul></li>
+<li>S3
+<ul>
+<li>Fix bucket Region auto detection when Region unset in config (Nick Craig-Wood)</li>
+</ul></li>
+</ul>
+<h2 id="v1.52.2---2020-06-24">v1.52.2 - 2020-06-24</h2>
+<p><a href="https://github.com/rclone/rclone/compare/v1.52.1...v1.52.2">See commits</a></p>
+<ul>
+<li>Bug Fixes
+<ul>
+<li>build
+<ul>
+<li>Fix docker release build action (Nick Craig-Wood)</li>
+<li>Fix custom timezone in Docker image (NoLooseEnds)</li>
+</ul></li>
+<li>check: Fix misleading message which printed errors instead of differences (Nick Craig-Wood)</li>
+<li>errors: Add WSAECONNREFUSED and more to the list of retriable Windows errors (Nick Craig-Wood)</li>
+<li>rcd: Fix incorrect prometheus metrics (Gary Kim)</li>
+<li>serve restic: Fix flags so they use environment variables (Nick Craig-Wood)</li>
+<li>serve webdav: Fix flags so they use environment variables (Nick Craig-Wood)</li>
+<li>sync: Fix --track-renames-strategy modtime (Nick Craig-Wood)</li>
+</ul></li>
+<li>Drive
+<ul>
+<li>Fix not being able to delete a directory with a trashed shortcut (Nick Craig-Wood)</li>
+<li>Fix creating a directory inside a shortcut (Nick Craig-Wood)</li>
+<li>Fix --drive-impersonate with cached root_folder_id (Nick Craig-Wood)</li>
+</ul></li>
+<li>SFTP
+<ul>
+<li>Fix SSH key PEM loading (Zac Rubin)</li>
+</ul></li>
+<li>Swift
+<ul>
+<li>Speed up deletes by not retrying segment container deletes (Nick Craig-Wood)</li>
+</ul></li>
+<li>Tardigrade
+<ul>
+<li>Upgrade to uplink v1.1.1 (Caleb Case)</li>
+</ul></li>
+<li>WebDAV
+<ul>
+<li>Fix free/used display for rclone about/df for certain backends (Nick Craig-Wood)</li>
+</ul></li>
+</ul>
+<h2 id="v1.52.1---2020-06-10">v1.52.1 - 2020-06-10</h2>
+<p><a href="https://github.com/rclone/rclone/compare/v1.52.0...v1.52.1">See commits</a></p>
+<ul>
+<li>Bug Fixes
+<ul>
+<li>lib/file: Fix SetSparse on Windows 7 which fixes downloads of files &gt; 250MB (Nick Craig-Wood)</li>
+<li>build
+<ul>
+<li>Update go.mod to go1.14 to enable -mod=vendor build (Nick Craig-Wood)</li>
+<li>Remove quicktest from Dockerfile (Nick Craig-Wood)</li>
+<li>Build Docker images with GitHub actions (Matteo Pietro Dazzi)</li>
+<li>Update Docker build workflows (Nick Craig-Wood)</li>
+<li>Set user_allow_other in /etc/fuse.conf in the Docker image (Nick Craig-Wood)</li>
+<li>Fix xgo build after go1.14 go.mod update (Nick Craig-Wood)</li>
+</ul></li>
+<li>docs
+<ul>
+<li>Add link to source and modified time to footer of every page (Nick Craig-Wood)</li>
+<li>Remove manually set dates and use git dates instead (Nick Craig-Wood)</li>
+<li>Minor tense, punctuation, brevity and positivity changes for the home page (edwardxml)</li>
+<li>Remove leading slash in page reference in footer when present (Nick Craig-Wood)</li>
+<li>Note commands which need obscured input in the docs (Nick Craig-Wood)</li>
+<li>obscure: Write more help as we are referencing it elsewhere (Nick Craig-Wood)</li>
+</ul></li>
+</ul></li>
+<li>VFS
+<ul>
+<li>Fix OS vs Unix path confusion - fixes ChangeNotify on Windows (Nick Craig-Wood)</li>
+</ul></li>
+<li>Drive
+<ul>
+<li>Fix missing items when listing using --fast-list / ListR (Nick Craig-Wood)</li>
+</ul></li>
+<li>Putio
+<ul>
+<li>Fix panic on Object.Open (Cenk Alti)</li>
+</ul></li>
+<li>S3
+<ul>
+<li>Fix upload of single files into buckets without create permission (Nick Craig-Wood)</li>
+<li>Fix --header-upload (Nick Craig-Wood)</li>
+</ul></li>
+<li>Tardigrade
+<ul>
+<li>Fix listing bug by upgrading to v1.0.7</li>
+<li>Set UserAgent to rclone (Caleb Case)</li>
+</ul></li>
+</ul>
 <h2 id="v1.52.0---2020-05-27">v1.52.0 - 2020-05-27</h2>
 <p>Special thanks to Martin Michlmayr for proof reading and correcting all the docs and Edward Barker for helping re-write the front page.</p>
 <p><a href="https://github.com/rclone/rclone/compare/v1.51.0...v1.52.0">See commits</a></p>
@@ -17117,12 +17837,12 @@ $ tree /tmp/b
 <ul>
 <li>accounting
 <ul>
-<li>Restore “Max number of stats groups reached” log line (Michał Matczuk)</li>
+<li>Restore "Max number of stats groups reached" log line (Michał Matczuk)</li>
 <li>Correct exitcode on Transfer Limit Exceeded flag. (Anuar Serdaliyev)</li>
 <li>Reset bytes read during copy retry (Ankur Gupta)</li>
 <li>Fix race clearing stats (Nick Craig-Wood)</li>
 </ul></li>
-<li>copy: Only create empty directories when they don’t exist on the remote (Ishuah Kariuki)</li>
+<li>copy: Only create empty directories when they don't exist on the remote (Ishuah Kariuki)</li>
 <li>dedupe: Stop dedupe deleting files with identical IDs (Nick Craig-Wood)</li>
 <li>oauth
 <ul>
@@ -17143,14 +17863,14 @@ $ tree /tmp/b
 </ul></li>
 <li>serve dlna
 <ul>
-<li>Cds: don’t specify childCount at all when unknown (Dan Walters)</li>
+<li>Cds: don't specify childCount at all when unknown (Dan Walters)</li>
 <li>Cds: use modification time as date in dlna metadata (Dan Walters)</li>
 </ul></li>
 <li>serve restic: Fix tests after restic project removed vendoring (Nick Craig-Wood)</li>
 <li>sync
 <ul>
-<li>Fix incorrect “nothing to transfer” message using <code>--delete-before</code> (Nick Craig-Wood)</li>
-<li>Only create empty directories when they don’t exist on the remote (Ishuah Kariuki)</li>
+<li>Fix incorrect "nothing to transfer" message using <code>--delete-before</code> (Nick Craig-Wood)</li>
+<li>Only create empty directories when they don't exist on the remote (Ishuah Kariuki)</li>
 </ul></li>
 </ul></li>
 <li>Mount
@@ -17188,7 +17908,7 @@ $ tree /tmp/b
 <li>Speed up multi thread downloads by using sparse files on Windows (Nick Craig-Wood)</li>
 <li>Implement <code>--local-no-sparse</code> flag for disabling sparse files (Nick Craig-Wood)</li>
 <li>Implement <code>rclone backend noop</code> for testing purposes (Nick Craig-Wood)</li>
-<li>Fix “file not found” errors on post transfer Hash calculation (Nick Craig-Wood)</li>
+<li>Fix "file not found" errors on post transfer Hash calculation (Nick Craig-Wood)</li>
 </ul></li>
 <li>Cache
 <ul>
@@ -17242,7 +17962,7 @@ $ tree /tmp/b
 <li>Fix missing files when using <code>--fast-list</code> and <code>--drive-shared-with-me</code> (Nick Craig-Wood)</li>
 <li>Fix duplicate items when using <code>--drive-shared-with-me</code> (Nick Craig-Wood)</li>
 <li>Extend <code>--drive-stop-on-upload-limit</code> to respond to <code>teamDriveFileLimitExceeded</code>. (harry)</li>
-<li>Don’t delete files with multiple parents to avoid data loss (Nick Craig-Wood)</li>
+<li>Don't delete files with multiple parents to avoid data loss (Nick Craig-Wood)</li>
 <li>Server side copy docs use default description if empty (Nick Craig-Wood)</li>
 </ul></li>
 <li>Dropbox
@@ -17273,8 +17993,8 @@ $ tree /tmp/b
 <li>Make the start year configurable (Daven)</li>
 <li>Add support for <code>--header-upload</code> and <code>--header-download</code> (Tim Gallant)</li>
 <li>Create feature/favorites directory (Brandon Philips)</li>
-<li>Fix “concurrent map write” error (Nick Craig-Wood)</li>
-<li>Don’t put an image in error message (Nick Craig-Wood)</li>
+<li>Fix "concurrent map write" error (Nick Craig-Wood)</li>
+<li>Don't put an image in error message (Nick Craig-Wood)</li>
 </ul></li>
 <li>HTTP
 <ul>
@@ -17309,7 +18029,7 @@ $ tree /tmp/b
 <ul>
 <li>Added support for interchangeable root folder for pCloud backend (Sunil Patra)</li>
 <li>Add support for <code>--header-upload</code> and <code>--header-download</code> (Tim Gallant)</li>
-<li>Fix initial config “Auth state doesn’t match” message (Nick Craig-Wood)</li>
+<li>Fix initial config "Auth state doesn't match" message (Nick Craig-Wood)</li>
 </ul></li>
 <li>Premiumizeme
 <ul>
@@ -17342,12 +18062,12 @@ $ tree /tmp/b
 <li>Fix multipart abort context (Aleksandar Jankovic)</li>
 <li>Replace deprecated <code>session.New()</code> with <code>session.NewSession()</code> (Lars Lehtonen)</li>
 <li>Use the provided size parameter when allocating a new memory pool (Joachim Brandon LeBlanc)</li>
-<li>Use rclone’s low level retries instead of AWS SDK to fix listing retries (Nick Craig-Wood)</li>
+<li>Use rclone's low level retries instead of AWS SDK to fix listing retries (Nick Craig-Wood)</li>
 <li>Ignore directory markers at the root also (Nick Craig-Wood)</li>
 <li>Use single memory pool (Michał Matczuk)</li>
 <li>Do not resize buf on put to memBuf (Michał Matczuk)</li>
 <li>Improve docs for <code>--s3-disable-checksum</code> (Nick Craig-Wood)</li>
-<li>Don’t leak memory or tokens in edge cases for multipart upload (Nick Craig-Wood)</li>
+<li>Don't leak memory or tokens in edge cases for multipart upload (Nick Craig-Wood)</li>
 </ul></li>
 <li>Seafile
 <ul>
@@ -17408,7 +18128,7 @@ $ tree /tmp/b
 <li>Implement <code>--order-by</code> flag to order transfers (Nick Craig-Wood)</li>
 <li>accounting
 <ul>
-<li>Don’t show entries in both transferring and checking (Nick Craig-Wood)</li>
+<li>Don't show entries in both transferring and checking (Nick Craig-Wood)</li>
 <li>Add option to delete stats (Aleksandar Jankovic)</li>
 </ul></li>
 <li>build
@@ -17469,9 +18189,9 @@ $ tree /tmp/b
 <li>vendor
 <ul>
 <li>Update bazil.org/fuse to fix FreeBSD 12.1 (Nick Craig-Wood)</li>
-<li>Update github.com/t3rm1n4l/go-mega to fix mega “illegal base64 data at input byte 22” (Nick Craig-Wood)</li>
+<li>Update github.com/t3rm1n4l/go-mega to fix mega "illegal base64 data at input byte 22" (Nick Craig-Wood)</li>
 <li>Update termbox-go to fix ncdu command on FreeBSD (Kuang-che Wu)</li>
-<li>Update t3rm1n4l/go-mega - fixes mega: couldn’t login: crypto/aes: invalid key size 0 (Nick Craig-Wood)</li>
+<li>Update t3rm1n4l/go-mega - fixes mega: couldn't login: crypto/aes: invalid key size 0 (Nick Craig-Wood)</li>
 </ul></li>
 </ul></li>
 <li>Mount
@@ -17479,7 +18199,7 @@ $ tree /tmp/b
 <li>Enable async reads for a 20% speedup (Nick Craig-Wood)</li>
 <li>Replace use of WriteAt with Write for cache mode &gt;= writes and O_APPEND (Brett Dutro)</li>
 <li>Make sure we call unmount when exiting (Nick Craig-Wood)</li>
-<li>Don’t build on go1.10 as bazil/fuse no longer supports it (Nick Craig-Wood)</li>
+<li>Don't build on go1.10 as bazil/fuse no longer supports it (Nick Craig-Wood)</li>
 <li>When setting dates discard out of range dates (Nick Craig-Wood)</li>
 </ul></li>
 <li>VFS
@@ -17489,7 +18209,7 @@ $ tree /tmp/b
 <li>Make ReadAt for non cached files work better with non-sequential reads (Nick Craig-Wood)</li>
 <li>Fix edge cases when reading ModTime from file (Nick Craig-Wood)</li>
 <li>Make sure existing files opened for write show correct size (Nick Craig-Wood)</li>
-<li>Don’t cache the path in RW file objects to fix renaming (Nick Craig-Wood)</li>
+<li>Don't cache the path in RW file objects to fix renaming (Nick Craig-Wood)</li>
 <li>Fix rename of open files when using the VFS cache (Nick Craig-Wood)</li>
 <li>When renaming files in the cache, rename the cache item in memory too (Nick Craig-Wood)</li>
 <li>Fix open file renaming on drive when using <code>--vfs-cache-mode writes</code> (Nick Craig-Wood)</li>
@@ -17542,7 +18262,7 @@ $ tree /tmp/b
 <li>Onedrive
 <ul>
 <li>Add Sites.Read.All permission (Benjamin Richter)</li>
-<li>Add support “Retry-After” header (Motonori IWAMURO)</li>
+<li>Add support "Retry-After" header (Motonori IWAMURO)</li>
 </ul></li>
 <li>Opendrive
 <ul>
@@ -17566,7 +18286,7 @@ $ tree /tmp/b
 <ul>
 <li>Add <code>--sftp-skip-links</code> to skip symlinks and non regular files (Nick Craig-Wood)</li>
 <li>Retry Creation of Connection (Sebastian Brandt)</li>
-<li>Fix “failed to parse private key file: ssh: not an encrypted key” error (Nick Craig-Wood)</li>
+<li>Fix "failed to parse private key file: ssh: not an encrypted key" error (Nick Craig-Wood)</li>
 <li>Open files for update write only to fix AWS SFTP interop (Nick Craig-Wood)</li>
 </ul></li>
 <li>Swift
@@ -17578,7 +18298,7 @@ $ tree /tmp/b
 <li>WebDAV
 <ul>
 <li>Make nextcloud only upload SHA1 checksums (Nick Craig-Wood)</li>
-<li>Fix case of “Bearer” in Authorization: header to agree with RFC (Nick Craig-Wood)</li>
+<li>Fix case of "Bearer" in Authorization: header to agree with RFC (Nick Craig-Wood)</li>
 <li>Add Referer header to fix problems with WAFs (Nick Craig-Wood)</li>
 </ul></li>
 </ul>
@@ -17591,7 +18311,7 @@ $ tree /tmp/b
 <li>Drive
 <ul>
 <li>Fix listing of the root directory with drive.files scope (Nick Craig-Wood)</li>
-<li>Fix –drive-root-folder-id with team/shared drives (Nick Craig-Wood)</li>
+<li>Fix --drive-root-folder-id with team/shared drives (Nick Craig-Wood)</li>
 </ul></li>
 </ul>
 <h2 id="v1.50.1---2019-11-02">v1.50.1 - 2019-11-02</h2>
@@ -17600,7 +18320,7 @@ $ tree /tmp/b
 <ul>
 <li>hash: Fix accidentally changed hash names for <code>DropboxHash</code> and <code>CRC-32</code> (Nick Craig-Wood)</li>
 <li>fshttp: Fix error reporting on tpslimit token bucket errors (Nick Craig-Wood)</li>
-<li>fshttp: Don’t print token bucket errors on context cancelled (Nick Craig-Wood)</li>
+<li>fshttp: Don't print token bucket errors on context cancelled (Nick Craig-Wood)</li>
 </ul></li>
 <li>Local
 <ul>
@@ -17664,15 +18384,15 @@ $ tree /tmp/b
 <ul>
 <li>sync
 <ul>
-<li>Make <code>--update</code>/<code>-u</code> not transfer files that haven’t changed (Nick Craig-Wood)</li>
+<li>Make <code>--update</code>/<code>-u</code> not transfer files that haven't changed (Nick Craig-Wood)</li>
 <li>Free objects after they come out of the transfer pipe to save memory (Nick Craig-Wood)</li>
 <li>Fix <code>--files-from without --no-traverse</code> doing a recursive scan (Nick Craig-Wood)</li>
 </ul></li>
 <li>operations
 <ul>
 <li>Fix accounting for server side copies (Nick Craig-Wood)</li>
-<li>Display ‘All duplicates removed’ only if dedupe successful (Sezal Agrawal)</li>
-<li>Display ‘Deleted X extra copies’ only if dedupe successful (Sezal Agrawal)</li>
+<li>Display 'All duplicates removed' only if dedupe successful (Sezal Agrawal)</li>
+<li>Display 'Deleted X extra copies' only if dedupe successful (Sezal Agrawal)</li>
 </ul></li>
 <li>accounting
 <ul>
@@ -17685,15 +18405,15 @@ $ tree /tmp/b
 <li>cmd
 <ul>
 <li>Fix environment variables not setting command line flags (Nick Craig-Wood)</li>
-<li>Make autocomplete compatible with bash’s posix mode for macOS (Danil Semelenov)</li>
+<li>Make autocomplete compatible with bash's posix mode for macOS (Danil Semelenov)</li>
 <li>Make <code>--progress</code> work in git bash on Windows (Nick Craig-Wood)</li>
-<li>Fix ‘compopt: command not found’ on autocomplete on macOS (Danil Semelenov)</li>
+<li>Fix 'compopt: command not found' on autocomplete on macOS (Danil Semelenov)</li>
 </ul></li>
 <li>config
 <ul>
 <li>Fix setting of non top level flags from environment variables (Nick Craig-Wood)</li>
 <li>Check config names more carefully and report errors (Nick Craig-Wood)</li>
-<li>Remove error: can’t use <code>--size-only</code> and <code>--ignore-size</code> together. (Nick Craig-Wood)</li>
+<li>Remove error: can't use <code>--size-only</code> and <code>--ignore-size</code> together. (Nick Craig-Wood)</li>
 </ul></li>
 <li>filter: Prevent mixing options when <code>--files-from</code> is in use (Michele Caci)</li>
 <li>serve sftp: Fix crash on unsupported operations (eg Readlink) (Nick Craig-Wood)</li>
@@ -17703,8 +18423,8 @@ $ tree /tmp/b
 <li>Allow files of unknown size to be read properly (Nick Craig-Wood)</li>
 <li>Skip tests on &lt;= 2 CPUs to avoid lockup (Nick Craig-Wood)</li>
 <li>Fix panic on File.Open (Nick Craig-Wood)</li>
-<li>Fix “mount_fusefs: -o timeout=: option not supported” on FreeBSD (Nick Craig-Wood)</li>
-<li>Don’t pass huge filenames (&gt;4k) to FUSE as it can’t cope (Nick Craig-Wood)</li>
+<li>Fix "mount_fusefs: -o timeout=: option not supported" on FreeBSD (Nick Craig-Wood)</li>
+<li>Don't pass huge filenames (&gt;4k) to FUSE as it can't cope (Nick Craig-Wood)</li>
 </ul></li>
 <li>VFS
 <ul>
@@ -17809,7 +18529,7 @@ $ tree /tmp/b
 <li>accounting
 <ul>
 <li>Fix total duration calculation (Aleksandar Jankovic)</li>
-<li>Fix “file already closed” on transfer retries (Nick Craig-Wood)</li>
+<li>Fix "file already closed" on transfer retries (Nick Craig-Wood)</li>
 </ul></li>
 </ul></li>
 </ul>
@@ -17875,7 +18595,7 @@ $ tree /tmp/b
 <li>operations:
 <ul>
 <li>Run hashing operations in parallel (Nick Craig-Wood)</li>
-<li>Don’t calculate checksums when using <code>--ignore-checksum</code> (Nick Craig-Wood)</li>
+<li>Don't calculate checksums when using <code>--ignore-checksum</code> (Nick Craig-Wood)</li>
 <li>Check transfer hashes when using <code>--size-only</code> mode (Nick Craig-Wood)</li>
 <li>Disable multi thread copy for local to local copies (Nick Craig-Wood)</li>
 <li>Debug successful hashes as well as failures (Nick Craig-Wood)</li>
@@ -17887,7 +18607,7 @@ $ tree /tmp/b
 <li>Rclone-WebUI integration with rclone (Chaitanya Bankanhal)</li>
 <li>Added command line parameter to control the cross origin resource sharing (CORS) in the rcd. (Security Improvement) (Chaitanya Bankanhal)</li>
 <li>Add anchor tags to the docs so links are consistent (Nick Craig-Wood)</li>
-<li>Remove _async key from input parameters after parsing so later operations won’t get confused (buengese)</li>
+<li>Remove _async key from input parameters after parsing so later operations won't get confused (buengese)</li>
 <li>Add call to clear stats (Aleksandar Jankovic)</li>
 </ul></li>
 <li>rcd
@@ -17921,7 +18641,7 @@ $ tree /tmp/b
 </ul></li>
 <li>Bug Fixes
 <ul>
-<li>Make “bad record MAC” a retriable error (Nick Craig-Wood)</li>
+<li>Make "bad record MAC" a retriable error (Nick Craig-Wood)</li>
 <li>copyurl: Fix copying files that return HTTP errors (Nick Craig-Wood)</li>
 <li>march: Fix checking sub-directories when using <code>--no-traverse</code> (buengese)</li>
 <li>rc
@@ -17948,7 +18668,7 @@ $ tree /tmp/b
 <ul>
 <li>Add <code>--local-case-sensitive</code> and <code>--local-case-insensitive</code> (Nick Craig-Wood)</li>
 <li>Avoid polluting page cache when uploading local files to remote backends (Michał Matczuk)</li>
-<li>Don’t calculate any hashes by default (Nick Craig-Wood)</li>
+<li>Don't calculate any hashes by default (Nick Craig-Wood)</li>
 <li>Fadvise run syscall on a dedicated go routine (Michał Matczuk)</li>
 </ul></li>
 <li>Azure Blob
@@ -18077,7 +18797,7 @@ $ tree /tmp/b
 <li>Bug Fixes
 <ul>
 <li>Make move and copy individual files obey <code>--backup-dir</code> (Nick Craig-Wood)</li>
-<li>If <code>--ignore-checksum</code> is in effect, don’t calculate checksum (Nick Craig-Wood)</li>
+<li>If <code>--ignore-checksum</code> is in effect, don't calculate checksum (Nick Craig-Wood)</li>
 <li>moveto: Fix case-insensitive same remote move (Gary Kim)</li>
 <li>rc: Fix serving bucket based objects with <code>--rc-serve</code> (Nick Craig-Wood)</li>
 <li>serve webdav: Fix serveDir not being updated with changes from webdav (Gary Kim)</li>
@@ -18140,7 +18860,7 @@ $ tree /tmp/b
 <li>S3
 <ul>
 <li>Support S3 Accelerated endpoints with <code>--s3-use-accelerate-endpoint</code> (Nick Craig-Wood)</li>
-<li>Add config info for Wasabi’s EU Central endpoint (Robert Marko)</li>
+<li>Add config info for Wasabi's EU Central endpoint (Robert Marko)</li>
 <li>Make SetModTime work for GLACIER while syncing (Philip Harvey)</li>
 </ul></li>
 <li>SFTP
@@ -18167,7 +18887,7 @@ $ tree /tmp/b
 <li>this means rclone will restart transfers if the source has an error</li>
 <li>this is most useful for downloads or cloud to cloud copies</li>
 </ul></li>
-<li>Use <code>--fast-list</code> for listing operations where it won’t use more memory (Nick Craig-Wood)
+<li>Use <code>--fast-list</code> for listing operations where it won't use more memory (Nick Craig-Wood)
 <ul>
 <li>this should speed up the following operations on remotes which support <code>ListR</code></li>
 <li><code>dedupe</code>, <code>serve restic</code> <code>lsf</code>, <code>ls</code>, <code>lsl</code>, <code>lsjson</code>, <code>lsd</code>, <code>md5sum</code>, <code>sha1sum</code>, <code>hashsum</code>, <code>size</code>, <code>delete</code>, <code>cat</code>, <code>settier</code></li>
@@ -18187,7 +18907,7 @@ $ tree /tmp/b
 <li>Update to use go1.12.x for the build (Nick Craig-Wood)</li>
 </ul></li>
 <li>serve dlna: Add connection manager service description to improve compatibility (Dan Walters)</li>
-<li>lsf: Add ‘e’ format to show encrypted names and ‘o’ for original IDs (Nick Craig-Wood)</li>
+<li>lsf: Add 'e' format to show encrypted names and 'o' for original IDs (Nick Craig-Wood)</li>
 <li>lsjson: Added <code>--files-only</code> and <code>--dirs-only</code> flags (calistri)</li>
 <li>rc: Implement operations/publiclink the equivalent of <code>rclone link</code> (Nick Craig-Wood)</li>
 </ul></li>
@@ -18214,7 +18934,7 @@ $ tree /tmp/b
 </ul></li>
 <li>Azure Blob
 <ul>
-<li>Enable MD5 checksums when uploading files bigger than the “Cutoff” (Dr.Rx)</li>
+<li>Enable MD5 checksums when uploading files bigger than the "Cutoff" (Dr.Rx)</li>
 <li>Fix SAS URL support (Nick Craig-Wood)</li>
 </ul></li>
 <li>B2
@@ -18264,7 +18984,7 @@ $ tree /tmp/b
 </ul></li>
 <li>S3
 <ul>
-<li>Add support for “Glacier Deep Archive” storage class (Manu)</li>
+<li>Add support for "Glacier Deep Archive" storage class (Manu)</li>
 <li>Update Dreamhost endpoint (Nick Craig-Wood)</li>
 <li>Note incompatibility with CEPH Jewel (Nick Craig-Wood)</li>
 </ul></li>
@@ -18327,7 +19047,7 @@ $ tree /tmp/b
 </ul></li>
 <li>Mount
 <ul>
-<li>Check that mountpoint and local directory to mount don’t overlap (Nick Craig-Wood)</li>
+<li>Check that mountpoint and local directory to mount don't overlap (Nick Craig-Wood)</li>
 <li>Fix mount size under 32 bit Windows (Nick Craig-Wood)</li>
 </ul></li>
 <li>VFS
@@ -18340,7 +19060,7 @@ $ tree /tmp/b
 <li>Add <code>--dir-perms</code> and <code>--file-perms</code> flags to set default permissions (Nick Craig-Wood)</li>
 <li>Fix deadlock on concurrent operations on a directory (Nick Craig-Wood)</li>
 <li>Fix deadlock between RWFileHandle.close and File.Remove (Nick Craig-Wood)</li>
-<li>Fix renaming/deleting open files with cache mode “writes” under Windows (Nick Craig-Wood)</li>
+<li>Fix renaming/deleting open files with cache mode "writes" under Windows (Nick Craig-Wood)</li>
 <li>Fix panic on rename with <code>--dry-run</code> set (Nick Craig-Wood)</li>
 <li>Fix vfs/refresh with recurse=true needing the <code>--fast-list</code> flag</li>
 </ul></li>
@@ -18406,7 +19126,7 @@ $ tree /tmp/b
 </ul></li>
 <li>HTTP
 <ul>
-<li>Add an example with username and password which is supported but wasn’t documented (Nick Craig-Wood)</li>
+<li>Add an example with username and password which is supported but wasn't documented (Nick Craig-Wood)</li>
 <li>Fix backend with <code>--files-from</code> and non-existent files (Nick Craig-Wood)</li>
 </ul></li>
 <li>Hubic
@@ -18416,7 +19136,7 @@ $ tree /tmp/b
 <li>Jottacloud
 <ul>
 <li>Resume and deduplication support (Oliver Heyme)</li>
-<li>Use token auth for all API requests Don’t store password anymore (Sebastian Bünger)</li>
+<li>Use token auth for all API requests Don't store password anymore (Sebastian Bünger)</li>
 <li>Add support for 2-factor authentication (Sebastian Bünger)</li>
 </ul></li>
 <li>Mega
@@ -18427,7 +19147,7 @@ $ tree /tmp/b
 </ul></li>
 <li>Onedrive
 <ul>
-<li>Fix broken support for “shared with me” folders (Alex Chen)</li>
+<li>Fix broken support for "shared with me" folders (Alex Chen)</li>
 <li>Fix root ID not normalised (Cnly)</li>
 <li>Return err instead of panic on unknown-sized uploads (Cnly)</li>
 </ul></li>
@@ -18508,13 +19228,13 @@ $ tree /tmp/b
 </ul></li>
 <li>sync/copy/move
 <ul>
-<li>Make <code>--files-from</code> only read the objects specified and don’t scan directories (Nick Craig-Wood)
+<li>Make <code>--files-from</code> only read the objects specified and don't scan directories (Nick Craig-Wood)
 <ul>
 <li>This is a huge speed improvement for destinations with lots of files</li>
 </ul></li>
 </ul></li>
 <li>filter: Add <code>--ignore-case</code> flag (Nick Craig-Wood)</li>
-<li>ncdu: Add remove function (‘d’ key) (Henning Surmeier)</li>
+<li>ncdu: Add remove function ('d' key) (Henning Surmeier)</li>
 <li>rc command
 <ul>
 <li>Add <code>--json</code> flag for structured JSON input (Nick Craig-Wood)</li>
@@ -18532,7 +19252,7 @@ $ tree /tmp/b
 <li>cmd: Make <code>--progress</code> update the stats correctly at the end (Nick Craig-Wood)</li>
 <li>config: Create config directory on save if it is missing (Nick Craig-Wood)</li>
 <li>dedupe: Check for existing filename before renaming a dupe file (ssaqua)</li>
-<li>move: Don’t create directories with <code>--dry-run</code> (Nick Craig-Wood)</li>
+<li>move: Don't create directories with <code>--dry-run</code> (Nick Craig-Wood)</li>
 <li>operations: Fix Purge and Rmdirs when dir is not the root (Nick Craig-Wood)</li>
 <li>serve http/webdav/restic: Ensure rclone exits if the port is in use (Nick Craig-Wood)</li>
 </ul></li>
@@ -18543,7 +19263,7 @@ $ tree /tmp/b
 <li>Azure Blob
 <ul>
 <li>Avoid context deadline exceeded error by setting a large TryTimeout value (brused27)</li>
-<li>Fix erroneous Rmdir error “directory not empty” (Nick Craig-Wood)</li>
+<li>Fix erroneous Rmdir error "directory not empty" (Nick Craig-Wood)</li>
 <li>Wait for up to 60s to create a just deleted container (Nick Craig-Wood)</li>
 </ul></li>
 <li>Dropbox
@@ -18562,8 +19282,8 @@ $ tree /tmp/b
 <li>S3
 <ul>
 <li>Set ACL for server side copies to that provided by the user (Nick Craig-Wood)</li>
-<li>Fix role_arn, credential_source, … (Erik Swanson)</li>
-<li>Add config info for Wasabi’s US-West endpoint (Henry Ptasinski)</li>
+<li>Fix role_arn, credential_source, ... (Erik Swanson)</li>
+<li>Add config info for Wasabi's US-West endpoint (Henry Ptasinski)</li>
 </ul></li>
 <li>SFTP
 <ul>
@@ -18614,8 +19334,8 @@ $ tree /tmp/b
 <li>Bug Fixes
 <ul>
 <li>Fix -P not ending with a new line (Nick Craig-Wood)</li>
-<li>config: don’t create default config dir when user supplies <code>--config</code> (albertony)</li>
-<li>Don’t print non-ASCII characters with <code>--progress</code> on windows (Nick Craig-Wood)</li>
+<li>config: don't create default config dir when user supplies <code>--config</code> (albertony)</li>
+<li>Don't print non-ASCII characters with <code>--progress</code> on windows (Nick Craig-Wood)</li>
 <li>Correct logs for excluded items (ssaqua)</li>
 </ul></li>
 <li>Mount
@@ -18912,8 +19632,8 @@ $ tree /tmp/b
 <li>WebDAV
 <ul>
 <li>Ensure we call MKCOL with a URL with a trailing / for QNAP interop (Nick Craig-Wood)</li>
-<li>If root ends with / then don’t check if it is a file (Nick Craig-Wood)</li>
-<li>Don’t accept redirects when reading metadata (Nick Craig-Wood)</li>
+<li>If root ends with / then don't check if it is a file (Nick Craig-Wood)</li>
+<li>Don't accept redirects when reading metadata (Nick Craig-Wood)</li>
 <li>Add bearer token (Macaroon) support for dCache (Nick Craig-Wood)</li>
 <li>Document dCache and Macaroons (Onno Zweers)</li>
 <li>Sharepoint recursion with different depth (Henning)</li>
@@ -18936,7 +19656,7 @@ $ tree /tmp/b
 </ul></li>
 <li>New Features
 <ul>
-<li>copy, move: Copy single files directly, don’t use <code>--files-from</code> work-around
+<li>copy, move: Copy single files directly, don't use <code>--files-from</code> work-around
 <ul>
 <li>this makes them much more efficient</li>
 </ul></li>
@@ -18957,8 +19677,8 @@ $ tree /tmp/b
 <ul>
 <li>Add <code>--absolute</code> flag to add a leading / onto path names</li>
 <li>Add <code>--csv</code> flag for compliant CSV output</li>
-<li>Add ‘m’ format specifier to show the MimeType</li>
-<li>Implement ‘i’ format for showing object ID</li>
+<li>Add 'm' format specifier to show the MimeType</li>
+<li>Implement 'i' format for showing object ID</li>
 </ul></li>
 <li>lsjson
 <ul>
@@ -18975,7 +19695,7 @@ $ tree /tmp/b
 </ul></li>
 <li>Mount
 <ul>
-<li>Only print “File.rename error” if there actually is an error (Stefan Breunig)</li>
+<li>Only print "File.rename error" if there actually is an error (Stefan Breunig)</li>
 <li>Delay rename if file has open writers instead of failing outright (Stefan Breunig)</li>
 <li>Ensure atexit gets run on interrupt</li>
 <li>macOS enhancements
@@ -19025,7 +19745,7 @@ $ tree /tmp/b
 <ul>
 <li>Add <code>--drive-acknowledge-abuse</code> to download flagged files</li>
 <li>Add <code>--drive-alternate-export</code> to fix large doc export</li>
-<li>Don’t attempt to choose Team Drives when using rclone config create</li>
+<li>Don't attempt to choose Team Drives when using rclone config create</li>
 <li>Fix change list polling with team drives</li>
 <li>Fix ChangeNotify for folders (Fabian Möller)</li>
 <li>Fix about (and df on a mount) for team drives</li>
@@ -19067,15 +19787,15 @@ $ tree /tmp/b
 <li>New Features
 <ul>
 <li>lsd: Add -R flag and fix and update docs for all ls commands</li>
-<li>ncdu: added a “refresh” key - CTRL-L (Keith Goldfarb)</li>
+<li>ncdu: added a "refresh" key - CTRL-L (Keith Goldfarb)</li>
 <li>serve restic: Add append-only mode (Steve Kriss)</li>
 <li>serve restic: Disallow overwriting files in append-only mode (Alexander Neumann)</li>
 <li>serve restic: Print actual listener address (Matt Holt)</li>
-<li>size: Add –json flag (Matthew Holt)</li>
-<li>sync: implement –ignore-errors (Mateusz Pabian)</li>
+<li>size: Add --json flag (Matthew Holt)</li>
+<li>sync: implement --ignore-errors (Mateusz Pabian)</li>
 <li>dedupe: Add dedupe largest functionality (Richard Yang)</li>
 <li>fs: Extend SizeSuffix to include TB and PB for rclone about</li>
-<li>fs: add –dump goroutines and –dump openfiles for debugging</li>
+<li>fs: add --dump goroutines and --dump openfiles for debugging</li>
 <li>rc: implement core/memstats to print internal memory usage info</li>
 <li>rc: new call rc/pid (Michael P. Dubner)</li>
 </ul></li>
@@ -19089,11 +19809,11 @@ $ tree /tmp/b
 </ul></li>
 <li>Bug Fixes
 <ul>
-<li>filter: fix –min-age and –max-age together check</li>
+<li>filter: fix --min-age and --max-age together check</li>
 <li>fs: limit MaxIdleConns and MaxIdleConnsPerHost in transport</li>
 <li>lsd,lsf: make sure all times we output are in local time</li>
 <li>rc: fix setting bwlimit to unlimited</li>
-<li>rc: take note of the –rc-addr flag too as per the docs</li>
+<li>rc: take note of the --rc-addr flag too as per the docs</li>
 </ul></li>
 <li>Mount
 <ul>
@@ -19109,11 +19829,11 @@ $ tree /tmp/b
 <li>VFS
 <ul>
 <li>Filter files <code>.</code> and <code>..</code> from directory listing</li>
-<li>Only make the VFS cache if –vfs-cache-mode &gt; Off</li>
+<li>Only make the VFS cache if --vfs-cache-mode &gt; Off</li>
 </ul></li>
 <li>Local
 <ul>
-<li>Add –local-no-check-updated to disable updated file checks</li>
+<li>Add --local-no-check-updated to disable updated file checks</li>
 <li>Retry remove on Windows sharing violation error</li>
 </ul></li>
 <li>Cache
@@ -19155,7 +19875,7 @@ $ tree /tmp/b
 </ul></li>
 <li>HTTP
 <ul>
-<li>Fix sync for servers which don’t return Content-Length in HEAD</li>
+<li>Fix sync for servers which don't return Content-Length in HEAD</li>
 </ul></li>
 <li>Onedrive
 <ul>
@@ -19169,8 +19889,8 @@ $ tree /tmp/b
 <li>Hierarchical configuration support (Giri Badanahatti)</li>
 <li>Add in config for all the supported S3 providers</li>
 <li>Add One Zone Infrequent Access storage class (Craig Rachel)</li>
-<li>Add –use-server-modtime support (Peter Baumgartner)</li>
-<li>Add –s3-chunk-size option to control multipart uploads</li>
+<li>Add --use-server-modtime support (Peter Baumgartner)</li>
+<li>Add --s3-chunk-size option to control multipart uploads</li>
 <li>Ignore zero length directory markers</li>
 </ul></li>
 <li>SFTP
@@ -19181,7 +19901,7 @@ $ tree /tmp/b
 </ul></li>
 <li>Swift
 <ul>
-<li>Add –use-server-modtime support (Peter Baumgartner)</li>
+<li>Add --use-server-modtime support (Peter Baumgartner)</li>
 </ul></li>
 <li>Webdav
 <ul>
@@ -19209,7 +19929,7 @@ $ tree /tmp/b
 </ul></li>
 <li><code>rc</code>: enable the remote control of a running rclone
 <ul>
-<li>The running rclone must be started with –rc and related flags.</li>
+<li>The running rclone must be started with --rc and related flags.</li>
 <li>Currently there is support for bwlimit, and flushing for mount and cache.</li>
 </ul></li>
 </ul></li>
@@ -19253,13 +19973,13 @@ $ tree /tmp/b
 <ul>
 <li>config: fixes errors on non existing config by loading config file only on first access</li>
 <li>config: retry saving the config after failure (Mateusz)</li>
-<li>sync: when using <code>--backup-dir</code> don’t delete files if we can’t set their modtime
+<li>sync: when using <code>--backup-dir</code> don't delete files if we can't set their modtime
 <ul>
 <li>this fixes odd behaviour with Dropbox and <code>--backup-dir</code></li>
 </ul></li>
 <li>fshttp: fix idle timeouts for HTTP connections</li>
 <li><code>serve http</code>: fix serving files with : in - fixes</li>
-<li>Fix <code>--exclude-if-present</code> to ignore directories which it doesn’t have permission for (Iakov Davydov)</li>
+<li>Fix <code>--exclude-if-present</code> to ignore directories which it doesn't have permission for (Iakov Davydov)</li>
 <li>Make accounting work properly with crypt and b2</li>
 <li>remove <code>--no-traverse</code> flag because it is obsolete</li>
 </ul></li>
@@ -19292,12 +20012,12 @@ $ tree /tmp/b
 <li>Fix applying modtime for an open Write Handle</li>
 <li>Fix creation of files when truncating</li>
 <li>Write 0 bytes when flushing unwritten handles to avoid race conditions in FUSE</li>
-<li>Downgrade “poll-interval is not supported” message to Info</li>
+<li>Downgrade "poll-interval is not supported" message to Info</li>
 <li>Make OpenFile and friends return EINVAL if O_RDONLY and O_TRUNC</li>
 </ul></li>
 <li>Local
 <ul>
-<li>Downgrade “invalid cross-device link: trying copy” to debug</li>
+<li>Downgrade "invalid cross-device link: trying copy" to debug</li>
 <li>Make DirMove return fs.ErrorCantDirMove to allow fallback to Copy for cross device</li>
 <li>Fix race conditions updating the hashes</li>
 </ul></li>
@@ -19320,7 +20040,7 @@ $ tree /tmp/b
 </ul></li>
 <li>Azureblob
 <ul>
-<li>Don’t check for bucket/container presence if listing was OK
+<li>Don't check for bucket/container presence if listing was OK
 <ul>
 <li>this makes rclone do one less request per invocation</li>
 </ul></li>
@@ -19328,7 +20048,7 @@ $ tree /tmp/b
 </ul></li>
 <li>Backblaze B2
 <ul>
-<li>Don’t check for bucket/container presence if listing was OK
+<li>Don't check for bucket/container presence if listing was OK
 <ul>
 <li>this makes rclone do one less request per invocation</li>
 </ul></li>
@@ -19343,7 +20063,7 @@ $ tree /tmp/b
 </ul></li>
 <li>Google Cloud Storage
 <ul>
-<li>Don’t check for bucket/container presence if listing was OK
+<li>Don't check for bucket/container presence if listing was OK
 <ul>
 <li>this makes rclone do one less request per invocation</li>
 </ul></li>
@@ -19386,7 +20106,7 @@ $ tree /tmp/b
 </ul></li>
 <li>Qingstor
 <ul>
-<li>Don’t check for bucket/container presence if listing was OK
+<li>Don't check for bucket/container presence if listing was OK
 <ul>
 <li>this makes rclone do one less request per invocation</li>
 </ul></li>
@@ -19396,7 +20116,7 @@ $ tree /tmp/b
 <li>Support hashes for multipart files (Chris Redekop)</li>
 <li>Initial support for IBM COS (S3) (Giri Badanahatti)</li>
 <li>Update docs to discourage use of v2 auth with CEPH and others</li>
-<li>Don’t check for bucket/container presence if listing was OK
+<li>Don't check for bucket/container presence if listing was OK
 <ul>
 <li>this makes rclone do one less request per invocation</li>
 </ul></li>
@@ -19419,7 +20139,7 @@ $ tree /tmp/b
 <li>in v1.39 a bug was introduced which ignored new tokens - this fixes it</li>
 </ul></li>
 <li>Fix extra HEAD transaction when uploading a new file</li>
-<li>Don’t check for bucket/container presence if listing was OK
+<li>Don't check for bucket/container presence if listing was OK
 <ul>
 <li>this makes rclone do one less request per invocation</li>
 </ul></li>
@@ -19460,11 +20180,11 @@ $ tree /tmp/b
 <li>New Features
 <ul>
 <li>curl install for rclone (Filip Bartodziej)</li>
-<li>–stats now shows percentage, size, rate and ETA in condensed form (Ishuah Kariuki)</li>
-<li>–exclude-if-present to exclude a directory if a file is present (Iakov Davydov)</li>
-<li>rmdirs: add –leave-root flag (lewapm)</li>
-<li>move: add –delete-empty-src-dirs flag to remove dirs after move (Ishuah Kariuki)</li>
-<li>Add –dump flag, introduce –dump requests, responses and remove –dump-auth, –dump-filters
+<li>--stats now shows percentage, size, rate and ETA in condensed form (Ishuah Kariuki)</li>
+<li>--exclude-if-present to exclude a directory if a file is present (Iakov Davydov)</li>
+<li>rmdirs: add --leave-root flag (lewapm)</li>
+<li>move: add --delete-empty-src-dirs flag to remove dirs after move (Ishuah Kariuki)</li>
+<li>Add --dump flag, introduce --dump requests, responses and remove --dump-auth, --dump-filters
 <ul>
 <li>Obscure X-Auth-Token: from headers when dumping too</li>
 </ul></li>
@@ -19475,7 +20195,7 @@ $ tree /tmp/b
 <ul>
 <li>Retry lots more different types of errors to make multipart transfers more reliable</li>
 <li>Save the config before asking for a token, fixes disappearing oauth config</li>
-<li>Warn the user if –include and –exclude are used together (Ernest Borowski)</li>
+<li>Warn the user if --include and --exclude are used together (Ernest Borowski)</li>
 <li>Fix duplicate files (eg on Google drive) causing spurious copies</li>
 <li>Allow trailing and leading whitespace for passwords (Jason Rose)</li>
 <li>ncdu: fix crashes on empty directories</li>
@@ -19484,9 +20204,9 @@ $ tree /tmp/b
 </ul></li>
 <li>Mount
 <ul>
-<li>–vfs-cache mode to make writes into mounts more reliable.
+<li>--vfs-cache mode to make writes into mounts more reliable.
 <ul>
-<li>this requires caching files on the disk (see –cache-dir)</li>
+<li>this requires caching files on the disk (see --cache-dir)</li>
 <li>As this is a new feature, use with care</li>
 </ul></li>
 <li>Use sdnotify to signal systemd the mount is ready (Fabian Möller)</li>
@@ -19524,7 +20244,7 @@ $ tree /tmp/b
 <li>Backblaze B2
 <ul>
 <li>Fix multipart upload retries</li>
-<li>Fix –hard-delete to make it work 100% of the time</li>
+<li>Fix --hard-delete to make it work 100% of the time</li>
 </ul></li>
 <li>Swift
 <ul>
@@ -19541,7 +20261,7 @@ $ tree /tmp/b
 </ul></li>
 <li>Amazon cloud drive
 <ul>
-<li>Fix download of large files failing with “Only one auth mechanism allowed”</li>
+<li>Fix download of large files failing with "Only one auth mechanism allowed"</li>
 </ul></li>
 <li>crypt
 <ul>
@@ -19576,7 +20296,7 @@ $ tree /tmp/b
 <li><code>dedupe</code> - implement merging of duplicate directories</li>
 <li><code>check</code> and <code>cryptcheck</code> made more consistent and use less memory</li>
 <li><code>cleanup</code> for remaining remotes (thanks ishuah)</li>
-<li><code>--immutable</code> for ensuring that files don’t change (thanks Jacob McNamee)</li>
+<li><code>--immutable</code> for ensuring that files don't change (thanks Jacob McNamee)</li>
 <li><code>--user-agent</code> option (thanks Alex McGrath Kraak)</li>
 <li><code>--disable</code> flag to disable optional features</li>
 <li><code>--bind</code> flag for choosing the local addr on outgoing connections</li>
@@ -19606,7 +20326,7 @@ $ tree /tmp/b
 </ul></li>
 <li>Dropbox
 <ul>
-<li>Fix “entry doesn’t belong in directory” error</li>
+<li>Fix "entry doesn't belong in directory" error</li>
 <li>Stop using deprecated API methods</li>
 </ul></li>
 <li>Swift
@@ -19670,20 +20390,20 @@ $ tree /tmp/b
 </ul></li>
 <li>New Features
 <ul>
-<li>Implement –fast-list flag
+<li>Implement --fast-list flag
 <ul>
 <li>This allows remotes to list recursively if they can</li>
 <li>This uses less transactions (important if you pay for them)</li>
 <li>This may or may not be quicker</li>
 <li>This will use more memory as it has to hold the listing in memory</li>
-<li>–old-sync-method deprecated - the remaining uses are covered by –fast-list</li>
+<li>--old-sync-method deprecated - the remaining uses are covered by --fast-list</li>
 <li>This involved a major re-write of all the listing code</li>
 </ul></li>
-<li>Add –tpslimit and –tpslimit-burst to limit transactions per second
+<li>Add --tpslimit and --tpslimit-burst to limit transactions per second
 <ul>
 <li>this is useful in conjunction with <code>rclone mount</code> to limit external apps</li>
 </ul></li>
-<li>Add –stats-log-level so can see –stats without -v</li>
+<li>Add --stats-log-level so can see --stats without -v</li>
 <li>Print password prompts to stderr - Hraban Luyat</li>
 <li>Warn about duplicate files when syncing</li>
 <li>Oauth improvements
@@ -19691,24 +20411,24 @@ $ tree /tmp/b
 <li>allow auth_url and token_url to be set in the config file</li>
 <li>Print redirection URI if using own credentials.</li>
 </ul></li>
-<li>Don’t Mkdir at the start of sync to save transactions</li>
+<li>Don't Mkdir at the start of sync to save transactions</li>
 </ul></li>
 <li>Compile
 <ul>
 <li>Update build to go1.8.3</li>
 <li>Require go1.6 for building rclone</li>
-<li>Compile 386 builds with “GO386=387” for maximum compatibility</li>
+<li>Compile 386 builds with "GO386=387" for maximum compatibility</li>
 </ul></li>
 <li>Bug Fixes
 <ul>
 <li>Fix menu selection when no remotes</li>
 <li>Config saving reworked to not kill the file if disk gets full</li>
-<li>Don’t delete remote if name does not change while renaming</li>
+<li>Don't delete remote if name does not change while renaming</li>
 <li>moveto, copyto: report transfers and checks as per move and copy</li>
 </ul></li>
 <li>Local
 <ul>
-<li>Add –local-no-unicode-normalization flag - Bob Potter</li>
+<li>Add --local-no-unicode-normalization flag - Bob Potter</li>
 </ul></li>
 <li>Mount
 <ul>
@@ -19716,7 +20436,7 @@ $ tree /tmp/b
 <li>Compare checksums on upload/download via FUSE</li>
 <li>Unmount when program ends with SIGINT (Ctrl+C) or SIGTERM - Jérôme Vizcaino</li>
 <li>On read only open of file, make open pending until first read</li>
-<li>Make –read-only reject modify operations</li>
+<li>Make --read-only reject modify operations</li>
 <li>Implement ModTime via FUSE for remotes that support it</li>
 <li>Allow modTime to be changed even before all writers are closed</li>
 <li>Fix panic on renames</li>
@@ -19725,7 +20445,7 @@ $ tree /tmp/b
 <li>Crypt
 <ul>
 <li>Report the name:root as specified by the user</li>
-<li>Add an “obfuscate” option for filename encryption - Stephen Harris</li>
+<li>Add an "obfuscate" option for filename encryption - Stephen Harris</li>
 </ul></li>
 <li>Amazon Drive
 <ul>
@@ -19740,9 +20460,9 @@ $ tree /tmp/b
 <ul>
 <li>Add team drive support</li>
 <li>Reduce bandwidth by adding fields for partial responses - Martin Kristensen</li>
-<li>Implement –drive-shared-with-me flag to view shared with me files - Danny Tsai</li>
-<li>Add –drive-trashed-only to read only the files in the trash</li>
-<li>Remove obsolete –drive-full-list</li>
+<li>Implement --drive-shared-with-me flag to view shared with me files - Danny Tsai</li>
+<li>Add --drive-trashed-only to read only the files in the trash</li>
+<li>Remove obsolete --drive-full-list</li>
 <li>Add missing seek to start on retries of chunked uploads</li>
 <li>Fix stats accounting for upload</li>
 <li>Convert / in names to a unicode equivalent (／)</li>
@@ -19816,20 +20536,20 @@ $ tree /tmp/b
 <ul>
 <li>SFTP remote (Jack Schmidt)</li>
 <li>Re-implement sync routine to work a directory at a time reducing memory usage</li>
-<li>Logging revamped to be more inline with rsync - now much quieter * -v only shows transfers * -vv is for full debug * –syslog to log to syslog on capable platforms</li>
-<li>Implement –backup-dir and –suffix</li>
-<li>Implement –track-renames (initial implementation by Bjørn Erik Pedersen)</li>
+<li>Logging revamped to be more inline with rsync - now much quieter * -v only shows transfers * -vv is for full debug * --syslog to log to syslog on capable platforms</li>
+<li>Implement --backup-dir and --suffix</li>
+<li>Implement --track-renames (initial implementation by Bjørn Erik Pedersen)</li>
 <li>Add time-based bandwidth limits (Lukas Loesche)</li>
 <li>rclone cryptcheck: checks integrity of crypt remotes</li>
 <li>Allow all config file variables and options to be set from environment variables</li>
-<li>Add –buffer-size parameter to control buffer size for copy</li>
-<li>Make –delete-after the default</li>
-<li>Add –ignore-checksum flag (fixed by Hisham Zarka)</li>
-<li>rclone check: Add –download flag to check all the data, not just hashes</li>
-<li>rclone cat: add –head, –tail, –offset, –count and –discard</li>
+<li>Add --buffer-size parameter to control buffer size for copy</li>
+<li>Make --delete-after the default</li>
+<li>Add --ignore-checksum flag (fixed by Hisham Zarka)</li>
+<li>rclone check: Add --download flag to check all the data, not just hashes</li>
+<li>rclone cat: add --head, --tail, --offset, --count and --discard</li>
 <li>rclone config: when choosing from a list, allow the value to be entered too</li>
 <li>rclone config: allow rename and copy of remotes</li>
-<li>rclone obscure: for generating encrypted passwords for rclone’s config (T.C. Ferguson)</li>
+<li>rclone obscure: for generating encrypted passwords for rclone's config (T.C. Ferguson)</li>
 <li>Comply with XDG Base Directory specification (Dario Giovannetti)
 <ul>
 <li>this moves the default location of the config file in a backwards compatible way</li>
@@ -19843,32 +20563,32 @@ $ tree /tmp/b
 </ul></li>
 <li>Bug Fixes
 <ul>
-<li>Fix copyto copying things to the wrong place if the destination dir didn’t exist</li>
+<li>Fix copyto copying things to the wrong place if the destination dir didn't exist</li>
 <li>Fix parsing of remotes in moveto and copyto</li>
-<li>Fix –delete-before deleting files on copy</li>
-<li>Fix –files-from with an empty file copying everything</li>
-<li>Fix sync: don’t update mod times if –dry-run set</li>
+<li>Fix --delete-before deleting files on copy</li>
+<li>Fix --files-from with an empty file copying everything</li>
+<li>Fix sync: don't update mod times if --dry-run set</li>
 <li>Fix MimeType propagation</li>
 <li>Fix filters to add ** rules to directory rules</li>
 </ul></li>
 <li>Local
 <ul>
-<li>Implement -L, –copy-links flag to allow rclone to follow symlinks</li>
+<li>Implement -L, --copy-links flag to allow rclone to follow symlinks</li>
 <li>Open files in write only mode so rclone can write to an rclone mount</li>
 <li>Fix unnormalised unicode causing problems reading directories</li>
-<li>Fix interaction between -x flag and –max-depth</li>
+<li>Fix interaction between -x flag and --max-depth</li>
 </ul></li>
 <li>Mount
 <ul>
 <li>Implement proper directory handling (mkdir, rmdir, renaming)</li>
 <li>Make include and exclude filters apply to mount</li>
-<li>Implement read and write async buffers - control with –buffer-size</li>
+<li>Implement read and write async buffers - control with --buffer-size</li>
 <li>Fix fsync on for directories</li>
 <li>Fix retry on network failure when reading off crypt</li>
 </ul></li>
 <li>Crypt
 <ul>
-<li>Add –crypt-show-mapping to show encrypted file mapping</li>
+<li>Add --crypt-show-mapping to show encrypted file mapping</li>
 <li>Fix crypt writer getting stuck in a loop
 <ul>
 <li><strong>IMPORTANT</strong> this bug had the potential to cause data corruption when
@@ -19895,9 +20615,9 @@ $ tree /tmp/b
 <li>Drive
 <ul>
 <li>Fix Rmdir on directories with trashed files</li>
-<li>Fix “Ignoring unknown object” when downloading</li>
-<li>Add –drive-list-chunk</li>
-<li>Add –drive-skip-gdocs (Károly Oláh)</li>
+<li>Fix "Ignoring unknown object" when downloading</li>
+<li>Add --drive-list-chunk</li>
+<li>Add --drive-skip-gdocs (Károly Oláh)</li>
 </ul></li>
 <li>OneDrive
 <ul>
@@ -19934,28 +20654,28 @@ $ tree /tmp/b
 <ul>
 <li>moveto and copyto commands for choosing a destination name on copy/move</li>
 <li>rmdirs command to recursively delete empty directories</li>
-<li>Allow repeated –include/–exclude/–filter options</li>
+<li>Allow repeated --include/--exclude/--filter options</li>
 <li>Only show transfer stats on commands which transfer stuff
 <ul>
 <li>show stats on any command using the <code>--stats</code> flag</li>
 </ul></li>
 <li>Allow overlapping directories in move when server side dir move is supported</li>
-<li>Add –stats-unit option - thanks Scott McGillivray</li>
+<li>Add --stats-unit option - thanks Scott McGillivray</li>
 </ul></li>
 <li>Bug Fixes
 <ul>
 <li>Fix the config file being overwritten when two rclone instances are running</li>
 <li>Make rclone lsd obey the filters properly</li>
 <li>Fix compilation on mips</li>
-<li>Fix not transferring files that don’t differ in size</li>
+<li>Fix not transferring files that don't differ in size</li>
 <li>Fix panic on nil retry/fatal error</li>
 </ul></li>
 <li>Mount
 <ul>
 <li>Retry reads on error - should help with reliability a lot</li>
 <li>Report the modification times for directories from the remote</li>
-<li>Add bandwidth accounting and limiting (fixes –bwlimit)</li>
-<li>If –stats provided will show stats and which files are transferring</li>
+<li>Add bandwidth accounting and limiting (fixes --bwlimit)</li>
+<li>If --stats provided will show stats and which files are transferring</li>
 <li>Support R/W files if truncate is set.</li>
 <li>Implement statfs interface so df works</li>
 <li>Note that write is now supported on Amazon Drive</li>
@@ -19978,7 +20698,7 @@ $ tree /tmp/b
 <ul>
 <li>Use new prefix and delimiter parameters in directory listings
 <ul>
-<li>This makes –max-depth 1 dir listings as used in mount much faster</li>
+<li>This makes --max-depth 1 dir listings as used in mount much faster</li>
 </ul></li>
 <li>Reauth the account while doing uploads too - should help with token expiry</li>
 </ul></li>
@@ -19996,7 +20716,7 @@ $ tree /tmp/b
 <li>Stop removing failed upload to cloud storage remotes</li>
 <li>Make ContentType be preserved for cloud to cloud copies</li>
 <li>Add support to toggle bandwidth limits via SIGUSR2 - thanks Marco Paganini</li>
-<li><code>rclone check</code> shows count of hashes that couldn’t be checked</li>
+<li><code>rclone check</code> shows count of hashes that couldn't be checked</li>
 <li><code>rclone listremotes</code> command</li>
 <li>Support linux/arm64 build - thanks Fredrik Fornwall</li>
 <li>Remove <code>Authorization:</code> lines from <code>--dump-headers</code> output</li>
@@ -20010,7 +20730,7 @@ $ tree /tmp/b
 <li>Fix deletion of src file when dst file older</li>
 </ul></li>
 <li>Fix <code>rclone check</code> on crypted file systems</li>
-<li>Make failed uploads not count as “Transferred”</li>
+<li>Make failed uploads not count as "Transferred"</li>
 <li>Make sure high level retries show with <code>-q</code></li>
 <li>Use a vendor directory with godep for repeatable builds</li>
 </ul></li>
@@ -20027,11 +20747,11 @@ $ tree /tmp/b
 <li>with <code>-no-seek</code> flag to disable</li>
 </ul></li>
 <li>Fix crash on 32 bit ARM (alignment of 64 bit counter)</li>
-<li>…and many more internal fixes and improvements!</li>
+<li>...and many more internal fixes and improvements!</li>
 </ul></li>
 <li>Crypt
 <ul>
-<li>Don’t show encrypted password in configurator to stop confusion</li>
+<li>Don't show encrypted password in configurator to stop confusion</li>
 </ul></li>
 <li>Amazon Drive
 <ul>
@@ -20075,7 +20795,7 @@ $ tree /tmp/b
 </ul></li>
 <li>Swift
 <ul>
-<li>Don’t read metadata for directory marker objects</li>
+<li>Don't read metadata for directory marker objects</li>
 </ul></li>
 </ul>
 <h2 id="v1.33---2016-08-24">v1.33 - 2016-08-24</h2>
@@ -20142,7 +20862,7 @@ $ tree /tmp/b
 <li>New Features
 <ul>
 <li>Reduce memory on sync by about 50%</li>
-<li>Implement –no-traverse flag to stop copy traversing the destination remote.
+<li>Implement --no-traverse flag to stop copy traversing the destination remote.
 <ul>
 <li>This can be used to reduce memory usage down to the smallest possible.</li>
 <li>Useful to copy a small number of files into a large destination folder.</li>
@@ -20153,11 +20873,11 @@ $ tree /tmp/b
 </ul></li>
 <li>Single file handling improved
 <ul>
-<li>Now copied with –files-from</li>
-<li>Automatically sets –no-traverse when copying a single file</li>
+<li>Now copied with --files-from</li>
+<li>Automatically sets --no-traverse when copying a single file</li>
 </ul></li>
 <li>Info on using installing with ansible - thanks Stefan Weichinger</li>
-<li>Implement –no-update-modtime flag to stop rclone fixing the remote modified times.</li>
+<li>Implement --no-update-modtime flag to stop rclone fixing the remote modified times.</li>
 </ul></li>
 <li>Bug Fixes
 <ul>
@@ -20179,22 +20899,22 @@ $ tree /tmp/b
 <ul>
 <li>Add instructions on how to use rclone with minio.</li>
 <li>Add ap-northeast-2 (Seoul) and ap-south-1 (Mumbai) regions.</li>
-<li>Skip setting the modified time for objects &gt; 5GB as it isn’t possible.</li>
+<li>Skip setting the modified time for objects &gt; 5GB as it isn't possible.</li>
 </ul></li>
 <li>Backblaze B2
 <ul>
-<li>Add –b2-versions flag so old versions can be listed and retrieved.</li>
+<li>Add --b2-versions flag so old versions can be listed and retrieved.</li>
 <li>Treat 403 errors (eg cap exceeded) as fatal.</li>
 <li>Implement cleanup command for deleting old file versions.</li>
 <li>Make error handling compliant with B2 integrations notes.</li>
 <li>Fix handling of token expiry.</li>
-<li>Implement –b2-test-mode to set <code>X-Bz-Test-Mode</code> header.</li>
+<li>Implement --b2-test-mode to set <code>X-Bz-Test-Mode</code> header.</li>
 <li>Set cutoff for chunked upload to 200MB as per B2 guidelines.</li>
 <li>Make upload multi-threaded.</li>
 </ul></li>
 <li>Dropbox
 <ul>
-<li>Don’t retry 461 errors.</li>
+<li>Don't retry 461 errors.</li>
 </ul></li>
 </ul>
 <h2 id="v1.30---2016-06-18">v1.30 - 2016-06-18</h2>
@@ -20204,17 +20924,17 @@ $ tree /tmp/b
 <li>Directory listing code reworked for more features and better error reporting (thanks to Klaus Post for help). This enables
 <ul>
 <li>Directory include filtering for efficiency</li>
-<li>–max-depth parameter</li>
+<li>--max-depth parameter</li>
 <li>Better error reporting</li>
 <li>More to come</li>
 </ul></li>
 <li>Retry more errors</li>
-<li>Add –ignore-size flag - for uploading images to onedrive</li>
+<li>Add --ignore-size flag - for uploading images to onedrive</li>
 <li>Log -v output to stdout by default</li>
 <li>Display the transfer stats in more human readable form</li>
 <li>Make 0 size files specifiable with <code>--max-size 0b</code></li>
-<li>Add <code>b</code> suffix so we can specify bytes in –bwlimit, –min-size etc</li>
-<li>Use “password:” instead of “password&gt;” prompt - thanks Klaus Post and Leigh Klotz</li>
+<li>Add <code>b</code> suffix so we can specify bytes in --bwlimit, --min-size etc</li>
+<li>Use "password:" instead of "password&gt;" prompt - thanks Klaus Post and Leigh Klotz</li>
 </ul></li>
 <li>Bug Fixes
 <ul>
@@ -20246,7 +20966,7 @@ $ tree /tmp/b
 </ul></li>
 <li>Google Cloud Storage
 <ul>
-<li>Make sure we don’t use conflicting content types on upload</li>
+<li>Make sure we don't use conflicting content types on upload</li>
 <li>Add service account support - thanks Michal Witkowski</li>
 </ul></li>
 <li>Swift
@@ -20278,8 +20998,8 @@ $ tree /tmp/b
 <li>Bug fixes
 <ul>
 <li>Make rclone check obey the <code>--size-only</code> flag.</li>
-<li>Use “application/octet-stream” if discovered mime type is invalid.</li>
-<li>Fix missing “quit” option when there are no remotes.</li>
+<li>Use "application/octet-stream" if discovered mime type is invalid.</li>
+<li>Fix missing "quit" option when there are no remotes.</li>
 </ul></li>
 <li>Google Drive
 <ul>
@@ -20294,7 +21014,7 @@ $ tree /tmp/b
 <ul>
 <li>This means that B2 will now check modification times</li>
 <li>It will upload new files to update the modification times</li>
-<li>(there isn’t an API to just set the mod time.)</li>
+<li>(there isn't an API to just set the mod time.)</li>
 <li>If you want the old behaviour use <code>--size-only</code>.</li>
 </ul></li>
 <li>Update API to new version</li>
@@ -20302,7 +21022,7 @@ $ tree /tmp/b
 </ul></li>
 <li>Swift/Hubic
 <ul>
-<li>Don’t return an MD5SUM for static large objects</li>
+<li>Don't return an MD5SUM for static large objects</li>
 </ul></li>
 <li>S3
 <ul>
@@ -20321,7 +21041,7 @@ $ tree /tmp/b
 </ul></li>
 <li>Bug fixes
 <ul>
-<li>Don’t make directories if <code>--dry-run</code> set</li>
+<li>Don't make directories if <code>--dry-run</code> set</li>
 <li>Fix and document the <code>move</code> command</li>
 <li>Fix redirecting stderr on unix-like OSes when using <code>--log-file</code></li>
 <li>Fix <code>delete</code> command to wait until all finished - fixes missing deletes.</li>
@@ -20331,7 +21051,7 @@ $ tree /tmp/b
 <li>Use one upload URL per go routine fixes <code>more than one upload using auth token</code></li>
 <li>Add pacing, retries and reauthentication - fixes token expiry problems</li>
 <li>Upload without using a temporary file from local (and remotes which support SHA1)</li>
-<li>Fix reading metadata for all files when it shouldn’t have been</li>
+<li>Fix reading metadata for all files when it shouldn't have been</li>
 </ul></li>
 <li>Drive
 <ul>
@@ -20371,7 +21091,7 @@ $ tree /tmp/b
 <li>Amazon Drive
 <ul>
 <li>Fix download of files &gt; 10 GB</li>
-<li>Fix directory traversal (“Next token is expired”) for large directory listings</li>
+<li>Fix directory traversal ("Next token is expired") for large directory listings</li>
 <li>Remove 409 conflict from error codes we will retry - stops very long pauses</li>
 </ul></li>
 <li>Backblaze B2
@@ -20404,9 +21124,9 @@ $ tree /tmp/b
 <ul>
 <li>New Features
 <ul>
-<li>Yandex storage backend - thank you Dmitry Burdeev (“dibu”)</li>
+<li>Yandex storage backend - thank you Dmitry Burdeev ("dibu")</li>
 <li>Implement Backblaze B2 storage backend</li>
-<li>Add –min-age and –max-age flags - thank you Adriano Aurélio Meirelles</li>
+<li>Add --min-age and --max-age flags - thank you Adriano Aurélio Meirelles</li>
 <li>Make ls/lsl/md5sum/size/check obey includes and excludes</li>
 </ul></li>
 <li>Fixes
@@ -20421,7 +21141,7 @@ $ tree /tmp/b
 <li>OneDrive
 <ul>
 <li>Re-enable server side copy</li>
-<li>Don’t mask HTTP error codes with JSON decode error</li>
+<li>Don't mask HTTP error codes with JSON decode error</li>
 </ul></li>
 <li>S3
 <ul>
@@ -20436,7 +21156,7 @@ $ tree /tmp/b
 </ul></li>
 <li>Fixes
 <ul>
-<li>Fix deletion of some excluded files without –delete-excluded
+<li>Fix deletion of some excluded files without --delete-excluded
 <ul>
 <li>This could have deleted files unexpectedly on sync</li>
 <li>Always check first with <code>--dry-run</code>!</li>
@@ -20466,20 +21186,20 @@ $ tree /tmp/b
 <li>Fixes
 <ul>
 <li>Allow spaces in remotes and check remote names for validity at creation time</li>
-<li>Allow ‘&amp;’ and disallow ‘:’ in Windows filenames.</li>
+<li>Allow '&amp;' and disallow ':' in Windows filenames.</li>
 </ul></li>
 <li>Swift
 <ul>
 <li>Ignore directory marker objects where appropriate - allows working with Hubic</li>
-<li>Don’t delete the container if fs wasn’t at root</li>
+<li>Don't delete the container if fs wasn't at root</li>
 </ul></li>
 <li>S3
 <ul>
-<li>Don’t delete the bucket if fs wasn’t at root</li>
+<li>Don't delete the bucket if fs wasn't at root</li>
 </ul></li>
 <li>Google Cloud Storage
 <ul>
-<li>Don’t delete the bucket if fs wasn’t at root</li>
+<li>Don't delete the bucket if fs wasn't at root</li>
 </ul></li>
 </ul>
 <h2 id="v1.23---2015-10-03">v1.23 - 2015-10-03</h2>
@@ -20500,7 +21220,7 @@ $ tree /tmp/b
 </ul></li>
 <li>Swift
 <ul>
-<li>Stop chunked operations logging “Failed to read info: Object Not Found”</li>
+<li>Stop chunked operations logging "Failed to read info: Object Not Found"</li>
 <li>Use Content-Length on uploads for extra reliability</li>
 </ul></li>
 </ul>
@@ -20539,11 +21259,11 @@ $ tree /tmp/b
 <li>Amazon Drive support</li>
 <li>Oauth support redone - fix many bugs and improve usability
 <ul>
-<li>Use “golang.org/x/oauth2” as oauth library of choice</li>
+<li>Use "golang.org/x/oauth2" as oauth library of choice</li>
 <li>Improve oauth usability for smoother initial signup</li>
 <li>drive, googlecloudstorage: optionally use auto config for the oauth token</li>
 </ul></li>
-<li>Implement –dump-headers and –dump-bodies debug flags</li>
+<li>Implement --dump-headers and --dump-bodies debug flags</li>
 <li>Show multiple matched commands if abbreviation too short</li>
 <li>Implement server side move where possible</li>
 </ul></li>
@@ -20563,7 +21283,7 @@ $ tree /tmp/b
 <ul>
 <li>Server side copies for s3/swift/drive/dropbox/gcs</li>
 <li>Move command - uses server side copies if it can</li>
-<li>Implement –retries flag - tries 3 times by default</li>
+<li>Implement --retries flag - tries 3 times by default</li>
 <li>Build for plan9/amd64 and solaris/amd64 too</li>
 </ul></li>
 <li>Fixes
@@ -20582,7 +21302,7 @@ $ tree /tmp/b
 <li>drive
 <ul>
 <li>Add <code>--drive-use-trash</code> flag so rclone trashes instead of deletes</li>
-<li>Add “Forbidden to download” message for files with no downloadURL</li>
+<li>Add "Forbidden to download" message for files with no downloadURL</li>
 </ul></li>
 <li>dropbox
 <ul>
@@ -20617,32 +21337,32 @@ $ tree /tmp/b
 <h2 id="v1.16---2015-06-09">v1.16 - 2015-06-09</h2>
 <ul>
 <li>Fix uploading big files which was causing timeouts or panics</li>
-<li>Don’t check md5sum after download with –size-only</li>
+<li>Don't check md5sum after download with --size-only</li>
 </ul>
 <h2 id="v1.15---2015-06-06">v1.15 - 2015-06-06</h2>
 <ul>
-<li>Add –checksum flag to only discard transfers by MD5SUM - thanks Alex Couper</li>
-<li>Implement –size-only flag to sync on size not checksum &amp; modtime</li>
+<li>Add --checksum flag to only discard transfers by MD5SUM - thanks Alex Couper</li>
+<li>Implement --size-only flag to sync on size not checksum &amp; modtime</li>
 <li>Expand docs and remove duplicated information</li>
-<li>Document rclone’s limitations with directories</li>
+<li>Document rclone's limitations with directories</li>
 <li>dropbox: update docs about case insensitivity</li>
 </ul>
 <h2 id="v1.14---2015-05-21">v1.14 - 2015-05-21</h2>
 <ul>
 <li>local: fix encoding of non utf-8 file names - fixes a duplicate file problem</li>
 <li>drive: docs about rate limiting</li>
-<li>google cloud storage: Fix compile after API change in “google.golang.org/api/storage/v1”</li>
+<li>google cloud storage: Fix compile after API change in "google.golang.org/api/storage/v1"</li>
 </ul>
 <h2 id="v1.13---2015-05-10">v1.13 - 2015-05-10</h2>
 <ul>
 <li>Revise documentation (especially sync)</li>
-<li>Implement –timeout and –conntimeout</li>
-<li>s3: ignore etags from multipart uploads which aren’t md5sums</li>
+<li>Implement --timeout and --conntimeout</li>
+<li>s3: ignore etags from multipart uploads which aren't md5sums</li>
 </ul>
 <h2 id="v1.12---2015-03-15">v1.12 - 2015-03-15</h2>
 <ul>
 <li>drive: Use chunked upload for files above a certain size</li>
-<li>drive: add –drive-chunk-size and –drive-upload-cutoff parameters</li>
+<li>drive: add --drive-chunk-size and --drive-upload-cutoff parameters</li>
 <li>drive: switch to insert from update when a failed copy deletes the upload</li>
 <li>core: Log duplicate files if they are detected</li>
 </ul>
@@ -20653,9 +21373,9 @@ $ tree /tmp/b
 <li>In remote paths, change native directory separators to /</li>
 <li>Add synchronization to ls/lsl/lsd output to stop corruptions</li>
 <li>Ensure all stats/log messages to go stderr</li>
-<li>Add –log-file flag to log everything (including panics) to file</li>
-<li>Make it possible to disable stats printing with –stats=0</li>
-<li>Implement –bwlimit to limit data transfer bandwidth</li>
+<li>Add --log-file flag to log everything (including panics) to file</li>
+<li>Make it possible to disable stats printing with --stats=0</li>
+<li>Implement --bwlimit to limit data transfer bandwidth</li>
 </ul>
 <h2 id="v1.10---2015-02-12">v1.10 - 2015-02-12</h2>
 <ul>
@@ -20680,7 +21400,7 @@ $ tree /tmp/b
 </ul>
 <h2 id="v1.06---2014-12-12">v1.06 - 2014-12-12</h2>
 <ul>
-<li>Fix “Couldn’t find home directory” on OSX</li>
+<li>Fix "Couldn't find home directory" on OSX</li>
 <li>swift: Add tenant parameter</li>
 <li>Use new location of Google API packages</li>
 </ul>
@@ -20711,9 +21431,9 @@ $ tree /tmp/b
 <li>Implement Dropbox remote</li>
 <li>Implement Google Cloud Storage remote</li>
 <li>Verify Md5sums and Sizes after copies</li>
-<li>Remove times from “ls” command - lists sizes only</li>
-<li>Add add “lsl” - lists times and sizes</li>
-<li>Add “md5sum” command</li>
+<li>Remove times from "ls" command - lists sizes only</li>
+<li>Add add "lsl" - lists times and sizes</li>
+<li>Add "md5sum" command</li>
 </ul>
 <h2 id="v1.01---2014-07-04">v1.01 - 2014-07-04</h2>
 <ul>
@@ -20725,7 +21445,7 @@ $ tree /tmp/b
 </ul>
 <h2 id="v0.99---2014-06-26">v0.99 - 2014-06-26</h2>
 <ul>
-<li>Fix –dry-run not working</li>
+<li>Fix --dry-run not working</li>
 <li>Make compatible with go 1.1</li>
 </ul>
 <h2 id="v0.98---2014-05-30">v0.98 - 2014-05-30</h2>
@@ -20742,7 +21462,7 @@ $ tree /tmp/b
 <ul>
 <li>drive: Fix multiple files of same name being created</li>
 <li>drive: Use o.Update and fs.Put to optimise transfers</li>
-<li>Add version number, -V and –version</li>
+<li>Add version number, -V and --version</li>
 </ul>
 <h2 id="v0.95---2014-03-28">v0.95 - 2014-03-28</h2>
 <ul>
@@ -20762,7 +21482,7 @@ $ tree /tmp/b
 </ul>
 <h2 id="v0.92---2014-03-15">v0.92 - 2014-03-15</h2>
 <ul>
-<li>Config fixes and –config option</li>
+<li>Config fixes and --config option</li>
 </ul>
 <h2 id="v0.91---2014-03-15">v0.91 - 2014-03-15</h2>
 <ul>
@@ -20777,17 +21497,17 @@ $ tree /tmp/b
 <li>Project started</li>
 </ul>
 <h1 id="bugs-and-limitations">Bugs and Limitations</h1>
-<h2 id="limitations-21">Limitations</h2>
-<h3 id="directory-timestamps-arent-preserved">Directory timestamps aren’t preserved</h3>
-<p>Rclone doesn’t currently preserve the timestamps of directories. This is because rclone only really considers objects when syncing.</p>
-<h3 id="rclone-struggles-with-millions-of-files-in-a-directory">Rclone struggles with millions of files in a directory</h3>
-<p>Currently rclone loads each directory entirely into memory before using it. Since each Rclone object takes 0.5k-1k of memory this can take a very long time and use an extremely large amount of memory.</p>
-<p>Millions of files in a directory tend caused by software writing cloud storage (eg S3 buckets).</p>
+<h2 id="limitations-14">Limitations</h2>
+<h3 id="directory-timestamps-arent-preserved">Directory timestamps aren't preserved</h3>
+<p>Rclone doesn't currently preserve the timestamps of directories. This is because rclone only really considers objects when syncing.</p>
+<h3 id="rclone-struggles-with-millions-of-files-in-a-directorybucket">Rclone struggles with millions of files in a directory/bucket</h3>
+<p>Currently rclone loads each directory/bucket entirely into memory before using it. Since each rclone object takes 0.5k-1k of memory this can take a very long time and use a large amount of memory.</p>
+<p>Millions of files in a directory tends to occur on bucket-based remotes (e.g. S3 buckets) since those remotes do not segregate subdirectories within the bucket.</p>
 <h3 id="bucket-based-remotes-and-folders">Bucket based remotes and folders</h3>
-<p>Bucket based remotes (eg S3/GCS/Swift/B2) do not have a concept of directories. Rclone therefore cannot create directories in them which means that empty directories on a bucket based remote will tend to disappear.</p>
-<p>Some software creates empty keys ending in <code>/</code> as directory markers. Rclone doesn’t do this as it potentially creates more objects and costs more. It may do in future (probably with a flag).</p>
+<p>Bucket based remotes (e.g. S3/GCS/Swift/B2) do not have a concept of directories. Rclone therefore cannot create directories in them which means that empty directories on a bucket based remote will tend to disappear.</p>
+<p>Some software creates empty keys ending in <code>/</code> as directory markers. Rclone doesn't do this as it potentially creates more objects and costs more. This ability may be added in the future (probably via a flag/option).</p>
 <h2 id="bugs">Bugs</h2>
-<p>Bugs are stored in rclone’s GitHub project:</p>
+<p>Bugs are stored in rclone's GitHub project:</p>
 <ul>
 <li><a href="https://github.com/rclone/rclone/issues?q=is%3Aopen+is%3Aissue+label%3Abug">Reported bugs</a></li>
 <li><a href="https://github.com/rclone/rclone/issues?q=is%3Aopen+is%3Aissue+milestone%3A%22Known+Problem%22">Known issues</a></li>
@@ -20805,18 +21525,18 @@ $ tree /tmp/b
 <p>Note that it effectively downloads the file and uploads it again, so the node running rclone would need to have lots of bandwidth.</p>
 <p>The syncs would be incremental (on a file by file basis).</p>
 <p>Eg</p>
-<pre><code>rclone sync drive:Folder s3:bucket</code></pre>
+<pre><code>rclone sync -i drive:Folder s3:bucket</code></pre>
 <h3 id="using-rclone-from-multiple-locations-at-the-same-time">Using rclone from multiple locations at the same time</h3>
 <p>You can use rclone from multiple places at the same time if you choose different subdirectory for the output, eg</p>
-<pre><code>Server A&gt; rclone sync /tmp/whatever remote:ServerA
-Server B&gt; rclone sync /tmp/whatever remote:ServerB</code></pre>
-<p>If you sync to the same directory then you should use rclone copy otherwise the two instances of rclone may delete each other’s files, eg</p>
+<pre><code>Server A&gt; rclone sync -i /tmp/whatever remote:ServerA
+Server B&gt; rclone sync -i /tmp/whatever remote:ServerB</code></pre>
+<p>If you sync to the same directory then you should use rclone copy otherwise the two instances of rclone may delete each other's files, eg</p>
 <pre><code>Server A&gt; rclone copy /tmp/whatever remote:Backup
 Server B&gt; rclone copy /tmp/whatever remote:Backup</code></pre>
 <p>The file names you upload from Server A and Server B should be different in this case, otherwise some file systems (eg Drive) may make duplicates.</p>
-<h3 id="why-doesnt-rclone-support-partial-transfers-binary-diffs-like-rsync">Why doesn’t rclone support partial transfers / binary diffs like rsync?</h3>
+<h3 id="why-doesnt-rclone-support-partial-transfers-binary-diffs-like-rsync">Why doesn't rclone support partial transfers / binary diffs like rsync?</h3>
 <p>Rclone stores each file you transfer as a native object on the remote cloud storage system. This means that you can see the files you upload as expected using alternative access methods (eg using the Google Drive web interface). There is a 1:1 mapping between files on your hard disk and objects created in the cloud storage system.</p>
-<p>Cloud storage systems (at least none I’ve come across yet) don’t support partially uploading an object. You can’t take an existing object, and change some bytes in the middle of it.</p>
+<p>Cloud storage systems (at least none I've come across yet) don't support partially uploading an object. You can't take an existing object, and change some bytes in the middle of it.</p>
 <p>It would be possible to make a sync system which stored binary diffs instead of whole objects like rclone does, but that would break the 1:1 mapping of files on your hard disk to objects in the remote cloud storage system.</p>
 <p>All the cloud storage systems support partial downloads of content, so it would be possible to make partial downloads work. However to make this work efficiently this would require storing a significant amount of metadata, which breaks the desired 1:1 mapping of files to objects.</p>
 <h3 id="can-rclone-do-bi-directional-sync">Can rclone do bi-directional sync?</h3>
@@ -20830,13 +21550,13 @@ Server B&gt; rclone copy /tmp/whatever remote:Backup</code></pre>
 export https_proxy=$http_proxy
 export HTTP_PROXY=$http_proxy
 export HTTPS_PROXY=$http_proxy</code></pre>
-<p>The <code>NO_PROXY</code> allows you to disable the proxy for specific hosts. Hosts must be comma separated, and can contain domains or parts. For instance “foo.com” also matches “bar.foo.com”.</p>
+<p>The <code>NO_PROXY</code> allows you to disable the proxy for specific hosts. Hosts must be comma separated, and can contain domains or parts. For instance "foo.com" also matches "bar.foo.com".</p>
 <p>e.g.</p>
 <pre><code>export no_proxy=localhost,127.0.0.0/8,my.host.name
 export NO_PROXY=$no_proxy</code></pre>
 <p>Note that the ftp backend does not support <code>ftp_proxy</code> yet.</p>
 <h3 id="rclone-gives-x509-failed-to-load-system-roots-and-no-roots-provided-error">Rclone gives x509: failed to load system roots and no roots provided error</h3>
-<p>This means that <code>rclone</code> can’t file the SSL root certificates. Likely you are running <code>rclone</code> on a NAS with a cut-down Linux OS, or possibly on Solaris.</p>
+<p>This means that <code>rclone</code> can't file the SSL root certificates. Likely you are running <code>rclone</code> on a NAS with a cut-down Linux OS, or possibly on Solaris.</p>
 <p>Rclone (via the Go runtime) tries to load the root certificates from these places on Linux.</p>
 <pre><code>&quot;/etc/ssl/certs/ca-certificates.crt&quot;, // Debian/Ubuntu/Gentoo etc.
 &quot;/etc/pki/tls/certs/ca-bundle.crt&quot;,   // Fedora/RHEL
@@ -20847,13 +21567,13 @@ export NO_PROXY=$no_proxy</code></pre>
 curl -o /etc/ssl/certs/ca-certificates.crt https://raw.githubusercontent.com/bagder/ca-bundle/master/ca-bundle.crt
 ntpclient -s -h pool.ntp.org</code></pre>
 <p>The two environment variables <code>SSL_CERT_FILE</code> and <code>SSL_CERT_DIR</code>, mentioned in the <a href="https://godoc.org/crypto/x509">x509 package</a>, provide an additional way to provide the SSL root certificates.</p>
-<p>Note that you may need to add the <code>--insecure</code> option to the <code>curl</code> command line if it doesn’t work without.</p>
+<p>Note that you may need to add the <code>--insecure</code> option to the <code>curl</code> command line if it doesn't work without.</p>
 <pre><code>curl --insecure -o /etc/ssl/certs/ca-certificates.crt https://raw.githubusercontent.com/bagder/ca-bundle/master/ca-bundle.crt</code></pre>
 <h3 id="rclone-gives-failed-to-load-config-file-function-not-implemented-error">Rclone gives Failed to load config file: function not implemented error</h3>
 <p>Likely this means that you are running rclone on Linux version not supported by the go runtime, ie earlier than version 2.6.23.</p>
 <p>See the <a href="https://golang.org/doc/install">system requirements section in the go install docs</a> for full details.</p>
 <h3 id="all-my-uploaded-docxxlsxpptx-files-appear-as-archivezip">All my uploaded docx/xlsx/pptx files appear as archive/zip</h3>
-<p>This is caused by uploading these files from a Windows computer which hasn’t got the Microsoft Office suite installed. The easiest way to fix is to install the Word viewer and the Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 and later versions’ file formats</p>
+<p>This is caused by uploading these files from a Windows computer which hasn't got the Microsoft Office suite installed. The easiest way to fix is to install the Word viewer and the Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 and later versions' file formats</p>
 <h3 id="tcp-lookup-some.domain.com-no-such-host">tcp lookup some.domain.com no such host</h3>
 <p>This happens when rclone cannot resolve a domain. Please check that your DNS setup is generally working, e.g.</p>
 <pre><code># both should print a long list of possible IP addresses
@@ -20862,7 +21582,7 @@ dig www.googleapis.com @8.8.8.8 # resolve with Google&#39;s DNS server</code></p
 <p>If you are using <code>systemd-resolved</code> (default on Arch Linux), ensure it is at version 233 or higher. Previous releases contain a bug which causes not all domains to be resolved properly.</p>
 <p>Additionally with the <code>GODEBUG=netdns=</code> environment variable the Go resolver decision can be influenced. This also allows to resolve certain issues with DNS resolution. See the <a href="https://golang.org/pkg/net/#hdr-Name_Resolution">name resolution section in the go docs</a>.</p>
 <h3 id="the-total-size-reported-in-the-stats-for-a-sync-is-wrong-and-keeps-changing">The total size reported in the stats for a sync is wrong and keeps changing</h3>
-<p>It is likely you have more than 10,000 files that need to be synced. By default rclone only gets 10,000 files ahead in a sync so as not to use up too much memory. You can change this default with the <a href="https://rclone.org/docs/#max-backlog-n">–max-backlog</a> flag.</p>
+<p>It is likely you have more than 10,000 files that need to be synced. By default rclone only gets 10,000 files ahead in a sync so as not to use up too much memory. You can change this default with the <a href="https://rclone.org/docs/#max-backlog-n">--max-backlog</a> flag.</p>
 <h3 id="rclone-is-using-too-much-memory-or-appears-to-have-a-memory-leak">Rclone is using too much memory or appears to have a memory leak</h3>
 <p>Rclone is written in Go which uses a garbage collector. The default settings for the garbage collector mean that it runs when the heap size has doubled.</p>
 <p>However it is possible to tune the garbage collector to use less memory by <a href="https://dave.cheney.net/tag/gogc">setting GOGC</a> to a lower value, say <code>export GOGC=20</code>. This will make the garbage collector work harder, reducing memory size at the expense of CPU usage.</p>
@@ -21070,7 +21790,7 @@ THE SOFTWARE.</code></pre>
 <li>Denis <a href="mailto:deniskovpen@gmail.com" class="email">deniskovpen@gmail.com</a></li>
 <li>bsteiss <a href="mailto:35940619+bsteiss@users.noreply.github.com" class="email">35940619+bsteiss@users.noreply.github.com</a></li>
 <li>Cédric Connes <a href="mailto:cedric.connes@gmail.com" class="email">cedric.connes@gmail.com</a></li>
-<li>Dr. Tobias Quathamer <a href="mailto:toddy15@users.noreply.github.com" class="email">toddy15@users.noreply.github.com</a></li>
+<li>Dr. Tobias Quathamer <a href="mailto:toddy15@users.noreply.github.com" class="email">toddy15@users.noreply.github.com</a></li>
 <li>dcpu <a href="mailto:42736967+dcpu@users.noreply.github.com" class="email">42736967+dcpu@users.noreply.github.com</a></li>
 <li>Sheldon Rupp <a href="mailto:me@shel.io" class="email">me@shel.io</a></li>
 <li>albertony <a href="mailto:12441419+albertony@users.noreply.github.com" class="email">12441419+albertony@users.noreply.github.com</a></li>
@@ -21257,6 +21977,38 @@ THE SOFTWARE.</code></pre>
 <li>Martin Michlmayr <a href="mailto:tbm@cyrius.com" class="email">tbm@cyrius.com</a></li>
 <li>Brandon McNama <a href="mailto:bmcnama@pagerduty.com" class="email">bmcnama@pagerduty.com</a></li>
 <li>Daniel Slyman <a href="mailto:github@skylayer.eu" class="email">github@skylayer.eu</a></li>
+<li>Alex Guerrero <a href="mailto:guerrero@users.noreply.github.com" class="email">guerrero@users.noreply.github.com</a></li>
+<li>Matteo Pietro Dazzi <a href="mailto:matteopietro.dazzi@gft.com" class="email">matteopietro.dazzi@gft.com</a></li>
+<li>edwardxml <a href="mailto:56691903+edwardxml@users.noreply.github.com" class="email">56691903+edwardxml@users.noreply.github.com</a></li>
+<li>Roman Kredentser <a href="mailto:shareed2k@gmail.com" class="email">shareed2k@gmail.com</a></li>
+<li>Kamil Trzciński <a href="mailto:ayufan@ayufan.eu" class="email">ayufan@ayufan.eu</a></li>
+<li>Zac Rubin <a href="mailto:z-0@users.noreply.github.com" class="email">z-0@users.noreply.github.com</a></li>
+<li>Vincent Feltz <a href="mailto:psycho@feltzv.fr" class="email">psycho@feltzv.fr</a></li>
+<li>Heiko Bornholdt <a href="mailto:bornholdt@informatik.uni-hamburg.de" class="email">bornholdt@informatik.uni-hamburg.de</a></li>
+<li>Matteo Pietro Dazzi <a href="mailto:matteopietro.dazzi@gmail.com" class="email">matteopietro.dazzi@gmail.com</a></li>
+<li>jtagcat <a href="mailto:gitlab@c7.ee" class="email">gitlab@c7.ee</a></li>
+<li>Petri Salminen <a href="mailto:petri@salminen.dev" class="email">petri@salminen.dev</a></li>
+<li>Tim Burke <a href="mailto:tim.burke@gmail.com" class="email">tim.burke@gmail.com</a></li>
+<li>Kai Lüke <a href="mailto:kai@kinvolk.io" class="email">kai@kinvolk.io</a></li>
+<li>Garrett Squire <a href="mailto:github@garrettsquire.com" class="email">github@garrettsquire.com</a></li>
+<li>Evan Harris <a href="mailto:eharris@puremagic.com" class="email">eharris@puremagic.com</a></li>
+<li>Kevin <a href="mailto:keyam@microsoft.com" class="email">keyam@microsoft.com</a></li>
+<li>Morten Linderud <a href="mailto:morten@linderud.pw" class="email">morten@linderud.pw</a></li>
+<li>Dmitry Ustalov <a href="mailto:dmitry.ustalov@gmail.com" class="email">dmitry.ustalov@gmail.com</a></li>
+<li>Jack <a href="mailto:196648+jdeng@users.noreply.github.com" class="email">196648+jdeng@users.noreply.github.com</a></li>
+<li>kcris <a href="mailto:cristian.tarsoaga@gmail.com" class="email">cristian.tarsoaga@gmail.com</a></li>
+<li>tyhuber1 <a href="mailto:68970760+tyhuber1@users.noreply.github.com" class="email">68970760+tyhuber1@users.noreply.github.com</a></li>
+<li>David Ibarra <a href="mailto:david.ibarra@realty.com" class="email">david.ibarra@realty.com</a></li>
+<li>Tim Gallant <a href="mailto:tim@lilt.com" class="email">tim@lilt.com</a></li>
+<li>Kaloyan Raev <a href="mailto:kaloyan@storj.io" class="email">kaloyan@storj.io</a></li>
+<li>Jay McEntire <a href="mailto:jay.mcentire@gmail.com" class="email">jay.mcentire@gmail.com</a></li>
+<li>Leo Luan <a href="mailto:leoluan@us.ibm.com" class="email">leoluan@us.ibm.com</a></li>
+<li>aus <a href="mailto:549081+aus@users.noreply.github.com" class="email">549081+aus@users.noreply.github.com</a></li>
+<li>Aaron Gokaslan <a href="mailto:agokaslan@fb.com" class="email">agokaslan@fb.com</a></li>
+<li>Egor Margineanu <a href="mailto:egmar@users.noreply.github.com" class="email">egmar@users.noreply.github.com</a></li>
+<li>Lucas Kanashiro <a href="mailto:lucas.kanashiro@canonical.com" class="email">lucas.kanashiro@canonical.com</a></li>
+<li>WarpedPixel <a href="mailto:WarpedPixel@users.noreply.github.com" class="email">WarpedPixel@users.noreply.github.com</a></li>
+<li>Sam Edwards <a href="mailto:sam@samedwards.ca" class="email">sam@samedwards.ca</a></li>
 </ul>
 <h1 id="contact-the-rclone-project">Contact the rclone project</h1>
 <h2 id="forum">Forum</h2>
@@ -21265,7 +22017,7 @@ THE SOFTWARE.</code></pre>
 <li>https://forum.rclone.org</li>
 </ul>
 <h2 id="github-repository">GitHub repository</h2>
-<p>The project’s repository is located at:</p>
+<p>The project's repository is located at:</p>
 <ul>
 <li>https://github.com/rclone/rclone</li>
 </ul>
@@ -21276,6 +22028,6 @@ THE SOFTWARE.</code></pre>
 <li><span class="citation" data-cites="njcw">[@njcw]</span>(https://twitter.com/njcw)</li>
 </ul>
 <h2 id="email">Email</h2>
-<p>Or if all else fails or you want to ask something private or confidential email <a href="mailto:nick@craig-wood.com">Nick Craig-Wood</a>. Please don’t email me requests for help - those are better directed to the forum. Thanks!</p>
+<p>Or if all else fails or you want to ask something private or confidential email <a href="mailto:nick@craig-wood.com">Nick Craig-Wood</a>. Please don't email me requests for help - those are better directed to the forum. Thanks!</p>
 </body>
 </html>
diff --git a/MANUAL.md b/MANUAL.md
index da3f4345e..35427b836 100644
--- a/MANUAL.md
+++ b/MANUAL.md
@@ -1,15 +1,15 @@
 % rclone(1) User Manual
 % Nick Craig-Wood
-% May 27, 2020
+% Sep 02, 2020
 
 # Rclone syncs your files to cloud storage
 
 <img width="50%" src="https://rclone.org/img/logo_on_light__horizontal_color.svg" alt="rclone logo" style="float:right; padding: 5px;" >
 
 - [About rclone](#about)
-- [What can rclone do for you](#what)
-- [What features does rclone have](#features)
-- [What providers does rclone support](#providers)
+- [What can rclone do for you?](#what)
+- [What features does rclone have?](#features)
+- [What providers does rclone support?](#providers)
 - [Download](https://rclone.org/downloads/)
 - [Install](https://rclone.org/install/)
 - [Donate.](https://rclone.org/donate/)
@@ -24,20 +24,20 @@ services, as well as standard transfer protocols.
 
 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 `--dry-run` protection. It can be
+includes shell pipeline support, and `--dry-run` protection. It is
 used at the command line, in scripts or via its [API](/rc).
 
-Users have called rclone *"The Swiss army knife of cloud storage"* and
+Users call rclone *"The Swiss army knife of cloud storage"*, and
 *"Technology indistinguishable from magic"*.
 
 Rclone really looks after your data. It preserves timestamps and
-verifies your data at all times. Transfers over limited bandwidth;
+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
 [check](https://rclone.org/commands/rclone_check/) 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 your local disk.
+using local disk.
 
 Virtual backends wrap local and cloud file systems to apply
 [encryption](https://rclone.org/crypt/), 
@@ -45,9 +45,9 @@ Virtual backends wrap local and cloud file systems to apply
 [chunking](https://rclone.org/chunker/) and
 [joining](https://rclone.org/union/).
 
-Rclone can [mount](https://rclone.org/commands/rclone_mount/) any local, cloud or
+Rclone [mounts](https://rclone.org/commands/rclone_mount/) any local, cloud or
 virtual filesystem as a disk on Windows,
-macOS, linux and FreeBSD, and also serve these over
+macOS, linux and FreeBSD, and also serves these over
 [SFTP](https://rclone.org/commands/rclone_serve_sftp/),
 [HTTP](https://rclone.org/commands/rclone_serve_http/),
 [WebDAV](https://rclone.org/commands/rclone_serve_webdav/),
@@ -61,14 +61,14 @@ Fedora, Brew and Chocolatey repos. include rclone. For the latest
 version [downloading from rclone.org](https://rclone.org/downloads/) is recommended.
 
 Rclone is widely used on Linux, Windows and Mac. Third party
-developers have built innovative backup, restore, GUI and business
+developers create innovative backup, restore, GUI and business
 process solutions using the rclone command line or API.
 
-Let rclone do the heavy lifting of communicating with cloud storage.
+Rclone does the heavy lifting of communicating with cloud storage.
 
-## What can rclone do for you {#what}
+## What can rclone do for you? {#what}
 
-Rclone can help you:
+Rclone helps you:
 
 - Backup (and encrypt) files to cloud storage
 - Restore (and decrypt) files from cloud storage
@@ -96,7 +96,7 @@ Rclone can help you:
 
 ## Supported providers {#providers}
 
-(There are many other providers, built on standard protocols such as
+(There are many others, built on standard protocols such as
 WebDAV or S3, that work out of the box.)
 
 
@@ -292,6 +292,13 @@ from the rclone image.
   reside on the host with a non-root UID:GID, you need to pass these on the container
   start command line.
 
+- If you want to access the RC interface (either via the API or the Web UI), it is
+  required to set the `--rc-addr` to `:5572` in order to connect to it from outside
+  the container. An explanation about why this is necessary is present [here](https://web.archive.org/web/20200808071950/https://pythonspeed.com/articles/docker-connection-refused/).
+    * NOTE: Users running this container with the docker network set to `host` should
+     probably set it to listen to localhost only, with `127.0.0.1:5572` as the value for
+      `--rc-addr`
+
 - It is possible to use `rclone mount` inside a userspace Docker container, and expose
   the resulting fuse mount to the host. The exact `docker run` options to do that might
   vary slightly between hosts. See, e.g. the discussion in this
@@ -330,7 +337,7 @@ kill %1
 
 ## Install from source ##
 
-Make sure you have at least [Go](https://golang.org/) 1.7
+Make sure you have at least [Go](https://golang.org/) 1.11
 installed.  [Download go](https://golang.org/dl/) if necessary.  The
 latest release is recommended. Then
 
@@ -339,16 +346,23 @@ latest release is recommended. Then
     go build
     ./rclone version
 
-You can also build and install rclone in the
-[GOPATH](https://github.com/golang/go/wiki/GOPATH) (which defaults to
-`~/go`) with:
+This will leave you a checked out version of rclone you can modify and
+send pull requests with. If you use `make` instead of `go build` then
+the rclone build will have the correct version information in it.
 
-    go get -u -v github.com/rclone/rclone
+You can also build the latest stable rclone with:
 
-and this will build the binary in `$GOPATH/bin` (`~/go/bin/rclone` by
-default) after downloading the source to
-`$GOPATH/src/github.com/rclone/rclone` (`~/go/src/github.com/rclone/rclone`
-by default).
+    go get github.com/rclone/rclone
+
+or the latest version (equivalent to the beta) with
+
+    go get github.com/rclone/rclone@master
+
+These will build the binary in `$(go env GOPATH)/bin`
+(`~/go/bin/rclone` by default) after downloading the source to the go
+module cache. Note - do **not** use the `-u` flag here. This causes go
+to try to update the depencencies that rclone uses and sometimes these
+don't work with the current version of rclone.
 
 ## Installation with Ansible ##
 
@@ -436,6 +450,9 @@ storage system in the config file then the sub path, eg
 
 You can define as many storage paths as you like in the config file.
 
+Please use the [`-i` / `--interactive`](#interactive) flag while
+learning rclone to avoid accidental data loss.
+
 Subcommands
 -----------
 
@@ -443,7 +460,7 @@ rclone uses a system of subcommands.  For example
 
     rclone ls remote:path # lists a remote
     rclone copy /local/path remote:path # copies /local/path to the remote
-    rclone sync /local/path remote:path # syncs /local/path to the remote
+    rclone sync -i /local/path remote:path # syncs /local/path to the remote
 
 # rclone config
 
@@ -538,7 +555,9 @@ recently very efficiently like this:
 
     rclone copy --max-age 24h --no-traverse /path/to/src remote:
 
-**Note**: Use the `-P`/`--progress` flag to view real-time transfer statistics
+**Note**: Use the `-P`/`--progress` flag to view real-time transfer statistics.
+
+**Note**: Use the `--dry-run` or the `--interactive`/`-i` flag to test without copying anything.
 
 
 ```
@@ -571,7 +590,9 @@ modification time or MD5SUM.  Destination is updated to match
 source, including deleting files if necessary.
 
 **Important**: Since this can cause data loss, test first with the
-`--dry-run` flag to see exactly what would be copied and deleted.
+`--dry-run` or the `--interactive`/`-i` flag.
+
+    rclone sync -i SOURCE remote:DESTINATION
 
 Note that files in the destination won't be deleted if there were any
 errors at any point.
@@ -633,7 +654,7 @@ option when moving a small number of files into a large destination
 can speed transfers up greatly.
 
 **Important**: Since this can cause data loss, test first with the
---dry-run flag.
+`--dry-run` or the `--interactive`/`-i` flag.
 
 **Note**: Use the `-P`/`--progress` flag to view real-time transfer statistics.
 
@@ -686,6 +707,9 @@ Then delete
 That reads "delete everything with a minimum size of 100 MB", hence
 delete all files bigger than 100MBytes.
 
+**Important**: Since this can cause data loss, test first with the
+`--dry-run` or the `--interactive`/`-i` flag.
+
 
 ```
 rclone delete remote:path [flags]
@@ -715,6 +739,9 @@ Remove the path and all of its contents.  Note that this does not obey
 include/exclude filters - everything will be removed.  Use `delete` if
 you want to selectively delete files.
 
+**Important**: Since this can cause data loss, test first with the
+`--dry-run` or the `--interactive`/`-i` flag.
+
 
 ```
 rclone purge remote:path [flags]
@@ -801,9 +828,26 @@ 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.
 
-If you supply the --one-way flag, it will only check that files in source
-match the files in destination, not the other way around. Meaning extra files in
-destination that are not in the source will not trigger an error.
+If you supply the `--one-way` 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.
+
+The `--differ`, `--missing-on-dst`, `--missing-on-src`, `--src-only`
+and `--error` flags write paths, one per line, to the file name (or
+stdout if it is `-`) supplied. What they write is described in the
+help below. For example `--differ` will write all paths which are
+present on both the source and destination but different.
+
+The `--combined` 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.
+
+- `= path` means path was found in source and destination and was identical
+- `- path` means path was missing on the source, so only in the destination
+- `+ path` means path was missing on the destination, so only in the source
+- `* path` means path was present in source and destination but different.
+- `! path` means there was an error reading or hashing the source or dest.
 
 
 ```
@@ -813,9 +857,14 @@ rclone check source:path dest:path [flags]
 ## Options
 
 ```
-      --download   Check by downloading rather than with hash.
-  -h, --help       help for check
-      --one-way    Check one way only, source files must exist on remote
+      --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 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
 ```
 
 See the [global flags page](https://rclone.org/flags/) for global options not listed here.
@@ -1169,23 +1218,38 @@ See the [global flags page](https://rclone.org/flags/) for global options not li
 
 # rclone dedupe
 
-Interactively find duplicate files and delete/rename them.
+Interactively find duplicate filenames and delete/rename them.
 
 ## Synopsis
 
 
-By default `dedupe` interactively finds duplicate files and offers to
-delete all but one or rename them to be different. Only useful with
-Google Drive which can have duplicate file names.
+
+By default `dedupe` interactively finds files with duplicate
+names and offers to delete all but one or rename them to be
+different.
+
+This is only useful with backends like Google Drive which can have
+duplicate file names. It can be run on wrapping backends (eg crypt) if
+they wrap a backend which supports duplicate file names.
 
 In the first pass it will merge directories with the same name.  It
-will do this iteratively until all the identical directories have been
-merged.
+will do this iteratively until all the identically named directories
+have been merged.
 
-The `dedupe` command will delete all but one of any identical (same
-md5sum) files it finds without confirmation.  This means that for most
-duplicated files the `dedupe` command will not be interactive.  You
-can use `--dry-run` to see what would happen without doing anything.
+In the second pass, for every group of duplicate file names, it will
+delete all but one identical files it finds without confirmation.
+This means that for most duplicated files the `dedupe`
+command will not be interactive.
+
+`dedupe` considers files to be identical if they have the
+same hash. If the backend does not support hashes (eg crypt wrapping
+Google Drive) then they will never be found to be identical. If you
+use the `--size-only` 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.
+
+**Important**: Since this can cause data loss, test first with the
+`--dry-run` or the `--interactive`/`-i` flag.
 
 Here is an example run.
 
@@ -1204,22 +1268,22 @@ Now the `dedupe` session
 
     $ rclone dedupe drive:dupes
     2016/03/05 16:24:37 Google drive root 'dupes': Looking for duplicates using interactive mode.
-    one.txt: Found 4 duplicates - deleting identical copies
-    one.txt: Deleting 2/3 identical duplicates (md5sum "1eedaa9fe86fd4b8632e2ac549403b36")
+    one.txt: Found 4 files with duplicate names
+    one.txt: Deleting 2/3 identical duplicates (MD5 "1eedaa9fe86fd4b8632e2ac549403b36")
     one.txt: 2 duplicates remain
-      1:      6048320 bytes, 2016-03-05 16:23:16.798000000, md5sum 1eedaa9fe86fd4b8632e2ac549403b36
-      2:       564374 bytes, 2016-03-05 16:23:06.731000000, md5sum 7594e7dc9fc28f727c42ee3e0749de81
+      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> k
     Enter the number of the file to keep> 1
     one.txt: Deleted 1 extra copies
-    two.txt: Found 3 duplicates - deleting identical copies
+    two.txt: Found 3 files with duplicates names
     two.txt: 3 duplicates remain
-      1:       564374 bytes, 2016-03-05 16:22:52.118000000, md5sum 7594e7dc9fc28f727c42ee3e0749de81
-      2:      6048320 bytes, 2016-03-05 16:22:46.185000000, md5sum 1eedaa9fe86fd4b8632e2ac549403b36
-      3:      1744073 bytes, 2016-03-05 16:22:38.104000000, md5sum 851957f7fb6f0bc4ce76be966d336802
+      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)
@@ -1971,9 +2035,26 @@ the files in remote:path.
 
 After it has run it will log the status of the encryptedremote:.
 
-If you supply the --one-way flag, it will only check that files in source
-match the files in destination, not the other way around. Meaning extra files in
-destination that are not in the source will not trigger an error.
+If you supply the `--one-way` 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.
+
+The `--differ`, `--missing-on-dst`, `--missing-on-src`, `--src-only`
+and `--error` flags write paths, one per line, to the file name (or
+stdout if it is `-`) supplied. What they write is described in the
+help below. For example `--differ` will write all paths which are
+present on both the source and destination but different.
+
+The `--combined` 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.
+
+- `= path` means path was found in source and destination and was identical
+- `- path` means path was missing on the source, so only in the destination
+- `+ path` means path was missing on the destination, so only in the source
+- `* path` means path was present in source and destination but different.
+- `! path` means there was an error reading or hashing the source or dest.
 
 
 ```
@@ -1983,8 +2064,14 @@ rclone cryptcheck remote:path cryptedremote:path [flags]
 ## Options
 
 ```
-  -h, --help      help for cryptcheck
-      --one-way   Check one way only, source files must exist on destination
+      --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
 ```
 
 See the [global flags page](https://rclone.org/flags/) for global options not listed here.
@@ -2275,16 +2362,27 @@ Generate public link to file/folder.
 
 ## Synopsis
 
-
-rclone link will create or retrieve a public link to the given file or folder.
+rclone link will create, retrieve or remove a public link to the given
+file or folder.
 
     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
 
-If successful, the last line of the output will contain the link. Exact
-capabilities depend on the remote, but the link will always be created with
-the least constraints – e.g. no expiry, no password protection, accessible
-without account.
+If you supply the --expire flag, it will set the expiration time
+otherwise it will use the default (100 years). **Note** not all
+backends support the --expire flag - if the backend doesn't support it
+then the link returned won't expire.
+
+Use the --unlink flag to remove existing public links to the file or
+folder. **Note** not all backends support "--unlink" flag - those that
+don't will just ignore it.
+
+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.
 
 
 ```
@@ -2294,7 +2392,9 @@ rclone link remote:path [flags]
 ## Options
 
 ```
-  -h, --help   help for link
+      --expire Duration   The amount of time that the link will be valid (default 100y)
+  -h, --help              help for link
+      --unlink            Remove existing public link to file/folder
 ```
 
 See the [global flags page](https://rclone.org/flags/) for global options not listed here.
@@ -2789,20 +2889,39 @@ When --vfs-read-chunk-size-limit 500M is specified, the result would be
 Chunked reading will only work with --vfs-cache-mode < full, as the file will always
 be copied to the vfs cache before opening with --vfs-cache-mode full.
 
-## Directory Cache
+## VFS - Virtual File System
 
-Using the `--dir-cache-time` flag, you can set how long a
+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.
+
+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.
+
+The VFS layer also implements a directory cache - this caches info
+about files and directories (but not the data) in memory.
+
+## VFS Directory Cache
+
+Using the `--dir-cache-time` flag, you can control how long a
 directory should be considered up to date and not refreshed from the
-backend. Changes made locally in the mount may appear immediately or
-invalidate the cache. However, changes done on the remote will only
-be picked up once the cache expires if the backend configured does not
-support polling for changes. If the backend supports polling, changes
-will be picked up on within the polling interval.
+backend. Changes made through the mount will appear immediately or
+invalidate the cache.
 
-Alternatively, you can send a `SIGHUP` 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:
+    --dir-cache-time duration   Time to cache directory entries for. (default 5m0s)
+    --poll-interval duration    Time to wait between polling for changes.
+
+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.
+
+You can send a `SIGHUP` 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:
 
     kill -SIGHUP $(pidof rclone)
 
@@ -2815,40 +2934,41 @@ Or individual files or directories:
 
     rclone rc vfs/forget file=path/to/file dir=path/to/dir
 
-## File Buffering
+## VFS File Buffering
 
 The `--buffer-size` flag determines the amount of memory,
 that will be used to buffer data in advance.
 
-Each open file descriptor will try to keep the specified amount of
-data in memory at all times. The buffered data is bound to one file
-descriptor and won't be shared between multiple open file descriptors
-of the same file.
+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.
+
+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.
 
-This flag is a upper limit for the used memory per file descriptor.
-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.
 The maximum memory used by rclone for buffering can be up to
 `--buffer-size * open files`.
 
-## File Caching
+## VFS File Caching
 
-These flags control the VFS file caching options.  The VFS layer is
-used by rclone mount to make a cloud storage system work more like a
-normal file system.
+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.
 
-You'll need to enable VFS caching if you want, for example, to read
-and write simultaneously to a file.  See below for more details.
+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.
 
-Note that the VFS cache works in addition to the cache backend and you
-may find that you need one or the other or both.
+Note that the VFS cache is separate from the cache backend and you may
+find that you need one or the other or both.
 
     --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 age of objects in the cache. (default 1h0m0s)
-    --vfs-cache-mode string              Cache mode off|minimal|writes|full (default "off")
+    --vfs-cache-max-size SizeSuffix      Max total size of objects in the cache. (default off)
     --vfs-cache-poll-interval duration   Interval to poll the cache for stale objects. (default 1m0s)
-    --vfs-cache-max-size int             Max total size of objects in the cache. (default off)
+    --vfs-write-back duration            Time to writeback files after last use when using cache. (default 5s)
 
 If run with `-vv` rclone will print the location of the file cache.  The
 files are stored in the user cache file area which is OS dependent but
@@ -2860,9 +2980,10 @@ The higher the cache mode the more compatible rclone becomes at the
 cost of using disk space.
 
 Note that files are written back to the remote only when they are
-closed so if rclone is quit or dies with open files then these won't
-get written back to the remote.  However they will still be in the on
-disk cache.
+closed and if they haven't been accessed for --vfs-write-back
+second. 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.
 
 If using --vfs-cache-max-size note that the cache may exceed this size
 for two reasons.  Firstly because it is only checked every
@@ -2871,7 +2992,7 @@ evicted from the cache.
 
 ### --vfs-cache-mode off
 
-In this mode the cache will read directly from the remote and write
+In this mode (the default) the cache will read directly from the remote and write
 directly to the remote without caching anything on disk.
 
 This will mean some operations are not possible
@@ -2887,7 +3008,7 @@ This will mean some operations are not possible
 ### --vfs-cache-mode minimal
 
 This is very similar to "off" except that files opened for read AND
-write will be buffered to disks.  This means that files opened for
+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.
 
 These operations are not possible
@@ -2905,32 +3026,72 @@ first.
 
 This mode should support all normal file system operations.
 
-If an upload fails it will be retried up to --low-level-retries times.
+If an upload fails it will be retried at exponentially increasing
+intervals up to 1 minute.
 
 ### --vfs-cache-mode full
 
-In this mode all reads and writes are buffered to and from disk.  When
-a file is opened for read it will be downloaded in its entirety first.
+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.
 
-This may be appropriate for your needs, or you may prefer to look at
-the cache backend which does a much more sophisticated job of caching,
-including caching directory hierarchies and chunks of files.
+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 dowloaded.
 
-In this mode, unlike the others, when a file is written to the disk,
-it will be kept on the disk after it is written to the remote.  It
-will be purged on a schedule according to `--vfs-cache-max-age`.
+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.
 
-This mode should support all normal file system operations.
+This mode should support all normal file system operations and is
+otherwise identical to --vfs-cache-mode writes.
 
-If an upload or download fails it will be retried up to
---low-level-retries times.
+When reading a file rclone will read --buffer-size plus
+--vfs-read-ahead bytes ahead.  The --buffer-size is buffered in memory
+whereas the --vfs-read-ahead is buffered on disk.
 
-## Case Sensitivity
+When using this mode it is recommended that --buffer-size is not set
+too big and --vfs-read-ahead is set large if required.
+
+## VFS Performance
+
+These flags may be used to enable/disable features of the VFS for
+performance or other reasons.
+
+In particular S3 and Swift benefit hugely from the --no-modtime flag
+(or use --use-server-modtime for a slightly different effect) as each
+read of the modification time takes a transaction.
+
+    --no-checksum     Don't compare checksums on up/download.
+    --no-modtime      Don't read/write the modification time (can speed things up).
+    --no-seek         Don't allow seeking in files.
+    --read-only       Mount read-only.
+
+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 is advantageous because some cloud providers
+account for reads being all the data requested, not all the data
+delivered.
+
+Rclone will keep doubling the chunk size requested starting at
+--vfs-read-chunk-size with a maximum of --vfs-read-chunk-size-limit
+unless it is set to "off" in which case there will be no limit.
+
+    --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")
+
+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.
+
+    --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)
+
+## VFS Case Sensitivity
 
 Linux file systems are case-sensitive: two files can differ only
 by case, and the exact case must be used when opening a file.
 
-Windows is not like most other operating systems supported by rclone.
 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.
@@ -2941,7 +3102,7 @@ file systems case-sensitive but that is not the default
 
 The "--vfs-case-insensitive" mount flag controls how rclone handles these
 two cases. If its value is "false", rclone passes file names to the mounted
-file system as is. If the flag is "true" (or appears without a value on
+file system as-is. If the flag is "true" (or appears without a value on
 command line), rclone may perform a "fixup" as explained below.
 
 The user may specify a file name to open/delete/rename/etc with a case
@@ -2957,7 +3118,7 @@ Note that case sensitivity of the operating system running rclone (the target)
 may differ from case sensitivity of a file system mounted by rclone (the source).
 The flag controls whether "fixup" is performed to satisfy the target.
 
-If the flag is not provided on command line, then its default value depends
+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".
 
@@ -2998,9 +3159,11 @@ rclone mount remote:path /path/to/mountpoint [flags]
       --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-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 128M)
       --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. 'off' is unlimited. (default off)
       --vfs-read-wait duration                 Time to wait for in-sequence read before seeking. (default 20ms)
+      --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 (not supported by all OSes).
       --write-back-cache                       Makes kernel buffer writes before sending them to rclone. Without this, writethrough caching is used.
@@ -3046,7 +3209,7 @@ modification time or MD5SUM.  src will be deleted on successful
 transfer.
 
 **Important**: Since this can cause data loss, test first with the
---dry-run flag.
+`--dry-run` or the `--interactive`/`-i` flag.
 
 **Note**: Use the `-P`/`--progress` flag to view real-time transfer statistics.
 
@@ -3126,11 +3289,32 @@ See the [global flags page](https://rclone.org/flags/) for global options not li
 
 # rclone obscure
 
-Obscure password for use in the rclone.conf
+Obscure password for use in the rclone config file
 
 ## Synopsis
 
-Obscure password for use in the rclone.conf
+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 **not** 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.
+
+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.
+
+This command can also accept a password through STDIN instead of an
+argument by passing a hyphen as an argument. Example:
+
+echo "secretpassword" | rclone obscure -
+
+If there is no data on STDIN to read, rclone obscure will default to
+obfuscating the hyphen itself.
+
+If you want to encrypt the config file then please use config file
+encryption - see [rclone config](https://rclone.org/commands/rclone_config/) for more
+info.
 
 ```
 rclone obscure password [flags]
@@ -3397,30 +3581,49 @@ players might show files that they are not able to play back correctly.
 
 ## Server options
 
-Use --addr to specify which IP address and port the server should
-listen on, eg --addr 1.2.3.4:8000 or --addr :8080 to listen to all
+Use `--addr` to specify which IP address and port the server should
+listen on, eg `--addr 1.2.3.4:8000` or `--addr :8080` to listen to all
 IPs.
 
-Use --name to choose the friendly server name, which is by
+Use `--name` to choose the friendly server name, which is by
 default "rclone (hostname)".
 
-Use --log-trace in conjunction with -vv to enable additional debug
+Use `--log-trace` in conjunction with `-vv` to enable additional debug
 logging of all UPNP traffic.
 
-## Directory Cache
+## VFS - Virtual File System
 
-Using the `--dir-cache-time` flag, you can set how long a
+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.
+
+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.
+
+The VFS layer also implements a directory cache - this caches info
+about files and directories (but not the data) in memory.
+
+## VFS Directory Cache
+
+Using the `--dir-cache-time` flag, you can control how long a
 directory should be considered up to date and not refreshed from the
-backend. Changes made locally in the mount may appear immediately or
-invalidate the cache. However, changes done on the remote will only
-be picked up once the cache expires if the backend configured does not
-support polling for changes. If the backend supports polling, changes
-will be picked up on within the polling interval.
+backend. Changes made through the mount will appear immediately or
+invalidate the cache.
 
-Alternatively, you can send a `SIGHUP` 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:
+    --dir-cache-time duration   Time to cache directory entries for. (default 5m0s)
+    --poll-interval duration    Time to wait between polling for changes.
+
+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.
+
+You can send a `SIGHUP` 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:
 
     kill -SIGHUP $(pidof rclone)
 
@@ -3433,40 +3636,41 @@ Or individual files or directories:
 
     rclone rc vfs/forget file=path/to/file dir=path/to/dir
 
-## File Buffering
+## VFS File Buffering
 
 The `--buffer-size` flag determines the amount of memory,
 that will be used to buffer data in advance.
 
-Each open file descriptor will try to keep the specified amount of
-data in memory at all times. The buffered data is bound to one file
-descriptor and won't be shared between multiple open file descriptors
-of the same file.
+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.
+
+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.
 
-This flag is a upper limit for the used memory per file descriptor.
-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.
 The maximum memory used by rclone for buffering can be up to
 `--buffer-size * open files`.
 
-## File Caching
+## VFS File Caching
 
-These flags control the VFS file caching options.  The VFS layer is
-used by rclone mount to make a cloud storage system work more like a
-normal file system.
+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.
 
-You'll need to enable VFS caching if you want, for example, to read
-and write simultaneously to a file.  See below for more details.
+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.
 
-Note that the VFS cache works in addition to the cache backend and you
-may find that you need one or the other or both.
+Note that the VFS cache is separate from the cache backend and you may
+find that you need one or the other or both.
 
     --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 age of objects in the cache. (default 1h0m0s)
-    --vfs-cache-mode string              Cache mode off|minimal|writes|full (default "off")
+    --vfs-cache-max-size SizeSuffix      Max total size of objects in the cache. (default off)
     --vfs-cache-poll-interval duration   Interval to poll the cache for stale objects. (default 1m0s)
-    --vfs-cache-max-size int             Max total size of objects in the cache. (default off)
+    --vfs-write-back duration            Time to writeback files after last use when using cache. (default 5s)
 
 If run with `-vv` rclone will print the location of the file cache.  The
 files are stored in the user cache file area which is OS dependent but
@@ -3478,9 +3682,10 @@ The higher the cache mode the more compatible rclone becomes at the
 cost of using disk space.
 
 Note that files are written back to the remote only when they are
-closed so if rclone is quit or dies with open files then these won't
-get written back to the remote.  However they will still be in the on
-disk cache.
+closed and if they haven't been accessed for --vfs-write-back
+second. 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.
 
 If using --vfs-cache-max-size note that the cache may exceed this size
 for two reasons.  Firstly because it is only checked every
@@ -3489,7 +3694,7 @@ evicted from the cache.
 
 ### --vfs-cache-mode off
 
-In this mode the cache will read directly from the remote and write
+In this mode (the default) the cache will read directly from the remote and write
 directly to the remote without caching anything on disk.
 
 This will mean some operations are not possible
@@ -3505,7 +3710,7 @@ This will mean some operations are not possible
 ### --vfs-cache-mode minimal
 
 This is very similar to "off" except that files opened for read AND
-write will be buffered to disks.  This means that files opened for
+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.
 
 These operations are not possible
@@ -3523,32 +3728,72 @@ first.
 
 This mode should support all normal file system operations.
 
-If an upload fails it will be retried up to --low-level-retries times.
+If an upload fails it will be retried at exponentially increasing
+intervals up to 1 minute.
 
 ### --vfs-cache-mode full
 
-In this mode all reads and writes are buffered to and from disk.  When
-a file is opened for read it will be downloaded in its entirety first.
+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.
 
-This may be appropriate for your needs, or you may prefer to look at
-the cache backend which does a much more sophisticated job of caching,
-including caching directory hierarchies and chunks of files.
+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 dowloaded.
 
-In this mode, unlike the others, when a file is written to the disk,
-it will be kept on the disk after it is written to the remote.  It
-will be purged on a schedule according to `--vfs-cache-max-age`.
+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.
 
-This mode should support all normal file system operations.
+This mode should support all normal file system operations and is
+otherwise identical to --vfs-cache-mode writes.
 
-If an upload or download fails it will be retried up to
---low-level-retries times.
+When reading a file rclone will read --buffer-size plus
+--vfs-read-ahead bytes ahead.  The --buffer-size is buffered in memory
+whereas the --vfs-read-ahead is buffered on disk.
 
-## Case Sensitivity
+When using this mode it is recommended that --buffer-size is not set
+too big and --vfs-read-ahead is set large if required.
+
+## VFS Performance
+
+These flags may be used to enable/disable features of the VFS for
+performance or other reasons.
+
+In particular S3 and Swift benefit hugely from the --no-modtime flag
+(or use --use-server-modtime for a slightly different effect) as each
+read of the modification time takes a transaction.
+
+    --no-checksum     Don't compare checksums on up/download.
+    --no-modtime      Don't read/write the modification time (can speed things up).
+    --no-seek         Don't allow seeking in files.
+    --read-only       Mount read-only.
+
+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 is advantageous because some cloud providers
+account for reads being all the data requested, not all the data
+delivered.
+
+Rclone will keep doubling the chunk size requested starting at
+--vfs-read-chunk-size with a maximum of --vfs-read-chunk-size-limit
+unless it is set to "off" in which case there will be no limit.
+
+    --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")
+
+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.
+
+    --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)
+
+## VFS Case Sensitivity
 
 Linux file systems are case-sensitive: two files can differ only
 by case, and the exact case must be used when opening a file.
 
-Windows is not like most other operating systems supported by rclone.
 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.
@@ -3559,7 +3804,7 @@ file systems case-sensitive but that is not the default
 
 The "--vfs-case-insensitive" mount flag controls how rclone handles these
 two cases. If its value is "false", rclone passes file names to the mounted
-file system as is. If the flag is "true" (or appears without a value on
+file system as-is. If the flag is "true" (or appears without a value on
 command line), rclone may perform a "fixup" as explained below.
 
 The user may specify a file name to open/delete/rename/etc with a case
@@ -3575,7 +3820,7 @@ Note that case sensitivity of the operating system running rclone (the target)
 may differ from case sensitivity of a file system mounted by rclone (the source).
 The flag controls whether "fixup" is performed to satisfy the target.
 
-If the flag is not provided on command line, then its default value depends
+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".
 
@@ -3607,9 +3852,11 @@ rclone serve dlna remote:path [flags]
       --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-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 128M)
       --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. 'off' is unlimited. (default off)
       --vfs-read-wait duration                 Time to wait for in-sequence read before seeking. (default 20ms)
+      --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)
 ```
 
@@ -3646,20 +3893,39 @@ By default this will serve files without needing a login.
 
 You can set a single username and password with the --user and --pass flags.
 
-## Directory Cache
+## VFS - Virtual File System
 
-Using the `--dir-cache-time` flag, you can set how long a
+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.
+
+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.
+
+The VFS layer also implements a directory cache - this caches info
+about files and directories (but not the data) in memory.
+
+## VFS Directory Cache
+
+Using the `--dir-cache-time` flag, you can control how long a
 directory should be considered up to date and not refreshed from the
-backend. Changes made locally in the mount may appear immediately or
-invalidate the cache. However, changes done on the remote will only
-be picked up once the cache expires if the backend configured does not
-support polling for changes. If the backend supports polling, changes
-will be picked up on within the polling interval.
+backend. Changes made through the mount will appear immediately or
+invalidate the cache.
 
-Alternatively, you can send a `SIGHUP` 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:
+    --dir-cache-time duration   Time to cache directory entries for. (default 5m0s)
+    --poll-interval duration    Time to wait between polling for changes.
+
+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.
+
+You can send a `SIGHUP` 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:
 
     kill -SIGHUP $(pidof rclone)
 
@@ -3672,40 +3938,41 @@ Or individual files or directories:
 
     rclone rc vfs/forget file=path/to/file dir=path/to/dir
 
-## File Buffering
+## VFS File Buffering
 
 The `--buffer-size` flag determines the amount of memory,
 that will be used to buffer data in advance.
 
-Each open file descriptor will try to keep the specified amount of
-data in memory at all times. The buffered data is bound to one file
-descriptor and won't be shared between multiple open file descriptors
-of the same file.
+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.
+
+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.
 
-This flag is a upper limit for the used memory per file descriptor.
-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.
 The maximum memory used by rclone for buffering can be up to
 `--buffer-size * open files`.
 
-## File Caching
+## VFS File Caching
 
-These flags control the VFS file caching options.  The VFS layer is
-used by rclone mount to make a cloud storage system work more like a
-normal file system.
+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.
 
-You'll need to enable VFS caching if you want, for example, to read
-and write simultaneously to a file.  See below for more details.
+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.
 
-Note that the VFS cache works in addition to the cache backend and you
-may find that you need one or the other or both.
+Note that the VFS cache is separate from the cache backend and you may
+find that you need one or the other or both.
 
     --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 age of objects in the cache. (default 1h0m0s)
-    --vfs-cache-mode string              Cache mode off|minimal|writes|full (default "off")
+    --vfs-cache-max-size SizeSuffix      Max total size of objects in the cache. (default off)
     --vfs-cache-poll-interval duration   Interval to poll the cache for stale objects. (default 1m0s)
-    --vfs-cache-max-size int             Max total size of objects in the cache. (default off)
+    --vfs-write-back duration            Time to writeback files after last use when using cache. (default 5s)
 
 If run with `-vv` rclone will print the location of the file cache.  The
 files are stored in the user cache file area which is OS dependent but
@@ -3717,9 +3984,10 @@ The higher the cache mode the more compatible rclone becomes at the
 cost of using disk space.
 
 Note that files are written back to the remote only when they are
-closed so if rclone is quit or dies with open files then these won't
-get written back to the remote.  However they will still be in the on
-disk cache.
+closed and if they haven't been accessed for --vfs-write-back
+second. 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.
 
 If using --vfs-cache-max-size note that the cache may exceed this size
 for two reasons.  Firstly because it is only checked every
@@ -3728,7 +3996,7 @@ evicted from the cache.
 
 ### --vfs-cache-mode off
 
-In this mode the cache will read directly from the remote and write
+In this mode (the default) the cache will read directly from the remote and write
 directly to the remote without caching anything on disk.
 
 This will mean some operations are not possible
@@ -3744,7 +4012,7 @@ This will mean some operations are not possible
 ### --vfs-cache-mode minimal
 
 This is very similar to "off" except that files opened for read AND
-write will be buffered to disks.  This means that files opened for
+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.
 
 These operations are not possible
@@ -3762,32 +4030,72 @@ first.
 
 This mode should support all normal file system operations.
 
-If an upload fails it will be retried up to --low-level-retries times.
+If an upload fails it will be retried at exponentially increasing
+intervals up to 1 minute.
 
 ### --vfs-cache-mode full
 
-In this mode all reads and writes are buffered to and from disk.  When
-a file is opened for read it will be downloaded in its entirety first.
+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.
 
-This may be appropriate for your needs, or you may prefer to look at
-the cache backend which does a much more sophisticated job of caching,
-including caching directory hierarchies and chunks of files.
+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 dowloaded.
 
-In this mode, unlike the others, when a file is written to the disk,
-it will be kept on the disk after it is written to the remote.  It
-will be purged on a schedule according to `--vfs-cache-max-age`.
+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.
 
-This mode should support all normal file system operations.
+This mode should support all normal file system operations and is
+otherwise identical to --vfs-cache-mode writes.
 
-If an upload or download fails it will be retried up to
---low-level-retries times.
+When reading a file rclone will read --buffer-size plus
+--vfs-read-ahead bytes ahead.  The --buffer-size is buffered in memory
+whereas the --vfs-read-ahead is buffered on disk.
 
-## Case Sensitivity
+When using this mode it is recommended that --buffer-size is not set
+too big and --vfs-read-ahead is set large if required.
+
+## VFS Performance
+
+These flags may be used to enable/disable features of the VFS for
+performance or other reasons.
+
+In particular S3 and Swift benefit hugely from the --no-modtime flag
+(or use --use-server-modtime for a slightly different effect) as each
+read of the modification time takes a transaction.
+
+    --no-checksum     Don't compare checksums on up/download.
+    --no-modtime      Don't read/write the modification time (can speed things up).
+    --no-seek         Don't allow seeking in files.
+    --read-only       Mount read-only.
+
+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 is advantageous because some cloud providers
+account for reads being all the data requested, not all the data
+delivered.
+
+Rclone will keep doubling the chunk size requested starting at
+--vfs-read-chunk-size with a maximum of --vfs-read-chunk-size-limit
+unless it is set to "off" in which case there will be no limit.
+
+    --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")
+
+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.
+
+    --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)
+
+## VFS Case Sensitivity
 
 Linux file systems are case-sensitive: two files can differ only
 by case, and the exact case must be used when opening a file.
 
-Windows is not like most other operating systems supported by rclone.
 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.
@@ -3798,7 +4106,7 @@ file systems case-sensitive but that is not the default
 
 The "--vfs-case-insensitive" mount flag controls how rclone handles these
 two cases. If its value is "false", rclone passes file names to the mounted
-file system as is. If the flag is "true" (or appears without a value on
+file system as-is. If the flag is "true" (or appears without a value on
 command line), rclone may perform a "fixup" as explained below.
 
 The user may specify a file name to open/delete/rename/etc with a case
@@ -3814,7 +4122,7 @@ Note that case sensitivity of the operating system running rclone (the target)
 may differ from case sensitivity of a file system mounted by rclone (the source).
 The flag controls whether "fixup" is performed to satisfy the target.
 
-If the flag is not provided on command line, then its default value depends
+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".
 
@@ -3930,9 +4238,11 @@ rclone serve ftp remote:path [flags]
       --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-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 128M)
       --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. 'off' is unlimited. (default off)
       --vfs-read-wait duration                 Time to wait for in-sequence read before seeking. (default 20ms)
+      --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)
 ```
 
@@ -4041,20 +4351,39 @@ of that with the CA certificate.  --key should be the PEM encoded
 private key and --client-ca should be the PEM encoded client
 certificate authority certificate.
 
-## Directory Cache
+## VFS - Virtual File System
 
-Using the `--dir-cache-time` flag, you can set how long a
+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.
+
+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.
+
+The VFS layer also implements a directory cache - this caches info
+about files and directories (but not the data) in memory.
+
+## VFS Directory Cache
+
+Using the `--dir-cache-time` flag, you can control how long a
 directory should be considered up to date and not refreshed from the
-backend. Changes made locally in the mount may appear immediately or
-invalidate the cache. However, changes done on the remote will only
-be picked up once the cache expires if the backend configured does not
-support polling for changes. If the backend supports polling, changes
-will be picked up on within the polling interval.
+backend. Changes made through the mount will appear immediately or
+invalidate the cache.
 
-Alternatively, you can send a `SIGHUP` 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:
+    --dir-cache-time duration   Time to cache directory entries for. (default 5m0s)
+    --poll-interval duration    Time to wait between polling for changes.
+
+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.
+
+You can send a `SIGHUP` 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:
 
     kill -SIGHUP $(pidof rclone)
 
@@ -4067,40 +4396,41 @@ Or individual files or directories:
 
     rclone rc vfs/forget file=path/to/file dir=path/to/dir
 
-## File Buffering
+## VFS File Buffering
 
 The `--buffer-size` flag determines the amount of memory,
 that will be used to buffer data in advance.
 
-Each open file descriptor will try to keep the specified amount of
-data in memory at all times. The buffered data is bound to one file
-descriptor and won't be shared between multiple open file descriptors
-of the same file.
+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.
+
+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.
 
-This flag is a upper limit for the used memory per file descriptor.
-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.
 The maximum memory used by rclone for buffering can be up to
 `--buffer-size * open files`.
 
-## File Caching
+## VFS File Caching
 
-These flags control the VFS file caching options.  The VFS layer is
-used by rclone mount to make a cloud storage system work more like a
-normal file system.
+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.
 
-You'll need to enable VFS caching if you want, for example, to read
-and write simultaneously to a file.  See below for more details.
+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.
 
-Note that the VFS cache works in addition to the cache backend and you
-may find that you need one or the other or both.
+Note that the VFS cache is separate from the cache backend and you may
+find that you need one or the other or both.
 
     --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 age of objects in the cache. (default 1h0m0s)
-    --vfs-cache-mode string              Cache mode off|minimal|writes|full (default "off")
+    --vfs-cache-max-size SizeSuffix      Max total size of objects in the cache. (default off)
     --vfs-cache-poll-interval duration   Interval to poll the cache for stale objects. (default 1m0s)
-    --vfs-cache-max-size int             Max total size of objects in the cache. (default off)
+    --vfs-write-back duration            Time to writeback files after last use when using cache. (default 5s)
 
 If run with `-vv` rclone will print the location of the file cache.  The
 files are stored in the user cache file area which is OS dependent but
@@ -4112,9 +4442,10 @@ The higher the cache mode the more compatible rclone becomes at the
 cost of using disk space.
 
 Note that files are written back to the remote only when they are
-closed so if rclone is quit or dies with open files then these won't
-get written back to the remote.  However they will still be in the on
-disk cache.
+closed and if they haven't been accessed for --vfs-write-back
+second. 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.
 
 If using --vfs-cache-max-size note that the cache may exceed this size
 for two reasons.  Firstly because it is only checked every
@@ -4123,7 +4454,7 @@ evicted from the cache.
 
 ### --vfs-cache-mode off
 
-In this mode the cache will read directly from the remote and write
+In this mode (the default) the cache will read directly from the remote and write
 directly to the remote without caching anything on disk.
 
 This will mean some operations are not possible
@@ -4139,7 +4470,7 @@ This will mean some operations are not possible
 ### --vfs-cache-mode minimal
 
 This is very similar to "off" except that files opened for read AND
-write will be buffered to disks.  This means that files opened for
+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.
 
 These operations are not possible
@@ -4157,32 +4488,72 @@ first.
 
 This mode should support all normal file system operations.
 
-If an upload fails it will be retried up to --low-level-retries times.
+If an upload fails it will be retried at exponentially increasing
+intervals up to 1 minute.
 
 ### --vfs-cache-mode full
 
-In this mode all reads and writes are buffered to and from disk.  When
-a file is opened for read it will be downloaded in its entirety first.
+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.
 
-This may be appropriate for your needs, or you may prefer to look at
-the cache backend which does a much more sophisticated job of caching,
-including caching directory hierarchies and chunks of files.
+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 dowloaded.
 
-In this mode, unlike the others, when a file is written to the disk,
-it will be kept on the disk after it is written to the remote.  It
-will be purged on a schedule according to `--vfs-cache-max-age`.
+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.
 
-This mode should support all normal file system operations.
+This mode should support all normal file system operations and is
+otherwise identical to --vfs-cache-mode writes.
 
-If an upload or download fails it will be retried up to
---low-level-retries times.
+When reading a file rclone will read --buffer-size plus
+--vfs-read-ahead bytes ahead.  The --buffer-size is buffered in memory
+whereas the --vfs-read-ahead is buffered on disk.
 
-## Case Sensitivity
+When using this mode it is recommended that --buffer-size is not set
+too big and --vfs-read-ahead is set large if required.
+
+## VFS Performance
+
+These flags may be used to enable/disable features of the VFS for
+performance or other reasons.
+
+In particular S3 and Swift benefit hugely from the --no-modtime flag
+(or use --use-server-modtime for a slightly different effect) as each
+read of the modification time takes a transaction.
+
+    --no-checksum     Don't compare checksums on up/download.
+    --no-modtime      Don't read/write the modification time (can speed things up).
+    --no-seek         Don't allow seeking in files.
+    --read-only       Mount read-only.
+
+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 is advantageous because some cloud providers
+account for reads being all the data requested, not all the data
+delivered.
+
+Rclone will keep doubling the chunk size requested starting at
+--vfs-read-chunk-size with a maximum of --vfs-read-chunk-size-limit
+unless it is set to "off" in which case there will be no limit.
+
+    --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")
+
+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.
+
+    --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)
+
+## VFS Case Sensitivity
 
 Linux file systems are case-sensitive: two files can differ only
 by case, and the exact case must be used when opening a file.
 
-Windows is not like most other operating systems supported by rclone.
 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.
@@ -4193,7 +4564,7 @@ file systems case-sensitive but that is not the default
 
 The "--vfs-case-insensitive" mount flag controls how rclone handles these
 two cases. If its value is "false", rclone passes file names to the mounted
-file system as is. If the flag is "true" (or appears without a value on
+file system as-is. If the flag is "true" (or appears without a value on
 command line), rclone may perform a "fixup" as explained below.
 
 The user may specify a file name to open/delete/rename/etc with a case
@@ -4209,7 +4580,7 @@ Note that case sensitivity of the operating system running rclone (the target)
 may differ from case sensitivity of a file system mounted by rclone (the source).
 The flag controls whether "fixup" is performed to satisfy the target.
 
-If the flag is not provided on command line, then its default value depends
+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".
 
@@ -4251,9 +4622,11 @@ rclone serve http remote:path [flags]
       --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-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 128M)
       --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. 'off' is unlimited. (default off)
       --vfs-read-wait duration                 Time to wait for in-sequence read before seeking. (default 20ms)
+      --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)
 ```
 
@@ -4499,20 +4872,39 @@ Note that the default of "--vfs-cache-mode off" is fine for the rclone
 sftp backend, but it may not be with other SFTP clients.
 
 
-## Directory Cache
+## VFS - Virtual File System
 
-Using the `--dir-cache-time` flag, you can set how long a
+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.
+
+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.
+
+The VFS layer also implements a directory cache - this caches info
+about files and directories (but not the data) in memory.
+
+## VFS Directory Cache
+
+Using the `--dir-cache-time` flag, you can control how long a
 directory should be considered up to date and not refreshed from the
-backend. Changes made locally in the mount may appear immediately or
-invalidate the cache. However, changes done on the remote will only
-be picked up once the cache expires if the backend configured does not
-support polling for changes. If the backend supports polling, changes
-will be picked up on within the polling interval.
+backend. Changes made through the mount will appear immediately or
+invalidate the cache.
 
-Alternatively, you can send a `SIGHUP` 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:
+    --dir-cache-time duration   Time to cache directory entries for. (default 5m0s)
+    --poll-interval duration    Time to wait between polling for changes.
+
+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.
+
+You can send a `SIGHUP` 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:
 
     kill -SIGHUP $(pidof rclone)
 
@@ -4525,40 +4917,41 @@ Or individual files or directories:
 
     rclone rc vfs/forget file=path/to/file dir=path/to/dir
 
-## File Buffering
+## VFS File Buffering
 
 The `--buffer-size` flag determines the amount of memory,
 that will be used to buffer data in advance.
 
-Each open file descriptor will try to keep the specified amount of
-data in memory at all times. The buffered data is bound to one file
-descriptor and won't be shared between multiple open file descriptors
-of the same file.
+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.
+
+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.
 
-This flag is a upper limit for the used memory per file descriptor.
-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.
 The maximum memory used by rclone for buffering can be up to
 `--buffer-size * open files`.
 
-## File Caching
+## VFS File Caching
 
-These flags control the VFS file caching options.  The VFS layer is
-used by rclone mount to make a cloud storage system work more like a
-normal file system.
+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.
 
-You'll need to enable VFS caching if you want, for example, to read
-and write simultaneously to a file.  See below for more details.
+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.
 
-Note that the VFS cache works in addition to the cache backend and you
-may find that you need one or the other or both.
+Note that the VFS cache is separate from the cache backend and you may
+find that you need one or the other or both.
 
     --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 age of objects in the cache. (default 1h0m0s)
-    --vfs-cache-mode string              Cache mode off|minimal|writes|full (default "off")
+    --vfs-cache-max-size SizeSuffix      Max total size of objects in the cache. (default off)
     --vfs-cache-poll-interval duration   Interval to poll the cache for stale objects. (default 1m0s)
-    --vfs-cache-max-size int             Max total size of objects in the cache. (default off)
+    --vfs-write-back duration            Time to writeback files after last use when using cache. (default 5s)
 
 If run with `-vv` rclone will print the location of the file cache.  The
 files are stored in the user cache file area which is OS dependent but
@@ -4570,9 +4963,10 @@ The higher the cache mode the more compatible rclone becomes at the
 cost of using disk space.
 
 Note that files are written back to the remote only when they are
-closed so if rclone is quit or dies with open files then these won't
-get written back to the remote.  However they will still be in the on
-disk cache.
+closed and if they haven't been accessed for --vfs-write-back
+second. 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.
 
 If using --vfs-cache-max-size note that the cache may exceed this size
 for two reasons.  Firstly because it is only checked every
@@ -4581,7 +4975,7 @@ evicted from the cache.
 
 ### --vfs-cache-mode off
 
-In this mode the cache will read directly from the remote and write
+In this mode (the default) the cache will read directly from the remote and write
 directly to the remote without caching anything on disk.
 
 This will mean some operations are not possible
@@ -4597,7 +4991,7 @@ This will mean some operations are not possible
 ### --vfs-cache-mode minimal
 
 This is very similar to "off" except that files opened for read AND
-write will be buffered to disks.  This means that files opened for
+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.
 
 These operations are not possible
@@ -4615,32 +5009,72 @@ first.
 
 This mode should support all normal file system operations.
 
-If an upload fails it will be retried up to --low-level-retries times.
+If an upload fails it will be retried at exponentially increasing
+intervals up to 1 minute.
 
 ### --vfs-cache-mode full
 
-In this mode all reads and writes are buffered to and from disk.  When
-a file is opened for read it will be downloaded in its entirety first.
+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.
 
-This may be appropriate for your needs, or you may prefer to look at
-the cache backend which does a much more sophisticated job of caching,
-including caching directory hierarchies and chunks of files.
+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 dowloaded.
 
-In this mode, unlike the others, when a file is written to the disk,
-it will be kept on the disk after it is written to the remote.  It
-will be purged on a schedule according to `--vfs-cache-max-age`.
+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.
 
-This mode should support all normal file system operations.
+This mode should support all normal file system operations and is
+otherwise identical to --vfs-cache-mode writes.
 
-If an upload or download fails it will be retried up to
---low-level-retries times.
+When reading a file rclone will read --buffer-size plus
+--vfs-read-ahead bytes ahead.  The --buffer-size is buffered in memory
+whereas the --vfs-read-ahead is buffered on disk.
 
-## Case Sensitivity
+When using this mode it is recommended that --buffer-size is not set
+too big and --vfs-read-ahead is set large if required.
+
+## VFS Performance
+
+These flags may be used to enable/disable features of the VFS for
+performance or other reasons.
+
+In particular S3 and Swift benefit hugely from the --no-modtime flag
+(or use --use-server-modtime for a slightly different effect) as each
+read of the modification time takes a transaction.
+
+    --no-checksum     Don't compare checksums on up/download.
+    --no-modtime      Don't read/write the modification time (can speed things up).
+    --no-seek         Don't allow seeking in files.
+    --read-only       Mount read-only.
+
+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 is advantageous because some cloud providers
+account for reads being all the data requested, not all the data
+delivered.
+
+Rclone will keep doubling the chunk size requested starting at
+--vfs-read-chunk-size with a maximum of --vfs-read-chunk-size-limit
+unless it is set to "off" in which case there will be no limit.
+
+    --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")
+
+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.
+
+    --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)
+
+## VFS Case Sensitivity
 
 Linux file systems are case-sensitive: two files can differ only
 by case, and the exact case must be used when opening a file.
 
-Windows is not like most other operating systems supported by rclone.
 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.
@@ -4651,7 +5085,7 @@ file systems case-sensitive but that is not the default
 
 The "--vfs-case-insensitive" mount flag controls how rclone handles these
 two cases. If its value is "false", rclone passes file names to the mounted
-file system as is. If the flag is "true" (or appears without a value on
+file system as-is. If the flag is "true" (or appears without a value on
 command line), rclone may perform a "fixup" as explained below.
 
 The user may specify a file name to open/delete/rename/etc with a case
@@ -4667,7 +5101,7 @@ Note that case sensitivity of the operating system running rclone (the target)
 may differ from case sensitivity of a file system mounted by rclone (the source).
 The flag controls whether "fixup" is performed to satisfy the target.
 
-If the flag is not provided on command line, then its default value depends
+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".
 
@@ -4784,9 +5218,11 @@ rclone serve sftp remote:path [flags]
       --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-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 128M)
       --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. 'off' is unlimited. (default off)
       --vfs-read-wait duration                 Time to wait for in-sequence read before seeking. (default 20ms)
+      --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)
 ```
 
@@ -4903,20 +5339,39 @@ of that with the CA certificate.  --key should be the PEM encoded
 private key and --client-ca should be the PEM encoded client
 certificate authority certificate.
 
-## Directory Cache
+## VFS - Virtual File System
 
-Using the `--dir-cache-time` flag, you can set how long a
+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.
+
+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.
+
+The VFS layer also implements a directory cache - this caches info
+about files and directories (but not the data) in memory.
+
+## VFS Directory Cache
+
+Using the `--dir-cache-time` flag, you can control how long a
 directory should be considered up to date and not refreshed from the
-backend. Changes made locally in the mount may appear immediately or
-invalidate the cache. However, changes done on the remote will only
-be picked up once the cache expires if the backend configured does not
-support polling for changes. If the backend supports polling, changes
-will be picked up on within the polling interval.
+backend. Changes made through the mount will appear immediately or
+invalidate the cache.
 
-Alternatively, you can send a `SIGHUP` 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:
+    --dir-cache-time duration   Time to cache directory entries for. (default 5m0s)
+    --poll-interval duration    Time to wait between polling for changes.
+
+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.
+
+You can send a `SIGHUP` 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:
 
     kill -SIGHUP $(pidof rclone)
 
@@ -4929,40 +5384,41 @@ Or individual files or directories:
 
     rclone rc vfs/forget file=path/to/file dir=path/to/dir
 
-## File Buffering
+## VFS File Buffering
 
 The `--buffer-size` flag determines the amount of memory,
 that will be used to buffer data in advance.
 
-Each open file descriptor will try to keep the specified amount of
-data in memory at all times. The buffered data is bound to one file
-descriptor and won't be shared between multiple open file descriptors
-of the same file.
+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.
+
+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.
 
-This flag is a upper limit for the used memory per file descriptor.
-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.
 The maximum memory used by rclone for buffering can be up to
 `--buffer-size * open files`.
 
-## File Caching
+## VFS File Caching
 
-These flags control the VFS file caching options.  The VFS layer is
-used by rclone mount to make a cloud storage system work more like a
-normal file system.
+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.
 
-You'll need to enable VFS caching if you want, for example, to read
-and write simultaneously to a file.  See below for more details.
+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.
 
-Note that the VFS cache works in addition to the cache backend and you
-may find that you need one or the other or both.
+Note that the VFS cache is separate from the cache backend and you may
+find that you need one or the other or both.
 
     --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 age of objects in the cache. (default 1h0m0s)
-    --vfs-cache-mode string              Cache mode off|minimal|writes|full (default "off")
+    --vfs-cache-max-size SizeSuffix      Max total size of objects in the cache. (default off)
     --vfs-cache-poll-interval duration   Interval to poll the cache for stale objects. (default 1m0s)
-    --vfs-cache-max-size int             Max total size of objects in the cache. (default off)
+    --vfs-write-back duration            Time to writeback files after last use when using cache. (default 5s)
 
 If run with `-vv` rclone will print the location of the file cache.  The
 files are stored in the user cache file area which is OS dependent but
@@ -4974,9 +5430,10 @@ The higher the cache mode the more compatible rclone becomes at the
 cost of using disk space.
 
 Note that files are written back to the remote only when they are
-closed so if rclone is quit or dies with open files then these won't
-get written back to the remote.  However they will still be in the on
-disk cache.
+closed and if they haven't been accessed for --vfs-write-back
+second. 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.
 
 If using --vfs-cache-max-size note that the cache may exceed this size
 for two reasons.  Firstly because it is only checked every
@@ -4985,7 +5442,7 @@ evicted from the cache.
 
 ### --vfs-cache-mode off
 
-In this mode the cache will read directly from the remote and write
+In this mode (the default) the cache will read directly from the remote and write
 directly to the remote without caching anything on disk.
 
 This will mean some operations are not possible
@@ -5001,7 +5458,7 @@ This will mean some operations are not possible
 ### --vfs-cache-mode minimal
 
 This is very similar to "off" except that files opened for read AND
-write will be buffered to disks.  This means that files opened for
+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.
 
 These operations are not possible
@@ -5019,32 +5476,72 @@ first.
 
 This mode should support all normal file system operations.
 
-If an upload fails it will be retried up to --low-level-retries times.
+If an upload fails it will be retried at exponentially increasing
+intervals up to 1 minute.
 
 ### --vfs-cache-mode full
 
-In this mode all reads and writes are buffered to and from disk.  When
-a file is opened for read it will be downloaded in its entirety first.
+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.
 
-This may be appropriate for your needs, or you may prefer to look at
-the cache backend which does a much more sophisticated job of caching,
-including caching directory hierarchies and chunks of files.
+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 dowloaded.
 
-In this mode, unlike the others, when a file is written to the disk,
-it will be kept on the disk after it is written to the remote.  It
-will be purged on a schedule according to `--vfs-cache-max-age`.
+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.
 
-This mode should support all normal file system operations.
+This mode should support all normal file system operations and is
+otherwise identical to --vfs-cache-mode writes.
 
-If an upload or download fails it will be retried up to
---low-level-retries times.
+When reading a file rclone will read --buffer-size plus
+--vfs-read-ahead bytes ahead.  The --buffer-size is buffered in memory
+whereas the --vfs-read-ahead is buffered on disk.
 
-## Case Sensitivity
+When using this mode it is recommended that --buffer-size is not set
+too big and --vfs-read-ahead is set large if required.
+
+## VFS Performance
+
+These flags may be used to enable/disable features of the VFS for
+performance or other reasons.
+
+In particular S3 and Swift benefit hugely from the --no-modtime flag
+(or use --use-server-modtime for a slightly different effect) as each
+read of the modification time takes a transaction.
+
+    --no-checksum     Don't compare checksums on up/download.
+    --no-modtime      Don't read/write the modification time (can speed things up).
+    --no-seek         Don't allow seeking in files.
+    --read-only       Mount read-only.
+
+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 is advantageous because some cloud providers
+account for reads being all the data requested, not all the data
+delivered.
+
+Rclone will keep doubling the chunk size requested starting at
+--vfs-read-chunk-size with a maximum of --vfs-read-chunk-size-limit
+unless it is set to "off" in which case there will be no limit.
+
+    --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")
+
+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.
+
+    --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)
+
+## VFS Case Sensitivity
 
 Linux file systems are case-sensitive: two files can differ only
 by case, and the exact case must be used when opening a file.
 
-Windows is not like most other operating systems supported by rclone.
 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.
@@ -5055,7 +5552,7 @@ file systems case-sensitive but that is not the default
 
 The "--vfs-case-insensitive" mount flag controls how rclone handles these
 two cases. If its value is "false", rclone passes file names to the mounted
-file system as is. If the flag is "true" (or appears without a value on
+file system as-is. If the flag is "true" (or appears without a value on
 command line), rclone may perform a "fixup" as explained below.
 
 The user may specify a file name to open/delete/rename/etc with a case
@@ -5071,7 +5568,7 @@ Note that case sensitivity of the operating system running rclone (the target)
 may differ from case sensitivity of a file system mounted by rclone (the source).
 The flag controls whether "fixup" is performed to satisfy the target.
 
-If the flag is not provided on command line, then its default value depends
+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".
 
@@ -5197,9 +5694,11 @@ rclone serve webdav remote:path [flags]
       --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-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 128M)
       --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. 'off' is unlimited. (default off)
       --vfs-read-wait duration                 Time to wait for in-sequence read before seeking. (default 20ms)
+      --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)
 ```
 
@@ -5273,6 +5772,7 @@ time instead of the current time. Times may be specified as one of:
 
 - 'YYMMDD' - eg. 17.10.30
 - 'YYYY-MM-DDTHH:MM:SS' - eg. 2006-01-02T15:04:05
+- 'YYYY-MM-DDTHH:MM:SS.SSS' - eg. 2006-01-02T15:04:05.123456789
 
 Note that --timestamp is in UTC if you want local time then add the
 --localtime flag.
@@ -5344,7 +5844,7 @@ rclone tree remote:path [flags]
       --human           Print the size in a more human readable way.
       --level int       Descend only level directories deep.
   -D, --modtime         Print the date of last modification.
-  -i, --noindent        Don't print indentation lines.
+      --noindent        Don'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.
@@ -5448,6 +5948,11 @@ To copy files and directories in `https://example.com/path/to/dir` to `/tmp/dir`
 To copy files and directories from `example.com` in the relative
 directory `path/to/dir` to `/tmp/dir` using sftp.
 
+### Valid remote names
+
+ - Remote names may only contain 0-9, A-Z ,a-z ,_ , - and space.
+ - Remote names may not start with -.
+
 Quoting and the shell
 ---------------------
 
@@ -5494,11 +5999,11 @@ file or directory like this then use the full path starting with a
 
 So to sync a directory called `sync:me` to a remote called `remote:` use
 
-    rclone sync ./sync:me remote:path
+    rclone sync -i ./sync:me remote:path
 
 or
 
-    rclone sync /full/path/to/sync:me remote:path
+    rclone sync -i /full/path/to/sync:me remote:path
 
 Server Side Copy
 ----------------
@@ -5531,8 +6036,8 @@ same.
 
 This can be used when scripting to make aged backups efficiently, eg
 
-    rclone sync remote:current-backup remote:previous-backup
-    rclone sync /path/to/files remote:current-backup
+    rclone sync -i remote:current-backup remote:previous-backup
+    rclone sync -i /path/to/files remote:current-backup
 
 Options
 -------
@@ -5574,7 +6079,7 @@ directory must not overlap the destination directory.
 
 For example
 
-    rclone sync /path/to/local remote:current --backup-dir remote:old
+    rclone sync -i /path/to/local remote:current --backup-dir remote:old
 
 will sync `/path/to/local` to `remote:current`, but for any files
 which would have been updated or deleted will be stored in
@@ -5662,6 +6167,20 @@ change the bwlimit dynamically:
 
     rclone rc core/bwlimit rate=1M
 
+### --bwlimit-file=BANDWIDTH_SPEC ###
+
+This option controls per file bandwidth limit. For the options see the
+`--bwlimit` flag.
+
+For example use this to allow no transfers to be faster than 1MByte/s
+
+    --bwlimit-file 1M
+
+This can be used in conjunction with `--bwlimit`.
+
+Note that if a schedule is provided the file will use the schedule in
+effect at the start of the transfer.
+
 ### --buffer-size=SIZE ###
 
 Use this sized buffer to speed up file transfers.  Each `--transfer`
@@ -5849,7 +6368,7 @@ Add an HTTP header for all download transactions. The flag can be repeated to
 add multiple headers.
 
 ```
-rclone sync s3:test/src ~/dst --header-download "X-Amz-Meta-Test: Foo" --header-download "X-Amz-Meta-Test2: Bar"
+rclone sync -i s3:test/src ~/dst --header-download "X-Amz-Meta-Test: Foo" --header-download "X-Amz-Meta-Test2: Bar"
 ```
 
 See the GitHub issue [here](https://github.com/rclone/rclone/issues/59) for
@@ -5861,7 +6380,7 @@ Add an HTTP header for all upload transactions. The flag can be repeated to add
 multiple headers.
 
 ```
-rclone sync ~/src s3:test/dst --header-upload "Content-Disposition: attachment; filename='cool.html'" --header-upload "X-Amz-Meta-Test: FooBar"
+rclone sync -i ~/src s3:test/dst --header-upload "Content-Disposition: attachment; filename='cool.html'" --header-upload "X-Amz-Meta-Test: FooBar"
 ```
 
 See the GitHub issue [here](https://github.com/rclone/rclone/issues/59) for
@@ -5934,7 +6453,45 @@ 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.
 
-## --leave-root ###
+### -i / --interactive {#interactive}
+
+This flag can be used to tell rclone that you wish a manual
+confirmation before destructive operations.
+
+It is **recommended** that you use this flag while learning rclone
+especially with `rclone sync`.
+
+For example
+
+```
+$ rclone delete -i /tmp/dir
+rclone: delete "important-file.txt"?
+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> n
+```
+
+The options mean
+
+- `y`: **Yes**, this operation should go ahead. You can also press Return
+  for this to happen. You'll be asked every time unless you choose `s`
+  or `!`.
+- `n`: **No**, do not do this operation. You'll be asked every time unless
+  you choose `s` or `!`.
+- `s`: **Skip** 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.
+- `!`: **Do all** 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.
+- `q`: **Quit** rclone now, just in case!
+
+### --leave-root ####
 
 During rmdirs it will not remove root directory, even if it's empty.
 
@@ -6298,6 +6855,41 @@ is fixed all non-ASCII characters will be replaced with `.` when
 
 This flag will limit rclone's output to error messages only.
 
+### --refresh-times ###
+
+The `--refresh-times` flag can be used to update modification times of
+existing files when they are out of sync on backends which don't
+support hashes.
+
+This is useful if you uploaded files with the incorrect timestamps and
+you now wish to correct them.
+
+This flag is **only** useful for destinations which don't support
+hashes (eg `crypt`).
+
+This can be used any of the sync commands `sync`, `copy` or `move`.
+
+To use this flag you will need to be doing a modification time sync
+(so not using `--size-only` or `--checksum`). The flag will have no
+effect when using `--size-only` or `--checksum`.
+
+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 (eg
+on a `crypt` backend) then rclone will update the timestamp.
+
+Note that some remotes can't set the modification time without
+re-uploading the file so this flag is less useful on them.
+
+Normally if you are doing a modification time sync rclone will update
+modification times without `--refresh-times` provided that the remote
+supports checksums **and** 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.
+
 ### --retries int ###
 
 Retry the entire sync if it fails this many times it fails (default 3).
@@ -6404,7 +6996,7 @@ or with `--backup-dir`. See `--backup-dir` for more info.
 
 For example
 
-    rclone sync /path/to/local/file remote:current --suffix .bak
+    rclone sync -i /path/to/local/file remote:current --suffix .bak
 
 will sync `/path/to/local` to `remote:current`, but for any files
 which would have been updated or deleted have .bak added.
@@ -6481,8 +7073,10 @@ will be considered.
 
 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. Note: Encrypted destinations are not supported
-by `--track-renames`.
+to the console.
+
+Encrypted destinations are not currently supported by `--track-renames`
+if `--track-renames-strategy` includes `hash`.
 
 Note that `--track-renames` is incompatible with `--no-traverse` and
 that it uses extra memory to keep track of all the rename candidates.
@@ -6491,13 +7085,27 @@ Note also that `--track-renames` is incompatible with
 `--delete-before` and will select `--delete-after` instead of
 `--delete-during`.
 
-### --track-renames-strategy (hash,modtime) ###
+### --track-renames-strategy (hash,modtime,leaf,size) ###
 
-This option changes the matching criteria for `--track-renames` to match
-by any combination of modtime, hash, size. Matching by size is always enabled
-no matter what option is selected here. This also means
-that it enables `--track-renames` support for encrypted destinations.
-If nothing is specified, the default option is matching by hashes.
+This option changes the matching criteria for `--track-renames`.
+
+The matching is controlled by a comma separated selection of these tokens:
+
+- `modtime` - the modification time of the file - not supported on all backends
+- `hash` - the hash of the file contents - not supported on all backends
+- `leaf` - the name of the file not including its directory name
+- `size` - the size of the file (this is always enabled)
+
+So using `--track-renames-strategy modtime,leaf` would match files
+based on modification time, the leaf of the file name and the size
+only.
+
+Using `--track-renames-strategy modtime` or `leaf` can enable
+`--track-renames` support for encrypted destinations.
+
+If nothing is specified, the default option is matching by `hash`es.
+
+Note that the `hash` strategy is not supported with encrypted destinations.
 
 ### --delete-(before,during,after) ###
 
@@ -7016,12 +7624,34 @@ mys3:
 Note that if you want to create a remote using environment variables
 you must create the `..._TYPE` variable as above.
 
+### Precedence
+
+The various different methods of backend configuration are read in
+this order and the first one with a value is used.
+
+- Flag values as supplied on the command line, eg `--drive-use-trash`.
+- Remote specific environment vars, eg `RCLONE_CONFIG_MYREMOTE_USE_TRASH` (see above).
+- Backend specific environment vars, eg `RCLONE_DRIVE_USE_TRASH`.
+- Config file, eg `use_trash = false`.
+- Default values, eg `true` - these can't be changed.
+
+So if both `--drive-use-trash` is supplied on the config line and an
+environment variable `RCLONE_DRIVE_USE_TRASH` is set, the command line
+flag will take preference.
+
+For non backend configuration the order is as follows:
+
+- Flag values as supplied on the command line, eg `--stats 5s`.
+- Environment vars, eg `RCLONE_STATS=5s`.
+- Default values, eg `1m` - these can't be changed.
+
 ### Other environment variables ###
 
-  * `RCLONE_CONFIG_PASS` set to contain your config file password (see [Configuration Encryption](#configuration-encryption) section)
-  * `HTTP_PROXY`, `HTTPS_PROXY` and `NO_PROXY` (or the lowercase versions thereof).
-    * `HTTPS_PROXY` takes precedence over `HTTP_PROXY` for https requests.
-    * The environment values may be either a complete URL or a "host[:port]" for, in which case the "http" scheme is assumed.
+- `RCLONE_CONFIG_PASS` set to contain your config file password (see [Configuration Encryption](#configuration-encryption) section)
+- `HTTP_PROXY`, `HTTPS_PROXY` and `NO_PROXY` (or the lowercase versions thereof).
+    - `HTTPS_PROXY` takes precedence over `HTTP_PROXY` for https requests.
+    - The environment values may be either a complete URL or a "host[:port]" for, in which case the "http" scheme is assumed.
+- `RCLONE_CONFIG_DIR` - rclone **sets** this variable for use in config files and sub processes to point to the directory holding the config file.
 
 # Configuring rclone on a remote / headless machine #
 
@@ -7562,7 +8192,7 @@ from the sync on the destination.
 
 If for example you did a sync from `A` to `B` without the `--min-size 50k` flag
 
-    rclone sync A: B:
+    rclone sync -i A: B:
 
 Then you repeated it like this with the `--delete-excluded`
 
@@ -7620,7 +8250,7 @@ Imagine, you have the following directory structure:
 
 You can exclude `dir3` from sync by running the following command:
 
-    rclone sync --exclude-if-present .ignore dir1 remote:backup
+    rclone sync -i --exclude-if-present .ignore dir1 remote:backup
 
 Currently only one filename is supported, i.e. `--exclude-if-present`
 should not be used multiple times.
@@ -7891,6 +8521,8 @@ $ rclone rc rc/noop param1=one param2=two
 Run `rclone rc` on its own to see the help for the installed remote
 control commands.
 
+## JSON input
+
 `rclone rc` also supports a `--json` flag which can be used to send
 more complicated input parameters.
 
@@ -7910,6 +8542,22 @@ $ rclone rc --json '{ "p1": [1,"2",null,4], "p2": { "a":1, "b":2 } }' rc/noop
 }
 ```
 
+If the parameter being passed is an object then it can be passed as a
+JSON string rather than using the `--json` flag which simplifies the
+command line.
+
+```
+rclone rc operations/list fs=/tmp remote=test opt='{"showHash": true}'
+```
+
+Rather than
+
+```
+rclone rc operations/list --json '{"fs": "/tmp", "remote": "test", "opt": {"showHash": true}}'
+```
+
+
+
 ## Special parameters
 
 The rc interface supports some special parameters which apply to
@@ -8212,6 +8860,41 @@ except only one bandwidth may be specified.
 In either case "rate" is returned as a human readable string, and
 "bytesPerSecond" is returned as a number.
 
+### core/command: Run a rclone terminal command over rc. {#core-command}
+
+This takes the following parameters
+
+- command - a string with the command name
+- arg - a list of arguments for the backend command
+- opt - a map of string to string of options
+
+Returns
+
+- result - result from the backend command
+- error	 - set if rclone exits with an error code
+- returnType - one of ("COMBINED_OUTPUT", "STREAM", "STREAM_ONLY_STDOUT". "STREAM_ONLY_STDERR")
+
+For example
+
+    rclone rc core/command command=ls -a mydrive:/ -o max-depth=1
+	rclone rc core/command -a ls -a mydrive:/ -o max-depth=1
+
+Returns
+
+```
+{
+	"error": false,
+	"result": "<Raw command line output>"
+}
+
+OR 
+{
+	"error": true,
+	"result": "<Raw command line output>"
+}
+
+**Authentication is required for this call.**
+
 ### core/gc: Runs a garbage collection. {#core-gc}
 
 This tells the go runtime to do a garbage collection run.  It isn't
@@ -8290,6 +8973,7 @@ Returns the following values:
 	"transfers": number of transferred files,
 	"deletes" : number of deleted files,
 	"renames" : number of renamed files,
+	"transferTime" : total time spent on running jobs,
 	"elapsedTime": time in seconds since the start of the process,
 	"lastError": last occurred error,
 	"transferring": an array of currently active file transfers:
@@ -8299,8 +8983,8 @@ Returns the following values:
 				"eta": estimated time in seconds until file transfer completion
 				"name": name of the file,
 				"percentage": progress of the file transfer in percent,
-				"speed": speed in bytes/sec,
-				"speedAvg": speed in bytes/sec as an exponentially weighted moving average,
+				"speed": average speed over the whole transfer in bytes/sec,
+				"speedAvg": current speed in bytes/sec as an exponentially weighted moving average,
 				"size": size of the file in bytes
 			}
 		],
@@ -8365,10 +9049,10 @@ Returns the following values:
 
 This shows the current version of go and the go runtime
 
-- version - rclone version, eg "v1.44"
-- decomposed - version number as [major, minor, patch, subpatch]
-    - note patch and subpatch will be 999 for a git compiled version
+- version - rclone version, eg "v1.53.0"
+- decomposed - version number as [major, minor, patch]
 - isGit - boolean - true if this was compiled from the git version
+- isBeta - boolean - true if this is a beta version
 - os - OS in use as according to Go
 - arch - cpu architecture in use according to Go
 - goVersion - version of Go runtime in use
@@ -8444,6 +9128,20 @@ Parameters
 
 - jobid - id of the job (integer)
 
+### mount/listmounts: Show current mount points {#mount-listmounts}
+
+This shows currently mounted points, which can be used for performing an unmount
+
+This takes no parameters and returns
+
+- mountPoints: list of current mount points
+
+Eg
+
+    rclone rc mount/listmounts
+
+**Authentication is required for this call.**
+
 ### mount/mount: Create a new mount point {#mount-mount}
 
 rclone allows Linux, FreeBSD, macOS and Windows to mount any of
@@ -8456,11 +9154,19 @@ This takes the following parameters
 - fs - a remote path to be mounted (required)
 - mountPoint: valid path on the local machine (required)
 - mountType: One of the values (mount, cmount, mount2) specifies the mount implementation to use
+- mountOpt: a JSON object with Mount options in.
+- vfsOpt: a JSON object with VFS options in.
 
 Eg
 
     rclone rc mount/mount fs=mydrive: mountPoint=/home/<user>/mountPoint
     rclone rc mount/mount fs=mydrive: mountPoint=/home/<user>/mountPoint mountType=mount
+    rclone rc mount/mount fs=TestDrive: mountPoint=/mnt/tmp vfsOpt='{"CacheMode": 2}' mountOpt='{"AllowOther": true}'
+
+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.
+
+    rclone rc options/get
 
 **Authentication is required for this call.**
 
@@ -8481,7 +9187,7 @@ Eg
 
 **Authentication is required for this call.**
 
-### mount/unmount: Unmount all active mounts {#mount-unmount}
+### mount/unmount: Unmount selected active mount {#mount-unmount}
 
 rclone allows Linux, FreeBSD, macOS and Windows to
 mount any of Rclone's cloud storage systems as a file system with
@@ -8497,6 +9203,18 @@ Eg
 
 **Authentication is required for this call.**
 
+### mount/unmountall: Show current mount points {#mount-unmountall}
+
+This shows currently mounted points, which can be used for performing an unmount
+
+This takes no parameters and returns error if unmount does not succeed.
+
+Eg
+
+    rclone rc mount/unmountall
+
+**Authentication is required for this call.**
+
 ### operations/about: Return the space used on the remote {#operations-about}
 
 This takes the following parameters
@@ -8670,6 +9388,8 @@ This takes the following parameters
 
 - fs - a remote name string eg "drive:"
 - remote - a path within that remote eg "dir"
+- unlink - boolean - if set removes the link rather than adding it (optional)
+- expire - string - the expiry time of the link eg "1d" (optional)
 
 Returns
 
@@ -8728,6 +9448,17 @@ See the [size command](https://rclone.org/commands/rclone_size/) command for mor
 
 **Authentication is required for this call.**
 
+### operations/uploadfile: Upload file using multiform/form-data {#operations-uploadfile}
+
+This takes the following parameters
+
+- fs - a remote name string eg "drive:"
+- remote - a path within that remote eg "dir"
+- each part in body represents a file to be uploaded
+See the [uploadfile command](https://rclone.org/commands/rclone_uploadfile/) command for more information on the above.
+
+**Authentication is required for this call.**
+
 ### options/blocks: List all the option blocks {#options-blocks}
 
 Returns
@@ -8768,6 +9499,97 @@ And this sets NOTICE level logs (normal without -v)
 
     rclone rc options/set --json '{"main": {"LogLevel": 6}}'
 
+### pluginsctl/addPlugin: Add a plugin using url {#pluginsctl-addPlugin}
+
+used for adding a plugin to the webgui
+
+This takes the following parameters
+
+- url: http url of the github repo where the plugin is hosted (http://github.com/rclone/rclone-webui-react)
+
+Eg
+
+   rclone rc pluginsctl/addPlugin
+
+**Authentication is required for this call.**
+
+### pluginsctl/getPluginsForType: Get plugins with type criteria {#pluginsctl-getPluginsForType}
+
+This shows all possible plugins by a mime type
+
+This takes the following parameters
+
+- type: supported mime type by a loaded plugin eg (video/mp4, audio/mp3)
+- pluginType: filter plugins based on their type eg (DASHBOARD, FILE_HANDLER, TERMINAL) 
+
+and returns
+
+- loadedPlugins: list of current production plugins
+- testPlugins: list of temporarily loaded development plugins, usually running on a different server.
+
+Eg
+
+   rclone rc pluginsctl/getPluginsForType type=video/mp4
+
+**Authentication is required for this call.**
+
+### pluginsctl/listPlugins: Get the list of currently loaded plugins {#pluginsctl-listPlugins}
+
+This allows you to get the currently enabled plugins and their details.
+
+This takes no parameters and returns
+
+- loadedPlugins: list of current production plugins
+- testPlugins: list of temporarily loaded development plugins, usually running on a different server.
+
+Eg
+
+   rclone rc pluginsctl/listPlugins
+
+**Authentication is required for this call.**
+
+### pluginsctl/listTestPlugins: Show currently loaded test plugins {#pluginsctl-listTestPlugins}
+
+allows listing of test plugins with the rclone.test set to true in package.json of the plugin
+
+This takes no parameters and returns
+
+- loadedTestPlugins: list of currently available test plugins
+
+Eg
+
+    rclone rc pluginsctl/listTestPlugins
+
+**Authentication is required for this call.**
+
+### pluginsctl/removePlugin: Remove a loaded plugin {#pluginsctl-removePlugin}
+
+This allows you to remove a plugin using it's name
+
+This takes parameters
+
+- name: name of the plugin in the format <author>/<plugin_name>
+
+Eg
+
+   rclone rc pluginsctl/removePlugin name=rclone/video-plugin
+
+**Authentication is required for this call.**
+
+### pluginsctl/removeTestPlugin: Remove  a test plugin {#pluginsctl-removeTestPlugin}
+
+This allows you to remove a plugin using it's name
+
+This takes the following parameters
+
+- name: name of the plugin in the format <author>/<plugin_name>
+
+Eg
+
+    rclone rc pluginsctl/removeTestPlugin name=rclone/rclone-webui-react
+
+**Authentication is required for this call.**
+
 ### rc/error: This returns an error {#rc-error}
 
 This returns an error with the input as part of its error string.
@@ -8844,6 +9666,19 @@ parameter key starting with file will forget that file and any
 starting with dir will forget that dir, eg
 
     rclone rc vfs/forget file=hello file2=goodbye dir=home/junk
+ 
+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.
+
+### vfs/list: List active VFSes. {#vfs-list}
+
+This lists the active VFSes.
+
+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.
 
 ### vfs/poll-interval: Get the status or update the value of the poll-interval option. {#vfs-poll-interval}
 
@@ -8866,6 +9701,11 @@ not reached.
 If poll-interval is updated or disabled temporarily, some changes
 might not get picked up by the polling function, depending on the
 used remote.
+ 
+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.
 
 ### vfs/refresh: Refresh the directory cache. {#vfs-refresh}
 
@@ -8883,6 +9723,11 @@ starting with dir will refresh that directory, eg
 
 If the parameter recursive=true is given the whole directory tree
 will get refreshed. This refresh will use --fast-list if enabled.
+ 
+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.
 
 
 
@@ -9137,7 +9982,7 @@ Here is an overview of the major features of each cloud storage system.
 | Memory                       | MD5         | Yes     | No               | No              | -         |
 | Microsoft Azure Blob Storage | MD5         | Yes     | No               | No              | R/W       |
 | Microsoft OneDrive           | SHA1 ‡‡     | Yes     | Yes              | No              | R         |
-| OpenDrive                    | MD5         | Yes     | Yes              | No              | -         |
+| OpenDrive                    | MD5         | Yes     | Yes              | Partial \*      | -         |
 | OpenStack Swift              | MD5         | Yes     | No               | No              | R/W       |
 | pCloud                       | MD5, SHA1   | Yes     | No               | No              | W         |
 | premiumize.me                | -           | No      | Yes              | No              | R         |
@@ -9218,6 +10063,12 @@ objects with the same name.
 This confuses rclone greatly when syncing - use the `rclone dedupe`
 command to rename or remove duplicates.
 
+\* 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 `rclone`.  It may be that this is a
+mistake or an unsupported feature.
+
 ### Restricted filenames ###
 
 Some cloud storage systems might have restrictions on the characters
@@ -9421,9 +10272,9 @@ operations more efficient.
 | ---------------------------- |:-----:|:----:|:----:|:-------:|:-------:|:-----:|:------------:|:------------:|:-----:| :------: |
 | 1Fichier                     | No    | No   | No   | No      | No      | No    | No           | No           |   No  |  Yes |
 | Amazon Drive                 | Yes   | No   | Yes  | Yes     | No [#575](https://github.com/rclone/rclone/issues/575) | No  | No  | No [#2178](https://github.com/rclone/rclone/issues/2178) | No  | Yes |
-| Amazon S3                    | No    | Yes  | No   | No      | No      | Yes   | Yes          | No [#2178](https://github.com/rclone/rclone/issues/2178) | No  | No |
-| Backblaze B2                 | No    | Yes  | No   | No      | Yes     | Yes   | Yes          | Yes | No  | No |
-| Box                          | Yes   | Yes  | Yes  | Yes     | No [#575](https://github.com/rclone/rclone/issues/575) | No  | Yes | Yes | No  | Yes |
+| Amazon S3                    | No    | Yes  | No   | No      | Yes     | Yes   | Yes          | No [#2178](https://github.com/rclone/rclone/issues/2178) | No  | No |
+| Backblaze B2                 | No    | Yes  | No   | No      | Yes     | Yes   | Yes          | Yes          | No  | No |
+| Box                          | Yes   | Yes  | Yes  | Yes     | Yes ‡‡  | No    | Yes          | Yes          | No  | Yes |
 | Citrix ShareFile             | Yes   | Yes  | Yes  | Yes     | No      | No    | Yes          | No          | No  | Yes |
 | Dropbox                      | Yes   | Yes  | Yes  | Yes     | No [#575](https://github.com/rclone/rclone/issues/575) | No  | Yes | Yes | Yes | Yes |
 | FTP                          | No    | No   | Yes  | Yes     | No      | No    | Yes          | No [#2178](https://github.com/rclone/rclone/issues/2178) | No  | Yes |
@@ -9437,10 +10288,10 @@ operations more efficient.
 | Mega                         | Yes   | No   | Yes  | Yes     | Yes     | No    | No           | No [#2178](https://github.com/rclone/rclone/issues/2178) | Yes | Yes |
 | Memory                       | No    | Yes  | No   | No      | No      | Yes   | Yes          | No          | No | No |
 | Microsoft Azure Blob Storage | Yes   | Yes  | No   | No      | No      | Yes   | Yes          | No [#2178](https://github.com/rclone/rclone/issues/2178) | No  | No |
-| Microsoft OneDrive           | Yes   | Yes  | Yes  | Yes     | No [#575](https://github.com/rclone/rclone/issues/575) | No | No | Yes | Yes | Yes |
+| Microsoft OneDrive           | Yes   | Yes  | Yes  | Yes     | Yes     | No    | No           | Yes | Yes | Yes |
 | OpenDrive                    | Yes   | Yes  | Yes  | Yes     | No      | No    | No           | No                                                    | No  | Yes |
 | OpenStack Swift              | Yes † | Yes  | No   | No      | No      | Yes   | Yes          | No [#2178](https://github.com/rclone/rclone/issues/2178) | Yes | No |
-| pCloud                       | Yes   | Yes  | Yes  | Yes     | Yes     | No    | No           | No [#2178](https://github.com/rclone/rclone/issues/2178) | Yes | Yes |
+| pCloud                       | Yes   | Yes  | Yes  | Yes     | Yes     | No    | No           | Yes | Yes | Yes |
 | premiumize.me                | Yes   | No   | Yes  | Yes     | No      | No    | No           | Yes         | Yes | Yes |
 | put.io                       | Yes   | No   | Yes  | Yes     | Yes     | No    | Yes          | No [#2178](https://github.com/rclone/rclone/issues/2178) | Yes | Yes |
 | QingStor                     | No    | Yes  | No   | No      | Yes     | Yes   | No           | No [#2178](https://github.com/rclone/rclone/issues/2178) | No  | No |
@@ -9496,6 +10347,9 @@ This is used for emptying the trash for a remote by `rclone cleanup`.
 If the server can't do `CleanUp` then `rclone cleanup` will return an
 error.
 
+‡‡ Note that while Box implements this it has to delete every file
+idividually so it will be slower than emptying the trash via the WebUI
+
 ### ListR ###
 
 The remote supports a recursive list to list all the contents beneath
@@ -9545,6 +10399,7 @@ These flags are available for every command.
       --bind string                          Local address to bind to for outgoing connections, IPv4, IPv6 or name.
       --buffer-size SizeSuffix               In memory buffer size when reading files for each --transfer. (default 16M)
       --bwlimit BwTimetable                  Bandwidth limit in kBytes/s, or use suffix b|k|M|G or a full timetable.
+      --bwlimit-file BwTimetable             Bandwidth limit per file in kBytes/s, or use suffix b|k|M|G or a full timetable.
       --ca-cert string                       CA certificate used to verify servers
       --cache-dir string                     Directory rclone will use for caching. (default "$HOME/.cache/rclone")
       --check-first                          Do all the checks before starting transfers.
@@ -9590,6 +10445,7 @@ These flags are available for every command.
       --immutable                            Do not modify files. Fail if existing files have been modified.
       --include stringArray                  Include files matching pattern
       --include-from stringArray             Read include patterns from file (use - to read from stdin)
+  -i, --interactive                          Enable interactive mode
       --log-file string                      Log everything to this file
       --log-format string                    Comma separated list of log format options (default "date,time")
       --log-level string                     Log level DEBUG|INFO|NOTICE|ERROR (default "NOTICE")
@@ -9644,6 +10500,7 @@ These flags are available for every command.
       --rc-web-gui-force-update              Force update to latest version of web gui
       --rc-web-gui-no-open-browser           Don't open the browser automatically
       --rc-web-gui-update                    Check and update to latest version of web gui
+      --refresh-times                        Refresh the modtime of remote files.
       --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)
       --size-only                            Skip based on size only, not mod-time or checksum
@@ -9663,14 +10520,14 @@ These flags are available for every command.
       --tpslimit float                       Limit HTTP transactions per second to this.
       --tpslimit-burst int                   Max burst of transactions for --tpslimit. (default 1)
       --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 (default "hash")
+      --track-renames-strategy string        Strategies to use when synchronizing using track-renames hash|modtime|leaf (default "hash")
       --transfers int                        Number of file transfers to run in parallel. (default 4)
   -u, --update                               Skip files that are newer on the destination.
       --use-cookies                          Enable session cookiejar.
       --use-json-log                         Use json log format.
       --use-mmap                             Use mmap allocator (see docs).
       --use-server-modtime                   Use server modified time instead of object metadata
-      --user-agent string                    Set the user-agent to a specified string. The default is rclone/ version (default "rclone/v1.52.0")
+      --user-agent string                    Set the user-agent to a specified string. The default is rclone/ version (default "rclone/v1.53.0")
   -v, --verbose count                        Print lots more stuff (repeat for more)
 ```
 
@@ -9681,10 +10538,11 @@ and may be set in the config file.
 
 ```
       --acd-auth-url string                                      Auth server URL.
-      --acd-client-id string                                     Amazon Application Client ID.
-      --acd-client-secret string                                 Amazon Application Client Secret.
+      --acd-client-id string                                     OAuth Client Id
+      --acd-client-secret string                                 OAuth Client Secret
       --acd-encoding MultiEncoder                                This sets the encoding for the backend. (default Slash,InvalidUtf8,Dot)
       --acd-templink-threshold SizeSuffix                        Files >= this size will be downloaded via their tempLink. (default 9G)
+      --acd-token string                                         OAuth Access Token as a JSON blob.
       --acd-token-url string                                     Token server url.
       --acd-upload-wait-per-gb Duration                          Additional time per GB to wait after a failed complete upload to see if it appears. (default 3m0s)
       --alias-remote string                                      Remote or path to alias.
@@ -9703,6 +10561,7 @@ and may be set in the config file.
       --azureblob-use-emulator                                   Uses local storage emulator if provided as 'true' (leave blank if using real azure storage endpoint)
       --b2-account string                                        Account ID or Application Key ID
       --b2-chunk-size SizeSuffix                                 Upload chunk size. Must fit in memory. (default 96M)
+      --b2-copy-cutoff SizeSuffix                                Cutoff for switching to multipart copy (default 4G)
       --b2-disable-checksum                                      Disable checksums for large (> upload cutoff) files
       --b2-download-auth-duration Duration                       Time before the authorization token will expire in s or suffix ms|s|m|h|d. (default 1w)
       --b2-download-url string                                   Custom endpoint for downloads.
@@ -9710,16 +10569,22 @@ and may be set in the config file.
       --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-memory-pool-flush-time Duration                       How often internal memory buffer pools will be flushed. (default 1m0s)
+      --b2-memory-pool-use-mmap                                  Whether to use mmap buffers in internal memory pool.
       --b2-test-mode string                                      A flag string for X-Bz-Test-Mode header for debugging.
       --b2-upload-cutoff SizeSuffix                              Cutoff for switching to chunked upload. (default 200M)
       --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 "user")
-      --box-client-id string                                     Box App Client Id.
-      --box-client-secret string                                 Box App Client Secret
+      --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-encoding MultiEncoder                                This sets the encoding for the backend. (default Slash,BackSlash,Del,Ctl,RightSpace,InvalidUtf8,Dot)
       --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 (>= 50MB). (default 50M)
       --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.
@@ -9731,7 +10596,7 @@ and may be set in the config file.
       --cache-db-wait-time Duration                              How long to wait for the DB to be available - 0 is unlimited (default 1s)
       --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
+      --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)
@@ -9751,17 +10616,18 @@ and may be set in the config file.
   -L, --copy-links                                               Follow symlinks and copy the pointed to item.
       --crypt-directory-name-encryption                          Option to either encrypt directory names or leave them intact. (default true)
       --crypt-filename-encryption string                         How to encrypt the filenames. (default "standard")
-      --crypt-password string                                    Password or pass phrase for encryption.
-      --crypt-password2 string                                   Password or pass phrase for salt. Optional but recommended.
+      --crypt-password string                                    Password or pass phrase for encryption. (obscured)
+      --crypt-password2 string                                   Password or pass phrase for salt. Optional but recommended. (obscured)
       --crypt-remote string                                      Remote to encrypt/decrypt.
+      --crypt-server-side-across-configs                         Allow server side operations (eg copy) to work across different crypt configs.
       --crypt-show-mapping                                       For all files listed show how the names encrypt.
       --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 (e.g. file.doc to file.docx). This will confuse sync and reupload every time.
-      --drive-alternate-export                                   Use alternate export URLs for google documents export.,
       --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. Must a power of 2 >= 256k. (default 8M)
-      --drive-client-id string                                   Google Application Client Id
-      --drive-client-secret string                               Google Application Client Secret
+      --drive-client-id string                                   OAuth Client Id
+      --drive-client-secret string                               OAuth Client Secret
       --drive-disable-http2                                      Disable drive using http2 (default true)
       --drive-encoding MultiEncoder                              This sets the encoding for the backend. (default InvalidUtf8)
       --drive-export-formats string                              Comma separated list of preferred formats for downloading Google docs. (default "docx,xlsx,pptx,svg")
@@ -9782,65 +10648,81 @@ and may be set in the config file.
       --drive-skip-checksum-gphotos                              Skip MD5 checksum on Google photos and videos only.
       --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-upload-limit                               Make upload limit errors be fatal
       --drive-team-drive string                                  ID of the 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 8M)
       --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's are greater, use drive v2 API to download. (default off)
+      --dropbox-auth-url string                                  Auth server URL.
       --dropbox-chunk-size SizeSuffix                            Upload chunk size. (< 150M). (default 48M)
-      --dropbox-client-id string                                 Dropbox App Client Id
-      --dropbox-client-secret string                             Dropbox App Client Secret
+      --dropbox-client-id string                                 OAuth Client Id
+      --dropbox-client-secret string                             OAuth Client Secret
       --dropbox-encoding MultiEncoder                            This sets the encoding for the backend. (default Slash,BackSlash,Del,RightSpace,InvalidUtf8,Dot)
       --dropbox-impersonate string                               Impersonate this user when using a business account.
+      --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-encoding MultiEncoder                            This sets the encoding for the backend. (default Slash,LtGt,DoubleQuote,SingleQuote,BackQuote,Dollar,BackSlash,Del,Ctl,LeftSpace,RightSpace,InvalidUtf8,Dot)
       --fichier-shared-folder string                             If you want to download a shared folder, add this parameter
       --ftp-concurrency int                                      Maximum number of FTP simultaneous connections, 0 for unlimited
       --ftp-disable-epsv                                         Disable using EPSV even if server advertises support
       --ftp-encoding MultiEncoder                                This sets the encoding for the backend. (default Slash,Del,Ctl,RightSpace,Dot)
+      --ftp-explicit-tls                                         Use FTP over TLS (Explicit)
       --ftp-host string                                          FTP host to connect to
       --ftp-no-check-certificate                                 Do not verify the TLS certificate of the server
-      --ftp-pass string                                          FTP password
+      --ftp-pass string                                          FTP password (obscured)
       --ftp-port string                                          FTP port, leave blank to use default (21)
-      --ftp-tls                                                  Use FTP over TLS (Implicit)
+      --ftp-tls                                                  Use FTPS over TLS (Implicit)
       --ftp-user string                                          FTP username, leave blank for current username, $USER
+      --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                                     Google Application Client Id
-      --gcs-client-secret string                                 Google Application Client Secret
+      --gcs-client-id string                                     OAuth Client Id
+      --gcs-client-secret string                                 OAuth Client Secret
       --gcs-encoding MultiEncoder                                This sets the encoding for the backend. (default Slash,CrLf,InvalidUtf8,Dot)
       --gcs-location string                                      Location for the newly created buckets.
       --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.
-      --gphotos-client-id string                                 Google Application Client Id
-      --gphotos-client-secret string                             Google Application Client Secret
+      --gcs-token string                                         OAuth Access Token as a JSON blob.
+      --gcs-token-url string                                     Token server url.
+      --gphotos-auth-url string                                  Auth server URL.
+      --gphotos-client-id string                                 OAuth Client Id
+      --gphotos-client-secret string                             OAuth Client Secret
       --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.
       --http-headers CommaSepList                                Set HTTP headers for all transactions
       --http-no-head                                             Don't use HEAD requests to find file sizes in dir listing
       --http-no-slash                                            Set this if the site doesn't end directories with /
       --http-url string                                          URL of http host to connect to
+      --hubic-auth-url string                                    Auth server URL.
       --hubic-chunk-size SizeSuffix                              Above this size files will be chunked into a _segments container. (default 5G)
-      --hubic-client-id string                                   Hubic Client Id
-      --hubic-client-secret string                               Hubic Client Secret
+      --hubic-client-id string                                   OAuth Client Id
+      --hubic-client-secret string                               OAuth Client Secret
       --hubic-encoding MultiEncoder                              This sets the encoding for the backend. (default Slash,InvalidUtf8)
       --hubic-no-chunk                                           Don't chunk files during streaming upload.
+      --hubic-token string                                       OAuth Access Token as a JSON blob.
+      --hubic-token-url string                                   Token server url.
       --jottacloud-encoding MultiEncoder                         This sets 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 10M)
       --jottacloud-trashed-only                                  Only show files that are in the trash.
-      --jottacloud-unlink                                        Remove existing public link to file/folder with link command rather than creating.
       --jottacloud-upload-resume-limit SizeSuffix                Files bigger than this can be resumed if the upload fail's. (default 10M)
       --koofr-encoding MultiEncoder                              This sets the encoding for the backend. (default Slash,BackSlash,Del,Ctl,InvalidUtf8,Dot)
       --koofr-endpoint string                                    The Koofr API endpoint to use (default "https://app.koofr.net")
       --koofr-mountid string                                     Mount ID of the mount to use. If omitted, the primary mount is used.
-      --koofr-password string                                    Your Koofr password for rclone (generate one at https://app.koofr.net/app/admin/preferences/password)
+      --koofr-password string                                    Your Koofr password for rclone (generate one at https://app.koofr.net/app/admin/preferences/password) (obscured)
       --koofr-setmtime                                           Does the backend support setting modification time. Set this to false if you use a mount ID that points to a Dropbox or Amazon Drive backend. (default true)
       --koofr-user string                                        Your Koofr user name
   -l, --links                                                    Translate symlinks to/from regular files with a '.rclonelink' extension
@@ -9848,12 +10730,13 @@ and may be set in the config file.
       --local-case-sensitive                                     Force the filesystem to report itself as case sensitive.
       --local-encoding MultiEncoder                              This sets the encoding for the backend. (default Slash,Dot)
       --local-no-check-updated                                   Don't check to see if the files change during upload
+      --local-no-set-modtime                                     Disable setting modtime
       --local-no-sparse                                          Disable sparse files for multi-thread downloads
       --local-no-unicode-normalization                           Don't apply unicode normalization to paths and filenames (Deprecated)
       --local-nounc string                                       Disable UNC (long path names) conversion on Windows
       --mailru-check-hash                                        What should copy do if file checksum is mismatched or invalid (default true)
       --mailru-encoding MultiEncoder                             This sets the encoding for the backend. (default Slash,LtGt,DoubleQuote,Colon,Question,Asterisk,Pipe,BackSlash,Del,Ctl,InvalidUtf8,Dot)
-      --mailru-pass string                                       Password
+      --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 "*.mkv,*.avi,*.mp4,*.mp3,*.zip,*.gz,*.rar,*.pdf")
       --mailru-speedup-max-disk SizeSuffix                       This option allows you to disable speedup (put by hash) for large files (default 3G)
@@ -9862,25 +10745,33 @@ and may be set in the config file.
       --mega-debug                                               Output more debug from Mega.
       --mega-encoding MultiEncoder                               This sets 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.
+      --mega-pass string                                         Password. (obscured)
       --mega-user string                                         User name
   -x, --one-file-system                                          Don't cross filesystem boundaries (unix/macOS only).
+      --onedrive-auth-url string                                 Auth server URL.
       --onedrive-chunk-size SizeSuffix                           Chunk size to upload files with - must be multiple of 320k (327,680 bytes). (default 10M)
-      --onedrive-client-id string                                Microsoft App Client Id
-      --onedrive-client-secret string                            Microsoft App Client Secret
+      --onedrive-client-id string                                OAuth Client Id
+      --onedrive-client-secret string                            OAuth Client Secret
       --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 MultiEncoder                           This sets the encoding for the backend. (default Slash,LtGt,DoubleQuote,Colon,Question,Asterisk,Pipe,Hash,Percent,BackSlash,Del,Ctl,LeftSpace,LeftTilde,RightSpace,RightPeriod,InvalidUtf8,Dot)
       --onedrive-expose-onenote-files                            Set to make OneNote files show up in directory listings.
+      --onedrive-no-versions                                     Remove all versions on modifying operations
       --onedrive-server-side-across-configs                      Allow server side operations (eg copy) to work across different onedrive configs.
+      --onedrive-token string                                    OAuth Access Token as a JSON blob.
+      --onedrive-token-url string                                Token server url.
       --opendrive-chunk-size SizeSuffix                          Files will be uploaded in chunks this size. (default 10M)
       --opendrive-encoding MultiEncoder                          This sets the encoding for the backend. (default Slash,LtGt,DoubleQuote,Colon,Question,Asterisk,Pipe,BackSlash,LeftSpace,LeftCrLfHtVt,RightSpace,RightCrLfHtVt,InvalidUtf8,Dot)
-      --opendrive-password string                                Password.
+      --opendrive-password string                                Password. (obscured)
       --opendrive-username string                                Username
-      --pcloud-client-id string                                  Pcloud App Client Id
-      --pcloud-client-secret string                              Pcloud App Client Secret
+      --pcloud-auth-url string                                   Auth server URL.
+      --pcloud-client-id string                                  OAuth Client Id
+      --pcloud-client-secret string                              OAuth Client Secret
       --pcloud-encoding MultiEncoder                             This sets the encoding for the backend. (default Slash,BackSlash,Del,Ctl,InvalidUtf8,Dot)
+      --pcloud-hostname string                                   Hostname to connect to. (default "api.pcloud.com")
       --pcloud-root-folder-id string                             Fill in for rclone to use a non root folder as its starting point. (default "d0")
+      --pcloud-token string                                      OAuth Access Token as a JSON blob.
+      --pcloud-token-url string                                  Token server url.
       --premiumizeme-encoding MultiEncoder                       This sets the encoding for the backend. (default Slash,DoubleQuote,BackSlash,Del,Ctl,InvalidUtf8,Dot)
       --putio-encoding MultiEncoder                              This sets the encoding for the backend. (default Slash,BackSlash,Del,Ctl,InvalidUtf8,Dot)
       --qingstor-access-key-id string                            QingStor Access Key ID
@@ -9897,7 +10788,7 @@ and may be set in the config file.
       --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 5M)
-      --s3-copy-cutoff SizeSuffix                                Cutoff for switching to multipart copy (default 5G)
+      --s3-copy-cutoff SizeSuffix                                Cutoff for switching to multipart copy (default 4.656G)
       --s3-disable-checksum                                      Don't store MD5 checksum with object metadata
       --s3-encoding MultiEncoder                                 This sets the encoding for the backend. (default Slash,InvalidUtf8,Dot)
       --s3-endpoint string                                       Endpoint for S3 API.
@@ -9906,13 +10797,17 @@ and may be set in the config file.
       --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-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-memory-pool-flush-time Duration                       How often internal memory buffer pools will be flushed. (default 1m0s)
       --s3-memory-pool-use-mmap                                  Whether to use mmap buffers in internal memory pool.
+      --s3-no-check-bucket                                       If set don't attempt to check the bucket exists or create it
+      --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-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                               If using SSE-C you must provide the secret encryption key used to encrypt/decrypt your data.
       --s3-sse-customer-key-md5 string                           If using SSE-C you must provide the secret encryption key MD5 checksum.
@@ -9926,24 +10821,26 @@ and may be set in the config file.
       --seafile-create-library                                   Should rclone create a library if it doesn't exist
       --seafile-encoding MultiEncoder                            This sets the encoding for the backend. (default Slash,DoubleQuote,BackSlash,Ctl,InvalidUtf8)
       --seafile-library string                                   Name of the library. Leave blank to access all non-encrypted libraries.
-      --seafile-library-key string                               Library password (for encrypted libraries only). Leave blank if you pass it through the command line.
-      --seafile-pass string                                      Password
+      --seafile-library-key string                               Library password (for encrypted libraries only). Leave blank if you pass it through the command line. (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-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-key-file string                                     Path to PEM-encoded private key file, leave blank or set key-use-agent to use ssh-agent.
-      --sftp-key-file-pass string                                The passphrase to decrypt the 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, If specified, will override key_file parameter.
       --sftp-key-use-agent                                       When set forces the usage of the ssh-agent.
       --sftp-md5sum-command string                               The command used to read md5 hashes. Leave blank for autodetect.
-      --sftp-pass string                                         SSH password, leave blank to use ssh-agent.
+      --sftp-pass string                                         SSH password, leave blank to use ssh-agent. (obscured)
       --sftp-path-override string                                Override path used by SSH connection.
       --sftp-port string                                         SSH port, leave blank to use default (22)
+      --sftp-server-command string                               Specifies the path or command to run a sftp server on the remote host.
       --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. Leave blank for autodetect.
       --sftp-skip-links                                          Set to skip any symlinks and any other non regular files.
+      --sftp-subsystem string                                    Specifies the SSH2 subsystem on the remote host. (default "sftp")
       --sftp-use-insecure-cipher                                 Enable the use of insecure ciphers and key exchange methods.
       --sftp-user string                                         SSH username, leave blank for current username, ncw
       --sharefile-chunk-size SizeSuffix                          Upload chunk size. Must a power of 2 >= 256k. (default 64M)
@@ -9996,14 +10893,16 @@ and may be set in the config file.
       --union-upstreams string                                   List of space separated upstreams.
       --webdav-bearer-token string                               Bearer token instead of user/pass (eg a Macaroon)
       --webdav-bearer-token-command string                       Command to run to get a bearer token
-      --webdav-pass string                                       Password.
+      --webdav-pass string                                       Password. (obscured)
       --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-client-id string                                  Yandex Client Id
-      --yandex-client-secret string                              Yandex Client Secret
+      --yandex-auth-url string                                   Auth server URL.
+      --yandex-client-id string                                  OAuth Client Id
+      --yandex-client-secret string                              OAuth Client Secret
       --yandex-encoding MultiEncoder                             This sets the encoding for the backend. (default Slash,Del,Ctl,InvalidUtf8,Dot)
-      --yandex-unlink                                            Remove existing public link to file/folder with link command rather than creating.
+      --yandex-token string                                      OAuth Access Token as a JSON blob.
+      --yandex-token-url string                                  Token server url.
 ```
 
  1Fichier
@@ -10418,7 +11317,8 @@ Here are the standard options specific to amazon cloud drive (Amazon Drive).
 
 #### --acd-client-id
 
-Amazon Application Client ID.
+OAuth Client Id
+Leave blank normally.
 
 - Config:      client_id
 - Env Var:     RCLONE_ACD_CLIENT_ID
@@ -10427,7 +11327,8 @@ Amazon Application Client ID.
 
 #### --acd-client-secret
 
-Amazon Application Client Secret.
+OAuth Client Secret
+Leave blank normally.
 
 - Config:      client_secret
 - Env Var:     RCLONE_ACD_CLIENT_SECRET
@@ -10438,10 +11339,19 @@ Amazon Application Client Secret.
 
 Here are the advanced options specific to amazon cloud drive (Amazon Drive).
 
+#### --acd-token
+
+OAuth Access Token as a JSON blob.
+
+- Config:      token
+- Env Var:     RCLONE_ACD_TOKEN
+- Type:        string
+- Default:     ""
+
 #### --acd-auth-url
 
 Auth server URL.
-Leave blank to use Amazon's.
+Leave blank to use the provider defaults.
 
 - Config:      auth_url
 - Env Var:     RCLONE_ACD_AUTH_URL
@@ -10451,7 +11361,7 @@ Leave blank to use Amazon's.
 #### --acd-token-url
 
 Token server url.
-leave blank to use Amazon's.
+Leave blank to use the provider defaults.
 
 - Config:      token_url
 - Env Var:     RCLONE_ACD_TOKEN_URL
@@ -10589,7 +11499,7 @@ List the contents of a bucket
 Sync `/home/local/directory` to the remote bucket, deleting any excess
 files in the bucket.
 
-    rclone sync /home/local/directory remote:bucket
+    rclone sync -i /home/local/directory remote:bucket
 
 ## AWS S3 {#amazon-s3}
 
@@ -10823,6 +11733,16 @@ side copy to update the modification if the object can be copied in a single par
 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.
 
+### Cleanup ###
+
+If you run `rclone cleanup s3:bucket` then it will remove all pending
+multipart uploads older than 24 hours. You can use the `-i` flag to
+see exactly what it will do. If you want more control over the expiry
+date then run `rclone backend cleanup s3:bucket -o max-age=1h` to
+expire all uploads older than one hour. You can use `rclone backend
+list-multipart-uploads s3:bucket` to see the pending multipart
+uploads.
+
 #### Restricted filename characters
 
 S3 allows any valid UTF-8 string as a key.
@@ -11019,6 +11939,8 @@ Choose your S3 provider.
         - Minio Object Storage
     - "Netease"
         - Netease Object Storage (NOS)
+    - "Scaleway"
+        - Scaleway Object Storage
     - "StackPath"
         - StackPath Object Storage
     - "Wasabi"
@@ -11122,6 +12044,20 @@ Region to connect to.
 
 #### --s3-region
 
+Region to connect to.
+
+- Config:      region
+- Env Var:     RCLONE_S3_REGION
+- Type:        string
+- Default:     ""
+- Examples:
+    - "nl-ams"
+        - Amsterdam, The Netherlands
+    - "fr-par"
+        - Paris, France
+
+#### --s3-region
+
 Region to connect to.
 Leave blank if you are using an S3 clone and you don't have a region.
 
@@ -11155,74 +12091,130 @@ Specify if using an IBM COS On Premise.
 - Type:        string
 - Default:     ""
 - Examples:
-    - "s3-api.us-geo.objectstorage.softlayer.net"
+    - "s3.us.cloud-object-storage.appdomain.cloud"
         - US Cross Region Endpoint
-    - "s3-api.dal.us-geo.objectstorage.softlayer.net"
+    - "s3.dal.us.cloud-object-storage.appdomain.cloud"
         - US Cross Region Dallas Endpoint
-    - "s3-api.wdc-us-geo.objectstorage.softlayer.net"
+    - "s3.wdc.us.cloud-object-storage.appdomain.cloud"
         - US Cross Region Washington DC Endpoint
-    - "s3-api.sjc-us-geo.objectstorage.softlayer.net"
+    - "s3.sjc.us.cloud-object-storage.appdomain.cloud"
         - US Cross Region San Jose Endpoint
-    - "s3-api.us-geo.objectstorage.service.networklayer.com"
+    - "s3.private.us.cloud-object-storage.appdomain.cloud"
         - US Cross Region Private Endpoint
-    - "s3-api.dal-us-geo.objectstorage.service.networklayer.com"
+    - "s3.private.dal.us.cloud-object-storage.appdomain.cloud"
         - US Cross Region Dallas Private Endpoint
-    - "s3-api.wdc-us-geo.objectstorage.service.networklayer.com"
+    - "s3.private.wdc.us.cloud-object-storage.appdomain.cloud"
         - US Cross Region Washington DC Private Endpoint
-    - "s3-api.sjc-us-geo.objectstorage.service.networklayer.com"
+    - "s3.private.sjc.us.cloud-object-storage.appdomain.cloud"
         - US Cross Region San Jose Private Endpoint
-    - "s3.us-east.objectstorage.softlayer.net"
+    - "s3.us-east.cloud-object-storage.appdomain.cloud"
         - US Region East Endpoint
-    - "s3.us-east.objectstorage.service.networklayer.com"
+    - "s3.private.us-east.cloud-object-storage.appdomain.cloud"
         - US Region East Private Endpoint
-    - "s3.us-south.objectstorage.softlayer.net"
+    - "s3.us-south.cloud-object-storage.appdomain.cloud"
         - US Region South Endpoint
-    - "s3.us-south.objectstorage.service.networklayer.com"
+    - "s3.private.us-south.cloud-object-storage.appdomain.cloud"
         - US Region South Private Endpoint
-    - "s3.eu-geo.objectstorage.softlayer.net"
+    - "s3.eu.cloud-object-storage.appdomain.cloud"
         - EU Cross Region Endpoint
-    - "s3.fra-eu-geo.objectstorage.softlayer.net"
+    - "s3.fra.eu.cloud-object-storage.appdomain.cloud"
         - EU Cross Region Frankfurt Endpoint
-    - "s3.mil-eu-geo.objectstorage.softlayer.net"
+    - "s3.mil.eu.cloud-object-storage.appdomain.cloud"
         - EU Cross Region Milan Endpoint
-    - "s3.ams-eu-geo.objectstorage.softlayer.net"
+    - "s3.ams.eu.cloud-object-storage.appdomain.cloud"
         - EU Cross Region Amsterdam Endpoint
-    - "s3.eu-geo.objectstorage.service.networklayer.com"
+    - "s3.private.eu.cloud-object-storage.appdomain.cloud"
         - EU Cross Region Private Endpoint
-    - "s3.fra-eu-geo.objectstorage.service.networklayer.com"
+    - "s3.private.fra.eu.cloud-object-storage.appdomain.cloud"
         - EU Cross Region Frankfurt Private Endpoint
-    - "s3.mil-eu-geo.objectstorage.service.networklayer.com"
+    - "s3.private.mil.eu.cloud-object-storage.appdomain.cloud"
         - EU Cross Region Milan Private Endpoint
-    - "s3.ams-eu-geo.objectstorage.service.networklayer.com"
+    - "s3.private.ams.eu.cloud-object-storage.appdomain.cloud"
         - EU Cross Region Amsterdam Private Endpoint
-    - "s3.eu-gb.objectstorage.softlayer.net"
+    - "s3.eu-gb.cloud-object-storage.appdomain.cloud"
         - Great Britain Endpoint
-    - "s3.eu-gb.objectstorage.service.networklayer.com"
+    - "s3.private.eu-gb.cloud-object-storage.appdomain.cloud"
         - Great Britain Private Endpoint
-    - "s3.ap-geo.objectstorage.softlayer.net"
+    - "s3.eu-de.cloud-object-storage.appdomain.cloud"
+        - EU Region DE Endpoint
+    - "s3.private.eu-de.cloud-object-storage.appdomain.cloud"
+        - EU Region DE Private Endpoint
+    - "s3.ap.cloud-object-storage.appdomain.cloud"
         - APAC Cross Regional Endpoint
-    - "s3.tok-ap-geo.objectstorage.softlayer.net"
+    - "s3.tok.ap.cloud-object-storage.appdomain.cloud"
         - APAC Cross Regional Tokyo Endpoint
-    - "s3.hkg-ap-geo.objectstorage.softlayer.net"
+    - "s3.hkg.ap.cloud-object-storage.appdomain.cloud"
         - APAC Cross Regional HongKong Endpoint
-    - "s3.seo-ap-geo.objectstorage.softlayer.net"
+    - "s3.seo.ap.cloud-object-storage.appdomain.cloud"
         - APAC Cross Regional Seoul Endpoint
-    - "s3.ap-geo.objectstorage.service.networklayer.com"
+    - "s3.private.ap.cloud-object-storage.appdomain.cloud"
         - APAC Cross Regional Private Endpoint
-    - "s3.tok-ap-geo.objectstorage.service.networklayer.com"
+    - "s3.private.tok.ap.cloud-object-storage.appdomain.cloud"
         - APAC Cross Regional Tokyo Private Endpoint
-    - "s3.hkg-ap-geo.objectstorage.service.networklayer.com"
+    - "s3.private.hkg.ap.cloud-object-storage.appdomain.cloud"
         - APAC Cross Regional HongKong Private Endpoint
-    - "s3.seo-ap-geo.objectstorage.service.networklayer.com"
+    - "s3.private.seo.ap.cloud-object-storage.appdomain.cloud"
         - APAC Cross Regional Seoul Private Endpoint
-    - "s3.mel01.objectstorage.softlayer.net"
+    - "s3.jp-tok.cloud-object-storage.appdomain.cloud"
+        - APAC Region Japan Endpoint
+    - "s3.private.jp-tok.cloud-object-storage.appdomain.cloud"
+        - APAC Region Japan Private Endpoint
+    - "s3.au-syd.cloud-object-storage.appdomain.cloud"
+        - APAC Region Australia Endpoint
+    - "s3.private.au-syd.cloud-object-storage.appdomain.cloud"
+        - APAC Region Australia Private Endpoint
+    - "s3.ams03.cloud-object-storage.appdomain.cloud"
+        - Amsterdam Single Site Endpoint
+    - "s3.private.ams03.cloud-object-storage.appdomain.cloud"
+        - Amsterdam Single Site Private Endpoint
+    - "s3.che01.cloud-object-storage.appdomain.cloud"
+        - Chennai Single Site Endpoint
+    - "s3.private.che01.cloud-object-storage.appdomain.cloud"
+        - Chennai Single Site Private Endpoint
+    - "s3.mel01.cloud-object-storage.appdomain.cloud"
         - Melbourne Single Site Endpoint
-    - "s3.mel01.objectstorage.service.networklayer.com"
+    - "s3.private.mel01.cloud-object-storage.appdomain.cloud"
         - Melbourne Single Site Private Endpoint
-    - "s3.tor01.objectstorage.softlayer.net"
+    - "s3.osl01.cloud-object-storage.appdomain.cloud"
+        - Oslo Single Site Endpoint
+    - "s3.private.osl01.cloud-object-storage.appdomain.cloud"
+        - Oslo Single Site Private Endpoint
+    - "s3.tor01.cloud-object-storage.appdomain.cloud"
         - Toronto Single Site Endpoint
-    - "s3.tor01.objectstorage.service.networklayer.com"
+    - "s3.private.tor01.cloud-object-storage.appdomain.cloud"
         - Toronto Single Site Private Endpoint
+    - "s3.seo01.cloud-object-storage.appdomain.cloud"
+        - Seoul Single Site Endpoint
+    - "s3.private.seo01.cloud-object-storage.appdomain.cloud"
+        - Seoul Single Site Private Endpoint
+    - "s3.mon01.cloud-object-storage.appdomain.cloud"
+        - Montreal Single Site Endpoint
+    - "s3.private.mon01.cloud-object-storage.appdomain.cloud"
+        - Montreal Single Site Private Endpoint
+    - "s3.mex01.cloud-object-storage.appdomain.cloud"
+        - Mexico Single Site Endpoint
+    - "s3.private.mex01.cloud-object-storage.appdomain.cloud"
+        - Mexico Single Site Private Endpoint
+    - "s3.sjc04.cloud-object-storage.appdomain.cloud"
+        - San Jose Single Site Endpoint
+    - "s3.private.sjc04.cloud-object-storage.appdomain.cloud"
+        - San Jose Single Site Private Endpoint
+    - "s3.mil01.cloud-object-storage.appdomain.cloud"
+        - Milan Single Site Endpoint
+    - "s3.private.mil01.cloud-object-storage.appdomain.cloud"
+        - Milan Single Site Private Endpoint
+    - "s3.hkg02.cloud-object-storage.appdomain.cloud"
+        - Hong Kong Single Site Endpoint
+    - "s3.private.hkg02.cloud-object-storage.appdomain.cloud"
+        - Hong Kong Single Site Private Endpoint
+    - "s3.par01.cloud-object-storage.appdomain.cloud"
+        - Paris Single Site Endpoint
+    - "s3.private.par01.cloud-object-storage.appdomain.cloud"
+        - Paris Single Site Private Endpoint
+    - "s3.sng01.cloud-object-storage.appdomain.cloud"
+        - Singapore Single Site Endpoint
+    - "s3.private.sng01.cloud-object-storage.appdomain.cloud"
+        - Singapore Single Site Private Endpoint
 
 #### --s3-endpoint
 
@@ -11274,6 +12266,20 @@ Endpoint for OSS API.
 
 #### --s3-endpoint
 
+Endpoint for Scaleway Object Storage.
+
+- Config:      endpoint
+- Env Var:     RCLONE_S3_ENDPOINT
+- Type:        string
+- Default:     ""
+- Examples:
+    - "s3.nl-ams.scw.cloud"
+        - Amsterdam Endpoint
+    - "s3.fr-par.scw.cloud"
+        - Paris Endpoint
+
+#### --s3-endpoint
+
 Endpoint for StackPath Object Storage.
 
 - Config:      endpoint
@@ -11555,6 +12561,22 @@ The storage class to use when storing new objects in OSS.
     - "STANDARD_IA"
         - Infrequent access storage mode.
 
+#### --s3-storage-class
+
+The storage class to use when storing new objects in S3.
+
+- Config:      storage_class
+- Env Var:     RCLONE_S3_STORAGE_CLASS
+- Type:        string
+- Default:     ""
+- Examples:
+    - ""
+        - Default
+    - "STANDARD"
+        - The Standard class for any upload; suitable for on-demand content like streaming or CDN.
+    - "GLACIER"
+        - Archived storage; prices are lower, but it needs to be restored first to be accessed.
+
 ### Advanced Options
 
 Here are the advanced options specific to s3 (Amazon S3 Compliant Storage Provider (AWS, Alibaba, Ceph, Digital Ocean, Dreamhost, IBM COS, Minio, etc)).
@@ -11662,6 +12684,25 @@ larger files then you will need to increase chunk_size.
 - Type:        SizeSuffix
 - Default:     5M
 
+#### --s3-max-upload-parts
+
+Maximum number of parts in a multipart upload.
+
+This option defines the maximum number of multipart chunks to use
+when doing a multipart upload.
+
+This can be useful if a service does not support the AWS S3
+specification of 10,000 chunks.
+
+Rclone will automatically increase the chunk size when uploading a
+large file of a known size to stay below this number of chunks limit.
+
+
+- Config:      max_upload_parts
+- Env Var:     RCLONE_S3_MAX_UPLOAD_PARTS
+- Type:        int
+- Default:     10000
+
 #### --s3-copy-cutoff
 
 Cutoff for switching to multipart copy
@@ -11674,7 +12715,7 @@ The minimum is 0 and the maximum is 5GB.
 - Config:      copy_cutoff
 - Env Var:     RCLONE_S3_COPY_CUTOFF
 - Type:        SizeSuffix
-- Default:     5G
+- Default:     4.656G
 
 #### --s3-disable-checksum
 
@@ -11690,6 +12731,41 @@ to start uploading.
 - Type:        bool
 - Default:     false
 
+#### --s3-shared-credentials-file
+
+Path to the shared credentials file
+
+If env_auth = true then rclone can use a shared credentials file.
+
+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.
+
+    Linux/OSX: "$HOME/.aws/credentials"
+    Windows:   "%USERPROFILE%\.aws\credentials"
+
+
+- Config:      shared_credentials_file
+- Env Var:     RCLONE_S3_SHARED_CREDENTIALS_FILE
+- Type:        string
+- Default:     ""
+
+#### --s3-profile
+
+Profile to use in the shared credentials file
+
+If env_auth = true then rclone can use a shared credentials file. This
+variable controls which profile is used in that file.
+
+If empty it will default to the environment variable "AWS_PROFILE" or
+"default" if that environment variable is also not set.
+
+
+- Config:      profile
+- Env Var:     RCLONE_S3_PROFILE
+- Type:        string
+- Default:     ""
+
 #### --s3-session-token
 
 An AWS session token
@@ -11787,6 +12863,19 @@ In Ceph, this can be increased with the "rgw list buckets max chunk" option.
 - Type:        int
 - Default:     1000
 
+#### --s3-no-check-bucket
+
+If set don'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.
+
+
+- Config:      no_check_bucket
+- Env Var:     RCLONE_S3_NO_CHECK_BUCKET
+- Type:        bool
+- Default:     false
+
 #### --s3-encoding
 
 This sets the encoding for the backend.
@@ -11818,6 +12907,129 @@ Whether to use mmap buffers in internal memory pool.
 - Type:        bool
 - Default:     false
 
+### Backend commands
+
+Here are the commands specific to the s3 backend.
+
+Run them with
+
+    rclone backend COMMAND remote:
+
+The help below will explain what arguments each command takes.
+
+See [the "rclone backend" command](https://rclone.org/commands/rclone_backend/) for more
+info on how to pass options and arguments.
+
+These can be run on a running backend using the rc command
+[backend/command](https://rclone.org/rc/#backend/command).
+
+#### restore
+
+Restore objects from GLACIER to normal storage
+
+    rclone backend restore remote: [options] [<arguments>+]
+
+This command can be used to restore one or more objects from GLACIER
+to normal storage.
+
+Usage Examples:
+
+    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]
+
+This flag also obeys the filters. Test first with -i/--interactive or --dry-run flags
+
+    rclone -i backend restore --include "*.txt" s3:bucket/path -o priority=Standard
+
+All the objects shown will be marked for restore, then
+
+    rclone backend restore --include "*.txt" s3:bucket/path -o priority=Standard
+
+It returns a list of status dictionaries with Remote and Status
+keys. The Status will be OK if it was successfull or an error message
+if not.
+
+    [
+        {
+            "Status": "OK",
+            "Path": "test.txt"
+        },
+        {
+            "Status": "OK",
+            "Path": "test/file4.txt"
+        }
+    ]
+
+
+
+Options:
+
+- "description": The optional description for the job.
+- "lifetime": Lifetime of the active copy in days
+- "priority": Priority of restore: Standard|Expedited|Bulk
+
+#### list-multipart-uploads
+
+List the unfinished multipart uploads
+
+    rclone backend list-multipart-uploads remote: [options] [<arguments>+]
+
+This command lists the unfinished multipart uploads in JSON format.
+
+    rclone backend list-multipart s3:bucket/path/to/object
+
+It returns a dictionary of buckets with values as lists of unfinished
+multipart uploads.
+
+You can call it with no bucket in which case it lists all bucket, with
+a bucket or with a bucket and path.
+
+    {
+      "rclone": [
+        {
+          "Initiated": "2020-06-26T14:20:36Z",
+          "Initiator": {
+            "DisplayName": "XXX",
+            "ID": "arn:aws:iam::XXX:user/XXX"
+          },
+          "Key": "KEY",
+          "Owner": {
+            "DisplayName": null,
+            "ID": "XXX"
+          },
+          "StorageClass": "STANDARD",
+          "UploadId": "XXX"
+        }
+      ],
+      "rclone-1000files": [],
+      "rclone-dst": []
+    }
+
+
+
+#### cleanup
+
+Remove unfinished multipart uploads.
+
+    rclone backend cleanup remote: [options] [<arguments>+]
+
+This command removes unfinished multipart uploads of age greater than
+max-age which defaults to 24 hours.
+
+Note that you can use -i/--dry-run with this command to see what it
+would do.
+
+    rclone backend cleanup s3:bucket/path/to/object
+    rclone backend cleanup -o max-age=7w s3:bucket/path/to/object
+
+Durations are parsed as per the rest of rclone, 2h, 7d, 7w etc.
+
+
+Options:
+
+- "max-age": Max age of upload to delete
+
 
 
 ### Anonymous access to public buckets ###
@@ -12222,6 +13434,7 @@ Scaleway provides an S3 interface which can be configured for use with rclone li
 ```
 [scaleway]
 type = s3
+provider = Scaleway
 env_auth = false
 endpoint = s3.nl-ams.scw.cloud
 access_key_id = SCWXXXXXXXXXXXXXX
@@ -12229,7 +13442,6 @@ secret_access_key = 1111111-2222-3333-44444-55555555555555
 region = nl-ams
 location_constraint =
 acl = private
-force_path_style = false
 server_side_encryption =
 storage_class =
 ```
@@ -12530,7 +13742,7 @@ List the contents of a bucket
 Sync `/home/local/directory` to the remote bucket, deleting any
 excess files in the bucket.
 
-    rclone sync /home/local/directory remote:bucket
+    rclone sync -i /home/local/directory remote:bucket
 
 ### Application Keys ###
 
@@ -12577,6 +13789,12 @@ the following characters are also replaced:
 Invalid UTF-8 bytes will also be [replaced](https://rclone.org/overview/#invalid-utf8),
 as they can't be used in JSON strings.
 
+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
+`--b2-encoding` flag below and remove the `BackSlash` from the
+string. This can be set in the config.
+
 ### SHA1 checksums ###
 
 The SHA1 checksums of the files are checked on upload and download and
@@ -12867,6 +14085,20 @@ This value should be set no larger than 4.657GiB (== 5GB).
 - Type:        SizeSuffix
 - Default:     200M
 
+#### --b2-copy-cutoff
+
+Cutoff for switching to multipart copy
+
+Any files larger than this that need to be server side copied will be
+copied in chunks of this size.
+
+The minimum is 0 and the maximum is 4.6GB.
+
+- Config:      copy_cutoff
+- Env Var:     RCLONE_B2_COPY_CUTOFF
+- Type:        SizeSuffix
+- Default:     4G
+
 #### --b2-chunk-size
 
 Upload chunk size. Must fit in memory.
@@ -12921,6 +14153,26 @@ The minimum value is 1 second. The maximum value is one week.
 - Type:        Duration
 - Default:     1w
 
+#### --b2-memory-pool-flush-time
+
+How often internal memory buffer pools will be flushed.
+Uploads which requires additional buffers (f.e multipart) will use memory pool for allocations.
+This option controls how often unused buffers will be removed from the pool.
+
+- Config:      memory_pool_flush_time
+- Env Var:     RCLONE_B2_MEMORY_POOL_FLUSH_TIME
+- Type:        Duration
+- Default:     1m0s
+
+#### --b2-memory-pool-use-mmap
+
+Whether to use mmap buffers in internal memory pool.
+
+- Config:      memory_pool_use_mmap
+- Env Var:     RCLONE_B2_MEMORY_POOL_USE_MMAP
+- Type:        bool
+- Default:     false
+
 #### --b2-encoding
 
 This sets the encoding for the backend.
@@ -12972,9 +14224,18 @@ client_secret>
 Box App config.json location
 Leave blank normally.
 Enter a string value. Press Enter for the default ("").
-config_json>
-'enterprise' or 'user' depending on the type of token being requested.
+box_config_file>
+Box App Primary Access Token
+Leave blank normally.
+Enter a string value. Press Enter for the default ("").
+access_token>
+
 Enter a string value. Press Enter for the default ("user").
+Choose a number from below, or type in your own value
+ 1 / Rclone should act on behalf of a user
+   \ "user"
+ 2 / Rclone should act on behalf of a service account
+   \ "enterprise"
 box_sub_type>
 Remote config
 Use auto config?
@@ -13157,6 +14418,12 @@ normally 8MB so increasing `--transfers` will increase memory use.
 Depending on the enterprise settings for your user, the item will
 either be actually deleted from Box or moved to the trash.
 
+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.
+
 ### Root folder ID ###
 
 You can set the `root_folder_id` for rclone.  This is the directory
@@ -13186,7 +14453,7 @@ Here are the standard options specific to box (Box).
 
 #### --box-client-id
 
-Box App Client Id.
+OAuth Client Id
 Leave blank normally.
 
 - Config:      client_id
@@ -13196,7 +14463,7 @@ Leave blank normally.
 
 #### --box-client-secret
 
-Box App Client Secret
+OAuth Client Secret
 Leave blank normally.
 
 - Config:      client_secret
@@ -13209,11 +14476,24 @@ Leave blank normally.
 Box App config.json location
 Leave blank normally.
 
+Leading `~` will be expanded in the file name as will environment variables such as `${RCLONE_CONFIG_DIR}`.
+
+
 - Config:      box_config_file
 - Env Var:     RCLONE_BOX_BOX_CONFIG_FILE
 - Type:        string
 - Default:     ""
 
+#### --box-access-token
+
+Box App Primary Access Token
+Leave blank normally.
+
+- Config:      access_token
+- Env Var:     RCLONE_BOX_ACCESS_TOKEN
+- Type:        string
+- Default:     ""
+
 #### --box-box-sub-type
 
 
@@ -13232,6 +14512,35 @@ Leave blank normally.
 
 Here are the advanced options specific to box (Box).
 
+#### --box-token
+
+OAuth Access Token as a JSON blob.
+
+- Config:      token
+- Env Var:     RCLONE_BOX_TOKEN
+- Type:        string
+- Default:     ""
+
+#### --box-auth-url
+
+Auth server URL.
+Leave blank to use the provider defaults.
+
+- Config:      auth_url
+- Env Var:     RCLONE_BOX_AUTH_URL
+- Type:        string
+- Default:     ""
+
+#### --box-token-url
+
+Token server url.
+Leave blank to use the provider defaults.
+
+- Config:      token_url
+- Env Var:     RCLONE_BOX_TOKEN_URL
+- Type:        string
+- Default:     ""
+
 #### --box-root-folder-id
 
 Fill in for rclone to use a non root folder as its starting point.
@@ -13622,6 +14931,8 @@ The username of the Plex user
 
 The password of the Plex user
 
+**NB** Input to this must be obscured - see [rclone obscure](https://rclone.org/commands/rclone_obscure/).
+
 - Config:      plex_password
 - Env Var:     RCLONE_CACHE_PLEX_PASSWORD
 - Type:        string
@@ -14166,7 +15477,7 @@ chunk naming scheme is to:
 - Create another directory (most probably on the same cloud storage)
   and configure a new remote with desired metadata format,
   hash type, chunk naming etc.
-- Now run `rclone sync oldchunks: newchunks:` and all your data
+- Now run `rclone sync -i oldchunks: newchunks:` and all your data
   will be transparently converted in transfer.
   This may take some time, yet chunker will try server-side
   copy if possible.
@@ -14880,6 +16191,8 @@ NB If filename_encryption is "off" then this option will do nothing.
 
 Password or pass phrase for encryption.
 
+**NB** Input to this must be obscured - see [rclone obscure](https://rclone.org/commands/rclone_obscure/).
+
 - Config:      password
 - Env Var:     RCLONE_CRYPT_PASSWORD
 - Type:        string
@@ -14890,6 +16203,8 @@ Password or pass phrase for encryption.
 Password or pass phrase for salt. Optional but recommended.
 Should be different to the previous password.
 
+**NB** Input to this must be obscured - see [rclone obscure](https://rclone.org/commands/rclone_obscure/).
+
 - Config:      password2
 - Env Var:     RCLONE_CRYPT_PASSWORD2
 - Type:        string
@@ -14899,6 +16214,24 @@ Should be different to the previous password.
 
 Here are the advanced options specific to crypt (Encrypt/Decrypt a remote).
 
+#### --crypt-server-side-across-configs
+
+Allow server side operations (eg copy) to work across different crypt configs.
+
+Normally this option is not what you want, but if you have two crypts
+pointing to the same backend you can use it.
+
+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.
+
+- Config:      server_side_across_configs
+- Env Var:     RCLONE_CRYPT_SERVER_SIDE_ACROSS_CONFIGS
+- Type:        bool
+- Default:     false
+
 #### --crypt-show-mapping
 
 For all files listed show how the names encrypt.
@@ -14985,7 +16318,7 @@ as `eremote:`.
 
 To sync the two remotes you would do
 
-    rclone sync remote:crypt remote2:crypt
+    rclone sync -i remote:crypt remote2:crypt
 
 And to check the integrity you would do
 
@@ -15214,7 +16547,7 @@ Here are the standard options specific to dropbox (Dropbox).
 
 #### --dropbox-client-id
 
-Dropbox App Client Id
+OAuth Client Id
 Leave blank normally.
 
 - Config:      client_id
@@ -15224,7 +16557,7 @@ Leave blank normally.
 
 #### --dropbox-client-secret
 
-Dropbox App Client Secret
+OAuth Client Secret
 Leave blank normally.
 
 - Config:      client_secret
@@ -15236,6 +16569,35 @@ Leave blank normally.
 
 Here are the advanced options specific to dropbox (Dropbox).
 
+#### --dropbox-token
+
+OAuth Access Token as a JSON blob.
+
+- Config:      token
+- Env Var:     RCLONE_DROPBOX_TOKEN
+- Type:        string
+- Default:     ""
+
+#### --dropbox-auth-url
+
+Auth server URL.
+Leave blank to use the provider defaults.
+
+- Config:      auth_url
+- Env Var:     RCLONE_DROPBOX_AUTH_URL
+- Type:        string
+- Default:     ""
+
+#### --dropbox-token-url
+
+Token server url.
+Leave blank to use the provider defaults.
+
+- Config:      token_url
+- Env Var:     RCLONE_DROPBOX_TOKEN_URL
+- Type:        string
+- Default:     ""
+
 #### --dropbox-chunk-size
 
 Upload chunk size. (< 150M).
@@ -15285,6 +16647,12 @@ of this document](https://www.dropbox.com/en/help/145).  Rclone will
 issue an error message `File name disallowed - not uploading` if it
 attempts to upload one of those file names, but the sync won't fail.
 
+Some errors may occur if you try to sync copyright-protected files
+because Dropbox has its own [copyright detector](https://techcrunch.com/2014/03/30/how-dropbox-knows-when-youre-sharing-copyrighted-stuff-without-actually-looking-at-your-stuff/) that
+prevents this sort of file being downloaded. This will return the error `ERROR :
+/path/to/your/file: Failed to copy: failed to open source object:
+path/restricted_content/.`
+
 If you have more than 10,000 files in a directory then `rclone purge
 dropbox:dir` will return the error `Failed to purge: There are too
 many files involved in this operation`.  As a work-around do an
@@ -15318,6 +16686,10 @@ FTP is the File Transfer Protocol. FTP support is provided using the
 [github.com/jlaffaye/ftp](https://godoc.org/github.com/jlaffaye/ftp)
 package.
 
+Paths are specified as `remote:path`. If the path does not begin with
+a `/` it is relative to the home directory of the user.  An empty path
+`remote:` refers to the user's home directory.
+
 Here is an example of making an FTP configuration.  First run
 
     rclone config
@@ -15369,6 +16741,9 @@ password:
 Use FTP over TLS (Implicit)
 Enter a boolean value (true or false). Press Enter for the default ("false").
 tls> 
+Use FTP over TLS (Explicit)
+Enter a boolean value (true or false). Press Enter for the default ("false").
+explicit_tls> 
 Remote config
 --------------------
 [remote]
@@ -15399,7 +16774,7 @@ List the contents of a directory
 Sync `/home/local/directory` to the remote directory, deleting any
 excess files in the directory.
 
-    rclone sync /home/local/directory remote:directory
+    rclone sync -i /home/local/directory remote:directory
 
 ### Modified time ###
 
@@ -15480,6 +16855,8 @@ FTP port, leave blank to use default (21)
 
 FTP password
 
+**NB** Input to this must be obscured - see [rclone obscure](https://rclone.org/commands/rclone_obscure/).
+
 - Config:      pass
 - Env Var:     RCLONE_FTP_PASS
 - Type:        string
@@ -15487,13 +16864,29 @@ FTP password
 
 #### --ftp-tls
 
-Use FTP over TLS (Implicit)
+Use FTPS over TLS (Implicit)
+When using implicit FTP over TLS the client will connect using TLS
+right from the start, which in turn breaks the compatibility with
+non-TLS-aware servers. This is usually served over port 990 rather
+than port 21. Cannot be used in combination with explicit FTP.
 
 - Config:      tls
 - Env Var:     RCLONE_FTP_TLS
 - Type:        bool
 - Default:     false
 
+#### --ftp-explicit-tls
+
+Use FTP over TLS (Explicit)
+When using explicit FTP over TLS the client explicitly request
+security from the server in order to upgrade a plain text connection
+to an encrypted one. Cannot be used in combination with implicit FTP.
+
+- Config:      explicit_tls
+- Env Var:     RCLONE_FTP_EXPLICIT_TLS
+- Type:        bool
+- Default:     false
+
 ### Advanced Options
 
 Here are the advanced options specific to ftp (FTP Connection).
@@ -15540,8 +16933,9 @@ See: the [encoding section in the overview](https://rclone.org/overview/#encodin
 
 ### Limitations ###
 
-Note that since FTP isn't HTTP based the following flags don't work
-with it: `--dump-headers`, `--dump-bodies`, `--dump-auth`
+Note that FTP does have its own implementation of : `--dump headers`,
+`--dump bodies`, `--dump auth` for debugging which isn't the same as
+the HTTP based backends - it has less fine grained control.
 
 Note that `--timeout` isn't supported (but `--contimeout` is).
 
@@ -15552,9 +16946,6 @@ FTP could support server side move but doesn't yet.
 Note that the ftp backend does not support the `ftp_proxy` environment
 variable yet.
 
-Note that while implicit FTP over TLS is supported,
-explicit FTP over TLS is not.
-
  Google Cloud Storage
 -------------------------------------------------
 
@@ -15717,7 +17108,7 @@ List the contents of a bucket
 Sync `/home/local/directory` to the remote bucket, deleting any excess
 files in the bucket.
 
-    rclone sync /home/local/directory remote:bucket
+    rclone sync -i /home/local/directory remote:bucket
 
 ### Service Account support ###
 
@@ -15746,6 +17137,13 @@ the rclone config file, you can set `service_account_credentials` with
 the actual contents of the file instead, or set the equivalent
 environment variable.
 
+### Anonymous Access ###
+
+For downloads of objects that permit public access you can configure rclone
+to use anonymous access by setting `anonymous` to `true`.
+With unauthorized access you can't write or create files but only read or list
+those buckets and objects that have public read access.
+
 ### Application Default Credentials ###
 
 If no other source of credentials is provided, rclone will fall back
@@ -15809,7 +17207,7 @@ Here are the standard options specific to google cloud storage (Google Cloud Sto
 
 #### --gcs-client-id
 
-Google Application Client Id
+OAuth Client Id
 Leave blank normally.
 
 - Config:      client_id
@@ -15819,7 +17217,7 @@ Leave blank normally.
 
 #### --gcs-client-secret
 
-Google Application Client Secret
+OAuth Client Secret
 Leave blank normally.
 
 - Config:      client_secret
@@ -15843,6 +17241,9 @@ Service Account Credentials JSON file path
 Leave blank normally.
 Needed only if you want use SA instead of interactive login.
 
+Leading `~` will be expanded in the file name as will environment variables such as `${RCLONE_CONFIG_DIR}`.
+
+
 - Config:      service_account_file
 - Env Var:     RCLONE_GCS_SERVICE_ACCOUNT_FILE
 - Type:        string
@@ -15859,6 +17260,16 @@ Needed only if you want use SA instead of interactive login.
 - Type:        string
 - Default:     ""
 
+#### --gcs-anonymous
+
+Access public buckets and objects without credentials
+Set to 'true' if you just want to download files and don't configure credentials.
+
+- Config:      anonymous
+- Env Var:     RCLONE_GCS_ANONYMOUS
+- Type:        bool
+- Default:     false
+
 #### --gcs-object-acl
 
 Access Control List for new objects.
@@ -16000,6 +17411,35 @@ The storage class to use when storing objects in Google Cloud Storage.
 
 Here are the advanced options specific to google cloud storage (Google Cloud Storage (this is not Google Drive)).
 
+#### --gcs-token
+
+OAuth Access Token as a JSON blob.
+
+- Config:      token
+- Env Var:     RCLONE_GCS_TOKEN
+- Type:        string
+- Default:     ""
+
+#### --gcs-auth-url
+
+Auth server URL.
+Leave blank to use the provider defaults.
+
+- Config:      auth_url
+- Env Var:     RCLONE_GCS_AUTH_URL
+- Type:        string
+- Default:     ""
+
+#### --gcs-token-url
+
+Token server url.
+Leave blank to use the provider defaults.
+
+- Config:      token_url
+- Env Var:     RCLONE_GCS_TOKEN_URL
+- Type:        string
+- Default:     ""
+
 #### --gcs-encoding
 
 This sets the encoding for the backend.
@@ -16283,6 +17723,12 @@ the magic, pretending to be user foo.
     - `gdrive:backup` - use the remote called gdrive, work in
 the folder named backup.
 
+Note: in case you configured a specific root folder on gdrive and rclone is unable to access the contents of that folder when using `--drive-impersonate`, 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 `--drive-impersonate` option, like this:
+        `rclone -v foo@example.com lsf gdrive:backup`
+
+
 ### Team drives ###
 
 If you want to configure the remote to point to a Google Team Drive
@@ -16426,7 +17872,7 @@ For shortcuts pointing to folders:
 - When deleting with `rclone rmdir` or `rclone purge` the shortcut is deleted not the linked folder.
 - **NB** When deleting with `rclone remove` or `rclone mount` the contents of the linked folder will be deleted.
 
-It isn't currently possible to create shortcuts with rclone.
+The [rclone backend](https://rclone.org/commands/rclone_backend/) command can be used to create shortcuts.  
 
 Shortcuts can be completely ignored with the `--drive-skip-shortcuts` flag
 or the corresponding `skip_shortcuts` configuration setting.
@@ -16551,10 +17997,8 @@ Here are the standard options specific to drive (Google Drive).
 
 #### --drive-client-id
 
-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.
+OAuth Client Id
+Leave blank normally.
 
 - Config:      client_id
 - Env Var:     RCLONE_DRIVE_CLIENT_ID
@@ -16563,8 +18007,8 @@ If you leave this blank, it will use an internal key which is low performance.
 
 #### --drive-client-secret
 
-Google Application Client Secret
-Setting your own is recommended.
+OAuth Client Secret
+Leave blank normally.
 
 - Config:      client_secret
 - Env Var:     RCLONE_DRIVE_CLIENT_SECRET
@@ -16603,9 +18047,6 @@ Leave blank normally.
 Fill in to access "Computers" folders (see docs), or for rclone to use
 a non root folder as its starting point.
 
-Note that if this is blank, the first time rclone runs it will fill it
-in with the ID of the root folder.
-
 
 - Config:      root_folder_id
 - Env Var:     RCLONE_DRIVE_ROOT_FOLDER_ID
@@ -16618,15 +18059,56 @@ Service Account Credentials JSON file path
 Leave blank normally.
 Needed only if you want use SA instead of interactive login.
 
+Leading `~` will be expanded in the file name as will environment variables such as `${RCLONE_CONFIG_DIR}`.
+
+
 - Config:      service_account_file
 - Env Var:     RCLONE_DRIVE_SERVICE_ACCOUNT_FILE
 - Type:        string
 - Default:     ""
 
+#### --drive-alternate-export
+
+Deprecated: no longer needed
+
+- Config:      alternate_export
+- Env Var:     RCLONE_DRIVE_ALTERNATE_EXPORT
+- Type:        bool
+- Default:     false
+
 ### Advanced Options
 
 Here are the advanced options specific to drive (Google Drive).
 
+#### --drive-token
+
+OAuth Access Token as a JSON blob.
+
+- Config:      token
+- Env Var:     RCLONE_DRIVE_TOKEN
+- Type:        string
+- Default:     ""
+
+#### --drive-auth-url
+
+Auth server URL.
+Leave blank to use the provider defaults.
+
+- Config:      auth_url
+- Env Var:     RCLONE_DRIVE_AUTH_URL
+- Type:        string
+- Default:     ""
+
+#### --drive-token-url
+
+Token server url.
+Leave blank to use the provider defaults.
+
+- Config:      token_url
+- Env Var:     RCLONE_DRIVE_TOKEN_URL
+- Type:        string
+- Default:     ""
+
 #### --drive-service-account-credentials
 
 Service Account Credentials JSON blob
@@ -16723,6 +18205,15 @@ This will show trashed files in their original directory structure.
 - Type:        bool
 - Default:     false
 
+#### --drive-starred-only
+
+Only show files that are starred.
+
+- Config:      starred_only
+- Env Var:     RCLONE_DRIVE_STARRED_ONLY
+- Type:        bool
+- Default:     false
+
 #### --drive-formats
 
 Deprecated: see export_formats
@@ -16817,24 +18308,6 @@ Impersonate this user when using a service account.
 - Type:        string
 - Default:     ""
 
-#### --drive-alternate-export
-
-Use alternate export URLs for google documents export.,
-
-If this option is set this instructs rclone to use an alternate set of
-export URLs for drive documents.  Users have reported that the
-official export URLs can't export large documents, whereas these
-unofficial ones can.
-
-See rclone issue [#2243](https://github.com/rclone/rclone/issues/2243) for background,
-[this google drive issue](https://issuetracker.google.com/issues/36761333) and
-[this helpful post](https://www.labnol.org/internet/direct-links-for-google-drive/28356/).
-
-- Config:      alternate_export
-- Env Var:     RCLONE_DRIVE_ALTERNATE_EXPORT
-- Type:        bool
-- Default:     false
-
 #### --drive-upload-cutoff
 
 Cutoff for switching to chunked upload
@@ -17091,6 +18564,63 @@ Options:
 
 - "target": optional target remote for the shortcut destination
 
+#### drives
+
+List the shared drives available to this account
+
+    rclone backend drives remote: [options] [<arguments>+]
+
+This command lists the shared drives (teamdrives) available to this
+account.
+
+Usage:
+
+    rclone backend drives drive:
+
+This will return a JSON list of objects like this
+
+    [
+        {
+            "id": "0ABCDEF-01234567890",
+            "kind": "drive#teamDrive",
+            "name": "My Drive"
+        },
+        {
+            "id": "0ABCDEFabcdefghijkl",
+            "kind": "drive#teamDrive",
+            "name": "Test Drive"
+        }
+    ]
+
+
+
+#### untrash
+
+Untrash files and directories
+
+    rclone backend untrash remote: [options] [<arguments>+]
+
+This command untrashes all the files and directories in the directory
+passed in recursively.
+
+Usage:
+
+This takes an optional directory to trash which make this easier to
+use via the API.
+
+    rclone backend untrash drive:directory
+    rclone backend -i untrash drive:directory subdir
+
+Use the -i flag to see what would be restored before restoring it.
+
+Result:
+
+    {
+        "Untrashed": 17,
+        "Errors": 0
+    }
+
+
 
 
 ### Limitations ###
@@ -17208,6 +18738,13 @@ the remote configuration, it's not such a big deal).
 
 (Thanks to @balazer on github for these instructions.)
 
+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
+[Python Quickstart](https://developers.google.com/drive/api/v3/quickstart/python) 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.
+
  Google Photos
 -------------------------------------------------
 
@@ -17317,7 +18854,7 @@ List the contents of an album
 Sync `/home/local/images` to the Google Photos, removing any excess
 files in the album.
 
-    rclone sync /home/local/image remote:album/newAlbum
+    rclone sync -i /home/local/image remote:album/newAlbum
 
 ## Layout
 
@@ -17520,7 +19057,7 @@ Here are the standard options specific to google photos (Google Photos).
 
 #### --gphotos-client-id
 
-Google Application Client Id
+OAuth Client Id
 Leave blank normally.
 
 - Config:      client_id
@@ -17530,7 +19067,7 @@ Leave blank normally.
 
 #### --gphotos-client-secret
 
-Google Application Client Secret
+OAuth Client Secret
 Leave blank normally.
 
 - Config:      client_secret
@@ -17554,6 +19091,35 @@ to your photos, otherwise rclone will request full access.
 
 Here are the advanced options specific to google photos (Google Photos).
 
+#### --gphotos-token
+
+OAuth Access Token as a JSON blob.
+
+- Config:      token
+- Env Var:     RCLONE_GPHOTOS_TOKEN
+- Type:        string
+- Default:     ""
+
+#### --gphotos-auth-url
+
+Auth server URL.
+Leave blank to use the provider defaults.
+
+- Config:      auth_url
+- Env Var:     RCLONE_GPHOTOS_AUTH_URL
+- Type:        string
+- Default:     ""
+
+#### --gphotos-token-url
+
+Token server url.
+Leave blank to use the provider defaults.
+
+- Config:      token_url
+- Env Var:     RCLONE_GPHOTOS_TOKEN_URL
+- Type:        string
+- Default:     ""
+
 #### --gphotos-read-size
 
 Set to read the size of media items.
@@ -17655,7 +19221,7 @@ List the contents of a directory
 
 Sync the remote `directory` to `/home/local/directory`, deleting any excess files.
 
-    rclone sync remote:directory /home/local/directory
+    rclone sync -i remote:directory /home/local/directory
 
 ### Read only ###
 
@@ -17873,7 +19439,7 @@ Here are the standard options specific to hubic (Hubic).
 
 #### --hubic-client-id
 
-Hubic Client Id
+OAuth Client Id
 Leave blank normally.
 
 - Config:      client_id
@@ -17883,7 +19449,7 @@ Leave blank normally.
 
 #### --hubic-client-secret
 
-Hubic Client Secret
+OAuth Client Secret
 Leave blank normally.
 
 - Config:      client_secret
@@ -17895,6 +19461,35 @@ Leave blank normally.
 
 Here are the advanced options specific to hubic (Hubic).
 
+#### --hubic-token
+
+OAuth Access Token as a JSON blob.
+
+- Config:      token
+- Env Var:     RCLONE_HUBIC_TOKEN
+- Type:        string
+- Default:     ""
+
+#### --hubic-auth-url
+
+Auth server URL.
+Leave blank to use the provider defaults.
+
+- Config:      auth_url
+- Env Var:     RCLONE_HUBIC_AUTH_URL
+- Type:        string
+- Default:     ""
+
+#### --hubic-token-url
+
+Token server url.
+Leave blank to use the provider defaults.
+
+- Config:      token_url
+- Env Var:     RCLONE_HUBIC_TOKEN_URL
+- Type:        string
+- Default:     ""
+
 #### --hubic-chunk-size
 
 Above this size files will be chunked into a _segments container.
@@ -17962,12 +19557,21 @@ Paths may be as deep as required, eg `remote:directory/subdirectory`.
 
 ## Setup
 
+### Default Setup
+
 To configure Jottacloud you will need to generate a personal security token in the Jottacloud web interface.
 You will the option to do in your [account security settings](https://www.jottacloud.com/web/secure)
 (for whitelabel version you need to find this page in its web interface).
 Note that the web interface may refer to this token as a JottaCli token.
 
-Here is an example of how to make a remote called `remote`.  First run:
+### Legacy Setup
+
+If you are using one of the whitelabel versions (Elgiganten, Com Hem Cloud) you may not have the option
+to generate a CLI token. In this case you'll have to use the legacy authentification. To to this select
+yes when the setup asks for legacy authentification and enter your username and password.
+The rest of the setup is identical to the default setup.
+
+Here is an example of how to make a remote called `remote` with the default setup.  First run:
 
     rclone config
 
@@ -17979,7 +19583,7 @@ n) New remote
 s) Set configuration password
 q) Quit config
 n/s/q> n
-name> jotta
+name> remote
 Type of storage to configure.
 Enter a string value. Press Enter for the default ("").
 Choose a number from below, or type in your own value
@@ -17995,6 +19599,11 @@ y) Yes
 n) No
 y/n> n
 Remote config
+Use legacy authentification?.
+This is only required for certain whitelabel versions of Jottacloud and not recommended for normal users.
+y) Yes
+n) No (default)
+y/n> n
 
 Generate a personal login token here: https://www.jottacloud.com/web/secure
 Login Token> <your token here>
@@ -18007,9 +19616,8 @@ y/n> y
 Please select the device to use. Normally this will be Jotta
 Choose a number from below, or type in an existing value
  1 > DESKTOP-3H31129
- 2 > fla1
- 3 > Jotta
-Devices> 3
+ 2 > Jotta
+Devices> 2
 Please select the mountpoint to user. Normally this will be Archive
 Choose a number from below, or type in an existing value
  1 > Archive
@@ -18020,7 +19628,6 @@ Mountpoints> 1
 --------------------
 [jotta]
 type = jottacloud
-user = 0xC4KE@gmail.com
 token = {........}
 device = Jotta
 mountpoint = Archive
@@ -18153,16 +19760,6 @@ Delete files permanently rather than putting them into the trash.
 - Type:        bool
 - Default:     false
 
-#### --jottacloud-unlink
-
-Remove existing public link to file/folder with link command rather than creating.
-Default is false, meaning link command will create or retrieve public link.
-
-- Config:      unlink
-- Env Var:     RCLONE_JOTTACLOUD_UNLINK
-- Type:        bool
-- Default:     false
-
 #### --jottacloud-upload-resume-limit
 
 Files bigger than this can be resumed if the upload fail's.
@@ -18312,6 +19909,8 @@ Your Koofr user name
 
 Your Koofr password for rclone (generate one at https://app.koofr.net/app/admin/preferences/password)
 
+**NB** Input to this must be obscured - see [rclone obscure](https://rclone.org/commands/rclone_obscure/).
+
 - Config:      password
 - Env Var:     RCLONE_KOOFR_PASSWORD
 - Type:        string
@@ -18469,7 +20068,7 @@ List the contents of a directory
 Sync `/home/local/directory` to the remote path, deleting any
 excess files in the path.
 
-    rclone sync /home/local/directory remote:directory
+    rclone sync -i /home/local/directory remote:directory
 
 ### Modified time ###
 
@@ -18544,6 +20143,8 @@ User name (usually email)
 
 Password
 
+**NB** Input to this must be obscured - see [rclone obscure](https://rclone.org/commands/rclone_obscure/).
+
 - Config:      pass
 - Env Var:     RCLONE_MAILRU_PASS
 - Type:        string
@@ -18842,6 +20443,8 @@ User name
 
 Password.
 
+**NB** Input to this must be obscured - see [rclone obscure](https://rclone.org/commands/rclone_obscure/).
+
 - Config:      pass
 - Env Var:     RCLONE_MEGA_PASS
 - Type:        string
@@ -19021,7 +20624,7 @@ List the contents of a container
 Sync `/home/local/directory` to the remote container, deleting any excess
 files in the container.
 
-    rclone sync /home/local/directory remote:container
+    rclone sync -i /home/local/directory remote:container
 
 ### --fast-list ###
 
@@ -19419,7 +21022,7 @@ requests.
 If you are having problems with them (E.g., seeing a lot of throttling), you can get your own
 Client ID and Key by following the steps below:
 
-1. Open https://portal.azure.com/#blade/Microsoft_AAD_RegisteredApps/ApplicationsListBlade, then click `New registration`.
+1. Open https://portal.azure.com/#blade/Microsoft_AAD_RegisteredApps/ApplicationsListBlade and then click `New registration`.
 2. Enter a name for your app, choose account type `Accounts in any organizational directory (Any Azure AD directory - Multitenant) and personal Microsoft accounts (e.g. Skype, Xbox)`, select `Web` in `Redirect URI` Enter `http://localhost:53682/` and click Register. Copy and keep the `Application (client) ID` under the app name for later use.
 3. Under `manage` select `Certificates & secrets`, click `New client secret`. Copy and keep that secret for later use.
 4. Under `manage` select `API permissions`, click `Add a permission` and select `Microsoft Graph` then select `delegated permissions`.
@@ -19491,7 +21094,7 @@ Here are the standard options specific to onedrive (Microsoft OneDrive).
 
 #### --onedrive-client-id
 
-Microsoft App Client Id
+OAuth Client Id
 Leave blank normally.
 
 - Config:      client_id
@@ -19501,7 +21104,7 @@ Leave blank normally.
 
 #### --onedrive-client-secret
 
-Microsoft App Client Secret
+OAuth Client Secret
 Leave blank normally.
 
 - Config:      client_secret
@@ -19513,6 +21116,35 @@ Leave blank normally.
 
 Here are the advanced options specific to onedrive (Microsoft OneDrive).
 
+#### --onedrive-token
+
+OAuth Access Token as a JSON blob.
+
+- Config:      token
+- Env Var:     RCLONE_ONEDRIVE_TOKEN
+- Type:        string
+- Default:     ""
+
+#### --onedrive-auth-url
+
+Auth server URL.
+Leave blank to use the provider defaults.
+
+- Config:      auth_url
+- Env Var:     RCLONE_ONEDRIVE_AUTH_URL
+- Type:        string
+- Default:     ""
+
+#### --onedrive-token-url
+
+Token server url.
+Leave blank to use the provider defaults.
+
+- Config:      token_url
+- Env Var:     RCLONE_ONEDRIVE_TOKEN_URL
+- Type:        string
+- Default:     ""
+
 #### --onedrive-chunk-size
 
 Chunk size to upload files with - must be multiple of 320k (327,680 bytes).
@@ -19573,6 +21205,27 @@ configurations.
 - Type:        bool
 - Default:     false
 
+#### --onedrive-no-versions
+
+Remove all versions on modifying operations
+
+Onedrive for business creates versions when rclone uploads new files
+overwriting an existing one and when it sets the modification time.
+
+These versions take up space out of the quota.
+
+This flag checks for versions after file upload and setting
+modification time and removes all but the last version.
+
+**NB** Onedrive personal can't currently delete versions so don't use
+this flag there.
+
+
+- Config:      no_versions
+- Env Var:     RCLONE_ONEDRIVE_NO_VERSIONS
+- Type:        bool
+- Default:     false
+
 #### --onedrive-encoding
 
 This sets the encoding for the backend.
@@ -19586,7 +21239,12 @@ See: the [encoding section in the overview](https://rclone.org/overview/#encodin
 
 
 
-### Limitations ###
+### Limitations
+
+If you don't use rclone for 90 days the refresh token will
+expire. This will result in authorization problems. This is easy to
+fix by running the `rclone config reconnect remote:` command to get a
+new token and refresh token.
 
 #### Naming ####
 
@@ -19601,9 +21259,7 @@ in it will be mapped to `？` instead.
 
 #### File sizes ####
 
-The largest allowed file sizes are 15GB for OneDrive for Business and 100GB for OneDrive Personal (Updated 19 May 2020).
-Source:
-https://support.office.com/en-us/article/upload-photos-and-files-to-onedrive-b00ad3fe-6643-4b16-9212-de00ef02b586
+The largest allowed file size is 100GB for both OneDrive Personal and OneDrive for Business [(Updated 17 June 2020)](https://support.microsoft.com/en-us/office/invalid-file-names-and-file-types-in-onedrive-and-sharepoint-64883a5d-228e-48f5-b3d2-eb39e07630fa?ui=en-us&rs=en-us&ad=us#individualfilesize).
 
 #### Path length ####
 
@@ -19618,24 +21274,45 @@ list files: UnknownError:`.  See
 
 An official document about the limitations for different types of OneDrive can be found [here](https://support.office.com/en-us/article/invalid-file-names-and-file-types-in-onedrive-onedrive-for-business-and-sharepoint-64883a5d-228e-48f5-b3d2-eb39e07630fa).
 
-### Versioning issue ###
+### Versions
 
-Every change in OneDrive causes the service to create a new version.
-This counts against a users quota.
-For example changing the modification time of a file creates a second
-version, so the file is using twice the space.
+Every change in a file OneDrive causes the service to create a new
+version of the the file.  This counts against a users quota.  For
+example changing the modification time of a file creates a second
+version, so the file apparently uses twice the space.
 
-The `copy` is the only rclone command affected by this as we copy
-the file and then afterwards set the modification time to match the
-source file.
+For example the `copy` command is affected by this as rclone copies
+the file and then afterwards sets the modification time to match the
+source file which uses another version.
 
-**Note**: Starting October 2018, users will no longer be able to disable versioning by default. This is because Microsoft has brought an [update](https://techcommunity.microsoft.com/t5/Microsoft-OneDrive-Blog/New-Updates-to-OneDrive-and-SharePoint-Team-Site-Versioning/ba-p/204390) to the mechanism. To change this new default setting, a PowerShell command is required to be run by a SharePoint admin. If you are an admin, you can run these commands in PowerShell to change that setting:
+You can use the `rclone cleanup` command (see below) to remove all old
+versions.
+
+Or you can set the `no_versions` parameter to `true` and rclone will
+remove versions after operations which create new versions. This takes
+extra transactions so only enable it if you need it.
+
+**Note** At the time of writing Onedrive Personal creates versions
+(but not for setting the modification time) but the API for removing
+them returns "API not found" so cleanup and `no_versions` should not
+be used on Onedrive Personal.
+
+### Disabling versioning
+
+Starting October 2018, users will no longer be able to
+disable versioning by default. This is because Microsoft has brought
+an
+[update](https://techcommunity.microsoft.com/t5/Microsoft-OneDrive-Blog/New-Updates-to-OneDrive-and-SharePoint-Team-Site-Versioning/ba-p/204390)
+to the mechanism. To change this new default setting, a PowerShell
+command is required to be run by a SharePoint admin. If you are an
+admin, you can run these commands in PowerShell to change that
+setting:
 
 1. `Install-Module -Name Microsoft.Online.SharePoint.PowerShell` (in case you haven't installed this already)
-1. `Import-Module Microsoft.Online.SharePoint.PowerShell -DisableNameChecking`
-1. `Connect-SPOService -Url https://YOURSITE-admin.sharepoint.com -Credential YOU@YOURSITE.COM` (replacing `YOURSITE`, `YOU`, `YOURSITE.COM` with the actual values; this will prompt for your credentials)
-1. `Set-SPOTenant -EnableMinimumVersionRequirement $False`
-1. `Disconnect-SPOService` (to disconnect from the server)
+2. `Import-Module Microsoft.Online.SharePoint.PowerShell -DisableNameChecking`
+3. `Connect-SPOService -Url https://YOURSITE-admin.sharepoint.com -Credential YOU@YOURSITE.COM` (replacing `YOURSITE`, `YOU`, `YOURSITE.COM` with the actual values; this will prompt for your credentials)
+4. `Set-SPOTenant -EnableMinimumVersionRequirement $False`
+5. `Disconnect-SPOService` (to disconnect from the server)
 
 *Below are the steps for normal users to disable versioning. If you don't see the "No Versioning" option, make sure the above requirements are met.*  
 
@@ -19653,6 +21330,20 @@ Note: This will disable the creation of new file versions, but will not remove a
 8. Use rclone to upload or modify files. (I also use the --no-update-modtime flag)
 9. Restore the versioning settings after using rclone. (Optional)
 
+### Cleanup
+
+OneDrive supports `rclone cleanup` which causes rclone to look through
+every file under the path supplied and delete all version but the
+current version. Because this involves traversing all the files, then
+querying each file for versions it can be quite slow. Rclone does
+`--checkers` tests in parallel. The command also supports `-i` which
+is a great way to see what it would do.
+
+    rclone cleanup -i remote:path/subdir # interactively remove all old version for path/subdir
+    rclone cleanup remote:path/subdir    # unconditionally remove all old version for path/subdir
+
+**NB** Onedrive personal can't currently delete versions
+
 ### Troubleshooting ###
 
 #### Unexpected file size/hash differences on Sharepoint ####
@@ -19661,13 +21352,24 @@ It is a
 [known](https://github.com/OneDrive/onedrive-api-docs/issues/935#issuecomment-441741631)
 issue that Sharepoint (not OneDrive or OneDrive for Business) silently modifies
 uploaded files, mainly Office files (.docx, .xlsx, etc.), causing file size and
-hash checks to fail. To use rclone with such affected files on Sharepoint, you
+hash checks to fail. There are also other situations that will cause OneDrive to 
+report inconsistent file sizes. To use rclone with such
+affected files on Sharepoint, you
 may disable these checks with the following command line arguments:
 
 ```
 --ignore-checksum --ignore-size
 ```
 
+Alternatively, if you have write access to the OneDrive files, it may be possible
+to fix this problem for certain files, by attempting the steps below.
+Open the web interface for [OneDrive](https://onedrive.live.com) and find the 
+affected files (which will be in the error messages/log for rclone). Simply click on
+each of these files, causing OneDrive to open them on the web. This will cause each 
+file to be converted in place to a format that is functionally equivalent
+but which will no longer trigger the size discrepancy. Once all problematic files
+are converted you will no longer need the ignore options above.
+
 #### Replacing/deleting existing files on Sharepoint gets "item not found" ####
 
 It is a [known](https://github.com/OneDrive/onedrive-api-docs/issues/1068) issue
@@ -19818,6 +21520,8 @@ Username
 
 Password.
 
+**NB** Input to this must be obscured - see [rclone obscure](https://rclone.org/commands/rclone_obscure/).
+
 - Config:      password
 - Env Var:     RCLONE_OPENDRIVE_PASSWORD
 - Type:        string
@@ -19950,7 +21654,7 @@ List the contents of a bucket
 Sync `/home/local/directory` to the remote bucket, deleting any excess
 files in the bucket.
 
-    rclone sync /home/local/directory remote:bucket
+    rclone sync -i /home/local/directory remote:bucket
 
 ### --fast-list ###
 
@@ -20273,7 +21977,7 @@ List the contents of a container
 Sync `/home/local/directory` to the remote container, deleting any
 excess files in the container.
 
-    rclone sync /home/local/directory remote:container
+    rclone sync -i /home/local/directory remote:container
 
 ### Configuration from an OpenStack credentials file ###
 
@@ -20795,7 +22499,7 @@ Here are the standard options specific to pcloud (Pcloud).
 
 #### --pcloud-client-id
 
-Pcloud App Client Id
+OAuth Client Id
 Leave blank normally.
 
 - Config:      client_id
@@ -20805,7 +22509,7 @@ Leave blank normally.
 
 #### --pcloud-client-secret
 
-Pcloud App Client Secret
+OAuth Client Secret
 Leave blank normally.
 
 - Config:      client_secret
@@ -20817,6 +22521,35 @@ Leave blank normally.
 
 Here are the advanced options specific to pcloud (Pcloud).
 
+#### --pcloud-token
+
+OAuth Access Token as a JSON blob.
+
+- Config:      token
+- Env Var:     RCLONE_PCLOUD_TOKEN
+- Type:        string
+- Default:     ""
+
+#### --pcloud-auth-url
+
+Auth server URL.
+Leave blank to use the provider defaults.
+
+- Config:      auth_url
+- Env Var:     RCLONE_PCLOUD_AUTH_URL
+- Type:        string
+- Default:     ""
+
+#### --pcloud-token-url
+
+Token server url.
+Leave blank to use the provider defaults.
+
+- Config:      token_url
+- Env Var:     RCLONE_PCLOUD_TOKEN_URL
+- Type:        string
+- Default:     ""
+
 #### --pcloud-encoding
 
 This sets the encoding for the backend.
@@ -20837,6 +22570,25 @@ Fill in for rclone to use a non root folder as its starting point.
 - Type:        string
 - Default:     "d0"
 
+#### --pcloud-hostname
+
+Hostname to connect to.
+
+This is normally set when rclone initially does the oauth connection,
+however you will need to set it by hand if you are using remote config
+with rclone authorize.
+
+
+- Config:      hostname
+- Env Var:     RCLONE_PCLOUD_HOSTNAME
+- Type:        string
+- Default:     "api.pcloud.com"
+- Examples:
+    - "api.pcloud.com"
+        - Original/US region
+    - "eapi.pcloud.com"
+        - EU region
+
 
 
  premiumize.me
@@ -21212,7 +22964,7 @@ List the contents of a library
 Sync `/home/local/directory` to the remote library, deleting any
 excess files in the library.
 
-    rclone sync /home/local/directory seafile:library
+    rclone sync -i /home/local/directory seafile:library
 
 ### Configuration in library mode ###
 
@@ -21308,7 +23060,7 @@ List the contents of a directory
 Sync `/home/local/directory` to the remote library, deleting any
 excess files in the library.
 
-    rclone sync /home/local/directory seafile:
+    rclone sync -i /home/local/directory seafile:
 
 
 ### --fast-list ###
@@ -21394,6 +23146,8 @@ User name (usually email address)
 
 Password
 
+**NB** Input to this must be obscured - see [rclone obscure](https://rclone.org/commands/rclone_obscure/).
+
 - Config:      pass
 - Env Var:     RCLONE_SEAFILE_PASS
 - Type:        string
@@ -21421,6 +23175,8 @@ Name of the library. Leave blank to access all non-encrypted libraries.
 
 Library password (for encrypted libraries only). Leave blank if you pass it through the command line.
 
+**NB** Input to this must be obscured - see [rclone obscure](https://rclone.org/commands/rclone_obscure/).
+
 - Config:      library_key
 - Env Var:     RCLONE_SEAFILE_LIBRARY_KEY
 - Type:        string
@@ -21553,7 +23309,7 @@ List the contents of a directory
 Sync `/home/local/directory` to the remote directory, deleting any
 excess files in the directory.
 
-    rclone sync /home/local/directory remote:directory
+    rclone sync -i /home/local/directory remote:directory
 
 ### SSH Authentication ###
 
@@ -21650,6 +23406,8 @@ SSH port, leave blank to use default (22)
 
 SSH password, leave blank to use ssh-agent.
 
+**NB** Input to this must be obscured - see [rclone obscure](https://rclone.org/commands/rclone_obscure/).
+
 - Config:      pass
 - Env Var:     RCLONE_SFTP_PASS
 - Type:        string
@@ -21668,6 +23426,9 @@ Raw PEM-encoded private key, If specified, will override key_file parameter.
 
 Path to PEM-encoded private key file, leave blank or set key-use-agent to use ssh-agent.
 
+Leading `~` will be expanded in the file name as will environment variables such as `${RCLONE_CONFIG_DIR}`.
+
+
 - Config:      key_file
 - Env Var:     RCLONE_SFTP_KEY_FILE
 - Type:        string
@@ -21680,6 +23441,8 @@ The passphrase to decrypt the PEM-encoded private key file.
 Only PEM encrypted key files (old OpenSSH format) are supported. Encrypted keys
 in the new OpenSSH format can't be used.
 
+**NB** Input to this must be obscured - see [rclone obscure](https://rclone.org/commands/rclone_obscure/).
+
 - Config:      key_file_pass
 - Env Var:     RCLONE_SFTP_KEY_FILE_PASS
 - Type:        string
@@ -21807,6 +23570,26 @@ Set to skip any symlinks and any other non regular files.
 - Type:        bool
 - Default:     false
 
+#### --sftp-subsystem
+
+Specifies the SSH2 subsystem on the remote host.
+
+- Config:      subsystem
+- Env Var:     RCLONE_SFTP_SUBSYSTEM
+- Type:        string
+- Default:     "sftp"
+
+#### --sftp-server-command
+
+Specifies the path or command to run a sftp server on the remote host.
+
+The subsystem option is ignored when server_command is defined.
+
+- Config:      server_command
+- Env Var:     RCLONE_SFTP_SERVER_COMMAND
+- Type:        string
+- Default:     ""
+
 
 
 ### Limitations ###
@@ -22322,7 +24105,7 @@ Use the `size` command to print the total size of objects in a bucket or a folde
 Use the `sync` command to sync the source to the destination,
 changing the destination only, deleting any excess files.
 
-    rclone sync --progress /home/local/directory/ remote:bucket/path/to/dir/
+    rclone sync -i --progress /home/local/directory/ remote:bucket/path/to/dir/
 
 The `--progress` flag is for displaying progress information.
 Remove it if you don't need this information.
@@ -22332,15 +24115,15 @@ to see exactly what would be copied and deleted.
 
 The sync can be done also from Tardigrade to the local file system.
 
-    rclone sync --progress remote:bucket/path/to/dir/ /home/local/directory/
+    rclone sync -i --progress remote:bucket/path/to/dir/ /home/local/directory/
 
 Or between two Tardigrade buckets.
 
-    rclone sync --progress remote-us:bucket/path/to/dir/ remote-europe:bucket/path/to/dir/
+    rclone sync -i --progress remote-us:bucket/path/to/dir/ remote-europe:bucket/path/to/dir/
 
 Or even between another cloud storage and Tardigrade.
 
-    rclone sync --progress s3:bucket/path/to/dir/ tardigrade:bucket/path/to/dir/
+    rclone sync -i --progress s3:bucket/path/to/dir/ tardigrade:bucket/path/to/dir/
 
 
 ### Standard Options
@@ -22778,6 +24561,8 @@ User name
 
 Password.
 
+**NB** Input to this must be obscured - see [rclone obscure](https://rclone.org/commands/rclone_obscure/).
+
 - Config:      pass
 - Env Var:     RCLONE_WEBDAV_PASS
 - Type:        string
@@ -23031,7 +24816,7 @@ List the contents of a directory
 Sync `/home/local/directory` to the remote path, deleting any
 excess files in the path.
 
-    rclone sync /home/local/directory remote:directory
+    rclone sync -i /home/local/directory remote:directory
 
 Yandex paths may be as deep as required, eg `remote:directory/subdirectory`.
 
@@ -23083,7 +24868,7 @@ Here are the standard options specific to yandex (Yandex Disk).
 
 #### --yandex-client-id
 
-Yandex Client Id
+OAuth Client Id
 Leave blank normally.
 
 - Config:      client_id
@@ -23093,7 +24878,7 @@ Leave blank normally.
 
 #### --yandex-client-secret
 
-Yandex Client Secret
+OAuth Client Secret
 Leave blank normally.
 
 - Config:      client_secret
@@ -23105,15 +24890,34 @@ Leave blank normally.
 
 Here are the advanced options specific to yandex (Yandex Disk).
 
-#### --yandex-unlink
+#### --yandex-token
 
-Remove existing public link to file/folder with link command rather than creating.
-Default is false, meaning link command will create or retrieve public link.
+OAuth Access Token as a JSON blob.
 
-- Config:      unlink
-- Env Var:     RCLONE_YANDEX_UNLINK
-- Type:        bool
-- Default:     false
+- Config:      token
+- Env Var:     RCLONE_YANDEX_TOKEN
+- Type:        string
+- Default:     ""
+
+#### --yandex-auth-url
+
+Auth server URL.
+Leave blank to use the provider defaults.
+
+- Config:      auth_url
+- Env Var:     RCLONE_YANDEX_AUTH_URL
+- Type:        string
+- Default:     ""
+
+#### --yandex-token-url
+
+Token server url.
+Leave blank to use the provider defaults.
+
+- Config:      token_url
+- Env Var:     RCLONE_YANDEX_TOKEN_URL
+- Type:        string
+- Default:     ""
 
 #### --yandex-encoding
 
@@ -23133,7 +24937,7 @@ See: the [encoding section in the overview](https://rclone.org/overview/#encodin
 
 Local paths are specified as normal filesystem paths, eg `/path/to/wherever`, so
 
-    rclone sync /home/source /tmp/destination
+    rclone sync -i /home/source /tmp/destination
 
 Will sync `/home/source` to `/tmp/destination`
 
@@ -23497,6 +25301,23 @@ However on some file systems this modification time check may fail (eg
 [Glusterfs #2206](https://github.com/rclone/rclone/issues/2206)) so this
 check can be disabled with this flag.
 
+If this flag is set, rclone will use its best efforts to transfer a
+file which is being updated. If the file is only having things
+appended to it (eg a log) then rclone will transfer the log file with
+the size it had the first time rclone saw it.
+
+If the file is being modified throughout (not just appended to) then
+the transfer may fail with a hash check failure.
+
+In detail, once the file has had stat() called on it for the first
+time we:
+
+- Only transfer the size that stat gave
+- Only checksum the size that stat gave
+- Don't update the stat info for the file
+
+
+
 - Config:      no_check_updated
 - Env Var:     RCLONE_LOCAL_NO_CHECK_UPDATED
 - Type:        bool
@@ -23551,6 +25372,21 @@ cause disk fragmentation and can be slow to work with.
 - Type:        bool
 - Default:     false
 
+#### --local-no-set-modtime
+
+Disable setting modtime
+
+Normally rclone updates modification time of files after they are done
+uploading. This can cause permissions issues on Linux platforms when 
+the user rclone is running as does not own the file uploaded, such as
+when copying to a CIFS mount owned by another user. If this option is 
+enabled, rclone will no longer update the modtime after copying a file.
+
+- Config:      no_set_modtime
+- Env Var:     RCLONE_LOCAL_NO_SET_MODTIME
+- Type:        bool
+- Default:     false
+
 #### --local-encoding
 
 This sets the encoding for the backend.
@@ -23596,6 +25432,273 @@ Options:
 
 # Changelog
 
+## v1.53.0 - 2020-09-02
+
+[See commits](https://github.com/rclone/rclone/compare/v1.52.0...v1.53.0)
+
+* New Features
+    * The [VFS layer](https://rclone.org/commands/rclone_mount/#vfs-virtual-file-system) was heavily reworked for this release - see below for more details
+    * Interactive mode [-i/--interactive](https://rclone.org/docs/#interactive) for destructive operations (fishbullet)
+    * Add [--bwlimit-file](https://rclone.org/docs/#bwlimit-file-bandwidth-spec) flag to limit speeds of individual file transfers (Nick Craig-Wood)
+    * Transfers are sorted by start time in the stats and progress output (Max Sum)
+    * Make sure backends expand `~` and environment vars in file names they use (Nick Craig-Wood)
+    * Add [--refresh-times](https://rclone.org/docs/#refresh-times) flag to set modtimes on hashless backends (Nick Craig-Wood)
+    * build
+        * Remove vendor directory in favour of Go modules (Nick Craig-Wood)
+        * Build with go1.15.x by default (Nick Craig-Wood)
+        * Drop macOS 386 build as it is no longer supported by go1.15 (Nick Craig-Wood)
+        * Add ARMv7 to the supported builds (Nick Craig-Wood)
+        * Enable `rclone cmount` on macOS (Nick Craig-Wood)
+        * Make rclone build with gccgo (Nick Craig-Wood)
+        * Make rclone build with wasm (Nick Craig-Wood)
+        * Change beta numbering to be semver compatible (Nick Craig-Wood)
+        * Add file properties and icon to Windows executable (albertony)
+        * Add experimental interface for integrating rclone into browsers (Nick Craig-Wood)
+    * lib: Add file name compression (Klaus Post)
+    * rc
+        * Allow installation and use of plugins and test plugins with rclone-webui (Chaitanya Bankanhal)
+        * Add reverse proxy pluginsHandler for serving plugins (Chaitanya Bankanhal)
+        * Add `mount/listmounts` option for listing current mounts (Chaitanya Bankanhal)
+        * Add `operations/uploadfile` to upload a file through rc using encoding multipart/form-data (Chaitanya Bankanhal)
+        * Add `core/copmmand` to execute rclone terminal commands. (Chaitanya Bankanhal)
+    * `rclone check`
+        * Add reporting of filenames for same/missing/changed (Nick Craig-Wood)
+        * Make check command obey `--dry-run`/`-i`/`--interactive` (Nick Craig-Wood)
+        * Make check do `--checkers` files concurrently (Nick Craig-Wood)
+        * Retry downloads if they fail when using the `--download` flag (Nick Craig-Wood)
+        * Make it show stats by default (Nick Craig-Wood)
+    * `rclone obscure`: Allow obscure command to accept password on STDIN (David Ibarra)
+    * `rclone config`
+        * Set RCLONE_CONFIG_DIR for use in config files and subprocesses (Nick Craig-Wood)
+        * Reject remote names starting with a dash. (jtagcat)
+    * `rclone cryptcheck`: Add reporting of filenames for same/missing/changed (Nick Craig-Wood)
+    * `rclone dedupe`: Make it obey the `--size-only` flag for duplicate detection (Nick Craig-Wood)
+    * `rclone link`: Add `--expire` and `--unlink` flags (Roman Kredentser)
+    * `rclone mkdir`: Warn when using mkdir on remotes which can't have empty directories (Nick Craig-Wood)
+    * `rclone rc`: Allow JSON parameters to simplify command line usage (Nick Craig-Wood)
+    * `rclone serve ftp`
+        * Don't compile on < go1.13 after dependency update (Nick Craig-Wood)
+        * Add error message if auth proxy fails (Nick Craig-Wood)
+        * Use refactored goftp.io/server library for binary shrink (Nick Craig-Wood)
+    * `rclone serve restic`: Expose interfaces so that rclone can be used as a library from within restic (Jack)
+    * `rclone sync`: Add `--track-renames-strategy leaf` (Nick Craig-Wood)
+    * `rclone touch`: Add ability to set nanosecond resolution times (Nick Craig-Wood)
+    * `rclone tree`: Remove `-i` shorthand for `--noindent` as it conflicts with `-i`/`--interactive` (Nick Craig-Wood)
+* Bug Fixes
+    * accounting
+        * Fix documentation for `speed`/`speedAvg` (Nick Craig-Wood)
+        * Fix elapsed time not show actual time since beginning (Chaitanya Bankanhal)
+        * Fix deadlock in stats printing (Nick Craig-Wood)
+    * build
+        * Fix file handle leak in GitHub release tool (Garrett Squire)
+    * `rclone check`: Fix successful retries with `--download` counting errors (Nick Craig-Wood)
+    * `rclone dedupe`: Fix logging to be easier to understand (Nick Craig-Wood)
+* Mount
+    * Warn macOS users that mount implementation is changing (Nick Craig-Wood)
+        * to test the new implementation use `rclone cmount` instead of `rclone mount`
+        * this is because the library rclone uses has dropped macOS support
+    * rc interface
+        * Add call for unmount all (Chaitanya Bankanhal)
+        * Make `mount/mount` remote control take vfsOpt option (Nick Craig-Wood)
+        * Add mountOpt to `mount/mount` (Nick Craig-Wood)
+        * Add VFS and Mount options to `mount/listmounts` (Nick Craig-Wood)
+    * Catch panics in cgofuse initialization and turn into error messages (Nick Craig-Wood)
+    * Always supply stat information in Readdir (Nick Craig-Wood)
+    * Add support for reading unknown length files using direct IO (Windows) (Nick Craig-Wood)
+    * Fix On Windows don't add `-o uid/gid=-1` if user supplies `-o uid/gid`. (Nick Craig-Wood)
+    * Fix macOS losing directory contents in cmount (Nick Craig-Wood)
+    * Fix volume name broken in recent refactor (Nick Craig-Wood)
+* VFS
+    * Implement partial reads for `--vfs-cache-mode full` (Nick Craig-Wood)
+    * Add `--vfs-writeback` option to delay writes back to cloud storage (Nick Craig-Wood)
+    * Add `--vfs-read-ahead` parameter for use with `--vfs-cache-mode full` (Nick Craig-Wood)
+    * Restart pending uploads on restart of the cache (Nick Craig-Wood)
+    * Support synchronous cache space recovery upon ENOSPC (Leo Luan)
+    * Allow ReadAt and WriteAt to run concurrently with themselves (Nick Craig-Wood)
+    * Change modtime of file before upload to current (Rob Calistri)
+    * Recommend `--vfs-cache-modes writes` on backends which can't stream (Nick Craig-Wood)
+    * Add an optional `fs` parameter to vfs rc methods (Nick Craig-Wood)
+    * Fix errors when using > 260 char files in the cache in Windows (Nick Craig-Wood)
+    * Fix renaming of items while they are being uploaded (Nick Craig-Wood)
+    * Fix very high load caused by slow directory listings (Nick Craig-Wood)
+    * Fix renamed files not being uploaded with `--vfs-cache-mode minimal` (Nick Craig-Wood)
+    * Fix directory locking caused by slow directory listings (Nick Craig-Wood)
+    * Fix saving from chrome without `--vfs-cache-mode writes` (Nick Craig-Wood)
+* Local
+    * Add `--local-no-updated` to provide a consistent view of changing objects (Nick Craig-Wood)
+    * Add `--local-no-set-modtime` option to prevent modtime changes (tyhuber1)
+    * Fix race conditions updating and reading Object metadata (Nick Craig-Wood)
+* Cache
+    * Make any created backends be cached to fix rc problems (Nick Craig-Wood)
+    * Fix dedupe on caches wrapping drives (Nick Craig-Wood)
+* Crypt
+    * Add `--crypt-server-side-across-configs` flag (Nick Craig-Wood)
+    * Make any created backends be cached to fix rc problems (Nick Craig-Wood)
+* Alias
+    * Make any created backends be cached to fix rc problems (Nick Craig-Wood)
+* Azure Blob
+    * Don't compile on < go1.13 after dependency update (Nick Craig-Wood)
+* B2
+    * Implement server side copy for files > 5GB (Nick Craig-Wood)
+    * Cancel in progress multipart uploads and copies on rclone exit (Nick Craig-Wood)
+    * Note that b2's encoding now allows \ but rclone's hasn't changed (Nick Craig-Wood)
+    * Fix transfers when using download_url (Nick Craig-Wood)
+* Box
+    * Implement rclone cleanup (buengese)
+    * Cancel in progress multipart uploads and copies on rclone exit (Nick Craig-Wood)
+    * Allow authentication with access token (David)
+* Chunker
+    * Make any created backends be cached to fix rc problems (Nick Craig-Wood)
+* Drive
+    * Add `rclone backend drives` to list shared drives (teamdrives) (Nick Craig-Wood)
+    * Implement `rclone backend untrash` (Nick Craig-Wood)
+    * Work around drive bug which didn't set modtime of copied docs (Nick Craig-Wood)
+    * Added `--drive-starred-only` to only show starred files (Jay McEntire)
+    * Deprecate `--drive-alternate-export` as it is no longer needed (themylogin)
+    * Fix duplication of Google docs on server side copy (Nick Craig-Wood)
+    * Fix "panic: send on closed channel" when recycling dir entries (Nick Craig-Wood)
+* Dropbox
+    * Add copyright detector info in limitations section in the docs (Alex Guerrero)
+    * Fix `rclone link` by removing expires parameter (Nick Craig-Wood)
+* Fichier
+    * Detect Flood detected: IP Locked error and sleep for 30s (Nick Craig-Wood)
+* FTP
+    * Add explicit TLS support (Heiko Bornholdt)
+    * Add support for `--dump bodies` and `--dump auth` for debugging (Nick Craig-Wood)
+    * Fix interoperation with pure-ftpd (Nick Craig-Wood)
+* Google Cloud Storage
+    * Add support for anonymous access (Kai Lüke)
+* Jottacloud
+    * Bring back legacy authentification for use with whitelabel versions (buengese)
+    * Switch to new api root - also implement a very ugly workaround for the DirMove failures (buengese)
+* Onedrive
+    * Rework cancel of multipart uploads on rclone exit (Nick Craig-Wood)
+    * Implement rclone cleanup (Nick Craig-Wood)
+    * Add `--onedrive-no-versions` flag to remove old versions (Nick Craig-Wood)
+* Pcloud
+    * Implement `rclone link` for public link creation (buengese)
+* Qingstor
+    * Cancel in progress multipart uploads on rclone exit (Nick Craig-Wood)
+* S3
+    * Preserve metadata when doing multipart copy (Nick Craig-Wood)
+    * Cancel in progress multipart uploads and copies on rclone exit (Nick Craig-Wood)
+    * Add `rclone link` for public link sharing (Roman Kredentser)
+    * Add `rclone backend restore` command to restore objects from GLACIER (Nick Craig-Wood)
+    * Add `rclone cleanup` and `rclone backend cleanup` to clean unfinished multipart uploads (Nick Craig-Wood)
+    * Add `rclone backend list-multipart-uploads` to list unfinished multipart uploads (Nick Craig-Wood)
+    * Add `--s3-max-upload-parts` support (Kamil Trzciński)
+    * Add `--s3-no-check-bucket` for minimising rclone transactions and perms (Nick Craig-Wood)
+    * Add `--s3-profile` and `--s3-shared-credentials-file` options (Nick Craig-Wood)
+    * Use regional s3 us-east-1 endpoint (David)
+    * Add Scaleway provider (Vincent Feltz)
+    * Update IBM COS endpoints (Egor Margineanu)
+    * Reduce the default `--s3-copy-cutoff` to < 5GB for Backblaze S3 compatibility (Nick Craig-Wood)
+    * Fix detection of bucket existing (Nick Craig-Wood)
+* SFTP
+    * Use the absolute path instead of the relative path for listing for improved compatibility (Nick Craig-Wood)
+    * Add `--sftp-subsystem` and `--sftp-server-command` options (aus)
+* Swift
+    * Fix dangling large objects breaking the listing (Nick Craig-Wood)
+    * Fix purge not deleting directory markers (Nick Craig-Wood)
+    * Fix update multipart object removing all of its own parts (Nick Craig-Wood)
+    * Fix missing hash from object returned from upload (Nick Craig-Wood)
+* Tardigrade
+    * Upgrade to uplink v1.2.0 (Kaloyan Raev)
+* Union
+    * Fix writing with the all policy (Nick Craig-Wood)
+* WebDAV
+    * Fix directory creation with 4shared (Nick Craig-Wood)
+
+## v1.52.3 - 2020-08-07
+
+[See commits](https://github.com/rclone/rclone/compare/v1.52.2...v1.52.3)
+
+* Bug Fixes
+    * docs
+        * Disable smart typography (eg en-dash) in MANUAL.* and man page (Nick Craig-Wood)
+        * Update install.md to reflect minimum Go version (Evan Harris)
+        * Update install from source instructions (Nick Craig-Wood)
+        * make_manual: Support SOURCE_DATE_EPOCH (Morten Linderud)
+    * log: Fix --use-json-log going to stderr not --log-file on Windows (Nick Craig-Wood)
+    * serve dlna: Fix file list on Samsung Series 6+ TVs (Matteo Pietro Dazzi)
+    * sync: Fix deadlock with --track-renames-strategy modtime (Nick Craig-Wood)
+* Cache
+    * Fix moveto/copyto remote:file remote:file2 (Nick Craig-Wood)
+* Drive
+    * Stop using root_folder_id as a cache (Nick Craig-Wood)
+    * Make dangling shortcuts appear in listings (Nick Craig-Wood)
+    * Drop "Disabling ListR" messages down to debug (Nick Craig-Wood)
+    * Workaround and policy for Google Drive API (Dmitry Ustalov)
+* FTP
+    * Add note to docs about home vs root directory selection (Nick Craig-Wood)
+* Onedrive
+    * Fix reverting to Copy when Move would have worked (Nick Craig-Wood)
+    * Avoid comma rendered in URL in onedrive.md (Kevin)
+* Pcloud
+    * Fix oauth on European region "eapi.pcloud.com" (Nick Craig-Wood)
+* S3
+    * Fix bucket Region auto detection when Region unset in config (Nick Craig-Wood)
+
+## v1.52.2 - 2020-06-24
+
+[See commits](https://github.com/rclone/rclone/compare/v1.52.1...v1.52.2)
+
+* Bug Fixes
+    * build
+        * Fix docker release build action (Nick Craig-Wood)
+        * Fix custom timezone in Docker image (NoLooseEnds)
+    * check: Fix misleading message which printed errors instead of differences (Nick Craig-Wood)
+    * errors: Add WSAECONNREFUSED and more to the list of retriable Windows errors (Nick Craig-Wood)
+    * rcd: Fix incorrect prometheus metrics (Gary Kim)
+    * serve restic: Fix flags so they use environment variables (Nick Craig-Wood)
+    * serve webdav: Fix flags so they use environment variables (Nick Craig-Wood)
+    * sync: Fix --track-renames-strategy modtime (Nick Craig-Wood)
+* Drive
+    * Fix not being able to delete a directory with a trashed shortcut (Nick Craig-Wood)
+    * Fix creating a directory inside a shortcut (Nick Craig-Wood)
+    * Fix --drive-impersonate with cached root_folder_id (Nick Craig-Wood)
+* SFTP
+    * Fix SSH key PEM loading (Zac Rubin)
+* Swift
+    * Speed up deletes by not retrying segment container deletes (Nick Craig-Wood)
+* Tardigrade
+    * Upgrade to uplink v1.1.1 (Caleb Case)
+* WebDAV
+    * Fix free/used display for rclone about/df for certain backends (Nick Craig-Wood)
+
+## v1.52.1 - 2020-06-10
+
+[See commits](https://github.com/rclone/rclone/compare/v1.52.0...v1.52.1)
+
+* Bug Fixes
+    * lib/file: Fix SetSparse on Windows 7 which fixes downloads of files > 250MB (Nick Craig-Wood)
+    * build
+        * Update go.mod to go1.14 to enable -mod=vendor build (Nick Craig-Wood)
+        * Remove quicktest from Dockerfile (Nick Craig-Wood)
+        * Build Docker images with GitHub actions (Matteo Pietro Dazzi)
+        * Update Docker build workflows (Nick Craig-Wood)
+        * Set user_allow_other in /etc/fuse.conf in the Docker image (Nick Craig-Wood)
+        * Fix xgo build after go1.14 go.mod update (Nick Craig-Wood)
+    * docs
+        * Add link to source and modified time to footer of every page (Nick Craig-Wood)
+        * Remove manually set dates and use git dates instead (Nick Craig-Wood)
+        * Minor tense, punctuation, brevity and positivity changes for the home page (edwardxml)
+        * Remove leading slash in page reference in footer when present (Nick Craig-Wood)
+        * Note commands which need obscured input in the docs (Nick Craig-Wood)
+        * obscure: Write more help as we are referencing it elsewhere (Nick Craig-Wood)
+* VFS
+    * Fix OS vs Unix path confusion - fixes ChangeNotify on Windows (Nick Craig-Wood)
+* Drive
+    * Fix missing items when listing using --fast-list / ListR (Nick Craig-Wood)
+* Putio
+    * Fix panic on Object.Open (Cenk Alti)
+* S3
+    * Fix upload of single files into buckets without create permission (Nick Craig-Wood)
+    * Fix --header-upload (Nick Craig-Wood)
+* Tardigrade
+    * Fix listing bug by upgrading to v1.0.7
+    * Set UserAgent to rclone (Caleb Case)
+
 ## v1.52.0 - 2020-05-27
 
 Special thanks to Martin Michlmayr for proof reading and correcting
@@ -26153,25 +28256,27 @@ Point release to fix hubic and azureblob backends.
 Rclone doesn't currently preserve the timestamps of directories.  This
 is because rclone only really considers objects when syncing.
 
-### Rclone struggles with millions of files in a directory
+### Rclone struggles with millions of files in a directory/bucket
 
-Currently rclone loads each directory entirely into memory before
-using it.  Since each Rclone object takes 0.5k-1k of memory this can
-take a very long time and use an extremely large amount of memory.
+Currently rclone loads each directory/bucket entirely into memory before
+using it.  Since each rclone object takes 0.5k-1k of memory this can take
+a very long time and use a large amount of memory.
 
-Millions of files in a directory tend caused by software writing cloud
-storage (eg S3 buckets).
+Millions of files in a directory tends to occur on bucket-based remotes
+(e.g. S3 buckets) since those remotes do not segregate subdirectories within
+the bucket.
 
 ### Bucket based remotes and folders
 
-Bucket based remotes (eg S3/GCS/Swift/B2) do not have a concept of
+Bucket based remotes (e.g. S3/GCS/Swift/B2) do not have a concept of
 directories.  Rclone therefore cannot create directories in them which
 means that empty directories on a bucket based remote will tend to
 disappear.
 
 Some software creates empty keys ending in `/` as directory markers.
 Rclone doesn't do this as it potentially creates more objects and
-costs more.  It may do in future (probably with a flag).
+costs more.  This ability may be added in the future (probably via a
+flag/option).
 
 ## Bugs
 
@@ -26211,7 +28316,7 @@ The syncs would be incremental (on a file by file basis).
 
 Eg
 
-    rclone sync drive:Folder s3:bucket
+    rclone sync -i drive:Folder s3:bucket
 
 
 ### Using rclone from multiple locations at the same time ###
@@ -26220,8 +28325,8 @@ You can use rclone from multiple places at the same time if you choose
 different subdirectory for the output, eg
 
 ```
-Server A> rclone sync /tmp/whatever remote:ServerA
-Server B> rclone sync /tmp/whatever remote:ServerB
+Server A> rclone sync -i /tmp/whatever remote:ServerA
+Server B> rclone sync -i /tmp/whatever remote:ServerB
 ```
 
 If you sync to the same directory then you should use rclone copy
@@ -26790,6 +28895,38 @@ put them back in again.` >}}
   * Martin Michlmayr <tbm@cyrius.com>
   * Brandon McNama <bmcnama@pagerduty.com>
   * Daniel Slyman <github@skylayer.eu>
+  * Alex Guerrero <guerrero@users.noreply.github.com>
+  * Matteo Pietro Dazzi <matteopietro.dazzi@gft.com>
+  * edwardxml <56691903+edwardxml@users.noreply.github.com>
+  * Roman Kredentser <shareed2k@gmail.com>
+  * Kamil Trzciński <ayufan@ayufan.eu>
+  * Zac Rubin <z-0@users.noreply.github.com>
+  * Vincent Feltz <psycho@feltzv.fr>
+  * Heiko Bornholdt <bornholdt@informatik.uni-hamburg.de>
+  * Matteo Pietro Dazzi <matteopietro.dazzi@gmail.com>
+  * jtagcat <gitlab@c7.ee>
+  * Petri Salminen <petri@salminen.dev>
+  * Tim Burke <tim.burke@gmail.com>
+  * Kai Lüke <kai@kinvolk.io>
+  * Garrett Squire <github@garrettsquire.com>
+  * Evan Harris <eharris@puremagic.com>
+  * Kevin <keyam@microsoft.com>
+  * Morten Linderud <morten@linderud.pw>
+  * Dmitry Ustalov <dmitry.ustalov@gmail.com>
+  * Jack <196648+jdeng@users.noreply.github.com>
+  * kcris <cristian.tarsoaga@gmail.com>
+  * tyhuber1 <68970760+tyhuber1@users.noreply.github.com>
+  * David Ibarra <david.ibarra@realty.com>
+  * Tim Gallant <tim@lilt.com>
+  * Kaloyan Raev <kaloyan@storj.io>
+  * Jay McEntire <jay.mcentire@gmail.com>
+  * Leo Luan <leoluan@us.ibm.com>
+  * aus <549081+aus@users.noreply.github.com>
+  * Aaron Gokaslan <agokaslan@fb.com>
+  * Egor Margineanu <egmar@users.noreply.github.com>
+  * Lucas Kanashiro <lucas.kanashiro@canonical.com>
+  * WarpedPixel <WarpedPixel@users.noreply.github.com>
+  * Sam Edwards <sam@samedwards.ca>
 
 # Contact the rclone project #
 
diff --git a/MANUAL.txt b/MANUAL.txt
index 4d0a7f9b2..59ebf1da2 100644
--- a/MANUAL.txt
+++ b/MANUAL.txt
@@ -1,6 +1,6 @@
 rclone(1) User Manual
 Nick Craig-Wood
-May 27, 2020
+Sep 02, 2020
 
 
 
@@ -8,9 +8,9 @@ RCLONE SYNCS YOUR FILES TO CLOUD STORAGE
 
 
 -   About rclone
--   What can rclone do for you
--   What features does rclone have
--   What providers does rclone support
+-   What can rclone do for you?
+-   What features does rclone have?
+-   What providers does rclone support?
 -   Download
 -   Install
 -   Donate.
@@ -19,33 +19,33 @@ RCLONE SYNCS YOUR FILES TO CLOUD STORAGE
 About rclone
 
 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 feature rich alternative to cloud vendors' web storage interfaces.
 Over 40 cloud storage products support rclone including S3 object
 stores, business & consumer file storage services, as well as standard
 transfer protocols.
 
 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 --dry-run protection. It can be
-used at the command line, in scripts or via its API.
+mv, mount, ls, ncdu, tree, rm, and cat. Rclone's familiar syntax
+includes shell pipeline support, and --dry-run protection. It is used at
+the command line, in scripts or via its API.
 
-Users have called rclone _“The Swiss army knife of cloud storage”_ and
-_“Technology indistinguishable from magic”_.
+Users call rclone _"The Swiss army knife of cloud storage"_, and
+_"Technology indistinguishable from magic"_.
 
 Rclone really looks after your data. It preserves timestamps and
-verifies your data at all times. Transfers over limited bandwidth;
+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 check 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
-your local disk.
+local disk.
 
 Virtual backends wrap local and cloud file systems to apply encryption,
 caching, chunking and joining.
 
-Rclone can mount any local, cloud or virtual filesystem as a disk on
-Windows, macOS, linux and FreeBSD, and also serve these over SFTP, HTTP,
-WebDAV, FTP and DLNA.
+Rclone mounts any local, cloud or virtual filesystem as a disk on
+Windows, macOS, linux and FreeBSD, and also serves these over SFTP,
+HTTP, WebDAV, FTP and DLNA.
 
 Rclone is mature, open source software originally inspired by rsync and
 written in Go. The friendly support community are familiar with varied
@@ -54,15 +54,15 @@ include rclone. For the latest version downloading from rclone.org is
 recommended.
 
 Rclone is widely used on Linux, Windows and Mac. Third party developers
-have built innovative backup, restore, GUI and business process
-solutions using the rclone command line or API.
+create innovative backup, restore, GUI and business process solutions
+using the rclone command line or API.
 
-Let rclone do the heavy lifting of communicating with cloud storage.
+Rclone does the heavy lifting of communicating with cloud storage.
 
 
-What can rclone do for you
+What can rclone do for you?
 
-Rclone can help you:
+Rclone helps you:
 
 -   Backup (and encrypt) files to cloud storage
 -   Restore (and decrypt) files from cloud storage
@@ -94,8 +94,8 @@ Features
 
 Supported providers
 
-(There are many other providers, built on standard protocols such as
-WebDAV or S3, that work out of the box.)
+(There are many others, built on standard protocols such as WebDAV or
+S3, that work out of the box.)
 
 -   1Fichier
 -   Alibaba Cloud (Aliyun) Object Storage System (OSS)
@@ -186,7 +186,7 @@ For beta installation, run:
     curl https://rclone.org/install.sh | sudo bash -s beta
 
 Note that this script checks the version of rclone installed first and
-won’t re-download if not needed.
+won't re-download if not needed.
 
 
 Linux installation from precompiled binary
@@ -300,10 +300,17 @@ Docker container from the rclone image.
     non-root UID:GID, you need to pass these on the container start
     command line.
 
+-   If you want to access the RC interface (either via the API or the
+    Web UI), it is required to set the --rc-addr to :5572 in order to
+    connect to it from outside the container. An explanation about why
+    this is necessary is present here.
+    -   NOTE: Users running this container with the docker network set
+        to host should probably set it to listen to localhost only, with
+        127.0.0.1:5572 as the value for --rc-addr
 -   It is possible to use rclone mount inside a userspace Docker
     container, and expose the resulting fuse mount to the host. The
     exact docker run options to do that might vary slightly between
-    hosts. See, e.g. the discussion in this thread.
+    hosts. See, e.g. the discussion in this thread.
 
     You also need to mount the host /etc/passwd and /etc/group for fuse
     to work inside the container.
@@ -337,7 +344,7 @@ Here are some commands tested on an Ubuntu 18.04.3 host:
 
 Install from source
 
-Make sure you have at least Go 1.7 installed. Download go if necessary.
+Make sure you have at least Go 1.11 installed. Download go if necessary.
 The latest release is recommended. Then
 
     git clone https://github.com/rclone/rclone.git
@@ -345,20 +352,28 @@ The latest release is recommended. Then
     go build
     ./rclone version
 
-You can also build and install rclone in the GOPATH (which defaults to
-~/go) with:
+This will leave you a checked out version of rclone you can modify and
+send pull requests with. If you use make instead of go build then the
+rclone build will have the correct version information in it.
 
-    go get -u -v github.com/rclone/rclone
+You can also build the latest stable rclone with:
 
-and this will build the binary in $GOPATH/bin (~/go/bin/rclone by
-default) after downloading the source to
-$GOPATH/src/github.com/rclone/rclone (~/go/src/github.com/rclone/rclone
-by default).
+    go get github.com/rclone/rclone
+
+or the latest version (equivalent to the beta) with
+
+    go get github.com/rclone/rclone@master
+
+These will build the binary in $(go env GOPATH)/bin (~/go/bin/rclone by
+default) after downloading the source to the go module cache. Note - do
+NOT use the -u flag here. This causes go to try to update the
+depencencies that rclone uses and sometimes these don't work with the
+current version of rclone.
 
 
 Installation with Ansible
 
-This can be done with Stefan Weichinger’s ansible role.
+This can be done with Stefan Weichinger's ansible role.
 
 Instructions
 
@@ -373,7 +388,7 @@ Instructions
 
 Configure
 
-First, you’ll need to configure rclone. As the object storage systems
+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 --config entry for how to find the config file and choose its
 location.)
@@ -435,11 +450,14 @@ Its syntax is like this
     Syntax: [options] subcommand <parameters> <parameters...>
 
 Source and destination paths are specified by the name you gave the
-storage system in the config file then the sub path, eg “drive:myfolder”
-to look at “myfolder” in Google drive.
+storage system in the config file then the sub path, eg "drive:myfolder"
+to look at "myfolder" in Google drive.
 
 You can define as many storage paths as you like in the config file.
 
+Please use the -i / --interactive flag while learning rclone to avoid
+accidental data loss.
+
 
 Subcommands
 
@@ -447,7 +465,7 @@ rclone uses a system of subcommands. For example
 
     rclone ls remote:path # lists a remote
     rclone copy /local/path remote:path # copies /local/path to the remote
-    rclone sync /local/path remote:path # syncs /local/path to the remote
+    rclone sync -i /local/path remote:path # syncs /local/path to the remote
 
 
 
@@ -502,22 +520,22 @@ Copy files from source to dest, skipping already copied
 
 Synopsis
 
-Copy the source to the destination. Doesn’t transfer unchanged files,
-testing by size and modification time or MD5SUM. Doesn’t delete files
+Copy the source to the destination. Doesn't transfer unchanged files,
+testing by size and modification time or MD5SUM. Doesn't delete files
 from the destination.
 
 Note that it is always the contents of the directory that is synced, not
-the directory so when source:path is a directory, it’s the contents of
+the directory so when source:path is a directory, it's the contents of
 source:path that are copied, not the directory name and contents.
 
-If dest:path doesn’t exist, it is created and the source:path contents
+If dest:path doesn't exist, it is created and the source:path contents
 go there.
 
 For example
 
     rclone copy source:sourcepath dest:destpath
 
-Let’s say there are two files in sourcepath
+Let's say there are two files in sourcepath
 
     sourcepath/one.txt
     sourcepath/two.txt
@@ -533,11 +551,11 @@ Not to
     destpath/sourcepath/two.txt
 
 If you are familiar with rsync, rclone always works as if you had
-written a trailing / - meaning “copy the contents of this directory”.
+written a trailing / - meaning "copy the contents of this directory".
 This applies to all commands and whether you are talking about the
 source or destination.
 
-See the –no-traverse option for controlling whether rclone lists the
+See the --no-traverse 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.
 
@@ -547,7 +565,10 @@ recently very efficiently like this:
 
     rclone copy --max-age 24h --no-traverse /path/to/src remote:
 
-NOTE: Use the -P/--progress flag to view real-time transfer statistics
+NOTE: Use the -P/--progress flag to view real-time transfer statistics.
+
+NOTE: Use the --dry-run or the --interactive/-i flag to test without
+copying anything.
 
     rclone copy source:path dest:path [flags]
 
@@ -575,22 +596,24 @@ Make source and dest identical, modifying destination only.
 Synopsis
 
 Sync the source to the destination, changing the destination only.
-Doesn’t transfer unchanged files, testing by size and modification time
+Doesn't transfer unchanged files, testing by size and modification time
 or MD5SUM. Destination is updated to match source, including deleting
 files if necessary.
 
 IMPORTANT: Since this can cause data loss, test first with the --dry-run
-flag to see exactly what would be copied and deleted.
+or the --interactive/-i flag.
 
-Note that files in the destination won’t be deleted if there were any
+    rclone sync -i SOURCE remote:DESTINATION
+
+Note that files in the destination won't be deleted if there were any
 errors at any point.
 
 It is always the contents of the directory that is synced, not the
-directory so when source:path is a directory, it’s the contents of
+directory 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 copy command above if unsure.
 
-If dest:path doesn’t exist, it is created and the source:path contents
+If dest:path doesn't exist, it is created and the source:path contents
 go there.
 
 NOTE: Use the -P/--progress flag to view real-time transfer statistics
@@ -633,14 +656,14 @@ used, otherwise it will copy it (server side if possible) into dest:path
 then delete the original (if no errors on copy) in source:path.
 
 If you want to delete empty source directories after move, use the
-–delete-empty-src-dirs flag.
+--delete-empty-src-dirs flag.
 
-See the –no-traverse option for controlling whether rclone lists the
+See the --no-traverse 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.
 
-IMPORTANT: Since this can cause data loss, test first with the –dry-run
-flag.
+IMPORTANT: Since this can cause data loss, test first with the --dry-run
+or the --interactive/-i flag.
 
 NOTE: Use the -P/--progress flag to view real-time transfer statistics.
 
@@ -677,7 +700,7 @@ rclone delete only deletes objects but leaves the directory structure
 alone. If you want to delete a directory and all of its contents use
 rclone purge
 
-If you supply the –rmdirs flag, it will remove all empty directories
+If you supply the --rmdirs flag, it will remove all empty directories
 along with it.
 
 Eg delete all files bigger than 100MBytes
@@ -691,9 +714,12 @@ Then delete
 
     rclone --min-size 100M delete remote:path
 
-That reads “delete everything with a minimum size of 100 MB”, hence
+That reads "delete everything with a minimum size of 100 MB", hence
 delete all files bigger than 100MBytes.
 
+IMPORTANT: Since this can cause data loss, test first with the --dry-run
+or the --interactive/-i flag.
+
     rclone delete remote:path [flags]
 
 
@@ -723,6 +749,9 @@ Remove the path and all of its contents. Note that this does not obey
 include/exclude filters - everything will be removed. Use delete if you
 want to selectively delete files.
 
+IMPORTANT: Since this can cause data loss, test first with the --dry-run
+or the --interactive/-i flag.
+
     rclone purge remote:path [flags]
 
 
@@ -742,12 +771,12 @@ SEE ALSO
 RCLONE MKDIR
 
 
-Make the path if it doesn’t already exist.
+Make the path if it doesn't already exist.
 
 
 Synopsis
 
-Make the path if it doesn’t already exist.
+Make the path if it doesn't already exist.
 
     rclone mkdir remote:path [flags]
 
@@ -773,7 +802,7 @@ Remove the path if empty.
 
 Synopsis
 
-Remove the path. Note that you can’t remove a path with objects in it,
+Remove the path. Note that you can't remove a path with objects in it,
 use purge for that.
 
     rclone rmdir remote:path [flags]
@@ -801,30 +830,56 @@ Checks the files in the source and destination match.
 Synopsis
 
 Checks the files in the source and destination match. It compares sizes
-and hashes (MD5 or SHA1) and logs a report of files which don’t match.
-It doesn’t alter the source or destination.
+and hashes (MD5 or SHA1) and logs a report of files which don't match.
+It doesn't alter the source or destination.
 
-If you supply the –size-only flag, it will only compare the sizes not
+If you supply the --size-only flag, it will only compare the sizes not
 the hashes as well. Use this for a quick check.
 
-If you supply the –download flag, it will download the data from both
+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
+for remotes that don't support hashes or if you really want to check all
 the data.
 
-If you supply the –one-way flag, it will only check that files in source
-match the files in destination, not the other way around. Meaning extra
-files in destination that are not in the source will not trigger an
-error.
+If you supply the --one-way 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.
+
+The --differ, --missing-on-dst, --missing-on-src, --src-only and --error
+flags write paths, one per line, to the file name (or stdout if it is -)
+supplied. What they write is described in the help below. For example
+--differ will write all paths which are present on both the source and
+destination but different.
+
+The --combined 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.
+
+-   = path means path was found in source and destination and was
+    identical
+-   - path means path was missing on the source, so only in the
+    destination
+-   + path means path was missing on the destination, so only in the
+    source
+-   * path means path was present in source and destination but
+    different.
+-   ! path means there was an error reading or hashing the source or
+    dest.
 
     rclone check source:path dest:path [flags]
 
 
 Options
 
-          --download   Check by downloading rather than with hash.
-      -h, --help       help for check
-          --one-way    Check one way only, source files must exist on remote
+          --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 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
 
 See the global flags page for global options not listed here.
 
@@ -867,14 +922,14 @@ There are several related list commands
 ls,lsl,lsd are designed to be human readable. lsf is designed to be
 human and machine readable. lsjson is designed to be machine readable.
 
-Note that ls and lsl recurse by default - use “–max-depth 1” to stop the
-recursion.
+Note that ls and lsl recurse by default - use "--max-depth 1" to stop
+the recursion.
 
 The other list commands lsd,lsf,lsjson do not recurse by default - use
-“-R” to make them recurse.
+"-R" to make them recurse.
 
 Listing a non existent directory will produce an error except for
-remotes which can’t have empty directories (eg s3, swift, gcs, etc - the
+remotes which can't have empty directories (eg s3, swift, gcs, etc - the
 bucket based remotes).
 
     rclone ls remote:path [flags]
@@ -920,7 +975,7 @@ Or
               -1 2017-01-03 14:40:54        -1 2500files
               -1 2017-07-08 14:39:28        -1 4000files
 
-If you just want the directory names use “rclone lsf –dirs-only”.
+If you just want the directory names use "rclone lsf --dirs-only".
 
 Any of the filtering options can be applied to this command.
 
@@ -935,14 +990,14 @@ There are several related list commands
 ls,lsl,lsd are designed to be human readable. lsf is designed to be
 human and machine readable. lsjson is designed to be machine readable.
 
-Note that ls and lsl recurse by default - use “–max-depth 1” to stop the
-recursion.
+Note that ls and lsl recurse by default - use "--max-depth 1" to stop
+the recursion.
 
 The other list commands lsd,lsf,lsjson do not recurse by default - use
-“-R” to make them recurse.
+"-R" to make them recurse.
 
 Listing a non existent directory will produce an error except for
-remotes which can’t have empty directories (eg s3, swift, gcs, etc - the
+remotes which can't have empty directories (eg s3, swift, gcs, etc - the
 bucket based remotes).
 
     rclone lsd remote:path [flags]
@@ -995,14 +1050,14 @@ There are several related list commands
 ls,lsl,lsd are designed to be human readable. lsf is designed to be
 human and machine readable. lsjson is designed to be machine readable.
 
-Note that ls and lsl recurse by default - use “–max-depth 1” to stop the
-recursion.
+Note that ls and lsl recurse by default - use "--max-depth 1" to stop
+the recursion.
 
 The other list commands lsd,lsf,lsjson do not recurse by default - use
-“-R” to make them recurse.
+"-R" to make them recurse.
 
 Listing a non existent directory will produce an error except for
-remotes which can’t have empty directories (eg s3, swift, gcs, etc - the
+remotes which can't have empty directories (eg s3, swift, gcs, etc - the
 bucket based remotes).
 
     rclone lsl remote:path [flags]
@@ -1119,7 +1174,7 @@ Eg
     - os/arch: linux/amd64
     - go version: go1.10
 
-If you supply the –check flag, then it will do an online check to
+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.
 
     $ rclone version --check
@@ -1183,23 +1238,36 @@ SEE ALSO
 RCLONE DEDUPE
 
 
-Interactively find duplicate files and delete/rename them.
+Interactively find duplicate filenames and delete/rename them.
 
 
 Synopsis
 
-By default dedupe interactively finds duplicate files and offers to
-delete all but one or rename them to be different. Only useful with
-Google Drive which can have duplicate file names.
+By default dedupe interactively finds files with duplicate names and
+offers to delete all but one or rename them to be different.
+
+This is only useful with backends like Google Drive which can have
+duplicate file names. It can be run on wrapping backends (eg crypt) if
+they wrap a backend which supports duplicate file names.
 
 In the first pass it will merge directories with the same name. It will
-do this iteratively until all the identical directories have been
-merged.
+do this iteratively until all the identically named directories have
+been merged.
 
-The dedupe command will delete all but one of any identical (same
-md5sum) files it finds without confirmation. This means that for most
-duplicated files the dedupe command will not be interactive. You can use
---dry-run to see what would happen without doing anything.
+In the second pass, for every group of duplicate file names, it will
+delete all but one identical files it finds without confirmation. This
+means that for most duplicated files the dedupe command will not be
+interactive.
+
+dedupe considers files to be identical if they have the same hash. If
+the backend does not support hashes (eg crypt wrapping Google Drive)
+then they will never be found to be identical. If you use the
+--size-only 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.
+
+IMPORTANT: Since this can cause data loss, test first with the --dry-run
+or the --interactive/-i flag.
 
 Here is an example run.
 
@@ -1218,22 +1286,22 @@ Now the dedupe session
 
     $ rclone dedupe drive:dupes
     2016/03/05 16:24:37 Google drive root 'dupes': Looking for duplicates using interactive mode.
-    one.txt: Found 4 duplicates - deleting identical copies
-    one.txt: Deleting 2/3 identical duplicates (md5sum "1eedaa9fe86fd4b8632e2ac549403b36")
+    one.txt: Found 4 files with duplicate names
+    one.txt: Deleting 2/3 identical duplicates (MD5 "1eedaa9fe86fd4b8632e2ac549403b36")
     one.txt: 2 duplicates remain
-      1:      6048320 bytes, 2016-03-05 16:23:16.798000000, md5sum 1eedaa9fe86fd4b8632e2ac549403b36
-      2:       564374 bytes, 2016-03-05 16:23:06.731000000, md5sum 7594e7dc9fc28f727c42ee3e0749de81
+      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> k
     Enter the number of the file to keep> 1
     one.txt: Deleted 1 extra copies
-    two.txt: Found 3 duplicates - deleting identical copies
+    two.txt: Found 3 files with duplicates names
     two.txt: 3 duplicates remain
-      1:       564374 bytes, 2016-03-05 16:22:52.118000000, md5sum 7594e7dc9fc28f727c42ee3e0749de81
-      2:      6048320 bytes, 2016-03-05 16:22:46.185000000, md5sum 1eedaa9fe86fd4b8632e2ac549403b36
-      3:      1744073 bytes, 2016-03-05 16:22:38.104000000, md5sum 851957f7fb6f0bc4ce76be966d336802
+      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)
@@ -1327,7 +1395,7 @@ Note that not all the backends provide all the fields - they will be
 missing if they are not known for that backend. Where it is known that
 the value is unlimited the value will also be omitted.
 
-Use the –full flag to see the numbers written out in full, eg
+Use the --full flag to see the numbers written out in full, eg
 
     Total:   18253611008
     Used:    7993453766
@@ -1335,7 +1403,7 @@ Use the –full flag to see the numbers written out in full, eg
     Trashed: 104857602
     Other:   8849156022
 
-Use the –json flag for a computer readable output, eg
+Use the --json flag for a computer readable output, eg
 
     {
         "total": 18253611008,
@@ -1374,7 +1442,7 @@ Synopsis
 Remote authorization. Used to authorize a remote or headless rclone from
 a machine with a browser - use as instructed by rclone config.
 
-Use the –auth-no-open-browser to prevent rclone to open auth link in
+Use the --auth-no-open-browser to prevent rclone to open auth link in
 default browser automatically.
 
     rclone authorize [flags]
@@ -1403,7 +1471,7 @@ Run a backend specific command.
 Synopsis
 
 This runs a backend specific command. The commands themselves (except
-for “help” and “features”) are defined by the backends and you should
+for "help" and "features") are defined by the backends and you should
 see the backend docs for definitions.
 
 You can discover what commands a backend implements by using
@@ -1468,10 +1536,10 @@ Or like this to output any .txt files in dir or its subdirectories.
 
     rclone --include "*.txt" cat remote:path/to/dir
 
-Use the –head flag to print characters only at the start, –tail for the
-end and –offset and –count to print a section in the middle. Note that
-if offset is negative it will count from the end, so –offset -1 –count 1
-is equivalent to –tail 1.
+Use the --head flag to print characters only at the start, --tail for
+the end and --offset and --count to print a section in the middle. Note
+that if offset is negative it will count from the end, so --offset -1
+--count 1 is equivalent to --tail 1.
 
     rclone cat remote:path [flags]
 
@@ -1515,16 +1583,16 @@ default is taken. Each time that happens rclone will print a message
 saying how to affect the value taken.
 
 If any of the parameters passed is a password field, then rclone will
-automatically obscure them if they aren’t already obscured before
+automatically obscure them if they aren't already obscured before
 putting them in the config file.
 
 NB 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 “–obscure” flag, or if you are 100% certain you
-are already passing obscured passwords then use “–no-obscure”. You can
-also set osbscured passwords using the “rclone config password” command.
+obscured then use the "--obscure" flag, or if you are 100% certain you
+are already passing obscured passwords then use "--no-obscure". You can
+also set osbscured passwords using the "rclone config password" command.
 
 So for example if you wanted to configure a Google Drive remote but
 using remote authorization you would do this:
@@ -1587,7 +1655,7 @@ This disconnects the remote: passed in to the cloud storage system.
 
 This normally means revoking the oauth token.
 
-To reconnect use “rclone config reconnect”.
+To reconnect use "rclone config reconnect".
 
     rclone config disconnect remote: [flags]
 
@@ -1693,14 +1761,14 @@ Update password in an existing remote.
 
 Synopsis
 
-Update an existing remote’s password. The password should be passed in
+Update an existing remote's password. The password should be passed in
 pairs of key value.
 
 For example to set password of a remote of name myremote you would do:
 
     rclone config password myremote fieldname mypassword
 
-This command is obsolete now that “config update” and “config create”
+This command is obsolete now that "config update" and "config create"
 both support obscuring passwords directly.
 
     rclone config password `name` [`key` `value`]+ [flags]
@@ -1755,7 +1823,7 @@ Synopsis
 
 This reconnects remote: passed in to the cloud storage system.
 
-To disconnect the remote use “rclone config disconnect”.
+To disconnect the remote use "rclone config disconnect".
 
 This normally means going through the interactive oauth flow again.
 
@@ -1809,7 +1877,7 @@ Update options in an existing remote.
 
 Synopsis
 
-Update an existing remote’s options. The options should be passed in in
+Update an existing remote's options. The options should be passed in in
 pairs of key value.
 
 For example to update the env_auth field of a remote of name myremote
@@ -1818,18 +1886,18 @@ you would do:
     rclone config update myremote swift env_auth true
 
 If any of the parameters passed is a password field, then rclone will
-automatically obscure them if they aren’t already obscured before
+automatically obscure them if they aren't already obscured before
 putting them in the config file.
 
 NB 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 “–obscure” flag, or if you are 100% certain you
-are already passing obscured passwords then use “–no-obscure”. You can
-also set osbscured passwords using the “rclone config password” command.
+obscured then use the "--obscure" flag, or if you are 100% certain you
+are already passing obscured passwords then use "--no-obscure". You can
+also set osbscured passwords using the "rclone config password" command.
 
-If the remote uses OAuth the token will be updated, if you don’t require
+If the remote uses OAuth the token will be updated, if you don't require
 this add an extra parameter thus:
 
     rclone config update myremote swift env_auth true config_refresh_token false
@@ -1910,8 +1978,8 @@ This will:
         copy it to dst, overwriting existing files if they exist
         see copy command for full details
 
-This doesn’t transfer unchanged files, testing by size and modification
-time or MD5SUM. It doesn’t delete files from the destination.
+This doesn't transfer unchanged files, testing by size and modification
+time or MD5SUM. It doesn't delete files from the destination.
 
 NOTE: Use the -P/--progress flag to view real-time transfer statistics
 
@@ -1939,17 +2007,17 @@ Copy url content to dest.
 
 Synopsis
 
-Download a URL’s content and copy it to the destination without saving
+Download a URL's content and copy it to the destination without saving
 it in temporary storage.
 
-Setting –auto-filename will cause the file name to be retrieved from the
-from URL (after any redirections) and used in the destination path.
+Setting --auto-filename will cause the file name to be retrieved from
+the from URL (after any redirections) and used in the destination path.
 
-Setting –no-clobber will prevent overwriting file on the destination if
+Setting --no-clobber will prevent overwriting file on the destination if
 there is one with the same name.
 
-Setting –stdout or making the output file name “-” will cause the output
-to be written to standard output.
+Setting --stdout or making the output file name "-" will cause the
+output to be written to standard output.
 
     rclone copyurl https://example.com dest:path [flags]
 
@@ -2001,18 +2069,45 @@ files in remote:path.
 
 After it has run it will log the status of the encryptedremote:.
 
-If you supply the –one-way flag, it will only check that files in source
-match the files in destination, not the other way around. Meaning extra
-files in destination that are not in the source will not trigger an
-error.
+If you supply the --one-way 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.
+
+The --differ, --missing-on-dst, --missing-on-src, --src-only and --error
+flags write paths, one per line, to the file name (or stdout if it is -)
+supplied. What they write is described in the help below. For example
+--differ will write all paths which are present on both the source and
+destination but different.
+
+The --combined 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.
+
+-   = path means path was found in source and destination and was
+    identical
+-   - path means path was missing on the source, so only in the
+    destination
+-   + path means path was missing on the destination, so only in the
+    source
+-   * path means path was present in source and destination but
+    different.
+-   ! path means there was an error reading or hashing the source or
+    dest.
 
     rclone cryptcheck remote:path cryptedremote:path [flags]
 
 
 Options
 
-      -h, --help      help for cryptcheck
-          --one-way   Check one way only, source files must exist on destination
+          --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
 
 See the global flags page for global options not listed here.
 
@@ -2034,7 +2129,7 @@ Synopsis
 rclone cryptdecode returns unencrypted file names when provided with a
 list of encrypted file names. List limit is 10 items.
 
-If you supply the –reverse flag, it will return encrypted file names.
+If you supply the --reverse flag, it will return encrypted file names.
 
 use it like this
 
@@ -2068,7 +2163,7 @@ Remove a single file from remote.
 Synopsis
 
 Remove a single file from remote. Unlike delete it cannot be used to
-remove a directory and it doesn’t obey include/exclude filters - if the
+remove a directory and it doesn't obey include/exclude filters - if the
 specified file exists, it will always be removed.
 
     rclone deletefile remote:path [flags]
@@ -2095,7 +2190,7 @@ Output completion script for a given shell.
 
 Synopsis
 
-Generates a shell completion script for rclone. Run with –help to list
+Generates a shell completion script for rclone. Run with --help to list
 the supported shells.
 
 
@@ -2310,23 +2405,36 @@ Generate public link to file/folder.
 
 Synopsis
 
-rclone link will create or retrieve a public link to the given file or
-folder.
+rclone link will create, retrieve or remove a public link to the given
+file or folder.
 
     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
+
+If you supply the --expire flag, it will set the expiration time
+otherwise it will use the default (100 years). NOTE not all backends
+support the --expire flag - if the backend doesn't support it then the
+link returned won't expire.
+
+Use the --unlink flag to remove existing public links to the file or
+folder. NOTE not all backends support "--unlink" flag - those that don't
+will just ignore it.
 
 If successful, the last line of the output will contain the link. Exact
-capabilities depend on the remote, but the link will always be created
-with the least constraints – e.g. no expiry, no password protection,
-accessible without account.
+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.
 
     rclone link remote:path [flags]
 
 
 Options
 
-      -h, --help   help for link
+          --expire Duration   The amount of time that the link will be valid (default 100y)
+      -h, --help              help for link
+          --unlink            Remove existing public link to file/folder
 
 See the global flags page for global options not listed here.
 
@@ -2388,7 +2496,7 @@ Eg
     ferejej3gux/
     fubuwic
 
-Use the –format option to control what gets listed. By default this is
+Use the --format option to control what gets listed. By default this is
 just the path, but you can use these parameters to control the output:
 
     p - path
@@ -2402,7 +2510,7 @@ just the path, but you can use these parameters to control the output:
     T - tier of storage if known, eg "Hot" or "Cool"
 
 So if you wanted the path, size and modification time, you would use
-–format “pst”, or maybe –format “tsp” to put the path last.
+--format "pst", or maybe --format "tsp" to put the path last.
 
 Eg
 
@@ -2413,11 +2521,11 @@ Eg
     2018-04-26 08:50:45;0;ferejej3gux/
     2016-06-25 18:55:40;37600;fubuwic
 
-If you specify “h” in the format you will get the MD5 hash by default,
-use the “–hash” 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.
+If you specify "h" in the format you will get the MD5 hash by default,
+use the "--hash" 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.
 
 For example to emulate the md5sum command you can use
 
@@ -2432,10 +2540,10 @@ Eg
     8fd37c3810dd660778137ac3a66cc06d  fubuwic
     99713e14a4c4ff553acaf1930fad985b  gixacuh7ku
 
-(Though “rclone md5sum .” is an easier way of typing this.)
+(Though "rclone md5sum ." is an easier way of typing this.)
 
-By default the separator is “;” this can be changed with the –separator
-flag. Note that separators aren’t escaped in the path so putting it last
+By default the separator is ";" this can be changed with the --separator
+flag. Note that separators aren't escaped in the path so putting it last
 is a good strategy.
 
 Eg
@@ -2457,8 +2565,8 @@ Eg
     test.sh,449
     "this file contains a comma, in the file name.txt",6
 
-Note that the –absolute parameter is useful for making lists of files to
-pass to an rclone copy with the –files-from-raw flag.
+Note that the --absolute parameter is useful for making lists of files
+to pass to an rclone copy with the --files-from-raw flag.
 
 For example to find all the files modified within one day and copy those
 only (without traversing the whole directory structure):
@@ -2479,14 +2587,14 @@ There are several related list commands
 ls,lsl,lsd are designed to be human readable. lsf is designed to be
 human and machine readable. lsjson is designed to be machine readable.
 
-Note that ls and lsl recurse by default - use “–max-depth 1” to stop the
-recursion.
+Note that ls and lsl recurse by default - use "--max-depth 1" to stop
+the recursion.
 
 The other list commands lsd,lsf,lsjson do not recurse by default - use
-“-R” to make them recurse.
+"-R" to make them recurse.
 
 Listing a non existent directory will produce an error except for
-remotes which can’t have empty directories (eg s3, swift, gcs, etc - the
+remotes which can't have empty directories (eg s3, swift, gcs, etc - the
 bucket based remotes).
 
     rclone lsf remote:path [flags]
@@ -2526,52 +2634,52 @@ List directories and objects in the path in JSON format.
 
 The output is an array of Items, where each Item looks like this
 
-{ “Hashes” : { “SHA-1” : “f572d396fae9206628714fb2ce00f72e94f2258f”,
-“MD5” : “b1946ac92492d2347c6235b4d2611184”, “DropboxHash” :
-“ecb65bb98f9d905b70458986c39fcbad7715e5f2fcc3b1f07767d7c83e2438cc” },
-“ID”: “y2djkhiujf83u33”, “OrigID”: “UYOJVTUW00Q1RzTDA”, “IsBucket” :
-false, “IsDir” : false, “MimeType” : “application/octet-stream”,
-“ModTime” : “2017-05-31T16:15:57.034468261+01:00”, “Name” : “file.txt”,
-“Encrypted” : “v0qpsdq8anpci8n929v3uu9338”, “EncryptedPath” :
-“kja9098349023498/v0qpsdq8anpci8n929v3uu9338”, “Path” :
-“full/path/goes/here/file.txt”, “Size” : 6, “Tier” : “hot”, }
+{ "Hashes" : { "SHA-1" : "f572d396fae9206628714fb2ce00f72e94f2258f",
+"MD5" : "b1946ac92492d2347c6235b4d2611184", "DropboxHash" :
+"ecb65bb98f9d905b70458986c39fcbad7715e5f2fcc3b1f07767d7c83e2438cc" },
+"ID": "y2djkhiujf83u33", "OrigID": "UYOJVTUW00Q1RzTDA", "IsBucket" :
+false, "IsDir" : false, "MimeType" : "application/octet-stream",
+"ModTime" : "2017-05-31T16:15:57.034468261+01:00", "Name" : "file.txt",
+"Encrypted" : "v0qpsdq8anpci8n929v3uu9338", "EncryptedPath" :
+"kja9098349023498/v0qpsdq8anpci8n929v3uu9338", "Path" :
+"full/path/goes/here/file.txt", "Size" : 6, "Tier" : "hot", }
 
-If –hash is not specified the Hashes property won’t be emitted. The
-types of hash can be specified with the –hash-type parameter (which may
-be repeated). If –hash-type is set then it implies –hash.
+If --hash is not specified the Hashes property won't be emitted. The
+types of hash can be specified with the --hash-type parameter (which may
+be repeated). If --hash-type is set then it implies --hash.
 
-If –no-modtime is specified then ModTime will be blank. This can speed
+If --no-modtime is specified then ModTime will be blank. This can speed
 things up on remotes where reading the ModTime takes an extra request
 (eg s3, swift).
 
-If –no-mimetype is specified then MimeType will be blank. This can speed
-things up on remotes where reading the MimeType takes an extra request
-(eg s3, swift).
+If --no-mimetype is specified then MimeType will be blank. This can
+speed things up on remotes where reading the MimeType takes an extra
+request (eg s3, swift).
 
-If –encrypted is not specified the Encrypted won’t be emitted.
+If --encrypted is not specified the Encrypted won't be emitted.
 
-If –dirs-only is not specified files in addition to directories are
+If --dirs-only is not specified files in addition to directories are
 returned
 
-If –files-only is not specified directories in addition to the files
+If --files-only is not specified directories in addition to the files
 will be returned.
 
 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 –recursive the Path
+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 --recursive the Path
 will always be the same as Name.
 
-If the directory is a bucket in a bucket based backend, then “IsBucket”
-will be set to true. This key won’t be present unless it is “true”.
+If the directory is a bucket in a bucket based backend, then "IsBucket"
+will be set to true. This key won't be present unless it is "true".
 
 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 (eg Google Drive) then 3 digits will always be shown
-(“2017-05-31T16:15:57.034+01:00”) whereas if the times are accurate to
+("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”).
+("2017-05-31T16:15:57+01:00").
 
 The whole output can be processed as a JSON blob, or alternatively it
 can be processed line by line as each item is written one to a line.
@@ -2589,14 +2697,14 @@ There are several related list commands
 ls,lsl,lsd are designed to be human readable. lsf is designed to be
 human and machine readable. lsjson is designed to be machine readable.
 
-Note that ls and lsl recurse by default - use “–max-depth 1” to stop the
-recursion.
+Note that ls and lsl recurse by default - use "--max-depth 1" to stop
+the recursion.
 
 The other list commands lsd,lsf,lsjson do not recurse by default - use
-“-R” to make them recurse.
+"-R" to make them recurse.
 
 Listing a non existent directory will produce an error except for
-remotes which can’t have empty directories (eg s3, swift, gcs, etc - the
+remotes which can't have empty directories (eg s3, swift, gcs, etc - the
 bucket based remotes).
 
     rclone lsjson remote:path [flags]
@@ -2633,13 +2741,13 @@ Mount the remote as file system on a mountpoint.
 Synopsis
 
 rclone mount allows Linux, FreeBSD, macOS and Windows to mount any of
-Rclone’s cloud storage systems as a file system with FUSE.
+Rclone's cloud storage systems as a file system with FUSE.
 
 First set up your remote using rclone config. Check it works with
 rclone ls etc.
 
 You can either run mount in foreground mode or background (daemon) mode.
-Mount runs in foreground mode by default, use the –daemon flag to
+Mount runs in foreground mode by default, use the --daemon flag to
 specify background mode mode. Background mode is only supported on Linux
 and OSX, you can only run mount in foreground mode on Windows.
 
@@ -2662,7 +2770,7 @@ receiving a SIGINT or SIGTERM signal, the mount is automatically
 stopped.
 
 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
+When that happens, it is the user's responsibility to stop the mount
 manually.
 
 Stopping the mount manually:
@@ -2718,8 +2826,8 @@ consider mounting rclone remotes as network shares, as Windows expects
 normal drives to be fast and reliable, while cloud storage is far from
 that. See also Limitations section below for more info
 
-Add “–fuse-flag –VolumePrefix=” to your “mount” command, REPLACING
-“SHARE” WITH ANY OTHER NAME OF YOUR CHOICE IF YOU ARE MOUNTING MORE THAN
+Add "--fuse-flag --VolumePrefix=" to your "mount" command, REPLACING
+"SHARE" WITH ANY OTHER NAME OF YOUR CHOICE IF YOU ARE MOUNTING MORE THAN
 ONE REMOTE. Otherwise, the mountpoints will conflict and your mounted
 filesystems will overlap.
 
@@ -2728,11 +2836,11 @@ Read more about drive mapping
 
 Limitations
 
-Without the use of “–vfs-cache-mode” this can only write files
+Without the use of "--vfs-cache-mode" 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
-“–vfs-cache-mode writes” or “–vfs-cache-mode full”. See the File Caching
-section for more info.
+applications won't work with their files on an rclone mount without
+"--vfs-cache-mode writes" or "--vfs-cache-mode full". See the File
+Caching section for more info.
 
 The bucket based remotes (eg Swift, S3, Google Compute Storage, B2,
 Hubic) do not support the concept of empty directories, so empty
@@ -2746,17 +2854,17 @@ rclone mount vs rclone sync/copy
 
 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
+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 file caching for solutions to make mount more reliable.
 
 
 Attribute caching
 
-You can use the flag –attr-timeout to set the time the kernel caches the
-attributes (size, modification time etc) for directory entries.
+You can use the flag --attr-timeout to set the time the kernel caches
+the attributes (size, modification time etc) for directory entries.
 
-The default is “1s” which caches files just long enough to avoid too
+The default is "1s" which caches files just long enough to avoid too
 many callbacks to rclone from the kernel.
 
 In theory 0s should be the correct value for filesystems which can
@@ -2765,18 +2873,18 @@ few problems such as rclone using too much memory, rclone not serving
 files to samba and excessive time listing directories.
 
 The kernel can cache the info about a file for the time given by
-“–attr-timeout”. You may see corruption if the remote file changes
+"--attr-timeout". 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 “–attr-timeout 1s” this is very
-unlikely but not impossible. The higher you set “–attr-timeout” the more
-likely it is. The default setting of “1s” is the lowest setting which
-mitigates the problems above.
+a file with garbage on the end. With "--attr-timeout 1s" this is very
+unlikely but not impossible. The higher you set "--attr-timeout" the
+more likely it is. The default setting of "1s" is the lowest setting
+which mitigates the problems above.
 
-If you set it higher (‘10s’ or ‘1m’ say) then the kernel will call back
+If you set it higher ('10s' or '1m' 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.
 
-If files don’t change on the remote outside of the control of rclone
+If files don't change on the remote outside of the control of rclone
 then there is no chance of corruption.
 
 This is the same as setting the attr_timeout option in mount.fuse.
@@ -2799,40 +2907,62 @@ immediately in this mode.
 
 chunked reading
 
-–vfs-read-chunk-size will enable reading the source objects in parts.
+--vfs-read-chunk-size will enable reading the source objects in parts.
 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.
 
-When –vfs-read-chunk-size-limit is also specified and greater than
-–vfs-read-chunk-size, the chunk size for each open file will get doubled
-for each chunk read, until the specified value is reached. A value of -1
-will disable the limit and the chunk size will grow indefinitely.
+When --vfs-read-chunk-size-limit is also specified and greater than
+--vfs-read-chunk-size, the chunk size for each open file will get
+doubled for each chunk read, until the specified value is reached. A
+value of -1 will disable the limit and the chunk size will grow
+indefinitely.
 
-With –vfs-read-chunk-size 100M and –vfs-read-chunk-size-limit 0 the
+With --vfs-read-chunk-size 100M and --vfs-read-chunk-size-limit 0 the
 following parts will be downloaded: 0-100M, 100M-200M, 200M-300M,
-300M-400M and so on. When –vfs-read-chunk-size-limit 500M is specified,
+300M-400M and so on. When --vfs-read-chunk-size-limit 500M is specified,
 the result would be 0-100M, 100M-300M, 300M-700M, 700M-1200M,
 1200M-1700M and so on.
 
-Chunked reading will only work with –vfs-cache-mode < full, as the file
+Chunked reading will only work with --vfs-cache-mode < full, as the file
 will always be copied to the vfs cache before opening with
-–vfs-cache-mode full.
+--vfs-cache-mode full.
 
 
-Directory Cache
+VFS - Virtual File System
 
-Using the --dir-cache-time flag, you can set how long a directory should
-be considered up to date and not refreshed from the backend. Changes
-made locally in the mount may appear immediately or invalidate the
-cache. However, changes done on the remote will only be picked up once
-the cache expires if the backend configured does not support polling for
-changes. If the backend supports polling, changes will be picked up on
+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.
+
+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.
+
+The VFS layer also implements a directory cache - this caches info about
+files and directories (but not the data) in memory.
+
+
+VFS Directory Cache
+
+Using the --dir-cache-time flag, you can control how long a directory
+should be considered up to date and not refreshed from the backend.
+Changes made through the mount will appear immediately or invalidate the
+cache.
+
+    --dir-cache-time duration   Time to cache directory entries for. (default 5m0s)
+    --poll-interval duration    Time to wait between polling for changes.
+
+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.
 
-Alternatively, you can send a SIGHUP 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:
+You can send a SIGHUP 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:
 
     kill -SIGHUP $(pidof rclone)
 
@@ -2846,40 +2976,41 @@ Or individual files or directories:
     rclone rc vfs/forget file=path/to/file dir=path/to/dir
 
 
-File Buffering
+VFS File Buffering
 
 The --buffer-size flag determines the amount of memory, that will be
 used to buffer data in advance.
 
-Each open file descriptor will try to keep the specified amount of data
-in memory at all times. The buffered data is bound to one file
-descriptor and won’t be shared between multiple open file descriptors of
-the same file.
+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.
 
-This flag is a upper limit for the used memory per file descriptor. 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. The maximum memory used by rclone for buffering can be up to
+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.
+
+The maximum memory used by rclone for buffering can be up to
 --buffer-size * open files.
 
 
-File Caching
+VFS File Caching
 
-These flags control the VFS file caching options. The VFS layer is used
-by rclone mount to make a cloud storage system work more like a normal
-file system.
+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.
 
-You’ll need to enable VFS caching if you want, for example, to read and
+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.
 
-Note that the VFS cache works in addition to the cache backend and you
-may find that you need one or the other or both.
+Note that the VFS cache is separate from the cache backend and you may
+find that you need one or the other or both.
 
     --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 age of objects in the cache. (default 1h0m0s)
-    --vfs-cache-mode string              Cache mode off|minimal|writes|full (default "off")
+    --vfs-cache-max-size SizeSuffix      Max total size of objects in the cache. (default off)
     --vfs-cache-poll-interval duration   Interval to poll the cache for stale objects. (default 1m0s)
-    --vfs-cache-max-size int             Max total size of objects in the cache. (default off)
+    --vfs-write-back duration            Time to writeback files after last use when using cache. (default 5s)
 
 If run with -vv rclone will print the location of the file cache. The
 files are stored in the user cache file area which is OS dependent but
@@ -2891,77 +3022,117 @@ the cache mode the more compatible rclone becomes at the cost of using
 disk space.
 
 Note that files are written back to the remote only when they are closed
-so if rclone is quit or dies with open files then these won’t get
-written back to the remote. However they will still be in the on disk
-cache.
+and if they haven't been accessed for --vfs-write-back second. 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.
 
-If using –vfs-cache-max-size note that the cache may exceed this size
+If using --vfs-cache-max-size note that the cache may exceed this size
 for two reasons. Firstly because it is only checked every
-–vfs-cache-poll-interval. Secondly because open files cannot be evicted
+--vfs-cache-poll-interval. Secondly because open files cannot be evicted
 from the cache.
 
-–vfs-cache-mode off
+--vfs-cache-mode off
 
-In this mode the cache will read directly from the remote and write
-directly to the remote without caching anything on disk.
+In this mode (the default) the cache will read directly from the remote
+and write directly to the remote without caching anything on disk.
 
 This will mean some operations are not possible
 
--   Files can’t be opened for both read AND write
--   Files opened for write can’t be seeked
+-   Files can't be opened for both read AND write
+-   Files opened for write can't be seeked
 -   Existing files opened for write must have O_TRUNC set
 -   Files open for read with O_TRUNC will be opened write only
 -   Files open for write only will behave as if O_TRUNC was supplied
 -   Open modes O_APPEND, O_TRUNC are ignored
--   If an upload fails it can’t be retried
+-   If an upload fails it can't be retried
 
-–vfs-cache-mode minimal
+--vfs-cache-mode minimal
 
-This is very similar to “off” except that files opened for read AND
-write will be buffered to disks. This means that files opened for write
+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.
 
 These operations are not possible
 
--   Files opened for write only can’t be seeked
+-   Files opened for write only can't be seeked
 -   Existing files opened for write must have O_TRUNC set
 -   Files opened for write only will ignore O_APPEND, O_TRUNC
--   If an upload fails it can’t be retried
+-   If an upload fails it can't be retried
 
-–vfs-cache-mode writes
+--vfs-cache-mode writes
 
 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.
 
 This mode should support all normal file system operations.
 
-If an upload fails it will be retried up to –low-level-retries times.
+If an upload fails it will be retried at exponentially increasing
+intervals up to 1 minute.
 
-–vfs-cache-mode full
+--vfs-cache-mode full
 
-In this mode all reads and writes are buffered to and from disk. When a
-file is opened for read it will be downloaded in its entirety first.
+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.
 
-This may be appropriate for your needs, or you may prefer to look at the
-cache backend which does a much more sophisticated job of caching,
-including caching directory hierarchies and chunks of files.
+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 dowloaded.
 
-In this mode, unlike the others, when a file is written to the disk, it
-will be kept on the disk after it is written to the remote. It will be
-purged on a schedule according to --vfs-cache-max-age.
+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.
 
-This mode should support all normal file system operations.
+This mode should support all normal file system operations and is
+otherwise identical to --vfs-cache-mode writes.
 
-If an upload or download fails it will be retried up to
-–low-level-retries times.
+When reading a file rclone will read --buffer-size plus --vfs-read-ahead
+bytes ahead. The --buffer-size is buffered in memory whereas the
+--vfs-read-ahead is buffered on disk.
+
+When using this mode it is recommended that --buffer-size is not set too
+big and --vfs-read-ahead is set large if required.
 
 
-Case Sensitivity
+VFS Performance
+
+These flags may be used to enable/disable features of the VFS for
+performance or other reasons.
+
+In particular S3 and Swift benefit hugely from the --no-modtime flag (or
+use --use-server-modtime for a slightly different effect) as each read
+of the modification time takes a transaction.
+
+    --no-checksum     Don't compare checksums on up/download.
+    --no-modtime      Don't read/write the modification time (can speed things up).
+    --no-seek         Don't allow seeking in files.
+    --read-only       Mount read-only.
+
+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 is advantageous because some cloud providers account for
+reads being all the data requested, not all the data delivered.
+
+Rclone will keep doubling the chunk size requested starting at
+--vfs-read-chunk-size with a maximum of --vfs-read-chunk-size-limit
+unless it is set to "off" in which case there will be no limit.
+
+    --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")
+
+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.
+
+    --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)
+
+
+VFS Case Sensitivity
 
 Linux file systems are case-sensitive: two files can differ only by
 case, and the exact case must be used when opening a file.
 
-Windows is not like most other operating systems supported by rclone.
 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
@@ -2971,10 +3142,11 @@ only by case.
 Usually file systems on macOS are case-insensitive. It is possible to
 make macOS file systems case-sensitive but that is not the default
 
-The “–vfs-case-insensitive” mount flag controls how rclone handles these
-two cases. If its value is “false”, rclone passes file names to the
-mounted file system as is. If the flag is “true” (or appears without a
-value on command line), rclone may perform a “fixup” as explained below.
+The "--vfs-case-insensitive" mount flag controls how rclone handles
+these two cases. If its value is "false", rclone passes file names to
+the mounted file system as-is. If the flag is "true" (or appears without
+a value on command line), rclone may perform a "fixup" as explained
+below.
 
 The user may specify a file name to open/delete/rename/etc with a case
 different than what is stored on mounted file system. If an argument
@@ -2988,13 +3160,13 @@ system.
 
 Note that case sensitivity of the operating system running rclone (the
 target) may differ from case sensitivity of a file system mounted by
-rclone (the source). The flag controls whether “fixup” is performed to
+rclone (the source). The flag controls whether "fixup" is performed to
 satisfy the target.
 
-If the flag is not provided on 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”.
+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".
 
     rclone mount remote:path /path/to/mountpoint [flags]
 
@@ -3030,9 +3202,11 @@ Options
           --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-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 128M)
           --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. 'off' is unlimited. (default off)
           --vfs-read-wait duration                 Time to wait for in-sequence read before seeking. (default 20ms)
+          --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 (not supported by all OSes).
           --write-back-cache                       Makes kernel buffer writes before sending them to rclone. Without this, writethrough caching is used.
@@ -3076,11 +3250,11 @@ This will:
         move it to dst, overwriting existing files if they exist
         see move command for full details
 
-This doesn’t transfer unchanged files, testing by size and modification
+This doesn't transfer unchanged files, testing by size and modification
 time or MD5SUM. src will be deleted on successful transfer.
 
-IMPORTANT: Since this can cause data loss, test first with the –dry-run
-flag.
+IMPORTANT: Since this can cause data loss, test first with the --dry-run
+or the --interactive/-i flag.
 
 NOTE: Use the -P/--progress flag to view real-time transfer statistics.
 
@@ -3109,15 +3283,15 @@ Explore a remote with a text based user interface.
 Synopsis
 
 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?”.
+remote. It is most useful for answering the question - "What is using
+all my disk space?".
 
 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.
 
-Here are the keys - press ‘?’ to toggle the help on and off
+Here are the keys - press '?' to toggle the help on and off
 
      ↑,↓ or k,j to Move
      →,l to enter
@@ -3136,7 +3310,7 @@ This an homage to the ncdu tool but for rclone remotes. It is missing
 lots of features at the moment but is useful as it stands.
 
 Note that it might take some time to delete big files/folders. The UI
-won’t respond in the meantime since the deletion is done synchronously.
+won't respond in the meantime since the deletion is done synchronously.
 
     rclone ncdu remote:path [flags]
 
@@ -3157,12 +3331,31 @@ SEE ALSO
 RCLONE OBSCURE
 
 
-Obscure password for use in the rclone.conf
+Obscure password for use in the rclone config file
 
 
 Synopsis
 
-Obscure password for use in the rclone.conf
+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 NOT 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.
+
+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.
+
+This command can also accept a password through STDIN instead of an
+argument by passing a hyphen as an argument. Example:
+
+echo "secretpassword" | rclone obscure -
+
+If there is no data on STDIN to read, rclone obscure will default to
+obfuscating the hyphen itself.
+
+If you want to encrypt the config file then please use config file
+encryption - see rclone config for more info.
 
     rclone obscure password [flags]
 
@@ -3188,52 +3381,53 @@ Run a command against a running rclone.
 
 Synopsis
 
-This runs a command against a running rclone. Use the –url 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”
+This runs a command against a running rclone. Use the --url 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"
 
-A username and password can be passed in with –user and –pass.
+A username and password can be passed in with --user and --pass.
 
-Note that –rc-addr, –rc-user, –rc-pass will be read also for –url,
-–user, –pass.
+Note that --rc-addr, --rc-user, --rc-pass will be read also for --url,
+--user, --pass.
 
 Arguments should be passed in as parameter=value.
 
 The result will be returned as a JSON object by default.
 
-The –json parameter can be used to pass in a JSON blob as an input
+The --json 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.
 
-The -o/–opt option can be used to set a key “opt” with key, value
-options in the form “-o key=value” or “-o key”. It can be repeated as
+The -o/--opt option can be used to set a key "opt" with key, value
+options in the form "-o key=value" or "-o key". 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.
+"opt" parameter which by convention is a dictionary of strings.
 
     -o key=value -o key2
 
-Will place this in the “opt” value
+Will place this in the "opt" value
 
     {"key":"value", "key2","")
 
-The -a/–arg 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.
+The -a/--arg 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.
 
     -a value -a value2
 
-Will place this in the “arg” value
+Will place this in the "arg" value
 
     ["value", "value2"]
 
-Use –loopback to connect to the rclone instance running “rclone rc”.
+Use --loopback to connect to the rclone instance running "rclone rc".
 This is very useful for testing commands without having to run an rclone
 rc server, eg:
 
     rclone rc --loopback operations/about fs=/
 
-Use “rclone rc” to see a list of all possible commands.
+Use "rclone rc" to see a list of all possible commands.
 
     rclone rc commands parameter [flags]
 
@@ -3286,7 +3480,7 @@ speaking, setting this cutoff too high will decrease your performance.
 
 Note that the upload can also not be retried because the data is not
 kept around until the upload succeeds. If you need to transfer a lot of
-data, you’re better off caching locally and then rclone move it to the
+data, you're better off caching locally and then rclone move it to the
 destination.
 
     rclone rcat remote:path [flags]
@@ -3351,7 +3545,7 @@ This removes any empty directories (or directories that only contain
 empty directories) under the path that it finds, including the path if
 it has nothing in.
 
-If you supply the –leave-root flag, it will not remove the root
+If you supply the --leave-root flag, it will not remove the root
 directory.
 
 This is useful for tidying up remotes that rclone has left a lot of
@@ -3405,7 +3599,7 @@ SEE ALSO
 -   rclone serve dlna - Serve remote:path over DLNA
 -   rclone serve ftp - Serve remote:path over FTP.
 -   rclone serve http - Serve the remote over HTTP.
--   rclone serve restic - Serve the remote for restic’s REST API.
+-   rclone serve restic - Serve the remote for restic's REST API.
 -   rclone serve sftp - Serve the remote over SFTP.
 -   rclone serve webdav - Serve remote:path over webdav.
 
@@ -3433,29 +3627,50 @@ that they are not able to play back correctly.
 
 Server options
 
-Use –addr to specify which IP address and port the server should listen
-on, eg –addr 1.2.3.4:8000 or –addr :8080 to listen to all IPs.
+Use --addr to specify which IP address and port the server should listen
+on, eg --addr 1.2.3.4:8000 or --addr :8080 to listen to all IPs.
 
-Use –name to choose the friendly server name, which is by default
-“rclone (hostname)”.
+Use --name to choose the friendly server name, which is by default
+"rclone (hostname)".
 
-Use –log-trace in conjunction with -vv to enable additional debug
+Use --log-trace in conjunction with -vv to enable additional debug
 logging of all UPNP traffic.
 
 
-Directory Cache
+VFS - Virtual File System
 
-Using the --dir-cache-time flag, you can set how long a directory should
-be considered up to date and not refreshed from the backend. Changes
-made locally in the mount may appear immediately or invalidate the
-cache. However, changes done on the remote will only be picked up once
-the cache expires if the backend configured does not support polling for
-changes. If the backend supports polling, changes will be picked up on
+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.
+
+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.
+
+The VFS layer also implements a directory cache - this caches info about
+files and directories (but not the data) in memory.
+
+
+VFS Directory Cache
+
+Using the --dir-cache-time flag, you can control how long a directory
+should be considered up to date and not refreshed from the backend.
+Changes made through the mount will appear immediately or invalidate the
+cache.
+
+    --dir-cache-time duration   Time to cache directory entries for. (default 5m0s)
+    --poll-interval duration    Time to wait between polling for changes.
+
+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.
 
-Alternatively, you can send a SIGHUP 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:
+You can send a SIGHUP 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:
 
     kill -SIGHUP $(pidof rclone)
 
@@ -3469,40 +3684,41 @@ Or individual files or directories:
     rclone rc vfs/forget file=path/to/file dir=path/to/dir
 
 
-File Buffering
+VFS File Buffering
 
 The --buffer-size flag determines the amount of memory, that will be
 used to buffer data in advance.
 
-Each open file descriptor will try to keep the specified amount of data
-in memory at all times. The buffered data is bound to one file
-descriptor and won’t be shared between multiple open file descriptors of
-the same file.
+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.
 
-This flag is a upper limit for the used memory per file descriptor. 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. The maximum memory used by rclone for buffering can be up to
+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.
+
+The maximum memory used by rclone for buffering can be up to
 --buffer-size * open files.
 
 
-File Caching
+VFS File Caching
 
-These flags control the VFS file caching options. The VFS layer is used
-by rclone mount to make a cloud storage system work more like a normal
-file system.
+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.
 
-You’ll need to enable VFS caching if you want, for example, to read and
+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.
 
-Note that the VFS cache works in addition to the cache backend and you
-may find that you need one or the other or both.
+Note that the VFS cache is separate from the cache backend and you may
+find that you need one or the other or both.
 
     --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 age of objects in the cache. (default 1h0m0s)
-    --vfs-cache-mode string              Cache mode off|minimal|writes|full (default "off")
+    --vfs-cache-max-size SizeSuffix      Max total size of objects in the cache. (default off)
     --vfs-cache-poll-interval duration   Interval to poll the cache for stale objects. (default 1m0s)
-    --vfs-cache-max-size int             Max total size of objects in the cache. (default off)
+    --vfs-write-back duration            Time to writeback files after last use when using cache. (default 5s)
 
 If run with -vv rclone will print the location of the file cache. The
 files are stored in the user cache file area which is OS dependent but
@@ -3514,77 +3730,117 @@ the cache mode the more compatible rclone becomes at the cost of using
 disk space.
 
 Note that files are written back to the remote only when they are closed
-so if rclone is quit or dies with open files then these won’t get
-written back to the remote. However they will still be in the on disk
-cache.
+and if they haven't been accessed for --vfs-write-back second. 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.
 
-If using –vfs-cache-max-size note that the cache may exceed this size
+If using --vfs-cache-max-size note that the cache may exceed this size
 for two reasons. Firstly because it is only checked every
-–vfs-cache-poll-interval. Secondly because open files cannot be evicted
+--vfs-cache-poll-interval. Secondly because open files cannot be evicted
 from the cache.
 
-–vfs-cache-mode off
+--vfs-cache-mode off
 
-In this mode the cache will read directly from the remote and write
-directly to the remote without caching anything on disk.
+In this mode (the default) the cache will read directly from the remote
+and write directly to the remote without caching anything on disk.
 
 This will mean some operations are not possible
 
--   Files can’t be opened for both read AND write
--   Files opened for write can’t be seeked
+-   Files can't be opened for both read AND write
+-   Files opened for write can't be seeked
 -   Existing files opened for write must have O_TRUNC set
 -   Files open for read with O_TRUNC will be opened write only
 -   Files open for write only will behave as if O_TRUNC was supplied
 -   Open modes O_APPEND, O_TRUNC are ignored
--   If an upload fails it can’t be retried
+-   If an upload fails it can't be retried
 
-–vfs-cache-mode minimal
+--vfs-cache-mode minimal
 
-This is very similar to “off” except that files opened for read AND
-write will be buffered to disks. This means that files opened for write
+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.
 
 These operations are not possible
 
--   Files opened for write only can’t be seeked
+-   Files opened for write only can't be seeked
 -   Existing files opened for write must have O_TRUNC set
 -   Files opened for write only will ignore O_APPEND, O_TRUNC
--   If an upload fails it can’t be retried
+-   If an upload fails it can't be retried
 
-–vfs-cache-mode writes
+--vfs-cache-mode writes
 
 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.
 
 This mode should support all normal file system operations.
 
-If an upload fails it will be retried up to –low-level-retries times.
+If an upload fails it will be retried at exponentially increasing
+intervals up to 1 minute.
 
-–vfs-cache-mode full
+--vfs-cache-mode full
 
-In this mode all reads and writes are buffered to and from disk. When a
-file is opened for read it will be downloaded in its entirety first.
+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.
 
-This may be appropriate for your needs, or you may prefer to look at the
-cache backend which does a much more sophisticated job of caching,
-including caching directory hierarchies and chunks of files.
+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 dowloaded.
 
-In this mode, unlike the others, when a file is written to the disk, it
-will be kept on the disk after it is written to the remote. It will be
-purged on a schedule according to --vfs-cache-max-age.
+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.
 
-This mode should support all normal file system operations.
+This mode should support all normal file system operations and is
+otherwise identical to --vfs-cache-mode writes.
 
-If an upload or download fails it will be retried up to
-–low-level-retries times.
+When reading a file rclone will read --buffer-size plus --vfs-read-ahead
+bytes ahead. The --buffer-size is buffered in memory whereas the
+--vfs-read-ahead is buffered on disk.
+
+When using this mode it is recommended that --buffer-size is not set too
+big and --vfs-read-ahead is set large if required.
 
 
-Case Sensitivity
+VFS Performance
+
+These flags may be used to enable/disable features of the VFS for
+performance or other reasons.
+
+In particular S3 and Swift benefit hugely from the --no-modtime flag (or
+use --use-server-modtime for a slightly different effect) as each read
+of the modification time takes a transaction.
+
+    --no-checksum     Don't compare checksums on up/download.
+    --no-modtime      Don't read/write the modification time (can speed things up).
+    --no-seek         Don't allow seeking in files.
+    --read-only       Mount read-only.
+
+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 is advantageous because some cloud providers account for
+reads being all the data requested, not all the data delivered.
+
+Rclone will keep doubling the chunk size requested starting at
+--vfs-read-chunk-size with a maximum of --vfs-read-chunk-size-limit
+unless it is set to "off" in which case there will be no limit.
+
+    --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")
+
+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.
+
+    --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)
+
+
+VFS Case Sensitivity
 
 Linux file systems are case-sensitive: two files can differ only by
 case, and the exact case must be used when opening a file.
 
-Windows is not like most other operating systems supported by rclone.
 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
@@ -3594,10 +3850,11 @@ only by case.
 Usually file systems on macOS are case-insensitive. It is possible to
 make macOS file systems case-sensitive but that is not the default
 
-The “–vfs-case-insensitive” mount flag controls how rclone handles these
-two cases. If its value is “false”, rclone passes file names to the
-mounted file system as is. If the flag is “true” (or appears without a
-value on command line), rclone may perform a “fixup” as explained below.
+The "--vfs-case-insensitive" mount flag controls how rclone handles
+these two cases. If its value is "false", rclone passes file names to
+the mounted file system as-is. If the flag is "true" (or appears without
+a value on command line), rclone may perform a "fixup" as explained
+below.
 
 The user may specify a file name to open/delete/rename/etc with a case
 different than what is stored on mounted file system. If an argument
@@ -3611,13 +3868,13 @@ system.
 
 Note that case sensitivity of the operating system running rclone (the
 target) may differ from case sensitivity of a file system mounted by
-rclone (the source). The flag controls whether “fixup” is performed to
+rclone (the source). The flag controls whether "fixup" is performed to
 satisfy the target.
 
-If the flag is not provided on 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”.
+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".
 
     rclone serve dlna remote:path [flags]
 
@@ -3644,9 +3901,11 @@ Options
           --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-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 128M)
           --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. 'off' is unlimited. (default off)
           --vfs-read-wait duration                 Time to wait for in-sequence read before seeking. (default 20ms)
+          --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)
 
 See the global flags page for global options not listed here.
@@ -3673,35 +3932,56 @@ remote of type ftp to read and write it.
 
 Server options
 
-Use –addr to specify which IP address and port the server should listen
-on, eg –addr 1.2.3.4:8000 or –addr :8080 to listen to all IPs. By
+Use --addr to specify which IP address and port the server should listen
+on, eg --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.
 
-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.
+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.
 
 Authentication
 
 By default this will serve files without needing a login.
 
-You can set a single username and password with the –user and –pass
+You can set a single username and password with the --user and --pass
 flags.
 
 
-Directory Cache
+VFS - Virtual File System
 
-Using the --dir-cache-time flag, you can set how long a directory should
-be considered up to date and not refreshed from the backend. Changes
-made locally in the mount may appear immediately or invalidate the
-cache. However, changes done on the remote will only be picked up once
-the cache expires if the backend configured does not support polling for
-changes. If the backend supports polling, changes will be picked up on
+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.
+
+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.
+
+The VFS layer also implements a directory cache - this caches info about
+files and directories (but not the data) in memory.
+
+
+VFS Directory Cache
+
+Using the --dir-cache-time flag, you can control how long a directory
+should be considered up to date and not refreshed from the backend.
+Changes made through the mount will appear immediately or invalidate the
+cache.
+
+    --dir-cache-time duration   Time to cache directory entries for. (default 5m0s)
+    --poll-interval duration    Time to wait between polling for changes.
+
+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.
 
-Alternatively, you can send a SIGHUP 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:
+You can send a SIGHUP 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:
 
     kill -SIGHUP $(pidof rclone)
 
@@ -3715,40 +3995,41 @@ Or individual files or directories:
     rclone rc vfs/forget file=path/to/file dir=path/to/dir
 
 
-File Buffering
+VFS File Buffering
 
 The --buffer-size flag determines the amount of memory, that will be
 used to buffer data in advance.
 
-Each open file descriptor will try to keep the specified amount of data
-in memory at all times. The buffered data is bound to one file
-descriptor and won’t be shared between multiple open file descriptors of
-the same file.
+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.
 
-This flag is a upper limit for the used memory per file descriptor. 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. The maximum memory used by rclone for buffering can be up to
+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.
+
+The maximum memory used by rclone for buffering can be up to
 --buffer-size * open files.
 
 
-File Caching
+VFS File Caching
 
-These flags control the VFS file caching options. The VFS layer is used
-by rclone mount to make a cloud storage system work more like a normal
-file system.
+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.
 
-You’ll need to enable VFS caching if you want, for example, to read and
+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.
 
-Note that the VFS cache works in addition to the cache backend and you
-may find that you need one or the other or both.
+Note that the VFS cache is separate from the cache backend and you may
+find that you need one or the other or both.
 
     --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 age of objects in the cache. (default 1h0m0s)
-    --vfs-cache-mode string              Cache mode off|minimal|writes|full (default "off")
+    --vfs-cache-max-size SizeSuffix      Max total size of objects in the cache. (default off)
     --vfs-cache-poll-interval duration   Interval to poll the cache for stale objects. (default 1m0s)
-    --vfs-cache-max-size int             Max total size of objects in the cache. (default off)
+    --vfs-write-back duration            Time to writeback files after last use when using cache. (default 5s)
 
 If run with -vv rclone will print the location of the file cache. The
 files are stored in the user cache file area which is OS dependent but
@@ -3760,77 +4041,117 @@ the cache mode the more compatible rclone becomes at the cost of using
 disk space.
 
 Note that files are written back to the remote only when they are closed
-so if rclone is quit or dies with open files then these won’t get
-written back to the remote. However they will still be in the on disk
-cache.
+and if they haven't been accessed for --vfs-write-back second. 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.
 
-If using –vfs-cache-max-size note that the cache may exceed this size
+If using --vfs-cache-max-size note that the cache may exceed this size
 for two reasons. Firstly because it is only checked every
-–vfs-cache-poll-interval. Secondly because open files cannot be evicted
+--vfs-cache-poll-interval. Secondly because open files cannot be evicted
 from the cache.
 
-–vfs-cache-mode off
+--vfs-cache-mode off
 
-In this mode the cache will read directly from the remote and write
-directly to the remote without caching anything on disk.
+In this mode (the default) the cache will read directly from the remote
+and write directly to the remote without caching anything on disk.
 
 This will mean some operations are not possible
 
--   Files can’t be opened for both read AND write
--   Files opened for write can’t be seeked
+-   Files can't be opened for both read AND write
+-   Files opened for write can't be seeked
 -   Existing files opened for write must have O_TRUNC set
 -   Files open for read with O_TRUNC will be opened write only
 -   Files open for write only will behave as if O_TRUNC was supplied
 -   Open modes O_APPEND, O_TRUNC are ignored
--   If an upload fails it can’t be retried
+-   If an upload fails it can't be retried
 
-–vfs-cache-mode minimal
+--vfs-cache-mode minimal
 
-This is very similar to “off” except that files opened for read AND
-write will be buffered to disks. This means that files opened for write
+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.
 
 These operations are not possible
 
--   Files opened for write only can’t be seeked
+-   Files opened for write only can't be seeked
 -   Existing files opened for write must have O_TRUNC set
 -   Files opened for write only will ignore O_APPEND, O_TRUNC
--   If an upload fails it can’t be retried
+-   If an upload fails it can't be retried
 
-–vfs-cache-mode writes
+--vfs-cache-mode writes
 
 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.
 
 This mode should support all normal file system operations.
 
-If an upload fails it will be retried up to –low-level-retries times.
+If an upload fails it will be retried at exponentially increasing
+intervals up to 1 minute.
 
-–vfs-cache-mode full
+--vfs-cache-mode full
 
-In this mode all reads and writes are buffered to and from disk. When a
-file is opened for read it will be downloaded in its entirety first.
+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.
 
-This may be appropriate for your needs, or you may prefer to look at the
-cache backend which does a much more sophisticated job of caching,
-including caching directory hierarchies and chunks of files.
+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 dowloaded.
 
-In this mode, unlike the others, when a file is written to the disk, it
-will be kept on the disk after it is written to the remote. It will be
-purged on a schedule according to --vfs-cache-max-age.
+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.
 
-This mode should support all normal file system operations.
+This mode should support all normal file system operations and is
+otherwise identical to --vfs-cache-mode writes.
 
-If an upload or download fails it will be retried up to
-–low-level-retries times.
+When reading a file rclone will read --buffer-size plus --vfs-read-ahead
+bytes ahead. The --buffer-size is buffered in memory whereas the
+--vfs-read-ahead is buffered on disk.
+
+When using this mode it is recommended that --buffer-size is not set too
+big and --vfs-read-ahead is set large if required.
 
 
-Case Sensitivity
+VFS Performance
+
+These flags may be used to enable/disable features of the VFS for
+performance or other reasons.
+
+In particular S3 and Swift benefit hugely from the --no-modtime flag (or
+use --use-server-modtime for a slightly different effect) as each read
+of the modification time takes a transaction.
+
+    --no-checksum     Don't compare checksums on up/download.
+    --no-modtime      Don't read/write the modification time (can speed things up).
+    --no-seek         Don't allow seeking in files.
+    --read-only       Mount read-only.
+
+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 is advantageous because some cloud providers account for
+reads being all the data requested, not all the data delivered.
+
+Rclone will keep doubling the chunk size requested starting at
+--vfs-read-chunk-size with a maximum of --vfs-read-chunk-size-limit
+unless it is set to "off" in which case there will be no limit.
+
+    --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")
+
+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.
+
+    --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)
+
+
+VFS Case Sensitivity
 
 Linux file systems are case-sensitive: two files can differ only by
 case, and the exact case must be used when opening a file.
 
-Windows is not like most other operating systems supported by rclone.
 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
@@ -3840,10 +4161,11 @@ only by case.
 Usually file systems on macOS are case-insensitive. It is possible to
 make macOS file systems case-sensitive but that is not the default
 
-The “–vfs-case-insensitive” mount flag controls how rclone handles these
-two cases. If its value is “false”, rclone passes file names to the
-mounted file system as is. If the flag is “true” (or appears without a
-value on command line), rclone may perform a “fixup” as explained below.
+The "--vfs-case-insensitive" mount flag controls how rclone handles
+these two cases. If its value is "false", rclone passes file names to
+the mounted file system as-is. If the flag is "true" (or appears without
+a value on command line), rclone may perform a "fixup" as explained
+below.
 
 The user may specify a file name to open/delete/rename/etc with a case
 different than what is stored on mounted file system. If an argument
@@ -3857,13 +4179,13 @@ system.
 
 Note that case sensitivity of the operating system running rclone (the
 target) may differ from case sensitivity of a file system mounted by
-rclone (the source). The flag controls whether “fixup” is performed to
+rclone (the source). The flag controls whether "fixup" is performed to
 satisfy the target.
 
-If the flag is not provided on 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”.
+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".
 
 
 Auth Proxy
@@ -3878,9 +4200,9 @@ if --auth-proxy is set the authorized keys option will be ignored.
 
 There is an example program bin/test_proxy.py in the rclone source code.
 
-The program’s job is to take a user and pass on the input and turn those
+The program's job is to take a user and pass 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
+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.
 
@@ -3926,12 +4248,12 @@ backends).
 The program can manipulate the supplied user in any way, for example to
 make proxy to many different sftp backends, you could make the user be
 user@example.com and then set the host to example.com in the output and
-the user to user. For security you’d probably want to restrict the host
+the user to user. For security you'd probably want to restrict the host
 to a limited list.
 
 Note that an internal cache is keyed on user so only use that for
-configuration, don’t use pass or public_key. This also means that if a
-user’s password or public-key is changed the cache will need to expire
+configuration, don't use pass or public_key. 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.
 
 This can be used to build general purpose proxies to any kind of backend
@@ -3965,9 +4287,11 @@ Options
           --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-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 128M)
           --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. 'off' is unlimited. (default off)
           --vfs-read-wait duration                 Time to wait for in-sequence read before seeking. (default 20ms)
+          --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)
 
 See the global flags page for global options not listed here.
@@ -3991,42 +4315,42 @@ rclone serve http implements a basic web server to serve the remote over
 HTTP. This can be viewed in a web browser or you can make a remote of
 type http read from it.
 
-You can use the filter flags (eg –include, –exclude) to control what is
-served.
+You can use the filter flags (eg --include, --exclude) to control what
+is served.
 
 The server will log errors. Use -v to see access logs.
 
-–bwlimit will be respected for file transfers. Use –stats to control the
-stats printing.
+--bwlimit will be respected for file transfers. Use --stats to control
+the stats printing.
 
 
 Server options
 
-Use –addr to specify which IP address and port the server should listen
-on, eg –addr 1.2.3.4:8000 or –addr :8080 to listen to all IPs. By
+Use --addr to specify which IP address and port the server should listen
+on, eg --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.
 
-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.
+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.
 
-–server-read-timeout and –server-write-timeout can be used to control
+--server-read-timeout and --server-write-timeout can be used to control
 the timeouts on the server. Note that this is the total time for a
 transfer.
 
-–max-header-bytes controls the maximum number of bytes the server will
+--max-header-bytes controls the maximum number of bytes the server will
 accept in the HTTP header.
 
-–baseurl controls the URL prefix that rclone serves from. By default
-rclone will serve from the root. If you used –baseurl “/rclone” then
-rclone would serve from a URL starting with “/rclone/”. This is useful
+--baseurl controls the URL prefix that rclone serves from. By default
+rclone will serve from the root. If you used --baseurl "/rclone" 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 –baseurl, so –baseurl “rclone”, –baseurl “/rclone”
-and –baseurl “/rclone/” are all treated identically.
+and trailing "/" on --baseurl, so --baseurl "rclone", --baseurl
+"/rclone" and --baseurl "/rclone/" are all treated identically.
 
-–template 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:
+--template 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:
 
   -----------------------------------------------------------------------
   Parameter                           Description
@@ -4053,25 +4377,25 @@ used within the template to server pages:
   .Breadcrumb                         Allows for creating a relative
                                       navigation
 
-  – .Link                             The relative to the root link of
+  -- .Link                            The relative to the root link of
                                       the Text.
 
-  – .Text                             The Name of the directory.
+  -- .Text                            The Name of the directory.
 
   .Entries                            Information about a specific
                                       file/directory.
 
-  – .URL                              The ‘url’ of an entry.
+  -- .URL                             The 'url' of an entry.
 
-  – .Leaf                             Currently same as ‘URL’ but
-                                      intended to be ‘just’ the name.
+  -- .Leaf                            Currently same as 'URL' but
+                                      intended to be 'just' the name.
 
-  – .IsDir                            Boolean for if an entry is a
+  -- .IsDir                           Boolean for if an entry is a
                                       directory or not.
 
-  – .Size                             Size in Bytes of the entry.
+  -- .Size                            Size in Bytes of the entry.
 
-  – .ModTime                          The UTC timestamp of an entry.
+  -- .ModTime                         The UTC timestamp of an entry.
   -----------------------------------------------------------------------
 
 Authentication
@@ -4079,9 +4403,9 @@ Authentication
 By default this will serve files without needing a login.
 
 You can either use an htpasswd file which can take lots of users, or set
-a single username and password with the –user and –pass flags.
+a single username and password with the --user and --pass flags.
 
-Use –htpasswd /path/to/htpasswd to provide an htpasswd file. This is in
+Use --htpasswd /path/to/htpasswd to provide an htpasswd file. This is in
 standard apache format and supports MD5, SHA1 and BCrypt for basic
 authentication. Bcrypt is recommended.
 
@@ -4093,34 +4417,55 @@ To create an htpasswd file:
 
 The password file can be updated while rclone is running.
 
-Use –realm to set the authentication realm.
+Use --realm to set the authentication realm.
 
 SSL/TLS
 
 By default this will serve over http. If you want you can serve over
-https. You will need to supply the –cert and –key flags. If you wish to
-do client side certificate validation then you will need to supply
-–client-ca also.
+https. You will need to supply the --cert and --key flags. If you wish
+to do client side certificate validation then you will need to supply
+--client-ca also.
 
-–cert should be either a PEM encoded certificate or a concatenation of
-that with the CA certificate. –key should be the PEM encoded private key
-and –client-ca should be the PEM encoded client certificate authority
-certificate.
+--cert should be either a PEM encoded certificate or a concatenation of
+that with the CA certificate. --key should be the PEM encoded private
+key and --client-ca should be the PEM encoded client certificate
+authority certificate.
 
 
-Directory Cache
+VFS - Virtual File System
 
-Using the --dir-cache-time flag, you can set how long a directory should
-be considered up to date and not refreshed from the backend. Changes
-made locally in the mount may appear immediately or invalidate the
-cache. However, changes done on the remote will only be picked up once
-the cache expires if the backend configured does not support polling for
-changes. If the backend supports polling, changes will be picked up on
+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.
+
+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.
+
+The VFS layer also implements a directory cache - this caches info about
+files and directories (but not the data) in memory.
+
+
+VFS Directory Cache
+
+Using the --dir-cache-time flag, you can control how long a directory
+should be considered up to date and not refreshed from the backend.
+Changes made through the mount will appear immediately or invalidate the
+cache.
+
+    --dir-cache-time duration   Time to cache directory entries for. (default 5m0s)
+    --poll-interval duration    Time to wait between polling for changes.
+
+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.
 
-Alternatively, you can send a SIGHUP 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:
+You can send a SIGHUP 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:
 
     kill -SIGHUP $(pidof rclone)
 
@@ -4134,40 +4479,41 @@ Or individual files or directories:
     rclone rc vfs/forget file=path/to/file dir=path/to/dir
 
 
-File Buffering
+VFS File Buffering
 
 The --buffer-size flag determines the amount of memory, that will be
 used to buffer data in advance.
 
-Each open file descriptor will try to keep the specified amount of data
-in memory at all times. The buffered data is bound to one file
-descriptor and won’t be shared between multiple open file descriptors of
-the same file.
+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.
 
-This flag is a upper limit for the used memory per file descriptor. 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. The maximum memory used by rclone for buffering can be up to
+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.
+
+The maximum memory used by rclone for buffering can be up to
 --buffer-size * open files.
 
 
-File Caching
+VFS File Caching
 
-These flags control the VFS file caching options. The VFS layer is used
-by rclone mount to make a cloud storage system work more like a normal
-file system.
+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.
 
-You’ll need to enable VFS caching if you want, for example, to read and
+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.
 
-Note that the VFS cache works in addition to the cache backend and you
-may find that you need one or the other or both.
+Note that the VFS cache is separate from the cache backend and you may
+find that you need one or the other or both.
 
     --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 age of objects in the cache. (default 1h0m0s)
-    --vfs-cache-mode string              Cache mode off|minimal|writes|full (default "off")
+    --vfs-cache-max-size SizeSuffix      Max total size of objects in the cache. (default off)
     --vfs-cache-poll-interval duration   Interval to poll the cache for stale objects. (default 1m0s)
-    --vfs-cache-max-size int             Max total size of objects in the cache. (default off)
+    --vfs-write-back duration            Time to writeback files after last use when using cache. (default 5s)
 
 If run with -vv rclone will print the location of the file cache. The
 files are stored in the user cache file area which is OS dependent but
@@ -4179,77 +4525,117 @@ the cache mode the more compatible rclone becomes at the cost of using
 disk space.
 
 Note that files are written back to the remote only when they are closed
-so if rclone is quit or dies with open files then these won’t get
-written back to the remote. However they will still be in the on disk
-cache.
+and if they haven't been accessed for --vfs-write-back second. 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.
 
-If using –vfs-cache-max-size note that the cache may exceed this size
+If using --vfs-cache-max-size note that the cache may exceed this size
 for two reasons. Firstly because it is only checked every
-–vfs-cache-poll-interval. Secondly because open files cannot be evicted
+--vfs-cache-poll-interval. Secondly because open files cannot be evicted
 from the cache.
 
-–vfs-cache-mode off
+--vfs-cache-mode off
 
-In this mode the cache will read directly from the remote and write
-directly to the remote without caching anything on disk.
+In this mode (the default) the cache will read directly from the remote
+and write directly to the remote without caching anything on disk.
 
 This will mean some operations are not possible
 
--   Files can’t be opened for both read AND write
--   Files opened for write can’t be seeked
+-   Files can't be opened for both read AND write
+-   Files opened for write can't be seeked
 -   Existing files opened for write must have O_TRUNC set
 -   Files open for read with O_TRUNC will be opened write only
 -   Files open for write only will behave as if O_TRUNC was supplied
 -   Open modes O_APPEND, O_TRUNC are ignored
--   If an upload fails it can’t be retried
+-   If an upload fails it can't be retried
 
-–vfs-cache-mode minimal
+--vfs-cache-mode minimal
 
-This is very similar to “off” except that files opened for read AND
-write will be buffered to disks. This means that files opened for write
+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.
 
 These operations are not possible
 
--   Files opened for write only can’t be seeked
+-   Files opened for write only can't be seeked
 -   Existing files opened for write must have O_TRUNC set
 -   Files opened for write only will ignore O_APPEND, O_TRUNC
--   If an upload fails it can’t be retried
+-   If an upload fails it can't be retried
 
-–vfs-cache-mode writes
+--vfs-cache-mode writes
 
 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.
 
 This mode should support all normal file system operations.
 
-If an upload fails it will be retried up to –low-level-retries times.
+If an upload fails it will be retried at exponentially increasing
+intervals up to 1 minute.
 
-–vfs-cache-mode full
+--vfs-cache-mode full
 
-In this mode all reads and writes are buffered to and from disk. When a
-file is opened for read it will be downloaded in its entirety first.
+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.
 
-This may be appropriate for your needs, or you may prefer to look at the
-cache backend which does a much more sophisticated job of caching,
-including caching directory hierarchies and chunks of files.
+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 dowloaded.
 
-In this mode, unlike the others, when a file is written to the disk, it
-will be kept on the disk after it is written to the remote. It will be
-purged on a schedule according to --vfs-cache-max-age.
+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.
 
-This mode should support all normal file system operations.
+This mode should support all normal file system operations and is
+otherwise identical to --vfs-cache-mode writes.
 
-If an upload or download fails it will be retried up to
-–low-level-retries times.
+When reading a file rclone will read --buffer-size plus --vfs-read-ahead
+bytes ahead. The --buffer-size is buffered in memory whereas the
+--vfs-read-ahead is buffered on disk.
+
+When using this mode it is recommended that --buffer-size is not set too
+big and --vfs-read-ahead is set large if required.
 
 
-Case Sensitivity
+VFS Performance
+
+These flags may be used to enable/disable features of the VFS for
+performance or other reasons.
+
+In particular S3 and Swift benefit hugely from the --no-modtime flag (or
+use --use-server-modtime for a slightly different effect) as each read
+of the modification time takes a transaction.
+
+    --no-checksum     Don't compare checksums on up/download.
+    --no-modtime      Don't read/write the modification time (can speed things up).
+    --no-seek         Don't allow seeking in files.
+    --read-only       Mount read-only.
+
+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 is advantageous because some cloud providers account for
+reads being all the data requested, not all the data delivered.
+
+Rclone will keep doubling the chunk size requested starting at
+--vfs-read-chunk-size with a maximum of --vfs-read-chunk-size-limit
+unless it is set to "off" in which case there will be no limit.
+
+    --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")
+
+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.
+
+    --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)
+
+
+VFS Case Sensitivity
 
 Linux file systems are case-sensitive: two files can differ only by
 case, and the exact case must be used when opening a file.
 
-Windows is not like most other operating systems supported by rclone.
 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
@@ -4259,10 +4645,11 @@ only by case.
 Usually file systems on macOS are case-insensitive. It is possible to
 make macOS file systems case-sensitive but that is not the default
 
-The “–vfs-case-insensitive” mount flag controls how rclone handles these
-two cases. If its value is “false”, rclone passes file names to the
-mounted file system as is. If the flag is “true” (or appears without a
-value on command line), rclone may perform a “fixup” as explained below.
+The "--vfs-case-insensitive" mount flag controls how rclone handles
+these two cases. If its value is "false", rclone passes file names to
+the mounted file system as-is. If the flag is "true" (or appears without
+a value on command line), rclone may perform a "fixup" as explained
+below.
 
 The user may specify a file name to open/delete/rename/etc with a case
 different than what is stored on mounted file system. If an argument
@@ -4276,13 +4663,13 @@ system.
 
 Note that case sensitivity of the operating system running rclone (the
 target) may differ from case sensitivity of a file system mounted by
-rclone (the source). The flag controls whether “fixup” is performed to
+rclone (the source). The flag controls whether "fixup" is performed to
 satisfy the target.
 
-If the flag is not provided on 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”.
+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".
 
     rclone serve http remote:path [flags]
 
@@ -4319,9 +4706,11 @@ Options
           --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-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 128M)
           --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. 'off' is unlimited. (default off)
           --vfs-read-wait duration                 Time to wait for in-sequence read before seeking. (default 20ms)
+          --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)
 
 See the global flags page for global options not listed here.
@@ -4336,12 +4725,12 @@ SEE ALSO
 RCLONE SERVE RESTIC
 
 
-Serve the remote for restic’s REST API.
+Serve the remote for restic's REST API.
 
 
 Synopsis
 
-rclone serve restic implements restic’s REST backend API over HTTP. This
+rclone serve restic implements 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.
 
@@ -4349,8 +4738,8 @@ Restic is a command line program for doing backups.
 
 The server will log errors. Use -v to see access logs.
 
-–bwlimit will be respected for file transfers. Use –stats to control the
-stats printing.
+--bwlimit will be respected for file transfers. Use --stats to control
+the stats printing.
 
 
 Setting up rclone for use by restic
@@ -4358,19 +4747,19 @@ Setting up rclone for use by restic
 First set up a remote for your chosen cloud provider.
 
 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
+"rclone lsd remote:". You may have called the remote something other
+than "remote:" - just substitute whatever you called it in the following
 instructions.
 
 Now start the rclone restic server
 
     rclone serve restic -v remote:backup
 
-Where you can replace “backup” in the above by whatever path in the
+Where you can replace "backup" in the above by whatever path in the
 remote you wish to use.
 
-By default this will serve on “localhost:8080” you can change this with
-use of the “–addr” flag.
+By default this will serve on "localhost:8080" you can change this with
+use of the "--addr" flag.
 
 You might wish to start this server on boot.
 
@@ -4382,7 +4771,7 @@ Now you can follow the restic instructions on setting up restic.
 Note that you will need restic 0.8.2 or later to interoperate with
 rclone.
 
-For the example above you will want to use “http://localhost:8080/” as
+For the example above you will want to use "http://localhost:8080/" as
 the URL for the REST server.
 
 For example:
@@ -4415,37 +4804,37 @@ MUST end with /. Eg
 
 Private repositories
 
-The “–private-repos” flag can be used to limit users to repositories
+The "--private-repos" flag can be used to limit users to repositories
 starting with a path of /<username>/.
 
 
 Server options
 
-Use –addr to specify which IP address and port the server should listen
-on, eg –addr 1.2.3.4:8000 or –addr :8080 to listen to all IPs. By
+Use --addr to specify which IP address and port the server should listen
+on, eg --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.
 
-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.
+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.
 
-–server-read-timeout and –server-write-timeout can be used to control
+--server-read-timeout and --server-write-timeout can be used to control
 the timeouts on the server. Note that this is the total time for a
 transfer.
 
-–max-header-bytes controls the maximum number of bytes the server will
+--max-header-bytes controls the maximum number of bytes the server will
 accept in the HTTP header.
 
-–baseurl controls the URL prefix that rclone serves from. By default
-rclone will serve from the root. If you used –baseurl “/rclone” then
-rclone would serve from a URL starting with “/rclone/”. This is useful
+--baseurl controls the URL prefix that rclone serves from. By default
+rclone will serve from the root. If you used --baseurl "/rclone" 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 –baseurl, so –baseurl “rclone”, –baseurl “/rclone”
-and –baseurl “/rclone/” are all treated identically.
+and trailing "/" on --baseurl, so --baseurl "rclone", --baseurl
+"/rclone" and --baseurl "/rclone/" are all treated identically.
 
-–template 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:
+--template 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:
 
   -----------------------------------------------------------------------
   Parameter                           Description
@@ -4472,25 +4861,25 @@ used within the template to server pages:
   .Breadcrumb                         Allows for creating a relative
                                       navigation
 
-  – .Link                             The relative to the root link of
+  -- .Link                            The relative to the root link of
                                       the Text.
 
-  – .Text                             The Name of the directory.
+  -- .Text                            The Name of the directory.
 
   .Entries                            Information about a specific
                                       file/directory.
 
-  – .URL                              The ‘url’ of an entry.
+  -- .URL                             The 'url' of an entry.
 
-  – .Leaf                             Currently same as ‘URL’ but
-                                      intended to be ‘just’ the name.
+  -- .Leaf                            Currently same as 'URL' but
+                                      intended to be 'just' the name.
 
-  – .IsDir                            Boolean for if an entry is a
+  -- .IsDir                           Boolean for if an entry is a
                                       directory or not.
 
-  – .Size                             Size in Bytes of the entry.
+  -- .Size                            Size in Bytes of the entry.
 
-  – .ModTime                          The UTC timestamp of an entry.
+  -- .ModTime                         The UTC timestamp of an entry.
   -----------------------------------------------------------------------
 
 Authentication
@@ -4498,9 +4887,9 @@ Authentication
 By default this will serve files without needing a login.
 
 You can either use an htpasswd file which can take lots of users, or set
-a single username and password with the –user and –pass flags.
+a single username and password with the --user and --pass flags.
 
-Use –htpasswd /path/to/htpasswd to provide an htpasswd file. This is in
+Use --htpasswd /path/to/htpasswd to provide an htpasswd file. This is in
 standard apache format and supports MD5, SHA1 and BCrypt for basic
 authentication. Bcrypt is recommended.
 
@@ -4512,19 +4901,19 @@ To create an htpasswd file:
 
 The password file can be updated while rclone is running.
 
-Use –realm to set the authentication realm.
+Use --realm to set the authentication realm.
 
 SSL/TLS
 
 By default this will serve over http. If you want you can serve over
-https. You will need to supply the –cert and –key flags. If you wish to
-do client side certificate validation then you will need to supply
-–client-ca also.
+https. You will need to supply the --cert and --key flags. If you wish
+to do client side certificate validation then you will need to supply
+--client-ca also.
 
-–cert should be either a PEM encoded certificate or a concatenation of
-that with the CA certificate. –key should be the PEM encoded private key
-and –client-ca should be the PEM encoded client certificate authority
-certificate.
+--cert should be either a PEM encoded certificate or a concatenation of
+that with the CA certificate. --key should be the PEM encoded private
+key and --client-ca should be the PEM encoded client certificate
+authority certificate.
 
     rclone serve restic remote:path [flags]
 
@@ -4570,47 +4959,68 @@ rclone serve sftp implements an SFTP server to serve the remote over
 SFTP. This can be used with an SFTP client or you can make a remote of
 type sftp to use with it.
 
-You can use the filter flags (eg –include, –exclude) to control what is
-served.
+You can use the filter flags (eg --include, --exclude) to control what
+is served.
 
 The server will log errors. Use -v to see access logs.
 
-–bwlimit will be respected for file transfers. Use –stats to control the
-stats printing.
+--bwlimit will be respected for file transfers. Use --stats to control
+the stats printing.
 
-You must provide some means of authentication, either with –user/–pass,
-an authorized keys file (specify location with –authorized-keys - the
-default is the same as ssh), an –auth-proxy, or set the –no-auth flag
-for no authentication when logging in.
+You must provide some means of authentication, either with
+--user/--pass, an authorized keys file (specify location with
+--authorized-keys - the default is the same as ssh), an --auth-proxy, or
+set the --no-auth flag for no authentication when logging in.
 
 Note that this also implements a small number of shell commands so that
 it can provide md5sum/sha1sum/df information for the rclone sftp
 backend. This means that is can support SHA1SUMs, MD5SUMs and the about
 command when paired with the rclone sftp backend.
 
-If you don’t supply a –key then rclone will generate one and cache it
+If you don't supply a --key then rclone will generate one and cache it
 for later use.
 
 By default the server binds to localhost:2022 - if you want it to be
-reachable externally then supply “–addr :2022” for example.
+reachable externally then supply "--addr :2022" for example.
 
-Note that the default of “–vfs-cache-mode off” is fine for the rclone
+Note that the default of "--vfs-cache-mode off" is fine for the rclone
 sftp backend, but it may not be with other SFTP clients.
 
 
-Directory Cache
+VFS - Virtual File System
 
-Using the --dir-cache-time flag, you can set how long a directory should
-be considered up to date and not refreshed from the backend. Changes
-made locally in the mount may appear immediately or invalidate the
-cache. However, changes done on the remote will only be picked up once
-the cache expires if the backend configured does not support polling for
-changes. If the backend supports polling, changes will be picked up on
+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.
+
+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.
+
+The VFS layer also implements a directory cache - this caches info about
+files and directories (but not the data) in memory.
+
+
+VFS Directory Cache
+
+Using the --dir-cache-time flag, you can control how long a directory
+should be considered up to date and not refreshed from the backend.
+Changes made through the mount will appear immediately or invalidate the
+cache.
+
+    --dir-cache-time duration   Time to cache directory entries for. (default 5m0s)
+    --poll-interval duration    Time to wait between polling for changes.
+
+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.
 
-Alternatively, you can send a SIGHUP 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:
+You can send a SIGHUP 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:
 
     kill -SIGHUP $(pidof rclone)
 
@@ -4624,40 +5034,41 @@ Or individual files or directories:
     rclone rc vfs/forget file=path/to/file dir=path/to/dir
 
 
-File Buffering
+VFS File Buffering
 
 The --buffer-size flag determines the amount of memory, that will be
 used to buffer data in advance.
 
-Each open file descriptor will try to keep the specified amount of data
-in memory at all times. The buffered data is bound to one file
-descriptor and won’t be shared between multiple open file descriptors of
-the same file.
+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.
 
-This flag is a upper limit for the used memory per file descriptor. 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. The maximum memory used by rclone for buffering can be up to
+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.
+
+The maximum memory used by rclone for buffering can be up to
 --buffer-size * open files.
 
 
-File Caching
+VFS File Caching
 
-These flags control the VFS file caching options. The VFS layer is used
-by rclone mount to make a cloud storage system work more like a normal
-file system.
+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.
 
-You’ll need to enable VFS caching if you want, for example, to read and
+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.
 
-Note that the VFS cache works in addition to the cache backend and you
-may find that you need one or the other or both.
+Note that the VFS cache is separate from the cache backend and you may
+find that you need one or the other or both.
 
     --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 age of objects in the cache. (default 1h0m0s)
-    --vfs-cache-mode string              Cache mode off|minimal|writes|full (default "off")
+    --vfs-cache-max-size SizeSuffix      Max total size of objects in the cache. (default off)
     --vfs-cache-poll-interval duration   Interval to poll the cache for stale objects. (default 1m0s)
-    --vfs-cache-max-size int             Max total size of objects in the cache. (default off)
+    --vfs-write-back duration            Time to writeback files after last use when using cache. (default 5s)
 
 If run with -vv rclone will print the location of the file cache. The
 files are stored in the user cache file area which is OS dependent but
@@ -4669,77 +5080,117 @@ the cache mode the more compatible rclone becomes at the cost of using
 disk space.
 
 Note that files are written back to the remote only when they are closed
-so if rclone is quit or dies with open files then these won’t get
-written back to the remote. However they will still be in the on disk
-cache.
+and if they haven't been accessed for --vfs-write-back second. 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.
 
-If using –vfs-cache-max-size note that the cache may exceed this size
+If using --vfs-cache-max-size note that the cache may exceed this size
 for two reasons. Firstly because it is only checked every
-–vfs-cache-poll-interval. Secondly because open files cannot be evicted
+--vfs-cache-poll-interval. Secondly because open files cannot be evicted
 from the cache.
 
-–vfs-cache-mode off
+--vfs-cache-mode off
 
-In this mode the cache will read directly from the remote and write
-directly to the remote without caching anything on disk.
+In this mode (the default) the cache will read directly from the remote
+and write directly to the remote without caching anything on disk.
 
 This will mean some operations are not possible
 
--   Files can’t be opened for both read AND write
--   Files opened for write can’t be seeked
+-   Files can't be opened for both read AND write
+-   Files opened for write can't be seeked
 -   Existing files opened for write must have O_TRUNC set
 -   Files open for read with O_TRUNC will be opened write only
 -   Files open for write only will behave as if O_TRUNC was supplied
 -   Open modes O_APPEND, O_TRUNC are ignored
--   If an upload fails it can’t be retried
+-   If an upload fails it can't be retried
 
-–vfs-cache-mode minimal
+--vfs-cache-mode minimal
 
-This is very similar to “off” except that files opened for read AND
-write will be buffered to disks. This means that files opened for write
+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.
 
 These operations are not possible
 
--   Files opened for write only can’t be seeked
+-   Files opened for write only can't be seeked
 -   Existing files opened for write must have O_TRUNC set
 -   Files opened for write only will ignore O_APPEND, O_TRUNC
--   If an upload fails it can’t be retried
+-   If an upload fails it can't be retried
 
-–vfs-cache-mode writes
+--vfs-cache-mode writes
 
 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.
 
 This mode should support all normal file system operations.
 
-If an upload fails it will be retried up to –low-level-retries times.
+If an upload fails it will be retried at exponentially increasing
+intervals up to 1 minute.
 
-–vfs-cache-mode full
+--vfs-cache-mode full
 
-In this mode all reads and writes are buffered to and from disk. When a
-file is opened for read it will be downloaded in its entirety first.
+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.
 
-This may be appropriate for your needs, or you may prefer to look at the
-cache backend which does a much more sophisticated job of caching,
-including caching directory hierarchies and chunks of files.
+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 dowloaded.
 
-In this mode, unlike the others, when a file is written to the disk, it
-will be kept on the disk after it is written to the remote. It will be
-purged on a schedule according to --vfs-cache-max-age.
+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.
 
-This mode should support all normal file system operations.
+This mode should support all normal file system operations and is
+otherwise identical to --vfs-cache-mode writes.
 
-If an upload or download fails it will be retried up to
-–low-level-retries times.
+When reading a file rclone will read --buffer-size plus --vfs-read-ahead
+bytes ahead. The --buffer-size is buffered in memory whereas the
+--vfs-read-ahead is buffered on disk.
+
+When using this mode it is recommended that --buffer-size is not set too
+big and --vfs-read-ahead is set large if required.
 
 
-Case Sensitivity
+VFS Performance
+
+These flags may be used to enable/disable features of the VFS for
+performance or other reasons.
+
+In particular S3 and Swift benefit hugely from the --no-modtime flag (or
+use --use-server-modtime for a slightly different effect) as each read
+of the modification time takes a transaction.
+
+    --no-checksum     Don't compare checksums on up/download.
+    --no-modtime      Don't read/write the modification time (can speed things up).
+    --no-seek         Don't allow seeking in files.
+    --read-only       Mount read-only.
+
+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 is advantageous because some cloud providers account for
+reads being all the data requested, not all the data delivered.
+
+Rclone will keep doubling the chunk size requested starting at
+--vfs-read-chunk-size with a maximum of --vfs-read-chunk-size-limit
+unless it is set to "off" in which case there will be no limit.
+
+    --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")
+
+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.
+
+    --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)
+
+
+VFS Case Sensitivity
 
 Linux file systems are case-sensitive: two files can differ only by
 case, and the exact case must be used when opening a file.
 
-Windows is not like most other operating systems supported by rclone.
 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
@@ -4749,10 +5200,11 @@ only by case.
 Usually file systems on macOS are case-insensitive. It is possible to
 make macOS file systems case-sensitive but that is not the default
 
-The “–vfs-case-insensitive” mount flag controls how rclone handles these
-two cases. If its value is “false”, rclone passes file names to the
-mounted file system as is. If the flag is “true” (or appears without a
-value on command line), rclone may perform a “fixup” as explained below.
+The "--vfs-case-insensitive" mount flag controls how rclone handles
+these two cases. If its value is "false", rclone passes file names to
+the mounted file system as-is. If the flag is "true" (or appears without
+a value on command line), rclone may perform a "fixup" as explained
+below.
 
 The user may specify a file name to open/delete/rename/etc with a case
 different than what is stored on mounted file system. If an argument
@@ -4766,13 +5218,13 @@ system.
 
 Note that case sensitivity of the operating system running rclone (the
 target) may differ from case sensitivity of a file system mounted by
-rclone (the source). The flag controls whether “fixup” is performed to
+rclone (the source). The flag controls whether "fixup" is performed to
 satisfy the target.
 
-If the flag is not provided on 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”.
+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".
 
 
 Auth Proxy
@@ -4787,9 +5239,9 @@ if --auth-proxy is set the authorized keys option will be ignored.
 
 There is an example program bin/test_proxy.py in the rclone source code.
 
-The program’s job is to take a user and pass on the input and turn those
+The program's job is to take a user and pass 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
+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.
 
@@ -4835,12 +5287,12 @@ backends).
 The program can manipulate the supplied user in any way, for example to
 make proxy to many different sftp backends, you could make the user be
 user@example.com and then set the host to example.com in the output and
-the user to user. For security you’d probably want to restrict the host
+the user to user. For security you'd probably want to restrict the host
 to a limited list.
 
 Note that an internal cache is keyed on user so only use that for
-configuration, don’t use pass or public_key. This also means that if a
-user’s password or public-key is changed the cache will need to expire
+configuration, don't use pass or public_key. 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.
 
 This can be used to build general purpose proxies to any kind of backend
@@ -4875,9 +5327,11 @@ Options
           --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-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 128M)
           --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. 'off' is unlimited. (default off)
           --vfs-read-wait duration                 Time to wait for in-sequence read before seeking. (default 20ms)
+          --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)
 
 See the global flags page for global options not listed here.
@@ -4905,45 +5359,45 @@ to read and write it.
 
 Webdav options
 
-–etag-hash
+--etag-hash
 
 This controls the ETag header. Without this flag the ETag will be based
 on the ModTime and Size of the object.
 
-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”.
+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 “rclone hashsum” to see the full list.
+Use "rclone hashsum" to see the full list.
 
 
 Server options
 
-Use –addr to specify which IP address and port the server should listen
-on, eg –addr 1.2.3.4:8000 or –addr :8080 to listen to all IPs. By
+Use --addr to specify which IP address and port the server should listen
+on, eg --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.
 
-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.
+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.
 
-–server-read-timeout and –server-write-timeout can be used to control
+--server-read-timeout and --server-write-timeout can be used to control
 the timeouts on the server. Note that this is the total time for a
 transfer.
 
-–max-header-bytes controls the maximum number of bytes the server will
+--max-header-bytes controls the maximum number of bytes the server will
 accept in the HTTP header.
 
-–baseurl controls the URL prefix that rclone serves from. By default
-rclone will serve from the root. If you used –baseurl “/rclone” then
-rclone would serve from a URL starting with “/rclone/”. This is useful
+--baseurl controls the URL prefix that rclone serves from. By default
+rclone will serve from the root. If you used --baseurl "/rclone" 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 –baseurl, so –baseurl “rclone”, –baseurl “/rclone”
-and –baseurl “/rclone/” are all treated identically.
+and trailing "/" on --baseurl, so --baseurl "rclone", --baseurl
+"/rclone" and --baseurl "/rclone/" are all treated identically.
 
-–template 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:
+--template 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:
 
   -----------------------------------------------------------------------
   Parameter                           Description
@@ -4970,25 +5424,25 @@ used within the template to server pages:
   .Breadcrumb                         Allows for creating a relative
                                       navigation
 
-  – .Link                             The relative to the root link of
+  -- .Link                            The relative to the root link of
                                       the Text.
 
-  – .Text                             The Name of the directory.
+  -- .Text                            The Name of the directory.
 
   .Entries                            Information about a specific
                                       file/directory.
 
-  – .URL                              The ‘url’ of an entry.
+  -- .URL                             The 'url' of an entry.
 
-  – .Leaf                             Currently same as ‘URL’ but
-                                      intended to be ‘just’ the name.
+  -- .Leaf                            Currently same as 'URL' but
+                                      intended to be 'just' the name.
 
-  – .IsDir                            Boolean for if an entry is a
+  -- .IsDir                           Boolean for if an entry is a
                                       directory or not.
 
-  – .Size                             Size in Bytes of the entry.
+  -- .Size                            Size in Bytes of the entry.
 
-  – .ModTime                          The UTC timestamp of an entry.
+  -- .ModTime                         The UTC timestamp of an entry.
   -----------------------------------------------------------------------
 
 Authentication
@@ -4996,9 +5450,9 @@ Authentication
 By default this will serve files without needing a login.
 
 You can either use an htpasswd file which can take lots of users, or set
-a single username and password with the –user and –pass flags.
+a single username and password with the --user and --pass flags.
 
-Use –htpasswd /path/to/htpasswd to provide an htpasswd file. This is in
+Use --htpasswd /path/to/htpasswd to provide an htpasswd file. This is in
 standard apache format and supports MD5, SHA1 and BCrypt for basic
 authentication. Bcrypt is recommended.
 
@@ -5010,34 +5464,55 @@ To create an htpasswd file:
 
 The password file can be updated while rclone is running.
 
-Use –realm to set the authentication realm.
+Use --realm to set the authentication realm.
 
 SSL/TLS
 
 By default this will serve over http. If you want you can serve over
-https. You will need to supply the –cert and –key flags. If you wish to
-do client side certificate validation then you will need to supply
-–client-ca also.
+https. You will need to supply the --cert and --key flags. If you wish
+to do client side certificate validation then you will need to supply
+--client-ca also.
 
-–cert should be either a PEM encoded certificate or a concatenation of
-that with the CA certificate. –key should be the PEM encoded private key
-and –client-ca should be the PEM encoded client certificate authority
-certificate.
+--cert should be either a PEM encoded certificate or a concatenation of
+that with the CA certificate. --key should be the PEM encoded private
+key and --client-ca should be the PEM encoded client certificate
+authority certificate.
 
 
-Directory Cache
+VFS - Virtual File System
 
-Using the --dir-cache-time flag, you can set how long a directory should
-be considered up to date and not refreshed from the backend. Changes
-made locally in the mount may appear immediately or invalidate the
-cache. However, changes done on the remote will only be picked up once
-the cache expires if the backend configured does not support polling for
-changes. If the backend supports polling, changes will be picked up on
+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.
+
+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.
+
+The VFS layer also implements a directory cache - this caches info about
+files and directories (but not the data) in memory.
+
+
+VFS Directory Cache
+
+Using the --dir-cache-time flag, you can control how long a directory
+should be considered up to date and not refreshed from the backend.
+Changes made through the mount will appear immediately or invalidate the
+cache.
+
+    --dir-cache-time duration   Time to cache directory entries for. (default 5m0s)
+    --poll-interval duration    Time to wait between polling for changes.
+
+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.
 
-Alternatively, you can send a SIGHUP 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:
+You can send a SIGHUP 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:
 
     kill -SIGHUP $(pidof rclone)
 
@@ -5051,40 +5526,41 @@ Or individual files or directories:
     rclone rc vfs/forget file=path/to/file dir=path/to/dir
 
 
-File Buffering
+VFS File Buffering
 
 The --buffer-size flag determines the amount of memory, that will be
 used to buffer data in advance.
 
-Each open file descriptor will try to keep the specified amount of data
-in memory at all times. The buffered data is bound to one file
-descriptor and won’t be shared between multiple open file descriptors of
-the same file.
+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.
 
-This flag is a upper limit for the used memory per file descriptor. 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. The maximum memory used by rclone for buffering can be up to
+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.
+
+The maximum memory used by rclone for buffering can be up to
 --buffer-size * open files.
 
 
-File Caching
+VFS File Caching
 
-These flags control the VFS file caching options. The VFS layer is used
-by rclone mount to make a cloud storage system work more like a normal
-file system.
+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.
 
-You’ll need to enable VFS caching if you want, for example, to read and
+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.
 
-Note that the VFS cache works in addition to the cache backend and you
-may find that you need one or the other or both.
+Note that the VFS cache is separate from the cache backend and you may
+find that you need one or the other or both.
 
     --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 age of objects in the cache. (default 1h0m0s)
-    --vfs-cache-mode string              Cache mode off|minimal|writes|full (default "off")
+    --vfs-cache-max-size SizeSuffix      Max total size of objects in the cache. (default off)
     --vfs-cache-poll-interval duration   Interval to poll the cache for stale objects. (default 1m0s)
-    --vfs-cache-max-size int             Max total size of objects in the cache. (default off)
+    --vfs-write-back duration            Time to writeback files after last use when using cache. (default 5s)
 
 If run with -vv rclone will print the location of the file cache. The
 files are stored in the user cache file area which is OS dependent but
@@ -5096,77 +5572,117 @@ the cache mode the more compatible rclone becomes at the cost of using
 disk space.
 
 Note that files are written back to the remote only when they are closed
-so if rclone is quit or dies with open files then these won’t get
-written back to the remote. However they will still be in the on disk
-cache.
+and if they haven't been accessed for --vfs-write-back second. 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.
 
-If using –vfs-cache-max-size note that the cache may exceed this size
+If using --vfs-cache-max-size note that the cache may exceed this size
 for two reasons. Firstly because it is only checked every
-–vfs-cache-poll-interval. Secondly because open files cannot be evicted
+--vfs-cache-poll-interval. Secondly because open files cannot be evicted
 from the cache.
 
-–vfs-cache-mode off
+--vfs-cache-mode off
 
-In this mode the cache will read directly from the remote and write
-directly to the remote without caching anything on disk.
+In this mode (the default) the cache will read directly from the remote
+and write directly to the remote without caching anything on disk.
 
 This will mean some operations are not possible
 
--   Files can’t be opened for both read AND write
--   Files opened for write can’t be seeked
+-   Files can't be opened for both read AND write
+-   Files opened for write can't be seeked
 -   Existing files opened for write must have O_TRUNC set
 -   Files open for read with O_TRUNC will be opened write only
 -   Files open for write only will behave as if O_TRUNC was supplied
 -   Open modes O_APPEND, O_TRUNC are ignored
--   If an upload fails it can’t be retried
+-   If an upload fails it can't be retried
 
-–vfs-cache-mode minimal
+--vfs-cache-mode minimal
 
-This is very similar to “off” except that files opened for read AND
-write will be buffered to disks. This means that files opened for write
+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.
 
 These operations are not possible
 
--   Files opened for write only can’t be seeked
+-   Files opened for write only can't be seeked
 -   Existing files opened for write must have O_TRUNC set
 -   Files opened for write only will ignore O_APPEND, O_TRUNC
--   If an upload fails it can’t be retried
+-   If an upload fails it can't be retried
 
-–vfs-cache-mode writes
+--vfs-cache-mode writes
 
 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.
 
 This mode should support all normal file system operations.
 
-If an upload fails it will be retried up to –low-level-retries times.
+If an upload fails it will be retried at exponentially increasing
+intervals up to 1 minute.
 
-–vfs-cache-mode full
+--vfs-cache-mode full
 
-In this mode all reads and writes are buffered to and from disk. When a
-file is opened for read it will be downloaded in its entirety first.
+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.
 
-This may be appropriate for your needs, or you may prefer to look at the
-cache backend which does a much more sophisticated job of caching,
-including caching directory hierarchies and chunks of files.
+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 dowloaded.
 
-In this mode, unlike the others, when a file is written to the disk, it
-will be kept on the disk after it is written to the remote. It will be
-purged on a schedule according to --vfs-cache-max-age.
+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.
 
-This mode should support all normal file system operations.
+This mode should support all normal file system operations and is
+otherwise identical to --vfs-cache-mode writes.
 
-If an upload or download fails it will be retried up to
-–low-level-retries times.
+When reading a file rclone will read --buffer-size plus --vfs-read-ahead
+bytes ahead. The --buffer-size is buffered in memory whereas the
+--vfs-read-ahead is buffered on disk.
+
+When using this mode it is recommended that --buffer-size is not set too
+big and --vfs-read-ahead is set large if required.
 
 
-Case Sensitivity
+VFS Performance
+
+These flags may be used to enable/disable features of the VFS for
+performance or other reasons.
+
+In particular S3 and Swift benefit hugely from the --no-modtime flag (or
+use --use-server-modtime for a slightly different effect) as each read
+of the modification time takes a transaction.
+
+    --no-checksum     Don't compare checksums on up/download.
+    --no-modtime      Don't read/write the modification time (can speed things up).
+    --no-seek         Don't allow seeking in files.
+    --read-only       Mount read-only.
+
+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 is advantageous because some cloud providers account for
+reads being all the data requested, not all the data delivered.
+
+Rclone will keep doubling the chunk size requested starting at
+--vfs-read-chunk-size with a maximum of --vfs-read-chunk-size-limit
+unless it is set to "off" in which case there will be no limit.
+
+    --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")
+
+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.
+
+    --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)
+
+
+VFS Case Sensitivity
 
 Linux file systems are case-sensitive: two files can differ only by
 case, and the exact case must be used when opening a file.
 
-Windows is not like most other operating systems supported by rclone.
 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
@@ -5176,10 +5692,11 @@ only by case.
 Usually file systems on macOS are case-insensitive. It is possible to
 make macOS file systems case-sensitive but that is not the default
 
-The “–vfs-case-insensitive” mount flag controls how rclone handles these
-two cases. If its value is “false”, rclone passes file names to the
-mounted file system as is. If the flag is “true” (or appears without a
-value on command line), rclone may perform a “fixup” as explained below.
+The "--vfs-case-insensitive" mount flag controls how rclone handles
+these two cases. If its value is "false", rclone passes file names to
+the mounted file system as-is. If the flag is "true" (or appears without
+a value on command line), rclone may perform a "fixup" as explained
+below.
 
 The user may specify a file name to open/delete/rename/etc with a case
 different than what is stored on mounted file system. If an argument
@@ -5193,13 +5710,13 @@ system.
 
 Note that case sensitivity of the operating system running rclone (the
 target) may differ from case sensitivity of a file system mounted by
-rclone (the source). The flag controls whether “fixup” is performed to
+rclone (the source). The flag controls whether "fixup" is performed to
 satisfy the target.
 
-If the flag is not provided on 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”.
+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".
 
 
 Auth Proxy
@@ -5214,9 +5731,9 @@ if --auth-proxy is set the authorized keys option will be ignored.
 
 There is an example program bin/test_proxy.py in the rclone source code.
 
-The program’s job is to take a user and pass on the input and turn those
+The program's job is to take a user and pass 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
+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.
 
@@ -5262,12 +5779,12 @@ backends).
 The program can manipulate the supplied user in any way, for example to
 make proxy to many different sftp backends, you could make the user be
 user@example.com and then set the host to example.com in the output and
-the user to user. For security you’d probably want to restrict the host
+the user to user. For security you'd probably want to restrict the host
 to a limited list.
 
 Note that an internal cache is keyed on user so only use that for
-configuration, don’t use pass or public_key. This also means that if a
-user’s password or public-key is changed the cache will need to expire
+configuration, don't use pass or public_key. 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.
 
 This can be used to build general purpose proxies to any kind of backend
@@ -5311,9 +5828,11 @@ Options
           --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-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 128M)
           --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. 'off' is unlimited. (default off)
           --vfs-read-wait duration                 Time to wait for in-sequence read before seeking. (default 20ms)
+          --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)
 
 See the global flags page for global options not listed here.
@@ -5384,16 +5903,17 @@ Set the modification time on object(s) as specified by remote:path to
 have the current time.
 
 If remote:path does not exist then a zero sized object will be created
-unless the –no-create flag is provided.
+unless the --no-create flag is provided.
 
-If –timestamp is used then it will set the modification time to that
+If --timestamp is used then it will set the modification time to that
 time instead of the current time. Times may be specified as one of:
 
--   ‘YYMMDD’ - eg. 17.10.30
--   ‘YYYY-MM-DDTHH:MM:SS’ - eg. 2006-01-02T15:04:05
+-   'YYMMDD' - eg. 17.10.30
+-   'YYYY-MM-DDTHH:MM:SS' - eg. 2006-01-02T15:04:05
+-   'YYYY-MM-DDTHH:MM:SS.SSS' - eg. 2006-01-02T15:04:05.123456789
 
-Note that –timestamp is in UTC if you want local time then add the
-–localtime flag.
+Note that --timestamp is in UTC if you want local time then add the
+--localtime flag.
 
     rclone touch remote:path [flags]
 
@@ -5439,11 +5959,11 @@ For example
     1 directories, 5 files
 
 You can use any of the filtering options with the tree command (eg
-–include and –exclude). You can also use –fast-list.
+--include and --exclude). You can also use --fast-list.
 
 The tree command has many options for controlling the listing which are
 compatible with the tree command. Note that not all of them have short
-options as they conflict with rclone’s short options.
+options as they conflict with rclone's short options.
 
     rclone tree remote:path [flags]
 
@@ -5459,7 +5979,7 @@ Options
           --human           Print the size in a more human readable way.
           --level int       Descend only level directories deep.
       -D, --modtime         Print the date of last modification.
-      -i, --noindent        Don't print indentation lines.
+          --noindent        Don'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.
@@ -5487,7 +6007,7 @@ remote points to a file, rclone will just copy that file. The
 destination remote must point to a directory - rclone will give the
 error
 Failed to create file system for "remote:file": is a file not a directory
-if it isn’t.
+if it isn't.
 
 For example, suppose you have a remote with a file in called test.jpg,
 then you could copy just that file like this
@@ -5520,7 +6040,7 @@ This refers to the local file system.
 On Windows only \ may be used instead of / in local paths ONLY, non
 local paths must use /.
 
-These paths needn’t start with a leading / - if they don’t then they
+These paths needn't start with a leading / - if they don't then they
 will be relative to the current directory.
 
 remote:path/to/dir
@@ -5534,7 +6054,7 @@ On most backends this is refers to the same directory as
 remote:path/to/dir 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 / will refer to
-your “home” directory and paths with a leading / will refer to the root.
+your "home" directory and paths with a leading / will refer to the root.
 
 :backend:path/to/dir
 
@@ -5563,6 +6083,11 @@ To copy files and directories in https://example.com/path/to/dir to
 To copy files and directories from example.com in the relative directory
 path/to/dir to /tmp/dir using sftp.
 
+Valid remote names
+
+-   Remote names may only contain 0-9, A-Z ,a-z ,_ , - and space.
+-   Remote names may not start with -.
+
 
 Quoting and the shell
 
@@ -5585,7 +6110,7 @@ If you want to send a ' you will need to use ", eg
     rclone copy "O'Reilly Reviews" remote:backup
 
 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.
+full details you'll have to consult the manual page for your shell.
 
 Windows
 
@@ -5593,7 +6118,7 @@ If your names have spaces in you need to put them in ", eg
 
     rclone copy "E:\folder name\folder name\folder name" remote:backup
 
-If you are using the root directory on its own then don’t quote it (see
+If you are using the root directory on its own then don't quote it (see
 #464 for why), eg
 
     rclone copy E:\ remote:backup
@@ -5609,18 +6134,18 @@ current directory prefix.
 
 So to sync a directory called sync:me to a remote called remote: use
 
-    rclone sync ./sync:me remote:path
+    rclone sync -i ./sync:me remote:path
 
 or
 
-    rclone sync /full/path/to/sync:me remote:path
+    rclone sync -i /full/path/to/sync:me remote:path
 
 
 Server Side Copy
 
 Most remotes (but not all - see the overview) support server side copy.
 
-This means if you want to copy one folder to another then rclone won’t
+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.
 
@@ -5631,12 +6156,12 @@ Eg
 Will copy the contents of oldbucket to newbucket without downloading and
 re-uploading.
 
-Remotes which don’t support server side copy WILL download and re-upload
+Remotes which don't support server side copy WILL download and re-upload
 in this case.
 
 Server side copies are used with sync and copy and will be identified in
 the log when using the -v flag. The move command may also use them if
-remote doesn’t support server side move directly. This is done by
+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.
 
@@ -5645,8 +6170,8 @@ same.
 
 This can be used when scripting to make aged backups efficiently, eg
 
-    rclone sync remote:current-backup remote:previous-backup
-    rclone sync /path/to/files remote:current-backup
+    rclone sync -i remote:current-backup remote:previous-backup
+    rclone sync -i /path/to/files remote:current-backup
 
 
 Options
@@ -5663,15 +6188,15 @@ is parsed as an extra command line argument for rclone.
 
 Options which use TIME use the go time parser. 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”. Valid time units
-are “ns”, “us” (or “µs”), “ms”, “s”, “m”, “h”.
+and a unit suffix, such as "300ms", "-1.5h" or "2h45m". Valid time units
+are "ns", "us" (or "µs"), "ms", "s", "m", "h".
 
 Options which use SIZE use kByte by default. However, a suffix of b for
 bytes, k for kBytes, M for MBytes, G for GBytes, T for TBytes and P for
 PBytes may be used. These are the binary units, eg 1, 2**10, 2**20,
 2**30 respectively.
 
-–backup-dir=DIR
+--backup-dir=DIR
 
 When using sync, copy or move any files which would have been
 overwritten or deleted are moved in their original hierarchy into this
@@ -5687,25 +6212,25 @@ must not overlap the destination directory.
 
 For example
 
-    rclone sync /path/to/local remote:current --backup-dir remote:old
+    rclone sync -i /path/to/local remote:current --backup-dir remote:old
 
 will sync /path/to/local to remote:current, but for any files which
 would have been updated or deleted will be stored in remote:old.
 
-If running rclone from a script you might want to use today’s date as
+If running rclone from a script you might want to use today's date as
 the directory name passed to --backup-dir to store the old files, or you
-might want to pass --suffix with today’s date.
+might want to pass --suffix with today's date.
 
 See --compare-dest and --copy-dest.
 
-–bind string
+--bind string
 
 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
+host name doesn't resolve or resolves to more than one IP address it
 will give an error.
 
-–bwlimit=BANDWIDTH_SPEC
+--bwlimit=BANDWIDTH_SPEC
 
 This option controls the bandwidth limit. Limits can be specified in two
 ways: As a single limit, or as a timetable.
@@ -5716,7 +6241,7 @@ b|k|M|G. The default is 0 which means to not limit bandwidth.
 
 For example, to limit bandwidth usage to 10 MBytes/s use --bwlimit 10M
 
-It is also possible to specify a “timetable” of limits, which will cause
+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
 WEEKDAY-HH:MM,BANDWIDTH WEEKDAY-HH:MM,BANDWIDTH... where: WEEKDAY is
@@ -5752,11 +6277,11 @@ Is equal to this:
 
 --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"
 
-Bandwidth limits only apply to the data transfer. They don’t apply to
+Bandwidth limits only apply to the data transfer. They don't apply to
 the bandwidth of the directory listings etc.
 
 Note that the units are Bytes/s, not Bits/s. Typically connections are
-measured in Bits/s - to convert divide by 8. For example, let’s say you
+measured in Bits/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.625MByte/s so you would use a --bwlimit 0.625M
 parameter for rclone.
@@ -5775,7 +6300,21 @@ the bwlimit dynamically:
 
     rclone rc core/bwlimit rate=1M
 
-–buffer-size=SIZE
+--bwlimit-file=BANDWIDTH_SPEC
+
+This option controls per file bandwidth limit. For the options see the
+--bwlimit flag.
+
+For example use this to allow no transfers to be faster than 1MByte/s
+
+    --bwlimit-file 1M
+
+This can be used in conjunction with --bwlimit.
+
+Note that if a schedule is provided the file will use the schedule in
+effect at the start of the transfer.
+
+--buffer-size=SIZE
 
 Use this sized buffer to speed up file transfers. Each --transfer will
 use this much memory for buffering.
@@ -5786,9 +6325,9 @@ memory for buffering. See the mount documentation for more details.
 Set to 0 to disable the buffering for the minimum memory usage.
 
 Note that the memory allocation of the buffers is influenced by the
-–use-mmap flag.
+--use-mmap flag.
 
-–check-first
+--check-first
 
 If this flag is set then in a sync, copy or move, rclone will do all the
 checks to see whether files need to be transferred before doing any of
@@ -5802,7 +6341,7 @@ Using this flag can use more memory as it effectively sets --max-backlog
 to infinite. This means that all the info on the objects to transfer is
 held in memory before the transfers start.
 
-–checkers=N
+--checkers=N
 
 The number of checkers to run in parallel. Checkers do the equality
 checking of files during a sync. For some storage systems (eg S3, Swift,
@@ -5811,13 +6350,13 @@ parallel.
 
 The default is to run 8 checkers in parallel.
 
--c, –checksum
+-c, --checksum
 
 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.
 
-This is useful when the remote doesn’t support setting modified time and
+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.
 
 This is very useful when transferring between remotes which store the
@@ -5827,10 +6366,10 @@ remotes support which hash type see the table in the overview section.
 Eg rclone --checksum sync s3:/bucket swift:/bucket would run much
 quicker than without the --checksum flag.
 
-When using this flag, rclone won’t update mtimes of remote files if they
+When using this flag, rclone won't update mtimes of remote files if they
 are incorrect as it would normally.
 
-–compare-dest=DIR
+--compare-dest=DIR
 
 When using sync, copy or move DIR is checked in addition to the
 destination for files. If a file identical to the source is found that
@@ -5842,7 +6381,7 @@ directory must not overlap the destination directory.
 
 See --copy-dest and --backup-dir.
 
-–config=CONFIG_FILE
+--config=CONFIG_FILE
 
 Specify the location of the rclone config file.
 
@@ -5861,7 +6400,7 @@ for you.
 Use this flag to override the config location, eg
 rclone --config=".myconfig" .config.
 
-–contimeout=TIME
+--contimeout=TIME
 
 Set the connection timeout. This should be in go time format which looks
 like 5s for 5 seconds, 10m for 10 minutes, or 3h30m.
@@ -5870,7 +6409,7 @@ 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 1m by
 default.
 
-–copy-dest=DIR
+--copy-dest=DIR
 
 When using sync, copy or move DIR is checked in addition to the
 destination for files. If a file identical to the source is found that
@@ -5883,13 +6422,13 @@ not overlap the destination directory.
 
 See --compare-dest and --backup-dir.
 
-–dedupe-mode MODE
+--dedupe-mode MODE
 
 Mode to run dedupe command in. One of interactive, skip, first, newest,
 oldest, rename. The default is interactive. See the dedupe command for
 more information as to what these options mean.
 
-–disable FEATURE,FEATURE,…
+--disable FEATURE,FEATURE,...
 
 This disables a comma separated list of optional features. For example
 to disable server side move and server side copy use:
@@ -5909,17 +6448,17 @@ This flag can be useful for debugging and in exceptional circumstances
 (eg Google Drive limiting the total volume of Server Side Copies to
 100GB/day).
 
--n, –dry-run
+-n, --dry-run
 
 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 sync
 command which deletes files in the destination.
 
-–expect-continue-timeout=TIME
+--expect-continue-timeout=TIME
 
-This specifies the amount of time to wait for a server’s first response
+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.
+"Expect: 100-continue" header. Not all backends support using this.
 
 Zero means no timeout and causes the body to be sent immediately,
 without waiting for the server to approve. This time does not include
@@ -5927,7 +6466,7 @@ the time to send the request header.
 
 The default is 1s. Set to 0 to disable.
 
-–error-on-no-transfer
+--error-on-no-transfer
 
 By default, rclone will exit with return code 0 if there were no errors.
 
@@ -5940,7 +6479,7 @@ NB: Enabling this option turns a usually non-fatal error into a
 potentially fatal one - please check and adjust your scripts
 accordingly!
 
-–header
+--header
 
 Add an HTTP header for all transactions. The flag can be repeated to add
 multiple headers.
@@ -5954,49 +6493,49 @@ workaround for those with care.
 
     rclone ls remote:test --header "X-Rclone: Foo" --header "X-LetMeIn: Yes"
 
-–header-download
+--header-download
 
 Add an HTTP header for all download transactions. The flag can be
 repeated to add multiple headers.
 
-    rclone sync s3:test/src ~/dst --header-download "X-Amz-Meta-Test: Foo" --header-download "X-Amz-Meta-Test2: Bar"
+    rclone sync -i s3:test/src ~/dst --header-download "X-Amz-Meta-Test: Foo" --header-download "X-Amz-Meta-Test2: Bar"
 
 See the GitHub issue here for currently supported backends.
 
-–header-upload
+--header-upload
 
 Add an HTTP header for all upload transactions. The flag can be repeated
 to add multiple headers.
 
-    rclone sync ~/src s3:test/dst --header-upload "Content-Disposition: attachment; filename='cool.html'" --header-upload "X-Amz-Meta-Test: FooBar"
+    rclone sync -i ~/src s3:test/dst --header-upload "Content-Disposition: attachment; filename='cool.html'" --header-upload "X-Amz-Meta-Test: FooBar"
 
 See the GitHub issue here for currently supported backends.
 
-–ignore-case-sync
+--ignore-case-sync
 
 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.
 
-–ignore-checksum
+--ignore-checksum
 
 Normally rclone will check that the checksums of transferred files
-match, and give an error “corrupted on transfer” if they don’t.
+match, and give an error "corrupted on transfer" if they don't.
 
 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 have had the "corrupted on transfer" error message and you are sure
 you might want to transfer potentially corrupted data.
 
-–ignore-existing
+--ignore-existing
 
 Using this option will make rclone unconditionally skip all files that
 exist on the destination, no matter the content of these files.
 
-While this isn’t a generally recommended option, it can be useful in
+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.
 
-–ignore-size
+--ignore-size
 
 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
@@ -6010,7 +6549,7 @@ This can be useful for transferring files to and from OneDrive which
 occasionally misreports the size of image files (see #399 for more
 info).
 
--I, –ignore-times
+-I, --ignore-times
 
 Using this option will cause rclone to unconditionally upload all files
 regardless of the state of files on the destination.
@@ -6019,7 +6558,7 @@ Normally rclone would skip any files that have the same modification
 time and are the same size (or have the same checksum if using
 --checksum).
 
-–immutable
+--immutable
 
 Treat source and destination files as immutable and disallow
 modification.
@@ -6029,37 +6568,71 @@ but existing files will never be updated. If an existing file does not
 match between the source and destination, rclone will give the error
 Source and destination exist but do not match: immutable file modified.
 
-Note that only commands which transfer files (e.g. sync, copy, move) are
+Note that only commands which transfer files (e.g. sync, copy, move) are
 affected by this behavior, and only modification is disallowed. Files
-may still be deleted explicitly (e.g. delete, purge) or implicitly
-(e.g. sync, move). Use copy --immutable if it is desired to avoid
-deletion as well as modification.
+may still be deleted explicitly (e.g. delete, purge) or implicitly (e.g.
+sync, move). Use copy --immutable if it is desired to avoid deletion as
+well as modification.
 
 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.
 
+-i / --interactive
 
-–leave-root
+This flag can be used to tell rclone that you wish a manual confirmation
+before destructive operations.
 
-During rmdirs it will not remove root directory, even if it’s empty.
+It is RECOMMENDED that you use this flag while learning rclone
+especially with rclone sync.
 
-–log-file=FILE
+For example
 
-Log all of rclone’s output to FILE. This is not active by default. This
+    $ rclone delete -i /tmp/dir
+    rclone: delete "important-file.txt"?
+    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> n
+
+The options mean
+
+-   y: YES, this operation should go ahead. You can also press Return
+    for this to happen. You'll be asked every time unless you choose s
+    or !.
+-   n: NO, do not do this operation. You'll be asked every time unless
+    you choose s or !.
+-   s: SKIP 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.
+-   !: DO ALL 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.
+-   q: QUIT rclone now, just in case!
+
+--leave-root
+
+During rmdirs it will not remove root directory, even if it's empty.
+
+--log-file=FILE
+
+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 -v flag. See the Logging section for more info.
 
-Note that if you are using the logrotate program to manage rclone’s
-logs, then you should use the copytruncate option as rclone doesn’t have
+Note that if you are using the logrotate program to manage rclone's
+logs, then you should use the copytruncate option as rclone doesn't have
 a signal to rotate logs.
 
-–log-format LIST
+--log-format LIST
 
 Comma separated list of log format options. date, time, microseconds,
-longfile, shortfile, UTC. The default is “date,time”.
+longfile, shortfile, UTC. The default is "date,time".
 
-–log-level LEVEL
+--log-level LEVEL
 
 This sets the log level for rclone. The default log level is NOTICE.
 
@@ -6075,12 +6648,12 @@ warnings and significant events.
 
 ERROR is equivalent to -q. It only outputs error messages.
 
-–use-json-log
+--use-json-log
 
 This switches the log format to JSON for rclone. The fields of json log
 are level, msg, source, time.
 
-–low-level-retries NUMBER
+--low-level-retries NUMBER
 
 This controls the number of low level retries rclone does.
 
@@ -6088,14 +6661,14 @@ 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 -v flag.
 
-This shouldn’t need to be changed from the default in normal operations.
+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 --retries
 flag) quicker.
 
 Disable low level retries with --low-level-retries 1.
 
-–max-backlog=N
+--max-backlog=N
 
 This is the maximum allowable backlog of files in a sync/copy/move
 queued for being checked or transferred.
@@ -6114,13 +6687,13 @@ the remote which may be desirable.
 Setting this to a negative number will make the backlog as large as
 possible.
 
-–max-delete=N
+--max-delete=N
 
 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.
 
-–max-depth=N
+--max-depth=N
 
 This modifies the recursion depth for all the commands except purge.
 
@@ -6138,7 +6711,7 @@ recursed through are considered excluded and will be deleted on the
 destination. Test first with --dry-run if you are not sure what will
 happen.
 
-–max-duration=TIME
+--max-duration=TIME
 
 Rclone will stop scheduling new transfers when it has run for the
 duration specified.
@@ -6147,9 +6720,9 @@ Defaults to off.
 
 When the limit is reached any existing transfers will complete.
 
-Rclone won’t exit with an error if the transfer limit is reached.
+Rclone won't exit with an error if the transfer limit is reached.
 
-–max-transfer=SIZE
+--max-transfer=SIZE
 
 Rclone will stop transferring when it has reached the size specified.
 Defaults to off.
@@ -6158,7 +6731,7 @@ When the limit is reached all transfers will stop immediately.
 
 Rclone will exit with exit code 8 if the transfer limit is reached.
 
-–cutoff-mode=hard|soft|cautious
+--cutoff-mode=hard|soft|cautious
 
 This modifies the behavior of --max-transfer Defaults to
 --cutoff-mode=hard.
@@ -6172,7 +6745,7 @@ Rclone reaches the limit.
 Specifying --cutoff-mode=cautious will try to prevent Rclone from
 reaching the limit.
 
-–modify-window=TIME
+--modify-window=TIME
 
 When checking whether a file has been modified, this is the maximum
 allowed time difference that a file can have and still be considered
@@ -6184,7 +6757,7 @@ reading and writing to an OS X filing system this will be 1s by default.
 
 This command line flag allows you to override that computed default.
 
-–multi-thread-cutoff=SIZE
+--multi-thread-cutoff=SIZE
 
 When downloading files to the local backend above this size, rclone will
 use multiple threads to download the file (default 250M).
@@ -6192,8 +6765,8 @@ use multiple threads to download the file (default 250M).
 Rclone preallocates the file (using fallocate(FALLOC_FL_KEEP_SIZE) on
 unix or NTSetInformationFile 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.
+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.
 
 The number of threads used to download is controlled by
 --multi-thread-streams.
@@ -6215,7 +6788,7 @@ files to be sparse. Use --local-no-sparse to disable sparse files (which
 may cause long delays at the start of downloads) or disable multi-thread
 downloads with --multi-thread-streams 0
 
-–multi-thread-streams=N
+--multi-thread-streams=N
 
 When using multi thread downloads (see above --multi-thread-cutoff) this
 sets the maximum number of streams to use. Set to 0 to disable multi
@@ -6234,7 +6807,7 @@ effect (the defaults):
 -   500MB..750MB files will be downloaded with 3 streams
 -   750MB+ files will be downloaded with 4 streams
 
-–no-check-dest
+--no-check-dest
 
 The --no-check-dest can be used with move or copy and it causes rclone
 not to check the destination at all when copying files.
@@ -6245,7 +6818,7 @@ This means that:
 -   files are always transferred
 -   this can cause duplicates on remotes which allow it (eg Google
     Drive)
--   --retries 1 is recommended otherwise you’ll transfer everything
+-   --retries 1 is recommended otherwise you'll transfer everything
     again on a retry
 
 This flag is useful to minimise the transactions if you know that none
@@ -6253,17 +6826,17 @@ of the files are on the destination.
 
 This is a specialized flag which should be ignored by most users!
 
-–no-gzip-encoding
+--no-gzip-encoding
 
-Don’t set Accept-Encoding: gzip. This means that rclone won’t ask the
-server for compressed files automatically. Useful if you’ve set the
+Don't set Accept-Encoding: gzip. This means that rclone won't ask the
+server for compressed files automatically. Useful if you've set the
 server to return files with Content-Encoding: gzip but you uploaded
 compressed files.
 
 There is no need to set this in normal operation, and doing so will
 decrease the network transfer efficiency of rclone.
 
-–no-traverse
+--no-traverse
 
 The --no-traverse flag controls whether the destination file system is
 traversed when using the copy or move commands. --no-traverse is not
@@ -6275,14 +6848,14 @@ then --no-traverse will stop rclone listing the destination and save
 time.
 
 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 --no-traverse.
+are doing a copy where lots of the files under consideration haven't
+changed and won't need copying then you shouldn't use --no-traverse.
 
 See rclone copy for an example of how to use it.
 
-–no-unicode-normalization
+--no-unicode-normalization
 
-Don’t normalize unicode characters in filenames during the sync routine.
+Don't normalize unicode characters in filenames during the sync routine.
 
 Sometimes, an operating system will store filenames containing unicode
 parts in their decomposed form (particularly macOS). Some cloud storage
@@ -6294,15 +6867,15 @@ character as unique. For example, by default é and é will be normalized
 into the same character. With --no-unicode-normalization they will be
 treated as unique characters.
 
-–no-update-modtime
+--no-update-modtime
 
-When using this flag, rclone won’t update modification times of remote
+When using this flag, rclone won't update modification times of remote
 files if they are incorrect as it would normally.
 
 This can be used if the remote is being synced with another tool also
 (eg the Google Drive client).
 
-–order-by string
+--order-by string
 
 The --order-by flag controls the order in which files in the backlog are
 processed in rclone sync, rclone copy and rclone move.
@@ -6352,13 +6925,13 @@ means that it may transfer some files out of the order specified if
 
 -   there are no files in the backlog or the source has not been fully
     scanned yet
--   there are more than –max-backlog files in the backlog
+-   there are more than --max-backlog files in the backlog
 
 Rclone will do its best to transfer the best file it has so in practice
 this should not cause a problem. Think of --order-by as being more of a
 best efforts flag rather than a perfect ordering.
 
-–password-command SpaceSepList
+--password-command SpaceSepList
 
 This flag supplies a program which should supply the config password
 when run. This is an alternative to rclone prompting for the password or
@@ -6379,7 +6952,7 @@ See the Configuration Encryption for more info.
 
 See a Windows PowerShell example on the Wiki.
 
--P, –progress
+-P, --progress
 
 This flag makes rclone update the stats in a static block in the
 terminal providing a realtime overview of the transfer.
@@ -6396,36 +6969,71 @@ This can be used with the --stats-one-line flag for a simpler display.
 Note: On Windows until this bug is fixed all non-ASCII characters will
 be replaced with . when --progress is in use.
 
--q, –quiet
+-q, --quiet
 
-This flag will limit rclone’s output to error messages only.
+This flag will limit rclone's output to error messages only.
 
-–retries int
+--refresh-times
+
+The --refresh-times flag can be used to update modification times of
+existing files when they are out of sync on backends which don't support
+hashes.
+
+This is useful if you uploaded files with the incorrect timestamps and
+you now wish to correct them.
+
+This flag is ONLY useful for destinations which don't support hashes (eg
+crypt).
+
+This can be used any of the sync commands sync, copy or move.
+
+To use this flag you will need to be doing a modification time sync (so
+not using --size-only or --checksum). The flag will have no effect when
+using --size-only or --checksum.
+
+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 (eg on a
+crypt backend) then rclone will update the timestamp.
+
+Note that some remotes can't set the modification time without
+re-uploading the file so this flag is less useful on them.
+
+Normally if you are doing a modification time sync rclone will update
+modification times without --refresh-times provided that the remote
+supports checksums AND 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.
+
+--retries int
 
 Retry the entire sync if it fails this many times it fails (default 3).
 
 Some remotes can be unreliable and a few retries help pick up the files
-which didn’t get transferred because of errors.
+which didn't get transferred because of errors.
 
 Disable retries with --retries 1.
 
-–retries-sleep=TIME
+--retries-sleep=TIME
 
 This sets the interval between each retry specified by --retries
 
 The default is 0. Use 0 to disable.
 
-–size-only
+--size-only
 
 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.
 
 This can be useful transferring files from Dropbox which have been
-modified by the desktop sync client which doesn’t set checksums of
+modified by the desktop sync client which doesn't set checksums of
 modification times in the same way as rclone.
 
-–stats=TIME
+--stats=TIME
 
 Commands which transfer data (sync, copy, copyto, move, moveto) will
 print data transfer stats at regular intervals to show their progress.
@@ -6437,47 +7045,47 @@ The default is 1m. Use 0 to disable.
 If you set the stats interval then all commands can show stats. This can
 be useful when running other commands, check or mount for example.
 
-Stats are logged at INFO level by default which means they won’t show at
+Stats are logged at INFO level by default which means they won't show at
 default log level NOTICE. Use --stats-log-level NOTICE or -v to make
 them show. See the Logging section for more info on log levels.
 
 Note that on macOS you can send a SIGINFO (which is normally ctrl-T in
 the terminal) to make the stats print immediately.
 
-–stats-file-name-length integer
+--stats-file-name-length integer
 
 By default, the --stats output will truncate file names and paths longer
 than 40 characters. This is equivalent to providing
 --stats-file-name-length 40. Use --stats-file-name-length 0 to disable
 any truncation of file names printed by stats.
 
-–stats-log-level string
+--stats-log-level string
 
 Log level to show --stats output at. This can be DEBUG, INFO, NOTICE, or
 ERROR. The default is INFO. This means at the default level of logging
-which is NOTICE the stats won’t show - if you want them to then use
+which is NOTICE the stats won't show - if you want them to then use
 --stats-log-level NOTICE. See the Logging section for more info on log
 levels.
 
-–stats-one-line
+--stats-one-line
 
 When this is specified, rclone condenses the stats into a single line
 showing the most important stats only.
 
-–stats-one-line-date
+--stats-one-line-date
 
 When this is specified, rclone enables the single-line stats and
 prepends the display with a date string. The default is
 2006/01/02 15:04:05 -
 
-–stats-one-line-date-format
+--stats-one-line-date-format
 
 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 golang specs for date formatting
 syntax.
 
-–stats-unit=bits|bytes
+--stats-unit=bits|bytes
 
 By default, data transfer rates will be printed in bytes/second.
 
@@ -6490,7 +7098,7 @@ The rate is reported as a binary unit, not SI unit. So 1 Mbit/s equals
 
 The default is bytes.
 
-–suffix=SUFFIX
+--suffix=SUFFIX
 
 When using sync, copy or move any files which would have been
 overwritten or deleted will have the suffix added to them. If there is a
@@ -6505,34 +7113,34 @@ with --backup-dir. See --backup-dir for more info.
 
 For example
 
-    rclone sync /path/to/local/file remote:current --suffix .bak
+    rclone sync -i /path/to/local/file remote:current --suffix .bak
 
 will sync /path/to/local to remote:current, but for any files which
 would have been updated or deleted have .bak added.
 
-–suffix-keep-extension
+--suffix-keep-extension
 
 When using --suffix, setting this causes rclone put the SUFFIX before
 the extension of the files that it backs up rather than after.
 
-So let’s say we had --suffix -2019-01-01, without the flag file.txt
+So let's say we had --suffix -2019-01-01, without the flag file.txt
 would be backed up to file.txt-2019-01-01 and with the flag it would be
 backed up to file-2019-01-01.txt. This can be helpful to make sure the
 suffixed files can still be opened.
 
-–syslog
+--syslog
 
 On capable OSes (not Windows or Plan9) send all log output to syslog.
 
 This can be useful for running rclone in a script or rclone mount.
 
-–syslog-facility string
+--syslog-facility string
 
 If using --syslog this sets the syslog facility (eg KERN, USER). See
 man syslog for a list of possible facilities. The default facility is
 DAEMON.
 
-–tpslimit float
+--tpslimit float
 
 Limit HTTP transactions per second to this. Default is 0 which is used
 to mean unlimited transactions per second.
@@ -6549,7 +7157,7 @@ applications using it.
 
 See also --tpslimit-burst.
 
-–tpslimit-burst int
+--tpslimit-burst int
 
 Max burst of transactions for --tpslimit (default 1).
 
@@ -6565,9 +7173,9 @@ quickly before they are limited again.
 This may be used to increase performance of --tpslimit without changing
 the long term average number of transactions per second.
 
-–track-renames
+--track-renames
 
-By default, rclone doesn’t keep track of renamed files, so if you rename
+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.
 
@@ -6581,8 +7189,10 @@ will be considered.
 
 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. Note: Encrypted destinations are not supported by
---track-renames.
+to the console.
+
+Encrypted destinations are not currently supported by --track-renames if
+--track-renames-strategy includes hash.
 
 Note that --track-renames is incompatible with --no-traverse and that it
 uses extra memory to keep track of all the rename candidates.
@@ -6590,15 +7200,31 @@ uses extra memory to keep track of all the rename candidates.
 Note also that --track-renames is incompatible with --delete-before and
 will select --delete-after instead of --delete-during.
 
-–track-renames-strategy (hash,modtime)
+--track-renames-strategy (hash,modtime,leaf,size)
 
-This option changes the matching criteria for --track-renames to match
-by any combination of modtime, hash, size. Matching by size is always
-enabled no matter what option is selected here. This also means that it
-enables --track-renames support for encrypted destinations. If nothing
-is specified, the default option is matching by hashes.
+This option changes the matching criteria for --track-renames.
 
-–delete-(before,during,after)
+The matching is controlled by a comma separated selection of these
+tokens:
+
+-   modtime - the modification time of the file - not supported on all
+    backends
+-   hash - the hash of the file contents - not supported on all backends
+-   leaf - the name of the file not including its directory name
+-   size - the size of the file (this is always enabled)
+
+So using --track-renames-strategy modtime,leaf would match files based
+on modification time, the leaf of the file name and the size only.
+
+Using --track-renames-strategy modtime or leaf can enable
+--track-renames support for encrypted destinations.
+
+If nothing is specified, the default option is matching by hashes.
+
+Note that the hash strategy is not supported with encrypted
+destinations.
+
+--delete-(before,during,after)
 
 This option allows you to specify when files on your destination are
 deleted when you sync folders.
@@ -6621,7 +7247,7 @@ subsequent to that. If there have been errors before the deletions start
 then you will get the message
 not deleting files as there were IO errors.
 
-–fast-list
+--fast-list
 
 When doing anything which involves a directory listing (eg sync, copy,
 ls - in fact nearly every command), rclone normally lists a directory
@@ -6641,26 +7267,26 @@ listing:
 -   It WILL use more memory. Rclone has to load the whole listing into
     memory.
 -   It _may_ be faster because it uses fewer transactions
--   It _may_ be slower because it can’t be parallelized
+-   It _may_ be slower because it can't be parallelized
 
 rclone should always give identical results with and without
 --fast-list.
 
 If you pay for transactions and can fit your entire sync listing into
 memory then --fast-list is recommended. If you have a very big sync to
-do then don’t use --fast-list otherwise you will run out of memory.
+do then don't use --fast-list otherwise you will run out of memory.
 
-If you use --fast-list on a remote which doesn’t support it, then rclone
+If you use --fast-list on a remote which doesn't support it, then rclone
 will just ignore it.
 
-–timeout=TIME
+--timeout=TIME
 
 This sets the IO idle timeout. If a transfer has started but then
 becomes idle for this long it is considered broken and disconnected.
 
 The default is 5m. Set to 0 to disable.
 
-–transfers=N
+--transfers=N
 
 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
@@ -6668,31 +7294,31 @@ timeouts or bigger if you have lots of bandwidth and a fast remote.
 
 The default is to run 4 file transfers in parallel.
 
--u, –update
+-u, --update
 
 This forces rclone to skip any files which exist on the destination and
 have a modified time that is newer than the source file.
 
-This can be useful when transferring to a remote which doesn’t support
+This can be useful when transferring to a remote which doesn't support
 mod times directly (or when using --use-server-modtime to avoid extra
 API calls) as it is more accurate than a --size-only check and faster
 than using --checksum.
 
 If an existing destination file has a modification time equal (within
-the computed modify window precision) to the source file’s, it will be
+the computed modify window precision) to the source file's, it will be
 updated if the sizes are different. If --checksum is set then rclone
 will update the destination if the checksums differ too.
 
 If an existing destination file is older than the source file then it
 will be updated if the size or checksum differs from the source file.
 
-On remotes which don’t support mod time directly (or when using
+On remotes which don't support mod time directly (or when using
 --use-server-modtime) the time checked will be the uploaded time. This
 means that if uploading to one of these remotes, rclone will skip any
 files which exist on the destination and have an uploaded time that is
 newer than the modification time of the source file.
 
-–use-mmap
+--use-mmap
 
 If this flag is set then rclone will use anonymous memory allocated by
 mmap on Unix based platforms and VirtualAlloc on Windows for its
@@ -6707,7 +7333,7 @@ are returned less aggressively to the OS.
 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.
 
-–use-server-modtime
+--use-server-modtime
 
 Some object-store backends (e.g, Swift, S3) do not preserve file
 modification times (modtime). On these backends, rclone stores the
@@ -6716,7 +7342,7 @@ will make an API call to retrieve the metadata when the modtime is
 needed by an operation.
 
 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
+server's modified time. In cases such as a local to remote sync using
 --update, 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.
@@ -6725,7 +7351,7 @@ Using this flag on a sync operation without also using --update 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.
 
--v, -vv, –verbose
+-v, -vv, --verbose
 
 With -v rclone will tell you about each file that is transferred and a
 small number of significant events.
@@ -6734,7 +7360,7 @@ With -vv rclone will become very verbose telling you about every file it
 considers and transfers. Please send bug reports with a log with this
 setting.
 
--V, –version
+-V, --version
 
 Prints the version number
 
@@ -6746,7 +7372,7 @@ 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.
 
-–ca-cert string
+--ca-cert string
 
 This loads the PEM encoded certificate authority certificate and uses it
 to verify the certificates of the servers rclone connects to.
@@ -6754,7 +7380,7 @@ to verify the certificates of the servers rclone connects to.
 If you have generated certificates signed with a local CA then you will
 need this flag to connect to servers using those certificates.
 
-–client-cert string
+--client-cert string
 
 This loads the PEM encoded client side certificate.
 
@@ -6762,14 +7388,14 @@ This is used for mutual TLS authentication.
 
 The --client-key flag is required too when using this.
 
-–client-key string
+--client-key string
 
 This loads the PEM encoded client side private key used for mutual TLS
 authentication. Used in conjunction with --client-cert.
 
-–no-check-certificate=true/false
+--no-check-certificate=true/false
 
---no-check-certificate controls whether a client verifies the server’s
+--no-check-certificate controls whether a client verifies the server's
 certificate chain and host name. If --no-check-certificate 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
@@ -6786,7 +7412,7 @@ Your configuration file contains information for logging in to your
 cloud services. This means that you should keep your .rclone.conf file
 in a secure location.
 
-If you are in an environment where that isn’t possible, you can add a
+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.
 
@@ -6878,22 +7504,22 @@ If you are running rclone inside a script, unless you are using the
 --password-command method, you might want to disable password prompts.
 To do that, pass the parameter --ask-password=false to rclone. This will
 make rclone fail instead of asking for a password if RCLONE_CONFIG_PASS
-doesn’t contain a valid password, and --password-command has not been
+doesn't contain a valid password, and --password-command has not been
 supplied.
 
 
 Developer options
 
 These options are useful when developing or debugging rclone. There are
-also some more remote specific options which aren’t documented here
+also some more remote specific options which aren't documented here
 which are used for testing. These start with remote name eg
 --drive-test-option - see the docs for the remote in question.
 
-–cpuprofile=FILE
+--cpuprofile=FILE
 
 Write CPU profile to file. This can be analysed with go tool pprof.
 
-–dump flag,flag,flag
+--dump flag,flag,flag
 
 The --dump flag takes a comma separated list of flags to dump info
 about.
@@ -6905,53 +7531,53 @@ the body of the request will be gunzipped before showing it.
 
 The available flags are:
 
-–dump headers
+--dump headers
 
 Dump HTTP headers with Authorization: lines removed. May still contain
 sensitive info. Can be very verbose. Useful for debugging only.
 
 Use --dump auth if you do want the Authorization: headers.
 
-–dump bodies
+--dump bodies
 
 Dump HTTP headers and bodies - may contain sensitive info. Can be very
 verbose. Useful for debugging only.
 
-Note that the bodies are buffered in memory so don’t use this for
+Note that the bodies are buffered in memory so don't use this for
 enormous files.
 
-–dump requests
+--dump requests
 
 Like --dump bodies but dumps the request bodies and the response
 headers. Useful for debugging download problems.
 
-–dump responses
+--dump responses
 
 Like --dump bodies but dumps the response bodies and the request
 headers. Useful for debugging upload problems.
 
-–dump auth
+--dump auth
 
 Dump HTTP headers - will contain sensitive info such as Authorization:
 headers - use --dump headers to dump without Authorization: headers. Can
 be very verbose. Useful for debugging only.
 
-–dump filters
+--dump filters
 
 Dump the filters to the output. Useful to see exactly what include and
 exclude options are filtering on.
 
-–dump goroutines
+--dump goroutines
 
 This dumps a list of the running go-routines at the end of the command
 to standard output.
 
-–dump openfiles
+--dump openfiles
 
 This dumps a list of the open files at the end of the command. It uses
-the lsof command to do that so you’ll need that installed to use it.
+the lsof command to do that so you'll need that installed to use it.
 
-–memprofile=FILE
+--memprofile=FILE
 
 Write memory profile to file. This can be analysed with go tool pprof.
 
@@ -7049,9 +7675,9 @@ List of exit codes
 -   5 - Temporary error (one that more retries might fix) (Retry errors)
 -   6 - Less serious errors (like 461 errors from dropbox) (NoRetry
     errors)
--   7 - Fatal error (one that more retries won’t fix, like account
+-   7 - Fatal error (one that more retries won't fix, like account
     suspended) (Fatal errors)
--   8 - Transfer exceeded - limit set by –max-transfer reached
+-   8 - Transfer exceeded - limit set by --max-transfer reached
 -   9 - Operation successful, but no files transferred
 
 
@@ -7105,6 +7731,28 @@ For example, to configure an S3 remote named mys3: without a config file
 Note that if you want to create a remote using environment variables you
 must create the ..._TYPE variable as above.
 
+Precedence
+
+The various different methods of backend configuration are read in this
+order and the first one with a value is used.
+
+-   Flag values as supplied on the command line, eg --drive-use-trash.
+-   Remote specific environment vars, eg
+    RCLONE_CONFIG_MYREMOTE_USE_TRASH (see above).
+-   Backend specific environment vars, eg RCLONE_DRIVE_USE_TRASH.
+-   Config file, eg use_trash = false.
+-   Default values, eg true - these can't be changed.
+
+So if both --drive-use-trash is supplied on the config line and an
+environment variable RCLONE_DRIVE_USE_TRASH is set, the command line
+flag will take preference.
+
+For non backend configuration the order is as follows:
+
+-   Flag values as supplied on the command line, eg --stats 5s.
+-   Environment vars, eg RCLONE_STATS=5s.
+-   Default values, eg 1m - these can't be changed.
+
 Other environment variables
 
 -   RCLONE_CONFIG_PASS set to contain your config file password (see
@@ -7113,7 +7761,10 @@ Other environment variables
     thereof).
     -   HTTPS_PROXY takes precedence over HTTP_PROXY for https requests.
     -   The environment values may be either a complete URL or a
-        “host[:port]” for, in which case the “http” scheme is assumed.
+        "host[:port]" for, in which case the "http" scheme is assumed.
+-   RCLONE_CONFIG_DIR - rclone SETS this variable for use in config
+    files and sub processes to point to the directory holding the config
+    file.
 
 
 
@@ -7225,11 +7876,11 @@ understand - as a file name to mean read from standard input.
 Patterns
 
 The patterns used to match files for inclusion or exclusion are based on
-“file globs” as used by the unix shell.
+"file globs" as used by the unix shell.
 
 If the pattern starts with a / then it only matches at the top level of
 the directory tree, RELATIVE TO THE ROOT OF THE REMOTE (not necessarily
-the root of the local drive). If it doesn’t start with / then it is
+the root of the local drive). If it doesn't start with / then it is
 matched starting at the END OF THE PATH, but it will only match a
 complete path element:
 
@@ -7299,7 +7950,7 @@ With --ignore-case
 
 Note also that rclone filter globs can only be used in one of the filter
 command line flags, not in the specification of the remote, so
-rclone copy "remote:dir*.jpg" /path/to/dir won’t work - what is required
+rclone copy "remote:dir*.jpg" /path/to/dir won't work - what is required
 is rclone --include "*.jpg" copy remote:dir /path/to/dir
 
 Directories
@@ -7318,12 +7969,12 @@ If you put any rules which end in / then it will only match directories.
 
 Directory matches are ONLY used to optimise directory access patterns -
 you must still match the files that you want to match. Directory matches
-won’t optimise anything on bucket based remotes (eg s3, swift, google
-compute storage, b2) which don’t have a concept of directory.
+won't optimise anything on bucket based remotes (eg s3, swift, google
+compute storage, b2) which don't have a concept of directory.
 
 Differences between rsync and rclone patterns
 
-Rclone implements bash style {a,b,c} glob matching which rsync doesn’t.
+Rclone implements bash style {a,b,c} glob matching which rsync doesn't.
 
 Rclone always does a wildcard match so \ must always escape a \.
 
@@ -7435,7 +8086,7 @@ and no others.
 This adds an implicit --exclude * at the very end of the filter list.
 This means you can mix --include and --include-from with the other
 filters (eg --exclude) but you must include all the files you want in
-the include statement. If this doesn’t provide enough flexibility then
+the include statement. If this doesn't provide enough flexibility then
 you must use --filter-from.
 
 --include-from - Read include patterns from file
@@ -7460,7 +8111,7 @@ This is useful if you have a lot of rules.
 This adds an implicit --exclude * at the very end of the filter list.
 This means you can mix --include and --include-from with the other
 filters (eg --exclude) but you must include all the files you want in
-the include statement. If this doesn’t provide enough flexibility then
+the include statement. If this doesn't provide enough flexibility then
 you must use --filter-from.
 
 --filter - Add a file-filtering rule
@@ -7526,7 +8177,7 @@ read in the order that they are placed on the command line.
 
 Paths within the --files-from file will be interpreted as starting with
 the root specified in the command. Leading / characters are ignored. See
-–files-from-raw if you need the input to be processed in a raw manner.
+--files-from-raw if you need the input to be processed in a raw manner.
 
 For example, suppose you had files-from.txt with this content:
 
@@ -7543,14 +8194,14 @@ This will transfer these files only (if they exist)
     /home/me/pics/file1.jpg        → remote:pics/file1.jpg
     /home/me/pics/subdir/file2.jpg → remote:pics/subdir/file2.jpg
 
-To take a more complicated example, let’s say you had a few files you
+To take a more complicated example, let's say you had a few files you
 want to back up regularly with these absolute paths:
 
     /home/user1/important
     /home/user1/dir/file
     /home/user2/stuff
 
-To copy these you’d find a common subdirectory - in this case /home and
+To copy these you'd find a common subdirectory - in this case /home and
 put the remaining files in files-from.txt with or without leading /, eg
 
     user1/important
@@ -7594,7 +8245,7 @@ without any processing. rclone lsf has a compatible format that can be
 used to export file lists from remotes, which can then be used as an
 input to --files-from-raw.
 
---min-size - Don’t transfer any file smaller than this
+--min-size - Don't transfer any file smaller than this
 
 This option controls the minimum size file which will be transferred.
 This defaults to kBytes but a suffix of k, M, or G can be used.
@@ -7602,7 +8253,7 @@ This defaults to kBytes but a suffix of k, M, or G can be used.
 For example --min-size 50k means no files smaller than 50kByte will be
 transferred.
 
---max-size - Don’t transfer any file larger than this
+--max-size - Don't transfer any file larger than this
 
 This option controls the maximum size file which will be transferred.
 This defaults to kBytes but a suffix of k, M, or G can be used.
@@ -7610,7 +8261,7 @@ This defaults to kBytes but a suffix of k, M, or G can be used.
 For example --max-size 1G means no files larger than 1GByte will be
 transferred.
 
---max-age - Don’t transfer any file older than this
+--max-age - Don't transfer any file older than this
 
 This option controls the maximum age of files to transfer. Give in
 seconds or with a suffix of:
@@ -7629,12 +8280,12 @@ transferred.
 
 This can also be an absolute time in one of these formats
 
--   RFC3339 - eg “2006-01-02T15:04:05Z07:00”
--   ISO8601 Date and time, local timezone - “2006-01-02T15:04:05”
--   ISO8601 Date and time, local timezone - “2006-01-02 15:04:05”
--   ISO8601 Date - “2006-01-02” (YYYY-MM-DD)
+-   RFC3339 - eg "2006-01-02T15:04:05Z07:00"
+-   ISO8601 Date and time, local timezone - "2006-01-02T15:04:05"
+-   ISO8601 Date and time, local timezone - "2006-01-02 15:04:05"
+-   ISO8601 Date - "2006-01-02" (YYYY-MM-DD)
 
---min-age - Don’t transfer any file younger than this
+--min-age - Don't transfer any file younger than this
 
 This option controls the minimum age of files to transfer. Give in
 seconds or with a suffix (see --max-age for list of suffixes)
@@ -7652,7 +8303,7 @@ from the sync on the destination.
 If for example you did a sync from A to B without the --min-size 50k
 flag
 
-    rclone sync A: B:
+    rclone sync -i A: B:
 
 Then you repeated it like this with the --delete-excluded
 
@@ -7712,9 +8363,9 @@ Imagine, you have the following directory structure:
 
 You can exclude dir3 from sync by running the following command:
 
-    rclone sync --exclude-if-present .ignore dir1 remote:backup
+    rclone sync -i --exclude-if-present .ignore dir1 remote:backup
 
-Currently only one filename is supported, i.e. --exclude-if-present
+Currently only one filename is supported, i.e. --exclude-if-present
 should not be used multiple times.
 
 
@@ -7773,7 +8424,7 @@ How it works
 
 When you run the rclone rcd --rc-web-gui this is what happens
 
--   Rclone starts but only runs the remote control API (“rc”).
+-   Rclone starts but only runs the remote control API ("rc").
 -   The API is bound to localhost with an auto generated username and
     password.
 -   If the API bundle is missing then rclone will download it.
@@ -7846,55 +8497,55 @@ If you just want to run a remote control then see the rcd command.
 
 Supported parameters
 
-–rc
+--rc
 
 Flag to start the http server listen on remote requests
 
-–rc-addr=IP
+--rc-addr=IP
 
-IPaddress:Port or :Port to bind server to. (default “localhost:5572”)
+IPaddress:Port or :Port to bind server to. (default "localhost:5572")
 
-–rc-cert=KEY
+--rc-cert=KEY
 
 SSL PEM key (concatenation of certificate and CA certificate)
 
-–rc-client-ca=PATH
+--rc-client-ca=PATH
 
 Client certificate authority to verify clients with
 
-–rc-htpasswd=PATH
+--rc-htpasswd=PATH
 
 htpasswd file - if not provided no authentication is done
 
-–rc-key=PATH
+--rc-key=PATH
 
 SSL PEM Private key
 
-–rc-max-header-bytes=VALUE
+--rc-max-header-bytes=VALUE
 
 Maximum size of request header (default 4096)
 
-–rc-user=VALUE
+--rc-user=VALUE
 
 User name for authentication.
 
-–rc-pass=VALUE
+--rc-pass=VALUE
 
 Password for authentication.
 
-–rc-realm=VALUE
+--rc-realm=VALUE
 
-Realm for authentication (default “rclone”)
+Realm for authentication (default "rclone")
 
-–rc-server-read-timeout=DURATION
+--rc-server-read-timeout=DURATION
 
 Timeout for server reading data (default 1h0m0s)
 
-–rc-server-write-timeout=DURATION
+--rc-server-write-timeout=DURATION
 
 Timeout for server writing data (default 1h0m0s)
 
-–rc-serve
+--rc-serve
 
 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
@@ -7904,7 +8555,7 @@ syntax http://127.0.0.1:5572/[remote:path]/path/to/object
 
 Default Off.
 
-–rc-files /path/to/directory
+--rc-files /path/to/directory
 
 Path to local files to serve on the HTTP server.
 
@@ -7917,64 +8568,64 @@ the authorization in the URL in the http://user:pass@localhost/ style.
 
 Default Off.
 
-–rc-enable-metrics
+--rc-enable-metrics
 
 Enable OpenMetrics/Prometheus compatible endpoint at /metrics.
 
 Default Off.
 
-–rc-web-gui
+--rc-web-gui
 
 Set this flag to serve the default web gui on the same port as rclone.
 
 Default Off.
 
-–rc-allow-origin
+--rc-allow-origin
 
 Set the allowed Access-Control-Allow-Origin for rc requests.
 
-Can be used with –rc-web-gui if the rclone is running on different IP
+Can be used with --rc-web-gui if the rclone is running on different IP
 than the web-gui.
 
 Default is IP address on which rc is running.
 
-–rc-web-fetch-url
+--rc-web-fetch-url
 
 Set the URL to fetch the rclone-web-gui files from.
 
 Default
 https://api.github.com/repos/rclone/rclone-webui-react/releases/latest.
 
-–rc-web-gui-update
+--rc-web-gui-update
 
 Set this flag to check and update rclone-webui-react from the
 rc-web-fetch-url.
 
 Default Off.
 
-–rc-web-gui-force-update
+--rc-web-gui-force-update
 
 Set this flag to force update rclone-webui-react from the
 rc-web-fetch-url.
 
 Default Off.
 
-–rc-web-gui-no-open-browser
+--rc-web-gui-no-open-browser
 
 Set this flag to disable opening browser automatically when using
 web-gui.
 
 Default Off.
 
-–rc-job-expire-duration=DURATION
+--rc-job-expire-duration=DURATION
 
 Expire finished async jobs older than DURATION (default 60s).
 
-–rc-job-expire-interval=DURATION
+--rc-job-expire-interval=DURATION
 
 Interval duration to check for expired async jobs (default 10s).
 
-–rc-no-auth
+--rc-no-auth
 
 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
@@ -8004,6 +8655,9 @@ You can use it like this
 Run rclone rc on its own to see the help for the installed remote
 control commands.
 
+
+JSON input
+
 rclone rc also supports a --json flag which can be used to send more
 complicated input parameters.
 
@@ -8021,6 +8675,16 @@ complicated input parameters.
         }
     }
 
+If the parameter being passed is an object then it can be passed as a
+JSON string rather than using the --json flag which simplifies the
+command line.
+
+    rclone rc operations/list fs=/tmp remote=test opt='{"showHash": true}'
+
+Rather than
+
+    rclone rc operations/list --json '{"fs": "/tmp", "remote": "test", "opt": {"showHash": true}}'
+
 
 Special parameters
 
@@ -8112,7 +8776,7 @@ backend/command: Runs a backend command.
 This takes the following parameters
 
 -   command - a string with the command name
--   fs - a remote name string eg “drive:”
+-   fs - a remote name string eg "drive:"
 -   arg - a list of arguments for the backend command
 -   opt - a map of string to string of options
 
@@ -8140,11 +8804,11 @@ Returns
         }
     }
 
-Note that this is the direct equivalent of using this “backend” command:
+Note that this is the direct equivalent of using this "backend" command:
 
     rclone backend noop . -o echo=yes -o blue path1 path2
 
-Note that arguments must be preceded by the “-a” flag
+Note that arguments must be preceded by the "-a" flag
 
 See the backend command for more information.
 
@@ -8172,14 +8836,14 @@ similar to Python slices: start[:end]
 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
+count from the back of the file. The value "-5:" represents the last 5
 chunks of a file.
 
-Some valid examples are: “:5,-5:” -> the first and last five chunks
-“0,-2” -> the first and the second last chunk “0:10” -> the first ten
+Some valid examples are: ":5,-5:" -> the first and last five chunks
+"0,-2" -> the first and the second last chunk "0:10" -> the first ten
 chunks
 
-Any parameter with a key that starts with “file” can be used to specify
+Any parameter with a key that starts with "file" can be used to specify
 files to fetch, eg
 
     rclone rc cache/fetch chunks=0 file=hello file2=home/goodbye
@@ -8196,7 +8860,7 @@ config/create: create the config for a remote.
 This takes the following parameters
 
 -   name - name of remote
--   parameters - a map of { “key”: “value” } pairs
+-   parameters - a map of { "key": "value" } pairs
 -   type - type of the new remote
 -   obscure - optional bool - forces obscuring of passwords
 -   noObscure - optional bool - forces passwords not to be obscured
@@ -8248,7 +8912,7 @@ config/password: password the config for a remote.
 This takes the following parameters
 
 -   name - name of remote
--   parameters - a map of { “key”: “value” } pairs
+-   parameters - a map of { "key": "value" } pairs
 
 See the config password command command for more information on the
 above.
@@ -8269,7 +8933,7 @@ config/update: update the config for a remote.
 This takes the following parameters
 
 -   name - name of remote
--   parameters - a map of { “key”: “value” } pairs
+-   parameters - a map of { "key": "value" } pairs
 -   obscure - optional bool - forces obscuring of passwords
 -   noObscure - optional bool - forces passwords not to be obscured
 
@@ -8302,9300 +8966,9242 @@ If the rate parameter is not supplied then the bandwidth is queried
         "rate": "1M"
     }
 
-The format of the parameter is exactly the same as passed to –bwlimit
+The format of the parameter is exactly the same as passed to --bwlimit
 except only one bandwidth may be specified.
 
-In either case “rate” is returned as a human readable string, and
-“bytesPerSecond” is returned as a number.
+In either case "rate" is returned as a human readable string, and
+"bytesPerSecond" is returned as a number.
 
-core/gc: Runs a garbage collection.
-
-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.
-
-core/group-list: Returns list of stats.
-
-This returns list of stats groups currently in memory.
-
-Returns the following values:
-
-    {
-        "groups":  an array of group names:
-            [
-                "group1",
-                "group2",
-                ...
-            ]
-    }
-
-core/memstats: Returns the memory statistics
-
-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
-
-The most interesting values for most people are:
-
--   HeapAlloc: This is the amount of memory rclone is actually using
--   HeapSys: This is the amount of memory rclone has obtained from the
-    OS
--   Sys: this is the total amount of memory requested from the OS
-    -   It is virtual memory so may include unused memory
-
-core/obscure: Obscures a string passed in.
-
-Pass a clear string and rclone will obscure it for the config file: -
-clear - string
-
-Returns - obscured - string
-
-core/pid: Return PID of current process
-
-This returns PID of current process. Useful for stopping rclone process.
-
-core/quit: Terminates the app.
-
-(optional) Pass an exit code to be used for terminating the app: -
-exitCode - int
-
-core/stats: Returns stats about current transfers.
-
-This returns all available stats:
-
-    rclone rc core/stats
-
-If group is not provided then summed up stats for all groups will be
-returned.
-
-Parameters
-
--   group - name of the stats group (string)
-
-Returns the following values:
-
-    {
-        "speed": average speed in bytes/sec since start of the process,
-        "bytes": total transferred bytes since the start of the process,
-        "errors": number of errors,
-        "fatalError": whether there has been at least one FatalError,
-        "retryError": whether there has been at least one non-NoRetryError,
-        "checks": number of checked files,
-        "transfers": number of transferred files,
-        "deletes" : number of deleted files,
-        "renames" : number of renamed files,
-        "elapsedTime": time in seconds since the start of the process,
-        "lastError": last occurred error,
-        "transferring": an array of currently active file transfers:
-            [
-                {
-                    "bytes": total transferred bytes for this file,
-                    "eta": estimated time in seconds until file transfer completion
-                    "name": name of the file,
-                    "percentage": progress of the file transfer in percent,
-                    "speed": speed in bytes/sec,
-                    "speedAvg": speed in bytes/sec as an exponentially weighted moving average,
-                    "size": size of the file in bytes
-                }
-            ],
-        "checking": an array of names of currently active file checks
-            []
-    }
-
-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.
-
-core/stats-delete: Delete stats group.
-
-This deletes entire stats group
-
-Parameters
-
--   group - name of the stats group (string)
-
-core/stats-reset: Reset stats.
-
-This clears counters, errors and finished transfers for all stats or
-specific stats group if group is provided.
-
-Parameters
-
--   group - name of the stats group (string)
-
-core/transferred: Returns stats about completed transfers.
-
-This returns stats about completed transfers:
-
-    rclone rc core/transferred
-
-If group is not provided then completed transfers for all groups will be
-returned.
-
-Note only the last 100 completed transfers are returned.
-
-Parameters
-
--   group - name of the stats group (string)
-
-Returns the following values:
-
-    {
-        "transferred":  an array of completed transfers (including failed ones):
-            [
-                {
-                    "name": name of the file,
-                    "size": size of the file in bytes,
-                    "bytes": total transferred bytes for this file,
-                    "checked": if the transfer is only checked (skipped, deleted),
-                    "timestamp": integer representing millisecond unix epoch,
-                    "error": string description of the error (empty if successful),
-                    "jobid": id of the job that this transfer belongs to
-                }
-            ]
-    }
-
-core/version: Shows the current version of rclone and the go runtime.
-
-This shows the current version of go and the go runtime
-
--   version - rclone version, eg “v1.44”
--   decomposed - version number as [major, minor, patch, subpatch]
-    -   note patch and subpatch will be 999 for a git compiled version
--   isGit - boolean - true if this was compiled from the git version
--   os - OS in use as according to Go
--   arch - cpu architecture in use according to Go
--   goVersion - version of Go runtime in use
-
-debug/set-block-profile-rate: Set runtime.SetBlockProfileRate for blocking profiling.
-
-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.
-
-To include every blocking event in the profile, pass rate = 1. To turn
-off profiling entirely, pass rate <= 0.
-
-After calling this you can use this to see the blocking profile:
-
-    go tool pprof http://localhost:5572/debug/pprof/block
-
-Parameters
-
--   rate - int
-
-debug/set-mutex-profile-fraction: Set runtime.SetMutexProfileFraction for mutex profiling.
-
-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.
-
-To turn off profiling entirely, pass rate 0. To just read the current
-rate, pass rate < 0. (For n>1 the details of sampling may change.)
-
-Once this is set you can look use this to profile the mutex contention:
-
-    go tool pprof http://localhost:5572/debug/pprof/mutex
-
-Parameters
-
--   rate - int
-
-Results
-
--   previousRate - int
-
-job/list: Lists the IDs of the running jobs
-
-Parameters - None
-
-Results
-
--   jobids - array of integer job ids
-
-job/status: Reads the status of the job ID
-
-Parameters
-
--   jobid - id of the job (integer)
-
-Results
-
--   finished - boolean
--   duration - time in seconds that the job ran for
--   endTime - time the job finished (eg
-    “2018-10-26T18:50:20.528746884+01:00”)
--   error - error from the job or empty string for no error
--   finished - boolean whether the job has finished or not
--   id - as passed in above
--   startTime - time the job started (eg
-    “2018-10-26T18:50:20.528336039+01:00”)
--   success - boolean - true for success false otherwise
--   output - output of the job as would have been returned if called
-    synchronously
--   progress - output of the progress related to the underlying job
-
-job/stop: Stop the running job
-
-Parameters
-
--   jobid - id of the job (integer)
-
-mount/mount: Create a new mount point
-
-rclone allows Linux, FreeBSD, macOS and Windows to mount any of Rclone’s
-cloud storage systems as a file system with FUSE.
-
-If no mountType is provided, the priority is given as follows: 1. mount
-2.cmount 3.mount2
+core/command: Run a rclone terminal command over rc.
 
 This takes the following parameters
 
--   fs - a remote path to be mounted (required)
--   mountPoint: valid path on the local machine (required)
--   mountType: One of the values (mount, cmount, mount2) specifies the
-    mount implementation to use
-
-Eg
-
-    rclone rc mount/mount fs=mydrive: mountPoint=/home/<user>/mountPoint
-    rclone rc mount/mount fs=mydrive: mountPoint=/home/<user>/mountPoint mountType=mount
-
-AUTHENTICATION IS REQUIRED FOR THIS CALL.
-
-mount/types: Show all possible mount types
-
-This shows all possible mount types and returns them as a list.
-
-This takes no parameters and returns
-
--   mountTypes: list of mount types
-
-The mount types are strings like “mount”, “mount2”, “cmount” and can be
-passed to mount/mount as the mountType parameter.
-
-Eg
-
-    rclone rc mount/types
-
-AUTHENTICATION IS REQUIRED FOR THIS CALL.
-
-mount/unmount: Unmount all active mounts
-
-rclone allows Linux, FreeBSD, macOS and Windows to mount any of Rclone’s
-cloud storage systems as a file system with FUSE.
-
-This takes the following parameters
-
--   mountPoint: valid path on the local machine where the mount was
-    created (required)
-
-Eg
-
-    rclone rc mount/unmount mountPoint=/home/<user>/mountPoint
-
-AUTHENTICATION IS REQUIRED FOR THIS CALL.
-
-operations/about: Return the space used on the remote
-
-This takes the following parameters
-
--   fs - a remote name string eg “drive:”
-
-The result is as returned from rclone about –json
-
-See the about command command for more information on the above.
-
-AUTHENTICATION IS REQUIRED FOR THIS CALL.
-
-operations/cleanup: Remove trashed files in the remote or path
-
-This takes the following parameters
-
--   fs - a remote name string eg “drive:”
-
-See the cleanup command command for more information on the above.
-
-AUTHENTICATION IS REQUIRED FOR THIS CALL.
-
-operations/copyfile: Copy a file from source remote to destination remote
-
-This takes the following parameters
-
--   srcFs - a remote name string eg “drive:” for the source
--   srcRemote - a path within that remote eg “file.txt” for the source
--   dstFs - a remote name string eg “drive2:” for the destination
--   dstRemote - a path within that remote eg “file2.txt” for the
-    destination
-
-AUTHENTICATION IS REQUIRED FOR THIS CALL.
-
-operations/copyurl: Copy the URL to the object
-
-This takes the following parameters
-
--   fs - a remote name string eg “drive:”
--   remote - a path within that remote eg “dir”
--   url - string, URL to read from
--   autoFilename - boolean, set to true to retrieve destination file
-    name from url See the copyurl command command for more information
-    on the above.
-
-AUTHENTICATION IS REQUIRED FOR THIS CALL.
-
-operations/delete: Remove files in the path
-
-This takes the following parameters
-
--   fs - a remote name string eg “drive:”
-
-See the delete command command for more information on the above.
-
-AUTHENTICATION IS REQUIRED FOR THIS CALL.
-
-operations/deletefile: Remove the single file pointed to
-
-This takes the following parameters
-
--   fs - a remote name string eg “drive:”
--   remote - a path within that remote eg “dir”
-
-See the deletefile command command for more information on the above.
-
-AUTHENTICATION IS REQUIRED FOR THIS CALL.
-
-operations/fsinfo: Return information about the remote
-
-This takes the following parameters
-
--   fs - a remote name string eg “drive:”
-
-This returns info about the remote passed in;
-
-    {
-        // optional features and whether they are available or not
-        "Features": {
-            "About": true,
-            "BucketBased": false,
-            "CanHaveEmptyDirectories": true,
-            "CaseInsensitive": false,
-            "ChangeNotify": false,
-            "CleanUp": false,
-            "Copy": false,
-            "DirCacheFlush": false,
-            "DirMove": true,
-            "DuplicateFiles": false,
-            "GetTier": false,
-            "ListR": false,
-            "MergeDirs": false,
-            "Move": true,
-            "OpenWriterAt": true,
-            "PublicLink": false,
-            "Purge": true,
-            "PutStream": true,
-            "PutUnchecked": false,
-            "ReadMimeType": false,
-            "ServerSideAcrossConfigs": false,
-            "SetTier": false,
-            "SetWrapper": false,
-            "UnWrap": false,
-            "WrapFs": false,
-            "WriteMimeType": false
-        },
-        // Names of hashes available
-        "Hashes": [
-            "MD5",
-            "SHA-1",
-            "DropboxHash",
-            "QuickXorHash"
-        ],
-        "Name": "local",    // Name as created
-        "Precision": 1,     // Precision of timestamps in ns
-        "Root": "/",        // Path as created
-        "String": "Local file system at /" // how the remote will appear in logs
-    }
-
-This command does not have a command line equivalent so use this
-instead:
-
-    rclone rc --loopback operations/fsinfo fs=remote:
-
-operations/list: List the given remote and path in JSON format
-
-This takes the following parameters
-
--   fs - a remote name string eg “drive:”
--   remote - a path within that remote eg “dir”
--   opt - a dictionary of options to control the listing (optional)
-    -   recurse - If set recurse directories
-    -   noModTime - If set return modification time
-    -   showEncrypted - If set show decrypted names
-    -   showOrigIDs - If set show the IDs for each item if known
-    -   showHash - If set return a dictionary of hashes
-
-The result is
-
--   list
-    -   This is an array of objects as described in the lsjson command
-
-See the lsjson command for more information on the above and examples.
-
-AUTHENTICATION IS REQUIRED FOR THIS CALL.
-
-operations/mkdir: Make a destination directory or container
-
-This takes the following parameters
-
--   fs - a remote name string eg “drive:”
--   remote - a path within that remote eg “dir”
-
-See the mkdir command command for more information on the above.
-
-AUTHENTICATION IS REQUIRED FOR THIS CALL.
-
-operations/movefile: Move a file from source remote to destination remote
-
-This takes the following parameters
-
--   srcFs - a remote name string eg “drive:” for the source
--   srcRemote - a path within that remote eg “file.txt” for the source
--   dstFs - a remote name string eg “drive2:” for the destination
--   dstRemote - a path within that remote eg “file2.txt” for the
-    destination
-
-AUTHENTICATION IS REQUIRED FOR THIS CALL.
-
-operations/publiclink: Create or retrieve a public link to the given file or folder.
-
-This takes the following parameters
-
--   fs - a remote name string eg “drive:”
--   remote - a path within that remote eg “dir”
+-   command - a string with the command name
+-   arg - a list of arguments for the backend command
+-   opt - a map of string to string of options
 
 Returns
 
--   url - URL of the resource
+-   result - result from the backend command
+-   error - set if rclone exits with an error code
+-   returnType - one of ("COMBINED_OUTPUT", "STREAM",
+    "STREAM_ONLY_STDOUT". "STREAM_ONLY_STDERR")
 
-See the link command command for more information on the above.
+For example
 
-AUTHENTICATION IS REQUIRED FOR THIS CALL.
-
-operations/purge: Remove a directory or container and all of its contents
-
-This takes the following parameters
-
--   fs - a remote name string eg “drive:”
--   remote - a path within that remote eg “dir”
-
-See the purge command command for more information on the above.
-
-AUTHENTICATION IS REQUIRED FOR THIS CALL.
-
-operations/rmdir: Remove an empty directory or container
-
-This takes the following parameters
-
--   fs - a remote name string eg “drive:”
--   remote - a path within that remote eg “dir”
-
-See the rmdir command command for more information on the above.
-
-AUTHENTICATION IS REQUIRED FOR THIS CALL.
-
-operations/rmdirs: Remove all the empty directories in the path
-
-This takes the following parameters
-
--   fs - a remote name string eg “drive:”
--   remote - a path within that remote eg “dir”
--   leaveRoot - boolean, set to true not to delete the root
-
-See the rmdirs command command for more information on the above.
-
-AUTHENTICATION IS REQUIRED FOR THIS CALL.
-
-operations/size: Count the number of bytes and files in remote
-
-This takes the following parameters
-
--   fs - a remote name string eg “drive:path/to/dir”
+    rclone rc core/command command=ls -a mydrive:/ -o max-depth=1
+    rclone rc core/command -a ls -a mydrive:/ -o max-depth=1
 
 Returns
 
--   count - number of files
--   bytes - number of bytes in those files
-
-See the size command command for more information on the above.
-
-AUTHENTICATION IS REQUIRED FOR THIS CALL.
-
-options/blocks: List all the option blocks
-
-Returns - options - a list of the options block names
-
-options/get: Get all the options
-
-Returns an object where keys are option block names and values are an
-object with the current option values in.
-
-This shows the internal names of the option within rclone which should
-map to the external options very easily with a few exceptions.
-
-options/set: Set an option
-
-Parameters
-
--   option block name containing an object with
-    -   key: value
-
-Repeated as often as required.
-
-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.
-
-For example:
-
-This sets DEBUG level logs (-vv)
-
-    rclone rc options/set --json '{"main": {"LogLevel": 8}}'
-
-And this sets INFO level logs (-v)
-
-    rclone rc options/set --json '{"main": {"LogLevel": 7}}'
-
-And this sets NOTICE level logs (normal without -v)
-
-    rclone rc options/set --json '{"main": {"LogLevel": 6}}'
-
-rc/error: This returns an error
-
-This returns an error with the input as part of its error string. Useful
-for testing error handling.
-
-rc/list: List all the registered remote control commands
-
-This lists all the registered remote control commands as a JSON map in
-the commands response.
-
-rc/noop: Echo the input to the output parameters
-
-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.
-
-rc/noopauth: Echo the input to the output parameters requiring auth
-
-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.
-
-AUTHENTICATION IS REQUIRED FOR THIS CALL.
-
-sync/copy: copy a directory from source remote to destination remote
-
-This takes the following parameters
-
--   srcFs - a remote name string eg “drive:src” for the source
--   dstFs - a remote name string eg “drive:dst” for the destination
-
-See the copy command command for more information on the above.
-
-AUTHENTICATION IS REQUIRED FOR THIS CALL.
-
-sync/move: move a directory from source remote to destination remote
-
-This takes the following parameters
-
--   srcFs - a remote name string eg “drive:src” for the source
--   dstFs - a remote name string eg “drive:dst” for the destination
--   deleteEmptySrcDirs - delete empty src directories if set
-
-See the move command command for more information on the above.
-
-AUTHENTICATION IS REQUIRED FOR THIS CALL.
-
-sync/sync: sync a directory from source remote to destination remote
-
-This takes the following parameters
-
--   srcFs - a remote name string eg “drive:src” for the source
--   dstFs - a remote name string eg “drive:dst” for the destination
-
-See the sync command command for more information on the above.
-
-AUTHENTICATION IS REQUIRED FOR THIS CALL.
-
-vfs/forget: Forget files or directories in the directory cache.
-
-This forgets the paths in the directory cache causing them to be re-read
-from the remote when needed.
-
-If no paths are passed in then it will forget all the paths in the
-directory cache.
-
-    rclone rc vfs/forget
-
-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, eg
-
-    rclone rc vfs/forget file=hello file2=goodbye dir=home/junk
-
-vfs/poll-interval: Get the status or update the value of the poll-interval option.
-
-Without any parameter given this returns the current status of the
-poll-interval setting.
-
-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.
-
-    rclone rc vfs/poll-interval interval=5m
-
-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.
-
-The new poll-interval value will only be active when the timeout is not
-reached.
-
-If poll-interval is updated or disabled temporarily, some changes might
-not get picked up by the polling function, depending on the used remote.
-
-vfs/refresh: Refresh the directory cache.
-
-This reads the directories for the specified paths and freshens the
-directory cache.
-
-If no paths are passed in then it will refresh the root directory.
-
-    rclone rc vfs/refresh
-
-Otherwise pass directories in as dir=path. Any parameter key starting
-with dir will refresh that directory, eg
-
-    rclone rc vfs/refresh dir=home/junk dir2=data/misc
-
-If the parameter recursive=true is given the whole directory tree will
-get refreshed. This refresh will use –fast-list if enabled.
-
-
-Accessing the remote control via HTTP
-
-Rclone implements a simple HTTP based protocol.
-
-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.
-
-All calls must made using POST.
-
-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 curl.
-
-The response will be a JSON blob in the body of the response. This is
-formatted to be reasonably human readable.
-
-Error returns
-
-If an error occurs then there will be an HTTP error status (eg 500) and
-the body of the response will contain a JSON encoded error object, eg
-
     {
-        "error": "Expecting string value for key \"remote\" (was float64)",
-        "input": {
-            "fs": "/tmp",
-            "remote": 3
-        },
-        "status": 400
-        "path": "operations/rmdir",
+        "error": false,
+        "result": "<Raw command line output>"
     }
 
-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
-
-CORS
-
-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.
-
-Using POST with URL parameters only
-
-    curl -X POST 'http://localhost:5572/rc/noop?potato=1&sausage=2'
-
-Response
-
+    OR 
     {
-        "potato": "1",
-        "sausage": "2"
+        "error": true,
+        "result": "<Raw command line output>"
     }
 
-Here is what an error response looks like:
+    **Authentication is required for this call.**
 
-    curl -X POST 'http://localhost:5572/rc/error?potato=1&sausage=2'
+    ### core/gc: Runs a garbage collection. {#core-gc}
 
-    {
-        "error": "arbitrary error on input map[potato:1 sausage:2]",
-        "input": {
-            "potato": "1",
-            "sausage": "2"
-        }
-    }
+    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.
 
-Note that curl doesn’t return errors to the shell unless you use the -f
-option
+    ### core/group-list: Returns list of stats. {#core-group-list}
 
-    $ curl -f -X POST 'http://localhost:5572/rc/error?potato=1&sausage=2'
-    curl: (22) The requested URL returned error: 400 Bad Request
-    $ echo $?
-    22
+    This returns list of stats groups currently in memory. 
 
-Using POST with a form
+    Returns the following values:
 
-    curl --data "potato=1" --data "sausage=2" http://localhost:5572/rc/noop
+{ "groups": an array of group names: [ "group1", "group2", ... ] }
 
-Response
 
-    {
-        "potato": "1",
-        "sausage": "2"
-    }
+    ### core/memstats: Returns the memory statistics {#core-memstats}
 
-Note that you can combine these with URL parameters too with the POST
-parameters taking precedence.
+    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
 
-    curl --data "potato=1" --data "sausage=2" "http://localhost:5572/rc/noop?rutabaga=3&sausage=4"
+    The most interesting values for most people are:
 
-Response
+    * HeapAlloc: This is the amount of memory rclone is actually using
+    * HeapSys: This is the amount of memory rclone has obtained from the OS
+    * Sys: this is the total amount of memory requested from the OS
+      * It is virtual memory so may include unused memory
 
-    {
-        "potato": "1",
-        "rutabaga": "3",
-        "sausage": "4"
-    }
+    ### core/obscure: Obscures a string passed in. {#core-obscure}
 
-Using POST with a JSON blob
+    Pass a clear string and rclone will obscure it for the config file:
+    - clear - string
 
-    curl -H "Content-Type: application/json" -X POST -d '{"potato":2,"sausage":1}' http://localhost:5572/rc/noop
+    Returns
+    - obscured - string
 
-response
+    ### core/pid: Return PID of current process {#core-pid}
 
-    {
-        "password": "xyz",
-        "username": "xyz"
-    }
+    This returns PID of current process.
+    Useful for stopping rclone process.
 
-This can be combined with URL parameters too if required. The JSON blob
-takes precedence.
+    ### core/quit: Terminates the app. {#core-quit}
 
-    curl -H "Content-Type: application/json" -X POST -d '{"potato":2,"sausage":1}' 'http://localhost:5572/rc/noop?rutabaga=3&potato=4'
+    (optional) Pass an exit code to be used for terminating the app:
+    - exitCode - int
 
-    {
-        "potato": 2,
-        "rutabaga": "3",
-        "sausage": 1
-    }
+    ### core/stats: Returns stats about current transfers. {#core-stats}
 
+    This returns all available stats:
 
-Debugging rclone with pprof
+        rclone rc core/stats
 
-If you use the --rc flag this will also enable the use of the go
-profiling tools on the same port.
+    If group is not provided then summed up stats for all groups will be
+    returned.
 
-To use these, first install go.
+    Parameters
 
-Debugging memory use
+    - group - name of the stats group (string)
 
-To profile rclone’s memory use you can run:
+    Returns the following values:
 
-    go tool pprof -web http://localhost:5572/debug/pprof/heap
+{ "speed": average speed in bytes/sec since start of the process,
+"bytes": total transferred bytes since the start of the process,
+"errors": number of errors, "fatalError": whether there has been at
+least one FatalError, "retryError": whether there has been at least one
+non-NoRetryError, "checks": number of checked files, "transfers": number
+of transferred files, "deletes" : number of deleted files, "renames" :
+number of renamed files, "transferTime" : total time spent on running
+jobs, "elapsedTime": time in seconds since the start of the process,
+"lastError": last occurred error, "transferring": an array of currently
+active file transfers: [ { "bytes": total transferred bytes for this
+file, "eta": estimated time in seconds until file transfer completion
+"name": name of the file, "percentage": progress of the file transfer in
+percent, "speed": average speed over the whole transfer in bytes/sec,
+"speedAvg": current speed in bytes/sec as an exponentially weighted
+moving average, "size": size of the file in bytes } ], "checking": an
+array of names of currently active file checks [] }
 
-This should open a page in your browser showing what is using what
-memory.
+    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.
 
-You can also use the -text flag to produce a textual summary
+    ### core/stats-delete: Delete stats group. {#core-stats-delete}
 
-    $ 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
+    This deletes entire stats group
 
-Debugging go routine leaks
+    Parameters
 
-Memory leaks are most often caused by go routine leaks keeping memory
-alive which should have been garbage collected.
+    - group - name of the stats group (string)
 
-See all active go routines using
+    ### core/stats-reset: Reset stats. {#core-stats-reset}
 
-    curl http://localhost:5572/debug/pprof/goroutine?debug=1
+    This clears counters, errors and finished transfers for all stats or specific 
+    stats group if group is provided.
 
-Or go to http://localhost:5572/debug/pprof/goroutine?debug=1 in your
-browser.
+    Parameters
 
-Other profiles to look at
+    - group - name of the stats group (string)
 
-You can see a summary of profiles available at
-http://localhost:5572/debug/pprof/
+    ### core/transferred: Returns stats about completed transfers. {#core-transferred}
 
-Here is how to use some of them:
+    This returns stats about completed transfers:
 
--   Memory: go tool pprof http://localhost:5572/debug/pprof/heap
--   Go routines:
-    curl http://localhost:5572/debug/pprof/goroutine?debug=1
--   30-second CPU profile:
-    go tool pprof http://localhost:5572/debug/pprof/profile
--   5-second execution trace:
-    wget http://localhost:5572/debug/pprof/trace?seconds=5
--   Goroutine blocking profile
-    -   Enable first with: rclone rc debug/set-block-profile-rate rate=1
-        (docs)
-    -   go tool pprof http://localhost:5572/debug/pprof/block
--   Contended mutexes:
-    -   Enable first with:
-        rclone rc debug/set-mutex-profile-fraction rate=1 (docs)
-    -   go tool pprof http://localhost:5572/debug/pprof/mutex
+        rclone rc core/transferred
 
-See the net/http/pprof docs for more info on how to use the profiling
-and for a general overview see the Go team’s blog post on profiling go
-programs.
+    If group is not provided then completed transfers for all groups will be
+    returned.
 
-The profiling hook is zero overhead unless it is used.
+    Note only the last 100 completed transfers are returned.
 
+    Parameters
 
+    - group - name of the stats group (string)
 
-OVERVIEW OF CLOUD STORAGE SYSTEMS
+    Returns the following values:
 
+{ "transferred": an array of completed transfers (including failed
+ones): [ { "name": name of the file, "size": size of the file in bytes,
+"bytes": total transferred bytes for this file, "checked": if the
+transfer is only checked (skipped, deleted), "timestamp": integer
+representing millisecond unix epoch, "error": string description of the
+error (empty if successful), "jobid": id of the job that this transfer
+belongs to } ] }
 
-Each cloud storage system is slightly different. Rclone attempts to
-provide a unified interface to them, but some underlying differences
-show through.
 
+    ### core/version: Shows the current version of rclone and the go runtime. {#core-version}
 
-Features
+    This shows the current version of go and the go runtime
 
-Here is an overview of the major features of each cloud storage system.
+    - version - rclone version, eg "v1.53.0"
+    - decomposed - version number as [major, minor, patch]
+    - isGit - boolean - true if this was compiled from the git version
+    - isBeta - boolean - true if this is a beta version
+    - os - OS in use as according to Go
+    - arch - cpu architecture in use according to Go
+    - goVersion - version of Go runtime in use
 
-  Name                                Hash       ModTime   Case Insensitive   Duplicate Files   MIME Type
-  ------------------------------ -------------- --------- ------------------ ----------------- -----------
-  1Fichier                         Whirlpool       No             No                Yes             R
-  Amazon Drive                        MD5          No            Yes                No              R
-  Amazon S3                           MD5          Yes            No                No             R/W
-  Backblaze B2                        SHA1         Yes            No                No             R/W
-  Box                                 SHA1         Yes           Yes                No              -
-  Citrix ShareFile                    MD5          Yes           Yes                No              -
-  Dropbox                           DBHASH †       Yes           Yes                No              -
-  FTP                                  -           No             No                No              -
-  Google Cloud Storage                MD5          Yes            No                No             R/W
-  Google Drive                        MD5          Yes            No                Yes            R/W
-  Google Photos                        -           No             No                Yes             R
-  HTTP                                 -           No             No                No              R
-  Hubic                               MD5          Yes            No                No             R/W
-  Jottacloud                          MD5          Yes           Yes                No             R/W
-  Koofr                               MD5          No            Yes                No              -
-  Mail.ru Cloud                    Mailru ‡‡‡      Yes           Yes                No              -
-  Mega                                 -           No             No                Yes             -
-  Memory                              MD5          Yes            No                No              -
-  Microsoft Azure Blob Storage        MD5          Yes            No                No             R/W
-  Microsoft OneDrive                SHA1 ‡‡        Yes           Yes                No              R
-  OpenDrive                           MD5          Yes           Yes                No              -
-  OpenStack Swift                     MD5          Yes            No                No             R/W
-  pCloud                           MD5, SHA1       Yes            No                No              W
-  premiumize.me                        -           No            Yes                No              R
-  put.io                             CRC-32        Yes            No                Yes             R
-  QingStor                            MD5          No             No                No             R/W
-  Seafile                              -           No             No                No              -
-  SFTP                            MD5, SHA1 ‡      Yes         Depends              No              -
-  SugarSync                            -           No             No                No              -
-  Tardigrade                           -           Yes            No                No              -
-  WebDAV                          MD5, SHA1 ††   Yes †††       Depends              No              -
-  Yandex Disk                         MD5          Yes            No                No             R/W
-  The local filesystem                All          Yes         Depends              No              -
+    ### debug/set-block-profile-rate: Set runtime.SetBlockProfileRate for blocking profiling. {#debug-set-block-profile-rate}
 
-Hash
+    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.
 
-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 --checksum flag in syncs and in the check
-command.
+    To include every blocking event in the profile, pass rate = 1. To turn
+    off profiling entirely, pass rate <= 0.
 
-To use the verify checksums when transferring between cloud storage
-systems they must support a common hash type.
+    After calling this you can use this to see the blocking profile:
 
-† Note that Dropbox supports its own custom hash. This is an SHA256 sum
-of all the 4MB block SHA256s.
-
-‡ SFTP supports checksums if the same login has shell access and md5sum
-or sha1sum as well as echo are in the remote’s PATH.
-
-†† WebDAV supports hashes when used with Owncloud and Nextcloud only.
-
-††† WebDAV supports modtimes when used with Owncloud and Nextcloud only.
-
-‡‡ Microsoft OneDrive Personal supports SHA1 hashes, whereas OneDrive
-for business and SharePoint server support Microsoft’s own QuickXorHash.
-
-‡‡‡ Mail.ru uses its own modified SHA1 hash
-
-ModTime
-
-The cloud storage system supports setting modification times on objects.
-If it does then this enables a using the modification times as part of
-the sync. If not then only the size will be checked by default, though
-the MD5SUM can be checked with the --checksum flag.
-
-All cloud storage systems support some kind of date on the object and
-these will be set when transferring from the cloud storage system.
-
-Case Insensitive
-
-If a cloud storage systems is case sensitive then it is possible to have
-two files which differ only in case, eg file.txt and FILE.txt. If a
-cloud storage system is case insensitive then that isn’t possible.
-
-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.
-
-The local filesystem and SFTP may or may not be case sensitive depending
-on OS.
-
--   Windows - usually case insensitive, though case is preserved
--   OSX - usually case insensitive, though it is possible to format case
-    sensitive
--   Linux - usually case sensitive, but there are case insensitive file
-    systems (eg FAT formatted USB keys)
-
-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.
-
-Duplicate files
-
-If a cloud storage system allows duplicate files then it can have two
-objects with the same name.
-
-This confuses rclone greatly when syncing - use the rclone dedupe
-command to rename or remove duplicates.
-
-Restricted filenames
-
-Some cloud storage systems might have restrictions on the characters
-that are usable in file or directory names. When rclone detects such a
-name during a file upload, it will transparently replace the restricted
-characters with similar looking Unicode characters.
-
-This process is designed to avoid ambiguous file names as much as
-possible and allow to move files between many cloud storage systems
-transparently.
-
-The name shown by rclone to the user or during log output will only
-contain a minimal set of replaced characters to ensure correct
-formatting and not necessarily the actual name used on the cloud
-storage.
-
-This transformation is reversed when downloading a file or parsing
-rclone arguments. For example, when uploading a file named my file?.txt
-to Onedrive will be displayed as my file?.txt on the console, but stored
-as my file？.txt (the ? gets replaced by the similar looking ？
-character) to Onedrive. The reverse transformation allows to read a
-fileunusual/name.txt from Google Drive, by passing the name
-unusual／name.txt (the / needs to be replaced by the similar looking ／
-character) on the command line.
-
-Default restricted characters
-
-The table below shows the characters that are replaced by default.
-
-When a replacement character is found in a filename, this character will
-be escaped with the ‛ character to avoid ambiguous file names. (e.g. a
-file named ␀.txt would shown as ‛␀.txt)
-
-Each cloud storage backend can use a different set of characters, which
-will be specified in the documentation for each backend.
-
-  Character    Value   Replacement
-  ----------- ------- -------------
-  NUL          0x00         ␀
-  SOH          0x01         ␁
-  STX          0x02         ␂
-  ETX          0x03         ␃
-  EOT          0x04         ␄
-  ENQ          0x05         ␅
-  ACK          0x06         ␆
-  BEL          0x07         ␇
-  BS           0x08         ␈
-  HT           0x09         ␉
-  LF           0x0A         ␊
-  VT           0x0B         ␋
-  FF           0x0C         ␌
-  CR           0x0D         ␍
-  SO           0x0E         ␎
-  SI           0x0F         ␏
-  DLE          0x10         ␐
-  DC1          0x11         ␑
-  DC2          0x12         ␒
-  DC3          0x13         ␓
-  DC4          0x14         ␔
-  NAK          0x15         ␕
-  SYN          0x16         ␖
-  ETB          0x17         ␗
-  CAN          0x18         ␘
-  EM           0x19         ␙
-  SUB          0x1A         ␚
-  ESC          0x1B         ␛
-  FS           0x1C         ␜
-  GS           0x1D         ␝
-  RS           0x1E         ␞
-  US           0x1F         ␟
-  /            0x2F        ／
-  DEL          0x7F         ␡
-
-The default encoding will also encode these file names as they are
-problematic with many cloud storage systems.
-
-  File name    Replacement
-  ----------- -------------
-  .                ．
-  ..              ．．
-
-Invalid UTF-8 bytes
-
-Some backends only support a sequence of well formed UTF-8 bytes as file
-or directory names.
-
-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 0xFE will be encoded as ‛FE.
-
-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
-local filenames section for details.
-
-Encoding option
-
-Most backends have an encoding options, specified as a flag
---backend-encoding where backend is the name of the backend, or as a
-config parameter encoding (you’ll need to select the Advanced config in
-rclone config to see it).
-
-This will have default value which encodes and decodes characters in
-such a way as to preserve the maximum number of characters (see above).
-
-However this can be incorrect in some scenarios, for example if you have
-a Windows file system with characters such as ＊ and ？ that you want to
-remain as those characters on the remote rather than being translated to
-* and ?.
-
-The --backend-encoding flags allow you to change that. You can disable
-the encoding completely with --backend-encoding None or set
-encoding = None in the config file.
-
-Encoding takes a comma separated list of encodings. You can see the list
-of all available characters by passing an invalid value to this flag, eg
---local-encoding "help" and rclone help flags encoding will show you the
-defaults for the backends.
-
-  Encoding        Characters
-  --------------- -------------------------------------------------------------
-  Asterisk        *
-  BackQuote       `
-  BackSlash       \
-  Colon           :
-  CrLf            CR 0x0D, LF 0x0A
-  Ctl             All control characters 0x00-0x1F
-  Del             DEL 0x7F
-  Dollar          $
-  Dot             .
-  DoubleQuote     "
-  Hash            #
-  InvalidUtf8     An invalid UTF-8 character (eg latin1)
-  LeftCrLfHtVt    CR 0x0D, LF 0x0A,HT 0x09, VT 0x0B on the left of a string
-  LeftPeriod      . on the left of a string
-  LeftSpace       SPACE on the left of a string
-  LeftTilde       ~ on the left of a string
-  LtGt            <, >
-  None            No characters are encoded
-  Percent         %
-  Pipe            |
-  Question        ?
-  RightCrLfHtVt   CR 0x0D, LF 0x0A, HT 0x09, VT 0x0B on the right of a string
-  RightPeriod     . on the right of a string
-  RightSpace      SPACE on the right of a string
-  SingleQuote     '
-  Slash           /
-
-To take a specific example, the FTP backend’s default encoding is
-
-    --ftp-encoding "Slash,Del,Ctl,RightSpace,Dot"
-
-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
-
-    Slash,LtGt,DoubleQuote,Colon,Question,Asterisk,Pipe,BackSlash,Ctl,RightSpace,RightPeriod,InvalidUtf8,Dot
-
-to the existing ones, giving:
-
-    Slash,LtGt,DoubleQuote,Colon,Question,Asterisk,Pipe,BackSlash,Ctl,RightSpace,RightPeriod,InvalidUtf8,Dot,Del,RightSpace
-
-This can be specified using the --ftp-encoding flag or using an encoding
-parameter in the config file.
-
-Or let’s say you have a Windows server but you want to preserve ＊ and
-？, you would then have this as the encoding (the Windows encoding minus
-Asterisk and Question).
-
-    Slash,LtGt,DoubleQuote,Colon,Pipe,BackSlash,Ctl,RightSpace,RightPeriod,InvalidUtf8,Dot
-
-This can be specified using the --local-encoding flag or using an
-encoding parameter in the config file.
-
-MIME Type
-
-MIME types (also known as media types) classify types of documents using
-a simple text classification, eg text/html or application/pdf.
-
-Some cloud storage systems support reading (R) the MIME type of objects
-and some support writing (W) the MIME type of objects.
-
-The MIME type can be important if you are serving files directly to HTTP
-from the storage system.
-
-If you are copying from a remote which supports reading (R) to a remote
-which supports writing (W) then rclone will preserve the MIME types.
-Otherwise they will be guessed from the extension, or the remote itself
-may assign the MIME type.
-
-
-Optional Features
-
-All the remotes support a basic set of features, but there are some
-optional features supported by some remotes used to make some operations
-more efficient.
-
-  Name                            Purge   Copy   Move   DirMove   CleanUp   ListR   StreamUpload   LinkSharing   About   EmptyDir
-  ------------------------------ ------- ------ ------ --------- --------- ------- -------------- ------------- ------- ----------
-  1Fichier                         No      No     No      No        No       No          No            No         No       Yes
-  Amazon Drive                     Yes     No    Yes      Yes     No #575    No          No         No #2178      No       Yes
-  Amazon S3                        No     Yes     No      No        No       Yes        Yes         No #2178      No        No
-  Backblaze B2                     No     Yes     No      No        Yes      Yes        Yes            Yes        No        No
-  Box                              Yes    Yes    Yes      Yes     No #575    No         Yes            Yes        No       Yes
-  Citrix ShareFile                 Yes    Yes    Yes      Yes       No       No         Yes            No         No       Yes
-  Dropbox                          Yes    Yes    Yes      Yes     No #575    No         Yes            Yes        Yes      Yes
-  FTP                              No      No    Yes      Yes       No       No         Yes         No #2178      No       Yes
-  Google Cloud Storage             Yes    Yes     No      No        No       Yes        Yes         No #2178      No        No
-  Google Drive                     Yes    Yes    Yes      Yes       Yes      Yes        Yes            Yes        Yes      Yes
-  Google Photos                    No      No     No      No        No       No          No            No         No        No
-  HTTP                             No      No     No      No        No       No          No         No #2178      No       Yes
-  Hubic                           Yes †   Yes     No      No        No       Yes        Yes         No #2178      Yes       No
-  Jottacloud                       Yes    Yes    Yes      Yes       Yes      Yes         No            Yes        Yes      Yes
-  Mail.ru Cloud                    Yes    Yes    Yes      Yes       Yes      No          No            Yes        Yes      Yes
-  Mega                             Yes     No    Yes      Yes       Yes      No          No         No #2178      Yes      Yes
-  Memory                           No     Yes     No      No        No       Yes        Yes            No         No        No
-  Microsoft Azure Blob Storage     Yes    Yes     No      No        No       Yes        Yes         No #2178      No        No
-  Microsoft OneDrive               Yes    Yes    Yes      Yes     No #575    No          No            Yes        Yes      Yes
-  OpenDrive                        Yes    Yes    Yes      Yes       No       No          No            No         No       Yes
-  OpenStack Swift                 Yes †   Yes     No      No        No       Yes        Yes         No #2178      Yes       No
-  pCloud                           Yes    Yes    Yes      Yes       Yes      No          No         No #2178      Yes      Yes
-  premiumize.me                    Yes     No    Yes      Yes       No       No          No            Yes        Yes      Yes
-  put.io                           Yes     No    Yes      Yes       Yes      No         Yes         No #2178      Yes      Yes
-  QingStor                         No     Yes     No      No        Yes      Yes         No         No #2178      No        No
-  Seafile                          Yes    Yes    Yes      Yes       Yes      Yes        Yes            Yes        Yes      Yes
-  SFTP                             No      No    Yes      Yes       No       No         Yes         No #2178      Yes      Yes
-  SugarSync                        Yes    Yes    Yes      Yes       No       No         Yes            Yes        No       Yes
-  Tardigrade                      Yes †    No     No      No        No       Yes        Yes            No         No        No
-  WebDAV                           Yes    Yes    Yes      Yes       No       No        Yes ‡        No #2178      Yes      Yes
-  Yandex Disk                      Yes    Yes    Yes      Yes       Yes      No         Yes            Yes        Yes      Yes
-  The local filesystem             Yes     No    Yes      Yes       No       No         Yes            No         Yes      Yes
+        go tool pprof http://localhost:5572/debug/pprof/block
 
-Purge
+    Parameters
 
-This deletes a directory quicker than just deleting all the files in the
-directory.
+    - rate - int
 
-† Note Swift, Hubic, and Tardigrade implement this in order to delete
-directory markers but they don’t actually have a quicker way of deleting
-files other than deleting them individually.
+    ### debug/set-mutex-profile-fraction: Set runtime.SetMutexProfileFraction for mutex profiling. {#debug-set-mutex-profile-fraction}
 
-‡ StreamUpload is not supported with Nextcloud
+    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.
 
-Copy
+    To turn off profiling entirely, pass rate 0. To just read the current
+    rate, pass rate < 0. (For n>1 the details of sampling may change.)
 
-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 rclone copy or rclone move if
-the remote doesn’t support Move directly.
+    Once this is set you can look use this to profile the mutex contention:
 
-If the server doesn’t support Copy directly then for copy operations the
-file is downloaded then re-uploaded.
+        go tool pprof http://localhost:5572/debug/pprof/mutex
 
-Move
+    Parameters
 
-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 rclone move if the server
-doesn’t support DirMove.
+    - rate - int
 
-If the server isn’t capable of Move then rclone simulates it with Copy
-then delete. If the server doesn’t support Copy then rclone will
-download the file and re-upload it.
-
-DirMove
-
-This is used to implement rclone move to move a directory if possible.
-If it isn’t then it will use Move on each file (which falls back to Copy
-then download and upload - see Move section).
-
-CleanUp
-
-This is used for emptying the trash for a remote by rclone cleanup.
-
-If the server can’t do CleanUp then rclone cleanup will return an error.
-
-ListR
-
-The remote supports a recursive list to list all the contents beneath a
-directory quickly. This enables the --fast-list flag to work. See the
-rclone docs for more details.
-
-StreamUpload
-
-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. rclone rcat.
-
-LinkSharing
-
-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.
-
-About
-
-This is used to fetch quota information from the remote, like bytes
-used/free/quota and bytes used in the trash.
-
-This is also used to return the space used, available for rclone mount.
-
-If the server can’t do About then rclone about will return an error.
-
-EmptyDir
-
-The remote supports empty directories. See Limitations for details. Most
-Object/Bucket based remotes do not support this.
-
-
-
-GLOBAL FLAGS
-
-
-This describes the global flags available to every rclone command split
-into two groups, non backend and backend flags.
-
-
-Non Backend Flags
-
-These flags are available for every command.
-
-          --ask-password                         Allow prompt for password for encrypted configuration. (default true)
-          --auto-confirm                         If enabled, do not request console confirmation.
-          --backup-dir string                    Make backups into hierarchy based in DIR.
-          --bind string                          Local address to bind to for outgoing connections, IPv4, IPv6 or name.
-          --buffer-size SizeSuffix               In memory buffer size when reading files for each --transfer. (default 16M)
-          --bwlimit BwTimetable                  Bandwidth limit in kBytes/s, or use suffix b|k|M|G or a full timetable.
-          --ca-cert string                       CA certificate used to verify servers
-          --cache-dir string                     Directory rclone will use for caching. (default "$HOME/.cache/rclone")
-          --check-first                          Do all the checks before starting transfers.
-          --checkers int                         Number of checkers to run in parallel. (default 8)
-      -c, --checksum                             Skip based on checksum (if available) & size, not mod-time & size
-          --client-cert string                   Client SSL certificate (PEM) for mutual TLS auth
-          --client-key string                    Client SSL private key (PEM) for mutual TLS auth
-          --compare-dest string                  Include additional server-side path during comparison.
-          --config string                        Config file. (default "$HOME/.config/rclone/rclone.conf")
-          --contimeout duration                  Connect timeout (default 1m0s)
-          --copy-dest string                     Implies --compare-dest but also copies files from path into destination.
-          --cpuprofile string                    Write cpu profile to file
-          --cutoff-mode string                   Mode to stop transfers when reaching the max transfer limit HARD|SOFT|CAUTIOUS (default "HARD")
-          --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
-          --delete-excluded                      Delete files on dest excluded from sync
-          --disable string                       Disable a comma separated list of features.  Use help to see a list.
-      -n, --dry-run                              Do a trial run with no permanent changes
-          --dump DumpFlags                       List of items to dump from: headers,bodies,requests,responses,auth,filters,goroutines,openfiles
-          --dump-bodies                          Dump HTTP headers and bodies - may contain sensitive info
-          --dump-headers                         Dump HTTP headers - may contain sensitive info
-          --error-on-no-transfer                 Sets exit code 9 if no files are transferred, useful in scripts
-          --exclude stringArray                  Exclude files matching pattern
-          --exclude-from stringArray             Read exclude patterns from file (use - to read from stdin)
-          --exclude-if-present string            Exclude directories if filename is present
-          --expect-continue-timeout duration     Timeout when using expect / 100-continue in HTTP (default 1s)
-          --fast-list                            Use recursive list if available. Uses more memory but fewer transactions.
-          --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 filtering patterns from a file (use - to read from stdin)
-          --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
-          --ignore-case                          Ignore case in filters (case insensitive)
-          --ignore-case-sync                     Ignore case when synchronizing
-          --ignore-checksum                      Skip post copy check of checksums.
-          --ignore-errors                        delete even if there are I/O errors
-          --ignore-existing                      Skip all files that exist on destination
-          --ignore-size                          Ignore size when skipping use mod-time or checksum.
-      -I, --ignore-times                         Don't skip files that match size and time - transfer all files
-          --immutable                            Do not modify files. Fail if existing files have been modified.
-          --include stringArray                  Include files matching pattern
-          --include-from stringArray             Read include patterns from file (use - to read from stdin)
-          --log-file string                      Log everything to this file
-          --log-format string                    Comma separated list of log format options (default "date,time")
-          --log-level string                     Log level DEBUG|INFO|NOTICE|ERROR (default "NOTICE")
-          --low-level-retries int                Number of low level retries to do. (default 10)
-          --max-age Duration                     Only transfer files younger than this in s or suffix ms|s|m|h|d|w|M|y (default off)
-          --max-backlog int                      Maximum number of objects in sync or check backlog. (default 10000)
-          --max-delete int                       When synchronizing, limit the number of deletes (default -1)
-          --max-depth int                        If set limits the recursion depth to this. (default -1)
-          --max-duration duration                Maximum duration rclone will transfer data for.
-          --max-size SizeSuffix                  Only transfer files smaller than this in k or suffix b|k|M|G (default off)
-          --max-stats-groups int                 Maximum number of stats groups to keep in memory. On max oldest is discarded. (default 1000)
-          --max-transfer SizeSuffix              Maximum size of data to transfer. (default off)
-          --memprofile string                    Write memory profile to file
-          --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 k or suffix b|k|M|G (default off)
-          --modify-window duration               Max time diff to be considered the same (default 1ns)
-          --multi-thread-cutoff SizeSuffix       Use multi-thread downloads for files above this size. (default 250M)
-          --multi-thread-streams int             Max number of streams to use for multi-thread downloads. (default 4)
-          --no-check-certificate                 Do not verify the server SSL certificate. Insecure.
-          --no-check-dest                        Don't check the destination, copy regardless.
-          --no-gzip-encoding                     Don't set Accept-Encoding: gzip.
-          --no-traverse                          Don't traverse destination file system on copy.
-          --no-unicode-normalization             Don't normalize unicode characters in filenames.
-          --no-update-modtime                    Don't update destination mod-time if files identical.
-          --order-by string                      Instructions on how to order the transfers, eg 'size,descending'
-          --password-command SpaceSepList        Command for supplying password for encrypted configuration.
-      -P, --progress                             Show progress during transfer.
-      -q, --quiet                                Print as little stuff as possible
-          --rc                                   Enable the remote control server.
-          --rc-addr string                       IPaddress:Port or :Port to bind server to. (default "localhost:5572")
-          --rc-allow-origin string               Set the allowed origin for CORS.
-          --rc-baseurl string                    Prefix for URLs - leave blank for root.
-          --rc-cert string                       SSL PEM key (concatenation of certificate and CA certificate)
-          --rc-client-ca string                  Client certificate authority to verify clients with
-          --rc-enable-metrics                    Enable prometheus metrics on /metrics
-          --rc-files string                      Path to local files to serve on the HTTP server.
-          --rc-htpasswd string                   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                        SSL PEM Private key
-          --rc-max-header-bytes int              Maximum size of request header (default 4096)
-          --rc-no-auth                           Don't require auth for certain methods.
-          --rc-pass string                       Password for authentication.
-          --rc-realm string                      realm for authentication (default "rclone")
-          --rc-serve                             Enable the serving of remote objects.
-          --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 "https://api.github.com/repos/rclone/rclone-webui-react/releases/latest")
-          --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't open the browser automatically
-          --rc-web-gui-update                    Check and update to latest version of web gui
-          --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)
-          --size-only                            Skip based on size only, not mod-time or checksum
-          --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 string               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                  Enables --stats-one-line and add current date/time prefix.
-          --stats-one-line-date-format string    Enables --stats-one-line-date and uses custom formatted date. Enclose date string in double quotes ("). See https://golang.org/pkg/time/#Time.Format
-          --stats-unit string                    Show data rate in stats as either 'bits' or 'bytes'/s (default "bytes")
-          --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 100k)
-          --suffix string                        Suffix to add to changed files.
-          --suffix-keep-extension                Preserve the extension when using --suffix.
-          --syslog                               Use Syslog for logging
-          --syslog-facility string               Facility for syslog, eg KERN,USER,... (default "DAEMON")
-          --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)
-          --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 (default "hash")
-          --transfers int                        Number of file transfers to run in parallel. (default 4)
-      -u, --update                               Skip files that are newer on the destination.
-          --use-cookies                          Enable session cookiejar.
-          --use-json-log                         Use json log format.
-          --use-mmap                             Use mmap allocator (see docs).
-          --use-server-modtime                   Use server modified time instead of object metadata
-          --user-agent string                    Set the user-agent to a specified string. The default is rclone/ version (default "rclone/v1.52.0")
-      -v, --verbose count                        Print lots more stuff (repeat for more)
-
-
-Backend Flags
-
-These flags are available for every command. They control the backends
-and may be set in the config file.
-
-          --acd-auth-url string                                      Auth server URL.
-          --acd-client-id string                                     Amazon Application Client ID.
-          --acd-client-secret string                                 Amazon Application Client Secret.
-          --acd-encoding MultiEncoder                                This sets the encoding for the backend. (default Slash,InvalidUtf8,Dot)
-          --acd-templink-threshold SizeSuffix                        Files >= this size will be downloaded via their tempLink. (default 9G)
-          --acd-token-url string                                     Token server url.
-          --acd-upload-wait-per-gb Duration                          Additional time per GB to wait after a failed complete upload to see if it appears. (default 3m0s)
-          --alias-remote string                                      Remote or path to alias.
-          --azureblob-access-tier string                             Access tier of blob: hot, cool or archive.
-          --azureblob-account string                                 Storage Account Name (leave blank to use SAS URL or Emulator)
-          --azureblob-chunk-size SizeSuffix                          Upload chunk size (<= 100MB). (default 4M)
-          --azureblob-disable-checksum                               Don't store MD5 checksum with object metadata.
-          --azureblob-encoding MultiEncoder                          This sets the encoding for the backend. (default Slash,BackSlash,Del,Ctl,RightPeriod,InvalidUtf8)
-          --azureblob-endpoint string                                Endpoint for the service
-          --azureblob-key string                                     Storage Account Key (leave blank to use SAS URL or Emulator)
-          --azureblob-list-chunk int                                 Size of blob list. (default 5000)
-          --azureblob-memory-pool-flush-time Duration                How often internal memory buffer pools will be flushed. (default 1m0s)
-          --azureblob-memory-pool-use-mmap                           Whether to use mmap buffers in internal memory pool.
-          --azureblob-sas-url string                                 SAS URL for container level access only
-          --azureblob-upload-cutoff SizeSuffix                       Cutoff for switching to chunked upload (<= 256MB). (default 256M)
-          --azureblob-use-emulator                                   Uses local storage emulator if provided as 'true' (leave blank if using real azure storage endpoint)
-          --b2-account string                                        Account ID or Application Key ID
-          --b2-chunk-size SizeSuffix                                 Upload chunk size. Must fit in memory. (default 96M)
-          --b2-disable-checksum                                      Disable checksums for large (> upload cutoff) files
-          --b2-download-auth-duration Duration                       Time before the 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 MultiEncoder                                 This sets 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-test-mode string                                      A flag string for X-Bz-Test-Mode header for debugging.
-          --b2-upload-cutoff SizeSuffix                              Cutoff for switching to chunked upload. (default 200M)
-          --b2-versions                                              Include old versions in directory listings.
-          --box-box-config-file string                               Box App config.json location
-          --box-box-sub-type string                                   (default "user")
-          --box-client-id string                                     Box App Client Id.
-          --box-client-secret string                                 Box App Client Secret
-          --box-commit-retries int                                   Max number of times to try committing a multipart file. (default 100)
-          --box-encoding MultiEncoder                                This sets the encoding for the backend. (default Slash,BackSlash,Del,Ctl,RightSpace,InvalidUtf8,Dot)
-          --box-root-folder-id string                                Fill in for rclone to use a non root folder as its starting point.
-          --box-upload-cutoff SizeSuffix                             Cutoff for switching to multipart upload (>= 50MB). (default 50M)
-          --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 "$HOME/.cache/rclone/cache-backend")
-          --cache-chunk-size SizeSuffix                              The size of a chunk (partial file data). (default 5M)
-          --cache-chunk-total-size SizeSuffix                        The total size that the chunks can take up on the local disk. (default 10G)
-          --cache-db-path string                                     Directory to store file structure metadata DB. (default "$HOME/.cache/rclone/cache-backend")
-          --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-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
-          --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 2G)
-          --chunker-fail-hard                                        Choose how chunker should handle files with missing or invalid chunks.
-          --chunker-hash-type string                                 Choose how chunker handles hash sums. All modes but "none" require metadata. (default "md5")
-          --chunker-meta-format string                               Format of the metadata object or "none". By default "simplejson". (default "simplejson")
-          --chunker-name-format string                               String format of chunk file names. (default "*.rclone_chunk.###")
-          --chunker-remote string                                    Remote to chunk/unchunk.
-          --chunker-start-from int                                   Minimum valid chunk number. Usually 0 or 1. (default 1)
-      -L, --copy-links                                               Follow symlinks and copy the pointed to item.
-          --crypt-directory-name-encryption                          Option to either encrypt directory names or leave them intact. (default true)
-          --crypt-filename-encryption string                         How to encrypt the filenames. (default "standard")
-          --crypt-password string                                    Password or pass phrase for encryption.
-          --crypt-password2 string                                   Password or pass phrase for salt. Optional but recommended.
-          --crypt-remote string                                      Remote to encrypt/decrypt.
-          --crypt-show-mapping                                       For all files listed show how the names encrypt.
-          --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 (e.g. file.doc to file.docx). This will confuse sync and reupload every time.
-          --drive-alternate-export                                   Use alternate export URLs for google documents export.,
-          --drive-auth-owner-only                                    Only consider files owned by the authenticated user.
-          --drive-chunk-size SizeSuffix                              Upload chunk size. Must a power of 2 >= 256k. (default 8M)
-          --drive-client-id string                                   Google Application Client Id
-          --drive-client-secret string                               Google Application Client Secret
-          --drive-disable-http2                                      Disable drive using http2 (default true)
-          --drive-encoding MultiEncoder                              This sets the encoding for the backend. (default InvalidUtf8)
-          --drive-export-formats string                              Comma separated list of preferred formats for downloading Google docs. (default "docx,xlsx,pptx,svg")
-          --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-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-root-folder-id string                              ID of the root folder
-          --drive-scope string                                       Scope that rclone should use when requesting access from drive.
-          --drive-server-side-across-configs                         Allow server side operations (eg copy) to work across different drive configs.
-          --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-size-as-quota                                      Show sizes as storage quota usage, not actual size.
-          --drive-skip-checksum-gphotos                              Skip MD5 checksum on Google photos and videos only.
-          --drive-skip-gdocs                                         Skip google documents in all listings.
-          --drive-skip-shortcuts                                     If set skip shortcut files
-          --drive-stop-on-upload-limit                               Make upload limit errors be fatal
-          --drive-team-drive string                                  ID of the Team Drive
-          --drive-trashed-only                                       Only show files that are in the trash.
-          --drive-upload-cutoff SizeSuffix                           Cutoff for switching to chunked upload (default 8M)
-          --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's are greater, use drive v2 API to download. (default off)
-          --dropbox-chunk-size SizeSuffix                            Upload chunk size. (< 150M). (default 48M)
-          --dropbox-client-id string                                 Dropbox App Client Id
-          --dropbox-client-secret string                             Dropbox App Client Secret
-          --dropbox-encoding MultiEncoder                            This sets the encoding for the backend. (default Slash,BackSlash,Del,RightSpace,InvalidUtf8,Dot)
-          --dropbox-impersonate string                               Impersonate this user when using a business account.
-          --fichier-api-key string                                   Your API Key, get it from https://1fichier.com/console/params.pl
-          --fichier-encoding MultiEncoder                            This sets the encoding for the backend. (default Slash,LtGt,DoubleQuote,SingleQuote,BackQuote,Dollar,BackSlash,Del,Ctl,LeftSpace,RightSpace,InvalidUtf8,Dot)
-          --fichier-shared-folder string                             If you want to download a shared folder, add this parameter
-          --ftp-concurrency int                                      Maximum number of FTP simultaneous connections, 0 for unlimited
-          --ftp-disable-epsv                                         Disable using EPSV even if server advertises support
-          --ftp-encoding MultiEncoder                                This sets the encoding for the backend. (default Slash,Del,Ctl,RightSpace,Dot)
-          --ftp-host string                                          FTP host to connect to
-          --ftp-no-check-certificate                                 Do not verify the TLS certificate of the server
-          --ftp-pass string                                          FTP password
-          --ftp-port string                                          FTP port, leave blank to use default (21)
-          --ftp-tls                                                  Use FTP over TLS (Implicit)
-          --ftp-user string                                          FTP username, leave blank for current username, $USER
-          --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                                     Google Application Client Id
-          --gcs-client-secret string                                 Google Application Client Secret
-          --gcs-encoding MultiEncoder                                This sets the encoding for the backend. (default Slash,CrLf,InvalidUtf8,Dot)
-          --gcs-location string                                      Location for the newly created buckets.
-          --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.
-          --gphotos-client-id string                                 Google Application Client Id
-          --gphotos-client-secret string                             Google Application Client Secret
-          --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)
-          --http-headers CommaSepList                                Set HTTP headers for all transactions
-          --http-no-head                                             Don't use HEAD requests to find file sizes in dir listing
-          --http-no-slash                                            Set this if the site doesn't end directories with /
-          --http-url string                                          URL of http host to connect to
-          --hubic-chunk-size SizeSuffix                              Above this size files will be chunked into a _segments container. (default 5G)
-          --hubic-client-id string                                   Hubic Client Id
-          --hubic-client-secret string                               Hubic Client Secret
-          --hubic-encoding MultiEncoder                              This sets the encoding for the backend. (default Slash,InvalidUtf8)
-          --hubic-no-chunk                                           Don't chunk files during streaming upload.
-          --jottacloud-encoding MultiEncoder                         This sets 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 10M)
-          --jottacloud-trashed-only                                  Only show files that are in the trash.
-          --jottacloud-unlink                                        Remove existing public link to file/folder with link command rather than creating.
-          --jottacloud-upload-resume-limit SizeSuffix                Files bigger than this can be resumed if the upload fail's. (default 10M)
-          --koofr-encoding MultiEncoder                              This sets the encoding for the backend. (default Slash,BackSlash,Del,Ctl,InvalidUtf8,Dot)
-          --koofr-endpoint string                                    The Koofr API endpoint to use (default "https://app.koofr.net")
-          --koofr-mountid string                                     Mount ID of the mount to use. If omitted, the primary mount is used.
-          --koofr-password string                                    Your Koofr password for rclone (generate one at https://app.koofr.net/app/admin/preferences/password)
-          --koofr-setmtime                                           Does the backend support setting modification time. Set this to false if you use a mount ID that points to a Dropbox or Amazon Drive backend. (default true)
-          --koofr-user string                                        Your Koofr user name
-      -l, --links                                                    Translate symlinks to/from regular files with a '.rclonelink' 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-encoding MultiEncoder                              This sets the encoding for the backend. (default Slash,Dot)
-          --local-no-check-updated                                   Don't check to see if the files change during upload
-          --local-no-sparse                                          Disable sparse files for multi-thread downloads
-          --local-no-unicode-normalization                           Don't apply unicode normalization to paths and filenames (Deprecated)
-          --local-nounc string                                       Disable UNC (long path names) conversion on Windows
-          --mailru-check-hash                                        What should copy do if file checksum is mismatched or invalid (default true)
-          --mailru-encoding MultiEncoder                             This sets the encoding for the backend. (default Slash,LtGt,DoubleQuote,Colon,Question,Asterisk,Pipe,BackSlash,Del,Ctl,InvalidUtf8,Dot)
-          --mailru-pass string                                       Password
-          --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 "*.mkv,*.avi,*.mp4,*.mp3,*.zip,*.gz,*.rar,*.pdf")
-          --mailru-speedup-max-disk SizeSuffix                       This option allows you to disable speedup (put by hash) for large files (default 3G)
-          --mailru-speedup-max-memory SizeSuffix                     Files larger than the size given below will always be hashed on disk. (default 32M)
-          --mailru-user string                                       User name (usually email)
-          --mega-debug                                               Output more debug from Mega.
-          --mega-encoding MultiEncoder                               This sets 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.
-          --mega-user string                                         User name
-      -x, --one-file-system                                          Don't cross filesystem boundaries (unix/macOS only).
-          --onedrive-chunk-size SizeSuffix                           Chunk size to upload files with - must be multiple of 320k (327,680 bytes). (default 10M)
-          --onedrive-client-id string                                Microsoft App Client Id
-          --onedrive-client-secret string                            Microsoft App Client Secret
-          --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 MultiEncoder                           This sets the encoding for the backend. (default Slash,LtGt,DoubleQuote,Colon,Question,Asterisk,Pipe,Hash,Percent,BackSlash,Del,Ctl,LeftSpace,LeftTilde,RightSpace,RightPeriod,InvalidUtf8,Dot)
-          --onedrive-expose-onenote-files                            Set to make OneNote files show up in directory listings.
-          --onedrive-server-side-across-configs                      Allow server side operations (eg copy) to work across different onedrive configs.
-          --opendrive-chunk-size SizeSuffix                          Files will be uploaded in chunks this size. (default 10M)
-          --opendrive-encoding MultiEncoder                          This sets the encoding for the backend. (default Slash,LtGt,DoubleQuote,Colon,Question,Asterisk,Pipe,BackSlash,LeftSpace,LeftCrLfHtVt,RightSpace,RightCrLfHtVt,InvalidUtf8,Dot)
-          --opendrive-password string                                Password.
-          --opendrive-username string                                Username
-          --pcloud-client-id string                                  Pcloud App Client Id
-          --pcloud-client-secret string                              Pcloud App Client Secret
-          --pcloud-encoding MultiEncoder                             This sets the encoding for the backend. (default Slash,BackSlash,Del,Ctl,InvalidUtf8,Dot)
-          --pcloud-root-folder-id string                             Fill in for rclone to use a non root folder as its starting point. (default "d0")
-          --premiumizeme-encoding MultiEncoder                       This sets the encoding for the backend. (default Slash,DoubleQuote,BackSlash,Del,Ctl,InvalidUtf8,Dot)
-          --putio-encoding MultiEncoder                              This sets the encoding for the backend. (default Slash,BackSlash,Del,Ctl,InvalidUtf8,Dot)
-          --qingstor-access-key-id string                            QingStor Access Key ID
-          --qingstor-chunk-size SizeSuffix                           Chunk size to use for uploading. (default 4M)
-          --qingstor-connection-retries int                          Number of connection retries. (default 3)
-          --qingstor-encoding MultiEncoder                           This sets 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. Only applies if access_key_id and secret_access_key is blank.
-          --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 200M)
-          --qingstor-zone string                                     Zone to connect to.
-          --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 5M)
-          --s3-copy-cutoff SizeSuffix                                Cutoff for switching to multipart copy (default 5G)
-          --s3-disable-checksum                                      Don't store MD5 checksum with object metadata
-          --s3-encoding MultiEncoder                                 This sets 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-location-constraint string                            Location constraint - must be set to match the Region.
-          --s3-memory-pool-flush-time Duration                       How often internal memory buffer pools will be flushed. (default 1m0s)
-          --s3-memory-pool-use-mmap                                  Whether to use mmap buffers in internal memory pool.
-          --s3-provider string                                       Choose your S3 provider.
-          --s3-region string                                         Region to connect to.
-          --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-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                               If using SSE-C you must provide the secret encryption key used to encrypt/decrypt your data.
-          --s3-sse-customer-key-md5 string                           If using SSE-C you must provide the secret encryption key MD5 checksum.
-          --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. (default 4)
-          --s3-upload-cutoff SizeSuffix                              Cutoff for switching to chunked upload (default 200M)
-          --s3-use-accelerate-endpoint                               If true use the AWS S3 accelerated endpoint.
-          --s3-v2-auth                                               If true use v2 authentication.
-          --seafile-2fa                                              Two-factor authentication ('true' if the account has 2FA enabled)
-          --seafile-create-library                                   Should rclone create a library if it doesn't exist
-          --seafile-encoding MultiEncoder                            This sets the encoding for the backend. (default Slash,DoubleQuote,BackSlash,Ctl,InvalidUtf8)
-          --seafile-library string                                   Name of the library. Leave blank to access all non-encrypted libraries.
-          --seafile-library-key string                               Library password (for encrypted libraries only). Leave blank if you pass it through the command line.
-          --seafile-pass string                                      Password
-          --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-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-key-file string                                     Path to PEM-encoded private key file, leave blank or set key-use-agent to use ssh-agent.
-          --sftp-key-file-pass string                                The passphrase to decrypt the PEM-encoded private key file.
-          --sftp-key-pem string                                      Raw PEM-encoded private key, If specified, will override key_file parameter.
-          --sftp-key-use-agent                                       When set forces the usage of the ssh-agent.
-          --sftp-md5sum-command string                               The command used to read md5 hashes. Leave blank for autodetect.
-          --sftp-pass string                                         SSH password, leave blank to use ssh-agent.
-          --sftp-path-override string                                Override path used by SSH connection.
-          --sftp-port string                                         SSH port, leave blank to use default (22)
-          --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. Leave blank for autodetect.
-          --sftp-skip-links                                          Set to skip any symlinks and any other non regular files.
-          --sftp-use-insecure-cipher                                 Enable the use of insecure ciphers and key exchange methods.
-          --sftp-user string                                         SSH username, leave blank for current username, ncw
-          --sharefile-chunk-size SizeSuffix                          Upload chunk size. Must a power of 2 >= 256k. (default 64M)
-          --sharefile-encoding MultiEncoder                          This sets 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-upload-cutoff SizeSuffix                       Cutoff for switching to multipart upload. (default 128M)
-          --skip-links                                               Don't warn about skipped symlinks.
-          --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-encoding MultiEncoder                          This sets 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 into a _segments container. (default 5G)
-          --swift-domain string                                      User domain - optional (v3 auth) (OS_USER_DOMAIN_NAME)
-          --swift-encoding MultiEncoder                              This sets the encoding for the backend. (default Slash,InvalidUtf8)
-          --swift-endpoint-type string                               Endpoint type to choose from the service catalogue (OS_ENDPOINT_TYPE) (default "public")
-          --swift-env-auth                                           Get swift credentials from environment variables in standard OpenStack form.
-          --swift-key string                                         API key or password (OS_PASSWORD).
-          --swift-no-chunk                                           Don't chunk files during streaming upload.
-          --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-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).
-          --tardigrade-access-grant string                           Access Grant.
-          --tardigrade-api-key string                                API Key.
-          --tardigrade-passphrase string                             Encryption Passphrase. To access existing objects enter passphrase used for uploading.
-          --tardigrade-provider string                               Choose an authentication method. (default "existing")
-          --tardigrade-satellite-address <nodeid>@<address>:<port>   Satellite Address. Custom satellite address should match the format: <nodeid>@<address>:<port>. (default "us-central-1.tardigrade.io")
-          --union-action-policy string                               Policy to choose upstream on ACTION category. (default "epall")
-          --union-cache-time int                                     Cache time of usage and free space (in seconds). This option is only useful when a path preserving policy is used. (default 120)
-          --union-create-policy string                               Policy to choose upstream on CREATE category. (default "epmfs")
-          --union-search-policy string                               Policy to choose upstream on SEARCH category. (default "ff")
-          --union-upstreams string                                   List of space separated upstreams.
-          --webdav-bearer-token string                               Bearer token instead of user/pass (eg a Macaroon)
-          --webdav-bearer-token-command string                       Command to run to get a bearer token
-          --webdav-pass string                                       Password.
-          --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-client-id string                                  Yandex Client Id
-          --yandex-client-secret string                              Yandex Client Secret
-          --yandex-encoding MultiEncoder                             This sets the encoding for the backend. (default Slash,Del,Ctl,InvalidUtf8,Dot)
-          --yandex-unlink                                            Remove existing public link to file/folder with link command rather than creating.
-
-
-1Fichier
-
-This is a backend for the 1fichier cloud storage service. Note that a
-Premium subscription is required to use the API.
-
-Paths are specified as remote:path
-
-Paths may be as deep as required, eg remote:directory/subdirectory.
-
-The initial setup for 1Fichier involves getting the API key from the
-website which you need to do in your browser.
-
-Here is an example of how to make a remote called remote. First run:
-
-     rclone config
-
-This will guide you through an interactive setup process:
-
-    No remotes found - make a new one
-    n) New remote
-    s) Set configuration password
-    q) Quit config
-    n/s/q> n
-    name> remote
-    Type of storage to configure.
-    Enter a string value. Press Enter for the default ("").
-    Choose a number from below, or type in your own value
-    [snip]
-    XX / 1Fichier
-       \ "fichier"
-    [snip]
-    Storage> fichier
-    ** See help for fichier backend at: https://rclone.org/fichier/ **
+    Results
+
+    - previousRate - int
+
+    ### job/list: Lists the IDs of the running jobs {#job-list}
+
+    Parameters - None
+
+    Results
+
+    - jobids - array of integer job ids
+
+    ### job/status: Reads the status of the job ID {#job-status}
+
+    Parameters
+
+    - jobid - id of the job (integer)
+
+    Results
+
+    - finished - boolean
+    - duration - time in seconds that the job ran for
+    - endTime - time the job finished (eg "2018-10-26T18:50:20.528746884+01:00")
+    - error - error from the job or empty string for no error
+    - finished - boolean whether the job has finished or not
+    - id - as passed in above
+    - startTime - time the job started (eg "2018-10-26T18:50:20.528336039+01:00")
+    - success - boolean - true for success false otherwise
+    - output - output of the job as would have been returned if called synchronously
+    - progress - output of the progress related to the underlying job
+
+    ### job/stop: Stop the running job {#job-stop}
+
+    Parameters
+
+    - jobid - id of the job (integer)
+
+    ### mount/listmounts: Show current mount points {#mount-listmounts}
+
+    This shows currently mounted points, which can be used for performing an unmount
+
+    This takes no parameters and returns
+
+    - mountPoints: list of current mount points
+
+    Eg
+
+        rclone rc mount/listmounts
+
+    **Authentication is required for this call.**
+
+    ### mount/mount: Create a new mount point {#mount-mount}
+
+    rclone allows Linux, FreeBSD, macOS and Windows to mount any of
+    Rclone's cloud storage systems as a file system with FUSE.
+
+    If no mountType is provided, the priority is given as follows: 1. mount 2.cmount 3.mount2
+
+    This takes the following parameters
+
+    - fs - a remote path to be mounted (required)
+    - mountPoint: valid path on the local machine (required)
+    - mountType: One of the values (mount, cmount, mount2) specifies the mount implementation to use
+    - mountOpt: a JSON object with Mount options in.
+    - vfsOpt: a JSON object with VFS options in.
+
+    Eg
+
+        rclone rc mount/mount fs=mydrive: mountPoint=/home/<user>/mountPoint
+        rclone rc mount/mount fs=mydrive: mountPoint=/home/<user>/mountPoint mountType=mount
+        rclone rc mount/mount fs=TestDrive: mountPoint=/mnt/tmp vfsOpt='{"CacheMode": 2}' mountOpt='{"AllowOther": true}'
+
+    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.
+
+        rclone rc options/get
+
+    **Authentication is required for this call.**
+
+    ### mount/types: Show all possible mount types {#mount-types}
+
+    This shows all possible mount types and returns them as a list.
+
+    This takes no parameters and returns
+
+    - mountTypes: list of mount types
+
+    The mount types are strings like "mount", "mount2", "cmount" and can
+    be passed to mount/mount as the mountType parameter.
+
+    Eg
+
+        rclone rc mount/types
+
+    **Authentication is required for this call.**
+
+    ### mount/unmount: Unmount selected active mount {#mount-unmount}
+
+    rclone allows Linux, FreeBSD, macOS and Windows to
+    mount any of Rclone's cloud storage systems as a file system with
+    FUSE.
+
+    This takes the following parameters
+
+    - mountPoint: valid path on the local machine where the mount was created (required)
+
+    Eg
+
+        rclone rc mount/unmount mountPoint=/home/<user>/mountPoint
+
+    **Authentication is required for this call.**
+
+    ### mount/unmountall: Show current mount points {#mount-unmountall}
+
+    This shows currently mounted points, which can be used for performing an unmount
+
+    This takes no parameters and returns error if unmount does not succeed.
+
+    Eg
+
+        rclone rc mount/unmountall
+
+    **Authentication is required for this call.**
+
+    ### operations/about: Return the space used on the remote {#operations-about}
+
+    This takes the following parameters
+
+    - fs - a remote name string eg "drive:"
+
+    The result is as returned from rclone about --json
+
+    See the [about command](https://rclone.org/commands/rclone_size/) command for more information on the above.
+
+    **Authentication is required for this call.**
+
+    ### operations/cleanup: Remove trashed files in the remote or path {#operations-cleanup}
+
+    This takes the following parameters
+
+    - fs - a remote name string eg "drive:"
+
+    See the [cleanup command](https://rclone.org/commands/rclone_cleanup/) command for more information on the above.
+
+    **Authentication is required for this call.**
+
+    ### operations/copyfile: Copy a file from source remote to destination remote {#operations-copyfile}
+
+    This takes the following parameters
+
+    - srcFs - a remote name string eg "drive:" for the source
+    - srcRemote - a path within that remote eg "file.txt" for the source
+    - dstFs - a remote name string eg "drive2:" for the destination
+    - dstRemote - a path within that remote eg "file2.txt" for the destination
+
+    **Authentication is required for this call.**
+
+    ### operations/copyurl: Copy the URL to the object {#operations-copyurl}
+
+    This takes the following parameters
+
+    - fs - a remote name string eg "drive:"
+    - remote - a path within that remote eg "dir"
+    - url - string, URL to read from
+     - autoFilename - boolean, set to true to retrieve destination file name from url
+    See the [copyurl command](https://rclone.org/commands/rclone_copyurl/) command for more information on the above.
+
+    **Authentication is required for this call.**
+
+    ### operations/delete: Remove files in the path {#operations-delete}
+
+    This takes the following parameters
+
+    - fs - a remote name string eg "drive:"
+
+    See the [delete command](https://rclone.org/commands/rclone_delete/) command for more information on the above.
+
+    **Authentication is required for this call.**
+
+    ### operations/deletefile: Remove the single file pointed to {#operations-deletefile}
+
+    This takes the following parameters
+
+    - fs - a remote name string eg "drive:"
+    - remote - a path within that remote eg "dir"
+
+    See the [deletefile command](https://rclone.org/commands/rclone_deletefile/) command for more information on the above.
+
+    **Authentication is required for this call.**
+
+    ### operations/fsinfo: Return information about the remote {#operations-fsinfo}
+
+    This takes the following parameters
+
+    - fs - a remote name string eg "drive:"
+
+    This returns info about the remote passed in;
+
+{ // optional features and whether they are available or not "Features":
+{ "About": true, "BucketBased": false, "CanHaveEmptyDirectories": true,
+"CaseInsensitive": false, "ChangeNotify": false, "CleanUp": false,
+"Copy": false, "DirCacheFlush": false, "DirMove": true,
+"DuplicateFiles": false, "GetTier": false, "ListR": false, "MergeDirs":
+false, "Move": true, "OpenWriterAt": true, "PublicLink": false, "Purge":
+true, "PutStream": true, "PutUnchecked": false, "ReadMimeType": false,
+"ServerSideAcrossConfigs": false, "SetTier": false, "SetWrapper": false,
+"UnWrap": false, "WrapFs": false, "WriteMimeType": false }, // Names of
+hashes available "Hashes": [ "MD5", "SHA-1", "DropboxHash",
+"QuickXorHash" ], "Name": "local", // Name as created "Precision": 1, //
+Precision of timestamps in ns "Root": "/", // Path as created "String":
+"Local file system at /" // how the remote will appear in logs }
+
+
+    This command does not have a command line equivalent so use this instead:
+
+        rclone rc --loopback operations/fsinfo fs=remote:
+
+    ### operations/list: List the given remote and path in JSON format {#operations-list}
+
+    This takes the following parameters
+
+    - fs - a remote name string eg "drive:"
+    - remote - a path within that remote eg "dir"
+    - opt - a dictionary of options to control the listing (optional)
+        - recurse - If set recurse directories
+        - noModTime - If set return modification time
+        - showEncrypted -  If set show decrypted names
+        - showOrigIDs - If set show the IDs for each item if known
+        - showHash - If set return a dictionary of hashes
+
+    The result is
+
+    - list
+        - This is an array of objects as described in the lsjson command
+
+    See the [lsjson command](https://rclone.org/commands/rclone_lsjson/) for more information on the above and examples.
+
+    **Authentication is required for this call.**
+
+    ### operations/mkdir: Make a destination directory or container {#operations-mkdir}
+
+    This takes the following parameters
+
+    - fs - a remote name string eg "drive:"
+    - remote - a path within that remote eg "dir"
+
+    See the [mkdir command](https://rclone.org/commands/rclone_mkdir/) command for more information on the above.
+
+    **Authentication is required for this call.**
+
+    ### operations/movefile: Move a file from source remote to destination remote {#operations-movefile}
+
+    This takes the following parameters
+
+    - srcFs - a remote name string eg "drive:" for the source
+    - srcRemote - a path within that remote eg "file.txt" for the source
+    - dstFs - a remote name string eg "drive2:" for the destination
+    - dstRemote - a path within that remote eg "file2.txt" for the destination
+
+    **Authentication is required for this call.**
+
+    ### operations/publiclink: Create or retrieve a public link to the given file or folder. {#operations-publiclink}
+
+    This takes the following parameters
+
+    - fs - a remote name string eg "drive:"
+    - remote - a path within that remote eg "dir"
+    - unlink - boolean - if set removes the link rather than adding it (optional)
+    - expire - string - the expiry time of the link eg "1d" (optional)
+
+    Returns
+
+    - url - URL of the resource
+
+    See the [link command](https://rclone.org/commands/rclone_link/) command for more information on the above.
+
+    **Authentication is required for this call.**
+
+    ### operations/purge: Remove a directory or container and all of its contents {#operations-purge}
+
+    This takes the following parameters
+
+    - fs - a remote name string eg "drive:"
+    - remote - a path within that remote eg "dir"
+
+    See the [purge command](https://rclone.org/commands/rclone_purge/) command for more information on the above.
+
+    **Authentication is required for this call.**
+
+    ### operations/rmdir: Remove an empty directory or container {#operations-rmdir}
+
+    This takes the following parameters
+
+    - fs - a remote name string eg "drive:"
+    - remote - a path within that remote eg "dir"
+
+    See the [rmdir command](https://rclone.org/commands/rclone_rmdir/) command for more information on the above.
+
+    **Authentication is required for this call.**
+
+    ### operations/rmdirs: Remove all the empty directories in the path {#operations-rmdirs}
+
+    This takes the following parameters
+
+    - fs - a remote name string eg "drive:"
+    - remote - a path within that remote eg "dir"
+    - leaveRoot - boolean, set to true not to delete the root
+
+    See the [rmdirs command](https://rclone.org/commands/rclone_rmdirs/) command for more information on the above.
+
+    **Authentication is required for this call.**
+
+    ### operations/size: Count the number of bytes and files in remote {#operations-size}
+
+    This takes the following parameters
+
+    - fs - a remote name string eg "drive:path/to/dir"
+
+    Returns
+
+    - count - number of files
+    - bytes - number of bytes in those files
+
+    See the [size command](https://rclone.org/commands/rclone_size/) command for more information on the above.
+
+    **Authentication is required for this call.**
+
+    ### operations/uploadfile: Upload file using multiform/form-data {#operations-uploadfile}
+
+    This takes the following parameters
+
+    - fs - a remote name string eg "drive:"
+    - remote - a path within that remote eg "dir"
+    - each part in body represents a file to be uploaded
+    See the [uploadfile command](https://rclone.org/commands/rclone_uploadfile/) command for more information on the above.
+
+    **Authentication is required for this call.**
+
+    ### options/blocks: List all the option blocks {#options-blocks}
+
+    Returns
+    - options - a list of the options block names
+
+    ### options/get: Get all the options {#options-get}
+
+    Returns an object where keys are option block names and values are an
+    object with the current option values in.
+
+    This shows the internal names of the option within rclone which should
+    map to the external options very easily with a few exceptions.
+
+    ### options/set: Set an option {#options-set}
+
+    Parameters
+
+    - option block name containing an object with
+      - key: value
+
+    Repeated as often as required.
+
+    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.
+
+    For example:
+
+    This sets DEBUG level logs (-vv)
+
+        rclone rc options/set --json '{"main": {"LogLevel": 8}}'
+
+    And this sets INFO level logs (-v)
+
+        rclone rc options/set --json '{"main": {"LogLevel": 7}}'
+
+    And this sets NOTICE level logs (normal without -v)
+
+        rclone rc options/set --json '{"main": {"LogLevel": 6}}'
+
+    ### pluginsctl/addPlugin: Add a plugin using url {#pluginsctl-addPlugin}
+
+    used for adding a plugin to the webgui
+
+    This takes the following parameters
+
+    - url: http url of the github repo where the plugin is hosted (http://github.com/rclone/rclone-webui-react)
+
+    Eg
+
+       rclone rc pluginsctl/addPlugin
+
+    **Authentication is required for this call.**
+
+    ### pluginsctl/getPluginsForType: Get plugins with type criteria {#pluginsctl-getPluginsForType}
+
+    This shows all possible plugins by a mime type
+
+    This takes the following parameters
+
+    - type: supported mime type by a loaded plugin eg (video/mp4, audio/mp3)
+    - pluginType: filter plugins based on their type eg (DASHBOARD, FILE_HANDLER, TERMINAL) 
+
+    and returns
+
+    - loadedPlugins: list of current production plugins
+    - testPlugins: list of temporarily loaded development plugins, usually running on a different server.
+
+    Eg
+
+       rclone rc pluginsctl/getPluginsForType type=video/mp4
+
+    **Authentication is required for this call.**
+
+    ### pluginsctl/listPlugins: Get the list of currently loaded plugins {#pluginsctl-listPlugins}
+
+    This allows you to get the currently enabled plugins and their details.
+
+    This takes no parameters and returns
+
+    - loadedPlugins: list of current production plugins
+    - testPlugins: list of temporarily loaded development plugins, usually running on a different server.
+
+    Eg
+
+       rclone rc pluginsctl/listPlugins
+
+    **Authentication is required for this call.**
+
+    ### pluginsctl/listTestPlugins: Show currently loaded test plugins {#pluginsctl-listTestPlugins}
+
+    allows listing of test plugins with the rclone.test set to true in package.json of the plugin
+
+    This takes no parameters and returns
+
+    - loadedTestPlugins: list of currently available test plugins
+
+    Eg
+
+        rclone rc pluginsctl/listTestPlugins
+
+    **Authentication is required for this call.**
+
+    ### pluginsctl/removePlugin: Remove a loaded plugin {#pluginsctl-removePlugin}
+
+    This allows you to remove a plugin using it's name
+
+    This takes parameters
+
+    - name: name of the plugin in the format <author>/<plugin_name>
+
+    Eg
+
+       rclone rc pluginsctl/removePlugin name=rclone/video-plugin
+
+    **Authentication is required for this call.**
+
+    ### pluginsctl/removeTestPlugin: Remove  a test plugin {#pluginsctl-removeTestPlugin}
+
+    This allows you to remove a plugin using it's name
+
+    This takes the following parameters
+
+    - name: name of the plugin in the format <author>/<plugin_name>
+
+    Eg
+
+        rclone rc pluginsctl/removeTestPlugin name=rclone/rclone-webui-react
+
+    **Authentication is required for this call.**
+
+    ### rc/error: This returns an error {#rc-error}
+
+    This returns an error with the input as part of its error string.
+    Useful for testing error handling.
+
+    ### rc/list: List all the registered remote control commands {#rc-list}
+
+    This lists all the registered remote control commands as a JSON map in
+    the commands response.
+
+    ### rc/noop: Echo the input to the output parameters {#rc-noop}
+
+    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.
+
+    ### rc/noopauth: Echo the input to the output parameters requiring auth {#rc-noopauth}
+
+    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.
+
+    **Authentication is required for this call.**
+
+    ### sync/copy: copy a directory from source remote to destination remote {#sync-copy}
+
+    This takes the following parameters
+
+    - srcFs - a remote name string eg "drive:src" for the source
+    - dstFs - a remote name string eg "drive:dst" for the destination
+
+
+    See the [copy command](https://rclone.org/commands/rclone_copy/) command for more information on the above.
+
+    **Authentication is required for this call.**
+
+    ### sync/move: move a directory from source remote to destination remote {#sync-move}
+
+    This takes the following parameters
+
+    - srcFs - a remote name string eg "drive:src" for the source
+    - dstFs - a remote name string eg "drive:dst" for the destination
+    - deleteEmptySrcDirs - delete empty src directories if set
+
+
+    See the [move command](https://rclone.org/commands/rclone_move/) command for more information on the above.
+
+    **Authentication is required for this call.**
+
+    ### sync/sync: sync a directory from source remote to destination remote {#sync-sync}
+
+    This takes the following parameters
+
+    - srcFs - a remote name string eg "drive:src" for the source
+    - dstFs - a remote name string eg "drive:dst" for the destination
+
+
+    See the [sync command](https://rclone.org/commands/rclone_sync/) command for more information on the above.
+
+    **Authentication is required for this call.**
+
+    ### vfs/forget: Forget files or directories in the directory cache. {#vfs-forget}
+
+    This forgets the paths in the directory cache causing them to be
+    re-read from the remote when needed.
+
+    If no paths are passed in then it will forget all the paths in the
+    directory cache.
+
+        rclone rc vfs/forget
+
+    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, eg
+
+        rclone rc vfs/forget file=hello file2=goodbye dir=home/junk
+     
+    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.
+
+    ### vfs/list: List active VFSes. {#vfs-list}
+
+    This lists the active VFSes.
+
+    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.
+
+    ### vfs/poll-interval: Get the status or update the value of the poll-interval option. {#vfs-poll-interval}
+
+    Without any parameter given this returns the current status of the
+    poll-interval setting.
+
+    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.
+
+        rclone rc vfs/poll-interval interval=5m
+
+    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.
+
+    The new poll-interval value will only be active when the timeout is
+    not reached.
+
+    If poll-interval is updated or disabled temporarily, some changes
+    might not get picked up by the polling function, depending on the
+    used remote.
+     
+    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.
+
+    ### vfs/refresh: Refresh the directory cache. {#vfs-refresh}
+
+    This reads the directories for the specified paths and freshens the
+    directory cache.
+
+    If no paths are passed in then it will refresh the root directory.
+
+        rclone rc vfs/refresh
+
+    Otherwise pass directories in as dir=path. Any parameter key
+    starting with dir will refresh that directory, eg
+
+        rclone rc vfs/refresh dir=home/junk dir2=data/misc
+
+    If the parameter recursive=true is given the whole directory tree
+    will get refreshed. This refresh will use --fast-list if enabled.
+     
+    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.
+
+
+
+    ## Accessing the remote control via HTTP
+
+    Rclone implements a simple HTTP based protocol.
+
+    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.
+
+    All calls must made using POST.
+
+    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 `curl`.
+
+    The response will be a JSON blob in the body of the response.  This is
+    formatted to be reasonably human readable.
+
+    ### Error returns
+
+    If an error occurs then there will be an HTTP error status (eg 500)
+    and the body of the response will contain a JSON encoded error object,
+    eg
+
+{ "error": "Expecting string value for key "remote" (was float64)",
+"input": { "fs": "/tmp", "remote": 3 }, "status": 400 "path":
+"operations/rmdir", }
+
+
+    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
+
+    ### CORS
+
+    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.
+
+    ### Using POST with URL parameters only
+
+curl -X POST 'http://localhost:5572/rc/noop?potato=1&sausage=2'
+
+
+    Response
+
+{ "potato": "1", "sausage": "2" }
+
+
+    Here is what an error response looks like:
+
+curl -X POST 'http://localhost:5572/rc/error?potato=1&sausage=2'
+
+{ "error": "arbitrary error on input map[potato:1 sausage:2]", "input":
+{ "potato": "1", "sausage": "2" } }
+
+
+    Note that curl doesn't return errors to the shell unless you use the `-f` option
+
+$ curl -f -X POST 'http://localhost:5572/rc/error?potato=1&sausage=2'
+curl: (22) The requested URL returned error: 400 Bad Request $ echo $?
+22
+
+
+    ### Using POST with a form
+
+curl --data "potato=1" --data "sausage=2" http://localhost:5572/rc/noop
+
+
+    Response
+
+{ "potato": "1", "sausage": "2" }
+
+
+    Note that you can combine these with URL parameters too with the POST
+    parameters taking precedence.
+
+curl --data "potato=1" --data "sausage=2"
+"http://localhost:5572/rc/noop?rutabaga=3&sausage=4"
+
+
+    Response
+
+{ "potato": "1", "rutabaga": "3", "sausage": "4" }
+
+
+    ### Using POST with a JSON blob
+
+curl -H "Content-Type: application/json" -X POST -d
+'{"potato":2,"sausage":1}' http://localhost:5572/rc/noop
+
+
+    response
+
+{ "password": "xyz", "username": "xyz" }
+
+
+    This can be combined with URL parameters too if required.  The JSON
+    blob takes precedence.
+
+curl -H "Content-Type: application/json" -X POST -d
+'{"potato":2,"sausage":1}'
+'http://localhost:5572/rc/noop?rutabaga=3&potato=4'
+
+{ "potato": 2, "rutabaga": "3", "sausage": 1 }
+
+
+    ## Debugging rclone with pprof ##
+
+    If you use the `--rc` flag this will also enable the use of the go
+    profiling tools on the same port.
+
+    To use these, first [install go](https://golang.org/doc/install).
+
+    ### Debugging memory use
+
+    To profile rclone's memory use you can run:
+
+        go tool pprof -web http://localhost:5572/debug/pprof/heap
+
+    This should open a page in your browser showing what is using what
+    memory.
+
+    You can also use the `-text` flag to produce a textual summary
+
+$ 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
+
+
+    ### Debugging go routine leaks
+
+    Memory leaks are most often caused by go routine leaks keeping memory
+    alive which should have been garbage collected.
+
+    See all active go routines using
+
+        curl http://localhost:5572/debug/pprof/goroutine?debug=1
+
+    Or go to http://localhost:5572/debug/pprof/goroutine?debug=1 in your browser.
+
+    ### Other profiles to look at
+
+    You can see a summary of profiles available at http://localhost:5572/debug/pprof/
+
+    Here is how to use some of them:
+
+    - Memory: `go tool pprof http://localhost:5572/debug/pprof/heap`
+    - Go routines: `curl http://localhost:5572/debug/pprof/goroutine?debug=1`
+    - 30-second CPU profile: `go tool pprof http://localhost:5572/debug/pprof/profile`
+    - 5-second execution trace: `wget http://localhost:5572/debug/pprof/trace?seconds=5`
+    - Goroutine blocking profile
+        - Enable first with: `rclone rc debug/set-block-profile-rate rate=1` ([docs](#debug/set-block-profile-rate))
+        - `go tool pprof http://localhost:5572/debug/pprof/block`
+    - Contended mutexes:
+        - Enable first with: `rclone rc debug/set-mutex-profile-fraction rate=1` ([docs](#debug/set-mutex-profile-fraction))
+        - `go tool pprof http://localhost:5572/debug/pprof/mutex`
+
+    See the [net/http/pprof docs](https://golang.org/pkg/net/http/pprof/)
+    for more info on how to use the profiling and for a general overview
+    see [the Go team's blog post on profiling go programs](https://blog.golang.org/profiling-go-programs).
+
+    The profiling hook is [zero overhead unless it is used](https://stackoverflow.com/q/26545159/164234).
+
+    # Overview of cloud storage systems #
+
+    Each cloud storage system is slightly different.  Rclone attempts to
+    provide a unified interface to them, but some underlying differences
+    show through.
+
+    ## Features ##
+
+    Here is an overview of the major features of each cloud storage system.
+
+    | Name                         | Hash        | ModTime | Case Insensitive | Duplicate Files | MIME Type |
+    | ---------------------------- |:-----------:|:-------:|:----------------:|:---------------:|:---------:|
+    | 1Fichier                     | Whirlpool   | No      | No               | Yes             | R         |
+    | Amazon Drive                 | MD5         | No      | Yes              | No              | R         |
+    | Amazon S3                    | MD5         | Yes     | No               | No              | R/W       |
+    | Backblaze B2                 | SHA1        | Yes     | No               | No              | R/W       |
+    | Box                          | SHA1        | Yes     | Yes              | No              | -         |
+    | Citrix ShareFile             | MD5         | Yes     | Yes              | No              | -         |
+    | Dropbox                      | DBHASH †    | Yes     | Yes              | No              | -         |
+    | FTP                          | -           | No      | No               | No              | -         |
+    | Google Cloud Storage         | MD5         | Yes     | No               | No              | R/W       |
+    | Google Drive                 | MD5         | Yes     | No               | Yes             | R/W       |
+    | Google Photos                | -           | No      | No               | Yes             | R         |
+    | HTTP                         | -           | No      | No               | No              | R         |
+    | Hubic                        | MD5         | Yes     | No               | No              | R/W       |
+    | Jottacloud                   | MD5         | Yes     | Yes              | No              | R/W       |
+    | Koofr                        | MD5         | No      | Yes              | No              | -         |
+    | Mail.ru Cloud                | Mailru ‡‡‡  | Yes     | Yes              | No              | -         |
+    | Mega                         | -           | No      | No               | Yes             | -         |
+    | Memory                       | MD5         | Yes     | No               | No              | -         |
+    | Microsoft Azure Blob Storage | MD5         | Yes     | No               | No              | R/W       |
+    | Microsoft OneDrive           | SHA1 ‡‡     | Yes     | Yes              | No              | R         |
+    | OpenDrive                    | MD5         | Yes     | Yes              | Partial \*      | -         |
+    | OpenStack Swift              | MD5         | Yes     | No               | No              | R/W       |
+    | pCloud                       | MD5, SHA1   | Yes     | No               | No              | W         |
+    | premiumize.me                | -           | No      | Yes              | No              | R         |
+    | put.io                       | CRC-32      | Yes     | No               | Yes             | R         |
+    | QingStor                     | MD5         | No      | No               | No              | R/W       |
+    | Seafile                      | -           | No      | No               | No              | -         |
+    | SFTP                         | MD5, SHA1 ‡ | Yes     | Depends          | No              | -         |
+    | SugarSync                    | -           | No      | No               | No              | -         |
+    | Tardigrade                   | -           | Yes     | No               | No              | -         |
+    | WebDAV                       | MD5, SHA1 ††| Yes ††† | Depends          | No              | -         |
+    | Yandex Disk                  | MD5         | Yes     | No               | No              | R/W       |
+    | The local filesystem         | All         | Yes     | Depends          | No              | -         |
+
+    ### Hash ###
+
+    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 `--checksum` flag in syncs and in
+    the `check` command.
+
+    To use the verify checksums when transferring between cloud storage
+    systems they must support a common hash type.
+
+    † Note that Dropbox supports [its own custom
+    hash](https://www.dropbox.com/developers/reference/content-hash).
+    This is an SHA256 sum of all the 4MB block SHA256s.
+
+    ‡ SFTP supports checksums if the same login has shell access and `md5sum`
+    or `sha1sum` as well as `echo` are in the remote's PATH.
+
+    †† WebDAV supports hashes when used with Owncloud and Nextcloud only.
+
+    ††† WebDAV supports modtimes when used with Owncloud and Nextcloud only.
+
+    ‡‡ Microsoft OneDrive Personal supports SHA1 hashes, whereas OneDrive
+    for business and SharePoint server support Microsoft's own
+    [QuickXorHash](https://docs.microsoft.com/en-us/onedrive/developer/code-snippets/quickxorhash).
+
+    ‡‡‡ Mail.ru uses its own modified SHA1 hash
+
+    ### ModTime ###
+
+    The cloud storage system supports setting modification times on
+    objects.  If it does then this enables a using the modification times
+    as part of the sync.  If not then only the size will be checked by
+    default, though the MD5SUM can be checked with the `--checksum` flag.
+
+    All cloud storage systems support some kind of date on the object and
+    these will be set when transferring from the cloud storage system.
+
+    ### Case Insensitive ###
+
+    If a cloud storage systems is case sensitive then it is possible to
+    have two files which differ only in case, eg `file.txt` and
+    `FILE.txt`.  If a cloud storage system is case insensitive then that
+    isn't possible.
+
+    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.
+
+    The local filesystem and SFTP may or may not be case sensitive
+    depending on OS.
+
+      * Windows - usually case insensitive, though case is preserved
+      * OSX - usually case insensitive, though it is possible to format case sensitive
+      * Linux - usually case sensitive, but there are case insensitive file systems (eg FAT formatted USB keys)
+
+    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.
+
+    ### Duplicate files ###
+
+    If a cloud storage system allows duplicate files then it can have two
+    objects with the same name.
+
+    This confuses rclone greatly when syncing - use the `rclone dedupe`
+    command to rename or remove duplicates.
+
+    \* 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 `rclone`.  It may be that this is a
+    mistake or an unsupported feature.
+
+    ### Restricted filenames ###
+
+    Some cloud storage systems might have restrictions on the characters
+    that are usable in file or directory names.
+    When `rclone` detects such a name during a file upload, it will
+    transparently replace the restricted characters with similar looking
+    Unicode characters.
+
+    This process is designed to avoid ambiguous file names as much as
+    possible and allow to move files between many cloud storage systems
+    transparently.
+
+    The name shown by `rclone` to the user or during log output will only
+    contain a minimal set of [replaced characters](#restricted-characters)
+    to ensure correct formatting and not necessarily the actual name used
+    on the cloud storage.
+
+    This transformation is reversed when downloading a file or parsing
+    `rclone` arguments.
+    For example, when uploading a file named `my file?.txt` to Onedrive
+    will be displayed as `my file?.txt` on the console, but stored as
+    `my file？.txt` (the `?` gets replaced by the similar looking `？`
+    character) to Onedrive.
+    The reverse transformation allows to read a file`unusual/name.txt`
+    from Google Drive, by passing the name `unusual／name.txt` (the `/` needs
+    to be replaced by the similar looking `／` character) on the command line.
+
+    #### Default restricted characters {#restricted-characters}
+
+    The table below shows the characters that are replaced by default.
+
+    When a replacement character is found in a filename, this character
+    will be escaped with the `‛` character to avoid ambiguous file names.
+    (e.g. a file named `␀.txt` would shown as `‛␀.txt`)
+
+    Each cloud storage backend can use a different set of characters,
+    which will be specified in the documentation for each backend.
+
+    | Character | Value | Replacement |
+    | --------- |:-----:|:-----------:|
+    | NUL       | 0x00  | ␀           |
+    | SOH       | 0x01  | ␁           |
+    | STX       | 0x02  | ␂           |
+    | ETX       | 0x03  | ␃           |
+    | EOT       | 0x04  | ␄           |
+    | ENQ       | 0x05  | ␅           |
+    | ACK       | 0x06  | ␆           |
+    | BEL       | 0x07  | ␇           |
+    | BS        | 0x08  | ␈           |
+    | HT        | 0x09  | ␉           |
+    | LF        | 0x0A  | ␊           |
+    | VT        | 0x0B  | ␋           |
+    | FF        | 0x0C  | ␌           |
+    | CR        | 0x0D  | ␍           |
+    | SO        | 0x0E  | ␎           |
+    | SI        | 0x0F  | ␏           |
+    | DLE       | 0x10  | ␐           |
+    | DC1       | 0x11  | ␑           |
+    | DC2       | 0x12  | ␒           |
+    | DC3       | 0x13  | ␓           |
+    | DC4       | 0x14  | ␔           |
+    | NAK       | 0x15  | ␕           |
+    | SYN       | 0x16  | ␖           |
+    | ETB       | 0x17  | ␗           |
+    | CAN       | 0x18  | ␘           |
+    | EM        | 0x19  | ␙           |
+    | SUB       | 0x1A  | ␚           |
+    | ESC       | 0x1B  | ␛           |
+    | FS        | 0x1C  | ␜           |
+    | GS        | 0x1D  | ␝           |
+    | RS        | 0x1E  | ␞           |
+    | US        | 0x1F  | ␟           |
+    | /         | 0x2F  | ／           |
+    | DEL       | 0x7F  | ␡           |
+
+    The default encoding will also encode these file names as they are
+    problematic with many cloud storage systems.
+
+    | File name | Replacement |
+    | --------- |:-----------:|
+    | .         | ．          |
+    | ..        | ．．         |
+
+    #### Invalid UTF-8 bytes {#invalid-utf8}
+
+    Some backends only support a sequence of well formed UTF-8 bytes
+    as file or directory names.
+
+    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 `0xFE` will be encoded as `‛FE`.
+
+    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
+    [local filenames](https://rclone.org/local/#filenames) section for details.
+
+    #### Encoding option {#encoding}
+
+    Most backends have an encoding options, specified as a flag
+    `--backend-encoding` where `backend` is the name of the backend, or as
+    a config parameter `encoding` (you'll need to select the Advanced
+    config in `rclone config` to see it).
+
+    This will have default value which encodes and decodes characters in
+    such a way as to preserve the maximum number of characters (see
+    above).
+
+    However this can be incorrect in some scenarios, for example if you
+    have a Windows file system with characters such as `＊` and `？` that
+    you want to remain as those characters on the remote rather than being
+    translated to `*` and `?`.
+
+    The `--backend-encoding` flags allow you to change that. You can
+    disable the encoding completely with `--backend-encoding None` or set
+    `encoding = None` in the config file.
+
+    Encoding takes a comma separated list of encodings. You can see the
+    list of all available characters by passing an invalid value to this
+    flag, eg `--local-encoding "help"` and `rclone help flags encoding`
+    will show you the defaults for the backends.
+
+    | Encoding  | Characters |
+    | --------- | ---------- |
+    | Asterisk | `*` |
+    | BackQuote | `` ` `` |
+    | BackSlash | `\` |
+    | Colon | `:` |
+    | CrLf | CR 0x0D, LF 0x0A |
+    | Ctl | All control characters 0x00-0x1F |
+    | Del | DEL 0x7F |
+    | Dollar | `$` |
+    | Dot | `.` |
+    | DoubleQuote | `"` |
+    | Hash | `#` |
+    | InvalidUtf8 | An invalid UTF-8 character (eg latin1) |
+    | LeftCrLfHtVt | CR 0x0D, LF 0x0A,HT 0x09, VT 0x0B on the left of a string |
+    | LeftPeriod | `.` on the left of a string |
+    | LeftSpace | SPACE on the left of a string |
+    | LeftTilde | `~` on the left of a string |
+    | LtGt | `<`, `>` |
+    | None | No characters are encoded |
+    | Percent | `%` |
+    | Pipe | \| |
+    | Question | `?` |
+    | RightCrLfHtVt | CR 0x0D, LF 0x0A, HT 0x09, VT 0x0B on the right of a string |
+    | RightPeriod | `.` on the right of a string |
+    | RightSpace | SPACE on the right of a string |
+    | SingleQuote | `'` |
+    | Slash | `/` |
+
+    To take a specific example, the FTP backend's default encoding is
+
+        --ftp-encoding "Slash,Del,Ctl,RightSpace,Dot"
+
+    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
+
+        Slash,LtGt,DoubleQuote,Colon,Question,Asterisk,Pipe,BackSlash,Ctl,RightSpace,RightPeriod,InvalidUtf8,Dot
+
+    to the existing ones, giving:
+
+        Slash,LtGt,DoubleQuote,Colon,Question,Asterisk,Pipe,BackSlash,Ctl,RightSpace,RightPeriod,InvalidUtf8,Dot,Del,RightSpace
+
+    This can be specified using the `--ftp-encoding` flag or using an `encoding` parameter in the config file.
+
+    Or let's say you have a Windows server but you want to preserve `＊`
+    and `？`, you would then have this as the encoding (the Windows
+    encoding minus `Asterisk` and `Question`).
+
+        Slash,LtGt,DoubleQuote,Colon,Pipe,BackSlash,Ctl,RightSpace,RightPeriod,InvalidUtf8,Dot
+
+    This can be specified using the `--local-encoding` flag or using an
+    `encoding` parameter in the config file.
+
+    ### MIME Type ###
+
+    MIME types (also known as media types) classify types of documents
+    using a simple text classification, eg `text/html` or
+    `application/pdf`.
+
+    Some cloud storage systems support reading (`R`) the MIME type of
+    objects and some support writing (`W`) the MIME type of objects.
+
+    The MIME type can be important if you are serving files directly to
+    HTTP from the storage system.
+
+    If you are copying from a remote which supports reading (`R`) to a
+    remote which supports writing (`W`) then rclone will preserve the MIME
+    types.  Otherwise they will be guessed from the extension, or the
+    remote itself may assign the MIME type.
+
+    ## Optional Features ##
+
+    All the remotes support a basic set of features, but there are some
+    optional features supported by some remotes used to make some
+    operations more efficient.
+
+    | Name                         | Purge | Copy | Move | DirMove | CleanUp | ListR | StreamUpload | LinkSharing | About | EmptyDir |
+    | ---------------------------- |:-----:|:----:|:----:|:-------:|:-------:|:-----:|:------------:|:------------:|:-----:| :------: |
+    | 1Fichier                     | No    | No   | No   | No      | No      | No    | No           | No           |   No  |  Yes |
+    | Amazon Drive                 | Yes   | No   | Yes  | Yes     | No [#575](https://github.com/rclone/rclone/issues/575) | No  | No  | No [#2178](https://github.com/rclone/rclone/issues/2178) | No  | Yes |
+    | Amazon S3                    | No    | Yes  | No   | No      | Yes     | Yes   | Yes          | No [#2178](https://github.com/rclone/rclone/issues/2178) | No  | No |
+    | Backblaze B2                 | No    | Yes  | No   | No      | Yes     | Yes   | Yes          | Yes          | No  | No |
+    | Box                          | Yes   | Yes  | Yes  | Yes     | Yes ‡‡  | No    | Yes          | Yes          | No  | Yes |
+    | Citrix ShareFile             | Yes   | Yes  | Yes  | Yes     | No      | No    | Yes          | No          | No  | Yes |
+    | Dropbox                      | Yes   | Yes  | Yes  | Yes     | No [#575](https://github.com/rclone/rclone/issues/575) | No  | Yes | Yes | Yes | Yes |
+    | FTP                          | No    | No   | Yes  | Yes     | No      | No    | Yes          | No [#2178](https://github.com/rclone/rclone/issues/2178) | No  | Yes |
+    | Google Cloud Storage         | Yes   | Yes  | No   | No      | No      | Yes   | Yes          | No [#2178](https://github.com/rclone/rclone/issues/2178) | No  | No |
+    | Google Drive                 | Yes   | Yes  | Yes  | Yes     | Yes     | Yes   | Yes          | Yes         | Yes | Yes |
+    | Google Photos                | No    | No   | No   | No      | No      | No    | No           | No          | No | No |
+    | HTTP                         | No    | No   | No   | No      | No      | No    | No           | No [#2178](https://github.com/rclone/rclone/issues/2178) | No  | Yes |
+    | Hubic                        | Yes † | Yes  | No   | No      | No      | Yes   | Yes          | No [#2178](https://github.com/rclone/rclone/issues/2178) | Yes | No |
+    | Jottacloud                   | Yes   | Yes  | Yes  | Yes     | Yes     | Yes   | No           | Yes                                                   | Yes | Yes |
+    | Mail.ru Cloud                | Yes   | Yes  | Yes  | Yes     | Yes     | No    | No           | Yes                                                   | Yes | Yes |
+    | Mega                         | Yes   | No   | Yes  | Yes     | Yes     | No    | No           | No [#2178](https://github.com/rclone/rclone/issues/2178) | Yes | Yes |
+    | Memory                       | No    | Yes  | No   | No      | No      | Yes   | Yes          | No          | No | No |
+    | Microsoft Azure Blob Storage | Yes   | Yes  | No   | No      | No      | Yes   | Yes          | No [#2178](https://github.com/rclone/rclone/issues/2178) | No  | No |
+    | Microsoft OneDrive           | Yes   | Yes  | Yes  | Yes     | Yes     | No    | No           | Yes | Yes | Yes |
+    | OpenDrive                    | Yes   | Yes  | Yes  | Yes     | No      | No    | No           | No                                                    | No  | Yes |
+    | OpenStack Swift              | Yes † | Yes  | No   | No      | No      | Yes   | Yes          | No [#2178](https://github.com/rclone/rclone/issues/2178) | Yes | No |
+    | pCloud                       | Yes   | Yes  | Yes  | Yes     | Yes     | No    | No           | Yes | Yes | Yes |
+    | premiumize.me                | Yes   | No   | Yes  | Yes     | No      | No    | No           | Yes         | Yes | Yes |
+    | put.io                       | Yes   | No   | Yes  | Yes     | Yes     | No    | Yes          | No [#2178](https://github.com/rclone/rclone/issues/2178) | Yes | Yes |
+    | QingStor                     | No    | Yes  | No   | No      | Yes     | Yes   | No           | No [#2178](https://github.com/rclone/rclone/issues/2178) | No  | No |
+    | Seafile                      | Yes   | Yes  | Yes  | Yes     | Yes     | Yes   | Yes          | Yes         | Yes | Yes |
+    | SFTP                         | No    | No   | Yes  | Yes     | No      | No    | Yes          | No [#2178](https://github.com/rclone/rclone/issues/2178) | Yes  | Yes |
+    | SugarSync                    | Yes   | Yes  | Yes  | Yes     | No      | No    | Yes          | Yes         | No  | Yes |
+    | Tardigrade                   | Yes † | No   | No   | No      | No      | Yes   | Yes          | No          | No  | No  |
+    | WebDAV                       | Yes   | Yes  | Yes  | Yes     | No      | No    | Yes ‡        | No [#2178](https://github.com/rclone/rclone/issues/2178) | Yes  | Yes |
+    | Yandex Disk                  | Yes   | Yes  | Yes  | Yes     | Yes     | No    | Yes          | Yes         | Yes | Yes |
+    | The local filesystem         | Yes   | No   | Yes  | Yes     | No      | No    | Yes          | No          | Yes | Yes |
+
+    ### Purge ###
+
+    This deletes a directory quicker than just deleting all the files in
+    the directory.
+
+    † Note Swift, Hubic, and Tardigrade implement this in order to delete
+    directory markers but they don't actually have a quicker way of deleting
+    files other than deleting them individually.
+
+    ‡ StreamUpload is not supported with Nextcloud
+
+    ### Copy ###
+
+    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 `rclone copy` or
+    `rclone move` if the remote doesn't support `Move` directly.
+
+    If the server doesn't support `Copy` directly then for copy operations
+    the file is downloaded then re-uploaded.
+
+    ### Move ###
+
+    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 `rclone move` if the
+    server doesn't support `DirMove`.
+
+    If the server isn't capable of `Move` then rclone simulates it with
+    `Copy` then delete.  If the server doesn't support `Copy` then rclone
+    will download the file and re-upload it.
+
+    ### DirMove ###
+
+    This is used to implement `rclone move` to move a directory if
+    possible.  If it isn't then it will use `Move` on each file (which
+    falls back to `Copy` then download and upload - see `Move` section).
+
+    ### CleanUp ###
+
+    This is used for emptying the trash for a remote by `rclone cleanup`.
+
+    If the server can't do `CleanUp` then `rclone cleanup` will return an
+    error.
+
+    ‡‡ Note that while Box implements this it has to delete every file
+    idividually so it will be slower than emptying the trash via the WebUI
+
+    ### ListR ###
+
+    The remote supports a recursive list to list all the contents beneath
+    a directory quickly.  This enables the `--fast-list` flag to work.
+    See the [rclone docs](https://rclone.org/docs/#fast-list) for more details.
+
+    ### StreamUpload ###
+
+    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. `rclone rcat`.
+
+    ### LinkSharing ###
+
+    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.
+
+    ### About ###
+
+    This is used to fetch quota information from the remote, like bytes
+    used/free/quota and bytes used in the trash.
+
+    This is also used to return the space used, available for `rclone mount`.
+
+    If the server can't do `About` then `rclone about` will return an
+    error.
+
+    ### EmptyDir ###
+
+    The remote supports empty directories. See [Limitations](https://rclone.org/bugs/#limitations)
+     for details. Most Object/Bucket based remotes do not support this.
+
+    # Global Flags
+
+    This describes the global flags available to every rclone command
+    split into two groups, non backend and backend flags.
+
+    ## Non Backend Flags
+
+    These flags are available for every command.
+
+      --ask-password                         Allow prompt for password for encrypted configuration. (default true)
+      --auto-confirm                         If enabled, do not request console confirmation.
+      --backup-dir string                    Make backups into hierarchy based in DIR.
+      --bind string                          Local address to bind to for outgoing connections, IPv4, IPv6 or name.
+      --buffer-size SizeSuffix               In memory buffer size when reading files for each --transfer. (default 16M)
+      --bwlimit BwTimetable                  Bandwidth limit in kBytes/s, or use suffix b|k|M|G or a full timetable.
+      --bwlimit-file BwTimetable             Bandwidth limit per file in kBytes/s, or use suffix b|k|M|G or a full timetable.
+      --ca-cert string                       CA certificate used to verify servers
+      --cache-dir string                     Directory rclone will use for caching. (default "$HOME/.cache/rclone")
+      --check-first                          Do all the checks before starting transfers.
+      --checkers int                         Number of checkers to run in parallel. (default 8)
+
+-c, --checksum Skip based on checksum (if available) & size, not
+mod-time & size --client-cert string Client SSL certificate (PEM) for
+mutual TLS auth --client-key string Client SSL private key (PEM) for
+mutual TLS auth --compare-dest string Include additional server-side
+path during comparison. --config string Config file. (default
+"$HOME/.config/rclone/rclone.conf") --contimeout duration Connect
+timeout (default 1m0s) --copy-dest string Implies --compare-dest but
+also copies files from path into destination. --cpuprofile string Write
+cpu profile to file --cutoff-mode string Mode to stop transfers when
+reaching the max transfer limit HARD|SOFT|CAUTIOUS (default "HARD")
+--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 --delete-excluded Delete files on dest
+excluded from sync --disable string Disable a comma separated list of
+features. Use help to see a list. -n, --dry-run Do a trial run with no
+permanent changes --dump DumpFlags List of items to dump from:
+headers,bodies,requests,responses,auth,filters,goroutines,openfiles
+--dump-bodies Dump HTTP headers and bodies - may contain sensitive info
+--dump-headers Dump HTTP headers - may contain sensitive info
+--error-on-no-transfer Sets exit code 9 if no files are transferred,
+useful in scripts --exclude stringArray Exclude files matching pattern
+--exclude-from stringArray Read exclude patterns from file (use - to
+read from stdin) --exclude-if-present string Exclude directories if
+filename is present --expect-continue-timeout duration Timeout when
+using expect / 100-continue in HTTP (default 1s) --fast-list Use
+recursive list if available. Uses more memory but fewer transactions.
+--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 filtering patterns from a file (use - to
+read from stdin) --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 --ignore-case Ignore case in filters (case insensitive)
+--ignore-case-sync Ignore case when synchronizing --ignore-checksum Skip
+post copy check of checksums. --ignore-errors delete even if there are
+I/O errors --ignore-existing Skip all files that exist on destination
+--ignore-size Ignore size when skipping use mod-time or checksum. -I,
+--ignore-times Don't skip files that match size and time - transfer all
+files --immutable Do not modify files. Fail if existing files have been
+modified. --include stringArray Include files matching pattern
+--include-from stringArray Read include patterns from file (use - to
+read from stdin) -i, --interactive Enable interactive mode --log-file
+string Log everything to this file --log-format string Comma separated
+list of log format options (default "date,time") --log-level string Log
+level DEBUG|INFO|NOTICE|ERROR (default "NOTICE") --low-level-retries int
+Number of low level retries to do. (default 10) --max-age Duration Only
+transfer files younger than this in s or suffix ms|s|m|h|d|w|M|y
+(default off) --max-backlog int Maximum number of objects in sync or
+check backlog. (default 10000) --max-delete int When synchronizing,
+limit the number of deletes (default -1) --max-depth int If set limits
+the recursion depth to this. (default -1) --max-duration duration
+Maximum duration rclone will transfer data for. --max-size SizeSuffix
+Only transfer files smaller than this in k or suffix b|k|M|G (default
+off) --max-stats-groups int Maximum number of stats groups to keep in
+memory. On max oldest is discarded. (default 1000) --max-transfer
+SizeSuffix Maximum size of data to transfer. (default off) --memprofile
+string Write memory profile to file --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 k or
+suffix b|k|M|G (default off) --modify-window duration Max time diff to
+be considered the same (default 1ns) --multi-thread-cutoff SizeSuffix
+Use multi-thread downloads for files above this size. (default 250M)
+--multi-thread-streams int Max number of streams to use for multi-thread
+downloads. (default 4) --no-check-certificate Do not verify the server
+SSL certificate. Insecure. --no-check-dest Don't check the destination,
+copy regardless. --no-gzip-encoding Don't set Accept-Encoding: gzip.
+--no-traverse Don't traverse destination file system on copy.
+--no-unicode-normalization Don't normalize unicode characters in
+filenames. --no-update-modtime Don't update destination mod-time if
+files identical. --order-by string Instructions on how to order the
+transfers, eg 'size,descending' --password-command SpaceSepList Command
+for supplying password for encrypted configuration. -P, --progress Show
+progress during transfer. -q, --quiet Print as little stuff as possible
+--rc Enable the remote control server. --rc-addr string IPaddress:Port
+or :Port to bind server to. (default "localhost:5572") --rc-allow-origin
+string Set the allowed origin for CORS. --rc-baseurl string Prefix for
+URLs - leave blank for root. --rc-cert string SSL PEM key (concatenation
+of certificate and CA certificate) --rc-client-ca string Client
+certificate authority to verify clients with --rc-enable-metrics Enable
+prometheus metrics on /metrics --rc-files string Path to local files to
+serve on the HTTP server. --rc-htpasswd string 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 SSL PEM Private key
+--rc-max-header-bytes int Maximum size of request header (default 4096)
+--rc-no-auth Don't require auth for certain methods. --rc-pass string
+Password for authentication. --rc-realm string realm for authentication
+(default "rclone") --rc-serve Enable the serving of remote objects.
+--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
+"https://api.github.com/repos/rclone/rclone-webui-react/releases/latest")
+--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't
+open the browser automatically --rc-web-gui-update Check and update to
+latest version of web gui --refresh-times Refresh the modtime of remote
+files. --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) --size-only
+Skip based on size only, not mod-time or checksum --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 string 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
+Enables --stats-one-line and add current date/time prefix.
+--stats-one-line-date-format string Enables --stats-one-line-date and
+uses custom formatted date. Enclose date string in double quotes (").
+See https://golang.org/pkg/time/#Time.Format --stats-unit string Show
+data rate in stats as either 'bits' or 'bytes'/s (default "bytes")
+--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 100k) --suffix string Suffix to add to changed
+files. --suffix-keep-extension Preserve the extension when using
+--suffix. --syslog Use Syslog for logging --syslog-facility string
+Facility for syslog, eg KERN,USER,... (default "DAEMON") --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) --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 "hash") --transfers int
+Number of file transfers to run in parallel. (default 4) -u, --update
+Skip files that are newer on the destination. --use-cookies Enable
+session cookiejar. --use-json-log Use json log format. --use-mmap Use
+mmap allocator (see docs). --use-server-modtime Use server modified time
+instead of object metadata --user-agent string Set the user-agent to a
+specified string. The default is rclone/ version (default
+"rclone/v1.53.0") -v, --verbose count Print lots more stuff (repeat for
+more)
+
+
+    ## Backend Flags
+
+    These flags are available for every command. They control the backends
+    and may be set in the config file.
+
+      --acd-auth-url string                                      Auth server URL.
+      --acd-client-id string                                     OAuth Client Id
+      --acd-client-secret string                                 OAuth Client Secret
+      --acd-encoding MultiEncoder                                This sets the encoding for the backend. (default Slash,InvalidUtf8,Dot)
+      --acd-templink-threshold SizeSuffix                        Files >= this size will be downloaded via their tempLink. (default 9G)
+      --acd-token string                                         OAuth Access Token as a JSON blob.
+      --acd-token-url string                                     Token server url.
+      --acd-upload-wait-per-gb Duration                          Additional time per GB to wait after a failed complete upload to see if it appears. (default 3m0s)
+      --alias-remote string                                      Remote or path to alias.
+      --azureblob-access-tier string                             Access tier of blob: hot, cool or archive.
+      --azureblob-account string                                 Storage Account Name (leave blank to use SAS URL or Emulator)
+      --azureblob-chunk-size SizeSuffix                          Upload chunk size (<= 100MB). (default 4M)
+      --azureblob-disable-checksum                               Don't store MD5 checksum with object metadata.
+      --azureblob-encoding MultiEncoder                          This sets the encoding for the backend. (default Slash,BackSlash,Del,Ctl,RightPeriod,InvalidUtf8)
+      --azureblob-endpoint string                                Endpoint for the service
+      --azureblob-key string                                     Storage Account Key (leave blank to use SAS URL or Emulator)
+      --azureblob-list-chunk int                                 Size of blob list. (default 5000)
+      --azureblob-memory-pool-flush-time Duration                How often internal memory buffer pools will be flushed. (default 1m0s)
+      --azureblob-memory-pool-use-mmap                           Whether to use mmap buffers in internal memory pool.
+      --azureblob-sas-url string                                 SAS URL for container level access only
+      --azureblob-upload-cutoff SizeSuffix                       Cutoff for switching to chunked upload (<= 256MB). (default 256M)
+      --azureblob-use-emulator                                   Uses local storage emulator if provided as 'true' (leave blank if using real azure storage endpoint)
+      --b2-account string                                        Account ID or Application Key ID
+      --b2-chunk-size SizeSuffix                                 Upload chunk size. Must fit in memory. (default 96M)
+      --b2-copy-cutoff SizeSuffix                                Cutoff for switching to multipart copy (default 4G)
+      --b2-disable-checksum                                      Disable checksums for large (> upload cutoff) files
+      --b2-download-auth-duration Duration                       Time before the 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 MultiEncoder                                 This sets 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-memory-pool-flush-time Duration                       How often internal memory buffer pools will be flushed. (default 1m0s)
+      --b2-memory-pool-use-mmap                                  Whether to use mmap buffers in internal memory pool.
+      --b2-test-mode string                                      A flag string for X-Bz-Test-Mode header for debugging.
+      --b2-upload-cutoff SizeSuffix                              Cutoff for switching to chunked upload. (default 200M)
+      --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 "user")
+      --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-encoding MultiEncoder                                This sets the encoding for the backend. (default Slash,BackSlash,Del,Ctl,RightSpace,InvalidUtf8,Dot)
+      --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 (>= 50MB). (default 50M)
+      --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 "$HOME/.cache/rclone/cache-backend")
+      --cache-chunk-size SizeSuffix                              The size of a chunk (partial file data). (default 5M)
+      --cache-chunk-total-size SizeSuffix                        The total size that the chunks can take up on the local disk. (default 10G)
+      --cache-db-path string                                     Directory to store file structure metadata DB. (default "$HOME/.cache/rclone/cache-backend")
+      --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-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 2G)
+      --chunker-fail-hard                                        Choose how chunker should handle files with missing or invalid chunks.
+      --chunker-hash-type string                                 Choose how chunker handles hash sums. All modes but "none" require metadata. (default "md5")
+      --chunker-meta-format string                               Format of the metadata object or "none". By default "simplejson". (default "simplejson")
+      --chunker-name-format string                               String format of chunk file names. (default "*.rclone_chunk.###")
+      --chunker-remote string                                    Remote to chunk/unchunk.
+      --chunker-start-from int                                   Minimum valid chunk number. Usually 0 or 1. (default 1)
+
+-L, --copy-links Follow symlinks and copy the pointed to item.
+--crypt-directory-name-encryption Option to either encrypt directory
+names or leave them intact. (default true) --crypt-filename-encryption
+string How to encrypt the filenames. (default "standard")
+--crypt-password string Password or pass phrase for encryption.
+(obscured) --crypt-password2 string Password or pass phrase for salt.
+Optional but recommended. (obscured) --crypt-remote string Remote to
+encrypt/decrypt. --crypt-server-side-across-configs Allow server side
+operations (eg copy) to work across different crypt configs.
+--crypt-show-mapping For all files listed show how the names encrypt.
+--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 (e.g. file.doc to file.docx). This will confuse
+sync and reupload every time. --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. Must a
+power of 2 >= 256k. (default 8M) --drive-client-id string OAuth Client
+Id --drive-client-secret string OAuth Client Secret
+--drive-disable-http2 Disable drive using http2 (default true)
+--drive-encoding MultiEncoder This sets the encoding for the backend.
+(default InvalidUtf8) --drive-export-formats string Comma separated list
+of preferred formats for downloading Google docs. (default
+"docx,xlsx,pptx,svg") --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-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-root-folder-id string ID of the root folder --drive-scope string
+Scope that rclone should use when requesting access from drive.
+--drive-server-side-across-configs Allow server side operations (eg
+copy) to work across different drive configs.
+--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-size-as-quota Show sizes as storage quota
+usage, not actual size. --drive-skip-checksum-gphotos Skip MD5 checksum
+on Google photos and videos only. --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-upload-limit Make upload limit errors be fatal
+--drive-team-drive string ID of the 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 8M) --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's are greater, use drive v2 API to download.
+(default off) --dropbox-auth-url string Auth server URL.
+--dropbox-chunk-size SizeSuffix Upload chunk size. (< 150M). (default
+48M) --dropbox-client-id string OAuth Client Id --dropbox-client-secret
+string OAuth Client Secret --dropbox-encoding MultiEncoder This sets the
+encoding for the backend. (default
+Slash,BackSlash,Del,RightSpace,InvalidUtf8,Dot) --dropbox-impersonate
+string Impersonate this user when using a business account.
+--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-encoding MultiEncoder This sets the encoding for the backend.
+(default
+Slash,LtGt,DoubleQuote,SingleQuote,BackQuote,Dollar,BackSlash,Del,Ctl,LeftSpace,RightSpace,InvalidUtf8,Dot)
+--fichier-shared-folder string If you want to download a shared folder,
+add this parameter --ftp-concurrency int Maximum number of FTP
+simultaneous connections, 0 for unlimited --ftp-disable-epsv Disable
+using EPSV even if server advertises support --ftp-encoding MultiEncoder
+This sets the encoding for the backend. (default
+Slash,Del,Ctl,RightSpace,Dot) --ftp-explicit-tls Use FTP over TLS
+(Explicit) --ftp-host string FTP host to connect to
+--ftp-no-check-certificate Do not verify the TLS certificate of the
+server --ftp-pass string FTP password (obscured) --ftp-port string FTP
+port, leave blank to use default (21) --ftp-tls Use FTPS over TLS
+(Implicit) --ftp-user string FTP username, leave blank for current
+username, $USER --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-encoding MultiEncoder This sets the
+encoding for the backend. (default Slash,CrLf,InvalidUtf8,Dot)
+--gcs-location string Location for the newly created buckets.
+--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. --gphotos-auth-url string Auth
+server URL. --gphotos-client-id string OAuth Client Id
+--gphotos-client-secret string OAuth Client Secret --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. --http-headers
+CommaSepList Set HTTP headers for all transactions --http-no-head Don't
+use HEAD requests to find file sizes in dir listing --http-no-slash Set
+this if the site doesn't end directories with / --http-url string URL of
+http host to connect to --hubic-auth-url string Auth server URL.
+--hubic-chunk-size SizeSuffix Above this size files will be chunked into
+a _segments container. (default 5G) --hubic-client-id string OAuth
+Client Id --hubic-client-secret string OAuth Client Secret
+--hubic-encoding MultiEncoder This sets the encoding for the backend.
+(default Slash,InvalidUtf8) --hubic-no-chunk Don't chunk files during
+streaming upload. --hubic-token string OAuth Access Token as a JSON
+blob. --hubic-token-url string Token server url. --jottacloud-encoding
+MultiEncoder This sets 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 10M) --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's. (default 10M)
+--koofr-encoding MultiEncoder This sets the encoding for the backend.
+(default Slash,BackSlash,Del,Ctl,InvalidUtf8,Dot) --koofr-endpoint
+string The Koofr API endpoint to use (default "https://app.koofr.net")
+--koofr-mountid string Mount ID of the mount to use. If omitted, the
+primary mount is used. --koofr-password string Your Koofr password for
+rclone (generate one at
+https://app.koofr.net/app/admin/preferences/password) (obscured)
+--koofr-setmtime Does the backend support setting modification time. Set
+this to false if you use a mount ID that points to a Dropbox or Amazon
+Drive backend. (default true) --koofr-user string Your Koofr user name
+-l, --links Translate symlinks to/from regular files with a
+'.rclonelink' 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-encoding
+MultiEncoder This sets the encoding for the backend. (default Slash,Dot)
+--local-no-check-updated Don't check to see if the files change during
+upload --local-no-set-modtime Disable setting modtime --local-no-sparse
+Disable sparse files for multi-thread downloads
+--local-no-unicode-normalization Don't apply unicode normalization to
+paths and filenames (Deprecated) --local-nounc string Disable UNC (long
+path names) conversion on Windows --mailru-check-hash What should copy
+do if file checksum is mismatched or invalid (default true)
+--mailru-encoding MultiEncoder This sets 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
+"_.mkv,_.avi,_.mp4,_.mp3,_.zip,_.gz,_.rar,_.pdf")
+--mailru-speedup-max-disk SizeSuffix This option allows you to disable
+speedup (put by hash) for large files (default 3G)
+--mailru-speedup-max-memory SizeSuffix Files larger than the size given
+below will always be hashed on disk. (default 32M) --mailru-user string
+User name (usually email) --mega-debug Output more debug from Mega.
+--mega-encoding MultiEncoder This sets 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-user string User name -x, --one-file-system
+Don't cross filesystem boundaries (unix/macOS only). --onedrive-auth-url
+string Auth server URL. --onedrive-chunk-size SizeSuffix Chunk size to
+upload files with - must be multiple of 320k (327,680 bytes). (default
+10M) --onedrive-client-id string OAuth Client Id
+--onedrive-client-secret string OAuth Client Secret --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 MultiEncoder This sets the encoding for the backend.
+(default
+Slash,LtGt,DoubleQuote,Colon,Question,Asterisk,Pipe,Hash,Percent,BackSlash,Del,Ctl,LeftSpace,LeftTilde,RightSpace,RightPeriod,InvalidUtf8,Dot)
+--onedrive-expose-onenote-files Set to make OneNote files show up in
+directory listings. --onedrive-no-versions Remove all versions on
+modifying operations --onedrive-server-side-across-configs Allow server
+side operations (eg copy) to work across different onedrive configs.
+--onedrive-token string OAuth Access Token as a JSON blob.
+--onedrive-token-url string Token server url. --opendrive-chunk-size
+SizeSuffix Files will be uploaded in chunks this size. (default 10M)
+--opendrive-encoding MultiEncoder This sets 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-encoding MultiEncoder This sets the
+encoding for the backend. (default
+Slash,BackSlash,Del,Ctl,InvalidUtf8,Dot) --pcloud-hostname string
+Hostname to connect to. (default "api.pcloud.com")
+--pcloud-root-folder-id string Fill in for rclone to use a non root
+folder as its starting point. (default "d0") --pcloud-token string OAuth
+Access Token as a JSON blob. --pcloud-token-url string Token server url.
+--premiumizeme-encoding MultiEncoder This sets the encoding for the
+backend. (default Slash,DoubleQuote,BackSlash,Del,Ctl,InvalidUtf8,Dot)
+--putio-encoding MultiEncoder This sets the encoding for the backend.
+(default Slash,BackSlash,Del,Ctl,InvalidUtf8,Dot)
+--qingstor-access-key-id string QingStor Access Key ID
+--qingstor-chunk-size SizeSuffix Chunk size to use for uploading.
+(default 4M) --qingstor-connection-retries int Number of connection
+retries. (default 3) --qingstor-encoding MultiEncoder This sets 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. Only
+applies if access_key_id and secret_access_key is blank.
+--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 200M) --qingstor-zone string Zone
+to connect to. --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 5M)
+--s3-copy-cutoff SizeSuffix Cutoff for switching to multipart copy
+(default 4.656G) --s3-disable-checksum Don't store MD5 checksum with
+object metadata --s3-encoding MultiEncoder This sets 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-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-memory-pool-flush-time Duration
+How often internal memory buffer pools will be flushed. (default 1m0s)
+--s3-memory-pool-use-mmap Whether to use mmap buffers in internal memory
+pool. --s3-no-check-bucket If set don't attempt to check the bucket
+exists or create it --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-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 If using SSE-C you must provide the secret
+encryption key used to encrypt/decrypt your data.
+--s3-sse-customer-key-md5 string If using SSE-C you must provide the
+secret encryption key MD5 checksum. --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. (default
+4) --s3-upload-cutoff SizeSuffix Cutoff for switching to chunked upload
+(default 200M) --s3-use-accelerate-endpoint If true use the AWS S3
+accelerated endpoint. --s3-v2-auth If true use v2 authentication.
+--seafile-2fa Two-factor authentication ('true' if the account has 2FA
+enabled) --seafile-create-library Should rclone create a library if it
+doesn't exist --seafile-encoding MultiEncoder This sets the encoding for
+the backend. (default Slash,DoubleQuote,BackSlash,Ctl,InvalidUtf8)
+--seafile-library string Name of the library. Leave blank to access all
+non-encrypted libraries. --seafile-library-key string Library password
+(for encrypted libraries only). Leave blank if you pass it through the
+command line. (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-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-key-file
+string Path to PEM-encoded private key file, leave blank or set
+key-use-agent to use ssh-agent. --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, If specified, will
+override key_file parameter. --sftp-key-use-agent When set forces the
+usage of the ssh-agent. --sftp-md5sum-command string The command used to
+read md5 hashes. Leave blank for autodetect. --sftp-pass string SSH
+password, leave blank to use ssh-agent. (obscured) --sftp-path-override
+string Override path used by SSH connection. --sftp-port string SSH
+port, leave blank to use default (22) --sftp-server-command string
+Specifies the path or command to run a sftp server on the remote host.
+--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. Leave blank for autodetect. --sftp-skip-links Set to skip any
+symlinks and any other non regular files. --sftp-subsystem string
+Specifies the SSH2 subsystem on the remote host. (default "sftp")
+--sftp-use-insecure-cipher Enable the use of insecure ciphers and key
+exchange methods. --sftp-user string SSH username, leave blank for
+current username, ncw --sharefile-chunk-size SizeSuffix Upload chunk
+size. Must a power of 2 >= 256k. (default 64M) --sharefile-encoding
+MultiEncoder This sets 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-upload-cutoff SizeSuffix Cutoff for switching to multipart
+upload. (default 128M) --skip-links Don't warn about skipped symlinks.
+--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-encoding MultiEncoder This sets 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 into
+a _segments container. (default 5G) --swift-domain string User domain -
+optional (v3 auth) (OS_USER_DOMAIN_NAME) --swift-encoding MultiEncoder
+This sets the encoding for the backend. (default Slash,InvalidUtf8)
+--swift-endpoint-type string Endpoint type to choose from the service
+catalogue (OS_ENDPOINT_TYPE) (default "public") --swift-env-auth Get
+swift credentials from environment variables in standard OpenStack form.
+--swift-key string API key or password (OS_PASSWORD). --swift-no-chunk
+Don't chunk files during streaming upload. --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-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).
+--tardigrade-access-grant string Access Grant. --tardigrade-api-key
+string API Key. --tardigrade-passphrase string Encryption Passphrase. To
+access existing objects enter passphrase used for uploading.
+--tardigrade-provider string Choose an authentication method. (default
+"existing") --tardigrade-satellite-address @
+: Satellite Address. Custom satellite address should match the format: @
+:. (default "us-central-1.tardigrade.io") --union-action-policy string
+Policy to choose upstream on ACTION category. (default "epall")
+--union-cache-time int Cache time of usage and free space (in seconds).
+This option is only useful when a path preserving policy is used.
+(default 120) --union-create-policy string Policy to choose upstream on
+CREATE category. (default "epmfs") --union-search-policy string Policy
+to choose upstream on SEARCH category. (default "ff") --union-upstreams
+string List of space separated upstreams. --webdav-bearer-token string
+Bearer token instead of user/pass (eg a Macaroon)
+--webdav-bearer-token-command string Command to run to get a bearer
+token --webdav-pass string Password. (obscured) --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-encoding MultiEncoder This sets the encoding for the backend.
+(default Slash,Del,Ctl,InvalidUtf8,Dot) --yandex-token string OAuth
+Access Token as a JSON blob. --yandex-token-url string Token server url.
+
+
+     1Fichier
+    -----------------------------------------
+
+    This is a backend for the [1fichier](https://1fichier.com) cloud
+    storage service. Note that a Premium subscription is required to use
+    the API.
+
+    Paths are specified as `remote:path`
+
+    Paths may be as deep as required, eg `remote:directory/subdirectory`.
+
+    The initial setup for 1Fichier involves getting the API key from the website which you
+    need to do in your browser.
+
+    Here is an example of how to make a remote called `remote`.  First run:
+
+         rclone config
+
+    This will guide you through an interactive setup process:
+
+No remotes found - make a new one n) New remote s) Set configuration
+password q) Quit config n/s/q> n name> remote Type of storage to
+configure. Enter a string value. Press Enter for the default ("").
+Choose a number from below, or type in your own value [snip] XX /
+1Fichier  "fichier" [snip] Storage> 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 (""). api_key> example_key
+
+Edit advanced config? (y/n) y) Yes n) No y/n> Remote config
+-------------------- [remote] type = fichier api_key = example_key
+-------------------- y) Yes this is OK e) Edit this remote d) Delete
+this remote y/e/d> y
+
+
+    Once configured you can then use `rclone` like this,
+
+    List directories in top level of your 1Fichier account
+
+        rclone lsd remote:
+
+    List all the files in your 1Fichier account
+
+        rclone ls remote:
+
+    To copy a local directory to a 1Fichier directory called backup
+
+        rclone copy /home/source remote:backup
+
+    ### Modified time and hashes ###
+
+    1Fichier does not support modification times. It supports the Whirlpool hash algorithm.
+
+    ### Duplicated files ###
+
+    1Fichier can have two files with exactly the same name and path (unlike a
+    normal file system).
+
+    Duplicated files cause problems with the syncing and you will see
+    messages in the log about duplicates.
+
+    #### Restricted filename characters
+
+    In addition to the [default restricted characters set](https://rclone.org/overview/#restricted-characters)
+    the following characters are also replaced:
+
+    | Character | Value | Replacement |
+    | --------- |:-----:|:-----------:|
+    | \         | 0x5C  | ＼           |
+    | <         | 0x3C  | ＜           |
+    | >         | 0x3E  | ＞           |
+    | "         | 0x22  | ＂           |
+    | $         | 0x24  | ＄           |
+    | `         | 0x60  | ｀           |
+    | '         | 0x27  | ＇           |
+
+    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:
+
+    | Character | Value | Replacement |
+    | --------- |:-----:|:-----------:|
+    | SP        | 0x20  | ␠           |
+
+    Invalid UTF-8 bytes will also be [replaced](https://rclone.org/overview/#invalid-utf8),
+    as they can't be used in JSON strings.
+
+
+    ### Standard Options
+
+    Here are the standard options specific to fichier (1Fichier).
+
+    #### --fichier-api-key
 
     Your API Key, get it from https://1fichier.com/console/params.pl
-    Enter a string value. Press Enter for the default ("").
-    api_key> example_key
 
-    Edit advanced config? (y/n)
-    y) Yes
-    n) No
-    y/n> 
-    Remote config
-    --------------------
-    [remote]
-    type = fichier
-    api_key = example_key
-    --------------------
-    y) Yes this is OK
-    e) Edit this remote
-    d) Delete this remote
-    y/e/d> y
+    - Config:      api_key
+    - Env Var:     RCLONE_FICHIER_API_KEY
+    - Type:        string
+    - Default:     ""
 
-Once configured you can then use rclone like this,
+    ### Advanced Options
 
-List directories in top level of your 1Fichier account
+    Here are the advanced options specific to fichier (1Fichier).
 
-    rclone lsd remote:
+    #### --fichier-shared-folder
 
-List all the files in your 1Fichier account
+    If you want to download a shared folder, add this parameter
 
-    rclone ls remote:
+    - Config:      shared_folder
+    - Env Var:     RCLONE_FICHIER_SHARED_FOLDER
+    - Type:        string
+    - Default:     ""
 
-To copy a local directory to a 1Fichier directory called backup
+    #### --fichier-encoding
 
-    rclone copy /home/source remote:backup
+    This sets the encoding for the backend.
 
-Modified time and hashes
+    See: the [encoding section in the overview](https://rclone.org/overview/#encoding) for more info.
 
-1Fichier does not support modification times. It supports the Whirlpool
-hash algorithm.
-
-Duplicated files
-
-1Fichier can have two files with exactly the same name and path (unlike
-a normal file system).
-
-Duplicated files cause problems with the syncing and you will see
-messages in the log about duplicates.
-
-Restricted filename characters
-
-In addition to the default restricted characters set the following
-characters are also replaced:
-
-  Character    Value   Replacement
-  ----------- ------- -------------
-  \            0x5C        ＼
-  <            0x3C        ＜
-  >            0x3E        ＞
-  "            0x22        ＂
-  $            0x24        ＄
-  `            0x60        ｀
-  ’            0x27        ＇
-
-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:
-
-  Character    Value   Replacement
-  ----------- ------- -------------
-  SP           0x20         ␠
-
-Invalid UTF-8 bytes will also be replaced, as they can’t be used in JSON
-strings.
-
-Standard Options
-
-Here are the standard options specific to fichier (1Fichier).
-
-–fichier-api-key
-
-Your API Key, get it from https://1fichier.com/console/params.pl
-
--   Config: api_key
--   Env Var: RCLONE_FICHIER_API_KEY
--   Type: string
--   Default: ""
-
-Advanced Options
-
-Here are the advanced options specific to fichier (1Fichier).
-
-–fichier-shared-folder
-
-If you want to download a shared folder, add this parameter
-
--   Config: shared_folder
--   Env Var: RCLONE_FICHIER_SHARED_FOLDER
--   Type: string
--   Default: ""
-
-–fichier-encoding
-
-This sets the encoding for the backend.
-
-See: the encoding section in the overview for more info.
-
--   Config: encoding
--   Env Var: RCLONE_FICHIER_ENCODING
--   Type: MultiEncoder
--   Default:
-    Slash,LtGt,DoubleQuote,SingleQuote,BackQuote,Dollar,BackSlash,Del,Ctl,LeftSpace,RightSpace,InvalidUtf8,Dot
+    - Config:      encoding
+    - Env Var:     RCLONE_FICHIER_ENCODING
+    - Type:        MultiEncoder
+    - Default:     Slash,LtGt,DoubleQuote,SingleQuote,BackQuote,Dollar,BackSlash,Del,Ctl,LeftSpace,RightSpace,InvalidUtf8,Dot
 
 
-Alias
 
-The alias remote provides a new name for another remote.
+     Alias
+    -----------------------------------------
 
-Paths may be as deep as required or a local path, eg
-remote:directory/subdirectory or /directory/subdirectory.
+    The `alias` remote provides a new name for another remote.
 
-During the initial setup with rclone config you will specify the target
-remote. The target remote can either be a local path or another remote.
+    Paths may be as deep as required or a local path, 
+    eg `remote:directory/subdirectory` or `/directory/subdirectory`.
 
-Subfolders can be used in target remote. Assume an alias remote named
-backup with the target mydrive:private/backup. Invoking
-rclone mkdir backup:desktop is exactly the same as invoking
-rclone mkdir mydrive:private/backup/desktop.
+    During the initial setup with `rclone config` you will specify the target
+    remote. The target remote can either be a local path or another remote.
 
-There will be no special handling of paths containing .. segments.
-Invoking rclone mkdir backup:../desktop is exactly the same as invoking
-rclone mkdir mydrive:private/backup/../desktop. The empty path is not
-allowed as a remote. To alias the current directory use . instead.
+    Subfolders can be used in target remote. Assume an alias remote named `backup`
+    with the target `mydrive:private/backup`. Invoking `rclone mkdir backup:desktop`
+    is exactly the same as invoking `rclone mkdir mydrive:private/backup/desktop`.
 
-Here is an example of how to make an alias called remote for local
-folder. First run:
+    There will be no special handling of paths containing `..` segments.
+    Invoking `rclone mkdir backup:../desktop` is exactly the same as invoking
+    `rclone mkdir mydrive:private/backup/../desktop`.
+    The empty path is not allowed as a remote. To alias the current directory
+    use `.` instead.
 
-     rclone config
+    Here is an example of how to make an alias called `remote` for local folder.
+    First run:
 
-This will guide you through an interactive setup process:
+         rclone config
+
+    This will guide you through an interactive setup process:
+
+No remotes found - make a new one n) New remote s) Set configuration
+password q) Quit config n/s/q> n name> remote Type of storage to
+configure. Choose a number from below, or type in your own value [snip]
+XX / Alias for an existing remote  "alias" [snip] Storage> alias Remote
+or path to alias. Can be "myremote:path/to/dir", "myremote:bucket",
+"myremote:" or "/local/path". remote> /mnt/storage/backup Remote config
+-------------------- [remote] remote = /mnt/storage/backup
+-------------------- y) Yes this is OK e) Edit this remote d) Delete
+this remote y/e/d> y Current remotes:
+
+Name Type ==== ==== remote alias
+
+e)  Edit existing remote
+f)  New remote
+g)  Delete remote
+h)  Rename remote
+i)  Copy remote
+j)  Set configuration password
+k)  Quit config e/n/d/r/c/s/q> q
+
+
+    Once configured you can then use `rclone` like this,
+
+    List directories in top level in `/mnt/storage/backup`
+
+        rclone lsd remote:
+
+    List all the files in `/mnt/storage/backup`
+
+        rclone ls remote:
+
+    Copy another local directory to the alias directory called source
+
+        rclone copy /home/source remote:source
+
+
+    ### Standard Options
+
+    Here are the standard options specific to alias (Alias for an existing remote).
+
+    #### --alias-remote
 
-    No remotes found - make a new one
-    n) New remote
-    s) Set configuration password
-    q) Quit config
-    n/s/q> n
-    name> remote
-    Type of storage to configure.
-    Choose a number from below, or type in your own value
-    [snip]
-    XX / Alias for an existing remote
-       \ "alias"
-    [snip]
-    Storage> alias
     Remote or path to alias.
     Can be "myremote:path/to/dir", "myremote:bucket", "myremote:" or "/local/path".
-    remote> /mnt/storage/backup
-    Remote config
-    --------------------
-    [remote]
-    remote = /mnt/storage/backup
-    --------------------
-    y) Yes this is OK
-    e) Edit this remote
-    d) Delete this remote
-    y/e/d> y
-    Current remotes:
 
-    Name                 Type
-    ====                 ====
-    remote               alias
+    - Config:      remote
+    - Env Var:     RCLONE_ALIAS_REMOTE
+    - Type:        string
+    - Default:     ""
 
-    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> q
 
-Once configured you can then use rclone like this,
 
-List directories in top level in /mnt/storage/backup
+     Amazon Drive
+    -----------------------------------------
 
-    rclone lsd remote:
-
-List all the files in /mnt/storage/backup
-
-    rclone ls remote:
-
-Copy another local directory to the alias directory called source
-
-    rclone copy /home/source remote:source
-
-Standard Options
-
-Here are the standard options specific to alias (Alias for an existing
-remote).
-
-–alias-remote
-
-Remote or path to alias. Can be “myremote:path/to/dir”,
-“myremote:bucket”, “myremote:” or “/local/path”.
-
--   Config: remote
--   Env Var: RCLONE_ALIAS_REMOTE
--   Type: string
--   Default: ""
-
-
-Amazon Drive
-
-Amazon Drive, formerly known as Amazon Cloud Drive, is a cloud storage
-service run by Amazon for consumers.
-
-
-Status
-
-IMPORTANT: rclone supports Amazon Drive only if you have your own set of
-API keys. Unfortunately the Amazon Drive developer program is now closed
-to new entries so if you don’t already have your own set of keys you
-will not be able to use rclone with Amazon Drive.
-
-For the history on why rclone no longer has a set of Amazon Drive API
-keys see the forum.
-
-If you happen to know anyone who works at Amazon then please ask them to
-re-instate rclone into the Amazon Drive developer program - thanks!
+    Amazon Drive, formerly known as Amazon Cloud Drive, is a cloud storage
+    service run by Amazon for consumers.
 
+    ## Status
 
-Setup
-
-The initial setup for Amazon Drive involves getting a token from Amazon
-which you need to do in your browser. rclone config walks you through
-it.
+    **Important:** rclone supports Amazon Drive only if you have your own
+    set of API keys. Unfortunately the [Amazon Drive developer
+    program](https://developer.amazon.com/amazon-drive) is now closed to
+    new entries so if you don't already have your own set of keys you will
+    not be able to use rclone with Amazon Drive.
 
-The configuration process for Amazon Drive may involve using an oauth
-proxy. This is used to keep the Amazon credentials out of the source
-code. The proxy runs in Google’s very secure App Engine environment and
-doesn’t store any credentials which pass through it.
+    For the history on why rclone no longer has a set of Amazon Drive API
+    keys see [the forum](https://forum.rclone.org/t/rclone-has-been-banned-from-amazon-drive/2314).
 
-Since rclone doesn’t currently have its own Amazon Drive credentials so
-you will either need to have your own client_id and client_secret with
-Amazon Drive, or use a third party oauth proxy in which case you will
-need to enter client_id, client_secret, auth_url and token_url.
+    If you happen to know anyone who works at Amazon then please ask them
+    to re-instate rclone into the Amazon Drive developer program - thanks!
 
-Note also if you are not using Amazon’s auth_url and token_url, (ie you
-filled in something for those) then if setting up on a remote machine
-you can only use the copying the config method of configuration -
-rclone authorize will not work.
+    ## Setup
 
-Here is an example of how to make a remote called remote. First run:
+    The initial setup for Amazon Drive involves getting a token from
+    Amazon which you need to do in your browser.  `rclone config` walks
+    you through it.
 
-     rclone config
+    The configuration process for Amazon Drive may involve using an [oauth
+    proxy](https://github.com/ncw/oauthproxy). This is used to keep the
+    Amazon credentials out of the source code.  The proxy runs in Google's
+    very secure App Engine environment and doesn't store any credentials
+    which pass through it.
 
-This will guide you through an interactive setup process:
+    Since rclone doesn't currently have its own Amazon Drive credentials
+    so you will either need to have your own `client_id` and
+    `client_secret` with Amazon Drive, or use a third party oauth proxy
+    in which case you will need to enter `client_id`, `client_secret`,
+    `auth_url` and `token_url`.
 
-    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> n
-    name> remote
-    Type of storage to configure.
-    Choose a number from below, or type in your own value
-    [snip]
-    XX / Amazon Drive
-       \ "amazon cloud drive"
-    [snip]
-    Storage> amazon cloud drive
-    Amazon Application Client Id - required.
-    client_id> your client ID goes here
-    Amazon Application Client Secret - required.
-    client_secret> your client secret goes here
-    Auth server URL - leave blank to use Amazon's.
-    auth_url> Optional auth URL
-    Token server url - leave blank to use Amazon's.
-    token_url> Optional token URL
-    Remote config
-    Make sure your Redirect URL is set to "http://127.0.0.1:53682/" in your custom config.
-    Use auto config?
-     * Say Y if not sure
-     * Say N if you are working on a remote or headless machine
-    y) Yes
-    n) No
-    y/n> y
-    If your browser doesn'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
-    --------------------
-    [remote]
-    client_id = your client ID goes here
-    client_secret = your client secret goes here
-    auth_url = Optional auth URL
-    token_url = Optional token URL
-    token = {"access_token":"xxxxxxxxxxxxxxxxxxxxxxx","token_type":"bearer","refresh_token":"xxxxxxxxxxxxxxxxxx","expiry":"2015-09-06T16:07:39.658438471+01:00"}
-    --------------------
-    y) Yes this is OK
-    e) Edit this remote
-    d) Delete this remote
-    y/e/d> y
+    Note also if you are not using Amazon's `auth_url` and `token_url`,
+    (ie you filled in something for those) then if setting up on a remote
+    machine you can only use the [copying the config method of
+    configuration](https://rclone.org/remote_setup/#configuring-by-copying-the-config-file)
+    - `rclone authorize` will not work.
 
-See the remote setup docs for how to set it up on a machine with no
-Internet browser available.
+    Here is an example of how to make a remote called `remote`.  First run:
 
-Note that rclone runs a webserver on your local machine to collect the
-token as returned from Amazon. This only runs from the moment it opens
-your browser to the moment you get back the verification code. This is
-on http://127.0.0.1:53682/ and this it may require you to unblock it
-temporarily if you are running a host firewall.
+         rclone config
 
-Once configured you can then use rclone like this,
+    This will guide you through an interactive setup process:
 
-List directories in top level of your Amazon Drive
+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> n name>
+remote Type of storage to configure. Choose a number from below, or type
+in your own value [snip] XX / Amazon Drive  "amazon cloud drive" [snip]
+Storage> amazon cloud drive Amazon Application Client Id - required.
+client_id> your client ID goes here Amazon Application Client Secret -
+required. client_secret> your client secret goes here Auth server URL -
+leave blank to use Amazon's. auth_url> Optional auth URL Token server
+url - leave blank to use Amazon's. token_url> Optional token URL Remote
+config Make sure your Redirect URL is set to "http://127.0.0.1:53682/"
+in your custom config. Use auto config? * Say Y if not sure * Say N if
+you are working on a remote or headless machine y) Yes n) No y/n> y If
+your browser doesn'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 -------------------- [remote] client_id =
+your client ID goes here client_secret = your client secret goes here
+auth_url = Optional auth URL token_url = Optional token URL token =
+{"access_token":"xxxxxxxxxxxxxxxxxxxxxxx","token_type":"bearer","refresh_token":"xxxxxxxxxxxxxxxxxx","expiry":"2015-09-06T16:07:39.658438471+01:00"}
+-------------------- y) Yes this is OK e) Edit this remote d) Delete
+this remote y/e/d> y
 
-    rclone lsd remote:
 
-List all the files in your Amazon Drive
+    See the [remote setup docs](https://rclone.org/remote_setup/) for how to set it up on a
+    machine with no Internet browser available.
 
-    rclone ls remote:
+    Note that rclone runs a webserver on your local machine to collect the
+    token as returned from Amazon. This only runs from the moment it
+    opens your browser to the moment you get back the verification
+    code.  This is on `http://127.0.0.1:53682/` and this it may require
+    you to unblock it temporarily if you are running a host firewall.
 
-To copy a local directory to an Amazon Drive directory called backup
+    Once configured you can then use `rclone` like this,
 
-    rclone copy /home/source remote:backup
+    List directories in top level of your Amazon Drive
 
-Modified time and MD5SUMs
+        rclone lsd remote:
 
-Amazon Drive doesn’t allow modification times to be changed via the API
-so these won’t be accurate or used for syncing.
+    List all the files in your Amazon Drive
 
-It does store MD5SUMs so for a more accurate sync, you can use the
---checksum flag.
+        rclone ls remote:
 
-Restricted filename characters
+    To copy a local directory to an Amazon Drive directory called backup
 
-  Character    Value   Replacement
-  ----------- ------- -------------
-  NUL          0x00         ␀
-  /            0x2F        ／
+        rclone copy /home/source remote:backup
 
-Invalid UTF-8 bytes will also be replaced, as they can’t be used in JSON
-strings.
+    ### Modified time and MD5SUMs ###
 
-Deleting files
+    Amazon Drive doesn't allow modification times to be changed via
+    the API so these won't be accurate or used for syncing.
 
-Any files you delete with rclone will end up in the trash. Amazon don’t
-provide an API to permanently delete files, nor to empty the trash, so
-you will have to do that with one of Amazon’s apps or via the Amazon
-Drive website. As of November 17, 2016, files are automatically deleted
-by Amazon from the trash after 30 days.
+    It does store MD5SUMs so for a more accurate sync, you can use the
+    `--checksum` flag.
 
-Using with non .com Amazon accounts
+    #### Restricted filename characters
 
-Let’s say you usually use amazon.co.uk. When you authenticate with
-rclone it will take you to an amazon.com page to log in. Your
-amazon.co.uk email and password should work here just fine.
+    | Character | Value | Replacement |
+    | --------- |:-----:|:-----------:|
+    | NUL       | 0x00  | ␀           |
+    | /         | 0x2F  | ／          |
 
-Standard Options
+    Invalid UTF-8 bytes will also be [replaced](https://rclone.org/overview/#invalid-utf8),
+    as they can't be used in JSON strings.
 
-Here are the standard options specific to amazon cloud drive (Amazon
-Drive).
+    ### Deleting files ###
 
-–acd-client-id
+    Any files you delete with rclone will end up in the trash.  Amazon
+    don't provide an API to permanently delete files, nor to empty the
+    trash, so you will have to do that with one of Amazon's apps or via
+    the Amazon Drive website. As of November 17, 2016, files are 
+    automatically deleted by Amazon from the trash after 30 days.
 
-Amazon Application Client ID.
+    ### Using with non `.com` Amazon accounts ###
 
--   Config: client_id
--   Env Var: RCLONE_ACD_CLIENT_ID
--   Type: string
--   Default: ""
+    Let's say you usually use `amazon.co.uk`. When you authenticate with
+    rclone it will take you to an `amazon.com` page to log in.  Your
+    `amazon.co.uk` email and password should work here just fine.
 
-–acd-client-secret
 
-Amazon Application Client Secret.
+    ### Standard Options
 
--   Config: client_secret
--   Env Var: RCLONE_ACD_CLIENT_SECRET
--   Type: string
--   Default: ""
+    Here are the standard options specific to amazon cloud drive (Amazon Drive).
 
-Advanced Options
+    #### --acd-client-id
 
-Here are the advanced options specific to amazon cloud drive (Amazon
-Drive).
+    OAuth Client Id
+    Leave blank normally.
 
-–acd-auth-url
+    - Config:      client_id
+    - Env Var:     RCLONE_ACD_CLIENT_ID
+    - Type:        string
+    - Default:     ""
 
-Auth server URL. Leave blank to use Amazon’s.
+    #### --acd-client-secret
 
--   Config: auth_url
--   Env Var: RCLONE_ACD_AUTH_URL
--   Type: string
--   Default: ""
+    OAuth Client Secret
+    Leave blank normally.
 
-–acd-token-url
+    - Config:      client_secret
+    - Env Var:     RCLONE_ACD_CLIENT_SECRET
+    - Type:        string
+    - Default:     ""
 
-Token server url. leave blank to use Amazon’s.
+    ### Advanced Options
 
--   Config: token_url
--   Env Var: RCLONE_ACD_TOKEN_URL
--   Type: string
--   Default: ""
+    Here are the advanced options specific to amazon cloud drive (Amazon Drive).
 
-–acd-checkpoint
+    #### --acd-token
 
-Checkpoint for internal polling (debug).
+    OAuth Access Token as a JSON blob.
 
--   Config: checkpoint
--   Env Var: RCLONE_ACD_CHECKPOINT
--   Type: string
--   Default: ""
+    - Config:      token
+    - Env Var:     RCLONE_ACD_TOKEN
+    - Type:        string
+    - Default:     ""
 
-–acd-upload-wait-per-gb
+    #### --acd-auth-url
 
-Additional time per GB to wait after a failed complete upload to see if
-it appears.
+    Auth server URL.
+    Leave blank to use the provider defaults.
 
-Sometimes Amazon Drive gives an error when a file has been fully
-uploaded but the file appears anyway after a little while. This happens
-sometimes for files over 1GB in size and nearly every time for files
-bigger than 10GB. This parameter controls the time rclone waits for the
-file to appear.
+    - Config:      auth_url
+    - Env Var:     RCLONE_ACD_AUTH_URL
+    - Type:        string
+    - Default:     ""
 
-The default value for this parameter is 3 minutes per GB, so by default
-it will wait 3 minutes for every GB uploaded to see if the file appears.
+    #### --acd-token-url
 
-You can disable this feature by setting it to 0. This may cause conflict
-errors as rclone retries the failed upload but the file will most likely
-appear correctly eventually.
+    Token server url.
+    Leave blank to use the provider defaults.
 
-These values were determined empirically by observing lots of uploads of
-big files for a range of file sizes.
+    - Config:      token_url
+    - Env Var:     RCLONE_ACD_TOKEN_URL
+    - Type:        string
+    - Default:     ""
 
-Upload with the “-v” flag to see more info about what rclone is doing in
-this situation.
+    #### --acd-checkpoint
 
--   Config: upload_wait_per_gb
--   Env Var: RCLONE_ACD_UPLOAD_WAIT_PER_GB
--   Type: Duration
--   Default: 3m0s
+    Checkpoint for internal polling (debug).
 
-–acd-templink-threshold
+    - Config:      checkpoint
+    - Env Var:     RCLONE_ACD_CHECKPOINT
+    - Type:        string
+    - Default:     ""
 
-Files >= this size will be downloaded via their tempLink.
+    #### --acd-upload-wait-per-gb
 
-Files this size or more will be downloaded via their “tempLink”. This is
-to work around a problem with Amazon Drive which blocks downloads of
-files bigger than about 10GB. The default for this is 9GB which
-shouldn’t need to be changed.
+    Additional time per GB to wait after a failed complete upload to see if it appears.
 
-To download files above this threshold, rclone requests a “tempLink”
-which downloads the file through a temporary URL directly from the
-underlying S3 storage.
+    Sometimes Amazon Drive gives an error when a file has been fully
+    uploaded but the file appears anyway after a little while.  This
+    happens sometimes for files over 1GB in size and nearly every time for
+    files bigger than 10GB. This parameter controls the time rclone waits
+    for the file to appear.
 
--   Config: templink_threshold
--   Env Var: RCLONE_ACD_TEMPLINK_THRESHOLD
--   Type: SizeSuffix
--   Default: 9G
+    The default value for this parameter is 3 minutes per GB, so by
+    default it will wait 3 minutes for every GB uploaded to see if the
+    file appears.
 
-–acd-encoding
+    You can disable this feature by setting it to 0. This may cause
+    conflict errors as rclone retries the failed upload but the file will
+    most likely appear correctly eventually.
 
-This sets the encoding for the backend.
+    These values were determined empirically by observing lots of uploads
+    of big files for a range of file sizes.
 
-See: the encoding section in the overview for more info.
+    Upload with the "-v" flag to see more info about what rclone is doing
+    in this situation.
 
--   Config: encoding
--   Env Var: RCLONE_ACD_ENCODING
--   Type: MultiEncoder
--   Default: Slash,InvalidUtf8,Dot
+    - Config:      upload_wait_per_gb
+    - Env Var:     RCLONE_ACD_UPLOAD_WAIT_PER_GB
+    - Type:        Duration
+    - Default:     3m0s
 
-Limitations
+    #### --acd-templink-threshold
 
-Note that Amazon Drive is case insensitive so you can’t have a file
-called “Hello.doc” and one called “hello.doc”.
+    Files >= this size will be downloaded via their tempLink.
 
-Amazon Drive has rate limiting so you may notice errors in the sync (429
-errors). rclone will automatically retry the sync up to 3 times by
-default (see --retries flag) which should hopefully work around this
-problem.
+    Files this size or more will be downloaded via their "tempLink". This
+    is to work around a problem with Amazon Drive which blocks downloads
+    of files bigger than about 10GB.  The default for this is 9GB which
+    shouldn't need to be changed.
 
-Amazon Drive has an internal limit of file sizes that can be uploaded to
-the service. This limit is not officially published, but all files
-larger than this will fail.
+    To download files above this threshold, rclone requests a "tempLink"
+    which downloads the file through a temporary URL directly from the
+    underlying S3 storage.
 
-At the time of writing (Jan 2016) is in the area of 50GB per file. This
-means that larger files are likely to fail.
+    - Config:      templink_threshold
+    - Env Var:     RCLONE_ACD_TEMPLINK_THRESHOLD
+    - Type:        SizeSuffix
+    - Default:     9G
 
-Unfortunately there is no way for rclone to see that this failure is
-because of file size, so it will retry the operation, as any other
-failure. To avoid this problem, use --max-size 50000M option to limit
-the maximum size of uploaded files. Note that --max-size does not split
-files into segments, it only ignores files over this size.
-
-
-Amazon S3 Storage Providers
-
-The S3 backend can be used with a number of different providers:
-
--   AWS S3
--   Alibaba Cloud (Aliyun) Object Storage System (OSS)
--   Ceph
--   DigitalOcean Spaces
--   Dreamhost
--   IBM COS S3
--   Minio
--   Scaleway
--   StackPath
--   Wasabi
-
-Paths are specified as remote:bucket (or remote: for the lsd command.)
-You may put subdirectories in too, eg remote:bucket/path/to/dir.
-
-Once you have made a remote (see the provider specific section above)
-you can use it like this:
-
-See all buckets
-
-    rclone lsd remote:
-
-Make a new bucket
-
-    rclone mkdir remote:bucket
-
-List the contents of a bucket
-
-    rclone ls remote:bucket
-
-Sync /home/local/directory to the remote bucket, deleting any excess
-files in the bucket.
-
-    rclone sync /home/local/directory remote:bucket
-
-
-AWS S3
-
-Here is an example of making an s3 configuration. First run
-
-    rclone config
-
-This will guide you through an interactive setup process.
-
-    No remotes found - make a new one
-    n) New remote
-    s) Set configuration password
-    q) Quit config
-    n/s/q> n
-    name> remote
-    Type of storage to configure.
-    Choose a number from below, or type in your own value
-    [snip]
-    XX / Amazon S3 Compliant Storage Providers (AWS, Ceph, Dreamhost, IBM COS, Minio)
-       \ "s3"
-    [snip]
-    Storage> s3
-    Choose your S3 provider.
-    Choose a number from below, or type in your own value
-     1 / Amazon Web Services (AWS) S3
-       \ "AWS"
-     2 / Ceph Object Storage
-       \ "Ceph"
-     3 / Digital Ocean Spaces
-       \ "DigitalOcean"
-     4 / Dreamhost DreamObjects
-       \ "Dreamhost"
-     5 / IBM COS S3
-       \ "IBMCOS"
-     6 / Minio Object Storage
-       \ "Minio"
-     7 / Wasabi Object Storage
-       \ "Wasabi"
-     8 / Any other S3 compatible provider
-       \ "Other"
-    provider> 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
-       \ "false"
-     2 / Get AWS credentials from the environment (env vars or IAM)
-       \ "true"
-    env_auth> 1
-    AWS Access Key ID - leave blank for anonymous access or runtime credentials.
-    access_key_id> XXX
-    AWS Secret Access Key (password) - leave blank for anonymous access or runtime credentials.
-    secret_access_key> 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.
-       \ "us-east-1"
-       / US East (Ohio) Region
-     2 | Needs location constraint us-east-2.
-       \ "us-east-2"
-       / US West (Oregon) Region
-     3 | Needs location constraint us-west-2.
-       \ "us-west-2"
-       / US West (Northern California) Region
-     4 | Needs location constraint us-west-1.
-       \ "us-west-1"
-       / Canada (Central) Region
-     5 | Needs location constraint ca-central-1.
-       \ "ca-central-1"
-       / EU (Ireland) Region
-     6 | Needs location constraint EU or eu-west-1.
-       \ "eu-west-1"
-       / EU (London) Region
-     7 | Needs location constraint eu-west-2.
-       \ "eu-west-2"
-       / EU (Frankfurt) Region
-     8 | Needs location constraint eu-central-1.
-       \ "eu-central-1"
-       / Asia Pacific (Singapore) Region
-     9 | Needs location constraint ap-southeast-1.
-       \ "ap-southeast-1"
-       / Asia Pacific (Sydney) Region
-    10 | Needs location constraint ap-southeast-2.
-       \ "ap-southeast-2"
-       / Asia Pacific (Tokyo) Region
-    11 | Needs location constraint ap-northeast-1.
-       \ "ap-northeast-1"
-       / Asia Pacific (Seoul)
-    12 | Needs location constraint ap-northeast-2.
-       \ "ap-northeast-2"
-       / Asia Pacific (Mumbai)
-    13 | Needs location constraint ap-south-1.
-       \ "ap-south-1"
-       / Asia Patific (Hong Kong) Region
-    14 | Needs location constraint ap-east-1.
-       \ "ap-east-1"
-       / South America (Sao Paulo) Region
-    15 | Needs location constraint sa-east-1.
-       \ "sa-east-1"
-    region> 1
-    Endpoint for S3 API.
-    Leave blank if using AWS to use the default endpoint for the region.
-    endpoint> 
-    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.
-       \ ""
-     2 / US East (Ohio) Region.
-       \ "us-east-2"
-     3 / US West (Oregon) Region.
-       \ "us-west-2"
-     4 / US West (Northern California) Region.
-       \ "us-west-1"
-     5 / Canada (Central) Region.
-       \ "ca-central-1"
-     6 / EU (Ireland) Region.
-       \ "eu-west-1"
-     7 / EU (London) Region.
-       \ "eu-west-2"
-     8 / EU Region.
-       \ "EU"
-     9 / Asia Pacific (Singapore) Region.
-       \ "ap-southeast-1"
-    10 / Asia Pacific (Sydney) Region.
-       \ "ap-southeast-2"
-    11 / Asia Pacific (Tokyo) Region.
-       \ "ap-northeast-1"
-    12 / Asia Pacific (Seoul)
-       \ "ap-northeast-2"
-    13 / Asia Pacific (Mumbai)
-       \ "ap-south-1"
-    14 / Asia Pacific (Hong Kong)
-       \ "ap-east-1"
-    15 / South America (Sao Paulo) Region.
-       \ "sa-east-1"
-    location_constraint> 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).
-       \ "private"
-     2 / Owner gets FULL_CONTROL. The AllUsers group gets READ access.
-       \ "public-read"
-       / Owner gets FULL_CONTROL. The AllUsers group gets READ and WRITE access.
-     3 | Granting this on a bucket is generally not recommended.
-       \ "public-read-write"
-     4 / Owner gets FULL_CONTROL. The AuthenticatedUsers group gets READ access.
-       \ "authenticated-read"
-       / 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.
-       \ "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> 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
-       \ ""
-     2 / AES256
-       \ "AES256"
-    server_side_encryption> 1
-    The storage class to use when storing objects in S3.
-    Choose a number from below, or type in your own value
-     1 / Default
-       \ ""
-     2 / Standard storage class
-       \ "STANDARD"
-     3 / Reduced redundancy storage class
-       \ "REDUCED_REDUNDANCY"
-     4 / Standard Infrequent Access storage class
-       \ "STANDARD_IA"
-     5 / One Zone Infrequent Access storage class
-       \ "ONEZONE_IA"
-     6 / Glacier storage class
-       \ "GLACIER"
-     7 / Glacier Deep Archive storage class
-       \ "DEEP_ARCHIVE"
-     8 / Intelligent-Tiering storage class
-       \ "INTELLIGENT_TIERING"
-    storage_class> 1
-    Remote config
-    --------------------
-    [remote]
-    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 = 
-    --------------------
-    y) Yes this is OK
-    e) Edit this remote
-    d) Delete this remote
-    y/e/d> 
-
-–fast-list
-
-This remote supports --fast-list which allows you to use fewer
-transactions in exchange for more memory. See the rclone docs for more
-details.
-
-–update and –use-server-modtime
-
-As noted below, the modified time is stored on metadata on the object.
-It 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 because it requires an extra
-API call to retrieve the metadata.
-
-For many operations, the time the object was last uploaded to the remote
-is sufficient to determine if it is “dirty”. By using --update along
-with --use-server-modtime, you can avoid the extra API call and simply
-upload files whose local modtime is newer than the time it was last
-uploaded.
-
-Modified time
-
-The modified time is stored as metadata on the object as
-X-Amz-Meta-Mtime as floating point since the epoch accurate to 1 ns.
-
-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.
-
-Restricted filename characters
-
-S3 allows any valid UTF-8 string as a key.
-
-Invalid UTF-8 bytes will be replaced, as they can’t be used in XML.
-
-The following characters are replaced since these are problematic when
-dealing with the REST API:
-
-  Character    Value   Replacement
-  ----------- ------- -------------
-  NUL          0x00         ␀
-  /            0x2F        ／
-
-The encoding will also encode these file names as they don’t seem to
-work with the SDK properly:
-
-  File name    Replacement
-  ----------- -------------
-  .                ．
-  ..              ．．
-
-Multipart uploads
-
-rclone supports multipart uploads with S3 which means that it can upload
-files bigger than 5GB.
-
-Note that files uploaded _both_ with multipart upload _and_ through
-crypt remotes do not have MD5 sums.
-
-rclone switches from single part uploads to multipart uploads at the
-point specified by --s3-upload-cutoff. This can be a maximum of 5GB and
-a minimum of 0 (ie always upload multipart files).
-
-The chunk sizes used in the multipart upload are specified by
---s3-chunk-size and the number of chunks uploaded concurrently is
-specified by --s3-upload-concurrency.
-
-Multipart uploads will use --transfers * --s3-upload-concurrency *
---s3-chunk-size extra memory. Single part uploads to not use extra
-memory.
-
-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.
-
-Increasing --s3-upload-concurrency will increase throughput (8 would be
-a sensible value) and increasing --s3-chunk-size 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.
-
-Buckets and Regions
-
-With Amazon S3 you can list buckets (rclone lsd) 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, incorrect region, the bucket is not in 'XXX' region.
-
-Authentication
-
-There are a number of ways to supply rclone with a set of AWS
-credentials, with and without using the environment.
-
-The different authentication methods are tried in this order:
-
--   Directly in the rclone configuration file (env_auth = false in the
-    config file):
-    -   access_key_id and secret_access_key are required.
-    -   session_token can be optionally set when using AWS STS.
--   Runtime configuration (env_auth = true in the config file):
-    -   Export the following environment variables before running
-        rclone:
-        -   Access Key ID: AWS_ACCESS_KEY_ID or AWS_ACCESS_KEY
-        -   Secret Access Key: AWS_SECRET_ACCESS_KEY or AWS_SECRET_KEY
-        -   Session Token: AWS_SESSION_TOKEN (optional)
-    -   Or, use a named profile:
-        -   Profile files are standard files used by AWS CLI tools
-        -   By default it will use the profile in your home directory
-            (eg ~/.aws/credentials on unix based systems) file and the
-            “default” profile, to change set these environment
-            variables:
-            -   AWS_SHARED_CREDENTIALS_FILE to control which file.
-            -   AWS_PROFILE to control which profile to use.
-    -   Or, run rclone in an ECS task with an IAM role (AWS only).
-    -   Or, run rclone on an EC2 instance with an IAM role (AWS only).
-    -   Or, run rclone in an EKS pod with an IAM role that is associated
-        with a service account (AWS only).
-
-If none of these option actually end up providing rclone with AWS
-credentials then S3 interaction will be non-authenticated (see below).
-
-S3 Permissions
-
-When using the sync subcommand of rclone the following minimum
-permissions are required to be available on the bucket being written to:
-
--   ListBucket
--   DeleteObject
--   GetObject
--   PutObject
--   PutObjectACL
-
-When using the lsd subcommand, the ListAllMyBuckets permission is
-required.
-
-Example policy:
-
-    {
-        "Version": "2012-10-17",
-        "Statement": [
-            {
-                "Effect": "Allow",
-                "Principal": {
-                    "AWS": "arn:aws:iam::USER_SID:user/USER_NAME"
-                },
-                "Action": [
-                    "s3:ListBucket",
-                    "s3:DeleteObject",
-                    "s3:GetObject",
-                    "s3:PutObject",
-                    "s3:PutObjectAcl"
-                ],
-                "Resource": [
-                  "arn:aws:s3:::BUCKET_NAME/*",
-                  "arn:aws:s3:::BUCKET_NAME"
-                ]
-            },
-            {
-                "Effect": "Allow",
-                "Action": "s3:ListAllMyBuckets",
-                "Resource": "arn:aws:s3:::*"
-            }   
-        ]
-    }
-
-Notes on above:
-
-1.  This is a policy that can be used when creating bucket. It assumes
-    that USER_NAME has been created.
-2.  The Resource entry must include both resource ARNs, as one implies
-    the bucket and the other implies the bucket’s objects.
-
-For reference, here’s an Ansible script that will generate one or more
-buckets that will work with rclone sync.
-
-Key Management System (KMS)
-
-If you are using server side encryption with KMS then you will find you
-can’t transfer small objects. As a work-around you can use the
---ignore-checksum flag.
-
-A proper fix is being worked on in issue #1824.
-
-Glacier and Glacier Deep Archive
-
-You can upload objects using the glacier storage class or transition
-them to glacier using a lifecycle policy. 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.
-
-    2017/09/11 19:07:43 Failed to sync: failed to open source object: Object in GLACIER, restore first: path/to/file
-
-In this case you need to restore the object(s) in question before using
-rclone.
-
-Note that rclone only speaks the S3 API it does not speak the Glacier
-Vault API, so rclone cannot directly access Glacier Vaults.
-
-Standard Options
-
-Here are the standard options specific to s3 (Amazon S3 Compliant
-Storage Provider (AWS, Alibaba, Ceph, Digital Ocean, Dreamhost, IBM COS,
-Minio, etc)).
-
-–s3-provider
-
-Choose your S3 provider.
-
--   Config: provider
--   Env Var: RCLONE_S3_PROVIDER
--   Type: string
--   Default: ""
--   Examples:
-    -   “AWS”
-        -   Amazon Web Services (AWS) S3
-    -   “Alibaba”
-        -   Alibaba Cloud Object Storage System (OSS) formerly Aliyun
-    -   “Ceph”
-        -   Ceph Object Storage
-    -   “DigitalOcean”
-        -   Digital Ocean Spaces
-    -   “Dreamhost”
-        -   Dreamhost DreamObjects
-    -   “IBMCOS”
-        -   IBM COS S3
-    -   “Minio”
-        -   Minio Object Storage
-    -   “Netease”
-        -   Netease Object Storage (NOS)
-    -   “StackPath”
-        -   StackPath Object Storage
-    -   “Wasabi”
-        -   Wasabi Object Storage
-    -   “Other”
-        -   Any other S3 compatible provider
-
-–s3-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.
-
--   Config: env_auth
--   Env Var: RCLONE_S3_ENV_AUTH
--   Type: bool
--   Default: false
--   Examples:
-    -   “false”
-        -   Enter AWS credentials in the next step
-    -   “true”
-        -   Get AWS credentials from the environment (env vars or IAM)
-
-–s3-access-key-id
-
-AWS Access Key ID. Leave blank for anonymous access or runtime
-credentials.
-
--   Config: access_key_id
--   Env Var: RCLONE_S3_ACCESS_KEY_ID
--   Type: string
--   Default: ""
-
-–s3-secret-access-key
-
-AWS Secret Access Key (password) Leave blank for anonymous access or
-runtime credentials.
-
--   Config: secret_access_key
--   Env Var: RCLONE_S3_SECRET_ACCESS_KEY
--   Type: string
--   Default: ""
-
-–s3-region
-
-Region to connect to.
-
--   Config: region
--   Env Var: RCLONE_S3_REGION
--   Type: string
--   Default: ""
--   Examples:
-    -   “us-east-1”
-        -   The default endpoint - a good choice if you are unsure.
-        -   US Region, Northern Virginia or Pacific Northwest.
-        -   Leave location constraint empty.
-    -   “us-east-2”
-        -   US East (Ohio) Region
-        -   Needs location constraint us-east-2.
-    -   “us-west-2”
-        -   US West (Oregon) Region
-        -   Needs location constraint us-west-2.
-    -   “us-west-1”
-        -   US West (Northern California) Region
-        -   Needs location constraint us-west-1.
-    -   “ca-central-1”
-        -   Canada (Central) Region
-        -   Needs location constraint ca-central-1.
-    -   “eu-west-1”
-        -   EU (Ireland) Region
-        -   Needs location constraint EU or eu-west-1.
-    -   “eu-west-2”
-        -   EU (London) Region
-        -   Needs location constraint eu-west-2.
-    -   “eu-north-1”
-        -   EU (Stockholm) Region
-        -   Needs location constraint eu-north-1.
-    -   “eu-central-1”
-        -   EU (Frankfurt) Region
-        -   Needs location constraint eu-central-1.
-    -   “ap-southeast-1”
-        -   Asia Pacific (Singapore) Region
-        -   Needs location constraint ap-southeast-1.
-    -   “ap-southeast-2”
-        -   Asia Pacific (Sydney) Region
-        -   Needs location constraint ap-southeast-2.
-    -   “ap-northeast-1”
-        -   Asia Pacific (Tokyo) Region
-        -   Needs location constraint ap-northeast-1.
-    -   “ap-northeast-2”
-        -   Asia Pacific (Seoul)
-        -   Needs location constraint ap-northeast-2.
-    -   “ap-south-1”
-        -   Asia Pacific (Mumbai)
-        -   Needs location constraint ap-south-1.
-    -   “ap-east-1”
-        -   Asia Patific (Hong Kong) Region
-        -   Needs location constraint ap-east-1.
-    -   “sa-east-1”
-        -   South America (Sao Paulo) Region
-        -   Needs location constraint sa-east-1.
-
-–s3-region
-
-Region to connect to. Leave blank if you are using an S3 clone and you
-don’t have a region.
-
--   Config: region
--   Env Var: RCLONE_S3_REGION
--   Type: string
--   Default: ""
--   Examples:
-    -   ""
-        -   Use this if unsure. Will use v4 signatures and an empty
-            region.
-    -   “other-v2-signature”
-        -   Use this only if v4 signatures don’t work, eg pre Jewel/v10
-            CEPH.
-
-–s3-endpoint
+    #### --acd-encoding
 
+    This sets the encoding for the backend.
+
+    See: the [encoding section in the overview](https://rclone.org/overview/#encoding) for more info.
+
+    - Config:      encoding
+    - Env Var:     RCLONE_ACD_ENCODING
+    - Type:        MultiEncoder
+    - Default:     Slash,InvalidUtf8,Dot
+
+
+
+    ### Limitations ###
+
+    Note that Amazon Drive is case insensitive so you can't have a
+    file called "Hello.doc" and one called "hello.doc".
+
+    Amazon Drive has rate limiting so you may notice errors in the
+    sync (429 errors).  rclone will automatically retry the sync up to 3
+    times by default (see `--retries` flag) which should hopefully work
+    around this problem.
+
+    Amazon Drive has an internal limit of file sizes that can be uploaded
+    to the service. This limit is not officially published, but all files
+    larger than this will fail.
+
+    At the time of writing (Jan 2016) is in the area of 50GB per file.
+    This means that larger files are likely to fail.
+
+    Unfortunately there is no way for rclone to see that this failure is
+    because of file size, so it will retry the operation, as any other
+    failure. To avoid this problem, use `--max-size 50000M` option to limit
+    the maximum size of uploaded files. Note that `--max-size` does not split
+    files into segments, it only ignores files over this size.
+
+     Amazon S3 Storage Providers
+    --------------------------------------------------------
+
+    The S3 backend can be used with a number of different providers:
+
+
+    - AWS S3
+    - Alibaba Cloud (Aliyun) Object Storage System (OSS)
+    - Ceph
+    - DigitalOcean Spaces
+    - Dreamhost
+    - IBM COS S3
+    - Minio
+    - Scaleway
+    - StackPath
+    - Wasabi
+
+
+    Paths are specified as `remote:bucket` (or `remote:` for the `lsd`
+    command.)  You may put subdirectories in too, eg `remote:bucket/path/to/dir`.
+
+    Once you have made a remote (see the provider specific section above)
+    you can use it like this:
+
+    See all buckets
+
+        rclone lsd remote:
+
+    Make a new bucket
+
+        rclone mkdir remote:bucket
+
+    List the contents of a bucket
+
+        rclone ls remote:bucket
+
+    Sync `/home/local/directory` to the remote bucket, deleting any excess
+    files in the bucket.
+
+        rclone sync -i /home/local/directory remote:bucket
+
+    ## AWS S3 {#amazon-s3}
+
+    Here is an example of making an s3 configuration.  First run
+
+        rclone config
+
+    This will guide you through an interactive setup process.
+
+No remotes found - make a new one n) New remote s) Set configuration
+password q) Quit config n/s/q> n name> remote Type of storage to
+configure. Choose a number from below, or type in your own value [snip]
+XX / Amazon S3 Compliant Storage Providers (AWS, Ceph, Dreamhost, IBM
+COS, Minio)  "s3" [snip] Storage> s3 Choose your S3 provider. Choose a
+number from below, or type in your own value 1 / Amazon Web Services
+(AWS) S3  "AWS" 2 / Ceph Object Storage  "Ceph" 3 / Digital Ocean Spaces
+ "DigitalOcean" 4 / Dreamhost DreamObjects  "Dreamhost" 5 / IBM COS S3
+ "IBMCOS" 6 / Minio Object Storage  "Minio" 7 / Wasabi Object Storage
+ "Wasabi" 8 / Any other S3 compatible provider  "Other" provider> 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  "false" 2 / Get AWS credentials from
+the environment (env vars or IAM)  "true" env_auth> 1 AWS Access Key ID
+- leave blank for anonymous access or runtime credentials.
+access_key_id> XXX AWS Secret Access Key (password) - leave blank for
+anonymous access or runtime credentials. secret_access_key> 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.  "us-east-1" / US East (Ohio) Region 2 | Needs location
+constraint us-east-2.  "us-east-2" / US West (Oregon) Region 3 | Needs
+location constraint us-west-2.  "us-west-2" / US West (Northern
+California) Region 4 | Needs location constraint us-west-1.  "us-west-1"
+/ Canada (Central) Region 5 | Needs location constraint ca-central-1.
+ "ca-central-1" / EU (Ireland) Region 6 | Needs location constraint EU
+or eu-west-1.  "eu-west-1" / EU (London) Region 7 | Needs location
+constraint eu-west-2.  "eu-west-2" / EU (Frankfurt) Region 8 | Needs
+location constraint eu-central-1.  "eu-central-1" / Asia Pacific
+(Singapore) Region 9 | Needs location constraint ap-southeast-1.
+ "ap-southeast-1" / Asia Pacific (Sydney) Region 10 | Needs location
+constraint ap-southeast-2.  "ap-southeast-2" / Asia Pacific (Tokyo)
+Region 11 | Needs location constraint ap-northeast-1.  "ap-northeast-1"
+/ Asia Pacific (Seoul) 12 | Needs location constraint ap-northeast-2.
+ "ap-northeast-2" / Asia Pacific (Mumbai) 13 | Needs location constraint
+ap-south-1.  "ap-south-1" / Asia Patific (Hong Kong) Region 14 | Needs
+location constraint ap-east-1.  "ap-east-1" / South America (Sao Paulo)
+Region 15 | Needs location constraint sa-east-1.  "sa-east-1" region> 1
 Endpoint for S3 API. Leave blank if using AWS to use the default
-endpoint for the region.
-
--   Config: endpoint
--   Env Var: RCLONE_S3_ENDPOINT
--   Type: string
--   Default: ""
-
-–s3-endpoint
-
-Endpoint for IBM COS S3 API. Specify if using an IBM COS On Premise.
-
--   Config: endpoint
--   Env Var: RCLONE_S3_ENDPOINT
--   Type: string
--   Default: ""
--   Examples:
-    -   “s3-api.us-geo.objectstorage.softlayer.net”
-        -   US Cross Region Endpoint
-    -   “s3-api.dal.us-geo.objectstorage.softlayer.net”
-        -   US Cross Region Dallas Endpoint
-    -   “s3-api.wdc-us-geo.objectstorage.softlayer.net”
-        -   US Cross Region Washington DC Endpoint
-    -   “s3-api.sjc-us-geo.objectstorage.softlayer.net”
-        -   US Cross Region San Jose Endpoint
-    -   “s3-api.us-geo.objectstorage.service.networklayer.com”
-        -   US Cross Region Private Endpoint
-    -   “s3-api.dal-us-geo.objectstorage.service.networklayer.com”
-        -   US Cross Region Dallas Private Endpoint
-    -   “s3-api.wdc-us-geo.objectstorage.service.networklayer.com”
-        -   US Cross Region Washington DC Private Endpoint
-    -   “s3-api.sjc-us-geo.objectstorage.service.networklayer.com”
-        -   US Cross Region San Jose Private Endpoint
-    -   “s3.us-east.objectstorage.softlayer.net”
-        -   US Region East Endpoint
-    -   “s3.us-east.objectstorage.service.networklayer.com”
-        -   US Region East Private Endpoint
-    -   “s3.us-south.objectstorage.softlayer.net”
-        -   US Region South Endpoint
-    -   “s3.us-south.objectstorage.service.networklayer.com”
-        -   US Region South Private Endpoint
-    -   “s3.eu-geo.objectstorage.softlayer.net”
-        -   EU Cross Region Endpoint
-    -   “s3.fra-eu-geo.objectstorage.softlayer.net”
-        -   EU Cross Region Frankfurt Endpoint
-    -   “s3.mil-eu-geo.objectstorage.softlayer.net”
-        -   EU Cross Region Milan Endpoint
-    -   “s3.ams-eu-geo.objectstorage.softlayer.net”
-        -   EU Cross Region Amsterdam Endpoint
-    -   “s3.eu-geo.objectstorage.service.networklayer.com”
-        -   EU Cross Region Private Endpoint
-    -   “s3.fra-eu-geo.objectstorage.service.networklayer.com”
-        -   EU Cross Region Frankfurt Private Endpoint
-    -   “s3.mil-eu-geo.objectstorage.service.networklayer.com”
-        -   EU Cross Region Milan Private Endpoint
-    -   “s3.ams-eu-geo.objectstorage.service.networklayer.com”
-        -   EU Cross Region Amsterdam Private Endpoint
-    -   “s3.eu-gb.objectstorage.softlayer.net”
-        -   Great Britain Endpoint
-    -   “s3.eu-gb.objectstorage.service.networklayer.com”
-        -   Great Britain Private Endpoint
-    -   “s3.ap-geo.objectstorage.softlayer.net”
-        -   APAC Cross Regional Endpoint
-    -   “s3.tok-ap-geo.objectstorage.softlayer.net”
-        -   APAC Cross Regional Tokyo Endpoint
-    -   “s3.hkg-ap-geo.objectstorage.softlayer.net”
-        -   APAC Cross Regional HongKong Endpoint
-    -   “s3.seo-ap-geo.objectstorage.softlayer.net”
-        -   APAC Cross Regional Seoul Endpoint
-    -   “s3.ap-geo.objectstorage.service.networklayer.com”
-        -   APAC Cross Regional Private Endpoint
-    -   “s3.tok-ap-geo.objectstorage.service.networklayer.com”
-        -   APAC Cross Regional Tokyo Private Endpoint
-    -   “s3.hkg-ap-geo.objectstorage.service.networklayer.com”
-        -   APAC Cross Regional HongKong Private Endpoint
-    -   “s3.seo-ap-geo.objectstorage.service.networklayer.com”
-        -   APAC Cross Regional Seoul Private Endpoint
-    -   “s3.mel01.objectstorage.softlayer.net”
-        -   Melbourne Single Site Endpoint
-    -   “s3.mel01.objectstorage.service.networklayer.com”
-        -   Melbourne Single Site Private Endpoint
-    -   “s3.tor01.objectstorage.softlayer.net”
-        -   Toronto Single Site Endpoint
-    -   “s3.tor01.objectstorage.service.networklayer.com”
-        -   Toronto Single Site Private Endpoint
-
-–s3-endpoint
-
-Endpoint for OSS API.
-
--   Config: endpoint
--   Env Var: RCLONE_S3_ENDPOINT
--   Type: string
--   Default: ""
--   Examples:
-    -   “oss-cn-hangzhou.aliyuncs.com”
-        -   East China 1 (Hangzhou)
-    -   “oss-cn-shanghai.aliyuncs.com”
-        -   East China 2 (Shanghai)
-    -   “oss-cn-qingdao.aliyuncs.com”
-        -   North China 1 (Qingdao)
-    -   “oss-cn-beijing.aliyuncs.com”
-        -   North China 2 (Beijing)
-    -   “oss-cn-zhangjiakou.aliyuncs.com”
-        -   North China 3 (Zhangjiakou)
-    -   “oss-cn-huhehaote.aliyuncs.com”
-        -   North China 5 (Huhehaote)
-    -   “oss-cn-shenzhen.aliyuncs.com”
-        -   South China 1 (Shenzhen)
-    -   “oss-cn-hongkong.aliyuncs.com”
-        -   Hong Kong (Hong Kong)
-    -   “oss-us-west-1.aliyuncs.com”
-        -   US West 1 (Silicon Valley)
-    -   “oss-us-east-1.aliyuncs.com”
-        -   US East 1 (Virginia)
-    -   “oss-ap-southeast-1.aliyuncs.com”
-        -   Southeast Asia Southeast 1 (Singapore)
-    -   “oss-ap-southeast-2.aliyuncs.com”
-        -   Asia Pacific Southeast 2 (Sydney)
-    -   “oss-ap-southeast-3.aliyuncs.com”
-        -   Southeast Asia Southeast 3 (Kuala Lumpur)
-    -   “oss-ap-southeast-5.aliyuncs.com”
-        -   Asia Pacific Southeast 5 (Jakarta)
-    -   “oss-ap-northeast-1.aliyuncs.com”
-        -   Asia Pacific Northeast 1 (Japan)
-    -   “oss-ap-south-1.aliyuncs.com”
-        -   Asia Pacific South 1 (Mumbai)
-    -   “oss-eu-central-1.aliyuncs.com”
-        -   Central Europe 1 (Frankfurt)
-    -   “oss-eu-west-1.aliyuncs.com”
-        -   West Europe (London)
-    -   “oss-me-east-1.aliyuncs.com”
-        -   Middle East 1 (Dubai)
-
-–s3-endpoint
-
-Endpoint for StackPath Object Storage.
-
--   Config: endpoint
--   Env Var: RCLONE_S3_ENDPOINT
--   Type: string
--   Default: ""
--   Examples:
-    -   “s3.us-east-2.stackpathstorage.com”
-        -   US East Endpoint
-    -   “s3.us-west-1.stackpathstorage.com”
-        -   US West Endpoint
-    -   “s3.eu-central-1.stackpathstorage.com”
-        -   EU Endpoint
-
-–s3-endpoint
-
-Endpoint for S3 API. Required when using an S3 clone.
-
--   Config: endpoint
--   Env Var: RCLONE_S3_ENDPOINT
--   Type: string
--   Default: ""
--   Examples:
-    -   “objects-us-east-1.dream.io”
-        -   Dream Objects endpoint
-    -   “nyc3.digitaloceanspaces.com”
-        -   Digital Ocean Spaces New York 3
-    -   “ams3.digitaloceanspaces.com”
-        -   Digital Ocean Spaces Amsterdam 3
-    -   “sgp1.digitaloceanspaces.com”
-        -   Digital Ocean Spaces Singapore 1
-    -   “s3.wasabisys.com”
-        -   Wasabi US East endpoint
-    -   “s3.us-west-1.wasabisys.com”
-        -   Wasabi US West endpoint
-    -   “s3.eu-central-1.wasabisys.com”
-        -   Wasabi EU Central endpoint
-
-–s3-location-constraint
-
-Location constraint - must be set to match the Region. Used when
-creating buckets only.
-
--   Config: location_constraint
--   Env Var: RCLONE_S3_LOCATION_CONSTRAINT
--   Type: string
--   Default: ""
--   Examples:
-    -   ""
-        -   Empty for US Region, Northern Virginia or Pacific Northwest.
-    -   “us-east-2”
-        -   US East (Ohio) Region.
-    -   “us-west-2”
-        -   US West (Oregon) Region.
-    -   “us-west-1”
-        -   US West (Northern California) Region.
-    -   “ca-central-1”
-        -   Canada (Central) Region.
-    -   “eu-west-1”
-        -   EU (Ireland) Region.
-    -   “eu-west-2”
-        -   EU (London) Region.
-    -   “eu-north-1”
-        -   EU (Stockholm) Region.
-    -   “EU”
-        -   EU Region.
-    -   “ap-southeast-1”
-        -   Asia Pacific (Singapore) Region.
-    -   “ap-southeast-2”
-        -   Asia Pacific (Sydney) Region.
-    -   “ap-northeast-1”
-        -   Asia Pacific (Tokyo) Region.
-    -   “ap-northeast-2”
-        -   Asia Pacific (Seoul)
-    -   “ap-south-1”
-        -   Asia Pacific (Mumbai)
-    -   “ap-east-1”
-        -   Asia Pacific (Hong Kong)
-    -   “sa-east-1”
-        -   South America (Sao Paulo) Region.
-
-–s3-location-constraint
-
-Location constraint - must match endpoint when using IBM Cloud Public.
-For on-prem COS, do not make a selection from this list, hit enter
-
--   Config: location_constraint
--   Env Var: RCLONE_S3_LOCATION_CONSTRAINT
--   Type: string
--   Default: ""
--   Examples:
-    -   “us-standard”
-        -   US Cross Region Standard
-    -   “us-vault”
-        -   US Cross Region Vault
-    -   “us-cold”
-        -   US Cross Region Cold
-    -   “us-flex”
-        -   US Cross Region Flex
-    -   “us-east-standard”
-        -   US East Region Standard
-    -   “us-east-vault”
-        -   US East Region Vault
-    -   “us-east-cold”
-        -   US East Region Cold
-    -   “us-east-flex”
-        -   US East Region Flex
-    -   “us-south-standard”
-        -   US South Region Standard
-    -   “us-south-vault”
-        -   US South Region Vault
-    -   “us-south-cold”
-        -   US South Region Cold
-    -   “us-south-flex”
-        -   US South Region Flex
-    -   “eu-standard”
-        -   EU Cross Region Standard
-    -   “eu-vault”
-        -   EU Cross Region Vault
-    -   “eu-cold”
-        -   EU Cross Region Cold
-    -   “eu-flex”
-        -   EU Cross Region Flex
-    -   “eu-gb-standard”
-        -   Great Britain Standard
-    -   “eu-gb-vault”
-        -   Great Britain Vault
-    -   “eu-gb-cold”
-        -   Great Britain Cold
-    -   “eu-gb-flex”
-        -   Great Britain Flex
-    -   “ap-standard”
-        -   APAC Standard
-    -   “ap-vault”
-        -   APAC Vault
-    -   “ap-cold”
-        -   APAC Cold
-    -   “ap-flex”
-        -   APAC Flex
-    -   “mel01-standard”
-        -   Melbourne Standard
-    -   “mel01-vault”
-        -   Melbourne Vault
-    -   “mel01-cold”
-        -   Melbourne Cold
-    -   “mel01-flex”
-        -   Melbourne Flex
-    -   “tor01-standard”
-        -   Toronto Standard
-    -   “tor01-vault”
-        -   Toronto Vault
-    -   “tor01-cold”
-        -   Toronto Cold
-    -   “tor01-flex”
-        -   Toronto Flex
-
-–s3-location-constraint
-
-Location constraint - must be set to match the Region. Leave blank if
-not sure. Used when creating buckets only.
-
--   Config: location_constraint
--   Env Var: RCLONE_S3_LOCATION_CONSTRAINT
--   Type: string
--   Default: ""
-
-–s3-acl
-
-Canned ACL used when creating buckets and storing or copying objects.
-
-This ACL is used for creating objects and if bucket_acl isn’t set, for
-creating buckets too.
-
-For more info visit
+endpoint for the region. endpoint> 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.  "" 2 / US East (Ohio) Region.
+ "us-east-2" 3 / US West (Oregon) Region.  "us-west-2" 4 / US West
+(Northern California) Region.  "us-west-1" 5 / Canada (Central) Region.
+ "ca-central-1" 6 / EU (Ireland) Region.  "eu-west-1" 7 / EU (London)
+Region.  "eu-west-2" 8 / EU Region.  "EU" 9 / Asia Pacific (Singapore)
+Region.  "ap-southeast-1" 10 / Asia Pacific (Sydney) Region.
+ "ap-southeast-2" 11 / Asia Pacific (Tokyo) Region.  "ap-northeast-1" 12
+/ Asia Pacific (Seoul)  "ap-northeast-2" 13 / Asia Pacific (Mumbai)
+ "ap-south-1" 14 / Asia Pacific (Hong Kong)  "ap-east-1" 15 / South
+America (Sao Paulo) Region.  "sa-east-1" location_constraint> 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).  "private" 2 /
+Owner gets FULL_CONTROL. The AllUsers group gets READ access.
+ "public-read" / Owner gets FULL_CONTROL. The AllUsers group gets READ
+and WRITE access. 3 | Granting this on a bucket is generally not
+recommended.  "public-read-write" 4 / Owner gets FULL_CONTROL. The
+AuthenticatedUsers group gets READ access.  "authenticated-read" /
+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.  "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> 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  "" 2 / AES256  "AES256"
+server_side_encryption> 1 The storage class to use when storing objects
+in S3. Choose a number from below, or type in your own value 1 / Default
+ "" 2 / Standard storage class  "STANDARD" 3 / Reduced redundancy
+storage class  "REDUCED_REDUNDANCY" 4 / Standard Infrequent Access
+storage class  "STANDARD_IA" 5 / One Zone Infrequent Access storage
+class  "ONEZONE_IA" 6 / Glacier storage class  "GLACIER" 7 / Glacier
+Deep Archive storage class  "DEEP_ARCHIVE" 8 / Intelligent-Tiering
+storage class  "INTELLIGENT_TIERING" storage_class> 1 Remote config
+-------------------- [remote] 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 = -------------------- y) Yes this is OK e) Edit this
+remote d) Delete this remote y/e/d>
+
+
+    ### --fast-list ###
+
+    This remote supports `--fast-list` which allows you to use fewer
+    transactions in exchange for more memory. See the [rclone
+    docs](https://rclone.org/docs/#fast-list) for more details.
+
+    ### --update and --use-server-modtime ###
+
+    As noted below, the modified time is stored on metadata on the object. It 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 because it requires an extra API call to retrieve the
+    metadata.
+
+    For many operations, the time the object was last uploaded to the remote is
+    sufficient to determine if it is "dirty". By using `--update` along with
+    `--use-server-modtime`, you can avoid the extra API call and simply upload
+    files whose local modtime is newer than the time it was last uploaded.
+
+    ### Modified time ###
+
+    The modified time is stored as metadata on the object as
+    `X-Amz-Meta-Mtime` as floating point since the epoch accurate to 1 ns.
+
+    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.
+
+    ### Cleanup ###
+
+    If you run `rclone cleanup s3:bucket` then it will remove all pending
+    multipart uploads older than 24 hours. You can use the `-i` flag to
+    see exactly what it will do. If you want more control over the expiry
+    date then run `rclone backend cleanup s3:bucket -o max-age=1h` to
+    expire all uploads older than one hour. You can use `rclone backend
+    list-multipart-uploads s3:bucket` to see the pending multipart
+    uploads.
+
+    #### Restricted filename characters
+
+    S3 allows any valid UTF-8 string as a key.
+
+    Invalid UTF-8 bytes will be [replaced](https://rclone.org/overview/#invalid-utf8), as
+    they can't be used in XML.
+
+    The following characters are replaced since these are problematic when
+    dealing with the REST API:
+
+    | Character | Value | Replacement |
+    | --------- |:-----:|:-----------:|
+    | NUL       | 0x00  | ␀           |
+    | /         | 0x2F  | ／           |
+
+    The encoding will also encode these file names as they don't seem to
+    work with the SDK properly:
+
+    | File name | Replacement |
+    | --------- |:-----------:|
+    | .         | ．          |
+    | ..        | ．．         |
+
+    ### Multipart uploads ###
+
+    rclone supports multipart uploads with S3 which means that it can
+    upload files bigger than 5GB.
+
+    Note that files uploaded *both* with multipart upload *and* through
+    crypt remotes do not have MD5 sums.
+
+    rclone switches from single part uploads to multipart uploads at the
+    point specified by `--s3-upload-cutoff`.  This can be a maximum of 5GB
+    and a minimum of 0 (ie always upload multipart files).
+
+    The chunk sizes used in the multipart upload are specified by
+    `--s3-chunk-size` and the number of chunks uploaded concurrently is
+    specified by `--s3-upload-concurrency`.
 
-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.
-
--   Config: acl
--   Env Var: RCLONE_S3_ACL
--   Type: string
--   Default: ""
--   Examples:
-    -   “private”
-        -   Owner gets FULL_CONTROL. No one else has access rights
-            (default).
-    -   “public-read”
-        -   Owner gets FULL_CONTROL. The AllUsers group gets READ
-            access.
-    -   “public-read-write”
-        -   Owner gets FULL_CONTROL. The AllUsers group gets READ and
-            WRITE access.
-        -   Granting this on a bucket is generally not recommended.
-    -   “authenticated-read”
-        -   Owner gets FULL_CONTROL. The AuthenticatedUsers group gets
-            READ access.
-    -   “bucket-owner-read”
-        -   Object owner gets FULL_CONTROL. Bucket owner gets READ
-            access.
-        -   If you specify this canned ACL when creating a bucket,
-            Amazon S3 ignores it.
-    -   “bucket-owner-full-control”
-        -   Both the object owner and the bucket owner get FULL_CONTROL
-            over the object.
-        -   If you specify this canned ACL when creating a bucket,
-            Amazon S3 ignores it.
-    -   “private”
-        -   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
-    -   “public-read”
-        -   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
-    -   “public-read-write”
-        -   Owner gets FULL_CONTROL. The AllUsers group gets READ and
-            WRITE access. This acl is available on IBM Cloud (Infra),
-            On-Premise IBM COS
-    -   “authenticated-read”
-        -   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
-
-–s3-server-side-encryption
-
-The server-side encryption algorithm used when storing this object in
-S3.
-
--   Config: server_side_encryption
--   Env Var: RCLONE_S3_SERVER_SIDE_ENCRYPTION
--   Type: string
--   Default: ""
--   Examples:
-    -   ""
-        -   None
-    -   “AES256”
-        -   AES256
-    -   “aws:kms”
-        -   aws:kms
-
-–s3-sse-kms-key-id
-
-If using KMS ID you must provide the ARN of Key.
-
--   Config: sse_kms_key_id
--   Env Var: RCLONE_S3_SSE_KMS_KEY_ID
--   Type: string
--   Default: ""
--   Examples:
-    -   ""
-        -   None
-    -   "arn:aws:kms:us-east-1:*"
-        -   arn:aws:kms:*
-
-–s3-storage-class
-
-The storage class to use when storing new objects in S3.
-
--   Config: storage_class
--   Env Var: RCLONE_S3_STORAGE_CLASS
--   Type: string
--   Default: ""
--   Examples:
-    -   ""
-        -   Default
-    -   “STANDARD”
-        -   Standard storage class
-    -   “REDUCED_REDUNDANCY”
-        -   Reduced redundancy storage class
-    -   “STANDARD_IA”
-        -   Standard Infrequent Access storage class
-    -   “ONEZONE_IA”
-        -   One Zone Infrequent Access storage class
-    -   “GLACIER”
-        -   Glacier storage class
-    -   “DEEP_ARCHIVE”
-        -   Glacier Deep Archive storage class
-    -   “INTELLIGENT_TIERING”
-        -   Intelligent-Tiering storage class
-
-–s3-storage-class
-
-The storage class to use when storing new objects in OSS.
-
--   Config: storage_class
--   Env Var: RCLONE_S3_STORAGE_CLASS
--   Type: string
--   Default: ""
--   Examples:
-    -   ""
-        -   Default
-    -   “STANDARD”
-        -   Standard storage class
-    -   “GLACIER”
-        -   Archive storage mode.
-    -   “STANDARD_IA”
-        -   Infrequent access storage mode.
-
-Advanced Options
-
-Here are the advanced options specific to s3 (Amazon S3 Compliant
-Storage Provider (AWS, Alibaba, Ceph, Digital Ocean, Dreamhost, IBM COS,
-Minio, etc)).
-
-–s3-bucket-acl
-
-Canned ACL used when creating buckets.
-
-For more info visit
-https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html#canned-acl
-
-Note that this ACL is applied when only when creating buckets. If it
-isn’t set then “acl” is used instead.
-
--   Config: bucket_acl
--   Env Var: RCLONE_S3_BUCKET_ACL
--   Type: string
--   Default: ""
--   Examples:
-    -   “private”
-        -   Owner gets FULL_CONTROL. No one else has access rights
-            (default).
-    -   “public-read”
-        -   Owner gets FULL_CONTROL. The AllUsers group gets READ
-            access.
-    -   “public-read-write”
-        -   Owner gets FULL_CONTROL. The AllUsers group gets READ and
-            WRITE access.
-        -   Granting this on a bucket is generally not recommended.
-    -   “authenticated-read”
-        -   Owner gets FULL_CONTROL. The AuthenticatedUsers group gets
-            READ access.
-
-–s3-sse-customer-algorithm
-
-If using SSE-C, the server-side encryption algorithm used when storing
-this object in S3.
-
--   Config: sse_customer_algorithm
--   Env Var: RCLONE_S3_SSE_CUSTOMER_ALGORITHM
--   Type: string
--   Default: ""
--   Examples:
-    -   ""
-        -   None
-    -   “AES256”
-        -   AES256
-
-–s3-sse-customer-key
-
-If using SSE-C you must provide the secret encryption key used to
-encrypt/decrypt your data.
-
--   Config: sse_customer_key
--   Env Var: RCLONE_S3_SSE_CUSTOMER_KEY
--   Type: string
--   Default: ""
--   Examples:
-    -   ""
-        -   None
-
-–s3-sse-customer-key-md5
-
-If using SSE-C you must provide the secret encryption key MD5 checksum.
-
--   Config: sse_customer_key_md5
--   Env Var: RCLONE_S3_SSE_CUSTOMER_KEY_MD5
--   Type: string
--   Default: ""
--   Examples:
-    -   ""
-        -   None
+    Multipart uploads will use `--transfers` * `--s3-upload-concurrency` *
+    `--s3-chunk-size` extra memory.  Single part uploads to not use extra
+    memory.
 
-–s3-upload-cutoff
+    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.
 
-Cutoff for switching to chunked upload
+    Increasing `--s3-upload-concurrency` will increase throughput (8 would
+    be a sensible value) and increasing `--s3-chunk-size` 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.
 
-Any files larger than this will be uploaded in chunks of chunk_size. The
-minimum is 0 and the maximum is 5GB.
 
--   Config: upload_cutoff
--   Env Var: RCLONE_S3_UPLOAD_CUTOFF
--   Type: SizeSuffix
--   Default: 200M
+    ### Buckets and Regions ###
 
-–s3-chunk-size
+    With Amazon S3 you can list buckets (`rclone lsd`) 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, `incorrect region, the bucket is not in 'XXX'
+    region`.
 
-Chunk size to use for uploading.
+    ### Authentication ###
 
-When uploading files larger than upload_cutoff or files with unknown
-size (eg 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.
+    There are a number of ways to supply `rclone` with a set of AWS
+    credentials, with and without using the environment.
 
-Note that “–s3-upload-concurrency” chunks of this size are buffered in
-memory per transfer.
+    The different authentication methods are tried in this order:
 
-If you are transferring large files over high speed links and you have
-enough memory, then increasing this will speed up the transfers.
+     - Directly in the rclone configuration file (`env_auth = false` in the config file):
+       - `access_key_id` and `secret_access_key` are required.
+       - `session_token` can be optionally set when using AWS STS.
+     - Runtime configuration (`env_auth = true` in the config file):
+       - Export the following environment variables before running `rclone`:
+         - Access Key ID: `AWS_ACCESS_KEY_ID` or `AWS_ACCESS_KEY`
+         - Secret Access Key: `AWS_SECRET_ACCESS_KEY` or `AWS_SECRET_KEY`
+         - Session Token: `AWS_SESSION_TOKEN` (optional)
+       - Or, use a [named profile](https://docs.aws.amazon.com/cli/latest/userguide/cli-multiple-profiles.html):
+         - Profile files are standard files used by AWS CLI tools
+         - By default it will use the profile in your home directory (eg `~/.aws/credentials` on unix based systems) file and the "default" profile, to change set these environment variables:
+             - `AWS_SHARED_CREDENTIALS_FILE` to control which file.
+             - `AWS_PROFILE` to control which profile to use.
+       - Or, run `rclone` in an ECS task with an IAM role (AWS only).
+       - Or, run `rclone` on an EC2 instance with an IAM role (AWS only).
+       - Or, run `rclone` in an EKS pod with an IAM role that is associated with a service account (AWS only).
 
-Rclone will automatically increase the chunk size when uploading a large
-file of known size to stay below the 10,000 chunks limit.
+    If none of these option actually end up providing `rclone` with AWS
+    credentials then S3 interaction will be non-authenticated (see below).
 
-Files of unknown size are uploaded with the configured chunk_size. Since
-the default chunk size is 5MB and there can be at most 10,000 chunks,
-this means that by default the maximum size of file you can stream
-upload is 48GB. If you wish to stream upload larger files then you will
-need to increase chunk_size.
+    ### S3 Permissions ###
 
--   Config: chunk_size
--   Env Var: RCLONE_S3_CHUNK_SIZE
--   Type: SizeSuffix
--   Default: 5M
+    When using the `sync` subcommand of `rclone` the following minimum
+    permissions are required to be available on the bucket being written to:
 
-–s3-copy-cutoff
+    * `ListBucket`
+    * `DeleteObject`
+    * `GetObject`
+    * `PutObject`
+    * `PutObjectACL`
 
-Cutoff for switching to multipart copy
+    When using the `lsd` subcommand, the `ListAllMyBuckets` permission is required.
 
-Any files larger than this that need to be server side copied will be
-copied in chunks of this size.
+    Example policy:
 
-The minimum is 0 and the maximum is 5GB.
+{ "Version": "2012-10-17", "Statement": [ { "Effect": "Allow",
+"Principal": { "AWS": "arn:aws:iam::USER_SID:user/USER_NAME" },
+"Action": [ "s3:ListBucket", "s3:DeleteObject", "s3:GetObject",
+"s3:PutObject", "s3:PutObjectAcl" ], "Resource": [
+"arn:aws:s3:::BUCKET_NAME/*", "arn:aws:s3:::BUCKET_NAME" ] }, {
+"Effect": "Allow", "Action": "s3:ListAllMyBuckets", "Resource":
+"arn:aws:s3:::*" }
+] }
 
--   Config: copy_cutoff
--   Env Var: RCLONE_S3_COPY_CUTOFF
--   Type: SizeSuffix
--   Default: 5G
 
-–s3-disable-checksum
+    Notes on above:
 
-Don’t store MD5 checksum with object metadata
+    1. This is a policy that can be used when creating bucket. It assumes
+       that `USER_NAME` has been created.
+    2. The Resource entry must include both resource ARNs, as one implies
+       the bucket and the other implies the bucket's objects.
 
-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.
+    For reference, [here's an Ansible script](https://gist.github.com/ebridges/ebfc9042dd7c756cd101cfa807b7ae2b)
+    that will generate one or more buckets that will work with `rclone sync`.
 
--   Config: disable_checksum
--   Env Var: RCLONE_S3_DISABLE_CHECKSUM
--   Type: bool
--   Default: false
+    ### Key Management System (KMS) ###
 
-–s3-session-token
+    If you are using server side encryption with KMS then you will find
+    you can't transfer small objects.  As a work-around you can use the
+    `--ignore-checksum` flag.
 
-An AWS session token
+    A proper fix is being worked on in [issue #1824](https://github.com/rclone/rclone/issues/1824).
 
--   Config: session_token
--   Env Var: RCLONE_S3_SESSION_TOKEN
--   Type: string
--   Default: ""
+    ### Glacier and Glacier Deep Archive ###
 
-–s3-upload-concurrency
+    You can upload objects using the glacier storage class or transition them to glacier using a [lifecycle policy](http://docs.aws.amazon.com/AmazonS3/latest/user-guide/create-lifecycle.html).
+    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.
 
-Concurrency for multipart uploads.
+        2017/09/11 19:07:43 Failed to sync: failed to open source object: Object in GLACIER, restore first: path/to/file
 
-This is the number of chunks of the same file that are uploaded
-concurrently.
+    In this case you need to [restore](http://docs.aws.amazon.com/AmazonS3/latest/user-guide/restore-archived-objects.html)
+    the object(s) in question before using rclone.
 
-If you are uploading small numbers of large file over high speed link
-and these uploads do not fully utilize your bandwidth, then increasing
-this may help to speed up the transfers.
+    Note that rclone only speaks the S3 API it does not speak the Glacier
+    Vault API, so rclone cannot directly access Glacier Vaults.
 
--   Config: upload_concurrency
--   Env Var: RCLONE_S3_UPLOAD_CONCURRENCY
--   Type: int
--   Default: 4
 
-–s3-force-path-style
+    ### Standard Options
 
-If true use path style access if false use virtual hosted style.
+    Here are the standard options specific to s3 (Amazon S3 Compliant Storage Provider (AWS, Alibaba, Ceph, Digital Ocean, Dreamhost, IBM COS, Minio, etc)).
 
-If this is true (the default) then rclone will use path style access, if
-false then rclone will use virtual path style. See the AWS S3 docs for
-more info.
+    #### --s3-provider
 
-Some providers (eg AWS, Aliyun OSS or Netease COS) require this set to
-false - rclone will do this automatically based on the provider setting.
-
--   Config: force_path_style
--   Env Var: RCLONE_S3_FORCE_PATH_STYLE
--   Type: bool
--   Default: true
-
-–s3-v2-auth
-
-If true use v2 authentication.
-
-If this is false (the default) then rclone will use v4 authentication.
-If it is set then rclone will use v2 authentication.
-
-Use this only if v4 signatures don’t work, eg pre Jewel/v10 CEPH.
-
--   Config: v2_auth
--   Env Var: RCLONE_S3_V2_AUTH
--   Type: bool
--   Default: false
-
-–s3-use-accelerate-endpoint
-
-If true use the AWS S3 accelerated endpoint.
-
-See: AWS S3 Transfer acceleration
-
--   Config: use_accelerate_endpoint
--   Env Var: RCLONE_S3_USE_ACCELERATE_ENDPOINT
--   Type: bool
--   Default: false
-
-–s3-leave-parts-on-error
-
-If true avoid calling abort upload on a failure, leaving all
-successfully uploaded parts on S3 for manual recovery.
-
-It should be set to true for resuming uploads across different sessions.
-
-WARNING: Storing parts of an incomplete multipart upload counts towards
-space usage on S3 and will add additional costs if not cleaned up.
-
--   Config: leave_parts_on_error
--   Env Var: RCLONE_S3_LEAVE_PARTS_ON_ERROR
--   Type: bool
--   Default: false
-
-–s3-list-chunk
-
-Size of listing chunk (response list for each ListObject S3 request).
-
-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 AWS S3. In Ceph, this can be
-increased with the “rgw list buckets max chunk” option.
-
--   Config: list_chunk
--   Env Var: RCLONE_S3_LIST_CHUNK
--   Type: int
--   Default: 1000
-
-–s3-encoding
-
-This sets the encoding for the backend.
-
-See: the encoding section in the overview for more info.
-
--   Config: encoding
--   Env Var: RCLONE_S3_ENCODING
--   Type: MultiEncoder
--   Default: Slash,InvalidUtf8,Dot
-
-–s3-memory-pool-flush-time
-
-How often internal memory buffer pools will be flushed. Uploads which
-requires additional buffers (f.e multipart) will use memory pool for
-allocations. This option controls how often unused buffers will be
-removed from the pool.
-
--   Config: memory_pool_flush_time
--   Env Var: RCLONE_S3_MEMORY_POOL_FLUSH_TIME
--   Type: Duration
--   Default: 1m0s
-
-–s3-memory-pool-use-mmap
-
-Whether to use mmap buffers in internal memory pool.
-
--   Config: memory_pool_use_mmap
--   Env Var: RCLONE_S3_MEMORY_POOL_USE_MMAP
--   Type: bool
--   Default: false
-
-Anonymous access to public buckets
-
-If you want to use rclone to access a public bucket, configure with a
-blank access_key_id and secret_access_key. Your config should end up
-looking like this:
-
-    [anons3]
-    type = s3
-    provider = AWS
-    env_auth = false
-    access_key_id = 
-    secret_access_key = 
-    region = us-east-1
-    endpoint = 
-    location_constraint = 
-    acl = private
-    server_side_encryption = 
-    storage_class = 
-
-Then use it as normal with the name of the public bucket, eg
-
-    rclone lsd anons3:1000genomes
-
-You will be able to list and copy data but not upload it.
-
-Ceph
-
-Ceph is an open source unified, distributed storage system designed for
-excellent performance, reliability and scalability. It has an S3
-compatible object storage interface.
-
-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:
-
-    [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 =
-
-If you are using an older version of CEPH, eg 10.2.x Jewel, then you may
-need to supply the parameter --s3-upload-cutoff 0 or put this in the
-config file as upload_cutoff 0 to work around a bug which causes
-uploading of small files to fail.
-
-Note also that Ceph sometimes puts / 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 / escaped as \/. Make sure you only write / in the
-secret access key.
-
-Eg the dump from Ceph looks something like this (irrelevant keys
-removed).
-
-    {
-        "user_id": "xxx",
-        "display_name": "xxxx",
-        "keys": [
-            {
-                "user": "xxx",
-                "access_key": "xxxxxx",
-                "secret_key": "xxxxxx\/xxxx"
-            }
-        ],
-    }
-
-Because this is a json dump, it is encoding the / as \/, so if you use
-the secret key as xxxxxx/xxxx it will work fine.
-
-Dreamhost
-
-Dreamhost DreamObjects is an object storage system based on CEPH.
-
-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:
-
-    [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 =
-
-DigitalOcean Spaces
-
-Spaces is an S3-interoperable object storage service from cloud provider
-DigitalOcean.
-
-To connect to DigitalOcean Spaces you will need an access key and secret
-key. These can be retrieved on the “Applications & API” page of the
-DigitalOcean control panel. They will be needed when prompted by
-rclone config for your access_key_id and secret_access_key.
-
-When prompted for a region or location_constraint, press enter to use
-the default value. The region must be included in the endpoint setting
-(e.g. nyc3.digitaloceanspaces.com). The default values can be used for
-other settings.
-
-Going through the whole process of creating a new remote by running
-rclone config, each prompt should be answered as shown below:
-
-    Storage> s3
-    env_auth> 1
-    access_key_id> YOUR_ACCESS_KEY
-    secret_access_key> YOUR_SECRET_KEY
-    region>
-    endpoint> nyc3.digitaloceanspaces.com
-    location_constraint>
-    acl>
-    storage_class>
-
-The resulting configuration file should look like:
-
-    [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 =
-
-Once configured, you can create a new Space and begin copying files. For
-example:
-
-    rclone mkdir spaces:my-new-space
-    rclone copy /path/to/files spaces:my-new-space
-
-IBM COS (S3)
-
-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)
-
-To configure access to IBM COS S3, follow the steps below:
-
-1.  Run rclone config and select n for a new remote.
-
-        2018/02/14 14:13:11 NOTICE: Config file "C:\\Users\\a\\.config\\rclone\\rclone.conf" not found - using defaults
-        No remotes found - make a new one
-        n) New remote
-        s) Set configuration password
-        q) Quit config
-        n/s/q> n
-
-2.  Enter the name for the configuration
-
-        name> <YOUR NAME>
-
-3.  Select “s3” storage.
-
-    Choose a number from below, or type in your own value
-        1 / Alias for an existing remote
-        \ "alias"
-        2 / Amazon Drive
-        \ "amazon cloud drive"
-        3 / Amazon S3 Complaint Storage Providers (Dreamhost, Ceph, Minio, IBM COS)
-        \ "s3"
-        4 / Backblaze B2
-        \ "b2"
-    [snip]
-        23 / http Connection
-        \ "http"
-    Storage> 3
-
-4.  Select IBM COS as the S3 Storage Provider.
-
-    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
-           \ "AWS"
-         2 / Choose this option to configure Storage to Ceph Systems
-         \ "Ceph"
-         3 /  Choose this option to configure Storage to Dreamhost
-         \ "Dreamhost"
-       4 / Choose this option to the configure Storage to IBM COS S3
-         \ "IBMCOS"
-         5 / Choose this option to the configure Storage to Minio
-         \ "Minio"
-         Provider>4
-
-5.  Enter the Access Key and Secret.
-
-        AWS Access Key ID - leave blank for anonymous access or runtime credentials.
-        access_key_id> <>
-        AWS Secret Access Key (password) - leave blank for anonymous access or runtime credentials.
-        secret_access_key> <>
-
-6.  Specify the endpoint for IBM COS. For Public IBM COS, choose from
-    the option below. For On Premise IBM COS, enter an enpoint address.
-
-        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
-           \ "s3-api.us-geo.objectstorage.softlayer.net"
-         2 / US Cross Region Dallas Endpoint
-           \ "s3-api.dal.us-geo.objectstorage.softlayer.net"
-         3 / US Cross Region Washington DC Endpoint
-           \ "s3-api.wdc-us-geo.objectstorage.softlayer.net"
-         4 / US Cross Region San Jose Endpoint
-           \ "s3-api.sjc-us-geo.objectstorage.softlayer.net"
-         5 / US Cross Region Private Endpoint
-           \ "s3-api.us-geo.objectstorage.service.networklayer.com"
-         6 / US Cross Region Dallas Private Endpoint
-           \ "s3-api.dal-us-geo.objectstorage.service.networklayer.com"
-         7 / US Cross Region Washington DC Private Endpoint
-           \ "s3-api.wdc-us-geo.objectstorage.service.networklayer.com"
-         8 / US Cross Region San Jose Private Endpoint
-           \ "s3-api.sjc-us-geo.objectstorage.service.networklayer.com"
-         9 / US Region East Endpoint
-           \ "s3.us-east.objectstorage.softlayer.net"
-        10 / US Region East Private Endpoint
-           \ "s3.us-east.objectstorage.service.networklayer.com"
-        11 / US Region South Endpoint
-    [snip]
-        34 / Toronto Single Site Private Endpoint
-           \ "s3.tor01.objectstorage.service.networklayer.com"
-        endpoint>1
-
-7.  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
-
-         1 / US Cross Region Standard
-           \ "us-standard"
-         2 / US Cross Region Vault
-           \ "us-vault"
-         3 / US Cross Region Cold
-           \ "us-cold"
-         4 / US Cross Region Flex
-           \ "us-flex"
-         5 / US East Region Standard
-           \ "us-east-standard"
-         6 / US East Region Vault
-           \ "us-east-vault"
-         7 / US East Region Cold
-           \ "us-east-cold"
-         8 / US East Region Flex
-           \ "us-east-flex"
-         9 / US South Region Standard
-           \ "us-south-standard"
-        10 / US South Region Vault
-           \ "us-south-vault"
-    [snip]
-        32 / Toronto Flex
-           \ "tor01-flex"
-    location_constraint>1
-
-9.  Specify a canned ACL. IBM Cloud (Strorage) supports “public-read”
-    and “private”. IBM Cloud(Infra) supports all the canned ACLs.
-    On-Premise COS supports all the canned ACLs.
-
-    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
-          \ "private"
-          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
-          \ "public-read"
-          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
-          \ "public-read-write"
-          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
-          \ "authenticated-read"
-    acl> 1
-
-12. Review the displayed configuration and accept to save the “remote”
-    then quit. The config file should look like this
-
-        [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
-
-13. Execute rclone commands
-
-        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
-
-Minio
-
-Minio is an object storage server built for cloud application developers
-and devops.
-
-It is very easy to install and provides an S3 compatible server which
-can be used by rclone.
-
-To use it, install Minio following the instructions here.
-
-When it configures itself Minio will print something like this
-
-    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
-
-These details need to go into rclone config like this. Note that it is
-important to put the region in as stated above.
-
-    env_auth> 1
-    access_key_id> USWUXHGYZQYFYFFIT3RE
-    secret_access_key> MOJRH0mkL1IPauahWITSVvyDrQbEEIwljvmxdq03
-    region> us-east-1
-    endpoint> http://192.168.1.106:9000
-    location_constraint>
-    server_side_encryption>
-
-Which makes the config file look like this
-
-    [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 =
-
-So once set up, for example to copy files into a bucket
-
-    rclone copy /path/to/files minio:bucket
-
-Scaleway
-
-Scaleway 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.
-
-Scaleway provides an S3 interface which can be configured for use with
-rclone like this:
-
-    [scaleway]
-    type = s3
-    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 =
-    acl = private
-    force_path_style = false
-    server_side_encryption =
-    storage_class =
-
-Wasabi
-
-Wasabi 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.
-
-Wasabi provides an S3 interface which can be configured for use with
-rclone like this.
-
-    No remotes found - make a new one
-    n) New remote
-    s) Set configuration password
-    n/s> n
-    name> wasabi
-    Type of storage to configure.
-    Choose a number from below, or type in your own value
-    [snip]
-    XX / Amazon S3 (also Dreamhost, Ceph, Minio)
-       \ "s3"
-    [snip]
-    Storage> 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
-       \ "false"
-     2 / Get AWS credentials from the environment (env vars or IAM)
-       \ "true"
-    env_auth> 1
-    AWS Access Key ID - leave blank for anonymous access or runtime credentials.
-    access_key_id> YOURACCESSKEY
-    AWS Secret Access Key (password) - leave blank for anonymous access or runtime credentials.
-    secret_access_key> 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.
-       \ "us-east-1"
-    [snip]
-    region> 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> 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.
-       \ ""
-    [snip]
-    location_constraint>
-    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).
-       \ "private"
-    [snip]
-    acl>
-    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
-       \ ""
-     2 / AES256
-       \ "AES256"
-    server_side_encryption>
-    The storage class to use when storing objects in S3.
-    Choose a number from below, or type in your own value
-     1 / Default
-       \ ""
-     2 / Standard storage class
-       \ "STANDARD"
-     3 / Reduced redundancy storage class
-       \ "REDUCED_REDUNDANCY"
-     4 / Standard Infrequent Access storage class
-       \ "STANDARD_IA"
-    storage_class>
-    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> y
-
-This will leave the config file looking like this.
-
-    [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 =
-
-Alibaba OSS
-
-Here is an example of making an Alibaba Cloud (Aliyun) OSS
-configuration. First run:
-
-    rclone config
-
-This will guide you through an interactive setup process.
-
-    No remotes found - make a new one
-    n) New remote
-    s) Set configuration password
-    q) Quit config
-    n/s/q> n
-    name> oss
-    Type of storage to configure.
-    Enter a string value. Press Enter for the default ("").
-    Choose a number from below, or type in your own value
-    [snip]
-     4 / Amazon S3 Compliant Storage Provider (AWS, Alibaba, Ceph, Digital Ocean, Dreamhost, IBM COS, Minio, etc)
-       \ "s3"
-    [snip]
-    Storage> s3
     Choose your S3 provider.
-    Enter a string value. Press Enter for the default ("").
-    Choose a number from below, or type in your own value
-     1 / Amazon Web Services (AWS) S3
-       \ "AWS"
-     2 / Alibaba Cloud Object Storage System (OSS) formerly Aliyun
-       \ "Alibaba"
-     3 / Ceph Object Storage
-       \ "Ceph"
-    [snip]
-    provider> Alibaba
+
+    - Config:      provider
+    - Env Var:     RCLONE_S3_PROVIDER
+    - Type:        string
+    - Default:     ""
+    - Examples:
+        - "AWS"
+            - Amazon Web Services (AWS) S3
+        - "Alibaba"
+            - Alibaba Cloud Object Storage System (OSS) formerly Aliyun
+        - "Ceph"
+            - Ceph Object Storage
+        - "DigitalOcean"
+            - Digital Ocean Spaces
+        - "Dreamhost"
+            - Dreamhost DreamObjects
+        - "IBMCOS"
+            - IBM COS S3
+        - "Minio"
+            - Minio Object Storage
+        - "Netease"
+            - Netease Object Storage (NOS)
+        - "Scaleway"
+            - Scaleway Object Storage
+        - "StackPath"
+            - StackPath Object Storage
+        - "Wasabi"
+            - Wasabi Object Storage
+        - "Other"
+            - Any other S3 compatible provider
+
+    #### --s3-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.
-    Enter a boolean value (true or false). Press Enter for the default ("false").
-    Choose a number from below, or type in your own value
-     1 / Enter AWS credentials in the next step
-       \ "false"
-     2 / Get AWS credentials from the environment (env vars or IAM)
-       \ "true"
-    env_auth> 1
+
+    - Config:      env_auth
+    - Env Var:     RCLONE_S3_ENV_AUTH
+    - Type:        bool
+    - Default:     false
+    - Examples:
+        - "false"
+            - Enter AWS credentials in the next step
+        - "true"
+            - Get AWS credentials from the environment (env vars or IAM)
+
+    #### --s3-access-key-id
+
     AWS Access Key ID.
     Leave blank for anonymous access or runtime credentials.
-    Enter a string value. Press Enter for the default ("").
-    access_key_id> accesskeyid
+
+    - Config:      access_key_id
+    - Env Var:     RCLONE_S3_ACCESS_KEY_ID
+    - Type:        string
+    - Default:     ""
+
+    #### --s3-secret-access-key
+
     AWS Secret Access Key (password)
     Leave blank for anonymous access or runtime credentials.
-    Enter a string value. Press Enter for the default ("").
-    secret_access_key> secretaccesskey
+
+    - Config:      secret_access_key
+    - Env Var:     RCLONE_S3_SECRET_ACCESS_KEY
+    - Type:        string
+    - Default:     ""
+
+    #### --s3-region
+
+    Region to connect to.
+
+    - Config:      region
+    - Env Var:     RCLONE_S3_REGION
+    - Type:        string
+    - Default:     ""
+    - Examples:
+        - "us-east-1"
+            - The default endpoint - a good choice if you are unsure.
+            - US Region, Northern Virginia or Pacific Northwest.
+            - Leave location constraint empty.
+        - "us-east-2"
+            - US East (Ohio) Region
+            - Needs location constraint us-east-2.
+        - "us-west-2"
+            - US West (Oregon) Region
+            - Needs location constraint us-west-2.
+        - "us-west-1"
+            - US West (Northern California) Region
+            - Needs location constraint us-west-1.
+        - "ca-central-1"
+            - Canada (Central) Region
+            - Needs location constraint ca-central-1.
+        - "eu-west-1"
+            - EU (Ireland) Region
+            - Needs location constraint EU or eu-west-1.
+        - "eu-west-2"
+            - EU (London) Region
+            - Needs location constraint eu-west-2.
+        - "eu-north-1"
+            - EU (Stockholm) Region
+            - Needs location constraint eu-north-1.
+        - "eu-central-1"
+            - EU (Frankfurt) Region
+            - Needs location constraint eu-central-1.
+        - "ap-southeast-1"
+            - Asia Pacific (Singapore) Region
+            - Needs location constraint ap-southeast-1.
+        - "ap-southeast-2"
+            - Asia Pacific (Sydney) Region
+            - Needs location constraint ap-southeast-2.
+        - "ap-northeast-1"
+            - Asia Pacific (Tokyo) Region
+            - Needs location constraint ap-northeast-1.
+        - "ap-northeast-2"
+            - Asia Pacific (Seoul)
+            - Needs location constraint ap-northeast-2.
+        - "ap-south-1"
+            - Asia Pacific (Mumbai)
+            - Needs location constraint ap-south-1.
+        - "ap-east-1"
+            - Asia Patific (Hong Kong) Region
+            - Needs location constraint ap-east-1.
+        - "sa-east-1"
+            - South America (Sao Paulo) Region
+            - Needs location constraint sa-east-1.
+
+    #### --s3-region
+
+    Region to connect to.
+
+    - Config:      region
+    - Env Var:     RCLONE_S3_REGION
+    - Type:        string
+    - Default:     ""
+    - Examples:
+        - "nl-ams"
+            - Amsterdam, The Netherlands
+        - "fr-par"
+            - Paris, France
+
+    #### --s3-region
+
+    Region to connect to.
+    Leave blank if you are using an S3 clone and you don't have a region.
+
+    - Config:      region
+    - Env Var:     RCLONE_S3_REGION
+    - Type:        string
+    - Default:     ""
+    - Examples:
+        - ""
+            - Use this if unsure. Will use v4 signatures and an empty region.
+        - "other-v2-signature"
+            - Use this only if v4 signatures don't work, eg pre Jewel/v10 CEPH.
+
+    #### --s3-endpoint
+
+    Endpoint for S3 API.
+    Leave blank if using AWS to use the default endpoint for the region.
+
+    - Config:      endpoint
+    - Env Var:     RCLONE_S3_ENDPOINT
+    - Type:        string
+    - Default:     ""
+
+    #### --s3-endpoint
+
+    Endpoint for IBM COS S3 API.
+    Specify if using an IBM COS On Premise.
+
+    - Config:      endpoint
+    - Env Var:     RCLONE_S3_ENDPOINT
+    - Type:        string
+    - Default:     ""
+    - Examples:
+        - "s3.us.cloud-object-storage.appdomain.cloud"
+            - US Cross Region Endpoint
+        - "s3.dal.us.cloud-object-storage.appdomain.cloud"
+            - US Cross Region Dallas Endpoint
+        - "s3.wdc.us.cloud-object-storage.appdomain.cloud"
+            - US Cross Region Washington DC Endpoint
+        - "s3.sjc.us.cloud-object-storage.appdomain.cloud"
+            - US Cross Region San Jose Endpoint
+        - "s3.private.us.cloud-object-storage.appdomain.cloud"
+            - US Cross Region Private Endpoint
+        - "s3.private.dal.us.cloud-object-storage.appdomain.cloud"
+            - US Cross Region Dallas Private Endpoint
+        - "s3.private.wdc.us.cloud-object-storage.appdomain.cloud"
+            - US Cross Region Washington DC Private Endpoint
+        - "s3.private.sjc.us.cloud-object-storage.appdomain.cloud"
+            - US Cross Region San Jose Private Endpoint
+        - "s3.us-east.cloud-object-storage.appdomain.cloud"
+            - US Region East Endpoint
+        - "s3.private.us-east.cloud-object-storage.appdomain.cloud"
+            - US Region East Private Endpoint
+        - "s3.us-south.cloud-object-storage.appdomain.cloud"
+            - US Region South Endpoint
+        - "s3.private.us-south.cloud-object-storage.appdomain.cloud"
+            - US Region South Private Endpoint
+        - "s3.eu.cloud-object-storage.appdomain.cloud"
+            - EU Cross Region Endpoint
+        - "s3.fra.eu.cloud-object-storage.appdomain.cloud"
+            - EU Cross Region Frankfurt Endpoint
+        - "s3.mil.eu.cloud-object-storage.appdomain.cloud"
+            - EU Cross Region Milan Endpoint
+        - "s3.ams.eu.cloud-object-storage.appdomain.cloud"
+            - EU Cross Region Amsterdam Endpoint
+        - "s3.private.eu.cloud-object-storage.appdomain.cloud"
+            - EU Cross Region Private Endpoint
+        - "s3.private.fra.eu.cloud-object-storage.appdomain.cloud"
+            - EU Cross Region Frankfurt Private Endpoint
+        - "s3.private.mil.eu.cloud-object-storage.appdomain.cloud"
+            - EU Cross Region Milan Private Endpoint
+        - "s3.private.ams.eu.cloud-object-storage.appdomain.cloud"
+            - EU Cross Region Amsterdam Private Endpoint
+        - "s3.eu-gb.cloud-object-storage.appdomain.cloud"
+            - Great Britain Endpoint
+        - "s3.private.eu-gb.cloud-object-storage.appdomain.cloud"
+            - Great Britain Private Endpoint
+        - "s3.eu-de.cloud-object-storage.appdomain.cloud"
+            - EU Region DE Endpoint
+        - "s3.private.eu-de.cloud-object-storage.appdomain.cloud"
+            - EU Region DE Private Endpoint
+        - "s3.ap.cloud-object-storage.appdomain.cloud"
+            - APAC Cross Regional Endpoint
+        - "s3.tok.ap.cloud-object-storage.appdomain.cloud"
+            - APAC Cross Regional Tokyo Endpoint
+        - "s3.hkg.ap.cloud-object-storage.appdomain.cloud"
+            - APAC Cross Regional HongKong Endpoint
+        - "s3.seo.ap.cloud-object-storage.appdomain.cloud"
+            - APAC Cross Regional Seoul Endpoint
+        - "s3.private.ap.cloud-object-storage.appdomain.cloud"
+            - APAC Cross Regional Private Endpoint
+        - "s3.private.tok.ap.cloud-object-storage.appdomain.cloud"
+            - APAC Cross Regional Tokyo Private Endpoint
+        - "s3.private.hkg.ap.cloud-object-storage.appdomain.cloud"
+            - APAC Cross Regional HongKong Private Endpoint
+        - "s3.private.seo.ap.cloud-object-storage.appdomain.cloud"
+            - APAC Cross Regional Seoul Private Endpoint
+        - "s3.jp-tok.cloud-object-storage.appdomain.cloud"
+            - APAC Region Japan Endpoint
+        - "s3.private.jp-tok.cloud-object-storage.appdomain.cloud"
+            - APAC Region Japan Private Endpoint
+        - "s3.au-syd.cloud-object-storage.appdomain.cloud"
+            - APAC Region Australia Endpoint
+        - "s3.private.au-syd.cloud-object-storage.appdomain.cloud"
+            - APAC Region Australia Private Endpoint
+        - "s3.ams03.cloud-object-storage.appdomain.cloud"
+            - Amsterdam Single Site Endpoint
+        - "s3.private.ams03.cloud-object-storage.appdomain.cloud"
+            - Amsterdam Single Site Private Endpoint
+        - "s3.che01.cloud-object-storage.appdomain.cloud"
+            - Chennai Single Site Endpoint
+        - "s3.private.che01.cloud-object-storage.appdomain.cloud"
+            - Chennai Single Site Private Endpoint
+        - "s3.mel01.cloud-object-storage.appdomain.cloud"
+            - Melbourne Single Site Endpoint
+        - "s3.private.mel01.cloud-object-storage.appdomain.cloud"
+            - Melbourne Single Site Private Endpoint
+        - "s3.osl01.cloud-object-storage.appdomain.cloud"
+            - Oslo Single Site Endpoint
+        - "s3.private.osl01.cloud-object-storage.appdomain.cloud"
+            - Oslo Single Site Private Endpoint
+        - "s3.tor01.cloud-object-storage.appdomain.cloud"
+            - Toronto Single Site Endpoint
+        - "s3.private.tor01.cloud-object-storage.appdomain.cloud"
+            - Toronto Single Site Private Endpoint
+        - "s3.seo01.cloud-object-storage.appdomain.cloud"
+            - Seoul Single Site Endpoint
+        - "s3.private.seo01.cloud-object-storage.appdomain.cloud"
+            - Seoul Single Site Private Endpoint
+        - "s3.mon01.cloud-object-storage.appdomain.cloud"
+            - Montreal Single Site Endpoint
+        - "s3.private.mon01.cloud-object-storage.appdomain.cloud"
+            - Montreal Single Site Private Endpoint
+        - "s3.mex01.cloud-object-storage.appdomain.cloud"
+            - Mexico Single Site Endpoint
+        - "s3.private.mex01.cloud-object-storage.appdomain.cloud"
+            - Mexico Single Site Private Endpoint
+        - "s3.sjc04.cloud-object-storage.appdomain.cloud"
+            - San Jose Single Site Endpoint
+        - "s3.private.sjc04.cloud-object-storage.appdomain.cloud"
+            - San Jose Single Site Private Endpoint
+        - "s3.mil01.cloud-object-storage.appdomain.cloud"
+            - Milan Single Site Endpoint
+        - "s3.private.mil01.cloud-object-storage.appdomain.cloud"
+            - Milan Single Site Private Endpoint
+        - "s3.hkg02.cloud-object-storage.appdomain.cloud"
+            - Hong Kong Single Site Endpoint
+        - "s3.private.hkg02.cloud-object-storage.appdomain.cloud"
+            - Hong Kong Single Site Private Endpoint
+        - "s3.par01.cloud-object-storage.appdomain.cloud"
+            - Paris Single Site Endpoint
+        - "s3.private.par01.cloud-object-storage.appdomain.cloud"
+            - Paris Single Site Private Endpoint
+        - "s3.sng01.cloud-object-storage.appdomain.cloud"
+            - Singapore Single Site Endpoint
+        - "s3.private.sng01.cloud-object-storage.appdomain.cloud"
+            - Singapore Single Site Private Endpoint
+
+    #### --s3-endpoint
+
     Endpoint for OSS API.
-    Enter a string value. Press Enter for the default ("").
-    Choose a number from below, or type in your own value
-     1 / East China 1 (Hangzhou)
-       \ "oss-cn-hangzhou.aliyuncs.com"
-     2 / East China 2 (Shanghai)
-       \ "oss-cn-shanghai.aliyuncs.com"
-     3 / North China 1 (Qingdao)
-       \ "oss-cn-qingdao.aliyuncs.com"
-    [snip]
-    endpoint> 1
+
+    - Config:      endpoint
+    - Env Var:     RCLONE_S3_ENDPOINT
+    - Type:        string
+    - Default:     ""
+    - Examples:
+        - "oss-cn-hangzhou.aliyuncs.com"
+            - East China 1 (Hangzhou)
+        - "oss-cn-shanghai.aliyuncs.com"
+            - East China 2 (Shanghai)
+        - "oss-cn-qingdao.aliyuncs.com"
+            - North China 1 (Qingdao)
+        - "oss-cn-beijing.aliyuncs.com"
+            - North China 2 (Beijing)
+        - "oss-cn-zhangjiakou.aliyuncs.com"
+            - North China 3 (Zhangjiakou)
+        - "oss-cn-huhehaote.aliyuncs.com"
+            - North China 5 (Huhehaote)
+        - "oss-cn-shenzhen.aliyuncs.com"
+            - South China 1 (Shenzhen)
+        - "oss-cn-hongkong.aliyuncs.com"
+            - Hong Kong (Hong Kong)
+        - "oss-us-west-1.aliyuncs.com"
+            - US West 1 (Silicon Valley)
+        - "oss-us-east-1.aliyuncs.com"
+            - US East 1 (Virginia)
+        - "oss-ap-southeast-1.aliyuncs.com"
+            - Southeast Asia Southeast 1 (Singapore)
+        - "oss-ap-southeast-2.aliyuncs.com"
+            - Asia Pacific Southeast 2 (Sydney)
+        - "oss-ap-southeast-3.aliyuncs.com"
+            - Southeast Asia Southeast 3 (Kuala Lumpur)
+        - "oss-ap-southeast-5.aliyuncs.com"
+            - Asia Pacific Southeast 5 (Jakarta)
+        - "oss-ap-northeast-1.aliyuncs.com"
+            - Asia Pacific Northeast 1 (Japan)
+        - "oss-ap-south-1.aliyuncs.com"
+            - Asia Pacific South 1 (Mumbai)
+        - "oss-eu-central-1.aliyuncs.com"
+            - Central Europe 1 (Frankfurt)
+        - "oss-eu-west-1.aliyuncs.com"
+            - West Europe (London)
+        - "oss-me-east-1.aliyuncs.com"
+            - Middle East 1 (Dubai)
+
+    #### --s3-endpoint
+
+    Endpoint for Scaleway Object Storage.
+
+    - Config:      endpoint
+    - Env Var:     RCLONE_S3_ENDPOINT
+    - Type:        string
+    - Default:     ""
+    - Examples:
+        - "s3.nl-ams.scw.cloud"
+            - Amsterdam Endpoint
+        - "s3.fr-par.scw.cloud"
+            - Paris Endpoint
+
+    #### --s3-endpoint
+
+    Endpoint for StackPath Object Storage.
+
+    - Config:      endpoint
+    - Env Var:     RCLONE_S3_ENDPOINT
+    - Type:        string
+    - Default:     ""
+    - Examples:
+        - "s3.us-east-2.stackpathstorage.com"
+            - US East Endpoint
+        - "s3.us-west-1.stackpathstorage.com"
+            - US West Endpoint
+        - "s3.eu-central-1.stackpathstorage.com"
+            - EU Endpoint
+
+    #### --s3-endpoint
+
+    Endpoint for S3 API.
+    Required when using an S3 clone.
+
+    - Config:      endpoint
+    - Env Var:     RCLONE_S3_ENDPOINT
+    - Type:        string
+    - Default:     ""
+    - Examples:
+        - "objects-us-east-1.dream.io"
+            - Dream Objects endpoint
+        - "nyc3.digitaloceanspaces.com"
+            - Digital Ocean Spaces New York 3
+        - "ams3.digitaloceanspaces.com"
+            - Digital Ocean Spaces Amsterdam 3
+        - "sgp1.digitaloceanspaces.com"
+            - Digital Ocean Spaces Singapore 1
+        - "s3.wasabisys.com"
+            - Wasabi US East endpoint
+        - "s3.us-west-1.wasabisys.com"
+            - Wasabi US West endpoint
+        - "s3.eu-central-1.wasabisys.com"
+            - Wasabi EU Central endpoint
+
+    #### --s3-location-constraint
+
+    Location constraint - must be set to match the Region.
+    Used when creating buckets only.
+
+    - Config:      location_constraint
+    - Env Var:     RCLONE_S3_LOCATION_CONSTRAINT
+    - Type:        string
+    - Default:     ""
+    - Examples:
+        - ""
+            - Empty for US Region, Northern Virginia or Pacific Northwest.
+        - "us-east-2"
+            - US East (Ohio) Region.
+        - "us-west-2"
+            - US West (Oregon) Region.
+        - "us-west-1"
+            - US West (Northern California) Region.
+        - "ca-central-1"
+            - Canada (Central) Region.
+        - "eu-west-1"
+            - EU (Ireland) Region.
+        - "eu-west-2"
+            - EU (London) Region.
+        - "eu-north-1"
+            - EU (Stockholm) Region.
+        - "EU"
+            - EU Region.
+        - "ap-southeast-1"
+            - Asia Pacific (Singapore) Region.
+        - "ap-southeast-2"
+            - Asia Pacific (Sydney) Region.
+        - "ap-northeast-1"
+            - Asia Pacific (Tokyo) Region.
+        - "ap-northeast-2"
+            - Asia Pacific (Seoul)
+        - "ap-south-1"
+            - Asia Pacific (Mumbai)
+        - "ap-east-1"
+            - Asia Pacific (Hong Kong)
+        - "sa-east-1"
+            - South America (Sao Paulo) Region.
+
+    #### --s3-location-constraint
+
+    Location constraint - must match endpoint when using IBM Cloud Public.
+    For on-prem COS, do not make a selection from this list, hit enter
+
+    - Config:      location_constraint
+    - Env Var:     RCLONE_S3_LOCATION_CONSTRAINT
+    - Type:        string
+    - Default:     ""
+    - Examples:
+        - "us-standard"
+            - US Cross Region Standard
+        - "us-vault"
+            - US Cross Region Vault
+        - "us-cold"
+            - US Cross Region Cold
+        - "us-flex"
+            - US Cross Region Flex
+        - "us-east-standard"
+            - US East Region Standard
+        - "us-east-vault"
+            - US East Region Vault
+        - "us-east-cold"
+            - US East Region Cold
+        - "us-east-flex"
+            - US East Region Flex
+        - "us-south-standard"
+            - US South Region Standard
+        - "us-south-vault"
+            - US South Region Vault
+        - "us-south-cold"
+            - US South Region Cold
+        - "us-south-flex"
+            - US South Region Flex
+        - "eu-standard"
+            - EU Cross Region Standard
+        - "eu-vault"
+            - EU Cross Region Vault
+        - "eu-cold"
+            - EU Cross Region Cold
+        - "eu-flex"
+            - EU Cross Region Flex
+        - "eu-gb-standard"
+            - Great Britain Standard
+        - "eu-gb-vault"
+            - Great Britain Vault
+        - "eu-gb-cold"
+            - Great Britain Cold
+        - "eu-gb-flex"
+            - Great Britain Flex
+        - "ap-standard"
+            - APAC Standard
+        - "ap-vault"
+            - APAC Vault
+        - "ap-cold"
+            - APAC Cold
+        - "ap-flex"
+            - APAC Flex
+        - "mel01-standard"
+            - Melbourne Standard
+        - "mel01-vault"
+            - Melbourne Vault
+        - "mel01-cold"
+            - Melbourne Cold
+        - "mel01-flex"
+            - Melbourne Flex
+        - "tor01-standard"
+            - Toronto Standard
+        - "tor01-vault"
+            - Toronto Vault
+        - "tor01-cold"
+            - Toronto Cold
+        - "tor01-flex"
+            - Toronto Flex
+
+    #### --s3-location-constraint
+
+    Location constraint - must be set to match the Region.
+    Leave blank if not sure. Used when creating buckets only.
+
+    - Config:      location_constraint
+    - Env Var:     RCLONE_S3_LOCATION_CONSTRAINT
+    - Type:        string
+    - Default:     ""
+
+    #### --s3-acl
+
     Canned ACL used when creating buckets and storing or copying objects.
 
+    This ACL is used for creating objects and if bucket_acl isn'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't copy the ACL from the source but rather writes a fresh one.
-    Enter a string value. Press Enter for the default ("").
-    Choose a number from below, or type in your own value
-     1 / Owner gets FULL_CONTROL. No one else has access rights (default).
-       \ "private"
-     2 / Owner gets FULL_CONTROL. The AllUsers group gets READ access.
-       \ "public-read"
-       / Owner gets FULL_CONTROL. The AllUsers group gets READ and WRITE access.
-    [snip]
-    acl> 1
+
+    - Config:      acl
+    - Env Var:     RCLONE_S3_ACL
+    - Type:        string
+    - Default:     ""
+    - Examples:
+        - "private"
+            - Owner gets FULL_CONTROL. No one else has access rights (default).
+        - "public-read"
+            - Owner gets FULL_CONTROL. The AllUsers group gets READ access.
+        - "public-read-write"
+            - Owner gets FULL_CONTROL. The AllUsers group gets READ and WRITE access.
+            - Granting this on a bucket is generally not recommended.
+        - "authenticated-read"
+            - Owner gets FULL_CONTROL. The AuthenticatedUsers group gets READ access.
+        - "bucket-owner-read"
+            - Object owner gets FULL_CONTROL. Bucket owner gets READ access.
+            - If you specify this canned ACL when creating a bucket, Amazon S3 ignores it.
+        - "bucket-owner-full-control"
+            - Both the object owner and the bucket owner get FULL_CONTROL over the object.
+            - If you specify this canned ACL when creating a bucket, Amazon S3 ignores it.
+        - "private"
+            - 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
+        - "public-read"
+            - 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
+        - "public-read-write"
+            - Owner gets FULL_CONTROL. The AllUsers group gets READ and WRITE access. This acl is available on IBM Cloud (Infra), On-Premise IBM COS
+        - "authenticated-read"
+            - 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
+
+    #### --s3-server-side-encryption
+
+    The server-side encryption algorithm used when storing this object in S3.
+
+    - Config:      server_side_encryption
+    - Env Var:     RCLONE_S3_SERVER_SIDE_ENCRYPTION
+    - Type:        string
+    - Default:     ""
+    - Examples:
+        - ""
+            - None
+        - "AES256"
+            - AES256
+        - "aws:kms"
+            - aws:kms
+
+    #### --s3-sse-kms-key-id
+
+    If using KMS ID you must provide the ARN of Key.
+
+    - Config:      sse_kms_key_id
+    - Env Var:     RCLONE_S3_SSE_KMS_KEY_ID
+    - Type:        string
+    - Default:     ""
+    - Examples:
+        - ""
+            - None
+        - "arn:aws:kms:us-east-1:*"
+            - arn:aws:kms:*
+
+    #### --s3-storage-class
+
+    The storage class to use when storing new objects in S3.
+
+    - Config:      storage_class
+    - Env Var:     RCLONE_S3_STORAGE_CLASS
+    - Type:        string
+    - Default:     ""
+    - Examples:
+        - ""
+            - Default
+        - "STANDARD"
+            - Standard storage class
+        - "REDUCED_REDUNDANCY"
+            - Reduced redundancy storage class
+        - "STANDARD_IA"
+            - Standard Infrequent Access storage class
+        - "ONEZONE_IA"
+            - One Zone Infrequent Access storage class
+        - "GLACIER"
+            - Glacier storage class
+        - "DEEP_ARCHIVE"
+            - Glacier Deep Archive storage class
+        - "INTELLIGENT_TIERING"
+            - Intelligent-Tiering storage class
+
+    #### --s3-storage-class
+
     The storage class to use when storing new objects in OSS.
-    Enter a string value. Press Enter for the default ("").
-    Choose a number from below, or type in your own value
-     1 / Default
-       \ ""
-     2 / Standard storage class
-       \ "STANDARD"
-     3 / Archive storage mode.
-       \ "GLACIER"
-     4 / Infrequent access storage mode.
-       \ "STANDARD_IA"
-    storage_class> 1
-    Edit advanced config? (y/n)
-    y) Yes
-    n) No
-    y/n> 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> y
-
-Netease NOS
-
-For Netease NOS configure as per the configurator rclone config setting
-the provider Netease. This will automatically set
-force_path_style = false which is necessary for it to run properly.
-
-
-Backblaze B2
-
-B2 is Backblaze’s cloud storage system.
-
-Paths are specified as remote:bucket (or remote: for the lsd command.)
-You may put subdirectories in too, eg remote:bucket/path/to/dir.
-
-Here is an example of making a b2 configuration. First run
-
-    rclone config
-
-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.
-
-    No remotes found - make a new one
-    n) New remote
-    q) Quit config
-    n/q> n
-    name> remote
-    Type of storage to configure.
-    Choose a number from below, or type in your own value
-    [snip]
-    XX / Backblaze B2
-       \ "b2"
-    [snip]
-    Storage> b2
-    Account ID or Application Key ID
-    account> 123456789abc
-    Application Key
-    key> 0123456789abcdef0123456789abcdef0123456789
-    Endpoint for the service - leave blank normally.
-    endpoint>
-    Remote config
-    --------------------
-    [remote]
-    account = 123456789abc
-    key = 0123456789abcdef0123456789abcdef0123456789
-    endpoint =
-    --------------------
-    y) Yes this is OK
-    e) Edit this remote
-    d) Delete this remote
-    y/e/d> y
-
-This remote is called remote and can now be used like this
-
-See all buckets
-
-    rclone lsd remote:
-
-Create a new bucket
-
-    rclone mkdir remote:bucket
-
-List the contents of a bucket
-
-    rclone ls remote:bucket
-
-Sync /home/local/directory to the remote bucket, deleting any excess
-files in the bucket.
-
-    rclone sync /home/local/directory remote:bucket
-
-Application Keys
-
-B2 supports multiple Application Keys for different access permission to
-B2 Buckets.
-
-You can use these with rclone too; you will need to use rclone version
-1.43 or later.
 
-Follow Backblaze’s docs to create an Application Key with the required
-permission and add the applicationKeyId as the account and the
-Application Key itself as the key.
+    - Config:      storage_class
+    - Env Var:     RCLONE_S3_STORAGE_CLASS
+    - Type:        string
+    - Default:     ""
+    - Examples:
+        - ""
+            - Default
+        - "STANDARD"
+            - Standard storage class
+        - "GLACIER"
+            - Archive storage mode.
+        - "STANDARD_IA"
+            - Infrequent access storage mode.
+
+    #### --s3-storage-class
+
+    The storage class to use when storing new objects in S3.
+
+    - Config:      storage_class
+    - Env Var:     RCLONE_S3_STORAGE_CLASS
+    - Type:        string
+    - Default:     ""
+    - Examples:
+        - ""
+            - Default
+        - "STANDARD"
+            - The Standard class for any upload; suitable for on-demand content like streaming or CDN.
+        - "GLACIER"
+            - Archived storage; prices are lower, but it needs to be restored first to be accessed.
+
+    ### Advanced Options
+
+    Here are the advanced options specific to s3 (Amazon S3 Compliant Storage Provider (AWS, Alibaba, Ceph, Digital Ocean, Dreamhost, IBM COS, Minio, etc)).
+
+    #### --s3-bucket-acl
+
+    Canned ACL used when creating buckets.
+
+    For more info visit https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html#canned-acl
+
+    Note that this ACL is applied when only when creating buckets.  If it
+    isn't set then "acl" is used instead.
+
+    - Config:      bucket_acl
+    - Env Var:     RCLONE_S3_BUCKET_ACL
+    - Type:        string
+    - Default:     ""
+    - Examples:
+        - "private"
+            - Owner gets FULL_CONTROL. No one else has access rights (default).
+        - "public-read"
+            - Owner gets FULL_CONTROL. The AllUsers group gets READ access.
+        - "public-read-write"
+            - Owner gets FULL_CONTROL. The AllUsers group gets READ and WRITE access.
+            - Granting this on a bucket is generally not recommended.
+        - "authenticated-read"
+            - Owner gets FULL_CONTROL. The AuthenticatedUsers group gets READ access.
 
-Note that you must put the _applicationKeyId_ as the account – you can’t
-use the master Account ID. If you try then B2 will return 401 errors.
+    #### --s3-sse-customer-algorithm
 
-–fast-list
+    If using SSE-C, the server-side encryption algorithm used when storing this object in S3.
 
-This remote supports --fast-list which allows you to use fewer
-transactions in exchange for more memory. See the rclone docs for more
-details.
+    - Config:      sse_customer_algorithm
+    - Env Var:     RCLONE_S3_SSE_CUSTOMER_ALGORITHM
+    - Type:        string
+    - Default:     ""
+    - Examples:
+        - ""
+            - None
+        - "AES256"
+            - AES256
 
-Modified time
+    #### --s3-sse-customer-key
 
-The modified time is stored as metadata on the object as
-X-Bz-Info-src_last_modified_millis as milliseconds since 1970-01-01 in
-the Backblaze standard. Other tools should be able to use this as a
-modified time.
+    If using SSE-C you must provide the secret encryption key used to encrypt/decrypt your data.
 
-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.
+    - Config:      sse_customer_key
+    - Env Var:     RCLONE_S3_SSE_CUSTOMER_KEY
+    - Type:        string
+    - Default:     ""
+    - Examples:
+        - ""
+            - None
 
-Restricted filename characters
+    #### --s3-sse-customer-key-md5
 
-In addition to the default restricted characters set the following
-characters are also replaced:
+    If using SSE-C you must provide the secret encryption key MD5 checksum.
 
-  Character    Value   Replacement
-  ----------- ------- -------------
-  \            0x5C        ＼
+    - Config:      sse_customer_key_md5
+    - Env Var:     RCLONE_S3_SSE_CUSTOMER_KEY_MD5
+    - Type:        string
+    - Default:     ""
+    - Examples:
+        - ""
+            - None
 
-Invalid UTF-8 bytes will also be replaced, as they can’t be used in JSON
-strings.
+    #### --s3-upload-cutoff
 
-SHA1 checksums
+    Cutoff for switching to chunked upload
 
-The SHA1 checksums of the files are checked on upload and download and
-will be used in the syncing process.
+    Any files larger than this will be uploaded in chunks of chunk_size.
+    The minimum is 0 and the maximum is 5GB.
 
-Large files (bigger than the limit in --b2-upload-cutoff) which are
-uploaded in chunks will store their SHA1 on the object as
-X-Bz-Info-large_file_sha1 as recommended by Backblaze.
+    - Config:      upload_cutoff
+    - Env Var:     RCLONE_S3_UPLOAD_CUTOFF
+    - Type:        SizeSuffix
+    - Default:     200M
 
-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 the overview
-for exactly which remotes support SHA1.
+    #### --s3-chunk-size
 
-Sources which don’t support SHA1, in particular crypt will upload large
-files without SHA1 checksums. This may be fixed in the future (see
-#1767).
+    Chunk size to use for uploading.
 
-Files sizes below --b2-upload-cutoff will always have an SHA1 regardless
-of the source.
+    When uploading files larger than upload_cutoff or files with unknown
+    size (eg 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.
 
-Transfers
+    Note that "--s3-upload-concurrency" chunks of this size are buffered
+    in memory per transfer.
 
-Backblaze recommends that you do lots of transfers simultaneously for
-maximum speed. In tests from my SSD equipped laptop the optimum setting
-is about --transfers 32 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 --transfers 4 is definitely too low for
-Backblaze B2 though.
+    If you are transferring large files over high speed links and you have
+    enough memory, then increasing this will speed up the transfers.
 
-Note that uploading big files (bigger than 200 MB by default) will use a
-96 MB RAM buffer by default. There can be at most --transfers of these
-in use at any moment, so this sets the upper limit on the memory used.
+    Rclone will automatically increase the chunk size when uploading a
+    large file of known size to stay below the 10,000 chunks limit.
 
-Versions
+    Files of unknown size are uploaded with the configured
+    chunk_size. Since the default chunk size is 5MB and there can be at
+    most 10,000 chunks, this means that by default the maximum size of
+    file you can stream upload is 48GB.  If you wish to stream upload
+    larger files then you will need to increase chunk_size.
 
-When rclone uploads a new version of a file it creates a new version of
-it. Likewise when you delete a file, the old version will be marked
-hidden and still be available. Conversely, you may opt in to a “hard
-delete” of files with the --b2-hard-delete flag which would permanently
-remove the file instead of hiding it.
+    - Config:      chunk_size
+    - Env Var:     RCLONE_S3_CHUNK_SIZE
+    - Type:        SizeSuffix
+    - Default:     5M
 
-Old versions of files, where available, are visible using the
---b2-versions flag.
+    #### --s3-max-upload-parts
 
-NB Note that --b2-versions does not work with crypt at the moment #1627.
-Using –backup-dir with rclone is the recommended way of working around
-this.
+    Maximum number of parts in a multipart upload.
 
-If you wish to remove all the old versions then you can use the
-rclone cleanup remote:bucket 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, eg
-rclone cleanup remote:bucket/path/to/stuff.
+    This option defines the maximum number of multipart chunks to use
+    when doing a multipart upload.
 
-Note that cleanup will remove partially uploaded files from the bucket
-if they are more than a day old.
+    This can be useful if a service does not support the AWS S3
+    specification of 10,000 chunks.
 
-When you purge a bucket, the current and the old versions will be
-deleted then the bucket will be deleted.
+    Rclone will automatically increase the chunk size when uploading a
+    large file of a known size to stay below this number of chunks limit.
 
-However delete will cause the current versions of the files to become
-hidden old versions.
 
-Here is a session showing the listing and retrieval of an old version
-followed by a cleanup of the old versions.
+    - Config:      max_upload_parts
+    - Env Var:     RCLONE_S3_MAX_UPLOAD_PARTS
+    - Type:        int
+    - Default:     10000
 
-Show current version and all the versions with --b2-versions flag.
+    #### --s3-copy-cutoff
 
-    $ rclone -q ls b2:cleanup-test
-            9 one.txt
+    Cutoff for switching to multipart copy
 
-    $ 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
+    Any files larger than this that need to be server side copied will be
+    copied in chunks of this size.
 
-Retrieve an old version
+    The minimum is 0 and the maximum is 5GB.
 
-    $ rclone -q --b2-versions copy b2:cleanup-test/one-v2016-07-04-141003-000.txt /tmp
+    - Config:      copy_cutoff
+    - Env Var:     RCLONE_S3_COPY_CUTOFF
+    - Type:        SizeSuffix
+    - Default:     4.656G
 
-    $ 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
+    #### --s3-disable-checksum
 
-Clean up all the old versions and show that they’ve gone.
+    Don't store MD5 checksum with object metadata
 
-    $ rclone -q cleanup b2:cleanup-test
+    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.
 
-    $ rclone -q ls b2:cleanup-test
-            9 one.txt
+    - Config:      disable_checksum
+    - Env Var:     RCLONE_S3_DISABLE_CHECKSUM
+    - Type:        bool
+    - Default:     false
 
-    $ rclone -q --b2-versions ls b2:cleanup-test
-            9 one.txt
+    #### --s3-shared-credentials-file
 
-Data usage
+    Path to the shared credentials file
 
-It is useful to know how many requests are sent to the server in
-different scenarios.
+    If env_auth = true then rclone can use a shared credentials file.
 
-All copy commands send the following 4 requests:
+    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.
 
-    /b2api/v1/b2_authorize_account
-    /b2api/v1/b2_create_bucket
-    /b2api/v1/b2_list_buckets
-    /b2api/v1/b2_list_file_names
+        Linux/OSX: "$HOME/.aws/credentials"
+        Windows:   "%USERPROFILE%\.aws\credentials"
 
-The b2_list_file_names 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 #818 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.
 
-Uploading files that do not require chunking, will send 2 requests per
-file upload:
+    - Config:      shared_credentials_file
+    - Env Var:     RCLONE_S3_SHARED_CREDENTIALS_FILE
+    - Type:        string
+    - Default:     ""
 
-    /b2api/v1/b2_get_upload_url
-    /b2api/v1/b2_upload_file/
+    #### --s3-profile
 
-Uploading files requiring chunking, will send 2 requests (one each to
-start and finish the upload) and another 2 requests for each chunk:
+    Profile to use in the shared credentials file
 
-    /b2api/v1/b2_start_large_file
-    /b2api/v1/b2_get_upload_part_url
-    /b2api/v1/b2_upload_part/
-    /b2api/v1/b2_finish_large_file
+    If env_auth = true then rclone can use a shared credentials file. This
+    variable controls which profile is used in that file.
 
-Versions
+    If empty it will default to the environment variable "AWS_PROFILE" or
+    "default" if that environment variable is also not set.
 
-Versions can be viewed with the --b2-versions flag. When it is set
-rclone will show and act on older versions of files. For example
 
-Listing without --b2-versions
+    - Config:      profile
+    - Env Var:     RCLONE_S3_PROFILE
+    - Type:        string
+    - Default:     ""
 
-    $ rclone -q ls b2:cleanup-test
-            9 one.txt
+    #### --s3-session-token
 
-And with
+    An AWS session token
 
-    $ 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
+    - Config:      session_token
+    - Env Var:     RCLONE_S3_SESSION_TOKEN
+    - Type:        string
+    - Default:     ""
 
-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.
+    #### --s3-upload-concurrency
 
-Note that when using --b2-versions no file write operations are
-permitted, so you can’t upload files or delete them.
+    Concurrency for multipart uploads.
 
-B2 and rclone link
+    This is the number of chunks of the same file that are uploaded
+    concurrently.
 
-Rclone supports generating file share links for private B2 buckets. They
-can either be for a file for example:
+    If you are uploading small numbers of large file over high speed link
+    and these uploads do not fully utilize your bandwidth, then increasing
+    this may help to speed up the transfers.
 
-    ./rclone link B2:bucket/path/to/file.txt
-    https://f002.backblazeb2.com/file/bucket/path/to/file.txt?Authorization=xxxxxxxx
+    - Config:      upload_concurrency
+    - Env Var:     RCLONE_S3_UPLOAD_CONCURRENCY
+    - Type:        int
+    - Default:     4
 
-or if run on a directory you will get:
+    #### --s3-force-path-style
 
-    ./rclone link B2:bucket/path
-    https://f002.backblazeb2.com/file/bucket/path?Authorization=xxxxxxxx
+    If true use path style access if false use virtual hosted style.
 
-you can then use the authorization token (the part of the url from the
-?Authorization= on) on any file path under that directory. For example:
+    If this is true (the default) then rclone will use path style access,
+    if false then rclone will use virtual path style. See [the AWS S3
+    docs](https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingBucket.html#access-bucket-intro)
+    for more info.
 
-    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
+    Some providers (eg AWS, Aliyun OSS or Netease COS) require this set to
+    false - rclone will do this automatically based on the provider
+    setting.
 
-Standard Options
+    - Config:      force_path_style
+    - Env Var:     RCLONE_S3_FORCE_PATH_STYLE
+    - Type:        bool
+    - Default:     true
 
-Here are the standard options specific to b2 (Backblaze B2).
+    #### --s3-v2-auth
 
-–b2-account
+    If true use v2 authentication.
 
-Account ID or Application Key ID
+    If this is false (the default) then rclone will use v4 authentication.
+    If it is set then rclone will use v2 authentication.
 
--   Config: account
--   Env Var: RCLONE_B2_ACCOUNT
--   Type: string
--   Default: ""
+    Use this only if v4 signatures don't work, eg pre Jewel/v10 CEPH.
 
-–b2-key
+    - Config:      v2_auth
+    - Env Var:     RCLONE_S3_V2_AUTH
+    - Type:        bool
+    - Default:     false
 
-Application Key
+    #### --s3-use-accelerate-endpoint
 
--   Config: key
--   Env Var: RCLONE_B2_KEY
--   Type: string
--   Default: ""
+    If true use the AWS S3 accelerated endpoint.
 
-–b2-hard-delete
+    See: [AWS S3 Transfer acceleration](https://docs.aws.amazon.com/AmazonS3/latest/dev/transfer-acceleration-examples.html)
 
-Permanently delete files on remote removal, otherwise hide files.
+    - Config:      use_accelerate_endpoint
+    - Env Var:     RCLONE_S3_USE_ACCELERATE_ENDPOINT
+    - Type:        bool
+    - Default:     false
 
--   Config: hard_delete
--   Env Var: RCLONE_B2_HARD_DELETE
--   Type: bool
--   Default: false
+    #### --s3-leave-parts-on-error
 
-Advanced Options
+    If true avoid calling abort upload on a failure, leaving all successfully uploaded parts on S3 for manual recovery.
 
-Here are the advanced options specific to b2 (Backblaze B2).
+    It should be set to true for resuming uploads across different sessions.
 
-–b2-endpoint
+    WARNING: Storing parts of an incomplete multipart upload counts towards space usage on S3 and will add additional costs if not cleaned up.
 
-Endpoint for the service. Leave blank normally.
 
--   Config: endpoint
--   Env Var: RCLONE_B2_ENDPOINT
--   Type: string
--   Default: ""
+    - Config:      leave_parts_on_error
+    - Env Var:     RCLONE_S3_LEAVE_PARTS_ON_ERROR
+    - Type:        bool
+    - Default:     false
 
-–b2-test-mode
+    #### --s3-list-chunk
 
-A flag string for X-Bz-Test-Mode header for debugging.
+    Size of listing chunk (response list for each ListObject S3 request).
 
-This is for debugging purposes only. Setting it to one of the strings
-below will cause b2 to return specific errors:
+    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 [AWS S3](https://docs.aws.amazon.com/cli/latest/reference/s3/ls.html).
+    In Ceph, this can be increased with the "rgw list buckets max chunk" option.
 
--   “fail_some_uploads”
--   “expire_some_account_authorization_tokens”
--   “force_cap_exceeded”
 
-These will be set in the “X-Bz-Test-Mode” header which is documented in
-the b2 integrations checklist.
+    - Config:      list_chunk
+    - Env Var:     RCLONE_S3_LIST_CHUNK
+    - Type:        int
+    - Default:     1000
 
--   Config: test_mode
--   Env Var: RCLONE_B2_TEST_MODE
--   Type: string
--   Default: ""
+    #### --s3-no-check-bucket
 
-–b2-versions
+    If set don't attempt to check the bucket exists or create it
 
-Include old versions in directory listings. Note that when using this no
-file write operations are permitted, so you can’t upload files or delete
-them.
+    This can be useful when trying to minimise the number of transactions
+    rclone does if you know the bucket exists already.
 
--   Config: versions
--   Env Var: RCLONE_B2_VERSIONS
--   Type: bool
--   Default: false
 
-–b2-upload-cutoff
+    - Config:      no_check_bucket
+    - Env Var:     RCLONE_S3_NO_CHECK_BUCKET
+    - Type:        bool
+    - Default:     false
 
-Cutoff for switching to chunked upload.
+    #### --s3-encoding
 
-Files above this size will be uploaded in chunks of “–b2-chunk-size”.
+    This sets the encoding for the backend.
 
-This value should be set no larger than 4.657GiB (== 5GB).
+    See: the [encoding section in the overview](https://rclone.org/overview/#encoding) for more info.
 
--   Config: upload_cutoff
--   Env Var: RCLONE_B2_UPLOAD_CUTOFF
--   Type: SizeSuffix
--   Default: 200M
+    - Config:      encoding
+    - Env Var:     RCLONE_S3_ENCODING
+    - Type:        MultiEncoder
+    - Default:     Slash,InvalidUtf8,Dot
 
-–b2-chunk-size
+    #### --s3-memory-pool-flush-time
 
-Upload chunk size. Must fit in memory.
+    How often internal memory buffer pools will be flushed.
+    Uploads which requires additional buffers (f.e multipart) will use memory pool for allocations.
+    This option controls how often unused buffers will be removed from the pool.
 
-When uploading large files, chunk the file into this size. Note that
-these chunks are buffered in memory and there might a maximum of
-“–transfers” chunks in progress at once. 5,000,000 Bytes is the minimum
-size.
+    - Config:      memory_pool_flush_time
+    - Env Var:     RCLONE_S3_MEMORY_POOL_FLUSH_TIME
+    - Type:        Duration
+    - Default:     1m0s
 
--   Config: chunk_size
--   Env Var: RCLONE_B2_CHUNK_SIZE
--   Type: SizeSuffix
--   Default: 96M
+    #### --s3-memory-pool-use-mmap
 
-–b2-disable-checksum
+    Whether to use mmap buffers in internal memory pool.
 
-Disable checksums for large (> upload cutoff) files
+    - Config:      memory_pool_use_mmap
+    - Env Var:     RCLONE_S3_MEMORY_POOL_USE_MMAP
+    - Type:        bool
+    - Default:     false
 
-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.
+    ### Backend commands
 
--   Config: disable_checksum
--   Env Var: RCLONE_B2_DISABLE_CHECKSUM
--   Type: bool
--   Default: false
+    Here are the commands specific to the s3 backend.
 
-–b2-download-url
+    Run them with
 
-Custom endpoint for downloads.
+        rclone backend COMMAND remote:
 
-This is usually set to a Cloudflare CDN URL as Backblaze offers free
-egress for data downloaded through the Cloudflare network. This is
-probably only useful for a public bucket. Leave blank if you want to use
-the endpoint provided by Backblaze.
+    The help below will explain what arguments each command takes.
 
--   Config: download_url
--   Env Var: RCLONE_B2_DOWNLOAD_URL
--   Type: string
--   Default: ""
+    See [the "rclone backend" command](https://rclone.org/commands/rclone_backend/) for more
+    info on how to pass options and arguments.
 
-–b2-download-auth-duration
+    These can be run on a running backend using the rc command
+    [backend/command](https://rclone.org/rc/#backend/command).
 
-Time before the authorization token will expire in s or suffix
-ms|s|m|h|d.
+    #### restore
 
-The duration before the download authorization token will expire. The
-minimum value is 1 second. The maximum value is one week.
+    Restore objects from GLACIER to normal storage
 
--   Config: download_auth_duration
--   Env Var: RCLONE_B2_DOWNLOAD_AUTH_DURATION
--   Type: Duration
--   Default: 1w
+        rclone backend restore remote: [options] [<arguments>+]
 
-–b2-encoding
+    This command can be used to restore one or more objects from GLACIER
+    to normal storage.
 
-This sets the encoding for the backend.
+    Usage Examples:
 
-See: the encoding section in the overview for more info.
+        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]
 
--   Config: encoding
--   Env Var: RCLONE_B2_ENCODING
--   Type: MultiEncoder
--   Default: Slash,BackSlash,Del,Ctl,InvalidUtf8,Dot
+    This flag also obeys the filters. Test first with -i/--interactive or --dry-run flags
 
+        rclone -i backend restore --include "*.txt" s3:bucket/path -o priority=Standard
 
-Box
+    All the objects shown will be marked for restore, then
 
-Paths are specified as remote:path
+        rclone backend restore --include "*.txt" s3:bucket/path -o priority=Standard
 
-Paths may be as deep as required, eg remote:directory/subdirectory.
+    It returns a list of status dictionaries with Remote and Status
+    keys. The Status will be OK if it was successfull or an error message
+    if not.
 
-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. rclone config walks you through it.
+        [
+            {
+                "Status": "OK",
+                "Path": "test.txt"
+            },
+            {
+                "Status": "OK",
+                "Path": "test/file4.txt"
+            }
+        ]
 
-Here is an example of how to make a remote called remote. First run:
 
-     rclone config
 
-This will guide you through an interactive setup process:
+    Options:
 
+    - "description": The optional description for the job.
+    - "lifetime": Lifetime of the active copy in days
+    - "priority": Priority of restore: Standard|Expedited|Bulk
+
+    #### list-multipart-uploads
+
+    List the unfinished multipart uploads
+
+        rclone backend list-multipart-uploads remote: [options] [<arguments>+]
+
+    This command lists the unfinished multipart uploads in JSON format.
+
+        rclone backend list-multipart s3:bucket/path/to/object
+
+    It returns a dictionary of buckets with values as lists of unfinished
+    multipart uploads.
+
+    You can call it with no bucket in which case it lists all bucket, with
+    a bucket or with a bucket and path.
+
+        {
+          "rclone": [
+            {
+              "Initiated": "2020-06-26T14:20:36Z",
+              "Initiator": {
+                "DisplayName": "XXX",
+                "ID": "arn:aws:iam::XXX:user/XXX"
+              },
+              "Key": "KEY",
+              "Owner": {
+                "DisplayName": null,
+                "ID": "XXX"
+              },
+              "StorageClass": "STANDARD",
+              "UploadId": "XXX"
+            }
+          ],
+          "rclone-1000files": [],
+          "rclone-dst": []
+        }
+
+
+
+    #### cleanup
+
+    Remove unfinished multipart uploads.
+
+        rclone backend cleanup remote: [options] [<arguments>+]
+
+    This command removes unfinished multipart uploads of age greater than
+    max-age which defaults to 24 hours.
+
+    Note that you can use -i/--dry-run with this command to see what it
+    would do.
+
+        rclone backend cleanup s3:bucket/path/to/object
+        rclone backend cleanup -o max-age=7w s3:bucket/path/to/object
+
+    Durations are parsed as per the rest of rclone, 2h, 7d, 7w etc.
+
+
+    Options:
+
+    - "max-age": Max age of upload to delete
+
+
+
+    ### Anonymous access to public buckets ###
+
+    If you want to use rclone to access a public bucket, configure with a
+    blank `access_key_id` and `secret_access_key`.  Your config should end
+    up looking like this:
+
+[anons3] type = s3 provider = AWS env_auth = false access_key_id =
+secret_access_key = region = us-east-1 endpoint = location_constraint =
+acl = private server_side_encryption = storage_class =
+
+
+    Then use it as normal with the name of the public bucket, eg
+
+        rclone lsd anons3:1000genomes
+
+    You will be able to list and copy data but not upload it.
+
+    ### Ceph ###
+
+    [Ceph](https://ceph.com/) is an open source unified, distributed
+    storage system designed for excellent performance, reliability and
+    scalability.  It has an S3 compatible object storage interface.
+
+    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:
+
+[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 =
+
+
+    If you are using an older version of CEPH, eg 10.2.x Jewel, then you
+    may need to supply the parameter `--s3-upload-cutoff 0` or put this in
+    the config file as `upload_cutoff 0` to work around a bug which causes
+    uploading of small files to fail.
+
+    Note also that Ceph sometimes puts `/` 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 `/` escaped as `\/`.  Make sure you
+    only write `/` in the secret access key.
+
+    Eg the dump from Ceph looks something like this (irrelevant keys
+    removed).
+
+{ "user_id": "xxx", "display_name": "xxxx", "keys": [ { "user": "xxx",
+"access_key": "xxxxxx", "secret_key": "xxxxxx/xxxx" } ], }
+
+
+    Because this is a json dump, it is encoding the `/` as `\/`, so if you
+    use the secret key as `xxxxxx/xxxx`  it will work fine.
+
+    ### Dreamhost ###
+
+    Dreamhost [DreamObjects](https://www.dreamhost.com/cloud/storage/) is
+    an object storage system based on CEPH.
+
+    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:
+
+[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 =
+
+
+    ### DigitalOcean Spaces ###
+
+    [Spaces](https://www.digitalocean.com/products/object-storage/) is an [S3-interoperable](https://developers.digitalocean.com/documentation/spaces/) object storage service from cloud provider DigitalOcean.
+
+    To connect to DigitalOcean Spaces you will need an access key and secret key. These can be retrieved on the "[Applications & API](https://cloud.digitalocean.com/settings/api/tokens)" page of the DigitalOcean control panel. They will be needed when prompted by `rclone config` for your `access_key_id` and `secret_access_key`.
+
+    When prompted for a `region` or `location_constraint`, press enter to use the default value. The region must be included in the `endpoint` setting (e.g. `nyc3.digitaloceanspaces.com`). The default values can be used for other settings.
+
+    Going through the whole process of creating a new remote by running `rclone config`, each prompt should be answered as shown below:
+
+Storage> s3 env_auth> 1 access_key_id> YOUR_ACCESS_KEY
+secret_access_key> YOUR_SECRET_KEY region> endpoint>
+nyc3.digitaloceanspaces.com location_constraint> acl> storage_class>
+
+
+    The resulting configuration file should look like:
+
+[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 =
+
+
+    Once configured, you can create a new Space and begin copying files. For example:
+
+rclone mkdir spaces:my-new-space rclone copy /path/to/files
+spaces:my-new-space
+
+
+    ### IBM COS (S3) ###
+
+    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)
+
+    To configure access to IBM COS S3, follow the steps below:
+
+    1. Run rclone config and select n for a new remote.
+
+    2018/02/14 14:13:11 NOTICE: Config file "C:\\Users\\a\\.config\\rclone\\rclone.conf" not found - using defaults
     No remotes found - make a new one
     n) New remote
     s) Set configuration password
     q) Quit config
     n/s/q> n
-    name> remote
-    Type of storage to configure.
+
+
+    2. Enter the name for the configuration
+
+    name> <YOUR NAME>
+
+
+    3. Select "s3" storage.
+
+Choose a number from below, or type in your own value 1 / Alias for an
+existing remote  "alias" 2 / Amazon Drive  "amazon cloud drive" 3 /
+Amazon S3 Complaint Storage Providers (Dreamhost, Ceph, Minio, IBM COS)
+ "s3" 4 / Backblaze B2  "b2" [snip] 23 / http Connection  "http"
+Storage> 3
+
+
+    4. Select IBM COS as the S3 Storage Provider.
+
+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  "AWS" 2 /
+Choose this option to configure Storage to Ceph Systems  "Ceph" 3 /
+Choose this option to configure Storage to Dreamhost  "Dreamhost" 4 /
+Choose this option to the configure Storage to IBM COS S3  "IBMCOS" 5 /
+Choose this option to the configure Storage to Minio  "Minio" Provider>4
+
+
+    5. Enter the Access Key and Secret.
+
+    AWS Access Key ID - leave blank for anonymous access or runtime credentials.
+    access_key_id> <>
+    AWS Secret Access Key (password) - leave blank for anonymous access or runtime credentials.
+    secret_access_key> <>
+
+
+    6. Specify the endpoint for IBM COS. For Public IBM COS, choose from the option below. For On Premise IBM COS, enter an enpoint address.
+
+    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
-    [snip]
-    XX / Box
-       \ "box"
-    [snip]
-    Storage> box
-    Box App Client Id - leave blank normally.
-    client_id> 
-    Box App Client Secret - leave blank normally.
-    client_secret>
+     1 / US Cross Region Endpoint
+       \ "s3-api.us-geo.objectstorage.softlayer.net"
+     2 / US Cross Region Dallas Endpoint
+       \ "s3-api.dal.us-geo.objectstorage.softlayer.net"
+     3 / US Cross Region Washington DC Endpoint
+       \ "s3-api.wdc-us-geo.objectstorage.softlayer.net"
+     4 / US Cross Region San Jose Endpoint
+       \ "s3-api.sjc-us-geo.objectstorage.softlayer.net"
+     5 / US Cross Region Private Endpoint
+       \ "s3-api.us-geo.objectstorage.service.networklayer.com"
+     6 / US Cross Region Dallas Private Endpoint
+       \ "s3-api.dal-us-geo.objectstorage.service.networklayer.com"
+     7 / US Cross Region Washington DC Private Endpoint
+       \ "s3-api.wdc-us-geo.objectstorage.service.networklayer.com"
+     8 / US Cross Region San Jose Private Endpoint
+       \ "s3-api.sjc-us-geo.objectstorage.service.networklayer.com"
+     9 / US Region East Endpoint
+       \ "s3.us-east.objectstorage.softlayer.net"
+    10 / US Region East Private Endpoint
+       \ "s3.us-east.objectstorage.service.networklayer.com"
+    11 / US Region South Endpoint
+
+[snip] 34 / Toronto Single Site Private Endpoint
+ "s3.tor01.objectstorage.service.networklayer.com" endpoint>1
+
+
+
+    7. 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
+
+     1 / US Cross Region Standard
+       \ "us-standard"
+     2 / US Cross Region Vault
+       \ "us-vault"
+     3 / US Cross Region Cold
+       \ "us-cold"
+     4 / US Cross Region Flex
+       \ "us-flex"
+     5 / US East Region Standard
+       \ "us-east-standard"
+     6 / US East Region Vault
+       \ "us-east-vault"
+     7 / US East Region Cold
+       \ "us-east-cold"
+     8 / US East Region Flex
+       \ "us-east-flex"
+     9 / US South Region Standard
+       \ "us-south-standard"
+    10 / US South Region Vault
+       \ "us-south-vault"
+
+[snip] 32 / Toronto Flex  "tor01-flex" location_constraint>1
+
+
+    9. Specify a canned ACL. IBM Cloud (Strorage) supports "public-read" and "private". IBM Cloud(Infra) supports all the canned ACLs. On-Premise COS supports all the canned ACLs.
+
+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
+ "private" 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  "public-read" 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  "public-read-write" 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  "authenticated-read" acl> 1
+
+
+
+    12. Review the displayed configuration and accept to save the "remote" then quit. The config file should look like this
+
+    [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
+
+
+    13. Execute rclone commands
+
+    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
+
+
+    ### Minio ###
+
+    [Minio](https://minio.io/) is an object storage server built for cloud application developers and devops.
+
+    It is very easy to install and provides an S3 compatible server which can be used by rclone.
+
+    To use it, install Minio following the instructions [here](https://docs.minio.io/docs/minio-quickstart-guide).
+
+    When it configures itself Minio will print something like this
+
+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
+
+
+    These details need to go into `rclone config` like this.  Note that it
+    is important to put the region in as stated above.
+
+env_auth> 1 access_key_id> USWUXHGYZQYFYFFIT3RE secret_access_key>
+MOJRH0mkL1IPauahWITSVvyDrQbEEIwljvmxdq03 region> us-east-1 endpoint>
+http://192.168.1.106:9000 location_constraint> server_side_encryption>
+
+
+    Which makes the config file look like this
+
+[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 =
+
+
+    So once set up, for example to copy files into a bucket
+
+rclone copy /path/to/files minio:bucket
+
+
+    ### Scaleway {#scaleway}
+
+    [Scaleway](https://www.scaleway.com/object-storage/) 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.
+
+    Scaleway provides an S3 interface which can be configured for use with rclone like this:
+
+[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 = acl = private server_side_encryption =
+storage_class =
+
+
+    ### Wasabi ###
+
+    [Wasabi](https://wasabi.com) 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.
+
+    Wasabi provides an S3 interface which can be configured for use with
+    rclone like this.
+
+No remotes found - make a new one n) New remote s) Set configuration
+password n/s> n name> wasabi Type of storage to configure. Choose a
+number from below, or type in your own value [snip] XX / Amazon S3 (also
+Dreamhost, Ceph, Minio)  "s3" [snip] Storage> 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  "false" 2 / Get AWS credentials from the
+environment (env vars or IAM)  "true" env_auth> 1 AWS Access Key ID -
+leave blank for anonymous access or runtime credentials. access_key_id>
+YOURACCESSKEY AWS Secret Access Key (password) - leave blank for
+anonymous access or runtime credentials. secret_access_key>
+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.  "us-east-1" [snip] region> 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> 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.  "" [snip] location_constraint> 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).  "private" [snip]
+acl> 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
+ "" 2 / AES256  "AES256" server_side_encryption> The storage class to
+use when storing objects in S3. Choose a number from below, or type in
+your own value 1 / Default  "" 2 / Standard storage class  "STANDARD" 3
+/ Reduced redundancy storage class  "REDUCED_REDUNDANCY" 4 / Standard
+Infrequent Access storage class  "STANDARD_IA" storage_class> 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> y
+
+
+    This will leave the config file looking like this.
+
+[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 =
+
+
+    ### Alibaba OSS {#alibaba-oss}
+
+    Here is an example of making an [Alibaba Cloud (Aliyun) OSS](https://www.alibabacloud.com/product/oss/)
+    configuration.  First run:
+
+        rclone config
+
+    This will guide you through an interactive setup process.
+
+No remotes found - make a new one n) New remote s) Set configuration
+password q) Quit config n/s/q> n name> oss Type of storage to configure.
+Enter a string value. Press Enter for the default (""). Choose a number
+from below, or type in your own value [snip] 4 / Amazon S3 Compliant
+Storage Provider (AWS, Alibaba, Ceph, Digital Ocean, Dreamhost, IBM COS,
+Minio, etc)  "s3" [snip] Storage> s3 Choose your S3 provider. Enter a
+string value. Press Enter for the default (""). Choose a number from
+below, or type in your own value 1 / Amazon Web Services (AWS) S3  "AWS"
+2 / Alibaba Cloud Object Storage System (OSS) formerly Aliyun  "Alibaba"
+3 / Ceph Object Storage  "Ceph" [snip] provider> 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 ("false"). Choose a number from below, or type in your own value
+1 / Enter AWS credentials in the next step  "false" 2 / Get AWS
+credentials from the environment (env vars or IAM)  "true" env_auth> 1
+AWS Access Key ID. Leave blank for anonymous access or runtime
+credentials. Enter a string value. Press Enter for the default ("").
+access_key_id> accesskeyid AWS Secret Access Key (password) Leave blank
+for anonymous access or runtime credentials. Enter a string value. Press
+Enter for the default (""). secret_access_key> secretaccesskey Endpoint
+for OSS API. Enter a string value. Press Enter for the default ("").
+Choose a number from below, or type in your own value 1 / East China 1
+(Hangzhou)  "oss-cn-hangzhou.aliyuncs.com" 2 / East China 2 (Shanghai)
+ "oss-cn-shanghai.aliyuncs.com" 3 / North China 1 (Qingdao)
+ "oss-cn-qingdao.aliyuncs.com" [snip] endpoint> 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't copy the ACL from the source but rather writes a fresh one.
+Enter a string value. Press Enter for the default (""). Choose a number
+from below, or type in your own value 1 / Owner gets FULL_CONTROL. No
+one else has access rights (default).  "private" 2 / Owner gets
+FULL_CONTROL. The AllUsers group gets READ access.  "public-read" /
+Owner gets FULL_CONTROL. The AllUsers group gets READ and WRITE access.
+[snip] acl> 1 The storage class to use when storing new objects in OSS.
+Enter a string value. Press Enter for the default (""). Choose a number
+from below, or type in your own value 1 / Default  "" 2 / Standard
+storage class  "STANDARD" 3 / Archive storage mode.  "GLACIER" 4 /
+Infrequent access storage mode.  "STANDARD_IA" storage_class> 1 Edit
+advanced config? (y/n) y) Yes n) No y/n> 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> y
+
+
+    ### Netease NOS  ###
+
+    For Netease NOS configure as per the configurator `rclone config`
+    setting the provider `Netease`.  This will automatically set
+    `force_path_style = false` which is necessary for it to run properly.
+
+     Backblaze B2
+    ----------------------------------------
+
+    B2 is [Backblaze's cloud storage system](https://www.backblaze.com/b2/).
+
+    Paths are specified as `remote:bucket` (or `remote:` for the `lsd`
+    command.)  You may put subdirectories in too, eg `remote:bucket/path/to/dir`.
+
+    Here is an example of making a b2 configuration.  First run
+
+        rclone config
+
+    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.
+
+No remotes found - make a new one n) New remote q) Quit config n/q> n
+name> remote Type of storage to configure. Choose a number from below,
+or type in your own value [snip] XX / Backblaze B2  "b2" [snip] Storage>
+b2 Account ID or Application Key ID account> 123456789abc Application
+Key key> 0123456789abcdef0123456789abcdef0123456789 Endpoint for the
+service - leave blank normally. endpoint> Remote config
+-------------------- [remote] account = 123456789abc key =
+0123456789abcdef0123456789abcdef0123456789 endpoint =
+-------------------- y) Yes this is OK e) Edit this remote d) Delete
+this remote y/e/d> y
+
+
+    This remote is called `remote` and can now be used like this
+
+    See all buckets
+
+        rclone lsd remote:
+
+    Create a new bucket
+
+        rclone mkdir remote:bucket
+
+    List the contents of a bucket
+
+        rclone ls remote:bucket
+
+    Sync `/home/local/directory` to the remote bucket, deleting any
+    excess files in the bucket.
+
+        rclone sync -i /home/local/directory remote:bucket
+
+    ### Application Keys ###
+
+    B2 supports multiple [Application Keys for different access permission
+    to B2 Buckets](https://www.backblaze.com/b2/docs/application_keys.html).
+
+    You can use these with rclone too; you will need to use rclone version 1.43
+    or later.
+
+    Follow Backblaze's docs to create an Application Key with the required
+    permission and add the `applicationKeyId` as the `account` and the
+    `Application Key` itself as the `key`.
+
+    Note that you must put the _applicationKeyId_ as the `account` – you
+    can't use the master Account ID.  If you try then B2 will return 401
+    errors.
+
+    ### --fast-list ###
+
+    This remote supports `--fast-list` which allows you to use fewer
+    transactions in exchange for more memory. See the [rclone
+    docs](https://rclone.org/docs/#fast-list) for more details.
+
+    ### Modified time ###
+
+    The modified time is stored as metadata on the object as
+    `X-Bz-Info-src_last_modified_millis` as milliseconds since 1970-01-01
+    in the Backblaze standard.  Other tools should be able to use this as
+    a modified time.
+
+    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.
+
+    #### Restricted filename characters
+
+    In addition to the [default restricted characters set](https://rclone.org/overview/#restricted-characters)
+    the following characters are also replaced:
+
+    | Character | Value | Replacement |
+    | --------- |:-----:|:-----------:|
+    | \         | 0x5C  | ＼           |
+
+    Invalid UTF-8 bytes will also be [replaced](https://rclone.org/overview/#invalid-utf8),
+    as they can't be used in JSON strings.
+
+    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
+    `--b2-encoding` flag below and remove the `BackSlash` from the
+    string. This can be set in the config.
+
+    ### SHA1 checksums ###
+
+    The SHA1 checksums of the files are checked on upload and download and
+    will be used in the syncing process.
+
+    Large files (bigger than the limit in `--b2-upload-cutoff`) which are
+    uploaded in chunks will store their SHA1 on the object as
+    `X-Bz-Info-large_file_sha1` as recommended by Backblaze.
+
+    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 [the overview](https://rclone.org/overview/#features) for exactly which remotes
+    support SHA1.
+
+    Sources which don't support SHA1, in particular `crypt` will upload
+    large files without SHA1 checksums.  This may be fixed in the future
+    (see [#1767](https://github.com/rclone/rclone/issues/1767)).
+
+    Files sizes below `--b2-upload-cutoff` will always have an SHA1
+    regardless of the source.
+
+    ### Transfers ###
+
+    Backblaze recommends that you do lots of transfers simultaneously for
+    maximum speed.  In tests from my SSD equipped laptop the optimum
+    setting is about `--transfers 32` 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 `--transfers 4` is
+    definitely too low for Backblaze B2 though.
+
+    Note that uploading big files (bigger than 200 MB by default) will use
+    a 96 MB RAM buffer by default.  There can be at most `--transfers` of
+    these in use at any moment, so this sets the upper limit on the memory
+    used.
+
+    ### Versions ###
+
+    When rclone uploads a new version of a file it creates a [new version
+    of it](https://www.backblaze.com/b2/docs/file_versions.html).
+    Likewise when you delete a file, the old version will be marked hidden
+    and still be available.  Conversely, you may opt in to a "hard delete"
+    of files with the `--b2-hard-delete` flag which would permanently remove
+    the file instead of hiding it.
+
+    Old versions of files, where available, are visible using the 
+    `--b2-versions` flag.
+
+    **NB** Note that `--b2-versions` does not work with crypt at the
+    moment [#1627](https://github.com/rclone/rclone/issues/1627). Using
+    [--backup-dir](https://rclone.org/docs/#backup-dir-dir) with rclone is the recommended
+    way of working around this.
+
+    If you wish to remove all the old versions then you can use the
+    `rclone cleanup remote:bucket` 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,
+    eg `rclone cleanup remote:bucket/path/to/stuff`.
+
+    Note that `cleanup` will remove partially uploaded files from the bucket
+    if they are more than a day old.
+
+    When you `purge` a bucket, the current and the old versions will be
+    deleted then the bucket will be deleted.
+
+    However `delete` will cause the current versions of the files to
+    become hidden old versions.
+
+    Here is a session showing the listing and retrieval of an old
+    version followed by a `cleanup` of the old versions.
+
+    Show current version and all the versions with `--b2-versions` flag.
+
+$ 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
+
+
+    Retrieve an old version
+
+$ 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
+
+
+    Clean up all the old versions and show that they've gone.
+
+$ 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
+
+
+    ### Data usage ###
+
+    It is useful to know how many requests are sent to the server in different scenarios.
+
+    All copy commands send the following 4 requests:
+
+/b2api/v1/b2_authorize_account /b2api/v1/b2_create_bucket
+/b2api/v1/b2_list_buckets /b2api/v1/b2_list_file_names
+
+
+    The `b2_list_file_names` 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
+    [#818](https://github.com/rclone/rclone/issues/818) 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.
+
+    Uploading files that do not require chunking, will send 2 requests per
+    file upload:
+
+/b2api/v1/b2_get_upload_url /b2api/v1/b2_upload_file/
+
+
+    Uploading files requiring chunking, will send 2 requests (one each to
+    start and finish the upload) and another 2 requests for each chunk:
+
+/b2api/v1/b2_start_large_file /b2api/v1/b2_get_upload_part_url
+/b2api/v1/b2_upload_part/ /b2api/v1/b2_finish_large_file
+
+
+    #### Versions ####
+
+    Versions can be viewed with the `--b2-versions` flag. When it is set
+    rclone will show and act on older versions of files.  For example
+
+    Listing without `--b2-versions`
+
+$ rclone -q ls b2:cleanup-test 9 one.txt
+
+
+    And with
+
+$ 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
+
+
+    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.
+
+    Note that when using `--b2-versions` no file write operations are
+    permitted, so you can't upload files or delete them.
+
+    ### B2 and rclone link ###
+
+    Rclone supports generating file share links for private B2 buckets.
+    They can either be for a file for example:
+
+./rclone link B2:bucket/path/to/file.txt
+https://f002.backblazeb2.com/file/bucket/path/to/file.txt?Authorization=xxxxxxxx
+
+
+    or if run on a directory you will get:
+
+./rclone link B2:bucket/path
+https://f002.backblazeb2.com/file/bucket/path?Authorization=xxxxxxxx
+
+
+    you can then use the authorization token (the part of the url from the
+     `?Authorization=` on) on any file path under that directory. For example:
+
+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
+
+
+
+    ### Standard Options
+
+    Here are the standard options specific to b2 (Backblaze B2).
+
+    #### --b2-account
+
+    Account ID or Application Key ID
+
+    - Config:      account
+    - Env Var:     RCLONE_B2_ACCOUNT
+    - Type:        string
+    - Default:     ""
+
+    #### --b2-key
+
+    Application Key
+
+    - Config:      key
+    - Env Var:     RCLONE_B2_KEY
+    - Type:        string
+    - Default:     ""
+
+    #### --b2-hard-delete
+
+    Permanently delete files on remote removal, otherwise hide files.
+
+    - Config:      hard_delete
+    - Env Var:     RCLONE_B2_HARD_DELETE
+    - Type:        bool
+    - Default:     false
+
+    ### Advanced Options
+
+    Here are the advanced options specific to b2 (Backblaze B2).
+
+    #### --b2-endpoint
+
+    Endpoint for the service.
+    Leave blank normally.
+
+    - Config:      endpoint
+    - Env Var:     RCLONE_B2_ENDPOINT
+    - Type:        string
+    - Default:     ""
+
+    #### --b2-test-mode
+
+    A flag string for X-Bz-Test-Mode header for debugging.
+
+    This is for debugging purposes only. Setting it to one of the strings
+    below will cause b2 to return specific errors:
+
+      * "fail_some_uploads"
+      * "expire_some_account_authorization_tokens"
+      * "force_cap_exceeded"
+
+    These will be set in the "X-Bz-Test-Mode" header which is documented
+    in the [b2 integrations checklist](https://www.backblaze.com/b2/docs/integration_checklist.html).
+
+    - Config:      test_mode
+    - Env Var:     RCLONE_B2_TEST_MODE
+    - Type:        string
+    - Default:     ""
+
+    #### --b2-versions
+
+    Include old versions in directory listings.
+    Note that when using this no file write operations are permitted,
+    so you can't upload files or delete them.
+
+    - Config:      versions
+    - Env Var:     RCLONE_B2_VERSIONS
+    - Type:        bool
+    - Default:     false
+
+    #### --b2-upload-cutoff
+
+    Cutoff for switching to chunked upload.
+
+    Files above this size will be uploaded in chunks of "--b2-chunk-size".
+
+    This value should be set no larger than 4.657GiB (== 5GB).
+
+    - Config:      upload_cutoff
+    - Env Var:     RCLONE_B2_UPLOAD_CUTOFF
+    - Type:        SizeSuffix
+    - Default:     200M
+
+    #### --b2-copy-cutoff
+
+    Cutoff for switching to multipart copy
+
+    Any files larger than this that need to be server side copied will be
+    copied in chunks of this size.
+
+    The minimum is 0 and the maximum is 4.6GB.
+
+    - Config:      copy_cutoff
+    - Env Var:     RCLONE_B2_COPY_CUTOFF
+    - Type:        SizeSuffix
+    - Default:     4G
+
+    #### --b2-chunk-size
+
+    Upload chunk size. Must fit in memory.
+
+    When uploading large files, chunk the file into this size.  Note that
+    these chunks are buffered in memory and there might a maximum of
+    "--transfers" chunks in progress at once.  5,000,000 Bytes is the
+    minimum size.
+
+    - Config:      chunk_size
+    - Env Var:     RCLONE_B2_CHUNK_SIZE
+    - Type:        SizeSuffix
+    - Default:     96M
+
+    #### --b2-disable-checksum
+
+    Disable checksums for large (> upload cutoff) files
+
+    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.
+
+    - Config:      disable_checksum
+    - Env Var:     RCLONE_B2_DISABLE_CHECKSUM
+    - Type:        bool
+    - Default:     false
+
+    #### --b2-download-url
+
+    Custom endpoint for downloads.
+
+    This is usually set to a Cloudflare CDN URL as Backblaze offers
+    free egress for data downloaded through the Cloudflare network.
+    This is probably only useful for a public bucket.
+    Leave blank if you want to use the endpoint provided by Backblaze.
+
+    - Config:      download_url
+    - Env Var:     RCLONE_B2_DOWNLOAD_URL
+    - Type:        string
+    - Default:     ""
+
+    #### --b2-download-auth-duration
+
+    Time before the authorization token will expire in s or suffix ms|s|m|h|d.
+
+    The duration before the download authorization token will expire.
+    The minimum value is 1 second. The maximum value is one week.
+
+    - Config:      download_auth_duration
+    - Env Var:     RCLONE_B2_DOWNLOAD_AUTH_DURATION
+    - Type:        Duration
+    - Default:     1w
+
+    #### --b2-memory-pool-flush-time
+
+    How often internal memory buffer pools will be flushed.
+    Uploads which requires additional buffers (f.e multipart) will use memory pool for allocations.
+    This option controls how often unused buffers will be removed from the pool.
+
+    - Config:      memory_pool_flush_time
+    - Env Var:     RCLONE_B2_MEMORY_POOL_FLUSH_TIME
+    - Type:        Duration
+    - Default:     1m0s
+
+    #### --b2-memory-pool-use-mmap
+
+    Whether to use mmap buffers in internal memory pool.
+
+    - Config:      memory_pool_use_mmap
+    - Env Var:     RCLONE_B2_MEMORY_POOL_USE_MMAP
+    - Type:        bool
+    - Default:     false
+
+    #### --b2-encoding
+
+    This sets the encoding for the backend.
+
+    See: the [encoding section in the overview](https://rclone.org/overview/#encoding) for more info.
+
+    - Config:      encoding
+    - Env Var:     RCLONE_B2_ENCODING
+    - Type:        MultiEncoder
+    - Default:     Slash,BackSlash,Del,Ctl,InvalidUtf8,Dot
+
+
+
+     Box
+    -----------------------------------------
+
+    Paths are specified as `remote:path`
+
+    Paths may be as deep as required, eg `remote:directory/subdirectory`.
+
+    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.  `rclone config` walks you through it.
+
+    Here is an example of how to make a remote called `remote`.  First run:
+
+         rclone config
+
+    This will guide you through an interactive setup process:
+
+No remotes found - make a new one n) New remote s) Set configuration
+password q) Quit config n/s/q> n name> remote Type of storage to
+configure. Choose a number from below, or type in your own value [snip]
+XX / Box  "box" [snip] Storage> box Box App Client Id - leave blank
+normally. client_id> Box App Client Secret - leave blank normally.
+client_secret> Box App config.json location Leave blank normally. Enter
+a string value. Press Enter for the default (""). box_config_file> Box
+App Primary Access Token Leave blank normally. Enter a string value.
+Press Enter for the default (""). access_token>
+
+Enter a string value. Press Enter for the default ("user"). Choose a
+number from below, or type in your own value 1 / Rclone should act on
+behalf of a user  "user" 2 / Rclone should act on behalf of a service
+account  "enterprise" box_sub_type> Remote config Use auto config? * Say
+Y if not sure * Say N if you are working on a remote or headless machine
+y) Yes n) No y/n> y If your browser doesn'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 -------------------- [remote]
+client_id = client_secret = token =
+{"access_token":"XXX","token_type":"bearer","refresh_token":"XXX","expiry":"XXX"}
+-------------------- y) Yes this is OK e) Edit this remote d) Delete
+this remote y/e/d> y
+
+
+    See the [remote setup docs](https://rclone.org/remote_setup/) for how to set it up on a
+    machine with no Internet browser available.
+
+    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 `http://127.0.0.1:53682/` and this it may require you to unblock
+    it temporarily if you are running a host firewall.
+
+    Once configured you can then use `rclone` like this,
+
+    List directories in top level of your Box
+
+        rclone lsd remote:
+
+    List all the files in your Box
+
+        rclone ls remote:
+
+    To copy a local directory to an Box directory called backup
+
+        rclone copy /home/source remote:backup
+
+    ### Using rclone with an Enterprise account with SSO ###
+
+    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.
+
+    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.
+
+    ### Invalid refresh token ###
+
+    According to the [box docs](https://developer.box.com/v2.0/docs/oauth-20#section-6-using-the-access-and-refresh-tokens):
+
+    > Each refresh_token is valid for one use in 60 days.
+
+    This means that if you
+
+      * Don't use the box remote for 60 days
+      * Copy the config file with a box refresh token in and use it in two places
+      * Get an error on a token refresh
+
+    then rclone will return an error which includes the text `Invalid
+    refresh token`.
+
+    To fix this you will need to use oauth2 again to update the refresh
+    token.  You can use the methods in [the remote setup
+    docs](https://rclone.org/remote_setup/), 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.
+
+    Here is how to do it.
+
+$ rclone config Current remotes:
+
+Name Type ==== ==== remote box
+
+e)  Edit existing remote
+f)  New remote
+g)  Delete remote
+h)  Rename remote
+i)  Copy remote
+j)  Set configuration password
+k)  Quit config e/n/d/r/c/s/q> e Choose a number from below, or type in
+    an existing value 1 > remote remote> remote --------------------
+    [remote] type = box token =
+    {"access_token":"XXX","token_type":"bearer","refresh_token":"XXX","expiry":"2017-07-08T23:40:08.059167677+01:00"}
+    -------------------- Edit remote Value "client_id" = "" Edit? (y/n)>
+l)  Yes
+m)  No y/n> n Value "client_secret" = "" Edit? (y/n)>
+n)  Yes
+o)  No y/n> n Remote config Already have a token - refresh?
+p)  Yes
+q)  No y/n> y Use auto config?
+
+-   Say Y if not sure
+-   Say N if you are working on a remote or headless machine
+
+y)  Yes
+z)  No y/n> y If your browser doesn'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 --------------------
+    [remote] type = box token =
+    {"access_token":"YYY","token_type":"bearer","refresh_token":"YYY","expiry":"2017-07-23T12:22:29.259137901+01:00"}
+    --------------------
+a)  Yes this is OK
+b)  Edit this remote
+c)  Delete this remote y/e/d> y
+
+
+    ### Modified time and hashes ###
+
+    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.
+
+    Box supports SHA1 type hashes, so you can use the `--checksum`
+    flag.
+
+    #### Restricted filename characters
+
+    In addition to the [default restricted characters set](https://rclone.org/overview/#restricted-characters)
+    the following characters are also replaced:
+
+    | Character | Value | Replacement |
+    | --------- |:-----:|:-----------:|
+    | \         | 0x5C  | ＼           |
+
+    File names can also not end with the following characters.
+    These only get replaced if they are the last character in the name:
+
+    | Character | Value | Replacement |
+    | --------- |:-----:|:-----------:|
+    | SP        | 0x20  | ␠           |
+
+    Invalid UTF-8 bytes will also be [replaced](https://rclone.org/overview/#invalid-utf8),
+    as they can't be used in JSON strings.
+
+    ### Transfers ###
+
+    For files above 50MB rclone will use a chunked transfer.  Rclone will
+    upload up to `--transfers` chunks at the same time (shared among all
+    the multipart uploads).  Chunks are buffered in memory and are
+    normally 8MB so increasing `--transfers` will increase memory use.
+
+    ### Deleting files ###
+
+    Depending on the enterprise settings for your user, the item will
+    either be actually deleted from Box or moved to the trash.
+
+    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.
+
+    ### Root folder ID ###
+
+    You can set the `root_folder_id` for rclone.  This is the directory
+    (identified by its `Folder ID`) that rclone considers to be the root
+    of your Box drive.
+
+    Normally you will leave this blank and rclone will determine the
+    correct root to use itself.
+
+    However you can set this to restrict rclone to a specific folder
+    hierarchy.
+
+    In order to do this you will have to find the `Folder ID` 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.
+
+    So if the folder you want rclone to use has a URL which looks like
+    `https://app.box.com/folder/11xxxxxxxxx8`
+    in the browser, then you use `11xxxxxxxxx8` as
+    the `root_folder_id` in the config.
+
+
+    ### Standard Options
+
+    Here are the standard options specific to box (Box).
+
+    #### --box-client-id
+
+    OAuth Client Id
+    Leave blank normally.
+
+    - Config:      client_id
+    - Env Var:     RCLONE_BOX_CLIENT_ID
+    - Type:        string
+    - Default:     ""
+
+    #### --box-client-secret
+
+    OAuth Client Secret
+    Leave blank normally.
+
+    - Config:      client_secret
+    - Env Var:     RCLONE_BOX_CLIENT_SECRET
+    - Type:        string
+    - Default:     ""
+
+    #### --box-box-config-file
+
     Box App config.json location
     Leave blank normally.
-    Enter a string value. Press Enter for the default ("").
-    config_json>
-    'enterprise' or 'user' depending on the type of token being requested.
-    Enter a string value. Press Enter for the default ("user").
-    box_sub_type>
-    Remote config
-    Use auto config?
-     * Say Y if not sure
-     * Say N if you are working on a remote or headless machine
-    y) Yes
-    n) No
-    y/n> y
-    If your browser doesn'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
-    --------------------
-    [remote]
-    client_id = 
-    client_secret = 
-    token = {"access_token":"XXX","token_type":"bearer","refresh_token":"XXX","expiry":"XXX"}
-    --------------------
-    y) Yes this is OK
-    e) Edit this remote
-    d) Delete this remote
-    y/e/d> y
-
-See the remote setup docs for how to set it up on a machine with no
-Internet browser available.
-
-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
-http://127.0.0.1:53682/ and this it may require you to unblock it
-temporarily if you are running a host firewall.
-
-Once configured you can then use rclone like this,
-
-List directories in top level of your Box
-
-    rclone lsd remote:
-
-List all the files in your Box
-
-    rclone ls remote:
-
-To copy a local directory to an Box directory called backup
-
-    rclone copy /home/source remote:backup
-
-Using rclone with an Enterprise account with SSO
-
-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.
-
-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.
-
-Invalid refresh token
-
-According to the box docs:
-
-  Each refresh_token is valid for one use in 60 days.
-
-This means that if you
-
--   Don’t use the box remote for 60 days
--   Copy the config file with a box refresh token in and use it in two
-    places
--   Get an error on a token refresh
-
-then rclone will return an error which includes the text
-Invalid refresh token.
-
-To fix this you will need to use oauth2 again to update the refresh
-token. You can use the methods in the remote setup docs, 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.
-
-Here is how to do it.
-
-    $ 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> e
-    Choose a number from below, or type in an existing value
-     1 > remote
-    remote> remote
-    --------------------
-    [remote]
-    type = box
-    token = {"access_token":"XXX","token_type":"bearer","refresh_token":"XXX","expiry":"2017-07-08T23:40:08.059167677+01:00"}
-    --------------------
-    Edit remote
-    Value "client_id" = ""
-    Edit? (y/n)>
-    y) Yes
-    n) No
-    y/n> n
-    Value "client_secret" = ""
-    Edit? (y/n)>
-    y) Yes
-    n) No
-    y/n> n
-    Remote config
-    Already have a token - refresh?
-    y) Yes
-    n) No
-    y/n> y
-    Use auto config?
-     * Say Y if not sure
-     * Say N if you are working on a remote or headless machine
-    y) Yes
-    n) No
-    y/n> y
-    If your browser doesn'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
-    --------------------
-    [remote]
-    type = box
-    token = {"access_token":"YYY","token_type":"bearer","refresh_token":"YYY","expiry":"2017-07-23T12:22:29.259137901+01:00"}
-    --------------------
-    y) Yes this is OK
-    e) Edit this remote
-    d) Delete this remote
-    y/e/d> y
-
-Modified time and hashes
-
-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.
 
-Box supports SHA1 type hashes, so you can use the --checksum flag.
+    Leading `~` will be expanded in the file name as will environment variables such as `${RCLONE_CONFIG_DIR}`.
 
-Restricted filename characters
 
-In addition to the default restricted characters set the following
-characters are also replaced:
-
-  Character    Value   Replacement
-  ----------- ------- -------------
-  \            0x5C        ＼
+    - Config:      box_config_file
+    - Env Var:     RCLONE_BOX_BOX_CONFIG_FILE
+    - Type:        string
+    - Default:     ""
 
-File names can also not end with the following characters. These only
-get replaced if they are the last character in the name:
+    #### --box-access-token
 
-  Character    Value   Replacement
-  ----------- ------- -------------
-  SP           0x20         ␠
-
-Invalid UTF-8 bytes will also be replaced, as they can’t be used in JSON
-strings.
-
-Transfers
-
-For files above 50MB rclone will use a chunked transfer. Rclone will
-upload up to --transfers chunks at the same time (shared among all the
-multipart uploads). Chunks are buffered in memory and are normally 8MB
-so increasing --transfers will increase memory use.
-
-Deleting files
-
-Depending on the enterprise settings for your user, the item will either
-be actually deleted from Box or moved to the trash.
+    Box App Primary Access Token
+    Leave blank normally.
 
-Root folder ID
+    - Config:      access_token
+    - Env Var:     RCLONE_BOX_ACCESS_TOKEN
+    - Type:        string
+    - Default:     ""
 
-You can set the root_folder_id for rclone. This is the directory
-(identified by its Folder ID) that rclone considers to be the root of
-your Box drive.
+    #### --box-box-sub-type
 
-Normally you will leave this blank and rclone will determine the correct
-root to use itself.
 
-However you can set this to restrict rclone to a specific folder
-hierarchy.
 
-In order to do this you will have to find the Folder ID 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.
+    - Config:      box_sub_type
+    - Env Var:     RCLONE_BOX_BOX_SUB_TYPE
+    - Type:        string
+    - Default:     "user"
+    - Examples:
+        - "user"
+            - Rclone should act on behalf of a user
+        - "enterprise"
+            - Rclone should act on behalf of a service account
 
-So if the folder you want rclone to use has a URL which looks like
-https://app.box.com/folder/11xxxxxxxxx8 in the browser, then you use
-11xxxxxxxxx8 as the root_folder_id in the config.
+    ### Advanced Options
 
-Standard Options
+    Here are the advanced options specific to box (Box).
 
-Here are the standard options specific to box (Box).
+    #### --box-token
 
-–box-client-id
+    OAuth Access Token as a JSON blob.
 
-Box App Client Id. Leave blank normally.
+    - Config:      token
+    - Env Var:     RCLONE_BOX_TOKEN
+    - Type:        string
+    - Default:     ""
 
--   Config: client_id
--   Env Var: RCLONE_BOX_CLIENT_ID
--   Type: string
--   Default: ""
+    #### --box-auth-url
 
-–box-client-secret
+    Auth server URL.
+    Leave blank to use the provider defaults.
 
-Box App Client Secret Leave blank normally.
+    - Config:      auth_url
+    - Env Var:     RCLONE_BOX_AUTH_URL
+    - Type:        string
+    - Default:     ""
 
--   Config: client_secret
--   Env Var: RCLONE_BOX_CLIENT_SECRET
--   Type: string
--   Default: ""
+    #### --box-token-url
 
-–box-box-config-file
+    Token server url.
+    Leave blank to use the provider defaults.
 
-Box App config.json location Leave blank normally.
+    - Config:      token_url
+    - Env Var:     RCLONE_BOX_TOKEN_URL
+    - Type:        string
+    - Default:     ""
 
--   Config: box_config_file
--   Env Var: RCLONE_BOX_BOX_CONFIG_FILE
--   Type: string
--   Default: ""
+    #### --box-root-folder-id
 
-–box-box-sub-type
+    Fill in for rclone to use a non root folder as its starting point.
 
--   Config: box_sub_type
--   Env Var: RCLONE_BOX_BOX_SUB_TYPE
--   Type: string
--   Default: “user”
--   Examples:
-    -   “user”
-        -   Rclone should act on behalf of a user
-    -   “enterprise”
-        -   Rclone should act on behalf of a service account
+    - Config:      root_folder_id
+    - Env Var:     RCLONE_BOX_ROOT_FOLDER_ID
+    - Type:        string
+    - Default:     "0"
 
-Advanced Options
+    #### --box-upload-cutoff
 
-Here are the advanced options specific to box (Box).
+    Cutoff for switching to multipart upload (>= 50MB).
 
-–box-root-folder-id
+    - Config:      upload_cutoff
+    - Env Var:     RCLONE_BOX_UPLOAD_CUTOFF
+    - Type:        SizeSuffix
+    - Default:     50M
 
-Fill in for rclone to use a non root folder as its starting point.
+    #### --box-commit-retries
 
--   Config: root_folder_id
--   Env Var: RCLONE_BOX_ROOT_FOLDER_ID
--   Type: string
--   Default: “0”
+    Max number of times to try committing a multipart file.
 
-–box-upload-cutoff
+    - Config:      commit_retries
+    - Env Var:     RCLONE_BOX_COMMIT_RETRIES
+    - Type:        int
+    - Default:     100
 
-Cutoff for switching to multipart upload (>= 50MB).
+    #### --box-encoding
 
--   Config: upload_cutoff
--   Env Var: RCLONE_BOX_UPLOAD_CUTOFF
--   Type: SizeSuffix
--   Default: 50M
+    This sets the encoding for the backend.
 
-–box-commit-retries
+    See: the [encoding section in the overview](https://rclone.org/overview/#encoding) for more info.
 
-Max number of times to try committing a multipart file.
+    - Config:      encoding
+    - Env Var:     RCLONE_BOX_ENCODING
+    - Type:        MultiEncoder
+    - Default:     Slash,BackSlash,Del,Ctl,RightSpace,InvalidUtf8,Dot
 
--   Config: commit_retries
--   Env Var: RCLONE_BOX_COMMIT_RETRIES
--   Type: int
--   Default: 100
 
-–box-encoding
 
-This sets the encoding for the backend.
+    ### Limitations ###
 
-See: the encoding section in the overview for more info.
+    Note that Box is case insensitive so you can't have a file called
+    "Hello.doc" and one called "hello.doc".
 
--   Config: encoding
--   Env Var: RCLONE_BOX_ENCODING
--   Type: MultiEncoder
--   Default: Slash,BackSlash,Del,Ctl,RightSpace,InvalidUtf8,Dot
+    Box file names can't have the `\` character in.  rclone maps this to
+    and from an identical looking unicode equivalent `＼`.
 
-Limitations
+    Box only supports filenames up to 255 characters in length.
 
-Note that Box is case insensitive so you can’t have a file called
-“Hello.doc” and one called “hello.doc”.
+     Cache (BETA)
+    -----------------------------------------
 
-Box file names can’t have the \ character in. rclone maps this to and
-from an identical looking unicode equivalent ＼.
+    The `cache` remote wraps another existing remote and stores file structure
+    and its data for long running tasks like `rclone mount`.
 
-Box only supports filenames up to 255 characters in length.
+    ## Status
 
+    The cache backend code is working but it currently doesn't
+    have a maintainer so there are [outstanding bugs](https://github.com/rclone/rclone/issues?q=is%3Aopen+is%3Aissue+label%3Abug+label%3A%22Remote%3A+Cache%22) which aren't getting fixed.
 
-Cache (BETA)
+    The cache backend is due to be phased out in favour of the VFS caching
+    layer eventually which is more tightly integrated into rclone.
 
-The cache remote wraps another existing remote and stores file structure
-and its data for long running tasks like rclone mount.
+    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.
 
+    ## Setup
 
-Status
+    To get started you just need to have an existing remote which can be configured
+    with `cache`.
 
-The cache backend code is working but it currently doesn’t have a
-maintainer so there are outstanding bugs which aren’t getting fixed.
+    Here is an example of how to make a remote called `test-cache`.  First run:
 
-The cache backend is due to be phased out in favour of the VFS caching
-layer eventually which is more tightly integrated into rclone.
+         rclone config
 
-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.
+    This will guide you through an interactive setup process:
 
+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> n name>
+test-cache Type of storage to configure. Choose a number from below, or
+type in your own value [snip] XX / Cache a remote  "cache" [snip]
+Storage> cache Remote to cache. Normally should contain a ':' and a
+path, eg "myremote:path/to/dir", "myremote:bucket" or maybe "myremote:"
+(not recommended). remote> local:/test Optional: The URL of the Plex
+server plex_url> http://127.0.0.1:32400 Optional: The username of the
+Plex user plex_username> 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> 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 /
+1MB  "1m" 2 / 5 MB  "5M" 3 / 10 MB  "10M" chunk_size> 2 How much time
+should object info (file size, file hashes etc) be stored in cache. Use
+a very high value if you don't plan on changing the source FS from
+outside the cache. Accepted units are: "s", "m", "h". Default: 5m Choose
+a number from below, or type in your own value 1 / 1 hour  "1h" 2 / 24
+hours  "24h" 3 / 24 hours  "48h" info_age> 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 MB  "500M" 2 / 1 GB  "1G" 3 / 10 GB  "10G"
+chunk_total_size> 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
 
-Setup
 
-To get started you just need to have an existing remote which can be
-configured with cache.
+    You can then use it like this,
 
-Here is an example of how to make a remote called test-cache. First run:
+    List directories in top level of your drive
 
-     rclone config
+        rclone lsd test-cache:
 
-This will guide you through an interactive setup process:
+    List all the files in your drive
+
+        rclone ls test-cache:
+
+    To start a cached mount
+
+        rclone mount --allow-other test-cache: /var/tmp/test-cache
+
+    ### Write Features ###
+
+    ### Offline uploading ###
+
+    In an effort to make writing through cache more reliable, the backend 
+    now supports this feature which can be activated by specifying a
+    `cache-tmp-upload-path`.
+
+    A files goes through these states when using this feature:
+
+    1. An upload is started (usually by copying a file on the cache remote)
+    2. 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)
+    3. After `cache-tmp-wait-time` passes and the file is next in line, `rclone move` 
+    is used to move the file to the cloud provider
+    4. Reading the file still works during the upload but most modifications on it will be prohibited
+    5. Once the move is complete the file is unlocked for modifications as it
+    becomes as any other regular file
+    6. If the file is being read through `cache` when it's actually
+    deleted from the temporary path then `cache` will simply swap the source
+    to the cloud provider without interrupting the reading (small blip can happen though)
+
+    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 `--cache-db-purge` flag.
+
+    ### Write Support ###
+
+    Writes are supported through `cache`.
+    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 `Offline uploading` for reliable writes.
+
+    One special case is covered with `cache-writes` 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.
+
+    ### Read Features ###
+
+    #### Multiple connections ####
+
+    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.
+
+    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.
+
+    #### Plex Integration ####
+
+    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.
+
+    Scans will have a minimum amount of workers (1) while in a confirmed playback cache
+    will deploy the configured number of workers.
+
+    This integration opens the doorway to additional performance improvements
+    which will be explored in the near future.
+
+    **Note:** If Plex options are not configured, `cache` will function with its
+    configured options without adapting any of its settings.
+
+    How to enable? Run `rclone config` and add all the Plex options (endpoint, username
+    and password) in your remote and it will be automatically enabled.
+
+    Affected settings:
+    - `cache-workers`: _Configured value_ during confirmed playback or _1_ all the other times
+
+    ##### Certificate Validation #####
+
+    When the Plex server is configured to only accept secure connections, it is
+    possible to use `.plex.direct` URLs to ensure certificate validation succeeds.
+    These URLs are used by Plex internally to connect to the Plex server securely.
+
+    The format for these URLs is the following:
+
+    https://ip-with-dots-replaced.server-hash.plex.direct:32400/
+
+    The `ip-with-dots-replaced` part can be any IPv4 address, where the dots
+    have been replaced with dashes, e.g. `127.0.0.1` becomes `127-0-0-1`.
+
+    To get the `server-hash` part, the easiest way is to visit
+
+    https://plex.tv/api/resources?includeHttps=1&X-Plex-Token=your-plex-token
+
+    This page will list all the available Plex servers for your account
+    with at least one `.plex.direct` link for each. Copy one URL and replace
+    the IP address with the desired address. This can be used as the
+    `plex_url` value.
+
+    ### Known issues ###
+
+    #### Mount and --dir-cache-time ####
+
+    --dir-cache-time controls the first layer of directory caching which works at the mount layer.
+    Being an independent caching mechanism from the `cache` backend, it will manage its own entries
+    based on the configured time.
+
+    To avoid getting in a scenario where dir cache has obsolete data and cache would have the correct
+    one, try to set `--dir-cache-time` to a lower time than `--cache-info-age`. Default values are
+    already configured in this way. 
+
+    #### Windows support - Experimental ####
+
+    There are a couple of issues with Windows `mount` functionality that still require some investigations.
+    It should be considered as experimental thus far as fixes come in for this OS.
+
+    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.
+
+    Any reports or feedback on how cache behaves on this OS is greatly appreciated.
+     
+    - https://github.com/rclone/rclone/issues/1935
+    - https://github.com/rclone/rclone/issues/1907
+    - https://github.com/rclone/rclone/issues/1834 
+
+    #### Risk of throttling ####
+
+    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. 
+
+    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.
+
+    Some recommendations:
+    - don't use a very small interval for entry information (`--cache-info-age`)
+    - while writes aren't yet optimised, you can still write through `cache` which gives you the advantage
+    of adding the file in the cache at the same time if configured to do so.
+
+    Future enhancements:
+
+    - https://github.com/rclone/rclone/issues/1937
+    - https://github.com/rclone/rclone/issues/1936 
+
+    #### cache and crypt ####
+
+    One common scenario is to keep your data encrypted in the cloud provider
+    using the `crypt` remote. `crypt` uses a similar technique to wrap around
+    an existing remote and handles this translation in a seamless way.
+
+    There is an issue with wrapping the remotes in this order:
+    **cloud remote** -> **crypt** -> **cache**
+
+    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:
+    **cloud remote** -> **cache** -> **crypt**
+
+    #### absolute remote paths ####
+
+    `cache` can not differentiate between relative and absolute paths for the wrapped remote.
+    Any path given in the `remote` 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 `/` character.
+
+    This behavior is irrelevant for most backend types, but there are backends where a leading `/`
+    changes the effective directory, e.g. in the `sftp` backend paths starting with a `/` are
+    relative to the root of the SSH server and paths without are relative to the user home directory.
+    As a result `sftp:bin` and `sftp:/bin` will share the same cache folder, even if they represent
+    a different directory on the SSH server.
+
+    ### Cache and Remote Control (--rc) ###
+    Cache supports the new `--rc` 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.
+
+    ### rc cache/expire
+    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.
+
+    Params:
+      - **remote** = path to remote **(required)**
+      - **withData** = true/false to delete cached data (chunks) as well _(optional, false by default)_
+
+
+    ### Standard Options
+
+    Here are the standard options specific to cache (Cache a remote).
+
+    #### --cache-remote
 
-    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> n
-    name> test-cache
-    Type of storage to configure.
-    Choose a number from below, or type in your own value
-    [snip]
-    XX / Cache a remote
-       \ "cache"
-    [snip]
-    Storage> cache
     Remote to cache.
     Normally should contain a ':' and a path, eg "myremote:path/to/dir",
     "myremote:bucket" or maybe "myremote:" (not recommended).
-    remote> local:/test
-    Optional: The URL of the Plex server
-    plex_url> http://127.0.0.1:32400
-    Optional: The username of the Plex user
-    plex_username> 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> 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 / 1MB
-       \ "1m"
-     2 / 5 MB
-       \ "5M"
-     3 / 10 MB
-       \ "10M"
-    chunk_size> 2
-    How much time should object info (file size, file hashes etc) be stored in cache. Use a very high value if you don't plan on changing the source FS from outside the cache.
-    Accepted units are: "s", "m", "h".
-    Default: 5m
-    Choose a number from below, or type in your own value
-     1 / 1 hour
-       \ "1h"
-     2 / 24 hours
-       \ "24h"
-     3 / 24 hours
-       \ "48h"
-    info_age> 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 MB
-       \ "500M"
-     2 / 1 GB
-       \ "1G"
-     3 / 10 GB
-       \ "10G"
-    chunk_total_size> 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
-
-You can then use it like this,
-
-List directories in top level of your drive
-
-    rclone lsd test-cache:
-
-List all the files in your drive
-
-    rclone ls test-cache:
-
-To start a cached mount
-
-    rclone mount --allow-other test-cache: /var/tmp/test-cache
-
-Write Features
-
-Offline uploading
-
-In an effort to make writing through cache more reliable, the backend
-now supports this feature which can be activated by specifying a
-cache-tmp-upload-path.
-
-A files goes through these states when using this feature:
-
-1.  An upload is started (usually by copying a file on the cache remote)
-2.  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)
-3.  After cache-tmp-wait-time passes and the file is next in line,
-    rclone move is used to move the file to the cloud provider
-4.  Reading the file still works during the upload but most
-    modifications on it will be prohibited
-5.  Once the move is complete the file is unlocked for modifications as
-    it becomes as any other regular file
-6.  If the file is being read through cache when it’s actually deleted
-    from the temporary path then cache will simply swap the source to
-    the cloud provider without interrupting the reading (small blip can
-    happen though)
-
-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 --cache-db-purge
-flag.
-
-Write Support
-
-Writes are supported through cache. 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 Offline uploading for reliable writes.
-
-One special case is covered with cache-writes 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.
-
-Read Features
-
-Multiple connections
-
-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.
 
-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.
+    - Config:      remote
+    - Env Var:     RCLONE_CACHE_REMOTE
+    - Type:        string
+    - Default:     ""
 
-Plex Integration
+    #### --cache-plex-url
 
-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.
+    The URL of the Plex server
 
-Scans will have a minimum amount of workers (1) while in a confirmed
-playback cache will deploy the configured number of workers.
+    - Config:      plex_url
+    - Env Var:     RCLONE_CACHE_PLEX_URL
+    - Type:        string
+    - Default:     ""
 
-This integration opens the doorway to additional performance
-improvements which will be explored in the near future.
+    #### --cache-plex-username
 
-NOTE: If Plex options are not configured, cache will function with its
-configured options without adapting any of its settings.
+    The username of the Plex user
 
-How to enable? Run rclone config and add all the Plex options (endpoint,
-username and password) in your remote and it will be automatically
-enabled.
+    - Config:      plex_username
+    - Env Var:     RCLONE_CACHE_PLEX_USERNAME
+    - Type:        string
+    - Default:     ""
 
-Affected settings: - cache-workers: _Configured value_ during confirmed
-playback or _1_ all the other times
+    #### --cache-plex-password
 
-Certificate Validation
+    The password of the Plex user
 
-When the Plex server is configured to only accept secure connections, it
-is possible to use .plex.direct URLs to ensure certificate validation
-succeeds. These URLs are used by Plex internally to connect to the Plex
-server securely.
+    **NB** Input to this must be obscured - see [rclone obscure](https://rclone.org/commands/rclone_obscure/).
 
-The format for these URLs is the following:
+    - Config:      plex_password
+    - Env Var:     RCLONE_CACHE_PLEX_PASSWORD
+    - Type:        string
+    - Default:     ""
 
-https://ip-with-dots-replaced.server-hash.plex.direct:32400/
+    #### --cache-chunk-size
 
-The ip-with-dots-replaced part can be any IPv4 address, where the dots
-have been replaced with dashes, e.g. 127.0.0.1 becomes 127-0-0-1.
+    The size of a chunk (partial file data).
 
-To get the server-hash part, the easiest way is to visit
+    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.
 
-https://plex.tv/api/resources?includeHttps=1&X-Plex-Token=your-plex-token
+    - Config:      chunk_size
+    - Env Var:     RCLONE_CACHE_CHUNK_SIZE
+    - Type:        SizeSuffix
+    - Default:     5M
+    - Examples:
+        - "1m"
+            - 1MB
+        - "5M"
+            - 5 MB
+        - "10M"
+            - 10 MB
 
-This page will list all the available Plex servers for your account with
-at least one .plex.direct link for each. Copy one URL and replace the IP
-address with the desired address. This can be used as the plex_url
-value.
+    #### --cache-info-age
 
-Known issues
+    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.
 
-Mount and –dir-cache-time
+    - Config:      info_age
+    - Env Var:     RCLONE_CACHE_INFO_AGE
+    - Type:        Duration
+    - Default:     6h0m0s
+    - Examples:
+        - "1h"
+            - 1 hour
+        - "24h"
+            - 24 hours
+        - "48h"
+            - 48 hours
 
-–dir-cache-time controls the first layer of directory caching which
-works at the mount layer. Being an independent caching mechanism from
-the cache backend, it will manage its own entries based on the
-configured time.
+    #### --cache-chunk-total-size
 
-To avoid getting in a scenario where dir cache has obsolete data and
-cache would have the correct one, try to set --dir-cache-time to a lower
-time than --cache-info-age. Default values are already configured in
-this way.
+    The total size that the chunks can take up on the local disk.
 
-Windows support - Experimental
+    If the cache exceeds this value then it will start to delete the
+    oldest chunks until it goes under this value.
 
-There are a couple of issues with Windows mount functionality that still
-require some investigations. It should be considered as experimental
-thus far as fixes come in for this OS.
+    - Config:      chunk_total_size
+    - Env Var:     RCLONE_CACHE_CHUNK_TOTAL_SIZE
+    - Type:        SizeSuffix
+    - Default:     10G
+    - Examples:
+        - "500M"
+            - 500 MB
+        - "1G"
+            - 1 GB
+        - "10G"
+            - 10 GB
 
-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.
+    ### Advanced Options
 
-Any reports or feedback on how cache behaves on this OS is greatly
-appreciated.
+    Here are the advanced options specific to cache (Cache a remote).
 
--   https://github.com/rclone/rclone/issues/1935
--   https://github.com/rclone/rclone/issues/1907
--   https://github.com/rclone/rclone/issues/1834
+    #### --cache-plex-token
 
-Risk of throttling
+    The plex token for authentication - auto set normally
 
-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.
+    - Config:      plex_token
+    - Env Var:     RCLONE_CACHE_PLEX_TOKEN
+    - Type:        string
+    - Default:     ""
 
-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.
+    #### --cache-plex-insecure
 
-Some recommendations: - don’t use a very small interval for entry
-information (--cache-info-age) - while writes aren’t yet optimised, you
-can still write through cache which gives you the advantage of adding
-the file in the cache at the same time if configured to do so.
+    Skip all certificate verification when connecting to the Plex server
 
-Future enhancements:
+    - Config:      plex_insecure
+    - Env Var:     RCLONE_CACHE_PLEX_INSECURE
+    - Type:        string
+    - Default:     ""
 
--   https://github.com/rclone/rclone/issues/1937
--   https://github.com/rclone/rclone/issues/1936
+    #### --cache-db-path
 
-cache and crypt
+    Directory to store file structure metadata DB.
+    The remote name is used as the DB file name.
 
-One common scenario is to keep your data encrypted in the cloud provider
-using the crypt remote. crypt uses a similar technique to wrap around an
-existing remote and handles this translation in a seamless way.
+    - Config:      db_path
+    - Env Var:     RCLONE_CACHE_DB_PATH
+    - Type:        string
+    - Default:     "$HOME/.cache/rclone/cache-backend"
 
-There is an issue with wrapping the remotes in this order: CLOUD REMOTE
--> CRYPT -> CACHE
+    #### --cache-chunk-path
 
-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: CLOUD REMOTE -> CACHE -> CRYPT
+    Directory to cache chunk files.
 
-absolute remote paths
+    Path to where partial file data (chunks) are stored locally. The remote
+    name is appended to the final path.
 
-cache can not differentiate between relative and absolute paths for the
-wrapped remote. Any path given in the remote 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 / character.
+    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".
 
-This behavior is irrelevant for most backend types, but there are
-backends where a leading / changes the effective directory, e.g. in the
-sftp backend paths starting with a / are relative to the root of the SSH
-server and paths without are relative to the user home directory. As a
-result sftp:bin and sftp:/bin will share the same cache folder, even if
-they represent a different directory on the SSH server.
+    - Config:      chunk_path
+    - Env Var:     RCLONE_CACHE_CHUNK_PATH
+    - Type:        string
+    - Default:     "$HOME/.cache/rclone/cache-backend"
 
-Cache and Remote Control (–rc)
+    #### --cache-db-purge
 
-Cache supports the new --rc 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.
+    Clear all the cached data for this remote on start.
 
-rc cache/expire
+    - Config:      db_purge
+    - Env Var:     RCLONE_CACHE_DB_PURGE
+    - Type:        bool
+    - Default:     false
 
-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.
+    #### --cache-chunk-clean-interval
 
-Params: - REMOTE = path to remote (REQUIRED) - WITHDATA = true/false to
-delete cached data (chunks) as well _(optional, false by default)_
+    How often should the cache perform cleanups of the chunk storage.
+    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.
 
-Standard Options
+    - Config:      chunk_clean_interval
+    - Env Var:     RCLONE_CACHE_CHUNK_CLEAN_INTERVAL
+    - Type:        Duration
+    - Default:     1m0s
 
-Here are the standard options specific to cache (Cache a remote).
+    #### --cache-read-retries
 
-–cache-remote
+    How many times to retry a read from a cache storage.
 
-Remote to cache. Normally should contain a ‘:’ and a path, eg
-“myremote:path/to/dir”, “myremote:bucket” or maybe “myremote:” (not
-recommended).
+    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.
 
--   Config: remote
--   Env Var: RCLONE_CACHE_REMOTE
--   Type: string
--   Default: ""
+    For really slow connections, increase this to a point where the stream is
+    able to provide data but your experience will be very stuttering.
 
-–cache-plex-url
+    - Config:      read_retries
+    - Env Var:     RCLONE_CACHE_READ_RETRIES
+    - Type:        int
+    - Default:     10
 
-The URL of the Plex server
+    #### --cache-workers
 
--   Config: plex_url
--   Env Var: RCLONE_CACHE_PLEX_URL
--   Type: string
--   Default: ""
+    How many workers should run in parallel to download chunks.
 
-–cache-plex-username
+    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.
 
-The username of the Plex user
+    **Note**: 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.
 
--   Config: plex_username
--   Env Var: RCLONE_CACHE_PLEX_USERNAME
--   Type: string
--   Default: ""
+    - Config:      workers
+    - Env Var:     RCLONE_CACHE_WORKERS
+    - Type:        int
+    - Default:     4
 
-–cache-plex-password
+    #### --cache-chunk-no-memory
 
-The password of the Plex user
+    Disable the in-memory cache for storing chunks during streaming.
 
--   Config: plex_password
--   Env Var: RCLONE_CACHE_PLEX_PASSWORD
--   Type: string
--   Default: ""
+    By default, cache will keep file data during streaming in RAM as well
+    to provide it to readers as fast as possible.
 
-–cache-chunk-size
+    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).
 
-The size of a chunk (partial file data).
+    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.
 
-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.
+    - Config:      chunk_no_memory
+    - Env Var:     RCLONE_CACHE_CHUNK_NO_MEMORY
+    - Type:        bool
+    - Default:     false
 
--   Config: chunk_size
--   Env Var: RCLONE_CACHE_CHUNK_SIZE
--   Type: SizeSuffix
--   Default: 5M
--   Examples:
-    -   “1m”
-        -   1MB
-    -   “5M”
-        -   5 MB
-    -   “10M”
-        -   10 MB
+    #### --cache-rps
 
-–cache-info-age
+    Limits the number of requests per second to the source FS (-1 to disable)
 
-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.
+    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.
 
--   Config: info_age
--   Env Var: RCLONE_CACHE_INFO_AGE
--   Type: Duration
--   Default: 6h0m0s
--   Examples:
-    -   “1h”
-        -   1 hour
-    -   “24h”
-        -   24 hours
-    -   “48h”
-        -   48 hours
+    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.
 
-–cache-chunk-total-size
+    A good balance of all the other settings should make this setting
+    useless but it is available to set for more special cases.
 
-The total size that the chunks can take up on the local disk.
+    **NOTE**: This will limit the number of requests during streams but
+    other API calls to the cloud provider like directory listings will
+    still pass.
 
-If the cache exceeds this value then it will start to delete the oldest
-chunks until it goes under this value.
+    - Config:      rps
+    - Env Var:     RCLONE_CACHE_RPS
+    - Type:        int
+    - Default:     -1
 
--   Config: chunk_total_size
--   Env Var: RCLONE_CACHE_CHUNK_TOTAL_SIZE
--   Type: SizeSuffix
--   Default: 10G
--   Examples:
-    -   “500M”
-        -   500 MB
-    -   “1G”
-        -   1 GB
-    -   “10G”
-        -   10 GB
+    #### --cache-writes
 
-Advanced Options
+    Cache file data on writes through the FS
 
-Here are the advanced options specific to cache (Cache a remote).
+    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.
 
-–cache-plex-token
+    - Config:      writes
+    - Env Var:     RCLONE_CACHE_WRITES
+    - Type:        bool
+    - Default:     false
 
-The plex token for authentication - auto set normally
+    #### --cache-tmp-upload-path
 
--   Config: plex_token
--   Env Var: RCLONE_CACHE_PLEX_TOKEN
--   Type: string
--   Default: ""
+    Directory to keep temporary files until they are uploaded.
 
-–cache-plex-insecure
+    This is the path where cache will use as a temporary storage for new
+    files that need to be uploaded to the cloud provider.
 
-Skip all certificate verification when connecting to the Plex server
+    Specifying a value will enable this feature. Without it, it is
+    completely disabled and files will be uploaded directly to the cloud
+    provider
 
--   Config: plex_insecure
--   Env Var: RCLONE_CACHE_PLEX_INSECURE
--   Type: string
--   Default: ""
+    - Config:      tmp_upload_path
+    - Env Var:     RCLONE_CACHE_TMP_UPLOAD_PATH
+    - Type:        string
+    - Default:     ""
 
-–cache-db-path
+    #### --cache-tmp-wait-time
 
-Directory to store file structure metadata DB. The remote name is used
-as the DB file name.
+    How long should files be stored in local cache before being uploaded
 
--   Config: db_path
--   Env Var: RCLONE_CACHE_DB_PATH
--   Type: string
--   Default: “$HOME/.cache/rclone/cache-backend”
+    This is the duration that a file must wait in the temporary location
+    _cache-tmp-upload-path_ before it is selected for upload.
 
-–cache-chunk-path
+    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.
 
-Directory to cache chunk files.
+    - Config:      tmp_wait_time
+    - Env Var:     RCLONE_CACHE_TMP_WAIT_TIME
+    - Type:        Duration
+    - Default:     15s
 
-Path to where partial file data (chunks) are stored locally. The remote
-name is appended to the final path.
+    #### --cache-db-wait-time
 
-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”.
+    How long to wait for the DB to be available - 0 is unlimited
 
--   Config: chunk_path
--   Env Var: RCLONE_CACHE_CHUNK_PATH
--   Type: string
--   Default: “$HOME/.cache/rclone/cache-backend”
+    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.
 
-–cache-db-purge
+    If you set it to 0 then it will wait forever.
 
-Clear all the cached data for this remote on start.
+    - Config:      db_wait_time
+    - Env Var:     RCLONE_CACHE_DB_WAIT_TIME
+    - Type:        Duration
+    - Default:     1s
 
--   Config: db_purge
--   Env Var: RCLONE_CACHE_DB_PURGE
--   Type: bool
--   Default: false
+    ### Backend commands
 
-–cache-chunk-clean-interval
+    Here are the commands specific to the cache backend.
 
-How often should the cache perform cleanups of the chunk storage. 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.
+    Run them with
 
--   Config: chunk_clean_interval
--   Env Var: RCLONE_CACHE_CHUNK_CLEAN_INTERVAL
--   Type: Duration
--   Default: 1m0s
+        rclone backend COMMAND remote:
 
-–cache-read-retries
+    The help below will explain what arguments each command takes.
 
-How many times to retry a read from a cache storage.
+    See [the "rclone backend" command](https://rclone.org/commands/rclone_backend/) for more
+    info on how to pass options and arguments.
 
-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.
+    These can be run on a running backend using the rc command
+    [backend/command](https://rclone.org/rc/#backend/command).
 
-For really slow connections, increase this to a point where the stream
-is able to provide data but your experience will be very stuttering.
+    #### stats
 
--   Config: read_retries
--   Env Var: RCLONE_CACHE_READ_RETRIES
--   Type: int
--   Default: 10
+    Print stats on the cache backend in JSON format.
 
-–cache-workers
+        rclone backend stats remote: [options] [<arguments>+]
 
-How many workers should run in parallel to download chunks.
 
-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.
 
-NOTE: 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.
+    Chunker (BETA)
+    ----------------------------------------
 
--   Config: workers
--   Env Var: RCLONE_CACHE_WORKERS
--   Type: int
--   Default: 4
+    The `chunker` 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.
 
-–cache-chunk-no-memory
+    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.
 
-Disable the in-memory cache for storing chunks during streaming.
+    First check your chosen remote is working - we'll call it `remote:path` here.
+    Note that anything inside `remote:path` will be chunked and anything outside
+    won't. This means that if you are using a bucket based remote (eg S3, B2, swift)
+    then you should probably put the bucket in the remote `s3:bucket`.
 
-By default, cache will keep file data during streaming in RAM as well to
-provide it to readers as fast as possible.
+    Now configure `chunker` using `rclone config`. We will call this one `overlay`
+    to separate it from the `remote` itself.
 
-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).
+No remotes found - make a new one n) New remote s) Set configuration
+password q) Quit config n/s/q> n name> overlay Type of storage to
+configure. Choose a number from below, or type in your own value [snip]
+XX / Transparently chunk/split large files  "chunker" [snip] Storage>
+chunker Remote to chunk/unchunk. Normally should contain a ':' and a
+path, eg "myremote:path/to/dir", "myremote:bucket" or maybe "myremote:"
+(not recommended). Enter a string value. Press Enter for the default
+(""). remote> 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
+("2G"). chunk_size> 100M Choose how chunker handles hash sums. All modes
+but "none" require metadata. Enter a string value. Press Enter for the
+default ("md5"). 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  "none" 2 / MD5 for composite files  "md5" 3 /
+SHA1 for composite files  "sha1" 4 / MD5 for all files  "md5all" 5 /
+SHA1 for all files  "sha1all" 6 / Copying a file to chunker will request
+MD5 from the source falling back to SHA1 if unsupported  "md5quick" 7 /
+Similar to "md5quick" but prefers SHA1 over MD5  "sha1quick" hash_type>
+md5 Edit advanced config? (y/n) y) Yes n) No y/n> 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> y
 
-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.
 
--   Config: chunk_no_memory
--   Env Var: RCLONE_CACHE_CHUNK_NO_MEMORY
--   Type: bool
--   Default: false
+    ### Specifying the remote
 
-–cache-rps
+    In normal use, make sure the remote has a `:` in. If you specify the remote
+    without a `:` then rclone will use a local directory of that name.
+    So if you use a remote of `/path/to/secret/files` then rclone will
+    chunk stuff in that directory. If you use a remote of `name` then rclone
+    will put files in a directory called `name` in the current directory.
 
-Limits the number of requests per second to the source FS (-1 to
-disable)
 
-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.
+    ### Chunking
 
-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.
+    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. 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.
 
-A good balance of all the other settings should make this setting
-useless but it is available to set for more special cases.
+    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.
+
+    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.
+
+    When the `list` 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.
+
+    List and other commands can sometimes come across composite files with
+    missing or invalid chunks, eg. 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 `--chunker-fail-hard` flag to have commands abort with
+    error message in such cases.
+
+
+    #### Chunk names
+
+    The default chunk name format is `*.rclone_chunk.###`, hence by default
+    chunk names are `BIG_FILE_NAME.rclone_chunk.001`,
+    `BIG_FILE_NAME.rclone_chunk.002` etc. You can configure another name format
+    using the `name_format` configuration file option. The format uses asterisk
+    `*` as a placeholder for the base file name and one or more consecutive
+    hash characters `#` 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, eg. for compatibility with legacy software.
+
+    For example, if name format is `big_*-##.part` and original file name is
+    `data.txt` and numbering starts from 0, then the first chunk will be named
+    `big_data.txt-00.part`, the 99th chunk will be `big_data.txt-98.part`
+    and the 302nd chunk will become `big_data.txt-301.part`.
+
+    Note that `list` assembles composite directory entries only when chunk names
+    match the configured format and treats non-conforming file names as normal
+    non-chunked files.
+
+
+    ### Metadata
+
+    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 `none` format).
+    Note that metadata is normally not created for files smaller than the
+    configured chunk size. This may change in future rclone releases.
+
+    #### Simple JSON metadata format
+
+    This is the default format. It supports hash sums and chunk validation
+    for composite files. Meta objects carry the following fields:
+
+    - `ver`     - version of format, currently `1`
+    - `size`    - total size of composite file
+    - `nchunks` - number of data chunks in file
+    - `md5`     - MD5 hashsum of composite file (if present)
+    - `sha1`    - SHA1 hashsum (if present)
+
+    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.
+
+    #### No metadata
+
+    You can disable meta objects by setting the meta format option to `none`.
+    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.
+
+
+    ### Hashsums
+
+    Chunker supports hashsums only when a compatible metadata is present.
+    Hence, if you choose metadata format of `none`, chunker will report hashsum
+    as `UNSUPPORTED`.
+
+    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.
+
+    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.
+
+    If your storage backend does not support MD5 or SHA1 but you need consistent
+    file hashing, configure chunker with `md5all` or `sha1all`. 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 eg. `chunk_type=sha1all`
+    to force hashsums and `chunk_size=1P` to effectively disable chunking.
+
+    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: `sha1quick` and `md5quick`. 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 `sync` command will
+    revert (sometimes silently) to time/size comparison if compatible hashsums
+    between source and target are not found.
+
+
+    ### Modified time
+
+    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 `none` then chunker will
+    use modification time of the first data chunk.
+
+
+    ### Migrations
+
+    The idiomatic way to migrate to a different chunk size, hash type or
+    chunk naming scheme is to:
+
+    - Collect all your chunked files under a directory and have your
+      chunker remote point to it.
+    - Create another directory (most probably on the same cloud storage)
+      and configure a new remote with desired metadata format,
+      hash type, chunk naming etc.
+    - Now run `rclone sync -i oldchunks: newchunks:` and all your data
+      will be transparently converted in transfer.
+      This may take some time, yet chunker will try server-side
+      copy if possible.
+    - After checking data integrity you may remove configuration section
+      of the old remote.
+
+    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 `list` command but will eat up your account quota.
+    Please note that the `deletefile` 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 `copy` command will copy only active chunks while the `purge` will
+    remove everything including garbage.
+
+
+    ### Caveats and Limitations
+
+    Chunker requires wrapped remote to support server side `move` (or `copy` +
+    `delete`) 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.
+
+    Chunker encodes chunk number in file name, so with default `name_format`
+    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
+    eg. `*.rcc##` and save 10 characters (provided at most 99 chunks per file).
+
+    Note that a move implemented using the copy-and-delete method may incur
+    double charging with some cloud storage providers.
+
+    Chunker will not automatically rename existing chunks when you run
+    `rclone config` 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.
+
+    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).
+
+
+
+    ### Standard Options
+
+    Here are the standard options specific to chunker (Transparently chunk/split large files).
+
+    #### --chunker-remote
 
-NOTE: This will limit the number of requests during streams but other
-API calls to the cloud provider like directory listings will still pass.
-
--   Config: rps
--   Env Var: RCLONE_CACHE_RPS
--   Type: int
--   Default: -1
-
-–cache-writes
-
-Cache file data on writes through the FS
-
-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.
-
--   Config: writes
--   Env Var: RCLONE_CACHE_WRITES
--   Type: bool
--   Default: false
-
-–cache-tmp-upload-path
-
-Directory to keep temporary files until they are uploaded.
-
-This is the path where cache will use as a temporary storage for new
-files that need to be uploaded to the cloud provider.
-
-Specifying a value will enable this feature. Without it, it is
-completely disabled and files will be uploaded directly to the cloud
-provider
-
--   Config: tmp_upload_path
--   Env Var: RCLONE_CACHE_TMP_UPLOAD_PATH
--   Type: string
--   Default: ""
-
-–cache-tmp-wait-time
-
-How long should files be stored in local cache before being uploaded
-
-This is the duration that a file must wait in the temporary location
-_cache-tmp-upload-path_ before it is selected for upload.
-
-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.
-
--   Config: tmp_wait_time
--   Env Var: RCLONE_CACHE_TMP_WAIT_TIME
--   Type: Duration
--   Default: 15s
-
-–cache-db-wait-time
-
-How long to wait for the DB to be available - 0 is unlimited
-
-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.
-
-If you set it to 0 then it will wait forever.
-
--   Config: db_wait_time
--   Env Var: RCLONE_CACHE_DB_WAIT_TIME
--   Type: Duration
--   Default: 1s
-
-Backend commands
-
-Here are the commands specific to the cache backend.
-
-Run them with
-
-    rclone backend COMMAND remote:
-
-The help below will explain what arguments each command takes.
-
-See the “rclone backend” command for more info on how to pass options
-and arguments.
-
-These can be run on a running backend using the rc command
-backend/command.
-
-stats
-
-Print stats on the cache backend in JSON format.
-
-    rclone backend stats remote: [options] [<arguments>+]
-
-
-Chunker (BETA)
-
-The chunker 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.
-
-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.
-
-First check your chosen remote is working - we’ll call it remote:path
-here. Note that anything inside remote:path will be chunked and anything
-outside won’t. This means that if you are using a bucket based remote
-(eg S3, B2, swift) then you should probably put the bucket in the remote
-s3:bucket.
-
-Now configure chunker using rclone config. We will call this one overlay
-to separate it from the remote itself.
-
-    No remotes found - make a new one
-    n) New remote
-    s) Set configuration password
-    q) Quit config
-    n/s/q> n
-    name> overlay
-    Type of storage to configure.
-    Choose a number from below, or type in your own value
-    [snip]
-    XX / Transparently chunk/split large files
-       \ "chunker"
-    [snip]
-    Storage> chunker
     Remote to chunk/unchunk.
     Normally should contain a ':' and a path, eg "myremote:path/to/dir",
     "myremote:bucket" or maybe "myremote:" (not recommended).
-    Enter a string value. Press Enter for the default ("").
-    remote> remote:path
+
+    - Config:      remote
+    - Env Var:     RCLONE_CHUNKER_REMOTE
+    - Type:        string
+    - Default:     ""
+
+    #### --chunker-chunk-size
+
     Files larger than chunk size will be split in chunks.
-    Enter a size with suffix k,M,G,T. Press Enter for the default ("2G").
-    chunk_size> 100M
+
+    - Config:      chunk_size
+    - Env Var:     RCLONE_CHUNKER_CHUNK_SIZE
+    - Type:        SizeSuffix
+    - Default:     2G
+
+    #### --chunker-hash-type
+
     Choose how chunker handles hash sums. All modes but "none" require metadata.
-    Enter a string value. Press Enter for the default ("md5").
-    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
-       \ "none"
-     2 / MD5 for composite files
-       \ "md5"
-     3 / SHA1 for composite files
-       \ "sha1"
-     4 / MD5 for all files
-       \ "md5all"
-     5 / SHA1 for all files
-       \ "sha1all"
-     6 / Copying a file to chunker will request MD5 from the source falling back to SHA1 if unsupported
-       \ "md5quick"
-     7 / Similar to "md5quick" but prefers SHA1 over MD5
-       \ "sha1quick"
-    hash_type> md5
-    Edit advanced config? (y/n)
-    y) Yes
-    n) No
-    y/n> 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> y
-
-Specifying the remote
-
-In normal use, make sure the remote has a : in. If you specify the
-remote without a : then rclone will use a local directory of that name.
-So if you use a remote of /path/to/secret/files then rclone will chunk
-stuff in that directory. If you use a remote of name then rclone will
-put files in a directory called name in the current directory.
-
-Chunking
-
-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. 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.
-
-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.
-
-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.
-
-When the list 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.
-
-List and other commands can sometimes come across composite files with
-missing or invalid chunks, eg. 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 --chunker-fail-hard
-flag to have commands abort with error message in such cases.
-
-Chunk names
-
-The default chunk name format is *.rclone_chunk.###, hence by default
-chunk names are BIG_FILE_NAME.rclone_chunk.001,
-BIG_FILE_NAME.rclone_chunk.002 etc. You can configure another name
-format using the name_format configuration file option. The format uses
-asterisk * as a placeholder for the base file name and one or more
-consecutive hash characters # 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, eg. for
-compatibility with legacy software.
-
-For example, if name format is big_*-##.part and original file name is
-data.txt and numbering starts from 0, then the first chunk will be named
-big_data.txt-00.part, the 99th chunk will be big_data.txt-98.part and
-the 302nd chunk will become big_data.txt-301.part.
-
-Note that list assembles composite directory entries only when chunk
-names match the configured format and treats non-conforming file names
-as normal non-chunked files.
-
-Metadata
-
-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 none format). Note that
-metadata is normally not created for files smaller than the configured
-chunk size. This may change in future rclone releases.
-
-Simple JSON metadata format
-
-This is the default format. It supports hash sums and chunk validation
-for composite files. Meta objects carry the following fields:
-
--   ver - version of format, currently 1
--   size - total size of composite file
--   nchunks - number of data chunks in file
--   md5 - MD5 hashsum of composite file (if present)
--   sha1 - SHA1 hashsum (if present)
-
-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.
-
-No metadata
-
-You can disable meta objects by setting the meta format option to none.
-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.
-
-Hashsums
-
-Chunker supports hashsums only when a compatible metadata is present.
-Hence, if you choose metadata format of none, chunker will report
-hashsum as UNSUPPORTED.
-
-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.
-
-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.
-
-If your storage backend does not support MD5 or SHA1 but you need
-consistent file hashing, configure chunker with md5all or sha1all. 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 eg. chunk_type=sha1all to force hashsums and chunk_size=1P to
-effectively disable chunking.
-
-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: sha1quick and md5quick. 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 sync command will revert (sometimes silently) to
-time/size comparison if compatible hashsums between source and target
-are not found.
-
-Modified time
-
-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 none then chunker will use modification time of the
-first data chunk.
-
-Migrations
-
-The idiomatic way to migrate to a different chunk size, hash type or
-chunk naming scheme is to:
-
--   Collect all your chunked files under a directory and have your
-    chunker remote point to it.
--   Create another directory (most probably on the same cloud storage)
-    and configure a new remote with desired metadata format, hash type,
-    chunk naming etc.
--   Now run rclone sync oldchunks: newchunks: and all your data will be
-    transparently converted in transfer. This may take some time, yet
-    chunker will try server-side copy if possible.
--   After checking data integrity you may remove configuration section
-    of the old remote.
-
-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 list command but will eat up your account quota. Please
-note that the deletefile 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 copy command will copy only active chunks while the purge
-will remove everything including garbage.
-
-Caveats and Limitations
-
-Chunker requires wrapped remote to support server side move (or copy +
-delete) 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.
-
-Chunker encodes chunk number in file name, so with default name_format
-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 eg. *.rcc## and save 10 characters
-(provided at most 99 chunks per file).
-
-Note that a move implemented using the copy-and-delete method may incur
-double charging with some cloud storage providers.
-
-Chunker will not automatically rename existing chunks when you run
-rclone config 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.
-
-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).
-
-Standard Options
-
-Here are the standard options specific to chunker (Transparently
-chunk/split large files).
-
-–chunker-remote
-
-Remote to chunk/unchunk. Normally should contain a ‘:’ and a path, eg
-“myremote:path/to/dir”, “myremote:bucket” or maybe “myremote:” (not
-recommended).
-
--   Config: remote
--   Env Var: RCLONE_CHUNKER_REMOTE
--   Type: string
--   Default: ""
-
-–chunker-chunk-size
-
-Files larger than chunk size will be split in chunks.
-
--   Config: chunk_size
--   Env Var: RCLONE_CHUNKER_CHUNK_SIZE
--   Type: SizeSuffix
--   Default: 2G
-
-–chunker-hash-type
-
-Choose how chunker handles hash sums. All modes but “none” require
-metadata.
-
--   Config: hash_type
--   Env Var: RCLONE_CHUNKER_HASH_TYPE
--   Type: string
--   Default: “md5”
--   Examples:
-    -   “none”
-        -   Pass any hash supported by wrapped remote for non-chunked
-            files, return nothing otherwise
-    -   “md5”
-        -   MD5 for composite files
-    -   “sha1”
-        -   SHA1 for composite files
-    -   “md5all”
-        -   MD5 for all files
-    -   “sha1all”
-        -   SHA1 for all files
-    -   “md5quick”
-        -   Copying a file to chunker will request MD5 from the source
-            falling back to SHA1 if unsupported
-    -   “sha1quick”
-        -   Similar to “md5quick” but prefers SHA1 over MD5
-
-Advanced Options
-
-Here are the advanced options specific to chunker (Transparently
-chunk/split large files).
-
-–chunker-name-format
-
-String format of chunk file names. 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.
-
--   Config: name_format
--   Env Var: RCLONE_CHUNKER_NAME_FORMAT
--   Type: string
--   Default: "*.rclone_chunk.###"
-
-–chunker-start-from
-
-Minimum valid chunk number. Usually 0 or 1. By default chunk numbers
-start from 1.
-
--   Config: start_from
--   Env Var: RCLONE_CHUNKER_START_FROM
--   Type: int
--   Default: 1
-
-–chunker-meta-format
-
-Format of the metadata object or “none”. By default “simplejson”.
-Metadata is a small JSON file named after the composite file.
-
--   Config: meta_format
--   Env Var: RCLONE_CHUNKER_META_FORMAT
--   Type: string
--   Default: “simplejson”
--   Examples:
-    -   “none”
-        -   Do not use metadata files at all. Requires hash type “none”.
-    -   “simplejson”
-        -   Simple JSON supports hash sums and chunk validation.
-        -   It has the following fields: ver, size, nchunks, md5, sha1.
-
-–chunker-fail-hard
-
-Choose how chunker should handle files with missing or invalid chunks.
-
--   Config: fail_hard
--   Env Var: RCLONE_CHUNKER_FAIL_HARD
--   Type: bool
--   Default: false
--   Examples:
-    -   “true”
-        -   Report errors and abort current command.
-    -   “false”
-        -   Warn user, skip incomplete file and proceed.
-
-
-Citrix ShareFile
-
-Citrix ShareFile is a secure file sharing and transfer service aimed as
-business.
-
-The initial setup for Citrix ShareFile involves getting a token from
-Citrix ShareFile which you can in your browser. rclone config walks you
-through it.
-
-Here is an example of how to make a remote called remote. First run:
-
-     rclone config
-
-This will guide you through an interactive setup process:
-
-    No remotes found - make a new one
-    n) New remote
-    s) Set configuration password
-    q) Quit config
-    n/s/q> n
-    name> remote
-    Type of storage to configure.
-    Enter a string value. Press Enter for the default ("").
-    Choose a number from below, or type in your own value
-    XX / Citrix Sharefile
-       \ "sharefile"
-    Storage> sharefile
-    ** See help for sharefile backend at: https://rclone.org/sharefile/ **
+
+    - Config:      hash_type
+    - Env Var:     RCLONE_CHUNKER_HASH_TYPE
+    - Type:        string
+    - Default:     "md5"
+    - Examples:
+        - "none"
+            - Pass any hash supported by wrapped remote for non-chunked files, return nothing otherwise
+        - "md5"
+            - MD5 for composite files
+        - "sha1"
+            - SHA1 for composite files
+        - "md5all"
+            - MD5 for all files
+        - "sha1all"
+            - SHA1 for all files
+        - "md5quick"
+            - Copying a file to chunker will request MD5 from the source falling back to SHA1 if unsupported
+        - "sha1quick"
+            - Similar to "md5quick" but prefers SHA1 over MD5
+
+    ### Advanced Options
+
+    Here are the advanced options specific to chunker (Transparently chunk/split large files).
+
+    #### --chunker-name-format
+
+    String format of chunk file names.
+    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.
+
+    - Config:      name_format
+    - Env Var:     RCLONE_CHUNKER_NAME_FORMAT
+    - Type:        string
+    - Default:     "*.rclone_chunk.###"
+
+    #### --chunker-start-from
+
+    Minimum valid chunk number. Usually 0 or 1.
+    By default chunk numbers start from 1.
+
+    - Config:      start_from
+    - Env Var:     RCLONE_CHUNKER_START_FROM
+    - Type:        int
+    - Default:     1
+
+    #### --chunker-meta-format
+
+    Format of the metadata object or "none". By default "simplejson".
+    Metadata is a small JSON file named after the composite file.
+
+    - Config:      meta_format
+    - Env Var:     RCLONE_CHUNKER_META_FORMAT
+    - Type:        string
+    - Default:     "simplejson"
+    - Examples:
+        - "none"
+            - Do not use metadata files at all. Requires hash type "none".
+        - "simplejson"
+            - Simple JSON supports hash sums and chunk validation.
+            - It has the following fields: ver, size, nchunks, md5, sha1.
+
+    #### --chunker-fail-hard
+
+    Choose how chunker should handle files with missing or invalid chunks.
+
+    - Config:      fail_hard
+    - Env Var:     RCLONE_CHUNKER_FAIL_HARD
+    - Type:        bool
+    - Default:     false
+    - Examples:
+        - "true"
+            - Report errors and abort current command.
+        - "false"
+            - Warn user, skip incomplete file and proceed.
+
+
+
+    ##  Citrix ShareFile
+
+    [Citrix ShareFile](https://sharefile.com) is a secure file sharing and transfer service aimed as business.
+
+    The initial setup for Citrix ShareFile involves getting a token from
+    Citrix ShareFile which you can in your browser.  `rclone config` walks you
+    through it.
+
+    Here is an example of how to make a remote called `remote`.  First run:
+
+         rclone config
+
+    This will guide you through an interactive setup process:
+
+No remotes found - make a new one n) New remote s) Set configuration
+password q) Quit config n/s/q> n name> remote Type of storage to
+configure. Enter a string value. Press Enter for the default ("").
+Choose a number from below, or type in your own value XX / Citrix
+Sharefile  "sharefile" Storage> sharefile ** See help for sharefile
+backend at: https://rclone.org/sharefile/ **
+
+ID of the root folder
+
+Leave blank to access "Personal Folders". 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 (""). Choose a number from
+below, or type in your own value 1 / Access the Personal Folders.
+(Default)  "" 2 / Access the Favorites folder.  "favorites" 3 / Access
+all the shared folders.  "allshared" 4 / Access all the individual
+connectors.  "connectors" 5 / Access the home, favorites, and shared
+folders as well as the connectors.  "top" root_folder_id> Edit advanced
+config? (y/n) y) Yes n) No y/n> n Remote config Use auto config? * Say Y
+if not sure * Say N if you are working on a remote or headless machine
+y) Yes n) No y/n> y If your browser doesn'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
+-------------------- [remote] type = sharefile endpoint =
+https://XXX.sharefile.com token =
+{"access_token":"XXX","token_type":"bearer","refresh_token":"XXX","expiry":"2019-09-30T19:41:45.878561877+01:00"}
+-------------------- y) Yes this is OK e) Edit this remote d) Delete
+this remote y/e/d> y
+
+
+    See the [remote setup docs](https://rclone.org/remote_setup/) for how to set it up on a
+    machine with no Internet browser available.
+
+    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 `http://127.0.0.1:53682/` and this it may require you to unblock
+    it temporarily if you are running a host firewall.
+
+    Once configured you can then use `rclone` like this,
+
+    List directories in top level of your ShareFile
+
+        rclone lsd remote:
+
+    List all the files in your ShareFile
+
+        rclone ls remote:
+
+    To copy a local directory to an ShareFile directory called backup
+
+        rclone copy /home/source remote:backup
+
+    Paths may be as deep as required, eg `remote:directory/subdirectory`.
+
+    ### Modified time and hashes ###
+
+    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.
+
+    ShareFile supports MD5 type hashes, so you can use the `--checksum`
+    flag.
+
+    ### Transfers ###
+
+    For files above 128MB rclone will use a chunked transfer.  Rclone will
+    upload up to `--transfers` chunks at the same time (shared among all
+    the multipart uploads).  Chunks are buffered in memory and are
+    normally 64MB so increasing `--transfers` will increase memory use.
+
+    ### Limitations ###
+
+    Note that ShareFile is case insensitive so you can't have a file called
+    "Hello.doc" and one called "hello.doc".
+
+    ShareFile only supports filenames up to 256 characters in length.
+
+    #### Restricted filename characters
+
+    In addition to the [default restricted characters set](https://rclone.org/overview/#restricted-characters)
+    the following characters are also replaced:
+
+    | Character | Value | Replacement |
+    | --------- |:-----:|:-----------:|
+    | \\        | 0x5C  | ＼           |
+    | *         | 0x2A  | ＊           |
+    | <         | 0x3C  | ＜           |
+    | >         | 0x3E  | ＞           |
+    | ?         | 0x3F  | ？           |
+    | :         | 0x3A  | ：           |
+    | \|        | 0x7C  | ｜           |
+    | "         | 0x22  | ＂           |
+
+    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:
+
+    | Character | Value | Replacement |
+    | --------- |:-----:|:-----------:|
+    | SP        | 0x20  | ␠           |
+    | .         | 0x2E  | ．           |
+
+    Invalid UTF-8 bytes will also be [replaced](https://rclone.org/overview/#invalid-utf8),
+    as they can't be used in JSON strings.
+
+
+    ### Standard Options
+
+    Here are the standard options specific to sharefile (Citrix Sharefile).
+
+    #### --sharefile-root-folder-id
 
     ID of the root folder
 
     Leave blank to access "Personal Folders".  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 ("").
-    Choose a number from below, or type in your own value
-     1 / Access the Personal Folders. (Default)
-       \ ""
-     2 / Access the Favorites folder.
-       \ "favorites"
-     3 / Access all the shared folders.
-       \ "allshared"
-     4 / Access all the individual connectors.
-       \ "connectors"
-     5 / Access the home, favorites, and shared folders as well as the connectors.
-       \ "top"
-    root_folder_id> 
-    Edit advanced config? (y/n)
-    y) Yes
-    n) No
-    y/n> n
-    Remote config
-    Use auto config?
-     * Say Y if not sure
-     * Say N if you are working on a remote or headless machine
-    y) Yes
-    n) No
-    y/n> y
-    If your browser doesn'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
-    --------------------
-    [remote]
-    type = sharefile
-    endpoint = https://XXX.sharefile.com
-    token = {"access_token":"XXX","token_type":"bearer","refresh_token":"XXX","expiry":"2019-09-30T19:41:45.878561877+01:00"}
-    --------------------
-    y) Yes this is OK
-    e) Edit this remote
-    d) Delete this remote
-    y/e/d> y
 
-See the remote setup docs for how to set it up on a machine with no
-Internet browser available.
+    - Config:      root_folder_id
+    - Env Var:     RCLONE_SHAREFILE_ROOT_FOLDER_ID
+    - Type:        string
+    - Default:     ""
+    - Examples:
+        - ""
+            - Access the Personal Folders. (Default)
+        - "favorites"
+            - Access the Favorites folder.
+        - "allshared"
+            - Access all the shared folders.
+        - "connectors"
+            - Access all the individual connectors.
+        - "top"
+            - Access the home, favorites, and shared folders as well as the connectors.
 
-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 http://127.0.0.1:53682/ and this it may require you to
-unblock it temporarily if you are running a host firewall.
+    ### Advanced Options
 
-Once configured you can then use rclone like this,
+    Here are the advanced options specific to sharefile (Citrix Sharefile).
 
-List directories in top level of your ShareFile
+    #### --sharefile-upload-cutoff
 
-    rclone lsd remote:
+    Cutoff for switching to multipart upload.
 
-List all the files in your ShareFile
+    - Config:      upload_cutoff
+    - Env Var:     RCLONE_SHAREFILE_UPLOAD_CUTOFF
+    - Type:        SizeSuffix
+    - Default:     128M
 
-    rclone ls remote:
+    #### --sharefile-chunk-size
 
-To copy a local directory to an ShareFile directory called backup
+    Upload chunk size. Must a power of 2 >= 256k.
 
-    rclone copy /home/source remote:backup
+    Making this larger will improve performance, but note that each chunk
+    is buffered in memory one per transfer.
 
-Paths may be as deep as required, eg remote:directory/subdirectory.
+    Reducing this will reduce memory usage but decrease performance.
 
-Modified time and hashes
+    - Config:      chunk_size
+    - Env Var:     RCLONE_SHAREFILE_CHUNK_SIZE
+    - Type:        SizeSuffix
+    - Default:     64M
 
-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.
+    #### --sharefile-endpoint
 
-ShareFile supports MD5 type hashes, so you can use the --checksum flag.
+    Endpoint for API calls.
 
-Transfers
-
-For files above 128MB rclone will use a chunked transfer. Rclone will
-upload up to --transfers chunks at the same time (shared among all the
-multipart uploads). Chunks are buffered in memory and are normally 64MB
-so increasing --transfers will increase memory use.
-
-Limitations
-
-Note that ShareFile is case insensitive so you can’t have a file called
-“Hello.doc” and one called “hello.doc”.
-
-ShareFile only supports filenames up to 256 characters in length.
-
-Restricted filename characters
-
-In addition to the default restricted characters set the following
-characters are also replaced:
-
-  Character    Value   Replacement
-  ----------- ------- -------------
-  \            0x5C        ＼
-  *            0x2A        ＊
-  <            0x3C        ＜
-  >            0x3E        ＞
-  ?            0x3F        ？
-  :            0x3A        ：
-  |            0x7C        ｜
-  "            0x22        ＂
-
-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:
-
-  Character    Value   Replacement
-  ----------- ------- -------------
-  SP           0x20         ␠
-  .            0x2E        ．
-
-Invalid UTF-8 bytes will also be replaced, as they can’t be used in JSON
-strings.
-
-Standard Options
-
-Here are the standard options specific to sharefile (Citrix Sharefile).
-
-–sharefile-root-folder-id
-
-ID of the root folder
-
-Leave blank to access “Personal Folders”. You can use one of the
-standard values here or any folder ID (long hex number ID).
-
--   Config: root_folder_id
--   Env Var: RCLONE_SHAREFILE_ROOT_FOLDER_ID
--   Type: string
--   Default: ""
--   Examples:
-    -   ""
-        -   Access the Personal Folders. (Default)
-    -   “favorites”
-        -   Access the Favorites folder.
-    -   “allshared”
-        -   Access all the shared folders.
-    -   “connectors”
-        -   Access all the individual connectors.
-    -   “top”
-        -   Access the home, favorites, and shared folders as well as
-            the connectors.
-
-Advanced Options
-
-Here are the advanced options specific to sharefile (Citrix Sharefile).
-
-–sharefile-upload-cutoff
-
-Cutoff for switching to multipart upload.
-
--   Config: upload_cutoff
--   Env Var: RCLONE_SHAREFILE_UPLOAD_CUTOFF
--   Type: SizeSuffix
--   Default: 128M
-
-–sharefile-chunk-size
-
-Upload chunk size. Must a power of 2 >= 256k.
-
-Making this larger will improve performance, but note that each chunk is
-buffered in memory one per transfer.
-
-Reducing this will reduce memory usage but decrease performance.
-
--   Config: chunk_size
--   Env Var: RCLONE_SHAREFILE_CHUNK_SIZE
--   Type: SizeSuffix
--   Default: 64M
-
-–sharefile-endpoint
-
-Endpoint for API calls.
-
-This is usually auto discovered as part of the oauth process, but can be
-set manually to something like: https://XXX.sharefile.com
-
--   Config: endpoint
--   Env Var: RCLONE_SHAREFILE_ENDPOINT
--   Type: string
--   Default: ""
-
-–sharefile-encoding
-
-This sets the encoding for the backend.
-
-See: the encoding section in the overview for more info.
-
--   Config: encoding
--   Env Var: RCLONE_SHAREFILE_ENCODING
--   Type: MultiEncoder
--   Default:
-    Slash,LtGt,DoubleQuote,Colon,Question,Asterisk,Pipe,BackSlash,Ctl,LeftSpace,LeftPeriod,RightSpace,RightPeriod,InvalidUtf8,Dot
+    This is usually auto discovered as part of the oauth process, but can
+    be set manually to something like: https://XXX.sharefile.com
 
 
-Crypt
+    - Config:      endpoint
+    - Env Var:     RCLONE_SHAREFILE_ENDPOINT
+    - Type:        string
+    - Default:     ""
 
-The crypt remote encrypts and decrypts another remote.
+    #### --sharefile-encoding
 
-To use it first set up the underlying remote following the config
-instructions for that remote. You can also use a local pathname instead
-of a remote which will encrypt and decrypt from that directory which
-might be useful for encrypting onto a USB stick for example.
+    This sets the encoding for the backend.
 
-First check your chosen remote is working - we’ll call it remote:path in
-these docs. Note that anything inside remote:path will be encrypted and
-anything outside won’t. This means that if you are using a bucket based
-remote (eg S3, B2, swift) then you should probably put the bucket in the
-remote s3:bucket. If you just use s3: then rclone will make encrypted
-bucket names too (if using file name encryption) which may or may not be
-what you want.
+    See: the [encoding section in the overview](https://rclone.org/overview/#encoding) for more info.
 
-Now configure crypt using rclone config. We will call this one secret to
-differentiate it from the remote.
+    - Config:      encoding
+    - Env Var:     RCLONE_SHAREFILE_ENCODING
+    - Type:        MultiEncoder
+    - Default:     Slash,LtGt,DoubleQuote,Colon,Question,Asterisk,Pipe,BackSlash,Ctl,LeftSpace,LeftPeriod,RightSpace,RightPeriod,InvalidUtf8,Dot
+
+
+
+    Crypt
+    ----------------------------------------
+
+    The `crypt` remote encrypts and decrypts another remote.
+
+    To use it first set up the underlying remote following the config
+    instructions for that remote.  You can also use a local pathname
+    instead of a remote which will encrypt and decrypt from that directory
+    which might be useful for encrypting onto a USB stick for example.
+
+    First check your chosen remote is working - we'll call it
+    `remote:path` in these docs.  Note that anything inside `remote:path`
+    will be encrypted and anything outside won't.  This means that if you
+    are using a bucket based remote (eg S3, B2, swift) then you should
+    probably put the bucket in the remote `s3:bucket`. If you just use
+    `s3:` then rclone will make encrypted bucket names too (if using file
+    name encryption) which may or may not be what you want.
+
+    Now configure `crypt` using `rclone config`. We will call this one
+    `secret` to differentiate it from the `remote`.
+
+No remotes found - make a new one n) New remote s) Set configuration
+password q) Quit config n/s/q> n
+name> secret Type of storage to configure. Choose a number from below,
+or type in your own value [snip] XX / Encrypt/Decrypt a remote  "crypt"
+[snip] Storage> crypt Remote to encrypt/decrypt. Normally should contain
+a ':' and a path, eg "myremote:path/to/dir", "myremote:bucket" or maybe
+"myremote:" (not recommended). remote> remote:path How to encrypt the
+filenames. Choose a number from below, or type in your own value 1 /
+Don't encrypt the file names. Adds a ".bin" extension only.  "off" 2 /
+Encrypt the filenames see the docs for the details.  "standard" 3 / Very
+simple filename obfuscation.  "obfuscate" filename_encryption> 2 Option
+to either encrypt directory names or leave them intact. Choose a number
+from below, or type in your own value 1 / Encrypt directory names.
+ "true" 2 / Don't encrypt directory names, leave them intact.  "false"
+filename_encryption> 1 Password or pass phrase for encryption. y) Yes
+type in my own password g) Generate random password y/g> 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 y/g/n> g Password
+strength in bits. 64 is just about memorable 128 is secure 1024 is the
+maximum Bits> 128 Your password is: JAsJvRcgR-_veXNfy_sGmQ Use this
+password? y) Yes n) No y/n> y Remote config --------------------
+[secret] remote = remote:path filename_encryption = standard password =
+*** ENCRYPTED _ PASSWORD2 = _ ENCRYPTED *** -------------------- y) Yes
+this is OK e) Edit this remote d) Delete this remote y/e/d> y
+
+
+    **Important** The password is stored in the config file is lightly
+    obscured so it isn't immediately obvious what it is.  It is in no way
+    secure unless you use config file encryption.
+
+    A long passphrase is recommended, or you can use a random one.
+
+    The obscured password is created by using AES-CTR with a static key, with
+    the salt stored verbatim at the beginning of the obscured password. This
+    static key is shared by between all versions of rclone.
+
+    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.
+
+    Note that rclone does not encrypt
+
+      * file length - this can be calculated within 16 bytes
+      * modification time - used for syncing
+
+    ## Specifying the remote ##
+
+    In normal use, make sure the remote has a `:` in. If you specify the
+    remote without a `:` then rclone will use a local directory of that
+    name.  So if you use a remote of `/path/to/secret/files` then rclone
+    will encrypt stuff to that directory.  If you use a remote of `name`
+    then rclone will put files in a directory called `name` in the current
+    directory.
+
+    If you specify the remote as `remote:path/to/dir` then rclone will
+    store encrypted files in `path/to/dir` on the remote. If you are using
+    file name encryption, then when you save files to
+    `secret:subdir/subfile` this will store them in the unencrypted path
+    `path/to/dir` but the `subdir/subpath` bit will be encrypted.
+
+    Note that unless you want encrypted bucket names (which are difficult
+    to manage because you won't know what directory they represent in web
+    interfaces etc), you should probably specify a bucket, eg
+    `remote:secretbucket` when using bucket based remotes such as S3,
+    Swift, Hubic, B2, GCS.
+
+    ## Example ##
+
+    To test I made a little directory of files using "standard" file name
+    encryption.
+
+plaintext/ ├── file0.txt ├── file1.txt └── subdir ├── file2.txt ├──
+file3.txt └── subsubdir └── file4.txt
+
+
+    Copy these to the remote and list them back
+
+$ 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
+
+
+    Now see what that looked like when encrypted
+
+$ rclone -q ls remote:path 55 hagjclgavj2mbiqm6u6cnjjqcg 54
+v05749mltvv1tf4onltun46gls 57
+86vhrsv86mpbtd3a0akjuqslj8/dlj7fkq4kdq72emafg7a7s41uo 58
+86vhrsv86mpbtd3a0akjuqslj8/7uu829995du6o42n32otfhjqp4/b9pausrfansjth5ob3jkdqd4lc
+56 86vhrsv86mpbtd3a0akjuqslj8/8njh1sk437gttmep3p70g81aps
+
+
+    Note that this retains the directory structure which means you can do this
+
+$ rclone -q ls secret:subdir 8 file2.txt 9 file3.txt 10
+subsubdir/file4.txt
+
+
+    If don't use file name encryption then the remote will look like this
+    - note the `.bin` extensions added to prevent the cloud provider
+    attempting to interpret the data.
+
+$ 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
+
+
+    ### File name encryption modes ###
+
+    Here are some of the features of the file name encryption modes
+
+    Off
+
+      * doesn't hide file names or directory structure
+      * allows for longer file names (~246 characters)
+      * can use sub paths and copy single files
+
+    Standard
+
+      * file names encrypted
+      * file names can't be as long (~143 characters)
+      * can use sub paths and copy single files
+      * directory structure visible
+      * identical files names will have identical uploaded names
+      * can use shortcuts to shorten the directory recursion
+
+    Obfuscation
+
+    This is a simple "rotate" of the filename, with each file having a rot
+    distance based on the filename. We store the distance at the beginning
+    of the filename. So a file called "hello" may become "53.jgnnq".
+
+    This is not a strong encryption of filenames, but it may stop automated
+    scanning tools from picking up on filename patterns. As such it's an
+    intermediate between "off" and "standard". The advantage is that it
+    allows for longer path segment names.
+
+    There is a possibility with some unicode based filenames that the
+    obfuscation is weak and may map lower case characters to upper case
+    equivalents.  You can not rely on this for strong protection.
+
+      * file names very lightly obfuscated
+      * file names can be longer than standard encryption
+      * can use sub paths and copy single files
+      * directory structure visible
+      * identical files names will have identical uploaded names
+
+    Cloud storage systems have various limits on file name length and
+    total path length which you are more likely to hit using "Standard"
+    file name encryption.  If you keep your file names to below 156
+    characters in length then you should be OK on all providers.
+
+    There may be an even more secure file name encryption mode in the
+    future which will address the long file name problem.
+
+    ### Directory name encryption ###
+    Crypt offers the option of encrypting dir names or leaving them intact.
+    There are two options:
+
+    True
+
+    Encrypts the whole file path including directory names
+    Example:
+    `1/12/123.txt` is encrypted to
+    `p0e52nreeaj0a5ea7s64m4j72s/l42g6771hnv3an9cgc8cr2n1ng/qgm4avr35m5loi1th53ato71v0`
+
+    False
+
+    Only encrypts file names, skips directory names
+    Example:
+    `1/12/123.txt` is encrypted to
+    `1/12/qgm4avr35m5loi1th53ato71v0`
+
+
+    ### Modified time and hashes ###
+
+    Crypt stores modification times using the underlying remote so support
+    depends on that.
+
+    Hashes are not stored for crypt.  However the data integrity is
+    protected by an extremely strong crypto authenticator.
+
+    Note that you should use the `rclone cryptcheck` command to check the
+    integrity of a crypted remote instead of `rclone check` which can't
+    check the checksums properly.
+
+
+    ### Standard Options
+
+    Here are the standard options specific to crypt (Encrypt/Decrypt a remote).
+
+    #### --crypt-remote
 
-    No remotes found - make a new one
-    n) New remote
-    s) Set configuration password
-    q) Quit config
-    n/s/q> n   
-    name> secret
-    Type of storage to configure.
-    Choose a number from below, or type in your own value
-    [snip]
-    XX / Encrypt/Decrypt a remote
-       \ "crypt"
-    [snip]
-    Storage> crypt
     Remote to encrypt/decrypt.
     Normally should contain a ':' and a path, eg "myremote:path/to/dir",
     "myremote:bucket" or maybe "myremote:" (not recommended).
-    remote> remote:path
+
+    - Config:      remote
+    - Env Var:     RCLONE_CRYPT_REMOTE
+    - Type:        string
+    - Default:     ""
+
+    #### --crypt-filename-encryption
+
     How to encrypt the filenames.
-    Choose a number from below, or type in your own value
-     1 / Don't encrypt the file names.  Adds a ".bin" extension only.
-       \ "off"
-     2 / Encrypt the filenames see the docs for the details.
-       \ "standard"
-     3 / Very simple filename obfuscation.
-       \ "obfuscate"
-    filename_encryption> 2
+
+    - Config:      filename_encryption
+    - Env Var:     RCLONE_CRYPT_FILENAME_ENCRYPTION
+    - Type:        string
+    - Default:     "standard"
+    - Examples:
+        - "standard"
+            - Encrypt the filenames see the docs for the details.
+        - "obfuscate"
+            - Very simple filename obfuscation.
+        - "off"
+            - Don't encrypt the file names.  Adds a ".bin" extension only.
+
+    #### --crypt-directory-name-encryption
+
     Option to either encrypt directory names or leave them intact.
-    Choose a number from below, or type in your own value
-     1 / Encrypt directory names.
-       \ "true"
-     2 / Don't encrypt directory names, leave them intact.
-       \ "false"
-    filename_encryption> 1
+
+    NB If filename_encryption is "off" then this option will do nothing.
+
+    - Config:      directory_name_encryption
+    - Env Var:     RCLONE_CRYPT_DIRECTORY_NAME_ENCRYPTION
+    - Type:        bool
+    - Default:     true
+    - Examples:
+        - "true"
+            - Encrypt directory names.
+        - "false"
+            - Don't encrypt directory names, leave them intact.
+
+    #### --crypt-password
+
     Password or pass phrase for encryption.
-    y) Yes type in my own password
-    g) Generate random password
-    y/g> y
-    Enter the password:
-    password:
-    Confirm the password:
-    password:
+
+    **NB** Input to this must be obscured - see [rclone obscure](https://rclone.org/commands/rclone_obscure/).
+
+    - Config:      password
+    - Env Var:     RCLONE_CRYPT_PASSWORD
+    - Type:        string
+    - Default:     ""
+
+    #### --crypt-password2
+
     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
-    y/g/n> g
-    Password strength in bits.
-    64 is just about memorable
-    128 is secure
-    1024 is the maximum
-    Bits> 128
-    Your password is: JAsJvRcgR-_veXNfy_sGmQ
-    Use this password?
-    y) Yes
-    n) No
-    y/n> y
-    Remote config
-    --------------------
-    [secret]
-    remote = remote:path
-    filename_encryption = standard
-    password = *** ENCRYPTED ***
-    password2 = *** ENCRYPTED ***
-    --------------------
-    y) Yes this is OK
-    e) Edit this remote
-    d) Delete this remote
-    y/e/d> y
-
-IMPORTANT The password is stored in the config file is lightly obscured
-so it isn’t immediately obvious what it is. It is in no way secure
-unless you use config file encryption.
-
-A long passphrase is recommended, or you can use a random one.
-
-The obscured password is created by using AES-CTR with a static key,
-with the salt stored verbatim at the beginning of the obscured password.
-This static key is shared by between all versions of rclone.
-
-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.
-
-Note that rclone does not encrypt
-
--   file length - this can be calculated within 16 bytes
--   modification time - used for syncing
-
-
-Specifying the remote
-
-In normal use, make sure the remote has a : in. If you specify the
-remote without a : then rclone will use a local directory of that name.
-So if you use a remote of /path/to/secret/files then rclone will encrypt
-stuff to that directory. If you use a remote of name then rclone will
-put files in a directory called name in the current directory.
-
-If you specify the remote as remote:path/to/dir then rclone will store
-encrypted files in path/to/dir on the remote. If you are using file name
-encryption, then when you save files to secret:subdir/subfile this will
-store them in the unencrypted path path/to/dir but the subdir/subpath
-bit will be encrypted.
-
-Note that unless you want encrypted bucket names (which are difficult to
-manage because you won’t know what directory they represent in web
-interfaces etc), you should probably specify a bucket, eg
-remote:secretbucket when using bucket based remotes such as S3, Swift,
-Hubic, B2, GCS.
-
-
-Example
-
-To test I made a little directory of files using “standard” file name
-encryption.
-
-    plaintext/
-    ├── file0.txt
-    ├── file1.txt
-    └── subdir
-        ├── file2.txt
-        ├── file3.txt
-        └── subsubdir
-            └── file4.txt
-
-Copy these to the remote and list them back
-
-    $ 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
-
-Now see what that looked like when encrypted
-
-    $ rclone -q ls remote:path
-           55 hagjclgavj2mbiqm6u6cnjjqcg
-           54 v05749mltvv1tf4onltun46gls
-           57 86vhrsv86mpbtd3a0akjuqslj8/dlj7fkq4kdq72emafg7a7s41uo
-           58 86vhrsv86mpbtd3a0akjuqslj8/7uu829995du6o42n32otfhjqp4/b9pausrfansjth5ob3jkdqd4lc
-           56 86vhrsv86mpbtd3a0akjuqslj8/8njh1sk437gttmep3p70g81aps
-
-Note that this retains the directory structure which means you can do
-this
 
-    $ rclone -q ls secret:subdir
-            8 file2.txt
-            9 file3.txt
-           10 subsubdir/file4.txt
+    **NB** Input to this must be obscured - see [rclone obscure](https://rclone.org/commands/rclone_obscure/).
 
-If don’t use file name encryption then the remote will look like this -
-note the .bin extensions added to prevent the cloud provider attempting
-to interpret the data.
+    - Config:      password2
+    - Env Var:     RCLONE_CRYPT_PASSWORD2
+    - Type:        string
+    - Default:     ""
 
-    $ 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
+    ### Advanced Options
 
-File name encryption modes
+    Here are the advanced options specific to crypt (Encrypt/Decrypt a remote).
 
-Here are some of the features of the file name encryption modes
+    #### --crypt-server-side-across-configs
 
-Off
+    Allow server side operations (eg copy) to work across different crypt configs.
 
--   doesn’t hide file names or directory structure
--   allows for longer file names (~246 characters)
--   can use sub paths and copy single files
+    Normally this option is not what you want, but if you have two crypts
+    pointing to the same backend you can use it.
 
-Standard
+    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.
 
--   file names encrypted
--   file names can’t be as long (~143 characters)
--   can use sub paths and copy single files
--   directory structure visible
--   identical files names will have identical uploaded names
--   can use shortcuts to shorten the directory recursion
+    - Config:      server_side_across_configs
+    - Env Var:     RCLONE_CRYPT_SERVER_SIDE_ACROSS_CONFIGS
+    - Type:        bool
+    - Default:     false
 
-Obfuscation
+    #### --crypt-show-mapping
 
-This is a simple “rotate” of the filename, with each file having a rot
-distance based on the filename. We store the distance at the beginning
-of the filename. So a file called “hello” may become “53.jgnnq”.
+    For all files listed show how the names encrypt.
 
-This is not a strong encryption of filenames, but it may stop automated
-scanning tools from picking up on filename patterns. As such it’s an
-intermediate between “off” and “standard”. The advantage is that it
-allows for longer path segment names.
+    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.
 
-There is a possibility with some unicode based filenames that the
-obfuscation is weak and may map lower case characters to upper case
-equivalents. You can not rely on this for strong protection.
+    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.
 
--   file names very lightly obfuscated
--   file names can be longer than standard encryption
--   can use sub paths and copy single files
--   directory structure visible
--   identical files names will have identical uploaded names
+    - Config:      show_mapping
+    - Env Var:     RCLONE_CRYPT_SHOW_MAPPING
+    - Type:        bool
+    - Default:     false
 
-Cloud storage systems have various limits on file name length and total
-path length which you are more likely to hit using “Standard” file name
-encryption. If you keep your file names to below 156 characters in
-length then you should be OK on all providers.
+    ### Backend commands
 
-There may be an even more secure file name encryption mode in the future
-which will address the long file name problem.
+    Here are the commands specific to the crypt backend.
 
-Directory name encryption
+    Run them with
 
-Crypt offers the option of encrypting dir names or leaving them intact.
-There are two options:
+        rclone backend COMMAND remote:
 
-True
+    The help below will explain what arguments each command takes.
 
-Encrypts the whole file path including directory names Example:
-1/12/123.txt is encrypted to
-p0e52nreeaj0a5ea7s64m4j72s/l42g6771hnv3an9cgc8cr2n1ng/qgm4avr35m5loi1th53ato71v0
+    See [the "rclone backend" command](https://rclone.org/commands/rclone_backend/) for more
+    info on how to pass options and arguments.
 
-False
+    These can be run on a running backend using the rc command
+    [backend/command](https://rclone.org/rc/#backend/command).
 
-Only encrypts file names, skips directory names Example: 1/12/123.txt is
-encrypted to 1/12/qgm4avr35m5loi1th53ato71v0
+    #### encode
 
-Modified time and hashes
+    Encode the given filename(s)
 
-Crypt stores modification times using the underlying remote so support
-depends on that.
+        rclone backend encode remote: [options] [<arguments>+]
 
-Hashes are not stored for crypt. However the data integrity is protected
-by an extremely strong crypto authenticator.
+    This encodes the filenames given as arguments returning a list of
+    strings of the encoded results.
 
-Note that you should use the rclone cryptcheck command to check the
-integrity of a crypted remote instead of rclone check which can’t check
-the checksums properly.
+    Usage Example:
 
-Standard Options
+        rclone backend encode crypt: file1 [file2...]
+        rclone rc backend/command command=encode fs=crypt: file1 [file2...]
 
-Here are the standard options specific to crypt (Encrypt/Decrypt a
-remote).
 
-–crypt-remote
+    #### decode
 
-Remote to encrypt/decrypt. Normally should contain a ‘:’ and a path, eg
-“myremote:path/to/dir”, “myremote:bucket” or maybe “myremote:” (not
-recommended).
+    Decode the given filename(s)
 
--   Config: remote
--   Env Var: RCLONE_CRYPT_REMOTE
--   Type: string
--   Default: ""
+        rclone backend decode remote: [options] [<arguments>+]
 
-–crypt-filename-encryption
+    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.
 
-How to encrypt the filenames.
+    Usage Example:
 
--   Config: filename_encryption
--   Env Var: RCLONE_CRYPT_FILENAME_ENCRYPTION
--   Type: string
--   Default: “standard”
--   Examples:
-    -   “standard”
-        -   Encrypt the filenames see the docs for the details.
-    -   “obfuscate”
-        -   Very simple filename obfuscation.
-    -   “off”
-        -   Don’t encrypt the file names. Adds a “.bin” extension only.
+        rclone backend decode crypt: encryptedfile1 [encryptedfile2...]
+        rclone rc backend/command command=decode fs=crypt: encryptedfile1 [encryptedfile2...]
 
-–crypt-directory-name-encryption
 
-Option to either encrypt directory names or leave them intact.
 
-NB If filename_encryption is “off” then this option will do nothing.
 
--   Config: directory_name_encryption
--   Env Var: RCLONE_CRYPT_DIRECTORY_NAME_ENCRYPTION
--   Type: bool
--   Default: true
--   Examples:
-    -   “true”
-        -   Encrypt directory names.
-    -   “false”
-        -   Don’t encrypt directory names, leave them intact.
+    ## Backing up a crypted remote ##
 
-–crypt-password
+    If you wish to backup a crypted remote, it is recommended that you use
+    `rclone sync` on the encrypted files, and make sure the passwords are
+    the same in the new encrypted remote.
 
-Password or pass phrase for encryption.
+    This will have the following advantages
 
--   Config: password
--   Env Var: RCLONE_CRYPT_PASSWORD
--   Type: string
--   Default: ""
+      * `rclone sync` will check the checksums while copying
+      * you can use `rclone check` between the encrypted remotes
+      * you don't decrypt and encrypt unnecessarily
 
-–crypt-password2
+    For example, let's say you have your original remote at `remote:` with
+    the encrypted version at `eremote:` with path `remote:crypt`.  You
+    would then set up the new remote `remote2:` and then the encrypted
+    version `eremote2:` with path `remote2:crypt` using the same passwords
+    as `eremote:`.
 
-Password or pass phrase for salt. Optional but recommended. Should be
-different to the previous password.
+    To sync the two remotes you would do
 
--   Config: password2
--   Env Var: RCLONE_CRYPT_PASSWORD2
--   Type: string
--   Default: ""
+        rclone sync -i remote:crypt remote2:crypt
 
-Advanced Options
+    And to check the integrity you would do
 
-Here are the advanced options specific to crypt (Encrypt/Decrypt a
-remote).
+        rclone check remote:crypt remote2:crypt
 
-–crypt-show-mapping
+    ## File formats ##
 
-For all files listed show how the names encrypt.
+    ### File encryption ###
 
-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.
+    Files are encrypted 1:1 source file to destination object.  The file
+    has a header and is divided into chunks.
 
-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.
+    #### Header ####
 
--   Config: show_mapping
--   Env Var: RCLONE_CRYPT_SHOW_MAPPING
--   Type: bool
--   Default: false
+      * 8 bytes magic string `RCLONE\x00\x00`
+      * 24 bytes Nonce (IV)
 
-Backend commands
+    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 re-used 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.
 
-Here are the commands specific to the crypt backend.
+    #### Chunk ####
 
-Run them with
+    Each chunk will contain 64kB 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.
 
-    rclone backend COMMAND remote:
+    Each chunk contains:
 
-The help below will explain what arguments each command takes.
+      * 16 Bytes of Poly1305 authenticator
+      * 1 - 65536 bytes XSalsa20 encrypted data
 
-See the “rclone backend” command for more info on how to pass options
-and arguments.
+    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.
 
-These can be run on a running backend using the rc command
-backend/command.
+    This uses a 32 byte (256 bit key) key derived from the user password.
 
-encode
+    #### Examples ####
 
-Encode the given filename(s)
+    1 byte file will encrypt to
 
-    rclone backend encode remote: [options] [<arguments>+]
+      * 32 bytes header
+      * 17 bytes data chunk
 
-This encodes the filenames given as arguments returning a list of
-strings of the encoded results.
+    49 bytes total
 
-Usage Example:
+    1MB (1048576 bytes) file will encrypt to
 
-    rclone backend encode crypt: file1 [file2...]
-    rclone rc backend/command command=encode fs=crypt: file1 [file2...]
+      * 32 bytes header
+      * 16 chunks of 65568 bytes
 
-decode
+    1049120 bytes total (a 0.05% overhead).  This is the overhead for big
+    files.
 
-Decode the given filename(s)
+    ### Name encryption ###
 
-    rclone backend decode remote: [options] [<arguments>+]
+    File names are encrypted segment by segment - the path is broken up
+    into `/` separated strings and these are encrypted individually.
 
-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.
+    File segments are padded using PKCS#7 to a multiple of 16 bytes
+    before encryption.
 
-Usage Example:
+    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.
 
-    rclone backend decode crypt: encryptedfile1 [encryptedfile2...]
-    rclone rc backend/command command=decode fs=crypt: encryptedfile1 [encryptedfile2...]
+    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.
 
+    This means that
 
-Backing up a crypted remote
+      * filenames with the same name will encrypt the same
+      * filenames which start the same won't have a common prefix
 
-If you wish to backup a crypted remote, it is recommended that you use
-rclone sync on the encrypted files, and make sure the passwords are the
-same in the new encrypted remote.
+    This uses a 32 byte key (256 bits) and a 16 byte (128 bits) IV both of
+    which are derived from the user password.
 
-This will have the following advantages
+    After encryption they are written out using a modified version of
+    standard `base32` encoding as described in RFC4648.  The standard
+    encoding is modified in two ways:
 
--   rclone sync will check the checksums while copying
--   you can use rclone check between the encrypted remotes
--   you don’t decrypt and encrypt unnecessarily
+      * it becomes lower case (no-one likes upper case filenames!)
+      * we strip the padding character `=`
 
-For example, let’s say you have your original remote at remote: with the
-encrypted version at eremote: with path remote:crypt. You would then set
-up the new remote remote2: and then the encrypted version eremote2: with
-path remote2:crypt using the same passwords as eremote:.
+    `base32` is used rather than the more efficient `base64` so rclone can be
+    used on case insensitive remotes (eg Windows, Amazon Drive).
 
-To sync the two remotes you would do
+    ### Key derivation ###
 
-    rclone sync remote:crypt remote2:crypt
+    Rclone uses `scrypt` with parameters `N=16384, r=8, p=1` 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.
 
-And to check the integrity you would do
+    `scrypt` makes it impractical to mount a dictionary attack on rclone
+    encrypted data.  For full protection against this you should always use
+    a salt.
 
-    rclone check remote:crypt remote2:crypt
+     Dropbox
+    ---------------------------------
 
+    Paths are specified as `remote:path`
 
-File formats
+    Dropbox paths may be as deep as required, eg
+    `remote:directory/subdirectory`.
 
-File encryption
+    The initial setup for dropbox involves getting a token from Dropbox
+    which you need to do in your browser.  `rclone config` walks you
+    through it.
 
-Files are encrypted 1:1 source file to destination object. The file has
-a header and is divided into chunks.
+    Here is an example of how to make a remote called `remote`.  First run:
 
-Header
+         rclone config
 
--   8 bytes magic string RCLONE\x00\x00
--   24 bytes Nonce (IV)
+    This will guide you through an interactive setup process:
 
-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 re-used 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.
-
-Chunk
-
-Each chunk will contain 64kB 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.
-
-Each chunk contains:
-
--   16 Bytes of Poly1305 authenticator
--   1 - 65536 bytes XSalsa20 encrypted data
-
-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.
-
-This uses a 32 byte (256 bit key) key derived from the user password.
-
-Examples
-
-1 byte file will encrypt to
-
--   32 bytes header
--   17 bytes data chunk
-
-49 bytes total
-
-1MB (1048576 bytes) file will encrypt to
-
--   32 bytes header
--   16 chunks of 65568 bytes
-
-1049120 bytes total (a 0.05% overhead). This is the overhead for big
-files.
-
-Name encryption
-
-File names are encrypted segment by segment - the path is broken up into
-/ separated strings and these are encrypted individually.
-
-File segments are padded using PKCS#7 to a multiple of 16 bytes before
-encryption.
-
-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.
-
-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.
-
-This means that
-
--   filenames with the same name will encrypt the same
--   filenames which start the same won’t have a common prefix
-
-This uses a 32 byte key (256 bits) and a 16 byte (128 bits) IV both of
-which are derived from the user password.
-
-After encryption they are written out using a modified version of
-standard base32 encoding as described in RFC4648. The standard encoding
-is modified in two ways:
-
--   it becomes lower case (no-one likes upper case filenames!)
--   we strip the padding character =
-
-base32 is used rather than the more efficient base64 so rclone can be
-used on case insensitive remotes (eg Windows, Amazon Drive).
-
-Key derivation
-
-Rclone uses scrypt with parameters N=16384, r=8, p=1 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.
-
-scrypt makes it impractical to mount a dictionary attack on rclone
-encrypted data. For full protection against this you should always use a
-salt.
-
-
-Dropbox
-
-Paths are specified as remote:path
-
-Dropbox paths may be as deep as required, eg
-remote:directory/subdirectory.
-
-The initial setup for dropbox involves getting a token from Dropbox
-which you need to do in your browser. rclone config walks you through
-it.
-
-Here is an example of how to make a remote called remote. First run:
-
-     rclone config
-
-This will guide you through an interactive setup process:
-
-    n) New remote
-    d) Delete remote
-    q) Quit config
-    e/n/d/q> n
-    name> remote
-    Type of storage to configure.
-    Choose a number from below, or type in your own value
-    [snip]
-    XX / Dropbox
-       \ "dropbox"
-    [snip]
-    Storage> dropbox
-    Dropbox App Key - leave blank normally.
-    app_key>
-    Dropbox App Secret - leave blank normally.
-    app_secret>
-    Remote config
-    Please visit:
+n)  New remote
+o)  Delete remote
+p)  Quit config e/n/d/q> n name> remote Type of storage to configure.
+    Choose a number from below, or type in your own value [snip] XX /
+    Dropbox  "dropbox" [snip] Storage> dropbox Dropbox App Key - leave
+    blank normally. app_key> Dropbox App Secret - leave blank normally.
+    app_secret> Remote config Please visit:
     https://www.dropbox.com/1/oauth2/authorize?client_id=XXXXXXXXXXXXXXX&response_type=code
     Enter the code: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX_XXXXXXXXXX
+    -------------------- [remote] app_key = app_secret = token =
+    XXXXXXXXXXXXXXXXXXXXXXXXXXXXX_XXXX_XXXXXXXXXXXXXXXXXXXXXXXXXXXXX
     --------------------
-    [remote]
-    app_key =
-    app_secret =
-    token = XXXXXXXXXXXXXXXXXXXXXXXXXXXXX_XXXX_XXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-    --------------------
-    y) Yes this is OK
-    e) Edit this remote
-    d) Delete this remote
-    y/e/d> y
+q)  Yes this is OK
+r)  Edit this remote
+s)  Delete this remote y/e/d> y
 
-You can then use it like this,
 
-List directories in top level of your dropbox
+    You can then use it like this,
 
-    rclone lsd remote:
+    List directories in top level of your dropbox
 
-List all the files in your dropbox
+        rclone lsd remote:
 
-    rclone ls remote:
+    List all the files in your dropbox
 
-To copy a local directory to a dropbox directory called backup
+        rclone ls remote:
 
-    rclone copy /home/source remote:backup
+    To copy a local directory to a dropbox directory called backup
 
-Dropbox for business
+        rclone copy /home/source remote:backup
 
-Rclone supports Dropbox for business and Team Folders.
+    ### Dropbox for business ###
 
-When using Dropbox for business remote: and remote:path/to/file will
-refer to your personal folder.
+    Rclone supports Dropbox for business and Team Folders.
 
-If you wish to see Team Folders you must use a leading / in the path, so
-rclone lsd remote:/ will refer to the root and show you all Team Folders
-and your User Folder.
+    When using Dropbox for business `remote:` and `remote:path/to/file`
+    will refer to your personal folder.
 
-You can then use team folders like this remote:/TeamFolder and
-remote:/TeamFolder/path/to/file.
+    If you wish to see Team Folders you must use a leading `/` in the
+    path, so `rclone lsd remote:/` will refer to the root and show you all
+    Team Folders and your User Folder.
 
-A leading / for a Dropbox personal account will do nothing, but it will
-take an extra HTTP transaction so it should be avoided.
+    You can then use team folders like this `remote:/TeamFolder` and
+    `remote:/TeamFolder/path/to/file`.
 
-Modified time and Hashes
+    A leading `/` for a Dropbox personal account will do nothing, but it
+    will take an extra HTTP transaction so it should be avoided.
 
-Dropbox supports modified times, but the only way to set a modification
-time is to re-upload the file.
+    ### Modified time and Hashes ###
 
-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 --size-only or --checksum flag to stop it.
+    Dropbox supports modified times, but the only way to set a
+    modification time is to re-upload the file.
 
-Dropbox supports its own hash type which is checked for all transfers.
+    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 `--size-only` or `--checksum` flag
+    to stop it.
 
-Restricted filename characters
+    Dropbox supports [its own hash
+    type](https://www.dropbox.com/developers/reference/content-hash) which
+    is checked for all transfers.
 
-  Character    Value   Replacement
-  ----------- ------- -------------
-  NUL          0x00         ␀
-  /            0x2F        ／
-  DEL          0x7F         ␡
-  \            0x5C        ＼
+    #### Restricted filename characters
 
-File names can also not end with the following characters. These only
-get replaced if they are the last character in the name:
+    | Character | Value | Replacement |
+    | --------- |:-----:|:-----------:|
+    | NUL       | 0x00  | ␀           |
+    | /         | 0x2F  | ／           |
+    | DEL       | 0x7F  | ␡           |
+    | \         | 0x5C  | ＼           |
 
-  Character    Value   Replacement
-  ----------- ------- -------------
-  SP           0x20         ␠
+    File names can also not end with the following characters.
+    These only get replaced if they are the last character in the name:
 
-Invalid UTF-8 bytes will also be replaced, as they can’t be used in JSON
-strings.
+    | Character | Value | Replacement |
+    | --------- |:-----:|:-----------:|
+    | SP        | 0x20  | ␠           |
 
-Standard Options
+    Invalid UTF-8 bytes will also be [replaced](https://rclone.org/overview/#invalid-utf8),
+    as they can't be used in JSON strings.
 
-Here are the standard options specific to dropbox (Dropbox).
 
-–dropbox-client-id
+    ### Standard Options
 
-Dropbox App Client Id Leave blank normally.
+    Here are the standard options specific to dropbox (Dropbox).
 
--   Config: client_id
--   Env Var: RCLONE_DROPBOX_CLIENT_ID
--   Type: string
--   Default: ""
+    #### --dropbox-client-id
 
-–dropbox-client-secret
+    OAuth Client Id
+    Leave blank normally.
 
-Dropbox App Client Secret Leave blank normally.
+    - Config:      client_id
+    - Env Var:     RCLONE_DROPBOX_CLIENT_ID
+    - Type:        string
+    - Default:     ""
 
--   Config: client_secret
--   Env Var: RCLONE_DROPBOX_CLIENT_SECRET
--   Type: string
--   Default: ""
+    #### --dropbox-client-secret
 
-Advanced Options
+    OAuth Client Secret
+    Leave blank normally.
 
-Here are the advanced options specific to dropbox (Dropbox).
+    - Config:      client_secret
+    - Env Var:     RCLONE_DROPBOX_CLIENT_SECRET
+    - Type:        string
+    - Default:     ""
 
-–dropbox-chunk-size
+    ### Advanced Options
 
-Upload chunk size. (< 150M).
+    Here are the advanced options specific to dropbox (Dropbox).
 
-Any files larger than this will be uploaded in chunks of this size.
+    #### --dropbox-token
 
-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 128MB in tests) at the cost of using more memory. It
-can be set smaller if you are tight on memory.
+    OAuth Access Token as a JSON blob.
 
--   Config: chunk_size
--   Env Var: RCLONE_DROPBOX_CHUNK_SIZE
--   Type: SizeSuffix
--   Default: 48M
+    - Config:      token
+    - Env Var:     RCLONE_DROPBOX_TOKEN
+    - Type:        string
+    - Default:     ""
 
-–dropbox-impersonate
+    #### --dropbox-auth-url
 
-Impersonate this user when using a business account.
+    Auth server URL.
+    Leave blank to use the provider defaults.
 
--   Config: impersonate
--   Env Var: RCLONE_DROPBOX_IMPERSONATE
--   Type: string
--   Default: ""
+    - Config:      auth_url
+    - Env Var:     RCLONE_DROPBOX_AUTH_URL
+    - Type:        string
+    - Default:     ""
 
-–dropbox-encoding
+    #### --dropbox-token-url
 
-This sets the encoding for the backend.
+    Token server url.
+    Leave blank to use the provider defaults.
 
-See: the encoding section in the overview for more info.
+    - Config:      token_url
+    - Env Var:     RCLONE_DROPBOX_TOKEN_URL
+    - Type:        string
+    - Default:     ""
 
--   Config: encoding
--   Env Var: RCLONE_DROPBOX_ENCODING
--   Type: MultiEncoder
--   Default: Slash,BackSlash,Del,RightSpace,InvalidUtf8,Dot
+    #### --dropbox-chunk-size
 
-Limitations
+    Upload chunk size. (< 150M).
 
-Note that Dropbox is case insensitive so you can’t have a file called
-“Hello.doc” and one called “hello.doc”.
+    Any files larger than this will be uploaded in chunks of this size.
 
-There are some file names such as thumbs.db which Dropbox can’t store.
-There is a full list of them in the “Ignored Files” section of this
-document. Rclone will issue an error message
-File name disallowed - not uploading if it attempts to upload one of
-those file names, but the sync won’t fail.
+    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 128MB in tests) at the cost of using more
+    memory.  It can be set smaller if you are tight on memory.
 
-If you have more than 10,000 files in a directory then
-rclone purge dropbox:dir will return the error
-Failed to purge: There are too many files involved in this operation. As
-a work-around do an rclone delete dropbox:dir followed by an
-rclone rmdir dropbox:dir.
+    - Config:      chunk_size
+    - Env Var:     RCLONE_DROPBOX_CHUNK_SIZE
+    - Type:        SizeSuffix
+    - Default:     48M
 
-Get your own Dropbox App ID
+    #### --dropbox-impersonate
 
-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.
+    Impersonate this user when using a business account.
 
-Here is how to create your own Dropbox App ID for rclone:
+    - Config:      impersonate
+    - Env Var:     RCLONE_DROPBOX_IMPERSONATE
+    - Type:        string
+    - Default:     ""
 
-1.  Log into the Dropbox App console with your Dropbox Account (It need
-    not to be the same account as the Dropbox you want to access)
+    #### --dropbox-encoding
 
-2.  Choose an API => Usually this should be Dropbox API
+    This sets the encoding for the backend.
 
-3.  Choose the type of access you want to use => Full Dropbox or
-    App Folder
+    See: the [encoding section in the overview](https://rclone.org/overview/#encoding) for more info.
 
-4.  Name your App. The app name is global, so you can’t use rclone for
-    example
+    - Config:      encoding
+    - Env Var:     RCLONE_DROPBOX_ENCODING
+    - Type:        MultiEncoder
+    - Default:     Slash,BackSlash,Del,RightSpace,InvalidUtf8,Dot
 
-5.  Click the button Create App
 
-6.  Fill Redirect URIs as http://localhost:53682/
 
-7.  Find the App key and App secret Use these values in rclone config to
-    add a new remote or edit an existing remote.
+    ### Limitations ###
 
+    Note that Dropbox is case insensitive so you can't have a file called
+    "Hello.doc" and one called "hello.doc".
 
-FTP
+    There are some file names such as `thumbs.db` which Dropbox can't
+    store.  There is a full list of them in the ["Ignored Files" section
+    of this document](https://www.dropbox.com/en/help/145).  Rclone will
+    issue an error message `File name disallowed - not uploading` if it
+    attempts to upload one of those file names, but the sync won't fail.
 
-FTP is the File Transfer Protocol. FTP support is provided using the
-github.com/jlaffaye/ftp package.
+    Some errors may occur if you try to sync copyright-protected files
+    because Dropbox has its own [copyright detector](https://techcrunch.com/2014/03/30/how-dropbox-knows-when-youre-sharing-copyrighted-stuff-without-actually-looking-at-your-stuff/) that
+    prevents this sort of file being downloaded. This will return the error `ERROR :
+    /path/to/your/file: Failed to copy: failed to open source object:
+    path/restricted_content/.`
 
-Here is an example of making an FTP configuration. First run
+    If you have more than 10,000 files in a directory then `rclone purge
+    dropbox:dir` will return the error `Failed to purge: There are too
+    many files involved in this operation`.  As a work-around do an
+    `rclone delete dropbox:dir` followed by an `rclone rmdir dropbox:dir`.
 
-    rclone config
+    ### Get your own Dropbox App ID ###
 
-This will guide you through an interactive setup process. An FTP remote
-only needs a host together with and a username and a password. With
-anonymous FTP server, you will need to use anonymous as username and
-your email address as the password.
+    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.
 
-    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> n
-    name> remote
-    Type of storage to configure.
-    Enter a string value. Press Enter for the default ("").
-    Choose a number from below, or type in your own value
-    [snip]
-    XX / FTP Connection
-       \ "ftp"
-    [snip]
-    Storage> ftp
-    ** See help for ftp backend at: https://rclone.org/ftp/ **
+    Here is how to create your own Dropbox App ID for rclone:
+
+    1. Log into the [Dropbox App console](https://www.dropbox.com/developers/apps/create) with your Dropbox Account (It need not
+    to be the same account as the Dropbox you want to access)
+
+    2. Choose an API => Usually this should be `Dropbox API`
+
+    3. Choose the type of access you want to use => `Full Dropbox` or `App Folder`
+
+    4. Name your App. The app name is global, so you can't use `rclone` for example
+
+    5. Click the button `Create App`
+
+    5. Fill `Redirect URIs` as `http://localhost:53682/`
+
+    6. Find the `App key` and `App secret` Use these values in rclone config to add a new remote or edit an existing remote.
+
+     FTP
+    ------------------------------
+
+    FTP is the File Transfer Protocol. FTP support is provided using the
+    [github.com/jlaffaye/ftp](https://godoc.org/github.com/jlaffaye/ftp)
+    package.
+
+    Paths are specified as `remote:path`. If the path does not begin with
+    a `/` it is relative to the home directory of the user.  An empty path
+    `remote:` refers to the user's home directory.
+
+    Here is an example of making an FTP configuration.  First run
+
+        rclone config
+
+    This will guide you through an interactive setup process. An FTP remote only
+    needs a host together with and a username and a password. With anonymous FTP
+    server, you will need to use `anonymous` as username and your email address as
+    the password.
+
+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> n name>
+remote Type of storage to configure. Enter a string value. Press Enter
+for the default (""). Choose a number from below, or type in your own
+value [snip] XX / FTP Connection  "ftp" [snip] Storage> 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
+(""). Choose a number from below, or type in your own value 1 / Connect
+to ftp.example.com  "ftp.example.com" host> ftp.example.com FTP
+username, leave blank for current username, ncw Enter a string value.
+Press Enter for the default (""). user> FTP port, leave blank to use
+default (21) Enter a string value. Press Enter for the default ("").
+port> FTP password y) Yes type in my own password g) Generate random
+password y/g> 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 ("false"). tls> Use FTP over TLS
+(Explicit) Enter a boolean value (true or false). Press Enter for the
+default ("false"). explicit_tls> Remote config --------------------
+[remote] type = ftp host = ftp.example.com pass = *** ENCRYPTED ***
+-------------------- y) Yes this is OK e) Edit this remote d) Delete
+this remote y/e/d> y
+
+
+    This remote is called `remote` and can now be used like this
+
+    See all directories in the home directory
+
+        rclone lsd remote:
+
+    Make a new directory
+
+        rclone mkdir remote:path/to/directory
+
+    List the contents of a directory
+
+        rclone ls remote:path/to/directory
+
+    Sync `/home/local/directory` to the remote directory, deleting any
+    excess files in the directory.
+
+        rclone sync -i /home/local/directory remote:directory
+
+    ### Modified time ###
+
+    FTP does not support modified times.  Any times you see on the server
+    will be time of upload.
+
+    ### Checksums ###
+
+    FTP does not support any checksums.
+
+    ### Usage without a config file ###
+
+    An example how to use the ftp remote without a config file:
+
+        rclone lsf :ftp: --ftp-host=speedtest.tele2.net --ftp-user=anonymous --ftp-pass=`rclone obscure dummy`
+
+    #### Restricted filename characters
+
+    In addition to the [default restricted characters set](https://rclone.org/overview/#restricted-characters)
+    the following characters are also replaced:
+
+    File names can also not end with the following characters.
+    These only get replaced if they are the last character in the name:
+
+    | Character | Value | Replacement |
+    | --------- |:-----:|:-----------:|
+    | SP        | 0x20  | ␠           |
+
+    Note that not all FTP servers can have all characters in file names, for example:
+
+    | FTP Server| Forbidden characters |
+    | --------- |:--------------------:|
+    | proftpd   | `*`                  |
+    | pureftpd  | `\ [ ]`              |
+
+    ### Implicit TLS ###
+
+    FTP supports implicit FTP over TLS servers (FTPS). This has to be enabled
+    in the config for the remote. The default FTPS port is `990` so the
+    port will likely have to be explicitly set in the config for the remote.
+
+
+    ### Standard Options
+
+    Here are the standard options specific to ftp (FTP Connection).
+
+    #### --ftp-host
 
     FTP host to connect to
-    Enter a string value. Press Enter for the default ("").
-    Choose a number from below, or type in your own value
-     1 / Connect to ftp.example.com
-       \ "ftp.example.com"
-    host> ftp.example.com
-    FTP username, leave blank for current username, ncw
-    Enter a string value. Press Enter for the default ("").
-    user> 
+
+    - Config:      host
+    - Env Var:     RCLONE_FTP_HOST
+    - Type:        string
+    - Default:     ""
+    - Examples:
+        - "ftp.example.com"
+            - Connect to ftp.example.com
+
+    #### --ftp-user
+
+    FTP username, leave blank for current username, $USER
+
+    - Config:      user
+    - Env Var:     RCLONE_FTP_USER
+    - Type:        string
+    - Default:     ""
+
+    #### --ftp-port
+
     FTP port, leave blank to use default (21)
-    Enter a string value. Press Enter for the default ("").
-    port> 
+
+    - Config:      port
+    - Env Var:     RCLONE_FTP_PORT
+    - Type:        string
+    - Default:     ""
+
+    #### --ftp-pass
+
     FTP password
-    y) Yes type in my own password
-    g) Generate random password
-    y/g> 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 ("false").
-    tls> 
-    Remote config
+
+    **NB** Input to this must be obscured - see [rclone obscure](https://rclone.org/commands/rclone_obscure/).
+
+    - Config:      pass
+    - Env Var:     RCLONE_FTP_PASS
+    - Type:        string
+    - Default:     ""
+
+    #### --ftp-tls
+
+    Use FTPS over TLS (Implicit)
+    When using implicit FTP over TLS the client will connect using TLS
+    right from the start, which in turn breaks the compatibility with
+    non-TLS-aware servers. This is usually served over port 990 rather
+    than port 21. Cannot be used in combination with explicit FTP.
+
+    - Config:      tls
+    - Env Var:     RCLONE_FTP_TLS
+    - Type:        bool
+    - Default:     false
+
+    #### --ftp-explicit-tls
+
+    Use FTP over TLS (Explicit)
+    When using explicit FTP over TLS the client explicitly request
+    security from the server in order to upgrade a plain text connection
+    to an encrypted one. Cannot be used in combination with implicit FTP.
+
+    - Config:      explicit_tls
+    - Env Var:     RCLONE_FTP_EXPLICIT_TLS
+    - Type:        bool
+    - Default:     false
+
+    ### Advanced Options
+
+    Here are the advanced options specific to ftp (FTP Connection).
+
+    #### --ftp-concurrency
+
+    Maximum number of FTP simultaneous connections, 0 for unlimited
+
+    - Config:      concurrency
+    - Env Var:     RCLONE_FTP_CONCURRENCY
+    - Type:        int
+    - Default:     0
+
+    #### --ftp-no-check-certificate
+
+    Do not verify the TLS certificate of the server
+
+    - Config:      no_check_certificate
+    - Env Var:     RCLONE_FTP_NO_CHECK_CERTIFICATE
+    - Type:        bool
+    - Default:     false
+
+    #### --ftp-disable-epsv
+
+    Disable using EPSV even if server advertises support
+
+    - Config:      disable_epsv
+    - Env Var:     RCLONE_FTP_DISABLE_EPSV
+    - Type:        bool
+    - Default:     false
+
+    #### --ftp-encoding
+
+    This sets the encoding for the backend.
+
+    See: the [encoding section in the overview](https://rclone.org/overview/#encoding) for more info.
+
+    - Config:      encoding
+    - Env Var:     RCLONE_FTP_ENCODING
+    - Type:        MultiEncoder
+    - Default:     Slash,Del,Ctl,RightSpace,Dot
+
+
+
+    ### Limitations ###
+
+    Note that FTP does have its own implementation of : `--dump headers`,
+    `--dump bodies`, `--dump auth` for debugging which isn't the same as
+    the HTTP based backends - it has less fine grained control.
+
+    Note that `--timeout` isn't supported (but `--contimeout` is).
+
+    Note that `--bind` isn't supported.
+
+    FTP could support server side move but doesn't yet.
+
+    Note that the ftp backend does not support the `ftp_proxy` environment
+    variable yet.
+
+     Google Cloud Storage
+    -------------------------------------------------
+
+    Paths are specified as `remote:bucket` (or `remote:` for the `lsd`
+    command.)  You may put subdirectories in too, eg `remote:bucket/path/to/dir`.
+
+    The initial setup for google cloud storage involves getting a token from Google Cloud Storage
+    which you need to do in your browser.  `rclone config` walks you
+    through it.
+
+    Here is an example of how to make a remote called `remote`.  First run:
+
+         rclone config
+
+    This will guide you through an interactive setup process:
+
+n)  New remote
+o)  Delete remote
+p)  Quit config e/n/d/q> n name> 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)  "google cloud
+    storage" [snip] Storage> google cloud storage Google Application
+    Client Id - leave blank normally. client_id> Google Application
+    Client Secret - leave blank normally. client_secret> Project number
+    optional - needed only for list/create/delete buckets - see your
+    developer console. project_number> 12345678 Service Account
+    Credentials JSON file path - needed only if you want use SA instead
+    of interactive login. service_account_file> 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.  "authenticatedRead" 2 / Object owner gets OWNER
+    access, and project team owners get OWNER access.
+     "bucketOwnerFullControl" 3 / Object owner gets OWNER access, and
+    project team owners get READER access.  "bucketOwnerRead" 4 / Object
+    owner gets OWNER access [default if left blank].  "private" 5 /
+    Object owner gets OWNER access, and project team members get access
+    according to their roles.  "projectPrivate" 6 / Object owner gets
+    OWNER access, and all Users get READER access.  "publicRead"
+    object_acl> 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.
+     "authenticatedRead" 2 / Project team owners get OWNER access
+    [default if left blank].  "private" 3 / Project team members get
+    access according to their roles.  "projectPrivate" 4 / Project team
+    owners get OWNER access, and all Users get READER access.
+     "publicRead" 5 / Project team owners get OWNER access, and all
+    Users get WRITER access.  "publicReadWrite" bucket_acl> 2 Location
+    for the newly created buckets. Choose a number from below, or type
+    in your own value 1 / Empty for default location (US).  "" 2 /
+    Multi-regional location for Asia.  "asia" 3 / Multi-regional
+    location for Europe.  "eu" 4 / Multi-regional location for United
+    States.  "us" 5 / Taiwan.  "asia-east1" 6 / Tokyo.
+     "asia-northeast1" 7 / Singapore.  "asia-southeast1" 8 / Sydney.
+     "australia-southeast1" 9 / Belgium.  "europe-west1" 10 / London.
+     "europe-west2" 11 / Iowa.  "us-central1" 12 / South Carolina.
+     "us-east1" 13 / Northern Virginia.  "us-east4" 14 / Oregon.
+     "us-west1" location> 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  "" 2 / Multi-regional storage class
+     "MULTI_REGIONAL" 3 / Regional storage class  "REGIONAL" 4 /
+    Nearline storage class  "NEARLINE" 5 / Coldline storage class
+     "COLDLINE" 6 / Durable reduced availability storage class
+     "DURABLE_REDUCED_AVAILABILITY" storage_class> 5 Remote config Use
+    auto config?
+
+-   Say Y if not sure
+-   Say N if you are working on a remote or headless machine or Y didn't
+    work
+
+y)  Yes
+z)  No y/n> y If your browser doesn'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 --------------------
+    [remote] type = google cloud storage client_id = client_secret =
+    token =
+    {"AccessToken":"xxxx.xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx","RefreshToken":"x/xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx_xxxxxxxxx","Expiry":"2014-07-17T20:49:14.929208288+01:00","Extra":null}
+    project_number = 12345678 object_acl = private bucket_acl = private
     --------------------
-    [remote]
-    type = ftp
-    host = ftp.example.com
-    pass = *** ENCRYPTED ***
-    --------------------
-    y) Yes this is OK
-    e) Edit this remote
-    d) Delete this remote
-    y/e/d> y
+a)  Yes this is OK
+b)  Edit this remote
+c)  Delete this remote y/e/d> y
 
-This remote is called remote and can now be used like this
 
-See all directories in the home directory
+    Note that rclone runs a webserver on your local machine to collect the
+    token as returned from Google if you use auto config mode. This only
+    runs from the moment it opens your browser to the moment you get back
+    the verification code.  This is on `http://127.0.0.1:53682/` and this
+    it may require you to unblock it temporarily if you are running a host
+    firewall, or use manual mode.
 
-    rclone lsd remote:
+    This remote is called `remote` and can now be used like this
 
-Make a new directory
+    See all the buckets in your project
 
-    rclone mkdir remote:path/to/directory
+        rclone lsd remote:
 
-List the contents of a directory
+    Make a new bucket
 
-    rclone ls remote:path/to/directory
+        rclone mkdir remote:bucket
 
-Sync /home/local/directory to the remote directory, deleting any excess
-files in the directory.
+    List the contents of a bucket
 
-    rclone sync /home/local/directory remote:directory
+        rclone ls remote:bucket
 
-Modified time
+    Sync `/home/local/directory` to the remote bucket, deleting any excess
+    files in the bucket.
 
-FTP does not support modified times. Any times you see on the server
-will be time of upload.
+        rclone sync -i /home/local/directory remote:bucket
 
-Checksums
+    ### Service Account support ###
 
-FTP does not support any checksums.
+    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.
 
-Usage without a config file
+    To get credentials for Google Cloud Platform
+    [IAM Service Accounts](https://cloud.google.com/iam/docs/service-accounts),
+    please head to the
+    [Service Account](https://console.cloud.google.com/permissions/serviceaccounts)
+    section of the Google Developer Console. Service Accounts behave just
+    like normal `User` permissions in
+    [Google Cloud Storage ACLs](https://cloud.google.com/storage/docs/access-control),
+    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.
 
-An example how to use the ftp remote without a config file:
+    To use a Service Account instead of OAuth2 token flow, enter the path
+    to your Service Account credentials at the `service_account_file`
+    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 `service_account_credentials` with
+    the actual contents of the file instead, or set the equivalent
+    environment variable.
 
-    rclone lsf :ftp: --ftp-host=speedtest.tele2.net --ftp-user=anonymous --ftp-pass=`rclone obscure dummy`
+    ### Anonymous Access ###
 
-Restricted filename characters
+    For downloads of objects that permit public access you can configure rclone
+    to use anonymous access by setting `anonymous` to `true`.
+    With unauthorized access you can't write or create files but only read or list
+    those buckets and objects that have public read access.
 
-In addition to the default restricted characters set the following
-characters are also replaced:
+    ### Application Default Credentials ###
 
-File names can also not end with the following characters. These only
-get replaced if they are the last character in the name:
+    If no other source of credentials is provided, rclone will fall back
+    to
+    [Application Default Credentials](https://cloud.google.com/video-intelligence/docs/common/auth#authenticating_with_application_default_credentials)
+    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 -
+    [see this page](https://cloud.google.com/container-registry/docs/advanced-authentication#gcloud_as_a_docker_credential_helper).
 
-  Character    Value   Replacement
-  ----------- ------- -------------
-  SP           0x20         ␠
+    Note that in the case application default credentials are used, there
+    is no need to explicitly configure a project number.
 
-Note that not all FTP servers can have all characters in file names, for
-example:
+    ### --fast-list ###
 
-  FTP Server    Forbidden characters
-  ------------ ----------------------
-  proftpd                *
-  pureftpd             \ [ ]
+    This remote supports `--fast-list` which allows you to use fewer
+    transactions in exchange for more memory. See the [rclone
+    docs](https://rclone.org/docs/#fast-list) for more details.
 
-Implicit TLS
+    ### Custom upload headers ###
 
-FTP supports implicit FTP over TLS servers (FTPS). This has to be
-enabled in the config for the remote. The default FTPS port is 990 so
-the port will likely have to be explicitly set in the config for the
-remote.
+    You can set custom upload headers with the `--header-upload`
+    flag. Google Cloud Storage supports the headers as described in the
+    [working with metadata documentation](https://cloud.google.com/storage/docs/gsutil/addlhelp/WorkingWithObjectMetadata)
 
-Standard Options
+    - Cache-Control
+    - Content-Disposition
+    - Content-Encoding
+    - Content-Language
+    - Content-Type
+    - X-Goog-Meta-
 
-Here are the standard options specific to ftp (FTP Connection).
+    Eg `--header-upload "Content-Type text/potato"`
 
-–ftp-host
+    Note that the last of these is for setting custom metadata in the form
+    `--header-upload "x-goog-meta-key: value"`
 
-FTP host to connect to
+    ### Modified time ###
 
--   Config: host
--   Env Var: RCLONE_FTP_HOST
--   Type: string
--   Default: ""
--   Examples:
-    -   “ftp.example.com”
-        -   Connect to ftp.example.com
+    Google google cloud storage stores md5sums natively and rclone stores
+    modification times as metadata on the object, under the "mtime" key in
+    RFC3339 format accurate to 1ns.
 
-–ftp-user
+    #### Restricted filename characters
 
-FTP username, leave blank for current username, $USER
+    | Character | Value | Replacement |
+    | --------- |:-----:|:-----------:|
+    | NUL       | 0x00  | ␀           |
+    | LF        | 0x0A  | ␊           |
+    | CR        | 0x0D  | ␍           |
+    | /         | 0x2F  | ／          |
 
--   Config: user
--   Env Var: RCLONE_FTP_USER
--   Type: string
--   Default: ""
+    Invalid UTF-8 bytes will also be [replaced](https://rclone.org/overview/#invalid-utf8),
+    as they can't be used in JSON strings.
 
-–ftp-port
 
-FTP port, leave blank to use default (21)
+    ### Standard Options
 
--   Config: port
--   Env Var: RCLONE_FTP_PORT
--   Type: string
--   Default: ""
+    Here are the standard options specific to google cloud storage (Google Cloud Storage (this is not Google Drive)).
 
-–ftp-pass
+    #### --gcs-client-id
 
-FTP password
+    OAuth Client Id
+    Leave blank normally.
 
--   Config: pass
--   Env Var: RCLONE_FTP_PASS
--   Type: string
--   Default: ""
+    - Config:      client_id
+    - Env Var:     RCLONE_GCS_CLIENT_ID
+    - Type:        string
+    - Default:     ""
 
-–ftp-tls
+    #### --gcs-client-secret
 
-Use FTP over TLS (Implicit)
+    OAuth Client Secret
+    Leave blank normally.
 
--   Config: tls
--   Env Var: RCLONE_FTP_TLS
--   Type: bool
--   Default: false
+    - Config:      client_secret
+    - Env Var:     RCLONE_GCS_CLIENT_SECRET
+    - Type:        string
+    - Default:     ""
 
-Advanced Options
+    #### --gcs-project-number
 
-Here are the advanced options specific to ftp (FTP Connection).
+    Project number.
+    Optional - needed only for list/create/delete buckets - see your developer console.
 
-–ftp-concurrency
+    - Config:      project_number
+    - Env Var:     RCLONE_GCS_PROJECT_NUMBER
+    - Type:        string
+    - Default:     ""
 
-Maximum number of FTP simultaneous connections, 0 for unlimited
+    #### --gcs-service-account-file
 
--   Config: concurrency
--   Env Var: RCLONE_FTP_CONCURRENCY
--   Type: int
--   Default: 0
+    Service Account Credentials JSON file path
+    Leave blank normally.
+    Needed only if you want use SA instead of interactive login.
 
-–ftp-no-check-certificate
+    Leading `~` will be expanded in the file name as will environment variables such as `${RCLONE_CONFIG_DIR}`.
 
-Do not verify the TLS certificate of the server
 
--   Config: no_check_certificate
--   Env Var: RCLONE_FTP_NO_CHECK_CERTIFICATE
--   Type: bool
--   Default: false
+    - Config:      service_account_file
+    - Env Var:     RCLONE_GCS_SERVICE_ACCOUNT_FILE
+    - Type:        string
+    - Default:     ""
 
-–ftp-disable-epsv
+    #### --gcs-service-account-credentials
 
-Disable using EPSV even if server advertises support
+    Service Account Credentials JSON blob
+    Leave blank normally.
+    Needed only if you want use SA instead of interactive login.
 
--   Config: disable_epsv
--   Env Var: RCLONE_FTP_DISABLE_EPSV
--   Type: bool
--   Default: false
+    - Config:      service_account_credentials
+    - Env Var:     RCLONE_GCS_SERVICE_ACCOUNT_CREDENTIALS
+    - Type:        string
+    - Default:     ""
 
-–ftp-encoding
+    #### --gcs-anonymous
 
-This sets the encoding for the backend.
+    Access public buckets and objects without credentials
+    Set to 'true' if you just want to download files and don't configure credentials.
 
-See: the encoding section in the overview for more info.
+    - Config:      anonymous
+    - Env Var:     RCLONE_GCS_ANONYMOUS
+    - Type:        bool
+    - Default:     false
 
--   Config: encoding
--   Env Var: RCLONE_FTP_ENCODING
--   Type: MultiEncoder
--   Default: Slash,Del,Ctl,RightSpace,Dot
+    #### --gcs-object-acl
 
-Limitations
-
-Note that since FTP isn’t HTTP based the following flags don’t work with
-it: --dump-headers, --dump-bodies, --dump-auth
-
-Note that --timeout isn’t supported (but --contimeout is).
-
-Note that --bind isn’t supported.
-
-FTP could support server side move but doesn’t yet.
-
-Note that the ftp backend does not support the ftp_proxy environment
-variable yet.
-
-Note that while implicit FTP over TLS is supported, explicit FTP over
-TLS is not.
-
-
-Google Cloud Storage
-
-Paths are specified as remote:bucket (or remote: for the lsd command.)
-You may put subdirectories in too, eg remote:bucket/path/to/dir.
-
-The initial setup for google cloud storage involves getting a token from
-Google Cloud Storage which you need to do in your browser. rclone config
-walks you through it.
-
-Here is an example of how to make a remote called remote. First run:
-
-     rclone config
-
-This will guide you through an interactive setup process:
-
-    n) New remote
-    d) Delete remote
-    q) Quit config
-    e/n/d/q> n
-    name> 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)
-       \ "google cloud storage"
-    [snip]
-    Storage> google cloud storage
-    Google Application Client Id - leave blank normally.
-    client_id>
-    Google Application Client Secret - leave blank normally.
-    client_secret>
-    Project number optional - needed only for list/create/delete buckets - see your developer console.
-    project_number> 12345678
-    Service Account Credentials JSON file path - needed only if you want use SA instead of interactive login.
-    service_account_file>
     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.
-       \ "authenticatedRead"
-     2 / Object owner gets OWNER access, and project team owners get OWNER access.
-       \ "bucketOwnerFullControl"
-     3 / Object owner gets OWNER access, and project team owners get READER access.
-       \ "bucketOwnerRead"
-     4 / Object owner gets OWNER access [default if left blank].
-       \ "private"
-     5 / Object owner gets OWNER access, and project team members get access according to their roles.
-       \ "projectPrivate"
-     6 / Object owner gets OWNER access, and all Users get READER access.
-       \ "publicRead"
-    object_acl> 4
+
+    - Config:      object_acl
+    - Env Var:     RCLONE_GCS_OBJECT_ACL
+    - Type:        string
+    - Default:     ""
+    - Examples:
+        - "authenticatedRead"
+            - Object owner gets OWNER access, and all Authenticated Users get READER access.
+        - "bucketOwnerFullControl"
+            - Object owner gets OWNER access, and project team owners get OWNER access.
+        - "bucketOwnerRead"
+            - Object owner gets OWNER access, and project team owners get READER access.
+        - "private"
+            - Object owner gets OWNER access [default if left blank].
+        - "projectPrivate"
+            - Object owner gets OWNER access, and project team members get access according to their roles.
+        - "publicRead"
+            - Object owner gets OWNER access, and all Users get READER access.
+
+    #### --gcs-bucket-acl
+
     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.
-       \ "authenticatedRead"
-     2 / Project team owners get OWNER access [default if left blank].
-       \ "private"
-     3 / Project team members get access according to their roles.
-       \ "projectPrivate"
-     4 / Project team owners get OWNER access, and all Users get READER access.
-       \ "publicRead"
-     5 / Project team owners get OWNER access, and all Users get WRITER access.
-       \ "publicReadWrite"
-    bucket_acl> 2
+
+    - Config:      bucket_acl
+    - Env Var:     RCLONE_GCS_BUCKET_ACL
+    - Type:        string
+    - Default:     ""
+    - Examples:
+        - "authenticatedRead"
+            - Project team owners get OWNER access, and all Authenticated Users get READER access.
+        - "private"
+            - Project team owners get OWNER access [default if left blank].
+        - "projectPrivate"
+            - Project team members get access according to their roles.
+        - "publicRead"
+            - Project team owners get OWNER access, and all Users get READER access.
+        - "publicReadWrite"
+            - Project team owners get OWNER access, and all Users get WRITER access.
+
+    #### --gcs-bucket-policy-only
+
+    Access checks should use bucket-level IAM policies.
+
+    If you want to upload objects to a bucket with Bucket Policy Only set
+    then you will need to set this.
+
+    When it is set, rclone:
+
+    - ignores ACLs set on buckets
+    - ignores ACLs set on objects
+    - creates buckets with Bucket Policy Only set
+
+    Docs: https://cloud.google.com/storage/docs/bucket-policy-only
+
+
+    - Config:      bucket_policy_only
+    - Env Var:     RCLONE_GCS_BUCKET_POLICY_ONLY
+    - Type:        bool
+    - Default:     false
+
+    #### --gcs-location
+
     Location for the newly created buckets.
-    Choose a number from below, or type in your own value
-     1 / Empty for default location (US).
-       \ ""
-     2 / Multi-regional location for Asia.
-       \ "asia"
-     3 / Multi-regional location for Europe.
-       \ "eu"
-     4 / Multi-regional location for United States.
-       \ "us"
-     5 / Taiwan.
-       \ "asia-east1"
-     6 / Tokyo.
-       \ "asia-northeast1"
-     7 / Singapore.
-       \ "asia-southeast1"
-     8 / Sydney.
-       \ "australia-southeast1"
-     9 / Belgium.
-       \ "europe-west1"
-    10 / London.
-       \ "europe-west2"
-    11 / Iowa.
-       \ "us-central1"
-    12 / South Carolina.
-       \ "us-east1"
-    13 / Northern Virginia.
-       \ "us-east4"
-    14 / Oregon.
-       \ "us-west1"
-    location> 12
+
+    - Config:      location
+    - Env Var:     RCLONE_GCS_LOCATION
+    - Type:        string
+    - Default:     ""
+    - Examples:
+        - ""
+            - Empty for default location (US).
+        - "asia"
+            - Multi-regional location for Asia.
+        - "eu"
+            - Multi-regional location for Europe.
+        - "us"
+            - Multi-regional location for United States.
+        - "asia-east1"
+            - Taiwan.
+        - "asia-east2"
+            - Hong Kong.
+        - "asia-northeast1"
+            - Tokyo.
+        - "asia-south1"
+            - Mumbai.
+        - "asia-southeast1"
+            - Singapore.
+        - "australia-southeast1"
+            - Sydney.
+        - "europe-north1"
+            - Finland.
+        - "europe-west1"
+            - Belgium.
+        - "europe-west2"
+            - London.
+        - "europe-west3"
+            - Frankfurt.
+        - "europe-west4"
+            - Netherlands.
+        - "us-central1"
+            - Iowa.
+        - "us-east1"
+            - South Carolina.
+        - "us-east4"
+            - Northern Virginia.
+        - "us-west1"
+            - Oregon.
+        - "us-west2"
+            - California.
+
+    #### --gcs-storage-class
+
     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
-       \ ""
-     2 / Multi-regional storage class
-       \ "MULTI_REGIONAL"
-     3 / Regional storage class
-       \ "REGIONAL"
-     4 / Nearline storage class
-       \ "NEARLINE"
-     5 / Coldline storage class
-       \ "COLDLINE"
-     6 / Durable reduced availability storage class
-       \ "DURABLE_REDUCED_AVAILABILITY"
-    storage_class> 5
-    Remote config
-    Use auto config?
-     * Say Y if not sure
-     * Say N if you are working on a remote or headless machine or Y didn't work
-    y) Yes
-    n) No
-    y/n> y
-    If your browser doesn'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
-    --------------------
-    [remote]
-    type = google cloud storage
-    client_id =
-    client_secret =
-    token = {"AccessToken":"xxxx.xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx","RefreshToken":"x/xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx_xxxxxxxxx","Expiry":"2014-07-17T20:49:14.929208288+01:00","Extra":null}
-    project_number = 12345678
-    object_acl = private
-    bucket_acl = private
-    --------------------
-    y) Yes this is OK
-    e) Edit this remote
-    d) Delete this remote
-    y/e/d> y
-
-Note that rclone runs a webserver on your local machine to collect the
-token as returned from Google if you use auto config mode. This only
-runs from the moment it opens your browser to the moment you get back
-the verification code. This is on http://127.0.0.1:53682/ and this it
-may require you to unblock it temporarily if you are running a host
-firewall, or use manual mode.
-
-This remote is called remote and can now be used like this
-
-See all the buckets in your project
-
-    rclone lsd remote:
-
-Make a new bucket
-
-    rclone mkdir remote:bucket
-
-List the contents of a bucket
-
-    rclone ls remote:bucket
-
-Sync /home/local/directory to the remote bucket, deleting any excess
-files in the bucket.
-
-    rclone sync /home/local/directory remote:bucket
-
-Service Account support
-
-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.
-
-To get credentials for Google Cloud Platform IAM Service Accounts,
-please head to the Service Account section of the Google Developer
-Console. Service Accounts behave just like normal User permissions in
-Google Cloud Storage ACLs, 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.
-
-To use a Service Account instead of OAuth2 token flow, enter the path to
-your Service Account credentials at the service_account_file 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 service_account_credentials with the actual contents of the
-file instead, or set the equivalent environment variable.
-
-Application Default Credentials
-
-If no other source of credentials is provided, rclone will fall back to
-Application Default Credentials 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 - see this page.
-
-Note that in the case application default credentials are used, there is
-no need to explicitly configure a project number.
-
-–fast-list
-
-This remote supports --fast-list which allows you to use fewer
-transactions in exchange for more memory. See the rclone docs for more
-details.
-
-Custom upload headers
-
-You can set custom upload headers with the --header-upload flag. Google
-Cloud Storage supports the headers as described in the working with
-metadata documentation
-
--   Cache-Control
--   Content-Disposition
--   Content-Encoding
--   Content-Language
--   Content-Type
--   X-Goog-Meta-
-
-Eg --header-upload "Content-Type text/potato"
-
-Note that the last of these is for setting custom metadata in the form
---header-upload "x-goog-meta-key: value"
 
-Modified time
+    - Config:      storage_class
+    - Env Var:     RCLONE_GCS_STORAGE_CLASS
+    - Type:        string
+    - Default:     ""
+    - Examples:
+        - ""
+            - Default
+        - "MULTI_REGIONAL"
+            - Multi-regional storage class
+        - "REGIONAL"
+            - Regional storage class
+        - "NEARLINE"
+            - Nearline storage class
+        - "COLDLINE"
+            - Coldline storage class
+        - "ARCHIVE"
+            - Archive storage class
+        - "DURABLE_REDUCED_AVAILABILITY"
+            - Durable reduced availability storage class
+
+    ### Advanced Options
+
+    Here are the advanced options specific to google cloud storage (Google Cloud Storage (this is not Google Drive)).
+
+    #### --gcs-token
 
-Google google cloud storage stores md5sums natively and rclone stores
-modification times as metadata on the object, under the “mtime” key in
-RFC3339 format accurate to 1ns.
+    OAuth Access Token as a JSON blob.
 
-Restricted filename characters
+    - Config:      token
+    - Env Var:     RCLONE_GCS_TOKEN
+    - Type:        string
+    - Default:     ""
 
-  Character    Value   Replacement
-  ----------- ------- -------------
-  NUL          0x00         ␀
-  LF           0x0A         ␊
-  CR           0x0D         ␍
-  /            0x2F        ／
+    #### --gcs-auth-url
 
-Invalid UTF-8 bytes will also be replaced, as they can’t be used in JSON
-strings.
+    Auth server URL.
+    Leave blank to use the provider defaults.
 
-Standard Options
+    - Config:      auth_url
+    - Env Var:     RCLONE_GCS_AUTH_URL
+    - Type:        string
+    - Default:     ""
 
-Here are the standard options specific to google cloud storage (Google
-Cloud Storage (this is not Google Drive)).
+    #### --gcs-token-url
 
-–gcs-client-id
+    Token server url.
+    Leave blank to use the provider defaults.
 
-Google Application Client Id Leave blank normally.
+    - Config:      token_url
+    - Env Var:     RCLONE_GCS_TOKEN_URL
+    - Type:        string
+    - Default:     ""
 
--   Config: client_id
--   Env Var: RCLONE_GCS_CLIENT_ID
--   Type: string
--   Default: ""
+    #### --gcs-encoding
 
-–gcs-client-secret
+    This sets the encoding for the backend.
 
-Google Application Client Secret Leave blank normally.
+    See: the [encoding section in the overview](https://rclone.org/overview/#encoding) for more info.
 
--   Config: client_secret
--   Env Var: RCLONE_GCS_CLIENT_SECRET
--   Type: string
--   Default: ""
-
-–gcs-project-number
-
-Project number. Optional - needed only for list/create/delete buckets -
-see your developer console.
+    - Config:      encoding
+    - Env Var:     RCLONE_GCS_ENCODING
+    - Type:        MultiEncoder
+    - Default:     Slash,CrLf,InvalidUtf8,Dot
+
+
+
+     Google Drive
+    -----------------------------------------
+
+    Paths are specified as `drive:path`
+
+    Drive paths may be as deep as required, eg `drive:directory/subdirectory`.
+
+    The initial setup for drive involves getting a token from Google drive
+    which you need to do in your browser.  `rclone config` walks you
+    through it.
+
+    Here is an example of how to make a remote called `remote`.  First run:
+
+         rclone config
+
+    This will guide you through an interactive setup process:
+
+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> n name>
+remote Type of storage to configure. Choose a number from below, or type
+in your own value [snip] XX / Google Drive  "drive" [snip] Storage>
+drive Google Application Client Id - leave blank normally. client_id>
+Google Application Client Secret - leave blank normally. client_secret>
+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.  "drive" 2 / Read-only access to file
+metadata and file contents.  "drive.readonly" / 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.
+ "drive.file" / Allows read and write access to the Application Data
+folder. 4 | This is not visible in the drive website.  "drive.appfolder"
+/ Allows read-only access to file metadata but 5 | does not allow any
+access to read or download file content.  "drive.metadata.readonly"
+scope> 1 ID of the root folder - leave blank normally. Fill in to access
+"Computers" folders. (see docs). root_folder_id> Service Account
+Credentials JSON file path - needed only if you want use SA instead of
+interactive login. service_account_file> Remote config Use auto config?
+* Say Y if not sure * Say N if you are working on a remote or headless
+machine or Y didn't work y) Yes n) No y/n> y If your browser doesn'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 team drive? y) Yes n) No y/n> n --------------------
+[remote] client_id = client_secret = scope = drive root_folder_id =
+service_account_file = token =
+{"access_token":"XXX","token_type":"Bearer","refresh_token":"XXX","expiry":"2014-03-16T13:57:58.955387075Z"}
+-------------------- y) Yes this is OK e) Edit this remote d) Delete
+this remote y/e/d> y
+
+
+    Note that rclone runs a webserver on your local machine to collect the
+    token as returned from Google if you use auto config mode. This only
+    runs from the moment it opens your browser to the moment you get back
+    the verification code.  This is on `http://127.0.0.1:53682/` and this
+    it may require you to unblock it temporarily if you are running a host
+    firewall, or use manual mode.
+
+    You can then use it like this,
+
+    List directories in top level of your drive
+
+        rclone lsd remote:
+
+    List all the files in your drive
+
+        rclone ls remote:
+
+    To copy a local directory to a drive directory called backup
+
+        rclone copy /home/source remote:backup
+
+    ### Scopes ###
+
+    Rclone allows you to select which scope you would like for rclone to
+    use.  This changes what type of token is granted to rclone.  [The
+    scopes are defined
+    here](https://developers.google.com/drive/v3/web/about-auth).
+
+    The scope are
+
+    #### drive ####
+
+    This is the default scope and allows full access to all files, except
+    for the Application Data Folder (see below).
+
+    Choose this one if you aren't sure.
+
+    #### drive.readonly ####
+
+    This allows read only access to all files.  Files may be listed and
+    downloaded but not uploaded, renamed or deleted.
+
+    #### drive.file ####
+
+    With this scope rclone can read/view/modify only those files and
+    folders it creates.
+
+    So if you uploaded files to drive via the web interface (or any other
+    means) they will not be visible to rclone.
+
+    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.
+
+    Files created with this scope are visible in the web interface.
+
+    #### drive.appfolder ####
+
+    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.
+
+    #### drive.metadata.readonly ####
+
+    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.
+
+    ### Root folder ID ###
+
+    You can set the `root_folder_id` for rclone.  This is the directory
+    (identified by its `Folder ID`) that rclone considers to be the root
+    of your drive.
+
+    Normally you will leave this blank and rclone will determine the
+    correct root to use itself.
+
+    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).
+
+    In order to do this you will have to find the `Folder ID` 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.
+
+    So if the folder you want rclone to use has a URL which looks like
+    `https://drive.google.com/drive/folders/1XyfxxxxxxxxxxxxxxxxxxxxxxxxxKHCh`
+    in the browser, then you use `1XyfxxxxxxxxxxxxxxxxxxxxxxxxxKHCh` as
+    the `root_folder_id` in the config.
+
+    **NB** folders under the "Computers" tab seem to be read only (drive
+    gives a 500 error) when using rclone.
+
+    There doesn't appear to be an API to discover the folder IDs of the
+    "Computers" tab - please contact us if you know otherwise!
+
+    Note also that rclone can't access any data under the "Backups" tab on
+    the google drive web interface yet.
+
+    ### Service Account support ###
+
+    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.
+
+    To use a Service Account instead of OAuth2 token flow, enter the path
+    to your Service Account credentials at the `service_account_file`
+    prompt during `rclone config` 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
+    `service_account_credentials` with the actual contents of the file
+    instead, or set the equivalent environment variable.
+
+    #### Use case - Google Apps/G-suite account and individual Drive ####
+
+    Let's say that you are the administrator of a Google Apps (old) or
+    G-suite account.
+    The goal is to store data on an individual's Drive account, who IS
+    a member of the domain.
+    We'll call the domain **example.com**, and the user
+    **foo@example.com**.
+
+    There's a few steps we need to go through to accomplish this:
+
+    ##### 1. Create a service account for example.com #####
+      - To create a service account and obtain its credentials, go to the
+    [Google Developer Console](https://console.developers.google.com).
+      - You must have a project - create one if you don't.
+      - Then go to "IAM & admin" -> "Service Accounts".
+      - Use the "Create Credentials" button. Fill in "Service account name"
+    with something that identifies your client. "Role" can be empty.
+      - Tick "Furnish a new private key" - select "Key type JSON".
+      - Tick "Enable G Suite Domain-wide Delegation". This option makes
+    "impersonation" possible, as documented here:
+    [Delegating domain-wide authority to the service account](https://developers.google.com/identity/protocols/OAuth2ServiceAccount#delegatingauthority)
+      - These credentials are what rclone will use for authentication.
+    If you ever need to remove access, press the "Delete service
+    account key" button.
+
+    ##### 2. Allowing API access to example.com Google Drive #####
+      - Go to example.com's admin console
+      - Go into "Security" (or use the search bar)
+      - Select "Show more" and then "Advanced settings"
+      - Select "Manage API client access" in the "Authentication" section
+      - In the "Client Name" field enter the service account's
+    "Client ID" - this can be found in the Developer Console under
+    "IAM & Admin" -> "Service Accounts", then "View Client ID" for
+    the newly created service account.
+    It is a ~21 character numerical string.
+      - In the next field, "One or More API Scopes", enter
+    `https://www.googleapis.com/auth/drive`
+    to grant access to Google Drive specifically.
+
+    ##### 3. Configure rclone, assuming a new install #####
+
+rclone config
+
+n/s/q> n # New name>gdrive # Gdrive is an example name Storage> # Select
+the number shown for Google Drive client_id> # Can be left blank
+client_secret> # Can be left blank scope> # Select your scope, 1 for
+example root_folder_id> # Can be left blank service_account_file>
+/home/foo/myJSONfile.json # This is where the JSON file goes! y/n> #
+Auto config, y
+
+
+    ##### 4. Verify that it's working #####
+      - `rclone -v --drive-impersonate foo@example.com lsf gdrive:backup`
+      - The arguments do:
+        - `-v` - verbose logging
+        - `--drive-impersonate foo@example.com` - this is what does
+    the magic, pretending to be user foo.
+        - `lsf` - list files in a parsing friendly way
+        - `gdrive:backup` - use the remote called gdrive, work in
+    the folder named backup.
+
+    Note: in case you configured a specific root folder on gdrive and rclone is unable to access the contents of that folder when using `--drive-impersonate`, 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 `--drive-impersonate` option, like this:
+            `rclone -v foo@example.com lsf gdrive:backup`
+
+
+    ### Team drives ###
+
+    If you want to configure the remote to point to a Google Team Drive
+    then answer `y` to the question `Configure this as a team drive?`.
+
+    This will fetch the list of Team Drives from google and allow you to
+    configure which one you want to use.  You can also type in a team
+    drive ID if you prefer.
+
+    For example:
+
+Configure this as a team drive? y) Yes n) No y/n> y Fetching team drive
+list... Choose a number from below, or type in your own value 1 / Rclone
+Test  "xxxxxxxxxxxxxxxxxxxx" 2 / Rclone Test 2  "yyyyyyyyyyyyyyyyyyyy" 3
+/ Rclone Test 3  "zzzzzzzzzzzzzzzzzzzz" Enter a Team Drive ID> 1
+-------------------- [remote] client_id = client_secret = token =
+{"AccessToken":"xxxx.x.xxxxx_xxxxxxxxxxx_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx","RefreshToken":"1/xxxxxxxxxxxxxxxx_xxxxxxxxxxxxxxxxxxxxxxxxxx","Expiry":"2014-03-16T13:57:58.955387075Z","Extra":null}
+team_drive = xxxxxxxxxxxxxxxxxxxx -------------------- y) Yes this is OK
+e) Edit this remote d) Delete this remote y/e/d> y
+
+
+    ### --fast-list ###
+
+    This remote supports `--fast-list` which allows you to use fewer
+    transactions in exchange for more memory. See the [rclone
+    docs](https://rclone.org/docs/#fast-list) for more details.
+
+    It does this by combining multiple `list` calls into a single API request.
+
+    This works by combining many `'%s' in parents` filters into one expression.
+    To list the contents of directories a, b and c, the following requests will be send by the regular `List` function:
+
+trashed=false and 'a' in parents trashed=false and 'b' in parents
+trashed=false and 'c' in parents
+
+    These can now be combined into a single request:
+
+trashed=false and ('a' in parents or 'b' in parents or 'c' in parents)
+
+
+    The implementation of `ListR` will put up to 50 `parents` filters into one request.
+    It will  use the `--checkers` value to specify the number of requests to run in parallel.
+
+    In tests, these batch requests were up to 20x faster than the regular method.
+    Running the following command against different sized folders gives:
+
+rclone lsjson -vv -R --checkers=6 gdrive:folder
+
+
+    small folder (220 directories, 700 files):
+
+    - without `--fast-list`: 38s
+    - with `--fast-list`: 10s
+
+    large folder (10600 directories, 39000 files):
+
+    - without `--fast-list`: 22:05 min
+    - with `--fast-list`: 58s
+
+    ### Modified time ###
+
+    Google drive stores modification times accurate to 1 ms.
+
+    #### Restricted filename characters
+
+    Only Invalid UTF-8 bytes will be [replaced](https://rclone.org/overview/#invalid-utf8),
+    as they can't be used in JSON strings.
+
+    In contrast to other backends, `/` can also be used in names and `.`
+    or `..` are valid names.
+
+    ### Revisions ###
+
+    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.
+
+    Revisions follow the standard google policy which at time of writing
+    was
+
+      * They are deleted after 30 days or 100 revisions (whatever comes first).
+      * They do not count towards a user storage quota.
+
+    ### Deleting files ###
+
+    By default rclone will send all files to the trash when deleting
+    files.  If deleting them permanently is required then use the
+    `--drive-use-trash=false` flag, or set the equivalent environment
+    variable.
+
+    ### Shortcuts ###
+
+    In March 2020 Google introduced a new feature in Google Drive called
+    [drive shortcuts](https://support.google.com/drive/answer/9700156)
+    ([API](https://developers.google.com/drive/api/v3/shortcuts)). These
+    will (by September 2020) [replace the ability for files or folders to
+    be in multiple folders at once](https://cloud.google.com/blog/products/g-suite/simplifying-google-drives-folder-structure-and-sharing-models).
+
+    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
+    (eg the inode in unix terms) so they don't break if the source is
+    renamed or moved about.
+
+    Be default rclone treats these as follows.
+
+    For shortcuts pointing to files:
+
+    - When listing a file shortcut appears as the destination file.
+    - When downloading the contents of the destination file is downloaded.
+    - When updating shortcut file with a non shortcut file, the shortcut is removed then a new file is uploaded in place of the shortcut.
+    - When server side moving (renaming) the shortcut is renamed, not the destination file.
+    - When server side copying the shortcut is copied, not the contents of the shortcut.
+    - When deleting the shortcut is deleted not the linked file.
+    - When setting the modification time, the modification time of the linked file will be set.
+
+    For shortcuts pointing to folders:
+
+    - When listing the shortcut appears as a folder and that folder will contain the contents of the linked folder appear (including any sub folders)
+    - When downloading the contents of the linked folder and sub contents are downloaded
+    - When uploading to a shortcut folder the file will be placed in the linked folder
+    - When server side moving (renaming) the shortcut is renamed, not the destination folder
+    - When server side copying the contents of the linked folder is copied, not the shortcut.
+    - When deleting with `rclone rmdir` or `rclone purge` the shortcut is deleted not the linked folder.
+    - **NB** When deleting with `rclone remove` or `rclone mount` the contents of the linked folder will be deleted.
+
+    The [rclone backend](https://rclone.org/commands/rclone_backend/) command can be used to create shortcuts.  
+
+    Shortcuts can be completely ignored with the `--drive-skip-shortcuts` flag
+    or the corresponding `skip_shortcuts` configuration setting.
+
+    ### Emptying trash ###
+
+    If you wish to empty your trash you can use the `rclone cleanup remote:`
+    command which will permanently delete all your trashed files. This command
+    does not take any path arguments.
+
+    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.
+
+    ### Quota information ###
+
+    To view your current quota you can use the `rclone about remote:`
+    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.
+
+    #### Import/Export of google documents ####
+
+    Google documents can be exported from and uploaded to Google Drive.
+
+    When rclone downloads a Google doc it chooses a format to download
+    depending upon the `--drive-export-formats` setting.
+    By default the export formats are `docx,xlsx,pptx,svg` which are a
+    sensible default for an editable document.
+
+    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.
+
+    If you prefer an archive copy then you might use `--drive-export-formats
+    pdf`, or if you prefer openoffice/libreoffice formats you might use
+    `--drive-export-formats ods,odt,odp`.
+
+    Note that rclone adds the extension to the google doc, so if it is
+    called `My Spreadsheet` on google docs, it will be exported as `My
+    Spreadsheet.xlsx` or `My Spreadsheet.pdf` etc.
+
+    When importing files into Google Drive, rclone will convert all
+    files with an extension in `--drive-import-formats` to their
+    associated document type.
+    rclone will not convert any files by default, since the conversion
+    is lossy process.
+
+    The conversion must result in a file with the same extension when
+    the `--drive-export-formats` rules are applied to the uploaded document.
+
+    Here are some examples for allowed and prohibited conversions.
+
+    | export-formats | import-formats | Upload Ext | Document Ext | Allowed |
+    | -------------- | -------------- | ---------- | ------------ | ------- |
+    | odt | odt | odt | odt | Yes |
+    | odt | docx,odt | odt | odt | Yes |
+    |  | docx | docx | docx | Yes |
+    |  | odt | odt | docx | No |
+    | odt,docx | docx,odt | docx | odt | No |
+    | docx,odt | docx,odt | docx | docx | Yes |
+    | docx,odt | docx,odt | odt | docx | No |
+
+    This limitation can be disabled by specifying `--drive-allow-import-name-change`.
+    When using this flag, rclone can convert multiple files types resulting
+    in the same document type at once, eg with `--drive-import-formats docx,odt,txt`,
+    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. 
+
+    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.
+
+    This list can be changed by Google Drive at any time and might not
+    represent the currently available conversions.
+
+    | Extension | Mime Type | Description |
+    | --------- |-----------| ------------|
+    | csv  | text/csv | Standard CSV format for Spreadsheets |
+    | docx | application/vnd.openxmlformats-officedocument.wordprocessingml.document | Microsoft Office Document |
+    | epub | application/epub+zip | E-book format |
+    | html | text/html | An HTML Document |
+    | jpg  | image/jpeg | A JPEG Image File |
+    | json | application/vnd.google-apps.script+json | JSON Text Format |
+    | odp  | application/vnd.oasis.opendocument.presentation | Openoffice Presentation |
+    | ods  | application/vnd.oasis.opendocument.spreadsheet | Openoffice Spreadsheet |
+    | ods  | application/x-vnd.oasis.opendocument.spreadsheet | Openoffice Spreadsheet |
+    | odt  | application/vnd.oasis.opendocument.text | Openoffice Document |
+    | pdf  | application/pdf | Adobe PDF Format |
+    | png  | image/png | PNG Image Format|
+    | pptx | application/vnd.openxmlformats-officedocument.presentationml.presentation | Microsoft Office Powerpoint |
+    | rtf  | application/rtf | Rich Text Format |
+    | svg  | image/svg+xml | Scalable Vector Graphics Format |
+    | tsv  | text/tab-separated-values | Standard TSV format for spreadsheets |
+    | txt  | text/plain | Plain Text |
+    | xlsx | application/vnd.openxmlformats-officedocument.spreadsheetml.sheet | Microsoft Office Spreadsheet |
+    | zip  | application/zip | A ZIP file of HTML, Images CSS |
+
+    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
+    `--drive-export-formats` parameter. They will match all available
+    Google Documents.
+
+    | Extension | Description | OS Support |
+    | --------- | ----------- | ---------- |
+    | desktop | freedesktop.org specified desktop entry | Linux |
+    | link.html | An HTML Document with a redirect | All |
+    | url | INI style link file | macOS, Windows |
+    | webloc | macOS specific XML format | macOS |
+
+
+    ### Standard Options
+
+    Here are the standard options specific to drive (Google Drive).
+
+    #### --drive-client-id
+
+    OAuth Client Id
+    Leave blank normally.
+
+    - Config:      client_id
+    - Env Var:     RCLONE_DRIVE_CLIENT_ID
+    - Type:        string
+    - Default:     ""
+
+    #### --drive-client-secret
+
+    OAuth Client Secret
+    Leave blank normally.
+
+    - Config:      client_secret
+    - Env Var:     RCLONE_DRIVE_CLIENT_SECRET
+    - Type:        string
+    - Default:     ""
+
+    #### --drive-scope
 
--   Config: project_number
--   Env Var: RCLONE_GCS_PROJECT_NUMBER
--   Type: string
--   Default: ""
-
-–gcs-service-account-file
-
-Service Account Credentials JSON file path Leave blank normally. Needed
-only if you want use SA instead of interactive login.
-
--   Config: service_account_file
--   Env Var: RCLONE_GCS_SERVICE_ACCOUNT_FILE
--   Type: string
--   Default: ""
-
-–gcs-service-account-credentials
-
-Service Account Credentials JSON blob Leave blank normally. Needed only
-if you want use SA instead of interactive login.
-
--   Config: service_account_credentials
--   Env Var: RCLONE_GCS_SERVICE_ACCOUNT_CREDENTIALS
--   Type: string
--   Default: ""
-
-–gcs-object-acl
-
-Access Control List for new objects.
-
--   Config: object_acl
--   Env Var: RCLONE_GCS_OBJECT_ACL
--   Type: string
--   Default: ""
--   Examples:
-    -   “authenticatedRead”
-        -   Object owner gets OWNER access, and all Authenticated Users
-            get READER access.
-    -   “bucketOwnerFullControl”
-        -   Object owner gets OWNER access, and project team owners get
-            OWNER access.
-    -   “bucketOwnerRead”
-        -   Object owner gets OWNER access, and project team owners get
-            READER access.
-    -   “private”
-        -   Object owner gets OWNER access [default if left blank].
-    -   “projectPrivate”
-        -   Object owner gets OWNER access, and project team members get
-            access according to their roles.
-    -   “publicRead”
-        -   Object owner gets OWNER access, and all Users get READER
-            access.
-
-–gcs-bucket-acl
-
-Access Control List for new buckets.
-
--   Config: bucket_acl
--   Env Var: RCLONE_GCS_BUCKET_ACL
--   Type: string
--   Default: ""
--   Examples:
-    -   “authenticatedRead”
-        -   Project team owners get OWNER access, and all Authenticated
-            Users get READER access.
-    -   “private”
-        -   Project team owners get OWNER access [default if left
-            blank].
-    -   “projectPrivate”
-        -   Project team members get access according to their roles.
-    -   “publicRead”
-        -   Project team owners get OWNER access, and all Users get
-            READER access.
-    -   “publicReadWrite”
-        -   Project team owners get OWNER access, and all Users get
-            WRITER access.
-
-–gcs-bucket-policy-only
-
-Access checks should use bucket-level IAM policies.
-
-If you want to upload objects to a bucket with Bucket Policy Only set
-then you will need to set this.
-
-When it is set, rclone:
-
--   ignores ACLs set on buckets
--   ignores ACLs set on objects
--   creates buckets with Bucket Policy Only set
-
-Docs: https://cloud.google.com/storage/docs/bucket-policy-only
-
--   Config: bucket_policy_only
--   Env Var: RCLONE_GCS_BUCKET_POLICY_ONLY
--   Type: bool
--   Default: false
-
-–gcs-location
-
-Location for the newly created buckets.
-
--   Config: location
--   Env Var: RCLONE_GCS_LOCATION
--   Type: string
--   Default: ""
--   Examples:
-    -   ""
-        -   Empty for default location (US).
-    -   “asia”
-        -   Multi-regional location for Asia.
-    -   “eu”
-        -   Multi-regional location for Europe.
-    -   “us”
-        -   Multi-regional location for United States.
-    -   “asia-east1”
-        -   Taiwan.
-    -   “asia-east2”
-        -   Hong Kong.
-    -   “asia-northeast1”
-        -   Tokyo.
-    -   “asia-south1”
-        -   Mumbai.
-    -   “asia-southeast1”
-        -   Singapore.
-    -   “australia-southeast1”
-        -   Sydney.
-    -   “europe-north1”
-        -   Finland.
-    -   “europe-west1”
-        -   Belgium.
-    -   “europe-west2”
-        -   London.
-    -   “europe-west3”
-        -   Frankfurt.
-    -   “europe-west4”
-        -   Netherlands.
-    -   “us-central1”
-        -   Iowa.
-    -   “us-east1”
-        -   South Carolina.
-    -   “us-east4”
-        -   Northern Virginia.
-    -   “us-west1”
-        -   Oregon.
-    -   “us-west2”
-        -   California.
-
-–gcs-storage-class
-
-The storage class to use when storing objects in Google Cloud Storage.
-
--   Config: storage_class
--   Env Var: RCLONE_GCS_STORAGE_CLASS
--   Type: string
--   Default: ""
--   Examples:
-    -   ""
-        -   Default
-    -   “MULTI_REGIONAL”
-        -   Multi-regional storage class
-    -   “REGIONAL”
-        -   Regional storage class
-    -   “NEARLINE”
-        -   Nearline storage class
-    -   “COLDLINE”
-        -   Coldline storage class
-    -   “ARCHIVE”
-        -   Archive storage class
-    -   “DURABLE_REDUCED_AVAILABILITY”
-        -   Durable reduced availability storage class
-
-Advanced Options
-
-Here are the advanced options specific to google cloud storage (Google
-Cloud Storage (this is not Google Drive)).
-
-–gcs-encoding
-
-This sets the encoding for the backend.
-
-See: the encoding section in the overview for more info.
-
--   Config: encoding
--   Env Var: RCLONE_GCS_ENCODING
--   Type: MultiEncoder
--   Default: Slash,CrLf,InvalidUtf8,Dot
-
-
-Google Drive
-
-Paths are specified as drive:path
-
-Drive paths may be as deep as required, eg drive:directory/subdirectory.
-
-The initial setup for drive involves getting a token from Google drive
-which you need to do in your browser. rclone config walks you through
-it.
-
-Here is an example of how to make a remote called remote. First run:
-
-     rclone config
-
-This will guide you through an interactive setup process:
-
-    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> n
-    name> remote
-    Type of storage to configure.
-    Choose a number from below, or type in your own value
-    [snip]
-    XX / Google Drive
-       \ "drive"
-    [snip]
-    Storage> drive
-    Google Application Client Id - leave blank normally.
-    client_id>
-    Google Application Client Secret - leave blank normally.
-    client_secret>
     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.
-       \ "drive"
-     2 / Read-only access to file metadata and file contents.
-       \ "drive.readonly"
-       / 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.
-       \ "drive.file"
-       / Allows read and write access to the Application Data folder.
-     4 | This is not visible in the drive website.
-       \ "drive.appfolder"
-       / Allows read-only access to file metadata but
-     5 | does not allow any access to read or download file content.
-       \ "drive.metadata.readonly"
-    scope> 1
-    ID of the root folder - leave blank normally.  Fill in to access "Computers" folders. (see docs).
-    root_folder_id> 
-    Service Account Credentials JSON file path - needed only if you want use SA instead of interactive login.
-    service_account_file>
-    Remote config
-    Use auto config?
-     * Say Y if not sure
-     * Say N if you are working on a remote or headless machine or Y didn't work
-    y) Yes
-    n) No
-    y/n> y
-    If your browser doesn'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 team drive?
-    y) Yes
-    n) No
-    y/n> n
-    --------------------
-    [remote]
-    client_id = 
-    client_secret = 
-    scope = drive
-    root_folder_id = 
-    service_account_file =
-    token = {"access_token":"XXX","token_type":"Bearer","refresh_token":"XXX","expiry":"2014-03-16T13:57:58.955387075Z"}
-    --------------------
-    y) Yes this is OK
-    e) Edit this remote
-    d) Delete this remote
-    y/e/d> y
 
-Note that rclone runs a webserver on your local machine to collect the
-token as returned from Google if you use auto config mode. This only
-runs from the moment it opens your browser to the moment you get back
-the verification code. This is on http://127.0.0.1:53682/ and this it
-may require you to unblock it temporarily if you are running a host
-firewall, or use manual mode.
-
-You can then use it like this,
-
-List directories in top level of your drive
-
-    rclone lsd remote:
-
-List all the files in your drive
-
-    rclone ls remote:
-
-To copy a local directory to a drive directory called backup
-
-    rclone copy /home/source remote:backup
-
-Scopes
-
-Rclone allows you to select which scope you would like for rclone to
-use. This changes what type of token is granted to rclone. The scopes
-are defined here.
-
-The scope are
-
-drive
-
-This is the default scope and allows full access to all files, except
-for the Application Data Folder (see below).
-
-Choose this one if you aren’t sure.
-
-drive.readonly
-
-This allows read only access to all files. Files may be listed and
-downloaded but not uploaded, renamed or deleted.
-
-drive.file
-
-With this scope rclone can read/view/modify only those files and folders
-it creates.
-
-So if you uploaded files to drive via the web interface (or any other
-means) they will not be visible to rclone.
-
-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.
-
-Files created with this scope are visible in the web interface.
-
-drive.appfolder
-
-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.
-
-drive.metadata.readonly
-
-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.
-
-Root folder ID
-
-You can set the root_folder_id for rclone. This is the directory
-(identified by its Folder ID) that rclone considers to be the root of
-your drive.
-
-Normally you will leave this blank and rclone will determine the correct
-root to use itself.
-
-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).
-
-In order to do this you will have to find the Folder ID 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.
-
-So if the folder you want rclone to use has a URL which looks like
-https://drive.google.com/drive/folders/1XyfxxxxxxxxxxxxxxxxxxxxxxxxxKHCh
-in the browser, then you use 1XyfxxxxxxxxxxxxxxxxxxxxxxxxxKHCh as the
-root_folder_id in the config.
-
-NB folders under the “Computers” tab seem to be read only (drive gives a
-500 error) when using rclone.
-
-There doesn’t appear to be an API to discover the folder IDs of the
-“Computers” tab - please contact us if you know otherwise!
-
-Note also that rclone can’t access any data under the “Backups” tab on
-the google drive web interface yet.
-
-Service Account support
-
-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.
-
-To use a Service Account instead of OAuth2 token flow, enter the path to
-your Service Account credentials at the service_account_file prompt
-during rclone config 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
-service_account_credentials with the actual contents of the file
-instead, or set the equivalent environment variable.
-
-Use case - Google Apps/G-suite account and individual Drive
-
-Let’s say that you are the administrator of a Google Apps (old) or
-G-suite account. The goal is to store data on an individual’s Drive
-account, who IS a member of the domain. We’ll call the domain
-EXAMPLE.COM, and the user FOO@EXAMPLE.COM.
-
-There’s a few steps we need to go through to accomplish this:
-
-1. Create a service account for example.com
-
--   To create a service account and obtain its credentials, go to the
-    Google Developer Console.
--   You must have a project - create one if you don’t.
--   Then go to “IAM & admin” -> “Service Accounts”.
--   Use the “Create Credentials” button. Fill in “Service account name”
-    with something that identifies your client. “Role” can be empty.
--   Tick “Furnish a new private key” - select “Key type JSON”.
--   Tick “Enable G Suite Domain-wide Delegation”. This option makes
-    “impersonation” possible, as documented here: Delegating domain-wide
-    authority to the service account
--   These credentials are what rclone will use for authentication. If
-    you ever need to remove access, press the “Delete service account
-    key” button.
-
-2. Allowing API access to example.com Google Drive
-
--   Go to example.com’s admin console
--   Go into “Security” (or use the search bar)
--   Select “Show more” and then “Advanced settings”
--   Select “Manage API client access” in the “Authentication” section
--   In the “Client Name” field enter the service account’s “Client ID” -
-    this can be found in the Developer Console under “IAM & Admin” ->
-    “Service Accounts”, then “View Client ID” for the newly created
-    service account. It is a ~21 character numerical string.
--   In the next field, “One or More API Scopes”, enter
-    https://www.googleapis.com/auth/drive to grant access to Google
-    Drive specifically.
-
-3. Configure rclone, assuming a new install
-
-    rclone config
-
-    n/s/q> n         # New
-    name>gdrive      # Gdrive is an example name
-    Storage>         # Select the number shown for Google Drive
-    client_id>       # Can be left blank
-    client_secret>   # Can be left blank
-    scope>           # Select your scope, 1 for example
-    root_folder_id>  # Can be left blank
-    service_account_file> /home/foo/myJSONfile.json # This is where the JSON file goes!
-    y/n>             # Auto config, y
-
-4. Verify that it’s working
-
--   rclone -v --drive-impersonate foo@example.com lsf gdrive:backup
--   The arguments do:
-    -   -v - verbose logging
-    -   --drive-impersonate foo@example.com - this is what does the
-        magic, pretending to be user foo.
-    -   lsf - list files in a parsing friendly way
-    -   gdrive:backup - use the remote called gdrive, work in the folder
-        named backup.
-
-Team drives
-
-If you want to configure the remote to point to a Google Team Drive then
-answer y to the question Configure this as a team drive?.
-
-This will fetch the list of Team Drives from google and allow you to
-configure which one you want to use. You can also type in a team drive
-ID if you prefer.
-
-For example:
-
-    Configure this as a team drive?
-    y) Yes
-    n) No
-    y/n> y
-    Fetching team drive list...
-    Choose a number from below, or type in your own value
-     1 / Rclone Test
-       \ "xxxxxxxxxxxxxxxxxxxx"
-     2 / Rclone Test 2
-       \ "yyyyyyyyyyyyyyyyyyyy"
-     3 / Rclone Test 3
-       \ "zzzzzzzzzzzzzzzzzzzz"
-    Enter a Team Drive ID> 1
-    --------------------
-    [remote]
-    client_id =
-    client_secret =
-    token = {"AccessToken":"xxxx.x.xxxxx_xxxxxxxxxxx_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx","RefreshToken":"1/xxxxxxxxxxxxxxxx_xxxxxxxxxxxxxxxxxxxxxxxxxx","Expiry":"2014-03-16T13:57:58.955387075Z","Extra":null}
-    team_drive = xxxxxxxxxxxxxxxxxxxx
-    --------------------
-    y) Yes this is OK
-    e) Edit this remote
-    d) Delete this remote
-    y/e/d> y
-
-–fast-list
-
-This remote supports --fast-list which allows you to use fewer
-transactions in exchange for more memory. See the rclone docs for more
-details.
-
-It does this by combining multiple list calls into a single API request.
-
-This works by combining many '%s' in parents filters into one
-expression. To list the contents of directories a, b and c, the
-following requests will be send by the regular List function:
-
-    trashed=false and 'a' in parents
-    trashed=false and 'b' in parents
-    trashed=false and 'c' in parents
-
-These can now be combined into a single request:
-
-    trashed=false and ('a' in parents or 'b' in parents or 'c' in parents)
-
-The implementation of ListR will put up to 50 parents filters into one
-request. It will use the --checkers value to specify the number of
-requests to run in parallel.
-
-In tests, these batch requests were up to 20x faster than the regular
-method. Running the following command against different sized folders
-gives:
-
-    rclone lsjson -vv -R --checkers=6 gdrive:folder
-
-small folder (220 directories, 700 files):
-
--   without --fast-list: 38s
--   with --fast-list: 10s
-
-large folder (10600 directories, 39000 files):
-
--   without --fast-list: 22:05 min
--   with --fast-list: 58s
-
-Modified time
-
-Google drive stores modification times accurate to 1 ms.
-
-Restricted filename characters
-
-Only Invalid UTF-8 bytes will be replaced, as they can’t be used in JSON
-strings.
-
-In contrast to other backends, / can also be used in names and . or ..
-are valid names.
-
-Revisions
-
-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.
-
-Revisions follow the standard google policy which at time of writing was
-
--   They are deleted after 30 days or 100 revisions (whatever comes
-    first).
--   They do not count towards a user storage quota.
-
-Deleting files
-
-By default rclone will send all files to the trash when deleting files.
-If deleting them permanently is required then use the
---drive-use-trash=false flag, or set the equivalent environment
-variable.
-
-Shortcuts
-
-In March 2020 Google introduced a new feature in Google Drive called
-drive shortcuts (API). These will (by September 2020) replace the
-ability for files or folders to be in multiple folders at once.
-
-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
-(eg the inode in unix terms) so they don’t break if the source is
-renamed or moved about.
-
-Be default rclone treats these as follows.
-
-For shortcuts pointing to files:
-
--   When listing a file shortcut appears as the destination file.
--   When downloading the contents of the destination file is downloaded.
--   When updating shortcut file with a non shortcut file, the shortcut
-    is removed then a new file is uploaded in place of the shortcut.
--   When server side moving (renaming) the shortcut is renamed, not the
-    destination file.
--   When server side copying the shortcut is copied, not the contents of
-    the shortcut.
--   When deleting the shortcut is deleted not the linked file.
--   When setting the modification time, the modification time of the
-    linked file will be set.
-
-For shortcuts pointing to folders:
-
--   When listing the shortcut appears as a folder and that folder will
-    contain the contents of the linked folder appear (including any sub
-    folders)
--   When downloading the contents of the linked folder and sub contents
-    are downloaded
--   When uploading to a shortcut folder the file will be placed in the
-    linked folder
--   When server side moving (renaming) the shortcut is renamed, not the
-    destination folder
--   When server side copying the contents of the linked folder is
-    copied, not the shortcut.
--   When deleting with rclone rmdir or rclone purge the shortcut is
-    deleted not the linked folder.
--   NB When deleting with rclone remove or rclone mount the contents of
-    the linked folder will be deleted.
-
-It isn’t currently possible to create shortcuts with rclone.
-
-Shortcuts can be completely ignored with the --drive-skip-shortcuts flag
-or the corresponding skip_shortcuts configuration setting.
-
-Emptying trash
-
-If you wish to empty your trash you can use the rclone cleanup remote:
-command which will permanently delete all your trashed files. This
-command does not take any path arguments.
-
-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.
-
-Quota information
-
-To view your current quota you can use the rclone about remote: 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.
-
-Import/Export of google documents
-
-Google documents can be exported from and uploaded to Google Drive.
-
-When rclone downloads a Google doc it chooses a format to download
-depending upon the --drive-export-formats setting. By default the export
-formats are docx,xlsx,pptx,svg which are a sensible default for an
-editable document.
-
-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.
-
-If you prefer an archive copy then you might use
---drive-export-formats pdf, or if you prefer openoffice/libreoffice
-formats you might use --drive-export-formats ods,odt,odp.
-
-Note that rclone adds the extension to the google doc, so if it is
-called My Spreadsheet on google docs, it will be exported as
-My Spreadsheet.xlsx or My Spreadsheet.pdf etc.
-
-When importing files into Google Drive, rclone will convert all files
-with an extension in --drive-import-formats to their associated document
-type. rclone will not convert any files by default, since the conversion
-is lossy process.
-
-The conversion must result in a file with the same extension when the
---drive-export-formats rules are applied to the uploaded document.
-
-Here are some examples for allowed and prohibited conversions.
-
-  export-formats   import-formats   Upload Ext   Document Ext   Allowed
-  ---------------- ---------------- ------------ -------------- ---------
-  odt              odt              odt          odt            Yes
-  odt              docx,odt         odt          odt            Yes
-                   docx             docx         docx           Yes
-                   odt              odt          docx           No
-  odt,docx         docx,odt         docx         odt            No
-  docx,odt         docx,odt         docx         docx           Yes
-  docx,odt         docx,odt         odt          docx           No
-
-This limitation can be disabled by specifying
---drive-allow-import-name-change. When using this flag, rclone can
-convert multiple files types resulting in the same document type at
-once, eg with --drive-import-formats docx,odt,txt, 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.
-
-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.
-
-This list can be changed by Google Drive at any time and might not
-represent the currently available conversions.
-
-  --------------------------------------------------------------------------------------------------------------------------
-  Extension           Mime Type                                                                   Description
-  ------------------- --------------------------------------------------------------------------- --------------------------
-  csv                 text/csv                                                                    Standard CSV format for
-                                                                                                  Spreadsheets
-
-  docx                application/vnd.openxmlformats-officedocument.wordprocessingml.document     Microsoft Office Document
-
-  epub                application/epub+zip                                                        E-book format
-
-  html                text/html                                                                   An HTML Document
-
-  jpg                 image/jpeg                                                                  A JPEG Image File
-
-  json                application/vnd.google-apps.script+json                                     JSON Text Format
-
-  odp                 application/vnd.oasis.opendocument.presentation                             Openoffice Presentation
-
-  ods                 application/vnd.oasis.opendocument.spreadsheet                              Openoffice Spreadsheet
-
-  ods                 application/x-vnd.oasis.opendocument.spreadsheet                            Openoffice Spreadsheet
-
-  odt                 application/vnd.oasis.opendocument.text                                     Openoffice Document
-
-  pdf                 application/pdf                                                             Adobe PDF Format
-
-  png                 image/png                                                                   PNG Image Format
-
-  pptx                application/vnd.openxmlformats-officedocument.presentationml.presentation   Microsoft Office
-                                                                                                  Powerpoint
-
-  rtf                 application/rtf                                                             Rich Text Format
-
-  svg                 image/svg+xml                                                               Scalable Vector Graphics
-                                                                                                  Format
-
-  tsv                 text/tab-separated-values                                                   Standard TSV format for
-                                                                                                  spreadsheets
-
-  txt                 text/plain                                                                  Plain Text
-
-  xlsx                application/vnd.openxmlformats-officedocument.spreadsheetml.sheet           Microsoft Office
-                                                                                                  Spreadsheet
-
-  zip                 application/zip                                                             A ZIP file of HTML, Images
-                                                                                                  CSS
-  --------------------------------------------------------------------------------------------------------------------------
-
-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
---drive-export-formats parameter. They will match all available Google
-Documents.
-
-  Extension   Description                               OS Support
-  ----------- ----------------------------------------- ----------------
-  desktop     freedesktop.org specified desktop entry   Linux
-  link.html   An HTML Document with a redirect          All
-  url         INI style link file                       macOS, Windows
-  webloc      macOS specific XML format                 macOS
-
-Standard Options
-
-Here are the standard options specific to drive (Google Drive).
-
-–drive-client-id
-
-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.
-
--   Config: client_id
--   Env Var: RCLONE_DRIVE_CLIENT_ID
--   Type: string
--   Default: ""
-
-–drive-client-secret
-
-Google Application Client Secret Setting your own is recommended.
-
--   Config: client_secret
--   Env Var: RCLONE_DRIVE_CLIENT_SECRET
--   Type: string
--   Default: ""
-
-–drive-scope
-
-Scope that rclone should use when requesting access from drive.
-
--   Config: scope
--   Env Var: RCLONE_DRIVE_SCOPE
--   Type: string
--   Default: ""
--   Examples:
-    -   “drive”
-        -   Full access all files, excluding Application Data Folder.
-    -   “drive.readonly”
-        -   Read-only access to file metadata and file contents.
-    -   “drive.file”
-        -   Access to files created by rclone only.
-        -   These are visible in the drive website.
-        -   File authorization is revoked when the user deauthorizes the
-            app.
-    -   “drive.appfolder”
-        -   Allows read and write access to the Application Data folder.
-        -   This is not visible in the drive website.
-    -   “drive.metadata.readonly”
-        -   Allows read-only access to file metadata but
-        -   does not allow any access to read or download file content.
-
-–drive-root-folder-id
-
-ID of the root folder Leave blank normally.
-
-Fill in to access “Computers” folders (see docs), or for rclone to use a
-non root folder as its starting point.
-
-Note that if this is blank, the first time rclone runs it will fill it
-in with the ID of the root folder.
-
--   Config: root_folder_id
--   Env Var: RCLONE_DRIVE_ROOT_FOLDER_ID
--   Type: string
--   Default: ""
-
-–drive-service-account-file
-
-Service Account Credentials JSON file path Leave blank normally. Needed
-only if you want use SA instead of interactive login.
-
--   Config: service_account_file
--   Env Var: RCLONE_DRIVE_SERVICE_ACCOUNT_FILE
--   Type: string
--   Default: ""
-
-Advanced Options
-
-Here are the advanced options specific to drive (Google Drive).
-
-–drive-service-account-credentials
-
-Service Account Credentials JSON blob Leave blank normally. Needed only
-if you want use SA instead of interactive login.
-
--   Config: service_account_credentials
--   Env Var: RCLONE_DRIVE_SERVICE_ACCOUNT_CREDENTIALS
--   Type: string
--   Default: ""
-
-–drive-team-drive
-
-ID of the Team Drive
-
--   Config: team_drive
--   Env Var: RCLONE_DRIVE_TEAM_DRIVE
--   Type: string
--   Default: ""
-
-–drive-auth-owner-only
-
-Only consider files owned by the authenticated user.
-
--   Config: auth_owner_only
--   Env Var: RCLONE_DRIVE_AUTH_OWNER_ONLY
--   Type: bool
--   Default: false
-
-–drive-use-trash
-
-Send files to the trash instead of deleting permanently. Defaults to
-true, namely sending files to the trash. Use --drive-use-trash=false to
-delete files permanently instead.
-
--   Config: use_trash
--   Env Var: RCLONE_DRIVE_USE_TRASH
--   Type: bool
--   Default: true
-
-–drive-skip-gdocs
-
-Skip google documents in all listings. If given, gdocs practically
-become invisible to rclone.
-
--   Config: skip_gdocs
--   Env Var: RCLONE_DRIVE_SKIP_GDOCS
--   Type: bool
--   Default: false
-
-–drive-skip-checksum-gphotos
-
-Skip MD5 checksum on Google photos and videos only.
-
-Use this if you get checksum errors when transferring Google photos or
-videos.
-
-Setting this flag will cause Google photos and videos to return a blank
-MD5 checksum.
-
-Google photos are identified by being in the “photos” space.
-
-Corrupted checksums are caused by Google modifying the image/video but
-not updating the checksum.
-
--   Config: skip_checksum_gphotos
--   Env Var: RCLONE_DRIVE_SKIP_CHECKSUM_GPHOTOS
--   Type: bool
--   Default: false
-
-–drive-shared-with-me
-
-Only show files that are shared with me.
-
-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).
-
-This works both with the “list” (lsd, lsl, etc) and the “copy” commands
-(copy, sync, etc), and with all other commands too.
-
--   Config: shared_with_me
--   Env Var: RCLONE_DRIVE_SHARED_WITH_ME
--   Type: bool
--   Default: false
-
-–drive-trashed-only
-
-Only show files that are in the trash. This will show trashed files in
-their original directory structure.
-
--   Config: trashed_only
--   Env Var: RCLONE_DRIVE_TRASHED_ONLY
--   Type: bool
--   Default: false
-
-–drive-formats
-
-Deprecated: see export_formats
-
--   Config: formats
--   Env Var: RCLONE_DRIVE_FORMATS
--   Type: string
--   Default: ""
-
-–drive-export-formats
-
-Comma separated list of preferred formats for downloading Google docs.
-
--   Config: export_formats
--   Env Var: RCLONE_DRIVE_EXPORT_FORMATS
--   Type: string
--   Default: “docx,xlsx,pptx,svg”
-
-–drive-import-formats
-
-Comma separated list of preferred formats for uploading Google docs.
-
--   Config: import_formats
--   Env Var: RCLONE_DRIVE_IMPORT_FORMATS
--   Type: string
--   Default: ""
-
-–drive-allow-import-name-change
-
-Allow the filetype to change when uploading Google docs (e.g. file.doc
-to file.docx). This will confuse sync and reupload every time.
-
--   Config: allow_import_name_change
--   Env Var: RCLONE_DRIVE_ALLOW_IMPORT_NAME_CHANGE
--   Type: bool
--   Default: false
-
-–drive-use-created-date
-
-Use file created date instead of modified date.,
-
-Useful when downloading data and you want the creation date used in
-place of the last modified date.
-
-WARNING: This flag may have some unexpected consequences.
-
-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.
-
-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.
-
--   Config: use_created_date
--   Env Var: RCLONE_DRIVE_USE_CREATED_DATE
--   Type: bool
--   Default: false
-
-–drive-use-shared-date
-
-Use date file was shared instead of modified date.
-
-Note that, as with “–drive-use-created-date”, this flag may have
-unexpected consequences when uploading/downloading files.
-
-If both this flag and “–drive-use-created-date” are set, the created
-date is used.
-
--   Config: use_shared_date
--   Env Var: RCLONE_DRIVE_USE_SHARED_DATE
--   Type: bool
--   Default: false
-
-–drive-list-chunk
-
-Size of listing chunk 100-1000. 0 to disable.
-
--   Config: list_chunk
--   Env Var: RCLONE_DRIVE_LIST_CHUNK
--   Type: int
--   Default: 1000
-
-–drive-impersonate
-
-Impersonate this user when using a service account.
-
--   Config: impersonate
--   Env Var: RCLONE_DRIVE_IMPERSONATE
--   Type: string
--   Default: ""
-
-–drive-alternate-export
-
-Use alternate export URLs for google documents export.,
-
-If this option is set this instructs rclone to use an alternate set of
-export URLs for drive documents. Users have reported that the official
-export URLs can’t export large documents, whereas these unofficial ones
-can.
-
-See rclone issue #2243 for background, this google drive issue and this
-helpful post.
-
--   Config: alternate_export
--   Env Var: RCLONE_DRIVE_ALTERNATE_EXPORT
--   Type: bool
--   Default: false
-
-–drive-upload-cutoff
-
-Cutoff for switching to chunked upload
-
--   Config: upload_cutoff
--   Env Var: RCLONE_DRIVE_UPLOAD_CUTOFF
--   Type: SizeSuffix
--   Default: 8M
-
-–drive-chunk-size
-
-Upload chunk size. Must a power of 2 >= 256k.
-
-Making this larger will improve performance, but note that each chunk is
-buffered in memory one per transfer.
-
-Reducing this will reduce memory usage but decrease performance.
-
--   Config: chunk_size
--   Env Var: RCLONE_DRIVE_CHUNK_SIZE
--   Type: SizeSuffix
--   Default: 8M
-
-–drive-acknowledge-abuse
-
-Set to allow files which return cannotDownloadAbusiveFile to be
-downloaded.
-
-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.
-
--   Config: acknowledge_abuse
--   Env Var: RCLONE_DRIVE_ACKNOWLEDGE_ABUSE
--   Type: bool
--   Default: false
-
-–drive-keep-revision-forever
-
-Keep new head revision of each file forever.
-
--   Config: keep_revision_forever
--   Env Var: RCLONE_DRIVE_KEEP_REVISION_FOREVER
--   Type: bool
--   Default: false
-
-–drive-size-as-quota
-
-Show sizes as storage quota usage, not actual size.
-
-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.
-
-WARNING: This flag may have some unexpected consequences.
-
-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.
-
-If you do use this flag for syncing (not recommended) then you will need
-to use –ignore size also.
-
--   Config: size_as_quota
--   Env Var: RCLONE_DRIVE_SIZE_AS_QUOTA
--   Type: bool
--   Default: false
-
-–drive-v2-download-min-size
-
-If Object’s are greater, use drive v2 API to download.
-
--   Config: v2_download_min_size
--   Env Var: RCLONE_DRIVE_V2_DOWNLOAD_MIN_SIZE
--   Type: SizeSuffix
--   Default: off
-
-–drive-pacer-min-sleep
-
-Minimum time to sleep between API calls.
-
--   Config: pacer_min_sleep
--   Env Var: RCLONE_DRIVE_PACER_MIN_SLEEP
--   Type: Duration
--   Default: 100ms
-
-–drive-pacer-burst
-
-Number of API calls to allow without sleeping.
-
--   Config: pacer_burst
--   Env Var: RCLONE_DRIVE_PACER_BURST
--   Type: int
--   Default: 100
-
-–drive-server-side-across-configs
-
-Allow server side operations (eg copy) to work across different drive
-configs.
-
-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.
-
--   Config: server_side_across_configs
--   Env Var: RCLONE_DRIVE_SERVER_SIDE_ACROSS_CONFIGS
--   Type: bool
--   Default: false
-
-–drive-disable-http2
-
-Disable drive using http2
-
-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.
-
-See: https://github.com/rclone/rclone/issues/3631
-
--   Config: disable_http2
--   Env Var: RCLONE_DRIVE_DISABLE_HTTP2
--   Type: bool
--   Default: true
-
-–drive-stop-on-upload-limit
-
-Make upload limit errors be fatal
-
-At the time of writing it is only possible to upload 750GB 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.
-
-Note that this detection is relying on error message strings which
-Google don’t document so it may break in the future.
-
-See: https://github.com/rclone/rclone/issues/3857
-
--   Config: stop_on_upload_limit
--   Env Var: RCLONE_DRIVE_STOP_ON_UPLOAD_LIMIT
--   Type: bool
--   Default: false
-
-–drive-skip-shortcuts
-
-If set skip shortcut files
-
-Normally rclone dereferences shortcut files making them appear as if
-they are the original file (see the shortcuts section). If this flag is
-set then rclone will ignore shortcut files completely.
-
--   Config: skip_shortcuts
--   Env Var: RCLONE_DRIVE_SKIP_SHORTCUTS
--   Type: bool
--   Default: false
-
-–drive-encoding
-
-This sets the encoding for the backend.
-
-See: the encoding section in the overview for more info.
-
--   Config: encoding
--   Env Var: RCLONE_DRIVE_ENCODING
--   Type: MultiEncoder
--   Default: InvalidUtf8
-
-Backend commands
-
-Here are the commands specific to the drive backend.
-
-Run them with
-
-    rclone backend COMMAND remote:
-
-The help below will explain what arguments each command takes.
-
-See the “rclone backend” command for more info on how to pass options
-and arguments.
-
-These can be run on a running backend using the rc command
-backend/command.
-
-get
-
-Get command for fetching the drive config parameters
-
-    rclone backend get remote: [options] [<arguments>+]
-
-This is a get command which will be used to fetch the various drive
-config parameters
-
-Usage Examples:
-
-    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]
-
-Options:
-
--   “chunk_size”: show the current upload chunk size
--   “service_account_file”: show the current service account file
-
-set
-
-Set command for updating the drive config parameters
-
-    rclone backend set remote: [options] [<arguments>+]
-
-This is a set command which will be used to update the various drive
-config parameters
-
-Usage Examples:
-
-    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]
-
-Options:
-
--   “chunk_size”: update the current upload chunk size
--   “service_account_file”: update the current service account file
-
-shortcut
-
-Create shortcuts from files or directories
-
-    rclone backend shortcut remote: [options] [<arguments>+]
-
-This command creates shortcuts from files or directories.
-
-Usage:
-
-    rclone backend shortcut drive: source_item destination_shortcut
-    rclone backend shortcut drive: source_item -o target=drive2: destination_shortcut
-
-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:”
-
-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:”.
-
-Options:
-
--   “target”: optional target remote for the shortcut destination
-
-Limitations
-
-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 MBytes/s but lots of small files can
-take a long time.
-
-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 --disable copy to download and
-upload the files if you prefer.
-
-Limitations of Google Docs
-
-Google docs will appear as size -1 in rclone ls and as size 0 in
-anything which uses the VFS layer, eg rclone mount, rclone serve.
-
-This is because rclone can’t find out the size of the Google docs
-without downloading them.
-
-Google docs will transfer correctly with rclone sync, rclone copy etc as
-rclone knows to ignore the size when doing the transfer.
-
-However an unfortunate consequence of this is that you may not be able
-to download Google docs using rclone mount. 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!
-
-Duplicated files
-
-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.
-
-Duplicated files cause problems with the syncing and you will see
-messages in the log about duplicates.
-
-Use rclone dedupe to fix duplicated files.
-
-Note that this isn’t just a problem with rclone, even Google Photos on
-Android duplicates files on drive sometimes.
-
-Rclone appears to be re-copying files it shouldn’t
-
-The most likely cause of this is the duplicated file issue above - run
-rclone dedupe and check your logs for duplicate object or directory
-messages.
-
-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.
-
-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.
-
-Making your own client_id
-
-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.
-
-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.
-
-Here is how to create your own Google Drive client ID for rclone:
-
-1.  Log into the Google API Console 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)
-
-2.  Select a project or create a new project.
-
-3.  Under “ENABLE APIS AND SERVICES” search for “Drive”, and enable the
-    “Google Drive API”.
-
-4.  Click “Credentials” in the left-side panel (not “Create
-    credentials”, which opens the wizard), then “Create credentials”
-
-5.  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) then click on “Save” (all other
-    data is optional). Click again on “Credentials” on the left panel to
-    go back to the “Credentials” screen.
-
-(PS: if you are a GSuite user, you could also select “Internal” instead
-of “External” above, but this has not been tested/documented so far).
-
-6.  Click on the “+ CREATE CREDENTIALS” button at the top of the screen,
-    then select “OAuth client ID”.
-
-7.  Choose an application type of “Desktop app” if you using a Google
-    account or “Other” if you using a GSuite account and click “Create”.
-    (the default name is fine)
-
-8.  It will show you a client ID and client secret. Use these values in
-    rclone config to add a new remote or edit an existing remote.
-
-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).
-
-(Thanks to @balazer on github for these instructions.)
-
-
-Google Photos
-
-The rclone backend for Google Photos is a specialized backend for
-transferring photos and videos to and from Google Photos.
-
-NB The Google Photos API which rclone uses has quite a few limitations,
-so please read the limitations section carefully to make sure it is
-suitable for your use.
-
-
-Configuring Google Photos
-
-The initial setup for google cloud storage involves getting a token from
-Google Photos which you need to do in your browser. rclone config walks
-you through it.
-
-Here is an example of how to make a remote called remote. First run:
-
-     rclone config
-
-This will guide you through an interactive setup process:
-
-    No remotes found - make a new one
-    n) New remote
-    s) Set configuration password
-    q) Quit config
-    n/s/q> n
-    name> remote
-    Type of storage to configure.
-    Enter a string value. Press Enter for the default ("").
-    Choose a number from below, or type in your own value
-    [snip]
-    XX / Google Photos
-       \ "google photos"
-    [snip]
-    Storage> google photos
-    ** See help for google photos backend at: https://rclone.org/googlephotos/ **
-
-    Google Application Client Id
+    - Config:      scope
+    - Env Var:     RCLONE_DRIVE_SCOPE
+    - Type:        string
+    - Default:     ""
+    - Examples:
+        - "drive"
+            - Full access all files, excluding Application Data Folder.
+        - "drive.readonly"
+            - Read-only access to file metadata and file contents.
+        - "drive.file"
+            - Access to files created by rclone only.
+            - These are visible in the drive website.
+            - File authorization is revoked when the user deauthorizes the app.
+        - "drive.appfolder"
+            - Allows read and write access to the Application Data folder.
+            - This is not visible in the drive website.
+        - "drive.metadata.readonly"
+            - Allows read-only access to file metadata but
+            - does not allow any access to read or download file content.
+
+    #### --drive-root-folder-id
+
+    ID of the root folder
     Leave blank normally.
-    Enter a string value. Press Enter for the default ("").
-    client_id> 
-    Google Application Client Secret
+
+    Fill in to access "Computers" folders (see docs), or for rclone to use
+    a non root folder as its starting point.
+
+
+    - Config:      root_folder_id
+    - Env Var:     RCLONE_DRIVE_ROOT_FOLDER_ID
+    - Type:        string
+    - Default:     ""
+
+    #### --drive-service-account-file
+
+    Service Account Credentials JSON file path 
     Leave blank normally.
-    Enter a string value. Press Enter for the default ("").
-    client_secret> 
-    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 ("false").
-    read_only> 
-    Edit advanced config? (y/n)
-    y) Yes
-    n) No
-    y/n> n
-    Remote config
-    Use auto config?
-     * Say Y if not sure
-     * Say N if you are working on a remote or headless machine
-    y) Yes
-    n) No
-    y/n> y
-    If your browser doesn'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.
-
-    --------------------
-    [remote]
-    type = google photos
-    token = {"access_token":"XXX","token_type":"Bearer","refresh_token":"XXX","expiry":"2019-06-28T17:38:04.644930156+01:00"}
-    --------------------
-    y) Yes this is OK
-    e) Edit this remote
-    d) Delete this remote
-    y/e/d> y
-
-Note that rclone runs a webserver on your local machine to collect the
-token as returned from Google if you use auto config mode. This only
-runs from the moment it opens your browser to the moment you get back
-the verification code. This is on http://127.0.0.1:53682/ and this may
-require you to unblock it temporarily if you are running a host
-firewall, or use manual mode.
-
-This remote is called remote and can now be used like this
-
-See all the albums in your photos
-
-    rclone lsd remote:album
-
-Make a new album
-
-    rclone mkdir remote:album/newAlbum
-
-List the contents of an album
-
-    rclone ls remote:album/newAlbum
-
-Sync /home/local/images to the Google Photos, removing any excess files
-in the album.
-
-    rclone sync /home/local/image remote:album/newAlbum
-
-
-Layout
-
-As Google Photos is not a general purpose cloud storage system the
-backend is laid out to help you navigate it.
-
-The directories under media 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
-remote:media/by-month. (NB remote:media/by-day is rather slow at the
-moment so avoid for syncing.)
-
-Note that all your photos and videos will appear somewhere under media,
-but they may not appear under album unless you’ve put them into albums.
-
-    /
-    - 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
-
-There are two writable parts of the tree, the upload directory and sub
-directories of the album directory.
-
-The upload 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 album will work better.
-
-Directories within the album directory are also writeable and you may
-create new directories (albums) under album. If you copy files with a
-directory hierarchy in there then rclone will create albums with the /
-character in them. For example if you do
-
-    rclone copy /path/to/images remote:album/images
-
-and the images directory contains
-
-    images
-        - file1.jpg
-        dir
-            file2.jpg
-        dir2
-            dir3
-                file3.jpg
-
-Then rclone will create the following albums with the following files in
-
--   images
-    -   file1.jpg
--   images/dir
-    -   file2.jpg
--   images/dir2/dir3
-    -   file3.jpg
-
-This means that you can use the album path pretty much like a normal
-filesystem and it is a good target for repeated syncing.
-
-The shared-album directory shows albums shared with you or by you. This
-is similar to the Sharing tab in the Google Photos web interface.
-
-
-Limitations
-
-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.
-
-Note that all media items uploaded to Google Photos through the API are
-stored in full resolution at “original quality” and WILL count towards
-your storage quota in your Google Account. The API does NOT offer a way
-to upload in “high quality” mode..
-
-Downloading Images
-
-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 bug #112096115.
-
-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
-
-Downloading Videos
+    Needed only if you want use SA instead of interactive login.
 
-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 bug #113672044.
+    Leading `~` will be expanded in the file name as will environment variables such as `${RCLONE_CONFIG_DIR}`.
 
-Duplicates
 
-If a file name is duplicated in a directory then rclone will add the
-file ID into its name. So two files called file.jpg would then appear as
-file {123456}.jpg and file {ABCDEF}.jpg (the actual IDs are a lot longer
-alas!).
+    - Config:      service_account_file
+    - Env Var:     RCLONE_DRIVE_SERVICE_ACCOUNT_FILE
+    - Type:        string
+    - Default:     ""
 
-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 upload then uploaded the same image to
-album/my_album the filename of the image in album/my_album will be what
-it was uploaded with initially, not what you uploaded it with to album.
-In practise this shouldn’t cause too many problems.
+    #### --drive-alternate-export
 
-Modified time
+    Deprecated: no longer needed
 
-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.
+    - Config:      alternate_export
+    - Env Var:     RCLONE_DRIVE_ALTERNATE_EXPORT
+    - Type:        bool
+    - Default:     false
 
-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.
+    ### Advanced Options
 
-Size
+    Here are the advanced options specific to drive (Google Drive).
 
-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.
+    #### --drive-token
 
-It is possible to read the size of the media, but this needs an extra
-HTTP HEAD request per media item so is VERY SLOW and uses up a lot of
-transactions. This can be enabled with the --gphotos-read-size option or
-the read_size = true config parameter.
+    OAuth Access Token as a JSON blob.
 
-If you want to use the backend with rclone mount 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.
+    - Config:      token
+    - Env Var:     RCLONE_DRIVE_TOKEN
+    - Type:        string
+    - Default:     ""
 
-Albums
+    #### --drive-auth-url
 
-Rclone can only upload files to albums it created. This is a limitation
-of the Google Photos API.
+    Auth server URL.
+    Leave blank to use the provider defaults.
 
-Rclone can remove files it uploaded from albums it created only.
+    - Config:      auth_url
+    - Env Var:     RCLONE_DRIVE_AUTH_URL
+    - Type:        string
+    - Default:     ""
 
-Deleting files
+    #### --drive-token-url
 
-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 bug #109759781.
+    Token server url.
+    Leave blank to use the provider defaults.
 
-Rclone cannot delete files anywhere except under album.
+    - Config:      token_url
+    - Env Var:     RCLONE_DRIVE_TOKEN_URL
+    - Type:        string
+    - Default:     ""
 
-Deleting albums
+    #### --drive-service-account-credentials
 
-The Google Photos API does not support deleting albums - see bug
-#135714733.
+    Service Account Credentials JSON blob
+    Leave blank normally.
+    Needed only if you want use SA instead of interactive login.
 
-Standard Options
+    - Config:      service_account_credentials
+    - Env Var:     RCLONE_DRIVE_SERVICE_ACCOUNT_CREDENTIALS
+    - Type:        string
+    - Default:     ""
 
-Here are the standard options specific to google photos (Google Photos).
+    #### --drive-team-drive
 
-–gphotos-client-id
+    ID of the Team Drive
 
-Google Application Client Id Leave blank normally.
+    - Config:      team_drive
+    - Env Var:     RCLONE_DRIVE_TEAM_DRIVE
+    - Type:        string
+    - Default:     ""
 
--   Config: client_id
--   Env Var: RCLONE_GPHOTOS_CLIENT_ID
--   Type: string
--   Default: ""
+    #### --drive-auth-owner-only
 
-–gphotos-client-secret
+    Only consider files owned by the authenticated user.
 
-Google Application Client Secret Leave blank normally.
+    - Config:      auth_owner_only
+    - Env Var:     RCLONE_DRIVE_AUTH_OWNER_ONLY
+    - Type:        bool
+    - Default:     false
 
--   Config: client_secret
--   Env Var: RCLONE_GPHOTOS_CLIENT_SECRET
--   Type: string
--   Default: ""
+    #### --drive-use-trash
 
-–gphotos-read-only
+    Send files to the trash instead of deleting permanently.
+    Defaults to true, namely sending files to the trash.
+    Use `--drive-use-trash=false` to delete files permanently instead.
 
-Set to make the Google Photos backend read only.
+    - Config:      use_trash
+    - Env Var:     RCLONE_DRIVE_USE_TRASH
+    - Type:        bool
+    - Default:     true
+
+    #### --drive-skip-gdocs
+
+    Skip google documents in all listings.
+    If given, gdocs practically become invisible to rclone.
+
+    - Config:      skip_gdocs
+    - Env Var:     RCLONE_DRIVE_SKIP_GDOCS
+    - Type:        bool
+    - Default:     false
+
+    #### --drive-skip-checksum-gphotos
+
+    Skip MD5 checksum on Google photos and videos only.
+
+    Use this if you get checksum errors when transferring Google photos or
+    videos.
+
+    Setting this flag will cause Google photos and videos to return a
+    blank MD5 checksum.
+
+    Google photos are identified by being in the "photos" space.
+
+    Corrupted checksums are caused by Google modifying the image/video but
+    not updating the checksum.
+
+    - Config:      skip_checksum_gphotos
+    - Env Var:     RCLONE_DRIVE_SKIP_CHECKSUM_GPHOTOS
+    - Type:        bool
+    - Default:     false
+
+    #### --drive-shared-with-me
+
+    Only show files that are shared with me.
+
+    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).
+
+    This works both with the "list" (lsd, lsl, etc) and the "copy"
+    commands (copy, sync, etc), and with all other commands too.
+
+    - Config:      shared_with_me
+    - Env Var:     RCLONE_DRIVE_SHARED_WITH_ME
+    - Type:        bool
+    - Default:     false
+
+    #### --drive-trashed-only
+
+    Only show files that are in the trash.
+    This will show trashed files in their original directory structure.
+
+    - Config:      trashed_only
+    - Env Var:     RCLONE_DRIVE_TRASHED_ONLY
+    - Type:        bool
+    - Default:     false
+
+    #### --drive-starred-only
+
+    Only show files that are starred.
+
+    - Config:      starred_only
+    - Env Var:     RCLONE_DRIVE_STARRED_ONLY
+    - Type:        bool
+    - Default:     false
+
+    #### --drive-formats
+
+    Deprecated: see export_formats
+
+    - Config:      formats
+    - Env Var:     RCLONE_DRIVE_FORMATS
+    - Type:        string
+    - Default:     ""
+
+    #### --drive-export-formats
+
+    Comma separated list of preferred formats for downloading Google docs.
+
+    - Config:      export_formats
+    - Env Var:     RCLONE_DRIVE_EXPORT_FORMATS
+    - Type:        string
+    - Default:     "docx,xlsx,pptx,svg"
+
+    #### --drive-import-formats
+
+    Comma separated list of preferred formats for uploading Google docs.
+
+    - Config:      import_formats
+    - Env Var:     RCLONE_DRIVE_IMPORT_FORMATS
+    - Type:        string
+    - Default:     ""
+
+    #### --drive-allow-import-name-change
+
+    Allow the filetype to change when uploading Google docs (e.g. file.doc to file.docx). This will confuse sync and reupload every time.
+
+    - Config:      allow_import_name_change
+    - Env Var:     RCLONE_DRIVE_ALLOW_IMPORT_NAME_CHANGE
+    - Type:        bool
+    - Default:     false
+
+    #### --drive-use-created-date
+
+    Use file created date instead of modified date.,
+
+    Useful when downloading data and you want the creation date used in
+    place of the last modified date.
+
+    **WARNING**: This flag may have some unexpected consequences.
+
+    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.
+
+    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.
+
+    - Config:      use_created_date
+    - Env Var:     RCLONE_DRIVE_USE_CREATED_DATE
+    - Type:        bool
+    - Default:     false
+
+    #### --drive-use-shared-date
+
+    Use date file was shared instead of modified date.
+
+    Note that, as with "--drive-use-created-date", this flag may have
+    unexpected consequences when uploading/downloading files.
+
+    If both this flag and "--drive-use-created-date" are set, the created
+    date is used.
+
+    - Config:      use_shared_date
+    - Env Var:     RCLONE_DRIVE_USE_SHARED_DATE
+    - Type:        bool
+    - Default:     false
+
+    #### --drive-list-chunk
+
+    Size of listing chunk 100-1000. 0 to disable.
+
+    - Config:      list_chunk
+    - Env Var:     RCLONE_DRIVE_LIST_CHUNK
+    - Type:        int
+    - Default:     1000
+
+    #### --drive-impersonate
+
+    Impersonate this user when using a service account.
+
+    - Config:      impersonate
+    - Env Var:     RCLONE_DRIVE_IMPERSONATE
+    - Type:        string
+    - Default:     ""
+
+    #### --drive-upload-cutoff
+
+    Cutoff for switching to chunked upload
+
+    - Config:      upload_cutoff
+    - Env Var:     RCLONE_DRIVE_UPLOAD_CUTOFF
+    - Type:        SizeSuffix
+    - Default:     8M
+
+    #### --drive-chunk-size
+
+    Upload chunk size. Must a power of 2 >= 256k.
+
+    Making this larger will improve performance, but note that each chunk
+    is buffered in memory one per transfer.
+
+    Reducing this will reduce memory usage but decrease performance.
+
+    - Config:      chunk_size
+    - Env Var:     RCLONE_DRIVE_CHUNK_SIZE
+    - Type:        SizeSuffix
+    - Default:     8M
+
+    #### --drive-acknowledge-abuse
+
+    Set to allow files which return cannotDownloadAbusiveFile to be downloaded.
+
+    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.
+
+    - Config:      acknowledge_abuse
+    - Env Var:     RCLONE_DRIVE_ACKNOWLEDGE_ABUSE
+    - Type:        bool
+    - Default:     false
+
+    #### --drive-keep-revision-forever
+
+    Keep new head revision of each file forever.
+
+    - Config:      keep_revision_forever
+    - Env Var:     RCLONE_DRIVE_KEEP_REVISION_FOREVER
+    - Type:        bool
+    - Default:     false
+
+    #### --drive-size-as-quota
+
+    Show sizes as storage quota usage, not actual size.
+
+    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.
+
+    **WARNING**: This flag may have some unexpected consequences.
+
+    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.
+
+    If you do use this flag for syncing (not recommended) then you will
+    need to use --ignore size also.
+
+    - Config:      size_as_quota
+    - Env Var:     RCLONE_DRIVE_SIZE_AS_QUOTA
+    - Type:        bool
+    - Default:     false
+
+    #### --drive-v2-download-min-size
+
+    If Object's are greater, use drive v2 API to download.
+
+    - Config:      v2_download_min_size
+    - Env Var:     RCLONE_DRIVE_V2_DOWNLOAD_MIN_SIZE
+    - Type:        SizeSuffix
+    - Default:     off
+
+    #### --drive-pacer-min-sleep
+
+    Minimum time to sleep between API calls.
+
+    - Config:      pacer_min_sleep
+    - Env Var:     RCLONE_DRIVE_PACER_MIN_SLEEP
+    - Type:        Duration
+    - Default:     100ms
+
+    #### --drive-pacer-burst
+
+    Number of API calls to allow without sleeping.
+
+    - Config:      pacer_burst
+    - Env Var:     RCLONE_DRIVE_PACER_BURST
+    - Type:        int
+    - Default:     100
+
+    #### --drive-server-side-across-configs
+
+    Allow server side operations (eg copy) to work across different drive configs.
+
+    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.
+
+    - Config:      server_side_across_configs
+    - Env Var:     RCLONE_DRIVE_SERVER_SIDE_ACROSS_CONFIGS
+    - Type:        bool
+    - Default:     false
+
+    #### --drive-disable-http2
+
+    Disable drive using http2
+
+    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.
+
+    See: https://github.com/rclone/rclone/issues/3631
+
+
+
+    - Config:      disable_http2
+    - Env Var:     RCLONE_DRIVE_DISABLE_HTTP2
+    - Type:        bool
+    - Default:     true
+
+    #### --drive-stop-on-upload-limit
+
+    Make upload limit errors be fatal
+
+    At the time of writing it is only possible to upload 750GB 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.
+
+    Note that this detection is relying on error message strings which
+    Google don't document so it may break in the future.
+
+    See: https://github.com/rclone/rclone/issues/3857
+
+
+    - Config:      stop_on_upload_limit
+    - Env Var:     RCLONE_DRIVE_STOP_ON_UPLOAD_LIMIT
+    - Type:        bool
+    - Default:     false
+
+    #### --drive-skip-shortcuts
+
+    If set skip shortcut files
+
+    Normally rclone dereferences shortcut files making them appear as if
+    they are the original file (see [the shortcuts section](#shortcuts)).
+    If this flag is set then rclone will ignore shortcut files completely.
+
+
+    - Config:      skip_shortcuts
+    - Env Var:     RCLONE_DRIVE_SKIP_SHORTCUTS
+    - Type:        bool
+    - Default:     false
+
+    #### --drive-encoding
+
+    This sets the encoding for the backend.
+
+    See: the [encoding section in the overview](https://rclone.org/overview/#encoding) for more info.
+
+    - Config:      encoding
+    - Env Var:     RCLONE_DRIVE_ENCODING
+    - Type:        MultiEncoder
+    - Default:     InvalidUtf8
+
+    ### Backend commands
+
+    Here are the commands specific to the drive backend.
+
+    Run them with
+
+        rclone backend COMMAND remote:
+
+    The help below will explain what arguments each command takes.
+
+    See [the "rclone backend" command](https://rclone.org/commands/rclone_backend/) for more
+    info on how to pass options and arguments.
+
+    These can be run on a running backend using the rc command
+    [backend/command](https://rclone.org/rc/#backend/command).
+
+    #### get
+
+    Get command for fetching the drive config parameters
+
+        rclone backend get remote: [options] [<arguments>+]
+
+    This is a get command which will be used to fetch the various drive config parameters
+
+    Usage Examples:
+
+        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]
+
+
+    Options:
+
+    - "chunk_size": show the current upload chunk size
+    - "service_account_file": show the current service account file
+
+    #### set
+
+    Set command for updating the drive config parameters
+
+        rclone backend set remote: [options] [<arguments>+]
+
+    This is a set command which will be used to update the various drive config parameters
+
+    Usage Examples:
+
+        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]
+
+
+    Options:
+
+    - "chunk_size": update the current upload chunk size
+    - "service_account_file": update the current service account file
+
+    #### shortcut
+
+    Create shortcuts from files or directories
+
+        rclone backend shortcut remote: [options] [<arguments>+]
+
+    This command creates shortcuts from files or directories.
+
+    Usage:
+
+        rclone backend shortcut drive: source_item destination_shortcut
+        rclone backend shortcut drive: source_item -o target=drive2: destination_shortcut
+
+    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:"
+
+    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:".
+
+
+    Options:
+
+    - "target": optional target remote for the shortcut destination
+
+    #### drives
+
+    List the shared drives available to this account
+
+        rclone backend drives remote: [options] [<arguments>+]
+
+    This command lists the shared drives (teamdrives) available to this
+    account.
+
+    Usage:
+
+        rclone backend drives drive:
+
+    This will return a JSON list of objects like this
+
+        [
+            {
+                "id": "0ABCDEF-01234567890",
+                "kind": "drive#teamDrive",
+                "name": "My Drive"
+            },
+            {
+                "id": "0ABCDEFabcdefghijkl",
+                "kind": "drive#teamDrive",
+                "name": "Test Drive"
+            }
+        ]
+
+
+
+    #### untrash
+
+    Untrash files and directories
+
+        rclone backend untrash remote: [options] [<arguments>+]
+
+    This command untrashes all the files and directories in the directory
+    passed in recursively.
+
+    Usage:
+
+    This takes an optional directory to trash which make this easier to
+    use via the API.
+
+        rclone backend untrash drive:directory
+        rclone backend -i untrash drive:directory subdir
+
+    Use the -i flag to see what would be restored before restoring it.
+
+    Result:
+
+        {
+            "Untrashed": 17,
+            "Errors": 0
+        }
+
+
+
+
+    ### Limitations ###
+
+    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 MBytes/s but lots of
+    small files can take a long time.
+
+    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 `--disable copy` to download
+    and upload the files if you prefer.
+
+    #### Limitations of Google Docs ####
+
+    Google docs will appear as size -1 in `rclone ls` and as size 0 in
+    anything which uses the VFS layer, eg `rclone mount`, `rclone serve`.
+
+    This is because rclone can't find out the size of the Google docs
+    without downloading them.
+
+    Google docs will transfer correctly with `rclone sync`, `rclone copy`
+    etc as rclone knows to ignore the size when doing the transfer.
+
+    However an unfortunate consequence of this is that you may not be able
+    to download Google docs using `rclone mount`. 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!
+
+    ### Duplicated files ###
+
+    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.
+
+    Duplicated files cause problems with the syncing and you will see
+    messages in the log about duplicates.
+
+    Use `rclone dedupe` to fix duplicated files.
+
+    Note that this isn't just a problem with rclone, even Google Photos on
+    Android duplicates files on drive sometimes.
+
+    ### Rclone appears to be re-copying files it shouldn't ###
+
+    The most likely cause of this is the duplicated file issue above - run
+    `rclone dedupe` and check your logs for duplicate object or directory
+    messages.
+
+    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.
+
+    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.
+
+    ### Making your own client_id ###
+
+    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.
+
+    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.
+
+    Here is how to create your own Google Drive client ID for rclone:
+
+    1. Log into the [Google API
+    Console](https://console.developers.google.com/) 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)
+
+    2. Select a project or create a new project.
+
+    3. Under "ENABLE APIS AND SERVICES" search for "Drive", and enable the
+    "Google Drive API".
+
+    4. Click "Credentials" in the left-side panel (not "Create
+    credentials", which opens the wizard), then "Create credentials"
+
+    5. 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) then click on "Save" (all other data is optional). 
+    Click again on "Credentials" on the left panel to go back to the 
+    "Credentials" screen.
+
+    (PS: if you are a GSuite user, you could also select "Internal" instead
+    of "External" above, but this has not been tested/documented so far). 
+
+    6.  Click on the "+ CREATE CREDENTIALS" button at the top of the screen,
+    then select "OAuth client ID".
+
+    7. Choose an application type of "Desktop app" if you using a Google account or "Other" if 
+    you using a GSuite account and click "Create". (the default name is fine)
+
+    8. It will show you a client ID and client secret.  Use these values
+    in rclone config to add a new remote or edit an existing remote.
+
+    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). 
+
+    (Thanks to @balazer on github for these instructions.)
+
+    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
+    [Python Quickstart](https://developers.google.com/drive/api/v3/quickstart/python) 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.
+
+     Google Photos
+    -------------------------------------------------
+
+    The rclone backend for [Google Photos](https://www.google.com/photos/about/) is
+    a specialized backend for transferring photos and videos to and from
+    Google Photos.
+
+    **NB** The Google Photos API which rclone uses has quite a few
+    limitations, so please read the [limitations section](#limitations)
+    carefully to make sure it is suitable for your use.
+
+    ## Configuring Google Photos
+
+    The initial setup for google cloud storage involves getting a token from Google Photos
+    which you need to do in your browser.  `rclone config` walks you
+    through it.
+
+    Here is an example of how to make a remote called `remote`.  First run:
+
+         rclone config
+
+    This will guide you through an interactive setup process:
+
+No remotes found - make a new one n) New remote s) Set configuration
+password q) Quit config n/s/q> n name> remote Type of storage to
+configure. Enter a string value. Press Enter for the default ("").
+Choose a number from below, or type in your own value [snip] XX / Google
+Photos  "google photos" [snip] Storage> 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 (""). client_id> Google Application Client
+Secret Leave blank normally. Enter a string value. Press Enter for the
+default (""). client_secret> 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.
+to your photos, otherwise rclone will request full access. Enter a
+boolean value (true or false). Press Enter for the default ("false").
+read_only> Edit advanced config? (y/n) y) Yes n) No y/n> n Remote config
+Use auto config? * Say Y if not sure * Say N if you are working on a
+remote or headless machine y) Yes n) No y/n> y If your browser doesn'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
 
--   Config: read_only
--   Env Var: RCLONE_GPHOTOS_READ_ONLY
--   Type: bool
--   Default: false
+*** 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.
 
-Advanced Options
+  -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
+  [remote] type = google photos token = {"access_token":"XXX","token_type":"Bearer","refresh_token":"XXX","expiry":"2019-06-28T17:38:04.644930156+01:00"}
+  -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
+  y) Yes this is OK e) Edit this remote d) Delete this remote y/e/d> y ```
 
-Here are the advanced options specific to google photos (Google Photos).
+  Note that rclone runs a webserver on your local machine to collect the token as returned from Google if you use auto config mode. This only runs from the moment it opens your browser to the moment you get back the verification code. This is on http://127.0.0.1:53682/ and this may require you to unblock it temporarily if you are running a host firewall, or use manual mode.
 
-–gphotos-read-size
+  This remote is called remote and can now be used like this
 
-Set to read the size of media items.
+  See all the albums in your photos
 
-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.
+  rclone lsd remote:album
 
--   Config: read_size
--   Env Var: RCLONE_GPHOTOS_READ_SIZE
--   Type: bool
--   Default: false
+  Make a new album
 
-–gphotos-start-year
+  rclone mkdir remote:album/newAlbum
 
-Year limits the photos to be downloaded to those which are uploaded
-after the given year
+  List the contents of an album
 
--   Config: start_year
--   Env Var: RCLONE_GPHOTOS_START_YEAR
--   Type: int
--   Default: 2000
+  rclone ls remote:album/newAlbum
 
+  Sync /home/local/images to the Google Photos, removing any excess files in the album.
 
-HTTP
+  rclone sync -i /home/local/image remote:album/newAlbum
+
+  ## Layout
+
+  As Google Photos is not a general purpose cloud storage system the backend is laid out to help you navigate it.
+
+  The directories under media 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 remote:media/by-month. (NB remote:media/by-day is rather slow at the moment so avoid for syncing.)
+
+  Note that all your photos and videos will appear somewhere under media, but they may not appear under album unless you've put them into albums.
+
+  / - 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
+
+  There are two writable parts of the tree, the upload directory and sub directories of the album directory.
+
+  The upload 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 album will work better.
+
+  Directories within the album directory are also writeable and you may create new directories (albums) under album. If you copy files with a directory hierarchy in there then rclone will create albums with the / character in them. For example if you do
+
+  rclone copy /path/to/images remote:album/images
+
+  and the images directory contains
+
+  images - file1.jpg dir file2.jpg dir2 dir3 file3.jpg
+
+  Then rclone will create the following albums with the following files in
+
+  - images - file1.jpg - images/dir - file2.jpg - images/dir2/dir3 - file3.jpg
+
+  This means that you can use the album path pretty much like a normal filesystem and it is a good target for repeated syncing.
+
+  The shared-album directory shows albums shared with you or by you. This is similar to the Sharing tab in the Google Photos web interface.
+
+  ## Limitations
+
+  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.
+
+  Note that all media items uploaded to Google Photos through the API are stored in full resolution at "original quality" and WILL count towards your storage quota in your Google Account. The API does NOT offer a way to upload in "high quality" mode..
+
+  ### Downloading Images
+
+  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 bug #112096115.
+
+  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
+
+  ### Downloading Videos
+
+  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 bug #113672044.
+
+  ### Duplicates
+
+  If a file name is duplicated in a directory then rclone will add the file ID into its name. So two files called file.jpg would then appear as file {123456}.jpg and file {ABCDEF}.jpg (the actual IDs are a lot longer alas!).
+
+  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 upload then uploaded the same image to album/my_album the filename of the image in album/my_album will be what it was uploaded with initially, not what you uploaded it with to album. In practise this shouldn't cause
+  too many problems.
+
+  ### Modified time
+
+  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.
+
+  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.
+
+  ### Size
+
+  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.
+
+  It is possible to read the size of the media, but this needs an extra HTTP HEAD request per media item so is VERY SLOW and uses up a lot of transactions. This can be enabled with the --gphotos-read-size option or the read_size = true config parameter.
+
+  If you want to use the backend with rclone mount 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.
+
+  ### Albums
+
+  Rclone can only upload files to albums it created. This is a limitation of the Google Photos API.
+
+  Rclone can remove files it uploaded from albums it created only.
+
+  ### Deleting files
+
+  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 bug #109759781.
+
+  Rclone cannot delete files anywhere except under album.
+
+  ### Deleting albums
+
+  The Google Photos API does not support deleting albums - see bug #135714733.
+
+  ### Standard Options
+
+  Here are the standard options specific to google photos (Google Photos).
+
+  #### --gphotos-client-id
+
+  OAuth Client Id Leave blank normally.
+
+  - Config: client_id - Env Var: RCLONE_GPHOTOS_CLIENT_ID - Type: string - Default: ""
+
+  #### --gphotos-client-secret
+
+  OAuth Client Secret Leave blank normally.
+
+  - Config: client_secret - Env Var: RCLONE_GPHOTOS_CLIENT_SECRET - Type: string - Default: ""
+
+  #### --gphotos-read-only
+
+  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.
+
+  - Config: read_only - Env Var: RCLONE_GPHOTOS_READ_ONLY - Type: bool - Default: false
+
+  ### Advanced Options
+
+  Here are the advanced options specific to google photos (Google Photos).
+
+  #### --gphotos-token
+
+  OAuth Access Token as a JSON blob.
+
+  - Config: token - Env Var: RCLONE_GPHOTOS_TOKEN - Type: string - Default: ""
+
+  #### --gphotos-auth-url
+
+  Auth server URL. Leave blank to use the provider defaults.
+
+  - Config: auth_url - Env Var: RCLONE_GPHOTOS_AUTH_URL - Type: string - Default: ""
+
+  #### --gphotos-token-url
+
+  Token server url. Leave blank to use the provider defaults.
+
+  - Config: token_url - Env Var: RCLONE_GPHOTOS_TOKEN_URL - Type: string - Default: ""
+
+  #### --gphotos-read-size
+
+  Set to read the size of media items.
+
+  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.
+
+  - Config: read_size - Env Var: RCLONE_GPHOTOS_READ_SIZE - Type: bool - Default: false
+
+  #### --gphotos-start-year
+
+  Year limits the photos to be downloaded to those which are uploaded after the given year
+
+  - Config: start_year - Env Var: RCLONE_GPHOTOS_START_YEAR - Type: int - Default: 2000
+
+  HTTP
+  -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
 
 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
+servers. (If it doesn't then please file an issue, or send a pull
 request!)
 
 Paths are specified as remote: or remote:path/to/dir.
@@ -17661,11 +18267,11 @@ List the contents of a directory
 Sync the remote directory to /home/local/directory, deleting any excess
 files.
 
-    rclone sync remote:directory /home/local/directory
+    rclone sync -i remote:directory /home/local/directory
 
 Read only
 
-This remote is read only - you can’t upload files to an HTTP server.
+This remote is read only - you can't upload files to an HTTP server.
 
 Modified time
 
@@ -17686,7 +18292,7 @@ Standard Options
 
 Here are the standard options specific to http (http Connection).
 
-–http-url
+--http-url
 
 URL of http host to connect to
 
@@ -17695,16 +18301,16 @@ URL of http host to connect to
 -   Type: string
 -   Default: ""
 -   Examples:
-    -   “https://example.com”
+    -   "https://example.com"
         -   Connect to example.com
-    -   “https://user:pass@example.com”
+    -   "https://user:pass@example.com"
         -   Connect to example.com using a username and password
 
 Advanced Options
 
 Here are the advanced options specific to http (http Connection).
 
-–http-headers
+--http-headers
 
 Set HTTP headers for all transactions
 
@@ -17713,20 +18319,20 @@ Use this to set additional HTTP headers for all transactions
 The input format is comma separated list of key,value pairs. Standard
 CSV encoding may be used.
 
-For example to set a Cookie use ‘Cookie,name=value’, or
-‘“Cookie”,“name=value”’.
+For example to set a Cookie use 'Cookie,name=value', or
+'"Cookie","name=value"'.
 
 You can set multiple headers, eg
-‘“Cookie”,“name=value”,“Authorization”,“xxx”’.
+'"Cookie","name=value","Authorization","xxx"'.
 
 -   Config: headers
 -   Env Var: RCLONE_HTTP_HEADERS
 -   Type: CommaSepList
 -   Default:
 
-–http-no-slash
+--http-no-slash
 
-Set this if the site doesn’t end directories with /
+Set this if the site doesn't end directories with /
 
 Use this if your target website does not use / on the end of
 directories.
@@ -17744,9 +18350,9 @@ directories.
 -   Type: bool
 -   Default: false
 
-–http-no-head
+--http-no-head
 
-Don’t use HEAD requests to find file sizes in dir listing
+Don't use HEAD requests 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
@@ -17760,8 +18366,8 @@ If you set this option, rclone will not do the HEAD request. This will
 mean
 
 -   directory listings are much quicker
--   rclone won’t have the times or sizes of any files
--   some files that don’t exist may be in the listing
+-   rclone won't have the times or sizes of any files
+-   some files that don't exist may be in the listing
 
 -   Config: no_head
 -   Env Var: RCLONE_HTTP_NO_HEAD
@@ -17851,7 +18457,7 @@ you need to copy your files to the default directory
 
     rclone copy /home/source remote:default/backup
 
-–fast-list
+--fast-list
 
 This remote supports --fast-list which allows you to use fewer
 transactions in exchange for more memory. See the rclone docs for more
@@ -17872,18 +18478,18 @@ Standard Options
 
 Here are the standard options specific to hubic (Hubic).
 
-–hubic-client-id
+--hubic-client-id
 
-Hubic Client Id Leave blank normally.
+OAuth Client Id Leave blank normally.
 
 -   Config: client_id
 -   Env Var: RCLONE_HUBIC_CLIENT_ID
 -   Type: string
 -   Default: ""
 
-–hubic-client-secret
+--hubic-client-secret
 
-Hubic Client Secret Leave blank normally.
+OAuth Client Secret Leave blank normally.
 
 -   Config: client_secret
 -   Env Var: RCLONE_HUBIC_CLIENT_SECRET
@@ -17894,7 +18500,34 @@ Advanced Options
 
 Here are the advanced options specific to hubic (Hubic).
 
-–hubic-chunk-size
+--hubic-token
+
+OAuth Access Token as a JSON blob.
+
+-   Config: token
+-   Env Var: RCLONE_HUBIC_TOKEN
+-   Type: string
+-   Default: ""
+
+--hubic-auth-url
+
+Auth server URL. Leave blank to use the provider defaults.
+
+-   Config: auth_url
+-   Env Var: RCLONE_HUBIC_AUTH_URL
+-   Type: string
+-   Default: ""
+
+--hubic-token-url
+
+Token server url. Leave blank to use the provider defaults.
+
+-   Config: token_url
+-   Env Var: RCLONE_HUBIC_TOKEN_URL
+-   Type: string
+-   Default: ""
+
+--hubic-chunk-size
 
 Above this size files will be chunked into a _segments container.
 
@@ -17906,9 +18539,9 @@ default for this is 5GB which is its maximum value.
 -   Type: SizeSuffix
 -   Default: 5G
 
-–hubic-no-chunk
+--hubic-no-chunk
 
-Don’t chunk files during streaming upload.
+Don't chunk files during streaming upload.
 
 When doing streaming uploads (eg using rcat or mount) setting this flag
 will cause the swift backend to not upload chunked files.
@@ -17924,7 +18557,7 @@ copy operations.
 -   Type: bool
 -   Default: false
 
-–hubic-encoding
+--hubic-encoding
 
 This sets the encoding for the backend.
 
@@ -17940,8 +18573,8 @@ Limitations
 This uses the normal OpenStack Swift mechanism to refresh the Swift API
 credentials and ignores the expires field returned by the Hubic API.
 
-The Swift API doesn’t return a correct MD5SUM for segmented files
-(Dynamic or Static Large Objects) so rclone won’t check or use the
+The Swift API doesn't return a correct MD5SUM for segmented files
+(Dynamic or Static Large Objects) so rclone won't check or use the
 MD5SUM for these.
 
 
@@ -17960,13 +18593,24 @@ Paths may be as deep as required, eg remote:directory/subdirectory.
 
 Setup
 
+Default Setup
+
 To configure Jottacloud you will need to generate a personal security
 token in the Jottacloud web interface. You will the option to do in your
 account security settings (for whitelabel version you need to find this
 page in its web interface). Note that the web interface may refer to
 this token as a JottaCli token.
 
-Here is an example of how to make a remote called remote. First run:
+Legacy Setup
+
+If you are using one of the whitelabel versions (Elgiganten, Com Hem
+Cloud) you may not have the option to generate a CLI token. In this case
+you'll have to use the legacy authentification. To to this select yes
+when the setup asks for legacy authentification and enter your username
+and password. The rest of the setup is identical to the default setup.
+
+Here is an example of how to make a remote called remote with the
+default setup. First run:
 
     rclone config
 
@@ -17977,7 +18621,7 @@ This will guide you through an interactive setup process:
     s) Set configuration password
     q) Quit config
     n/s/q> n
-    name> jotta
+    name> remote
     Type of storage to configure.
     Enter a string value. Press Enter for the default ("").
     Choose a number from below, or type in your own value
@@ -17993,6 +18637,11 @@ This will guide you through an interactive setup process:
     n) No
     y/n> n
     Remote config
+    Use legacy authentification?.
+    This is only required for certain whitelabel versions of Jottacloud and not recommended for normal users.
+    y) Yes
+    n) No (default)
+    y/n> n
 
     Generate a personal login token here: https://www.jottacloud.com/web/secure
     Login Token> <your token here>
@@ -18005,9 +18654,8 @@ This will guide you through an interactive setup process:
     Please select the device to use. Normally this will be Jotta
     Choose a number from below, or type in an existing value
      1 > DESKTOP-3H31129
-     2 > fla1
-     3 > Jotta
-    Devices> 3
+     2 > Jotta
+    Devices> 2
     Please select the mountpoint to user. Normally this will be Archive
     Choose a number from below, or type in an existing value
      1 > Archive
@@ -18018,7 +18666,6 @@ This will guide you through an interactive setup process:
     --------------------
     [jotta]
     type = jottacloud
-    user = 0xC4KE@gmail.com
     token = {........}
     device = Jotta
     mountpoint = Archive
@@ -18048,18 +18695,18 @@ Devices and Mountpoints
 The official Jottacloud client registers a device for each computer you
 install it on, and then creates a mountpoint for each folder you select
 for Backup. The web interface uses a special device called Jotta for the
-Archive and Sync mountpoints. In most cases you’ll want to use the
+Archive and Sync mountpoints. In most cases you'll want to use the
 Jotta/Archive device/mountpoint, however if you want to access files
 uploaded by any of the official clients rclone provides the option to
 select other devices and mountpoints during config.
 
 The built-in Jotta device may also contain several other mountpoints,
 such as: Latest, Links, Shared and Trash. These are special mountpoints
-with a different internal representation than the “regular” 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.
 
-–fast-list
+--fast-list
 
 This remote supports --fast-list which allows you to use fewer
 transactions in exchange for more memory. See the rclone docs for more
@@ -18081,7 +18728,7 @@ 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 (wherever the TMPDIR environment variable points to)
 before it is uploaded. Small files will be cached in memory - see the
-–jottacloud-md5-memory-limit flag.
+--jottacloud-md5-memory-limit flag.
 
 Restricted filename characters
 
@@ -18098,7 +18745,7 @@ characters are also replaced:
   ?            0x3F        ？
   |            0x7C        ｜
 
-Invalid UTF-8 bytes will also be replaced, as they can’t be used in XML
+Invalid UTF-8 bytes will also be replaced, as they can't be used in XML
 strings.
 
 Deleting files
@@ -18106,7 +18753,7 @@ Deleting files
 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
-–jottacloud-hard-delete flag, or set the equivalent environment
+--jottacloud-hard-delete flag, or set the equivalent environment
 variable. Emptying the trash is supported by the cleanup command.
 
 Versions
@@ -18126,7 +18773,7 @@ Advanced Options
 
 Here are the advanced options specific to jottacloud (Jottacloud).
 
-–jottacloud-md5-memory-limit
+--jottacloud-md5-memory-limit
 
 Files bigger than this will be cached on disk to calculate the MD5 if
 required.
@@ -18136,7 +18783,7 @@ required.
 -   Type: SizeSuffix
 -   Default: 10M
 
-–jottacloud-trashed-only
+--jottacloud-trashed-only
 
 Only show files that are in the trash. This will show trashed files in
 their original directory structure.
@@ -18146,7 +18793,7 @@ their original directory structure.
 -   Type: bool
 -   Default: false
 
-–jottacloud-hard-delete
+--jottacloud-hard-delete
 
 Delete files permanently rather than putting them into the trash.
 
@@ -18155,27 +18802,16 @@ Delete files permanently rather than putting them into the trash.
 -   Type: bool
 -   Default: false
 
-–jottacloud-unlink
+--jottacloud-upload-resume-limit
 
-Remove existing public link to file/folder with link command rather than
-creating. Default is false, meaning link command will create or retrieve
-public link.
-
--   Config: unlink
--   Env Var: RCLONE_JOTTACLOUD_UNLINK
--   Type: bool
--   Default: false
-
-–jottacloud-upload-resume-limit
-
-Files bigger than this can be resumed if the upload fail’s.
+Files bigger than this can be resumed if the upload fail's.
 
 -   Config: upload_resume_limit
 -   Env Var: RCLONE_JOTTACLOUD_UPLOAD_RESUME_LIMIT
 -   Type: SizeSuffix
 -   Default: 10M
 
-–jottacloud-encoding
+--jottacloud-encoding
 
 This sets the encoding for the backend.
 
@@ -18189,10 +18825,10 @@ See: the encoding section in the overview for more info.
 
 Limitations
 
-Note that Jottacloud is case insensitive so you can’t have a file called
-“Hello.doc” and one called “hello.doc”.
+Note that Jottacloud is case insensitive so you can't have a file called
+"Hello.doc" and one called "hello.doc".
 
-There are quite a few characters that can’t be in Jottacloud file names.
+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.
@@ -18294,14 +18930,14 @@ characters are also replaced:
   ----------- ------- -------------
   \            0x5C        ＼
 
-Invalid UTF-8 bytes will also be replaced, as they can’t be used in XML
+Invalid UTF-8 bytes will also be replaced, as they can't be used in XML
 strings.
 
 Standard Options
 
 Here are the standard options specific to koofr (Koofr).
 
-–koofr-user
+--koofr-user
 
 Your Koofr user name
 
@@ -18310,11 +18946,13 @@ Your Koofr user name
 -   Type: string
 -   Default: ""
 
-–koofr-password
+--koofr-password
 
 Your Koofr password for rclone (generate one at
 https://app.koofr.net/app/admin/preferences/password)
 
+NB Input to this must be obscured - see rclone obscure.
+
 -   Config: password
 -   Env Var: RCLONE_KOOFR_PASSWORD
 -   Type: string
@@ -18324,16 +18962,16 @@ Advanced Options
 
 Here are the advanced options specific to koofr (Koofr).
 
-–koofr-endpoint
+--koofr-endpoint
 
 The Koofr API endpoint to use
 
 -   Config: endpoint
 -   Env Var: RCLONE_KOOFR_ENDPOINT
 -   Type: string
--   Default: “https://app.koofr.net”
+-   Default: "https://app.koofr.net"
 
-–koofr-mountid
+--koofr-mountid
 
 Mount ID of the mount to use. If omitted, the primary mount is used.
 
@@ -18342,7 +18980,7 @@ Mount ID of the mount to use. If omitted, the primary mount is used.
 -   Type: string
 -   Default: ""
 
-–koofr-setmtime
+--koofr-setmtime
 
 Does the backend support setting modification time. Set this to false if
 you use a mount ID that points to a Dropbox or Amazon Drive backend.
@@ -18352,7 +18990,7 @@ you use a mount ID that points to a Dropbox or Amazon Drive backend.
 -   Type: bool
 -   Default: true
 
-–koofr-encoding
+--koofr-encoding
 
 This sets the encoding for the backend.
 
@@ -18365,8 +19003,8 @@ See: the encoding section in the overview for more info.
 
 Limitations
 
-Note that Koofr is case insensitive so you can’t have a file called
-“Hello.doc” and one called “hello.doc”.
+Note that Koofr is case insensitive so you can't have a file called
+"Hello.doc" and one called "hello.doc".
 
 
 Mail.ru Cloud
@@ -18381,7 +19019,7 @@ for rclone until it gets eventually implemented.
 Features highlights
 
 -   Paths may be as deep as required, eg remote:directory/subdirectory
--   Files have a last modified time property, directories don’t
+-   Files have a last modified time property, directories don't
 -   Deleted files are by default moved to the trash
 -   Files and directories can be shared via public links
 -   Partial uploads or streaming are not supported, file size must be
@@ -18475,13 +19113,13 @@ List the contents of a directory
 Sync /home/local/directory to the remote path, deleting any excess files
 in the path.
 
-    rclone sync /home/local/directory remote:directory
+    rclone sync -i /home/local/directory remote:directory
 
 Modified time
 
 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”.
+as "Jan 1 1970".
 
 Hash checksums
 
@@ -18521,7 +19159,7 @@ characters are also replaced:
   \            0x5C        ＼
   |            0x7C        ｜
 
-Invalid UTF-8 bytes will also be replaced, as they can’t be used in JSON
+Invalid UTF-8 bytes will also be replaced, as they can't be used in JSON
 strings.
 
 Limitations
@@ -18530,14 +19168,14 @@ 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.
 
-Note that Mailru is case insensitive so you can’t have a file called
-“Hello.doc” and one called “hello.doc”.
+Note that Mailru is case insensitive so you can't have a file called
+"Hello.doc" and one called "hello.doc".
 
 Standard Options
 
 Here are the standard options specific to mailru (Mail.ru Cloud).
 
-–mailru-user
+--mailru-user
 
 User name (usually email)
 
@@ -18546,24 +19184,26 @@ User name (usually email)
 -   Type: string
 -   Default: ""
 
-–mailru-pass
+--mailru-pass
 
 Password
 
+NB Input to this must be obscured - see rclone obscure.
+
 -   Config: pass
 -   Env Var: RCLONE_MAILRU_PASS
 -   Type: string
 -   Default: ""
 
-–mailru-speedup-enable
+--mailru-speedup-enable
 
 Skip full upload if there is another file with same data hash. This
-feature is called “speedup” or “put by hash”. It is especially efficient
+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. 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
+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.
 
@@ -18572,36 +19212,36 @@ optimization.
 -   Type: bool
 -   Default: true
 -   Examples:
-    -   “true”
+    -   "true"
         -   Enable
-    -   “false”
+    -   "false"
         -   Disable
 
 Advanced Options
 
 Here are the advanced options specific to mailru (Mail.ru Cloud).
 
-–mailru-speedup-file-patterns
+--mailru-speedup-file-patterns
 
 Comma separated list of file name patterns eligible for speedup (put by
-hash). Patterns are case insensitive and can contain ’*’ or ‘?’ meta
+hash). Patterns are case insensitive and can contain '*' or '?' meta
 characters.
 
 -   Config: speedup_file_patterns
 -   Env Var: RCLONE_MAILRU_SPEEDUP_FILE_PATTERNS
 -   Type: string
--   Default: “_.mkv,_.avi,_.mp4,_.mp3,_.zip,_.gz,_.rar,_.pdf”
+-   Default: "_.mkv,_.avi,_.mp4,_.mp3,_.zip,_.gz,_.rar,_.pdf"
 -   Examples:
     -   ""
         -   Empty list completely disables speedup (put by hash).
     -   "*"
         -   All files will be attempted for speedup.
-    -   “_.mkv,_.avi,_.mp4,_.mp3”
+    -   "_.mkv,_.avi,_.mp4,_.mp3"
         -   Only common audio/video files will be tried for put by hash.
-    -   “_.zip,_.gz,_.rar,_.pdf”
+    -   "_.zip,_.gz,_.rar,_.pdf"
         -   Only common archives or PDF books will be tried for speedup.
 
-–mailru-speedup-max-disk
+--mailru-speedup-max-disk
 
 This option allows you to disable speedup (put by hash) for large files
 (because preliminary hashing can exhaust you RAM or disk space)
@@ -18611,15 +19251,15 @@ This option allows you to disable speedup (put by hash) for large files
 -   Type: SizeSuffix
 -   Default: 3G
 -   Examples:
-    -   “0”
+    -   "0"
         -   Completely disable speedup (put by hash).
-    -   “1G”
+    -   "1G"
         -   Files larger than 1Gb will be uploaded directly.
-    -   “3G”
+    -   "3G"
         -   Choose this option if you have less than 3Gb free on local
             disk.
 
-–mailru-speedup-max-memory
+--mailru-speedup-max-memory
 
 Files larger than the size given below will always be hashed on disk.
 
@@ -18628,15 +19268,15 @@ Files larger than the size given below will always be hashed on disk.
 -   Type: SizeSuffix
 -   Default: 32M
 -   Examples:
-    -   “0”
+    -   "0"
         -   Preliminary hashing will always be done in a temporary disk
             location.
-    -   “32M”
+    -   "32M"
         -   Do not dedicate more than 32Mb RAM for preliminary hashing.
-    -   “256M”
+    -   "256M"
         -   You have at most 256Mb RAM free for hash calculations.
 
-–mailru-check-hash
+--mailru-check-hash
 
 What should copy do if file checksum is mismatched or invalid
 
@@ -18645,22 +19285,22 @@ What should copy do if file checksum is mismatched or invalid
 -   Type: bool
 -   Default: true
 -   Examples:
-    -   “true”
+    -   "true"
         -   Fail with error.
-    -   “false”
+    -   "false"
         -   Ignore and continue.
 
-–mailru-user-agent
+--mailru-user-agent
 
-HTTP user agent used internally by client. Defaults to “rclone/VERSION”
-or “–user-agent” provided on command line.
+HTTP user agent used internally by client. Defaults to "rclone/VERSION"
+or "--user-agent" provided on command line.
 
 -   Config: user_agent
 -   Env Var: RCLONE_MAILRU_USER_AGENT
 -   Type: string
 -   Default: ""
 
-–mailru-quirks
+--mailru-quirks
 
 Comma separated list of internal maintenance flags. This option must not
 be used by an ordinary user. It is intended only to facilitate remote
@@ -18674,7 +19314,7 @@ binlist gzip insecure retry400
 -   Type: string
 -   Default: ""
 
-–mailru-encoding
+--mailru-encoding
 
 This sets the encoding for the backend.
 
@@ -18772,7 +19412,7 @@ Restricted filename characters
   NUL          0x00         ␀
   /            0x2F        ／
 
-Invalid UTF-8 bytes will also be replaced, as they can’t be used in JSON
+Invalid UTF-8 bytes will also be replaced, as they can't be used in JSON
 strings.
 
 Duplicated files
@@ -18787,14 +19427,14 @@ Use rclone dedupe to fix duplicated files.
 
 Failure to log-in
 
-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
+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.
 
 For example, executing this command 90 times in a row
-rclone link remote:file will cause the remote to become “blocked”. This
+rclone link remote:file 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,
+links of a directory with hundred of files... After more or less a week,
 the remote will remote accept rclone logins normally again.
 
 You can mitigate this issue by mounting the remote it with rclone mount.
@@ -18806,16 +19446,16 @@ Rclone does not currently close mega sessions (you can see them in the
 web interface), however closing the sessions does not solve the issue.
 
 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
+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…
+waiting 3 seconds, then continuing...
 
 Note that this has been observed by trial and error and might not be set
 in stone.
 
 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
+log-in) which isn't compatible with the current stateless rclone
 approach.
 
 Note that once blocked, the use of other tools (such as megacmd) is not
@@ -18835,7 +19475,7 @@ Standard Options
 
 Here are the standard options specific to mega (Mega).
 
-–mega-user
+--mega-user
 
 User name
 
@@ -18844,10 +19484,12 @@ User name
 -   Type: string
 -   Default: ""
 
-–mega-pass
+--mega-pass
 
 Password.
 
+NB Input to this must be obscured - see rclone obscure.
+
 -   Config: pass
 -   Env Var: RCLONE_MEGA_PASS
 -   Type: string
@@ -18857,7 +19499,7 @@ Advanced Options
 
 Here are the advanced options specific to mega (Mega).
 
-–mega-debug
+--mega-debug
 
 Output more debug from Mega.
 
@@ -18869,7 +19511,7 @@ information from the mega backend.
 -   Type: bool
 -   Default: false
 
-–mega-hard-delete
+--mega-hard-delete
 
 Delete files permanently rather than putting them into the trash.
 
@@ -18882,7 +19524,7 @@ permanently delete objects instead.
 -   Type: bool
 -   Default: false
 
-–mega-encoding
+--mega-encoding
 
 This sets the encoding for the backend.
 
@@ -18896,7 +19538,7 @@ See: the encoding section in the overview for more info.
 Limitations
 
 This backend uses the go-mega go library which is an opensource go
-library implementing the Mega API. There doesn’t appear to be any
+library implementing the Mega API. There doesn't appear to be any
 documentation for the mega protocol beyond the mega C++ SDK source code
 so there are likely quite a few errors still remaining in this library.
 
@@ -18942,7 +19584,7 @@ want to:
     d) Delete this remote
     y/e/d> y
 
-Because the memory backend isn’t persistent it is most useful for
+Because the memory backend isn't persistent it is most useful for
 testing or with an rclone server or rclone mount, eg
 
     rclone mount :memory: /mnt/tmp
@@ -19018,9 +19660,9 @@ List the contents of a container
 Sync /home/local/directory to the remote container, deleting any excess
 files in the container.
 
-    rclone sync /home/local/directory remote:container
+    rclone sync -i /home/local/directory remote:container
 
-–fast-list
+--fast-list
 
 This remote supports --fast-list which allows you to use fewer
 transactions in exchange for more memory. See the rclone docs for more
@@ -19050,7 +19692,7 @@ get replaced if they are the last character in the name:
   ----------- ------- -------------
   .            0x2E        ．
 
-Invalid UTF-8 bytes will also be replaced, as they can’t be used in JSON
+Invalid UTF-8 bytes will also be replaced, as they can't be used in JSON
 strings.
 
 Hashes
@@ -19090,7 +19732,7 @@ show the container specified by the SAS URL.
     $ rclone lsd azureblob:
     container/
 
-Note that you can’t see or access any other containers - this will fail
+Note that you can't see or access any other containers - this will fail
 
     rclone ls azureblob:othercontainer
 
@@ -19107,15 +19749,15 @@ The files will be uploaded in parallel in 4MB chunks (by default). Note
 that these chunks are buffered in memory and there may be up to
 --transfers of them being uploaded at once.
 
-Files can’t be split into more than 50,000 chunks so by default, so the
+Files can't be split into more than 50,000 chunks so by default, so the
 largest file that can be uploaded with 4MB chunk size is 195GB. Above
 this rclone will double the chunk size until it creates less than 50,000
 chunks. By default this will mean a maximum file size of 3.2TB can be
 uploaded. This can be raised to 5TB using --azureblob-chunk-size 100M.
 
-Note that rclone doesn’t commit the block list until the end of the
+Note that rclone doesn't commit the block list until the end of the
 upload which means that there is a limit of 9.5TB of multipart uploads
-in progress as Azure won’t allow more than that amount of uncommitted
+in progress as Azure won't allow more than that amount of uncommitted
 blocks.
 
 Standard Options
@@ -19123,7 +19765,7 @@ Standard Options
 Here are the standard options specific to azureblob (Microsoft Azure
 Blob Storage).
 
-–azureblob-account
+--azureblob-account
 
 Storage Account Name (leave blank to use SAS URL or Emulator)
 
@@ -19132,7 +19774,7 @@ Storage Account Name (leave blank to use SAS URL or Emulator)
 -   Type: string
 -   Default: ""
 
-–azureblob-key
+--azureblob-key
 
 Storage Account Key (leave blank to use SAS URL or Emulator)
 
@@ -19141,7 +19783,7 @@ Storage Account Key (leave blank to use SAS URL or Emulator)
 -   Type: string
 -   Default: ""
 
-–azureblob-sas-url
+--azureblob-sas-url
 
 SAS URL for container level access only (leave blank if using
 account/key or Emulator)
@@ -19151,9 +19793,9 @@ account/key or Emulator)
 -   Type: string
 -   Default: ""
 
-–azureblob-use-emulator
+--azureblob-use-emulator
 
-Uses local storage emulator if provided as ‘true’ (leave blank if using
+Uses local storage emulator if provided as 'true' (leave blank if using
 real azure storage endpoint)
 
 -   Config: use_emulator
@@ -19166,7 +19808,7 @@ Advanced Options
 Here are the advanced options specific to azureblob (Microsoft Azure
 Blob Storage).
 
-–azureblob-endpoint
+--azureblob-endpoint
 
 Endpoint for the service Leave blank normally.
 
@@ -19175,7 +19817,7 @@ Endpoint for the service Leave blank normally.
 -   Type: string
 -   Default: ""
 
-–azureblob-upload-cutoff
+--azureblob-upload-cutoff
 
 Cutoff for switching to chunked upload (<= 256MB).
 
@@ -19184,11 +19826,11 @@ Cutoff for switching to chunked upload (<= 256MB).
 -   Type: SizeSuffix
 -   Default: 256M
 
-–azureblob-chunk-size
+--azureblob-chunk-size
 
 Upload chunk size (<= 100MB).
 
-Note that this is stored in memory and there may be up to “–transfers”
+Note that this is stored in memory and there may be up to "--transfers"
 chunks stored at once in memory.
 
 -   Config: chunk_size
@@ -19196,12 +19838,12 @@ chunks stored at once in memory.
 -   Type: SizeSuffix
 -   Default: 4M
 
-–azureblob-list-chunk
+--azureblob-list-chunk
 
 Size of blob list.
 
 This sets the number of blobs requested in each listing chunk. Default
-is the maximum, 5000. “List blobs” requests are permitted 2 minutes per
+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 ( source ). This can be used
 to limit the number of blobs items to return, to avoid the time out.
@@ -19211,7 +19853,7 @@ to limit the number of blobs items to return, to avoid the time out.
 -   Type: int
 -   Default: 5000
 
-–azureblob-access-tier
+--azureblob-access-tier
 
 Access tier of blob: hot, cool or archive.
 
@@ -19219,21 +19861,21 @@ Archived blobs can be restored by setting access tier to hot or cool.
 Leave blank if you intend to use default access tier, which is set at
 account level
 
-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
+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” or “Cool”.
+first restore by tiering blob to "Hot" or "Cool".
 
 -   Config: access_tier
 -   Env Var: RCLONE_AZUREBLOB_ACCESS_TIER
 -   Type: string
 -   Default: ""
 
-–azureblob-disable-checksum
+--azureblob-disable-checksum
 
-Don’t store MD5 checksum with object metadata.
+Don't store MD5 checksum with object metadata.
 
 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
@@ -19245,7 +19887,7 @@ start uploading.
 -   Type: bool
 -   Default: false
 
-–azureblob-memory-pool-flush-time
+--azureblob-memory-pool-flush-time
 
 How often internal memory buffer pools will be flushed. Uploads which
 requires additional buffers (f.e multipart) will use memory pool for
@@ -19257,7 +19899,7 @@ removed from the pool.
 -   Type: Duration
 -   Default: 1m0s
 
-–azureblob-memory-pool-use-mmap
+--azureblob-memory-pool-use-mmap
 
 Whether to use mmap buffers in internal memory pool.
 
@@ -19266,7 +19908,7 @@ Whether to use mmap buffers in internal memory pool.
 -   Type: bool
 -   Default: false
 
-–azureblob-encoding
+--azureblob-encoding
 
 This sets the encoding for the backend.
 
@@ -19405,15 +20047,15 @@ To copy a local directory to an OneDrive directory called backup
 Getting your own Client ID and Key
 
 You can use your own Client ID if the default (client_id left blank) one
-doesn’t work for you or you see lots of throttling. The default Client
+doesn't work for you or you see lots of throttling. The default Client
 ID and Key is shared by all rclone users when performing requests.
 
 If you are having problems with them (E.g., seeing a lot of throttling),
 you can get your own Client ID and Key by following the steps below:
 
 1.  Open
-    https://portal.azure.com/#blade/Microsoft_AAD_RegisteredApps/ApplicationsListBlade,
-    then click New registration.
+    https://portal.azure.com/#blade/Microsoft_AAD_RegisteredApps/ApplicationsListBlade
+    and then click New registration.
 2.  Enter a name for your app, choose account type
     Accounts in any organizational directory (Any Azure AD directory - Multitenant) and personal Microsoft accounts (e.g. Skype, Xbox),
     select Web in Redirect URI Enter http://localhost:53682/ and click
@@ -19477,32 +20119,32 @@ get replaced if they are the first character in the name:
   SP           0x20         ␠
   ~            0x7E        ～
 
-Invalid UTF-8 bytes will also be replaced, as they can’t be used in JSON
+Invalid UTF-8 bytes will also be replaced, as they can't be used in JSON
 strings.
 
 Deleting files
 
 Any files you delete with rclone will end up in the trash. Microsoft
-doesn’t provide an API to permanently delete files, nor to empty the
-trash, so you will have to do that with one of Microsoft’s apps or via
+doesn't provide an API to permanently delete files, nor to empty the
+trash, so you will have to do that with one of Microsoft's apps or via
 the OneDrive website.
 
 Standard Options
 
 Here are the standard options specific to onedrive (Microsoft OneDrive).
 
-–onedrive-client-id
+--onedrive-client-id
 
-Microsoft App Client Id Leave blank normally.
+OAuth Client Id Leave blank normally.
 
 -   Config: client_id
 -   Env Var: RCLONE_ONEDRIVE_CLIENT_ID
 -   Type: string
 -   Default: ""
 
-–onedrive-client-secret
+--onedrive-client-secret
 
-Microsoft App Client Secret Leave blank normally.
+OAuth Client Secret Leave blank normally.
 
 -   Config: client_secret
 -   Env Var: RCLONE_ONEDRIVE_CLIENT_SECRET
@@ -19513,7 +20155,34 @@ Advanced Options
 
 Here are the advanced options specific to onedrive (Microsoft OneDrive).
 
-–onedrive-chunk-size
+--onedrive-token
+
+OAuth Access Token as a JSON blob.
+
+-   Config: token
+-   Env Var: RCLONE_ONEDRIVE_TOKEN
+-   Type: string
+-   Default: ""
+
+--onedrive-auth-url
+
+Auth server URL. Leave blank to use the provider defaults.
+
+-   Config: auth_url
+-   Env Var: RCLONE_ONEDRIVE_AUTH_URL
+-   Type: string
+-   Default: ""
+
+--onedrive-token-url
+
+Token server url. Leave blank to use the provider defaults.
+
+-   Config: token_url
+-   Env Var: RCLONE_ONEDRIVE_TOKEN_URL
+-   Type: string
+-   Default: ""
+
+--onedrive-chunk-size
 
 Chunk size to upload files with - must be multiple of 320k (327,680
 bytes).
@@ -19529,7 +20198,7 @@ into memory.
 -   Type: SizeSuffix
 -   Default: 10M
 
-–onedrive-drive-id
+--onedrive-drive-id
 
 The ID of the drive to use
 
@@ -19538,7 +20207,7 @@ The ID of the drive to use
 -   Type: string
 -   Default: ""
 
-–onedrive-drive-type
+--onedrive-drive-type
 
 The type of the drive ( personal | business | documentLibrary )
 
@@ -19547,12 +20216,12 @@ The type of the drive ( personal | business | documentLibrary )
 -   Type: string
 -   Default: ""
 
-–onedrive-expose-onenote-files
+--onedrive-expose-onenote-files
 
 Set to make OneNote files show up in directory listings.
 
 By default rclone will hide OneNote files in directory listings because
-operations like “Open” and “Update” won’t work on them. But this
+operations like "Open" and "Update" won't work on them. But this
 behaviour may also prevent you from deleting them. If you want to delete
 OneNote files or otherwise want them to show up in directory listing,
 set this option.
@@ -19562,21 +20231,41 @@ set this option.
 -   Type: bool
 -   Default: false
 
-–onedrive-server-side-across-configs
+--onedrive-server-side-across-configs
 
 Allow server side operations (eg copy) to work across different onedrive
 configs.
 
 This can be useful if you wish to do a server side copy between two
-different Onedrives. Note that this isn’t enabled by default because it
-isn’t easy to tell if it will work between any two configurations.
+different Onedrives. Note that this isn't enabled by default because it
+isn't easy to tell if it will work between any two configurations.
 
 -   Config: server_side_across_configs
 -   Env Var: RCLONE_ONEDRIVE_SERVER_SIDE_ACROSS_CONFIGS
 -   Type: bool
 -   Default: false
 
-–onedrive-encoding
+--onedrive-no-versions
+
+Remove all versions on modifying operations
+
+Onedrive for business creates versions when rclone uploads new files
+overwriting an existing one and when it sets the modification time.
+
+These versions take up space out of the quota.
+
+This flag checks for versions after file upload and setting modification
+time and removes all but the last version.
+
+NB Onedrive personal can't currently delete versions so don't use this
+flag there.
+
+-   Config: no_versions
+-   Env Var: RCLONE_ONEDRIVE_NO_VERSIONS
+-   Type: bool
+-   Default: false
+
+--onedrive-encoding
 
 This sets the encoding for the backend.
 
@@ -19590,22 +20279,26 @@ See: the encoding section in the overview for more info.
 
 Limitations
 
+If you don't use rclone for 90 days the refresh token will expire. This
+will result in authorization problems. This is easy to fix by running
+the rclone config reconnect remote: command to get a new token and
+refresh token.
+
 Naming
 
-Note that OneDrive is case insensitive so you can’t have a file called
-“Hello.doc” and one called “hello.doc”.
+Note that OneDrive is case insensitive so you can't have a file called
+"Hello.doc" and one called "hello.doc".
 
-There are quite a few characters that can’t be in OneDrive file names.
-These can’t occur on Windows platforms, but on non-Windows platforms
+There are quite a few characters that can't be in OneDrive file names.
+These can't occur on Windows platforms, but on non-Windows platforms
 they are common. 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.
 
 File sizes
 
-The largest allowed file sizes are 15GB for OneDrive for Business and
-100GB for OneDrive Personal (Updated 19 May 2020). Source:
-https://support.office.com/en-us/article/upload-photos-and-files-to-onedrive-b00ad3fe-6643-4b16-9212-de00ef02b586
+The largest allowed file size is 100GB for both OneDrive Personal and
+OneDrive for Business (Updated 17 June 2020).
 
 Path length
 
@@ -19624,24 +20317,39 @@ couldn’t list files: UnknownError:. See #2707 for more info.
 An official document about the limitations for different types of
 OneDrive can be found here.
 
-Versioning issue
+Versions
 
-Every change in OneDrive causes the service to create a new version.
-This counts against a users quota. For example changing the modification
-time of a file creates a second version, so the file is using twice the
-space.
+Every change in a file OneDrive causes the service to create a new
+version of the the file. This counts against a users quota. For example
+changing the modification time of a file creates a second version, so
+the file apparently uses twice the space.
 
-The copy is the only rclone command affected by this as we copy the file
-and then afterwards set the modification time to match the source file.
+For example the copy command is affected by this as rclone copies the
+file and then afterwards sets the modification time to match the source
+file which uses another version.
 
-NOTE: Starting October 2018, users will no longer be able to disable
+You can use the rclone cleanup command (see below) to remove all old
+versions.
+
+Or you can set the no_versions parameter to true and rclone will remove
+versions after operations which create new versions. This takes extra
+transactions so only enable it if you need it.
+
+NOTE At the time of writing Onedrive Personal creates versions (but not
+for setting the modification time) but the API for removing them returns
+"API not found" so cleanup and no_versions should not be used on
+Onedrive Personal.
+
+Disabling versioning
+
+Starting October 2018, users will no longer be able to disable
 versioning by default. This is because Microsoft has brought an update
 to the mechanism. To change this new default setting, a PowerShell
 command is required to be run by a SharePoint admin. If you are an
 admin, you can run these commands in PowerShell to change that setting:
 
 1.  Install-Module -Name Microsoft.Online.SharePoint.PowerShell (in case
-    you haven’t installed this already)
+    you haven't installed this already)
 2.  Import-Module Microsoft.Online.SharePoint.PowerShell -DisableNameChecking
 3.  Connect-SPOService -Url https://YOURSITE-admin.sharepoint.com -Credential YOU@YOURSITE.COM
     (replacing YOURSITE, YOU, YOURSITE.COM with the actual values; this
@@ -19650,7 +20358,7 @@ admin, you can run these commands in PowerShell to change that setting:
 5.  Disconnect-SPOService (to disconnect from the server)
 
 _Below are the steps for normal users to disable versioning. If you
-don’t see the “No Versioning” option, make sure the above requirements
+don't see the "No Versioning" option, make sure the above requirements
 are met._
 
 User Weropol has found a method to disable versioning on OneDrive
@@ -19660,32 +20368,57 @@ User Weropol has found a method to disable versioning on OneDrive
 2.  Click Site settings.
 3.  Once on the Site settings page, navigate to Site Administration >
     Site libraries and lists.
-4.  Click Customize “Documents”.
+4.  Click Customize "Documents".
 5.  Click General Settings > Versioning Settings.
 6.  Under Document Version History select the option No versioning.
     Note: This will disable the creation of new file versions, but will
     not remove any previous versions. Your documents are safe.
 7.  Apply the changes by clicking OK.
 8.  Use rclone to upload or modify files. (I also use the
-    –no-update-modtime flag)
+    --no-update-modtime flag)
 9.  Restore the versioning settings after using rclone. (Optional)
 
+Cleanup
+
+OneDrive supports rclone cleanup which causes rclone to look through
+every file under the path supplied and delete all version but the
+current version. Because this involves traversing all the files, then
+querying each file for versions it can be quite slow. Rclone does
+--checkers tests in parallel. The command also supports -i which is a
+great way to see what it would do.
+
+    rclone cleanup -i remote:path/subdir # interactively remove all old version for path/subdir
+    rclone cleanup remote:path/subdir    # unconditionally remove all old version for path/subdir
+
+NB Onedrive personal can't currently delete versions
+
 Troubleshooting
 
 Unexpected file size/hash differences on Sharepoint
 
 It is a known issue that Sharepoint (not OneDrive or OneDrive for
 Business) silently modifies uploaded files, mainly Office files (.docx,
-.xlsx, etc.), causing file size and hash checks to fail. To use rclone
-with such affected files on Sharepoint, you may disable these checks
-with the following command line arguments:
+.xlsx, etc.), causing file size and hash checks to fail. There are also
+other situations that will cause OneDrive to report inconsistent file
+sizes. To use rclone with such affected files on Sharepoint, you may
+disable these checks with the following command line arguments:
 
     --ignore-checksum --ignore-size
 
-Replacing/deleting existing files on Sharepoint gets “item not found”
+Alternatively, if you have write access to the OneDrive files, it may be
+possible to fix this problem for certain files, by attempting the steps
+below. Open the web interface for OneDrive and find the affected files
+(which will be in the error messages/log for rclone). Simply click on
+each of these files, causing OneDrive to open them on the web. This will
+cause each file to be converted in place to a format that is
+functionally equivalent but which will no longer trigger the size
+discrepancy. Once all problematic files are converted you will no longer
+need the ignore options above.
+
+Replacing/deleting existing files on Sharepoint gets "item not found"
 
 It is a known issue that Sharepoint (not OneDrive or OneDrive for
-Business) may return “item not found” errors when users try to replace
+Business) may return "item not found" errors when users try to replace
 or delete uploaded files; this seems to mainly affect Office files
 (.docx, .xlsx, etc.). As a workaround, you may use the
 --backup-dir <BACKUP_DIR> command line argument so rclone moves the
@@ -19702,8 +20435,8 @@ access_denied (AADSTS65005)
     Code: AADSTS65005
     Description: Using application 'rclone' is currently not supported for your organization [YOUR_ORGANIZATION] because it is in an unmanaged state. An administrator needs to claim ownership of the company by DNS validation of [YOUR_ORGANIZATION] before the application rclone can be provisioned.
 
-This means that rclone can’t use the OneDrive for Business API with your
-account. You can’t do much about it, maybe write an email to your
+This means that rclone can't use the OneDrive for Business API with your
+account. You can't do much about it, maybe write an email to your
 admins.
 
 However, there are other ways to interact with your OneDrive account.
@@ -19718,7 +20451,7 @@ invalid_grant (AADSTS50076)
 If you see the error above after enabling multi-factor authentication
 for your account, you can fix it by refreshing your OAuth refresh token.
 To do that, run rclone config, and choose to edit your OneDrive backend.
-Then, you don’t need to actually make any changes until you reach this
+Then, you don't need to actually make any changes until you reach this
 question: Already have a token - refresh?. For this question, answer y
 and go through the process to refresh your token, just like the first
 time the backend is configured. After this, rclone should work again for
@@ -19814,14 +20547,14 @@ name:
   VT           0x0B         ␋
   CR           0x0D         ␍
 
-Invalid UTF-8 bytes will also be replaced, as they can’t be used in JSON
+Invalid UTF-8 bytes will also be replaced, as they can't be used in JSON
 strings.
 
 Standard Options
 
 Here are the standard options specific to opendrive (OpenDrive).
 
-–opendrive-username
+--opendrive-username
 
 Username
 
@@ -19830,10 +20563,12 @@ Username
 -   Type: string
 -   Default: ""
 
-–opendrive-password
+--opendrive-password
 
 Password.
 
+NB Input to this must be obscured - see rclone obscure.
+
 -   Config: password
 -   Env Var: RCLONE_OPENDRIVE_PASSWORD
 -   Type: string
@@ -19843,7 +20578,7 @@ Advanced Options
 
 Here are the advanced options specific to opendrive (OpenDrive).
 
-–opendrive-encoding
+--opendrive-encoding
 
 This sets the encoding for the backend.
 
@@ -19855,7 +20590,7 @@ See: the encoding section in the overview for more info.
 -   Default:
     Slash,LtGt,DoubleQuote,Colon,Question,Asterisk,Pipe,BackSlash,LeftSpace,LeftCrLfHtVt,RightSpace,RightCrLfHtVt,InvalidUtf8,Dot
 
-–opendrive-chunk-size
+--opendrive-chunk-size
 
 Files will be uploaded in chunks this size.
 
@@ -19869,11 +20604,11 @@ increase memory use.
 
 Limitations
 
-Note that OpenDrive is case insensitive so you can’t have a file called
-“Hello.doc” and one called “hello.doc”.
+Note that OpenDrive is case insensitive so you can't have a file called
+"Hello.doc" and one called "hello.doc".
 
-There are quite a few characters that can’t be in OpenDrive file names.
-These can’t occur on Windows platforms, but on non-Windows platforms
+There are quite a few characters that can't be in OpenDrive file names.
+These can't occur on Windows platforms, but on non-Windows platforms
 they are common. 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.
@@ -19963,9 +20698,9 @@ List the contents of a bucket
 Sync /home/local/directory to the remote bucket, deleting any excess
 files in the bucket.
 
-    rclone sync /home/local/directory remote:bucket
+    rclone sync -i /home/local/directory remote:bucket
 
-–fast-list
+--fast-list
 
 This remote supports --fast-list which allows you to use fewer
 transactions in exchange for more memory. See the rclone docs for more
@@ -19975,7 +20710,7 @@ Multipart uploads
 
 rclone supports multipart uploads with QingStor which means that it can
 upload files bigger than 5GB. Note that files uploaded with multipart
-upload don’t have an MD5SUM.
+upload don't have an MD5SUM.
 
 Note that incomplete multipart uploads older than 24 hours can be
 removed with rclone cleanup remote:bucket just for one bucket
@@ -20010,7 +20745,7 @@ Restricted filename characters
 The control characters 0x00-0x1F and / are replaced as in the default
 restricted characters set. Note that 0x7F is not replaced.
 
-Invalid UTF-8 bytes will also be replaced, as they can’t be used in JSON
+Invalid UTF-8 bytes will also be replaced, as they can't be used in JSON
 strings.
 
 Standard Options
@@ -20018,7 +20753,7 @@ Standard Options
 Here are the standard options specific to qingstor (QingCloud Object
 Storage).
 
-–qingstor-env-auth
+--qingstor-env-auth
 
 Get QingStor credentials from runtime. Only applies if access_key_id and
 secret_access_key is blank.
@@ -20028,13 +20763,13 @@ secret_access_key is blank.
 -   Type: bool
 -   Default: false
 -   Examples:
-    -   “false”
+    -   "false"
         -   Enter QingStor credentials in the next step
-    -   “true”
+    -   "true"
         -   Get QingStor credentials from the environment (env vars or
             IAM)
 
-–qingstor-access-key-id
+--qingstor-access-key-id
 
 QingStor Access Key ID Leave blank for anonymous access or runtime
 credentials.
@@ -20044,7 +20779,7 @@ credentials.
 -   Type: string
 -   Default: ""
 
-–qingstor-secret-access-key
+--qingstor-secret-access-key
 
 QingStor Secret Access Key (password) Leave blank for anonymous access
 or runtime credentials.
@@ -20054,32 +20789,32 @@ or runtime credentials.
 -   Type: string
 -   Default: ""
 
-–qingstor-endpoint
+--qingstor-endpoint
 
 Enter an endpoint URL to connection QingStor API. Leave blank will use
-the default value “https://qingstor.com:443”
+the default value "https://qingstor.com:443"
 
 -   Config: endpoint
 -   Env Var: RCLONE_QINGSTOR_ENDPOINT
 -   Type: string
 -   Default: ""
 
-–qingstor-zone
+--qingstor-zone
 
-Zone to connect to. Default is “pek3a”.
+Zone to connect to. Default is "pek3a".
 
 -   Config: zone
 -   Env Var: RCLONE_QINGSTOR_ZONE
 -   Type: string
 -   Default: ""
 -   Examples:
-    -   “pek3a”
+    -   "pek3a"
         -   The Beijing (China) Three Zone
         -   Needs location constraint pek3a.
-    -   “sh1a”
+    -   "sh1a"
         -   The Shanghai (China) First Zone
         -   Needs location constraint sh1a.
-    -   “gd2a”
+    -   "gd2a"
         -   The Guangdong (China) Second Zone
         -   Needs location constraint gd2a.
 
@@ -20088,7 +20823,7 @@ Advanced Options
 Here are the advanced options specific to qingstor (QingCloud Object
 Storage).
 
-–qingstor-connection-retries
+--qingstor-connection-retries
 
 Number of connection retries.
 
@@ -20097,7 +20832,7 @@ Number of connection retries.
 -   Type: int
 -   Default: 3
 
-–qingstor-upload-cutoff
+--qingstor-upload-cutoff
 
 Cutoff for switching to chunked upload
 
@@ -20109,14 +20844,14 @@ minimum is 0 and the maximum is 5GB.
 -   Type: SizeSuffix
 -   Default: 200M
 
-–qingstor-chunk-size
+--qingstor-chunk-size
 
 Chunk size to use for uploading.
 
 When uploading files larger than upload_cutoff they will be uploaded as
 multipart uploads using this chunk size.
 
-Note that “–qingstor-upload-concurrency” chunks of this size are
+Note that "--qingstor-upload-concurrency" chunks of this size are
 buffered in memory per transfer.
 
 If you are transferring large files over high speed links and you have
@@ -20127,7 +20862,7 @@ enough memory, then increasing this will speed up the transfers.
 -   Type: SizeSuffix
 -   Default: 4M
 
-–qingstor-upload-concurrency
+--qingstor-upload-concurrency
 
 Concurrency for multipart uploads.
 
@@ -20146,7 +20881,7 @@ this may help to speed up the transfers.
 -   Type: int
 -   Default: 1
 
-–qingstor-encoding
+--qingstor-encoding
 
 This sets the encoding for the backend.
 
@@ -20285,7 +21020,7 @@ List the contents of a container
 Sync /home/local/directory to the remote container, deleting any excess
 files in the container.
 
-    rclone sync /home/local/directory remote:container
+    rclone sync -i /home/local/directory remote:container
 
 Configuration from an OpenStack credentials file
 
@@ -20332,7 +21067,7 @@ Using an alternate authentication method
 
 If your OpenStack installation uses a non-standard authentication method
 that might not be yet supported by rclone or the underlying swift
-library, you can authenticate externally (e.g. calling manually the
+library, you can authenticate externally (e.g. calling manually the
 openstack commands to get a token). Then, you just need to pass the two
 configuration variables auth_token and storage_url. If they are both
 provided, the other variables are ignored. rclone will not try to
@@ -20349,13 +21084,13 @@ this:
     export RCLONE_CONFIG_MYREMOTE_ENV_AUTH=true
     rclone lsd myremote:
 
-–fast-list
+--fast-list
 
 This remote supports --fast-list which allows you to use fewer
 transactions in exchange for more memory. See the rclone docs for more
 details.
 
-–update and –use-server-modtime
+--update and --use-server-modtime
 
 As noted below, the modified time is stored on metadata on the object.
 It is used by default for all operations that require checking the time
@@ -20364,7 +21099,7 @@ a true filesystem, but it is inefficient because it requires an extra
 API call to retrieve the metadata.
 
 For many operations, the time the object was last uploaded to the remote
-is sufficient to determine if it is “dirty”. By using --update along
+is sufficient to determine if it is "dirty". By using --update along
 with --use-server-modtime, you can avoid the extra API call and simply
 upload files whose local modtime is newer than the time it was last
 uploaded.
@@ -20374,7 +21109,7 @@ Standard Options
 Here are the standard options specific to swift (OpenStack Swift
 (Rackspace Cloud Files, Memset Memstore, OVH)).
 
-–swift-env-auth
+--swift-env-auth
 
 Get swift credentials from environment variables in standard OpenStack
 form.
@@ -20384,13 +21119,13 @@ form.
 -   Type: bool
 -   Default: false
 -   Examples:
-    -   “false”
+    -   "false"
         -   Enter swift credentials in the next step
-    -   “true”
+    -   "true"
         -   Get swift credentials from environment vars. Leave other
             fields blank if using this.
 
-–swift-user
+--swift-user
 
 User name to log in (OS_USERNAME).
 
@@ -20399,7 +21134,7 @@ User name to log in (OS_USERNAME).
 -   Type: string
 -   Default: ""
 
-–swift-key
+--swift-key
 
 API key or password (OS_PASSWORD).
 
@@ -20408,7 +21143,7 @@ API key or password (OS_PASSWORD).
 -   Type: string
 -   Default: ""
 
-–swift-auth
+--swift-auth
 
 Authentication URL for server (OS_AUTH_URL).
 
@@ -20417,20 +21152,20 @@ Authentication URL for server (OS_AUTH_URL).
 -   Type: string
 -   Default: ""
 -   Examples:
-    -   “https://auth.api.rackspacecloud.com/v1.0”
+    -   "https://auth.api.rackspacecloud.com/v1.0"
         -   Rackspace US
-    -   “https://lon.auth.api.rackspacecloud.com/v1.0”
+    -   "https://lon.auth.api.rackspacecloud.com/v1.0"
         -   Rackspace UK
-    -   “https://identity.api.rackspacecloud.com/v2.0”
+    -   "https://identity.api.rackspacecloud.com/v2.0"
         -   Rackspace v2
-    -   “https://auth.storage.memset.com/v1.0”
+    -   "https://auth.storage.memset.com/v1.0"
         -   Memset Memstore UK
-    -   “https://auth.storage.memset.com/v2.0”
+    -   "https://auth.storage.memset.com/v2.0"
         -   Memset Memstore UK v2
-    -   “https://auth.cloud.ovh.net/v3”
+    -   "https://auth.cloud.ovh.net/v3"
         -   OVH
 
-–swift-user-id
+--swift-user-id
 
 User ID to log in - optional - most swift systems use user and leave
 this blank (v3 auth) (OS_USER_ID).
@@ -20440,7 +21175,7 @@ this blank (v3 auth) (OS_USER_ID).
 -   Type: string
 -   Default: ""
 
-–swift-domain
+--swift-domain
 
 User domain - optional (v3 auth) (OS_USER_DOMAIN_NAME)
 
@@ -20449,7 +21184,7 @@ User domain - optional (v3 auth) (OS_USER_DOMAIN_NAME)
 -   Type: string
 -   Default: ""
 
-–swift-tenant
+--swift-tenant
 
 Tenant name - optional for v1 auth, this or tenant_id required otherwise
 (OS_TENANT_NAME or OS_PROJECT_NAME)
@@ -20459,7 +21194,7 @@ Tenant name - optional for v1 auth, this or tenant_id required otherwise
 -   Type: string
 -   Default: ""
 
-–swift-tenant-id
+--swift-tenant-id
 
 Tenant ID - optional for v1 auth, this or tenant required otherwise
 (OS_TENANT_ID)
@@ -20469,7 +21204,7 @@ Tenant ID - optional for v1 auth, this or tenant required otherwise
 -   Type: string
 -   Default: ""
 
-–swift-tenant-domain
+--swift-tenant-domain
 
 Tenant domain - optional (v3 auth) (OS_PROJECT_DOMAIN_NAME)
 
@@ -20478,7 +21213,7 @@ Tenant domain - optional (v3 auth) (OS_PROJECT_DOMAIN_NAME)
 -   Type: string
 -   Default: ""
 
-–swift-region
+--swift-region
 
 Region name - optional (OS_REGION_NAME)
 
@@ -20487,7 +21222,7 @@ Region name - optional (OS_REGION_NAME)
 -   Type: string
 -   Default: ""
 
-–swift-storage-url
+--swift-storage-url
 
 Storage URL - optional (OS_STORAGE_URL)
 
@@ -20496,7 +21231,7 @@ Storage URL - optional (OS_STORAGE_URL)
 -   Type: string
 -   Default: ""
 
-–swift-auth-token
+--swift-auth-token
 
 Auth Token from alternate authentication - optional (OS_AUTH_TOKEN)
 
@@ -20505,7 +21240,7 @@ Auth Token from alternate authentication - optional (OS_AUTH_TOKEN)
 -   Type: string
 -   Default: ""
 
-–swift-application-credential-id
+--swift-application-credential-id
 
 Application Credential ID (OS_APPLICATION_CREDENTIAL_ID)
 
@@ -20514,7 +21249,7 @@ Application Credential ID (OS_APPLICATION_CREDENTIAL_ID)
 -   Type: string
 -   Default: ""
 
-–swift-application-credential-name
+--swift-application-credential-name
 
 Application Credential Name (OS_APPLICATION_CREDENTIAL_NAME)
 
@@ -20523,7 +21258,7 @@ Application Credential Name (OS_APPLICATION_CREDENTIAL_NAME)
 -   Type: string
 -   Default: ""
 
-–swift-application-credential-secret
+--swift-application-credential-secret
 
 Application Credential Secret (OS_APPLICATION_CREDENTIAL_SECRET)
 
@@ -20532,7 +21267,7 @@ Application Credential Secret (OS_APPLICATION_CREDENTIAL_SECRET)
 -   Type: string
 -   Default: ""
 
-–swift-auth-version
+--swift-auth-version
 
 AuthVersion - optional - set to (1,2,3) if your auth URL has no version
 (ST_AUTH_VERSION)
@@ -20542,23 +21277,23 @@ AuthVersion - optional - set to (1,2,3) if your auth URL has no version
 -   Type: int
 -   Default: 0
 
-–swift-endpoint-type
+--swift-endpoint-type
 
 Endpoint type to choose from the service catalogue (OS_ENDPOINT_TYPE)
 
 -   Config: endpoint_type
 -   Env Var: RCLONE_SWIFT_ENDPOINT_TYPE
 -   Type: string
--   Default: “public”
+-   Default: "public"
 -   Examples:
-    -   “public”
+    -   "public"
         -   Public (default, choose this if not sure)
-    -   “internal”
+    -   "internal"
         -   Internal (use internal service net)
-    -   “admin”
+    -   "admin"
         -   Admin
 
-–swift-storage-policy
+--swift-storage-policy
 
 The storage policy to use when creating a new container
 
@@ -20573,9 +21308,9 @@ values and their meaning depend on your Swift storage provider.
 -   Examples:
     -   ""
         -   Default
-    -   “pcs”
+    -   "pcs"
         -   OVH Public Cloud Storage
-    -   “pca”
+    -   "pca"
         -   OVH Public Cloud Archive
 
 Advanced Options
@@ -20583,7 +21318,7 @@ Advanced Options
 Here are the advanced options specific to swift (OpenStack Swift
 (Rackspace Cloud Files, Memset Memstore, OVH)).
 
-–swift-chunk-size
+--swift-chunk-size
 
 Above this size files will be chunked into a _segments container.
 
@@ -20595,9 +21330,9 @@ default for this is 5GB which is its maximum value.
 -   Type: SizeSuffix
 -   Default: 5G
 
-–swift-no-chunk
+--swift-no-chunk
 
-Don’t chunk files during streaming upload.
+Don't chunk files during streaming upload.
 
 When doing streaming uploads (eg using rcat or mount) setting this flag
 will cause the swift backend to not upload chunked files.
@@ -20613,7 +21348,7 @@ copy operations.
 -   Type: bool
 -   Default: false
 
-–swift-encoding
+--swift-encoding
 
 This sets the encoding for the backend.
 
@@ -20639,30 +21374,30 @@ Restricted filename characters
   NUL          0x00         ␀
   /            0x2F        ／
 
-Invalid UTF-8 bytes will also be replaced, as they can’t be used in JSON
+Invalid UTF-8 bytes will also be replaced, as they can't be used in JSON
 strings.
 
 Limitations
 
-The Swift API doesn’t return a correct MD5SUM for segmented files
-(Dynamic or Static Large Objects) so rclone won’t check or use the
+The Swift API doesn't return a correct MD5SUM for segmented files
+(Dynamic or Static Large Objects) so rclone won't check or use the
 MD5SUM for these.
 
 Troubleshooting
 
-Rclone gives Failed to create file system for “remote:”: Bad Request
+Rclone gives Failed to create file system for "remote:": Bad Request
 
-Due to an oddity of the underlying swift library, it gives a “Bad
-Request” error rather than a more sensible error when the authentication
+Due to an oddity of the underlying swift library, it gives a "Bad
+Request" error rather than a more sensible error when the authentication
 fails for Swift.
 
 So this most likely means your username / password is wrong. You can
 investigate further with the --dump-bodies flag.
 
-This may also be caused by specifying the region when you shouldn’t have
+This may also be caused by specifying the region when you shouldn't have
 (eg OVH).
 
-Rclone gives Failed to create file system: Response didn’t have storage url and auth token
+Rclone gives Failed to create file system: Response didn't have storage url and auth token
 
 This is most likely caused by forgetting to specify your tenant when
 setting up a swift remote.
@@ -20764,7 +21499,7 @@ characters are also replaced:
   ----------- ------- -------------
   \            0x5C        ＼
 
-Invalid UTF-8 bytes will also be replaced, as they can’t be used in JSON
+Invalid UTF-8 bytes will also be replaced, as they can't be used in JSON
 strings.
 
 Deleting files
@@ -20798,18 +21533,18 @@ Standard Options
 
 Here are the standard options specific to pcloud (Pcloud).
 
-–pcloud-client-id
+--pcloud-client-id
 
-Pcloud App Client Id Leave blank normally.
+OAuth Client Id Leave blank normally.
 
 -   Config: client_id
 -   Env Var: RCLONE_PCLOUD_CLIENT_ID
 -   Type: string
 -   Default: ""
 
-–pcloud-client-secret
+--pcloud-client-secret
 
-Pcloud App Client Secret Leave blank normally.
+OAuth Client Secret Leave blank normally.
 
 -   Config: client_secret
 -   Env Var: RCLONE_PCLOUD_CLIENT_SECRET
@@ -20820,7 +21555,34 @@ Advanced Options
 
 Here are the advanced options specific to pcloud (Pcloud).
 
-–pcloud-encoding
+--pcloud-token
+
+OAuth Access Token as a JSON blob.
+
+-   Config: token
+-   Env Var: RCLONE_PCLOUD_TOKEN
+-   Type: string
+-   Default: ""
+
+--pcloud-auth-url
+
+Auth server URL. Leave blank to use the provider defaults.
+
+-   Config: auth_url
+-   Env Var: RCLONE_PCLOUD_AUTH_URL
+-   Type: string
+-   Default: ""
+
+--pcloud-token-url
+
+Token server url. Leave blank to use the provider defaults.
+
+-   Config: token_url
+-   Env Var: RCLONE_PCLOUD_TOKEN_URL
+-   Type: string
+-   Default: ""
+
+--pcloud-encoding
 
 This sets the encoding for the backend.
 
@@ -20831,14 +21593,32 @@ See: the encoding section in the overview for more info.
 -   Type: MultiEncoder
 -   Default: Slash,BackSlash,Del,Ctl,InvalidUtf8,Dot
 
-–pcloud-root-folder-id
+--pcloud-root-folder-id
 
 Fill in for rclone to use a non root folder as its starting point.
 
 -   Config: root_folder_id
 -   Env Var: RCLONE_PCLOUD_ROOT_FOLDER_ID
 -   Type: string
--   Default: “d0”
+-   Default: "d0"
+
+--pcloud-hostname
+
+Hostname to connect to.
+
+This is normally set when rclone initially does the oauth connection,
+however you will need to set it by hand if you are using remote config
+with rclone authorize.
+
+-   Config: hostname
+-   Env Var: RCLONE_PCLOUD_HOSTNAME
+-   Type: string
+-   Default: "api.pcloud.com"
+-   Examples:
+    -   "api.pcloud.com"
+        -   Original/US region
+    -   "eapi.pcloud.com"
+        -   EU region
 
 
 premiumize.me
@@ -20933,14 +21713,14 @@ characters are also replaced:
   \            0x5C        ＼
   "            0x22        ＂
 
-Invalid UTF-8 bytes will also be replaced, as they can’t be used in JSON
+Invalid UTF-8 bytes will also be replaced, as they can't be used in JSON
 strings.
 
 Standard Options
 
 Here are the standard options specific to premiumizeme (premiumize.me).
 
-–premiumizeme-api-key
+--premiumizeme-api-key
 
 API Key.
 
@@ -20955,7 +21735,7 @@ Advanced Options
 
 Here are the advanced options specific to premiumizeme (premiumize.me).
 
-–premiumizeme-encoding
+--premiumizeme-encoding
 
 This sets the encoding for the backend.
 
@@ -20968,10 +21748,10 @@ See: the encoding section in the overview for more info.
 
 Limitations
 
-Note that premiumize.me is case insensitive so you can’t have a file
-called “Hello.doc” and one called “hello.doc”.
+Note that premiumize.me is case insensitive so you can't have a file
+called "Hello.doc" and one called "hello.doc".
 
-premiumize.me file names can’t have the \ or " characters in. rclone
+premiumize.me file names can't have the \ or " characters in. rclone
 maps these to and from an identical looking unicode equivalents ＼ and
 ＂
 
@@ -21075,14 +21855,14 @@ characters are also replaced:
   ----------- ------- -------------
   \            0x5C        ＼
 
-Invalid UTF-8 bytes will also be replaced, as they can’t be used in JSON
+Invalid UTF-8 bytes will also be replaced, as they can't be used in JSON
 strings.
 
 Advanced Options
 
 Here are the advanced options specific to putio (Put.io).
 
-–putio-encoding
+--putio-encoding
 
 This sets the encoding for the backend.
 
@@ -21104,7 +21884,7 @@ supported. - It supports 2FA enabled users
 Root mode vs Library mode
 
 There are two distinct modes you can setup your remote: - you point your
-remote to the ROOT OF THE SERVER, meaning you don’t specify a library
+remote to the ROOT OF THE SERVER, meaning you don't specify a library
 during the configuration: Paths are specified as remote:library. You may
 put subdirectories in too, eg remote:library/path/to/dir. - you point
 your remote to a specific library during the configuration: Paths are
@@ -21187,7 +21967,7 @@ username) and your password.
     d) Delete this remote
     y/e/d> y
 
-This remote is called seafile. It’s pointing to the root of your seafile
+This remote is called seafile. It's pointing to the root of your seafile
 server and can now be used like this:
 
 See all libraries
@@ -21205,11 +21985,11 @@ List the contents of a library
 Sync /home/local/directory to the remote library, deleting any excess
 files in the library.
 
-    rclone sync /home/local/directory seafile:library
+    rclone sync -i /home/local/directory seafile:library
 
 Configuration in library mode
 
-Here’s an example of a configuration in library mode with a user that
+Here's an example of a configuration in library mode with a user that
 has the two-factor authentication enabled. Your 2FA code will be asked
 at the end of the configuration, and will attempt to authenticate you:
 
@@ -21281,7 +22061,7 @@ at the end of the configuration, and will attempt to authenticate you:
     d) Delete this remote
     y/e/d> y
 
-You’ll notice your password is blank in the configuration. It’s because
+You'll notice your password is blank in the configuration. It's because
 we only need the password to authenticate you once.
 
 You specified My Library during the configuration. The root of the
@@ -21302,9 +22082,9 @@ List the contents of a directory
 Sync /home/local/directory to the remote library, deleting any excess
 files in the library.
 
-    rclone sync /home/local/directory seafile:
+    rclone sync -i /home/local/directory seafile:
 
-–fast-list
+--fast-list
 
 Seafile version 7+ supports --fast-list which allows you to use fewer
 transactions in exchange for more memory. See the rclone docs for more
@@ -21321,7 +22101,7 @@ characters are also replaced:
   "            0x22        ＂
   \            0x5C        ＼
 
-Invalid UTF-8 bytes will also be replaced, as they can’t be used in JSON
+Invalid UTF-8 bytes will also be replaced, as they can't be used in JSON
 strings.
 
 Seafile and rclone link
@@ -21348,13 +22128,13 @@ versions: - 6.3.4 community edition - 7.0.5 community edition - 7.1.3
 community edition
 
 Versions below 6.0 are not supported. Versions between 6.0 and 6.3
-haven’t been tested and might not work properly.
+haven't been tested and might not work properly.
 
 Standard Options
 
 Here are the standard options specific to seafile (seafile).
 
-–seafile-url
+--seafile-url
 
 URL of seafile host to connect to
 
@@ -21363,10 +22143,10 @@ URL of seafile host to connect to
 -   Type: string
 -   Default: ""
 -   Examples:
-    -   “https://cloud.seafile.com/”
+    -   "https://cloud.seafile.com/"
         -   Connect to cloud.seafile.com
 
-–seafile-user
+--seafile-user
 
 User name (usually email address)
 
@@ -21375,25 +22155,27 @@ User name (usually email address)
 -   Type: string
 -   Default: ""
 
-–seafile-pass
+--seafile-pass
 
 Password
 
+NB Input to this must be obscured - see rclone obscure.
+
 -   Config: pass
 -   Env Var: RCLONE_SEAFILE_PASS
 -   Type: string
 -   Default: ""
 
-–seafile-2fa
+--seafile-2fa
 
-Two-factor authentication (‘true’ if the account has 2FA enabled)
+Two-factor authentication ('true' if the account has 2FA enabled)
 
 -   Config: 2fa
 -   Env Var: RCLONE_SEAFILE_2FA
 -   Type: bool
 -   Default: false
 
-–seafile-library
+--seafile-library
 
 Name of the library. Leave blank to access all non-encrypted libraries.
 
@@ -21402,17 +22184,19 @@ Name of the library. Leave blank to access all non-encrypted libraries.
 -   Type: string
 -   Default: ""
 
-–seafile-library-key
+--seafile-library-key
 
 Library password (for encrypted libraries only). Leave blank if you pass
 it through the command line.
 
+NB Input to this must be obscured - see rclone obscure.
+
 -   Config: library_key
 -   Env Var: RCLONE_SEAFILE_LIBRARY_KEY
 -   Type: string
 -   Default: ""
 
-–seafile-auth-token
+--seafile-auth-token
 
 Authentication token
 
@@ -21425,16 +22209,16 @@ Advanced Options
 
 Here are the advanced options specific to seafile (seafile).
 
-–seafile-create-library
+--seafile-create-library
 
-Should rclone create a library if it doesn’t exist
+Should rclone create a library if it doesn't exist
 
 -   Config: create_library
 -   Env Var: RCLONE_SEAFILE_CREATE_LIBRARY
 -   Type: bool
 -   Default: false
 
-–seafile-encoding
+--seafile-encoding
 
 This sets the encoding for the backend.
 
@@ -21460,7 +22244,7 @@ installations.
 
 Paths are specified as remote:path. If the path does not begin with a /
 it is relative to the home directory of the user. An empty path remote:
-refers to the user’s home directory.
+refers to the user's home directory.
 
 "Note that some SFTP servers will need the leading / - Synology is a
 good example of this. rsync.net, on the other hand, requires users to
@@ -21532,7 +22316,7 @@ List the contents of a directory
 Sync /home/local/directory to the remote directory, deleting any excess
 files in the directory.
 
-    rclone sync /home/local/directory remote:directory
+    rclone sync -i /home/local/directory remote:directory
 
 SSH Authentication
 
@@ -21548,16 +22332,17 @@ are supported.
 
 The key file can be specified in either an external file (key_file) or
 contained within the rclone config file (key_pem). If using key_pem in
-the config file, the entry should be on a single line with new line (‘’
-or ‘’) separating lines. i.e. 
+the config file, the entry should be on a single line with new line (''
+or '') separating lines. i.e.
 
-key_pem = —–BEGIN RSA PRIVATE KEY—–0gAMbMbaSsd—–END RSA PRIVATE KEY—–
+key_pem = -----BEGIN RSA PRIVATE KEY-----0gAMbMbaSsd-----END RSA PRIVATE
+KEY-----
 
 This will generate it correctly for key_pem for use in the config:
 
     awk '{printf "%s\\n", $0}' < ~/.ssh/id_rsa
 
-If you don’t specify pass, key_file, or key_pem then rclone will attempt
+If you don't specify pass, key_file, or key_pem then rclone will attempt
 to contact an ssh-agent.
 
 You can also specify key_use_agent to force the usage of an ssh-agent.
@@ -21600,7 +22385,7 @@ Standard Options
 
 Here are the standard options specific to sftp (SSH/SFTP Connection).
 
-–sftp-host
+--sftp-host
 
 SSH host to connect to
 
@@ -21609,10 +22394,10 @@ SSH host to connect to
 -   Type: string
 -   Default: ""
 -   Examples:
-    -   “example.com”
+    -   "example.com"
         -   Connect to example.com
 
-–sftp-user
+--sftp-user
 
 SSH username, leave blank for current username, ncw
 
@@ -21621,7 +22406,7 @@ SSH username, leave blank for current username, ncw
 -   Type: string
 -   Default: ""
 
-–sftp-port
+--sftp-port
 
 SSH port, leave blank to use default (22)
 
@@ -21630,16 +22415,18 @@ SSH port, leave blank to use default (22)
 -   Type: string
 -   Default: ""
 
-–sftp-pass
+--sftp-pass
 
 SSH password, leave blank to use ssh-agent.
 
+NB Input to this must be obscured - see rclone obscure.
+
 -   Config: pass
 -   Env Var: RCLONE_SFTP_PASS
 -   Type: string
 -   Default: ""
 
-–sftp-key-pem
+--sftp-key-pem
 
 Raw PEM-encoded private key, If specified, will override key_file
 parameter.
@@ -21649,33 +22436,38 @@ parameter.
 -   Type: string
 -   Default: ""
 
-–sftp-key-file
+--sftp-key-file
 
 Path to PEM-encoded private key file, leave blank or set key-use-agent
 to use ssh-agent.
 
+Leading ~ will be expanded in the file name as will environment
+variables such as ${RCLONE_CONFIG_DIR}.
+
 -   Config: key_file
 -   Env Var: RCLONE_SFTP_KEY_FILE
 -   Type: string
 -   Default: ""
 
-–sftp-key-file-pass
+--sftp-key-file-pass
 
 The passphrase to decrypt the PEM-encoded private key file.
 
 Only PEM encrypted key files (old OpenSSH format) are supported.
-Encrypted keys in the new OpenSSH format can’t be used.
+Encrypted keys in the new OpenSSH format can't be used.
+
+NB Input to this must be obscured - see rclone obscure.
 
 -   Config: key_file_pass
 -   Env Var: RCLONE_SFTP_KEY_FILE_PASS
 -   Type: string
 -   Default: ""
 
-–sftp-key-use-agent
+--sftp-key-use-agent
 
 When set forces the usage of the ssh-agent.
 
-When key-file is also set, the “.pub” file of the specified key-file is
+When key-file is also set, the ".pub" file of the specified key-file is
 read and only the associated key is requested from the ssh-agent. This
 allows to avoid Too many authentication failures for *username* errors
 when the ssh-agent contains many keys.
@@ -21685,7 +22477,7 @@ when the ssh-agent contains many keys.
 -   Type: bool
 -   Default: false
 
-–sftp-use-insecure-cipher
+--sftp-use-insecure-cipher
 
 Enable the use of insecure ciphers and key exchange methods.
 
@@ -21707,14 +22499,14 @@ recovered by an attacker.
 -   Type: bool
 -   Default: false
 -   Examples:
-    -   “false”
+    -   "false"
         -   Use default Cipher list.
-    -   “true”
+    -   "true"
         -   Enables the use of the aes128-cbc cipher and
             diffie-hellman-group-exchange-sha256,
             diffie-hellman-group-exchange-sha1 key exchange.
 
-–sftp-disable-hashcheck
+--sftp-disable-hashcheck
 
 Disable the execution of SSH commands to determine if remote file
 hashing is available. Leave blank or set to false to enable hashing
@@ -21729,7 +22521,7 @@ Advanced Options
 
 Here are the advanced options specific to sftp (SSH/SFTP Connection).
 
-–sftp-ask-password
+--sftp-ask-password
 
 Allow asking for SFTP password when needed.
 
@@ -21741,7 +22533,7 @@ password - not contact the ssh agent
 -   Type: bool
 -   Default: false
 
-–sftp-path-override
+--sftp-path-override
 
 Override path used by SSH connection.
 
@@ -21752,7 +22544,7 @@ Shared folders can be found in directories representing volumes
 
     rclone sync /home/local/directory remote:/directory --ssh-path-override /volume2/directory
 
-Home directory can be found in a shared folder called “home”
+Home directory can be found in a shared folder called "home"
 
     rclone sync /home/local/directory remote:/home/directory --ssh-path-override /volume1/homes/USER/directory
 
@@ -21761,7 +22553,7 @@ Home directory can be found in a shared folder called “home”
 -   Type: string
 -   Default: ""
 
-–sftp-set-modtime
+--sftp-set-modtime
 
 Set the modified time on the remote if set.
 
@@ -21770,7 +22562,7 @@ Set the modified time on the remote if set.
 -   Type: bool
 -   Default: true
 
-–sftp-md5sum-command
+--sftp-md5sum-command
 
 The command used to read md5 hashes. Leave blank for autodetect.
 
@@ -21779,7 +22571,7 @@ The command used to read md5 hashes. Leave blank for autodetect.
 -   Type: string
 -   Default: ""
 
-–sftp-sha1sum-command
+--sftp-sha1sum-command
 
 The command used to read sha1 hashes. Leave blank for autodetect.
 
@@ -21788,7 +22580,7 @@ The command used to read sha1 hashes. Leave blank for autodetect.
 -   Type: string
 -   Default: ""
 
-–sftp-skip-links
+--sftp-skip-links
 
 Set to skip any symlinks and any other non regular files.
 
@@ -21797,10 +22589,30 @@ Set to skip any symlinks and any other non regular files.
 -   Type: bool
 -   Default: false
 
+--sftp-subsystem
+
+Specifies the SSH2 subsystem on the remote host.
+
+-   Config: subsystem
+-   Env Var: RCLONE_SFTP_SUBSYSTEM
+-   Type: string
+-   Default: "sftp"
+
+--sftp-server-command
+
+Specifies the path or command to run a sftp server on the remote host.
+
+The subsystem option is ignored when server_command is defined.
+
+-   Config: server_command
+-   Env Var: RCLONE_SFTP_SERVER_COMMAND
+-   Type: string
+-   Default: ""
+
 Limitations
 
 SFTP supports checksums if the same login has shell access and md5sum or
-sha1sum as well as echo are in the remote’s PATH. This remote
+sha1sum as well as echo are in the remote's PATH. This remote
 checksumming (file hashing) is recommended and enabled by default.
 Disabling the checksumming may be required if you are connecting to SFTP
 servers which are not under your control, and to which the execution of
@@ -21808,17 +22620,17 @@ remote commands is prohibited. Set the configuration option
 disable_hashcheck to true to disable checksumming.
 
 SFTP also supports about if the same login has shell access and df are
-in the remote’s PATH. about will return the total space, free space, and
+in the remote's PATH. about will return the total space, free space, and
 used space on the remote for the disk of the specified path on the
 remote or, if not set, the disk of the root on the remote. about will
-fail if it does not have shell access or if df is not in the remote’s
+fail if it does not have shell access or if df is not in the remote's
 PATH.
 
 Note that some SFTP servers (eg Synology) the paths are different for
-SSH and SFTP so the hashes can’t be calculated properly. For them using
+SSH and SFTP so the hashes can't be calculated properly. For them using
 disable_hashcheck is a good idea.
 
-The only ssh agent supported under Windows is Putty’s pageant.
+The only ssh agent supported under Windows is Putty's pageant.
 
 The Go SSH library disables the use of the aes128-cbc cipher by default,
 due to security concerns. This can be re-enabled on a per-connection
@@ -21826,26 +22638,26 @@ basis by setting the use_insecure_cipher setting in the configuration
 file to true. Further details on the insecurity of this cipher can be
 found [in this paper] (http://www.isg.rhul.ac.uk/~kp/SandPfinal.pdf).
 
-SFTP isn’t supported under plan9 until this issue is fixed.
+SFTP isn't supported under plan9 until this issue is fixed.
 
-Note that since SFTP isn’t HTTP based the following flags don’t work
+Note that since SFTP isn't HTTP based the following flags don't work
 with it: --dump-headers, --dump-bodies, --dump-auth
 
-Note that --timeout isn’t supported (but --contimeout is).
+Note that --timeout isn't supported (but --contimeout is).
 
 
 C14
 
 C14 is supported through the SFTP backend.
 
-See C14’s documentation
+See C14's documentation
 
 
 rsync.net
 
 rsync.net is supported through the SFTP backend.
 
-See rsync.net’s documentation of rclone examples.
+See rsync.net's documentation of rclone examples.
 
 
 SugarSync
@@ -21913,7 +22725,7 @@ This will guide you through an interactive setup process:
     d) Delete this remote
     y/e/d> y
 
-Note that the config asks for your email and password but doesn’t store
+Note that the config asks for your email and password but doesn't store
 them, it only uses them to get the initial token.
 
 Once configured you can then use rclone like this,
@@ -21922,7 +22734,7 @@ List directories (sync folders) in top level of your SugarSync
 
     rclone lsd remote:
 
-List all the files in your SugarSync folder “Test”
+List all the files in your SugarSync folder "Test"
 
     rclone ls remote:Test
 
@@ -21934,8 +22746,8 @@ Paths are specified as remote:path
 
 Paths may be as deep as required, eg remote:directory/subdirectory.
 
-NB you can’t create files in the top level folder you have to create a
-folder, which rclone will create as a “Sync Folder” with SugarSync.
+NB you can't create files in the top level folder you have to create a
+folder, which rclone will create as a "Sync Folder" with SugarSync.
 
 Modified time and hashes
 
@@ -21947,12 +22759,12 @@ Restricted filename characters
 
 SugarSync replaces the default restricted characters set except for DEL.
 
-Invalid UTF-8 bytes will also be replaced, as they can’t be used in XML
+Invalid UTF-8 bytes will also be replaced, as they can't be used in XML
 strings.
 
 Deleting files
 
-Deleted files will be moved to the “Deleted items” folder by default.
+Deleted files will be moved to the "Deleted items" folder by default.
 
 However you can supply the flag --sugarsync-hard-delete or set the
 config parameter hard_delete = true if you would like files to be
@@ -21962,40 +22774,40 @@ Standard Options
 
 Here are the standard options specific to sugarsync (Sugarsync).
 
-–sugarsync-app-id
+--sugarsync-app-id
 
 Sugarsync App ID.
 
-Leave blank to use rclone’s.
+Leave blank to use rclone's.
 
 -   Config: app_id
 -   Env Var: RCLONE_SUGARSYNC_APP_ID
 -   Type: string
 -   Default: ""
 
-–sugarsync-access-key-id
+--sugarsync-access-key-id
 
 Sugarsync Access Key ID.
 
-Leave blank to use rclone’s.
+Leave blank to use rclone's.
 
 -   Config: access_key_id
 -   Env Var: RCLONE_SUGARSYNC_ACCESS_KEY_ID
 -   Type: string
 -   Default: ""
 
-–sugarsync-private-access-key
+--sugarsync-private-access-key
 
 Sugarsync Private Access Key
 
-Leave blank to use rclone’s.
+Leave blank to use rclone's.
 
 -   Config: private_access_key
 -   Env Var: RCLONE_SUGARSYNC_PRIVATE_ACCESS_KEY
 -   Type: string
 -   Default: ""
 
-–sugarsync-hard-delete
+--sugarsync-hard-delete
 
 Permanently delete files if true otherwise put them in the deleted
 files.
@@ -22009,7 +22821,7 @@ Advanced Options
 
 Here are the advanced options specific to sugarsync (Sugarsync).
 
-–sugarsync-refresh-token
+--sugarsync-refresh-token
 
 Sugarsync refresh token
 
@@ -22020,7 +22832,7 @@ Leave blank normally, will be auto configured by rclone.
 -   Type: string
 -   Default: ""
 
-–sugarsync-authorization
+--sugarsync-authorization
 
 Sugarsync authorization
 
@@ -22031,7 +22843,7 @@ Leave blank normally, will be auto configured by rclone.
 -   Type: string
 -   Default: ""
 
-–sugarsync-authorization-expiry
+--sugarsync-authorization-expiry
 
 Sugarsync authorization expiry
 
@@ -22042,7 +22854,7 @@ Leave blank normally, will be auto configured by rclone.
 -   Type: string
 -   Default: ""
 
-–sugarsync-user
+--sugarsync-user
 
 Sugarsync user
 
@@ -22053,7 +22865,7 @@ Leave blank normally, will be auto configured by rclone.
 -   Type: string
 -   Default: ""
 
-–sugarsync-root-id
+--sugarsync-root-id
 
 Sugarsync root id
 
@@ -22064,7 +22876,7 @@ Leave blank normally, will be auto configured by rclone.
 -   Type: string
 -   Default: ""
 
-–sugarsync-deleted-id
+--sugarsync-deleted-id
 
 Sugarsync deleted folder id
 
@@ -22075,7 +22887,7 @@ Leave blank normally, will be auto configured by rclone.
 -   Type: string
 -   Default: ""
 
-–sugarsync-encoding
+--sugarsync-encoding
 
 This sets the encoding for the backend.
 
@@ -22212,7 +23024,7 @@ Once configured you can then use rclone like this.
 
 Create a new bucket
 
-Use the mkdir command to create new bucket, e.g. bucket.
+Use the mkdir command to create new bucket, e.g. bucket.
 
     rclone mkdir remote:bucket
 
@@ -22241,7 +23053,7 @@ Use the copy command to upload an object.
     rclone copy --progress /home/local/directory/file.ext remote:bucket/path/to/dir/
 
 The --progress flag is for displaying progress information. Remove it if
-you don’t need this information.
+you don't need this information.
 
 Use a folder in the local path to upload all its objects.
 
@@ -22272,7 +23084,7 @@ Use the copy command to download an object.
     rclone copy --progress remote:bucket/path/to/dir/file.ext /home/local/directory/
 
 The --progress flag is for displaying progress information. Remove it if
-you don’t need this information.
+you don't need this information.
 
 Use a folder in the remote path to download all its objects.
 
@@ -22300,47 +23112,47 @@ Sync two Locations
 Use the sync command to sync the source to the destination, changing the
 destination only, deleting any excess files.
 
-    rclone sync --progress /home/local/directory/ remote:bucket/path/to/dir/
+    rclone sync -i --progress /home/local/directory/ remote:bucket/path/to/dir/
 
 The --progress flag is for displaying progress information. Remove it if
-you don’t need this information.
+you don't need this information.
 
 Since this can cause data loss, test first with the --dry-run flag to
 see exactly what would be copied and deleted.
 
 The sync can be done also from Tardigrade to the local file system.
 
-    rclone sync --progress remote:bucket/path/to/dir/ /home/local/directory/
+    rclone sync -i --progress remote:bucket/path/to/dir/ /home/local/directory/
 
 Or between two Tardigrade buckets.
 
-    rclone sync --progress remote-us:bucket/path/to/dir/ remote-europe:bucket/path/to/dir/
+    rclone sync -i --progress remote-us:bucket/path/to/dir/ remote-europe:bucket/path/to/dir/
 
 Or even between another cloud storage and Tardigrade.
 
-    rclone sync --progress s3:bucket/path/to/dir/ tardigrade:bucket/path/to/dir/
+    rclone sync -i --progress s3:bucket/path/to/dir/ tardigrade:bucket/path/to/dir/
 
 Standard Options
 
 Here are the standard options specific to tardigrade (Tardigrade
 Decentralized Cloud Storage).
 
-–tardigrade-provider
+--tardigrade-provider
 
 Choose an authentication method.
 
 -   Config: provider
 -   Env Var: RCLONE_TARDIGRADE_PROVIDER
 -   Type: string
--   Default: “existing”
+-   Default: "existing"
 -   Examples:
-    -   “existing”
+    -   "existing"
         -   Use an existing access grant.
-    -   “new”
+    -   "new"
         -   Create a new access grant from satellite address, API key,
             and passphrase.
 
-–tardigrade-access-grant
+--tardigrade-access-grant
 
 Access Grant.
 
@@ -22349,7 +23161,7 @@ Access Grant.
 -   Type: string
 -   Default: ""
 
-–tardigrade-satellite-address
+--tardigrade-satellite-address
 
 Satellite Address. Custom satellite address should match the format:
 <nodeid>@<address>:<port>.
@@ -22357,16 +23169,16 @@ Satellite Address. Custom satellite address should match the format:
 -   Config: satellite_address
 -   Env Var: RCLONE_TARDIGRADE_SATELLITE_ADDRESS
 -   Type: string
--   Default: “us-central-1.tardigrade.io”
+-   Default: "us-central-1.tardigrade.io"
 -   Examples:
-    -   “us-central-1.tardigrade.io”
+    -   "us-central-1.tardigrade.io"
         -   US Central 1
-    -   “europe-west-1.tardigrade.io”
+    -   "europe-west-1.tardigrade.io"
         -   Europe West 1
-    -   “asia-east-1.tardigrade.io”
+    -   "asia-east-1.tardigrade.io"
         -   Asia East 1
 
-–tardigrade-api-key
+--tardigrade-api-key
 
 API Key.
 
@@ -22375,7 +23187,7 @@ API Key.
 -   Type: string
 -   Default: ""
 
-–tardigrade-passphrase
+--tardigrade-passphrase
 
 Encryption Passphrase. To access existing objects enter passphrase used
 for uploading.
@@ -22634,44 +23446,44 @@ Standard Options
 Here are the standard options specific to union (Union merges the
 contents of several upstream fs).
 
-–union-upstreams
+--union-upstreams
 
-List of space separated upstreams. Can be ‘upstreama:test/dir
-upstreamb:’, ‘“upstreama:test/space:ro dir” upstreamb:’, etc.
+List of space separated upstreams. Can be 'upstreama:test/dir
+upstreamb:', '"upstreama:test/space:ro dir" upstreamb:', etc.
 
 -   Config: upstreams
 -   Env Var: RCLONE_UNION_UPSTREAMS
 -   Type: string
 -   Default: ""
 
-–union-action-policy
+--union-action-policy
 
 Policy to choose upstream on ACTION category.
 
 -   Config: action_policy
 -   Env Var: RCLONE_UNION_ACTION_POLICY
 -   Type: string
--   Default: “epall”
+-   Default: "epall"
 
-–union-create-policy
+--union-create-policy
 
 Policy to choose upstream on CREATE category.
 
 -   Config: create_policy
 -   Env Var: RCLONE_UNION_CREATE_POLICY
 -   Type: string
--   Default: “epmfs”
+-   Default: "epmfs"
 
-–union-search-policy
+--union-search-policy
 
 Policy to choose upstream on SEARCH category.
 
 -   Config: search_policy
 -   Env Var: RCLONE_UNION_SEARCH_POLICY
 -   Type: string
--   Default: “ff”
+-   Default: "ff"
 
-–union-cache-time
+--union-cache-time
 
 Cache time of usage and free space (in seconds). This option is only
 useful when a path preserving policy is used.
@@ -22783,7 +23595,7 @@ Standard Options
 
 Here are the standard options specific to webdav (Webdav).
 
-–webdav-url
+--webdav-url
 
 URL of http host to connect to
 
@@ -22792,10 +23604,10 @@ URL of http host to connect to
 -   Type: string
 -   Default: ""
 -   Examples:
-    -   “https://example.com”
+    -   "https://example.com"
         -   Connect to example.com
 
-–webdav-vendor
+--webdav-vendor
 
 Name of the Webdav site/service/software you are using
 
@@ -22804,16 +23616,16 @@ Name of the Webdav site/service/software you are using
 -   Type: string
 -   Default: ""
 -   Examples:
-    -   “nextcloud”
+    -   "nextcloud"
         -   Nextcloud
-    -   “owncloud”
+    -   "owncloud"
         -   Owncloud
-    -   “sharepoint”
+    -   "sharepoint"
         -   Sharepoint
-    -   “other”
+    -   "other"
         -   Other site/service or software
 
-–webdav-user
+--webdav-user
 
 User name
 
@@ -22822,16 +23634,18 @@ User name
 -   Type: string
 -   Default: ""
 
-–webdav-pass
+--webdav-pass
 
 Password.
 
+NB Input to this must be obscured - see rclone obscure.
+
 -   Config: pass
 -   Env Var: RCLONE_WEBDAV_PASS
 -   Type: string
 -   Default: ""
 
-–webdav-bearer-token
+--webdav-bearer-token
 
 Bearer token instead of user/pass (eg a Macaroon)
 
@@ -22844,7 +23658,7 @@ Advanced Options
 
 Here are the advanced options specific to webdav (Webdav).
 
-–webdav-bearer-token-command
+--webdav-bearer-token-command
 
 Command to run to get a bearer token
 
@@ -22879,19 +23693,19 @@ Office365 Education Accounts. This feature is only needed for a few of
 these Accounts, mostly Office365 Education ones. These accounts are
 sometimes not verified by the domain owner github#1975
 
-This means that these accounts can’t be added using the official API
-(other Accounts should work with the “onedrive” option). However, it is
+This means that these accounts can't be added using the official API
+(other Accounts should work with the "onedrive" option). However, it is
 possible to access them using webdav.
 
 To use a sharepoint remote with rclone, add it like this: First, you
-need to get your remote’s URL:
+need to get your remote's URL:
 
 -   Go here to open your OneDrive or to sign in
 -   Now take a look at your address bar, the URL should look like this:
     https://[YOUR-DOMAIN]-my.sharepoint.com/personal/[YOUR-EMAIL]/_layouts/15/onedrive.aspx
 
-You’ll only need this URL up to the email address. After that, you’ll
-most likely want to add “/Documents”. That subdirectory contains the
+You'll only need this URL up to the email address. After that, you'll
+most likely want to add "/Documents". That subdirectory contains the
 actual data stored on your OneDrive.
 
 Add the remote to rclone like this: Configure the url as
@@ -22912,12 +23726,12 @@ Your config file should look like this:
 Required Flags for SharePoint
 
 As SharePoint does some special things with uploaded documents, you
-won’t be able to use the documents size or the documents hash to compare
+won't be able to use the documents size or the documents hash to compare
 if a file has been changed since the upload / which file is newer.
 
 For Rclone calls copying files (especially Office files such as .docx,
 .xlsx, etc.) from/to SharePoint (like copy, sync, etc.), you should
-append these flags to ensure Rclone uses the “Last Modified” datetime
+append these flags to ensure Rclone uses the "Last Modified" datetime
 property to compare your documents:
 
     --ignore-size --ignore-checksum --update
@@ -22930,7 +23744,7 @@ users to authenticate with username and password (BASIC), X.509,
 Kerberos, and various bearer tokens, including Macaroons and
 OpenID-Connect access tokens.
 
-Configure as normal using the other type. Don’t enter a username or
+Configure as normal using the other type. Don't enter a username or
 password, instead enter your Macaroon as the bearer_token.
 
 The config will end up looking something like this.
@@ -22975,7 +23789,7 @@ Provider are provided in the oidc-agent documentation.
 The rclone bearer_token_command configuration option is used to fetch
 the access token from oidc-agent.
 
-Configure as a normal WebDAV endpoint, using the ‘other’ vendor, leaving
+Configure as a normal WebDAV endpoint, using the 'other' vendor, leaving
 the username and password empty. When prompted, choose to edit the
 advanced config and enter the command to get a bearer token (e.g.,
 oidc-agent XDC).
@@ -23064,7 +23878,7 @@ List the contents of a directory
 Sync /home/local/directory to the remote path, deleting any excess files
 in the path.
 
-    rclone sync /home/local/directory remote:directory
+    rclone sync -i /home/local/directory remote:directory
 
 Yandex paths may be as deep as required, eg
 remote:directory/subdirectory.
@@ -23093,7 +23907,7 @@ Restricted filename characters
 
 The default restricted characters set are replaced.
 
-Invalid UTF-8 bytes will also be replaced, as they can’t be used in JSON
+Invalid UTF-8 bytes will also be replaced, as they can't be used in JSON
 strings.
 
 Limitations
@@ -23103,7 +23917,7 @@ increase the --timeout parameter. This is because Yandex pauses (perhaps
 to calculate the MD5SUM for the entire file) before returning
 confirmation that the file has been uploaded. The default handling of
 timeouts in rclone is to assume a 5 minute pause is an error and close
-the connection - you’ll see net/http: timeout awaiting response headers
+the connection - you'll see net/http: timeout awaiting response headers
 errors in the logs if this is happening. Setting the timeout to twice
 the max size of file in GB should be enough, so if you want to upload a
 30GB file set a timeout of 2 * 30 = 60m, that is --timeout 60m.
@@ -23112,18 +23926,18 @@ Standard Options
 
 Here are the standard options specific to yandex (Yandex Disk).
 
-–yandex-client-id
+--yandex-client-id
 
-Yandex Client Id Leave blank normally.
+OAuth Client Id Leave blank normally.
 
 -   Config: client_id
 -   Env Var: RCLONE_YANDEX_CLIENT_ID
 -   Type: string
 -   Default: ""
 
-–yandex-client-secret
+--yandex-client-secret
 
-Yandex Client Secret Leave blank normally.
+OAuth Client Secret Leave blank normally.
 
 -   Config: client_secret
 -   Env Var: RCLONE_YANDEX_CLIENT_SECRET
@@ -23134,18 +23948,34 @@ Advanced Options
 
 Here are the advanced options specific to yandex (Yandex Disk).
 
-–yandex-unlink
+--yandex-token
 
-Remove existing public link to file/folder with link command rather than
-creating. Default is false, meaning link command will create or retrieve
-public link.
+OAuth Access Token as a JSON blob.
 
--   Config: unlink
--   Env Var: RCLONE_YANDEX_UNLINK
--   Type: bool
--   Default: false
+-   Config: token
+-   Env Var: RCLONE_YANDEX_TOKEN
+-   Type: string
+-   Default: ""
 
-–yandex-encoding
+--yandex-auth-url
+
+Auth server URL. Leave blank to use the provider defaults.
+
+-   Config: auth_url
+-   Env Var: RCLONE_YANDEX_AUTH_URL
+-   Type: string
+-   Default: ""
+
+--yandex-token-url
+
+Token server url. Leave blank to use the provider defaults.
+
+-   Config: token_url
+-   Env Var: RCLONE_YANDEX_TOKEN_URL
+-   Type: string
+-   Default: ""
+
+--yandex-encoding
 
 This sets the encoding for the backend.
 
@@ -23162,7 +23992,7 @@ Local Filesystem
 Local paths are specified as normal filesystem paths, eg
 /path/to/wherever, so
 
-    rclone sync /home/source /tmp/destination
+    rclone sync -i /home/source /tmp/destination
 
 Will sync /home/source to /tmp/destination
 
@@ -23184,7 +24014,7 @@ There is a bit more uncertainty in the Linux world, but new
 distributions will have UTF-8 encoded files names. If you are using an
 old Linux filesystem with non UTF-8 file names (eg latin1) then you can
 use the convmv tool to convert the filesystem to UTF-8. This tool is
-available in most distributions’ package managers.
+available in most distributions' package managers.
 
 If an invalid (non-UTF8) filename is read, the invalid characters will
 be replaced with a quoted representation of the invalid bytes. The name
@@ -23258,7 +24088,7 @@ These only get replaced if they are the last character in the name:
   SP           0x20         ␠
   .            0x2E        ．
 
-Invalid UTF-8 bytes will also be replaced, as they can’t be converted to
+Invalid UTF-8 bytes will also be replaced, as they can't be converted to
 UTF-16.
 
 Long paths on Windows
@@ -23328,13 +24158,13 @@ and
             6 b/two
             6 b/one
 
-–links, -l
+--links, -l
 
 Normally rclone will ignore symlinks or junction points (which behave
 like symlinks under Windows).
 
 If you supply this flag then rclone will copy symbolic links from the
-local storage, and store them as text files, with a ‘.rclonelink’ suffix
+local storage, and store them as text files, with a '.rclonelink' suffix
 in the remote storage.
 
 The text file will contain the target of the symbolic link (see
@@ -23349,11 +24179,11 @@ For example, supposing you have a directory structure like this
     ├── file1 -> ./file4
     └── file2 -> /home/user/file3
 
-Copying the entire directory with ‘-l’
+Copying the entire directory with '-l'
 
     $ rclone copyto -l /tmp/a/file1 remote:/tmp/a/
 
-The remote files are created with a ‘.rclonelink’ suffix
+The remote files are created with a '.rclonelink' suffix
 
     $ rclone ls remote:/tmp/a
            5 file1.rclonelink
@@ -23367,7 +24197,7 @@ The remote files will contain the target of the symbolic links
     $ rclone cat remote:/tmp/a/file2.rclonelink
     /home/user/file3
 
-Copying them back with ‘-l’
+Copying them back with '-l'
 
     $ rclone copyto -l remote:/tmp/a/ /tmp/b/
 
@@ -23376,7 +24206,7 @@ Copying them back with ‘-l’
     ├── file1 -> ./file4
     └── file2 -> /home/user/file3
 
-However, if copied back without ‘-l’
+However, if copied back without '-l'
 
     $ rclone copyto remote:/tmp/a/ /tmp/b/
 
@@ -23387,7 +24217,7 @@ However, if copied back without ‘-l’
 
 Note that this flag is incompatible with -copy-links / -L.
 
-Restricting filesystems with –one-file-system
+Restricting filesystems with --one-file-system
 
 Normally rclone will recurse through filesystems as mounted.
 
@@ -23422,13 +24252,13 @@ NB Rclone (like most unix tools such as du, rsync and tar) treats a bind
 mount to the same device as being on the same filesystem.
 
 NB This flag is only available on Unix based systems. On systems where
-it isn’t supported (eg Windows) it will be ignored.
+it isn't supported (eg Windows) it will be ignored.
 
 Standard Options
 
 Here are the standard options specific to local (Local Disk).
 
-–local-nounc
+--local-nounc
 
 Disable UNC (long path names) conversion on Windows
 
@@ -23437,14 +24267,14 @@ Disable UNC (long path names) conversion on Windows
 -   Type: string
 -   Default: ""
 -   Examples:
-    -   “true”
+    -   "true"
         -   Disables long file names
 
 Advanced Options
 
 Here are the advanced options specific to local (Local Disk).
 
-–copy-links / -L
+--copy-links / -L
 
 Follow symlinks and copy the pointed to item.
 
@@ -23453,18 +24283,18 @@ Follow symlinks and copy the pointed to item.
 -   Type: bool
 -   Default: false
 
-–links / -l
+--links / -l
 
-Translate symlinks to/from regular files with a ‘.rclonelink’ extension
+Translate symlinks to/from regular files with a '.rclonelink' extension
 
 -   Config: links
 -   Env Var: RCLONE_LOCAL_LINKS
 -   Type: bool
 -   Default: false
 
-–skip-links
+--skip-links
 
-Don’t warn about skipped symlinks. This flag disables warning messages
+Don't warn about skipped symlinks. This flag disables warning messages
 on skipped symlinks or junction points, as you explicitly acknowledge
 that they should be skipped.
 
@@ -23473,9 +24303,9 @@ that they should be skipped.
 -   Type: bool
 -   Default: false
 
-–local-no-unicode-normalization
+--local-no-unicode-normalization
 
-Don’t apply unicode normalization to paths and filenames (Deprecated)
+Don't apply unicode normalization to paths and filenames (Deprecated)
 
 This flag is deprecated now. Rclone no longer normalizes unicode file
 names, but it compares them with unicode normalization in the sync
@@ -23486,32 +24316,47 @@ routine instead.
 -   Type: bool
 -   Default: false
 
-–local-no-check-updated
+--local-no-check-updated
 
-Don’t check to see if the files change during upload
+Don't check to see if the files change during upload
 
 Normally rclone checks the size and modification time of files as they
-are being uploaded and aborts with a message which starts “can’t copy -
-source file is being updated” if the file changes during upload.
+are being uploaded and aborts with a message which starts "can't copy -
+source file is being updated" if the file changes during upload.
 
 However on some file systems this modification time check may fail (eg
 Glusterfs #2206) so this check can be disabled with this flag.
 
+If this flag is set, rclone will use its best efforts to transfer a file
+which is being updated. If the file is only having things appended to it
+(eg a log) then rclone will transfer the log file with the size it had
+the first time rclone saw it.
+
+If the file is being modified throughout (not just appended to) then the
+transfer may fail with a hash check failure.
+
+In detail, once the file has had stat() called on it for the first time
+we:
+
+-   Only transfer the size that stat gave
+-   Only checksum the size that stat gave
+-   Don't update the stat info for the file
+
 -   Config: no_check_updated
 -   Env Var: RCLONE_LOCAL_NO_CHECK_UPDATED
 -   Type: bool
 -   Default: false
 
-–one-file-system / -x
+--one-file-system / -x
 
-Don’t cross filesystem boundaries (unix/macOS only).
+Don't cross filesystem boundaries (unix/macOS only).
 
 -   Config: one_file_system
 -   Env Var: RCLONE_LOCAL_ONE_FILE_SYSTEM
 -   Type: bool
 -   Default: false
 
-–local-case-sensitive
+--local-case-sensitive
 
 Force the filesystem to report itself as case sensitive.
 
@@ -23524,7 +24369,7 @@ override the default choice.
 -   Type: bool
 -   Default: false
 
-–local-case-insensitive
+--local-case-insensitive
 
 Force the filesystem to report itself as case insensitive
 
@@ -23537,7 +24382,7 @@ override the default choice.
 -   Type: bool
 -   Default: false
 
-–local-no-sparse
+--local-no-sparse
 
 Disable sparse files for multi-thread downloads
 
@@ -23551,7 +24396,22 @@ disk fragmentation and can be slow to work with.
 -   Type: bool
 -   Default: false
 
-–local-encoding
+--local-no-set-modtime
+
+Disable setting modtime
+
+Normally rclone updates modification time of files after they are done
+uploading. This can cause permissions issues on Linux platforms when the
+user rclone is running as does not own the file uploaded, such as when
+copying to a CIFS mount owned by another user. If this option is
+enabled, rclone will no longer update the modtime after copying a file.
+
+-   Config: no_set_modtime
+-   Env Var: RCLONE_LOCAL_NO_SET_MODTIME
+-   Type: bool
+-   Default: false
+
+--local-encoding
 
 This sets the encoding for the backend.
 
@@ -23572,7 +24432,7 @@ Run them with
 
 The help below will explain what arguments each command takes.
 
-See the “rclone backend” command for more info on how to pass options
+See the "rclone backend" command for more info on how to pass options
 and arguments.
 
 These can be run on a running backend using the rc command
@@ -23589,14 +24449,404 @@ output.
 
 Options:
 
--   “echo”: echo the input arguments
--   “error”: return an error based on option value
+-   "echo": echo the input arguments
+-   "error": return an error based on option value
 
 
 
 CHANGELOG
 
 
+v1.53.0 - 2020-09-02
+
+See commits
+
+-   New Features
+    -   The VFS layer was heavily reworked for this release - see below
+        for more details
+    -   Interactive mode -i/--interactive for destructive operations
+        (fishbullet)
+    -   Add --bwlimit-file flag to limit speeds of individual file
+        transfers (Nick Craig-Wood)
+    -   Transfers are sorted by start time in the stats and progress
+        output (Max Sum)
+    -   Make sure backends expand ~ and environment vars in file names
+        they use (Nick Craig-Wood)
+    -   Add --refresh-times flag to set modtimes on hashless backends
+        (Nick Craig-Wood)
+    -   build
+        -   Remove vendor directory in favour of Go modules (Nick
+            Craig-Wood)
+        -   Build with go1.15.x by default (Nick Craig-Wood)
+        -   Drop macOS 386 build as it is no longer supported by go1.15
+            (Nick Craig-Wood)
+        -   Add ARMv7 to the supported builds (Nick Craig-Wood)
+        -   Enable rclone cmount on macOS (Nick Craig-Wood)
+        -   Make rclone build with gccgo (Nick Craig-Wood)
+        -   Make rclone build with wasm (Nick Craig-Wood)
+        -   Change beta numbering to be semver compatible (Nick
+            Craig-Wood)
+        -   Add file properties and icon to Windows executable
+            (albertony)
+        -   Add experimental interface for integrating rclone into
+            browsers (Nick Craig-Wood)
+    -   lib: Add file name compression (Klaus Post)
+    -   rc
+        -   Allow installation and use of plugins and test plugins with
+            rclone-webui (Chaitanya Bankanhal)
+        -   Add reverse proxy pluginsHandler for serving plugins
+            (Chaitanya Bankanhal)
+        -   Add mount/listmounts option for listing current mounts
+            (Chaitanya Bankanhal)
+        -   Add operations/uploadfile to upload a file through rc using
+            encoding multipart/form-data (Chaitanya Bankanhal)
+        -   Add core/copmmand to execute rclone terminal commands.
+            (Chaitanya Bankanhal)
+    -   rclone check
+        -   Add reporting of filenames for same/missing/changed (Nick
+            Craig-Wood)
+        -   Make check command obey --dry-run/-i/--interactive (Nick
+            Craig-Wood)
+        -   Make check do --checkers files concurrently (Nick
+            Craig-Wood)
+        -   Retry downloads if they fail when using the --download flag
+            (Nick Craig-Wood)
+        -   Make it show stats by default (Nick Craig-Wood)
+    -   rclone obscure: Allow obscure command to accept password on
+        STDIN (David Ibarra)
+    -   rclone config
+        -   Set RCLONE_CONFIG_DIR for use in config files and
+            subprocesses (Nick Craig-Wood)
+        -   Reject remote names starting with a dash. (jtagcat)
+    -   rclone cryptcheck: Add reporting of filenames for
+        same/missing/changed (Nick Craig-Wood)
+    -   rclone dedupe: Make it obey the --size-only flag for duplicate
+        detection (Nick Craig-Wood)
+    -   rclone link: Add --expire and --unlink flags (Roman Kredentser)
+    -   rclone mkdir: Warn when using mkdir on remotes which can't have
+        empty directories (Nick Craig-Wood)
+    -   rclone rc: Allow JSON parameters to simplify command line usage
+        (Nick Craig-Wood)
+    -   rclone serve ftp
+        -   Don't compile on < go1.13 after dependency update (Nick
+            Craig-Wood)
+        -   Add error message if auth proxy fails (Nick Craig-Wood)
+        -   Use refactored goftp.io/server library for binary shrink
+            (Nick Craig-Wood)
+    -   rclone serve restic: Expose interfaces so that rclone can be
+        used as a library from within restic (Jack)
+    -   rclone sync: Add --track-renames-strategy leaf (Nick Craig-Wood)
+    -   rclone touch: Add ability to set nanosecond resolution times
+        (Nick Craig-Wood)
+    -   rclone tree: Remove -i shorthand for --noindent as it conflicts
+        with -i/--interactive (Nick Craig-Wood)
+-   Bug Fixes
+    -   accounting
+        -   Fix documentation for speed/speedAvg (Nick Craig-Wood)
+        -   Fix elapsed time not show actual time since beginning
+            (Chaitanya Bankanhal)
+        -   Fix deadlock in stats printing (Nick Craig-Wood)
+    -   build
+        -   Fix file handle leak in GitHub release tool (Garrett Squire)
+    -   rclone check: Fix successful retries with --download counting
+        errors (Nick Craig-Wood)
+    -   rclone dedupe: Fix logging to be easier to understand (Nick
+        Craig-Wood)
+-   Mount
+    -   Warn macOS users that mount implementation is changing (Nick
+        Craig-Wood)
+        -   to test the new implementation use rclone cmount instead of
+            rclone mount
+        -   this is because the library rclone uses has dropped macOS
+            support
+    -   rc interface
+        -   Add call for unmount all (Chaitanya Bankanhal)
+        -   Make mount/mount remote control take vfsOpt option (Nick
+            Craig-Wood)
+        -   Add mountOpt to mount/mount (Nick Craig-Wood)
+        -   Add VFS and Mount options to mount/listmounts (Nick
+            Craig-Wood)
+    -   Catch panics in cgofuse initialization and turn into error
+        messages (Nick Craig-Wood)
+    -   Always supply stat information in Readdir (Nick Craig-Wood)
+    -   Add support for reading unknown length files using direct IO
+        (Windows) (Nick Craig-Wood)
+    -   Fix On Windows don't add -o uid/gid=-1 if user supplies
+        -o uid/gid. (Nick Craig-Wood)
+    -   Fix macOS losing directory contents in cmount (Nick Craig-Wood)
+    -   Fix volume name broken in recent refactor (Nick Craig-Wood)
+-   VFS
+    -   Implement partial reads for --vfs-cache-mode full (Nick
+        Craig-Wood)
+    -   Add --vfs-writeback option to delay writes back to cloud storage
+        (Nick Craig-Wood)
+    -   Add --vfs-read-ahead parameter for use with
+        --vfs-cache-mode full (Nick Craig-Wood)
+    -   Restart pending uploads on restart of the cache (Nick
+        Craig-Wood)
+    -   Support synchronous cache space recovery upon ENOSPC (Leo Luan)
+    -   Allow ReadAt and WriteAt to run concurrently with themselves
+        (Nick Craig-Wood)
+    -   Change modtime of file before upload to current (Rob Calistri)
+    -   Recommend --vfs-cache-modes writes on backends which can't
+        stream (Nick Craig-Wood)
+    -   Add an optional fs parameter to vfs rc methods (Nick Craig-Wood)
+    -   Fix errors when using > 260 char files in the cache in Windows
+        (Nick Craig-Wood)
+    -   Fix renaming of items while they are being uploaded (Nick
+        Craig-Wood)
+    -   Fix very high load caused by slow directory listings (Nick
+        Craig-Wood)
+    -   Fix renamed files not being uploaded with
+        --vfs-cache-mode minimal (Nick Craig-Wood)
+    -   Fix directory locking caused by slow directory listings (Nick
+        Craig-Wood)
+    -   Fix saving from chrome without --vfs-cache-mode writes (Nick
+        Craig-Wood)
+-   Local
+    -   Add --local-no-updated to provide a consistent view of changing
+        objects (Nick Craig-Wood)
+    -   Add --local-no-set-modtime option to prevent modtime changes
+        (tyhuber1)
+    -   Fix race conditions updating and reading Object metadata (Nick
+        Craig-Wood)
+-   Cache
+    -   Make any created backends be cached to fix rc problems (Nick
+        Craig-Wood)
+    -   Fix dedupe on caches wrapping drives (Nick Craig-Wood)
+-   Crypt
+    -   Add --crypt-server-side-across-configs flag (Nick Craig-Wood)
+    -   Make any created backends be cached to fix rc problems (Nick
+        Craig-Wood)
+-   Alias
+    -   Make any created backends be cached to fix rc problems (Nick
+        Craig-Wood)
+-   Azure Blob
+    -   Don't compile on < go1.13 after dependency update (Nick
+        Craig-Wood)
+-   B2
+    -   Implement server side copy for files > 5GB (Nick Craig-Wood)
+    -   Cancel in progress multipart uploads and copies on rclone exit
+        (Nick Craig-Wood)
+    -   Note that b2's encoding now allows  but rclone's hasn't changed
+        (Nick Craig-Wood)
+    -   Fix transfers when using download_url (Nick Craig-Wood)
+-   Box
+    -   Implement rclone cleanup (buengese)
+    -   Cancel in progress multipart uploads and copies on rclone exit
+        (Nick Craig-Wood)
+    -   Allow authentication with access token (David)
+-   Chunker
+    -   Make any created backends be cached to fix rc problems (Nick
+        Craig-Wood)
+-   Drive
+    -   Add rclone backend drives to list shared drives (teamdrives)
+        (Nick Craig-Wood)
+    -   Implement rclone backend untrash (Nick Craig-Wood)
+    -   Work around drive bug which didn't set modtime of copied docs
+        (Nick Craig-Wood)
+    -   Added --drive-starred-only to only show starred files (Jay
+        McEntire)
+    -   Deprecate --drive-alternate-export as it is no longer needed
+        (themylogin)
+    -   Fix duplication of Google docs on server side copy (Nick
+        Craig-Wood)
+    -   Fix "panic: send on closed channel" when recycling dir entries
+        (Nick Craig-Wood)
+-   Dropbox
+    -   Add copyright detector info in limitations section in the docs
+        (Alex Guerrero)
+    -   Fix rclone link by removing expires parameter (Nick Craig-Wood)
+-   Fichier
+    -   Detect Flood detected: IP Locked error and sleep for 30s (Nick
+        Craig-Wood)
+-   FTP
+    -   Add explicit TLS support (Heiko Bornholdt)
+    -   Add support for --dump bodies and --dump auth for debugging
+        (Nick Craig-Wood)
+    -   Fix interoperation with pure-ftpd (Nick Craig-Wood)
+-   Google Cloud Storage
+    -   Add support for anonymous access (Kai Lüke)
+-   Jottacloud
+    -   Bring back legacy authentification for use with whitelabel
+        versions (buengese)
+    -   Switch to new api root - also implement a very ugly workaround
+        for the DirMove failures (buengese)
+-   Onedrive
+    -   Rework cancel of multipart uploads on rclone exit (Nick
+        Craig-Wood)
+    -   Implement rclone cleanup (Nick Craig-Wood)
+    -   Add --onedrive-no-versions flag to remove old versions (Nick
+        Craig-Wood)
+-   Pcloud
+    -   Implement rclone link for public link creation (buengese)
+-   Qingstor
+    -   Cancel in progress multipart uploads on rclone exit (Nick
+        Craig-Wood)
+-   S3
+    -   Preserve metadata when doing multipart copy (Nick Craig-Wood)
+    -   Cancel in progress multipart uploads and copies on rclone exit
+        (Nick Craig-Wood)
+    -   Add rclone link for public link sharing (Roman Kredentser)
+    -   Add rclone backend restore command to restore objects from
+        GLACIER (Nick Craig-Wood)
+    -   Add rclone cleanup and rclone backend cleanup to clean
+        unfinished multipart uploads (Nick Craig-Wood)
+    -   Add rclone backend list-multipart-uploads to list unfinished
+        multipart uploads (Nick Craig-Wood)
+    -   Add --s3-max-upload-parts support (Kamil Trzciński)
+    -   Add --s3-no-check-bucket for minimising rclone transactions and
+        perms (Nick Craig-Wood)
+    -   Add --s3-profile and --s3-shared-credentials-file options (Nick
+        Craig-Wood)
+    -   Use regional s3 us-east-1 endpoint (David)
+    -   Add Scaleway provider (Vincent Feltz)
+    -   Update IBM COS endpoints (Egor Margineanu)
+    -   Reduce the default --s3-copy-cutoff to < 5GB for Backblaze S3
+        compatibility (Nick Craig-Wood)
+    -   Fix detection of bucket existing (Nick Craig-Wood)
+-   SFTP
+    -   Use the absolute path instead of the relative path for listing
+        for improved compatibility (Nick Craig-Wood)
+    -   Add --sftp-subsystem and --sftp-server-command options (aus)
+-   Swift
+    -   Fix dangling large objects breaking the listing (Nick
+        Craig-Wood)
+    -   Fix purge not deleting directory markers (Nick Craig-Wood)
+    -   Fix update multipart object removing all of its own parts (Nick
+        Craig-Wood)
+    -   Fix missing hash from object returned from upload (Nick
+        Craig-Wood)
+-   Tardigrade
+    -   Upgrade to uplink v1.2.0 (Kaloyan Raev)
+-   Union
+    -   Fix writing with the all policy (Nick Craig-Wood)
+-   WebDAV
+    -   Fix directory creation with 4shared (Nick Craig-Wood)
+
+
+v1.52.3 - 2020-08-07
+
+See commits
+
+-   Bug Fixes
+    -   docs
+        -   Disable smart typography (eg en-dash) in MANUAL.* and man
+            page (Nick Craig-Wood)
+        -   Update install.md to reflect minimum Go version (Evan
+            Harris)
+        -   Update install from source instructions (Nick Craig-Wood)
+        -   make_manual: Support SOURCE_DATE_EPOCH (Morten Linderud)
+    -   log: Fix --use-json-log going to stderr not --log-file on
+        Windows (Nick Craig-Wood)
+    -   serve dlna: Fix file list on Samsung Series 6+ TVs (Matteo
+        Pietro Dazzi)
+    -   sync: Fix deadlock with --track-renames-strategy modtime (Nick
+        Craig-Wood)
+-   Cache
+    -   Fix moveto/copyto remote:file remote:file2 (Nick Craig-Wood)
+-   Drive
+    -   Stop using root_folder_id as a cache (Nick Craig-Wood)
+    -   Make dangling shortcuts appear in listings (Nick Craig-Wood)
+    -   Drop "Disabling ListR" messages down to debug (Nick Craig-Wood)
+    -   Workaround and policy for Google Drive API (Dmitry Ustalov)
+-   FTP
+    -   Add note to docs about home vs root directory selection (Nick
+        Craig-Wood)
+-   Onedrive
+    -   Fix reverting to Copy when Move would have worked (Nick
+        Craig-Wood)
+    -   Avoid comma rendered in URL in onedrive.md (Kevin)
+-   Pcloud
+    -   Fix oauth on European region "eapi.pcloud.com" (Nick Craig-Wood)
+-   S3
+    -   Fix bucket Region auto detection when Region unset in config
+        (Nick Craig-Wood)
+
+
+v1.52.2 - 2020-06-24
+
+See commits
+
+-   Bug Fixes
+    -   build
+        -   Fix docker release build action (Nick Craig-Wood)
+        -   Fix custom timezone in Docker image (NoLooseEnds)
+    -   check: Fix misleading message which printed errors instead of
+        differences (Nick Craig-Wood)
+    -   errors: Add WSAECONNREFUSED and more to the list of retriable
+        Windows errors (Nick Craig-Wood)
+    -   rcd: Fix incorrect prometheus metrics (Gary Kim)
+    -   serve restic: Fix flags so they use environment variables (Nick
+        Craig-Wood)
+    -   serve webdav: Fix flags so they use environment variables (Nick
+        Craig-Wood)
+    -   sync: Fix --track-renames-strategy modtime (Nick Craig-Wood)
+-   Drive
+    -   Fix not being able to delete a directory with a trashed shortcut
+        (Nick Craig-Wood)
+    -   Fix creating a directory inside a shortcut (Nick Craig-Wood)
+    -   Fix --drive-impersonate with cached root_folder_id (Nick
+        Craig-Wood)
+-   SFTP
+    -   Fix SSH key PEM loading (Zac Rubin)
+-   Swift
+    -   Speed up deletes by not retrying segment container deletes (Nick
+        Craig-Wood)
+-   Tardigrade
+    -   Upgrade to uplink v1.1.1 (Caleb Case)
+-   WebDAV
+    -   Fix free/used display for rclone about/df for certain backends
+        (Nick Craig-Wood)
+
+
+v1.52.1 - 2020-06-10
+
+See commits
+
+-   Bug Fixes
+    -   lib/file: Fix SetSparse on Windows 7 which fixes downloads of
+        files > 250MB (Nick Craig-Wood)
+    -   build
+        -   Update go.mod to go1.14 to enable -mod=vendor build (Nick
+            Craig-Wood)
+        -   Remove quicktest from Dockerfile (Nick Craig-Wood)
+        -   Build Docker images with GitHub actions (Matteo Pietro
+            Dazzi)
+        -   Update Docker build workflows (Nick Craig-Wood)
+        -   Set user_allow_other in /etc/fuse.conf in the Docker image
+            (Nick Craig-Wood)
+        -   Fix xgo build after go1.14 go.mod update (Nick Craig-Wood)
+    -   docs
+        -   Add link to source and modified time to footer of every page
+            (Nick Craig-Wood)
+        -   Remove manually set dates and use git dates instead (Nick
+            Craig-Wood)
+        -   Minor tense, punctuation, brevity and positivity changes for
+            the home page (edwardxml)
+        -   Remove leading slash in page reference in footer when
+            present (Nick Craig-Wood)
+        -   Note commands which need obscured input in the docs (Nick
+            Craig-Wood)
+        -   obscure: Write more help as we are referencing it elsewhere
+            (Nick Craig-Wood)
+-   VFS
+    -   Fix OS vs Unix path confusion - fixes ChangeNotify on Windows
+        (Nick Craig-Wood)
+-   Drive
+    -   Fix missing items when listing using --fast-list / ListR (Nick
+        Craig-Wood)
+-   Putio
+    -   Fix panic on Object.Open (Cenk Alti)
+-   S3
+    -   Fix upload of single files into buckets without create
+        permission (Nick Craig-Wood)
+    -   Fix --header-upload (Nick Craig-Wood)
+-   Tardigrade
+    -   Fix listing bug by upgrading to v1.0.7
+    -   Set UserAgent to rclone (Caleb Case)
+
+
 v1.52.0 - 2020-05-27
 
 Special thanks to Martin Michlmayr for proof reading and correcting all
@@ -23683,13 +24933,13 @@ See commits
         UTC (Nick Craig-Wood)
 -   Bug Fixes
     -   accounting
-        -   Restore “Max number of stats groups reached” log line
+        -   Restore "Max number of stats groups reached" log line
             (Michał Matczuk)
         -   Correct exitcode on Transfer Limit Exceeded flag. (Anuar
             Serdaliyev)
         -   Reset bytes read during copy retry (Ankur Gupta)
         -   Fix race clearing stats (Nick Craig-Wood)
-    -   copy: Only create empty directories when they don’t exist on the
+    -   copy: Only create empty directories when they don't exist on the
         remote (Ishuah Kariuki)
     -   dedupe: Stop dedupe deleting files with identical IDs (Nick
         Craig-Wood)
@@ -23707,16 +24957,16 @@ See commits
         -   Fix misplaced http server config (Xiaoxing Ye)
         -   Disable duplicate log (ElonH)
     -   serve dlna
-        -   Cds: don’t specify childCount at all when unknown (Dan
+        -   Cds: don't specify childCount at all when unknown (Dan
             Walters)
         -   Cds: use modification time as date in dlna metadata (Dan
             Walters)
     -   serve restic: Fix tests after restic project removed vendoring
         (Nick Craig-Wood)
     -   sync
-        -   Fix incorrect “nothing to transfer” message using
+        -   Fix incorrect "nothing to transfer" message using
             --delete-before (Nick Craig-Wood)
-        -   Only create empty directories when they don’t exist on the
+        -   Only create empty directories when they don't exist on the
             remote (Ishuah Kariuki)
 -   Mount
     -   Add --async-read flag to disable asynchronous reads (Nick
@@ -23765,7 +25015,7 @@ See commits
         (Nick Craig-Wood)
     -   Implement rclone backend noop for testing purposes (Nick
         Craig-Wood)
-    -   Fix “file not found” errors on post transfer Hash calculation
+    -   Fix "file not found" errors on post transfer Hash calculation
         (Nick Craig-Wood)
 -   Cache
     -   Implement rclone backend stats command (Nick Craig-Wood)
@@ -23821,7 +25071,7 @@ See commits
         Craig-Wood)
     -   Extend --drive-stop-on-upload-limit to respond to
         teamDriveFileLimitExceeded. (harry)
-    -   Don’t delete files with multiple parents to avoid data loss
+    -   Don't delete files with multiple parents to avoid data loss
         (Nick Craig-Wood)
     -   Server side copy docs use default description if empty (Nick
         Craig-Wood)
@@ -23852,8 +25102,8 @@ See commits
     -   Add support for --header-upload and --header-download (Tim
         Gallant)
     -   Create feature/favorites directory (Brandon Philips)
-    -   Fix “concurrent map write” error (Nick Craig-Wood)
-    -   Don’t put an image in error message (Nick Craig-Wood)
+    -   Fix "concurrent map write" error (Nick Craig-Wood)
+    -   Don't put an image in error message (Nick Craig-Wood)
 -   HTTP
     -   Improved directory listing with new template from Caddy project
         (calisro)
@@ -23885,7 +25135,7 @@ See commits
         (Sunil Patra)
     -   Add support for --header-upload and --header-download (Tim
         Gallant)
-    -   Fix initial config “Auth state doesn’t match” message (Nick
+    -   Fix initial config "Auth state doesn't match" message (Nick
         Craig-Wood)
 -   Premiumizeme
     -   Add support for --header-upload and --header-download (Tim
@@ -23922,13 +25172,13 @@ See commits
         Lehtonen)
     -   Use the provided size parameter when allocating a new memory
         pool (Joachim Brandon LeBlanc)
-    -   Use rclone’s low level retries instead of AWS SDK to fix listing
+    -   Use rclone's low level retries instead of AWS SDK to fix listing
         retries (Nick Craig-Wood)
     -   Ignore directory markers at the root also (Nick Craig-Wood)
     -   Use single memory pool (Michał Matczuk)
     -   Do not resize buf on put to memBuf (Michał Matczuk)
     -   Improve docs for --s3-disable-checksum (Nick Craig-Wood)
-    -   Don’t leak memory or tokens in edge cases for multipart upload
+    -   Don't leak memory or tokens in edge cases for multipart upload
         (Nick Craig-Wood)
 -   Seafile
     -   Implement 2FA (Fred)
@@ -23979,7 +25229,7 @@ v1.51.0 - 2020-02-01
         destination (Nick Craig-Wood)
     -   Implement --order-by flag to order transfers (Nick Craig-Wood)
     -   accounting
-        -   Don’t show entries in both transferring and checking (Nick
+        -   Don't show entries in both transferring and checking (Nick
             Craig-Wood)
         -   Add option to delete stats (Aleksandar Jankovic)
     -   build
@@ -24042,18 +25292,18 @@ v1.51.0 - 2020-02-01
     -   proxy: Replace use of bcrypt with sha256 (Nick Craig-Wood)
     -   vendor
         -   Update bazil.org/fuse to fix FreeBSD 12.1 (Nick Craig-Wood)
-        -   Update github.com/t3rm1n4l/go-mega to fix mega “illegal
-            base64 data at input byte 22” (Nick Craig-Wood)
+        -   Update github.com/t3rm1n4l/go-mega to fix mega "illegal
+            base64 data at input byte 22" (Nick Craig-Wood)
         -   Update termbox-go to fix ncdu command on FreeBSD (Kuang-che
             Wu)
-        -   Update t3rm1n4l/go-mega - fixes mega: couldn’t login:
+        -   Update t3rm1n4l/go-mega - fixes mega: couldn't login:
             crypto/aes: invalid key size 0 (Nick Craig-Wood)
 -   Mount
     -   Enable async reads for a 20% speedup (Nick Craig-Wood)
     -   Replace use of WriteAt with Write for cache mode >= writes and
         O_APPEND (Brett Dutro)
     -   Make sure we call unmount when exiting (Nick Craig-Wood)
-    -   Don’t build on go1.10 as bazil/fuse no longer supports it (Nick
+    -   Don't build on go1.10 as bazil/fuse no longer supports it (Nick
         Craig-Wood)
     -   When setting dates discard out of range dates (Nick Craig-Wood)
 -   VFS
@@ -24066,7 +25316,7 @@ v1.51.0 - 2020-02-01
     -   Fix edge cases when reading ModTime from file (Nick Craig-Wood)
     -   Make sure existing files opened for write show correct size
         (Nick Craig-Wood)
-    -   Don’t cache the path in RW file objects to fix renaming (Nick
+    -   Don't cache the path in RW file objects to fix renaming (Nick
         Craig-Wood)
     -   Fix rename of open files when using the VFS cache (Nick
         Craig-Wood)
@@ -24116,7 +25366,7 @@ v1.51.0 - 2020-02-01
     -   Use rclone HTTP client. (jaKa)
 -   Onedrive
     -   Add Sites.Read.All permission (Benjamin Richter)
-    -   Add support “Retry-After” header (Motonori IWAMURO)
+    -   Add support "Retry-After" header (Motonori IWAMURO)
 -   Opendrive
     -   Implement --opendrive-chunk-size (Nick Craig-Wood)
 -   S3
@@ -24140,8 +25390,8 @@ v1.51.0 - 2020-02-01
     -   Add --sftp-skip-links to skip symlinks and non regular files
         (Nick Craig-Wood)
     -   Retry Creation of Connection (Sebastian Brandt)
-    -   Fix “failed to parse private key file: ssh: not an encrypted
-        key” error (Nick Craig-Wood)
+    -   Fix "failed to parse private key file: ssh: not an encrypted
+        key" error (Nick Craig-Wood)
     -   Open files for update write only to fix AWS SFTP interop (Nick
         Craig-Wood)
 -   Swift
@@ -24151,7 +25401,7 @@ v1.51.0 - 2020-02-01
     -   Update OVH API endpoint (unbelauscht)
 -   WebDAV
     -   Make nextcloud only upload SHA1 checksums (Nick Craig-Wood)
-    -   Fix case of “Bearer” in Authorization: header to agree with RFC
+    -   Fix case of "Bearer" in Authorization: header to agree with RFC
         (Nick Craig-Wood)
     -   Add Referer header to fix problems with WAFs (Nick Craig-Wood)
 
@@ -24164,7 +25414,7 @@ v1.50.2 - 2019-11-19
 -   Drive
     -   Fix listing of the root directory with drive.files scope (Nick
         Craig-Wood)
-    -   Fix –drive-root-folder-id with team/shared drives (Nick
+    -   Fix --drive-root-folder-id with team/shared drives (Nick
         Craig-Wood)
 
 
@@ -24175,7 +25425,7 @@ v1.50.1 - 2019-11-02
         CRC-32 (Nick Craig-Wood)
     -   fshttp: Fix error reporting on tpslimit token bucket errors
         (Nick Craig-Wood)
-    -   fshttp: Don’t print token bucket errors on context cancelled
+    -   fshttp: Don't print token bucket errors on context cancelled
         (Nick Craig-Wood)
 -   Local
     -   Fix listings of . on Windows (Nick Craig-Wood)
@@ -24225,7 +25475,7 @@ v1.50.0 - 2019-10-26
         -   Added command core/quit (Saksham Khanna)
 -   Bug Fixes
     -   sync
-        -   Make --update/-u not transfer files that haven’t changed
+        -   Make --update/-u not transfer files that haven't changed
             (Nick Craig-Wood)
         -   Free objects after they come out of the transfer pipe to
             save memory (Nick Craig-Wood)
@@ -24233,9 +25483,9 @@ v1.50.0 - 2019-10-26
             scan (Nick Craig-Wood)
     -   operations
         -   Fix accounting for server side copies (Nick Craig-Wood)
-        -   Display ‘All duplicates removed’ only if dedupe successful
+        -   Display 'All duplicates removed' only if dedupe successful
             (Sezal Agrawal)
-        -   Display ‘Deleted X extra copies’ only if dedupe successful
+        -   Display 'Deleted X extra copies' only if dedupe successful
             (Sezal Agrawal)
     -   accounting
         -   Only allow up to 100 completed transfers in the accounting
@@ -24249,18 +25499,18 @@ v1.50.0 - 2019-10-26
     -   cmd
         -   Fix environment variables not setting command line flags
             (Nick Craig-Wood)
-        -   Make autocomplete compatible with bash’s posix mode for
+        -   Make autocomplete compatible with bash's posix mode for
             macOS (Danil Semelenov)
         -   Make --progress work in git bash on Windows (Nick
             Craig-Wood)
-        -   Fix ‘compopt: command not found’ on autocomplete on macOS
+        -   Fix 'compopt: command not found' on autocomplete on macOS
             (Danil Semelenov)
     -   config
         -   Fix setting of non top level flags from environment
             variables (Nick Craig-Wood)
         -   Check config names more carefully and report errors (Nick
             Craig-Wood)
-        -   Remove error: can’t use --size-only and --ignore-size
+        -   Remove error: can't use --size-only and --ignore-size
             together. (Nick Craig-Wood)
     -   filter: Prevent mixing options when --files-from is in use
         (Michele Caci)
@@ -24271,9 +25521,9 @@ v1.50.0 - 2019-10-26
         Craig-Wood)
     -   Skip tests on <= 2 CPUs to avoid lockup (Nick Craig-Wood)
     -   Fix panic on File.Open (Nick Craig-Wood)
-    -   Fix “mount_fusefs: -o timeout=: option not supported” on FreeBSD
+    -   Fix "mount_fusefs: -o timeout=: option not supported" on FreeBSD
         (Nick Craig-Wood)
-    -   Don’t pass huge filenames (>4k) to FUSE as it can’t cope (Nick
+    -   Don't pass huge filenames (>4k) to FUSE as it can't cope (Nick
         Craig-Wood)
 -   VFS
     -   Add flag --vfs-case-insensitive for windows/macOS mounts (Ivan
@@ -24366,7 +25616,7 @@ v1.49.3 - 2019-09-15
 -   Bug Fixes
     -   accounting
         -   Fix total duration calculation (Aleksandar Jankovic)
-        -   Fix “file already closed” on transfer retries (Nick
+        -   Fix "file already closed" on transfer retries (Nick
             Craig-Wood)
 
 
@@ -24429,7 +25679,7 @@ v1.49.0 - 2019-08-26
     -   ncdu: Display/Copy to Clipboard Current Path (Gary Kim)
     -   operations:
         -   Run hashing operations in parallel (Nick Craig-Wood)
-        -   Don’t calculate checksums when using --ignore-checksum (Nick
+        -   Don't calculate checksums when using --ignore-checksum (Nick
             Craig-Wood)
         -   Check transfer hashes when using --size-only mode (Nick
             Craig-Wood)
@@ -24448,7 +25698,7 @@ v1.49.0 - 2019-08-26
         -   Add anchor tags to the docs so links are consistent (Nick
             Craig-Wood)
         -   Remove _async key from input parameters after parsing so
-            later operations won’t get confused (buengese)
+            later operations won't get confused (buengese)
         -   Add call to clear stats (Aleksandar Jankovic)
     -   rcd
         -   Auto-login for web-gui (Chaitanya Bankanhal)
@@ -24475,7 +25725,7 @@ v1.49.0 - 2019-08-26
         -   Implement --baseurl (Nick Craig-Wood)
         -   Support --auth-proxy (Nick Craig-Wood)
 -   Bug Fixes
-    -   Make “bad record MAC” a retriable error (Nick Craig-Wood)
+    -   Make "bad record MAC" a retriable error (Nick Craig-Wood)
     -   copyurl: Fix copying files that return HTTP errors (Nick
         Craig-Wood)
     -   march: Fix checking sub-directories when using --no-traverse
@@ -24505,7 +25755,7 @@ v1.49.0 - 2019-08-26
         Craig-Wood)
     -   Avoid polluting page cache when uploading local files to remote
         backends (Michał Matczuk)
-    -   Don’t calculate any hashes by default (Nick Craig-Wood)
+    -   Don't calculate any hashes by default (Nick Craig-Wood)
     -   Fadvise run syscall on a dedicated go routine (Michał Matczuk)
 -   Azure Blob
     -   Azure Storage Emulator support (Sandeep)
@@ -24623,7 +25873,7 @@ v1.48.0 - 2019-06-15
 -   Bug Fixes
     -   Make move and copy individual files obey --backup-dir (Nick
         Craig-Wood)
-    -   If --ignore-checksum is in effect, don’t calculate checksum
+    -   If --ignore-checksum is in effect, don't calculate checksum
         (Nick Craig-Wood)
     -   moveto: Fix case-insensitive same remote move (Gary Kim)
     -   rc: Fix serving bucket based objects with --rc-serve (Nick
@@ -24675,7 +25925,7 @@ v1.48.0 - 2019-06-15
 -   S3
     -   Support S3 Accelerated endpoints with
         --s3-use-accelerate-endpoint (Nick Craig-Wood)
-    -   Add config info for Wasabi’s EU Central endpoint (Robert Marko)
+    -   Add config info for Wasabi's EU Central endpoint (Robert Marko)
     -   Make SetModTime work for GLACIER while syncing (Philip Harvey)
 -   SFTP
     -   Add About support (Gary Kim)
@@ -24696,7 +25946,7 @@ v1.47.0 - 2019-04-13
         -   this means rclone will restart transfers if the source has
             an error
         -   this is most useful for downloads or cloud to cloud copies
-    -   Use --fast-list for listing operations where it won’t use more
+    -   Use --fast-list for listing operations where it won't use more
         memory (Nick Craig-Wood)
         -   this should speed up the following operations on remotes
             which support ListR
@@ -24721,7 +25971,7 @@ v1.47.0 - 2019-04-13
         -   Update to use go1.12.x for the build (Nick Craig-Wood)
     -   serve dlna: Add connection manager service description to
         improve compatibility (Dan Walters)
-    -   lsf: Add ‘e’ format to show encrypted names and ‘o’ for original
+    -   lsf: Add 'e' format to show encrypted names and 'o' for original
         IDs (Nick Craig-Wood)
     -   lsjson: Added --files-only and --dirs-only flags (calistri)
     -   rc: Implement operations/publiclink the equivalent of
@@ -24751,7 +26001,7 @@ v1.47.0 - 2019-04-13
     -   Shorten the locking window for vfs/refresh (Nick Craig-Wood)
 -   Azure Blob
     -   Enable MD5 checksums when uploading files bigger than the
-        “Cutoff” (Dr.Rx)
+        "Cutoff" (Dr.Rx)
     -   Fix SAS URL support (Nick Craig-Wood)
 -   B2
     -   Allow manual configuration of backblaze downloadUrl (Vince)
@@ -24790,7 +26040,7 @@ v1.47.0 - 2019-04-13
     -   Return errors instead of panic for invalid uploads (Fabian
         Möller)
 -   S3
-    -   Add support for “Glacier Deep Archive” storage class (Manu)
+    -   Add support for "Glacier Deep Archive" storage class (Manu)
     -   Update Dreamhost endpoint (Nick Craig-Wood)
     -   Note incompatibility with CEPH Jewel (Nick Craig-Wood)
 -   SFTP
@@ -24854,7 +26104,7 @@ v1.46 - 2019-02-09
         when size is -1 (Cnly)
     -   copyurl: Fix checking of --dry-run (Denis Skovpen)
 -   Mount
-    -   Check that mountpoint and local directory to mount don’t overlap
+    -   Check that mountpoint and local directory to mount don't overlap
         (Nick Craig-Wood)
     -   Fix mount size under 32 bit Windows (Nick Craig-Wood)
 -   VFS
@@ -24869,7 +26119,7 @@ v1.46 - 2019-02-09
         Craig-Wood)
     -   Fix deadlock between RWFileHandle.close and File.Remove (Nick
         Craig-Wood)
-    -   Fix renaming/deleting open files with cache mode “writes” under
+    -   Fix renaming/deleting open files with cache mode "writes" under
         Windows (Nick Craig-Wood)
     -   Fix panic on rename with --dry-run set (Nick Craig-Wood)
     -   Fix vfs/refresh with recurse=true needing the --fast-list flag
@@ -24925,7 +26175,7 @@ v1.46 - 2019-02-09
     -   Update google cloud storage endpoints (weetmuts)
 -   HTTP
     -   Add an example with username and password which is supported but
-        wasn’t documented (Nick Craig-Wood)
+        wasn't documented (Nick Craig-Wood)
     -   Fix backend with --files-from and non-existent files (Nick
         Craig-Wood)
 -   Hubic
@@ -24933,7 +26183,7 @@ v1.46 - 2019-02-09
         (Nick Craig-Wood)
 -   Jottacloud
     -   Resume and deduplication support (Oliver Heyme)
-    -   Use token auth for all API requests Don’t store password anymore
+    -   Use token auth for all API requests Don't store password anymore
         (Sebastian Bünger)
     -   Add support for 2-factor authentication (Sebastian Bünger)
 -   Mega
@@ -24943,7 +26193,7 @@ v1.46 - 2019-02-09
         uploaded (Nick Craig-Wood)
     -   Add new error codes for better error reporting (Nick Craig-Wood)
 -   Onedrive
-    -   Fix broken support for “shared with me” folders (Alex Chen)
+    -   Fix broken support for "shared with me" folders (Alex Chen)
     -   Fix root ID not normalised (Cnly)
     -   Return err instead of panic on unknown-sized uploads (Cnly)
 -   Qingstor
@@ -25021,12 +26271,12 @@ v1.45 - 2018-11-24
             already
         -   See the rc docs for more info
     -   sync/copy/move
-        -   Make --files-from only read the objects specified and don’t
+        -   Make --files-from only read the objects specified and don't
             scan directories (Nick Craig-Wood)
             -   This is a huge speed improvement for destinations with
                 lots of files
     -   filter: Add --ignore-case flag (Nick Craig-Wood)
-    -   ncdu: Add remove function (‘d’ key) (Henning Surmeier)
+    -   ncdu: Add remove function ('d' key) (Henning Surmeier)
     -   rc command
         -   Add --json flag for structured JSON input (Nick Craig-Wood)
         -   Add --user and --pass flags and interpret --rc-user,
@@ -25043,7 +26293,7 @@ v1.45 - 2018-11-24
         Craig-Wood)
     -   dedupe: Check for existing filename before renaming a dupe file
         (ssaqua)
-    -   move: Don’t create directories with --dry-run (Nick Craig-Wood)
+    -   move: Don't create directories with --dry-run (Nick Craig-Wood)
     -   operations: Fix Purge and Rmdirs when dir is not the root (Nick
         Craig-Wood)
     -   serve http/webdav/restic: Ensure rclone exits if the port is in
@@ -25053,7 +26303,7 @@ v1.45 - 2018-11-24
 -   Azure Blob
     -   Avoid context deadline exceeded error by setting a large
         TryTimeout value (brused27)
-    -   Fix erroneous Rmdir error “directory not empty” (Nick
+    -   Fix erroneous Rmdir error "directory not empty" (Nick
         Craig-Wood)
     -   Wait for up to 60s to create a just deleted container (Nick
         Craig-Wood)
@@ -25067,8 +26317,8 @@ v1.45 - 2018-11-24
 -   S3
     -   Set ACL for server side copies to that provided by the user
         (Nick Craig-Wood)
-    -   Fix role_arn, credential_source, … (Erik Swanson)
-    -   Add config info for Wasabi’s US-West endpoint (Henry Ptasinski)
+    -   Fix role_arn, credential_source, ... (Erik Swanson)
+    -   Add config info for Wasabi's US-West endpoint (Henry Ptasinski)
 -   SFTP
     -   Ensure file hash checking is really disabled (Jon Fautley)
 -   Swift
@@ -25111,9 +26361,9 @@ v1.44 - 2018-10-15
         Connes)
 -   Bug Fixes
     -   Fix -P not ending with a new line (Nick Craig-Wood)
-    -   config: don’t create default config dir when user supplies
+    -   config: don't create default config dir when user supplies
         --config (albertony)
-    -   Don’t print non-ASCII characters with --progress on windows
+    -   Don't print non-ASCII characters with --progress on windows
         (Nick Craig-Wood)
     -   Correct logs for excluded items (ssaqua)
 -   Mount
@@ -25357,9 +26607,9 @@ v1.43 - 2018-09-01
 -   WebDAV
     -   Ensure we call MKCOL with a URL with a trailing / for QNAP
         interop (Nick Craig-Wood)
-    -   If root ends with / then don’t check if it is a file (Nick
+    -   If root ends with / then don't check if it is a file (Nick
         Craig-Wood)
-    -   Don’t accept redirects when reading metadata (Nick Craig-Wood)
+    -   Don't accept redirects when reading metadata (Nick Craig-Wood)
     -   Add bearer token (Macaroon) support for dCache (Nick Craig-Wood)
     -   Document dCache and Macaroons (Onno Zweers)
     -   Sharepoint recursion with different depth (Henning)
@@ -25375,7 +26625,7 @@ v1.42 - 2018-06-16
 -   New commands
     -   deletefile command (Filip Bartodziej)
 -   New Features
-    -   copy, move: Copy single files directly, don’t use --files-from
+    -   copy, move: Copy single files directly, don't use --files-from
         work-around
         -   this makes them much more efficient
     -   Implement --max-transfer flag to quit transferring at a limit
@@ -25391,8 +26641,8 @@ v1.42 - 2018-06-16
     -   lsf
         -   Add --absolute flag to add a leading / onto path names
         -   Add --csv flag for compliant CSV output
-        -   Add ‘m’ format specifier to show the MimeType
-        -   Implement ‘i’ format for showing object ID
+        -   Add 'm' format specifier to show the MimeType
+        -   Implement 'i' format for showing object ID
     -   lsjson
         -   Add MimeType to the output
         -   Add ID field to output to show Object ID
@@ -25404,7 +26654,7 @@ v1.42 - 2018-06-16
     -   Calculate ModifyWindow each time on the fly to fix various
         problems (Stefan Breunig)
 -   Mount
-    -   Only print “File.rename error” if there actually is an error
+    -   Only print "File.rename error" if there actually is an error
         (Stefan Breunig)
     -   Delay rename if file has open writers instead of failing
         outright (Stefan Breunig)
@@ -25443,7 +26693,7 @@ v1.42 - 2018-06-16
 -   Google Drive
     -   Add --drive-acknowledge-abuse to download flagged files
     -   Add --drive-alternate-export to fix large doc export
-    -   Don’t attempt to choose Team Drives when using rclone config
+    -   Don't attempt to choose Team Drives when using rclone config
         create
     -   Fix change list polling with team drives
     -   Fix ChangeNotify for folders (Fabian Möller)
@@ -25476,16 +26726,16 @@ v1.41 - 2018-04-28
         output
 -   New Features
     -   lsd: Add -R flag and fix and update docs for all ls commands
-    -   ncdu: added a “refresh” key - CTRL-L (Keith Goldfarb)
+    -   ncdu: added a "refresh" key - CTRL-L (Keith Goldfarb)
     -   serve restic: Add append-only mode (Steve Kriss)
     -   serve restic: Disallow overwriting files in append-only mode
         (Alexander Neumann)
     -   serve restic: Print actual listener address (Matt Holt)
-    -   size: Add –json flag (Matthew Holt)
-    -   sync: implement –ignore-errors (Mateusz Pabian)
+    -   size: Add --json flag (Matthew Holt)
+    -   sync: implement --ignore-errors (Mateusz Pabian)
     -   dedupe: Add dedupe largest functionality (Richard Yang)
     -   fs: Extend SizeSuffix to include TB and PB for rclone about
-    -   fs: add –dump goroutines and –dump openfiles for debugging
+    -   fs: add --dump goroutines and --dump openfiles for debugging
     -   rc: implement core/memstats to print internal memory usage info
     -   rc: new call rc/pid (Michael P. Dubner)
 -   Compile
@@ -25493,11 +26743,11 @@ v1.41 - 2018-04-28
 -   Release
     -   Fix make tarball (Chih-Hsuan Yen)
 -   Bug Fixes
-    -   filter: fix –min-age and –max-age together check
+    -   filter: fix --min-age and --max-age together check
     -   fs: limit MaxIdleConns and MaxIdleConnsPerHost in transport
     -   lsd,lsf: make sure all times we output are in local time
     -   rc: fix setting bwlimit to unlimited
-    -   rc: take note of the –rc-addr flag too as per the docs
+    -   rc: take note of the --rc-addr flag too as per the docs
 -   Mount
     -   Use About to return the correct disk total/used/free (eg in df)
     -   Set --attr-timeout default to 1s - fixes:
@@ -25507,9 +26757,9 @@ v1.41 - 2018-04-28
     -   Fix df -i (upstream fix)
 -   VFS
     -   Filter files . and .. from directory listing
-    -   Only make the VFS cache if –vfs-cache-mode > Off
+    -   Only make the VFS cache if --vfs-cache-mode > Off
 -   Local
-    -   Add –local-no-check-updated to disable updated file checks
+    -   Add --local-no-check-updated to disable updated file checks
     -   Retry remove on Windows sharing violation error
 -   Cache
     -   Flush the memory cache after close
@@ -25540,7 +26790,7 @@ v1.41 - 2018-04-28
     -   When initialized with a filepath, optional features used
         incorrect root path (Stefan Breunig)
 -   HTTP
-    -   Fix sync for servers which don’t return Content-Length in HEAD
+    -   Fix sync for servers which don't return Content-Length in HEAD
 -   Onedrive
     -   Add QuickXorHash support for OneDrive for business
     -   Fix socket leak in multipart session upload
@@ -25551,8 +26801,8 @@ v1.41 - 2018-04-28
     -   Hierarchical configuration support (Giri Badanahatti)
     -   Add in config for all the supported S3 providers
     -   Add One Zone Infrequent Access storage class (Craig Rachel)
-    -   Add –use-server-modtime support (Peter Baumgartner)
-    -   Add –s3-chunk-size option to control multipart uploads
+    -   Add --use-server-modtime support (Peter Baumgartner)
+    -   Add --s3-chunk-size option to control multipart uploads
     -   Ignore zero length directory markers
 -   SFTP
     -   Update docs to match code, fix typos and clarify
@@ -25560,7 +26810,7 @@ v1.41 - 2018-04-28
     -   Update docs with Synology quirks
     -   Fail soft with a debug on hash failure
 -   Swift
-    -   Add –use-server-modtime support (Peter Baumgartner)
+    -   Add --use-server-modtime support (Peter Baumgartner)
 -   Webdav
     -   Support SharePoint cookie authentication (hensur)
     -   Strip leading and trailing / off root
@@ -25582,7 +26832,7 @@ v1.40 - 2018-03-19
             access
         -   Thanks Alexander Neumann for help, patches and review
     -   rc: enable the remote control of a running rclone
-        -   The running rclone must be started with –rc and related
+        -   The running rclone must be started with --rc and related
             flags.
         -   Currently there is support for bwlimit, and flushing for
             mount and cache.
@@ -25622,12 +26872,12 @@ v1.40 - 2018-03-19
     -   config: fixes errors on non existing config by loading config
         file only on first access
     -   config: retry saving the config after failure (Mateusz)
-    -   sync: when using --backup-dir don’t delete files if we can’t set
+    -   sync: when using --backup-dir don't delete files if we can't set
         their modtime
         -   this fixes odd behaviour with Dropbox and --backup-dir
     -   fshttp: fix idle timeouts for HTTP connections
     -   serve http: fix serving files with : in - fixes
-    -   Fix --exclude-if-present to ignore directories which it doesn’t
+    -   Fix --exclude-if-present to ignore directories which it doesn't
         have permission for (Iakov Davydov)
     -   Make accounting work properly with crypt and b2
     -   remove --no-traverse flag because it is obsolete
@@ -25655,10 +26905,10 @@ v1.40 - 2018-03-19
     -   Fix creation of files when truncating
     -   Write 0 bytes when flushing unwritten handles to avoid race
         conditions in FUSE
-    -   Downgrade “poll-interval is not supported” message to Info
+    -   Downgrade "poll-interval is not supported" message to Info
     -   Make OpenFile and friends return EINVAL if O_RDONLY and O_TRUNC
 -   Local
-    -   Downgrade “invalid cross-device link: trying copy” to debug
+    -   Downgrade "invalid cross-device link: trying copy" to debug
     -   Make DirMove return fs.ErrorCantDirMove to allow fallback to
         Copy for cross device
     -   Fix race conditions updating the hashes
@@ -25678,18 +26928,18 @@ v1.40 - 2018-03-19
         tests
     -   Implement DirChangeNotify to notify cache/vfs/mount of changes
 -   Azureblob
-    -   Don’t check for bucket/container presence if listing was OK
+    -   Don't check for bucket/container presence if listing was OK
         -   this makes rclone do one less request per invocation
     -   Improve accounting for chunked uploads
 -   Backblaze B2
-    -   Don’t check for bucket/container presence if listing was OK
+    -   Don't check for bucket/container presence if listing was OK
         -   this makes rclone do one less request per invocation
 -   Box
     -   Improve accounting for chunked uploads
 -   Dropbox
     -   Fix custom oauth client parameters
 -   Google Cloud Storage
-    -   Don’t check for bucket/container presence if listing was OK
+    -   Don't check for bucket/container presence if listing was OK
         -   this makes rclone do one less request per invocation
 -   Google Drive
     -   Migrate to api v3 (Fabian Möller)
@@ -25717,13 +26967,13 @@ v1.40 - 2018-03-19
 -   Pcloud
     -   Remove unused chunked upload flag and code
 -   Qingstor
-    -   Don’t check for bucket/container presence if listing was OK
+    -   Don't check for bucket/container presence if listing was OK
         -   this makes rclone do one less request per invocation
 -   S3
     -   Support hashes for multipart files (Chris Redekop)
     -   Initial support for IBM COS (S3) (Giri Badanahatti)
     -   Update docs to discourage use of v2 auth with CEPH and others
-    -   Don’t check for bucket/container presence if listing was OK
+    -   Don't check for bucket/container presence if listing was OK
         -   this makes rclone do one less request per invocation
     -   Fix server side copy and set modtime on files with + in
 -   SFTP
@@ -25742,7 +26992,7 @@ v1.40 - 2018-03-19
         -   in v1.39 a bug was introduced which ignored new tokens -
             this fixes it
     -   Fix extra HEAD transaction when uploading a new file
-    -   Don’t check for bucket/container presence if listing was OK
+    -   Don't check for bucket/container presence if listing was OK
         -   this makes rclone do one less request per invocation
 -   Webdav
     -   Add new time formats to support mydrive.ch and others
@@ -25768,15 +27018,15 @@ v1.39 - 2017-12-23
         Tasiemski)
 -   New Features
     -   curl install for rclone (Filip Bartodziej)
-    -   –stats now shows percentage, size, rate and ETA in condensed
+    -   --stats now shows percentage, size, rate and ETA in condensed
         form (Ishuah Kariuki)
-    -   –exclude-if-present to exclude a directory if a file is present
+    -   --exclude-if-present to exclude a directory if a file is present
         (Iakov Davydov)
-    -   rmdirs: add –leave-root flag (lewapm)
-    -   move: add –delete-empty-src-dirs flag to remove dirs after move
+    -   rmdirs: add --leave-root flag (lewapm)
+    -   move: add --delete-empty-src-dirs flag to remove dirs after move
         (Ishuah Kariuki)
-    -   Add –dump flag, introduce –dump requests, responses and remove
-        –dump-auth, –dump-filters
+    -   Add --dump flag, introduce --dump requests, responses and remove
+        --dump-auth, --dump-filters
         -   Obscure X-Auth-Token: from headers when dumping too
     -   Document and implement exit codes for different failure modes
         (Ishuah Kariuki)
@@ -25786,16 +27036,16 @@ v1.39 - 2017-12-23
         transfers more reliable
     -   Save the config before asking for a token, fixes disappearing
         oauth config
-    -   Warn the user if –include and –exclude are used together (Ernest
-        Borowski)
+    -   Warn the user if --include and --exclude are used together
+        (Ernest Borowski)
     -   Fix duplicate files (eg on Google drive) causing spurious copies
     -   Allow trailing and leading whitespace for passwords (Jason Rose)
     -   ncdu: fix crashes on empty directories
     -   rcat: fix goroutine leak
     -   moveto/copyto: Fix to allow copying to the same name
 -   Mount
-    -   –vfs-cache mode to make writes into mounts more reliable.
-        -   this requires caching files on the disk (see –cache-dir)
+    -   --vfs-cache mode to make writes into mounts more reliable.
+        -   this requires caching files on the disk (see --cache-dir)
         -   As this is a new feature, use with care
     -   Use sdnotify to signal systemd the mount is ready (Fabian
         Möller)
@@ -25823,7 +27073,7 @@ v1.39 - 2017-12-23
     -   Add support for ECS task IAM roles (David Minor)
 -   Backblaze B2
     -   Fix multipart upload retries
-    -   Fix –hard-delete to make it work 100% of the time
+    -   Fix --hard-delete to make it work 100% of the time
 -   Swift
     -   Allow authentication with storage URL and auth key (Giovanni
         Pizzi)
@@ -25837,8 +27087,8 @@ v1.39 - 2017-12-23
 -   SFTP
     -   Add option to enable the use of aes128-cbc cipher (Jon Fautley)
 -   Amazon cloud drive
-    -   Fix download of large files failing with “Only one auth
-        mechanism allowed”
+    -   Fix download of large files failing with "Only one auth
+        mechanism allowed"
 -   crypt
     -   Option to encrypt directory names or leave them intact
     -   Implement DirChangeNotify (Fabian Möller)
@@ -25865,7 +27115,7 @@ v1.38 - 2017-09-30
     -   dedupe - implement merging of duplicate directories
     -   check and cryptcheck made more consistent and use less memory
     -   cleanup for remaining remotes (thanks ishuah)
-    -   --immutable for ensuring that files don’t change (thanks Jacob
+    -   --immutable for ensuring that files don't change (thanks Jacob
         McNamee)
     -   --user-agent option (thanks Alex McGrath Kraak)
     -   --disable flag to disable optional features
@@ -25888,7 +27138,7 @@ v1.38 - 2017-09-30
 -   Mount
     -   Re-use rcat internals to support uploads from all remotes
 -   Dropbox
-    -   Fix “entry doesn’t belong in directory” error
+    -   Fix "entry doesn't belong in directory" error
     -   Stop using deprecated API methods
 -   Swift
     -   Fix server side copy to empty container with --fast-list
@@ -25935,37 +27185,37 @@ v1.37 - 2017-07-22
     -   rclone dbhashsum - to show Dropbox style hashes of files (local
         or Dropbox)
 -   New Features
-    -   Implement –fast-list flag
+    -   Implement --fast-list flag
         -   This allows remotes to list recursively if they can
         -   This uses less transactions (important if you pay for them)
         -   This may or may not be quicker
         -   This will use more memory as it has to hold the listing in
             memory
-        -   –old-sync-method deprecated - the remaining uses are covered
-            by –fast-list
+        -   --old-sync-method deprecated - the remaining uses are
+            covered by --fast-list
         -   This involved a major re-write of all the listing code
-    -   Add –tpslimit and –tpslimit-burst to limit transactions per
+    -   Add --tpslimit and --tpslimit-burst to limit transactions per
         second
         -   this is useful in conjunction with rclone mount to limit
             external apps
-    -   Add –stats-log-level so can see –stats without -v
+    -   Add --stats-log-level so can see --stats without -v
     -   Print password prompts to stderr - Hraban Luyat
     -   Warn about duplicate files when syncing
     -   Oauth improvements
         -   allow auth_url and token_url to be set in the config file
         -   Print redirection URI if using own credentials.
-    -   Don’t Mkdir at the start of sync to save transactions
+    -   Don't Mkdir at the start of sync to save transactions
 -   Compile
     -   Update build to go1.8.3
     -   Require go1.6 for building rclone
-    -   Compile 386 builds with “GO386=387” for maximum compatibility
+    -   Compile 386 builds with "GO386=387" for maximum compatibility
 -   Bug Fixes
     -   Fix menu selection when no remotes
     -   Config saving reworked to not kill the file if disk gets full
-    -   Don’t delete remote if name does not change while renaming
+    -   Don't delete remote if name does not change while renaming
     -   moveto, copyto: report transfers and checks as per move and copy
 -   Local
-    -   Add –local-no-unicode-normalization flag - Bob Potter
+    -   Add --local-no-unicode-normalization flag - Bob Potter
 -   Mount
     -   Now supported on Windows using cgofuse and WinFsp - thanks to
         Bill Zissimopoulos for much help
@@ -25973,14 +27223,14 @@ v1.37 - 2017-07-22
     -   Unmount when program ends with SIGINT (Ctrl+C) or SIGTERM -
         Jérôme Vizcaino
     -   On read only open of file, make open pending until first read
-    -   Make –read-only reject modify operations
+    -   Make --read-only reject modify operations
     -   Implement ModTime via FUSE for remotes that support it
     -   Allow modTime to be changed even before all writers are closed
     -   Fix panic on renames
     -   Fix hang on errored upload
 -   Crypt
     -   Report the name:root as specified by the user
-    -   Add an “obfuscate” option for filename encryption - Stephen
+    -   Add an "obfuscate" option for filename encryption - Stephen
         Harris
 -   Amazon Drive
     -   Fix initialization order for token renewer
@@ -25992,10 +27242,10 @@ v1.37 - 2017-07-22
     -   Add team drive support
     -   Reduce bandwidth by adding fields for partial responses - Martin
         Kristensen
-    -   Implement –drive-shared-with-me flag to view shared with me
+    -   Implement --drive-shared-with-me flag to view shared with me
         files - Danny Tsai
-    -   Add –drive-trashed-only to read only the files in the trash
-    -   Remove obsolete –drive-full-list
+    -   Add --drive-trashed-only to read only the files in the trash
+    -   Remove obsolete --drive-full-list
     -   Add missing seek to start on retries of chunked uploads
     -   Fix stats accounting for upload
     -   Convert / in names to a unicode equivalent (／)
@@ -26055,24 +27305,24 @@ v1.36 - 2017-03-18
         memory usage
     -   Logging revamped to be more inline with rsync - now much
         quieter * -v only shows transfers * -vv is for full debug *
-        –syslog to log to syslog on capable platforms
-    -   Implement –backup-dir and –suffix
-    -   Implement –track-renames (initial implementation by Bjørn Erik
+        --syslog to log to syslog on capable platforms
+    -   Implement --backup-dir and --suffix
+    -   Implement --track-renames (initial implementation by Bjørn Erik
         Pedersen)
     -   Add time-based bandwidth limits (Lukas Loesche)
     -   rclone cryptcheck: checks integrity of crypt remotes
     -   Allow all config file variables and options to be set from
         environment variables
-    -   Add –buffer-size parameter to control buffer size for copy
-    -   Make –delete-after the default
-    -   Add –ignore-checksum flag (fixed by Hisham Zarka)
-    -   rclone check: Add –download flag to check all the data, not just
-        hashes
-    -   rclone cat: add –head, –tail, –offset, –count and –discard
+    -   Add --buffer-size parameter to control buffer size for copy
+    -   Make --delete-after the default
+    -   Add --ignore-checksum flag (fixed by Hisham Zarka)
+    -   rclone check: Add --download flag to check all the data, not
+        just hashes
+    -   rclone cat: add --head, --tail, --offset, --count and --discard
     -   rclone config: when choosing from a list, allow the value to be
         entered too
     -   rclone config: allow rename and copy of remotes
-    -   rclone obscure: for generating encrypted passwords for rclone’s
+    -   rclone obscure: for generating encrypted passwords for rclone's
         config (T.C. Ferguson)
     -   Comply with XDG Base Directory specification (Dario Giovannetti)
         -   this moves the default location of the config file in a
@@ -26083,29 +27333,29 @@ v1.36 - 2017-03-18
         -   MIPS/Linux big and little endian support
 -   Bug Fixes
     -   Fix copyto copying things to the wrong place if the destination
-        dir didn’t exist
+        dir didn't exist
     -   Fix parsing of remotes in moveto and copyto
-    -   Fix –delete-before deleting files on copy
-    -   Fix –files-from with an empty file copying everything
-    -   Fix sync: don’t update mod times if –dry-run set
+    -   Fix --delete-before deleting files on copy
+    -   Fix --files-from with an empty file copying everything
+    -   Fix sync: don't update mod times if --dry-run set
     -   Fix MimeType propagation
     -   Fix filters to add ** rules to directory rules
 -   Local
-    -   Implement -L, –copy-links flag to allow rclone to follow
+    -   Implement -L, --copy-links flag to allow rclone to follow
         symlinks
     -   Open files in write only mode so rclone can write to an rclone
         mount
     -   Fix unnormalised unicode causing problems reading directories
-    -   Fix interaction between -x flag and –max-depth
+    -   Fix interaction between -x flag and --max-depth
 -   Mount
     -   Implement proper directory handling (mkdir, rmdir, renaming)
     -   Make include and exclude filters apply to mount
     -   Implement read and write async buffers - control with
-        –buffer-size
+        --buffer-size
     -   Fix fsync on for directories
     -   Fix retry on network failure when reading off crypt
 -   Crypt
-    -   Add –crypt-show-mapping to show encrypted file mapping
+    -   Add --crypt-show-mapping to show encrypted file mapping
     -   Fix crypt writer getting stuck in a loop
         -   IMPORTANT this bug had the potential to cause data
             corruption when
@@ -26124,9 +27374,9 @@ v1.36 - 2017-03-18
     -   Fix upload url not being refreshed properly
 -   Drive
     -   Fix Rmdir on directories with trashed files
-    -   Fix “Ignoring unknown object” when downloading
-    -   Add –drive-list-chunk
-    -   Add –drive-skip-gdocs (Károly Oláh)
+    -   Fix "Ignoring unknown object" when downloading
+    -   Add --drive-list-chunk
+    -   Add --drive-skip-gdocs (Károly Oláh)
 -   OneDrive
     -   Implement Move
     -   Fix Copy
@@ -26151,24 +27401,24 @@ v1.35 - 2017-01-02
     -   moveto and copyto commands for choosing a destination name on
         copy/move
     -   rmdirs command to recursively delete empty directories
-    -   Allow repeated –include/–exclude/–filter options
+    -   Allow repeated --include/--exclude/--filter options
     -   Only show transfer stats on commands which transfer stuff
         -   show stats on any command using the --stats flag
     -   Allow overlapping directories in move when server side dir move
         is supported
-    -   Add –stats-unit option - thanks Scott McGillivray
+    -   Add --stats-unit option - thanks Scott McGillivray
 -   Bug Fixes
     -   Fix the config file being overwritten when two rclone instances
         are running
     -   Make rclone lsd obey the filters properly
     -   Fix compilation on mips
-    -   Fix not transferring files that don’t differ in size
+    -   Fix not transferring files that don't differ in size
     -   Fix panic on nil retry/fatal error
 -   Mount
     -   Retry reads on error - should help with reliability a lot
     -   Report the modification times for directories from the remote
-    -   Add bandwidth accounting and limiting (fixes –bwlimit)
-    -   If –stats provided will show stats and which files are
+    -   Add bandwidth accounting and limiting (fixes --bwlimit)
+    -   If --stats provided will show stats and which files are
         transferring
     -   Support R/W files if truncate is set.
     -   Implement statfs interface so df works
@@ -26184,7 +27434,7 @@ v1.35 - 2017-01-02
     -   Fix nil pointer deref on size attribute
 -   B2
     -   Use new prefix and delimiter parameters in directory listings
-        -   This makes –max-depth 1 dir listings as used in mount much
+        -   This makes --max-depth 1 dir listings as used in mount much
             faster
     -   Reauth the account while doing uploads too - should help with
         token expiry
@@ -26202,7 +27452,7 @@ v1.34 - 2016-11-06
     -   Make ContentType be preserved for cloud to cloud copies
     -   Add support to toggle bandwidth limits via SIGUSR2 - thanks
         Marco Paganini
-    -   rclone check shows count of hashes that couldn’t be checked
+    -   rclone check shows count of hashes that couldn't be checked
     -   rclone listremotes command
     -   Support linux/arm64 build - thanks Fredrik Fornwall
     -   Remove Authorization: lines from --dump-headers output
@@ -26212,7 +27462,7 @@ v1.34 - 2016-11-06
         -   Delete src files which already existed in dst
         -   Fix deletion of src file when dst file older
     -   Fix rclone check on crypted file systems
-    -   Make failed uploads not count as “Transferred”
+    -   Make failed uploads not count as "Transferred"
     -   Make sure high level retries show with -q
     -   Use a vendor directory with godep for repeatable builds
 -   rclone mount - FUSE
@@ -26226,9 +27476,9 @@ v1.34 - 2016-11-06
         players)
         -   with -no-seek flag to disable
     -   Fix crash on 32 bit ARM (alignment of 64 bit counter)
-    -   …and many more internal fixes and improvements!
+    -   ...and many more internal fixes and improvements!
 -   Crypt
-    -   Don’t show encrypted password in configurator to stop confusion
+    -   Don't show encrypted password in configurator to stop confusion
 -   Amazon Drive
     -   New wait for upload option --acd-upload-wait-per-gb
         -   upload timeouts scale by file size and can be disabled
@@ -26259,7 +27509,7 @@ v1.34 - 2016-11-06
         specification
     -   add .epub, .odp and .tsv as export formats.
 -   Swift
-    -   Don’t read metadata for directory marker objects
+    -   Don't read metadata for directory marker objects
 
 
 v1.33 - 2016-08-24
@@ -26310,7 +27560,7 @@ v1.31 - 2016-07-13
 
 -   New Features
     -   Reduce memory on sync by about 50%
-    -   Implement –no-traverse flag to stop copy traversing the
+    -   Implement --no-traverse flag to stop copy traversing the
         destination remote.
         -   This can be used to reduce memory usage down to the smallest
             possible.
@@ -26320,10 +27570,10 @@ v1.31 - 2016-07-13
         versions of files
         -   Currently B2 only
     -   Single file handling improved
-        -   Now copied with –files-from
-        -   Automatically sets –no-traverse when copying a single file
+        -   Now copied with --files-from
+        -   Automatically sets --no-traverse when copying a single file
     -   Info on using installing with ansible - thanks Stefan Weichinger
-    -   Implement –no-update-modtime flag to stop rclone fixing the
+    -   Implement --no-update-modtime flag to stop rclone fixing the
         remote modified times.
 -   Bug Fixes
     -   Fix move command - stop it running for overlapping Fses - this
@@ -26339,20 +27589,20 @@ v1.31 - 2016-07-13
 -   S3
     -   Add instructions on how to use rclone with minio.
     -   Add ap-northeast-2 (Seoul) and ap-south-1 (Mumbai) regions.
-    -   Skip setting the modified time for objects > 5GB as it isn’t
+    -   Skip setting the modified time for objects > 5GB as it isn't
         possible.
 -   Backblaze B2
-    -   Add –b2-versions flag so old versions can be listed and
+    -   Add --b2-versions flag so old versions can be listed and
         retrieved.
     -   Treat 403 errors (eg cap exceeded) as fatal.
     -   Implement cleanup command for deleting old file versions.
     -   Make error handling compliant with B2 integrations notes.
     -   Fix handling of token expiry.
-    -   Implement –b2-test-mode to set X-Bz-Test-Mode header.
+    -   Implement --b2-test-mode to set X-Bz-Test-Mode header.
     -   Set cutoff for chunked upload to 200MB as per B2 guidelines.
     -   Make upload multi-threaded.
 -   Dropbox
-    -   Don’t retry 461 errors.
+    -   Don't retry 461 errors.
 
 
 v1.30 - 2016-06-18
@@ -26361,16 +27611,17 @@ v1.30 - 2016-06-18
     -   Directory listing code reworked for more features and better
         error reporting (thanks to Klaus Post for help). This enables
         -   Directory include filtering for efficiency
-        -   –max-depth parameter
+        -   --max-depth parameter
         -   Better error reporting
         -   More to come
     -   Retry more errors
-    -   Add –ignore-size flag - for uploading images to onedrive
+    -   Add --ignore-size flag - for uploading images to onedrive
     -   Log -v output to stdout by default
     -   Display the transfer stats in more human readable form
     -   Make 0 size files specifiable with --max-size 0b
-    -   Add b suffix so we can specify bytes in –bwlimit, –min-size etc
-    -   Use “password:” instead of “password>” prompt - thanks Klaus
+    -   Add b suffix so we can specify bytes in --bwlimit, --min-size
+        etc
+    -   Use "password:" instead of "password>" prompt - thanks Klaus
         Post and Leigh Klotz
 -   Bug Fixes
     -   Fix retry doing one too many retries
@@ -26390,7 +27641,7 @@ v1.30 - 2016-06-18
 -   S3
     -   Add AES256 server-side encryption for - thanks Justin R. Wilson
 -   Google Cloud Storage
-    -   Make sure we don’t use conflicting content types on upload
+    -   Make sure we don't use conflicting content types on upload
     -   Add service account support - thanks Michal Witkowski
 -   Swift
     -   Add auth version parameter
@@ -26418,9 +27669,9 @@ v1.29 - 2016-04-18
                 renames the rest to be different.
 -   Bug fixes
     -   Make rclone check obey the --size-only flag.
-    -   Use “application/octet-stream” if discovered mime type is
+    -   Use "application/octet-stream" if discovered mime type is
         invalid.
-    -   Fix missing “quit” option when there are no remotes.
+    -   Fix missing "quit" option when there are no remotes.
 -   Google Drive
     -   Increase default chunk size to 8 MB - increases upload speed of
         big files
@@ -26431,12 +27682,12 @@ v1.29 - 2016-04-18
     -   Enable mod time syncing
         -   This means that B2 will now check modification times
         -   It will upload new files to update the modification times
-        -   (there isn’t an API to just set the mod time.)
+        -   (there isn't an API to just set the mod time.)
         -   If you want the old behaviour use --size-only.
     -   Update API to new version
     -   Fix parsing of mod time when not in metadata
 -   Swift/Hubic
-    -   Don’t return an MD5SUM for static large objects
+    -   Don't return an MD5SUM for static large objects
 -   S3
     -   Fix uploading files bigger than 50GB
 
@@ -26453,7 +27704,7 @@ v1.28 - 2016-03-01
     -   Optionally disable gzip compression on downloads with
         --no-gzip-encoding
 -   Bug fixes
-    -   Don’t make directories if --dry-run set
+    -   Don't make directories if --dry-run set
     -   Fix and document the move command
     -   Fix redirecting stderr on unix-like OSes when using --log-file
     -   Fix delete command to wait until all finished - fixes missing
@@ -26465,7 +27716,7 @@ v1.28 - 2016-03-01
         problems
     -   Upload without using a temporary file from local (and remotes
         which support SHA1)
-    -   Fix reading metadata for all files when it shouldn’t have been
+    -   Fix reading metadata for all files when it shouldn't have been
 -   Drive
     -   Fix listing drive documents at root
     -   Disable copy and move for Google docs
@@ -26500,7 +27751,7 @@ v1.27 - 2016-01-31
     -   Deprecate compiling with go1.3
 -   Amazon Drive
     -   Fix download of files > 10 GB
-    -   Fix directory traversal (“Next token is expired”) for large
+    -   Fix directory traversal ("Next token is expired") for large
         directory listings
     -   Remove 409 conflict from error codes we will retry - stops very
         long pauses
@@ -26523,9 +27774,9 @@ v1.27 - 2016-01-31
 v1.26 - 2016-01-02
 
 -   New Features
-    -   Yandex storage backend - thank you Dmitry Burdeev (“dibu”)
+    -   Yandex storage backend - thank you Dmitry Burdeev ("dibu")
     -   Implement Backblaze B2 storage backend
-    -   Add –min-age and –max-age flags - thank you Adriano Aurélio
+    -   Add --min-age and --max-age flags - thank you Adriano Aurélio
         Meirelles
     -   Make ls/lsl/md5sum/size/check obey includes and excludes
 -   Fixes
@@ -26535,7 +27786,7 @@ v1.26 - 2016-01-02
     -   Fix sync for chunked files
 -   OneDrive
     -   Re-enable server side copy
-    -   Don’t mask HTTP error codes with JSON decode error
+    -   Don't mask HTTP error codes with JSON decode error
 -   S3
     -   Fix corrupting Content-Type on mod time update (thanks Joseph
         Spurrier)
@@ -26546,7 +27797,7 @@ v1.25 - 2015-11-14
 -   New features
     -   Implement Hubic storage system
 -   Fixes
-    -   Fix deletion of some excluded files without –delete-excluded
+    -   Fix deletion of some excluded files without --delete-excluded
         -   This could have deleted files unexpectedly on sync
         -   Always check first with --dry-run!
 -   Swift
@@ -26567,15 +27818,15 @@ v1.24 - 2015-11-07
 -   Fixes
     -   Allow spaces in remotes and check remote names for validity at
         creation time
-    -   Allow ‘&’ and disallow ‘:’ in Windows filenames.
+    -   Allow '&' and disallow ':' in Windows filenames.
 -   Swift
     -   Ignore directory marker objects where appropriate - allows
         working with Hubic
-    -   Don’t delete the container if fs wasn’t at root
+    -   Don't delete the container if fs wasn't at root
 -   S3
-    -   Don’t delete the bucket if fs wasn’t at root
+    -   Don't delete the bucket if fs wasn't at root
 -   Google Cloud Storage
-    -   Don’t delete the bucket if fs wasn’t at root
+    -   Don't delete the bucket if fs wasn't at root
 
 
 v1.23 - 2015-10-03
@@ -26590,8 +27841,8 @@ v1.23 - 2015-10-03
 -   S3
     -   Allow anonymous access to public buckets
 -   Swift
-    -   Stop chunked operations logging “Failed to read info: Object Not
-        Found”
+    -   Stop chunked operations logging "Failed to read info: Object Not
+        Found"
     -   Use Content-Length on uploads for extra reliability
 
 
@@ -26621,11 +27872,11 @@ v1.20 - 2015-09-15
 -   New features
     -   Amazon Drive support
     -   Oauth support redone - fix many bugs and improve usability
-        -   Use “golang.org/x/oauth2” as oauth library of choice
+        -   Use "golang.org/x/oauth2" as oauth library of choice
         -   Improve oauth usability for smoother initial signup
         -   drive, googlecloudstorage: optionally use auto config for
             the oauth token
-    -   Implement –dump-headers and –dump-bodies debug flags
+    -   Implement --dump-headers and --dump-bodies debug flags
     -   Show multiple matched commands if abbreviation too short
     -   Implement server side move where possible
 -   local
@@ -26640,7 +27891,7 @@ v1.19 - 2015-08-28
 -   New features
     -   Server side copies for s3/swift/drive/dropbox/gcs
     -   Move command - uses server side copies if it can
-    -   Implement –retries flag - tries 3 times by default
+    -   Implement --retries flag - tries 3 times by default
     -   Build for plan9/amd64 and solaris/amd64 too
 -   Fixes
     -   Make a current version download with a fixed URL for scripting
@@ -26654,7 +27905,7 @@ v1.18 - 2015-08-17
 
 -   drive
     -   Add --drive-use-trash flag so rclone trashes instead of deletes
-    -   Add “Forbidden to download” message for files with no
+    -   Add "Forbidden to download" message for files with no
         downloadURL
 -   dropbox
     -   Remove datastore
@@ -26684,16 +27935,16 @@ v1.17 - 2015-06-14
 v1.16 - 2015-06-09
 
 -   Fix uploading big files which was causing timeouts or panics
--   Don’t check md5sum after download with –size-only
+-   Don't check md5sum after download with --size-only
 
 
 v1.15 - 2015-06-06
 
--   Add –checksum flag to only discard transfers by MD5SUM - thanks Alex
-    Couper
--   Implement –size-only flag to sync on size not checksum & modtime
+-   Add --checksum flag to only discard transfers by MD5SUM - thanks
+    Alex Couper
+-   Implement --size-only flag to sync on size not checksum & modtime
 -   Expand docs and remove duplicated information
--   Document rclone’s limitations with directories
+-   Document rclone's limitations with directories
 -   dropbox: update docs about case insensitivity
 
 
@@ -26703,20 +27954,20 @@ v1.14 - 2015-05-21
     problem
 -   drive: docs about rate limiting
 -   google cloud storage: Fix compile after API change in
-    “google.golang.org/api/storage/v1”
+    "google.golang.org/api/storage/v1"
 
 
 v1.13 - 2015-05-10
 
 -   Revise documentation (especially sync)
--   Implement –timeout and –conntimeout
--   s3: ignore etags from multipart uploads which aren’t md5sums
+-   Implement --timeout and --conntimeout
+-   s3: ignore etags from multipart uploads which aren't md5sums
 
 
 v1.12 - 2015-03-15
 
 -   drive: Use chunked upload for files above a certain size
--   drive: add –drive-chunk-size and –drive-upload-cutoff parameters
+-   drive: add --drive-chunk-size and --drive-upload-cutoff parameters
 -   drive: switch to insert from update when a failed copy deletes the
     upload
 -   core: Log duplicate files if they are detected
@@ -26729,9 +27980,9 @@ v1.11 - 2015-03-04
 -   In remote paths, change native directory separators to /
 -   Add synchronization to ls/lsl/lsd output to stop corruptions
 -   Ensure all stats/log messages to go stderr
--   Add –log-file flag to log everything (including panics) to file
--   Make it possible to disable stats printing with –stats=0
--   Implement –bwlimit to limit data transfer bandwidth
+-   Add --log-file flag to log everything (including panics) to file
+-   Make it possible to disable stats printing with --stats=0
+-   Implement --bwlimit to limit data transfer bandwidth
 
 
 v1.10 - 2015-02-12
@@ -26762,7 +28013,7 @@ v1.07 - 2014-12-23
 
 v1.06 - 2014-12-12
 
--   Fix “Couldn’t find home directory” on OSX
+-   Fix "Couldn't find home directory" on OSX
 -   swift: Add tenant parameter
 -   Use new location of Google API packages
 
@@ -26799,9 +28050,9 @@ v1.02 - 2014-07-19
 -   Implement Dropbox remote
 -   Implement Google Cloud Storage remote
 -   Verify Md5sums and Sizes after copies
--   Remove times from “ls” command - lists sizes only
--   Add add “lsl” - lists times and sizes
--   Add “md5sum” command
+-   Remove times from "ls" command - lists sizes only
+-   Add add "lsl" - lists times and sizes
+-   Add "md5sum" command
 
 
 v1.01 - 2014-07-04
@@ -26816,7 +28067,7 @@ v1.00 - 2014-07-03
 
 v0.99 - 2014-06-26
 
--   Fix –dry-run not working
+-   Fix --dry-run not working
 -   Make compatible with go 1.1
 
 
@@ -26836,7 +28087,7 @@ v0.96 - 2014-04-24
 
 -   drive: Fix multiple files of same name being created
 -   drive: Use o.Update and fs.Put to optimise transfers
--   Add version number, -V and –version
+-   Add version number, -V and --version
 
 
 v0.95 - 2014-03-28
@@ -26860,7 +28111,7 @@ v0.93 - 2014-03-16
 
 v0.92 - 2014-03-15
 
--   Config fixes and –config option
+-   Config fixes and --config option
 
 
 v0.91 - 2014-03-15
@@ -26884,35 +28135,37 @@ BUGS AND LIMITATIONS
 
 Limitations
 
-Directory timestamps aren’t preserved
+Directory timestamps aren't preserved
 
-Rclone doesn’t currently preserve the timestamps of directories. This is
+Rclone doesn't currently preserve the timestamps of directories. This is
 because rclone only really considers objects when syncing.
 
-Rclone struggles with millions of files in a directory
+Rclone struggles with millions of files in a directory/bucket
 
-Currently rclone loads each directory entirely into memory before using
-it. Since each Rclone object takes 0.5k-1k of memory this can take a
-very long time and use an extremely large amount of memory.
+Currently rclone loads each directory/bucket entirely into memory before
+using it. Since each rclone object takes 0.5k-1k of memory this can take
+a very long time and use a large amount of memory.
 
-Millions of files in a directory tend caused by software writing cloud
-storage (eg S3 buckets).
+Millions of files in a directory tends to occur on bucket-based remotes
+(e.g. S3 buckets) since those remotes do not segregate subdirectories
+within the bucket.
 
 Bucket based remotes and folders
 
-Bucket based remotes (eg S3/GCS/Swift/B2) do not have a concept of
+Bucket based remotes (e.g. S3/GCS/Swift/B2) do not have a concept of
 directories. Rclone therefore cannot create directories in them which
 means that empty directories on a bucket based remote will tend to
 disappear.
 
 Some software creates empty keys ending in / as directory markers.
-Rclone doesn’t do this as it potentially creates more objects and costs
-more. It may do in future (probably with a flag).
+Rclone doesn't do this as it potentially creates more objects and costs
+more. This ability may be added in the future (probably via a
+flag/option).
 
 
 Bugs
 
-Bugs are stored in rclone’s GitHub project:
+Bugs are stored in rclone's GitHub project:
 
 -   Reported bugs
 -   Known issues
@@ -26947,18 +28200,18 @@ The syncs would be incremental (on a file by file basis).
 
 Eg
 
-    rclone sync drive:Folder s3:bucket
+    rclone sync -i drive:Folder s3:bucket
 
 Using rclone from multiple locations at the same time
 
 You can use rclone from multiple places at the same time if you choose
 different subdirectory for the output, eg
 
-    Server A> rclone sync /tmp/whatever remote:ServerA
-    Server B> rclone sync /tmp/whatever remote:ServerB
+    Server A> rclone sync -i /tmp/whatever remote:ServerA
+    Server B> rclone sync -i /tmp/whatever remote:ServerB
 
 If you sync to the same directory then you should use rclone copy
-otherwise the two instances of rclone may delete each other’s files, eg
+otherwise the two instances of rclone may delete each other's files, eg
 
     Server A> rclone copy /tmp/whatever remote:Backup
     Server B> rclone copy /tmp/whatever remote:Backup
@@ -26967,7 +28220,7 @@ The file names you upload from Server A and Server B should be different
 in this case, otherwise some file systems (eg Drive) may make
 duplicates.
 
-Why doesn’t rclone support partial transfers / binary diffs like rsync?
+Why doesn't rclone support partial transfers / binary diffs like rsync?
 
 Rclone stores each file you transfer as a native object on the remote
 cloud storage system. This means that you can see the files you upload
@@ -26975,8 +28228,8 @@ as expected using alternative access methods (eg using the Google Drive
 web interface). There is a 1:1 mapping between files on your hard disk
 and objects created in the cloud storage system.
 
-Cloud storage systems (at least none I’ve come across yet) don’t support
-partially uploading an object. You can’t take an existing object, and
+Cloud storage systems (at least none I've come across yet) don't support
+partially uploading an object. You can't take an existing object, and
 change some bytes in the middle of it.
 
 It would be possible to make a sync system which stored binary diffs
@@ -27020,7 +28273,7 @@ set all possibilities. So, on Linux, you may end up with code similar to
 
 The NO_PROXY allows you to disable the proxy for specific hosts. Hosts
 must be comma separated, and can contain domains or parts. For instance
-“foo.com” also matches “bar.foo.com”.
+"foo.com" also matches "bar.foo.com".
 
 e.g.
 
@@ -27031,7 +28284,7 @@ Note that the ftp backend does not support ftp_proxy yet.
 
 Rclone gives x509: failed to load system roots and no roots provided error
 
-This means that rclone can’t file the SSL root certificates. Likely you
+This means that rclone can't file the SSL root certificates. Likely you
 are running rclone on a NAS with a cut-down Linux OS, or possibly on
 Solaris.
 
@@ -27055,7 +28308,7 @@ in the x509 package, provide an additional way to provide the SSL root
 certificates.
 
 Note that you may need to add the --insecure option to the curl command
-line if it doesn’t work without.
+line if it doesn't work without.
 
     curl --insecure -o /etc/ssl/certs/ca-certificates.crt https://raw.githubusercontent.com/bagder/ca-bundle/master/ca-bundle.crt
 
@@ -27070,9 +28323,9 @@ details.
 All my uploaded docx/xlsx/pptx files appear as archive/zip
 
 This is caused by uploading these files from a Windows computer which
-hasn’t got the Microsoft Office suite installed. The easiest way to fix
+hasn't got the Microsoft Office suite installed. The easiest way to fix
 is to install the Word viewer and the Microsoft Office Compatibility
-Pack for Word, Excel, and PowerPoint 2007 and later versions’ file
+Pack for Word, Excel, and PowerPoint 2007 and later versions' file
 formats
 
 tcp lookup some.domain.com no such host
@@ -27097,7 +28350,7 @@ The total size reported in the stats for a sync is wrong and keeps changing
 
 It is likely you have more than 10,000 files that need to be synced. By
 default rclone only gets 10,000 files ahead in a sync so as not to use
-up too much memory. You can change this default with the –max-backlog
+up too much memory. You can change this default with the --max-backlog
 flag.
 
 Rclone is using too much memory or appears to have a memory leak
@@ -27333,7 +28586,7 @@ email addresses removed from here need to be addeed to bin/.ignore-emails to mak
 -   Denis deniskovpen@gmail.com
 -   bsteiss 35940619+bsteiss@users.noreply.github.com
 -   Cédric Connes cedric.connes@gmail.com
--   Dr. Tobias Quathamer toddy15@users.noreply.github.com
+-   Dr. Tobias Quathamer toddy15@users.noreply.github.com
 -   dcpu 42736967+dcpu@users.noreply.github.com
 -   Sheldon Rupp me@shel.io
 -   albertony 12441419+albertony@users.noreply.github.com
@@ -27522,6 +28775,38 @@ email addresses removed from here need to be addeed to bin/.ignore-emails to mak
 -   Martin Michlmayr tbm@cyrius.com
 -   Brandon McNama bmcnama@pagerduty.com
 -   Daniel Slyman github@skylayer.eu
+-   Alex Guerrero guerrero@users.noreply.github.com
+-   Matteo Pietro Dazzi matteopietro.dazzi@gft.com
+-   edwardxml 56691903+edwardxml@users.noreply.github.com
+-   Roman Kredentser shareed2k@gmail.com
+-   Kamil Trzciński ayufan@ayufan.eu
+-   Zac Rubin z-0@users.noreply.github.com
+-   Vincent Feltz psycho@feltzv.fr
+-   Heiko Bornholdt bornholdt@informatik.uni-hamburg.de
+-   Matteo Pietro Dazzi matteopietro.dazzi@gmail.com
+-   jtagcat gitlab@c7.ee
+-   Petri Salminen petri@salminen.dev
+-   Tim Burke tim.burke@gmail.com
+-   Kai Lüke kai@kinvolk.io
+-   Garrett Squire github@garrettsquire.com
+-   Evan Harris eharris@puremagic.com
+-   Kevin keyam@microsoft.com
+-   Morten Linderud morten@linderud.pw
+-   Dmitry Ustalov dmitry.ustalov@gmail.com
+-   Jack 196648+jdeng@users.noreply.github.com
+-   kcris cristian.tarsoaga@gmail.com
+-   tyhuber1 68970760+tyhuber1@users.noreply.github.com
+-   David Ibarra david.ibarra@realty.com
+-   Tim Gallant tim@lilt.com
+-   Kaloyan Raev kaloyan@storj.io
+-   Jay McEntire jay.mcentire@gmail.com
+-   Leo Luan leoluan@us.ibm.com
+-   aus 549081+aus@users.noreply.github.com
+-   Aaron Gokaslan agokaslan@fb.com
+-   Egor Margineanu egmar@users.noreply.github.com
+-   Lucas Kanashiro lucas.kanashiro@canonical.com
+-   WarpedPixel WarpedPixel@users.noreply.github.com
+-   Sam Edwards sam@samedwards.ca
 
 
 
@@ -27537,7 +28822,7 @@ Forum for questions and general discussion:
 
 GitHub repository
 
-The project’s repository is located at:
+The project's repository is located at:
 
 -   https://github.com/rclone/rclone
 
@@ -27554,5 +28839,5 @@ You can also follow me on twitter for rclone announcements:
 Email
 
 Or if all else fails or you want to ask something private or
-confidential email Nick Craig-Wood. Please don’t email me requests for
+confidential email Nick Craig-Wood. Please don't email me requests for
 help - those are better directed to the forum. Thanks!
diff --git a/docs/content/amazonclouddrive.md b/docs/content/amazonclouddrive.md
index c22cd17c6..73e0d7a0c 100644
--- a/docs/content/amazonclouddrive.md
+++ b/docs/content/amazonclouddrive.md
@@ -165,7 +165,8 @@ Here are the standard options specific to amazon cloud drive (Amazon Drive).
 
 #### --acd-client-id
 
-Amazon Application Client ID.
+OAuth Client Id
+Leave blank normally.
 
 - Config:      client_id
 - Env Var:     RCLONE_ACD_CLIENT_ID
@@ -174,7 +175,8 @@ Amazon Application Client ID.
 
 #### --acd-client-secret
 
-Amazon Application Client Secret.
+OAuth Client Secret
+Leave blank normally.
 
 - Config:      client_secret
 - Env Var:     RCLONE_ACD_CLIENT_SECRET
@@ -185,10 +187,19 @@ Amazon Application Client Secret.
 
 Here are the advanced options specific to amazon cloud drive (Amazon Drive).
 
+#### --acd-token
+
+OAuth Access Token as a JSON blob.
+
+- Config:      token
+- Env Var:     RCLONE_ACD_TOKEN
+- Type:        string
+- Default:     ""
+
 #### --acd-auth-url
 
 Auth server URL.
-Leave blank to use Amazon's.
+Leave blank to use the provider defaults.
 
 - Config:      auth_url
 - Env Var:     RCLONE_ACD_AUTH_URL
@@ -198,7 +209,7 @@ Leave blank to use Amazon's.
 #### --acd-token-url
 
 Token server url.
-leave blank to use Amazon's.
+Leave blank to use the provider defaults.
 
 - Config:      token_url
 - Env Var:     RCLONE_ACD_TOKEN_URL
diff --git a/docs/content/b2.md b/docs/content/b2.md
index edfe8bd79..5569e49ce 100644
--- a/docs/content/b2.md
+++ b/docs/content/b2.md
@@ -413,6 +413,20 @@ This value should be set no larger than 4.657GiB (== 5GB).
 - Type:        SizeSuffix
 - Default:     200M
 
+#### --b2-copy-cutoff
+
+Cutoff for switching to multipart copy
+
+Any files larger than this that need to be server side copied will be
+copied in chunks of this size.
+
+The minimum is 0 and the maximum is 4.6GB.
+
+- Config:      copy_cutoff
+- Env Var:     RCLONE_B2_COPY_CUTOFF
+- Type:        SizeSuffix
+- Default:     4G
+
 #### --b2-chunk-size
 
 Upload chunk size. Must fit in memory.
@@ -467,6 +481,26 @@ The minimum value is 1 second. The maximum value is one week.
 - Type:        Duration
 - Default:     1w
 
+#### --b2-memory-pool-flush-time
+
+How often internal memory buffer pools will be flushed.
+Uploads which requires additional buffers (f.e multipart) will use memory pool for allocations.
+This option controls how often unused buffers will be removed from the pool.
+
+- Config:      memory_pool_flush_time
+- Env Var:     RCLONE_B2_MEMORY_POOL_FLUSH_TIME
+- Type:        Duration
+- Default:     1m0s
+
+#### --b2-memory-pool-use-mmap
+
+Whether to use mmap buffers in internal memory pool.
+
+- Config:      memory_pool_use_mmap
+- Env Var:     RCLONE_B2_MEMORY_POOL_USE_MMAP
+- Type:        bool
+- Default:     false
+
 #### --b2-encoding
 
 This sets the encoding for the backend.
diff --git a/docs/content/box.md b/docs/content/box.md
index 696a80919..fd1c6bc0b 100644
--- a/docs/content/box.md
+++ b/docs/content/box.md
@@ -270,7 +270,7 @@ Here are the standard options specific to box (Box).
 
 #### --box-client-id
 
-Box App Client Id.
+OAuth Client Id
 Leave blank normally.
 
 - Config:      client_id
@@ -280,7 +280,7 @@ Leave blank normally.
 
 #### --box-client-secret
 
-Box App Client Secret
+OAuth Client Secret
 Leave blank normally.
 
 - Config:      client_secret
@@ -293,11 +293,24 @@ Leave blank normally.
 Box App config.json location
 Leave blank normally.
 
+Leading `~` will be expanded in the file name as will environment variables such as `${RCLONE_CONFIG_DIR}`.
+
+
 - Config:      box_config_file
 - Env Var:     RCLONE_BOX_BOX_CONFIG_FILE
 - Type:        string
 - Default:     ""
 
+#### --box-access-token
+
+Box App Primary Access Token
+Leave blank normally.
+
+- Config:      access_token
+- Env Var:     RCLONE_BOX_ACCESS_TOKEN
+- Type:        string
+- Default:     ""
+
 #### --box-box-sub-type
 
 
@@ -316,6 +329,35 @@ Leave blank normally.
 
 Here are the advanced options specific to box (Box).
 
+#### --box-token
+
+OAuth Access Token as a JSON blob.
+
+- Config:      token
+- Env Var:     RCLONE_BOX_TOKEN
+- Type:        string
+- Default:     ""
+
+#### --box-auth-url
+
+Auth server URL.
+Leave blank to use the provider defaults.
+
+- Config:      auth_url
+- Env Var:     RCLONE_BOX_AUTH_URL
+- Type:        string
+- Default:     ""
+
+#### --box-token-url
+
+Token server url.
+Leave blank to use the provider defaults.
+
+- Config:      token_url
+- Env Var:     RCLONE_BOX_TOKEN_URL
+- Type:        string
+- Default:     ""
+
 #### --box-root-folder-id
 
 Fill in for rclone to use a non root folder as its starting point.
diff --git a/docs/content/cache.md b/docs/content/cache.md
index d719c8c29..74a75e6ac 100644
--- a/docs/content/cache.md
+++ b/docs/content/cache.md
@@ -343,6 +343,8 @@ The username of the Plex user
 
 The password of the Plex user
 
+**NB** Input to this must be obscured - see [rclone obscure](/commands/rclone_obscure/).
+
 - Config:      plex_password
 - Env Var:     RCLONE_CACHE_PLEX_PASSWORD
 - Type:        string
diff --git a/docs/content/changelog.md b/docs/content/changelog.md
index 3f3fa806d..79b9f8482 100644
--- a/docs/content/changelog.md
+++ b/docs/content/changelog.md
@@ -5,6 +5,183 @@ description: "Rclone Changelog"
 
 # Changelog
 
+## v1.53.0 - 2020-09-02
+
+[See commits](https://github.com/rclone/rclone/compare/v1.52.0...v1.53.0)
+
+* New Features
+    * The [VFS layer](/commands/rclone_mount/#vfs-virtual-file-system) was heavily reworked for this release - see below for more details
+    * Interactive mode [-i/--interactive](/docs/#interactive) for destructive operations (fishbullet)
+    * Add [--bwlimit-file](/docs/#bwlimit-file-bandwidth-spec) flag to limit speeds of individual file transfers (Nick Craig-Wood)
+    * Transfers are sorted by start time in the stats and progress output (Max Sum)
+    * Make sure backends expand `~` and environment vars in file names they use (Nick Craig-Wood)
+    * Add [--refresh-times](/docs/#refresh-times) flag to set modtimes on hashless backends (Nick Craig-Wood)
+    * build
+        * Remove vendor directory in favour of Go modules (Nick Craig-Wood)
+        * Build with go1.15.x by default (Nick Craig-Wood)
+        * Drop macOS 386 build as it is no longer supported by go1.15 (Nick Craig-Wood)
+        * Add ARMv7 to the supported builds (Nick Craig-Wood)
+        * Enable `rclone cmount` on macOS (Nick Craig-Wood)
+        * Make rclone build with gccgo (Nick Craig-Wood)
+        * Make rclone build with wasm (Nick Craig-Wood)
+        * Change beta numbering to be semver compatible (Nick Craig-Wood)
+        * Add file properties and icon to Windows executable (albertony)
+        * Add experimental interface for integrating rclone into browsers (Nick Craig-Wood)
+    * lib: Add file name compression (Klaus Post)
+    * rc
+        * Allow installation and use of plugins and test plugins with rclone-webui (Chaitanya Bankanhal)
+        * Add reverse proxy pluginsHandler for serving plugins (Chaitanya Bankanhal)
+        * Add `mount/listmounts` option for listing current mounts (Chaitanya Bankanhal)
+        * Add `operations/uploadfile` to upload a file through rc using encoding multipart/form-data (Chaitanya Bankanhal)
+        * Add `core/copmmand` to execute rclone terminal commands. (Chaitanya Bankanhal)
+    * `rclone check`
+        * Add reporting of filenames for same/missing/changed (Nick Craig-Wood)
+        * Make check command obey `--dry-run`/`-i`/`--interactive` (Nick Craig-Wood)
+        * Make check do `--checkers` files concurrently (Nick Craig-Wood)
+        * Retry downloads if they fail when using the `--download` flag (Nick Craig-Wood)
+        * Make it show stats by default (Nick Craig-Wood)
+    * `rclone obscure`: Allow obscure command to accept password on STDIN (David Ibarra)
+    * `rclone config`
+        * Set RCLONE_CONFIG_DIR for use in config files and subprocesses (Nick Craig-Wood)
+        * Reject remote names starting with a dash. (jtagcat)
+    * `rclone cryptcheck`: Add reporting of filenames for same/missing/changed (Nick Craig-Wood)
+    * `rclone dedupe`: Make it obey the `--size-only` flag for duplicate detection (Nick Craig-Wood)
+    * `rclone link`: Add `--expire` and `--unlink` flags (Roman Kredentser)
+    * `rclone mkdir`: Warn when using mkdir on remotes which can't have empty directories (Nick Craig-Wood)
+    * `rclone rc`: Allow JSON parameters to simplify command line usage (Nick Craig-Wood)
+    * `rclone serve ftp`
+        * Don't compile on < go1.13 after dependency update (Nick Craig-Wood)
+        * Add error message if auth proxy fails (Nick Craig-Wood)
+        * Use refactored goftp.io/server library for binary shrink (Nick Craig-Wood)
+    * `rclone serve restic`: Expose interfaces so that rclone can be used as a library from within restic (Jack)
+    * `rclone sync`: Add `--track-renames-strategy leaf` (Nick Craig-Wood)
+    * `rclone touch`: Add ability to set nanosecond resolution times (Nick Craig-Wood)
+    * `rclone tree`: Remove `-i` shorthand for `--noindent` as it conflicts with `-i`/`--interactive` (Nick Craig-Wood)
+* Bug Fixes
+    * accounting
+        * Fix documentation for `speed`/`speedAvg` (Nick Craig-Wood)
+        * Fix elapsed time not show actual time since beginning (Chaitanya Bankanhal)
+        * Fix deadlock in stats printing (Nick Craig-Wood)
+    * build
+        * Fix file handle leak in GitHub release tool (Garrett Squire)
+    * `rclone check`: Fix successful retries with `--download` counting errors (Nick Craig-Wood)
+    * `rclone dedupe`: Fix logging to be easier to understand (Nick Craig-Wood)
+* Mount
+    * Warn macOS users that mount implementation is changing (Nick Craig-Wood)
+        * to test the new implementation use `rclone cmount` instead of `rclone mount`
+        * this is because the library rclone uses has dropped macOS support
+    * rc interface
+        * Add call for unmount all (Chaitanya Bankanhal)
+        * Make `mount/mount` remote control take vfsOpt option (Nick Craig-Wood)
+        * Add mountOpt to `mount/mount` (Nick Craig-Wood)
+        * Add VFS and Mount options to `mount/listmounts` (Nick Craig-Wood)
+    * Catch panics in cgofuse initialization and turn into error messages (Nick Craig-Wood)
+    * Always supply stat information in Readdir (Nick Craig-Wood)
+    * Add support for reading unknown length files using direct IO (Windows) (Nick Craig-Wood)
+    * Fix On Windows don't add `-o uid/gid=-1` if user supplies `-o uid/gid`. (Nick Craig-Wood)
+    * Fix macOS losing directory contents in cmount (Nick Craig-Wood)
+    * Fix volume name broken in recent refactor (Nick Craig-Wood)
+* VFS
+    * Implement partial reads for `--vfs-cache-mode full` (Nick Craig-Wood)
+    * Add `--vfs-writeback` option to delay writes back to cloud storage (Nick Craig-Wood)
+    * Add `--vfs-read-ahead` parameter for use with `--vfs-cache-mode full` (Nick Craig-Wood)
+    * Restart pending uploads on restart of the cache (Nick Craig-Wood)
+    * Support synchronous cache space recovery upon ENOSPC (Leo Luan)
+    * Allow ReadAt and WriteAt to run concurrently with themselves (Nick Craig-Wood)
+    * Change modtime of file before upload to current (Rob Calistri)
+    * Recommend `--vfs-cache-modes writes` on backends which can't stream (Nick Craig-Wood)
+    * Add an optional `fs` parameter to vfs rc methods (Nick Craig-Wood)
+    * Fix errors when using > 260 char files in the cache in Windows (Nick Craig-Wood)
+    * Fix renaming of items while they are being uploaded (Nick Craig-Wood)
+    * Fix very high load caused by slow directory listings (Nick Craig-Wood)
+    * Fix renamed files not being uploaded with `--vfs-cache-mode minimal` (Nick Craig-Wood)
+    * Fix directory locking caused by slow directory listings (Nick Craig-Wood)
+    * Fix saving from chrome without `--vfs-cache-mode writes` (Nick Craig-Wood)
+* Local
+    * Add `--local-no-updated` to provide a consistent view of changing objects (Nick Craig-Wood)
+    * Add `--local-no-set-modtime` option to prevent modtime changes (tyhuber1)
+    * Fix race conditions updating and reading Object metadata (Nick Craig-Wood)
+* Cache
+    * Make any created backends be cached to fix rc problems (Nick Craig-Wood)
+    * Fix dedupe on caches wrapping drives (Nick Craig-Wood)
+* Crypt
+    * Add `--crypt-server-side-across-configs` flag (Nick Craig-Wood)
+    * Make any created backends be cached to fix rc problems (Nick Craig-Wood)
+* Alias
+    * Make any created backends be cached to fix rc problems (Nick Craig-Wood)
+* Azure Blob
+    * Don't compile on < go1.13 after dependency update (Nick Craig-Wood)
+* B2
+    * Implement server side copy for files > 5GB (Nick Craig-Wood)
+    * Cancel in progress multipart uploads and copies on rclone exit (Nick Craig-Wood)
+    * Note that b2's encoding now allows \ but rclone's hasn't changed (Nick Craig-Wood)
+    * Fix transfers when using download_url (Nick Craig-Wood)
+* Box
+    * Implement rclone cleanup (buengese)
+    * Cancel in progress multipart uploads and copies on rclone exit (Nick Craig-Wood)
+    * Allow authentication with access token (David)
+* Chunker
+    * Make any created backends be cached to fix rc problems (Nick Craig-Wood)
+* Drive
+    * Add `rclone backend drives` to list shared drives (teamdrives) (Nick Craig-Wood)
+    * Implement `rclone backend untrash` (Nick Craig-Wood)
+    * Work around drive bug which didn't set modtime of copied docs (Nick Craig-Wood)
+    * Added `--drive-starred-only` to only show starred files (Jay McEntire)
+    * Deprecate `--drive-alternate-export` as it is no longer needed (themylogin)
+    * Fix duplication of Google docs on server side copy (Nick Craig-Wood)
+    * Fix "panic: send on closed channel" when recycling dir entries (Nick Craig-Wood)
+* Dropbox
+    * Add copyright detector info in limitations section in the docs (Alex Guerrero)
+    * Fix `rclone link` by removing expires parameter (Nick Craig-Wood)
+* Fichier
+    * Detect Flood detected: IP Locked error and sleep for 30s (Nick Craig-Wood)
+* FTP
+    * Add explicit TLS support (Heiko Bornholdt)
+    * Add support for `--dump bodies` and `--dump auth` for debugging (Nick Craig-Wood)
+    * Fix interoperation with pure-ftpd (Nick Craig-Wood)
+* Google Cloud Storage
+    * Add support for anonymous access (Kai Lüke)
+* Jottacloud
+    * Bring back legacy authentification for use with whitelabel versions (buengese)
+    * Switch to new api root - also implement a very ugly workaround for the DirMove failures (buengese)
+* Onedrive
+    * Rework cancel of multipart uploads on rclone exit (Nick Craig-Wood)
+    * Implement rclone cleanup (Nick Craig-Wood)
+    * Add `--onedrive-no-versions` flag to remove old versions (Nick Craig-Wood)
+* Pcloud
+    * Implement `rclone link` for public link creation (buengese)
+* Qingstor
+    * Cancel in progress multipart uploads on rclone exit (Nick Craig-Wood)
+* S3
+    * Preserve metadata when doing multipart copy (Nick Craig-Wood)
+    * Cancel in progress multipart uploads and copies on rclone exit (Nick Craig-Wood)
+    * Add `rclone link` for public link sharing (Roman Kredentser)
+    * Add `rclone backend restore` command to restore objects from GLACIER (Nick Craig-Wood)
+    * Add `rclone cleanup` and `rclone backend cleanup` to clean unfinished multipart uploads (Nick Craig-Wood)
+    * Add `rclone backend list-multipart-uploads` to list unfinished multipart uploads (Nick Craig-Wood)
+    * Add `--s3-max-upload-parts` support (Kamil Trzciński)
+    * Add `--s3-no-check-bucket` for minimising rclone transactions and perms (Nick Craig-Wood)
+    * Add `--s3-profile` and `--s3-shared-credentials-file` options (Nick Craig-Wood)
+    * Use regional s3 us-east-1 endpoint (David)
+    * Add Scaleway provider (Vincent Feltz)
+    * Update IBM COS endpoints (Egor Margineanu)
+    * Reduce the default `--s3-copy-cutoff` to < 5GB for Backblaze S3 compatibility (Nick Craig-Wood)
+    * Fix detection of bucket existing (Nick Craig-Wood)
+* SFTP
+    * Use the absolute path instead of the relative path for listing for improved compatibility (Nick Craig-Wood)
+    * Add `--sftp-subsystem` and `--sftp-server-command` options (aus)
+* Swift
+    * Fix dangling large objects breaking the listing (Nick Craig-Wood)
+    * Fix purge not deleting directory markers (Nick Craig-Wood)
+    * Fix update multipart object removing all of its own parts (Nick Craig-Wood)
+    * Fix missing hash from object returned from upload (Nick Craig-Wood)
+* Tardigrade
+    * Upgrade to uplink v1.2.0 (Kaloyan Raev)
+* Union
+    * Fix writing with the all policy (Nick Craig-Wood)
+* WebDAV
+    * Fix directory creation with 4shared (Nick Craig-Wood)
+
 ## v1.52.3 - 2020-08-07
 
 [See commits](https://github.com/rclone/rclone/compare/v1.52.2...v1.52.3)
diff --git a/docs/content/commands/rclone.md b/docs/content/commands/rclone.md
index 2fa9fc1a3..2025bbeb0 100644
--- a/docs/content/commands/rclone.md
+++ b/docs/content/commands/rclone.md
@@ -46,7 +46,7 @@ See the [global flags page](/flags/) for global options not listed here.
 * [rclone copyurl](/commands/rclone_copyurl/)	 - Copy url content to dest.
 * [rclone cryptcheck](/commands/rclone_cryptcheck/)	 - Cryptcheck checks the integrity of a crypted remote.
 * [rclone cryptdecode](/commands/rclone_cryptdecode/)	 - Cryptdecode returns unencrypted file names.
-* [rclone dedupe](/commands/rclone_dedupe/)	 - Interactively find duplicate files and delete/rename them.
+* [rclone dedupe](/commands/rclone_dedupe/)	 - Interactively find duplicate filenames and delete/rename them.
 * [rclone delete](/commands/rclone_delete/)	 - Remove the contents of path.
 * [rclone deletefile](/commands/rclone_deletefile/)	 - Remove a single file from remote.
 * [rclone genautocomplete](/commands/rclone_genautocomplete/)	 - Output completion script for a given shell.
@@ -65,7 +65,7 @@ See the [global flags page](/flags/) for global options not listed here.
 * [rclone move](/commands/rclone_move/)	 - Move files from source to dest.
 * [rclone moveto](/commands/rclone_moveto/)	 - Move file or directory from source to dest.
 * [rclone ncdu](/commands/rclone_ncdu/)	 - Explore a remote with a text based user interface.
-* [rclone obscure](/commands/rclone_obscure/)	 - Obscure password for use in the rclone.conf
+* [rclone obscure](/commands/rclone_obscure/)	 - Obscure password for use in the rclone config file
 * [rclone purge](/commands/rclone_purge/)	 - Remove the path and all of its contents.
 * [rclone rc](/commands/rclone_rc/)	 - Run a command against a running rclone.
 * [rclone rcat](/commands/rclone_rcat/)	 - Copies standard input to file on remote.
diff --git a/docs/content/commands/rclone_check.md b/docs/content/commands/rclone_check.md
index 14c5a34c9..c91d5c196 100644
--- a/docs/content/commands/rclone_check.md
+++ b/docs/content/commands/rclone_check.md
@@ -24,9 +24,26 @@ 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.
 
-If you supply the --one-way flag, it will only check that files in source
-match the files in destination, not the other way around. Meaning extra files in
-destination that are not in the source will not trigger an error.
+If you supply the `--one-way` 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.
+
+The `--differ`, `--missing-on-dst`, `--missing-on-src`, `--src-only`
+and `--error` flags write paths, one per line, to the file name (or
+stdout if it is `-`) supplied. What they write is described in the
+help below. For example `--differ` will write all paths which are
+present on both the source and destination but different.
+
+The `--combined` 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.
+
+- `= path` means path was found in source and destination and was identical
+- `- path` means path was missing on the source, so only in the destination
+- `+ path` means path was missing on the destination, so only in the source
+- `* path` means path was present in source and destination but different.
+- `! path` means there was an error reading or hashing the source or dest.
 
 
 ```
@@ -36,9 +53,14 @@ rclone check source:path dest:path [flags]
 ## Options
 
 ```
-      --download   Check by downloading rather than with hash.
-  -h, --help       help for check
-      --one-way    Check one way only, source files must exist on remote
+      --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 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
 ```
 
 See the [global flags page](/flags/) for global options not listed here.
diff --git a/docs/content/commands/rclone_copy.md b/docs/content/commands/rclone_copy.md
index 627c7e8ef..16b25d04e 100644
--- a/docs/content/commands/rclone_copy.md
+++ b/docs/content/commands/rclone_copy.md
@@ -59,7 +59,9 @@ recently very efficiently like this:
 
     rclone copy --max-age 24h --no-traverse /path/to/src remote:
 
-**Note**: Use the `-P`/`--progress` flag to view real-time transfer statistics
+**Note**: Use the `-P`/`--progress` flag to view real-time transfer statistics.
+
+**Note**: Use the `--dry-run` or the `--interactive`/`-i` flag to test without copying anything.
 
 
 ```
diff --git a/docs/content/commands/rclone_cryptcheck.md b/docs/content/commands/rclone_cryptcheck.md
index 7f13fe044..47cbf716b 100644
--- a/docs/content/commands/rclone_cryptcheck.md
+++ b/docs/content/commands/rclone_cryptcheck.md
@@ -35,9 +35,26 @@ the files in remote:path.
 
 After it has run it will log the status of the encryptedremote:.
 
-If you supply the --one-way flag, it will only check that files in source
-match the files in destination, not the other way around. Meaning extra files in
-destination that are not in the source will not trigger an error.
+If you supply the `--one-way` 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.
+
+The `--differ`, `--missing-on-dst`, `--missing-on-src`, `--src-only`
+and `--error` flags write paths, one per line, to the file name (or
+stdout if it is `-`) supplied. What they write is described in the
+help below. For example `--differ` will write all paths which are
+present on both the source and destination but different.
+
+The `--combined` 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.
+
+- `= path` means path was found in source and destination and was identical
+- `- path` means path was missing on the source, so only in the destination
+- `+ path` means path was missing on the destination, so only in the source
+- `* path` means path was present in source and destination but different.
+- `! path` means there was an error reading or hashing the source or dest.
 
 
 ```
@@ -47,8 +64,14 @@ rclone cryptcheck remote:path cryptedremote:path [flags]
 ## Options
 
 ```
-  -h, --help      help for cryptcheck
-      --one-way   Check one way only, source files must exist on destination
+      --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
 ```
 
 See the [global flags page](/flags/) for global options not listed here.
diff --git a/docs/content/commands/rclone_dedupe.md b/docs/content/commands/rclone_dedupe.md
index d43f4c59c..139ad4682 100644
--- a/docs/content/commands/rclone_dedupe.md
+++ b/docs/content/commands/rclone_dedupe.md
@@ -1,29 +1,44 @@
 ---
 title: "rclone dedupe"
-description: "Interactively find duplicate files and delete/rename them."
+description: "Interactively find duplicate filenames and delete/rename them."
 slug: rclone_dedupe
 url: /commands/rclone_dedupe/
 # autogenerated - DO NOT EDIT, instead edit the source code in cmd/dedupe/ and as part of making a release run "make commanddocs"
 ---
 # rclone dedupe
 
-Interactively find duplicate files and delete/rename them.
+Interactively find duplicate filenames and delete/rename them.
 
 ## Synopsis
 
 
-By default `dedupe` interactively finds duplicate files and offers to
-delete all but one or rename them to be different. Only useful with
-Google Drive which can have duplicate file names.
+
+By default `dedupe` interactively finds files with duplicate
+names and offers to delete all but one or rename them to be
+different.
+
+This is only useful with backends like Google Drive which can have
+duplicate file names. It can be run on wrapping backends (eg crypt) if
+they wrap a backend which supports duplicate file names.
 
 In the first pass it will merge directories with the same name.  It
-will do this iteratively until all the identical directories have been
-merged.
+will do this iteratively until all the identically named directories
+have been merged.
 
-The `dedupe` command will delete all but one of any identical (same
-md5sum) files it finds without confirmation.  This means that for most
-duplicated files the `dedupe` command will not be interactive.  You
-can use `--dry-run` to see what would happen without doing anything.
+In the second pass, for every group of duplicate file names, it will
+delete all but one identical files it finds without confirmation.
+This means that for most duplicated files the `dedupe`
+command will not be interactive.
+
+`dedupe` considers files to be identical if they have the
+same hash. If the backend does not support hashes (eg crypt wrapping
+Google Drive) then they will never be found to be identical. If you
+use the `--size-only` 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.
+
+**Important**: Since this can cause data loss, test first with the
+`--dry-run` or the `--interactive`/`-i` flag.
 
 Here is an example run.
 
@@ -42,22 +57,22 @@ Now the `dedupe` session
 
     $ rclone dedupe drive:dupes
     2016/03/05 16:24:37 Google drive root 'dupes': Looking for duplicates using interactive mode.
-    one.txt: Found 4 duplicates - deleting identical copies
-    one.txt: Deleting 2/3 identical duplicates (md5sum "1eedaa9fe86fd4b8632e2ac549403b36")
+    one.txt: Found 4 files with duplicate names
+    one.txt: Deleting 2/3 identical duplicates (MD5 "1eedaa9fe86fd4b8632e2ac549403b36")
     one.txt: 2 duplicates remain
-      1:      6048320 bytes, 2016-03-05 16:23:16.798000000, md5sum 1eedaa9fe86fd4b8632e2ac549403b36
-      2:       564374 bytes, 2016-03-05 16:23:06.731000000, md5sum 7594e7dc9fc28f727c42ee3e0749de81
+      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> k
     Enter the number of the file to keep> 1
     one.txt: Deleted 1 extra copies
-    two.txt: Found 3 duplicates - deleting identical copies
+    two.txt: Found 3 files with duplicates names
     two.txt: 3 duplicates remain
-      1:       564374 bytes, 2016-03-05 16:22:52.118000000, md5sum 7594e7dc9fc28f727c42ee3e0749de81
-      2:      6048320 bytes, 2016-03-05 16:22:46.185000000, md5sum 1eedaa9fe86fd4b8632e2ac549403b36
-      3:      1744073 bytes, 2016-03-05 16:22:38.104000000, md5sum 851957f7fb6f0bc4ce76be966d336802
+      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)
diff --git a/docs/content/commands/rclone_delete.md b/docs/content/commands/rclone_delete.md
index 2b28c0715..04e3ca0b7 100644
--- a/docs/content/commands/rclone_delete.md
+++ b/docs/content/commands/rclone_delete.md
@@ -35,6 +35,9 @@ Then delete
 That reads "delete everything with a minimum size of 100 MB", hence
 delete all files bigger than 100MBytes.
 
+**Important**: Since this can cause data loss, test first with the
+`--dry-run` or the `--interactive`/`-i` flag.
+
 
 ```
 rclone delete remote:path [flags]
diff --git a/docs/content/commands/rclone_link.md b/docs/content/commands/rclone_link.md
index a99c3a384..3bed988f4 100644
--- a/docs/content/commands/rclone_link.md
+++ b/docs/content/commands/rclone_link.md
@@ -11,16 +11,27 @@ Generate public link to file/folder.
 
 ## Synopsis
 
-
-rclone link will create or retrieve a public link to the given file or folder.
+rclone link will create, retrieve or remove a public link to the given
+file or folder.
 
     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
 
-If successful, the last line of the output will contain the link. Exact
-capabilities depend on the remote, but the link will always be created with
-the least constraints – e.g. no expiry, no password protection, accessible
-without account.
+If you supply the --expire flag, it will set the expiration time
+otherwise it will use the default (100 years). **Note** not all
+backends support the --expire flag - if the backend doesn't support it
+then the link returned won't expire.
+
+Use the --unlink flag to remove existing public links to the file or
+folder. **Note** not all backends support "--unlink" flag - those that
+don't will just ignore it.
+
+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.
 
 
 ```
@@ -30,7 +41,9 @@ rclone link remote:path [flags]
 ## Options
 
 ```
-  -h, --help   help for link
+      --expire Duration   The amount of time that the link will be valid (default 100y)
+  -h, --help              help for link
+      --unlink            Remove existing public link to file/folder
 ```
 
 See the [global flags page](/flags/) for global options not listed here.
diff --git a/docs/content/commands/rclone_mount.md b/docs/content/commands/rclone_mount.md
index b12db3411..fbf78b11d 100644
--- a/docs/content/commands/rclone_mount.md
+++ b/docs/content/commands/rclone_mount.md
@@ -194,20 +194,39 @@ When --vfs-read-chunk-size-limit 500M is specified, the result would be
 Chunked reading will only work with --vfs-cache-mode < full, as the file will always
 be copied to the vfs cache before opening with --vfs-cache-mode full.
 
-## Directory Cache
+## VFS - Virtual File System
 
-Using the `--dir-cache-time` flag, you can set how long a
+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.
+
+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.
+
+The VFS layer also implements a directory cache - this caches info
+about files and directories (but not the data) in memory.
+
+## VFS Directory Cache
+
+Using the `--dir-cache-time` flag, you can control how long a
 directory should be considered up to date and not refreshed from the
-backend. Changes made locally in the mount may appear immediately or
-invalidate the cache. However, changes done on the remote will only
-be picked up once the cache expires if the backend configured does not
-support polling for changes. If the backend supports polling, changes
-will be picked up on within the polling interval.
+backend. Changes made through the mount will appear immediately or
+invalidate the cache.
 
-Alternatively, you can send a `SIGHUP` 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:
+    --dir-cache-time duration   Time to cache directory entries for. (default 5m0s)
+    --poll-interval duration    Time to wait between polling for changes.
+
+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.
+
+You can send a `SIGHUP` 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:
 
     kill -SIGHUP $(pidof rclone)
 
@@ -220,40 +239,41 @@ Or individual files or directories:
 
     rclone rc vfs/forget file=path/to/file dir=path/to/dir
 
-## File Buffering
+## VFS File Buffering
 
 The `--buffer-size` flag determines the amount of memory,
 that will be used to buffer data in advance.
 
-Each open file descriptor will try to keep the specified amount of
-data in memory at all times. The buffered data is bound to one file
-descriptor and won't be shared between multiple open file descriptors
-of the same file.
+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.
+
+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.
 
-This flag is a upper limit for the used memory per file descriptor.
-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.
 The maximum memory used by rclone for buffering can be up to
 `--buffer-size * open files`.
 
-## File Caching
+## VFS File Caching
 
-These flags control the VFS file caching options.  The VFS layer is
-used by rclone mount to make a cloud storage system work more like a
-normal file system.
+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.
 
-You'll need to enable VFS caching if you want, for example, to read
-and write simultaneously to a file.  See below for more details.
+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.
 
-Note that the VFS cache works in addition to the cache backend and you
-may find that you need one or the other or both.
+Note that the VFS cache is separate from the cache backend and you may
+find that you need one or the other or both.
 
     --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 age of objects in the cache. (default 1h0m0s)
-    --vfs-cache-mode string              Cache mode off|minimal|writes|full (default "off")
+    --vfs-cache-max-size SizeSuffix      Max total size of objects in the cache. (default off)
     --vfs-cache-poll-interval duration   Interval to poll the cache for stale objects. (default 1m0s)
-    --vfs-cache-max-size int             Max total size of objects in the cache. (default off)
+    --vfs-write-back duration            Time to writeback files after last use when using cache. (default 5s)
 
 If run with `-vv` rclone will print the location of the file cache.  The
 files are stored in the user cache file area which is OS dependent but
@@ -265,9 +285,10 @@ The higher the cache mode the more compatible rclone becomes at the
 cost of using disk space.
 
 Note that files are written back to the remote only when they are
-closed so if rclone is quit or dies with open files then these won't
-get written back to the remote.  However they will still be in the on
-disk cache.
+closed and if they haven't been accessed for --vfs-write-back
+second. 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.
 
 If using --vfs-cache-max-size note that the cache may exceed this size
 for two reasons.  Firstly because it is only checked every
@@ -276,7 +297,7 @@ evicted from the cache.
 
 ### --vfs-cache-mode off
 
-In this mode the cache will read directly from the remote and write
+In this mode (the default) the cache will read directly from the remote and write
 directly to the remote without caching anything on disk.
 
 This will mean some operations are not possible
@@ -292,7 +313,7 @@ This will mean some operations are not possible
 ### --vfs-cache-mode minimal
 
 This is very similar to "off" except that files opened for read AND
-write will be buffered to disks.  This means that files opened for
+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.
 
 These operations are not possible
@@ -310,32 +331,72 @@ first.
 
 This mode should support all normal file system operations.
 
-If an upload fails it will be retried up to --low-level-retries times.
+If an upload fails it will be retried at exponentially increasing
+intervals up to 1 minute.
 
 ### --vfs-cache-mode full
 
-In this mode all reads and writes are buffered to and from disk.  When
-a file is opened for read it will be downloaded in its entirety first.
+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.
 
-This may be appropriate for your needs, or you may prefer to look at
-the cache backend which does a much more sophisticated job of caching,
-including caching directory hierarchies and chunks of files.
+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 dowloaded.
 
-In this mode, unlike the others, when a file is written to the disk,
-it will be kept on the disk after it is written to the remote.  It
-will be purged on a schedule according to `--vfs-cache-max-age`.
+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.
 
-This mode should support all normal file system operations.
+This mode should support all normal file system operations and is
+otherwise identical to --vfs-cache-mode writes.
 
-If an upload or download fails it will be retried up to
---low-level-retries times.
+When reading a file rclone will read --buffer-size plus
+--vfs-read-ahead bytes ahead.  The --buffer-size is buffered in memory
+whereas the --vfs-read-ahead is buffered on disk.
 
-## Case Sensitivity
+When using this mode it is recommended that --buffer-size is not set
+too big and --vfs-read-ahead is set large if required.
+
+## VFS Performance
+
+These flags may be used to enable/disable features of the VFS for
+performance or other reasons.
+
+In particular S3 and Swift benefit hugely from the --no-modtime flag
+(or use --use-server-modtime for a slightly different effect) as each
+read of the modification time takes a transaction.
+
+    --no-checksum     Don't compare checksums on up/download.
+    --no-modtime      Don't read/write the modification time (can speed things up).
+    --no-seek         Don't allow seeking in files.
+    --read-only       Mount read-only.
+
+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 is advantageous because some cloud providers
+account for reads being all the data requested, not all the data
+delivered.
+
+Rclone will keep doubling the chunk size requested starting at
+--vfs-read-chunk-size with a maximum of --vfs-read-chunk-size-limit
+unless it is set to "off" in which case there will be no limit.
+
+    --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")
+
+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.
+
+    --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)
+
+## VFS Case Sensitivity
 
 Linux file systems are case-sensitive: two files can differ only
 by case, and the exact case must be used when opening a file.
 
-Windows is not like most other operating systems supported by rclone.
 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.
@@ -346,7 +407,7 @@ file systems case-sensitive but that is not the default
 
 The "--vfs-case-insensitive" mount flag controls how rclone handles these
 two cases. If its value is "false", rclone passes file names to the mounted
-file system as is. If the flag is "true" (or appears without a value on
+file system as-is. If the flag is "true" (or appears without a value on
 command line), rclone may perform a "fixup" as explained below.
 
 The user may specify a file name to open/delete/rename/etc with a case
@@ -362,7 +423,7 @@ Note that case sensitivity of the operating system running rclone (the target)
 may differ from case sensitivity of a file system mounted by rclone (the source).
 The flag controls whether "fixup" is performed to satisfy the target.
 
-If the flag is not provided on command line, then its default value depends
+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".
 
@@ -403,9 +464,11 @@ rclone mount remote:path /path/to/mountpoint [flags]
       --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-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 128M)
       --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. 'off' is unlimited. (default off)
       --vfs-read-wait duration                 Time to wait for in-sequence read before seeking. (default 20ms)
+      --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 (not supported by all OSes).
       --write-back-cache                       Makes kernel buffer writes before sending them to rclone. Without this, writethrough caching is used.
diff --git a/docs/content/commands/rclone_move.md b/docs/content/commands/rclone_move.md
index 353a27159..9e2cc4634 100644
--- a/docs/content/commands/rclone_move.md
+++ b/docs/content/commands/rclone_move.md
@@ -34,7 +34,7 @@ option when moving a small number of files into a large destination
 can speed transfers up greatly.
 
 **Important**: Since this can cause data loss, test first with the
---dry-run flag.
+`--dry-run` or the `--interactive`/`-i` flag.
 
 **Note**: Use the `-P`/`--progress` flag to view real-time transfer statistics.
 
diff --git a/docs/content/commands/rclone_moveto.md b/docs/content/commands/rclone_moveto.md
index ece4e8c44..159328a6c 100644
--- a/docs/content/commands/rclone_moveto.md
+++ b/docs/content/commands/rclone_moveto.md
@@ -39,7 +39,7 @@ modification time or MD5SUM.  src will be deleted on successful
 transfer.
 
 **Important**: Since this can cause data loss, test first with the
---dry-run flag.
+`--dry-run` or the `--interactive`/`-i` flag.
 
 **Note**: Use the `-P`/`--progress` flag to view real-time transfer statistics.
 
diff --git a/docs/content/commands/rclone_obscure.md b/docs/content/commands/rclone_obscure.md
index fc685fdab..bbc5f7bfc 100644
--- a/docs/content/commands/rclone_obscure.md
+++ b/docs/content/commands/rclone_obscure.md
@@ -1,17 +1,38 @@
 ---
 title: "rclone obscure"
-description: "Obscure password for use in the rclone.conf"
+description: "Obscure password for use in the rclone config file"
 slug: rclone_obscure
 url: /commands/rclone_obscure/
 # autogenerated - DO NOT EDIT, instead edit the source code in cmd/obscure/ and as part of making a release run "make commanddocs"
 ---
 # rclone obscure
 
-Obscure password for use in the rclone.conf
+Obscure password for use in the rclone config file
 
 ## Synopsis
 
-Obscure password for use in the rclone.conf
+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 **not** 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.
+
+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.
+
+This command can also accept a password through STDIN instead of an
+argument by passing a hyphen as an argument. Example:
+
+echo "secretpassword" | rclone obscure -
+
+If there is no data on STDIN to read, rclone obscure will default to
+obfuscating the hyphen itself.
+
+If you want to encrypt the config file then please use config file
+encryption - see [rclone config](/commands/rclone_config/) for more
+info.
 
 ```
 rclone obscure password [flags]
diff --git a/docs/content/commands/rclone_purge.md b/docs/content/commands/rclone_purge.md
index 2e83a2ba5..c021ef7ae 100644
--- a/docs/content/commands/rclone_purge.md
+++ b/docs/content/commands/rclone_purge.md
@@ -16,6 +16,9 @@ Remove the path and all of its contents.  Note that this does not obey
 include/exclude filters - everything will be removed.  Use `delete` if
 you want to selectively delete files.
 
+**Important**: Since this can cause data loss, test first with the
+`--dry-run` or the `--interactive`/`-i` flag.
+
 
 ```
 rclone purge remote:path [flags]
diff --git a/docs/content/commands/rclone_serve_dlna.md b/docs/content/commands/rclone_serve_dlna.md
index d5fb87eff..9f7b27932 100644
--- a/docs/content/commands/rclone_serve_dlna.md
+++ b/docs/content/commands/rclone_serve_dlna.md
@@ -23,30 +23,49 @@ players might show files that they are not able to play back correctly.
 
 ## Server options
 
-Use --addr to specify which IP address and port the server should
-listen on, eg --addr 1.2.3.4:8000 or --addr :8080 to listen to all
+Use `--addr` to specify which IP address and port the server should
+listen on, eg `--addr 1.2.3.4:8000` or `--addr :8080` to listen to all
 IPs.
 
-Use --name to choose the friendly server name, which is by
+Use `--name` to choose the friendly server name, which is by
 default "rclone (hostname)".
 
-Use --log-trace in conjunction with -vv to enable additional debug
+Use `--log-trace` in conjunction with `-vv` to enable additional debug
 logging of all UPNP traffic.
 
-## Directory Cache
+## VFS - Virtual File System
 
-Using the `--dir-cache-time` flag, you can set how long a
+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.
+
+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.
+
+The VFS layer also implements a directory cache - this caches info
+about files and directories (but not the data) in memory.
+
+## VFS Directory Cache
+
+Using the `--dir-cache-time` flag, you can control how long a
 directory should be considered up to date and not refreshed from the
-backend. Changes made locally in the mount may appear immediately or
-invalidate the cache. However, changes done on the remote will only
-be picked up once the cache expires if the backend configured does not
-support polling for changes. If the backend supports polling, changes
-will be picked up on within the polling interval.
+backend. Changes made through the mount will appear immediately or
+invalidate the cache.
 
-Alternatively, you can send a `SIGHUP` 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:
+    --dir-cache-time duration   Time to cache directory entries for. (default 5m0s)
+    --poll-interval duration    Time to wait between polling for changes.
+
+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.
+
+You can send a `SIGHUP` 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:
 
     kill -SIGHUP $(pidof rclone)
 
@@ -59,40 +78,41 @@ Or individual files or directories:
 
     rclone rc vfs/forget file=path/to/file dir=path/to/dir
 
-## File Buffering
+## VFS File Buffering
 
 The `--buffer-size` flag determines the amount of memory,
 that will be used to buffer data in advance.
 
-Each open file descriptor will try to keep the specified amount of
-data in memory at all times. The buffered data is bound to one file
-descriptor and won't be shared between multiple open file descriptors
-of the same file.
+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.
+
+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.
 
-This flag is a upper limit for the used memory per file descriptor.
-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.
 The maximum memory used by rclone for buffering can be up to
 `--buffer-size * open files`.
 
-## File Caching
+## VFS File Caching
 
-These flags control the VFS file caching options.  The VFS layer is
-used by rclone mount to make a cloud storage system work more like a
-normal file system.
+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.
 
-You'll need to enable VFS caching if you want, for example, to read
-and write simultaneously to a file.  See below for more details.
+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.
 
-Note that the VFS cache works in addition to the cache backend and you
-may find that you need one or the other or both.
+Note that the VFS cache is separate from the cache backend and you may
+find that you need one or the other or both.
 
     --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 age of objects in the cache. (default 1h0m0s)
-    --vfs-cache-mode string              Cache mode off|minimal|writes|full (default "off")
+    --vfs-cache-max-size SizeSuffix      Max total size of objects in the cache. (default off)
     --vfs-cache-poll-interval duration   Interval to poll the cache for stale objects. (default 1m0s)
-    --vfs-cache-max-size int             Max total size of objects in the cache. (default off)
+    --vfs-write-back duration            Time to writeback files after last use when using cache. (default 5s)
 
 If run with `-vv` rclone will print the location of the file cache.  The
 files are stored in the user cache file area which is OS dependent but
@@ -104,9 +124,10 @@ The higher the cache mode the more compatible rclone becomes at the
 cost of using disk space.
 
 Note that files are written back to the remote only when they are
-closed so if rclone is quit or dies with open files then these won't
-get written back to the remote.  However they will still be in the on
-disk cache.
+closed and if they haven't been accessed for --vfs-write-back
+second. 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.
 
 If using --vfs-cache-max-size note that the cache may exceed this size
 for two reasons.  Firstly because it is only checked every
@@ -115,7 +136,7 @@ evicted from the cache.
 
 ### --vfs-cache-mode off
 
-In this mode the cache will read directly from the remote and write
+In this mode (the default) the cache will read directly from the remote and write
 directly to the remote without caching anything on disk.
 
 This will mean some operations are not possible
@@ -131,7 +152,7 @@ This will mean some operations are not possible
 ### --vfs-cache-mode minimal
 
 This is very similar to "off" except that files opened for read AND
-write will be buffered to disks.  This means that files opened for
+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.
 
 These operations are not possible
@@ -149,32 +170,72 @@ first.
 
 This mode should support all normal file system operations.
 
-If an upload fails it will be retried up to --low-level-retries times.
+If an upload fails it will be retried at exponentially increasing
+intervals up to 1 minute.
 
 ### --vfs-cache-mode full
 
-In this mode all reads and writes are buffered to and from disk.  When
-a file is opened for read it will be downloaded in its entirety first.
+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.
 
-This may be appropriate for your needs, or you may prefer to look at
-the cache backend which does a much more sophisticated job of caching,
-including caching directory hierarchies and chunks of files.
+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 dowloaded.
 
-In this mode, unlike the others, when a file is written to the disk,
-it will be kept on the disk after it is written to the remote.  It
-will be purged on a schedule according to `--vfs-cache-max-age`.
+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.
 
-This mode should support all normal file system operations.
+This mode should support all normal file system operations and is
+otherwise identical to --vfs-cache-mode writes.
 
-If an upload or download fails it will be retried up to
---low-level-retries times.
+When reading a file rclone will read --buffer-size plus
+--vfs-read-ahead bytes ahead.  The --buffer-size is buffered in memory
+whereas the --vfs-read-ahead is buffered on disk.
 
-## Case Sensitivity
+When using this mode it is recommended that --buffer-size is not set
+too big and --vfs-read-ahead is set large if required.
+
+## VFS Performance
+
+These flags may be used to enable/disable features of the VFS for
+performance or other reasons.
+
+In particular S3 and Swift benefit hugely from the --no-modtime flag
+(or use --use-server-modtime for a slightly different effect) as each
+read of the modification time takes a transaction.
+
+    --no-checksum     Don't compare checksums on up/download.
+    --no-modtime      Don't read/write the modification time (can speed things up).
+    --no-seek         Don't allow seeking in files.
+    --read-only       Mount read-only.
+
+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 is advantageous because some cloud providers
+account for reads being all the data requested, not all the data
+delivered.
+
+Rclone will keep doubling the chunk size requested starting at
+--vfs-read-chunk-size with a maximum of --vfs-read-chunk-size-limit
+unless it is set to "off" in which case there will be no limit.
+
+    --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")
+
+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.
+
+    --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)
+
+## VFS Case Sensitivity
 
 Linux file systems are case-sensitive: two files can differ only
 by case, and the exact case must be used when opening a file.
 
-Windows is not like most other operating systems supported by rclone.
 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.
@@ -185,7 +246,7 @@ file systems case-sensitive but that is not the default
 
 The "--vfs-case-insensitive" mount flag controls how rclone handles these
 two cases. If its value is "false", rclone passes file names to the mounted
-file system as is. If the flag is "true" (or appears without a value on
+file system as-is. If the flag is "true" (or appears without a value on
 command line), rclone may perform a "fixup" as explained below.
 
 The user may specify a file name to open/delete/rename/etc with a case
@@ -201,7 +262,7 @@ Note that case sensitivity of the operating system running rclone (the target)
 may differ from case sensitivity of a file system mounted by rclone (the source).
 The flag controls whether "fixup" is performed to satisfy the target.
 
-If the flag is not provided on command line, then its default value depends
+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".
 
@@ -233,9 +294,11 @@ rclone serve dlna remote:path [flags]
       --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-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 128M)
       --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. 'off' is unlimited. (default off)
       --vfs-read-wait duration                 Time to wait for in-sequence read before seeking. (default 20ms)
+      --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)
 ```
 
diff --git a/docs/content/commands/rclone_serve_ftp.md b/docs/content/commands/rclone_serve_ftp.md
index db17426e8..fadbf2b9f 100644
--- a/docs/content/commands/rclone_serve_ftp.md
+++ b/docs/content/commands/rclone_serve_ftp.md
@@ -32,20 +32,39 @@ By default this will serve files without needing a login.
 
 You can set a single username and password with the --user and --pass flags.
 
-## Directory Cache
+## VFS - Virtual File System
 
-Using the `--dir-cache-time` flag, you can set how long a
+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.
+
+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.
+
+The VFS layer also implements a directory cache - this caches info
+about files and directories (but not the data) in memory.
+
+## VFS Directory Cache
+
+Using the `--dir-cache-time` flag, you can control how long a
 directory should be considered up to date and not refreshed from the
-backend. Changes made locally in the mount may appear immediately or
-invalidate the cache. However, changes done on the remote will only
-be picked up once the cache expires if the backend configured does not
-support polling for changes. If the backend supports polling, changes
-will be picked up on within the polling interval.
+backend. Changes made through the mount will appear immediately or
+invalidate the cache.
 
-Alternatively, you can send a `SIGHUP` 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:
+    --dir-cache-time duration   Time to cache directory entries for. (default 5m0s)
+    --poll-interval duration    Time to wait between polling for changes.
+
+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.
+
+You can send a `SIGHUP` 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:
 
     kill -SIGHUP $(pidof rclone)
 
@@ -58,40 +77,41 @@ Or individual files or directories:
 
     rclone rc vfs/forget file=path/to/file dir=path/to/dir
 
-## File Buffering
+## VFS File Buffering
 
 The `--buffer-size` flag determines the amount of memory,
 that will be used to buffer data in advance.
 
-Each open file descriptor will try to keep the specified amount of
-data in memory at all times. The buffered data is bound to one file
-descriptor and won't be shared between multiple open file descriptors
-of the same file.
+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.
+
+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.
 
-This flag is a upper limit for the used memory per file descriptor.
-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.
 The maximum memory used by rclone for buffering can be up to
 `--buffer-size * open files`.
 
-## File Caching
+## VFS File Caching
 
-These flags control the VFS file caching options.  The VFS layer is
-used by rclone mount to make a cloud storage system work more like a
-normal file system.
+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.
 
-You'll need to enable VFS caching if you want, for example, to read
-and write simultaneously to a file.  See below for more details.
+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.
 
-Note that the VFS cache works in addition to the cache backend and you
-may find that you need one or the other or both.
+Note that the VFS cache is separate from the cache backend and you may
+find that you need one or the other or both.
 
     --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 age of objects in the cache. (default 1h0m0s)
-    --vfs-cache-mode string              Cache mode off|minimal|writes|full (default "off")
+    --vfs-cache-max-size SizeSuffix      Max total size of objects in the cache. (default off)
     --vfs-cache-poll-interval duration   Interval to poll the cache for stale objects. (default 1m0s)
-    --vfs-cache-max-size int             Max total size of objects in the cache. (default off)
+    --vfs-write-back duration            Time to writeback files after last use when using cache. (default 5s)
 
 If run with `-vv` rclone will print the location of the file cache.  The
 files are stored in the user cache file area which is OS dependent but
@@ -103,9 +123,10 @@ The higher the cache mode the more compatible rclone becomes at the
 cost of using disk space.
 
 Note that files are written back to the remote only when they are
-closed so if rclone is quit or dies with open files then these won't
-get written back to the remote.  However they will still be in the on
-disk cache.
+closed and if they haven't been accessed for --vfs-write-back
+second. 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.
 
 If using --vfs-cache-max-size note that the cache may exceed this size
 for two reasons.  Firstly because it is only checked every
@@ -114,7 +135,7 @@ evicted from the cache.
 
 ### --vfs-cache-mode off
 
-In this mode the cache will read directly from the remote and write
+In this mode (the default) the cache will read directly from the remote and write
 directly to the remote without caching anything on disk.
 
 This will mean some operations are not possible
@@ -130,7 +151,7 @@ This will mean some operations are not possible
 ### --vfs-cache-mode minimal
 
 This is very similar to "off" except that files opened for read AND
-write will be buffered to disks.  This means that files opened for
+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.
 
 These operations are not possible
@@ -148,32 +169,72 @@ first.
 
 This mode should support all normal file system operations.
 
-If an upload fails it will be retried up to --low-level-retries times.
+If an upload fails it will be retried at exponentially increasing
+intervals up to 1 minute.
 
 ### --vfs-cache-mode full
 
-In this mode all reads and writes are buffered to and from disk.  When
-a file is opened for read it will be downloaded in its entirety first.
+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.
 
-This may be appropriate for your needs, or you may prefer to look at
-the cache backend which does a much more sophisticated job of caching,
-including caching directory hierarchies and chunks of files.
+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 dowloaded.
 
-In this mode, unlike the others, when a file is written to the disk,
-it will be kept on the disk after it is written to the remote.  It
-will be purged on a schedule according to `--vfs-cache-max-age`.
+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.
 
-This mode should support all normal file system operations.
+This mode should support all normal file system operations and is
+otherwise identical to --vfs-cache-mode writes.
 
-If an upload or download fails it will be retried up to
---low-level-retries times.
+When reading a file rclone will read --buffer-size plus
+--vfs-read-ahead bytes ahead.  The --buffer-size is buffered in memory
+whereas the --vfs-read-ahead is buffered on disk.
 
-## Case Sensitivity
+When using this mode it is recommended that --buffer-size is not set
+too big and --vfs-read-ahead is set large if required.
+
+## VFS Performance
+
+These flags may be used to enable/disable features of the VFS for
+performance or other reasons.
+
+In particular S3 and Swift benefit hugely from the --no-modtime flag
+(or use --use-server-modtime for a slightly different effect) as each
+read of the modification time takes a transaction.
+
+    --no-checksum     Don't compare checksums on up/download.
+    --no-modtime      Don't read/write the modification time (can speed things up).
+    --no-seek         Don't allow seeking in files.
+    --read-only       Mount read-only.
+
+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 is advantageous because some cloud providers
+account for reads being all the data requested, not all the data
+delivered.
+
+Rclone will keep doubling the chunk size requested starting at
+--vfs-read-chunk-size with a maximum of --vfs-read-chunk-size-limit
+unless it is set to "off" in which case there will be no limit.
+
+    --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")
+
+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.
+
+    --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)
+
+## VFS Case Sensitivity
 
 Linux file systems are case-sensitive: two files can differ only
 by case, and the exact case must be used when opening a file.
 
-Windows is not like most other operating systems supported by rclone.
 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.
@@ -184,7 +245,7 @@ file systems case-sensitive but that is not the default
 
 The "--vfs-case-insensitive" mount flag controls how rclone handles these
 two cases. If its value is "false", rclone passes file names to the mounted
-file system as is. If the flag is "true" (or appears without a value on
+file system as-is. If the flag is "true" (or appears without a value on
 command line), rclone may perform a "fixup" as explained below.
 
 The user may specify a file name to open/delete/rename/etc with a case
@@ -200,7 +261,7 @@ Note that case sensitivity of the operating system running rclone (the target)
 may differ from case sensitivity of a file system mounted by rclone (the source).
 The flag controls whether "fixup" is performed to satisfy the target.
 
-If the flag is not provided on command line, then its default value depends
+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".
 
@@ -316,9 +377,11 @@ rclone serve ftp remote:path [flags]
       --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-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 128M)
       --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. 'off' is unlimited. (default off)
       --vfs-read-wait duration                 Time to wait for in-sequence read before seeking. (default 20ms)
+      --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)
 ```
 
diff --git a/docs/content/commands/rclone_serve_http.md b/docs/content/commands/rclone_serve_http.md
index cae4a8909..39ca31f90 100644
--- a/docs/content/commands/rclone_serve_http.md
+++ b/docs/content/commands/rclone_serve_http.md
@@ -104,20 +104,39 @@ of that with the CA certificate.  --key should be the PEM encoded
 private key and --client-ca should be the PEM encoded client
 certificate authority certificate.
 
-## Directory Cache
+## VFS - Virtual File System
 
-Using the `--dir-cache-time` flag, you can set how long a
+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.
+
+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.
+
+The VFS layer also implements a directory cache - this caches info
+about files and directories (but not the data) in memory.
+
+## VFS Directory Cache
+
+Using the `--dir-cache-time` flag, you can control how long a
 directory should be considered up to date and not refreshed from the
-backend. Changes made locally in the mount may appear immediately or
-invalidate the cache. However, changes done on the remote will only
-be picked up once the cache expires if the backend configured does not
-support polling for changes. If the backend supports polling, changes
-will be picked up on within the polling interval.
+backend. Changes made through the mount will appear immediately or
+invalidate the cache.
 
-Alternatively, you can send a `SIGHUP` 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:
+    --dir-cache-time duration   Time to cache directory entries for. (default 5m0s)
+    --poll-interval duration    Time to wait between polling for changes.
+
+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.
+
+You can send a `SIGHUP` 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:
 
     kill -SIGHUP $(pidof rclone)
 
@@ -130,40 +149,41 @@ Or individual files or directories:
 
     rclone rc vfs/forget file=path/to/file dir=path/to/dir
 
-## File Buffering
+## VFS File Buffering
 
 The `--buffer-size` flag determines the amount of memory,
 that will be used to buffer data in advance.
 
-Each open file descriptor will try to keep the specified amount of
-data in memory at all times. The buffered data is bound to one file
-descriptor and won't be shared between multiple open file descriptors
-of the same file.
+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.
+
+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.
 
-This flag is a upper limit for the used memory per file descriptor.
-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.
 The maximum memory used by rclone for buffering can be up to
 `--buffer-size * open files`.
 
-## File Caching
+## VFS File Caching
 
-These flags control the VFS file caching options.  The VFS layer is
-used by rclone mount to make a cloud storage system work more like a
-normal file system.
+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.
 
-You'll need to enable VFS caching if you want, for example, to read
-and write simultaneously to a file.  See below for more details.
+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.
 
-Note that the VFS cache works in addition to the cache backend and you
-may find that you need one or the other or both.
+Note that the VFS cache is separate from the cache backend and you may
+find that you need one or the other or both.
 
     --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 age of objects in the cache. (default 1h0m0s)
-    --vfs-cache-mode string              Cache mode off|minimal|writes|full (default "off")
+    --vfs-cache-max-size SizeSuffix      Max total size of objects in the cache. (default off)
     --vfs-cache-poll-interval duration   Interval to poll the cache for stale objects. (default 1m0s)
-    --vfs-cache-max-size int             Max total size of objects in the cache. (default off)
+    --vfs-write-back duration            Time to writeback files after last use when using cache. (default 5s)
 
 If run with `-vv` rclone will print the location of the file cache.  The
 files are stored in the user cache file area which is OS dependent but
@@ -175,9 +195,10 @@ The higher the cache mode the more compatible rclone becomes at the
 cost of using disk space.
 
 Note that files are written back to the remote only when they are
-closed so if rclone is quit or dies with open files then these won't
-get written back to the remote.  However they will still be in the on
-disk cache.
+closed and if they haven't been accessed for --vfs-write-back
+second. 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.
 
 If using --vfs-cache-max-size note that the cache may exceed this size
 for two reasons.  Firstly because it is only checked every
@@ -186,7 +207,7 @@ evicted from the cache.
 
 ### --vfs-cache-mode off
 
-In this mode the cache will read directly from the remote and write
+In this mode (the default) the cache will read directly from the remote and write
 directly to the remote without caching anything on disk.
 
 This will mean some operations are not possible
@@ -202,7 +223,7 @@ This will mean some operations are not possible
 ### --vfs-cache-mode minimal
 
 This is very similar to "off" except that files opened for read AND
-write will be buffered to disks.  This means that files opened for
+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.
 
 These operations are not possible
@@ -220,32 +241,72 @@ first.
 
 This mode should support all normal file system operations.
 
-If an upload fails it will be retried up to --low-level-retries times.
+If an upload fails it will be retried at exponentially increasing
+intervals up to 1 minute.
 
 ### --vfs-cache-mode full
 
-In this mode all reads and writes are buffered to and from disk.  When
-a file is opened for read it will be downloaded in its entirety first.
+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.
 
-This may be appropriate for your needs, or you may prefer to look at
-the cache backend which does a much more sophisticated job of caching,
-including caching directory hierarchies and chunks of files.
+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 dowloaded.
 
-In this mode, unlike the others, when a file is written to the disk,
-it will be kept on the disk after it is written to the remote.  It
-will be purged on a schedule according to `--vfs-cache-max-age`.
+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.
 
-This mode should support all normal file system operations.
+This mode should support all normal file system operations and is
+otherwise identical to --vfs-cache-mode writes.
 
-If an upload or download fails it will be retried up to
---low-level-retries times.
+When reading a file rclone will read --buffer-size plus
+--vfs-read-ahead bytes ahead.  The --buffer-size is buffered in memory
+whereas the --vfs-read-ahead is buffered on disk.
 
-## Case Sensitivity
+When using this mode it is recommended that --buffer-size is not set
+too big and --vfs-read-ahead is set large if required.
+
+## VFS Performance
+
+These flags may be used to enable/disable features of the VFS for
+performance or other reasons.
+
+In particular S3 and Swift benefit hugely from the --no-modtime flag
+(or use --use-server-modtime for a slightly different effect) as each
+read of the modification time takes a transaction.
+
+    --no-checksum     Don't compare checksums on up/download.
+    --no-modtime      Don't read/write the modification time (can speed things up).
+    --no-seek         Don't allow seeking in files.
+    --read-only       Mount read-only.
+
+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 is advantageous because some cloud providers
+account for reads being all the data requested, not all the data
+delivered.
+
+Rclone will keep doubling the chunk size requested starting at
+--vfs-read-chunk-size with a maximum of --vfs-read-chunk-size-limit
+unless it is set to "off" in which case there will be no limit.
+
+    --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")
+
+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.
+
+    --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)
+
+## VFS Case Sensitivity
 
 Linux file systems are case-sensitive: two files can differ only
 by case, and the exact case must be used when opening a file.
 
-Windows is not like most other operating systems supported by rclone.
 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.
@@ -256,7 +317,7 @@ file systems case-sensitive but that is not the default
 
 The "--vfs-case-insensitive" mount flag controls how rclone handles these
 two cases. If its value is "false", rclone passes file names to the mounted
-file system as is. If the flag is "true" (or appears without a value on
+file system as-is. If the flag is "true" (or appears without a value on
 command line), rclone may perform a "fixup" as explained below.
 
 The user may specify a file name to open/delete/rename/etc with a case
@@ -272,7 +333,7 @@ Note that case sensitivity of the operating system running rclone (the target)
 may differ from case sensitivity of a file system mounted by rclone (the source).
 The flag controls whether "fixup" is performed to satisfy the target.
 
-If the flag is not provided on command line, then its default value depends
+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".
 
@@ -314,9 +375,11 @@ rclone serve http remote:path [flags]
       --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-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 128M)
       --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. 'off' is unlimited. (default off)
       --vfs-read-wait duration                 Time to wait for in-sequence read before seeking. (default 20ms)
+      --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)
 ```
 
diff --git a/docs/content/commands/rclone_serve_sftp.md b/docs/content/commands/rclone_serve_sftp.md
index 01b7c2d9b..3f750f9f7 100644
--- a/docs/content/commands/rclone_serve_sftp.md
+++ b/docs/content/commands/rclone_serve_sftp.md
@@ -43,20 +43,39 @@ Note that the default of "--vfs-cache-mode off" is fine for the rclone
 sftp backend, but it may not be with other SFTP clients.
 
 
-## Directory Cache
+## VFS - Virtual File System
 
-Using the `--dir-cache-time` flag, you can set how long a
+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.
+
+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.
+
+The VFS layer also implements a directory cache - this caches info
+about files and directories (but not the data) in memory.
+
+## VFS Directory Cache
+
+Using the `--dir-cache-time` flag, you can control how long a
 directory should be considered up to date and not refreshed from the
-backend. Changes made locally in the mount may appear immediately or
-invalidate the cache. However, changes done on the remote will only
-be picked up once the cache expires if the backend configured does not
-support polling for changes. If the backend supports polling, changes
-will be picked up on within the polling interval.
+backend. Changes made through the mount will appear immediately or
+invalidate the cache.
 
-Alternatively, you can send a `SIGHUP` 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:
+    --dir-cache-time duration   Time to cache directory entries for. (default 5m0s)
+    --poll-interval duration    Time to wait between polling for changes.
+
+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.
+
+You can send a `SIGHUP` 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:
 
     kill -SIGHUP $(pidof rclone)
 
@@ -69,40 +88,41 @@ Or individual files or directories:
 
     rclone rc vfs/forget file=path/to/file dir=path/to/dir
 
-## File Buffering
+## VFS File Buffering
 
 The `--buffer-size` flag determines the amount of memory,
 that will be used to buffer data in advance.
 
-Each open file descriptor will try to keep the specified amount of
-data in memory at all times. The buffered data is bound to one file
-descriptor and won't be shared between multiple open file descriptors
-of the same file.
+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.
+
+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.
 
-This flag is a upper limit for the used memory per file descriptor.
-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.
 The maximum memory used by rclone for buffering can be up to
 `--buffer-size * open files`.
 
-## File Caching
+## VFS File Caching
 
-These flags control the VFS file caching options.  The VFS layer is
-used by rclone mount to make a cloud storage system work more like a
-normal file system.
+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.
 
-You'll need to enable VFS caching if you want, for example, to read
-and write simultaneously to a file.  See below for more details.
+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.
 
-Note that the VFS cache works in addition to the cache backend and you
-may find that you need one or the other or both.
+Note that the VFS cache is separate from the cache backend and you may
+find that you need one or the other or both.
 
     --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 age of objects in the cache. (default 1h0m0s)
-    --vfs-cache-mode string              Cache mode off|minimal|writes|full (default "off")
+    --vfs-cache-max-size SizeSuffix      Max total size of objects in the cache. (default off)
     --vfs-cache-poll-interval duration   Interval to poll the cache for stale objects. (default 1m0s)
-    --vfs-cache-max-size int             Max total size of objects in the cache. (default off)
+    --vfs-write-back duration            Time to writeback files after last use when using cache. (default 5s)
 
 If run with `-vv` rclone will print the location of the file cache.  The
 files are stored in the user cache file area which is OS dependent but
@@ -114,9 +134,10 @@ The higher the cache mode the more compatible rclone becomes at the
 cost of using disk space.
 
 Note that files are written back to the remote only when they are
-closed so if rclone is quit or dies with open files then these won't
-get written back to the remote.  However they will still be in the on
-disk cache.
+closed and if they haven't been accessed for --vfs-write-back
+second. 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.
 
 If using --vfs-cache-max-size note that the cache may exceed this size
 for two reasons.  Firstly because it is only checked every
@@ -125,7 +146,7 @@ evicted from the cache.
 
 ### --vfs-cache-mode off
 
-In this mode the cache will read directly from the remote and write
+In this mode (the default) the cache will read directly from the remote and write
 directly to the remote without caching anything on disk.
 
 This will mean some operations are not possible
@@ -141,7 +162,7 @@ This will mean some operations are not possible
 ### --vfs-cache-mode minimal
 
 This is very similar to "off" except that files opened for read AND
-write will be buffered to disks.  This means that files opened for
+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.
 
 These operations are not possible
@@ -159,32 +180,72 @@ first.
 
 This mode should support all normal file system operations.
 
-If an upload fails it will be retried up to --low-level-retries times.
+If an upload fails it will be retried at exponentially increasing
+intervals up to 1 minute.
 
 ### --vfs-cache-mode full
 
-In this mode all reads and writes are buffered to and from disk.  When
-a file is opened for read it will be downloaded in its entirety first.
+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.
 
-This may be appropriate for your needs, or you may prefer to look at
-the cache backend which does a much more sophisticated job of caching,
-including caching directory hierarchies and chunks of files.
+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 dowloaded.
 
-In this mode, unlike the others, when a file is written to the disk,
-it will be kept on the disk after it is written to the remote.  It
-will be purged on a schedule according to `--vfs-cache-max-age`.
+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.
 
-This mode should support all normal file system operations.
+This mode should support all normal file system operations and is
+otherwise identical to --vfs-cache-mode writes.
 
-If an upload or download fails it will be retried up to
---low-level-retries times.
+When reading a file rclone will read --buffer-size plus
+--vfs-read-ahead bytes ahead.  The --buffer-size is buffered in memory
+whereas the --vfs-read-ahead is buffered on disk.
 
-## Case Sensitivity
+When using this mode it is recommended that --buffer-size is not set
+too big and --vfs-read-ahead is set large if required.
+
+## VFS Performance
+
+These flags may be used to enable/disable features of the VFS for
+performance or other reasons.
+
+In particular S3 and Swift benefit hugely from the --no-modtime flag
+(or use --use-server-modtime for a slightly different effect) as each
+read of the modification time takes a transaction.
+
+    --no-checksum     Don't compare checksums on up/download.
+    --no-modtime      Don't read/write the modification time (can speed things up).
+    --no-seek         Don't allow seeking in files.
+    --read-only       Mount read-only.
+
+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 is advantageous because some cloud providers
+account for reads being all the data requested, not all the data
+delivered.
+
+Rclone will keep doubling the chunk size requested starting at
+--vfs-read-chunk-size with a maximum of --vfs-read-chunk-size-limit
+unless it is set to "off" in which case there will be no limit.
+
+    --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")
+
+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.
+
+    --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)
+
+## VFS Case Sensitivity
 
 Linux file systems are case-sensitive: two files can differ only
 by case, and the exact case must be used when opening a file.
 
-Windows is not like most other operating systems supported by rclone.
 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.
@@ -195,7 +256,7 @@ file systems case-sensitive but that is not the default
 
 The "--vfs-case-insensitive" mount flag controls how rclone handles these
 two cases. If its value is "false", rclone passes file names to the mounted
-file system as is. If the flag is "true" (or appears without a value on
+file system as-is. If the flag is "true" (or appears without a value on
 command line), rclone may perform a "fixup" as explained below.
 
 The user may specify a file name to open/delete/rename/etc with a case
@@ -211,7 +272,7 @@ Note that case sensitivity of the operating system running rclone (the target)
 may differ from case sensitivity of a file system mounted by rclone (the source).
 The flag controls whether "fixup" is performed to satisfy the target.
 
-If the flag is not provided on command line, then its default value depends
+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".
 
@@ -328,9 +389,11 @@ rclone serve sftp remote:path [flags]
       --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-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 128M)
       --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. 'off' is unlimited. (default off)
       --vfs-read-wait duration                 Time to wait for in-sequence read before seeking. (default 20ms)
+      --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)
 ```
 
diff --git a/docs/content/commands/rclone_serve_webdav.md b/docs/content/commands/rclone_serve_webdav.md
index ed8b5ae88..0f29adcec 100644
--- a/docs/content/commands/rclone_serve_webdav.md
+++ b/docs/content/commands/rclone_serve_webdav.md
@@ -112,20 +112,39 @@ of that with the CA certificate.  --key should be the PEM encoded
 private key and --client-ca should be the PEM encoded client
 certificate authority certificate.
 
-## Directory Cache
+## VFS - Virtual File System
 
-Using the `--dir-cache-time` flag, you can set how long a
+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.
+
+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.
+
+The VFS layer also implements a directory cache - this caches info
+about files and directories (but not the data) in memory.
+
+## VFS Directory Cache
+
+Using the `--dir-cache-time` flag, you can control how long a
 directory should be considered up to date and not refreshed from the
-backend. Changes made locally in the mount may appear immediately or
-invalidate the cache. However, changes done on the remote will only
-be picked up once the cache expires if the backend configured does not
-support polling for changes. If the backend supports polling, changes
-will be picked up on within the polling interval.
+backend. Changes made through the mount will appear immediately or
+invalidate the cache.
 
-Alternatively, you can send a `SIGHUP` 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:
+    --dir-cache-time duration   Time to cache directory entries for. (default 5m0s)
+    --poll-interval duration    Time to wait between polling for changes.
+
+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.
+
+You can send a `SIGHUP` 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:
 
     kill -SIGHUP $(pidof rclone)
 
@@ -138,40 +157,41 @@ Or individual files or directories:
 
     rclone rc vfs/forget file=path/to/file dir=path/to/dir
 
-## File Buffering
+## VFS File Buffering
 
 The `--buffer-size` flag determines the amount of memory,
 that will be used to buffer data in advance.
 
-Each open file descriptor will try to keep the specified amount of
-data in memory at all times. The buffered data is bound to one file
-descriptor and won't be shared between multiple open file descriptors
-of the same file.
+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.
+
+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.
 
-This flag is a upper limit for the used memory per file descriptor.
-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.
 The maximum memory used by rclone for buffering can be up to
 `--buffer-size * open files`.
 
-## File Caching
+## VFS File Caching
 
-These flags control the VFS file caching options.  The VFS layer is
-used by rclone mount to make a cloud storage system work more like a
-normal file system.
+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.
 
-You'll need to enable VFS caching if you want, for example, to read
-and write simultaneously to a file.  See below for more details.
+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.
 
-Note that the VFS cache works in addition to the cache backend and you
-may find that you need one or the other or both.
+Note that the VFS cache is separate from the cache backend and you may
+find that you need one or the other or both.
 
     --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 age of objects in the cache. (default 1h0m0s)
-    --vfs-cache-mode string              Cache mode off|minimal|writes|full (default "off")
+    --vfs-cache-max-size SizeSuffix      Max total size of objects in the cache. (default off)
     --vfs-cache-poll-interval duration   Interval to poll the cache for stale objects. (default 1m0s)
-    --vfs-cache-max-size int             Max total size of objects in the cache. (default off)
+    --vfs-write-back duration            Time to writeback files after last use when using cache. (default 5s)
 
 If run with `-vv` rclone will print the location of the file cache.  The
 files are stored in the user cache file area which is OS dependent but
@@ -183,9 +203,10 @@ The higher the cache mode the more compatible rclone becomes at the
 cost of using disk space.
 
 Note that files are written back to the remote only when they are
-closed so if rclone is quit or dies with open files then these won't
-get written back to the remote.  However they will still be in the on
-disk cache.
+closed and if they haven't been accessed for --vfs-write-back
+second. 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.
 
 If using --vfs-cache-max-size note that the cache may exceed this size
 for two reasons.  Firstly because it is only checked every
@@ -194,7 +215,7 @@ evicted from the cache.
 
 ### --vfs-cache-mode off
 
-In this mode the cache will read directly from the remote and write
+In this mode (the default) the cache will read directly from the remote and write
 directly to the remote without caching anything on disk.
 
 This will mean some operations are not possible
@@ -210,7 +231,7 @@ This will mean some operations are not possible
 ### --vfs-cache-mode minimal
 
 This is very similar to "off" except that files opened for read AND
-write will be buffered to disks.  This means that files opened for
+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.
 
 These operations are not possible
@@ -228,32 +249,72 @@ first.
 
 This mode should support all normal file system operations.
 
-If an upload fails it will be retried up to --low-level-retries times.
+If an upload fails it will be retried at exponentially increasing
+intervals up to 1 minute.
 
 ### --vfs-cache-mode full
 
-In this mode all reads and writes are buffered to and from disk.  When
-a file is opened for read it will be downloaded in its entirety first.
+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.
 
-This may be appropriate for your needs, or you may prefer to look at
-the cache backend which does a much more sophisticated job of caching,
-including caching directory hierarchies and chunks of files.
+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 dowloaded.
 
-In this mode, unlike the others, when a file is written to the disk,
-it will be kept on the disk after it is written to the remote.  It
-will be purged on a schedule according to `--vfs-cache-max-age`.
+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.
 
-This mode should support all normal file system operations.
+This mode should support all normal file system operations and is
+otherwise identical to --vfs-cache-mode writes.
 
-If an upload or download fails it will be retried up to
---low-level-retries times.
+When reading a file rclone will read --buffer-size plus
+--vfs-read-ahead bytes ahead.  The --buffer-size is buffered in memory
+whereas the --vfs-read-ahead is buffered on disk.
 
-## Case Sensitivity
+When using this mode it is recommended that --buffer-size is not set
+too big and --vfs-read-ahead is set large if required.
+
+## VFS Performance
+
+These flags may be used to enable/disable features of the VFS for
+performance or other reasons.
+
+In particular S3 and Swift benefit hugely from the --no-modtime flag
+(or use --use-server-modtime for a slightly different effect) as each
+read of the modification time takes a transaction.
+
+    --no-checksum     Don't compare checksums on up/download.
+    --no-modtime      Don't read/write the modification time (can speed things up).
+    --no-seek         Don't allow seeking in files.
+    --read-only       Mount read-only.
+
+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 is advantageous because some cloud providers
+account for reads being all the data requested, not all the data
+delivered.
+
+Rclone will keep doubling the chunk size requested starting at
+--vfs-read-chunk-size with a maximum of --vfs-read-chunk-size-limit
+unless it is set to "off" in which case there will be no limit.
+
+    --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")
+
+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.
+
+    --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)
+
+## VFS Case Sensitivity
 
 Linux file systems are case-sensitive: two files can differ only
 by case, and the exact case must be used when opening a file.
 
-Windows is not like most other operating systems supported by rclone.
 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.
@@ -264,7 +325,7 @@ file systems case-sensitive but that is not the default
 
 The "--vfs-case-insensitive" mount flag controls how rclone handles these
 two cases. If its value is "false", rclone passes file names to the mounted
-file system as is. If the flag is "true" (or appears without a value on
+file system as-is. If the flag is "true" (or appears without a value on
 command line), rclone may perform a "fixup" as explained below.
 
 The user may specify a file name to open/delete/rename/etc with a case
@@ -280,7 +341,7 @@ Note that case sensitivity of the operating system running rclone (the target)
 may differ from case sensitivity of a file system mounted by rclone (the source).
 The flag controls whether "fixup" is performed to satisfy the target.
 
-If the flag is not provided on command line, then its default value depends
+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".
 
@@ -406,9 +467,11 @@ rclone serve webdav remote:path [flags]
       --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-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 128M)
       --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. 'off' is unlimited. (default off)
       --vfs-read-wait duration                 Time to wait for in-sequence read before seeking. (default 20ms)
+      --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)
 ```
 
diff --git a/docs/content/commands/rclone_sync.md b/docs/content/commands/rclone_sync.md
index e398c96db..1438ebd53 100644
--- a/docs/content/commands/rclone_sync.md
+++ b/docs/content/commands/rclone_sync.md
@@ -18,7 +18,9 @@ modification time or MD5SUM.  Destination is updated to match
 source, including deleting files if necessary.
 
 **Important**: Since this can cause data loss, test first with the
-`--dry-run` flag to see exactly what would be copied and deleted.
+`--dry-run` or the `--interactive`/`-i` flag.
+
+    rclone sync -i SOURCE remote:DESTINATION
 
 Note that files in the destination won't be deleted if there were any
 errors at any point.
diff --git a/docs/content/commands/rclone_touch.md b/docs/content/commands/rclone_touch.md
index 01e453b56..8708e80d3 100644
--- a/docs/content/commands/rclone_touch.md
+++ b/docs/content/commands/rclone_touch.md
@@ -23,6 +23,7 @@ time instead of the current time. Times may be specified as one of:
 
 - 'YYMMDD' - eg. 17.10.30
 - 'YYYY-MM-DDTHH:MM:SS' - eg. 2006-01-02T15:04:05
+- 'YYYY-MM-DDTHH:MM:SS.SSS' - eg. 2006-01-02T15:04:05.123456789
 
 Note that --timestamp is in UTC if you want local time then add the
 --localtime flag.
diff --git a/docs/content/commands/rclone_tree.md b/docs/content/commands/rclone_tree.md
index 1ae6107db..1f08bd35b 100644
--- a/docs/content/commands/rclone_tree.md
+++ b/docs/content/commands/rclone_tree.md
@@ -52,7 +52,7 @@ rclone tree remote:path [flags]
       --human           Print the size in a more human readable way.
       --level int       Descend only level directories deep.
   -D, --modtime         Print the date of last modification.
-  -i, --noindent        Don't print indentation lines.
+      --noindent        Don'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.
diff --git a/docs/content/crypt.md b/docs/content/crypt.md
index ffd1f22aa..dbaa69f99 100644
--- a/docs/content/crypt.md
+++ b/docs/content/crypt.md
@@ -328,6 +328,8 @@ NB If filename_encryption is "off" then this option will do nothing.
 
 Password or pass phrase for encryption.
 
+**NB** Input to this must be obscured - see [rclone obscure](/commands/rclone_obscure/).
+
 - Config:      password
 - Env Var:     RCLONE_CRYPT_PASSWORD
 - Type:        string
@@ -338,6 +340,8 @@ Password or pass phrase for encryption.
 Password or pass phrase for salt. Optional but recommended.
 Should be different to the previous password.
 
+**NB** Input to this must be obscured - see [rclone obscure](/commands/rclone_obscure/).
+
 - Config:      password2
 - Env Var:     RCLONE_CRYPT_PASSWORD2
 - Type:        string
@@ -347,6 +351,24 @@ Should be different to the previous password.
 
 Here are the advanced options specific to crypt (Encrypt/Decrypt a remote).
 
+#### --crypt-server-side-across-configs
+
+Allow server side operations (eg copy) to work across different crypt configs.
+
+Normally this option is not what you want, but if you have two crypts
+pointing to the same backend you can use it.
+
+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.
+
+- Config:      server_side_across_configs
+- Env Var:     RCLONE_CRYPT_SERVER_SIDE_ACROSS_CONFIGS
+- Type:        bool
+- Default:     false
+
 #### --crypt-show-mapping
 
 For all files listed show how the names encrypt.
diff --git a/docs/content/drive.md b/docs/content/drive.md
index c5bbd0393..ddbef261e 100644
--- a/docs/content/drive.md
+++ b/docs/content/drive.md
@@ -547,10 +547,8 @@ Here are the standard options specific to drive (Google Drive).
 
 #### --drive-client-id
 
-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.
+OAuth Client Id
+Leave blank normally.
 
 - Config:      client_id
 - Env Var:     RCLONE_DRIVE_CLIENT_ID
@@ -559,8 +557,8 @@ If you leave this blank, it will use an internal key which is low performance.
 
 #### --drive-client-secret
 
-Google Application Client Secret
-Setting your own is recommended.
+OAuth Client Secret
+Leave blank normally.
 
 - Config:      client_secret
 - Env Var:     RCLONE_DRIVE_CLIENT_SECRET
@@ -599,9 +597,6 @@ Leave blank normally.
 Fill in to access "Computers" folders (see docs), or for rclone to use
 a non root folder as its starting point.
 
-Note that if this is blank, the first time rclone runs it will fill it
-in with the ID of the root folder.
-
 
 - Config:      root_folder_id
 - Env Var:     RCLONE_DRIVE_ROOT_FOLDER_ID
@@ -614,15 +609,56 @@ Service Account Credentials JSON file path
 Leave blank normally.
 Needed only if you want use SA instead of interactive login.
 
+Leading `~` will be expanded in the file name as will environment variables such as `${RCLONE_CONFIG_DIR}`.
+
+
 - Config:      service_account_file
 - Env Var:     RCLONE_DRIVE_SERVICE_ACCOUNT_FILE
 - Type:        string
 - Default:     ""
 
+#### --drive-alternate-export
+
+Deprecated: no longer needed
+
+- Config:      alternate_export
+- Env Var:     RCLONE_DRIVE_ALTERNATE_EXPORT
+- Type:        bool
+- Default:     false
+
 ### Advanced Options
 
 Here are the advanced options specific to drive (Google Drive).
 
+#### --drive-token
+
+OAuth Access Token as a JSON blob.
+
+- Config:      token
+- Env Var:     RCLONE_DRIVE_TOKEN
+- Type:        string
+- Default:     ""
+
+#### --drive-auth-url
+
+Auth server URL.
+Leave blank to use the provider defaults.
+
+- Config:      auth_url
+- Env Var:     RCLONE_DRIVE_AUTH_URL
+- Type:        string
+- Default:     ""
+
+#### --drive-token-url
+
+Token server url.
+Leave blank to use the provider defaults.
+
+- Config:      token_url
+- Env Var:     RCLONE_DRIVE_TOKEN_URL
+- Type:        string
+- Default:     ""
+
 #### --drive-service-account-credentials
 
 Service Account Credentials JSON blob
@@ -719,6 +755,15 @@ This will show trashed files in their original directory structure.
 - Type:        bool
 - Default:     false
 
+#### --drive-starred-only
+
+Only show files that are starred.
+
+- Config:      starred_only
+- Env Var:     RCLONE_DRIVE_STARRED_ONLY
+- Type:        bool
+- Default:     false
+
 #### --drive-formats
 
 Deprecated: see export_formats
@@ -1069,6 +1114,63 @@ Options:
 
 - "target": optional target remote for the shortcut destination
 
+#### drives
+
+List the shared drives available to this account
+
+    rclone backend drives remote: [options] [<arguments>+]
+
+This command lists the shared drives (teamdrives) available to this
+account.
+
+Usage:
+
+    rclone backend drives drive:
+
+This will return a JSON list of objects like this
+
+    [
+        {
+            "id": "0ABCDEF-01234567890",
+            "kind": "drive#teamDrive",
+            "name": "My Drive"
+        },
+        {
+            "id": "0ABCDEFabcdefghijkl",
+            "kind": "drive#teamDrive",
+            "name": "Test Drive"
+        }
+    ]
+
+
+
+#### untrash
+
+Untrash files and directories
+
+    rclone backend untrash remote: [options] [<arguments>+]
+
+This command untrashes all the files and directories in the directory
+passed in recursively.
+
+Usage:
+
+This takes an optional directory to trash which make this easier to
+use via the API.
+
+    rclone backend untrash drive:directory
+    rclone backend -i untrash drive:directory subdir
+
+Use the -i flag to see what would be restored before restoring it.
+
+Result:
+
+    {
+        "Untrashed": 17,
+        "Errors": 0
+    }
+
+
 {{< rem autogenerated options stop >}}
 
 ### Limitations ###
diff --git a/docs/content/dropbox.md b/docs/content/dropbox.md
index 94ceb8581..bb93640ab 100644
--- a/docs/content/dropbox.md
+++ b/docs/content/dropbox.md
@@ -126,7 +126,7 @@ Here are the standard options specific to dropbox (Dropbox).
 
 #### --dropbox-client-id
 
-Dropbox App Client Id
+OAuth Client Id
 Leave blank normally.
 
 - Config:      client_id
@@ -136,7 +136,7 @@ Leave blank normally.
 
 #### --dropbox-client-secret
 
-Dropbox App Client Secret
+OAuth Client Secret
 Leave blank normally.
 
 - Config:      client_secret
@@ -148,6 +148,35 @@ Leave blank normally.
 
 Here are the advanced options specific to dropbox (Dropbox).
 
+#### --dropbox-token
+
+OAuth Access Token as a JSON blob.
+
+- Config:      token
+- Env Var:     RCLONE_DROPBOX_TOKEN
+- Type:        string
+- Default:     ""
+
+#### --dropbox-auth-url
+
+Auth server URL.
+Leave blank to use the provider defaults.
+
+- Config:      auth_url
+- Env Var:     RCLONE_DROPBOX_AUTH_URL
+- Type:        string
+- Default:     ""
+
+#### --dropbox-token-url
+
+Token server url.
+Leave blank to use the provider defaults.
+
+- Config:      token_url
+- Env Var:     RCLONE_DROPBOX_TOKEN_URL
+- Type:        string
+- Default:     ""
+
 #### --dropbox-chunk-size
 
 Upload chunk size. (< 150M).
diff --git a/docs/content/flags.md b/docs/content/flags.md
index e470b2338..d710580ef 100755
--- a/docs/content/flags.md
+++ b/docs/content/flags.md
@@ -19,6 +19,7 @@ These flags are available for every command.
       --bind string                          Local address to bind to for outgoing connections, IPv4, IPv6 or name.
       --buffer-size SizeSuffix               In memory buffer size when reading files for each --transfer. (default 16M)
       --bwlimit BwTimetable                  Bandwidth limit in kBytes/s, or use suffix b|k|M|G or a full timetable.
+      --bwlimit-file BwTimetable             Bandwidth limit per file in kBytes/s, or use suffix b|k|M|G or a full timetable.
       --ca-cert string                       CA certificate used to verify servers
       --cache-dir string                     Directory rclone will use for caching. (default "$HOME/.cache/rclone")
       --check-first                          Do all the checks before starting transfers.
@@ -64,6 +65,7 @@ These flags are available for every command.
       --immutable                            Do not modify files. Fail if existing files have been modified.
       --include stringArray                  Include files matching pattern
       --include-from stringArray             Read include patterns from file (use - to read from stdin)
+  -i, --interactive                          Enable interactive mode
       --log-file string                      Log everything to this file
       --log-format string                    Comma separated list of log format options (default "date,time")
       --log-level string                     Log level DEBUG|INFO|NOTICE|ERROR (default "NOTICE")
@@ -118,6 +120,7 @@ These flags are available for every command.
       --rc-web-gui-force-update              Force update to latest version of web gui
       --rc-web-gui-no-open-browser           Don't open the browser automatically
       --rc-web-gui-update                    Check and update to latest version of web gui
+      --refresh-times                        Refresh the modtime of remote files.
       --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)
       --size-only                            Skip based on size only, not mod-time or checksum
@@ -137,14 +140,14 @@ These flags are available for every command.
       --tpslimit float                       Limit HTTP transactions per second to this.
       --tpslimit-burst int                   Max burst of transactions for --tpslimit. (default 1)
       --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 (default "hash")
+      --track-renames-strategy string        Strategies to use when synchronizing using track-renames hash|modtime|leaf (default "hash")
       --transfers int                        Number of file transfers to run in parallel. (default 4)
   -u, --update                               Skip files that are newer on the destination.
       --use-cookies                          Enable session cookiejar.
       --use-json-log                         Use json log format.
       --use-mmap                             Use mmap allocator (see docs).
       --use-server-modtime                   Use server modified time instead of object metadata
-      --user-agent string                    Set the user-agent to a specified string. The default is rclone/ version (default "rclone/v1.52.0")
+      --user-agent string                    Set the user-agent to a specified string. The default is rclone/ version (default "rclone/v1.53.0")
   -v, --verbose count                        Print lots more stuff (repeat for more)
 ```
 
@@ -155,10 +158,11 @@ and may be set in the config file.
 
 ```
       --acd-auth-url string                                      Auth server URL.
-      --acd-client-id string                                     Amazon Application Client ID.
-      --acd-client-secret string                                 Amazon Application Client Secret.
+      --acd-client-id string                                     OAuth Client Id
+      --acd-client-secret string                                 OAuth Client Secret
       --acd-encoding MultiEncoder                                This sets the encoding for the backend. (default Slash,InvalidUtf8,Dot)
       --acd-templink-threshold SizeSuffix                        Files >= this size will be downloaded via their tempLink. (default 9G)
+      --acd-token string                                         OAuth Access Token as a JSON blob.
       --acd-token-url string                                     Token server url.
       --acd-upload-wait-per-gb Duration                          Additional time per GB to wait after a failed complete upload to see if it appears. (default 3m0s)
       --alias-remote string                                      Remote or path to alias.
@@ -177,6 +181,7 @@ and may be set in the config file.
       --azureblob-use-emulator                                   Uses local storage emulator if provided as 'true' (leave blank if using real azure storage endpoint)
       --b2-account string                                        Account ID or Application Key ID
       --b2-chunk-size SizeSuffix                                 Upload chunk size. Must fit in memory. (default 96M)
+      --b2-copy-cutoff SizeSuffix                                Cutoff for switching to multipart copy (default 4G)
       --b2-disable-checksum                                      Disable checksums for large (> upload cutoff) files
       --b2-download-auth-duration Duration                       Time before the authorization token will expire in s or suffix ms|s|m|h|d. (default 1w)
       --b2-download-url string                                   Custom endpoint for downloads.
@@ -184,16 +189,22 @@ and may be set in the config file.
       --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-memory-pool-flush-time Duration                       How often internal memory buffer pools will be flushed. (default 1m0s)
+      --b2-memory-pool-use-mmap                                  Whether to use mmap buffers in internal memory pool.
       --b2-test-mode string                                      A flag string for X-Bz-Test-Mode header for debugging.
       --b2-upload-cutoff SizeSuffix                              Cutoff for switching to chunked upload. (default 200M)
       --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 "user")
-      --box-client-id string                                     Box App Client Id.
-      --box-client-secret string                                 Box App Client Secret
+      --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-encoding MultiEncoder                                This sets the encoding for the backend. (default Slash,BackSlash,Del,Ctl,RightSpace,InvalidUtf8,Dot)
       --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 (>= 50MB). (default 50M)
       --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.
@@ -205,7 +216,7 @@ and may be set in the config file.
       --cache-db-wait-time Duration                              How long to wait for the DB to be available - 0 is unlimited (default 1s)
       --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
+      --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)
@@ -225,17 +236,18 @@ and may be set in the config file.
   -L, --copy-links                                               Follow symlinks and copy the pointed to item.
       --crypt-directory-name-encryption                          Option to either encrypt directory names or leave them intact. (default true)
       --crypt-filename-encryption string                         How to encrypt the filenames. (default "standard")
-      --crypt-password string                                    Password or pass phrase for encryption.
-      --crypt-password2 string                                   Password or pass phrase for salt. Optional but recommended.
+      --crypt-password string                                    Password or pass phrase for encryption. (obscured)
+      --crypt-password2 string                                   Password or pass phrase for salt. Optional but recommended. (obscured)
       --crypt-remote string                                      Remote to encrypt/decrypt.
+      --crypt-server-side-across-configs                         Allow server side operations (eg copy) to work across different crypt configs.
       --crypt-show-mapping                                       For all files listed show how the names encrypt.
       --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 (e.g. file.doc to file.docx). This will confuse sync and reupload every time.
-      --drive-alternate-export                                   Use alternate export URLs for google documents export.,
       --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. Must a power of 2 >= 256k. (default 8M)
-      --drive-client-id string                                   Google Application Client Id
-      --drive-client-secret string                               Google Application Client Secret
+      --drive-client-id string                                   OAuth Client Id
+      --drive-client-secret string                               OAuth Client Secret
       --drive-disable-http2                                      Disable drive using http2 (default true)
       --drive-encoding MultiEncoder                              This sets the encoding for the backend. (default InvalidUtf8)
       --drive-export-formats string                              Comma separated list of preferred formats for downloading Google docs. (default "docx,xlsx,pptx,svg")
@@ -256,65 +268,81 @@ and may be set in the config file.
       --drive-skip-checksum-gphotos                              Skip MD5 checksum on Google photos and videos only.
       --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-upload-limit                               Make upload limit errors be fatal
       --drive-team-drive string                                  ID of the 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 8M)
       --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's are greater, use drive v2 API to download. (default off)
+      --dropbox-auth-url string                                  Auth server URL.
       --dropbox-chunk-size SizeSuffix                            Upload chunk size. (< 150M). (default 48M)
-      --dropbox-client-id string                                 Dropbox App Client Id
-      --dropbox-client-secret string                             Dropbox App Client Secret
+      --dropbox-client-id string                                 OAuth Client Id
+      --dropbox-client-secret string                             OAuth Client Secret
       --dropbox-encoding MultiEncoder                            This sets the encoding for the backend. (default Slash,BackSlash,Del,RightSpace,InvalidUtf8,Dot)
       --dropbox-impersonate string                               Impersonate this user when using a business account.
+      --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-encoding MultiEncoder                            This sets the encoding for the backend. (default Slash,LtGt,DoubleQuote,SingleQuote,BackQuote,Dollar,BackSlash,Del,Ctl,LeftSpace,RightSpace,InvalidUtf8,Dot)
       --fichier-shared-folder string                             If you want to download a shared folder, add this parameter
       --ftp-concurrency int                                      Maximum number of FTP simultaneous connections, 0 for unlimited
       --ftp-disable-epsv                                         Disable using EPSV even if server advertises support
       --ftp-encoding MultiEncoder                                This sets the encoding for the backend. (default Slash,Del,Ctl,RightSpace,Dot)
+      --ftp-explicit-tls                                         Use FTP over TLS (Explicit)
       --ftp-host string                                          FTP host to connect to
       --ftp-no-check-certificate                                 Do not verify the TLS certificate of the server
-      --ftp-pass string                                          FTP password
+      --ftp-pass string                                          FTP password (obscured)
       --ftp-port string                                          FTP port, leave blank to use default (21)
-      --ftp-tls                                                  Use FTP over TLS (Implicit)
+      --ftp-tls                                                  Use FTPS over TLS (Implicit)
       --ftp-user string                                          FTP username, leave blank for current username, $USER
+      --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                                     Google Application Client Id
-      --gcs-client-secret string                                 Google Application Client Secret
+      --gcs-client-id string                                     OAuth Client Id
+      --gcs-client-secret string                                 OAuth Client Secret
       --gcs-encoding MultiEncoder                                This sets the encoding for the backend. (default Slash,CrLf,InvalidUtf8,Dot)
       --gcs-location string                                      Location for the newly created buckets.
       --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.
-      --gphotos-client-id string                                 Google Application Client Id
-      --gphotos-client-secret string                             Google Application Client Secret
+      --gcs-token string                                         OAuth Access Token as a JSON blob.
+      --gcs-token-url string                                     Token server url.
+      --gphotos-auth-url string                                  Auth server URL.
+      --gphotos-client-id string                                 OAuth Client Id
+      --gphotos-client-secret string                             OAuth Client Secret
       --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.
       --http-headers CommaSepList                                Set HTTP headers for all transactions
       --http-no-head                                             Don't use HEAD requests to find file sizes in dir listing
       --http-no-slash                                            Set this if the site doesn't end directories with /
       --http-url string                                          URL of http host to connect to
+      --hubic-auth-url string                                    Auth server URL.
       --hubic-chunk-size SizeSuffix                              Above this size files will be chunked into a _segments container. (default 5G)
-      --hubic-client-id string                                   Hubic Client Id
-      --hubic-client-secret string                               Hubic Client Secret
+      --hubic-client-id string                                   OAuth Client Id
+      --hubic-client-secret string                               OAuth Client Secret
       --hubic-encoding MultiEncoder                              This sets the encoding for the backend. (default Slash,InvalidUtf8)
       --hubic-no-chunk                                           Don't chunk files during streaming upload.
+      --hubic-token string                                       OAuth Access Token as a JSON blob.
+      --hubic-token-url string                                   Token server url.
       --jottacloud-encoding MultiEncoder                         This sets 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 10M)
       --jottacloud-trashed-only                                  Only show files that are in the trash.
-      --jottacloud-unlink                                        Remove existing public link to file/folder with link command rather than creating.
       --jottacloud-upload-resume-limit SizeSuffix                Files bigger than this can be resumed if the upload fail's. (default 10M)
       --koofr-encoding MultiEncoder                              This sets the encoding for the backend. (default Slash,BackSlash,Del,Ctl,InvalidUtf8,Dot)
       --koofr-endpoint string                                    The Koofr API endpoint to use (default "https://app.koofr.net")
       --koofr-mountid string                                     Mount ID of the mount to use. If omitted, the primary mount is used.
-      --koofr-password string                                    Your Koofr password for rclone (generate one at https://app.koofr.net/app/admin/preferences/password)
+      --koofr-password string                                    Your Koofr password for rclone (generate one at https://app.koofr.net/app/admin/preferences/password) (obscured)
       --koofr-setmtime                                           Does the backend support setting modification time. Set this to false if you use a mount ID that points to a Dropbox or Amazon Drive backend. (default true)
       --koofr-user string                                        Your Koofr user name
   -l, --links                                                    Translate symlinks to/from regular files with a '.rclonelink' extension
@@ -322,12 +350,13 @@ and may be set in the config file.
       --local-case-sensitive                                     Force the filesystem to report itself as case sensitive.
       --local-encoding MultiEncoder                              This sets the encoding for the backend. (default Slash,Dot)
       --local-no-check-updated                                   Don't check to see if the files change during upload
+      --local-no-set-modtime                                     Disable setting modtime
       --local-no-sparse                                          Disable sparse files for multi-thread downloads
       --local-no-unicode-normalization                           Don't apply unicode normalization to paths and filenames (Deprecated)
       --local-nounc string                                       Disable UNC (long path names) conversion on Windows
       --mailru-check-hash                                        What should copy do if file checksum is mismatched or invalid (default true)
       --mailru-encoding MultiEncoder                             This sets the encoding for the backend. (default Slash,LtGt,DoubleQuote,Colon,Question,Asterisk,Pipe,BackSlash,Del,Ctl,InvalidUtf8,Dot)
-      --mailru-pass string                                       Password
+      --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 "*.mkv,*.avi,*.mp4,*.mp3,*.zip,*.gz,*.rar,*.pdf")
       --mailru-speedup-max-disk SizeSuffix                       This option allows you to disable speedup (put by hash) for large files (default 3G)
@@ -336,25 +365,33 @@ and may be set in the config file.
       --mega-debug                                               Output more debug from Mega.
       --mega-encoding MultiEncoder                               This sets 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.
+      --mega-pass string                                         Password. (obscured)
       --mega-user string                                         User name
   -x, --one-file-system                                          Don't cross filesystem boundaries (unix/macOS only).
+      --onedrive-auth-url string                                 Auth server URL.
       --onedrive-chunk-size SizeSuffix                           Chunk size to upload files with - must be multiple of 320k (327,680 bytes). (default 10M)
-      --onedrive-client-id string                                Microsoft App Client Id
-      --onedrive-client-secret string                            Microsoft App Client Secret
+      --onedrive-client-id string                                OAuth Client Id
+      --onedrive-client-secret string                            OAuth Client Secret
       --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 MultiEncoder                           This sets the encoding for the backend. (default Slash,LtGt,DoubleQuote,Colon,Question,Asterisk,Pipe,Hash,Percent,BackSlash,Del,Ctl,LeftSpace,LeftTilde,RightSpace,RightPeriod,InvalidUtf8,Dot)
       --onedrive-expose-onenote-files                            Set to make OneNote files show up in directory listings.
+      --onedrive-no-versions                                     Remove all versions on modifying operations
       --onedrive-server-side-across-configs                      Allow server side operations (eg copy) to work across different onedrive configs.
+      --onedrive-token string                                    OAuth Access Token as a JSON blob.
+      --onedrive-token-url string                                Token server url.
       --opendrive-chunk-size SizeSuffix                          Files will be uploaded in chunks this size. (default 10M)
       --opendrive-encoding MultiEncoder                          This sets the encoding for the backend. (default Slash,LtGt,DoubleQuote,Colon,Question,Asterisk,Pipe,BackSlash,LeftSpace,LeftCrLfHtVt,RightSpace,RightCrLfHtVt,InvalidUtf8,Dot)
-      --opendrive-password string                                Password.
+      --opendrive-password string                                Password. (obscured)
       --opendrive-username string                                Username
-      --pcloud-client-id string                                  Pcloud App Client Id
-      --pcloud-client-secret string                              Pcloud App Client Secret
+      --pcloud-auth-url string                                   Auth server URL.
+      --pcloud-client-id string                                  OAuth Client Id
+      --pcloud-client-secret string                              OAuth Client Secret
       --pcloud-encoding MultiEncoder                             This sets the encoding for the backend. (default Slash,BackSlash,Del,Ctl,InvalidUtf8,Dot)
+      --pcloud-hostname string                                   Hostname to connect to. (default "api.pcloud.com")
       --pcloud-root-folder-id string                             Fill in for rclone to use a non root folder as its starting point. (default "d0")
+      --pcloud-token string                                      OAuth Access Token as a JSON blob.
+      --pcloud-token-url string                                  Token server url.
       --premiumizeme-encoding MultiEncoder                       This sets the encoding for the backend. (default Slash,DoubleQuote,BackSlash,Del,Ctl,InvalidUtf8,Dot)
       --putio-encoding MultiEncoder                              This sets the encoding for the backend. (default Slash,BackSlash,Del,Ctl,InvalidUtf8,Dot)
       --qingstor-access-key-id string                            QingStor Access Key ID
@@ -371,7 +408,7 @@ and may be set in the config file.
       --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 5M)
-      --s3-copy-cutoff SizeSuffix                                Cutoff for switching to multipart copy (default 5G)
+      --s3-copy-cutoff SizeSuffix                                Cutoff for switching to multipart copy (default 4.656G)
       --s3-disable-checksum                                      Don't store MD5 checksum with object metadata
       --s3-encoding MultiEncoder                                 This sets the encoding for the backend. (default Slash,InvalidUtf8,Dot)
       --s3-endpoint string                                       Endpoint for S3 API.
@@ -380,13 +417,17 @@ and may be set in the config file.
       --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-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-memory-pool-flush-time Duration                       How often internal memory buffer pools will be flushed. (default 1m0s)
       --s3-memory-pool-use-mmap                                  Whether to use mmap buffers in internal memory pool.
+      --s3-no-check-bucket                                       If set don't attempt to check the bucket exists or create it
+      --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-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                               If using SSE-C you must provide the secret encryption key used to encrypt/decrypt your data.
       --s3-sse-customer-key-md5 string                           If using SSE-C you must provide the secret encryption key MD5 checksum.
@@ -400,24 +441,26 @@ and may be set in the config file.
       --seafile-create-library                                   Should rclone create a library if it doesn't exist
       --seafile-encoding MultiEncoder                            This sets the encoding for the backend. (default Slash,DoubleQuote,BackSlash,Ctl,InvalidUtf8)
       --seafile-library string                                   Name of the library. Leave blank to access all non-encrypted libraries.
-      --seafile-library-key string                               Library password (for encrypted libraries only). Leave blank if you pass it through the command line.
-      --seafile-pass string                                      Password
+      --seafile-library-key string                               Library password (for encrypted libraries only). Leave blank if you pass it through the command line. (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-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-key-file string                                     Path to PEM-encoded private key file, leave blank or set key-use-agent to use ssh-agent.
-      --sftp-key-file-pass string                                The passphrase to decrypt the 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, If specified, will override key_file parameter.
       --sftp-key-use-agent                                       When set forces the usage of the ssh-agent.
       --sftp-md5sum-command string                               The command used to read md5 hashes. Leave blank for autodetect.
-      --sftp-pass string                                         SSH password, leave blank to use ssh-agent.
+      --sftp-pass string                                         SSH password, leave blank to use ssh-agent. (obscured)
       --sftp-path-override string                                Override path used by SSH connection.
       --sftp-port string                                         SSH port, leave blank to use default (22)
+      --sftp-server-command string                               Specifies the path or command to run a sftp server on the remote host.
       --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. Leave blank for autodetect.
       --sftp-skip-links                                          Set to skip any symlinks and any other non regular files.
+      --sftp-subsystem string                                    Specifies the SSH2 subsystem on the remote host. (default "sftp")
       --sftp-use-insecure-cipher                                 Enable the use of insecure ciphers and key exchange methods.
       --sftp-user string                                         SSH username, leave blank for current username, ncw
       --sharefile-chunk-size SizeSuffix                          Upload chunk size. Must a power of 2 >= 256k. (default 64M)
@@ -470,12 +513,14 @@ and may be set in the config file.
       --union-upstreams string                                   List of space separated upstreams.
       --webdav-bearer-token string                               Bearer token instead of user/pass (eg a Macaroon)
       --webdav-bearer-token-command string                       Command to run to get a bearer token
-      --webdav-pass string                                       Password.
+      --webdav-pass string                                       Password. (obscured)
       --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-client-id string                                  Yandex Client Id
-      --yandex-client-secret string                              Yandex Client Secret
+      --yandex-auth-url string                                   Auth server URL.
+      --yandex-client-id string                                  OAuth Client Id
+      --yandex-client-secret string                              OAuth Client Secret
       --yandex-encoding MultiEncoder                             This sets the encoding for the backend. (default Slash,Del,Ctl,InvalidUtf8,Dot)
-      --yandex-unlink                                            Remove existing public link to file/folder with link command rather than creating.
+      --yandex-token string                                      OAuth Access Token as a JSON blob.
+      --yandex-token-url string                                  Token server url.
 ```
diff --git a/docs/content/ftp.md b/docs/content/ftp.md
index 3e110a628..baf2d69e0 100644
--- a/docs/content/ftp.md
+++ b/docs/content/ftp.md
@@ -179,6 +179,8 @@ FTP port, leave blank to use default (21)
 
 FTP password
 
+**NB** Input to this must be obscured - see [rclone obscure](/commands/rclone_obscure/).
+
 - Config:      pass
 - Env Var:     RCLONE_FTP_PASS
 - Type:        string
@@ -186,8 +188,7 @@ FTP password
 
 #### --ftp-tls
 
-Use FTP over TLS (Implicit)
-
+Use FTPS over TLS (Implicit)
 When using implicit FTP over TLS the client will connect using TLS
 right from the start, which in turn breaks the compatibility with
 non-TLS-aware servers. This is usually served over port 990 rather
@@ -201,13 +202,12 @@ than port 21. Cannot be used in combination with explicit FTP.
 #### --ftp-explicit-tls
 
 Use FTP over TLS (Explicit)
-
 When using explicit FTP over TLS the client explicitly request
 security from the server in order to upgrade a plain text connection
 to an encrypted one. Cannot be used in combination with implicit FTP.
 
 - Config:      explicit_tls
-- Env Var:     RCLONE_FTP_TLS
+- Env Var:     RCLONE_FTP_EXPLICIT_TLS
 - Type:        bool
 - Default:     false
 
diff --git a/docs/content/googlecloudstorage.md b/docs/content/googlecloudstorage.md
index 3408ccfd6..ae60d8527 100644
--- a/docs/content/googlecloudstorage.md
+++ b/docs/content/googlecloudstorage.md
@@ -264,7 +264,7 @@ Here are the standard options specific to google cloud storage (Google Cloud Sto
 
 #### --gcs-client-id
 
-Google Application Client Id
+OAuth Client Id
 Leave blank normally.
 
 - Config:      client_id
@@ -274,7 +274,7 @@ Leave blank normally.
 
 #### --gcs-client-secret
 
-Google Application Client Secret
+OAuth Client Secret
 Leave blank normally.
 
 - Config:      client_secret
@@ -298,6 +298,9 @@ Service Account Credentials JSON file path
 Leave blank normally.
 Needed only if you want use SA instead of interactive login.
 
+Leading `~` will be expanded in the file name as will environment variables such as `${RCLONE_CONFIG_DIR}`.
+
+
 - Config:      service_account_file
 - Env Var:     RCLONE_GCS_SERVICE_ACCOUNT_FILE
 - Type:        string
@@ -314,6 +317,16 @@ Needed only if you want use SA instead of interactive login.
 - Type:        string
 - Default:     ""
 
+#### --gcs-anonymous
+
+Access public buckets and objects without credentials
+Set to 'true' if you just want to download files and don't configure credentials.
+
+- Config:      anonymous
+- Env Var:     RCLONE_GCS_ANONYMOUS
+- Type:        bool
+- Default:     false
+
 #### --gcs-object-acl
 
 Access Control List for new objects.
@@ -455,6 +468,35 @@ The storage class to use when storing objects in Google Cloud Storage.
 
 Here are the advanced options specific to google cloud storage (Google Cloud Storage (this is not Google Drive)).
 
+#### --gcs-token
+
+OAuth Access Token as a JSON blob.
+
+- Config:      token
+- Env Var:     RCLONE_GCS_TOKEN
+- Type:        string
+- Default:     ""
+
+#### --gcs-auth-url
+
+Auth server URL.
+Leave blank to use the provider defaults.
+
+- Config:      auth_url
+- Env Var:     RCLONE_GCS_AUTH_URL
+- Type:        string
+- Default:     ""
+
+#### --gcs-token-url
+
+Token server url.
+Leave blank to use the provider defaults.
+
+- Config:      token_url
+- Env Var:     RCLONE_GCS_TOKEN_URL
+- Type:        string
+- Default:     ""
+
 #### --gcs-encoding
 
 This sets the encoding for the backend.
diff --git a/docs/content/googlephotos.md b/docs/content/googlephotos.md
index 51def918a..452f10122 100644
--- a/docs/content/googlephotos.md
+++ b/docs/content/googlephotos.md
@@ -315,7 +315,7 @@ Here are the standard options specific to google photos (Google Photos).
 
 #### --gphotos-client-id
 
-Google Application Client Id
+OAuth Client Id
 Leave blank normally.
 
 - Config:      client_id
@@ -325,7 +325,7 @@ Leave blank normally.
 
 #### --gphotos-client-secret
 
-Google Application Client Secret
+OAuth Client Secret
 Leave blank normally.
 
 - Config:      client_secret
@@ -349,6 +349,35 @@ to your photos, otherwise rclone will request full access.
 
 Here are the advanced options specific to google photos (Google Photos).
 
+#### --gphotos-token
+
+OAuth Access Token as a JSON blob.
+
+- Config:      token
+- Env Var:     RCLONE_GPHOTOS_TOKEN
+- Type:        string
+- Default:     ""
+
+#### --gphotos-auth-url
+
+Auth server URL.
+Leave blank to use the provider defaults.
+
+- Config:      auth_url
+- Env Var:     RCLONE_GPHOTOS_AUTH_URL
+- Type:        string
+- Default:     ""
+
+#### --gphotos-token-url
+
+Token server url.
+Leave blank to use the provider defaults.
+
+- Config:      token_url
+- Env Var:     RCLONE_GPHOTOS_TOKEN_URL
+- Type:        string
+- Default:     ""
+
 #### --gphotos-read-size
 
 Set to read the size of media items.
diff --git a/docs/content/hubic.md b/docs/content/hubic.md
index 9061d90a5..989bdcf7a 100644
--- a/docs/content/hubic.md
+++ b/docs/content/hubic.md
@@ -112,7 +112,7 @@ Here are the standard options specific to hubic (Hubic).
 
 #### --hubic-client-id
 
-Hubic Client Id
+OAuth Client Id
 Leave blank normally.
 
 - Config:      client_id
@@ -122,7 +122,7 @@ Leave blank normally.
 
 #### --hubic-client-secret
 
-Hubic Client Secret
+OAuth Client Secret
 Leave blank normally.
 
 - Config:      client_secret
@@ -134,6 +134,35 @@ Leave blank normally.
 
 Here are the advanced options specific to hubic (Hubic).
 
+#### --hubic-token
+
+OAuth Access Token as a JSON blob.
+
+- Config:      token
+- Env Var:     RCLONE_HUBIC_TOKEN
+- Type:        string
+- Default:     ""
+
+#### --hubic-auth-url
+
+Auth server URL.
+Leave blank to use the provider defaults.
+
+- Config:      auth_url
+- Env Var:     RCLONE_HUBIC_AUTH_URL
+- Type:        string
+- Default:     ""
+
+#### --hubic-token-url
+
+Token server url.
+Leave blank to use the provider defaults.
+
+- Config:      token_url
+- Env Var:     RCLONE_HUBIC_TOKEN_URL
+- Type:        string
+- Default:     ""
+
 #### --hubic-chunk-size
 
 Above this size files will be chunked into a _segments container.
diff --git a/docs/content/jottacloud.md b/docs/content/jottacloud.md
index 61068cd2f..f65eafe3b 100644
--- a/docs/content/jottacloud.md
+++ b/docs/content/jottacloud.md
@@ -220,16 +220,6 @@ Delete files permanently rather than putting them into the trash.
 - Type:        bool
 - Default:     false
 
-#### --jottacloud-unlink
-
-Remove existing public link to file/folder with link command rather than creating.
-Default is false, meaning link command will create or retrieve public link.
-
-- Config:      unlink
-- Env Var:     RCLONE_JOTTACLOUD_UNLINK
-- Type:        bool
-- Default:     false
-
 #### --jottacloud-upload-resume-limit
 
 Files bigger than this can be resumed if the upload fail's.
diff --git a/docs/content/koofr.md b/docs/content/koofr.md
index 309427858..4096a5918 100644
--- a/docs/content/koofr.md
+++ b/docs/content/koofr.md
@@ -115,6 +115,8 @@ Your Koofr user name
 
 Your Koofr password for rclone (generate one at https://app.koofr.net/app/admin/preferences/password)
 
+**NB** Input to this must be obscured - see [rclone obscure](/commands/rclone_obscure/).
+
 - Config:      password
 - Env Var:     RCLONE_KOOFR_PASSWORD
 - Type:        string
diff --git a/docs/content/local.md b/docs/content/local.md
index c0da9a961..60060ecef 100644
--- a/docs/content/local.md
+++ b/docs/content/local.md
@@ -372,6 +372,23 @@ However on some file systems this modification time check may fail (eg
 [Glusterfs #2206](https://github.com/rclone/rclone/issues/2206)) so this
 check can be disabled with this flag.
 
+If this flag is set, rclone will use its best efforts to transfer a
+file which is being updated. If the file is only having things
+appended to it (eg a log) then rclone will transfer the log file with
+the size it had the first time rclone saw it.
+
+If the file is being modified throughout (not just appended to) then
+the transfer may fail with a hash check failure.
+
+In detail, once the file has had stat() called on it for the first
+time we:
+
+- Only transfer the size that stat gave
+- Only checksum the size that stat gave
+- Don't update the stat info for the file
+
+
+
 - Config:      no_check_updated
 - Env Var:     RCLONE_LOCAL_NO_CHECK_UPDATED
 - Type:        bool
@@ -426,6 +443,21 @@ cause disk fragmentation and can be slow to work with.
 - Type:        bool
 - Default:     false
 
+#### --local-no-set-modtime
+
+Disable setting modtime
+
+Normally rclone updates modification time of files after they are done
+uploading. This can cause permissions issues on Linux platforms when 
+the user rclone is running as does not own the file uploaded, such as
+when copying to a CIFS mount owned by another user. If this option is 
+enabled, rclone will no longer update the modtime after copying a file.
+
+- Config:      no_set_modtime
+- Env Var:     RCLONE_LOCAL_NO_SET_MODTIME
+- Type:        bool
+- Default:     false
+
 #### --local-encoding
 
 This sets the encoding for the backend.
diff --git a/docs/content/mailru.md b/docs/content/mailru.md
index ba9577301..090332f70 100644
--- a/docs/content/mailru.md
+++ b/docs/content/mailru.md
@@ -181,6 +181,8 @@ User name (usually email)
 
 Password
 
+**NB** Input to this must be obscured - see [rclone obscure](/commands/rclone_obscure/).
+
 - Config:      pass
 - Env Var:     RCLONE_MAILRU_PASS
 - Type:        string
diff --git a/docs/content/mega.md b/docs/content/mega.md
index dfdfeed40..9cee961ba 100644
--- a/docs/content/mega.md
+++ b/docs/content/mega.md
@@ -168,6 +168,8 @@ User name
 
 Password.
 
+**NB** Input to this must be obscured - see [rclone obscure](/commands/rclone_obscure/).
+
 - Config:      pass
 - Env Var:     RCLONE_MEGA_PASS
 - Type:        string
diff --git a/docs/content/onedrive.md b/docs/content/onedrive.md
index 330f7476b..7452f039f 100644
--- a/docs/content/onedrive.md
+++ b/docs/content/onedrive.md
@@ -199,7 +199,7 @@ Here are the standard options specific to onedrive (Microsoft OneDrive).
 
 #### --onedrive-client-id
 
-Microsoft App Client Id
+OAuth Client Id
 Leave blank normally.
 
 - Config:      client_id
@@ -209,7 +209,7 @@ Leave blank normally.
 
 #### --onedrive-client-secret
 
-Microsoft App Client Secret
+OAuth Client Secret
 Leave blank normally.
 
 - Config:      client_secret
@@ -221,6 +221,35 @@ Leave blank normally.
 
 Here are the advanced options specific to onedrive (Microsoft OneDrive).
 
+#### --onedrive-token
+
+OAuth Access Token as a JSON blob.
+
+- Config:      token
+- Env Var:     RCLONE_ONEDRIVE_TOKEN
+- Type:        string
+- Default:     ""
+
+#### --onedrive-auth-url
+
+Auth server URL.
+Leave blank to use the provider defaults.
+
+- Config:      auth_url
+- Env Var:     RCLONE_ONEDRIVE_AUTH_URL
+- Type:        string
+- Default:     ""
+
+#### --onedrive-token-url
+
+Token server url.
+Leave blank to use the provider defaults.
+
+- Config:      token_url
+- Env Var:     RCLONE_ONEDRIVE_TOKEN_URL
+- Type:        string
+- Default:     ""
+
 #### --onedrive-chunk-size
 
 Chunk size to upload files with - must be multiple of 320k (327,680 bytes).
@@ -281,6 +310,27 @@ configurations.
 - Type:        bool
 - Default:     false
 
+#### --onedrive-no-versions
+
+Remove all versions on modifying operations
+
+Onedrive for business creates versions when rclone uploads new files
+overwriting an existing one and when it sets the modification time.
+
+These versions take up space out of the quota.
+
+This flag checks for versions after file upload and setting
+modification time and removes all but the last version.
+
+**NB** Onedrive personal can't currently delete versions so don't use
+this flag there.
+
+
+- Config:      no_versions
+- Env Var:     RCLONE_ONEDRIVE_NO_VERSIONS
+- Type:        bool
+- Default:     false
+
 #### --onedrive-encoding
 
 This sets the encoding for the backend.
diff --git a/docs/content/opendrive.md b/docs/content/opendrive.md
index b4371a919..2c5c5d12e 100644
--- a/docs/content/opendrive.md
+++ b/docs/content/opendrive.md
@@ -116,6 +116,8 @@ Username
 
 Password.
 
+**NB** Input to this must be obscured - see [rclone obscure](/commands/rclone_obscure/).
+
 - Config:      password
 - Env Var:     RCLONE_OPENDRIVE_PASSWORD
 - Type:        string
diff --git a/docs/content/pcloud.md b/docs/content/pcloud.md
index 31fe91dc7..d4160439e 100644
--- a/docs/content/pcloud.md
+++ b/docs/content/pcloud.md
@@ -140,7 +140,7 @@ Here are the standard options specific to pcloud (Pcloud).
 
 #### --pcloud-client-id
 
-Pcloud App Client Id
+OAuth Client Id
 Leave blank normally.
 
 - Config:      client_id
@@ -150,7 +150,7 @@ Leave blank normally.
 
 #### --pcloud-client-secret
 
-Pcloud App Client Secret
+OAuth Client Secret
 Leave blank normally.
 
 - Config:      client_secret
@@ -162,6 +162,35 @@ Leave blank normally.
 
 Here are the advanced options specific to pcloud (Pcloud).
 
+#### --pcloud-token
+
+OAuth Access Token as a JSON blob.
+
+- Config:      token
+- Env Var:     RCLONE_PCLOUD_TOKEN
+- Type:        string
+- Default:     ""
+
+#### --pcloud-auth-url
+
+Auth server URL.
+Leave blank to use the provider defaults.
+
+- Config:      auth_url
+- Env Var:     RCLONE_PCLOUD_AUTH_URL
+- Type:        string
+- Default:     ""
+
+#### --pcloud-token-url
+
+Token server url.
+Leave blank to use the provider defaults.
+
+- Config:      token_url
+- Env Var:     RCLONE_PCLOUD_TOKEN_URL
+- Type:        string
+- Default:     ""
+
 #### --pcloud-encoding
 
 This sets the encoding for the backend.
@@ -182,4 +211,23 @@ Fill in for rclone to use a non root folder as its starting point.
 - Type:        string
 - Default:     "d0"
 
+#### --pcloud-hostname
+
+Hostname to connect to.
+
+This is normally set when rclone initially does the oauth connection,
+however you will need to set it by hand if you are using remote config
+with rclone authorize.
+
+
+- Config:      hostname
+- Env Var:     RCLONE_PCLOUD_HOSTNAME
+- Type:        string
+- Default:     "api.pcloud.com"
+- Examples:
+    - "api.pcloud.com"
+        - Original/US region
+    - "eapi.pcloud.com"
+        - EU region
+
 {{< rem autogenerated options stop >}}
diff --git a/docs/content/rc.md b/docs/content/rc.md
index ee9f08fa2..5fa7a2835 100644
--- a/docs/content/rc.md
+++ b/docs/content/rc.md
@@ -504,6 +504,41 @@ except only one bandwidth may be specified.
 In either case "rate" is returned as a human readable string, and
 "bytesPerSecond" is returned as a number.
 
+### core/command: Run a rclone terminal command over rc. {#core-command}
+
+This takes the following parameters
+
+- command - a string with the command name
+- arg - a list of arguments for the backend command
+- opt - a map of string to string of options
+
+Returns
+
+- result - result from the backend command
+- error	 - set if rclone exits with an error code
+- returnType - one of ("COMBINED_OUTPUT", "STREAM", "STREAM_ONLY_STDOUT". "STREAM_ONLY_STDERR")
+
+For example
+
+    rclone rc core/command command=ls -a mydrive:/ -o max-depth=1
+	rclone rc core/command -a ls -a mydrive:/ -o max-depth=1
+
+Returns
+
+```
+{
+	"error": false,
+	"result": "<Raw command line output>"
+}
+
+OR 
+{
+	"error": true,
+	"result": "<Raw command line output>"
+}
+
+**Authentication is required for this call.**
+
 ### core/gc: Runs a garbage collection. {#core-gc}
 
 This tells the go runtime to do a garbage collection run.  It isn't
@@ -582,6 +617,7 @@ Returns the following values:
 	"transfers": number of transferred files,
 	"deletes" : number of deleted files,
 	"renames" : number of renamed files,
+	"transferTime" : total time spent on running jobs,
 	"elapsedTime": time in seconds since the start of the process,
 	"lastError": last occurred error,
 	"transferring": an array of currently active file transfers:
@@ -591,8 +627,8 @@ Returns the following values:
 				"eta": estimated time in seconds until file transfer completion
 				"name": name of the file,
 				"percentage": progress of the file transfer in percent,
-				"speed": speed in bytes/sec,
-				"speedAvg": speed in bytes/sec as an exponentially weighted moving average,
+				"speed": average speed over the whole transfer in bytes/sec,
+				"speedAvg": current speed in bytes/sec as an exponentially weighted moving average,
 				"size": size of the file in bytes
 			}
 		],
@@ -657,10 +693,10 @@ Returns the following values:
 
 This shows the current version of go and the go runtime
 
-- version - rclone version, eg "v1.44"
-- decomposed - version number as [major, minor, patch, subpatch]
-    - note patch and subpatch will be 999 for a git compiled version
+- version - rclone version, eg "v1.53.0"
+- decomposed - version number as [major, minor, patch]
 - isGit - boolean - true if this was compiled from the git version
+- isBeta - boolean - true if this is a beta version
 - os - OS in use as according to Go
 - arch - cpu architecture in use according to Go
 - goVersion - version of Go runtime in use
@@ -736,6 +772,20 @@ Parameters
 
 - jobid - id of the job (integer)
 
+### mount/listmounts: Show current mount points {#mount-listmounts}
+
+This shows currently mounted points, which can be used for performing an unmount
+
+This takes no parameters and returns
+
+- mountPoints: list of current mount points
+
+Eg
+
+    rclone rc mount/listmounts
+
+**Authentication is required for this call.**
+
 ### mount/mount: Create a new mount point {#mount-mount}
 
 rclone allows Linux, FreeBSD, macOS and Windows to mount any of
@@ -748,11 +798,19 @@ This takes the following parameters
 - fs - a remote path to be mounted (required)
 - mountPoint: valid path on the local machine (required)
 - mountType: One of the values (mount, cmount, mount2) specifies the mount implementation to use
+- mountOpt: a JSON object with Mount options in.
+- vfsOpt: a JSON object with VFS options in.
 
 Eg
 
     rclone rc mount/mount fs=mydrive: mountPoint=/home/<user>/mountPoint
     rclone rc mount/mount fs=mydrive: mountPoint=/home/<user>/mountPoint mountType=mount
+    rclone rc mount/mount fs=TestDrive: mountPoint=/mnt/tmp vfsOpt='{"CacheMode": 2}' mountOpt='{"AllowOther": true}'
+
+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.
+
+    rclone rc options/get
 
 **Authentication is required for this call.**
 
@@ -773,7 +831,7 @@ Eg
 
 **Authentication is required for this call.**
 
-### mount/unmount: Unmount all active mounts {#mount-unmount}
+### mount/unmount: Unmount selected active mount {#mount-unmount}
 
 rclone allows Linux, FreeBSD, macOS and Windows to
 mount any of Rclone's cloud storage systems as a file system with
@@ -789,6 +847,18 @@ Eg
 
 **Authentication is required for this call.**
 
+### mount/unmountall: Show current mount points {#mount-unmountall}
+
+This shows currently mounted points, which can be used for performing an unmount
+
+This takes no parameters and returns error if unmount does not succeed.
+
+Eg
+
+    rclone rc mount/unmountall
+
+**Authentication is required for this call.**
+
 ### operations/about: Return the space used on the remote {#operations-about}
 
 This takes the following parameters
@@ -962,6 +1032,8 @@ This takes the following parameters
 
 - fs - a remote name string eg "drive:"
 - remote - a path within that remote eg "dir"
+- unlink - boolean - if set removes the link rather than adding it (optional)
+- expire - string - the expiry time of the link eg "1d" (optional)
 
 Returns
 
@@ -1020,6 +1092,17 @@ See the [size command](/commands/rclone_size/) command for more information on t
 
 **Authentication is required for this call.**
 
+### operations/uploadfile: Upload file using multiform/form-data {#operations-uploadfile}
+
+This takes the following parameters
+
+- fs - a remote name string eg "drive:"
+- remote - a path within that remote eg "dir"
+- each part in body represents a file to be uploaded
+See the [uploadfile command](/commands/rclone_uploadfile/) command for more information on the above.
+
+**Authentication is required for this call.**
+
 ### options/blocks: List all the option blocks {#options-blocks}
 
 Returns
@@ -1060,6 +1143,97 @@ And this sets NOTICE level logs (normal without -v)
 
     rclone rc options/set --json '{"main": {"LogLevel": 6}}'
 
+### pluginsctl/addPlugin: Add a plugin using url {#pluginsctl-addPlugin}
+
+used for adding a plugin to the webgui
+
+This takes the following parameters
+
+- url: http url of the github repo where the plugin is hosted (http://github.com/rclone/rclone-webui-react)
+
+Eg
+
+   rclone rc pluginsctl/addPlugin
+
+**Authentication is required for this call.**
+
+### pluginsctl/getPluginsForType: Get plugins with type criteria {#pluginsctl-getPluginsForType}
+
+This shows all possible plugins by a mime type
+
+This takes the following parameters
+
+- type: supported mime type by a loaded plugin eg (video/mp4, audio/mp3)
+- pluginType: filter plugins based on their type eg (DASHBOARD, FILE_HANDLER, TERMINAL) 
+
+and returns
+
+- loadedPlugins: list of current production plugins
+- testPlugins: list of temporarily loaded development plugins, usually running on a different server.
+
+Eg
+
+   rclone rc pluginsctl/getPluginsForType type=video/mp4
+
+**Authentication is required for this call.**
+
+### pluginsctl/listPlugins: Get the list of currently loaded plugins {#pluginsctl-listPlugins}
+
+This allows you to get the currently enabled plugins and their details.
+
+This takes no parameters and returns
+
+- loadedPlugins: list of current production plugins
+- testPlugins: list of temporarily loaded development plugins, usually running on a different server.
+
+Eg
+
+   rclone rc pluginsctl/listPlugins
+
+**Authentication is required for this call.**
+
+### pluginsctl/listTestPlugins: Show currently loaded test plugins {#pluginsctl-listTestPlugins}
+
+allows listing of test plugins with the rclone.test set to true in package.json of the plugin
+
+This takes no parameters and returns
+
+- loadedTestPlugins: list of currently available test plugins
+
+Eg
+
+    rclone rc pluginsctl/listTestPlugins
+
+**Authentication is required for this call.**
+
+### pluginsctl/removePlugin: Remove a loaded plugin {#pluginsctl-removePlugin}
+
+This allows you to remove a plugin using it's name
+
+This takes parameters
+
+- name: name of the plugin in the format <author>/<plugin_name>
+
+Eg
+
+   rclone rc pluginsctl/removePlugin name=rclone/video-plugin
+
+**Authentication is required for this call.**
+
+### pluginsctl/removeTestPlugin: Remove  a test plugin {#pluginsctl-removeTestPlugin}
+
+This allows you to remove a plugin using it's name
+
+This takes the following parameters
+
+- name: name of the plugin in the format <author>/<plugin_name>
+
+Eg
+
+    rclone rc pluginsctl/removeTestPlugin name=rclone/rclone-webui-react
+
+**Authentication is required for this call.**
+
 ### rc/error: This returns an error {#rc-error}
 
 This returns an error with the input as part of its error string.
@@ -1136,6 +1310,19 @@ parameter key starting with file will forget that file and any
 starting with dir will forget that dir, eg
 
     rclone rc vfs/forget file=hello file2=goodbye dir=home/junk
+ 
+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.
+
+### vfs/list: List active VFSes. {#vfs-list}
+
+This lists the active VFSes.
+
+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.
 
 ### vfs/poll-interval: Get the status or update the value of the poll-interval option. {#vfs-poll-interval}
 
@@ -1158,6 +1345,11 @@ not reached.
 If poll-interval is updated or disabled temporarily, some changes
 might not get picked up by the polling function, depending on the
 used remote.
+ 
+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.
 
 ### vfs/refresh: Refresh the directory cache. {#vfs-refresh}
 
@@ -1175,6 +1367,11 @@ starting with dir will refresh that directory, eg
 
 If the parameter recursive=true is given the whole directory tree
 will get refreshed. This refresh will use --fast-list if enabled.
+ 
+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.
 
 {{< rem autogenerated stop >}}
 
diff --git a/docs/content/s3.md b/docs/content/s3.md
index 4590e0aa6..7c3d6cf6d 100644
--- a/docs/content/s3.md
+++ b/docs/content/s3.md
@@ -482,6 +482,8 @@ Choose your S3 provider.
         - Minio Object Storage
     - "Netease"
         - Netease Object Storage (NOS)
+    - "Scaleway"
+        - Scaleway Object Storage
     - "StackPath"
         - StackPath Object Storage
     - "Wasabi"
@@ -585,6 +587,20 @@ Region to connect to.
 
 #### --s3-region
 
+Region to connect to.
+
+- Config:      region
+- Env Var:     RCLONE_S3_REGION
+- Type:        string
+- Default:     ""
+- Examples:
+    - "nl-ams"
+        - Amsterdam, The Netherlands
+    - "fr-par"
+        - Paris, France
+
+#### --s3-region
+
 Region to connect to.
 Leave blank if you are using an S3 clone and you don't have a region.
 
@@ -618,74 +634,130 @@ Specify if using an IBM COS On Premise.
 - Type:        string
 - Default:     ""
 - Examples:
-    - "s3-api.us-geo.objectstorage.softlayer.net"
+    - "s3.us.cloud-object-storage.appdomain.cloud"
         - US Cross Region Endpoint
-    - "s3-api.dal.us-geo.objectstorage.softlayer.net"
+    - "s3.dal.us.cloud-object-storage.appdomain.cloud"
         - US Cross Region Dallas Endpoint
-    - "s3-api.wdc-us-geo.objectstorage.softlayer.net"
+    - "s3.wdc.us.cloud-object-storage.appdomain.cloud"
         - US Cross Region Washington DC Endpoint
-    - "s3-api.sjc-us-geo.objectstorage.softlayer.net"
+    - "s3.sjc.us.cloud-object-storage.appdomain.cloud"
         - US Cross Region San Jose Endpoint
-    - "s3-api.us-geo.objectstorage.service.networklayer.com"
+    - "s3.private.us.cloud-object-storage.appdomain.cloud"
         - US Cross Region Private Endpoint
-    - "s3-api.dal-us-geo.objectstorage.service.networklayer.com"
+    - "s3.private.dal.us.cloud-object-storage.appdomain.cloud"
         - US Cross Region Dallas Private Endpoint
-    - "s3-api.wdc-us-geo.objectstorage.service.networklayer.com"
+    - "s3.private.wdc.us.cloud-object-storage.appdomain.cloud"
         - US Cross Region Washington DC Private Endpoint
-    - "s3-api.sjc-us-geo.objectstorage.service.networklayer.com"
+    - "s3.private.sjc.us.cloud-object-storage.appdomain.cloud"
         - US Cross Region San Jose Private Endpoint
-    - "s3.us-east.objectstorage.softlayer.net"
+    - "s3.us-east.cloud-object-storage.appdomain.cloud"
         - US Region East Endpoint
-    - "s3.us-east.objectstorage.service.networklayer.com"
+    - "s3.private.us-east.cloud-object-storage.appdomain.cloud"
         - US Region East Private Endpoint
-    - "s3.us-south.objectstorage.softlayer.net"
+    - "s3.us-south.cloud-object-storage.appdomain.cloud"
         - US Region South Endpoint
-    - "s3.us-south.objectstorage.service.networklayer.com"
+    - "s3.private.us-south.cloud-object-storage.appdomain.cloud"
         - US Region South Private Endpoint
-    - "s3.eu-geo.objectstorage.softlayer.net"
+    - "s3.eu.cloud-object-storage.appdomain.cloud"
         - EU Cross Region Endpoint
-    - "s3.fra-eu-geo.objectstorage.softlayer.net"
+    - "s3.fra.eu.cloud-object-storage.appdomain.cloud"
         - EU Cross Region Frankfurt Endpoint
-    - "s3.mil-eu-geo.objectstorage.softlayer.net"
+    - "s3.mil.eu.cloud-object-storage.appdomain.cloud"
         - EU Cross Region Milan Endpoint
-    - "s3.ams-eu-geo.objectstorage.softlayer.net"
+    - "s3.ams.eu.cloud-object-storage.appdomain.cloud"
         - EU Cross Region Amsterdam Endpoint
-    - "s3.eu-geo.objectstorage.service.networklayer.com"
+    - "s3.private.eu.cloud-object-storage.appdomain.cloud"
         - EU Cross Region Private Endpoint
-    - "s3.fra-eu-geo.objectstorage.service.networklayer.com"
+    - "s3.private.fra.eu.cloud-object-storage.appdomain.cloud"
         - EU Cross Region Frankfurt Private Endpoint
-    - "s3.mil-eu-geo.objectstorage.service.networklayer.com"
+    - "s3.private.mil.eu.cloud-object-storage.appdomain.cloud"
         - EU Cross Region Milan Private Endpoint
-    - "s3.ams-eu-geo.objectstorage.service.networklayer.com"
+    - "s3.private.ams.eu.cloud-object-storage.appdomain.cloud"
         - EU Cross Region Amsterdam Private Endpoint
-    - "s3.eu-gb.objectstorage.softlayer.net"
+    - "s3.eu-gb.cloud-object-storage.appdomain.cloud"
         - Great Britain Endpoint
-    - "s3.eu-gb.objectstorage.service.networklayer.com"
+    - "s3.private.eu-gb.cloud-object-storage.appdomain.cloud"
         - Great Britain Private Endpoint
-    - "s3.ap-geo.objectstorage.softlayer.net"
+    - "s3.eu-de.cloud-object-storage.appdomain.cloud"
+        - EU Region DE Endpoint
+    - "s3.private.eu-de.cloud-object-storage.appdomain.cloud"
+        - EU Region DE Private Endpoint
+    - "s3.ap.cloud-object-storage.appdomain.cloud"
         - APAC Cross Regional Endpoint
-    - "s3.tok-ap-geo.objectstorage.softlayer.net"
+    - "s3.tok.ap.cloud-object-storage.appdomain.cloud"
         - APAC Cross Regional Tokyo Endpoint
-    - "s3.hkg-ap-geo.objectstorage.softlayer.net"
+    - "s3.hkg.ap.cloud-object-storage.appdomain.cloud"
         - APAC Cross Regional HongKong Endpoint
-    - "s3.seo-ap-geo.objectstorage.softlayer.net"
+    - "s3.seo.ap.cloud-object-storage.appdomain.cloud"
         - APAC Cross Regional Seoul Endpoint
-    - "s3.ap-geo.objectstorage.service.networklayer.com"
+    - "s3.private.ap.cloud-object-storage.appdomain.cloud"
         - APAC Cross Regional Private Endpoint
-    - "s3.tok-ap-geo.objectstorage.service.networklayer.com"
+    - "s3.private.tok.ap.cloud-object-storage.appdomain.cloud"
         - APAC Cross Regional Tokyo Private Endpoint
-    - "s3.hkg-ap-geo.objectstorage.service.networklayer.com"
+    - "s3.private.hkg.ap.cloud-object-storage.appdomain.cloud"
         - APAC Cross Regional HongKong Private Endpoint
-    - "s3.seo-ap-geo.objectstorage.service.networklayer.com"
+    - "s3.private.seo.ap.cloud-object-storage.appdomain.cloud"
         - APAC Cross Regional Seoul Private Endpoint
-    - "s3.mel01.objectstorage.softlayer.net"
+    - "s3.jp-tok.cloud-object-storage.appdomain.cloud"
+        - APAC Region Japan Endpoint
+    - "s3.private.jp-tok.cloud-object-storage.appdomain.cloud"
+        - APAC Region Japan Private Endpoint
+    - "s3.au-syd.cloud-object-storage.appdomain.cloud"
+        - APAC Region Australia Endpoint
+    - "s3.private.au-syd.cloud-object-storage.appdomain.cloud"
+        - APAC Region Australia Private Endpoint
+    - "s3.ams03.cloud-object-storage.appdomain.cloud"
+        - Amsterdam Single Site Endpoint
+    - "s3.private.ams03.cloud-object-storage.appdomain.cloud"
+        - Amsterdam Single Site Private Endpoint
+    - "s3.che01.cloud-object-storage.appdomain.cloud"
+        - Chennai Single Site Endpoint
+    - "s3.private.che01.cloud-object-storage.appdomain.cloud"
+        - Chennai Single Site Private Endpoint
+    - "s3.mel01.cloud-object-storage.appdomain.cloud"
         - Melbourne Single Site Endpoint
-    - "s3.mel01.objectstorage.service.networklayer.com"
+    - "s3.private.mel01.cloud-object-storage.appdomain.cloud"
         - Melbourne Single Site Private Endpoint
-    - "s3.tor01.objectstorage.softlayer.net"
+    - "s3.osl01.cloud-object-storage.appdomain.cloud"
+        - Oslo Single Site Endpoint
+    - "s3.private.osl01.cloud-object-storage.appdomain.cloud"
+        - Oslo Single Site Private Endpoint
+    - "s3.tor01.cloud-object-storage.appdomain.cloud"
         - Toronto Single Site Endpoint
-    - "s3.tor01.objectstorage.service.networklayer.com"
+    - "s3.private.tor01.cloud-object-storage.appdomain.cloud"
         - Toronto Single Site Private Endpoint
+    - "s3.seo01.cloud-object-storage.appdomain.cloud"
+        - Seoul Single Site Endpoint
+    - "s3.private.seo01.cloud-object-storage.appdomain.cloud"
+        - Seoul Single Site Private Endpoint
+    - "s3.mon01.cloud-object-storage.appdomain.cloud"
+        - Montreal Single Site Endpoint
+    - "s3.private.mon01.cloud-object-storage.appdomain.cloud"
+        - Montreal Single Site Private Endpoint
+    - "s3.mex01.cloud-object-storage.appdomain.cloud"
+        - Mexico Single Site Endpoint
+    - "s3.private.mex01.cloud-object-storage.appdomain.cloud"
+        - Mexico Single Site Private Endpoint
+    - "s3.sjc04.cloud-object-storage.appdomain.cloud"
+        - San Jose Single Site Endpoint
+    - "s3.private.sjc04.cloud-object-storage.appdomain.cloud"
+        - San Jose Single Site Private Endpoint
+    - "s3.mil01.cloud-object-storage.appdomain.cloud"
+        - Milan Single Site Endpoint
+    - "s3.private.mil01.cloud-object-storage.appdomain.cloud"
+        - Milan Single Site Private Endpoint
+    - "s3.hkg02.cloud-object-storage.appdomain.cloud"
+        - Hong Kong Single Site Endpoint
+    - "s3.private.hkg02.cloud-object-storage.appdomain.cloud"
+        - Hong Kong Single Site Private Endpoint
+    - "s3.par01.cloud-object-storage.appdomain.cloud"
+        - Paris Single Site Endpoint
+    - "s3.private.par01.cloud-object-storage.appdomain.cloud"
+        - Paris Single Site Private Endpoint
+    - "s3.sng01.cloud-object-storage.appdomain.cloud"
+        - Singapore Single Site Endpoint
+    - "s3.private.sng01.cloud-object-storage.appdomain.cloud"
+        - Singapore Single Site Private Endpoint
 
 #### --s3-endpoint
 
@@ -737,6 +809,20 @@ Endpoint for OSS API.
 
 #### --s3-endpoint
 
+Endpoint for Scaleway Object Storage.
+
+- Config:      endpoint
+- Env Var:     RCLONE_S3_ENDPOINT
+- Type:        string
+- Default:     ""
+- Examples:
+    - "s3.nl-ams.scw.cloud"
+        - Amsterdam Endpoint
+    - "s3.fr-par.scw.cloud"
+        - Paris Endpoint
+
+#### --s3-endpoint
+
 Endpoint for StackPath Object Storage.
 
 - Config:      endpoint
@@ -1018,6 +1104,22 @@ The storage class to use when storing new objects in OSS.
     - "STANDARD_IA"
         - Infrequent access storage mode.
 
+#### --s3-storage-class
+
+The storage class to use when storing new objects in S3.
+
+- Config:      storage_class
+- Env Var:     RCLONE_S3_STORAGE_CLASS
+- Type:        string
+- Default:     ""
+- Examples:
+    - ""
+        - Default
+    - "STANDARD"
+        - The Standard class for any upload; suitable for on-demand content like streaming or CDN.
+    - "GLACIER"
+        - Archived storage; prices are lower, but it needs to be restored first to be accessed.
+
 ### Advanced Options
 
 Here are the advanced options specific to s3 (Amazon S3 Compliant Storage Provider (AWS, Alibaba, Ceph, Digital Ocean, Dreamhost, IBM COS, Minio, etc)).
@@ -1125,6 +1227,25 @@ larger files then you will need to increase chunk_size.
 - Type:        SizeSuffix
 - Default:     5M
 
+#### --s3-max-upload-parts
+
+Maximum number of parts in a multipart upload.
+
+This option defines the maximum number of multipart chunks to use
+when doing a multipart upload.
+
+This can be useful if a service does not support the AWS S3
+specification of 10,000 chunks.
+
+Rclone will automatically increase the chunk size when uploading a
+large file of a known size to stay below this number of chunks limit.
+
+
+- Config:      max_upload_parts
+- Env Var:     RCLONE_S3_MAX_UPLOAD_PARTS
+- Type:        int
+- Default:     10000
+
 #### --s3-copy-cutoff
 
 Cutoff for switching to multipart copy
@@ -1137,7 +1258,7 @@ The minimum is 0 and the maximum is 5GB.
 - Config:      copy_cutoff
 - Env Var:     RCLONE_S3_COPY_CUTOFF
 - Type:        SizeSuffix
-- Default:     5G
+- Default:     4.656G
 
 #### --s3-disable-checksum
 
@@ -1153,6 +1274,41 @@ to start uploading.
 - Type:        bool
 - Default:     false
 
+#### --s3-shared-credentials-file
+
+Path to the shared credentials file
+
+If env_auth = true then rclone can use a shared credentials file.
+
+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.
+
+    Linux/OSX: "$HOME/.aws/credentials"
+    Windows:   "%USERPROFILE%\.aws\credentials"
+
+
+- Config:      shared_credentials_file
+- Env Var:     RCLONE_S3_SHARED_CREDENTIALS_FILE
+- Type:        string
+- Default:     ""
+
+#### --s3-profile
+
+Profile to use in the shared credentials file
+
+If env_auth = true then rclone can use a shared credentials file. This
+variable controls which profile is used in that file.
+
+If empty it will default to the environment variable "AWS_PROFILE" or
+"default" if that environment variable is also not set.
+
+
+- Config:      profile
+- Env Var:     RCLONE_S3_PROFILE
+- Type:        string
+- Default:     ""
+
 #### --s3-session-token
 
 An AWS session token
@@ -1250,6 +1406,19 @@ In Ceph, this can be increased with the "rgw list buckets max chunk" option.
 - Type:        int
 - Default:     1000
 
+#### --s3-no-check-bucket
+
+If set don'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.
+
+
+- Config:      no_check_bucket
+- Env Var:     RCLONE_S3_NO_CHECK_BUCKET
+- Type:        bool
+- Default:     false
+
 #### --s3-encoding
 
 This sets the encoding for the backend.
@@ -1281,6 +1450,129 @@ Whether to use mmap buffers in internal memory pool.
 - Type:        bool
 - Default:     false
 
+### Backend commands
+
+Here are the commands specific to the s3 backend.
+
+Run them with
+
+    rclone backend COMMAND remote:
+
+The help below will explain what arguments each command takes.
+
+See [the "rclone backend" command](/commands/rclone_backend/) for more
+info on how to pass options and arguments.
+
+These can be run on a running backend using the rc command
+[backend/command](/rc/#backend/command).
+
+#### restore
+
+Restore objects from GLACIER to normal storage
+
+    rclone backend restore remote: [options] [<arguments>+]
+
+This command can be used to restore one or more objects from GLACIER
+to normal storage.
+
+Usage Examples:
+
+    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]
+
+This flag also obeys the filters. Test first with -i/--interactive or --dry-run flags
+
+    rclone -i backend restore --include "*.txt" s3:bucket/path -o priority=Standard
+
+All the objects shown will be marked for restore, then
+
+    rclone backend restore --include "*.txt" s3:bucket/path -o priority=Standard
+
+It returns a list of status dictionaries with Remote and Status
+keys. The Status will be OK if it was successfull or an error message
+if not.
+
+    [
+        {
+            "Status": "OK",
+            "Path": "test.txt"
+        },
+        {
+            "Status": "OK",
+            "Path": "test/file4.txt"
+        }
+    ]
+
+
+
+Options:
+
+- "description": The optional description for the job.
+- "lifetime": Lifetime of the active copy in days
+- "priority": Priority of restore: Standard|Expedited|Bulk
+
+#### list-multipart-uploads
+
+List the unfinished multipart uploads
+
+    rclone backend list-multipart-uploads remote: [options] [<arguments>+]
+
+This command lists the unfinished multipart uploads in JSON format.
+
+    rclone backend list-multipart s3:bucket/path/to/object
+
+It returns a dictionary of buckets with values as lists of unfinished
+multipart uploads.
+
+You can call it with no bucket in which case it lists all bucket, with
+a bucket or with a bucket and path.
+
+    {
+      "rclone": [
+        {
+          "Initiated": "2020-06-26T14:20:36Z",
+          "Initiator": {
+            "DisplayName": "XXX",
+            "ID": "arn:aws:iam::XXX:user/XXX"
+          },
+          "Key": "KEY",
+          "Owner": {
+            "DisplayName": null,
+            "ID": "XXX"
+          },
+          "StorageClass": "STANDARD",
+          "UploadId": "XXX"
+        }
+      ],
+      "rclone-1000files": [],
+      "rclone-dst": []
+    }
+
+
+
+#### cleanup
+
+Remove unfinished multipart uploads.
+
+    rclone backend cleanup remote: [options] [<arguments>+]
+
+This command removes unfinished multipart uploads of age greater than
+max-age which defaults to 24 hours.
+
+Note that you can use -i/--dry-run with this command to see what it
+would do.
+
+    rclone backend cleanup s3:bucket/path/to/object
+    rclone backend cleanup -o max-age=7w s3:bucket/path/to/object
+
+Durations are parsed as per the rest of rclone, 2h, 7d, 7w etc.
+
+
+Options:
+
+- "max-age": Max age of upload to delete
+
 {{< rem autogenerated options stop >}}
 
 ### Anonymous access to public buckets ###
diff --git a/docs/content/seafile.md b/docs/content/seafile.md
index b8fefadf0..46fa854c7 100644
--- a/docs/content/seafile.md
+++ b/docs/content/seafile.md
@@ -294,6 +294,8 @@ User name (usually email address)
 
 Password
 
+**NB** Input to this must be obscured - see [rclone obscure](/commands/rclone_obscure/).
+
 - Config:      pass
 - Env Var:     RCLONE_SEAFILE_PASS
 - Type:        string
@@ -321,6 +323,8 @@ Name of the library. Leave blank to access all non-encrypted libraries.
 
 Library password (for encrypted libraries only). Leave blank if you pass it through the command line.
 
+**NB** Input to this must be obscured - see [rclone obscure](/commands/rclone_obscure/).
+
 - Config:      library_key
 - Env Var:     RCLONE_SEAFILE_LIBRARY_KEY
 - Type:        string
diff --git a/docs/content/sftp.md b/docs/content/sftp.md
index ddee387fb..bc13b1909 100644
--- a/docs/content/sftp.md
+++ b/docs/content/sftp.md
@@ -192,6 +192,8 @@ SSH port, leave blank to use default (22)
 
 SSH password, leave blank to use ssh-agent.
 
+**NB** Input to this must be obscured - see [rclone obscure](/commands/rclone_obscure/).
+
 - Config:      pass
 - Env Var:     RCLONE_SFTP_PASS
 - Type:        string
@@ -210,6 +212,9 @@ Raw PEM-encoded private key, If specified, will override key_file parameter.
 
 Path to PEM-encoded private key file, leave blank or set key-use-agent to use ssh-agent.
 
+Leading `~` will be expanded in the file name as will environment variables such as `${RCLONE_CONFIG_DIR}`.
+
+
 - Config:      key_file
 - Env Var:     RCLONE_SFTP_KEY_FILE
 - Type:        string
@@ -222,6 +227,8 @@ The passphrase to decrypt the PEM-encoded private key file.
 Only PEM encrypted key files (old OpenSSH format) are supported. Encrypted keys
 in the new OpenSSH format can't be used.
 
+**NB** Input to this must be obscured - see [rclone obscure](/commands/rclone_obscure/).
+
 - Config:      key_file_pass
 - Env Var:     RCLONE_SFTP_KEY_FILE_PASS
 - Type:        string
@@ -302,11 +309,11 @@ different. This issue affects among others Synology NAS boxes.
 
 Shared folders can be found in directories representing volumes
 
-    rclone sync -i /home/local/directory remote:/directory --ssh-path-override /volume2/directory
+    rclone sync /home/local/directory remote:/directory --ssh-path-override /volume2/directory
 
 Home directory can be found in a shared folder called "home"
 
-    rclone sync -i /home/local/directory remote:/home/directory --ssh-path-override /volume1/homes/USER/directory
+    rclone sync /home/local/directory remote:/home/directory --ssh-path-override /volume1/homes/USER/directory
 
 - Config:      path_override
 - Env Var:     RCLONE_SFTP_PATH_OVERRIDE
@@ -349,6 +356,26 @@ Set to skip any symlinks and any other non regular files.
 - Type:        bool
 - Default:     false
 
+#### --sftp-subsystem
+
+Specifies the SSH2 subsystem on the remote host.
+
+- Config:      subsystem
+- Env Var:     RCLONE_SFTP_SUBSYSTEM
+- Type:        string
+- Default:     "sftp"
+
+#### --sftp-server-command
+
+Specifies the path or command to run a sftp server on the remote host.
+
+The subsystem option is ignored when server_command is defined.
+
+- Config:      server_command
+- Env Var:     RCLONE_SFTP_SERVER_COMMAND
+- Type:        string
+- Default:     ""
+
 {{< rem autogenerated options stop >}}
 
 ### Limitations ###
diff --git a/docs/content/webdav.md b/docs/content/webdav.md
index 0e9038f83..219f7f481 100644
--- a/docs/content/webdav.md
+++ b/docs/content/webdav.md
@@ -152,6 +152,8 @@ User name
 
 Password.
 
+**NB** Input to this must be obscured - see [rclone obscure](/commands/rclone_obscure/).
+
 - Config:      pass
 - Env Var:     RCLONE_WEBDAV_PASS
 - Type:        string
diff --git a/docs/content/yandex.md b/docs/content/yandex.md
index 90c32520c..003b045b5 100644
--- a/docs/content/yandex.md
+++ b/docs/content/yandex.md
@@ -132,7 +132,7 @@ Here are the standard options specific to yandex (Yandex Disk).
 
 #### --yandex-client-id
 
-Yandex Client Id
+OAuth Client Id
 Leave blank normally.
 
 - Config:      client_id
@@ -142,7 +142,7 @@ Leave blank normally.
 
 #### --yandex-client-secret
 
-Yandex Client Secret
+OAuth Client Secret
 Leave blank normally.
 
 - Config:      client_secret
@@ -154,15 +154,34 @@ Leave blank normally.
 
 Here are the advanced options specific to yandex (Yandex Disk).
 
-#### --yandex-unlink
+#### --yandex-token
 
-Remove existing public link to file/folder with link command rather than creating.
-Default is false, meaning link command will create or retrieve public link.
+OAuth Access Token as a JSON blob.
 
-- Config:      unlink
-- Env Var:     RCLONE_YANDEX_UNLINK
-- Type:        bool
-- Default:     false
+- Config:      token
+- Env Var:     RCLONE_YANDEX_TOKEN
+- Type:        string
+- Default:     ""
+
+#### --yandex-auth-url
+
+Auth server URL.
+Leave blank to use the provider defaults.
+
+- Config:      auth_url
+- Env Var:     RCLONE_YANDEX_AUTH_URL
+- Type:        string
+- Default:     ""
+
+#### --yandex-token-url
+
+Token server url.
+Leave blank to use the provider defaults.
+
+- Config:      token_url
+- Env Var:     RCLONE_YANDEX_TOKEN_URL
+- Type:        string
+- Default:     ""
 
 #### --yandex-encoding
 
diff --git a/rclone.1 b/rclone.1
index d1112c5ad..a7aae105f 100644
--- a/rclone.1
+++ b/rclone.1
@@ -1,18 +1,18 @@
 .\"t
 .\" Automatically generated by Pandoc 2.5
 .\"
-.TH "rclone" "1" "May 27, 2020" "User Manual" ""
+.TH "rclone" "1" "Sep 02, 2020" "User Manual" ""
 .hy
 .SH Rclone syncs your files to cloud storage
 .PP
 .IP \[bu] 2
 About rclone
 .IP \[bu] 2
-What can rclone do for you
+What can rclone do for you?
 .IP \[bu] 2
-What features does rclone have
+What features does rclone have?
 .IP \[bu] 2
-What providers does rclone support
+What providers does rclone support?
 .IP \[bu] 2
 Download (https://rclone.org/downloads/)
 .IP \[bu] 2
@@ -22,7 +22,7 @@ Donate. (https://rclone.org/donate/)
 .SS About rclone
 .PP
 Rclone is a command line program to manage files on cloud storage.
-It is a feature rich alternative to cloud vendors\[cq] web storage
+It is a feature rich alternative to cloud vendors\[aq] web storage
 interfaces.
 Over 40 cloud storage products support rclone including S3 object
 stores, business & consumer file storage services, as well as standard
@@ -30,23 +30,23 @@ transfer protocols.
 .PP
 Rclone has powerful cloud equivalents to the unix commands rsync, cp,
 mv, mount, ls, ncdu, tree, rm, and cat.
-Rclone\[cq]s familiar syntax includes shell pipeline support, and
+Rclone\[aq]s familiar syntax includes shell pipeline support, and
 \f[C]\-\-dry\-run\f[R] protection.
-It can be used at the command line, in scripts or via its API (/rc).
+It is used at the command line, in scripts or via its API (/rc).
 .PP
-Users have called rclone \f[I]\[lq]The Swiss army knife of cloud
-storage\[rq]\f[R] and \f[I]\[lq]Technology indistinguishable from
-magic\[rq]\f[R].
+Users call rclone \f[I]\[dq]The Swiss army knife of cloud
+storage\[dq]\f[R], and \f[I]\[dq]Technology indistinguishable from
+magic\[dq]\f[R].
 .PP
 Rclone really looks after your data.
-It preserves timestamps and verifies your data at all times.
+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 check (https://rclone.org/commands/rclone_check/) 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
-your local disk.
+local disk.
 .PP
 Virtual backends wrap local and cloud file systems to apply
 encryption (https://rclone.org/crypt/),
@@ -54,9 +54,9 @@ caching (https://rclone.org/cache/),
 chunking (https://rclone.org/chunker/) and
 joining (https://rclone.org/union/).
 .PP
-Rclone can mount (https://rclone.org/commands/rclone_mount/) any local,
+Rclone mounts (https://rclone.org/commands/rclone_mount/) any local,
 cloud or virtual filesystem as a disk on Windows, macOS, linux and
-FreeBSD, and also serve these over
+FreeBSD, and also serves these over
 SFTP (https://rclone.org/commands/rclone_serve_sftp/),
 HTTP (https://rclone.org/commands/rclone_serve_http/),
 WebDAV (https://rclone.org/commands/rclone_serve_webdav/),
@@ -72,13 +72,13 @@ For the latest version downloading from
 rclone.org (https://rclone.org/downloads/) is recommended.
 .PP
 Rclone is widely used on Linux, Windows and Mac.
-Third party developers have built innovative backup, restore, GUI and
+Third party developers create innovative backup, restore, GUI and
 business process solutions using the rclone command line or API.
 .PP
-Let rclone do the heavy lifting of communicating with cloud storage.
-.SS What can rclone do for you
+Rclone does the heavy lifting of communicating with cloud storage.
+.SS What can rclone do for you?
 .PP
-Rclone can help you:
+Rclone helps you:
 .IP \[bu] 2
 Backup (and encrypt) files to cloud storage
 .IP \[bu] 2
@@ -136,8 +136,8 @@ HTTP (https://rclone.org/commands/rclone_serve_http/)/WebDav (https://rclone.org
 Experimental Web based GUI (https://rclone.org/gui/)
 .SS Supported providers
 .PP
-(There are many other providers, built on standard protocols such as
-WebDAV or S3, that work out of the box.)
+(There are many others, built on standard protocols such as WebDAV or
+S3, that work out of the box.)
 .IP \[bu] 2
 1Fichier
 .IP \[bu] 2
@@ -285,7 +285,7 @@ curl https://rclone.org/install.sh | sudo bash \-s beta
 .fi
 .PP
 Note that this script checks the version of rclone installed first and
-won\[cq]t re\-download if not needed.
+won\[aq]t re\-download if not needed.
 .SS Linux installation from precompiled binary
 .PP
 Fetch and unpack
@@ -449,11 +449,24 @@ 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.
 .IP \[bu] 2
+If you want to access the RC interface (either via the API or the Web
+UI), it is required to set the \f[C]\-\-rc\-addr\f[R] to \f[C]:5572\f[R]
+in order to connect to it from outside the container.
+An explanation about why this is necessary is present
+here (https://web.archive.org/web/20200808071950/https://pythonspeed.com/articles/docker-connection-refused/).
+.RS 2
+.IP \[bu] 2
+NOTE: Users running this container with the docker network set to
+\f[C]host\f[R] should probably set it to listen to localhost only, with
+\f[C]127.0.0.1:5572\f[R] as the value for \f[C]\-\-rc\-addr\f[R]
+.RE
+.IP \[bu] 2
 It is possible to use \f[C]rclone mount\f[R] inside a userspace Docker
 container, and expose the resulting fuse mount to the host.
 The exact \f[C]docker run\f[R] options to do that might vary slightly
 between hosts.
-See, e.g.\ the discussion in this
+See, e.g.
+the discussion in this
 thread (https://github.com/moby/moby/issues/9448).
 .RS 2
 .PP
@@ -492,7 +505,7 @@ kill %1
 .fi
 .SS Install from source
 .PP
-Make sure you have at least Go (https://golang.org/) 1.7 installed.
+Make sure you have at least Go (https://golang.org/) 1.11 installed.
 Download go (https://golang.org/dl/) if necessary.
 The latest release is recommended.
 Then
@@ -506,23 +519,36 @@ go build
 \f[R]
 .fi
 .PP
-You can also build and install rclone in the
-GOPATH (https://github.com/golang/go/wiki/GOPATH) (which defaults to
-\f[C]\[ti]/go\f[R]) with:
+This will leave you a checked out version of rclone you can modify and
+send pull requests with.
+If you use \f[C]make\f[R] instead of \f[C]go build\f[R] then the rclone
+build will have the correct version information in it.
+.PP
+You can also build the latest stable rclone with:
 .IP
 .nf
 \f[C]
-go get \-u \-v github.com/rclone/rclone
+go get github.com/rclone/rclone
 \f[R]
 .fi
 .PP
-and this will build the binary in \f[C]$GOPATH/bin\f[R]
+or the latest version (equivalent to the beta) with
+.IP
+.nf
+\f[C]
+go get github.com/rclone/rclone\[at]master
+\f[R]
+.fi
+.PP
+These will build the binary in \f[C]$(go env GOPATH)/bin\f[R]
 (\f[C]\[ti]/go/bin/rclone\f[R] by default) after downloading the source
-to \f[C]$GOPATH/src/github.com/rclone/rclone\f[R]
-(\f[C]\[ti]/go/src/github.com/rclone/rclone\f[R] by default).
+to the go module cache.
+Note \- do \f[B]not\f[R] use the \f[C]\-u\f[R] flag here.
+This causes go to try to update the depencencies that rclone uses and
+sometimes these don\[aq]t work with the current version of rclone.
 .SS Installation with Ansible
 .PP
-This can be done with Stefan Weichinger\[cq]s ansible
+This can be done with Stefan Weichinger\[aq]s ansible
 role (https://github.com/stefangweichinger/ansible-rclone).
 .PP
 Instructions
@@ -541,7 +567,7 @@ add the role to the hosts you want rclone installed to:
 .fi
 .SS Configure
 .PP
-First, you\[cq]ll need to configure rclone.
+First, you\[aq]ll need to configure rclone.
 As the object storage systems have quite complicated authentication
 these are kept in a config file.
 (See the \f[C]\-\-config\f[R] entry for how to find the config file and
@@ -651,9 +677,12 @@ Syntax: [options] subcommand <parameters> <parameters...>
 .PP
 Source and destination paths are specified by the name you gave the
 storage system in the config file then the sub path, eg
-\[lq]drive:myfolder\[rq] to look at \[lq]myfolder\[rq] in Google drive.
+\[dq]drive:myfolder\[dq] to look at \[dq]myfolder\[dq] in Google drive.
 .PP
 You can define as many storage paths as you like in the config file.
+.PP
+Please use the \f[C]\-i\f[R] / \f[C]\-\-interactive\f[R] flag while
+learning rclone to avoid accidental data loss.
 .SS Subcommands
 .PP
 rclone uses a system of subcommands.
@@ -663,7 +692,7 @@ For example
 \f[C]
 rclone ls remote:path # lists a remote
 rclone copy /local/path remote:path # copies /local/path to the remote
-rclone sync /local/path remote:path # syncs /local/path to the remote
+rclone sync \-i /local/path remote:path # syncs /local/path to the remote
 \f[R]
 .fi
 .SH rclone config
@@ -741,15 +770,15 @@ Copy files from source to dest, skipping already copied
 .SS Synopsis
 .PP
 Copy the source to the destination.
-Doesn\[cq]t transfer unchanged files, testing by size and modification
+Doesn\[aq]t transfer unchanged files, testing by size and modification
 time or MD5SUM.
-Doesn\[cq]t delete files from the destination.
+Doesn\[aq]t delete files from the destination.
 .PP
 Note that it is always the contents of the directory that is synced, not
-the directory so when source:path is a directory, it\[cq]s the contents
+the directory so when source:path is a directory, it\[aq]s the contents
 of source:path that are copied, not the directory name and contents.
 .PP
-If dest:path doesn\[cq]t exist, it is created and the source:path
+If dest:path doesn\[aq]t exist, it is created and the source:path
 contents go there.
 .PP
 For example
@@ -760,7 +789,7 @@ rclone copy source:sourcepath dest:destpath
 \f[R]
 .fi
 .PP
-Let\[cq]s say there are two files in sourcepath
+Let\[aq]s say there are two files in sourcepath
 .IP
 .nf
 \f[C]
@@ -788,12 +817,12 @@ destpath/sourcepath/two.txt
 .fi
 .PP
 If you are familiar with \f[C]rsync\f[R], rclone always works as if you
-had written a trailing / \- meaning \[lq]copy the contents of this
-directory\[rq].
+had written a trailing / \- meaning \[dq]copy the contents of this
+directory\[dq].
 This applies to all commands and whether you are talking about the
 source or destination.
 .PP
-See the \[en]no\-traverse (https://rclone.org/docs/#no-traverse) option
+See the \-\-no\-traverse (https://rclone.org/docs/#no-traverse) 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.
@@ -809,7 +838,11 @@ rclone copy \-\-max\-age 24h \-\-no\-traverse /path/to/src remote:
 .fi
 .PP
 \f[B]Note\f[R]: Use the \f[C]\-P\f[R]/\f[C]\-\-progress\f[R] flag to
-view real\-time transfer statistics
+view real\-time transfer statistics.
+.PP
+\f[B]Note\f[R]: Use the \f[C]\-\-dry\-run\f[R] or the
+\f[C]\-\-interactive\f[R]/\f[C]\-i\f[R] flag to test without copying
+anything.
 .IP
 .nf
 \f[C]
@@ -837,24 +870,30 @@ Make source and dest identical, modifying destination only.
 .SS Synopsis
 .PP
 Sync the source to the destination, changing the destination only.
-Doesn\[cq]t transfer unchanged files, testing by size and modification
+Doesn\[aq]t transfer unchanged files, testing by size and modification
 time or MD5SUM.
 Destination is updated to match source, including deleting files if
 necessary.
 .PP
 \f[B]Important\f[R]: Since this can cause data loss, test first with the
-\f[C]\-\-dry\-run\f[R] flag to see exactly what would be copied and
-deleted.
+\f[C]\-\-dry\-run\f[R] or the \f[C]\-\-interactive\f[R]/\f[C]\-i\f[R]
+flag.
+.IP
+.nf
+\f[C]
+rclone sync \-i SOURCE remote:DESTINATION
+\f[R]
+.fi
 .PP
-Note that files in the destination won\[cq]t be deleted if there were
+Note that files in the destination won\[aq]t be deleted if there were
 any errors at any point.
 .PP
 It is always the contents of the directory that is synced, not the
-directory so when source:path is a directory, it\[cq]s the contents of
+directory so when source:path is a directory, it\[aq]s the contents of
 source:path that are copied, not the directory name and contents.
 See extended explanation in the \f[C]copy\f[R] command above if unsure.
 .PP
-If dest:path doesn\[cq]t exist, it is created and the source:path
+If dest:path doesn\[aq]t exist, it is created and the source:path
 contents go there.
 .PP
 \f[B]Note\f[R]: Use the \f[C]\-P\f[R]/\f[C]\-\-progress\f[R] flag to
@@ -900,15 +939,16 @@ If possible a server side move will be used, otherwise it will copy it
 original (if no errors on copy) in \f[C]source:path\f[R].
 .PP
 If you want to delete empty source directories after move, use the
-\[en]delete\-empty\-src\-dirs flag.
+\-\-delete\-empty\-src\-dirs flag.
 .PP
-See the \[en]no\-traverse (https://rclone.org/docs/#no-traverse) option
+See the \-\-no\-traverse (https://rclone.org/docs/#no-traverse) 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.
 .PP
 \f[B]Important\f[R]: Since this can cause data loss, test first with the
-\[en]dry\-run flag.
+\f[C]\-\-dry\-run\f[R] or the \f[C]\-\-interactive\f[R]/\f[C]\-i\f[R]
+flag.
 .PP
 \f[B]Note\f[R]: Use the \f[C]\-P\f[R]/\f[C]\-\-progress\f[R] flag to
 view real\-time transfer statistics.
@@ -948,7 +988,7 @@ structure alone.
 If you want to delete a directory and all of its contents use
 \f[C]rclone purge\f[R]
 .PP
-If you supply the \[en]rmdirs flag, it will remove all empty directories
+If you supply the \-\-rmdirs flag, it will remove all empty directories
 along with it.
 .PP
 Eg delete all files bigger than 100MBytes
@@ -970,8 +1010,12 @@ rclone \-\-min\-size 100M delete remote:path
 \f[R]
 .fi
 .PP
-That reads \[lq]delete everything with a minimum size of 100 MB\[rq],
+That reads \[dq]delete everything with a minimum size of 100 MB\[dq],
 hence delete all files bigger than 100MBytes.
+.PP
+\f[B]Important\f[R]: Since this can cause data loss, test first with the
+\f[C]\-\-dry\-run\f[R] or the \f[C]\-\-interactive\f[R]/\f[C]\-i\f[R]
+flag.
 .IP
 .nf
 \f[C]
@@ -1002,6 +1046,10 @@ Remove the path and all of its contents.
 Note that this does not obey include/exclude filters \- everything will
 be removed.
 Use \f[C]delete\f[R] if you want to selectively delete files.
+.PP
+\f[B]Important\f[R]: Since this can cause data loss, test first with the
+\f[C]\-\-dry\-run\f[R] or the \f[C]\-\-interactive\f[R]/\f[C]\-i\f[R]
+flag.
 .IP
 .nf
 \f[C]
@@ -1024,10 +1072,10 @@ rclone (https://rclone.org/commands/rclone/) \- Show help for rclone
 commands, flags and backends.
 .SH rclone mkdir
 .PP
-Make the path if it doesn\[cq]t already exist.
+Make the path if it doesn\[aq]t already exist.
 .SS Synopsis
 .PP
-Make the path if it doesn\[cq]t already exist.
+Make the path if it doesn\[aq]t already exist.
 .IP
 .nf
 \f[C]
@@ -1054,7 +1102,7 @@ Remove the path if empty.
 .SS Synopsis
 .PP
 Remove the path.
-Note that you can\[cq]t remove a path with objects in it, use purge for
+Note that you can\[aq]t remove a path with objects in it, use purge for
 that.
 .IP
 .nf
@@ -1083,22 +1131,51 @@ Checks the files in the source and destination match.
 .PP
 Checks the files in the source and destination match.
 It compares sizes and hashes (MD5 or SHA1) and logs a report of files
-which don\[cq]t match.
-It doesn\[cq]t alter the source or destination.
+which don\[aq]t match.
+It doesn\[aq]t alter the source or destination.
 .PP
-If you supply the \[en]size\-only flag, it will only compare the sizes
+If you supply the \-\-size\-only flag, it will only compare the sizes
 not the hashes as well.
 Use this for a quick check.
 .PP
-If you supply the \[en]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\[cq]t support hashes or if you
+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\[aq]t support hashes or if you
 really want to check all the data.
 .PP
-If you supply the \[en]one\-way flag, it will only check that files in
-source match the files in destination, not the other way around.
-Meaning extra files in destination that are not in the source will not
-trigger an error.
+If you supply the \f[C]\-\-one\-way\f[R] 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.
+.PP
+The \f[C]\-\-differ\f[R], \f[C]\-\-missing\-on\-dst\f[R],
+\f[C]\-\-missing\-on\-src\f[R], \f[C]\-\-src\-only\f[R] and
+\f[C]\-\-error\f[R] flags write paths, one per line, to the file name
+(or stdout if it is \f[C]\-\f[R]) supplied.
+What they write is described in the help below.
+For example \f[C]\-\-differ\f[R] will write all paths which are present
+on both the source and destination but different.
+.PP
+The \f[C]\-\-combined\f[R] 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.
+.IP \[bu] 2
+\f[C]= path\f[R] means path was found in source and destination and was
+identical
+.IP \[bu] 2
+\f[C]\- path\f[R] means path was missing on the source, so only in the
+destination
+.IP \[bu] 2
+\f[C]+ path\f[R] means path was missing on the destination, so only in
+the source
+.IP \[bu] 2
+\f[C]* path\f[R] means path was present in source and destination but
+different.
+.IP \[bu] 2
+\f[C]! path\f[R] means there was an error reading or hashing the source
+or dest.
 .IP
 .nf
 \f[C]
@@ -1109,9 +1186,14 @@ rclone check source:path dest:path [flags]
 .IP
 .nf
 \f[C]
-      \-\-download   Check by downloading rather than with hash.
-  \-h, \-\-help       help for check
-      \-\-one\-way    Check one way only, source files must exist on remote
+      \-\-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 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
 \f[R]
 .fi
 .PP
@@ -1162,13 +1244,13 @@ readable.
 \f[C]lsjson\f[R] is designed to be machine readable.
 .PP
 Note that \f[C]ls\f[R] and \f[C]lsl\f[R] recurse by default \- use
-\[lq]\[en]max\-depth 1\[rq] to stop the recursion.
+\[dq]\-\-max\-depth 1\[dq] to stop the recursion.
 .PP
 The other list commands \f[C]lsd\f[R],\f[C]lsf\f[R],\f[C]lsjson\f[R] do
-not recurse by default \- use \[lq]\-R\[rq] to make them recurse.
+not recurse by default \- use \[dq]\-R\[dq] to make them recurse.
 .PP
 Listing a non existent directory will produce an error except for
-remotes which can\[cq]t have empty directories (eg s3, swift, gcs, etc
+remotes which can\[aq]t have empty directories (eg s3, swift, gcs, etc
 \- the bucket based remotes).
 .IP
 .nf
@@ -1223,8 +1305,8 @@ $ rclone lsd drive:test
 \f[R]
 .fi
 .PP
-If you just want the directory names use \[lq]rclone lsf
-\[en]dirs\-only\[rq].
+If you just want the directory names use \[dq]rclone lsf
+\-\-dirs\-only\[dq].
 .PP
 Any of the filtering options can be applied to this command.
 .PP
@@ -1246,13 +1328,13 @@ readable.
 \f[C]lsjson\f[R] is designed to be machine readable.
 .PP
 Note that \f[C]ls\f[R] and \f[C]lsl\f[R] recurse by default \- use
-\[lq]\[en]max\-depth 1\[rq] to stop the recursion.
+\[dq]\-\-max\-depth 1\[dq] to stop the recursion.
 .PP
 The other list commands \f[C]lsd\f[R],\f[C]lsf\f[R],\f[C]lsjson\f[R] do
-not recurse by default \- use \[lq]\-R\[rq] to make them recurse.
+not recurse by default \- use \[dq]\-R\[dq] to make them recurse.
 .PP
 Listing a non existent directory will produce an error except for
-remotes which can\[cq]t have empty directories (eg s3, swift, gcs, etc
+remotes which can\[aq]t have empty directories (eg s3, swift, gcs, etc
 \- the bucket based remotes).
 .IP
 .nf
@@ -1316,13 +1398,13 @@ readable.
 \f[C]lsjson\f[R] is designed to be machine readable.
 .PP
 Note that \f[C]ls\f[R] and \f[C]lsl\f[R] recurse by default \- use
-\[lq]\[en]max\-depth 1\[rq] to stop the recursion.
+\[dq]\-\-max\-depth 1\[dq] to stop the recursion.
 .PP
 The other list commands \f[C]lsd\f[R],\f[C]lsf\f[R],\f[C]lsjson\f[R] do
-not recurse by default \- use \[lq]\-R\[rq] to make them recurse.
+not recurse by default \- use \[dq]\-R\[dq] to make them recurse.
 .PP
 Listing a non existent directory will produce an error except for
-remotes which can\[cq]t have empty directories (eg s3, swift, gcs, etc
+remotes which can\[aq]t have empty directories (eg s3, swift, gcs, etc
 \- the bucket based remotes).
 .IP
 .nf
@@ -1443,7 +1525,7 @@ rclone v1.41
 \f[R]
 .fi
 .PP
-If you supply the \[en]check flag, then it will do an online check to
+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.
 .IP
 .nf
@@ -1518,23 +1600,38 @@ rclone (https://rclone.org/commands/rclone/) \- Show help for rclone
 commands, flags and backends.
 .SH rclone dedupe
 .PP
-Interactively find duplicate files and delete/rename them.
+Interactively find duplicate filenames and delete/rename them.
 .SS Synopsis
 .PP
-By default \f[C]dedupe\f[R] interactively finds duplicate files and
-offers to delete all but one or rename them to be different.
-Only useful with Google Drive which can have duplicate file names.
+By default \f[C]dedupe\f[R] interactively finds files with duplicate
+names and offers to delete all but one or rename them to be different.
+.PP
+This is only useful with backends like Google Drive which can have
+duplicate file names.
+It can be run on wrapping backends (eg crypt) if they wrap a backend
+which supports duplicate file names.
 .PP
 In the first pass it will merge directories with the same name.
-It will do this iteratively until all the identical directories have
-been merged.
+It will do this iteratively until all the identically named directories
+have been merged.
 .PP
-The \f[C]dedupe\f[R] command will delete all but one of any identical
-(same md5sum) files it finds without confirmation.
+In the second pass, for every group of duplicate file names, it will
+delete all but one identical files it finds without confirmation.
 This means that for most duplicated files the \f[C]dedupe\f[R] command
 will not be interactive.
-You can use \f[C]\-\-dry\-run\f[R] to see what would happen without
-doing anything.
+.PP
+\f[C]dedupe\f[R] considers files to be identical if they have the same
+hash.
+If the backend does not support hashes (eg crypt wrapping Google Drive)
+then they will never be found to be identical.
+If you use the \f[C]\-\-size\-only\f[R] 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.
+.PP
+\f[B]Important\f[R]: Since this can cause data loss, test first with the
+\f[C]\-\-dry\-run\f[R] or the \f[C]\-\-interactive\f[R]/\f[C]\-i\f[R]
+flag.
 .PP
 Here is an example run.
 .PP
@@ -1559,22 +1656,22 @@ Now the \f[C]dedupe\f[R] session
 \f[C]
 $ rclone dedupe drive:dupes
 2016/03/05 16:24:37 Google drive root \[aq]dupes\[aq]: Looking for duplicates using interactive mode.
-one.txt: Found 4 duplicates \- deleting identical copies
-one.txt: Deleting 2/3 identical duplicates (md5sum \[dq]1eedaa9fe86fd4b8632e2ac549403b36\[dq])
+one.txt: Found 4 files with duplicate names
+one.txt: Deleting 2/3 identical duplicates (MD5 \[dq]1eedaa9fe86fd4b8632e2ac549403b36\[dq])
 one.txt: 2 duplicates remain
-  1:      6048320 bytes, 2016\-03\-05 16:23:16.798000000, md5sum 1eedaa9fe86fd4b8632e2ac549403b36
-  2:       564374 bytes, 2016\-03\-05 16:23:06.731000000, md5sum 7594e7dc9fc28f727c42ee3e0749de81
+  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> k
 Enter the number of the file to keep> 1
 one.txt: Deleted 1 extra copies
-two.txt: Found 3 duplicates \- deleting identical copies
+two.txt: Found 3 files with duplicates names
 two.txt: 3 duplicates remain
-  1:       564374 bytes, 2016\-03\-05 16:22:52.118000000, md5sum 7594e7dc9fc28f727c42ee3e0749de81
-  2:      6048320 bytes, 2016\-03\-05 16:22:46.185000000, md5sum 1eedaa9fe86fd4b8632e2ac549403b36
-  3:      1744073 bytes, 2016\-03\-05 16:22:38.104000000, md5sum 851957f7fb6f0bc4ce76be966d336802
+  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)
@@ -1700,7 +1797,7 @@ missing if they are not known for that backend.
 Where it is known that the value is unlimited the value will also be
 omitted.
 .PP
-Use the \[en]full flag to see the numbers written out in full, eg
+Use the \-\-full flag to see the numbers written out in full, eg
 .IP
 .nf
 \f[C]
@@ -1712,7 +1809,7 @@ Other:   8849156022
 \f[R]
 .fi
 .PP
-Use the \[en]json flag for a computer readable output, eg
+Use the \-\-json flag for a computer readable output, eg
 .IP
 .nf
 \f[C]
@@ -1756,7 +1853,7 @@ Remote authorization.
 Used to authorize a remote or headless rclone from a machine with a
 browser \- use as instructed by rclone config.
 .PP
-Use the \[en]auth\-no\-open\-browser to prevent rclone to open auth link
+Use the \-\-auth\-no\-open\-browser to prevent rclone to open auth link
 in default browser automatically.
 .IP
 .nf
@@ -1785,8 +1882,8 @@ Run a backend specific command.
 .SS Synopsis
 .PP
 This runs a backend specific command.
-The commands themselves (except for \[lq]help\[rq] and
-\[lq]features\[rq]) are defined by the backends and you should see the
+The commands themselves (except for \[dq]help\[dq] and
+\[dq]features\[dq]) are defined by the backends and you should see the
 backend docs for definitions.
 .PP
 You can discover what commands a backend implements by using
@@ -1880,11 +1977,11 @@ rclone \-\-include \[dq]*.txt\[dq] cat remote:path/to/dir
 \f[R]
 .fi
 .PP
-Use the \[en]head flag to print characters only at the start, \[en]tail
-for the end and \[en]offset and \[en]count to print a section in the
+Use the \-\-head flag to print characters only at the start, \-\-tail
+for the end and \-\-offset and \-\-count to print a section in the
 middle.
 Note that if offset is negative it will count from the end, so
-\[en]offset \-1 \[en]count 1 is equivalent to \[en]tail 1.
+\-\-offset \-1 \-\-count 1 is equivalent to \-\-tail 1.
 .IP
 .nf
 \f[C]
@@ -1933,7 +2030,7 @@ Each time that happens rclone will print a message saying how to affect
 the value taken.
 .PP
 If any of the parameters passed is a password field, then rclone will
-automatically obscure them if they aren\[cq]t already obscured before
+automatically obscure them if they aren\[aq]t already obscured before
 putting them in the config file.
 .PP
 \f[B]NB\f[R] If the password parameter is 22 characters or longer and
@@ -1941,10 +2038,10 @@ 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 \[lq]\[en]obscure\[rq] flag, or if you are 100% certain you are
-already passing obscured passwords then use \[lq]\[en]no\-obscure\[rq].
-You can also set osbscured passwords using the \[lq]rclone config
-password\[rq] command.
+the \[dq]\-\-obscure\[dq] flag, or if you are 100% certain you are
+already passing obscured passwords then use \[dq]\-\-no\-obscure\[dq].
+You can also set osbscured passwords using the \[dq]rclone config
+password\[dq] command.
 .PP
 So for example if you wanted to configure a Google Drive remote but
 using remote authorization you would do this:
@@ -2011,7 +2108,7 @@ This disconnects the remote: passed in to the cloud storage system.
 .PP
 This normally means revoking the oauth token.
 .PP
-To reconnect use \[lq]rclone config reconnect\[rq].
+To reconnect use \[dq]rclone config reconnect\[dq].
 .IP
 .nf
 \f[C]
@@ -2117,7 +2214,7 @@ interactive configuration session.
 Update password in an existing remote.
 .SS Synopsis
 .PP
-Update an existing remote\[cq]s password.
+Update an existing remote\[aq]s password.
 The password should be passed in pairs of \f[C]key\f[R] \f[C]value\f[R].
 .PP
 For example to set password of a remote of name myremote you would do:
@@ -2128,8 +2225,8 @@ rclone config password myremote fieldname mypassword
 \f[R]
 .fi
 .PP
-This command is obsolete now that \[lq]config update\[rq] and
-\[lq]config create\[rq] both support obscuring passwords directly.
+This command is obsolete now that \[dq]config update\[dq] and
+\[dq]config create\[dq] both support obscuring passwords directly.
 .IP
 .nf
 \f[C]
@@ -2183,7 +2280,7 @@ Re\-authenticates user with remote.
 .PP
 This reconnects remote: passed in to the cloud storage system.
 .PP
-To disconnect the remote use \[lq]rclone config disconnect\[rq].
+To disconnect the remote use \[dq]rclone config disconnect\[dq].
 .PP
 This normally means going through the interactive oauth flow again.
 .IP
@@ -2237,7 +2334,7 @@ interactive configuration session.
 Update options in an existing remote.
 .SS Synopsis
 .PP
-Update an existing remote\[cq]s options.
+Update an existing remote\[aq]s options.
 The options should be passed in in pairs of \f[C]key\f[R]
 \f[C]value\f[R].
 .PP
@@ -2251,7 +2348,7 @@ rclone config update myremote swift env_auth true
 .fi
 .PP
 If any of the parameters passed is a password field, then rclone will
-automatically obscure them if they aren\[cq]t already obscured before
+automatically obscure them if they aren\[aq]t already obscured before
 putting them in the config file.
 .PP
 \f[B]NB\f[R] If the password parameter is 22 characters or longer and
@@ -2259,12 +2356,12 @@ 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 \[lq]\[en]obscure\[rq] flag, or if you are 100% certain you are
-already passing obscured passwords then use \[lq]\[en]no\-obscure\[rq].
-You can also set osbscured passwords using the \[lq]rclone config
-password\[rq] command.
+the \[dq]\-\-obscure\[dq] flag, or if you are 100% certain you are
+already passing obscured passwords then use \[dq]\-\-no\-obscure\[dq].
+You can also set osbscured passwords using the \[dq]rclone config
+password\[dq] command.
 .PP
-If the remote uses OAuth the token will be updated, if you don\[cq]t
+If the remote uses OAuth the token will be updated, if you don\[aq]t
 require this add an extra parameter thus:
 .IP
 .nf
@@ -2357,9 +2454,9 @@ if src is directory
 \f[R]
 .fi
 .PP
-This doesn\[cq]t transfer unchanged files, testing by size and
+This doesn\[aq]t transfer unchanged files, testing by size and
 modification time or MD5SUM.
-It doesn\[cq]t delete files from the destination.
+It doesn\[aq]t delete files from the destination.
 .PP
 \f[B]Note\f[R]: Use the \f[C]\-P\f[R]/\f[C]\-\-progress\f[R] flag to
 view real\-time transfer statistics
@@ -2388,17 +2485,16 @@ commands, flags and backends.
 Copy url content to dest.
 .SS Synopsis
 .PP
-Download a URL\[cq]s content and copy it to the destination without
+Download a URL\[aq]s content and copy it to the destination without
 saving it in temporary storage.
 .PP
-Setting \[en]auto\-filename will cause the file name to be retrieved
-from the from URL (after any redirections) and used in the destination
-path.
+Setting \-\-auto\-filename will cause the file name to be retrieved from
+the from URL (after any redirections) and used in the destination path.
 .PP
-Setting \[en]no\-clobber will prevent overwriting file on the
-destination if there is one with the same name.
+Setting \-\-no\-clobber will prevent overwriting file on the destination
+if there is one with the same name.
 .PP
-Setting \[en]stdout or making the output file name \[lq]\-\[rq] will
+Setting \-\-stdout or making the output file name \[dq]\-\[dq] will
 cause the output to be written to standard output.
 .IP
 .nf
@@ -2459,10 +2555,39 @@ rclone cryptcheck remote:path encryptedremote:path
 .PP
 After it has run it will log the status of the encryptedremote:.
 .PP
-If you supply the \[en]one\-way flag, it will only check that files in
-source match the files in destination, not the other way around.
-Meaning extra files in destination that are not in the source will not
-trigger an error.
+If you supply the \f[C]\-\-one\-way\f[R] 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.
+.PP
+The \f[C]\-\-differ\f[R], \f[C]\-\-missing\-on\-dst\f[R],
+\f[C]\-\-missing\-on\-src\f[R], \f[C]\-\-src\-only\f[R] and
+\f[C]\-\-error\f[R] flags write paths, one per line, to the file name
+(or stdout if it is \f[C]\-\f[R]) supplied.
+What they write is described in the help below.
+For example \f[C]\-\-differ\f[R] will write all paths which are present
+on both the source and destination but different.
+.PP
+The \f[C]\-\-combined\f[R] 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.
+.IP \[bu] 2
+\f[C]= path\f[R] means path was found in source and destination and was
+identical
+.IP \[bu] 2
+\f[C]\- path\f[R] means path was missing on the source, so only in the
+destination
+.IP \[bu] 2
+\f[C]+ path\f[R] means path was missing on the destination, so only in
+the source
+.IP \[bu] 2
+\f[C]* path\f[R] means path was present in source and destination but
+different.
+.IP \[bu] 2
+\f[C]! path\f[R] means there was an error reading or hashing the source
+or dest.
 .IP
 .nf
 \f[C]
@@ -2473,8 +2598,14 @@ rclone cryptcheck remote:path cryptedremote:path [flags]
 .IP
 .nf
 \f[C]
-  \-h, \-\-help      help for cryptcheck
-      \-\-one\-way   Check one way only, source files must exist on destination
+      \-\-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
 \f[R]
 .fi
 .PP
@@ -2493,8 +2624,7 @@ rclone cryptdecode returns unencrypted file names when provided with a
 list of encrypted file names.
 List limit is 10 items.
 .PP
-If you supply the \[en]reverse flag, it will return encrypted file
-names.
+If you supply the \-\-reverse flag, it will return encrypted file names.
 .PP
 use it like this
 .IP
@@ -2533,7 +2663,7 @@ Remove a single file from remote.
 .PP
 Remove a single file from remote.
 Unlike \f[C]delete\f[R] it cannot be used to remove a directory and it
-doesn\[cq]t obey include/exclude filters \- if the specified file
+doesn\[aq]t obey include/exclude filters \- if the specified file
 exists, it will always be removed.
 .IP
 .nf
@@ -2561,7 +2691,7 @@ Output completion script for a given shell.
 .SS Synopsis
 .PP
 Generates a shell completion script for rclone.
-Run with \[en]help to list the supported shells.
+Run with \-\-help to list the supported shells.
 .SS Options
 .IP
 .nf
@@ -2813,20 +2943,32 @@ commands, flags and backends.
 Generate public link to file/folder.
 .SS Synopsis
 .PP
-rclone link will create or retrieve a public link to the given file or
-folder.
+rclone link will create, retrieve or remove a public link to the given
+file or folder.
 .IP
 .nf
 \f[C]
 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
 \f[R]
 .fi
 .PP
+If you supply the \-\-expire flag, it will set the expiration time
+otherwise it will use the default (100 years).
+\f[B]Note\f[R] not all backends support the \-\-expire flag \- if the
+backend doesn\[aq]t support it then the link returned won\[aq]t expire.
+.PP
+Use the \-\-unlink flag to remove existing public links to the file or
+folder.
+\f[B]Note\f[R] not all backends support \[dq]\-\-unlink\[dq] flag \-
+those that don\[aq]t will just ignore it.
+.PP
 If successful, the last line of the output will contain the link.
-Exact capabilities depend on the remote, but the link will always be
-created with the least constraints \[en] e.g.\ no expiry, no password
-protection, accessible without account.
+Exact capabilities depend on the remote, but the link will always by
+default be created with the least constraints \[en] e.g.
+no expiry, no password protection, accessible without account.
 .IP
 .nf
 \f[C]
@@ -2837,7 +2979,9 @@ rclone link remote:path [flags]
 .IP
 .nf
 \f[C]
-  \-h, \-\-help   help for link
+      \-\-expire Duration   The amount of time that the link will be valid (default 100y)
+  \-h, \-\-help              help for link
+      \-\-unlink            Remove existing public link to file/folder
 \f[R]
 .fi
 .PP
@@ -2900,7 +3044,7 @@ fubuwic
 \f[R]
 .fi
 .PP
-Use the \[en]format option to control what gets listed.
+Use the \-\-format option to control what gets listed.
 By default this is just the path, but you can use these parameters to
 control the output:
 .IP
@@ -2919,7 +3063,7 @@ T \- tier of storage if known, eg \[dq]Hot\[dq] or \[dq]Cool\[dq]
 .fi
 .PP
 So if you wanted the path, size and modification time, you would use
-\[en]format \[lq]pst\[rq], or maybe \[en]format \[lq]tsp\[rq] to put the
+\-\-format \[dq]pst\[dq], or maybe \-\-format \[dq]tsp\[dq] to put the
 path last.
 .PP
 Eg
@@ -2935,11 +3079,11 @@ $ rclone lsf  \-\-format \[dq]tsp\[dq] swift:bucket
 \f[R]
 .fi
 .PP
-If you specify \[lq]h\[rq] in the format you will get the MD5 hash by
-default, use the \[lq]\[en]hash\[rq] flag to change which hash you want.
-Note that this can be returned as an empty string if it isn\[cq]t
-available on the object (and for directories), \[lq]ERROR\[rq] if there
-was an error reading it from the object and \[lq]UNSUPPORTED\[rq] if
+If you specify \[dq]h\[dq] in the format you will get the MD5 hash by
+default, use the \[dq]\-\-hash\[dq] flag to change which hash you want.
+Note that this can be returned as an empty string if it isn\[aq]t
+available on the object (and for directories), \[dq]ERROR\[dq] if there
+was an error reading it from the object and \[dq]UNSUPPORTED\[dq] if
 that object does not support that hash type.
 .PP
 For example to emulate the md5sum command you can use
@@ -2963,11 +3107,11 @@ cd65ac234e6fea5925974a51cdd865cc  canole
 \f[R]
 .fi
 .PP
-(Though \[lq]rclone md5sum .\[rq] is an easier way of typing this.)
+(Though \[dq]rclone md5sum .\[dq] is an easier way of typing this.)
 .PP
-By default the separator is \[lq];\[rq] this can be changed with the
-\[en]separator flag.
-Note that separators aren\[cq]t escaped in the path so putting it last
+By default the separator is \[dq];\[dq] this can be changed with the
+\-\-separator flag.
+Note that separators aren\[aq]t escaped in the path so putting it last
 is a good strategy.
 .PP
 Eg
@@ -2997,8 +3141,8 @@ test.sh,449
 \f[R]
 .fi
 .PP
-Note that the \[en]absolute parameter is useful for making lists of
-files to pass to an rclone copy with the \[en]files\-from\-raw flag.
+Note that the \-\-absolute parameter is useful for making lists of files
+to pass to an rclone copy with the \-\-files\-from\-raw flag.
 .PP
 For example to find all the files modified within one day and copy those
 only (without traversing the whole directory structure):
@@ -3030,13 +3174,13 @@ readable.
 \f[C]lsjson\f[R] is designed to be machine readable.
 .PP
 Note that \f[C]ls\f[R] and \f[C]lsl\f[R] recurse by default \- use
-\[lq]\[en]max\-depth 1\[rq] to stop the recursion.
+\[dq]\-\-max\-depth 1\[dq] to stop the recursion.
 .PP
 The other list commands \f[C]lsd\f[R],\f[C]lsf\f[R],\f[C]lsjson\f[R] do
-not recurse by default \- use \[lq]\-R\[rq] to make them recurse.
+not recurse by default \- use \[dq]\-R\[dq] to make them recurse.
 .PP
 Listing a non existent directory will produce an error except for
-remotes which can\[cq]t have empty directories (eg s3, swift, gcs, etc
+remotes which can\[aq]t have empty directories (eg s3, swift, gcs, etc
 \- the bucket based remotes).
 .IP
 .nf
@@ -3076,60 +3220,60 @@ List directories and objects in the path in JSON format.
 .PP
 The output is an array of Items, where each Item looks like this
 .PP
-{ \[lq]Hashes\[rq] : { \[lq]SHA\-1\[rq] :
-\[lq]f572d396fae9206628714fb2ce00f72e94f2258f\[rq], \[lq]MD5\[rq] :
-\[lq]b1946ac92492d2347c6235b4d2611184\[rq], \[lq]DropboxHash\[rq] :
-\[lq]ecb65bb98f9d905b70458986c39fcbad7715e5f2fcc3b1f07767d7c83e2438cc\[rq]
-}, \[lq]ID\[rq]: \[lq]y2djkhiujf83u33\[rq], \[lq]OrigID\[rq]:
-\[lq]UYOJVTUW00Q1RzTDA\[rq], \[lq]IsBucket\[rq] : false, \[lq]IsDir\[rq]
-: false, \[lq]MimeType\[rq] : \[lq]application/octet\-stream\[rq],
-\[lq]ModTime\[rq] : \[lq]2017\-05\-31T16:15:57.034468261+01:00\[rq],
-\[lq]Name\[rq] : \[lq]file.txt\[rq], \[lq]Encrypted\[rq] :
-\[lq]v0qpsdq8anpci8n929v3uu9338\[rq], \[lq]EncryptedPath\[rq] :
-\[lq]kja9098349023498/v0qpsdq8anpci8n929v3uu9338\[rq], \[lq]Path\[rq] :
-\[lq]full/path/goes/here/file.txt\[rq], \[lq]Size\[rq] : 6,
-\[lq]Tier\[rq] : \[lq]hot\[rq], }
+{ \[dq]Hashes\[dq] : { \[dq]SHA\-1\[dq] :
+\[dq]f572d396fae9206628714fb2ce00f72e94f2258f\[dq], \[dq]MD5\[dq] :
+\[dq]b1946ac92492d2347c6235b4d2611184\[dq], \[dq]DropboxHash\[dq] :
+\[dq]ecb65bb98f9d905b70458986c39fcbad7715e5f2fcc3b1f07767d7c83e2438cc\[dq]
+}, \[dq]ID\[dq]: \[dq]y2djkhiujf83u33\[dq], \[dq]OrigID\[dq]:
+\[dq]UYOJVTUW00Q1RzTDA\[dq], \[dq]IsBucket\[dq] : false, \[dq]IsDir\[dq]
+: false, \[dq]MimeType\[dq] : \[dq]application/octet\-stream\[dq],
+\[dq]ModTime\[dq] : \[dq]2017\-05\-31T16:15:57.034468261+01:00\[dq],
+\[dq]Name\[dq] : \[dq]file.txt\[dq], \[dq]Encrypted\[dq] :
+\[dq]v0qpsdq8anpci8n929v3uu9338\[dq], \[dq]EncryptedPath\[dq] :
+\[dq]kja9098349023498/v0qpsdq8anpci8n929v3uu9338\[dq], \[dq]Path\[dq] :
+\[dq]full/path/goes/here/file.txt\[dq], \[dq]Size\[dq] : 6,
+\[dq]Tier\[dq] : \[dq]hot\[dq], }
 .PP
-If \[en]hash is not specified the Hashes property won\[cq]t be emitted.
-The types of hash can be specified with the \[en]hash\-type parameter
+If \-\-hash is not specified the Hashes property won\[aq]t be emitted.
+The types of hash can be specified with the \-\-hash\-type parameter
 (which may be repeated).
-If \[en]hash\-type is set then it implies \[en]hash.
+If \-\-hash\-type is set then it implies \-\-hash.
 .PP
-If \[en]no\-modtime is specified then ModTime will be blank.
+If \-\-no\-modtime is specified then ModTime will be blank.
 This can speed things up on remotes where reading the ModTime takes an
 extra request (eg s3, swift).
 .PP
-If \[en]no\-mimetype is specified then MimeType will be blank.
+If \-\-no\-mimetype is specified then MimeType will be blank.
 This can speed things up on remotes where reading the MimeType takes an
 extra request (eg s3, swift).
 .PP
-If \[en]encrypted is not specified the Encrypted won\[cq]t be emitted.
+If \-\-encrypted is not specified the Encrypted won\[aq]t be emitted.
 .PP
-If \[en]dirs\-only is not specified files in addition to directories are
+If \-\-dirs\-only is not specified files in addition to directories are
 returned
 .PP
-If \[en]files\-only is not specified directories in addition to the
-files will be returned.
+If \-\-files\-only is not specified directories in addition to the files
+will be returned.
 .PP
 The Path field will only show folders below the remote path being
 listed.
-If \[lq]remote:path\[rq] contains the file \[lq]subfolder/file.txt\[rq],
-the Path for \[lq]file.txt\[rq] will be \[lq]subfolder/file.txt\[rq],
-not \[lq]remote:path/subfolder/file.txt\[rq].
-When used without \[en]recursive the Path will always be the same as
+If \[dq]remote:path\[dq] contains the file \[dq]subfolder/file.txt\[dq],
+the Path for \[dq]file.txt\[dq] will be \[dq]subfolder/file.txt\[dq],
+not \[dq]remote:path/subfolder/file.txt\[dq].
+When used without \-\-recursive the Path will always be the same as
 Name.
 .PP
 If the directory is a bucket in a bucket based backend, then
-\[lq]IsBucket\[rq] will be set to true.
-This key won\[cq]t be present unless it is \[lq]true\[rq].
+\[dq]IsBucket\[dq] will be set to true.
+This key won\[aq]t be present unless it is \[dq]true\[dq].
 .PP
 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 (eg Google Drive) then 3 digits will always be shown
-(\[lq]2017\-05\-31T16:15:57.034+01:00\[rq]) whereas if the times are
+(\[dq]2017\-05\-31T16:15:57.034+01:00\[dq]) whereas if the times are
 accurate to the nearest second (Dropbox, Box, WebDav etc) no digits will
-be shown (\[lq]2017\-05\-31T16:15:57+01:00\[rq]).
+be shown (\[dq]2017\-05\-31T16:15:57+01:00\[dq]).
 .PP
 The whole output can be processed as a JSON blob, or alternatively it
 can be processed line by line as each item is written one to a line.
@@ -3154,13 +3298,13 @@ readable.
 \f[C]lsjson\f[R] is designed to be machine readable.
 .PP
 Note that \f[C]ls\f[R] and \f[C]lsl\f[R] recurse by default \- use
-\[lq]\[en]max\-depth 1\[rq] to stop the recursion.
+\[dq]\-\-max\-depth 1\[dq] to stop the recursion.
 .PP
 The other list commands \f[C]lsd\f[R],\f[C]lsf\f[R],\f[C]lsjson\f[R] do
-not recurse by default \- use \[lq]\-R\[rq] to make them recurse.
+not recurse by default \- use \[dq]\-R\[dq] to make them recurse.
 .PP
 Listing a non existent directory will produce an error except for
-remotes which can\[cq]t have empty directories (eg s3, swift, gcs, etc
+remotes which can\[aq]t have empty directories (eg s3, swift, gcs, etc
 \- the bucket based remotes).
 .IP
 .nf
@@ -3197,13 +3341,13 @@ Mount the remote as file system on a mountpoint.
 .SS Synopsis
 .PP
 rclone mount allows Linux, FreeBSD, macOS and Windows to mount any of
-Rclone\[cq]s cloud storage systems as a file system with FUSE.
+Rclone\[aq]s cloud storage systems as a file system with FUSE.
 .PP
 First set up your remote using \f[C]rclone config\f[R].
 Check it works with \f[C]rclone ls\f[R] etc.
 .PP
 You can either run mount in foreground mode or background (daemon) mode.
-Mount runs in foreground mode by default, use the \[en]daemon flag to
+Mount runs in foreground mode by default, use the \-\-daemon flag to
 specify background mode mode.
 Background mode is only supported on Linux and OSX, you can only run
 mount in foreground mode on Windows.
@@ -3236,7 +3380,7 @@ receiving a SIGINT or SIGTERM signal, the mount is automatically
 stopped.
 .PP
 The umount operation can fail, for example when the mountpoint is busy.
-When that happens, it is the user\[cq]s responsibility to stop the mount
+When that happens, it is the user\[aq]s responsibility to stop the mount
 manually.
 .PP
 Stopping the mount manually:
@@ -3298,8 +3442,8 @@ network shares, as Windows expects normal drives to be fast and
 reliable, while cloud storage is far from that.
 See also Limitations section below for more info
 .PP
-Add \[lq]\[en]fuse\-flag \[en]VolumePrefix=\[rq] to your \[lq]mount\[rq]
-command, \f[B]replacing \[lq]share\[rq] with any other name of your
+Add \[dq]\-\-fuse\-flag \-\-VolumePrefix=\[dq] to your \[dq]mount\[dq]
+command, \f[B]replacing \[dq]share\[dq] with any other name of your
 choice if you are mounting more than one remote\f[R].
 Otherwise, the mountpoints will conflict and your mounted filesystems
 will overlap.
@@ -3308,11 +3452,11 @@ Read more about drive
 mapping (https://en.wikipedia.org/wiki/Drive_mapping)
 .SS Limitations
 .PP
-Without the use of \[lq]\[en]vfs\-cache\-mode\[rq] this can only write
+Without the use of \[dq]\-\-vfs\-cache\-mode\[dq] this can only write
 files sequentially, it can only seek when reading.
-This means that many applications won\[cq]t work with their files on an
-rclone mount without \[lq]\[en]vfs\-cache\-mode writes\[rq] or
-\[lq]\[en]vfs\-cache\-mode full\[rq].
+This means that many applications won\[aq]t work with their files on an
+rclone mount without \[dq]\-\-vfs\-cache\-mode writes\[dq] or
+\[dq]\-\-vfs\-cache\-mode full\[dq].
 See the File Caching section for more info.
 .PP
 The bucket based remotes (eg Swift, S3, Google Compute Storage, B2,
@@ -3326,16 +3470,15 @@ Only supported on Linux, FreeBSD, OS X and Windows at the moment.
 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\[cq]t use retries in the same way without
+However rclone mount can\[aq]t use retries in the same way without
 making local copies of the uploads.
 Look at the file caching for solutions to make mount more reliable.
 .SS Attribute caching
 .PP
-You can use the flag \[en]attr\-timeout to set the time the kernel
-caches the attributes (size, modification time etc) for directory
-entries.
+You can use the flag \-\-attr\-timeout to set the time the kernel caches
+the attributes (size, modification time etc) for directory entries.
 .PP
-The default is \[lq]1s\[rq] which caches files just long enough to avoid
+The default is \[dq]1s\[dq] which caches files just long enough to avoid
 too many callbacks to rclone from the kernel.
 .PP
 In theory 0s should be the correct value for filesystems which can
@@ -3348,22 +3491,22 @@ and excessive time listing
 directories (https://github.com/rclone/rclone/issues/2095#issuecomment-371141147).
 .PP
 The kernel can cache the info about a file for the time given by
-\[lq]\[en]attr\-timeout\[rq].
+\[dq]\-\-attr\-timeout\[dq].
 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 \[lq]\[en]attr\-timeout 1s\[rq] this is very unlikely but not
+With \[dq]\-\-attr\-timeout 1s\[dq] this is very unlikely but not
 impossible.
-The higher you set \[lq]\[en]attr\-timeout\[rq] the more likely it is.
-The default setting of \[lq]1s\[rq] is the lowest setting which
+The higher you set \[dq]\-\-attr\-timeout\[dq] the more likely it is.
+The default setting of \[dq]1s\[dq] is the lowest setting which
 mitigates the problems above.
 .PP
-If you set it higher (`10s' or `1m' 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.
+If you set it higher (\[aq]10s\[aq] or \[aq]1m\[aq] 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.
 .PP
-If files don\[cq]t change on the remote outside of the control of rclone
+If files don\[aq]t change on the remote outside of the control of rclone
 then there is no chance of corruption.
 .PP
 This is the same as setting the attr_timeout option in mount.fuse.
@@ -3381,43 +3524,66 @@ Units having the rclone mount service specified as a requirement will
 see all files and folders immediately in this mode.
 .SS chunked reading
 .PP
-\[en]vfs\-read\-chunk\-size will enable reading the source objects in
+\-\-vfs\-read\-chunk\-size will enable reading the source objects in
 parts.
 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.
 .PP
-When \[en]vfs\-read\-chunk\-size\-limit is also specified and greater
-than \[en]vfs\-read\-chunk\-size, the chunk size for each open file will
+When \-\-vfs\-read\-chunk\-size\-limit is also specified and greater
+than \-\-vfs\-read\-chunk\-size, the chunk size for each open file will
 get doubled for each chunk read, until the specified value is reached.
 A value of \-1 will disable the limit and the chunk size will grow
 indefinitely.
 .PP
-With \[en]vfs\-read\-chunk\-size 100M and
-\[en]vfs\-read\-chunk\-size\-limit 0 the following parts will be
+With \-\-vfs\-read\-chunk\-size 100M and
+\-\-vfs\-read\-chunk\-size\-limit 0 the following parts will be
 downloaded: 0\-100M, 100M\-200M, 200M\-300M, 300M\-400M and so on.
-When \[en]vfs\-read\-chunk\-size\-limit 500M is specified, the result
+When \-\-vfs\-read\-chunk\-size\-limit 500M is specified, the result
 would be 0\-100M, 100M\-300M, 300M\-700M, 700M\-1200M, 1200M\-1700M and
 so on.
 .PP
-Chunked reading will only work with \[en]vfs\-cache\-mode < full, as the
+Chunked reading will only work with \-\-vfs\-cache\-mode < full, as the
 file will always be copied to the vfs cache before opening with
-\[en]vfs\-cache\-mode full.
-.SS Directory Cache
+\-\-vfs\-cache\-mode full.
+.SS VFS \- Virtual File System
 .PP
-Using the \f[C]\-\-dir\-cache\-time\f[R] flag, you can set how long a
-directory should be considered up to date and not refreshed from the
+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.
+.PP
+Cloud storage objects have lots of properties which aren\[aq]t like disk
+files \- you can\[aq]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.
+.PP
+The VFS layer also implements a directory cache \- this caches info
+about files and directories (but not the data) in memory.
+.SS VFS Directory Cache
+.PP
+Using the \f[C]\-\-dir\-cache\-time\f[R] flag, you can control how long
+a directory should be considered up to date and not refreshed from the
 backend.
-Changes made locally in the mount may appear immediately or invalidate
-the cache.
-However, changes done on the remote will only be picked up once the
+Changes made through the mount will appear immediately or invalidate the
+cache.
+.IP
+.nf
+\f[C]
+\-\-dir\-cache\-time duration   Time to cache directory entries for. (default 5m0s)
+\-\-poll\-interval duration    Time to wait between polling for changes.
+\f[R]
+.fi
+.PP
+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 on within the
+If the backend supports polling, changes will be picked up within the
 polling interval.
 .PP
-Alternatively, you can send a \f[C]SIGHUP\f[R] signal to rclone for it
-to flush all directory caches, regardless of how old they are.
+You can send a \f[C]SIGHUP\f[R] 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:
 .IP
@@ -3443,42 +3609,44 @@ Or individual files or directories:
 rclone rc vfs/forget file=path/to/file dir=path/to/dir
 \f[R]
 .fi
-.SS File Buffering
+.SS VFS File Buffering
 .PP
 The \f[C]\-\-buffer\-size\f[R] flag determines the amount of memory,
 that will be used to buffer data in advance.
 .PP
-Each open file descriptor will try to keep the specified amount of data
-in memory at all times.
-The buffered data is bound to one file descriptor and won\[cq]t be
-shared between multiple open file descriptors of the same file.
+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\[aq]t be shared.
 .PP
-This flag is a upper limit for the used memory per file descriptor.
+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.
+.PP
 The maximum memory used by rclone for buffering can be up to
 \f[C]\-\-buffer\-size * open files\f[R].
-.SS File Caching
+.SS VFS File Caching
 .PP
 These flags control the VFS file caching options.
-The VFS layer is used by rclone mount to make a cloud storage system
-work more like a normal file system.
+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.
 .PP
-You\[cq]ll need to enable VFS caching if you want, for example, to read
+For example you\[aq]ll need to enable VFS caching if you want to read
 and write simultaneously to a file.
 See below for more details.
 .PP
-Note that the VFS cache works in addition to the cache backend and you
-may find that you need one or the other or both.
+Note that the VFS cache is separate from the cache backend and you may
+find that you need one or the other or both.
 .IP
 .nf
 \f[C]
 \-\-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 age of objects in the cache. (default 1h0m0s)
-\-\-vfs\-cache\-mode string              Cache mode off|minimal|writes|full (default \[dq]off\[dq])
+\-\-vfs\-cache\-max\-size SizeSuffix      Max total size of objects in the cache. (default off)
 \-\-vfs\-cache\-poll\-interval duration   Interval to poll the cache for stale objects. (default 1m0s)
-\-\-vfs\-cache\-max\-size int             Max total size of objects in the cache. (default off)
+\-\-vfs\-write\-back duration            Time to writeback files after last use when using cache. (default 5s)
 \f[R]
 .fi
 .PP
@@ -3494,25 +3662,24 @@ The higher the cache mode the more compatible rclone becomes at the cost
 of using disk space.
 .PP
 Note that files are written back to the remote only when they are closed
-so if rclone is quit or dies with open files then these won\[cq]t get
-written back to the remote.
-However they will still be in the on disk cache.
+and if they haven\[aq]t been accessed for \-\-vfs\-write\-back second.
+If rclone is quit or dies with files that haven\[aq]t been uploaded,
+these will be uploaded next time rclone is run with the same flags.
 .PP
-If using \[en]vfs\-cache\-max\-size note that the cache may exceed this
+If using \-\-vfs\-cache\-max\-size note that the cache may exceed this
 size for two reasons.
-Firstly because it is only checked every
-\[en]vfs\-cache\-poll\-interval.
+Firstly because it is only checked every \-\-vfs\-cache\-poll\-interval.
 Secondly because open files cannot be evicted from the cache.
-.SS \[en]vfs\-cache\-mode off
+.SS \-\-vfs\-cache\-mode off
 .PP
-In this mode the cache will read directly from the remote and write
-directly to the remote without caching anything on disk.
+In this mode (the default) the cache will read directly from the remote
+and write directly to the remote without caching anything on disk.
 .PP
 This will mean some operations are not possible
 .IP \[bu] 2
-Files can\[cq]t be opened for both read AND write
+Files can\[aq]t be opened for both read AND write
 .IP \[bu] 2
-Files opened for write can\[cq]t be seeked
+Files opened for write can\[aq]t be seeked
 .IP \[bu] 2
 Existing files opened for write must have O_TRUNC set
 .IP \[bu] 2
@@ -3522,57 +3689,108 @@ Files open for write only will behave as if O_TRUNC was supplied
 .IP \[bu] 2
 Open modes O_APPEND, O_TRUNC are ignored
 .IP \[bu] 2
-If an upload fails it can\[cq]t be retried
-.SS \[en]vfs\-cache\-mode minimal
+If an upload fails it can\[aq]t be retried
+.SS \-\-vfs\-cache\-mode minimal
 .PP
-This is very similar to \[lq]off\[rq] except that files opened for read
-AND write will be buffered to disks.
+This is very similar to \[dq]off\[dq] 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.
 .PP
 These operations are not possible
 .IP \[bu] 2
-Files opened for write only can\[cq]t be seeked
+Files opened for write only can\[aq]t be seeked
 .IP \[bu] 2
 Existing files opened for write must have O_TRUNC set
 .IP \[bu] 2
 Files opened for write only will ignore O_APPEND, O_TRUNC
 .IP \[bu] 2
-If an upload fails it can\[cq]t be retried
-.SS \[en]vfs\-cache\-mode writes
+If an upload fails it can\[aq]t be retried
+.SS \-\-vfs\-cache\-mode writes
 .PP
 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.
 .PP
 This mode should support all normal file system operations.
 .PP
-If an upload fails it will be retried up to \[en]low\-level\-retries
-times.
-.SS \[en]vfs\-cache\-mode full
+If an upload fails it will be retried at exponentially increasing
+intervals up to 1 minute.
+.SS \-\-vfs\-cache\-mode full
 .PP
 In this mode all reads and writes are buffered to and from disk.
-When a file is opened for read it will be downloaded in its entirety
-first.
+When data is read from the remote this is buffered to disk as well.
 .PP
-This may be appropriate for your needs, or you may prefer to look at the
-cache backend which does a much more sophisticated job of caching,
-including caching directory hierarchies and chunks of files.
+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 dowloaded.
 .PP
-In this mode, unlike the others, when a file is written to the disk, it
-will be kept on the disk after it is written to the remote.
-It will be purged on a schedule according to
-\f[C]\-\-vfs\-cache\-max\-age\f[R].
+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.
 .PP
-This mode should support all normal file system operations.
+This mode should support all normal file system operations and is
+otherwise identical to \-\-vfs\-cache\-mode writes.
 .PP
-If an upload or download fails it will be retried up to
-\[en]low\-level\-retries times.
-.SS Case Sensitivity
+When reading a file rclone will read \-\-buffer\-size plus
+\-\-vfs\-read\-ahead bytes ahead.
+The \-\-buffer\-size is buffered in memory whereas the
+\-\-vfs\-read\-ahead is buffered on disk.
+.PP
+When using this mode it is recommended that \-\-buffer\-size is not set
+too big and \-\-vfs\-read\-ahead is set large if required.
+.SS VFS Performance
+.PP
+These flags may be used to enable/disable features of the VFS for
+performance or other reasons.
+.PP
+In particular S3 and Swift benefit hugely from the \-\-no\-modtime flag
+(or use \-\-use\-server\-modtime for a slightly different effect) as
+each read of the modification time takes a transaction.
+.IP
+.nf
+\f[C]
+\-\-no\-checksum     Don\[aq]t compare checksums on up/download.
+\-\-no\-modtime      Don\[aq]t read/write the modification time (can speed things up).
+\-\-no\-seek         Don\[aq]t allow seeking in files.
+\-\-read\-only       Mount read\-only.
+\f[R]
+.fi
+.PP
+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 is advantageous because some cloud providers account for reads
+being all the data requested, not all the data delivered.
+.PP
+Rclone will keep doubling the chunk size requested starting at
+\-\-vfs\-read\-chunk\-size with a maximum of
+\-\-vfs\-read\-chunk\-size\-limit unless it is set to \[dq]off\[dq] in
+which case there will be no limit.
+.IP
+.nf
+\f[C]
+\-\-vfs\-read\-chunk\-size SizeSuffix        Read the source objects in chunks. (default 128M)
+\-\-vfs\-read\-chunk\-size\-limit SizeSuffix  Max chunk doubling size (default \[dq]off\[dq])
+\f[R]
+.fi
+.PP
+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.
+.IP
+.nf
+\f[C]
+\-\-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)
+\f[R]
+.fi
+.SS VFS Case Sensitivity
 .PP
 Linux file systems are case\-sensitive: two files can differ only by
 case, and the exact case must be used when opening a file.
 .PP
-Windows is not like most other operating systems supported by rclone.
 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
@@ -3584,12 +3802,12 @@ Usually file systems on macOS are case\-insensitive.
 It is possible to make macOS file systems case\-sensitive but that is
 not the default
 .PP
-The \[lq]\[en]vfs\-case\-insensitive\[rq] mount flag controls how rclone
+The \[dq]\-\-vfs\-case\-insensitive\[dq] mount flag controls how rclone
 handles these two cases.
-If its value is \[lq]false\[rq], rclone passes file names to the mounted
-file system as is.
-If the flag is \[lq]true\[rq] (or appears without a value on command
-line), rclone may perform a \[lq]fixup\[rq] as explained below.
+If its value is \[dq]false\[dq], rclone passes file names to the mounted
+file system as\-is.
+If the flag is \[dq]true\[dq] (or appears without a value on command
+line), rclone may perform a \[dq]fixup\[dq] as explained below.
 .PP
 The user may specify a file name to open/delete/rename/etc with a case
 different than what is stored on mounted file system.
@@ -3605,13 +3823,13 @@ an underlying mounted file system.
 Note that case sensitivity of the operating system running rclone (the
 target) may differ from case sensitivity of a file system mounted by
 rclone (the source).
-The flag controls whether \[lq]fixup\[rq] is performed to satisfy the
+The flag controls whether \[dq]fixup\[dq] is performed to satisfy the
 target.
 .PP
-If the flag is not provided on command line, then its default value
-depends on the operating system where rclone runs: \[lq]true\[rq] on
-Windows and macOS, \[lq]false\[rq] otherwise.
-If the flag is provided without a value, then it is \[lq]true\[rq].
+If the flag is not provided on the command line, then its default value
+depends on the operating system where rclone runs: \[dq]true\[dq] on
+Windows and macOS, \[dq]false\[dq] otherwise.
+If the flag is provided without a value, then it is \[dq]true\[dq].
 .IP
 .nf
 \f[C]
@@ -3651,9 +3869,11 @@ rclone mount remote:path /path/to/mountpoint [flags]
       \-\-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\-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 128M)
       \-\-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. \[aq]off\[aq] is unlimited. (default off)
       \-\-vfs\-read\-wait duration                 Time to wait for in\-sequence read before seeking. (default 20ms)
+      \-\-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 (not supported by all OSes).
       \-\-write\-back\-cache                       Makes kernel buffer writes before sending them to rclone. Without this, writethrough caching is used.
@@ -3701,12 +3921,13 @@ if src is directory
 \f[R]
 .fi
 .PP
-This doesn\[cq]t transfer unchanged files, testing by size and
+This doesn\[aq]t transfer unchanged files, testing by size and
 modification time or MD5SUM.
 src will be deleted on successful transfer.
 .PP
 \f[B]Important\f[R]: Since this can cause data loss, test first with the
-\[en]dry\-run flag.
+\f[C]\-\-dry\-run\f[R] or the \f[C]\-\-interactive\f[R]/\f[C]\-i\f[R]
+flag.
 .PP
 \f[B]Note\f[R]: Use the \f[C]\-P\f[R]/\f[C]\-\-progress\f[R] flag to
 view real\-time transfer statistics.
@@ -3737,15 +3958,15 @@ Explore a remote with a text based user interface.
 .PP
 This displays a text based user interface allowing the navigation of a
 remote.
-It is most useful for answering the question \- \[lq]What is using all
-my disk space?\[rq].
+It is most useful for answering the question \- \[dq]What is using all
+my disk space?\[dq].
 .PP
 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.
 .PP
-Here are the keys \- press `?' to toggle the help on and off
+Here are the keys \- press \[aq]?\[aq] to toggle the help on and off
 .IP
 .nf
 \f[C]
@@ -3769,7 +3990,7 @@ rclone remotes.
 It is missing lots of features at the moment but is useful as it stands.
 .PP
 Note that it might take some time to delete big files/folders.
-The UI won\[cq]t respond in the meantime since the deletion is done
+The UI won\[aq]t respond in the meantime since the deletion is done
 synchronously.
 .IP
 .nf
@@ -3793,10 +4014,32 @@ rclone (https://rclone.org/commands/rclone/) \- Show help for rclone
 commands, flags and backends.
 .SH rclone obscure
 .PP
-Obscure password for use in the rclone.conf
+Obscure password for use in the rclone config file
 .SS Synopsis
 .PP
-Obscure password for use in the rclone.conf
+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 \f[B]not\f[R] a secure way of encrypting these passwords as
+rclone can decrypt them \- it is to prevent \[dq]eyedropping\[dq] \-
+namely someone seeing a password in the rclone config file by accident.
+.PP
+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.
+.PP
+This command can also accept a password through STDIN instead of an
+argument by passing a hyphen as an argument.
+Example:
+.PP
+echo \[dq]secretpassword\[dq] | rclone obscure \-
+.PP
+If there is no data on STDIN to read, rclone obscure will default to
+obfuscating the hyphen itself.
+.PP
+If you want to encrypt the config file then please use config file
+encryption \- see rclone
+config (https://rclone.org/commands/rclone_config/) for more info.
 .IP
 .nf
 \f[C]
@@ -3823,28 +4066,28 @@ Run a command against a running rclone.
 .SS Synopsis
 .PP
 This runs a command against a running rclone.
-Use the \[en]url flag to specify an non default URL to connect on.
-This can be either a \[lq]:port\[rq] which is taken to mean
-\[lq]http://localhost:port\[rq] or a \[lq]host:port\[rq] which is taken
-to mean \[lq]http://host:port\[rq]
+Use the \-\-url flag to specify an non default URL to connect on.
+This can be either a \[dq]:port\[dq] which is taken to mean
+\[dq]http://localhost:port\[dq] or a \[dq]host:port\[dq] which is taken
+to mean \[dq]http://host:port\[dq]
 .PP
-A username and password can be passed in with \[en]user and \[en]pass.
+A username and password can be passed in with \-\-user and \-\-pass.
 .PP
-Note that \[en]rc\-addr, \[en]rc\-user, \[en]rc\-pass will be read also
-for \[en]url, \[en]user, \[en]pass.
+Note that \-\-rc\-addr, \-\-rc\-user, \-\-rc\-pass will be read also for
+\-\-url, \-\-user, \-\-pass.
 .PP
 Arguments should be passed in as parameter=value.
 .PP
 The result will be returned as a JSON object by default.
 .PP
-The \[en]json parameter can be used to pass in a JSON blob as an input
+The \-\-json 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.
 .PP
-The \-o/\[en]opt option can be used to set a key \[lq]opt\[rq] with key,
-value options in the form \[lq]\-o key=value\[rq] or \[lq]\-o key\[rq].
+The \-o/\-\-opt option can be used to set a key \[dq]opt\[dq] with key,
+value options in the form \[dq]\-o key=value\[dq] or \[dq]\-o key\[dq].
 It can be repeated as many times as required.
-This is useful for rc commands which take the \[lq]opt\[rq] parameter
+This is useful for rc commands which take the \[dq]opt\[dq] parameter
 which by convention is a dictionary of strings.
 .IP
 .nf
@@ -3853,7 +4096,7 @@ which by convention is a dictionary of strings.
 \f[R]
 .fi
 .PP
-Will place this in the \[lq]opt\[rq] value
+Will place this in the \[dq]opt\[dq] value
 .IP
 .nf
 \f[C]
@@ -3861,10 +4104,10 @@ Will place this in the \[lq]opt\[rq] value
 \f[R]
 .fi
 .PP
-The \-a/\[en]arg option can be used to set strings in the \[lq]arg\[rq]
+The \-a/\-\-arg option can be used to set strings in the \[dq]arg\[dq]
 value.
 It can be repeated as many times as required.
-This is useful for rc commands which take the \[lq]arg\[rq] parameter
+This is useful for rc commands which take the \[dq]arg\[dq] parameter
 which by convention is a list of strings.
 .IP
 .nf
@@ -3873,7 +4116,7 @@ which by convention is a list of strings.
 \f[R]
 .fi
 .PP
-Will place this in the \[lq]arg\[rq] value
+Will place this in the \[dq]arg\[dq] value
 .IP
 .nf
 \f[C]
@@ -3881,8 +4124,8 @@ Will place this in the \[lq]arg\[rq] value
 \f[R]
 .fi
 .PP
-Use \[en]loopback to connect to the rclone instance running \[lq]rclone
-rc\[rq].
+Use \-\-loopback to connect to the rclone instance running \[dq]rclone
+rc\[dq].
 This is very useful for testing commands without having to run an rclone
 rc server, eg:
 .IP
@@ -3892,7 +4135,7 @@ rclone rc \-\-loopback operations/about fs=/
 \f[R]
 .fi
 .PP
-Use \[lq]rclone rc\[rq] to see a list of all possible commands.
+Use \[dq]rclone rc\[dq] to see a list of all possible commands.
 .IP
 .nf
 \f[C]
@@ -3954,7 +4197,7 @@ performance.
 .PP
 Note that the upload can also not be retried because the data is not
 kept around until the upload succeeds.
-If you need to transfer a lot of data, you\[cq]re better off caching
+If you need to transfer a lot of data, you\[aq]re better off caching
 locally and then \f[C]rclone move\f[R] it to the destination.
 .IP
 .nf
@@ -4020,7 +4263,7 @@ This removes any empty directories (or directories that only contain
 empty directories) under the path that it finds, including the path if
 it has nothing in.
 .PP
-If you supply the \[en]leave\-root flag, it will not remove the root
+If you supply the \-\-leave\-root flag, it will not remove the root
 directory.
 .PP
 This is useful for tidying up remotes that rclone has left a lot of
@@ -4093,7 +4336,7 @@ rclone serve http (https://rclone.org/commands/rclone_serve_http/) \-
 Serve the remote over HTTP.
 .IP \[bu] 2
 rclone serve restic (https://rclone.org/commands/rclone_serve_restic/)
-\- Serve the remote for restic\[cq]s REST API.
+\- Serve the remote for restic\[aq]s REST API.
 .IP \[bu] 2
 rclone serve sftp (https://rclone.org/commands/rclone_serve_sftp/) \-
 Serve the remote over SFTP.
@@ -4120,30 +4363,53 @@ This means that some players might show files that they are not able to
 play back correctly.
 .SS Server options
 .PP
-Use \[en]addr to specify which IP address and port the server should
-listen on, eg \[en]addr 1.2.3.4:8000 or \[en]addr :8080 to listen to all
-IPs.
+Use \f[C]\-\-addr\f[R] to specify which IP address and port the server
+should listen on, eg \f[C]\-\-addr 1.2.3.4:8000\f[R] or
+\f[C]\-\-addr :8080\f[R] to listen to all IPs.
 .PP
-Use \[en]name to choose the friendly server name, which is by default
-\[lq]rclone (hostname)\[rq].
+Use \f[C]\-\-name\f[R] to choose the friendly server name, which is by
+default \[dq]rclone (hostname)\[dq].
 .PP
-Use \[en]log\-trace in conjunction with \-vv to enable additional debug
-logging of all UPNP traffic.
-.SS Directory Cache
+Use \f[C]\-\-log\-trace\f[R] in conjunction with \f[C]\-vv\f[R] to
+enable additional debug logging of all UPNP traffic.
+.SS VFS \- Virtual File System
 .PP
-Using the \f[C]\-\-dir\-cache\-time\f[R] flag, you can set how long a
-directory should be considered up to date and not refreshed from the
+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.
+.PP
+Cloud storage objects have lots of properties which aren\[aq]t like disk
+files \- you can\[aq]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.
+.PP
+The VFS layer also implements a directory cache \- this caches info
+about files and directories (but not the data) in memory.
+.SS VFS Directory Cache
+.PP
+Using the \f[C]\-\-dir\-cache\-time\f[R] flag, you can control how long
+a directory should be considered up to date and not refreshed from the
 backend.
-Changes made locally in the mount may appear immediately or invalidate
-the cache.
-However, changes done on the remote will only be picked up once the
+Changes made through the mount will appear immediately or invalidate the
+cache.
+.IP
+.nf
+\f[C]
+\-\-dir\-cache\-time duration   Time to cache directory entries for. (default 5m0s)
+\-\-poll\-interval duration    Time to wait between polling for changes.
+\f[R]
+.fi
+.PP
+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 on within the
+If the backend supports polling, changes will be picked up within the
 polling interval.
 .PP
-Alternatively, you can send a \f[C]SIGHUP\f[R] signal to rclone for it
-to flush all directory caches, regardless of how old they are.
+You can send a \f[C]SIGHUP\f[R] 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:
 .IP
@@ -4169,42 +4435,44 @@ Or individual files or directories:
 rclone rc vfs/forget file=path/to/file dir=path/to/dir
 \f[R]
 .fi
-.SS File Buffering
+.SS VFS File Buffering
 .PP
 The \f[C]\-\-buffer\-size\f[R] flag determines the amount of memory,
 that will be used to buffer data in advance.
 .PP
-Each open file descriptor will try to keep the specified amount of data
-in memory at all times.
-The buffered data is bound to one file descriptor and won\[cq]t be
-shared between multiple open file descriptors of the same file.
+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\[aq]t be shared.
 .PP
-This flag is a upper limit for the used memory per file descriptor.
+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.
+.PP
 The maximum memory used by rclone for buffering can be up to
 \f[C]\-\-buffer\-size * open files\f[R].
-.SS File Caching
+.SS VFS File Caching
 .PP
 These flags control the VFS file caching options.
-The VFS layer is used by rclone mount to make a cloud storage system
-work more like a normal file system.
+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.
 .PP
-You\[cq]ll need to enable VFS caching if you want, for example, to read
+For example you\[aq]ll need to enable VFS caching if you want to read
 and write simultaneously to a file.
 See below for more details.
 .PP
-Note that the VFS cache works in addition to the cache backend and you
-may find that you need one or the other or both.
+Note that the VFS cache is separate from the cache backend and you may
+find that you need one or the other or both.
 .IP
 .nf
 \f[C]
 \-\-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 age of objects in the cache. (default 1h0m0s)
-\-\-vfs\-cache\-mode string              Cache mode off|minimal|writes|full (default \[dq]off\[dq])
+\-\-vfs\-cache\-max\-size SizeSuffix      Max total size of objects in the cache. (default off)
 \-\-vfs\-cache\-poll\-interval duration   Interval to poll the cache for stale objects. (default 1m0s)
-\-\-vfs\-cache\-max\-size int             Max total size of objects in the cache. (default off)
+\-\-vfs\-write\-back duration            Time to writeback files after last use when using cache. (default 5s)
 \f[R]
 .fi
 .PP
@@ -4220,25 +4488,24 @@ The higher the cache mode the more compatible rclone becomes at the cost
 of using disk space.
 .PP
 Note that files are written back to the remote only when they are closed
-so if rclone is quit or dies with open files then these won\[cq]t get
-written back to the remote.
-However they will still be in the on disk cache.
+and if they haven\[aq]t been accessed for \-\-vfs\-write\-back second.
+If rclone is quit or dies with files that haven\[aq]t been uploaded,
+these will be uploaded next time rclone is run with the same flags.
 .PP
-If using \[en]vfs\-cache\-max\-size note that the cache may exceed this
+If using \-\-vfs\-cache\-max\-size note that the cache may exceed this
 size for two reasons.
-Firstly because it is only checked every
-\[en]vfs\-cache\-poll\-interval.
+Firstly because it is only checked every \-\-vfs\-cache\-poll\-interval.
 Secondly because open files cannot be evicted from the cache.
-.SS \[en]vfs\-cache\-mode off
+.SS \-\-vfs\-cache\-mode off
 .PP
-In this mode the cache will read directly from the remote and write
-directly to the remote without caching anything on disk.
+In this mode (the default) the cache will read directly from the remote
+and write directly to the remote without caching anything on disk.
 .PP
 This will mean some operations are not possible
 .IP \[bu] 2
-Files can\[cq]t be opened for both read AND write
+Files can\[aq]t be opened for both read AND write
 .IP \[bu] 2
-Files opened for write can\[cq]t be seeked
+Files opened for write can\[aq]t be seeked
 .IP \[bu] 2
 Existing files opened for write must have O_TRUNC set
 .IP \[bu] 2
@@ -4248,57 +4515,108 @@ Files open for write only will behave as if O_TRUNC was supplied
 .IP \[bu] 2
 Open modes O_APPEND, O_TRUNC are ignored
 .IP \[bu] 2
-If an upload fails it can\[cq]t be retried
-.SS \[en]vfs\-cache\-mode minimal
+If an upload fails it can\[aq]t be retried
+.SS \-\-vfs\-cache\-mode minimal
 .PP
-This is very similar to \[lq]off\[rq] except that files opened for read
-AND write will be buffered to disks.
+This is very similar to \[dq]off\[dq] 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.
 .PP
 These operations are not possible
 .IP \[bu] 2
-Files opened for write only can\[cq]t be seeked
+Files opened for write only can\[aq]t be seeked
 .IP \[bu] 2
 Existing files opened for write must have O_TRUNC set
 .IP \[bu] 2
 Files opened for write only will ignore O_APPEND, O_TRUNC
 .IP \[bu] 2
-If an upload fails it can\[cq]t be retried
-.SS \[en]vfs\-cache\-mode writes
+If an upload fails it can\[aq]t be retried
+.SS \-\-vfs\-cache\-mode writes
 .PP
 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.
 .PP
 This mode should support all normal file system operations.
 .PP
-If an upload fails it will be retried up to \[en]low\-level\-retries
-times.
-.SS \[en]vfs\-cache\-mode full
+If an upload fails it will be retried at exponentially increasing
+intervals up to 1 minute.
+.SS \-\-vfs\-cache\-mode full
 .PP
 In this mode all reads and writes are buffered to and from disk.
-When a file is opened for read it will be downloaded in its entirety
-first.
+When data is read from the remote this is buffered to disk as well.
 .PP
-This may be appropriate for your needs, or you may prefer to look at the
-cache backend which does a much more sophisticated job of caching,
-including caching directory hierarchies and chunks of files.
+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 dowloaded.
 .PP
-In this mode, unlike the others, when a file is written to the disk, it
-will be kept on the disk after it is written to the remote.
-It will be purged on a schedule according to
-\f[C]\-\-vfs\-cache\-max\-age\f[R].
+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.
 .PP
-This mode should support all normal file system operations.
+This mode should support all normal file system operations and is
+otherwise identical to \-\-vfs\-cache\-mode writes.
 .PP
-If an upload or download fails it will be retried up to
-\[en]low\-level\-retries times.
-.SS Case Sensitivity
+When reading a file rclone will read \-\-buffer\-size plus
+\-\-vfs\-read\-ahead bytes ahead.
+The \-\-buffer\-size is buffered in memory whereas the
+\-\-vfs\-read\-ahead is buffered on disk.
+.PP
+When using this mode it is recommended that \-\-buffer\-size is not set
+too big and \-\-vfs\-read\-ahead is set large if required.
+.SS VFS Performance
+.PP
+These flags may be used to enable/disable features of the VFS for
+performance or other reasons.
+.PP
+In particular S3 and Swift benefit hugely from the \-\-no\-modtime flag
+(or use \-\-use\-server\-modtime for a slightly different effect) as
+each read of the modification time takes a transaction.
+.IP
+.nf
+\f[C]
+\-\-no\-checksum     Don\[aq]t compare checksums on up/download.
+\-\-no\-modtime      Don\[aq]t read/write the modification time (can speed things up).
+\-\-no\-seek         Don\[aq]t allow seeking in files.
+\-\-read\-only       Mount read\-only.
+\f[R]
+.fi
+.PP
+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 is advantageous because some cloud providers account for reads
+being all the data requested, not all the data delivered.
+.PP
+Rclone will keep doubling the chunk size requested starting at
+\-\-vfs\-read\-chunk\-size with a maximum of
+\-\-vfs\-read\-chunk\-size\-limit unless it is set to \[dq]off\[dq] in
+which case there will be no limit.
+.IP
+.nf
+\f[C]
+\-\-vfs\-read\-chunk\-size SizeSuffix        Read the source objects in chunks. (default 128M)
+\-\-vfs\-read\-chunk\-size\-limit SizeSuffix  Max chunk doubling size (default \[dq]off\[dq])
+\f[R]
+.fi
+.PP
+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.
+.IP
+.nf
+\f[C]
+\-\-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)
+\f[R]
+.fi
+.SS VFS Case Sensitivity
 .PP
 Linux file systems are case\-sensitive: two files can differ only by
 case, and the exact case must be used when opening a file.
 .PP
-Windows is not like most other operating systems supported by rclone.
 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
@@ -4310,12 +4628,12 @@ Usually file systems on macOS are case\-insensitive.
 It is possible to make macOS file systems case\-sensitive but that is
 not the default
 .PP
-The \[lq]\[en]vfs\-case\-insensitive\[rq] mount flag controls how rclone
+The \[dq]\-\-vfs\-case\-insensitive\[dq] mount flag controls how rclone
 handles these two cases.
-If its value is \[lq]false\[rq], rclone passes file names to the mounted
-file system as is.
-If the flag is \[lq]true\[rq] (or appears without a value on command
-line), rclone may perform a \[lq]fixup\[rq] as explained below.
+If its value is \[dq]false\[dq], rclone passes file names to the mounted
+file system as\-is.
+If the flag is \[dq]true\[dq] (or appears without a value on command
+line), rclone may perform a \[dq]fixup\[dq] as explained below.
 .PP
 The user may specify a file name to open/delete/rename/etc with a case
 different than what is stored on mounted file system.
@@ -4331,13 +4649,13 @@ an underlying mounted file system.
 Note that case sensitivity of the operating system running rclone (the
 target) may differ from case sensitivity of a file system mounted by
 rclone (the source).
-The flag controls whether \[lq]fixup\[rq] is performed to satisfy the
+The flag controls whether \[dq]fixup\[dq] is performed to satisfy the
 target.
 .PP
-If the flag is not provided on command line, then its default value
-depends on the operating system where rclone runs: \[lq]true\[rq] on
-Windows and macOS, \[lq]false\[rq] otherwise.
-If the flag is provided without a value, then it is \[lq]true\[rq].
+If the flag is not provided on the command line, then its default value
+depends on the operating system where rclone runs: \[dq]true\[dq] on
+Windows and macOS, \[dq]false\[dq] otherwise.
+If the flag is provided without a value, then it is \[dq]true\[dq].
 .IP
 .nf
 \f[C]
@@ -4368,9 +4686,11 @@ rclone serve dlna remote:path [flags]
       \-\-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\-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 128M)
       \-\-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. \[aq]off\[aq] is unlimited. (default off)
       \-\-vfs\-read\-wait duration                 Time to wait for in\-sequence read before seeking. (default 20ms)
+      \-\-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)
 \f[R]
 .fi
@@ -4392,35 +4712,58 @@ This can be viewed with a ftp client or you can make a remote of type
 ftp to read and write it.
 .SS Server options
 .PP
-Use \[en]addr to specify which IP address and port the server should
-listen on, eg \[en]addr 1.2.3.4:8000 or \[en]addr :8080 to listen to all
+Use \-\-addr to specify which IP address and port the server should
+listen on, eg \-\-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.
 .PP
-If you set \[en]addr to listen on a public or LAN accessible IP address
+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.
 .SS Authentication
 .PP
 By default this will serve files without needing a login.
 .PP
-You can set a single username and password with the \[en]user and
-\[en]pass flags.
-.SS Directory Cache
+You can set a single username and password with the \-\-user and
+\-\-pass flags.
+.SS VFS \- Virtual File System
 .PP
-Using the \f[C]\-\-dir\-cache\-time\f[R] flag, you can set how long a
-directory should be considered up to date and not refreshed from the
+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.
+.PP
+Cloud storage objects have lots of properties which aren\[aq]t like disk
+files \- you can\[aq]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.
+.PP
+The VFS layer also implements a directory cache \- this caches info
+about files and directories (but not the data) in memory.
+.SS VFS Directory Cache
+.PP
+Using the \f[C]\-\-dir\-cache\-time\f[R] flag, you can control how long
+a directory should be considered up to date and not refreshed from the
 backend.
-Changes made locally in the mount may appear immediately or invalidate
-the cache.
-However, changes done on the remote will only be picked up once the
+Changes made through the mount will appear immediately or invalidate the
+cache.
+.IP
+.nf
+\f[C]
+\-\-dir\-cache\-time duration   Time to cache directory entries for. (default 5m0s)
+\-\-poll\-interval duration    Time to wait between polling for changes.
+\f[R]
+.fi
+.PP
+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 on within the
+If the backend supports polling, changes will be picked up within the
 polling interval.
 .PP
-Alternatively, you can send a \f[C]SIGHUP\f[R] signal to rclone for it
-to flush all directory caches, regardless of how old they are.
+You can send a \f[C]SIGHUP\f[R] 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:
 .IP
@@ -4446,42 +4789,44 @@ Or individual files or directories:
 rclone rc vfs/forget file=path/to/file dir=path/to/dir
 \f[R]
 .fi
-.SS File Buffering
+.SS VFS File Buffering
 .PP
 The \f[C]\-\-buffer\-size\f[R] flag determines the amount of memory,
 that will be used to buffer data in advance.
 .PP
-Each open file descriptor will try to keep the specified amount of data
-in memory at all times.
-The buffered data is bound to one file descriptor and won\[cq]t be
-shared between multiple open file descriptors of the same file.
+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\[aq]t be shared.
 .PP
-This flag is a upper limit for the used memory per file descriptor.
+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.
+.PP
 The maximum memory used by rclone for buffering can be up to
 \f[C]\-\-buffer\-size * open files\f[R].
-.SS File Caching
+.SS VFS File Caching
 .PP
 These flags control the VFS file caching options.
-The VFS layer is used by rclone mount to make a cloud storage system
-work more like a normal file system.
+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.
 .PP
-You\[cq]ll need to enable VFS caching if you want, for example, to read
+For example you\[aq]ll need to enable VFS caching if you want to read
 and write simultaneously to a file.
 See below for more details.
 .PP
-Note that the VFS cache works in addition to the cache backend and you
-may find that you need one or the other or both.
+Note that the VFS cache is separate from the cache backend and you may
+find that you need one or the other or both.
 .IP
 .nf
 \f[C]
 \-\-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 age of objects in the cache. (default 1h0m0s)
-\-\-vfs\-cache\-mode string              Cache mode off|minimal|writes|full (default \[dq]off\[dq])
+\-\-vfs\-cache\-max\-size SizeSuffix      Max total size of objects in the cache. (default off)
 \-\-vfs\-cache\-poll\-interval duration   Interval to poll the cache for stale objects. (default 1m0s)
-\-\-vfs\-cache\-max\-size int             Max total size of objects in the cache. (default off)
+\-\-vfs\-write\-back duration            Time to writeback files after last use when using cache. (default 5s)
 \f[R]
 .fi
 .PP
@@ -4497,25 +4842,24 @@ The higher the cache mode the more compatible rclone becomes at the cost
 of using disk space.
 .PP
 Note that files are written back to the remote only when they are closed
-so if rclone is quit or dies with open files then these won\[cq]t get
-written back to the remote.
-However they will still be in the on disk cache.
+and if they haven\[aq]t been accessed for \-\-vfs\-write\-back second.
+If rclone is quit or dies with files that haven\[aq]t been uploaded,
+these will be uploaded next time rclone is run with the same flags.
 .PP
-If using \[en]vfs\-cache\-max\-size note that the cache may exceed this
+If using \-\-vfs\-cache\-max\-size note that the cache may exceed this
 size for two reasons.
-Firstly because it is only checked every
-\[en]vfs\-cache\-poll\-interval.
+Firstly because it is only checked every \-\-vfs\-cache\-poll\-interval.
 Secondly because open files cannot be evicted from the cache.
-.SS \[en]vfs\-cache\-mode off
+.SS \-\-vfs\-cache\-mode off
 .PP
-In this mode the cache will read directly from the remote and write
-directly to the remote without caching anything on disk.
+In this mode (the default) the cache will read directly from the remote
+and write directly to the remote without caching anything on disk.
 .PP
 This will mean some operations are not possible
 .IP \[bu] 2
-Files can\[cq]t be opened for both read AND write
+Files can\[aq]t be opened for both read AND write
 .IP \[bu] 2
-Files opened for write can\[cq]t be seeked
+Files opened for write can\[aq]t be seeked
 .IP \[bu] 2
 Existing files opened for write must have O_TRUNC set
 .IP \[bu] 2
@@ -4525,57 +4869,108 @@ Files open for write only will behave as if O_TRUNC was supplied
 .IP \[bu] 2
 Open modes O_APPEND, O_TRUNC are ignored
 .IP \[bu] 2
-If an upload fails it can\[cq]t be retried
-.SS \[en]vfs\-cache\-mode minimal
+If an upload fails it can\[aq]t be retried
+.SS \-\-vfs\-cache\-mode minimal
 .PP
-This is very similar to \[lq]off\[rq] except that files opened for read
-AND write will be buffered to disks.
+This is very similar to \[dq]off\[dq] 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.
 .PP
 These operations are not possible
 .IP \[bu] 2
-Files opened for write only can\[cq]t be seeked
+Files opened for write only can\[aq]t be seeked
 .IP \[bu] 2
 Existing files opened for write must have O_TRUNC set
 .IP \[bu] 2
 Files opened for write only will ignore O_APPEND, O_TRUNC
 .IP \[bu] 2
-If an upload fails it can\[cq]t be retried
-.SS \[en]vfs\-cache\-mode writes
+If an upload fails it can\[aq]t be retried
+.SS \-\-vfs\-cache\-mode writes
 .PP
 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.
 .PP
 This mode should support all normal file system operations.
 .PP
-If an upload fails it will be retried up to \[en]low\-level\-retries
-times.
-.SS \[en]vfs\-cache\-mode full
+If an upload fails it will be retried at exponentially increasing
+intervals up to 1 minute.
+.SS \-\-vfs\-cache\-mode full
 .PP
 In this mode all reads and writes are buffered to and from disk.
-When a file is opened for read it will be downloaded in its entirety
-first.
+When data is read from the remote this is buffered to disk as well.
 .PP
-This may be appropriate for your needs, or you may prefer to look at the
-cache backend which does a much more sophisticated job of caching,
-including caching directory hierarchies and chunks of files.
+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 dowloaded.
 .PP
-In this mode, unlike the others, when a file is written to the disk, it
-will be kept on the disk after it is written to the remote.
-It will be purged on a schedule according to
-\f[C]\-\-vfs\-cache\-max\-age\f[R].
+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.
 .PP
-This mode should support all normal file system operations.
+This mode should support all normal file system operations and is
+otherwise identical to \-\-vfs\-cache\-mode writes.
 .PP
-If an upload or download fails it will be retried up to
-\[en]low\-level\-retries times.
-.SS Case Sensitivity
+When reading a file rclone will read \-\-buffer\-size plus
+\-\-vfs\-read\-ahead bytes ahead.
+The \-\-buffer\-size is buffered in memory whereas the
+\-\-vfs\-read\-ahead is buffered on disk.
+.PP
+When using this mode it is recommended that \-\-buffer\-size is not set
+too big and \-\-vfs\-read\-ahead is set large if required.
+.SS VFS Performance
+.PP
+These flags may be used to enable/disable features of the VFS for
+performance or other reasons.
+.PP
+In particular S3 and Swift benefit hugely from the \-\-no\-modtime flag
+(or use \-\-use\-server\-modtime for a slightly different effect) as
+each read of the modification time takes a transaction.
+.IP
+.nf
+\f[C]
+\-\-no\-checksum     Don\[aq]t compare checksums on up/download.
+\-\-no\-modtime      Don\[aq]t read/write the modification time (can speed things up).
+\-\-no\-seek         Don\[aq]t allow seeking in files.
+\-\-read\-only       Mount read\-only.
+\f[R]
+.fi
+.PP
+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 is advantageous because some cloud providers account for reads
+being all the data requested, not all the data delivered.
+.PP
+Rclone will keep doubling the chunk size requested starting at
+\-\-vfs\-read\-chunk\-size with a maximum of
+\-\-vfs\-read\-chunk\-size\-limit unless it is set to \[dq]off\[dq] in
+which case there will be no limit.
+.IP
+.nf
+\f[C]
+\-\-vfs\-read\-chunk\-size SizeSuffix        Read the source objects in chunks. (default 128M)
+\-\-vfs\-read\-chunk\-size\-limit SizeSuffix  Max chunk doubling size (default \[dq]off\[dq])
+\f[R]
+.fi
+.PP
+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.
+.IP
+.nf
+\f[C]
+\-\-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)
+\f[R]
+.fi
+.SS VFS Case Sensitivity
 .PP
 Linux file systems are case\-sensitive: two files can differ only by
 case, and the exact case must be used when opening a file.
 .PP
-Windows is not like most other operating systems supported by rclone.
 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
@@ -4587,12 +4982,12 @@ Usually file systems on macOS are case\-insensitive.
 It is possible to make macOS file systems case\-sensitive but that is
 not the default
 .PP
-The \[lq]\[en]vfs\-case\-insensitive\[rq] mount flag controls how rclone
+The \[dq]\-\-vfs\-case\-insensitive\[dq] mount flag controls how rclone
 handles these two cases.
-If its value is \[lq]false\[rq], rclone passes file names to the mounted
-file system as is.
-If the flag is \[lq]true\[rq] (or appears without a value on command
-line), rclone may perform a \[lq]fixup\[rq] as explained below.
+If its value is \[dq]false\[dq], rclone passes file names to the mounted
+file system as\-is.
+If the flag is \[dq]true\[dq] (or appears without a value on command
+line), rclone may perform a \[dq]fixup\[dq] as explained below.
 .PP
 The user may specify a file name to open/delete/rename/etc with a case
 different than what is stored on mounted file system.
@@ -4608,13 +5003,13 @@ an underlying mounted file system.
 Note that case sensitivity of the operating system running rclone (the
 target) may differ from case sensitivity of a file system mounted by
 rclone (the source).
-The flag controls whether \[lq]fixup\[rq] is performed to satisfy the
+The flag controls whether \[dq]fixup\[dq] is performed to satisfy the
 target.
 .PP
-If the flag is not provided on command line, then its default value
-depends on the operating system where rclone runs: \[lq]true\[rq] on
-Windows and macOS, \[lq]false\[rq] otherwise.
-If the flag is provided without a value, then it is \[lq]true\[rq].
+If the flag is not provided on the command line, then its default value
+depends on the operating system where rclone runs: \[dq]true\[dq] on
+Windows and macOS, \[dq]false\[dq] otherwise.
+If the flag is provided without a value, then it is \[dq]true\[dq].
 .SS Auth Proxy
 .PP
 If you supply the parameter \f[C]\-\-auth\-proxy /path/to/program\f[R]
@@ -4632,11 +5027,11 @@ There is an example program
 bin/test_proxy.py (https://github.com/rclone/rclone/blob/master/test_proxy.py)
 in the rclone source code.
 .PP
-The program\[cq]s job is to take a \f[C]user\f[R] and \f[C]pass\f[R] on
+The program\[aq]s job is to take a \f[C]user\f[R] and \f[C]pass\f[R] 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\[cq]t use configuration from environment variables or command
+it won\[aq]t use configuration from environment variables or command
 line options \- it is the job of the proxy program to make a complete
 config.
 .PP
@@ -4697,12 +5092,12 @@ example to make proxy to many different sftp backends, you could make
 the \f[C]user\f[R] be \f[C]user\[at]example.com\f[R] and then set the
 \f[C]host\f[R] to \f[C]example.com\f[R] in the output and the user to
 \f[C]user\f[R].
-For security you\[cq]d probably want to restrict the \f[C]host\f[R] to a
+For security you\[aq]d probably want to restrict the \f[C]host\f[R] to a
 limited list.
 .PP
 Note that an internal cache is keyed on \f[C]user\f[R] so only use that
-for configuration, don\[cq]t use \f[C]pass\f[R] or \f[C]public_key\f[R].
-This also means that if a user\[cq]s password or public\-key is changed
+for configuration, don\[aq]t use \f[C]pass\f[R] or \f[C]public_key\f[R].
+This also means that if a user\[aq]s password or public\-key is changed
 the cache will need to expire (which takes 5 mins) before it takes
 effect.
 .PP
@@ -4741,9 +5136,11 @@ rclone serve ftp remote:path [flags]
       \-\-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\-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 128M)
       \-\-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. \[aq]off\[aq] is unlimited. (default off)
       \-\-vfs\-read\-wait duration                 Time to wait for in\-sequence read before seeking. (default 20ms)
+      \-\-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)
 \f[R]
 .fi
@@ -4764,43 +5161,43 @@ HTTP.
 This can be viewed in a web browser or you can make a remote of type
 http read from it.
 .PP
-You can use the filter flags (eg \[en]include, \[en]exclude) to control
+You can use the filter flags (eg \-\-include, \-\-exclude) to control
 what is served.
 .PP
 The server will log errors.
 Use \-v to see access logs.
 .PP
-\[en]bwlimit will be respected for file transfers.
-Use \[en]stats to control the stats printing.
+\-\-bwlimit will be respected for file transfers.
+Use \-\-stats to control the stats printing.
 .SS Server options
 .PP
-Use \[en]addr to specify which IP address and port the server should
-listen on, eg \[en]addr 1.2.3.4:8000 or \[en]addr :8080 to listen to all
+Use \-\-addr to specify which IP address and port the server should
+listen on, eg \-\-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.
 .PP
-If you set \[en]addr to listen on a public or LAN accessible IP address
+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.
 .PP
-\[en]server\-read\-timeout and \[en]server\-write\-timeout can be used
-to control the timeouts on the server.
+\-\-server\-read\-timeout and \-\-server\-write\-timeout can be used to
+control the timeouts on the server.
 Note that this is the total time for a transfer.
 .PP
-\[en]max\-header\-bytes controls the maximum number of bytes the server
+\-\-max\-header\-bytes controls the maximum number of bytes the server
 will accept in the HTTP header.
 .PP
-\[en]baseurl controls the URL prefix that rclone serves from.
+\-\-baseurl controls the URL prefix that rclone serves from.
 By default rclone will serve from the root.
-If you used \[en]baseurl \[lq]/rclone\[rq] then rclone would serve from
-a URL starting with \[lq]/rclone/\[rq].
+If you used \-\-baseurl \[dq]/rclone\[dq] then rclone would serve from a
+URL starting with \[dq]/rclone/\[dq].
 This is useful if you wish to proxy rclone serve.
-Rclone automatically inserts leading and trailing \[lq]/\[rq] on
-\[en]baseurl, so \[en]baseurl \[lq]rclone\[rq], \[en]baseurl
-\[lq]/rclone\[rq] and \[en]baseurl \[lq]/rclone/\[rq] are all treated
+Rclone automatically inserts leading and trailing \[dq]/\[dq] on
+\-\-baseurl, so \-\-baseurl \[dq]rclone\[dq], \-\-baseurl
+\[dq]/rclone\[dq] and \-\-baseurl \[dq]/rclone/\[dq] are all treated
 identically.
 .PP
-\[en]template allows a user to specify a custom markup template for http
+\-\-template 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:
@@ -4855,12 +5252,12 @@ T}@T{
 Allows for creating a relative navigation
 T}
 T{
-\[en] .Link
+\-\- .Link
 T}@T{
 The relative to the root link of the Text.
 T}
 T{
-\[en] .Text
+\-\- .Text
 T}@T{
 The Name of the directory.
 T}
@@ -4870,27 +5267,28 @@ T}@T{
 Information about a specific file/directory.
 T}
 T{
-\[en] .URL
+\-\- .URL
 T}@T{
-The `url' of an entry.
+The \[aq]url\[aq] of an entry.
 T}
 T{
-\[en] .Leaf
+\-\- .Leaf
 T}@T{
-Currently same as `URL' but intended to be `just' the name.
+Currently same as \[aq]URL\[aq] but intended to be \[aq]just\[aq] the
+name.
 T}
 T{
-\[en] .IsDir
+\-\- .IsDir
 T}@T{
 Boolean for if an entry is a directory or not.
 T}
 T{
-\[en] .Size
+\-\- .Size
 T}@T{
 Size in Bytes of the entry.
 T}
 T{
-\[en] .ModTime
+\-\- .ModTime
 T}@T{
 The UTC timestamp of an entry.
 T}
@@ -4900,9 +5298,9 @@ T}
 By default this will serve files without needing a login.
 .PP
 You can either use an htpasswd file which can take lots of users, or set
-a single username and password with the \[en]user and \[en]pass flags.
+a single username and password with the \-\-user and \-\-pass flags.
 .PP
-Use \[en]htpasswd /path/to/htpasswd to provide an htpasswd file.
+Use \-\-htpasswd /path/to/htpasswd to provide an htpasswd file.
 This is in standard apache format and supports MD5, SHA1 and BCrypt for
 basic authentication.
 Bcrypt is recommended.
@@ -4919,34 +5317,57 @@ htpasswd \-B htpasswd anotherUser
 .PP
 The password file can be updated while rclone is running.
 .PP
-Use \[en]realm to set the authentication realm.
+Use \-\-realm to set the authentication realm.
 .SS SSL/TLS
 .PP
 By default this will serve over http.
 If you want you can serve over https.
-You will need to supply the \[en]cert and \[en]key flags.
+You will need to supply the \-\-cert and \-\-key flags.
 If you wish to do client side certificate validation then you will need
-to supply \[en]client\-ca also.
+to supply \-\-client\-ca also.
 .PP
-\[en]cert should be either a PEM encoded certificate or a concatenation
+\-\-cert should be either a PEM encoded certificate or a concatenation
 of that with the CA certificate.
-\[en]key should be the PEM encoded private key and \[en]client\-ca
-should be the PEM encoded client certificate authority certificate.
-.SS Directory Cache
+\-\-key should be the PEM encoded private key and \-\-client\-ca should
+be the PEM encoded client certificate authority certificate.
+.SS VFS \- Virtual File System
 .PP
-Using the \f[C]\-\-dir\-cache\-time\f[R] flag, you can set how long a
-directory should be considered up to date and not refreshed from the
+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.
+.PP
+Cloud storage objects have lots of properties which aren\[aq]t like disk
+files \- you can\[aq]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.
+.PP
+The VFS layer also implements a directory cache \- this caches info
+about files and directories (but not the data) in memory.
+.SS VFS Directory Cache
+.PP
+Using the \f[C]\-\-dir\-cache\-time\f[R] flag, you can control how long
+a directory should be considered up to date and not refreshed from the
 backend.
-Changes made locally in the mount may appear immediately or invalidate
-the cache.
-However, changes done on the remote will only be picked up once the
+Changes made through the mount will appear immediately or invalidate the
+cache.
+.IP
+.nf
+\f[C]
+\-\-dir\-cache\-time duration   Time to cache directory entries for. (default 5m0s)
+\-\-poll\-interval duration    Time to wait between polling for changes.
+\f[R]
+.fi
+.PP
+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 on within the
+If the backend supports polling, changes will be picked up within the
 polling interval.
 .PP
-Alternatively, you can send a \f[C]SIGHUP\f[R] signal to rclone for it
-to flush all directory caches, regardless of how old they are.
+You can send a \f[C]SIGHUP\f[R] 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:
 .IP
@@ -4972,42 +5393,44 @@ Or individual files or directories:
 rclone rc vfs/forget file=path/to/file dir=path/to/dir
 \f[R]
 .fi
-.SS File Buffering
+.SS VFS File Buffering
 .PP
 The \f[C]\-\-buffer\-size\f[R] flag determines the amount of memory,
 that will be used to buffer data in advance.
 .PP
-Each open file descriptor will try to keep the specified amount of data
-in memory at all times.
-The buffered data is bound to one file descriptor and won\[cq]t be
-shared between multiple open file descriptors of the same file.
+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\[aq]t be shared.
 .PP
-This flag is a upper limit for the used memory per file descriptor.
+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.
+.PP
 The maximum memory used by rclone for buffering can be up to
 \f[C]\-\-buffer\-size * open files\f[R].
-.SS File Caching
+.SS VFS File Caching
 .PP
 These flags control the VFS file caching options.
-The VFS layer is used by rclone mount to make a cloud storage system
-work more like a normal file system.
+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.
 .PP
-You\[cq]ll need to enable VFS caching if you want, for example, to read
+For example you\[aq]ll need to enable VFS caching if you want to read
 and write simultaneously to a file.
 See below for more details.
 .PP
-Note that the VFS cache works in addition to the cache backend and you
-may find that you need one or the other or both.
+Note that the VFS cache is separate from the cache backend and you may
+find that you need one or the other or both.
 .IP
 .nf
 \f[C]
 \-\-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 age of objects in the cache. (default 1h0m0s)
-\-\-vfs\-cache\-mode string              Cache mode off|minimal|writes|full (default \[dq]off\[dq])
+\-\-vfs\-cache\-max\-size SizeSuffix      Max total size of objects in the cache. (default off)
 \-\-vfs\-cache\-poll\-interval duration   Interval to poll the cache for stale objects. (default 1m0s)
-\-\-vfs\-cache\-max\-size int             Max total size of objects in the cache. (default off)
+\-\-vfs\-write\-back duration            Time to writeback files after last use when using cache. (default 5s)
 \f[R]
 .fi
 .PP
@@ -5023,25 +5446,24 @@ The higher the cache mode the more compatible rclone becomes at the cost
 of using disk space.
 .PP
 Note that files are written back to the remote only when they are closed
-so if rclone is quit or dies with open files then these won\[cq]t get
-written back to the remote.
-However they will still be in the on disk cache.
+and if they haven\[aq]t been accessed for \-\-vfs\-write\-back second.
+If rclone is quit or dies with files that haven\[aq]t been uploaded,
+these will be uploaded next time rclone is run with the same flags.
 .PP
-If using \[en]vfs\-cache\-max\-size note that the cache may exceed this
+If using \-\-vfs\-cache\-max\-size note that the cache may exceed this
 size for two reasons.
-Firstly because it is only checked every
-\[en]vfs\-cache\-poll\-interval.
+Firstly because it is only checked every \-\-vfs\-cache\-poll\-interval.
 Secondly because open files cannot be evicted from the cache.
-.SS \[en]vfs\-cache\-mode off
+.SS \-\-vfs\-cache\-mode off
 .PP
-In this mode the cache will read directly from the remote and write
-directly to the remote without caching anything on disk.
+In this mode (the default) the cache will read directly from the remote
+and write directly to the remote without caching anything on disk.
 .PP
 This will mean some operations are not possible
 .IP \[bu] 2
-Files can\[cq]t be opened for both read AND write
+Files can\[aq]t be opened for both read AND write
 .IP \[bu] 2
-Files opened for write can\[cq]t be seeked
+Files opened for write can\[aq]t be seeked
 .IP \[bu] 2
 Existing files opened for write must have O_TRUNC set
 .IP \[bu] 2
@@ -5051,57 +5473,108 @@ Files open for write only will behave as if O_TRUNC was supplied
 .IP \[bu] 2
 Open modes O_APPEND, O_TRUNC are ignored
 .IP \[bu] 2
-If an upload fails it can\[cq]t be retried
-.SS \[en]vfs\-cache\-mode minimal
+If an upload fails it can\[aq]t be retried
+.SS \-\-vfs\-cache\-mode minimal
 .PP
-This is very similar to \[lq]off\[rq] except that files opened for read
-AND write will be buffered to disks.
+This is very similar to \[dq]off\[dq] 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.
 .PP
 These operations are not possible
 .IP \[bu] 2
-Files opened for write only can\[cq]t be seeked
+Files opened for write only can\[aq]t be seeked
 .IP \[bu] 2
 Existing files opened for write must have O_TRUNC set
 .IP \[bu] 2
 Files opened for write only will ignore O_APPEND, O_TRUNC
 .IP \[bu] 2
-If an upload fails it can\[cq]t be retried
-.SS \[en]vfs\-cache\-mode writes
+If an upload fails it can\[aq]t be retried
+.SS \-\-vfs\-cache\-mode writes
 .PP
 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.
 .PP
 This mode should support all normal file system operations.
 .PP
-If an upload fails it will be retried up to \[en]low\-level\-retries
-times.
-.SS \[en]vfs\-cache\-mode full
+If an upload fails it will be retried at exponentially increasing
+intervals up to 1 minute.
+.SS \-\-vfs\-cache\-mode full
 .PP
 In this mode all reads and writes are buffered to and from disk.
-When a file is opened for read it will be downloaded in its entirety
-first.
+When data is read from the remote this is buffered to disk as well.
 .PP
-This may be appropriate for your needs, or you may prefer to look at the
-cache backend which does a much more sophisticated job of caching,
-including caching directory hierarchies and chunks of files.
+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 dowloaded.
 .PP
-In this mode, unlike the others, when a file is written to the disk, it
-will be kept on the disk after it is written to the remote.
-It will be purged on a schedule according to
-\f[C]\-\-vfs\-cache\-max\-age\f[R].
+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.
 .PP
-This mode should support all normal file system operations.
+This mode should support all normal file system operations and is
+otherwise identical to \-\-vfs\-cache\-mode writes.
 .PP
-If an upload or download fails it will be retried up to
-\[en]low\-level\-retries times.
-.SS Case Sensitivity
+When reading a file rclone will read \-\-buffer\-size plus
+\-\-vfs\-read\-ahead bytes ahead.
+The \-\-buffer\-size is buffered in memory whereas the
+\-\-vfs\-read\-ahead is buffered on disk.
+.PP
+When using this mode it is recommended that \-\-buffer\-size is not set
+too big and \-\-vfs\-read\-ahead is set large if required.
+.SS VFS Performance
+.PP
+These flags may be used to enable/disable features of the VFS for
+performance or other reasons.
+.PP
+In particular S3 and Swift benefit hugely from the \-\-no\-modtime flag
+(or use \-\-use\-server\-modtime for a slightly different effect) as
+each read of the modification time takes a transaction.
+.IP
+.nf
+\f[C]
+\-\-no\-checksum     Don\[aq]t compare checksums on up/download.
+\-\-no\-modtime      Don\[aq]t read/write the modification time (can speed things up).
+\-\-no\-seek         Don\[aq]t allow seeking in files.
+\-\-read\-only       Mount read\-only.
+\f[R]
+.fi
+.PP
+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 is advantageous because some cloud providers account for reads
+being all the data requested, not all the data delivered.
+.PP
+Rclone will keep doubling the chunk size requested starting at
+\-\-vfs\-read\-chunk\-size with a maximum of
+\-\-vfs\-read\-chunk\-size\-limit unless it is set to \[dq]off\[dq] in
+which case there will be no limit.
+.IP
+.nf
+\f[C]
+\-\-vfs\-read\-chunk\-size SizeSuffix        Read the source objects in chunks. (default 128M)
+\-\-vfs\-read\-chunk\-size\-limit SizeSuffix  Max chunk doubling size (default \[dq]off\[dq])
+\f[R]
+.fi
+.PP
+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.
+.IP
+.nf
+\f[C]
+\-\-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)
+\f[R]
+.fi
+.SS VFS Case Sensitivity
 .PP
 Linux file systems are case\-sensitive: two files can differ only by
 case, and the exact case must be used when opening a file.
 .PP
-Windows is not like most other operating systems supported by rclone.
 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
@@ -5113,12 +5586,12 @@ Usually file systems on macOS are case\-insensitive.
 It is possible to make macOS file systems case\-sensitive but that is
 not the default
 .PP
-The \[lq]\[en]vfs\-case\-insensitive\[rq] mount flag controls how rclone
+The \[dq]\-\-vfs\-case\-insensitive\[dq] mount flag controls how rclone
 handles these two cases.
-If its value is \[lq]false\[rq], rclone passes file names to the mounted
-file system as is.
-If the flag is \[lq]true\[rq] (or appears without a value on command
-line), rclone may perform a \[lq]fixup\[rq] as explained below.
+If its value is \[dq]false\[dq], rclone passes file names to the mounted
+file system as\-is.
+If the flag is \[dq]true\[dq] (or appears without a value on command
+line), rclone may perform a \[dq]fixup\[dq] as explained below.
 .PP
 The user may specify a file name to open/delete/rename/etc with a case
 different than what is stored on mounted file system.
@@ -5134,13 +5607,13 @@ an underlying mounted file system.
 Note that case sensitivity of the operating system running rclone (the
 target) may differ from case sensitivity of a file system mounted by
 rclone (the source).
-The flag controls whether \[lq]fixup\[rq] is performed to satisfy the
+The flag controls whether \[dq]fixup\[dq] is performed to satisfy the
 target.
 .PP
-If the flag is not provided on command line, then its default value
-depends on the operating system where rclone runs: \[lq]true\[rq] on
-Windows and macOS, \[lq]false\[rq] otherwise.
-If the flag is provided without a value, then it is \[lq]true\[rq].
+If the flag is not provided on the command line, then its default value
+depends on the operating system where rclone runs: \[dq]true\[dq] on
+Windows and macOS, \[dq]false\[dq] otherwise.
+If the flag is provided without a value, then it is \[dq]true\[dq].
 .IP
 .nf
 \f[C]
@@ -5181,9 +5654,11 @@ rclone serve http remote:path [flags]
       \-\-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\-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 128M)
       \-\-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. \[aq]off\[aq] is unlimited. (default off)
       \-\-vfs\-read\-wait duration                 Time to wait for in\-sequence read before seeking. (default 20ms)
+      \-\-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)
 \f[R]
 .fi
@@ -5196,10 +5671,10 @@ rclone serve (https://rclone.org/commands/rclone_serve/) \- Serve a
 remote over a protocol.
 .SH rclone serve restic
 .PP
-Serve the remote for restic\[cq]s REST API.
+Serve the remote for restic\[aq]s REST API.
 .SS Synopsis
 .PP
-rclone serve restic implements restic\[cq]s REST backend API over HTTP.
+rclone serve restic implements restic\[aq]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.
 .PP
@@ -5209,16 +5684,16 @@ backups.
 The server will log errors.
 Use \-v to see access logs.
 .PP
-\[en]bwlimit will be respected for file transfers.
-Use \[en]stats to control the stats printing.
+\-\-bwlimit will be respected for file transfers.
+Use \-\-stats to control the stats printing.
 .SS Setting up rclone for use by restic
 .PP
 First set up a remote for your chosen cloud
 provider (https://rclone.org/docs/#configure).
 .PP
 Once you have set up the remote, check it is working with, for example
-\[lq]rclone lsd remote:\[rq].
-You may have called the remote something other than \[lq]remote:\[rq] \-
+\[dq]rclone lsd remote:\[dq].
+You may have called the remote something other than \[dq]remote:\[dq] \-
 just substitute whatever you called it in the following instructions.
 .PP
 Now start the rclone restic server
@@ -5229,11 +5704,11 @@ rclone serve restic \-v remote:backup
 \f[R]
 .fi
 .PP
-Where you can replace \[lq]backup\[rq] in the above by whatever path in
+Where you can replace \[dq]backup\[dq] in the above by whatever path in
 the remote you wish to use.
 .PP
-By default this will serve on \[lq]localhost:8080\[rq] you can change
-this with use of the \[lq]\[en]addr\[rq] flag.
+By default this will serve on \[dq]localhost:8080\[dq] you can change
+this with use of the \[dq]\-\-addr\[dq] flag.
 .PP
 You might wish to start this server on boot.
 .SS Setting up restic to use rclone
@@ -5246,7 +5721,7 @@ Note that you will need restic 0.8.2 or later to interoperate with
 rclone.
 .PP
 For the example above you will want to use
-\[lq]http://localhost:8080/\[rq] as the URL for the REST server.
+\[dq]http://localhost:8080/\[dq] as the URL for the REST server.
 .PP
 For example:
 .IP
@@ -5285,37 +5760,37 @@ $ export RESTIC_REPOSITORY=rest:http://localhost:8080/user2repo/
 .fi
 .SS Private repositories
 .PP
-The \[lq]\[en]private\-repos\[rq] flag can be used to limit users to
+The \[dq]\-\-private\-repos\[dq] flag can be used to limit users to
 repositories starting with a path of \f[C]/<username>/\f[R].
 .SS Server options
 .PP
-Use \[en]addr to specify which IP address and port the server should
-listen on, eg \[en]addr 1.2.3.4:8000 or \[en]addr :8080 to listen to all
+Use \-\-addr to specify which IP address and port the server should
+listen on, eg \-\-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.
 .PP
-If you set \[en]addr to listen on a public or LAN accessible IP address
+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.
 .PP
-\[en]server\-read\-timeout and \[en]server\-write\-timeout can be used
-to control the timeouts on the server.
+\-\-server\-read\-timeout and \-\-server\-write\-timeout can be used to
+control the timeouts on the server.
 Note that this is the total time for a transfer.
 .PP
-\[en]max\-header\-bytes controls the maximum number of bytes the server
+\-\-max\-header\-bytes controls the maximum number of bytes the server
 will accept in the HTTP header.
 .PP
-\[en]baseurl controls the URL prefix that rclone serves from.
+\-\-baseurl controls the URL prefix that rclone serves from.
 By default rclone will serve from the root.
-If you used \[en]baseurl \[lq]/rclone\[rq] then rclone would serve from
-a URL starting with \[lq]/rclone/\[rq].
+If you used \-\-baseurl \[dq]/rclone\[dq] then rclone would serve from a
+URL starting with \[dq]/rclone/\[dq].
 This is useful if you wish to proxy rclone serve.
-Rclone automatically inserts leading and trailing \[lq]/\[rq] on
-\[en]baseurl, so \[en]baseurl \[lq]rclone\[rq], \[en]baseurl
-\[lq]/rclone\[rq] and \[en]baseurl \[lq]/rclone/\[rq] are all treated
+Rclone automatically inserts leading and trailing \[dq]/\[dq] on
+\-\-baseurl, so \-\-baseurl \[dq]rclone\[dq], \-\-baseurl
+\[dq]/rclone\[dq] and \-\-baseurl \[dq]/rclone/\[dq] are all treated
 identically.
 .PP
-\[en]template allows a user to specify a custom markup template for http
+\-\-template 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:
@@ -5370,12 +5845,12 @@ T}@T{
 Allows for creating a relative navigation
 T}
 T{
-\[en] .Link
+\-\- .Link
 T}@T{
 The relative to the root link of the Text.
 T}
 T{
-\[en] .Text
+\-\- .Text
 T}@T{
 The Name of the directory.
 T}
@@ -5385,27 +5860,28 @@ T}@T{
 Information about a specific file/directory.
 T}
 T{
-\[en] .URL
+\-\- .URL
 T}@T{
-The `url' of an entry.
+The \[aq]url\[aq] of an entry.
 T}
 T{
-\[en] .Leaf
+\-\- .Leaf
 T}@T{
-Currently same as `URL' but intended to be `just' the name.
+Currently same as \[aq]URL\[aq] but intended to be \[aq]just\[aq] the
+name.
 T}
 T{
-\[en] .IsDir
+\-\- .IsDir
 T}@T{
 Boolean for if an entry is a directory or not.
 T}
 T{
-\[en] .Size
+\-\- .Size
 T}@T{
 Size in Bytes of the entry.
 T}
 T{
-\[en] .ModTime
+\-\- .ModTime
 T}@T{
 The UTC timestamp of an entry.
 T}
@@ -5415,9 +5891,9 @@ T}
 By default this will serve files without needing a login.
 .PP
 You can either use an htpasswd file which can take lots of users, or set
-a single username and password with the \[en]user and \[en]pass flags.
+a single username and password with the \-\-user and \-\-pass flags.
 .PP
-Use \[en]htpasswd /path/to/htpasswd to provide an htpasswd file.
+Use \-\-htpasswd /path/to/htpasswd to provide an htpasswd file.
 This is in standard apache format and supports MD5, SHA1 and BCrypt for
 basic authentication.
 Bcrypt is recommended.
@@ -5434,19 +5910,19 @@ htpasswd \-B htpasswd anotherUser
 .PP
 The password file can be updated while rclone is running.
 .PP
-Use \[en]realm to set the authentication realm.
+Use \-\-realm to set the authentication realm.
 .SS SSL/TLS
 .PP
 By default this will serve over http.
 If you want you can serve over https.
-You will need to supply the \[en]cert and \[en]key flags.
+You will need to supply the \-\-cert and \-\-key flags.
 If you wish to do client side certificate validation then you will need
-to supply \[en]client\-ca also.
+to supply \-\-client\-ca also.
 .PP
-\[en]cert should be either a PEM encoded certificate or a concatenation
+\-\-cert should be either a PEM encoded certificate or a concatenation
 of that with the CA certificate.
-\[en]key should be the PEM encoded private key and \[en]client\-ca
-should be the PEM encoded client certificate authority certificate.
+\-\-key should be the PEM encoded private key and \-\-client\-ca should
+be the PEM encoded client certificate authority certificate.
 .IP
 .nf
 \f[C]
@@ -5493,20 +5969,20 @@ SFTP.
 This can be used with an SFTP client or you can make a remote of type
 sftp to use with it.
 .PP
-You can use the filter flags (eg \[en]include, \[en]exclude) to control
+You can use the filter flags (eg \-\-include, \-\-exclude) to control
 what is served.
 .PP
 The server will log errors.
 Use \-v to see access logs.
 .PP
-\[en]bwlimit will be respected for file transfers.
-Use \[en]stats to control the stats printing.
+\-\-bwlimit will be respected for file transfers.
+Use \-\-stats to control the stats printing.
 .PP
 You must provide some means of authentication, either with
-\[en]user/\[en]pass, an authorized keys file (specify location with
-\[en]authorized\-keys \- the default is the same as ssh), an
-\[en]auth\-proxy, or set the \[en]no\-auth flag for no authentication
-when logging in.
+\-\-user/\-\-pass, an authorized keys file (specify location with
+\-\-authorized\-keys \- the default is the same as ssh), an
+\-\-auth\-proxy, or set the \-\-no\-auth flag for no authentication when
+logging in.
 .PP
 Note that this also implements a small number of shell commands so that
 it can provide md5sum/sha1sum/df information for the rclone sftp
@@ -5514,29 +5990,52 @@ backend.
 This means that is can support SHA1SUMs, MD5SUMs and the about command
 when paired with the rclone sftp backend.
 .PP
-If you don\[cq]t supply a \[en]key then rclone will generate one and
+If you don\[aq]t supply a \-\-key then rclone will generate one and
 cache it for later use.
 .PP
 By default the server binds to localhost:2022 \- if you want it to be
-reachable externally then supply \[lq]\[en]addr :2022\[rq] for example.
+reachable externally then supply \[dq]\-\-addr :2022\[dq] for example.
 .PP
-Note that the default of \[lq]\[en]vfs\-cache\-mode off\[rq] is fine for
+Note that the default of \[dq]\-\-vfs\-cache\-mode off\[dq] is fine for
 the rclone sftp backend, but it may not be with other SFTP clients.
-.SS Directory Cache
+.SS VFS \- Virtual File System
 .PP
-Using the \f[C]\-\-dir\-cache\-time\f[R] flag, you can set how long a
-directory should be considered up to date and not refreshed from the
+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.
+.PP
+Cloud storage objects have lots of properties which aren\[aq]t like disk
+files \- you can\[aq]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.
+.PP
+The VFS layer also implements a directory cache \- this caches info
+about files and directories (but not the data) in memory.
+.SS VFS Directory Cache
+.PP
+Using the \f[C]\-\-dir\-cache\-time\f[R] flag, you can control how long
+a directory should be considered up to date and not refreshed from the
 backend.
-Changes made locally in the mount may appear immediately or invalidate
-the cache.
-However, changes done on the remote will only be picked up once the
+Changes made through the mount will appear immediately or invalidate the
+cache.
+.IP
+.nf
+\f[C]
+\-\-dir\-cache\-time duration   Time to cache directory entries for. (default 5m0s)
+\-\-poll\-interval duration    Time to wait between polling for changes.
+\f[R]
+.fi
+.PP
+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 on within the
+If the backend supports polling, changes will be picked up within the
 polling interval.
 .PP
-Alternatively, you can send a \f[C]SIGHUP\f[R] signal to rclone for it
-to flush all directory caches, regardless of how old they are.
+You can send a \f[C]SIGHUP\f[R] 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:
 .IP
@@ -5562,42 +6061,44 @@ Or individual files or directories:
 rclone rc vfs/forget file=path/to/file dir=path/to/dir
 \f[R]
 .fi
-.SS File Buffering
+.SS VFS File Buffering
 .PP
 The \f[C]\-\-buffer\-size\f[R] flag determines the amount of memory,
 that will be used to buffer data in advance.
 .PP
-Each open file descriptor will try to keep the specified amount of data
-in memory at all times.
-The buffered data is bound to one file descriptor and won\[cq]t be
-shared between multiple open file descriptors of the same file.
+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\[aq]t be shared.
 .PP
-This flag is a upper limit for the used memory per file descriptor.
+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.
+.PP
 The maximum memory used by rclone for buffering can be up to
 \f[C]\-\-buffer\-size * open files\f[R].
-.SS File Caching
+.SS VFS File Caching
 .PP
 These flags control the VFS file caching options.
-The VFS layer is used by rclone mount to make a cloud storage system
-work more like a normal file system.
+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.
 .PP
-You\[cq]ll need to enable VFS caching if you want, for example, to read
+For example you\[aq]ll need to enable VFS caching if you want to read
 and write simultaneously to a file.
 See below for more details.
 .PP
-Note that the VFS cache works in addition to the cache backend and you
-may find that you need one or the other or both.
+Note that the VFS cache is separate from the cache backend and you may
+find that you need one or the other or both.
 .IP
 .nf
 \f[C]
 \-\-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 age of objects in the cache. (default 1h0m0s)
-\-\-vfs\-cache\-mode string              Cache mode off|minimal|writes|full (default \[dq]off\[dq])
+\-\-vfs\-cache\-max\-size SizeSuffix      Max total size of objects in the cache. (default off)
 \-\-vfs\-cache\-poll\-interval duration   Interval to poll the cache for stale objects. (default 1m0s)
-\-\-vfs\-cache\-max\-size int             Max total size of objects in the cache. (default off)
+\-\-vfs\-write\-back duration            Time to writeback files after last use when using cache. (default 5s)
 \f[R]
 .fi
 .PP
@@ -5613,25 +6114,24 @@ The higher the cache mode the more compatible rclone becomes at the cost
 of using disk space.
 .PP
 Note that files are written back to the remote only when they are closed
-so if rclone is quit or dies with open files then these won\[cq]t get
-written back to the remote.
-However they will still be in the on disk cache.
+and if they haven\[aq]t been accessed for \-\-vfs\-write\-back second.
+If rclone is quit or dies with files that haven\[aq]t been uploaded,
+these will be uploaded next time rclone is run with the same flags.
 .PP
-If using \[en]vfs\-cache\-max\-size note that the cache may exceed this
+If using \-\-vfs\-cache\-max\-size note that the cache may exceed this
 size for two reasons.
-Firstly because it is only checked every
-\[en]vfs\-cache\-poll\-interval.
+Firstly because it is only checked every \-\-vfs\-cache\-poll\-interval.
 Secondly because open files cannot be evicted from the cache.
-.SS \[en]vfs\-cache\-mode off
+.SS \-\-vfs\-cache\-mode off
 .PP
-In this mode the cache will read directly from the remote and write
-directly to the remote without caching anything on disk.
+In this mode (the default) the cache will read directly from the remote
+and write directly to the remote without caching anything on disk.
 .PP
 This will mean some operations are not possible
 .IP \[bu] 2
-Files can\[cq]t be opened for both read AND write
+Files can\[aq]t be opened for both read AND write
 .IP \[bu] 2
-Files opened for write can\[cq]t be seeked
+Files opened for write can\[aq]t be seeked
 .IP \[bu] 2
 Existing files opened for write must have O_TRUNC set
 .IP \[bu] 2
@@ -5641,57 +6141,108 @@ Files open for write only will behave as if O_TRUNC was supplied
 .IP \[bu] 2
 Open modes O_APPEND, O_TRUNC are ignored
 .IP \[bu] 2
-If an upload fails it can\[cq]t be retried
-.SS \[en]vfs\-cache\-mode minimal
+If an upload fails it can\[aq]t be retried
+.SS \-\-vfs\-cache\-mode minimal
 .PP
-This is very similar to \[lq]off\[rq] except that files opened for read
-AND write will be buffered to disks.
+This is very similar to \[dq]off\[dq] 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.
 .PP
 These operations are not possible
 .IP \[bu] 2
-Files opened for write only can\[cq]t be seeked
+Files opened for write only can\[aq]t be seeked
 .IP \[bu] 2
 Existing files opened for write must have O_TRUNC set
 .IP \[bu] 2
 Files opened for write only will ignore O_APPEND, O_TRUNC
 .IP \[bu] 2
-If an upload fails it can\[cq]t be retried
-.SS \[en]vfs\-cache\-mode writes
+If an upload fails it can\[aq]t be retried
+.SS \-\-vfs\-cache\-mode writes
 .PP
 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.
 .PP
 This mode should support all normal file system operations.
 .PP
-If an upload fails it will be retried up to \[en]low\-level\-retries
-times.
-.SS \[en]vfs\-cache\-mode full
+If an upload fails it will be retried at exponentially increasing
+intervals up to 1 minute.
+.SS \-\-vfs\-cache\-mode full
 .PP
 In this mode all reads and writes are buffered to and from disk.
-When a file is opened for read it will be downloaded in its entirety
-first.
+When data is read from the remote this is buffered to disk as well.
 .PP
-This may be appropriate for your needs, or you may prefer to look at the
-cache backend which does a much more sophisticated job of caching,
-including caching directory hierarchies and chunks of files.
+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 dowloaded.
 .PP
-In this mode, unlike the others, when a file is written to the disk, it
-will be kept on the disk after it is written to the remote.
-It will be purged on a schedule according to
-\f[C]\-\-vfs\-cache\-max\-age\f[R].
+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.
 .PP
-This mode should support all normal file system operations.
+This mode should support all normal file system operations and is
+otherwise identical to \-\-vfs\-cache\-mode writes.
 .PP
-If an upload or download fails it will be retried up to
-\[en]low\-level\-retries times.
-.SS Case Sensitivity
+When reading a file rclone will read \-\-buffer\-size plus
+\-\-vfs\-read\-ahead bytes ahead.
+The \-\-buffer\-size is buffered in memory whereas the
+\-\-vfs\-read\-ahead is buffered on disk.
+.PP
+When using this mode it is recommended that \-\-buffer\-size is not set
+too big and \-\-vfs\-read\-ahead is set large if required.
+.SS VFS Performance
+.PP
+These flags may be used to enable/disable features of the VFS for
+performance or other reasons.
+.PP
+In particular S3 and Swift benefit hugely from the \-\-no\-modtime flag
+(or use \-\-use\-server\-modtime for a slightly different effect) as
+each read of the modification time takes a transaction.
+.IP
+.nf
+\f[C]
+\-\-no\-checksum     Don\[aq]t compare checksums on up/download.
+\-\-no\-modtime      Don\[aq]t read/write the modification time (can speed things up).
+\-\-no\-seek         Don\[aq]t allow seeking in files.
+\-\-read\-only       Mount read\-only.
+\f[R]
+.fi
+.PP
+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 is advantageous because some cloud providers account for reads
+being all the data requested, not all the data delivered.
+.PP
+Rclone will keep doubling the chunk size requested starting at
+\-\-vfs\-read\-chunk\-size with a maximum of
+\-\-vfs\-read\-chunk\-size\-limit unless it is set to \[dq]off\[dq] in
+which case there will be no limit.
+.IP
+.nf
+\f[C]
+\-\-vfs\-read\-chunk\-size SizeSuffix        Read the source objects in chunks. (default 128M)
+\-\-vfs\-read\-chunk\-size\-limit SizeSuffix  Max chunk doubling size (default \[dq]off\[dq])
+\f[R]
+.fi
+.PP
+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.
+.IP
+.nf
+\f[C]
+\-\-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)
+\f[R]
+.fi
+.SS VFS Case Sensitivity
 .PP
 Linux file systems are case\-sensitive: two files can differ only by
 case, and the exact case must be used when opening a file.
 .PP
-Windows is not like most other operating systems supported by rclone.
 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
@@ -5703,12 +6254,12 @@ Usually file systems on macOS are case\-insensitive.
 It is possible to make macOS file systems case\-sensitive but that is
 not the default
 .PP
-The \[lq]\[en]vfs\-case\-insensitive\[rq] mount flag controls how rclone
+The \[dq]\-\-vfs\-case\-insensitive\[dq] mount flag controls how rclone
 handles these two cases.
-If its value is \[lq]false\[rq], rclone passes file names to the mounted
-file system as is.
-If the flag is \[lq]true\[rq] (or appears without a value on command
-line), rclone may perform a \[lq]fixup\[rq] as explained below.
+If its value is \[dq]false\[dq], rclone passes file names to the mounted
+file system as\-is.
+If the flag is \[dq]true\[dq] (or appears without a value on command
+line), rclone may perform a \[dq]fixup\[dq] as explained below.
 .PP
 The user may specify a file name to open/delete/rename/etc with a case
 different than what is stored on mounted file system.
@@ -5724,13 +6275,13 @@ an underlying mounted file system.
 Note that case sensitivity of the operating system running rclone (the
 target) may differ from case sensitivity of a file system mounted by
 rclone (the source).
-The flag controls whether \[lq]fixup\[rq] is performed to satisfy the
+The flag controls whether \[dq]fixup\[dq] is performed to satisfy the
 target.
 .PP
-If the flag is not provided on command line, then its default value
-depends on the operating system where rclone runs: \[lq]true\[rq] on
-Windows and macOS, \[lq]false\[rq] otherwise.
-If the flag is provided without a value, then it is \[lq]true\[rq].
+If the flag is not provided on the command line, then its default value
+depends on the operating system where rclone runs: \[dq]true\[dq] on
+Windows and macOS, \[dq]false\[dq] otherwise.
+If the flag is provided without a value, then it is \[dq]true\[dq].
 .SS Auth Proxy
 .PP
 If you supply the parameter \f[C]\-\-auth\-proxy /path/to/program\f[R]
@@ -5748,11 +6299,11 @@ There is an example program
 bin/test_proxy.py (https://github.com/rclone/rclone/blob/master/test_proxy.py)
 in the rclone source code.
 .PP
-The program\[cq]s job is to take a \f[C]user\f[R] and \f[C]pass\f[R] on
+The program\[aq]s job is to take a \f[C]user\f[R] and \f[C]pass\f[R] 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\[cq]t use configuration from environment variables or command
+it won\[aq]t use configuration from environment variables or command
 line options \- it is the job of the proxy program to make a complete
 config.
 .PP
@@ -5813,12 +6364,12 @@ example to make proxy to many different sftp backends, you could make
 the \f[C]user\f[R] be \f[C]user\[at]example.com\f[R] and then set the
 \f[C]host\f[R] to \f[C]example.com\f[R] in the output and the user to
 \f[C]user\f[R].
-For security you\[cq]d probably want to restrict the \f[C]host\f[R] to a
+For security you\[aq]d probably want to restrict the \f[C]host\f[R] to a
 limited list.
 .PP
 Note that an internal cache is keyed on \f[C]user\f[R] so only use that
-for configuration, don\[cq]t use \f[C]pass\f[R] or \f[C]public_key\f[R].
-This also means that if a user\[cq]s password or public\-key is changed
+for configuration, don\[aq]t use \f[C]pass\f[R] or \f[C]public_key\f[R].
+This also means that if a user\[aq]s password or public\-key is changed
 the cache will need to expire (which takes 5 mins) before it takes
 effect.
 .PP
@@ -5858,9 +6409,11 @@ rclone serve sftp remote:path [flags]
       \-\-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\-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 128M)
       \-\-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. \[aq]off\[aq] is unlimited. (default off)
       \-\-vfs\-read\-wait duration                 Time to wait for in\-sequence read before seeking. (default 20ms)
+      \-\-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)
 \f[R]
 .fi
@@ -5881,46 +6434,46 @@ 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.
 .SS Webdav options
-.SS \[en]etag\-hash
+.SS \-\-etag\-hash
 .PP
 This controls the ETag header.
 Without this flag the ETag will be based on the ModTime and Size of the
 object.
 .PP
-If this flag is set to \[lq]auto\[rq] then rclone will choose the first
+If this flag is set to \[dq]auto\[dq] then rclone will choose the first
 supported hash on the backend or you can use a named hash such as
-\[lq]MD5\[rq] or \[lq]SHA\-1\[rq].
+\[dq]MD5\[dq] or \[dq]SHA\-1\[dq].
 .PP
-Use \[lq]rclone hashsum\[rq] to see the full list.
+Use \[dq]rclone hashsum\[dq] to see the full list.
 .SS Server options
 .PP
-Use \[en]addr to specify which IP address and port the server should
-listen on, eg \[en]addr 1.2.3.4:8000 or \[en]addr :8080 to listen to all
+Use \-\-addr to specify which IP address and port the server should
+listen on, eg \-\-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.
 .PP
-If you set \[en]addr to listen on a public or LAN accessible IP address
+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.
 .PP
-\[en]server\-read\-timeout and \[en]server\-write\-timeout can be used
-to control the timeouts on the server.
+\-\-server\-read\-timeout and \-\-server\-write\-timeout can be used to
+control the timeouts on the server.
 Note that this is the total time for a transfer.
 .PP
-\[en]max\-header\-bytes controls the maximum number of bytes the server
+\-\-max\-header\-bytes controls the maximum number of bytes the server
 will accept in the HTTP header.
 .PP
-\[en]baseurl controls the URL prefix that rclone serves from.
+\-\-baseurl controls the URL prefix that rclone serves from.
 By default rclone will serve from the root.
-If you used \[en]baseurl \[lq]/rclone\[rq] then rclone would serve from
-a URL starting with \[lq]/rclone/\[rq].
+If you used \-\-baseurl \[dq]/rclone\[dq] then rclone would serve from a
+URL starting with \[dq]/rclone/\[dq].
 This is useful if you wish to proxy rclone serve.
-Rclone automatically inserts leading and trailing \[lq]/\[rq] on
-\[en]baseurl, so \[en]baseurl \[lq]rclone\[rq], \[en]baseurl
-\[lq]/rclone\[rq] and \[en]baseurl \[lq]/rclone/\[rq] are all treated
+Rclone automatically inserts leading and trailing \[dq]/\[dq] on
+\-\-baseurl, so \-\-baseurl \[dq]rclone\[dq], \-\-baseurl
+\[dq]/rclone\[dq] and \-\-baseurl \[dq]/rclone/\[dq] are all treated
 identically.
 .PP
-\[en]template allows a user to specify a custom markup template for http
+\-\-template 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:
@@ -5975,12 +6528,12 @@ T}@T{
 Allows for creating a relative navigation
 T}
 T{
-\[en] .Link
+\-\- .Link
 T}@T{
 The relative to the root link of the Text.
 T}
 T{
-\[en] .Text
+\-\- .Text
 T}@T{
 The Name of the directory.
 T}
@@ -5990,27 +6543,28 @@ T}@T{
 Information about a specific file/directory.
 T}
 T{
-\[en] .URL
+\-\- .URL
 T}@T{
-The `url' of an entry.
+The \[aq]url\[aq] of an entry.
 T}
 T{
-\[en] .Leaf
+\-\- .Leaf
 T}@T{
-Currently same as `URL' but intended to be `just' the name.
+Currently same as \[aq]URL\[aq] but intended to be \[aq]just\[aq] the
+name.
 T}
 T{
-\[en] .IsDir
+\-\- .IsDir
 T}@T{
 Boolean for if an entry is a directory or not.
 T}
 T{
-\[en] .Size
+\-\- .Size
 T}@T{
 Size in Bytes of the entry.
 T}
 T{
-\[en] .ModTime
+\-\- .ModTime
 T}@T{
 The UTC timestamp of an entry.
 T}
@@ -6020,9 +6574,9 @@ T}
 By default this will serve files without needing a login.
 .PP
 You can either use an htpasswd file which can take lots of users, or set
-a single username and password with the \[en]user and \[en]pass flags.
+a single username and password with the \-\-user and \-\-pass flags.
 .PP
-Use \[en]htpasswd /path/to/htpasswd to provide an htpasswd file.
+Use \-\-htpasswd /path/to/htpasswd to provide an htpasswd file.
 This is in standard apache format and supports MD5, SHA1 and BCrypt for
 basic authentication.
 Bcrypt is recommended.
@@ -6039,34 +6593,57 @@ htpasswd \-B htpasswd anotherUser
 .PP
 The password file can be updated while rclone is running.
 .PP
-Use \[en]realm to set the authentication realm.
+Use \-\-realm to set the authentication realm.
 .SS SSL/TLS
 .PP
 By default this will serve over http.
 If you want you can serve over https.
-You will need to supply the \[en]cert and \[en]key flags.
+You will need to supply the \-\-cert and \-\-key flags.
 If you wish to do client side certificate validation then you will need
-to supply \[en]client\-ca also.
+to supply \-\-client\-ca also.
 .PP
-\[en]cert should be either a PEM encoded certificate or a concatenation
+\-\-cert should be either a PEM encoded certificate or a concatenation
 of that with the CA certificate.
-\[en]key should be the PEM encoded private key and \[en]client\-ca
-should be the PEM encoded client certificate authority certificate.
-.SS Directory Cache
+\-\-key should be the PEM encoded private key and \-\-client\-ca should
+be the PEM encoded client certificate authority certificate.
+.SS VFS \- Virtual File System
 .PP
-Using the \f[C]\-\-dir\-cache\-time\f[R] flag, you can set how long a
-directory should be considered up to date and not refreshed from the
+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.
+.PP
+Cloud storage objects have lots of properties which aren\[aq]t like disk
+files \- you can\[aq]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.
+.PP
+The VFS layer also implements a directory cache \- this caches info
+about files and directories (but not the data) in memory.
+.SS VFS Directory Cache
+.PP
+Using the \f[C]\-\-dir\-cache\-time\f[R] flag, you can control how long
+a directory should be considered up to date and not refreshed from the
 backend.
-Changes made locally in the mount may appear immediately or invalidate
-the cache.
-However, changes done on the remote will only be picked up once the
+Changes made through the mount will appear immediately or invalidate the
+cache.
+.IP
+.nf
+\f[C]
+\-\-dir\-cache\-time duration   Time to cache directory entries for. (default 5m0s)
+\-\-poll\-interval duration    Time to wait between polling for changes.
+\f[R]
+.fi
+.PP
+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 on within the
+If the backend supports polling, changes will be picked up within the
 polling interval.
 .PP
-Alternatively, you can send a \f[C]SIGHUP\f[R] signal to rclone for it
-to flush all directory caches, regardless of how old they are.
+You can send a \f[C]SIGHUP\f[R] 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:
 .IP
@@ -6092,42 +6669,44 @@ Or individual files or directories:
 rclone rc vfs/forget file=path/to/file dir=path/to/dir
 \f[R]
 .fi
-.SS File Buffering
+.SS VFS File Buffering
 .PP
 The \f[C]\-\-buffer\-size\f[R] flag determines the amount of memory,
 that will be used to buffer data in advance.
 .PP
-Each open file descriptor will try to keep the specified amount of data
-in memory at all times.
-The buffered data is bound to one file descriptor and won\[cq]t be
-shared between multiple open file descriptors of the same file.
+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\[aq]t be shared.
 .PP
-This flag is a upper limit for the used memory per file descriptor.
+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.
+.PP
 The maximum memory used by rclone for buffering can be up to
 \f[C]\-\-buffer\-size * open files\f[R].
-.SS File Caching
+.SS VFS File Caching
 .PP
 These flags control the VFS file caching options.
-The VFS layer is used by rclone mount to make a cloud storage system
-work more like a normal file system.
+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.
 .PP
-You\[cq]ll need to enable VFS caching if you want, for example, to read
+For example you\[aq]ll need to enable VFS caching if you want to read
 and write simultaneously to a file.
 See below for more details.
 .PP
-Note that the VFS cache works in addition to the cache backend and you
-may find that you need one or the other or both.
+Note that the VFS cache is separate from the cache backend and you may
+find that you need one or the other or both.
 .IP
 .nf
 \f[C]
 \-\-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 age of objects in the cache. (default 1h0m0s)
-\-\-vfs\-cache\-mode string              Cache mode off|minimal|writes|full (default \[dq]off\[dq])
+\-\-vfs\-cache\-max\-size SizeSuffix      Max total size of objects in the cache. (default off)
 \-\-vfs\-cache\-poll\-interval duration   Interval to poll the cache for stale objects. (default 1m0s)
-\-\-vfs\-cache\-max\-size int             Max total size of objects in the cache. (default off)
+\-\-vfs\-write\-back duration            Time to writeback files after last use when using cache. (default 5s)
 \f[R]
 .fi
 .PP
@@ -6143,25 +6722,24 @@ The higher the cache mode the more compatible rclone becomes at the cost
 of using disk space.
 .PP
 Note that files are written back to the remote only when they are closed
-so if rclone is quit or dies with open files then these won\[cq]t get
-written back to the remote.
-However they will still be in the on disk cache.
+and if they haven\[aq]t been accessed for \-\-vfs\-write\-back second.
+If rclone is quit or dies with files that haven\[aq]t been uploaded,
+these will be uploaded next time rclone is run with the same flags.
 .PP
-If using \[en]vfs\-cache\-max\-size note that the cache may exceed this
+If using \-\-vfs\-cache\-max\-size note that the cache may exceed this
 size for two reasons.
-Firstly because it is only checked every
-\[en]vfs\-cache\-poll\-interval.
+Firstly because it is only checked every \-\-vfs\-cache\-poll\-interval.
 Secondly because open files cannot be evicted from the cache.
-.SS \[en]vfs\-cache\-mode off
+.SS \-\-vfs\-cache\-mode off
 .PP
-In this mode the cache will read directly from the remote and write
-directly to the remote without caching anything on disk.
+In this mode (the default) the cache will read directly from the remote
+and write directly to the remote without caching anything on disk.
 .PP
 This will mean some operations are not possible
 .IP \[bu] 2
-Files can\[cq]t be opened for both read AND write
+Files can\[aq]t be opened for both read AND write
 .IP \[bu] 2
-Files opened for write can\[cq]t be seeked
+Files opened for write can\[aq]t be seeked
 .IP \[bu] 2
 Existing files opened for write must have O_TRUNC set
 .IP \[bu] 2
@@ -6171,57 +6749,108 @@ Files open for write only will behave as if O_TRUNC was supplied
 .IP \[bu] 2
 Open modes O_APPEND, O_TRUNC are ignored
 .IP \[bu] 2
-If an upload fails it can\[cq]t be retried
-.SS \[en]vfs\-cache\-mode minimal
+If an upload fails it can\[aq]t be retried
+.SS \-\-vfs\-cache\-mode minimal
 .PP
-This is very similar to \[lq]off\[rq] except that files opened for read
-AND write will be buffered to disks.
+This is very similar to \[dq]off\[dq] 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.
 .PP
 These operations are not possible
 .IP \[bu] 2
-Files opened for write only can\[cq]t be seeked
+Files opened for write only can\[aq]t be seeked
 .IP \[bu] 2
 Existing files opened for write must have O_TRUNC set
 .IP \[bu] 2
 Files opened for write only will ignore O_APPEND, O_TRUNC
 .IP \[bu] 2
-If an upload fails it can\[cq]t be retried
-.SS \[en]vfs\-cache\-mode writes
+If an upload fails it can\[aq]t be retried
+.SS \-\-vfs\-cache\-mode writes
 .PP
 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.
 .PP
 This mode should support all normal file system operations.
 .PP
-If an upload fails it will be retried up to \[en]low\-level\-retries
-times.
-.SS \[en]vfs\-cache\-mode full
+If an upload fails it will be retried at exponentially increasing
+intervals up to 1 minute.
+.SS \-\-vfs\-cache\-mode full
 .PP
 In this mode all reads and writes are buffered to and from disk.
-When a file is opened for read it will be downloaded in its entirety
-first.
+When data is read from the remote this is buffered to disk as well.
 .PP
-This may be appropriate for your needs, or you may prefer to look at the
-cache backend which does a much more sophisticated job of caching,
-including caching directory hierarchies and chunks of files.
+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 dowloaded.
 .PP
-In this mode, unlike the others, when a file is written to the disk, it
-will be kept on the disk after it is written to the remote.
-It will be purged on a schedule according to
-\f[C]\-\-vfs\-cache\-max\-age\f[R].
+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.
 .PP
-This mode should support all normal file system operations.
+This mode should support all normal file system operations and is
+otherwise identical to \-\-vfs\-cache\-mode writes.
 .PP
-If an upload or download fails it will be retried up to
-\[en]low\-level\-retries times.
-.SS Case Sensitivity
+When reading a file rclone will read \-\-buffer\-size plus
+\-\-vfs\-read\-ahead bytes ahead.
+The \-\-buffer\-size is buffered in memory whereas the
+\-\-vfs\-read\-ahead is buffered on disk.
+.PP
+When using this mode it is recommended that \-\-buffer\-size is not set
+too big and \-\-vfs\-read\-ahead is set large if required.
+.SS VFS Performance
+.PP
+These flags may be used to enable/disable features of the VFS for
+performance or other reasons.
+.PP
+In particular S3 and Swift benefit hugely from the \-\-no\-modtime flag
+(or use \-\-use\-server\-modtime for a slightly different effect) as
+each read of the modification time takes a transaction.
+.IP
+.nf
+\f[C]
+\-\-no\-checksum     Don\[aq]t compare checksums on up/download.
+\-\-no\-modtime      Don\[aq]t read/write the modification time (can speed things up).
+\-\-no\-seek         Don\[aq]t allow seeking in files.
+\-\-read\-only       Mount read\-only.
+\f[R]
+.fi
+.PP
+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 is advantageous because some cloud providers account for reads
+being all the data requested, not all the data delivered.
+.PP
+Rclone will keep doubling the chunk size requested starting at
+\-\-vfs\-read\-chunk\-size with a maximum of
+\-\-vfs\-read\-chunk\-size\-limit unless it is set to \[dq]off\[dq] in
+which case there will be no limit.
+.IP
+.nf
+\f[C]
+\-\-vfs\-read\-chunk\-size SizeSuffix        Read the source objects in chunks. (default 128M)
+\-\-vfs\-read\-chunk\-size\-limit SizeSuffix  Max chunk doubling size (default \[dq]off\[dq])
+\f[R]
+.fi
+.PP
+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.
+.IP
+.nf
+\f[C]
+\-\-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)
+\f[R]
+.fi
+.SS VFS Case Sensitivity
 .PP
 Linux file systems are case\-sensitive: two files can differ only by
 case, and the exact case must be used when opening a file.
 .PP
-Windows is not like most other operating systems supported by rclone.
 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
@@ -6233,12 +6862,12 @@ Usually file systems on macOS are case\-insensitive.
 It is possible to make macOS file systems case\-sensitive but that is
 not the default
 .PP
-The \[lq]\[en]vfs\-case\-insensitive\[rq] mount flag controls how rclone
+The \[dq]\-\-vfs\-case\-insensitive\[dq] mount flag controls how rclone
 handles these two cases.
-If its value is \[lq]false\[rq], rclone passes file names to the mounted
-file system as is.
-If the flag is \[lq]true\[rq] (or appears without a value on command
-line), rclone may perform a \[lq]fixup\[rq] as explained below.
+If its value is \[dq]false\[dq], rclone passes file names to the mounted
+file system as\-is.
+If the flag is \[dq]true\[dq] (or appears without a value on command
+line), rclone may perform a \[dq]fixup\[dq] as explained below.
 .PP
 The user may specify a file name to open/delete/rename/etc with a case
 different than what is stored on mounted file system.
@@ -6254,13 +6883,13 @@ an underlying mounted file system.
 Note that case sensitivity of the operating system running rclone (the
 target) may differ from case sensitivity of a file system mounted by
 rclone (the source).
-The flag controls whether \[lq]fixup\[rq] is performed to satisfy the
+The flag controls whether \[dq]fixup\[dq] is performed to satisfy the
 target.
 .PP
-If the flag is not provided on command line, then its default value
-depends on the operating system where rclone runs: \[lq]true\[rq] on
-Windows and macOS, \[lq]false\[rq] otherwise.
-If the flag is provided without a value, then it is \[lq]true\[rq].
+If the flag is not provided on the command line, then its default value
+depends on the operating system where rclone runs: \[dq]true\[dq] on
+Windows and macOS, \[dq]false\[dq] otherwise.
+If the flag is provided without a value, then it is \[dq]true\[dq].
 .SS Auth Proxy
 .PP
 If you supply the parameter \f[C]\-\-auth\-proxy /path/to/program\f[R]
@@ -6278,11 +6907,11 @@ There is an example program
 bin/test_proxy.py (https://github.com/rclone/rclone/blob/master/test_proxy.py)
 in the rclone source code.
 .PP
-The program\[cq]s job is to take a \f[C]user\f[R] and \f[C]pass\f[R] on
+The program\[aq]s job is to take a \f[C]user\f[R] and \f[C]pass\f[R] 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\[cq]t use configuration from environment variables or command
+it won\[aq]t use configuration from environment variables or command
 line options \- it is the job of the proxy program to make a complete
 config.
 .PP
@@ -6343,12 +6972,12 @@ example to make proxy to many different sftp backends, you could make
 the \f[C]user\f[R] be \f[C]user\[at]example.com\f[R] and then set the
 \f[C]host\f[R] to \f[C]example.com\f[R] in the output and the user to
 \f[C]user\f[R].
-For security you\[cq]d probably want to restrict the \f[C]host\f[R] to a
+For security you\[aq]d probably want to restrict the \f[C]host\f[R] to a
 limited list.
 .PP
 Note that an internal cache is keyed on \f[C]user\f[R] so only use that
-for configuration, don\[cq]t use \f[C]pass\f[R] or \f[C]public_key\f[R].
-This also means that if a user\[cq]s password or public\-key is changed
+for configuration, don\[aq]t use \f[C]pass\f[R] or \f[C]public_key\f[R].
+This also means that if a user\[aq]s password or public\-key is changed
 the cache will need to expire (which takes 5 mins) before it takes
 effect.
 .PP
@@ -6397,9 +7026,11 @@ rclone serve webdav remote:path [flags]
       \-\-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\-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 128M)
       \-\-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. \[aq]off\[aq] is unlimited. (default off)
       \-\-vfs\-read\-wait duration                 Time to wait for in\-sequence read before seeking. (default 20ms)
+      \-\-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)
 \f[R]
 .fi
@@ -6480,20 +7111,23 @@ Set the modification time on object(s) as specified by remote:path to
 have the current time.
 .PP
 If remote:path does not exist then a zero sized object will be created
-unless the \[en]no\-create flag is provided.
+unless the \-\-no\-create flag is provided.
 .PP
-If \[en]timestamp is used then it will set the modification time to that
+If \-\-timestamp is used then it will set the modification time to that
 time instead of the current time.
 Times may be specified as one of:
 .IP \[bu] 2
-`YYMMDD' \- eg.
+\[aq]YYMMDD\[aq] \- eg.
 17.10.30
 .IP \[bu] 2
-`YYYY\-MM\-DDTHH:MM:SS' \- eg.
+\[aq]YYYY\-MM\-DDTHH:MM:SS\[aq] \- eg.
 2006\-01\-02T15:04:05
+.IP \[bu] 2
+\[aq]YYYY\-MM\-DDTHH:MM:SS.SSS\[aq] \- eg.
+2006\-01\-02T15:04:05.123456789
 .PP
-Note that \[en]timestamp is in UTC if you want local time then add the
-\[en]localtime flag.
+Note that \-\-timestamp is in UTC if you want local time then add the
+\-\-localtime flag.
 .IP
 .nf
 \f[C]
@@ -6543,13 +7177,13 @@ $ rclone tree remote:path
 .fi
 .PP
 You can use any of the filtering options with the tree command (eg
-\[en]include and \[en]exclude).
-You can also use \[en]fast\-list.
+\-\-include and \-\-exclude).
+You can also use \-\-fast\-list.
 .PP
 The tree command has many options for controlling the listing which are
 compatible with the tree command.
 Note that not all of them have short options as they conflict with
-rclone\[cq]s short options.
+rclone\[aq]s short options.
 .IP
 .nf
 \f[C]
@@ -6569,7 +7203,7 @@ rclone tree remote:path [flags]
       \-\-human           Print the size in a more human readable way.
       \-\-level int       Descend only level directories deep.
   \-D, \-\-modtime         Print the date of last modification.
-  \-i, \-\-noindent        Don\[aq]t print indentation lines.
+      \-\-noindent        Don\[aq]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.
@@ -6598,7 +7232,7 @@ that file.
 The destination remote must point to a directory \- rclone will give the
 error
 \f[C]Failed to create file system for \[dq]remote:file\[dq]: is a file not a directory\f[R]
-if it isn\[cq]t.
+if it isn\[aq]t.
 .PP
 For example, suppose you have a remote with a file in called
 \f[C]test.jpg\f[R], then you could copy just that file like this
@@ -6642,8 +7276,8 @@ This refers to the local file system.
 On Windows only \f[C]\[rs]\f[R] may be used instead of \f[C]/\f[R] in
 local paths \f[B]only\f[R], non local paths must use \f[C]/\f[R].
 .PP
-These paths needn\[cq]t start with a leading \f[C]/\f[R] \- if they
-don\[cq]t then they will be relative to the current directory.
+These paths needn\[aq]t start with a leading \f[C]/\f[R] \- if they
+don\[aq]t then they will be relative to the current directory.
 .SS remote:path/to/dir
 .PP
 This refers to a directory \f[C]path/to/dir\f[R] on \f[C]remote:\f[R] as
@@ -6655,7 +7289,7 @@ On most backends this is refers to the same directory as
 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 \f[C]/\f[R] will refer to your
-\[lq]home\[rq] directory and paths with a leading \f[C]/\f[R] will refer
+\[dq]home\[dq] directory and paths with a leading \f[C]/\f[R] will refer
 to the root.
 .SS :backend:path/to/dir
 .PP
@@ -6702,6 +7336,11 @@ rclone copy \-\-sftp\-host example.com :sftp:path/to/dir /tmp/dir
 .PP
 To copy files and directories from \f[C]example.com\f[R] in the relative
 directory \f[C]path/to/dir\f[R] to \f[C]/tmp/dir\f[R] using sftp.
+.SS Valid remote names
+.IP \[bu] 2
+Remote names may only contain 0\-9, A\-Z ,a\-z ,_ , \- and space.
+.IP \[bu] 2
+Remote names may not start with \-.
 .SS Quoting and the shell
 .PP
 When you are typing commands to your computer you are using something
@@ -6733,7 +7372,7 @@ rclone copy \[dq]O\[aq]Reilly Reviews\[dq] remote:backup
 .fi
 .PP
 The rules for quoting metacharacters are complicated and if you want the
-full details you\[cq]ll have to consult the manual page for your shell.
+full details you\[aq]ll have to consult the manual page for your shell.
 .SS Windows
 .PP
 If your names have spaces in you need to put them in \f[C]\[dq]\f[R], eg
@@ -6744,7 +7383,7 @@ rclone copy \[dq]E:\[rs]folder name\[rs]folder name\[rs]folder name\[dq] remote:
 \f[R]
 .fi
 .PP
-If you are using the root directory on its own then don\[cq]t quote it
+If you are using the root directory on its own then don\[aq]t quote it
 (see #464 (https://github.com/rclone/rclone/issues/464) for why), eg
 .IP
 .nf
@@ -6766,7 +7405,7 @@ So to sync a directory called \f[C]sync:me\f[R] to a remote called
 .IP
 .nf
 \f[C]
-rclone sync ./sync:me remote:path
+rclone sync \-i ./sync:me remote:path
 \f[R]
 .fi
 .PP
@@ -6774,7 +7413,7 @@ or
 .IP
 .nf
 \f[C]
-rclone sync /full/path/to/sync:me remote:path
+rclone sync \-i /full/path/to/sync:me remote:path
 \f[R]
 .fi
 .SS Server Side Copy
@@ -6784,7 +7423,7 @@ overview (https://rclone.org/overview/#optional-features)) support
 server side copy.
 .PP
 This means if you want to copy one folder to another then rclone
-won\[cq]t download all the files and re\-upload them; it will instruct
+won\[aq]t download all the files and re\-upload them; it will instruct
 the server to copy them in place.
 .PP
 Eg
@@ -6798,12 +7437,12 @@ rclone copy s3:oldbucket s3:newbucket
 Will copy the contents of \f[C]oldbucket\f[R] to \f[C]newbucket\f[R]
 without downloading and re\-uploading.
 .PP
-Remotes which don\[cq]t support server side copy \f[B]will\f[R] download
+Remotes which don\[aq]t support server side copy \f[B]will\f[R] download
 and re\-upload in this case.
 .PP
 Server side copies are used with \f[C]sync\f[R] and \f[C]copy\f[R] and
 will be identified in the log when using the \f[C]\-v\f[R] flag.
-The \f[C]move\f[R] command may also use them if remote doesn\[cq]t
+The \f[C]move\f[R] command may also use them if remote doesn\[aq]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.
@@ -6815,8 +7454,8 @@ This can be used when scripting to make aged backups efficiently, eg
 .IP
 .nf
 \f[C]
-rclone sync remote:current\-backup remote:previous\-backup
-rclone sync /path/to/files remote:current\-backup
+rclone sync \-i remote:current\-backup remote:previous\-backup
+rclone sync \-i /path/to/files remote:current\-backup
 \f[R]
 .fi
 .SS Options
@@ -6836,17 +7475,17 @@ command line argument for rclone.
 .PP
 Options which use TIME use the go time parser.
 A duration string is a possibly signed sequence of decimal numbers, each
-with optional fraction and a unit suffix, such as \[lq]300ms\[rq],
-\[lq]\-1.5h\[rq] or \[lq]2h45m\[rq].
-Valid time units are \[lq]ns\[rq], \[lq]us\[rq] (or \[lq]\[mc]s\[rq]),
-\[lq]ms\[rq], \[lq]s\[rq], \[lq]m\[rq], \[lq]h\[rq].
+with optional fraction and a unit suffix, such as \[dq]300ms\[dq],
+\[dq]\-1.5h\[dq] or \[dq]2h45m\[dq].
+Valid time units are \[dq]ns\[dq], \[dq]us\[dq] (or \[dq]\[mc]s\[dq]),
+\[dq]ms\[dq], \[dq]s\[dq], \[dq]m\[dq], \[dq]h\[dq].
 .PP
 Options which use SIZE use kByte by default.
 However, a suffix of \f[C]b\f[R] for bytes, \f[C]k\f[R] for kBytes,
 \f[C]M\f[R] for MBytes, \f[C]G\f[R] for GBytes, \f[C]T\f[R] for TBytes
 and \f[C]P\f[R] for PBytes may be used.
 These are the binary units, eg 1, 2**10, 2**20, 2**30 respectively.
-.SS \[en]backup\-dir=DIR
+.SS \-\-backup\-dir=DIR
 .PP
 When using \f[C]sync\f[R], \f[C]copy\f[R] or \f[C]move\f[R] any files
 which would have been overwritten or deleted are moved in their original
@@ -6865,7 +7504,7 @@ For example
 .IP
 .nf
 \f[C]
-rclone sync /path/to/local remote:current \-\-backup\-dir remote:old
+rclone sync \-i /path/to/local remote:current \-\-backup\-dir remote:old
 \f[R]
 .fi
 .PP
@@ -6873,20 +7512,20 @@ will sync \f[C]/path/to/local\f[R] to \f[C]remote:current\f[R], but for
 any files which would have been updated or deleted will be stored in
 \f[C]remote:old\f[R].
 .PP
-If running rclone from a script you might want to use today\[cq]s date
+If running rclone from a script you might want to use today\[aq]s date
 as the directory name passed to \f[C]\-\-backup\-dir\f[R] to store the
 old files, or you might want to pass \f[C]\-\-suffix\f[R] with
-today\[cq]s date.
+today\[aq]s date.
 .PP
 See \f[C]\-\-compare\-dest\f[R] and \f[C]\-\-copy\-dest\f[R].
-.SS \[en]bind string
+.SS \-\-bind string
 .PP
 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\[cq]t resolve or resolves to more than one IP
+If the host name doesn\[aq]t resolve or resolves to more than one IP
 address it will give an error.
-.SS \[en]bwlimit=BANDWIDTH_SPEC
+.SS \-\-bwlimit=BANDWIDTH_SPEC
 .PP
 This option controls the bandwidth limit.
 Limits can be specified in two ways: As a single limit, or as a
@@ -6900,7 +7539,7 @@ The default is \f[C]0\f[R] which means to not limit bandwidth.
 For example, to limit bandwidth usage to 10 MBytes/s use
 \f[C]\-\-bwlimit 10M\f[R]
 .PP
-It is also possible to specify a \[lq]timetable\[rq] of limits, which
+It is also possible to specify a \[dq]timetable\[dq] of limits, which
 will cause certain limits to be applied at certain times.
 To specify a timetable, format your entries as
 \f[C]WEEKDAY\-HH:MM,BANDWIDTH WEEKDAY\-HH:MM,BANDWIDTH...\f[R] where:
@@ -6941,11 +7580,11 @@ Is equal to this:
 \f[C]\-\-bwlimit \[dq]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\[dq]\f[R]
 .PP
 Bandwidth limits only apply to the data transfer.
-They don\[cq]t apply to the bandwidth of the directory listings etc.
+They don\[aq]t apply to the bandwidth of the directory listings etc.
 .PP
 Note that the units are Bytes/s, not Bits/s.
 Typically connections are measured in Bits/s \- to convert divide by 8.
-For example, let\[cq]s say you have a 10 Mbit/s connection and you wish
+For example, let\[aq]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.625MByte/s so you would use a
 \f[C]\-\-bwlimit 0.625M\f[R] parameter for rclone.
@@ -6972,7 +7611,24 @@ change the bwlimit dynamically:
 rclone rc core/bwlimit rate=1M
 \f[R]
 .fi
-.SS \[en]buffer\-size=SIZE
+.SS \-\-bwlimit\-file=BANDWIDTH_SPEC
+.PP
+This option controls per file bandwidth limit.
+For the options see the \f[C]\-\-bwlimit\f[R] flag.
+.PP
+For example use this to allow no transfers to be faster than 1MByte/s
+.IP
+.nf
+\f[C]
+\-\-bwlimit\-file 1M
+\f[R]
+.fi
+.PP
+This can be used in conjunction with \f[C]\-\-bwlimit\f[R].
+.PP
+Note that if a schedule is provided the file will use the schedule in
+effect at the start of the transfer.
+.SS \-\-buffer\-size=SIZE
 .PP
 Use this sized buffer to speed up file transfers.
 Each \f[C]\-\-transfer\f[R] will use this much memory for buffering.
@@ -6986,8 +7642,8 @@ Set to \f[C]0\f[R] to disable the buffering for the minimum memory
 usage.
 .PP
 Note that the memory allocation of the buffers is influenced by the
-\[en]use\-mmap flag.
-.SS \[en]check\-first
+\-\-use\-mmap flag.
+.SS \-\-check\-first
 .PP
 If this flag is set then in a \f[C]sync\f[R], \f[C]copy\f[R] or
 \f[C]move\f[R], rclone will do all the checks to see whether files need
@@ -7001,7 +7657,7 @@ Using this flag can use more memory as it effectively sets
 \f[C]\-\-max\-backlog\f[R] to infinite.
 This means that all the info on the objects to transfer is held in
 memory before the transfers start.
-.SS \[en]checkers=N
+.SS \-\-checkers=N
 .PP
 The number of checkers to run in parallel.
 Checkers do the equality checking of files during a sync.
@@ -7009,14 +7665,14 @@ For some storage systems (eg S3, Swift, Dropbox) this can take a
 significant amount of time so they are run in parallel.
 .PP
 The default is to run 8 checkers in parallel.
-.SS \-c, \[en]checksum
+.SS \-c, \-\-checksum
 .PP
 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.
 .PP
-This is useful when the remote doesn\[cq]t support setting modified time
+This is useful when the remote doesn\[aq]t support setting modified time
 and a more accurate sync is desired than just checking the file size.
 .PP
 This is very useful when transferring between remotes which store the
@@ -7027,9 +7683,9 @@ the overview section (https://rclone.org/overview/).
 Eg \f[C]rclone \-\-checksum sync s3:/bucket swift:/bucket\f[R] would run
 much quicker than without the \f[C]\-\-checksum\f[R] flag.
 .PP
-When using this flag, rclone won\[cq]t update mtimes of remote files if
+When using this flag, rclone won\[aq]t update mtimes of remote files if
 they are incorrect as it would normally.
-.SS \[en]compare\-dest=DIR
+.SS \-\-compare\-dest=DIR
 .PP
 When using \f[C]sync\f[R], \f[C]copy\f[R] or \f[C]move\f[R] DIR is
 checked in addition to the destination for files.
@@ -7042,7 +7698,7 @@ You must use the same remote as the destination of the sync.
 The compare directory must not overlap the destination directory.
 .PP
 See \f[C]\-\-copy\-dest\f[R] and \f[C]\-\-backup\-dir\f[R].
-.SS \[en]config=CONFIG_FILE
+.SS \-\-config=CONFIG_FILE
 .PP
 Specify the location of the rclone config file.
 .PP
@@ -7062,7 +7718,7 @@ location is for you.
 .PP
 Use this flag to override the config location, eg
 \f[C]rclone \-\-config=\[dq].myconfig\[dq] .config\f[R].
-.SS \[en]contimeout=TIME
+.SS \-\-contimeout=TIME
 .PP
 Set the connection timeout.
 This should be in go time format which looks like \f[C]5s\f[R] for 5
@@ -7071,7 +7727,7 @@ seconds, \f[C]10m\f[R] for 10 minutes, or \f[C]3h30m\f[R].
 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 \f[C]1m\f[R] by default.
-.SS \[en]copy\-dest=DIR
+.SS \-\-copy\-dest=DIR
 .PP
 When using \f[C]sync\f[R], \f[C]copy\f[R] or \f[C]move\f[R] DIR is
 checked in addition to the destination for files.
@@ -7084,7 +7740,7 @@ same remote as the destination of the sync.
 The compare directory must not overlap the destination directory.
 .PP
 See \f[C]\-\-compare\-dest\f[R] and \f[C]\-\-backup\-dir\f[R].
-.SS \[en]dedupe\-mode MODE
+.SS \-\-dedupe\-mode MODE
 .PP
 Mode to run dedupe command in.
 One of \f[C]interactive\f[R], \f[C]skip\f[R], \f[C]first\f[R],
@@ -7092,7 +7748,7 @@ One of \f[C]interactive\f[R], \f[C]skip\f[R], \f[C]first\f[R],
 The default is \f[C]interactive\f[R].
 See the dedupe command for more information as to what these options
 mean.
-.SS \[en]disable FEATURE,FEATURE,\&...
+.SS \-\-disable FEATURE,FEATURE,...
 .PP
 This disables a comma separated list of optional features.
 For example to disable server side move and server side copy use:
@@ -7120,17 +7776,17 @@ get an idea of which feature does what.
 This flag can be useful for debugging and in exceptional circumstances
 (eg Google Drive limiting the total volume of Server Side Copies to
 100GB/day).
-.SS \-n, \[en]dry\-run
+.SS \-n, \-\-dry\-run
 .PP
 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 \f[C]sync\f[R] command which deletes files in
 the destination.
-.SS \[en]expect\-continue\-timeout=TIME
+.SS \-\-expect\-continue\-timeout=TIME
 .PP
-This specifies the amount of time to wait for a server\[cq]s first
+This specifies the amount of time to wait for a server\[aq]s first
 response headers after fully writing the request headers if the request
-has an \[lq]Expect: 100\-continue\[rq] header.
+has an \[dq]Expect: 100\-continue\[dq] header.
 Not all backends support using this.
 .PP
 Zero means no timeout and causes the body to be sent immediately,
@@ -7139,7 +7795,7 @@ This time does not include the time to send the request header.
 .PP
 The default is \f[C]1s\f[R].
 Set to \f[C]0\f[R] to disable.
-.SS \[en]error\-on\-no\-transfer
+.SS \-\-error\-on\-no\-transfer
 .PP
 By default, rclone will exit with return code 0 if there were no errors.
 .PP
@@ -7151,7 +7807,7 @@ if data was copied, or skipping if not.
 NB: Enabling this option turns a usually non\-fatal error into a
 potentially fatal one \- please check and adjust your scripts
 accordingly!
-.SS \[en]header
+.SS \-\-header
 .PP
 Add an HTTP header for all transactions.
 The flag can be repeated to add multiple headers.
@@ -7170,57 +7826,57 @@ with care.
 rclone ls remote:test \-\-header \[dq]X\-Rclone: Foo\[dq] \-\-header \[dq]X\-LetMeIn: Yes\[dq]
 \f[R]
 .fi
-.SS \[en]header\-download
+.SS \-\-header\-download
 .PP
 Add an HTTP header for all download transactions.
 The flag can be repeated to add multiple headers.
 .IP
 .nf
 \f[C]
-rclone sync s3:test/src \[ti]/dst \-\-header\-download \[dq]X\-Amz\-Meta\-Test: Foo\[dq] \-\-header\-download \[dq]X\-Amz\-Meta\-Test2: Bar\[dq]
+rclone sync \-i s3:test/src \[ti]/dst \-\-header\-download \[dq]X\-Amz\-Meta\-Test: Foo\[dq] \-\-header\-download \[dq]X\-Amz\-Meta\-Test2: Bar\[dq]
 \f[R]
 .fi
 .PP
 See the GitHub issue here (https://github.com/rclone/rclone/issues/59)
 for currently supported backends.
-.SS \[en]header\-upload
+.SS \-\-header\-upload
 .PP
 Add an HTTP header for all upload transactions.
 The flag can be repeated to add multiple headers.
 .IP
 .nf
 \f[C]
-rclone sync \[ti]/src s3:test/dst \-\-header\-upload \[dq]Content\-Disposition: attachment; filename=\[aq]cool.html\[aq]\[dq] \-\-header\-upload \[dq]X\-Amz\-Meta\-Test: FooBar\[dq]
+rclone sync \-i \[ti]/src s3:test/dst \-\-header\-upload \[dq]Content\-Disposition: attachment; filename=\[aq]cool.html\[aq]\[dq] \-\-header\-upload \[dq]X\-Amz\-Meta\-Test: FooBar\[dq]
 \f[R]
 .fi
 .PP
 See the GitHub issue here (https://github.com/rclone/rclone/issues/59)
 for currently supported backends.
-.SS \[en]ignore\-case\-sync
+.SS \-\-ignore\-case\-sync
 .PP
 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.
-.SS \[en]ignore\-checksum
+.SS \-\-ignore\-checksum
 .PP
 Normally rclone will check that the checksums of transferred files
-match, and give an error \[lq]corrupted on transfer\[rq] if they
-don\[cq]t.
+match, and give an error \[dq]corrupted on transfer\[dq] if they
+don\[aq]t.
 .PP
 You can use this option to skip that check.
-You should only use it if you have had the \[lq]corrupted on
-transfer\[rq] error message and you are sure you might want to transfer
+You should only use it if you have had the \[dq]corrupted on
+transfer\[dq] error message and you are sure you might want to transfer
 potentially corrupted data.
-.SS \[en]ignore\-existing
+.SS \-\-ignore\-existing
 .PP
 Using this option will make rclone unconditionally skip all files that
 exist on the destination, no matter the content of these files.
 .PP
-While this isn\[cq]t a generally recommended option, it can be useful in
+While this isn\[aq]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.
-.SS \[en]ignore\-size
+.SS \-\-ignore\-size
 .PP
 Normally rclone will look at modification time and size of files to see
 if they are equal.
@@ -7233,7 +7889,7 @@ transfer.
 This can be useful for transferring files to and from OneDrive which
 occasionally misreports the size of image files (see
 #399 (https://github.com/rclone/rclone/issues/399) for more info).
-.SS \-I, \[en]ignore\-times
+.SS \-I, \-\-ignore\-times
 .PP
 Using this option will cause rclone to unconditionally upload all files
 regardless of the state of files on the destination.
@@ -7241,7 +7897,7 @@ regardless of the state of files on the destination.
 Normally rclone would skip any files that have the same modification
 time and are the same size (or have the same checksum if using
 \f[C]\-\-checksum\f[R]).
-.SS \[en]immutable
+.SS \-\-immutable
 .PP
 Treat source and destination files as immutable and disallow
 modification.
@@ -7252,38 +7908,88 @@ If an existing file does not match between the source and destination,
 rclone will give the error
 \f[C]Source and destination exist but do not match: immutable file modified\f[R].
 .PP
-Note that only commands which transfer files (e.g.\ \f[C]sync\f[R],
-\f[C]copy\f[R], \f[C]move\f[R]) are affected by this behavior, and only
-modification is disallowed.
-Files may still be deleted explicitly (e.g.\ \f[C]delete\f[R],
-\f[C]purge\f[R]) or implicitly (e.g.\ \f[C]sync\f[R], \f[C]move\f[R]).
+Note that only commands which transfer files (e.g.
+\f[C]sync\f[R], \f[C]copy\f[R], \f[C]move\f[R]) are affected by this
+behavior, and only modification is disallowed.
+Files may still be deleted explicitly (e.g.
+\f[C]delete\f[R], \f[C]purge\f[R]) or implicitly (e.g.
+\f[C]sync\f[R], \f[C]move\f[R]).
 Use \f[C]copy \-\-immutable\f[R] if it is desired to avoid deletion as
 well as modification.
 .PP
 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.
-.SS \[en]leave\-root
+.SS \-i / \-\-interactive
 .PP
-During rmdirs it will not remove root directory, even if it\[cq]s empty.
-.SS \[en]log\-file=FILE
+This flag can be used to tell rclone that you wish a manual confirmation
+before destructive operations.
 .PP
-Log all of rclone\[cq]s output to FILE.
+It is \f[B]recommended\f[R] that you use this flag while learning rclone
+especially with \f[C]rclone sync\f[R].
+.PP
+For example
+.IP
+.nf
+\f[C]
+$ rclone delete \-i /tmp/dir
+rclone: delete \[dq]important\-file.txt\[dq]?
+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> n
+\f[R]
+.fi
+.PP
+The options mean
+.IP \[bu] 2
+\f[C]y\f[R]: \f[B]Yes\f[R], this operation should go ahead.
+You can also press Return for this to happen.
+You\[aq]ll be asked every time unless you choose \f[C]s\f[R] or
+\f[C]!\f[R].
+.IP \[bu] 2
+\f[C]n\f[R]: \f[B]No\f[R], do not do this operation.
+You\[aq]ll be asked every time unless you choose \f[C]s\f[R] or
+\f[C]!\f[R].
+.IP \[bu] 2
+\f[C]s\f[R]: \f[B]Skip\f[R] 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\[aq]ll be prompted for
+them.
+.IP \[bu] 2
+\f[C]!\f[R]: \f[B]Do all\f[R] the following operations with no more
+questions.
+Useful if you\[aq]ve decided that you don\[aq]t mind rclone doing that
+kind of operation.
+This takes effect until rclone exits .
+If there are any different kind of operations you\[aq]ll be prompted for
+them.
+.IP \[bu] 2
+\f[C]q\f[R]: \f[B]Quit\f[R] rclone now, just in case!
+.SS \-\-leave\-root
+.PP
+During rmdirs it will not remove root directory, even if it\[aq]s empty.
+.SS \-\-log\-file=FILE
+.PP
+Log all of rclone\[aq]s output to FILE.
 This is not active by default.
 This can be useful for tracking down problems with syncs in combination
 with the \f[C]\-v\f[R] flag.
 See the Logging section for more info.
 .PP
 Note that if you are using the \f[C]logrotate\f[R] program to manage
-rclone\[cq]s logs, then you should use the \f[C]copytruncate\f[R] option
-as rclone doesn\[cq]t have a signal to rotate logs.
-.SS \[en]log\-format LIST
+rclone\[aq]s logs, then you should use the \f[C]copytruncate\f[R] option
+as rclone doesn\[aq]t have a signal to rotate logs.
+.SS \-\-log\-format LIST
 .PP
 Comma separated list of log format options.
 \f[C]date\f[R], \f[C]time\f[R], \f[C]microseconds\f[R],
 \f[C]longfile\f[R], \f[C]shortfile\f[R], \f[C]UTC\f[R].
-The default is \[lq]\f[C]date\f[R],\f[C]time\f[R]\[rq].
-.SS \[en]log\-level LEVEL
+The default is \[dq]\f[C]date\f[R],\f[C]time\f[R]\[dq].
+.SS \-\-log\-level LEVEL
 .PP
 This sets the log level for rclone.
 The default log level is \f[C]NOTICE\f[R].
@@ -7303,11 +8009,11 @@ It outputs warnings and significant events.
 .PP
 \f[C]ERROR\f[R] is equivalent to \f[C]\-q\f[R].
 It only outputs error messages.
-.SS \[en]use\-json\-log
+.SS \-\-use\-json\-log
 .PP
 This switches the log format to JSON for rclone.
 The fields of json log are level, msg, source, time.
-.SS \[en]low\-level\-retries NUMBER
+.SS \-\-low\-level\-retries NUMBER
 .PP
 This controls the number of low level retries rclone does.
 .PP
@@ -7316,14 +8022,14 @@ 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 \f[C]\-v\f[R] flag.
 .PP
-This shouldn\[cq]t need to be changed from the default in normal
+This shouldn\[aq]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
 \f[C]\-\-retries\f[R] flag) quicker.
 .PP
 Disable low level retries with \f[C]\-\-low\-level\-retries 1\f[R].
-.SS \[en]max\-backlog=N
+.SS \-\-max\-backlog=N
 .PP
 This is the maximum allowable backlog of files in a sync/copy/move
 queued for being checked or transferred.
@@ -7342,12 +8048,12 @@ the remote which may be desirable.
 .PP
 Setting this to a negative number will make the backlog as large as
 possible.
-.SS \[en]max\-delete=N
+.SS \-\-max\-delete=N
 .PP
 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.
-.SS \[en]max\-depth=N
+.SS \-\-max\-depth=N
 .PP
 This modifies the recursion depth for all the commands except purge.
 .PP
@@ -7368,7 +8074,7 @@ Note that if you use this with \f[C]sync\f[R] and
 considered excluded and will be deleted on the destination.
 Test first with \f[C]\-\-dry\-run\f[R] if you are not sure what will
 happen.
-.SS \[en]max\-duration=TIME
+.SS \-\-max\-duration=TIME
 .PP
 Rclone will stop scheduling new transfers when it has run for the
 duration specified.
@@ -7377,8 +8083,8 @@ Defaults to off.
 .PP
 When the limit is reached any existing transfers will complete.
 .PP
-Rclone won\[cq]t exit with an error if the transfer limit is reached.
-.SS \[en]max\-transfer=SIZE
+Rclone won\[aq]t exit with an error if the transfer limit is reached.
+.SS \-\-max\-transfer=SIZE
 .PP
 Rclone will stop transferring when it has reached the size specified.
 Defaults to off.
@@ -7386,7 +8092,7 @@ Defaults to off.
 When the limit is reached all transfers will stop immediately.
 .PP
 Rclone will exit with exit code 8 if the transfer limit is reached.
-.SS \[en]cutoff\-mode=hard|soft|cautious
+.SS \-\-cutoff\-mode=hard|soft|cautious
 .PP
 This modifies the behavior of \f[C]\-\-max\-transfer\f[R] Defaults to
 \f[C]\-\-cutoff\-mode=hard\f[R].
@@ -7399,7 +8105,7 @@ transfers when Rclone reaches the limit.
 .PP
 Specifying \f[C]\-\-cutoff\-mode=cautious\f[R] will try to prevent
 Rclone from reaching the limit.
-.SS \[en]modify\-window=TIME
+.SS \-\-modify\-window=TIME
 .PP
 When checking whether a file has been modified, this is the maximum
 allowed time difference that a file can have and still be considered
@@ -7411,7 +8117,7 @@ if you are reading and writing to an OS X filing system this will be
 \f[C]1s\f[R] by default.
 .PP
 This command line flag allows you to override that computed default.
-.SS \[en]multi\-thread\-cutoff=SIZE
+.SS \-\-multi\-thread\-cutoff=SIZE
 .PP
 When downloading files to the local backend above this size, rclone will
 use multiple threads to download the file (default 250M).
@@ -7420,8 +8126,8 @@ Rclone preallocates the file (using
 \f[C]fallocate(FALLOC_FL_KEEP_SIZE)\f[R] on unix or
 \f[C]NTSetInformationFile\f[R] 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\[cq]t create fragmented or sparse files and
-there won\[cq]t be any assembly time at the end of the transfer.
+This means that rclone won\[aq]t create fragmented or sparse files and
+there won\[aq]t be any assembly time at the end of the transfer.
 .PP
 The number of threads used to download is controlled by
 \f[C]\-\-multi\-thread\-streams\f[R].
@@ -7447,7 +8153,7 @@ sparse (https://en.wikipedia.org/wiki/Sparse_file).
 Use \f[C]\-\-local\-no\-sparse\f[R] to disable sparse files (which may
 cause long delays at the start of downloads) or disable multi\-thread
 downloads with \f[C]\-\-multi\-thread\-streams 0\f[R]
-.SS \[en]multi\-thread\-streams=N
+.SS \-\-multi\-thread\-streams=N
 .PP
 When using multi thread downloads (see above
 \f[C]\-\-multi\-thread\-cutoff\f[R]) this sets the maximum number of
@@ -7470,7 +8176,7 @@ So if \f[C]\-\-multi\-thread\-cutoff 250MB\f[R] and
 500MB..750MB files will be downloaded with 3 streams
 .IP \[bu] 2
 750MB+ files will be downloaded with 4 streams
-.SS \[en]no\-check\-dest
+.SS \-\-no\-check\-dest
 .PP
 The \f[C]\-\-no\-check\-dest\f[R] can be used with \f[C]move\f[R] or
 \f[C]copy\f[R] and it causes rclone not to check the destination at all
@@ -7484,24 +8190,24 @@ files are always transferred
 .IP \[bu] 2
 this can cause duplicates on remotes which allow it (eg Google Drive)
 .IP \[bu] 2
-\f[C]\-\-retries 1\f[R] is recommended otherwise you\[cq]ll transfer
+\f[C]\-\-retries 1\f[R] is recommended otherwise you\[aq]ll transfer
 everything again on a retry
 .PP
 This flag is useful to minimise the transactions if you know that none
 of the files are on the destination.
 .PP
 This is a specialized flag which should be ignored by most users!
-.SS \[en]no\-gzip\-encoding
+.SS \-\-no\-gzip\-encoding
 .PP
-Don\[cq]t set \f[C]Accept\-Encoding: gzip\f[R].
-This means that rclone won\[cq]t ask the server for compressed files
+Don\[aq]t set \f[C]Accept\-Encoding: gzip\f[R].
+This means that rclone won\[aq]t ask the server for compressed files
 automatically.
-Useful if you\[cq]ve set the server to return files with
+Useful if you\[aq]ve set the server to return files with
 \f[C]Content\-Encoding: gzip\f[R] but you uploaded compressed files.
 .PP
 There is no need to set this in normal operation, and doing so will
 decrease the network transfer efficiency of rclone.
-.SS \[en]no\-traverse
+.SS \-\-no\-traverse
 .PP
 The \f[C]\-\-no\-traverse\f[R] flag controls whether the destination
 file system is traversed when using the \f[C]copy\f[R] or \f[C]move\f[R]
@@ -7515,15 +8221,15 @@ then \f[C]\-\-no\-traverse\f[R] will stop rclone listing the destination
 and save time.
 .PP
 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\[cq]t
-changed and won\[cq]t need copying then you shouldn\[cq]t use
+are doing a copy where lots of the files under consideration haven\[aq]t
+changed and won\[aq]t need copying then you shouldn\[aq]t use
 \f[C]\-\-no\-traverse\f[R].
 .PP
 See rclone copy (https://rclone.org/commands/rclone_copy/) for an
 example of how to use it.
-.SS \[en]no\-unicode\-normalization
+.SS \-\-no\-unicode\-normalization
 .PP
-Don\[cq]t normalize unicode characters in filenames during the sync
+Don\[aq]t normalize unicode characters in filenames during the sync
 routine.
 .PP
 Sometimes, an operating system will store filenames containing unicode
@@ -7537,14 +8243,14 @@ For example, by default e\[u0301] and \['e] will be normalized into the
 same character.
 With \f[C]\-\-no\-unicode\-normalization\f[R] they will be treated as
 unique characters.
-.SS \[en]no\-update\-modtime
+.SS \-\-no\-update\-modtime
 .PP
-When using this flag, rclone won\[cq]t update modification times of
+When using this flag, rclone won\[aq]t update modification times of
 remote files if they are incorrect as it would normally.
 .PP
 This can be used if the remote is being synced with another tool also
 (eg the Google Drive client).
-.SS \[en]order\-by string
+.SS \-\-order\-by string
 .PP
 The \f[C]\-\-order\-by\f[R] flag controls the order in which files in
 the backlog are processed in \f[C]rclone sync\f[R],
@@ -7606,13 +8312,13 @@ This means that it may transfer some files out of the order specified if
 there are no files in the backlog or the source has not been fully
 scanned yet
 .IP \[bu] 2
-there are more than \[en]max\-backlog files in the backlog
+there are more than \-\-max\-backlog files in the backlog
 .PP
 Rclone will do its best to transfer the best file it has so in practice
 this should not cause a problem.
 Think of \f[C]\-\-order\-by\f[R] as being more of a best efforts flag
 rather than a perfect ordering.
-.SS \[en]password\-command SpaceSepList
+.SS \-\-password\-command SpaceSepList
 .PP
 This flag supplies a program which should supply the config password
 when run.
@@ -7641,7 +8347,7 @@ See the Configuration Encryption for more info.
 .PP
 See a Windows PowerShell example on the
 Wiki (https://github.com/rclone/rclone/wiki/Windows-Powershell-use-rclone-password-command-for-Config-file-password).
-.SS \-P, \[en]progress
+.SS \-P, \-\-progress
 .PP
 This flag makes rclone update the stats in a static block in the
 terminal providing a realtime overview of the transfer.
@@ -7660,34 +8366,72 @@ Note: On Windows until this
 bug (https://github.com/Azure/go-ansiterm/issues/26) is fixed all
 non\-ASCII characters will be replaced with \f[C].\f[R] when
 \f[C]\-\-progress\f[R] is in use.
-.SS \-q, \[en]quiet
+.SS \-q, \-\-quiet
 .PP
-This flag will limit rclone\[cq]s output to error messages only.
-.SS \[en]retries int
+This flag will limit rclone\[aq]s output to error messages only.
+.SS \-\-refresh\-times
+.PP
+The \f[C]\-\-refresh\-times\f[R] flag can be used to update modification
+times of existing files when they are out of sync on backends which
+don\[aq]t support hashes.
+.PP
+This is useful if you uploaded files with the incorrect timestamps and
+you now wish to correct them.
+.PP
+This flag is \f[B]only\f[R] useful for destinations which don\[aq]t
+support hashes (eg \f[C]crypt\f[R]).
+.PP
+This can be used any of the sync commands \f[C]sync\f[R], \f[C]copy\f[R]
+or \f[C]move\f[R].
+.PP
+To use this flag you will need to be doing a modification time sync (so
+not using \f[C]\-\-size\-only\f[R] or \f[C]\-\-checksum\f[R]).
+The flag will have no effect when using \f[C]\-\-size\-only\f[R] or
+\f[C]\-\-checksum\f[R].
+.PP
+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 (eg on a \f[C]crypt\f[R] backend) then rclone
+will update the timestamp.
+.PP
+Note that some remotes can\[aq]t set the modification time without
+re\-uploading the file so this flag is less useful on them.
+.PP
+Normally if you are doing a modification time sync rclone will update
+modification times without \f[C]\-\-refresh\-times\f[R] provided that
+the remote supports checksums \f[B]and\f[R] 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.
+.SS \-\-retries int
 .PP
 Retry the entire sync if it fails this many times it fails (default 3).
 .PP
 Some remotes can be unreliable and a few retries help pick up the files
-which didn\[cq]t get transferred because of errors.
+which didn\[aq]t get transferred because of errors.
 .PP
 Disable retries with \f[C]\-\-retries 1\f[R].
-.SS \[en]retries\-sleep=TIME
+.SS \-\-retries\-sleep=TIME
 .PP
 This sets the interval between each retry specified by
 \f[C]\-\-retries\f[R]
 .PP
 The default is \f[C]0\f[R].
 Use \f[C]0\f[R] to disable.
-.SS \[en]size\-only
+.SS \-\-size\-only
 .PP
 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.
 .PP
 This can be useful transferring files from Dropbox which have been
-modified by the desktop sync client which doesn\[cq]t set checksums of
+modified by the desktop sync client which doesn\[aq]t set checksums of
 modification times in the same way as rclone.
-.SS \[en]stats=TIME
+.SS \-\-stats=TIME
 .PP
 Commands which transfer data (\f[C]sync\f[R], \f[C]copy\f[R],
 \f[C]copyto\f[R], \f[C]move\f[R], \f[C]moveto\f[R]) will print data
@@ -7703,14 +8447,14 @@ This can be useful when running other commands, \f[C]check\f[R] or
 \f[C]mount\f[R] for example.
 .PP
 Stats are logged at \f[C]INFO\f[R] level by default which means they
-won\[cq]t show at default log level \f[C]NOTICE\f[R].
+won\[aq]t show at default log level \f[C]NOTICE\f[R].
 Use \f[C]\-\-stats\-log\-level NOTICE\f[R] or \f[C]\-v\f[R] to make them
 show.
 See the Logging section for more info on log levels.
 .PP
 Note that on macOS you can send a SIGINFO (which is normally ctrl\-T in
 the terminal) to make the stats print immediately.
-.SS \[en]stats\-file\-name\-length integer
+.SS \-\-stats\-file\-name\-length integer
 .PP
 By default, the \f[C]\-\-stats\f[R] output will truncate file names and
 paths longer than 40 characters.
@@ -7718,33 +8462,33 @@ This is equivalent to providing
 \f[C]\-\-stats\-file\-name\-length 40\f[R].
 Use \f[C]\-\-stats\-file\-name\-length 0\f[R] to disable any truncation
 of file names printed by stats.
-.SS \[en]stats\-log\-level string
+.SS \-\-stats\-log\-level string
 .PP
 Log level to show \f[C]\-\-stats\f[R] output at.
 This can be \f[C]DEBUG\f[R], \f[C]INFO\f[R], \f[C]NOTICE\f[R], or
 \f[C]ERROR\f[R].
 The default is \f[C]INFO\f[R].
 This means at the default level of logging which is \f[C]NOTICE\f[R] the
-stats won\[cq]t show \- if you want them to then use
+stats won\[aq]t show \- if you want them to then use
 \f[C]\-\-stats\-log\-level NOTICE\f[R].
 See the Logging section for more info on log levels.
-.SS \[en]stats\-one\-line
+.SS \-\-stats\-one\-line
 .PP
 When this is specified, rclone condenses the stats into a single line
 showing the most important stats only.
-.SS \[en]stats\-one\-line\-date
+.SS \-\-stats\-one\-line\-date
 .PP
 When this is specified, rclone enables the single\-line stats and
 prepends the display with a date string.
 The default is \f[C]2006/01/02 15:04:05 \-\f[R]
-.SS \[en]stats\-one\-line\-date\-format
+.SS \-\-stats\-one\-line\-date\-format
 .PP
 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 golang specs (https://golang.org/pkg/time/#Time.Format) for date
 formatting syntax.
-.SS \[en]stats\-unit=bits|bytes
+.SS \-\-stats\-unit=bits|bytes
 .PP
 By default, data transfer rates will be printed in bytes/second.
 .PP
@@ -7756,7 +8500,7 @@ The rate is reported as a binary unit, not SI unit.
 So 1 Mbit/s equals 1,048,576 bits/s and not 1,000,000 bits/s.
 .PP
 The default is \f[C]bytes\f[R].
-.SS \[en]suffix=SUFFIX
+.SS \-\-suffix=SUFFIX
 .PP
 When using \f[C]sync\f[R], \f[C]copy\f[R] or \f[C]move\f[R] any files
 which would have been overwritten or deleted will have the suffix added
@@ -7775,36 +8519,36 @@ For example
 .IP
 .nf
 \f[C]
-rclone sync /path/to/local/file remote:current \-\-suffix .bak
+rclone sync \-i /path/to/local/file remote:current \-\-suffix .bak
 \f[R]
 .fi
 .PP
 will sync \f[C]/path/to/local\f[R] to \f[C]remote:current\f[R], but for
 any files which would have been updated or deleted have .bak added.
-.SS \[en]suffix\-keep\-extension
+.SS \-\-suffix\-keep\-extension
 .PP
 When using \f[C]\-\-suffix\f[R], setting this causes rclone put the
 SUFFIX before the extension of the files that it backs up rather than
 after.
 .PP
-So let\[cq]s say we had \f[C]\-\-suffix \-2019\-01\-01\f[R], without the
+So let\[aq]s say we had \f[C]\-\-suffix \-2019\-01\-01\f[R], without the
 flag \f[C]file.txt\f[R] would be backed up to
 \f[C]file.txt\-2019\-01\-01\f[R] and with the flag it would be backed up
 to \f[C]file\-2019\-01\-01.txt\f[R].
 This can be helpful to make sure the suffixed files can still be opened.
-.SS \[en]syslog
+.SS \-\-syslog
 .PP
 On capable OSes (not Windows or Plan9) send all log output to syslog.
 .PP
 This can be useful for running rclone in a script or
 \f[C]rclone mount\f[R].
-.SS \[en]syslog\-facility string
+.SS \-\-syslog\-facility string
 .PP
 If using \f[C]\-\-syslog\f[R] this sets the syslog facility (eg
 \f[C]KERN\f[R], \f[C]USER\f[R]).
 See \f[C]man syslog\f[R] for a list of possible facilities.
 The default facility is \f[C]DAEMON\f[R].
-.SS \[en]tpslimit float
+.SS \-\-tpslimit float
 .PP
 Limit HTTP transactions per second to this.
 Default is 0 which is used to mean unlimited transactions per second.
@@ -7821,7 +8565,7 @@ This can be very useful for \f[C]rclone mount\f[R] to control the
 behaviour of applications using it.
 .PP
 See also \f[C]\-\-tpslimit\-burst\f[R].
-.SS \[en]tpslimit\-burst int
+.SS \-\-tpslimit\-burst int
 .PP
 Max burst of transactions for \f[C]\-\-tpslimit\f[R] (default
 \f[C]1\f[R]).
@@ -7839,9 +8583,9 @@ do 10 transactions very quickly before they are limited again.
 This may be used to increase performance of \f[C]\-\-tpslimit\f[R]
 without changing the long term average number of transactions per
 second.
-.SS \[en]track\-renames
+.SS \-\-track\-renames
 .PP
-By default, rclone doesn\[cq]t keep track of renamed files, so if you
+By default, rclone doesn\[aq]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.
 .PP
@@ -7856,8 +8600,10 @@ will be considered.
 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.
-Note: Encrypted destinations are not supported by
-\f[C]\-\-track\-renames\f[R].
+.PP
+Encrypted destinations are not currently supported by
+\f[C]\-\-track\-renames\f[R] if \f[C]\-\-track\-renames\-strategy\f[R]
+includes \f[C]hash\f[R].
 .PP
 Note that \f[C]\-\-track\-renames\f[R] is incompatible with
 \f[C]\-\-no\-traverse\f[R] and that it uses extra memory to keep track
@@ -7866,17 +8612,38 @@ of all the rename candidates.
 Note also that \f[C]\-\-track\-renames\f[R] is incompatible with
 \f[C]\-\-delete\-before\f[R] and will select \f[C]\-\-delete\-after\f[R]
 instead of \f[C]\-\-delete\-during\f[R].
-.SS \[en]track\-renames\-strategy (hash,modtime)
+.SS \-\-track\-renames\-strategy (hash,modtime,leaf,size)
 .PP
 This option changes the matching criteria for
-\f[C]\-\-track\-renames\f[R] to match by any combination of modtime,
-hash, size.
-Matching by size is always enabled no matter what option is selected
-here.
-This also means that it enables \f[C]\-\-track\-renames\f[R] support for
-encrypted destinations.
-If nothing is specified, the default option is matching by hashes.
-.SS \[en]delete\-(before,during,after)
+\f[C]\-\-track\-renames\f[R].
+.PP
+The matching is controlled by a comma separated selection of these
+tokens:
+.IP \[bu] 2
+\f[C]modtime\f[R] \- the modification time of the file \- not supported
+on all backends
+.IP \[bu] 2
+\f[C]hash\f[R] \- the hash of the file contents \- not supported on all
+backends
+.IP \[bu] 2
+\f[C]leaf\f[R] \- the name of the file not including its directory name
+.IP \[bu] 2
+\f[C]size\f[R] \- the size of the file (this is always enabled)
+.PP
+So using \f[C]\-\-track\-renames\-strategy modtime,leaf\f[R] would match
+files based on modification time, the leaf of the file name and the size
+only.
+.PP
+Using \f[C]\-\-track\-renames\-strategy modtime\f[R] or \f[C]leaf\f[R]
+can enable \f[C]\-\-track\-renames\f[R] support for encrypted
+destinations.
+.PP
+If nothing is specified, the default option is matching by
+\f[C]hash\f[R]es.
+.PP
+Note that the \f[C]hash\f[R] strategy is not supported with encrypted
+destinations.
+.SS \-\-delete\-(before,during,after)
 .PP
 This option allows you to specify when files on your destination are
 deleted when you sync folders.
@@ -7902,7 +8669,7 @@ 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 \f[C]not deleting files as there were IO errors\f[R].
-.SS \[en]fast\-list
+.SS \-\-fast\-list
 .PP
 When doing anything which involves a directory listing (eg
 \f[C]sync\f[R], \f[C]copy\f[R], \f[C]ls\f[R] \- in fact nearly every
@@ -7927,19 +8694,19 @@ Rclone has to load the whole listing into memory.
 .IP \[bu] 2
 It \f[I]may\f[R] be faster because it uses fewer transactions
 .IP \[bu] 2
-It \f[I]may\f[R] be slower because it can\[cq]t be parallelized
+It \f[I]may\f[R] be slower because it can\[aq]t be parallelized
 .PP
 rclone should always give identical results with and without
 \f[C]\-\-fast\-list\f[R].
 .PP
 If you pay for transactions and can fit your entire sync listing into
 memory then \f[C]\-\-fast\-list\f[R] is recommended.
-If you have a very big sync to do then don\[cq]t use
+If you have a very big sync to do then don\[aq]t use
 \f[C]\-\-fast\-list\f[R] otherwise you will run out of memory.
 .PP
-If you use \f[C]\-\-fast\-list\f[R] on a remote which doesn\[cq]t
+If you use \f[C]\-\-fast\-list\f[R] on a remote which doesn\[aq]t
 support it, then rclone will just ignore it.
-.SS \[en]timeout=TIME
+.SS \-\-timeout=TIME
 .PP
 This sets the IO idle timeout.
 If a transfer has started but then becomes idle for this long it is
@@ -7947,7 +8714,7 @@ considered broken and disconnected.
 .PP
 The default is \f[C]5m\f[R].
 Set to \f[C]0\f[R] to disable.
-.SS \[en]transfers=N
+.SS \-\-transfers=N
 .PP
 The number of file transfers to run in parallel.
 It can sometimes be useful to set this to a smaller number if the remote
@@ -7955,19 +8722,19 @@ is giving a lot of timeouts or bigger if you have lots of bandwidth and
 a fast remote.
 .PP
 The default is to run 4 file transfers in parallel.
-.SS \-u, \[en]update
+.SS \-u, \-\-update
 .PP
 This forces rclone to skip any files which exist on the destination and
 have a modified time that is newer than the source file.
 .PP
-This can be useful when transferring to a remote which doesn\[cq]t
+This can be useful when transferring to a remote which doesn\[aq]t
 support mod times directly (or when using
 \f[C]\-\-use\-server\-modtime\f[R] to avoid extra API calls) as it is
 more accurate than a \f[C]\-\-size\-only\f[R] check and faster than
 using \f[C]\-\-checksum\f[R].
 .PP
 If an existing destination file has a modification time equal (within
-the computed modify window precision) to the source file\[cq]s, it will
+the computed modify window precision) to the source file\[aq]s, it will
 be updated if the sizes are different.
 If \f[C]\-\-checksum\f[R] is set then rclone will update the destination
 if the checksums differ too.
@@ -7975,13 +8742,13 @@ if the checksums differ too.
 If an existing destination file is older than the source file then it
 will be updated if the size or checksum differs from the source file.
 .PP
-On remotes which don\[cq]t support mod time directly (or when using
+On remotes which don\[aq]t support mod time directly (or when using
 \f[C]\-\-use\-server\-modtime\f[R]) the time checked will be the
 uploaded time.
 This means that if uploading to one of these remotes, rclone will skip
 any files which exist on the destination and have an uploaded time that
 is newer than the modification time of the source file.
-.SS \[en]use\-mmap
+.SS \-\-use\-mmap
 .PP
 If this flag is set then rclone will use anonymous memory allocated by
 mmap on Unix based platforms and VirtualAlloc on Windows for its
@@ -7995,7 +8762,7 @@ are returned less aggressively to the OS.
 .PP
 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.
-.SS \[en]use\-server\-modtime
+.SS \-\-use\-server\-modtime
 .PP
 Some object\-store backends (e.g, Swift, S3) do not preserve file
 modification times (modtime).
@@ -8005,7 +8772,7 @@ By default it will make an API call to retrieve the metadata when the
 modtime is needed by an operation.
 .PP
 Use this flag to disable the extra API call and rely instead on the
-server\[cq]s modified time.
+server\[aq]s modified time.
 In cases such as a local to remote sync using \f[C]\-\-update\f[R],
 knowing the local file is newer than the time it was last uploaded to
 the remote is sufficient.
@@ -8016,7 +8783,7 @@ Using this flag on a sync operation without also using
 \f[C]\-\-update\f[R] 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.
-.SS \-v, \-vv, \[en]verbose
+.SS \-v, \-vv, \-\-verbose
 .PP
 With \f[C]\-v\f[R] rclone will tell you about each file that is
 transferred and a small number of significant events.
@@ -8024,7 +8791,7 @@ transferred and a small number of significant events.
 With \f[C]\-vv\f[R] rclone will become very verbose telling you about
 every file it considers and transfers.
 Please send bug reports with a log with this setting.
-.SS \-V, \[en]version
+.SS \-V, \-\-version
 .PP
 Prints the version number
 .SS SSL/TLS options
@@ -8034,14 +8801,14 @@ 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.
-.SS \[en]ca\-cert string
+.SS \-\-ca\-cert string
 .PP
 This loads the PEM encoded certificate authority certificate and uses it
 to verify the certificates of the servers rclone connects to.
 .PP
 If you have generated certificates signed with a local CA then you will
 need this flag to connect to servers using those certificates.
-.SS \[en]client\-cert string
+.SS \-\-client\-cert string
 .PP
 This loads the PEM encoded client side certificate.
 .PP
@@ -8049,15 +8816,15 @@ This is used for mutual TLS
 authentication (https://en.wikipedia.org/wiki/Mutual_authentication).
 .PP
 The \f[C]\-\-client\-key\f[R] flag is required too when using this.
-.SS \[en]client\-key string
+.SS \-\-client\-key string
 .PP
 This loads the PEM encoded client side private key used for mutual TLS
 authentication.
 Used in conjunction with \f[C]\-\-client\-cert\f[R].
-.SS \[en]no\-check\-certificate=true/false
+.SS \-\-no\-check\-certificate=true/false
 .PP
 \f[C]\-\-no\-check\-certificate\f[R] controls whether a client verifies
-the server\[cq]s certificate chain and host name.
+the server\[aq]s certificate chain and host name.
 If \f[C]\-\-no\-check\-certificate\f[R] is true, TLS accepts any
 certificate presented by the server and any host name in that
 certificate.
@@ -8073,7 +8840,7 @@ cloud services.
 This means that you should keep your \f[C].rclone.conf\f[R] file in a
 secure location.
 .PP
-If you are in an environment where that isn\[cq]t possible, you can add
+If you are in an environment where that isn\[aq]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.
@@ -8194,20 +8961,20 @@ password prompts.
 To do that, pass the parameter \f[C]\-\-ask\-password=false\f[R] to
 rclone.
 This will make rclone fail instead of asking for a password if
-\f[C]RCLONE_CONFIG_PASS\f[R] doesn\[cq]t contain a valid password, and
+\f[C]RCLONE_CONFIG_PASS\f[R] doesn\[aq]t contain a valid password, and
 \f[C]\-\-password\-command\f[R] has not been supplied.
 .SS Developer options
 .PP
 These options are useful when developing or debugging rclone.
-There are also some more remote specific options which aren\[cq]t
+There are also some more remote specific options which aren\[aq]t
 documented here which are used for testing.
 These start with remote name eg \f[C]\-\-drive\-test\-option\f[R] \- see
 the docs for the remote in question.
-.SS \[en]cpuprofile=FILE
+.SS \-\-cpuprofile=FILE
 .PP
 Write CPU profile to file.
 This can be analysed with \f[C]go tool pprof\f[R].
-.SS \[en]dump flag,flag,flag
+.SS \-\-dump flag,flag,flag
 .PP
 The \f[C]\-\-dump\f[R] flag takes a comma separated list of flags to
 dump info about.
@@ -8220,7 +8987,7 @@ In this case the body of the request will be gunzipped before showing
 it.
 .PP
 The available flags are:
-.SS \[en]dump headers
+.SS \-\-dump headers
 .PP
 Dump HTTP headers with \f[C]Authorization:\f[R] lines removed.
 May still contain sensitive info.
@@ -8229,45 +8996,45 @@ Useful for debugging only.
 .PP
 Use \f[C]\-\-dump auth\f[R] if you do want the \f[C]Authorization:\f[R]
 headers.
-.SS \[en]dump bodies
+.SS \-\-dump bodies
 .PP
 Dump HTTP headers and bodies \- may contain sensitive info.
 Can be very verbose.
 Useful for debugging only.
 .PP
-Note that the bodies are buffered in memory so don\[cq]t use this for
+Note that the bodies are buffered in memory so don\[aq]t use this for
 enormous files.
-.SS \[en]dump requests
+.SS \-\-dump requests
 .PP
 Like \f[C]\-\-dump bodies\f[R] but dumps the request bodies and the
 response headers.
 Useful for debugging download problems.
-.SS \[en]dump responses
+.SS \-\-dump responses
 .PP
 Like \f[C]\-\-dump bodies\f[R] but dumps the response bodies and the
 request headers.
 Useful for debugging upload problems.
-.SS \[en]dump auth
+.SS \-\-dump auth
 .PP
 Dump HTTP headers \- will contain sensitive info such as
 \f[C]Authorization:\f[R] headers \- use \f[C]\-\-dump headers\f[R] to
 dump without \f[C]Authorization:\f[R] headers.
 Can be very verbose.
 Useful for debugging only.
-.SS \[en]dump filters
+.SS \-\-dump filters
 .PP
 Dump the filters to the output.
 Useful to see exactly what include and exclude options are filtering on.
-.SS \[en]dump goroutines
+.SS \-\-dump goroutines
 .PP
 This dumps a list of the running go\-routines at the end of the command
 to standard output.
-.SS \[en]dump openfiles
+.SS \-\-dump openfiles
 .PP
 This dumps a list of the open files at the end of the command.
-It uses the \f[C]lsof\f[R] command to do that so you\[cq]ll need that
+It uses the \f[C]lsof\f[R] command to do that so you\[aq]ll need that
 installed to use it.
-.SS \[en]memprofile=FILE
+.SS \-\-memprofile=FILE
 .PP
 Write memory profile to file.
 This can be analysed with \f[C]go tool pprof\f[R].
@@ -8387,10 +9154,10 @@ errors)
 \f[C]6\f[R] \- Less serious errors (like 461 errors from dropbox)
 (NoRetry errors)
 .IP \[bu] 2
-\f[C]7\f[R] \- Fatal error (one that more retries won\[cq]t fix, like
+\f[C]7\f[R] \- Fatal error (one that more retries won\[aq]t fix, like
 account suspended) (Fatal errors)
 .IP \[bu] 2
-\f[C]8\f[R] \- Transfer exceeded \- limit set by \[en]max\-transfer
+\f[C]8\f[R] \- Transfer exceeded \- limit set by \-\-max\-transfer
 reached
 .IP \[bu] 2
 \f[C]9\f[R] \- Operation successful, but no files transferred
@@ -8448,6 +9215,34 @@ mys3:
 .PP
 Note that if you want to create a remote using environment variables you
 must create the \f[C]..._TYPE\f[R] variable as above.
+.SS Precedence
+.PP
+The various different methods of backend configuration are read in this
+order and the first one with a value is used.
+.IP \[bu] 2
+Flag values as supplied on the command line, eg
+\f[C]\-\-drive\-use\-trash\f[R].
+.IP \[bu] 2
+Remote specific environment vars, eg
+\f[C]RCLONE_CONFIG_MYREMOTE_USE_TRASH\f[R] (see above).
+.IP \[bu] 2
+Backend specific environment vars, eg \f[C]RCLONE_DRIVE_USE_TRASH\f[R].
+.IP \[bu] 2
+Config file, eg \f[C]use_trash = false\f[R].
+.IP \[bu] 2
+Default values, eg \f[C]true\f[R] \- these can\[aq]t be changed.
+.PP
+So if both \f[C]\-\-drive\-use\-trash\f[R] is supplied on the config
+line and an environment variable \f[C]RCLONE_DRIVE_USE_TRASH\f[R] is
+set, the command line flag will take preference.
+.PP
+For non backend configuration the order is as follows:
+.IP \[bu] 2
+Flag values as supplied on the command line, eg \f[C]\-\-stats 5s\f[R].
+.IP \[bu] 2
+Environment vars, eg \f[C]RCLONE_STATS=5s\f[R].
+.IP \[bu] 2
+Default values, eg \f[C]1m\f[R] \- these can\[aq]t be changed.
 .SS Other environment variables
 .IP \[bu] 2
 \f[C]RCLONE_CONFIG_PASS\f[R] set to contain your config file password
@@ -8461,9 +9256,13 @@ the lowercase versions thereof).
 https requests.
 .IP \[bu] 2
 The environment values may be either a complete URL or a
-\[lq]host[:port]\[rq] for, in which case the \[lq]http\[rq] scheme is
+\[dq]host[:port]\[dq] for, in which case the \[dq]http\[dq] scheme is
 assumed.
 .RE
+.IP \[bu] 2
+\f[C]RCLONE_CONFIG_DIR\f[R] \- rclone \f[B]sets\f[R] this variable for
+use in config files and sub processes to point to the directory holding
+the config file.
 .SH Configuring rclone on a remote / headless machine
 .PP
 Some of the configurations (those involving oauth2) require an Internet
@@ -8589,12 +9388,12 @@ mean read from standard input.
 .SS Patterns
 .PP
 The patterns used to match files for inclusion or exclusion are based on
-\[lq]file globs\[rq] as used by the unix shell.
+\[dq]file globs\[dq] as used by the unix shell.
 .PP
 If the pattern starts with a \f[C]/\f[R] then it only matches at the top
 level of the directory tree, \f[B]relative to the root of the
 remote\f[R] (not necessarily the root of the local drive).
-If it doesn\[cq]t start with \f[C]/\f[R] then it is matched starting at
+If it doesn\[aq]t start with \f[C]/\f[R] then it is matched starting at
 the \f[B]end of the path\f[R], but it will only match a complete path
 element:
 .IP
@@ -8704,7 +9503,7 @@ potato \- matches \[dq]potato\[dq]
 .PP
 Note also that rclone filter globs can only be used in one of the filter
 command line flags, not in the specification of the remote, so
-\f[C]rclone copy \[dq]remote:dir*.jpg\[dq] /path/to/dir\f[R] won\[cq]t
+\f[C]rclone copy \[dq]remote:dir*.jpg\[dq] /path/to/dir\f[R] won\[aq]t
 work \- what is required is
 \f[C]rclone \-\-include \[dq]*.jpg\[dq] copy remote:dir /path/to/dir\f[R]
 .SS Directories
@@ -8732,13 +9531,13 @@ directories.
 .PP
 Directory matches are \f[B]only\f[R] used to optimise directory access
 patterns \- you must still match the files that you want to match.
-Directory matches won\[cq]t optimise anything on bucket based remotes
-(eg s3, swift, google compute storage, b2) which don\[cq]t have a
+Directory matches won\[aq]t optimise anything on bucket based remotes
+(eg s3, swift, google compute storage, b2) which don\[aq]t have a
 concept of directory.
 .SS Differences between rsync and rclone patterns
 .PP
 Rclone implements bash style \f[C]{a,b,c}\f[R] glob matching which rsync
-doesn\[cq]t.
+doesn\[aq]t.
 .PP
 Rclone always does a wildcard match so \f[C]\[rs]\f[R] must always
 escape a \f[C]\[rs]\f[R].
@@ -8868,7 +9667,7 @@ This means you can mix \f[C]\-\-include\f[R] and
 \f[C]\-\-include\-from\f[R] with the other filters (eg
 \f[C]\-\-exclude\f[R]) but you must include all the files you want in
 the include statement.
-If this doesn\[cq]t provide enough flexibility then you must use
+If this doesn\[aq]t provide enough flexibility then you must use
 \f[C]\-\-filter\-from\f[R].
 .SS \f[C]\-\-include\-from\f[R] \- Read include patterns from file
 .PP
@@ -8900,7 +9699,7 @@ This means you can mix \f[C]\-\-include\f[R] and
 \f[C]\-\-include\-from\f[R] with the other filters (eg
 \f[C]\-\-exclude\f[R]) but you must include all the files you want in
 the include statement.
-If this doesn\[cq]t provide enough flexibility then you must use
+If this doesn\[aq]t provide enough flexibility then you must use
 \f[C]\-\-filter\-from\f[R].
 .SS \f[C]\-\-filter\f[R] \- Add a file\-filtering rule
 .PP
@@ -8975,7 +9774,7 @@ These are read in the order that they are placed on the command line.
 Paths within the \f[C]\-\-files\-from\f[R] file will be interpreted as
 starting with the root specified in the command.
 Leading \f[C]/\f[R] characters are ignored.
-See \[en]files\-from\-raw if you need the input to be processed in a raw
+See \-\-files\-from\-raw if you need the input to be processed in a raw
 manner.
 .PP
 For example, suppose you had \f[C]files\-from.txt\f[R] with this
@@ -9006,7 +9805,7 @@ This will transfer these files only (if they exist)
 \f[R]
 .fi
 .PP
-To take a more complicated example, let\[cq]s say you had a few files
+To take a more complicated example, let\[aq]s say you had a few files
 you want to back up regularly with these absolute paths:
 .IP
 .nf
@@ -9017,7 +9816,7 @@ you want to back up regularly with these absolute paths:
 \f[R]
 .fi
 .PP
-To copy these you\[cq]d find a common subdirectory \- in this case
+To copy these you\[aq]d find a common subdirectory \- in this case
 \f[C]/home\f[R] and put the remaining files in \f[C]files\-from.txt\f[R]
 with or without leading \f[C]/\f[R], eg
 .IP
@@ -9087,7 +9886,7 @@ processing.
 rclone lsf (https://rclone.org/commands/rclone_lsf/) has a compatible
 format that can be used to export file lists from remotes, which can
 then be used as an input to \f[C]\-\-files\-from\-raw\f[R].
-.SS \f[C]\-\-min\-size\f[R] \- Don\[cq]t transfer any file smaller than this
+.SS \f[C]\-\-min\-size\f[R] \- Don\[aq]t transfer any file smaller than this
 .PP
 This option controls the minimum size file which will be transferred.
 This defaults to \f[C]kBytes\f[R] but a suffix of \f[C]k\f[R],
@@ -9095,7 +9894,7 @@ This defaults to \f[C]kBytes\f[R] but a suffix of \f[C]k\f[R],
 .PP
 For example \f[C]\-\-min\-size 50k\f[R] means no files smaller than
 50kByte will be transferred.
-.SS \f[C]\-\-max\-size\f[R] \- Don\[cq]t transfer any file larger than this
+.SS \f[C]\-\-max\-size\f[R] \- Don\[aq]t transfer any file larger than this
 .PP
 This option controls the maximum size file which will be transferred.
 This defaults to \f[C]kBytes\f[R] but a suffix of \f[C]k\f[R],
@@ -9103,7 +9902,7 @@ This defaults to \f[C]kBytes\f[R] but a suffix of \f[C]k\f[R],
 .PP
 For example \f[C]\-\-max\-size 1G\f[R] means no files larger than 1GByte
 will be transferred.
-.SS \f[C]\-\-max\-age\f[R] \- Don\[cq]t transfer any file older than this
+.SS \f[C]\-\-max\-age\f[R] \- Don\[aq]t transfer any file older than this
 .PP
 This option controls the maximum age of files to transfer.
 Give in seconds or with a suffix of:
@@ -9129,14 +9928,14 @@ will be transferred.
 .PP
 This can also be an absolute time in one of these formats
 .IP \[bu] 2
-RFC3339 \- eg \[lq]2006\-01\-02T15:04:05Z07:00\[rq]
+RFC3339 \- eg \[dq]2006\-01\-02T15:04:05Z07:00\[dq]
 .IP \[bu] 2
-ISO8601 Date and time, local timezone \- \[lq]2006\-01\-02T15:04:05\[rq]
+ISO8601 Date and time, local timezone \- \[dq]2006\-01\-02T15:04:05\[dq]
 .IP \[bu] 2
-ISO8601 Date and time, local timezone \- \[lq]2006\-01\-02 15:04:05\[rq]
+ISO8601 Date and time, local timezone \- \[dq]2006\-01\-02 15:04:05\[dq]
 .IP \[bu] 2
-ISO8601 Date \- \[lq]2006\-01\-02\[rq] (YYYY\-MM\-DD)
-.SS \f[C]\-\-min\-age\f[R] \- Don\[cq]t transfer any file younger than this
+ISO8601 Date \- \[dq]2006\-01\-02\[dq] (YYYY\-MM\-DD)
+.SS \f[C]\-\-min\-age\f[R] \- Don\[aq]t transfer any file younger than this
 .PP
 This option controls the minimum age of files to transfer.
 Give in seconds or with a suffix (see \f[C]\-\-max\-age\f[R] for list of
@@ -9157,7 +9956,7 @@ the \f[C]\-\-min\-size 50k\f[R] flag
 .IP
 .nf
 \f[C]
-rclone sync A: B:
+rclone sync \-i A: B:
 \f[R]
 .fi
 .PP
@@ -9230,13 +10029,12 @@ command:
 .IP
 .nf
 \f[C]
-rclone sync \-\-exclude\-if\-present .ignore dir1 remote:backup
+rclone sync \-i \-\-exclude\-if\-present .ignore dir1 remote:backup
 \f[R]
 .fi
 .PP
-Currently only one filename is supported,
-i.e.\ \f[C]\-\-exclude\-if\-present\f[R] should not be used multiple
-times.
+Currently only one filename is supported, i.e.
+\f[C]\-\-exclude\-if\-present\f[R] should not be used multiple times.
 .SH GUI (Experimental)
 .PP
 Rclone can serve a web based GUI (graphical user interface).
@@ -9301,7 +10099,7 @@ Log out
 When you run the \f[C]rclone rcd \-\-rc\-web\-gui\f[R] this is what
 happens
 .IP \[bu] 2
-Rclone starts but only runs the remote control API (\[lq]rc\[rq]).
+Rclone starts but only runs the remote control API (\[dq]rc\[dq]).
 .IP \[bu] 2
 The API is bound to localhost with an auto generated username and
 password.
@@ -9381,44 +10179,44 @@ server which can be used to remote control rclone using its API.
 If you just want to run a remote control then see the rcd
 command (https://rclone.org/commands/rclone_rcd/).
 .SS Supported parameters
-.SS \[en]rc
+.SS \-\-rc
 .PP
 Flag to start the http server listen on remote requests
-.SS \[en]rc\-addr=IP
+.SS \-\-rc\-addr=IP
 .PP
 IPaddress:Port or :Port to bind server to.
-(default \[lq]localhost:5572\[rq])
-.SS \[en]rc\-cert=KEY
+(default \[dq]localhost:5572\[dq])
+.SS \-\-rc\-cert=KEY
 .PP
 SSL PEM key (concatenation of certificate and CA certificate)
-.SS \[en]rc\-client\-ca=PATH
+.SS \-\-rc\-client\-ca=PATH
 .PP
 Client certificate authority to verify clients with
-.SS \[en]rc\-htpasswd=PATH
+.SS \-\-rc\-htpasswd=PATH
 .PP
 htpasswd file \- if not provided no authentication is done
-.SS \[en]rc\-key=PATH
+.SS \-\-rc\-key=PATH
 .PP
 SSL PEM Private key
-.SS \[en]rc\-max\-header\-bytes=VALUE
+.SS \-\-rc\-max\-header\-bytes=VALUE
 .PP
 Maximum size of request header (default 4096)
-.SS \[en]rc\-user=VALUE
+.SS \-\-rc\-user=VALUE
 .PP
 User name for authentication.
-.SS \[en]rc\-pass=VALUE
+.SS \-\-rc\-pass=VALUE
 .PP
 Password for authentication.
-.SS \[en]rc\-realm=VALUE
+.SS \-\-rc\-realm=VALUE
 .PP
-Realm for authentication (default \[lq]rclone\[rq])
-.SS \[en]rc\-server\-read\-timeout=DURATION
+Realm for authentication (default \[dq]rclone\[dq])
+.SS \-\-rc\-server\-read\-timeout=DURATION
 .PP
 Timeout for server reading data (default 1h0m0s)
-.SS \[en]rc\-server\-write\-timeout=DURATION
+.SS \-\-rc\-server\-write\-timeout=DURATION
 .PP
 Timeout for server writing data (default 1h0m0s)
-.SS \[en]rc\-serve
+.SS \-\-rc\-serve
 .PP
 Enable the serving of remote objects via the HTTP interface.
 This means objects will be accessible at http://127.0.0.1:5572/ by
@@ -9428,7 +10226,7 @@ Objects may be requested from remotes using this syntax
 http://127.0.0.1:5572/[remote:path]/path/to/object
 .PP
 Default Off.
-.SS \[en]rc\-files /path/to/directory
+.SS \-\-rc\-files /path/to/directory
 .PP
 Path to local files to serve on the HTTP server.
 .PP
@@ -9441,55 +10239,55 @@ that is opened will have the authorization in the URL in the
 \f[C]http://user:pass\[at]localhost/\f[R] style.
 .PP
 Default Off.
-.SS \[en]rc\-enable\-metrics
+.SS \-\-rc\-enable\-metrics
 .PP
 Enable OpenMetrics/Prometheus compatible endpoint at \f[C]/metrics\f[R].
 .PP
 Default Off.
-.SS \[en]rc\-web\-gui
+.SS \-\-rc\-web\-gui
 .PP
 Set this flag to serve the default web gui on the same port as rclone.
 .PP
 Default Off.
-.SS \[en]rc\-allow\-origin
+.SS \-\-rc\-allow\-origin
 .PP
 Set the allowed Access\-Control\-Allow\-Origin for rc requests.
 .PP
-Can be used with \[en]rc\-web\-gui if the rclone is running on different
+Can be used with \-\-rc\-web\-gui if the rclone is running on different
 IP than the web\-gui.
 .PP
 Default is IP address on which rc is running.
-.SS \[en]rc\-web\-fetch\-url
+.SS \-\-rc\-web\-fetch\-url
 .PP
 Set the URL to fetch the rclone\-web\-gui files from.
 .PP
 Default
 https://api.github.com/repos/rclone/rclone\-webui\-react/releases/latest.
-.SS \[en]rc\-web\-gui\-update
+.SS \-\-rc\-web\-gui\-update
 .PP
 Set this flag to check and update rclone\-webui\-react from the
 rc\-web\-fetch\-url.
 .PP
 Default Off.
-.SS \[en]rc\-web\-gui\-force\-update
+.SS \-\-rc\-web\-gui\-force\-update
 .PP
 Set this flag to force update rclone\-webui\-react from the
 rc\-web\-fetch\-url.
 .PP
 Default Off.
-.SS \[en]rc\-web\-gui\-no\-open\-browser
+.SS \-\-rc\-web\-gui\-no\-open\-browser
 .PP
 Set this flag to disable opening browser automatically when using
 web\-gui.
 .PP
 Default Off.
-.SS \[en]rc\-job\-expire\-duration=DURATION
+.SS \-\-rc\-job\-expire\-duration=DURATION
 .PP
 Expire finished async jobs older than DURATION (default 60s).
-.SS \[en]rc\-job\-expire\-interval=DURATION
+.SS \-\-rc\-job\-expire\-interval=DURATION
 .PP
 Interval duration to check for expired async jobs (default 10s).
-.SS \[en]rc\-no\-auth
+.SS \-\-rc\-no\-auth
 .PP
 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
@@ -9522,6 +10320,7 @@ $ rclone rc rc/noop param1=one param2=two
 .PP
 Run \f[C]rclone rc\f[R] on its own to see the help for the installed
 remote control commands.
+.SS JSON input
 .PP
 \f[C]rclone rc\f[R] also supports a \f[C]\-\-json\f[R] flag which can be
 used to send more complicated input parameters.
@@ -9543,6 +10342,24 @@ $ rclone rc \-\-json \[aq]{ \[dq]p1\[dq]: [1,\[dq]2\[dq],null,4], \[dq]p2\[dq]:
 }
 \f[R]
 .fi
+.PP
+If the parameter being passed is an object then it can be passed as a
+JSON string rather than using the \f[C]\-\-json\f[R] flag which
+simplifies the command line.
+.IP
+.nf
+\f[C]
+rclone rc operations/list fs=/tmp remote=test opt=\[aq]{\[dq]showHash\[dq]: true}\[aq]
+\f[R]
+.fi
+.PP
+Rather than
+.IP
+.nf
+\f[C]
+rclone rc operations/list \-\-json \[aq]{\[dq]fs\[dq]: \[dq]/tmp\[dq], \[dq]remote\[dq]: \[dq]test\[dq], \[dq]opt\[dq]: {\[dq]showHash\[dq]: true}}\[aq]
+\f[R]
+.fi
 .SS Special parameters
 .PP
 The rc interface supports some special parameters which apply to
@@ -9652,7 +10469,7 @@ This takes the following parameters
 .IP \[bu] 2
 command \- a string with the command name
 .IP \[bu] 2
-fs \- a remote name string eg \[lq]drive:\[rq]
+fs \- a remote name string eg \[dq]drive:\[dq]
 .IP \[bu] 2
 arg \- a list of arguments for the backend command
 .IP \[bu] 2
@@ -9690,7 +10507,7 @@ Returns
 \f[R]
 .fi
 .PP
-Note that this is the direct equivalent of using this \[lq]backend\[rq]
+Note that this is the direct equivalent of using this \[dq]backend\[dq]
 command:
 .IP
 .nf
@@ -9699,7 +10516,7 @@ rclone backend noop . \-o echo=yes \-o blue path1 path2
 \f[R]
 .fi
 .PP
-Note that arguments must be preceded by the \[lq]\-a\[rq] flag
+Note that arguments must be preceded by the \[dq]\-a\[dq] flag
 .PP
 See the backend (https://rclone.org/commands/rclone_backend/) command
 for more information.
@@ -9734,13 +10551,13 @@ 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 \[lq]\-5:\[rq] represents the last 5 chunks of a file.
+The value \[dq]\-5:\[dq] represents the last 5 chunks of a file.
 .PP
-Some valid examples are: \[lq]:5,\-5:\[rq] \-> the first and last five
-chunks \[lq]0,\-2\[rq] \-> the first and the second last chunk
-\[lq]0:10\[rq] \-> the first ten chunks
+Some valid examples are: \[dq]:5,\-5:\[dq] \-> the first and last five
+chunks \[dq]0,\-2\[dq] \-> the first and the second last chunk
+\[dq]0:10\[dq] \-> the first ten chunks
 .PP
-Any parameter with a key that starts with \[lq]file\[rq] can be used to
+Any parameter with a key that starts with \[dq]file\[dq] can be used to
 specify files to fetch, eg
 .IP
 .nf
@@ -9760,7 +10577,7 @@ This takes the following parameters
 .IP \[bu] 2
 name \- name of remote
 .IP \[bu] 2
-parameters \- a map of { \[lq]key\[rq]: \[lq]value\[rq] } pairs
+parameters \- a map of { \[dq]key\[dq]: \[dq]value\[dq] } pairs
 .IP \[bu] 2
 type \- type of the new remote
 .IP \[bu] 2
@@ -9821,7 +10638,7 @@ This takes the following parameters
 .IP \[bu] 2
 name \- name of remote
 .IP \[bu] 2
-parameters \- a map of { \[lq]key\[rq]: \[lq]value\[rq] } pairs
+parameters \- a map of { \[dq]key\[dq]: \[dq]value\[dq] } pairs
 .PP
 See the config password
 command (https://rclone.org/commands/rclone_config_password/) command
@@ -9843,7 +10660,7 @@ This takes the following parameters
 .IP \[bu] 2
 name \- name of remote
 .IP \[bu] 2
-parameters \- a map of { \[lq]key\[rq]: \[lq]value\[rq] } pairs
+parameters \- a map of { \[dq]key\[dq]: \[dq]value\[dq] } pairs
 .IP \[bu] 2
 obscure \- optional bool \- forces obscuring of passwords
 .IP \[bu] 2
@@ -9887,13594 +10704,9844 @@ rclone rc core/bwlimit
 \f[R]
 .fi
 .PP
-The format of the parameter is exactly the same as passed to
-\[en]bwlimit except only one bandwidth may be specified.
+The format of the parameter is exactly the same as passed to \-\-bwlimit
+except only one bandwidth may be specified.
 .PP
-In either case \[lq]rate\[rq] is returned as a human readable string,
-and \[lq]bytesPerSecond\[rq] is returned as a number.
-.SS core/gc: Runs a garbage collection.
+In either case \[dq]rate\[dq] is returned as a human readable string,
+and \[dq]bytesPerSecond\[dq] is returned as a number.
+.SS core/command: Run a rclone terminal command over rc.
 .PP
-This tells the go runtime to do a garbage collection run.
-It isn\[cq]t necessary to call this normally, but it can be useful for
-debugging memory problems.
-.SS core/group\-list: Returns list of stats.
+This takes the following parameters
+.IP \[bu] 2
+command \- a string with the command name
+.IP \[bu] 2
+arg \- a list of arguments for the backend command
+.IP \[bu] 2
+opt \- a map of string to string of options
 .PP
-This returns list of stats groups currently in memory.
+Returns
+.IP \[bu] 2
+result \- result from the backend command
+.IP \[bu] 2
+error \- set if rclone exits with an error code
+.IP \[bu] 2
+returnType \- one of (\[dq]COMBINED_OUTPUT\[dq], \[dq]STREAM\[dq],
+\[dq]STREAM_ONLY_STDOUT\[dq].
+\[dq]STREAM_ONLY_STDERR\[dq])
 .PP
-Returns the following values:
+For example
+.IP
+.nf
+\f[C]
+rclone rc core/command command=ls \-a mydrive:/ \-o max\-depth=1
+rclone rc core/command \-a ls \-a mydrive:/ \-o max\-depth=1
+\f[R]
+.fi
+.PP
+Returns
 .IP
 .nf
 \f[C]
 {
-    \[dq]groups\[dq]:  an array of group names:
-        [
-            \[dq]group1\[dq],
-            \[dq]group2\[dq],
-            ...
-        ]
+    \[dq]error\[dq]: false,
+    \[dq]result\[dq]: \[dq]<Raw command line output>\[dq]
 }
+
+OR 
+{
+    \[dq]error\[dq]: true,
+    \[dq]result\[dq]: \[dq]<Raw command line output>\[dq]
+}
+
+**Authentication is required for this call.**
+
+### core/gc: Runs a garbage collection. {#core\-gc}
+
+This tells the go runtime to do a garbage collection run.  It isn\[aq]t
+necessary to call this normally, but it can be useful for debugging
+memory problems.
+
+### core/group\-list: Returns list of stats. {#core\-group\-list}
+
+This returns list of stats groups currently in memory. 
+
+Returns the following values:
 \f[R]
 .fi
-.SS core/memstats: Returns the memory statistics
-.PP
-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
 .PP
+{ \[dq]groups\[dq]: an array of group names: [ \[dq]group1\[dq],
+\[dq]group2\[dq], ...
+] }
+.IP
+.nf
+\f[C]
+
+### core/memstats: Returns the memory statistics {#core\-memstats}
+
+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
+
 The most interesting values for most people are:
-.IP \[bu] 2
-HeapAlloc: This is the amount of memory rclone is actually using
-.IP \[bu] 2
-HeapSys: This is the amount of memory rclone has obtained from the OS
-.IP \[bu] 2
-Sys: this is the total amount of memory requested from the OS
-.RS 2
-.IP \[bu] 2
-It is virtual memory so may include unused memory
-.RE
-.SS core/obscure: Obscures a string passed in.
-.PP
-Pass a clear string and rclone will obscure it for the config file: \-
-clear \- string
-.PP
-Returns \- obscured \- string
-.SS core/pid: Return PID of current process
-.PP
+
+* HeapAlloc: This is the amount of memory rclone is actually using
+* HeapSys: This is the amount of memory rclone has obtained from the OS
+* Sys: this is the total amount of memory requested from the OS
+  * It is virtual memory so may include unused memory
+
+### core/obscure: Obscures a string passed in. {#core\-obscure}
+
+Pass a clear string and rclone will obscure it for the config file:
+\- clear \- string
+
+Returns
+\- obscured \- string
+
+### core/pid: Return PID of current process {#core\-pid}
+
 This returns PID of current process.
 Useful for stopping rclone process.
-.SS core/quit: Terminates the app.
-.PP
-(optional) Pass an exit code to be used for terminating the app: \-
-exitCode \- int
-.SS core/stats: Returns stats about current transfers.
-.PP
+
+### core/quit: Terminates the app. {#core\-quit}
+
+(optional) Pass an exit code to be used for terminating the app:
+\- exitCode \- int
+
+### core/stats: Returns stats about current transfers. {#core\-stats}
+
 This returns all available stats:
-.IP
-.nf
-\f[C]
-rclone rc core/stats
-\f[R]
-.fi
-.PP
+
+    rclone rc core/stats
+
 If group is not provided then summed up stats for all groups will be
 returned.
-.PP
+
 Parameters
-.IP \[bu] 2
-group \- name of the stats group (string)
-.PP
+
+\- group \- name of the stats group (string)
+
 Returns the following values:
-.IP
-.nf
-\f[C]
-{
-    \[dq]speed\[dq]: average speed in bytes/sec since start of the process,
-    \[dq]bytes\[dq]: total transferred bytes since the start of the process,
-    \[dq]errors\[dq]: number of errors,
-    \[dq]fatalError\[dq]: whether there has been at least one FatalError,
-    \[dq]retryError\[dq]: whether there has been at least one non\-NoRetryError,
-    \[dq]checks\[dq]: number of checked files,
-    \[dq]transfers\[dq]: number of transferred files,
-    \[dq]deletes\[dq] : number of deleted files,
-    \[dq]renames\[dq] : number of renamed files,
-    \[dq]elapsedTime\[dq]: time in seconds since the start of the process,
-    \[dq]lastError\[dq]: last occurred error,
-    \[dq]transferring\[dq]: an array of currently active file transfers:
-        [
-            {
-                \[dq]bytes\[dq]: total transferred bytes for this file,
-                \[dq]eta\[dq]: estimated time in seconds until file transfer completion
-                \[dq]name\[dq]: name of the file,
-                \[dq]percentage\[dq]: progress of the file transfer in percent,
-                \[dq]speed\[dq]: speed in bytes/sec,
-                \[dq]speedAvg\[dq]: speed in bytes/sec as an exponentially weighted moving average,
-                \[dq]size\[dq]: size of the file in bytes
-            }
-        ],
-    \[dq]checking\[dq]: an array of names of currently active file checks
-        []
-}
 \f[R]
 .fi
 .PP
-Values for \[lq]transferring\[rq], \[lq]checking\[rq] and
-\[lq]lastError\[rq] are only assigned if data is available.
-The value for \[lq]eta\[rq] is null if an eta cannot be determined.
-.SS core/stats\-delete: Delete stats group.
-.PP
+{ \[dq]speed\[dq]: average speed in bytes/sec since start of the
+process, \[dq]bytes\[dq]: total transferred bytes since the start of the
+process, \[dq]errors\[dq]: number of errors, \[dq]fatalError\[dq]:
+whether there has been at least one FatalError, \[dq]retryError\[dq]:
+whether there has been at least one non\-NoRetryError, \[dq]checks\[dq]:
+number of checked files, \[dq]transfers\[dq]: number of transferred
+files, \[dq]deletes\[dq] : number of deleted files, \[dq]renames\[dq] :
+number of renamed files, \[dq]transferTime\[dq] : total time spent on
+running jobs, \[dq]elapsedTime\[dq]: time in seconds since the start of
+the process, \[dq]lastError\[dq]: last occurred error,
+\[dq]transferring\[dq]: an array of currently active file transfers: [ {
+\[dq]bytes\[dq]: total transferred bytes for this file, \[dq]eta\[dq]:
+estimated time in seconds until file transfer completion \[dq]name\[dq]:
+name of the file, \[dq]percentage\[dq]: progress of the file transfer in
+percent, \[dq]speed\[dq]: average speed over the whole transfer in
+bytes/sec, \[dq]speedAvg\[dq]: current speed in bytes/sec as an
+exponentially weighted moving average, \[dq]size\[dq]: size of the file
+in bytes } ], \[dq]checking\[dq]: an array of names of currently active
+file checks [] }
+.IP
+.nf
+\f[C]
+Values for \[dq]transferring\[dq], \[dq]checking\[dq] and \[dq]lastError\[dq] are only assigned if data is available.
+The value for \[dq]eta\[dq] is null if an eta cannot be determined.
+
+### core/stats\-delete: Delete stats group. {#core\-stats\-delete}
+
 This deletes entire stats group
-.PP
+
 Parameters
-.IP \[bu] 2
-group \- name of the stats group (string)
-.SS core/stats\-reset: Reset stats.
-.PP
-This clears counters, errors and finished transfers for all stats or
-specific stats group if group is provided.
-.PP
+
+\- group \- name of the stats group (string)
+
+### core/stats\-reset: Reset stats. {#core\-stats\-reset}
+
+This clears counters, errors and finished transfers for all stats or specific 
+stats group if group is provided.
+
 Parameters
-.IP \[bu] 2
-group \- name of the stats group (string)
-.SS core/transferred: Returns stats about completed transfers.
-.PP
+
+\- group \- name of the stats group (string)
+
+### core/transferred: Returns stats about completed transfers. {#core\-transferred}
+
 This returns stats about completed transfers:
-.IP
-.nf
-\f[C]
-rclone rc core/transferred
-\f[R]
-.fi
-.PP
+
+    rclone rc core/transferred
+
 If group is not provided then completed transfers for all groups will be
 returned.
-.PP
+
 Note only the last 100 completed transfers are returned.
-.PP
+
 Parameters
-.IP \[bu] 2
-group \- name of the stats group (string)
-.PP
+
+\- group \- name of the stats group (string)
+
 Returns the following values:
+\f[R]
+.fi
+.PP
+{ \[dq]transferred\[dq]: an array of completed transfers (including
+failed ones): [ { \[dq]name\[dq]: name of the file, \[dq]size\[dq]: size
+of the file in bytes, \[dq]bytes\[dq]: total transferred bytes for this
+file, \[dq]checked\[dq]: if the transfer is only checked (skipped,
+deleted), \[dq]timestamp\[dq]: integer representing millisecond unix
+epoch, \[dq]error\[dq]: string description of the error (empty if
+successful), \[dq]jobid\[dq]: id of the job that this transfer belongs
+to } ] }
 .IP
 .nf
 \f[C]
-{
-    \[dq]transferred\[dq]:  an array of completed transfers (including failed ones):
-        [
-            {
-                \[dq]name\[dq]: name of the file,
-                \[dq]size\[dq]: size of the file in bytes,
-                \[dq]bytes\[dq]: total transferred bytes for this file,
-                \[dq]checked\[dq]: if the transfer is only checked (skipped, deleted),
-                \[dq]timestamp\[dq]: integer representing millisecond unix epoch,
-                \[dq]error\[dq]: string description of the error (empty if successful),
-                \[dq]jobid\[dq]: id of the job that this transfer belongs to
-            }
-        ]
-}
-\f[R]
-.fi
-.SS core/version: Shows the current version of rclone and the go runtime.
-.PP
+
+### core/version: Shows the current version of rclone and the go runtime. {#core\-version}
+
 This shows the current version of go and the go runtime
-.IP \[bu] 2
-version \- rclone version, eg \[lq]v1.44\[rq]
-.IP \[bu] 2
-decomposed \- version number as [major, minor, patch, subpatch]
-.RS 2
-.IP \[bu] 2
-note patch and subpatch will be 999 for a git compiled version
-.RE
-.IP \[bu] 2
-isGit \- boolean \- true if this was compiled from the git version
-.IP \[bu] 2
-os \- OS in use as according to Go
-.IP \[bu] 2
-arch \- cpu architecture in use according to Go
-.IP \[bu] 2
-goVersion \- version of Go runtime in use
-.SS debug/set\-block\-profile\-rate: Set runtime.SetBlockProfileRate for blocking profiling.
-.PP
+
+\- version \- rclone version, eg \[dq]v1.53.0\[dq]
+\- decomposed \- version number as [major, minor, patch]
+\- isGit \- boolean \- true if this was compiled from the git version
+\- isBeta \- boolean \- true if this is a beta version
+\- os \- OS in use as according to Go
+\- arch \- cpu architecture in use according to Go
+\- goVersion \- version of Go runtime in use
+
+### debug/set\-block\-profile\-rate: Set runtime.SetBlockProfileRate for blocking profiling. {#debug\-set\-block\-profile\-rate}
+
 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.
-.PP
-To include every blocking event in the profile, pass rate = 1.
-To turn off profiling entirely, pass rate <= 0.
-.PP
+that are reported in the blocking profile. The profiler aims to sample
+an average of one blocking event per rate nanoseconds spent blocked.
+
+To include every blocking event in the profile, pass rate = 1. To turn
+off profiling entirely, pass rate <= 0.
+
 After calling this you can use this to see the blocking profile:
-.IP
-.nf
-\f[C]
-go tool pprof http://localhost:5572/debug/pprof/block
-\f[R]
-.fi
-.PP
+
+    go tool pprof http://localhost:5572/debug/pprof/block
+
 Parameters
-.IP \[bu] 2
-rate \- int
-.SS debug/set\-mutex\-profile\-fraction: Set runtime.SetMutexProfileFraction for mutex profiling.
-.PP
-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.
-.PP
-To turn off profiling entirely, pass rate 0.
-To just read the current rate, pass rate < 0.
-(For n>1 the details of sampling may change.)
-.PP
+
+\- rate \- int
+
+### debug/set\-mutex\-profile\-fraction: Set runtime.SetMutexProfileFraction for mutex profiling. {#debug\-set\-mutex\-profile\-fraction}
+
+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.
+
+To turn off profiling entirely, pass rate 0. To just read the current
+rate, pass rate < 0. (For n>1 the details of sampling may change.)
+
 Once this is set you can look use this to profile the mutex contention:
-.IP
-.nf
-\f[C]
-go tool pprof http://localhost:5572/debug/pprof/mutex
-\f[R]
-.fi
-.PP
+
+    go tool pprof http://localhost:5572/debug/pprof/mutex
+
 Parameters
-.IP \[bu] 2
-rate \- int
-.PP
+
+\- rate \- int
+
 Results
-.IP \[bu] 2
-previousRate \- int
-.SS job/list: Lists the IDs of the running jobs
-.PP
+
+\- previousRate \- int
+
+### job/list: Lists the IDs of the running jobs {#job\-list}
+
 Parameters \- None
-.PP
+
 Results
-.IP \[bu] 2
-jobids \- array of integer job ids
-.SS job/status: Reads the status of the job ID
-.PP
+
+\- jobids \- array of integer job ids
+
+### job/status: Reads the status of the job ID {#job\-status}
+
 Parameters
-.IP \[bu] 2
-jobid \- id of the job (integer)
-.PP
+
+\- jobid \- id of the job (integer)
+
 Results
-.IP \[bu] 2
-finished \- boolean
-.IP \[bu] 2
-duration \- time in seconds that the job ran for
-.IP \[bu] 2
-endTime \- time the job finished (eg
-\[lq]2018\-10\-26T18:50:20.528746884+01:00\[rq])
-.IP \[bu] 2
-error \- error from the job or empty string for no error
-.IP \[bu] 2
-finished \- boolean whether the job has finished or not
-.IP \[bu] 2
-id \- as passed in above
-.IP \[bu] 2
-startTime \- time the job started (eg
-\[lq]2018\-10\-26T18:50:20.528336039+01:00\[rq])
-.IP \[bu] 2
-success \- boolean \- true for success false otherwise
-.IP \[bu] 2
-output \- output of the job as would have been returned if called
-synchronously
-.IP \[bu] 2
-progress \- output of the progress related to the underlying job
-.SS job/stop: Stop the running job
-.PP
+
+\- finished \- boolean
+\- duration \- time in seconds that the job ran for
+\- endTime \- time the job finished (eg \[dq]2018\-10\-26T18:50:20.528746884+01:00\[dq])
+\- error \- error from the job or empty string for no error
+\- finished \- boolean whether the job has finished or not
+\- id \- as passed in above
+\- startTime \- time the job started (eg \[dq]2018\-10\-26T18:50:20.528336039+01:00\[dq])
+\- success \- boolean \- true for success false otherwise
+\- output \- output of the job as would have been returned if called synchronously
+\- progress \- output of the progress related to the underlying job
+
+### job/stop: Stop the running job {#job\-stop}
+
 Parameters
-.IP \[bu] 2
-jobid \- id of the job (integer)
-.SS mount/mount: Create a new mount point
-.PP
-rclone allows Linux, FreeBSD, macOS and Windows to mount any of
-Rclone\[cq]s cloud storage systems as a file system with FUSE.
-.PP
-If no mountType is provided, the priority is given as follows: 1.
-mount 2.cmount 3.mount2
-.PP
-This takes the following parameters
-.IP \[bu] 2
-fs \- a remote path to be mounted (required)
-.IP \[bu] 2
-mountPoint: valid path on the local machine (required)
-.IP \[bu] 2
-mountType: One of the values (mount, cmount, mount2) specifies the mount
-implementation to use
-.PP
-Eg
-.IP
-.nf
-\f[C]
-rclone rc mount/mount fs=mydrive: mountPoint=/home/<user>/mountPoint
-rclone rc mount/mount fs=mydrive: mountPoint=/home/<user>/mountPoint mountType=mount
-\f[R]
-.fi
-.PP
-\f[B]Authentication is required for this call.\f[R]
-.SS mount/types: Show all possible mount types
-.PP
-This shows all possible mount types and returns them as a list.
-.PP
+
+\- jobid \- id of the job (integer)
+
+### mount/listmounts: Show current mount points {#mount\-listmounts}
+
+This shows currently mounted points, which can be used for performing an unmount
+
 This takes no parameters and returns
-.IP \[bu] 2
-mountTypes: list of mount types
-.PP
-The mount types are strings like \[lq]mount\[rq], \[lq]mount2\[rq],
-\[lq]cmount\[rq] and can be passed to mount/mount as the mountType
-parameter.
-.PP
+
+\- mountPoints: list of current mount points
+
 Eg
-.IP
-.nf
-\f[C]
-rclone rc mount/types
-\f[R]
-.fi
-.PP
-\f[B]Authentication is required for this call.\f[R]
-.SS mount/unmount: Unmount all active mounts
-.PP
+
+    rclone rc mount/listmounts
+
+**Authentication is required for this call.**
+
+### mount/mount: Create a new mount point {#mount\-mount}
+
 rclone allows Linux, FreeBSD, macOS and Windows to mount any of
-Rclone\[cq]s cloud storage systems as a file system with FUSE.
-.PP
+Rclone\[aq]s cloud storage systems as a file system with FUSE.
+
+If no mountType is provided, the priority is given as follows: 1. mount 2.cmount 3.mount2
+
 This takes the following parameters
-.IP \[bu] 2
-mountPoint: valid path on the local machine where the mount was created
-(required)
-.PP
+
+\- fs \- a remote path to be mounted (required)
+\- mountPoint: valid path on the local machine (required)
+\- mountType: One of the values (mount, cmount, mount2) specifies the mount implementation to use
+\- mountOpt: a JSON object with Mount options in.
+\- vfsOpt: a JSON object with VFS options in.
+
 Eg
-.IP
-.nf
-\f[C]
-rclone rc mount/unmount mountPoint=/home/<user>/mountPoint
-\f[R]
-.fi
-.PP
-\f[B]Authentication is required for this call.\f[R]
-.SS operations/about: Return the space used on the remote
-.PP
+
+    rclone rc mount/mount fs=mydrive: mountPoint=/home/<user>/mountPoint
+    rclone rc mount/mount fs=mydrive: mountPoint=/home/<user>/mountPoint mountType=mount
+    rclone rc mount/mount fs=TestDrive: mountPoint=/mnt/tmp vfsOpt=\[aq]{\[dq]CacheMode\[dq]: 2}\[aq] mountOpt=\[aq]{\[dq]AllowOther\[dq]: true}\[aq]
+
+The vfsOpt are as described in options/get and can be seen in the the
+\[dq]vfs\[dq] section when running and the mountOpt can be seen in the \[dq]mount\[dq] section.
+
+    rclone rc options/get
+
+**Authentication is required for this call.**
+
+### mount/types: Show all possible mount types {#mount\-types}
+
+This shows all possible mount types and returns them as a list.
+
+This takes no parameters and returns
+
+\- mountTypes: list of mount types
+
+The mount types are strings like \[dq]mount\[dq], \[dq]mount2\[dq], \[dq]cmount\[dq] and can
+be passed to mount/mount as the mountType parameter.
+
+Eg
+
+    rclone rc mount/types
+
+**Authentication is required for this call.**
+
+### mount/unmount: Unmount selected active mount {#mount\-unmount}
+
+rclone allows Linux, FreeBSD, macOS and Windows to
+mount any of Rclone\[aq]s cloud storage systems as a file system with
+FUSE.
+
 This takes the following parameters
-.IP \[bu] 2
-fs \- a remote name string eg \[lq]drive:\[rq]
-.PP
-The result is as returned from rclone about \[en]json
-.PP
-See the about command (https://rclone.org/commands/rclone_size/) command
-for more information on the above.
-.PP
-\f[B]Authentication is required for this call.\f[R]
-.SS operations/cleanup: Remove trashed files in the remote or path
-.PP
+
+\- mountPoint: valid path on the local machine where the mount was created (required)
+
+Eg
+
+    rclone rc mount/unmount mountPoint=/home/<user>/mountPoint
+
+**Authentication is required for this call.**
+
+### mount/unmountall: Show current mount points {#mount\-unmountall}
+
+This shows currently mounted points, which can be used for performing an unmount
+
+This takes no parameters and returns error if unmount does not succeed.
+
+Eg
+
+    rclone rc mount/unmountall
+
+**Authentication is required for this call.**
+
+### operations/about: Return the space used on the remote {#operations\-about}
+
 This takes the following parameters
-.IP \[bu] 2
-fs \- a remote name string eg \[lq]drive:\[rq]
-.PP
-See the cleanup command (https://rclone.org/commands/rclone_cleanup/)
-command for more information on the above.
-.PP
-\f[B]Authentication is required for this call.\f[R]
-.SS operations/copyfile: Copy a file from source remote to destination remote
-.PP
+
+\- fs \- a remote name string eg \[dq]drive:\[dq]
+
+The result is as returned from rclone about \-\-json
+
+See the [about command](https://rclone.org/commands/rclone_size/) command for more information on the above.
+
+**Authentication is required for this call.**
+
+### operations/cleanup: Remove trashed files in the remote or path {#operations\-cleanup}
+
 This takes the following parameters
-.IP \[bu] 2
-srcFs \- a remote name string eg \[lq]drive:\[rq] for the source
-.IP \[bu] 2
-srcRemote \- a path within that remote eg \[lq]file.txt\[rq] for the
-source
-.IP \[bu] 2
-dstFs \- a remote name string eg \[lq]drive2:\[rq] for the destination
-.IP \[bu] 2
-dstRemote \- a path within that remote eg \[lq]file2.txt\[rq] for the
-destination
-.PP
-\f[B]Authentication is required for this call.\f[R]
-.SS operations/copyurl: Copy the URL to the object
-.PP
+
+\- fs \- a remote name string eg \[dq]drive:\[dq]
+
+See the [cleanup command](https://rclone.org/commands/rclone_cleanup/) command for more information on the above.
+
+**Authentication is required for this call.**
+
+### operations/copyfile: Copy a file from source remote to destination remote {#operations\-copyfile}
+
 This takes the following parameters
-.IP \[bu] 2
-fs \- a remote name string eg \[lq]drive:\[rq]
-.IP \[bu] 2
-remote \- a path within that remote eg \[lq]dir\[rq]
-.IP \[bu] 2
-url \- string, URL to read from
-.IP \[bu] 2
-autoFilename \- boolean, set to true to retrieve destination file name
-from url See the copyurl
-command (https://rclone.org/commands/rclone_copyurl/) command for more
-information on the above.
-.PP
-\f[B]Authentication is required for this call.\f[R]
-.SS operations/delete: Remove files in the path
-.PP
+
+\- srcFs \- a remote name string eg \[dq]drive:\[dq] for the source
+\- srcRemote \- a path within that remote eg \[dq]file.txt\[dq] for the source
+\- dstFs \- a remote name string eg \[dq]drive2:\[dq] for the destination
+\- dstRemote \- a path within that remote eg \[dq]file2.txt\[dq] for the destination
+
+**Authentication is required for this call.**
+
+### operations/copyurl: Copy the URL to the object {#operations\-copyurl}
+
 This takes the following parameters
-.IP \[bu] 2
-fs \- a remote name string eg \[lq]drive:\[rq]
-.PP
-See the delete command (https://rclone.org/commands/rclone_delete/)
-command for more information on the above.
-.PP
-\f[B]Authentication is required for this call.\f[R]
-.SS operations/deletefile: Remove the single file pointed to
-.PP
+
+\- fs \- a remote name string eg \[dq]drive:\[dq]
+\- remote \- a path within that remote eg \[dq]dir\[dq]
+\- url \- string, URL to read from
+ \- autoFilename \- boolean, set to true to retrieve destination file name from url
+See the [copyurl command](https://rclone.org/commands/rclone_copyurl/) command for more information on the above.
+
+**Authentication is required for this call.**
+
+### operations/delete: Remove files in the path {#operations\-delete}
+
 This takes the following parameters
-.IP \[bu] 2
-fs \- a remote name string eg \[lq]drive:\[rq]
-.IP \[bu] 2
-remote \- a path within that remote eg \[lq]dir\[rq]
-.PP
-See the deletefile
-command (https://rclone.org/commands/rclone_deletefile/) command for
-more information on the above.
-.PP
-\f[B]Authentication is required for this call.\f[R]
-.SS operations/fsinfo: Return information about the remote
-.PP
+
+\- fs \- a remote name string eg \[dq]drive:\[dq]
+
+See the [delete command](https://rclone.org/commands/rclone_delete/) command for more information on the above.
+
+**Authentication is required for this call.**
+
+### operations/deletefile: Remove the single file pointed to {#operations\-deletefile}
+
 This takes the following parameters
-.IP \[bu] 2
-fs \- a remote name string eg \[lq]drive:\[rq]
-.PP
+
+\- fs \- a remote name string eg \[dq]drive:\[dq]
+\- remote \- a path within that remote eg \[dq]dir\[dq]
+
+See the [deletefile command](https://rclone.org/commands/rclone_deletefile/) command for more information on the above.
+
+**Authentication is required for this call.**
+
+### operations/fsinfo: Return information about the remote {#operations\-fsinfo}
+
+This takes the following parameters
+
+\- fs \- a remote name string eg \[dq]drive:\[dq]
+
 This returns info about the remote passed in;
-.IP
-.nf
-\f[C]
-{
-    // optional features and whether they are available or not
-    \[dq]Features\[dq]: {
-        \[dq]About\[dq]: true,
-        \[dq]BucketBased\[dq]: false,
-        \[dq]CanHaveEmptyDirectories\[dq]: true,
-        \[dq]CaseInsensitive\[dq]: false,
-        \[dq]ChangeNotify\[dq]: false,
-        \[dq]CleanUp\[dq]: false,
-        \[dq]Copy\[dq]: false,
-        \[dq]DirCacheFlush\[dq]: false,
-        \[dq]DirMove\[dq]: true,
-        \[dq]DuplicateFiles\[dq]: false,
-        \[dq]GetTier\[dq]: false,
-        \[dq]ListR\[dq]: false,
-        \[dq]MergeDirs\[dq]: false,
-        \[dq]Move\[dq]: true,
-        \[dq]OpenWriterAt\[dq]: true,
-        \[dq]PublicLink\[dq]: false,
-        \[dq]Purge\[dq]: true,
-        \[dq]PutStream\[dq]: true,
-        \[dq]PutUnchecked\[dq]: false,
-        \[dq]ReadMimeType\[dq]: false,
-        \[dq]ServerSideAcrossConfigs\[dq]: false,
-        \[dq]SetTier\[dq]: false,
-        \[dq]SetWrapper\[dq]: false,
-        \[dq]UnWrap\[dq]: false,
-        \[dq]WrapFs\[dq]: false,
-        \[dq]WriteMimeType\[dq]: false
-    },
-    // Names of hashes available
-    \[dq]Hashes\[dq]: [
-        \[dq]MD5\[dq],
-        \[dq]SHA\-1\[dq],
-        \[dq]DropboxHash\[dq],
-        \[dq]QuickXorHash\[dq]
-    ],
-    \[dq]Name\[dq]: \[dq]local\[dq],    // Name as created
-    \[dq]Precision\[dq]: 1,     // Precision of timestamps in ns
-    \[dq]Root\[dq]: \[dq]/\[dq],        // Path as created
-    \[dq]String\[dq]: \[dq]Local file system at /\[dq] // how the remote will appear in logs
-}
 \f[R]
 .fi
 .PP
-This command does not have a command line equivalent so use this
-instead:
+{ // optional features and whether they are available or not
+\[dq]Features\[dq]: { \[dq]About\[dq]: true, \[dq]BucketBased\[dq]:
+false, \[dq]CanHaveEmptyDirectories\[dq]: true,
+\[dq]CaseInsensitive\[dq]: false, \[dq]ChangeNotify\[dq]: false,
+\[dq]CleanUp\[dq]: false, \[dq]Copy\[dq]: false,
+\[dq]DirCacheFlush\[dq]: false, \[dq]DirMove\[dq]: true,
+\[dq]DuplicateFiles\[dq]: false, \[dq]GetTier\[dq]: false,
+\[dq]ListR\[dq]: false, \[dq]MergeDirs\[dq]: false, \[dq]Move\[dq]:
+true, \[dq]OpenWriterAt\[dq]: true, \[dq]PublicLink\[dq]: false,
+\[dq]Purge\[dq]: true, \[dq]PutStream\[dq]: true,
+\[dq]PutUnchecked\[dq]: false, \[dq]ReadMimeType\[dq]: false,
+\[dq]ServerSideAcrossConfigs\[dq]: false, \[dq]SetTier\[dq]: false,
+\[dq]SetWrapper\[dq]: false, \[dq]UnWrap\[dq]: false, \[dq]WrapFs\[dq]:
+false, \[dq]WriteMimeType\[dq]: false }, // Names of hashes available
+\[dq]Hashes\[dq]: [ \[dq]MD5\[dq], \[dq]SHA\-1\[dq],
+\[dq]DropboxHash\[dq], \[dq]QuickXorHash\[dq] ], \[dq]Name\[dq]:
+\[dq]local\[dq], // Name as created \[dq]Precision\[dq]: 1, // Precision
+of timestamps in ns \[dq]Root\[dq]: \[dq]/\[dq], // Path as created
+\[dq]String\[dq]: \[dq]Local file system at /\[dq] // how the remote
+will appear in logs }
 .IP
 .nf
 \f[C]
-rclone rc \-\-loopback operations/fsinfo fs=remote:
-\f[R]
-.fi
-.SS operations/list: List the given remote and path in JSON format
-.PP
+
+This command does not have a command line equivalent so use this instead:
+
+    rclone rc \-\-loopback operations/fsinfo fs=remote:
+
+### operations/list: List the given remote and path in JSON format {#operations\-list}
+
 This takes the following parameters
-.IP \[bu] 2
-fs \- a remote name string eg \[lq]drive:\[rq]
-.IP \[bu] 2
-remote \- a path within that remote eg \[lq]dir\[rq]
-.IP \[bu] 2
-opt \- a dictionary of options to control the listing (optional)
-.RS 2
-.IP \[bu] 2
-recurse \- If set recurse directories
-.IP \[bu] 2
-noModTime \- If set return modification time
-.IP \[bu] 2
-showEncrypted \- If set show decrypted names
-.IP \[bu] 2
-showOrigIDs \- If set show the IDs for each item if known
-.IP \[bu] 2
-showHash \- If set return a dictionary of hashes
-.RE
-.PP
+
+\- fs \- a remote name string eg \[dq]drive:\[dq]
+\- remote \- a path within that remote eg \[dq]dir\[dq]
+\- opt \- a dictionary of options to control the listing (optional)
+    \- recurse \- If set recurse directories
+    \- noModTime \- If set return modification time
+    \- showEncrypted \-  If set show decrypted names
+    \- showOrigIDs \- If set show the IDs for each item if known
+    \- showHash \- If set return a dictionary of hashes
+
 The result is
-.IP \[bu] 2
-list
-.RS 2
-.IP \[bu] 2
-This is an array of objects as described in the lsjson command
-.RE
-.PP
-See the lsjson command (https://rclone.org/commands/rclone_lsjson/) for
-more information on the above and examples.
-.PP
-\f[B]Authentication is required for this call.\f[R]
-.SS operations/mkdir: Make a destination directory or container
-.PP
+
+\- list
+    \- This is an array of objects as described in the lsjson command
+
+See the [lsjson command](https://rclone.org/commands/rclone_lsjson/) for more information on the above and examples.
+
+**Authentication is required for this call.**
+
+### operations/mkdir: Make a destination directory or container {#operations\-mkdir}
+
 This takes the following parameters
-.IP \[bu] 2
-fs \- a remote name string eg \[lq]drive:\[rq]
-.IP \[bu] 2
-remote \- a path within that remote eg \[lq]dir\[rq]
-.PP
-See the mkdir command (https://rclone.org/commands/rclone_mkdir/)
-command for more information on the above.
-.PP
-\f[B]Authentication is required for this call.\f[R]
-.SS operations/movefile: Move a file from source remote to destination remote
-.PP
+
+\- fs \- a remote name string eg \[dq]drive:\[dq]
+\- remote \- a path within that remote eg \[dq]dir\[dq]
+
+See the [mkdir command](https://rclone.org/commands/rclone_mkdir/) command for more information on the above.
+
+**Authentication is required for this call.**
+
+### operations/movefile: Move a file from source remote to destination remote {#operations\-movefile}
+
 This takes the following parameters
-.IP \[bu] 2
-srcFs \- a remote name string eg \[lq]drive:\[rq] for the source
-.IP \[bu] 2
-srcRemote \- a path within that remote eg \[lq]file.txt\[rq] for the
-source
-.IP \[bu] 2
-dstFs \- a remote name string eg \[lq]drive2:\[rq] for the destination
-.IP \[bu] 2
-dstRemote \- a path within that remote eg \[lq]file2.txt\[rq] for the
-destination
-.PP
-\f[B]Authentication is required for this call.\f[R]
-.SS operations/publiclink: Create or retrieve a public link to the given file or folder.
-.PP
+
+\- srcFs \- a remote name string eg \[dq]drive:\[dq] for the source
+\- srcRemote \- a path within that remote eg \[dq]file.txt\[dq] for the source
+\- dstFs \- a remote name string eg \[dq]drive2:\[dq] for the destination
+\- dstRemote \- a path within that remote eg \[dq]file2.txt\[dq] for the destination
+
+**Authentication is required for this call.**
+
+### operations/publiclink: Create or retrieve a public link to the given file or folder. {#operations\-publiclink}
+
 This takes the following parameters
-.IP \[bu] 2
-fs \- a remote name string eg \[lq]drive:\[rq]
-.IP \[bu] 2
-remote \- a path within that remote eg \[lq]dir\[rq]
-.PP
+
+\- fs \- a remote name string eg \[dq]drive:\[dq]
+\- remote \- a path within that remote eg \[dq]dir\[dq]
+\- unlink \- boolean \- if set removes the link rather than adding it (optional)
+\- expire \- string \- the expiry time of the link eg \[dq]1d\[dq] (optional)
+
 Returns
-.IP \[bu] 2
-url \- URL of the resource
-.PP
-See the link command (https://rclone.org/commands/rclone_link/) command
-for more information on the above.
-.PP
-\f[B]Authentication is required for this call.\f[R]
-.SS operations/purge: Remove a directory or container and all of its contents
-.PP
+
+\- url \- URL of the resource
+
+See the [link command](https://rclone.org/commands/rclone_link/) command for more information on the above.
+
+**Authentication is required for this call.**
+
+### operations/purge: Remove a directory or container and all of its contents {#operations\-purge}
+
 This takes the following parameters
-.IP \[bu] 2
-fs \- a remote name string eg \[lq]drive:\[rq]
-.IP \[bu] 2
-remote \- a path within that remote eg \[lq]dir\[rq]
-.PP
-See the purge command (https://rclone.org/commands/rclone_purge/)
-command for more information on the above.
-.PP
-\f[B]Authentication is required for this call.\f[R]
-.SS operations/rmdir: Remove an empty directory or container
-.PP
+
+\- fs \- a remote name string eg \[dq]drive:\[dq]
+\- remote \- a path within that remote eg \[dq]dir\[dq]
+
+See the [purge command](https://rclone.org/commands/rclone_purge/) command for more information on the above.
+
+**Authentication is required for this call.**
+
+### operations/rmdir: Remove an empty directory or container {#operations\-rmdir}
+
 This takes the following parameters
-.IP \[bu] 2
-fs \- a remote name string eg \[lq]drive:\[rq]
-.IP \[bu] 2
-remote \- a path within that remote eg \[lq]dir\[rq]
-.PP
-See the rmdir command (https://rclone.org/commands/rclone_rmdir/)
-command for more information on the above.
-.PP
-\f[B]Authentication is required for this call.\f[R]
-.SS operations/rmdirs: Remove all the empty directories in the path
-.PP
+
+\- fs \- a remote name string eg \[dq]drive:\[dq]
+\- remote \- a path within that remote eg \[dq]dir\[dq]
+
+See the [rmdir command](https://rclone.org/commands/rclone_rmdir/) command for more information on the above.
+
+**Authentication is required for this call.**
+
+### operations/rmdirs: Remove all the empty directories in the path {#operations\-rmdirs}
+
 This takes the following parameters
-.IP \[bu] 2
-fs \- a remote name string eg \[lq]drive:\[rq]
-.IP \[bu] 2
-remote \- a path within that remote eg \[lq]dir\[rq]
-.IP \[bu] 2
-leaveRoot \- boolean, set to true not to delete the root
-.PP
-See the rmdirs command (https://rclone.org/commands/rclone_rmdirs/)
-command for more information on the above.
-.PP
-\f[B]Authentication is required for this call.\f[R]
-.SS operations/size: Count the number of bytes and files in remote
-.PP
+
+\- fs \- a remote name string eg \[dq]drive:\[dq]
+\- remote \- a path within that remote eg \[dq]dir\[dq]
+\- leaveRoot \- boolean, set to true not to delete the root
+
+See the [rmdirs command](https://rclone.org/commands/rclone_rmdirs/) command for more information on the above.
+
+**Authentication is required for this call.**
+
+### operations/size: Count the number of bytes and files in remote {#operations\-size}
+
 This takes the following parameters
-.IP \[bu] 2
-fs \- a remote name string eg \[lq]drive:path/to/dir\[rq]
-.PP
+
+\- fs \- a remote name string eg \[dq]drive:path/to/dir\[dq]
+
 Returns
-.IP \[bu] 2
-count \- number of files
-.IP \[bu] 2
-bytes \- number of bytes in those files
-.PP
-See the size command (https://rclone.org/commands/rclone_size/) command
-for more information on the above.
-.PP
-\f[B]Authentication is required for this call.\f[R]
-.SS options/blocks: List all the option blocks
-.PP
-Returns \- options \- a list of the options block names
-.SS options/get: Get all the options
-.PP
+
+\- count \- number of files
+\- bytes \- number of bytes in those files
+
+See the [size command](https://rclone.org/commands/rclone_size/) command for more information on the above.
+
+**Authentication is required for this call.**
+
+### operations/uploadfile: Upload file using multiform/form\-data {#operations\-uploadfile}
+
+This takes the following parameters
+
+\- fs \- a remote name string eg \[dq]drive:\[dq]
+\- remote \- a path within that remote eg \[dq]dir\[dq]
+\- each part in body represents a file to be uploaded
+See the [uploadfile command](https://rclone.org/commands/rclone_uploadfile/) command for more information on the above.
+
+**Authentication is required for this call.**
+
+### options/blocks: List all the option blocks {#options\-blocks}
+
+Returns
+\- options \- a list of the options block names
+
+### options/get: Get all the options {#options\-get}
+
 Returns an object where keys are option block names and values are an
 object with the current option values in.
-.PP
+
 This shows the internal names of the option within rclone which should
 map to the external options very easily with a few exceptions.
-.SS options/set: Set an option
-.PP
+
+### options/set: Set an option {#options\-set}
+
 Parameters
-.IP \[bu] 2
-option block name containing an object with
-.RS 2
-.IP \[bu] 2
-key: value
-.RE
-.PP
+
+\- option block name containing an object with
+  \- key: value
+
 Repeated as often as required.
-.PP
-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.
-.PP
+
+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.
+
 For example:
-.PP
+
 This sets DEBUG level logs (\-vv)
-.IP
-.nf
-\f[C]
-rclone rc options/set \-\-json \[aq]{\[dq]main\[dq]: {\[dq]LogLevel\[dq]: 8}}\[aq]
-\f[R]
-.fi
-.PP
+
+    rclone rc options/set \-\-json \[aq]{\[dq]main\[dq]: {\[dq]LogLevel\[dq]: 8}}\[aq]
+
 And this sets INFO level logs (\-v)
-.IP
-.nf
-\f[C]
-rclone rc options/set \-\-json \[aq]{\[dq]main\[dq]: {\[dq]LogLevel\[dq]: 7}}\[aq]
-\f[R]
-.fi
-.PP
+
+    rclone rc options/set \-\-json \[aq]{\[dq]main\[dq]: {\[dq]LogLevel\[dq]: 7}}\[aq]
+
 And this sets NOTICE level logs (normal without \-v)
-.IP
-.nf
-\f[C]
-rclone rc options/set \-\-json \[aq]{\[dq]main\[dq]: {\[dq]LogLevel\[dq]: 6}}\[aq]
-\f[R]
-.fi
-.SS rc/error: This returns an error
-.PP
+
+    rclone rc options/set \-\-json \[aq]{\[dq]main\[dq]: {\[dq]LogLevel\[dq]: 6}}\[aq]
+
+### pluginsctl/addPlugin: Add a plugin using url {#pluginsctl\-addPlugin}
+
+used for adding a plugin to the webgui
+
+This takes the following parameters
+
+\- url: http url of the github repo where the plugin is hosted (http://github.com/rclone/rclone\-webui\-react)
+
+Eg
+
+   rclone rc pluginsctl/addPlugin
+
+**Authentication is required for this call.**
+
+### pluginsctl/getPluginsForType: Get plugins with type criteria {#pluginsctl\-getPluginsForType}
+
+This shows all possible plugins by a mime type
+
+This takes the following parameters
+
+\- type: supported mime type by a loaded plugin eg (video/mp4, audio/mp3)
+\- pluginType: filter plugins based on their type eg (DASHBOARD, FILE_HANDLER, TERMINAL) 
+
+and returns
+
+\- loadedPlugins: list of current production plugins
+\- testPlugins: list of temporarily loaded development plugins, usually running on a different server.
+
+Eg
+
+   rclone rc pluginsctl/getPluginsForType type=video/mp4
+
+**Authentication is required for this call.**
+
+### pluginsctl/listPlugins: Get the list of currently loaded plugins {#pluginsctl\-listPlugins}
+
+This allows you to get the currently enabled plugins and their details.
+
+This takes no parameters and returns
+
+\- loadedPlugins: list of current production plugins
+\- testPlugins: list of temporarily loaded development plugins, usually running on a different server.
+
+Eg
+
+   rclone rc pluginsctl/listPlugins
+
+**Authentication is required for this call.**
+
+### pluginsctl/listTestPlugins: Show currently loaded test plugins {#pluginsctl\-listTestPlugins}
+
+allows listing of test plugins with the rclone.test set to true in package.json of the plugin
+
+This takes no parameters and returns
+
+\- loadedTestPlugins: list of currently available test plugins
+
+Eg
+
+    rclone rc pluginsctl/listTestPlugins
+
+**Authentication is required for this call.**
+
+### pluginsctl/removePlugin: Remove a loaded plugin {#pluginsctl\-removePlugin}
+
+This allows you to remove a plugin using it\[aq]s name
+
+This takes parameters
+
+\- name: name of the plugin in the format <author>/<plugin_name>
+
+Eg
+
+   rclone rc pluginsctl/removePlugin name=rclone/video\-plugin
+
+**Authentication is required for this call.**
+
+### pluginsctl/removeTestPlugin: Remove  a test plugin {#pluginsctl\-removeTestPlugin}
+
+This allows you to remove a plugin using it\[aq]s name
+
+This takes the following parameters
+
+\- name: name of the plugin in the format <author>/<plugin_name>
+
+Eg
+
+    rclone rc pluginsctl/removeTestPlugin name=rclone/rclone\-webui\-react
+
+**Authentication is required for this call.**
+
+### rc/error: This returns an error {#rc\-error}
+
 This returns an error with the input as part of its error string.
 Useful for testing error handling.
-.SS rc/list: List all the registered remote control commands
-.PP
+
+### rc/list: List all the registered remote control commands {#rc\-list}
+
 This lists all the registered remote control commands as a JSON map in
 the commands response.
-.SS rc/noop: Echo the input to the output parameters
-.PP
+
+### rc/noop: Echo the input to the output parameters {#rc\-noop}
+
 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.
-.SS rc/noopauth: Echo the input to the output parameters requiring auth
-.PP
+purposes.  It can be used to check that rclone is still alive and to
+check that parameter passing is working properly.
+
+### rc/noopauth: Echo the input to the output parameters requiring auth {#rc\-noopauth}
+
 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.
-.PP
-\f[B]Authentication is required for this call.\f[R]
-.SS sync/copy: copy a directory from source remote to destination remote
-.PP
+purposes.  It can be used to check that rclone is still alive and to
+check that parameter passing is working properly.
+
+**Authentication is required for this call.**
+
+### sync/copy: copy a directory from source remote to destination remote {#sync\-copy}
+
 This takes the following parameters
-.IP \[bu] 2
-srcFs \- a remote name string eg \[lq]drive:src\[rq] for the source
-.IP \[bu] 2
-dstFs \- a remote name string eg \[lq]drive:dst\[rq] for the destination
-.PP
-See the copy command (https://rclone.org/commands/rclone_copy/) command
-for more information on the above.
-.PP
-\f[B]Authentication is required for this call.\f[R]
-.SS sync/move: move a directory from source remote to destination remote
-.PP
+
+\- srcFs \- a remote name string eg \[dq]drive:src\[dq] for the source
+\- dstFs \- a remote name string eg \[dq]drive:dst\[dq] for the destination
+
+
+See the [copy command](https://rclone.org/commands/rclone_copy/) command for more information on the above.
+
+**Authentication is required for this call.**
+
+### sync/move: move a directory from source remote to destination remote {#sync\-move}
+
 This takes the following parameters
-.IP \[bu] 2
-srcFs \- a remote name string eg \[lq]drive:src\[rq] for the source
-.IP \[bu] 2
-dstFs \- a remote name string eg \[lq]drive:dst\[rq] for the destination
-.IP \[bu] 2
-deleteEmptySrcDirs \- delete empty src directories if set
-.PP
-See the move command (https://rclone.org/commands/rclone_move/) command
-for more information on the above.
-.PP
-\f[B]Authentication is required for this call.\f[R]
-.SS sync/sync: sync a directory from source remote to destination remote
-.PP
+
+\- srcFs \- a remote name string eg \[dq]drive:src\[dq] for the source
+\- dstFs \- a remote name string eg \[dq]drive:dst\[dq] for the destination
+\- deleteEmptySrcDirs \- delete empty src directories if set
+
+
+See the [move command](https://rclone.org/commands/rclone_move/) command for more information on the above.
+
+**Authentication is required for this call.**
+
+### sync/sync: sync a directory from source remote to destination remote {#sync\-sync}
+
 This takes the following parameters
-.IP \[bu] 2
-srcFs \- a remote name string eg \[lq]drive:src\[rq] for the source
-.IP \[bu] 2
-dstFs \- a remote name string eg \[lq]drive:dst\[rq] for the destination
-.PP
-See the sync command (https://rclone.org/commands/rclone_sync/) command
-for more information on the above.
-.PP
-\f[B]Authentication is required for this call.\f[R]
-.SS vfs/forget: Forget files or directories in the directory cache.
-.PP
+
+\- srcFs \- a remote name string eg \[dq]drive:src\[dq] for the source
+\- dstFs \- a remote name string eg \[dq]drive:dst\[dq] for the destination
+
+
+See the [sync command](https://rclone.org/commands/rclone_sync/) command for more information on the above.
+
+**Authentication is required for this call.**
+
+### vfs/forget: Forget files or directories in the directory cache. {#vfs\-forget}
+
 This forgets the paths in the directory cache causing them to be
 re\-read from the remote when needed.
-.PP
+
 If no paths are passed in then it will forget all the paths in the
 directory cache.
-.IP
-.nf
-\f[C]
-rclone rc vfs/forget
-\f[R]
-.fi
-.PP
-Otherwise pass files or dirs in as file=path or dir=path.
-Any parameter key starting with file will forget that file and any
+
+    rclone rc vfs/forget
+
+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, eg
-.IP
-.nf
-\f[C]
-rclone rc vfs/forget file=hello file2=goodbye dir=home/junk
-\f[R]
-.fi
-.SS vfs/poll\-interval: Get the status or update the value of the poll\-interval option.
-.PP
+
+    rclone rc vfs/forget file=hello file2=goodbye dir=home/junk
+ 
+This command takes an \[dq]fs\[dq] 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 \[dq]fs\[dq] parameter
+must be supplied.
+
+### vfs/list: List active VFSes. {#vfs\-list}
+
+This lists the active VFSes.
+
+It returns a list under the key \[dq]vfses\[dq] where the values are the VFS
+names that could be passed to the other VFS commands in the \[dq]fs\[dq]
+parameter.
+
+### vfs/poll\-interval: Get the status or update the value of the poll\-interval option. {#vfs\-poll\-interval}
+
 Without any parameter given this returns the current status of the
 poll\-interval setting.
-.PP
-When the interval=duration parameter is set, the poll\-interval value is
-updated and the polling function is notified.
+
+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.
-.IP
-.nf
-\f[C]
-rclone rc vfs/poll\-interval interval=5m
-\f[R]
-.fi
-.PP
-The timeout=duration parameter can be used to specify a time to wait for
-the current poll function to apply the new value.
+
+    rclone rc vfs/poll\-interval interval=5m
+
+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.
-.PP
-The new poll\-interval value will only be active when the timeout is not
-reached.
-.PP
-If poll\-interval is updated or disabled temporarily, some changes might
-not get picked up by the polling function, depending on the used remote.
-.SS vfs/refresh: Refresh the directory cache.
-.PP
+
+The new poll\-interval value will only be active when the timeout is
+not reached.
+
+If poll\-interval is updated or disabled temporarily, some changes
+might not get picked up by the polling function, depending on the
+used remote.
+ 
+This command takes an \[dq]fs\[dq] 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 \[dq]fs\[dq] parameter
+must be supplied.
+
+### vfs/refresh: Refresh the directory cache. {#vfs\-refresh}
+
 This reads the directories for the specified paths and freshens the
 directory cache.
-.PP
+
 If no paths are passed in then it will refresh the root directory.
-.IP
-.nf
-\f[C]
-rclone rc vfs/refresh
-\f[R]
-.fi
-.PP
-Otherwise pass directories in as dir=path.
-Any parameter key starting with dir will refresh that directory, eg
-.IP
-.nf
-\f[C]
-rclone rc vfs/refresh dir=home/junk dir2=data/misc
-\f[R]
-.fi
-.PP
-If the parameter recursive=true is given the whole directory tree will
-get refreshed.
-This refresh will use \[en]fast\-list if enabled.
-.SS Accessing the remote control via HTTP
-.PP
+
+    rclone rc vfs/refresh
+
+Otherwise pass directories in as dir=path. Any parameter key
+starting with dir will refresh that directory, eg
+
+    rclone rc vfs/refresh dir=home/junk dir2=data/misc
+
+If the parameter recursive=true is given the whole directory tree
+will get refreshed. This refresh will use \-\-fast\-list if enabled.
+ 
+This command takes an \[dq]fs\[dq] 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 \[dq]fs\[dq] parameter
+must be supplied.
+
+
+
+## Accessing the remote control via HTTP
+
 Rclone implements a simple HTTP based protocol.
-.PP
+
 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.
-.PP
+error.  The JSON objects are essentially a map of string names to
+values.
+
 All calls must made using POST.
-.PP
-The input objects can be supplied using URL parameters, POST parameters
-or by supplying \[lq]Content\-Type: application/json\[rq] and a JSON
-blob in the body.
-There are examples of these below using \f[C]curl\f[R].
-.PP
-The response will be a JSON blob in the body of the response.
-This is formatted to be reasonably human readable.
-.SS Error returns
-.PP
-If an error occurs then there will be an HTTP error status (eg 500) and
-the body of the response will contain a JSON encoded error object, eg
-.IP
-.nf
-\f[C]
-{
-    \[dq]error\[dq]: \[dq]Expecting string value for key \[rs]\[dq]remote\[rs]\[dq] (was float64)\[dq],
-    \[dq]input\[dq]: {
-        \[dq]fs\[dq]: \[dq]/tmp\[dq],
-        \[dq]remote\[dq]: 3
-    },
-    \[dq]status\[dq]: 400
-    \[dq]path\[dq]: \[dq]operations/rmdir\[dq],
-}
+
+The input objects can be supplied using URL parameters, POST
+parameters or by supplying \[dq]Content\-Type: application/json\[dq] and a JSON
+blob in the body.  There are examples of these below using \[ga]curl\[ga].
+
+The response will be a JSON blob in the body of the response.  This is
+formatted to be reasonably human readable.
+
+### Error returns
+
+If an error occurs then there will be an HTTP error status (eg 500)
+and the body of the response will contain a JSON encoded error object,
+eg
 \f[R]
 .fi
 .PP
-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
-.SS CORS
-.PP
+{ \[dq]error\[dq]: \[dq]Expecting string value for key \[dq]remote\[dq]
+(was float64)\[dq], \[dq]input\[dq]: { \[dq]fs\[dq]: \[dq]/tmp\[dq],
+\[dq]remote\[dq]: 3 }, \[dq]status\[dq]: 400 \[dq]path\[dq]:
+\[dq]operations/rmdir\[dq], }
+.IP
+.nf
+\f[C]
+
+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
+
+### CORS
+
 The sever implements basic CORS support and allows all origins for that.
-The response to a preflight OPTIONS request will echo the requested
-\[lq]Access\-Control\-Request\-Headers\[rq] back.
-.SS Using POST with URL parameters only
-.IP
-.nf
-\f[C]
+The response to a preflight OPTIONS request will echo the requested \[dq]Access\-Control\-Request\-Headers\[dq] back.
+
+### Using POST with URL parameters only
+\f[R]
+.fi
+.PP
 curl \-X POST \[aq]http://localhost:5572/rc/noop?potato=1&sausage=2\[aq]
-\f[R]
-.fi
-.PP
-Response
 .IP
 .nf
 \f[C]
-{
-    \[dq]potato\[dq]: \[dq]1\[dq],
-    \[dq]sausage\[dq]: \[dq]2\[dq]
-}
+
+Response
 \f[R]
 .fi
 .PP
+{ \[dq]potato\[dq]: \[dq]1\[dq], \[dq]sausage\[dq]: \[dq]2\[dq] }
+.IP
+.nf
+\f[C]
+
 Here is what an error response looks like:
-.IP
-.nf
-\f[C]
-curl \-X POST \[aq]http://localhost:5572/rc/error?potato=1&sausage=2\[aq]
-\f[R]
-.fi
-.IP
-.nf
-\f[C]
-{
-    \[dq]error\[dq]: \[dq]arbitrary error on input map[potato:1 sausage:2]\[dq],
-    \[dq]input\[dq]: {
-        \[dq]potato\[dq]: \[dq]1\[dq],
-        \[dq]sausage\[dq]: \[dq]2\[dq]
-    }
-}
 \f[R]
 .fi
 .PP
-Note that curl doesn\[cq]t return errors to the shell unless you use the
-\f[C]\-f\f[R] option
+curl \-X POST
+\[aq]http://localhost:5572/rc/error?potato=1&sausage=2\[aq]
 .IP
 .nf
 \f[C]
-$ curl \-f \-X POST \[aq]http://localhost:5572/rc/error?potato=1&sausage=2\[aq]
-curl: (22) The requested URL returned error: 400 Bad Request
-$ echo $?
+\f[R]
+.fi
+.PP
+{ \[dq]error\[dq]: \[dq]arbitrary error on input map[potato:1
+sausage:2]\[dq], \[dq]input\[dq]: { \[dq]potato\[dq]: \[dq]1\[dq],
+\[dq]sausage\[dq]: \[dq]2\[dq] } }
+.IP
+.nf
+\f[C]
+
+Note that curl doesn\[aq]t return errors to the shell unless you use the \[ga]\-f\[ga] option
+\f[R]
+.fi
+.PP
+$ curl \-f \-X POST
+\[aq]http://localhost:5572/rc/error?potato=1&sausage=2\[aq] curl: (22)
+The requested URL returned error: 400 Bad Request $ echo $?
 22
-\f[R]
-.fi
-.SS Using POST with a form
 .IP
 .nf
 \f[C]
-curl \-\-data \[dq]potato=1\[dq] \-\-data \[dq]sausage=2\[dq] http://localhost:5572/rc/noop
+
+### Using POST with a form
 \f[R]
 .fi
 .PP
+curl \-\-data \[dq]potato=1\[dq] \-\-data \[dq]sausage=2\[dq]
+http://localhost:5572/rc/noop
+.IP
+.nf
+\f[C]
+
 Response
-.IP
-.nf
-\f[C]
-{
-    \[dq]potato\[dq]: \[dq]1\[dq],
-    \[dq]sausage\[dq]: \[dq]2\[dq]
-}
 \f[R]
 .fi
 .PP
+{ \[dq]potato\[dq]: \[dq]1\[dq], \[dq]sausage\[dq]: \[dq]2\[dq] }
+.IP
+.nf
+\f[C]
+
 Note that you can combine these with URL parameters too with the POST
 parameters taking precedence.
-.IP
-.nf
-\f[C]
-curl \-\-data \[dq]potato=1\[dq] \-\-data \[dq]sausage=2\[dq] \[dq]http://localhost:5572/rc/noop?rutabaga=3&sausage=4\[dq]
 \f[R]
 .fi
 .PP
+curl \-\-data \[dq]potato=1\[dq] \-\-data \[dq]sausage=2\[dq]
+\[dq]http://localhost:5572/rc/noop?rutabaga=3&sausage=4\[dq]
+.IP
+.nf
+\f[C]
+
 Response
-.IP
-.nf
-\f[C]
-{
-    \[dq]potato\[dq]: \[dq]1\[dq],
-    \[dq]rutabaga\[dq]: \[dq]3\[dq],
-    \[dq]sausage\[dq]: \[dq]4\[dq]
-}
-\f[R]
-.fi
-.SS Using POST with a JSON blob
-.IP
-.nf
-\f[C]
-curl \-H \[dq]Content\-Type: application/json\[dq] \-X POST \-d \[aq]{\[dq]potato\[dq]:2,\[dq]sausage\[dq]:1}\[aq] http://localhost:5572/rc/noop
 \f[R]
 .fi
 .PP
+{ \[dq]potato\[dq]: \[dq]1\[dq], \[dq]rutabaga\[dq]: \[dq]3\[dq],
+\[dq]sausage\[dq]: \[dq]4\[dq] }
+.IP
+.nf
+\f[C]
+
+### Using POST with a JSON blob
+\f[R]
+.fi
+.PP
+curl \-H \[dq]Content\-Type: application/json\[dq] \-X POST \-d
+\[aq]{\[dq]potato\[dq]:2,\[dq]sausage\[dq]:1}\[aq]
+http://localhost:5572/rc/noop
+.IP
+.nf
+\f[C]
+
 response
-.IP
-.nf
-\f[C]
-{
-    \[dq]password\[dq]: \[dq]xyz\[dq],
-    \[dq]username\[dq]: \[dq]xyz\[dq]
-}
 \f[R]
 .fi
 .PP
-This can be combined with URL parameters too if required.
-The JSON blob takes precedence.
+{ \[dq]password\[dq]: \[dq]xyz\[dq], \[dq]username\[dq]: \[dq]xyz\[dq] }
 .IP
 .nf
 \f[C]
-curl \-H \[dq]Content\-Type: application/json\[dq] \-X POST \-d \[aq]{\[dq]potato\[dq]:2,\[dq]sausage\[dq]:1}\[aq] \[aq]http://localhost:5572/rc/noop?rutabaga=3&potato=4\[aq]
+
+This can be combined with URL parameters too if required.  The JSON
+blob takes precedence.
 \f[R]
 .fi
+.PP
+curl \-H \[dq]Content\-Type: application/json\[dq] \-X POST \-d
+\[aq]{\[dq]potato\[dq]:2,\[dq]sausage\[dq]:1}\[aq]
+\[aq]http://localhost:5572/rc/noop?rutabaga=3&potato=4\[aq]
 .IP
 .nf
 \f[C]
-{
-    \[dq]potato\[dq]: 2,
-    \[dq]rutabaga\[dq]: \[dq]3\[dq],
-    \[dq]sausage\[dq]: 1
-}
 \f[R]
 .fi
-.SS Debugging rclone with pprof
 .PP
-If you use the \f[C]\-\-rc\f[R] flag this will also enable the use of
-the go profiling tools on the same port.
-.PP
-To use these, first install go (https://golang.org/doc/install).
-.SS Debugging memory use
-.PP
-To profile rclone\[cq]s memory use you can run:
+{ \[dq]potato\[dq]: 2, \[dq]rutabaga\[dq]: \[dq]3\[dq],
+\[dq]sausage\[dq]: 1 }
 .IP
 .nf
 \f[C]
-go tool pprof \-web http://localhost:5572/debug/pprof/heap
-\f[R]
-.fi
-.PP
+
+## Debugging rclone with pprof ##
+
+If you use the \[ga]\-\-rc\[ga] flag this will also enable the use of the go
+profiling tools on the same port.
+
+To use these, first [install go](https://golang.org/doc/install).
+
+### Debugging memory use
+
+To profile rclone\[aq]s memory use you can run:
+
+    go tool pprof \-web http://localhost:5572/debug/pprof/heap
+
 This should open a page in your browser showing what is using what
 memory.
+
+You can also use the \[ga]\-text\[ga] flag to produce a textual summary
+\f[R]
+.fi
 .PP
-You can also use the \f[C]\-text\f[R] flag to produce a textual summary
+$ 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.(\f[I]conn).readRequest 0 0% 100% 513kB 33.38%
+net/http.(\f[R]conn).serve 0 0% 100% 1024.03kB 66.62% runtime.main
 .IP
 .nf
 \f[C]
-$ 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
-\f[R]
-.fi
-.SS Debugging go routine leaks
-.PP
+
+### Debugging go routine leaks
+
 Memory leaks are most often caused by go routine leaks keeping memory
 alive which should have been garbage collected.
-.PP
+
 See all active go routines using
-.IP
-.nf
-\f[C]
-curl http://localhost:5572/debug/pprof/goroutine?debug=1
-\f[R]
-.fi
-.PP
-Or go to http://localhost:5572/debug/pprof/goroutine?debug=1 in your
-browser.
-.SS Other profiles to look at
-.PP
-You can see a summary of profiles available at
-http://localhost:5572/debug/pprof/
-.PP
+
+    curl http://localhost:5572/debug/pprof/goroutine?debug=1
+
+Or go to http://localhost:5572/debug/pprof/goroutine?debug=1 in your browser.
+
+### Other profiles to look at
+
+You can see a summary of profiles available at http://localhost:5572/debug/pprof/
+
 Here is how to use some of them:
-.IP \[bu] 2
-Memory: \f[C]go tool pprof http://localhost:5572/debug/pprof/heap\f[R]
-.IP \[bu] 2
-Go routines:
-\f[C]curl http://localhost:5572/debug/pprof/goroutine?debug=1\f[R]
-.IP \[bu] 2
-30\-second CPU profile:
-\f[C]go tool pprof http://localhost:5572/debug/pprof/profile\f[R]
-.IP \[bu] 2
-5\-second execution trace:
-\f[C]wget http://localhost:5572/debug/pprof/trace?seconds=5\f[R]
-.IP \[bu] 2
-Goroutine blocking profile
-.RS 2
-.IP \[bu] 2
-Enable first with:
-\f[C]rclone rc debug/set\-block\-profile\-rate rate=1\f[R] (docs)
-.IP \[bu] 2
-\f[C]go tool pprof http://localhost:5572/debug/pprof/block\f[R]
-.RE
-.IP \[bu] 2
-Contended mutexes:
-.RS 2
-.IP \[bu] 2
-Enable first with:
-\f[C]rclone rc debug/set\-mutex\-profile\-fraction rate=1\f[R] (docs)
-.IP \[bu] 2
-\f[C]go tool pprof http://localhost:5572/debug/pprof/mutex\f[R]
-.RE
-.PP
-See the net/http/pprof docs (https://golang.org/pkg/net/http/pprof/) for
-more info on how to use the profiling and for a general overview see the
-Go team\[cq]s blog post on profiling go
-programs (https://blog.golang.org/profiling-go-programs).
-.PP
-The profiling hook is zero overhead unless it is
-used (https://stackoverflow.com/q/26545159/164234).
-.SH Overview of cloud storage systems
-.PP
-Each cloud storage system is slightly different.
-Rclone attempts to provide a unified interface to them, but some
-underlying differences show through.
-.SS Features
-.PP
+
+\- Memory: \[ga]go tool pprof http://localhost:5572/debug/pprof/heap\[ga]
+\- Go routines: \[ga]curl http://localhost:5572/debug/pprof/goroutine?debug=1\[ga]
+\- 30\-second CPU profile: \[ga]go tool pprof http://localhost:5572/debug/pprof/profile\[ga]
+\- 5\-second execution trace: \[ga]wget http://localhost:5572/debug/pprof/trace?seconds=5\[ga]
+\- Goroutine blocking profile
+    \- Enable first with: \[ga]rclone rc debug/set\-block\-profile\-rate rate=1\[ga] ([docs](#debug/set\-block\-profile\-rate))
+    \- \[ga]go tool pprof http://localhost:5572/debug/pprof/block\[ga]
+\- Contended mutexes:
+    \- Enable first with: \[ga]rclone rc debug/set\-mutex\-profile\-fraction rate=1\[ga] ([docs](#debug/set\-mutex\-profile\-fraction))
+    \- \[ga]go tool pprof http://localhost:5572/debug/pprof/mutex\[ga]
+
+See the [net/http/pprof docs](https://golang.org/pkg/net/http/pprof/)
+for more info on how to use the profiling and for a general overview
+see [the Go team\[aq]s blog post on profiling go programs](https://blog.golang.org/profiling\-go\-programs).
+
+The profiling hook is [zero overhead unless it is used](https://stackoverflow.com/q/26545159/164234).
+
+# Overview of cloud storage systems #
+
+Each cloud storage system is slightly different.  Rclone attempts to
+provide a unified interface to them, but some underlying differences
+show through.
+
+## Features ##
+
 Here is an overview of the major features of each cloud storage system.
-.PP
-.TS
-tab(@);
-l c c c c c.
-T{
-Name
-T}@T{
-Hash
-T}@T{
-ModTime
-T}@T{
-Case Insensitive
-T}@T{
-Duplicate Files
-T}@T{
-MIME Type
-T}
-_
-T{
-1Fichier
-T}@T{
-Whirlpool
-T}@T{
-No
-T}@T{
-No
-T}@T{
-Yes
-T}@T{
-R
-T}
-T{
-Amazon Drive
-T}@T{
-MD5
-T}@T{
-No
-T}@T{
-Yes
-T}@T{
-No
-T}@T{
-R
-T}
-T{
-Amazon S3
-T}@T{
-MD5
-T}@T{
-Yes
-T}@T{
-No
-T}@T{
-No
-T}@T{
-R/W
-T}
-T{
-Backblaze B2
-T}@T{
-SHA1
-T}@T{
-Yes
-T}@T{
-No
-T}@T{
-No
-T}@T{
-R/W
-T}
-T{
-Box
-T}@T{
-SHA1
-T}@T{
-Yes
-T}@T{
-Yes
-T}@T{
-No
-T}@T{
-\-
-T}
-T{
-Citrix ShareFile
-T}@T{
-MD5
-T}@T{
-Yes
-T}@T{
-Yes
-T}@T{
-No
-T}@T{
-\-
-T}
-T{
-Dropbox
-T}@T{
-DBHASH \[dg]
-T}@T{
-Yes
-T}@T{
-Yes
-T}@T{
-No
-T}@T{
-\-
-T}
-T{
-FTP
-T}@T{
-\-
-T}@T{
-No
-T}@T{
-No
-T}@T{
-No
-T}@T{
-\-
-T}
-T{
-Google Cloud Storage
-T}@T{
-MD5
-T}@T{
-Yes
-T}@T{
-No
-T}@T{
-No
-T}@T{
-R/W
-T}
-T{
-Google Drive
-T}@T{
-MD5
-T}@T{
-Yes
-T}@T{
-No
-T}@T{
-Yes
-T}@T{
-R/W
-T}
-T{
-Google Photos
-T}@T{
-\-
-T}@T{
-No
-T}@T{
-No
-T}@T{
-Yes
-T}@T{
-R
-T}
-T{
-HTTP
-T}@T{
-\-
-T}@T{
-No
-T}@T{
-No
-T}@T{
-No
-T}@T{
-R
-T}
-T{
-Hubic
-T}@T{
-MD5
-T}@T{
-Yes
-T}@T{
-No
-T}@T{
-No
-T}@T{
-R/W
-T}
-T{
-Jottacloud
-T}@T{
-MD5
-T}@T{
-Yes
-T}@T{
-Yes
-T}@T{
-No
-T}@T{
-R/W
-T}
-T{
-Koofr
-T}@T{
-MD5
-T}@T{
-No
-T}@T{
-Yes
-T}@T{
-No
-T}@T{
-\-
-T}
-T{
-Mail.ru Cloud
-T}@T{
-Mailru \[dd]\[dd]\[dd]
-T}@T{
-Yes
-T}@T{
-Yes
-T}@T{
-No
-T}@T{
-\-
-T}
-T{
-Mega
-T}@T{
-\-
-T}@T{
-No
-T}@T{
-No
-T}@T{
-Yes
-T}@T{
-\-
-T}
-T{
-Memory
-T}@T{
-MD5
-T}@T{
-Yes
-T}@T{
-No
-T}@T{
-No
-T}@T{
-\-
-T}
-T{
-Microsoft Azure Blob Storage
-T}@T{
-MD5
-T}@T{
-Yes
-T}@T{
-No
-T}@T{
-No
-T}@T{
-R/W
-T}
-T{
-Microsoft OneDrive
-T}@T{
-SHA1 \[dd]\[dd]
-T}@T{
-Yes
-T}@T{
-Yes
-T}@T{
-No
-T}@T{
-R
-T}
-T{
-OpenDrive
-T}@T{
-MD5
-T}@T{
-Yes
-T}@T{
-Yes
-T}@T{
-No
-T}@T{
-\-
-T}
-T{
-OpenStack Swift
-T}@T{
-MD5
-T}@T{
-Yes
-T}@T{
-No
-T}@T{
-No
-T}@T{
-R/W
-T}
-T{
-pCloud
-T}@T{
-MD5, SHA1
-T}@T{
-Yes
-T}@T{
-No
-T}@T{
-No
-T}@T{
-W
-T}
-T{
-premiumize.me
-T}@T{
-\-
-T}@T{
-No
-T}@T{
-Yes
-T}@T{
-No
-T}@T{
-R
-T}
-T{
-put.io
-T}@T{
-CRC\-32
-T}@T{
-Yes
-T}@T{
-No
-T}@T{
-Yes
-T}@T{
-R
-T}
-T{
-QingStor
-T}@T{
-MD5
-T}@T{
-No
-T}@T{
-No
-T}@T{
-No
-T}@T{
-R/W
-T}
-T{
-Seafile
-T}@T{
-\-
-T}@T{
-No
-T}@T{
-No
-T}@T{
-No
-T}@T{
-\-
-T}
-T{
-SFTP
-T}@T{
-MD5, SHA1 \[dd]
-T}@T{
-Yes
-T}@T{
-Depends
-T}@T{
-No
-T}@T{
-\-
-T}
-T{
-SugarSync
-T}@T{
-\-
-T}@T{
-No
-T}@T{
-No
-T}@T{
-No
-T}@T{
-\-
-T}
-T{
-Tardigrade
-T}@T{
-\-
-T}@T{
-Yes
-T}@T{
-No
-T}@T{
-No
-T}@T{
-\-
-T}
-T{
-WebDAV
-T}@T{
-MD5, SHA1 \[dg]\[dg]
-T}@T{
-Yes \[dg]\[dg]\[dg]
-T}@T{
-Depends
-T}@T{
-No
-T}@T{
-\-
-T}
-T{
-Yandex Disk
-T}@T{
-MD5
-T}@T{
-Yes
-T}@T{
-No
-T}@T{
-No
-T}@T{
-R/W
-T}
-T{
-The local filesystem
-T}@T{
-All
-T}@T{
-Yes
-T}@T{
-Depends
-T}@T{
-No
-T}@T{
-\-
-T}
-.TE
-.SS Hash
-.PP
+
+| Name                         | Hash        | ModTime | Case Insensitive | Duplicate Files | MIME Type |
+| \-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\- |:\-\-\-\-\-\-\-\-\-\-\-:|:\-\-\-\-\-\-\-:|:\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-:|:\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-:|:\-\-\-\-\-\-\-\-\-:|
+| 1Fichier                     | Whirlpool   | No      | No               | Yes             | R         |
+| Amazon Drive                 | MD5         | No      | Yes              | No              | R         |
+| Amazon S3                    | MD5         | Yes     | No               | No              | R/W       |
+| Backblaze B2                 | SHA1        | Yes     | No               | No              | R/W       |
+| Box                          | SHA1        | Yes     | Yes              | No              | \-         |
+| Citrix ShareFile             | MD5         | Yes     | Yes              | No              | \-         |
+| Dropbox                      | DBHASH \[dg]    | Yes     | Yes              | No              | \-         |
+| FTP                          | \-           | No      | No               | No              | \-         |
+| Google Cloud Storage         | MD5         | Yes     | No               | No              | R/W       |
+| Google Drive                 | MD5         | Yes     | No               | Yes             | R/W       |
+| Google Photos                | \-           | No      | No               | Yes             | R         |
+| HTTP                         | \-           | No      | No               | No              | R         |
+| Hubic                        | MD5         | Yes     | No               | No              | R/W       |
+| Jottacloud                   | MD5         | Yes     | Yes              | No              | R/W       |
+| Koofr                        | MD5         | No      | Yes              | No              | \-         |
+| Mail.ru Cloud                | Mailru \[dd]\[dd]\[dd]  | Yes     | Yes              | No              | \-         |
+| Mega                         | \-           | No      | No               | Yes             | \-         |
+| Memory                       | MD5         | Yes     | No               | No              | \-         |
+| Microsoft Azure Blob Storage | MD5         | Yes     | No               | No              | R/W       |
+| Microsoft OneDrive           | SHA1 \[dd]\[dd]     | Yes     | Yes              | No              | R         |
+| OpenDrive                    | MD5         | Yes     | Yes              | Partial \[rs]*      | \-         |
+| OpenStack Swift              | MD5         | Yes     | No               | No              | R/W       |
+| pCloud                       | MD5, SHA1   | Yes     | No               | No              | W         |
+| premiumize.me                | \-           | No      | Yes              | No              | R         |
+| put.io                       | CRC\-32      | Yes     | No               | Yes             | R         |
+| QingStor                     | MD5         | No      | No               | No              | R/W       |
+| Seafile                      | \-           | No      | No               | No              | \-         |
+| SFTP                         | MD5, SHA1 \[dd] | Yes     | Depends          | No              | \-         |
+| SugarSync                    | \-           | No      | No               | No              | \-         |
+| Tardigrade                   | \-           | Yes     | No               | No              | \-         |
+| WebDAV                       | MD5, SHA1 \[dg]\[dg]| Yes \[dg]\[dg]\[dg] | Depends          | No              | \-         |
+| Yandex Disk                  | MD5         | Yes     | No               | No              | R/W       |
+| The local filesystem         | All         | Yes     | Depends          | No              | \-         |
+
+### Hash ###
+
 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 \f[C]\-\-checksum\f[R] flag in syncs and
-in the \f[C]check\f[R] command.
-.PP
+The hashes are used when transferring data as an integrity check and
+can be specifically used with the \[ga]\-\-checksum\[ga] flag in syncs and in
+the \[ga]check\[ga] command.
+
 To use the verify checksums when transferring between cloud storage
 systems they must support a common hash type.
-.PP
-\[dg] Note that Dropbox supports its own custom
-hash (https://www.dropbox.com/developers/reference/content-hash).
+
+\[dg] Note that Dropbox supports [its own custom
+hash](https://www.dropbox.com/developers/reference/content\-hash).
 This is an SHA256 sum of all the 4MB block SHA256s.
-.PP
-\[dd] SFTP supports checksums if the same login has shell access and
-\f[C]md5sum\f[R] or \f[C]sha1sum\f[R] as well as \f[C]echo\f[R] are in
-the remote\[cq]s PATH.
-.PP
-\[dg]\[dg] WebDAV supports hashes when used with Owncloud and Nextcloud
-only.
-.PP
-\[dg]\[dg]\[dg] WebDAV supports modtimes when used with Owncloud and
-Nextcloud only.
-.PP
-\[dd]\[dd] Microsoft OneDrive Personal supports SHA1 hashes, whereas
-OneDrive for business and SharePoint server support Microsoft\[cq]s own
-QuickXorHash (https://docs.microsoft.com/en-us/onedrive/developer/code-snippets/quickxorhash).
-.PP
+
+\[dd] SFTP supports checksums if the same login has shell access and \[ga]md5sum\[ga]
+or \[ga]sha1sum\[ga] as well as \[ga]echo\[ga] are in the remote\[aq]s PATH.
+
+\[dg]\[dg] WebDAV supports hashes when used with Owncloud and Nextcloud only.
+
+\[dg]\[dg]\[dg] WebDAV supports modtimes when used with Owncloud and Nextcloud only.
+
+\[dd]\[dd] Microsoft OneDrive Personal supports SHA1 hashes, whereas OneDrive
+for business and SharePoint server support Microsoft\[aq]s own
+[QuickXorHash](https://docs.microsoft.com/en\-us/onedrive/developer/code\-snippets/quickxorhash).
+
 \[dd]\[dd]\[dd] Mail.ru uses its own modified SHA1 hash
-.SS ModTime
-.PP
-The cloud storage system supports setting modification times on objects.
-If it does then this enables a using the modification times as part of
-the sync.
-If not then only the size will be checked by default, though the MD5SUM
-can be checked with the \f[C]\-\-checksum\f[R] flag.
-.PP
+
+### ModTime ###
+
+The cloud storage system supports setting modification times on
+objects.  If it does then this enables a using the modification times
+as part of the sync.  If not then only the size will be checked by
+default, though the MD5SUM can be checked with the \[ga]\-\-checksum\[ga] flag.
+
 All cloud storage systems support some kind of date on the object and
 these will be set when transferring from the cloud storage system.
-.SS Case Insensitive
-.PP
-If a cloud storage systems is case sensitive then it is possible to have
-two files which differ only in case, eg \f[C]file.txt\f[R] and
-\f[C]FILE.txt\f[R].
-If a cloud storage system is case insensitive then that isn\[cq]t
-possible.
-.PP
-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.
-.PP
-The local filesystem and SFTP may or may not be case sensitive depending
-on OS.
-.IP \[bu] 2
-Windows \- usually case insensitive, though case is preserved
-.IP \[bu] 2
-OSX \- usually case insensitive, though it is possible to format case
-sensitive
-.IP \[bu] 2
-Linux \- usually case sensitive, but there are case insensitive file
-systems (eg FAT formatted USB keys)
-.PP
-Most of the time this doesn\[cq]t cause any problems as people tend to
+
+### Case Insensitive ###
+
+If a cloud storage systems is case sensitive then it is possible to
+have two files which differ only in case, eg \[ga]file.txt\[ga] and
+\[ga]FILE.txt\[ga].  If a cloud storage system is case insensitive then that
+isn\[aq]t possible.
+
+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.
+
+The local filesystem and SFTP may or may not be case sensitive
+depending on OS.
+
+  * Windows \- usually case insensitive, though case is preserved
+  * OSX \- usually case insensitive, though it is possible to format case sensitive
+  * Linux \- usually case sensitive, but there are case insensitive file systems (eg FAT formatted USB keys)
+
+Most of the time this doesn\[aq]t cause any problems as people tend to
 avoid files whose name differs only by case even on case sensitive
 systems.
-.SS Duplicate files
-.PP
+
+### Duplicate files ###
+
 If a cloud storage system allows duplicate files then it can have two
 objects with the same name.
-.PP
-This confuses rclone greatly when syncing \- use the
-\f[C]rclone dedupe\f[R] command to rename or remove duplicates.
-.SS Restricted filenames
-.PP
+
+This confuses rclone greatly when syncing \- use the \[ga]rclone dedupe\[ga]
+command to rename or remove duplicates.
+
+\[rs]* 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 \[ga]rclone\[ga].  It may be that this is a
+mistake or an unsupported feature.
+
+### Restricted filenames ###
+
 Some cloud storage systems might have restrictions on the characters
 that are usable in file or directory names.
-When \f[C]rclone\f[R] detects such a name during a file upload, it will
+When \[ga]rclone\[ga] detects such a name during a file upload, it will
 transparently replace the restricted characters with similar looking
 Unicode characters.
-.PP
+
 This process is designed to avoid ambiguous file names as much as
 possible and allow to move files between many cloud storage systems
 transparently.
-.PP
-The name shown by \f[C]rclone\f[R] to the user or during log output will
-only contain a minimal set of replaced characters to ensure correct
-formatting and not necessarily the actual name used on the cloud
-storage.
-.PP
+
+The name shown by \[ga]rclone\[ga] to the user or during log output will only
+contain a minimal set of [replaced characters](#restricted\-characters)
+to ensure correct formatting and not necessarily the actual name used
+on the cloud storage.
+
 This transformation is reversed when downloading a file or parsing
-\f[C]rclone\f[R] arguments.
-For example, when uploading a file named \f[C]my file?.txt\f[R] to
-Onedrive will be displayed as \f[C]my file?.txt\f[R] on the console, but
-stored as \f[C]my file\[uFF1F].txt\f[R] (the \f[C]?\f[R] gets replaced
-by the similar looking \f[C]\[uFF1F]\f[R] character) to Onedrive.
-The reverse transformation allows to read a
-file\f[C]unusual/name.txt\f[R] from Google Drive, by passing the name
-\f[C]unusual\[uFF0F]name.txt\f[R] (the \f[C]/\f[R] needs to be replaced
-by the similar looking \f[C]\[uFF0F]\f[R] character) on the command
-line.
-.SS Default restricted characters
-.PP
+\[ga]rclone\[ga] arguments.
+For example, when uploading a file named \[ga]my file?.txt\[ga] to Onedrive
+will be displayed as \[ga]my file?.txt\[ga] on the console, but stored as
+\[ga]my file\[uFF1F].txt\[ga] (the \[ga]?\[ga] gets replaced by the similar looking \[ga]\[uFF1F]\[ga]
+character) to Onedrive.
+The reverse transformation allows to read a file\[ga]unusual/name.txt\[ga]
+from Google Drive, by passing the name \[ga]unusual\[uFF0F]name.txt\[ga] (the \[ga]/\[ga] needs
+to be replaced by the similar looking \[ga]\[uFF0F]\[ga] character) on the command line.
+
+#### Default restricted characters {#restricted\-characters}
+
 The table below shows the characters that are replaced by default.
-.PP
-When a replacement character is found in a filename, this character will
-be escaped with the \f[C]\[u201B]\f[R] character to avoid ambiguous file
-names.
-(e.g.\ a file named \f[C]\[u2400].txt\f[R] would shown as
-\f[C]\[u201B]\[u2400].txt\f[R])
-.PP
-Each cloud storage backend can use a different set of characters, which
-will be specified in the documentation for each backend.
-.PP
-.TS
-tab(@);
-l c c.
-T{
-Character
-T}@T{
-Value
-T}@T{
-Replacement
-T}
-_
-T{
-NUL
-T}@T{
-0x00
-T}@T{
-\[u2400]
-T}
-T{
-SOH
-T}@T{
-0x01
-T}@T{
-\[u2401]
-T}
-T{
-STX
-T}@T{
-0x02
-T}@T{
-\[u2402]
-T}
-T{
-ETX
-T}@T{
-0x03
-T}@T{
-\[u2403]
-T}
-T{
-EOT
-T}@T{
-0x04
-T}@T{
-\[u2404]
-T}
-T{
-ENQ
-T}@T{
-0x05
-T}@T{
-\[u2405]
-T}
-T{
-ACK
-T}@T{
-0x06
-T}@T{
-\[u2406]
-T}
-T{
-BEL
-T}@T{
-0x07
-T}@T{
-\[u2407]
-T}
-T{
-BS
-T}@T{
-0x08
-T}@T{
-\[u2408]
-T}
-T{
-HT
-T}@T{
-0x09
-T}@T{
-\[u2409]
-T}
-T{
-LF
-T}@T{
-0x0A
-T}@T{
-\[u240A]
-T}
-T{
-VT
-T}@T{
-0x0B
-T}@T{
-\[u240B]
-T}
-T{
-FF
-T}@T{
-0x0C
-T}@T{
-\[u240C]
-T}
-T{
-CR
-T}@T{
-0x0D
-T}@T{
-\[u240D]
-T}
-T{
-SO
-T}@T{
-0x0E
-T}@T{
-\[u240E]
-T}
-T{
-SI
-T}@T{
-0x0F
-T}@T{
-\[u240F]
-T}
-T{
-DLE
-T}@T{
-0x10
-T}@T{
-\[u2410]
-T}
-T{
-DC1
-T}@T{
-0x11
-T}@T{
-\[u2411]
-T}
-T{
-DC2
-T}@T{
-0x12
-T}@T{
-\[u2412]
-T}
-T{
-DC3
-T}@T{
-0x13
-T}@T{
-\[u2413]
-T}
-T{
-DC4
-T}@T{
-0x14
-T}@T{
-\[u2414]
-T}
-T{
-NAK
-T}@T{
-0x15
-T}@T{
-\[u2415]
-T}
-T{
-SYN
-T}@T{
-0x16
-T}@T{
-\[u2416]
-T}
-T{
-ETB
-T}@T{
-0x17
-T}@T{
-\[u2417]
-T}
-T{
-CAN
-T}@T{
-0x18
-T}@T{
-\[u2418]
-T}
-T{
-EM
-T}@T{
-0x19
-T}@T{
-\[u2419]
-T}
-T{
-SUB
-T}@T{
-0x1A
-T}@T{
-\[u241A]
-T}
-T{
-ESC
-T}@T{
-0x1B
-T}@T{
-\[u241B]
-T}
-T{
-FS
-T}@T{
-0x1C
-T}@T{
-\[u241C]
-T}
-T{
-GS
-T}@T{
-0x1D
-T}@T{
-\[u241D]
-T}
-T{
-RS
-T}@T{
-0x1E
-T}@T{
-\[u241E]
-T}
-T{
-US
-T}@T{
-0x1F
-T}@T{
-\[u241F]
-T}
-T{
-/
-T}@T{
-0x2F
-T}@T{
-\[uFF0F]
-T}
-T{
-DEL
-T}@T{
-0x7F
-T}@T{
-\[u2421]
-T}
-.TE
-.PP
+
+When a replacement character is found in a filename, this character
+will be escaped with the \[ga]\[u201B]\[ga] character to avoid ambiguous file names.
+(e.g. a file named \[ga]\[u2400].txt\[ga] would shown as \[ga]\[u201B]\[u2400].txt\[ga])
+
+Each cloud storage backend can use a different set of characters,
+which will be specified in the documentation for each backend.
+
+| Character | Value | Replacement |
+| \-\-\-\-\-\-\-\-\- |:\-\-\-\-\-:|:\-\-\-\-\-\-\-\-\-\-\-:|
+| NUL       | 0x00  | \[u2400]           |
+| SOH       | 0x01  | \[u2401]           |
+| STX       | 0x02  | \[u2402]           |
+| ETX       | 0x03  | \[u2403]           |
+| EOT       | 0x04  | \[u2404]           |
+| ENQ       | 0x05  | \[u2405]           |
+| ACK       | 0x06  | \[u2406]           |
+| BEL       | 0x07  | \[u2407]           |
+| BS        | 0x08  | \[u2408]           |
+| HT        | 0x09  | \[u2409]           |
+| LF        | 0x0A  | \[u240A]           |
+| VT        | 0x0B  | \[u240B]           |
+| FF        | 0x0C  | \[u240C]           |
+| CR        | 0x0D  | \[u240D]           |
+| SO        | 0x0E  | \[u240E]           |
+| SI        | 0x0F  | \[u240F]           |
+| DLE       | 0x10  | \[u2410]           |
+| DC1       | 0x11  | \[u2411]           |
+| DC2       | 0x12  | \[u2412]           |
+| DC3       | 0x13  | \[u2413]           |
+| DC4       | 0x14  | \[u2414]           |
+| NAK       | 0x15  | \[u2415]           |
+| SYN       | 0x16  | \[u2416]           |
+| ETB       | 0x17  | \[u2417]           |
+| CAN       | 0x18  | \[u2418]           |
+| EM        | 0x19  | \[u2419]           |
+| SUB       | 0x1A  | \[u241A]           |
+| ESC       | 0x1B  | \[u241B]           |
+| FS        | 0x1C  | \[u241C]           |
+| GS        | 0x1D  | \[u241D]           |
+| RS        | 0x1E  | \[u241E]           |
+| US        | 0x1F  | \[u241F]           |
+| /         | 0x2F  | \[uFF0F]           |
+| DEL       | 0x7F  | \[u2421]           |
+
 The default encoding will also encode these file names as they are
 problematic with many cloud storage systems.
-.PP
-.TS
-tab(@);
-l c.
-T{
-File name
-T}@T{
-Replacement
-T}
-_
-T{
-\&.
-T}@T{
-\[uFF0E]
-T}
-T{
-\&..
-T}@T{
-\[uFF0E]\[uFF0E]
-T}
-.TE
-.SS Invalid UTF\-8 bytes
-.PP
-Some backends only support a sequence of well formed UTF\-8 bytes as
-file or directory names.
-.PP
+
+| File name | Replacement |
+| \-\-\-\-\-\-\-\-\- |:\-\-\-\-\-\-\-\-\-\-\-:|
+| .         | \[uFF0E]          |
+| ..        | \[uFF0E]\[uFF0E]         |
+
+#### Invalid UTF\-8 bytes {#invalid\-utf8}
+
+Some backends only support a sequence of well formed UTF\-8 bytes
+as file or directory names.
+
 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 \f[C]0xFE\f[R] will be encoded as
-\f[C]\[u201B]FE\f[R].
-.PP
-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 local filenames (https://rclone.org/local/#filenames) section
-for details.
-.SS Encoding option
-.PP
+backend. For example, the invalid byte \[ga]0xFE\[ga] will be encoded as \[ga]\[u201B]FE\[ga].
+
+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
+[local filenames](https://rclone.org/local/#filenames) section for details.
+
+#### Encoding option {#encoding}
+
 Most backends have an encoding options, specified as a flag
-\f[C]\-\-backend\-encoding\f[R] where \f[C]backend\f[R] is the name of
-the backend, or as a config parameter \f[C]encoding\f[R] (you\[cq]ll
-need to select the Advanced config in \f[C]rclone config\f[R] to see
-it).
-.PP
+\[ga]\-\-backend\-encoding\[ga] where \[ga]backend\[ga] is the name of the backend, or as
+a config parameter \[ga]encoding\[ga] (you\[aq]ll need to select the Advanced
+config in \[ga]rclone config\[ga] to see it).
+
 This will have default value which encodes and decodes characters in
-such a way as to preserve the maximum number of characters (see above).
-.PP
-However this can be incorrect in some scenarios, for example if you have
-a Windows file system with characters such as \f[C]\[uFF0A]\f[R] and
-\f[C]\[uFF1F]\f[R] that you want to remain as those characters on the
-remote rather than being translated to \f[C]*\f[R] and \f[C]?\f[R].
-.PP
-The \f[C]\-\-backend\-encoding\f[R] flags allow you to change that.
-You can disable the encoding completely with
-\f[C]\-\-backend\-encoding None\f[R] or set \f[C]encoding = None\f[R] in
-the config file.
-.PP
-Encoding takes a comma separated list of encodings.
-You can see the list of all available characters by passing an invalid
-value to this flag, eg \f[C]\-\-local\-encoding \[dq]help\[dq]\f[R] and
-\f[C]rclone help flags encoding\f[R] will show you the defaults for the
-backends.
-.PP
-.TS
-tab(@);
-l l.
-T{
-Encoding
-T}@T{
-Characters
-T}
-_
-T{
-Asterisk
-T}@T{
-\f[C]*\f[R]
-T}
-T{
-BackQuote
-T}@T{
-\f[C]\[ga]\f[R]
-T}
-T{
-BackSlash
-T}@T{
-\f[C]\[rs]\f[R]
-T}
-T{
-Colon
-T}@T{
-\f[C]:\f[R]
-T}
-T{
-CrLf
-T}@T{
-CR 0x0D, LF 0x0A
-T}
-T{
-Ctl
-T}@T{
-All control characters 0x00\-0x1F
-T}
-T{
-Del
-T}@T{
-DEL 0x7F
-T}
-T{
-Dollar
-T}@T{
-\f[C]$\f[R]
-T}
-T{
-Dot
-T}@T{
-\f[C].\f[R]
-T}
-T{
-DoubleQuote
-T}@T{
-\f[C]\[dq]\f[R]
-T}
-T{
-Hash
-T}@T{
-\f[C]#\f[R]
-T}
-T{
-InvalidUtf8
-T}@T{
-An invalid UTF\-8 character (eg latin1)
-T}
-T{
-LeftCrLfHtVt
-T}@T{
-CR 0x0D, LF 0x0A,HT 0x09, VT 0x0B on the left of a string
-T}
-T{
-LeftPeriod
-T}@T{
-\f[C].\f[R] on the left of a string
-T}
-T{
-LeftSpace
-T}@T{
-SPACE on the left of a string
-T}
-T{
-LeftTilde
-T}@T{
-\f[C]\[ti]\f[R] on the left of a string
-T}
-T{
-LtGt
-T}@T{
-\f[C]<\f[R], \f[C]>\f[R]
-T}
-T{
-None
-T}@T{
-No characters are encoded
-T}
-T{
-Percent
-T}@T{
-\f[C]%\f[R]
-T}
-T{
-Pipe
-T}@T{
-|
-T}
-T{
-Question
-T}@T{
-\f[C]?\f[R]
-T}
-T{
-RightCrLfHtVt
-T}@T{
-CR 0x0D, LF 0x0A, HT 0x09, VT 0x0B on the right of a string
-T}
-T{
-RightPeriod
-T}@T{
-\f[C].\f[R] on the right of a string
-T}
-T{
-RightSpace
-T}@T{
-SPACE on the right of a string
-T}
-T{
-SingleQuote
-T}@T{
-\f[C]\[aq]\f[R]
-T}
-T{
-Slash
-T}@T{
-\f[C]/\f[R]
-T}
-.TE
-.PP
-To take a specific example, the FTP backend\[cq]s default encoding is
-.IP
-.nf
-\f[C]
-\-\-ftp\-encoding \[dq]Slash,Del,Ctl,RightSpace,Dot\[dq]
-\f[R]
-.fi
-.PP
-However, let\[cq]s say the FTP server is running on Windows and
-can\[cq]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
-.IP
-.nf
-\f[C]
-Slash,LtGt,DoubleQuote,Colon,Question,Asterisk,Pipe,BackSlash,Ctl,RightSpace,RightPeriod,InvalidUtf8,Dot
-\f[R]
-.fi
-.PP
+such a way as to preserve the maximum number of characters (see
+above).
+
+However this can be incorrect in some scenarios, for example if you
+have a Windows file system with characters such as \[ga]\[uFF0A]\[ga] and \[ga]\[uFF1F]\[ga] that
+you want to remain as those characters on the remote rather than being
+translated to \[ga]*\[ga] and \[ga]?\[ga].
+
+The \[ga]\-\-backend\-encoding\[ga] flags allow you to change that. You can
+disable the encoding completely with \[ga]\-\-backend\-encoding None\[ga] or set
+\[ga]encoding = None\[ga] in the config file.
+
+Encoding takes a comma separated list of encodings. You can see the
+list of all available characters by passing an invalid value to this
+flag, eg \[ga]\-\-local\-encoding \[dq]help\[dq]\[ga] and \[ga]rclone help flags encoding\[ga]
+will show you the defaults for the backends.
+
+| Encoding  | Characters |
+| \-\-\-\-\-\-\-\-\- | \-\-\-\-\-\-\-\-\-\- |
+| Asterisk | \[ga]*\[ga] |
+| BackQuote | \[ga]\[ga] \[ga] \[ga]\[ga] |
+| BackSlash | \[ga]\[rs]\[ga] |
+| Colon | \[ga]:\[ga] |
+| CrLf | CR 0x0D, LF 0x0A |
+| Ctl | All control characters 0x00\-0x1F |
+| Del | DEL 0x7F |
+| Dollar | \[ga]$\[ga] |
+| Dot | \[ga].\[ga] |
+| DoubleQuote | \[ga]\[dq]\[ga] |
+| Hash | \[ga]#\[ga] |
+| InvalidUtf8 | An invalid UTF\-8 character (eg latin1) |
+| LeftCrLfHtVt | CR 0x0D, LF 0x0A,HT 0x09, VT 0x0B on the left of a string |
+| LeftPeriod | \[ga].\[ga] on the left of a string |
+| LeftSpace | SPACE on the left of a string |
+| LeftTilde | \[ga]\[ti]\[ga] on the left of a string |
+| LtGt | \[ga]<\[ga], \[ga]>\[ga] |
+| None | No characters are encoded |
+| Percent | \[ga]%\[ga] |
+| Pipe | \[rs]| |
+| Question | \[ga]?\[ga] |
+| RightCrLfHtVt | CR 0x0D, LF 0x0A, HT 0x09, VT 0x0B on the right of a string |
+| RightPeriod | \[ga].\[ga] on the right of a string |
+| RightSpace | SPACE on the right of a string |
+| SingleQuote | \[ga]\[aq]\[ga] |
+| Slash | \[ga]/\[ga] |
+
+To take a specific example, the FTP backend\[aq]s default encoding is
+
+    \-\-ftp\-encoding \[dq]Slash,Del,Ctl,RightSpace,Dot\[dq]
+
+However, let\[aq]s say the FTP server is running on Windows and can\[aq]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
+
+    Slash,LtGt,DoubleQuote,Colon,Question,Asterisk,Pipe,BackSlash,Ctl,RightSpace,RightPeriod,InvalidUtf8,Dot
+
 to the existing ones, giving:
-.IP
-.nf
-\f[C]
-Slash,LtGt,DoubleQuote,Colon,Question,Asterisk,Pipe,BackSlash,Ctl,RightSpace,RightPeriod,InvalidUtf8,Dot,Del,RightSpace
-\f[R]
-.fi
-.PP
-This can be specified using the \f[C]\-\-ftp\-encoding\f[R] flag or
-using an \f[C]encoding\f[R] parameter in the config file.
-.PP
-Or let\[cq]s say you have a Windows server but you want to preserve
-\f[C]\[uFF0A]\f[R] and \f[C]\[uFF1F]\f[R], you would then have this as
-the encoding (the Windows encoding minus \f[C]Asterisk\f[R] and
-\f[C]Question\f[R]).
-.IP
-.nf
-\f[C]
-Slash,LtGt,DoubleQuote,Colon,Pipe,BackSlash,Ctl,RightSpace,RightPeriod,InvalidUtf8,Dot
-\f[R]
-.fi
-.PP
-This can be specified using the \f[C]\-\-local\-encoding\f[R] flag or
-using an \f[C]encoding\f[R] parameter in the config file.
-.SS MIME Type
-.PP
-MIME types (also known as media types) classify types of documents using
-a simple text classification, eg \f[C]text/html\f[R] or
-\f[C]application/pdf\f[R].
-.PP
-Some cloud storage systems support reading (\f[C]R\f[R]) the MIME type
-of objects and some support writing (\f[C]W\f[R]) the MIME type of
-objects.
-.PP
-The MIME type can be important if you are serving files directly to HTTP
-from the storage system.
-.PP
-If you are copying from a remote which supports reading (\f[C]R\f[R]) to
-a remote which supports writing (\f[C]W\f[R]) then rclone will preserve
-the MIME types.
-Otherwise they will be guessed from the extension, or the remote itself
-may assign the MIME type.
-.SS Optional Features
-.PP
+
+    Slash,LtGt,DoubleQuote,Colon,Question,Asterisk,Pipe,BackSlash,Ctl,RightSpace,RightPeriod,InvalidUtf8,Dot,Del,RightSpace
+
+This can be specified using the \[ga]\-\-ftp\-encoding\[ga] flag or using an \[ga]encoding\[ga] parameter in the config file.
+
+Or let\[aq]s say you have a Windows server but you want to preserve \[ga]\[uFF0A]\[ga]
+and \[ga]\[uFF1F]\[ga], you would then have this as the encoding (the Windows
+encoding minus \[ga]Asterisk\[ga] and \[ga]Question\[ga]).
+
+    Slash,LtGt,DoubleQuote,Colon,Pipe,BackSlash,Ctl,RightSpace,RightPeriod,InvalidUtf8,Dot
+
+This can be specified using the \[ga]\-\-local\-encoding\[ga] flag or using an
+\[ga]encoding\[ga] parameter in the config file.
+
+### MIME Type ###
+
+MIME types (also known as media types) classify types of documents
+using a simple text classification, eg \[ga]text/html\[ga] or
+\[ga]application/pdf\[ga].
+
+Some cloud storage systems support reading (\[ga]R\[ga]) the MIME type of
+objects and some support writing (\[ga]W\[ga]) the MIME type of objects.
+
+The MIME type can be important if you are serving files directly to
+HTTP from the storage system.
+
+If you are copying from a remote which supports reading (\[ga]R\[ga]) to a
+remote which supports writing (\[ga]W\[ga]) then rclone will preserve the MIME
+types.  Otherwise they will be guessed from the extension, or the
+remote itself may assign the MIME type.
+
+## Optional Features ##
+
 All the remotes support a basic set of features, but there are some
-optional features supported by some remotes used to make some operations
-more efficient.
-.PP
-.TS
-tab(@);
-l c c c c c c c c c c.
-T{
-Name
-T}@T{
-Purge
-T}@T{
-Copy
-T}@T{
-Move
-T}@T{
-DirMove
-T}@T{
-CleanUp
-T}@T{
-ListR
-T}@T{
-StreamUpload
-T}@T{
-LinkSharing
-T}@T{
-About
-T}@T{
-EmptyDir
-T}
-_
-T{
-1Fichier
-T}@T{
-No
-T}@T{
-No
-T}@T{
-No
-T}@T{
-No
-T}@T{
-No
-T}@T{
-No
-T}@T{
-No
-T}@T{
-No
-T}@T{
-No
-T}@T{
-Yes
-T}
-T{
-Amazon Drive
-T}@T{
-Yes
-T}@T{
-No
-T}@T{
-Yes
-T}@T{
-Yes
-T}@T{
-No #575 (https://github.com/rclone/rclone/issues/575)
-T}@T{
-No
-T}@T{
-No
-T}@T{
-No #2178 (https://github.com/rclone/rclone/issues/2178)
-T}@T{
-No
-T}@T{
-Yes
-T}
-T{
-Amazon S3
-T}@T{
-No
-T}@T{
-Yes
-T}@T{
-No
-T}@T{
-No
-T}@T{
-No
-T}@T{
-Yes
-T}@T{
-Yes
-T}@T{
-No #2178 (https://github.com/rclone/rclone/issues/2178)
-T}@T{
-No
-T}@T{
-No
-T}
-T{
-Backblaze B2
-T}@T{
-No
-T}@T{
-Yes
-T}@T{
-No
-T}@T{
-No
-T}@T{
-Yes
-T}@T{
-Yes
-T}@T{
-Yes
-T}@T{
-Yes
-T}@T{
-No
-T}@T{
-No
-T}
-T{
-Box
-T}@T{
-Yes
-T}@T{
-Yes
-T}@T{
-Yes
-T}@T{
-Yes
-T}@T{
-No #575 (https://github.com/rclone/rclone/issues/575)
-T}@T{
-No
-T}@T{
-Yes
-T}@T{
-Yes
-T}@T{
-No
-T}@T{
-Yes
-T}
-T{
-Citrix ShareFile
-T}@T{
-Yes
-T}@T{
-Yes
-T}@T{
-Yes
-T}@T{
-Yes
-T}@T{
-No
-T}@T{
-No
-T}@T{
-Yes
-T}@T{
-No
-T}@T{
-No
-T}@T{
-Yes
-T}
-T{
-Dropbox
-T}@T{
-Yes
-T}@T{
-Yes
-T}@T{
-Yes
-T}@T{
-Yes
-T}@T{
-No #575 (https://github.com/rclone/rclone/issues/575)
-T}@T{
-No
-T}@T{
-Yes
-T}@T{
-Yes
-T}@T{
-Yes
-T}@T{
-Yes
-T}
-T{
-FTP
-T}@T{
-No
-T}@T{
-No
-T}@T{
-Yes
-T}@T{
-Yes
-T}@T{
-No
-T}@T{
-No
-T}@T{
-Yes
-T}@T{
-No #2178 (https://github.com/rclone/rclone/issues/2178)
-T}@T{
-No
-T}@T{
-Yes
-T}
-T{
-Google Cloud Storage
-T}@T{
-Yes
-T}@T{
-Yes
-T}@T{
-No
-T}@T{
-No
-T}@T{
-No
-T}@T{
-Yes
-T}@T{
-Yes
-T}@T{
-No #2178 (https://github.com/rclone/rclone/issues/2178)
-T}@T{
-No
-T}@T{
-No
-T}
-T{
-Google Drive
-T}@T{
-Yes
-T}@T{
-Yes
-T}@T{
-Yes
-T}@T{
-Yes
-T}@T{
-Yes
-T}@T{
-Yes
-T}@T{
-Yes
-T}@T{
-Yes
-T}@T{
-Yes
-T}@T{
-Yes
-T}
-T{
-Google Photos
-T}@T{
-No
-T}@T{
-No
-T}@T{
-No
-T}@T{
-No
-T}@T{
-No
-T}@T{
-No
-T}@T{
-No
-T}@T{
-No
-T}@T{
-No
-T}@T{
-No
-T}
-T{
-HTTP
-T}@T{
-No
-T}@T{
-No
-T}@T{
-No
-T}@T{
-No
-T}@T{
-No
-T}@T{
-No
-T}@T{
-No
-T}@T{
-No #2178 (https://github.com/rclone/rclone/issues/2178)
-T}@T{
-No
-T}@T{
-Yes
-T}
-T{
-Hubic
-T}@T{
-Yes \[dg]
-T}@T{
-Yes
-T}@T{
-No
-T}@T{
-No
-T}@T{
-No
-T}@T{
-Yes
-T}@T{
-Yes
-T}@T{
-No #2178 (https://github.com/rclone/rclone/issues/2178)
-T}@T{
-Yes
-T}@T{
-No
-T}
-T{
-Jottacloud
-T}@T{
-Yes
-T}@T{
-Yes
-T}@T{
-Yes
-T}@T{
-Yes
-T}@T{
-Yes
-T}@T{
-Yes
-T}@T{
-No
-T}@T{
-Yes
-T}@T{
-Yes
-T}@T{
-Yes
-T}
-T{
-Mail.ru Cloud
-T}@T{
-Yes
-T}@T{
-Yes
-T}@T{
-Yes
-T}@T{
-Yes
-T}@T{
-Yes
-T}@T{
-No
-T}@T{
-No
-T}@T{
-Yes
-T}@T{
-Yes
-T}@T{
-Yes
-T}
-T{
-Mega
-T}@T{
-Yes
-T}@T{
-No
-T}@T{
-Yes
-T}@T{
-Yes
-T}@T{
-Yes
-T}@T{
-No
-T}@T{
-No
-T}@T{
-No #2178 (https://github.com/rclone/rclone/issues/2178)
-T}@T{
-Yes
-T}@T{
-Yes
-T}
-T{
-Memory
-T}@T{
-No
-T}@T{
-Yes
-T}@T{
-No
-T}@T{
-No
-T}@T{
-No
-T}@T{
-Yes
-T}@T{
-Yes
-T}@T{
-No
-T}@T{
-No
-T}@T{
-No
-T}
-T{
-Microsoft Azure Blob Storage
-T}@T{
-Yes
-T}@T{
-Yes
-T}@T{
-No
-T}@T{
-No
-T}@T{
-No
-T}@T{
-Yes
-T}@T{
-Yes
-T}@T{
-No #2178 (https://github.com/rclone/rclone/issues/2178)
-T}@T{
-No
-T}@T{
-No
-T}
-T{
-Microsoft OneDrive
-T}@T{
-Yes
-T}@T{
-Yes
-T}@T{
-Yes
-T}@T{
-Yes
-T}@T{
-No #575 (https://github.com/rclone/rclone/issues/575)
-T}@T{
-No
-T}@T{
-No
-T}@T{
-Yes
-T}@T{
-Yes
-T}@T{
-Yes
-T}
-T{
-OpenDrive
-T}@T{
-Yes
-T}@T{
-Yes
-T}@T{
-Yes
-T}@T{
-Yes
-T}@T{
-No
-T}@T{
-No
-T}@T{
-No
-T}@T{
-No
-T}@T{
-No
-T}@T{
-Yes
-T}
-T{
-OpenStack Swift
-T}@T{
-Yes \[dg]
-T}@T{
-Yes
-T}@T{
-No
-T}@T{
-No
-T}@T{
-No
-T}@T{
-Yes
-T}@T{
-Yes
-T}@T{
-No #2178 (https://github.com/rclone/rclone/issues/2178)
-T}@T{
-Yes
-T}@T{
-No
-T}
-T{
-pCloud
-T}@T{
-Yes
-T}@T{
-Yes
-T}@T{
-Yes
-T}@T{
-Yes
-T}@T{
-Yes
-T}@T{
-No
-T}@T{
-No
-T}@T{
-No #2178 (https://github.com/rclone/rclone/issues/2178)
-T}@T{
-Yes
-T}@T{
-Yes
-T}
-T{
-premiumize.me
-T}@T{
-Yes
-T}@T{
-No
-T}@T{
-Yes
-T}@T{
-Yes
-T}@T{
-No
-T}@T{
-No
-T}@T{
-No
-T}@T{
-Yes
-T}@T{
-Yes
-T}@T{
-Yes
-T}
-T{
-put.io
-T}@T{
-Yes
-T}@T{
-No
-T}@T{
-Yes
-T}@T{
-Yes
-T}@T{
-Yes
-T}@T{
-No
-T}@T{
-Yes
-T}@T{
-No #2178 (https://github.com/rclone/rclone/issues/2178)
-T}@T{
-Yes
-T}@T{
-Yes
-T}
-T{
-QingStor
-T}@T{
-No
-T}@T{
-Yes
-T}@T{
-No
-T}@T{
-No
-T}@T{
-Yes
-T}@T{
-Yes
-T}@T{
-No
-T}@T{
-No #2178 (https://github.com/rclone/rclone/issues/2178)
-T}@T{
-No
-T}@T{
-No
-T}
-T{
-Seafile
-T}@T{
-Yes
-T}@T{
-Yes
-T}@T{
-Yes
-T}@T{
-Yes
-T}@T{
-Yes
-T}@T{
-Yes
-T}@T{
-Yes
-T}@T{
-Yes
-T}@T{
-Yes
-T}@T{
-Yes
-T}
-T{
-SFTP
-T}@T{
-No
-T}@T{
-No
-T}@T{
-Yes
-T}@T{
-Yes
-T}@T{
-No
-T}@T{
-No
-T}@T{
-Yes
-T}@T{
-No #2178 (https://github.com/rclone/rclone/issues/2178)
-T}@T{
-Yes
-T}@T{
-Yes
-T}
-T{
-SugarSync
-T}@T{
-Yes
-T}@T{
-Yes
-T}@T{
-Yes
-T}@T{
-Yes
-T}@T{
-No
-T}@T{
-No
-T}@T{
-Yes
-T}@T{
-Yes
-T}@T{
-No
-T}@T{
-Yes
-T}
-T{
-Tardigrade
-T}@T{
-Yes \[dg]
-T}@T{
-No
-T}@T{
-No
-T}@T{
-No
-T}@T{
-No
-T}@T{
-Yes
-T}@T{
-Yes
-T}@T{
-No
-T}@T{
-No
-T}@T{
-No
-T}
-T{
-WebDAV
-T}@T{
-Yes
-T}@T{
-Yes
-T}@T{
-Yes
-T}@T{
-Yes
-T}@T{
-No
-T}@T{
-No
-T}@T{
-Yes \[dd]
-T}@T{
-No #2178 (https://github.com/rclone/rclone/issues/2178)
-T}@T{
-Yes
-T}@T{
-Yes
-T}
-T{
-Yandex Disk
-T}@T{
-Yes
-T}@T{
-Yes
-T}@T{
-Yes
-T}@T{
-Yes
-T}@T{
-Yes
-T}@T{
-No
-T}@T{
-Yes
-T}@T{
-Yes
-T}@T{
-Yes
-T}@T{
-Yes
-T}
-T{
-The local filesystem
-T}@T{
-Yes
-T}@T{
-No
-T}@T{
-Yes
-T}@T{
-Yes
-T}@T{
-No
-T}@T{
-No
-T}@T{
-Yes
-T}@T{
-No
-T}@T{
-Yes
-T}@T{
-Yes
-T}
-.TE
-.SS Purge
-.PP
-This deletes a directory quicker than just deleting all the files in the
-directory.
-.PP
-\[dg] Note Swift, Hubic, and Tardigrade implement this in order to
-delete directory markers but they don\[cq]t actually have a quicker way
-of deleting files other than deleting them individually.
-.PP
+optional features supported by some remotes used to make some
+operations more efficient.
+
+| Name                         | Purge | Copy | Move | DirMove | CleanUp | ListR | StreamUpload | LinkSharing | About | EmptyDir |
+| \-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\- |:\-\-\-\-\-:|:\-\-\-\-:|:\-\-\-\-:|:\-\-\-\-\-\-\-:|:\-\-\-\-\-\-\-:|:\-\-\-\-\-:|:\-\-\-\-\-\-\-\-\-\-\-\-:|:\-\-\-\-\-\-\-\-\-\-\-\-:|:\-\-\-\-\-:| :\-\-\-\-\-\-: |
+| 1Fichier                     | No    | No   | No   | No      | No      | No    | No           | No           |   No  |  Yes |
+| Amazon Drive                 | Yes   | No   | Yes  | Yes     | No [#575](https://github.com/rclone/rclone/issues/575) | No  | No  | No [#2178](https://github.com/rclone/rclone/issues/2178) | No  | Yes |
+| Amazon S3                    | No    | Yes  | No   | No      | Yes     | Yes   | Yes          | No [#2178](https://github.com/rclone/rclone/issues/2178) | No  | No |
+| Backblaze B2                 | No    | Yes  | No   | No      | Yes     | Yes   | Yes          | Yes          | No  | No |
+| Box                          | Yes   | Yes  | Yes  | Yes     | Yes \[dd]\[dd]  | No    | Yes          | Yes          | No  | Yes |
+| Citrix ShareFile             | Yes   | Yes  | Yes  | Yes     | No      | No    | Yes          | No          | No  | Yes |
+| Dropbox                      | Yes   | Yes  | Yes  | Yes     | No [#575](https://github.com/rclone/rclone/issues/575) | No  | Yes | Yes | Yes | Yes |
+| FTP                          | No    | No   | Yes  | Yes     | No      | No    | Yes          | No [#2178](https://github.com/rclone/rclone/issues/2178) | No  | Yes |
+| Google Cloud Storage         | Yes   | Yes  | No   | No      | No      | Yes   | Yes          | No [#2178](https://github.com/rclone/rclone/issues/2178) | No  | No |
+| Google Drive                 | Yes   | Yes  | Yes  | Yes     | Yes     | Yes   | Yes          | Yes         | Yes | Yes |
+| Google Photos                | No    | No   | No   | No      | No      | No    | No           | No          | No | No |
+| HTTP                         | No    | No   | No   | No      | No      | No    | No           | No [#2178](https://github.com/rclone/rclone/issues/2178) | No  | Yes |
+| Hubic                        | Yes \[dg] | Yes  | No   | No      | No      | Yes   | Yes          | No [#2178](https://github.com/rclone/rclone/issues/2178) | Yes | No |
+| Jottacloud                   | Yes   | Yes  | Yes  | Yes     | Yes     | Yes   | No           | Yes                                                   | Yes | Yes |
+| Mail.ru Cloud                | Yes   | Yes  | Yes  | Yes     | Yes     | No    | No           | Yes                                                   | Yes | Yes |
+| Mega                         | Yes   | No   | Yes  | Yes     | Yes     | No    | No           | No [#2178](https://github.com/rclone/rclone/issues/2178) | Yes | Yes |
+| Memory                       | No    | Yes  | No   | No      | No      | Yes   | Yes          | No          | No | No |
+| Microsoft Azure Blob Storage | Yes   | Yes  | No   | No      | No      | Yes   | Yes          | No [#2178](https://github.com/rclone/rclone/issues/2178) | No  | No |
+| Microsoft OneDrive           | Yes   | Yes  | Yes  | Yes     | Yes     | No    | No           | Yes | Yes | Yes |
+| OpenDrive                    | Yes   | Yes  | Yes  | Yes     | No      | No    | No           | No                                                    | No  | Yes |
+| OpenStack Swift              | Yes \[dg] | Yes  | No   | No      | No      | Yes   | Yes          | No [#2178](https://github.com/rclone/rclone/issues/2178) | Yes | No |
+| pCloud                       | Yes   | Yes  | Yes  | Yes     | Yes     | No    | No           | Yes | Yes | Yes |
+| premiumize.me                | Yes   | No   | Yes  | Yes     | No      | No    | No           | Yes         | Yes | Yes |
+| put.io                       | Yes   | No   | Yes  | Yes     | Yes     | No    | Yes          | No [#2178](https://github.com/rclone/rclone/issues/2178) | Yes | Yes |
+| QingStor                     | No    | Yes  | No   | No      | Yes     | Yes   | No           | No [#2178](https://github.com/rclone/rclone/issues/2178) | No  | No |
+| Seafile                      | Yes   | Yes  | Yes  | Yes     | Yes     | Yes   | Yes          | Yes         | Yes | Yes |
+| SFTP                         | No    | No   | Yes  | Yes     | No      | No    | Yes          | No [#2178](https://github.com/rclone/rclone/issues/2178) | Yes  | Yes |
+| SugarSync                    | Yes   | Yes  | Yes  | Yes     | No      | No    | Yes          | Yes         | No  | Yes |
+| Tardigrade                   | Yes \[dg] | No   | No   | No      | No      | Yes   | Yes          | No          | No  | No  |
+| WebDAV                       | Yes   | Yes  | Yes  | Yes     | No      | No    | Yes \[dd]        | No [#2178](https://github.com/rclone/rclone/issues/2178) | Yes  | Yes |
+| Yandex Disk                  | Yes   | Yes  | Yes  | Yes     | Yes     | No    | Yes          | Yes         | Yes | Yes |
+| The local filesystem         | Yes   | No   | Yes  | Yes     | No      | No    | Yes          | No          | Yes | Yes |
+
+### Purge ###
+
+This deletes a directory quicker than just deleting all the files in
+the directory.
+
+\[dg] Note Swift, Hubic, and Tardigrade implement this in order to delete
+directory markers but they don\[aq]t actually have a quicker way of deleting
+files other than deleting them individually.
+
 \[dd] StreamUpload is not supported with Nextcloud
-.SS Copy
-.PP
-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 \f[C]rclone copy\f[R] or \f[C]rclone move\f[R] if
-the remote doesn\[cq]t support \f[C]Move\f[R] directly.
-.PP
-If the server doesn\[cq]t support \f[C]Copy\f[R] directly then for copy
-operations the file is downloaded then re\-uploaded.
-.SS Move
-.PP
-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 \f[C]rclone move\f[R] if the server doesn\[cq]t support
-\f[C]DirMove\f[R].
-.PP
-If the server isn\[cq]t capable of \f[C]Move\f[R] then rclone simulates
-it with \f[C]Copy\f[R] then delete.
-If the server doesn\[cq]t support \f[C]Copy\f[R] then rclone will
-download the file and re\-upload it.
-.SS DirMove
-.PP
-This is used to implement \f[C]rclone move\f[R] to move a directory if
-possible.
-If it isn\[cq]t then it will use \f[C]Move\f[R] on each file (which
-falls back to \f[C]Copy\f[R] then download and upload \- see
-\f[C]Move\f[R] section).
-.SS CleanUp
-.PP
-This is used for emptying the trash for a remote by
-\f[C]rclone cleanup\f[R].
-.PP
-If the server can\[cq]t do \f[C]CleanUp\f[R] then
-\f[C]rclone cleanup\f[R] will return an error.
-.SS ListR
-.PP
-The remote supports a recursive list to list all the contents beneath a
-directory quickly.
-This enables the \f[C]\-\-fast\-list\f[R] flag to work.
-See the rclone docs (https://rclone.org/docs/#fast-list) for more
-details.
-.SS StreamUpload
-.PP
-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.\ \f[C]rclone rcat\f[R].
-.SS LinkSharing
-.PP
+
+### Copy ###
+
+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 \[ga]rclone copy\[ga] or
+\[ga]rclone move\[ga] if the remote doesn\[aq]t support \[ga]Move\[ga] directly.
+
+If the server doesn\[aq]t support \[ga]Copy\[ga] directly then for copy operations
+the file is downloaded then re\-uploaded.
+
+### Move ###
+
+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 \[ga]rclone move\[ga] if the
+server doesn\[aq]t support \[ga]DirMove\[ga].
+
+If the server isn\[aq]t capable of \[ga]Move\[ga] then rclone simulates it with
+\[ga]Copy\[ga] then delete.  If the server doesn\[aq]t support \[ga]Copy\[ga] then rclone
+will download the file and re\-upload it.
+
+### DirMove ###
+
+This is used to implement \[ga]rclone move\[ga] to move a directory if
+possible.  If it isn\[aq]t then it will use \[ga]Move\[ga] on each file (which
+falls back to \[ga]Copy\[ga] then download and upload \- see \[ga]Move\[ga] section).
+
+### CleanUp ###
+
+This is used for emptying the trash for a remote by \[ga]rclone cleanup\[ga].
+
+If the server can\[aq]t do \[ga]CleanUp\[ga] then \[ga]rclone cleanup\[ga] will return an
+error.
+
+\[dd]\[dd] Note that while Box implements this it has to delete every file
+idividually so it will be slower than emptying the trash via the WebUI
+
+### ListR ###
+
+The remote supports a recursive list to list all the contents beneath
+a directory quickly.  This enables the \[ga]\-\-fast\-list\[ga] flag to work.
+See the [rclone docs](https://rclone.org/docs/#fast\-list) for more details.
+
+### StreamUpload ###
+
+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. \[ga]rclone rcat\[ga].
+
+### LinkSharing ###
+
 Sets the necessary permissions on a file or folder and prints a link
-that allows others to access them, even if they don\[cq]t have an
-account on the particular cloud provider.
-.SS About
-.PP
+that allows others to access them, even if they don\[aq]t have an account
+on the particular cloud provider.
+
+### About ###
+
 This is used to fetch quota information from the remote, like bytes
 used/free/quota and bytes used in the trash.
-.PP
-This is also used to return the space used, available for
-\f[C]rclone mount\f[R].
-.PP
-If the server can\[cq]t do \f[C]About\f[R] then \f[C]rclone about\f[R]
-will return an error.
-.SS EmptyDir
-.PP
-The remote supports empty directories.
-See Limitations (https://rclone.org/bugs/#limitations) for details.
-Most Object/Bucket based remotes do not support this.
-.SH Global Flags
-.PP
-This describes the global flags available to every rclone command split
-into two groups, non backend and backend flags.
-.SS Non Backend Flags
-.PP
+
+This is also used to return the space used, available for \[ga]rclone mount\[ga].
+
+If the server can\[aq]t do \[ga]About\[ga] then \[ga]rclone about\[ga] will return an
+error.
+
+### EmptyDir ###
+
+The remote supports empty directories. See [Limitations](https://rclone.org/bugs/#limitations)
+ for details. Most Object/Bucket based remotes do not support this.
+
+# Global Flags
+
+This describes the global flags available to every rclone command
+split into two groups, non backend and backend flags.
+
+## Non Backend Flags
+
 These flags are available for every command.
+\f[R]
+.fi
 .IP
 .nf
 \f[C]
-      \-\-ask\-password                         Allow prompt for password for encrypted configuration. (default true)
-      \-\-auto\-confirm                         If enabled, do not request console confirmation.
-      \-\-backup\-dir string                    Make backups into hierarchy based in DIR.
-      \-\-bind string                          Local address to bind to for outgoing connections, IPv4, IPv6 or name.
-      \-\-buffer\-size SizeSuffix               In memory buffer size when reading files for each \-\-transfer. (default 16M)
-      \-\-bwlimit BwTimetable                  Bandwidth limit in kBytes/s, or use suffix b|k|M|G or a full timetable.
-      \-\-ca\-cert string                       CA certificate used to verify servers
-      \-\-cache\-dir string                     Directory rclone will use for caching. (default \[dq]$HOME/.cache/rclone\[dq])
-      \-\-check\-first                          Do all the checks before starting transfers.
-      \-\-checkers int                         Number of checkers to run in parallel. (default 8)
-  \-c, \-\-checksum                             Skip based on checksum (if available) & size, not mod\-time & size
-      \-\-client\-cert string                   Client SSL certificate (PEM) for mutual TLS auth
-      \-\-client\-key string                    Client SSL private key (PEM) for mutual TLS auth
-      \-\-compare\-dest string                  Include additional server\-side path during comparison.
-      \-\-config string                        Config file. (default \[dq]$HOME/.config/rclone/rclone.conf\[dq])
-      \-\-contimeout duration                  Connect timeout (default 1m0s)
-      \-\-copy\-dest string                     Implies \-\-compare\-dest but also copies files from path into destination.
-      \-\-cpuprofile string                    Write cpu profile to file
-      \-\-cutoff\-mode string                   Mode to stop transfers when reaching the max transfer limit HARD|SOFT|CAUTIOUS (default \[dq]HARD\[dq])
-      \-\-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
-      \-\-delete\-excluded                      Delete files on dest excluded from sync
-      \-\-disable string                       Disable a comma separated list of features.  Use help to see a list.
-  \-n, \-\-dry\-run                              Do a trial run with no permanent changes
-      \-\-dump DumpFlags                       List of items to dump from: headers,bodies,requests,responses,auth,filters,goroutines,openfiles
-      \-\-dump\-bodies                          Dump HTTP headers and bodies \- may contain sensitive info
-      \-\-dump\-headers                         Dump HTTP headers \- may contain sensitive info
-      \-\-error\-on\-no\-transfer                 Sets exit code 9 if no files are transferred, useful in scripts
-      \-\-exclude stringArray                  Exclude files matching pattern
-      \-\-exclude\-from stringArray             Read exclude patterns from file (use \- to read from stdin)
-      \-\-exclude\-if\-present string            Exclude directories if filename is present
-      \-\-expect\-continue\-timeout duration     Timeout when using expect / 100\-continue in HTTP (default 1s)
-      \-\-fast\-list                            Use recursive list if available. Uses more memory but fewer transactions.
-      \-\-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 filtering patterns from a file (use \- to read from stdin)
-      \-\-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
-      \-\-ignore\-case                          Ignore case in filters (case insensitive)
-      \-\-ignore\-case\-sync                     Ignore case when synchronizing
-      \-\-ignore\-checksum                      Skip post copy check of checksums.
-      \-\-ignore\-errors                        delete even if there are I/O errors
-      \-\-ignore\-existing                      Skip all files that exist on destination
-      \-\-ignore\-size                          Ignore size when skipping use mod\-time or checksum.
-  \-I, \-\-ignore\-times                         Don\[aq]t skip files that match size and time \- transfer all files
-      \-\-immutable                            Do not modify files. Fail if existing files have been modified.
-      \-\-include stringArray                  Include files matching pattern
-      \-\-include\-from stringArray             Read include patterns from file (use \- to read from stdin)
-      \-\-log\-file string                      Log everything to this file
-      \-\-log\-format string                    Comma separated list of log format options (default \[dq]date,time\[dq])
-      \-\-log\-level string                     Log level DEBUG|INFO|NOTICE|ERROR (default \[dq]NOTICE\[dq])
-      \-\-low\-level\-retries int                Number of low level retries to do. (default 10)
-      \-\-max\-age Duration                     Only transfer files younger than this in s or suffix ms|s|m|h|d|w|M|y (default off)
-      \-\-max\-backlog int                      Maximum number of objects in sync or check backlog. (default 10000)
-      \-\-max\-delete int                       When synchronizing, limit the number of deletes (default \-1)
-      \-\-max\-depth int                        If set limits the recursion depth to this. (default \-1)
-      \-\-max\-duration duration                Maximum duration rclone will transfer data for.
-      \-\-max\-size SizeSuffix                  Only transfer files smaller than this in k or suffix b|k|M|G (default off)
-      \-\-max\-stats\-groups int                 Maximum number of stats groups to keep in memory. On max oldest is discarded. (default 1000)
-      \-\-max\-transfer SizeSuffix              Maximum size of data to transfer. (default off)
-      \-\-memprofile string                    Write memory profile to file
-      \-\-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 k or suffix b|k|M|G (default off)
-      \-\-modify\-window duration               Max time diff to be considered the same (default 1ns)
-      \-\-multi\-thread\-cutoff SizeSuffix       Use multi\-thread downloads for files above this size. (default 250M)
-      \-\-multi\-thread\-streams int             Max number of streams to use for multi\-thread downloads. (default 4)
-      \-\-no\-check\-certificate                 Do not verify the server SSL certificate. Insecure.
-      \-\-no\-check\-dest                        Don\[aq]t check the destination, copy regardless.
-      \-\-no\-gzip\-encoding                     Don\[aq]t set Accept\-Encoding: gzip.
-      \-\-no\-traverse                          Don\[aq]t traverse destination file system on copy.
-      \-\-no\-unicode\-normalization             Don\[aq]t normalize unicode characters in filenames.
-      \-\-no\-update\-modtime                    Don\[aq]t update destination mod\-time if files identical.
-      \-\-order\-by string                      Instructions on how to order the transfers, eg \[aq]size,descending\[aq]
-      \-\-password\-command SpaceSepList        Command for supplying password for encrypted configuration.
-  \-P, \-\-progress                             Show progress during transfer.
-  \-q, \-\-quiet                                Print as little stuff as possible
-      \-\-rc                                   Enable the remote control server.
-      \-\-rc\-addr string                       IPaddress:Port or :Port to bind server to. (default \[dq]localhost:5572\[dq])
-      \-\-rc\-allow\-origin string               Set the allowed origin for CORS.
-      \-\-rc\-baseurl string                    Prefix for URLs \- leave blank for root.
-      \-\-rc\-cert string                       SSL PEM key (concatenation of certificate and CA certificate)
-      \-\-rc\-client\-ca string                  Client certificate authority to verify clients with
-      \-\-rc\-enable\-metrics                    Enable prometheus metrics on /metrics
-      \-\-rc\-files string                      Path to local files to serve on the HTTP server.
-      \-\-rc\-htpasswd string                   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                        SSL PEM Private key
-      \-\-rc\-max\-header\-bytes int              Maximum size of request header (default 4096)
-      \-\-rc\-no\-auth                           Don\[aq]t require auth for certain methods.
-      \-\-rc\-pass string                       Password for authentication.
-      \-\-rc\-realm string                      realm for authentication (default \[dq]rclone\[dq])
-      \-\-rc\-serve                             Enable the serving of remote objects.
-      \-\-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 \[dq]https://api.github.com/repos/rclone/rclone\-webui\-react/releases/latest\[dq])
-      \-\-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\[aq]t open the browser automatically
-      \-\-rc\-web\-gui\-update                    Check and update to latest version of web gui
-      \-\-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)
-      \-\-size\-only                            Skip based on size only, not mod\-time or checksum
-      \-\-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 string               Log level to show \-\-stats output DEBUG|INFO|NOTICE|ERROR (default \[dq]INFO\[dq])
-      \-\-stats\-one\-line                       Make the stats fit on one line.
-      \-\-stats\-one\-line\-date                  Enables \-\-stats\-one\-line and add current date/time prefix.
-      \-\-stats\-one\-line\-date\-format string    Enables \-\-stats\-one\-line\-date and uses custom formatted date. Enclose date string in double quotes (\[dq]). See https://golang.org/pkg/time/#Time.Format
-      \-\-stats\-unit string                    Show data rate in stats as either \[aq]bits\[aq] or \[aq]bytes\[aq]/s (default \[dq]bytes\[dq])
-      \-\-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 100k)
-      \-\-suffix string                        Suffix to add to changed files.
-      \-\-suffix\-keep\-extension                Preserve the extension when using \-\-suffix.
-      \-\-syslog                               Use Syslog for logging
-      \-\-syslog\-facility string               Facility for syslog, eg KERN,USER,... (default \[dq]DAEMON\[dq])
-      \-\-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)
-      \-\-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 (default \[dq]hash\[dq])
-      \-\-transfers int                        Number of file transfers to run in parallel. (default 4)
-  \-u, \-\-update                               Skip files that are newer on the destination.
-      \-\-use\-cookies                          Enable session cookiejar.
-      \-\-use\-json\-log                         Use json log format.
-      \-\-use\-mmap                             Use mmap allocator (see docs).
-      \-\-use\-server\-modtime                   Use server modified time instead of object metadata
-      \-\-user\-agent string                    Set the user\-agent to a specified string. The default is rclone/ version (default \[dq]rclone/v1.52.0\[dq])
-  \-v, \-\-verbose count                        Print lots more stuff (repeat for more)
+  \-\-ask\-password                         Allow prompt for password for encrypted configuration. (default true)
+  \-\-auto\-confirm                         If enabled, do not request console confirmation.
+  \-\-backup\-dir string                    Make backups into hierarchy based in DIR.
+  \-\-bind string                          Local address to bind to for outgoing connections, IPv4, IPv6 or name.
+  \-\-buffer\-size SizeSuffix               In memory buffer size when reading files for each \-\-transfer. (default 16M)
+  \-\-bwlimit BwTimetable                  Bandwidth limit in kBytes/s, or use suffix b|k|M|G or a full timetable.
+  \-\-bwlimit\-file BwTimetable             Bandwidth limit per file in kBytes/s, or use suffix b|k|M|G or a full timetable.
+  \-\-ca\-cert string                       CA certificate used to verify servers
+  \-\-cache\-dir string                     Directory rclone will use for caching. (default \[dq]$HOME/.cache/rclone\[dq])
+  \-\-check\-first                          Do all the checks before starting transfers.
+  \-\-checkers int                         Number of checkers to run in parallel. (default 8)
 \f[R]
 .fi
-.SS Backend Flags
 .PP
-These flags are available for every command.
-They control the backends and may be set in the config file.
+\-c, \-\-checksum Skip based on checksum (if available) & size, not
+mod\-time & size \-\-client\-cert string Client SSL certificate (PEM)
+for mutual TLS auth \-\-client\-key string Client SSL private key (PEM)
+for mutual TLS auth \-\-compare\-dest string Include additional
+server\-side path during comparison.
+\-\-config string Config file.
+(default \[dq]$HOME/.config/rclone/rclone.conf\[dq]) \-\-contimeout
+duration Connect timeout (default 1m0s) \-\-copy\-dest string Implies
+\-\-compare\-dest but also copies files from path into destination.
+\-\-cpuprofile string Write cpu profile to file \-\-cutoff\-mode string
+Mode to stop transfers when reaching the max transfer limit
+HARD|SOFT|CAUTIOUS (default \[dq]HARD\[dq]) \-\-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 \-\-delete\-excluded Delete files on dest excluded from
+sync \-\-disable string Disable a comma separated list of features.
+Use help to see a list.
+\-n, \-\-dry\-run Do a trial run with no permanent changes \-\-dump
+DumpFlags List of items to dump from:
+headers,bodies,requests,responses,auth,filters,goroutines,openfiles
+\-\-dump\-bodies Dump HTTP headers and bodies \- may contain sensitive
+info \-\-dump\-headers Dump HTTP headers \- may contain sensitive info
+\-\-error\-on\-no\-transfer Sets exit code 9 if no files are
+transferred, useful in scripts \-\-exclude stringArray Exclude files
+matching pattern \-\-exclude\-from stringArray Read exclude patterns
+from file (use \- to read from stdin) \-\-exclude\-if\-present string
+Exclude directories if filename is present \-\-expect\-continue\-timeout
+duration Timeout when using expect / 100\-continue in HTTP (default 1s)
+\-\-fast\-list Use recursive list if available.
+Uses more memory but fewer transactions.
+\-\-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 filtering patterns from a file
+(use \- to read from stdin) \-\-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 \-\-ignore\-case Ignore case in filters (case
+insensitive) \-\-ignore\-case\-sync Ignore case when synchronizing
+\-\-ignore\-checksum Skip post copy check of checksums.
+\-\-ignore\-errors delete even if there are I/O errors
+\-\-ignore\-existing Skip all files that exist on destination
+\-\-ignore\-size Ignore size when skipping use mod\-time or checksum.
+\-I, \-\-ignore\-times Don\[aq]t skip files that match size and time \-
+transfer all files \-\-immutable Do not modify files.
+Fail if existing files have been modified.
+\-\-include stringArray Include files matching pattern \-\-include\-from
+stringArray Read include patterns from file (use \- to read from stdin)
+\-i, \-\-interactive Enable interactive mode \-\-log\-file string Log
+everything to this file \-\-log\-format string Comma separated list of
+log format options (default \[dq]date,time\[dq]) \-\-log\-level string
+Log level DEBUG|INFO|NOTICE|ERROR (default \[dq]NOTICE\[dq])
+\-\-low\-level\-retries int Number of low level retries to do.
+(default 10) \-\-max\-age Duration Only transfer files younger than this
+in s or suffix ms|s|m|h|d|w|M|y (default off) \-\-max\-backlog int
+Maximum number of objects in sync or check backlog.
+(default 10000) \-\-max\-delete int When synchronizing, limit the number
+of deletes (default \-1) \-\-max\-depth int If set limits the recursion
+depth to this.
+(default \-1) \-\-max\-duration duration Maximum duration rclone will
+transfer data for.
+\-\-max\-size SizeSuffix Only transfer files smaller than this in k or
+suffix b|k|M|G (default off) \-\-max\-stats\-groups int Maximum number
+of stats groups to keep in memory.
+On max oldest is discarded.
+(default 1000) \-\-max\-transfer SizeSuffix Maximum size of data to
+transfer.
+(default off) \-\-memprofile string Write memory profile to file
+\-\-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 k or suffix b|k|M|G (default off)
+\-\-modify\-window duration Max time diff to be considered the same
+(default 1ns) \-\-multi\-thread\-cutoff SizeSuffix Use multi\-thread
+downloads for files above this size.
+(default 250M) \-\-multi\-thread\-streams int Max number of streams to
+use for multi\-thread downloads.
+(default 4) \-\-no\-check\-certificate Do not verify the server SSL
+certificate.
+Insecure.
+\-\-no\-check\-dest Don\[aq]t check the destination, copy regardless.
+\-\-no\-gzip\-encoding Don\[aq]t set Accept\-Encoding: gzip.
+\-\-no\-traverse Don\[aq]t traverse destination file system on copy.
+\-\-no\-unicode\-normalization Don\[aq]t normalize unicode characters in
+filenames.
+\-\-no\-update\-modtime Don\[aq]t update destination mod\-time if files
+identical.
+\-\-order\-by string Instructions on how to order the transfers, eg
+\[aq]size,descending\[aq] \-\-password\-command SpaceSepList Command for
+supplying password for encrypted configuration.
+\-P, \-\-progress Show progress during transfer.
+\-q, \-\-quiet Print as little stuff as possible \-\-rc Enable the
+remote control server.
+\-\-rc\-addr string IPaddress:Port or :Port to bind server to.
+(default \[dq]localhost:5572\[dq]) \-\-rc\-allow\-origin string Set the
+allowed origin for CORS.
+\-\-rc\-baseurl string Prefix for URLs \- leave blank for root.
+\-\-rc\-cert string SSL PEM key (concatenation of certificate and CA
+certificate) \-\-rc\-client\-ca string Client certificate authority to
+verify clients with \-\-rc\-enable\-metrics Enable prometheus metrics on
+/metrics \-\-rc\-files string Path to local files to serve on the HTTP
+server.
+\-\-rc\-htpasswd string 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 SSL PEM Private key
+\-\-rc\-max\-header\-bytes int Maximum size of request header (default
+4096) \-\-rc\-no\-auth Don\[aq]t require auth for certain methods.
+\-\-rc\-pass string Password for authentication.
+\-\-rc\-realm string realm for authentication (default \[dq]rclone\[dq])
+\-\-rc\-serve Enable the serving of remote objects.
+\-\-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
+\[dq]https://api.github.com/repos/rclone/rclone\-webui\-react/releases/latest\[dq])
+\-\-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\[aq]t open the browser
+automatically \-\-rc\-web\-gui\-update Check and update to latest
+version of web gui \-\-refresh\-times Refresh the modtime of remote
+files.
+\-\-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) \-\-size\-only Skip based on size only, not mod\-time or
+checksum \-\-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 string Log level to
+show \-\-stats output DEBUG|INFO|NOTICE|ERROR (default \[dq]INFO\[dq])
+\-\-stats\-one\-line Make the stats fit on one line.
+\-\-stats\-one\-line\-date Enables \-\-stats\-one\-line and add current
+date/time prefix.
+\-\-stats\-one\-line\-date\-format string Enables
+\-\-stats\-one\-line\-date and uses custom formatted date.
+Enclose date string in double quotes (\[dq]).
+See https://golang.org/pkg/time/#Time.Format \-\-stats\-unit string Show
+data rate in stats as either \[aq]bits\[aq] or \[aq]bytes\[aq]/s
+(default \[dq]bytes\[dq]) \-\-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 100k) \-\-suffix string Suffix to add to changed files.
+\-\-suffix\-keep\-extension Preserve the extension when using
+\-\-suffix.
+\-\-syslog Use Syslog for logging \-\-syslog\-facility string Facility
+for syslog, eg KERN,USER,...
+(default \[dq]DAEMON\[dq]) \-\-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) \-\-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 \[dq]hash\[dq]) \-\-transfers int Number of
+file transfers to run in parallel.
+(default 4) \-u, \-\-update Skip files that are newer on the
+destination.
+\-\-use\-cookies Enable session cookiejar.
+\-\-use\-json\-log Use json log format.
+\-\-use\-mmap Use mmap allocator (see docs).
+\-\-use\-server\-modtime Use server modified time instead of object
+metadata \-\-user\-agent string Set the user\-agent to a specified
+string.
+The default is rclone/ version (default \[dq]rclone/v1.53.0\[dq]) \-v,
+\-\-verbose count Print lots more stuff (repeat for more)
 .IP
 .nf
 \f[C]
-      \-\-acd\-auth\-url string                                      Auth server URL.
-      \-\-acd\-client\-id string                                     Amazon Application Client ID.
-      \-\-acd\-client\-secret string                                 Amazon Application Client Secret.
-      \-\-acd\-encoding MultiEncoder                                This sets the encoding for the backend. (default Slash,InvalidUtf8,Dot)
-      \-\-acd\-templink\-threshold SizeSuffix                        Files >= this size will be downloaded via their tempLink. (default 9G)
-      \-\-acd\-token\-url string                                     Token server url.
-      \-\-acd\-upload\-wait\-per\-gb Duration                          Additional time per GB to wait after a failed complete upload to see if it appears. (default 3m0s)
-      \-\-alias\-remote string                                      Remote or path to alias.
-      \-\-azureblob\-access\-tier string                             Access tier of blob: hot, cool or archive.
-      \-\-azureblob\-account string                                 Storage Account Name (leave blank to use SAS URL or Emulator)
-      \-\-azureblob\-chunk\-size SizeSuffix                          Upload chunk size (<= 100MB). (default 4M)
-      \-\-azureblob\-disable\-checksum                               Don\[aq]t store MD5 checksum with object metadata.
-      \-\-azureblob\-encoding MultiEncoder                          This sets the encoding for the backend. (default Slash,BackSlash,Del,Ctl,RightPeriod,InvalidUtf8)
-      \-\-azureblob\-endpoint string                                Endpoint for the service
-      \-\-azureblob\-key string                                     Storage Account Key (leave blank to use SAS URL or Emulator)
-      \-\-azureblob\-list\-chunk int                                 Size of blob list. (default 5000)
-      \-\-azureblob\-memory\-pool\-flush\-time Duration                How often internal memory buffer pools will be flushed. (default 1m0s)
-      \-\-azureblob\-memory\-pool\-use\-mmap                           Whether to use mmap buffers in internal memory pool.
-      \-\-azureblob\-sas\-url string                                 SAS URL for container level access only
-      \-\-azureblob\-upload\-cutoff SizeSuffix                       Cutoff for switching to chunked upload (<= 256MB). (default 256M)
-      \-\-azureblob\-use\-emulator                                   Uses local storage emulator if provided as \[aq]true\[aq] (leave blank if using real azure storage endpoint)
-      \-\-b2\-account string                                        Account ID or Application Key ID
-      \-\-b2\-chunk\-size SizeSuffix                                 Upload chunk size. Must fit in memory. (default 96M)
-      \-\-b2\-disable\-checksum                                      Disable checksums for large (> upload cutoff) files
-      \-\-b2\-download\-auth\-duration Duration                       Time before the 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 MultiEncoder                                 This sets 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\-test\-mode string                                      A flag string for X\-Bz\-Test\-Mode header for debugging.
-      \-\-b2\-upload\-cutoff SizeSuffix                              Cutoff for switching to chunked upload. (default 200M)
-      \-\-b2\-versions                                              Include old versions in directory listings.
-      \-\-box\-box\-config\-file string                               Box App config.json location
-      \-\-box\-box\-sub\-type string                                   (default \[dq]user\[dq])
-      \-\-box\-client\-id string                                     Box App Client Id.
-      \-\-box\-client\-secret string                                 Box App Client Secret
-      \-\-box\-commit\-retries int                                   Max number of times to try committing a multipart file. (default 100)
-      \-\-box\-encoding MultiEncoder                                This sets the encoding for the backend. (default Slash,BackSlash,Del,Ctl,RightSpace,InvalidUtf8,Dot)
-      \-\-box\-root\-folder\-id string                                Fill in for rclone to use a non root folder as its starting point.
-      \-\-box\-upload\-cutoff SizeSuffix                             Cutoff for switching to multipart upload (>= 50MB). (default 50M)
-      \-\-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 \[dq]$HOME/.cache/rclone/cache\-backend\[dq])
-      \-\-cache\-chunk\-size SizeSuffix                              The size of a chunk (partial file data). (default 5M)
-      \-\-cache\-chunk\-total\-size SizeSuffix                        The total size that the chunks can take up on the local disk. (default 10G)
-      \-\-cache\-db\-path string                                     Directory to store file structure metadata DB. (default \[dq]$HOME/.cache/rclone/cache\-backend\[dq])
-      \-\-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\-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
-      \-\-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 2G)
-      \-\-chunker\-fail\-hard                                        Choose how chunker should handle files with missing or invalid chunks.
-      \-\-chunker\-hash\-type string                                 Choose how chunker handles hash sums. All modes but \[dq]none\[dq] require metadata. (default \[dq]md5\[dq])
-      \-\-chunker\-meta\-format string                               Format of the metadata object or \[dq]none\[dq]. By default \[dq]simplejson\[dq]. (default \[dq]simplejson\[dq])
-      \-\-chunker\-name\-format string                               String format of chunk file names. (default \[dq]*.rclone_chunk.###\[dq])
-      \-\-chunker\-remote string                                    Remote to chunk/unchunk.
-      \-\-chunker\-start\-from int                                   Minimum valid chunk number. Usually 0 or 1. (default 1)
-  \-L, \-\-copy\-links                                               Follow symlinks and copy the pointed to item.
-      \-\-crypt\-directory\-name\-encryption                          Option to either encrypt directory names or leave them intact. (default true)
-      \-\-crypt\-filename\-encryption string                         How to encrypt the filenames. (default \[dq]standard\[dq])
-      \-\-crypt\-password string                                    Password or pass phrase for encryption.
-      \-\-crypt\-password2 string                                   Password or pass phrase for salt. Optional but recommended.
-      \-\-crypt\-remote string                                      Remote to encrypt/decrypt.
-      \-\-crypt\-show\-mapping                                       For all files listed show how the names encrypt.
-      \-\-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 (e.g. file.doc to file.docx). This will confuse sync and reupload every time.
-      \-\-drive\-alternate\-export                                   Use alternate export URLs for google documents export.,
-      \-\-drive\-auth\-owner\-only                                    Only consider files owned by the authenticated user.
-      \-\-drive\-chunk\-size SizeSuffix                              Upload chunk size. Must a power of 2 >= 256k. (default 8M)
-      \-\-drive\-client\-id string                                   Google Application Client Id
-      \-\-drive\-client\-secret string                               Google Application Client Secret
-      \-\-drive\-disable\-http2                                      Disable drive using http2 (default true)
-      \-\-drive\-encoding MultiEncoder                              This sets the encoding for the backend. (default InvalidUtf8)
-      \-\-drive\-export\-formats string                              Comma separated list of preferred formats for downloading Google docs. (default \[dq]docx,xlsx,pptx,svg\[dq])
-      \-\-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\-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\-root\-folder\-id string                              ID of the root folder
-      \-\-drive\-scope string                                       Scope that rclone should use when requesting access from drive.
-      \-\-drive\-server\-side\-across\-configs                         Allow server side operations (eg copy) to work across different drive configs.
-      \-\-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\-size\-as\-quota                                      Show sizes as storage quota usage, not actual size.
-      \-\-drive\-skip\-checksum\-gphotos                              Skip MD5 checksum on Google photos and videos only.
-      \-\-drive\-skip\-gdocs                                         Skip google documents in all listings.
-      \-\-drive\-skip\-shortcuts                                     If set skip shortcut files
-      \-\-drive\-stop\-on\-upload\-limit                               Make upload limit errors be fatal
-      \-\-drive\-team\-drive string                                  ID of the Team Drive
-      \-\-drive\-trashed\-only                                       Only show files that are in the trash.
-      \-\-drive\-upload\-cutoff SizeSuffix                           Cutoff for switching to chunked upload (default 8M)
-      \-\-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\[aq]s are greater, use drive v2 API to download. (default off)
-      \-\-dropbox\-chunk\-size SizeSuffix                            Upload chunk size. (< 150M). (default 48M)
-      \-\-dropbox\-client\-id string                                 Dropbox App Client Id
-      \-\-dropbox\-client\-secret string                             Dropbox App Client Secret
-      \-\-dropbox\-encoding MultiEncoder                            This sets the encoding for the backend. (default Slash,BackSlash,Del,RightSpace,InvalidUtf8,Dot)
-      \-\-dropbox\-impersonate string                               Impersonate this user when using a business account.
-      \-\-fichier\-api\-key string                                   Your API Key, get it from https://1fichier.com/console/params.pl
-      \-\-fichier\-encoding MultiEncoder                            This sets the encoding for the backend. (default Slash,LtGt,DoubleQuote,SingleQuote,BackQuote,Dollar,BackSlash,Del,Ctl,LeftSpace,RightSpace,InvalidUtf8,Dot)
-      \-\-fichier\-shared\-folder string                             If you want to download a shared folder, add this parameter
-      \-\-ftp\-concurrency int                                      Maximum number of FTP simultaneous connections, 0 for unlimited
-      \-\-ftp\-disable\-epsv                                         Disable using EPSV even if server advertises support
-      \-\-ftp\-encoding MultiEncoder                                This sets the encoding for the backend. (default Slash,Del,Ctl,RightSpace,Dot)
-      \-\-ftp\-host string                                          FTP host to connect to
-      \-\-ftp\-no\-check\-certificate                                 Do not verify the TLS certificate of the server
-      \-\-ftp\-pass string                                          FTP password
-      \-\-ftp\-port string                                          FTP port, leave blank to use default (21)
-      \-\-ftp\-tls                                                  Use FTP over TLS (Implicit)
-      \-\-ftp\-user string                                          FTP username, leave blank for current username, $USER
-      \-\-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                                     Google Application Client Id
-      \-\-gcs\-client\-secret string                                 Google Application Client Secret
-      \-\-gcs\-encoding MultiEncoder                                This sets the encoding for the backend. (default Slash,CrLf,InvalidUtf8,Dot)
-      \-\-gcs\-location string                                      Location for the newly created buckets.
-      \-\-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.
-      \-\-gphotos\-client\-id string                                 Google Application Client Id
-      \-\-gphotos\-client\-secret string                             Google Application Client Secret
-      \-\-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)
-      \-\-http\-headers CommaSepList                                Set HTTP headers for all transactions
-      \-\-http\-no\-head                                             Don\[aq]t use HEAD requests to find file sizes in dir listing
-      \-\-http\-no\-slash                                            Set this if the site doesn\[aq]t end directories with /
-      \-\-http\-url string                                          URL of http host to connect to
-      \-\-hubic\-chunk\-size SizeSuffix                              Above this size files will be chunked into a _segments container. (default 5G)
-      \-\-hubic\-client\-id string                                   Hubic Client Id
-      \-\-hubic\-client\-secret string                               Hubic Client Secret
-      \-\-hubic\-encoding MultiEncoder                              This sets the encoding for the backend. (default Slash,InvalidUtf8)
-      \-\-hubic\-no\-chunk                                           Don\[aq]t chunk files during streaming upload.
-      \-\-jottacloud\-encoding MultiEncoder                         This sets 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 10M)
-      \-\-jottacloud\-trashed\-only                                  Only show files that are in the trash.
-      \-\-jottacloud\-unlink                                        Remove existing public link to file/folder with link command rather than creating.
-      \-\-jottacloud\-upload\-resume\-limit SizeSuffix                Files bigger than this can be resumed if the upload fail\[aq]s. (default 10M)
-      \-\-koofr\-encoding MultiEncoder                              This sets the encoding for the backend. (default Slash,BackSlash,Del,Ctl,InvalidUtf8,Dot)
-      \-\-koofr\-endpoint string                                    The Koofr API endpoint to use (default \[dq]https://app.koofr.net\[dq])
-      \-\-koofr\-mountid string                                     Mount ID of the mount to use. If omitted, the primary mount is used.
-      \-\-koofr\-password string                                    Your Koofr password for rclone (generate one at https://app.koofr.net/app/admin/preferences/password)
-      \-\-koofr\-setmtime                                           Does the backend support setting modification time. Set this to false if you use a mount ID that points to a Dropbox or Amazon Drive backend. (default true)
-      \-\-koofr\-user string                                        Your Koofr user name
-  \-l, \-\-links                                                    Translate symlinks to/from regular files with a \[aq].rclonelink\[aq] 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\-encoding MultiEncoder                              This sets the encoding for the backend. (default Slash,Dot)
-      \-\-local\-no\-check\-updated                                   Don\[aq]t check to see if the files change during upload
-      \-\-local\-no\-sparse                                          Disable sparse files for multi\-thread downloads
-      \-\-local\-no\-unicode\-normalization                           Don\[aq]t apply unicode normalization to paths and filenames (Deprecated)
-      \-\-local\-nounc string                                       Disable UNC (long path names) conversion on Windows
-      \-\-mailru\-check\-hash                                        What should copy do if file checksum is mismatched or invalid (default true)
-      \-\-mailru\-encoding MultiEncoder                             This sets the encoding for the backend. (default Slash,LtGt,DoubleQuote,Colon,Question,Asterisk,Pipe,BackSlash,Del,Ctl,InvalidUtf8,Dot)
-      \-\-mailru\-pass string                                       Password
-      \-\-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 \[dq]*.mkv,*.avi,*.mp4,*.mp3,*.zip,*.gz,*.rar,*.pdf\[dq])
-      \-\-mailru\-speedup\-max\-disk SizeSuffix                       This option allows you to disable speedup (put by hash) for large files (default 3G)
-      \-\-mailru\-speedup\-max\-memory SizeSuffix                     Files larger than the size given below will always be hashed on disk. (default 32M)
-      \-\-mailru\-user string                                       User name (usually email)
-      \-\-mega\-debug                                               Output more debug from Mega.
-      \-\-mega\-encoding MultiEncoder                               This sets 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.
-      \-\-mega\-user string                                         User name
-  \-x, \-\-one\-file\-system                                          Don\[aq]t cross filesystem boundaries (unix/macOS only).
-      \-\-onedrive\-chunk\-size SizeSuffix                           Chunk size to upload files with \- must be multiple of 320k (327,680 bytes). (default 10M)
-      \-\-onedrive\-client\-id string                                Microsoft App Client Id
-      \-\-onedrive\-client\-secret string                            Microsoft App Client Secret
-      \-\-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 MultiEncoder                           This sets the encoding for the backend. (default Slash,LtGt,DoubleQuote,Colon,Question,Asterisk,Pipe,Hash,Percent,BackSlash,Del,Ctl,LeftSpace,LeftTilde,RightSpace,RightPeriod,InvalidUtf8,Dot)
-      \-\-onedrive\-expose\-onenote\-files                            Set to make OneNote files show up in directory listings.
-      \-\-onedrive\-server\-side\-across\-configs                      Allow server side operations (eg copy) to work across different onedrive configs.
-      \-\-opendrive\-chunk\-size SizeSuffix                          Files will be uploaded in chunks this size. (default 10M)
-      \-\-opendrive\-encoding MultiEncoder                          This sets the encoding for the backend. (default Slash,LtGt,DoubleQuote,Colon,Question,Asterisk,Pipe,BackSlash,LeftSpace,LeftCrLfHtVt,RightSpace,RightCrLfHtVt,InvalidUtf8,Dot)
-      \-\-opendrive\-password string                                Password.
-      \-\-opendrive\-username string                                Username
-      \-\-pcloud\-client\-id string                                  Pcloud App Client Id
-      \-\-pcloud\-client\-secret string                              Pcloud App Client Secret
-      \-\-pcloud\-encoding MultiEncoder                             This sets the encoding for the backend. (default Slash,BackSlash,Del,Ctl,InvalidUtf8,Dot)
-      \-\-pcloud\-root\-folder\-id string                             Fill in for rclone to use a non root folder as its starting point. (default \[dq]d0\[dq])
-      \-\-premiumizeme\-encoding MultiEncoder                       This sets the encoding for the backend. (default Slash,DoubleQuote,BackSlash,Del,Ctl,InvalidUtf8,Dot)
-      \-\-putio\-encoding MultiEncoder                              This sets the encoding for the backend. (default Slash,BackSlash,Del,Ctl,InvalidUtf8,Dot)
-      \-\-qingstor\-access\-key\-id string                            QingStor Access Key ID
-      \-\-qingstor\-chunk\-size SizeSuffix                           Chunk size to use for uploading. (default 4M)
-      \-\-qingstor\-connection\-retries int                          Number of connection retries. (default 3)
-      \-\-qingstor\-encoding MultiEncoder                           This sets 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. Only applies if access_key_id and secret_access_key is blank.
-      \-\-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 200M)
-      \-\-qingstor\-zone string                                     Zone to connect to.
-      \-\-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 5M)
-      \-\-s3\-copy\-cutoff SizeSuffix                                Cutoff for switching to multipart copy (default 5G)
-      \-\-s3\-disable\-checksum                                      Don\[aq]t store MD5 checksum with object metadata
-      \-\-s3\-encoding MultiEncoder                                 This sets 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\-location\-constraint string                            Location constraint \- must be set to match the Region.
-      \-\-s3\-memory\-pool\-flush\-time Duration                       How often internal memory buffer pools will be flushed. (default 1m0s)
-      \-\-s3\-memory\-pool\-use\-mmap                                  Whether to use mmap buffers in internal memory pool.
-      \-\-s3\-provider string                                       Choose your S3 provider.
-      \-\-s3\-region string                                         Region to connect to.
-      \-\-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\-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                               If using SSE\-C you must provide the secret encryption key used to encrypt/decrypt your data.
-      \-\-s3\-sse\-customer\-key\-md5 string                           If using SSE\-C you must provide the secret encryption key MD5 checksum.
-      \-\-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. (default 4)
-      \-\-s3\-upload\-cutoff SizeSuffix                              Cutoff for switching to chunked upload (default 200M)
-      \-\-s3\-use\-accelerate\-endpoint                               If true use the AWS S3 accelerated endpoint.
-      \-\-s3\-v2\-auth                                               If true use v2 authentication.
-      \-\-seafile\-2fa                                              Two\-factor authentication (\[aq]true\[aq] if the account has 2FA enabled)
-      \-\-seafile\-create\-library                                   Should rclone create a library if it doesn\[aq]t exist
-      \-\-seafile\-encoding MultiEncoder                            This sets the encoding for the backend. (default Slash,DoubleQuote,BackSlash,Ctl,InvalidUtf8)
-      \-\-seafile\-library string                                   Name of the library. Leave blank to access all non\-encrypted libraries.
-      \-\-seafile\-library\-key string                               Library password (for encrypted libraries only). Leave blank if you pass it through the command line.
-      \-\-seafile\-pass string                                      Password
-      \-\-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\-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\-key\-file string                                     Path to PEM\-encoded private key file, leave blank or set key\-use\-agent to use ssh\-agent.
-      \-\-sftp\-key\-file\-pass string                                The passphrase to decrypt the PEM\-encoded private key file.
-      \-\-sftp\-key\-pem string                                      Raw PEM\-encoded private key, If specified, will override key_file parameter.
-      \-\-sftp\-key\-use\-agent                                       When set forces the usage of the ssh\-agent.
-      \-\-sftp\-md5sum\-command string                               The command used to read md5 hashes. Leave blank for autodetect.
-      \-\-sftp\-pass string                                         SSH password, leave blank to use ssh\-agent.
-      \-\-sftp\-path\-override string                                Override path used by SSH connection.
-      \-\-sftp\-port string                                         SSH port, leave blank to use default (22)
-      \-\-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. Leave blank for autodetect.
-      \-\-sftp\-skip\-links                                          Set to skip any symlinks and any other non regular files.
-      \-\-sftp\-use\-insecure\-cipher                                 Enable the use of insecure ciphers and key exchange methods.
-      \-\-sftp\-user string                                         SSH username, leave blank for current username, ncw
-      \-\-sharefile\-chunk\-size SizeSuffix                          Upload chunk size. Must a power of 2 >= 256k. (default 64M)
-      \-\-sharefile\-encoding MultiEncoder                          This sets 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\-upload\-cutoff SizeSuffix                       Cutoff for switching to multipart upload. (default 128M)
-      \-\-skip\-links                                               Don\[aq]t warn about skipped symlinks.
-      \-\-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\-encoding MultiEncoder                          This sets 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 into a _segments container. (default 5G)
-      \-\-swift\-domain string                                      User domain \- optional (v3 auth) (OS_USER_DOMAIN_NAME)
-      \-\-swift\-encoding MultiEncoder                              This sets the encoding for the backend. (default Slash,InvalidUtf8)
-      \-\-swift\-endpoint\-type string                               Endpoint type to choose from the service catalogue (OS_ENDPOINT_TYPE) (default \[dq]public\[dq])
-      \-\-swift\-env\-auth                                           Get swift credentials from environment variables in standard OpenStack form.
-      \-\-swift\-key string                                         API key or password (OS_PASSWORD).
-      \-\-swift\-no\-chunk                                           Don\[aq]t chunk files during streaming upload.
-      \-\-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\-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).
-      \-\-tardigrade\-access\-grant string                           Access Grant.
-      \-\-tardigrade\-api\-key string                                API Key.
-      \-\-tardigrade\-passphrase string                             Encryption Passphrase. To access existing objects enter passphrase used for uploading.
-      \-\-tardigrade\-provider string                               Choose an authentication method. (default \[dq]existing\[dq])
-      \-\-tardigrade\-satellite\-address <nodeid>\[at]<address>:<port>   Satellite Address. Custom satellite address should match the format: <nodeid>\[at]<address>:<port>. (default \[dq]us\-central\-1.tardigrade.io\[dq])
-      \-\-union\-action\-policy string                               Policy to choose upstream on ACTION category. (default \[dq]epall\[dq])
-      \-\-union\-cache\-time int                                     Cache time of usage and free space (in seconds). This option is only useful when a path preserving policy is used. (default 120)
-      \-\-union\-create\-policy string                               Policy to choose upstream on CREATE category. (default \[dq]epmfs\[dq])
-      \-\-union\-search\-policy string                               Policy to choose upstream on SEARCH category. (default \[dq]ff\[dq])
-      \-\-union\-upstreams string                                   List of space separated upstreams.
-      \-\-webdav\-bearer\-token string                               Bearer token instead of user/pass (eg a Macaroon)
-      \-\-webdav\-bearer\-token\-command string                       Command to run to get a bearer token
-      \-\-webdav\-pass string                                       Password.
-      \-\-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\-client\-id string                                  Yandex Client Id
-      \-\-yandex\-client\-secret string                              Yandex Client Secret
-      \-\-yandex\-encoding MultiEncoder                             This sets the encoding for the backend. (default Slash,Del,Ctl,InvalidUtf8,Dot)
-      \-\-yandex\-unlink                                            Remove existing public link to file/folder with link command rather than creating.
+
+## Backend Flags
+
+These flags are available for every command. They control the backends
+and may be set in the config file.
 \f[R]
 .fi
-.SS 1Fichier
-.PP
-This is a backend for the 1fichier (https://1fichier.com) cloud storage
-service.
-Note that a Premium subscription is required to use the API.
-.PP
-Paths are specified as \f[C]remote:path\f[R]
-.PP
-Paths may be as deep as required, eg
-\f[C]remote:directory/subdirectory\f[R].
-.PP
-The initial setup for 1Fichier involves getting the API key from the
-website which you need to do in your browser.
-.PP
-Here is an example of how to make a remote called \f[C]remote\f[R].
-First run:
 .IP
 .nf
 \f[C]
- rclone config
+  \-\-acd\-auth\-url string                                      Auth server URL.
+  \-\-acd\-client\-id string                                     OAuth Client Id
+  \-\-acd\-client\-secret string                                 OAuth Client Secret
+  \-\-acd\-encoding MultiEncoder                                This sets the encoding for the backend. (default Slash,InvalidUtf8,Dot)
+  \-\-acd\-templink\-threshold SizeSuffix                        Files >= this size will be downloaded via their tempLink. (default 9G)
+  \-\-acd\-token string                                         OAuth Access Token as a JSON blob.
+  \-\-acd\-token\-url string                                     Token server url.
+  \-\-acd\-upload\-wait\-per\-gb Duration                          Additional time per GB to wait after a failed complete upload to see if it appears. (default 3m0s)
+  \-\-alias\-remote string                                      Remote or path to alias.
+  \-\-azureblob\-access\-tier string                             Access tier of blob: hot, cool or archive.
+  \-\-azureblob\-account string                                 Storage Account Name (leave blank to use SAS URL or Emulator)
+  \-\-azureblob\-chunk\-size SizeSuffix                          Upload chunk size (<= 100MB). (default 4M)
+  \-\-azureblob\-disable\-checksum                               Don\[aq]t store MD5 checksum with object metadata.
+  \-\-azureblob\-encoding MultiEncoder                          This sets the encoding for the backend. (default Slash,BackSlash,Del,Ctl,RightPeriod,InvalidUtf8)
+  \-\-azureblob\-endpoint string                                Endpoint for the service
+  \-\-azureblob\-key string                                     Storage Account Key (leave blank to use SAS URL or Emulator)
+  \-\-azureblob\-list\-chunk int                                 Size of blob list. (default 5000)
+  \-\-azureblob\-memory\-pool\-flush\-time Duration                How often internal memory buffer pools will be flushed. (default 1m0s)
+  \-\-azureblob\-memory\-pool\-use\-mmap                           Whether to use mmap buffers in internal memory pool.
+  \-\-azureblob\-sas\-url string                                 SAS URL for container level access only
+  \-\-azureblob\-upload\-cutoff SizeSuffix                       Cutoff for switching to chunked upload (<= 256MB). (default 256M)
+  \-\-azureblob\-use\-emulator                                   Uses local storage emulator if provided as \[aq]true\[aq] (leave blank if using real azure storage endpoint)
+  \-\-b2\-account string                                        Account ID or Application Key ID
+  \-\-b2\-chunk\-size SizeSuffix                                 Upload chunk size. Must fit in memory. (default 96M)
+  \-\-b2\-copy\-cutoff SizeSuffix                                Cutoff for switching to multipart copy (default 4G)
+  \-\-b2\-disable\-checksum                                      Disable checksums for large (> upload cutoff) files
+  \-\-b2\-download\-auth\-duration Duration                       Time before the 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 MultiEncoder                                 This sets 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\-memory\-pool\-flush\-time Duration                       How often internal memory buffer pools will be flushed. (default 1m0s)
+  \-\-b2\-memory\-pool\-use\-mmap                                  Whether to use mmap buffers in internal memory pool.
+  \-\-b2\-test\-mode string                                      A flag string for X\-Bz\-Test\-Mode header for debugging.
+  \-\-b2\-upload\-cutoff SizeSuffix                              Cutoff for switching to chunked upload. (default 200M)
+  \-\-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 \[dq]user\[dq])
+  \-\-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\-encoding MultiEncoder                                This sets the encoding for the backend. (default Slash,BackSlash,Del,Ctl,RightSpace,InvalidUtf8,Dot)
+  \-\-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 (>= 50MB). (default 50M)
+  \-\-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 \[dq]$HOME/.cache/rclone/cache\-backend\[dq])
+  \-\-cache\-chunk\-size SizeSuffix                              The size of a chunk (partial file data). (default 5M)
+  \-\-cache\-chunk\-total\-size SizeSuffix                        The total size that the chunks can take up on the local disk. (default 10G)
+  \-\-cache\-db\-path string                                     Directory to store file structure metadata DB. (default \[dq]$HOME/.cache/rclone/cache\-backend\[dq])
+  \-\-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\-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 2G)
+  \-\-chunker\-fail\-hard                                        Choose how chunker should handle files with missing or invalid chunks.
+  \-\-chunker\-hash\-type string                                 Choose how chunker handles hash sums. All modes but \[dq]none\[dq] require metadata. (default \[dq]md5\[dq])
+  \-\-chunker\-meta\-format string                               Format of the metadata object or \[dq]none\[dq]. By default \[dq]simplejson\[dq]. (default \[dq]simplejson\[dq])
+  \-\-chunker\-name\-format string                               String format of chunk file names. (default \[dq]*.rclone_chunk.###\[dq])
+  \-\-chunker\-remote string                                    Remote to chunk/unchunk.
+  \-\-chunker\-start\-from int                                   Minimum valid chunk number. Usually 0 or 1. (default 1)
 \f[R]
 .fi
+\-L, \-\-copy\-links Follow symlinks and copy the pointed to item.
+\-\-crypt\-directory\-name\-encryption Option to either encrypt
+directory names or leave them intact.
+(default true) \-\-crypt\-filename\-encryption string How to encrypt the
+filenames.
+(default \[dq]standard\[dq]) \-\-crypt\-password string Password or pass
+phrase for encryption.
+(obscured) \-\-crypt\-password2 string Password or pass phrase for salt.
+Optional but recommended.
+(obscured) \-\-crypt\-remote string Remote to encrypt/decrypt.
+\-\-crypt\-server\-side\-across\-configs Allow server side operations
+(eg copy) to work across different crypt configs.
+\-\-crypt\-show\-mapping For all files listed show how the names
+encrypt.
+\-\-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 (e.g.
+file.doc to file.docx).
+This will confuse sync and reupload every time.
+\-\-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.
+Must a power of 2 >= 256k.
+(default 8M) \-\-drive\-client\-id string OAuth Client Id
+\-\-drive\-client\-secret string OAuth Client Secret
+\-\-drive\-disable\-http2 Disable drive using http2 (default true)
+\-\-drive\-encoding MultiEncoder This sets the encoding for the backend.
+(default InvalidUtf8) \-\-drive\-export\-formats string Comma separated
+list of preferred formats for downloading Google docs.
+(default \[dq]docx,xlsx,pptx,svg\[dq]) \-\-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\-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\-root\-folder\-id string ID of the root folder
+\-\-drive\-scope string Scope that rclone should use when requesting
+access from drive.
+\-\-drive\-server\-side\-across\-configs Allow server side operations
+(eg copy) to work across different drive configs.
+\-\-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\-size\-as\-quota Show sizes as storage quota usage, not actual
+size.
+\-\-drive\-skip\-checksum\-gphotos Skip MD5 checksum on Google photos
+and videos only.
+\-\-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\-upload\-limit Make upload limit errors be fatal
+\-\-drive\-team\-drive string ID of the 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 8M) \-\-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\[aq]s are greater, use drive v2 API to download.
+(default off) \-\-dropbox\-auth\-url string Auth server URL.
+\-\-dropbox\-chunk\-size SizeSuffix Upload chunk size.
+(< 150M).
+(default 48M) \-\-dropbox\-client\-id string OAuth Client Id
+\-\-dropbox\-client\-secret string OAuth Client Secret
+\-\-dropbox\-encoding MultiEncoder This sets the encoding for the
+backend.
+(default Slash,BackSlash,Del,RightSpace,InvalidUtf8,Dot)
+\-\-dropbox\-impersonate string Impersonate this user when using a
+business account.
+\-\-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\-encoding
+MultiEncoder This sets the encoding for the backend.
+(default
+Slash,LtGt,DoubleQuote,SingleQuote,BackQuote,Dollar,BackSlash,Del,Ctl,LeftSpace,RightSpace,InvalidUtf8,Dot)
+\-\-fichier\-shared\-folder string If you want to download a shared
+folder, add this parameter \-\-ftp\-concurrency int Maximum number of
+FTP simultaneous connections, 0 for unlimited \-\-ftp\-disable\-epsv
+Disable using EPSV even if server advertises support \-\-ftp\-encoding
+MultiEncoder This sets the encoding for the backend.
+(default Slash,Del,Ctl,RightSpace,Dot) \-\-ftp\-explicit\-tls Use FTP
+over TLS (Explicit) \-\-ftp\-host string FTP host to connect to
+\-\-ftp\-no\-check\-certificate Do not verify the TLS certificate of the
+server \-\-ftp\-pass string FTP password (obscured) \-\-ftp\-port string
+FTP port, leave blank to use default (21) \-\-ftp\-tls Use FTPS over TLS
+(Implicit) \-\-ftp\-user string FTP username, leave blank for current
+username, $USER \-\-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\-encoding MultiEncoder This sets the
+encoding for the backend.
+(default Slash,CrLf,InvalidUtf8,Dot) \-\-gcs\-location string Location
+for the newly created buckets.
+\-\-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.
+\-\-gphotos\-auth\-url string Auth server URL.
+\-\-gphotos\-client\-id string OAuth Client Id
+\-\-gphotos\-client\-secret string OAuth Client Secret
+\-\-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.
+\-\-http\-headers CommaSepList Set HTTP headers for all transactions
+\-\-http\-no\-head Don\[aq]t use HEAD requests to find file sizes in dir
+listing \-\-http\-no\-slash Set this if the site doesn\[aq]t end
+directories with / \-\-http\-url string URL of http host to connect to
+\-\-hubic\-auth\-url string Auth server URL.
+\-\-hubic\-chunk\-size SizeSuffix Above this size files will be chunked
+into a _segments container.
+(default 5G) \-\-hubic\-client\-id string OAuth Client Id
+\-\-hubic\-client\-secret string OAuth Client Secret \-\-hubic\-encoding
+MultiEncoder This sets the encoding for the backend.
+(default Slash,InvalidUtf8) \-\-hubic\-no\-chunk Don\[aq]t chunk files
+during streaming upload.
+\-\-hubic\-token string OAuth Access Token as a JSON blob.
+\-\-hubic\-token\-url string Token server url.
+\-\-jottacloud\-encoding MultiEncoder This sets 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 10M) \-\-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\[aq]s.
+(default 10M) \-\-koofr\-encoding MultiEncoder This sets the encoding
+for the backend.
+(default Slash,BackSlash,Del,Ctl,InvalidUtf8,Dot) \-\-koofr\-endpoint
+string The Koofr API endpoint to use (default
+\[dq]https://app.koofr.net\[dq]) \-\-koofr\-mountid string Mount ID of
+the mount to use.
+If omitted, the primary mount is used.
+\-\-koofr\-password string Your Koofr password for rclone (generate one
+at https://app.koofr.net/app/admin/preferences/password) (obscured)
+\-\-koofr\-setmtime Does the backend support setting modification time.
+Set this to false if you use a mount ID that points to a Dropbox or
+Amazon Drive backend.
+(default true) \-\-koofr\-user string Your Koofr user name \-l,
+\-\-links Translate symlinks to/from regular files with a
+\[aq].rclonelink\[aq] 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\-encoding MultiEncoder This sets the encoding for the backend.
+(default Slash,Dot) \-\-local\-no\-check\-updated Don\[aq]t check to see
+if the files change during upload \-\-local\-no\-set\-modtime Disable
+setting modtime \-\-local\-no\-sparse Disable sparse files for
+multi\-thread downloads \-\-local\-no\-unicode\-normalization Don\[aq]t
+apply unicode normalization to paths and filenames (Deprecated)
+\-\-local\-nounc string Disable UNC (long path names) conversion on
+Windows \-\-mailru\-check\-hash What should copy do if file checksum is
+mismatched or invalid (default true) \-\-mailru\-encoding MultiEncoder
+This sets 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
+\[dq]\f[I].mkv,\f[R].avi,\f[I].mp4,\f[R].mp3,\f[I].zip,\f[R].gz,\f[I].rar,\f[R].pdf\[dq])
+\-\-mailru\-speedup\-max\-disk SizeSuffix This option allows you to
+disable speedup (put by hash) for large files (default 3G)
+\-\-mailru\-speedup\-max\-memory SizeSuffix Files larger than the size
+given below will always be hashed on disk.
+(default 32M) \-\-mailru\-user string User name (usually email)
+\-\-mega\-debug Output more debug from Mega.
+\-\-mega\-encoding MultiEncoder This sets 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\-user string User name \-x, \-\-one\-file\-system
+Don\[aq]t cross filesystem boundaries (unix/macOS only).
+\-\-onedrive\-auth\-url string Auth server URL.
+\-\-onedrive\-chunk\-size SizeSuffix Chunk size to upload files with \-
+must be multiple of 320k (327,680 bytes).
+(default 10M) \-\-onedrive\-client\-id string OAuth Client Id
+\-\-onedrive\-client\-secret string OAuth Client Secret
+\-\-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 MultiEncoder This
+sets the encoding for the backend.
+(default
+Slash,LtGt,DoubleQuote,Colon,Question,Asterisk,Pipe,Hash,Percent,BackSlash,Del,Ctl,LeftSpace,LeftTilde,RightSpace,RightPeriod,InvalidUtf8,Dot)
+\-\-onedrive\-expose\-onenote\-files Set to make OneNote files show up
+in directory listings.
+\-\-onedrive\-no\-versions Remove all versions on modifying operations
+\-\-onedrive\-server\-side\-across\-configs Allow server side operations
+(eg copy) to work across different onedrive configs.
+\-\-onedrive\-token string OAuth Access Token as a JSON blob.
+\-\-onedrive\-token\-url string Token server url.
+\-\-opendrive\-chunk\-size SizeSuffix Files will be uploaded in chunks
+this size.
+(default 10M) \-\-opendrive\-encoding MultiEncoder This sets 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\-encoding MultiEncoder This sets
+the encoding for the backend.
+(default Slash,BackSlash,Del,Ctl,InvalidUtf8,Dot) \-\-pcloud\-hostname
+string Hostname to connect to.
+(default \[dq]api.pcloud.com\[dq]) \-\-pcloud\-root\-folder\-id string
+Fill in for rclone to use a non root folder as its starting point.
+(default \[dq]d0\[dq]) \-\-pcloud\-token string OAuth Access Token as a
+JSON blob.
+\-\-pcloud\-token\-url string Token server url.
+\-\-premiumizeme\-encoding MultiEncoder This sets the encoding for the
+backend.
+(default Slash,DoubleQuote,BackSlash,Del,Ctl,InvalidUtf8,Dot)
+\-\-putio\-encoding MultiEncoder This sets the encoding for the backend.
+(default Slash,BackSlash,Del,Ctl,InvalidUtf8,Dot)
+\-\-qingstor\-access\-key\-id string QingStor Access Key ID
+\-\-qingstor\-chunk\-size SizeSuffix Chunk size to use for uploading.
+(default 4M) \-\-qingstor\-connection\-retries int Number of connection
+retries.
+(default 3) \-\-qingstor\-encoding MultiEncoder This sets 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.
+Only applies if access_key_id and secret_access_key is blank.
+\-\-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 200M) \-\-qingstor\-zone string Zone to
+connect to.
+\-\-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 5M) \-\-s3\-copy\-cutoff SizeSuffix Cutoff for switching to
+multipart copy (default 4.656G) \-\-s3\-disable\-checksum Don\[aq]t
+store MD5 checksum with object metadata \-\-s3\-encoding MultiEncoder
+This sets 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\-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\-memory\-pool\-flush\-time Duration How often
+internal memory buffer pools will be flushed.
+(default 1m0s) \-\-s3\-memory\-pool\-use\-mmap Whether to use mmap
+buffers in internal memory pool.
+\-\-s3\-no\-check\-bucket If set don\[aq]t attempt to check the bucket
+exists or create it \-\-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\-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 If using SSE\-C you must provide the
+secret encryption key used to encrypt/decrypt your data.
+\-\-s3\-sse\-customer\-key\-md5 string If using SSE\-C you must provide
+the secret encryption key MD5 checksum.
+\-\-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.
+(default 4) \-\-s3\-upload\-cutoff SizeSuffix Cutoff for switching to
+chunked upload (default 200M) \-\-s3\-use\-accelerate\-endpoint If true
+use the AWS S3 accelerated endpoint.
+\-\-s3\-v2\-auth If true use v2 authentication.
+\-\-seafile\-2fa Two\-factor authentication (\[aq]true\[aq] if the
+account has 2FA enabled) \-\-seafile\-create\-library Should rclone
+create a library if it doesn\[aq]t exist \-\-seafile\-encoding
+MultiEncoder This sets the encoding for the backend.
+(default Slash,DoubleQuote,BackSlash,Ctl,InvalidUtf8)
+\-\-seafile\-library string Name of the library.
+Leave blank to access all non\-encrypted libraries.
+\-\-seafile\-library\-key string Library password (for encrypted
+libraries only).
+Leave blank if you pass it through the command line.
+(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\-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\-key\-file string
+Path to PEM\-encoded private key file, leave blank or set
+key\-use\-agent to use ssh\-agent.
+\-\-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, If
+specified, will override key_file parameter.
+\-\-sftp\-key\-use\-agent When set forces the usage of the ssh\-agent.
+\-\-sftp\-md5sum\-command string The command used to read md5 hashes.
+Leave blank for autodetect.
+\-\-sftp\-pass string SSH password, leave blank to use ssh\-agent.
+(obscured) \-\-sftp\-path\-override string Override path used by SSH
+connection.
+\-\-sftp\-port string SSH port, leave blank to use default (22)
+\-\-sftp\-server\-command string Specifies the path or command to run a
+sftp server on the remote host.
+\-\-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.
+Leave blank for autodetect.
+\-\-sftp\-skip\-links Set to skip any symlinks and any other non regular
+files.
+\-\-sftp\-subsystem string Specifies the SSH2 subsystem on the remote
+host.
+(default \[dq]sftp\[dq]) \-\-sftp\-use\-insecure\-cipher Enable the use
+of insecure ciphers and key exchange methods.
+\-\-sftp\-user string SSH username, leave blank for current username,
+ncw \-\-sharefile\-chunk\-size SizeSuffix Upload chunk size.
+Must a power of 2 >= 256k.
+(default 64M) \-\-sharefile\-encoding MultiEncoder This sets 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\-upload\-cutoff SizeSuffix Cutoff for switching to
+multipart upload.
+(default 128M) \-\-skip\-links Don\[aq]t warn about skipped symlinks.
+\-\-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\-encoding MultiEncoder This sets 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 into a _segments container.
+(default 5G) \-\-swift\-domain string User domain \- optional (v3 auth)
+(OS_USER_DOMAIN_NAME) \-\-swift\-encoding MultiEncoder This sets the
+encoding for the backend.
+(default Slash,InvalidUtf8) \-\-swift\-endpoint\-type string Endpoint
+type to choose from the service catalogue (OS_ENDPOINT_TYPE) (default
+\[dq]public\[dq]) \-\-swift\-env\-auth Get swift credentials from
+environment variables in standard OpenStack form.
+\-\-swift\-key string API key or password (OS_PASSWORD).
+\-\-swift\-no\-chunk Don\[aq]t chunk files during streaming upload.
+\-\-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\-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).
+\-\-tardigrade\-access\-grant string Access Grant.
+\-\-tardigrade\-api\-key string API Key.
+\-\-tardigrade\-passphrase string Encryption Passphrase.
+To access existing objects enter passphrase used for uploading.
+\-\-tardigrade\-provider string Choose an authentication method.
+(default \[dq]existing\[dq]) \-\-tardigrade\-satellite\-address \[at]
+: Satellite Address.
+Custom satellite address should match the format: \[at]
 .PP
+:.
+(default \[dq]us\-central\-1.tardigrade.io\[dq])
+\-\-union\-action\-policy string Policy to choose upstream on ACTION
+category.
+(default \[dq]epall\[dq]) \-\-union\-cache\-time int Cache time of usage
+and free space (in seconds).
+This option is only useful when a path preserving policy is used.
+(default 120) \-\-union\-create\-policy string Policy to choose upstream
+on CREATE category.
+(default \[dq]epmfs\[dq]) \-\-union\-search\-policy string Policy to
+choose upstream on SEARCH category.
+(default \[dq]ff\[dq]) \-\-union\-upstreams string List of space
+separated upstreams.
+\-\-webdav\-bearer\-token string Bearer token instead of user/pass (eg a
+Macaroon) \-\-webdav\-bearer\-token\-command string Command to run to
+get a bearer token \-\-webdav\-pass string Password.
+(obscured) \-\-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\-encoding MultiEncoder This sets
+the encoding for the backend.
+(default Slash,Del,Ctl,InvalidUtf8,Dot) \-\-yandex\-token string OAuth
+Access Token as a JSON blob.
+\-\-yandex\-token\-url string Token server url.
+.IP
+.nf
+\f[C]
+
+ 1Fichier
+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
+
+This is a backend for the [1fichier](https://1fichier.com) cloud
+storage service. Note that a Premium subscription is required to use
+the API.
+
+Paths are specified as \[ga]remote:path\[ga]
+
+Paths may be as deep as required, eg \[ga]remote:directory/subdirectory\[ga].
+
+The initial setup for 1Fichier involves getting the API key from the website which you
+need to do in your browser.
+
+Here is an example of how to make a remote called \[ga]remote\[ga].  First run:
+
+     rclone config
+
 This will guide you through an interactive setup process:
-.IP
-.nf
-\f[C]
-No remotes found \- make a new one
-n) New remote
-s) Set configuration password
-q) Quit config
-n/s/q> n
-name> remote
-Type of storage to configure.
-Enter a string value. Press Enter for the default (\[dq]\[dq]).
-Choose a number from below, or type in your own value
-[snip]
-XX / 1Fichier
-   \[rs] \[dq]fichier\[dq]
-[snip]
-Storage> 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 (\[dq]\[dq]).
+\f[R]
+.fi
+.PP
+No remotes found \- make a new one n) New remote s) Set configuration
+password q) Quit config n/s/q> n name> remote Type of storage to
+configure.
+Enter a string value.
+Press Enter for the default (\[dq]\[dq]).
+Choose a number from below, or type in your own value [snip] XX /
+1Fichier \ \[dq]fichier\[dq] [snip] Storage> fichier ** See help for
+fichier backend at: https://rclone.org/fichier/ **
+.PP
+Your API Key, get it from https://1fichier.com/console/params.pl Enter a
+string value.
+Press Enter for the default (\[dq]\[dq]).
 api_key> example_key
+.PP
+Edit advanced config?
+(y/n) y) Yes n) No y/n> Remote config
+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\- [remote] type = fichier api_key
+= example_key \-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\- y) Yes this is OK
+e) Edit this remote d) Delete this remote y/e/d> y
+.IP
+.nf
+\f[C]
+
+Once configured you can then use \[ga]rclone\[ga] like this,
 
-Edit advanced config? (y/n)
-y) Yes
-n) No
-y/n> 
-Remote config
-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
-[remote]
-type = fichier
-api_key = example_key
-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
-y) Yes this is OK
-e) Edit this remote
-d) Delete this remote
-y/e/d> y
-\f[R]
-.fi
-.PP
-Once configured you can then use \f[C]rclone\f[R] like this,
-.PP
 List directories in top level of your 1Fichier account
-.IP
-.nf
-\f[C]
-rclone lsd remote:
-\f[R]
-.fi
-.PP
+
+    rclone lsd remote:
+
 List all the files in your 1Fichier account
-.IP
-.nf
-\f[C]
-rclone ls remote:
-\f[R]
-.fi
-.PP
+
+    rclone ls remote:
+
 To copy a local directory to a 1Fichier directory called backup
-.IP
-.nf
-\f[C]
-rclone copy /home/source remote:backup
-\f[R]
-.fi
-.SS Modified time and hashes
-.PP
-1Fichier does not support modification times.
-It supports the Whirlpool hash algorithm.
-.SS Duplicated files
-.PP
-1Fichier can have two files with exactly the same name and path (unlike
-a normal file system).
-.PP
+
+    rclone copy /home/source remote:backup
+
+### Modified time and hashes ###
+
+1Fichier does not support modification times. It supports the Whirlpool hash algorithm.
+
+### Duplicated files ###
+
+1Fichier can have two files with exactly the same name and path (unlike a
+normal file system).
+
 Duplicated files cause problems with the syncing and you will see
 messages in the log about duplicates.
-.SS Restricted filename characters
-.PP
-In addition to the default restricted characters
-set (https://rclone.org/overview/#restricted-characters) the following
-characters are also replaced:
-.PP
-.TS
-tab(@);
-l c c.
-T{
-Character
-T}@T{
-Value
-T}@T{
-Replacement
-T}
-_
-T{
-\[rs]
-T}@T{
-0x5C
-T}@T{
-\[uFF3C]
-T}
-T{
-<
-T}@T{
-0x3C
-T}@T{
-\[uFF1C]
-T}
-T{
->
-T}@T{
-0x3E
-T}@T{
-\[uFF1E]
-T}
-T{
-\[dq]
-T}@T{
-0x22
-T}@T{
-\[uFF02]
-T}
-T{
-$
-T}@T{
-0x24
-T}@T{
-\[uFF04]
-T}
-T{
-\[ga]
-T}@T{
-0x60
-T}@T{
-\[uFF40]
-T}
-T{
-\[cq]
-T}@T{
-0x27
-T}@T{
-\[uFF07]
-T}
-.TE
-.PP
+
+#### Restricted filename characters
+
+In addition to the [default restricted characters set](https://rclone.org/overview/#restricted\-characters)
+the following characters are also replaced:
+
+| Character | Value | Replacement |
+| \-\-\-\-\-\-\-\-\- |:\-\-\-\-\-:|:\-\-\-\-\-\-\-\-\-\-\-:|
+| \[rs]         | 0x5C  | \[uFF3C]           |
+| <         | 0x3C  | \[uFF1C]           |
+| >         | 0x3E  | \[uFF1E]           |
+| \[dq]         | 0x22  | \[uFF02]           |
+| $         | 0x24  | \[uFF04]           |
+| \[ga]         | 0x60  | \[uFF40]           |
+| \[aq]         | 0x27  | \[uFF07]           |
+
 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:
-.PP
-.TS
-tab(@);
-l c c.
-T{
-Character
-T}@T{
-Value
-T}@T{
-Replacement
-T}
-_
-T{
-SP
-T}@T{
-0x20
-T}@T{
-\[u2420]
-T}
-.TE
-.PP
-Invalid UTF\-8 bytes will also be
-replaced (https://rclone.org/overview/#invalid-utf8), as they can\[cq]t
-be used in JSON strings.
-.SS Standard Options
-.PP
+
+| Character | Value | Replacement |
+| \-\-\-\-\-\-\-\-\- |:\-\-\-\-\-:|:\-\-\-\-\-\-\-\-\-\-\-:|
+| SP        | 0x20  | \[u2420]           |
+
+Invalid UTF\-8 bytes will also be [replaced](https://rclone.org/overview/#invalid\-utf8),
+as they can\[aq]t be used in JSON strings.
+
+
+### Standard Options
+
 Here are the standard options specific to fichier (1Fichier).
-.SS \[en]fichier\-api\-key
-.PP
+
+#### \-\-fichier\-api\-key
+
 Your API Key, get it from https://1fichier.com/console/params.pl
-.IP \[bu] 2
-Config: api_key
-.IP \[bu] 2
-Env Var: RCLONE_FICHIER_API_KEY
-.IP \[bu] 2
-Type: string
-.IP \[bu] 2
-Default: \[dq]\[dq]
-.SS Advanced Options
-.PP
+
+\- Config:      api_key
+\- Env Var:     RCLONE_FICHIER_API_KEY
+\- Type:        string
+\- Default:     \[dq]\[dq]
+
+### Advanced Options
+
 Here are the advanced options specific to fichier (1Fichier).
-.SS \[en]fichier\-shared\-folder
-.PP
+
+#### \-\-fichier\-shared\-folder
+
 If you want to download a shared folder, add this parameter
-.IP \[bu] 2
-Config: shared_folder
-.IP \[bu] 2
-Env Var: RCLONE_FICHIER_SHARED_FOLDER
-.IP \[bu] 2
-Type: string
-.IP \[bu] 2
-Default: \[dq]\[dq]
-.SS \[en]fichier\-encoding
-.PP
+
+\- Config:      shared_folder
+\- Env Var:     RCLONE_FICHIER_SHARED_FOLDER
+\- Type:        string
+\- Default:     \[dq]\[dq]
+
+#### \-\-fichier\-encoding
+
 This sets the encoding for the backend.
-.PP
-See: the encoding section in the
-overview (https://rclone.org/overview/#encoding) for more info.
-.IP \[bu] 2
-Config: encoding
-.IP \[bu] 2
-Env Var: RCLONE_FICHIER_ENCODING
-.IP \[bu] 2
-Type: MultiEncoder
-.IP \[bu] 2
-Default:
-Slash,LtGt,DoubleQuote,SingleQuote,BackQuote,Dollar,BackSlash,Del,Ctl,LeftSpace,RightSpace,InvalidUtf8,Dot
-.SS Alias
-.PP
-The \f[C]alias\f[R] remote provides a new name for another remote.
-.PP
-Paths may be as deep as required or a local path, eg
-\f[C]remote:directory/subdirectory\f[R] or
-\f[C]/directory/subdirectory\f[R].
-.PP
-During the initial setup with \f[C]rclone config\f[R] you will specify
-the target remote.
-The target remote can either be a local path or another remote.
-.PP
-Subfolders can be used in target remote.
-Assume an alias remote named \f[C]backup\f[R] with the target
-\f[C]mydrive:private/backup\f[R].
-Invoking \f[C]rclone mkdir backup:desktop\f[R] is exactly the same as
-invoking \f[C]rclone mkdir mydrive:private/backup/desktop\f[R].
-.PP
-There will be no special handling of paths containing \f[C]..\f[R]
-segments.
-Invoking \f[C]rclone mkdir backup:../desktop\f[R] is exactly the same as
-invoking \f[C]rclone mkdir mydrive:private/backup/../desktop\f[R].
-The empty path is not allowed as a remote.
-To alias the current directory use \f[C].\f[R] instead.
-.PP
-Here is an example of how to make an alias called \f[C]remote\f[R] for
-local folder.
+
+See: the [encoding section in the overview](https://rclone.org/overview/#encoding) for more info.
+
+\- Config:      encoding
+\- Env Var:     RCLONE_FICHIER_ENCODING
+\- Type:        MultiEncoder
+\- Default:     Slash,LtGt,DoubleQuote,SingleQuote,BackQuote,Dollar,BackSlash,Del,Ctl,LeftSpace,RightSpace,InvalidUtf8,Dot
+
+
+
+ Alias
+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
+
+The \[ga]alias\[ga] remote provides a new name for another remote.
+
+Paths may be as deep as required or a local path, 
+eg \[ga]remote:directory/subdirectory\[ga] or \[ga]/directory/subdirectory\[ga].
+
+During the initial setup with \[ga]rclone config\[ga] you will specify the target
+remote. The target remote can either be a local path or another remote.
+
+Subfolders can be used in target remote. Assume an alias remote named \[ga]backup\[ga]
+with the target \[ga]mydrive:private/backup\[ga]. Invoking \[ga]rclone mkdir backup:desktop\[ga]
+is exactly the same as invoking \[ga]rclone mkdir mydrive:private/backup/desktop\[ga].
+
+There will be no special handling of paths containing \[ga]..\[ga] segments.
+Invoking \[ga]rclone mkdir backup:../desktop\[ga] is exactly the same as invoking
+\[ga]rclone mkdir mydrive:private/backup/../desktop\[ga].
+The empty path is not allowed as a remote. To alias the current directory
+use \[ga].\[ga] instead.
+
+Here is an example of how to make an alias called \[ga]remote\[ga] for local folder.
 First run:
-.IP
-.nf
-\f[C]
- rclone config
+
+     rclone config
+
+This will guide you through an interactive setup process:
 \f[R]
 .fi
 .PP
-This will guide you through an interactive setup process:
+No remotes found \- make a new one n) New remote s) Set configuration
+password q) Quit config n/s/q> n name> remote Type of storage to
+configure.
+Choose a number from below, or type in your own value [snip] XX / Alias
+for an existing remote \ \[dq]alias\[dq] [snip] Storage> alias Remote or
+path to alias.
+Can be \[dq]myremote:path/to/dir\[dq], \[dq]myremote:bucket\[dq],
+\[dq]myremote:\[dq] or \[dq]/local/path\[dq].
+remote> /mnt/storage/backup Remote config
+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\- [remote] remote =
+/mnt/storage/backup \-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\- y) Yes this
+is OK e) Edit this remote d) Delete this remote y/e/d> y Current
+remotes:
+.PP
+Name Type ==== ==== remote alias
+.IP "e)" 3
+Edit existing remote
+.IP "f)" 3
+New remote
+.IP "g)" 3
+Delete remote
+.IP "h)" 3
+Rename remote
+.IP "i)" 3
+Copy remote
+.IP "j)" 3
+Set configuration password
+.IP "k)" 3
+Quit config e/n/d/r/c/s/q> q
 .IP
 .nf
 \f[C]
-No remotes found \- make a new one
-n) New remote
-s) Set configuration password
-q) Quit config
-n/s/q> n
-name> remote
-Type of storage to configure.
-Choose a number from below, or type in your own value
-[snip]
-XX / Alias for an existing remote
-   \[rs] \[dq]alias\[dq]
-[snip]
-Storage> alias
+
+Once configured you can then use \[ga]rclone\[ga] like this,
+
+List directories in top level in \[ga]/mnt/storage/backup\[ga]
+
+    rclone lsd remote:
+
+List all the files in \[ga]/mnt/storage/backup\[ga]
+
+    rclone ls remote:
+
+Copy another local directory to the alias directory called source
+
+    rclone copy /home/source remote:source
+
+
+### Standard Options
+
+Here are the standard options specific to alias (Alias for an existing remote).
+
+#### \-\-alias\-remote
+
 Remote or path to alias.
 Can be \[dq]myremote:path/to/dir\[dq], \[dq]myremote:bucket\[dq], \[dq]myremote:\[dq] or \[dq]/local/path\[dq].
-remote> /mnt/storage/backup
-Remote config
-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
-[remote]
-remote = /mnt/storage/backup
-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
-y) Yes this is OK
-e) Edit this remote
-d) Delete this remote
-y/e/d> y
-Current remotes:
 
-Name                 Type
-====                 ====
-remote               alias
+\- Config:      remote
+\- Env Var:     RCLONE_ALIAS_REMOTE
+\- Type:        string
+\- Default:     \[dq]\[dq]
+
+
+
+ Amazon Drive
+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
 
-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> q
-\f[R]
-.fi
-.PP
-Once configured you can then use \f[C]rclone\f[R] like this,
-.PP
-List directories in top level in \f[C]/mnt/storage/backup\f[R]
-.IP
-.nf
-\f[C]
-rclone lsd remote:
-\f[R]
-.fi
-.PP
-List all the files in \f[C]/mnt/storage/backup\f[R]
-.IP
-.nf
-\f[C]
-rclone ls remote:
-\f[R]
-.fi
-.PP
-Copy another local directory to the alias directory called source
-.IP
-.nf
-\f[C]
-rclone copy /home/source remote:source
-\f[R]
-.fi
-.SS Standard Options
-.PP
-Here are the standard options specific to alias (Alias for an existing
-remote).
-.SS \[en]alias\-remote
-.PP
-Remote or path to alias.
-Can be \[lq]myremote:path/to/dir\[rq], \[lq]myremote:bucket\[rq],
-\[lq]myremote:\[rq] or \[lq]/local/path\[rq].
-.IP \[bu] 2
-Config: remote
-.IP \[bu] 2
-Env Var: RCLONE_ALIAS_REMOTE
-.IP \[bu] 2
-Type: string
-.IP \[bu] 2
-Default: \[dq]\[dq]
-.SS Amazon Drive
-.PP
 Amazon Drive, formerly known as Amazon Cloud Drive, is a cloud storage
 service run by Amazon for consumers.
-.SS Status
-.PP
-\f[B]Important:\f[R] rclone supports Amazon Drive only if you have your
-own set of API keys.
-Unfortunately the Amazon Drive developer
-program (https://developer.amazon.com/amazon-drive) is now closed to new
-entries so if you don\[cq]t already have your own set of keys you will
+
+## Status
+
+**Important:** rclone supports Amazon Drive only if you have your own
+set of API keys. Unfortunately the [Amazon Drive developer
+program](https://developer.amazon.com/amazon\-drive) is now closed to
+new entries so if you don\[aq]t already have your own set of keys you will
 not be able to use rclone with Amazon Drive.
-.PP
+
 For the history on why rclone no longer has a set of Amazon Drive API
-keys see the
-forum (https://forum.rclone.org/t/rclone-has-been-banned-from-amazon-drive/2314).
-.PP
-If you happen to know anyone who works at Amazon then please ask them to
-re\-instate rclone into the Amazon Drive developer program \- thanks!
-.SS Setup
-.PP
-The initial setup for Amazon Drive involves getting a token from Amazon
-which you need to do in your browser.
-\f[C]rclone config\f[R] walks you through it.
-.PP
-The configuration process for Amazon Drive may involve using an oauth
-proxy (https://github.com/ncw/oauthproxy).
-This is used to keep the Amazon credentials out of the source code.
-The proxy runs in Google\[cq]s very secure App Engine environment and
-doesn\[cq]t store any credentials which pass through it.
-.PP
-Since rclone doesn\[cq]t currently have its own Amazon Drive credentials
-so you will either need to have your own \f[C]client_id\f[R] and
-\f[C]client_secret\f[R] with Amazon Drive, or use a third party oauth
-proxy in which case you will need to enter \f[C]client_id\f[R],
-\f[C]client_secret\f[R], \f[C]auth_url\f[R] and \f[C]token_url\f[R].
-.PP
-Note also if you are not using Amazon\[cq]s \f[C]auth_url\f[R] and
-\f[C]token_url\f[R], (ie you filled in something for those) then if
-setting up on a remote machine you can only use the copying the config
-method of
-configuration (https://rclone.org/remote_setup/#configuring-by-copying-the-config-file)
-\- \f[C]rclone authorize\f[R] will not work.
-.PP
-Here is an example of how to make a remote called \f[C]remote\f[R].
-First run:
-.IP
-.nf
-\f[C]
- rclone config
-\f[R]
-.fi
-.PP
+keys see [the forum](https://forum.rclone.org/t/rclone\-has\-been\-banned\-from\-amazon\-drive/2314).
+
+If you happen to know anyone who works at Amazon then please ask them
+to re\-instate rclone into the Amazon Drive developer program \- thanks!
+
+## Setup
+
+The initial setup for Amazon Drive involves getting a token from
+Amazon which you need to do in your browser.  \[ga]rclone config\[ga] walks
+you through it.
+
+The configuration process for Amazon Drive may involve using an [oauth
+proxy](https://github.com/ncw/oauthproxy). This is used to keep the
+Amazon credentials out of the source code.  The proxy runs in Google\[aq]s
+very secure App Engine environment and doesn\[aq]t store any credentials
+which pass through it.
+
+Since rclone doesn\[aq]t currently have its own Amazon Drive credentials
+so you will either need to have your own \[ga]client_id\[ga] and
+\[ga]client_secret\[ga] with Amazon Drive, or use a third party oauth proxy
+in which case you will need to enter \[ga]client_id\[ga], \[ga]client_secret\[ga],
+\[ga]auth_url\[ga] and \[ga]token_url\[ga].
+
+Note also if you are not using Amazon\[aq]s \[ga]auth_url\[ga] and \[ga]token_url\[ga],
+(ie you filled in something for those) then if setting up on a remote
+machine you can only use the [copying the config method of
+configuration](https://rclone.org/remote_setup/#configuring\-by\-copying\-the\-config\-file)
+\- \[ga]rclone authorize\[ga] will not work.
+
+Here is an example of how to make a remote called \[ga]remote\[ga].  First run:
+
+     rclone config
+
 This will guide you through an interactive setup process:
-.IP
-.nf
-\f[C]
-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> n
-name> remote
-Type of storage to configure.
-Choose a number from below, or type in your own value
-[snip]
-XX / Amazon Drive
-   \[rs] \[dq]amazon cloud drive\[dq]
-[snip]
-Storage> amazon cloud drive
+\f[R]
+.fi
+.PP
+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> n
+name> remote Type of storage to configure.
+Choose a number from below, or type in your own value [snip] XX / Amazon
+Drive \ \[dq]amazon cloud drive\[dq] [snip] Storage> amazon cloud drive
 Amazon Application Client Id \- required.
-client_id> your client ID goes here
-Amazon Application Client Secret \- required.
-client_secret> your client secret goes here
-Auth server URL \- leave blank to use Amazon\[aq]s.
-auth_url> Optional auth URL
-Token server url \- leave blank to use Amazon\[aq]s.
-token_url> Optional token URL
-Remote config
-Make sure your Redirect URL is set to \[dq]http://127.0.0.1:53682/\[dq] in your custom config.
+client_id> your client ID goes here Amazon Application Client Secret \-
+required.
+client_secret> your client secret goes here Auth server URL \- leave
+blank to use Amazon\[aq]s.
+auth_url> Optional auth URL Token server url \- leave blank to use
+Amazon\[aq]s.
+token_url> Optional token URL Remote config Make sure your Redirect URL
+is set to \[dq]http://127.0.0.1:53682/\[dq] in your custom config.
 Use auto config?
- * Say Y if not sure
- * Say N if you are working on a remote or headless machine
-y) Yes
-n) No
-y/n> y
-If your browser doesn\[aq]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
-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
-[remote]
-client_id = your client ID goes here
-client_secret = your client secret goes here
-auth_url = Optional auth URL
-token_url = Optional token URL
-token = {\[dq]access_token\[dq]:\[dq]xxxxxxxxxxxxxxxxxxxxxxx\[dq],\[dq]token_type\[dq]:\[dq]bearer\[dq],\[dq]refresh_token\[dq]:\[dq]xxxxxxxxxxxxxxxxxx\[dq],\[dq]expiry\[dq]:\[dq]2015\-09\-06T16:07:39.658438471+01:00\[dq]}
-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
-y) Yes this is OK
-e) Edit this remote
-d) Delete this remote
-y/e/d> y
-\f[R]
-.fi
-.PP
-See the remote setup docs (https://rclone.org/remote_setup/) for how to
-set it up on a machine with no Internet browser available.
-.PP
+* Say Y if not sure * Say N if you are working on a remote or headless
+machine y) Yes n) No y/n> y If your browser doesn\[aq]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 \-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\- [remote] client_id =
+your client ID goes here client_secret = your client secret goes here
+auth_url = Optional auth URL token_url = Optional token URL token =
+{\[dq]access_token\[dq]:\[dq]xxxxxxxxxxxxxxxxxxxxxxx\[dq],\[dq]token_type\[dq]:\[dq]bearer\[dq],\[dq]refresh_token\[dq]:\[dq]xxxxxxxxxxxxxxxxxx\[dq],\[dq]expiry\[dq]:\[dq]2015\-09\-06T16:07:39.658438471+01:00\[dq]}
+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\- y) Yes this is OK e) Edit this
+remote d) Delete this remote y/e/d> y
+.IP
+.nf
+\f[C]
+
+See the [remote setup docs](https://rclone.org/remote_setup/) for how to set it up on a
+machine with no Internet browser available.
+
 Note that rclone runs a webserver on your local machine to collect the
-token as returned from Amazon.
-This only runs from the moment it opens your browser to the moment you
-get back the verification code.
-This is on \f[C]http://127.0.0.1:53682/\f[R] and this it may require you
-to unblock it temporarily if you are running a host firewall.
-.PP
-Once configured you can then use \f[C]rclone\f[R] like this,
-.PP
+token as returned from Amazon. This only runs from the moment it
+opens your browser to the moment you get back the verification
+code.  This is on \[ga]http://127.0.0.1:53682/\[ga] and this it may require
+you to unblock it temporarily if you are running a host firewall.
+
+Once configured you can then use \[ga]rclone\[ga] like this,
+
 List directories in top level of your Amazon Drive
-.IP
-.nf
-\f[C]
-rclone lsd remote:
-\f[R]
-.fi
-.PP
+
+    rclone lsd remote:
+
 List all the files in your Amazon Drive
-.IP
-.nf
-\f[C]
-rclone ls remote:
-\f[R]
-.fi
-.PP
+
+    rclone ls remote:
+
 To copy a local directory to an Amazon Drive directory called backup
-.IP
-.nf
-\f[C]
-rclone copy /home/source remote:backup
-\f[R]
-.fi
-.SS Modified time and MD5SUMs
-.PP
-Amazon Drive doesn\[cq]t allow modification times to be changed via the
-API so these won\[cq]t be accurate or used for syncing.
-.PP
+
+    rclone copy /home/source remote:backup
+
+### Modified time and MD5SUMs ###
+
+Amazon Drive doesn\[aq]t allow modification times to be changed via
+the API so these won\[aq]t be accurate or used for syncing.
+
 It does store MD5SUMs so for a more accurate sync, you can use the
-\f[C]\-\-checksum\f[R] flag.
-.SS Restricted filename characters
-.PP
-.TS
-tab(@);
-l c c.
-T{
-Character
-T}@T{
-Value
-T}@T{
-Replacement
-T}
-_
-T{
-NUL
-T}@T{
-0x00
-T}@T{
-\[u2400]
-T}
-T{
-/
-T}@T{
-0x2F
-T}@T{
-\[uFF0F]
-T}
-.TE
-.PP
-Invalid UTF\-8 bytes will also be
-replaced (https://rclone.org/overview/#invalid-utf8), as they can\[cq]t
-be used in JSON strings.
-.SS Deleting files
-.PP
-Any files you delete with rclone will end up in the trash.
-Amazon don\[cq]t provide an API to permanently delete files, nor to
-empty the trash, so you will have to do that with one of Amazon\[cq]s
-apps or via the Amazon Drive website.
-As of November 17, 2016, files are automatically deleted by Amazon from
-the trash after 30 days.
-.SS Using with non \f[C].com\f[R] Amazon accounts
-.PP
-Let\[cq]s say you usually use \f[C]amazon.co.uk\f[R].
-When you authenticate with rclone it will take you to an
-\f[C]amazon.com\f[R] page to log in.
-Your \f[C]amazon.co.uk\f[R] email and password should work here just
-fine.
-.SS Standard Options
-.PP
-Here are the standard options specific to amazon cloud drive (Amazon
-Drive).
-.SS \[en]acd\-client\-id
-.PP
-Amazon Application Client ID.
-.IP \[bu] 2
-Config: client_id
-.IP \[bu] 2
-Env Var: RCLONE_ACD_CLIENT_ID
-.IP \[bu] 2
-Type: string
-.IP \[bu] 2
-Default: \[dq]\[dq]
-.SS \[en]acd\-client\-secret
-.PP
-Amazon Application Client Secret.
-.IP \[bu] 2
-Config: client_secret
-.IP \[bu] 2
-Env Var: RCLONE_ACD_CLIENT_SECRET
-.IP \[bu] 2
-Type: string
-.IP \[bu] 2
-Default: \[dq]\[dq]
-.SS Advanced Options
-.PP
-Here are the advanced options specific to amazon cloud drive (Amazon
-Drive).
-.SS \[en]acd\-auth\-url
-.PP
+\[ga]\-\-checksum\[ga] flag.
+
+#### Restricted filename characters
+
+| Character | Value | Replacement |
+| \-\-\-\-\-\-\-\-\- |:\-\-\-\-\-:|:\-\-\-\-\-\-\-\-\-\-\-:|
+| NUL       | 0x00  | \[u2400]           |
+| /         | 0x2F  | \[uFF0F]          |
+
+Invalid UTF\-8 bytes will also be [replaced](https://rclone.org/overview/#invalid\-utf8),
+as they can\[aq]t be used in JSON strings.
+
+### Deleting files ###
+
+Any files you delete with rclone will end up in the trash.  Amazon
+don\[aq]t provide an API to permanently delete files, nor to empty the
+trash, so you will have to do that with one of Amazon\[aq]s apps or via
+the Amazon Drive website. As of November 17, 2016, files are 
+automatically deleted by Amazon from the trash after 30 days.
+
+### Using with non \[ga].com\[ga] Amazon accounts ###
+
+Let\[aq]s say you usually use \[ga]amazon.co.uk\[ga]. When you authenticate with
+rclone it will take you to an \[ga]amazon.com\[ga] page to log in.  Your
+\[ga]amazon.co.uk\[ga] email and password should work here just fine.
+
+
+### Standard Options
+
+Here are the standard options specific to amazon cloud drive (Amazon Drive).
+
+#### \-\-acd\-client\-id
+
+OAuth Client Id
+Leave blank normally.
+
+\- Config:      client_id
+\- Env Var:     RCLONE_ACD_CLIENT_ID
+\- Type:        string
+\- Default:     \[dq]\[dq]
+
+#### \-\-acd\-client\-secret
+
+OAuth Client Secret
+Leave blank normally.
+
+\- Config:      client_secret
+\- Env Var:     RCLONE_ACD_CLIENT_SECRET
+\- Type:        string
+\- Default:     \[dq]\[dq]
+
+### Advanced Options
+
+Here are the advanced options specific to amazon cloud drive (Amazon Drive).
+
+#### \-\-acd\-token
+
+OAuth Access Token as a JSON blob.
+
+\- Config:      token
+\- Env Var:     RCLONE_ACD_TOKEN
+\- Type:        string
+\- Default:     \[dq]\[dq]
+
+#### \-\-acd\-auth\-url
+
 Auth server URL.
-Leave blank to use Amazon\[cq]s.
-.IP \[bu] 2
-Config: auth_url
-.IP \[bu] 2
-Env Var: RCLONE_ACD_AUTH_URL
-.IP \[bu] 2
-Type: string
-.IP \[bu] 2
-Default: \[dq]\[dq]
-.SS \[en]acd\-token\-url
-.PP
+Leave blank to use the provider defaults.
+
+\- Config:      auth_url
+\- Env Var:     RCLONE_ACD_AUTH_URL
+\- Type:        string
+\- Default:     \[dq]\[dq]
+
+#### \-\-acd\-token\-url
+
 Token server url.
-leave blank to use Amazon\[cq]s.
-.IP \[bu] 2
-Config: token_url
-.IP \[bu] 2
-Env Var: RCLONE_ACD_TOKEN_URL
-.IP \[bu] 2
-Type: string
-.IP \[bu] 2
-Default: \[dq]\[dq]
-.SS \[en]acd\-checkpoint
-.PP
+Leave blank to use the provider defaults.
+
+\- Config:      token_url
+\- Env Var:     RCLONE_ACD_TOKEN_URL
+\- Type:        string
+\- Default:     \[dq]\[dq]
+
+#### \-\-acd\-checkpoint
+
 Checkpoint for internal polling (debug).
-.IP \[bu] 2
-Config: checkpoint
-.IP \[bu] 2
-Env Var: RCLONE_ACD_CHECKPOINT
-.IP \[bu] 2
-Type: string
-.IP \[bu] 2
-Default: \[dq]\[dq]
-.SS \[en]acd\-upload\-wait\-per\-gb
-.PP
-Additional time per GB to wait after a failed complete upload to see if
-it appears.
-.PP
+
+\- Config:      checkpoint
+\- Env Var:     RCLONE_ACD_CHECKPOINT
+\- Type:        string
+\- Default:     \[dq]\[dq]
+
+#### \-\-acd\-upload\-wait\-per\-gb
+
+Additional time per GB to wait after a failed complete upload to see if it appears.
+
 Sometimes Amazon Drive gives an error when a file has been fully
-uploaded but the file appears anyway after a little while.
-This happens sometimes for files over 1GB in size and nearly every time
-for files bigger than 10GB.
-This parameter controls the time rclone waits for the file to appear.
-.PP
-The default value for this parameter is 3 minutes per GB, so by default
-it will wait 3 minutes for every GB uploaded to see if the file appears.
-.PP
-You can disable this feature by setting it to 0.
-This may cause conflict errors as rclone retries the failed upload but
-the file will most likely appear correctly eventually.
-.PP
-These values were determined empirically by observing lots of uploads of
-big files for a range of file sizes.
-.PP
-Upload with the \[lq]\-v\[rq] flag to see more info about what rclone is
-doing in this situation.
-.IP \[bu] 2
-Config: upload_wait_per_gb
-.IP \[bu] 2
-Env Var: RCLONE_ACD_UPLOAD_WAIT_PER_GB
-.IP \[bu] 2
-Type: Duration
-.IP \[bu] 2
-Default: 3m0s
-.SS \[en]acd\-templink\-threshold
-.PP
+uploaded but the file appears anyway after a little while.  This
+happens sometimes for files over 1GB in size and nearly every time for
+files bigger than 10GB. This parameter controls the time rclone waits
+for the file to appear.
+
+The default value for this parameter is 3 minutes per GB, so by
+default it will wait 3 minutes for every GB uploaded to see if the
+file appears.
+
+You can disable this feature by setting it to 0. This may cause
+conflict errors as rclone retries the failed upload but the file will
+most likely appear correctly eventually.
+
+These values were determined empirically by observing lots of uploads
+of big files for a range of file sizes.
+
+Upload with the \[dq]\-v\[dq] flag to see more info about what rclone is doing
+in this situation.
+
+\- Config:      upload_wait_per_gb
+\- Env Var:     RCLONE_ACD_UPLOAD_WAIT_PER_GB
+\- Type:        Duration
+\- Default:     3m0s
+
+#### \-\-acd\-templink\-threshold
+
 Files >= this size will be downloaded via their tempLink.
-.PP
-Files this size or more will be downloaded via their \[lq]tempLink\[rq].
-This is to work around a problem with Amazon Drive which blocks
-downloads of files bigger than about 10GB.
-The default for this is 9GB which shouldn\[cq]t need to be changed.
-.PP
-To download files above this threshold, rclone requests a
-\[lq]tempLink\[rq] which downloads the file through a temporary URL
-directly from the underlying S3 storage.
-.IP \[bu] 2
-Config: templink_threshold
-.IP \[bu] 2
-Env Var: RCLONE_ACD_TEMPLINK_THRESHOLD
-.IP \[bu] 2
-Type: SizeSuffix
-.IP \[bu] 2
-Default: 9G
-.SS \[en]acd\-encoding
-.PP
+
+Files this size or more will be downloaded via their \[dq]tempLink\[dq]. This
+is to work around a problem with Amazon Drive which blocks downloads
+of files bigger than about 10GB.  The default for this is 9GB which
+shouldn\[aq]t need to be changed.
+
+To download files above this threshold, rclone requests a \[dq]tempLink\[dq]
+which downloads the file through a temporary URL directly from the
+underlying S3 storage.
+
+\- Config:      templink_threshold
+\- Env Var:     RCLONE_ACD_TEMPLINK_THRESHOLD
+\- Type:        SizeSuffix
+\- Default:     9G
+
+#### \-\-acd\-encoding
+
 This sets the encoding for the backend.
-.PP
-See: the encoding section in the
-overview (https://rclone.org/overview/#encoding) for more info.
-.IP \[bu] 2
-Config: encoding
-.IP \[bu] 2
-Env Var: RCLONE_ACD_ENCODING
-.IP \[bu] 2
-Type: MultiEncoder
-.IP \[bu] 2
-Default: Slash,InvalidUtf8,Dot
-.SS Limitations
-.PP
-Note that Amazon Drive is case insensitive so you can\[cq]t have a file
-called \[lq]Hello.doc\[rq] and one called \[lq]hello.doc\[rq].
-.PP
-Amazon Drive has rate limiting so you may notice errors in the sync (429
-errors).
-rclone will automatically retry the sync up to 3 times by default (see
-\f[C]\-\-retries\f[R] flag) which should hopefully work around this
-problem.
-.PP
-Amazon Drive has an internal limit of file sizes that can be uploaded to
-the service.
-This limit is not officially published, but all files larger than this
-will fail.
-.PP
+
+See: the [encoding section in the overview](https://rclone.org/overview/#encoding) for more info.
+
+\- Config:      encoding
+\- Env Var:     RCLONE_ACD_ENCODING
+\- Type:        MultiEncoder
+\- Default:     Slash,InvalidUtf8,Dot
+
+
+
+### Limitations ###
+
+Note that Amazon Drive is case insensitive so you can\[aq]t have a
+file called \[dq]Hello.doc\[dq] and one called \[dq]hello.doc\[dq].
+
+Amazon Drive has rate limiting so you may notice errors in the
+sync (429 errors).  rclone will automatically retry the sync up to 3
+times by default (see \[ga]\-\-retries\[ga] flag) which should hopefully work
+around this problem.
+
+Amazon Drive has an internal limit of file sizes that can be uploaded
+to the service. This limit is not officially published, but all files
+larger than this will fail.
+
 At the time of writing (Jan 2016) is in the area of 50GB per file.
 This means that larger files are likely to fail.
-.PP
+
 Unfortunately there is no way for rclone to see that this failure is
 because of file size, so it will retry the operation, as any other
-failure.
-To avoid this problem, use \f[C]\-\-max\-size 50000M\f[R] option to
-limit the maximum size of uploaded files.
-Note that \f[C]\-\-max\-size\f[R] does not split files into segments, it
-only ignores files over this size.
-.SS Amazon S3 Storage Providers
-.PP
+failure. To avoid this problem, use \[ga]\-\-max\-size 50000M\[ga] option to limit
+the maximum size of uploaded files. Note that \[ga]\-\-max\-size\[ga] does not split
+files into segments, it only ignores files over this size.
+
+ Amazon S3 Storage Providers
+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
+
 The S3 backend can be used with a number of different providers:
-.IP \[bu] 2
-AWS S3
-.IP \[bu] 2
-Alibaba Cloud (Aliyun) Object Storage System (OSS)
-.IP \[bu] 2
-Ceph
-.IP \[bu] 2
-DigitalOcean Spaces
-.IP \[bu] 2
-Dreamhost
-.IP \[bu] 2
-IBM COS S3
-.IP \[bu] 2
-Minio
-.IP \[bu] 2
-Scaleway
-.IP \[bu] 2
-StackPath
-.IP \[bu] 2
-Wasabi
-.PP
-Paths are specified as \f[C]remote:bucket\f[R] (or \f[C]remote:\f[R] for
-the \f[C]lsd\f[R] command.) You may put subdirectories in too, eg
-\f[C]remote:bucket/path/to/dir\f[R].
-.PP
+
+
+\- AWS S3
+\- Alibaba Cloud (Aliyun) Object Storage System (OSS)
+\- Ceph
+\- DigitalOcean Spaces
+\- Dreamhost
+\- IBM COS S3
+\- Minio
+\- Scaleway
+\- StackPath
+\- Wasabi
+
+
+Paths are specified as \[ga]remote:bucket\[ga] (or \[ga]remote:\[ga] for the \[ga]lsd\[ga]
+command.)  You may put subdirectories in too, eg \[ga]remote:bucket/path/to/dir\[ga].
+
 Once you have made a remote (see the provider specific section above)
 you can use it like this:
-.PP
+
 See all buckets
-.IP
-.nf
-\f[C]
-rclone lsd remote:
-\f[R]
-.fi
-.PP
+
+    rclone lsd remote:
+
 Make a new bucket
-.IP
-.nf
-\f[C]
-rclone mkdir remote:bucket
-\f[R]
-.fi
-.PP
+
+    rclone mkdir remote:bucket
+
 List the contents of a bucket
-.IP
-.nf
-\f[C]
-rclone ls remote:bucket
-\f[R]
-.fi
-.PP
-Sync \f[C]/home/local/directory\f[R] to the remote bucket, deleting any
-excess files in the bucket.
-.IP
-.nf
-\f[C]
-rclone sync /home/local/directory remote:bucket
-\f[R]
-.fi
-.SS AWS S3
-.PP
-Here is an example of making an s3 configuration.
-First run
-.IP
-.nf
-\f[C]
-rclone config
-\f[R]
-.fi
-.PP
+
+    rclone ls remote:bucket
+
+Sync \[ga]/home/local/directory\[ga] to the remote bucket, deleting any excess
+files in the bucket.
+
+    rclone sync \-i /home/local/directory remote:bucket
+
+## AWS S3 {#amazon\-s3}
+
+Here is an example of making an s3 configuration.  First run
+
+    rclone config
+
 This will guide you through an interactive setup process.
+\f[R]
+.fi
+.PP
+No remotes found \- make a new one n) New remote s) Set configuration
+password q) Quit config n/s/q> n name> remote Type of storage to
+configure.
+Choose a number from below, or type in your own value [snip] XX / Amazon
+S3 Compliant Storage Providers (AWS, Ceph, Dreamhost, IBM COS, Minio)
+\ \[dq]s3\[dq] [snip] Storage> s3 Choose your S3 provider.
+Choose a number from below, or type in your own value 1 / Amazon Web
+Services (AWS) S3 \ \[dq]AWS\[dq] 2 / Ceph Object Storage
+\ \[dq]Ceph\[dq] 3 / Digital Ocean Spaces \ \[dq]DigitalOcean\[dq] 4 /
+Dreamhost DreamObjects \ \[dq]Dreamhost\[dq] 5 / IBM COS S3
+\ \[dq]IBMCOS\[dq] 6 / Minio Object Storage \ \[dq]Minio\[dq] 7 / Wasabi
+Object Storage \ \[dq]Wasabi\[dq] 8 / Any other S3 compatible provider
+\ \[dq]Other\[dq] provider> 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 \ \[dq]false\[dq] 2 / Get AWS credentials
+from the environment (env vars or IAM) \ \[dq]true\[dq] env_auth> 1 AWS
+Access Key ID \- leave blank for anonymous access or runtime
+credentials.
+access_key_id> XXX AWS Secret Access Key (password) \- leave blank for
+anonymous access or runtime credentials.
+secret_access_key> 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.
+\ \[dq]us\-east\-1\[dq] / US East (Ohio) Region 2 | Needs location
+constraint us\-east\-2.
+\ \[dq]us\-east\-2\[dq] / US West (Oregon) Region 3 | Needs location
+constraint us\-west\-2.
+\ \[dq]us\-west\-2\[dq] / US West (Northern California) Region 4 | Needs
+location constraint us\-west\-1.
+\ \[dq]us\-west\-1\[dq] / Canada (Central) Region 5 | Needs location
+constraint ca\-central\-1.
+\ \[dq]ca\-central\-1\[dq] / EU (Ireland) Region 6 | Needs location
+constraint EU or eu\-west\-1.
+\ \[dq]eu\-west\-1\[dq] / EU (London) Region 7 | Needs location
+constraint eu\-west\-2.
+\ \[dq]eu\-west\-2\[dq] / EU (Frankfurt) Region 8 | Needs location
+constraint eu\-central\-1.
+\ \[dq]eu\-central\-1\[dq] / Asia Pacific (Singapore) Region 9 | Needs
+location constraint ap\-southeast\-1.
+\ \[dq]ap\-southeast\-1\[dq] / Asia Pacific (Sydney) Region 10 | Needs
+location constraint ap\-southeast\-2.
+\ \[dq]ap\-southeast\-2\[dq] / Asia Pacific (Tokyo) Region 11 | Needs
+location constraint ap\-northeast\-1.
+\ \[dq]ap\-northeast\-1\[dq] / Asia Pacific (Seoul) 12 | Needs location
+constraint ap\-northeast\-2.
+\ \[dq]ap\-northeast\-2\[dq] / Asia Pacific (Mumbai) 13 | Needs location
+constraint ap\-south\-1.
+\ \[dq]ap\-south\-1\[dq] / Asia Patific (Hong Kong) Region 14 | Needs
+location constraint ap\-east\-1.
+\ \[dq]ap\-east\-1\[dq] / South America (Sao Paulo) Region 15 | Needs
+location constraint sa\-east\-1.
+\ \[dq]sa\-east\-1\[dq] region> 1 Endpoint for S3 API.
+Leave blank if using AWS to use the default endpoint for the region.
+endpoint> 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.
+\ \[dq]\[dq] 2 / US East (Ohio) Region.
+\ \[dq]us\-east\-2\[dq] 3 / US West (Oregon) Region.
+\ \[dq]us\-west\-2\[dq] 4 / US West (Northern California) Region.
+\ \[dq]us\-west\-1\[dq] 5 / Canada (Central) Region.
+\ \[dq]ca\-central\-1\[dq] 6 / EU (Ireland) Region.
+\ \[dq]eu\-west\-1\[dq] 7 / EU (London) Region.
+\ \[dq]eu\-west\-2\[dq] 8 / EU Region.
+\ \[dq]EU\[dq] 9 / Asia Pacific (Singapore) Region.
+\ \[dq]ap\-southeast\-1\[dq] 10 / Asia Pacific (Sydney) Region.
+\ \[dq]ap\-southeast\-2\[dq] 11 / Asia Pacific (Tokyo) Region.
+\ \[dq]ap\-northeast\-1\[dq] 12 / Asia Pacific (Seoul)
+\ \[dq]ap\-northeast\-2\[dq] 13 / Asia Pacific (Mumbai)
+\ \[dq]ap\-south\-1\[dq] 14 / Asia Pacific (Hong Kong)
+\ \[dq]ap\-east\-1\[dq] 15 / South America (Sao Paulo) Region.
+\ \[dq]sa\-east\-1\[dq] location_constraint> 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).
+\ \[dq]private\[dq] 2 / Owner gets FULL_CONTROL.
+The AllUsers group gets READ access.
+\ \[dq]public\-read\[dq] / Owner gets FULL_CONTROL.
+The AllUsers group gets READ and WRITE access.
+3 | Granting this on a bucket is generally not recommended.
+\ \[dq]public\-read\-write\[dq] 4 / Owner gets FULL_CONTROL.
+The AuthenticatedUsers group gets READ access.
+\ \[dq]authenticated\-read\[dq] / 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.
+\ \[dq]bucket\-owner\-read\[dq] / 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.
+\ \[dq]bucket\-owner\-full\-control\[dq] acl> 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
+\ \[dq]\[dq] 2 / AES256 \ \[dq]AES256\[dq] server_side_encryption> 1 The
+storage class to use when storing objects in S3.
+Choose a number from below, or type in your own value 1 / Default
+\ \[dq]\[dq] 2 / Standard storage class \ \[dq]STANDARD\[dq] 3 / Reduced
+redundancy storage class \ \[dq]REDUCED_REDUNDANCY\[dq] 4 / Standard
+Infrequent Access storage class \ \[dq]STANDARD_IA\[dq] 5 / One Zone
+Infrequent Access storage class \ \[dq]ONEZONE_IA\[dq] 6 / Glacier
+storage class \ \[dq]GLACIER\[dq] 7 / Glacier Deep Archive storage class
+\ \[dq]DEEP_ARCHIVE\[dq] 8 / Intelligent\-Tiering storage class
+\ \[dq]INTELLIGENT_TIERING\[dq] storage_class> 1 Remote config
+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\- [remote] 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 =
+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\- y) Yes this is OK e) Edit this
+remote d) Delete this remote y/e/d>
 .IP
 .nf
 \f[C]
-No remotes found \- make a new one
-n) New remote
-s) Set configuration password
-q) Quit config
-n/s/q> n
-name> remote
-Type of storage to configure.
-Choose a number from below, or type in your own value
-[snip]
-XX / Amazon S3 Compliant Storage Providers (AWS, Ceph, Dreamhost, IBM COS, Minio)
-   \[rs] \[dq]s3\[dq]
-[snip]
-Storage> s3
-Choose your S3 provider.
-Choose a number from below, or type in your own value
- 1 / Amazon Web Services (AWS) S3
-   \[rs] \[dq]AWS\[dq]
- 2 / Ceph Object Storage
-   \[rs] \[dq]Ceph\[dq]
- 3 / Digital Ocean Spaces
-   \[rs] \[dq]DigitalOcean\[dq]
- 4 / Dreamhost DreamObjects
-   \[rs] \[dq]Dreamhost\[dq]
- 5 / IBM COS S3
-   \[rs] \[dq]IBMCOS\[dq]
- 6 / Minio Object Storage
-   \[rs] \[dq]Minio\[dq]
- 7 / Wasabi Object Storage
-   \[rs] \[dq]Wasabi\[dq]
- 8 / Any other S3 compatible provider
-   \[rs] \[dq]Other\[dq]
-provider> 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
-   \[rs] \[dq]false\[dq]
- 2 / Get AWS credentials from the environment (env vars or IAM)
-   \[rs] \[dq]true\[dq]
-env_auth> 1
-AWS Access Key ID \- leave blank for anonymous access or runtime credentials.
-access_key_id> XXX
-AWS Secret Access Key (password) \- leave blank for anonymous access or runtime credentials.
-secret_access_key> 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.
-   \[rs] \[dq]us\-east\-1\[dq]
-   / US East (Ohio) Region
- 2 | Needs location constraint us\-east\-2.
-   \[rs] \[dq]us\-east\-2\[dq]
-   / US West (Oregon) Region
- 3 | Needs location constraint us\-west\-2.
-   \[rs] \[dq]us\-west\-2\[dq]
-   / US West (Northern California) Region
- 4 | Needs location constraint us\-west\-1.
-   \[rs] \[dq]us\-west\-1\[dq]
-   / Canada (Central) Region
- 5 | Needs location constraint ca\-central\-1.
-   \[rs] \[dq]ca\-central\-1\[dq]
-   / EU (Ireland) Region
- 6 | Needs location constraint EU or eu\-west\-1.
-   \[rs] \[dq]eu\-west\-1\[dq]
-   / EU (London) Region
- 7 | Needs location constraint eu\-west\-2.
-   \[rs] \[dq]eu\-west\-2\[dq]
-   / EU (Frankfurt) Region
- 8 | Needs location constraint eu\-central\-1.
-   \[rs] \[dq]eu\-central\-1\[dq]
-   / Asia Pacific (Singapore) Region
- 9 | Needs location constraint ap\-southeast\-1.
-   \[rs] \[dq]ap\-southeast\-1\[dq]
-   / Asia Pacific (Sydney) Region
-10 | Needs location constraint ap\-southeast\-2.
-   \[rs] \[dq]ap\-southeast\-2\[dq]
-   / Asia Pacific (Tokyo) Region
-11 | Needs location constraint ap\-northeast\-1.
-   \[rs] \[dq]ap\-northeast\-1\[dq]
-   / Asia Pacific (Seoul)
-12 | Needs location constraint ap\-northeast\-2.
-   \[rs] \[dq]ap\-northeast\-2\[dq]
-   / Asia Pacific (Mumbai)
-13 | Needs location constraint ap\-south\-1.
-   \[rs] \[dq]ap\-south\-1\[dq]
-   / Asia Patific (Hong Kong) Region
-14 | Needs location constraint ap\-east\-1.
-   \[rs] \[dq]ap\-east\-1\[dq]
-   / South America (Sao Paulo) Region
-15 | Needs location constraint sa\-east\-1.
-   \[rs] \[dq]sa\-east\-1\[dq]
-region> 1
-Endpoint for S3 API.
-Leave blank if using AWS to use the default endpoint for the region.
-endpoint> 
-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.
-   \[rs] \[dq]\[dq]
- 2 / US East (Ohio) Region.
-   \[rs] \[dq]us\-east\-2\[dq]
- 3 / US West (Oregon) Region.
-   \[rs] \[dq]us\-west\-2\[dq]
- 4 / US West (Northern California) Region.
-   \[rs] \[dq]us\-west\-1\[dq]
- 5 / Canada (Central) Region.
-   \[rs] \[dq]ca\-central\-1\[dq]
- 6 / EU (Ireland) Region.
-   \[rs] \[dq]eu\-west\-1\[dq]
- 7 / EU (London) Region.
-   \[rs] \[dq]eu\-west\-2\[dq]
- 8 / EU Region.
-   \[rs] \[dq]EU\[dq]
- 9 / Asia Pacific (Singapore) Region.
-   \[rs] \[dq]ap\-southeast\-1\[dq]
-10 / Asia Pacific (Sydney) Region.
-   \[rs] \[dq]ap\-southeast\-2\[dq]
-11 / Asia Pacific (Tokyo) Region.
-   \[rs] \[dq]ap\-northeast\-1\[dq]
-12 / Asia Pacific (Seoul)
-   \[rs] \[dq]ap\-northeast\-2\[dq]
-13 / Asia Pacific (Mumbai)
-   \[rs] \[dq]ap\-south\-1\[dq]
-14 / Asia Pacific (Hong Kong)
-   \[rs] \[dq]ap\-east\-1\[dq]
-15 / South America (Sao Paulo) Region.
-   \[rs] \[dq]sa\-east\-1\[dq]
-location_constraint> 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).
-   \[rs] \[dq]private\[dq]
- 2 / Owner gets FULL_CONTROL. The AllUsers group gets READ access.
-   \[rs] \[dq]public\-read\[dq]
-   / Owner gets FULL_CONTROL. The AllUsers group gets READ and WRITE access.
- 3 | Granting this on a bucket is generally not recommended.
-   \[rs] \[dq]public\-read\-write\[dq]
- 4 / Owner gets FULL_CONTROL. The AuthenticatedUsers group gets READ access.
-   \[rs] \[dq]authenticated\-read\[dq]
-   / 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.
-   \[rs] \[dq]bucket\-owner\-read\[dq]
-   / 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.
-   \[rs] \[dq]bucket\-owner\-full\-control\[dq]
-acl> 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
-   \[rs] \[dq]\[dq]
- 2 / AES256
-   \[rs] \[dq]AES256\[dq]
-server_side_encryption> 1
-The storage class to use when storing objects in S3.
-Choose a number from below, or type in your own value
- 1 / Default
-   \[rs] \[dq]\[dq]
- 2 / Standard storage class
-   \[rs] \[dq]STANDARD\[dq]
- 3 / Reduced redundancy storage class
-   \[rs] \[dq]REDUCED_REDUNDANCY\[dq]
- 4 / Standard Infrequent Access storage class
-   \[rs] \[dq]STANDARD_IA\[dq]
- 5 / One Zone Infrequent Access storage class
-   \[rs] \[dq]ONEZONE_IA\[dq]
- 6 / Glacier storage class
-   \[rs] \[dq]GLACIER\[dq]
- 7 / Glacier Deep Archive storage class
-   \[rs] \[dq]DEEP_ARCHIVE\[dq]
- 8 / Intelligent\-Tiering storage class
-   \[rs] \[dq]INTELLIGENT_TIERING\[dq]
-storage_class> 1
-Remote config
-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
-[remote]
-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 = 
-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
-y) Yes this is OK
-e) Edit this remote
-d) Delete this remote
-y/e/d> 
-\f[R]
-.fi
-.SS \[en]fast\-list
-.PP
-This remote supports \f[C]\-\-fast\-list\f[R] which allows you to use
-fewer transactions in exchange for more memory.
-See the rclone docs (https://rclone.org/docs/#fast-list) for more
-details.
-.SS \[en]update and \[en]use\-server\-modtime
-.PP
-As noted below, the modified time is stored on metadata on the object.
-It 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 because it requires an extra API call to retrieve the
+
+### \-\-fast\-list ###
+
+This remote supports \[ga]\-\-fast\-list\[ga] which allows you to use fewer
+transactions in exchange for more memory. See the [rclone
+docs](https://rclone.org/docs/#fast\-list) for more details.
+
+### \-\-update and \-\-use\-server\-modtime ###
+
+As noted below, the modified time is stored on metadata on the object. It 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 because it requires an extra API call to retrieve the
 metadata.
-.PP
-For many operations, the time the object was last uploaded to the remote
-is sufficient to determine if it is \[lq]dirty\[rq].
-By using \f[C]\-\-update\f[R] along with
-\f[C]\-\-use\-server\-modtime\f[R], you can avoid the extra API call and
-simply upload files whose local modtime is newer than the time it was
-last uploaded.
-.SS Modified time
-.PP
+
+For many operations, the time the object was last uploaded to the remote is
+sufficient to determine if it is \[dq]dirty\[dq]. By using \[ga]\-\-update\[ga] along with
+\[ga]\-\-use\-server\-modtime\[ga], you can avoid the extra API call and simply upload
+files whose local modtime is newer than the time it was last uploaded.
+
+### Modified time ###
+
 The modified time is stored as metadata on the object as
-\f[C]X\-Amz\-Meta\-Mtime\f[R] as floating point since the epoch accurate
-to 1 ns.
-.PP
-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.
-.SS Restricted filename characters
-.PP
+\[ga]X\-Amz\-Meta\-Mtime\[ga] as floating point since the epoch accurate to 1 ns.
+
+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.
+
+### Cleanup ###
+
+If you run \[ga]rclone cleanup s3:bucket\[ga] then it will remove all pending
+multipart uploads older than 24 hours. You can use the \[ga]\-i\[ga] flag to
+see exactly what it will do. If you want more control over the expiry
+date then run \[ga]rclone backend cleanup s3:bucket \-o max\-age=1h\[ga] to
+expire all uploads older than one hour. You can use \[ga]rclone backend
+list\-multipart\-uploads s3:bucket\[ga] to see the pending multipart
+uploads.
+
+#### Restricted filename characters
+
 S3 allows any valid UTF\-8 string as a key.
-.PP
-Invalid UTF\-8 bytes will be
-replaced (https://rclone.org/overview/#invalid-utf8), as they can\[cq]t
-be used in XML.
-.PP
+
+Invalid UTF\-8 bytes will be [replaced](https://rclone.org/overview/#invalid\-utf8), as
+they can\[aq]t be used in XML.
+
 The following characters are replaced since these are problematic when
 dealing with the REST API:
-.PP
-.TS
-tab(@);
-l c c.
-T{
-Character
-T}@T{
-Value
-T}@T{
-Replacement
-T}
-_
-T{
-NUL
-T}@T{
-0x00
-T}@T{
-\[u2400]
-T}
-T{
-/
-T}@T{
-0x2F
-T}@T{
-\[uFF0F]
-T}
-.TE
-.PP
-The encoding will also encode these file names as they don\[cq]t seem to
+
+| Character | Value | Replacement |
+| \-\-\-\-\-\-\-\-\- |:\-\-\-\-\-:|:\-\-\-\-\-\-\-\-\-\-\-:|
+| NUL       | 0x00  | \[u2400]           |
+| /         | 0x2F  | \[uFF0F]           |
+
+The encoding will also encode these file names as they don\[aq]t seem to
 work with the SDK properly:
-.PP
-.TS
-tab(@);
-l c.
-T{
-File name
-T}@T{
-Replacement
-T}
-_
-T{
-\&.
-T}@T{
-\[uFF0E]
-T}
-T{
-\&..
-T}@T{
-\[uFF0E]\[uFF0E]
-T}
-.TE
-.SS Multipart uploads
-.PP
-rclone supports multipart uploads with S3 which means that it can upload
-files bigger than 5GB.
-.PP
-Note that files uploaded \f[I]both\f[R] with multipart upload
-\f[I]and\f[R] through crypt remotes do not have MD5 sums.
-.PP
+
+| File name | Replacement |
+| \-\-\-\-\-\-\-\-\- |:\-\-\-\-\-\-\-\-\-\-\-:|
+| .         | \[uFF0E]          |
+| ..        | \[uFF0E]\[uFF0E]         |
+
+### Multipart uploads ###
+
+rclone supports multipart uploads with S3 which means that it can
+upload files bigger than 5GB.
+
+Note that files uploaded *both* with multipart upload *and* through
+crypt remotes do not have MD5 sums.
+
 rclone switches from single part uploads to multipart uploads at the
-point specified by \f[C]\-\-s3\-upload\-cutoff\f[R].
-This can be a maximum of 5GB and a minimum of 0 (ie always upload
-multipart files).
-.PP
+point specified by \[ga]\-\-s3\-upload\-cutoff\[ga].  This can be a maximum of 5GB
+and a minimum of 0 (ie always upload multipart files).
+
 The chunk sizes used in the multipart upload are specified by
-\f[C]\-\-s3\-chunk\-size\f[R] and the number of chunks uploaded
-concurrently is specified by \f[C]\-\-s3\-upload\-concurrency\f[R].
-.PP
-Multipart uploads will use \f[C]\-\-transfers\f[R] *
-\f[C]\-\-s3\-upload\-concurrency\f[R] * \f[C]\-\-s3\-chunk\-size\f[R]
-extra memory.
-Single part uploads to not use extra memory.
-.PP
+\[ga]\-\-s3\-chunk\-size\[ga] and the number of chunks uploaded concurrently is
+specified by \[ga]\-\-s3\-upload\-concurrency\[ga].
+
+Multipart uploads will use \[ga]\-\-transfers\[ga] * \[ga]\-\-s3\-upload\-concurrency\[ga] *
+\[ga]\-\-s3\-chunk\-size\[ga] extra memory.  Single part uploads to not use extra
+memory.
+
 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.
-.PP
-Increasing \f[C]\-\-s3\-upload\-concurrency\f[R] will increase
-throughput (8 would be a sensible value) and increasing
-\f[C]\-\-s3\-chunk\-size\f[R] 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.
-.SS Buckets and Regions
-.PP
-With Amazon S3 you can list buckets (\f[C]rclone lsd\f[R]) 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,
-\f[C]incorrect region, the bucket is not in \[aq]XXX\[aq] region\f[R].
-.SS Authentication
-.PP
-There are a number of ways to supply \f[C]rclone\f[R] with a set of AWS
+
+Increasing \[ga]\-\-s3\-upload\-concurrency\[ga] will increase throughput (8 would
+be a sensible value) and increasing \[ga]\-\-s3\-chunk\-size\[ga] 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.
+
+
+### Buckets and Regions ###
+
+With Amazon S3 you can list buckets (\[ga]rclone lsd\[ga]) 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, \[ga]incorrect region, the bucket is not in \[aq]XXX\[aq]
+region\[ga].
+
+### Authentication ###
+
+There are a number of ways to supply \[ga]rclone\[ga] with a set of AWS
 credentials, with and without using the environment.
-.PP
+
 The different authentication methods are tried in this order:
-.IP \[bu] 2
-Directly in the rclone configuration file (\f[C]env_auth = false\f[R] in
-the config file):
-.RS 2
-.IP \[bu] 2
-\f[C]access_key_id\f[R] and \f[C]secret_access_key\f[R] are required.
-.IP \[bu] 2
-\f[C]session_token\f[R] can be optionally set when using AWS STS.
-.RE
-.IP \[bu] 2
-Runtime configuration (\f[C]env_auth = true\f[R] in the config file):
-.RS 2
-.IP \[bu] 2
-Export the following environment variables before running
-\f[C]rclone\f[R]:
-.RS 2
-.IP \[bu] 2
-Access Key ID: \f[C]AWS_ACCESS_KEY_ID\f[R] or \f[C]AWS_ACCESS_KEY\f[R]
-.IP \[bu] 2
-Secret Access Key: \f[C]AWS_SECRET_ACCESS_KEY\f[R] or
-\f[C]AWS_SECRET_KEY\f[R]
-.IP \[bu] 2
-Session Token: \f[C]AWS_SESSION_TOKEN\f[R] (optional)
-.RE
-.IP \[bu] 2
-Or, use a named
-profile (https://docs.aws.amazon.com/cli/latest/userguide/cli-multiple-profiles.html):
-.RS 2
-.IP \[bu] 2
-Profile files are standard files used by AWS CLI tools
-.IP \[bu] 2
-By default it will use the profile in your home directory (eg
-\f[C]\[ti]/.aws/credentials\f[R] on unix based systems) file and the
-\[lq]default\[rq] profile, to change set these environment variables:
-.RS 2
-.IP \[bu] 2
-\f[C]AWS_SHARED_CREDENTIALS_FILE\f[R] to control which file.
-.IP \[bu] 2
-\f[C]AWS_PROFILE\f[R] to control which profile to use.
-.RE
-.RE
-.IP \[bu] 2
-Or, run \f[C]rclone\f[R] in an ECS task with an IAM role (AWS only).
-.IP \[bu] 2
-Or, run \f[C]rclone\f[R] on an EC2 instance with an IAM role (AWS only).
-.IP \[bu] 2
-Or, run \f[C]rclone\f[R] in an EKS pod with an IAM role that is
-associated with a service account (AWS only).
-.RE
-.PP
-If none of these option actually end up providing \f[C]rclone\f[R] with
-AWS credentials then S3 interaction will be non\-authenticated (see
-below).
-.SS S3 Permissions
-.PP
-When using the \f[C]sync\f[R] subcommand of \f[C]rclone\f[R] the
-following minimum permissions are required to be available on the bucket
-being written to:
-.IP \[bu] 2
-\f[C]ListBucket\f[R]
-.IP \[bu] 2
-\f[C]DeleteObject\f[R]
-.IP \[bu] 2
-\f[C]GetObject\f[R]
-.IP \[bu] 2
-\f[C]PutObject\f[R]
-.IP \[bu] 2
-\f[C]PutObjectACL\f[R]
-.PP
-When using the \f[C]lsd\f[R] subcommand, the \f[C]ListAllMyBuckets\f[R]
-permission is required.
-.PP
+
+ \- Directly in the rclone configuration file (\[ga]env_auth = false\[ga] in the config file):
+   \- \[ga]access_key_id\[ga] and \[ga]secret_access_key\[ga] are required.
+   \- \[ga]session_token\[ga] can be optionally set when using AWS STS.
+ \- Runtime configuration (\[ga]env_auth = true\[ga] in the config file):
+   \- Export the following environment variables before running \[ga]rclone\[ga]:
+     \- Access Key ID: \[ga]AWS_ACCESS_KEY_ID\[ga] or \[ga]AWS_ACCESS_KEY\[ga]
+     \- Secret Access Key: \[ga]AWS_SECRET_ACCESS_KEY\[ga] or \[ga]AWS_SECRET_KEY\[ga]
+     \- Session Token: \[ga]AWS_SESSION_TOKEN\[ga] (optional)
+   \- Or, use a [named profile](https://docs.aws.amazon.com/cli/latest/userguide/cli\-multiple\-profiles.html):
+     \- Profile files are standard files used by AWS CLI tools
+     \- By default it will use the profile in your home directory (eg \[ga]\[ti]/.aws/credentials\[ga] on unix based systems) file and the \[dq]default\[dq] profile, to change set these environment variables:
+         \- \[ga]AWS_SHARED_CREDENTIALS_FILE\[ga] to control which file.
+         \- \[ga]AWS_PROFILE\[ga] to control which profile to use.
+   \- Or, run \[ga]rclone\[ga] in an ECS task with an IAM role (AWS only).
+   \- Or, run \[ga]rclone\[ga] on an EC2 instance with an IAM role (AWS only).
+   \- Or, run \[ga]rclone\[ga] in an EKS pod with an IAM role that is associated with a service account (AWS only).
+
+If none of these option actually end up providing \[ga]rclone\[ga] with AWS
+credentials then S3 interaction will be non\-authenticated (see below).
+
+### S3 Permissions ###
+
+When using the \[ga]sync\[ga] subcommand of \[ga]rclone\[ga] the following minimum
+permissions are required to be available on the bucket being written to:
+
+* \[ga]ListBucket\[ga]
+* \[ga]DeleteObject\[ga]
+* \[ga]GetObject\[ga]
+* \[ga]PutObject\[ga]
+* \[ga]PutObjectACL\[ga]
+
+When using the \[ga]lsd\[ga] subcommand, the \[ga]ListAllMyBuckets\[ga] permission is required.
+
 Example policy:
-.IP
-.nf
-\f[C]
-{
-    \[dq]Version\[dq]: \[dq]2012\-10\-17\[dq],
-    \[dq]Statement\[dq]: [
-        {
-            \[dq]Effect\[dq]: \[dq]Allow\[dq],
-            \[dq]Principal\[dq]: {
-                \[dq]AWS\[dq]: \[dq]arn:aws:iam::USER_SID:user/USER_NAME\[dq]
-            },
-            \[dq]Action\[dq]: [
-                \[dq]s3:ListBucket\[dq],
-                \[dq]s3:DeleteObject\[dq],
-                \[dq]s3:GetObject\[dq],
-                \[dq]s3:PutObject\[dq],
-                \[dq]s3:PutObjectAcl\[dq]
-            ],
-            \[dq]Resource\[dq]: [
-              \[dq]arn:aws:s3:::BUCKET_NAME/*\[dq],
-              \[dq]arn:aws:s3:::BUCKET_NAME\[dq]
-            ]
-        },
-        {
-            \[dq]Effect\[dq]: \[dq]Allow\[dq],
-            \[dq]Action\[dq]: \[dq]s3:ListAllMyBuckets\[dq],
-            \[dq]Resource\[dq]: \[dq]arn:aws:s3:::*\[dq]
-        }   
-    ]
-}
 \f[R]
 .fi
 .PP
+{ \[dq]Version\[dq]: \[dq]2012\-10\-17\[dq], \[dq]Statement\[dq]: [ {
+\[dq]Effect\[dq]: \[dq]Allow\[dq], \[dq]Principal\[dq]: { \[dq]AWS\[dq]:
+\[dq]arn:aws:iam::USER_SID:user/USER_NAME\[dq] }, \[dq]Action\[dq]: [
+\[dq]s3:ListBucket\[dq], \[dq]s3:DeleteObject\[dq],
+\[dq]s3:GetObject\[dq], \[dq]s3:PutObject\[dq],
+\[dq]s3:PutObjectAcl\[dq] ], \[dq]Resource\[dq]: [
+\[dq]arn:aws:s3:::BUCKET_NAME/*\[dq], \[dq]arn:aws:s3:::BUCKET_NAME\[dq]
+] }, { \[dq]Effect\[dq]: \[dq]Allow\[dq], \[dq]Action\[dq]:
+\[dq]s3:ListAllMyBuckets\[dq], \[dq]Resource\[dq]:
+\[dq]arn:aws:s3:::*\[dq] }
+.PD 0
+.P
+.PD
+] }
+.IP
+.nf
+\f[C]
+
 Notes on above:
-.IP "1." 3
-This is a policy that can be used when creating bucket.
-It assumes that \f[C]USER_NAME\f[R] has been created.
-.IP "2." 3
-The Resource entry must include both resource ARNs, as one implies the
-bucket and the other implies the bucket\[cq]s objects.
-.PP
-For reference, here\[cq]s an Ansible
-script (https://gist.github.com/ebridges/ebfc9042dd7c756cd101cfa807b7ae2b)
-that will generate one or more buckets that will work with
-\f[C]rclone sync\f[R].
-.SS Key Management System (KMS)
-.PP
-If you are using server side encryption with KMS then you will find you
-can\[cq]t transfer small objects.
-As a work\-around you can use the \f[C]\-\-ignore\-checksum\f[R] flag.
-.PP
-A proper fix is being worked on in issue
-#1824 (https://github.com/rclone/rclone/issues/1824).
-.SS Glacier and Glacier Deep Archive
-.PP
-You can upload objects using the glacier storage class or transition
-them to glacier using a lifecycle
-policy (http://docs.aws.amazon.com/AmazonS3/latest/user-guide/create-lifecycle.html).
+
+1. This is a policy that can be used when creating bucket. It assumes
+   that \[ga]USER_NAME\[ga] has been created.
+2. The Resource entry must include both resource ARNs, as one implies
+   the bucket and the other implies the bucket\[aq]s objects.
+
+For reference, [here\[aq]s an Ansible script](https://gist.github.com/ebridges/ebfc9042dd7c756cd101cfa807b7ae2b)
+that will generate one or more buckets that will work with \[ga]rclone sync\[ga].
+
+### Key Management System (KMS) ###
+
+If you are using server side encryption with KMS then you will find
+you can\[aq]t transfer small objects.  As a work\-around you can use the
+\[ga]\-\-ignore\-checksum\[ga] flag.
+
+A proper fix is being worked on in [issue #1824](https://github.com/rclone/rclone/issues/1824).
+
+### Glacier and Glacier Deep Archive ###
+
+You can upload objects using the glacier storage class or transition them to glacier using a [lifecycle policy](http://docs.aws.amazon.com/AmazonS3/latest/user\-guide/create\-lifecycle.html).
 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.
-.IP
-.nf
-\f[C]
-2017/09/11 19:07:43 Failed to sync: failed to open source object: Object in GLACIER, restore first: path/to/file
-\f[R]
-.fi
-.PP
-In this case you need to
-restore (http://docs.aws.amazon.com/AmazonS3/latest/user-guide/restore-archived-objects.html)
+tries to access data from the glacier storage class you will see an error like below.
+
+    2017/09/11 19:07:43 Failed to sync: failed to open source object: Object in GLACIER, restore first: path/to/file
+
+In this case you need to [restore](http://docs.aws.amazon.com/AmazonS3/latest/user\-guide/restore\-archived\-objects.html)
 the object(s) in question before using rclone.
-.PP
+
 Note that rclone only speaks the S3 API it does not speak the Glacier
 Vault API, so rclone cannot directly access Glacier Vaults.
-.SS Standard Options
-.PP
-Here are the standard options specific to s3 (Amazon S3 Compliant
-Storage Provider (AWS, Alibaba, Ceph, Digital Ocean, Dreamhost, IBM COS,
-Minio, etc)).
-.SS \[en]s3\-provider
-.PP
+
+
+### Standard Options
+
+Here are the standard options specific to s3 (Amazon S3 Compliant Storage Provider (AWS, Alibaba, Ceph, Digital Ocean, Dreamhost, IBM COS, Minio, etc)).
+
+#### \-\-s3\-provider
+
 Choose your S3 provider.
-.IP \[bu] 2
-Config: provider
-.IP \[bu] 2
-Env Var: RCLONE_S3_PROVIDER
-.IP \[bu] 2
-Type: string
-.IP \[bu] 2
-Default: \[dq]\[dq]
-.IP \[bu] 2
-Examples:
-.RS 2
-.IP \[bu] 2
-\[lq]AWS\[rq]
-.RS 2
-.IP \[bu] 2
-Amazon Web Services (AWS) S3
-.RE
-.IP \[bu] 2
-\[lq]Alibaba\[rq]
-.RS 2
-.IP \[bu] 2
-Alibaba Cloud Object Storage System (OSS) formerly Aliyun
-.RE
-.IP \[bu] 2
-\[lq]Ceph\[rq]
-.RS 2
-.IP \[bu] 2
-Ceph Object Storage
-.RE
-.IP \[bu] 2
-\[lq]DigitalOcean\[rq]
-.RS 2
-.IP \[bu] 2
-Digital Ocean Spaces
-.RE
-.IP \[bu] 2
-\[lq]Dreamhost\[rq]
-.RS 2
-.IP \[bu] 2
-Dreamhost DreamObjects
-.RE
-.IP \[bu] 2
-\[lq]IBMCOS\[rq]
-.RS 2
-.IP \[bu] 2
-IBM COS S3
-.RE
-.IP \[bu] 2
-\[lq]Minio\[rq]
-.RS 2
-.IP \[bu] 2
-Minio Object Storage
-.RE
-.IP \[bu] 2
-\[lq]Netease\[rq]
-.RS 2
-.IP \[bu] 2
-Netease Object Storage (NOS)
-.RE
-.IP \[bu] 2
-\[lq]StackPath\[rq]
-.RS 2
-.IP \[bu] 2
-StackPath Object Storage
-.RE
-.IP \[bu] 2
-\[lq]Wasabi\[rq]
-.RS 2
-.IP \[bu] 2
-Wasabi Object Storage
-.RE
-.IP \[bu] 2
-\[lq]Other\[rq]
-.RS 2
-.IP \[bu] 2
-Any other S3 compatible provider
-.RE
-.RE
-.SS \[en]s3\-env\-auth
-.PP
-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.
-.IP \[bu] 2
-Config: env_auth
-.IP \[bu] 2
-Env Var: RCLONE_S3_ENV_AUTH
-.IP \[bu] 2
-Type: bool
-.IP \[bu] 2
-Default: false
-.IP \[bu] 2
-Examples:
-.RS 2
-.IP \[bu] 2
-\[lq]false\[rq]
-.RS 2
-.IP \[bu] 2
-Enter AWS credentials in the next step
-.RE
-.IP \[bu] 2
-\[lq]true\[rq]
-.RS 2
-.IP \[bu] 2
-Get AWS credentials from the environment (env vars or IAM)
-.RE
-.RE
-.SS \[en]s3\-access\-key\-id
-.PP
-AWS Access Key ID.
-Leave blank for anonymous access or runtime credentials.
-.IP \[bu] 2
-Config: access_key_id
-.IP \[bu] 2
-Env Var: RCLONE_S3_ACCESS_KEY_ID
-.IP \[bu] 2
-Type: string
-.IP \[bu] 2
-Default: \[dq]\[dq]
-.SS \[en]s3\-secret\-access\-key
-.PP
-AWS Secret Access Key (password) Leave blank for anonymous access or
-runtime credentials.
-.IP \[bu] 2
-Config: secret_access_key
-.IP \[bu] 2
-Env Var: RCLONE_S3_SECRET_ACCESS_KEY
-.IP \[bu] 2
-Type: string
-.IP \[bu] 2
-Default: \[dq]\[dq]
-.SS \[en]s3\-region
-.PP
-Region to connect to.
-.IP \[bu] 2
-Config: region
-.IP \[bu] 2
-Env Var: RCLONE_S3_REGION
-.IP \[bu] 2
-Type: string
-.IP \[bu] 2
-Default: \[dq]\[dq]
-.IP \[bu] 2
-Examples:
-.RS 2
-.IP \[bu] 2
-\[lq]us\-east\-1\[rq]
-.RS 2
-.IP \[bu] 2
-The default endpoint \- a good choice if you are unsure.
-.IP \[bu] 2
-US Region, Northern Virginia or Pacific Northwest.
-.IP \[bu] 2
-Leave location constraint empty.
-.RE
-.IP \[bu] 2
-\[lq]us\-east\-2\[rq]
-.RS 2
-.IP \[bu] 2
-US East (Ohio) Region
-.IP \[bu] 2
-Needs location constraint us\-east\-2.
-.RE
-.IP \[bu] 2
-\[lq]us\-west\-2\[rq]
-.RS 2
-.IP \[bu] 2
-US West (Oregon) Region
-.IP \[bu] 2
-Needs location constraint us\-west\-2.
-.RE
-.IP \[bu] 2
-\[lq]us\-west\-1\[rq]
-.RS 2
-.IP \[bu] 2
-US West (Northern California) Region
-.IP \[bu] 2
-Needs location constraint us\-west\-1.
-.RE
-.IP \[bu] 2
-\[lq]ca\-central\-1\[rq]
-.RS 2
-.IP \[bu] 2
-Canada (Central) Region
-.IP \[bu] 2
-Needs location constraint ca\-central\-1.
-.RE
-.IP \[bu] 2
-\[lq]eu\-west\-1\[rq]
-.RS 2
-.IP \[bu] 2
-EU (Ireland) Region
-.IP \[bu] 2
-Needs location constraint EU or eu\-west\-1.
-.RE
-.IP \[bu] 2
-\[lq]eu\-west\-2\[rq]
-.RS 2
-.IP \[bu] 2
-EU (London) Region
-.IP \[bu] 2
-Needs location constraint eu\-west\-2.
-.RE
-.IP \[bu] 2
-\[lq]eu\-north\-1\[rq]
-.RS 2
-.IP \[bu] 2
-EU (Stockholm) Region
-.IP \[bu] 2
-Needs location constraint eu\-north\-1.
-.RE
-.IP \[bu] 2
-\[lq]eu\-central\-1\[rq]
-.RS 2
-.IP \[bu] 2
-EU (Frankfurt) Region
-.IP \[bu] 2
-Needs location constraint eu\-central\-1.
-.RE
-.IP \[bu] 2
-\[lq]ap\-southeast\-1\[rq]
-.RS 2
-.IP \[bu] 2
-Asia Pacific (Singapore) Region
-.IP \[bu] 2
-Needs location constraint ap\-southeast\-1.
-.RE
-.IP \[bu] 2
-\[lq]ap\-southeast\-2\[rq]
-.RS 2
-.IP \[bu] 2
-Asia Pacific (Sydney) Region
-.IP \[bu] 2
-Needs location constraint ap\-southeast\-2.
-.RE
-.IP \[bu] 2
-\[lq]ap\-northeast\-1\[rq]
-.RS 2
-.IP \[bu] 2
-Asia Pacific (Tokyo) Region
-.IP \[bu] 2
-Needs location constraint ap\-northeast\-1.
-.RE
-.IP \[bu] 2
-\[lq]ap\-northeast\-2\[rq]
-.RS 2
-.IP \[bu] 2
-Asia Pacific (Seoul)
-.IP \[bu] 2
-Needs location constraint ap\-northeast\-2.
-.RE
-.IP \[bu] 2
-\[lq]ap\-south\-1\[rq]
-.RS 2
-.IP \[bu] 2
-Asia Pacific (Mumbai)
-.IP \[bu] 2
-Needs location constraint ap\-south\-1.
-.RE
-.IP \[bu] 2
-\[lq]ap\-east\-1\[rq]
-.RS 2
-.IP \[bu] 2
-Asia Patific (Hong Kong) Region
-.IP \[bu] 2
-Needs location constraint ap\-east\-1.
-.RE
-.IP \[bu] 2
-\[lq]sa\-east\-1\[rq]
-.RS 2
-.IP \[bu] 2
-South America (Sao Paulo) Region
-.IP \[bu] 2
-Needs location constraint sa\-east\-1.
-.RE
-.RE
-.SS \[en]s3\-region
-.PP
-Region to connect to.
-Leave blank if you are using an S3 clone and you don\[cq]t have a
-region.
-.IP \[bu] 2
-Config: region
-.IP \[bu] 2
-Env Var: RCLONE_S3_REGION
-.IP \[bu] 2
-Type: string
-.IP \[bu] 2
-Default: \[dq]\[dq]
-.IP \[bu] 2
-Examples:
-.RS 2
-.IP \[bu] 2
-\[dq]\[dq]
-.RS 2
-.IP \[bu] 2
-Use this if unsure.
-Will use v4 signatures and an empty region.
-.RE
-.IP \[bu] 2
-\[lq]other\-v2\-signature\[rq]
-.RS 2
-.IP \[bu] 2
-Use this only if v4 signatures don\[cq]t work, eg pre Jewel/v10 CEPH.
-.RE
-.RE
-.SS \[en]s3\-endpoint
-.PP
-Endpoint for S3 API.
-Leave blank if using AWS to use the default endpoint for the region.
-.IP \[bu] 2
-Config: endpoint
-.IP \[bu] 2
-Env Var: RCLONE_S3_ENDPOINT
-.IP \[bu] 2
-Type: string
-.IP \[bu] 2
-Default: \[dq]\[dq]
-.SS \[en]s3\-endpoint
-.PP
-Endpoint for IBM COS S3 API.
-Specify if using an IBM COS On Premise.
-.IP \[bu] 2
-Config: endpoint
-.IP \[bu] 2
-Env Var: RCLONE_S3_ENDPOINT
-.IP \[bu] 2
-Type: string
-.IP \[bu] 2
-Default: \[dq]\[dq]
-.IP \[bu] 2
-Examples:
-.RS 2
-.IP \[bu] 2
-\[lq]s3\-api.us\-geo.objectstorage.softlayer.net\[rq]
-.RS 2
-.IP \[bu] 2
-US Cross Region Endpoint
-.RE
-.IP \[bu] 2
-\[lq]s3\-api.dal.us\-geo.objectstorage.softlayer.net\[rq]
-.RS 2
-.IP \[bu] 2
-US Cross Region Dallas Endpoint
-.RE
-.IP \[bu] 2
-\[lq]s3\-api.wdc\-us\-geo.objectstorage.softlayer.net\[rq]
-.RS 2
-.IP \[bu] 2
-US Cross Region Washington DC Endpoint
-.RE
-.IP \[bu] 2
-\[lq]s3\-api.sjc\-us\-geo.objectstorage.softlayer.net\[rq]
-.RS 2
-.IP \[bu] 2
-US Cross Region San Jose Endpoint
-.RE
-.IP \[bu] 2
-\[lq]s3\-api.us\-geo.objectstorage.service.networklayer.com\[rq]
-.RS 2
-.IP \[bu] 2
-US Cross Region Private Endpoint
-.RE
-.IP \[bu] 2
-\[lq]s3\-api.dal\-us\-geo.objectstorage.service.networklayer.com\[rq]
-.RS 2
-.IP \[bu] 2
-US Cross Region Dallas Private Endpoint
-.RE
-.IP \[bu] 2
-\[lq]s3\-api.wdc\-us\-geo.objectstorage.service.networklayer.com\[rq]
-.RS 2
-.IP \[bu] 2
-US Cross Region Washington DC Private Endpoint
-.RE
-.IP \[bu] 2
-\[lq]s3\-api.sjc\-us\-geo.objectstorage.service.networklayer.com\[rq]
-.RS 2
-.IP \[bu] 2
-US Cross Region San Jose Private Endpoint
-.RE
-.IP \[bu] 2
-\[lq]s3.us\-east.objectstorage.softlayer.net\[rq]
-.RS 2
-.IP \[bu] 2
-US Region East Endpoint
-.RE
-.IP \[bu] 2
-\[lq]s3.us\-east.objectstorage.service.networklayer.com\[rq]
-.RS 2
-.IP \[bu] 2
-US Region East Private Endpoint
-.RE
-.IP \[bu] 2
-\[lq]s3.us\-south.objectstorage.softlayer.net\[rq]
-.RS 2
-.IP \[bu] 2
-US Region South Endpoint
-.RE
-.IP \[bu] 2
-\[lq]s3.us\-south.objectstorage.service.networklayer.com\[rq]
-.RS 2
-.IP \[bu] 2
-US Region South Private Endpoint
-.RE
-.IP \[bu] 2
-\[lq]s3.eu\-geo.objectstorage.softlayer.net\[rq]
-.RS 2
-.IP \[bu] 2
-EU Cross Region Endpoint
-.RE
-.IP \[bu] 2
-\[lq]s3.fra\-eu\-geo.objectstorage.softlayer.net\[rq]
-.RS 2
-.IP \[bu] 2
-EU Cross Region Frankfurt Endpoint
-.RE
-.IP \[bu] 2
-\[lq]s3.mil\-eu\-geo.objectstorage.softlayer.net\[rq]
-.RS 2
-.IP \[bu] 2
-EU Cross Region Milan Endpoint
-.RE
-.IP \[bu] 2
-\[lq]s3.ams\-eu\-geo.objectstorage.softlayer.net\[rq]
-.RS 2
-.IP \[bu] 2
-EU Cross Region Amsterdam Endpoint
-.RE
-.IP \[bu] 2
-\[lq]s3.eu\-geo.objectstorage.service.networklayer.com\[rq]
-.RS 2
-.IP \[bu] 2
-EU Cross Region Private Endpoint
-.RE
-.IP \[bu] 2
-\[lq]s3.fra\-eu\-geo.objectstorage.service.networklayer.com\[rq]
-.RS 2
-.IP \[bu] 2
-EU Cross Region Frankfurt Private Endpoint
-.RE
-.IP \[bu] 2
-\[lq]s3.mil\-eu\-geo.objectstorage.service.networklayer.com\[rq]
-.RS 2
-.IP \[bu] 2
-EU Cross Region Milan Private Endpoint
-.RE
-.IP \[bu] 2
-\[lq]s3.ams\-eu\-geo.objectstorage.service.networklayer.com\[rq]
-.RS 2
-.IP \[bu] 2
-EU Cross Region Amsterdam Private Endpoint
-.RE
-.IP \[bu] 2
-\[lq]s3.eu\-gb.objectstorage.softlayer.net\[rq]
-.RS 2
-.IP \[bu] 2
-Great Britain Endpoint
-.RE
-.IP \[bu] 2
-\[lq]s3.eu\-gb.objectstorage.service.networklayer.com\[rq]
-.RS 2
-.IP \[bu] 2
-Great Britain Private Endpoint
-.RE
-.IP \[bu] 2
-\[lq]s3.ap\-geo.objectstorage.softlayer.net\[rq]
-.RS 2
-.IP \[bu] 2
-APAC Cross Regional Endpoint
-.RE
-.IP \[bu] 2
-\[lq]s3.tok\-ap\-geo.objectstorage.softlayer.net\[rq]
-.RS 2
-.IP \[bu] 2
-APAC Cross Regional Tokyo Endpoint
-.RE
-.IP \[bu] 2
-\[lq]s3.hkg\-ap\-geo.objectstorage.softlayer.net\[rq]
-.RS 2
-.IP \[bu] 2
-APAC Cross Regional HongKong Endpoint
-.RE
-.IP \[bu] 2
-\[lq]s3.seo\-ap\-geo.objectstorage.softlayer.net\[rq]
-.RS 2
-.IP \[bu] 2
-APAC Cross Regional Seoul Endpoint
-.RE
-.IP \[bu] 2
-\[lq]s3.ap\-geo.objectstorage.service.networklayer.com\[rq]
-.RS 2
-.IP \[bu] 2
-APAC Cross Regional Private Endpoint
-.RE
-.IP \[bu] 2
-\[lq]s3.tok\-ap\-geo.objectstorage.service.networklayer.com\[rq]
-.RS 2
-.IP \[bu] 2
-APAC Cross Regional Tokyo Private Endpoint
-.RE
-.IP \[bu] 2
-\[lq]s3.hkg\-ap\-geo.objectstorage.service.networklayer.com\[rq]
-.RS 2
-.IP \[bu] 2
-APAC Cross Regional HongKong Private Endpoint
-.RE
-.IP \[bu] 2
-\[lq]s3.seo\-ap\-geo.objectstorage.service.networklayer.com\[rq]
-.RS 2
-.IP \[bu] 2
-APAC Cross Regional Seoul Private Endpoint
-.RE
-.IP \[bu] 2
-\[lq]s3.mel01.objectstorage.softlayer.net\[rq]
-.RS 2
-.IP \[bu] 2
-Melbourne Single Site Endpoint
-.RE
-.IP \[bu] 2
-\[lq]s3.mel01.objectstorage.service.networklayer.com\[rq]
-.RS 2
-.IP \[bu] 2
-Melbourne Single Site Private Endpoint
-.RE
-.IP \[bu] 2
-\[lq]s3.tor01.objectstorage.softlayer.net\[rq]
-.RS 2
-.IP \[bu] 2
-Toronto Single Site Endpoint
-.RE
-.IP \[bu] 2
-\[lq]s3.tor01.objectstorage.service.networklayer.com\[rq]
-.RS 2
-.IP \[bu] 2
-Toronto Single Site Private Endpoint
-.RE
-.RE
-.SS \[en]s3\-endpoint
-.PP
-Endpoint for OSS API.
-.IP \[bu] 2
-Config: endpoint
-.IP \[bu] 2
-Env Var: RCLONE_S3_ENDPOINT
-.IP \[bu] 2
-Type: string
-.IP \[bu] 2
-Default: \[dq]\[dq]
-.IP \[bu] 2
-Examples:
-.RS 2
-.IP \[bu] 2
-\[lq]oss\-cn\-hangzhou.aliyuncs.com\[rq]
-.RS 2
-.IP \[bu] 2
-East China 1 (Hangzhou)
-.RE
-.IP \[bu] 2
-\[lq]oss\-cn\-shanghai.aliyuncs.com\[rq]
-.RS 2
-.IP \[bu] 2
-East China 2 (Shanghai)
-.RE
-.IP \[bu] 2
-\[lq]oss\-cn\-qingdao.aliyuncs.com\[rq]
-.RS 2
-.IP \[bu] 2
-North China 1 (Qingdao)
-.RE
-.IP \[bu] 2
-\[lq]oss\-cn\-beijing.aliyuncs.com\[rq]
-.RS 2
-.IP \[bu] 2
-North China 2 (Beijing)
-.RE
-.IP \[bu] 2
-\[lq]oss\-cn\-zhangjiakou.aliyuncs.com\[rq]
-.RS 2
-.IP \[bu] 2
-North China 3 (Zhangjiakou)
-.RE
-.IP \[bu] 2
-\[lq]oss\-cn\-huhehaote.aliyuncs.com\[rq]
-.RS 2
-.IP \[bu] 2
-North China 5 (Huhehaote)
-.RE
-.IP \[bu] 2
-\[lq]oss\-cn\-shenzhen.aliyuncs.com\[rq]
-.RS 2
-.IP \[bu] 2
-South China 1 (Shenzhen)
-.RE
-.IP \[bu] 2
-\[lq]oss\-cn\-hongkong.aliyuncs.com\[rq]
-.RS 2
-.IP \[bu] 2
-Hong Kong (Hong Kong)
-.RE
-.IP \[bu] 2
-\[lq]oss\-us\-west\-1.aliyuncs.com\[rq]
-.RS 2
-.IP \[bu] 2
-US West 1 (Silicon Valley)
-.RE
-.IP \[bu] 2
-\[lq]oss\-us\-east\-1.aliyuncs.com\[rq]
-.RS 2
-.IP \[bu] 2
-US East 1 (Virginia)
-.RE
-.IP \[bu] 2
-\[lq]oss\-ap\-southeast\-1.aliyuncs.com\[rq]
-.RS 2
-.IP \[bu] 2
-Southeast Asia Southeast 1 (Singapore)
-.RE
-.IP \[bu] 2
-\[lq]oss\-ap\-southeast\-2.aliyuncs.com\[rq]
-.RS 2
-.IP \[bu] 2
-Asia Pacific Southeast 2 (Sydney)
-.RE
-.IP \[bu] 2
-\[lq]oss\-ap\-southeast\-3.aliyuncs.com\[rq]
-.RS 2
-.IP \[bu] 2
-Southeast Asia Southeast 3 (Kuala Lumpur)
-.RE
-.IP \[bu] 2
-\[lq]oss\-ap\-southeast\-5.aliyuncs.com\[rq]
-.RS 2
-.IP \[bu] 2
-Asia Pacific Southeast 5 (Jakarta)
-.RE
-.IP \[bu] 2
-\[lq]oss\-ap\-northeast\-1.aliyuncs.com\[rq]
-.RS 2
-.IP \[bu] 2
-Asia Pacific Northeast 1 (Japan)
-.RE
-.IP \[bu] 2
-\[lq]oss\-ap\-south\-1.aliyuncs.com\[rq]
-.RS 2
-.IP \[bu] 2
-Asia Pacific South 1 (Mumbai)
-.RE
-.IP \[bu] 2
-\[lq]oss\-eu\-central\-1.aliyuncs.com\[rq]
-.RS 2
-.IP \[bu] 2
-Central Europe 1 (Frankfurt)
-.RE
-.IP \[bu] 2
-\[lq]oss\-eu\-west\-1.aliyuncs.com\[rq]
-.RS 2
-.IP \[bu] 2
-West Europe (London)
-.RE
-.IP \[bu] 2
-\[lq]oss\-me\-east\-1.aliyuncs.com\[rq]
-.RS 2
-.IP \[bu] 2
-Middle East 1 (Dubai)
-.RE
-.RE
-.SS \[en]s3\-endpoint
-.PP
-Endpoint for StackPath Object Storage.
-.IP \[bu] 2
-Config: endpoint
-.IP \[bu] 2
-Env Var: RCLONE_S3_ENDPOINT
-.IP \[bu] 2
-Type: string
-.IP \[bu] 2
-Default: \[dq]\[dq]
-.IP \[bu] 2
-Examples:
-.RS 2
-.IP \[bu] 2
-\[lq]s3.us\-east\-2.stackpathstorage.com\[rq]
-.RS 2
-.IP \[bu] 2
-US East Endpoint
-.RE
-.IP \[bu] 2
-\[lq]s3.us\-west\-1.stackpathstorage.com\[rq]
-.RS 2
-.IP \[bu] 2
-US West Endpoint
-.RE
-.IP \[bu] 2
-\[lq]s3.eu\-central\-1.stackpathstorage.com\[rq]
-.RS 2
-.IP \[bu] 2
-EU Endpoint
-.RE
-.RE
-.SS \[en]s3\-endpoint
-.PP
-Endpoint for S3 API.
-Required when using an S3 clone.
-.IP \[bu] 2
-Config: endpoint
-.IP \[bu] 2
-Env Var: RCLONE_S3_ENDPOINT
-.IP \[bu] 2
-Type: string
-.IP \[bu] 2
-Default: \[dq]\[dq]
-.IP \[bu] 2
-Examples:
-.RS 2
-.IP \[bu] 2
-\[lq]objects\-us\-east\-1.dream.io\[rq]
-.RS 2
-.IP \[bu] 2
-Dream Objects endpoint
-.RE
-.IP \[bu] 2
-\[lq]nyc3.digitaloceanspaces.com\[rq]
-.RS 2
-.IP \[bu] 2
-Digital Ocean Spaces New York 3
-.RE
-.IP \[bu] 2
-\[lq]ams3.digitaloceanspaces.com\[rq]
-.RS 2
-.IP \[bu] 2
-Digital Ocean Spaces Amsterdam 3
-.RE
-.IP \[bu] 2
-\[lq]sgp1.digitaloceanspaces.com\[rq]
-.RS 2
-.IP \[bu] 2
-Digital Ocean Spaces Singapore 1
-.RE
-.IP \[bu] 2
-\[lq]s3.wasabisys.com\[rq]
-.RS 2
-.IP \[bu] 2
-Wasabi US East endpoint
-.RE
-.IP \[bu] 2
-\[lq]s3.us\-west\-1.wasabisys.com\[rq]
-.RS 2
-.IP \[bu] 2
-Wasabi US West endpoint
-.RE
-.IP \[bu] 2
-\[lq]s3.eu\-central\-1.wasabisys.com\[rq]
-.RS 2
-.IP \[bu] 2
-Wasabi EU Central endpoint
-.RE
-.RE
-.SS \[en]s3\-location\-constraint
-.PP
-Location constraint \- must be set to match the Region.
-Used when creating buckets only.
-.IP \[bu] 2
-Config: location_constraint
-.IP \[bu] 2
-Env Var: RCLONE_S3_LOCATION_CONSTRAINT
-.IP \[bu] 2
-Type: string
-.IP \[bu] 2
-Default: \[dq]\[dq]
-.IP \[bu] 2
-Examples:
-.RS 2
-.IP \[bu] 2
-\[dq]\[dq]
-.RS 2
-.IP \[bu] 2
-Empty for US Region, Northern Virginia or Pacific Northwest.
-.RE
-.IP \[bu] 2
-\[lq]us\-east\-2\[rq]
-.RS 2
-.IP \[bu] 2
-US East (Ohio) Region.
-.RE
-.IP \[bu] 2
-\[lq]us\-west\-2\[rq]
-.RS 2
-.IP \[bu] 2
-US West (Oregon) Region.
-.RE
-.IP \[bu] 2
-\[lq]us\-west\-1\[rq]
-.RS 2
-.IP \[bu] 2
-US West (Northern California) Region.
-.RE
-.IP \[bu] 2
-\[lq]ca\-central\-1\[rq]
-.RS 2
-.IP \[bu] 2
-Canada (Central) Region.
-.RE
-.IP \[bu] 2
-\[lq]eu\-west\-1\[rq]
-.RS 2
-.IP \[bu] 2
-EU (Ireland) Region.
-.RE
-.IP \[bu] 2
-\[lq]eu\-west\-2\[rq]
-.RS 2
-.IP \[bu] 2
-EU (London) Region.
-.RE
-.IP \[bu] 2
-\[lq]eu\-north\-1\[rq]
-.RS 2
-.IP \[bu] 2
-EU (Stockholm) Region.
-.RE
-.IP \[bu] 2
-\[lq]EU\[rq]
-.RS 2
-.IP \[bu] 2
-EU Region.
-.RE
-.IP \[bu] 2
-\[lq]ap\-southeast\-1\[rq]
-.RS 2
-.IP \[bu] 2
-Asia Pacific (Singapore) Region.
-.RE
-.IP \[bu] 2
-\[lq]ap\-southeast\-2\[rq]
-.RS 2
-.IP \[bu] 2
-Asia Pacific (Sydney) Region.
-.RE
-.IP \[bu] 2
-\[lq]ap\-northeast\-1\[rq]
-.RS 2
-.IP \[bu] 2
-Asia Pacific (Tokyo) Region.
-.RE
-.IP \[bu] 2
-\[lq]ap\-northeast\-2\[rq]
-.RS 2
-.IP \[bu] 2
-Asia Pacific (Seoul)
-.RE
-.IP \[bu] 2
-\[lq]ap\-south\-1\[rq]
-.RS 2
-.IP \[bu] 2
-Asia Pacific (Mumbai)
-.RE
-.IP \[bu] 2
-\[lq]ap\-east\-1\[rq]
-.RS 2
-.IP \[bu] 2
-Asia Pacific (Hong Kong)
-.RE
-.IP \[bu] 2
-\[lq]sa\-east\-1\[rq]
-.RS 2
-.IP \[bu] 2
-South America (Sao Paulo) Region.
-.RE
-.RE
-.SS \[en]s3\-location\-constraint
-.PP
-Location constraint \- must match endpoint when using IBM Cloud Public.
-For on\-prem COS, do not make a selection from this list, hit enter
-.IP \[bu] 2
-Config: location_constraint
-.IP \[bu] 2
-Env Var: RCLONE_S3_LOCATION_CONSTRAINT
-.IP \[bu] 2
-Type: string
-.IP \[bu] 2
-Default: \[dq]\[dq]
-.IP \[bu] 2
-Examples:
-.RS 2
-.IP \[bu] 2
-\[lq]us\-standard\[rq]
-.RS 2
-.IP \[bu] 2
-US Cross Region Standard
-.RE
-.IP \[bu] 2
-\[lq]us\-vault\[rq]
-.RS 2
-.IP \[bu] 2
-US Cross Region Vault
-.RE
-.IP \[bu] 2
-\[lq]us\-cold\[rq]
-.RS 2
-.IP \[bu] 2
-US Cross Region Cold
-.RE
-.IP \[bu] 2
-\[lq]us\-flex\[rq]
-.RS 2
-.IP \[bu] 2
-US Cross Region Flex
-.RE
-.IP \[bu] 2
-\[lq]us\-east\-standard\[rq]
-.RS 2
-.IP \[bu] 2
-US East Region Standard
-.RE
-.IP \[bu] 2
-\[lq]us\-east\-vault\[rq]
-.RS 2
-.IP \[bu] 2
-US East Region Vault
-.RE
-.IP \[bu] 2
-\[lq]us\-east\-cold\[rq]
-.RS 2
-.IP \[bu] 2
-US East Region Cold
-.RE
-.IP \[bu] 2
-\[lq]us\-east\-flex\[rq]
-.RS 2
-.IP \[bu] 2
-US East Region Flex
-.RE
-.IP \[bu] 2
-\[lq]us\-south\-standard\[rq]
-.RS 2
-.IP \[bu] 2
-US South Region Standard
-.RE
-.IP \[bu] 2
-\[lq]us\-south\-vault\[rq]
-.RS 2
-.IP \[bu] 2
-US South Region Vault
-.RE
-.IP \[bu] 2
-\[lq]us\-south\-cold\[rq]
-.RS 2
-.IP \[bu] 2
-US South Region Cold
-.RE
-.IP \[bu] 2
-\[lq]us\-south\-flex\[rq]
-.RS 2
-.IP \[bu] 2
-US South Region Flex
-.RE
-.IP \[bu] 2
-\[lq]eu\-standard\[rq]
-.RS 2
-.IP \[bu] 2
-EU Cross Region Standard
-.RE
-.IP \[bu] 2
-\[lq]eu\-vault\[rq]
-.RS 2
-.IP \[bu] 2
-EU Cross Region Vault
-.RE
-.IP \[bu] 2
-\[lq]eu\-cold\[rq]
-.RS 2
-.IP \[bu] 2
-EU Cross Region Cold
-.RE
-.IP \[bu] 2
-\[lq]eu\-flex\[rq]
-.RS 2
-.IP \[bu] 2
-EU Cross Region Flex
-.RE
-.IP \[bu] 2
-\[lq]eu\-gb\-standard\[rq]
-.RS 2
-.IP \[bu] 2
-Great Britain Standard
-.RE
-.IP \[bu] 2
-\[lq]eu\-gb\-vault\[rq]
-.RS 2
-.IP \[bu] 2
-Great Britain Vault
-.RE
-.IP \[bu] 2
-\[lq]eu\-gb\-cold\[rq]
-.RS 2
-.IP \[bu] 2
-Great Britain Cold
-.RE
-.IP \[bu] 2
-\[lq]eu\-gb\-flex\[rq]
-.RS 2
-.IP \[bu] 2
-Great Britain Flex
-.RE
-.IP \[bu] 2
-\[lq]ap\-standard\[rq]
-.RS 2
-.IP \[bu] 2
-APAC Standard
-.RE
-.IP \[bu] 2
-\[lq]ap\-vault\[rq]
-.RS 2
-.IP \[bu] 2
-APAC Vault
-.RE
-.IP \[bu] 2
-\[lq]ap\-cold\[rq]
-.RS 2
-.IP \[bu] 2
-APAC Cold
-.RE
-.IP \[bu] 2
-\[lq]ap\-flex\[rq]
-.RS 2
-.IP \[bu] 2
-APAC Flex
-.RE
-.IP \[bu] 2
-\[lq]mel01\-standard\[rq]
-.RS 2
-.IP \[bu] 2
-Melbourne Standard
-.RE
-.IP \[bu] 2
-\[lq]mel01\-vault\[rq]
-.RS 2
-.IP \[bu] 2
-Melbourne Vault
-.RE
-.IP \[bu] 2
-\[lq]mel01\-cold\[rq]
-.RS 2
-.IP \[bu] 2
-Melbourne Cold
-.RE
-.IP \[bu] 2
-\[lq]mel01\-flex\[rq]
-.RS 2
-.IP \[bu] 2
-Melbourne Flex
-.RE
-.IP \[bu] 2
-\[lq]tor01\-standard\[rq]
-.RS 2
-.IP \[bu] 2
-Toronto Standard
-.RE
-.IP \[bu] 2
-\[lq]tor01\-vault\[rq]
-.RS 2
-.IP \[bu] 2
-Toronto Vault
-.RE
-.IP \[bu] 2
-\[lq]tor01\-cold\[rq]
-.RS 2
-.IP \[bu] 2
-Toronto Cold
-.RE
-.IP \[bu] 2
-\[lq]tor01\-flex\[rq]
-.RS 2
-.IP \[bu] 2
-Toronto Flex
-.RE
-.RE
-.SS \[en]s3\-location\-constraint
-.PP
-Location constraint \- must be set to match the Region.
-Leave blank if not sure.
-Used when creating buckets only.
-.IP \[bu] 2
-Config: location_constraint
-.IP \[bu] 2
-Env Var: RCLONE_S3_LOCATION_CONSTRAINT
-.IP \[bu] 2
-Type: string
-.IP \[bu] 2
-Default: \[dq]\[dq]
-.SS \[en]s3\-acl
-.PP
-Canned ACL used when creating buckets and storing or copying objects.
-.PP
-This ACL is used for creating objects and if bucket_acl isn\[cq]t set,
-for creating buckets too.
-.PP
-For more info visit
-https://docs.aws.amazon.com/AmazonS3/latest/dev/acl\-overview.html#canned\-acl
-.PP
-Note that this ACL is applied when server side copying objects as S3
-doesn\[cq]t copy the ACL from the source but rather writes a fresh one.
-.IP \[bu] 2
-Config: acl
-.IP \[bu] 2
-Env Var: RCLONE_S3_ACL
-.IP \[bu] 2
-Type: string
-.IP \[bu] 2
-Default: \[dq]\[dq]
-.IP \[bu] 2
-Examples:
-.RS 2
-.IP \[bu] 2
-\[lq]private\[rq]
-.RS 2
-.IP \[bu] 2
-Owner gets FULL_CONTROL.
-No one else has access rights (default).
-.RE
-.IP \[bu] 2
-\[lq]public\-read\[rq]
-.RS 2
-.IP \[bu] 2
-Owner gets FULL_CONTROL.
-The AllUsers group gets READ access.
-.RE
-.IP \[bu] 2
-\[lq]public\-read\-write\[rq]
-.RS 2
-.IP \[bu] 2
-Owner gets FULL_CONTROL.
-The AllUsers group gets READ and WRITE access.
-.IP \[bu] 2
-Granting this on a bucket is generally not recommended.
-.RE
-.IP \[bu] 2
-\[lq]authenticated\-read\[rq]
-.RS 2
-.IP \[bu] 2
-Owner gets FULL_CONTROL.
-The AuthenticatedUsers group gets READ access.
-.RE
-.IP \[bu] 2
-\[lq]bucket\-owner\-read\[rq]
-.RS 2
-.IP \[bu] 2
-Object owner gets FULL_CONTROL.
-Bucket owner gets READ access.
-.IP \[bu] 2
-If you specify this canned ACL when creating a bucket, Amazon S3 ignores
-it.
-.RE
-.IP \[bu] 2
-\[lq]bucket\-owner\-full\-control\[rq]
-.RS 2
-.IP \[bu] 2
-Both the object owner and the bucket owner get FULL_CONTROL over the
-object.
-.IP \[bu] 2
-If you specify this canned ACL when creating a bucket, Amazon S3 ignores
-it.
-.RE
-.IP \[bu] 2
-\[lq]private\[rq]
-.RS 2
-.IP \[bu] 2
-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
-.RE
-.IP \[bu] 2
-\[lq]public\-read\[rq]
-.RS 2
-.IP \[bu] 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
-.RE
-.IP \[bu] 2
-\[lq]public\-read\-write\[rq]
-.RS 2
-.IP \[bu] 2
-Owner gets FULL_CONTROL.
-The AllUsers group gets READ and WRITE access.
-This acl is available on IBM Cloud (Infra), On\-Premise IBM COS
-.RE
-.IP \[bu] 2
-\[lq]authenticated\-read\[rq]
-.RS 2
-.IP \[bu] 2
-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
-.RE
-.RE
-.SS \[en]s3\-server\-side\-encryption
-.PP
-The server\-side encryption algorithm used when storing this object in
-S3.
-.IP \[bu] 2
-Config: server_side_encryption
-.IP \[bu] 2
-Env Var: RCLONE_S3_SERVER_SIDE_ENCRYPTION
-.IP \[bu] 2
-Type: string
-.IP \[bu] 2
-Default: \[dq]\[dq]
-.IP \[bu] 2
-Examples:
-.RS 2
-.IP \[bu] 2
-\[dq]\[dq]
-.RS 2
-.IP \[bu] 2
-None
-.RE
-.IP \[bu] 2
-\[lq]AES256\[rq]
-.RS 2
-.IP \[bu] 2
-AES256
-.RE
-.IP \[bu] 2
-\[lq]aws:kms\[rq]
-.RS 2
-.IP \[bu] 2
-aws:kms
-.RE
-.RE
-.SS \[en]s3\-sse\-kms\-key\-id
-.PP
-If using KMS ID you must provide the ARN of Key.
-.IP \[bu] 2
-Config: sse_kms_key_id
-.IP \[bu] 2
-Env Var: RCLONE_S3_SSE_KMS_KEY_ID
-.IP \[bu] 2
-Type: string
-.IP \[bu] 2
-Default: \[dq]\[dq]
-.IP \[bu] 2
-Examples:
-.RS 2
-.IP \[bu] 2
-\[dq]\[dq]
-.RS 2
-.IP \[bu] 2
-None
-.RE
-.IP \[bu] 2
-\[dq]arn:aws:kms:us\-east\-1:*\[dq]
-.RS 2
-.IP \[bu] 2
-arn:aws:kms:*
-.RE
-.RE
-.SS \[en]s3\-storage\-class
-.PP
-The storage class to use when storing new objects in S3.
-.IP \[bu] 2
-Config: storage_class
-.IP \[bu] 2
-Env Var: RCLONE_S3_STORAGE_CLASS
-.IP \[bu] 2
-Type: string
-.IP \[bu] 2
-Default: \[dq]\[dq]
-.IP \[bu] 2
-Examples:
-.RS 2
-.IP \[bu] 2
-\[dq]\[dq]
-.RS 2
-.IP \[bu] 2
-Default
-.RE
-.IP \[bu] 2
-\[lq]STANDARD\[rq]
-.RS 2
-.IP \[bu] 2
-Standard storage class
-.RE
-.IP \[bu] 2
-\[lq]REDUCED_REDUNDANCY\[rq]
-.RS 2
-.IP \[bu] 2
-Reduced redundancy storage class
-.RE
-.IP \[bu] 2
-\[lq]STANDARD_IA\[rq]
-.RS 2
-.IP \[bu] 2
-Standard Infrequent Access storage class
-.RE
-.IP \[bu] 2
-\[lq]ONEZONE_IA\[rq]
-.RS 2
-.IP \[bu] 2
-One Zone Infrequent Access storage class
-.RE
-.IP \[bu] 2
-\[lq]GLACIER\[rq]
-.RS 2
-.IP \[bu] 2
-Glacier storage class
-.RE
-.IP \[bu] 2
-\[lq]DEEP_ARCHIVE\[rq]
-.RS 2
-.IP \[bu] 2
-Glacier Deep Archive storage class
-.RE
-.IP \[bu] 2
-\[lq]INTELLIGENT_TIERING\[rq]
-.RS 2
-.IP \[bu] 2
-Intelligent\-Tiering storage class
-.RE
-.RE
-.SS \[en]s3\-storage\-class
-.PP
-The storage class to use when storing new objects in OSS.
-.IP \[bu] 2
-Config: storage_class
-.IP \[bu] 2
-Env Var: RCLONE_S3_STORAGE_CLASS
-.IP \[bu] 2
-Type: string
-.IP \[bu] 2
-Default: \[dq]\[dq]
-.IP \[bu] 2
-Examples:
-.RS 2
-.IP \[bu] 2
-\[dq]\[dq]
-.RS 2
-.IP \[bu] 2
-Default
-.RE
-.IP \[bu] 2
-\[lq]STANDARD\[rq]
-.RS 2
-.IP \[bu] 2
-Standard storage class
-.RE
-.IP \[bu] 2
-\[lq]GLACIER\[rq]
-.RS 2
-.IP \[bu] 2
-Archive storage mode.
-.RE
-.IP \[bu] 2
-\[lq]STANDARD_IA\[rq]
-.RS 2
-.IP \[bu] 2
-Infrequent access storage mode.
-.RE
-.RE
-.SS Advanced Options
-.PP
-Here are the advanced options specific to s3 (Amazon S3 Compliant
-Storage Provider (AWS, Alibaba, Ceph, Digital Ocean, Dreamhost, IBM COS,
-Minio, etc)).
-.SS \[en]s3\-bucket\-acl
-.PP
-Canned ACL used when creating buckets.
-.PP
-For more info visit
-https://docs.aws.amazon.com/AmazonS3/latest/dev/acl\-overview.html#canned\-acl
-.PP
-Note that this ACL is applied when only when creating buckets.
-If it isn\[cq]t set then \[lq]acl\[rq] is used instead.
-.IP \[bu] 2
-Config: bucket_acl
-.IP \[bu] 2
-Env Var: RCLONE_S3_BUCKET_ACL
-.IP \[bu] 2
-Type: string
-.IP \[bu] 2
-Default: \[dq]\[dq]
-.IP \[bu] 2
-Examples:
-.RS 2
-.IP \[bu] 2
-\[lq]private\[rq]
-.RS 2
-.IP \[bu] 2
-Owner gets FULL_CONTROL.
-No one else has access rights (default).
-.RE
-.IP \[bu] 2
-\[lq]public\-read\[rq]
-.RS 2
-.IP \[bu] 2
-Owner gets FULL_CONTROL.
-The AllUsers group gets READ access.
-.RE
-.IP \[bu] 2
-\[lq]public\-read\-write\[rq]
-.RS 2
-.IP \[bu] 2
-Owner gets FULL_CONTROL.
-The AllUsers group gets READ and WRITE access.
-.IP \[bu] 2
-Granting this on a bucket is generally not recommended.
-.RE
-.IP \[bu] 2
-\[lq]authenticated\-read\[rq]
-.RS 2
-.IP \[bu] 2
-Owner gets FULL_CONTROL.
-The AuthenticatedUsers group gets READ access.
-.RE
-.RE
-.SS \[en]s3\-sse\-customer\-algorithm
-.PP
-If using SSE\-C, the server\-side encryption algorithm used when storing
-this object in S3.
-.IP \[bu] 2
-Config: sse_customer_algorithm
-.IP \[bu] 2
-Env Var: RCLONE_S3_SSE_CUSTOMER_ALGORITHM
-.IP \[bu] 2
-Type: string
-.IP \[bu] 2
-Default: \[dq]\[dq]
-.IP \[bu] 2
-Examples:
-.RS 2
-.IP \[bu] 2
-\[dq]\[dq]
-.RS 2
-.IP \[bu] 2
-None
-.RE
-.IP \[bu] 2
-\[lq]AES256\[rq]
-.RS 2
-.IP \[bu] 2
-AES256
-.RE
-.RE
-.SS \[en]s3\-sse\-customer\-key
-.PP
-If using SSE\-C you must provide the secret encryption key used to
-encrypt/decrypt your data.
-.IP \[bu] 2
-Config: sse_customer_key
-.IP \[bu] 2
-Env Var: RCLONE_S3_SSE_CUSTOMER_KEY
-.IP \[bu] 2
-Type: string
-.IP \[bu] 2
-Default: \[dq]\[dq]
-.IP \[bu] 2
-Examples:
-.RS 2
-.IP \[bu] 2
-\[dq]\[dq]
-.RS 2
-.IP \[bu] 2
-None
-.RE
-.RE
-.SS \[en]s3\-sse\-customer\-key\-md5
-.PP
-If using SSE\-C you must provide the secret encryption key MD5 checksum.
-.IP \[bu] 2
-Config: sse_customer_key_md5
-.IP \[bu] 2
-Env Var: RCLONE_S3_SSE_CUSTOMER_KEY_MD5
-.IP \[bu] 2
-Type: string
-.IP \[bu] 2
-Default: \[dq]\[dq]
-.IP \[bu] 2
-Examples:
-.RS 2
-.IP \[bu] 2
-\[dq]\[dq]
-.RS 2
-.IP \[bu] 2
-None
-.RE
-.RE
-.SS \[en]s3\-upload\-cutoff
-.PP
-Cutoff for switching to chunked upload
-.PP
-Any files larger than this will be uploaded in chunks of chunk_size.
-The minimum is 0 and the maximum is 5GB.
-.IP \[bu] 2
-Config: upload_cutoff
-.IP \[bu] 2
-Env Var: RCLONE_S3_UPLOAD_CUTOFF
-.IP \[bu] 2
-Type: SizeSuffix
-.IP \[bu] 2
-Default: 200M
-.SS \[en]s3\-chunk\-size
-.PP
-Chunk size to use for uploading.
-.PP
-When uploading files larger than upload_cutoff or files with unknown
-size (eg from \[lq]rclone rcat\[rq] or uploaded with \[lq]rclone
-mount\[rq] or google photos or google docs) they will be uploaded as
-multipart uploads using this chunk size.
-.PP
-Note that \[lq]\[en]s3\-upload\-concurrency\[rq] chunks of this size are
-buffered in memory per transfer.
-.PP
-If you are transferring large files over high speed links and you have
-enough memory, then increasing this will speed up the transfers.
-.PP
-Rclone will automatically increase the chunk size when uploading a large
-file of known size to stay below the 10,000 chunks limit.
-.PP
-Files of unknown size are uploaded with the configured chunk_size.
-Since the default chunk size is 5MB and there can be at most 10,000
-chunks, this means that by default the maximum size of file you can
-stream upload is 48GB.
-If you wish to stream upload larger files then you will need to increase
-chunk_size.
-.IP \[bu] 2
-Config: chunk_size
-.IP \[bu] 2
-Env Var: RCLONE_S3_CHUNK_SIZE
-.IP \[bu] 2
-Type: SizeSuffix
-.IP \[bu] 2
-Default: 5M
-.SS \[en]s3\-copy\-cutoff
-.PP
-Cutoff for switching to multipart copy
-.PP
-Any files larger than this that need to be server side copied will be
-copied in chunks of this size.
-.PP
-The minimum is 0 and the maximum is 5GB.
-.IP \[bu] 2
-Config: copy_cutoff
-.IP \[bu] 2
-Env Var: RCLONE_S3_COPY_CUTOFF
-.IP \[bu] 2
-Type: SizeSuffix
-.IP \[bu] 2
-Default: 5G
-.SS \[en]s3\-disable\-checksum
-.PP
-Don\[cq]t store MD5 checksum with object metadata
-.PP
-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.
-.IP \[bu] 2
-Config: disable_checksum
-.IP \[bu] 2
-Env Var: RCLONE_S3_DISABLE_CHECKSUM
-.IP \[bu] 2
-Type: bool
-.IP \[bu] 2
-Default: false
-.SS \[en]s3\-session\-token
-.PP
-An AWS session token
-.IP \[bu] 2
-Config: session_token
-.IP \[bu] 2
-Env Var: RCLONE_S3_SESSION_TOKEN
-.IP \[bu] 2
-Type: string
-.IP \[bu] 2
-Default: \[dq]\[dq]
-.SS \[en]s3\-upload\-concurrency
-.PP
-Concurrency for multipart uploads.
-.PP
-This is the number of chunks of the same file that are uploaded
-concurrently.
-.PP
-If you are uploading small numbers of large file over high speed link
-and these uploads do not fully utilize your bandwidth, then increasing
-this may help to speed up the transfers.
-.IP \[bu] 2
-Config: upload_concurrency
-.IP \[bu] 2
-Env Var: RCLONE_S3_UPLOAD_CONCURRENCY
-.IP \[bu] 2
-Type: int
-.IP \[bu] 2
-Default: 4
-.SS \[en]s3\-force\-path\-style
-.PP
-If true use path style access if false use virtual hosted style.
-.PP
-If this is true (the default) then rclone will use path style access, if
-false then rclone will use virtual path style.
-See the AWS S3
-docs (https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingBucket.html#access-bucket-intro)
-for more info.
-.PP
-Some providers (eg AWS, Aliyun OSS or Netease COS) require this set to
-false \- rclone will do this automatically based on the provider
-setting.
-.IP \[bu] 2
-Config: force_path_style
-.IP \[bu] 2
-Env Var: RCLONE_S3_FORCE_PATH_STYLE
-.IP \[bu] 2
-Type: bool
-.IP \[bu] 2
-Default: true
-.SS \[en]s3\-v2\-auth
-.PP
-If true use v2 authentication.
-.PP
-If this is false (the default) then rclone will use v4 authentication.
-If it is set then rclone will use v2 authentication.
-.PP
-Use this only if v4 signatures don\[cq]t work, eg pre Jewel/v10 CEPH.
-.IP \[bu] 2
-Config: v2_auth
-.IP \[bu] 2
-Env Var: RCLONE_S3_V2_AUTH
-.IP \[bu] 2
-Type: bool
-.IP \[bu] 2
-Default: false
-.SS \[en]s3\-use\-accelerate\-endpoint
-.PP
-If true use the AWS S3 accelerated endpoint.
-.PP
-See: AWS S3 Transfer
-acceleration (https://docs.aws.amazon.com/AmazonS3/latest/dev/transfer-acceleration-examples.html)
-.IP \[bu] 2
-Config: use_accelerate_endpoint
-.IP \[bu] 2
-Env Var: RCLONE_S3_USE_ACCELERATE_ENDPOINT
-.IP \[bu] 2
-Type: bool
-.IP \[bu] 2
-Default: false
-.SS \[en]s3\-leave\-parts\-on\-error
-.PP
-If true avoid calling abort upload on a failure, leaving all
-successfully uploaded parts on S3 for manual recovery.
-.PP
-It should be set to true for resuming uploads across different sessions.
-.PP
-WARNING: Storing parts of an incomplete multipart upload counts towards
-space usage on S3 and will add additional costs if not cleaned up.
-.IP \[bu] 2
-Config: leave_parts_on_error
-.IP \[bu] 2
-Env Var: RCLONE_S3_LEAVE_PARTS_ON_ERROR
-.IP \[bu] 2
-Type: bool
-.IP \[bu] 2
-Default: false
-.SS \[en]s3\-list\-chunk
-.PP
-Size of listing chunk (response list for each ListObject S3 request).
-.PP
-This option is also known as \[lq]MaxKeys\[rq], \[lq]max\-items\[rq], or
-\[lq]page\-size\[rq] 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 AWS
-S3 (https://docs.aws.amazon.com/cli/latest/reference/s3/ls.html).
-In Ceph, this can be increased with the \[lq]rgw list buckets max
-chunk\[rq] option.
-.IP \[bu] 2
-Config: list_chunk
-.IP \[bu] 2
-Env Var: RCLONE_S3_LIST_CHUNK
-.IP \[bu] 2
-Type: int
-.IP \[bu] 2
-Default: 1000
-.SS \[en]s3\-encoding
-.PP
-This sets the encoding for the backend.
-.PP
-See: the encoding section in the
-overview (https://rclone.org/overview/#encoding) for more info.
-.IP \[bu] 2
-Config: encoding
-.IP \[bu] 2
-Env Var: RCLONE_S3_ENCODING
-.IP \[bu] 2
-Type: MultiEncoder
-.IP \[bu] 2
-Default: Slash,InvalidUtf8,Dot
-.SS \[en]s3\-memory\-pool\-flush\-time
-.PP
-How often internal memory buffer pools will be flushed.
-Uploads which requires additional buffers (f.e multipart) will use
-memory pool for allocations.
-This option controls how often unused buffers will be removed from the
-pool.
-.IP \[bu] 2
-Config: memory_pool_flush_time
-.IP \[bu] 2
-Env Var: RCLONE_S3_MEMORY_POOL_FLUSH_TIME
-.IP \[bu] 2
-Type: Duration
-.IP \[bu] 2
-Default: 1m0s
-.SS \[en]s3\-memory\-pool\-use\-mmap
-.PP
-Whether to use mmap buffers in internal memory pool.
-.IP \[bu] 2
-Config: memory_pool_use_mmap
-.IP \[bu] 2
-Env Var: RCLONE_S3_MEMORY_POOL_USE_MMAP
-.IP \[bu] 2
-Type: bool
-.IP \[bu] 2
-Default: false
-.SS Anonymous access to public buckets
-.PP
-If you want to use rclone to access a public bucket, configure with a
-blank \f[C]access_key_id\f[R] and \f[C]secret_access_key\f[R].
-Your config should end up looking like this:
-.IP
-.nf
-\f[C]
-[anons3]
-type = s3
-provider = AWS
-env_auth = false
-access_key_id = 
-secret_access_key = 
-region = us\-east\-1
-endpoint = 
-location_constraint = 
-acl = private
-server_side_encryption = 
-storage_class = 
-\f[R]
-.fi
-.PP
-Then use it as normal with the name of the public bucket, eg
-.IP
-.nf
-\f[C]
-rclone lsd anons3:1000genomes
-\f[R]
-.fi
-.PP
-You will be able to list and copy data but not upload it.
-.SS Ceph
-.PP
-Ceph (https://ceph.com/) is an open source unified, distributed storage
-system designed for excellent performance, reliability and scalability.
-It has an S3 compatible object storage interface.
-.PP
-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:
-.IP
-.nf
-\f[C]
-[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 =
-\f[R]
-.fi
-.PP
-If you are using an older version of CEPH, eg 10.2.x Jewel, then you may
-need to supply the parameter \f[C]\-\-s3\-upload\-cutoff 0\f[R] or put
-this in the config file as \f[C]upload_cutoff 0\f[R] to work around a
-bug which causes uploading of small files to fail.
-.PP
-Note also that Ceph sometimes puts \f[C]/\f[R] 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 \f[C]/\f[R] escaped as \f[C]\[rs]/\f[R].
-Make sure you only write \f[C]/\f[R] in the secret access key.
-.PP
-Eg the dump from Ceph looks something like this (irrelevant keys
-removed).
-.IP
-.nf
-\f[C]
-{
-    \[dq]user_id\[dq]: \[dq]xxx\[dq],
-    \[dq]display_name\[dq]: \[dq]xxxx\[dq],
-    \[dq]keys\[dq]: [
-        {
-            \[dq]user\[dq]: \[dq]xxx\[dq],
-            \[dq]access_key\[dq]: \[dq]xxxxxx\[dq],
-            \[dq]secret_key\[dq]: \[dq]xxxxxx\[rs]/xxxx\[dq]
-        }
-    ],
-}
-\f[R]
-.fi
-.PP
-Because this is a json dump, it is encoding the \f[C]/\f[R] as
-\f[C]\[rs]/\f[R], so if you use the secret key as \f[C]xxxxxx/xxxx\f[R]
-it will work fine.
-.SS Dreamhost
-.PP
-Dreamhost DreamObjects (https://www.dreamhost.com/cloud/storage/) is an
-object storage system based on CEPH.
-.PP
-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:
-.IP
-.nf
-\f[C]
-[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 =
-\f[R]
-.fi
-.SS DigitalOcean Spaces
-.PP
-Spaces (https://www.digitalocean.com/products/object-storage/) is an
-S3\-interoperable (https://developers.digitalocean.com/documentation/spaces/)
-object storage service from cloud provider DigitalOcean.
-.PP
-To connect to DigitalOcean Spaces you will need an access key and secret
-key.
-These can be retrieved on the \[lq]Applications &
-API (https://cloud.digitalocean.com/settings/api/tokens)\[rq] page of
-the DigitalOcean control panel.
-They will be needed when prompted by \f[C]rclone config\f[R] for your
-\f[C]access_key_id\f[R] and \f[C]secret_access_key\f[R].
-.PP
-When prompted for a \f[C]region\f[R] or \f[C]location_constraint\f[R],
-press enter to use the default value.
-The region must be included in the \f[C]endpoint\f[R] setting
-(e.g.\ \f[C]nyc3.digitaloceanspaces.com\f[R]).
-The default values can be used for other settings.
-.PP
-Going through the whole process of creating a new remote by running
-\f[C]rclone config\f[R], each prompt should be answered as shown below:
-.IP
-.nf
-\f[C]
-Storage> s3
-env_auth> 1
-access_key_id> YOUR_ACCESS_KEY
-secret_access_key> YOUR_SECRET_KEY
-region>
-endpoint> nyc3.digitaloceanspaces.com
-location_constraint>
-acl>
-storage_class>
-\f[R]
-.fi
-.PP
-The resulting configuration file should look like:
-.IP
-.nf
-\f[C]
-[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 =
-\f[R]
-.fi
-.PP
-Once configured, you can create a new Space and begin copying files.
-For example:
-.IP
-.nf
-\f[C]
-rclone mkdir spaces:my\-new\-space
-rclone copy /path/to/files spaces:my\-new\-space
-\f[R]
-.fi
-.SS IBM COS (S3)
-.PP
-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\[cq]s Cloud Object Storage System (formerly Cleversafe).
-For more information visit: (http://www.ibm.com/cloud/object\-storage)
-.PP
-To configure access to IBM COS S3, follow the steps below:
-.IP "1." 3
-Run rclone config and select n for a new remote.
-.IP
-.nf
-\f[C]
-    2018/02/14 14:13:11 NOTICE: Config file \[dq]C:\[rs]\[rs]Users\[rs]\[rs]a\[rs]\[rs].config\[rs]\[rs]rclone\[rs]\[rs]rclone.conf\[dq] not found \- using defaults
-    No remotes found \- make a new one
-    n) New remote
-    s) Set configuration password
-    q) Quit config
-    n/s/q> n
-\f[R]
-.fi
-.IP "2." 3
-Enter the name for the configuration
-.IP
-.nf
-\f[C]
-    name> <YOUR NAME>
-\f[R]
-.fi
-.IP "3." 3
-Select \[lq]s3\[rq] storage.
-.IP
-.nf
-\f[C]
-Choose a number from below, or type in your own value
-    1 / Alias for an existing remote
-    \[rs] \[dq]alias\[dq]
-    2 / Amazon Drive
-    \[rs] \[dq]amazon cloud drive\[dq]
-    3 / Amazon S3 Complaint Storage Providers (Dreamhost, Ceph, Minio, IBM COS)
-    \[rs] \[dq]s3\[dq]
-    4 / Backblaze B2
-    \[rs] \[dq]b2\[dq]
-[snip]
-    23 / http Connection
-    \[rs] \[dq]http\[dq]
-Storage> 3
-\f[R]
-.fi
-.IP "4." 3
-Select IBM COS as the S3 Storage Provider.
-.IP
-.nf
-\f[C]
-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
-       \[rs] \[dq]AWS\[dq]
-     2 / Choose this option to configure Storage to Ceph Systems
-     \[rs] \[dq]Ceph\[dq]
-     3 /  Choose this option to configure Storage to Dreamhost
-     \[rs] \[dq]Dreamhost\[dq]
-   4 / Choose this option to the configure Storage to IBM COS S3
-     \[rs] \[dq]IBMCOS\[dq]
-     5 / Choose this option to the configure Storage to Minio
-     \[rs] \[dq]Minio\[dq]
-     Provider>4
-\f[R]
-.fi
-.IP "5." 3
-Enter the Access Key and Secret.
-.IP
-.nf
-\f[C]
-    AWS Access Key ID \- leave blank for anonymous access or runtime credentials.
-    access_key_id> <>
-    AWS Secret Access Key (password) \- leave blank for anonymous access or runtime credentials.
-    secret_access_key> <>
-\f[R]
-.fi
-.IP "6." 3
-Specify the endpoint for IBM COS.
-For Public IBM COS, choose from the option below.
-For On Premise IBM COS, enter an enpoint address.
-.IP
-.nf
-\f[C]
-    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
-       \[rs] \[dq]s3\-api.us\-geo.objectstorage.softlayer.net\[dq]
-     2 / US Cross Region Dallas Endpoint
-       \[rs] \[dq]s3\-api.dal.us\-geo.objectstorage.softlayer.net\[dq]
-     3 / US Cross Region Washington DC Endpoint
-       \[rs] \[dq]s3\-api.wdc\-us\-geo.objectstorage.softlayer.net\[dq]
-     4 / US Cross Region San Jose Endpoint
-       \[rs] \[dq]s3\-api.sjc\-us\-geo.objectstorage.softlayer.net\[dq]
-     5 / US Cross Region Private Endpoint
-       \[rs] \[dq]s3\-api.us\-geo.objectstorage.service.networklayer.com\[dq]
-     6 / US Cross Region Dallas Private Endpoint
-       \[rs] \[dq]s3\-api.dal\-us\-geo.objectstorage.service.networklayer.com\[dq]
-     7 / US Cross Region Washington DC Private Endpoint
-       \[rs] \[dq]s3\-api.wdc\-us\-geo.objectstorage.service.networklayer.com\[dq]
-     8 / US Cross Region San Jose Private Endpoint
-       \[rs] \[dq]s3\-api.sjc\-us\-geo.objectstorage.service.networklayer.com\[dq]
-     9 / US Region East Endpoint
-       \[rs] \[dq]s3.us\-east.objectstorage.softlayer.net\[dq]
-    10 / US Region East Private Endpoint
-       \[rs] \[dq]s3.us\-east.objectstorage.service.networklayer.com\[dq]
-    11 / US Region South Endpoint
-[snip]
-    34 / Toronto Single Site Private Endpoint
-       \[rs] \[dq]s3.tor01.objectstorage.service.networklayer.com\[dq]
-    endpoint>1
-\f[R]
-.fi
-.IP "7." 3
-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
-.IP
-.nf
-\f[C]
-     1 / US Cross Region Standard
-       \[rs] \[dq]us\-standard\[dq]
-     2 / US Cross Region Vault
-       \[rs] \[dq]us\-vault\[dq]
-     3 / US Cross Region Cold
-       \[rs] \[dq]us\-cold\[dq]
-     4 / US Cross Region Flex
-       \[rs] \[dq]us\-flex\[dq]
-     5 / US East Region Standard
-       \[rs] \[dq]us\-east\-standard\[dq]
-     6 / US East Region Vault
-       \[rs] \[dq]us\-east\-vault\[dq]
-     7 / US East Region Cold
-       \[rs] \[dq]us\-east\-cold\[dq]
-     8 / US East Region Flex
-       \[rs] \[dq]us\-east\-flex\[dq]
-     9 / US South Region Standard
-       \[rs] \[dq]us\-south\-standard\[dq]
-    10 / US South Region Vault
-       \[rs] \[dq]us\-south\-vault\[dq]
-[snip]
-    32 / Toronto Flex
-       \[rs] \[dq]tor01\-flex\[dq]
-location_constraint>1
-\f[R]
-.fi
-.IP "9." 3
-Specify a canned ACL.
-IBM Cloud (Strorage) supports \[lq]public\-read\[rq] and
-\[lq]private\[rq].
-IBM Cloud(Infra) supports all the canned ACLs.
-On\-Premise COS supports all the canned ACLs.
-.IP
-.nf
-\f[C]
-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
-      \[rs] \[dq]private\[dq]
-      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
-      \[rs] \[dq]public\-read\[dq]
-      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
-      \[rs] \[dq]public\-read\-write\[dq]
-      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
-      \[rs] \[dq]authenticated\-read\[dq]
-acl> 1
-\f[R]
-.fi
-.IP "12." 4
-Review the displayed configuration and accept to save the
-\[lq]remote\[rq] then quit.
-The config file should look like this
-.IP
-.nf
-\f[C]
-    [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
-\f[R]
-.fi
-.IP "13." 4
-Execute rclone commands
-.IP
-.nf
-\f[C]
-    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
-\f[R]
-.fi
-.SS Minio
-.PP
-Minio (https://minio.io/) is an object storage server built for cloud
-application developers and devops.
-.PP
-It is very easy to install and provides an S3 compatible server which
-can be used by rclone.
-.PP
-To use it, install Minio following the instructions
-here (https://docs.minio.io/docs/minio-quickstart-guide).
-.PP
-When it configures itself Minio will print something like this
-.IP
-.nf
-\f[C]
-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
+\- Config:      provider
+\- Env Var:     RCLONE_S3_PROVIDER
+\- Type:        string
+\- Default:     \[dq]\[dq]
+\- Examples:
+    \- \[dq]AWS\[dq]
+        \- Amazon Web Services (AWS) S3
+    \- \[dq]Alibaba\[dq]
+        \- Alibaba Cloud Object Storage System (OSS) formerly Aliyun
+    \- \[dq]Ceph\[dq]
+        \- Ceph Object Storage
+    \- \[dq]DigitalOcean\[dq]
+        \- Digital Ocean Spaces
+    \- \[dq]Dreamhost\[dq]
+        \- Dreamhost DreamObjects
+    \- \[dq]IBMCOS\[dq]
+        \- IBM COS S3
+    \- \[dq]Minio\[dq]
+        \- Minio Object Storage
+    \- \[dq]Netease\[dq]
+        \- Netease Object Storage (NOS)
+    \- \[dq]Scaleway\[dq]
+        \- Scaleway Object Storage
+    \- \[dq]StackPath\[dq]
+        \- StackPath Object Storage
+    \- \[dq]Wasabi\[dq]
+        \- Wasabi Object Storage
+    \- \[dq]Other\[dq]
+        \- Any other S3 compatible provider
 
-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
+#### \-\-s3\-env\-auth
 
-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
-\f[R]
-.fi
-.PP
-These details need to go into \f[C]rclone config\f[R] like this.
-Note that it is important to put the region in as stated above.
-.IP
-.nf
-\f[C]
-env_auth> 1
-access_key_id> USWUXHGYZQYFYFFIT3RE
-secret_access_key> MOJRH0mkL1IPauahWITSVvyDrQbEEIwljvmxdq03
-region> us\-east\-1
-endpoint> http://192.168.1.106:9000
-location_constraint>
-server_side_encryption>
-\f[R]
-.fi
-.PP
-Which makes the config file look like this
-.IP
-.nf
-\f[C]
-[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 =
-\f[R]
-.fi
-.PP
-So once set up, for example to copy files into a bucket
-.IP
-.nf
-\f[C]
-rclone copy /path/to/files minio:bucket
-\f[R]
-.fi
-.SS Scaleway
-.PP
-Scaleway (https://www.scaleway.com/object-storage/) 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.
-.PP
-Scaleway provides an S3 interface which can be configured for use with
-rclone like this:
-.IP
-.nf
-\f[C]
-[scaleway]
-type = s3
-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 =
-acl = private
-force_path_style = false
-server_side_encryption =
-storage_class =
-\f[R]
-.fi
-.SS Wasabi
-.PP
-Wasabi (https://wasabi.com) 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.
-.PP
-Wasabi provides an S3 interface which can be configured for use with
-rclone like this.
-.IP
-.nf
-\f[C]
-No remotes found \- make a new one
-n) New remote
-s) Set configuration password
-n/s> n
-name> wasabi
-Type of storage to configure.
-Choose a number from below, or type in your own value
-[snip]
-XX / Amazon S3 (also Dreamhost, Ceph, Minio)
-   \[rs] \[dq]s3\[dq]
-[snip]
-Storage> 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
-   \[rs] \[dq]false\[dq]
- 2 / Get AWS credentials from the environment (env vars or IAM)
-   \[rs] \[dq]true\[dq]
-env_auth> 1
-AWS Access Key ID \- leave blank for anonymous access or runtime credentials.
-access_key_id> YOURACCESSKEY
-AWS Secret Access Key (password) \- leave blank for anonymous access or runtime credentials.
-secret_access_key> 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.
-   \[rs] \[dq]us\-east\-1\[dq]
-[snip]
-region> 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> 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.
-   \[rs] \[dq]\[dq]
-[snip]
-location_constraint>
-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).
-   \[rs] \[dq]private\[dq]
-[snip]
-acl>
-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
-   \[rs] \[dq]\[dq]
- 2 / AES256
-   \[rs] \[dq]AES256\[dq]
-server_side_encryption>
-The storage class to use when storing objects in S3.
-Choose a number from below, or type in your own value
- 1 / Default
-   \[rs] \[dq]\[dq]
- 2 / Standard storage class
-   \[rs] \[dq]STANDARD\[dq]
- 3 / Reduced redundancy storage class
-   \[rs] \[dq]REDUCED_REDUNDANCY\[dq]
- 4 / Standard Infrequent Access storage class
-   \[rs] \[dq]STANDARD_IA\[dq]
-storage_class>
-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> y
-\f[R]
-.fi
-.PP
-This will leave the config file looking like this.
-.IP
-.nf
-\f[C]
-[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 =
-\f[R]
-.fi
-.SS Alibaba OSS
-.PP
-Here is an example of making an Alibaba Cloud (Aliyun)
-OSS (https://www.alibabacloud.com/product/oss/) configuration.
-First run:
-.IP
-.nf
-\f[C]
-rclone config
-\f[R]
-.fi
-.PP
-This will guide you through an interactive setup process.
-.IP
-.nf
-\f[C]
-No remotes found \- make a new one
-n) New remote
-s) Set configuration password
-q) Quit config
-n/s/q> n
-name> oss
-Type of storage to configure.
-Enter a string value. Press Enter for the default (\[dq]\[dq]).
-Choose a number from below, or type in your own value
-[snip]
- 4 / Amazon S3 Compliant Storage Provider (AWS, Alibaba, Ceph, Digital Ocean, Dreamhost, IBM COS, Minio, etc)
-   \[rs] \[dq]s3\[dq]
-[snip]
-Storage> s3
-Choose your S3 provider.
-Enter a string value. Press Enter for the default (\[dq]\[dq]).
-Choose a number from below, or type in your own value
- 1 / Amazon Web Services (AWS) S3
-   \[rs] \[dq]AWS\[dq]
- 2 / Alibaba Cloud Object Storage System (OSS) formerly Aliyun
-   \[rs] \[dq]Alibaba\[dq]
- 3 / Ceph Object Storage
-   \[rs] \[dq]Ceph\[dq]
-[snip]
-provider> 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 (\[dq]false\[dq]).
-Choose a number from below, or type in your own value
- 1 / Enter AWS credentials in the next step
-   \[rs] \[dq]false\[dq]
- 2 / Get AWS credentials from the environment (env vars or IAM)
-   \[rs] \[dq]true\[dq]
-env_auth> 1
+
+\- Config:      env_auth
+\- Env Var:     RCLONE_S3_ENV_AUTH
+\- Type:        bool
+\- Default:     false
+\- Examples:
+    \- \[dq]false\[dq]
+        \- Enter AWS credentials in the next step
+    \- \[dq]true\[dq]
+        \- Get AWS credentials from the environment (env vars or IAM)
+
+#### \-\-s3\-access\-key\-id
+
 AWS Access Key ID.
 Leave blank for anonymous access or runtime credentials.
-Enter a string value. Press Enter for the default (\[dq]\[dq]).
-access_key_id> accesskeyid
+
+\- Config:      access_key_id
+\- Env Var:     RCLONE_S3_ACCESS_KEY_ID
+\- Type:        string
+\- Default:     \[dq]\[dq]
+
+#### \-\-s3\-secret\-access\-key
+
 AWS Secret Access Key (password)
 Leave blank for anonymous access or runtime credentials.
-Enter a string value. Press Enter for the default (\[dq]\[dq]).
-secret_access_key> secretaccesskey
+
+\- Config:      secret_access_key
+\- Env Var:     RCLONE_S3_SECRET_ACCESS_KEY
+\- Type:        string
+\- Default:     \[dq]\[dq]
+
+#### \-\-s3\-region
+
+Region to connect to.
+
+\- Config:      region
+\- Env Var:     RCLONE_S3_REGION
+\- Type:        string
+\- Default:     \[dq]\[dq]
+\- Examples:
+    \- \[dq]us\-east\-1\[dq]
+        \- The default endpoint \- a good choice if you are unsure.
+        \- US Region, Northern Virginia or Pacific Northwest.
+        \- Leave location constraint empty.
+    \- \[dq]us\-east\-2\[dq]
+        \- US East (Ohio) Region
+        \- Needs location constraint us\-east\-2.
+    \- \[dq]us\-west\-2\[dq]
+        \- US West (Oregon) Region
+        \- Needs location constraint us\-west\-2.
+    \- \[dq]us\-west\-1\[dq]
+        \- US West (Northern California) Region
+        \- Needs location constraint us\-west\-1.
+    \- \[dq]ca\-central\-1\[dq]
+        \- Canada (Central) Region
+        \- Needs location constraint ca\-central\-1.
+    \- \[dq]eu\-west\-1\[dq]
+        \- EU (Ireland) Region
+        \- Needs location constraint EU or eu\-west\-1.
+    \- \[dq]eu\-west\-2\[dq]
+        \- EU (London) Region
+        \- Needs location constraint eu\-west\-2.
+    \- \[dq]eu\-north\-1\[dq]
+        \- EU (Stockholm) Region
+        \- Needs location constraint eu\-north\-1.
+    \- \[dq]eu\-central\-1\[dq]
+        \- EU (Frankfurt) Region
+        \- Needs location constraint eu\-central\-1.
+    \- \[dq]ap\-southeast\-1\[dq]
+        \- Asia Pacific (Singapore) Region
+        \- Needs location constraint ap\-southeast\-1.
+    \- \[dq]ap\-southeast\-2\[dq]
+        \- Asia Pacific (Sydney) Region
+        \- Needs location constraint ap\-southeast\-2.
+    \- \[dq]ap\-northeast\-1\[dq]
+        \- Asia Pacific (Tokyo) Region
+        \- Needs location constraint ap\-northeast\-1.
+    \- \[dq]ap\-northeast\-2\[dq]
+        \- Asia Pacific (Seoul)
+        \- Needs location constraint ap\-northeast\-2.
+    \- \[dq]ap\-south\-1\[dq]
+        \- Asia Pacific (Mumbai)
+        \- Needs location constraint ap\-south\-1.
+    \- \[dq]ap\-east\-1\[dq]
+        \- Asia Patific (Hong Kong) Region
+        \- Needs location constraint ap\-east\-1.
+    \- \[dq]sa\-east\-1\[dq]
+        \- South America (Sao Paulo) Region
+        \- Needs location constraint sa\-east\-1.
+
+#### \-\-s3\-region
+
+Region to connect to.
+
+\- Config:      region
+\- Env Var:     RCLONE_S3_REGION
+\- Type:        string
+\- Default:     \[dq]\[dq]
+\- Examples:
+    \- \[dq]nl\-ams\[dq]
+        \- Amsterdam, The Netherlands
+    \- \[dq]fr\-par\[dq]
+        \- Paris, France
+
+#### \-\-s3\-region
+
+Region to connect to.
+Leave blank if you are using an S3 clone and you don\[aq]t have a region.
+
+\- Config:      region
+\- Env Var:     RCLONE_S3_REGION
+\- Type:        string
+\- Default:     \[dq]\[dq]
+\- Examples:
+    \- \[dq]\[dq]
+        \- Use this if unsure. Will use v4 signatures and an empty region.
+    \- \[dq]other\-v2\-signature\[dq]
+        \- Use this only if v4 signatures don\[aq]t work, eg pre Jewel/v10 CEPH.
+
+#### \-\-s3\-endpoint
+
+Endpoint for S3 API.
+Leave blank if using AWS to use the default endpoint for the region.
+
+\- Config:      endpoint
+\- Env Var:     RCLONE_S3_ENDPOINT
+\- Type:        string
+\- Default:     \[dq]\[dq]
+
+#### \-\-s3\-endpoint
+
+Endpoint for IBM COS S3 API.
+Specify if using an IBM COS On Premise.
+
+\- Config:      endpoint
+\- Env Var:     RCLONE_S3_ENDPOINT
+\- Type:        string
+\- Default:     \[dq]\[dq]
+\- Examples:
+    \- \[dq]s3.us.cloud\-object\-storage.appdomain.cloud\[dq]
+        \- US Cross Region Endpoint
+    \- \[dq]s3.dal.us.cloud\-object\-storage.appdomain.cloud\[dq]
+        \- US Cross Region Dallas Endpoint
+    \- \[dq]s3.wdc.us.cloud\-object\-storage.appdomain.cloud\[dq]
+        \- US Cross Region Washington DC Endpoint
+    \- \[dq]s3.sjc.us.cloud\-object\-storage.appdomain.cloud\[dq]
+        \- US Cross Region San Jose Endpoint
+    \- \[dq]s3.private.us.cloud\-object\-storage.appdomain.cloud\[dq]
+        \- US Cross Region Private Endpoint
+    \- \[dq]s3.private.dal.us.cloud\-object\-storage.appdomain.cloud\[dq]
+        \- US Cross Region Dallas Private Endpoint
+    \- \[dq]s3.private.wdc.us.cloud\-object\-storage.appdomain.cloud\[dq]
+        \- US Cross Region Washington DC Private Endpoint
+    \- \[dq]s3.private.sjc.us.cloud\-object\-storage.appdomain.cloud\[dq]
+        \- US Cross Region San Jose Private Endpoint
+    \- \[dq]s3.us\-east.cloud\-object\-storage.appdomain.cloud\[dq]
+        \- US Region East Endpoint
+    \- \[dq]s3.private.us\-east.cloud\-object\-storage.appdomain.cloud\[dq]
+        \- US Region East Private Endpoint
+    \- \[dq]s3.us\-south.cloud\-object\-storage.appdomain.cloud\[dq]
+        \- US Region South Endpoint
+    \- \[dq]s3.private.us\-south.cloud\-object\-storage.appdomain.cloud\[dq]
+        \- US Region South Private Endpoint
+    \- \[dq]s3.eu.cloud\-object\-storage.appdomain.cloud\[dq]
+        \- EU Cross Region Endpoint
+    \- \[dq]s3.fra.eu.cloud\-object\-storage.appdomain.cloud\[dq]
+        \- EU Cross Region Frankfurt Endpoint
+    \- \[dq]s3.mil.eu.cloud\-object\-storage.appdomain.cloud\[dq]
+        \- EU Cross Region Milan Endpoint
+    \- \[dq]s3.ams.eu.cloud\-object\-storage.appdomain.cloud\[dq]
+        \- EU Cross Region Amsterdam Endpoint
+    \- \[dq]s3.private.eu.cloud\-object\-storage.appdomain.cloud\[dq]
+        \- EU Cross Region Private Endpoint
+    \- \[dq]s3.private.fra.eu.cloud\-object\-storage.appdomain.cloud\[dq]
+        \- EU Cross Region Frankfurt Private Endpoint
+    \- \[dq]s3.private.mil.eu.cloud\-object\-storage.appdomain.cloud\[dq]
+        \- EU Cross Region Milan Private Endpoint
+    \- \[dq]s3.private.ams.eu.cloud\-object\-storage.appdomain.cloud\[dq]
+        \- EU Cross Region Amsterdam Private Endpoint
+    \- \[dq]s3.eu\-gb.cloud\-object\-storage.appdomain.cloud\[dq]
+        \- Great Britain Endpoint
+    \- \[dq]s3.private.eu\-gb.cloud\-object\-storage.appdomain.cloud\[dq]
+        \- Great Britain Private Endpoint
+    \- \[dq]s3.eu\-de.cloud\-object\-storage.appdomain.cloud\[dq]
+        \- EU Region DE Endpoint
+    \- \[dq]s3.private.eu\-de.cloud\-object\-storage.appdomain.cloud\[dq]
+        \- EU Region DE Private Endpoint
+    \- \[dq]s3.ap.cloud\-object\-storage.appdomain.cloud\[dq]
+        \- APAC Cross Regional Endpoint
+    \- \[dq]s3.tok.ap.cloud\-object\-storage.appdomain.cloud\[dq]
+        \- APAC Cross Regional Tokyo Endpoint
+    \- \[dq]s3.hkg.ap.cloud\-object\-storage.appdomain.cloud\[dq]
+        \- APAC Cross Regional HongKong Endpoint
+    \- \[dq]s3.seo.ap.cloud\-object\-storage.appdomain.cloud\[dq]
+        \- APAC Cross Regional Seoul Endpoint
+    \- \[dq]s3.private.ap.cloud\-object\-storage.appdomain.cloud\[dq]
+        \- APAC Cross Regional Private Endpoint
+    \- \[dq]s3.private.tok.ap.cloud\-object\-storage.appdomain.cloud\[dq]
+        \- APAC Cross Regional Tokyo Private Endpoint
+    \- \[dq]s3.private.hkg.ap.cloud\-object\-storage.appdomain.cloud\[dq]
+        \- APAC Cross Regional HongKong Private Endpoint
+    \- \[dq]s3.private.seo.ap.cloud\-object\-storage.appdomain.cloud\[dq]
+        \- APAC Cross Regional Seoul Private Endpoint
+    \- \[dq]s3.jp\-tok.cloud\-object\-storage.appdomain.cloud\[dq]
+        \- APAC Region Japan Endpoint
+    \- \[dq]s3.private.jp\-tok.cloud\-object\-storage.appdomain.cloud\[dq]
+        \- APAC Region Japan Private Endpoint
+    \- \[dq]s3.au\-syd.cloud\-object\-storage.appdomain.cloud\[dq]
+        \- APAC Region Australia Endpoint
+    \- \[dq]s3.private.au\-syd.cloud\-object\-storage.appdomain.cloud\[dq]
+        \- APAC Region Australia Private Endpoint
+    \- \[dq]s3.ams03.cloud\-object\-storage.appdomain.cloud\[dq]
+        \- Amsterdam Single Site Endpoint
+    \- \[dq]s3.private.ams03.cloud\-object\-storage.appdomain.cloud\[dq]
+        \- Amsterdam Single Site Private Endpoint
+    \- \[dq]s3.che01.cloud\-object\-storage.appdomain.cloud\[dq]
+        \- Chennai Single Site Endpoint
+    \- \[dq]s3.private.che01.cloud\-object\-storage.appdomain.cloud\[dq]
+        \- Chennai Single Site Private Endpoint
+    \- \[dq]s3.mel01.cloud\-object\-storage.appdomain.cloud\[dq]
+        \- Melbourne Single Site Endpoint
+    \- \[dq]s3.private.mel01.cloud\-object\-storage.appdomain.cloud\[dq]
+        \- Melbourne Single Site Private Endpoint
+    \- \[dq]s3.osl01.cloud\-object\-storage.appdomain.cloud\[dq]
+        \- Oslo Single Site Endpoint
+    \- \[dq]s3.private.osl01.cloud\-object\-storage.appdomain.cloud\[dq]
+        \- Oslo Single Site Private Endpoint
+    \- \[dq]s3.tor01.cloud\-object\-storage.appdomain.cloud\[dq]
+        \- Toronto Single Site Endpoint
+    \- \[dq]s3.private.tor01.cloud\-object\-storage.appdomain.cloud\[dq]
+        \- Toronto Single Site Private Endpoint
+    \- \[dq]s3.seo01.cloud\-object\-storage.appdomain.cloud\[dq]
+        \- Seoul Single Site Endpoint
+    \- \[dq]s3.private.seo01.cloud\-object\-storage.appdomain.cloud\[dq]
+        \- Seoul Single Site Private Endpoint
+    \- \[dq]s3.mon01.cloud\-object\-storage.appdomain.cloud\[dq]
+        \- Montreal Single Site Endpoint
+    \- \[dq]s3.private.mon01.cloud\-object\-storage.appdomain.cloud\[dq]
+        \- Montreal Single Site Private Endpoint
+    \- \[dq]s3.mex01.cloud\-object\-storage.appdomain.cloud\[dq]
+        \- Mexico Single Site Endpoint
+    \- \[dq]s3.private.mex01.cloud\-object\-storage.appdomain.cloud\[dq]
+        \- Mexico Single Site Private Endpoint
+    \- \[dq]s3.sjc04.cloud\-object\-storage.appdomain.cloud\[dq]
+        \- San Jose Single Site Endpoint
+    \- \[dq]s3.private.sjc04.cloud\-object\-storage.appdomain.cloud\[dq]
+        \- San Jose Single Site Private Endpoint
+    \- \[dq]s3.mil01.cloud\-object\-storage.appdomain.cloud\[dq]
+        \- Milan Single Site Endpoint
+    \- \[dq]s3.private.mil01.cloud\-object\-storage.appdomain.cloud\[dq]
+        \- Milan Single Site Private Endpoint
+    \- \[dq]s3.hkg02.cloud\-object\-storage.appdomain.cloud\[dq]
+        \- Hong Kong Single Site Endpoint
+    \- \[dq]s3.private.hkg02.cloud\-object\-storage.appdomain.cloud\[dq]
+        \- Hong Kong Single Site Private Endpoint
+    \- \[dq]s3.par01.cloud\-object\-storage.appdomain.cloud\[dq]
+        \- Paris Single Site Endpoint
+    \- \[dq]s3.private.par01.cloud\-object\-storage.appdomain.cloud\[dq]
+        \- Paris Single Site Private Endpoint
+    \- \[dq]s3.sng01.cloud\-object\-storage.appdomain.cloud\[dq]
+        \- Singapore Single Site Endpoint
+    \- \[dq]s3.private.sng01.cloud\-object\-storage.appdomain.cloud\[dq]
+        \- Singapore Single Site Private Endpoint
+
+#### \-\-s3\-endpoint
+
 Endpoint for OSS API.
-Enter a string value. Press Enter for the default (\[dq]\[dq]).
-Choose a number from below, or type in your own value
- 1 / East China 1 (Hangzhou)
-   \[rs] \[dq]oss\-cn\-hangzhou.aliyuncs.com\[dq]
- 2 / East China 2 (Shanghai)
-   \[rs] \[dq]oss\-cn\-shanghai.aliyuncs.com\[dq]
- 3 / North China 1 (Qingdao)
-   \[rs] \[dq]oss\-cn\-qingdao.aliyuncs.com\[dq]
-[snip]
-endpoint> 1
+
+\- Config:      endpoint
+\- Env Var:     RCLONE_S3_ENDPOINT
+\- Type:        string
+\- Default:     \[dq]\[dq]
+\- Examples:
+    \- \[dq]oss\-cn\-hangzhou.aliyuncs.com\[dq]
+        \- East China 1 (Hangzhou)
+    \- \[dq]oss\-cn\-shanghai.aliyuncs.com\[dq]
+        \- East China 2 (Shanghai)
+    \- \[dq]oss\-cn\-qingdao.aliyuncs.com\[dq]
+        \- North China 1 (Qingdao)
+    \- \[dq]oss\-cn\-beijing.aliyuncs.com\[dq]
+        \- North China 2 (Beijing)
+    \- \[dq]oss\-cn\-zhangjiakou.aliyuncs.com\[dq]
+        \- North China 3 (Zhangjiakou)
+    \- \[dq]oss\-cn\-huhehaote.aliyuncs.com\[dq]
+        \- North China 5 (Huhehaote)
+    \- \[dq]oss\-cn\-shenzhen.aliyuncs.com\[dq]
+        \- South China 1 (Shenzhen)
+    \- \[dq]oss\-cn\-hongkong.aliyuncs.com\[dq]
+        \- Hong Kong (Hong Kong)
+    \- \[dq]oss\-us\-west\-1.aliyuncs.com\[dq]
+        \- US West 1 (Silicon Valley)
+    \- \[dq]oss\-us\-east\-1.aliyuncs.com\[dq]
+        \- US East 1 (Virginia)
+    \- \[dq]oss\-ap\-southeast\-1.aliyuncs.com\[dq]
+        \- Southeast Asia Southeast 1 (Singapore)
+    \- \[dq]oss\-ap\-southeast\-2.aliyuncs.com\[dq]
+        \- Asia Pacific Southeast 2 (Sydney)
+    \- \[dq]oss\-ap\-southeast\-3.aliyuncs.com\[dq]
+        \- Southeast Asia Southeast 3 (Kuala Lumpur)
+    \- \[dq]oss\-ap\-southeast\-5.aliyuncs.com\[dq]
+        \- Asia Pacific Southeast 5 (Jakarta)
+    \- \[dq]oss\-ap\-northeast\-1.aliyuncs.com\[dq]
+        \- Asia Pacific Northeast 1 (Japan)
+    \- \[dq]oss\-ap\-south\-1.aliyuncs.com\[dq]
+        \- Asia Pacific South 1 (Mumbai)
+    \- \[dq]oss\-eu\-central\-1.aliyuncs.com\[dq]
+        \- Central Europe 1 (Frankfurt)
+    \- \[dq]oss\-eu\-west\-1.aliyuncs.com\[dq]
+        \- West Europe (London)
+    \- \[dq]oss\-me\-east\-1.aliyuncs.com\[dq]
+        \- Middle East 1 (Dubai)
+
+#### \-\-s3\-endpoint
+
+Endpoint for Scaleway Object Storage.
+
+\- Config:      endpoint
+\- Env Var:     RCLONE_S3_ENDPOINT
+\- Type:        string
+\- Default:     \[dq]\[dq]
+\- Examples:
+    \- \[dq]s3.nl\-ams.scw.cloud\[dq]
+        \- Amsterdam Endpoint
+    \- \[dq]s3.fr\-par.scw.cloud\[dq]
+        \- Paris Endpoint
+
+#### \-\-s3\-endpoint
+
+Endpoint for StackPath Object Storage.
+
+\- Config:      endpoint
+\- Env Var:     RCLONE_S3_ENDPOINT
+\- Type:        string
+\- Default:     \[dq]\[dq]
+\- Examples:
+    \- \[dq]s3.us\-east\-2.stackpathstorage.com\[dq]
+        \- US East Endpoint
+    \- \[dq]s3.us\-west\-1.stackpathstorage.com\[dq]
+        \- US West Endpoint
+    \- \[dq]s3.eu\-central\-1.stackpathstorage.com\[dq]
+        \- EU Endpoint
+
+#### \-\-s3\-endpoint
+
+Endpoint for S3 API.
+Required when using an S3 clone.
+
+\- Config:      endpoint
+\- Env Var:     RCLONE_S3_ENDPOINT
+\- Type:        string
+\- Default:     \[dq]\[dq]
+\- Examples:
+    \- \[dq]objects\-us\-east\-1.dream.io\[dq]
+        \- Dream Objects endpoint
+    \- \[dq]nyc3.digitaloceanspaces.com\[dq]
+        \- Digital Ocean Spaces New York 3
+    \- \[dq]ams3.digitaloceanspaces.com\[dq]
+        \- Digital Ocean Spaces Amsterdam 3
+    \- \[dq]sgp1.digitaloceanspaces.com\[dq]
+        \- Digital Ocean Spaces Singapore 1
+    \- \[dq]s3.wasabisys.com\[dq]
+        \- Wasabi US East endpoint
+    \- \[dq]s3.us\-west\-1.wasabisys.com\[dq]
+        \- Wasabi US West endpoint
+    \- \[dq]s3.eu\-central\-1.wasabisys.com\[dq]
+        \- Wasabi EU Central endpoint
+
+#### \-\-s3\-location\-constraint
+
+Location constraint \- must be set to match the Region.
+Used when creating buckets only.
+
+\- Config:      location_constraint
+\- Env Var:     RCLONE_S3_LOCATION_CONSTRAINT
+\- Type:        string
+\- Default:     \[dq]\[dq]
+\- Examples:
+    \- \[dq]\[dq]
+        \- Empty for US Region, Northern Virginia or Pacific Northwest.
+    \- \[dq]us\-east\-2\[dq]
+        \- US East (Ohio) Region.
+    \- \[dq]us\-west\-2\[dq]
+        \- US West (Oregon) Region.
+    \- \[dq]us\-west\-1\[dq]
+        \- US West (Northern California) Region.
+    \- \[dq]ca\-central\-1\[dq]
+        \- Canada (Central) Region.
+    \- \[dq]eu\-west\-1\[dq]
+        \- EU (Ireland) Region.
+    \- \[dq]eu\-west\-2\[dq]
+        \- EU (London) Region.
+    \- \[dq]eu\-north\-1\[dq]
+        \- EU (Stockholm) Region.
+    \- \[dq]EU\[dq]
+        \- EU Region.
+    \- \[dq]ap\-southeast\-1\[dq]
+        \- Asia Pacific (Singapore) Region.
+    \- \[dq]ap\-southeast\-2\[dq]
+        \- Asia Pacific (Sydney) Region.
+    \- \[dq]ap\-northeast\-1\[dq]
+        \- Asia Pacific (Tokyo) Region.
+    \- \[dq]ap\-northeast\-2\[dq]
+        \- Asia Pacific (Seoul)
+    \- \[dq]ap\-south\-1\[dq]
+        \- Asia Pacific (Mumbai)
+    \- \[dq]ap\-east\-1\[dq]
+        \- Asia Pacific (Hong Kong)
+    \- \[dq]sa\-east\-1\[dq]
+        \- South America (Sao Paulo) Region.
+
+#### \-\-s3\-location\-constraint
+
+Location constraint \- must match endpoint when using IBM Cloud Public.
+For on\-prem COS, do not make a selection from this list, hit enter
+
+\- Config:      location_constraint
+\- Env Var:     RCLONE_S3_LOCATION_CONSTRAINT
+\- Type:        string
+\- Default:     \[dq]\[dq]
+\- Examples:
+    \- \[dq]us\-standard\[dq]
+        \- US Cross Region Standard
+    \- \[dq]us\-vault\[dq]
+        \- US Cross Region Vault
+    \- \[dq]us\-cold\[dq]
+        \- US Cross Region Cold
+    \- \[dq]us\-flex\[dq]
+        \- US Cross Region Flex
+    \- \[dq]us\-east\-standard\[dq]
+        \- US East Region Standard
+    \- \[dq]us\-east\-vault\[dq]
+        \- US East Region Vault
+    \- \[dq]us\-east\-cold\[dq]
+        \- US East Region Cold
+    \- \[dq]us\-east\-flex\[dq]
+        \- US East Region Flex
+    \- \[dq]us\-south\-standard\[dq]
+        \- US South Region Standard
+    \- \[dq]us\-south\-vault\[dq]
+        \- US South Region Vault
+    \- \[dq]us\-south\-cold\[dq]
+        \- US South Region Cold
+    \- \[dq]us\-south\-flex\[dq]
+        \- US South Region Flex
+    \- \[dq]eu\-standard\[dq]
+        \- EU Cross Region Standard
+    \- \[dq]eu\-vault\[dq]
+        \- EU Cross Region Vault
+    \- \[dq]eu\-cold\[dq]
+        \- EU Cross Region Cold
+    \- \[dq]eu\-flex\[dq]
+        \- EU Cross Region Flex
+    \- \[dq]eu\-gb\-standard\[dq]
+        \- Great Britain Standard
+    \- \[dq]eu\-gb\-vault\[dq]
+        \- Great Britain Vault
+    \- \[dq]eu\-gb\-cold\[dq]
+        \- Great Britain Cold
+    \- \[dq]eu\-gb\-flex\[dq]
+        \- Great Britain Flex
+    \- \[dq]ap\-standard\[dq]
+        \- APAC Standard
+    \- \[dq]ap\-vault\[dq]
+        \- APAC Vault
+    \- \[dq]ap\-cold\[dq]
+        \- APAC Cold
+    \- \[dq]ap\-flex\[dq]
+        \- APAC Flex
+    \- \[dq]mel01\-standard\[dq]
+        \- Melbourne Standard
+    \- \[dq]mel01\-vault\[dq]
+        \- Melbourne Vault
+    \- \[dq]mel01\-cold\[dq]
+        \- Melbourne Cold
+    \- \[dq]mel01\-flex\[dq]
+        \- Melbourne Flex
+    \- \[dq]tor01\-standard\[dq]
+        \- Toronto Standard
+    \- \[dq]tor01\-vault\[dq]
+        \- Toronto Vault
+    \- \[dq]tor01\-cold\[dq]
+        \- Toronto Cold
+    \- \[dq]tor01\-flex\[dq]
+        \- Toronto Flex
+
+#### \-\-s3\-location\-constraint
+
+Location constraint \- must be set to match the Region.
+Leave blank if not sure. Used when creating buckets only.
+
+\- Config:      location_constraint
+\- Env Var:     RCLONE_S3_LOCATION_CONSTRAINT
+\- Type:        string
+\- Default:     \[dq]\[dq]
+
+#### \-\-s3\-acl
+
 Canned ACL used when creating buckets and storing or copying objects.
 
+This ACL is used for creating objects and if bucket_acl isn\[aq]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\[aq]t copy the ACL from the source but rather writes a fresh one.
-Enter a string value. Press Enter for the default (\[dq]\[dq]).
-Choose a number from below, or type in your own value
- 1 / Owner gets FULL_CONTROL. No one else has access rights (default).
-   \[rs] \[dq]private\[dq]
- 2 / Owner gets FULL_CONTROL. The AllUsers group gets READ access.
-   \[rs] \[dq]public\-read\[dq]
-   / Owner gets FULL_CONTROL. The AllUsers group gets READ and WRITE access.
-[snip]
-acl> 1
+
+\- Config:      acl
+\- Env Var:     RCLONE_S3_ACL
+\- Type:        string
+\- Default:     \[dq]\[dq]
+\- Examples:
+    \- \[dq]private\[dq]
+        \- Owner gets FULL_CONTROL. No one else has access rights (default).
+    \- \[dq]public\-read\[dq]
+        \- Owner gets FULL_CONTROL. The AllUsers group gets READ access.
+    \- \[dq]public\-read\-write\[dq]
+        \- Owner gets FULL_CONTROL. The AllUsers group gets READ and WRITE access.
+        \- Granting this on a bucket is generally not recommended.
+    \- \[dq]authenticated\-read\[dq]
+        \- Owner gets FULL_CONTROL. The AuthenticatedUsers group gets READ access.
+    \- \[dq]bucket\-owner\-read\[dq]
+        \- Object owner gets FULL_CONTROL. Bucket owner gets READ access.
+        \- If you specify this canned ACL when creating a bucket, Amazon S3 ignores it.
+    \- \[dq]bucket\-owner\-full\-control\[dq]
+        \- Both the object owner and the bucket owner get FULL_CONTROL over the object.
+        \- If you specify this canned ACL when creating a bucket, Amazon S3 ignores it.
+    \- \[dq]private\[dq]
+        \- 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
+    \- \[dq]public\-read\[dq]
+        \- 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
+    \- \[dq]public\-read\-write\[dq]
+        \- Owner gets FULL_CONTROL. The AllUsers group gets READ and WRITE access. This acl is available on IBM Cloud (Infra), On\-Premise IBM COS
+    \- \[dq]authenticated\-read\[dq]
+        \- 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
+
+#### \-\-s3\-server\-side\-encryption
+
+The server\-side encryption algorithm used when storing this object in S3.
+
+\- Config:      server_side_encryption
+\- Env Var:     RCLONE_S3_SERVER_SIDE_ENCRYPTION
+\- Type:        string
+\- Default:     \[dq]\[dq]
+\- Examples:
+    \- \[dq]\[dq]
+        \- None
+    \- \[dq]AES256\[dq]
+        \- AES256
+    \- \[dq]aws:kms\[dq]
+        \- aws:kms
+
+#### \-\-s3\-sse\-kms\-key\-id
+
+If using KMS ID you must provide the ARN of Key.
+
+\- Config:      sse_kms_key_id
+\- Env Var:     RCLONE_S3_SSE_KMS_KEY_ID
+\- Type:        string
+\- Default:     \[dq]\[dq]
+\- Examples:
+    \- \[dq]\[dq]
+        \- None
+    \- \[dq]arn:aws:kms:us\-east\-1:*\[dq]
+        \- arn:aws:kms:*
+
+#### \-\-s3\-storage\-class
+
+The storage class to use when storing new objects in S3.
+
+\- Config:      storage_class
+\- Env Var:     RCLONE_S3_STORAGE_CLASS
+\- Type:        string
+\- Default:     \[dq]\[dq]
+\- Examples:
+    \- \[dq]\[dq]
+        \- Default
+    \- \[dq]STANDARD\[dq]
+        \- Standard storage class
+    \- \[dq]REDUCED_REDUNDANCY\[dq]
+        \- Reduced redundancy storage class
+    \- \[dq]STANDARD_IA\[dq]
+        \- Standard Infrequent Access storage class
+    \- \[dq]ONEZONE_IA\[dq]
+        \- One Zone Infrequent Access storage class
+    \- \[dq]GLACIER\[dq]
+        \- Glacier storage class
+    \- \[dq]DEEP_ARCHIVE\[dq]
+        \- Glacier Deep Archive storage class
+    \- \[dq]INTELLIGENT_TIERING\[dq]
+        \- Intelligent\-Tiering storage class
+
+#### \-\-s3\-storage\-class
+
 The storage class to use when storing new objects in OSS.
-Enter a string value. Press Enter for the default (\[dq]\[dq]).
-Choose a number from below, or type in your own value
- 1 / Default
-   \[rs] \[dq]\[dq]
- 2 / Standard storage class
-   \[rs] \[dq]STANDARD\[dq]
- 3 / Archive storage mode.
-   \[rs] \[dq]GLACIER\[dq]
- 4 / Infrequent access storage mode.
-   \[rs] \[dq]STANDARD_IA\[dq]
-storage_class> 1
-Edit advanced config? (y/n)
-y) Yes
-n) No
-y/n> 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> y
-\f[R]
-.fi
-.SS Netease NOS
-.PP
-For Netease NOS configure as per the configurator
-\f[C]rclone config\f[R] setting the provider \f[C]Netease\f[R].
-This will automatically set \f[C]force_path_style = false\f[R] which is
-necessary for it to run properly.
-.SS Backblaze B2
-.PP
-B2 is Backblaze\[cq]s cloud storage
-system (https://www.backblaze.com/b2/).
-.PP
-Paths are specified as \f[C]remote:bucket\f[R] (or \f[C]remote:\f[R] for
-the \f[C]lsd\f[R] command.) You may put subdirectories in too, eg
-\f[C]remote:bucket/path/to/dir\f[R].
-.PP
-Here is an example of making a b2 configuration.
-First run
-.IP
-.nf
-\f[C]
-rclone config
+
+\- Config:      storage_class
+\- Env Var:     RCLONE_S3_STORAGE_CLASS
+\- Type:        string
+\- Default:     \[dq]\[dq]
+\- Examples:
+    \- \[dq]\[dq]
+        \- Default
+    \- \[dq]STANDARD\[dq]
+        \- Standard storage class
+    \- \[dq]GLACIER\[dq]
+        \- Archive storage mode.
+    \- \[dq]STANDARD_IA\[dq]
+        \- Infrequent access storage mode.
+
+#### \-\-s3\-storage\-class
+
+The storage class to use when storing new objects in S3.
+
+\- Config:      storage_class
+\- Env Var:     RCLONE_S3_STORAGE_CLASS
+\- Type:        string
+\- Default:     \[dq]\[dq]
+\- Examples:
+    \- \[dq]\[dq]
+        \- Default
+    \- \[dq]STANDARD\[dq]
+        \- The Standard class for any upload; suitable for on\-demand content like streaming or CDN.
+    \- \[dq]GLACIER\[dq]
+        \- Archived storage; prices are lower, but it needs to be restored first to be accessed.
+
+### Advanced Options
+
+Here are the advanced options specific to s3 (Amazon S3 Compliant Storage Provider (AWS, Alibaba, Ceph, Digital Ocean, Dreamhost, IBM COS, Minio, etc)).
+
+#### \-\-s3\-bucket\-acl
+
+Canned ACL used when creating buckets.
+
+For more info visit https://docs.aws.amazon.com/AmazonS3/latest/dev/acl\-overview.html#canned\-acl
+
+Note that this ACL is applied when only when creating buckets.  If it
+isn\[aq]t set then \[dq]acl\[dq] is used instead.
+
+\- Config:      bucket_acl
+\- Env Var:     RCLONE_S3_BUCKET_ACL
+\- Type:        string
+\- Default:     \[dq]\[dq]
+\- Examples:
+    \- \[dq]private\[dq]
+        \- Owner gets FULL_CONTROL. No one else has access rights (default).
+    \- \[dq]public\-read\[dq]
+        \- Owner gets FULL_CONTROL. The AllUsers group gets READ access.
+    \- \[dq]public\-read\-write\[dq]
+        \- Owner gets FULL_CONTROL. The AllUsers group gets READ and WRITE access.
+        \- Granting this on a bucket is generally not recommended.
+    \- \[dq]authenticated\-read\[dq]
+        \- Owner gets FULL_CONTROL. The AuthenticatedUsers group gets READ access.
+
+#### \-\-s3\-sse\-customer\-algorithm
+
+If using SSE\-C, the server\-side encryption algorithm used when storing this object in S3.
+
+\- Config:      sse_customer_algorithm
+\- Env Var:     RCLONE_S3_SSE_CUSTOMER_ALGORITHM
+\- Type:        string
+\- Default:     \[dq]\[dq]
+\- Examples:
+    \- \[dq]\[dq]
+        \- None
+    \- \[dq]AES256\[dq]
+        \- AES256
+
+#### \-\-s3\-sse\-customer\-key
+
+If using SSE\-C you must provide the secret encryption key used to encrypt/decrypt your data.
+
+\- Config:      sse_customer_key
+\- Env Var:     RCLONE_S3_SSE_CUSTOMER_KEY
+\- Type:        string
+\- Default:     \[dq]\[dq]
+\- Examples:
+    \- \[dq]\[dq]
+        \- None
+
+#### \-\-s3\-sse\-customer\-key\-md5
+
+If using SSE\-C you must provide the secret encryption key MD5 checksum.
+
+\- Config:      sse_customer_key_md5
+\- Env Var:     RCLONE_S3_SSE_CUSTOMER_KEY_MD5
+\- Type:        string
+\- Default:     \[dq]\[dq]
+\- Examples:
+    \- \[dq]\[dq]
+        \- None
+
+#### \-\-s3\-upload\-cutoff
+
+Cutoff for switching to chunked upload
+
+Any files larger than this will be uploaded in chunks of chunk_size.
+The minimum is 0 and the maximum is 5GB.
+
+\- Config:      upload_cutoff
+\- Env Var:     RCLONE_S3_UPLOAD_CUTOFF
+\- Type:        SizeSuffix
+\- Default:     200M
+
+#### \-\-s3\-chunk\-size
+
+Chunk size to use for uploading.
+
+When uploading files larger than upload_cutoff or files with unknown
+size (eg from \[dq]rclone rcat\[dq] or uploaded with \[dq]rclone mount\[dq] or google
+photos or google docs) they will be uploaded as multipart uploads
+using this chunk size.
+
+Note that \[dq]\-\-s3\-upload\-concurrency\[dq] chunks of this size are buffered
+in memory per transfer.
+
+If you are transferring large files over high speed links and you have
+enough memory, then increasing this will speed up the transfers.
+
+Rclone will automatically increase the chunk size when uploading a
+large file of known size to stay below the 10,000 chunks limit.
+
+Files of unknown size are uploaded with the configured
+chunk_size. Since the default chunk size is 5MB and there can be at
+most 10,000 chunks, this means that by default the maximum size of
+file you can stream upload is 48GB.  If you wish to stream upload
+larger files then you will need to increase chunk_size.
+
+\- Config:      chunk_size
+\- Env Var:     RCLONE_S3_CHUNK_SIZE
+\- Type:        SizeSuffix
+\- Default:     5M
+
+#### \-\-s3\-max\-upload\-parts
+
+Maximum number of parts in a multipart upload.
+
+This option defines the maximum number of multipart chunks to use
+when doing a multipart upload.
+
+This can be useful if a service does not support the AWS S3
+specification of 10,000 chunks.
+
+Rclone will automatically increase the chunk size when uploading a
+large file of a known size to stay below this number of chunks limit.
+
+
+\- Config:      max_upload_parts
+\- Env Var:     RCLONE_S3_MAX_UPLOAD_PARTS
+\- Type:        int
+\- Default:     10000
+
+#### \-\-s3\-copy\-cutoff
+
+Cutoff for switching to multipart copy
+
+Any files larger than this that need to be server side copied will be
+copied in chunks of this size.
+
+The minimum is 0 and the maximum is 5GB.
+
+\- Config:      copy_cutoff
+\- Env Var:     RCLONE_S3_COPY_CUTOFF
+\- Type:        SizeSuffix
+\- Default:     4.656G
+
+#### \-\-s3\-disable\-checksum
+
+Don\[aq]t store MD5 checksum with object metadata
+
+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.
+
+\- Config:      disable_checksum
+\- Env Var:     RCLONE_S3_DISABLE_CHECKSUM
+\- Type:        bool
+\- Default:     false
+
+#### \-\-s3\-shared\-credentials\-file
+
+Path to the shared credentials file
+
+If env_auth = true then rclone can use a shared credentials file.
+
+If this variable is empty rclone will look for the
+\[dq]AWS_SHARED_CREDENTIALS_FILE\[dq] env variable. If the env value is empty
+it will default to the current user\[aq]s home directory.
+
+    Linux/OSX: \[dq]$HOME/.aws/credentials\[dq]
+    Windows:   \[dq]%USERPROFILE%\[rs].aws\[rs]credentials\[dq]
+
+
+\- Config:      shared_credentials_file
+\- Env Var:     RCLONE_S3_SHARED_CREDENTIALS_FILE
+\- Type:        string
+\- Default:     \[dq]\[dq]
+
+#### \-\-s3\-profile
+
+Profile to use in the shared credentials file
+
+If env_auth = true then rclone can use a shared credentials file. This
+variable controls which profile is used in that file.
+
+If empty it will default to the environment variable \[dq]AWS_PROFILE\[dq] or
+\[dq]default\[dq] if that environment variable is also not set.
+
+
+\- Config:      profile
+\- Env Var:     RCLONE_S3_PROFILE
+\- Type:        string
+\- Default:     \[dq]\[dq]
+
+#### \-\-s3\-session\-token
+
+An AWS session token
+
+\- Config:      session_token
+\- Env Var:     RCLONE_S3_SESSION_TOKEN
+\- Type:        string
+\- Default:     \[dq]\[dq]
+
+#### \-\-s3\-upload\-concurrency
+
+Concurrency for multipart uploads.
+
+This is the number of chunks of the same file that are uploaded
+concurrently.
+
+If you are uploading small numbers of large file over high speed link
+and these uploads do not fully utilize your bandwidth, then increasing
+this may help to speed up the transfers.
+
+\- Config:      upload_concurrency
+\- Env Var:     RCLONE_S3_UPLOAD_CONCURRENCY
+\- Type:        int
+\- Default:     4
+
+#### \-\-s3\-force\-path\-style
+
+If true use path style access if false use virtual hosted style.
+
+If this is true (the default) then rclone will use path style access,
+if false then rclone will use virtual path style. See [the AWS S3
+docs](https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingBucket.html#access\-bucket\-intro)
+for more info.
+
+Some providers (eg AWS, Aliyun OSS or Netease COS) require this set to
+false \- rclone will do this automatically based on the provider
+setting.
+
+\- Config:      force_path_style
+\- Env Var:     RCLONE_S3_FORCE_PATH_STYLE
+\- Type:        bool
+\- Default:     true
+
+#### \-\-s3\-v2\-auth
+
+If true use v2 authentication.
+
+If this is false (the default) then rclone will use v4 authentication.
+If it is set then rclone will use v2 authentication.
+
+Use this only if v4 signatures don\[aq]t work, eg pre Jewel/v10 CEPH.
+
+\- Config:      v2_auth
+\- Env Var:     RCLONE_S3_V2_AUTH
+\- Type:        bool
+\- Default:     false
+
+#### \-\-s3\-use\-accelerate\-endpoint
+
+If true use the AWS S3 accelerated endpoint.
+
+See: [AWS S3 Transfer acceleration](https://docs.aws.amazon.com/AmazonS3/latest/dev/transfer\-acceleration\-examples.html)
+
+\- Config:      use_accelerate_endpoint
+\- Env Var:     RCLONE_S3_USE_ACCELERATE_ENDPOINT
+\- Type:        bool
+\- Default:     false
+
+#### \-\-s3\-leave\-parts\-on\-error
+
+If true avoid calling abort upload on a failure, leaving all successfully uploaded parts on S3 for manual recovery.
+
+It should be set to true for resuming uploads across different sessions.
+
+WARNING: Storing parts of an incomplete multipart upload counts towards space usage on S3 and will add additional costs if not cleaned up.
+
+
+\- Config:      leave_parts_on_error
+\- Env Var:     RCLONE_S3_LEAVE_PARTS_ON_ERROR
+\- Type:        bool
+\- Default:     false
+
+#### \-\-s3\-list\-chunk
+
+Size of listing chunk (response list for each ListObject S3 request).
+
+This option is also known as \[dq]MaxKeys\[dq], \[dq]max\-items\[dq], or \[dq]page\-size\[dq] 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 [AWS S3](https://docs.aws.amazon.com/cli/latest/reference/s3/ls.html).
+In Ceph, this can be increased with the \[dq]rgw list buckets max chunk\[dq] option.
+
+
+\- Config:      list_chunk
+\- Env Var:     RCLONE_S3_LIST_CHUNK
+\- Type:        int
+\- Default:     1000
+
+#### \-\-s3\-no\-check\-bucket
+
+If set don\[aq]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.
+
+
+\- Config:      no_check_bucket
+\- Env Var:     RCLONE_S3_NO_CHECK_BUCKET
+\- Type:        bool
+\- Default:     false
+
+#### \-\-s3\-encoding
+
+This sets the encoding for the backend.
+
+See: the [encoding section in the overview](https://rclone.org/overview/#encoding) for more info.
+
+\- Config:      encoding
+\- Env Var:     RCLONE_S3_ENCODING
+\- Type:        MultiEncoder
+\- Default:     Slash,InvalidUtf8,Dot
+
+#### \-\-s3\-memory\-pool\-flush\-time
+
+How often internal memory buffer pools will be flushed.
+Uploads which requires additional buffers (f.e multipart) will use memory pool for allocations.
+This option controls how often unused buffers will be removed from the pool.
+
+\- Config:      memory_pool_flush_time
+\- Env Var:     RCLONE_S3_MEMORY_POOL_FLUSH_TIME
+\- Type:        Duration
+\- Default:     1m0s
+
+#### \-\-s3\-memory\-pool\-use\-mmap
+
+Whether to use mmap buffers in internal memory pool.
+
+\- Config:      memory_pool_use_mmap
+\- Env Var:     RCLONE_S3_MEMORY_POOL_USE_MMAP
+\- Type:        bool
+\- Default:     false
+
+### Backend commands
+
+Here are the commands specific to the s3 backend.
+
+Run them with
+
+    rclone backend COMMAND remote:
+
+The help below will explain what arguments each command takes.
+
+See [the \[dq]rclone backend\[dq] command](https://rclone.org/commands/rclone_backend/) for more
+info on how to pass options and arguments.
+
+These can be run on a running backend using the rc command
+[backend/command](https://rclone.org/rc/#backend/command).
+
+#### restore
+
+Restore objects from GLACIER to normal storage
+
+    rclone backend restore remote: [options] [<arguments>+]
+
+This command can be used to restore one or more objects from GLACIER
+to normal storage.
+
+Usage Examples:
+
+    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]
+
+This flag also obeys the filters. Test first with \-i/\-\-interactive or \-\-dry\-run flags
+
+    rclone \-i backend restore \-\-include \[dq]*.txt\[dq] s3:bucket/path \-o priority=Standard
+
+All the objects shown will be marked for restore, then
+
+    rclone backend restore \-\-include \[dq]*.txt\[dq] s3:bucket/path \-o priority=Standard
+
+It returns a list of status dictionaries with Remote and Status
+keys. The Status will be OK if it was successfull or an error message
+if not.
+
+    [
+        {
+            \[dq]Status\[dq]: \[dq]OK\[dq],
+            \[dq]Path\[dq]: \[dq]test.txt\[dq]
+        },
+        {
+            \[dq]Status\[dq]: \[dq]OK\[dq],
+            \[dq]Path\[dq]: \[dq]test/file4.txt\[dq]
+        }
+    ]
+
+
+
+Options:
+
+\- \[dq]description\[dq]: The optional description for the job.
+\- \[dq]lifetime\[dq]: Lifetime of the active copy in days
+\- \[dq]priority\[dq]: Priority of restore: Standard|Expedited|Bulk
+
+#### list\-multipart\-uploads
+
+List the unfinished multipart uploads
+
+    rclone backend list\-multipart\-uploads remote: [options] [<arguments>+]
+
+This command lists the unfinished multipart uploads in JSON format.
+
+    rclone backend list\-multipart s3:bucket/path/to/object
+
+It returns a dictionary of buckets with values as lists of unfinished
+multipart uploads.
+
+You can call it with no bucket in which case it lists all bucket, with
+a bucket or with a bucket and path.
+
+    {
+      \[dq]rclone\[dq]: [
+        {
+          \[dq]Initiated\[dq]: \[dq]2020\-06\-26T14:20:36Z\[dq],
+          \[dq]Initiator\[dq]: {
+            \[dq]DisplayName\[dq]: \[dq]XXX\[dq],
+            \[dq]ID\[dq]: \[dq]arn:aws:iam::XXX:user/XXX\[dq]
+          },
+          \[dq]Key\[dq]: \[dq]KEY\[dq],
+          \[dq]Owner\[dq]: {
+            \[dq]DisplayName\[dq]: null,
+            \[dq]ID\[dq]: \[dq]XXX\[dq]
+          },
+          \[dq]StorageClass\[dq]: \[dq]STANDARD\[dq],
+          \[dq]UploadId\[dq]: \[dq]XXX\[dq]
+        }
+      ],
+      \[dq]rclone\-1000files\[dq]: [],
+      \[dq]rclone\-dst\[dq]: []
+    }
+
+
+
+#### cleanup
+
+Remove unfinished multipart uploads.
+
+    rclone backend cleanup remote: [options] [<arguments>+]
+
+This command removes unfinished multipart uploads of age greater than
+max\-age which defaults to 24 hours.
+
+Note that you can use \-i/\-\-dry\-run with this command to see what it
+would do.
+
+    rclone backend cleanup s3:bucket/path/to/object
+    rclone backend cleanup \-o max\-age=7w s3:bucket/path/to/object
+
+Durations are parsed as per the rest of rclone, 2h, 7d, 7w etc.
+
+
+Options:
+
+\- \[dq]max\-age\[dq]: Max age of upload to delete
+
+
+
+### Anonymous access to public buckets ###
+
+If you want to use rclone to access a public bucket, configure with a
+blank \[ga]access_key_id\[ga] and \[ga]secret_access_key\[ga].  Your config should end
+up looking like this:
 \f[R]
 .fi
 .PP
-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.
+[anons3] type = s3 provider = AWS env_auth = false access_key_id =
+secret_access_key = region = us\-east\-1 endpoint = location_constraint
+= acl = private server_side_encryption = storage_class =
 .IP
 .nf
 \f[C]
+
+Then use it as normal with the name of the public bucket, eg
+
+    rclone lsd anons3:1000genomes
+
+You will be able to list and copy data but not upload it.
+
+### Ceph ###
+
+[Ceph](https://ceph.com/) is an open source unified, distributed
+storage system designed for excellent performance, reliability and
+scalability.  It has an S3 compatible object storage interface.
+
+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:
+
+\f[R]
+.fi
+.PP
+[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 =
+.IP
+.nf
+\f[C]
+
+If you are using an older version of CEPH, eg 10.2.x Jewel, then you
+may need to supply the parameter \[ga]\-\-s3\-upload\-cutoff 0\[ga] or put this in
+the config file as \[ga]upload_cutoff 0\[ga] to work around a bug which causes
+uploading of small files to fail.
+
+Note also that Ceph sometimes puts \[ga]/\[ga] 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 \[ga]/\[ga] escaped as \[ga]\[rs]/\[ga].  Make sure you
+only write \[ga]/\[ga] in the secret access key.
+
+Eg the dump from Ceph looks something like this (irrelevant keys
+removed).
+\f[R]
+.fi
+.PP
+{ \[dq]user_id\[dq]: \[dq]xxx\[dq], \[dq]display_name\[dq]:
+\[dq]xxxx\[dq], \[dq]keys\[dq]: [ { \[dq]user\[dq]: \[dq]xxx\[dq],
+\[dq]access_key\[dq]: \[dq]xxxxxx\[dq], \[dq]secret_key\[dq]:
+\[dq]xxxxxx/xxxx\[dq] } ], }
+.IP
+.nf
+\f[C]
+
+Because this is a json dump, it is encoding the \[ga]/\[ga] as \[ga]\[rs]/\[ga], so if you
+use the secret key as \[ga]xxxxxx/xxxx\[ga]  it will work fine.
+
+### Dreamhost ###
+
+Dreamhost [DreamObjects](https://www.dreamhost.com/cloud/storage/) is
+an object storage system based on CEPH.
+
+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:
+\f[R]
+.fi
+.PP
+[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 =
+.IP
+.nf
+\f[C]
+
+### DigitalOcean Spaces ###
+
+[Spaces](https://www.digitalocean.com/products/object\-storage/) is an [S3\-interoperable](https://developers.digitalocean.com/documentation/spaces/) object storage service from cloud provider DigitalOcean.
+
+To connect to DigitalOcean Spaces you will need an access key and secret key. These can be retrieved on the \[dq][Applications & API](https://cloud.digitalocean.com/settings/api/tokens)\[dq] page of the DigitalOcean control panel. They will be needed when prompted by \[ga]rclone config\[ga] for your \[ga]access_key_id\[ga] and \[ga]secret_access_key\[ga].
+
+When prompted for a \[ga]region\[ga] or \[ga]location_constraint\[ga], press enter to use the default value. The region must be included in the \[ga]endpoint\[ga] setting (e.g. \[ga]nyc3.digitaloceanspaces.com\[ga]). The default values can be used for other settings.
+
+Going through the whole process of creating a new remote by running \[ga]rclone config\[ga], each prompt should be answered as shown below:
+\f[R]
+.fi
+.PP
+Storage> s3 env_auth> 1 access_key_id> YOUR_ACCESS_KEY
+secret_access_key> YOUR_SECRET_KEY region> endpoint>
+nyc3.digitaloceanspaces.com location_constraint> acl> storage_class>
+.IP
+.nf
+\f[C]
+
+The resulting configuration file should look like:
+\f[R]
+.fi
+.PP
+[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 =
+.IP
+.nf
+\f[C]
+
+Once configured, you can create a new Space and begin copying files. For example:
+\f[R]
+.fi
+.PP
+rclone mkdir spaces:my\-new\-space rclone copy /path/to/files
+spaces:my\-new\-space
+.IP
+.nf
+\f[C]
+
+### IBM COS (S3) ###
+
+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\[cq]s Cloud Object Storage System (formerly Cleversafe). For more information visit: (http://www.ibm.com/cloud/object\-storage)
+
+To configure access to IBM COS S3, follow the steps below:
+
+1. Run rclone config and select n for a new remote.
+\f[R]
+.fi
+.IP
+.nf
+\f[C]
+2018/02/14 14:13:11 NOTICE: Config file \[dq]C:\[rs]\[rs]Users\[rs]\[rs]a\[rs]\[rs].config\[rs]\[rs]rclone\[rs]\[rs]rclone.conf\[dq] not found \- using defaults
 No remotes found \- make a new one
 n) New remote
+s) Set configuration password
 q) Quit config
-n/q> n
-name> remote
-Type of storage to configure.
+n/s/q> n
+\f[R]
+.fi
+.IP
+.nf
+\f[C]
+
+2. Enter the name for the configuration
+\f[R]
+.fi
+.IP
+.nf
+\f[C]
+name> <YOUR NAME>
+\f[R]
+.fi
+.IP
+.nf
+\f[C]
+
+3. Select \[dq]s3\[dq] storage.
+\f[R]
+.fi
+.PP
+Choose a number from below, or type in your own value 1 / Alias for an
+existing remote \ \[dq]alias\[dq] 2 / Amazon Drive \ \[dq]amazon cloud
+drive\[dq] 3 / Amazon S3 Complaint Storage Providers (Dreamhost, Ceph,
+Minio, IBM COS) \ \[dq]s3\[dq] 4 / Backblaze B2 \ \[dq]b2\[dq] [snip] 23
+/ http Connection \ \[dq]http\[dq] Storage> 3
+.IP
+.nf
+\f[C]
+
+4. Select IBM COS as the S3 Storage Provider.
+\f[R]
+.fi
+.PP
+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 \ \[dq]AWS\[dq] 2 / Choose this
+option to configure Storage to Ceph Systems \ \[dq]Ceph\[dq] 3 / Choose
+this option to configure Storage to Dreamhost \ \[dq]Dreamhost\[dq] 4 /
+Choose this option to the configure Storage to IBM COS S3
+\ \[dq]IBMCOS\[dq] 5 / Choose this option to the configure Storage to
+Minio \ \[dq]Minio\[dq] Provider>4
+.IP
+.nf
+\f[C]
+
+5. Enter the Access Key and Secret.
+\f[R]
+.fi
+.IP
+.nf
+\f[C]
+AWS Access Key ID \- leave blank for anonymous access or runtime credentials.
+access_key_id> <>
+AWS Secret Access Key (password) \- leave blank for anonymous access or runtime credentials.
+secret_access_key> <>
+\f[R]
+.fi
+.IP
+.nf
+\f[C]
+
+6. Specify the endpoint for IBM COS. For Public IBM COS, choose from the option below. For On Premise IBM COS, enter an enpoint address.
+\f[R]
+.fi
+.IP
+.nf
+\f[C]
+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
-[snip]
-XX / Backblaze B2
-   \[rs] \[dq]b2\[dq]
-[snip]
-Storage> b2
-Account ID or Application Key ID
-account> 123456789abc
-Application Key
-key> 0123456789abcdef0123456789abcdef0123456789
-Endpoint for the service \- leave blank normally.
-endpoint>
-Remote config
-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
-[remote]
-account = 123456789abc
-key = 0123456789abcdef0123456789abcdef0123456789
-endpoint =
-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
-y) Yes this is OK
-e) Edit this remote
-d) Delete this remote
-y/e/d> y
+ 1 / US Cross Region Endpoint
+   \[rs] \[dq]s3\-api.us\-geo.objectstorage.softlayer.net\[dq]
+ 2 / US Cross Region Dallas Endpoint
+   \[rs] \[dq]s3\-api.dal.us\-geo.objectstorage.softlayer.net\[dq]
+ 3 / US Cross Region Washington DC Endpoint
+   \[rs] \[dq]s3\-api.wdc\-us\-geo.objectstorage.softlayer.net\[dq]
+ 4 / US Cross Region San Jose Endpoint
+   \[rs] \[dq]s3\-api.sjc\-us\-geo.objectstorage.softlayer.net\[dq]
+ 5 / US Cross Region Private Endpoint
+   \[rs] \[dq]s3\-api.us\-geo.objectstorage.service.networklayer.com\[dq]
+ 6 / US Cross Region Dallas Private Endpoint
+   \[rs] \[dq]s3\-api.dal\-us\-geo.objectstorage.service.networklayer.com\[dq]
+ 7 / US Cross Region Washington DC Private Endpoint
+   \[rs] \[dq]s3\-api.wdc\-us\-geo.objectstorage.service.networklayer.com\[dq]
+ 8 / US Cross Region San Jose Private Endpoint
+   \[rs] \[dq]s3\-api.sjc\-us\-geo.objectstorage.service.networklayer.com\[dq]
+ 9 / US Region East Endpoint
+   \[rs] \[dq]s3.us\-east.objectstorage.softlayer.net\[dq]
+10 / US Region East Private Endpoint
+   \[rs] \[dq]s3.us\-east.objectstorage.service.networklayer.com\[dq]
+11 / US Region South Endpoint
 \f[R]
 .fi
 .PP
-This remote is called \f[C]remote\f[R] and can now be used like this
+[snip] 34 / Toronto Single Site Private Endpoint
+\ \[dq]s3.tor01.objectstorage.service.networklayer.com\[dq] endpoint>1
+.IP
+.nf
+\f[C]
+
+
+7. 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
+\f[R]
+.fi
+.IP
+.nf
+\f[C]
+ 1 / US Cross Region Standard
+   \[rs] \[dq]us\-standard\[dq]
+ 2 / US Cross Region Vault
+   \[rs] \[dq]us\-vault\[dq]
+ 3 / US Cross Region Cold
+   \[rs] \[dq]us\-cold\[dq]
+ 4 / US Cross Region Flex
+   \[rs] \[dq]us\-flex\[dq]
+ 5 / US East Region Standard
+   \[rs] \[dq]us\-east\-standard\[dq]
+ 6 / US East Region Vault
+   \[rs] \[dq]us\-east\-vault\[dq]
+ 7 / US East Region Cold
+   \[rs] \[dq]us\-east\-cold\[dq]
+ 8 / US East Region Flex
+   \[rs] \[dq]us\-east\-flex\[dq]
+ 9 / US South Region Standard
+   \[rs] \[dq]us\-south\-standard\[dq]
+10 / US South Region Vault
+   \[rs] \[dq]us\-south\-vault\[dq]
+\f[R]
+.fi
 .PP
+[snip] 32 / Toronto Flex \ \[dq]tor01\-flex\[dq] location_constraint>1
+.IP
+.nf
+\f[C]
+
+9. Specify a canned ACL. IBM Cloud (Strorage) supports \[dq]public\-read\[dq] and \[dq]private\[dq]. IBM Cloud(Infra) supports all the canned ACLs. On\-Premise COS supports all the canned ACLs.
+\f[R]
+.fi
+.PP
+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 \ \[dq]private\[dq] 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 \ \[dq]public\-read\[dq] 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
+\ \[dq]public\-read\-write\[dq] 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
+\ \[dq]authenticated\-read\[dq] acl> 1
+.IP
+.nf
+\f[C]
+
+
+12. Review the displayed configuration and accept to save the \[dq]remote\[dq] then quit. The config file should look like this
+\f[R]
+.fi
+.IP
+.nf
+\f[C]
+[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
+\f[R]
+.fi
+.IP
+.nf
+\f[C]
+
+13. Execute rclone commands
+\f[R]
+.fi
+.IP
+.nf
+\f[C]
+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
+\f[R]
+.fi
+.IP
+.nf
+\f[C]
+
+### Minio ###
+
+[Minio](https://minio.io/) is an object storage server built for cloud application developers and devops.
+
+It is very easy to install and provides an S3 compatible server which can be used by rclone.
+
+To use it, install Minio following the instructions [here](https://docs.minio.io/docs/minio\-quickstart\-guide).
+
+When it configures itself Minio will print something like this
+\f[R]
+.fi
+.PP
+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
+.PP
+Browser Access: http://192.168.1.106:9000 http://172.23.0.1:9000
+.PP
+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
+.PP
+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
+.PP
+Drive Capacity: 26 GiB Free, 165 GiB Total
+.IP
+.nf
+\f[C]
+
+These details need to go into \[ga]rclone config\[ga] like this.  Note that it
+is important to put the region in as stated above.
+\f[R]
+.fi
+.PP
+env_auth> 1 access_key_id> USWUXHGYZQYFYFFIT3RE secret_access_key>
+MOJRH0mkL1IPauahWITSVvyDrQbEEIwljvmxdq03 region> us\-east\-1 endpoint>
+http://192.168.1.106:9000 location_constraint> server_side_encryption>
+.IP
+.nf
+\f[C]
+
+Which makes the config file look like this
+\f[R]
+.fi
+.PP
+[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 =
+.IP
+.nf
+\f[C]
+
+So once set up, for example to copy files into a bucket
+\f[R]
+.fi
+.PP
+rclone copy /path/to/files minio:bucket
+.IP
+.nf
+\f[C]
+
+### Scaleway {#scaleway}
+
+[Scaleway](https://www.scaleway.com/object\-storage/) 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.
+
+Scaleway provides an S3 interface which can be configured for use with rclone like this:
+\f[R]
+.fi
+.PP
+[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 = acl = private server_side_encryption =
+storage_class =
+.IP
+.nf
+\f[C]
+
+### Wasabi ###
+
+[Wasabi](https://wasabi.com) 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.
+
+Wasabi provides an S3 interface which can be configured for use with
+rclone like this.
+\f[R]
+.fi
+.PP
+No remotes found \- make a new one n) New remote s) Set configuration
+password n/s> n name> wasabi Type of storage to configure.
+Choose a number from below, or type in your own value [snip] XX / Amazon
+S3 (also Dreamhost, Ceph, Minio) \ \[dq]s3\[dq] [snip] Storage> 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 \ \[dq]false\[dq] 2 / Get AWS credentials
+from the environment (env vars or IAM) \ \[dq]true\[dq] env_auth> 1 AWS
+Access Key ID \- leave blank for anonymous access or runtime
+credentials.
+access_key_id> YOURACCESSKEY AWS Secret Access Key (password) \- leave
+blank for anonymous access or runtime credentials.
+secret_access_key> 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.
+\ \[dq]us\-east\-1\[dq] [snip] region> 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> 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.
+\ \[dq]\[dq] [snip] location_constraint> 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).
+\ \[dq]private\[dq] [snip] acl> 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
+\ \[dq]\[dq] 2 / AES256 \ \[dq]AES256\[dq] server_side_encryption> The
+storage class to use when storing objects in S3.
+Choose a number from below, or type in your own value 1 / Default
+\ \[dq]\[dq] 2 / Standard storage class \ \[dq]STANDARD\[dq] 3 / Reduced
+redundancy storage class \ \[dq]REDUCED_REDUNDANCY\[dq] 4 / Standard
+Infrequent Access storage class \ \[dq]STANDARD_IA\[dq] storage_class>
+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> y
+.IP
+.nf
+\f[C]
+
+This will leave the config file looking like this.
+\f[R]
+.fi
+.PP
+[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 =
+.IP
+.nf
+\f[C]
+
+### Alibaba OSS {#alibaba\-oss}
+
+Here is an example of making an [Alibaba Cloud (Aliyun) OSS](https://www.alibabacloud.com/product/oss/)
+configuration.  First run:
+
+    rclone config
+
+This will guide you through an interactive setup process.
+\f[R]
+.fi
+.PP
+No remotes found \- make a new one n) New remote s) Set configuration
+password q) Quit config n/s/q> n name> oss Type of storage to configure.
+Enter a string value.
+Press Enter for the default (\[dq]\[dq]).
+Choose a number from below, or type in your own value [snip] 4 / Amazon
+S3 Compliant Storage Provider (AWS, Alibaba, Ceph, Digital Ocean,
+Dreamhost, IBM COS, Minio, etc) \ \[dq]s3\[dq] [snip] Storage> s3 Choose
+your S3 provider.
+Enter a string value.
+Press Enter for the default (\[dq]\[dq]).
+Choose a number from below, or type in your own value 1 / Amazon Web
+Services (AWS) S3 \ \[dq]AWS\[dq] 2 / Alibaba Cloud Object Storage
+System (OSS) formerly Aliyun \ \[dq]Alibaba\[dq] 3 / Ceph Object Storage
+\ \[dq]Ceph\[dq] [snip] provider> 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 (\[dq]false\[dq]).
+Choose a number from below, or type in your own value 1 / Enter AWS
+credentials in the next step \ \[dq]false\[dq] 2 / Get AWS credentials
+from the environment (env vars or IAM) \ \[dq]true\[dq] env_auth> 1 AWS
+Access Key ID.
+Leave blank for anonymous access or runtime credentials.
+Enter a string value.
+Press Enter for the default (\[dq]\[dq]).
+access_key_id> accesskeyid AWS Secret Access Key (password) Leave blank
+for anonymous access or runtime credentials.
+Enter a string value.
+Press Enter for the default (\[dq]\[dq]).
+secret_access_key> secretaccesskey Endpoint for OSS API.
+Enter a string value.
+Press Enter for the default (\[dq]\[dq]).
+Choose a number from below, or type in your own value 1 / East China 1
+(Hangzhou) \ \[dq]oss\-cn\-hangzhou.aliyuncs.com\[dq] 2 / East China 2
+(Shanghai) \ \[dq]oss\-cn\-shanghai.aliyuncs.com\[dq] 3 / North China 1
+(Qingdao) \ \[dq]oss\-cn\-qingdao.aliyuncs.com\[dq] [snip] endpoint> 1
+Canned ACL used when creating buckets and storing or copying objects.
+.PP
+Note that this ACL is applied when server side copying objects as S3
+doesn\[aq]t copy the ACL from the source but rather writes a fresh one.
+Enter a string value.
+Press Enter for the default (\[dq]\[dq]).
+Choose a number from below, or type in your own value 1 / Owner gets
+FULL_CONTROL.
+No one else has access rights (default).
+\ \[dq]private\[dq] 2 / Owner gets FULL_CONTROL.
+The AllUsers group gets READ access.
+\ \[dq]public\-read\[dq] / Owner gets FULL_CONTROL.
+The AllUsers group gets READ and WRITE access.
+[snip] acl> 1 The storage class to use when storing new objects in OSS.
+Enter a string value.
+Press Enter for the default (\[dq]\[dq]).
+Choose a number from below, or type in your own value 1 / Default
+\ \[dq]\[dq] 2 / Standard storage class \ \[dq]STANDARD\[dq] 3 / Archive
+storage mode.
+\ \[dq]GLACIER\[dq] 4 / Infrequent access storage mode.
+\ \[dq]STANDARD_IA\[dq] storage_class> 1 Edit advanced config?
+(y/n) y) Yes n) No y/n> 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> y
+.IP
+.nf
+\f[C]
+
+### Netease NOS  ###
+
+For Netease NOS configure as per the configurator \[ga]rclone config\[ga]
+setting the provider \[ga]Netease\[ga].  This will automatically set
+\[ga]force_path_style = false\[ga] which is necessary for it to run properly.
+
+ Backblaze B2
+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
+
+B2 is [Backblaze\[aq]s cloud storage system](https://www.backblaze.com/b2/).
+
+Paths are specified as \[ga]remote:bucket\[ga] (or \[ga]remote:\[ga] for the \[ga]lsd\[ga]
+command.)  You may put subdirectories in too, eg \[ga]remote:bucket/path/to/dir\[ga].
+
+Here is an example of making a b2 configuration.  First run
+
+    rclone config
+
+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.
+\f[R]
+.fi
+.PP
+No remotes found \- make a new one n) New remote q) Quit config n/q> n
+name> remote Type of storage to configure.
+Choose a number from below, or type in your own value [snip] XX /
+Backblaze B2 \ \[dq]b2\[dq] [snip] Storage> b2 Account ID or Application
+Key ID account> 123456789abc Application Key key>
+0123456789abcdef0123456789abcdef0123456789 Endpoint for the service \-
+leave blank normally.
+endpoint> Remote config \-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
+[remote] account = 123456789abc key =
+0123456789abcdef0123456789abcdef0123456789 endpoint =
+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\- y) Yes this is OK e) Edit this
+remote d) Delete this remote y/e/d> y
+.IP
+.nf
+\f[C]
+
+This remote is called \[ga]remote\[ga] and can now be used like this
+
 See all buckets
-.IP
-.nf
-\f[C]
-rclone lsd remote:
-\f[R]
-.fi
-.PP
+
+    rclone lsd remote:
+
 Create a new bucket
-.IP
-.nf
-\f[C]
-rclone mkdir remote:bucket
-\f[R]
-.fi
-.PP
+
+    rclone mkdir remote:bucket
+
 List the contents of a bucket
-.IP
-.nf
-\f[C]
-rclone ls remote:bucket
-\f[R]
-.fi
-.PP
-Sync \f[C]/home/local/directory\f[R] to the remote bucket, deleting any
+
+    rclone ls remote:bucket
+
+Sync \[ga]/home/local/directory\[ga] to the remote bucket, deleting any
 excess files in the bucket.
-.IP
-.nf
-\f[C]
-rclone sync /home/local/directory remote:bucket
-\f[R]
-.fi
-.SS Application Keys
-.PP
-B2 supports multiple Application Keys for different access permission to
-B2 Buckets (https://www.backblaze.com/b2/docs/application_keys.html).
-.PP
-You can use these with rclone too; you will need to use rclone version
-1.43 or later.
-.PP
-Follow Backblaze\[cq]s docs to create an Application Key with the
-required permission and add the \f[C]applicationKeyId\f[R] as the
-\f[C]account\f[R] and the \f[C]Application Key\f[R] itself as the
-\f[C]key\f[R].
-.PP
-Note that you must put the \f[I]applicationKeyId\f[R] as the
-\f[C]account\f[R] \[en] you can\[cq]t use the master Account ID.
-If you try then B2 will return 401 errors.
-.SS \[en]fast\-list
-.PP
-This remote supports \f[C]\-\-fast\-list\f[R] which allows you to use
-fewer transactions in exchange for more memory.
-See the rclone docs (https://rclone.org/docs/#fast-list) for more
-details.
-.SS Modified time
-.PP
+
+    rclone sync \-i /home/local/directory remote:bucket
+
+### Application Keys ###
+
+B2 supports multiple [Application Keys for different access permission
+to B2 Buckets](https://www.backblaze.com/b2/docs/application_keys.html).
+
+You can use these with rclone too; you will need to use rclone version 1.43
+or later.
+
+Follow Backblaze\[aq]s docs to create an Application Key with the required
+permission and add the \[ga]applicationKeyId\[ga] as the \[ga]account\[ga] and the
+\[ga]Application Key\[ga] itself as the \[ga]key\[ga].
+
+Note that you must put the _applicationKeyId_ as the \[ga]account\[ga] \[en] you
+can\[aq]t use the master Account ID.  If you try then B2 will return 401
+errors.
+
+### \-\-fast\-list ###
+
+This remote supports \[ga]\-\-fast\-list\[ga] which allows you to use fewer
+transactions in exchange for more memory. See the [rclone
+docs](https://rclone.org/docs/#fast\-list) for more details.
+
+### Modified time ###
+
 The modified time is stored as metadata on the object as
-\f[C]X\-Bz\-Info\-src_last_modified_millis\f[R] as milliseconds since
-1970\-01\-01 in the Backblaze standard.
-Other tools should be able to use this as a modified time.
-.PP
-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.
-.SS Restricted filename characters
-.PP
-In addition to the default restricted characters
-set (https://rclone.org/overview/#restricted-characters) the following
-characters are also replaced:
-.PP
-.TS
-tab(@);
-l c c.
-T{
-Character
-T}@T{
-Value
-T}@T{
-Replacement
-T}
-_
-T{
-\[rs]
-T}@T{
-0x5C
-T}@T{
-\[uFF3C]
-T}
-.TE
-.PP
-Invalid UTF\-8 bytes will also be
-replaced (https://rclone.org/overview/#invalid-utf8), as they can\[cq]t
-be used in JSON strings.
-.SS SHA1 checksums
-.PP
+\[ga]X\-Bz\-Info\-src_last_modified_millis\[ga] as milliseconds since 1970\-01\-01
+in the Backblaze standard.  Other tools should be able to use this as
+a modified time.
+
+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.
+
+#### Restricted filename characters
+
+In addition to the [default restricted characters set](https://rclone.org/overview/#restricted\-characters)
+the following characters are also replaced:
+
+| Character | Value | Replacement |
+| \-\-\-\-\-\-\-\-\- |:\-\-\-\-\-:|:\-\-\-\-\-\-\-\-\-\-\-:|
+| \[rs]         | 0x5C  | \[uFF3C]           |
+
+Invalid UTF\-8 bytes will also be [replaced](https://rclone.org/overview/#invalid\-utf8),
+as they can\[aq]t be used in JSON strings.
+
+Note that in 2020\-05 Backblaze started allowing \[rs] characters in file
+names. Rclone hasn\[aq]t changed its encoding as this could cause syncs to
+re\-transfer files. If you want rclone not to replace \[rs] then see the
+\[ga]\-\-b2\-encoding\[ga] flag below and remove the \[ga]BackSlash\[ga] from the
+string. This can be set in the config.
+
+### SHA1 checksums ###
+
 The SHA1 checksums of the files are checked on upload and download and
 will be used in the syncing process.
-.PP
-Large files (bigger than the limit in \f[C]\-\-b2\-upload\-cutoff\f[R])
-which are uploaded in chunks will store their SHA1 on the object as
-\f[C]X\-Bz\-Info\-large_file_sha1\f[R] as recommended by Backblaze.
-.PP
-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 the overview (https://rclone.org/overview/#features) for exactly
-which remotes support SHA1.
-.PP
-Sources which don\[cq]t support SHA1, in particular \f[C]crypt\f[R] will
-upload large files without SHA1 checksums.
-This may be fixed in the future (see
-#1767 (https://github.com/rclone/rclone/issues/1767)).
-.PP
-Files sizes below \f[C]\-\-b2\-upload\-cutoff\f[R] will always have an
-SHA1 regardless of the source.
-.SS Transfers
-.PP
+
+Large files (bigger than the limit in \[ga]\-\-b2\-upload\-cutoff\[ga]) which are
+uploaded in chunks will store their SHA1 on the object as
+\[ga]X\-Bz\-Info\-large_file_sha1\[ga] as recommended by Backblaze.
+
+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 [the overview](https://rclone.org/overview/#features) for exactly which remotes
+support SHA1.
+
+Sources which don\[aq]t support SHA1, in particular \[ga]crypt\[ga] will upload
+large files without SHA1 checksums.  This may be fixed in the future
+(see [#1767](https://github.com/rclone/rclone/issues/1767)).
+
+Files sizes below \[ga]\-\-b2\-upload\-cutoff\[ga] will always have an SHA1
+regardless of the source.
+
+### Transfers ###
+
 Backblaze recommends that you do lots of transfers simultaneously for
-maximum speed.
-In tests from my SSD equipped laptop the optimum setting is about
-\f[C]\-\-transfers 32\f[R] 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 \f[C]\-\-transfers 4\f[R] is definitely too low for
-Backblaze B2 though.
-.PP
-Note that uploading big files (bigger than 200 MB by default) will use a
-96 MB RAM buffer by default.
-There can be at most \f[C]\-\-transfers\f[R] of these in use at any
-moment, so this sets the upper limit on the memory used.
-.SS Versions
-.PP
-When rclone uploads a new version of a file it creates a new version of
-it (https://www.backblaze.com/b2/docs/file_versions.html).
+maximum speed.  In tests from my SSD equipped laptop the optimum
+setting is about \[ga]\-\-transfers 32\[ga] 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 \[ga]\-\-transfers 4\[ga] is
+definitely too low for Backblaze B2 though.
+
+Note that uploading big files (bigger than 200 MB by default) will use
+a 96 MB RAM buffer by default.  There can be at most \[ga]\-\-transfers\[ga] of
+these in use at any moment, so this sets the upper limit on the memory
+used.
+
+### Versions ###
+
+When rclone uploads a new version of a file it creates a [new version
+of it](https://www.backblaze.com/b2/docs/file_versions.html).
 Likewise when you delete a file, the old version will be marked hidden
-and still be available.
-Conversely, you may opt in to a \[lq]hard delete\[rq] of files with the
-\f[C]\-\-b2\-hard\-delete\f[R] flag which would permanently remove the
-file instead of hiding it.
-.PP
-Old versions of files, where available, are visible using the
-\f[C]\-\-b2\-versions\f[R] flag.
-.PP
-\f[B]NB\f[R] Note that \f[C]\-\-b2\-versions\f[R] does not work with
-crypt at the moment
-#1627 (https://github.com/rclone/rclone/issues/1627).
-Using \[en]backup\-dir (https://rclone.org/docs/#backup-dir-dir) with
-rclone is the recommended way of working around this.
-.PP
+and still be available.  Conversely, you may opt in to a \[dq]hard delete\[dq]
+of files with the \[ga]\-\-b2\-hard\-delete\[ga] flag which would permanently remove
+the file instead of hiding it.
+
+Old versions of files, where available, are visible using the 
+\[ga]\-\-b2\-versions\[ga] flag.
+
+**NB** Note that \[ga]\-\-b2\-versions\[ga] does not work with crypt at the
+moment [#1627](https://github.com/rclone/rclone/issues/1627). Using
+[\-\-backup\-dir](https://rclone.org/docs/#backup\-dir\-dir) with rclone is the recommended
+way of working around this.
+
 If you wish to remove all the old versions then you can use the
-\f[C]rclone cleanup remote:bucket\f[R] 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, eg \f[C]rclone cleanup remote:bucket/path/to/stuff\f[R].
-.PP
-Note that \f[C]cleanup\f[R] will remove partially uploaded files from
-the bucket if they are more than a day old.
-.PP
-When you \f[C]purge\f[R] a bucket, the current and the old versions will
-be deleted then the bucket will be deleted.
-.PP
-However \f[C]delete\f[R] will cause the current versions of the files to
+\[ga]rclone cleanup remote:bucket\[ga] 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,
+eg \[ga]rclone cleanup remote:bucket/path/to/stuff\[ga].
+
+Note that \[ga]cleanup\[ga] will remove partially uploaded files from the bucket
+if they are more than a day old.
+
+When you \[ga]purge\[ga] a bucket, the current and the old versions will be
+deleted then the bucket will be deleted.
+
+However \[ga]delete\[ga] will cause the current versions of the files to
 become hidden old versions.
-.PP
-Here is a session showing the listing and retrieval of an old version
-followed by a \f[C]cleanup\f[R] of the old versions.
-.PP
-Show current version and all the versions with
-\f[C]\-\-b2\-versions\f[R] flag.
-.IP
-.nf
-\f[C]
-$ 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
+Here is a session showing the listing and retrieval of an old
+version followed by a \[ga]cleanup\[ga] of the old versions.
+
+Show current version and all the versions with \[ga]\-\-b2\-versions\[ga] flag.
 \f[R]
 .fi
 .PP
+$ rclone \-q ls b2:cleanup\-test 9 one.txt
+.PP
+$ 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
+.IP
+.nf
+\f[C]
+
 Retrieve an old version
-.IP
-.nf
-\f[C]
-$ 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
 \f[R]
 .fi
 .PP
-Clean up all the old versions and show that they\[cq]ve gone.
+$ rclone \-q \-\-b2\-versions copy
+b2:cleanup\-test/one\-v2016\-07\-04\-141003\-000.txt /tmp
+.PP
+$ 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
 .IP
 .nf
 \f[C]
+
+Clean up all the old versions and show that they\[aq]ve gone.
+\f[R]
+.fi
+.PP
 $ 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
-\f[R]
-.fi
-.SS Data usage
 .PP
-It is useful to know how many requests are sent to the server in
-different scenarios.
+$ rclone \-q ls b2:cleanup\-test 9 one.txt
 .PP
-All copy commands send the following 4 requests:
+$ rclone \-q \-\-b2\-versions ls b2:cleanup\-test 9 one.txt
 .IP
 .nf
 \f[C]
-/b2api/v1/b2_authorize_account
-/b2api/v1/b2_create_bucket
-/b2api/v1/b2_list_buckets
-/b2api/v1/b2_list_file_names
+
+### Data usage ###
+
+It is useful to know how many requests are sent to the server in different scenarios.
+
+All copy commands send the following 4 requests:
 \f[R]
 .fi
 .PP
-The \f[C]b2_list_file_names\f[R] 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
-#818 (https://github.com/rclone/rclone/issues/818) 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.
-.PP
+/b2api/v1/b2_authorize_account /b2api/v1/b2_create_bucket
+/b2api/v1/b2_list_buckets /b2api/v1/b2_list_file_names
+.IP
+.nf
+\f[C]
+
+The \[ga]b2_list_file_names\[ga] 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
+[#818](https://github.com/rclone/rclone/issues/818) 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.
+
 Uploading files that do not require chunking, will send 2 requests per
 file upload:
-.IP
-.nf
-\f[C]
-/b2api/v1/b2_get_upload_url
-/b2api/v1/b2_upload_file/
 \f[R]
 .fi
 .PP
+/b2api/v1/b2_get_upload_url /b2api/v1/b2_upload_file/
+.IP
+.nf
+\f[C]
+
 Uploading files requiring chunking, will send 2 requests (one each to
 start and finish the upload) and another 2 requests for each chunk:
-.IP
-.nf
-\f[C]
-/b2api/v1/b2_start_large_file
-/b2api/v1/b2_get_upload_part_url
-/b2api/v1/b2_upload_part/
-/b2api/v1/b2_finish_large_file
-\f[R]
-.fi
-.SS Versions
-.PP
-Versions can be viewed with the \f[C]\-\-b2\-versions\f[R] flag.
-When it is set rclone will show and act on older versions of files.
-For example
-.PP
-Listing without \f[C]\-\-b2\-versions\f[R]
-.IP
-.nf
-\f[C]
-$ rclone \-q ls b2:cleanup\-test
-        9 one.txt
 \f[R]
 .fi
 .PP
+/b2api/v1/b2_start_large_file /b2api/v1/b2_get_upload_part_url
+/b2api/v1/b2_upload_part/ /b2api/v1/b2_finish_large_file
+.IP
+.nf
+\f[C]
+
+#### Versions ####
+
+Versions can be viewed with the \[ga]\-\-b2\-versions\[ga] flag. When it is set
+rclone will show and act on older versions of files.  For example
+
+Listing without \[ga]\-\-b2\-versions\[ga]
+\f[R]
+.fi
+.PP
+$ rclone \-q ls b2:cleanup\-test 9 one.txt
+.IP
+.nf
+\f[C]
+
 And with
-.IP
-.nf
-\f[C]
-$ 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
 \f[R]
 .fi
 .PP
-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.
-.PP
-Note that when using \f[C]\-\-b2\-versions\f[R] no file write operations
-are permitted, so you can\[cq]t upload files or delete them.
-.SS B2 and rclone link
-.PP
+$ 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
+.IP
+.nf
+\f[C]
+
+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.
+
+Note that when using \[ga]\-\-b2\-versions\[ga] no file write operations are
+permitted, so you can\[aq]t upload files or delete them.
+
+### B2 and rclone link ###
+
 Rclone supports generating file share links for private B2 buckets.
 They can either be for a file for example:
-.IP
-.nf
-\f[C]
+\f[R]
+.fi
+.PP
 \&./rclone link B2:bucket/path/to/file.txt
 https://f002.backblazeb2.com/file/bucket/path/to/file.txt?Authorization=xxxxxxxx
-\f[R]
-.fi
-.PP
-or if run on a directory you will get:
 .IP
 .nf
 \f[C]
+
+or if run on a directory you will get:
+\f[R]
+.fi
+.PP
 \&./rclone link B2:bucket/path
 https://f002.backblazeb2.com/file/bucket/path?Authorization=xxxxxxxx
-\f[R]
-.fi
-.PP
-you can then use the authorization token (the part of the url from the
-\f[C]?Authorization=\f[R] on) on any file path under that directory.
-For example:
 .IP
 .nf
 \f[C]
+
+you can then use the authorization token (the part of the url from the
+ \[ga]?Authorization=\[ga] on) on any file path under that directory. For example:
+\f[R]
+.fi
+.PP
 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
-\f[R]
-.fi
-.SS Standard Options
-.PP
+.IP
+.nf
+\f[C]
+
+
+### Standard Options
+
 Here are the standard options specific to b2 (Backblaze B2).
-.SS \[en]b2\-account
-.PP
+
+#### \-\-b2\-account
+
 Account ID or Application Key ID
-.IP \[bu] 2
-Config: account
-.IP \[bu] 2
-Env Var: RCLONE_B2_ACCOUNT
-.IP \[bu] 2
-Type: string
-.IP \[bu] 2
-Default: \[dq]\[dq]
-.SS \[en]b2\-key
-.PP
+
+\- Config:      account
+\- Env Var:     RCLONE_B2_ACCOUNT
+\- Type:        string
+\- Default:     \[dq]\[dq]
+
+#### \-\-b2\-key
+
 Application Key
-.IP \[bu] 2
-Config: key
-.IP \[bu] 2
-Env Var: RCLONE_B2_KEY
-.IP \[bu] 2
-Type: string
-.IP \[bu] 2
-Default: \[dq]\[dq]
-.SS \[en]b2\-hard\-delete
-.PP
+
+\- Config:      key
+\- Env Var:     RCLONE_B2_KEY
+\- Type:        string
+\- Default:     \[dq]\[dq]
+
+#### \-\-b2\-hard\-delete
+
 Permanently delete files on remote removal, otherwise hide files.
-.IP \[bu] 2
-Config: hard_delete
-.IP \[bu] 2
-Env Var: RCLONE_B2_HARD_DELETE
-.IP \[bu] 2
-Type: bool
-.IP \[bu] 2
-Default: false
-.SS Advanced Options
-.PP
+
+\- Config:      hard_delete
+\- Env Var:     RCLONE_B2_HARD_DELETE
+\- Type:        bool
+\- Default:     false
+
+### Advanced Options
+
 Here are the advanced options specific to b2 (Backblaze B2).
-.SS \[en]b2\-endpoint
-.PP
+
+#### \-\-b2\-endpoint
+
 Endpoint for the service.
 Leave blank normally.
-.IP \[bu] 2
-Config: endpoint
-.IP \[bu] 2
-Env Var: RCLONE_B2_ENDPOINT
-.IP \[bu] 2
-Type: string
-.IP \[bu] 2
-Default: \[dq]\[dq]
-.SS \[en]b2\-test\-mode
-.PP
+
+\- Config:      endpoint
+\- Env Var:     RCLONE_B2_ENDPOINT
+\- Type:        string
+\- Default:     \[dq]\[dq]
+
+#### \-\-b2\-test\-mode
+
 A flag string for X\-Bz\-Test\-Mode header for debugging.
-.PP
-This is for debugging purposes only.
-Setting it to one of the strings below will cause b2 to return specific
-errors:
-.IP \[bu] 2
-\[lq]fail_some_uploads\[rq]
-.IP \[bu] 2
-\[lq]expire_some_account_authorization_tokens\[rq]
-.IP \[bu] 2
-\[lq]force_cap_exceeded\[rq]
-.PP
-These will be set in the \[lq]X\-Bz\-Test\-Mode\[rq] header which is
-documented in the b2 integrations
-checklist (https://www.backblaze.com/b2/docs/integration_checklist.html).
-.IP \[bu] 2
-Config: test_mode
-.IP \[bu] 2
-Env Var: RCLONE_B2_TEST_MODE
-.IP \[bu] 2
-Type: string
-.IP \[bu] 2
-Default: \[dq]\[dq]
-.SS \[en]b2\-versions
-.PP
+
+This is for debugging purposes only. Setting it to one of the strings
+below will cause b2 to return specific errors:
+
+  * \[dq]fail_some_uploads\[dq]
+  * \[dq]expire_some_account_authorization_tokens\[dq]
+  * \[dq]force_cap_exceeded\[dq]
+
+These will be set in the \[dq]X\-Bz\-Test\-Mode\[dq] header which is documented
+in the [b2 integrations checklist](https://www.backblaze.com/b2/docs/integration_checklist.html).
+
+\- Config:      test_mode
+\- Env Var:     RCLONE_B2_TEST_MODE
+\- Type:        string
+\- Default:     \[dq]\[dq]
+
+#### \-\-b2\-versions
+
 Include old versions in directory listings.
-Note that when using this no file write operations are permitted, so you
-can\[cq]t upload files or delete them.
-.IP \[bu] 2
-Config: versions
-.IP \[bu] 2
-Env Var: RCLONE_B2_VERSIONS
-.IP \[bu] 2
-Type: bool
-.IP \[bu] 2
-Default: false
-.SS \[en]b2\-upload\-cutoff
-.PP
+Note that when using this no file write operations are permitted,
+so you can\[aq]t upload files or delete them.
+
+\- Config:      versions
+\- Env Var:     RCLONE_B2_VERSIONS
+\- Type:        bool
+\- Default:     false
+
+#### \-\-b2\-upload\-cutoff
+
 Cutoff for switching to chunked upload.
-.PP
-Files above this size will be uploaded in chunks of
-\[lq]\[en]b2\-chunk\-size\[rq].
-.PP
+
+Files above this size will be uploaded in chunks of \[dq]\-\-b2\-chunk\-size\[dq].
+
 This value should be set no larger than 4.657GiB (== 5GB).
-.IP \[bu] 2
-Config: upload_cutoff
-.IP \[bu] 2
-Env Var: RCLONE_B2_UPLOAD_CUTOFF
-.IP \[bu] 2
-Type: SizeSuffix
-.IP \[bu] 2
-Default: 200M
-.SS \[en]b2\-chunk\-size
-.PP
-Upload chunk size.
-Must fit in memory.
-.PP
-When uploading large files, chunk the file into this size.
-Note that these chunks are buffered in memory and there might a maximum
-of \[lq]\[en]transfers\[rq] chunks in progress at once.
-5,000,000 Bytes is the minimum size.
-.IP \[bu] 2
-Config: chunk_size
-.IP \[bu] 2
-Env Var: RCLONE_B2_CHUNK_SIZE
-.IP \[bu] 2
-Type: SizeSuffix
-.IP \[bu] 2
-Default: 96M
-.SS \[en]b2\-disable\-checksum
-.PP
+
+\- Config:      upload_cutoff
+\- Env Var:     RCLONE_B2_UPLOAD_CUTOFF
+\- Type:        SizeSuffix
+\- Default:     200M
+
+#### \-\-b2\-copy\-cutoff
+
+Cutoff for switching to multipart copy
+
+Any files larger than this that need to be server side copied will be
+copied in chunks of this size.
+
+The minimum is 0 and the maximum is 4.6GB.
+
+\- Config:      copy_cutoff
+\- Env Var:     RCLONE_B2_COPY_CUTOFF
+\- Type:        SizeSuffix
+\- Default:     4G
+
+#### \-\-b2\-chunk\-size
+
+Upload chunk size. Must fit in memory.
+
+When uploading large files, chunk the file into this size.  Note that
+these chunks are buffered in memory and there might a maximum of
+\[dq]\-\-transfers\[dq] chunks in progress at once.  5,000,000 Bytes is the
+minimum size.
+
+\- Config:      chunk_size
+\- Env Var:     RCLONE_B2_CHUNK_SIZE
+\- Type:        SizeSuffix
+\- Default:     96M
+
+#### \-\-b2\-disable\-checksum
+
 Disable checksums for large (> upload cutoff) files
-.PP
+
 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.
-.IP \[bu] 2
-Config: disable_checksum
-.IP \[bu] 2
-Env Var: RCLONE_B2_DISABLE_CHECKSUM
-.IP \[bu] 2
-Type: bool
-.IP \[bu] 2
-Default: false
-.SS \[en]b2\-download\-url
-.PP
+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.
+
+\- Config:      disable_checksum
+\- Env Var:     RCLONE_B2_DISABLE_CHECKSUM
+\- Type:        bool
+\- Default:     false
+
+#### \-\-b2\-download\-url
+
 Custom endpoint for downloads.
-.PP
-This is usually set to a Cloudflare CDN URL as Backblaze offers free
-egress for data downloaded through the Cloudflare network.
+
+This is usually set to a Cloudflare CDN URL as Backblaze offers
+free egress for data downloaded through the Cloudflare network.
 This is probably only useful for a public bucket.
 Leave blank if you want to use the endpoint provided by Backblaze.
-.IP \[bu] 2
-Config: download_url
-.IP \[bu] 2
-Env Var: RCLONE_B2_DOWNLOAD_URL
-.IP \[bu] 2
-Type: string
-.IP \[bu] 2
-Default: \[dq]\[dq]
-.SS \[en]b2\-download\-auth\-duration
-.PP
-Time before the authorization token will expire in s or suffix
-ms|s|m|h|d.
-.PP
+
+\- Config:      download_url
+\- Env Var:     RCLONE_B2_DOWNLOAD_URL
+\- Type:        string
+\- Default:     \[dq]\[dq]
+
+#### \-\-b2\-download\-auth\-duration
+
+Time before the authorization token will expire in s or suffix ms|s|m|h|d.
+
 The duration before the download authorization token will expire.
-The minimum value is 1 second.
-The maximum value is one week.
-.IP \[bu] 2
-Config: download_auth_duration
-.IP \[bu] 2
-Env Var: RCLONE_B2_DOWNLOAD_AUTH_DURATION
-.IP \[bu] 2
-Type: Duration
-.IP \[bu] 2
-Default: 1w
-.SS \[en]b2\-encoding
-.PP
+The minimum value is 1 second. The maximum value is one week.
+
+\- Config:      download_auth_duration
+\- Env Var:     RCLONE_B2_DOWNLOAD_AUTH_DURATION
+\- Type:        Duration
+\- Default:     1w
+
+#### \-\-b2\-memory\-pool\-flush\-time
+
+How often internal memory buffer pools will be flushed.
+Uploads which requires additional buffers (f.e multipart) will use memory pool for allocations.
+This option controls how often unused buffers will be removed from the pool.
+
+\- Config:      memory_pool_flush_time
+\- Env Var:     RCLONE_B2_MEMORY_POOL_FLUSH_TIME
+\- Type:        Duration
+\- Default:     1m0s
+
+#### \-\-b2\-memory\-pool\-use\-mmap
+
+Whether to use mmap buffers in internal memory pool.
+
+\- Config:      memory_pool_use_mmap
+\- Env Var:     RCLONE_B2_MEMORY_POOL_USE_MMAP
+\- Type:        bool
+\- Default:     false
+
+#### \-\-b2\-encoding
+
 This sets the encoding for the backend.
-.PP
-See: the encoding section in the
-overview (https://rclone.org/overview/#encoding) for more info.
-.IP \[bu] 2
-Config: encoding
-.IP \[bu] 2
-Env Var: RCLONE_B2_ENCODING
-.IP \[bu] 2
-Type: MultiEncoder
-.IP \[bu] 2
-Default: Slash,BackSlash,Del,Ctl,InvalidUtf8,Dot
-.SS Box
-.PP
-Paths are specified as \f[C]remote:path\f[R]
-.PP
-Paths may be as deep as required, eg
-\f[C]remote:directory/subdirectory\f[R].
-.PP
+
+See: the [encoding section in the overview](https://rclone.org/overview/#encoding) for more info.
+
+\- Config:      encoding
+\- Env Var:     RCLONE_B2_ENCODING
+\- Type:        MultiEncoder
+\- Default:     Slash,BackSlash,Del,Ctl,InvalidUtf8,Dot
+
+
+
+ Box
+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
+
+Paths are specified as \[ga]remote:path\[ga]
+
+Paths may be as deep as required, eg \[ga]remote:directory/subdirectory\[ga].
+
 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.
-\f[C]rclone config\f[R] walks you through it.
-.PP
-Here is an example of how to make a remote called \f[C]remote\f[R].
-First run:
-.IP
-.nf
-\f[C]
- rclone config
-\f[R]
-.fi
-.PP
+to use JWT authentication.  \[ga]rclone config\[ga] walks you through it.
+
+Here is an example of how to make a remote called \[ga]remote\[ga].  First run:
+
+     rclone config
+
 This will guide you through an interactive setup process:
-.IP
-.nf
-\f[C]
-No remotes found \- make a new one
-n) New remote
-s) Set configuration password
-q) Quit config
-n/s/q> n
-name> remote
-Type of storage to configure.
-Choose a number from below, or type in your own value
-[snip]
-XX / Box
-   \[rs] \[dq]box\[dq]
-[snip]
-Storage> box
-Box App Client Id \- leave blank normally.
-client_id> 
-Box App Client Secret \- leave blank normally.
-client_secret>
-Box App config.json location
-Leave blank normally.
-Enter a string value. Press Enter for the default (\[dq]\[dq]).
-config_json>
-\[aq]enterprise\[aq] or \[aq]user\[aq] depending on the type of token being requested.
-Enter a string value. Press Enter for the default (\[dq]user\[dq]).
-box_sub_type>
-Remote config
-Use auto config?
- * Say Y if not sure
- * Say N if you are working on a remote or headless machine
-y) Yes
-n) No
-y/n> y
-If your browser doesn\[aq]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
-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
-[remote]
-client_id = 
-client_secret = 
-token = {\[dq]access_token\[dq]:\[dq]XXX\[dq],\[dq]token_type\[dq]:\[dq]bearer\[dq],\[dq]refresh_token\[dq]:\[dq]XXX\[dq],\[dq]expiry\[dq]:\[dq]XXX\[dq]}
-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
-y) Yes this is OK
-e) Edit this remote
-d) Delete this remote
-y/e/d> y
 \f[R]
 .fi
 .PP
-See the remote setup docs (https://rclone.org/remote_setup/) for how to
-set it up on a machine with no Internet browser available.
+No remotes found \- make a new one n) New remote s) Set configuration
+password q) Quit config n/s/q> n name> remote Type of storage to
+configure.
+Choose a number from below, or type in your own value [snip] XX / Box
+\ \[dq]box\[dq] [snip] Storage> box Box App Client Id \- leave blank
+normally.
+client_id> Box App Client Secret \- leave blank normally.
+client_secret> Box App config.json location Leave blank normally.
+Enter a string value.
+Press Enter for the default (\[dq]\[dq]).
+box_config_file> Box App Primary Access Token Leave blank normally.
+Enter a string value.
+Press Enter for the default (\[dq]\[dq]).
+access_token>
 .PP
+Enter a string value.
+Press Enter for the default (\[dq]user\[dq]).
+Choose a number from below, or type in your own value 1 / Rclone should
+act on behalf of a user \ \[dq]user\[dq] 2 / Rclone should act on behalf
+of a service account \ \[dq]enterprise\[dq] box_sub_type> Remote config
+Use auto config?
+* Say Y if not sure * Say N if you are working on a remote or headless
+machine y) Yes n) No y/n> y If your browser doesn\[aq]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 \-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\- [remote] client_id =
+client_secret = token =
+{\[dq]access_token\[dq]:\[dq]XXX\[dq],\[dq]token_type\[dq]:\[dq]bearer\[dq],\[dq]refresh_token\[dq]:\[dq]XXX\[dq],\[dq]expiry\[dq]:\[dq]XXX\[dq]}
+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\- y) Yes this is OK e) Edit this
+remote d) Delete this remote y/e/d> y
+.IP
+.nf
+\f[C]
+
+See the [remote setup docs](https://rclone.org/remote_setup/) for how to set it up on a
+machine with no Internet browser available.
+
 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 \f[C]http://127.0.0.1:53682/\f[R] and this it may require you
-to unblock it temporarily if you are running a host firewall.
-.PP
-Once configured you can then use \f[C]rclone\f[R] like this,
-.PP
+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 \[ga]http://127.0.0.1:53682/\[ga] and this it may require you to unblock
+it temporarily if you are running a host firewall.
+
+Once configured you can then use \[ga]rclone\[ga] like this,
+
 List directories in top level of your Box
-.IP
-.nf
-\f[C]
-rclone lsd remote:
-\f[R]
-.fi
-.PP
+
+    rclone lsd remote:
+
 List all the files in your Box
-.IP
-.nf
-\f[C]
-rclone ls remote:
-\f[R]
-.fi
-.PP
+
+    rclone ls remote:
+
 To copy a local directory to an Box directory called backup
-.IP
-.nf
-\f[C]
-rclone copy /home/source remote:backup
-\f[R]
-.fi
-.SS Using rclone with an Enterprise account with SSO
-.PP
-If you have an \[lq]Enterprise\[rq] 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,
-\[lq]Account\[rq] Tab, and then set the password in the
-\[lq]Authentication\[rq] field.
-.PP
-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.
-.SS Invalid refresh token
-.PP
-According to the box
-docs (https://developer.box.com/v2.0/docs/oauth-20#section-6-using-the-access-and-refresh-tokens):
-.RS
-.PP
-Each refresh_token is valid for one use in 60 days.
-.RE
-.PP
+
+    rclone copy /home/source remote:backup
+
+### Using rclone with an Enterprise account with SSO ###
+
+If you have an \[dq]Enterprise\[dq] 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, \[dq]Account\[dq]
+Tab, and then set the password in the \[dq]Authentication\[dq] field.
+
+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.
+
+### Invalid refresh token ###
+
+According to the [box docs](https://developer.box.com/v2.0/docs/oauth\-20#section\-6\-using\-the\-access\-and\-refresh\-tokens):
+
+> Each refresh_token is valid for one use in 60 days.
+
 This means that if you
-.IP \[bu] 2
-Don\[cq]t use the box remote for 60 days
-.IP \[bu] 2
-Copy the config file with a box refresh token in and use it in two
-places
-.IP \[bu] 2
-Get an error on a token refresh
-.PP
-then rclone will return an error which includes the text
-\f[C]Invalid refresh token\f[R].
-.PP
+
+  * Don\[aq]t use the box remote for 60 days
+  * Copy the config file with a box refresh token in and use it in two places
+  * Get an error on a token refresh
+
+then rclone will return an error which includes the text \[ga]Invalid
+refresh token\[ga].
+
 To fix this you will need to use oauth2 again to update the refresh
-token.
-You can use the methods in the remote setup
-docs (https://rclone.org/remote_setup/), 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.
-.PP
+token.  You can use the methods in [the remote setup
+docs](https://rclone.org/remote_setup/), 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.
+
 Here is how to do it.
+\f[R]
+.fi
+.PP
+$ rclone config Current remotes:
+.PP
+Name Type ==== ==== remote box
+.IP "e)" 3
+Edit existing remote
+.IP "f)" 3
+New remote
+.IP "g)" 3
+Delete remote
+.IP "h)" 3
+Rename remote
+.IP "i)" 3
+Copy remote
+.IP "j)" 3
+Set configuration password
+.IP "k)" 3
+Quit config e/n/d/r/c/s/q> e Choose a number from below, or type in an
+existing value 1 > remote remote> remote
+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\- [remote] type = box token =
+{\[dq]access_token\[dq]:\[dq]XXX\[dq],\[dq]token_type\[dq]:\[dq]bearer\[dq],\[dq]refresh_token\[dq]:\[dq]XXX\[dq],\[dq]expiry\[dq]:\[dq]2017\-07\-08T23:40:08.059167677+01:00\[dq]}
+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\- Edit remote Value
+\[dq]client_id\[dq] = \[dq]\[dq] Edit?
+(y/n)>
+.IP "l)" 3
+Yes
+.IP "m)" 3
+No y/n> n Value \[dq]client_secret\[dq] = \[dq]\[dq] Edit?
+(y/n)>
+.IP "n)" 3
+Yes
+.IP "o)" 3
+No y/n> n Remote config Already have a token \- refresh?
+.IP "p)" 3
+Yes
+.IP "q)" 3
+No y/n> y Use auto config?
+.IP \[bu] 2
+Say Y if not sure
+.IP \[bu] 2
+Say N if you are working on a remote or headless machine
+.IP "y)" 3
+Yes
+.IP "z)" 3
+No y/n> y If your browser doesn\[aq]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 \-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\- [remote] type = box
+token =
+{\[dq]access_token\[dq]:\[dq]YYY\[dq],\[dq]token_type\[dq]:\[dq]bearer\[dq],\[dq]refresh_token\[dq]:\[dq]YYY\[dq],\[dq]expiry\[dq]:\[dq]2017\-07\-23T12:22:29.259137901+01:00\[dq]}
+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
+.IP "a)" 3
+Yes this is OK
+.IP "b)" 3
+Edit this remote
+.IP "c)" 3
+Delete this remote y/e/d> y
 .IP
 .nf
 \f[C]
-$ rclone config
-Current remotes:
 
-Name                 Type
-====                 ====
-remote               box
+### Modified time and hashes ###
 
-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> e
-Choose a number from below, or type in an existing value
- 1 > remote
-remote> remote
-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
-[remote]
-type = box
-token = {\[dq]access_token\[dq]:\[dq]XXX\[dq],\[dq]token_type\[dq]:\[dq]bearer\[dq],\[dq]refresh_token\[dq]:\[dq]XXX\[dq],\[dq]expiry\[dq]:\[dq]2017\-07\-08T23:40:08.059167677+01:00\[dq]}
-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
-Edit remote
-Value \[dq]client_id\[dq] = \[dq]\[dq]
-Edit? (y/n)>
-y) Yes
-n) No
-y/n> n
-Value \[dq]client_secret\[dq] = \[dq]\[dq]
-Edit? (y/n)>
-y) Yes
-n) No
-y/n> n
-Remote config
-Already have a token \- refresh?
-y) Yes
-n) No
-y/n> y
-Use auto config?
- * Say Y if not sure
- * Say N if you are working on a remote or headless machine
-y) Yes
-n) No
-y/n> y
-If your browser doesn\[aq]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
-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
-[remote]
-type = box
-token = {\[dq]access_token\[dq]:\[dq]YYY\[dq],\[dq]token_type\[dq]:\[dq]bearer\[dq],\[dq]refresh_token\[dq]:\[dq]YYY\[dq],\[dq]expiry\[dq]:\[dq]2017\-07\-23T12:22:29.259137901+01:00\[dq]}
-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
-y) Yes this is OK
-e) Edit this remote
-d) Delete this remote
-y/e/d> y
-\f[R]
-.fi
-.SS Modified time and hashes
-.PP
-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.
-.PP
-Box supports SHA1 type hashes, so you can use the \f[C]\-\-checksum\f[R]
+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.
+
+Box supports SHA1 type hashes, so you can use the \[ga]\-\-checksum\[ga]
 flag.
-.SS Restricted filename characters
-.PP
-In addition to the default restricted characters
-set (https://rclone.org/overview/#restricted-characters) the following
-characters are also replaced:
-.PP
-.TS
-tab(@);
-l c c.
-T{
-Character
-T}@T{
-Value
-T}@T{
-Replacement
-T}
-_
-T{
-\[rs]
-T}@T{
-0x5C
-T}@T{
-\[uFF3C]
-T}
-.TE
-.PP
+
+#### Restricted filename characters
+
+In addition to the [default restricted characters set](https://rclone.org/overview/#restricted\-characters)
+the following characters are also replaced:
+
+| Character | Value | Replacement |
+| \-\-\-\-\-\-\-\-\- |:\-\-\-\-\-:|:\-\-\-\-\-\-\-\-\-\-\-:|
+| \[rs]         | 0x5C  | \[uFF3C]           |
+
 File names can also not end with the following characters.
 These only get replaced if they are the last character in the name:
-.PP
-.TS
-tab(@);
-l c c.
-T{
-Character
-T}@T{
-Value
-T}@T{
-Replacement
-T}
-_
-T{
-SP
-T}@T{
-0x20
-T}@T{
-\[u2420]
-T}
-.TE
-.PP
-Invalid UTF\-8 bytes will also be
-replaced (https://rclone.org/overview/#invalid-utf8), as they can\[cq]t
-be used in JSON strings.
-.SS Transfers
-.PP
-For files above 50MB rclone will use a chunked transfer.
-Rclone will upload up to \f[C]\-\-transfers\f[R] chunks at the same time
-(shared among all the multipart uploads).
-Chunks are buffered in memory and are normally 8MB so increasing
-\f[C]\-\-transfers\f[R] will increase memory use.
-.SS Deleting files
-.PP
-Depending on the enterprise settings for your user, the item will either
-be actually deleted from Box or moved to the trash.
-.SS Root folder ID
-.PP
-You can set the \f[C]root_folder_id\f[R] for rclone.
-This is the directory (identified by its \f[C]Folder ID\f[R]) that
-rclone considers to be the root of your Box drive.
-.PP
-Normally you will leave this blank and rclone will determine the correct
-root to use itself.
-.PP
+
+| Character | Value | Replacement |
+| \-\-\-\-\-\-\-\-\- |:\-\-\-\-\-:|:\-\-\-\-\-\-\-\-\-\-\-:|
+| SP        | 0x20  | \[u2420]           |
+
+Invalid UTF\-8 bytes will also be [replaced](https://rclone.org/overview/#invalid\-utf8),
+as they can\[aq]t be used in JSON strings.
+
+### Transfers ###
+
+For files above 50MB rclone will use a chunked transfer.  Rclone will
+upload up to \[ga]\-\-transfers\[ga] chunks at the same time (shared among all
+the multipart uploads).  Chunks are buffered in memory and are
+normally 8MB so increasing \[ga]\-\-transfers\[ga] will increase memory use.
+
+### Deleting files ###
+
+Depending on the enterprise settings for your user, the item will
+either be actually deleted from Box or moved to the trash.
+
+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.
+
+### Root folder ID ###
+
+You can set the \[ga]root_folder_id\[ga] for rclone.  This is the directory
+(identified by its \[ga]Folder ID\[ga]) that rclone considers to be the root
+of your Box drive.
+
+Normally you will leave this blank and rclone will determine the
+correct root to use itself.
+
 However you can set this to restrict rclone to a specific folder
 hierarchy.
-.PP
-In order to do this you will have to find the \f[C]Folder ID\f[R] 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.
-.PP
+
+In order to do this you will have to find the \[ga]Folder ID\[ga] 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.
+
 So if the folder you want rclone to use has a URL which looks like
-\f[C]https://app.box.com/folder/11xxxxxxxxx8\f[R] in the browser, then
-you use \f[C]11xxxxxxxxx8\f[R] as the \f[C]root_folder_id\f[R] in the
-config.
-.SS Standard Options
-.PP
+\[ga]https://app.box.com/folder/11xxxxxxxxx8\[ga]
+in the browser, then you use \[ga]11xxxxxxxxx8\[ga] as
+the \[ga]root_folder_id\[ga] in the config.
+
+
+### Standard Options
+
 Here are the standard options specific to box (Box).
-.SS \[en]box\-client\-id
-.PP
-Box App Client Id.
+
+#### \-\-box\-client\-id
+
+OAuth Client Id
 Leave blank normally.
-.IP \[bu] 2
-Config: client_id
-.IP \[bu] 2
-Env Var: RCLONE_BOX_CLIENT_ID
-.IP \[bu] 2
-Type: string
-.IP \[bu] 2
-Default: \[dq]\[dq]
-.SS \[en]box\-client\-secret
-.PP
-Box App Client Secret Leave blank normally.
-.IP \[bu] 2
-Config: client_secret
-.IP \[bu] 2
-Env Var: RCLONE_BOX_CLIENT_SECRET
-.IP \[bu] 2
-Type: string
-.IP \[bu] 2
-Default: \[dq]\[dq]
-.SS \[en]box\-box\-config\-file
-.PP
-Box App config.json location Leave blank normally.
-.IP \[bu] 2
-Config: box_config_file
-.IP \[bu] 2
-Env Var: RCLONE_BOX_BOX_CONFIG_FILE
-.IP \[bu] 2
-Type: string
-.IP \[bu] 2
-Default: \[dq]\[dq]
-.SS \[en]box\-box\-sub\-type
-.IP \[bu] 2
-Config: box_sub_type
-.IP \[bu] 2
-Env Var: RCLONE_BOX_BOX_SUB_TYPE
-.IP \[bu] 2
-Type: string
-.IP \[bu] 2
-Default: \[lq]user\[rq]
-.IP \[bu] 2
-Examples:
-.RS 2
-.IP \[bu] 2
-\[lq]user\[rq]
-.RS 2
-.IP \[bu] 2
-Rclone should act on behalf of a user
-.RE
-.IP \[bu] 2
-\[lq]enterprise\[rq]
-.RS 2
-.IP \[bu] 2
-Rclone should act on behalf of a service account
-.RE
-.RE
-.SS Advanced Options
-.PP
+
+\- Config:      client_id
+\- Env Var:     RCLONE_BOX_CLIENT_ID
+\- Type:        string
+\- Default:     \[dq]\[dq]
+
+#### \-\-box\-client\-secret
+
+OAuth Client Secret
+Leave blank normally.
+
+\- Config:      client_secret
+\- Env Var:     RCLONE_BOX_CLIENT_SECRET
+\- Type:        string
+\- Default:     \[dq]\[dq]
+
+#### \-\-box\-box\-config\-file
+
+Box App config.json location
+Leave blank normally.
+
+Leading \[ga]\[ti]\[ga] will be expanded in the file name as will environment variables such as \[ga]${RCLONE_CONFIG_DIR}\[ga].
+
+
+\- Config:      box_config_file
+\- Env Var:     RCLONE_BOX_BOX_CONFIG_FILE
+\- Type:        string
+\- Default:     \[dq]\[dq]
+
+#### \-\-box\-access\-token
+
+Box App Primary Access Token
+Leave blank normally.
+
+\- Config:      access_token
+\- Env Var:     RCLONE_BOX_ACCESS_TOKEN
+\- Type:        string
+\- Default:     \[dq]\[dq]
+
+#### \-\-box\-box\-sub\-type
+
+
+
+\- Config:      box_sub_type
+\- Env Var:     RCLONE_BOX_BOX_SUB_TYPE
+\- Type:        string
+\- Default:     \[dq]user\[dq]
+\- Examples:
+    \- \[dq]user\[dq]
+        \- Rclone should act on behalf of a user
+    \- \[dq]enterprise\[dq]
+        \- Rclone should act on behalf of a service account
+
+### Advanced Options
+
 Here are the advanced options specific to box (Box).
-.SS \[en]box\-root\-folder\-id
-.PP
+
+#### \-\-box\-token
+
+OAuth Access Token as a JSON blob.
+
+\- Config:      token
+\- Env Var:     RCLONE_BOX_TOKEN
+\- Type:        string
+\- Default:     \[dq]\[dq]
+
+#### \-\-box\-auth\-url
+
+Auth server URL.
+Leave blank to use the provider defaults.
+
+\- Config:      auth_url
+\- Env Var:     RCLONE_BOX_AUTH_URL
+\- Type:        string
+\- Default:     \[dq]\[dq]
+
+#### \-\-box\-token\-url
+
+Token server url.
+Leave blank to use the provider defaults.
+
+\- Config:      token_url
+\- Env Var:     RCLONE_BOX_TOKEN_URL
+\- Type:        string
+\- Default:     \[dq]\[dq]
+
+#### \-\-box\-root\-folder\-id
+
 Fill in for rclone to use a non root folder as its starting point.
-.IP \[bu] 2
-Config: root_folder_id
-.IP \[bu] 2
-Env Var: RCLONE_BOX_ROOT_FOLDER_ID
-.IP \[bu] 2
-Type: string
-.IP \[bu] 2
-Default: \[lq]0\[rq]
-.SS \[en]box\-upload\-cutoff
-.PP
+
+\- Config:      root_folder_id
+\- Env Var:     RCLONE_BOX_ROOT_FOLDER_ID
+\- Type:        string
+\- Default:     \[dq]0\[dq]
+
+#### \-\-box\-upload\-cutoff
+
 Cutoff for switching to multipart upload (>= 50MB).
-.IP \[bu] 2
-Config: upload_cutoff
-.IP \[bu] 2
-Env Var: RCLONE_BOX_UPLOAD_CUTOFF
-.IP \[bu] 2
-Type: SizeSuffix
-.IP \[bu] 2
-Default: 50M
-.SS \[en]box\-commit\-retries
-.PP
+
+\- Config:      upload_cutoff
+\- Env Var:     RCLONE_BOX_UPLOAD_CUTOFF
+\- Type:        SizeSuffix
+\- Default:     50M
+
+#### \-\-box\-commit\-retries
+
 Max number of times to try committing a multipart file.
-.IP \[bu] 2
-Config: commit_retries
-.IP \[bu] 2
-Env Var: RCLONE_BOX_COMMIT_RETRIES
-.IP \[bu] 2
-Type: int
-.IP \[bu] 2
-Default: 100
-.SS \[en]box\-encoding
-.PP
+
+\- Config:      commit_retries
+\- Env Var:     RCLONE_BOX_COMMIT_RETRIES
+\- Type:        int
+\- Default:     100
+
+#### \-\-box\-encoding
+
 This sets the encoding for the backend.
-.PP
-See: the encoding section in the
-overview (https://rclone.org/overview/#encoding) for more info.
-.IP \[bu] 2
-Config: encoding
-.IP \[bu] 2
-Env Var: RCLONE_BOX_ENCODING
-.IP \[bu] 2
-Type: MultiEncoder
-.IP \[bu] 2
-Default: Slash,BackSlash,Del,Ctl,RightSpace,InvalidUtf8,Dot
-.SS Limitations
-.PP
-Note that Box is case insensitive so you can\[cq]t have a file called
-\[lq]Hello.doc\[rq] and one called \[lq]hello.doc\[rq].
-.PP
-Box file names can\[cq]t have the \f[C]\[rs]\f[R] character in.
-rclone maps this to and from an identical looking unicode equivalent
-\f[C]\[uFF3C]\f[R].
-.PP
+
+See: the [encoding section in the overview](https://rclone.org/overview/#encoding) for more info.
+
+\- Config:      encoding
+\- Env Var:     RCLONE_BOX_ENCODING
+\- Type:        MultiEncoder
+\- Default:     Slash,BackSlash,Del,Ctl,RightSpace,InvalidUtf8,Dot
+
+
+
+### Limitations ###
+
+Note that Box is case insensitive so you can\[aq]t have a file called
+\[dq]Hello.doc\[dq] and one called \[dq]hello.doc\[dq].
+
+Box file names can\[aq]t have the \[ga]\[rs]\[ga] character in.  rclone maps this to
+and from an identical looking unicode equivalent \[ga]\[uFF3C]\[ga].
+
 Box only supports filenames up to 255 characters in length.
-.SS Cache (BETA)
-.PP
-The \f[C]cache\f[R] remote wraps another existing remote and stores file
-structure and its data for long running tasks like
-\f[C]rclone mount\f[R].
-.SS Status
-.PP
-The cache backend code is working but it currently doesn\[cq]t have a
-maintainer so there are outstanding
-bugs (https://github.com/rclone/rclone/issues?q=is%3Aopen+is%3Aissue+label%3Abug+label%3A%22Remote%3A+Cache%22)
-which aren\[cq]t getting fixed.
-.PP
+
+ Cache (BETA)
+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
+
+The \[ga]cache\[ga] remote wraps another existing remote and stores file structure
+and its data for long running tasks like \[ga]rclone mount\[ga].
+
+## Status
+
+The cache backend code is working but it currently doesn\[aq]t
+have a maintainer so there are [outstanding bugs](https://github.com/rclone/rclone/issues?q=is%3Aopen+is%3Aissue+label%3Abug+label%3A%22Remote%3A+Cache%22) which aren\[aq]t getting fixed.
+
 The cache backend is due to be phased out in favour of the VFS caching
 layer eventually which is more tightly integrated into rclone.
-.PP
-Until this happens we recommend only using the cache backend if you find
-you can\[cq]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\[cq]t needed in those scenarios any more.
-.SS Setup
-.PP
-To get started you just need to have an existing remote which can be
-configured with \f[C]cache\f[R].
-.PP
-Here is an example of how to make a remote called \f[C]test\-cache\f[R].
-First run:
-.IP
-.nf
-\f[C]
- rclone config
+
+Until this happens we recommend only using the cache backend if you
+find you can\[aq]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\[aq]t needed in those
+scenarios any more.
+
+## Setup
+
+To get started you just need to have an existing remote which can be configured
+with \[ga]cache\[ga].
+
+Here is an example of how to make a remote called \[ga]test\-cache\[ga].  First run:
+
+     rclone config
+
+This will guide you through an interactive setup process:
 \f[R]
 .fi
 .PP
-This will guide you through an interactive setup process:
+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> n
+name> test\-cache Type of storage to configure.
+Choose a number from below, or type in your own value [snip] XX / Cache
+a remote \ \[dq]cache\[dq] [snip] Storage> cache Remote to cache.
+Normally should contain a \[aq]:\[aq] and a path, eg
+\[dq]myremote:path/to/dir\[dq], \[dq]myremote:bucket\[dq] or maybe
+\[dq]myremote:\[dq] (not recommended).
+remote> local:/test Optional: The URL of the Plex server plex_url>
+http://127.0.0.1:32400 Optional: The username of the Plex user
+plex_username> 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> 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 /
+1MB \ \[dq]1m\[dq] 2 / 5 MB \ \[dq]5M\[dq] 3 / 10 MB \ \[dq]10M\[dq]
+chunk_size> 2 How much time should object info (file size, file hashes
+etc) be stored in cache.
+Use a very high value if you don\[aq]t plan on changing the source FS
+from outside the cache.
+Accepted units are: \[dq]s\[dq], \[dq]m\[dq], \[dq]h\[dq].
+Default: 5m Choose a number from below, or type in your own value 1 / 1
+hour \ \[dq]1h\[dq] 2 / 24 hours \ \[dq]24h\[dq] 3 / 24 hours
+\ \[dq]48h\[dq] info_age> 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 MB \ \[dq]500M\[dq] 2 / 1 GB \ \[dq]1G\[dq] 3 / 10 GB
+\ \[dq]10G\[dq] chunk_total_size> 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
 .IP
 .nf
 \f[C]
-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> n
-name> test\-cache
-Type of storage to configure.
-Choose a number from below, or type in your own value
-[snip]
-XX / Cache a remote
-   \[rs] \[dq]cache\[dq]
-[snip]
-Storage> cache
+
+You can then use it like this,
+
+List directories in top level of your drive
+
+    rclone lsd test\-cache:
+
+List all the files in your drive
+
+    rclone ls test\-cache:
+
+To start a cached mount
+
+    rclone mount \-\-allow\-other test\-cache: /var/tmp/test\-cache
+
+### Write Features ###
+
+### Offline uploading ###
+
+In an effort to make writing through cache more reliable, the backend 
+now supports this feature which can be activated by specifying a
+\[ga]cache\-tmp\-upload\-path\[ga].
+
+A files goes through these states when using this feature:
+
+1. An upload is started (usually by copying a file on the cache remote)
+2. 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)
+3. After \[ga]cache\-tmp\-wait\-time\[ga] passes and the file is next in line, \[ga]rclone move\[ga] 
+is used to move the file to the cloud provider
+4. Reading the file still works during the upload but most modifications on it will be prohibited
+5. Once the move is complete the file is unlocked for modifications as it
+becomes as any other regular file
+6. If the file is being read through \[ga]cache\[ga] when it\[aq]s actually
+deleted from the temporary path then \[ga]cache\[ga] will simply swap the source
+to the cloud provider without interrupting the reading (small blip can happen though)
+
+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 \[ga]\-\-cache\-db\-purge\[ga] flag.
+
+### Write Support ###
+
+Writes are supported through \[ga]cache\[ga].
+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 \[ga]Offline uploading\[ga] for reliable writes.
+
+One special case is covered with \[ga]cache\-writes\[ga] 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.
+
+### Read Features ###
+
+#### Multiple connections ####
+
+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.
+
+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.
+
+#### Plex Integration ####
+
+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.
+
+Scans will have a minimum amount of workers (1) while in a confirmed playback cache
+will deploy the configured number of workers.
+
+This integration opens the doorway to additional performance improvements
+which will be explored in the near future.
+
+**Note:** If Plex options are not configured, \[ga]cache\[ga] will function with its
+configured options without adapting any of its settings.
+
+How to enable? Run \[ga]rclone config\[ga] and add all the Plex options (endpoint, username
+and password) in your remote and it will be automatically enabled.
+
+Affected settings:
+\- \[ga]cache\-workers\[ga]: _Configured value_ during confirmed playback or _1_ all the other times
+
+##### Certificate Validation #####
+
+When the Plex server is configured to only accept secure connections, it is
+possible to use \[ga].plex.direct\[ga] URLs to ensure certificate validation succeeds.
+These URLs are used by Plex internally to connect to the Plex server securely.
+
+The format for these URLs is the following:
+
+https://ip\-with\-dots\-replaced.server\-hash.plex.direct:32400/
+
+The \[ga]ip\-with\-dots\-replaced\[ga] part can be any IPv4 address, where the dots
+have been replaced with dashes, e.g. \[ga]127.0.0.1\[ga] becomes \[ga]127\-0\-0\-1\[ga].
+
+To get the \[ga]server\-hash\[ga] part, the easiest way is to visit
+
+https://plex.tv/api/resources?includeHttps=1&X\-Plex\-Token=your\-plex\-token
+
+This page will list all the available Plex servers for your account
+with at least one \[ga].plex.direct\[ga] link for each. Copy one URL and replace
+the IP address with the desired address. This can be used as the
+\[ga]plex_url\[ga] value.
+
+### Known issues ###
+
+#### Mount and \-\-dir\-cache\-time ####
+
+\-\-dir\-cache\-time controls the first layer of directory caching which works at the mount layer.
+Being an independent caching mechanism from the \[ga]cache\[ga] backend, it will manage its own entries
+based on the configured time.
+
+To avoid getting in a scenario where dir cache has obsolete data and cache would have the correct
+one, try to set \[ga]\-\-dir\-cache\-time\[ga] to a lower time than \[ga]\-\-cache\-info\-age\[ga]. Default values are
+already configured in this way. 
+
+#### Windows support \- Experimental ####
+
+There are a couple of issues with Windows \[ga]mount\[ga] functionality that still require some investigations.
+It should be considered as experimental thus far as fixes come in for this OS.
+
+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.
+
+Any reports or feedback on how cache behaves on this OS is greatly appreciated.
+ 
+\- https://github.com/rclone/rclone/issues/1935
+\- https://github.com/rclone/rclone/issues/1907
+\- https://github.com/rclone/rclone/issues/1834 
+
+#### Risk of throttling ####
+
+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. 
+
+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.
+
+Some recommendations:
+\- don\[aq]t use a very small interval for entry information (\[ga]\-\-cache\-info\-age\[ga])
+\- while writes aren\[aq]t yet optimised, you can still write through \[ga]cache\[ga] which gives you the advantage
+of adding the file in the cache at the same time if configured to do so.
+
+Future enhancements:
+
+\- https://github.com/rclone/rclone/issues/1937
+\- https://github.com/rclone/rclone/issues/1936 
+
+#### cache and crypt ####
+
+One common scenario is to keep your data encrypted in the cloud provider
+using the \[ga]crypt\[ga] remote. \[ga]crypt\[ga] uses a similar technique to wrap around
+an existing remote and handles this translation in a seamless way.
+
+There is an issue with wrapping the remotes in this order:
+**cloud remote** \-> **crypt** \-> **cache**
+
+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\[aq]re downloading the full file instead of small chunks.
+Organizing the remotes in this order yields better results:
+**cloud remote** \-> **cache** \-> **crypt**
+
+#### absolute remote paths ####
+
+\[ga]cache\[ga] can not differentiate between relative and absolute paths for the wrapped remote.
+Any path given in the \[ga]remote\[ga] 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 \[ga]/\[ga] character.
+
+This behavior is irrelevant for most backend types, but there are backends where a leading \[ga]/\[ga]
+changes the effective directory, e.g. in the \[ga]sftp\[ga] backend paths starting with a \[ga]/\[ga] are
+relative to the root of the SSH server and paths without are relative to the user home directory.
+As a result \[ga]sftp:bin\[ga] and \[ga]sftp:/bin\[ga] will share the same cache folder, even if they represent
+a different directory on the SSH server.
+
+### Cache and Remote Control (\-\-rc) ###
+Cache supports the new \[ga]\-\-rc\[ga] 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.
+
+### rc cache/expire
+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.
+
+Params:
+  \- **remote** = path to remote **(required)**
+  \- **withData** = true/false to delete cached data (chunks) as well _(optional, false by default)_
+
+
+### Standard Options
+
+Here are the standard options specific to cache (Cache a remote).
+
+#### \-\-cache\-remote
+
 Remote to cache.
 Normally should contain a \[aq]:\[aq] and a path, eg \[dq]myremote:path/to/dir\[dq],
 \[dq]myremote:bucket\[dq] or maybe \[dq]myremote:\[dq] (not recommended).
-remote> local:/test
-Optional: The URL of the Plex server
-plex_url> http://127.0.0.1:32400
-Optional: The username of the Plex user
-plex_username> 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> 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 / 1MB
-   \[rs] \[dq]1m\[dq]
- 2 / 5 MB
-   \[rs] \[dq]5M\[dq]
- 3 / 10 MB
-   \[rs] \[dq]10M\[dq]
-chunk_size> 2
-How much time should object info (file size, file hashes etc) be stored in cache. Use a very high value if you don\[aq]t plan on changing the source FS from outside the cache.
-Accepted units are: \[dq]s\[dq], \[dq]m\[dq], \[dq]h\[dq].
-Default: 5m
-Choose a number from below, or type in your own value
- 1 / 1 hour
-   \[rs] \[dq]1h\[dq]
- 2 / 24 hours
-   \[rs] \[dq]24h\[dq]
- 3 / 24 hours
-   \[rs] \[dq]48h\[dq]
-info_age> 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 MB
-   \[rs] \[dq]500M\[dq]
- 2 / 1 GB
-   \[rs] \[dq]1G\[dq]
- 3 / 10 GB
-   \[rs] \[dq]10G\[dq]
-chunk_total_size> 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
-\f[R]
-.fi
-.PP
-You can then use it like this,
-.PP
-List directories in top level of your drive
-.IP
-.nf
-\f[C]
-rclone lsd test\-cache:
-\f[R]
-.fi
-.PP
-List all the files in your drive
-.IP
-.nf
-\f[C]
-rclone ls test\-cache:
-\f[R]
-.fi
-.PP
-To start a cached mount
-.IP
-.nf
-\f[C]
-rclone mount \-\-allow\-other test\-cache: /var/tmp/test\-cache
-\f[R]
-.fi
-.SS Write Features
-.SS Offline uploading
-.PP
-In an effort to make writing through cache more reliable, the backend
-now supports this feature which can be activated by specifying a
-\f[C]cache\-tmp\-upload\-path\f[R].
-.PP
-A files goes through these states when using this feature:
-.IP "1." 3
-An upload is started (usually by copying a file on the cache remote)
-.IP "2." 3
-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)
-.IP "3." 3
-After \f[C]cache\-tmp\-wait\-time\f[R] passes and the file is next in
-line, \f[C]rclone move\f[R] is used to move the file to the cloud
-provider
-.IP "4." 3
-Reading the file still works during the upload but most modifications on
-it will be prohibited
-.IP "5." 3
-Once the move is complete the file is unlocked for modifications as it
-becomes as any other regular file
-.IP "6." 3
-If the file is being read through \f[C]cache\f[R] when it\[cq]s actually
-deleted from the temporary path then \f[C]cache\f[R] will simply swap
-the source to the cloud provider without interrupting the reading (small
-blip can happen though)
-.PP
-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 \f[C]\-\-cache\-db\-purge\f[R] flag.
-.SS Write Support
-.PP
-Writes are supported through \f[C]cache\f[R].
-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 \f[C]Offline uploading\f[R] for reliable writes.
-.PP
-One special case is covered with \f[C]cache\-writes\f[R] 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.
-.SS Read Features
-.SS Multiple connections
-.PP
-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.
-.PP
-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.
-.SS Plex Integration
-.PP
-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.
-.PP
-Scans will have a minimum amount of workers (1) while in a confirmed
-playback cache will deploy the configured number of workers.
-.PP
-This integration opens the doorway to additional performance
-improvements which will be explored in the near future.
-.PP
-\f[B]Note:\f[R] If Plex options are not configured, \f[C]cache\f[R] will
-function with its configured options without adapting any of its
-settings.
-.PP
-How to enable?
-Run \f[C]rclone config\f[R] and add all the Plex options (endpoint,
-username and password) in your remote and it will be automatically
-enabled.
-.PP
-Affected settings: \- \f[C]cache\-workers\f[R]: \f[I]Configured
-value\f[R] during confirmed playback or \f[I]1\f[R] all the other times
-.SS Certificate Validation
-.PP
-When the Plex server is configured to only accept secure connections, it
-is possible to use \f[C].plex.direct\f[R] URLs to ensure certificate
-validation succeeds.
-These URLs are used by Plex internally to connect to the Plex server
-securely.
-.PP
-The format for these URLs is the following:
-.PP
-https://ip\-with\-dots\-replaced.server\-hash.plex.direct:32400/
-.PP
-The \f[C]ip\-with\-dots\-replaced\f[R] part can be any IPv4 address,
-where the dots have been replaced with dashes, e.g.\ \f[C]127.0.0.1\f[R]
-becomes \f[C]127\-0\-0\-1\f[R].
-.PP
-To get the \f[C]server\-hash\f[R] part, the easiest way is to visit
-.PP
-https://plex.tv/api/resources?includeHttps=1&X\-Plex\-Token=your\-plex\-token
-.PP
-This page will list all the available Plex servers for your account with
-at least one \f[C].plex.direct\f[R] link for each.
-Copy one URL and replace the IP address with the desired address.
-This can be used as the \f[C]plex_url\f[R] value.
-.SS Known issues
-.SS Mount and \[en]dir\-cache\-time
-.PP
-\[en]dir\-cache\-time controls the first layer of directory caching
-which works at the mount layer.
-Being an independent caching mechanism from the \f[C]cache\f[R] backend,
-it will manage its own entries based on the configured time.
-.PP
-To avoid getting in a scenario where dir cache has obsolete data and
-cache would have the correct one, try to set
-\f[C]\-\-dir\-cache\-time\f[R] to a lower time than
-\f[C]\-\-cache\-info\-age\f[R].
-Default values are already configured in this way.
-.SS Windows support \- Experimental
-.PP
-There are a couple of issues with Windows \f[C]mount\f[R] functionality
-that still require some investigations.
-It should be considered as experimental thus far as fixes come in for
-this OS.
-.PP
-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.
-.PP
-Any reports or feedback on how cache behaves on this OS is greatly
-appreciated.
-.IP \[bu] 2
-https://github.com/rclone/rclone/issues/1935
-.IP \[bu] 2
-https://github.com/rclone/rclone/issues/1907
-.IP \[bu] 2
-https://github.com/rclone/rclone/issues/1834
-.SS Risk of throttling
-.PP
-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.
-.PP
-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.
-.PP
-Some recommendations: \- don\[cq]t use a very small interval for entry
-information (\f[C]\-\-cache\-info\-age\f[R]) \- while writes aren\[cq]t
-yet optimised, you can still write through \f[C]cache\f[R] which gives
-you the advantage of adding the file in the cache at the same time if
-configured to do so.
-.PP
-Future enhancements:
-.IP \[bu] 2
-https://github.com/rclone/rclone/issues/1937
-.IP \[bu] 2
-https://github.com/rclone/rclone/issues/1936
-.SS cache and crypt
-.PP
-One common scenario is to keep your data encrypted in the cloud provider
-using the \f[C]crypt\f[R] remote.
-\f[C]crypt\f[R] uses a similar technique to wrap around an existing
-remote and handles this translation in a seamless way.
-.PP
-There is an issue with wrapping the remotes in this order: \f[B]cloud
-remote\f[R] \-> \f[B]crypt\f[R] \-> \f[B]cache\f[R]
-.PP
-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\[cq]re downloading the full file
-instead of small chunks.
-Organizing the remotes in this order yields better results: \f[B]cloud
-remote\f[R] \-> \f[B]cache\f[R] \-> \f[B]crypt\f[R]
-.SS absolute remote paths
-.PP
-\f[C]cache\f[R] can not differentiate between relative and absolute
-paths for the wrapped remote.
-Any path given in the \f[C]remote\f[R] 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
-\f[C]/\f[R] character.
-.PP
-This behavior is irrelevant for most backend types, but there are
-backends where a leading \f[C]/\f[R] changes the effective directory,
-e.g.\ in the \f[C]sftp\f[R] backend paths starting with a \f[C]/\f[R]
-are relative to the root of the SSH server and paths without are
-relative to the user home directory.
-As a result \f[C]sftp:bin\f[R] and \f[C]sftp:/bin\f[R] will share the
-same cache folder, even if they represent a different directory on the
-SSH server.
-.SS Cache and Remote Control (\[en]rc)
-.PP
-Cache supports the new \f[C]\-\-rc\f[R] 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.
-.SS rc cache/expire
-.PP
-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.
-.PP
-Params: \- \f[B]remote\f[R] = path to remote \f[B](required)\f[R] \-
-\f[B]withData\f[R] = true/false to delete cached data (chunks) as well
-\f[I](optional, false by default)\f[R]
-.SS Standard Options
-.PP
-Here are the standard options specific to cache (Cache a remote).
-.SS \[en]cache\-remote
-.PP
-Remote to cache.
-Normally should contain a `:' and a path, eg
-\[lq]myremote:path/to/dir\[rq], \[lq]myremote:bucket\[rq] or maybe
-\[lq]myremote:\[rq] (not recommended).
-.IP \[bu] 2
-Config: remote
-.IP \[bu] 2
-Env Var: RCLONE_CACHE_REMOTE
-.IP \[bu] 2
-Type: string
-.IP \[bu] 2
-Default: \[dq]\[dq]
-.SS \[en]cache\-plex\-url
-.PP
+
+\- Config:      remote
+\- Env Var:     RCLONE_CACHE_REMOTE
+\- Type:        string
+\- Default:     \[dq]\[dq]
+
+#### \-\-cache\-plex\-url
+
 The URL of the Plex server
-.IP \[bu] 2
-Config: plex_url
-.IP \[bu] 2
-Env Var: RCLONE_CACHE_PLEX_URL
-.IP \[bu] 2
-Type: string
-.IP \[bu] 2
-Default: \[dq]\[dq]
-.SS \[en]cache\-plex\-username
-.PP
+
+\- Config:      plex_url
+\- Env Var:     RCLONE_CACHE_PLEX_URL
+\- Type:        string
+\- Default:     \[dq]\[dq]
+
+#### \-\-cache\-plex\-username
+
 The username of the Plex user
-.IP \[bu] 2
-Config: plex_username
-.IP \[bu] 2
-Env Var: RCLONE_CACHE_PLEX_USERNAME
-.IP \[bu] 2
-Type: string
-.IP \[bu] 2
-Default: \[dq]\[dq]
-.SS \[en]cache\-plex\-password
-.PP
+
+\- Config:      plex_username
+\- Env Var:     RCLONE_CACHE_PLEX_USERNAME
+\- Type:        string
+\- Default:     \[dq]\[dq]
+
+#### \-\-cache\-plex\-password
+
 The password of the Plex user
-.IP \[bu] 2
-Config: plex_password
-.IP \[bu] 2
-Env Var: RCLONE_CACHE_PLEX_PASSWORD
-.IP \[bu] 2
-Type: string
-.IP \[bu] 2
-Default: \[dq]\[dq]
-.SS \[en]cache\-chunk\-size
-.PP
+
+**NB** Input to this must be obscured \- see [rclone obscure](https://rclone.org/commands/rclone_obscure/).
+
+\- Config:      plex_password
+\- Env Var:     RCLONE_CACHE_PLEX_PASSWORD
+\- Type:        string
+\- Default:     \[dq]\[dq]
+
+#### \-\-cache\-chunk\-size
+
 The size of a chunk (partial file data).
-.PP
-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.
-.IP \[bu] 2
-Config: chunk_size
-.IP \[bu] 2
-Env Var: RCLONE_CACHE_CHUNK_SIZE
-.IP \[bu] 2
-Type: SizeSuffix
-.IP \[bu] 2
-Default: 5M
-.IP \[bu] 2
-Examples:
-.RS 2
-.IP \[bu] 2
-\[lq]1m\[rq]
-.RS 2
-.IP \[bu] 2
-1MB
-.RE
-.IP \[bu] 2
-\[lq]5M\[rq]
-.RS 2
-.IP \[bu] 2
-5 MB
-.RE
-.IP \[bu] 2
-\[lq]10M\[rq]
-.RS 2
-.IP \[bu] 2
-10 MB
-.RE
-.RE
-.SS \[en]cache\-info\-age
-.PP
-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.
-.IP \[bu] 2
-Config: info_age
-.IP \[bu] 2
-Env Var: RCLONE_CACHE_INFO_AGE
-.IP \[bu] 2
-Type: Duration
-.IP \[bu] 2
-Default: 6h0m0s
-.IP \[bu] 2
-Examples:
-.RS 2
-.IP \[bu] 2
-\[lq]1h\[rq]
-.RS 2
-.IP \[bu] 2
-1 hour
-.RE
-.IP \[bu] 2
-\[lq]24h\[rq]
-.RS 2
-.IP \[bu] 2
-24 hours
-.RE
-.IP \[bu] 2
-\[lq]48h\[rq]
-.RS 2
-.IP \[bu] 2
-48 hours
-.RE
-.RE
-.SS \[en]cache\-chunk\-total\-size
-.PP
+
+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.
+
+\- Config:      chunk_size
+\- Env Var:     RCLONE_CACHE_CHUNK_SIZE
+\- Type:        SizeSuffix
+\- Default:     5M
+\- Examples:
+    \- \[dq]1m\[dq]
+        \- 1MB
+    \- \[dq]5M\[dq]
+        \- 5 MB
+    \- \[dq]10M\[dq]
+        \- 10 MB
+
+#### \-\-cache\-info\-age
+
+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.
+
+\- Config:      info_age
+\- Env Var:     RCLONE_CACHE_INFO_AGE
+\- Type:        Duration
+\- Default:     6h0m0s
+\- Examples:
+    \- \[dq]1h\[dq]
+        \- 1 hour
+    \- \[dq]24h\[dq]
+        \- 24 hours
+    \- \[dq]48h\[dq]
+        \- 48 hours
+
+#### \-\-cache\-chunk\-total\-size
+
 The total size that the chunks can take up on the local disk.
-.PP
-If the cache exceeds this value then it will start to delete the oldest
-chunks until it goes under this value.
-.IP \[bu] 2
-Config: chunk_total_size
-.IP \[bu] 2
-Env Var: RCLONE_CACHE_CHUNK_TOTAL_SIZE
-.IP \[bu] 2
-Type: SizeSuffix
-.IP \[bu] 2
-Default: 10G
-.IP \[bu] 2
-Examples:
-.RS 2
-.IP \[bu] 2
-\[lq]500M\[rq]
-.RS 2
-.IP \[bu] 2
-500 MB
-.RE
-.IP \[bu] 2
-\[lq]1G\[rq]
-.RS 2
-.IP \[bu] 2
-1 GB
-.RE
-.IP \[bu] 2
-\[lq]10G\[rq]
-.RS 2
-.IP \[bu] 2
-10 GB
-.RE
-.RE
-.SS Advanced Options
-.PP
+
+If the cache exceeds this value then it will start to delete the
+oldest chunks until it goes under this value.
+
+\- Config:      chunk_total_size
+\- Env Var:     RCLONE_CACHE_CHUNK_TOTAL_SIZE
+\- Type:        SizeSuffix
+\- Default:     10G
+\- Examples:
+    \- \[dq]500M\[dq]
+        \- 500 MB
+    \- \[dq]1G\[dq]
+        \- 1 GB
+    \- \[dq]10G\[dq]
+        \- 10 GB
+
+### Advanced Options
+
 Here are the advanced options specific to cache (Cache a remote).
-.SS \[en]cache\-plex\-token
-.PP
+
+#### \-\-cache\-plex\-token
+
 The plex token for authentication \- auto set normally
-.IP \[bu] 2
-Config: plex_token
-.IP \[bu] 2
-Env Var: RCLONE_CACHE_PLEX_TOKEN
-.IP \[bu] 2
-Type: string
-.IP \[bu] 2
-Default: \[dq]\[dq]
-.SS \[en]cache\-plex\-insecure
-.PP
+
+\- Config:      plex_token
+\- Env Var:     RCLONE_CACHE_PLEX_TOKEN
+\- Type:        string
+\- Default:     \[dq]\[dq]
+
+#### \-\-cache\-plex\-insecure
+
 Skip all certificate verification when connecting to the Plex server
-.IP \[bu] 2
-Config: plex_insecure
-.IP \[bu] 2
-Env Var: RCLONE_CACHE_PLEX_INSECURE
-.IP \[bu] 2
-Type: string
-.IP \[bu] 2
-Default: \[dq]\[dq]
-.SS \[en]cache\-db\-path
-.PP
+
+\- Config:      plex_insecure
+\- Env Var:     RCLONE_CACHE_PLEX_INSECURE
+\- Type:        string
+\- Default:     \[dq]\[dq]
+
+#### \-\-cache\-db\-path
+
 Directory to store file structure metadata DB.
 The remote name is used as the DB file name.
-.IP \[bu] 2
-Config: db_path
-.IP \[bu] 2
-Env Var: RCLONE_CACHE_DB_PATH
-.IP \[bu] 2
-Type: string
-.IP \[bu] 2
-Default: \[lq]$HOME/.cache/rclone/cache\-backend\[rq]
-.SS \[en]cache\-chunk\-path
-.PP
+
+\- Config:      db_path
+\- Env Var:     RCLONE_CACHE_DB_PATH
+\- Type:        string
+\- Default:     \[dq]$HOME/.cache/rclone/cache\-backend\[dq]
+
+#### \-\-cache\-chunk\-path
+
 Directory to cache chunk files.
-.PP
-Path to where partial file data (chunks) are stored locally.
-The remote name is appended to the final path.
-.PP
-This config follows the \[lq]\[en]cache\-db\-path\[rq].
-If you specify a custom location for \[lq]\[en]cache\-db\-path\[rq] and
-don\[cq]t specify one for \[lq]\[en]cache\-chunk\-path\[rq] then
-\[lq]\[en]cache\-chunk\-path\[rq] will use the same path as
-\[lq]\[en]cache\-db\-path\[rq].
-.IP \[bu] 2
-Config: chunk_path
-.IP \[bu] 2
-Env Var: RCLONE_CACHE_CHUNK_PATH
-.IP \[bu] 2
-Type: string
-.IP \[bu] 2
-Default: \[lq]$HOME/.cache/rclone/cache\-backend\[rq]
-.SS \[en]cache\-db\-purge
-.PP
+
+Path to where partial file data (chunks) are stored locally. The remote
+name is appended to the final path.
+
+This config follows the \[dq]\-\-cache\-db\-path\[dq]. If you specify a custom
+location for \[dq]\-\-cache\-db\-path\[dq] and don\[aq]t specify one for \[dq]\-\-cache\-chunk\-path\[dq]
+then \[dq]\-\-cache\-chunk\-path\[dq] will use the same path as \[dq]\-\-cache\-db\-path\[dq].
+
+\- Config:      chunk_path
+\- Env Var:     RCLONE_CACHE_CHUNK_PATH
+\- Type:        string
+\- Default:     \[dq]$HOME/.cache/rclone/cache\-backend\[dq]
+
+#### \-\-cache\-db\-purge
+
 Clear all the cached data for this remote on start.
-.IP \[bu] 2
-Config: db_purge
-.IP \[bu] 2
-Env Var: RCLONE_CACHE_DB_PURGE
-.IP \[bu] 2
-Type: bool
-.IP \[bu] 2
-Default: false
-.SS \[en]cache\-chunk\-clean\-interval
-.PP
+
+\- Config:      db_purge
+\- Env Var:     RCLONE_CACHE_DB_PURGE
+\- Type:        bool
+\- Default:     false
+
+#### \-\-cache\-chunk\-clean\-interval
+
 How often should the cache perform cleanups of the chunk storage.
-The default value should be ok for most people.
-If you find that the cache goes over \[lq]cache\-chunk\-total\-size\[rq]
-too often then try to lower this value to force it to perform cleanups
-more often.
-.IP \[bu] 2
-Config: chunk_clean_interval
-.IP \[bu] 2
-Env Var: RCLONE_CACHE_CHUNK_CLEAN_INTERVAL
-.IP \[bu] 2
-Type: Duration
-.IP \[bu] 2
-Default: 1m0s
-.SS \[en]cache\-read\-retries
-.PP
+The default value should be ok for most people. If you find that the
+cache goes over \[dq]cache\-chunk\-total\-size\[dq] too often then try to lower
+this value to force it to perform cleanups more often.
+
+\- Config:      chunk_clean_interval
+\- Env Var:     RCLONE_CACHE_CHUNK_CLEAN_INTERVAL
+\- Type:        Duration
+\- Default:     1m0s
+
+#### \-\-cache\-read\-retries
+
 How many times to retry a read from a cache storage.
-.PP
+
 Since reading from a cache stream is independent from downloading file
-data, readers can get to a point where there\[cq]s no more data in the
-cache.
-Most of the times this can indicate a connectivity issue if cache
-isn\[cq]t able to provide file data anymore.
-.PP
-For really slow connections, increase this to a point where the stream
-is able to provide data but your experience will be very stuttering.
-.IP \[bu] 2
-Config: read_retries
-.IP \[bu] 2
-Env Var: RCLONE_CACHE_READ_RETRIES
-.IP \[bu] 2
-Type: int
-.IP \[bu] 2
-Default: 10
-.SS \[en]cache\-workers
-.PP
+data, readers can get to a point where there\[aq]s no more data in the
+cache.  Most of the times this can indicate a connectivity issue if
+cache isn\[aq]t able to provide file data anymore.
+
+For really slow connections, increase this to a point where the stream is
+able to provide data but your experience will be very stuttering.
+
+\- Config:      read_retries
+\- Env Var:     RCLONE_CACHE_READ_RETRIES
+\- Type:        int
+\- Default:     10
+
+#### \-\-cache\-workers
+
 How many workers should run in parallel to download chunks.
-.PP
-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.
-.PP
-\f[B]Note\f[R]: If the optional Plex integration is enabled then this
+
+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.
+
+**Note**: 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.
-.IP \[bu] 2
-Config: workers
-.IP \[bu] 2
-Env Var: RCLONE_CACHE_WORKERS
-.IP \[bu] 2
-Type: int
-.IP \[bu] 2
-Default: 4
-.SS \[en]cache\-chunk\-no\-memory
-.PP
+
+\- Config:      workers
+\- Env Var:     RCLONE_CACHE_WORKERS
+\- Type:        int
+\- Default:     4
+
+#### \-\-cache\-chunk\-no\-memory
+
 Disable the in\-memory cache for storing chunks during streaming.
-.PP
-By default, cache will keep file data during streaming in RAM as well to
-provide it to readers as fast as possible.
-.PP
+
+By default, cache will keep file data during streaming in RAM as well
+to provide it to readers as fast as possible.
+
 This transient data is evicted as soon as it is read and the number of
-chunks stored doesn\[cq]t exceed the number of workers.
-However, depending on other settings like \[lq]cache\-chunk\-size\[rq]
-and \[lq]cache\-workers\[rq] this footprint can increase if there are
-parallel streams too (multiple files being read at the same time).
-.PP
-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.
-.IP \[bu] 2
-Config: chunk_no_memory
-.IP \[bu] 2
-Env Var: RCLONE_CACHE_CHUNK_NO_MEMORY
-.IP \[bu] 2
-Type: bool
-.IP \[bu] 2
-Default: false
-.SS \[en]cache\-rps
-.PP
-Limits the number of requests per second to the source FS (\-1 to
-disable)
-.PP
+chunks stored doesn\[aq]t exceed the number of workers. However, depending
+on other settings like \[dq]cache\-chunk\-size\[dq] and \[dq]cache\-workers\[dq] this footprint
+can increase if there are parallel streams too (multiple files being read
+at the same time).
+
+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.
+
+\- Config:      chunk_no_memory
+\- Env Var:     RCLONE_CACHE_CHUNK_NO_MEMORY
+\- Type:        bool
+\- Default:     false
+
+#### \-\-cache\-rps
+
+Limits the number of requests per second to the source FS (\-1 to disable)
+
 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.
-.PP
-If you find that you\[cq]re getting banned or limited on the cloud
+that cache will be doing to the cloud provider remote and try to
+respect that value by setting waits between reads.
+
+If you find that you\[aq]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.
-.PP
+second will allow you to work with it then you can use this setting
+for that.
+
 A good balance of all the other settings should make this setting
 useless but it is available to set for more special cases.
-.PP
-\f[B]NOTE\f[R]: This will limit the number of requests during streams
-but other API calls to the cloud provider like directory listings will
+
+**NOTE**: This will limit the number of requests during streams but
+other API calls to the cloud provider like directory listings will
 still pass.
-.IP \[bu] 2
-Config: rps
-.IP \[bu] 2
-Env Var: RCLONE_CACHE_RPS
-.IP \[bu] 2
-Type: int
-.IP \[bu] 2
-Default: \-1
-.SS \[en]cache\-writes
-.PP
+
+\- Config:      rps
+\- Env Var:     RCLONE_CACHE_RPS
+\- Type:        int
+\- Default:     \-1
+
+#### \-\-cache\-writes
+
 Cache file data on writes through the FS
-.PP
+
 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.
-.IP \[bu] 2
-Config: writes
-.IP \[bu] 2
-Env Var: RCLONE_CACHE_WRITES
-.IP \[bu] 2
-Type: bool
-.IP \[bu] 2
-Default: false
-.SS \[en]cache\-tmp\-upload\-path
-.PP
+cache you can enable this flag to have their data stored in the
+cache store at the same time during upload.
+
+\- Config:      writes
+\- Env Var:     RCLONE_CACHE_WRITES
+\- Type:        bool
+\- Default:     false
+
+#### \-\-cache\-tmp\-upload\-path
+
 Directory to keep temporary files until they are uploaded.
-.PP
+
 This is the path where cache will use as a temporary storage for new
 files that need to be uploaded to the cloud provider.
-.PP
-Specifying a value will enable this feature.
-Without it, it is completely disabled and files will be uploaded
-directly to the cloud provider
-.IP \[bu] 2
-Config: tmp_upload_path
-.IP \[bu] 2
-Env Var: RCLONE_CACHE_TMP_UPLOAD_PATH
-.IP \[bu] 2
-Type: string
-.IP \[bu] 2
-Default: \[dq]\[dq]
-.SS \[en]cache\-tmp\-wait\-time
-.PP
+
+Specifying a value will enable this feature. Without it, it is
+completely disabled and files will be uploaded directly to the cloud
+provider
+
+\- Config:      tmp_upload_path
+\- Env Var:     RCLONE_CACHE_TMP_UPLOAD_PATH
+\- Type:        string
+\- Default:     \[dq]\[dq]
+
+#### \-\-cache\-tmp\-wait\-time
+
 How long should files be stored in local cache before being uploaded
-.PP
+
 This is the duration that a file must wait in the temporary location
-\f[I]cache\-tmp\-upload\-path\f[R] before it is selected for upload.
-.PP
-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.
-.IP \[bu] 2
-Config: tmp_wait_time
-.IP \[bu] 2
-Env Var: RCLONE_CACHE_TMP_WAIT_TIME
-.IP \[bu] 2
-Type: Duration
-.IP \[bu] 2
-Default: 15s
-.SS \[en]cache\-db\-wait\-time
-.PP
+_cache\-tmp\-upload\-path_ before it is selected for upload.
+
+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.
+
+\- Config:      tmp_wait_time
+\- Env Var:     RCLONE_CACHE_TMP_WAIT_TIME
+\- Type:        Duration
+\- Default:     15s
+
+#### \-\-cache\-db\-wait\-time
+
 How long to wait for the DB to be available \- 0 is unlimited
-.PP
+
 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.
-.PP
+
 If you set it to 0 then it will wait forever.
-.IP \[bu] 2
-Config: db_wait_time
-.IP \[bu] 2
-Env Var: RCLONE_CACHE_DB_WAIT_TIME
-.IP \[bu] 2
-Type: Duration
-.IP \[bu] 2
-Default: 1s
-.SS Backend commands
-.PP
+
+\- Config:      db_wait_time
+\- Env Var:     RCLONE_CACHE_DB_WAIT_TIME
+\- Type:        Duration
+\- Default:     1s
+
+### Backend commands
+
 Here are the commands specific to the cache backend.
-.PP
+
 Run them with
-.IP
-.nf
-\f[C]
-rclone backend COMMAND remote:
-\f[R]
-.fi
-.PP
+
+    rclone backend COMMAND remote:
+
 The help below will explain what arguments each command takes.
-.PP
-See the \[lq]rclone backend\[rq]
-command (https://rclone.org/commands/rclone_backend/) for more info on
-how to pass options and arguments.
-.PP
+
+See [the \[dq]rclone backend\[dq] command](https://rclone.org/commands/rclone_backend/) for more
+info on how to pass options and arguments.
+
 These can be run on a running backend using the rc command
-backend/command (https://rclone.org/rc/#backend/command).
-.SS stats
-.PP
+[backend/command](https://rclone.org/rc/#backend/command).
+
+#### stats
+
 Print stats on the cache backend in JSON format.
+
+    rclone backend stats remote: [options] [<arguments>+]
+
+
+
+Chunker (BETA)
+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
+
+The \[ga]chunker\[ga] 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.
+
+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.
+
+First check your chosen remote is working \- we\[aq]ll call it \[ga]remote:path\[ga] here.
+Note that anything inside \[ga]remote:path\[ga] will be chunked and anything outside
+won\[aq]t. This means that if you are using a bucket based remote (eg S3, B2, swift)
+then you should probably put the bucket in the remote \[ga]s3:bucket\[ga].
+
+Now configure \[ga]chunker\[ga] using \[ga]rclone config\[ga]. We will call this one \[ga]overlay\[ga]
+to separate it from the \[ga]remote\[ga] itself.
+\f[R]
+.fi
+.PP
+No remotes found \- make a new one n) New remote s) Set configuration
+password q) Quit config n/s/q> n name> overlay Type of storage to
+configure.
+Choose a number from below, or type in your own value [snip] XX /
+Transparently chunk/split large files \ \[dq]chunker\[dq] [snip]
+Storage> chunker Remote to chunk/unchunk.
+Normally should contain a \[aq]:\[aq] and a path, eg
+\[dq]myremote:path/to/dir\[dq], \[dq]myremote:bucket\[dq] or maybe
+\[dq]myremote:\[dq] (not recommended).
+Enter a string value.
+Press Enter for the default (\[dq]\[dq]).
+remote> 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 (\[dq]2G\[dq]).
+chunk_size> 100M Choose how chunker handles hash sums.
+All modes but \[dq]none\[dq] require metadata.
+Enter a string value.
+Press Enter for the default (\[dq]md5\[dq]).
+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 \ \[dq]none\[dq] 2 / MD5 for composite files \ \[dq]md5\[dq] 3
+/ SHA1 for composite files \ \[dq]sha1\[dq] 4 / MD5 for all files
+\ \[dq]md5all\[dq] 5 / SHA1 for all files \ \[dq]sha1all\[dq] 6 /
+Copying a file to chunker will request MD5 from the source falling back
+to SHA1 if unsupported \ \[dq]md5quick\[dq] 7 / Similar to
+\[dq]md5quick\[dq] but prefers SHA1 over MD5 \ \[dq]sha1quick\[dq]
+hash_type> md5 Edit advanced config?
+(y/n) y) Yes n) No y/n> 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> y
 .IP
 .nf
 \f[C]
-rclone backend stats remote: [options] [<arguments>+]
-\f[R]
-.fi
-.SS Chunker (BETA)
-.PP
-The \f[C]chunker\f[R] 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.
-.PP
-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.
-.PP
-First check your chosen remote is working \- we\[cq]ll call it
-\f[C]remote:path\f[R] here.
-Note that anything inside \f[C]remote:path\f[R] will be chunked and
-anything outside won\[cq]t.
-This means that if you are using a bucket based remote (eg S3, B2,
-swift) then you should probably put the bucket in the remote
-\f[C]s3:bucket\f[R].
-.PP
-Now configure \f[C]chunker\f[R] using \f[C]rclone config\f[R].
-We will call this one \f[C]overlay\f[R] to separate it from the
-\f[C]remote\f[R] itself.
-.IP
-.nf
-\f[C]
-No remotes found \- make a new one
-n) New remote
-s) Set configuration password
-q) Quit config
-n/s/q> n
-name> overlay
-Type of storage to configure.
-Choose a number from below, or type in your own value
-[snip]
-XX / Transparently chunk/split large files
-   \[rs] \[dq]chunker\[dq]
-[snip]
-Storage> chunker
-Remote to chunk/unchunk.
-Normally should contain a \[aq]:\[aq] and a path, eg \[dq]myremote:path/to/dir\[dq],
-\[dq]myremote:bucket\[dq] or maybe \[dq]myremote:\[dq] (not recommended).
-Enter a string value. Press Enter for the default (\[dq]\[dq]).
-remote> 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 (\[dq]2G\[dq]).
-chunk_size> 100M
-Choose how chunker handles hash sums. All modes but \[dq]none\[dq] require metadata.
-Enter a string value. Press Enter for the default (\[dq]md5\[dq]).
-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
-   \[rs] \[dq]none\[dq]
- 2 / MD5 for composite files
-   \[rs] \[dq]md5\[dq]
- 3 / SHA1 for composite files
-   \[rs] \[dq]sha1\[dq]
- 4 / MD5 for all files
-   \[rs] \[dq]md5all\[dq]
- 5 / SHA1 for all files
-   \[rs] \[dq]sha1all\[dq]
- 6 / Copying a file to chunker will request MD5 from the source falling back to SHA1 if unsupported
-   \[rs] \[dq]md5quick\[dq]
- 7 / Similar to \[dq]md5quick\[dq] but prefers SHA1 over MD5
-   \[rs] \[dq]sha1quick\[dq]
-hash_type> md5
-Edit advanced config? (y/n)
-y) Yes
-n) No
-y/n> 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> y
-\f[R]
-.fi
-.SS Specifying the remote
-.PP
-In normal use, make sure the remote has a \f[C]:\f[R] in.
-If you specify the remote without a \f[C]:\f[R] then rclone will use a
-local directory of that name.
-So if you use a remote of \f[C]/path/to/secret/files\f[R] then rclone
-will chunk stuff in that directory.
-If you use a remote of \f[C]name\f[R] then rclone will put files in a
-directory called \f[C]name\f[R] in the current directory.
-.SS Chunking
-.PP
-When rclone starts a file upload, chunker checks the file size.
-If it doesn\[cq]t exceed the configured chunk size, chunker will just
-pass the file to the wrapped remote.
-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.
-.PP
+
+### Specifying the remote
+
+In normal use, make sure the remote has a \[ga]:\[ga] in. If you specify the remote
+without a \[ga]:\[ga] then rclone will use a local directory of that name.
+So if you use a remote of \[ga]/path/to/secret/files\[ga] then rclone will
+chunk stuff in that directory. If you use a remote of \[ga]name\[ga] then rclone
+will put files in a directory called \[ga]name\[ga] in the current directory.
+
+
+### Chunking
+
+When rclone starts a file upload, chunker checks the file size. If it
+doesn\[aq]t exceed the configured chunk size, chunker will just pass the file
+to the wrapped remote. 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.
+
 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.
-.PP
+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.
+
 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.
-.PP
-When the \f[C]list\f[R] 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.
-.PP
+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.
+
+When the \[ga]list\[ga] 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.
+
 List and other commands can sometimes come across composite files with
-missing or invalid chunks, eg.
-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 \f[C]\-\-chunker\-fail\-hard\f[R] flag to have commands
-abort with error message in such cases.
-.SS Chunk names
-.PP
-The default chunk name format is \f[C]*.rclone_chunk.###\f[R], hence by
-default chunk names are \f[C]BIG_FILE_NAME.rclone_chunk.001\f[R],
-\f[C]BIG_FILE_NAME.rclone_chunk.002\f[R] etc.
-You can configure another name format using the \f[C]name_format\f[R]
-configuration file option.
-The format uses asterisk \f[C]*\f[R] as a placeholder for the base file
-name and one or more consecutive hash characters \f[C]#\f[R] 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.
+missing or invalid chunks, eg. 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 \[ga]\-\-chunker\-fail\-hard\[ga] flag to have commands abort with
+error message in such cases.
+
+
+#### Chunk names
+
+The default chunk name format is \[ga]*.rclone_chunk.###\[ga], hence by default
+chunk names are \[ga]BIG_FILE_NAME.rclone_chunk.001\[ga],
+\[ga]BIG_FILE_NAME.rclone_chunk.002\[ga] etc. You can configure another name format
+using the \[ga]name_format\[ga] configuration file option. The format uses asterisk
+\[ga]*\[ga] as a placeholder for the base file name and one or more consecutive
+hash characters \[ga]#\[ga] 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, eg.
-for compatibility with legacy software.
-.PP
-For example, if name format is \f[C]big_*\-##.part\f[R] and original
-file name is \f[C]data.txt\f[R] and numbering starts from 0, then the
-first chunk will be named \f[C]big_data.txt\-00.part\f[R], the 99th
-chunk will be \f[C]big_data.txt\-98.part\f[R] and the 302nd chunk will
-become \f[C]big_data.txt\-301.part\f[R].
-.PP
-Note that \f[C]list\f[R] assembles composite directory entries only when
-chunk names match the configured format and treats non\-conforming file
-names as normal non\-chunked files.
-.SS Metadata
-.PP
-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 \f[C]none\f[R]
-format).
+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, eg. for compatibility with legacy software.
+
+For example, if name format is \[ga]big_*\-##.part\[ga] and original file name is
+\[ga]data.txt\[ga] and numbering starts from 0, then the first chunk will be named
+\[ga]big_data.txt\-00.part\[ga], the 99th chunk will be \[ga]big_data.txt\-98.part\[ga]
+and the 302nd chunk will become \[ga]big_data.txt\-301.part\[ga].
+
+Note that \[ga]list\[ga] assembles composite directory entries only when chunk names
+match the configured format and treats non\-conforming file names as normal
+non\-chunked files.
+
+
+### Metadata
+
+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 \[ga]none\[ga] format).
 Note that metadata is normally not created for files smaller than the
-configured chunk size.
-This may change in future rclone releases.
-.SS Simple JSON metadata format
-.PP
-This is the default format.
-It supports hash sums and chunk validation for composite files.
-Meta objects carry the following fields:
-.IP \[bu] 2
-\f[C]ver\f[R] \- version of format, currently \f[C]1\f[R]
-.IP \[bu] 2
-\f[C]size\f[R] \- total size of composite file
-.IP \[bu] 2
-\f[C]nchunks\f[R] \- number of data chunks in file
-.IP \[bu] 2
-\f[C]md5\f[R] \- MD5 hashsum of composite file (if present)
-.IP \[bu] 2
-\f[C]sha1\f[R] \- SHA1 hashsum (if present)
-.PP
-There is no field for composite file name as it\[cq]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.
-.SS No metadata
-.PP
-You can disable meta objects by setting the meta format option to
-\f[C]none\f[R].
+configured chunk size. This may change in future rclone releases.
+
+#### Simple JSON metadata format
+
+This is the default format. It supports hash sums and chunk validation
+for composite files. Meta objects carry the following fields:
+
+\- \[ga]ver\[ga]     \- version of format, currently \[ga]1\[ga]
+\- \[ga]size\[ga]    \- total size of composite file
+\- \[ga]nchunks\[ga] \- number of data chunks in file
+\- \[ga]md5\[ga]     \- MD5 hashsum of composite file (if present)
+\- \[ga]sha1\[ga]    \- SHA1 hashsum (if present)
+
+There is no field for composite file name as it\[aq]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.
+
+#### No metadata
+
+You can disable meta objects by setting the meta format option to \[ga]none\[ga].
 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.
+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.
-.SS Hashsums
-.PP
+
+
+### Hashsums
+
 Chunker supports hashsums only when a compatible metadata is present.
-Hence, if you choose metadata format of \f[C]none\f[R], chunker will
-report hashsum as \f[C]UNSUPPORTED\f[R].
-.PP
+Hence, if you choose metadata format of \[ga]none\[ga], chunker will report hashsum
+as \[ga]UNSUPPORTED\[ga].
+
 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.
+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\[cq]t support it.
-.PP
+files if the wrapped remote doesn\[aq]t support it.
+
 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
+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.
-.PP
-If your storage backend does not support MD5 or SHA1 but you need
-consistent file hashing, configure chunker with \f[C]md5all\f[R] or
-\f[C]sha1all\f[R].
-These two modes guarantee given hash for all files.
-If wrapped remote doesn\[cq]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.
+
+If your storage backend does not support MD5 or SHA1 but you need consistent
+file hashing, configure chunker with \[ga]md5all\[ga] or \[ga]sha1all\[ga]. These two modes
+guarantee given hash for all files. If wrapped remote doesn\[aq]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 eg.
-\f[C]chunk_type=sha1all\f[R] to force hashsums and
-\f[C]chunk_size=1P\f[R] to effectively disable chunking.
-.PP
+at expense of sidecar meta objects by setting eg. \[ga]chunk_type=sha1all\[ga]
+to force hashsums and \[ga]chunk_size=1P\[ga] to effectively disable chunking.
+
 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: \f[C]sha1quick\f[R] and \f[C]md5quick\f[R].
-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 \f[C]sync\f[R] command will revert
-(sometimes silently) to time/size comparison if compatible hashsums
+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: \[ga]sha1quick\[ga] and \[ga]md5quick\[ga]. 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 \[ga]sync\[ga] command will
+revert (sometimes silently) to time/size comparison if compatible hashsums
 between source and target are not found.
-.SS Modified time
-.PP
+
+
+### Modified time
+
 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 \f[C]none\f[R] then chunker
-will use modification time of the first data chunk.
-.SS Migrations
-.PP
+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 \[ga]none\[ga] then chunker will
+use modification time of the first data chunk.
+
+
+### Migrations
+
 The idiomatic way to migrate to a different chunk size, hash type or
 chunk naming scheme is to:
-.IP \[bu] 2
-Collect all your chunked files under a directory and have your chunker
-remote point to it.
-.IP \[bu] 2
-Create another directory (most probably on the same cloud storage) and
-configure a new remote with desired metadata format, hash type, chunk
-naming etc.
-.IP \[bu] 2
-Now run \f[C]rclone sync oldchunks: newchunks:\f[R] and all your data
-will be transparently converted in transfer.
-This may take some time, yet chunker will try server\-side copy if
-possible.
-.IP \[bu] 2
-After checking data integrity you may remove configuration section of
-the old remote.
-.PP
+
+\- Collect all your chunked files under a directory and have your
+  chunker remote point to it.
+\- Create another directory (most probably on the same cloud storage)
+  and configure a new remote with desired metadata format,
+  hash type, chunk naming etc.
+\- Now run \[ga]rclone sync \-i oldchunks: newchunks:\[ga] and all your data
+  will be transparently converted in transfer.
+  This may take some time, yet chunker will try server\-side
+  copy if possible.
+\- After checking data integrity you may remove configuration section
+  of the old remote.
+
 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 \f[C]list\f[R] command but will eat up
-your account quota.
-Please note that the \f[C]deletefile\f[R] command deletes only active
-chunks of a file.
-As a workaround, you can use remote of the wrapped file system to see
-them.
+hidden temporary chunks may stay in the directory. They will not be
+shown by the \[ga]list\[ga] command but will eat up your account quota.
+Please note that the \[ga]deletefile\[ga] 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 \f[C]copy\f[R] command will copy only active chunks while the
-\f[C]purge\f[R] will remove everything including garbage.
-.SS Caveats and Limitations
-.PP
-Chunker requires wrapped remote to support server side \f[C]move\f[R]
-(or \f[C]copy\f[R] + \f[C]delete\f[R]) 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.
-.PP
-Chunker encodes chunk number in file name, so with default
-\f[C]name_format\f[R] 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\[cq]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 eg.
-\f[C]*.rcc##\f[R] and save 10 characters (provided at most 99 chunks per
-file).
-.PP
-Note that a move implemented using the copy\-and\-delete method may
-incur double charging with some cloud storage providers.
-.PP
+The \[ga]copy\[ga] command will copy only active chunks while the \[ga]purge\[ga] will
+remove everything including garbage.
+
+
+### Caveats and Limitations
+
+Chunker requires wrapped remote to support server side \[ga]move\[ga] (or \[ga]copy\[ga] +
+\[ga]delete\[ga]) 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.
+
+Chunker encodes chunk number in file name, so with default \[ga]name_format\[ga]
+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\[aq]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
+eg. \[ga]*.rcc##\[ga] and save 10 characters (provided at most 99 chunks per file).
+
+Note that a move implemented using the copy\-and\-delete method may incur
+double charging with some cloud storage providers.
+
 Chunker will not automatically rename existing chunks when you run
-\f[C]rclone config\f[R] 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.
+\[ga]rclone config\[ga] 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.
-.PP
+
 If wrapped remote is case insensitive, the chunker overlay will inherit
-that property (so you can\[cq]t have a file called \[lq]Hello.doc\[rq]
-and \[lq]hello.doc\[rq] in the same directory).
-.SS Standard Options
-.PP
-Here are the standard options specific to chunker (Transparently
-chunk/split large files).
-.SS \[en]chunker\-remote
-.PP
+that property (so you can\[aq]t have a file called \[dq]Hello.doc\[dq] and \[dq]hello.doc\[dq]
+in the same directory).
+
+
+
+### Standard Options
+
+Here are the standard options specific to chunker (Transparently chunk/split large files).
+
+#### \-\-chunker\-remote
+
 Remote to chunk/unchunk.
-Normally should contain a `:' and a path, eg
-\[lq]myremote:path/to/dir\[rq], \[lq]myremote:bucket\[rq] or maybe
-\[lq]myremote:\[rq] (not recommended).
-.IP \[bu] 2
-Config: remote
-.IP \[bu] 2
-Env Var: RCLONE_CHUNKER_REMOTE
-.IP \[bu] 2
-Type: string
-.IP \[bu] 2
-Default: \[dq]\[dq]
-.SS \[en]chunker\-chunk\-size
-.PP
+Normally should contain a \[aq]:\[aq] and a path, eg \[dq]myremote:path/to/dir\[dq],
+\[dq]myremote:bucket\[dq] or maybe \[dq]myremote:\[dq] (not recommended).
+
+\- Config:      remote
+\- Env Var:     RCLONE_CHUNKER_REMOTE
+\- Type:        string
+\- Default:     \[dq]\[dq]
+
+#### \-\-chunker\-chunk\-size
+
 Files larger than chunk size will be split in chunks.
-.IP \[bu] 2
-Config: chunk_size
-.IP \[bu] 2
-Env Var: RCLONE_CHUNKER_CHUNK_SIZE
-.IP \[bu] 2
-Type: SizeSuffix
-.IP \[bu] 2
-Default: 2G
-.SS \[en]chunker\-hash\-type
-.PP
-Choose how chunker handles hash sums.
-All modes but \[lq]none\[rq] require metadata.
-.IP \[bu] 2
-Config: hash_type
-.IP \[bu] 2
-Env Var: RCLONE_CHUNKER_HASH_TYPE
-.IP \[bu] 2
-Type: string
-.IP \[bu] 2
-Default: \[lq]md5\[rq]
-.IP \[bu] 2
-Examples:
-.RS 2
-.IP \[bu] 2
-\[lq]none\[rq]
-.RS 2
-.IP \[bu] 2
-Pass any hash supported by wrapped remote for non\-chunked files, return
-nothing otherwise
-.RE
-.IP \[bu] 2
-\[lq]md5\[rq]
-.RS 2
-.IP \[bu] 2
-MD5 for composite files
-.RE
-.IP \[bu] 2
-\[lq]sha1\[rq]
-.RS 2
-.IP \[bu] 2
-SHA1 for composite files
-.RE
-.IP \[bu] 2
-\[lq]md5all\[rq]
-.RS 2
-.IP \[bu] 2
-MD5 for all files
-.RE
-.IP \[bu] 2
-\[lq]sha1all\[rq]
-.RS 2
-.IP \[bu] 2
-SHA1 for all files
-.RE
-.IP \[bu] 2
-\[lq]md5quick\[rq]
-.RS 2
-.IP \[bu] 2
-Copying a file to chunker will request MD5 from the source falling back
-to SHA1 if unsupported
-.RE
-.IP \[bu] 2
-\[lq]sha1quick\[rq]
-.RS 2
-.IP \[bu] 2
-Similar to \[lq]md5quick\[rq] but prefers SHA1 over MD5
-.RE
-.RE
-.SS Advanced Options
-.PP
-Here are the advanced options specific to chunker (Transparently
-chunk/split large files).
-.SS \[en]chunker\-name\-format
-.PP
+
+\- Config:      chunk_size
+\- Env Var:     RCLONE_CHUNKER_CHUNK_SIZE
+\- Type:        SizeSuffix
+\- Default:     2G
+
+#### \-\-chunker\-hash\-type
+
+Choose how chunker handles hash sums. All modes but \[dq]none\[dq] require metadata.
+
+\- Config:      hash_type
+\- Env Var:     RCLONE_CHUNKER_HASH_TYPE
+\- Type:        string
+\- Default:     \[dq]md5\[dq]
+\- Examples:
+    \- \[dq]none\[dq]
+        \- Pass any hash supported by wrapped remote for non\-chunked files, return nothing otherwise
+    \- \[dq]md5\[dq]
+        \- MD5 for composite files
+    \- \[dq]sha1\[dq]
+        \- SHA1 for composite files
+    \- \[dq]md5all\[dq]
+        \- MD5 for all files
+    \- \[dq]sha1all\[dq]
+        \- SHA1 for all files
+    \- \[dq]md5quick\[dq]
+        \- Copying a file to chunker will request MD5 from the source falling back to SHA1 if unsupported
+    \- \[dq]sha1quick\[dq]
+        \- Similar to \[dq]md5quick\[dq] but prefers SHA1 over MD5
+
+### Advanced Options
+
+Here are the advanced options specific to chunker (Transparently chunk/split large files).
+
+#### \-\-chunker\-name\-format
+
 String format of chunk file names.
-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.
+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.
-.IP \[bu] 2
-Config: name_format
-.IP \[bu] 2
-Env Var: RCLONE_CHUNKER_NAME_FORMAT
-.IP \[bu] 2
-Type: string
-.IP \[bu] 2
-Default: \[dq]*.rclone_chunk.###\[dq]
-.SS \[en]chunker\-start\-from
-.PP
-Minimum valid chunk number.
-Usually 0 or 1.
+Possible chunk files are ignored if their name does not match given format.
+
+\- Config:      name_format
+\- Env Var:     RCLONE_CHUNKER_NAME_FORMAT
+\- Type:        string
+\- Default:     \[dq]*.rclone_chunk.###\[dq]
+
+#### \-\-chunker\-start\-from
+
+Minimum valid chunk number. Usually 0 or 1.
 By default chunk numbers start from 1.
-.IP \[bu] 2
-Config: start_from
-.IP \[bu] 2
-Env Var: RCLONE_CHUNKER_START_FROM
-.IP \[bu] 2
-Type: int
-.IP \[bu] 2
-Default: 1
-.SS \[en]chunker\-meta\-format
-.PP
-Format of the metadata object or \[lq]none\[rq].
-By default \[lq]simplejson\[rq].
+
+\- Config:      start_from
+\- Env Var:     RCLONE_CHUNKER_START_FROM
+\- Type:        int
+\- Default:     1
+
+#### \-\-chunker\-meta\-format
+
+Format of the metadata object or \[dq]none\[dq]. By default \[dq]simplejson\[dq].
 Metadata is a small JSON file named after the composite file.
-.IP \[bu] 2
-Config: meta_format
-.IP \[bu] 2
-Env Var: RCLONE_CHUNKER_META_FORMAT
-.IP \[bu] 2
-Type: string
-.IP \[bu] 2
-Default: \[lq]simplejson\[rq]
-.IP \[bu] 2
-Examples:
-.RS 2
-.IP \[bu] 2
-\[lq]none\[rq]
-.RS 2
-.IP \[bu] 2
-Do not use metadata files at all.
-Requires hash type \[lq]none\[rq].
-.RE
-.IP \[bu] 2
-\[lq]simplejson\[rq]
-.RS 2
-.IP \[bu] 2
-Simple JSON supports hash sums and chunk validation.
-.IP \[bu] 2
-It has the following fields: ver, size, nchunks, md5, sha1.
-.RE
-.RE
-.SS \[en]chunker\-fail\-hard
-.PP
+
+\- Config:      meta_format
+\- Env Var:     RCLONE_CHUNKER_META_FORMAT
+\- Type:        string
+\- Default:     \[dq]simplejson\[dq]
+\- Examples:
+    \- \[dq]none\[dq]
+        \- Do not use metadata files at all. Requires hash type \[dq]none\[dq].
+    \- \[dq]simplejson\[dq]
+        \- Simple JSON supports hash sums and chunk validation.
+        \- It has the following fields: ver, size, nchunks, md5, sha1.
+
+#### \-\-chunker\-fail\-hard
+
 Choose how chunker should handle files with missing or invalid chunks.
-.IP \[bu] 2
-Config: fail_hard
-.IP \[bu] 2
-Env Var: RCLONE_CHUNKER_FAIL_HARD
-.IP \[bu] 2
-Type: bool
-.IP \[bu] 2
-Default: false
-.IP \[bu] 2
-Examples:
-.RS 2
-.IP \[bu] 2
-\[lq]true\[rq]
-.RS 2
-.IP \[bu] 2
-Report errors and abort current command.
-.RE
-.IP \[bu] 2
-\[lq]false\[rq]
-.RS 2
-.IP \[bu] 2
-Warn user, skip incomplete file and proceed.
-.RE
-.RE
-.SS Citrix ShareFile
-.PP
-Citrix ShareFile (https://sharefile.com) is a secure file sharing and
-transfer service aimed as business.
-.PP
+
+\- Config:      fail_hard
+\- Env Var:     RCLONE_CHUNKER_FAIL_HARD
+\- Type:        bool
+\- Default:     false
+\- Examples:
+    \- \[dq]true\[dq]
+        \- Report errors and abort current command.
+    \- \[dq]false\[dq]
+        \- Warn user, skip incomplete file and proceed.
+
+
+
+##  Citrix ShareFile
+
+[Citrix ShareFile](https://sharefile.com) is a secure file sharing and transfer service aimed as business.
+
 The initial setup for Citrix ShareFile involves getting a token from
-Citrix ShareFile which you can in your browser.
-\f[C]rclone config\f[R] walks you through it.
-.PP
-Here is an example of how to make a remote called \f[C]remote\f[R].
-First run:
-.IP
-.nf
-\f[C]
- rclone config
+Citrix ShareFile which you can in your browser.  \[ga]rclone config\[ga] walks you
+through it.
+
+Here is an example of how to make a remote called \[ga]remote\[ga].  First run:
+
+     rclone config
+
+This will guide you through an interactive setup process:
 \f[R]
 .fi
 .PP
-This will guide you through an interactive setup process:
+No remotes found \- make a new one n) New remote s) Set configuration
+password q) Quit config n/s/q> n name> remote Type of storage to
+configure.
+Enter a string value.
+Press Enter for the default (\[dq]\[dq]).
+Choose a number from below, or type in your own value XX / Citrix
+Sharefile \ \[dq]sharefile\[dq] Storage> sharefile ** See help for
+sharefile backend at: https://rclone.org/sharefile/ **
+.PP
+ID of the root folder
+.PP
+Leave blank to access \[dq]Personal Folders\[dq].
+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 (\[dq]\[dq]).
+Choose a number from below, or type in your own value 1 / Access the
+Personal Folders.
+(Default) \ \[dq]\[dq] 2 / Access the Favorites folder.
+\ \[dq]favorites\[dq] 3 / Access all the shared folders.
+\ \[dq]allshared\[dq] 4 / Access all the individual connectors.
+\ \[dq]connectors\[dq] 5 / Access the home, favorites, and shared
+folders as well as the connectors.
+\ \[dq]top\[dq] root_folder_id> Edit advanced config?
+(y/n) y) Yes n) No y/n> n Remote config Use auto config?
+* Say Y if not sure * Say N if you are working on a remote or headless
+machine y) Yes n) No y/n> y If your browser doesn\[aq]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 \-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\- [remote] type =
+sharefile endpoint = https://XXX.sharefile.com token =
+{\[dq]access_token\[dq]:\[dq]XXX\[dq],\[dq]token_type\[dq]:\[dq]bearer\[dq],\[dq]refresh_token\[dq]:\[dq]XXX\[dq],\[dq]expiry\[dq]:\[dq]2019\-09\-30T19:41:45.878561877+01:00\[dq]}
+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\- y) Yes this is OK e) Edit this
+remote d) Delete this remote y/e/d> y
 .IP
 .nf
 \f[C]
-No remotes found \- make a new one
-n) New remote
-s) Set configuration password
-q) Quit config
-n/s/q> n
-name> remote
-Type of storage to configure.
-Enter a string value. Press Enter for the default (\[dq]\[dq]).
-Choose a number from below, or type in your own value
-XX / Citrix Sharefile
-   \[rs] \[dq]sharefile\[dq]
-Storage> sharefile
-** See help for sharefile backend at: https://rclone.org/sharefile/ **
+
+See the [remote setup docs](https://rclone.org/remote_setup/) for how to set it up on a
+machine with no Internet browser available.
+
+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 \[ga]http://127.0.0.1:53682/\[ga] and this it may require you to unblock
+it temporarily if you are running a host firewall.
+
+Once configured you can then use \[ga]rclone\[ga] like this,
+
+List directories in top level of your ShareFile
+
+    rclone lsd remote:
+
+List all the files in your ShareFile
+
+    rclone ls remote:
+
+To copy a local directory to an ShareFile directory called backup
+
+    rclone copy /home/source remote:backup
+
+Paths may be as deep as required, eg \[ga]remote:directory/subdirectory\[ga].
+
+### Modified time and hashes ###
+
+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.
+
+ShareFile supports MD5 type hashes, so you can use the \[ga]\-\-checksum\[ga]
+flag.
+
+### Transfers ###
+
+For files above 128MB rclone will use a chunked transfer.  Rclone will
+upload up to \[ga]\-\-transfers\[ga] chunks at the same time (shared among all
+the multipart uploads).  Chunks are buffered in memory and are
+normally 64MB so increasing \[ga]\-\-transfers\[ga] will increase memory use.
+
+### Limitations ###
+
+Note that ShareFile is case insensitive so you can\[aq]t have a file called
+\[dq]Hello.doc\[dq] and one called \[dq]hello.doc\[dq].
+
+ShareFile only supports filenames up to 256 characters in length.
+
+#### Restricted filename characters
+
+In addition to the [default restricted characters set](https://rclone.org/overview/#restricted\-characters)
+the following characters are also replaced:
+
+| Character | Value | Replacement |
+| \-\-\-\-\-\-\-\-\- |:\-\-\-\-\-:|:\-\-\-\-\-\-\-\-\-\-\-:|
+| \[rs]\[rs]        | 0x5C  | \[uFF3C]           |
+| *         | 0x2A  | \[uFF0A]           |
+| <         | 0x3C  | \[uFF1C]           |
+| >         | 0x3E  | \[uFF1E]           |
+| ?         | 0x3F  | \[uFF1F]           |
+| :         | 0x3A  | \[uFF1A]           |
+| \[rs]|        | 0x7C  | \[uFF5C]           |
+| \[dq]         | 0x22  | \[uFF02]           |
+
+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:
+
+| Character | Value | Replacement |
+| \-\-\-\-\-\-\-\-\- |:\-\-\-\-\-:|:\-\-\-\-\-\-\-\-\-\-\-:|
+| SP        | 0x20  | \[u2420]           |
+| .         | 0x2E  | \[uFF0E]           |
+
+Invalid UTF\-8 bytes will also be [replaced](https://rclone.org/overview/#invalid\-utf8),
+as they can\[aq]t be used in JSON strings.
+
+
+### Standard Options
+
+Here are the standard options specific to sharefile (Citrix Sharefile).
+
+#### \-\-sharefile\-root\-folder\-id
 
 ID of the root folder
 
 Leave blank to access \[dq]Personal Folders\[dq].  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 (\[dq]\[dq]).
-Choose a number from below, or type in your own value
- 1 / Access the Personal Folders. (Default)
-   \[rs] \[dq]\[dq]
- 2 / Access the Favorites folder.
-   \[rs] \[dq]favorites\[dq]
- 3 / Access all the shared folders.
-   \[rs] \[dq]allshared\[dq]
- 4 / Access all the individual connectors.
-   \[rs] \[dq]connectors\[dq]
- 5 / Access the home, favorites, and shared folders as well as the connectors.
-   \[rs] \[dq]top\[dq]
-root_folder_id> 
-Edit advanced config? (y/n)
-y) Yes
-n) No
-y/n> n
-Remote config
-Use auto config?
- * Say Y if not sure
- * Say N if you are working on a remote or headless machine
-y) Yes
-n) No
-y/n> y
-If your browser doesn\[aq]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
-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
-[remote]
-type = sharefile
-endpoint = https://XXX.sharefile.com
-token = {\[dq]access_token\[dq]:\[dq]XXX\[dq],\[dq]token_type\[dq]:\[dq]bearer\[dq],\[dq]refresh_token\[dq]:\[dq]XXX\[dq],\[dq]expiry\[dq]:\[dq]2019\-09\-30T19:41:45.878561877+01:00\[dq]}
-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
-y) Yes this is OK
-e) Edit this remote
-d) Delete this remote
-y/e/d> y
-\f[R]
-.fi
-.PP
-See the remote setup docs (https://rclone.org/remote_setup/) for how to
-set it up on a machine with no Internet browser available.
-.PP
-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 \f[C]http://127.0.0.1:53682/\f[R] and this it may require you
-to unblock it temporarily if you are running a host firewall.
-.PP
-Once configured you can then use \f[C]rclone\f[R] like this,
-.PP
-List directories in top level of your ShareFile
-.IP
-.nf
-\f[C]
-rclone lsd remote:
-\f[R]
-.fi
-.PP
-List all the files in your ShareFile
-.IP
-.nf
-\f[C]
-rclone ls remote:
-\f[R]
-.fi
-.PP
-To copy a local directory to an ShareFile directory called backup
-.IP
-.nf
-\f[C]
-rclone copy /home/source remote:backup
-\f[R]
-.fi
-.PP
-Paths may be as deep as required, eg
-\f[C]remote:directory/subdirectory\f[R].
-.SS Modified time and hashes
-.PP
-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.
-.PP
-ShareFile supports MD5 type hashes, so you can use the
-\f[C]\-\-checksum\f[R] flag.
-.SS Transfers
-.PP
-For files above 128MB rclone will use a chunked transfer.
-Rclone will upload up to \f[C]\-\-transfers\f[R] chunks at the same time
-(shared among all the multipart uploads).
-Chunks are buffered in memory and are normally 64MB so increasing
-\f[C]\-\-transfers\f[R] will increase memory use.
-.SS Limitations
-.PP
-Note that ShareFile is case insensitive so you can\[cq]t have a file
-called \[lq]Hello.doc\[rq] and one called \[lq]hello.doc\[rq].
-.PP
-ShareFile only supports filenames up to 256 characters in length.
-.SS Restricted filename characters
-.PP
-In addition to the default restricted characters
-set (https://rclone.org/overview/#restricted-characters) the following
-characters are also replaced:
-.PP
-.TS
-tab(@);
-l c c.
-T{
-Character
-T}@T{
-Value
-T}@T{
-Replacement
-T}
-_
-T{
-\[rs]
-T}@T{
-0x5C
-T}@T{
-\[uFF3C]
-T}
-T{
-*
-T}@T{
-0x2A
-T}@T{
-\[uFF0A]
-T}
-T{
-<
-T}@T{
-0x3C
-T}@T{
-\[uFF1C]
-T}
-T{
->
-T}@T{
-0x3E
-T}@T{
-\[uFF1E]
-T}
-T{
-?
-T}@T{
-0x3F
-T}@T{
-\[uFF1F]
-T}
-T{
-:
-T}@T{
-0x3A
-T}@T{
-\[uFF1A]
-T}
-T{
-|
-T}@T{
-0x7C
-T}@T{
-\[uFF5C]
-T}
-T{
-\[dq]
-T}@T{
-0x22
-T}@T{
-\[uFF02]
-T}
-.TE
-.PP
-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:
-.PP
-.TS
-tab(@);
-l c c.
-T{
-Character
-T}@T{
-Value
-T}@T{
-Replacement
-T}
-_
-T{
-SP
-T}@T{
-0x20
-T}@T{
-\[u2420]
-T}
-T{
-\&.
-T}@T{
-0x2E
-T}@T{
-\[uFF0E]
-T}
-.TE
-.PP
-Invalid UTF\-8 bytes will also be
-replaced (https://rclone.org/overview/#invalid-utf8), as they can\[cq]t
-be used in JSON strings.
-.SS Standard Options
-.PP
-Here are the standard options specific to sharefile (Citrix Sharefile).
-.SS \[en]sharefile\-root\-folder\-id
-.PP
-ID of the root folder
-.PP
-Leave blank to access \[lq]Personal Folders\[rq].
-You can use one of the standard values here or any folder ID (long hex
-number ID).
-.IP \[bu] 2
-Config: root_folder_id
-.IP \[bu] 2
-Env Var: RCLONE_SHAREFILE_ROOT_FOLDER_ID
-.IP \[bu] 2
-Type: string
-.IP \[bu] 2
-Default: \[dq]\[dq]
-.IP \[bu] 2
-Examples:
-.RS 2
-.IP \[bu] 2
-\[dq]\[dq]
-.RS 2
-.IP \[bu] 2
-Access the Personal Folders.
-(Default)
-.RE
-.IP \[bu] 2
-\[lq]favorites\[rq]
-.RS 2
-.IP \[bu] 2
-Access the Favorites folder.
-.RE
-.IP \[bu] 2
-\[lq]allshared\[rq]
-.RS 2
-.IP \[bu] 2
-Access all the shared folders.
-.RE
-.IP \[bu] 2
-\[lq]connectors\[rq]
-.RS 2
-.IP \[bu] 2
-Access all the individual connectors.
-.RE
-.IP \[bu] 2
-\[lq]top\[rq]
-.RS 2
-.IP \[bu] 2
-Access the home, favorites, and shared folders as well as the
-connectors.
-.RE
-.RE
-.SS Advanced Options
-.PP
+
+\- Config:      root_folder_id
+\- Env Var:     RCLONE_SHAREFILE_ROOT_FOLDER_ID
+\- Type:        string
+\- Default:     \[dq]\[dq]
+\- Examples:
+    \- \[dq]\[dq]
+        \- Access the Personal Folders. (Default)
+    \- \[dq]favorites\[dq]
+        \- Access the Favorites folder.
+    \- \[dq]allshared\[dq]
+        \- Access all the shared folders.
+    \- \[dq]connectors\[dq]
+        \- Access all the individual connectors.
+    \- \[dq]top\[dq]
+        \- Access the home, favorites, and shared folders as well as the connectors.
+
+### Advanced Options
+
 Here are the advanced options specific to sharefile (Citrix Sharefile).
-.SS \[en]sharefile\-upload\-cutoff
-.PP
+
+#### \-\-sharefile\-upload\-cutoff
+
 Cutoff for switching to multipart upload.
-.IP \[bu] 2
-Config: upload_cutoff
-.IP \[bu] 2
-Env Var: RCLONE_SHAREFILE_UPLOAD_CUTOFF
-.IP \[bu] 2
-Type: SizeSuffix
-.IP \[bu] 2
-Default: 128M
-.SS \[en]sharefile\-chunk\-size
-.PP
-Upload chunk size.
-Must a power of 2 >= 256k.
-.PP
-Making this larger will improve performance, but note that each chunk is
-buffered in memory one per transfer.
-.PP
+
+\- Config:      upload_cutoff
+\- Env Var:     RCLONE_SHAREFILE_UPLOAD_CUTOFF
+\- Type:        SizeSuffix
+\- Default:     128M
+
+#### \-\-sharefile\-chunk\-size
+
+Upload chunk size. Must a power of 2 >= 256k.
+
+Making this larger will improve performance, but note that each chunk
+is buffered in memory one per transfer.
+
 Reducing this will reduce memory usage but decrease performance.
-.IP \[bu] 2
-Config: chunk_size
-.IP \[bu] 2
-Env Var: RCLONE_SHAREFILE_CHUNK_SIZE
-.IP \[bu] 2
-Type: SizeSuffix
-.IP \[bu] 2
-Default: 64M
-.SS \[en]sharefile\-endpoint
-.PP
+
+\- Config:      chunk_size
+\- Env Var:     RCLONE_SHAREFILE_CHUNK_SIZE
+\- Type:        SizeSuffix
+\- Default:     64M
+
+#### \-\-sharefile\-endpoint
+
 Endpoint for API calls.
-.PP
-This is usually auto discovered as part of the oauth process, but can be
-set manually to something like: https://XXX.sharefile.com
-.IP \[bu] 2
-Config: endpoint
-.IP \[bu] 2
-Env Var: RCLONE_SHAREFILE_ENDPOINT
-.IP \[bu] 2
-Type: string
-.IP \[bu] 2
-Default: \[dq]\[dq]
-.SS \[en]sharefile\-encoding
-.PP
+
+This is usually auto discovered as part of the oauth process, but can
+be set manually to something like: https://XXX.sharefile.com
+
+
+\- Config:      endpoint
+\- Env Var:     RCLONE_SHAREFILE_ENDPOINT
+\- Type:        string
+\- Default:     \[dq]\[dq]
+
+#### \-\-sharefile\-encoding
+
 This sets the encoding for the backend.
-.PP
-See: the encoding section in the
-overview (https://rclone.org/overview/#encoding) for more info.
-.IP \[bu] 2
-Config: encoding
-.IP \[bu] 2
-Env Var: RCLONE_SHAREFILE_ENCODING
-.IP \[bu] 2
-Type: MultiEncoder
-.IP \[bu] 2
-Default:
-Slash,LtGt,DoubleQuote,Colon,Question,Asterisk,Pipe,BackSlash,Ctl,LeftSpace,LeftPeriod,RightSpace,RightPeriod,InvalidUtf8,Dot
-.SS Crypt
-.PP
-The \f[C]crypt\f[R] remote encrypts and decrypts another remote.
-.PP
+
+See: the [encoding section in the overview](https://rclone.org/overview/#encoding) for more info.
+
+\- Config:      encoding
+\- Env Var:     RCLONE_SHAREFILE_ENCODING
+\- Type:        MultiEncoder
+\- Default:     Slash,LtGt,DoubleQuote,Colon,Question,Asterisk,Pipe,BackSlash,Ctl,LeftSpace,LeftPeriod,RightSpace,RightPeriod,InvalidUtf8,Dot
+
+
+
+Crypt
+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
+
+The \[ga]crypt\[ga] remote encrypts and decrypts another remote.
+
 To use it first set up the underlying remote following the config
-instructions for that remote.
-You can also use a local pathname instead of a remote which will encrypt
-and decrypt from that directory which might be useful for encrypting
-onto a USB stick for example.
+instructions for that remote.  You can also use a local pathname
+instead of a remote which will encrypt and decrypt from that directory
+which might be useful for encrypting onto a USB stick for example.
+
+First check your chosen remote is working \- we\[aq]ll call it
+\[ga]remote:path\[ga] in these docs.  Note that anything inside \[ga]remote:path\[ga]
+will be encrypted and anything outside won\[aq]t.  This means that if you
+are using a bucket based remote (eg S3, B2, swift) then you should
+probably put the bucket in the remote \[ga]s3:bucket\[ga]. If you just use
+\[ga]s3:\[ga] then rclone will make encrypted bucket names too (if using file
+name encryption) which may or may not be what you want.
+
+Now configure \[ga]crypt\[ga] using \[ga]rclone config\[ga]. We will call this one
+\[ga]secret\[ga] to differentiate it from the \[ga]remote\[ga].
+\f[R]
+.fi
 .PP
-First check your chosen remote is working \- we\[cq]ll call it
-\f[C]remote:path\f[R] in these docs.
-Note that anything inside \f[C]remote:path\f[R] will be encrypted and
-anything outside won\[cq]t.
-This means that if you are using a bucket based remote (eg S3, B2,
-swift) then you should probably put the bucket in the remote
-\f[C]s3:bucket\f[R].
-If you just use \f[C]s3:\f[R] then rclone will make encrypted bucket
-names too (if using file name encryption) which may or may not be what
-you want.
-.PP
-Now configure \f[C]crypt\f[R] using \f[C]rclone config\f[R].
-We will call this one \f[C]secret\f[R] to differentiate it from the
-\f[C]remote\f[R].
+No remotes found \- make a new one n) New remote s) Set configuration
+password q) Quit config n/s/q> n
+.PD 0
+.P
+.PD
+name> secret Type of storage to configure.
+Choose a number from below, or type in your own value [snip] XX /
+Encrypt/Decrypt a remote \ \[dq]crypt\[dq] [snip] Storage> crypt Remote
+to encrypt/decrypt.
+Normally should contain a \[aq]:\[aq] and a path, eg
+\[dq]myremote:path/to/dir\[dq], \[dq]myremote:bucket\[dq] or maybe
+\[dq]myremote:\[dq] (not recommended).
+remote> remote:path How to encrypt the filenames.
+Choose a number from below, or type in your own value 1 / Don\[aq]t
+encrypt the file names.
+Adds a \[dq].bin\[dq] extension only.
+\ \[dq]off\[dq] 2 / Encrypt the filenames see the docs for the details.
+\ \[dq]standard\[dq] 3 / Very simple filename obfuscation.
+\ \[dq]obfuscate\[dq] filename_encryption> 2 Option to either encrypt
+directory names or leave them intact.
+Choose a number from below, or type in your own value 1 / Encrypt
+directory names.
+\ \[dq]true\[dq] 2 / Don\[aq]t encrypt directory names, leave them
+intact.
+\ \[dq]false\[dq] filename_encryption> 1 Password or pass phrase for
+encryption.
+y) Yes type in my own password g) Generate random password y/g> 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 y/g/n> g Password strength in bits.
+64 is just about memorable 128 is secure 1024 is the maximum Bits> 128
+Your password is: JAsJvRcgR\-_veXNfy_sGmQ Use this password?
+y) Yes n) No y/n> y Remote config
+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\- [secret] remote = remote:path
+filename_encryption = standard password = *** ENCRYPTED \f[B]\f[BI]
+password2 = \f[B]\f[R] ENCRYPTED ***
+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\- y) Yes this is OK e) Edit this
+remote d) Delete this remote y/e/d> y
 .IP
 .nf
 \f[C]
-No remotes found \- make a new one
-n) New remote
-s) Set configuration password
-q) Quit config
-n/s/q> n   
-name> secret
-Type of storage to configure.
-Choose a number from below, or type in your own value
-[snip]
-XX / Encrypt/Decrypt a remote
-   \[rs] \[dq]crypt\[dq]
-[snip]
-Storage> crypt
+
+**Important** The password is stored in the config file is lightly
+obscured so it isn\[aq]t immediately obvious what it is.  It is in no way
+secure unless you use config file encryption.
+
+A long passphrase is recommended, or you can use a random one.
+
+The obscured password is created by using AES\-CTR with a static key, with
+the salt stored verbatim at the beginning of the obscured password. This
+static key is shared by between all versions of rclone.
+
+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.
+
+Note that rclone does not encrypt
+
+  * file length \- this can be calculated within 16 bytes
+  * modification time \- used for syncing
+
+## Specifying the remote ##
+
+In normal use, make sure the remote has a \[ga]:\[ga] in. If you specify the
+remote without a \[ga]:\[ga] then rclone will use a local directory of that
+name.  So if you use a remote of \[ga]/path/to/secret/files\[ga] then rclone
+will encrypt stuff to that directory.  If you use a remote of \[ga]name\[ga]
+then rclone will put files in a directory called \[ga]name\[ga] in the current
+directory.
+
+If you specify the remote as \[ga]remote:path/to/dir\[ga] then rclone will
+store encrypted files in \[ga]path/to/dir\[ga] on the remote. If you are using
+file name encryption, then when you save files to
+\[ga]secret:subdir/subfile\[ga] this will store them in the unencrypted path
+\[ga]path/to/dir\[ga] but the \[ga]subdir/subpath\[ga] bit will be encrypted.
+
+Note that unless you want encrypted bucket names (which are difficult
+to manage because you won\[aq]t know what directory they represent in web
+interfaces etc), you should probably specify a bucket, eg
+\[ga]remote:secretbucket\[ga] when using bucket based remotes such as S3,
+Swift, Hubic, B2, GCS.
+
+## Example ##
+
+To test I made a little directory of files using \[dq]standard\[dq] file name
+encryption.
+\f[R]
+.fi
+.PP
+plaintext/ \[u251C]\[u2500]\[u2500] file0.txt \[u251C]\[u2500]\[u2500]
+file1.txt \[u2514]\[u2500]\[u2500] subdir \[u251C]\[u2500]\[u2500]
+file2.txt \[u251C]\[u2500]\[u2500] file3.txt \[u2514]\[u2500]\[u2500]
+subsubdir \[u2514]\[u2500]\[u2500] file4.txt
+.IP
+.nf
+\f[C]
+
+Copy these to the remote and list them back
+\f[R]
+.fi
+.PP
+$ 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
+.IP
+.nf
+\f[C]
+
+Now see what that looked like when encrypted
+\f[R]
+.fi
+.PP
+$ rclone \-q ls remote:path 55 hagjclgavj2mbiqm6u6cnjjqcg 54
+v05749mltvv1tf4onltun46gls 57
+86vhrsv86mpbtd3a0akjuqslj8/dlj7fkq4kdq72emafg7a7s41uo 58
+86vhrsv86mpbtd3a0akjuqslj8/7uu829995du6o42n32otfhjqp4/b9pausrfansjth5ob3jkdqd4lc
+56 86vhrsv86mpbtd3a0akjuqslj8/8njh1sk437gttmep3p70g81aps
+.IP
+.nf
+\f[C]
+
+Note that this retains the directory structure which means you can do this
+\f[R]
+.fi
+.PP
+$ rclone \-q ls secret:subdir 8 file2.txt 9 file3.txt 10
+subsubdir/file4.txt
+.IP
+.nf
+\f[C]
+
+If don\[aq]t use file name encryption then the remote will look like this
+\- note the \[ga].bin\[ga] extensions added to prevent the cloud provider
+attempting to interpret the data.
+\f[R]
+.fi
+.PP
+$ 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
+.IP
+.nf
+\f[C]
+
+### File name encryption modes ###
+
+Here are some of the features of the file name encryption modes
+
+Off
+
+  * doesn\[aq]t hide file names or directory structure
+  * allows for longer file names (\[ti]246 characters)
+  * can use sub paths and copy single files
+
+Standard
+
+  * file names encrypted
+  * file names can\[aq]t be as long (\[ti]143 characters)
+  * can use sub paths and copy single files
+  * directory structure visible
+  * identical files names will have identical uploaded names
+  * can use shortcuts to shorten the directory recursion
+
+Obfuscation
+
+This is a simple \[dq]rotate\[dq] of the filename, with each file having a rot
+distance based on the filename. We store the distance at the beginning
+of the filename. So a file called \[dq]hello\[dq] may become \[dq]53.jgnnq\[dq].
+
+This is not a strong encryption of filenames, but it may stop automated
+scanning tools from picking up on filename patterns. As such it\[aq]s an
+intermediate between \[dq]off\[dq] and \[dq]standard\[dq]. The advantage is that it
+allows for longer path segment names.
+
+There is a possibility with some unicode based filenames that the
+obfuscation is weak and may map lower case characters to upper case
+equivalents.  You can not rely on this for strong protection.
+
+  * file names very lightly obfuscated
+  * file names can be longer than standard encryption
+  * can use sub paths and copy single files
+  * directory structure visible
+  * identical files names will have identical uploaded names
+
+Cloud storage systems have various limits on file name length and
+total path length which you are more likely to hit using \[dq]Standard\[dq]
+file name encryption.  If you keep your file names to below 156
+characters in length then you should be OK on all providers.
+
+There may be an even more secure file name encryption mode in the
+future which will address the long file name problem.
+
+### Directory name encryption ###
+Crypt offers the option of encrypting dir names or leaving them intact.
+There are two options:
+
+True
+
+Encrypts the whole file path including directory names
+Example:
+\[ga]1/12/123.txt\[ga] is encrypted to
+\[ga]p0e52nreeaj0a5ea7s64m4j72s/l42g6771hnv3an9cgc8cr2n1ng/qgm4avr35m5loi1th53ato71v0\[ga]
+
+False
+
+Only encrypts file names, skips directory names
+Example:
+\[ga]1/12/123.txt\[ga] is encrypted to
+\[ga]1/12/qgm4avr35m5loi1th53ato71v0\[ga]
+
+
+### Modified time and hashes ###
+
+Crypt stores modification times using the underlying remote so support
+depends on that.
+
+Hashes are not stored for crypt.  However the data integrity is
+protected by an extremely strong crypto authenticator.
+
+Note that you should use the \[ga]rclone cryptcheck\[ga] command to check the
+integrity of a crypted remote instead of \[ga]rclone check\[ga] which can\[aq]t
+check the checksums properly.
+
+
+### Standard Options
+
+Here are the standard options specific to crypt (Encrypt/Decrypt a remote).
+
+#### \-\-crypt\-remote
+
 Remote to encrypt/decrypt.
 Normally should contain a \[aq]:\[aq] and a path, eg \[dq]myremote:path/to/dir\[dq],
 \[dq]myremote:bucket\[dq] or maybe \[dq]myremote:\[dq] (not recommended).
-remote> remote:path
+
+\- Config:      remote
+\- Env Var:     RCLONE_CRYPT_REMOTE
+\- Type:        string
+\- Default:     \[dq]\[dq]
+
+#### \-\-crypt\-filename\-encryption
+
 How to encrypt the filenames.
-Choose a number from below, or type in your own value
- 1 / Don\[aq]t encrypt the file names.  Adds a \[dq].bin\[dq] extension only.
-   \[rs] \[dq]off\[dq]
- 2 / Encrypt the filenames see the docs for the details.
-   \[rs] \[dq]standard\[dq]
- 3 / Very simple filename obfuscation.
-   \[rs] \[dq]obfuscate\[dq]
-filename_encryption> 2
+
+\- Config:      filename_encryption
+\- Env Var:     RCLONE_CRYPT_FILENAME_ENCRYPTION
+\- Type:        string
+\- Default:     \[dq]standard\[dq]
+\- Examples:
+    \- \[dq]standard\[dq]
+        \- Encrypt the filenames see the docs for the details.
+    \- \[dq]obfuscate\[dq]
+        \- Very simple filename obfuscation.
+    \- \[dq]off\[dq]
+        \- Don\[aq]t encrypt the file names.  Adds a \[dq].bin\[dq] extension only.
+
+#### \-\-crypt\-directory\-name\-encryption
+
 Option to either encrypt directory names or leave them intact.
-Choose a number from below, or type in your own value
- 1 / Encrypt directory names.
-   \[rs] \[dq]true\[dq]
- 2 / Don\[aq]t encrypt directory names, leave them intact.
-   \[rs] \[dq]false\[dq]
-filename_encryption> 1
+
+NB If filename_encryption is \[dq]off\[dq] then this option will do nothing.
+
+\- Config:      directory_name_encryption
+\- Env Var:     RCLONE_CRYPT_DIRECTORY_NAME_ENCRYPTION
+\- Type:        bool
+\- Default:     true
+\- Examples:
+    \- \[dq]true\[dq]
+        \- Encrypt directory names.
+    \- \[dq]false\[dq]
+        \- Don\[aq]t encrypt directory names, leave them intact.
+
+#### \-\-crypt\-password
+
 Password or pass phrase for encryption.
-y) Yes type in my own password
-g) Generate random password
-y/g> y
-Enter the password:
-password:
-Confirm the password:
-password:
+
+**NB** Input to this must be obscured \- see [rclone obscure](https://rclone.org/commands/rclone_obscure/).
+
+\- Config:      password
+\- Env Var:     RCLONE_CRYPT_PASSWORD
+\- Type:        string
+\- Default:     \[dq]\[dq]
+
+#### \-\-crypt\-password2
+
 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
-y/g/n> g
-Password strength in bits.
-64 is just about memorable
-128 is secure
-1024 is the maximum
-Bits> 128
-Your password is: JAsJvRcgR\-_veXNfy_sGmQ
-Use this password?
-y) Yes
-n) No
-y/n> y
-Remote config
-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
-[secret]
-remote = remote:path
-filename_encryption = standard
-password = *** ENCRYPTED ***
-password2 = *** ENCRYPTED ***
-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
-y) Yes this is OK
-e) Edit this remote
-d) Delete this remote
-y/e/d> y
-\f[R]
-.fi
-.PP
-\f[B]Important\f[R] The password is stored in the config file is lightly
-obscured so it isn\[cq]t immediately obvious what it is.
-It is in no way secure unless you use config file encryption.
-.PP
-A long passphrase is recommended, or you can use a random one.
-.PP
-The obscured password is created by using AES\-CTR with a static key,
-with the salt stored verbatim at the beginning of the obscured password.
-This static key is shared by between all versions of rclone.
-.PP
-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.
-.PP
-Note that rclone does not encrypt
-.IP \[bu] 2
-file length \- this can be calculated within 16 bytes
-.IP \[bu] 2
-modification time \- used for syncing
-.SS Specifying the remote
-.PP
-In normal use, make sure the remote has a \f[C]:\f[R] in.
-If you specify the remote without a \f[C]:\f[R] then rclone will use a
-local directory of that name.
-So if you use a remote of \f[C]/path/to/secret/files\f[R] then rclone
-will encrypt stuff to that directory.
-If you use a remote of \f[C]name\f[R] then rclone will put files in a
-directory called \f[C]name\f[R] in the current directory.
-.PP
-If you specify the remote as \f[C]remote:path/to/dir\f[R] then rclone
-will store encrypted files in \f[C]path/to/dir\f[R] on the remote.
-If you are using file name encryption, then when you save files to
-\f[C]secret:subdir/subfile\f[R] this will store them in the unencrypted
-path \f[C]path/to/dir\f[R] but the \f[C]subdir/subpath\f[R] bit will be
-encrypted.
-.PP
-Note that unless you want encrypted bucket names (which are difficult to
-manage because you won\[cq]t know what directory they represent in web
-interfaces etc), you should probably specify a bucket, eg
-\f[C]remote:secretbucket\f[R] when using bucket based remotes such as
-S3, Swift, Hubic, B2, GCS.
-.SS Example
-.PP
-To test I made a little directory of files using \[lq]standard\[rq] file
-name encryption.
-.IP
-.nf
-\f[C]
-plaintext/
-\[u251C]\[u2500]\[u2500] file0.txt
-\[u251C]\[u2500]\[u2500] file1.txt
-\[u2514]\[u2500]\[u2500] subdir
-    \[u251C]\[u2500]\[u2500] file2.txt
-    \[u251C]\[u2500]\[u2500] file3.txt
-    \[u2514]\[u2500]\[u2500] subsubdir
-        \[u2514]\[u2500]\[u2500] file4.txt
-\f[R]
-.fi
-.PP
-Copy these to the remote and list them back
-.IP
-.nf
-\f[C]
-$ 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
-\f[R]
-.fi
-.PP
-Now see what that looked like when encrypted
-.IP
-.nf
-\f[C]
-$ rclone \-q ls remote:path
-       55 hagjclgavj2mbiqm6u6cnjjqcg
-       54 v05749mltvv1tf4onltun46gls
-       57 86vhrsv86mpbtd3a0akjuqslj8/dlj7fkq4kdq72emafg7a7s41uo
-       58 86vhrsv86mpbtd3a0akjuqslj8/7uu829995du6o42n32otfhjqp4/b9pausrfansjth5ob3jkdqd4lc
-       56 86vhrsv86mpbtd3a0akjuqslj8/8njh1sk437gttmep3p70g81aps
-\f[R]
-.fi
-.PP
-Note that this retains the directory structure which means you can do
-this
-.IP
-.nf
-\f[C]
-$ rclone \-q ls secret:subdir
-        8 file2.txt
-        9 file3.txt
-       10 subsubdir/file4.txt
-\f[R]
-.fi
-.PP
-If don\[cq]t use file name encryption then the remote will look like
-this \- note the \f[C].bin\f[R] extensions added to prevent the cloud
-provider attempting to interpret the data.
-.IP
-.nf
-\f[C]
-$ 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
-\f[R]
-.fi
-.SS File name encryption modes
-.PP
-Here are some of the features of the file name encryption modes
-.PP
-Off
-.IP \[bu] 2
-doesn\[cq]t hide file names or directory structure
-.IP \[bu] 2
-allows for longer file names (\[ti]246 characters)
-.IP \[bu] 2
-can use sub paths and copy single files
-.PP
-Standard
-.IP \[bu] 2
-file names encrypted
-.IP \[bu] 2
-file names can\[cq]t be as long (\[ti]143 characters)
-.IP \[bu] 2
-can use sub paths and copy single files
-.IP \[bu] 2
-directory structure visible
-.IP \[bu] 2
-identical files names will have identical uploaded names
-.IP \[bu] 2
-can use shortcuts to shorten the directory recursion
-.PP
-Obfuscation
-.PP
-This is a simple \[lq]rotate\[rq] of the filename, with each file having
-a rot distance based on the filename.
-We store the distance at the beginning of the filename.
-So a file called \[lq]hello\[rq] may become \[lq]53.jgnnq\[rq].
-.PP
-This is not a strong encryption of filenames, but it may stop automated
-scanning tools from picking up on filename patterns.
-As such it\[cq]s an intermediate between \[lq]off\[rq] and
-\[lq]standard\[rq].
-The advantage is that it allows for longer path segment names.
-.PP
-There is a possibility with some unicode based filenames that the
-obfuscation is weak and may map lower case characters to upper case
-equivalents.
-You can not rely on this for strong protection.
-.IP \[bu] 2
-file names very lightly obfuscated
-.IP \[bu] 2
-file names can be longer than standard encryption
-.IP \[bu] 2
-can use sub paths and copy single files
-.IP \[bu] 2
-directory structure visible
-.IP \[bu] 2
-identical files names will have identical uploaded names
-.PP
-Cloud storage systems have various limits on file name length and total
-path length which you are more likely to hit using \[lq]Standard\[rq]
-file name encryption.
-If you keep your file names to below 156 characters in length then you
-should be OK on all providers.
-.PP
-There may be an even more secure file name encryption mode in the future
-which will address the long file name problem.
-.SS Directory name encryption
-.PP
-Crypt offers the option of encrypting dir names or leaving them intact.
-There are two options:
-.PP
-True
-.PP
-Encrypts the whole file path including directory names Example:
-\f[C]1/12/123.txt\f[R] is encrypted to
-\f[C]p0e52nreeaj0a5ea7s64m4j72s/l42g6771hnv3an9cgc8cr2n1ng/qgm4avr35m5loi1th53ato71v0\f[R]
-.PP
-False
-.PP
-Only encrypts file names, skips directory names Example:
-\f[C]1/12/123.txt\f[R] is encrypted to
-\f[C]1/12/qgm4avr35m5loi1th53ato71v0\f[R]
-.SS Modified time and hashes
-.PP
-Crypt stores modification times using the underlying remote so support
-depends on that.
-.PP
-Hashes are not stored for crypt.
-However the data integrity is protected by an extremely strong crypto
-authenticator.
-.PP
-Note that you should use the \f[C]rclone cryptcheck\f[R] command to
-check the integrity of a crypted remote instead of
-\f[C]rclone check\f[R] which can\[cq]t check the checksums properly.
-.SS Standard Options
-.PP
-Here are the standard options specific to crypt (Encrypt/Decrypt a
-remote).
-.SS \[en]crypt\-remote
-.PP
-Remote to encrypt/decrypt.
-Normally should contain a `:' and a path, eg
-\[lq]myremote:path/to/dir\[rq], \[lq]myremote:bucket\[rq] or maybe
-\[lq]myremote:\[rq] (not recommended).
-.IP \[bu] 2
-Config: remote
-.IP \[bu] 2
-Env Var: RCLONE_CRYPT_REMOTE
-.IP \[bu] 2
-Type: string
-.IP \[bu] 2
-Default: \[dq]\[dq]
-.SS \[en]crypt\-filename\-encryption
-.PP
-How to encrypt the filenames.
-.IP \[bu] 2
-Config: filename_encryption
-.IP \[bu] 2
-Env Var: RCLONE_CRYPT_FILENAME_ENCRYPTION
-.IP \[bu] 2
-Type: string
-.IP \[bu] 2
-Default: \[lq]standard\[rq]
-.IP \[bu] 2
-Examples:
-.RS 2
-.IP \[bu] 2
-\[lq]standard\[rq]
-.RS 2
-.IP \[bu] 2
-Encrypt the filenames see the docs for the details.
-.RE
-.IP \[bu] 2
-\[lq]obfuscate\[rq]
-.RS 2
-.IP \[bu] 2
-Very simple filename obfuscation.
-.RE
-.IP \[bu] 2
-\[lq]off\[rq]
-.RS 2
-.IP \[bu] 2
-Don\[cq]t encrypt the file names.
-Adds a \[lq].bin\[rq] extension only.
-.RE
-.RE
-.SS \[en]crypt\-directory\-name\-encryption
-.PP
-Option to either encrypt directory names or leave them intact.
-.PP
-NB If filename_encryption is \[lq]off\[rq] then this option will do
-nothing.
-.IP \[bu] 2
-Config: directory_name_encryption
-.IP \[bu] 2
-Env Var: RCLONE_CRYPT_DIRECTORY_NAME_ENCRYPTION
-.IP \[bu] 2
-Type: bool
-.IP \[bu] 2
-Default: true
-.IP \[bu] 2
-Examples:
-.RS 2
-.IP \[bu] 2
-\[lq]true\[rq]
-.RS 2
-.IP \[bu] 2
-Encrypt directory names.
-.RE
-.IP \[bu] 2
-\[lq]false\[rq]
-.RS 2
-.IP \[bu] 2
-Don\[cq]t encrypt directory names, leave them intact.
-.RE
-.RE
-.SS \[en]crypt\-password
-.PP
-Password or pass phrase for encryption.
-.IP \[bu] 2
-Config: password
-.IP \[bu] 2
-Env Var: RCLONE_CRYPT_PASSWORD
-.IP \[bu] 2
-Type: string
-.IP \[bu] 2
-Default: \[dq]\[dq]
-.SS \[en]crypt\-password2
-.PP
-Password or pass phrase for salt.
-Optional but recommended.
-Should be different to the previous password.
-.IP \[bu] 2
-Config: password2
-.IP \[bu] 2
-Env Var: RCLONE_CRYPT_PASSWORD2
-.IP \[bu] 2
-Type: string
-.IP \[bu] 2
-Default: \[dq]\[dq]
-.SS Advanced Options
-.PP
-Here are the advanced options specific to crypt (Encrypt/Decrypt a
-remote).
-.SS \[en]crypt\-show\-mapping
-.PP
+
+**NB** Input to this must be obscured \- see [rclone obscure](https://rclone.org/commands/rclone_obscure/).
+
+\- Config:      password2
+\- Env Var:     RCLONE_CRYPT_PASSWORD2
+\- Type:        string
+\- Default:     \[dq]\[dq]
+
+### Advanced Options
+
+Here are the advanced options specific to crypt (Encrypt/Decrypt a remote).
+
+#### \-\-crypt\-server\-side\-across\-configs
+
+Allow server side operations (eg copy) to work across different crypt configs.
+
+Normally this option is not what you want, but if you have two crypts
+pointing to the same backend you can use it.
+
+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.
+
+\- Config:      server_side_across_configs
+\- Env Var:     RCLONE_CRYPT_SERVER_SIDE_ACROSS_CONFIGS
+\- Type:        bool
+\- Default:     false
+
+#### \-\-crypt\-show\-mapping
+
 For all files listed show how the names encrypt.
-.PP
-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.
-.PP
+
+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.
+
 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.
-.IP \[bu] 2
-Config: show_mapping
-.IP \[bu] 2
-Env Var: RCLONE_CRYPT_SHOW_MAPPING
-.IP \[bu] 2
-Type: bool
-.IP \[bu] 2
-Default: false
-.SS Backend commands
-.PP
+
+\- Config:      show_mapping
+\- Env Var:     RCLONE_CRYPT_SHOW_MAPPING
+\- Type:        bool
+\- Default:     false
+
+### Backend commands
+
 Here are the commands specific to the crypt backend.
-.PP
+
 Run them with
-.IP
-.nf
-\f[C]
-rclone backend COMMAND remote:
-\f[R]
-.fi
-.PP
+
+    rclone backend COMMAND remote:
+
 The help below will explain what arguments each command takes.
-.PP
-See the \[lq]rclone backend\[rq]
-command (https://rclone.org/commands/rclone_backend/) for more info on
-how to pass options and arguments.
-.PP
+
+See [the \[dq]rclone backend\[dq] command](https://rclone.org/commands/rclone_backend/) for more
+info on how to pass options and arguments.
+
 These can be run on a running backend using the rc command
-backend/command (https://rclone.org/rc/#backend/command).
-.SS encode
-.PP
+[backend/command](https://rclone.org/rc/#backend/command).
+
+#### encode
+
 Encode the given filename(s)
-.IP
-.nf
-\f[C]
-rclone backend encode remote: [options] [<arguments>+]
-\f[R]
-.fi
-.PP
+
+    rclone backend encode remote: [options] [<arguments>+]
+
 This encodes the filenames given as arguments returning a list of
 strings of the encoded results.
-.PP
+
 Usage Example:
-.IP
-.nf
-\f[C]
-rclone backend encode crypt: file1 [file2...]
-rclone rc backend/command command=encode fs=crypt: file1 [file2...]
-\f[R]
-.fi
-.SS decode
-.PP
+
+    rclone backend encode crypt: file1 [file2...]
+    rclone rc backend/command command=encode fs=crypt: file1 [file2...]
+
+
+#### decode
+
 Decode the given filename(s)
-.IP
-.nf
-\f[C]
-rclone backend decode remote: [options] [<arguments>+]
-\f[R]
-.fi
-.PP
+
+    rclone backend decode remote: [options] [<arguments>+]
+
 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.
-.PP
+strings of the decoded results. It will return an error if any of the
+inputs are invalid.
+
 Usage Example:
-.IP
-.nf
-\f[C]
-rclone backend decode crypt: encryptedfile1 [encryptedfile2...]
-rclone rc backend/command command=decode fs=crypt: encryptedfile1 [encryptedfile2...]
-\f[R]
-.fi
-.SS Backing up a crypted remote
-.PP
+
+    rclone backend decode crypt: encryptedfile1 [encryptedfile2...]
+    rclone rc backend/command command=decode fs=crypt: encryptedfile1 [encryptedfile2...]
+
+
+
+
+## Backing up a crypted remote ##
+
 If you wish to backup a crypted remote, it is recommended that you use
-\f[C]rclone sync\f[R] on the encrypted files, and make sure the
-passwords are the same in the new encrypted remote.
-.PP
+\[ga]rclone sync\[ga] on the encrypted files, and make sure the passwords are
+the same in the new encrypted remote.
+
 This will have the following advantages
-.IP \[bu] 2
-\f[C]rclone sync\f[R] will check the checksums while copying
-.IP \[bu] 2
-you can use \f[C]rclone check\f[R] between the encrypted remotes
-.IP \[bu] 2
-you don\[cq]t decrypt and encrypt unnecessarily
-.PP
-For example, let\[cq]s say you have your original remote at
-\f[C]remote:\f[R] with the encrypted version at \f[C]eremote:\f[R] with
-path \f[C]remote:crypt\f[R].
-You would then set up the new remote \f[C]remote2:\f[R] and then the
-encrypted version \f[C]eremote2:\f[R] with path \f[C]remote2:crypt\f[R]
-using the same passwords as \f[C]eremote:\f[R].
-.PP
+
+  * \[ga]rclone sync\[ga] will check the checksums while copying
+  * you can use \[ga]rclone check\[ga] between the encrypted remotes
+  * you don\[aq]t decrypt and encrypt unnecessarily
+
+For example, let\[aq]s say you have your original remote at \[ga]remote:\[ga] with
+the encrypted version at \[ga]eremote:\[ga] with path \[ga]remote:crypt\[ga].  You
+would then set up the new remote \[ga]remote2:\[ga] and then the encrypted
+version \[ga]eremote2:\[ga] with path \[ga]remote2:crypt\[ga] using the same passwords
+as \[ga]eremote:\[ga].
+
 To sync the two remotes you would do
-.IP
-.nf
-\f[C]
-rclone sync remote:crypt remote2:crypt
-\f[R]
-.fi
-.PP
+
+    rclone sync \-i remote:crypt remote2:crypt
+
 And to check the integrity you would do
-.IP
-.nf
-\f[C]
-rclone check remote:crypt remote2:crypt
-\f[R]
-.fi
-.SS File formats
-.SS File encryption
-.PP
-Files are encrypted 1:1 source file to destination object.
-The file has a header and is divided into chunks.
-.SS Header
-.IP \[bu] 2
-8 bytes magic string \f[C]RCLONE\[rs]x00\[rs]x00\f[R]
-.IP \[bu] 2
-24 bytes Nonce (IV)
-.PP
-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 re\-used is minuscule.
-If you wrote an exabyte of data (10\[S1]\[u2078] bytes) you would have a
-probability of approximately 2\[tmu]10\[u207B]\[S3]\[S2] of re\-using a
-nonce.
-.SS Chunk
-.PP
-Each chunk will contain 64kB 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.
-.PP
+
+    rclone check remote:crypt remote2:crypt
+
+## File formats ##
+
+### File encryption ###
+
+Files are encrypted 1:1 source file to destination object.  The file
+has a header and is divided into chunks.
+
+#### Header ####
+
+  * 8 bytes magic string \[ga]RCLONE\[rs]x00\[rs]x00\[ga]
+  * 24 bytes Nonce (IV)
+
+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 re\-used is minuscule.  If you wrote an
+exabyte of data (10\[S1]\[u2078] bytes) you would have a probability of
+approximately 2\[tmu]10\[u207B]\[S3]\[S2] of re\-using a nonce.
+
+#### Chunk ####
+
+Each chunk will contain 64kB 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.
+
 Each chunk contains:
-.IP \[bu] 2
-16 Bytes of Poly1305 authenticator
-.IP \[bu] 2
-1 \- 65536 bytes XSalsa20 encrypted data
-.PP
+
+  * 16 Bytes of Poly1305 authenticator
+  * 1 \- 65536 bytes XSalsa20 encrypted data
+
 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\[cq]t be too
-big.
-.PP
+off due to cache effects above this).  Note that these chunks are
+buffered in memory so they can\[aq]t be too big.
+
 This uses a 32 byte (256 bit key) key derived from the user password.
-.SS Examples
-.PP
+
+#### Examples ####
+
 1 byte file will encrypt to
-.IP \[bu] 2
-32 bytes header
-.IP \[bu] 2
-17 bytes data chunk
-.PP
+
+  * 32 bytes header
+  * 17 bytes data chunk
+
 49 bytes total
-.PP
+
 1MB (1048576 bytes) file will encrypt to
-.IP \[bu] 2
-32 bytes header
-.IP \[bu] 2
-16 chunks of 65568 bytes
-.PP
-1049120 bytes total (a 0.05% overhead).
-This is the overhead for big files.
-.SS Name encryption
-.PP
+
+  * 32 bytes header
+  * 16 chunks of 65568 bytes
+
+1049120 bytes total (a 0.05% overhead).  This is the overhead for big
+files.
+
+### Name encryption ###
+
 File names are encrypted segment by segment \- the path is broken up
-into \f[C]/\f[R] separated strings and these are encrypted individually.
-.PP
-File segments are padded using PKCS#7 to a multiple of 16 bytes before
-encryption.
-.PP
-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 \[lq]A Parallelizable Enciphering Mode\[rq] by Halevi and
-Rogaway.
-.PP
+into \[ga]/\[ga] separated strings and these are encrypted individually.
+
+File segments are padded using PKCS#7 to a multiple of 16 bytes
+before encryption.
+
+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 \[dq]A Parallelizable Enciphering Mode\[dq] by Halevi and Rogaway.
+
 This makes for deterministic encryption which is what we want \- the
-same filename must encrypt to the same thing otherwise we can\[cq]t find
+same filename must encrypt to the same thing otherwise we can\[aq]t find
 it on the cloud storage system.
-.PP
+
 This means that
-.IP \[bu] 2
-filenames with the same name will encrypt the same
-.IP \[bu] 2
-filenames which start the same won\[cq]t have a common prefix
-.PP
+
+  * filenames with the same name will encrypt the same
+  * filenames which start the same won\[aq]t have a common prefix
+
 This uses a 32 byte key (256 bits) and a 16 byte (128 bits) IV both of
 which are derived from the user password.
-.PP
+
 After encryption they are written out using a modified version of
-standard \f[C]base32\f[R] encoding as described in RFC4648.
-The standard encoding is modified in two ways:
-.IP \[bu] 2
-it becomes lower case (no\-one likes upper case filenames!)
-.IP \[bu] 2
-we strip the padding character \f[C]=\f[R]
-.PP
-\f[C]base32\f[R] is used rather than the more efficient \f[C]base64\f[R]
-so rclone can be used on case insensitive remotes (eg Windows, Amazon
-Drive).
-.SS Key derivation
-.PP
-Rclone uses \f[C]scrypt\f[R] with parameters \f[C]N=16384, r=8, p=1\f[R]
-with an optional user supplied salt (password2) to derive the 32+32+16 =
-80 bytes of key material required.
-If the user doesn\[cq]t supply a salt then rclone uses an internal one.
-.PP
-\f[C]scrypt\f[R] makes it impractical to mount a dictionary attack on
-rclone encrypted data.
-For full protection against this you should always use a salt.
-.SS Dropbox
-.PP
-Paths are specified as \f[C]remote:path\f[R]
-.PP
+standard \[ga]base32\[ga] encoding as described in RFC4648.  The standard
+encoding is modified in two ways:
+
+  * it becomes lower case (no\-one likes upper case filenames!)
+  * we strip the padding character \[ga]=\[ga]
+
+\[ga]base32\[ga] is used rather than the more efficient \[ga]base64\[ga] so rclone can be
+used on case insensitive remotes (eg Windows, Amazon Drive).
+
+### Key derivation ###
+
+Rclone uses \[ga]scrypt\[ga] with parameters \[ga]N=16384, r=8, p=1\[ga] with an
+optional user supplied salt (password2) to derive the 32+32+16 = 80
+bytes of key material required.  If the user doesn\[aq]t supply a salt
+then rclone uses an internal one.
+
+\[ga]scrypt\[ga] makes it impractical to mount a dictionary attack on rclone
+encrypted data.  For full protection against this you should always use
+a salt.
+
+ Dropbox
+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
+
+Paths are specified as \[ga]remote:path\[ga]
+
 Dropbox paths may be as deep as required, eg
-\f[C]remote:directory/subdirectory\f[R].
-.PP
+\[ga]remote:directory/subdirectory\[ga].
+
 The initial setup for dropbox involves getting a token from Dropbox
-which you need to do in your browser.
-\f[C]rclone config\f[R] walks you through it.
-.PP
-Here is an example of how to make a remote called \f[C]remote\f[R].
-First run:
-.IP
-.nf
-\f[C]
- rclone config
+which you need to do in your browser.  \[ga]rclone config\[ga] walks you
+through it.
+
+Here is an example of how to make a remote called \[ga]remote\[ga].  First run:
+
+     rclone config
+
+This will guide you through an interactive setup process:
 \f[R]
 .fi
-.PP
-This will guide you through an interactive setup process:
-.IP
-.nf
-\f[C]
-n) New remote
-d) Delete remote
-q) Quit config
-e/n/d/q> n
-name> remote
-Type of storage to configure.
-Choose a number from below, or type in your own value
-[snip]
-XX / Dropbox
-   \[rs] \[dq]dropbox\[dq]
-[snip]
-Storage> dropbox
-Dropbox App Key \- leave blank normally.
-app_key>
-Dropbox App Secret \- leave blank normally.
-app_secret>
-Remote config
-Please visit:
+.IP "n)" 3
+New remote
+.IP "o)" 3
+Delete remote
+.IP "p)" 3
+Quit config e/n/d/q> n name> remote Type of storage to configure.
+Choose a number from below, or type in your own value [snip] XX /
+Dropbox \ \[dq]dropbox\[dq] [snip] Storage> dropbox Dropbox App Key \-
+leave blank normally.
+app_key> Dropbox App Secret \- leave blank normally.
+app_secret> Remote config Please visit:
 https://www.dropbox.com/1/oauth2/authorize?client_id=XXXXXXXXXXXXXXX&response_type=code
 Enter the code: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX_XXXXXXXXXX
-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
-[remote]
-app_key =
-app_secret =
+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\- [remote] app_key = app_secret =
 token = XXXXXXXXXXXXXXXXXXXXXXXXXXXXX_XXXX_XXXXXXXXXXXXXXXXXXXXXXXXXXXXX
 \-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
-y) Yes this is OK
-e) Edit this remote
-d) Delete this remote
-y/e/d> y
-\f[R]
-.fi
-.PP
+.IP "q)" 3
+Yes this is OK
+.IP "r)" 3
+Edit this remote
+.IP "s)" 3
+Delete this remote y/e/d> y
+.IP
+.nf
+\f[C]
+
 You can then use it like this,
-.PP
+
 List directories in top level of your dropbox
-.IP
-.nf
-\f[C]
-rclone lsd remote:
-\f[R]
-.fi
-.PP
+
+    rclone lsd remote:
+
 List all the files in your dropbox
-.IP
-.nf
-\f[C]
-rclone ls remote:
-\f[R]
-.fi
-.PP
+
+    rclone ls remote:
+
 To copy a local directory to a dropbox directory called backup
-.IP
-.nf
-\f[C]
-rclone copy /home/source remote:backup
-\f[R]
-.fi
-.SS Dropbox for business
-.PP
+
+    rclone copy /home/source remote:backup
+
+### Dropbox for business ###
+
 Rclone supports Dropbox for business and Team Folders.
-.PP
-When using Dropbox for business \f[C]remote:\f[R] and
-\f[C]remote:path/to/file\f[R] will refer to your personal folder.
-.PP
-If you wish to see Team Folders you must use a leading \f[C]/\f[R] in
-the path, so \f[C]rclone lsd remote:/\f[R] will refer to the root and
-show you all Team Folders and your User Folder.
-.PP
-You can then use team folders like this \f[C]remote:/TeamFolder\f[R] and
-\f[C]remote:/TeamFolder/path/to/file\f[R].
-.PP
-A leading \f[C]/\f[R] for a Dropbox personal account will do nothing,
-but it will take an extra HTTP transaction so it should be avoided.
-.SS Modified time and Hashes
-.PP
-Dropbox supports modified times, but the only way to set a modification
-time is to re\-upload the file.
-.PP
+
+When using Dropbox for business \[ga]remote:\[ga] and \[ga]remote:path/to/file\[ga]
+will refer to your personal folder.
+
+If you wish to see Team Folders you must use a leading \[ga]/\[ga] in the
+path, so \[ga]rclone lsd remote:/\[ga] will refer to the root and show you all
+Team Folders and your User Folder.
+
+You can then use team folders like this \[ga]remote:/TeamFolder\[ga] and
+\[ga]remote:/TeamFolder/path/to/file\[ga].
+
+A leading \[ga]/\[ga] for a Dropbox personal account will do nothing, but it
+will take an extra HTTP transaction so it should be avoided.
+
+### Modified time and Hashes ###
+
+Dropbox supports modified times, but the only way to set a
+modification time is to re\-upload the file.
+
 This means that if you uploaded your data with an older version of
-rclone which didn\[cq]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\[cq]t want this to happen use \f[C]\-\-size\-only\f[R] or
-\f[C]\-\-checksum\f[R] flag to stop it.
-.PP
-Dropbox supports its own hash
-type (https://www.dropbox.com/developers/reference/content-hash) which
+rclone which didn\[aq]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\[aq]t want this to happen use \[ga]\-\-size\-only\[ga] or \[ga]\-\-checksum\[ga] flag
+to stop it.
+
+Dropbox supports [its own hash
+type](https://www.dropbox.com/developers/reference/content\-hash) which
 is checked for all transfers.
-.SS Restricted filename characters
-.PP
-.TS
-tab(@);
-l c c.
-T{
-Character
-T}@T{
-Value
-T}@T{
-Replacement
-T}
-_
-T{
-NUL
-T}@T{
-0x00
-T}@T{
-\[u2400]
-T}
-T{
-/
-T}@T{
-0x2F
-T}@T{
-\[uFF0F]
-T}
-T{
-DEL
-T}@T{
-0x7F
-T}@T{
-\[u2421]
-T}
-T{
-\[rs]
-T}@T{
-0x5C
-T}@T{
-\[uFF3C]
-T}
-.TE
-.PP
+
+#### Restricted filename characters
+
+| Character | Value | Replacement |
+| \-\-\-\-\-\-\-\-\- |:\-\-\-\-\-:|:\-\-\-\-\-\-\-\-\-\-\-:|
+| NUL       | 0x00  | \[u2400]           |
+| /         | 0x2F  | \[uFF0F]           |
+| DEL       | 0x7F  | \[u2421]           |
+| \[rs]         | 0x5C  | \[uFF3C]           |
+
 File names can also not end with the following characters.
 These only get replaced if they are the last character in the name:
-.PP
-.TS
-tab(@);
-l c c.
-T{
-Character
-T}@T{
-Value
-T}@T{
-Replacement
-T}
-_
-T{
-SP
-T}@T{
-0x20
-T}@T{
-\[u2420]
-T}
-.TE
-.PP
-Invalid UTF\-8 bytes will also be
-replaced (https://rclone.org/overview/#invalid-utf8), as they can\[cq]t
-be used in JSON strings.
-.SS Standard Options
-.PP
+
+| Character | Value | Replacement |
+| \-\-\-\-\-\-\-\-\- |:\-\-\-\-\-:|:\-\-\-\-\-\-\-\-\-\-\-:|
+| SP        | 0x20  | \[u2420]           |
+
+Invalid UTF\-8 bytes will also be [replaced](https://rclone.org/overview/#invalid\-utf8),
+as they can\[aq]t be used in JSON strings.
+
+
+### Standard Options
+
 Here are the standard options specific to dropbox (Dropbox).
-.SS \[en]dropbox\-client\-id
-.PP
-Dropbox App Client Id Leave blank normally.
-.IP \[bu] 2
-Config: client_id
-.IP \[bu] 2
-Env Var: RCLONE_DROPBOX_CLIENT_ID
-.IP \[bu] 2
-Type: string
-.IP \[bu] 2
-Default: \[dq]\[dq]
-.SS \[en]dropbox\-client\-secret
-.PP
-Dropbox App Client Secret Leave blank normally.
-.IP \[bu] 2
-Config: client_secret
-.IP \[bu] 2
-Env Var: RCLONE_DROPBOX_CLIENT_SECRET
-.IP \[bu] 2
-Type: string
-.IP \[bu] 2
-Default: \[dq]\[dq]
-.SS Advanced Options
-.PP
+
+#### \-\-dropbox\-client\-id
+
+OAuth Client Id
+Leave blank normally.
+
+\- Config:      client_id
+\- Env Var:     RCLONE_DROPBOX_CLIENT_ID
+\- Type:        string
+\- Default:     \[dq]\[dq]
+
+#### \-\-dropbox\-client\-secret
+
+OAuth Client Secret
+Leave blank normally.
+
+\- Config:      client_secret
+\- Env Var:     RCLONE_DROPBOX_CLIENT_SECRET
+\- Type:        string
+\- Default:     \[dq]\[dq]
+
+### Advanced Options
+
 Here are the advanced options specific to dropbox (Dropbox).
-.SS \[en]dropbox\-chunk\-size
-.PP
-Upload chunk size.
-(< 150M).
-.PP
+
+#### \-\-dropbox\-token
+
+OAuth Access Token as a JSON blob.
+
+\- Config:      token
+\- Env Var:     RCLONE_DROPBOX_TOKEN
+\- Type:        string
+\- Default:     \[dq]\[dq]
+
+#### \-\-dropbox\-auth\-url
+
+Auth server URL.
+Leave blank to use the provider defaults.
+
+\- Config:      auth_url
+\- Env Var:     RCLONE_DROPBOX_AUTH_URL
+\- Type:        string
+\- Default:     \[dq]\[dq]
+
+#### \-\-dropbox\-token\-url
+
+Token server url.
+Leave blank to use the provider defaults.
+
+\- Config:      token_url
+\- Env Var:     RCLONE_DROPBOX_TOKEN_URL
+\- Type:        string
+\- Default:     \[dq]\[dq]
+
+#### \-\-dropbox\-chunk\-size
+
+Upload chunk size. (< 150M).
+
 Any files larger than this will be uploaded in chunks of this size.
-.PP
+
 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
-128MB in tests) at the cost of using more memory.
-It can be set smaller if you are tight on memory.
-.IP \[bu] 2
-Config: chunk_size
-.IP \[bu] 2
-Env Var: RCLONE_DROPBOX_CHUNK_SIZE
-.IP \[bu] 2
-Type: SizeSuffix
-.IP \[bu] 2
-Default: 48M
-.SS \[en]dropbox\-impersonate
-.PP
+deal with retries.  Setting this larger will increase the speed
+slightly (at most 10% for 128MB in tests) at the cost of using more
+memory.  It can be set smaller if you are tight on memory.
+
+\- Config:      chunk_size
+\- Env Var:     RCLONE_DROPBOX_CHUNK_SIZE
+\- Type:        SizeSuffix
+\- Default:     48M
+
+#### \-\-dropbox\-impersonate
+
 Impersonate this user when using a business account.
-.IP \[bu] 2
-Config: impersonate
-.IP \[bu] 2
-Env Var: RCLONE_DROPBOX_IMPERSONATE
-.IP \[bu] 2
-Type: string
-.IP \[bu] 2
-Default: \[dq]\[dq]
-.SS \[en]dropbox\-encoding
-.PP
+
+\- Config:      impersonate
+\- Env Var:     RCLONE_DROPBOX_IMPERSONATE
+\- Type:        string
+\- Default:     \[dq]\[dq]
+
+#### \-\-dropbox\-encoding
+
 This sets the encoding for the backend.
-.PP
-See: the encoding section in the
-overview (https://rclone.org/overview/#encoding) for more info.
-.IP \[bu] 2
-Config: encoding
-.IP \[bu] 2
-Env Var: RCLONE_DROPBOX_ENCODING
-.IP \[bu] 2
-Type: MultiEncoder
-.IP \[bu] 2
-Default: Slash,BackSlash,Del,RightSpace,InvalidUtf8,Dot
-.SS Limitations
-.PP
-Note that Dropbox is case insensitive so you can\[cq]t have a file
-called \[lq]Hello.doc\[rq] and one called \[lq]hello.doc\[rq].
-.PP
-There are some file names such as \f[C]thumbs.db\f[R] which Dropbox
-can\[cq]t store.
-There is a full list of them in the \[lq]Ignored Files\[rq] section of
-this document (https://www.dropbox.com/en/help/145).
-Rclone will issue an error message
-\f[C]File name disallowed \- not uploading\f[R] if it attempts to upload
-one of those file names, but the sync won\[cq]t fail.
-.PP
-If you have more than 10,000 files in a directory then
-\f[C]rclone purge dropbox:dir\f[R] will return the error
-\f[C]Failed to purge: There are too many files involved in this operation\f[R].
-As a work\-around do an \f[C]rclone delete dropbox:dir\f[R] followed by
-an \f[C]rclone rmdir dropbox:dir\f[R].
-.SS Get your own Dropbox App ID
-.PP
-When you use rclone with Dropbox in its default configuration you are
-using rclone\[cq]s App ID.
-This is shared between all the rclone users.
-.PP
+
+See: the [encoding section in the overview](https://rclone.org/overview/#encoding) for more info.
+
+\- Config:      encoding
+\- Env Var:     RCLONE_DROPBOX_ENCODING
+\- Type:        MultiEncoder
+\- Default:     Slash,BackSlash,Del,RightSpace,InvalidUtf8,Dot
+
+
+
+### Limitations ###
+
+Note that Dropbox is case insensitive so you can\[aq]t have a file called
+\[dq]Hello.doc\[dq] and one called \[dq]hello.doc\[dq].
+
+There are some file names such as \[ga]thumbs.db\[ga] which Dropbox can\[aq]t
+store.  There is a full list of them in the [\[dq]Ignored Files\[dq] section
+of this document](https://www.dropbox.com/en/help/145).  Rclone will
+issue an error message \[ga]File name disallowed \- not uploading\[ga] if it
+attempts to upload one of those file names, but the sync won\[aq]t fail.
+
+Some errors may occur if you try to sync copyright\-protected files
+because Dropbox has its own [copyright detector](https://techcrunch.com/2014/03/30/how\-dropbox\-knows\-when\-youre\-sharing\-copyrighted\-stuff\-without\-actually\-looking\-at\-your\-stuff/) that
+prevents this sort of file being downloaded. This will return the error \[ga]ERROR :
+/path/to/your/file: Failed to copy: failed to open source object:
+path/restricted_content/.\[ga]
+
+If you have more than 10,000 files in a directory then \[ga]rclone purge
+dropbox:dir\[ga] will return the error \[ga]Failed to purge: There are too
+many files involved in this operation\[ga].  As a work\-around do an
+\[ga]rclone delete dropbox:dir\[ga] followed by an \[ga]rclone rmdir dropbox:dir\[ga].
+
+### Get your own Dropbox App ID ###
+
+When you use rclone with Dropbox in its default configuration you are using rclone\[aq]s App ID. This is shared between all the rclone users.
+
 Here is how to create your own Dropbox App ID for rclone:
-.IP "1." 3
-Log into the Dropbox App
-console (https://www.dropbox.com/developers/apps/create) with your
-Dropbox Account (It need not to be the same account as the Dropbox you
-want to access)
-.IP "2." 3
-Choose an API => Usually this should be \f[C]Dropbox API\f[R]
-.IP "3." 3
-Choose the type of access you want to use => \f[C]Full Dropbox\f[R] or
-\f[C]App Folder\f[R]
-.IP "4." 3
-Name your App.
-The app name is global, so you can\[cq]t use \f[C]rclone\f[R] for
-example
-.IP "5." 3
-Click the button \f[C]Create App\f[R]
-.IP "6." 3
-Fill \f[C]Redirect URIs\f[R] as \f[C]http://localhost:53682/\f[R]
-.IP "7." 3
-Find the \f[C]App key\f[R] and \f[C]App secret\f[R] Use these values in
-rclone config to add a new remote or edit an existing remote.
-.SS FTP
-.PP
-FTP is the File Transfer Protocol.
-FTP support is provided using the
-github.com/jlaffaye/ftp (https://godoc.org/github.com/jlaffaye/ftp)
+
+1. Log into the [Dropbox App console](https://www.dropbox.com/developers/apps/create) with your Dropbox Account (It need not
+to be the same account as the Dropbox you want to access)
+
+2. Choose an API => Usually this should be \[ga]Dropbox API\[ga]
+
+3. Choose the type of access you want to use => \[ga]Full Dropbox\[ga] or \[ga]App Folder\[ga]
+
+4. Name your App. The app name is global, so you can\[aq]t use \[ga]rclone\[ga] for example
+
+5. Click the button \[ga]Create App\[ga]
+
+5. Fill \[ga]Redirect URIs\[ga] as \[ga]http://localhost:53682/\[ga]
+
+6. Find the \[ga]App key\[ga] and \[ga]App secret\[ga] Use these values in rclone config to add a new remote or edit an existing remote.
+
+ FTP
+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
+
+FTP is the File Transfer Protocol. FTP support is provided using the
+[github.com/jlaffaye/ftp](https://godoc.org/github.com/jlaffaye/ftp)
 package.
-.PP
-Here is an example of making an FTP configuration.
-First run
-.IP
-.nf
-\f[C]
-rclone config
+
+Paths are specified as \[ga]remote:path\[ga]. If the path does not begin with
+a \[ga]/\[ga] it is relative to the home directory of the user.  An empty path
+\[ga]remote:\[ga] refers to the user\[aq]s home directory.
+
+Here is an example of making an FTP configuration.  First run
+
+    rclone config
+
+This will guide you through an interactive setup process. An FTP remote only
+needs a host together with and a username and a password. With anonymous FTP
+server, you will need to use \[ga]anonymous\[ga] as username and your email address as
+the password.
 \f[R]
 .fi
 .PP
-This will guide you through an interactive setup process.
-An FTP remote only needs a host together with and a username and a
-password.
-With anonymous FTP server, you will need to use \f[C]anonymous\f[R] as
-username and your email address as the password.
+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> n
+name> remote Type of storage to configure.
+Enter a string value.
+Press Enter for the default (\[dq]\[dq]).
+Choose a number from below, or type in your own value [snip] XX / FTP
+Connection \ \[dq]ftp\[dq] [snip] Storage> ftp ** See help for ftp
+backend at: https://rclone.org/ftp/ **
+.PP
+FTP host to connect to Enter a string value.
+Press Enter for the default (\[dq]\[dq]).
+Choose a number from below, or type in your own value 1 / Connect to
+ftp.example.com \ \[dq]ftp.example.com\[dq] host> ftp.example.com FTP
+username, leave blank for current username, ncw Enter a string value.
+Press Enter for the default (\[dq]\[dq]).
+user> FTP port, leave blank to use default (21) Enter a string value.
+Press Enter for the default (\[dq]\[dq]).
+port> FTP password y) Yes type in my own password g) Generate random
+password y/g> 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 (\[dq]false\[dq]).
+tls> Use FTP over TLS (Explicit) Enter a boolean value (true or false).
+Press Enter for the default (\[dq]false\[dq]).
+explicit_tls> Remote config \-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
+[remote] type = ftp host = ftp.example.com pass = *** ENCRYPTED ***
+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\- y) Yes this is OK e) Edit this
+remote d) Delete this remote y/e/d> y
 .IP
 .nf
 \f[C]
-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> n
-name> remote
-Type of storage to configure.
-Enter a string value. Press Enter for the default (\[dq]\[dq]).
-Choose a number from below, or type in your own value
-[snip]
-XX / FTP Connection
-   \[rs] \[dq]ftp\[dq]
-[snip]
-Storage> ftp
-** See help for ftp backend at: https://rclone.org/ftp/ **
+
+This remote is called \[ga]remote\[ga] and can now be used like this
+
+See all directories in the home directory
+
+    rclone lsd remote:
+
+Make a new directory
+
+    rclone mkdir remote:path/to/directory
+
+List the contents of a directory
+
+    rclone ls remote:path/to/directory
+
+Sync \[ga]/home/local/directory\[ga] to the remote directory, deleting any
+excess files in the directory.
+
+    rclone sync \-i /home/local/directory remote:directory
+
+### Modified time ###
+
+FTP does not support modified times.  Any times you see on the server
+will be time of upload.
+
+### Checksums ###
+
+FTP does not support any checksums.
+
+### Usage without a config file ###
+
+An example how to use the ftp remote without a config file:
+
+    rclone lsf :ftp: \-\-ftp\-host=speedtest.tele2.net \-\-ftp\-user=anonymous \-\-ftp\-pass=\[ga]rclone obscure dummy\[ga]
+
+#### Restricted filename characters
+
+In addition to the [default restricted characters set](https://rclone.org/overview/#restricted\-characters)
+the following characters are also replaced:
+
+File names can also not end with the following characters.
+These only get replaced if they are the last character in the name:
+
+| Character | Value | Replacement |
+| \-\-\-\-\-\-\-\-\- |:\-\-\-\-\-:|:\-\-\-\-\-\-\-\-\-\-\-:|
+| SP        | 0x20  | \[u2420]           |
+
+Note that not all FTP servers can have all characters in file names, for example:
+
+| FTP Server| Forbidden characters |
+| \-\-\-\-\-\-\-\-\- |:\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-:|
+| proftpd   | \[ga]*\[ga]                  |
+| pureftpd  | \[ga]\[rs] [ ]\[ga]              |
+
+### Implicit TLS ###
+
+FTP supports implicit FTP over TLS servers (FTPS). This has to be enabled
+in the config for the remote. The default FTPS port is \[ga]990\[ga] so the
+port will likely have to be explicitly set in the config for the remote.
+
+
+### Standard Options
+
+Here are the standard options specific to ftp (FTP Connection).
+
+#### \-\-ftp\-host
 
 FTP host to connect to
-Enter a string value. Press Enter for the default (\[dq]\[dq]).
-Choose a number from below, or type in your own value
- 1 / Connect to ftp.example.com
-   \[rs] \[dq]ftp.example.com\[dq]
-host> ftp.example.com
-FTP username, leave blank for current username, ncw
-Enter a string value. Press Enter for the default (\[dq]\[dq]).
-user> 
-FTP port, leave blank to use default (21)
-Enter a string value. Press Enter for the default (\[dq]\[dq]).
-port> 
-FTP password
-y) Yes type in my own password
-g) Generate random password
-y/g> 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 (\[dq]false\[dq]).
-tls> 
-Remote config
-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
-[remote]
-type = ftp
-host = ftp.example.com
-pass = *** ENCRYPTED ***
-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
-y) Yes this is OK
-e) Edit this remote
-d) Delete this remote
-y/e/d> y
-\f[R]
-.fi
-.PP
-This remote is called \f[C]remote\f[R] and can now be used like this
-.PP
-See all directories in the home directory
-.IP
-.nf
-\f[C]
-rclone lsd remote:
-\f[R]
-.fi
-.PP
-Make a new directory
-.IP
-.nf
-\f[C]
-rclone mkdir remote:path/to/directory
-\f[R]
-.fi
-.PP
-List the contents of a directory
-.IP
-.nf
-\f[C]
-rclone ls remote:path/to/directory
-\f[R]
-.fi
-.PP
-Sync \f[C]/home/local/directory\f[R] to the remote directory, deleting
-any excess files in the directory.
-.IP
-.nf
-\f[C]
-rclone sync /home/local/directory remote:directory
-\f[R]
-.fi
-.SS Modified time
-.PP
-FTP does not support modified times.
-Any times you see on the server will be time of upload.
-.SS Checksums
-.PP
-FTP does not support any checksums.
-.SS Usage without a config file
-.PP
-An example how to use the ftp remote without a config file:
-.IP
-.nf
-\f[C]
-rclone lsf :ftp: \-\-ftp\-host=speedtest.tele2.net \-\-ftp\-user=anonymous \-\-ftp\-pass=\[ga]rclone obscure dummy\[ga]
-\f[R]
-.fi
-.SS Restricted filename characters
-.PP
-In addition to the default restricted characters
-set (https://rclone.org/overview/#restricted-characters) the following
-characters are also replaced:
-.PP
-File names can also not end with the following characters.
-These only get replaced if they are the last character in the name:
-.PP
-.TS
-tab(@);
-l c c.
-T{
-Character
-T}@T{
-Value
-T}@T{
-Replacement
-T}
-_
-T{
-SP
-T}@T{
-0x20
-T}@T{
-\[u2420]
-T}
-.TE
-.PP
-Note that not all FTP servers can have all characters in file names, for
-example:
-.PP
-.TS
-tab(@);
-l c.
-T{
-FTP Server
-T}@T{
-Forbidden characters
-T}
-_
-T{
-proftpd
-T}@T{
-\f[C]*\f[R]
-T}
-T{
-pureftpd
-T}@T{
-\f[C]\[rs] [ ]\f[R]
-T}
-.TE
-.SS Implicit TLS
-.PP
-FTP supports implicit FTP over TLS servers (FTPS).
-This has to be enabled in the config for the remote.
-The default FTPS port is \f[C]990\f[R] so the port will likely have to
-be explicitly set in the config for the remote.
-.SS Standard Options
-.PP
-Here are the standard options specific to ftp (FTP Connection).
-.SS \[en]ftp\-host
-.PP
-FTP host to connect to
-.IP \[bu] 2
-Config: host
-.IP \[bu] 2
-Env Var: RCLONE_FTP_HOST
-.IP \[bu] 2
-Type: string
-.IP \[bu] 2
-Default: \[dq]\[dq]
-.IP \[bu] 2
-Examples:
-.RS 2
-.IP \[bu] 2
-\[lq]ftp.example.com\[rq]
-.RS 2
-.IP \[bu] 2
-Connect to ftp.example.com
-.RE
-.RE
-.SS \[en]ftp\-user
-.PP
+
+\- Config:      host
+\- Env Var:     RCLONE_FTP_HOST
+\- Type:        string
+\- Default:     \[dq]\[dq]
+\- Examples:
+    \- \[dq]ftp.example.com\[dq]
+        \- Connect to ftp.example.com
+
+#### \-\-ftp\-user
+
 FTP username, leave blank for current username, $USER
-.IP \[bu] 2
-Config: user
-.IP \[bu] 2
-Env Var: RCLONE_FTP_USER
-.IP \[bu] 2
-Type: string
-.IP \[bu] 2
-Default: \[dq]\[dq]
-.SS \[en]ftp\-port
-.PP
+
+\- Config:      user
+\- Env Var:     RCLONE_FTP_USER
+\- Type:        string
+\- Default:     \[dq]\[dq]
+
+#### \-\-ftp\-port
+
 FTP port, leave blank to use default (21)
-.IP \[bu] 2
-Config: port
-.IP \[bu] 2
-Env Var: RCLONE_FTP_PORT
-.IP \[bu] 2
-Type: string
-.IP \[bu] 2
-Default: \[dq]\[dq]
-.SS \[en]ftp\-pass
-.PP
+
+\- Config:      port
+\- Env Var:     RCLONE_FTP_PORT
+\- Type:        string
+\- Default:     \[dq]\[dq]
+
+#### \-\-ftp\-pass
+
 FTP password
-.IP \[bu] 2
-Config: pass
-.IP \[bu] 2
-Env Var: RCLONE_FTP_PASS
-.IP \[bu] 2
-Type: string
-.IP \[bu] 2
-Default: \[dq]\[dq]
-.SS \[en]ftp\-tls
-.PP
-Use FTP over TLS (Implicit)
-.IP \[bu] 2
-Config: tls
-.IP \[bu] 2
-Env Var: RCLONE_FTP_TLS
-.IP \[bu] 2
-Type: bool
-.IP \[bu] 2
-Default: false
-.SS Advanced Options
-.PP
+
+**NB** Input to this must be obscured \- see [rclone obscure](https://rclone.org/commands/rclone_obscure/).
+
+\- Config:      pass
+\- Env Var:     RCLONE_FTP_PASS
+\- Type:        string
+\- Default:     \[dq]\[dq]
+
+#### \-\-ftp\-tls
+
+Use FTPS over TLS (Implicit)
+When using implicit FTP over TLS the client will connect using TLS
+right from the start, which in turn breaks the compatibility with
+non\-TLS\-aware servers. This is usually served over port 990 rather
+than port 21. Cannot be used in combination with explicit FTP.
+
+\- Config:      tls
+\- Env Var:     RCLONE_FTP_TLS
+\- Type:        bool
+\- Default:     false
+
+#### \-\-ftp\-explicit\-tls
+
+Use FTP over TLS (Explicit)
+When using explicit FTP over TLS the client explicitly request
+security from the server in order to upgrade a plain text connection
+to an encrypted one. Cannot be used in combination with implicit FTP.
+
+\- Config:      explicit_tls
+\- Env Var:     RCLONE_FTP_EXPLICIT_TLS
+\- Type:        bool
+\- Default:     false
+
+### Advanced Options
+
 Here are the advanced options specific to ftp (FTP Connection).
-.SS \[en]ftp\-concurrency
-.PP
+
+#### \-\-ftp\-concurrency
+
 Maximum number of FTP simultaneous connections, 0 for unlimited
-.IP \[bu] 2
-Config: concurrency
-.IP \[bu] 2
-Env Var: RCLONE_FTP_CONCURRENCY
-.IP \[bu] 2
-Type: int
-.IP \[bu] 2
-Default: 0
-.SS \[en]ftp\-no\-check\-certificate
-.PP
+
+\- Config:      concurrency
+\- Env Var:     RCLONE_FTP_CONCURRENCY
+\- Type:        int
+\- Default:     0
+
+#### \-\-ftp\-no\-check\-certificate
+
 Do not verify the TLS certificate of the server
-.IP \[bu] 2
-Config: no_check_certificate
-.IP \[bu] 2
-Env Var: RCLONE_FTP_NO_CHECK_CERTIFICATE
-.IP \[bu] 2
-Type: bool
-.IP \[bu] 2
-Default: false
-.SS \[en]ftp\-disable\-epsv
-.PP
+
+\- Config:      no_check_certificate
+\- Env Var:     RCLONE_FTP_NO_CHECK_CERTIFICATE
+\- Type:        bool
+\- Default:     false
+
+#### \-\-ftp\-disable\-epsv
+
 Disable using EPSV even if server advertises support
-.IP \[bu] 2
-Config: disable_epsv
-.IP \[bu] 2
-Env Var: RCLONE_FTP_DISABLE_EPSV
-.IP \[bu] 2
-Type: bool
-.IP \[bu] 2
-Default: false
-.SS \[en]ftp\-encoding
-.PP
+
+\- Config:      disable_epsv
+\- Env Var:     RCLONE_FTP_DISABLE_EPSV
+\- Type:        bool
+\- Default:     false
+
+#### \-\-ftp\-encoding
+
 This sets the encoding for the backend.
-.PP
-See: the encoding section in the
-overview (https://rclone.org/overview/#encoding) for more info.
-.IP \[bu] 2
-Config: encoding
-.IP \[bu] 2
-Env Var: RCLONE_FTP_ENCODING
-.IP \[bu] 2
-Type: MultiEncoder
-.IP \[bu] 2
-Default: Slash,Del,Ctl,RightSpace,Dot
-.SS Limitations
-.PP
-Note that since FTP isn\[cq]t HTTP based the following flags don\[cq]t
-work with it: \f[C]\-\-dump\-headers\f[R], \f[C]\-\-dump\-bodies\f[R],
-\f[C]\-\-dump\-auth\f[R]
-.PP
-Note that \f[C]\-\-timeout\f[R] isn\[cq]t supported (but
-\f[C]\-\-contimeout\f[R] is).
-.PP
-Note that \f[C]\-\-bind\f[R] isn\[cq]t supported.
-.PP
-FTP could support server side move but doesn\[cq]t yet.
-.PP
-Note that the ftp backend does not support the \f[C]ftp_proxy\f[R]
-environment variable yet.
-.PP
-Note that while implicit FTP over TLS is supported, explicit FTP over
-TLS is not.
-.SS Google Cloud Storage
-.PP
-Paths are specified as \f[C]remote:bucket\f[R] (or \f[C]remote:\f[R] for
-the \f[C]lsd\f[R] command.) You may put subdirectories in too, eg
-\f[C]remote:bucket/path/to/dir\f[R].
-.PP
-The initial setup for google cloud storage involves getting a token from
-Google Cloud Storage which you need to do in your browser.
-\f[C]rclone config\f[R] walks you through it.
-.PP
-Here is an example of how to make a remote called \f[C]remote\f[R].
-First run:
-.IP
-.nf
-\f[C]
- rclone config
-\f[R]
-.fi
-.PP
+
+See: the [encoding section in the overview](https://rclone.org/overview/#encoding) for more info.
+
+\- Config:      encoding
+\- Env Var:     RCLONE_FTP_ENCODING
+\- Type:        MultiEncoder
+\- Default:     Slash,Del,Ctl,RightSpace,Dot
+
+
+
+### Limitations ###
+
+Note that FTP does have its own implementation of : \[ga]\-\-dump headers\[ga],
+\[ga]\-\-dump bodies\[ga], \[ga]\-\-dump auth\[ga] for debugging which isn\[aq]t the same as
+the HTTP based backends \- it has less fine grained control.
+
+Note that \[ga]\-\-timeout\[ga] isn\[aq]t supported (but \[ga]\-\-contimeout\[ga] is).
+
+Note that \[ga]\-\-bind\[ga] isn\[aq]t supported.
+
+FTP could support server side move but doesn\[aq]t yet.
+
+Note that the ftp backend does not support the \[ga]ftp_proxy\[ga] environment
+variable yet.
+
+ Google Cloud Storage
+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
+
+Paths are specified as \[ga]remote:bucket\[ga] (or \[ga]remote:\[ga] for the \[ga]lsd\[ga]
+command.)  You may put subdirectories in too, eg \[ga]remote:bucket/path/to/dir\[ga].
+
+The initial setup for google cloud storage involves getting a token from Google Cloud Storage
+which you need to do in your browser.  \[ga]rclone config\[ga] walks you
+through it.
+
+Here is an example of how to make a remote called \[ga]remote\[ga].  First run:
+
+     rclone config
+
 This will guide you through an interactive setup process:
+\f[R]
+.fi
+.IP "n)" 3
+New remote
+.IP "o)" 3
+Delete remote
+.IP "p)" 3
+Quit config e/n/d/q> n name> 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) \ \[dq]google cloud
+storage\[dq] [snip] Storage> google cloud storage Google Application
+Client Id \- leave blank normally.
+client_id> Google Application Client Secret \- leave blank normally.
+client_secret> Project number optional \- needed only for
+list/create/delete buckets \- see your developer console.
+project_number> 12345678 Service Account Credentials JSON file path \-
+needed only if you want use SA instead of interactive login.
+service_account_file> 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.
+\ \[dq]authenticatedRead\[dq] 2 / Object owner gets OWNER access, and
+project team owners get OWNER access.
+\ \[dq]bucketOwnerFullControl\[dq] 3 / Object owner gets OWNER access,
+and project team owners get READER access.
+\ \[dq]bucketOwnerRead\[dq] 4 / Object owner gets OWNER access [default
+if left blank].
+\ \[dq]private\[dq] 5 / Object owner gets OWNER access, and project team
+members get access according to their roles.
+\ \[dq]projectPrivate\[dq] 6 / Object owner gets OWNER access, and all
+Users get READER access.
+\ \[dq]publicRead\[dq] object_acl> 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.
+\ \[dq]authenticatedRead\[dq] 2 / Project team owners get OWNER access
+[default if left blank].
+\ \[dq]private\[dq] 3 / Project team members get access according to
+their roles.
+\ \[dq]projectPrivate\[dq] 4 / Project team owners get OWNER access, and
+all Users get READER access.
+\ \[dq]publicRead\[dq] 5 / Project team owners get OWNER access, and all
+Users get WRITER access.
+\ \[dq]publicReadWrite\[dq] bucket_acl> 2 Location for the newly created
+buckets.
+Choose a number from below, or type in your own value 1 / Empty for
+default location (US).
+\ \[dq]\[dq] 2 / Multi\-regional location for Asia.
+\ \[dq]asia\[dq] 3 / Multi\-regional location for Europe.
+\ \[dq]eu\[dq] 4 / Multi\-regional location for United States.
+\ \[dq]us\[dq] 5 / Taiwan.
+\ \[dq]asia\-east1\[dq] 6 / Tokyo.
+\ \[dq]asia\-northeast1\[dq] 7 / Singapore.
+\ \[dq]asia\-southeast1\[dq] 8 / Sydney.
+\ \[dq]australia\-southeast1\[dq] 9 / Belgium.
+\ \[dq]europe\-west1\[dq] 10 / London.
+\ \[dq]europe\-west2\[dq] 11 / Iowa.
+\ \[dq]us\-central1\[dq] 12 / South Carolina.
+\ \[dq]us\-east1\[dq] 13 / Northern Virginia.
+\ \[dq]us\-east4\[dq] 14 / Oregon.
+\ \[dq]us\-west1\[dq] location> 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
+\ \[dq]\[dq] 2 / Multi\-regional storage class
+\ \[dq]MULTI_REGIONAL\[dq] 3 / Regional storage class
+\ \[dq]REGIONAL\[dq] 4 / Nearline storage class \ \[dq]NEARLINE\[dq] 5 /
+Coldline storage class \ \[dq]COLDLINE\[dq] 6 / Durable reduced
+availability storage class \ \[dq]DURABLE_REDUCED_AVAILABILITY\[dq]
+storage_class> 5 Remote config Use auto config?
+.IP \[bu] 2
+Say Y if not sure
+.IP \[bu] 2
+Say N if you are working on a remote or headless machine or Y didn\[aq]t
+work
+.IP "y)" 3
+Yes
+.IP "z)" 3
+No y/n> y If your browser doesn\[aq]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 \-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\- [remote] type = google
+cloud storage client_id = client_secret = token =
+{\[dq]AccessToken\[dq]:\[dq]xxxx.xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx\-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx\[dq],\[dq]RefreshToken\[dq]:\[dq]x/xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx_xxxxxxxxx\[dq],\[dq]Expiry\[dq]:\[dq]2014\-07\-17T20:49:14.929208288+01:00\[dq],\[dq]Extra\[dq]:null}
+project_number = 12345678 object_acl = private bucket_acl = private
+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
+.IP "a)" 3
+Yes this is OK
+.IP "b)" 3
+Edit this remote
+.IP "c)" 3
+Delete this remote y/e/d> y
 .IP
 .nf
 \f[C]
-n) New remote
-d) Delete remote
-q) Quit config
-e/n/d/q> n
-name> 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)
-   \[rs] \[dq]google cloud storage\[dq]
-[snip]
-Storage> google cloud storage
-Google Application Client Id \- leave blank normally.
-client_id>
-Google Application Client Secret \- leave blank normally.
-client_secret>
-Project number optional \- needed only for list/create/delete buckets \- see your developer console.
-project_number> 12345678
-Service Account Credentials JSON file path \- needed only if you want use SA instead of interactive login.
-service_account_file>
-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.
-   \[rs] \[dq]authenticatedRead\[dq]
- 2 / Object owner gets OWNER access, and project team owners get OWNER access.
-   \[rs] \[dq]bucketOwnerFullControl\[dq]
- 3 / Object owner gets OWNER access, and project team owners get READER access.
-   \[rs] \[dq]bucketOwnerRead\[dq]
- 4 / Object owner gets OWNER access [default if left blank].
-   \[rs] \[dq]private\[dq]
- 5 / Object owner gets OWNER access, and project team members get access according to their roles.
-   \[rs] \[dq]projectPrivate\[dq]
- 6 / Object owner gets OWNER access, and all Users get READER access.
-   \[rs] \[dq]publicRead\[dq]
-object_acl> 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.
-   \[rs] \[dq]authenticatedRead\[dq]
- 2 / Project team owners get OWNER access [default if left blank].
-   \[rs] \[dq]private\[dq]
- 3 / Project team members get access according to their roles.
-   \[rs] \[dq]projectPrivate\[dq]
- 4 / Project team owners get OWNER access, and all Users get READER access.
-   \[rs] \[dq]publicRead\[dq]
- 5 / Project team owners get OWNER access, and all Users get WRITER access.
-   \[rs] \[dq]publicReadWrite\[dq]
-bucket_acl> 2
-Location for the newly created buckets.
-Choose a number from below, or type in your own value
- 1 / Empty for default location (US).
-   \[rs] \[dq]\[dq]
- 2 / Multi\-regional location for Asia.
-   \[rs] \[dq]asia\[dq]
- 3 / Multi\-regional location for Europe.
-   \[rs] \[dq]eu\[dq]
- 4 / Multi\-regional location for United States.
-   \[rs] \[dq]us\[dq]
- 5 / Taiwan.
-   \[rs] \[dq]asia\-east1\[dq]
- 6 / Tokyo.
-   \[rs] \[dq]asia\-northeast1\[dq]
- 7 / Singapore.
-   \[rs] \[dq]asia\-southeast1\[dq]
- 8 / Sydney.
-   \[rs] \[dq]australia\-southeast1\[dq]
- 9 / Belgium.
-   \[rs] \[dq]europe\-west1\[dq]
-10 / London.
-   \[rs] \[dq]europe\-west2\[dq]
-11 / Iowa.
-   \[rs] \[dq]us\-central1\[dq]
-12 / South Carolina.
-   \[rs] \[dq]us\-east1\[dq]
-13 / Northern Virginia.
-   \[rs] \[dq]us\-east4\[dq]
-14 / Oregon.
-   \[rs] \[dq]us\-west1\[dq]
-location> 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
-   \[rs] \[dq]\[dq]
- 2 / Multi\-regional storage class
-   \[rs] \[dq]MULTI_REGIONAL\[dq]
- 3 / Regional storage class
-   \[rs] \[dq]REGIONAL\[dq]
- 4 / Nearline storage class
-   \[rs] \[dq]NEARLINE\[dq]
- 5 / Coldline storage class
-   \[rs] \[dq]COLDLINE\[dq]
- 6 / Durable reduced availability storage class
-   \[rs] \[dq]DURABLE_REDUCED_AVAILABILITY\[dq]
-storage_class> 5
-Remote config
-Use auto config?
- * Say Y if not sure
- * Say N if you are working on a remote or headless machine or Y didn\[aq]t work
-y) Yes
-n) No
-y/n> y
-If your browser doesn\[aq]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
-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
-[remote]
-type = google cloud storage
-client_id =
-client_secret =
-token = {\[dq]AccessToken\[dq]:\[dq]xxxx.xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx\-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx\[dq],\[dq]RefreshToken\[dq]:\[dq]x/xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx_xxxxxxxxx\[dq],\[dq]Expiry\[dq]:\[dq]2014\-07\-17T20:49:14.929208288+01:00\[dq],\[dq]Extra\[dq]:null}
-project_number = 12345678
-object_acl = private
-bucket_acl = private
-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
-y) Yes this is OK
-e) Edit this remote
-d) Delete this remote
-y/e/d> y
-\f[R]
-.fi
-.PP
+
 Note that rclone runs a webserver on your local machine to collect the
-token as returned from Google if you use auto config mode.
-This only runs from the moment it opens your browser to the moment you
-get back the verification code.
-This is on \f[C]http://127.0.0.1:53682/\f[R] and this it may require you
-to unblock it temporarily if you are running a host firewall, or use
-manual mode.
-.PP
-This remote is called \f[C]remote\f[R] and can now be used like this
-.PP
+token as returned from Google if you use auto config mode. This only
+runs from the moment it opens your browser to the moment you get back
+the verification code.  This is on \[ga]http://127.0.0.1:53682/\[ga] and this
+it may require you to unblock it temporarily if you are running a host
+firewall, or use manual mode.
+
+This remote is called \[ga]remote\[ga] and can now be used like this
+
 See all the buckets in your project
-.IP
-.nf
-\f[C]
-rclone lsd remote:
-\f[R]
-.fi
-.PP
+
+    rclone lsd remote:
+
 Make a new bucket
-.IP
-.nf
-\f[C]
-rclone mkdir remote:bucket
-\f[R]
-.fi
-.PP
+
+    rclone mkdir remote:bucket
+
 List the contents of a bucket
-.IP
-.nf
-\f[C]
-rclone ls remote:bucket
-\f[R]
-.fi
-.PP
-Sync \f[C]/home/local/directory\f[R] to the remote bucket, deleting any
-excess files in the bucket.
-.IP
-.nf
-\f[C]
-rclone sync /home/local/directory remote:bucket
-\f[R]
-.fi
-.SS Service Account support
-.PP
+
+    rclone ls remote:bucket
+
+Sync \[ga]/home/local/directory\[ga] to the remote bucket, deleting any excess
+files in the bucket.
+
+    rclone sync \-i /home/local/directory remote:bucket
+
+### Service Account support ###
+
 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\[cq]t have actively logged\-in users, for example build machines.
-.PP
-To get credentials for Google Cloud Platform IAM Service
-Accounts (https://cloud.google.com/iam/docs/service-accounts), please
-head to the Service
-Account (https://console.cloud.google.com/permissions/serviceaccounts)
-section of the Google Developer Console.
-Service Accounts behave just like normal \f[C]User\f[R] permissions in
-Google Cloud Storage
-ACLs (https://cloud.google.com/storage/docs/access-control), so you can
-limit their access (e.g.\ make them read only).
-After creating an account, a JSON file containing the Service
-Account\[cq]s credentials will be downloaded onto your machines.
-These credentials are what rclone will use for authentication.
-.PP
-To use a Service Account instead of OAuth2 token flow, enter the path to
-your Service Account credentials at the \f[C]service_account_file\f[R]
-prompt and rclone won\[cq]t use the browser based authentication flow.
-If you\[cq]d rather stuff the contents of the credentials file into the
-rclone config file, you can set \f[C]service_account_credentials\f[R]
-with the actual contents of the file instead, or set the equivalent
+i.e. not tied to a specific end\-user Google account. This is useful
+when you want to synchronise files onto machines that don\[aq]t have
+actively logged\-in users, for example build machines.
+
+To get credentials for Google Cloud Platform
+[IAM Service Accounts](https://cloud.google.com/iam/docs/service\-accounts),
+please head to the
+[Service Account](https://console.cloud.google.com/permissions/serviceaccounts)
+section of the Google Developer Console. Service Accounts behave just
+like normal \[ga]User\[ga] permissions in
+[Google Cloud Storage ACLs](https://cloud.google.com/storage/docs/access\-control),
+so you can limit their access (e.g. make them read only). After
+creating an account, a JSON file containing the Service Account\[aq]s
+credentials will be downloaded onto your machines. These credentials
+are what rclone will use for authentication.
+
+To use a Service Account instead of OAuth2 token flow, enter the path
+to your Service Account credentials at the \[ga]service_account_file\[ga]
+prompt and rclone won\[aq]t use the browser based authentication
+flow. If you\[aq]d rather stuff the contents of the credentials file into
+the rclone config file, you can set \[ga]service_account_credentials\[ga] with
+the actual contents of the file instead, or set the equivalent
 environment variable.
-.SS Application Default Credentials
-.PP
-If no other source of credentials is provided, rclone will fall back to
-Application Default
-Credentials (https://cloud.google.com/video-intelligence/docs/common/auth#authenticating_with_application_default_credentials)
-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 \- see this
-page (https://cloud.google.com/container-registry/docs/advanced-authentication#gcloud_as_a_docker_credential_helper).
-.PP
-Note that in the case application default credentials are used, there is
-no need to explicitly configure a project number.
-.SS \[en]fast\-list
-.PP
-This remote supports \f[C]\-\-fast\-list\f[R] which allows you to use
-fewer transactions in exchange for more memory.
-See the rclone docs (https://rclone.org/docs/#fast-list) for more
-details.
-.SS Custom upload headers
-.PP
-You can set custom upload headers with the \f[C]\-\-header\-upload\f[R]
-flag.
-Google Cloud Storage supports the headers as described in the working
-with metadata
-documentation (https://cloud.google.com/storage/docs/gsutil/addlhelp/WorkingWithObjectMetadata)
-.IP \[bu] 2
-Cache\-Control
-.IP \[bu] 2
-Content\-Disposition
-.IP \[bu] 2
-Content\-Encoding
-.IP \[bu] 2
-Content\-Language
-.IP \[bu] 2
-Content\-Type
-.IP \[bu] 2
-X\-Goog\-Meta\-
-.PP
-Eg \f[C]\-\-header\-upload \[dq]Content\-Type text/potato\[dq]\f[R]
-.PP
+
+### Anonymous Access ###
+
+For downloads of objects that permit public access you can configure rclone
+to use anonymous access by setting \[ga]anonymous\[ga] to \[ga]true\[ga].
+With unauthorized access you can\[aq]t write or create files but only read or list
+those buckets and objects that have public read access.
+
+### Application Default Credentials ###
+
+If no other source of credentials is provided, rclone will fall back
+to
+[Application Default Credentials](https://cloud.google.com/video\-intelligence/docs/common/auth#authenticating_with_application_default_credentials)
+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 \-
+[see this page](https://cloud.google.com/container\-registry/docs/advanced\-authentication#gcloud_as_a_docker_credential_helper).
+
+Note that in the case application default credentials are used, there
+is no need to explicitly configure a project number.
+
+### \-\-fast\-list ###
+
+This remote supports \[ga]\-\-fast\-list\[ga] which allows you to use fewer
+transactions in exchange for more memory. See the [rclone
+docs](https://rclone.org/docs/#fast\-list) for more details.
+
+### Custom upload headers ###
+
+You can set custom upload headers with the \[ga]\-\-header\-upload\[ga]
+flag. Google Cloud Storage supports the headers as described in the
+[working with metadata documentation](https://cloud.google.com/storage/docs/gsutil/addlhelp/WorkingWithObjectMetadata)
+
+\- Cache\-Control
+\- Content\-Disposition
+\- Content\-Encoding
+\- Content\-Language
+\- Content\-Type
+\- X\-Goog\-Meta\-
+
+Eg \[ga]\-\-header\-upload \[dq]Content\-Type text/potato\[dq]\[ga]
+
 Note that the last of these is for setting custom metadata in the form
-\f[C]\-\-header\-upload \[dq]x\-goog\-meta\-key: value\[dq]\f[R]
-.SS Modified time
-.PP
+\[ga]\-\-header\-upload \[dq]x\-goog\-meta\-key: value\[dq]\[ga]
+
+### Modified time ###
+
 Google google cloud storage stores md5sums natively and rclone stores
-modification times as metadata on the object, under the \[lq]mtime\[rq]
-key in RFC3339 format accurate to 1ns.
-.SS Restricted filename characters
-.PP
-.TS
-tab(@);
-l c c.
-T{
-Character
-T}@T{
-Value
-T}@T{
-Replacement
-T}
-_
-T{
-NUL
-T}@T{
-0x00
-T}@T{
-\[u2400]
-T}
-T{
-LF
-T}@T{
-0x0A
-T}@T{
-\[u240A]
-T}
-T{
-CR
-T}@T{
-0x0D
-T}@T{
-\[u240D]
-T}
-T{
-/
-T}@T{
-0x2F
-T}@T{
-\[uFF0F]
-T}
-.TE
-.PP
-Invalid UTF\-8 bytes will also be
-replaced (https://rclone.org/overview/#invalid-utf8), as they can\[cq]t
-be used in JSON strings.
-.SS Standard Options
-.PP
-Here are the standard options specific to google cloud storage (Google
-Cloud Storage (this is not Google Drive)).
-.SS \[en]gcs\-client\-id
-.PP
-Google Application Client Id Leave blank normally.
-.IP \[bu] 2
-Config: client_id
-.IP \[bu] 2
-Env Var: RCLONE_GCS_CLIENT_ID
-.IP \[bu] 2
-Type: string
-.IP \[bu] 2
-Default: \[dq]\[dq]
-.SS \[en]gcs\-client\-secret
-.PP
-Google Application Client Secret Leave blank normally.
-.IP \[bu] 2
-Config: client_secret
-.IP \[bu] 2
-Env Var: RCLONE_GCS_CLIENT_SECRET
-.IP \[bu] 2
-Type: string
-.IP \[bu] 2
-Default: \[dq]\[dq]
-.SS \[en]gcs\-project\-number
-.PP
+modification times as metadata on the object, under the \[dq]mtime\[dq] key in
+RFC3339 format accurate to 1ns.
+
+#### Restricted filename characters
+
+| Character | Value | Replacement |
+| \-\-\-\-\-\-\-\-\- |:\-\-\-\-\-:|:\-\-\-\-\-\-\-\-\-\-\-:|
+| NUL       | 0x00  | \[u2400]           |
+| LF        | 0x0A  | \[u240A]           |
+| CR        | 0x0D  | \[u240D]           |
+| /         | 0x2F  | \[uFF0F]          |
+
+Invalid UTF\-8 bytes will also be [replaced](https://rclone.org/overview/#invalid\-utf8),
+as they can\[aq]t be used in JSON strings.
+
+
+### Standard Options
+
+Here are the standard options specific to google cloud storage (Google Cloud Storage (this is not Google Drive)).
+
+#### \-\-gcs\-client\-id
+
+OAuth Client Id
+Leave blank normally.
+
+\- Config:      client_id
+\- Env Var:     RCLONE_GCS_CLIENT_ID
+\- Type:        string
+\- Default:     \[dq]\[dq]
+
+#### \-\-gcs\-client\-secret
+
+OAuth Client Secret
+Leave blank normally.
+
+\- Config:      client_secret
+\- Env Var:     RCLONE_GCS_CLIENT_SECRET
+\- Type:        string
+\- Default:     \[dq]\[dq]
+
+#### \-\-gcs\-project\-number
+
 Project number.
-Optional \- needed only for list/create/delete buckets \- see your
-developer console.
-.IP \[bu] 2
-Config: project_number
-.IP \[bu] 2
-Env Var: RCLONE_GCS_PROJECT_NUMBER
-.IP \[bu] 2
-Type: string
-.IP \[bu] 2
-Default: \[dq]\[dq]
-.SS \[en]gcs\-service\-account\-file
-.PP
-Service Account Credentials JSON file path Leave blank normally.
+Optional \- needed only for list/create/delete buckets \- see your developer console.
+
+\- Config:      project_number
+\- Env Var:     RCLONE_GCS_PROJECT_NUMBER
+\- Type:        string
+\- Default:     \[dq]\[dq]
+
+#### \-\-gcs\-service\-account\-file
+
+Service Account Credentials JSON file path
+Leave blank normally.
 Needed only if you want use SA instead of interactive login.
-.IP \[bu] 2
-Config: service_account_file
-.IP \[bu] 2
-Env Var: RCLONE_GCS_SERVICE_ACCOUNT_FILE
-.IP \[bu] 2
-Type: string
-.IP \[bu] 2
-Default: \[dq]\[dq]
-.SS \[en]gcs\-service\-account\-credentials
-.PP
-Service Account Credentials JSON blob Leave blank normally.
+
+Leading \[ga]\[ti]\[ga] will be expanded in the file name as will environment variables such as \[ga]${RCLONE_CONFIG_DIR}\[ga].
+
+
+\- Config:      service_account_file
+\- Env Var:     RCLONE_GCS_SERVICE_ACCOUNT_FILE
+\- Type:        string
+\- Default:     \[dq]\[dq]
+
+#### \-\-gcs\-service\-account\-credentials
+
+Service Account Credentials JSON blob
+Leave blank normally.
 Needed only if you want use SA instead of interactive login.
-.IP \[bu] 2
-Config: service_account_credentials
-.IP \[bu] 2
-Env Var: RCLONE_GCS_SERVICE_ACCOUNT_CREDENTIALS
-.IP \[bu] 2
-Type: string
-.IP \[bu] 2
-Default: \[dq]\[dq]
-.SS \[en]gcs\-object\-acl
-.PP
+
+\- Config:      service_account_credentials
+\- Env Var:     RCLONE_GCS_SERVICE_ACCOUNT_CREDENTIALS
+\- Type:        string
+\- Default:     \[dq]\[dq]
+
+#### \-\-gcs\-anonymous
+
+Access public buckets and objects without credentials
+Set to \[aq]true\[aq] if you just want to download files and don\[aq]t configure credentials.
+
+\- Config:      anonymous
+\- Env Var:     RCLONE_GCS_ANONYMOUS
+\- Type:        bool
+\- Default:     false
+
+#### \-\-gcs\-object\-acl
+
 Access Control List for new objects.
-.IP \[bu] 2
-Config: object_acl
-.IP \[bu] 2
-Env Var: RCLONE_GCS_OBJECT_ACL
-.IP \[bu] 2
-Type: string
-.IP \[bu] 2
-Default: \[dq]\[dq]
-.IP \[bu] 2
-Examples:
-.RS 2
-.IP \[bu] 2
-\[lq]authenticatedRead\[rq]
-.RS 2
-.IP \[bu] 2
-Object owner gets OWNER access, and all Authenticated Users get READER
-access.
-.RE
-.IP \[bu] 2
-\[lq]bucketOwnerFullControl\[rq]
-.RS 2
-.IP \[bu] 2
-Object owner gets OWNER access, and project team owners get OWNER
-access.
-.RE
-.IP \[bu] 2
-\[lq]bucketOwnerRead\[rq]
-.RS 2
-.IP \[bu] 2
-Object owner gets OWNER access, and project team owners get READER
-access.
-.RE
-.IP \[bu] 2
-\[lq]private\[rq]
-.RS 2
-.IP \[bu] 2
-Object owner gets OWNER access [default if left blank].
-.RE
-.IP \[bu] 2
-\[lq]projectPrivate\[rq]
-.RS 2
-.IP \[bu] 2
-Object owner gets OWNER access, and project team members get access
-according to their roles.
-.RE
-.IP \[bu] 2
-\[lq]publicRead\[rq]
-.RS 2
-.IP \[bu] 2
-Object owner gets OWNER access, and all Users get READER access.
-.RE
-.RE
-.SS \[en]gcs\-bucket\-acl
-.PP
+
+\- Config:      object_acl
+\- Env Var:     RCLONE_GCS_OBJECT_ACL
+\- Type:        string
+\- Default:     \[dq]\[dq]
+\- Examples:
+    \- \[dq]authenticatedRead\[dq]
+        \- Object owner gets OWNER access, and all Authenticated Users get READER access.
+    \- \[dq]bucketOwnerFullControl\[dq]
+        \- Object owner gets OWNER access, and project team owners get OWNER access.
+    \- \[dq]bucketOwnerRead\[dq]
+        \- Object owner gets OWNER access, and project team owners get READER access.
+    \- \[dq]private\[dq]
+        \- Object owner gets OWNER access [default if left blank].
+    \- \[dq]projectPrivate\[dq]
+        \- Object owner gets OWNER access, and project team members get access according to their roles.
+    \- \[dq]publicRead\[dq]
+        \- Object owner gets OWNER access, and all Users get READER access.
+
+#### \-\-gcs\-bucket\-acl
+
 Access Control List for new buckets.
-.IP \[bu] 2
-Config: bucket_acl
-.IP \[bu] 2
-Env Var: RCLONE_GCS_BUCKET_ACL
-.IP \[bu] 2
-Type: string
-.IP \[bu] 2
-Default: \[dq]\[dq]
-.IP \[bu] 2
-Examples:
-.RS 2
-.IP \[bu] 2
-\[lq]authenticatedRead\[rq]
-.RS 2
-.IP \[bu] 2
-Project team owners get OWNER access, and all Authenticated Users get
-READER access.
-.RE
-.IP \[bu] 2
-\[lq]private\[rq]
-.RS 2
-.IP \[bu] 2
-Project team owners get OWNER access [default if left blank].
-.RE
-.IP \[bu] 2
-\[lq]projectPrivate\[rq]
-.RS 2
-.IP \[bu] 2
-Project team members get access according to their roles.
-.RE
-.IP \[bu] 2
-\[lq]publicRead\[rq]
-.RS 2
-.IP \[bu] 2
-Project team owners get OWNER access, and all Users get READER access.
-.RE
-.IP \[bu] 2
-\[lq]publicReadWrite\[rq]
-.RS 2
-.IP \[bu] 2
-Project team owners get OWNER access, and all Users get WRITER access.
-.RE
-.RE
-.SS \[en]gcs\-bucket\-policy\-only
-.PP
+
+\- Config:      bucket_acl
+\- Env Var:     RCLONE_GCS_BUCKET_ACL
+\- Type:        string
+\- Default:     \[dq]\[dq]
+\- Examples:
+    \- \[dq]authenticatedRead\[dq]
+        \- Project team owners get OWNER access, and all Authenticated Users get READER access.
+    \- \[dq]private\[dq]
+        \- Project team owners get OWNER access [default if left blank].
+    \- \[dq]projectPrivate\[dq]
+        \- Project team members get access according to their roles.
+    \- \[dq]publicRead\[dq]
+        \- Project team owners get OWNER access, and all Users get READER access.
+    \- \[dq]publicReadWrite\[dq]
+        \- Project team owners get OWNER access, and all Users get WRITER access.
+
+#### \-\-gcs\-bucket\-policy\-only
+
 Access checks should use bucket\-level IAM policies.
-.PP
+
 If you want to upload objects to a bucket with Bucket Policy Only set
 then you will need to set this.
-.PP
+
 When it is set, rclone:
-.IP \[bu] 2
-ignores ACLs set on buckets
-.IP \[bu] 2
-ignores ACLs set on objects
-.IP \[bu] 2
-creates buckets with Bucket Policy Only set
-.PP
+
+\- ignores ACLs set on buckets
+\- ignores ACLs set on objects
+\- creates buckets with Bucket Policy Only set
+
 Docs: https://cloud.google.com/storage/docs/bucket\-policy\-only
-.IP \[bu] 2
-Config: bucket_policy_only
-.IP \[bu] 2
-Env Var: RCLONE_GCS_BUCKET_POLICY_ONLY
-.IP \[bu] 2
-Type: bool
-.IP \[bu] 2
-Default: false
-.SS \[en]gcs\-location
-.PP
+
+
+\- Config:      bucket_policy_only
+\- Env Var:     RCLONE_GCS_BUCKET_POLICY_ONLY
+\- Type:        bool
+\- Default:     false
+
+#### \-\-gcs\-location
+
 Location for the newly created buckets.
-.IP \[bu] 2
-Config: location
-.IP \[bu] 2
-Env Var: RCLONE_GCS_LOCATION
-.IP \[bu] 2
-Type: string
-.IP \[bu] 2
-Default: \[dq]\[dq]
-.IP \[bu] 2
-Examples:
-.RS 2
-.IP \[bu] 2
-\[dq]\[dq]
-.RS 2
-.IP \[bu] 2
-Empty for default location (US).
-.RE
-.IP \[bu] 2
-\[lq]asia\[rq]
-.RS 2
-.IP \[bu] 2
-Multi\-regional location for Asia.
-.RE
-.IP \[bu] 2
-\[lq]eu\[rq]
-.RS 2
-.IP \[bu] 2
-Multi\-regional location for Europe.
-.RE
-.IP \[bu] 2
-\[lq]us\[rq]
-.RS 2
-.IP \[bu] 2
-Multi\-regional location for United States.
-.RE
-.IP \[bu] 2
-\[lq]asia\-east1\[rq]
-.RS 2
-.IP \[bu] 2
-Taiwan.
-.RE
-.IP \[bu] 2
-\[lq]asia\-east2\[rq]
-.RS 2
-.IP \[bu] 2
-Hong Kong.
-.RE
-.IP \[bu] 2
-\[lq]asia\-northeast1\[rq]
-.RS 2
-.IP \[bu] 2
-Tokyo.
-.RE
-.IP \[bu] 2
-\[lq]asia\-south1\[rq]
-.RS 2
-.IP \[bu] 2
-Mumbai.
-.RE
-.IP \[bu] 2
-\[lq]asia\-southeast1\[rq]
-.RS 2
-.IP \[bu] 2
-Singapore.
-.RE
-.IP \[bu] 2
-\[lq]australia\-southeast1\[rq]
-.RS 2
-.IP \[bu] 2
-Sydney.
-.RE
-.IP \[bu] 2
-\[lq]europe\-north1\[rq]
-.RS 2
-.IP \[bu] 2
-Finland.
-.RE
-.IP \[bu] 2
-\[lq]europe\-west1\[rq]
-.RS 2
-.IP \[bu] 2
-Belgium.
-.RE
-.IP \[bu] 2
-\[lq]europe\-west2\[rq]
-.RS 2
-.IP \[bu] 2
-London.
-.RE
-.IP \[bu] 2
-\[lq]europe\-west3\[rq]
-.RS 2
-.IP \[bu] 2
-Frankfurt.
-.RE
-.IP \[bu] 2
-\[lq]europe\-west4\[rq]
-.RS 2
-.IP \[bu] 2
-Netherlands.
-.RE
-.IP \[bu] 2
-\[lq]us\-central1\[rq]
-.RS 2
-.IP \[bu] 2
-Iowa.
-.RE
-.IP \[bu] 2
-\[lq]us\-east1\[rq]
-.RS 2
-.IP \[bu] 2
-South Carolina.
-.RE
-.IP \[bu] 2
-\[lq]us\-east4\[rq]
-.RS 2
-.IP \[bu] 2
-Northern Virginia.
-.RE
-.IP \[bu] 2
-\[lq]us\-west1\[rq]
-.RS 2
-.IP \[bu] 2
-Oregon.
-.RE
-.IP \[bu] 2
-\[lq]us\-west2\[rq]
-.RS 2
-.IP \[bu] 2
-California.
-.RE
-.RE
-.SS \[en]gcs\-storage\-class
-.PP
+
+\- Config:      location
+\- Env Var:     RCLONE_GCS_LOCATION
+\- Type:        string
+\- Default:     \[dq]\[dq]
+\- Examples:
+    \- \[dq]\[dq]
+        \- Empty for default location (US).
+    \- \[dq]asia\[dq]
+        \- Multi\-regional location for Asia.
+    \- \[dq]eu\[dq]
+        \- Multi\-regional location for Europe.
+    \- \[dq]us\[dq]
+        \- Multi\-regional location for United States.
+    \- \[dq]asia\-east1\[dq]
+        \- Taiwan.
+    \- \[dq]asia\-east2\[dq]
+        \- Hong Kong.
+    \- \[dq]asia\-northeast1\[dq]
+        \- Tokyo.
+    \- \[dq]asia\-south1\[dq]
+        \- Mumbai.
+    \- \[dq]asia\-southeast1\[dq]
+        \- Singapore.
+    \- \[dq]australia\-southeast1\[dq]
+        \- Sydney.
+    \- \[dq]europe\-north1\[dq]
+        \- Finland.
+    \- \[dq]europe\-west1\[dq]
+        \- Belgium.
+    \- \[dq]europe\-west2\[dq]
+        \- London.
+    \- \[dq]europe\-west3\[dq]
+        \- Frankfurt.
+    \- \[dq]europe\-west4\[dq]
+        \- Netherlands.
+    \- \[dq]us\-central1\[dq]
+        \- Iowa.
+    \- \[dq]us\-east1\[dq]
+        \- South Carolina.
+    \- \[dq]us\-east4\[dq]
+        \- Northern Virginia.
+    \- \[dq]us\-west1\[dq]
+        \- Oregon.
+    \- \[dq]us\-west2\[dq]
+        \- California.
+
+#### \-\-gcs\-storage\-class
+
 The storage class to use when storing objects in Google Cloud Storage.
-.IP \[bu] 2
-Config: storage_class
-.IP \[bu] 2
-Env Var: RCLONE_GCS_STORAGE_CLASS
-.IP \[bu] 2
-Type: string
-.IP \[bu] 2
-Default: \[dq]\[dq]
-.IP \[bu] 2
-Examples:
-.RS 2
-.IP \[bu] 2
-\[dq]\[dq]
-.RS 2
-.IP \[bu] 2
-Default
-.RE
-.IP \[bu] 2
-\[lq]MULTI_REGIONAL\[rq]
-.RS 2
-.IP \[bu] 2
-Multi\-regional storage class
-.RE
-.IP \[bu] 2
-\[lq]REGIONAL\[rq]
-.RS 2
-.IP \[bu] 2
-Regional storage class
-.RE
-.IP \[bu] 2
-\[lq]NEARLINE\[rq]
-.RS 2
-.IP \[bu] 2
-Nearline storage class
-.RE
-.IP \[bu] 2
-\[lq]COLDLINE\[rq]
-.RS 2
-.IP \[bu] 2
-Coldline storage class
-.RE
-.IP \[bu] 2
-\[lq]ARCHIVE\[rq]
-.RS 2
-.IP \[bu] 2
-Archive storage class
-.RE
-.IP \[bu] 2
-\[lq]DURABLE_REDUCED_AVAILABILITY\[rq]
-.RS 2
-.IP \[bu] 2
-Durable reduced availability storage class
-.RE
-.RE
-.SS Advanced Options
-.PP
-Here are the advanced options specific to google cloud storage (Google
-Cloud Storage (this is not Google Drive)).
-.SS \[en]gcs\-encoding
-.PP
+
+\- Config:      storage_class
+\- Env Var:     RCLONE_GCS_STORAGE_CLASS
+\- Type:        string
+\- Default:     \[dq]\[dq]
+\- Examples:
+    \- \[dq]\[dq]
+        \- Default
+    \- \[dq]MULTI_REGIONAL\[dq]
+        \- Multi\-regional storage class
+    \- \[dq]REGIONAL\[dq]
+        \- Regional storage class
+    \- \[dq]NEARLINE\[dq]
+        \- Nearline storage class
+    \- \[dq]COLDLINE\[dq]
+        \- Coldline storage class
+    \- \[dq]ARCHIVE\[dq]
+        \- Archive storage class
+    \- \[dq]DURABLE_REDUCED_AVAILABILITY\[dq]
+        \- Durable reduced availability storage class
+
+### Advanced Options
+
+Here are the advanced options specific to google cloud storage (Google Cloud Storage (this is not Google Drive)).
+
+#### \-\-gcs\-token
+
+OAuth Access Token as a JSON blob.
+
+\- Config:      token
+\- Env Var:     RCLONE_GCS_TOKEN
+\- Type:        string
+\- Default:     \[dq]\[dq]
+
+#### \-\-gcs\-auth\-url
+
+Auth server URL.
+Leave blank to use the provider defaults.
+
+\- Config:      auth_url
+\- Env Var:     RCLONE_GCS_AUTH_URL
+\- Type:        string
+\- Default:     \[dq]\[dq]
+
+#### \-\-gcs\-token\-url
+
+Token server url.
+Leave blank to use the provider defaults.
+
+\- Config:      token_url
+\- Env Var:     RCLONE_GCS_TOKEN_URL
+\- Type:        string
+\- Default:     \[dq]\[dq]
+
+#### \-\-gcs\-encoding
+
 This sets the encoding for the backend.
-.PP
-See: the encoding section in the
-overview (https://rclone.org/overview/#encoding) for more info.
-.IP \[bu] 2
-Config: encoding
-.IP \[bu] 2
-Env Var: RCLONE_GCS_ENCODING
-.IP \[bu] 2
-Type: MultiEncoder
-.IP \[bu] 2
-Default: Slash,CrLf,InvalidUtf8,Dot
-.SS Google Drive
-.PP
-Paths are specified as \f[C]drive:path\f[R]
-.PP
-Drive paths may be as deep as required, eg
-\f[C]drive:directory/subdirectory\f[R].
-.PP
+
+See: the [encoding section in the overview](https://rclone.org/overview/#encoding) for more info.
+
+\- Config:      encoding
+\- Env Var:     RCLONE_GCS_ENCODING
+\- Type:        MultiEncoder
+\- Default:     Slash,CrLf,InvalidUtf8,Dot
+
+
+
+ Google Drive
+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
+
+Paths are specified as \[ga]drive:path\[ga]
+
+Drive paths may be as deep as required, eg \[ga]drive:directory/subdirectory\[ga].
+
 The initial setup for drive involves getting a token from Google drive
-which you need to do in your browser.
-\f[C]rclone config\f[R] walks you through it.
-.PP
-Here is an example of how to make a remote called \f[C]remote\f[R].
-First run:
-.IP
-.nf
-\f[C]
- rclone config
-\f[R]
-.fi
-.PP
+which you need to do in your browser.  \[ga]rclone config\[ga] walks you
+through it.
+
+Here is an example of how to make a remote called \[ga]remote\[ga].  First run:
+
+     rclone config
+
 This will guide you through an interactive setup process:
-.IP
-.nf
-\f[C]
-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> n
-name> remote
-Type of storage to configure.
-Choose a number from below, or type in your own value
-[snip]
-XX / Google Drive
-   \[rs] \[dq]drive\[dq]
-[snip]
-Storage> drive
-Google Application Client Id \- leave blank normally.
-client_id>
-Google Application Client Secret \- leave blank normally.
-client_secret>
-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.
-   \[rs] \[dq]drive\[dq]
- 2 / Read\-only access to file metadata and file contents.
-   \[rs] \[dq]drive.readonly\[dq]
-   / 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.
-   \[rs] \[dq]drive.file\[dq]
-   / Allows read and write access to the Application Data folder.
- 4 | This is not visible in the drive website.
-   \[rs] \[dq]drive.appfolder\[dq]
-   / Allows read\-only access to file metadata but
- 5 | does not allow any access to read or download file content.
-   \[rs] \[dq]drive.metadata.readonly\[dq]
-scope> 1
-ID of the root folder \- leave blank normally.  Fill in to access \[dq]Computers\[dq] folders. (see docs).
-root_folder_id> 
-Service Account Credentials JSON file path \- needed only if you want use SA instead of interactive login.
-service_account_file>
-Remote config
-Use auto config?
- * Say Y if not sure
- * Say N if you are working on a remote or headless machine or Y didn\[aq]t work
-y) Yes
-n) No
-y/n> y
-If your browser doesn\[aq]t open automatically go to the following link: http://127.0.0.1:53682/auth
-Log in and authorize rclone for access
+\f[R]
+.fi
+.PP
+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> n
+name> remote Type of storage to configure.
+Choose a number from below, or type in your own value [snip] XX / Google
+Drive \ \[dq]drive\[dq] [snip] Storage> drive Google Application Client
+Id \- leave blank normally.
+client_id> Google Application Client Secret \- leave blank normally.
+client_secret> 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.
+\ \[dq]drive\[dq] 2 / Read\-only access to file metadata and file
+contents.
+\ \[dq]drive.readonly\[dq] / 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.
+\ \[dq]drive.file\[dq] / Allows read and write access to the Application
+Data folder.
+4 | This is not visible in the drive website.
+\ \[dq]drive.appfolder\[dq] / Allows read\-only access to file metadata
+but 5 | does not allow any access to read or download file content.
+\ \[dq]drive.metadata.readonly\[dq] scope> 1 ID of the root folder \-
+leave blank normally.
+Fill in to access \[dq]Computers\[dq] folders.
+(see docs).
+root_folder_id> Service Account Credentials JSON file path \- needed
+only if you want use SA instead of interactive login.
+service_account_file> Remote config Use auto config?
+* Say Y if not sure * Say N if you are working on a remote or headless
+machine or Y didn\[aq]t work y) Yes n) No y/n> y If your browser
+doesn\[aq]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 team drive?
-y) Yes
-n) No
-y/n> n
-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
-[remote]
-client_id = 
-client_secret = 
-scope = drive
-root_folder_id = 
-service_account_file =
-token = {\[dq]access_token\[dq]:\[dq]XXX\[dq],\[dq]token_type\[dq]:\[dq]Bearer\[dq],\[dq]refresh_token\[dq]:\[dq]XXX\[dq],\[dq]expiry\[dq]:\[dq]2014\-03\-16T13:57:58.955387075Z\[dq]}
-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
-y) Yes this is OK
-e) Edit this remote
-d) Delete this remote
-y/e/d> y
-\f[R]
-.fi
-.PP
+Got code Configure this as a team drive?
+y) Yes n) No y/n> n \-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\- [remote]
+client_id = client_secret = scope = drive root_folder_id =
+service_account_file = token =
+{\[dq]access_token\[dq]:\[dq]XXX\[dq],\[dq]token_type\[dq]:\[dq]Bearer\[dq],\[dq]refresh_token\[dq]:\[dq]XXX\[dq],\[dq]expiry\[dq]:\[dq]2014\-03\-16T13:57:58.955387075Z\[dq]}
+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\- y) Yes this is OK e) Edit this
+remote d) Delete this remote y/e/d> y
+.IP
+.nf
+\f[C]
+
 Note that rclone runs a webserver on your local machine to collect the
-token as returned from Google if you use auto config mode.
-This only runs from the moment it opens your browser to the moment you
-get back the verification code.
-This is on \f[C]http://127.0.0.1:53682/\f[R] and this it may require you
-to unblock it temporarily if you are running a host firewall, or use
-manual mode.
-.PP
+token as returned from Google if you use auto config mode. This only
+runs from the moment it opens your browser to the moment you get back
+the verification code.  This is on \[ga]http://127.0.0.1:53682/\[ga] and this
+it may require you to unblock it temporarily if you are running a host
+firewall, or use manual mode.
+
 You can then use it like this,
-.PP
+
 List directories in top level of your drive
-.IP
-.nf
-\f[C]
-rclone lsd remote:
-\f[R]
-.fi
-.PP
+
+    rclone lsd remote:
+
 List all the files in your drive
-.IP
-.nf
-\f[C]
-rclone ls remote:
-\f[R]
-.fi
-.PP
+
+    rclone ls remote:
+
 To copy a local directory to a drive directory called backup
-.IP
-.nf
-\f[C]
-rclone copy /home/source remote:backup
-\f[R]
-.fi
-.SS Scopes
-.PP
+
+    rclone copy /home/source remote:backup
+
+### Scopes ###
+
 Rclone allows you to select which scope you would like for rclone to
-use.
-This changes what type of token is granted to rclone.
-The scopes are defined
-here (https://developers.google.com/drive/v3/web/about-auth).
-.PP
+use.  This changes what type of token is granted to rclone.  [The
+scopes are defined
+here](https://developers.google.com/drive/v3/web/about\-auth).
+
 The scope are
-.SS drive
-.PP
+
+#### drive ####
+
 This is the default scope and allows full access to all files, except
 for the Application Data Folder (see below).
-.PP
-Choose this one if you aren\[cq]t sure.
-.SS drive.readonly
-.PP
-This allows read only access to all files.
-Files may be listed and downloaded but not uploaded, renamed or deleted.
-.SS drive.file
-.PP
-With this scope rclone can read/view/modify only those files and folders
-it creates.
-.PP
+
+Choose this one if you aren\[aq]t sure.
+
+#### drive.readonly ####
+
+This allows read only access to all files.  Files may be listed and
+downloaded but not uploaded, renamed or deleted.
+
+#### drive.file ####
+
+With this scope rclone can read/view/modify only those files and
+folders it creates.
+
 So if you uploaded files to drive via the web interface (or any other
 means) they will not be visible to rclone.
-.PP
+
 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.
-.PP
-Files created with this scope are visible in the web interface.
-.SS drive.appfolder
-.PP
-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\[cq]t be able to see rclone\[cq]s files from the web interface
-either.
-.SS drive.metadata.readonly
-.PP
-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.
-.SS Root folder ID
-.PP
-You can set the \f[C]root_folder_id\f[R] for rclone.
-This is the directory (identified by its \f[C]Folder ID\f[R]) that
-rclone considers to be the root of your drive.
-.PP
-Normally you will leave this blank and rclone will determine the correct
-root to use itself.
-.PP
-However you can set this to restrict rclone to a specific folder
-hierarchy or to access data within the \[lq]Computers\[rq] tab on the
-drive web interface (where files from Google\[cq]s Backup and Sync
-desktop program go).
-.PP
-In order to do this you will have to find the \f[C]Folder ID\f[R] 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.
-.PP
-So if the folder you want rclone to use has a URL which looks like
-\f[C]https://drive.google.com/drive/folders/1XyfxxxxxxxxxxxxxxxxxxxxxxxxxKHCh\f[R]
-in the browser, then you use \f[C]1XyfxxxxxxxxxxxxxxxxxxxxxxxxxKHCh\f[R]
-as the \f[C]root_folder_id\f[R] in the config.
-.PP
-\f[B]NB\f[R] folders under the \[lq]Computers\[rq] tab seem to be read
-only (drive gives a 500 error) when using rclone.
-.PP
-There doesn\[cq]t appear to be an API to discover the folder IDs of the
-\[lq]Computers\[rq] tab \- please contact us if you know otherwise!
-.PP
-Note also that rclone can\[cq]t access any data under the
-\[lq]Backups\[rq] tab on the google drive web interface yet.
-.SS Service Account support
-.PP
-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\[cq]t have actively logged\-in users, for example build machines.
-.PP
-To use a Service Account instead of OAuth2 token flow, enter the path to
-your Service Account credentials at the \f[C]service_account_file\f[R]
-prompt during \f[C]rclone config\f[R] and rclone won\[cq]t use the
-browser based authentication flow.
-If you\[cq]d rather stuff the contents of the credentials file into the
-rclone config file, you can set \f[C]service_account_credentials\f[R]
-with the actual contents of the file instead, or set the equivalent
-environment variable.
-.SS Use case \- Google Apps/G\-suite account and individual Drive
-.PP
-Let\[cq]s say that you are the administrator of a Google Apps (old) or
-G\-suite account.
-The goal is to store data on an individual\[cq]s Drive account, who IS a
-member of the domain.
-We\[cq]ll call the domain \f[B]example.com\f[R], and the user
-\f[B]foo\[at]example.com\f[R].
-.PP
-There\[cq]s a few steps we need to go through to accomplish this:
-.SS 1. Create a service account for example.com
-.IP \[bu] 2
-To create a service account and obtain its credentials, go to the Google
-Developer Console (https://console.developers.google.com).
-.IP \[bu] 2
-You must have a project \- create one if you don\[cq]t.
-.IP \[bu] 2
-Then go to \[lq]IAM & admin\[rq] \-> \[lq]Service Accounts\[rq].
-.IP \[bu] 2
-Use the \[lq]Create Credentials\[rq] button.
-Fill in \[lq]Service account name\[rq] with something that identifies
-your client.
-\[lq]Role\[rq] can be empty.
-.IP \[bu] 2
-Tick \[lq]Furnish a new private key\[rq] \- select \[lq]Key type
-JSON\[rq].
-.IP \[bu] 2
-Tick \[lq]Enable G Suite Domain\-wide Delegation\[rq].
-This option makes \[lq]impersonation\[rq] possible, as documented here:
-Delegating domain\-wide authority to the service
-account (https://developers.google.com/identity/protocols/OAuth2ServiceAccount#delegatingauthority)
-.IP \[bu] 2
-These credentials are what rclone will use for authentication.
-If you ever need to remove access, press the \[lq]Delete service account
-key\[rq] button.
-.SS 2. Allowing API access to example.com Google Drive
-.IP \[bu] 2
-Go to example.com\[cq]s admin console
-.IP \[bu] 2
-Go into \[lq]Security\[rq] (or use the search bar)
-.IP \[bu] 2
-Select \[lq]Show more\[rq] and then \[lq]Advanced settings\[rq]
-.IP \[bu] 2
-Select \[lq]Manage API client access\[rq] in the
-\[lq]Authentication\[rq] section
-.IP \[bu] 2
-In the \[lq]Client Name\[rq] field enter the service account\[cq]s
-\[lq]Client ID\[rq] \- this can be found in the Developer Console under
-\[lq]IAM & Admin\[rq] \-> \[lq]Service Accounts\[rq], then \[lq]View
-Client ID\[rq] for the newly created service account.
-It is a \[ti]21 character numerical string.
-.IP \[bu] 2
-In the next field, \[lq]One or More API Scopes\[rq], enter
-\f[C]https://www.googleapis.com/auth/drive\f[R] to grant access to
-Google Drive specifically.
-.SS 3. Configure rclone, assuming a new install
-.IP
-.nf
-\f[C]
-rclone config
 
-n/s/q> n         # New
-name>gdrive      # Gdrive is an example name
-Storage>         # Select the number shown for Google Drive
-client_id>       # Can be left blank
-client_secret>   # Can be left blank
-scope>           # Select your scope, 1 for example
-root_folder_id>  # Can be left blank
-service_account_file> /home/foo/myJSONfile.json # This is where the JSON file goes!
-y/n>             # Auto config, y
+Files created with this scope are visible in the web interface.
+
+#### drive.appfolder ####
+
+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\[aq]t be able
+to see rclone\[aq]s files from the web interface either.
+
+#### drive.metadata.readonly ####
+
+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.
+
+### Root folder ID ###
+
+You can set the \[ga]root_folder_id\[ga] for rclone.  This is the directory
+(identified by its \[ga]Folder ID\[ga]) that rclone considers to be the root
+of your drive.
+
+Normally you will leave this blank and rclone will determine the
+correct root to use itself.
+
+However you can set this to restrict rclone to a specific folder
+hierarchy or to access data within the \[dq]Computers\[dq] tab on the drive
+web interface (where files from Google\[aq]s Backup and Sync desktop
+program go).
+
+In order to do this you will have to find the \[ga]Folder ID\[ga] 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.
+
+So if the folder you want rclone to use has a URL which looks like
+\[ga]https://drive.google.com/drive/folders/1XyfxxxxxxxxxxxxxxxxxxxxxxxxxKHCh\[ga]
+in the browser, then you use \[ga]1XyfxxxxxxxxxxxxxxxxxxxxxxxxxKHCh\[ga] as
+the \[ga]root_folder_id\[ga] in the config.
+
+**NB** folders under the \[dq]Computers\[dq] tab seem to be read only (drive
+gives a 500 error) when using rclone.
+
+There doesn\[aq]t appear to be an API to discover the folder IDs of the
+\[dq]Computers\[dq] tab \- please contact us if you know otherwise!
+
+Note also that rclone can\[aq]t access any data under the \[dq]Backups\[dq] tab on
+the google drive web interface yet.
+
+### Service Account support ###
+
+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\[aq]t have
+actively logged\-in users, for example build machines.
+
+To use a Service Account instead of OAuth2 token flow, enter the path
+to your Service Account credentials at the \[ga]service_account_file\[ga]
+prompt during \[ga]rclone config\[ga] and rclone won\[aq]t use the browser based
+authentication flow. If you\[aq]d rather stuff the contents of the
+credentials file into the rclone config file, you can set
+\[ga]service_account_credentials\[ga] with the actual contents of the file
+instead, or set the equivalent environment variable.
+
+#### Use case \- Google Apps/G\-suite account and individual Drive ####
+
+Let\[aq]s say that you are the administrator of a Google Apps (old) or
+G\-suite account.
+The goal is to store data on an individual\[aq]s Drive account, who IS
+a member of the domain.
+We\[aq]ll call the domain **example.com**, and the user
+**foo\[at]example.com**.
+
+There\[aq]s a few steps we need to go through to accomplish this:
+
+##### 1. Create a service account for example.com #####
+  \- To create a service account and obtain its credentials, go to the
+[Google Developer Console](https://console.developers.google.com).
+  \- You must have a project \- create one if you don\[aq]t.
+  \- Then go to \[dq]IAM & admin\[dq] \-> \[dq]Service Accounts\[dq].
+  \- Use the \[dq]Create Credentials\[dq] button. Fill in \[dq]Service account name\[dq]
+with something that identifies your client. \[dq]Role\[dq] can be empty.
+  \- Tick \[dq]Furnish a new private key\[dq] \- select \[dq]Key type JSON\[dq].
+  \- Tick \[dq]Enable G Suite Domain\-wide Delegation\[dq]. This option makes
+\[dq]impersonation\[dq] possible, as documented here:
+[Delegating domain\-wide authority to the service account](https://developers.google.com/identity/protocols/OAuth2ServiceAccount#delegatingauthority)
+  \- These credentials are what rclone will use for authentication.
+If you ever need to remove access, press the \[dq]Delete service
+account key\[dq] button.
+
+##### 2. Allowing API access to example.com Google Drive #####
+  \- Go to example.com\[aq]s admin console
+  \- Go into \[dq]Security\[dq] (or use the search bar)
+  \- Select \[dq]Show more\[dq] and then \[dq]Advanced settings\[dq]
+  \- Select \[dq]Manage API client access\[dq] in the \[dq]Authentication\[dq] section
+  \- In the \[dq]Client Name\[dq] field enter the service account\[aq]s
+\[dq]Client ID\[dq] \- this can be found in the Developer Console under
+\[dq]IAM & Admin\[dq] \-> \[dq]Service Accounts\[dq], then \[dq]View Client ID\[dq] for
+the newly created service account.
+It is a \[ti]21 character numerical string.
+  \- In the next field, \[dq]One or More API Scopes\[dq], enter
+\[ga]https://www.googleapis.com/auth/drive\[ga]
+to grant access to Google Drive specifically.
+
+##### 3. Configure rclone, assuming a new install #####
 \f[R]
 .fi
-.SS 4. Verify that it\[cq]s working
-.IP \[bu] 2
-\f[C]rclone \-v \-\-drive\-impersonate foo\[at]example.com lsf gdrive:backup\f[R]
-.IP \[bu] 2
-The arguments do:
-.RS 2
-.IP \[bu] 2
-\f[C]\-v\f[R] \- verbose logging
-.IP \[bu] 2
-\f[C]\-\-drive\-impersonate foo\[at]example.com\f[R] \- this is what
-does the magic, pretending to be user foo.
-.IP \[bu] 2
-\f[C]lsf\f[R] \- list files in a parsing friendly way
-.IP \[bu] 2
-\f[C]gdrive:backup\f[R] \- use the remote called gdrive, work in the
-folder named backup.
-.RE
-.SS Team drives
 .PP
-If you want to configure the remote to point to a Google Team Drive then
-answer \f[C]y\f[R] to the question
-\f[C]Configure this as a team drive?\f[R].
+rclone config
 .PP
+n/s/q> n # New name>gdrive # Gdrive is an example name Storage> # Select
+the number shown for Google Drive client_id> # Can be left blank
+client_secret> # Can be left blank scope> # Select your scope, 1 for
+example root_folder_id> # Can be left blank service_account_file>
+/home/foo/myJSONfile.json # This is where the JSON file goes! y/n> #
+Auto config, y
+.IP
+.nf
+\f[C]
+
+##### 4. Verify that it\[aq]s working #####
+  \- \[ga]rclone \-v \-\-drive\-impersonate foo\[at]example.com lsf gdrive:backup\[ga]
+  \- The arguments do:
+    \- \[ga]\-v\[ga] \- verbose logging
+    \- \[ga]\-\-drive\-impersonate foo\[at]example.com\[ga] \- this is what does
+the magic, pretending to be user foo.
+    \- \[ga]lsf\[ga] \- list files in a parsing friendly way
+    \- \[ga]gdrive:backup\[ga] \- use the remote called gdrive, work in
+the folder named backup.
+
+Note: in case you configured a specific root folder on gdrive and rclone is unable to access the contents of that folder when using \[ga]\-\-drive\-impersonate\[ga], 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 \[ga]\-\-drive\-impersonate\[ga] option, like this:
+        \[ga]rclone \-v foo\[at]example.com lsf gdrive:backup\[ga]
+
+
+### Team drives ###
+
+If you want to configure the remote to point to a Google Team Drive
+then answer \[ga]y\[ga] to the question \[ga]Configure this as a team drive?\[ga].
+
 This will fetch the list of Team Drives from google and allow you to
-configure which one you want to use.
-You can also type in a team drive ID if you prefer.
-.PP
+configure which one you want to use.  You can also type in a team
+drive ID if you prefer.
+
 For example:
-.IP
-.nf
-\f[C]
+\f[R]
+.fi
+.PP
 Configure this as a team drive?
-y) Yes
-n) No
-y/n> y
-Fetching team drive list...
-Choose a number from below, or type in your own value
- 1 / Rclone Test
-   \[rs] \[dq]xxxxxxxxxxxxxxxxxxxx\[dq]
- 2 / Rclone Test 2
-   \[rs] \[dq]yyyyyyyyyyyyyyyyyyyy\[dq]
- 3 / Rclone Test 3
-   \[rs] \[dq]zzzzzzzzzzzzzzzzzzzz\[dq]
-Enter a Team Drive ID> 1
-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
-[remote]
-client_id =
-client_secret =
-token = {\[dq]AccessToken\[dq]:\[dq]xxxx.x.xxxxx_xxxxxxxxxxx_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx\[dq],\[dq]RefreshToken\[dq]:\[dq]1/xxxxxxxxxxxxxxxx_xxxxxxxxxxxxxxxxxxxxxxxxxx\[dq],\[dq]Expiry\[dq]:\[dq]2014\-03\-16T13:57:58.955387075Z\[dq],\[dq]Extra\[dq]:null}
+y) Yes n) No y/n> y Fetching team drive list...
+Choose a number from below, or type in your own value 1 / Rclone Test
+\ \[dq]xxxxxxxxxxxxxxxxxxxx\[dq] 2 / Rclone Test 2
+\ \[dq]yyyyyyyyyyyyyyyyyyyy\[dq] 3 / Rclone Test 3
+\ \[dq]zzzzzzzzzzzzzzzzzzzz\[dq] Enter a Team Drive ID> 1
+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\- [remote] client_id =
+client_secret = token =
+{\[dq]AccessToken\[dq]:\[dq]xxxx.x.xxxxx_xxxxxxxxxxx_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx\[dq],\[dq]RefreshToken\[dq]:\[dq]1/xxxxxxxxxxxxxxxx_xxxxxxxxxxxxxxxxxxxxxxxxxx\[dq],\[dq]Expiry\[dq]:\[dq]2014\-03\-16T13:57:58.955387075Z\[dq],\[dq]Extra\[dq]:null}
 team_drive = xxxxxxxxxxxxxxxxxxxx
-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
-y) Yes this is OK
-e) Edit this remote
-d) Delete this remote
-y/e/d> y
-\f[R]
-.fi
-.SS \[en]fast\-list
-.PP
-This remote supports \f[C]\-\-fast\-list\f[R] which allows you to use
-fewer transactions in exchange for more memory.
-See the rclone docs (https://rclone.org/docs/#fast-list) for more
-details.
-.PP
-It does this by combining multiple \f[C]list\f[R] calls into a single
-API request.
-.PP
-This works by combining many \f[C]\[aq]%s\[aq] in parents\f[R] filters
-into one expression.
-To list the contents of directories a, b and c, the following requests
-will be send by the regular \f[C]List\f[R] function:
+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\- y) Yes this is OK e) Edit this
+remote d) Delete this remote y/e/d> y
 .IP
 .nf
 \f[C]
-trashed=false and \[aq]a\[aq] in parents
-trashed=false and \[aq]b\[aq] in parents
-trashed=false and \[aq]c\[aq] in parents
+
+### \-\-fast\-list ###
+
+This remote supports \[ga]\-\-fast\-list\[ga] which allows you to use fewer
+transactions in exchange for more memory. See the [rclone
+docs](https://rclone.org/docs/#fast\-list) for more details.
+
+It does this by combining multiple \[ga]list\[ga] calls into a single API request.
+
+This works by combining many \[ga]\[aq]%s\[aq] in parents\[ga] filters into one expression.
+To list the contents of directories a, b and c, the following requests will be send by the regular \[ga]List\[ga] function:
 \f[R]
 .fi
 .PP
+trashed=false and \[aq]a\[aq] in parents trashed=false and \[aq]b\[aq]
+in parents trashed=false and \[aq]c\[aq] in parents
+.IP
+.nf
+\f[C]
 These can now be combined into a single request:
-.IP
-.nf
-\f[C]
-trashed=false and (\[aq]a\[aq] in parents or \[aq]b\[aq] in parents or \[aq]c\[aq] in parents)
 \f[R]
 .fi
 .PP
-The implementation of \f[C]ListR\f[R] will put up to 50
-\f[C]parents\f[R] filters into one request.
-It will use the \f[C]\-\-checkers\f[R] value to specify the number of
-requests to run in parallel.
-.PP
-In tests, these batch requests were up to 20x faster than the regular
-method.
+trashed=false and (\[aq]a\[aq] in parents or \[aq]b\[aq] in parents or
+\[aq]c\[aq] in parents)
+.IP
+.nf
+\f[C]
+
+The implementation of \[ga]ListR\[ga] will put up to 50 \[ga]parents\[ga] filters into one request.
+It will  use the \[ga]\-\-checkers\[ga] value to specify the number of requests to run in parallel.
+
+In tests, these batch requests were up to 20x faster than the regular method.
 Running the following command against different sized folders gives:
-.IP
-.nf
-\f[C]
-rclone lsjson \-vv \-R \-\-checkers=6 gdrive:folder
 \f[R]
 .fi
 .PP
+rclone lsjson \-vv \-R \-\-checkers=6 gdrive:folder
+.IP
+.nf
+\f[C]
+
 small folder (220 directories, 700 files):
-.IP \[bu] 2
-without \f[C]\-\-fast\-list\f[R]: 38s
-.IP \[bu] 2
-with \f[C]\-\-fast\-list\f[R]: 10s
-.PP
+
+\- without \[ga]\-\-fast\-list\[ga]: 38s
+\- with \[ga]\-\-fast\-list\[ga]: 10s
+
 large folder (10600 directories, 39000 files):
-.IP \[bu] 2
-without \f[C]\-\-fast\-list\f[R]: 22:05 min
-.IP \[bu] 2
-with \f[C]\-\-fast\-list\f[R]: 58s
-.SS Modified time
-.PP
+
+\- without \[ga]\-\-fast\-list\[ga]: 22:05 min
+\- with \[ga]\-\-fast\-list\[ga]: 58s
+
+### Modified time ###
+
 Google drive stores modification times accurate to 1 ms.
-.SS Restricted filename characters
-.PP
-Only Invalid UTF\-8 bytes will be
-replaced (https://rclone.org/overview/#invalid-utf8), as they can\[cq]t
-be used in JSON strings.
-.PP
-In contrast to other backends, \f[C]/\f[R] can also be used in names and
-\f[C].\f[R] or \f[C]..\f[R] are valid names.
-.SS Revisions
-.PP
-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.
-.PP
-Revisions follow the standard google policy which at time of writing was
-.IP \[bu] 2
-They are deleted after 30 days or 100 revisions (whatever comes first).
-.IP \[bu] 2
-They do not count towards a user storage quota.
-.SS Deleting files
-.PP
-By default rclone will send all files to the trash when deleting files.
-If deleting them permanently is required then use the
-\f[C]\-\-drive\-use\-trash=false\f[R] flag, or set the equivalent
-environment variable.
-.SS Shortcuts
-.PP
+
+#### Restricted filename characters
+
+Only Invalid UTF\-8 bytes will be [replaced](https://rclone.org/overview/#invalid\-utf8),
+as they can\[aq]t be used in JSON strings.
+
+In contrast to other backends, \[ga]/\[ga] can also be used in names and \[ga].\[ga]
+or \[ga]..\[ga] are valid names.
+
+### Revisions ###
+
+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.
+
+Revisions follow the standard google policy which at time of writing
+was
+
+  * They are deleted after 30 days or 100 revisions (whatever comes first).
+  * They do not count towards a user storage quota.
+
+### Deleting files ###
+
+By default rclone will send all files to the trash when deleting
+files.  If deleting them permanently is required then use the
+\[ga]\-\-drive\-use\-trash=false\[ga] flag, or set the equivalent environment
+variable.
+
+### Shortcuts ###
+
 In March 2020 Google introduced a new feature in Google Drive called
-drive shortcuts (https://support.google.com/drive/answer/9700156)
-(API (https://developers.google.com/drive/api/v3/shortcuts)).
-These will (by September 2020) replace the ability for files or folders
-to be in multiple folders at
-once (https://cloud.google.com/blog/products/g-suite/simplifying-google-drives-folder-structure-and-sharing-models).
-.PP
+[drive shortcuts](https://support.google.com/drive/answer/9700156)
+([API](https://developers.google.com/drive/api/v3/shortcuts)). These
+will (by September 2020) [replace the ability for files or folders to
+be in multiple folders at once](https://cloud.google.com/blog/products/g\-suite/simplifying\-google\-drives\-folder\-structure\-and\-sharing\-models).
+
 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
-(eg the inode in unix terms) so they don\[cq]t break if the source is
+(eg the inode in unix terms) so they don\[aq]t break if the source is
 renamed or moved about.
-.PP
+
 Be default rclone treats these as follows.
-.PP
+
 For shortcuts pointing to files:
-.IP \[bu] 2
-When listing a file shortcut appears as the destination file.
-.IP \[bu] 2
-When downloading the contents of the destination file is downloaded.
-.IP \[bu] 2
-When updating shortcut file with a non shortcut file, the shortcut is
-removed then a new file is uploaded in place of the shortcut.
-.IP \[bu] 2
-When server side moving (renaming) the shortcut is renamed, not the
-destination file.
-.IP \[bu] 2
-When server side copying the shortcut is copied, not the contents of the
-shortcut.
-.IP \[bu] 2
-When deleting the shortcut is deleted not the linked file.
-.IP \[bu] 2
-When setting the modification time, the modification time of the linked
-file will be set.
-.PP
+
+\- When listing a file shortcut appears as the destination file.
+\- When downloading the contents of the destination file is downloaded.
+\- When updating shortcut file with a non shortcut file, the shortcut is removed then a new file is uploaded in place of the shortcut.
+\- When server side moving (renaming) the shortcut is renamed, not the destination file.
+\- When server side copying the shortcut is copied, not the contents of the shortcut.
+\- When deleting the shortcut is deleted not the linked file.
+\- When setting the modification time, the modification time of the linked file will be set.
+
 For shortcuts pointing to folders:
-.IP \[bu] 2
-When listing the shortcut appears as a folder and that folder will
-contain the contents of the linked folder appear (including any sub
-folders)
-.IP \[bu] 2
-When downloading the contents of the linked folder and sub contents are
-downloaded
-.IP \[bu] 2
-When uploading to a shortcut folder the file will be placed in the
-linked folder
-.IP \[bu] 2
-When server side moving (renaming) the shortcut is renamed, not the
-destination folder
-.IP \[bu] 2
-When server side copying the contents of the linked folder is copied,
-not the shortcut.
-.IP \[bu] 2
-When deleting with \f[C]rclone rmdir\f[R] or \f[C]rclone purge\f[R] the
-shortcut is deleted not the linked folder.
-.IP \[bu] 2
-\f[B]NB\f[R] When deleting with \f[C]rclone remove\f[R] or
-\f[C]rclone mount\f[R] the contents of the linked folder will be
-deleted.
-.PP
-It isn\[cq]t currently possible to create shortcuts with rclone.
-.PP
-Shortcuts can be completely ignored with the
-\f[C]\-\-drive\-skip\-shortcuts\f[R] flag or the corresponding
-\f[C]skip_shortcuts\f[R] configuration setting.
-.SS Emptying trash
-.PP
-If you wish to empty your trash you can use the
-\f[C]rclone cleanup remote:\f[R] command which will permanently delete
-all your trashed files.
-This command does not take any path arguments.
-.PP
+
+\- When listing the shortcut appears as a folder and that folder will contain the contents of the linked folder appear (including any sub folders)
+\- When downloading the contents of the linked folder and sub contents are downloaded
+\- When uploading to a shortcut folder the file will be placed in the linked folder
+\- When server side moving (renaming) the shortcut is renamed, not the destination folder
+\- When server side copying the contents of the linked folder is copied, not the shortcut.
+\- When deleting with \[ga]rclone rmdir\[ga] or \[ga]rclone purge\[ga] the shortcut is deleted not the linked folder.
+\- **NB** When deleting with \[ga]rclone remove\[ga] or \[ga]rclone mount\[ga] the contents of the linked folder will be deleted.
+
+The [rclone backend](https://rclone.org/commands/rclone_backend/) command can be used to create shortcuts.  
+
+Shortcuts can be completely ignored with the \[ga]\-\-drive\-skip\-shortcuts\[ga] flag
+or the corresponding \[ga]skip_shortcuts\[ga] configuration setting.
+
+### Emptying trash ###
+
+If you wish to empty your trash you can use the \[ga]rclone cleanup remote:\[ga]
+command which will permanently delete all your trashed files. This command
+does not take any path arguments.
+
 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.
-.SS Quota information
-.PP
-To view your current quota you can use the
-\f[C]rclone about remote:\f[R] 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.
-.SS Import/Export of google documents
-.PP
+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.
+
+### Quota information ###
+
+To view your current quota you can use the \[ga]rclone about remote:\[ga]
+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.
+
+#### Import/Export of google documents ####
+
 Google documents can be exported from and uploaded to Google Drive.
-.PP
+
 When rclone downloads a Google doc it chooses a format to download
-depending upon the \f[C]\-\-drive\-export\-formats\f[R] setting.
-By default the export formats are \f[C]docx,xlsx,pptx,svg\f[R] which are
-a sensible default for an editable document.
-.PP
-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\[cq]t be exported to a format on the formats list, then
-rclone will choose a format from the default list.
-.PP
-If you prefer an archive copy then you might use
-\f[C]\-\-drive\-export\-formats pdf\f[R], or if you prefer
-openoffice/libreoffice formats you might use
-\f[C]\-\-drive\-export\-formats ods,odt,odp\f[R].
-.PP
+depending upon the \[ga]\-\-drive\-export\-formats\[ga] setting.
+By default the export formats are \[ga]docx,xlsx,pptx,svg\[ga] which are a
+sensible default for an editable document.
+
+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\[aq]t be exported to a format on the formats list,
+then rclone will choose a format from the default list.
+
+If you prefer an archive copy then you might use \[ga]\-\-drive\-export\-formats
+pdf\[ga], or if you prefer openoffice/libreoffice formats you might use
+\[ga]\-\-drive\-export\-formats ods,odt,odp\[ga].
+
 Note that rclone adds the extension to the google doc, so if it is
-called \f[C]My Spreadsheet\f[R] on google docs, it will be exported as
-\f[C]My Spreadsheet.xlsx\f[R] or \f[C]My Spreadsheet.pdf\f[R] etc.
-.PP
-When importing files into Google Drive, rclone will convert all files
-with an extension in \f[C]\-\-drive\-import\-formats\f[R] to their
+called \[ga]My Spreadsheet\[ga] on google docs, it will be exported as \[ga]My
+Spreadsheet.xlsx\[ga] or \[ga]My Spreadsheet.pdf\[ga] etc.
+
+When importing files into Google Drive, rclone will convert all
+files with an extension in \[ga]\-\-drive\-import\-formats\[ga] to their
 associated document type.
-rclone will not convert any files by default, since the conversion is
-lossy process.
-.PP
-The conversion must result in a file with the same extension when the
-\f[C]\-\-drive\-export\-formats\f[R] rules are applied to the uploaded
-document.
-.PP
+rclone will not convert any files by default, since the conversion
+is lossy process.
+
+The conversion must result in a file with the same extension when
+the \[ga]\-\-drive\-export\-formats\[ga] rules are applied to the uploaded document.
+
 Here are some examples for allowed and prohibited conversions.
-.PP
-.TS
-tab(@);
-l l l l l.
-T{
-export\-formats
-T}@T{
-import\-formats
-T}@T{
-Upload Ext
-T}@T{
-Document Ext
-T}@T{
-Allowed
-T}
-_
-T{
-odt
-T}@T{
-odt
-T}@T{
-odt
-T}@T{
-odt
-T}@T{
-Yes
-T}
-T{
-odt
-T}@T{
-docx,odt
-T}@T{
-odt
-T}@T{
-odt
-T}@T{
-Yes
-T}
-T{
-T}@T{
-docx
-T}@T{
-docx
-T}@T{
-docx
-T}@T{
-Yes
-T}
-T{
-T}@T{
-odt
-T}@T{
-odt
-T}@T{
-docx
-T}@T{
-No
-T}
-T{
-odt,docx
-T}@T{
-docx,odt
-T}@T{
-docx
-T}@T{
-odt
-T}@T{
-No
-T}
-T{
-docx,odt
-T}@T{
-docx,odt
-T}@T{
-docx
-T}@T{
-docx
-T}@T{
-Yes
-T}
-T{
-docx,odt
-T}@T{
-docx,odt
-T}@T{
-odt
-T}@T{
-docx
-T}@T{
-No
-T}
-.TE
-.PP
-This limitation can be disabled by specifying
-\f[C]\-\-drive\-allow\-import\-name\-change\f[R].
+
+| export\-formats | import\-formats | Upload Ext | Document Ext | Allowed |
+| \-\-\-\-\-\-\-\-\-\-\-\-\-\- | \-\-\-\-\-\-\-\-\-\-\-\-\-\- | \-\-\-\-\-\-\-\-\-\- | \-\-\-\-\-\-\-\-\-\-\-\- | \-\-\-\-\-\-\- |
+| odt | odt | odt | odt | Yes |
+| odt | docx,odt | odt | odt | Yes |
+|  | docx | docx | docx | Yes |
+|  | odt | odt | docx | No |
+| odt,docx | docx,odt | docx | odt | No |
+| docx,odt | docx,odt | docx | docx | Yes |
+| docx,odt | docx,odt | odt | docx | No |
+
+This limitation can be disabled by specifying \[ga]\-\-drive\-allow\-import\-name\-change\[ga].
 When using this flag, rclone can convert multiple files types resulting
-in the same document type at once, eg with
-\f[C]\-\-drive\-import\-formats docx,odt,txt\f[R], 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.
-.PP
-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.
-.PP
+in the same document type at once, eg with \[ga]\-\-drive\-import\-formats docx,odt,txt\[ga],
+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. 
+
+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.
+
 This list can be changed by Google Drive at any time and might not
 represent the currently available conversions.
-.PP
-.TS
-tab(@);
-lw(19.7n) lw(24.1n) lw(26.2n).
-T{
-Extension
-T}@T{
-Mime Type
-T}@T{
-Description
-T}
-_
-T{
-csv
-T}@T{
-text/csv
-T}@T{
-Standard CSV format for Spreadsheets
-T}
-T{
-docx
-T}@T{
-application/vnd.openxmlformats\-officedocument.wordprocessingml.document
-T}@T{
-Microsoft Office Document
-T}
-T{
-epub
-T}@T{
-application/epub+zip
-T}@T{
-E\-book format
-T}
-T{
-html
-T}@T{
-text/html
-T}@T{
-An HTML Document
-T}
-T{
-jpg
-T}@T{
-image/jpeg
-T}@T{
-A JPEG Image File
-T}
-T{
-json
-T}@T{
-application/vnd.google\-apps.script+json
-T}@T{
-JSON Text Format
-T}
-T{
-odp
-T}@T{
-application/vnd.oasis.opendocument.presentation
-T}@T{
-Openoffice Presentation
-T}
-T{
-ods
-T}@T{
-application/vnd.oasis.opendocument.spreadsheet
-T}@T{
-Openoffice Spreadsheet
-T}
-T{
-ods
-T}@T{
-application/x\-vnd.oasis.opendocument.spreadsheet
-T}@T{
-Openoffice Spreadsheet
-T}
-T{
-odt
-T}@T{
-application/vnd.oasis.opendocument.text
-T}@T{
-Openoffice Document
-T}
-T{
-pdf
-T}@T{
-application/pdf
-T}@T{
-Adobe PDF Format
-T}
-T{
-png
-T}@T{
-image/png
-T}@T{
-PNG Image Format
-T}
-T{
-pptx
-T}@T{
-application/vnd.openxmlformats\-officedocument.presentationml.presentation
-T}@T{
-Microsoft Office Powerpoint
-T}
-T{
-rtf
-T}@T{
-application/rtf
-T}@T{
-Rich Text Format
-T}
-T{
-svg
-T}@T{
-image/svg+xml
-T}@T{
-Scalable Vector Graphics Format
-T}
-T{
-tsv
-T}@T{
-text/tab\-separated\-values
-T}@T{
-Standard TSV format for spreadsheets
-T}
-T{
-txt
-T}@T{
-text/plain
-T}@T{
-Plain Text
-T}
-T{
-xlsx
-T}@T{
-application/vnd.openxmlformats\-officedocument.spreadsheetml.sheet
-T}@T{
-Microsoft Office Spreadsheet
-T}
-T{
-zip
-T}@T{
-application/zip
-T}@T{
-A ZIP file of HTML, Images CSS
-T}
-.TE
-.PP
-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
-\f[C]\-\-drive\-export\-formats\f[R] parameter.
-They will match all available Google Documents.
-.PP
-.TS
-tab(@);
-l l l.
-T{
-Extension
-T}@T{
-Description
-T}@T{
-OS Support
-T}
-_
-T{
-desktop
-T}@T{
-freedesktop.org specified desktop entry
-T}@T{
-Linux
-T}
-T{
-link.html
-T}@T{
-An HTML Document with a redirect
-T}@T{
-All
-T}
-T{
-url
-T}@T{
-INI style link file
-T}@T{
-macOS, Windows
-T}
-T{
-webloc
-T}@T{
-macOS specific XML format
-T}@T{
-macOS
-T}
-.TE
-.SS Standard Options
-.PP
+
+| Extension | Mime Type | Description |
+| \-\-\-\-\-\-\-\-\- |\-\-\-\-\-\-\-\-\-\-\-| \-\-\-\-\-\-\-\-\-\-\-\-|
+| csv  | text/csv | Standard CSV format for Spreadsheets |
+| docx | application/vnd.openxmlformats\-officedocument.wordprocessingml.document | Microsoft Office Document |
+| epub | application/epub+zip | E\-book format |
+| html | text/html | An HTML Document |
+| jpg  | image/jpeg | A JPEG Image File |
+| json | application/vnd.google\-apps.script+json | JSON Text Format |
+| odp  | application/vnd.oasis.opendocument.presentation | Openoffice Presentation |
+| ods  | application/vnd.oasis.opendocument.spreadsheet | Openoffice Spreadsheet |
+| ods  | application/x\-vnd.oasis.opendocument.spreadsheet | Openoffice Spreadsheet |
+| odt  | application/vnd.oasis.opendocument.text | Openoffice Document |
+| pdf  | application/pdf | Adobe PDF Format |
+| png  | image/png | PNG Image Format|
+| pptx | application/vnd.openxmlformats\-officedocument.presentationml.presentation | Microsoft Office Powerpoint |
+| rtf  | application/rtf | Rich Text Format |
+| svg  | image/svg+xml | Scalable Vector Graphics Format |
+| tsv  | text/tab\-separated\-values | Standard TSV format for spreadsheets |
+| txt  | text/plain | Plain Text |
+| xlsx | application/vnd.openxmlformats\-officedocument.spreadsheetml.sheet | Microsoft Office Spreadsheet |
+| zip  | application/zip | A ZIP file of HTML, Images CSS |
+
+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
+\[ga]\-\-drive\-export\-formats\[ga] parameter. They will match all available
+Google Documents.
+
+| Extension | Description | OS Support |
+| \-\-\-\-\-\-\-\-\- | \-\-\-\-\-\-\-\-\-\-\- | \-\-\-\-\-\-\-\-\-\- |
+| desktop | freedesktop.org specified desktop entry | Linux |
+| link.html | An HTML Document with a redirect | All |
+| url | INI style link file | macOS, Windows |
+| webloc | macOS specific XML format | macOS |
+
+
+### Standard Options
+
 Here are the standard options specific to drive (Google Drive).
-.SS \[en]drive\-client\-id
-.PP
-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.
-.IP \[bu] 2
-Config: client_id
-.IP \[bu] 2
-Env Var: RCLONE_DRIVE_CLIENT_ID
-.IP \[bu] 2
-Type: string
-.IP \[bu] 2
-Default: \[dq]\[dq]
-.SS \[en]drive\-client\-secret
-.PP
-Google Application Client Secret Setting your own is recommended.
-.IP \[bu] 2
-Config: client_secret
-.IP \[bu] 2
-Env Var: RCLONE_DRIVE_CLIENT_SECRET
-.IP \[bu] 2
-Type: string
-.IP \[bu] 2
-Default: \[dq]\[dq]
-.SS \[en]drive\-scope
-.PP
+
+#### \-\-drive\-client\-id
+
+OAuth Client Id
+Leave blank normally.
+
+\- Config:      client_id
+\- Env Var:     RCLONE_DRIVE_CLIENT_ID
+\- Type:        string
+\- Default:     \[dq]\[dq]
+
+#### \-\-drive\-client\-secret
+
+OAuth Client Secret
+Leave blank normally.
+
+\- Config:      client_secret
+\- Env Var:     RCLONE_DRIVE_CLIENT_SECRET
+\- Type:        string
+\- Default:     \[dq]\[dq]
+
+#### \-\-drive\-scope
+
 Scope that rclone should use when requesting access from drive.
-.IP \[bu] 2
-Config: scope
-.IP \[bu] 2
-Env Var: RCLONE_DRIVE_SCOPE
-.IP \[bu] 2
-Type: string
-.IP \[bu] 2
-Default: \[dq]\[dq]
-.IP \[bu] 2
-Examples:
-.RS 2
-.IP \[bu] 2
-\[lq]drive\[rq]
-.RS 2
-.IP \[bu] 2
-Full access all files, excluding Application Data Folder.
-.RE
-.IP \[bu] 2
-\[lq]drive.readonly\[rq]
-.RS 2
-.IP \[bu] 2
-Read\-only access to file metadata and file contents.
-.RE
-.IP \[bu] 2
-\[lq]drive.file\[rq]
-.RS 2
-.IP \[bu] 2
-Access to files created by rclone only.
-.IP \[bu] 2
-These are visible in the drive website.
-.IP \[bu] 2
-File authorization is revoked when the user deauthorizes the app.
-.RE
-.IP \[bu] 2
-\[lq]drive.appfolder\[rq]
-.RS 2
-.IP \[bu] 2
-Allows read and write access to the Application Data folder.
-.IP \[bu] 2
-This is not visible in the drive website.
-.RE
-.IP \[bu] 2
-\[lq]drive.metadata.readonly\[rq]
-.RS 2
-.IP \[bu] 2
-Allows read\-only access to file metadata but
-.IP \[bu] 2
-does not allow any access to read or download file content.
-.RE
-.RE
-.SS \[en]drive\-root\-folder\-id
-.PP
-ID of the root folder Leave blank normally.
-.PP
-Fill in to access \[lq]Computers\[rq] folders (see docs), or for rclone
-to use a non root folder as its starting point.
-.PP
-Note that if this is blank, the first time rclone runs it will fill it
-in with the ID of the root folder.
-.IP \[bu] 2
-Config: root_folder_id
-.IP \[bu] 2
-Env Var: RCLONE_DRIVE_ROOT_FOLDER_ID
-.IP \[bu] 2
-Type: string
-.IP \[bu] 2
-Default: \[dq]\[dq]
-.SS \[en]drive\-service\-account\-file
-.PP
-Service Account Credentials JSON file path Leave blank normally.
+
+\- Config:      scope
+\- Env Var:     RCLONE_DRIVE_SCOPE
+\- Type:        string
+\- Default:     \[dq]\[dq]
+\- Examples:
+    \- \[dq]drive\[dq]
+        \- Full access all files, excluding Application Data Folder.
+    \- \[dq]drive.readonly\[dq]
+        \- Read\-only access to file metadata and file contents.
+    \- \[dq]drive.file\[dq]
+        \- Access to files created by rclone only.
+        \- These are visible in the drive website.
+        \- File authorization is revoked when the user deauthorizes the app.
+    \- \[dq]drive.appfolder\[dq]
+        \- Allows read and write access to the Application Data folder.
+        \- This is not visible in the drive website.
+    \- \[dq]drive.metadata.readonly\[dq]
+        \- Allows read\-only access to file metadata but
+        \- does not allow any access to read or download file content.
+
+#### \-\-drive\-root\-folder\-id
+
+ID of the root folder
+Leave blank normally.
+
+Fill in to access \[dq]Computers\[dq] folders (see docs), or for rclone to use
+a non root folder as its starting point.
+
+
+\- Config:      root_folder_id
+\- Env Var:     RCLONE_DRIVE_ROOT_FOLDER_ID
+\- Type:        string
+\- Default:     \[dq]\[dq]
+
+#### \-\-drive\-service\-account\-file
+
+Service Account Credentials JSON file path 
+Leave blank normally.
 Needed only if you want use SA instead of interactive login.
-.IP \[bu] 2
-Config: service_account_file
-.IP \[bu] 2
-Env Var: RCLONE_DRIVE_SERVICE_ACCOUNT_FILE
-.IP \[bu] 2
-Type: string
-.IP \[bu] 2
-Default: \[dq]\[dq]
-.SS Advanced Options
-.PP
+
+Leading \[ga]\[ti]\[ga] will be expanded in the file name as will environment variables such as \[ga]${RCLONE_CONFIG_DIR}\[ga].
+
+
+\- Config:      service_account_file
+\- Env Var:     RCLONE_DRIVE_SERVICE_ACCOUNT_FILE
+\- Type:        string
+\- Default:     \[dq]\[dq]
+
+#### \-\-drive\-alternate\-export
+
+Deprecated: no longer needed
+
+\- Config:      alternate_export
+\- Env Var:     RCLONE_DRIVE_ALTERNATE_EXPORT
+\- Type:        bool
+\- Default:     false
+
+### Advanced Options
+
 Here are the advanced options specific to drive (Google Drive).
-.SS \[en]drive\-service\-account\-credentials
-.PP
-Service Account Credentials JSON blob Leave blank normally.
+
+#### \-\-drive\-token
+
+OAuth Access Token as a JSON blob.
+
+\- Config:      token
+\- Env Var:     RCLONE_DRIVE_TOKEN
+\- Type:        string
+\- Default:     \[dq]\[dq]
+
+#### \-\-drive\-auth\-url
+
+Auth server URL.
+Leave blank to use the provider defaults.
+
+\- Config:      auth_url
+\- Env Var:     RCLONE_DRIVE_AUTH_URL
+\- Type:        string
+\- Default:     \[dq]\[dq]
+
+#### \-\-drive\-token\-url
+
+Token server url.
+Leave blank to use the provider defaults.
+
+\- Config:      token_url
+\- Env Var:     RCLONE_DRIVE_TOKEN_URL
+\- Type:        string
+\- Default:     \[dq]\[dq]
+
+#### \-\-drive\-service\-account\-credentials
+
+Service Account Credentials JSON blob
+Leave blank normally.
 Needed only if you want use SA instead of interactive login.
-.IP \[bu] 2
-Config: service_account_credentials
-.IP \[bu] 2
-Env Var: RCLONE_DRIVE_SERVICE_ACCOUNT_CREDENTIALS
-.IP \[bu] 2
-Type: string
-.IP \[bu] 2
-Default: \[dq]\[dq]
-.SS \[en]drive\-team\-drive
-.PP
+
+\- Config:      service_account_credentials
+\- Env Var:     RCLONE_DRIVE_SERVICE_ACCOUNT_CREDENTIALS
+\- Type:        string
+\- Default:     \[dq]\[dq]
+
+#### \-\-drive\-team\-drive
+
 ID of the Team Drive
-.IP \[bu] 2
-Config: team_drive
-.IP \[bu] 2
-Env Var: RCLONE_DRIVE_TEAM_DRIVE
-.IP \[bu] 2
-Type: string
-.IP \[bu] 2
-Default: \[dq]\[dq]
-.SS \[en]drive\-auth\-owner\-only
-.PP
+
+\- Config:      team_drive
+\- Env Var:     RCLONE_DRIVE_TEAM_DRIVE
+\- Type:        string
+\- Default:     \[dq]\[dq]
+
+#### \-\-drive\-auth\-owner\-only
+
 Only consider files owned by the authenticated user.
-.IP \[bu] 2
-Config: auth_owner_only
-.IP \[bu] 2
-Env Var: RCLONE_DRIVE_AUTH_OWNER_ONLY
-.IP \[bu] 2
-Type: bool
-.IP \[bu] 2
-Default: false
-.SS \[en]drive\-use\-trash
-.PP
+
+\- Config:      auth_owner_only
+\- Env Var:     RCLONE_DRIVE_AUTH_OWNER_ONLY
+\- Type:        bool
+\- Default:     false
+
+#### \-\-drive\-use\-trash
+
 Send files to the trash instead of deleting permanently.
 Defaults to true, namely sending files to the trash.
-Use \f[C]\-\-drive\-use\-trash=false\f[R] to delete files permanently
-instead.
-.IP \[bu] 2
-Config: use_trash
-.IP \[bu] 2
-Env Var: RCLONE_DRIVE_USE_TRASH
-.IP \[bu] 2
-Type: bool
-.IP \[bu] 2
-Default: true
-.SS \[en]drive\-skip\-gdocs
-.PP
+Use \[ga]\-\-drive\-use\-trash=false\[ga] to delete files permanently instead.
+
+\- Config:      use_trash
+\- Env Var:     RCLONE_DRIVE_USE_TRASH
+\- Type:        bool
+\- Default:     true
+
+#### \-\-drive\-skip\-gdocs
+
 Skip google documents in all listings.
 If given, gdocs practically become invisible to rclone.
-.IP \[bu] 2
-Config: skip_gdocs
-.IP \[bu] 2
-Env Var: RCLONE_DRIVE_SKIP_GDOCS
-.IP \[bu] 2
-Type: bool
-.IP \[bu] 2
-Default: false
-.SS \[en]drive\-skip\-checksum\-gphotos
-.PP
+
+\- Config:      skip_gdocs
+\- Env Var:     RCLONE_DRIVE_SKIP_GDOCS
+\- Type:        bool
+\- Default:     false
+
+#### \-\-drive\-skip\-checksum\-gphotos
+
 Skip MD5 checksum on Google photos and videos only.
-.PP
+
 Use this if you get checksum errors when transferring Google photos or
 videos.
-.PP
-Setting this flag will cause Google photos and videos to return a blank
-MD5 checksum.
-.PP
-Google photos are identified by being in the \[lq]photos\[rq] space.
-.PP
+
+Setting this flag will cause Google photos and videos to return a
+blank MD5 checksum.
+
+Google photos are identified by being in the \[dq]photos\[dq] space.
+
 Corrupted checksums are caused by Google modifying the image/video but
 not updating the checksum.
-.IP \[bu] 2
-Config: skip_checksum_gphotos
-.IP \[bu] 2
-Env Var: RCLONE_DRIVE_SKIP_CHECKSUM_GPHOTOS
-.IP \[bu] 2
-Type: bool
-.IP \[bu] 2
-Default: false
-.SS \[en]drive\-shared\-with\-me
-.PP
+
+\- Config:      skip_checksum_gphotos
+\- Env Var:     RCLONE_DRIVE_SKIP_CHECKSUM_GPHOTOS
+\- Type:        bool
+\- Default:     false
+
+#### \-\-drive\-shared\-with\-me
+
 Only show files that are shared with me.
-.PP
-Instructs rclone to operate on your \[lq]Shared with me\[rq] folder
-(where Google Drive lets you access the files and folders others have
-shared with you).
-.PP
-This works both with the \[lq]list\[rq] (lsd, lsl, etc) and the
-\[lq]copy\[rq] commands (copy, sync, etc), and with all other commands
-too.
-.IP \[bu] 2
-Config: shared_with_me
-.IP \[bu] 2
-Env Var: RCLONE_DRIVE_SHARED_WITH_ME
-.IP \[bu] 2
-Type: bool
-.IP \[bu] 2
-Default: false
-.SS \[en]drive\-trashed\-only
-.PP
+
+Instructs rclone to operate on your \[dq]Shared with me\[dq] folder (where
+Google Drive lets you access the files and folders others have shared
+with you).
+
+This works both with the \[dq]list\[dq] (lsd, lsl, etc) and the \[dq]copy\[dq]
+commands (copy, sync, etc), and with all other commands too.
+
+\- Config:      shared_with_me
+\- Env Var:     RCLONE_DRIVE_SHARED_WITH_ME
+\- Type:        bool
+\- Default:     false
+
+#### \-\-drive\-trashed\-only
+
 Only show files that are in the trash.
 This will show trashed files in their original directory structure.
-.IP \[bu] 2
-Config: trashed_only
-.IP \[bu] 2
-Env Var: RCLONE_DRIVE_TRASHED_ONLY
-.IP \[bu] 2
-Type: bool
-.IP \[bu] 2
-Default: false
-.SS \[en]drive\-formats
-.PP
+
+\- Config:      trashed_only
+\- Env Var:     RCLONE_DRIVE_TRASHED_ONLY
+\- Type:        bool
+\- Default:     false
+
+#### \-\-drive\-starred\-only
+
+Only show files that are starred.
+
+\- Config:      starred_only
+\- Env Var:     RCLONE_DRIVE_STARRED_ONLY
+\- Type:        bool
+\- Default:     false
+
+#### \-\-drive\-formats
+
 Deprecated: see export_formats
-.IP \[bu] 2
-Config: formats
-.IP \[bu] 2
-Env Var: RCLONE_DRIVE_FORMATS
-.IP \[bu] 2
-Type: string
-.IP \[bu] 2
-Default: \[dq]\[dq]
-.SS \[en]drive\-export\-formats
-.PP
+
+\- Config:      formats
+\- Env Var:     RCLONE_DRIVE_FORMATS
+\- Type:        string
+\- Default:     \[dq]\[dq]
+
+#### \-\-drive\-export\-formats
+
 Comma separated list of preferred formats for downloading Google docs.
-.IP \[bu] 2
-Config: export_formats
-.IP \[bu] 2
-Env Var: RCLONE_DRIVE_EXPORT_FORMATS
-.IP \[bu] 2
-Type: string
-.IP \[bu] 2
-Default: \[lq]docx,xlsx,pptx,svg\[rq]
-.SS \[en]drive\-import\-formats
-.PP
+
+\- Config:      export_formats
+\- Env Var:     RCLONE_DRIVE_EXPORT_FORMATS
+\- Type:        string
+\- Default:     \[dq]docx,xlsx,pptx,svg\[dq]
+
+#### \-\-drive\-import\-formats
+
 Comma separated list of preferred formats for uploading Google docs.
-.IP \[bu] 2
-Config: import_formats
-.IP \[bu] 2
-Env Var: RCLONE_DRIVE_IMPORT_FORMATS
-.IP \[bu] 2
-Type: string
-.IP \[bu] 2
-Default: \[dq]\[dq]
-.SS \[en]drive\-allow\-import\-name\-change
-.PP
-Allow the filetype to change when uploading Google docs (e.g.\ file.doc
-to file.docx).
-This will confuse sync and reupload every time.
-.IP \[bu] 2
-Config: allow_import_name_change
-.IP \[bu] 2
-Env Var: RCLONE_DRIVE_ALLOW_IMPORT_NAME_CHANGE
-.IP \[bu] 2
-Type: bool
-.IP \[bu] 2
-Default: false
-.SS \[en]drive\-use\-created\-date
-.PP
+
+\- Config:      import_formats
+\- Env Var:     RCLONE_DRIVE_IMPORT_FORMATS
+\- Type:        string
+\- Default:     \[dq]\[dq]
+
+#### \-\-drive\-allow\-import\-name\-change
+
+Allow the filetype to change when uploading Google docs (e.g. file.doc to file.docx). This will confuse sync and reupload every time.
+
+\- Config:      allow_import_name_change
+\- Env Var:     RCLONE_DRIVE_ALLOW_IMPORT_NAME_CHANGE
+\- Type:        bool
+\- Default:     false
+
+#### \-\-drive\-use\-created\-date
+
 Use file created date instead of modified date.,
-.PP
+
 Useful when downloading data and you want the creation date used in
 place of the last modified date.
-.PP
-\f[B]WARNING\f[R]: This flag may have some unexpected consequences.
-.PP
+
+**WARNING**: This flag may have some unexpected consequences.
+
 When uploading to your drive all files will be overwritten unless they
-haven\[cq]t been modified since their creation.
-And the inverse will occur while downloading.
-This side effect can be avoided by using the \[lq]\[en]checksum\[rq]
-flag.
-.PP
+haven\[aq]t been modified since their creation. And the inverse will occur
+while downloading.  This side effect can be avoided by using the
+\[dq]\-\-checksum\[dq] flag.
+
 This feature was implemented to retain photos capture date as recorded
-by google photos.
-You will first need to check the \[lq]Create a Google Photos folder\[rq]
-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.
-.IP \[bu] 2
-Config: use_created_date
-.IP \[bu] 2
-Env Var: RCLONE_DRIVE_USE_CREATED_DATE
-.IP \[bu] 2
-Type: bool
-.IP \[bu] 2
-Default: false
-.SS \[en]drive\-use\-shared\-date
-.PP
+by google photos. You will first need to check the \[dq]Create a Google
+Photos folder\[dq] 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.
+
+\- Config:      use_created_date
+\- Env Var:     RCLONE_DRIVE_USE_CREATED_DATE
+\- Type:        bool
+\- Default:     false
+
+#### \-\-drive\-use\-shared\-date
+
 Use date file was shared instead of modified date.
-.PP
-Note that, as with \[lq]\[en]drive\-use\-created\-date\[rq], this flag
-may have unexpected consequences when uploading/downloading files.
-.PP
-If both this flag and \[lq]\[en]drive\-use\-created\-date\[rq] are set,
-the created date is used.
-.IP \[bu] 2
-Config: use_shared_date
-.IP \[bu] 2
-Env Var: RCLONE_DRIVE_USE_SHARED_DATE
-.IP \[bu] 2
-Type: bool
-.IP \[bu] 2
-Default: false
-.SS \[en]drive\-list\-chunk
-.PP
-Size of listing chunk 100\-1000.
-0 to disable.
-.IP \[bu] 2
-Config: list_chunk
-.IP \[bu] 2
-Env Var: RCLONE_DRIVE_LIST_CHUNK
-.IP \[bu] 2
-Type: int
-.IP \[bu] 2
-Default: 1000
-.SS \[en]drive\-impersonate
-.PP
+
+Note that, as with \[dq]\-\-drive\-use\-created\-date\[dq], this flag may have
+unexpected consequences when uploading/downloading files.
+
+If both this flag and \[dq]\-\-drive\-use\-created\-date\[dq] are set, the created
+date is used.
+
+\- Config:      use_shared_date
+\- Env Var:     RCLONE_DRIVE_USE_SHARED_DATE
+\- Type:        bool
+\- Default:     false
+
+#### \-\-drive\-list\-chunk
+
+Size of listing chunk 100\-1000. 0 to disable.
+
+\- Config:      list_chunk
+\- Env Var:     RCLONE_DRIVE_LIST_CHUNK
+\- Type:        int
+\- Default:     1000
+
+#### \-\-drive\-impersonate
+
 Impersonate this user when using a service account.
-.IP \[bu] 2
-Config: impersonate
-.IP \[bu] 2
-Env Var: RCLONE_DRIVE_IMPERSONATE
-.IP \[bu] 2
-Type: string
-.IP \[bu] 2
-Default: \[dq]\[dq]
-.SS \[en]drive\-alternate\-export
-.PP
-Use alternate export URLs for google documents export.,
-.PP
-If this option is set this instructs rclone to use an alternate set of
-export URLs for drive documents.
-Users have reported that the official export URLs can\[cq]t export large
-documents, whereas these unofficial ones can.
-.PP
-See rclone issue #2243 (https://github.com/rclone/rclone/issues/2243)
-for background, this google drive
-issue (https://issuetracker.google.com/issues/36761333) and this helpful
-post (https://www.labnol.org/internet/direct-links-for-google-drive/28356/).
-.IP \[bu] 2
-Config: alternate_export
-.IP \[bu] 2
-Env Var: RCLONE_DRIVE_ALTERNATE_EXPORT
-.IP \[bu] 2
-Type: bool
-.IP \[bu] 2
-Default: false
-.SS \[en]drive\-upload\-cutoff
-.PP
+
+\- Config:      impersonate
+\- Env Var:     RCLONE_DRIVE_IMPERSONATE
+\- Type:        string
+\- Default:     \[dq]\[dq]
+
+#### \-\-drive\-upload\-cutoff
+
 Cutoff for switching to chunked upload
-.IP \[bu] 2
-Config: upload_cutoff
-.IP \[bu] 2
-Env Var: RCLONE_DRIVE_UPLOAD_CUTOFF
-.IP \[bu] 2
-Type: SizeSuffix
-.IP \[bu] 2
-Default: 8M
-.SS \[en]drive\-chunk\-size
-.PP
-Upload chunk size.
-Must a power of 2 >= 256k.
-.PP
-Making this larger will improve performance, but note that each chunk is
-buffered in memory one per transfer.
-.PP
+
+\- Config:      upload_cutoff
+\- Env Var:     RCLONE_DRIVE_UPLOAD_CUTOFF
+\- Type:        SizeSuffix
+\- Default:     8M
+
+#### \-\-drive\-chunk\-size
+
+Upload chunk size. Must a power of 2 >= 256k.
+
+Making this larger will improve performance, but note that each chunk
+is buffered in memory one per transfer.
+
 Reducing this will reduce memory usage but decrease performance.
-.IP \[bu] 2
-Config: chunk_size
-.IP \[bu] 2
-Env Var: RCLONE_DRIVE_CHUNK_SIZE
-.IP \[bu] 2
-Type: SizeSuffix
-.IP \[bu] 2
-Default: 8M
-.SS \[en]drive\-acknowledge\-abuse
-.PP
-Set to allow files which return cannotDownloadAbusiveFile to be
-downloaded.
-.PP
-If downloading a file returns the error \[lq]This file has been
-identified as malware or spam and cannot be downloaded\[rq] with the
-error code \[lq]cannotDownloadAbusiveFile\[rq] then supply this flag to
-rclone to indicate you acknowledge the risks of downloading the file and
-rclone will download it anyway.
-.IP \[bu] 2
-Config: acknowledge_abuse
-.IP \[bu] 2
-Env Var: RCLONE_DRIVE_ACKNOWLEDGE_ABUSE
-.IP \[bu] 2
-Type: bool
-.IP \[bu] 2
-Default: false
-.SS \[en]drive\-keep\-revision\-forever
-.PP
+
+\- Config:      chunk_size
+\- Env Var:     RCLONE_DRIVE_CHUNK_SIZE
+\- Type:        SizeSuffix
+\- Default:     8M
+
+#### \-\-drive\-acknowledge\-abuse
+
+Set to allow files which return cannotDownloadAbusiveFile to be downloaded.
+
+If downloading a file returns the error \[dq]This file has been identified
+as malware or spam and cannot be downloaded\[dq] with the error code
+\[dq]cannotDownloadAbusiveFile\[dq] then supply this flag to rclone to
+indicate you acknowledge the risks of downloading the file and rclone
+will download it anyway.
+
+\- Config:      acknowledge_abuse
+\- Env Var:     RCLONE_DRIVE_ACKNOWLEDGE_ABUSE
+\- Type:        bool
+\- Default:     false
+
+#### \-\-drive\-keep\-revision\-forever
+
 Keep new head revision of each file forever.
-.IP \[bu] 2
-Config: keep_revision_forever
-.IP \[bu] 2
-Env Var: RCLONE_DRIVE_KEEP_REVISION_FOREVER
-.IP \[bu] 2
-Type: bool
-.IP \[bu] 2
-Default: false
-.SS \[en]drive\-size\-as\-quota
-.PP
+
+\- Config:      keep_revision_forever
+\- Env Var:     RCLONE_DRIVE_KEEP_REVISION_FOREVER
+\- Type:        bool
+\- Default:     false
+
+#### \-\-drive\-size\-as\-quota
+
 Show sizes as storage quota usage, not actual size.
-.PP
-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.
-.PP
-\f[B]WARNING\f[R]: This flag may have some unexpected consequences.
-.PP
-It is not recommended to set this flag in your config \- the recommended
-usage is using the flag form \[en]drive\-size\-as\-quota when doing
-rclone ls/lsl/lsf/lsjson/etc only.
-.PP
-If you do use this flag for syncing (not recommended) then you will need
-to use \[en]ignore size also.
-.IP \[bu] 2
-Config: size_as_quota
-.IP \[bu] 2
-Env Var: RCLONE_DRIVE_SIZE_AS_QUOTA
-.IP \[bu] 2
-Type: bool
-.IP \[bu] 2
-Default: false
-.SS \[en]drive\-v2\-download\-min\-size
-.PP
-If Object\[cq]s are greater, use drive v2 API to download.
-.IP \[bu] 2
-Config: v2_download_min_size
-.IP \[bu] 2
-Env Var: RCLONE_DRIVE_V2_DOWNLOAD_MIN_SIZE
-.IP \[bu] 2
-Type: SizeSuffix
-.IP \[bu] 2
-Default: off
-.SS \[en]drive\-pacer\-min\-sleep
-.PP
+
+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.
+
+**WARNING**: This flag may have some unexpected consequences.
+
+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.
+
+If you do use this flag for syncing (not recommended) then you will
+need to use \-\-ignore size also.
+
+\- Config:      size_as_quota
+\- Env Var:     RCLONE_DRIVE_SIZE_AS_QUOTA
+\- Type:        bool
+\- Default:     false
+
+#### \-\-drive\-v2\-download\-min\-size
+
+If Object\[aq]s are greater, use drive v2 API to download.
+
+\- Config:      v2_download_min_size
+\- Env Var:     RCLONE_DRIVE_V2_DOWNLOAD_MIN_SIZE
+\- Type:        SizeSuffix
+\- Default:     off
+
+#### \-\-drive\-pacer\-min\-sleep
+
 Minimum time to sleep between API calls.
-.IP \[bu] 2
-Config: pacer_min_sleep
-.IP \[bu] 2
-Env Var: RCLONE_DRIVE_PACER_MIN_SLEEP
-.IP \[bu] 2
-Type: Duration
-.IP \[bu] 2
-Default: 100ms
-.SS \[en]drive\-pacer\-burst
-.PP
+
+\- Config:      pacer_min_sleep
+\- Env Var:     RCLONE_DRIVE_PACER_MIN_SLEEP
+\- Type:        Duration
+\- Default:     100ms
+
+#### \-\-drive\-pacer\-burst
+
 Number of API calls to allow without sleeping.
-.IP \[bu] 2
-Config: pacer_burst
-.IP \[bu] 2
-Env Var: RCLONE_DRIVE_PACER_BURST
-.IP \[bu] 2
-Type: int
-.IP \[bu] 2
-Default: 100
-.SS \[en]drive\-server\-side\-across\-configs
-.PP
-Allow server side operations (eg copy) to work across different drive
-configs.
-.PP
+
+\- Config:      pacer_burst
+\- Env Var:     RCLONE_DRIVE_PACER_BURST
+\- Type:        int
+\- Default:     100
+
+#### \-\-drive\-server\-side\-across\-configs
+
+Allow server side operations (eg copy) to work across different drive configs.
+
 This can be useful if you wish to do a server side copy between two
-different Google drives.
-Note that this isn\[cq]t enabled by default because it isn\[cq]t easy to
-tell if it will work between any two configurations.
-.IP \[bu] 2
-Config: server_side_across_configs
-.IP \[bu] 2
-Env Var: RCLONE_DRIVE_SERVER_SIDE_ACROSS_CONFIGS
-.IP \[bu] 2
-Type: bool
-.IP \[bu] 2
-Default: false
-.SS \[en]drive\-disable\-http2
-.PP
+different Google drives.  Note that this isn\[aq]t enabled by default
+because it isn\[aq]t easy to tell if it will work between any two
+configurations.
+
+\- Config:      server_side_across_configs
+\- Env Var:     RCLONE_DRIVE_SERVER_SIDE_ACROSS_CONFIGS
+\- Type:        bool
+\- Default:     false
+
+#### \-\-drive\-disable\-http2
+
 Disable drive using http2
-.PP
+
 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.
-.PP
+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.
+
 See: https://github.com/rclone/rclone/issues/3631
-.IP \[bu] 2
-Config: disable_http2
-.IP \[bu] 2
-Env Var: RCLONE_DRIVE_DISABLE_HTTP2
-.IP \[bu] 2
-Type: bool
-.IP \[bu] 2
-Default: true
-.SS \[en]drive\-stop\-on\-upload\-limit
-.PP
+
+
+
+\- Config:      disable_http2
+\- Env Var:     RCLONE_DRIVE_DISABLE_HTTP2
+\- Type:        bool
+\- Default:     true
+
+#### \-\-drive\-stop\-on\-upload\-limit
+
 Make upload limit errors be fatal
-.PP
+
 At the time of writing it is only possible to upload 750GB 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.
-.PP
+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.
+
 Note that this detection is relying on error message strings which
-Google don\[cq]t document so it may break in the future.
-.PP
+Google don\[aq]t document so it may break in the future.
+
 See: https://github.com/rclone/rclone/issues/3857
-.IP \[bu] 2
-Config: stop_on_upload_limit
-.IP \[bu] 2
-Env Var: RCLONE_DRIVE_STOP_ON_UPLOAD_LIMIT
-.IP \[bu] 2
-Type: bool
-.IP \[bu] 2
-Default: false
-.SS \[en]drive\-skip\-shortcuts
-.PP
+
+
+\- Config:      stop_on_upload_limit
+\- Env Var:     RCLONE_DRIVE_STOP_ON_UPLOAD_LIMIT
+\- Type:        bool
+\- Default:     false
+
+#### \-\-drive\-skip\-shortcuts
+
 If set skip shortcut files
-.PP
+
 Normally rclone dereferences shortcut files making them appear as if
-they are the original file (see the shortcuts section).
+they are the original file (see [the shortcuts section](#shortcuts)).
 If this flag is set then rclone will ignore shortcut files completely.
-.IP \[bu] 2
-Config: skip_shortcuts
-.IP \[bu] 2
-Env Var: RCLONE_DRIVE_SKIP_SHORTCUTS
-.IP \[bu] 2
-Type: bool
-.IP \[bu] 2
-Default: false
-.SS \[en]drive\-encoding
-.PP
+
+
+\- Config:      skip_shortcuts
+\- Env Var:     RCLONE_DRIVE_SKIP_SHORTCUTS
+\- Type:        bool
+\- Default:     false
+
+#### \-\-drive\-encoding
+
 This sets the encoding for the backend.
-.PP
-See: the encoding section in the
-overview (https://rclone.org/overview/#encoding) for more info.
-.IP \[bu] 2
-Config: encoding
-.IP \[bu] 2
-Env Var: RCLONE_DRIVE_ENCODING
-.IP \[bu] 2
-Type: MultiEncoder
-.IP \[bu] 2
-Default: InvalidUtf8
-.SS Backend commands
-.PP
+
+See: the [encoding section in the overview](https://rclone.org/overview/#encoding) for more info.
+
+\- Config:      encoding
+\- Env Var:     RCLONE_DRIVE_ENCODING
+\- Type:        MultiEncoder
+\- Default:     InvalidUtf8
+
+### Backend commands
+
 Here are the commands specific to the drive backend.
-.PP
+
 Run them with
-.IP
-.nf
-\f[C]
-rclone backend COMMAND remote:
-\f[R]
-.fi
-.PP
+
+    rclone backend COMMAND remote:
+
 The help below will explain what arguments each command takes.
-.PP
-See the \[lq]rclone backend\[rq]
-command (https://rclone.org/commands/rclone_backend/) for more info on
-how to pass options and arguments.
-.PP
+
+See [the \[dq]rclone backend\[dq] command](https://rclone.org/commands/rclone_backend/) for more
+info on how to pass options and arguments.
+
 These can be run on a running backend using the rc command
-backend/command (https://rclone.org/rc/#backend/command).
-.SS get
-.PP
+[backend/command](https://rclone.org/rc/#backend/command).
+
+#### get
+
 Get command for fetching the drive config parameters
-.IP
-.nf
-\f[C]
-rclone backend get remote: [options] [<arguments>+]
-\f[R]
-.fi
-.PP
-This is a get command which will be used to fetch the various drive
-config parameters
-.PP
+
+    rclone backend get remote: [options] [<arguments>+]
+
+This is a get command which will be used to fetch the various drive config parameters
+
 Usage Examples:
-.IP
-.nf
-\f[C]
-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]
-\f[R]
-.fi
-.PP
+
+    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]
+
+
 Options:
-.IP \[bu] 2
-\[lq]chunk_size\[rq]: show the current upload chunk size
-.IP \[bu] 2
-\[lq]service_account_file\[rq]: show the current service account file
-.SS set
-.PP
+
+\- \[dq]chunk_size\[dq]: show the current upload chunk size
+\- \[dq]service_account_file\[dq]: show the current service account file
+
+#### set
+
 Set command for updating the drive config parameters
-.IP
-.nf
-\f[C]
-rclone backend set remote: [options] [<arguments>+]
-\f[R]
-.fi
-.PP
-This is a set command which will be used to update the various drive
-config parameters
-.PP
+
+    rclone backend set remote: [options] [<arguments>+]
+
+This is a set command which will be used to update the various drive config parameters
+
 Usage Examples:
-.IP
-.nf
-\f[C]
-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]
-\f[R]
-.fi
-.PP
+
+    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]
+
+
 Options:
-.IP \[bu] 2
-\[lq]chunk_size\[rq]: update the current upload chunk size
-.IP \[bu] 2
-\[lq]service_account_file\[rq]: update the current service account file
-.SS shortcut
-.PP
+
+\- \[dq]chunk_size\[dq]: update the current upload chunk size
+\- \[dq]service_account_file\[dq]: update the current service account file
+
+#### shortcut
+
 Create shortcuts from files or directories
-.IP
-.nf
-\f[C]
-rclone backend shortcut remote: [options] [<arguments>+]
-\f[R]
-.fi
-.PP
+
+    rclone backend shortcut remote: [options] [<arguments>+]
+
 This command creates shortcuts from files or directories.
-.PP
+
 Usage:
-.IP
-.nf
-\f[C]
-rclone backend shortcut drive: source_item destination_shortcut
-rclone backend shortcut drive: source_item \-o target=drive2: destination_shortcut
-\f[R]
-.fi
-.PP
-In the first example this creates a shortcut from the
-\[lq]source_item\[rq] which can be a file or a directory to the
-\[lq]destination_shortcut\[rq].
-The \[lq]source_item\[rq] and the \[lq]destination_shortcut\[rq] should
-be relative paths from \[lq]drive:\[rq]
-.PP
-In the second example this creates a shortcut from the
-\[lq]source_item\[rq] relative to \[lq]drive:\[rq] to the
-\[lq]destination_shortcut\[rq] relative to \[lq]drive2:\[rq].
-This may fail with a permission error if the user authenticated with
-\[lq]drive2:\[rq] can\[cq]t read files from \[lq]drive:\[rq].
-.PP
+
+    rclone backend shortcut drive: source_item destination_shortcut
+    rclone backend shortcut drive: source_item \-o target=drive2: destination_shortcut
+
+In the first example this creates a shortcut from the \[dq]source_item\[dq]
+which can be a file or a directory to the \[dq]destination_shortcut\[dq]. The
+\[dq]source_item\[dq] and the \[dq]destination_shortcut\[dq] should be relative paths
+from \[dq]drive:\[dq]
+
+In the second example this creates a shortcut from the \[dq]source_item\[dq]
+relative to \[dq]drive:\[dq] to the \[dq]destination_shortcut\[dq] relative to
+\[dq]drive2:\[dq]. This may fail with a permission error if the user
+authenticated with \[dq]drive2:\[dq] can\[aq]t read files from \[dq]drive:\[dq].
+
+
 Options:
-.IP \[bu] 2
-\[lq]target\[rq]: optional target remote for the shortcut destination
-.SS Limitations
-.PP
-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 MBytes/s but
-lots of small files can take a long time.
-.PP
-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 \f[C]\-\-disable copy\f[R] to
-download and upload the files if you prefer.
-.SS Limitations of Google Docs
-.PP
-Google docs will appear as size \-1 in \f[C]rclone ls\f[R] and as size 0
-in anything which uses the VFS layer, eg \f[C]rclone mount\f[R],
-\f[C]rclone serve\f[R].
-.PP
-This is because rclone can\[cq]t find out the size of the Google docs
+
+\- \[dq]target\[dq]: optional target remote for the shortcut destination
+
+#### drives
+
+List the shared drives available to this account
+
+    rclone backend drives remote: [options] [<arguments>+]
+
+This command lists the shared drives (teamdrives) available to this
+account.
+
+Usage:
+
+    rclone backend drives drive:
+
+This will return a JSON list of objects like this
+
+    [
+        {
+            \[dq]id\[dq]: \[dq]0ABCDEF\-01234567890\[dq],
+            \[dq]kind\[dq]: \[dq]drive#teamDrive\[dq],
+            \[dq]name\[dq]: \[dq]My Drive\[dq]
+        },
+        {
+            \[dq]id\[dq]: \[dq]0ABCDEFabcdefghijkl\[dq],
+            \[dq]kind\[dq]: \[dq]drive#teamDrive\[dq],
+            \[dq]name\[dq]: \[dq]Test Drive\[dq]
+        }
+    ]
+
+
+
+#### untrash
+
+Untrash files and directories
+
+    rclone backend untrash remote: [options] [<arguments>+]
+
+This command untrashes all the files and directories in the directory
+passed in recursively.
+
+Usage:
+
+This takes an optional directory to trash which make this easier to
+use via the API.
+
+    rclone backend untrash drive:directory
+    rclone backend \-i untrash drive:directory subdir
+
+Use the \-i flag to see what would be restored before restoring it.
+
+Result:
+
+    {
+        \[dq]Untrashed\[dq]: 17,
+        \[dq]Errors\[dq]: 0
+    }
+
+
+
+
+### Limitations ###
+
+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 MBytes/s but lots of
+small files can take a long time.
+
+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 \[ga]\-\-disable copy\[ga] to download
+and upload the files if you prefer.
+
+#### Limitations of Google Docs ####
+
+Google docs will appear as size \-1 in \[ga]rclone ls\[ga] and as size 0 in
+anything which uses the VFS layer, eg \[ga]rclone mount\[ga], \[ga]rclone serve\[ga].
+
+This is because rclone can\[aq]t find out the size of the Google docs
 without downloading them.
-.PP
-Google docs will transfer correctly with \f[C]rclone sync\f[R],
-\f[C]rclone copy\f[R] etc as rclone knows to ignore the size when doing
-the transfer.
-.PP
+
+Google docs will transfer correctly with \[ga]rclone sync\[ga], \[ga]rclone copy\[ga]
+etc as rclone knows to ignore the size when doing the transfer.
+
 However an unfortunate consequence of this is that you may not be able
-to download Google docs using \f[C]rclone mount\f[R].
-If it doesn\[cq]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!
-.SS Duplicated files
-.PP
-Sometimes, for no reason I\[cq]ve been able to track down, drive will
-duplicate a file that rclone uploads.
-Drive unlike all the other remotes can have duplicated files.
-.PP
+to download Google docs using \[ga]rclone mount\[ga]. If it doesn\[aq]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!
+
+### Duplicated files ###
+
+Sometimes, for no reason I\[aq]ve been able to track down, drive will
+duplicate a file that rclone uploads.  Drive unlike all the other
+remotes can have duplicated files.
+
 Duplicated files cause problems with the syncing and you will see
 messages in the log about duplicates.
-.PP
-Use \f[C]rclone dedupe\f[R] to fix duplicated files.
-.PP
-Note that this isn\[cq]t just a problem with rclone, even Google Photos
-on Android duplicates files on drive sometimes.
-.SS Rclone appears to be re\-copying files it shouldn\[cq]t
-.PP
+
+Use \[ga]rclone dedupe\[ga] to fix duplicated files.
+
+Note that this isn\[aq]t just a problem with rclone, even Google Photos on
+Android duplicates files on drive sometimes.
+
+### Rclone appears to be re\-copying files it shouldn\[aq]t ###
+
 The most likely cause of this is the duplicated file issue above \- run
-\f[C]rclone dedupe\f[R] and check your logs for duplicate object or
-directory messages.
-.PP
-This can also be caused by a delay/caching on google drive\[cq]s end
-when comparing directory listings.
-Specifically with team drives used in combination with \[en]fast\-list.
-Files that were uploaded recently may not appear on the directory list
-sent to rclone when using \[en]fast\-list.
-.PP
+\[ga]rclone dedupe\[ga] and check your logs for duplicate object or directory
+messages.
+
+This can also be caused by a delay/caching on google drive\[aq]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.
+
 Waiting a moderate period of time between attempts (estimated to be
-approximately 1 hour) and/or not using \[en]fast\-list both seem to be
+approximately 1 hour) and/or not using \-\-fast\-list both seem to be
 effective in preventing the problem.
-.SS Making your own client_id
-.PP
+
+### Making your own client_id ###
+
 When you use rclone with Google drive in its default configuration you
-are using rclone\[cq]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.
-.PP
-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.
-.PP
+are using rclone\[aq]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.
+
+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.
+
 Here is how to create your own Google Drive client ID for rclone:
-.IP "1." 3
-Log into the Google API Console (https://console.developers.google.com/)
-with your Google account.
-It doesn\[cq]t matter what Google account you use.
-(It need not be the same account as the Google Drive you want to access)
-.IP "2." 3
-Select a project or create a new project.
-.IP "3." 3
-Under \[lq]ENABLE APIS AND SERVICES\[rq] search for \[lq]Drive\[rq], and
-enable the \[lq]Google Drive API\[rq].
-.IP "4." 3
-Click \[lq]Credentials\[rq] in the left\-side panel (not \[lq]Create
-credentials\[rq], which opens the wizard), then \[lq]Create
-credentials\[rq]
-.IP "5." 3
-If you already configured an \[lq]Oauth Consent Screen\[rq], then skip
-to the next step; if not, click on \[lq]CONFIGURE CONSENT SCREEN\[rq]
-button (near the top right corner of the right panel), then select
-\[lq]External\[rq] and click on \[lq]CREATE\[rq]; on the next screen,
-enter an \[lq]Application name\[rq] (\[lq]rclone\[rq] is OK) then click
-on \[lq]Save\[rq] (all other data is optional).
-Click again on \[lq]Credentials\[rq] on the left panel to go back to the
-\[lq]Credentials\[rq] screen.
-.PP
-(PS: if you are a GSuite user, you could also select \[lq]Internal\[rq]
-instead of \[lq]External\[rq] above, but this has not been
-tested/documented so far).
-.IP "6." 3
-Click on the \[lq]+ CREATE CREDENTIALS\[rq] button at the top of the
-screen, then select \[lq]OAuth client ID\[rq].
-.IP "7." 3
-Choose an application type of \[lq]Desktop app\[rq] if you using a
-Google account or \[lq]Other\[rq] if you using a GSuite account and
-click \[lq]Create\[rq].
-(the default name is fine)
-.IP "8." 3
-It will show you a client ID and client secret.
-Use these values in rclone config to add a new remote or edit an
-existing remote.
-.PP
-Be aware that, due to the \[lq]enhanced security\[rq] recently
-introduced by Google, you are theoretically expected to \[lq]submit your
-app for verification\[rq] 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\[cq]s not such a big deal).
-.PP
+
+1. Log into the [Google API
+Console](https://console.developers.google.com/) with your Google
+account. It doesn\[aq]t matter what Google account you use. (It need not
+be the same account as the Google Drive you want to access)
+
+2. Select a project or create a new project.
+
+3. Under \[dq]ENABLE APIS AND SERVICES\[dq] search for \[dq]Drive\[dq], and enable the
+\[dq]Google Drive API\[dq].
+
+4. Click \[dq]Credentials\[dq] in the left\-side panel (not \[dq]Create
+credentials\[dq], which opens the wizard), then \[dq]Create credentials\[dq]
+
+5. If you already configured an \[dq]Oauth Consent Screen\[dq], then skip
+to the next step; if not, click on \[dq]CONFIGURE CONSENT SCREEN\[dq] button 
+(near the top right corner of the right panel), then select \[dq]External\[dq]
+and click on \[dq]CREATE\[dq]; on the next screen, enter an \[dq]Application name\[dq]
+(\[dq]rclone\[dq] is OK) then click on \[dq]Save\[dq] (all other data is optional). 
+Click again on \[dq]Credentials\[dq] on the left panel to go back to the 
+\[dq]Credentials\[dq] screen.
+
+(PS: if you are a GSuite user, you could also select \[dq]Internal\[dq] instead
+of \[dq]External\[dq] above, but this has not been tested/documented so far). 
+
+6.  Click on the \[dq]+ CREATE CREDENTIALS\[dq] button at the top of the screen,
+then select \[dq]OAuth client ID\[dq].
+
+7. Choose an application type of \[dq]Desktop app\[dq] if you using a Google account or \[dq]Other\[dq] if 
+you using a GSuite account and click \[dq]Create\[dq]. (the default name is fine)
+
+8. It will show you a client ID and client secret.  Use these values
+in rclone config to add a new remote or edit an existing remote.
+
+Be aware that, due to the \[dq]enhanced security\[dq] recently introduced by
+Google, you are theoretically expected to \[dq]submit your app for verification\[dq]
+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\[aq]s not such a big deal). 
+
 (Thanks to \[at]balazer on github for these instructions.)
-.SS Google Photos
-.PP
-The rclone backend for Google
-Photos (https://www.google.com/photos/about/) is a specialized backend
-for transferring photos and videos to and from Google Photos.
-.PP
-\f[B]NB\f[R] The Google Photos API which rclone uses has quite a few
-limitations, so please read the limitations section carefully to make
-sure it is suitable for your use.
-.SS Configuring Google Photos
-.PP
-The initial setup for google cloud storage involves getting a token from
-Google Photos which you need to do in your browser.
-\f[C]rclone config\f[R] walks you through it.
-.PP
-Here is an example of how to make a remote called \f[C]remote\f[R].
-First run:
-.IP
-.nf
-\f[C]
- rclone config
+
+Sometimes, creation of an OAuth consent in Google API Console fails due to an error message
+\[lq]The request failed because changes to one of the field of the resource is not supported\[rq].
+As a convenient workaround, the necessary Google Drive API key can be created on the
+[Python Quickstart](https://developers.google.com/drive/api/v3/quickstart/python) 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.
+
+ Google Photos
+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
+
+The rclone backend for [Google Photos](https://www.google.com/photos/about/) is
+a specialized backend for transferring photos and videos to and from
+Google Photos.
+
+**NB** The Google Photos API which rclone uses has quite a few
+limitations, so please read the [limitations section](#limitations)
+carefully to make sure it is suitable for your use.
+
+## Configuring Google Photos
+
+The initial setup for google cloud storage involves getting a token from Google Photos
+which you need to do in your browser.  \[ga]rclone config\[ga] walks you
+through it.
+
+Here is an example of how to make a remote called \[ga]remote\[ga].  First run:
+
+     rclone config
+
+This will guide you through an interactive setup process:
 \f[R]
 .fi
 .PP
-This will guide you through an interactive setup process:
-.IP
-.nf
-\f[C]
-No remotes found \- make a new one
-n) New remote
-s) Set configuration password
-q) Quit config
-n/s/q> n
-name> remote
-Type of storage to configure.
-Enter a string value. Press Enter for the default (\[dq]\[dq]).
-Choose a number from below, or type in your own value
-[snip]
-XX / Google Photos
-   \[rs] \[dq]google photos\[dq]
-[snip]
-Storage> 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 (\[dq]\[dq]).
-client_id> 
-Google Application Client Secret
-Leave blank normally.
-Enter a string value. Press Enter for the default (\[dq]\[dq]).
-client_secret> 
-Set to make the Google Photos backend read only.
-
+No remotes found \- make a new one n) New remote s) Set configuration
+password q) Quit config n/s/q> n name> remote Type of storage to
+configure.
+Enter a string value.
+Press Enter for the default (\[dq]\[dq]).
+Choose a number from below, or type in your own value [snip] XX / Google
+Photos \ \[dq]google photos\[dq] [snip] Storage> google photos ** See
+help for google photos backend at: https://rclone.org/googlephotos/ **
+.PP
+Google Application Client Id Leave blank normally.
+Enter a string value.
+Press Enter for the default (\[dq]\[dq]).
+client_id> Google Application Client Secret Leave blank normally.
+Enter a string value.
+Press Enter for the default (\[dq]\[dq]).
+client_secret> Set to make the Google Photos backend read only.
+.PP
 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 (\[dq]false\[dq]).
-read_only> 
-Edit advanced config? (y/n)
-y) Yes
-n) No
-y/n> n
-Remote config
-Use auto config?
- * Say Y if not sure
- * Say N if you are working on a remote or headless machine
-y) Yes
-n) No
-y/n> y
-If your browser doesn\[aq]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...
+Enter a boolean value (true or false).
+Press Enter for the default (\[dq]false\[dq]).
+read_only> Edit advanced config?
+(y/n) y) Yes n) No y/n> n Remote config Use auto config?
+* Say Y if not sure * Say N if you are working on a remote or headless
+machine y) Yes n) No y/n> y If your browser doesn\[aq]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.
-
-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
-[remote]
-type = google photos
-token = {\[dq]access_token\[dq]:\[dq]XXX\[dq],\[dq]token_type\[dq]:\[dq]Bearer\[dq],\[dq]refresh_token\[dq]:\[dq]XXX\[dq],\[dq]expiry\[dq]:\[dq]2019\-06\-28T17:38:04.644930156+01:00\[dq]}
-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
-y) Yes this is OK
-e) Edit this remote
-d) Delete this remote
-y/e/d> y
-\f[R]
-.fi
 .PP
+*** 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.
+.PP
+.TS
+tab(@);
+lw(20.4n).
+T{
+[remote] type = google photos token =
+{\[dq]access_token\[dq]:\[dq]XXX\[dq],\[dq]token_type\[dq]:\[dq]Bearer\[dq],\[dq]refresh_token\[dq]:\[dq]XXX\[dq],\[dq]expiry\[dq]:\[dq]2019\-06\-28T17:38:04.644930156+01:00\[dq]}
+T}
+_
+T{
+y) Yes this is OK e) Edit this remote d) Delete this remote y/e/d> y
+\[ga]\[ga]\[ga]
+T}
+T{
 Note that rclone runs a webserver on your local machine to collect the
 token as returned from Google if you use auto config mode.
 This only runs from the moment it opens your browser to the moment you
@@ -23482,46 +20549,43 @@ get back the verification code.
 This is on \f[C]http://127.0.0.1:53682/\f[R] and this may require you to
 unblock it temporarily if you are running a host firewall, or use manual
 mode.
-.PP
+T}
+T{
 This remote is called \f[C]remote\f[R] and can now be used like this
-.PP
+T}
+T{
 See all the albums in your photos
-.IP
-.nf
-\f[C]
+T}
+T{
 rclone lsd remote:album
-\f[R]
-.fi
-.PP
+T}
+T{
 Make a new album
-.IP
-.nf
-\f[C]
+T}
+T{
 rclone mkdir remote:album/newAlbum
-\f[R]
-.fi
-.PP
+T}
+T{
 List the contents of an album
-.IP
-.nf
-\f[C]
+T}
+T{
 rclone ls remote:album/newAlbum
-\f[R]
-.fi
-.PP
+T}
+T{
 Sync \f[C]/home/local/images\f[R] to the Google Photos, removing any
 excess files in the album.
-.IP
-.nf
-\f[C]
-rclone sync /home/local/image remote:album/newAlbum
-\f[R]
-.fi
-.SS Layout
-.PP
+T}
+T{
+rclone sync \-i /home/local/image remote:album/newAlbum
+T}
+T{
+## Layout
+T}
+T{
 As Google Photos is not a general purpose cloud storage system the
 backend is laid out to help you navigate it.
-.PP
+T}
+T{
 The directories under \f[C]media\f[R] show different ways of
 categorizing the media.
 Each file will appear multiple times.
@@ -23529,165 +20593,115 @@ So if you want to make a backup of your google photos you might choose
 to backup \f[C]remote:media/by\-month\f[R].
 (\f[B]NB\f[R] \f[C]remote:media/by\-day\f[R] is rather slow at the
 moment so avoid for syncing.)
-.PP
+T}
+T{
 Note that all your photos and videos will appear somewhere under
 \f[C]media\f[R], but they may not appear under \f[C]album\f[R] unless
-you\[cq]ve put them into albums.
-.IP
-.nf
-\f[C]
-/
-\- 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
-\f[R]
-.fi
-.PP
+you\[aq]ve put them into albums.
+T}
+T{
+\f[C]/ \- 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\f[R]
+T}
+T{
 There are two writable parts of the tree, the \f[C]upload\f[R] directory
 and sub directories of the \f[C]album\f[R] directory.
-.PP
-The \f[C]upload\f[R] directory is for uploading files you don\[cq]t want
+T}
+T{
+The \f[C]upload\f[R] directory is for uploading files you don\[aq]t want
 to put into albums.
-This will be empty to start with and will contain the files you\[cq]ve
+This will be empty to start with and will contain the files you\[aq]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 \f[C]album\f[R] will work better.
-.PP
+T}
+T{
 Directories within the \f[C]album\f[R] directory are also writeable and
 you may create new directories (albums) under \f[C]album\f[R].
 If you copy files with a directory hierarchy in there then rclone will
 create albums with the \f[C]/\f[R] character in them.
 For example if you do
-.IP
-.nf
-\f[C]
+T}
+T{
 rclone copy /path/to/images remote:album/images
-\f[R]
-.fi
-.PP
+T}
+T{
 and the images directory contains
-.IP
-.nf
-\f[C]
-images
-    \- file1.jpg
-    dir
-        file2.jpg
-    dir2
-        dir3
-            file3.jpg
-\f[R]
-.fi
-.PP
+T}
+T{
+\f[C]images \- file1.jpg dir file2.jpg dir2 dir3 file3.jpg\f[R]
+T}
+T{
 Then rclone will create the following albums with the following files in
-.IP \[bu] 2
-images
-.RS 2
-.IP \[bu] 2
-file1.jpg
-.RE
-.IP \[bu] 2
-images/dir
-.RS 2
-.IP \[bu] 2
-file2.jpg
-.RE
-.IP \[bu] 2
-images/dir2/dir3
-.RS 2
-.IP \[bu] 2
+T}
+T{
+\- images \- file1.jpg \- images/dir \- file2.jpg \- images/dir2/dir3 \-
 file3.jpg
-.RE
-.PP
+T}
+T{
 This means that you can use the \f[C]album\f[R] path pretty much like a
 normal filesystem and it is a good target for repeated syncing.
-.PP
+T}
+T{
 The \f[C]shared\-album\f[R] directory shows albums shared with you or by
 you.
 This is similar to the Sharing tab in the Google Photos web interface.
-.SS Limitations
-.PP
+T}
+T{
+## Limitations
+T}
+T{
 Only images and videos can be uploaded.
 If you attempt to upload non videos or images or formats that Google
-Photos doesn\[cq]t understand, rclone will upload the file, then Google
+Photos doesn\[aq]t understand, rclone will upload the file, then Google
 Photos will give an error when it is put turned into a media item.
-.PP
+T}
+T{
 Note that all media items uploaded to Google Photos through the API are
-stored in full resolution at \[lq]original quality\[rq] and
+stored in full resolution at \[dq]original quality\[dq] and
 \f[B]will\f[R] count towards your storage quota in your Google Account.
-The API does \f[B]not\f[R] offer a way to upload in \[lq]high
-quality\[rq] mode..
-.SS Downloading Images
-.PP
+The API does \f[B]not\f[R] offer a way to upload in \[dq]high
+quality\[dq] mode..
+T}
+T{
+### Downloading Images
+T}
+T{
 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 bug
 #112096115 (https://issuetracker.google.com/issues/112096115).
-.PP
+T}
+T{
 \f[B]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 \[lq]Google Photos\[rq] as a backup of your photos. You will
+relying on \[dq]Google Photos\[dq] 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\f[R]
-.SS Downloading Videos
-.PP
+\[aq]google takeout\[aq] to recover the original photos as a last
+resort\f[R]
+T}
+T{
+### Downloading Videos
+T}
+T{
 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 bug
 #113672044 (https://issuetracker.google.com/issues/113672044).
-.SS Duplicates
-.PP
+T}
+T{
+### Duplicates
+T}
+T{
 If a file name is duplicated in a directory then rclone will add the
 file ID into its name.
 So two files called \f[C]file.jpg\f[R] would then appear as
 \f[C]file {123456}.jpg\f[R] and \f[C]file {ABCDEF}.jpg\f[R] (the actual
 IDs are a lot longer alas!).
-.PP
+T}
+T{
 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
@@ -23696,133 +20710,192 @@ For example if you uploaded an image to \f[C]upload\f[R] then uploaded
 the same image to \f[C]album/my_album\f[R] the filename of the image in
 \f[C]album/my_album\f[R] will be what it was uploaded with initially,
 not what you uploaded it with to \f[C]album\f[R].
-In practise this shouldn\[cq]t cause too many problems.
-.SS Modified time
-.PP
+In practise this shouldn\[aq]t cause too many problems.
+T}
+T{
+### Modified time
+T}
+T{
 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.
-.PP
+T}
+T{
 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.
-.SS Size
-.PP
+T}
+T{
+### Size
+T}
+T{
 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.
-.PP
+T}
+T{
 It is possible to read the size of the media, but this needs an extra
 HTTP HEAD request per media item so is \f[B]very slow\f[R] and uses up a
 lot of transactions.
 This can be enabled with the \f[C]\-\-gphotos\-read\-size\f[R] option or
 the \f[C]read_size = true\f[R] config parameter.
-.PP
+T}
+T{
 If you want to use the backend with \f[C]rclone mount\f[R] 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\[cq]ll need to experiment to see if it works for you without the
+You\[aq]ll need to experiment to see if it works for you without the
 flag.
-.SS Albums
-.PP
+T}
+T{
+### Albums
+T}
+T{
 Rclone can only upload files to albums it created.
 This is a limitation of the Google Photos
 API (https://developers.google.com/photos/library/guides/manage-albums).
-.PP
+T}
+T{
 Rclone can remove files it uploaded from albums it created only.
-.SS Deleting files
-.PP
+T}
+T{
+### Deleting files
+T}
+T{
 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 bug #109759781 (https://issuetracker.google.com/issues/109759781).
-.PP
+T}
+T{
 Rclone cannot delete files anywhere except under \f[C]album\f[R].
-.SS Deleting albums
-.PP
+T}
+T{
+### Deleting albums
+T}
+T{
 The Google Photos API does not support deleting albums \- see bug
 #135714733 (https://issuetracker.google.com/issues/135714733).
-.SS Standard Options
-.PP
+T}
+T{
+### Standard Options
+T}
+T{
 Here are the standard options specific to google photos (Google Photos).
-.SS \[en]gphotos\-client\-id
-.PP
-Google Application Client Id Leave blank normally.
-.IP \[bu] 2
-Config: client_id
-.IP \[bu] 2
-Env Var: RCLONE_GPHOTOS_CLIENT_ID
-.IP \[bu] 2
-Type: string
-.IP \[bu] 2
-Default: \[dq]\[dq]
-.SS \[en]gphotos\-client\-secret
-.PP
-Google Application Client Secret Leave blank normally.
-.IP \[bu] 2
-Config: client_secret
-.IP \[bu] 2
-Env Var: RCLONE_GPHOTOS_CLIENT_SECRET
-.IP \[bu] 2
-Type: string
-.IP \[bu] 2
-Default: \[dq]\[dq]
-.SS \[en]gphotos\-read\-only
-.PP
+T}
+T{
+#### \-\-gphotos\-client\-id
+T}
+T{
+OAuth Client Id Leave blank normally.
+T}
+T{
+\- Config: client_id \- Env Var: RCLONE_GPHOTOS_CLIENT_ID \- Type:
+string \- Default: \[dq]\[dq]
+T}
+T{
+#### \-\-gphotos\-client\-secret
+T}
+T{
+OAuth Client Secret Leave blank normally.
+T}
+T{
+\- Config: client_secret \- Env Var: RCLONE_GPHOTOS_CLIENT_SECRET \-
+Type: string \- Default: \[dq]\[dq]
+T}
+T{
+#### \-\-gphotos\-read\-only
+T}
+T{
 Set to make the Google Photos backend read only.
-.PP
+T}
+T{
 If you choose read only then rclone will only request read only access
 to your photos, otherwise rclone will request full access.
-.IP \[bu] 2
-Config: read_only
-.IP \[bu] 2
-Env Var: RCLONE_GPHOTOS_READ_ONLY
-.IP \[bu] 2
-Type: bool
-.IP \[bu] 2
-Default: false
-.SS Advanced Options
-.PP
+T}
+T{
+\- Config: read_only \- Env Var: RCLONE_GPHOTOS_READ_ONLY \- Type: bool
+\- Default: false
+T}
+T{
+### Advanced Options
+T}
+T{
 Here are the advanced options specific to google photos (Google Photos).
-.SS \[en]gphotos\-read\-size
-.PP
+T}
+T{
+#### \-\-gphotos\-token
+T}
+T{
+OAuth Access Token as a JSON blob.
+T}
+T{
+\- Config: token \- Env Var: RCLONE_GPHOTOS_TOKEN \- Type: string \-
+Default: \[dq]\[dq]
+T}
+T{
+#### \-\-gphotos\-auth\-url
+T}
+T{
+Auth server URL.
+Leave blank to use the provider defaults.
+T}
+T{
+\- Config: auth_url \- Env Var: RCLONE_GPHOTOS_AUTH_URL \- Type: string
+\- Default: \[dq]\[dq]
+T}
+T{
+#### \-\-gphotos\-token\-url
+T}
+T{
+Token server url.
+Leave blank to use the provider defaults.
+T}
+T{
+\- Config: token_url \- Env Var: RCLONE_GPHOTOS_TOKEN_URL \- Type:
+string \- Default: \[dq]\[dq]
+T}
+T{
+#### \-\-gphotos\-read\-size
+T}
+T{
 Set to read the size of media items.
-.PP
+T}
+T{
 Normally rclone does not read the size of media items since this takes
 another transaction.
-This isn\[cq]t necessary for syncing.
+This isn\[aq]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.
-.IP \[bu] 2
-Config: read_size
-.IP \[bu] 2
-Env Var: RCLONE_GPHOTOS_READ_SIZE
-.IP \[bu] 2
-Type: bool
-.IP \[bu] 2
-Default: false
-.SS \[en]gphotos\-start\-year
-.PP
+T}
+T{
+\- Config: read_size \- Env Var: RCLONE_GPHOTOS_READ_SIZE \- Type: bool
+\- Default: false
+T}
+T{
+#### \-\-gphotos\-start\-year
+T}
+T{
 Year limits the photos to be downloaded to those which are uploaded
 after the given year
-.IP \[bu] 2
-Config: start_year
-.IP \[bu] 2
-Env Var: RCLONE_GPHOTOS_START_YEAR
-.IP \[bu] 2
-Type: int
-.IP \[bu] 2
-Default: 2000
-.SS HTTP
+T}
+T{
+\- Config: start_year \- Env Var: RCLONE_GPHOTOS_START_YEAR \- Type: int
+\- Default: 2000
+T}
+T{
+HTTP
+T}
+.TE
 .PP
 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\[cq]t then please file an issue, or send a pull request!)
+(If it doesn\[aq]t then please file an issue, or send a pull request!)
 .PP
 Paths are specified as \f[C]remote:\f[R] or
 \f[C]remote:path/to/dir\f[R].
@@ -23907,12 +20980,12 @@ deleting any excess files.
 .IP
 .nf
 \f[C]
-rclone sync remote:directory /home/local/directory
+rclone sync \-i remote:directory /home/local/directory
 \f[R]
 .fi
 .SS Read only
 .PP
-This remote is read only \- you can\[cq]t upload files to an HTTP
+This remote is read only \- you can\[aq]t upload files to an HTTP
 server.
 .SS Modified time
 .PP
@@ -23933,7 +21006,7 @@ rclone lsd \-\-http\-url https://beta.rclone.org :http:
 .SS Standard Options
 .PP
 Here are the standard options specific to http (http Connection).
-.SS \[en]http\-url
+.SS \-\-http\-url
 .PP
 URL of http host to connect to
 .IP \[bu] 2
@@ -23948,13 +21021,13 @@ Default: \[dq]\[dq]
 Examples:
 .RS 2
 .IP \[bu] 2
-\[lq]https://example.com\[rq]
+\[dq]https://example.com\[dq]
 .RS 2
 .IP \[bu] 2
 Connect to example.com
 .RE
 .IP \[bu] 2
-\[lq]https://user:pass\[at]example.com\[rq]
+\[dq]https://user:pass\[at]example.com\[dq]
 .RS 2
 .IP \[bu] 2
 Connect to example.com using a username and password
@@ -23963,7 +21036,7 @@ Connect to example.com using a username and password
 .SS Advanced Options
 .PP
 Here are the advanced options specific to http (http Connection).
-.SS \[en]http\-headers
+.SS \-\-http\-headers
 .PP
 Set HTTP headers for all transactions
 .PP
@@ -23972,11 +21045,11 @@ Use this to set additional HTTP headers for all transactions
 The input format is comma separated list of key,value pairs.
 Standard CSV encoding (https://godoc.org/encoding/csv) may be used.
 .PP
-For example to set a Cookie use `Cookie,name=value', or
-`\[lq]Cookie\[rq],\[lq]name=value\[rq]'.
+For example to set a Cookie use \[aq]Cookie,name=value\[aq], or
+\[aq]\[dq]Cookie\[dq],\[dq]name=value\[dq]\[aq].
 .PP
 You can set multiple headers, eg
-`\[lq]Cookie\[rq],\[lq]name=value\[rq],\[lq]Authorization\[rq],\[lq]xxx\[rq]'.
+\[aq]\[dq]Cookie\[dq],\[dq]name=value\[dq],\[dq]Authorization\[dq],\[dq]xxx\[dq]\[aq].
 .IP \[bu] 2
 Config: headers
 .IP \[bu] 2
@@ -23985,9 +21058,9 @@ Env Var: RCLONE_HTTP_HEADERS
 Type: CommaSepList
 .IP \[bu] 2
 Default:
-.SS \[en]http\-no\-slash
+.SS \-\-http\-no\-slash
 .PP
-Set this if the site doesn\[cq]t end directories with /
+Set this if the site doesn\[aq]t end directories with /
 .PP
 Use this if your target website does not use / on the end of
 directories.
@@ -24008,9 +21081,9 @@ Env Var: RCLONE_HTTP_NO_SLASH
 Type: bool
 .IP \[bu] 2
 Default: false
-.SS \[en]http\-no\-head
+.SS \-\-http\-no\-head
 .PP
-Don\[cq]t use HEAD requests to find file sizes in dir listing
+Don\[aq]t use HEAD requests to find file sizes in dir listing
 .PP
 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
@@ -24027,9 +21100,9 @@ This will mean
 .IP \[bu] 2
 directory listings are much quicker
 .IP \[bu] 2
-rclone won\[cq]t have the times or sizes of any files
+rclone won\[aq]t have the times or sizes of any files
 .IP \[bu] 2
-some files that don\[cq]t exist may be in the listing
+some files that don\[aq]t exist may be in the listing
 .IP \[bu] 2
 Config: no_head
 .IP \[bu] 2
@@ -24147,7 +21220,7 @@ directory
 rclone copy /home/source remote:default/backup
 \f[R]
 .fi
-.SS \[en]fast\-list
+.SS \-\-fast\-list
 .PP
 This remote supports \f[C]\-\-fast\-list\f[R] which allows you to use
 fewer transactions in exchange for more memory.
@@ -24167,9 +21240,9 @@ are the same.
 .SS Standard Options
 .PP
 Here are the standard options specific to hubic (Hubic).
-.SS \[en]hubic\-client\-id
+.SS \-\-hubic\-client\-id
 .PP
-Hubic Client Id Leave blank normally.
+OAuth Client Id Leave blank normally.
 .IP \[bu] 2
 Config: client_id
 .IP \[bu] 2
@@ -24178,9 +21251,9 @@ Env Var: RCLONE_HUBIC_CLIENT_ID
 Type: string
 .IP \[bu] 2
 Default: \[dq]\[dq]
-.SS \[en]hubic\-client\-secret
+.SS \-\-hubic\-client\-secret
 .PP
-Hubic Client Secret Leave blank normally.
+OAuth Client Secret Leave blank normally.
 .IP \[bu] 2
 Config: client_secret
 .IP \[bu] 2
@@ -24192,7 +21265,42 @@ Default: \[dq]\[dq]
 .SS Advanced Options
 .PP
 Here are the advanced options specific to hubic (Hubic).
-.SS \[en]hubic\-chunk\-size
+.SS \-\-hubic\-token
+.PP
+OAuth Access Token as a JSON blob.
+.IP \[bu] 2
+Config: token
+.IP \[bu] 2
+Env Var: RCLONE_HUBIC_TOKEN
+.IP \[bu] 2
+Type: string
+.IP \[bu] 2
+Default: \[dq]\[dq]
+.SS \-\-hubic\-auth\-url
+.PP
+Auth server URL.
+Leave blank to use the provider defaults.
+.IP \[bu] 2
+Config: auth_url
+.IP \[bu] 2
+Env Var: RCLONE_HUBIC_AUTH_URL
+.IP \[bu] 2
+Type: string
+.IP \[bu] 2
+Default: \[dq]\[dq]
+.SS \-\-hubic\-token\-url
+.PP
+Token server url.
+Leave blank to use the provider defaults.
+.IP \[bu] 2
+Config: token_url
+.IP \[bu] 2
+Env Var: RCLONE_HUBIC_TOKEN_URL
+.IP \[bu] 2
+Type: string
+.IP \[bu] 2
+Default: \[dq]\[dq]
+.SS \-\-hubic\-chunk\-size
 .PP
 Above this size files will be chunked into a _segments container.
 .PP
@@ -24206,9 +21314,9 @@ Env Var: RCLONE_HUBIC_CHUNK_SIZE
 Type: SizeSuffix
 .IP \[bu] 2
 Default: 5G
-.SS \[en]hubic\-no\-chunk
+.SS \-\-hubic\-no\-chunk
 .PP
-Don\[cq]t chunk files during streaming upload.
+Don\[aq]t chunk files during streaming upload.
 .PP
 When doing streaming uploads (eg using rcat or mount) setting this flag
 will cause the swift backend to not upload chunked files.
@@ -24226,7 +21334,7 @@ Env Var: RCLONE_HUBIC_NO_CHUNK
 Type: bool
 .IP \[bu] 2
 Default: false
-.SS \[en]hubic\-encoding
+.SS \-\-hubic\-encoding
 .PP
 This sets the encoding for the backend.
 .PP
@@ -24245,8 +21353,8 @@ Default: Slash,InvalidUtf8
 This uses the normal OpenStack Swift mechanism to refresh the Swift API
 credentials and ignores the expires field returned by the Hubic API.
 .PP
-The Swift API doesn\[cq]t return a correct MD5SUM for segmented files
-(Dynamic or Static Large Objects) so rclone won\[cq]t check or use the
+The Swift API doesn\[aq]t return a correct MD5SUM for segmented files
+(Dynamic or Static Large Objects) so rclone won\[aq]t check or use the
 MD5SUM for these.
 .SS Jottacloud
 .PP
@@ -24262,6 +21370,7 @@ Paths are specified as \f[C]remote:path\f[R]
 Paths may be as deep as required, eg
 \f[C]remote:directory/subdirectory\f[R].
 .SS Setup
+.SS Default Setup
 .PP
 To configure Jottacloud you will need to generate a personal security
 token in the Jottacloud web interface.
@@ -24269,8 +21378,17 @@ You will the option to do in your account security
 settings (https://www.jottacloud.com/web/secure) (for whitelabel version
 you need to find this page in its web interface).
 Note that the web interface may refer to this token as a JottaCli token.
+.SS Legacy Setup
 .PP
-Here is an example of how to make a remote called \f[C]remote\f[R].
+If you are using one of the whitelabel versions (Elgiganten, Com Hem
+Cloud) you may not have the option to generate a CLI token.
+In this case you\[aq]ll have to use the legacy authentification.
+To to this select yes when the setup asks for legacy authentification
+and enter your username and password.
+The rest of the setup is identical to the default setup.
+.PP
+Here is an example of how to make a remote called \f[C]remote\f[R] with
+the default setup.
 First run:
 .IP
 .nf
@@ -24288,7 +21406,7 @@ n) New remote
 s) Set configuration password
 q) Quit config
 n/s/q> n
-name> jotta
+name> remote
 Type of storage to configure.
 Enter a string value. Press Enter for the default (\[dq]\[dq]).
 Choose a number from below, or type in your own value
@@ -24304,6 +21422,11 @@ y) Yes
 n) No
 y/n> n
 Remote config
+Use legacy authentification?.
+This is only required for certain whitelabel versions of Jottacloud and not recommended for normal users.
+y) Yes
+n) No (default)
+y/n> n
 
 Generate a personal login token here: https://www.jottacloud.com/web/secure
 Login Token> <your token here>
@@ -24316,9 +21439,8 @@ y/n> y
 Please select the device to use. Normally this will be Jotta
 Choose a number from below, or type in an existing value
  1 > DESKTOP\-3H31129
- 2 > fla1
- 3 > Jotta
-Devices> 3
+ 2 > Jotta
+Devices> 2
 Please select the mountpoint to user. Normally this will be Archive
 Choose a number from below, or type in an existing value
  1 > Archive
@@ -24329,7 +21451,6 @@ Mountpoints> 1
 \-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
 [jotta]
 type = jottacloud
-user = 0xC4KE\[at]gmail.com
 token = {........}
 device = Jotta
 mountpoint = Archive
@@ -24374,7 +21495,7 @@ install it on, and then creates a mountpoint for each folder you select
 for Backup.
 The web interface uses a special device called Jotta for the Archive and
 Sync mountpoints.
-In most cases you\[cq]ll want to use the Jotta/Archive
+In most cases you\[aq]ll want to use the Jotta/Archive
 device/mountpoint, however if you want to access files uploaded by any
 of the official clients rclone provides the option to select other
 devices and mountpoints during config.
@@ -24382,10 +21503,10 @@ devices and mountpoints during config.
 The built\-in Jotta device may also contain several other mountpoints,
 such as: Latest, Links, Shared and Trash.
 These are special mountpoints with a different internal representation
-than the \[lq]regular\[rq] mountpoints.
+than the \[dq]regular\[dq] mountpoints.
 Rclone will only to a very limited degree support them.
 Generally you should avoid these, unless you know what you are doing.
-.SS \[en]fast\-list
+.SS \-\-fast\-list
 .PP
 This remote supports \f[C]\-\-fast\-list\f[R] which allows you to use
 fewer transactions in exchange for more memory.
@@ -24409,7 +21530,7 @@ source does not have an MD5 checksum then the file will be cached
 temporarily on disk (wherever the \f[C]TMPDIR\f[R] environment variable
 points to) before it is uploaded.
 Small files will be cached in memory \- see the
-\[en]jottacloud\-md5\-memory\-limit flag.
+\-\-jottacloud\-md5\-memory\-limit flag.
 .SS Restricted filename characters
 .PP
 In addition to the default restricted characters
@@ -24479,14 +21600,14 @@ T}
 .TE
 .PP
 Invalid UTF\-8 bytes will also be
-replaced (https://rclone.org/overview/#invalid-utf8), as they can\[cq]t
+replaced (https://rclone.org/overview/#invalid-utf8), as they can\[aq]t
 be used in XML strings.
 .SS Deleting files
 .PP
 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 \[en]jottacloud\-hard\-delete flag, or set the equivalent
+using the \-\-jottacloud\-hard\-delete flag, or set the equivalent
 environment variable.
 Emptying the trash is supported by the
 cleanup (https://rclone.org/commands/rclone_cleanup/) command.
@@ -24505,7 +21626,7 @@ limit (unless it is unlimited) and the current usage.
 .SS Advanced Options
 .PP
 Here are the advanced options specific to jottacloud (Jottacloud).
-.SS \[en]jottacloud\-md5\-memory\-limit
+.SS \-\-jottacloud\-md5\-memory\-limit
 .PP
 Files bigger than this will be cached on disk to calculate the MD5 if
 required.
@@ -24517,7 +21638,7 @@ Env Var: RCLONE_JOTTACLOUD_MD5_MEMORY_LIMIT
 Type: SizeSuffix
 .IP \[bu] 2
 Default: 10M
-.SS \[en]jottacloud\-trashed\-only
+.SS \-\-jottacloud\-trashed\-only
 .PP
 Only show files that are in the trash.
 This will show trashed files in their original directory structure.
@@ -24529,7 +21650,7 @@ Env Var: RCLONE_JOTTACLOUD_TRASHED_ONLY
 Type: bool
 .IP \[bu] 2
 Default: false
-.SS \[en]jottacloud\-hard\-delete
+.SS \-\-jottacloud\-hard\-delete
 .PP
 Delete files permanently rather than putting them into the trash.
 .IP \[bu] 2
@@ -24540,23 +21661,9 @@ Env Var: RCLONE_JOTTACLOUD_HARD_DELETE
 Type: bool
 .IP \[bu] 2
 Default: false
-.SS \[en]jottacloud\-unlink
+.SS \-\-jottacloud\-upload\-resume\-limit
 .PP
-Remove existing public link to file/folder with link command rather than
-creating.
-Default is false, meaning link command will create or retrieve public
-link.
-.IP \[bu] 2
-Config: unlink
-.IP \[bu] 2
-Env Var: RCLONE_JOTTACLOUD_UNLINK
-.IP \[bu] 2
-Type: bool
-.IP \[bu] 2
-Default: false
-.SS \[en]jottacloud\-upload\-resume\-limit
-.PP
-Files bigger than this can be resumed if the upload fail\[cq]s.
+Files bigger than this can be resumed if the upload fail\[aq]s.
 .IP \[bu] 2
 Config: upload_resume_limit
 .IP \[bu] 2
@@ -24565,7 +21672,7 @@ Env Var: RCLONE_JOTTACLOUD_UPLOAD_RESUME_LIMIT
 Type: SizeSuffix
 .IP \[bu] 2
 Default: 10M
-.SS \[en]jottacloud\-encoding
+.SS \-\-jottacloud\-encoding
 .PP
 This sets the encoding for the backend.
 .PP
@@ -24582,10 +21689,10 @@ Default:
 Slash,LtGt,DoubleQuote,Colon,Question,Asterisk,Pipe,Del,Ctl,InvalidUtf8,Dot
 .SS Limitations
 .PP
-Note that Jottacloud is case insensitive so you can\[cq]t have a file
-called \[lq]Hello.doc\[rq] and one called \[lq]hello.doc\[rq].
+Note that Jottacloud is case insensitive so you can\[aq]t have a file
+called \[dq]Hello.doc\[dq] and one called \[dq]hello.doc\[dq].
 .PP
-There are quite a few characters that can\[cq]t be in Jottacloud file
+There are quite a few characters that can\[aq]t be in Jottacloud file
 names.
 Rclone will map these names to and from an identical looking unicode
 equivalent.
@@ -24728,12 +21835,12 @@ T}
 .TE
 .PP
 Invalid UTF\-8 bytes will also be
-replaced (https://rclone.org/overview/#invalid-utf8), as they can\[cq]t
+replaced (https://rclone.org/overview/#invalid-utf8), as they can\[aq]t
 be used in XML strings.
 .SS Standard Options
 .PP
 Here are the standard options specific to koofr (Koofr).
-.SS \[en]koofr\-user
+.SS \-\-koofr\-user
 .PP
 Your Koofr user name
 .IP \[bu] 2
@@ -24744,10 +21851,13 @@ Env Var: RCLONE_KOOFR_USER
 Type: string
 .IP \[bu] 2
 Default: \[dq]\[dq]
-.SS \[en]koofr\-password
+.SS \-\-koofr\-password
 .PP
 Your Koofr password for rclone (generate one at
 https://app.koofr.net/app/admin/preferences/password)
+.PP
+\f[B]NB\f[R] Input to this must be obscured \- see rclone
+obscure (https://rclone.org/commands/rclone_obscure/).
 .IP \[bu] 2
 Config: password
 .IP \[bu] 2
@@ -24759,7 +21869,7 @@ Default: \[dq]\[dq]
 .SS Advanced Options
 .PP
 Here are the advanced options specific to koofr (Koofr).
-.SS \[en]koofr\-endpoint
+.SS \-\-koofr\-endpoint
 .PP
 The Koofr API endpoint to use
 .IP \[bu] 2
@@ -24769,8 +21879,8 @@ Env Var: RCLONE_KOOFR_ENDPOINT
 .IP \[bu] 2
 Type: string
 .IP \[bu] 2
-Default: \[lq]https://app.koofr.net\[rq]
-.SS \[en]koofr\-mountid
+Default: \[dq]https://app.koofr.net\[dq]
+.SS \-\-koofr\-mountid
 .PP
 Mount ID of the mount to use.
 If omitted, the primary mount is used.
@@ -24782,7 +21892,7 @@ Env Var: RCLONE_KOOFR_MOUNTID
 Type: string
 .IP \[bu] 2
 Default: \[dq]\[dq]
-.SS \[en]koofr\-setmtime
+.SS \-\-koofr\-setmtime
 .PP
 Does the backend support setting modification time.
 Set this to false if you use a mount ID that points to a Dropbox or
@@ -24795,7 +21905,7 @@ Env Var: RCLONE_KOOFR_SETMTIME
 Type: bool
 .IP \[bu] 2
 Default: true
-.SS \[en]koofr\-encoding
+.SS \-\-koofr\-encoding
 .PP
 This sets the encoding for the backend.
 .PP
@@ -24811,8 +21921,8 @@ Type: MultiEncoder
 Default: Slash,BackSlash,Del,Ctl,InvalidUtf8,Dot
 .SS Limitations
 .PP
-Note that Koofr is case insensitive so you can\[cq]t have a file called
-\[lq]Hello.doc\[rq] and one called \[lq]hello.doc\[rq].
+Note that Koofr is case insensitive so you can\[aq]t have a file called
+\[dq]Hello.doc\[dq] and one called \[dq]hello.doc\[dq].
 .SS Mail.ru Cloud
 .PP
 Mail.ru Cloud (https://cloud.mail.ru/) is a cloud storage provided by a
@@ -24829,7 +21939,7 @@ Paths may be as deep as required, eg
 \f[C]remote:directory/subdirectory\f[R]
 .IP \[bu] 2
 Files have a \f[C]last modified time\f[R] property, directories
-don\[cq]t
+don\[aq]t
 .IP \[bu] 2
 Deleted files are by default moved to the trash
 .IP \[bu] 2
@@ -24950,15 +22060,15 @@ excess files in the path.
 .IP
 .nf
 \f[C]
-rclone sync /home/local/directory remote:directory
+rclone sync \-i /home/local/directory remote:directory
 \f[R]
 .fi
 .SS Modified time
 .PP
 Files support a modification time attribute with up to 1 second
 precision.
-Directories do not have a modification time, which is shown as \[lq]Jan
-1 1970\[rq].
+Directories do not have a modification time, which is shown as \[dq]Jan
+1 1970\[dq].
 .SS Hash checksums
 .PP
 Hash sums use a custom Mail.ru algorithm based on SHA1.
@@ -25056,7 +22166,7 @@ T}
 .TE
 .PP
 Invalid UTF\-8 bytes will also be
-replaced (https://rclone.org/overview/#invalid-utf8), as they can\[cq]t
+replaced (https://rclone.org/overview/#invalid-utf8), as they can\[aq]t
 be used in JSON strings.
 .SS Limitations
 .PP
@@ -25065,12 +22175,12 @@ 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.
 .PP
-Note that Mailru is case insensitive so you can\[cq]t have a file called
-\[lq]Hello.doc\[rq] and one called \[lq]hello.doc\[rq].
+Note that Mailru is case insensitive so you can\[aq]t have a file called
+\[dq]Hello.doc\[dq] and one called \[dq]hello.doc\[dq].
 .SS Standard Options
 .PP
 Here are the standard options specific to mailru (Mail.ru Cloud).
-.SS \[en]mailru\-user
+.SS \-\-mailru\-user
 .PP
 User name (usually email)
 .IP \[bu] 2
@@ -25081,9 +22191,12 @@ Env Var: RCLONE_MAILRU_USER
 Type: string
 .IP \[bu] 2
 Default: \[dq]\[dq]
-.SS \[en]mailru\-pass
+.SS \-\-mailru\-pass
 .PP
 Password
+.PP
+\f[B]NB\f[R] Input to this must be obscured \- see rclone
+obscure (https://rclone.org/commands/rclone_obscure/).
 .IP \[bu] 2
 Config: pass
 .IP \[bu] 2
@@ -25092,18 +22205,19 @@ Env Var: RCLONE_MAILRU_PASS
 Type: string
 .IP \[bu] 2
 Default: \[dq]\[dq]
-.SS \[en]mailru\-speedup\-enable
+.SS \-\-mailru\-speedup\-enable
 .PP
 Skip full upload if there is another file with same data hash.
-This feature is called \[lq]speedup\[rq] or \[lq]put by hash\[rq].
+This feature is called \[dq]speedup\[dq] or \[dq]put by hash\[dq].
 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.
 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.
+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.
 .IP \[bu] 2
 Config: speedup_enable
 .IP \[bu] 2
@@ -25116,13 +22230,13 @@ Default: true
 Examples:
 .RS 2
 .IP \[bu] 2
-\[lq]true\[rq]
+\[dq]true\[dq]
 .RS 2
 .IP \[bu] 2
 Enable
 .RE
 .IP \[bu] 2
-\[lq]false\[rq]
+\[dq]false\[dq]
 .RS 2
 .IP \[bu] 2
 Disable
@@ -25131,12 +22245,12 @@ Disable
 .SS Advanced Options
 .PP
 Here are the advanced options specific to mailru (Mail.ru Cloud).
-.SS \[en]mailru\-speedup\-file\-patterns
+.SS \-\-mailru\-speedup\-file\-patterns
 .PP
 Comma separated list of file name patterns eligible for speedup (put by
 hash).
-Patterns are case insensitive and can contain \[cq]*\[cq] or `?' meta
-characters.
+Patterns are case insensitive and can contain \[aq]*\[aq] or \[aq]?\[aq]
+meta characters.
 .IP \[bu] 2
 Config: speedup_file_patterns
 .IP \[bu] 2
@@ -25145,7 +22259,7 @@ Env Var: RCLONE_MAILRU_SPEEDUP_FILE_PATTERNS
 Type: string
 .IP \[bu] 2
 Default:
-\[lq]\f[I].mkv,\f[R].avi,\f[I].mp4,\f[R].mp3,\f[I].zip,\f[R].gz,\f[I].rar,\f[R].pdf\[rq]
+\[dq]\f[I].mkv,\f[R].avi,\f[I].mp4,\f[R].mp3,\f[I].zip,\f[R].gz,\f[I].rar,\f[R].pdf\[dq]
 .IP \[bu] 2
 Examples:
 .RS 2
@@ -25162,19 +22276,19 @@ Empty list completely disables speedup (put by hash).
 All files will be attempted for speedup.
 .RE
 .IP \[bu] 2
-\[lq]\f[I].mkv,\f[R].avi,\f[I].mp4,\f[R].mp3\[rq]
+\[dq]\f[I].mkv,\f[R].avi,\f[I].mp4,\f[R].mp3\[dq]
 .RS 2
 .IP \[bu] 2
 Only common audio/video files will be tried for put by hash.
 .RE
 .IP \[bu] 2
-\[lq]\f[I].zip,\f[R].gz,\f[I].rar,\f[R].pdf\[rq]
+\[dq]\f[I].zip,\f[R].gz,\f[I].rar,\f[R].pdf\[dq]
 .RS 2
 .IP \[bu] 2
 Only common archives or PDF books will be tried for speedup.
 .RE
 .RE
-.SS \[en]mailru\-speedup\-max\-disk
+.SS \-\-mailru\-speedup\-max\-disk
 .PP
 This option allows you to disable speedup (put by hash) for large files
 (because preliminary hashing can exhaust you RAM or disk space)
@@ -25190,25 +22304,25 @@ Default: 3G
 Examples:
 .RS 2
 .IP \[bu] 2
-\[lq]0\[rq]
+\[dq]0\[dq]
 .RS 2
 .IP \[bu] 2
 Completely disable speedup (put by hash).
 .RE
 .IP \[bu] 2
-\[lq]1G\[rq]
+\[dq]1G\[dq]
 .RS 2
 .IP \[bu] 2
 Files larger than 1Gb will be uploaded directly.
 .RE
 .IP \[bu] 2
-\[lq]3G\[rq]
+\[dq]3G\[dq]
 .RS 2
 .IP \[bu] 2
 Choose this option if you have less than 3Gb free on local disk.
 .RE
 .RE
-.SS \[en]mailru\-speedup\-max\-memory
+.SS \-\-mailru\-speedup\-max\-memory
 .PP
 Files larger than the size given below will always be hashed on disk.
 .IP \[bu] 2
@@ -25223,25 +22337,25 @@ Default: 32M
 Examples:
 .RS 2
 .IP \[bu] 2
-\[lq]0\[rq]
+\[dq]0\[dq]
 .RS 2
 .IP \[bu] 2
 Preliminary hashing will always be done in a temporary disk location.
 .RE
 .IP \[bu] 2
-\[lq]32M\[rq]
+\[dq]32M\[dq]
 .RS 2
 .IP \[bu] 2
 Do not dedicate more than 32Mb RAM for preliminary hashing.
 .RE
 .IP \[bu] 2
-\[lq]256M\[rq]
+\[dq]256M\[dq]
 .RS 2
 .IP \[bu] 2
 You have at most 256Mb RAM free for hash calculations.
 .RE
 .RE
-.SS \[en]mailru\-check\-hash
+.SS \-\-mailru\-check\-hash
 .PP
 What should copy do if file checksum is mismatched or invalid
 .IP \[bu] 2
@@ -25256,22 +22370,22 @@ Default: true
 Examples:
 .RS 2
 .IP \[bu] 2
-\[lq]true\[rq]
+\[dq]true\[dq]
 .RS 2
 .IP \[bu] 2
 Fail with error.
 .RE
 .IP \[bu] 2
-\[lq]false\[rq]
+\[dq]false\[dq]
 .RS 2
 .IP \[bu] 2
 Ignore and continue.
 .RE
 .RE
-.SS \[en]mailru\-user\-agent
+.SS \-\-mailru\-user\-agent
 .PP
 HTTP user agent used internally by client.
-Defaults to \[lq]rclone/VERSION\[rq] or \[lq]\[en]user\-agent\[rq]
+Defaults to \[dq]rclone/VERSION\[dq] or \[dq]\-\-user\-agent\[dq]
 provided on command line.
 .IP \[bu] 2
 Config: user_agent
@@ -25281,7 +22395,7 @@ Env Var: RCLONE_MAILRU_USER_AGENT
 Type: string
 .IP \[bu] 2
 Default: \[dq]\[dq]
-.SS \[en]mailru\-quirks
+.SS \-\-mailru\-quirks
 .PP
 Comma separated list of internal maintenance flags.
 This option must not be used by an ordinary user.
@@ -25299,7 +22413,7 @@ Env Var: RCLONE_MAILRU_QUIRKS
 Type: string
 .IP \[bu] 2
 Default: \[dq]\[dq]
-.SS \[en]mailru\-encoding
+.SS \-\-mailru\-encoding
 .PP
 This sets the encoding for the backend.
 .PP
@@ -25443,7 +22557,7 @@ T}
 .TE
 .PP
 Invalid UTF\-8 bytes will also be
-replaced (https://rclone.org/overview/#invalid-utf8), as they can\[cq]t
+replaced (https://rclone.org/overview/#invalid-utf8), as they can\[aq]t
 be used in JSON strings.
 .SS Duplicated files
 .PP
@@ -25456,17 +22570,18 @@ messages in the log about duplicates.
 Use \f[C]rclone dedupe\f[R] to fix duplicated files.
 .SS Failure to log\-in
 .PP
-Mega remotes seem to get blocked (reject logins) under \[lq]heavy
-use\[rq].
-We haven\[cq]t worked out the exact blocking rules but it seems to be
+Mega remotes seem to get blocked (reject logins) under \[dq]heavy
+use\[dq].
+We haven\[aq]t worked out the exact blocking rules but it seems to be
 related to fast paced, successive rclone commands.
 .PP
 For example, executing this command 90 times in a row
 \f[C]rclone link remote:file\f[R] will cause the remote to become
-\[lq]blocked\[rq].
+\[dq]blocked\[dq].
 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.
+public links of a directory with hundred of files...
+After more or less a week, the remote will remote accept rclone logins
+normally again.
 .PP
 You can mitigate this issue by mounting the remote it with
 \f[C]rclone mount\f[R].
@@ -25479,16 +22594,16 @@ web interface), however closing the sessions does not solve the issue.
 .PP
 If you space rclone commands by 3 seconds it will avoid blocking the
 remote.
-We haven\[cq]t identified the exact blocking rules, so perhaps one could
+We haven\[aq]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\&...
+waiting 3 seconds, then continuing...
 .PP
 Note that this has been observed by trial and error and might not be set
 in stone.
 .PP
 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\[cq]t compatible with the current stateless rclone
+log\-in) which isn\[aq]t compatible with the current stateless rclone
 approach.
 .PP
 Note that once blocked, the use of other tools (such as megacmd) is not
@@ -25506,7 +22621,7 @@ got the remote blocked for a while.
 .SS Standard Options
 .PP
 Here are the standard options specific to mega (Mega).
-.SS \[en]mega\-user
+.SS \-\-mega\-user
 .PP
 User name
 .IP \[bu] 2
@@ -25517,9 +22632,12 @@ Env Var: RCLONE_MEGA_USER
 Type: string
 .IP \[bu] 2
 Default: \[dq]\[dq]
-.SS \[en]mega\-pass
+.SS \-\-mega\-pass
 .PP
 Password.
+.PP
+\f[B]NB\f[R] Input to this must be obscured \- see rclone
+obscure (https://rclone.org/commands/rclone_obscure/).
 .IP \[bu] 2
 Config: pass
 .IP \[bu] 2
@@ -25531,7 +22649,7 @@ Default: \[dq]\[dq]
 .SS Advanced Options
 .PP
 Here are the advanced options specific to mega (Mega).
-.SS \[en]mega\-debug
+.SS \-\-mega\-debug
 .PP
 Output more debug from Mega.
 .PP
@@ -25545,7 +22663,7 @@ Env Var: RCLONE_MEGA_DEBUG
 Type: bool
 .IP \[bu] 2
 Default: false
-.SS \[en]mega\-hard\-delete
+.SS \-\-mega\-hard\-delete
 .PP
 Delete files permanently rather than putting them into the trash.
 .PP
@@ -25560,7 +22678,7 @@ Env Var: RCLONE_MEGA_HARD_DELETE
 Type: bool
 .IP \[bu] 2
 Default: false
-.SS \[en]mega\-encoding
+.SS \-\-mega\-encoding
 .PP
 This sets the encoding for the backend.
 .PP
@@ -25579,7 +22697,7 @@ Default: Slash,InvalidUtf8,Dot
 This backend uses the go\-mega go
 library (https://github.com/t3rm1n4l/go-mega) which is an opensource go
 library implementing the Mega API.
-There doesn\[cq]t appear to be any documentation for the mega protocol
+There doesn\[aq]t appear to be any documentation for the mega protocol
 beyond the mega C++ SDK (https://github.com/meganz/sdk) source code so
 there are likely quite a few errors still remaining in this library.
 .PP
@@ -25627,7 +22745,7 @@ y/e/d> y
 \f[R]
 .fi
 .PP
-Because the memory backend isn\[cq]t persistent it is most useful for
+Because the memory backend isn\[aq]t persistent it is most useful for
 testing or with an rclone server or rclone mount, eg
 .IP
 .nf
@@ -25728,10 +22846,10 @@ any excess files in the container.
 .IP
 .nf
 \f[C]
-rclone sync /home/local/directory remote:container
+rclone sync \-i /home/local/directory remote:container
 \f[R]
 .fi
-.SS \[en]fast\-list
+.SS \-\-fast\-list
 .PP
 This remote supports \f[C]\-\-fast\-list\f[R] which allows you to use
 fewer transactions in exchange for more memory.
@@ -25801,7 +22919,7 @@ T}
 .TE
 .PP
 Invalid UTF\-8 bytes will also be
-replaced (https://rclone.org/overview/#invalid-utf8), as they can\[cq]t
+replaced (https://rclone.org/overview/#invalid-utf8), as they can\[aq]t
 be used in JSON strings.
 .SS Hashes
 .PP
@@ -25847,7 +22965,7 @@ container/
 \f[R]
 .fi
 .PP
-Note that you can\[cq]t see or access any other containers \- this will
+Note that you can\[aq]t see or access any other containers \- this will
 fail
 .IP
 .nf
@@ -25869,7 +22987,7 @@ The files will be uploaded in parallel in 4MB chunks (by default).
 Note that these chunks are buffered in memory and there may be up to
 \f[C]\-\-transfers\f[R] of them being uploaded at once.
 .PP
-Files can\[cq]t be split into more than 50,000 chunks so by default, so
+Files can\[aq]t be split into more than 50,000 chunks so by default, so
 the largest file that can be uploaded with 4MB chunk size is 195GB.
 Above this rclone will double the chunk size until it creates less than
 50,000 chunks.
@@ -25877,15 +22995,15 @@ By default this will mean a maximum file size of 3.2TB can be uploaded.
 This can be raised to 5TB using
 \f[C]\-\-azureblob\-chunk\-size 100M\f[R].
 .PP
-Note that rclone doesn\[cq]t commit the block list until the end of the
+Note that rclone doesn\[aq]t commit the block list until the end of the
 upload which means that there is a limit of 9.5TB of multipart uploads
-in progress as Azure won\[cq]t allow more than that amount of
+in progress as Azure won\[aq]t allow more than that amount of
 uncommitted blocks.
 .SS Standard Options
 .PP
 Here are the standard options specific to azureblob (Microsoft Azure
 Blob Storage).
-.SS \[en]azureblob\-account
+.SS \-\-azureblob\-account
 .PP
 Storage Account Name (leave blank to use SAS URL or Emulator)
 .IP \[bu] 2
@@ -25896,7 +23014,7 @@ Env Var: RCLONE_AZUREBLOB_ACCOUNT
 Type: string
 .IP \[bu] 2
 Default: \[dq]\[dq]
-.SS \[en]azureblob\-key
+.SS \-\-azureblob\-key
 .PP
 Storage Account Key (leave blank to use SAS URL or Emulator)
 .IP \[bu] 2
@@ -25907,7 +23025,7 @@ Env Var: RCLONE_AZUREBLOB_KEY
 Type: string
 .IP \[bu] 2
 Default: \[dq]\[dq]
-.SS \[en]azureblob\-sas\-url
+.SS \-\-azureblob\-sas\-url
 .PP
 SAS URL for container level access only (leave blank if using
 account/key or Emulator)
@@ -25919,10 +23037,10 @@ Env Var: RCLONE_AZUREBLOB_SAS_URL
 Type: string
 .IP \[bu] 2
 Default: \[dq]\[dq]
-.SS \[en]azureblob\-use\-emulator
+.SS \-\-azureblob\-use\-emulator
 .PP
-Uses local storage emulator if provided as `true' (leave blank if using
-real azure storage endpoint)
+Uses local storage emulator if provided as \[aq]true\[aq] (leave blank
+if using real azure storage endpoint)
 .IP \[bu] 2
 Config: use_emulator
 .IP \[bu] 2
@@ -25935,7 +23053,7 @@ Default: false
 .PP
 Here are the advanced options specific to azureblob (Microsoft Azure
 Blob Storage).
-.SS \[en]azureblob\-endpoint
+.SS \-\-azureblob\-endpoint
 .PP
 Endpoint for the service Leave blank normally.
 .IP \[bu] 2
@@ -25946,7 +23064,7 @@ Env Var: RCLONE_AZUREBLOB_ENDPOINT
 Type: string
 .IP \[bu] 2
 Default: \[dq]\[dq]
-.SS \[en]azureblob\-upload\-cutoff
+.SS \-\-azureblob\-upload\-cutoff
 .PP
 Cutoff for switching to chunked upload (<= 256MB).
 .IP \[bu] 2
@@ -25957,12 +23075,12 @@ Env Var: RCLONE_AZUREBLOB_UPLOAD_CUTOFF
 Type: SizeSuffix
 .IP \[bu] 2
 Default: 256M
-.SS \[en]azureblob\-chunk\-size
+.SS \-\-azureblob\-chunk\-size
 .PP
 Upload chunk size (<= 100MB).
 .PP
 Note that this is stored in memory and there may be up to
-\[lq]\[en]transfers\[rq] chunks stored at once in memory.
+\[dq]\-\-transfers\[dq] chunks stored at once in memory.
 .IP \[bu] 2
 Config: chunk_size
 .IP \[bu] 2
@@ -25971,13 +23089,13 @@ Env Var: RCLONE_AZUREBLOB_CHUNK_SIZE
 Type: SizeSuffix
 .IP \[bu] 2
 Default: 4M
-.SS \[en]azureblob\-list\-chunk
+.SS \-\-azureblob\-list\-chunk
 .PP
 Size of blob list.
 .PP
 This sets the number of blobs requested in each listing chunk.
 Default is the maximum, 5000.
-\[lq]List blobs\[rq] requests are permitted 2 minutes per megabyte to
+\[dq]List blobs\[dq] 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 (
@@ -25993,7 +23111,7 @@ Env Var: RCLONE_AZUREBLOB_LIST_CHUNK
 Type: int
 .IP \[bu] 2
 Default: 5000
-.SS \[en]azureblob\-access\-tier
+.SS \-\-azureblob\-access\-tier
 .PP
 Access tier of blob: hot, cool or archive.
 .PP
@@ -26001,15 +23119,15 @@ Archived blobs can be restored by setting access tier to hot or cool.
 Leave blank if you intend to use default access tier, which is set at
 account level
 .PP
-If there is no \[lq]access tier\[rq] specified, rclone doesn\[cq]t apply
+If there is no \[dq]access tier\[dq] specified, rclone doesn\[aq]t apply
 any tier.
-rclone performs \[lq]Set Tier\[rq] operation on blobs while uploading,
-if objects are not modified, specifying \[lq]access tier\[rq] to new one
+rclone performs \[dq]Set Tier\[dq] operation on blobs while uploading,
+if objects are not modified, specifying \[dq]access tier\[dq] to new one
 will have no effect.
-If blobs are in \[lq]archive tier\[rq] at remote, trying to perform data
+If blobs are in \[dq]archive tier\[dq] at remote, trying to perform data
 transfer operations from remote will not be allowed.
-User should first restore by tiering blob to \[lq]Hot\[rq] or
-\[lq]Cool\[rq].
+User should first restore by tiering blob to \[dq]Hot\[dq] or
+\[dq]Cool\[dq].
 .IP \[bu] 2
 Config: access_tier
 .IP \[bu] 2
@@ -26018,9 +23136,9 @@ Env Var: RCLONE_AZUREBLOB_ACCESS_TIER
 Type: string
 .IP \[bu] 2
 Default: \[dq]\[dq]
-.SS \[en]azureblob\-disable\-checksum
+.SS \-\-azureblob\-disable\-checksum
 .PP
-Don\[cq]t store MD5 checksum with object metadata.
+Don\[aq]t store MD5 checksum with object metadata.
 .PP
 Normally rclone will calculate the MD5 checksum of the input before
 uploading it so it can add it to metadata on the object.
@@ -26034,7 +23152,7 @@ Env Var: RCLONE_AZUREBLOB_DISABLE_CHECKSUM
 Type: bool
 .IP \[bu] 2
 Default: false
-.SS \[en]azureblob\-memory\-pool\-flush\-time
+.SS \-\-azureblob\-memory\-pool\-flush\-time
 .PP
 How often internal memory buffer pools will be flushed.
 Uploads which requires additional buffers (f.e multipart) will use
@@ -26049,7 +23167,7 @@ Env Var: RCLONE_AZUREBLOB_MEMORY_POOL_FLUSH_TIME
 Type: Duration
 .IP \[bu] 2
 Default: 1m0s
-.SS \[en]azureblob\-memory\-pool\-use\-mmap
+.SS \-\-azureblob\-memory\-pool\-use\-mmap
 .PP
 Whether to use mmap buffers in internal memory pool.
 .IP \[bu] 2
@@ -26060,7 +23178,7 @@ Env Var: RCLONE_AZUREBLOB_MEMORY_POOL_USE_MMAP
 Type: bool
 .IP \[bu] 2
 Default: false
-.SS \[en]azureblob\-encoding
+.SS \-\-azureblob\-encoding
 .PP
 This sets the encoding for the backend.
 .PP
@@ -26222,7 +23340,7 @@ rclone copy /home/source remote:backup
 .SS Getting your own Client ID and Key
 .PP
 You can use your own Client ID if the default (\f[C]client_id\f[R] left
-blank) one doesn\[cq]t work for you or you see lots of throttling.
+blank) one doesn\[aq]t work for you or you see lots of throttling.
 The default Client ID and Key is shared by all rclone users when
 performing requests.
 .PP
@@ -26230,8 +23348,8 @@ If you are having problems with them (E.g., seeing a lot of throttling),
 you can get your own Client ID and Key by following the steps below:
 .IP "1." 3
 Open
-https://portal.azure.com/#blade/Microsoft_AAD_RegisteredApps/ApplicationsListBlade,
-then click \f[C]New registration\f[R].
+https://portal.azure.com/#blade/Microsoft_AAD_RegisteredApps/ApplicationsListBlade
+and then click \f[C]New registration\f[R].
 .IP "2." 3
 Enter a name for your app, choose account type
 \f[C]Accounts in any organizational directory (Any Azure AD directory \- Multitenant) and personal Microsoft accounts (e.g. Skype, Xbox)\f[R],
@@ -26419,20 +23537,20 @@ T}
 .TE
 .PP
 Invalid UTF\-8 bytes will also be
-replaced (https://rclone.org/overview/#invalid-utf8), as they can\[cq]t
+replaced (https://rclone.org/overview/#invalid-utf8), as they can\[aq]t
 be used in JSON strings.
 .SS Deleting files
 .PP
 Any files you delete with rclone will end up in the trash.
-Microsoft doesn\[cq]t provide an API to permanently delete files, nor to
-empty the trash, so you will have to do that with one of Microsoft\[cq]s
+Microsoft doesn\[aq]t provide an API to permanently delete files, nor to
+empty the trash, so you will have to do that with one of Microsoft\[aq]s
 apps or via the OneDrive website.
 .SS Standard Options
 .PP
 Here are the standard options specific to onedrive (Microsoft OneDrive).
-.SS \[en]onedrive\-client\-id
+.SS \-\-onedrive\-client\-id
 .PP
-Microsoft App Client Id Leave blank normally.
+OAuth Client Id Leave blank normally.
 .IP \[bu] 2
 Config: client_id
 .IP \[bu] 2
@@ -26441,9 +23559,9 @@ Env Var: RCLONE_ONEDRIVE_CLIENT_ID
 Type: string
 .IP \[bu] 2
 Default: \[dq]\[dq]
-.SS \[en]onedrive\-client\-secret
+.SS \-\-onedrive\-client\-secret
 .PP
-Microsoft App Client Secret Leave blank normally.
+OAuth Client Secret Leave blank normally.
 .IP \[bu] 2
 Config: client_secret
 .IP \[bu] 2
@@ -26455,7 +23573,42 @@ Default: \[dq]\[dq]
 .SS Advanced Options
 .PP
 Here are the advanced options specific to onedrive (Microsoft OneDrive).
-.SS \[en]onedrive\-chunk\-size
+.SS \-\-onedrive\-token
+.PP
+OAuth Access Token as a JSON blob.
+.IP \[bu] 2
+Config: token
+.IP \[bu] 2
+Env Var: RCLONE_ONEDRIVE_TOKEN
+.IP \[bu] 2
+Type: string
+.IP \[bu] 2
+Default: \[dq]\[dq]
+.SS \-\-onedrive\-auth\-url
+.PP
+Auth server URL.
+Leave blank to use the provider defaults.
+.IP \[bu] 2
+Config: auth_url
+.IP \[bu] 2
+Env Var: RCLONE_ONEDRIVE_AUTH_URL
+.IP \[bu] 2
+Type: string
+.IP \[bu] 2
+Default: \[dq]\[dq]
+.SS \-\-onedrive\-token\-url
+.PP
+Token server url.
+Leave blank to use the provider defaults.
+.IP \[bu] 2
+Config: token_url
+.IP \[bu] 2
+Env Var: RCLONE_ONEDRIVE_TOKEN_URL
+.IP \[bu] 2
+Type: string
+.IP \[bu] 2
+Default: \[dq]\[dq]
+.SS \-\-onedrive\-chunk\-size
 .PP
 Chunk size to upload files with \- must be multiple of 320k (327,680
 bytes).
@@ -26474,7 +23627,7 @@ Env Var: RCLONE_ONEDRIVE_CHUNK_SIZE
 Type: SizeSuffix
 .IP \[bu] 2
 Default: 10M
-.SS \[en]onedrive\-drive\-id
+.SS \-\-onedrive\-drive\-id
 .PP
 The ID of the drive to use
 .IP \[bu] 2
@@ -26485,7 +23638,7 @@ Env Var: RCLONE_ONEDRIVE_DRIVE_ID
 Type: string
 .IP \[bu] 2
 Default: \[dq]\[dq]
-.SS \[en]onedrive\-drive\-type
+.SS \-\-onedrive\-drive\-type
 .PP
 The type of the drive ( personal | business | documentLibrary )
 .IP \[bu] 2
@@ -26496,12 +23649,12 @@ Env Var: RCLONE_ONEDRIVE_DRIVE_TYPE
 Type: string
 .IP \[bu] 2
 Default: \[dq]\[dq]
-.SS \[en]onedrive\-expose\-onenote\-files
+.SS \-\-onedrive\-expose\-onenote\-files
 .PP
 Set to make OneNote files show up in directory listings.
 .PP
 By default rclone will hide OneNote files in directory listings because
-operations like \[lq]Open\[rq] and \[lq]Update\[rq] won\[cq]t work on
+operations like \[dq]Open\[dq] and \[dq]Update\[dq] won\[aq]t work on
 them.
 But this behaviour may also prevent you from deleting them.
 If you want to delete OneNote files or otherwise want them to show up in
@@ -26514,14 +23667,14 @@ Env Var: RCLONE_ONEDRIVE_EXPOSE_ONENOTE_FILES
 Type: bool
 .IP \[bu] 2
 Default: false
-.SS \[en]onedrive\-server\-side\-across\-configs
+.SS \-\-onedrive\-server\-side\-across\-configs
 .PP
 Allow server side operations (eg copy) to work across different onedrive
 configs.
 .PP
 This can be useful if you wish to do a server side copy between two
 different Onedrives.
-Note that this isn\[cq]t enabled by default because it isn\[cq]t easy to
+Note that this isn\[aq]t enabled by default because it isn\[aq]t easy to
 tell if it will work between any two configurations.
 .IP \[bu] 2
 Config: server_side_across_configs
@@ -26531,7 +23684,29 @@ Env Var: RCLONE_ONEDRIVE_SERVER_SIDE_ACROSS_CONFIGS
 Type: bool
 .IP \[bu] 2
 Default: false
-.SS \[en]onedrive\-encoding
+.SS \-\-onedrive\-no\-versions
+.PP
+Remove all versions on modifying operations
+.PP
+Onedrive for business creates versions when rclone uploads new files
+overwriting an existing one and when it sets the modification time.
+.PP
+These versions take up space out of the quota.
+.PP
+This flag checks for versions after file upload and setting modification
+time and removes all but the last version.
+.PP
+\f[B]NB\f[R] Onedrive personal can\[aq]t currently delete versions so
+don\[aq]t use this flag there.
+.IP \[bu] 2
+Config: no_versions
+.IP \[bu] 2
+Env Var: RCLONE_ONEDRIVE_NO_VERSIONS
+.IP \[bu] 2
+Type: bool
+.IP \[bu] 2
+Default: false
+.SS \-\-onedrive\-encoding
 .PP
 This sets the encoding for the backend.
 .PP
@@ -26547,14 +23722,20 @@ Type: MultiEncoder
 Default:
 Slash,LtGt,DoubleQuote,Colon,Question,Asterisk,Pipe,Hash,Percent,BackSlash,Del,Ctl,LeftSpace,LeftTilde,RightSpace,RightPeriod,InvalidUtf8,Dot
 .SS Limitations
+.PP
+If you don\[aq]t use rclone for 90 days the refresh token will expire.
+This will result in authorization problems.
+This is easy to fix by running the
+\f[C]rclone config reconnect remote:\f[R] command to get a new token and
+refresh token.
 .SS Naming
 .PP
-Note that OneDrive is case insensitive so you can\[cq]t have a file
-called \[lq]Hello.doc\[rq] and one called \[lq]hello.doc\[rq].
+Note that OneDrive is case insensitive so you can\[aq]t have a file
+called \[dq]Hello.doc\[dq] and one called \[dq]hello.doc\[dq].
 .PP
-There are quite a few characters that can\[cq]t be in OneDrive file
+There are quite a few characters that can\[aq]t be in OneDrive file
 names.
-These can\[cq]t occur on Windows platforms, but on non\-Windows
+These can\[aq]t occur on Windows platforms, but on non\-Windows
 platforms they are common.
 Rclone will map these names to and from an identical looking unicode
 equivalent.
@@ -26562,10 +23743,9 @@ For example if a file has a \f[C]?\f[R] in it will be mapped to
 \f[C]\[uFF1F]\f[R] instead.
 .SS File sizes
 .PP
-The largest allowed file sizes are 15GB for OneDrive for Business and
-100GB for OneDrive Personal (Updated 19 May 2020).
-Source:
-https://support.office.com/en\-us/article/upload\-photos\-and\-files\-to\-onedrive\-b00ad3fe\-6643\-4b16\-9212\-de00ef02b586
+The largest allowed file size is 100GB for both OneDrive Personal and
+OneDrive for Business (Updated 17 June
+2020) (https://support.microsoft.com/en-us/office/invalid-file-names-and-file-types-in-onedrive-and-sharepoint-64883a5d-228e-48f5-b3d2-eb39e07630fa?ui=en-us&rs=en-us&ad=us#individualfilesize).
 .SS Path length
 .PP
 The entire path, including the file name, must contain fewer than 400
@@ -26583,19 +23763,33 @@ See #2707 (https://github.com/rclone/rclone/issues/2707) for more info.
 An official document about the limitations for different types of
 OneDrive can be found
 here (https://support.office.com/en-us/article/invalid-file-names-and-file-types-in-onedrive-onedrive-for-business-and-sharepoint-64883a5d-228e-48f5-b3d2-eb39e07630fa).
-.SS Versioning issue
+.SS Versions
 .PP
-Every change in OneDrive causes the service to create a new version.
+Every change in a file OneDrive causes the service to create a new
+version of the the file.
 This counts against a users quota.
 For example changing the modification time of a file creates a second
-version, so the file is using twice the space.
+version, so the file apparently uses twice the space.
 .PP
-The \f[C]copy\f[R] is the only rclone command affected by this as we
-copy the file and then afterwards set the modification time to match the
-source file.
+For example the \f[C]copy\f[R] command is affected by this as rclone
+copies the file and then afterwards sets the modification time to match
+the source file which uses another version.
 .PP
-\f[B]Note\f[R]: Starting October 2018, users will no longer be able to
-disable versioning by default.
+You can use the \f[C]rclone cleanup\f[R] command (see below) to remove
+all old versions.
+.PP
+Or you can set the \f[C]no_versions\f[R] parameter to \f[C]true\f[R] and
+rclone will remove versions after operations which create new versions.
+This takes extra transactions so only enable it if you need it.
+.PP
+\f[B]Note\f[R] At the time of writing Onedrive Personal creates versions
+(but not for setting the modification time) but the API for removing
+them returns \[dq]API not found\[dq] so cleanup and
+\f[C]no_versions\f[R] should not be used on Onedrive Personal.
+.SS Disabling versioning
+.PP
+Starting October 2018, users will no longer be able to disable
+versioning by default.
 This is because Microsoft has brought an
 update (https://techcommunity.microsoft.com/t5/Microsoft-OneDrive-Blog/New-Updates-to-OneDrive-and-SharePoint-Team-Site-Versioning/ba-p/204390)
 to the mechanism.
@@ -26605,7 +23799,7 @@ If you are an admin, you can run these commands in PowerShell to change
 that setting:
 .IP "1." 3
 \f[C]Install\-Module \-Name Microsoft.Online.SharePoint.PowerShell\f[R]
-(in case you haven\[cq]t installed this already)
+(in case you haven\[aq]t installed this already)
 .IP "2." 3
 \f[C]Import\-Module Microsoft.Online.SharePoint.PowerShell \-DisableNameChecking\f[R]
 .IP "3." 3
@@ -26618,7 +23812,7 @@ with the actual values; this will prompt for your credentials)
 \f[C]Disconnect\-SPOService\f[R] (to disconnect from the server)
 .PP
 \f[I]Below are the steps for normal users to disable versioning. If you
-don\[cq]t see the \[lq]No Versioning\[rq] option, make sure the above
+don\[aq]t see the \[dq]No Versioning\[dq] option, make sure the above
 requirements are met.\f[R]
 .PP
 User Weropol (https://github.com/Weropol) has found a method to disable
@@ -26632,7 +23826,7 @@ Click Site settings.
 Once on the Site settings page, navigate to Site Administration > Site
 libraries and lists.
 .IP "4." 3
-Click Customize \[lq]Documents\[rq].
+Click Customize \[dq]Documents\[dq].
 .IP "5." 3
 Click General Settings > Versioning Settings.
 .IP "6." 3
@@ -26644,10 +23838,29 @@ Your documents are safe.
 Apply the changes by clicking OK.
 .IP "8." 3
 Use rclone to upload or modify files.
-(I also use the \[en]no\-update\-modtime flag)
+(I also use the \-\-no\-update\-modtime flag)
 .IP "9." 3
 Restore the versioning settings after using rclone.
 (Optional)
+.SS Cleanup
+.PP
+OneDrive supports \f[C]rclone cleanup\f[R] which causes rclone to look
+through every file under the path supplied and delete all version but
+the current version.
+Because this involves traversing all the files, then querying each file
+for versions it can be quite slow.
+Rclone does \f[C]\-\-checkers\f[R] tests in parallel.
+The command also supports \f[C]\-i\f[R] which is a great way to see what
+it would do.
+.IP
+.nf
+\f[C]
+rclone cleanup \-i remote:path/subdir # interactively remove all old version for path/subdir
+rclone cleanup remote:path/subdir    # unconditionally remove all old version for path/subdir
+\f[R]
+.fi
+.PP
+\f[B]NB\f[R] Onedrive personal can\[aq]t currently delete versions
 .SS Troubleshooting
 .SS Unexpected file size/hash differences on Sharepoint
 .PP
@@ -26656,6 +23869,8 @@ known (https://github.com/OneDrive/onedrive-api-docs/issues/935#issuecomment-441
 issue that Sharepoint (not OneDrive or OneDrive for Business) silently
 modifies uploaded files, mainly Office files (.docx, .xlsx, etc.),
 causing file size and hash checks to fail.
+There are also other situations that will cause OneDrive to report
+inconsistent file sizes.
 To use rclone with such affected files on Sharepoint, you may disable
 these checks with the following command line arguments:
 .IP
@@ -26664,12 +23879,25 @@ these checks with the following command line arguments:
 \-\-ignore\-checksum \-\-ignore\-size
 \f[R]
 .fi
-.SS Replacing/deleting existing files on Sharepoint gets \[lq]item not found\[rq]
+.PP
+Alternatively, if you have write access to the OneDrive files, it may be
+possible to fix this problem for certain files, by attempting the steps
+below.
+Open the web interface for OneDrive (https://onedrive.live.com) and find
+the affected files (which will be in the error messages/log for rclone).
+Simply click on each of these files, causing OneDrive to open them on
+the web.
+This will cause each file to be converted in place to a format that is
+functionally equivalent but which will no longer trigger the size
+discrepancy.
+Once all problematic files are converted you will no longer need the
+ignore options above.
+.SS Replacing/deleting existing files on Sharepoint gets \[dq]item not found\[dq]
 .PP
 It is a
 known (https://github.com/OneDrive/onedrive-api-docs/issues/1068) issue
 that Sharepoint (not OneDrive or OneDrive for Business) may return
-\[lq]item not found\[rq] errors when users try to replace or delete
+\[dq]item not found\[dq] errors when users try to replace or delete
 uploaded files; this seems to mainly affect Office files (.docx, .xlsx,
 etc.).
 As a workaround, you may use the \f[C]\-\-backup\-dir <BACKUP_DIR>\f[R]
@@ -26695,9 +23923,9 @@ Description: Using application \[aq]rclone\[aq] is currently not supported for y
 \f[R]
 .fi
 .PP
-This means that rclone can\[cq]t use the OneDrive for Business API with
+This means that rclone can\[aq]t use the OneDrive for Business API with
 your account.
-You can\[cq]t do much about it, maybe write an email to your admins.
+You can\[aq]t do much about it, maybe write an email to your admins.
 .PP
 However, there are other ways to interact with your OneDrive account.
 Have a look at the webdav backend: https://rclone.org/webdav/#sharepoint
@@ -26715,7 +23943,7 @@ If you see the error above after enabling multi\-factor authentication
 for your account, you can fix it by refreshing your OAuth refresh token.
 To do that, run \f[C]rclone config\f[R], and choose to edit your
 OneDrive backend.
-Then, you don\[cq]t need to actually make any changes until you reach
+Then, you don\[aq]t need to actually make any changes until you reach
 this question: \f[C]Already have a token \- refresh?\f[R].
 For this question, answer \f[C]y\f[R] and go through the process to
 refresh your token, just like the first time the backend is configured.
@@ -26940,12 +24168,12 @@ T}
 .TE
 .PP
 Invalid UTF\-8 bytes will also be
-replaced (https://rclone.org/overview/#invalid-utf8), as they can\[cq]t
+replaced (https://rclone.org/overview/#invalid-utf8), as they can\[aq]t
 be used in JSON strings.
 .SS Standard Options
 .PP
 Here are the standard options specific to opendrive (OpenDrive).
-.SS \[en]opendrive\-username
+.SS \-\-opendrive\-username
 .PP
 Username
 .IP \[bu] 2
@@ -26956,9 +24184,12 @@ Env Var: RCLONE_OPENDRIVE_USERNAME
 Type: string
 .IP \[bu] 2
 Default: \[dq]\[dq]
-.SS \[en]opendrive\-password
+.SS \-\-opendrive\-password
 .PP
 Password.
+.PP
+\f[B]NB\f[R] Input to this must be obscured \- see rclone
+obscure (https://rclone.org/commands/rclone_obscure/).
 .IP \[bu] 2
 Config: password
 .IP \[bu] 2
@@ -26970,7 +24201,7 @@ Default: \[dq]\[dq]
 .SS Advanced Options
 .PP
 Here are the advanced options specific to opendrive (OpenDrive).
-.SS \[en]opendrive\-encoding
+.SS \-\-opendrive\-encoding
 .PP
 This sets the encoding for the backend.
 .PP
@@ -26985,7 +24216,7 @@ Type: MultiEncoder
 .IP \[bu] 2
 Default:
 Slash,LtGt,DoubleQuote,Colon,Question,Asterisk,Pipe,BackSlash,LeftSpace,LeftCrLfHtVt,RightSpace,RightCrLfHtVt,InvalidUtf8,Dot
-.SS \[en]opendrive\-chunk\-size
+.SS \-\-opendrive\-chunk\-size
 .PP
 Files will be uploaded in chunks this size.
 .PP
@@ -27001,12 +24232,12 @@ Type: SizeSuffix
 Default: 10M
 .SS Limitations
 .PP
-Note that OpenDrive is case insensitive so you can\[cq]t have a file
-called \[lq]Hello.doc\[rq] and one called \[lq]hello.doc\[rq].
+Note that OpenDrive is case insensitive so you can\[aq]t have a file
+called \[dq]Hello.doc\[dq] and one called \[dq]hello.doc\[dq].
 .PP
-There are quite a few characters that can\[cq]t be in OpenDrive file
+There are quite a few characters that can\[aq]t be in OpenDrive file
 names.
-These can\[cq]t occur on Windows platforms, but on non\-Windows
+These can\[aq]t occur on Windows platforms, but on non\-Windows
 platforms they are common.
 Rclone will map these names to and from an identical looking unicode
 equivalent.
@@ -27120,10 +24351,10 @@ excess files in the bucket.
 .IP
 .nf
 \f[C]
-rclone sync /home/local/directory remote:bucket
+rclone sync \-i /home/local/directory remote:bucket
 \f[R]
 .fi
-.SS \[en]fast\-list
+.SS \-\-fast\-list
 .PP
 This remote supports \f[C]\-\-fast\-list\f[R] which allows you to use
 fewer transactions in exchange for more memory.
@@ -27133,7 +24364,7 @@ details.
 .PP
 rclone supports multipart uploads with QingStor which means that it can
 upload files bigger than 5GB.
-Note that files uploaded with multipart upload don\[cq]t have an MD5SUM.
+Note that files uploaded with multipart upload don\[aq]t have an MD5SUM.
 .PP
 Note that incomplete multipart uploads older than 24 hours can be
 removed with \f[C]rclone cleanup remote:bucket\f[R] just for one bucket
@@ -27184,13 +24415,13 @@ set (https://rclone.org/overview/#restricted-characters).
 Note that 0x7F is not replaced.
 .PP
 Invalid UTF\-8 bytes will also be
-replaced (https://rclone.org/overview/#invalid-utf8), as they can\[cq]t
+replaced (https://rclone.org/overview/#invalid-utf8), as they can\[aq]t
 be used in JSON strings.
 .SS Standard Options
 .PP
 Here are the standard options specific to qingstor (QingCloud Object
 Storage).
-.SS \[en]qingstor\-env\-auth
+.SS \-\-qingstor\-env\-auth
 .PP
 Get QingStor credentials from runtime.
 Only applies if access_key_id and secret_access_key is blank.
@@ -27206,19 +24437,19 @@ Default: false
 Examples:
 .RS 2
 .IP \[bu] 2
-\[lq]false\[rq]
+\[dq]false\[dq]
 .RS 2
 .IP \[bu] 2
 Enter QingStor credentials in the next step
 .RE
 .IP \[bu] 2
-\[lq]true\[rq]
+\[dq]true\[dq]
 .RS 2
 .IP \[bu] 2
 Get QingStor credentials from the environment (env vars or IAM)
 .RE
 .RE
-.SS \[en]qingstor\-access\-key\-id
+.SS \-\-qingstor\-access\-key\-id
 .PP
 QingStor Access Key ID Leave blank for anonymous access or runtime
 credentials.
@@ -27230,7 +24461,7 @@ Env Var: RCLONE_QINGSTOR_ACCESS_KEY_ID
 Type: string
 .IP \[bu] 2
 Default: \[dq]\[dq]
-.SS \[en]qingstor\-secret\-access\-key
+.SS \-\-qingstor\-secret\-access\-key
 .PP
 QingStor Secret Access Key (password) Leave blank for anonymous access
 or runtime credentials.
@@ -27242,11 +24473,11 @@ Env Var: RCLONE_QINGSTOR_SECRET_ACCESS_KEY
 Type: string
 .IP \[bu] 2
 Default: \[dq]\[dq]
-.SS \[en]qingstor\-endpoint
+.SS \-\-qingstor\-endpoint
 .PP
 Enter an endpoint URL to connection QingStor API.
 Leave blank will use the default value
-\[lq]https://qingstor.com:443\[rq]
+\[dq]https://qingstor.com:443\[dq]
 .IP \[bu] 2
 Config: endpoint
 .IP \[bu] 2
@@ -27255,10 +24486,10 @@ Env Var: RCLONE_QINGSTOR_ENDPOINT
 Type: string
 .IP \[bu] 2
 Default: \[dq]\[dq]
-.SS \[en]qingstor\-zone
+.SS \-\-qingstor\-zone
 .PP
 Zone to connect to.
-Default is \[lq]pek3a\[rq].
+Default is \[dq]pek3a\[dq].
 .IP \[bu] 2
 Config: zone
 .IP \[bu] 2
@@ -27271,7 +24502,7 @@ Default: \[dq]\[dq]
 Examples:
 .RS 2
 .IP \[bu] 2
-\[lq]pek3a\[rq]
+\[dq]pek3a\[dq]
 .RS 2
 .IP \[bu] 2
 The Beijing (China) Three Zone
@@ -27279,7 +24510,7 @@ The Beijing (China) Three Zone
 Needs location constraint pek3a.
 .RE
 .IP \[bu] 2
-\[lq]sh1a\[rq]
+\[dq]sh1a\[dq]
 .RS 2
 .IP \[bu] 2
 The Shanghai (China) First Zone
@@ -27287,7 +24518,7 @@ The Shanghai (China) First Zone
 Needs location constraint sh1a.
 .RE
 .IP \[bu] 2
-\[lq]gd2a\[rq]
+\[dq]gd2a\[dq]
 .RS 2
 .IP \[bu] 2
 The Guangdong (China) Second Zone
@@ -27299,7 +24530,7 @@ Needs location constraint gd2a.
 .PP
 Here are the advanced options specific to qingstor (QingCloud Object
 Storage).
-.SS \[en]qingstor\-connection\-retries
+.SS \-\-qingstor\-connection\-retries
 .PP
 Number of connection retries.
 .IP \[bu] 2
@@ -27310,7 +24541,7 @@ Env Var: RCLONE_QINGSTOR_CONNECTION_RETRIES
 Type: int
 .IP \[bu] 2
 Default: 3
-.SS \[en]qingstor\-upload\-cutoff
+.SS \-\-qingstor\-upload\-cutoff
 .PP
 Cutoff for switching to chunked upload
 .PP
@@ -27324,14 +24555,14 @@ Env Var: RCLONE_QINGSTOR_UPLOAD_CUTOFF
 Type: SizeSuffix
 .IP \[bu] 2
 Default: 200M
-.SS \[en]qingstor\-chunk\-size
+.SS \-\-qingstor\-chunk\-size
 .PP
 Chunk size to use for uploading.
 .PP
 When uploading files larger than upload_cutoff they will be uploaded as
 multipart uploads using this chunk size.
 .PP
-Note that \[lq]\[en]qingstor\-upload\-concurrency\[rq] chunks of this
+Note that \[dq]\-\-qingstor\-upload\-concurrency\[dq] chunks of this
 size are buffered in memory per transfer.
 .PP
 If you are transferring large files over high speed links and you have
@@ -27344,7 +24575,7 @@ Env Var: RCLONE_QINGSTOR_CHUNK_SIZE
 Type: SizeSuffix
 .IP \[bu] 2
 Default: 4M
-.SS \[en]qingstor\-upload\-concurrency
+.SS \-\-qingstor\-upload\-concurrency
 .PP
 Concurrency for multipart uploads.
 .PP
@@ -27365,7 +24596,7 @@ Env Var: RCLONE_QINGSTOR_UPLOAD_CONCURRENCY
 Type: int
 .IP \[bu] 2
 Default: 1
-.SS \[en]qingstor\-encoding
+.SS \-\-qingstor\-encoding
 .PP
 This sets the encoding for the backend.
 .PP
@@ -27536,7 +24767,7 @@ any excess files in the container.
 .IP
 .nf
 \f[C]
-rclone sync /home/local/directory remote:container
+rclone sync \-i /home/local/directory remote:container
 \f[R]
 .fi
 .SS Configuration from an OpenStack credentials file
@@ -27592,8 +24823,8 @@ in the docs for the swift library.
 .PP
 If your OpenStack installation uses a non\-standard authentication
 method that might not be yet supported by rclone or the underlying swift
-library, you can authenticate externally (e.g.\ calling manually the
-\f[C]openstack\f[R] commands to get a token).
+library, you can authenticate externally (e.g.
+calling manually the \f[C]openstack\f[R] commands to get a token).
 Then, you just need to pass the two configuration variables
 \f[C]auth_token\f[R] and \f[C]storage_url\f[R].
 If they are both provided, the other variables are ignored.
@@ -27613,13 +24844,13 @@ export RCLONE_CONFIG_MYREMOTE_ENV_AUTH=true
 rclone lsd myremote:
 \f[R]
 .fi
-.SS \[en]fast\-list
+.SS \-\-fast\-list
 .PP
 This remote supports \f[C]\-\-fast\-list\f[R] which allows you to use
 fewer transactions in exchange for more memory.
 See the rclone docs (https://rclone.org/docs/#fast-list) for more
 details.
-.SS \[en]update and \[en]use\-server\-modtime
+.SS \-\-update and \-\-use\-server\-modtime
 .PP
 As noted below, the modified time is stored on metadata on the object.
 It is used by default for all operations that require checking the time
@@ -27629,7 +24860,7 @@ is inefficient because it requires an extra API call to retrieve the
 metadata.
 .PP
 For many operations, the time the object was last uploaded to the remote
-is sufficient to determine if it is \[lq]dirty\[rq].
+is sufficient to determine if it is \[dq]dirty\[dq].
 By using \f[C]\-\-update\f[R] along with
 \f[C]\-\-use\-server\-modtime\f[R], you can avoid the extra API call and
 simply upload files whose local modtime is newer than the time it was
@@ -27638,7 +24869,7 @@ last uploaded.
 .PP
 Here are the standard options specific to swift (OpenStack Swift
 (Rackspace Cloud Files, Memset Memstore, OVH)).
-.SS \[en]swift\-env\-auth
+.SS \-\-swift\-env\-auth
 .PP
 Get swift credentials from environment variables in standard OpenStack
 form.
@@ -27654,20 +24885,20 @@ Default: false
 Examples:
 .RS 2
 .IP \[bu] 2
-\[lq]false\[rq]
+\[dq]false\[dq]
 .RS 2
 .IP \[bu] 2
 Enter swift credentials in the next step
 .RE
 .IP \[bu] 2
-\[lq]true\[rq]
+\[dq]true\[dq]
 .RS 2
 .IP \[bu] 2
 Get swift credentials from environment vars.
 Leave other fields blank if using this.
 .RE
 .RE
-.SS \[en]swift\-user
+.SS \-\-swift\-user
 .PP
 User name to log in (OS_USERNAME).
 .IP \[bu] 2
@@ -27678,7 +24909,7 @@ Env Var: RCLONE_SWIFT_USER
 Type: string
 .IP \[bu] 2
 Default: \[dq]\[dq]
-.SS \[en]swift\-key
+.SS \-\-swift\-key
 .PP
 API key or password (OS_PASSWORD).
 .IP \[bu] 2
@@ -27689,7 +24920,7 @@ Env Var: RCLONE_SWIFT_KEY
 Type: string
 .IP \[bu] 2
 Default: \[dq]\[dq]
-.SS \[en]swift\-auth
+.SS \-\-swift\-auth
 .PP
 Authentication URL for server (OS_AUTH_URL).
 .IP \[bu] 2
@@ -27704,43 +24935,43 @@ Default: \[dq]\[dq]
 Examples:
 .RS 2
 .IP \[bu] 2
-\[lq]https://auth.api.rackspacecloud.com/v1.0\[rq]
+\[dq]https://auth.api.rackspacecloud.com/v1.0\[dq]
 .RS 2
 .IP \[bu] 2
 Rackspace US
 .RE
 .IP \[bu] 2
-\[lq]https://lon.auth.api.rackspacecloud.com/v1.0\[rq]
+\[dq]https://lon.auth.api.rackspacecloud.com/v1.0\[dq]
 .RS 2
 .IP \[bu] 2
 Rackspace UK
 .RE
 .IP \[bu] 2
-\[lq]https://identity.api.rackspacecloud.com/v2.0\[rq]
+\[dq]https://identity.api.rackspacecloud.com/v2.0\[dq]
 .RS 2
 .IP \[bu] 2
 Rackspace v2
 .RE
 .IP \[bu] 2
-\[lq]https://auth.storage.memset.com/v1.0\[rq]
+\[dq]https://auth.storage.memset.com/v1.0\[dq]
 .RS 2
 .IP \[bu] 2
 Memset Memstore UK
 .RE
 .IP \[bu] 2
-\[lq]https://auth.storage.memset.com/v2.0\[rq]
+\[dq]https://auth.storage.memset.com/v2.0\[dq]
 .RS 2
 .IP \[bu] 2
 Memset Memstore UK v2
 .RE
 .IP \[bu] 2
-\[lq]https://auth.cloud.ovh.net/v3\[rq]
+\[dq]https://auth.cloud.ovh.net/v3\[dq]
 .RS 2
 .IP \[bu] 2
 OVH
 .RE
 .RE
-.SS \[en]swift\-user\-id
+.SS \-\-swift\-user\-id
 .PP
 User ID to log in \- optional \- most swift systems use user and leave
 this blank (v3 auth) (OS_USER_ID).
@@ -27752,7 +24983,7 @@ Env Var: RCLONE_SWIFT_USER_ID
 Type: string
 .IP \[bu] 2
 Default: \[dq]\[dq]
-.SS \[en]swift\-domain
+.SS \-\-swift\-domain
 .PP
 User domain \- optional (v3 auth) (OS_USER_DOMAIN_NAME)
 .IP \[bu] 2
@@ -27763,7 +24994,7 @@ Env Var: RCLONE_SWIFT_DOMAIN
 Type: string
 .IP \[bu] 2
 Default: \[dq]\[dq]
-.SS \[en]swift\-tenant
+.SS \-\-swift\-tenant
 .PP
 Tenant name \- optional for v1 auth, this or tenant_id required
 otherwise (OS_TENANT_NAME or OS_PROJECT_NAME)
@@ -27775,7 +25006,7 @@ Env Var: RCLONE_SWIFT_TENANT
 Type: string
 .IP \[bu] 2
 Default: \[dq]\[dq]
-.SS \[en]swift\-tenant\-id
+.SS \-\-swift\-tenant\-id
 .PP
 Tenant ID \- optional for v1 auth, this or tenant required otherwise
 (OS_TENANT_ID)
@@ -27787,7 +25018,7 @@ Env Var: RCLONE_SWIFT_TENANT_ID
 Type: string
 .IP \[bu] 2
 Default: \[dq]\[dq]
-.SS \[en]swift\-tenant\-domain
+.SS \-\-swift\-tenant\-domain
 .PP
 Tenant domain \- optional (v3 auth) (OS_PROJECT_DOMAIN_NAME)
 .IP \[bu] 2
@@ -27798,7 +25029,7 @@ Env Var: RCLONE_SWIFT_TENANT_DOMAIN
 Type: string
 .IP \[bu] 2
 Default: \[dq]\[dq]
-.SS \[en]swift\-region
+.SS \-\-swift\-region
 .PP
 Region name \- optional (OS_REGION_NAME)
 .IP \[bu] 2
@@ -27809,7 +25040,7 @@ Env Var: RCLONE_SWIFT_REGION
 Type: string
 .IP \[bu] 2
 Default: \[dq]\[dq]
-.SS \[en]swift\-storage\-url
+.SS \-\-swift\-storage\-url
 .PP
 Storage URL \- optional (OS_STORAGE_URL)
 .IP \[bu] 2
@@ -27820,7 +25051,7 @@ Env Var: RCLONE_SWIFT_STORAGE_URL
 Type: string
 .IP \[bu] 2
 Default: \[dq]\[dq]
-.SS \[en]swift\-auth\-token
+.SS \-\-swift\-auth\-token
 .PP
 Auth Token from alternate authentication \- optional (OS_AUTH_TOKEN)
 .IP \[bu] 2
@@ -27831,7 +25062,7 @@ Env Var: RCLONE_SWIFT_AUTH_TOKEN
 Type: string
 .IP \[bu] 2
 Default: \[dq]\[dq]
-.SS \[en]swift\-application\-credential\-id
+.SS \-\-swift\-application\-credential\-id
 .PP
 Application Credential ID (OS_APPLICATION_CREDENTIAL_ID)
 .IP \[bu] 2
@@ -27842,7 +25073,7 @@ Env Var: RCLONE_SWIFT_APPLICATION_CREDENTIAL_ID
 Type: string
 .IP \[bu] 2
 Default: \[dq]\[dq]
-.SS \[en]swift\-application\-credential\-name
+.SS \-\-swift\-application\-credential\-name
 .PP
 Application Credential Name (OS_APPLICATION_CREDENTIAL_NAME)
 .IP \[bu] 2
@@ -27853,7 +25084,7 @@ Env Var: RCLONE_SWIFT_APPLICATION_CREDENTIAL_NAME
 Type: string
 .IP \[bu] 2
 Default: \[dq]\[dq]
-.SS \[en]swift\-application\-credential\-secret
+.SS \-\-swift\-application\-credential\-secret
 .PP
 Application Credential Secret (OS_APPLICATION_CREDENTIAL_SECRET)
 .IP \[bu] 2
@@ -27864,7 +25095,7 @@ Env Var: RCLONE_SWIFT_APPLICATION_CREDENTIAL_SECRET
 Type: string
 .IP \[bu] 2
 Default: \[dq]\[dq]
-.SS \[en]swift\-auth\-version
+.SS \-\-swift\-auth\-version
 .PP
 AuthVersion \- optional \- set to (1,2,3) if your auth URL has no
 version (ST_AUTH_VERSION)
@@ -27876,7 +25107,7 @@ Env Var: RCLONE_SWIFT_AUTH_VERSION
 Type: int
 .IP \[bu] 2
 Default: 0
-.SS \[en]swift\-endpoint\-type
+.SS \-\-swift\-endpoint\-type
 .PP
 Endpoint type to choose from the service catalogue (OS_ENDPOINT_TYPE)
 .IP \[bu] 2
@@ -27886,30 +25117,30 @@ Env Var: RCLONE_SWIFT_ENDPOINT_TYPE
 .IP \[bu] 2
 Type: string
 .IP \[bu] 2
-Default: \[lq]public\[rq]
+Default: \[dq]public\[dq]
 .IP \[bu] 2
 Examples:
 .RS 2
 .IP \[bu] 2
-\[lq]public\[rq]
+\[dq]public\[dq]
 .RS 2
 .IP \[bu] 2
 Public (default, choose this if not sure)
 .RE
 .IP \[bu] 2
-\[lq]internal\[rq]
+\[dq]internal\[dq]
 .RS 2
 .IP \[bu] 2
 Internal (use internal service net)
 .RE
 .IP \[bu] 2
-\[lq]admin\[rq]
+\[dq]admin\[dq]
 .RS 2
 .IP \[bu] 2
 Admin
 .RE
 .RE
-.SS \[en]swift\-storage\-policy
+.SS \-\-swift\-storage\-policy
 .PP
 The storage policy to use when creating a new container
 .PP
@@ -27935,13 +25166,13 @@ Examples:
 Default
 .RE
 .IP \[bu] 2
-\[lq]pcs\[rq]
+\[dq]pcs\[dq]
 .RS 2
 .IP \[bu] 2
 OVH Public Cloud Storage
 .RE
 .IP \[bu] 2
-\[lq]pca\[rq]
+\[dq]pca\[dq]
 .RS 2
 .IP \[bu] 2
 OVH Public Cloud Archive
@@ -27951,7 +25182,7 @@ OVH Public Cloud Archive
 .PP
 Here are the advanced options specific to swift (OpenStack Swift
 (Rackspace Cloud Files, Memset Memstore, OVH)).
-.SS \[en]swift\-chunk\-size
+.SS \-\-swift\-chunk\-size
 .PP
 Above this size files will be chunked into a _segments container.
 .PP
@@ -27965,9 +25196,9 @@ Env Var: RCLONE_SWIFT_CHUNK_SIZE
 Type: SizeSuffix
 .IP \[bu] 2
 Default: 5G
-.SS \[en]swift\-no\-chunk
+.SS \-\-swift\-no\-chunk
 .PP
-Don\[cq]t chunk files during streaming upload.
+Don\[aq]t chunk files during streaming upload.
 .PP
 When doing streaming uploads (eg using rcat or mount) setting this flag
 will cause the swift backend to not upload chunked files.
@@ -27985,7 +25216,7 @@ Env Var: RCLONE_SWIFT_NO_CHUNK
 Type: bool
 .IP \[bu] 2
 Default: false
-.SS \[en]swift\-encoding
+.SS \-\-swift\-encoding
 .PP
 This sets the encoding for the backend.
 .PP
@@ -28037,26 +25268,26 @@ T}
 .TE
 .PP
 Invalid UTF\-8 bytes will also be
-replaced (https://rclone.org/overview/#invalid-utf8), as they can\[cq]t
+replaced (https://rclone.org/overview/#invalid-utf8), as they can\[aq]t
 be used in JSON strings.
 .SS Limitations
 .PP
-The Swift API doesn\[cq]t return a correct MD5SUM for segmented files
-(Dynamic or Static Large Objects) so rclone won\[cq]t check or use the
+The Swift API doesn\[aq]t return a correct MD5SUM for segmented files
+(Dynamic or Static Large Objects) so rclone won\[aq]t check or use the
 MD5SUM for these.
 .SS Troubleshooting
-.SS Rclone gives Failed to create file system for \[lq]remote:\[rq]: Bad Request
+.SS Rclone gives Failed to create file system for \[dq]remote:\[dq]: Bad Request
 .PP
-Due to an oddity of the underlying swift library, it gives a \[lq]Bad
-Request\[rq] error rather than a more sensible error when the
+Due to an oddity of the underlying swift library, it gives a \[dq]Bad
+Request\[dq] error rather than a more sensible error when the
 authentication fails for Swift.
 .PP
 So this most likely means your username / password is wrong.
 You can investigate further with the \f[C]\-\-dump\-bodies\f[R] flag.
 .PP
-This may also be caused by specifying the region when you shouldn\[cq]t
+This may also be caused by specifying the region when you shouldn\[aq]t
 have (eg OVH).
-.SS Rclone gives Failed to create file system: Response didn\[cq]t have storage url and auth token
+.SS Rclone gives Failed to create file system: Response didn\[aq]t have storage url and auth token
 .PP
 This is most likely caused by forgetting to specify your tenant when
 setting up a swift remote.
@@ -28197,7 +25428,7 @@ T}
 .TE
 .PP
 Invalid UTF\-8 bytes will also be
-replaced (https://rclone.org/overview/#invalid-utf8), as they can\[cq]t
+replaced (https://rclone.org/overview/#invalid-utf8), as they can\[aq]t
 be used in JSON strings.
 .SS Deleting files
 .PP
@@ -28228,9 +25459,9 @@ in the browser, then you use \f[C]5xxxxxxxx8\f[R] as the
 .SS Standard Options
 .PP
 Here are the standard options specific to pcloud (Pcloud).
-.SS \[en]pcloud\-client\-id
+.SS \-\-pcloud\-client\-id
 .PP
-Pcloud App Client Id Leave blank normally.
+OAuth Client Id Leave blank normally.
 .IP \[bu] 2
 Config: client_id
 .IP \[bu] 2
@@ -28239,9 +25470,9 @@ Env Var: RCLONE_PCLOUD_CLIENT_ID
 Type: string
 .IP \[bu] 2
 Default: \[dq]\[dq]
-.SS \[en]pcloud\-client\-secret
+.SS \-\-pcloud\-client\-secret
 .PP
-Pcloud App Client Secret Leave blank normally.
+OAuth Client Secret Leave blank normally.
 .IP \[bu] 2
 Config: client_secret
 .IP \[bu] 2
@@ -28253,7 +25484,42 @@ Default: \[dq]\[dq]
 .SS Advanced Options
 .PP
 Here are the advanced options specific to pcloud (Pcloud).
-.SS \[en]pcloud\-encoding
+.SS \-\-pcloud\-token
+.PP
+OAuth Access Token as a JSON blob.
+.IP \[bu] 2
+Config: token
+.IP \[bu] 2
+Env Var: RCLONE_PCLOUD_TOKEN
+.IP \[bu] 2
+Type: string
+.IP \[bu] 2
+Default: \[dq]\[dq]
+.SS \-\-pcloud\-auth\-url
+.PP
+Auth server URL.
+Leave blank to use the provider defaults.
+.IP \[bu] 2
+Config: auth_url
+.IP \[bu] 2
+Env Var: RCLONE_PCLOUD_AUTH_URL
+.IP \[bu] 2
+Type: string
+.IP \[bu] 2
+Default: \[dq]\[dq]
+.SS \-\-pcloud\-token\-url
+.PP
+Token server url.
+Leave blank to use the provider defaults.
+.IP \[bu] 2
+Config: token_url
+.IP \[bu] 2
+Env Var: RCLONE_PCLOUD_TOKEN_URL
+.IP \[bu] 2
+Type: string
+.IP \[bu] 2
+Default: \[dq]\[dq]
+.SS \-\-pcloud\-encoding
 .PP
 This sets the encoding for the backend.
 .PP
@@ -28267,7 +25533,7 @@ Env Var: RCLONE_PCLOUD_ENCODING
 Type: MultiEncoder
 .IP \[bu] 2
 Default: Slash,BackSlash,Del,Ctl,InvalidUtf8,Dot
-.SS \[en]pcloud\-root\-folder\-id
+.SS \-\-pcloud\-root\-folder\-id
 .PP
 Fill in for rclone to use a non root folder as its starting point.
 .IP \[bu] 2
@@ -28277,7 +25543,38 @@ Env Var: RCLONE_PCLOUD_ROOT_FOLDER_ID
 .IP \[bu] 2
 Type: string
 .IP \[bu] 2
-Default: \[lq]d0\[rq]
+Default: \[dq]d0\[dq]
+.SS \-\-pcloud\-hostname
+.PP
+Hostname to connect to.
+.PP
+This is normally set when rclone initially does the oauth connection,
+however you will need to set it by hand if you are using remote config
+with rclone authorize.
+.IP \[bu] 2
+Config: hostname
+.IP \[bu] 2
+Env Var: RCLONE_PCLOUD_HOSTNAME
+.IP \[bu] 2
+Type: string
+.IP \[bu] 2
+Default: \[dq]api.pcloud.com\[dq]
+.IP \[bu] 2
+Examples:
+.RS 2
+.IP \[bu] 2
+\[dq]api.pcloud.com\[dq]
+.RS 2
+.IP \[bu] 2
+Original/US region
+.RE
+.IP \[bu] 2
+\[dq]eapi.pcloud.com\[dq]
+.RS 2
+.IP \[bu] 2
+EU region
+.RE
+.RE
 .SS premiumize.me
 .PP
 Paths are specified as \f[C]remote:path\f[R]
@@ -28415,12 +25712,12 @@ T}
 .TE
 .PP
 Invalid UTF\-8 bytes will also be
-replaced (https://rclone.org/overview/#invalid-utf8), as they can\[cq]t
+replaced (https://rclone.org/overview/#invalid-utf8), as they can\[aq]t
 be used in JSON strings.
 .SS Standard Options
 .PP
 Here are the standard options specific to premiumizeme (premiumize.me).
-.SS \[en]premiumizeme\-api\-key
+.SS \-\-premiumizeme\-api\-key
 .PP
 API Key.
 .PP
@@ -28436,7 +25733,7 @@ Default: \[dq]\[dq]
 .SS Advanced Options
 .PP
 Here are the advanced options specific to premiumizeme (premiumize.me).
-.SS \[en]premiumizeme\-encoding
+.SS \-\-premiumizeme\-encoding
 .PP
 This sets the encoding for the backend.
 .PP
@@ -28452,10 +25749,10 @@ Type: MultiEncoder
 Default: Slash,DoubleQuote,BackSlash,Del,Ctl,InvalidUtf8,Dot
 .SS Limitations
 .PP
-Note that premiumize.me is case insensitive so you can\[cq]t have a file
-called \[lq]Hello.doc\[rq] and one called \[lq]hello.doc\[rq].
+Note that premiumize.me is case insensitive so you can\[aq]t have a file
+called \[dq]Hello.doc\[dq] and one called \[dq]hello.doc\[dq].
 .PP
-premiumize.me file names can\[cq]t have the \f[C]\[rs]\f[R] or
+premiumize.me file names can\[aq]t have the \f[C]\[rs]\f[R] or
 \f[C]\[dq]\f[R] characters in.
 rclone maps these to and from an identical looking unicode equivalents
 \f[C]\[uFF3C]\f[R] and \f[C]\[uFF02]\f[R]
@@ -28598,12 +25895,12 @@ T}
 .TE
 .PP
 Invalid UTF\-8 bytes will also be
-replaced (https://rclone.org/overview/#invalid-utf8), as they can\[cq]t
+replaced (https://rclone.org/overview/#invalid-utf8), as they can\[aq]t
 be used in JSON strings.
 .SS Advanced Options
 .PP
 Here are the advanced options specific to putio (Put.io).
-.SS \[en]putio\-encoding
+.SS \-\-putio\-encoding
 .PP
 This sets the encoding for the backend.
 .PP
@@ -28628,7 +25925,7 @@ professional edition.
 .SS Root mode vs Library mode
 .PP
 There are two distinct modes you can setup your remote: \- you point
-your remote to the \f[B]root of the server\f[R], meaning you don\[cq]t
+your remote to the \f[B]root of the server\f[R], meaning you don\[aq]t
 specify a library during the configuration: Paths are specified as
 \f[C]remote:library\f[R].
 You may put subdirectories in too, eg
@@ -28722,7 +26019,7 @@ y/e/d> y
 .fi
 .PP
 This remote is called \f[C]seafile\f[R].
-It\[cq]s pointing to the root of your seafile server and can now be used
+It\[aq]s pointing to the root of your seafile server and can now be used
 like this:
 .PP
 See all libraries
@@ -28754,12 +26051,12 @@ excess files in the library.
 .IP
 .nf
 \f[C]
-rclone sync /home/local/directory seafile:library
+rclone sync \-i /home/local/directory seafile:library
 \f[R]
 .fi
 .SS Configuration in library mode
 .PP
-Here\[cq]s an example of a configuration in library mode with a user
+Here\[aq]s an example of a configuration in library mode with a user
 that has the two\-factor authentication enabled.
 Your 2FA code will be asked at the end of the configuration, and will
 attempt to authenticate you:
@@ -28836,8 +26133,8 @@ y/e/d> y
 \f[R]
 .fi
 .PP
-You\[cq]ll notice your password is blank in the configuration.
-It\[cq]s because we only need the password to authenticate you once.
+You\[aq]ll notice your password is blank in the configuration.
+It\[aq]s because we only need the password to authenticate you once.
 .PP
 You specified \f[C]My Library\f[R] during the configuration.
 The root of the remote is pointing at the root of the library
@@ -28872,10 +26169,10 @@ excess files in the library.
 .IP
 .nf
 \f[C]
-rclone sync /home/local/directory seafile:
+rclone sync \-i /home/local/directory seafile:
 \f[R]
 .fi
-.SS \[en]fast\-list
+.SS \-\-fast\-list
 .PP
 Seafile version 7+ supports \f[C]\-\-fast\-list\f[R] which allows you to
 use fewer transactions in exchange for more memory.
@@ -28923,7 +26220,7 @@ T}
 .TE
 .PP
 Invalid UTF\-8 bytes will also be
-replaced (https://rclone.org/overview/#invalid-utf8), as they can\[cq]t
+replaced (https://rclone.org/overview/#invalid-utf8), as they can\[aq]t
 be used in JSON strings.
 .SS Seafile and rclone link
 .PP
@@ -28958,12 +26255,12 @@ image (https://github.com/haiwen/seafile-docker) of these versions: \-
 edition
 .PP
 Versions below 6.0 are not supported.
-Versions between 6.0 and 6.3 haven\[cq]t been tested and might not work
+Versions between 6.0 and 6.3 haven\[aq]t been tested and might not work
 properly.
 .SS Standard Options
 .PP
 Here are the standard options specific to seafile (seafile).
-.SS \[en]seafile\-url
+.SS \-\-seafile\-url
 .PP
 URL of seafile host to connect to
 .IP \[bu] 2
@@ -28978,13 +26275,13 @@ Default: \[dq]\[dq]
 Examples:
 .RS 2
 .IP \[bu] 2
-\[lq]https://cloud.seafile.com/\[rq]
+\[dq]https://cloud.seafile.com/\[dq]
 .RS 2
 .IP \[bu] 2
 Connect to cloud.seafile.com
 .RE
 .RE
-.SS \[en]seafile\-user
+.SS \-\-seafile\-user
 .PP
 User name (usually email address)
 .IP \[bu] 2
@@ -28995,9 +26292,12 @@ Env Var: RCLONE_SEAFILE_USER
 Type: string
 .IP \[bu] 2
 Default: \[dq]\[dq]
-.SS \[en]seafile\-pass
+.SS \-\-seafile\-pass
 .PP
 Password
+.PP
+\f[B]NB\f[R] Input to this must be obscured \- see rclone
+obscure (https://rclone.org/commands/rclone_obscure/).
 .IP \[bu] 2
 Config: pass
 .IP \[bu] 2
@@ -29006,9 +26306,10 @@ Env Var: RCLONE_SEAFILE_PASS
 Type: string
 .IP \[bu] 2
 Default: \[dq]\[dq]
-.SS \[en]seafile\-2fa
+.SS \-\-seafile\-2fa
 .PP
-Two\-factor authentication (`true' if the account has 2FA enabled)
+Two\-factor authentication (\[aq]true\[aq] if the account has 2FA
+enabled)
 .IP \[bu] 2
 Config: 2fa
 .IP \[bu] 2
@@ -29017,7 +26318,7 @@ Env Var: RCLONE_SEAFILE_2FA
 Type: bool
 .IP \[bu] 2
 Default: false
-.SS \[en]seafile\-library
+.SS \-\-seafile\-library
 .PP
 Name of the library.
 Leave blank to access all non\-encrypted libraries.
@@ -29029,10 +26330,13 @@ Env Var: RCLONE_SEAFILE_LIBRARY
 Type: string
 .IP \[bu] 2
 Default: \[dq]\[dq]
-.SS \[en]seafile\-library\-key
+.SS \-\-seafile\-library\-key
 .PP
 Library password (for encrypted libraries only).
 Leave blank if you pass it through the command line.
+.PP
+\f[B]NB\f[R] Input to this must be obscured \- see rclone
+obscure (https://rclone.org/commands/rclone_obscure/).
 .IP \[bu] 2
 Config: library_key
 .IP \[bu] 2
@@ -29041,7 +26345,7 @@ Env Var: RCLONE_SEAFILE_LIBRARY_KEY
 Type: string
 .IP \[bu] 2
 Default: \[dq]\[dq]
-.SS \[en]seafile\-auth\-token
+.SS \-\-seafile\-auth\-token
 .PP
 Authentication token
 .IP \[bu] 2
@@ -29055,9 +26359,9 @@ Default: \[dq]\[dq]
 .SS Advanced Options
 .PP
 Here are the advanced options specific to seafile (seafile).
-.SS \[en]seafile\-create\-library
+.SS \-\-seafile\-create\-library
 .PP
-Should rclone create a library if it doesn\[cq]t exist
+Should rclone create a library if it doesn\[aq]t exist
 .IP \[bu] 2
 Config: create_library
 .IP \[bu] 2
@@ -29066,7 +26370,7 @@ Env Var: RCLONE_SEAFILE_CREATE_LIBRARY
 Type: bool
 .IP \[bu] 2
 Default: false
-.SS \[en]seafile\-encoding
+.SS \-\-seafile\-encoding
 .PP
 This sets the encoding for the backend.
 .PP
@@ -29097,7 +26401,7 @@ installations.
 Paths are specified as \f[C]remote:path\f[R].
 If the path does not begin with a \f[C]/\f[R] it is relative to the home
 directory of the user.
-An empty path \f[C]remote:\f[R] refers to the user\[cq]s home directory.
+An empty path \f[C]remote:\f[R] refers to the user\[aq]s home directory.
 .PP
 \[dq]Note that some SFTP servers will need the leading / \- Synology is
 a good example of this.
@@ -29192,7 +26496,7 @@ any excess files in the directory.
 .IP
 .nf
 \f[C]
-rclone sync /home/local/directory remote:directory
+rclone sync \-i /home/local/directory remote:directory
 \f[R]
 .fi
 .SS SSH Authentication
@@ -29212,11 +26516,11 @@ Only unencrypted OpenSSH or PEM encrypted files are supported.
 The key file can be specified in either an external file (key_file) or
 contained within the rclone config file (key_pem).
 If using key_pem in the config file, the entry should be on a single
-line with new line (`' or `') separating lines.
-i.e.\ 
+line with new line (\[aq]\[aq] or \[aq]\[aq]) separating lines.
+i.e.
 .PP
-key_pem = \[em]\[en]BEGIN RSA PRIVATE
-KEY\[em]\[en]0gAMbMbaSsd\[em]\[en]END RSA PRIVATE KEY\[em]\[en]
+key_pem = \-\-\-\-\-BEGIN RSA PRIVATE
+KEY\-\-\-\-\-0gAMbMbaSsd\-\-\-\-\-END RSA PRIVATE KEY\-\-\-\-\-
 .PP
 This will generate it correctly for key_pem for use in the config:
 .IP
@@ -29226,7 +26530,7 @@ awk \[aq]{printf \[dq]%s\[rs]\[rs]n\[dq], $0}\[aq] < \[ti]/.ssh/id_rsa
 \f[R]
 .fi
 .PP
-If you don\[cq]t specify \f[C]pass\f[R], \f[C]key_file\f[R], or
+If you don\[aq]t specify \f[C]pass\f[R], \f[C]key_file\f[R], or
 \f[C]key_pem\f[R] then rclone will attempt to contact an ssh\-agent.
 .PP
 You can also specify \f[C]key_use_agent\f[R] to force the usage of an
@@ -29276,7 +26580,7 @@ disable this behaviour.
 .SS Standard Options
 .PP
 Here are the standard options specific to sftp (SSH/SFTP Connection).
-.SS \[en]sftp\-host
+.SS \-\-sftp\-host
 .PP
 SSH host to connect to
 .IP \[bu] 2
@@ -29291,13 +26595,13 @@ Default: \[dq]\[dq]
 Examples:
 .RS 2
 .IP \[bu] 2
-\[lq]example.com\[rq]
+\[dq]example.com\[dq]
 .RS 2
 .IP \[bu] 2
 Connect to example.com
 .RE
 .RE
-.SS \[en]sftp\-user
+.SS \-\-sftp\-user
 .PP
 SSH username, leave blank for current username, ncw
 .IP \[bu] 2
@@ -29308,7 +26612,7 @@ Env Var: RCLONE_SFTP_USER
 Type: string
 .IP \[bu] 2
 Default: \[dq]\[dq]
-.SS \[en]sftp\-port
+.SS \-\-sftp\-port
 .PP
 SSH port, leave blank to use default (22)
 .IP \[bu] 2
@@ -29319,9 +26623,12 @@ Env Var: RCLONE_SFTP_PORT
 Type: string
 .IP \[bu] 2
 Default: \[dq]\[dq]
-.SS \[en]sftp\-pass
+.SS \-\-sftp\-pass
 .PP
 SSH password, leave blank to use ssh\-agent.
+.PP
+\f[B]NB\f[R] Input to this must be obscured \- see rclone
+obscure (https://rclone.org/commands/rclone_obscure/).
 .IP \[bu] 2
 Config: pass
 .IP \[bu] 2
@@ -29330,7 +26637,7 @@ Env Var: RCLONE_SFTP_PASS
 Type: string
 .IP \[bu] 2
 Default: \[dq]\[dq]
-.SS \[en]sftp\-key\-pem
+.SS \-\-sftp\-key\-pem
 .PP
 Raw PEM\-encoded private key, If specified, will override key_file
 parameter.
@@ -29342,10 +26649,13 @@ Env Var: RCLONE_SFTP_KEY_PEM
 Type: string
 .IP \[bu] 2
 Default: \[dq]\[dq]
-.SS \[en]sftp\-key\-file
+.SS \-\-sftp\-key\-file
 .PP
 Path to PEM\-encoded private key file, leave blank or set
 key\-use\-agent to use ssh\-agent.
+.PP
+Leading \f[C]\[ti]\f[R] will be expanded in the file name as will
+environment variables such as \f[C]${RCLONE_CONFIG_DIR}\f[R].
 .IP \[bu] 2
 Config: key_file
 .IP \[bu] 2
@@ -29354,12 +26664,15 @@ Env Var: RCLONE_SFTP_KEY_FILE
 Type: string
 .IP \[bu] 2
 Default: \[dq]\[dq]
-.SS \[en]sftp\-key\-file\-pass
+.SS \-\-sftp\-key\-file\-pass
 .PP
 The passphrase to decrypt the PEM\-encoded private key file.
 .PP
 Only PEM encrypted key files (old OpenSSH format) are supported.
-Encrypted keys in the new OpenSSH format can\[cq]t be used.
+Encrypted keys in the new OpenSSH format can\[aq]t be used.
+.PP
+\f[B]NB\f[R] Input to this must be obscured \- see rclone
+obscure (https://rclone.org/commands/rclone_obscure/).
 .IP \[bu] 2
 Config: key_file_pass
 .IP \[bu] 2
@@ -29368,11 +26681,11 @@ Env Var: RCLONE_SFTP_KEY_FILE_PASS
 Type: string
 .IP \[bu] 2
 Default: \[dq]\[dq]
-.SS \[en]sftp\-key\-use\-agent
+.SS \-\-sftp\-key\-use\-agent
 .PP
 When set forces the usage of the ssh\-agent.
 .PP
-When key\-file is also set, the \[lq].pub\[rq] file of the specified
+When key\-file is also set, the \[dq].pub\[dq] file of the specified
 key\-file is read and only the associated key is requested from the
 ssh\-agent.
 This allows to avoid
@@ -29386,7 +26699,7 @@ Env Var: RCLONE_SFTP_KEY_USE_AGENT
 Type: bool
 .IP \[bu] 2
 Default: false
-.SS \[en]sftp\-use\-insecure\-cipher
+.SS \-\-sftp\-use\-insecure\-cipher
 .PP
 Enable the use of insecure ciphers and key exchange methods.
 .PP
@@ -29419,13 +26732,13 @@ Default: false
 Examples:
 .RS 2
 .IP \[bu] 2
-\[lq]false\[rq]
+\[dq]false\[dq]
 .RS 2
 .IP \[bu] 2
 Use default Cipher list.
 .RE
 .IP \[bu] 2
-\[lq]true\[rq]
+\[dq]true\[dq]
 .RS 2
 .IP \[bu] 2
 Enables the use of the aes128\-cbc cipher and
@@ -29433,7 +26746,7 @@ diffie\-hellman\-group\-exchange\-sha256,
 diffie\-hellman\-group\-exchange\-sha1 key exchange.
 .RE
 .RE
-.SS \[en]sftp\-disable\-hashcheck
+.SS \-\-sftp\-disable\-hashcheck
 .PP
 Disable the execution of SSH commands to determine if remote file
 hashing is available.
@@ -29450,7 +26763,7 @@ Default: false
 .SS Advanced Options
 .PP
 Here are the advanced options specific to sftp (SSH/SFTP Connection).
-.SS \[en]sftp\-ask\-password
+.SS \-\-sftp\-ask\-password
 .PP
 Allow asking for SFTP password when needed.
 .PP
@@ -29464,7 +26777,7 @@ Env Var: RCLONE_SFTP_ASK_PASSWORD
 Type: bool
 .IP \[bu] 2
 Default: false
-.SS \[en]sftp\-path\-override
+.SS \-\-sftp\-path\-override
 .PP
 Override path used by SSH connection.
 .PP
@@ -29479,7 +26792,7 @@ rclone sync /home/local/directory remote:/directory \-\-ssh\-path\-override /vol
 \f[R]
 .fi
 .PP
-Home directory can be found in a shared folder called \[lq]home\[rq]
+Home directory can be found in a shared folder called \[dq]home\[dq]
 .IP
 .nf
 \f[C]
@@ -29494,7 +26807,7 @@ Env Var: RCLONE_SFTP_PATH_OVERRIDE
 Type: string
 .IP \[bu] 2
 Default: \[dq]\[dq]
-.SS \[en]sftp\-set\-modtime
+.SS \-\-sftp\-set\-modtime
 .PP
 Set the modified time on the remote if set.
 .IP \[bu] 2
@@ -29505,7 +26818,7 @@ Env Var: RCLONE_SFTP_SET_MODTIME
 Type: bool
 .IP \[bu] 2
 Default: true
-.SS \[en]sftp\-md5sum\-command
+.SS \-\-sftp\-md5sum\-command
 .PP
 The command used to read md5 hashes.
 Leave blank for autodetect.
@@ -29517,7 +26830,7 @@ Env Var: RCLONE_SFTP_MD5SUM_COMMAND
 Type: string
 .IP \[bu] 2
 Default: \[dq]\[dq]
-.SS \[en]sftp\-sha1sum\-command
+.SS \-\-sftp\-sha1sum\-command
 .PP
 The command used to read sha1 hashes.
 Leave blank for autodetect.
@@ -29529,7 +26842,7 @@ Env Var: RCLONE_SFTP_SHA1SUM_COMMAND
 Type: string
 .IP \[bu] 2
 Default: \[dq]\[dq]
-.SS \[en]sftp\-skip\-links
+.SS \-\-sftp\-skip\-links
 .PP
 Set to skip any symlinks and any other non regular files.
 .IP \[bu] 2
@@ -29540,11 +26853,35 @@ Env Var: RCLONE_SFTP_SKIP_LINKS
 Type: bool
 .IP \[bu] 2
 Default: false
+.SS \-\-sftp\-subsystem
+.PP
+Specifies the SSH2 subsystem on the remote host.
+.IP \[bu] 2
+Config: subsystem
+.IP \[bu] 2
+Env Var: RCLONE_SFTP_SUBSYSTEM
+.IP \[bu] 2
+Type: string
+.IP \[bu] 2
+Default: \[dq]sftp\[dq]
+.SS \-\-sftp\-server\-command
+.PP
+Specifies the path or command to run a sftp server on the remote host.
+.PP
+The subsystem option is ignored when server_command is defined.
+.IP \[bu] 2
+Config: server_command
+.IP \[bu] 2
+Env Var: RCLONE_SFTP_SERVER_COMMAND
+.IP \[bu] 2
+Type: string
+.IP \[bu] 2
+Default: \[dq]\[dq]
 .SS Limitations
 .PP
 SFTP supports checksums if the same login has shell access and
 \f[C]md5sum\f[R] or \f[C]sha1sum\f[R] as well as \f[C]echo\f[R] are in
-the remote\[cq]s PATH.
+the remote\[aq]s PATH.
 This remote checksumming (file hashing) is recommended and enabled by
 default.
 Disabling the checksumming may be required if you are connecting to SFTP
@@ -29554,18 +26891,18 @@ Set the configuration option \f[C]disable_hashcheck\f[R] to
 \f[C]true\f[R] to disable checksumming.
 .PP
 SFTP also supports \f[C]about\f[R] if the same login has shell access
-and \f[C]df\f[R] are in the remote\[cq]s PATH.
+and \f[C]df\f[R] are in the remote\[aq]s PATH.
 \f[C]about\f[R] will return the total space, free space, and used space
 on the remote for the disk of the specified path on the remote or, if
 not set, the disk of the root on the remote.
 \f[C]about\f[R] will fail if it does not have shell access or if
-\f[C]df\f[R] is not in the remote\[cq]s PATH.
+\f[C]df\f[R] is not in the remote\[aq]s PATH.
 .PP
 Note that some SFTP servers (eg Synology) the paths are different for
-SSH and SFTP so the hashes can\[cq]t be calculated properly.
+SSH and SFTP so the hashes can\[aq]t be calculated properly.
 For them using \f[C]disable_hashcheck\f[R] is a good idea.
 .PP
-The only ssh agent supported under Windows is Putty\[cq]s pageant.
+The only ssh agent supported under Windows is Putty\[aq]s pageant.
 .PP
 The Go SSH library disables the use of the aes128\-cbc cipher by
 default, due to security concerns.
@@ -29575,26 +26912,26 @@ This can be re\-enabled on a per\-connection basis by setting the
 Further details on the insecurity of this cipher can be found [in this
 paper] (http://www.isg.rhul.ac.uk/\[ti]kp/SandPfinal.pdf).
 .PP
-SFTP isn\[cq]t supported under plan9 until this
+SFTP isn\[aq]t supported under plan9 until this
 issue (https://github.com/pkg/sftp/issues/156) is fixed.
 .PP
-Note that since SFTP isn\[cq]t HTTP based the following flags don\[cq]t
+Note that since SFTP isn\[aq]t HTTP based the following flags don\[aq]t
 work with it: \f[C]\-\-dump\-headers\f[R], \f[C]\-\-dump\-bodies\f[R],
 \f[C]\-\-dump\-auth\f[R]
 .PP
-Note that \f[C]\-\-timeout\f[R] isn\[cq]t supported (but
+Note that \f[C]\-\-timeout\f[R] isn\[aq]t supported (but
 \f[C]\-\-contimeout\f[R] is).
 .SS C14
 .PP
 C14 is supported through the SFTP backend.
 .PP
-See C14\[cq]s
+See C14\[aq]s
 documentation (https://www.online.net/en/storage/c14-cold-storage)
 .SS rsync.net
 .PP
 rsync.net is supported through the SFTP backend.
 .PP
-See rsync.net\[cq]s documentation of rclone
+See rsync.net\[aq]s documentation of rclone
 examples (https://www.rsync.net/products/rclone.html).
 .SS SugarSync
 .PP
@@ -29671,7 +27008,7 @@ y/e/d> y
 \f[R]
 .fi
 .PP
-Note that the config asks for your email and password but doesn\[cq]t
+Note that the config asks for your email and password but doesn\[aq]t
 store them, it only uses them to get the initial token.
 .PP
 Once configured you can then use \f[C]rclone\f[R] like this,
@@ -29684,7 +27021,7 @@ rclone lsd remote:
 \f[R]
 .fi
 .PP
-List all the files in your SugarSync folder \[lq]Test\[rq]
+List all the files in your SugarSync folder \[dq]Test\[dq]
 .IP
 .nf
 \f[C]
@@ -29705,8 +27042,8 @@ Paths are specified as \f[C]remote:path\f[R]
 Paths may be as deep as required, eg
 \f[C]remote:directory/subdirectory\f[R].
 .PP
-\f[B]NB\f[R] you can\[cq]t create files in the top level folder you have
-to create a folder, which rclone will create as a \[lq]Sync Folder\[rq]
+\f[B]NB\f[R] you can\[aq]t create files in the top level folder you have
+to create a folder, which rclone will create as a \[dq]Sync Folder\[dq]
 with SugarSync.
 .SS Modified time and hashes
 .PP
@@ -29720,11 +27057,11 @@ SugarSync replaces the default restricted characters
 set (https://rclone.org/overview/#restricted-characters) except for DEL.
 .PP
 Invalid UTF\-8 bytes will also be
-replaced (https://rclone.org/overview/#invalid-utf8), as they can\[cq]t
+replaced (https://rclone.org/overview/#invalid-utf8), as they can\[aq]t
 be used in XML strings.
 .SS Deleting files
 .PP
-Deleted files will be moved to the \[lq]Deleted items\[rq] folder by
+Deleted files will be moved to the \[dq]Deleted items\[dq] folder by
 default.
 .PP
 However you can supply the flag \f[C]\-\-sugarsync\-hard\-delete\f[R] or
@@ -29733,11 +27070,11 @@ files to be deleted straight away.
 .SS Standard Options
 .PP
 Here are the standard options specific to sugarsync (Sugarsync).
-.SS \[en]sugarsync\-app\-id
+.SS \-\-sugarsync\-app\-id
 .PP
 Sugarsync App ID.
 .PP
-Leave blank to use rclone\[cq]s.
+Leave blank to use rclone\[aq]s.
 .IP \[bu] 2
 Config: app_id
 .IP \[bu] 2
@@ -29746,11 +27083,11 @@ Env Var: RCLONE_SUGARSYNC_APP_ID
 Type: string
 .IP \[bu] 2
 Default: \[dq]\[dq]
-.SS \[en]sugarsync\-access\-key\-id
+.SS \-\-sugarsync\-access\-key\-id
 .PP
 Sugarsync Access Key ID.
 .PP
-Leave blank to use rclone\[cq]s.
+Leave blank to use rclone\[aq]s.
 .IP \[bu] 2
 Config: access_key_id
 .IP \[bu] 2
@@ -29759,11 +27096,11 @@ Env Var: RCLONE_SUGARSYNC_ACCESS_KEY_ID
 Type: string
 .IP \[bu] 2
 Default: \[dq]\[dq]
-.SS \[en]sugarsync\-private\-access\-key
+.SS \-\-sugarsync\-private\-access\-key
 .PP
 Sugarsync Private Access Key
 .PP
-Leave blank to use rclone\[cq]s.
+Leave blank to use rclone\[aq]s.
 .IP \[bu] 2
 Config: private_access_key
 .IP \[bu] 2
@@ -29772,7 +27109,7 @@ Env Var: RCLONE_SUGARSYNC_PRIVATE_ACCESS_KEY
 Type: string
 .IP \[bu] 2
 Default: \[dq]\[dq]
-.SS \[en]sugarsync\-hard\-delete
+.SS \-\-sugarsync\-hard\-delete
 .PP
 Permanently delete files if true otherwise put them in the deleted
 files.
@@ -29787,7 +27124,7 @@ Default: false
 .SS Advanced Options
 .PP
 Here are the advanced options specific to sugarsync (Sugarsync).
-.SS \[en]sugarsync\-refresh\-token
+.SS \-\-sugarsync\-refresh\-token
 .PP
 Sugarsync refresh token
 .PP
@@ -29800,7 +27137,7 @@ Env Var: RCLONE_SUGARSYNC_REFRESH_TOKEN
 Type: string
 .IP \[bu] 2
 Default: \[dq]\[dq]
-.SS \[en]sugarsync\-authorization
+.SS \-\-sugarsync\-authorization
 .PP
 Sugarsync authorization
 .PP
@@ -29813,7 +27150,7 @@ Env Var: RCLONE_SUGARSYNC_AUTHORIZATION
 Type: string
 .IP \[bu] 2
 Default: \[dq]\[dq]
-.SS \[en]sugarsync\-authorization\-expiry
+.SS \-\-sugarsync\-authorization\-expiry
 .PP
 Sugarsync authorization expiry
 .PP
@@ -29826,7 +27163,7 @@ Env Var: RCLONE_SUGARSYNC_AUTHORIZATION_EXPIRY
 Type: string
 .IP \[bu] 2
 Default: \[dq]\[dq]
-.SS \[en]sugarsync\-user
+.SS \-\-sugarsync\-user
 .PP
 Sugarsync user
 .PP
@@ -29839,7 +27176,7 @@ Env Var: RCLONE_SUGARSYNC_USER
 Type: string
 .IP \[bu] 2
 Default: \[dq]\[dq]
-.SS \[en]sugarsync\-root\-id
+.SS \-\-sugarsync\-root\-id
 .PP
 Sugarsync root id
 .PP
@@ -29852,7 +27189,7 @@ Env Var: RCLONE_SUGARSYNC_ROOT_ID
 Type: string
 .IP \[bu] 2
 Default: \[dq]\[dq]
-.SS \[en]sugarsync\-deleted\-id
+.SS \-\-sugarsync\-deleted\-id
 .PP
 Sugarsync deleted folder id
 .PP
@@ -29865,7 +27202,7 @@ Env Var: RCLONE_SUGARSYNC_DELETED_ID
 Type: string
 .IP \[bu] 2
 Default: \[dq]\[dq]
-.SS \[en]sugarsync\-encoding
+.SS \-\-sugarsync\-encoding
 .PP
 This sets the encoding for the backend.
 .PP
@@ -30013,8 +27350,8 @@ the \f[C]lsf\f[R] command.) You may put subdirectories in too, eg
 Once configured you can then use \f[C]rclone\f[R] like this.
 .SS Create a new bucket
 .PP
-Use the \f[C]mkdir\f[R] command to create new bucket,
-e.g.\ \f[C]bucket\f[R].
+Use the \f[C]mkdir\f[R] command to create new bucket, e.g.
+\f[C]bucket\f[R].
 .IP
 .nf
 \f[C]
@@ -30061,7 +27398,7 @@ rclone copy \-\-progress /home/local/directory/file.ext remote:bucket/path/to/di
 .fi
 .PP
 The \f[C]\-\-progress\f[R] flag is for displaying progress information.
-Remove it if you don\[cq]t need this information.
+Remove it if you don\[aq]t need this information.
 .PP
 Use a folder in the local path to upload all its objects.
 .IP
@@ -30111,7 +27448,7 @@ rclone copy \-\-progress remote:bucket/path/to/dir/file.ext /home/local/director
 .fi
 .PP
 The \f[C]\-\-progress\f[R] flag is for displaying progress information.
-Remove it if you don\[cq]t need this information.
+Remove it if you don\[aq]t need this information.
 .PP
 Use a folder in the remote path to download all its objects.
 .IP
@@ -30154,12 +27491,12 @@ changing the destination only, deleting any excess files.
 .IP
 .nf
 \f[C]
-rclone sync \-\-progress /home/local/directory/ remote:bucket/path/to/dir/
+rclone sync \-i \-\-progress /home/local/directory/ remote:bucket/path/to/dir/
 \f[R]
 .fi
 .PP
 The \f[C]\-\-progress\f[R] flag is for displaying progress information.
-Remove it if you don\[cq]t need this information.
+Remove it if you don\[aq]t need this information.
 .PP
 Since this can cause data loss, test first with the
 \f[C]\-\-dry\-run\f[R] flag to see exactly what would be copied and
@@ -30169,7 +27506,7 @@ The sync can be done also from Tardigrade to the local file system.
 .IP
 .nf
 \f[C]
-rclone sync \-\-progress remote:bucket/path/to/dir/ /home/local/directory/
+rclone sync \-i \-\-progress remote:bucket/path/to/dir/ /home/local/directory/
 \f[R]
 .fi
 .PP
@@ -30177,7 +27514,7 @@ Or between two Tardigrade buckets.
 .IP
 .nf
 \f[C]
-rclone sync \-\-progress remote\-us:bucket/path/to/dir/ remote\-europe:bucket/path/to/dir/
+rclone sync \-i \-\-progress remote\-us:bucket/path/to/dir/ remote\-europe:bucket/path/to/dir/
 \f[R]
 .fi
 .PP
@@ -30185,14 +27522,14 @@ Or even between another cloud storage and Tardigrade.
 .IP
 .nf
 \f[C]
-rclone sync \-\-progress s3:bucket/path/to/dir/ tardigrade:bucket/path/to/dir/
+rclone sync \-i \-\-progress s3:bucket/path/to/dir/ tardigrade:bucket/path/to/dir/
 \f[R]
 .fi
 .SS Standard Options
 .PP
 Here are the standard options specific to tardigrade (Tardigrade
 Decentralized Cloud Storage).
-.SS \[en]tardigrade\-provider
+.SS \-\-tardigrade\-provider
 .PP
 Choose an authentication method.
 .IP \[bu] 2
@@ -30202,25 +27539,25 @@ Env Var: RCLONE_TARDIGRADE_PROVIDER
 .IP \[bu] 2
 Type: string
 .IP \[bu] 2
-Default: \[lq]existing\[rq]
+Default: \[dq]existing\[dq]
 .IP \[bu] 2
 Examples:
 .RS 2
 .IP \[bu] 2
-\[lq]existing\[rq]
+\[dq]existing\[dq]
 .RS 2
 .IP \[bu] 2
 Use an existing access grant.
 .RE
 .IP \[bu] 2
-\[lq]new\[rq]
+\[dq]new\[dq]
 .RS 2
 .IP \[bu] 2
 Create a new access grant from satellite address, API key, and
 passphrase.
 .RE
 .RE
-.SS \[en]tardigrade\-access\-grant
+.SS \-\-tardigrade\-access\-grant
 .PP
 Access Grant.
 .IP \[bu] 2
@@ -30231,7 +27568,7 @@ Env Var: RCLONE_TARDIGRADE_ACCESS_GRANT
 Type: string
 .IP \[bu] 2
 Default: \[dq]\[dq]
-.SS \[en]tardigrade\-satellite\-address
+.SS \-\-tardigrade\-satellite\-address
 .PP
 Satellite Address.
 Custom satellite address should match the format:
@@ -30243,30 +27580,30 @@ Env Var: RCLONE_TARDIGRADE_SATELLITE_ADDRESS
 .IP \[bu] 2
 Type: string
 .IP \[bu] 2
-Default: \[lq]us\-central\-1.tardigrade.io\[rq]
+Default: \[dq]us\-central\-1.tardigrade.io\[dq]
 .IP \[bu] 2
 Examples:
 .RS 2
 .IP \[bu] 2
-\[lq]us\-central\-1.tardigrade.io\[rq]
+\[dq]us\-central\-1.tardigrade.io\[dq]
 .RS 2
 .IP \[bu] 2
 US Central 1
 .RE
 .IP \[bu] 2
-\[lq]europe\-west\-1.tardigrade.io\[rq]
+\[dq]europe\-west\-1.tardigrade.io\[dq]
 .RS 2
 .IP \[bu] 2
 Europe West 1
 .RE
 .IP \[bu] 2
-\[lq]asia\-east\-1.tardigrade.io\[rq]
+\[dq]asia\-east\-1.tardigrade.io\[dq]
 .RS 2
 .IP \[bu] 2
 Asia East 1
 .RE
 .RE
-.SS \[en]tardigrade\-api\-key
+.SS \-\-tardigrade\-api\-key
 .PP
 API Key.
 .IP \[bu] 2
@@ -30277,7 +27614,7 @@ Env Var: RCLONE_TARDIGRADE_API_KEY
 Type: string
 .IP \[bu] 2
 Default: \[dq]\[dq]
-.SS \[en]tardigrade\-passphrase
+.SS \-\-tardigrade\-passphrase
 .PP
 Encryption Passphrase.
 To access existing objects enter passphrase used for uploading.
@@ -30663,11 +28000,11 @@ rclone copy C:\[rs]source remote:source
 .PP
 Here are the standard options specific to union (Union merges the
 contents of several upstream fs).
-.SS \[en]union\-upstreams
+.SS \-\-union\-upstreams
 .PP
 List of space separated upstreams.
-Can be `upstreama:test/dir upstreamb:', `\[lq]upstreama:test/space:ro
-dir\[rq] upstreamb:', etc.
+Can be \[aq]upstreama:test/dir upstreamb:\[aq],
+\[aq]\[dq]upstreama:test/space:ro dir\[dq] upstreamb:\[aq], etc.
 .IP \[bu] 2
 Config: upstreams
 .IP \[bu] 2
@@ -30676,7 +28013,7 @@ Env Var: RCLONE_UNION_UPSTREAMS
 Type: string
 .IP \[bu] 2
 Default: \[dq]\[dq]
-.SS \[en]union\-action\-policy
+.SS \-\-union\-action\-policy
 .PP
 Policy to choose upstream on ACTION category.
 .IP \[bu] 2
@@ -30686,8 +28023,8 @@ Env Var: RCLONE_UNION_ACTION_POLICY
 .IP \[bu] 2
 Type: string
 .IP \[bu] 2
-Default: \[lq]epall\[rq]
-.SS \[en]union\-create\-policy
+Default: \[dq]epall\[dq]
+.SS \-\-union\-create\-policy
 .PP
 Policy to choose upstream on CREATE category.
 .IP \[bu] 2
@@ -30697,8 +28034,8 @@ Env Var: RCLONE_UNION_CREATE_POLICY
 .IP \[bu] 2
 Type: string
 .IP \[bu] 2
-Default: \[lq]epmfs\[rq]
-.SS \[en]union\-search\-policy
+Default: \[dq]epmfs\[dq]
+.SS \-\-union\-search\-policy
 .PP
 Policy to choose upstream on SEARCH category.
 .IP \[bu] 2
@@ -30708,8 +28045,8 @@ Env Var: RCLONE_UNION_SEARCH_POLICY
 .IP \[bu] 2
 Type: string
 .IP \[bu] 2
-Default: \[lq]ff\[rq]
-.SS \[en]union\-cache\-time
+Default: \[dq]ff\[dq]
+.SS \-\-union\-cache\-time
 .PP
 Cache time of usage and free space (in seconds).
 This option is only useful when a path preserving policy is used.
@@ -30844,7 +28181,7 @@ them.
 .SS Standard Options
 .PP
 Here are the standard options specific to webdav (Webdav).
-.SS \[en]webdav\-url
+.SS \-\-webdav\-url
 .PP
 URL of http host to connect to
 .IP \[bu] 2
@@ -30859,13 +28196,13 @@ Default: \[dq]\[dq]
 Examples:
 .RS 2
 .IP \[bu] 2
-\[lq]https://example.com\[rq]
+\[dq]https://example.com\[dq]
 .RS 2
 .IP \[bu] 2
 Connect to example.com
 .RE
 .RE
-.SS \[en]webdav\-vendor
+.SS \-\-webdav\-vendor
 .PP
 Name of the Webdav site/service/software you are using
 .IP \[bu] 2
@@ -30880,31 +28217,31 @@ Default: \[dq]\[dq]
 Examples:
 .RS 2
 .IP \[bu] 2
-\[lq]nextcloud\[rq]
+\[dq]nextcloud\[dq]
 .RS 2
 .IP \[bu] 2
 Nextcloud
 .RE
 .IP \[bu] 2
-\[lq]owncloud\[rq]
+\[dq]owncloud\[dq]
 .RS 2
 .IP \[bu] 2
 Owncloud
 .RE
 .IP \[bu] 2
-\[lq]sharepoint\[rq]
+\[dq]sharepoint\[dq]
 .RS 2
 .IP \[bu] 2
 Sharepoint
 .RE
 .IP \[bu] 2
-\[lq]other\[rq]
+\[dq]other\[dq]
 .RS 2
 .IP \[bu] 2
 Other site/service or software
 .RE
 .RE
-.SS \[en]webdav\-user
+.SS \-\-webdav\-user
 .PP
 User name
 .IP \[bu] 2
@@ -30915,9 +28252,12 @@ Env Var: RCLONE_WEBDAV_USER
 Type: string
 .IP \[bu] 2
 Default: \[dq]\[dq]
-.SS \[en]webdav\-pass
+.SS \-\-webdav\-pass
 .PP
 Password.
+.PP
+\f[B]NB\f[R] Input to this must be obscured \- see rclone
+obscure (https://rclone.org/commands/rclone_obscure/).
 .IP \[bu] 2
 Config: pass
 .IP \[bu] 2
@@ -30926,7 +28266,7 @@ Env Var: RCLONE_WEBDAV_PASS
 Type: string
 .IP \[bu] 2
 Default: \[dq]\[dq]
-.SS \[en]webdav\-bearer\-token
+.SS \-\-webdav\-bearer\-token
 .PP
 Bearer token instead of user/pass (eg a Macaroon)
 .IP \[bu] 2
@@ -30940,7 +28280,7 @@ Default: \[dq]\[dq]
 .SS Advanced Options
 .PP
 Here are the advanced options specific to webdav (Webdav).
-.SS \[en]webdav\-bearer\-token\-command
+.SS \-\-webdav\-bearer\-token\-command
 .PP
 Command to run to get a bearer token
 .IP \[bu] 2
@@ -30980,12 +28320,12 @@ Office365 Education ones.
 These accounts are sometimes not verified by the domain owner
 github#1975 (https://github.com/rclone/rclone/issues/1975)
 .PP
-This means that these accounts can\[cq]t be added using the official API
-(other Accounts should work with the \[lq]onedrive\[rq] option).
+This means that these accounts can\[aq]t be added using the official API
+(other Accounts should work with the \[dq]onedrive\[dq] option).
 However, it is possible to access them using webdav.
 .PP
 To use a sharepoint remote with rclone, add it like this: First, you
-need to get your remote\[cq]s URL:
+need to get your remote\[aq]s URL:
 .IP \[bu] 2
 Go here (https://onedrive.live.com/about/en-us/signin/) to open your
 OneDrive or to sign in
@@ -30993,8 +28333,8 @@ OneDrive or to sign in
 Now take a look at your address bar, the URL should look like this:
 \f[C]https://[YOUR\-DOMAIN]\-my.sharepoint.com/personal/[YOUR\-EMAIL]/_layouts/15/onedrive.aspx\f[R]
 .PP
-You\[cq]ll only need this URL up to the email address.
-After that, you\[cq]ll most likely want to add \[lq]/Documents\[rq].
+You\[aq]ll only need this URL up to the email address.
+After that, you\[aq]ll most likely want to add \[dq]/Documents\[dq].
 That subdirectory contains the actual data stored on your OneDrive.
 .PP
 Add the remote to rclone like this: Configure the \f[C]url\f[R] as
@@ -31019,13 +28359,13 @@ pass = encryptedpassword
 .SS Required Flags for SharePoint
 .PP
 As SharePoint does some special things with uploaded documents, you
-won\[cq]t be able to use the documents size or the documents hash to
+won\[aq]t be able to use the documents size or the documents hash to
 compare if a file has been changed since the upload / which file is
 newer.
 .PP
 For Rclone calls copying files (especially Office files such as .docx,
 \&.xlsx, etc.) from/to SharePoint (like copy, sync, etc.), you should
-append these flags to ensure Rclone uses the \[lq]Last Modified\[rq]
+append these flags to ensure Rclone uses the \[dq]Last Modified\[dq]
 datetime property to compare your documents:
 .IP
 .nf
@@ -31044,7 +28384,7 @@ and OpenID\-Connect (https://en.wikipedia.org/wiki/OpenID_Connect)
 access tokens.
 .PP
 Configure as normal using the \f[C]other\f[R] type.
-Don\[cq]t enter a username or password, instead enter your Macaroon as
+Don\[aq]t enter a username or password, instead enter your Macaroon as
 the \f[C]bearer_token\f[R].
 .PP
 The config will end up looking something like this.
@@ -31103,8 +28443,8 @@ documentation (https://indigo-dc.gitbooks.io/oidc-agent/).
 The rclone \f[C]bearer_token_command\f[R] configuration option is used
 to fetch the access token from oidc\-agent.
 .PP
-Configure as a normal WebDAV endpoint, using the `other' vendor, leaving
-the username and password empty.
+Configure as a normal WebDAV endpoint, using the \[aq]other\[aq] vendor,
+leaving the username and password empty.
 When prompted, choose to edit the advanced config and enter the command
 to get a bearer token (e.g., \f[C]oidc\-agent XDC\f[R]).
 .PP
@@ -31220,7 +28560,7 @@ excess files in the path.
 .IP
 .nf
 \f[C]
-rclone sync /home/local/directory remote:directory
+rclone sync \-i /home/local/directory remote:directory
 \f[R]
 .fi
 .PP
@@ -31251,7 +28591,7 @@ The default restricted characters
 set (https://rclone.org/overview/#restricted-characters) are replaced.
 .PP
 Invalid UTF\-8 bytes will also be
-replaced (https://rclone.org/overview/#invalid-utf8), as they can\[cq]t
+replaced (https://rclone.org/overview/#invalid-utf8), as they can\[aq]t
 be used in JSON strings.
 .SS Limitations
 .PP
@@ -31261,7 +28601,7 @@ This is because Yandex pauses (perhaps to calculate the MD5SUM for the
 entire file) before returning confirmation that the file has been
 uploaded.
 The default handling of timeouts in rclone is to assume a 5 minute pause
-is an error and close the connection \- you\[cq]ll see
+is an error and close the connection \- you\[aq]ll see
 \f[C]net/http: timeout awaiting response headers\f[R] errors in the logs
 if this is happening.
 Setting the timeout to twice the max size of file in GB should be
@@ -31270,9 +28610,9 @@ enough, so if you want to upload a 30GB file set a timeout of
 .SS Standard Options
 .PP
 Here are the standard options specific to yandex (Yandex Disk).
-.SS \[en]yandex\-client\-id
+.SS \-\-yandex\-client\-id
 .PP
-Yandex Client Id Leave blank normally.
+OAuth Client Id Leave blank normally.
 .IP \[bu] 2
 Config: client_id
 .IP \[bu] 2
@@ -31281,9 +28621,9 @@ Env Var: RCLONE_YANDEX_CLIENT_ID
 Type: string
 .IP \[bu] 2
 Default: \[dq]\[dq]
-.SS \[en]yandex\-client\-secret
+.SS \-\-yandex\-client\-secret
 .PP
-Yandex Client Secret Leave blank normally.
+OAuth Client Secret Leave blank normally.
 .IP \[bu] 2
 Config: client_secret
 .IP \[bu] 2
@@ -31295,21 +28635,42 @@ Default: \[dq]\[dq]
 .SS Advanced Options
 .PP
 Here are the advanced options specific to yandex (Yandex Disk).
-.SS \[en]yandex\-unlink
+.SS \-\-yandex\-token
 .PP
-Remove existing public link to file/folder with link command rather than
-creating.
-Default is false, meaning link command will create or retrieve public
-link.
+OAuth Access Token as a JSON blob.
 .IP \[bu] 2
-Config: unlink
+Config: token
 .IP \[bu] 2
-Env Var: RCLONE_YANDEX_UNLINK
+Env Var: RCLONE_YANDEX_TOKEN
 .IP \[bu] 2
-Type: bool
+Type: string
 .IP \[bu] 2
-Default: false
-.SS \[en]yandex\-encoding
+Default: \[dq]\[dq]
+.SS \-\-yandex\-auth\-url
+.PP
+Auth server URL.
+Leave blank to use the provider defaults.
+.IP \[bu] 2
+Config: auth_url
+.IP \[bu] 2
+Env Var: RCLONE_YANDEX_AUTH_URL
+.IP \[bu] 2
+Type: string
+.IP \[bu] 2
+Default: \[dq]\[dq]
+.SS \-\-yandex\-token\-url
+.PP
+Token server url.
+Leave blank to use the provider defaults.
+.IP \[bu] 2
+Config: token_url
+.IP \[bu] 2
+Env Var: RCLONE_YANDEX_TOKEN_URL
+.IP \[bu] 2
+Type: string
+.IP \[bu] 2
+Default: \[dq]\[dq]
+.SS \-\-yandex\-encoding
 .PP
 This sets the encoding for the backend.
 .PP
@@ -31330,7 +28691,7 @@ Local paths are specified as normal filesystem paths, eg
 .IP
 .nf
 \f[C]
-rclone sync /home/source /tmp/destination
+rclone sync \-i /home/source /tmp/destination
 \f[R]
 .fi
 .PP
@@ -31353,7 +28714,7 @@ distributions will have UTF\-8 encoded files names.
 If you are using an old Linux filesystem with non UTF\-8 file names (eg
 latin1) then you can use the \f[C]convmv\f[R] tool to convert the
 filesystem to UTF\-8.
-This tool is available in most distributions\[cq] package managers.
+This tool is available in most distributions\[aq] package managers.
 .PP
 If an invalid (non\-UTF8) filename is read, the invalid characters will
 be replaced with a quoted representation of the invalid bytes.
@@ -31734,7 +29095,7 @@ T}
 .TE
 .PP
 Invalid UTF\-8 bytes will also be
-replaced (https://rclone.org/overview/#invalid-utf8), as they can\[cq]t
+replaced (https://rclone.org/overview/#invalid-utf8), as they can\[aq]t
 be converted to UTF\-16.
 .SS Long paths on Windows
 .PP
@@ -31828,14 +29189,14 @@ $ rclone \-L ls /tmp/a
         6 b/one
 \f[R]
 .fi
-.SS \[en]links, \-l
+.SS \-\-links, \-l
 .PP
 Normally rclone will ignore symlinks or junction points (which behave
 like symlinks under Windows).
 .PP
 If you supply this flag then rclone will copy symbolic links from the
-local storage, and store them as text files, with a `.rclonelink' suffix
-in the remote storage.
+local storage, and store them as text files, with a
+\[aq].rclonelink\[aq] suffix in the remote storage.
 .PP
 The text file will contain the target of the symbolic link (see
 example).
@@ -31853,7 +29214,7 @@ $ tree /tmp/a
 \f[R]
 .fi
 .PP
-Copying the entire directory with `\-l'
+Copying the entire directory with \[aq]\-l\[aq]
 .IP
 .nf
 \f[C]
@@ -31861,7 +29222,7 @@ $ rclone copyto \-l /tmp/a/file1 remote:/tmp/a/
 \f[R]
 .fi
 .PP
-The remote files are created with a `.rclonelink' suffix
+The remote files are created with a \[aq].rclonelink\[aq] suffix
 .IP
 .nf
 \f[C]
@@ -31883,7 +29244,7 @@ $ rclone cat remote:/tmp/a/file2.rclonelink
 \f[R]
 .fi
 .PP
-Copying them back with `\-l'
+Copying them back with \[aq]\-l\[aq]
 .IP
 .nf
 \f[C]
@@ -31896,7 +29257,7 @@ $ tree /tmp/b
 \f[R]
 .fi
 .PP
-However, if copied back without `\-l'
+However, if copied back without \[aq]\-l\[aq]
 .IP
 .nf
 \f[C]
@@ -31911,7 +29272,7 @@ $ tree /tmp/b
 .PP
 Note that this flag is incompatible with \f[C]\-copy\-links\f[R] /
 \f[C]\-L\f[R].
-.SS Restricting filesystems with \[en]one\-file\-system
+.SS Restricting filesystems with \-\-one\-file\-system
 .PP
 Normally rclone will recurse through filesystems as mounted.
 .PP
@@ -31960,11 +29321,11 @@ $ rclone \-q ls root
 device as being on the same filesystem.
 .PP
 \f[B]NB\f[R] This flag is only available on Unix based systems.
-On systems where it isn\[cq]t supported (eg Windows) it will be ignored.
+On systems where it isn\[aq]t supported (eg Windows) it will be ignored.
 .SS Standard Options
 .PP
 Here are the standard options specific to local (Local Disk).
-.SS \[en]local\-nounc
+.SS \-\-local\-nounc
 .PP
 Disable UNC (long path names) conversion on Windows
 .IP \[bu] 2
@@ -31979,7 +29340,7 @@ Default: \[dq]\[dq]
 Examples:
 .RS 2
 .IP \[bu] 2
-\[lq]true\[rq]
+\[dq]true\[dq]
 .RS 2
 .IP \[bu] 2
 Disables long file names
@@ -31988,7 +29349,7 @@ Disables long file names
 .SS Advanced Options
 .PP
 Here are the advanced options specific to local (Local Disk).
-.SS \[en]copy\-links / \-L
+.SS \-\-copy\-links / \-L
 .PP
 Follow symlinks and copy the pointed to item.
 .IP \[bu] 2
@@ -31999,9 +29360,10 @@ Env Var: RCLONE_LOCAL_COPY_LINKS
 Type: bool
 .IP \[bu] 2
 Default: false
-.SS \[en]links / \-l
+.SS \-\-links / \-l
 .PP
-Translate symlinks to/from regular files with a `.rclonelink' extension
+Translate symlinks to/from regular files with a \[aq].rclonelink\[aq]
+extension
 .IP \[bu] 2
 Config: links
 .IP \[bu] 2
@@ -32010,9 +29372,9 @@ Env Var: RCLONE_LOCAL_LINKS
 Type: bool
 .IP \[bu] 2
 Default: false
-.SS \[en]skip\-links
+.SS \-\-skip\-links
 .PP
-Don\[cq]t warn about skipped symlinks.
+Don\[aq]t warn about skipped symlinks.
 This flag disables warning messages on skipped symlinks or junction
 points, as you explicitly acknowledge that they should be skipped.
 .IP \[bu] 2
@@ -32023,9 +29385,9 @@ Env Var: RCLONE_LOCAL_SKIP_LINKS
 Type: bool
 .IP \[bu] 2
 Default: false
-.SS \[en]local\-no\-unicode\-normalization
+.SS \-\-local\-no\-unicode\-normalization
 .PP
-Don\[cq]t apply unicode normalization to paths and filenames
+Don\[aq]t apply unicode normalization to paths and filenames
 (Deprecated)
 .PP
 This flag is deprecated now.
@@ -32039,18 +29401,36 @@ Env Var: RCLONE_LOCAL_NO_UNICODE_NORMALIZATION
 Type: bool
 .IP \[bu] 2
 Default: false
-.SS \[en]local\-no\-check\-updated
+.SS \-\-local\-no\-check\-updated
 .PP
-Don\[cq]t check to see if the files change during upload
+Don\[aq]t check to see if the files change during upload
 .PP
 Normally rclone checks the size and modification time of files as they
-are being uploaded and aborts with a message which starts \[lq]can\[cq]t
-copy \- source file is being updated\[rq] if the file changes during
+are being uploaded and aborts with a message which starts \[dq]can\[aq]t
+copy \- source file is being updated\[dq] if the file changes during
 upload.
 .PP
 However on some file systems this modification time check may fail (eg
 Glusterfs #2206 (https://github.com/rclone/rclone/issues/2206)) so this
 check can be disabled with this flag.
+.PP
+If this flag is set, rclone will use its best efforts to transfer a file
+which is being updated.
+If the file is only having things appended to it (eg a log) then rclone
+will transfer the log file with the size it had the first time rclone
+saw it.
+.PP
+If the file is being modified throughout (not just appended to) then the
+transfer may fail with a hash check failure.
+.PP
+In detail, once the file has had stat() called on it for the first time
+we:
+.IP \[bu] 2
+Only transfer the size that stat gave
+.IP \[bu] 2
+Only checksum the size that stat gave
+.IP \[bu] 2
+Don\[aq]t update the stat info for the file
 .IP \[bu] 2
 Config: no_check_updated
 .IP \[bu] 2
@@ -32059,9 +29439,9 @@ Env Var: RCLONE_LOCAL_NO_CHECK_UPDATED
 Type: bool
 .IP \[bu] 2
 Default: false
-.SS \[en]one\-file\-system / \-x
+.SS \-\-one\-file\-system / \-x
 .PP
-Don\[cq]t cross filesystem boundaries (unix/macOS only).
+Don\[aq]t cross filesystem boundaries (unix/macOS only).
 .IP \[bu] 2
 Config: one_file_system
 .IP \[bu] 2
@@ -32070,7 +29450,7 @@ Env Var: RCLONE_LOCAL_ONE_FILE_SYSTEM
 Type: bool
 .IP \[bu] 2
 Default: false
-.SS \[en]local\-case\-sensitive
+.SS \-\-local\-case\-sensitive
 .PP
 Force the filesystem to report itself as case sensitive.
 .PP
@@ -32085,7 +29465,7 @@ Env Var: RCLONE_LOCAL_CASE_SENSITIVE
 Type: bool
 .IP \[bu] 2
 Default: false
-.SS \[en]local\-case\-insensitive
+.SS \-\-local\-case\-insensitive
 .PP
 Force the filesystem to report itself as case insensitive
 .PP
@@ -32100,7 +29480,7 @@ Env Var: RCLONE_LOCAL_CASE_INSENSITIVE
 Type: bool
 .IP \[bu] 2
 Default: false
-.SS \[en]local\-no\-sparse
+.SS \-\-local\-no\-sparse
 .PP
 Disable sparse files for multi\-thread downloads
 .PP
@@ -32117,7 +29497,26 @@ Env Var: RCLONE_LOCAL_NO_SPARSE
 Type: bool
 .IP \[bu] 2
 Default: false
-.SS \[en]local\-encoding
+.SS \-\-local\-no\-set\-modtime
+.PP
+Disable setting modtime
+.PP
+Normally rclone updates modification time of files after they are done
+uploading.
+This can cause permissions issues on Linux platforms when the user
+rclone is running as does not own the file uploaded, such as when
+copying to a CIFS mount owned by another user.
+If this option is enabled, rclone will no longer update the modtime
+after copying a file.
+.IP \[bu] 2
+Config: no_set_modtime
+.IP \[bu] 2
+Env Var: RCLONE_LOCAL_NO_SET_MODTIME
+.IP \[bu] 2
+Type: bool
+.IP \[bu] 2
+Default: false
+.SS \-\-local\-encoding
 .PP
 This sets the encoding for the backend.
 .PP
@@ -32145,7 +29544,7 @@ rclone backend COMMAND remote:
 .PP
 The help below will explain what arguments each command takes.
 .PP
-See the \[lq]rclone backend\[rq]
+See the \[dq]rclone backend\[dq]
 command (https://rclone.org/commands/rclone_backend/) for more info on
 how to pass options and arguments.
 .PP
@@ -32166,10 +29565,746 @@ output.
 .PP
 Options:
 .IP \[bu] 2
-\[lq]echo\[rq]: echo the input arguments
+\[dq]echo\[dq]: echo the input arguments
 .IP \[bu] 2
-\[lq]error\[rq]: return an error based on option value
+\[dq]error\[dq]: return an error based on option value
 .SH Changelog
+.SS v1.53.0 \- 2020\-09\-02
+.PP
+See commits (https://github.com/rclone/rclone/compare/v1.52.0...v1.53.0)
+.IP \[bu] 2
+New Features
+.RS 2
+.IP \[bu] 2
+The VFS
+layer (https://rclone.org/commands/rclone_mount/#vfs-virtual-file-system)
+was heavily reworked for this release \- see below for more details
+.IP \[bu] 2
+Interactive mode
+\-i/\-\-interactive (https://rclone.org/docs/#interactive) for
+destructive operations (fishbullet)
+.IP \[bu] 2
+Add
+\-\-bwlimit\-file (https://rclone.org/docs/#bwlimit-file-bandwidth-spec)
+flag to limit speeds of individual file transfers (Nick Craig\-Wood)
+.IP \[bu] 2
+Transfers are sorted by start time in the stats and progress output (Max
+Sum)
+.IP \[bu] 2
+Make sure backends expand \f[C]\[ti]\f[R] and environment vars in file
+names they use (Nick Craig\-Wood)
+.IP \[bu] 2
+Add \-\-refresh\-times (https://rclone.org/docs/#refresh-times) flag to
+set modtimes on hashless backends (Nick Craig\-Wood)
+.IP \[bu] 2
+build
+.RS 2
+.IP \[bu] 2
+Remove vendor directory in favour of Go modules (Nick Craig\-Wood)
+.IP \[bu] 2
+Build with go1.15.x by default (Nick Craig\-Wood)
+.IP \[bu] 2
+Drop macOS 386 build as it is no longer supported by go1.15 (Nick
+Craig\-Wood)
+.IP \[bu] 2
+Add ARMv7 to the supported builds (Nick Craig\-Wood)
+.IP \[bu] 2
+Enable \f[C]rclone cmount\f[R] on macOS (Nick Craig\-Wood)
+.IP \[bu] 2
+Make rclone build with gccgo (Nick Craig\-Wood)
+.IP \[bu] 2
+Make rclone build with wasm (Nick Craig\-Wood)
+.IP \[bu] 2
+Change beta numbering to be semver compatible (Nick Craig\-Wood)
+.IP \[bu] 2
+Add file properties and icon to Windows executable (albertony)
+.IP \[bu] 2
+Add experimental interface for integrating rclone into browsers (Nick
+Craig\-Wood)
+.RE
+.IP \[bu] 2
+lib: Add file name compression (Klaus Post)
+.IP \[bu] 2
+rc
+.RS 2
+.IP \[bu] 2
+Allow installation and use of plugins and test plugins with
+rclone\-webui (Chaitanya Bankanhal)
+.IP \[bu] 2
+Add reverse proxy pluginsHandler for serving plugins (Chaitanya
+Bankanhal)
+.IP \[bu] 2
+Add \f[C]mount/listmounts\f[R] option for listing current mounts
+(Chaitanya Bankanhal)
+.IP \[bu] 2
+Add \f[C]operations/uploadfile\f[R] to upload a file through rc using
+encoding multipart/form\-data (Chaitanya Bankanhal)
+.IP \[bu] 2
+Add \f[C]core/copmmand\f[R] to execute rclone terminal commands.
+(Chaitanya Bankanhal)
+.RE
+.IP \[bu] 2
+\f[C]rclone check\f[R]
+.RS 2
+.IP \[bu] 2
+Add reporting of filenames for same/missing/changed (Nick Craig\-Wood)
+.IP \[bu] 2
+Make check command obey
+\f[C]\-\-dry\-run\f[R]/\f[C]\-i\f[R]/\f[C]\-\-interactive\f[R] (Nick
+Craig\-Wood)
+.IP \[bu] 2
+Make check do \f[C]\-\-checkers\f[R] files concurrently (Nick
+Craig\-Wood)
+.IP \[bu] 2
+Retry downloads if they fail when using the \f[C]\-\-download\f[R] flag
+(Nick Craig\-Wood)
+.IP \[bu] 2
+Make it show stats by default (Nick Craig\-Wood)
+.RE
+.IP \[bu] 2
+\f[C]rclone obscure\f[R]: Allow obscure command to accept password on
+STDIN (David Ibarra)
+.IP \[bu] 2
+\f[C]rclone config\f[R]
+.RS 2
+.IP \[bu] 2
+Set RCLONE_CONFIG_DIR for use in config files and subprocesses (Nick
+Craig\-Wood)
+.IP \[bu] 2
+Reject remote names starting with a dash.
+(jtagcat)
+.RE
+.IP \[bu] 2
+\f[C]rclone cryptcheck\f[R]: Add reporting of filenames for
+same/missing/changed (Nick Craig\-Wood)
+.IP \[bu] 2
+\f[C]rclone dedupe\f[R]: Make it obey the \f[C]\-\-size\-only\f[R] flag
+for duplicate detection (Nick Craig\-Wood)
+.IP \[bu] 2
+\f[C]rclone link\f[R]: Add \f[C]\-\-expire\f[R] and \f[C]\-\-unlink\f[R]
+flags (Roman Kredentser)
+.IP \[bu] 2
+\f[C]rclone mkdir\f[R]: Warn when using mkdir on remotes which can\[aq]t
+have empty directories (Nick Craig\-Wood)
+.IP \[bu] 2
+\f[C]rclone rc\f[R]: Allow JSON parameters to simplify command line
+usage (Nick Craig\-Wood)
+.IP \[bu] 2
+\f[C]rclone serve ftp\f[R]
+.RS 2
+.IP \[bu] 2
+Don\[aq]t compile on < go1.13 after dependency update (Nick Craig\-Wood)
+.IP \[bu] 2
+Add error message if auth proxy fails (Nick Craig\-Wood)
+.IP \[bu] 2
+Use refactored goftp.io/server library for binary shrink (Nick
+Craig\-Wood)
+.RE
+.IP \[bu] 2
+\f[C]rclone serve restic\f[R]: Expose interfaces so that rclone can be
+used as a library from within restic (Jack)
+.IP \[bu] 2
+\f[C]rclone sync\f[R]: Add \f[C]\-\-track\-renames\-strategy leaf\f[R]
+(Nick Craig\-Wood)
+.IP \[bu] 2
+\f[C]rclone touch\f[R]: Add ability to set nanosecond resolution times
+(Nick Craig\-Wood)
+.IP \[bu] 2
+\f[C]rclone tree\f[R]: Remove \f[C]\-i\f[R] shorthand for
+\f[C]\-\-noindent\f[R] as it conflicts with
+\f[C]\-i\f[R]/\f[C]\-\-interactive\f[R] (Nick Craig\-Wood)
+.RE
+.IP \[bu] 2
+Bug Fixes
+.RS 2
+.IP \[bu] 2
+accounting
+.RS 2
+.IP \[bu] 2
+Fix documentation for \f[C]speed\f[R]/\f[C]speedAvg\f[R] (Nick
+Craig\-Wood)
+.IP \[bu] 2
+Fix elapsed time not show actual time since beginning (Chaitanya
+Bankanhal)
+.IP \[bu] 2
+Fix deadlock in stats printing (Nick Craig\-Wood)
+.RE
+.IP \[bu] 2
+build
+.RS 2
+.IP \[bu] 2
+Fix file handle leak in GitHub release tool (Garrett Squire)
+.RE
+.IP \[bu] 2
+\f[C]rclone check\f[R]: Fix successful retries with
+\f[C]\-\-download\f[R] counting errors (Nick Craig\-Wood)
+.IP \[bu] 2
+\f[C]rclone dedupe\f[R]: Fix logging to be easier to understand (Nick
+Craig\-Wood)
+.RE
+.IP \[bu] 2
+Mount
+.RS 2
+.IP \[bu] 2
+Warn macOS users that mount implementation is changing (Nick
+Craig\-Wood)
+.RS 2
+.IP \[bu] 2
+to test the new implementation use \f[C]rclone cmount\f[R] instead of
+\f[C]rclone mount\f[R]
+.IP \[bu] 2
+this is because the library rclone uses has dropped macOS support
+.RE
+.IP \[bu] 2
+rc interface
+.RS 2
+.IP \[bu] 2
+Add call for unmount all (Chaitanya Bankanhal)
+.IP \[bu] 2
+Make \f[C]mount/mount\f[R] remote control take vfsOpt option (Nick
+Craig\-Wood)
+.IP \[bu] 2
+Add mountOpt to \f[C]mount/mount\f[R] (Nick Craig\-Wood)
+.IP \[bu] 2
+Add VFS and Mount options to \f[C]mount/listmounts\f[R] (Nick
+Craig\-Wood)
+.RE
+.IP \[bu] 2
+Catch panics in cgofuse initialization and turn into error messages
+(Nick Craig\-Wood)
+.IP \[bu] 2
+Always supply stat information in Readdir (Nick Craig\-Wood)
+.IP \[bu] 2
+Add support for reading unknown length files using direct IO (Windows)
+(Nick Craig\-Wood)
+.IP \[bu] 2
+Fix On Windows don\[aq]t add \f[C]\-o uid/gid=\-1\f[R] if user supplies
+\f[C]\-o uid/gid\f[R].
+(Nick Craig\-Wood)
+.IP \[bu] 2
+Fix macOS losing directory contents in cmount (Nick Craig\-Wood)
+.IP \[bu] 2
+Fix volume name broken in recent refactor (Nick Craig\-Wood)
+.RE
+.IP \[bu] 2
+VFS
+.RS 2
+.IP \[bu] 2
+Implement partial reads for \f[C]\-\-vfs\-cache\-mode full\f[R] (Nick
+Craig\-Wood)
+.IP \[bu] 2
+Add \f[C]\-\-vfs\-writeback\f[R] option to delay writes back to cloud
+storage (Nick Craig\-Wood)
+.IP \[bu] 2
+Add \f[C]\-\-vfs\-read\-ahead\f[R] parameter for use with
+\f[C]\-\-vfs\-cache\-mode full\f[R] (Nick Craig\-Wood)
+.IP \[bu] 2
+Restart pending uploads on restart of the cache (Nick Craig\-Wood)
+.IP \[bu] 2
+Support synchronous cache space recovery upon ENOSPC (Leo Luan)
+.IP \[bu] 2
+Allow ReadAt and WriteAt to run concurrently with themselves (Nick
+Craig\-Wood)
+.IP \[bu] 2
+Change modtime of file before upload to current (Rob Calistri)
+.IP \[bu] 2
+Recommend \f[C]\-\-vfs\-cache\-modes writes\f[R] on backends which
+can\[aq]t stream (Nick Craig\-Wood)
+.IP \[bu] 2
+Add an optional \f[C]fs\f[R] parameter to vfs rc methods (Nick
+Craig\-Wood)
+.IP \[bu] 2
+Fix errors when using > 260 char files in the cache in Windows (Nick
+Craig\-Wood)
+.IP \[bu] 2
+Fix renaming of items while they are being uploaded (Nick Craig\-Wood)
+.IP \[bu] 2
+Fix very high load caused by slow directory listings (Nick Craig\-Wood)
+.IP \[bu] 2
+Fix renamed files not being uploaded with
+\f[C]\-\-vfs\-cache\-mode minimal\f[R] (Nick Craig\-Wood)
+.IP \[bu] 2
+Fix directory locking caused by slow directory listings (Nick
+Craig\-Wood)
+.IP \[bu] 2
+Fix saving from chrome without \f[C]\-\-vfs\-cache\-mode writes\f[R]
+(Nick Craig\-Wood)
+.RE
+.IP \[bu] 2
+Local
+.RS 2
+.IP \[bu] 2
+Add \f[C]\-\-local\-no\-updated\f[R] to provide a consistent view of
+changing objects (Nick Craig\-Wood)
+.IP \[bu] 2
+Add \f[C]\-\-local\-no\-set\-modtime\f[R] option to prevent modtime
+changes (tyhuber1)
+.IP \[bu] 2
+Fix race conditions updating and reading Object metadata (Nick
+Craig\-Wood)
+.RE
+.IP \[bu] 2
+Cache
+.RS 2
+.IP \[bu] 2
+Make any created backends be cached to fix rc problems (Nick
+Craig\-Wood)
+.IP \[bu] 2
+Fix dedupe on caches wrapping drives (Nick Craig\-Wood)
+.RE
+.IP \[bu] 2
+Crypt
+.RS 2
+.IP \[bu] 2
+Add \f[C]\-\-crypt\-server\-side\-across\-configs\f[R] flag (Nick
+Craig\-Wood)
+.IP \[bu] 2
+Make any created backends be cached to fix rc problems (Nick
+Craig\-Wood)
+.RE
+.IP \[bu] 2
+Alias
+.RS 2
+.IP \[bu] 2
+Make any created backends be cached to fix rc problems (Nick
+Craig\-Wood)
+.RE
+.IP \[bu] 2
+Azure Blob
+.RS 2
+.IP \[bu] 2
+Don\[aq]t compile on < go1.13 after dependency update (Nick Craig\-Wood)
+.RE
+.IP \[bu] 2
+B2
+.RS 2
+.IP \[bu] 2
+Implement server side copy for files > 5GB (Nick Craig\-Wood)
+.IP \[bu] 2
+Cancel in progress multipart uploads and copies on rclone exit (Nick
+Craig\-Wood)
+.IP \[bu] 2
+Note that b2\[aq]s encoding now allows \ but rclone\[aq]s hasn\[aq]t
+changed (Nick Craig\-Wood)
+.IP \[bu] 2
+Fix transfers when using download_url (Nick Craig\-Wood)
+.RE
+.IP \[bu] 2
+Box
+.RS 2
+.IP \[bu] 2
+Implement rclone cleanup (buengese)
+.IP \[bu] 2
+Cancel in progress multipart uploads and copies on rclone exit (Nick
+Craig\-Wood)
+.IP \[bu] 2
+Allow authentication with access token (David)
+.RE
+.IP \[bu] 2
+Chunker
+.RS 2
+.IP \[bu] 2
+Make any created backends be cached to fix rc problems (Nick
+Craig\-Wood)
+.RE
+.IP \[bu] 2
+Drive
+.RS 2
+.IP \[bu] 2
+Add \f[C]rclone backend drives\f[R] to list shared drives (teamdrives)
+(Nick Craig\-Wood)
+.IP \[bu] 2
+Implement \f[C]rclone backend untrash\f[R] (Nick Craig\-Wood)
+.IP \[bu] 2
+Work around drive bug which didn\[aq]t set modtime of copied docs (Nick
+Craig\-Wood)
+.IP \[bu] 2
+Added \f[C]\-\-drive\-starred\-only\f[R] to only show starred files (Jay
+McEntire)
+.IP \[bu] 2
+Deprecate \f[C]\-\-drive\-alternate\-export\f[R] as it is no longer
+needed (themylogin)
+.IP \[bu] 2
+Fix duplication of Google docs on server side copy (Nick Craig\-Wood)
+.IP \[bu] 2
+Fix \[dq]panic: send on closed channel\[dq] when recycling dir entries
+(Nick Craig\-Wood)
+.RE
+.IP \[bu] 2
+Dropbox
+.RS 2
+.IP \[bu] 2
+Add copyright detector info in limitations section in the docs (Alex
+Guerrero)
+.IP \[bu] 2
+Fix \f[C]rclone link\f[R] by removing expires parameter (Nick
+Craig\-Wood)
+.RE
+.IP \[bu] 2
+Fichier
+.RS 2
+.IP \[bu] 2
+Detect Flood detected: IP Locked error and sleep for 30s (Nick
+Craig\-Wood)
+.RE
+.IP \[bu] 2
+FTP
+.RS 2
+.IP \[bu] 2
+Add explicit TLS support (Heiko Bornholdt)
+.IP \[bu] 2
+Add support for \f[C]\-\-dump bodies\f[R] and \f[C]\-\-dump auth\f[R]
+for debugging (Nick Craig\-Wood)
+.IP \[bu] 2
+Fix interoperation with pure\-ftpd (Nick Craig\-Wood)
+.RE
+.IP \[bu] 2
+Google Cloud Storage
+.RS 2
+.IP \[bu] 2
+Add support for anonymous access (Kai L\[:u]ke)
+.RE
+.IP \[bu] 2
+Jottacloud
+.RS 2
+.IP \[bu] 2
+Bring back legacy authentification for use with whitelabel versions
+(buengese)
+.IP \[bu] 2
+Switch to new api root \- also implement a very ugly workaround for the
+DirMove failures (buengese)
+.RE
+.IP \[bu] 2
+Onedrive
+.RS 2
+.IP \[bu] 2
+Rework cancel of multipart uploads on rclone exit (Nick Craig\-Wood)
+.IP \[bu] 2
+Implement rclone cleanup (Nick Craig\-Wood)
+.IP \[bu] 2
+Add \f[C]\-\-onedrive\-no\-versions\f[R] flag to remove old versions
+(Nick Craig\-Wood)
+.RE
+.IP \[bu] 2
+Pcloud
+.RS 2
+.IP \[bu] 2
+Implement \f[C]rclone link\f[R] for public link creation (buengese)
+.RE
+.IP \[bu] 2
+Qingstor
+.RS 2
+.IP \[bu] 2
+Cancel in progress multipart uploads on rclone exit (Nick Craig\-Wood)
+.RE
+.IP \[bu] 2
+S3
+.RS 2
+.IP \[bu] 2
+Preserve metadata when doing multipart copy (Nick Craig\-Wood)
+.IP \[bu] 2
+Cancel in progress multipart uploads and copies on rclone exit (Nick
+Craig\-Wood)
+.IP \[bu] 2
+Add \f[C]rclone link\f[R] for public link sharing (Roman Kredentser)
+.IP \[bu] 2
+Add \f[C]rclone backend restore\f[R] command to restore objects from
+GLACIER (Nick Craig\-Wood)
+.IP \[bu] 2
+Add \f[C]rclone cleanup\f[R] and \f[C]rclone backend cleanup\f[R] to
+clean unfinished multipart uploads (Nick Craig\-Wood)
+.IP \[bu] 2
+Add \f[C]rclone backend list\-multipart\-uploads\f[R] to list unfinished
+multipart uploads (Nick Craig\-Wood)
+.IP \[bu] 2
+Add \f[C]\-\-s3\-max\-upload\-parts\f[R] support (Kamil
+Trzci\[u0144]ski)
+.IP \[bu] 2
+Add \f[C]\-\-s3\-no\-check\-bucket\f[R] for minimising rclone
+transactions and perms (Nick Craig\-Wood)
+.IP \[bu] 2
+Add \f[C]\-\-s3\-profile\f[R] and
+\f[C]\-\-s3\-shared\-credentials\-file\f[R] options (Nick Craig\-Wood)
+.IP \[bu] 2
+Use regional s3 us\-east\-1 endpoint (David)
+.IP \[bu] 2
+Add Scaleway provider (Vincent Feltz)
+.IP \[bu] 2
+Update IBM COS endpoints (Egor Margineanu)
+.IP \[bu] 2
+Reduce the default \f[C]\-\-s3\-copy\-cutoff\f[R] to < 5GB for Backblaze
+S3 compatibility (Nick Craig\-Wood)
+.IP \[bu] 2
+Fix detection of bucket existing (Nick Craig\-Wood)
+.RE
+.IP \[bu] 2
+SFTP
+.RS 2
+.IP \[bu] 2
+Use the absolute path instead of the relative path for listing for
+improved compatibility (Nick Craig\-Wood)
+.IP \[bu] 2
+Add \f[C]\-\-sftp\-subsystem\f[R] and
+\f[C]\-\-sftp\-server\-command\f[R] options (aus)
+.RE
+.IP \[bu] 2
+Swift
+.RS 2
+.IP \[bu] 2
+Fix dangling large objects breaking the listing (Nick Craig\-Wood)
+.IP \[bu] 2
+Fix purge not deleting directory markers (Nick Craig\-Wood)
+.IP \[bu] 2
+Fix update multipart object removing all of its own parts (Nick
+Craig\-Wood)
+.IP \[bu] 2
+Fix missing hash from object returned from upload (Nick Craig\-Wood)
+.RE
+.IP \[bu] 2
+Tardigrade
+.RS 2
+.IP \[bu] 2
+Upgrade to uplink v1.2.0 (Kaloyan Raev)
+.RE
+.IP \[bu] 2
+Union
+.RS 2
+.IP \[bu] 2
+Fix writing with the all policy (Nick Craig\-Wood)
+.RE
+.IP \[bu] 2
+WebDAV
+.RS 2
+.IP \[bu] 2
+Fix directory creation with 4shared (Nick Craig\-Wood)
+.RE
+.SS v1.52.3 \- 2020\-08\-07
+.PP
+See commits (https://github.com/rclone/rclone/compare/v1.52.2...v1.52.3)
+.IP \[bu] 2
+Bug Fixes
+.RS 2
+.IP \[bu] 2
+docs
+.RS 2
+.IP \[bu] 2
+Disable smart typography (eg en\-dash) in MANUAL.* and man page (Nick
+Craig\-Wood)
+.IP \[bu] 2
+Update install.md to reflect minimum Go version (Evan Harris)
+.IP \[bu] 2
+Update install from source instructions (Nick Craig\-Wood)
+.IP \[bu] 2
+make_manual: Support SOURCE_DATE_EPOCH (Morten Linderud)
+.RE
+.IP \[bu] 2
+log: Fix \-\-use\-json\-log going to stderr not \-\-log\-file on Windows
+(Nick Craig\-Wood)
+.IP \[bu] 2
+serve dlna: Fix file list on Samsung Series 6+ TVs (Matteo Pietro Dazzi)
+.IP \[bu] 2
+sync: Fix deadlock with \-\-track\-renames\-strategy modtime (Nick
+Craig\-Wood)
+.RE
+.IP \[bu] 2
+Cache
+.RS 2
+.IP \[bu] 2
+Fix moveto/copyto remote:file remote:file2 (Nick Craig\-Wood)
+.RE
+.IP \[bu] 2
+Drive
+.RS 2
+.IP \[bu] 2
+Stop using root_folder_id as a cache (Nick Craig\-Wood)
+.IP \[bu] 2
+Make dangling shortcuts appear in listings (Nick Craig\-Wood)
+.IP \[bu] 2
+Drop \[dq]Disabling ListR\[dq] messages down to debug (Nick Craig\-Wood)
+.IP \[bu] 2
+Workaround and policy for Google Drive API (Dmitry Ustalov)
+.RE
+.IP \[bu] 2
+FTP
+.RS 2
+.IP \[bu] 2
+Add note to docs about home vs root directory selection (Nick
+Craig\-Wood)
+.RE
+.IP \[bu] 2
+Onedrive
+.RS 2
+.IP \[bu] 2
+Fix reverting to Copy when Move would have worked (Nick Craig\-Wood)
+.IP \[bu] 2
+Avoid comma rendered in URL in onedrive.md (Kevin)
+.RE
+.IP \[bu] 2
+Pcloud
+.RS 2
+.IP \[bu] 2
+Fix oauth on European region \[dq]eapi.pcloud.com\[dq] (Nick
+Craig\-Wood)
+.RE
+.IP \[bu] 2
+S3
+.RS 2
+.IP \[bu] 2
+Fix bucket Region auto detection when Region unset in config (Nick
+Craig\-Wood)
+.RE
+.SS v1.52.2 \- 2020\-06\-24
+.PP
+See commits (https://github.com/rclone/rclone/compare/v1.52.1...v1.52.2)
+.IP \[bu] 2
+Bug Fixes
+.RS 2
+.IP \[bu] 2
+build
+.RS 2
+.IP \[bu] 2
+Fix docker release build action (Nick Craig\-Wood)
+.IP \[bu] 2
+Fix custom timezone in Docker image (NoLooseEnds)
+.RE
+.IP \[bu] 2
+check: Fix misleading message which printed errors instead of
+differences (Nick Craig\-Wood)
+.IP \[bu] 2
+errors: Add WSAECONNREFUSED and more to the list of retriable Windows
+errors (Nick Craig\-Wood)
+.IP \[bu] 2
+rcd: Fix incorrect prometheus metrics (Gary Kim)
+.IP \[bu] 2
+serve restic: Fix flags so they use environment variables (Nick
+Craig\-Wood)
+.IP \[bu] 2
+serve webdav: Fix flags so they use environment variables (Nick
+Craig\-Wood)
+.IP \[bu] 2
+sync: Fix \-\-track\-renames\-strategy modtime (Nick Craig\-Wood)
+.RE
+.IP \[bu] 2
+Drive
+.RS 2
+.IP \[bu] 2
+Fix not being able to delete a directory with a trashed shortcut (Nick
+Craig\-Wood)
+.IP \[bu] 2
+Fix creating a directory inside a shortcut (Nick Craig\-Wood)
+.IP \[bu] 2
+Fix \-\-drive\-impersonate with cached root_folder_id (Nick Craig\-Wood)
+.RE
+.IP \[bu] 2
+SFTP
+.RS 2
+.IP \[bu] 2
+Fix SSH key PEM loading (Zac Rubin)
+.RE
+.IP \[bu] 2
+Swift
+.RS 2
+.IP \[bu] 2
+Speed up deletes by not retrying segment container deletes (Nick
+Craig\-Wood)
+.RE
+.IP \[bu] 2
+Tardigrade
+.RS 2
+.IP \[bu] 2
+Upgrade to uplink v1.1.1 (Caleb Case)
+.RE
+.IP \[bu] 2
+WebDAV
+.RS 2
+.IP \[bu] 2
+Fix free/used display for rclone about/df for certain backends (Nick
+Craig\-Wood)
+.RE
+.SS v1.52.1 \- 2020\-06\-10
+.PP
+See commits (https://github.com/rclone/rclone/compare/v1.52.0...v1.52.1)
+.IP \[bu] 2
+Bug Fixes
+.RS 2
+.IP \[bu] 2
+lib/file: Fix SetSparse on Windows 7 which fixes downloads of files >
+250MB (Nick Craig\-Wood)
+.IP \[bu] 2
+build
+.RS 2
+.IP \[bu] 2
+Update go.mod to go1.14 to enable \-mod=vendor build (Nick Craig\-Wood)
+.IP \[bu] 2
+Remove quicktest from Dockerfile (Nick Craig\-Wood)
+.IP \[bu] 2
+Build Docker images with GitHub actions (Matteo Pietro Dazzi)
+.IP \[bu] 2
+Update Docker build workflows (Nick Craig\-Wood)
+.IP \[bu] 2
+Set user_allow_other in /etc/fuse.conf in the Docker image (Nick
+Craig\-Wood)
+.IP \[bu] 2
+Fix xgo build after go1.14 go.mod update (Nick Craig\-Wood)
+.RE
+.IP \[bu] 2
+docs
+.RS 2
+.IP \[bu] 2
+Add link to source and modified time to footer of every page (Nick
+Craig\-Wood)
+.IP \[bu] 2
+Remove manually set dates and use git dates instead (Nick Craig\-Wood)
+.IP \[bu] 2
+Minor tense, punctuation, brevity and positivity changes for the home
+page (edwardxml)
+.IP \[bu] 2
+Remove leading slash in page reference in footer when present (Nick
+Craig\-Wood)
+.IP \[bu] 2
+Note commands which need obscured input in the docs (Nick Craig\-Wood)
+.IP \[bu] 2
+obscure: Write more help as we are referencing it elsewhere (Nick
+Craig\-Wood)
+.RE
+.RE
+.IP \[bu] 2
+VFS
+.RS 2
+.IP \[bu] 2
+Fix OS vs Unix path confusion \- fixes ChangeNotify on Windows (Nick
+Craig\-Wood)
+.RE
+.IP \[bu] 2
+Drive
+.RS 2
+.IP \[bu] 2
+Fix missing items when listing using \-\-fast\-list / ListR (Nick
+Craig\-Wood)
+.RE
+.IP \[bu] 2
+Putio
+.RS 2
+.IP \[bu] 2
+Fix panic on Object.Open (Cenk Alti)
+.RE
+.IP \[bu] 2
+S3
+.RS 2
+.IP \[bu] 2
+Fix upload of single files into buckets without create permission (Nick
+Craig\-Wood)
+.IP \[bu] 2
+Fix \-\-header\-upload (Nick Craig\-Wood)
+.RE
+.IP \[bu] 2
+Tardigrade
+.RS 2
+.IP \[bu] 2
+Fix listing bug by upgrading to v1.0.7
+.IP \[bu] 2
+Set UserAgent to rclone (Caleb Case)
+.RE
 .SS v1.52.0 \- 2020\-05\-27
 .PP
 Special thanks to Martin Michlmayr for proof reading and correcting all
@@ -32324,7 +30459,7 @@ Bug Fixes
 accounting
 .RS 2
 .IP \[bu] 2
-Restore \[lq]Max number of stats groups reached\[rq] log line
+Restore \[dq]Max number of stats groups reached\[dq] log line
 (Micha\[/l] Matczuk)
 .IP \[bu] 2
 Correct exitcode on Transfer Limit Exceeded flag.
@@ -32335,7 +30470,7 @@ Reset bytes read during copy retry (Ankur Gupta)
 Fix race clearing stats (Nick Craig\-Wood)
 .RE
 .IP \[bu] 2
-copy: Only create empty directories when they don\[cq]t exist on the
+copy: Only create empty directories when they don\[aq]t exist on the
 remote (Ishuah Kariuki)
 .IP \[bu] 2
 dedupe: Stop dedupe deleting files with identical IDs (Nick Craig\-Wood)
@@ -32373,7 +30508,7 @@ Disable duplicate log (ElonH)
 serve dlna
 .RS 2
 .IP \[bu] 2
-Cds: don\[cq]t specify childCount at all when unknown (Dan Walters)
+Cds: don\[aq]t specify childCount at all when unknown (Dan Walters)
 .IP \[bu] 2
 Cds: use modification time as date in dlna metadata (Dan Walters)
 .RE
@@ -32384,10 +30519,10 @@ Craig\-Wood)
 sync
 .RS 2
 .IP \[bu] 2
-Fix incorrect \[lq]nothing to transfer\[rq] message using
+Fix incorrect \[dq]nothing to transfer\[dq] message using
 \f[C]\-\-delete\-before\f[R] (Nick Craig\-Wood)
 .IP \[bu] 2
-Only create empty directories when they don\[cq]t exist on the remote
+Only create empty directories when they don\[aq]t exist on the remote
 (Ishuah Kariuki)
 .RE
 .RE
@@ -32475,7 +30610,7 @@ files (Nick Craig\-Wood)
 Implement \f[C]rclone backend noop\f[R] for testing purposes (Nick
 Craig\-Wood)
 .IP \[bu] 2
-Fix \[lq]file not found\[rq] errors on post transfer Hash calculation
+Fix \[dq]file not found\[dq] errors on post transfer Hash calculation
 (Nick Craig\-Wood)
 .RE
 .IP \[bu] 2
@@ -32585,7 +30720,7 @@ Extend \f[C]\-\-drive\-stop\-on\-upload\-limit\f[R] to respond to
 \f[C]teamDriveFileLimitExceeded\f[R].
 (harry)
 .IP \[bu] 2
-Don\[cq]t delete files with multiple parents to avoid data loss (Nick
+Don\[aq]t delete files with multiple parents to avoid data loss (Nick
 Craig\-Wood)
 .IP \[bu] 2
 Server side copy docs use default description if empty (Nick
@@ -32645,9 +30780,9 @@ Add support for \f[C]\-\-header\-upload\f[R] and
 .IP \[bu] 2
 Create feature/favorites directory (Brandon Philips)
 .IP \[bu] 2
-Fix \[lq]concurrent map write\[rq] error (Nick Craig\-Wood)
+Fix \[dq]concurrent map write\[dq] error (Nick Craig\-Wood)
 .IP \[bu] 2
-Don\[cq]t put an image in error message (Nick Craig\-Wood)
+Don\[aq]t put an image in error message (Nick Craig\-Wood)
 .RE
 .IP \[bu] 2
 HTTP
@@ -32715,7 +30850,7 @@ Patra)
 Add support for \f[C]\-\-header\-upload\f[R] and
 \f[C]\-\-header\-download\f[R] (Tim Gallant)
 .IP \[bu] 2
-Fix initial config \[lq]Auth state doesn\[cq]t match\[rq] message (Nick
+Fix initial config \[dq]Auth state doesn\[aq]t match\[dq] message (Nick
 Craig\-Wood)
 .RE
 .IP \[bu] 2
@@ -32781,7 +30916,7 @@ Replace deprecated \f[C]session.New()\f[R] with
 Use the provided size parameter when allocating a new memory pool
 (Joachim Brandon LeBlanc)
 .IP \[bu] 2
-Use rclone\[cq]s low level retries instead of AWS SDK to fix listing
+Use rclone\[aq]s low level retries instead of AWS SDK to fix listing
 retries (Nick Craig\-Wood)
 .IP \[bu] 2
 Ignore directory markers at the root also (Nick Craig\-Wood)
@@ -32792,7 +30927,7 @@ Do not resize buf on put to memBuf (Micha\[/l] Matczuk)
 .IP \[bu] 2
 Improve docs for \f[C]\-\-s3\-disable\-checksum\f[R] (Nick Craig\-Wood)
 .IP \[bu] 2
-Don\[cq]t leak memory or tokens in edge cases for multipart upload (Nick
+Don\[aq]t leak memory or tokens in edge cases for multipart upload (Nick
 Craig\-Wood)
 .RE
 .IP \[bu] 2
@@ -32900,7 +31035,7 @@ Craig\-Wood)
 accounting
 .RS 2
 .IP \[bu] 2
-Don\[cq]t show entries in both transferring and checking (Nick
+Don\[aq]t show entries in both transferring and checking (Nick
 Craig\-Wood)
 .IP \[bu] 2
 Add option to delete stats (Aleksandar Jankovic)
@@ -33018,12 +31153,12 @@ vendor
 .IP \[bu] 2
 Update bazil.org/fuse to fix FreeBSD 12.1 (Nick Craig\-Wood)
 .IP \[bu] 2
-Update github.com/t3rm1n4l/go\-mega to fix mega \[lq]illegal base64 data
-at input byte 22\[rq] (Nick Craig\-Wood)
+Update github.com/t3rm1n4l/go\-mega to fix mega \[dq]illegal base64 data
+at input byte 22\[dq] (Nick Craig\-Wood)
 .IP \[bu] 2
 Update termbox\-go to fix ncdu command on FreeBSD (Kuang\-che Wu)
 .IP \[bu] 2
-Update t3rm1n4l/go\-mega \- fixes mega: couldn\[cq]t login: crypto/aes:
+Update t3rm1n4l/go\-mega \- fixes mega: couldn\[aq]t login: crypto/aes:
 invalid key size 0 (Nick Craig\-Wood)
 .RE
 .RE
@@ -33038,7 +31173,7 @@ Replace use of WriteAt with Write for cache mode >= writes and O_APPEND
 .IP \[bu] 2
 Make sure we call unmount when exiting (Nick Craig\-Wood)
 .IP \[bu] 2
-Don\[cq]t build on go1.10 as bazil/fuse no longer supports it (Nick
+Don\[aq]t build on go1.10 as bazil/fuse no longer supports it (Nick
 Craig\-Wood)
 .IP \[bu] 2
 When setting dates discard out of range dates (Nick Craig\-Wood)
@@ -33059,7 +31194,7 @@ Fix edge cases when reading ModTime from file (Nick Craig\-Wood)
 Make sure existing files opened for write show correct size (Nick
 Craig\-Wood)
 .IP \[bu] 2
-Don\[cq]t cache the path in RW file objects to fix renaming (Nick
+Don\[aq]t cache the path in RW file objects to fix renaming (Nick
 Craig\-Wood)
 .IP \[bu] 2
 Fix rename of open files when using the VFS cache (Nick Craig\-Wood)
@@ -33159,7 +31294,7 @@ Onedrive
 .IP \[bu] 2
 Add Sites.Read.All permission (Benjamin Richter)
 .IP \[bu] 2
-Add support \[lq]Retry\-After\[rq] header (Motonori IWAMURO)
+Add support \[dq]Retry\-After\[dq] header (Motonori IWAMURO)
 .RE
 .IP \[bu] 2
 Opendrive
@@ -33206,8 +31341,8 @@ files (Nick Craig\-Wood)
 .IP \[bu] 2
 Retry Creation of Connection (Sebastian Brandt)
 .IP \[bu] 2
-Fix \[lq]failed to parse private key file: ssh: not an encrypted
-key\[rq] error (Nick Craig\-Wood)
+Fix \[dq]failed to parse private key file: ssh: not an encrypted
+key\[dq] error (Nick Craig\-Wood)
 .IP \[bu] 2
 Open files for update write only to fix AWS SFTP interop (Nick
 Craig\-Wood)
@@ -33230,7 +31365,7 @@ WebDAV
 .IP \[bu] 2
 Make nextcloud only upload SHA1 checksums (Nick Craig\-Wood)
 .IP \[bu] 2
-Fix case of \[lq]Bearer\[rq] in Authorization: header to agree with RFC
+Fix case of \[dq]Bearer\[dq] in Authorization: header to agree with RFC
 (Nick Craig\-Wood)
 .IP \[bu] 2
 Add Referer header to fix problems with WAFs (Nick Craig\-Wood)
@@ -33249,7 +31384,7 @@ Drive
 Fix listing of the root directory with drive.files scope (Nick
 Craig\-Wood)
 .IP \[bu] 2
-Fix \[en]drive\-root\-folder\-id with team/shared drives (Nick
+Fix \-\-drive\-root\-folder\-id with team/shared drives (Nick
 Craig\-Wood)
 .RE
 .SS v1.50.1 \- 2019\-11\-02
@@ -33263,7 +31398,7 @@ hash: Fix accidentally changed hash names for \f[C]DropboxHash\f[R] and
 fshttp: Fix error reporting on tpslimit token bucket errors (Nick
 Craig\-Wood)
 .IP \[bu] 2
-fshttp: Don\[cq]t print token bucket errors on context cancelled (Nick
+fshttp: Don\[aq]t print token bucket errors on context cancelled (Nick
 Craig\-Wood)
 .RE
 .IP \[bu] 2
@@ -33376,7 +31511,7 @@ sync
 .RS 2
 .IP \[bu] 2
 Make \f[C]\-\-update\f[R]/\f[C]\-u\f[R] not transfer files that
-haven\[cq]t changed (Nick Craig\-Wood)
+haven\[aq]t changed (Nick Craig\-Wood)
 .IP \[bu] 2
 Free objects after they come out of the transfer pipe to save memory
 (Nick Craig\-Wood)
@@ -33390,11 +31525,11 @@ operations
 .IP \[bu] 2
 Fix accounting for server side copies (Nick Craig\-Wood)
 .IP \[bu] 2
-Display `All duplicates removed' only if dedupe successful (Sezal
-Agrawal)
+Display \[aq]All duplicates removed\[aq] only if dedupe successful
+(Sezal Agrawal)
 .IP \[bu] 2
-Display `Deleted X extra copies' only if dedupe successful (Sezal
-Agrawal)
+Display \[aq]Deleted X extra copies\[aq] only if dedupe successful
+(Sezal Agrawal)
 .RE
 .IP \[bu] 2
 accounting
@@ -33419,13 +31554,13 @@ cmd
 Fix environment variables not setting command line flags (Nick
 Craig\-Wood)
 .IP \[bu] 2
-Make autocomplete compatible with bash\[cq]s posix mode for macOS (Danil
+Make autocomplete compatible with bash\[aq]s posix mode for macOS (Danil
 Semelenov)
 .IP \[bu] 2
 Make \f[C]\-\-progress\f[R] work in git bash on Windows (Nick
 Craig\-Wood)
 .IP \[bu] 2
-Fix `compopt: command not found' on autocomplete on macOS (Danil
+Fix \[aq]compopt: command not found\[aq] on autocomplete on macOS (Danil
 Semelenov)
 .RE
 .IP \[bu] 2
@@ -33437,7 +31572,7 @@ Craig\-Wood)
 .IP \[bu] 2
 Check config names more carefully and report errors (Nick Craig\-Wood)
 .IP \[bu] 2
-Remove error: can\[cq]t use \f[C]\-\-size\-only\f[R] and
+Remove error: can\[aq]t use \f[C]\-\-size\-only\f[R] and
 \f[C]\-\-ignore\-size\f[R] together.
 (Nick Craig\-Wood)
 .RE
@@ -33458,10 +31593,10 @@ Skip tests on <= 2 CPUs to avoid lockup (Nick Craig\-Wood)
 .IP \[bu] 2
 Fix panic on File.Open (Nick Craig\-Wood)
 .IP \[bu] 2
-Fix \[lq]mount_fusefs: \-o timeout=: option not supported\[rq] on
+Fix \[dq]mount_fusefs: \-o timeout=: option not supported\[dq] on
 FreeBSD (Nick Craig\-Wood)
 .IP \[bu] 2
-Don\[cq]t pass huge filenames (>4k) to FUSE as it can\[cq]t cope (Nick
+Don\[aq]t pass huge filenames (>4k) to FUSE as it can\[aq]t cope (Nick
 Craig\-Wood)
 .RE
 .IP \[bu] 2
@@ -33636,7 +31771,7 @@ accounting
 .IP \[bu] 2
 Fix total duration calculation (Aleksandar Jankovic)
 .IP \[bu] 2
-Fix \[lq]file already closed\[rq] on transfer retries (Nick Craig\-Wood)
+Fix \[dq]file already closed\[dq] on transfer retries (Nick Craig\-Wood)
 .RE
 .RE
 .SS v1.49.2 \- 2019\-09\-08
@@ -33748,7 +31883,7 @@ operations:
 .IP \[bu] 2
 Run hashing operations in parallel (Nick Craig\-Wood)
 .IP \[bu] 2
-Don\[cq]t calculate checksums when using \f[C]\-\-ignore\-checksum\f[R]
+Don\[aq]t calculate checksums when using \f[C]\-\-ignore\-checksum\f[R]
 (Nick Craig\-Wood)
 .IP \[bu] 2
 Check transfer hashes when using \f[C]\-\-size\-only\f[R] mode (Nick
@@ -33776,7 +31911,7 @@ sharing (CORS) in the rcd.
 Add anchor tags to the docs so links are consistent (Nick Craig\-Wood)
 .IP \[bu] 2
 Remove _async key from input parameters after parsing so later
-operations won\[cq]t get confused (buengese)
+operations won\[aq]t get confused (buengese)
 .IP \[bu] 2
 Add call to clear stats (Aleksandar Jankovic)
 .RE
@@ -33834,7 +31969,7 @@ Support \f[C]\-\-auth\-proxy\f[R] (Nick Craig\-Wood)
 Bug Fixes
 .RS 2
 .IP \[bu] 2
-Make \[lq]bad record MAC\[rq] a retriable error (Nick Craig\-Wood)
+Make \[dq]bad record MAC\[dq] a retriable error (Nick Craig\-Wood)
 .IP \[bu] 2
 copyurl: Fix copying files that return HTTP errors (Nick Craig\-Wood)
 .IP \[bu] 2
@@ -33889,7 +32024,7 @@ Add \f[C]\-\-local\-case\-sensitive\f[R] and
 Avoid polluting page cache when uploading local files to remote backends
 (Micha\[/l] Matczuk)
 .IP \[bu] 2
-Don\[cq]t calculate any hashes by default (Nick Craig\-Wood)
+Don\[aq]t calculate any hashes by default (Nick Craig\-Wood)
 .IP \[bu] 2
 Fadvise run syscall on a dedicated go routine (Micha\[/l] Matczuk)
 .RE
@@ -34124,7 +32259,7 @@ Bug Fixes
 Make move and copy individual files obey \f[C]\-\-backup\-dir\f[R] (Nick
 Craig\-Wood)
 .IP \[bu] 2
-If \f[C]\-\-ignore\-checksum\f[R] is in effect, don\[cq]t calculate
+If \f[C]\-\-ignore\-checksum\f[R] is in effect, don\[aq]t calculate
 checksum (Nick Craig\-Wood)
 .IP \[bu] 2
 moveto: Fix case\-insensitive same remote move (Gary Kim)
@@ -34237,7 +32372,7 @@ S3
 Support S3 Accelerated endpoints with
 \f[C]\-\-s3\-use\-accelerate\-endpoint\f[R] (Nick Craig\-Wood)
 .IP \[bu] 2
-Add config info for Wasabi\[cq]s EU Central endpoint (Robert Marko)
+Add config info for Wasabi\[aq]s EU Central endpoint (Robert Marko)
 .IP \[bu] 2
 Make SetModTime work for GLACIER while syncing (Philip Harvey)
 .RE
@@ -34278,7 +32413,7 @@ this means rclone will restart transfers if the source has an error
 this is most useful for downloads or cloud to cloud copies
 .RE
 .IP \[bu] 2
-Use \f[C]\-\-fast\-list\f[R] for listing operations where it won\[cq]t
+Use \f[C]\-\-fast\-list\f[R] for listing operations where it won\[aq]t
 use more memory (Nick Craig\-Wood)
 .RS 2
 .IP \[bu] 2
@@ -34326,8 +32461,8 @@ Update to use go1.12.x for the build (Nick Craig\-Wood)
 serve dlna: Add connection manager service description to improve
 compatibility (Dan Walters)
 .IP \[bu] 2
-lsf: Add `e' format to show encrypted names and `o' for original IDs
-(Nick Craig\-Wood)
+lsf: Add \[aq]e\[aq] format to show encrypted names and \[aq]o\[aq] for
+original IDs (Nick Craig\-Wood)
 .IP \[bu] 2
 lsjson: Added \f[C]\-\-files\-only\f[R] and \f[C]\-\-dirs\-only\f[R]
 flags (calistri)
@@ -34380,7 +32515,7 @@ Azure Blob
 .RS 2
 .IP \[bu] 2
 Enable MD5 checksums when uploading files bigger than the
-\[lq]Cutoff\[rq] (Dr.Rx)
+\[dq]Cutoff\[dq] (Dr.Rx)
 .IP \[bu] 2
 Fix SAS URL support (Nick Craig\-Wood)
 .RE
@@ -34468,7 +32603,7 @@ Return errors instead of panic for invalid uploads (Fabian M\[:o]ller)
 S3
 .RS 2
 .IP \[bu] 2
-Add support for \[lq]Glacier Deep Archive\[rq] storage class (Manu)
+Add support for \[dq]Glacier Deep Archive\[dq] storage class (Manu)
 .IP \[bu] 2
 Update Dreamhost endpoint (Nick Craig\-Wood)
 .IP \[bu] 2
@@ -34587,7 +32722,7 @@ copyurl: Fix checking of \f[C]\-\-dry\-run\f[R] (Denis Skovpen)
 Mount
 .RS 2
 .IP \[bu] 2
-Check that mountpoint and local directory to mount don\[cq]t overlap
+Check that mountpoint and local directory to mount don\[aq]t overlap
 (Nick Craig\-Wood)
 .IP \[bu] 2
 Fix mount size under 32 bit Windows (Nick Craig\-Wood)
@@ -34614,7 +32749,7 @@ Fix deadlock on concurrent operations on a directory (Nick Craig\-Wood)
 Fix deadlock between RWFileHandle.close and File.Remove (Nick
 Craig\-Wood)
 .IP \[bu] 2
-Fix renaming/deleting open files with cache mode \[lq]writes\[rq] under
+Fix renaming/deleting open files with cache mode \[dq]writes\[dq] under
 Windows (Nick Craig\-Wood)
 .IP \[bu] 2
 Fix panic on rename with \f[C]\-\-dry\-run\f[R] set (Nick Craig\-Wood)
@@ -34735,7 +32870,7 @@ HTTP
 .RS 2
 .IP \[bu] 2
 Add an example with username and password which is supported but
-wasn\[cq]t documented (Nick Craig\-Wood)
+wasn\[aq]t documented (Nick Craig\-Wood)
 .IP \[bu] 2
 Fix backend with \f[C]\-\-files\-from\f[R] and non\-existent files (Nick
 Craig\-Wood)
@@ -34753,7 +32888,7 @@ Jottacloud
 .IP \[bu] 2
 Resume and deduplication support (Oliver Heyme)
 .IP \[bu] 2
-Use token auth for all API requests Don\[cq]t store password anymore
+Use token auth for all API requests Don\[aq]t store password anymore
 (Sebastian B\[:u]nger)
 .IP \[bu] 2
 Add support for 2\-factor authentication (Sebastian B\[:u]nger)
@@ -34774,7 +32909,7 @@ Add new error codes for better error reporting (Nick Craig\-Wood)
 Onedrive
 .RS 2
 .IP \[bu] 2
-Fix broken support for \[lq]shared with me\[rq] folders (Alex Chen)
+Fix broken support for \[dq]shared with me\[dq] folders (Alex Chen)
 .IP \[bu] 2
 Fix root ID not normalised (Cnly)
 .IP \[bu] 2
@@ -34923,7 +33058,7 @@ sync/copy/move
 .RS 2
 .IP \[bu] 2
 Make \f[C]\-\-files\-from\f[R] only read the objects specified and
-don\[cq]t scan directories (Nick Craig\-Wood)
+don\[aq]t scan directories (Nick Craig\-Wood)
 .RS 2
 .IP \[bu] 2
 This is a huge speed improvement for destinations with lots of files
@@ -34932,7 +33067,7 @@ This is a huge speed improvement for destinations with lots of files
 .IP \[bu] 2
 filter: Add \f[C]\-\-ignore\-case\f[R] flag (Nick Craig\-Wood)
 .IP \[bu] 2
-ncdu: Add remove function (`d' key) (Henning Surmeier)
+ncdu: Add remove function (\[aq]d\[aq] key) (Henning Surmeier)
 .IP \[bu] 2
 rc command
 .RS 2
@@ -34967,7 +33102,7 @@ Craig\-Wood)
 .IP \[bu] 2
 dedupe: Check for existing filename before renaming a dupe file (ssaqua)
 .IP \[bu] 2
-move: Don\[cq]t create directories with \f[C]\-\-dry\-run\f[R] (Nick
+move: Don\[aq]t create directories with \f[C]\-\-dry\-run\f[R] (Nick
 Craig\-Wood)
 .IP \[bu] 2
 operations: Fix Purge and Rmdirs when dir is not the root (Nick
@@ -34989,7 +33124,7 @@ Azure Blob
 Avoid context deadline exceeded error by setting a large TryTimeout
 value (brused27)
 .IP \[bu] 2
-Fix erroneous Rmdir error \[lq]directory not empty\[rq] (Nick
+Fix erroneous Rmdir error \[dq]directory not empty\[dq] (Nick
 Craig\-Wood)
 .IP \[bu] 2
 Wait for up to 60s to create a just deleted container (Nick Craig\-Wood)
@@ -35022,9 +33157,10 @@ S3
 Set ACL for server side copies to that provided by the user (Nick
 Craig\-Wood)
 .IP \[bu] 2
-Fix role_arn, credential_source, \&... (Erik Swanson)
+Fix role_arn, credential_source, ...
+(Erik Swanson)
 .IP \[bu] 2
-Add config info for Wasabi\[cq]s US\-West endpoint (Henry Ptasinski)
+Add config info for Wasabi\[aq]s US\-West endpoint (Henry Ptasinski)
 .RE
 .IP \[bu] 2
 SFTP
@@ -35107,10 +33243,10 @@ Bug Fixes
 .IP \[bu] 2
 Fix \-P not ending with a new line (Nick Craig\-Wood)
 .IP \[bu] 2
-config: don\[cq]t create default config dir when user supplies
+config: don\[aq]t create default config dir when user supplies
 \f[C]\-\-config\f[R] (albertony)
 .IP \[bu] 2
-Don\[cq]t print non\-ASCII characters with \f[C]\-\-progress\f[R] on
+Don\[aq]t print non\-ASCII characters with \f[C]\-\-progress\f[R] on
 windows (Nick Craig\-Wood)
 .IP \[bu] 2
 Correct logs for excluded items (ssaqua)
@@ -35638,10 +33774,10 @@ WebDAV
 Ensure we call MKCOL with a URL with a trailing / for QNAP interop (Nick
 Craig\-Wood)
 .IP \[bu] 2
-If root ends with / then don\[cq]t check if it is a file (Nick
+If root ends with / then don\[aq]t check if it is a file (Nick
 Craig\-Wood)
 .IP \[bu] 2
-Don\[cq]t accept redirects when reading metadata (Nick Craig\-Wood)
+Don\[aq]t accept redirects when reading metadata (Nick Craig\-Wood)
 .IP \[bu] 2
 Add bearer token (Macaroon) support for dCache (Nick Craig\-Wood)
 .IP \[bu] 2
@@ -35674,7 +33810,7 @@ deletefile command (Filip Bartodziej)
 New Features
 .RS 2
 .IP \[bu] 2
-copy, move: Copy single files directly, don\[cq]t use
+copy, move: Copy single files directly, don\[aq]t use
 \f[C]\-\-files\-from\f[R] work\-around
 .RS 2
 .IP \[bu] 2
@@ -35711,9 +33847,9 @@ Add \f[C]\-\-absolute\f[R] flag to add a leading / onto path names
 .IP \[bu] 2
 Add \f[C]\-\-csv\f[R] flag for compliant CSV output
 .IP \[bu] 2
-Add `m' format specifier to show the MimeType
+Add \[aq]m\[aq] format specifier to show the MimeType
 .IP \[bu] 2
-Implement `i' format for showing object ID
+Implement \[aq]i\[aq] format for showing object ID
 .RE
 .IP \[bu] 2
 lsjson
@@ -35742,7 +33878,7 @@ Calculate ModifyWindow each time on the fly to fix various problems
 Mount
 .RS 2
 .IP \[bu] 2
-Only print \[lq]File.rename error\[rq] if there actually is an error
+Only print \[dq]File.rename error\[dq] if there actually is an error
 (Stefan Breunig)
 .IP \[bu] 2
 Delay rename if file has open writers instead of failing outright
@@ -35829,7 +33965,7 @@ Add \f[C]\-\-drive\-acknowledge\-abuse\f[R] to download flagged files
 .IP \[bu] 2
 Add \f[C]\-\-drive\-alternate\-export\f[R] to fix large doc export
 .IP \[bu] 2
-Don\[cq]t attempt to choose Team Drives when using rclone config create
+Don\[aq]t attempt to choose Team Drives when using rclone config create
 .IP \[bu] 2
 Fix change list polling with team drives
 .IP \[bu] 2
@@ -35895,7 +34031,7 @@ New Features
 .IP \[bu] 2
 lsd: Add \-R flag and fix and update docs for all ls commands
 .IP \[bu] 2
-ncdu: added a \[lq]refresh\[rq] key \- CTRL\-L (Keith Goldfarb)
+ncdu: added a \[dq]refresh\[dq] key \- CTRL\-L (Keith Goldfarb)
 .IP \[bu] 2
 serve restic: Add append\-only mode (Steve Kriss)
 .IP \[bu] 2
@@ -35904,15 +34040,15 @@ Neumann)
 .IP \[bu] 2
 serve restic: Print actual listener address (Matt Holt)
 .IP \[bu] 2
-size: Add \[en]json flag (Matthew Holt)
+size: Add \-\-json flag (Matthew Holt)
 .IP \[bu] 2
-sync: implement \[en]ignore\-errors (Mateusz Pabian)
+sync: implement \-\-ignore\-errors (Mateusz Pabian)
 .IP \[bu] 2
 dedupe: Add dedupe largest functionality (Richard Yang)
 .IP \[bu] 2
 fs: Extend SizeSuffix to include TB and PB for rclone about
 .IP \[bu] 2
-fs: add \[en]dump goroutines and \[en]dump openfiles for debugging
+fs: add \-\-dump goroutines and \-\-dump openfiles for debugging
 .IP \[bu] 2
 rc: implement core/memstats to print internal memory usage info
 .IP \[bu] 2
@@ -35935,7 +34071,7 @@ Fix \f[C]make tarball\f[R] (Chih\-Hsuan Yen)
 Bug Fixes
 .RS 2
 .IP \[bu] 2
-filter: fix \[en]min\-age and \[en]max\-age together check
+filter: fix \-\-min\-age and \-\-max\-age together check
 .IP \[bu] 2
 fs: limit MaxIdleConns and MaxIdleConnsPerHost in transport
 .IP \[bu] 2
@@ -35943,7 +34079,7 @@ lsd,lsf: make sure all times we output are in local time
 .IP \[bu] 2
 rc: fix setting bwlimit to unlimited
 .IP \[bu] 2
-rc: take note of the \[en]rc\-addr flag too as per the docs
+rc: take note of the \-\-rc\-addr flag too as per the docs
 .RE
 .IP \[bu] 2
 Mount
@@ -35970,13 +34106,13 @@ VFS
 .IP \[bu] 2
 Filter files \f[C].\f[R] and \f[C]..\f[R] from directory listing
 .IP \[bu] 2
-Only make the VFS cache if \[en]vfs\-cache\-mode > Off
+Only make the VFS cache if \-\-vfs\-cache\-mode > Off
 .RE
 .IP \[bu] 2
 Local
 .RS 2
 .IP \[bu] 2
-Add \[en]local\-no\-check\-updated to disable updated file checks
+Add \-\-local\-no\-check\-updated to disable updated file checks
 .IP \[bu] 2
 Retry remove on Windows sharing violation error
 .RE
@@ -36048,7 +34184,7 @@ path (Stefan Breunig)
 HTTP
 .RS 2
 .IP \[bu] 2
-Fix sync for servers which don\[cq]t return Content\-Length in HEAD
+Fix sync for servers which don\[aq]t return Content\-Length in HEAD
 .RE
 .IP \[bu] 2
 Onedrive
@@ -36073,9 +34209,9 @@ Add in config for all the supported S3 providers
 .IP \[bu] 2
 Add One Zone Infrequent Access storage class (Craig Rachel)
 .IP \[bu] 2
-Add \[en]use\-server\-modtime support (Peter Baumgartner)
+Add \-\-use\-server\-modtime support (Peter Baumgartner)
 .IP \[bu] 2
-Add \[en]s3\-chunk\-size option to control multipart uploads
+Add \-\-s3\-chunk\-size option to control multipart uploads
 .IP \[bu] 2
 Ignore zero length directory markers
 .RE
@@ -36095,7 +34231,7 @@ Fail soft with a debug on hash failure
 Swift
 .RS 2
 .IP \[bu] 2
-Add \[en]use\-server\-modtime support (Peter Baumgartner)
+Add \-\-use\-server\-modtime support (Peter Baumgartner)
 .RE
 .IP \[bu] 2
 Webdav
@@ -36136,7 +34272,7 @@ Thanks Alexander Neumann for help, patches and review
 \f[C]rc\f[R]: enable the remote control of a running rclone
 .RS 2
 .IP \[bu] 2
-The running rclone must be started with \[en]rc and related flags.
+The running rclone must be started with \-\-rc and related flags.
 .IP \[bu] 2
 Currently there is support for bwlimit, and flushing for mount and
 cache.
@@ -36221,8 +34357,8 @@ on first access
 .IP \[bu] 2
 config: retry saving the config after failure (Mateusz)
 .IP \[bu] 2
-sync: when using \f[C]\-\-backup\-dir\f[R] don\[cq]t delete files if we
-can\[cq]t set their modtime
+sync: when using \f[C]\-\-backup\-dir\f[R] don\[aq]t delete files if we
+can\[aq]t set their modtime
 .RS 2
 .IP \[bu] 2
 this fixes odd behaviour with Dropbox and \f[C]\-\-backup\-dir\f[R]
@@ -36233,7 +34369,7 @@ fshttp: fix idle timeouts for HTTP connections
 \f[C]serve http\f[R]: fix serving files with : in \- fixes
 .IP \[bu] 2
 Fix \f[C]\-\-exclude\-if\-present\f[R] to ignore directories which it
-doesn\[cq]t have permission for (Iakov Davydov)
+doesn\[aq]t have permission for (Iakov Davydov)
 .IP \[bu] 2
 Make accounting work properly with crypt and b2
 .IP \[bu] 2
@@ -36294,7 +34430,7 @@ Fix creation of files when truncating
 Write 0 bytes when flushing unwritten handles to avoid race conditions
 in FUSE
 .IP \[bu] 2
-Downgrade \[lq]poll\-interval is not supported\[rq] message to Info
+Downgrade \[dq]poll\-interval is not supported\[dq] message to Info
 .IP \[bu] 2
 Make OpenFile and friends return EINVAL if O_RDONLY and O_TRUNC
 .RE
@@ -36302,7 +34438,7 @@ Make OpenFile and friends return EINVAL if O_RDONLY and O_TRUNC
 Local
 .RS 2
 .IP \[bu] 2
-Downgrade \[lq]invalid cross\-device link: trying copy\[rq] to debug
+Downgrade \[dq]invalid cross\-device link: trying copy\[dq] to debug
 .IP \[bu] 2
 Make DirMove return fs.ErrorCantDirMove to allow fallback to Copy for
 cross device
@@ -36344,7 +34480,7 @@ Implement DirChangeNotify to notify cache/vfs/mount of changes
 Azureblob
 .RS 2
 .IP \[bu] 2
-Don\[cq]t check for bucket/container presence if listing was OK
+Don\[aq]t check for bucket/container presence if listing was OK
 .RS 2
 .IP \[bu] 2
 this makes rclone do one less request per invocation
@@ -36356,7 +34492,7 @@ Improve accounting for chunked uploads
 Backblaze B2
 .RS 2
 .IP \[bu] 2
-Don\[cq]t check for bucket/container presence if listing was OK
+Don\[aq]t check for bucket/container presence if listing was OK
 .RS 2
 .IP \[bu] 2
 this makes rclone do one less request per invocation
@@ -36378,7 +34514,7 @@ Fix custom oauth client parameters
 Google Cloud Storage
 .RS 2
 .IP \[bu] 2
-Don\[cq]t check for bucket/container presence if listing was OK
+Don\[aq]t check for bucket/container presence if listing was OK
 .RS 2
 .IP \[bu] 2
 this makes rclone do one less request per invocation
@@ -36446,7 +34582,7 @@ Remove unused chunked upload flag and code
 Qingstor
 .RS 2
 .IP \[bu] 2
-Don\[cq]t check for bucket/container presence if listing was OK
+Don\[aq]t check for bucket/container presence if listing was OK
 .RS 2
 .IP \[bu] 2
 this makes rclone do one less request per invocation
@@ -36462,7 +34598,7 @@ Initial support for IBM COS (S3) (Giri Badanahatti)
 .IP \[bu] 2
 Update docs to discourage use of v2 auth with CEPH and others
 .IP \[bu] 2
-Don\[cq]t check for bucket/container presence if listing was OK
+Don\[aq]t check for bucket/container presence if listing was OK
 .RS 2
 .IP \[bu] 2
 this makes rclone do one less request per invocation
@@ -36502,7 +34638,7 @@ in v1.39 a bug was introduced which ignored new tokens \- this fixes it
 .IP \[bu] 2
 Fix extra HEAD transaction when uploading a new file
 .IP \[bu] 2
-Don\[cq]t check for bucket/container presence if listing was OK
+Don\[aq]t check for bucket/container presence if listing was OK
 .RS 2
 .IP \[bu] 2
 this makes rclone do one less request per invocation
@@ -36561,19 +34697,19 @@ New Features
 .IP \[bu] 2
 curl install for rclone (Filip Bartodziej)
 .IP \[bu] 2
-\[en]stats now shows percentage, size, rate and ETA in condensed form
+\-\-stats now shows percentage, size, rate and ETA in condensed form
 (Ishuah Kariuki)
 .IP \[bu] 2
-\[en]exclude\-if\-present to exclude a directory if a file is present
+\-\-exclude\-if\-present to exclude a directory if a file is present
 (Iakov Davydov)
 .IP \[bu] 2
-rmdirs: add \[en]leave\-root flag (lewapm)
+rmdirs: add \-\-leave\-root flag (lewapm)
 .IP \[bu] 2
-move: add \[en]delete\-empty\-src\-dirs flag to remove dirs after move
+move: add \-\-delete\-empty\-src\-dirs flag to remove dirs after move
 (Ishuah Kariuki)
 .IP \[bu] 2
-Add \[en]dump flag, introduce \[en]dump requests, responses and remove
-\[en]dump\-auth, \[en]dump\-filters
+Add \-\-dump flag, introduce \-\-dump requests, responses and remove
+\-\-dump\-auth, \-\-dump\-filters
 .RS 2
 .IP \[bu] 2
 Obscure X\-Auth\-Token: from headers when dumping too
@@ -36594,7 +34730,7 @@ more reliable
 Save the config before asking for a token, fixes disappearing oauth
 config
 .IP \[bu] 2
-Warn the user if \[en]include and \[en]exclude are used together (Ernest
+Warn the user if \-\-include and \-\-exclude are used together (Ernest
 Borowski)
 .IP \[bu] 2
 Fix duplicate files (eg on Google drive) causing spurious copies
@@ -36611,10 +34747,10 @@ moveto/copyto: Fix to allow copying to the same name
 Mount
 .RS 2
 .IP \[bu] 2
-\[en]vfs\-cache mode to make writes into mounts more reliable.
+\-\-vfs\-cache mode to make writes into mounts more reliable.
 .RS 2
 .IP \[bu] 2
-this requires caching files on the disk (see \[en]cache\-dir)
+this requires caching files on the disk (see \-\-cache\-dir)
 .IP \[bu] 2
 As this is a new feature, use with care
 .RE
@@ -36676,7 +34812,7 @@ Backblaze B2
 .IP \[bu] 2
 Fix multipart upload retries
 .IP \[bu] 2
-Fix \[en]hard\-delete to make it work 100% of the time
+Fix \-\-hard\-delete to make it work 100% of the time
 .RE
 .IP \[bu] 2
 Swift
@@ -36705,8 +34841,8 @@ Add option to enable the use of aes128\-cbc cipher (Jon Fautley)
 Amazon cloud drive
 .RS 2
 .IP \[bu] 2
-Fix download of large files failing with \[lq]Only one auth mechanism
-allowed\[rq]
+Fix download of large files failing with \[dq]Only one auth mechanism
+allowed\[dq]
 .RE
 .IP \[bu] 2
 crypt
@@ -36763,7 +34899,7 @@ less memory
 .IP \[bu] 2
 \f[C]cleanup\f[R] for remaining remotes (thanks ishuah)
 .IP \[bu] 2
-\f[C]\-\-immutable\f[R] for ensuring that files don\[cq]t change (thanks
+\f[C]\-\-immutable\f[R] for ensuring that files don\[aq]t change (thanks
 Jacob McNamee)
 .IP \[bu] 2
 \f[C]\-\-user\-agent\f[R] option (thanks Alex McGrath Kraak)
@@ -36817,7 +34953,7 @@ Re\-use \f[C]rcat\f[R] internals to support uploads from all remotes
 Dropbox
 .RS 2
 .IP \[bu] 2
-Fix \[lq]entry doesn\[cq]t belong in directory\[rq] error
+Fix \[dq]entry doesn\[aq]t belong in directory\[dq] error
 .IP \[bu] 2
 Stop using deprecated API methods
 .RE
@@ -36920,7 +35056,7 @@ Dropbox)
 New Features
 .RS 2
 .IP \[bu] 2
-Implement \[en]fast\-list flag
+Implement \-\-fast\-list flag
 .RS 2
 .IP \[bu] 2
 This allows remotes to list recursively if they can
@@ -36931,13 +35067,13 @@ This may or may not be quicker
 .IP \[bu] 2
 This will use more memory as it has to hold the listing in memory
 .IP \[bu] 2
-\[en]old\-sync\-method deprecated \- the remaining uses are covered by
-\[en]fast\-list
+\-\-old\-sync\-method deprecated \- the remaining uses are covered by
+\-\-fast\-list
 .IP \[bu] 2
 This involved a major re\-write of all the listing code
 .RE
 .IP \[bu] 2
-Add \[en]tpslimit and \[en]tpslimit\-burst to limit transactions per
+Add \-\-tpslimit and \-\-tpslimit\-burst to limit transactions per
 second
 .RS 2
 .IP \[bu] 2
@@ -36945,7 +35081,7 @@ this is useful in conjunction with \f[C]rclone mount\f[R] to limit
 external apps
 .RE
 .IP \[bu] 2
-Add \[en]stats\-log\-level so can see \[en]stats without \-v
+Add \-\-stats\-log\-level so can see \-\-stats without \-v
 .IP \[bu] 2
 Print password prompts to stderr \- Hraban Luyat
 .IP \[bu] 2
@@ -36959,7 +35095,7 @@ allow auth_url and token_url to be set in the config file
 Print redirection URI if using own credentials.
 .RE
 .IP \[bu] 2
-Don\[cq]t Mkdir at the start of sync to save transactions
+Don\[aq]t Mkdir at the start of sync to save transactions
 .RE
 .IP \[bu] 2
 Compile
@@ -36969,7 +35105,7 @@ Update build to go1.8.3
 .IP \[bu] 2
 Require go1.6 for building rclone
 .IP \[bu] 2
-Compile 386 builds with \[lq]GO386=387\[rq] for maximum compatibility
+Compile 386 builds with \[dq]GO386=387\[dq] for maximum compatibility
 .RE
 .IP \[bu] 2
 Bug Fixes
@@ -36979,7 +35115,7 @@ Fix menu selection when no remotes
 .IP \[bu] 2
 Config saving reworked to not kill the file if disk gets full
 .IP \[bu] 2
-Don\[cq]t delete remote if name does not change while renaming
+Don\[aq]t delete remote if name does not change while renaming
 .IP \[bu] 2
 moveto, copyto: report transfers and checks as per move and copy
 .RE
@@ -36987,7 +35123,7 @@ moveto, copyto: report transfers and checks as per move and copy
 Local
 .RS 2
 .IP \[bu] 2
-Add \[en]local\-no\-unicode\-normalization flag \- Bob Potter
+Add \-\-local\-no\-unicode\-normalization flag \- Bob Potter
 .RE
 .IP \[bu] 2
 Mount
@@ -37003,7 +35139,7 @@ J\['e]r\[^o]me Vizcaino
 .IP \[bu] 2
 On read only open of file, make open pending until first read
 .IP \[bu] 2
-Make \[en]read\-only reject modify operations
+Make \-\-read\-only reject modify operations
 .IP \[bu] 2
 Implement ModTime via FUSE for remotes that support it
 .IP \[bu] 2
@@ -37019,7 +35155,7 @@ Crypt
 .IP \[bu] 2
 Report the name:root as specified by the user
 .IP \[bu] 2
-Add an \[lq]obfuscate\[rq] option for filename encryption \- Stephen
+Add an \[dq]obfuscate\[dq] option for filename encryption \- Stephen
 Harris
 .RE
 .IP \[bu] 2
@@ -37045,12 +35181,12 @@ Add team drive support
 Reduce bandwidth by adding fields for partial responses \- Martin
 Kristensen
 .IP \[bu] 2
-Implement \[en]drive\-shared\-with\-me flag to view shared with me files
+Implement \-\-drive\-shared\-with\-me flag to view shared with me files
 \- Danny Tsai
 .IP \[bu] 2
-Add \[en]drive\-trashed\-only to read only the files in the trash
+Add \-\-drive\-trashed\-only to read only the files in the trash
 .IP \[bu] 2
-Remove obsolete \[en]drive\-full\-list
+Remove obsolete \-\-drive\-full\-list
 .IP \[bu] 2
 Add missing seek to start on retries of chunked uploads
 .IP \[bu] 2
@@ -37173,12 +35309,12 @@ Re\-implement sync routine to work a directory at a time reducing memory
 usage
 .IP \[bu] 2
 Logging revamped to be more inline with rsync \- now much quieter * \-v
-only shows transfers * \-vv is for full debug * \[en]syslog to log to
+only shows transfers * \-vv is for full debug * \-\-syslog to log to
 syslog on capable platforms
 .IP \[bu] 2
-Implement \[en]backup\-dir and \[en]suffix
+Implement \-\-backup\-dir and \-\-suffix
 .IP \[bu] 2
-Implement \[en]track\-renames (initial implementation by Bj\[/o]rn Erik
+Implement \-\-track\-renames (initial implementation by Bj\[/o]rn Erik
 Pedersen)
 .IP \[bu] 2
 Add time\-based bandwidth limits (Lukas Loesche)
@@ -37188,24 +35324,24 @@ rclone cryptcheck: checks integrity of crypt remotes
 Allow all config file variables and options to be set from environment
 variables
 .IP \[bu] 2
-Add \[en]buffer\-size parameter to control buffer size for copy
+Add \-\-buffer\-size parameter to control buffer size for copy
 .IP \[bu] 2
-Make \[en]delete\-after the default
+Make \-\-delete\-after the default
 .IP \[bu] 2
-Add \[en]ignore\-checksum flag (fixed by Hisham Zarka)
+Add \-\-ignore\-checksum flag (fixed by Hisham Zarka)
 .IP \[bu] 2
-rclone check: Add \[en]download flag to check all the data, not just
+rclone check: Add \-\-download flag to check all the data, not just
 hashes
 .IP \[bu] 2
-rclone cat: add \[en]head, \[en]tail, \[en]offset, \[en]count and
-\[en]discard
+rclone cat: add \-\-head, \-\-tail, \-\-offset, \-\-count and
+\-\-discard
 .IP \[bu] 2
 rclone config: when choosing from a list, allow the value to be entered
 too
 .IP \[bu] 2
 rclone config: allow rename and copy of remotes
 .IP \[bu] 2
-rclone obscure: for generating encrypted passwords for rclone\[cq]s
+rclone obscure: for generating encrypted passwords for rclone\[aq]s
 config (T.C.
 Ferguson)
 .IP \[bu] 2
@@ -37231,15 +35367,15 @@ Bug Fixes
 .RS 2
 .IP \[bu] 2
 Fix copyto copying things to the wrong place if the destination dir
-didn\[cq]t exist
+didn\[aq]t exist
 .IP \[bu] 2
 Fix parsing of remotes in moveto and copyto
 .IP \[bu] 2
-Fix \[en]delete\-before deleting files on copy
+Fix \-\-delete\-before deleting files on copy
 .IP \[bu] 2
-Fix \[en]files\-from with an empty file copying everything
+Fix \-\-files\-from with an empty file copying everything
 .IP \[bu] 2
-Fix sync: don\[cq]t update mod times if \[en]dry\-run set
+Fix sync: don\[aq]t update mod times if \-\-dry\-run set
 .IP \[bu] 2
 Fix MimeType propagation
 .IP \[bu] 2
@@ -37249,13 +35385,13 @@ Fix filters to add ** rules to directory rules
 Local
 .RS 2
 .IP \[bu] 2
-Implement \-L, \[en]copy\-links flag to allow rclone to follow symlinks
+Implement \-L, \-\-copy\-links flag to allow rclone to follow symlinks
 .IP \[bu] 2
 Open files in write only mode so rclone can write to an rclone mount
 .IP \[bu] 2
 Fix unnormalised unicode causing problems reading directories
 .IP \[bu] 2
-Fix interaction between \-x flag and \[en]max\-depth
+Fix interaction between \-x flag and \-\-max\-depth
 .RE
 .IP \[bu] 2
 Mount
@@ -37265,7 +35401,7 @@ Implement proper directory handling (mkdir, rmdir, renaming)
 .IP \[bu] 2
 Make include and exclude filters apply to mount
 .IP \[bu] 2
-Implement read and write async buffers \- control with \[en]buffer\-size
+Implement read and write async buffers \- control with \-\-buffer\-size
 .IP \[bu] 2
 Fix fsync on for directories
 .IP \[bu] 2
@@ -37275,7 +35411,7 @@ Fix retry on network failure when reading off crypt
 Crypt
 .RS 2
 .IP \[bu] 2
-Add \[en]crypt\-show\-mapping to show encrypted file mapping
+Add \-\-crypt\-show\-mapping to show encrypted file mapping
 .IP \[bu] 2
 Fix crypt writer getting stuck in a loop
 .RS 2
@@ -37320,11 +35456,11 @@ Drive
 .IP \[bu] 2
 Fix Rmdir on directories with trashed files
 .IP \[bu] 2
-Fix \[lq]Ignoring unknown object\[rq] when downloading
+Fix \[dq]Ignoring unknown object\[dq] when downloading
 .IP \[bu] 2
-Add \[en]drive\-list\-chunk
+Add \-\-drive\-list\-chunk
 .IP \[bu] 2
-Add \[en]drive\-skip\-gdocs (K\['a]roly Ol\['a]h)
+Add \-\-drive\-skip\-gdocs (K\['a]roly Ol\['a]h)
 .RE
 .IP \[bu] 2
 OneDrive
@@ -37379,7 +35515,7 @@ moveto and copyto commands for choosing a destination name on copy/move
 .IP \[bu] 2
 rmdirs command to recursively delete empty directories
 .IP \[bu] 2
-Allow repeated \[en]include/\[en]exclude/\[en]filter options
+Allow repeated \-\-include/\-\-exclude/\-\-filter options
 .IP \[bu] 2
 Only show transfer stats on commands which transfer stuff
 .RS 2
@@ -37390,7 +35526,7 @@ show stats on any command using the \f[C]\-\-stats\f[R] flag
 Allow overlapping directories in move when server side dir move is
 supported
 .IP \[bu] 2
-Add \[en]stats\-unit option \- thanks Scott McGillivray
+Add \-\-stats\-unit option \- thanks Scott McGillivray
 .RE
 .IP \[bu] 2
 Bug Fixes
@@ -37403,7 +35539,7 @@ Make rclone lsd obey the filters properly
 .IP \[bu] 2
 Fix compilation on mips
 .IP \[bu] 2
-Fix not transferring files that don\[cq]t differ in size
+Fix not transferring files that don\[aq]t differ in size
 .IP \[bu] 2
 Fix panic on nil retry/fatal error
 .RE
@@ -37415,9 +35551,9 @@ Retry reads on error \- should help with reliability a lot
 .IP \[bu] 2
 Report the modification times for directories from the remote
 .IP \[bu] 2
-Add bandwidth accounting and limiting (fixes \[en]bwlimit)
+Add bandwidth accounting and limiting (fixes \-\-bwlimit)
 .IP \[bu] 2
-If \[en]stats provided will show stats and which files are transferring
+If \-\-stats provided will show stats and which files are transferring
 .IP \[bu] 2
 Support R/W files if truncate is set.
 .IP \[bu] 2
@@ -37455,7 +35591,7 @@ B2
 Use new prefix and delimiter parameters in directory listings
 .RS 2
 .IP \[bu] 2
-This makes \[en]max\-depth 1 dir listings as used in mount much faster
+This makes \-\-max\-depth 1 dir listings as used in mount much faster
 .RE
 .IP \[bu] 2
 Reauth the account while doing uploads too \- should help with token
@@ -37484,7 +35620,7 @@ Make ContentType be preserved for cloud to cloud copies
 Add support to toggle bandwidth limits via SIGUSR2 \- thanks Marco
 Paganini
 .IP \[bu] 2
-\f[C]rclone check\f[R] shows count of hashes that couldn\[cq]t be
+\f[C]rclone check\f[R] shows count of hashes that couldn\[aq]t be
 checked
 .IP \[bu] 2
 \f[C]rclone listremotes\f[R] command
@@ -37510,7 +35646,7 @@ Fix deletion of src file when dst file older
 .IP \[bu] 2
 Fix \f[C]rclone check\f[R] on crypted file systems
 .IP \[bu] 2
-Make failed uploads not count as \[lq]Transferred\[rq]
+Make failed uploads not count as \[dq]Transferred\[dq]
 .IP \[bu] 2
 Make sure high level retries show with \f[C]\-q\f[R]
 .IP \[bu] 2
@@ -37549,7 +35685,7 @@ Fix crash on 32 bit ARM (alignment of 64 bit counter)
 Crypt
 .RS 2
 .IP \[bu] 2
-Don\[cq]t show encrypted password in configurator to stop confusion
+Don\[aq]t show encrypted password in configurator to stop confusion
 .RE
 .IP \[bu] 2
 Amazon Drive
@@ -37622,7 +35758,7 @@ formats.
 Swift
 .RS 2
 .IP \[bu] 2
-Don\[cq]t read metadata for directory marker objects
+Don\[aq]t read metadata for directory marker objects
 .RE
 .SS v1.33 \- 2016\-08\-24
 .IP \[bu] 2
@@ -37721,7 +35857,7 @@ New Features
 .IP \[bu] 2
 Reduce memory on sync by about 50%
 .IP \[bu] 2
-Implement \[en]no\-traverse flag to stop copy traversing the destination
+Implement \-\-no\-traverse flag to stop copy traversing the destination
 remote.
 .RS 2
 .IP \[bu] 2
@@ -37740,14 +35876,14 @@ Currently B2 only
 Single file handling improved
 .RS 2
 .IP \[bu] 2
-Now copied with \[en]files\-from
+Now copied with \-\-files\-from
 .IP \[bu] 2
-Automatically sets \[en]no\-traverse when copying a single file
+Automatically sets \-\-no\-traverse when copying a single file
 .RE
 .IP \[bu] 2
 Info on using installing with ansible \- thanks Stefan Weichinger
 .IP \[bu] 2
-Implement \[en]no\-update\-modtime flag to stop rclone fixing the remote
+Implement \-\-no\-update\-modtime flag to stop rclone fixing the remote
 modified times.
 .RE
 .IP \[bu] 2
@@ -37784,14 +35920,14 @@ Add instructions on how to use rclone with minio.
 .IP \[bu] 2
 Add ap\-northeast\-2 (Seoul) and ap\-south\-1 (Mumbai) regions.
 .IP \[bu] 2
-Skip setting the modified time for objects > 5GB as it isn\[cq]t
+Skip setting the modified time for objects > 5GB as it isn\[aq]t
 possible.
 .RE
 .IP \[bu] 2
 Backblaze B2
 .RS 2
 .IP \[bu] 2
-Add \[en]b2\-versions flag so old versions can be listed and retrieved.
+Add \-\-b2\-versions flag so old versions can be listed and retrieved.
 .IP \[bu] 2
 Treat 403 errors (eg cap exceeded) as fatal.
 .IP \[bu] 2
@@ -37801,7 +35937,7 @@ Make error handling compliant with B2 integrations notes.
 .IP \[bu] 2
 Fix handling of token expiry.
 .IP \[bu] 2
-Implement \[en]b2\-test\-mode to set \f[C]X\-Bz\-Test\-Mode\f[R] header.
+Implement \-\-b2\-test\-mode to set \f[C]X\-Bz\-Test\-Mode\f[R] header.
 .IP \[bu] 2
 Set cutoff for chunked upload to 200MB as per B2 guidelines.
 .IP \[bu] 2
@@ -37811,7 +35947,7 @@ Make upload multi\-threaded.
 Dropbox
 .RS 2
 .IP \[bu] 2
-Don\[cq]t retry 461 errors.
+Don\[aq]t retry 461 errors.
 .RE
 .SS v1.30 \- 2016\-06\-18
 .IP \[bu] 2
@@ -37825,7 +35961,7 @@ This enables
 .IP \[bu] 2
 Directory include filtering for efficiency
 .IP \[bu] 2
-\[en]max\-depth parameter
+\-\-max\-depth parameter
 .IP \[bu] 2
 Better error reporting
 .IP \[bu] 2
@@ -37834,7 +35970,7 @@ More to come
 .IP \[bu] 2
 Retry more errors
 .IP \[bu] 2
-Add \[en]ignore\-size flag \- for uploading images to onedrive
+Add \-\-ignore\-size flag \- for uploading images to onedrive
 .IP \[bu] 2
 Log \-v output to stdout by default
 .IP \[bu] 2
@@ -37842,10 +35978,10 @@ Display the transfer stats in more human readable form
 .IP \[bu] 2
 Make 0 size files specifiable with \f[C]\-\-max\-size 0b\f[R]
 .IP \[bu] 2
-Add \f[C]b\f[R] suffix so we can specify bytes in \[en]bwlimit,
-\[en]min\-size etc
+Add \f[C]b\f[R] suffix so we can specify bytes in \-\-bwlimit,
+\-\-min\-size etc
 .IP \[bu] 2
-Use \[lq]password:\[rq] instead of \[lq]password>\[rq] prompt \- thanks
+Use \[dq]password:\[dq] instead of \[dq]password>\[dq] prompt \- thanks
 Klaus Post and Leigh Klotz
 .RE
 .IP \[bu] 2
@@ -37897,7 +36033,7 @@ Wilson
 Google Cloud Storage
 .RS 2
 .IP \[bu] 2
-Make sure we don\[cq]t use conflicting content types on upload
+Make sure we don\[aq]t use conflicting content types on upload
 .IP \[bu] 2
 Add service account support \- thanks Michal Witkowski
 .RE
@@ -37951,10 +36087,10 @@ Bug fixes
 .IP \[bu] 2
 Make rclone check obey the \f[C]\-\-size\-only\f[R] flag.
 .IP \[bu] 2
-Use \[lq]application/octet\-stream\[rq] if discovered mime type is
+Use \[dq]application/octet\-stream\[dq] if discovered mime type is
 invalid.
 .IP \[bu] 2
-Fix missing \[lq]quit\[rq] option when there are no remotes.
+Fix missing \[dq]quit\[dq] option when there are no remotes.
 .RE
 .IP \[bu] 2
 Google Drive
@@ -37980,7 +36116,7 @@ This means that B2 will now check modification times
 .IP \[bu] 2
 It will upload new files to update the modification times
 .IP \[bu] 2
-(there isn\[cq]t an API to just set the mod time.)
+(there isn\[aq]t an API to just set the mod time.)
 .IP \[bu] 2
 If you want the old behaviour use \f[C]\-\-size\-only\f[R].
 .RE
@@ -37993,7 +36129,7 @@ Fix parsing of mod time when not in metadata
 Swift/Hubic
 .RS 2
 .IP \[bu] 2
-Don\[cq]t return an MD5SUM for static large objects
+Don\[aq]t return an MD5SUM for static large objects
 .RE
 .IP \[bu] 2
 S3
@@ -38023,7 +36159,7 @@ Optionally disable gzip compression on downloads with
 Bug fixes
 .RS 2
 .IP \[bu] 2
-Don\[cq]t make directories if \f[C]\-\-dry\-run\f[R] set
+Don\[aq]t make directories if \f[C]\-\-dry\-run\f[R] set
 .IP \[bu] 2
 Fix and document the \f[C]move\f[R] command
 .IP \[bu] 2
@@ -38045,7 +36181,7 @@ Add pacing, retries and reauthentication \- fixes token expiry problems
 Upload without using a temporary file from local (and remotes which
 support SHA1)
 .IP \[bu] 2
-Fix reading metadata for all files when it shouldn\[cq]t have been
+Fix reading metadata for all files when it shouldn\[aq]t have been
 .RE
 .IP \[bu] 2
 Drive
@@ -38117,7 +36253,7 @@ Amazon Drive
 .IP \[bu] 2
 Fix download of files > 10 GB
 .IP \[bu] 2
-Fix directory traversal (\[lq]Next token is expired\[rq]) for large
+Fix directory traversal (\[dq]Next token is expired\[dq]) for large
 directory listings
 .IP \[bu] 2
 Remove 409 conflict from error codes we will retry \- stops very long
@@ -38167,12 +36303,12 @@ Add local file system option to disable UNC on Windows.
 New Features
 .RS 2
 .IP \[bu] 2
-Yandex storage backend \- thank you Dmitry Burdeev (\[lq]dibu\[rq])
+Yandex storage backend \- thank you Dmitry Burdeev (\[dq]dibu\[dq])
 .IP \[bu] 2
 Implement Backblaze B2 storage backend
 .IP \[bu] 2
-Add \[en]min\-age and \[en]max\-age flags \- thank you Adriano
-Aur\['e]lio Meirelles
+Add \-\-min\-age and \-\-max\-age flags \- thank you Adriano Aur\['e]lio
+Meirelles
 .IP \[bu] 2
 Make ls/lsl/md5sum/size/check obey includes and excludes
 .RE
@@ -38196,7 +36332,7 @@ OneDrive
 .IP \[bu] 2
 Re\-enable server side copy
 .IP \[bu] 2
-Don\[cq]t mask HTTP error codes with JSON decode error
+Don\[aq]t mask HTTP error codes with JSON decode error
 .RE
 .IP \[bu] 2
 S3
@@ -38215,7 +36351,7 @@ Implement Hubic storage system
 Fixes
 .RS 2
 .IP \[bu] 2
-Fix deletion of some excluded files without \[en]delete\-excluded
+Fix deletion of some excluded files without \-\-delete\-excluded
 .RS 2
 .IP \[bu] 2
 This could have deleted files unexpectedly on sync
@@ -38260,7 +36396,7 @@ Fixes
 Allow spaces in remotes and check remote names for validity at creation
 time
 .IP \[bu] 2
-Allow `&' and disallow `:' in Windows filenames.
+Allow \[aq]&\[aq] and disallow \[aq]:\[aq] in Windows filenames.
 .RE
 .IP \[bu] 2
 Swift
@@ -38269,19 +36405,19 @@ Swift
 Ignore directory marker objects where appropriate \- allows working with
 Hubic
 .IP \[bu] 2
-Don\[cq]t delete the container if fs wasn\[cq]t at root
+Don\[aq]t delete the container if fs wasn\[aq]t at root
 .RE
 .IP \[bu] 2
 S3
 .RS 2
 .IP \[bu] 2
-Don\[cq]t delete the bucket if fs wasn\[cq]t at root
+Don\[aq]t delete the bucket if fs wasn\[aq]t at root
 .RE
 .IP \[bu] 2
 Google Cloud Storage
 .RS 2
 .IP \[bu] 2
-Don\[cq]t delete the bucket if fs wasn\[cq]t at root
+Don\[aq]t delete the bucket if fs wasn\[aq]t at root
 .RE
 .SS v1.23 \- 2015\-10\-03
 .IP \[bu] 2
@@ -38310,8 +36446,8 @@ Allow anonymous access to public buckets
 Swift
 .RS 2
 .IP \[bu] 2
-Stop chunked operations logging \[lq]Failed to read info: Object Not
-Found\[rq]
+Stop chunked operations logging \[dq]Failed to read info: Object Not
+Found\[dq]
 .IP \[bu] 2
 Use Content\-Length on uploads for extra reliability
 .RE
@@ -38361,7 +36497,7 @@ Amazon Drive support
 Oauth support redone \- fix many bugs and improve usability
 .RS 2
 .IP \[bu] 2
-Use \[lq]golang.org/x/oauth2\[rq] as oauth library of choice
+Use \[dq]golang.org/x/oauth2\[dq] as oauth library of choice
 .IP \[bu] 2
 Improve oauth usability for smoother initial signup
 .IP \[bu] 2
@@ -38369,7 +36505,7 @@ drive, googlecloudstorage: optionally use auto config for the oauth
 token
 .RE
 .IP \[bu] 2
-Implement \[en]dump\-headers and \[en]dump\-bodies debug flags
+Implement \-\-dump\-headers and \-\-dump\-bodies debug flags
 .IP \[bu] 2
 Show multiple matched commands if abbreviation too short
 .IP \[bu] 2
@@ -38398,7 +36534,7 @@ Server side copies for s3/swift/drive/dropbox/gcs
 .IP \[bu] 2
 Move command \- uses server side copies if it can
 .IP \[bu] 2
-Implement \[en]retries flag \- tries 3 times by default
+Implement \-\-retries flag \- tries 3 times by default
 .IP \[bu] 2
 Build for plan9/amd64 and solaris/amd64 too
 .RE
@@ -38426,7 +36562,7 @@ drive
 Add \f[C]\-\-drive\-use\-trash\f[R] flag so rclone trashes instead of
 deletes
 .IP \[bu] 2
-Add \[lq]Forbidden to download\[rq] message for files with no
+Add \[dq]Forbidden to download\[dq] message for files with no
 downloadURL
 .RE
 .IP \[bu] 2
@@ -38480,17 +36616,17 @@ dropbox: fix case insensitivity issues \- thanks Leonid Shalupov
 .IP \[bu] 2
 Fix uploading big files which was causing timeouts or panics
 .IP \[bu] 2
-Don\[cq]t check md5sum after download with \[en]size\-only
+Don\[aq]t check md5sum after download with \-\-size\-only
 .SS v1.15 \- 2015\-06\-06
 .IP \[bu] 2
-Add \[en]checksum flag to only discard transfers by MD5SUM \- thanks
-Alex Couper
+Add \-\-checksum flag to only discard transfers by MD5SUM \- thanks Alex
+Couper
 .IP \[bu] 2
-Implement \[en]size\-only flag to sync on size not checksum & modtime
+Implement \-\-size\-only flag to sync on size not checksum & modtime
 .IP \[bu] 2
 Expand docs and remove duplicated information
 .IP \[bu] 2
-Document rclone\[cq]s limitations with directories
+Document rclone\[aq]s limitations with directories
 .IP \[bu] 2
 dropbox: update docs about case insensitivity
 .SS v1.14 \- 2015\-05\-21
@@ -38501,19 +36637,19 @@ problem
 drive: docs about rate limiting
 .IP \[bu] 2
 google cloud storage: Fix compile after API change in
-\[lq]google.golang.org/api/storage/v1\[rq]
+\[dq]google.golang.org/api/storage/v1\[dq]
 .SS v1.13 \- 2015\-05\-10
 .IP \[bu] 2
 Revise documentation (especially sync)
 .IP \[bu] 2
-Implement \[en]timeout and \[en]conntimeout
+Implement \-\-timeout and \-\-conntimeout
 .IP \[bu] 2
-s3: ignore etags from multipart uploads which aren\[cq]t md5sums
+s3: ignore etags from multipart uploads which aren\[aq]t md5sums
 .SS v1.12 \- 2015\-03\-15
 .IP \[bu] 2
 drive: Use chunked upload for files above a certain size
 .IP \[bu] 2
-drive: add \[en]drive\-chunk\-size and \[en]drive\-upload\-cutoff
+drive: add \-\-drive\-chunk\-size and \-\-drive\-upload\-cutoff
 parameters
 .IP \[bu] 2
 drive: switch to insert from update when a failed copy deletes the
@@ -38532,11 +36668,11 @@ Add synchronization to ls/lsl/lsd output to stop corruptions
 .IP \[bu] 2
 Ensure all stats/log messages to go stderr
 .IP \[bu] 2
-Add \[en]log\-file flag to log everything (including panics) to file
+Add \-\-log\-file flag to log everything (including panics) to file
 .IP \[bu] 2
-Make it possible to disable stats printing with \[en]stats=0
+Make it possible to disable stats printing with \-\-stats=0
 .IP \[bu] 2
-Implement \[en]bwlimit to limit data transfer bandwidth
+Implement \-\-bwlimit to limit data transfer bandwidth
 .SS v1.10 \- 2015\-02\-12
 .IP \[bu] 2
 s3: list an unlimited number of items
@@ -38562,7 +36698,7 @@ dropbox: adapt code to recent library changes
 google cloud storage: fix memory leak
 .SS v1.06 \- 2014\-12\-12
 .IP \[bu] 2
-Fix \[lq]Couldn\[cq]t find home directory\[rq] on OSX
+Fix \[dq]Couldn\[aq]t find home directory\[dq] on OSX
 .IP \[bu] 2
 swift: Add tenant parameter
 .IP \[bu] 2
@@ -38605,11 +36741,11 @@ Implement Google Cloud Storage remote
 .IP \[bu] 2
 Verify Md5sums and Sizes after copies
 .IP \[bu] 2
-Remove times from \[lq]ls\[rq] command \- lists sizes only
+Remove times from \[dq]ls\[dq] command \- lists sizes only
 .IP \[bu] 2
-Add add \[lq]lsl\[rq] \- lists times and sizes
+Add add \[dq]lsl\[dq] \- lists times and sizes
 .IP \[bu] 2
-Add \[lq]md5sum\[rq] command
+Add \[dq]md5sum\[dq] command
 .SS v1.01 \- 2014\-07\-04
 .IP \[bu] 2
 drive: fix transfer of big files using up lots of memory
@@ -38618,7 +36754,7 @@ drive: fix transfer of big files using up lots of memory
 drive: fix whole second dates
 .SS v0.99 \- 2014\-06\-26
 .IP \[bu] 2
-Fix \[en]dry\-run not working
+Fix \-\-dry\-run not working
 .IP \[bu] 2
 Make compatible with go 1.1
 .SS v0.98 \- 2014\-05\-30
@@ -38637,7 +36773,7 @@ drive: Fix multiple files of same name being created
 .IP \[bu] 2
 drive: Use o.Update and fs.Put to optimise transfers
 .IP \[bu] 2
-Add version number, \-V and \[en]version
+Add version number, \-V and \-\-version
 .SS v0.95 \- 2014\-03\-28
 .IP \[bu] 2
 rclone.org: website, docs and graphics
@@ -38657,7 +36793,7 @@ cross compile other versions
 set strict permissions on config file
 .SS v0.92 \- 2014\-03\-15
 .IP \[bu] 2
-Config fixes and \[en]config option
+Config fixes and \-\-config option
 .SS v0.91 \- 2014\-03\-15
 .IP \[bu] 2
 Make config file
@@ -38669,34 +36805,36 @@ Project named rclone
 Project started
 .SH Bugs and Limitations
 .SS Limitations
-.SS Directory timestamps aren\[cq]t preserved
+.SS Directory timestamps aren\[aq]t preserved
 .PP
-Rclone doesn\[cq]t currently preserve the timestamps of directories.
+Rclone doesn\[aq]t currently preserve the timestamps of directories.
 This is because rclone only really considers objects when syncing.
-.SS Rclone struggles with millions of files in a directory
+.SS Rclone struggles with millions of files in a directory/bucket
 .PP
-Currently rclone loads each directory entirely into memory before using
-it.
-Since each Rclone object takes 0.5k\-1k of memory this can take a very
-long time and use an extremely large amount of memory.
+Currently rclone loads each directory/bucket entirely into memory before
+using it.
+Since each rclone object takes 0.5k\-1k of memory this can take a very
+long time and use a large amount of memory.
 .PP
-Millions of files in a directory tend caused by software writing cloud
-storage (eg S3 buckets).
+Millions of files in a directory tends to occur on bucket\-based remotes
+(e.g.
+S3 buckets) since those remotes do not segregate subdirectories within
+the bucket.
 .SS Bucket based remotes and folders
 .PP
-Bucket based remotes (eg S3/GCS/Swift/B2) do not have a concept of
-directories.
+Bucket based remotes (e.g.
+S3/GCS/Swift/B2) do not have a concept of directories.
 Rclone therefore cannot create directories in them which means that
 empty directories on a bucket based remote will tend to disappear.
 .PP
 Some software creates empty keys ending in \f[C]/\f[R] as directory
 markers.
-Rclone doesn\[cq]t do this as it potentially creates more objects and
+Rclone doesn\[aq]t do this as it potentially creates more objects and
 costs more.
-It may do in future (probably with a flag).
+This ability may be added in the future (probably via a flag/option).
 .SS Bugs
 .PP
-Bugs are stored in rclone\[cq]s GitHub project:
+Bugs are stored in rclone\[aq]s GitHub project:
 .IP \[bu] 2
 Reported
 bugs (https://github.com/rclone/rclone/issues?q=is%3Aopen+is%3Aissue+label%3Abug)
@@ -38734,7 +36872,7 @@ Eg
 .IP
 .nf
 \f[C]
-rclone sync drive:Folder s3:bucket
+rclone sync \-i drive:Folder s3:bucket
 \f[R]
 .fi
 .SS Using rclone from multiple locations at the same time
@@ -38744,13 +36882,13 @@ different subdirectory for the output, eg
 .IP
 .nf
 \f[C]
-Server A> rclone sync /tmp/whatever remote:ServerA
-Server B> rclone sync /tmp/whatever remote:ServerB
+Server A> rclone sync \-i /tmp/whatever remote:ServerA
+Server B> rclone sync \-i /tmp/whatever remote:ServerB
 \f[R]
 .fi
 .PP
 If you sync to the same directory then you should use rclone copy
-otherwise the two instances of rclone may delete each other\[cq]s files,
+otherwise the two instances of rclone may delete each other\[aq]s files,
 eg
 .IP
 .nf
@@ -38763,7 +36901,7 @@ Server B> rclone copy /tmp/whatever remote:Backup
 The file names you upload from Server A and Server B should be different
 in this case, otherwise some file systems (eg Drive) may make
 duplicates.
-.SS Why doesn\[cq]t rclone support partial transfers / binary diffs like rsync?
+.SS Why doesn\[aq]t rclone support partial transfers / binary diffs like rsync?
 .PP
 Rclone stores each file you transfer as a native object on the remote
 cloud storage system.
@@ -38772,9 +36910,9 @@ alternative access methods (eg using the Google Drive web interface).
 There is a 1:1 mapping between files on your hard disk and objects
 created in the cloud storage system.
 .PP
-Cloud storage systems (at least none I\[cq]ve come across yet) don\[cq]t
+Cloud storage systems (at least none I\[aq]ve come across yet) don\[aq]t
 support partially uploading an object.
-You can\[cq]t take an existing object, and change some bytes in the
+You can\[aq]t take an existing object, and change some bytes in the
 middle of it.
 .PP
 It would be possible to make a sync system which stored binary diffs
@@ -38828,7 +36966,7 @@ export HTTPS_PROXY=$http_proxy
 The \f[C]NO_PROXY\f[R] allows you to disable the proxy for specific
 hosts.
 Hosts must be comma separated, and can contain domains or parts.
-For instance \[lq]foo.com\[rq] also matches \[lq]bar.foo.com\[rq].
+For instance \[dq]foo.com\[dq] also matches \[dq]bar.foo.com\[dq].
 .PP
 e.g.
 .IP
@@ -38842,7 +36980,7 @@ export NO_PROXY=$no_proxy
 Note that the ftp backend does not support \f[C]ftp_proxy\f[R] yet.
 .SS Rclone gives x509: failed to load system roots and no roots provided error
 .PP
-This means that \f[C]rclone\f[R] can\[cq]t file the SSL root
+This means that \f[C]rclone\f[R] can\[aq]t file the SSL root
 certificates.
 Likely you are running \f[C]rclone\f[R] on a NAS with a cut\-down Linux
 OS, or possibly on Solaris.
@@ -38876,7 +37014,7 @@ package (https://godoc.org/crypto/x509), provide an additional way to
 provide the SSL root certificates.
 .PP
 Note that you may need to add the \f[C]\-\-insecure\f[R] option to the
-\f[C]curl\f[R] command line if it doesn\[cq]t work without.
+\f[C]curl\f[R] command line if it doesn\[aq]t work without.
 .IP
 .nf
 \f[C]
@@ -38893,10 +37031,10 @@ docs (https://golang.org/doc/install) for full details.
 .SS All my uploaded docx/xlsx/pptx files appear as archive/zip
 .PP
 This is caused by uploading these files from a Windows computer which
-hasn\[cq]t got the Microsoft Office suite installed.
+hasn\[aq]t got the Microsoft Office suite installed.
 The easiest way to fix is to install the Word viewer and the Microsoft
 Office Compatibility Pack for Word, Excel, and PowerPoint 2007 and later
-versions\[cq] file formats
+versions\[aq] file formats
 .SS tcp lookup some.domain.com no such host
 .PP
 This happens when rclone cannot resolve a domain.
@@ -38926,7 +37064,7 @@ It is likely you have more than 10,000 files that need to be synced.
 By default rclone only gets 10,000 files ahead in a sync so as not to
 use up too much memory.
 You can change this default with the
-\[en]max\-backlog (https://rclone.org/docs/#max-backlog-n) flag.
+\-\-max\-backlog (https://rclone.org/docs/#max-backlog-n) flag.
 .SS Rclone is using too much memory or appears to have a memory leak
 .PP
 Rclone is written in Go which uses a garbage collector.
@@ -39342,7 +37480,8 @@ bsteiss <35940619+bsteiss@users.noreply.github.com>
 .IP \[bu] 2
 C\['e]dric Connes <cedric.connes@gmail.com>
 .IP \[bu] 2
-Dr.\ Tobias Quathamer <toddy15@users.noreply.github.com>
+Dr.
+Tobias Quathamer <toddy15@users.noreply.github.com>
 .IP \[bu] 2
 dcpu <42736967+dcpu@users.noreply.github.com>
 .IP \[bu] 2
@@ -39718,6 +37857,70 @@ Martin Michlmayr <tbm@cyrius.com>
 Brandon McNama <bmcnama@pagerduty.com>
 .IP \[bu] 2
 Daniel Slyman <github@skylayer.eu>
+.IP \[bu] 2
+Alex Guerrero <guerrero@users.noreply.github.com>
+.IP \[bu] 2
+Matteo Pietro Dazzi <matteopietro.dazzi@gft.com>
+.IP \[bu] 2
+edwardxml <56691903+edwardxml@users.noreply.github.com>
+.IP \[bu] 2
+Roman Kredentser <shareed2k@gmail.com>
+.IP \[bu] 2
+Kamil Trzci\[u0144]ski <ayufan@ayufan.eu>
+.IP \[bu] 2
+Zac Rubin <z-0@users.noreply.github.com>
+.IP \[bu] 2
+Vincent Feltz <psycho@feltzv.fr>
+.IP \[bu] 2
+Heiko Bornholdt <bornholdt@informatik.uni-hamburg.de>
+.IP \[bu] 2
+Matteo Pietro Dazzi <matteopietro.dazzi@gmail.com>
+.IP \[bu] 2
+jtagcat <gitlab@c7.ee>
+.IP \[bu] 2
+Petri Salminen <petri@salminen.dev>
+.IP \[bu] 2
+Tim Burke <tim.burke@gmail.com>
+.IP \[bu] 2
+Kai L\[:u]ke <kai@kinvolk.io>
+.IP \[bu] 2
+Garrett Squire <github@garrettsquire.com>
+.IP \[bu] 2
+Evan Harris <eharris@puremagic.com>
+.IP \[bu] 2
+Kevin <keyam@microsoft.com>
+.IP \[bu] 2
+Morten Linderud <morten@linderud.pw>
+.IP \[bu] 2
+Dmitry Ustalov <dmitry.ustalov@gmail.com>
+.IP \[bu] 2
+Jack <196648+jdeng@users.noreply.github.com>
+.IP \[bu] 2
+kcris <cristian.tarsoaga@gmail.com>
+.IP \[bu] 2
+tyhuber1 <68970760+tyhuber1@users.noreply.github.com>
+.IP \[bu] 2
+David Ibarra <david.ibarra@realty.com>
+.IP \[bu] 2
+Tim Gallant <tim@lilt.com>
+.IP \[bu] 2
+Kaloyan Raev <kaloyan@storj.io>
+.IP \[bu] 2
+Jay McEntire <jay.mcentire@gmail.com>
+.IP \[bu] 2
+Leo Luan <leoluan@us.ibm.com>
+.IP \[bu] 2
+aus <549081+aus@users.noreply.github.com>
+.IP \[bu] 2
+Aaron Gokaslan <agokaslan@fb.com>
+.IP \[bu] 2
+Egor Margineanu <egmar@users.noreply.github.com>
+.IP \[bu] 2
+Lucas Kanashiro <lucas.kanashiro@canonical.com>
+.IP \[bu] 2
+WarpedPixel <WarpedPixel@users.noreply.github.com>
+.IP \[bu] 2
+Sam Edwards <sam@samedwards.ca>
 .SH Contact the rclone project
 .SS Forum
 .PP
@@ -39726,7 +37929,7 @@ Forum for questions and general discussion:
 https://forum.rclone.org
 .SS GitHub repository
 .PP
-The project\[cq]s repository is located at:
+The project\[aq]s repository is located at:
 .IP \[bu] 2
 https://github.com/rclone/rclone
 .PP
@@ -39740,7 +37943,7 @@ You can also follow me on twitter for rclone announcements:
 .PP
 Or if all else fails or you want to ask something private or
 confidential email Nick Craig\-Wood (mailto:nick@craig-wood.com).
-Please don\[cq]t email me requests for help \- those are better directed
+Please don\[aq]t email me requests for help \- those are better directed
 to the forum.
 Thanks!
 .SH AUTHORS