Files are reusable ConverterHQ assets. Large binaries move directly between your client and ConverterHQ object storage; the API control plane handles metadata while signed transfers carry the file bytes.
Create a File
Create the resource first, upload using the returned signed plan, then complete it. Official SDKs perform these steps automatically.
Large uploads
Multipart uploads split large objects into independently retryable parts and verify completion/checksums before the File becomes ready.
Downloads
Output Files expose short-lived signed GET URLs. Generate a new URL when an old one expires; the durable object is the File ID.
Deletion
Deleting a File revokes future signed access and removes its binary payload. Billing/audit metadata may remain where required, but never as a hidden retained copy of the user file.