[Feature] Temporary option to skip large files in mobile auto-backup (configurable size threshold)

[XTAI9]

I have searched the existing feature requests, both open and closed, to make sure this is not a duplicate request.

• Yes

The feature

Description

Currently, the mobile app’s automatic backup attempts to upload all selected assets, including large videos that frequently fail when the server is behind Cloudflare Tunnel (100 MB free-tier limit) or certain reverse-proxy configurations (nginx default limits, etc.).

These failures often result in:

• Repeated failed upload attempts
• Wasted mobile data and battery
• Background workers being killed by the OS
• Poor user experience (no clear feedback why the upload keeps failing)

While proper chunked / resumable uploads are already planned (#1674, PR #22385), they are still blocked by technical challenges (especially iOS + Cloudflare interaction).

Proposed temporary solution

Add a configurable option in the mobile app’s Backup Settings:

1. Skip files larger than X MB (default suggestion: 80–100 MB, user-adjustable).
2. Files that exceed the threshold are not automatically backed up.
3. Optional but highly useful:
   • Show these skipped large files in a dedicated “Large files / Pending” section (or filter) inside the app, so users can easily review and manage them later.
4. Allow the user to:
   • Manually force-upload individual or selected large files
   • Temporarily or permanently disable the size limit

Benefits

• Prevents repeated failed uploads and data/battery waste before chunked upload is ready.
• Gives users control over large video uploads (especially useful for people using Cloudflare free tier).
• Reduces unnecessary load on the server and reverse proxy.
• Complements existing controls (album selection + “Backup videos” toggle) without being as coarse-grained.
• Low implementation complexity on the client side (size is already available during scanning/hashing).

Implementation notes (suggestions)

• Client-side only filter during the backup candidate selection / hashing phase.
• Persist the skipped status locally so the same files are not re-attempted every time.
• Clear user-facing messaging when a file is skipped because of the size limit.
• Optionally improve error detection for 413 / payload-too-large responses and surface a helpful tip.

Related

• Original feature request for chunked/resumable uploads: [Feature]: Upload large files in chunks #1674
• Current server-side PR: feat(server): resumable uploads #22385
• Multiple user reports of large video backup failures (especially with Cloudflare)

This is intended as a temporary / transitional mitigation until proper chunked uploads land. Once chunked uploads are available, this option can remain as an additional safety/control feature or be simplified.

Would the team be open to this as a relatively lightweight improvement in the meantime?

Platform

• Server
• Web
• Mobile

[bo0tzz]

#6914

[XTAI9]

Hi, I just found this discussion and wanted to expand on the idea a bit, since it still seems very relevant.

The original request (manually marking individual files to skip via context menu) is already useful. I’d like to propose a more systematic version that could solve the same problem for more people, especially those behind Cloudflare or reverse proxies with upload size limits:

Suggested enhancement:

1. Add a setting in the mobile app’s Backup Settings:

   • “Skip files larger than X MB” (user-configurable threshold, e.g. default 80–100 MB to work around Cloudflare free tier).

2. Files that exceed the threshold are automatically excluded from auto-backup.

3. Optionally show these skipped large files in a dedicated section / filter (e.g. “Large files / Pending”) so users can easily review them later.

4. Still allow:

   • Manually force-upload individual or selected large files
   • Temporarily or permanently disable the size limit

Why this would help:

• Prevents the app from repeatedly trying (and failing) to upload large videos when the server is behind Cloudflare (100 MB limit) or certain nginx configurations.
• Saves mobile data, battery, and avoids background workers being killed.
• Gives users control without having to manually mark every large file one by one.
• Acts as a practical temporary mitigation while we wait for proper chunked / resumable uploads ([Feature]: Upload large files in chunks #1674 / PR feat(server): resumable uploads #22385).

This would complement the original “manual skip” idea rather than replace it. The context-menu option could still be useful for one-off cases, while the size threshold handles the common “large video keeps failing” scenario automatically.

Would the team consider this as an enhancement to the original request?

Thanks!