A rebuilt, resumable upload engine

Uploading from a venue is the most fragile moment in a creator's day. One dropped connection used to mean starting a whole batch again — at 1am, on hotel Wi-Fi, with a couple waiting. That had to stop being a risk.

• Resumable, chunked uploads — a dropped connection resumes mid-file
• A durable queue that survives refreshes, tab closes and sleeping phones
• Per-file state: queued, uploading, retrying, verified, ready
• Automatic retries with backoff, plus clear, plain-language errors
• Completed files are never re-uploaded

Each file gets its own record with a fingerprint, byte offset and state, stored locally and on our side. When the connection returns, the queue resumes each unfinished file from its last confirmed byte instead of starting the batch again.

Where to find it — Upload from the dashboard, or the Upload screen on your phone.

• Creators did not want to re-upload everything because one file failed
• Venue Wi-Fi dropped mid-batch and progress was lost
• It was unclear whether a file had actually arrived

What we did: Every file now reports its own verified state, so you can close the tab, move to the car, and let the queue finish what's left.

Themes are summarised from creator conversations and feature requests — not attributed quotes.

Planned work connected to this release — shaped by the roadmap, not a delivery promise.

• Background uploads on mobile
• Per-venue network diagnostics