mirror of
https://github.com/supabase/supabase.git
synced 2026-10-13 05:09:12 +03:00
5b349a49c3
new troubleshooting doc to download complete storage <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Documentation** * Added a "Download Objects" guide detailing: downloading from the Dashboard UI, using the CLI to list/copy objects, connecting with S3-compatible clients (enable S3, generate keys, use endpoint), migration scripts for bulk downloads, note on separate file metadata storage, and links to backup/restore and authentication references. * **New Features** * Added a "Download Objects" entry to the docs navigation under Storage → Management. <!-- end of auto-generated comment: release notes by coderabbit.ai --> --------- Co-authored-by: Chris Chinchilla <chris@chrischinchilla.com> Co-authored-by: Chris Chinchilla <chris.ward@supabase.io>
53 lines
2.3 KiB
Plaintext
53 lines
2.3 KiB
Plaintext
---
|
|
id: 'storage-management'
|
|
title: 'Download Objects'
|
|
description: 'Learn about downloading objects'
|
|
subtitle: 'Learn about downloading objects'
|
|
sidebar_label: 'Download Objects'
|
|
---
|
|
|
|
You can download Supabase Storage files can in a variety of ways depending on your use case.
|
|
|
|
## From the Dashboard
|
|
|
|
You can download individual files directly from the [**Storage > Files**](/dashboard/project/_/storage/buckets) section of the Dashboard by browsing to your bucket and selecting files.
|
|
|
|
## Using the Supabase CLI
|
|
|
|
You can use the `supabase storage` commands to list and copy objects from your linked project.
|
|
|
|
See the [CLI reference](/docs/reference/cli/supabase-storage) for available commands.
|
|
|
|
## Using an S3-compatible client
|
|
|
|
Supabase Storage exposes an S3-compatible endpoint, which means you can use tools like [Cyberduck](https://cyberduck.io/) (via a connection profile), AWS CLI, or rclone to browse and download your files.
|
|
|
|
To connect:
|
|
|
|
1. Go to [**Storage > Configuration > S3**](/dashboard/project/_/storage/s3) section of the Dashboard.
|
|
2. Enable the S3 protocol and generate an access key + secret key pair (Save it immediately as it is shown once).
|
|
3. Use your S3-compatible tool with the endpoint and credentials from the Dashboard.
|
|
|
|
See the [S3 authentication doc](/docs/guides/storage/s3/authentication) for full connection details.
|
|
|
|
<Admonition type="tip">
|
|
|
|
For downloading a large number of objects, using an S3-compatible tool like rclone or Cyberduck is significantly more efficient than downloading files individually.
|
|
|
|
</Admonition>
|
|
|
|
## Using migration scripts
|
|
|
|
For bulk downloads or project migrations, you can use the scripts from our migration docs:
|
|
|
|
- **Node.js script** — see "Migrating storage objects" in the [migration guide](/docs/guides/platform/migrating-within-supabase/backup-restore)
|
|
- **Google Colab script** — see "Migrate storage objects to new project's S3 storage" in the [dashboard restore guide](/docs/guides/platform/migrating-within-supabase/dashboard-restore)
|
|
|
|
## File metadata
|
|
|
|
<Admonition type="note">
|
|
|
|
File metadata is stored separately from the actual files. It lives in the `storage.buckets` and `storage.objects` tables in your Postgres database. If you need a complete backup (files + metadata), see the [backup and restore guide](/docs/guides/platform/migrating-within-supabase/backup-restore).
|
|
|
|
</Admonition>
|