Guide
Upload and Resume Private Delivery Files
Prepare files up to 10 GB each, recover interrupted local uploads, and import direct download links.
Delivery files up to 10 GB each
Each private delivery file can be up to 10 GB (10,000,000,000 bytes). Local multipart uploads retry interrupted parts. After a page reload, reselect the same file to reuse completed parts within 24 hours of starting the upload; the browser cannot silently reopen a local file.
Upload history shows the product, progress, and resume deadline. A remote-link import copies the file into private storage; retrying it may restart from the source rather than resume at the same byte. Protected or expired download links need a new direct link.
A file is attached only after its stored object, size, and upload session are checked. Incomplete uploads are not customer downloads. Public artwork and demos remain separate from private delivery files; attaching a file does not publish the product or grant ownership.
SoundSync
Add the private files after reviewing the import
The delivery step lets you select multiple installers or archives and review their product matches. Its resume guidance applies to this importer; public promotional media and customer-authorized downloads remain separate workflows.
SoundSync
Resume a local file
-
Open upload history
Choose the correct product and inspect the unfinished job and deadline.
-
Reselect the same file
The file identity must match; a renamed or changed archive is not interchangeable.
-
Continue remaining parts
Completed parts are reused within the original 24-hour session. Network retries do not extend that deadline.
-
Wait for attachment
Completion verifies the stored object and expected size before the file is listed as attached.
SoundSync
When an upload cannot continue
| Situation | Next step |
|---|---|
| Expired session | Start a new upload; the previous deadline is not extended by a retry. |
| File changed or fingerprint mismatch | Choose the original file or start a new job for the changed content. |
| Remote URL expired or requires sign-in | Supply a fresh direct URL or upload locally. |
| Upload complete but not attached | Inspect job status and attachment errors before starting another copy. |
| Unauthorized product | Ask the workspace owner for the correct product and file-management permissions. |
Protect download credentials
Private source links and signed storage URLs may authorize downloads. Do not put them in public screenshots, analytics labels, or a product description. A customer download is authorized separately from an upload and from a checkout return URL.
SoundSync
Delivery contracts
A private storage key is not ownership proof
Attaching a private delivery file requires a verified object available to the selected workspace and product scope. A copied key from another developer cannot be used to grant that file to your customers. Identical files can still be deduplicated after your own upload has been verified; source product assignments continue to apply.
New-policy products use the managed attachment workflow and the chosen storage allowance. Historical file references remain intact; adding a different file still requires ownership proof. This does not change already-issued offline licensing grants.
Activate production storage before growing beyond the draft allowance
Draft managed storage includes 2 GB without production activation. Larger new additions require an active hosting service and verified billing. The workspace owner can use Activate production storage on Billing and explicitly confirm the monthly pricing. Activation starts the selected service; it is not an immediate card charge.
URL imports have unknown sizes and require active production storage and verified billing before queuing. Small draft trials can use local files instead. Full Store includes 500 GB and Licensing + Hosting includes 100 GB across current and retained versions. New-upload holds do not remove existing downloads.
Distinguish current private uploads from older delivery links
New managed product uploads use private delivery storage and authorized, short-lived download links. Some older files retain legacy public delivery locations. Signing an application download does not revoke a public URL that was already shared.
Legacy migration uses verified private copies while preserving product references, versions and customer access. A prepared migration or a private copy is not proof that historical public URLs have been retired. Contact support when an older catalog needs a delivery review.
