Transfer folders with desktop resume
Sends whole folders and keeps their structure. Resumes big transfers after sleep, restarts and dropped connections. Use the desktop app when a folder delivery needs to survive an interrupted connection.
For teams moving project folders, image sequences and other deliveries made of many files.
Business use only
What you need
The desktop app is free on every plan. Sending needs an account. The CLI is included with every registered account; recipients can use the desktop app without signing in.
The workflow
1
Select the complete project folder
Choose the folder in the desktop app. Keep its contents and location stable while uploading. Upload regular files; symbolic links are skipped, and empty directories are not a way to carry folder structure.
2
Retry the same selection after an interruption
After a retryable failure or relaunch, select the same source files and transfer details. The client checks saved progress and already uploaded parts before sending missing data. Re-enter a transfer password if you originally set one.
3
Receive into a stable destination
Open the transfer link in the desktop app and choose a folder with enough free space. To resume an interrupted download, keep its partial files and checkpoints and select the same destination. Reconnect an external drive before retrying.
CLI: inspect a folder locally, then send it
yasync push ./Project --dry-run
yasync login
yasync push ./Project --title "Project handoff"Use the verified desktop and CLI downloads. CLI reference and authentication.
Before your first delivery
Resume has conditions
A transfer still needs an available source, a valid transfer and unchanged file contents. Moving files, editing them during upload, removing partial downloads or changing the destination can prevent recovery. Current desktop and CLI folder sends retain upload progress when stopped; keep the same files and transfer details to resume.
Use the right tool for a changing folder
A normal folder send is a selected delivery, not a continuing sync. For newly completed renders that keep arriving, use a watch folder. Watch delivery does not propagate deletions or edit files already delivered.
Start with a representative folder
Before a deadline, send and receive a small copy that includes your nested paths and typical filenames. Confirm that the destination has the expected structure and that the recipient can open the files.
Common questions
Will browser and desktop resume behave identically?
Use desktop resume for workflows that must recover after app or machine restarts. A browser tab has different file-access and download constraints; do not assume a browser retry will recover a desktop checkpoint.
Does folder transfer synchronize later changes?
No. Send another delivery for later changes, or run a watch folder to append newly completed or changed files.