Use Case Examples
Attachments / Files
Syncing large attachments/files directly using PowerSync is not recommended.
Smaller files can be stored as base64-encoded data, but syncing many larger files using database rows may cause performance degradation.
On the other hand, PowerSync works well for syncing the attachment metadata, which could include the file path, name, size, and type. The client may then download the file from the storage provider, such as Supabase Storage or AWS S3.
The example implementations above use Supabase Storage as storage provider.
Helper Packages
We currently have these helper packages available to manage attachments:| SDK | Attachments Helper Package | Example Implementation |
|---|---|---|
| React Native / JavaScript | powersync/attachments | To-Do List demo app |
| Flutter | powersync_attachments_helper | To-Do List demo app |
| Kotlin | attachments | To-Do List demo app |
| Swift | attachments | To-Do List demo app |
- For more information on the use of Supabase as the storage provider, refer to Handling Attachments
- To learn how to adapt the implementations to use AWS S3 as the storage provider, see this tutorial