Send a large batch without restarting failed files
Use multipart device transfer, folder upload or secure-link import and verify every source before production.
CategoryUploads and transfers
Steps4
Checklist6 verification points
Need help?Use workspace support
Choose the transfer method
Use device files for selected sources, folder upload for complete structures and secure links for accessible cloud originals.
Keep the batch stable
Do not rename or move local files while they are transferring. Keep the browser and device awake.
Retry only failed parts
Multipart transfer breaks large files into chunks and retries failed parts instead of restarting completed data.
Reconcile received files
Compare expected count, filenames and rejected formats before confirming production.
Questions teams ask before production.
01What is the local-file limit?＋
The current multipart route supports up to 20 GB per local file.
02Can I upload a folder?＋
Yes, using a browser that supports folder selection.
03What if the browser closes?＋
Completed assets remain recorded, but remaining local files may need to be selected again.
ONE ORDER OR A COMPLETE CATALOGUE
Make the brief clear before the first file moves.
Rupato keeps uploads, specifications, tasks, review and delivery attached to the same production record.
Start an order ↗