ConverterHQDevelopers
Documentation

Large files and multipart uploads

Move large binaries efficiently with signed direct uploads, multipart recovery and checksum verification.

Do not proxy multi-gigabyte files through your application server unless your architecture specifically requires it. ConverterHQ can separate API metadata from file transfer so binaries move directly to object storage.

Transfer strategy

Create a File resource, obtain its upload plan and send bytes directly to the signed destination. The File becomes eligible for processing only after upload completion is confirmed.

Multipart lifecycle

  1. Create the File and multipart upload.
  2. Request signed part uploads in bounded batches.
  3. Upload parts concurrently within your own network limits.
  4. Persist returned ETags/checksums.
  5. Complete the multipart upload with the ordered part manifest.

Failure recovery

Retry only failed parts. Persist the File/upload identifiers so a process restart does not require restarting the entire transfer. Abort abandoned uploads and enforce a client-side maximum retry horizon.

Output downloads

Output Files expose short-lived signed download URLs. Treat the File ID as durable and the URL as disposable. Generate a fresh URL when one expires rather than persisting the signed URL permanently.