Why External Storage?
By default, Fileloom stores generated PDFs in Firebase Storage with permanent public URLs. External storage lets you:- Keep PDFs in your infrastructure — Meet compliance and data residency requirements
- Integrate with existing workflows — Use your current storage systems
- Control access — Manage permissions with your own policies
- Reduce costs — Leverage existing storage allocations
Supported Providers
AWS S3
Store PDFs in Amazon S3 buckets with full control over regions, paths, and permissions
Supabase Storage
S3-compatible storage integrated with your Supabase project
Setting Up Storage Integrations
Open Workspace Settings
Click the settings icon in your workspace sidebar to open Workspace Settings.
Go to Integrations
Select Integrations from the left menu. You’ll see the Storage Integrations section with all supported providers.
Connect a Provider
Find the storage provider you want to use (Amazon S3 or Supabase Storage) and click the Connect button.
Enter Credentials
Fill out the connection form with your provider credentials (bucket name, access keys, region, etc.).
Automatic Connection Test
Click Connect to save. Fileloom automatically runs a connection test to verify your credentials and permissions.
Storage Mode Settings
Once you have at least one connection, you can configure how Fileloom handles PDF storage. In the Settings section below your connections, choose your preferred Save on mode:| Mode | Fileloom Storage | External Storage | Best For |
|---|---|---|---|
| Fileloom | ✅ | ❌ | Simple setup, getting started |
| External | ❌ | ✅ | Compliance, existing infrastructure |
| Both | ✅ | ✅ | Redundancy, migration period |
Mode Behaviors
Fileloom Mode (Default)- PDFs stored in Firebase Storage
- Permanent public URLs
- 24-hour signed URLs for secure access
- No external configuration needed
- PDFs stored only in your connected external provider
- URLs from your storage provider
- If external upload fails, falls back to Fileloom to prevent data loss
- PDFs stored in Fileloom AND external provider
- Primary URL from Fileloom
- External copies listed in API response
- Best for gradual migration or backup
Managing Connections
After connecting a provider, you can manage it from the Integrations page:- Primary — If you have multiple connections, one is marked as Primary and used first
- Connected / Inactive — Shows the current status of each connection
- Actions menu (⋮) — Edit credentials, run connection test, or disconnect
Connection Status
| Status | Description |
|---|---|
| Connected | Working normally, ready to receive files |
| Inactive | Connection disabled or credentials invalid |
Path Patterns
Customize how files are organized in your external storage using path pattern variables:| Variable | Description | Example |
|---|---|---|
{year} | Current year | 2024 |
{month} | Current month (01-12) | 12 |
{day} | Current day (01-31) | 15 |
{workspace} | Workspace ID | ws_abc123 |
{template} | Template ID | tpl_xyz789 |
{filename} | Generated filename | invoice-001.pdf |
{fileid} | Unique file ID | file_abc123 |
API Response
When external storage is configured, the API response includes external copy information:Response
Plan Availability
External storage integrations are available on all plans.| Feature | Free | Starter | Growth | Scale+ |
|---|---|---|---|---|
| External Storage | ✅ | ✅ | ✅ | ✅ |
| Multiple Connections | ❌ | ❌ | ✅ | ✅ |

