Uloz.to
At a glance
Section titled “At a glance”| Capability | Support |
|---|---|
| rclone support tier | Tier 3: Supported |
| Checksums | MD5, SHA-256 |
| Modification times | Kept, to 1 µs |
| Case-insensitive names | No |
| Duplicate names allowed | Yes |
| Server-side copy | No |
| 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 | No |
| Public links | No |
The initial setup for Uloz.to involves filling in the user credentials.
rclone config walks you through it.
Setup notes
Section titled “Setup notes”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.
User credentials
Section titled “User credentials”The only reliable method is to authenticate the user using username and password. Uloz.to offers an API key as well, but it’s reserved for the use of Uloz.to’s in-house application and using it in different circumstances is unreliable.
Modification times and hashes
Section titled “Modification times and hashes”Uloz.to doesn’t allow the user to set a custom modification time, or retrieve the hashes after upload. As a result, the integration uses a free form field the API provides to encode client-provided timestamps and hashes. Timestamps are stored with microsecond precision.
A server calculated MD5 hash of the file is verified upon upload.
Afterwards, the backend only serves the client-side calculated
hashes. Hashes can also be retrieved upon creating a file download
link, but it’s impractical for list-like use cases.
Restricted filename characters
Section titled “Restricted filename characters”In addition to the default restricted characters set the following characters are also replaced:
| Character | Value | Replacement |
|---|---|---|
| \ | 0x5C | ＼ |
Invalid UTF-8 bytes will also be replaced, as they can’t be used in JSON strings.
Transfers
Section titled “Transfers”All files are currently uploaded using a single HTTP request, so
for uploading large files a stable connection is necessary. Rclone will
upload up to --transfers chunks at the same time (shared among all
uploads).
Deleting files
Section titled “Deleting files”By default, files are moved to the recycle bin whereas folders are deleted immediately. Trashed files are permanently deleted after 30 days in the recycle bin.
Emptying the trash is currently not implemented in rclone.
Root folder ID
Section titled “Root folder ID”You can set the root_folder_slug for rclone. This is the folder
(identified by its Folder slug) that rclone considers to be the root
of your Uloz.to 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 slug of the
folder you wish to use as root. This will be the last segment
of the URL when you open the relevant folder in the Uloz.to web
interface.
For example, for exploring a folder with URL
https://uloz.to/fm/my-files/foobar, foobar should be used as the
root slug.
root_folder_slug can be used alongside a specific path in the remote
path. For example, if your remote’s root_folder_slug corresponds to /foo/bar,
remote:baz/qux will refer to ABSOLUTE_ULOZTO_ROOT/foo/bar/baz/qux.
Options
Section titled “Options”Standard options
Section titled “Standard options”The wizard asks for these when you add the drive.
app_token
Section titled “app_token”The application token identifying the app. An app API key can be either found in the API doc https://uloz.to/upload-resumable-api-beta or obtained from customer service.
Type: string
username
Section titled “username”The username of the principal to operate as.
Type: string
password
Section titled “password”The password for the user.
NB Input to this must be obscured - see rclone obscure.
Type: string
Advanced options
Section titled “Advanced options”The wizard shows these under Advanced options. Most drives work without changing any of them.
root_folder_slug
Section titled “root_folder_slug”If set, rclone will use this folder as the root folder for all operations. For example, if the slug identifies ‘foo/bar/’, ‘ulozto:baz’ is equivalent to ‘ulozto:foo/bar/baz’ without any root slug set.
Type: string
list_page_size
Section titled “list_page_size”The size of a single page for list commands. 1-500
Type: int · Default: 500
encoding
Section titled “encoding”The encoding for the backend.
See the encoding section in the overview for more info.
Type: Encoding · Default: Slash,BackSlash,Del,Ctl,InvalidUtf8,Dot
description
Section titled “description”Description of the remote.
Type: string
Limitations
Section titled “Limitations”Uloz.to file names can’t have the \ character in. rclone maps this to
and from an identical looking unicode equivalent ＼ (U+FF3C Fullwidth
Reverse Solidus).
Uloz.to only supports filenames up to 255 characters in length.
Uloz.to rate limits access to the API, but exact details are undisclosed. Practical testing reveals that hitting the rate limit during normal use is very rare, although not impossible with higher number of concurrently uploaded files.
rclone about is not supported by the Uloz.to backend. Although
there’s an endpoint to retrieve the information for the UI, it’s not
exposed in the API. Backends without this capability cannot determine
free space for an rclone mount or use policy mfs (most free space)
as a member of an rclone union remote.
See List of backends that do not support rclone about and rclone about.