Uppy: Resume upload after browser refresh/crash
Hi there!
First, I would like to congratulate the Uppy devs/maintainers for such a great project.
Having said that, I'm working on a project where we've using the AWS S3 Multipart plugin to upload files straight to an S3 bucket from the browser.
While resuming works if we get disconnected and reconnect, it won't work if the page gets refreshed or the browser crashes.
Since we're dealing with large video files, some of our locations with slower connections would benefit from resuming after a crash, avoiding to upload the entire file again.
We couldn't find anything in the Uppy documentation that would enables us to do this.
The only related issue we found was #433, but it seems to be GoldenRetriever specific, which we don't use.
So did we miss something, or is this currently not possible? And if not, would you consider such feature?
Thank you!
quetzyg
All 3 comments
Hi! And thanks!
For upload resumeability Uppy supports tus.io: https://uppy.io/docs/tus/. That requires that you run tus on your server side too. It’s a standard protocol adopted by Vimeo and Transloadit, among others. Refresh or browser crash — user will have to re-select a file, and then tus on the client and server will resume the upload from where it was dropped.
Golden Retriever compliments that, and makes sure to automatically restore the files that were in progress before browser crash / refresh. It does so by keeping smaller files in IndexedDB, and larger in Service Worker memory. Here’s a demo video of that: https://uppy.io/images/blog/golden-retriever/uppy-golden-retriever-crash-demo-2.mp4 (actual demo starts at 0:32).
arturi
on 11 Jul 2018
Thank you for replying @arturi.
I'll let the team know and we'll decide on what to do next.
Appreciated!
quetzyg
on 11 Jul 2018
Should we leave a note in the Golden Retriever docs that only tus uploads can resume after a crash / accidental-navigate-away?
kvz
on 11 Jul 2018
Related issues
brandonccx
·
4Comments
enneid
·
4Comments
aleccool213
·
3Comments
mokutsu-coursera
·
3Comments
rrjanbiah
·
3Comments
Most helpful comment
Hi! And thanks!
For upload resumeability Uppy supports tus.io: https://uppy.io/docs/tus/. That requires that you run tus on your server side too. It’s a standard protocol adopted by Vimeo and Transloadit, among others. Refresh or browser crash — user will have to re-select a file, and then tus on the client and server will resume the upload from where it was dropped.
Golden Retriever compliments that, and makes sure to automatically restore the files that were in progress before browser crash / refresh. It does so by keeping smaller files in IndexedDB, and larger in Service Worker memory. Here’s a demo video of that: https://uppy.io/images/blog/golden-retriever/uppy-golden-retriever-crash-demo-2.mp4 (actual demo starts at 0:32).