Connect your own S3 storage server
Fileflare does not apply storage limitations when you connect your own S3 storage server, giving you unlimited storage possibilities.
S3 stands for Simple Storage Service. It was originally created by Amazon Web Services, but other platforms have adopted the architecture, such as Cloudflare, Digital Ocean, and others.
You can essentially have your own cloud storage space on either of these platforms, and then connect it to Fileflare so that Fileflare will use your storage service for any uploaded files. It gives you more control over your storage limits, costs and files.
Connect Cloudflare R2 server to Fileflare - Go to guide
Connect Amazon S3 server to Fileflare - Go to guide
Comparison guide for all S3-compatible server costs and details - Go to guide
Watch a video on how to connect Cloudflare R2:
View table in full with links and data
These are settings on the S3 settings page.
This feature is only used for legacy compatibility; older S3 clients and tools may default to or require path-style endpoints. This refers to the way requests are structured when accessing S3 buckets and objects. With path-style endpoints, the bucket name is included in the path portion of the URL. In contrast, virtual-hosted style endpoints include the bucket name as part of the domain name (as a subdomain).
Enabling this setting will delete the files from your S3 bucket when you delete the files inside the Fileflare user interface.
Enabling this setting ensures that all files uploaded via the Fileflare uploader are renamed using the UUID4 format when stored in your S3 bucket, eliminating the risk of overwriting existing files with the same name in the bucket. While the UUID4 format is used exclusively within the bucket, the original filenames are retained in Fileflare's system for display in the app interface and for file delivery to your customers.
If this setting is disabled, files uploaded with duplicate filenames will overwrite existing files in the S3 bucket. Note that UUID4 filenames cannot be reverted to their original names within the bucket.
What is an S3 server?
S3 stands for Simple Storage Service. It was originally created by Amazon Web Services, but other platforms have adopted the architecture, such as Cloudflare, Digital Ocean, and others.
You can essentially have your own cloud storage space on either of these platforms, and then connect it to Fileflare so that Fileflare will use your storage service for any uploaded files. It gives you more control over your storage limits, costs and files.
Learn how to connect your own S3
Connect Cloudflare R2 server to Fileflare - Go to guide
Connect Amazon S3 server to Fileflare - Go to guide
Comparison guide for all S3-compatible server costs and details - Go to guide
Watch a video on how to connect Cloudflare R2:
View table in full with links and data
Explanation of settings
These are settings on the S3 settings page.
Use path style endpoint
This feature is only used for legacy compatibility; older S3 clients and tools may default to or require path-style endpoints. This refers to the way requests are structured when accessing S3 buckets and objects. With path-style endpoints, the bucket name is included in the path portion of the URL. In contrast, virtual-hosted style endpoints include the bucket name as part of the domain name (as a subdomain).
Delete files in S3 when removed from the App?
Enabling this setting will delete the files from your S3 bucket when you delete the files inside the Fileflare user interface.
Rename my files to keep their name unique?
Enabling this setting ensures that all files uploaded via the Fileflare uploader are renamed using the UUID4 format when stored in your S3 bucket, eliminating the risk of overwriting existing files with the same name in the bucket. While the UUID4 format is used exclusively within the bucket, the original filenames are retained in Fileflare's system for display in the app interface and for file delivery to your customers.
If this setting is disabled, files uploaded with duplicate filenames will overwrite existing files in the S3 bucket. Note that UUID4 filenames cannot be reverted to their original names within the bucket.
Updated on: 23/01/2025
Thank you!