Docs /Uploading Products Dashboard →

Uploading Products

Best practices for organising, uploading, and managing your digital products on Continuata.

Preparing Your Files

Proper file organisation before upload ensures your customers have the best experience.

epic-drum-kit-v1/
├── README.txt
├── samples/
│   ├── kicks/
│   │   ├── kick_01.wav
│   │   └── kick_02.wav
│   └── snares/
│       ├── snare_01.wav
│       └── snare_02.wav
├── loops/
│   └── full_beat.wav
└── license.txt

Upload Methods

Dashboard Upload (Recommended)

API Upload

For automated workflows, use the upload API:

// 1. Check which packs already exist (skip re-uploading unchanged content)
POST /api/pack-check
{
  "vendorId": "audio-company",
  "packHashes": ["sha256_pack1", "sha256_pack2", ...]
}
// Response: { "existing": ["sha256_pack1"] }

// 2. Upload each new pack (raw bytes, ~8MB each)
PUT /api/blob/{vendorId}/packs/pack-{sha256}
Content-Type: application/octet-stream
[raw pack bytes]

// 3. Upload the manifest (describes all files, packs, and segments)
POST /api/manifest
{
  "vendorId": "audio-company",
  "productId": "epic-drums-v1",
  "productHash": "abc123...",
  "manifest": { "v": 3, "packs": [...], "files": [...] }
}

Version Management

Each product can have multiple versions with different activation states:

File Processing

The upload flow runs five stages in order. Each one shows live progress in the dashboard.

Storage Optimization

Automatic Deduplication

Packs are deduplicated across versions. Before uploading, Continuata checks which packs already exist in storage — only packs containing changed or new files need to be transferred:

Storage Efficiency Tips

• Use consistent sample rates and bit depths across your library
• Normalise audio levels before uploading to maximise deduplication
• Keep common files (READMEs, licenses) identical across products
• Use lossless formats for master files when possible

Pause & Resume

Uploads can be paused and resumed at any point during the uploading stage. Use the Pause button that appears once the upload begins. Current speed (MB/s) and estimated time remaining are shown throughout.

Because packs are content-addressed, a resumed upload picks up exactly where it left off — any packs already confirmed in storage are not re-transferred.

Troubleshooting Uploads