Skip to content

Yandex Disk

Capability Support
rclone support tier Tier 1: Core
Checksums MD5
Modification times Kept, to 1 ns
Case-insensitive names No
Duplicate names allowed No
Server-side copy Yes
Server-side move and rename Yes
Folder move and rename Yes, in one step
Free space reporting Yes
Empty folders Yes
Change notifications No
Uploads of unknown size Yes
Public links Yes

Yandex Disk is a cloud storage solution created by Yandex.

In CloudMount you add this drive from the Add drive screen, and the wizard asks for the options listed under Options. The notes below come from rclone’s setup guide.

Modified times are supported and are stored accurate to 1 ns in custom metadata called rclone_modified in RFC3339 with nanoseconds format.

The MD5 hash algorithm is natively supported by Yandex Disk.

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.

To view your current quota you can use the rclone about remote: command which will display your usage limit (quota) and the current usage.

The default restricted characters set are replaced.

Invalid UTF-8 bytes will also be replaced, as they can’t be used in JSON strings.

The wizard asks for these when you add the drive.

OAuth Client Id.

Leave blank normally.

Type: string

OAuth Client Secret.

Leave blank normally.

Type: string

The wizard shows these under Advanced options. Most drives work without changing any of them.

OAuth Access Token as a JSON blob.

Type: string

Auth server URL.

Leave blank to use the provider defaults.

Type: string

Token server url.

Leave blank to use the provider defaults.

Type: string

Use client credentials OAuth flow.

This will use the OAUTH2 client Credentials Flow as described in RFC 6749.

Note that this option is NOT supported by all backends.

Type: bool · Default: false

Delete files permanently rather than putting them into the trash.

Type: bool · Default: false

The encoding for the backend.

See the encoding section in the overview for more info.

Type: Encoding · Default: Slash,Del,Ctl,InvalidUtf8,Dot

Set the user agent to match an official version of the yandex disk client. May help with upload performance.

Type: bool · Default: true

Wait this long after an upload before setting the modification time.

Yandex Disk finalizes an upload asynchronously on its servers after the upload has completed. If the modification time is set while this finalization is still in progress the server returns 500 Internal Server Error errors.

If you are getting 500 errors on upload then setting this to 2s is normally enough to stop them, at the cost of slowing down uploads.

Yandex support recommend a value of 1.5s - 3s.

Type: Duration · Default: 0s

Description of the remote.

Type: string

When uploading very large files (bigger than about 5 GiB) you will need to 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 errors in the logs if this is happening. Setting the timeout to twice the max size of file in GiB should be enough, so if you want to upload a 30 GiB file set a timeout of 2 * 30 = 60m, that is --timeout 60m.

If you get 500 Internal Server Error errors just after uploads, particularly when uploading many files in parallel, then try setting --yandex-upload-wait 2s. Yandex Disk finalizes uploads asynchronously on its servers and can report an upload as complete slightly before the file is ready, so accessing the file’s metadata too soon causes these errors. Yandex support recommend waiting 1.5s - 3s after each upload.

Having a Yandex Mail account is mandatory to use the Yandex.Disk subscription. Token generation will work without a mail account, but Rclone won’t be able to complete any actions.

[403 - DiskUnsupportedUserAccountTypeError] User account type is not supported.