Profile Photo Setup

​

What Is Profile Photo Storage?

​

Quick Overview

-- Users can upload their own photos
CREATE POLICY "Users upload own" ON storage.objects
FOR INSERT TO authenticated WITH CHECK (
  bucket_id = 'profile-photos' AND
  (storage.foldername(name))[1] = 'avatars' AND
  auth.uid()::text = (storage.foldername(name))[2]
);

-- Photos are public (read)
CREATE POLICY "Photos public" ON storage.objects
FOR SELECT TO public USING (bucket_id = 'profile-photos');

self.profilePhotoStorageClient = SupabaseProfilePhotoStorageClient(
    supabaseClient: supabaseClient,
    bucketName: "profile-photos"
)

​

How It Works

Upload Flow:
User selects photo → Compress (~500KB) → Upload to Supabase → Update profile

Download Flow:
App opens → Load from Supabase → Cache locally → Display

• ✅ Photos sync across devices
• ✅ Automatic compression
• ✅ Public CDN URLs
• ✅ Graceful fallback to local
• ✅ Privacy-first (iOS 17+ PhotosPicker)

​

Prerequisites

• Supabase project configured
• Supabase dependency in Storage package
• User authenticated

​

What You Get

• ✅ Upload profile photos
• ✅ Photos sync across devices
• ✅ Automatic compression
• ✅ CDN-hosted images
• ✅ Local fallback if upload fails
• ✅ No camera permissions needed (PhotosPicker)

​

Complete Guide

• Storage bucket configuration
• Row Level Security policies
• Upload implementation
• Compression strategy
• Error handling
• Testing procedures

​

Related Guides

​

Need Help?

• 📖 Complete troubleshooting in full guide
• 💬 Create an issue
• 🔍 Check Supabase Storage logs