# Supabase resumable uploads

**URL:** <https://community.weweb.io/t/supabase-resumable-uploads/9500>\
**Category:** Ask us anything\
**Tags:** supabase\
**Created:** [July 2, 2024, 8:19pm UTC](https://community.weweb.io/t/supabase-resumable-uploads/9500 "2024-07-02T20:19:15Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![Kawwl](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/kawwl/32/14297_2.png) [@Kawwl](https://community.weweb.io/u/Kawwl)\
**Post date:** [July 2, 2024, 8:19pm UTC](https://community.weweb.io/t/supabase-resumable-uploads/9500/1 "2024-07-02T20:19:15Z")

</div>

Hey guys,

I saw another thread about using resumable upload. I’m wondering if anyone has had luck with this yet? In the documentation Supabase also mentions UppyJS (?)

I’m not actually looking for the actual resumable feature, but rather uploading large files with stability and getting the progress bar of uploads. I’m concerned that many of the files may be pretty large, and that it will be really hard to give users comfort during upload.

---

<div class="post-metadata">

**Author:** ![Broberto](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/broberto/32/5918_2.png) [@Broberto](https://community.weweb.io/u/Broberto)\
**Post date:** [July 3, 2024, 6:22am UTC](https://community.weweb.io/t/supabase-resumable-uploads/9500/2 "2024-07-03T06:22:18Z")

</div>

You could do this with the exposed SDK instance that WeWeb provides. I think there is many mentions about this, or at least I’ve mentioned it quite a lot before the big update that we had to the SDK v2.

---

<div class="post-metadata">

**Author:** ![Kawwl](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/kawwl/32/14297_2.png) [@Kawwl](https://community.weweb.io/u/Kawwl)\
**Post date:** [July 3, 2024, 7:19am UTC](https://community.weweb.io/t/supabase-resumable-uploads/9500/3 "2024-07-03T07:19:41Z")

</div>

Have you done it?  
If so, were there any limitations, difficulties, things I should consider?

I probably have to search some more, but I didn’t quite grasp if anyone has had success with it.

---

<div class="post-metadata">

**Author:** ![Broberto](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/broberto/32/5918_2.png) [@Broberto](https://community.weweb.io/u/Broberto)\
**Post date:** [July 3, 2024, 7:45am UTC](https://community.weweb.io/t/supabase-resumable-uploads/9500/4 "2024-07-03T07:45:02Z")

</div>

I didn’t exactly do your usecase, but I’ve worked a lot with the SDK instance, with realtime and classic image uploads - before it even was a thing in the WeWeb’s plugin.

I’ll link you some resources that I can find on the forum 🙂

I usually do these kind of things as a part of my coaching sessions, where we either crack it on the meeting, or I provide specific and aimed guidance regarding issues, as we have more time to discuss this in depth. [You might want to book a session,](https://broberto.sk/consult) just to try it out, usually people tell me they get quite deeper understanding of the topics we discuss, especially Supabase.

This one is your problem-specific:

> [@What's the best way tu opload a file directly to Supabase storage?](https://community.weweb.io/t/whats-the-best-way-tu-opload-a-file-directly-to-supabase-storage/1517/55):
>
> @mander if you use the code I provided here async function uploadImages(images, bucket, path) { const storage = wwLib.wwPlugins.supabaseAuth.publicInstance.storage; const promises = []; for (let i = 0; i \< images.length; i++) { const image = images[i]; const randomName = generateRandomName(); // Implement your random name generation logic const filePath = `${path}/${randomName}.jpg`; const promise = storage .from(bucket) // Your bucket name goes her…

Other references to using Supabase SDK’s instance:

> [@Multiple Supabase Databases](https://community.weweb.io/t/multiple-supabase-databases/6345/11):
>
> I thought about it a little bit, We initialize plugins before an user is logged in (because we need auth plugins to work to fetch and restore the connected user for exemple). But here you need the supabase sdk to be initialised after the user was logged in, so you want to make it login to a third party first. But you will probably have a hard time making the third party be the authentication provider for supabase then (Having a Xano token will not magically make you able to access your supabase…

> [@Passing Supabase auth to web worker?](https://community.weweb.io/t/passing-supabase-auth-to-web-worker/7671):
>
> I have a web worker that’s calling a Supabase db function. Currently I have it creating a new Supabase client with the anon key in the worker. RLS prevents that from working correctly because access to the underlying table is set to only allow authenticated users. Disabling RLS gets it to work. Users will be authenticated in order to invoke this at all. It follows that I should be able to pass the authentication along to call the db function with the right access. My question is simply: what is…

> [@Displaying an image from Supabase](https://community.weweb.io/t/displaying-an-image-from-supabase/5630/12):
>
> You can go to your Page in the Pages section → Desired Page → Gear icon → Workflows There you can choose, when to trigger the workflow to run (Page Load, App Load etc…), then based on the parameters, for each page you can fetch your images, and add them to an array, or whatever logic you use and then just display - bind them. for the URL only, instead of download you can use the code @Alexis provided. or if your bucket is public, you can construct the public URL yourself, without the need t…

> [@Multiple bulk mass delete Supabase](https://community.weweb.io/t/multiple-bulk-mass-delete-supabase/5607):
>
> Is there a way enter multiple id’s to delete multiple rows using the Supabase Delete function?

---

<div class="post-metadata">

**Author:** ![Kawwl](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/kawwl/32/14297_2.png) [@Kawwl](https://community.weweb.io/u/Kawwl)\
**Post date:** [July 3, 2024, 8:02am UTC](https://community.weweb.io/t/supabase-resumable-uploads/9500/5 "2024-07-03T08:02:47Z")

</div>

I understand. I have no issues with Supabase Storage and WeWeb using regular storage. But, Supabase recommends any file over 6MB to use resumable upload (TUS); and limits standard uploads at 5GB.

I have to go down this path anyway, but I was wondering if anyone has done this before (or solved the 5GB limit or progress bar) in another way. I might just take you up on that call offer at some point.

Still looking for successful deployments of large file uploads and/or upload progress bar streaming with Supabase.

---

<div class="post-metadata">

**Author:** ![Broberto](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/broberto/32/5918_2.png) [@Broberto](https://community.weweb.io/u/Broberto)\
**Post date:** [July 3, 2024, 8:38am UTC](https://community.weweb.io/t/supabase-resumable-uploads/9500/6 "2024-07-03T08:38:36Z")

</div>

With the above mentioned resources you should be able to use resumable uploads as per their Docs. So I’d definitely give it a try 🙂

---

<div class="post-metadata">

**Author:** ![Kawwl](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/kawwl/32/14297_2.png) [@Kawwl](https://community.weweb.io/u/Kawwl)\
**Post date:** [July 4, 2024, 4:44pm UTC](https://community.weweb.io/t/supabase-resumable-uploads/9500/7 "2024-07-04T16:44:04Z")

</div>

I successfully implemented TUS.

 ![image](https://us1.discourse-cdn.com/flex016/uploads/weweb/original/2X/9/9a8543822df67af205f42975aef532d9eced7612.png)

I load this script on a global app workflow (thanks [https://weweb-embed.statechange.ai/](https://weweb-embed.statechange.ai/)):

```auto
  if(!window["scp-loading-fe9fdf6a-9c05-4016-8f9c-62ea62b08990"]) {
    window["scp-loading-fe9fdf6a-9c05-4016-8f9c-62ea62b08990"] = true;
    let doc;
    /* Adding script from https://cdn.jsdelivr.net/npm/tus-js-client@latest/dist/tus.js */
    doc = document.createElement('script');
    doc.src = 'https://cdn.jsdelivr.net/npm/tus-js-client@latest/dist/tus.js';
    document.body.appendChild(doc);
  }

```

Then i run this on submit. It’s a lot of logging, but i had some problems i had to troubleshoot.  
I’m also checking if the script is loaded, and if not, i load it. Not sure if needed, but ChatGPT and I did it anyway. I had some issues where I had to manually load the package.

I’m using the supabase auth session token to authenticate as well. Hopefully its secure enough.

```auto
const projectId = ' **SUPABASE PROJECT ID**';

// Importing tus.js library asynchronously
(function() {
	if (!window["scp-loading-fe9fdf6a-9c05-4016-8f9c-62ea62b08990"]) {
		window["scp-loading-fe9fdf6a-9c05-4016-8f9c-62ea62b08990"] = true;
		let script = document.createElement('script');
		script.src = 'https://cdn.jsdelivr.net/npm/tus-js-client@4.1.0/lib.es5/browser/index.min.js';
		script.onload = function() {
			startUpload();
		};
		document.body.appendChild(script);
	} else {
		startUpload();
	}
})();

async function uploadFile(bucketName, filePath, fileName, file) {
	console.log('Starting upload process...');
	const {
		data: {
			session
		}
	} = await wwLib.wwPlugins.supabaseAuth.publicInstance.auth.getSession();
	console.log('Session retrieved:', session);

	return new Promise((resolve, reject) => {
		console.log('Creating tus upload...');
		var upload = new tus.Upload(file, {
			endpoint: `https://${projectId}.supabase.co/storage/v1/upload/resumable`,
			retryDelays: [0, 3000, 5000, 10000, 20000],
			headers: {
				authorization: `Bearer ${session.access_token}`,
				'x-upsert': 'true',
			},
			uploadDataDuringCreation: true,
			removeFingerprintOnSuccess: true,
			metadata: {
				bucketName: bucketName,
				objectName: fileName,
				contentType: file.type,
				cacheControl: '3600',
			},
			chunkSize: 6 * 1024 * 1024,
			onError: function(error) {
				console.log('Upload failed:', error);
				reject(error);
			},
			onProgress: function(bytesUploaded, bytesTotal) {
				var percentage = ((bytesUploaded / bytesTotal) * 100).toFixed(0);
				console.log('Upload progress:', percentage + '%');

				// Update progress to context variables if it exists
				if (context.component && context.component.variables && context.component.variables[' **SOMEWHERE TO DISPLAY %**'] !== undefined) {
					context.component.variables[' **SOMEWHERE TO DISPLAY %**'] = percentage;
				} else {
					console.warn('Progress variable not found in context');
				}
			},
			onSuccess: function() {
				console.log('Download %s from %s', upload.file.name, upload.url)
				resolve()
			},
		});

		upload.findPreviousUploads().then(function(previousUploads) {
			console.log('Previous uploads found:', previousUploads);
			if (previousUploads.length) {
				upload.resumeFromPreviousUpload(previousUploads[0]);
			}
			console.log('Starting the upload...');
			upload.start();
		}).catch((error) => {
			console.log('Error finding previous uploads:', error);
			reject(error);
		});
	});
}

function startUpload() {
	console.log('Starting upload script...');
	const file = ' **YOUR ACTUAL FILE**';
	if (!file) {
		console.error('No file found in context variables');
		return;
	}

	const filePath = ` **CONSTRUCT FILE PATH** `;

	const bucketName = ' **YOUR BUCKET NAME**';
	const fileName = ` **YOUR FILE PATH + FILE NAME.EXT** `;

	uploadFile(bucketName, filePath, fileName, file).then(() => {
		console.log('File uploaded successfully');

		};
	}).catch((error) => {
		console.error('File upload failed', error);
	});
}

```

Additionally, you can trigger ie. a variable change or something onSuccess. I’m doing a variable change to true, and triggering a new workflow (with solution from @MatthewS [Triggering Component Workflow w/ JS Workaround - #2 by Doc](https://community.weweb.io/t/triggering-component-workflow-w-js-workaround/8209/2) )

---

<div class="post-metadata">

**Author:** ![Broberto](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/broberto/32/5918_2.png) [@Broberto](https://community.weweb.io/u/Broberto)\
**Post date:** [July 4, 2024, 6:08pm UTC](https://community.weweb.io/t/supabase-resumable-uploads/9500/8 "2024-07-04T18:08:01Z")

</div>

By the way, the same way you’d use the Supabase instance (via the wwLib) you also can go and change variables, and trigger workflows, without workarounds.

---

<div class="post-metadata">

**Author:** ![Kawwl](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/kawwl/32/14297_2.png) [@Kawwl](https://community.weweb.io/u/Kawwl)\
**Post date:** [July 4, 2024, 6:55pm UTC](https://community.weweb.io/t/supabase-resumable-uploads/9500/9 "2024-07-04T18:55:48Z")

</div>

I can? I have done the variable change on success but I can’t trigger the component workflow? How do I access the workflow id?