Storage: Clean up partial files from failed or aborted uploads

An upload can create partial files in the backend file service before it finishes. If the upload fails or stops, those partial files need cleanup. Examples include a network failure during a standard upload and a resumable upload that the user abandons.

Supabase cleans up partial files from failed or aborted uploads automatically. You can’t view the backend file service, so you can’t list these files yourself.

Check for a size mismatch

Compare your storage size from object metadata with the storage size on your organization usage page. A large difference can mean the project has partial or orphaned files.

• Direct database or SQL changes to Storage tables bypass the Storage service and create orphaned files.
• The SQL query measures your data at one moment, while organization usage is an average across the day. Small differences are expected.

Contact support

If the sizes still don’t match, open a support ticket so the team can review your project. If you find an upload failure that doesn’t get cleaned up, include the details and reproduction steps in the ticket.