Using Edge Platforms with Public Hosting

Public Hosting lets you share files and directories via public URLs. By default, those URLs are served under the hosted-by-files.com domain, and you can replace that with your own domain natively by attaching a Custom Domain to the folder.

Put an edge platform in front of your Files.com public links instead of using a Custom Domain when you need more than a branded domain, such as rewrite rules that route requests across multiple domains or regions, or edge-level caching. Cloudflare Workers, Netlify Edge Functions, Akamai EdgeWorkers, Vercel, Fastly Compute@Edge, and AWS Lambda@Edge all support URL rewriting at the edge. Each provider lets you modify requests and responses without redirecting users or exposing the underlying Files.com URLs. Refer to Implementing URL Rewrites for setup instructions.

This pattern gives you full control over the domain, branding, and delivery experience. Unlike the native Custom Domain option, it requires you to build and maintain that integration yourself.

Caching at the edge also reduces repeat requests to your Files.com site. Users download content from the edge platform's servers instead of going back to Files.com on every request, which lowers outbound data usage and reduces transfer usage costs.

For example, when you distribute large files such as product manuals, videos, or software installers, only the first request reaches Files.com. Subsequent downloads are served from the edge. The savings are meaningful at scale.

Edge Platforms with Public Hosting Use Cases covers patterns for serving multi-region or multi-brand content from clean, branded URLs, including examples in healthcare, media, and manufacturing.