There are several ways to get files into Fileflare — direct upload through the app, connecting your own S3-compatible storage, programmatic upload via the API, and bulk attachment via CSV. The right method depends on how many files you have, how big they are, and where they live today.
Available on all plans. There’s no per-file size limit (a single file can be as large as your plan storage allows), but very large batches are best uploaded via S3 or in smaller groups to avoid browser timeouts.
When you’d use which method
- A handful of files, mixed sizes — use the native uploader. Done in two clicks.
- Hundreds or thousands of files — connect your own S3 (Cloudflare R2 is the cheapest option), upload directly to the bucket, then sync with Fileflare.
- Files already hosted somewhere (Dropbox, Drive, course platform) — use URL assets instead of uploading.
- Programmatic / scripted uploads — use the API.
- Mapping uploaded files to specific products in bulk — use the CSV bulk-attach feature after uploading.
Upload methods
Method 1: Native Fileflare uploader
The simplest path. Upload from your computer directly to Fileflare’s storage.
- Open Fileflare from your Shopify Apps menu.
- Click Upload in the main navigation.
- Drag files in or click to browse. Upload as many as you want, up to your plan’s storage allowance.
Recommendation: upload in batches of 50–100 files. Larger batches can fail mid-upload due to browser memory limits or transient network issues. If you have thousands of files, switch to Method 2.
Method 2: Connect your own S3 storage
If you already use AWS S3 or a compatible service (Cloudflare R2, Backblaze B2, DigitalOcean Spaces, Wasabi), connect it to Fileflare instead of uploading to Fileflare’s hosted storage. Files stay on your bucket; Fileflare reads them and delivers signed download links.
Why use your own S3:
- Storage costs are yours, not Fileflare’s — useful for very large file libraries.
- Files you’ve already uploaded for another purpose (a course platform, a media library) don’t need to be re-uploaded.
- Bulk uploading thousands of files is much faster via S3 tooling than the browser uploader.
The cheapest option is Cloudflare R2: free up to 10 GB, free egress (no bandwidth charges), ~$15/TB after that. See Connect Cloudflare R2. For AWS, see Connect Amazon S3.
R2 / S3 upload tools
- R2Uploader — free browser-based uploader (recommended for R2)
- R2up — alternative free browser uploader
- CloudMounter — macOS app, paid
- AWS CLI — for scripted uploads
Method 3: API upload
If you have an existing build process or want to wire uploads into your own tooling, the file upload API lets you create assets programmatically. Useful for stores that generate digital products on-the-fly (POD-style) or migrate large catalogs.
Method 4: Bulk URL assets via CSV
If your files live on Dropbox, Drive, or another external service and you don’t want to re-host them, you can bulk-create URL assets and attach them to products in one CSV upload. See Bulk add URLs and attach to products.
After uploading: attach to products
Uploaded files don’t deliver to customers until they’re attached to Shopify products. You have two options:
- One product at a time — go to Products in Fileflare, click a product, and attach assets from the asset library.
- Bulk via CSV — map files to products by SKU. See Bulk attach via CSV.
Common issues
- Upload fails partway through — the most common cause is a browser tab going to sleep, a flaky network, or a browser extension blocking large requests. Try a different browser, fully restart your current browser, or split the batch into smaller groups.
- “Insufficient storage” error — you’ve hit your plan’s storage limit. Either upgrade your plan, or connect your own S3 (S3-hosted files don’t count toward your Fileflare quota). See how-much-storage-can-i-get.
- Upload completes but the file isn’t visible in the asset list — refresh the Assets page. If it still doesn’t appear, check the upload log in your browser’s network tab — sometimes the request shows “succeeded” but the server flagged the file (e.g., for an unsupported extension). Contact support with the filename if this persists.
- S3 sync isn’t pulling all files — confirm Fileflare’s IAM permissions on the bucket are correct (read + list). The most common misconfiguration is missing
s3:ListBucket. See the S3 setup guide. - Very large file (50 GB+) upload times out — switch to S3. Direct browser uploads aren’t reliable past about 5 GB depending on your network.
- File extension is rejected — Fileflare accepts most extensions, but some (executables on certain plans, certain media containers) may be flagged. Contact support with the file type if you’re stuck.