Seafile FAQ

Seafile stores file versions based on the version history settings configured per library. You can set this to a number of days (e.g., 365) or keep versions indefinitely.

Seafile uses interval-based versioning. Multiple changes within a short period (default is 1 hour) are saved as a single version. Tags do not trigger new versions.

Yes. You can right-click the file in the Web UI, select “History” or “Versions”, and restore any previous version, provided versioning is enabled.

Tags are saved with the version they are applied to but do not create a new version on their own.

This section shows file creation, renaming, and deletion events. Modifications and downloads are not shown here.

Enable audit logging in seafile.conf with enable_audit = true. Then use the System Admin panel or audit logs to see detailed access history.

Yes, if audit logging is enabled. Viewing, downloading, uploading, deletion, and sharing actions are recorded.

For most environments, performance impact is minimal. However, it increases database writes and storage usage in large or high-traffic setups.

Audit logs grow over time and should be managed with log rotation or cleanup policies to avoid excessive disk usage.

A locked file prevents other users from modifying it. The locker can still make changes. Others see a lock icon and may be restricted.

Yes. The lock applies only to other users, not to the one who initiated it.

Yes. It prevents conflicting edits by restricting write access to all but the locking user.

The client uses auto-lock during editing, which is removed when the file is closed. The Web UI shows manual locks until manually cleared.

Yes, but it may cause conflicts. Use manual or auto-locking to prevent overlapping edits.

No. Due to browser restrictions, users must select “Open via Client” to open files in desktop applications.

Yes. This is necessary for the Web UI to securely hand off the file to the Seafile desktop client.

“My Libraries” shows libraries you own. “Shared with me > My Library” appears if your own library is shared back to you via a group or team rule.

Because it is still your own library with write permissions. The view is just a shared context.

Yes. You can disable library creation. Please contact your Seafile admin or service provider.

Disable personal libraries in Seafile and direct users to use OneDrive via policy and documentation.

The upload will hang in the Web UI without a proper error. The server blocks the upload but doesn’t show a message.

This is a known UI limitation. The server rejects the upload silently due to read-only permissions.

The client allows local changes, but sync fails due to lack of write permission. The changes remain visible locally until refreshed.

We recommend using daily server snapshots retained for 7 days.

Typically 7 days, assuming daily snapshot schedules.

Yes. The cost depends on the size of the disk to be backed up. We can provide an estimate based on your specific setup. Various backup options are available at different price points—for example, snapshots, which allow for rapid entire server restores but are more expensive, and standard backups to object storage, which are much more cost-efficient but have longer restore times. Please note that this refers to full server recovery; file-level restore is handled instantly by Seafile and does not relate to the full server backup.

Because Seafile already retains file version history (e.g., 365 days or more), so restoring from any recent snapshot gives access to all prior data.

Yes. Version history is stored inside Seafile, separate from server-level backups.

Yes. Users can access the “Deleted Files” section in the library’s history and restore files directly.

In the Web UI, open the library and use the “History” or “Deleted Files” button to view and restore deleted items.

As long as the file history retention is active — e.g., 365 days or unlimited, depending on admin settings.

Yes, we can define custom roles that can be assigned to individual users or groups. These roles can include specific restrictions—such as disabling the ability to create external share links—to align with your organization’s policies.