Automate render delivery with a watch folder
Sends new or changed files from a folder as soon as they're complete. Deliver output incrementally rather than waiting to assemble one final folder.
For render operators, finishing teams and automation engineers delivering output while a job runs.
Business use only
What you need
Watching into your own account and live incoming downloads are included with every registered account. A sender can watch into someone else’s paid upload link without a sender account.
The workflow
1
Create a dedicated delivery folder
Point the watcher at completed deliverables, not the working directory of a renderer that repeatedly changes files. Finish each export elsewhere on the same filesystem, then atomically move it into the watched folder.
2
Start the watcher
Sign in and start watching the folder with a recognizable title. Leave the app or CLI running. The watcher waits for unchanged size and modification time across consecutive scans before uploading a regular file.
3
Receive verified files as they arrive
The account that owns the watch package can use incoming downloads to save completed files while a package remains open. Keep that receiver running too. Stop the watcher when delivery is finished; completed files stay, and unfinished uploads are aborted.
CLI: watch output and receive incoming packages on another signed-in machine
yasync login
yasync watch ./Delivery --title "Night renders"
# On another machine, signed in to the same account:
yasync incoming -o ./IncomingUse the verified desktop and CLI downloads. CLI reference and authentication.
Before your first delivery
Append deliveries, not bidirectional sync
A changed file becomes a new immutable uploaded object. Deleting a local file does not delete an earlier delivery, and a watcher does not reconcile two editing folders. Use titles and filenames that distinguish versions.
File stability is not export completion
A writer may pause long enough to pass a stability check and then continue. Moving a finished file into the folder is the dependable handoff. Symlinks and known metadata files are skipped; files changed during upload fail verification rather than publishing unverified bytes.
Handle a disconnected sender
Watch sessions allow a bounded connection-loss grace period. Once the session closes, it cannot be revived by a late heartbeat; restart the sender as a new session. Watch delivery is not an unattended backup service.
Common questions
Can I watch into a client’s upload link?
Yes. Use yasync watch with --upload-link and the supplied yasync upload URL. Enter its password when required. Files go to the account that owns the link, and the sender does not receive a public download link.
Can the recipient start before the whole render job finishes?
The owner can receive each completed, verified incoming file while its package is still open. Ordinary public download links become available after a normal transfer is finalized.