Uploading Photos & Videos
How the resumable upload queue works
Aisle keeps a durable upload queue on your device so a dropped venue network never costs you a file.
You'll understand every state in the queue and what to do in each one.
Event
Amelia & James
Keep screen open · wake-lock on
Quick answer
Every file you add becomes a queued upload stored on your device. Aisle uploads in resumable chunks, so a lost connection continues from the last completed chunk instead of restarting. Nothing is lost if you close the tab — reopen the event and the queue picks up where it stopped.
Quick steps
- 1.Open the event and add files — they enter the queue as Queued.
- 2.Leave the tab open and the screen awake while Uploading.
- 3.Watch for Processing, then Ready.
- 4.Tap Retry on anything marked Failed before you leave the venue.
Full walkthrough with screens below.
Before you begin
Prerequisites
- An event created in your dashboard
- Media on the device you're uploading from
You'll walk away with
- Read the queue and know whether a wedding is safe to leave
- Recover failed files without re-uploading everything
Wedding venues have the worst networks you will ever work on. The upload engine assumes that: it writes every intended upload to a local queue on your device first, then transfers each file in resumable chunks.
Because progress is tracked per chunk on both the device and the server, an interruption costs you seconds, not a re-upload.
The five queue states
- 1Queued — recorded on your device, waiting for a transfer slot.
- 2Uploading — chunks are moving; the percentage is real, not estimated.
- 3Processing — the file arrived and Aisle is generating previews and posters.
- 4Ready — visible in the gallery and safe to deliver.
- 5Failed — the transfer stopped for a reason retrying can't fix on its own; tap Retry.
What happens when the network drops
Aisle pauses rather than fails. It retries with increasing backoff, and switching from venue Wi-Fi to cellular mid-upload is safe — the transfer resumes on the new connection from the last completed chunk.
On iPhoneOn iPhone, keep the tab in the foreground. Aisle holds a wake lock so the screen won't sleep, but iOS can suspend a backgrounded tab after a few minutes.
If you close the tab
The queue lives on your device, not in memory. Reopen the event in the same browser and unfinished uploads resume automatically. For files the browser can no longer read, Aisle asks you to reselect them — the already-uploaded chunks are still reused.
Common mistakes
- Leaving the venue with files still marked Uploading.
- Force-quitting the browser to 'restart' a slow upload.
- Clearing browser data mid-wedding, which erases the local queue.
Pro tips
- Plug into power before a 200+ file upload — sustained transfer is the biggest battery draw of the day.
- Turn Low Power Mode off; it throttles the network stack.
- Upload in waves through the day instead of one dump at the end.
Best practices
- 1Offload during cocktail hour so the reception isn't your only upload window.
- 2Keep the event open on one device — a second device starts its own queue.
- 3Retry failed files while you're still on-site and can change networks.
Troubleshooting
If something goes wrong
A file sits in Processing for a long time
Long 4K clips take a few minutes. It's server-side, so you can close the tab.
Failed with a file-access error
Reselect the file when prompted. Completed chunks are reused.
Progress is moving very slowly
Compare Wi-Fi and cellular, then stay on the faster one. Switching mid-file is safe.
Related resources
Keep building skill
Frequently asked
Do I lose progress if I switch from Wi-Fi to 5G?
No. The transfer resumes from the last completed chunk on the new network.
Can I upload from two phones at once?
Yes. Each device keeps its own queue and both feed the same gallery.
Are my originals compressed?
No. Originals are stored as-is; previews are generated separately.
Did this guide solve the problem?
Need more help?
Related articles