Seafile WebDAV vs the REST API: What to Use for Transfers

Seafile keeps files in libraries. Outside its own apps, you can reach them through WebDAV, which an administrator has to switch on. The alternative is Seafile's web API, which is what Blober uses. For a few hundred gigabytes, the choice decides how much setup and waiting you have.

• WebDAV is off until an administrator turns it on. Seafile's manual says "By default, seafdav is disabled" and tells you to check for enabled = true in seafdav.conf^[1]. If you do not run the server, you need to ask the administrator.
• Seafile's manual calls WebDAV slow for many files. It says that uploading a large number of files at once is "usually much slower than the syncing client", and that WebDAV is "more suitable for infrequent file access"^[2].
• The manual points to the sync client for speed. It says "If you want better performance, please use the sync client instead"^[3]. The sync client syncs a library with a folder on your computer^[4], so a move to another cloud takes a second step.
• rclone has a Seafile backend that supports two-factor accounts and encrypted libraries^[5]. It is a terminal tool, so you work with a config file and read the errors yourself.

Blober does not use WebDAV. You sign in on Seafile's own page, and Blober works with your libraries through Seafile's web API. Nothing has to be turned on at the server, and nobody has to be asked.

• Libraries: your own libraries, libraries shared with you and group libraries appear as the top level. When two libraries have the same name, Blober adds the first characters of the library ID to each name.
• Seafile to another cloud: files go from your server through your computer to the destination.
• Another cloud into Seafile: files upload to the library you choose, and Blober creates missing folders.
• Inside Seafile: copy and move happen on the server, including between libraries, so reorganizing an account uses none of your bandwidth.
• Deduplication: the default skips a file whose name already exists, so running a workflow again does not copy files twice.
• Folder structure: a path template sorts files into folders while they move.

1. Add Seafile with your server address and sign in on Seafile's own page. The Seafile setup guide covers it.
2. Create a workflow with Seafile on one side and the other cloud on the other side.
3. Run it and watch the Progress page. If a file fails, retry it from the task without repeating the whole transfer.

• Encrypted libraries are listed as read-only. Blober cannot open them.
• Blober cannot create libraries. Create the library in the Seafile web app first.
• A library where you have read-only access cannot be a destination.
• Deleted files go to the library trash in Seafile, where you can restore them^[6].
• When your Seafile sign-in expires, Blober opens the Seafile sign-in window. Sign in, and the task goes on.

Do I need to enable WebDAV on the server? No. Blober does not use WebDAV. If you already run WebDAV for something else, it stays as it is.

Why not use rclone? You can. rclone has a Seafile backend^[7]. Blober suits you if you prefer to pick folders in a window and watch the progress, with no config file.

Can two libraries have the same name? Yes. Blober adds the first characters of each library's ID to its name. In the Seafile web app the names stay the same, so match on the ID.

Does Blober see my Seafile password? No. You type it on Seafile's own page.

Does copying inside Seafile move any data through my computer? No. Seafile does the copy or move itself, including between libraries.

• Seafile setup guide
• Server-to-server vs download-and-reupload
• Blober vs rclone
• Moving between OneDrive and Google Drive