Bottom Line: Treat a Stuck Files Progress Bar and a Failed Cloud Copy as Two Separate Problems
The 2024 thread exposed both. Dropbox transfers could genuinely stop, while the Files UI could also keep showing an old canceled task, lose progress after refresh or hide concurrent operations. That distinction matters because refreshing the browser can change what you see without changing the underlying transfer, and retrying the copy can create duplicate work.
Start by Classifying the Transfer Path
Write down the exact source and destination:
- Cloud → ZimaOS local storage
- ZimaOS local storage → Cloud
- Local ZimaOS folder → another local folder
- SMB client → ZimaOS
Current ZimaOS cloud-drive support treats Google Drive, Dropbox and OneDrive as mounted sources that can move data to and from local storage. The modern workflow is much broader than the early 1.2.x implementation described in the thread.
The ZimaOS cloud drives is the current product baseline.
Check Destination Capacity Before Retrying a Large Copy
df -h
du -sh /media/DESTINATION/TARGETA cloud transfer can fail partway through when the destination fills, an external disk disconnects or a mounted path changes. Confirm free space and destination stability before assuming the provider API is broken. If the data matters, copy rather than move until the destination is verified.
For Large Cloud Libraries, Use Smaller Batches and Verify Each Batch
The original 1.2.x/1.3.x reports were especially unreliable on large-scale cloud transfers. Current ZimaOS has improved that path, but large libraries are still easier to validate when moved in logical batches. Copy one top-level folder, verify file count/size and open representative files before starting the next.
Google Drive's resumable upload model and Dropbox's Dropbox transfer patterns illustrate why large cloud transfers need retryable, stateful operations.
Do Not Use Browser Refresh as a Transfer-Control Mechanism
In the old Files design, progress state lived partly in the loaded web session and could disappear after refresh even while server-side work continued. The UI also showed only one operation even when several were running. Therefore, when a progress card looks stale, do not immediately paste the same folder again. First inspect the destination and wait for disk/network activity to settle.
Canceling a Transfer May Not Be Instant
IceWhale explained that the old cancellation mechanism could need the current file to finish before the task actually stopped. That means “Cancel clicked” and “backend stopped” were not always identical states. For large individual files, give the active file enough time to close cleanly before launching a replacement job.
Finder or SMB Can Be Better for Mac Metadata
The original author eventually preferred Mac Finder over ZimaOS Files because Finder tags and some metadata did not survive the browser copy workflow the way they expected. If macOS metadata matters, direct SMB can be a better local transfer path than routing the copy through a browser/cloud abstraction.
The NAS file sharing provides the local-file alternative.
Current Cloud Support Does Not Mean Every Provider Exists
Do not infer iCloud or Box support from old marketing images or feature requests. Use the providers listed in the current ZimaOS Cloud Drive interface and documentation. If a provider is not present, use that provider's supported sync/export mechanism or a deliberate third-party tool rather than inventing an unofficial mount.
Back Up Before You Turn a Migration Into a Move
For irreplaceable data, the safe order is copy → verify → back up → delete the source later. The ZimaOS backup is a better safety layer than relying on one browser transfer. If application data is being moved rather than ordinary files, use the ZimaOS data migration instead of a manual Files copy.
FAQ
Why does the Files progress bar get stuck?
A stale UI state and a genuinely stuck backend transfer are different possibilities. Check destination activity before retrying the same copy.
Can I refresh the browser during a copy?
A modern transfer may continue, but refreshing can remove or reset client-side progress information. Avoid using refresh as a way to control the job.
Why do large cloud copies fail more often?
Long transfers expose provider throttling, network interruptions, disk-full conditions and retry logic. Smaller verified batches are easier to recover.
Does ZimaOS support iCloud Drive?
Do not assume so from old product imagery. Use the providers currently listed in ZimaOS Cloud Drive settings and current documentation.
Should I use Files or SMB on a Mac?
Use SMB/Finder when local performance and Mac filesystem metadata matter. Use Files when the browser/cloud workflow is the feature you need.
