The high-volume image upload playbook
How to structure folders, choose transfer methods, recover interruptions and prove a large catalogue arrived intact.
Reading time9 minute guide
Written forStudio producers, ecommerce operations and DAM teams
FormatOperating guide and checklist
Updated20 August 2026
Organise before transfer
Use one order or batch identifier, stable SKU folders and a simple source manifest. Separate selects, holds and references so production never interprets a folder name as an instruction.
Choose the route by source system
Use browser multipart transfer for local files, folder upload for a complete shoot structure, and secure HTTPS imports for cloud-hosted originals. Avoid forwarding private sources through ordinary email.
Design for interruption
Large-file transfer should retry failed chunks instead of restarting the entire file. Keep the device awake, avoid renaming files during transfer and verify per-file completion rather than trusting one overall progress bar.
Reconcile against a manifest
Compare expected and received counts, filenames, sizes and rejected formats before production. Resolve duplicates and missing views while the shoot context is still available.
Questions teams ask before production.
01How large can local files be?＋
The Rupato multipart route is designed for files up to 20 GB, although practical limits also depend on the browser, connection and source format.
02Should a huge catalogue be one order?＋
Split by a useful operational boundary such as campaign, category, shoot day or deadline—not arbitrary file counts.
03Can cloud links be imported?＋
Yes when they resolve to a secure downloadable file and the provider permits server-side access.
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 ↗